1 Updating Information for FreeBSD stable/12 users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 20211103: p11 FreeBSD-EN-21:27.caroot
21 FreeBSD-EN-21:29.tzdata
23 Root certificate bundle update. [EN-21:27.caroot]
25 Fix kernel panic in vmci driver initialization. [EN-21:28.vmci]
27 Timezone database information update. [EN-21:29.tzdata]
29 20210824: p10 FreeBSD-EN-21:24.libcrypto
30 FreeBSD-EN-21:25.bhyve
31 FreeBSD-SA-21:13.bhyve
32 FreeBSD-SA-21:14.ggatec
33 FreeBSD-SA-21:15.libfetch
34 FreeBSD-SA-21:16.openssl
35 FreeBSD-SA-21:17.openssl
37 Fix OpenSSL 1.1.1e API functions not being exported. [EN-21:24.libcrypto]
39 Fix NVMe iovec construction for large IOs. [EN-21:25.bhyve]
41 Fix missing error handling in bhyve(8) device models. [SA-21:13.bhyve]
43 Fix remote code execution in ggatec(8). [SA-21:14.ggatec]
45 Fix libfetch out of bounds read. [SA-21:15.libfetch]
47 Fix multiple OpenSSL vulnerabilities. [SA-21:16.openssl]
49 Fix multiple vulnerabilities in OpenSSL. [SA-21:17.openssl]
51 20210629: p9 FreeBSD-EN-21:19.libcasper
52 FreeBSD-EN-21:22.linux_futex
54 libcasper assertion failures [EN-21:19.libcasper]
56 Linux compatibility layer futex(2) system call vulnerability [EN-21:22.linux_futex]
58 20210601: p8 FreeBSD-EN-21:17.libradius
60 Incorrect validation in rad_get_attr(3) [FreeBSD-EN-21:17.libradius]
62 20210526: p7 FreeBSD-EN-21:11.aesni
65 FreeBSD-SA-21:12.libradius
67 Race condition in aesni(4) encrypt-then-auth operations [FreeBSD-EN-21:11.aesni]
69 pms(4) data corruption [FreeBSD-EN-21:14.pms]
71 SMAP bypass [FreeBSD-SA-21:11.smap]
73 Missing message validation in libradius(3) [FreeBSD-SA-21:12.libradius]
75 20210406: p6 FreeBSD-EN-21:09.pf
78 FreeBSD-SA-21:09.accept_filter
79 FreeBSD-SA-21:10.jail_mount
81 net.pf.request_maxcount not settable from loader.conf(5) [EN-21:09.pf]
83 lldb abort on print command [EN-21:10.lldb]
85 Memory disclosure by stale virtual memory mapping [SA-21:08.vm]
87 Double free in accept_filter(9) socket configuration interface [SA-21:09.accept_filter]
89 Jail escape possible by mounting over jail root [SA-21:10.jail_mount]
91 20210325: p5 FreeBSD-SA-21:07.openssl
93 Fix multiple OpenSSL issues [SA-21:07.openssl]
95 20210223: p4 FreeBSD-SA-21:03.pam_login_access
96 FreeBSD-SA-21:04.jail_remove
97 FreeBSD-SA-21:05.jail_chdir
99 FreeBSD-EN-21:06.microcode
100 FreeBSD-EN-21:07.caroot
101 FreeBSD-EN-21:08.freebsd-update
103 login.access fails to apply rules [SA-21:03.pam_login_access]
105 jail_remove(2) fails to kill all jailed processes [SA-21:04.jail_remove]
107 jail_attach(2) relies on the caller to change the cwd [SA-21:05.jail_chdir]
109 Xen grant mapping error handling issues [SA-21:06.xen]
111 Boot-time microcode loading causes a boot hang [EN-21:06.microcode]
113 Root certificate bundle update [EN-21:07.caroot]
115 freebsd-update passwd regeneration [EN-21:08.freebsd-update]
117 20210128: p3 FreeBSD-EN-21:01.tzdata
118 FreeBSD-EN-21:03.vnet
120 FreeBSD-SA-21:01.fsdisclosure
121 FreeBSD-SA-21:02.xenoom
123 Update timezone database information [EN-21:01.tzdata]
125 Panic when destroying VNET and epair simultaneously [EN-21:03.vnet]
127 zfs recv fails to propagate snapshot deletion [EN-21:04.zfs]
129 Uninitialized file system kernel stack leaks [SA-21:01.fsdisclosure]
131 Xen guest-triggered out of memory [SA-21:02.xenoom]
133 20201208: p2 FreeBSD-SA-20:33.openssl
135 Fix OpenSSL NULL pointer de-reference. [SA-20:33.openssl]
137 20201201: p1 FreeBSD-EN-20:19.audit
138 FreeBSD-EN-20:20.tzdata
139 FreeBSD-EN-20:21.ipfw
140 FreeBSD-EN-20:22.callout
141 FreeBSD-SA-20:31.icmp6
142 FreeBSD-SA-20:32.rtsold
144 Fix execve/fexecve system call auditing. [EN-20:19.audit]
146 Update timezone database information. [EN-20:20.tzdata]
148 Fix uninitialized variable in ipfw. [EN-20:21.ipfw]
150 Fix race condition in callout CPU migration. [EN-20:22.callout]
152 Fix ICMPv6 use-after-free in error message handling. [SA-20:31.icmp6]
154 Fix multiple vulnerabilities in rtsold. [SA-20:32.rtsold]
159 20200915: p1 FreeBSD-SA-20:27.ure
160 FreeBSD-SA-20:28.bhyve_vmcs
161 FreeBSD-SA-20:29.bhyve_svm
162 FreeBSD-SA-20:30.ftpd
164 Fix ure device driver susceptible to packet-in-packet attack.
167 Fix bhyve privilege escalation via VMCS access. [SA-20:28.bhyve_vmcs]
169 Fix bhyve SVM guest escape. [SA-20:29.bhyve_svm]
171 Fix ftpd privilege escalation via ftpchroot. [SA-20:30.ftpd]
174 The make.conf(5) MALLOC_PRODUCTION variable, used for disabling and
175 enabling assertions and statistics gathering in malloc(3), has been
176 migrated to a src.conf(5) WITH/WITHOUT_MALLOC_PRODUCTION option.
178 On stable branches, WITH_MALLOC_PRODUCTION is set by default, which
179 means that malloc(3) has assertions and statistics gathering disabled,
180 for improved performance.
182 For backwards compatibility, the make.conf(5) MALLOC_PRODUCTION is still
183 honored, but it is now deprecated and undocumented.
186 The resume code now notifies devd with the 'kernel' system
187 rather than the old 'kern' subsystem to be consistent with
188 other use. The old notification will be created as well, but
189 will be removed prior to FreeBSD 14.0.
192 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
193 been upgraded to 10.0.1. Please see the 20141231 entry below for
194 information about prerequisites and upgrading, if you are not already
195 using clang 3.5.0 or higher.
198 read(2) of a directory fd is now rejected by default. root may
199 re-enable it for the entire system with the
200 security.bsd.allow_read_dir sysctl(8) MIB.
202 It may be advised to setup aliases for grep to default to `-d skip` if
203 commonly non-recursively grepping a list that includes directories and
204 the potential for the resulting stderr output is not tolerable. Example
205 aliases are now installed, commented out, in /root/.cshrc.
208 Upstream DTS from Linux 5.6 was merged and they now have the SID
209 and THS (Secure ID controller and THermal Sensor) node present.
210 The DTB overlays have now been removed from the tree for the H3/H5 and
211 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
212 deal with upstream DTS. If you are using those overlays you need to
213 remove them from loader.conf and update the DTBs on the FAT partition.
216 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
217 been upgraded to 10.0.0. Please see the 20141231 entry below for
218 information about prerequisites and upgrading, if you are not already
219 using clang 3.5.0 or higher.
222 The root certificates of the Mozilla CA Certificate Store have been
223 imported into the base system and can be managed with the certctl(8)
224 utility. If you have installed the security/ca_root_nss port or package
225 with the ETCSYMLINK option (the default), be advised that there may be
226 differences between those included in the port and those included in
227 base due to differences in nss branch used as well as general update
228 frequency. Note also that certctl(8) cannot manage certs in the
229 format used by the security/ca_root_nss port.
232 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
233 been upgraded to 9.0.1. Please see the 20141231 entry below for
234 information about prerequisites and upgrading, if you are not already
235 using clang 3.5.0 or higher.
238 The nctgpio and wbwd drivers have been moved to the superio bus.
239 If you have one of these drivers in a kernel configuration, then
240 you should add device superio to it. If you use one of these drivers
241 as a module and you compile a custom set of modules, then you should
242 add superio to the set.
245 The tap(4) driver has been folded into tun(4), and the module has been
246 renamed to tuntap. You should update any kld_list="if_tap" or
247 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
248 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
249 module instead, and "device tap" or "device tun" entries in kernel
250 config files to select the tuntap device instead.
253 ntpd no longer by default locks its pages in memory, allowing them
254 to be paged out by the kernel. Use rlimit memlock to restore
255 historic BSD behaviour. For example, add "rlimit memlock 32"
256 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
259 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
260 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
261 been removed from mount_fusefs(8). You can safely remove them from
262 your scripts, because they had no effect.
264 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
265 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
266 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
267 sysctls have been removed. If you felt the need to set any of them to
268 a non-default value, please tell asomers@FreeBSD.org why.
271 The fuse(4) module has been renamed to fusefs(4) for consistency with
272 other filesystems. You should update any kld_load="fuse" entries in
273 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
274 "options FUSE" enties in kernel config files.
277 Default permissions on the /var/account/acct file (and copies of it
278 rotated by periodic daily scripts) are changed from 0644 to 0640
279 because the file contains sensitive information that should not be
280 world-readable. If the /var/account directory must be created by
281 rc.d/accounting, the mode used is now 0750. Admins who use the
282 accounting feature are encouraged to change the mode of an existing
283 /var/account directory to 0750 or 0700.
286 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
287 been upgraded to 8.0.1. Please see the 20141231 entry below for
288 information about prerequisites and upgrading, if you are not already
289 using clang 3.5.0 or higher.
292 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
293 functionality needed for the RETPOLINE option should work properly
294 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
297 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
298 8.0.0. Please see the 20141231 entry below for information about
299 prerequisites and upgrading, if you are not already using clang 3.5.0
303 The RETPOLINE option produces non-functional ifunc-using binaries
304 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
305 Once Clang 8 is merged it may be enabled again.
308 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
309 7.0.1. Please see the 20141231 entry below for information about
310 prerequisites and upgrading, if you are not already using clang 3.5.0
314 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
315 compiled into your custom kernel, add 'device xz' statement to the
319 Iflib is no longer unconditionally compiled into the kernel. Drivers
320 using iflib and statically compiled into the kernel, now require
321 the 'device iflib' config option. For the same drivers loaded as
322 modules on kernels not having 'device iflib', the iflib.ko module
323 is loaded automatically.
326 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
327 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
328 servers that have vfs.nfsd.nfs_privport set will only allow mounts
329 from clients using a reserved port#. Since both the FreeBSD and Linux
330 NFSv4 clients use reserved port#s by default, this should not affect
334 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
335 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
336 it produces broken binaries when ifuncs are in use. Users needing
337 GNU ld should install the binutils port or package.
340 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
341 has been converted to a port (misc/ctm) and will be removed from
342 FreeBSD-13. A depreciation warning will be printed to stderr by
343 the ctm command, but the functionality will remain in base for all
347 The stable/12 branch has been created in subversion from head
351 Ports for the DRM modules have been simplified. Now, amd64 users should
352 just install the drm-kmod port. All others should install
355 Graphics hardware that's newer than about 2010 usually works with
356 drm-kmod. For hardware older than 2013, however, some users will need
357 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
358 than 2008 usually only works in drm-legacy-kmod. The graphics team can
359 only commit to hardware made since 2013 due to the complexity of the
360 market and difficulty to test all the older cards effectively. If you
361 have hardware supported by drm-kmod, you are strongly encouraged to use
362 that as you will get better support.
364 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
365 elsewhere, the drm and drm2 modules will be eliminated from the src base
366 soon (with a limited exception for arm). Please update to the package asap
367 and report any issues to x11@freebsd.org.
369 Generally, anybody using the drm*-kmod packages should add
370 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
371 cross-threading surprises, especially with automatic driver
372 loading from X11 startup. These will become the defaults in 13-current
376 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
377 custom kernel and module loading configuration files must be updated
378 accordingly. Moreover, interfaces previous presented as ixlvN to the
379 system are now exposed as iavfN and network configuration files must
380 be adjusted as necessary.
383 OpenSSL has been updated to version 1.1.1. This update included
384 additional various API changes througout the base system. It is
385 important to rebuild third-party software after upgrading. The value
386 of __FreeBSD_version has been bumped accordingly.
389 The legacy DRM modules and drivers have now been added to the loader's
390 module blacklist, in favor of loading them with kld_list in rc.conf(5).
391 The module blacklist may be overridden with the loader.conf(5)
392 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
396 The cam(4) based nda(4) driver will be used over nvd(4) by default on
397 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
398 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
399 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
403 Reproducible build mode is now on by default, in preparation for
404 FreeBSD 12.0. This eliminates build metadata such as the user,
405 host, and time from the kernel (and uname), unless the working tree
406 corresponds to a modified checkout from a version control system.
407 The previous behavior can be obtained by setting the /etc/src.conf
408 knob WITHOUT_REPRODUCIBLE_BUILD.
411 The Yarrow CSPRNG has been removed from the kernel as it has not been
412 supported by its designers since at least 2003. Fortuna has been the
413 default since FreeBSD-11.
416 devctl freeze/thaw have gone into the tree, the rc scripts have been
417 updated to use them and devmatch has been changed. You should update
418 kernel, userland and rc scripts all at the same time.
421 The default interpreter has been switched from 4th to Lua.
422 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
423 interpreter. If you have custom FORTH code you will need to set
424 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
425 src.conf for the build. This will create default hard links between
426 loader and loader_4th instead of loader and loader_lua, the new default.
427 If you are using UEFI it will create the proper hard link to loader.efi.
429 bhyve uses userboot.so. It remains 4th-only until some issues are solved
430 regarding coexisting with multiple versions of FreeBSD are resolved.
433 ls(1) now respects the COLORTERM environment variable used in other
434 systems and software to indicate that a colored terminal is both
435 supported and desired. If ls(1) is suddenly emitting colors, they may
436 be disabled again by either removing the unwanted COLORTERM from your
437 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
438 may not be observed in a future release.
441 The default pager for most commands has been changed to "less". To
442 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
446 The jedec_ts(4) driver has been removed. A superset of its functionality
447 is available in the jedec_dimm(4) driver, and the manpage for that
448 driver includes migration instructions. If you have "device jedec_ts"
449 in your kernel configuration file, it must be removed.
452 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
453 This should have no effect if the kernel is booted via BIOS/legacy boot.
454 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
455 has a buggy firmware that prevents a successful boot due to use of
459 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
460 support has been removed from the tree. These ports were
461 obsolete and/or known to be broken for many years.
464 loader.efi has been augmented to participate more fully in the
465 UEFI boot manager protocol. loader.efi will now look at the
466 BootXXXX environment variable to determine if a specific kernel
467 or root partition was specified. XXXX is derived from BootCurrent.
468 efibootmgr(8) manages these standard UEFI variables.
471 zfsloader's functionality has now been folded into loader.
472 zfsloader is no longer necessary once you've updated your
473 boot blocks. For a transition period, we will install a
474 hardlink for zfsloader to loader to allow a smooth transition
475 until the boot blocks can be updated (hard link because old
476 zfs boot blocks don't understand symlinks).
479 ARM64 now have efifb support, if you want to have serial console
480 on your arm64 board when an screen is connected and the bootloader
481 setup a frambuffer for us to use, just add :
485 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
486 an screen connected as the firmware will setup a framebuffer are that
487 u-boot will expose as an EFI framebuffer.
490 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
491 or take steps to update /etc/passwd before doing installworld on
492 existing systems. Do not skip the "mergemaster -Fp" step before
493 installworld, as described in the update procedures near the bottom
494 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
495 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
496 the ntp config file contain options that change file/dir locations.
497 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
498 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
499 taking steps to ensure that all required files/dirs are accessible
503 Big endian arm support has been removed.
506 The static environment setup in kernel configs is no longer mutually
507 exclusive with the loader(8) environment by default. In order to
508 restore the previous default behavior of disabling the loader(8)
509 environment if a static environment is present, you must specify
510 loader_env.disabled=1 in the static environment.
513 The ABI of syscalls used by management tools like sockstat and
514 netstat has been broken to allow 32-bit binaries to work on
515 64-bit kernels without modification. These programs will need
516 to match the kernel in order to function. External programs may
517 require minor modifications to accommodate a change of type in
518 structures from pointers to 64-bit virtual addresses.
521 On i386 and amd64 atomics are now inlined. Out of tree modules using
522 atomics will need to be rebuilt.
525 The '%I' format in the kern.corefile sysctl limits the number of
526 core files that a process can generate to the number stored in the
527 debug.ncores sysctl. The '%I' format is replaced by the single digit
528 index. Previously, if all indexes were taken the kernel would overwrite
529 only a core file with the highest index in a filename.
530 Currently the system will create a new core file if there is a free
531 index or if all slots are taken it will overwrite the oldest one.
534 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
535 6.0.1. Please see the 20141231 entry below for information about
536 prerequisites and upgrading, if you are not already using clang 3.5.0
540 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
541 needed to be changed to work with it. This change was made with r335763
542 and requires a mergemaster / etcupdate / etc to update the installed file.
545 r334930 changed the interface between the NFS modules, so they all
546 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
549 As of r334391 lld is the default amd64 system linker; it is installed
550 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
554 The kernel / userland interface for devinfo changed, so you'll
555 need a new kernel and userland as a pair for it to work (rebuilding
556 lib/libdevinfo is all that's required). devinfo and devmatch will
557 not work, but everything else will when there's a mismatch.
560 The on-disk format for hwpmc callchain records has changed to include
561 threadid corresponding to a given record. This changes the field offsets
562 and thus requires that libpmcstat be rebuilt before using a kernel
566 The vxge(4) driver has been removed. This driver was introduced into
567 HEAD one week before the Exar left the Ethernet market and is not
568 known to be used. If you have device vxge in your kernel config file
572 The amd64 kernel now requires a ld that supports ifunc to produce a
573 working kernel, either lld or a newer binutils. lld is built by default
574 on amd64, and the 'buildkernel' target uses it automatically. However,
575 it is not the default linker, so building the kernel the traditional
576 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
577 binutils port/package). lld will soon be default, and this requirement
580 NOTE: As of r334391 lld is the default system linker on amd64, and no
581 workaround is necessary.
584 The nxge(4) driver has been removed. This driver was for PCI-X 10g
585 cards made by s2io/Neterion. The company was aquired by Exar and
586 no longer sells or supports Ethernet products. If you have device
587 nxge in your kernel config file it must be removed.
590 The tz database (tzdb) has been updated to 2018e. This version more
591 correctly models time stamps in time zones with negative DST such as
592 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
593 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
594 time zone abbreviations and the tm_isdst flag.
597 The ixgb(4) driver has been removed. This driver was for an early and
598 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
599 quickly shifted to the long lived ixgbe family. If you have device
600 ixgb in your kernel config file it must be removed.
603 The lmc(4) driver has been removed. This was a WAN interface
604 card that was already reportedly rare in 2003, and had an ambiguous
605 license. If you have device lmc in your kernel config file it must
609 Support for Arcnet networks has been removed. If you have device
610 arcnet or device cm in your kernel config file they must be
614 Support for FDDI networks has been removed. If you have device
615 fddi or device fpa in your kernel config file they must be
619 In addition to supporting RFC 3164 formatted messages, the
620 syslogd(8) service is now capable of parsing RFC 5424 formatted
621 log messages. The main benefit of using RFC 5424 is that clients
622 may now send log messages with timestamps containing year numbers,
623 microseconds and time zone offsets.
625 Similarly, the syslog(3) C library function has been altered to
626 send RFC 5424 formatted messages to the local system logging
627 daemon. On systems using syslogd(8), this change should have no
628 negative impact, as long as syslogd(8) and the C library are
629 updated at the same time. On systems using a different system
630 logging daemon, it may be necessary to make configuration
631 adjustments, depending on the software used.
633 When using syslog-ng, add the 'syslog-protocol' flag to local
634 input sources to enable parsing of RFC 5424 formatted messages:
637 unix-dgram("/var/run/log" flags(syslog-protocol));
640 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
641 of the 'imuxsock' module to let messages be processed by the
642 regular RFC 3164/5424 parsing pipeline:
644 module(load="imuxsock" SysSock.UseSpecialParser="off")
646 Do note that these changes only affect communication between local
647 applications and syslogd(8). The format that syslogd(8) uses to
648 store messages on disk or forward messages to other systems
649 remains unchanged. syslogd(8) still uses RFC 3164 for these
650 purposes. Options to customize this behaviour will be added in the
651 future. Utilities that process log files stored in /var/log are
652 thus expected to continue to function as before.
654 __FreeBSD_version has been incremented to 1200061 to denote this
658 Support for token ring networks has been removed. If you
659 have "device token" in your kernel config you should remove
660 it. No device drivers supported token ring.
663 makefs was modified to be able to tag ISO9660 El Torito boot catalog
664 entries as EFI instead of overloading the i386 tag as done previously.
665 The amd64 mkisoimages.sh script used to build amd64 ISO images for
666 release was updated to use this. This may mean that makefs must be
667 updated before "make cdrom" can be run in the release directory. This
668 should be as simple as:
670 $ cd $SRCDIR/usr.sbin/makefs
671 $ make depend all install
674 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
675 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
676 Co-existance for the transition period will come shortly. Booting is a
677 complex environment and test coverage for Lua-enabled loaders has been
678 thin, so it would be prudent to assume it might not work and make
679 provisions for backup boot methods.
682 devmatch functionality has been turned on in devd. It will automatically
683 load drivers for unattached devices. This may cause unexpected drivers to
684 be loaded. Please report any problems to current@ and imp@freebsd.org.
687 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
688 6.0.0. Please see the 20141231 entry below for information about
689 prerequisites and upgrading, if you are not already using clang 3.5.0
693 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
694 This means it is used to link the kernel and userland libraries and
695 executables, but is not yet installed as /usr/bin/ld by default.
697 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
698 WITHOUT_LLD_BOOTSTRAP=yes
701 On i386, pmtimer has been removed. Its functionality has been folded
702 into apm. It was a no-op on ACPI in current for a while now (but was still
703 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
704 from kernel config files.
707 The use of RSS hash from the network card aka flowid has been
708 disabled by default for lagg(4) as it's currently incompatible with
709 the lacp and loadbalance protocols.
711 This can be re-enabled by setting the following in loader.conf:
712 net.link.lagg.default_use_flowid="1"
715 The SW_WATCHDOG option is no longer necessary to enable the
716 hardclock-based software watchdog if no hardware watchdog is
717 configured. As before, SW_WATCHDOG will cause the software
718 watchdog to be enabled even if a hardware watchdog is configured.
721 r326887 fixes the issue described in the 20171214 UPDATING entry.
722 r326888 flips the switch back to building GELI support always.
725 r362593 broke ZFS + GELI support for reasons unknown. However,
726 it also broke ZFS support generally, so GELI has been turned off
727 by default as the lesser evil in r326857. If you boot off ZFS and/or
728 GELI, it might not be a good time to update.
731 PowerPC users must update loader(8) by rebuilding world before
732 installing a new kernel, as the protocol connecting them has
733 changed. Without the update, loader metadata will not be passed
734 successfully to the kernel and users will have to enter their
735 root partition at the kernel mountroot prompt to continue booting.
736 Newer versions of loader can boot old kernels without issue.
739 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
740 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
741 to WITH/OUT_LOADER_GELI.
744 The naive and non-compliant support of posix_fallocate(2) in ZFS
745 has been removed as of r325320. The system call now returns EINVAL
746 when used on a ZFS file. Although the new behavior complies with the
747 standard, some consumers are not prepared to cope with it.
748 One known victim is lld prior to r325420.
751 Building in a FreeBSD src checkout will automatically create object
752 directories now rather than store files in the current directory if
753 'make obj' was not ran. Calling 'make obj' is no longer necessary.
754 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
755 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
759 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
760 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
761 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
762 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
763 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
764 The UNIFIED_OBJDIR option is a transitional feature that will be
765 removed for 12.0 release; please migrate to the new format for any
766 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
767 than hardcoding paths.
770 The native-xtools target no longer installs the files by default to the
771 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
772 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
775 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
776 options are changing from controlling the build if defined / undefined
777 to controlling the build with explicit 'yes' or 'no' values. They will
778 shift to WITH/WITHOUT options to match other options in the system.
781 libstand has turned into a private library for sys/boot use only.
782 It is no longer supported as a public interface outside of sys/boot.
785 The arm port has split armv6 into armv6 and armv7. armv7 is now
786 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
787 and are running a kernel from before r324363, you will need to add
788 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
791 When building multiple kernels using KERNCONF, non-existent KERNCONF
792 files will produce an error and buildkernel will fail. Previously
793 missing KERNCONF files silently failed giving no indication as to
794 why, only to subsequently discover during installkernel that the
795 desired kernel was never built in the first place.
798 The default serial number format for CTL LUNs has changed. This will
799 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
800 or iSCSI clients care about their LUNs' serial numbers. Users who
801 require serial number stability should hardcode serial numbers in
805 For 32-bit arm compiled for hard-float support, soft-floating point
806 binaries now always get their shared libraries from
807 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
808 /usr/libsoft also existed). Only users with a hard-float ld.so, but
809 soft-float everything else should be affected.
812 The geli password typed at boot is now hidden. To restore the previous
813 behavior, see geli(8) for configuration options.
816 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
817 sysctl values. Minor nit, but requires a rebuild of both world/kernel
821 "make check" behavior (made in ^/head@r295380) has been changed to
822 execute from a limited sandbox, as opposed to executing from
826 - The "beforecheck" and "aftercheck" targets are now specified.
827 - ${CHECKDIR} (added in commit noted above) has been removed.
828 - Legacy behavior can be enabled by setting
829 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
831 If the limited sandbox mode is enabled, "make check" will execute
832 "make distribution", then install, execute the tests, and clean up the
833 sandbox if successful.
835 The "make distribution" and "make install" targets are typically run as
836 root to set appropriate permissions and ownership at installation time.
837 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
838 environment if executing "make check" with limited sandbox mode using
839 an unprivileged user.
842 Since the switch to GPT disk labels, fsck for UFS/FFS has been
843 unable to automatically find alternate superblocks. As of r322297,
844 the information needed to find alternate superblocks has been
845 moved to the end of the area reserved for the boot block.
846 Filesystems created with a newfs of this vintage or later
847 will create the recovery information. If you have a filesystem
848 created prior to this change and wish to have a recovery block
849 created for your filesystem, you can do so by running fsck in
850 foreground mode (i.e., do not use the -p or -y options). As it
851 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
852 to which you should answer yes.
855 As of r321665, an NFSv4 server configuration that services
856 Kerberos mounts or clients that do not support the uid/gid in
857 owner/owner_group string capability, must explicitly enable
858 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
859 machine's /etc/rc.conf file.
862 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
863 Please see the 20141231 entry below for information about prerequisites
864 and upgrading, if you are not already using clang 3.5.0 or higher.
867 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
868 r-commands (rlogin, rsh, etc.) to be built with the base system.
871 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
872 a very major ABI incompatible change, so users of FreeBSD/powerpc must
873 be careful when performing source upgrades. It is best to run
874 'make installworld' from an alternate root system, either a live
875 CD/memory stick, or a temporary root partition. Additionally, all ports
876 must be recompiled. powerpc64 is largely unaffected, except in the case
877 of 32-bit compatibility. All 32-bit binaries will be affected.
880 Forward compatibility for the "ino64" project have been committed. This
881 will allow most new binaries to run on older kernels in a limited
882 fashion. This prevents many of the common foot-shooting actions in the
883 upgrade as well as the limited ability to roll back the kernel across
884 the ino64 upgrade. Complicated use cases may not work properly, though
885 enough simpler ones work to allow recovery in most situations.
888 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
889 if you require the GPL compiler.
892 The internal ABI used for communication between the NFS kernel modules
893 was changed by r320085, so __FreeBSD_version was bumped to
894 ensure all the NFS related modules are updated together.
897 The ABI of struct event was changed by extending the data
898 member to 64bit and adding ext fields. For upgrade, same
899 precautions as for the entry 20170523 "ino64" must be
903 The GNU roff toolchain has been removed from base. To render manpages
904 which are not supported by mandoc(1), man(1) can fallback on GNU roff
905 from ports (and recommends to install it).
906 To render roff(7) documents, consider using GNU roff from ports or the
907 heirloom doctools roff toolchain from ports via pkg install groff or
908 via pkg install heirloom-doctools.
911 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
912 smaller runtime footprint builds. This is useful for embedded systems
913 which only require one chipset support.
915 If you load it as a module, make sure this is in /boot/loader.conf:
919 This will load the HAL, all chip/RF backends and if_ath_pci.
920 If you have if_ath_pci in /boot/loader.conf, ensure it is after
921 if_ath or it will not load any HAL chipset support.
923 If you want to selectively load things (eg on ye cheape ARM/MIPS
924 platforms where RAM is at a premium) you should:
927 * load the chip modules in question
928 * load ath_rate, ath_dfs
930 * load if_ath_pci and/or if_ath_ahb depending upon your particular
931 bus bind type - this is where probe/attach is done.
933 For further comments/feedback, poke adrian@ .
936 The "ino64" 64-bit inode project has been committed, which extends
937 a number of types to 64 bits. Upgrading in place requires care and
938 adherence to the documented upgrade procedure.
940 If using a custom kernel configuration ensure that the
941 COMPAT_FREEBSD11 option is included (as during the upgrade the
942 system will be running the ino64 kernel with the existing world).
944 For the safest in-place upgrade begin by removing previous build
945 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
946 full procedure documented below under the heading "To rebuild
947 everything and install it on the current system." Specifically,
948 a reboot is required after installing the new kernel before
952 The NATM framework including the en(4), fatm(4), hatm(4), and
953 patm(4) devices has been removed. Consumers should plan a
954 migration before the end-of-life date for FreeBSD 11.
957 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
958 diff has not been implemented, if those are needed a newer version of
959 GNU diff is available via the diffutils package under the gdiff name.
962 As of r316810 for ipfilter, keep frags is no longer assumed when
963 keep state is specified in a rule. r316810 aligns ipfilter with
964 documentation in man pages separating keep frags from keep state.
965 This allows keep state to be specified without forcing keep frags
966 and allows keep frags to be specified independently of keep state.
967 To maintain previous behaviour, also specify keep frags with
968 keep state (as documented in ipf.conf.5).
971 arm64 builds now use the base system LLD 4.0.0 linker by default,
972 instead of requiring that the aarch64-binutils port or package be
973 installed. To continue using aarch64-binutils, set
974 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
977 The UDP optimization in entry 20160818 that added the sysctl
978 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
979 packets will no longer be treated as L3 broadcast packets.
982 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
983 use any explicitly assigned loopback address available in the jail
984 instead of using the first assigned address of the jail.
987 The ctl.ko module no longer implements the iSCSI target frontend:
988 cfiscsi.ko does instead.
990 If building cfiscsi.ko as a kernel module, the module can be loaded
991 via one of the following methods:
992 - `cfiscsi_load="YES"` in loader.conf(5).
993 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
994 - ctladm(8)/ctld(8), when compiled with iSCSI support
995 (`WITH_ISCSI=yes` in src.conf(5))
997 Please see cfiscsi(4) for more details.
1000 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1001 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1002 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1003 missing, but mmcsd.ko now will refuse to load if it is incompatible
1007 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1008 If you have used named states in the firewall rules, you need to modify
1009 them after installworld and before rebooting. Now named states must
1010 be prefixed with colon.
1013 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1014 removed as the userland we provide cannot use them. The KMS version
1015 (sys/dev/drm2) supports the same hardware.
1018 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1019 Please see the 20141231 entry below for information about prerequisites
1020 and upgrading, if you are not already using clang 3.5.0 or higher.
1023 The code that provides support for ZFS .zfs/ directory functionality
1024 has been reimplemented. It's not possible now to create a snapshot
1025 by mkdir under .zfs/snapshot/. That should be the only user visible
1029 EISA bus support has been removed. The WITH_EISA option is no longer
1033 MCA bus support has been removed.
1036 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1037 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1040 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1041 the em(4) driver conforms to iflib specifications.
1044 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1045 IFLIB. If you have a custom kernel configuration that excludes em(4)
1046 but you use igb(4), you need to re-add em(4) to your custom configuration.
1049 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1050 Please see the 20141231 entry below for information about prerequisites
1051 and upgrading, if you are not already using clang 3.5.0 or higher.
1054 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1055 Please see the 20141231 entry below for information about prerequisites
1056 and upgrading, if you are not already using clang 3.5.0 or higher.
1059 The layout of the pmap structure has changed for powerpc to put the pmap
1060 statistics at the front for all CPU variations. libkvm(3) and all tools
1061 that link against it need to be recompiled.
1064 isl(4) and cyapa(4) drivers now require a new driver,
1065 chromebook_platform(4), to work properly on Chromebook-class hardware.
1066 On other types of hardware the drivers may need to be configured using
1067 device hints. Please see the corresponding manual pages for details.
1070 The urtwn(4) driver was merged into rtwn(4) and now consists of
1071 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1073 Also, firmware for RTL8188CE was renamed due to possible name
1074 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1077 GNU rcs has been removed from base. It is available as packages:
1078 - rcs: Latest GPLv3 GNU rcs version.
1079 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1083 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1084 modules now requires that the kernel configuration contain the
1085 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1088 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1089 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1092 Relocatable object files with the extension of .So have been renamed
1093 to use an extension of .pico instead. The purpose of this change is
1094 to avoid a name clash with shared libraries on case-insensitive file
1095 systems. On those file systems, foo.So is the same file as foo.so.
1098 GNU rcs has been turned off by default. It can (temporarily) be built
1099 again by adding WITH_RCS knob in src.conf.
1100 Otherwise, GNU rcs is available from packages:
1101 - rcs: Latest GPLv3 GNU rcs version.
1102 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1105 The backup_uses_rcs functionality has been removed from rc.subr.
1108 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1109 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1110 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1111 QUEUE_MACRO_DEBUG behavior.
1114 r304787 changed some ioctl interfaces between the iSCSI userspace
1115 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1116 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1120 The UDP receive code has been updated to only treat incoming UDP
1121 packets that were addressed to an L2 broadcast address as L3
1122 broadcast packets. It is not expected that this will affect any
1123 standards-conforming UDP application. The new behaviour can be
1124 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1128 Remove the openbsd_poll system call.
1129 __FreeBSD_version has been bumped because of this.
1132 The stable/11 branch has been created from head@r302406.
1135 The libc stub for the pipe(2) system call has been replaced with
1136 a wrapper that calls the pipe2(2) system call and the pipe(2)
1137 system call is now only implemented by the kernels that include
1138 "options COMPAT_FREEBSD10" in their config file (this is the
1139 default). Users should ensure that this option is enabled in
1140 their kernel or upgrade userspace to r302092 before upgrading their
1144 CAM will now strip leading spaces from SCSI disks' serial numbers.
1145 This will affect users who create UFS filesystems on SCSI disks using
1146 those disk's diskid device nodes. For example, if /etc/fstab
1147 previously contained a line like
1148 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1149 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1150 transforms like gmirror may also be affected. ZFS users should
1154 The bitstring(3) API has been updated with new functionality and
1155 improved performance. But it is binary-incompatible with the old API.
1156 Objects built with the new headers may not be linked against objects
1157 built with the old headers.
1160 The brk and sbrk functions have been removed from libc on arm64.
1161 Binutils from ports has been updated to not link to these
1162 functions and should be updated to the latest version before
1163 installing a new libc.
1166 The armv6 port now defaults to hard float ABI. Limited support
1167 for running both hardfloat and soft float on the same system
1168 is available using the libraries installed with -DWITH_LIBSOFT.
1169 This has only been tested as an upgrade path for installworld
1170 and packages may fail or need manual intervention to run. New
1171 packages will be needed.
1173 To update an existing self-hosted armv6hf system, you must add
1174 TARGET_ARCH=armv6 on the make command line for both the build
1175 and the install steps.
1178 Kernel modules compiled outside of a kernel build now default to
1179 installing to /boot/modules instead of /boot/kernel. Many kernel
1180 modules built this way (such as those in ports) already overrode
1181 KMODDIR explicitly to install into /boot/modules. However,
1182 manually building and installing a module from /sys/modules will
1183 now install to /boot/modules instead of /boot/kernel.
1186 The CAM I/O scheduler has been committed to the kernel. There should be
1187 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1188 list of known rogues that claim support for this but actually corrupt
1189 data is believed to be complete, be on the lookout for data
1190 corruption. The known rogue list is believed to be complete:
1192 o Crucial MX100, M550 drives with MU01 firmware.
1193 o Micron M510 and M550 drives with MU01 firmware.
1194 o Micron M500 prior to MU07 firmware
1195 o Samsung 830, 840, and 850 all firmwares
1196 o FCCT M500 all firmwares
1198 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1199 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1200 updated firmware. Black listed drives will work correctly because these
1201 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1202 this list is the same as found in Linux, it's believed there are no
1203 other rogues in the market place. All other models from the above
1206 To be safe, if you are at all concerned, you can quirk each of your
1207 drives to prevent NCQ from being sent by setting:
1208 kern.cam.ada.X.quirks="0x2"
1209 in loader.conf. If the drive requires the 4k sector quirk, set the
1210 quirks entry to 0x3.
1213 The FAST_DEPEND build option has been removed and its functionality is
1214 now the one true way. The old mkdep(1) style of 'make depend' has
1215 been removed. See 20160311 for further details.
1218 Resource range types have grown from unsigned long to uintmax_t. All
1219 drivers, and anything using libdevinfo, need to be recompiled.
1222 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1223 builds. It no longer runs mkdep(1) during 'make depend', and the
1224 'make depend' stage can safely be skipped now as it is auto ran
1225 when building 'make all' and will generate all SRCS and DPSRCS before
1226 building anything else. Dependencies are gathered at compile time with
1227 -MF flags kept in separate .depend files per object file. Users should
1228 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1229 stale .depend files.
1232 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1233 kernel modules. Therefore, if you load any kernel modules at boot time,
1234 please install the boot loaders after you install the kernel, but before
1238 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1239 make installkernel KERNCONF=YOUR_KERNEL_HERE
1240 make -C sys/boot install
1241 <reboot in single user>
1243 Then follow the usual steps, described in the General Notes section,
1247 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1248 see the 20141231 entry below for information about prerequisites and
1249 upgrading, if you are not already using clang 3.5.0 or higher.
1252 The AIO subsystem is now a standard part of the kernel. The
1253 VFS_AIO kernel option and aio.ko kernel module have been removed.
1254 Due to stability concerns, asynchronous I/O requests are only
1255 permitted on sockets and raw disks by default. To enable
1256 asynchronous I/O requests on all file types, set the
1257 vfs.aio.enable_unsafe sysctl to a non-zero value.
1260 The ELF object manipulation tool objcopy is now provided by the
1261 ELF Tool Chain project rather than by GNU binutils. It should be a
1262 drop-in replacement, with the addition of arm64 support. The
1263 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1264 to obtain the GNU version if necessary.
1267 Building ZFS pools on top of zvols is prohibited by default. That
1268 feature has never worked safely; it's always been prone to deadlocks.
1269 Using a zvol as the backing store for a VM guest's virtual disk will
1270 still work, even if the guest is using ZFS. Legacy behavior can be
1271 restored by setting vfs.zfs.vol.recursive=1.
1274 The NONE and HPN patches has been removed from OpenSSH. They are
1275 still available in the security/openssh-portable port.
1278 With the addition of ypldap(8), a new _ypldap user is now required
1279 during installworld. "mergemaster -p" can be used to add the user
1280 prior to installworld, as documented in the handbook.
1283 The tftp loader (pxeboot) now uses the option root-path directive. As a
1284 consequence it no longer looks for a pxeboot.4th file on the tftp
1285 server. Instead it uses the regular /boot infrastructure as with the
1289 The code to start recording plug and play data into the modules has
1290 been committed. While the old tools will properly build a new kernel,
1291 a number of warnings about "unknown metadata record 4" will be produced
1292 for an older kldxref. To avoid such warnings, make sure to rebuild
1293 the kernel toolchain (or world). Make sure that you have r292078 or
1294 later when trying to build 292077 or later before rebuilding.
1297 Debug data files are now built by default with 'make buildworld' and
1298 installed with 'make installworld'. This facilitates debugging but
1299 requires more disk space both during the build and for the installed
1300 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1304 r291527 changed the internal interface between the nfsd.ko and
1305 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1306 __FreeBSD_version has been bumped because of this.
1309 Add support for unicode collation strings leads to a change of
1310 order of files listed by ls(1) for example. To get back to the old
1311 behaviour, set LC_COLLATE environment variable to "C".
1313 Databases administrators will need to reindex their databases given
1314 collation results will be different.
1316 Due to a bug in install(1) it is recommended to remove the ancient
1317 locales before running make installworld.
1319 rm -rf /usr/share/locale/*
1322 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1323 libcrypto.so.7 or libssl.so.7 must be recompiled.
1326 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1327 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1328 should be replaced with isp_2400 and isp_2500 modules respectively.
1331 The build previously allowed using 'make -n' to not recurse into
1332 sub-directories while showing what commands would be executed, and
1333 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1334 and 'make -N' will not.
1337 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1338 and etcupdate will now use this file. A custom sendmail.cf is now
1339 updated via this mechanism rather than via installworld. If you had
1340 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1341 want to remove the exclusion or change it to "always install".
1342 /etc/mail/sendmail.cf is now managed the same way regardless of
1343 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1344 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1347 Compatibility shims for legacy ATA device names have been removed.
1348 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1349 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1350 environment variables, /dev/ad* and /dev/ar* symbolic links.
1353 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1354 Please see the 20141231 entry below for information about prerequisites
1355 and upgrading, if you are not already using clang 3.5.0 or higher.
1358 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1359 and renamed from .symbols to .debug. This reduces the size requirements
1360 on the boot partition or file system and provides consistency with
1361 userland debug files.
1363 When using the supported kernel installation method the
1364 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1365 as is done with /boot/kernel.
1367 Developers wishing to maintain the historical behavior of installing
1368 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1371 The wireless drivers had undergone changes that remove the 'parent
1372 interface' from the ifconfig -l output. The rc.d network scripts
1373 used to check presence of a parent interface in the list, so old
1374 scripts would fail to start wireless networking. Thus, etcupdate(3)
1375 or mergemaster(8) run is required after kernel update, to update your
1376 rc.d scripts in /etc.
1379 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1380 These configurations are now automatically interpreted as
1381 'scrub fragment reassemble'.
1384 Kernel-loadable modules for the random(4) device are back. To use
1385 them, the kernel must have
1388 options RANDOM_LOADABLE
1390 kldload(8) can then be used to load random_fortuna.ko
1391 or random_yarrow.ko. Please note that due to the indirect
1392 function calls that the loadable modules need to provide,
1393 the build-in variants will be slightly more efficient.
1395 The random(4) kernel option RANDOM_DUMMY has been retired due to
1396 unpopularity. It was not all that useful anyway.
1399 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1400 Control over building the ELF Tool Chain tools is now provided by
1401 the WITHOUT_TOOLCHAIN knob.
1404 The polarity of Pulse Per Second (PPS) capture events with the
1405 uart(4) driver has been corrected. Prior to this change the PPS
1406 "assert" event corresponded to the trailing edge of a positive PPS
1407 pulse and the "clear" event was the leading edge of the next pulse.
1409 As the width of a PPS pulse in a typical GPS receiver is on the
1410 order of 1 millisecond, most users will not notice any significant
1411 difference with this change.
1413 Anyone who has compensated for the historical polarity reversal by
1414 configuring a negative offset equal to the pulse width will need to
1415 remove that workaround.
1418 The default group assigned to /dev/dri entries has been changed
1419 from 'wheel' to 'video' with the id of '44'. If you want to have
1420 access to the dri devices please add yourself to the video group
1423 # pw groupmod video -m $USER
1426 The menu.rc and loader.rc files will now be replaced during
1427 upgrades. Please migrate local changes to menu.rc.local and
1428 loader.rc.local instead.
1431 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1432 strings and strip have been removed. The src.conf(5) knob
1433 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1436 As ZFS requires more kernel stack pages than is the default on some
1437 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1438 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1440 Please consider using 'options KSTACK_PAGES=X' where X is greater
1441 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1444 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1445 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1446 default, i.e., they will not contain "::". For example, instead
1447 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1448 to have a more specific match, such as different map entries for
1449 IPv6:0:0 vs IPv6:0. This change requires that configuration
1450 data (including maps, files, classes, custom ruleset, etc.) must
1451 use the same format, so make certain such configuration data is
1452 upgrading. As a very simple check search for patterns like
1453 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1454 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1455 the cf option UseCompressedIPv6Addresses.
1458 The default kernel entropy-processing algorithm is now
1459 Fortuna, replacing Yarrow.
1461 Assuming you have 'device random' in your kernel config
1462 file, the configurations allow a kernel option to override
1463 this default. You may choose *ONE* of:
1465 options RANDOM_YARROW # Legacy /dev/random algorithm.
1466 options RANDOM_DUMMY # Blocking-only driver.
1468 If you have neither, you get Fortuna. For most people,
1469 read no further, Fortuna will give a /dev/random that works
1470 like it always used to, and the difference will be irrelevant.
1472 If you remove 'device random', you get *NO* kernel-processed
1473 entropy at all. This may be acceptable to folks building
1474 embedded systems, but has complications. Carry on reading,
1475 and it is assumed you know what you need.
1477 *PLEASE* read random(4) and random(9) if you are in the
1478 habit of tweaking kernel configs, and/or if you are a member
1479 of the embedded community, wanting specific and not-usual
1480 behaviour from your security subsystems.
1482 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1483 random', you will NOT have a functioning /dev/random, and
1484 many cryptographic features will not work, including SSH.
1485 You may also find strange behaviour from the random(3) set
1486 of library functions, in particular sranddev(3), srandomdev(3)
1487 and arc4random(3). The reason for this is that the KERN_ARND
1488 sysctl only returns entropy if it thinks it has some to
1489 share, and with RANDOM_DUMMY or no 'device random' this
1493 An additional fix for the issue described in the 20150614 sendmail
1494 entry below has been committed in revision 284717.
1497 FreeBSD's old make (fmake) has been removed from the system. It is
1498 available as the devel/fmake port or via pkg install fmake.
1501 The fix for the issue described in the 20150614 sendmail entry
1502 below has been committed in revision 284436. The work
1503 around described in that entry is no longer needed unless the
1504 default setting is overridden by a confDH_PARAMETERS configuration
1505 setting of '5' or pointing to a 512 bit DH parameter file.
1508 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1509 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1510 and devel/kyua to version 0.20+ and adjust any calling code to work
1511 with Kyuafile and kyua.
1514 The import of openssl to address the FreeBSD-SA-15:10.openssl
1515 security advisory includes a change which rejects handshakes
1516 with DH parameters below 768 bits. sendmail releases prior
1517 to 8.15.2 (not yet released), defaulted to a 512 bit
1518 DH parameter setting for client connections. To work around
1519 this interoperability, sendmail can be configured to use a
1520 2048 bit DH parameter by:
1522 1. Edit /etc/mail/`hostname`.mc
1523 2. If a setting for confDH_PARAMETERS does not exist or
1524 exists and is set to a string beginning with '5',
1525 replace it with '2'.
1526 3. If a setting for confDH_PARAMETERS exists and is set to
1527 a file path, create a new file with:
1528 openssl dhparam -out /path/to/file 2048
1529 4. Rebuild the .cf file:
1530 cd /etc/mail/; make; make install
1531 5. Restart sendmail:
1532 cd /etc/mail/; make restart
1534 A sendmail patch is coming, at which time this file will be
1538 Generation of legacy formatted entries have been disabled by default
1539 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1540 entries were converted to use the new format by default when the new,
1541 machine independent format have been added and supported since FreeBSD
1544 Please see the pwd_mkdb(8) manual page for further details.
1547 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1548 20141231 entry below for information about prerequisites and upgrading,
1549 if you are not already using 3.5.0 or higher.
1552 TI platform code switched to using vendor DTS files and this update
1553 may break existing systems running on Beaglebone, Beaglebone Black,
1556 - dtb files should be regenerated/reinstalled. Filenames are the
1557 same but content is different now
1558 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1559 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1560 addressing scheme is now pin 25 on /dev/gpioc3.
1561 - Pandaboard: /etc/ttys should be updated, serial console device is
1562 now /dev/ttyu2, not /dev/ttyu0
1565 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1566 If you need the GNU extension from groff soelim(1), install groff
1567 from package: pkg install groff, or via ports: textproc/groff.
1570 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1571 defined in symlink(7); previously symlinks were silently ignored.
1574 The const qualifier has been removed from iconv(3) to comply with
1575 POSIX. The ports tree is aware of this from r384038 onwards.
1578 Libraries specified by LIBADD in Makefiles must have a corresponding
1579 DPADD_<lib> variable to ensure correct dependencies. This is now
1580 enforced in src.libnames.mk.
1583 From legacy ata(4) driver was removed support for SATA controllers
1584 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1585 Kernel modules ataahci and ataadaptec were removed completely,
1586 replaced by ahci and mvs modules respectively.
1589 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1590 the 20141231 entry below for information about prerequisites and
1591 upgrading, if you are not already using 3.5.0 or higher.
1594 The 32-bit PowerPC kernel has been changed to a position-independent
1595 executable. This can only be booted with a version of loader(8)
1596 newer than January 31, 2015, so make sure to update both world and
1597 kernel before rebooting.
1600 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1601 but before r278950, the RNG was not seeded properly. Immediately
1602 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1603 ssh keys or openssl keys) that were generated w/ a kernel from that
1604 range. This does not affect programs that directly used /dev/random
1605 or /dev/urandom. All userland uses of arc4random(3) are affected.
1608 The autofs(4) ABI was changed in order to restore binary compatibility
1609 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1610 with the new kernel.
1613 The powerpc64 kernel has been changed to a position-independent
1614 executable. This can only be booted with a new version of loader(8),
1615 so make sure to update both world and kernel before rebooting.
1618 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1619 only release, no new features have been added. Please see the 20141231
1620 entry below for information about prerequisites and upgrading, if you
1621 are not already using 3.5.0.
1624 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1625 taken from the ELF Tool Chain project rather than GNU binutils. They
1626 should be drop-in replacements, with the addition of arm64 support.
1627 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1628 binutils tools, if necessary. See 20150805 for updated information.
1631 The default Unbound configuration now enables remote control
1632 using a local socket. Users who have already enabled the
1633 local_unbound service should regenerate their configuration
1634 by running "service local_unbound setup" as root.
1637 The GNU texinfo and GNU info pages have been removed.
1638 To be able to view GNU info pages please install texinfo from ports.
1641 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1643 As of this release, a prerequisite for building clang, llvm and lldb is
1644 a C++11 capable compiler and C++11 standard library. This means that to
1645 be able to successfully build the cross-tools stage of buildworld, with
1646 clang as the bootstrap compiler, your system compiler or cross compiler
1647 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1648 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1651 On any standard FreeBSD 10.x or 11.x installation, where clang and
1652 libc++ are on by default (that is, on x86 or arm), this should work out
1655 On 9.x installations where clang is enabled by default, e.g. on x86 and
1656 powerpc, libc++ will not be enabled by default, so libc++ should be
1657 built (with clang) and installed first. If both clang and libc++ are
1658 missing, build clang first, then use it to build libc++.
1660 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1661 the instructions for 9.x above.
1663 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1664 default, and do not build clang.
1666 Many embedded systems are resource constrained, and will not be able to
1667 build clang in a reasonable time, or in some cases at all. In those
1668 cases, cross building bootable systems on amd64 is a workaround.
1670 This new version of clang introduces a number of new warnings, of which
1671 the following are most likely to appear:
1675 This warns in two cases, for both C and C++:
1676 * When the code is trying to take the absolute value of an unsigned
1677 quantity, which is effectively a no-op, and almost never what was
1678 intended. The code should be fixed, if at all possible. If you are
1679 sure that the unsigned quantity can be safely cast to signed, without
1680 loss of information or undefined behavior, you can add an explicit
1681 cast, or disable the warning.
1683 * When the code is trying to take an absolute value, but the called
1684 abs() variant is for the wrong type, which can lead to truncation.
1685 If you want to disable the warning instead of fixing the code, please
1686 make sure that truncation will not occur, or it might lead to unwanted
1689 -Wtautological-undefined-compare and
1690 -Wundefined-bool-conversion
1692 These warn when C++ code is trying to compare 'this' against NULL, while
1693 'this' should never be NULL in well-defined C++ code. However, there is
1694 some legacy (pre C++11) code out there, which actively abuses this
1695 feature, which was less strictly defined in previous C++ versions.
1697 Squid and openjdk do this, for example. The warning can be turned off
1698 for C++98 and earlier, but compiling the code in C++11 mode might result
1699 in unexpected behavior; for example, the parts of the program that are
1700 unreachable could be optimized away.
1703 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1704 kernel sources have been removed. The .h files remain, since some
1705 utilities include them. This will need to be fixed later.
1706 If "mount -t oldnfs ..." is attempted, it will fail.
1707 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1708 the utilities will report errors.
1711 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1712 directories to top level SUBDIR variable when their parent
1713 directory is included in LOCAL_DIRS. Users with build systems with
1714 such hierarchies and without SUBDIR entries in the parent
1715 directory Makefiles should add them or add the directories to
1719 faith(4) and faithd(8) have been removed from the base system. Faith
1720 has been obsolete for a very long time.
1723 vt(4), the new console driver, is enabled by default. It brings
1724 support for Unicode and double-width characters, as well as
1725 support for UEFI and integration with the KMS kernel video
1728 You may need to update your console settings in /etc/rc.conf,
1729 most probably the keymap. During boot, /etc/rc.d/syscons will
1730 indicate what you need to do.
1732 vt(4) still has issues and lacks some features compared to
1733 syscons(4). See the wiki for up-to-date information:
1734 https://wiki.freebsd.org/Newcons
1736 If you want to keep using syscons(4), you can do so by adding
1737 the following line to /boot/loader.conf:
1741 pjdfstest has been integrated into kyua as an opt-in test suite.
1742 Please see share/doc/pjdfstest/README for more details on how to
1746 gperf has been removed from the base system for architectures
1747 that use clang. Ports that require gperf will obtain it from the
1751 pjdfstest has been moved from tools/regression/pjdfstest to
1755 At svn r271982, The default linux compat kernel ABI has been adjusted
1756 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1757 update. If you wish to continue using the linux-f10 compat ports,
1758 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1759 encouraged to update their linux-compat packages to linux-c6 during
1760 their next update cycle.
1763 The ofwfb driver, used to provide a graphics console on PowerPC when
1764 using vt(4), no longer allows mmap() of all physical memory. This
1765 will prevent Xorg on PowerPC with some ATI graphics cards from
1766 initializing properly unless x11-servers/xorg-server is updated to
1770 The xdev targets have been converted to using TARGET and
1771 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1774 The default unbound configuration has been modified to address
1775 issues with reverse lookups on networks that use private
1776 address ranges. If you use the local_unbound service, run
1777 "service local_unbound setup" as root to regenerate your
1778 configuration, then "service local_unbound reload" to load the
1782 The GNU texinfo and GNU info pages are not built and installed
1783 anymore, WITH_INFO knob has been added to allow to built and install
1785 UPDATE: see 20150102 entry on texinfo's removal
1788 The GNU readline library is now an INTERNALLIB - that is, it is
1789 statically linked into consumers (GDB and variants) in the base
1790 system, and the shared library is no longer installed. The
1791 devel/readline port is available for third party software that
1795 The Itanium architecture (ia64) has been removed from the list of
1796 known architectures. This is the first step in the removal of the
1800 Commit r268115 has added NFSv4.1 server support, merged from
1801 projects/nfsv4.1-server. Since this includes changes to the
1802 internal interfaces between the NFS related modules, a full
1803 build of the kernel and modules will be necessary.
1804 __FreeBSD_version has been bumped.
1807 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1808 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1809 which differs from the behaviour controlled by this knob.)
1812 Maximal length of the serial number in CTL was increased from 16 to
1813 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1814 and ctld, need to be rebuilt to work with a new kernel.
1817 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1818 1 respectively to match the upstream numbers. They were out of
1819 sync because, when they were originally added to FreeBSD, the
1820 upstream versions were not respected. These libraries are private
1821 and not yet built by default, so renumbering them should be a
1822 non-issue. However, unclean source trees will yield broken test
1823 programs once the operator executes "make delete-old-libs" after a
1824 "make installworld".
1826 Additionally, the atf-sh binary was made private by moving it into
1827 /usr/libexec/. Already-built shell test programs will keep the
1828 path to the old binary so they will break after "make delete-old"
1831 If you are using WITH_TESTS=yes (not the default), wipe the object
1832 tree and rebuild from scratch to prevent spurious test failures.
1833 This is only needed once: the misnumbered libraries and misplaced
1834 binaries have been added to OptionalObsoleteFiles.inc so they will
1835 be removed during a clean upgrade.
1838 Clang and llvm have been upgraded to 3.4.1 release.
1841 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1842 be removed to avoid issues in the future (and has been added to
1846 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1847 past, it affected all builds that used the bsd.*.mk files. The old
1848 behavior was a bug, but people may have relied upon it. To get this
1849 behavior back, you can .include /etc/src.conf from /etc/make.conf
1850 (which is still global and isn't changed). This also changes the
1851 behavior of incremental builds inside the tree of individual
1852 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1853 Although this has survived make universe and some upgrade scenarios,
1854 other upgrade scenarios may have broken. At least one form of
1855 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1856 as well... In cases where MAKESYSPATH isn't working with this
1857 setting, you'll need to set it to the full path to your tree.
1859 One side effect of all this cleaning up is that bsd.compiler.mk
1860 is no longer implicitly included by bsd.own.mk. If you wish to
1861 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1865 The lindev device has been removed since /dev/full has been made a
1866 standard device. __FreeBSD_version has been bumped.
1869 The knob WITHOUT_VI was added to the base system, which controls
1870 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1871 in order to reorder files share/termcap and didn't build ex(1) as a
1872 build tool, so building/installing with WITH_VI is highly advised for
1873 build hosts for older releases.
1875 This issue has been fixed in stable/9 and stable/10 in r277022 and
1876 r276991, respectively.
1879 The YES_HESIOD knob has been removed. It has been obsolete for
1880 a decade. Please move to using WITH_HESIOD instead or your builds
1881 will silently lack HESIOD.
1884 The uart(4) driver has been changed with respect to its handling
1885 of the low-level console. Previously the uart(4) driver prevented
1886 any process from changing the baudrate or the CLOCAL and HUPCL
1887 control flags. By removing the restrictions, operators can make
1888 changes to the serial console port without having to reboot.
1889 However, when getty(8) is started on the serial device that is
1890 associated with the low-level console, a misconfigured terminal
1891 line in /etc/ttys will now have a real impact.
1892 Before upgrading the kernel, make sure that /etc/ttys has the
1893 serial console device configured as 3wire without baudrate to
1894 preserve the previous behaviour. E.g:
1895 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1898 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1899 to improve performance. To re-enable it, if needed, run rpcbind
1900 with command line option -W.
1903 Switched back to the GPL dtc compiler due to updates in the upstream
1904 dts files not being supported by the BSDL dtc compiler. You will need
1905 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1906 may result while building dtb files during a kernel build if you fail
1907 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1910 Clang and llvm have been upgraded to 3.4 release.
1913 The nve(4) driver has been removed. Please use the nfe(4) driver
1914 for NVIDIA nForce MCP Ethernet adapters instead.
1917 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1918 This could cause certain C++ applications using shared libraries built
1919 against the previous version of libc++ to crash. The incompatibility
1920 has now been fixed, but any C++ applications or shared libraries built
1921 between r261283 and r261801 should be recompiled.
1924 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1925 capability mode support. Please note that enabling the feature in
1926 kernel is still highly recommended.
1929 OpenSSH is now built with sandbox support, and will use sandbox as
1930 the default privilege separation method. This requires Capsicum
1931 capability mode support in kernel.
1934 The libelf and libdwarf libraries have been updated to newer
1935 versions from upstream. Shared library version numbers for
1936 these two libraries were bumped. Any ports or binaries
1937 requiring these two libraries should be recompiled.
1938 __FreeBSD_version is bumped to 1100006.
1941 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1942 instead of providing an explicit one, this would prevent such
1943 Makefile from providing its own Kyuafile in the future during
1944 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1945 intervention is needed to clean an objdir if you use NO_CLEAN:
1946 # find /usr/obj -name Kyuafile | xargs rm -f
1949 The behavior of gss_pseudo_random() for the krb5 mechanism
1950 has changed, for applications requesting a longer random string
1951 than produced by the underlying enctype's pseudo-random() function.
1952 In particular, the random string produced from a session key of
1953 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1954 be different at the 17th octet and later, after this change.
1955 The counter used in the PRF+ construction is now encoded as a
1956 big-endian integer in accordance with RFC 4402.
1957 __FreeBSD_version is bumped to 1100004.
1960 The WITHOUT_ATF build knob has been removed and its functionality
1961 has been subsumed into the more generic WITHOUT_TESTS. If you were
1962 using the former to disable the build of the ATF libraries, you
1963 should change your settings to use the latter.
1966 The default version of mtree is nmtree which is obtained from
1967 NetBSD. The output is generally the same, but may vary
1968 slightly. If you found you need identical output adding
1969 "-F freebsd9" to the command line should do the trick. For the
1970 time being, the old mtree is available as fmtree.
1973 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1974 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1975 1.1.4_8 and verify bsdyml not linked in, before running "make
1977 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1979 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1982 The stable/10 branch has been created in subversion from head
1989 Avoid using make -j when upgrading. While generally safe, there are
1990 sometimes problems using -j to upgrade. If your upgrade fails with
1991 -j, please try again without -j. From time to time in the past there
1992 have been problems using -j with buildworld and/or installworld. This
1993 is especially true when upgrading between "distant" versions (eg one
1994 that cross a major release boundary or several minor releases, or when
1995 several months have passed on the -current branch).
1997 Sometimes, obscure build problems are the result of environment
1998 poisoning. This can happen because the make utility reads its
1999 environment when searching for values for global variables. To run
2000 your build attempts in an "environmental clean room", prefix all make
2001 commands with 'env -i '. See the env(1) manual page for more details.
2003 When upgrading from one major version to another it is generally best to
2004 upgrade to the latest code in the currently installed branch first, then
2005 do an upgrade to the new branch. This is the best-tested upgrade path,
2006 and has the highest probability of being successful. Please try this
2007 approach if you encounter problems with a major version upgrade. Since
2008 the stable 4.x branch point, one has generally been able to upgrade from
2009 anywhere in the most recent stable branch to head / current (or even the
2010 last couple of stable branches). See the top of this file when there's
2013 When upgrading a live system, having a root shell around before
2014 installing anything can help undo problems. Not having a root shell
2015 around can lead to problems if pam has changed too much from your
2016 starting point to allow continued authentication after the upgrade.
2018 This file should be read as a log of events. When a later event changes
2019 information of a prior event, the prior event should not be deleted.
2020 Instead, a pointer to the entry with the new information should be
2021 placed in the old entry. Readers of this file should also sanity check
2022 older entries before relying on them blindly. Authors of new entries
2023 should write them with this in mind.
2027 When upgrading the boot ZFS pool to a new version, always follow
2030 1.) recompile and reinstall the ZFS boot loader and boot block
2031 (this is part of "make buildworld" and "make installworld")
2033 2.) update the ZFS boot block on your boot drive
2035 The following example updates the ZFS boot block on the first
2036 partition (freebsd-boot) of a GPT partitioned drive ada0:
2037 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2039 Non-boot pools do not need these updates.
2043 If you are updating from a prior version of FreeBSD (even one just
2044 a few days old), you should follow this procedure. It is the most
2045 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2047 make kernel-toolchain
2048 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2049 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2051 To test a kernel once
2052 ---------------------
2053 If you just want to boot a kernel once (because you are not sure
2054 if it works, or if you want to boot a known bad kernel to provide
2055 debugging information) run
2056 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2057 nextboot -k testkernel
2059 To rebuild everything and install it on the current system.
2060 -----------------------------------------------------------
2061 # Note: sometimes if you are running current you gotta do more than
2062 # is listed here if you are upgrading from a really old current.
2064 <make sure you have good level 0 dumps>
2066 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2067 make installkernel KERNCONF=YOUR_KERNEL_HERE
2069 <reboot in single user> [3]
2076 To cross-install current onto a separate partition
2077 --------------------------------------------------
2078 # In this approach we use a separate partition to hold
2079 # current's root, 'usr', and 'var' directories. A partition
2080 # holding "/", "/usr" and "/var" should be about 2GB in
2083 <make sure you have good level 0 dumps>
2086 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2087 <maybe newfs current's root partition>
2088 <mount current's root partition on directory ${CURRENT_ROOT}>
2089 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2090 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2091 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2092 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2093 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2094 <reboot into current>
2095 <do a "native" rebuild/install as described in the previous section>
2096 <maybe install compatibility libraries from ports/misc/compat*>
2100 To upgrade in-place from stable to current
2101 ----------------------------------------------
2102 <make sure you have good level 0 dumps>
2104 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2105 make installkernel KERNCONF=YOUR_KERNEL_HERE
2107 <reboot in single user> [3]
2114 Make sure that you've read the UPDATING file to understand the
2115 tweaks to various things you need. At this point in the life
2116 cycle of current, things change often and you are on your own
2117 to cope. The defaults can also change, so please read ALL of
2118 the UPDATING entries.
2120 Also, if you are tracking -current, you must be subscribed to
2121 freebsd-current@freebsd.org. Make sure that before you update
2122 your sources that you have read and understood all the recent
2123 messages there. If in doubt, please track -stable which has
2124 much fewer pitfalls.
2126 [1] If you have third party modules, such as vmware, you
2127 should disable them at this point so they don't crash your
2130 [3] From the bootblocks, boot -s, and then do
2135 adjkerntz -i # if CMOS is wall time
2136 Also, when doing a major release upgrade, it is required that
2137 you boot into single user mode to do the installworld.
2139 [4] Note: This step is non-optional. Failure to do this step
2140 can result in a significant reduction in the functionality of the
2141 system. Attempting to do it by hand is not recommended and those
2142 that pursue this avenue should read this file carefully, as well
2143 as the archives of freebsd-current and freebsd-hackers mailing lists
2144 for potential gotchas. The -U option is also useful to consider.
2145 See mergemaster(8) for more information.
2147 [5] Usually this step is a no-op. However, from time to time
2148 you may need to do this if you get unknown user in the following
2149 step. It never hurts to do it all the time. You may need to
2150 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2151 install) after the buildworld before this step if you last updated
2152 from current before 20130425 or from -stable before 20130430.
2154 [6] This only deletes old files and directories. Old libraries
2155 can be deleted by "make delete-old-libs", but you have to make
2156 sure that no program is using those libraries anymore.
2158 [8] The new kernel must be able to run existing binaries used by
2159 an installworld. When upgrading across major versions, the new
2160 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2161 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2162 binaries). Failure to do so may leave you with a system that is
2163 hard to boot to recover. A GENERIC kernel will include suitable
2164 compatibility options to run binaries from older branches.
2166 Make sure that you merge any new devices from GENERIC since the
2167 last time you updated your kernel config file.
2169 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2170 "?=" instead of the "=" assignment operator, so that buildworld can
2171 override the CPUTYPE if it needs to.
2173 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2174 not on the command line, or in /etc/make.conf. buildworld will
2175 warn if it is improperly defined.
2178 This file contains a list, in reverse chronological order, of major
2179 breakages in tracking -current. It is not guaranteed to be a complete
2180 list of such breakages, and only contains entries since September 23, 2011.
2181 If you need to see UPDATING entries from before that date, you will need
2182 to fetch an UPDATING file from an older FreeBSD release.
2184 Copyright information:
2186 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2188 Redistribution, publication, translation and use, with or without
2189 modification, in full or in part, in any form or format of this
2190 document are permitted without further permission from the author.
2192 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2193 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2194 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2195 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2196 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2197 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2198 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2199 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2200 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2201 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2202 POSSIBILITY OF SUCH DAMAGE.
2204 Contact Warner Losh if you have any questions about your use of