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 updating system packages
15 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
16 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
17 the tip of head, and then rebuild without this option. The bootstrap process
18 from older version of current across the gcc/clang cutover is a bit fragile.
21 12.3-RELEASE-p12 FreeBSD-SA-23:03.openssl
23 Fix multiple OpenSSL vulnerabilities [SA-23:03.openssl]
26 12.3-RELEASE-p11 FreeBSD-SA-23:01.geli
27 FreeBSD-EN-23:01.tzdata
28 FreeBSD-EN-23:04.ixgbe
30 Fix GELI silently omits the keyfile if read from stdin [SA-23:01.geli]
32 Timezone database information update [EN-23:01.tzdata]
34 Fix ixgbe incorrectly reporting input errors for 82599ES [EN-23:04.ixgbe]
37 12.3-RELEASE-p10 FreeBSD-SA-22:15.ping
38 FreeBSD-EN-22:28.heimdal
40 Stack overflow in ping [SA-22:15.ping]
42 Regression in Heimdal KDC [EN-22:28.heimdal]
45 12.3-RELEASE-p9 FreeBSD-SA-22:14.heimdal
47 Multiple vulnerabilities in Heimdal [SA-22:14.heimdal]
50 12.3-RELEASE-p8 FreeBSD-EN-22:22.tzdata
52 Timezone database information update [EN-22:20.tzdata]
55 12.3-RELEASE-p7 FreeBSD-SA-22:13.zlib
56 FreeBSD-EN-22:20.tzdata
58 zlib heap buffer overflow [SA-22:13.zlib]
60 Timezone database information update [EN-22:20.tzdata]
63 12.3-RELEASE-p6 FreeBSD-SA-22:09.elf
68 Out of bounds read in elf_note_prpsinfo() [SA-22:09.elf]
70 AIO credential reference count leak [SA-22:10.aio]
72 Memory disclosure by stale virtual memory mapping [SA-22:11.vm]
74 Kernel memory corruption during SCSI error recovery [EN-22:17.cam]
77 12.3-RELEASE-p5 FreeBSD-SA-22:04.netmap
78 FreeBSD-SA-22:05.bhyve
79 FreeBSD-SA-22:06.ioctl
80 FreeBSD-SA-22:07.wifi_meshid
83 Potential jail escape vulnerabilities in netmap [SA-22:04.netmap]
85 Bhyve e82545 device emulation out-of-bounds write [SA-22:05.bhyve]
87 mpr/mps/mpt driver ioctl heap out-of-bounds write [SA-22:06.ioctl]
89 802.11 heap buffer overflow [SA-22:07.wifi_meshid]
91 zlib compression out-of-bounds write [SA-22:08.zlib]
94 12.3-RELEASE-p4 FreeBSD-EN-22:14.tzdata
96 Timezone database information update. [EN-22:14.tzdata]
99 12.3-RELEASE-p3 FreeBSD-EN-22:09.freebsd-update
100 FreeBSD-SA-22:02.wifi
101 FreeBSD-SA-22:03.openssl
103 freebsd-update creating erroneous boot environments [FreeBSD-EN-22:09.freebsd-update]
105 Multiple WiFi issues [FreeBSD-SA-22:02.wifi]
107 OpenSSL certificate parsing infinite loop [FreeBSD-SA-22:03.openssl]
110 12.3-RELEASE-p2 FreeBSD-EN-22:08.i386
112 Fix regression in i386 TLB invalidation logic. [FreeBSD-EN-22:08.i386]
115 12.3-RELEASE-p1 FreeBSD-EN-22:02.xsave
116 FreeBSD-EN-22:03.hyperv
117 FreeBSD-EN-22:04.pcid
118 FreeBSD-EN-22:06.libalias
121 Correct size of the amd64 SSE area in the xsave layout [FreeBSD-EN-22:02.xsave]
123 Prepopulate Hyper-V PCI device bars [FreeBSD-EN-22:03.hyperv]
125 Fix amd64 pmap PCID mode invalidations [FreeBSD-EN-22:04.pcid]
127 Fix fragmented UDP packets handling [FreeBSD-EN-22:06.libalias]
129 Fix vt console buffer overflow [FreeBSD-SA-22:01.vt]
135 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
136 As of be70c7a50d32 it is no longer used by userspace, but it does mean
137 users may not be able to enumerate pf states if they update the kernel
138 past c021ff986e2b without first updating userspace past be70c7a50d32.
141 The 20210707 awk update brought in a change in behavior. This has
142 been corrected as of d4d252c49976. Between these dates, if you
143 installed a new awk binary, you may not be able to build a new
144 kernel because the change in behavior affected the genoffset
145 script used to build the kernel. If you did update, the fix is
146 to update your sources past the above hash and do
149 % sudo -E make install
150 to enable building kernels again.
153 awk has been updated to the latest one-true-awk version 20210215.
154 This contains a number of minor bug fixes.
157 Commit 6ae32cc8182f changed the internal KAPI between the krpc and
158 nfsd modules. As such, both need to be rebuilt from sources.
159 Bump __FreeBSD_version to 1202508.
162 Commit e9959506d2cc changed the internal KAPI between the
163 nscl.ko and nfscommon.ko modules, so they both need to be
164 rebuilt from sources.
167 Commit 0a1fdb867c72 changed the internal KAPI between
168 the krpc and NFS. As such, the krpc, nfscommon and
169 nfscl modules must all be rebuilt from sources.
170 Without this patch, NFSv4.1 mounts should not
171 be done with the nfscbd(8) daemon running, to avoid
172 needing a working back channel for server->client RPCs.
175 The make.conf(5) MALLOC_PRODUCTION variable, used for disabling and
176 enabling assertions and statistics gathering in malloc(3), has been
177 migrated to a src.conf(5) WITH/WITHOUT_MALLOC_PRODUCTION option.
179 On stable branches, WITH_MALLOC_PRODUCTION is set by default, which
180 means that malloc(3) has assertions and statistics gathering disabled,
181 for improved performance.
183 For backwards compatibility, the make.conf(5) MALLOC_PRODUCTION is still
184 honored, but it is now deprecated and undocumented.
187 The resume code now notifies devd with the 'kernel' system
188 rather than the old 'kern' subsystem to be consistent with
189 other use. The old notification will be created as well, but
190 will be removed prior to FreeBSD 14.0.
193 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
194 been upgraded to 10.0.1. Please see the 20141231 entry below for
195 information about prerequisites and upgrading, if you are not already
196 using clang 3.5.0 or higher.
199 read(2) of a directory fd is now rejected by default. root may
200 re-enable it for the entire system with the
201 security.bsd.allow_read_dir sysctl(8) MIB.
203 It may be advised to setup aliases for grep to default to `-d skip` if
204 commonly non-recursively grepping a list that includes directories and
205 the potential for the resulting stderr output is not tolerable. Example
206 aliases are now installed, commented out, in /root/.cshrc.
209 Upstream DTS from Linux 5.6 was merged and they now have the SID
210 and THS (Secure ID controller and THermal Sensor) node present.
211 The DTB overlays have now been removed from the tree for the H3/H5 and
212 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
213 deal with upstream DTS. If you are using those overlays you need to
214 remove them from loader.conf and update the DTBs on the FAT partition.
217 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
218 been upgraded to 10.0.0. Please see the 20141231 entry below for
219 information about prerequisites and upgrading, if you are not already
220 using clang 3.5.0 or higher.
223 The root certificates of the Mozilla CA Certificate Store have been
224 imported into the base system and can be managed with the certctl(8)
225 utility. If you have installed the security/ca_root_nss port or package
226 with the ETCSYMLINK option (the default), be advised that there may be
227 differences between those included in the port and those included in
228 base due to differences in nss branch used as well as general update
229 frequency. Note also that certctl(8) cannot manage certs in the
230 format used by the security/ca_root_nss port.
233 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
234 been upgraded to 9.0.1. Please see the 20141231 entry below for
235 information about prerequisites and upgrading, if you are not already
236 using clang 3.5.0 or higher.
239 The nctgpio and wbwd drivers have been moved to the superio bus.
240 If you have one of these drivers in a kernel configuration, then
241 you should add device superio to it. If you use one of these drivers
242 as a module and you compile a custom set of modules, then you should
243 add superio to the set.
246 The tap(4) driver has been folded into tun(4), and the module has been
247 renamed to tuntap. You should update any kld_list="if_tap" or
248 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
249 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
250 module instead, and "device tap" or "device tun" entries in kernel
251 config files to select the tuntap device instead.
254 ntpd no longer by default locks its pages in memory, allowing them
255 to be paged out by the kernel. Use rlimit memlock to restore
256 historic BSD behaviour. For example, add "rlimit memlock 32"
257 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
260 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
261 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
262 been removed from mount_fusefs(8). You can safely remove them from
263 your scripts, because they had no effect.
265 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
266 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
267 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
268 sysctls have been removed. If you felt the need to set any of them to
269 a non-default value, please tell asomers@FreeBSD.org why.
272 The fuse(4) module has been renamed to fusefs(4) for consistency with
273 other filesystems. You should update any kld_load="fuse" entries in
274 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
275 "options FUSE" enties in kernel config files.
278 Default permissions on the /var/account/acct file (and copies of it
279 rotated by periodic daily scripts) are changed from 0644 to 0640
280 because the file contains sensitive information that should not be
281 world-readable. If the /var/account directory must be created by
282 rc.d/accounting, the mode used is now 0750. Admins who use the
283 accounting feature are encouraged to change the mode of an existing
284 /var/account directory to 0750 or 0700.
287 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
288 been upgraded to 8.0.1. Please see the 20141231 entry below for
289 information about prerequisites and upgrading, if you are not already
290 using clang 3.5.0 or higher.
293 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
294 functionality needed for the RETPOLINE option should work properly
295 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
298 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
299 8.0.0. Please see the 20141231 entry below for information about
300 prerequisites and upgrading, if you are not already using clang 3.5.0
304 The RETPOLINE option produces non-functional ifunc-using binaries
305 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
306 Once Clang 8 is merged it may be enabled again.
309 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
310 7.0.1. Please see the 20141231 entry below for information about
311 prerequisites and upgrading, if you are not already using clang 3.5.0
315 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
316 compiled into your custom kernel, add 'device xz' statement to the
320 Iflib is no longer unconditionally compiled into the kernel. Drivers
321 using iflib and statically compiled into the kernel, now require
322 the 'device iflib' config option. For the same drivers loaded as
323 modules on kernels not having 'device iflib', the iflib.ko module
324 is loaded automatically.
327 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
328 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
329 servers that have vfs.nfsd.nfs_privport set will only allow mounts
330 from clients using a reserved port#. Since both the FreeBSD and Linux
331 NFSv4 clients use reserved port#s by default, this should not affect
335 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
336 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
337 it produces broken binaries when ifuncs are in use. Users needing
338 GNU ld should install the binutils port or package.
341 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
342 has been converted to a port (misc/ctm) and will be removed from
343 FreeBSD-13. A depreciation warning will be printed to stderr by
344 the ctm command, but the functionality will remain in base for all
348 The stable/12 branch has been created in subversion from head
352 Ports for the DRM modules have been simplified. Now, amd64 users should
353 just install the drm-kmod port. All others should install
356 Graphics hardware that's newer than about 2010 usually works with
357 drm-kmod. For hardware older than 2013, however, some users will need
358 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
359 than 2008 usually only works in drm-legacy-kmod. The graphics team can
360 only commit to hardware made since 2013 due to the complexity of the
361 market and difficulty to test all the older cards effectively. If you
362 have hardware supported by drm-kmod, you are strongly encouraged to use
363 that as you will get better support.
365 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
366 elsewhere, the drm and drm2 modules will be eliminated from the src base
367 soon (with a limited exception for arm). Please update to the package asap
368 and report any issues to x11@freebsd.org.
370 Generally, anybody using the drm*-kmod packages should add
371 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
372 cross-threading surprises, especially with automatic driver
373 loading from X11 startup. These will become the defaults in 13-current
377 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
378 custom kernel and module loading configuration files must be updated
379 accordingly. Moreover, interfaces previous presented as ixlvN to the
380 system are now exposed as iavfN and network configuration files must
381 be adjusted as necessary.
384 OpenSSL has been updated to version 1.1.1. This update included
385 additional various API changes througout the base system. It is
386 important to rebuild third-party software after upgrading. The value
387 of __FreeBSD_version has been bumped accordingly.
390 The legacy DRM modules and drivers have now been added to the loader's
391 module blacklist, in favor of loading them with kld_list in rc.conf(5).
392 The module blacklist may be overridden with the loader.conf(5)
393 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
397 The cam(4) based nda(4) driver will be used over nvd(4) by default on
398 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
399 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
400 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
404 Reproducible build mode is now on by default, in preparation for
405 FreeBSD 12.0. This eliminates build metadata such as the user,
406 host, and time from the kernel (and uname), unless the working tree
407 corresponds to a modified checkout from a version control system.
408 The previous behavior can be obtained by setting the /etc/src.conf
409 knob WITHOUT_REPRODUCIBLE_BUILD.
412 The Yarrow CSPRNG has been removed from the kernel as it has not been
413 supported by its designers since at least 2003. Fortuna has been the
414 default since FreeBSD-11.
417 devctl freeze/thaw have gone into the tree, the rc scripts have been
418 updated to use them and devmatch has been changed. You should update
419 kernel, userland and rc scripts all at the same time.
422 The default interpreter has been switched from 4th to Lua.
423 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
424 interpreter. If you have custom FORTH code you will need to set
425 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
426 src.conf for the build. This will create default hard links between
427 loader and loader_4th instead of loader and loader_lua, the new default.
428 If you are using UEFI it will create the proper hard link to loader.efi.
430 bhyve uses userboot.so. It remains 4th-only until some issues are solved
431 regarding coexisting with multiple versions of FreeBSD are resolved.
434 ls(1) now respects the COLORTERM environment variable used in other
435 systems and software to indicate that a colored terminal is both
436 supported and desired. If ls(1) is suddenly emitting colors, they may
437 be disabled again by either removing the unwanted COLORTERM from your
438 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
439 may not be observed in a future release.
442 The default pager for most commands has been changed to "less". To
443 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
447 The jedec_ts(4) driver has been removed. A superset of its functionality
448 is available in the jedec_dimm(4) driver, and the manpage for that
449 driver includes migration instructions. If you have "device jedec_ts"
450 in your kernel configuration file, it must be removed.
453 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
454 This should have no effect if the kernel is booted via BIOS/legacy boot.
455 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
456 has a buggy firmware that prevents a successful boot due to use of
460 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
461 support has been removed from the tree. These ports were
462 obsolete and/or known to be broken for many years.
465 loader.efi has been augmented to participate more fully in the
466 UEFI boot manager protocol. loader.efi will now look at the
467 BootXXXX environment variable to determine if a specific kernel
468 or root partition was specified. XXXX is derived from BootCurrent.
469 efibootmgr(8) manages these standard UEFI variables.
472 zfsloader's functionality has now been folded into loader.
473 zfsloader is no longer necessary once you've updated your
474 boot blocks. For a transition period, we will install a
475 hardlink for zfsloader to loader to allow a smooth transition
476 until the boot blocks can be updated (hard link because old
477 zfs boot blocks don't understand symlinks).
480 ARM64 now have efifb support, if you want to have serial console
481 on your arm64 board when an screen is connected and the bootloader
482 setup a frambuffer for us to use, just add :
486 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
487 an screen connected as the firmware will setup a framebuffer are that
488 u-boot will expose as an EFI framebuffer.
491 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
492 or take steps to update /etc/passwd before doing installworld on
493 existing systems. Do not skip the "mergemaster -Fp" step before
494 installworld, as described in the update procedures near the bottom
495 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
496 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
497 the ntp config file contain options that change file/dir locations.
498 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
499 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
500 taking steps to ensure that all required files/dirs are accessible
504 Big endian arm support has been removed.
507 The static environment setup in kernel configs is no longer mutually
508 exclusive with the loader(8) environment by default. In order to
509 restore the previous default behavior of disabling the loader(8)
510 environment if a static environment is present, you must specify
511 loader_env.disabled=1 in the static environment.
514 The ABI of syscalls used by management tools like sockstat and
515 netstat has been broken to allow 32-bit binaries to work on
516 64-bit kernels without modification. These programs will need
517 to match the kernel in order to function. External programs may
518 require minor modifications to accommodate a change of type in
519 structures from pointers to 64-bit virtual addresses.
522 On i386 and amd64 atomics are now inlined. Out of tree modules using
523 atomics will need to be rebuilt.
526 The '%I' format in the kern.corefile sysctl limits the number of
527 core files that a process can generate to the number stored in the
528 debug.ncores sysctl. The '%I' format is replaced by the single digit
529 index. Previously, if all indexes were taken the kernel would overwrite
530 only a core file with the highest index in a filename.
531 Currently the system will create a new core file if there is a free
532 index or if all slots are taken it will overwrite the oldest one.
535 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
536 6.0.1. Please see the 20141231 entry below for information about
537 prerequisites and upgrading, if you are not already using clang 3.5.0
541 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
542 needed to be changed to work with it. This change was made with r335763
543 and requires a mergemaster / etcupdate / etc to update the installed file.
546 r334930 changed the interface between the NFS modules, so they all
547 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
550 As of r334391 lld is the default amd64 system linker; it is installed
551 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
555 The kernel / userland interface for devinfo changed, so you'll
556 need a new kernel and userland as a pair for it to work (rebuilding
557 lib/libdevinfo is all that's required). devinfo and devmatch will
558 not work, but everything else will when there's a mismatch.
561 The on-disk format for hwpmc callchain records has changed to include
562 threadid corresponding to a given record. This changes the field offsets
563 and thus requires that libpmcstat be rebuilt before using a kernel
567 The vxge(4) driver has been removed. This driver was introduced into
568 HEAD one week before the Exar left the Ethernet market and is not
569 known to be used. If you have device vxge in your kernel config file
573 The amd64 kernel now requires a ld that supports ifunc to produce a
574 working kernel, either lld or a newer binutils. lld is built by default
575 on amd64, and the 'buildkernel' target uses it automatically. However,
576 it is not the default linker, so building the kernel the traditional
577 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
578 binutils port/package). lld will soon be default, and this requirement
581 NOTE: As of r334391 lld is the default system linker on amd64, and no
582 workaround is necessary.
585 The nxge(4) driver has been removed. This driver was for PCI-X 10g
586 cards made by s2io/Neterion. The company was aquired by Exar and
587 no longer sells or supports Ethernet products. If you have device
588 nxge in your kernel config file it must be removed.
591 The tz database (tzdb) has been updated to 2018e. This version more
592 correctly models time stamps in time zones with negative DST such as
593 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
594 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
595 time zone abbreviations and the tm_isdst flag.
598 The ixgb(4) driver has been removed. This driver was for an early and
599 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
600 quickly shifted to the long lived ixgbe family. If you have device
601 ixgb in your kernel config file it must be removed.
604 The lmc(4) driver has been removed. This was a WAN interface
605 card that was already reportedly rare in 2003, and had an ambiguous
606 license. If you have device lmc in your kernel config file it must
610 Support for Arcnet networks has been removed. If you have device
611 arcnet or device cm in your kernel config file they must be
615 Support for FDDI networks has been removed. If you have device
616 fddi or device fpa in your kernel config file they must be
620 In addition to supporting RFC 3164 formatted messages, the
621 syslogd(8) service is now capable of parsing RFC 5424 formatted
622 log messages. The main benefit of using RFC 5424 is that clients
623 may now send log messages with timestamps containing year numbers,
624 microseconds and time zone offsets.
626 Similarly, the syslog(3) C library function has been altered to
627 send RFC 5424 formatted messages to the local system logging
628 daemon. On systems using syslogd(8), this change should have no
629 negative impact, as long as syslogd(8) and the C library are
630 updated at the same time. On systems using a different system
631 logging daemon, it may be necessary to make configuration
632 adjustments, depending on the software used.
634 When using syslog-ng, add the 'syslog-protocol' flag to local
635 input sources to enable parsing of RFC 5424 formatted messages:
638 unix-dgram("/var/run/log" flags(syslog-protocol));
641 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
642 of the 'imuxsock' module to let messages be processed by the
643 regular RFC 3164/5424 parsing pipeline:
645 module(load="imuxsock" SysSock.UseSpecialParser="off")
647 Do note that these changes only affect communication between local
648 applications and syslogd(8). The format that syslogd(8) uses to
649 store messages on disk or forward messages to other systems
650 remains unchanged. syslogd(8) still uses RFC 3164 for these
651 purposes. Options to customize this behaviour will be added in the
652 future. Utilities that process log files stored in /var/log are
653 thus expected to continue to function as before.
655 __FreeBSD_version has been incremented to 1200061 to denote this
659 Support for token ring networks has been removed. If you
660 have "device token" in your kernel config you should remove
661 it. No device drivers supported token ring.
664 makefs was modified to be able to tag ISO9660 El Torito boot catalog
665 entries as EFI instead of overloading the i386 tag as done previously.
666 The amd64 mkisoimages.sh script used to build amd64 ISO images for
667 release was updated to use this. This may mean that makefs must be
668 updated before "make cdrom" can be run in the release directory. This
669 should be as simple as:
671 $ cd $SRCDIR/usr.sbin/makefs
672 $ make depend all install
675 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
676 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
677 Co-existance for the transition period will come shortly. Booting is a
678 complex environment and test coverage for Lua-enabled loaders has been
679 thin, so it would be prudent to assume it might not work and make
680 provisions for backup boot methods.
683 devmatch functionality has been turned on in devd. It will automatically
684 load drivers for unattached devices. This may cause unexpected drivers to
685 be loaded. Please report any problems to current@ and imp@freebsd.org.
688 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
689 6.0.0. Please see the 20141231 entry below for information about
690 prerequisites and upgrading, if you are not already using clang 3.5.0
694 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
695 This means it is used to link the kernel and userland libraries and
696 executables, but is not yet installed as /usr/bin/ld by default.
698 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
699 WITHOUT_LLD_BOOTSTRAP=yes
702 On i386, pmtimer has been removed. Its functionality has been folded
703 into apm. It was a no-op on ACPI in current for a while now (but was still
704 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
705 from kernel config files.
708 The use of RSS hash from the network card aka flowid has been
709 disabled by default for lagg(4) as it's currently incompatible with
710 the lacp and loadbalance protocols.
712 This can be re-enabled by setting the following in loader.conf:
713 net.link.lagg.default_use_flowid="1"
716 The SW_WATCHDOG option is no longer necessary to enable the
717 hardclock-based software watchdog if no hardware watchdog is
718 configured. As before, SW_WATCHDOG will cause the software
719 watchdog to be enabled even if a hardware watchdog is configured.
722 r326887 fixes the issue described in the 20171214 UPDATING entry.
723 r326888 flips the switch back to building GELI support always.
726 r362593 broke ZFS + GELI support for reasons unknown. However,
727 it also broke ZFS support generally, so GELI has been turned off
728 by default as the lesser evil in r326857. If you boot off ZFS and/or
729 GELI, it might not be a good time to update.
732 PowerPC users must update loader(8) by rebuilding world before
733 installing a new kernel, as the protocol connecting them has
734 changed. Without the update, loader metadata will not be passed
735 successfully to the kernel and users will have to enter their
736 root partition at the kernel mountroot prompt to continue booting.
737 Newer versions of loader can boot old kernels without issue.
740 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
741 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
742 to WITH/OUT_LOADER_GELI.
745 The naive and non-compliant support of posix_fallocate(2) in ZFS
746 has been removed as of r325320. The system call now returns EINVAL
747 when used on a ZFS file. Although the new behavior complies with the
748 standard, some consumers are not prepared to cope with it.
749 One known victim is lld prior to r325420.
752 Building in a FreeBSD src checkout will automatically create object
753 directories now rather than store files in the current directory if
754 'make obj' was not ran. Calling 'make obj' is no longer necessary.
755 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
756 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
760 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
761 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
762 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
763 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
764 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
765 The UNIFIED_OBJDIR option is a transitional feature that will be
766 removed for 12.0 release; please migrate to the new format for any
767 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
768 than hardcoding paths.
771 The native-xtools target no longer installs the files by default to the
772 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
773 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
776 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
777 options are changing from controlling the build if defined / undefined
778 to controlling the build with explicit 'yes' or 'no' values. They will
779 shift to WITH/WITHOUT options to match other options in the system.
782 libstand has turned into a private library for sys/boot use only.
783 It is no longer supported as a public interface outside of sys/boot.
786 The arm port has split armv6 into armv6 and armv7. armv7 is now
787 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
788 and are running a kernel from before r324363, you will need to add
789 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
792 When building multiple kernels using KERNCONF, non-existent KERNCONF
793 files will produce an error and buildkernel will fail. Previously
794 missing KERNCONF files silently failed giving no indication as to
795 why, only to subsequently discover during installkernel that the
796 desired kernel was never built in the first place.
799 The default serial number format for CTL LUNs has changed. This will
800 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
801 or iSCSI clients care about their LUNs' serial numbers. Users who
802 require serial number stability should hardcode serial numbers in
806 For 32-bit arm compiled for hard-float support, soft-floating point
807 binaries now always get their shared libraries from
808 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
809 /usr/libsoft also existed). Only users with a hard-float ld.so, but
810 soft-float everything else should be affected.
813 The geli password typed at boot is now hidden. To restore the previous
814 behavior, see geli(8) for configuration options.
817 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
818 sysctl values. Minor nit, but requires a rebuild of both world/kernel
822 "make check" behavior (made in ^/head@r295380) has been changed to
823 execute from a limited sandbox, as opposed to executing from
827 - The "beforecheck" and "aftercheck" targets are now specified.
828 - ${CHECKDIR} (added in commit noted above) has been removed.
829 - Legacy behavior can be enabled by setting
830 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
832 If the limited sandbox mode is enabled, "make check" will execute
833 "make distribution", then install, execute the tests, and clean up the
834 sandbox if successful.
836 The "make distribution" and "make install" targets are typically run as
837 root to set appropriate permissions and ownership at installation time.
838 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
839 environment if executing "make check" with limited sandbox mode using
840 an unprivileged user.
843 Since the switch to GPT disk labels, fsck for UFS/FFS has been
844 unable to automatically find alternate superblocks. As of r322297,
845 the information needed to find alternate superblocks has been
846 moved to the end of the area reserved for the boot block.
847 Filesystems created with a newfs of this vintage or later
848 will create the recovery information. If you have a filesystem
849 created prior to this change and wish to have a recovery block
850 created for your filesystem, you can do so by running fsck in
851 foreground mode (i.e., do not use the -p or -y options). As it
852 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
853 to which you should answer yes.
856 As of r321665, an NFSv4 server configuration that services
857 Kerberos mounts or clients that do not support the uid/gid in
858 owner/owner_group string capability, must explicitly enable
859 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
860 machine's /etc/rc.conf file.
863 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
864 Please see the 20141231 entry below for information about prerequisites
865 and upgrading, if you are not already using clang 3.5.0 or higher.
868 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
869 r-commands (rlogin, rsh, etc.) to be built with the base system.
872 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
873 a very major ABI incompatible change, so users of FreeBSD/powerpc must
874 be careful when performing source upgrades. It is best to run
875 'make installworld' from an alternate root system, either a live
876 CD/memory stick, or a temporary root partition. Additionally, all ports
877 must be recompiled. powerpc64 is largely unaffected, except in the case
878 of 32-bit compatibility. All 32-bit binaries will be affected.
881 Forward compatibility for the "ino64" project have been committed. This
882 will allow most new binaries to run on older kernels in a limited
883 fashion. This prevents many of the common foot-shooting actions in the
884 upgrade as well as the limited ability to roll back the kernel across
885 the ino64 upgrade. Complicated use cases may not work properly, though
886 enough simpler ones work to allow recovery in most situations.
889 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
890 if you require the GPL compiler.
893 The internal ABI used for communication between the NFS kernel modules
894 was changed by r320085, so __FreeBSD_version was bumped to
895 ensure all the NFS related modules are updated together.
898 The ABI of struct event was changed by extending the data
899 member to 64bit and adding ext fields. For upgrade, same
900 precautions as for the entry 20170523 "ino64" must be
904 The GNU roff toolchain has been removed from base. To render manpages
905 which are not supported by mandoc(1), man(1) can fallback on GNU roff
906 from ports (and recommends to install it).
907 To render roff(7) documents, consider using GNU roff from ports or the
908 heirloom doctools roff toolchain from ports via pkg install groff or
909 via pkg install heirloom-doctools.
912 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
913 smaller runtime footprint builds. This is useful for embedded systems
914 which only require one chipset support.
916 If you load it as a module, make sure this is in /boot/loader.conf:
920 This will load the HAL, all chip/RF backends and if_ath_pci.
921 If you have if_ath_pci in /boot/loader.conf, ensure it is after
922 if_ath or it will not load any HAL chipset support.
924 If you want to selectively load things (eg on ye cheape ARM/MIPS
925 platforms where RAM is at a premium) you should:
928 * load the chip modules in question
929 * load ath_rate, ath_dfs
931 * load if_ath_pci and/or if_ath_ahb depending upon your particular
932 bus bind type - this is where probe/attach is done.
934 For further comments/feedback, poke adrian@ .
937 The "ino64" 64-bit inode project has been committed, which extends
938 a number of types to 64 bits. Upgrading in place requires care and
939 adherence to the documented upgrade procedure.
941 If using a custom kernel configuration ensure that the
942 COMPAT_FREEBSD11 option is included (as during the upgrade the
943 system will be running the ino64 kernel with the existing world).
945 For the safest in-place upgrade begin by removing previous build
946 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
947 full procedure documented below under the heading "To rebuild
948 everything and install it on the current system." Specifically,
949 a reboot is required after installing the new kernel before
953 The NATM framework including the en(4), fatm(4), hatm(4), and
954 patm(4) devices has been removed. Consumers should plan a
955 migration before the end-of-life date for FreeBSD 11.
958 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
959 diff has not been implemented, if those are needed a newer version of
960 GNU diff is available via the diffutils package under the gdiff name.
963 As of r316810 for ipfilter, keep frags is no longer assumed when
964 keep state is specified in a rule. r316810 aligns ipfilter with
965 documentation in man pages separating keep frags from keep state.
966 This allows keep state to be specified without forcing keep frags
967 and allows keep frags to be specified independently of keep state.
968 To maintain previous behaviour, also specify keep frags with
969 keep state (as documented in ipf.conf.5).
972 arm64 builds now use the base system LLD 4.0.0 linker by default,
973 instead of requiring that the aarch64-binutils port or package be
974 installed. To continue using aarch64-binutils, set
975 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
978 The UDP optimization in entry 20160818 that added the sysctl
979 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
980 packets will no longer be treated as L3 broadcast packets.
983 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
984 use any explicitly assigned loopback address available in the jail
985 instead of using the first assigned address of the jail.
988 The ctl.ko module no longer implements the iSCSI target frontend:
989 cfiscsi.ko does instead.
991 If building cfiscsi.ko as a kernel module, the module can be loaded
992 via one of the following methods:
993 - `cfiscsi_load="YES"` in loader.conf(5).
994 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
995 - ctladm(8)/ctld(8), when compiled with iSCSI support
996 (`WITH_ISCSI=yes` in src.conf(5))
998 Please see cfiscsi(4) for more details.
1001 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1002 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1003 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1004 missing, but mmcsd.ko now will refuse to load if it is incompatible
1008 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1009 If you have used named states in the firewall rules, you need to modify
1010 them after installworld and before rebooting. Now named states must
1011 be prefixed with colon.
1014 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1015 removed as the userland we provide cannot use them. The KMS version
1016 (sys/dev/drm2) supports the same hardware.
1019 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1020 Please see the 20141231 entry below for information about prerequisites
1021 and upgrading, if you are not already using clang 3.5.0 or higher.
1024 The code that provides support for ZFS .zfs/ directory functionality
1025 has been reimplemented. It's not possible now to create a snapshot
1026 by mkdir under .zfs/snapshot/. That should be the only user visible
1030 EISA bus support has been removed. The WITH_EISA option is no longer
1034 MCA bus support has been removed.
1037 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1038 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1041 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1042 the em(4) driver conforms to iflib specifications.
1045 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1046 IFLIB. If you have a custom kernel configuration that excludes em(4)
1047 but you use igb(4), you need to re-add em(4) to your custom configuration.
1050 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1051 Please see the 20141231 entry below for information about prerequisites
1052 and upgrading, if you are not already using clang 3.5.0 or higher.
1055 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1056 Please see the 20141231 entry below for information about prerequisites
1057 and upgrading, if you are not already using clang 3.5.0 or higher.
1060 The layout of the pmap structure has changed for powerpc to put the pmap
1061 statistics at the front for all CPU variations. libkvm(3) and all tools
1062 that link against it need to be recompiled.
1065 isl(4) and cyapa(4) drivers now require a new driver,
1066 chromebook_platform(4), to work properly on Chromebook-class hardware.
1067 On other types of hardware the drivers may need to be configured using
1068 device hints. Please see the corresponding manual pages for details.
1071 The urtwn(4) driver was merged into rtwn(4) and now consists of
1072 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1074 Also, firmware for RTL8188CE was renamed due to possible name
1075 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1078 GNU rcs has been removed from base. It is available as packages:
1079 - rcs: Latest GPLv3 GNU rcs version.
1080 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1084 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1085 modules now requires that the kernel configuration contain the
1086 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1089 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1090 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1093 Relocatable object files with the extension of .So have been renamed
1094 to use an extension of .pico instead. The purpose of this change is
1095 to avoid a name clash with shared libraries on case-insensitive file
1096 systems. On those file systems, foo.So is the same file as foo.so.
1099 GNU rcs has been turned off by default. It can (temporarily) be built
1100 again by adding WITH_RCS knob in src.conf.
1101 Otherwise, GNU rcs is available from packages:
1102 - rcs: Latest GPLv3 GNU rcs version.
1103 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1106 The backup_uses_rcs functionality has been removed from rc.subr.
1109 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1110 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1111 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1112 QUEUE_MACRO_DEBUG behavior.
1115 r304787 changed some ioctl interfaces between the iSCSI userspace
1116 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1117 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1121 The UDP receive code has been updated to only treat incoming UDP
1122 packets that were addressed to an L2 broadcast address as L3
1123 broadcast packets. It is not expected that this will affect any
1124 standards-conforming UDP application. The new behaviour can be
1125 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1129 Remove the openbsd_poll system call.
1130 __FreeBSD_version has been bumped because of this.
1133 The stable/11 branch has been created from head@r302406.
1136 The libc stub for the pipe(2) system call has been replaced with
1137 a wrapper that calls the pipe2(2) system call and the pipe(2)
1138 system call is now only implemented by the kernels that include
1139 "options COMPAT_FREEBSD10" in their config file (this is the
1140 default). Users should ensure that this option is enabled in
1141 their kernel or upgrade userspace to r302092 before upgrading their
1145 CAM will now strip leading spaces from SCSI disks' serial numbers.
1146 This will affect users who create UFS filesystems on SCSI disks using
1147 those disk's diskid device nodes. For example, if /etc/fstab
1148 previously contained a line like
1149 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1150 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1151 transforms like gmirror may also be affected. ZFS users should
1155 The bitstring(3) API has been updated with new functionality and
1156 improved performance. But it is binary-incompatible with the old API.
1157 Objects built with the new headers may not be linked against objects
1158 built with the old headers.
1161 The brk and sbrk functions have been removed from libc on arm64.
1162 Binutils from ports has been updated to not link to these
1163 functions and should be updated to the latest version before
1164 installing a new libc.
1167 The armv6 port now defaults to hard float ABI. Limited support
1168 for running both hardfloat and soft float on the same system
1169 is available using the libraries installed with -DWITH_LIBSOFT.
1170 This has only been tested as an upgrade path for installworld
1171 and packages may fail or need manual intervention to run. New
1172 packages will be needed.
1174 To update an existing self-hosted armv6hf system, you must add
1175 TARGET_ARCH=armv6 on the make command line for both the build
1176 and the install steps.
1179 Kernel modules compiled outside of a kernel build now default to
1180 installing to /boot/modules instead of /boot/kernel. Many kernel
1181 modules built this way (such as those in ports) already overrode
1182 KMODDIR explicitly to install into /boot/modules. However,
1183 manually building and installing a module from /sys/modules will
1184 now install to /boot/modules instead of /boot/kernel.
1187 The CAM I/O scheduler has been committed to the kernel. There should be
1188 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1189 list of known rogues that claim support for this but actually corrupt
1190 data is believed to be complete, be on the lookout for data
1191 corruption. The known rogue list is believed to be complete:
1193 o Crucial MX100, M550 drives with MU01 firmware.
1194 o Micron M510 and M550 drives with MU01 firmware.
1195 o Micron M500 prior to MU07 firmware
1196 o Samsung 830, 840, and 850 all firmwares
1197 o FCCT M500 all firmwares
1199 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1200 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1201 updated firmware. Black listed drives will work correctly because these
1202 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1203 this list is the same as found in Linux, it's believed there are no
1204 other rogues in the market place. All other models from the above
1207 To be safe, if you are at all concerned, you can quirk each of your
1208 drives to prevent NCQ from being sent by setting:
1209 kern.cam.ada.X.quirks="0x2"
1210 in loader.conf. If the drive requires the 4k sector quirk, set the
1211 quirks entry to 0x3.
1214 The FAST_DEPEND build option has been removed and its functionality is
1215 now the one true way. The old mkdep(1) style of 'make depend' has
1216 been removed. See 20160311 for further details.
1219 Resource range types have grown from unsigned long to uintmax_t. All
1220 drivers, and anything using libdevinfo, need to be recompiled.
1223 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1224 builds. It no longer runs mkdep(1) during 'make depend', and the
1225 'make depend' stage can safely be skipped now as it is auto ran
1226 when building 'make all' and will generate all SRCS and DPSRCS before
1227 building anything else. Dependencies are gathered at compile time with
1228 -MF flags kept in separate .depend files per object file. Users should
1229 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1230 stale .depend files.
1233 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1234 kernel modules. Therefore, if you load any kernel modules at boot time,
1235 please install the boot loaders after you install the kernel, but before
1239 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1240 make installkernel KERNCONF=YOUR_KERNEL_HERE
1241 make -C sys/boot install
1242 <reboot in single user>
1244 Then follow the usual steps, described in the General Notes section,
1248 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1249 see the 20141231 entry below for information about prerequisites and
1250 upgrading, if you are not already using clang 3.5.0 or higher.
1253 The AIO subsystem is now a standard part of the kernel. The
1254 VFS_AIO kernel option and aio.ko kernel module have been removed.
1255 Due to stability concerns, asynchronous I/O requests are only
1256 permitted on sockets and raw disks by default. To enable
1257 asynchronous I/O requests on all file types, set the
1258 vfs.aio.enable_unsafe sysctl to a non-zero value.
1261 The ELF object manipulation tool objcopy is now provided by the
1262 ELF Tool Chain project rather than by GNU binutils. It should be a
1263 drop-in replacement, with the addition of arm64 support. The
1264 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1265 to obtain the GNU version if necessary.
1268 Building ZFS pools on top of zvols is prohibited by default. That
1269 feature has never worked safely; it's always been prone to deadlocks.
1270 Using a zvol as the backing store for a VM guest's virtual disk will
1271 still work, even if the guest is using ZFS. Legacy behavior can be
1272 restored by setting vfs.zfs.vol.recursive=1.
1275 The NONE and HPN patches has been removed from OpenSSH. They are
1276 still available in the security/openssh-portable port.
1279 With the addition of ypldap(8), a new _ypldap user is now required
1280 during installworld. "mergemaster -p" can be used to add the user
1281 prior to installworld, as documented in the handbook.
1284 The tftp loader (pxeboot) now uses the option root-path directive. As a
1285 consequence it no longer looks for a pxeboot.4th file on the tftp
1286 server. Instead it uses the regular /boot infrastructure as with the
1290 The code to start recording plug and play data into the modules has
1291 been committed. While the old tools will properly build a new kernel,
1292 a number of warnings about "unknown metadata record 4" will be produced
1293 for an older kldxref. To avoid such warnings, make sure to rebuild
1294 the kernel toolchain (or world). Make sure that you have r292078 or
1295 later when trying to build 292077 or later before rebuilding.
1298 Debug data files are now built by default with 'make buildworld' and
1299 installed with 'make installworld'. This facilitates debugging but
1300 requires more disk space both during the build and for the installed
1301 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1305 r291527 changed the internal interface between the nfsd.ko and
1306 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1307 __FreeBSD_version has been bumped because of this.
1310 Add support for unicode collation strings leads to a change of
1311 order of files listed by ls(1) for example. To get back to the old
1312 behaviour, set LC_COLLATE environment variable to "C".
1314 Databases administrators will need to reindex their databases given
1315 collation results will be different.
1317 Due to a bug in install(1) it is recommended to remove the ancient
1318 locales before running make installworld.
1320 rm -rf /usr/share/locale/*
1323 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1324 libcrypto.so.7 or libssl.so.7 must be recompiled.
1327 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1328 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1329 should be replaced with isp_2400 and isp_2500 modules respectively.
1332 The build previously allowed using 'make -n' to not recurse into
1333 sub-directories while showing what commands would be executed, and
1334 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1335 and 'make -N' will not.
1338 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1339 and etcupdate will now use this file. A custom sendmail.cf is now
1340 updated via this mechanism rather than via installworld. If you had
1341 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1342 want to remove the exclusion or change it to "always install".
1343 /etc/mail/sendmail.cf is now managed the same way regardless of
1344 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1345 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1348 Compatibility shims for legacy ATA device names have been removed.
1349 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1350 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1351 environment variables, /dev/ad* and /dev/ar* symbolic links.
1354 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1355 Please see the 20141231 entry below for information about prerequisites
1356 and upgrading, if you are not already using clang 3.5.0 or higher.
1359 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1360 and renamed from .symbols to .debug. This reduces the size requirements
1361 on the boot partition or file system and provides consistency with
1362 userland debug files.
1364 When using the supported kernel installation method the
1365 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1366 as is done with /boot/kernel.
1368 Developers wishing to maintain the historical behavior of installing
1369 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1372 The wireless drivers had undergone changes that remove the 'parent
1373 interface' from the ifconfig -l output. The rc.d network scripts
1374 used to check presence of a parent interface in the list, so old
1375 scripts would fail to start wireless networking. Thus, etcupdate(3)
1376 or mergemaster(8) run is required after kernel update, to update your
1377 rc.d scripts in /etc.
1380 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1381 These configurations are now automatically interpreted as
1382 'scrub fragment reassemble'.
1385 Kernel-loadable modules for the random(4) device are back. To use
1386 them, the kernel must have
1389 options RANDOM_LOADABLE
1391 kldload(8) can then be used to load random_fortuna.ko
1392 or random_yarrow.ko. Please note that due to the indirect
1393 function calls that the loadable modules need to provide,
1394 the build-in variants will be slightly more efficient.
1396 The random(4) kernel option RANDOM_DUMMY has been retired due to
1397 unpopularity. It was not all that useful anyway.
1400 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1401 Control over building the ELF Tool Chain tools is now provided by
1402 the WITHOUT_TOOLCHAIN knob.
1405 The polarity of Pulse Per Second (PPS) capture events with the
1406 uart(4) driver has been corrected. Prior to this change the PPS
1407 "assert" event corresponded to the trailing edge of a positive PPS
1408 pulse and the "clear" event was the leading edge of the next pulse.
1410 As the width of a PPS pulse in a typical GPS receiver is on the
1411 order of 1 millisecond, most users will not notice any significant
1412 difference with this change.
1414 Anyone who has compensated for the historical polarity reversal by
1415 configuring a negative offset equal to the pulse width will need to
1416 remove that workaround.
1419 The default group assigned to /dev/dri entries has been changed
1420 from 'wheel' to 'video' with the id of '44'. If you want to have
1421 access to the dri devices please add yourself to the video group
1424 # pw groupmod video -m $USER
1427 The menu.rc and loader.rc files will now be replaced during
1428 upgrades. Please migrate local changes to menu.rc.local and
1429 loader.rc.local instead.
1432 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1433 strings and strip have been removed. The src.conf(5) knob
1434 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1437 As ZFS requires more kernel stack pages than is the default on some
1438 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1439 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1441 Please consider using 'options KSTACK_PAGES=X' where X is greater
1442 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1445 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1446 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1447 default, i.e., they will not contain "::". For example, instead
1448 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1449 to have a more specific match, such as different map entries for
1450 IPv6:0:0 vs IPv6:0. This change requires that configuration
1451 data (including maps, files, classes, custom ruleset, etc.) must
1452 use the same format, so make certain such configuration data is
1453 upgrading. As a very simple check search for patterns like
1454 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1455 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1456 the cf option UseCompressedIPv6Addresses.
1459 The default kernel entropy-processing algorithm is now
1460 Fortuna, replacing Yarrow.
1462 Assuming you have 'device random' in your kernel config
1463 file, the configurations allow a kernel option to override
1464 this default. You may choose *ONE* of:
1466 options RANDOM_YARROW # Legacy /dev/random algorithm.
1467 options RANDOM_DUMMY # Blocking-only driver.
1469 If you have neither, you get Fortuna. For most people,
1470 read no further, Fortuna will give a /dev/random that works
1471 like it always used to, and the difference will be irrelevant.
1473 If you remove 'device random', you get *NO* kernel-processed
1474 entropy at all. This may be acceptable to folks building
1475 embedded systems, but has complications. Carry on reading,
1476 and it is assumed you know what you need.
1478 *PLEASE* read random(4) and random(9) if you are in the
1479 habit of tweaking kernel configs, and/or if you are a member
1480 of the embedded community, wanting specific and not-usual
1481 behaviour from your security subsystems.
1483 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1484 random', you will NOT have a functioning /dev/random, and
1485 many cryptographic features will not work, including SSH.
1486 You may also find strange behaviour from the random(3) set
1487 of library functions, in particular sranddev(3), srandomdev(3)
1488 and arc4random(3). The reason for this is that the KERN_ARND
1489 sysctl only returns entropy if it thinks it has some to
1490 share, and with RANDOM_DUMMY or no 'device random' this
1494 An additional fix for the issue described in the 20150614 sendmail
1495 entry below has been committed in revision 284717.
1498 FreeBSD's old make (fmake) has been removed from the system. It is
1499 available as the devel/fmake port or via pkg install fmake.
1502 The fix for the issue described in the 20150614 sendmail entry
1503 below has been committed in revision 284436. The work
1504 around described in that entry is no longer needed unless the
1505 default setting is overridden by a confDH_PARAMETERS configuration
1506 setting of '5' or pointing to a 512 bit DH parameter file.
1509 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1510 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1511 and devel/kyua to version 0.20+ and adjust any calling code to work
1512 with Kyuafile and kyua.
1515 The import of openssl to address the FreeBSD-SA-15:10.openssl
1516 security advisory includes a change which rejects handshakes
1517 with DH parameters below 768 bits. sendmail releases prior
1518 to 8.15.2 (not yet released), defaulted to a 512 bit
1519 DH parameter setting for client connections. To work around
1520 this interoperability, sendmail can be configured to use a
1521 2048 bit DH parameter by:
1523 1. Edit /etc/mail/`hostname`.mc
1524 2. If a setting for confDH_PARAMETERS does not exist or
1525 exists and is set to a string beginning with '5',
1526 replace it with '2'.
1527 3. If a setting for confDH_PARAMETERS exists and is set to
1528 a file path, create a new file with:
1529 openssl dhparam -out /path/to/file 2048
1530 4. Rebuild the .cf file:
1531 cd /etc/mail/; make; make install
1532 5. Restart sendmail:
1533 cd /etc/mail/; make restart
1535 A sendmail patch is coming, at which time this file will be
1539 Generation of legacy formatted entries have been disabled by default
1540 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1541 entries were converted to use the new format by default when the new,
1542 machine independent format have been added and supported since FreeBSD
1545 Please see the pwd_mkdb(8) manual page for further details.
1548 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1549 20141231 entry below for information about prerequisites and upgrading,
1550 if you are not already using 3.5.0 or higher.
1553 TI platform code switched to using vendor DTS files and this update
1554 may break existing systems running on Beaglebone, Beaglebone Black,
1557 - dtb files should be regenerated/reinstalled. Filenames are the
1558 same but content is different now
1559 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1560 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1561 addressing scheme is now pin 25 on /dev/gpioc3.
1562 - Pandaboard: /etc/ttys should be updated, serial console device is
1563 now /dev/ttyu2, not /dev/ttyu0
1566 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1567 If you need the GNU extension from groff soelim(1), install groff
1568 from package: pkg install groff, or via ports: textproc/groff.
1571 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1572 defined in symlink(7); previously symlinks were silently ignored.
1575 The const qualifier has been removed from iconv(3) to comply with
1576 POSIX. The ports tree is aware of this from r384038 onwards.
1579 Libraries specified by LIBADD in Makefiles must have a corresponding
1580 DPADD_<lib> variable to ensure correct dependencies. This is now
1581 enforced in src.libnames.mk.
1584 From legacy ata(4) driver was removed support for SATA controllers
1585 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1586 Kernel modules ataahci and ataadaptec were removed completely,
1587 replaced by ahci and mvs modules respectively.
1590 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1591 the 20141231 entry below for information about prerequisites and
1592 upgrading, if you are not already using 3.5.0 or higher.
1595 The 32-bit PowerPC kernel has been changed to a position-independent
1596 executable. This can only be booted with a version of loader(8)
1597 newer than January 31, 2015, so make sure to update both world and
1598 kernel before rebooting.
1601 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1602 but before r278950, the RNG was not seeded properly. Immediately
1603 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1604 ssh keys or openssl keys) that were generated w/ a kernel from that
1605 range. This does not affect programs that directly used /dev/random
1606 or /dev/urandom. All userland uses of arc4random(3) are affected.
1609 The autofs(4) ABI was changed in order to restore binary compatibility
1610 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1611 with the new kernel.
1614 The powerpc64 kernel has been changed to a position-independent
1615 executable. This can only be booted with a new version of loader(8),
1616 so make sure to update both world and kernel before rebooting.
1619 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1620 only release, no new features have been added. Please see the 20141231
1621 entry below for information about prerequisites and upgrading, if you
1622 are not already using 3.5.0.
1625 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1626 taken from the ELF Tool Chain project rather than GNU binutils. They
1627 should be drop-in replacements, with the addition of arm64 support.
1628 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1629 binutils tools, if necessary. See 20150805 for updated information.
1632 The default Unbound configuration now enables remote control
1633 using a local socket. Users who have already enabled the
1634 local_unbound service should regenerate their configuration
1635 by running "service local_unbound setup" as root.
1638 The GNU texinfo and GNU info pages have been removed.
1639 To be able to view GNU info pages please install texinfo from ports.
1642 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1644 As of this release, a prerequisite for building clang, llvm and lldb is
1645 a C++11 capable compiler and C++11 standard library. This means that to
1646 be able to successfully build the cross-tools stage of buildworld, with
1647 clang as the bootstrap compiler, your system compiler or cross compiler
1648 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1649 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1652 On any standard FreeBSD 10.x or 11.x installation, where clang and
1653 libc++ are on by default (that is, on x86 or arm), this should work out
1656 On 9.x installations where clang is enabled by default, e.g. on x86 and
1657 powerpc, libc++ will not be enabled by default, so libc++ should be
1658 built (with clang) and installed first. If both clang and libc++ are
1659 missing, build clang first, then use it to build libc++.
1661 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1662 the instructions for 9.x above.
1664 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1665 default, and do not build clang.
1667 Many embedded systems are resource constrained, and will not be able to
1668 build clang in a reasonable time, or in some cases at all. In those
1669 cases, cross building bootable systems on amd64 is a workaround.
1671 This new version of clang introduces a number of new warnings, of which
1672 the following are most likely to appear:
1676 This warns in two cases, for both C and C++:
1677 * When the code is trying to take the absolute value of an unsigned
1678 quantity, which is effectively a no-op, and almost never what was
1679 intended. The code should be fixed, if at all possible. If you are
1680 sure that the unsigned quantity can be safely cast to signed, without
1681 loss of information or undefined behavior, you can add an explicit
1682 cast, or disable the warning.
1684 * When the code is trying to take an absolute value, but the called
1685 abs() variant is for the wrong type, which can lead to truncation.
1686 If you want to disable the warning instead of fixing the code, please
1687 make sure that truncation will not occur, or it might lead to unwanted
1690 -Wtautological-undefined-compare and
1691 -Wundefined-bool-conversion
1693 These warn when C++ code is trying to compare 'this' against NULL, while
1694 'this' should never be NULL in well-defined C++ code. However, there is
1695 some legacy (pre C++11) code out there, which actively abuses this
1696 feature, which was less strictly defined in previous C++ versions.
1698 Squid and openjdk do this, for example. The warning can be turned off
1699 for C++98 and earlier, but compiling the code in C++11 mode might result
1700 in unexpected behavior; for example, the parts of the program that are
1701 unreachable could be optimized away.
1704 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1705 kernel sources have been removed. The .h files remain, since some
1706 utilities include them. This will need to be fixed later.
1707 If "mount -t oldnfs ..." is attempted, it will fail.
1708 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1709 the utilities will report errors.
1712 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1713 directories to top level SUBDIR variable when their parent
1714 directory is included in LOCAL_DIRS. Users with build systems with
1715 such hierarchies and without SUBDIR entries in the parent
1716 directory Makefiles should add them or add the directories to
1720 faith(4) and faithd(8) have been removed from the base system. Faith
1721 has been obsolete for a very long time.
1724 vt(4), the new console driver, is enabled by default. It brings
1725 support for Unicode and double-width characters, as well as
1726 support for UEFI and integration with the KMS kernel video
1729 You may need to update your console settings in /etc/rc.conf,
1730 most probably the keymap. During boot, /etc/rc.d/syscons will
1731 indicate what you need to do.
1733 vt(4) still has issues and lacks some features compared to
1734 syscons(4). See the wiki for up-to-date information:
1735 https://wiki.freebsd.org/Newcons
1737 If you want to keep using syscons(4), you can do so by adding
1738 the following line to /boot/loader.conf:
1742 pjdfstest has been integrated into kyua as an opt-in test suite.
1743 Please see share/doc/pjdfstest/README for more details on how to
1747 gperf has been removed from the base system for architectures
1748 that use clang. Ports that require gperf will obtain it from the
1752 pjdfstest has been moved from tools/regression/pjdfstest to
1756 At svn r271982, The default linux compat kernel ABI has been adjusted
1757 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1758 update. If you wish to continue using the linux-f10 compat ports,
1759 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1760 encouraged to update their linux-compat packages to linux-c6 during
1761 their next update cycle.
1764 The ofwfb driver, used to provide a graphics console on PowerPC when
1765 using vt(4), no longer allows mmap() of all physical memory. This
1766 will prevent Xorg on PowerPC with some ATI graphics cards from
1767 initializing properly unless x11-servers/xorg-server is updated to
1771 The xdev targets have been converted to using TARGET and
1772 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1775 The default unbound configuration has been modified to address
1776 issues with reverse lookups on networks that use private
1777 address ranges. If you use the local_unbound service, run
1778 "service local_unbound setup" as root to regenerate your
1779 configuration, then "service local_unbound reload" to load the
1783 The GNU texinfo and GNU info pages are not built and installed
1784 anymore, WITH_INFO knob has been added to allow to built and install
1786 UPDATE: see 20150102 entry on texinfo's removal
1789 The GNU readline library is now an INTERNALLIB - that is, it is
1790 statically linked into consumers (GDB and variants) in the base
1791 system, and the shared library is no longer installed. The
1792 devel/readline port is available for third party software that
1796 The Itanium architecture (ia64) has been removed from the list of
1797 known architectures. This is the first step in the removal of the
1801 Commit r268115 has added NFSv4.1 server support, merged from
1802 projects/nfsv4.1-server. Since this includes changes to the
1803 internal interfaces between the NFS related modules, a full
1804 build of the kernel and modules will be necessary.
1805 __FreeBSD_version has been bumped.
1808 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1809 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1810 which differs from the behaviour controlled by this knob.)
1813 Maximal length of the serial number in CTL was increased from 16 to
1814 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1815 and ctld, need to be rebuilt to work with a new kernel.
1818 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1819 1 respectively to match the upstream numbers. They were out of
1820 sync because, when they were originally added to FreeBSD, the
1821 upstream versions were not respected. These libraries are private
1822 and not yet built by default, so renumbering them should be a
1823 non-issue. However, unclean source trees will yield broken test
1824 programs once the operator executes "make delete-old-libs" after a
1825 "make installworld".
1827 Additionally, the atf-sh binary was made private by moving it into
1828 /usr/libexec/. Already-built shell test programs will keep the
1829 path to the old binary so they will break after "make delete-old"
1832 If you are using WITH_TESTS=yes (not the default), wipe the object
1833 tree and rebuild from scratch to prevent spurious test failures.
1834 This is only needed once: the misnumbered libraries and misplaced
1835 binaries have been added to OptionalObsoleteFiles.inc so they will
1836 be removed during a clean upgrade.
1839 Clang and llvm have been upgraded to 3.4.1 release.
1842 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1843 be removed to avoid issues in the future (and has been added to
1847 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1848 past, it affected all builds that used the bsd.*.mk files. The old
1849 behavior was a bug, but people may have relied upon it. To get this
1850 behavior back, you can .include /etc/src.conf from /etc/make.conf
1851 (which is still global and isn't changed). This also changes the
1852 behavior of incremental builds inside the tree of individual
1853 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1854 Although this has survived make universe and some upgrade scenarios,
1855 other upgrade scenarios may have broken. At least one form of
1856 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1857 as well... In cases where MAKESYSPATH isn't working with this
1858 setting, you'll need to set it to the full path to your tree.
1860 One side effect of all this cleaning up is that bsd.compiler.mk
1861 is no longer implicitly included by bsd.own.mk. If you wish to
1862 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1866 The lindev device has been removed since /dev/full has been made a
1867 standard device. __FreeBSD_version has been bumped.
1870 The knob WITHOUT_VI was added to the base system, which controls
1871 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1872 in order to reorder files share/termcap and didn't build ex(1) as a
1873 build tool, so building/installing with WITH_VI is highly advised for
1874 build hosts for older releases.
1876 This issue has been fixed in stable/9 and stable/10 in r277022 and
1877 r276991, respectively.
1880 The YES_HESIOD knob has been removed. It has been obsolete for
1881 a decade. Please move to using WITH_HESIOD instead or your builds
1882 will silently lack HESIOD.
1885 The uart(4) driver has been changed with respect to its handling
1886 of the low-level console. Previously the uart(4) driver prevented
1887 any process from changing the baudrate or the CLOCAL and HUPCL
1888 control flags. By removing the restrictions, operators can make
1889 changes to the serial console port without having to reboot.
1890 However, when getty(8) is started on the serial device that is
1891 associated with the low-level console, a misconfigured terminal
1892 line in /etc/ttys will now have a real impact.
1893 Before upgrading the kernel, make sure that /etc/ttys has the
1894 serial console device configured as 3wire without baudrate to
1895 preserve the previous behaviour. E.g:
1896 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1899 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1900 to improve performance. To re-enable it, if needed, run rpcbind
1901 with command line option -W.
1904 Switched back to the GPL dtc compiler due to updates in the upstream
1905 dts files not being supported by the BSDL dtc compiler. You will need
1906 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1907 may result while building dtb files during a kernel build if you fail
1908 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1911 Clang and llvm have been upgraded to 3.4 release.
1914 The nve(4) driver has been removed. Please use the nfe(4) driver
1915 for NVIDIA nForce MCP Ethernet adapters instead.
1918 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1919 This could cause certain C++ applications using shared libraries built
1920 against the previous version of libc++ to crash. The incompatibility
1921 has now been fixed, but any C++ applications or shared libraries built
1922 between r261283 and r261801 should be recompiled.
1925 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1926 capability mode support. Please note that enabling the feature in
1927 kernel is still highly recommended.
1930 OpenSSH is now built with sandbox support, and will use sandbox as
1931 the default privilege separation method. This requires Capsicum
1932 capability mode support in kernel.
1935 The libelf and libdwarf libraries have been updated to newer
1936 versions from upstream. Shared library version numbers for
1937 these two libraries were bumped. Any ports or binaries
1938 requiring these two libraries should be recompiled.
1939 __FreeBSD_version is bumped to 1100006.
1942 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1943 instead of providing an explicit one, this would prevent such
1944 Makefile from providing its own Kyuafile in the future during
1945 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1946 intervention is needed to clean an objdir if you use NO_CLEAN:
1947 # find /usr/obj -name Kyuafile | xargs rm -f
1950 The behavior of gss_pseudo_random() for the krb5 mechanism
1951 has changed, for applications requesting a longer random string
1952 than produced by the underlying enctype's pseudo-random() function.
1953 In particular, the random string produced from a session key of
1954 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1955 be different at the 17th octet and later, after this change.
1956 The counter used in the PRF+ construction is now encoded as a
1957 big-endian integer in accordance with RFC 4402.
1958 __FreeBSD_version is bumped to 1100004.
1961 The WITHOUT_ATF build knob has been removed and its functionality
1962 has been subsumed into the more generic WITHOUT_TESTS. If you were
1963 using the former to disable the build of the ATF libraries, you
1964 should change your settings to use the latter.
1967 The default version of mtree is nmtree which is obtained from
1968 NetBSD. The output is generally the same, but may vary
1969 slightly. If you found you need identical output adding
1970 "-F freebsd9" to the command line should do the trick. For the
1971 time being, the old mtree is available as fmtree.
1974 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1975 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1976 1.1.4_8 and verify bsdyml not linked in, before running "make
1978 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1980 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1983 The stable/10 branch has been created in subversion from head
1990 Avoid using make -j when upgrading. While generally safe, there are
1991 sometimes problems using -j to upgrade. If your upgrade fails with
1992 -j, please try again without -j. From time to time in the past there
1993 have been problems using -j with buildworld and/or installworld. This
1994 is especially true when upgrading between "distant" versions (eg one
1995 that cross a major release boundary or several minor releases, or when
1996 several months have passed on the -current branch).
1998 Sometimes, obscure build problems are the result of environment
1999 poisoning. This can happen because the make utility reads its
2000 environment when searching for values for global variables. To run
2001 your build attempts in an "environmental clean room", prefix all make
2002 commands with 'env -i '. See the env(1) manual page for more details.
2004 When upgrading from one major version to another it is generally best to
2005 upgrade to the latest code in the currently installed branch first, then
2006 do an upgrade to the new branch. This is the best-tested upgrade path,
2007 and has the highest probability of being successful. Please try this
2008 approach if you encounter problems with a major version upgrade. Since
2009 the stable 4.x branch point, one has generally been able to upgrade from
2010 anywhere in the most recent stable branch to head / current (or even the
2011 last couple of stable branches). See the top of this file when there's
2014 When upgrading a live system, having a root shell around before
2015 installing anything can help undo problems. Not having a root shell
2016 around can lead to problems if pam has changed too much from your
2017 starting point to allow continued authentication after the upgrade.
2019 This file should be read as a log of events. When a later event changes
2020 information of a prior event, the prior event should not be deleted.
2021 Instead, a pointer to the entry with the new information should be
2022 placed in the old entry. Readers of this file should also sanity check
2023 older entries before relying on them blindly. Authors of new entries
2024 should write them with this in mind.
2028 When upgrading the boot ZFS pool to a new version, always follow
2031 1.) recompile and reinstall the ZFS boot loader and boot block
2032 (this is part of "make buildworld" and "make installworld")
2034 2.) update the ZFS boot block on your boot drive
2036 The following example updates the ZFS boot block on the first
2037 partition (freebsd-boot) of a GPT partitioned drive ada0:
2038 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2040 Non-boot pools do not need these updates.
2044 If you are updating from a prior version of FreeBSD (even one just
2045 a few days old), you should follow this procedure. It is the most
2046 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2048 make kernel-toolchain
2049 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2050 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2052 To test a kernel once
2053 ---------------------
2054 If you just want to boot a kernel once (because you are not sure
2055 if it works, or if you want to boot a known bad kernel to provide
2056 debugging information) run
2057 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2058 nextboot -k testkernel
2060 To rebuild everything and install it on the current system.
2061 -----------------------------------------------------------
2062 # Note: sometimes if you are running current you gotta do more than
2063 # is listed here if you are upgrading from a really old current.
2065 <make sure you have good level 0 dumps>
2067 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2068 make installkernel KERNCONF=YOUR_KERNEL_HERE
2070 <reboot in single user> [3]
2077 To cross-install current onto a separate partition
2078 --------------------------------------------------
2079 # In this approach we use a separate partition to hold
2080 # current's root, 'usr', and 'var' directories. A partition
2081 # holding "/", "/usr" and "/var" should be about 2GB in
2084 <make sure you have good level 0 dumps>
2087 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2088 <maybe newfs current's root partition>
2089 <mount current's root partition on directory ${CURRENT_ROOT}>
2090 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2091 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2092 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2093 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2094 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2095 <reboot into current>
2096 <do a "native" rebuild/install as described in the previous section>
2097 <maybe install compatibility libraries from ports/misc/compat*>
2101 To upgrade in-place from stable to current
2102 ----------------------------------------------
2103 <make sure you have good level 0 dumps>
2105 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2106 make installkernel KERNCONF=YOUR_KERNEL_HERE
2108 <reboot in single user> [3]
2115 Make sure that you've read the UPDATING file to understand the
2116 tweaks to various things you need. At this point in the life
2117 cycle of current, things change often and you are on your own
2118 to cope. The defaults can also change, so please read ALL of
2119 the UPDATING entries.
2121 Also, if you are tracking -current, you must be subscribed to
2122 freebsd-current@freebsd.org. Make sure that before you update
2123 your sources that you have read and understood all the recent
2124 messages there. If in doubt, please track -stable which has
2125 much fewer pitfalls.
2127 [1] If you have third party modules, such as vmware, you
2128 should disable them at this point so they don't crash your
2131 [3] From the bootblocks, boot -s, and then do
2136 adjkerntz -i # if CMOS is wall time
2137 Also, when doing a major release upgrade, it is required that
2138 you boot into single user mode to do the installworld.
2140 [4] Note: This step is non-optional. Failure to do this step
2141 can result in a significant reduction in the functionality of the
2142 system. Attempting to do it by hand is not recommended and those
2143 that pursue this avenue should read this file carefully, as well
2144 as the archives of freebsd-current and freebsd-hackers mailing lists
2145 for potential gotchas. The -U option is also useful to consider.
2146 See mergemaster(8) for more information.
2148 [5] Usually this step is a no-op. However, from time to time
2149 you may need to do this if you get unknown user in the following
2150 step. It never hurts to do it all the time. You may need to
2151 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2152 install) after the buildworld before this step if you last updated
2153 from current before 20130425 or from -stable before 20130430.
2155 [6] This only deletes old files and directories. Old libraries
2156 can be deleted by "make delete-old-libs", but you have to make
2157 sure that no program is using those libraries anymore.
2159 [8] The new kernel must be able to run existing binaries used by
2160 an installworld. When upgrading across major versions, the new
2161 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2162 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2163 binaries). Failure to do so may leave you with a system that is
2164 hard to boot to recover. A GENERIC kernel will include suitable
2165 compatibility options to run binaries from older branches.
2167 Make sure that you merge any new devices from GENERIC since the
2168 last time you updated your kernel config file.
2170 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2171 "?=" instead of the "=" assignment operator, so that buildworld can
2172 override the CPUTYPE if it needs to.
2174 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2175 not on the command line, or in /etc/make.conf. buildworld will
2176 warn if it is improperly defined.
2179 This file contains a list, in reverse chronological order, of major
2180 breakages in tracking -current. It is not guaranteed to be a complete
2181 list of such breakages, and only contains entries since September 23, 2011.
2182 If you need to see UPDATING entries from before that date, you will need
2183 to fetch an UPDATING file from an older FreeBSD release.
2185 Copyright information:
2187 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2189 Redistribution, publication, translation and use, with or without
2190 modification, in full or in part, in any form or format of this
2191 document are permitted without further permission from the author.
2193 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2194 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2195 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2196 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2197 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2198 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2199 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2200 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2201 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2202 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2203 POSSIBILITY OF SUCH DAMAGE.
2205 Contact Warner Losh if you have any questions about your use of