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