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