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 12.x IS SLOW:
20 FreeBSD 12.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 Reproducible build mode is now on by default, in preparation for
36 FreeBSD 12.0. This eliminates build metadata such as the user,
37 host, and time from the kernel (and uname), unless the working tree
38 corresponds to a modified checkout from a version control system.
39 The previous behavior can be obtained by setting the /etc/src.conf
40 knob WITHOUT_REPRODUCIBLE_BUILD.
43 The Yarrow CSPRNG has been removed from the kernel as it has not been
44 supported by its designers since at least 2003. Fortuna has been the
45 default since FreeBSD-11.
48 devctl freeze/thaw have gone into the tree, the rc scripts have been
49 updated to use them and devmatch has been changed. You should update
50 kernel, userland and rc scripts all at the same time.
53 The default interpreter has been switched from 4th to Lua.
54 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
55 interpreter. If you have custom FORTH code you will need to set
56 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
57 src.conf for the build. This will create default hard links between
58 loader and loader_4th instead of loader and loader_lua, the new default.
59 If you are using UEFI it will create the proper hard link to loader.efi.
61 bhyve uses userboot.so. It remains 4th-only until some issues are solved
62 regarding coexisting with multiple versions of FreeBSD are resolved.
65 ls(1) now respects the COLORTERM environment variable used in other
66 systems and software to indicate that a colored terminal is both
67 supported and desired. If ls(1) is suddenly emitting colors, they may
68 be disabled again by either removing the unwanted COLORTERM from your
69 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
70 may not be observed in a future release.
73 The default pager for most commands has been changed to "less". To
74 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
78 The jedec_ts(4) driver has been removed. A superset of its functionality
79 is available in the jedec_dimm(4) driver, and the manpage for that
80 driver includes migration instructions. If you have "device jedec_ts"
81 in your kernel configuration file, it must be removed.
84 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
85 This should have no effect if the kernel is booted via BIOS/legacy boot.
86 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
87 has a buggy firmware that prevents a successful boot due to use of
91 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
92 support has been removed from the tree. These ports were
93 obsolete and/or known to be broken for many years.
96 loader.efi has been augmented to participate more fully in the
97 UEFI boot manager protocol. loader.efi will now look at the
98 BootXXXX environment variable to determine if a specific kernel
99 or root partition was specified. XXXX is derived from BootCurrent.
100 efibootmgr(8) manages these standard UEFI variables.
103 zfsloader's functionality has now been folded into loader.
104 zfsloader is no longer necessary once you've updated your
105 boot blocks. For a transition period, we will install a
106 hardlink for zfsloader to loader to allow a smooth transition
107 until the boot blocks can be updated (hard link because old
108 zfs boot blocks don't understand symlinks).
111 ARM64 now have efifb support, if you want to have serial console
112 on your arm64 board when an screen is connected and the bootloader
113 setup a frambuffer for us to use, just add :
117 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
118 an screen connected as the firmware will setup a framebuffer are that
119 u-boot will expose as an EFI framebuffer.
122 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
123 or take steps to update /etc/passwd before doing installworld on
124 existing systems. Do not skip the "mergemaster -Fp" step before
125 installworld, as described in the update procedures near the bottom
126 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
127 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
128 the ntp config file contain options that change file/dir locations.
129 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
130 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
131 taking steps to ensure that all required files/dirs are accessible
135 Big endian arm support has been removed.
138 The static environment setup in kernel configs is no longer mutually
139 exclusive with the loader(8) environment by default. In order to
140 restore the previous default behavior of disabling the loader(8)
141 environment if a static environment is present, you must specify
142 loader_env.disabled=1 in the static environment.
145 The ABI of syscalls used by management tools like sockstat and
146 netstat has been broken to allow 32-bit binaries to work on
147 64-bit kernels without modification. These programs will need
148 to match the kernel in order to function. External programs may
149 require minor modifications to accommodate a change of type in
150 structures from pointers to 64-bit virtual addresses.
153 On i386 and amd64 atomics are now inlined. Out of tree modules using
154 atomics will need to be rebuilt.
157 The '%I' format in the kern.corefile sysctl limits the number of
158 core files that a process can generate to the number stored in the
159 debug.ncores sysctl. The '%I' format is replaced by the single digit
160 index. Previously, if all indexes were taken the kernel would overwrite
161 only a core file with the highest index in a filename.
162 Currently the system will create a new core file if there is a free
163 index or if all slots are taken it will overwrite the oldest one.
166 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
167 6.0.1. Please see the 20141231 entry below for information about
168 prerequisites and upgrading, if you are not already using clang 3.5.0
172 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
173 needed to be changed to work with it. This change was made with r335763
174 and requires a mergemaster / etcupdate / etc to update the installed file.
177 r334930 changed the interface between the NFS modules, so they all
178 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
181 As of r334391 lld is the default amd64 system linker; it is installed
182 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
186 The kernel / userland interface for devinfo changed, so you'll
187 need a new kernel and userland as a pair for it to work (rebuilding
188 lib/libdevinfo is all that's required). devinfo and devmatch will
189 not work, but everything else will when there's a mismatch.
192 The on-disk format for hwpmc callchain records has changed to include
193 threadid corresponding to a given record. This changes the field offsets
194 and thus requires that libpmcstat be rebuilt before using a kernel
198 The vxge(4) driver has been removed. This driver was introduced into
199 HEAD one week before the Exar left the Ethernet market and is not
200 known to be used. If you have device vxge in your kernel config file
204 The amd64 kernel now requires a ld that supports ifunc to produce a
205 working kernel, either lld or a newer binutils. lld is built by default
206 on amd64, and the 'buildkernel' target uses it automatically. However,
207 it is not the default linker, so building the kernel the traditional
208 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
209 binutils port/package). lld will soon be default, and this requirement
212 NOTE: As of r334391 lld is the default system linker on amd64, and no
213 workaround is necessary.
216 The nxge(4) driver has been removed. This driver was for PCI-X 10g
217 cards made by s2io/Neterion. The company was aquired by Exar and
218 no longer sells or supports Ethernet products. If you have device
219 nxge in your kernel config file it must be removed.
222 The tz database (tzdb) has been updated to 2018e. This version more
223 correctly models time stamps in time zones with negative DST such as
224 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
225 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
226 time zone abbreviations and the tm_isdst flag.
229 The ixgb(4) driver has been removed. This driver was for an early and
230 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
231 quickly shifted to the long lived ixgbe family. If you have device
232 ixgb in your kernel config file it must be removed.
235 The lmc(4) driver has been removed. This was a WAN interface
236 card that was already reportedly rare in 2003, and had an ambiguous
237 license. If you have device lmc in your kernel config file it must
241 Support for Arcnet networks has been removed. If you have device
242 arcnet or device cm in your kernel config file they must be
246 Support for FDDI networks has been removed. If you have device
247 fddi or device fpa in your kernel config file they must be
251 In addition to supporting RFC 3164 formatted messages, the
252 syslogd(8) service is now capable of parsing RFC 5424 formatted
253 log messages. The main benefit of using RFC 5424 is that clients
254 may now send log messages with timestamps containing year numbers,
255 microseconds and time zone offsets.
257 Similarly, the syslog(3) C library function has been altered to
258 send RFC 5424 formatted messages to the local system logging
259 daemon. On systems using syslogd(8), this change should have no
260 negative impact, as long as syslogd(8) and the C library are
261 updated at the same time. On systems using a different system
262 logging daemon, it may be necessary to make configuration
263 adjustments, depending on the software used.
265 When using syslog-ng, add the 'syslog-protocol' flag to local
266 input sources to enable parsing of RFC 5424 formatted messages:
269 unix-dgram("/var/run/log" flags(syslog-protocol));
272 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
273 of the 'imuxsock' module to let messages be processed by the
274 regular RFC 3164/5424 parsing pipeline:
276 module(load="imuxsock" SysSock.UseSpecialParser="off")
278 Do note that these changes only affect communication between local
279 applications and syslogd(8). The format that syslogd(8) uses to
280 store messages on disk or forward messages to other systems
281 remains unchanged. syslogd(8) still uses RFC 3164 for these
282 purposes. Options to customize this behaviour will be added in the
283 future. Utilities that process log files stored in /var/log are
284 thus expected to continue to function as before.
286 __FreeBSD_version has been incremented to 1200061 to denote this
290 Support for token ring networks has been removed. If you
291 have "device token" in your kernel config you should remove
292 it. No device drivers supported token ring.
295 makefs was modified to be able to tag ISO9660 El Torito boot catalog
296 entries as EFI instead of overloading the i386 tag as done previously.
297 The amd64 mkisoimages.sh script used to build amd64 ISO images for
298 release was updated to use this. This may mean that makefs must be
299 updated before "make cdrom" can be run in the release directory. This
300 should be as simple as:
302 $ cd $SRCDIR/usr.sbin/makefs
303 $ make depend all install
306 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
307 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
308 Co-existance for the transition period will come shortly. Booting is a
309 complex environment and test coverage for Lua-enabled loaders has been
310 thin, so it would be prudent to assume it might not work and make
311 provisions for backup boot methods.
314 devmatch functionality has been turned on in devd. It will automatically
315 load drivers for unattached devices. This may cause unexpected drivers to
316 be loaded. Please report any problems to current@ and imp@freebsd.org.
319 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
320 6.0.0. Please see the 20141231 entry below for information about
321 prerequisites and upgrading, if you are not already using clang 3.5.0
325 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
326 This means it is used to link the kernel and userland libraries and
327 executables, but is not yet installed as /usr/bin/ld by default.
329 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
330 WITHOUT_LLD_BOOTSTRAP=yes
333 On i386, pmtimer has been removed. Its functionality has been folded
334 into apm. It was a no-op on ACPI in current for a while now (but was still
335 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
336 from kernel config files.
339 The use of RSS hash from the network card aka flowid has been
340 disabled by default for lagg(4) as it's currently incompatible with
341 the lacp and loadbalance protocols.
343 This can be re-enabled by setting the following in loader.conf:
344 net.link.lagg.default_use_flowid="1"
347 The SW_WATCHDOG option is no longer necessary to enable the
348 hardclock-based software watchdog if no hardware watchdog is
349 configured. As before, SW_WATCHDOG will cause the software
350 watchdog to be enabled even if a hardware watchdog is configured.
353 r326887 fixes the issue described in the 20171214 UPDATING entry.
354 r326888 flips the switch back to building GELI support always.
357 r362593 broke ZFS + GELI support for reasons unknown. However,
358 it also broke ZFS support generally, so GELI has been turned off
359 by default as the lesser evil in r326857. If you boot off ZFS and/or
360 GELI, it might not be a good time to update.
363 PowerPC users must update loader(8) by rebuilding world before
364 installing a new kernel, as the protocol connecting them has
365 changed. Without the update, loader metadata will not be passed
366 successfully to the kernel and users will have to enter their
367 root partition at the kernel mountroot prompt to continue booting.
368 Newer versions of loader can boot old kernels without issue.
371 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
372 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
373 to WITH/OUT_LOADER_GELI.
376 The naive and non-compliant support of posix_fallocate(2) in ZFS
377 has been removed as of r325320. The system call now returns EINVAL
378 when used on a ZFS file. Although the new behavior complies with the
379 standard, some consumers are not prepared to cope with it.
380 One known victim is lld prior to r325420.
383 Building in a FreeBSD src checkout will automatically create object
384 directories now rather than store files in the current directory if
385 'make obj' was not ran. Calling 'make obj' is no longer necessary.
386 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
387 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
391 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
392 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
393 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
394 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
395 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
396 The UNIFIED_OBJDIR option is a transitional feature that will be
397 removed for 12.0 release; please migrate to the new format for any
398 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
399 than hardcoding paths.
402 The native-xtools target no longer installs the files by default to the
403 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
404 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
407 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
408 options are changing from controlling the build if defined / undefined
409 to controlling the build with explicit 'yes' or 'no' values. They will
410 shift to WITH/WITHOUT options to match other options in the system.
413 libstand has turned into a private library for sys/boot use only.
414 It is no longer supported as a public interface outside of sys/boot.
417 The arm port has split armv6 into armv6 and armv7. armv7 is now
418 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
419 and are running a kernel from before r324363, you will need to add
420 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
423 When building multiple kernels using KERNCONF, non-existent KERNCONF
424 files will produce an error and buildkernel will fail. Previously
425 missing KERNCONF files silently failed giving no indication as to
426 why, only to subsequently discover during installkernel that the
427 desired kernel was never built in the first place.
430 The default serial number format for CTL LUNs has changed. This will
431 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
432 or iSCSI clients care about their LUNs' serial numbers. Users who
433 require serial number stability should hardcode serial numbers in
437 For 32-bit arm compiled for hard-float support, soft-floating point
438 binaries now always get their shared libraries from
439 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
440 /usr/libsoft also existed). Only users with a hard-float ld.so, but
441 soft-float everything else should be affected.
444 The geli password typed at boot is now hidden. To restore the previous
445 behavior, see geli(8) for configuration options.
448 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
449 sysctl values. Minor nit, but requires a rebuild of both world/kernel
453 "make check" behavior (made in ^/head@r295380) has been changed to
454 execute from a limited sandbox, as opposed to executing from
458 - The "beforecheck" and "aftercheck" targets are now specified.
459 - ${CHECKDIR} (added in commit noted above) has been removed.
460 - Legacy behavior can be enabled by setting
461 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
463 If the limited sandbox mode is enabled, "make check" will execute
464 "make distribution", then install, execute the tests, and clean up the
465 sandbox if successful.
467 The "make distribution" and "make install" targets are typically run as
468 root to set appropriate permissions and ownership at installation time.
469 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
470 environment if executing "make check" with limited sandbox mode using
471 an unprivileged user.
474 Since the switch to GPT disk labels, fsck for UFS/FFS has been
475 unable to automatically find alternate superblocks. As of r322297,
476 the information needed to find alternate superblocks has been
477 moved to the end of the area reserved for the boot block.
478 Filesystems created with a newfs of this vintage or later
479 will create the recovery information. If you have a filesystem
480 created prior to this change and wish to have a recovery block
481 created for your filesystem, you can do so by running fsck in
482 foreground mode (i.e., do not use the -p or -y options). As it
483 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
484 to which you should answer yes.
487 As of r321665, an NFSv4 server configuration that services
488 Kerberos mounts or clients that do not support the uid/gid in
489 owner/owner_group string capability, must explicitly enable
490 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
491 machine's /etc/rc.conf file.
494 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
495 Please see the 20141231 entry below for information about prerequisites
496 and upgrading, if you are not already using clang 3.5.0 or higher.
499 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
500 r-commands (rlogin, rsh, etc.) to be built with the base system.
503 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
504 a very major ABI incompatible change, so users of FreeBSD/powerpc must
505 be careful when performing source upgrades. It is best to run
506 'make installworld' from an alternate root system, either a live
507 CD/memory stick, or a temporary root partition. Additionally, all ports
508 must be recompiled. powerpc64 is largely unaffected, except in the case
509 of 32-bit compatibility. All 32-bit binaries will be affected.
512 Forward compatibility for the "ino64" project have been committed. This
513 will allow most new binaries to run on older kernels in a limited
514 fashion. This prevents many of the common foot-shooting actions in the
515 upgrade as well as the limited ability to roll back the kernel across
516 the ino64 upgrade. Complicated use cases may not work properly, though
517 enough simpler ones work to allow recovery in most situations.
520 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
521 if you require the GPL compiler.
524 The internal ABI used for communication between the NFS kernel modules
525 was changed by r320085, so __FreeBSD_version was bumped to
526 ensure all the NFS related modules are updated together.
529 The ABI of struct event was changed by extending the data
530 member to 64bit and adding ext fields. For upgrade, same
531 precautions as for the entry 20170523 "ino64" must be
535 The GNU roff toolchain has been removed from base. To render manpages
536 which are not supported by mandoc(1), man(1) can fallback on GNU roff
537 from ports (and recommends to install it).
538 To render roff(7) documents, consider using GNU roff from ports or the
539 heirloom doctools roff toolchain from ports via pkg install groff or
540 via pkg install heirloom-doctools.
543 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
544 smaller runtime footprint builds. This is useful for embedded systems
545 which only require one chipset support.
547 If you load it as a module, make sure this is in /boot/loader.conf:
551 This will load the HAL, all chip/RF backends and if_ath_pci.
552 If you have if_ath_pci in /boot/loader.conf, ensure it is after
553 if_ath or it will not load any HAL chipset support.
555 If you want to selectively load things (eg on ye cheape ARM/MIPS
556 platforms where RAM is at a premium) you should:
559 * load the chip modules in question
560 * load ath_rate, ath_dfs
562 * load if_ath_pci and/or if_ath_ahb depending upon your particular
563 bus bind type - this is where probe/attach is done.
565 For further comments/feedback, poke adrian@ .
568 The "ino64" 64-bit inode project has been committed, which extends
569 a number of types to 64 bits. Upgrading in place requires care and
570 adherence to the documented upgrade procedure.
572 If using a custom kernel configuration ensure that the
573 COMPAT_FREEBSD11 option is included (as during the upgrade the
574 system will be running the ino64 kernel with the existing world).
576 For the safest in-place upgrade begin by removing previous build
577 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
578 full procedure documented below under the heading "To rebuild
579 everything and install it on the current system." Specifically,
580 a reboot is required after installing the new kernel before
584 The NATM framework including the en(4), fatm(4), hatm(4), and
585 patm(4) devices has been removed. Consumers should plan a
586 migration before the end-of-life date for FreeBSD 11.
589 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
590 diff has not been implemented, if those are needed a newer version of
591 GNU diff is available via the diffutils package under the gdiff name.
594 As of r316810 for ipfilter, keep frags is no longer assumed when
595 keep state is specified in a rule. r316810 aligns ipfilter with
596 documentation in man pages separating keep frags from keep state.
597 This allows keep state to be specified without forcing keep frags
598 and allows keep frags to be specified independently of keep state.
599 To maintain previous behaviour, also specify keep frags with
600 keep state (as documented in ipf.conf.5).
603 arm64 builds now use the base system LLD 4.0.0 linker by default,
604 instead of requiring that the aarch64-binutils port or package be
605 installed. To continue using aarch64-binutils, set
606 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
609 The UDP optimization in entry 20160818 that added the sysctl
610 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
611 packets will no longer be treated as L3 broadcast packets.
614 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
615 use any explicitly assigned loopback address available in the jail
616 instead of using the first assigned address of the jail.
619 The ctl.ko module no longer implements the iSCSI target frontend:
620 cfiscsi.ko does instead.
622 If building cfiscsi.ko as a kernel module, the module can be loaded
623 via one of the following methods:
624 - `cfiscsi_load="YES"` in loader.conf(5).
625 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
626 - ctladm(8)/ctld(8), when compiled with iSCSI support
627 (`WITH_ISCSI=yes` in src.conf(5))
629 Please see cfiscsi(4) for more details.
632 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
633 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
634 same source (previously, the dependency of mmcsd.ko on mmc.ko was
635 missing, but mmcsd.ko now will refuse to load if it is incompatible
639 The syntax of ipfw(8) named states was changed to avoid ambiguity.
640 If you have used named states in the firewall rules, you need to modify
641 them after installworld and before rebooting. Now named states must
642 be prefixed with colon.
645 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
646 removed as the userland we provide cannot use them. The KMS version
647 (sys/dev/drm2) supports the same hardware.
650 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
651 Please see the 20141231 entry below for information about prerequisites
652 and upgrading, if you are not already using clang 3.5.0 or higher.
655 The code that provides support for ZFS .zfs/ directory functionality
656 has been reimplemented. It's not possible now to create a snapshot
657 by mkdir under .zfs/snapshot/. That should be the only user visible
661 EISA bus support has been removed. The WITH_EISA option is no longer
665 MCA bus support has been removed.
668 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
669 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
672 The EM_MULTIQUEUE kernel configuration option is deprecated now that
673 the em(4) driver conforms to iflib specifications.
676 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
677 IFLIB. If you have a custom kernel configuration that excludes em(4)
678 but you use igb(4), you need to re-add em(4) to your custom configuration.
681 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
682 Please see the 20141231 entry below for information about prerequisites
683 and upgrading, if you are not already using clang 3.5.0 or higher.
686 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
687 Please see the 20141231 entry below for information about prerequisites
688 and upgrading, if you are not already using clang 3.5.0 or higher.
691 The layout of the pmap structure has changed for powerpc to put the pmap
692 statistics at the front for all CPU variations. libkvm(3) and all tools
693 that link against it need to be recompiled.
696 isl(4) and cyapa(4) drivers now require a new driver,
697 chromebook_platform(4), to work properly on Chromebook-class hardware.
698 On other types of hardware the drivers may need to be configured using
699 device hints. Please see the corresponding manual pages for details.
702 The urtwn(4) driver was merged into rtwn(4) and now consists of
703 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
705 Also, firmware for RTL8188CE was renamed due to possible name
706 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
709 GNU rcs has been removed from base. It is available as packages:
710 - rcs: Latest GPLv3 GNU rcs version.
711 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
715 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
716 modules now requires that the kernel configuration contain the
717 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
720 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
721 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
724 Relocatable object files with the extension of .So have been renamed
725 to use an extension of .pico instead. The purpose of this change is
726 to avoid a name clash with shared libraries on case-insensitive file
727 systems. On those file systems, foo.So is the same file as foo.so.
730 GNU rcs has been turned off by default. It can (temporarily) be built
731 again by adding WITH_RCS knob in src.conf.
732 Otherwise, GNU rcs is available from packages:
733 - rcs: Latest GPLv3 GNU rcs version.
734 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
737 The backup_uses_rcs functionality has been removed from rc.subr.
740 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
741 two separate components, QUEUE_MACRO_DEBUG_TRACE and
742 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
743 QUEUE_MACRO_DEBUG behavior.
746 r304787 changed some ioctl interfaces between the iSCSI userspace
747 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
748 rebuilt to work with new kernels. __FreeBSD_version has been bumped
752 The UDP receive code has been updated to only treat incoming UDP
753 packets that were addressed to an L2 broadcast address as L3
754 broadcast packets. It is not expected that this will affect any
755 standards-conforming UDP application. The new behaviour can be
756 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
760 Remove the openbsd_poll system call.
761 __FreeBSD_version has been bumped because of this.
764 The stable/11 branch has been created from head@r302406.
767 The libc stub for the pipe(2) system call has been replaced with
768 a wrapper that calls the pipe2(2) system call and the pipe(2)
769 system call is now only implemented by the kernels that include
770 "options COMPAT_FREEBSD10" in their config file (this is the
771 default). Users should ensure that this option is enabled in
772 their kernel or upgrade userspace to r302092 before upgrading their
776 CAM will now strip leading spaces from SCSI disks' serial numbers.
777 This will affect users who create UFS filesystems on SCSI disks using
778 those disk's diskid device nodes. For example, if /etc/fstab
779 previously contained a line like
780 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
781 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
782 transforms like gmirror may also be affected. ZFS users should
786 The bitstring(3) API has been updated with new functionality and
787 improved performance. But it is binary-incompatible with the old API.
788 Objects built with the new headers may not be linked against objects
789 built with the old headers.
792 The brk and sbrk functions have been removed from libc on arm64.
793 Binutils from ports has been updated to not link to these
794 functions and should be updated to the latest version before
795 installing a new libc.
798 The armv6 port now defaults to hard float ABI. Limited support
799 for running both hardfloat and soft float on the same system
800 is available using the libraries installed with -DWITH_LIBSOFT.
801 This has only been tested as an upgrade path for installworld
802 and packages may fail or need manual intervention to run. New
803 packages will be needed.
805 To update an existing self-hosted armv6hf system, you must add
806 TARGET_ARCH=armv6 on the make command line for both the build
807 and the install steps.
810 Kernel modules compiled outside of a kernel build now default to
811 installing to /boot/modules instead of /boot/kernel. Many kernel
812 modules built this way (such as those in ports) already overrode
813 KMODDIR explicitly to install into /boot/modules. However,
814 manually building and installing a module from /sys/modules will
815 now install to /boot/modules instead of /boot/kernel.
818 The CAM I/O scheduler has been committed to the kernel. There should be
819 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
820 list of known rogues that claim support for this but actually corrupt
821 data is believed to be complete, be on the lookout for data
822 corruption. The known rogue list is believed to be complete:
824 o Crucial MX100, M550 drives with MU01 firmware.
825 o Micron M510 and M550 drives with MU01 firmware.
826 o Micron M500 prior to MU07 firmware
827 o Samsung 830, 840, and 850 all firmwares
828 o FCCT M500 all firmwares
830 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
831 with working NCQ TRIM. For Micron branded drives, see your sales rep for
832 updated firmware. Black listed drives will work correctly because these
833 drives work correctly so long as no NCQ TRIMs are sent to them. Given
834 this list is the same as found in Linux, it's believed there are no
835 other rogues in the market place. All other models from the above
838 To be safe, if you are at all concerned, you can quirk each of your
839 drives to prevent NCQ from being sent by setting:
840 kern.cam.ada.X.quirks="0x2"
841 in loader.conf. If the drive requires the 4k sector quirk, set the
845 The FAST_DEPEND build option has been removed and its functionality is
846 now the one true way. The old mkdep(1) style of 'make depend' has
847 been removed. See 20160311 for further details.
850 Resource range types have grown from unsigned long to uintmax_t. All
851 drivers, and anything using libdevinfo, need to be recompiled.
854 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
855 builds. It no longer runs mkdep(1) during 'make depend', and the
856 'make depend' stage can safely be skipped now as it is auto ran
857 when building 'make all' and will generate all SRCS and DPSRCS before
858 building anything else. Dependencies are gathered at compile time with
859 -MF flags kept in separate .depend files per object file. Users should
860 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
864 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
865 kernel modules. Therefore, if you load any kernel modules at boot time,
866 please install the boot loaders after you install the kernel, but before
870 make buildkernel KERNCONF=YOUR_KERNEL_HERE
871 make installkernel KERNCONF=YOUR_KERNEL_HERE
872 make -C sys/boot install
873 <reboot in single user>
875 Then follow the usual steps, described in the General Notes section,
879 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
880 see the 20141231 entry below for information about prerequisites and
881 upgrading, if you are not already using clang 3.5.0 or higher.
884 The AIO subsystem is now a standard part of the kernel. The
885 VFS_AIO kernel option and aio.ko kernel module have been removed.
886 Due to stability concerns, asynchronous I/O requests are only
887 permitted on sockets and raw disks by default. To enable
888 asynchronous I/O requests on all file types, set the
889 vfs.aio.enable_unsafe sysctl to a non-zero value.
892 The ELF object manipulation tool objcopy is now provided by the
893 ELF Tool Chain project rather than by GNU binutils. It should be a
894 drop-in replacement, with the addition of arm64 support. The
895 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
896 to obtain the GNU version if necessary.
899 Building ZFS pools on top of zvols is prohibited by default. That
900 feature has never worked safely; it's always been prone to deadlocks.
901 Using a zvol as the backing store for a VM guest's virtual disk will
902 still work, even if the guest is using ZFS. Legacy behavior can be
903 restored by setting vfs.zfs.vol.recursive=1.
906 The NONE and HPN patches has been removed from OpenSSH. They are
907 still available in the security/openssh-portable port.
910 With the addition of ypldap(8), a new _ypldap user is now required
911 during installworld. "mergemaster -p" can be used to add the user
912 prior to installworld, as documented in the handbook.
915 The tftp loader (pxeboot) now uses the option root-path directive. As a
916 consequence it no longer looks for a pxeboot.4th file on the tftp
917 server. Instead it uses the regular /boot infrastructure as with the
921 The code to start recording plug and play data into the modules has
922 been committed. While the old tools will properly build a new kernel,
923 a number of warnings about "unknown metadata record 4" will be produced
924 for an older kldxref. To avoid such warnings, make sure to rebuild
925 the kernel toolchain (or world). Make sure that you have r292078 or
926 later when trying to build 292077 or later before rebuilding.
929 Debug data files are now built by default with 'make buildworld' and
930 installed with 'make installworld'. This facilitates debugging but
931 requires more disk space both during the build and for the installed
932 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
936 r291527 changed the internal interface between the nfsd.ko and
937 nfscommon.ko modules. As such, they must both be upgraded to-gether.
938 __FreeBSD_version has been bumped because of this.
941 Add support for unicode collation strings leads to a change of
942 order of files listed by ls(1) for example. To get back to the old
943 behaviour, set LC_COLLATE environment variable to "C".
945 Databases administrators will need to reindex their databases given
946 collation results will be different.
948 Due to a bug in install(1) it is recommended to remove the ancient
949 locales before running make installworld.
951 rm -rf /usr/share/locale/*
954 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
955 libcrypto.so.7 or libssl.so.7 must be recompiled.
958 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
959 Kernel modules isp_2400_multi and isp_2500_multi were removed and
960 should be replaced with isp_2400 and isp_2500 modules respectively.
963 The build previously allowed using 'make -n' to not recurse into
964 sub-directories while showing what commands would be executed, and
965 'make -n -n' to recursively show commands. Now 'make -n' will recurse
966 and 'make -N' will not.
969 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
970 and etcupdate will now use this file. A custom sendmail.cf is now
971 updated via this mechanism rather than via installworld. If you had
972 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
973 want to remove the exclusion or change it to "always install".
974 /etc/mail/sendmail.cf is now managed the same way regardless of
975 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
976 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
979 Compatibility shims for legacy ATA device names have been removed.
980 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
981 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
982 environment variables, /dev/ad* and /dev/ar* symbolic links.
985 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
986 Please see the 20141231 entry below for information about prerequisites
987 and upgrading, if you are not already using clang 3.5.0 or higher.
990 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
991 and renamed from .symbols to .debug. This reduces the size requirements
992 on the boot partition or file system and provides consistency with
993 userland debug files.
995 When using the supported kernel installation method the
996 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
997 as is done with /boot/kernel.
999 Developers wishing to maintain the historical behavior of installing
1000 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1003 The wireless drivers had undergone changes that remove the 'parent
1004 interface' from the ifconfig -l output. The rc.d network scripts
1005 used to check presence of a parent interface in the list, so old
1006 scripts would fail to start wireless networking. Thus, etcupdate(3)
1007 or mergemaster(8) run is required after kernel update, to update your
1008 rc.d scripts in /etc.
1011 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1012 These configurations are now automatically interpreted as
1013 'scrub fragment reassemble'.
1016 Kernel-loadable modules for the random(4) device are back. To use
1017 them, the kernel must have
1020 options RANDOM_LOADABLE
1022 kldload(8) can then be used to load random_fortuna.ko
1023 or random_yarrow.ko. Please note that due to the indirect
1024 function calls that the loadable modules need to provide,
1025 the build-in variants will be slightly more efficient.
1027 The random(4) kernel option RANDOM_DUMMY has been retired due to
1028 unpopularity. It was not all that useful anyway.
1031 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1032 Control over building the ELF Tool Chain tools is now provided by
1033 the WITHOUT_TOOLCHAIN knob.
1036 The polarity of Pulse Per Second (PPS) capture events with the
1037 uart(4) driver has been corrected. Prior to this change the PPS
1038 "assert" event corresponded to the trailing edge of a positive PPS
1039 pulse and the "clear" event was the leading edge of the next pulse.
1041 As the width of a PPS pulse in a typical GPS receiver is on the
1042 order of 1 millisecond, most users will not notice any significant
1043 difference with this change.
1045 Anyone who has compensated for the historical polarity reversal by
1046 configuring a negative offset equal to the pulse width will need to
1047 remove that workaround.
1050 The default group assigned to /dev/dri entries has been changed
1051 from 'wheel' to 'video' with the id of '44'. If you want to have
1052 access to the dri devices please add yourself to the video group
1055 # pw groupmod video -m $USER
1058 The menu.rc and loader.rc files will now be replaced during
1059 upgrades. Please migrate local changes to menu.rc.local and
1060 loader.rc.local instead.
1063 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1064 strings and strip have been removed. The src.conf(5) knob
1065 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1068 As ZFS requires more kernel stack pages than is the default on some
1069 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1070 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1072 Please consider using 'options KSTACK_PAGES=X' where X is greater
1073 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1076 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1077 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1078 default, i.e., they will not contain "::". For example, instead
1079 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1080 to have a more specific match, such as different map entries for
1081 IPv6:0:0 vs IPv6:0. This change requires that configuration
1082 data (including maps, files, classes, custom ruleset, etc.) must
1083 use the same format, so make certain such configuration data is
1084 upgrading. As a very simple check search for patterns like
1085 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1086 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1087 the cf option UseCompressedIPv6Addresses.
1090 The default kernel entropy-processing algorithm is now
1091 Fortuna, replacing Yarrow.
1093 Assuming you have 'device random' in your kernel config
1094 file, the configurations allow a kernel option to override
1095 this default. You may choose *ONE* of:
1097 options RANDOM_YARROW # Legacy /dev/random algorithm.
1098 options RANDOM_DUMMY # Blocking-only driver.
1100 If you have neither, you get Fortuna. For most people,
1101 read no further, Fortuna will give a /dev/random that works
1102 like it always used to, and the difference will be irrelevant.
1104 If you remove 'device random', you get *NO* kernel-processed
1105 entropy at all. This may be acceptable to folks building
1106 embedded systems, but has complications. Carry on reading,
1107 and it is assumed you know what you need.
1109 *PLEASE* read random(4) and random(9) if you are in the
1110 habit of tweaking kernel configs, and/or if you are a member
1111 of the embedded community, wanting specific and not-usual
1112 behaviour from your security subsystems.
1114 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1115 random', you will NOT have a functioning /dev/random, and
1116 many cryptographic features will not work, including SSH.
1117 You may also find strange behaviour from the random(3) set
1118 of library functions, in particular sranddev(3), srandomdev(3)
1119 and arc4random(3). The reason for this is that the KERN_ARND
1120 sysctl only returns entropy if it thinks it has some to
1121 share, and with RANDOM_DUMMY or no 'device random' this
1125 An additional fix for the issue described in the 20150614 sendmail
1126 entry below has been committed in revision 284717.
1129 FreeBSD's old make (fmake) has been removed from the system. It is
1130 available as the devel/fmake port or via pkg install fmake.
1133 The fix for the issue described in the 20150614 sendmail entry
1134 below has been committed in revision 284436. The work
1135 around described in that entry is no longer needed unless the
1136 default setting is overridden by a confDH_PARAMETERS configuration
1137 setting of '5' or pointing to a 512 bit DH parameter file.
1140 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1141 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1142 and devel/kyua to version 0.20+ and adjust any calling code to work
1143 with Kyuafile and kyua.
1146 The import of openssl to address the FreeBSD-SA-15:10.openssl
1147 security advisory includes a change which rejects handshakes
1148 with DH parameters below 768 bits. sendmail releases prior
1149 to 8.15.2 (not yet released), defaulted to a 512 bit
1150 DH parameter setting for client connections. To work around
1151 this interoperability, sendmail can be configured to use a
1152 2048 bit DH parameter by:
1154 1. Edit /etc/mail/`hostname`.mc
1155 2. If a setting for confDH_PARAMETERS does not exist or
1156 exists and is set to a string beginning with '5',
1157 replace it with '2'.
1158 3. If a setting for confDH_PARAMETERS exists and is set to
1159 a file path, create a new file with:
1160 openssl dhparam -out /path/to/file 2048
1161 4. Rebuild the .cf file:
1162 cd /etc/mail/; make; make install
1163 5. Restart sendmail:
1164 cd /etc/mail/; make restart
1166 A sendmail patch is coming, at which time this file will be
1170 Generation of legacy formatted entries have been disabled by default
1171 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1172 entries were converted to use the new format by default when the new,
1173 machine independent format have been added and supported since FreeBSD
1176 Please see the pwd_mkdb(8) manual page for further details.
1179 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1180 20141231 entry below for information about prerequisites and upgrading,
1181 if you are not already using 3.5.0 or higher.
1184 TI platform code switched to using vendor DTS files and this update
1185 may break existing systems running on Beaglebone, Beaglebone Black,
1188 - dtb files should be regenerated/reinstalled. Filenames are the
1189 same but content is different now
1190 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1191 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1192 addressing scheme is now pin 25 on /dev/gpioc3.
1193 - Pandaboard: /etc/ttys should be updated, serial console device is
1194 now /dev/ttyu2, not /dev/ttyu0
1197 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1198 If you need the GNU extension from groff soelim(1), install groff
1199 from package: pkg install groff, or via ports: textproc/groff.
1202 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1203 defined in symlink(7); previously symlinks were silently ignored.
1206 The const qualifier has been removed from iconv(3) to comply with
1207 POSIX. The ports tree is aware of this from r384038 onwards.
1210 Libraries specified by LIBADD in Makefiles must have a corresponding
1211 DPADD_<lib> variable to ensure correct dependencies. This is now
1212 enforced in src.libnames.mk.
1215 From legacy ata(4) driver was removed support for SATA controllers
1216 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1217 Kernel modules ataahci and ataadaptec were removed completely,
1218 replaced by ahci and mvs modules respectively.
1221 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1222 the 20141231 entry below for information about prerequisites and
1223 upgrading, if you are not already using 3.5.0 or higher.
1226 The 32-bit PowerPC kernel has been changed to a position-independent
1227 executable. This can only be booted with a version of loader(8)
1228 newer than January 31, 2015, so make sure to update both world and
1229 kernel before rebooting.
1232 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1233 but before r278950, the RNG was not seeded properly. Immediately
1234 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1235 ssh keys or openssl keys) that were generated w/ a kernel from that
1236 range. This does not affect programs that directly used /dev/random
1237 or /dev/urandom. All userland uses of arc4random(3) are affected.
1240 The autofs(4) ABI was changed in order to restore binary compatibility
1241 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1242 with the new kernel.
1245 The powerpc64 kernel has been changed to a position-independent
1246 executable. This can only be booted with a new version of loader(8),
1247 so make sure to update both world and kernel before rebooting.
1250 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1251 only release, no new features have been added. Please see the 20141231
1252 entry below for information about prerequisites and upgrading, if you
1253 are not already using 3.5.0.
1256 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1257 taken from the ELF Tool Chain project rather than GNU binutils. They
1258 should be drop-in replacements, with the addition of arm64 support.
1259 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1260 binutils tools, if necessary. See 20150805 for updated information.
1263 The default Unbound configuration now enables remote control
1264 using a local socket. Users who have already enabled the
1265 local_unbound service should regenerate their configuration
1266 by running "service local_unbound setup" as root.
1269 The GNU texinfo and GNU info pages have been removed.
1270 To be able to view GNU info pages please install texinfo from ports.
1273 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1275 As of this release, a prerequisite for building clang, llvm and lldb is
1276 a C++11 capable compiler and C++11 standard library. This means that to
1277 be able to successfully build the cross-tools stage of buildworld, with
1278 clang as the bootstrap compiler, your system compiler or cross compiler
1279 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1280 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1283 On any standard FreeBSD 10.x or 11.x installation, where clang and
1284 libc++ are on by default (that is, on x86 or arm), this should work out
1287 On 9.x installations where clang is enabled by default, e.g. on x86 and
1288 powerpc, libc++ will not be enabled by default, so libc++ should be
1289 built (with clang) and installed first. If both clang and libc++ are
1290 missing, build clang first, then use it to build libc++.
1292 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1293 the instructions for 9.x above.
1295 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1296 default, and do not build clang.
1298 Many embedded systems are resource constrained, and will not be able to
1299 build clang in a reasonable time, or in some cases at all. In those
1300 cases, cross building bootable systems on amd64 is a workaround.
1302 This new version of clang introduces a number of new warnings, of which
1303 the following are most likely to appear:
1307 This warns in two cases, for both C and C++:
1308 * When the code is trying to take the absolute value of an unsigned
1309 quantity, which is effectively a no-op, and almost never what was
1310 intended. The code should be fixed, if at all possible. If you are
1311 sure that the unsigned quantity can be safely cast to signed, without
1312 loss of information or undefined behavior, you can add an explicit
1313 cast, or disable the warning.
1315 * When the code is trying to take an absolute value, but the called
1316 abs() variant is for the wrong type, which can lead to truncation.
1317 If you want to disable the warning instead of fixing the code, please
1318 make sure that truncation will not occur, or it might lead to unwanted
1321 -Wtautological-undefined-compare and
1322 -Wundefined-bool-conversion
1324 These warn when C++ code is trying to compare 'this' against NULL, while
1325 'this' should never be NULL in well-defined C++ code. However, there is
1326 some legacy (pre C++11) code out there, which actively abuses this
1327 feature, which was less strictly defined in previous C++ versions.
1329 Squid and openjdk do this, for example. The warning can be turned off
1330 for C++98 and earlier, but compiling the code in C++11 mode might result
1331 in unexpected behavior; for example, the parts of the program that are
1332 unreachable could be optimized away.
1335 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1336 kernel sources have been removed. The .h files remain, since some
1337 utilities include them. This will need to be fixed later.
1338 If "mount -t oldnfs ..." is attempted, it will fail.
1339 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1340 the utilities will report errors.
1343 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1344 directories to top level SUBDIR variable when their parent
1345 directory is included in LOCAL_DIRS. Users with build systems with
1346 such hierarchies and without SUBDIR entries in the parent
1347 directory Makefiles should add them or add the directories to
1351 faith(4) and faithd(8) have been removed from the base system. Faith
1352 has been obsolete for a very long time.
1355 vt(4), the new console driver, is enabled by default. It brings
1356 support for Unicode and double-width characters, as well as
1357 support for UEFI and integration with the KMS kernel video
1360 You may need to update your console settings in /etc/rc.conf,
1361 most probably the keymap. During boot, /etc/rc.d/syscons will
1362 indicate what you need to do.
1364 vt(4) still has issues and lacks some features compared to
1365 syscons(4). See the wiki for up-to-date information:
1366 https://wiki.freebsd.org/Newcons
1368 If you want to keep using syscons(4), you can do so by adding
1369 the following line to /boot/loader.conf:
1373 pjdfstest has been integrated into kyua as an opt-in test suite.
1374 Please see share/doc/pjdfstest/README for more details on how to
1378 gperf has been removed from the base system for architectures
1379 that use clang. Ports that require gperf will obtain it from the
1383 pjdfstest has been moved from tools/regression/pjdfstest to
1387 At svn r271982, The default linux compat kernel ABI has been adjusted
1388 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1389 update. If you wish to continue using the linux-f10 compat ports,
1390 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1391 encouraged to update their linux-compat packages to linux-c6 during
1392 their next update cycle.
1395 The ofwfb driver, used to provide a graphics console on PowerPC when
1396 using vt(4), no longer allows mmap() of all physical memory. This
1397 will prevent Xorg on PowerPC with some ATI graphics cards from
1398 initializing properly unless x11-servers/xorg-server is updated to
1402 The xdev targets have been converted to using TARGET and
1403 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1406 The default unbound configuration has been modified to address
1407 issues with reverse lookups on networks that use private
1408 address ranges. If you use the local_unbound service, run
1409 "service local_unbound setup" as root to regenerate your
1410 configuration, then "service local_unbound reload" to load the
1414 The GNU texinfo and GNU info pages are not built and installed
1415 anymore, WITH_INFO knob has been added to allow to built and install
1417 UPDATE: see 20150102 entry on texinfo's removal
1420 The GNU readline library is now an INTERNALLIB - that is, it is
1421 statically linked into consumers (GDB and variants) in the base
1422 system, and the shared library is no longer installed. The
1423 devel/readline port is available for third party software that
1427 The Itanium architecture (ia64) has been removed from the list of
1428 known architectures. This is the first step in the removal of the
1432 Commit r268115 has added NFSv4.1 server support, merged from
1433 projects/nfsv4.1-server. Since this includes changes to the
1434 internal interfaces between the NFS related modules, a full
1435 build of the kernel and modules will be necessary.
1436 __FreeBSD_version has been bumped.
1439 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1440 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1441 which differs from the behaviour controlled by this knob.)
1444 Maximal length of the serial number in CTL was increased from 16 to
1445 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1446 and ctld, need to be rebuilt to work with a new kernel.
1449 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1450 1 respectively to match the upstream numbers. They were out of
1451 sync because, when they were originally added to FreeBSD, the
1452 upstream versions were not respected. These libraries are private
1453 and not yet built by default, so renumbering them should be a
1454 non-issue. However, unclean source trees will yield broken test
1455 programs once the operator executes "make delete-old-libs" after a
1456 "make installworld".
1458 Additionally, the atf-sh binary was made private by moving it into
1459 /usr/libexec/. Already-built shell test programs will keep the
1460 path to the old binary so they will break after "make delete-old"
1463 If you are using WITH_TESTS=yes (not the default), wipe the object
1464 tree and rebuild from scratch to prevent spurious test failures.
1465 This is only needed once: the misnumbered libraries and misplaced
1466 binaries have been added to OptionalObsoleteFiles.inc so they will
1467 be removed during a clean upgrade.
1470 Clang and llvm have been upgraded to 3.4.1 release.
1473 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1474 be removed to avoid issues in the future (and has been added to
1478 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1479 past, it affected all builds that used the bsd.*.mk files. The old
1480 behavior was a bug, but people may have relied upon it. To get this
1481 behavior back, you can .include /etc/src.conf from /etc/make.conf
1482 (which is still global and isn't changed). This also changes the
1483 behavior of incremental builds inside the tree of individual
1484 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1485 Although this has survived make universe and some upgrade scenarios,
1486 other upgrade scenarios may have broken. At least one form of
1487 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1488 as well... In cases where MAKESYSPATH isn't working with this
1489 setting, you'll need to set it to the full path to your tree.
1491 One side effect of all this cleaning up is that bsd.compiler.mk
1492 is no longer implicitly included by bsd.own.mk. If you wish to
1493 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1497 The lindev device has been removed since /dev/full has been made a
1498 standard device. __FreeBSD_version has been bumped.
1501 The knob WITHOUT_VI was added to the base system, which controls
1502 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1503 in order to reorder files share/termcap and didn't build ex(1) as a
1504 build tool, so building/installing with WITH_VI is highly advised for
1505 build hosts for older releases.
1507 This issue has been fixed in stable/9 and stable/10 in r277022 and
1508 r276991, respectively.
1511 The YES_HESIOD knob has been removed. It has been obsolete for
1512 a decade. Please move to using WITH_HESIOD instead or your builds
1513 will silently lack HESIOD.
1516 The uart(4) driver has been changed with respect to its handling
1517 of the low-level console. Previously the uart(4) driver prevented
1518 any process from changing the baudrate or the CLOCAL and HUPCL
1519 control flags. By removing the restrictions, operators can make
1520 changes to the serial console port without having to reboot.
1521 However, when getty(8) is started on the serial device that is
1522 associated with the low-level console, a misconfigured terminal
1523 line in /etc/ttys will now have a real impact.
1524 Before upgrading the kernel, make sure that /etc/ttys has the
1525 serial console device configured as 3wire without baudrate to
1526 preserve the previous behaviour. E.g:
1527 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1530 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1531 to improve performance. To re-enable it, if needed, run rpcbind
1532 with command line option -W.
1535 Switched back to the GPL dtc compiler due to updates in the upstream
1536 dts files not being supported by the BSDL dtc compiler. You will need
1537 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1538 may result while building dtb files during a kernel build if you fail
1539 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1542 Clang and llvm have been upgraded to 3.4 release.
1545 The nve(4) driver has been removed. Please use the nfe(4) driver
1546 for NVIDIA nForce MCP Ethernet adapters instead.
1549 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1550 This could cause certain C++ applications using shared libraries built
1551 against the previous version of libc++ to crash. The incompatibility
1552 has now been fixed, but any C++ applications or shared libraries built
1553 between r261283 and r261801 should be recompiled.
1556 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1557 capability mode support. Please note that enabling the feature in
1558 kernel is still highly recommended.
1561 OpenSSH is now built with sandbox support, and will use sandbox as
1562 the default privilege separation method. This requires Capsicum
1563 capability mode support in kernel.
1566 The libelf and libdwarf libraries have been updated to newer
1567 versions from upstream. Shared library version numbers for
1568 these two libraries were bumped. Any ports or binaries
1569 requiring these two libraries should be recompiled.
1570 __FreeBSD_version is bumped to 1100006.
1573 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1574 instead of providing an explicit one, this would prevent such
1575 Makefile from providing its own Kyuafile in the future during
1576 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1577 intervention is needed to clean an objdir if you use NO_CLEAN:
1578 # find /usr/obj -name Kyuafile | xargs rm -f
1581 The behavior of gss_pseudo_random() for the krb5 mechanism
1582 has changed, for applications requesting a longer random string
1583 than produced by the underlying enctype's pseudo-random() function.
1584 In particular, the random string produced from a session key of
1585 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1586 be different at the 17th octet and later, after this change.
1587 The counter used in the PRF+ construction is now encoded as a
1588 big-endian integer in accordance with RFC 4402.
1589 __FreeBSD_version is bumped to 1100004.
1592 The WITHOUT_ATF build knob has been removed and its functionality
1593 has been subsumed into the more generic WITHOUT_TESTS. If you were
1594 using the former to disable the build of the ATF libraries, you
1595 should change your settings to use the latter.
1598 The default version of mtree is nmtree which is obtained from
1599 NetBSD. The output is generally the same, but may vary
1600 slightly. If you found you need identical output adding
1601 "-F freebsd9" to the command line should do the trick. For the
1602 time being, the old mtree is available as fmtree.
1605 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1606 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1607 1.1.4_8 and verify bsdyml not linked in, before running "make
1609 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1611 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1614 The stable/10 branch has been created in subversion from head
1621 Avoid using make -j when upgrading. While generally safe, there are
1622 sometimes problems using -j to upgrade. If your upgrade fails with
1623 -j, please try again without -j. From time to time in the past there
1624 have been problems using -j with buildworld and/or installworld. This
1625 is especially true when upgrading between "distant" versions (eg one
1626 that cross a major release boundary or several minor releases, or when
1627 several months have passed on the -current branch).
1629 Sometimes, obscure build problems are the result of environment
1630 poisoning. This can happen because the make utility reads its
1631 environment when searching for values for global variables. To run
1632 your build attempts in an "environmental clean room", prefix all make
1633 commands with 'env -i '. See the env(1) manual page for more details.
1635 When upgrading from one major version to another it is generally best to
1636 upgrade to the latest code in the currently installed branch first, then
1637 do an upgrade to the new branch. This is the best-tested upgrade path,
1638 and has the highest probability of being successful. Please try this
1639 approach if you encounter problems with a major version upgrade. Since
1640 the stable 4.x branch point, one has generally been able to upgrade from
1641 anywhere in the most recent stable branch to head / current (or even the
1642 last couple of stable branches). See the top of this file when there's
1645 When upgrading a live system, having a root shell around before
1646 installing anything can help undo problems. Not having a root shell
1647 around can lead to problems if pam has changed too much from your
1648 starting point to allow continued authentication after the upgrade.
1650 This file should be read as a log of events. When a later event changes
1651 information of a prior event, the prior event should not be deleted.
1652 Instead, a pointer to the entry with the new information should be
1653 placed in the old entry. Readers of this file should also sanity check
1654 older entries before relying on them blindly. Authors of new entries
1655 should write them with this in mind.
1659 When upgrading the boot ZFS pool to a new version, always follow
1662 1.) recompile and reinstall the ZFS boot loader and boot block
1663 (this is part of "make buildworld" and "make installworld")
1665 2.) update the ZFS boot block on your boot drive
1667 The following example updates the ZFS boot block on the first
1668 partition (freebsd-boot) of a GPT partitioned drive ada0:
1669 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1671 Non-boot pools do not need these updates.
1675 If you are updating from a prior version of FreeBSD (even one just
1676 a few days old), you should follow this procedure. It is the most
1677 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1679 make kernel-toolchain
1680 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1681 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1683 To test a kernel once
1684 ---------------------
1685 If you just want to boot a kernel once (because you are not sure
1686 if it works, or if you want to boot a known bad kernel to provide
1687 debugging information) run
1688 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1689 nextboot -k testkernel
1691 To rebuild everything and install it on the current system.
1692 -----------------------------------------------------------
1693 # Note: sometimes if you are running current you gotta do more than
1694 # is listed here if you are upgrading from a really old current.
1696 <make sure you have good level 0 dumps>
1698 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1699 make installkernel KERNCONF=YOUR_KERNEL_HERE
1701 <reboot in single user> [3]
1708 To cross-install current onto a separate partition
1709 --------------------------------------------------
1710 # In this approach we use a separate partition to hold
1711 # current's root, 'usr', and 'var' directories. A partition
1712 # holding "/", "/usr" and "/var" should be about 2GB in
1715 <make sure you have good level 0 dumps>
1718 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1719 <maybe newfs current's root partition>
1720 <mount current's root partition on directory ${CURRENT_ROOT}>
1721 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1722 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1723 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1724 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1725 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1726 <reboot into current>
1727 <do a "native" rebuild/install as described in the previous section>
1728 <maybe install compatibility libraries from ports/misc/compat*>
1732 To upgrade in-place from stable to current
1733 ----------------------------------------------
1734 <make sure you have good level 0 dumps>
1736 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1737 make installkernel KERNCONF=YOUR_KERNEL_HERE
1739 <reboot in single user> [3]
1746 Make sure that you've read the UPDATING file to understand the
1747 tweaks to various things you need. At this point in the life
1748 cycle of current, things change often and you are on your own
1749 to cope. The defaults can also change, so please read ALL of
1750 the UPDATING entries.
1752 Also, if you are tracking -current, you must be subscribed to
1753 freebsd-current@freebsd.org. Make sure that before you update
1754 your sources that you have read and understood all the recent
1755 messages there. If in doubt, please track -stable which has
1756 much fewer pitfalls.
1758 [1] If you have third party modules, such as vmware, you
1759 should disable them at this point so they don't crash your
1762 [3] From the bootblocks, boot -s, and then do
1767 adjkerntz -i # if CMOS is wall time
1768 Also, when doing a major release upgrade, it is required that
1769 you boot into single user mode to do the installworld.
1771 [4] Note: This step is non-optional. Failure to do this step
1772 can result in a significant reduction in the functionality of the
1773 system. Attempting to do it by hand is not recommended and those
1774 that pursue this avenue should read this file carefully, as well
1775 as the archives of freebsd-current and freebsd-hackers mailing lists
1776 for potential gotchas. The -U option is also useful to consider.
1777 See mergemaster(8) for more information.
1779 [5] Usually this step is a no-op. However, from time to time
1780 you may need to do this if you get unknown user in the following
1781 step. It never hurts to do it all the time. You may need to
1782 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1783 install) after the buildworld before this step if you last updated
1784 from current before 20130425 or from -stable before 20130430.
1786 [6] This only deletes old files and directories. Old libraries
1787 can be deleted by "make delete-old-libs", but you have to make
1788 sure that no program is using those libraries anymore.
1790 [8] In order to have a kernel that can run the 4.x binaries needed to
1791 do an installworld, you must include the COMPAT_FREEBSD4 option in
1792 your kernel. Failure to do so may leave you with a system that is
1793 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1794 required to run the 5.x binaries on more recent kernels. And so on
1795 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1797 Make sure that you merge any new devices from GENERIC since the
1798 last time you updated your kernel config file.
1800 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1801 "?=" instead of the "=" assignment operator, so that buildworld can
1802 override the CPUTYPE if it needs to.
1804 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1805 not on the command line, or in /etc/make.conf. buildworld will
1806 warn if it is improperly defined.
1809 This file contains a list, in reverse chronological order, of major
1810 breakages in tracking -current. It is not guaranteed to be a complete
1811 list of such breakages, and only contains entries since September 23, 2011.
1812 If you need to see UPDATING entries from before that date, you will need
1813 to fetch an UPDATING file from an older FreeBSD release.
1815 Copyright information:
1817 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1819 Redistribution, publication, translation and use, with or without
1820 modification, in full or in part, in any form or format of this
1821 document are permitted without further permission from the author.
1823 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1824 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1825 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1826 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1827 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1828 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1829 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1830 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1831 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1832 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1833 POSSIBILITY OF SUCH DAMAGE.
1835 Contact Warner Losh if you have any questions about your use of