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