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