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 The old sibyte / swarm / Broadcom BCM1250 support has been
36 removed from the mips port.
39 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
40 7.0.1. Please see the 20141231 entry below for information about
41 prerequisites and upgrading, if you are not already using clang 3.5.0
45 Remove the timed and netdate programs from the base tree. Setting
46 the time with these deamons has been obsolete for over a decade.
49 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
50 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
51 it produces broken binaries when ifuncs are in use. Users needing
52 GNU ld should install the binutils port or package.
55 The BSD crtbegin and crtend code has been enabled by default. It has
56 had extensive testing on amd64, arm64, and i386. It can be disabled
57 by building a world with -DWITHOUT_BSD_CRTBEGIN.
60 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
61 has been converted to a port (misc/ctm) and will be removed from
62 FreeBSD-13. It is available as a package (ctm) for all supported
66 The default newsyslog.conf(5) file has been changed to only include
67 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
68 the filenames end in '.conf' and do not begin with a '.'.
70 You should check the configuration files in these two directories match
71 this naming convention. You can verify which configuration files are
72 being included using the command:
76 Ports for the DRM modules have been simplified. Now, amd64 users should
77 just install the drm-kmod port. All others should install
80 Graphics hardware that's newer than about 2010 usually works with
81 drm-kmod. For hardware older than 2013, however, some users will need
82 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
83 than 2008 usually only works in drm-legacy-kmod. The graphics team can
84 only commit to hardware made since 2013 due to the complexity of the
85 market and difficulty to test all the older cards effectively. If you
86 have hardware supported by drm-kmod, you are strongly encouraged to use
87 that as you will get better support.
89 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
90 elsewhere, the drm and drm2 modules will be eliminated from the src base
91 soon (with a limited exception for arm). Please update to the package asap
92 and report any issues to x11@freebsd.org.
94 Generally, anybody using the drm*-kmod packages should add
95 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
96 cross-threading surprises, especially with automatic driver
97 loading from X11 startup. These will become the defaults in 13-current
101 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
102 custom kernel and module loading configuration files must be updated
103 accordingly. Moreover, interfaces previous presented as ixlvN to the
104 system are now exposed as iavfN and network configuration files must
105 be adjusted as necessary.
108 OpenSSL has been updated to version 1.1.1. This update included
109 additional various API changes througout the base system. It is
110 important to rebuild third-party software after upgrading. The value
111 of __FreeBSD_version has been bumped accordingly.
114 The legacy DRM modules and drivers have now been added to the loader's
115 module blacklist, in favor of loading them with kld_list in rc.conf(5).
116 The module blacklist may be overridden with the loader.conf(5)
117 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
121 The cam(4) based nda(4) driver will be used over nvd(4) by default on
122 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
123 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
124 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
128 Reproducible build mode is now on by default, in preparation for
129 FreeBSD 12.0. This eliminates build metadata such as the user,
130 host, and time from the kernel (and uname), unless the working tree
131 corresponds to a modified checkout from a version control system.
132 The previous behavior can be obtained by setting the /etc/src.conf
133 knob WITHOUT_REPRODUCIBLE_BUILD.
136 The Yarrow CSPRNG has been removed from the kernel as it has not been
137 supported by its designers since at least 2003. Fortuna has been the
138 default since FreeBSD-11.
141 devctl freeze/thaw have gone into the tree, the rc scripts have been
142 updated to use them and devmatch has been changed. You should update
143 kernel, userland and rc scripts all at the same time.
146 The default interpreter has been switched from 4th to Lua.
147 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
148 interpreter. If you have custom FORTH code you will need to set
149 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
150 src.conf for the build. This will create default hard links between
151 loader and loader_4th instead of loader and loader_lua, the new default.
152 If you are using UEFI it will create the proper hard link to loader.efi.
154 bhyve uses userboot.so. It remains 4th-only until some issues are solved
155 regarding coexisting with multiple versions of FreeBSD are resolved.
158 ls(1) now respects the COLORTERM environment variable used in other
159 systems and software to indicate that a colored terminal is both
160 supported and desired. If ls(1) is suddenly emitting colors, they may
161 be disabled again by either removing the unwanted COLORTERM from your
162 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
163 may not be observed in a future release.
166 The default pager for most commands has been changed to "less". To
167 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
171 The jedec_ts(4) driver has been removed. A superset of its functionality
172 is available in the jedec_dimm(4) driver, and the manpage for that
173 driver includes migration instructions. If you have "device jedec_ts"
174 in your kernel configuration file, it must be removed.
177 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
178 This should have no effect if the kernel is booted via BIOS/legacy boot.
179 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
180 has a buggy firmware that prevents a successful boot due to use of
184 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
185 support has been removed from the tree. These ports were
186 obsolete and/or known to be broken for many years.
189 loader.efi has been augmented to participate more fully in the
190 UEFI boot manager protocol. loader.efi will now look at the
191 BootXXXX environment variable to determine if a specific kernel
192 or root partition was specified. XXXX is derived from BootCurrent.
193 efibootmgr(8) manages these standard UEFI variables.
196 zfsloader's functionality has now been folded into loader.
197 zfsloader is no longer necessary once you've updated your
198 boot blocks. For a transition period, we will install a
199 hardlink for zfsloader to loader to allow a smooth transition
200 until the boot blocks can be updated (hard link because old
201 zfs boot blocks don't understand symlinks).
204 ARM64 now have efifb support, if you want to have serial console
205 on your arm64 board when an screen is connected and the bootloader
206 setup a frambuffer for us to use, just add :
210 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
211 an screen connected as the firmware will setup a framebuffer are that
212 u-boot will expose as an EFI framebuffer.
215 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
216 or take steps to update /etc/passwd before doing installworld on
217 existing systems. Do not skip the "mergemaster -Fp" step before
218 installworld, as described in the update procedures near the bottom
219 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
220 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
221 the ntp config file contain options that change file/dir locations.
222 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
223 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
224 taking steps to ensure that all required files/dirs are accessible
228 Big endian arm support has been removed.
231 The static environment setup in kernel configs is no longer mutually
232 exclusive with the loader(8) environment by default. In order to
233 restore the previous default behavior of disabling the loader(8)
234 environment if a static environment is present, you must specify
235 loader_env.disabled=1 in the static environment.
238 The ABI of syscalls used by management tools like sockstat and
239 netstat has been broken to allow 32-bit binaries to work on
240 64-bit kernels without modification. These programs will need
241 to match the kernel in order to function. External programs may
242 require minor modifications to accommodate a change of type in
243 structures from pointers to 64-bit virtual addresses.
246 On i386 and amd64 atomics are now inlined. Out of tree modules using
247 atomics will need to be rebuilt.
250 The '%I' format in the kern.corefile sysctl limits the number of
251 core files that a process can generate to the number stored in the
252 debug.ncores sysctl. The '%I' format is replaced by the single digit
253 index. Previously, if all indexes were taken the kernel would overwrite
254 only a core file with the highest index in a filename.
255 Currently the system will create a new core file if there is a free
256 index or if all slots are taken it will overwrite the oldest one.
259 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
260 6.0.1. Please see the 20141231 entry below for information about
261 prerequisites and upgrading, if you are not already using clang 3.5.0
265 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
266 needed to be changed to work with it. This change was made with r335763
267 and requires a mergemaster / etcupdate / etc to update the installed file.
270 r334930 changed the interface between the NFS modules, so they all
271 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
274 As of r334391 lld is the default amd64 system linker; it is installed
275 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
279 The kernel / userland interface for devinfo changed, so you'll
280 need a new kernel and userland as a pair for it to work (rebuilding
281 lib/libdevinfo is all that's required). devinfo and devmatch will
282 not work, but everything else will when there's a mismatch.
285 The on-disk format for hwpmc callchain records has changed to include
286 threadid corresponding to a given record. This changes the field offsets
287 and thus requires that libpmcstat be rebuilt before using a kernel
291 The vxge(4) driver has been removed. This driver was introduced into
292 HEAD one week before the Exar left the Ethernet market and is not
293 known to be used. If you have device vxge in your kernel config file
297 The amd64 kernel now requires a ld that supports ifunc to produce a
298 working kernel, either lld or a newer binutils. lld is built by default
299 on amd64, and the 'buildkernel' target uses it automatically. However,
300 it is not the default linker, so building the kernel the traditional
301 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
302 binutils port/package). lld will soon be default, and this requirement
305 NOTE: As of r334391 lld is the default system linker on amd64, and no
306 workaround is necessary.
309 The nxge(4) driver has been removed. This driver was for PCI-X 10g
310 cards made by s2io/Neterion. The company was aquired by Exar and
311 no longer sells or supports Ethernet products. If you have device
312 nxge in your kernel config file it must be removed.
315 The tz database (tzdb) has been updated to 2018e. This version more
316 correctly models time stamps in time zones with negative DST such as
317 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
318 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
319 time zone abbreviations and the tm_isdst flag.
322 The ixgb(4) driver has been removed. This driver was for an early and
323 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
324 quickly shifted to the long lived ixgbe family. If you have device
325 ixgb in your kernel config file it must be removed.
328 The lmc(4) driver has been removed. This was a WAN interface
329 card that was already reportedly rare in 2003, and had an ambiguous
330 license. If you have device lmc in your kernel config file it must
334 Support for Arcnet networks has been removed. If you have device
335 arcnet or device cm in your kernel config file they must be
339 Support for FDDI networks has been removed. If you have device
340 fddi or device fpa in your kernel config file they must be
344 In addition to supporting RFC 3164 formatted messages, the
345 syslogd(8) service is now capable of parsing RFC 5424 formatted
346 log messages. The main benefit of using RFC 5424 is that clients
347 may now send log messages with timestamps containing year numbers,
348 microseconds and time zone offsets.
350 Similarly, the syslog(3) C library function has been altered to
351 send RFC 5424 formatted messages to the local system logging
352 daemon. On systems using syslogd(8), this change should have no
353 negative impact, as long as syslogd(8) and the C library are
354 updated at the same time. On systems using a different system
355 logging daemon, it may be necessary to make configuration
356 adjustments, depending on the software used.
358 When using syslog-ng, add the 'syslog-protocol' flag to local
359 input sources to enable parsing of RFC 5424 formatted messages:
362 unix-dgram("/var/run/log" flags(syslog-protocol));
365 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
366 of the 'imuxsock' module to let messages be processed by the
367 regular RFC 3164/5424 parsing pipeline:
369 module(load="imuxsock" SysSock.UseSpecialParser="off")
371 Do note that these changes only affect communication between local
372 applications and syslogd(8). The format that syslogd(8) uses to
373 store messages on disk or forward messages to other systems
374 remains unchanged. syslogd(8) still uses RFC 3164 for these
375 purposes. Options to customize this behaviour will be added in the
376 future. Utilities that process log files stored in /var/log are
377 thus expected to continue to function as before.
379 __FreeBSD_version has been incremented to 1200061 to denote this
383 Support for token ring networks has been removed. If you
384 have "device token" in your kernel config you should remove
385 it. No device drivers supported token ring.
388 makefs was modified to be able to tag ISO9660 El Torito boot catalog
389 entries as EFI instead of overloading the i386 tag as done previously.
390 The amd64 mkisoimages.sh script used to build amd64 ISO images for
391 release was updated to use this. This may mean that makefs must be
392 updated before "make cdrom" can be run in the release directory. This
393 should be as simple as:
395 $ cd $SRCDIR/usr.sbin/makefs
396 $ make depend all install
399 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
400 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
401 Co-existance for the transition period will come shortly. Booting is a
402 complex environment and test coverage for Lua-enabled loaders has been
403 thin, so it would be prudent to assume it might not work and make
404 provisions for backup boot methods.
407 devmatch functionality has been turned on in devd. It will automatically
408 load drivers for unattached devices. This may cause unexpected drivers to
409 be loaded. Please report any problems to current@ and imp@freebsd.org.
412 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
413 6.0.0. Please see the 20141231 entry below for information about
414 prerequisites and upgrading, if you are not already using clang 3.5.0
418 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
419 This means it is used to link the kernel and userland libraries and
420 executables, but is not yet installed as /usr/bin/ld by default.
422 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
423 WITHOUT_LLD_BOOTSTRAP=yes
426 On i386, pmtimer has been removed. Its functionality has been folded
427 into apm. It was a no-op on ACPI in current for a while now (but was still
428 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
429 from kernel config files.
432 The use of RSS hash from the network card aka flowid has been
433 disabled by default for lagg(4) as it's currently incompatible with
434 the lacp and loadbalance protocols.
436 This can be re-enabled by setting the following in loader.conf:
437 net.link.lagg.default_use_flowid="1"
440 The SW_WATCHDOG option is no longer necessary to enable the
441 hardclock-based software watchdog if no hardware watchdog is
442 configured. As before, SW_WATCHDOG will cause the software
443 watchdog to be enabled even if a hardware watchdog is configured.
446 r326887 fixes the issue described in the 20171214 UPDATING entry.
447 r326888 flips the switch back to building GELI support always.
450 r362593 broke ZFS + GELI support for reasons unknown. However,
451 it also broke ZFS support generally, so GELI has been turned off
452 by default as the lesser evil in r326857. If you boot off ZFS and/or
453 GELI, it might not be a good time to update.
456 PowerPC users must update loader(8) by rebuilding world before
457 installing a new kernel, as the protocol connecting them has
458 changed. Without the update, loader metadata will not be passed
459 successfully to the kernel and users will have to enter their
460 root partition at the kernel mountroot prompt to continue booting.
461 Newer versions of loader can boot old kernels without issue.
464 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
465 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
466 to WITH/OUT_LOADER_GELI.
469 The naive and non-compliant support of posix_fallocate(2) in ZFS
470 has been removed as of r325320. The system call now returns EINVAL
471 when used on a ZFS file. Although the new behavior complies with the
472 standard, some consumers are not prepared to cope with it.
473 One known victim is lld prior to r325420.
476 Building in a FreeBSD src checkout will automatically create object
477 directories now rather than store files in the current directory if
478 'make obj' was not ran. Calling 'make obj' is no longer necessary.
479 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
480 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
484 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
485 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
486 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
487 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
488 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
489 The UNIFIED_OBJDIR option is a transitional feature that will be
490 removed for 12.0 release; please migrate to the new format for any
491 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
492 than hardcoding paths.
495 The native-xtools target no longer installs the files by default to the
496 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
497 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
500 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
501 options are changing from controlling the build if defined / undefined
502 to controlling the build with explicit 'yes' or 'no' values. They will
503 shift to WITH/WITHOUT options to match other options in the system.
506 libstand has turned into a private library for sys/boot use only.
507 It is no longer supported as a public interface outside of sys/boot.
510 The arm port has split armv6 into armv6 and armv7. armv7 is now
511 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
512 and are running a kernel from before r324363, you will need to add
513 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
516 When building multiple kernels using KERNCONF, non-existent KERNCONF
517 files will produce an error and buildkernel will fail. Previously
518 missing KERNCONF files silently failed giving no indication as to
519 why, only to subsequently discover during installkernel that the
520 desired kernel was never built in the first place.
523 The default serial number format for CTL LUNs has changed. This will
524 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
525 or iSCSI clients care about their LUNs' serial numbers. Users who
526 require serial number stability should hardcode serial numbers in
530 For 32-bit arm compiled for hard-float support, soft-floating point
531 binaries now always get their shared libraries from
532 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
533 /usr/libsoft also existed). Only users with a hard-float ld.so, but
534 soft-float everything else should be affected.
537 The geli password typed at boot is now hidden. To restore the previous
538 behavior, see geli(8) for configuration options.
541 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
542 sysctl values. Minor nit, but requires a rebuild of both world/kernel
546 "make check" behavior (made in ^/head@r295380) has been changed to
547 execute from a limited sandbox, as opposed to executing from
551 - The "beforecheck" and "aftercheck" targets are now specified.
552 - ${CHECKDIR} (added in commit noted above) has been removed.
553 - Legacy behavior can be enabled by setting
554 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
556 If the limited sandbox mode is enabled, "make check" will execute
557 "make distribution", then install, execute the tests, and clean up the
558 sandbox if successful.
560 The "make distribution" and "make install" targets are typically run as
561 root to set appropriate permissions and ownership at installation time.
562 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
563 environment if executing "make check" with limited sandbox mode using
564 an unprivileged user.
567 Since the switch to GPT disk labels, fsck for UFS/FFS has been
568 unable to automatically find alternate superblocks. As of r322297,
569 the information needed to find alternate superblocks has been
570 moved to the end of the area reserved for the boot block.
571 Filesystems created with a newfs of this vintage or later
572 will create the recovery information. If you have a filesystem
573 created prior to this change and wish to have a recovery block
574 created for your filesystem, you can do so by running fsck in
575 foreground mode (i.e., do not use the -p or -y options). As it
576 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
577 to which you should answer yes.
580 As of r321665, an NFSv4 server configuration that services
581 Kerberos mounts or clients that do not support the uid/gid in
582 owner/owner_group string capability, must explicitly enable
583 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
584 machine's /etc/rc.conf file.
587 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
588 Please see the 20141231 entry below for information about prerequisites
589 and upgrading, if you are not already using clang 3.5.0 or higher.
592 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
593 r-commands (rlogin, rsh, etc.) to be built with the base system.
596 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
597 a very major ABI incompatible change, so users of FreeBSD/powerpc must
598 be careful when performing source upgrades. It is best to run
599 'make installworld' from an alternate root system, either a live
600 CD/memory stick, or a temporary root partition. Additionally, all ports
601 must be recompiled. powerpc64 is largely unaffected, except in the case
602 of 32-bit compatibility. All 32-bit binaries will be affected.
605 Forward compatibility for the "ino64" project have been committed. This
606 will allow most new binaries to run on older kernels in a limited
607 fashion. This prevents many of the common foot-shooting actions in the
608 upgrade as well as the limited ability to roll back the kernel across
609 the ino64 upgrade. Complicated use cases may not work properly, though
610 enough simpler ones work to allow recovery in most situations.
613 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
614 if you require the GPL compiler.
617 The internal ABI used for communication between the NFS kernel modules
618 was changed by r320085, so __FreeBSD_version was bumped to
619 ensure all the NFS related modules are updated together.
622 The ABI of struct event was changed by extending the data
623 member to 64bit and adding ext fields. For upgrade, same
624 precautions as for the entry 20170523 "ino64" must be
628 The GNU roff toolchain has been removed from base. To render manpages
629 which are not supported by mandoc(1), man(1) can fallback on GNU roff
630 from ports (and recommends to install it).
631 To render roff(7) documents, consider using GNU roff from ports or the
632 heirloom doctools roff toolchain from ports via pkg install groff or
633 via pkg install heirloom-doctools.
636 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
637 smaller runtime footprint builds. This is useful for embedded systems
638 which only require one chipset support.
640 If you load it as a module, make sure this is in /boot/loader.conf:
644 This will load the HAL, all chip/RF backends and if_ath_pci.
645 If you have if_ath_pci in /boot/loader.conf, ensure it is after
646 if_ath or it will not load any HAL chipset support.
648 If you want to selectively load things (eg on ye cheape ARM/MIPS
649 platforms where RAM is at a premium) you should:
652 * load the chip modules in question
653 * load ath_rate, ath_dfs
655 * load if_ath_pci and/or if_ath_ahb depending upon your particular
656 bus bind type - this is where probe/attach is done.
658 For further comments/feedback, poke adrian@ .
661 The "ino64" 64-bit inode project has been committed, which extends
662 a number of types to 64 bits. Upgrading in place requires care and
663 adherence to the documented upgrade procedure.
665 If using a custom kernel configuration ensure that the
666 COMPAT_FREEBSD11 option is included (as during the upgrade the
667 system will be running the ino64 kernel with the existing world).
669 For the safest in-place upgrade begin by removing previous build
670 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
671 full procedure documented below under the heading "To rebuild
672 everything and install it on the current system." Specifically,
673 a reboot is required after installing the new kernel before
677 The NATM framework including the en(4), fatm(4), hatm(4), and
678 patm(4) devices has been removed. Consumers should plan a
679 migration before the end-of-life date for FreeBSD 11.
682 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
683 diff has not been implemented, if those are needed a newer version of
684 GNU diff is available via the diffutils package under the gdiff name.
687 As of r316810 for ipfilter, keep frags is no longer assumed when
688 keep state is specified in a rule. r316810 aligns ipfilter with
689 documentation in man pages separating keep frags from keep state.
690 This allows keep state to be specified without forcing keep frags
691 and allows keep frags to be specified independently of keep state.
692 To maintain previous behaviour, also specify keep frags with
693 keep state (as documented in ipf.conf.5).
696 arm64 builds now use the base system LLD 4.0.0 linker by default,
697 instead of requiring that the aarch64-binutils port or package be
698 installed. To continue using aarch64-binutils, set
699 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
702 The UDP optimization in entry 20160818 that added the sysctl
703 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
704 packets will no longer be treated as L3 broadcast packets.
707 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
708 use any explicitly assigned loopback address available in the jail
709 instead of using the first assigned address of the jail.
712 The ctl.ko module no longer implements the iSCSI target frontend:
713 cfiscsi.ko does instead.
715 If building cfiscsi.ko as a kernel module, the module can be loaded
716 via one of the following methods:
717 - `cfiscsi_load="YES"` in loader.conf(5).
718 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
719 - ctladm(8)/ctld(8), when compiled with iSCSI support
720 (`WITH_ISCSI=yes` in src.conf(5))
722 Please see cfiscsi(4) for more details.
725 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
726 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
727 same source (previously, the dependency of mmcsd.ko on mmc.ko was
728 missing, but mmcsd.ko now will refuse to load if it is incompatible
732 The syntax of ipfw(8) named states was changed to avoid ambiguity.
733 If you have used named states in the firewall rules, you need to modify
734 them after installworld and before rebooting. Now named states must
735 be prefixed with colon.
738 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
739 removed as the userland we provide cannot use them. The KMS version
740 (sys/dev/drm2) supports the same hardware.
743 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
744 Please see the 20141231 entry below for information about prerequisites
745 and upgrading, if you are not already using clang 3.5.0 or higher.
748 The code that provides support for ZFS .zfs/ directory functionality
749 has been reimplemented. It's not possible now to create a snapshot
750 by mkdir under .zfs/snapshot/. That should be the only user visible
754 EISA bus support has been removed. The WITH_EISA option is no longer
758 MCA bus support has been removed.
761 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
762 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
765 The EM_MULTIQUEUE kernel configuration option is deprecated now that
766 the em(4) driver conforms to iflib specifications.
769 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
770 IFLIB. If you have a custom kernel configuration that excludes em(4)
771 but you use igb(4), you need to re-add em(4) to your custom configuration.
774 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
775 Please see the 20141231 entry below for information about prerequisites
776 and upgrading, if you are not already using clang 3.5.0 or higher.
779 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
780 Please see the 20141231 entry below for information about prerequisites
781 and upgrading, if you are not already using clang 3.5.0 or higher.
784 The layout of the pmap structure has changed for powerpc to put the pmap
785 statistics at the front for all CPU variations. libkvm(3) and all tools
786 that link against it need to be recompiled.
789 isl(4) and cyapa(4) drivers now require a new driver,
790 chromebook_platform(4), to work properly on Chromebook-class hardware.
791 On other types of hardware the drivers may need to be configured using
792 device hints. Please see the corresponding manual pages for details.
795 The urtwn(4) driver was merged into rtwn(4) and now consists of
796 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
798 Also, firmware for RTL8188CE was renamed due to possible name
799 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
802 GNU rcs has been removed from base. It is available as packages:
803 - rcs: Latest GPLv3 GNU rcs version.
804 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
808 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
809 modules now requires that the kernel configuration contain the
810 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
813 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
814 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
817 Relocatable object files with the extension of .So have been renamed
818 to use an extension of .pico instead. The purpose of this change is
819 to avoid a name clash with shared libraries on case-insensitive file
820 systems. On those file systems, foo.So is the same file as foo.so.
823 GNU rcs has been turned off by default. It can (temporarily) be built
824 again by adding WITH_RCS knob in src.conf.
825 Otherwise, GNU rcs is available from packages:
826 - rcs: Latest GPLv3 GNU rcs version.
827 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
830 The backup_uses_rcs functionality has been removed from rc.subr.
833 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
834 two separate components, QUEUE_MACRO_DEBUG_TRACE and
835 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
836 QUEUE_MACRO_DEBUG behavior.
839 r304787 changed some ioctl interfaces between the iSCSI userspace
840 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
841 rebuilt to work with new kernels. __FreeBSD_version has been bumped
845 The UDP receive code has been updated to only treat incoming UDP
846 packets that were addressed to an L2 broadcast address as L3
847 broadcast packets. It is not expected that this will affect any
848 standards-conforming UDP application. The new behaviour can be
849 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
853 Remove the openbsd_poll system call.
854 __FreeBSD_version has been bumped because of this.
857 The stable/11 branch has been created from head@r302406.
860 The libc stub for the pipe(2) system call has been replaced with
861 a wrapper that calls the pipe2(2) system call and the pipe(2)
862 system call is now only implemented by the kernels that include
863 "options COMPAT_FREEBSD10" in their config file (this is the
864 default). Users should ensure that this option is enabled in
865 their kernel or upgrade userspace to r302092 before upgrading their
869 CAM will now strip leading spaces from SCSI disks' serial numbers.
870 This will affect users who create UFS filesystems on SCSI disks using
871 those disk's diskid device nodes. For example, if /etc/fstab
872 previously contained a line like
873 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
874 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
875 transforms like gmirror may also be affected. ZFS users should
879 The bitstring(3) API has been updated with new functionality and
880 improved performance. But it is binary-incompatible with the old API.
881 Objects built with the new headers may not be linked against objects
882 built with the old headers.
885 The brk and sbrk functions have been removed from libc on arm64.
886 Binutils from ports has been updated to not link to these
887 functions and should be updated to the latest version before
888 installing a new libc.
891 The armv6 port now defaults to hard float ABI. Limited support
892 for running both hardfloat and soft float on the same system
893 is available using the libraries installed with -DWITH_LIBSOFT.
894 This has only been tested as an upgrade path for installworld
895 and packages may fail or need manual intervention to run. New
896 packages will be needed.
898 To update an existing self-hosted armv6hf system, you must add
899 TARGET_ARCH=armv6 on the make command line for both the build
900 and the install steps.
903 Kernel modules compiled outside of a kernel build now default to
904 installing to /boot/modules instead of /boot/kernel. Many kernel
905 modules built this way (such as those in ports) already overrode
906 KMODDIR explicitly to install into /boot/modules. However,
907 manually building and installing a module from /sys/modules will
908 now install to /boot/modules instead of /boot/kernel.
911 The CAM I/O scheduler has been committed to the kernel. There should be
912 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
913 list of known rogues that claim support for this but actually corrupt
914 data is believed to be complete, be on the lookout for data
915 corruption. The known rogue list is believed to be complete:
917 o Crucial MX100, M550 drives with MU01 firmware.
918 o Micron M510 and M550 drives with MU01 firmware.
919 o Micron M500 prior to MU07 firmware
920 o Samsung 830, 840, and 850 all firmwares
921 o FCCT M500 all firmwares
923 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
924 with working NCQ TRIM. For Micron branded drives, see your sales rep for
925 updated firmware. Black listed drives will work correctly because these
926 drives work correctly so long as no NCQ TRIMs are sent to them. Given
927 this list is the same as found in Linux, it's believed there are no
928 other rogues in the market place. All other models from the above
931 To be safe, if you are at all concerned, you can quirk each of your
932 drives to prevent NCQ from being sent by setting:
933 kern.cam.ada.X.quirks="0x2"
934 in loader.conf. If the drive requires the 4k sector quirk, set the
938 The FAST_DEPEND build option has been removed and its functionality is
939 now the one true way. The old mkdep(1) style of 'make depend' has
940 been removed. See 20160311 for further details.
943 Resource range types have grown from unsigned long to uintmax_t. All
944 drivers, and anything using libdevinfo, need to be recompiled.
947 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
948 builds. It no longer runs mkdep(1) during 'make depend', and the
949 'make depend' stage can safely be skipped now as it is auto ran
950 when building 'make all' and will generate all SRCS and DPSRCS before
951 building anything else. Dependencies are gathered at compile time with
952 -MF flags kept in separate .depend files per object file. Users should
953 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
957 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
958 kernel modules. Therefore, if you load any kernel modules at boot time,
959 please install the boot loaders after you install the kernel, but before
963 make buildkernel KERNCONF=YOUR_KERNEL_HERE
964 make installkernel KERNCONF=YOUR_KERNEL_HERE
965 make -C sys/boot install
966 <reboot in single user>
968 Then follow the usual steps, described in the General Notes section,
972 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
973 see the 20141231 entry below for information about prerequisites and
974 upgrading, if you are not already using clang 3.5.0 or higher.
977 The AIO subsystem is now a standard part of the kernel. The
978 VFS_AIO kernel option and aio.ko kernel module have been removed.
979 Due to stability concerns, asynchronous I/O requests are only
980 permitted on sockets and raw disks by default. To enable
981 asynchronous I/O requests on all file types, set the
982 vfs.aio.enable_unsafe sysctl to a non-zero value.
985 The ELF object manipulation tool objcopy is now provided by the
986 ELF Tool Chain project rather than by GNU binutils. It should be a
987 drop-in replacement, with the addition of arm64 support. The
988 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
989 to obtain the GNU version if necessary.
992 Building ZFS pools on top of zvols is prohibited by default. That
993 feature has never worked safely; it's always been prone to deadlocks.
994 Using a zvol as the backing store for a VM guest's virtual disk will
995 still work, even if the guest is using ZFS. Legacy behavior can be
996 restored by setting vfs.zfs.vol.recursive=1.
999 The NONE and HPN patches has been removed from OpenSSH. They are
1000 still available in the security/openssh-portable port.
1003 With the addition of ypldap(8), a new _ypldap user is now required
1004 during installworld. "mergemaster -p" can be used to add the user
1005 prior to installworld, as documented in the handbook.
1008 The tftp loader (pxeboot) now uses the option root-path directive. As a
1009 consequence it no longer looks for a pxeboot.4th file on the tftp
1010 server. Instead it uses the regular /boot infrastructure as with the
1014 The code to start recording plug and play data into the modules has
1015 been committed. While the old tools will properly build a new kernel,
1016 a number of warnings about "unknown metadata record 4" will be produced
1017 for an older kldxref. To avoid such warnings, make sure to rebuild
1018 the kernel toolchain (or world). Make sure that you have r292078 or
1019 later when trying to build 292077 or later before rebuilding.
1022 Debug data files are now built by default with 'make buildworld' and
1023 installed with 'make installworld'. This facilitates debugging but
1024 requires more disk space both during the build and for the installed
1025 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1029 r291527 changed the internal interface between the nfsd.ko and
1030 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1031 __FreeBSD_version has been bumped because of this.
1034 Add support for unicode collation strings leads to a change of
1035 order of files listed by ls(1) for example. To get back to the old
1036 behaviour, set LC_COLLATE environment variable to "C".
1038 Databases administrators will need to reindex their databases given
1039 collation results will be different.
1041 Due to a bug in install(1) it is recommended to remove the ancient
1042 locales before running make installworld.
1044 rm -rf /usr/share/locale/*
1047 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1048 libcrypto.so.7 or libssl.so.7 must be recompiled.
1051 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1052 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1053 should be replaced with isp_2400 and isp_2500 modules respectively.
1056 The build previously allowed using 'make -n' to not recurse into
1057 sub-directories while showing what commands would be executed, and
1058 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1059 and 'make -N' will not.
1062 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1063 and etcupdate will now use this file. A custom sendmail.cf is now
1064 updated via this mechanism rather than via installworld. If you had
1065 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1066 want to remove the exclusion or change it to "always install".
1067 /etc/mail/sendmail.cf is now managed the same way regardless of
1068 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1069 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1072 Compatibility shims for legacy ATA device names have been removed.
1073 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1074 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1075 environment variables, /dev/ad* and /dev/ar* symbolic links.
1078 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1079 Please see the 20141231 entry below for information about prerequisites
1080 and upgrading, if you are not already using clang 3.5.0 or higher.
1083 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1084 and renamed from .symbols to .debug. This reduces the size requirements
1085 on the boot partition or file system and provides consistency with
1086 userland debug files.
1088 When using the supported kernel installation method the
1089 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1090 as is done with /boot/kernel.
1092 Developers wishing to maintain the historical behavior of installing
1093 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1096 The wireless drivers had undergone changes that remove the 'parent
1097 interface' from the ifconfig -l output. The rc.d network scripts
1098 used to check presence of a parent interface in the list, so old
1099 scripts would fail to start wireless networking. Thus, etcupdate(3)
1100 or mergemaster(8) run is required after kernel update, to update your
1101 rc.d scripts in /etc.
1104 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1105 These configurations are now automatically interpreted as
1106 'scrub fragment reassemble'.
1109 Kernel-loadable modules for the random(4) device are back. To use
1110 them, the kernel must have
1113 options RANDOM_LOADABLE
1115 kldload(8) can then be used to load random_fortuna.ko
1116 or random_yarrow.ko. Please note that due to the indirect
1117 function calls that the loadable modules need to provide,
1118 the build-in variants will be slightly more efficient.
1120 The random(4) kernel option RANDOM_DUMMY has been retired due to
1121 unpopularity. It was not all that useful anyway.
1124 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1125 Control over building the ELF Tool Chain tools is now provided by
1126 the WITHOUT_TOOLCHAIN knob.
1129 The polarity of Pulse Per Second (PPS) capture events with the
1130 uart(4) driver has been corrected. Prior to this change the PPS
1131 "assert" event corresponded to the trailing edge of a positive PPS
1132 pulse and the "clear" event was the leading edge of the next pulse.
1134 As the width of a PPS pulse in a typical GPS receiver is on the
1135 order of 1 millisecond, most users will not notice any significant
1136 difference with this change.
1138 Anyone who has compensated for the historical polarity reversal by
1139 configuring a negative offset equal to the pulse width will need to
1140 remove that workaround.
1143 The default group assigned to /dev/dri entries has been changed
1144 from 'wheel' to 'video' with the id of '44'. If you want to have
1145 access to the dri devices please add yourself to the video group
1148 # pw groupmod video -m $USER
1151 The menu.rc and loader.rc files will now be replaced during
1152 upgrades. Please migrate local changes to menu.rc.local and
1153 loader.rc.local instead.
1156 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1157 strings and strip have been removed. The src.conf(5) knob
1158 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1161 As ZFS requires more kernel stack pages than is the default on some
1162 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1163 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1165 Please consider using 'options KSTACK_PAGES=X' where X is greater
1166 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1169 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1170 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1171 default, i.e., they will not contain "::". For example, instead
1172 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1173 to have a more specific match, such as different map entries for
1174 IPv6:0:0 vs IPv6:0. This change requires that configuration
1175 data (including maps, files, classes, custom ruleset, etc.) must
1176 use the same format, so make certain such configuration data is
1177 upgrading. As a very simple check search for patterns like
1178 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1179 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1180 the cf option UseCompressedIPv6Addresses.
1183 The default kernel entropy-processing algorithm is now
1184 Fortuna, replacing Yarrow.
1186 Assuming you have 'device random' in your kernel config
1187 file, the configurations allow a kernel option to override
1188 this default. You may choose *ONE* of:
1190 options RANDOM_YARROW # Legacy /dev/random algorithm.
1191 options RANDOM_DUMMY # Blocking-only driver.
1193 If you have neither, you get Fortuna. For most people,
1194 read no further, Fortuna will give a /dev/random that works
1195 like it always used to, and the difference will be irrelevant.
1197 If you remove 'device random', you get *NO* kernel-processed
1198 entropy at all. This may be acceptable to folks building
1199 embedded systems, but has complications. Carry on reading,
1200 and it is assumed you know what you need.
1202 *PLEASE* read random(4) and random(9) if you are in the
1203 habit of tweaking kernel configs, and/or if you are a member
1204 of the embedded community, wanting specific and not-usual
1205 behaviour from your security subsystems.
1207 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1208 random', you will NOT have a functioning /dev/random, and
1209 many cryptographic features will not work, including SSH.
1210 You may also find strange behaviour from the random(3) set
1211 of library functions, in particular sranddev(3), srandomdev(3)
1212 and arc4random(3). The reason for this is that the KERN_ARND
1213 sysctl only returns entropy if it thinks it has some to
1214 share, and with RANDOM_DUMMY or no 'device random' this
1218 An additional fix for the issue described in the 20150614 sendmail
1219 entry below has been committed in revision 284717.
1222 FreeBSD's old make (fmake) has been removed from the system. It is
1223 available as the devel/fmake port or via pkg install fmake.
1226 The fix for the issue described in the 20150614 sendmail entry
1227 below has been committed in revision 284436. The work
1228 around described in that entry is no longer needed unless the
1229 default setting is overridden by a confDH_PARAMETERS configuration
1230 setting of '5' or pointing to a 512 bit DH parameter file.
1233 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1234 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1235 and devel/kyua to version 0.20+ and adjust any calling code to work
1236 with Kyuafile and kyua.
1239 The import of openssl to address the FreeBSD-SA-15:10.openssl
1240 security advisory includes a change which rejects handshakes
1241 with DH parameters below 768 bits. sendmail releases prior
1242 to 8.15.2 (not yet released), defaulted to a 512 bit
1243 DH parameter setting for client connections. To work around
1244 this interoperability, sendmail can be configured to use a
1245 2048 bit DH parameter by:
1247 1. Edit /etc/mail/`hostname`.mc
1248 2. If a setting for confDH_PARAMETERS does not exist or
1249 exists and is set to a string beginning with '5',
1250 replace it with '2'.
1251 3. If a setting for confDH_PARAMETERS exists and is set to
1252 a file path, create a new file with:
1253 openssl dhparam -out /path/to/file 2048
1254 4. Rebuild the .cf file:
1255 cd /etc/mail/; make; make install
1256 5. Restart sendmail:
1257 cd /etc/mail/; make restart
1259 A sendmail patch is coming, at which time this file will be
1263 Generation of legacy formatted entries have been disabled by default
1264 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1265 entries were converted to use the new format by default when the new,
1266 machine independent format have been added and supported since FreeBSD
1269 Please see the pwd_mkdb(8) manual page for further details.
1272 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1273 20141231 entry below for information about prerequisites and upgrading,
1274 if you are not already using 3.5.0 or higher.
1277 TI platform code switched to using vendor DTS files and this update
1278 may break existing systems running on Beaglebone, Beaglebone Black,
1281 - dtb files should be regenerated/reinstalled. Filenames are the
1282 same but content is different now
1283 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1284 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1285 addressing scheme is now pin 25 on /dev/gpioc3.
1286 - Pandaboard: /etc/ttys should be updated, serial console device is
1287 now /dev/ttyu2, not /dev/ttyu0
1290 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1291 If you need the GNU extension from groff soelim(1), install groff
1292 from package: pkg install groff, or via ports: textproc/groff.
1295 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1296 defined in symlink(7); previously symlinks were silently ignored.
1299 The const qualifier has been removed from iconv(3) to comply with
1300 POSIX. The ports tree is aware of this from r384038 onwards.
1303 Libraries specified by LIBADD in Makefiles must have a corresponding
1304 DPADD_<lib> variable to ensure correct dependencies. This is now
1305 enforced in src.libnames.mk.
1308 From legacy ata(4) driver was removed support for SATA controllers
1309 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1310 Kernel modules ataahci and ataadaptec were removed completely,
1311 replaced by ahci and mvs modules respectively.
1314 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1315 the 20141231 entry below for information about prerequisites and
1316 upgrading, if you are not already using 3.5.0 or higher.
1319 The 32-bit PowerPC kernel has been changed to a position-independent
1320 executable. This can only be booted with a version of loader(8)
1321 newer than January 31, 2015, so make sure to update both world and
1322 kernel before rebooting.
1325 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1326 but before r278950, the RNG was not seeded properly. Immediately
1327 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1328 ssh keys or openssl keys) that were generated w/ a kernel from that
1329 range. This does not affect programs that directly used /dev/random
1330 or /dev/urandom. All userland uses of arc4random(3) are affected.
1333 The autofs(4) ABI was changed in order to restore binary compatibility
1334 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1335 with the new kernel.
1338 The powerpc64 kernel has been changed to a position-independent
1339 executable. This can only be booted with a new version of loader(8),
1340 so make sure to update both world and kernel before rebooting.
1343 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1344 only release, no new features have been added. Please see the 20141231
1345 entry below for information about prerequisites and upgrading, if you
1346 are not already using 3.5.0.
1349 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1350 taken from the ELF Tool Chain project rather than GNU binutils. They
1351 should be drop-in replacements, with the addition of arm64 support.
1352 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1353 binutils tools, if necessary. See 20150805 for updated information.
1356 The default Unbound configuration now enables remote control
1357 using a local socket. Users who have already enabled the
1358 local_unbound service should regenerate their configuration
1359 by running "service local_unbound setup" as root.
1362 The GNU texinfo and GNU info pages have been removed.
1363 To be able to view GNU info pages please install texinfo from ports.
1366 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1368 As of this release, a prerequisite for building clang, llvm and lldb is
1369 a C++11 capable compiler and C++11 standard library. This means that to
1370 be able to successfully build the cross-tools stage of buildworld, with
1371 clang as the bootstrap compiler, your system compiler or cross compiler
1372 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1373 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1376 On any standard FreeBSD 10.x or 11.x installation, where clang and
1377 libc++ are on by default (that is, on x86 or arm), this should work out
1380 On 9.x installations where clang is enabled by default, e.g. on x86 and
1381 powerpc, libc++ will not be enabled by default, so libc++ should be
1382 built (with clang) and installed first. If both clang and libc++ are
1383 missing, build clang first, then use it to build libc++.
1385 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1386 the instructions for 9.x above.
1388 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1389 default, and do not build clang.
1391 Many embedded systems are resource constrained, and will not be able to
1392 build clang in a reasonable time, or in some cases at all. In those
1393 cases, cross building bootable systems on amd64 is a workaround.
1395 This new version of clang introduces a number of new warnings, of which
1396 the following are most likely to appear:
1400 This warns in two cases, for both C and C++:
1401 * When the code is trying to take the absolute value of an unsigned
1402 quantity, which is effectively a no-op, and almost never what was
1403 intended. The code should be fixed, if at all possible. If you are
1404 sure that the unsigned quantity can be safely cast to signed, without
1405 loss of information or undefined behavior, you can add an explicit
1406 cast, or disable the warning.
1408 * When the code is trying to take an absolute value, but the called
1409 abs() variant is for the wrong type, which can lead to truncation.
1410 If you want to disable the warning instead of fixing the code, please
1411 make sure that truncation will not occur, or it might lead to unwanted
1414 -Wtautological-undefined-compare and
1415 -Wundefined-bool-conversion
1417 These warn when C++ code is trying to compare 'this' against NULL, while
1418 'this' should never be NULL in well-defined C++ code. However, there is
1419 some legacy (pre C++11) code out there, which actively abuses this
1420 feature, which was less strictly defined in previous C++ versions.
1422 Squid and openjdk do this, for example. The warning can be turned off
1423 for C++98 and earlier, but compiling the code in C++11 mode might result
1424 in unexpected behavior; for example, the parts of the program that are
1425 unreachable could be optimized away.
1428 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1429 kernel sources have been removed. The .h files remain, since some
1430 utilities include them. This will need to be fixed later.
1431 If "mount -t oldnfs ..." is attempted, it will fail.
1432 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1433 the utilities will report errors.
1436 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1437 directories to top level SUBDIR variable when their parent
1438 directory is included in LOCAL_DIRS. Users with build systems with
1439 such hierarchies and without SUBDIR entries in the parent
1440 directory Makefiles should add them or add the directories to
1444 faith(4) and faithd(8) have been removed from the base system. Faith
1445 has been obsolete for a very long time.
1448 vt(4), the new console driver, is enabled by default. It brings
1449 support for Unicode and double-width characters, as well as
1450 support for UEFI and integration with the KMS kernel video
1453 You may need to update your console settings in /etc/rc.conf,
1454 most probably the keymap. During boot, /etc/rc.d/syscons will
1455 indicate what you need to do.
1457 vt(4) still has issues and lacks some features compared to
1458 syscons(4). See the wiki for up-to-date information:
1459 https://wiki.freebsd.org/Newcons
1461 If you want to keep using syscons(4), you can do so by adding
1462 the following line to /boot/loader.conf:
1466 pjdfstest has been integrated into kyua as an opt-in test suite.
1467 Please see share/doc/pjdfstest/README for more details on how to
1471 gperf has been removed from the base system for architectures
1472 that use clang. Ports that require gperf will obtain it from the
1476 pjdfstest has been moved from tools/regression/pjdfstest to
1480 At svn r271982, The default linux compat kernel ABI has been adjusted
1481 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1482 update. If you wish to continue using the linux-f10 compat ports,
1483 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1484 encouraged to update their linux-compat packages to linux-c6 during
1485 their next update cycle.
1488 The ofwfb driver, used to provide a graphics console on PowerPC when
1489 using vt(4), no longer allows mmap() of all physical memory. This
1490 will prevent Xorg on PowerPC with some ATI graphics cards from
1491 initializing properly unless x11-servers/xorg-server is updated to
1495 The xdev targets have been converted to using TARGET and
1496 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1499 The default unbound configuration has been modified to address
1500 issues with reverse lookups on networks that use private
1501 address ranges. If you use the local_unbound service, run
1502 "service local_unbound setup" as root to regenerate your
1503 configuration, then "service local_unbound reload" to load the
1507 The GNU texinfo and GNU info pages are not built and installed
1508 anymore, WITH_INFO knob has been added to allow to built and install
1510 UPDATE: see 20150102 entry on texinfo's removal
1513 The GNU readline library is now an INTERNALLIB - that is, it is
1514 statically linked into consumers (GDB and variants) in the base
1515 system, and the shared library is no longer installed. The
1516 devel/readline port is available for third party software that
1520 The Itanium architecture (ia64) has been removed from the list of
1521 known architectures. This is the first step in the removal of the
1525 Commit r268115 has added NFSv4.1 server support, merged from
1526 projects/nfsv4.1-server. Since this includes changes to the
1527 internal interfaces between the NFS related modules, a full
1528 build of the kernel and modules will be necessary.
1529 __FreeBSD_version has been bumped.
1532 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1533 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1534 which differs from the behaviour controlled by this knob.)
1537 Maximal length of the serial number in CTL was increased from 16 to
1538 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1539 and ctld, need to be rebuilt to work with a new kernel.
1542 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1543 1 respectively to match the upstream numbers. They were out of
1544 sync because, when they were originally added to FreeBSD, the
1545 upstream versions were not respected. These libraries are private
1546 and not yet built by default, so renumbering them should be a
1547 non-issue. However, unclean source trees will yield broken test
1548 programs once the operator executes "make delete-old-libs" after a
1549 "make installworld".
1551 Additionally, the atf-sh binary was made private by moving it into
1552 /usr/libexec/. Already-built shell test programs will keep the
1553 path to the old binary so they will break after "make delete-old"
1556 If you are using WITH_TESTS=yes (not the default), wipe the object
1557 tree and rebuild from scratch to prevent spurious test failures.
1558 This is only needed once: the misnumbered libraries and misplaced
1559 binaries have been added to OptionalObsoleteFiles.inc so they will
1560 be removed during a clean upgrade.
1563 Clang and llvm have been upgraded to 3.4.1 release.
1566 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1567 be removed to avoid issues in the future (and has been added to
1571 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1572 past, it affected all builds that used the bsd.*.mk files. The old
1573 behavior was a bug, but people may have relied upon it. To get this
1574 behavior back, you can .include /etc/src.conf from /etc/make.conf
1575 (which is still global and isn't changed). This also changes the
1576 behavior of incremental builds inside the tree of individual
1577 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1578 Although this has survived make universe and some upgrade scenarios,
1579 other upgrade scenarios may have broken. At least one form of
1580 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1581 as well... In cases where MAKESYSPATH isn't working with this
1582 setting, you'll need to set it to the full path to your tree.
1584 One side effect of all this cleaning up is that bsd.compiler.mk
1585 is no longer implicitly included by bsd.own.mk. If you wish to
1586 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1590 The lindev device has been removed since /dev/full has been made a
1591 standard device. __FreeBSD_version has been bumped.
1594 The knob WITHOUT_VI was added to the base system, which controls
1595 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1596 in order to reorder files share/termcap and didn't build ex(1) as a
1597 build tool, so building/installing with WITH_VI is highly advised for
1598 build hosts for older releases.
1600 This issue has been fixed in stable/9 and stable/10 in r277022 and
1601 r276991, respectively.
1604 The YES_HESIOD knob has been removed. It has been obsolete for
1605 a decade. Please move to using WITH_HESIOD instead or your builds
1606 will silently lack HESIOD.
1609 The uart(4) driver has been changed with respect to its handling
1610 of the low-level console. Previously the uart(4) driver prevented
1611 any process from changing the baudrate or the CLOCAL and HUPCL
1612 control flags. By removing the restrictions, operators can make
1613 changes to the serial console port without having to reboot.
1614 However, when getty(8) is started on the serial device that is
1615 associated with the low-level console, a misconfigured terminal
1616 line in /etc/ttys will now have a real impact.
1617 Before upgrading the kernel, make sure that /etc/ttys has the
1618 serial console device configured as 3wire without baudrate to
1619 preserve the previous behaviour. E.g:
1620 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1623 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1624 to improve performance. To re-enable it, if needed, run rpcbind
1625 with command line option -W.
1628 Switched back to the GPL dtc compiler due to updates in the upstream
1629 dts files not being supported by the BSDL dtc compiler. You will need
1630 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1631 may result while building dtb files during a kernel build if you fail
1632 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1635 Clang and llvm have been upgraded to 3.4 release.
1638 The nve(4) driver has been removed. Please use the nfe(4) driver
1639 for NVIDIA nForce MCP Ethernet adapters instead.
1642 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1643 This could cause certain C++ applications using shared libraries built
1644 against the previous version of libc++ to crash. The incompatibility
1645 has now been fixed, but any C++ applications or shared libraries built
1646 between r261283 and r261801 should be recompiled.
1649 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1650 capability mode support. Please note that enabling the feature in
1651 kernel is still highly recommended.
1654 OpenSSH is now built with sandbox support, and will use sandbox as
1655 the default privilege separation method. This requires Capsicum
1656 capability mode support in kernel.
1659 The libelf and libdwarf libraries have been updated to newer
1660 versions from upstream. Shared library version numbers for
1661 these two libraries were bumped. Any ports or binaries
1662 requiring these two libraries should be recompiled.
1663 __FreeBSD_version is bumped to 1100006.
1666 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1667 instead of providing an explicit one, this would prevent such
1668 Makefile from providing its own Kyuafile in the future during
1669 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1670 intervention is needed to clean an objdir if you use NO_CLEAN:
1671 # find /usr/obj -name Kyuafile | xargs rm -f
1674 The behavior of gss_pseudo_random() for the krb5 mechanism
1675 has changed, for applications requesting a longer random string
1676 than produced by the underlying enctype's pseudo-random() function.
1677 In particular, the random string produced from a session key of
1678 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1679 be different at the 17th octet and later, after this change.
1680 The counter used in the PRF+ construction is now encoded as a
1681 big-endian integer in accordance with RFC 4402.
1682 __FreeBSD_version is bumped to 1100004.
1685 The WITHOUT_ATF build knob has been removed and its functionality
1686 has been subsumed into the more generic WITHOUT_TESTS. If you were
1687 using the former to disable the build of the ATF libraries, you
1688 should change your settings to use the latter.
1691 The default version of mtree is nmtree which is obtained from
1692 NetBSD. The output is generally the same, but may vary
1693 slightly. If you found you need identical output adding
1694 "-F freebsd9" to the command line should do the trick. For the
1695 time being, the old mtree is available as fmtree.
1698 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1699 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1700 1.1.4_8 and verify bsdyml not linked in, before running "make
1702 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1704 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1707 The stable/10 branch has been created in subversion from head
1714 Avoid using make -j when upgrading. While generally safe, there are
1715 sometimes problems using -j to upgrade. If your upgrade fails with
1716 -j, please try again without -j. From time to time in the past there
1717 have been problems using -j with buildworld and/or installworld. This
1718 is especially true when upgrading between "distant" versions (eg one
1719 that cross a major release boundary or several minor releases, or when
1720 several months have passed on the -current branch).
1722 Sometimes, obscure build problems are the result of environment
1723 poisoning. This can happen because the make utility reads its
1724 environment when searching for values for global variables. To run
1725 your build attempts in an "environmental clean room", prefix all make
1726 commands with 'env -i '. See the env(1) manual page for more details.
1728 When upgrading from one major version to another it is generally best to
1729 upgrade to the latest code in the currently installed branch first, then
1730 do an upgrade to the new branch. This is the best-tested upgrade path,
1731 and has the highest probability of being successful. Please try this
1732 approach if you encounter problems with a major version upgrade. Since
1733 the stable 4.x branch point, one has generally been able to upgrade from
1734 anywhere in the most recent stable branch to head / current (or even the
1735 last couple of stable branches). See the top of this file when there's
1738 When upgrading a live system, having a root shell around before
1739 installing anything can help undo problems. Not having a root shell
1740 around can lead to problems if pam has changed too much from your
1741 starting point to allow continued authentication after the upgrade.
1743 This file should be read as a log of events. When a later event changes
1744 information of a prior event, the prior event should not be deleted.
1745 Instead, a pointer to the entry with the new information should be
1746 placed in the old entry. Readers of this file should also sanity check
1747 older entries before relying on them blindly. Authors of new entries
1748 should write them with this in mind.
1752 When upgrading the boot ZFS pool to a new version, always follow
1755 1.) recompile and reinstall the ZFS boot loader and boot block
1756 (this is part of "make buildworld" and "make installworld")
1758 2.) update the ZFS boot block on your boot drive
1760 The following example updates the ZFS boot block on the first
1761 partition (freebsd-boot) of a GPT partitioned drive ada0:
1762 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1764 Non-boot pools do not need these updates.
1768 If you are updating from a prior version of FreeBSD (even one just
1769 a few days old), you should follow this procedure. It is the most
1770 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1772 make kernel-toolchain
1773 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1774 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1776 To test a kernel once
1777 ---------------------
1778 If you just want to boot a kernel once (because you are not sure
1779 if it works, or if you want to boot a known bad kernel to provide
1780 debugging information) run
1781 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1782 nextboot -k testkernel
1784 To rebuild everything and install it on the current system.
1785 -----------------------------------------------------------
1786 # Note: sometimes if you are running current you gotta do more than
1787 # is listed here if you are upgrading from a really old current.
1789 <make sure you have good level 0 dumps>
1791 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1792 make installkernel KERNCONF=YOUR_KERNEL_HERE
1794 <reboot in single user> [3]
1801 To cross-install current onto a separate partition
1802 --------------------------------------------------
1803 # In this approach we use a separate partition to hold
1804 # current's root, 'usr', and 'var' directories. A partition
1805 # holding "/", "/usr" and "/var" should be about 2GB in
1808 <make sure you have good level 0 dumps>
1811 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1812 <maybe newfs current's root partition>
1813 <mount current's root partition on directory ${CURRENT_ROOT}>
1814 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1815 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1816 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1817 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1818 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1819 <reboot into current>
1820 <do a "native" rebuild/install as described in the previous section>
1821 <maybe install compatibility libraries from ports/misc/compat*>
1825 To upgrade in-place from stable to current
1826 ----------------------------------------------
1827 <make sure you have good level 0 dumps>
1829 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1830 make installkernel KERNCONF=YOUR_KERNEL_HERE
1832 <reboot in single user> [3]
1839 Make sure that you've read the UPDATING file to understand the
1840 tweaks to various things you need. At this point in the life
1841 cycle of current, things change often and you are on your own
1842 to cope. The defaults can also change, so please read ALL of
1843 the UPDATING entries.
1845 Also, if you are tracking -current, you must be subscribed to
1846 freebsd-current@freebsd.org. Make sure that before you update
1847 your sources that you have read and understood all the recent
1848 messages there. If in doubt, please track -stable which has
1849 much fewer pitfalls.
1851 [1] If you have third party modules, such as vmware, you
1852 should disable them at this point so they don't crash your
1855 [3] From the bootblocks, boot -s, and then do
1860 adjkerntz -i # if CMOS is wall time
1861 Also, when doing a major release upgrade, it is required that
1862 you boot into single user mode to do the installworld.
1864 [4] Note: This step is non-optional. Failure to do this step
1865 can result in a significant reduction in the functionality of the
1866 system. Attempting to do it by hand is not recommended and those
1867 that pursue this avenue should read this file carefully, as well
1868 as the archives of freebsd-current and freebsd-hackers mailing lists
1869 for potential gotchas. The -U option is also useful to consider.
1870 See mergemaster(8) for more information.
1872 [5] Usually this step is a no-op. However, from time to time
1873 you may need to do this if you get unknown user in the following
1874 step. It never hurts to do it all the time. You may need to
1875 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1876 install) after the buildworld before this step if you last updated
1877 from current before 20130425 or from -stable before 20130430.
1879 [6] This only deletes old files and directories. Old libraries
1880 can be deleted by "make delete-old-libs", but you have to make
1881 sure that no program is using those libraries anymore.
1883 [8] In order to have a kernel that can run the 4.x binaries needed to
1884 do an installworld, you must include the COMPAT_FREEBSD4 option in
1885 your kernel. Failure to do so may leave you with a system that is
1886 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1887 required to run the 5.x binaries on more recent kernels. And so on
1888 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1890 Make sure that you merge any new devices from GENERIC since the
1891 last time you updated your kernel config file.
1893 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1894 "?=" instead of the "=" assignment operator, so that buildworld can
1895 override the CPUTYPE if it needs to.
1897 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1898 not on the command line, or in /etc/make.conf. buildworld will
1899 warn if it is improperly defined.
1902 This file contains a list, in reverse chronological order, of major
1903 breakages in tracking -current. It is not guaranteed to be a complete
1904 list of such breakages, and only contains entries since September 23, 2011.
1905 If you need to see UPDATING entries from before that date, you will need
1906 to fetch an UPDATING file from an older FreeBSD release.
1908 Copyright information:
1910 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1912 Redistribution, publication, translation and use, with or without
1913 modification, in full or in part, in any form or format of this
1914 document are permitted without further permission from the author.
1916 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1917 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1918 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1919 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1920 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1921 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1922 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1923 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1924 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1925 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1926 POSSIBILITY OF SUCH DAMAGE.
1928 Contact Warner Losh if you have any questions about your use of