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 set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
21 has been converted to a port (misc/ctm) and will be removed from
22 FreeBSD-13. A depreciation warning will be printed to stderr by
23 the ctm command, but the functionality will remain in base for all
27 The stable/12 branch has been created in subversion from head
31 Ports for the DRM modules have been simplified. Now, amd64 users should
32 just install the drm-kmod port. All others should install
35 Graphics hardware that's newer than about 2010 usually works with
36 drm-kmod. For hardware older than 2013, however, some users will need
37 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
38 than 2008 usually only works in drm-legacy-kmod. The graphics team can
39 only commit to hardware made since 2013 due to the complexity of the
40 market and difficulty to test all the older cards effectively. If you
41 have hardware supported by drm-kmod, you are strongly encouraged to use
42 that as you will get better support.
44 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
45 elsewhere, the drm and drm2 modules will be eliminated from the src base
46 soon (with a limited exception for arm). Please update to the package asap
47 and report any issues to x11@freebsd.org.
49 Generally, anybody using the drm*-kmod packages should add
50 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
51 cross-threading surprises, especially with automatic driver
52 loading from X11 startup. These will become the defaults in 13-current
56 OpenSSL has been updated to version 1.1.1. This update included
57 additional various API changes througout the base system. It is
58 important to rebuild third-party software after upgrading. The value
59 of __FreeBSD_version has been bumped accordingly.
62 The legacy DRM modules and drivers have now been added to the loader's
63 module blacklist, in favor of loading them with kld_list in rc.conf(5).
64 The module blacklist may be overridden with the loader.conf(5)
65 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
69 The cam(4) based nda(4) driver will be used over nvd(4) by default on
70 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
71 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
72 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
76 Reproducible build mode is now on by default, in preparation for
77 FreeBSD 12.0. This eliminates build metadata such as the user,
78 host, and time from the kernel (and uname), unless the working tree
79 corresponds to a modified checkout from a version control system.
80 The previous behavior can be obtained by setting the /etc/src.conf
81 knob WITHOUT_REPRODUCIBLE_BUILD.
84 The Yarrow CSPRNG has been removed from the kernel as it has not been
85 supported by its designers since at least 2003. Fortuna has been the
86 default since FreeBSD-11.
89 devctl freeze/thaw have gone into the tree, the rc scripts have been
90 updated to use them and devmatch has been changed. You should update
91 kernel, userland and rc scripts all at the same time.
94 The default interpreter has been switched from 4th to Lua.
95 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
96 interpreter. If you have custom FORTH code you will need to set
97 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
98 src.conf for the build. This will create default hard links between
99 loader and loader_4th instead of loader and loader_lua, the new default.
100 If you are using UEFI it will create the proper hard link to loader.efi.
102 bhyve uses userboot.so. It remains 4th-only until some issues are solved
103 regarding coexisting with multiple versions of FreeBSD are resolved.
106 ls(1) now respects the COLORTERM environment variable used in other
107 systems and software to indicate that a colored terminal is both
108 supported and desired. If ls(1) is suddenly emitting colors, they may
109 be disabled again by either removing the unwanted COLORTERM from your
110 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
111 may not be observed in a future release.
114 The default pager for most commands has been changed to "less". To
115 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
119 The jedec_ts(4) driver has been removed. A superset of its functionality
120 is available in the jedec_dimm(4) driver, and the manpage for that
121 driver includes migration instructions. If you have "device jedec_ts"
122 in your kernel configuration file, it must be removed.
125 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
126 This should have no effect if the kernel is booted via BIOS/legacy boot.
127 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
128 has a buggy firmware that prevents a successful boot due to use of
132 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
133 support has been removed from the tree. These ports were
134 obsolete and/or known to be broken for many years.
137 loader.efi has been augmented to participate more fully in the
138 UEFI boot manager protocol. loader.efi will now look at the
139 BootXXXX environment variable to determine if a specific kernel
140 or root partition was specified. XXXX is derived from BootCurrent.
141 efibootmgr(8) manages these standard UEFI variables.
144 zfsloader's functionality has now been folded into loader.
145 zfsloader is no longer necessary once you've updated your
146 boot blocks. For a transition period, we will install a
147 hardlink for zfsloader to loader to allow a smooth transition
148 until the boot blocks can be updated (hard link because old
149 zfs boot blocks don't understand symlinks).
152 ARM64 now have efifb support, if you want to have serial console
153 on your arm64 board when an screen is connected and the bootloader
154 setup a frambuffer for us to use, just add :
158 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
159 an screen connected as the firmware will setup a framebuffer are that
160 u-boot will expose as an EFI framebuffer.
163 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
164 or take steps to update /etc/passwd before doing installworld on
165 existing systems. Do not skip the "mergemaster -Fp" step before
166 installworld, as described in the update procedures near the bottom
167 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
168 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
169 the ntp config file contain options that change file/dir locations.
170 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
171 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
172 taking steps to ensure that all required files/dirs are accessible
176 Big endian arm support has been removed.
179 The static environment setup in kernel configs is no longer mutually
180 exclusive with the loader(8) environment by default. In order to
181 restore the previous default behavior of disabling the loader(8)
182 environment if a static environment is present, you must specify
183 loader_env.disabled=1 in the static environment.
186 The ABI of syscalls used by management tools like sockstat and
187 netstat has been broken to allow 32-bit binaries to work on
188 64-bit kernels without modification. These programs will need
189 to match the kernel in order to function. External programs may
190 require minor modifications to accommodate a change of type in
191 structures from pointers to 64-bit virtual addresses.
194 On i386 and amd64 atomics are now inlined. Out of tree modules using
195 atomics will need to be rebuilt.
198 The '%I' format in the kern.corefile sysctl limits the number of
199 core files that a process can generate to the number stored in the
200 debug.ncores sysctl. The '%I' format is replaced by the single digit
201 index. Previously, if all indexes were taken the kernel would overwrite
202 only a core file with the highest index in a filename.
203 Currently the system will create a new core file if there is a free
204 index or if all slots are taken it will overwrite the oldest one.
207 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
208 6.0.1. Please see the 20141231 entry below for information about
209 prerequisites and upgrading, if you are not already using clang 3.5.0
213 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
214 needed to be changed to work with it. This change was made with r335763
215 and requires a mergemaster / etcupdate / etc to update the installed file.
218 r334930 changed the interface between the NFS modules, so they all
219 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
222 As of r334391 lld is the default amd64 system linker; it is installed
223 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
227 The kernel / userland interface for devinfo changed, so you'll
228 need a new kernel and userland as a pair for it to work (rebuilding
229 lib/libdevinfo is all that's required). devinfo and devmatch will
230 not work, but everything else will when there's a mismatch.
233 The on-disk format for hwpmc callchain records has changed to include
234 threadid corresponding to a given record. This changes the field offsets
235 and thus requires that libpmcstat be rebuilt before using a kernel
239 The vxge(4) driver has been removed. This driver was introduced into
240 HEAD one week before the Exar left the Ethernet market and is not
241 known to be used. If you have device vxge in your kernel config file
245 The amd64 kernel now requires a ld that supports ifunc to produce a
246 working kernel, either lld or a newer binutils. lld is built by default
247 on amd64, and the 'buildkernel' target uses it automatically. However,
248 it is not the default linker, so building the kernel the traditional
249 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
250 binutils port/package). lld will soon be default, and this requirement
253 NOTE: As of r334391 lld is the default system linker on amd64, and no
254 workaround is necessary.
257 The nxge(4) driver has been removed. This driver was for PCI-X 10g
258 cards made by s2io/Neterion. The company was aquired by Exar and
259 no longer sells or supports Ethernet products. If you have device
260 nxge in your kernel config file it must be removed.
263 The tz database (tzdb) has been updated to 2018e. This version more
264 correctly models time stamps in time zones with negative DST such as
265 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
266 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
267 time zone abbreviations and the tm_isdst flag.
270 The ixgb(4) driver has been removed. This driver was for an early and
271 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
272 quickly shifted to the long lived ixgbe family. If you have device
273 ixgb in your kernel config file it must be removed.
276 The lmc(4) driver has been removed. This was a WAN interface
277 card that was already reportedly rare in 2003, and had an ambiguous
278 license. If you have device lmc in your kernel config file it must
282 Support for Arcnet networks has been removed. If you have device
283 arcnet or device cm in your kernel config file they must be
287 Support for FDDI networks has been removed. If you have device
288 fddi or device fpa in your kernel config file they must be
292 In addition to supporting RFC 3164 formatted messages, the
293 syslogd(8) service is now capable of parsing RFC 5424 formatted
294 log messages. The main benefit of using RFC 5424 is that clients
295 may now send log messages with timestamps containing year numbers,
296 microseconds and time zone offsets.
298 Similarly, the syslog(3) C library function has been altered to
299 send RFC 5424 formatted messages to the local system logging
300 daemon. On systems using syslogd(8), this change should have no
301 negative impact, as long as syslogd(8) and the C library are
302 updated at the same time. On systems using a different system
303 logging daemon, it may be necessary to make configuration
304 adjustments, depending on the software used.
306 When using syslog-ng, add the 'syslog-protocol' flag to local
307 input sources to enable parsing of RFC 5424 formatted messages:
310 unix-dgram("/var/run/log" flags(syslog-protocol));
313 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
314 of the 'imuxsock' module to let messages be processed by the
315 regular RFC 3164/5424 parsing pipeline:
317 module(load="imuxsock" SysSock.UseSpecialParser="off")
319 Do note that these changes only affect communication between local
320 applications and syslogd(8). The format that syslogd(8) uses to
321 store messages on disk or forward messages to other systems
322 remains unchanged. syslogd(8) still uses RFC 3164 for these
323 purposes. Options to customize this behaviour will be added in the
324 future. Utilities that process log files stored in /var/log are
325 thus expected to continue to function as before.
327 __FreeBSD_version has been incremented to 1200061 to denote this
331 Support for token ring networks has been removed. If you
332 have "device token" in your kernel config you should remove
333 it. No device drivers supported token ring.
336 makefs was modified to be able to tag ISO9660 El Torito boot catalog
337 entries as EFI instead of overloading the i386 tag as done previously.
338 The amd64 mkisoimages.sh script used to build amd64 ISO images for
339 release was updated to use this. This may mean that makefs must be
340 updated before "make cdrom" can be run in the release directory. This
341 should be as simple as:
343 $ cd $SRCDIR/usr.sbin/makefs
344 $ make depend all install
347 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
348 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
349 Co-existance for the transition period will come shortly. Booting is a
350 complex environment and test coverage for Lua-enabled loaders has been
351 thin, so it would be prudent to assume it might not work and make
352 provisions for backup boot methods.
355 devmatch functionality has been turned on in devd. It will automatically
356 load drivers for unattached devices. This may cause unexpected drivers to
357 be loaded. Please report any problems to current@ and imp@freebsd.org.
360 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
361 6.0.0. Please see the 20141231 entry below for information about
362 prerequisites and upgrading, if you are not already using clang 3.5.0
366 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
367 This means it is used to link the kernel and userland libraries and
368 executables, but is not yet installed as /usr/bin/ld by default.
370 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
371 WITHOUT_LLD_BOOTSTRAP=yes
374 On i386, pmtimer has been removed. Its functionality has been folded
375 into apm. It was a no-op on ACPI in current for a while now (but was still
376 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
377 from kernel config files.
380 The use of RSS hash from the network card aka flowid has been
381 disabled by default for lagg(4) as it's currently incompatible with
382 the lacp and loadbalance protocols.
384 This can be re-enabled by setting the following in loader.conf:
385 net.link.lagg.default_use_flowid="1"
388 The SW_WATCHDOG option is no longer necessary to enable the
389 hardclock-based software watchdog if no hardware watchdog is
390 configured. As before, SW_WATCHDOG will cause the software
391 watchdog to be enabled even if a hardware watchdog is configured.
394 r326887 fixes the issue described in the 20171214 UPDATING entry.
395 r326888 flips the switch back to building GELI support always.
398 r362593 broke ZFS + GELI support for reasons unknown. However,
399 it also broke ZFS support generally, so GELI has been turned off
400 by default as the lesser evil in r326857. If you boot off ZFS and/or
401 GELI, it might not be a good time to update.
404 PowerPC users must update loader(8) by rebuilding world before
405 installing a new kernel, as the protocol connecting them has
406 changed. Without the update, loader metadata will not be passed
407 successfully to the kernel and users will have to enter their
408 root partition at the kernel mountroot prompt to continue booting.
409 Newer versions of loader can boot old kernels without issue.
412 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
413 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
414 to WITH/OUT_LOADER_GELI.
417 The naive and non-compliant support of posix_fallocate(2) in ZFS
418 has been removed as of r325320. The system call now returns EINVAL
419 when used on a ZFS file. Although the new behavior complies with the
420 standard, some consumers are not prepared to cope with it.
421 One known victim is lld prior to r325420.
424 Building in a FreeBSD src checkout will automatically create object
425 directories now rather than store files in the current directory if
426 'make obj' was not ran. Calling 'make obj' is no longer necessary.
427 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
428 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
432 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
433 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
434 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
435 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
436 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
437 The UNIFIED_OBJDIR option is a transitional feature that will be
438 removed for 12.0 release; please migrate to the new format for any
439 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
440 than hardcoding paths.
443 The native-xtools target no longer installs the files by default to the
444 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
445 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
448 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
449 options are changing from controlling the build if defined / undefined
450 to controlling the build with explicit 'yes' or 'no' values. They will
451 shift to WITH/WITHOUT options to match other options in the system.
454 libstand has turned into a private library for sys/boot use only.
455 It is no longer supported as a public interface outside of sys/boot.
458 The arm port has split armv6 into armv6 and armv7. armv7 is now
459 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
460 and are running a kernel from before r324363, you will need to add
461 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
464 When building multiple kernels using KERNCONF, non-existent KERNCONF
465 files will produce an error and buildkernel will fail. Previously
466 missing KERNCONF files silently failed giving no indication as to
467 why, only to subsequently discover during installkernel that the
468 desired kernel was never built in the first place.
471 The default serial number format for CTL LUNs has changed. This will
472 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
473 or iSCSI clients care about their LUNs' serial numbers. Users who
474 require serial number stability should hardcode serial numbers in
478 For 32-bit arm compiled for hard-float support, soft-floating point
479 binaries now always get their shared libraries from
480 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
481 /usr/libsoft also existed). Only users with a hard-float ld.so, but
482 soft-float everything else should be affected.
485 The geli password typed at boot is now hidden. To restore the previous
486 behavior, see geli(8) for configuration options.
489 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
490 sysctl values. Minor nit, but requires a rebuild of both world/kernel
494 "make check" behavior (made in ^/head@r295380) has been changed to
495 execute from a limited sandbox, as opposed to executing from
499 - The "beforecheck" and "aftercheck" targets are now specified.
500 - ${CHECKDIR} (added in commit noted above) has been removed.
501 - Legacy behavior can be enabled by setting
502 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
504 If the limited sandbox mode is enabled, "make check" will execute
505 "make distribution", then install, execute the tests, and clean up the
506 sandbox if successful.
508 The "make distribution" and "make install" targets are typically run as
509 root to set appropriate permissions and ownership at installation time.
510 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
511 environment if executing "make check" with limited sandbox mode using
512 an unprivileged user.
515 Since the switch to GPT disk labels, fsck for UFS/FFS has been
516 unable to automatically find alternate superblocks. As of r322297,
517 the information needed to find alternate superblocks has been
518 moved to the end of the area reserved for the boot block.
519 Filesystems created with a newfs of this vintage or later
520 will create the recovery information. If you have a filesystem
521 created prior to this change and wish to have a recovery block
522 created for your filesystem, you can do so by running fsck in
523 foreground mode (i.e., do not use the -p or -y options). As it
524 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
525 to which you should answer yes.
528 As of r321665, an NFSv4 server configuration that services
529 Kerberos mounts or clients that do not support the uid/gid in
530 owner/owner_group string capability, must explicitly enable
531 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
532 machine's /etc/rc.conf file.
535 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
536 Please see the 20141231 entry below for information about prerequisites
537 and upgrading, if you are not already using clang 3.5.0 or higher.
540 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
541 r-commands (rlogin, rsh, etc.) to be built with the base system.
544 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
545 a very major ABI incompatible change, so users of FreeBSD/powerpc must
546 be careful when performing source upgrades. It is best to run
547 'make installworld' from an alternate root system, either a live
548 CD/memory stick, or a temporary root partition. Additionally, all ports
549 must be recompiled. powerpc64 is largely unaffected, except in the case
550 of 32-bit compatibility. All 32-bit binaries will be affected.
553 Forward compatibility for the "ino64" project have been committed. This
554 will allow most new binaries to run on older kernels in a limited
555 fashion. This prevents many of the common foot-shooting actions in the
556 upgrade as well as the limited ability to roll back the kernel across
557 the ino64 upgrade. Complicated use cases may not work properly, though
558 enough simpler ones work to allow recovery in most situations.
561 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
562 if you require the GPL compiler.
565 The internal ABI used for communication between the NFS kernel modules
566 was changed by r320085, so __FreeBSD_version was bumped to
567 ensure all the NFS related modules are updated together.
570 The ABI of struct event was changed by extending the data
571 member to 64bit and adding ext fields. For upgrade, same
572 precautions as for the entry 20170523 "ino64" must be
576 The GNU roff toolchain has been removed from base. To render manpages
577 which are not supported by mandoc(1), man(1) can fallback on GNU roff
578 from ports (and recommends to install it).
579 To render roff(7) documents, consider using GNU roff from ports or the
580 heirloom doctools roff toolchain from ports via pkg install groff or
581 via pkg install heirloom-doctools.
584 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
585 smaller runtime footprint builds. This is useful for embedded systems
586 which only require one chipset support.
588 If you load it as a module, make sure this is in /boot/loader.conf:
592 This will load the HAL, all chip/RF backends and if_ath_pci.
593 If you have if_ath_pci in /boot/loader.conf, ensure it is after
594 if_ath or it will not load any HAL chipset support.
596 If you want to selectively load things (eg on ye cheape ARM/MIPS
597 platforms where RAM is at a premium) you should:
600 * load the chip modules in question
601 * load ath_rate, ath_dfs
603 * load if_ath_pci and/or if_ath_ahb depending upon your particular
604 bus bind type - this is where probe/attach is done.
606 For further comments/feedback, poke adrian@ .
609 The "ino64" 64-bit inode project has been committed, which extends
610 a number of types to 64 bits. Upgrading in place requires care and
611 adherence to the documented upgrade procedure.
613 If using a custom kernel configuration ensure that the
614 COMPAT_FREEBSD11 option is included (as during the upgrade the
615 system will be running the ino64 kernel with the existing world).
617 For the safest in-place upgrade begin by removing previous build
618 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
619 full procedure documented below under the heading "To rebuild
620 everything and install it on the current system." Specifically,
621 a reboot is required after installing the new kernel before
625 The NATM framework including the en(4), fatm(4), hatm(4), and
626 patm(4) devices has been removed. Consumers should plan a
627 migration before the end-of-life date for FreeBSD 11.
630 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
631 diff has not been implemented, if those are needed a newer version of
632 GNU diff is available via the diffutils package under the gdiff name.
635 As of r316810 for ipfilter, keep frags is no longer assumed when
636 keep state is specified in a rule. r316810 aligns ipfilter with
637 documentation in man pages separating keep frags from keep state.
638 This allows keep state to be specified without forcing keep frags
639 and allows keep frags to be specified independently of keep state.
640 To maintain previous behaviour, also specify keep frags with
641 keep state (as documented in ipf.conf.5).
644 arm64 builds now use the base system LLD 4.0.0 linker by default,
645 instead of requiring that the aarch64-binutils port or package be
646 installed. To continue using aarch64-binutils, set
647 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
650 The UDP optimization in entry 20160818 that added the sysctl
651 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
652 packets will no longer be treated as L3 broadcast packets.
655 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
656 use any explicitly assigned loopback address available in the jail
657 instead of using the first assigned address of the jail.
660 The ctl.ko module no longer implements the iSCSI target frontend:
661 cfiscsi.ko does instead.
663 If building cfiscsi.ko as a kernel module, the module can be loaded
664 via one of the following methods:
665 - `cfiscsi_load="YES"` in loader.conf(5).
666 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
667 - ctladm(8)/ctld(8), when compiled with iSCSI support
668 (`WITH_ISCSI=yes` in src.conf(5))
670 Please see cfiscsi(4) for more details.
673 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
674 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
675 same source (previously, the dependency of mmcsd.ko on mmc.ko was
676 missing, but mmcsd.ko now will refuse to load if it is incompatible
680 The syntax of ipfw(8) named states was changed to avoid ambiguity.
681 If you have used named states in the firewall rules, you need to modify
682 them after installworld and before rebooting. Now named states must
683 be prefixed with colon.
686 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
687 removed as the userland we provide cannot use them. The KMS version
688 (sys/dev/drm2) supports the same hardware.
691 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
692 Please see the 20141231 entry below for information about prerequisites
693 and upgrading, if you are not already using clang 3.5.0 or higher.
696 The code that provides support for ZFS .zfs/ directory functionality
697 has been reimplemented. It's not possible now to create a snapshot
698 by mkdir under .zfs/snapshot/. That should be the only user visible
702 EISA bus support has been removed. The WITH_EISA option is no longer
706 MCA bus support has been removed.
709 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
710 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
713 The EM_MULTIQUEUE kernel configuration option is deprecated now that
714 the em(4) driver conforms to iflib specifications.
717 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
718 IFLIB. If you have a custom kernel configuration that excludes em(4)
719 but you use igb(4), you need to re-add em(4) to your custom configuration.
722 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
723 Please see the 20141231 entry below for information about prerequisites
724 and upgrading, if you are not already using clang 3.5.0 or higher.
727 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
728 Please see the 20141231 entry below for information about prerequisites
729 and upgrading, if you are not already using clang 3.5.0 or higher.
732 The layout of the pmap structure has changed for powerpc to put the pmap
733 statistics at the front for all CPU variations. libkvm(3) and all tools
734 that link against it need to be recompiled.
737 isl(4) and cyapa(4) drivers now require a new driver,
738 chromebook_platform(4), to work properly on Chromebook-class hardware.
739 On other types of hardware the drivers may need to be configured using
740 device hints. Please see the corresponding manual pages for details.
743 The urtwn(4) driver was merged into rtwn(4) and now consists of
744 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
746 Also, firmware for RTL8188CE was renamed due to possible name
747 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
750 GNU rcs has been removed from base. It is available as packages:
751 - rcs: Latest GPLv3 GNU rcs version.
752 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
756 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
757 modules now requires that the kernel configuration contain the
758 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
761 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
762 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
765 Relocatable object files with the extension of .So have been renamed
766 to use an extension of .pico instead. The purpose of this change is
767 to avoid a name clash with shared libraries on case-insensitive file
768 systems. On those file systems, foo.So is the same file as foo.so.
771 GNU rcs has been turned off by default. It can (temporarily) be built
772 again by adding WITH_RCS knob in src.conf.
773 Otherwise, GNU rcs is available from packages:
774 - rcs: Latest GPLv3 GNU rcs version.
775 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
778 The backup_uses_rcs functionality has been removed from rc.subr.
781 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
782 two separate components, QUEUE_MACRO_DEBUG_TRACE and
783 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
784 QUEUE_MACRO_DEBUG behavior.
787 r304787 changed some ioctl interfaces between the iSCSI userspace
788 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
789 rebuilt to work with new kernels. __FreeBSD_version has been bumped
793 The UDP receive code has been updated to only treat incoming UDP
794 packets that were addressed to an L2 broadcast address as L3
795 broadcast packets. It is not expected that this will affect any
796 standards-conforming UDP application. The new behaviour can be
797 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
801 Remove the openbsd_poll system call.
802 __FreeBSD_version has been bumped because of this.
805 The stable/11 branch has been created from head@r302406.
808 The libc stub for the pipe(2) system call has been replaced with
809 a wrapper that calls the pipe2(2) system call and the pipe(2)
810 system call is now only implemented by the kernels that include
811 "options COMPAT_FREEBSD10" in their config file (this is the
812 default). Users should ensure that this option is enabled in
813 their kernel or upgrade userspace to r302092 before upgrading their
817 CAM will now strip leading spaces from SCSI disks' serial numbers.
818 This will affect users who create UFS filesystems on SCSI disks using
819 those disk's diskid device nodes. For example, if /etc/fstab
820 previously contained a line like
821 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
822 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
823 transforms like gmirror may also be affected. ZFS users should
827 The bitstring(3) API has been updated with new functionality and
828 improved performance. But it is binary-incompatible with the old API.
829 Objects built with the new headers may not be linked against objects
830 built with the old headers.
833 The brk and sbrk functions have been removed from libc on arm64.
834 Binutils from ports has been updated to not link to these
835 functions and should be updated to the latest version before
836 installing a new libc.
839 The armv6 port now defaults to hard float ABI. Limited support
840 for running both hardfloat and soft float on the same system
841 is available using the libraries installed with -DWITH_LIBSOFT.
842 This has only been tested as an upgrade path for installworld
843 and packages may fail or need manual intervention to run. New
844 packages will be needed.
846 To update an existing self-hosted armv6hf system, you must add
847 TARGET_ARCH=armv6 on the make command line for both the build
848 and the install steps.
851 Kernel modules compiled outside of a kernel build now default to
852 installing to /boot/modules instead of /boot/kernel. Many kernel
853 modules built this way (such as those in ports) already overrode
854 KMODDIR explicitly to install into /boot/modules. However,
855 manually building and installing a module from /sys/modules will
856 now install to /boot/modules instead of /boot/kernel.
859 The CAM I/O scheduler has been committed to the kernel. There should be
860 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
861 list of known rogues that claim support for this but actually corrupt
862 data is believed to be complete, be on the lookout for data
863 corruption. The known rogue list is believed to be complete:
865 o Crucial MX100, M550 drives with MU01 firmware.
866 o Micron M510 and M550 drives with MU01 firmware.
867 o Micron M500 prior to MU07 firmware
868 o Samsung 830, 840, and 850 all firmwares
869 o FCCT M500 all firmwares
871 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
872 with working NCQ TRIM. For Micron branded drives, see your sales rep for
873 updated firmware. Black listed drives will work correctly because these
874 drives work correctly so long as no NCQ TRIMs are sent to them. Given
875 this list is the same as found in Linux, it's believed there are no
876 other rogues in the market place. All other models from the above
879 To be safe, if you are at all concerned, you can quirk each of your
880 drives to prevent NCQ from being sent by setting:
881 kern.cam.ada.X.quirks="0x2"
882 in loader.conf. If the drive requires the 4k sector quirk, set the
886 The FAST_DEPEND build option has been removed and its functionality is
887 now the one true way. The old mkdep(1) style of 'make depend' has
888 been removed. See 20160311 for further details.
891 Resource range types have grown from unsigned long to uintmax_t. All
892 drivers, and anything using libdevinfo, need to be recompiled.
895 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
896 builds. It no longer runs mkdep(1) during 'make depend', and the
897 'make depend' stage can safely be skipped now as it is auto ran
898 when building 'make all' and will generate all SRCS and DPSRCS before
899 building anything else. Dependencies are gathered at compile time with
900 -MF flags kept in separate .depend files per object file. Users should
901 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
905 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
906 kernel modules. Therefore, if you load any kernel modules at boot time,
907 please install the boot loaders after you install the kernel, but before
911 make buildkernel KERNCONF=YOUR_KERNEL_HERE
912 make installkernel KERNCONF=YOUR_KERNEL_HERE
913 make -C sys/boot install
914 <reboot in single user>
916 Then follow the usual steps, described in the General Notes section,
920 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
921 see the 20141231 entry below for information about prerequisites and
922 upgrading, if you are not already using clang 3.5.0 or higher.
925 The AIO subsystem is now a standard part of the kernel. The
926 VFS_AIO kernel option and aio.ko kernel module have been removed.
927 Due to stability concerns, asynchronous I/O requests are only
928 permitted on sockets and raw disks by default. To enable
929 asynchronous I/O requests on all file types, set the
930 vfs.aio.enable_unsafe sysctl to a non-zero value.
933 The ELF object manipulation tool objcopy is now provided by the
934 ELF Tool Chain project rather than by GNU binutils. It should be a
935 drop-in replacement, with the addition of arm64 support. The
936 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
937 to obtain the GNU version if necessary.
940 Building ZFS pools on top of zvols is prohibited by default. That
941 feature has never worked safely; it's always been prone to deadlocks.
942 Using a zvol as the backing store for a VM guest's virtual disk will
943 still work, even if the guest is using ZFS. Legacy behavior can be
944 restored by setting vfs.zfs.vol.recursive=1.
947 The NONE and HPN patches has been removed from OpenSSH. They are
948 still available in the security/openssh-portable port.
951 With the addition of ypldap(8), a new _ypldap user is now required
952 during installworld. "mergemaster -p" can be used to add the user
953 prior to installworld, as documented in the handbook.
956 The tftp loader (pxeboot) now uses the option root-path directive. As a
957 consequence it no longer looks for a pxeboot.4th file on the tftp
958 server. Instead it uses the regular /boot infrastructure as with the
962 The code to start recording plug and play data into the modules has
963 been committed. While the old tools will properly build a new kernel,
964 a number of warnings about "unknown metadata record 4" will be produced
965 for an older kldxref. To avoid such warnings, make sure to rebuild
966 the kernel toolchain (or world). Make sure that you have r292078 or
967 later when trying to build 292077 or later before rebuilding.
970 Debug data files are now built by default with 'make buildworld' and
971 installed with 'make installworld'. This facilitates debugging but
972 requires more disk space both during the build and for the installed
973 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
977 r291527 changed the internal interface between the nfsd.ko and
978 nfscommon.ko modules. As such, they must both be upgraded to-gether.
979 __FreeBSD_version has been bumped because of this.
982 Add support for unicode collation strings leads to a change of
983 order of files listed by ls(1) for example. To get back to the old
984 behaviour, set LC_COLLATE environment variable to "C".
986 Databases administrators will need to reindex their databases given
987 collation results will be different.
989 Due to a bug in install(1) it is recommended to remove the ancient
990 locales before running make installworld.
992 rm -rf /usr/share/locale/*
995 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
996 libcrypto.so.7 or libssl.so.7 must be recompiled.
999 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1000 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1001 should be replaced with isp_2400 and isp_2500 modules respectively.
1004 The build previously allowed using 'make -n' to not recurse into
1005 sub-directories while showing what commands would be executed, and
1006 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1007 and 'make -N' will not.
1010 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1011 and etcupdate will now use this file. A custom sendmail.cf is now
1012 updated via this mechanism rather than via installworld. If you had
1013 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1014 want to remove the exclusion or change it to "always install".
1015 /etc/mail/sendmail.cf is now managed the same way regardless of
1016 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1017 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1020 Compatibility shims for legacy ATA device names have been removed.
1021 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1022 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1023 environment variables, /dev/ad* and /dev/ar* symbolic links.
1026 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1027 Please see the 20141231 entry below for information about prerequisites
1028 and upgrading, if you are not already using clang 3.5.0 or higher.
1031 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1032 and renamed from .symbols to .debug. This reduces the size requirements
1033 on the boot partition or file system and provides consistency with
1034 userland debug files.
1036 When using the supported kernel installation method the
1037 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1038 as is done with /boot/kernel.
1040 Developers wishing to maintain the historical behavior of installing
1041 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1044 The wireless drivers had undergone changes that remove the 'parent
1045 interface' from the ifconfig -l output. The rc.d network scripts
1046 used to check presence of a parent interface in the list, so old
1047 scripts would fail to start wireless networking. Thus, etcupdate(3)
1048 or mergemaster(8) run is required after kernel update, to update your
1049 rc.d scripts in /etc.
1052 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1053 These configurations are now automatically interpreted as
1054 'scrub fragment reassemble'.
1057 Kernel-loadable modules for the random(4) device are back. To use
1058 them, the kernel must have
1061 options RANDOM_LOADABLE
1063 kldload(8) can then be used to load random_fortuna.ko
1064 or random_yarrow.ko. Please note that due to the indirect
1065 function calls that the loadable modules need to provide,
1066 the build-in variants will be slightly more efficient.
1068 The random(4) kernel option RANDOM_DUMMY has been retired due to
1069 unpopularity. It was not all that useful anyway.
1072 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1073 Control over building the ELF Tool Chain tools is now provided by
1074 the WITHOUT_TOOLCHAIN knob.
1077 The polarity of Pulse Per Second (PPS) capture events with the
1078 uart(4) driver has been corrected. Prior to this change the PPS
1079 "assert" event corresponded to the trailing edge of a positive PPS
1080 pulse and the "clear" event was the leading edge of the next pulse.
1082 As the width of a PPS pulse in a typical GPS receiver is on the
1083 order of 1 millisecond, most users will not notice any significant
1084 difference with this change.
1086 Anyone who has compensated for the historical polarity reversal by
1087 configuring a negative offset equal to the pulse width will need to
1088 remove that workaround.
1091 The default group assigned to /dev/dri entries has been changed
1092 from 'wheel' to 'video' with the id of '44'. If you want to have
1093 access to the dri devices please add yourself to the video group
1096 # pw groupmod video -m $USER
1099 The menu.rc and loader.rc files will now be replaced during
1100 upgrades. Please migrate local changes to menu.rc.local and
1101 loader.rc.local instead.
1104 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1105 strings and strip have been removed. The src.conf(5) knob
1106 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1109 As ZFS requires more kernel stack pages than is the default on some
1110 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1111 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1113 Please consider using 'options KSTACK_PAGES=X' where X is greater
1114 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1117 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1118 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1119 default, i.e., they will not contain "::". For example, instead
1120 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1121 to have a more specific match, such as different map entries for
1122 IPv6:0:0 vs IPv6:0. This change requires that configuration
1123 data (including maps, files, classes, custom ruleset, etc.) must
1124 use the same format, so make certain such configuration data is
1125 upgrading. As a very simple check search for patterns like
1126 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1127 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1128 the cf option UseCompressedIPv6Addresses.
1131 The default kernel entropy-processing algorithm is now
1132 Fortuna, replacing Yarrow.
1134 Assuming you have 'device random' in your kernel config
1135 file, the configurations allow a kernel option to override
1136 this default. You may choose *ONE* of:
1138 options RANDOM_YARROW # Legacy /dev/random algorithm.
1139 options RANDOM_DUMMY # Blocking-only driver.
1141 If you have neither, you get Fortuna. For most people,
1142 read no further, Fortuna will give a /dev/random that works
1143 like it always used to, and the difference will be irrelevant.
1145 If you remove 'device random', you get *NO* kernel-processed
1146 entropy at all. This may be acceptable to folks building
1147 embedded systems, but has complications. Carry on reading,
1148 and it is assumed you know what you need.
1150 *PLEASE* read random(4) and random(9) if you are in the
1151 habit of tweaking kernel configs, and/or if you are a member
1152 of the embedded community, wanting specific and not-usual
1153 behaviour from your security subsystems.
1155 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1156 random', you will NOT have a functioning /dev/random, and
1157 many cryptographic features will not work, including SSH.
1158 You may also find strange behaviour from the random(3) set
1159 of library functions, in particular sranddev(3), srandomdev(3)
1160 and arc4random(3). The reason for this is that the KERN_ARND
1161 sysctl only returns entropy if it thinks it has some to
1162 share, and with RANDOM_DUMMY or no 'device random' this
1166 An additional fix for the issue described in the 20150614 sendmail
1167 entry below has been committed in revision 284717.
1170 FreeBSD's old make (fmake) has been removed from the system. It is
1171 available as the devel/fmake port or via pkg install fmake.
1174 The fix for the issue described in the 20150614 sendmail entry
1175 below has been committed in revision 284436. The work
1176 around described in that entry is no longer needed unless the
1177 default setting is overridden by a confDH_PARAMETERS configuration
1178 setting of '5' or pointing to a 512 bit DH parameter file.
1181 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1182 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1183 and devel/kyua to version 0.20+ and adjust any calling code to work
1184 with Kyuafile and kyua.
1187 The import of openssl to address the FreeBSD-SA-15:10.openssl
1188 security advisory includes a change which rejects handshakes
1189 with DH parameters below 768 bits. sendmail releases prior
1190 to 8.15.2 (not yet released), defaulted to a 512 bit
1191 DH parameter setting for client connections. To work around
1192 this interoperability, sendmail can be configured to use a
1193 2048 bit DH parameter by:
1195 1. Edit /etc/mail/`hostname`.mc
1196 2. If a setting for confDH_PARAMETERS does not exist or
1197 exists and is set to a string beginning with '5',
1198 replace it with '2'.
1199 3. If a setting for confDH_PARAMETERS exists and is set to
1200 a file path, create a new file with:
1201 openssl dhparam -out /path/to/file 2048
1202 4. Rebuild the .cf file:
1203 cd /etc/mail/; make; make install
1204 5. Restart sendmail:
1205 cd /etc/mail/; make restart
1207 A sendmail patch is coming, at which time this file will be
1211 Generation of legacy formatted entries have been disabled by default
1212 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1213 entries were converted to use the new format by default when the new,
1214 machine independent format have been added and supported since FreeBSD
1217 Please see the pwd_mkdb(8) manual page for further details.
1220 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1221 20141231 entry below for information about prerequisites and upgrading,
1222 if you are not already using 3.5.0 or higher.
1225 TI platform code switched to using vendor DTS files and this update
1226 may break existing systems running on Beaglebone, Beaglebone Black,
1229 - dtb files should be regenerated/reinstalled. Filenames are the
1230 same but content is different now
1231 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1232 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1233 addressing scheme is now pin 25 on /dev/gpioc3.
1234 - Pandaboard: /etc/ttys should be updated, serial console device is
1235 now /dev/ttyu2, not /dev/ttyu0
1238 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1239 If you need the GNU extension from groff soelim(1), install groff
1240 from package: pkg install groff, or via ports: textproc/groff.
1243 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1244 defined in symlink(7); previously symlinks were silently ignored.
1247 The const qualifier has been removed from iconv(3) to comply with
1248 POSIX. The ports tree is aware of this from r384038 onwards.
1251 Libraries specified by LIBADD in Makefiles must have a corresponding
1252 DPADD_<lib> variable to ensure correct dependencies. This is now
1253 enforced in src.libnames.mk.
1256 From legacy ata(4) driver was removed support for SATA controllers
1257 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1258 Kernel modules ataahci and ataadaptec were removed completely,
1259 replaced by ahci and mvs modules respectively.
1262 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1263 the 20141231 entry below for information about prerequisites and
1264 upgrading, if you are not already using 3.5.0 or higher.
1267 The 32-bit PowerPC kernel has been changed to a position-independent
1268 executable. This can only be booted with a version of loader(8)
1269 newer than January 31, 2015, so make sure to update both world and
1270 kernel before rebooting.
1273 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1274 but before r278950, the RNG was not seeded properly. Immediately
1275 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1276 ssh keys or openssl keys) that were generated w/ a kernel from that
1277 range. This does not affect programs that directly used /dev/random
1278 or /dev/urandom. All userland uses of arc4random(3) are affected.
1281 The autofs(4) ABI was changed in order to restore binary compatibility
1282 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1283 with the new kernel.
1286 The powerpc64 kernel has been changed to a position-independent
1287 executable. This can only be booted with a new version of loader(8),
1288 so make sure to update both world and kernel before rebooting.
1291 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1292 only release, no new features have been added. Please see the 20141231
1293 entry below for information about prerequisites and upgrading, if you
1294 are not already using 3.5.0.
1297 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1298 taken from the ELF Tool Chain project rather than GNU binutils. They
1299 should be drop-in replacements, with the addition of arm64 support.
1300 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1301 binutils tools, if necessary. See 20150805 for updated information.
1304 The default Unbound configuration now enables remote control
1305 using a local socket. Users who have already enabled the
1306 local_unbound service should regenerate their configuration
1307 by running "service local_unbound setup" as root.
1310 The GNU texinfo and GNU info pages have been removed.
1311 To be able to view GNU info pages please install texinfo from ports.
1314 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1316 As of this release, a prerequisite for building clang, llvm and lldb is
1317 a C++11 capable compiler and C++11 standard library. This means that to
1318 be able to successfully build the cross-tools stage of buildworld, with
1319 clang as the bootstrap compiler, your system compiler or cross compiler
1320 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1321 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1324 On any standard FreeBSD 10.x or 11.x installation, where clang and
1325 libc++ are on by default (that is, on x86 or arm), this should work out
1328 On 9.x installations where clang is enabled by default, e.g. on x86 and
1329 powerpc, libc++ will not be enabled by default, so libc++ should be
1330 built (with clang) and installed first. If both clang and libc++ are
1331 missing, build clang first, then use it to build libc++.
1333 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1334 the instructions for 9.x above.
1336 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1337 default, and do not build clang.
1339 Many embedded systems are resource constrained, and will not be able to
1340 build clang in a reasonable time, or in some cases at all. In those
1341 cases, cross building bootable systems on amd64 is a workaround.
1343 This new version of clang introduces a number of new warnings, of which
1344 the following are most likely to appear:
1348 This warns in two cases, for both C and C++:
1349 * When the code is trying to take the absolute value of an unsigned
1350 quantity, which is effectively a no-op, and almost never what was
1351 intended. The code should be fixed, if at all possible. If you are
1352 sure that the unsigned quantity can be safely cast to signed, without
1353 loss of information or undefined behavior, you can add an explicit
1354 cast, or disable the warning.
1356 * When the code is trying to take an absolute value, but the called
1357 abs() variant is for the wrong type, which can lead to truncation.
1358 If you want to disable the warning instead of fixing the code, please
1359 make sure that truncation will not occur, or it might lead to unwanted
1362 -Wtautological-undefined-compare and
1363 -Wundefined-bool-conversion
1365 These warn when C++ code is trying to compare 'this' against NULL, while
1366 'this' should never be NULL in well-defined C++ code. However, there is
1367 some legacy (pre C++11) code out there, which actively abuses this
1368 feature, which was less strictly defined in previous C++ versions.
1370 Squid and openjdk do this, for example. The warning can be turned off
1371 for C++98 and earlier, but compiling the code in C++11 mode might result
1372 in unexpected behavior; for example, the parts of the program that are
1373 unreachable could be optimized away.
1376 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1377 kernel sources have been removed. The .h files remain, since some
1378 utilities include them. This will need to be fixed later.
1379 If "mount -t oldnfs ..." is attempted, it will fail.
1380 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1381 the utilities will report errors.
1384 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1385 directories to top level SUBDIR variable when their parent
1386 directory is included in LOCAL_DIRS. Users with build systems with
1387 such hierarchies and without SUBDIR entries in the parent
1388 directory Makefiles should add them or add the directories to
1392 faith(4) and faithd(8) have been removed from the base system. Faith
1393 has been obsolete for a very long time.
1396 vt(4), the new console driver, is enabled by default. It brings
1397 support for Unicode and double-width characters, as well as
1398 support for UEFI and integration with the KMS kernel video
1401 You may need to update your console settings in /etc/rc.conf,
1402 most probably the keymap. During boot, /etc/rc.d/syscons will
1403 indicate what you need to do.
1405 vt(4) still has issues and lacks some features compared to
1406 syscons(4). See the wiki for up-to-date information:
1407 https://wiki.freebsd.org/Newcons
1409 If you want to keep using syscons(4), you can do so by adding
1410 the following line to /boot/loader.conf:
1414 pjdfstest has been integrated into kyua as an opt-in test suite.
1415 Please see share/doc/pjdfstest/README for more details on how to
1419 gperf has been removed from the base system for architectures
1420 that use clang. Ports that require gperf will obtain it from the
1424 pjdfstest has been moved from tools/regression/pjdfstest to
1428 At svn r271982, The default linux compat kernel ABI has been adjusted
1429 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1430 update. If you wish to continue using the linux-f10 compat ports,
1431 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1432 encouraged to update their linux-compat packages to linux-c6 during
1433 their next update cycle.
1436 The ofwfb driver, used to provide a graphics console on PowerPC when
1437 using vt(4), no longer allows mmap() of all physical memory. This
1438 will prevent Xorg on PowerPC with some ATI graphics cards from
1439 initializing properly unless x11-servers/xorg-server is updated to
1443 The xdev targets have been converted to using TARGET and
1444 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1447 The default unbound configuration has been modified to address
1448 issues with reverse lookups on networks that use private
1449 address ranges. If you use the local_unbound service, run
1450 "service local_unbound setup" as root to regenerate your
1451 configuration, then "service local_unbound reload" to load the
1455 The GNU texinfo and GNU info pages are not built and installed
1456 anymore, WITH_INFO knob has been added to allow to built and install
1458 UPDATE: see 20150102 entry on texinfo's removal
1461 The GNU readline library is now an INTERNALLIB - that is, it is
1462 statically linked into consumers (GDB and variants) in the base
1463 system, and the shared library is no longer installed. The
1464 devel/readline port is available for third party software that
1468 The Itanium architecture (ia64) has been removed from the list of
1469 known architectures. This is the first step in the removal of the
1473 Commit r268115 has added NFSv4.1 server support, merged from
1474 projects/nfsv4.1-server. Since this includes changes to the
1475 internal interfaces between the NFS related modules, a full
1476 build of the kernel and modules will be necessary.
1477 __FreeBSD_version has been bumped.
1480 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1481 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1482 which differs from the behaviour controlled by this knob.)
1485 Maximal length of the serial number in CTL was increased from 16 to
1486 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1487 and ctld, need to be rebuilt to work with a new kernel.
1490 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1491 1 respectively to match the upstream numbers. They were out of
1492 sync because, when they were originally added to FreeBSD, the
1493 upstream versions were not respected. These libraries are private
1494 and not yet built by default, so renumbering them should be a
1495 non-issue. However, unclean source trees will yield broken test
1496 programs once the operator executes "make delete-old-libs" after a
1497 "make installworld".
1499 Additionally, the atf-sh binary was made private by moving it into
1500 /usr/libexec/. Already-built shell test programs will keep the
1501 path to the old binary so they will break after "make delete-old"
1504 If you are using WITH_TESTS=yes (not the default), wipe the object
1505 tree and rebuild from scratch to prevent spurious test failures.
1506 This is only needed once: the misnumbered libraries and misplaced
1507 binaries have been added to OptionalObsoleteFiles.inc so they will
1508 be removed during a clean upgrade.
1511 Clang and llvm have been upgraded to 3.4.1 release.
1514 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1515 be removed to avoid issues in the future (and has been added to
1519 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1520 past, it affected all builds that used the bsd.*.mk files. The old
1521 behavior was a bug, but people may have relied upon it. To get this
1522 behavior back, you can .include /etc/src.conf from /etc/make.conf
1523 (which is still global and isn't changed). This also changes the
1524 behavior of incremental builds inside the tree of individual
1525 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1526 Although this has survived make universe and some upgrade scenarios,
1527 other upgrade scenarios may have broken. At least one form of
1528 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1529 as well... In cases where MAKESYSPATH isn't working with this
1530 setting, you'll need to set it to the full path to your tree.
1532 One side effect of all this cleaning up is that bsd.compiler.mk
1533 is no longer implicitly included by bsd.own.mk. If you wish to
1534 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1538 The lindev device has been removed since /dev/full has been made a
1539 standard device. __FreeBSD_version has been bumped.
1542 The knob WITHOUT_VI was added to the base system, which controls
1543 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1544 in order to reorder files share/termcap and didn't build ex(1) as a
1545 build tool, so building/installing with WITH_VI is highly advised for
1546 build hosts for older releases.
1548 This issue has been fixed in stable/9 and stable/10 in r277022 and
1549 r276991, respectively.
1552 The YES_HESIOD knob has been removed. It has been obsolete for
1553 a decade. Please move to using WITH_HESIOD instead or your builds
1554 will silently lack HESIOD.
1557 The uart(4) driver has been changed with respect to its handling
1558 of the low-level console. Previously the uart(4) driver prevented
1559 any process from changing the baudrate or the CLOCAL and HUPCL
1560 control flags. By removing the restrictions, operators can make
1561 changes to the serial console port without having to reboot.
1562 However, when getty(8) is started on the serial device that is
1563 associated with the low-level console, a misconfigured terminal
1564 line in /etc/ttys will now have a real impact.
1565 Before upgrading the kernel, make sure that /etc/ttys has the
1566 serial console device configured as 3wire without baudrate to
1567 preserve the previous behaviour. E.g:
1568 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1571 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1572 to improve performance. To re-enable it, if needed, run rpcbind
1573 with command line option -W.
1576 Switched back to the GPL dtc compiler due to updates in the upstream
1577 dts files not being supported by the BSDL dtc compiler. You will need
1578 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1579 may result while building dtb files during a kernel build if you fail
1580 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1583 Clang and llvm have been upgraded to 3.4 release.
1586 The nve(4) driver has been removed. Please use the nfe(4) driver
1587 for NVIDIA nForce MCP Ethernet adapters instead.
1590 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1591 This could cause certain C++ applications using shared libraries built
1592 against the previous version of libc++ to crash. The incompatibility
1593 has now been fixed, but any C++ applications or shared libraries built
1594 between r261283 and r261801 should be recompiled.
1597 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1598 capability mode support. Please note that enabling the feature in
1599 kernel is still highly recommended.
1602 OpenSSH is now built with sandbox support, and will use sandbox as
1603 the default privilege separation method. This requires Capsicum
1604 capability mode support in kernel.
1607 The libelf and libdwarf libraries have been updated to newer
1608 versions from upstream. Shared library version numbers for
1609 these two libraries were bumped. Any ports or binaries
1610 requiring these two libraries should be recompiled.
1611 __FreeBSD_version is bumped to 1100006.
1614 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1615 instead of providing an explicit one, this would prevent such
1616 Makefile from providing its own Kyuafile in the future during
1617 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1618 intervention is needed to clean an objdir if you use NO_CLEAN:
1619 # find /usr/obj -name Kyuafile | xargs rm -f
1622 The behavior of gss_pseudo_random() for the krb5 mechanism
1623 has changed, for applications requesting a longer random string
1624 than produced by the underlying enctype's pseudo-random() function.
1625 In particular, the random string produced from a session key of
1626 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1627 be different at the 17th octet and later, after this change.
1628 The counter used in the PRF+ construction is now encoded as a
1629 big-endian integer in accordance with RFC 4402.
1630 __FreeBSD_version is bumped to 1100004.
1633 The WITHOUT_ATF build knob has been removed and its functionality
1634 has been subsumed into the more generic WITHOUT_TESTS. If you were
1635 using the former to disable the build of the ATF libraries, you
1636 should change your settings to use the latter.
1639 The default version of mtree is nmtree which is obtained from
1640 NetBSD. The output is generally the same, but may vary
1641 slightly. If you found you need identical output adding
1642 "-F freebsd9" to the command line should do the trick. For the
1643 time being, the old mtree is available as fmtree.
1646 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1647 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1648 1.1.4_8 and verify bsdyml not linked in, before running "make
1650 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1652 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1655 The stable/10 branch has been created in subversion from head
1662 Avoid using make -j when upgrading. While generally safe, there are
1663 sometimes problems using -j to upgrade. If your upgrade fails with
1664 -j, please try again without -j. From time to time in the past there
1665 have been problems using -j with buildworld and/or installworld. This
1666 is especially true when upgrading between "distant" versions (eg one
1667 that cross a major release boundary or several minor releases, or when
1668 several months have passed on the -current branch).
1670 Sometimes, obscure build problems are the result of environment
1671 poisoning. This can happen because the make utility reads its
1672 environment when searching for values for global variables. To run
1673 your build attempts in an "environmental clean room", prefix all make
1674 commands with 'env -i '. See the env(1) manual page for more details.
1676 When upgrading from one major version to another it is generally best to
1677 upgrade to the latest code in the currently installed branch first, then
1678 do an upgrade to the new branch. This is the best-tested upgrade path,
1679 and has the highest probability of being successful. Please try this
1680 approach if you encounter problems with a major version upgrade. Since
1681 the stable 4.x branch point, one has generally been able to upgrade from
1682 anywhere in the most recent stable branch to head / current (or even the
1683 last couple of stable branches). See the top of this file when there's
1686 When upgrading a live system, having a root shell around before
1687 installing anything can help undo problems. Not having a root shell
1688 around can lead to problems if pam has changed too much from your
1689 starting point to allow continued authentication after the upgrade.
1691 This file should be read as a log of events. When a later event changes
1692 information of a prior event, the prior event should not be deleted.
1693 Instead, a pointer to the entry with the new information should be
1694 placed in the old entry. Readers of this file should also sanity check
1695 older entries before relying on them blindly. Authors of new entries
1696 should write them with this in mind.
1700 When upgrading the boot ZFS pool to a new version, always follow
1703 1.) recompile and reinstall the ZFS boot loader and boot block
1704 (this is part of "make buildworld" and "make installworld")
1706 2.) update the ZFS boot block on your boot drive
1708 The following example updates the ZFS boot block on the first
1709 partition (freebsd-boot) of a GPT partitioned drive ada0:
1710 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1712 Non-boot pools do not need these updates.
1716 If you are updating from a prior version of FreeBSD (even one just
1717 a few days old), you should follow this procedure. It is the most
1718 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1720 make kernel-toolchain
1721 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1722 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1724 To test a kernel once
1725 ---------------------
1726 If you just want to boot a kernel once (because you are not sure
1727 if it works, or if you want to boot a known bad kernel to provide
1728 debugging information) run
1729 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1730 nextboot -k testkernel
1732 To rebuild everything and install it on the current system.
1733 -----------------------------------------------------------
1734 # Note: sometimes if you are running current you gotta do more than
1735 # is listed here if you are upgrading from a really old current.
1737 <make sure you have good level 0 dumps>
1739 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1740 make installkernel KERNCONF=YOUR_KERNEL_HERE
1742 <reboot in single user> [3]
1749 To cross-install current onto a separate partition
1750 --------------------------------------------------
1751 # In this approach we use a separate partition to hold
1752 # current's root, 'usr', and 'var' directories. A partition
1753 # holding "/", "/usr" and "/var" should be about 2GB in
1756 <make sure you have good level 0 dumps>
1759 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1760 <maybe newfs current's root partition>
1761 <mount current's root partition on directory ${CURRENT_ROOT}>
1762 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1763 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1764 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1765 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1766 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1767 <reboot into current>
1768 <do a "native" rebuild/install as described in the previous section>
1769 <maybe install compatibility libraries from ports/misc/compat*>
1773 To upgrade in-place from stable to current
1774 ----------------------------------------------
1775 <make sure you have good level 0 dumps>
1777 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1778 make installkernel KERNCONF=YOUR_KERNEL_HERE
1780 <reboot in single user> [3]
1787 Make sure that you've read the UPDATING file to understand the
1788 tweaks to various things you need. At this point in the life
1789 cycle of current, things change often and you are on your own
1790 to cope. The defaults can also change, so please read ALL of
1791 the UPDATING entries.
1793 Also, if you are tracking -current, you must be subscribed to
1794 freebsd-current@freebsd.org. Make sure that before you update
1795 your sources that you have read and understood all the recent
1796 messages there. If in doubt, please track -stable which has
1797 much fewer pitfalls.
1799 [1] If you have third party modules, such as vmware, you
1800 should disable them at this point so they don't crash your
1803 [3] From the bootblocks, boot -s, and then do
1808 adjkerntz -i # if CMOS is wall time
1809 Also, when doing a major release upgrade, it is required that
1810 you boot into single user mode to do the installworld.
1812 [4] Note: This step is non-optional. Failure to do this step
1813 can result in a significant reduction in the functionality of the
1814 system. Attempting to do it by hand is not recommended and those
1815 that pursue this avenue should read this file carefully, as well
1816 as the archives of freebsd-current and freebsd-hackers mailing lists
1817 for potential gotchas. The -U option is also useful to consider.
1818 See mergemaster(8) for more information.
1820 [5] Usually this step is a no-op. However, from time to time
1821 you may need to do this if you get unknown user in the following
1822 step. It never hurts to do it all the time. You may need to
1823 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1824 install) after the buildworld before this step if you last updated
1825 from current before 20130425 or from -stable before 20130430.
1827 [6] This only deletes old files and directories. Old libraries
1828 can be deleted by "make delete-old-libs", but you have to make
1829 sure that no program is using those libraries anymore.
1831 [8] In order to have a kernel that can run the 4.x binaries needed to
1832 do an installworld, you must include the COMPAT_FREEBSD4 option in
1833 your kernel. Failure to do so may leave you with a system that is
1834 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1835 required to run the 5.x binaries on more recent kernels. And so on
1836 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1838 Make sure that you merge any new devices from GENERIC since the
1839 last time you updated your kernel config file.
1841 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1842 "?=" instead of the "=" assignment operator, so that buildworld can
1843 override the CPUTYPE if it needs to.
1845 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1846 not on the command line, or in /etc/make.conf. buildworld will
1847 warn if it is improperly defined.
1850 This file contains a list, in reverse chronological order, of major
1851 breakages in tracking -current. It is not guaranteed to be a complete
1852 list of such breakages, and only contains entries since September 23, 2011.
1853 If you need to see UPDATING entries from before that date, you will need
1854 to fetch an UPDATING file from an older FreeBSD release.
1856 Copyright information:
1858 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1860 Redistribution, publication, translation and use, with or without
1861 modification, in full or in part, in any form or format of this
1862 document are permitted without further permission from the author.
1864 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1865 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1866 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1867 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1868 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1869 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1870 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1871 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1872 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1873 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1874 POSSIBILITY OF SUCH DAMAGE.
1876 Contact Warner Losh if you have any questions about your use of