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 20201208: p2 FreeBSD-SA-20:33.openssl
21 Fix OpenSSL NULL pointer de-reference. [SA-20:33.openssl]
23 20201201: p1 FreeBSD-EN-20:19.audit
24 FreeBSD-EN-20:20.tzdata
26 FreeBSD-EN-20:22.callout
27 FreeBSD-SA-20:31.icmp6
28 FreeBSD-SA-20:32.rtsold
30 Fix execve/fexecve system call auditing. [EN-20:19.audit]
32 Update timezone database information. [EN-20:20.tzdata]
34 Fix uninitialized variable in ipfw. [EN-20:21.ipfw]
36 Fix race condition in callout CPU migration. [EN-20:22.callout]
38 Fix ICMPv6 use-after-free in error message handling. [SA-20:31.icmp6]
40 Fix multiple vulnerabilities in rtsold. [SA-20:32.rtsold]
45 20200915: p1 FreeBSD-SA-20:27.ure
46 FreeBSD-SA-20:28.bhyve_vmcs
47 FreeBSD-SA-20:29.bhyve_svm
50 Fix ure device driver susceptible to packet-in-packet attack.
53 Fix bhyve privilege escalation via VMCS access. [SA-20:28.bhyve_vmcs]
55 Fix bhyve SVM guest escape. [SA-20:29.bhyve_svm]
57 Fix ftpd privilege escalation via ftpchroot. [SA-20:30.ftpd]
60 The make.conf(5) MALLOC_PRODUCTION variable, used for disabling and
61 enabling assertions and statistics gathering in malloc(3), has been
62 migrated to a src.conf(5) WITH/WITHOUT_MALLOC_PRODUCTION option.
64 On stable branches, WITH_MALLOC_PRODUCTION is set by default, which
65 means that malloc(3) has assertions and statistics gathering disabled,
66 for improved performance.
68 For backwards compatibility, the make.conf(5) MALLOC_PRODUCTION is still
69 honored, but it is now deprecated and undocumented.
72 The resume code now notifies devd with the 'kernel' system
73 rather than the old 'kern' subsystem to be consistent with
74 other use. The old notification will be created as well, but
75 will be removed prior to FreeBSD 14.0.
78 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
79 been upgraded to 10.0.1. Please see the 20141231 entry below for
80 information about prerequisites and upgrading, if you are not already
81 using clang 3.5.0 or higher.
84 read(2) of a directory fd is now rejected by default. root may
85 re-enable it for the entire system with the
86 security.bsd.allow_read_dir sysctl(8) MIB.
88 It may be advised to setup aliases for grep to default to `-d skip` if
89 commonly non-recursively grepping a list that includes directories and
90 the potential for the resulting stderr output is not tolerable. Example
91 aliases are now installed, commented out, in /root/.cshrc.
94 Upstream DTS from Linux 5.6 was merged and they now have the SID
95 and THS (Secure ID controller and THermal Sensor) node present.
96 The DTB overlays have now been removed from the tree for the H3/H5 and
97 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
98 deal with upstream DTS. If you are using those overlays you need to
99 remove them from loader.conf and update the DTBs on the FAT partition.
102 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
103 been upgraded to 10.0.0. Please see the 20141231 entry below for
104 information about prerequisites and upgrading, if you are not already
105 using clang 3.5.0 or higher.
108 The root certificates of the Mozilla CA Certificate Store have been
109 imported into the base system and can be managed with the certctl(8)
110 utility. If you have installed the security/ca_root_nss port or package
111 with the ETCSYMLINK option (the default), be advised that there may be
112 differences between those included in the port and those included in
113 base due to differences in nss branch used as well as general update
114 frequency. Note also that certctl(8) cannot manage certs in the
115 format used by the security/ca_root_nss port.
118 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
119 been upgraded to 9.0.1. Please see the 20141231 entry below for
120 information about prerequisites and upgrading, if you are not already
121 using clang 3.5.0 or higher.
124 The nctgpio and wbwd drivers have been moved to the superio bus.
125 If you have one of these drivers in a kernel configuration, then
126 you should add device superio to it. If you use one of these drivers
127 as a module and you compile a custom set of modules, then you should
128 add superio to the set.
131 The tap(4) driver has been folded into tun(4), and the module has been
132 renamed to tuntap. You should update any kld_list="if_tap" or
133 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
134 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
135 module instead, and "device tap" or "device tun" entries in kernel
136 config files to select the tuntap device instead.
139 ntpd no longer by default locks its pages in memory, allowing them
140 to be paged out by the kernel. Use rlimit memlock to restore
141 historic BSD behaviour. For example, add "rlimit memlock 32"
142 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
145 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
146 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
147 been removed from mount_fusefs(8). You can safely remove them from
148 your scripts, because they had no effect.
150 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
151 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
152 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
153 sysctls have been removed. If you felt the need to set any of them to
154 a non-default value, please tell asomers@FreeBSD.org why.
157 The fuse(4) module has been renamed to fusefs(4) for consistency with
158 other filesystems. You should update any kld_load="fuse" entries in
159 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
160 "options FUSE" enties in kernel config files.
163 Default permissions on the /var/account/acct file (and copies of it
164 rotated by periodic daily scripts) are changed from 0644 to 0640
165 because the file contains sensitive information that should not be
166 world-readable. If the /var/account directory must be created by
167 rc.d/accounting, the mode used is now 0750. Admins who use the
168 accounting feature are encouraged to change the mode of an existing
169 /var/account directory to 0750 or 0700.
172 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
173 been upgraded to 8.0.1. Please see the 20141231 entry below for
174 information about prerequisites and upgrading, if you are not already
175 using clang 3.5.0 or higher.
178 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
179 functionality needed for the RETPOLINE option should work properly
180 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
183 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
184 8.0.0. Please see the 20141231 entry below for information about
185 prerequisites and upgrading, if you are not already using clang 3.5.0
189 The RETPOLINE option produces non-functional ifunc-using binaries
190 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
191 Once Clang 8 is merged it may be enabled again.
194 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
195 7.0.1. Please see the 20141231 entry below for information about
196 prerequisites and upgrading, if you are not already using clang 3.5.0
200 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
201 compiled into your custom kernel, add 'device xz' statement to the
205 Iflib is no longer unconditionally compiled into the kernel. Drivers
206 using iflib and statically compiled into the kernel, now require
207 the 'device iflib' config option. For the same drivers loaded as
208 modules on kernels not having 'device iflib', the iflib.ko module
209 is loaded automatically.
212 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
213 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
214 servers that have vfs.nfsd.nfs_privport set will only allow mounts
215 from clients using a reserved port#. Since both the FreeBSD and Linux
216 NFSv4 clients use reserved port#s by default, this should not affect
220 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
221 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
222 it produces broken binaries when ifuncs are in use. Users needing
223 GNU ld should install the binutils port or package.
226 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
227 has been converted to a port (misc/ctm) and will be removed from
228 FreeBSD-13. A depreciation warning will be printed to stderr by
229 the ctm command, but the functionality will remain in base for all
233 The stable/12 branch has been created in subversion from head
237 Ports for the DRM modules have been simplified. Now, amd64 users should
238 just install the drm-kmod port. All others should install
241 Graphics hardware that's newer than about 2010 usually works with
242 drm-kmod. For hardware older than 2013, however, some users will need
243 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
244 than 2008 usually only works in drm-legacy-kmod. The graphics team can
245 only commit to hardware made since 2013 due to the complexity of the
246 market and difficulty to test all the older cards effectively. If you
247 have hardware supported by drm-kmod, you are strongly encouraged to use
248 that as you will get better support.
250 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
251 elsewhere, the drm and drm2 modules will be eliminated from the src base
252 soon (with a limited exception for arm). Please update to the package asap
253 and report any issues to x11@freebsd.org.
255 Generally, anybody using the drm*-kmod packages should add
256 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
257 cross-threading surprises, especially with automatic driver
258 loading from X11 startup. These will become the defaults in 13-current
262 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
263 custom kernel and module loading configuration files must be updated
264 accordingly. Moreover, interfaces previous presented as ixlvN to the
265 system are now exposed as iavfN and network configuration files must
266 be adjusted as necessary.
269 OpenSSL has been updated to version 1.1.1. This update included
270 additional various API changes througout the base system. It is
271 important to rebuild third-party software after upgrading. The value
272 of __FreeBSD_version has been bumped accordingly.
275 The legacy DRM modules and drivers have now been added to the loader's
276 module blacklist, in favor of loading them with kld_list in rc.conf(5).
277 The module blacklist may be overridden with the loader.conf(5)
278 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
282 The cam(4) based nda(4) driver will be used over nvd(4) by default on
283 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
284 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
285 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
289 Reproducible build mode is now on by default, in preparation for
290 FreeBSD 12.0. This eliminates build metadata such as the user,
291 host, and time from the kernel (and uname), unless the working tree
292 corresponds to a modified checkout from a version control system.
293 The previous behavior can be obtained by setting the /etc/src.conf
294 knob WITHOUT_REPRODUCIBLE_BUILD.
297 The Yarrow CSPRNG has been removed from the kernel as it has not been
298 supported by its designers since at least 2003. Fortuna has been the
299 default since FreeBSD-11.
302 devctl freeze/thaw have gone into the tree, the rc scripts have been
303 updated to use them and devmatch has been changed. You should update
304 kernel, userland and rc scripts all at the same time.
307 The default interpreter has been switched from 4th to Lua.
308 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
309 interpreter. If you have custom FORTH code you will need to set
310 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
311 src.conf for the build. This will create default hard links between
312 loader and loader_4th instead of loader and loader_lua, the new default.
313 If you are using UEFI it will create the proper hard link to loader.efi.
315 bhyve uses userboot.so. It remains 4th-only until some issues are solved
316 regarding coexisting with multiple versions of FreeBSD are resolved.
319 ls(1) now respects the COLORTERM environment variable used in other
320 systems and software to indicate that a colored terminal is both
321 supported and desired. If ls(1) is suddenly emitting colors, they may
322 be disabled again by either removing the unwanted COLORTERM from your
323 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
324 may not be observed in a future release.
327 The default pager for most commands has been changed to "less". To
328 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
332 The jedec_ts(4) driver has been removed. A superset of its functionality
333 is available in the jedec_dimm(4) driver, and the manpage for that
334 driver includes migration instructions. If you have "device jedec_ts"
335 in your kernel configuration file, it must be removed.
338 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
339 This should have no effect if the kernel is booted via BIOS/legacy boot.
340 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
341 has a buggy firmware that prevents a successful boot due to use of
345 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
346 support has been removed from the tree. These ports were
347 obsolete and/or known to be broken for many years.
350 loader.efi has been augmented to participate more fully in the
351 UEFI boot manager protocol. loader.efi will now look at the
352 BootXXXX environment variable to determine if a specific kernel
353 or root partition was specified. XXXX is derived from BootCurrent.
354 efibootmgr(8) manages these standard UEFI variables.
357 zfsloader's functionality has now been folded into loader.
358 zfsloader is no longer necessary once you've updated your
359 boot blocks. For a transition period, we will install a
360 hardlink for zfsloader to loader to allow a smooth transition
361 until the boot blocks can be updated (hard link because old
362 zfs boot blocks don't understand symlinks).
365 ARM64 now have efifb support, if you want to have serial console
366 on your arm64 board when an screen is connected and the bootloader
367 setup a frambuffer for us to use, just add :
371 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
372 an screen connected as the firmware will setup a framebuffer are that
373 u-boot will expose as an EFI framebuffer.
376 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
377 or take steps to update /etc/passwd before doing installworld on
378 existing systems. Do not skip the "mergemaster -Fp" step before
379 installworld, as described in the update procedures near the bottom
380 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
381 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
382 the ntp config file contain options that change file/dir locations.
383 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
384 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
385 taking steps to ensure that all required files/dirs are accessible
389 Big endian arm support has been removed.
392 The static environment setup in kernel configs is no longer mutually
393 exclusive with the loader(8) environment by default. In order to
394 restore the previous default behavior of disabling the loader(8)
395 environment if a static environment is present, you must specify
396 loader_env.disabled=1 in the static environment.
399 The ABI of syscalls used by management tools like sockstat and
400 netstat has been broken to allow 32-bit binaries to work on
401 64-bit kernels without modification. These programs will need
402 to match the kernel in order to function. External programs may
403 require minor modifications to accommodate a change of type in
404 structures from pointers to 64-bit virtual addresses.
407 On i386 and amd64 atomics are now inlined. Out of tree modules using
408 atomics will need to be rebuilt.
411 The '%I' format in the kern.corefile sysctl limits the number of
412 core files that a process can generate to the number stored in the
413 debug.ncores sysctl. The '%I' format is replaced by the single digit
414 index. Previously, if all indexes were taken the kernel would overwrite
415 only a core file with the highest index in a filename.
416 Currently the system will create a new core file if there is a free
417 index or if all slots are taken it will overwrite the oldest one.
420 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
421 6.0.1. Please see the 20141231 entry below for information about
422 prerequisites and upgrading, if you are not already using clang 3.5.0
426 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
427 needed to be changed to work with it. This change was made with r335763
428 and requires a mergemaster / etcupdate / etc to update the installed file.
431 r334930 changed the interface between the NFS modules, so they all
432 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
435 As of r334391 lld is the default amd64 system linker; it is installed
436 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
440 The kernel / userland interface for devinfo changed, so you'll
441 need a new kernel and userland as a pair for it to work (rebuilding
442 lib/libdevinfo is all that's required). devinfo and devmatch will
443 not work, but everything else will when there's a mismatch.
446 The on-disk format for hwpmc callchain records has changed to include
447 threadid corresponding to a given record. This changes the field offsets
448 and thus requires that libpmcstat be rebuilt before using a kernel
452 The vxge(4) driver has been removed. This driver was introduced into
453 HEAD one week before the Exar left the Ethernet market and is not
454 known to be used. If you have device vxge in your kernel config file
458 The amd64 kernel now requires a ld that supports ifunc to produce a
459 working kernel, either lld or a newer binutils. lld is built by default
460 on amd64, and the 'buildkernel' target uses it automatically. However,
461 it is not the default linker, so building the kernel the traditional
462 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
463 binutils port/package). lld will soon be default, and this requirement
466 NOTE: As of r334391 lld is the default system linker on amd64, and no
467 workaround is necessary.
470 The nxge(4) driver has been removed. This driver was for PCI-X 10g
471 cards made by s2io/Neterion. The company was aquired by Exar and
472 no longer sells or supports Ethernet products. If you have device
473 nxge in your kernel config file it must be removed.
476 The tz database (tzdb) has been updated to 2018e. This version more
477 correctly models time stamps in time zones with negative DST such as
478 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
479 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
480 time zone abbreviations and the tm_isdst flag.
483 The ixgb(4) driver has been removed. This driver was for an early and
484 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
485 quickly shifted to the long lived ixgbe family. If you have device
486 ixgb in your kernel config file it must be removed.
489 The lmc(4) driver has been removed. This was a WAN interface
490 card that was already reportedly rare in 2003, and had an ambiguous
491 license. If you have device lmc in your kernel config file it must
495 Support for Arcnet networks has been removed. If you have device
496 arcnet or device cm in your kernel config file they must be
500 Support for FDDI networks has been removed. If you have device
501 fddi or device fpa in your kernel config file they must be
505 In addition to supporting RFC 3164 formatted messages, the
506 syslogd(8) service is now capable of parsing RFC 5424 formatted
507 log messages. The main benefit of using RFC 5424 is that clients
508 may now send log messages with timestamps containing year numbers,
509 microseconds and time zone offsets.
511 Similarly, the syslog(3) C library function has been altered to
512 send RFC 5424 formatted messages to the local system logging
513 daemon. On systems using syslogd(8), this change should have no
514 negative impact, as long as syslogd(8) and the C library are
515 updated at the same time. On systems using a different system
516 logging daemon, it may be necessary to make configuration
517 adjustments, depending on the software used.
519 When using syslog-ng, add the 'syslog-protocol' flag to local
520 input sources to enable parsing of RFC 5424 formatted messages:
523 unix-dgram("/var/run/log" flags(syslog-protocol));
526 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
527 of the 'imuxsock' module to let messages be processed by the
528 regular RFC 3164/5424 parsing pipeline:
530 module(load="imuxsock" SysSock.UseSpecialParser="off")
532 Do note that these changes only affect communication between local
533 applications and syslogd(8). The format that syslogd(8) uses to
534 store messages on disk or forward messages to other systems
535 remains unchanged. syslogd(8) still uses RFC 3164 for these
536 purposes. Options to customize this behaviour will be added in the
537 future. Utilities that process log files stored in /var/log are
538 thus expected to continue to function as before.
540 __FreeBSD_version has been incremented to 1200061 to denote this
544 Support for token ring networks has been removed. If you
545 have "device token" in your kernel config you should remove
546 it. No device drivers supported token ring.
549 makefs was modified to be able to tag ISO9660 El Torito boot catalog
550 entries as EFI instead of overloading the i386 tag as done previously.
551 The amd64 mkisoimages.sh script used to build amd64 ISO images for
552 release was updated to use this. This may mean that makefs must be
553 updated before "make cdrom" can be run in the release directory. This
554 should be as simple as:
556 $ cd $SRCDIR/usr.sbin/makefs
557 $ make depend all install
560 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
561 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
562 Co-existance for the transition period will come shortly. Booting is a
563 complex environment and test coverage for Lua-enabled loaders has been
564 thin, so it would be prudent to assume it might not work and make
565 provisions for backup boot methods.
568 devmatch functionality has been turned on in devd. It will automatically
569 load drivers for unattached devices. This may cause unexpected drivers to
570 be loaded. Please report any problems to current@ and imp@freebsd.org.
573 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
574 6.0.0. Please see the 20141231 entry below for information about
575 prerequisites and upgrading, if you are not already using clang 3.5.0
579 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
580 This means it is used to link the kernel and userland libraries and
581 executables, but is not yet installed as /usr/bin/ld by default.
583 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
584 WITHOUT_LLD_BOOTSTRAP=yes
587 On i386, pmtimer has been removed. Its functionality has been folded
588 into apm. It was a no-op on ACPI in current for a while now (but was still
589 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
590 from kernel config files.
593 The use of RSS hash from the network card aka flowid has been
594 disabled by default for lagg(4) as it's currently incompatible with
595 the lacp and loadbalance protocols.
597 This can be re-enabled by setting the following in loader.conf:
598 net.link.lagg.default_use_flowid="1"
601 The SW_WATCHDOG option is no longer necessary to enable the
602 hardclock-based software watchdog if no hardware watchdog is
603 configured. As before, SW_WATCHDOG will cause the software
604 watchdog to be enabled even if a hardware watchdog is configured.
607 r326887 fixes the issue described in the 20171214 UPDATING entry.
608 r326888 flips the switch back to building GELI support always.
611 r362593 broke ZFS + GELI support for reasons unknown. However,
612 it also broke ZFS support generally, so GELI has been turned off
613 by default as the lesser evil in r326857. If you boot off ZFS and/or
614 GELI, it might not be a good time to update.
617 PowerPC users must update loader(8) by rebuilding world before
618 installing a new kernel, as the protocol connecting them has
619 changed. Without the update, loader metadata will not be passed
620 successfully to the kernel and users will have to enter their
621 root partition at the kernel mountroot prompt to continue booting.
622 Newer versions of loader can boot old kernels without issue.
625 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
626 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
627 to WITH/OUT_LOADER_GELI.
630 The naive and non-compliant support of posix_fallocate(2) in ZFS
631 has been removed as of r325320. The system call now returns EINVAL
632 when used on a ZFS file. Although the new behavior complies with the
633 standard, some consumers are not prepared to cope with it.
634 One known victim is lld prior to r325420.
637 Building in a FreeBSD src checkout will automatically create object
638 directories now rather than store files in the current directory if
639 'make obj' was not ran. Calling 'make obj' is no longer necessary.
640 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
641 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
645 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
646 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
647 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
648 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
649 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
650 The UNIFIED_OBJDIR option is a transitional feature that will be
651 removed for 12.0 release; please migrate to the new format for any
652 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
653 than hardcoding paths.
656 The native-xtools target no longer installs the files by default to the
657 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
658 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
661 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
662 options are changing from controlling the build if defined / undefined
663 to controlling the build with explicit 'yes' or 'no' values. They will
664 shift to WITH/WITHOUT options to match other options in the system.
667 libstand has turned into a private library for sys/boot use only.
668 It is no longer supported as a public interface outside of sys/boot.
671 The arm port has split armv6 into armv6 and armv7. armv7 is now
672 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
673 and are running a kernel from before r324363, you will need to add
674 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
677 When building multiple kernels using KERNCONF, non-existent KERNCONF
678 files will produce an error and buildkernel will fail. Previously
679 missing KERNCONF files silently failed giving no indication as to
680 why, only to subsequently discover during installkernel that the
681 desired kernel was never built in the first place.
684 The default serial number format for CTL LUNs has changed. This will
685 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
686 or iSCSI clients care about their LUNs' serial numbers. Users who
687 require serial number stability should hardcode serial numbers in
691 For 32-bit arm compiled for hard-float support, soft-floating point
692 binaries now always get their shared libraries from
693 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
694 /usr/libsoft also existed). Only users with a hard-float ld.so, but
695 soft-float everything else should be affected.
698 The geli password typed at boot is now hidden. To restore the previous
699 behavior, see geli(8) for configuration options.
702 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
703 sysctl values. Minor nit, but requires a rebuild of both world/kernel
707 "make check" behavior (made in ^/head@r295380) has been changed to
708 execute from a limited sandbox, as opposed to executing from
712 - The "beforecheck" and "aftercheck" targets are now specified.
713 - ${CHECKDIR} (added in commit noted above) has been removed.
714 - Legacy behavior can be enabled by setting
715 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
717 If the limited sandbox mode is enabled, "make check" will execute
718 "make distribution", then install, execute the tests, and clean up the
719 sandbox if successful.
721 The "make distribution" and "make install" targets are typically run as
722 root to set appropriate permissions and ownership at installation time.
723 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
724 environment if executing "make check" with limited sandbox mode using
725 an unprivileged user.
728 Since the switch to GPT disk labels, fsck for UFS/FFS has been
729 unable to automatically find alternate superblocks. As of r322297,
730 the information needed to find alternate superblocks has been
731 moved to the end of the area reserved for the boot block.
732 Filesystems created with a newfs of this vintage or later
733 will create the recovery information. If you have a filesystem
734 created prior to this change and wish to have a recovery block
735 created for your filesystem, you can do so by running fsck in
736 foreground mode (i.e., do not use the -p or -y options). As it
737 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
738 to which you should answer yes.
741 As of r321665, an NFSv4 server configuration that services
742 Kerberos mounts or clients that do not support the uid/gid in
743 owner/owner_group string capability, must explicitly enable
744 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
745 machine's /etc/rc.conf file.
748 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
749 Please see the 20141231 entry below for information about prerequisites
750 and upgrading, if you are not already using clang 3.5.0 or higher.
753 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
754 r-commands (rlogin, rsh, etc.) to be built with the base system.
757 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
758 a very major ABI incompatible change, so users of FreeBSD/powerpc must
759 be careful when performing source upgrades. It is best to run
760 'make installworld' from an alternate root system, either a live
761 CD/memory stick, or a temporary root partition. Additionally, all ports
762 must be recompiled. powerpc64 is largely unaffected, except in the case
763 of 32-bit compatibility. All 32-bit binaries will be affected.
766 Forward compatibility for the "ino64" project have been committed. This
767 will allow most new binaries to run on older kernels in a limited
768 fashion. This prevents many of the common foot-shooting actions in the
769 upgrade as well as the limited ability to roll back the kernel across
770 the ino64 upgrade. Complicated use cases may not work properly, though
771 enough simpler ones work to allow recovery in most situations.
774 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
775 if you require the GPL compiler.
778 The internal ABI used for communication between the NFS kernel modules
779 was changed by r320085, so __FreeBSD_version was bumped to
780 ensure all the NFS related modules are updated together.
783 The ABI of struct event was changed by extending the data
784 member to 64bit and adding ext fields. For upgrade, same
785 precautions as for the entry 20170523 "ino64" must be
789 The GNU roff toolchain has been removed from base. To render manpages
790 which are not supported by mandoc(1), man(1) can fallback on GNU roff
791 from ports (and recommends to install it).
792 To render roff(7) documents, consider using GNU roff from ports or the
793 heirloom doctools roff toolchain from ports via pkg install groff or
794 via pkg install heirloom-doctools.
797 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
798 smaller runtime footprint builds. This is useful for embedded systems
799 which only require one chipset support.
801 If you load it as a module, make sure this is in /boot/loader.conf:
805 This will load the HAL, all chip/RF backends and if_ath_pci.
806 If you have if_ath_pci in /boot/loader.conf, ensure it is after
807 if_ath or it will not load any HAL chipset support.
809 If you want to selectively load things (eg on ye cheape ARM/MIPS
810 platforms where RAM is at a premium) you should:
813 * load the chip modules in question
814 * load ath_rate, ath_dfs
816 * load if_ath_pci and/or if_ath_ahb depending upon your particular
817 bus bind type - this is where probe/attach is done.
819 For further comments/feedback, poke adrian@ .
822 The "ino64" 64-bit inode project has been committed, which extends
823 a number of types to 64 bits. Upgrading in place requires care and
824 adherence to the documented upgrade procedure.
826 If using a custom kernel configuration ensure that the
827 COMPAT_FREEBSD11 option is included (as during the upgrade the
828 system will be running the ino64 kernel with the existing world).
830 For the safest in-place upgrade begin by removing previous build
831 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
832 full procedure documented below under the heading "To rebuild
833 everything and install it on the current system." Specifically,
834 a reboot is required after installing the new kernel before
838 The NATM framework including the en(4), fatm(4), hatm(4), and
839 patm(4) devices has been removed. Consumers should plan a
840 migration before the end-of-life date for FreeBSD 11.
843 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
844 diff has not been implemented, if those are needed a newer version of
845 GNU diff is available via the diffutils package under the gdiff name.
848 As of r316810 for ipfilter, keep frags is no longer assumed when
849 keep state is specified in a rule. r316810 aligns ipfilter with
850 documentation in man pages separating keep frags from keep state.
851 This allows keep state to be specified without forcing keep frags
852 and allows keep frags to be specified independently of keep state.
853 To maintain previous behaviour, also specify keep frags with
854 keep state (as documented in ipf.conf.5).
857 arm64 builds now use the base system LLD 4.0.0 linker by default,
858 instead of requiring that the aarch64-binutils port or package be
859 installed. To continue using aarch64-binutils, set
860 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
863 The UDP optimization in entry 20160818 that added the sysctl
864 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
865 packets will no longer be treated as L3 broadcast packets.
868 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
869 use any explicitly assigned loopback address available in the jail
870 instead of using the first assigned address of the jail.
873 The ctl.ko module no longer implements the iSCSI target frontend:
874 cfiscsi.ko does instead.
876 If building cfiscsi.ko as a kernel module, the module can be loaded
877 via one of the following methods:
878 - `cfiscsi_load="YES"` in loader.conf(5).
879 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
880 - ctladm(8)/ctld(8), when compiled with iSCSI support
881 (`WITH_ISCSI=yes` in src.conf(5))
883 Please see cfiscsi(4) for more details.
886 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
887 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
888 same source (previously, the dependency of mmcsd.ko on mmc.ko was
889 missing, but mmcsd.ko now will refuse to load if it is incompatible
893 The syntax of ipfw(8) named states was changed to avoid ambiguity.
894 If you have used named states in the firewall rules, you need to modify
895 them after installworld and before rebooting. Now named states must
896 be prefixed with colon.
899 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
900 removed as the userland we provide cannot use them. The KMS version
901 (sys/dev/drm2) supports the same hardware.
904 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
905 Please see the 20141231 entry below for information about prerequisites
906 and upgrading, if you are not already using clang 3.5.0 or higher.
909 The code that provides support for ZFS .zfs/ directory functionality
910 has been reimplemented. It's not possible now to create a snapshot
911 by mkdir under .zfs/snapshot/. That should be the only user visible
915 EISA bus support has been removed. The WITH_EISA option is no longer
919 MCA bus support has been removed.
922 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
923 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
926 The EM_MULTIQUEUE kernel configuration option is deprecated now that
927 the em(4) driver conforms to iflib specifications.
930 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
931 IFLIB. If you have a custom kernel configuration that excludes em(4)
932 but you use igb(4), you need to re-add em(4) to your custom configuration.
935 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
936 Please see the 20141231 entry below for information about prerequisites
937 and upgrading, if you are not already using clang 3.5.0 or higher.
940 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
941 Please see the 20141231 entry below for information about prerequisites
942 and upgrading, if you are not already using clang 3.5.0 or higher.
945 The layout of the pmap structure has changed for powerpc to put the pmap
946 statistics at the front for all CPU variations. libkvm(3) and all tools
947 that link against it need to be recompiled.
950 isl(4) and cyapa(4) drivers now require a new driver,
951 chromebook_platform(4), to work properly on Chromebook-class hardware.
952 On other types of hardware the drivers may need to be configured using
953 device hints. Please see the corresponding manual pages for details.
956 The urtwn(4) driver was merged into rtwn(4) and now consists of
957 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
959 Also, firmware for RTL8188CE was renamed due to possible name
960 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
963 GNU rcs has been removed from base. It is available as packages:
964 - rcs: Latest GPLv3 GNU rcs version.
965 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
969 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
970 modules now requires that the kernel configuration contain the
971 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
974 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
975 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
978 Relocatable object files with the extension of .So have been renamed
979 to use an extension of .pico instead. The purpose of this change is
980 to avoid a name clash with shared libraries on case-insensitive file
981 systems. On those file systems, foo.So is the same file as foo.so.
984 GNU rcs has been turned off by default. It can (temporarily) be built
985 again by adding WITH_RCS knob in src.conf.
986 Otherwise, GNU rcs is available from packages:
987 - rcs: Latest GPLv3 GNU rcs version.
988 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
991 The backup_uses_rcs functionality has been removed from rc.subr.
994 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
995 two separate components, QUEUE_MACRO_DEBUG_TRACE and
996 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
997 QUEUE_MACRO_DEBUG behavior.
1000 r304787 changed some ioctl interfaces between the iSCSI userspace
1001 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1002 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1006 The UDP receive code has been updated to only treat incoming UDP
1007 packets that were addressed to an L2 broadcast address as L3
1008 broadcast packets. It is not expected that this will affect any
1009 standards-conforming UDP application. The new behaviour can be
1010 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1014 Remove the openbsd_poll system call.
1015 __FreeBSD_version has been bumped because of this.
1018 The stable/11 branch has been created from head@r302406.
1021 The libc stub for the pipe(2) system call has been replaced with
1022 a wrapper that calls the pipe2(2) system call and the pipe(2)
1023 system call is now only implemented by the kernels that include
1024 "options COMPAT_FREEBSD10" in their config file (this is the
1025 default). Users should ensure that this option is enabled in
1026 their kernel or upgrade userspace to r302092 before upgrading their
1030 CAM will now strip leading spaces from SCSI disks' serial numbers.
1031 This will affect users who create UFS filesystems on SCSI disks using
1032 those disk's diskid device nodes. For example, if /etc/fstab
1033 previously contained a line like
1034 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1035 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1036 transforms like gmirror may also be affected. ZFS users should
1040 The bitstring(3) API has been updated with new functionality and
1041 improved performance. But it is binary-incompatible with the old API.
1042 Objects built with the new headers may not be linked against objects
1043 built with the old headers.
1046 The brk and sbrk functions have been removed from libc on arm64.
1047 Binutils from ports has been updated to not link to these
1048 functions and should be updated to the latest version before
1049 installing a new libc.
1052 The armv6 port now defaults to hard float ABI. Limited support
1053 for running both hardfloat and soft float on the same system
1054 is available using the libraries installed with -DWITH_LIBSOFT.
1055 This has only been tested as an upgrade path for installworld
1056 and packages may fail or need manual intervention to run. New
1057 packages will be needed.
1059 To update an existing self-hosted armv6hf system, you must add
1060 TARGET_ARCH=armv6 on the make command line for both the build
1061 and the install steps.
1064 Kernel modules compiled outside of a kernel build now default to
1065 installing to /boot/modules instead of /boot/kernel. Many kernel
1066 modules built this way (such as those in ports) already overrode
1067 KMODDIR explicitly to install into /boot/modules. However,
1068 manually building and installing a module from /sys/modules will
1069 now install to /boot/modules instead of /boot/kernel.
1072 The CAM I/O scheduler has been committed to the kernel. There should be
1073 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1074 list of known rogues that claim support for this but actually corrupt
1075 data is believed to be complete, be on the lookout for data
1076 corruption. The known rogue list is believed to be complete:
1078 o Crucial MX100, M550 drives with MU01 firmware.
1079 o Micron M510 and M550 drives with MU01 firmware.
1080 o Micron M500 prior to MU07 firmware
1081 o Samsung 830, 840, and 850 all firmwares
1082 o FCCT M500 all firmwares
1084 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1085 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1086 updated firmware. Black listed drives will work correctly because these
1087 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1088 this list is the same as found in Linux, it's believed there are no
1089 other rogues in the market place. All other models from the above
1092 To be safe, if you are at all concerned, you can quirk each of your
1093 drives to prevent NCQ from being sent by setting:
1094 kern.cam.ada.X.quirks="0x2"
1095 in loader.conf. If the drive requires the 4k sector quirk, set the
1096 quirks entry to 0x3.
1099 The FAST_DEPEND build option has been removed and its functionality is
1100 now the one true way. The old mkdep(1) style of 'make depend' has
1101 been removed. See 20160311 for further details.
1104 Resource range types have grown from unsigned long to uintmax_t. All
1105 drivers, and anything using libdevinfo, need to be recompiled.
1108 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1109 builds. It no longer runs mkdep(1) during 'make depend', and the
1110 'make depend' stage can safely be skipped now as it is auto ran
1111 when building 'make all' and will generate all SRCS and DPSRCS before
1112 building anything else. Dependencies are gathered at compile time with
1113 -MF flags kept in separate .depend files per object file. Users should
1114 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1115 stale .depend files.
1118 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1119 kernel modules. Therefore, if you load any kernel modules at boot time,
1120 please install the boot loaders after you install the kernel, but before
1124 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1125 make installkernel KERNCONF=YOUR_KERNEL_HERE
1126 make -C sys/boot install
1127 <reboot in single user>
1129 Then follow the usual steps, described in the General Notes section,
1133 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1134 see the 20141231 entry below for information about prerequisites and
1135 upgrading, if you are not already using clang 3.5.0 or higher.
1138 The AIO subsystem is now a standard part of the kernel. The
1139 VFS_AIO kernel option and aio.ko kernel module have been removed.
1140 Due to stability concerns, asynchronous I/O requests are only
1141 permitted on sockets and raw disks by default. To enable
1142 asynchronous I/O requests on all file types, set the
1143 vfs.aio.enable_unsafe sysctl to a non-zero value.
1146 The ELF object manipulation tool objcopy is now provided by the
1147 ELF Tool Chain project rather than by GNU binutils. It should be a
1148 drop-in replacement, with the addition of arm64 support. The
1149 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1150 to obtain the GNU version if necessary.
1153 Building ZFS pools on top of zvols is prohibited by default. That
1154 feature has never worked safely; it's always been prone to deadlocks.
1155 Using a zvol as the backing store for a VM guest's virtual disk will
1156 still work, even if the guest is using ZFS. Legacy behavior can be
1157 restored by setting vfs.zfs.vol.recursive=1.
1160 The NONE and HPN patches has been removed from OpenSSH. They are
1161 still available in the security/openssh-portable port.
1164 With the addition of ypldap(8), a new _ypldap user is now required
1165 during installworld. "mergemaster -p" can be used to add the user
1166 prior to installworld, as documented in the handbook.
1169 The tftp loader (pxeboot) now uses the option root-path directive. As a
1170 consequence it no longer looks for a pxeboot.4th file on the tftp
1171 server. Instead it uses the regular /boot infrastructure as with the
1175 The code to start recording plug and play data into the modules has
1176 been committed. While the old tools will properly build a new kernel,
1177 a number of warnings about "unknown metadata record 4" will be produced
1178 for an older kldxref. To avoid such warnings, make sure to rebuild
1179 the kernel toolchain (or world). Make sure that you have r292078 or
1180 later when trying to build 292077 or later before rebuilding.
1183 Debug data files are now built by default with 'make buildworld' and
1184 installed with 'make installworld'. This facilitates debugging but
1185 requires more disk space both during the build and for the installed
1186 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1190 r291527 changed the internal interface between the nfsd.ko and
1191 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1192 __FreeBSD_version has been bumped because of this.
1195 Add support for unicode collation strings leads to a change of
1196 order of files listed by ls(1) for example. To get back to the old
1197 behaviour, set LC_COLLATE environment variable to "C".
1199 Databases administrators will need to reindex their databases given
1200 collation results will be different.
1202 Due to a bug in install(1) it is recommended to remove the ancient
1203 locales before running make installworld.
1205 rm -rf /usr/share/locale/*
1208 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1209 libcrypto.so.7 or libssl.so.7 must be recompiled.
1212 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1213 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1214 should be replaced with isp_2400 and isp_2500 modules respectively.
1217 The build previously allowed using 'make -n' to not recurse into
1218 sub-directories while showing what commands would be executed, and
1219 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1220 and 'make -N' will not.
1223 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1224 and etcupdate will now use this file. A custom sendmail.cf is now
1225 updated via this mechanism rather than via installworld. If you had
1226 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1227 want to remove the exclusion or change it to "always install".
1228 /etc/mail/sendmail.cf is now managed the same way regardless of
1229 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1230 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1233 Compatibility shims for legacy ATA device names have been removed.
1234 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1235 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1236 environment variables, /dev/ad* and /dev/ar* symbolic links.
1239 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1240 Please see the 20141231 entry below for information about prerequisites
1241 and upgrading, if you are not already using clang 3.5.0 or higher.
1244 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1245 and renamed from .symbols to .debug. This reduces the size requirements
1246 on the boot partition or file system and provides consistency with
1247 userland debug files.
1249 When using the supported kernel installation method the
1250 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1251 as is done with /boot/kernel.
1253 Developers wishing to maintain the historical behavior of installing
1254 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1257 The wireless drivers had undergone changes that remove the 'parent
1258 interface' from the ifconfig -l output. The rc.d network scripts
1259 used to check presence of a parent interface in the list, so old
1260 scripts would fail to start wireless networking. Thus, etcupdate(3)
1261 or mergemaster(8) run is required after kernel update, to update your
1262 rc.d scripts in /etc.
1265 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1266 These configurations are now automatically interpreted as
1267 'scrub fragment reassemble'.
1270 Kernel-loadable modules for the random(4) device are back. To use
1271 them, the kernel must have
1274 options RANDOM_LOADABLE
1276 kldload(8) can then be used to load random_fortuna.ko
1277 or random_yarrow.ko. Please note that due to the indirect
1278 function calls that the loadable modules need to provide,
1279 the build-in variants will be slightly more efficient.
1281 The random(4) kernel option RANDOM_DUMMY has been retired due to
1282 unpopularity. It was not all that useful anyway.
1285 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1286 Control over building the ELF Tool Chain tools is now provided by
1287 the WITHOUT_TOOLCHAIN knob.
1290 The polarity of Pulse Per Second (PPS) capture events with the
1291 uart(4) driver has been corrected. Prior to this change the PPS
1292 "assert" event corresponded to the trailing edge of a positive PPS
1293 pulse and the "clear" event was the leading edge of the next pulse.
1295 As the width of a PPS pulse in a typical GPS receiver is on the
1296 order of 1 millisecond, most users will not notice any significant
1297 difference with this change.
1299 Anyone who has compensated for the historical polarity reversal by
1300 configuring a negative offset equal to the pulse width will need to
1301 remove that workaround.
1304 The default group assigned to /dev/dri entries has been changed
1305 from 'wheel' to 'video' with the id of '44'. If you want to have
1306 access to the dri devices please add yourself to the video group
1309 # pw groupmod video -m $USER
1312 The menu.rc and loader.rc files will now be replaced during
1313 upgrades. Please migrate local changes to menu.rc.local and
1314 loader.rc.local instead.
1317 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1318 strings and strip have been removed. The src.conf(5) knob
1319 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1322 As ZFS requires more kernel stack pages than is the default on some
1323 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1324 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1326 Please consider using 'options KSTACK_PAGES=X' where X is greater
1327 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1330 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1331 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1332 default, i.e., they will not contain "::". For example, instead
1333 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1334 to have a more specific match, such as different map entries for
1335 IPv6:0:0 vs IPv6:0. This change requires that configuration
1336 data (including maps, files, classes, custom ruleset, etc.) must
1337 use the same format, so make certain such configuration data is
1338 upgrading. As a very simple check search for patterns like
1339 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1340 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1341 the cf option UseCompressedIPv6Addresses.
1344 The default kernel entropy-processing algorithm is now
1345 Fortuna, replacing Yarrow.
1347 Assuming you have 'device random' in your kernel config
1348 file, the configurations allow a kernel option to override
1349 this default. You may choose *ONE* of:
1351 options RANDOM_YARROW # Legacy /dev/random algorithm.
1352 options RANDOM_DUMMY # Blocking-only driver.
1354 If you have neither, you get Fortuna. For most people,
1355 read no further, Fortuna will give a /dev/random that works
1356 like it always used to, and the difference will be irrelevant.
1358 If you remove 'device random', you get *NO* kernel-processed
1359 entropy at all. This may be acceptable to folks building
1360 embedded systems, but has complications. Carry on reading,
1361 and it is assumed you know what you need.
1363 *PLEASE* read random(4) and random(9) if you are in the
1364 habit of tweaking kernel configs, and/or if you are a member
1365 of the embedded community, wanting specific and not-usual
1366 behaviour from your security subsystems.
1368 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1369 random', you will NOT have a functioning /dev/random, and
1370 many cryptographic features will not work, including SSH.
1371 You may also find strange behaviour from the random(3) set
1372 of library functions, in particular sranddev(3), srandomdev(3)
1373 and arc4random(3). The reason for this is that the KERN_ARND
1374 sysctl only returns entropy if it thinks it has some to
1375 share, and with RANDOM_DUMMY or no 'device random' this
1379 An additional fix for the issue described in the 20150614 sendmail
1380 entry below has been committed in revision 284717.
1383 FreeBSD's old make (fmake) has been removed from the system. It is
1384 available as the devel/fmake port or via pkg install fmake.
1387 The fix for the issue described in the 20150614 sendmail entry
1388 below has been committed in revision 284436. The work
1389 around described in that entry is no longer needed unless the
1390 default setting is overridden by a confDH_PARAMETERS configuration
1391 setting of '5' or pointing to a 512 bit DH parameter file.
1394 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1395 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1396 and devel/kyua to version 0.20+ and adjust any calling code to work
1397 with Kyuafile and kyua.
1400 The import of openssl to address the FreeBSD-SA-15:10.openssl
1401 security advisory includes a change which rejects handshakes
1402 with DH parameters below 768 bits. sendmail releases prior
1403 to 8.15.2 (not yet released), defaulted to a 512 bit
1404 DH parameter setting for client connections. To work around
1405 this interoperability, sendmail can be configured to use a
1406 2048 bit DH parameter by:
1408 1. Edit /etc/mail/`hostname`.mc
1409 2. If a setting for confDH_PARAMETERS does not exist or
1410 exists and is set to a string beginning with '5',
1411 replace it with '2'.
1412 3. If a setting for confDH_PARAMETERS exists and is set to
1413 a file path, create a new file with:
1414 openssl dhparam -out /path/to/file 2048
1415 4. Rebuild the .cf file:
1416 cd /etc/mail/; make; make install
1417 5. Restart sendmail:
1418 cd /etc/mail/; make restart
1420 A sendmail patch is coming, at which time this file will be
1424 Generation of legacy formatted entries have been disabled by default
1425 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1426 entries were converted to use the new format by default when the new,
1427 machine independent format have been added and supported since FreeBSD
1430 Please see the pwd_mkdb(8) manual page for further details.
1433 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1434 20141231 entry below for information about prerequisites and upgrading,
1435 if you are not already using 3.5.0 or higher.
1438 TI platform code switched to using vendor DTS files and this update
1439 may break existing systems running on Beaglebone, Beaglebone Black,
1442 - dtb files should be regenerated/reinstalled. Filenames are the
1443 same but content is different now
1444 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1445 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1446 addressing scheme is now pin 25 on /dev/gpioc3.
1447 - Pandaboard: /etc/ttys should be updated, serial console device is
1448 now /dev/ttyu2, not /dev/ttyu0
1451 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1452 If you need the GNU extension from groff soelim(1), install groff
1453 from package: pkg install groff, or via ports: textproc/groff.
1456 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1457 defined in symlink(7); previously symlinks were silently ignored.
1460 The const qualifier has been removed from iconv(3) to comply with
1461 POSIX. The ports tree is aware of this from r384038 onwards.
1464 Libraries specified by LIBADD in Makefiles must have a corresponding
1465 DPADD_<lib> variable to ensure correct dependencies. This is now
1466 enforced in src.libnames.mk.
1469 From legacy ata(4) driver was removed support for SATA controllers
1470 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1471 Kernel modules ataahci and ataadaptec were removed completely,
1472 replaced by ahci and mvs modules respectively.
1475 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1476 the 20141231 entry below for information about prerequisites and
1477 upgrading, if you are not already using 3.5.0 or higher.
1480 The 32-bit PowerPC kernel has been changed to a position-independent
1481 executable. This can only be booted with a version of loader(8)
1482 newer than January 31, 2015, so make sure to update both world and
1483 kernel before rebooting.
1486 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1487 but before r278950, the RNG was not seeded properly. Immediately
1488 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1489 ssh keys or openssl keys) that were generated w/ a kernel from that
1490 range. This does not affect programs that directly used /dev/random
1491 or /dev/urandom. All userland uses of arc4random(3) are affected.
1494 The autofs(4) ABI was changed in order to restore binary compatibility
1495 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1496 with the new kernel.
1499 The powerpc64 kernel has been changed to a position-independent
1500 executable. This can only be booted with a new version of loader(8),
1501 so make sure to update both world and kernel before rebooting.
1504 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1505 only release, no new features have been added. Please see the 20141231
1506 entry below for information about prerequisites and upgrading, if you
1507 are not already using 3.5.0.
1510 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1511 taken from the ELF Tool Chain project rather than GNU binutils. They
1512 should be drop-in replacements, with the addition of arm64 support.
1513 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1514 binutils tools, if necessary. See 20150805 for updated information.
1517 The default Unbound configuration now enables remote control
1518 using a local socket. Users who have already enabled the
1519 local_unbound service should regenerate their configuration
1520 by running "service local_unbound setup" as root.
1523 The GNU texinfo and GNU info pages have been removed.
1524 To be able to view GNU info pages please install texinfo from ports.
1527 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1529 As of this release, a prerequisite for building clang, llvm and lldb is
1530 a C++11 capable compiler and C++11 standard library. This means that to
1531 be able to successfully build the cross-tools stage of buildworld, with
1532 clang as the bootstrap compiler, your system compiler or cross compiler
1533 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1534 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1537 On any standard FreeBSD 10.x or 11.x installation, where clang and
1538 libc++ are on by default (that is, on x86 or arm), this should work out
1541 On 9.x installations where clang is enabled by default, e.g. on x86 and
1542 powerpc, libc++ will not be enabled by default, so libc++ should be
1543 built (with clang) and installed first. If both clang and libc++ are
1544 missing, build clang first, then use it to build libc++.
1546 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1547 the instructions for 9.x above.
1549 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1550 default, and do not build clang.
1552 Many embedded systems are resource constrained, and will not be able to
1553 build clang in a reasonable time, or in some cases at all. In those
1554 cases, cross building bootable systems on amd64 is a workaround.
1556 This new version of clang introduces a number of new warnings, of which
1557 the following are most likely to appear:
1561 This warns in two cases, for both C and C++:
1562 * When the code is trying to take the absolute value of an unsigned
1563 quantity, which is effectively a no-op, and almost never what was
1564 intended. The code should be fixed, if at all possible. If you are
1565 sure that the unsigned quantity can be safely cast to signed, without
1566 loss of information or undefined behavior, you can add an explicit
1567 cast, or disable the warning.
1569 * When the code is trying to take an absolute value, but the called
1570 abs() variant is for the wrong type, which can lead to truncation.
1571 If you want to disable the warning instead of fixing the code, please
1572 make sure that truncation will not occur, or it might lead to unwanted
1575 -Wtautological-undefined-compare and
1576 -Wundefined-bool-conversion
1578 These warn when C++ code is trying to compare 'this' against NULL, while
1579 'this' should never be NULL in well-defined C++ code. However, there is
1580 some legacy (pre C++11) code out there, which actively abuses this
1581 feature, which was less strictly defined in previous C++ versions.
1583 Squid and openjdk do this, for example. The warning can be turned off
1584 for C++98 and earlier, but compiling the code in C++11 mode might result
1585 in unexpected behavior; for example, the parts of the program that are
1586 unreachable could be optimized away.
1589 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1590 kernel sources have been removed. The .h files remain, since some
1591 utilities include them. This will need to be fixed later.
1592 If "mount -t oldnfs ..." is attempted, it will fail.
1593 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1594 the utilities will report errors.
1597 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1598 directories to top level SUBDIR variable when their parent
1599 directory is included in LOCAL_DIRS. Users with build systems with
1600 such hierarchies and without SUBDIR entries in the parent
1601 directory Makefiles should add them or add the directories to
1605 faith(4) and faithd(8) have been removed from the base system. Faith
1606 has been obsolete for a very long time.
1609 vt(4), the new console driver, is enabled by default. It brings
1610 support for Unicode and double-width characters, as well as
1611 support for UEFI and integration with the KMS kernel video
1614 You may need to update your console settings in /etc/rc.conf,
1615 most probably the keymap. During boot, /etc/rc.d/syscons will
1616 indicate what you need to do.
1618 vt(4) still has issues and lacks some features compared to
1619 syscons(4). See the wiki for up-to-date information:
1620 https://wiki.freebsd.org/Newcons
1622 If you want to keep using syscons(4), you can do so by adding
1623 the following line to /boot/loader.conf:
1627 pjdfstest has been integrated into kyua as an opt-in test suite.
1628 Please see share/doc/pjdfstest/README for more details on how to
1632 gperf has been removed from the base system for architectures
1633 that use clang. Ports that require gperf will obtain it from the
1637 pjdfstest has been moved from tools/regression/pjdfstest to
1641 At svn r271982, The default linux compat kernel ABI has been adjusted
1642 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1643 update. If you wish to continue using the linux-f10 compat ports,
1644 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1645 encouraged to update their linux-compat packages to linux-c6 during
1646 their next update cycle.
1649 The ofwfb driver, used to provide a graphics console on PowerPC when
1650 using vt(4), no longer allows mmap() of all physical memory. This
1651 will prevent Xorg on PowerPC with some ATI graphics cards from
1652 initializing properly unless x11-servers/xorg-server is updated to
1656 The xdev targets have been converted to using TARGET and
1657 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1660 The default unbound configuration has been modified to address
1661 issues with reverse lookups on networks that use private
1662 address ranges. If you use the local_unbound service, run
1663 "service local_unbound setup" as root to regenerate your
1664 configuration, then "service local_unbound reload" to load the
1668 The GNU texinfo and GNU info pages are not built and installed
1669 anymore, WITH_INFO knob has been added to allow to built and install
1671 UPDATE: see 20150102 entry on texinfo's removal
1674 The GNU readline library is now an INTERNALLIB - that is, it is
1675 statically linked into consumers (GDB and variants) in the base
1676 system, and the shared library is no longer installed. The
1677 devel/readline port is available for third party software that
1681 The Itanium architecture (ia64) has been removed from the list of
1682 known architectures. This is the first step in the removal of the
1686 Commit r268115 has added NFSv4.1 server support, merged from
1687 projects/nfsv4.1-server. Since this includes changes to the
1688 internal interfaces between the NFS related modules, a full
1689 build of the kernel and modules will be necessary.
1690 __FreeBSD_version has been bumped.
1693 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1694 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1695 which differs from the behaviour controlled by this knob.)
1698 Maximal length of the serial number in CTL was increased from 16 to
1699 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1700 and ctld, need to be rebuilt to work with a new kernel.
1703 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1704 1 respectively to match the upstream numbers. They were out of
1705 sync because, when they were originally added to FreeBSD, the
1706 upstream versions were not respected. These libraries are private
1707 and not yet built by default, so renumbering them should be a
1708 non-issue. However, unclean source trees will yield broken test
1709 programs once the operator executes "make delete-old-libs" after a
1710 "make installworld".
1712 Additionally, the atf-sh binary was made private by moving it into
1713 /usr/libexec/. Already-built shell test programs will keep the
1714 path to the old binary so they will break after "make delete-old"
1717 If you are using WITH_TESTS=yes (not the default), wipe the object
1718 tree and rebuild from scratch to prevent spurious test failures.
1719 This is only needed once: the misnumbered libraries and misplaced
1720 binaries have been added to OptionalObsoleteFiles.inc so they will
1721 be removed during a clean upgrade.
1724 Clang and llvm have been upgraded to 3.4.1 release.
1727 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1728 be removed to avoid issues in the future (and has been added to
1732 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1733 past, it affected all builds that used the bsd.*.mk files. The old
1734 behavior was a bug, but people may have relied upon it. To get this
1735 behavior back, you can .include /etc/src.conf from /etc/make.conf
1736 (which is still global and isn't changed). This also changes the
1737 behavior of incremental builds inside the tree of individual
1738 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1739 Although this has survived make universe and some upgrade scenarios,
1740 other upgrade scenarios may have broken. At least one form of
1741 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1742 as well... In cases where MAKESYSPATH isn't working with this
1743 setting, you'll need to set it to the full path to your tree.
1745 One side effect of all this cleaning up is that bsd.compiler.mk
1746 is no longer implicitly included by bsd.own.mk. If you wish to
1747 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1751 The lindev device has been removed since /dev/full has been made a
1752 standard device. __FreeBSD_version has been bumped.
1755 The knob WITHOUT_VI was added to the base system, which controls
1756 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1757 in order to reorder files share/termcap and didn't build ex(1) as a
1758 build tool, so building/installing with WITH_VI is highly advised for
1759 build hosts for older releases.
1761 This issue has been fixed in stable/9 and stable/10 in r277022 and
1762 r276991, respectively.
1765 The YES_HESIOD knob has been removed. It has been obsolete for
1766 a decade. Please move to using WITH_HESIOD instead or your builds
1767 will silently lack HESIOD.
1770 The uart(4) driver has been changed with respect to its handling
1771 of the low-level console. Previously the uart(4) driver prevented
1772 any process from changing the baudrate or the CLOCAL and HUPCL
1773 control flags. By removing the restrictions, operators can make
1774 changes to the serial console port without having to reboot.
1775 However, when getty(8) is started on the serial device that is
1776 associated with the low-level console, a misconfigured terminal
1777 line in /etc/ttys will now have a real impact.
1778 Before upgrading the kernel, make sure that /etc/ttys has the
1779 serial console device configured as 3wire without baudrate to
1780 preserve the previous behaviour. E.g:
1781 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1784 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1785 to improve performance. To re-enable it, if needed, run rpcbind
1786 with command line option -W.
1789 Switched back to the GPL dtc compiler due to updates in the upstream
1790 dts files not being supported by the BSDL dtc compiler. You will need
1791 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1792 may result while building dtb files during a kernel build if you fail
1793 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1796 Clang and llvm have been upgraded to 3.4 release.
1799 The nve(4) driver has been removed. Please use the nfe(4) driver
1800 for NVIDIA nForce MCP Ethernet adapters instead.
1803 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1804 This could cause certain C++ applications using shared libraries built
1805 against the previous version of libc++ to crash. The incompatibility
1806 has now been fixed, but any C++ applications or shared libraries built
1807 between r261283 and r261801 should be recompiled.
1810 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1811 capability mode support. Please note that enabling the feature in
1812 kernel is still highly recommended.
1815 OpenSSH is now built with sandbox support, and will use sandbox as
1816 the default privilege separation method. This requires Capsicum
1817 capability mode support in kernel.
1820 The libelf and libdwarf libraries have been updated to newer
1821 versions from upstream. Shared library version numbers for
1822 these two libraries were bumped. Any ports or binaries
1823 requiring these two libraries should be recompiled.
1824 __FreeBSD_version is bumped to 1100006.
1827 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1828 instead of providing an explicit one, this would prevent such
1829 Makefile from providing its own Kyuafile in the future during
1830 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1831 intervention is needed to clean an objdir if you use NO_CLEAN:
1832 # find /usr/obj -name Kyuafile | xargs rm -f
1835 The behavior of gss_pseudo_random() for the krb5 mechanism
1836 has changed, for applications requesting a longer random string
1837 than produced by the underlying enctype's pseudo-random() function.
1838 In particular, the random string produced from a session key of
1839 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1840 be different at the 17th octet and later, after this change.
1841 The counter used in the PRF+ construction is now encoded as a
1842 big-endian integer in accordance with RFC 4402.
1843 __FreeBSD_version is bumped to 1100004.
1846 The WITHOUT_ATF build knob has been removed and its functionality
1847 has been subsumed into the more generic WITHOUT_TESTS. If you were
1848 using the former to disable the build of the ATF libraries, you
1849 should change your settings to use the latter.
1852 The default version of mtree is nmtree which is obtained from
1853 NetBSD. The output is generally the same, but may vary
1854 slightly. If you found you need identical output adding
1855 "-F freebsd9" to the command line should do the trick. For the
1856 time being, the old mtree is available as fmtree.
1859 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1860 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1861 1.1.4_8 and verify bsdyml not linked in, before running "make
1863 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1865 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1868 The stable/10 branch has been created in subversion from head
1875 Avoid using make -j when upgrading. While generally safe, there are
1876 sometimes problems using -j to upgrade. If your upgrade fails with
1877 -j, please try again without -j. From time to time in the past there
1878 have been problems using -j with buildworld and/or installworld. This
1879 is especially true when upgrading between "distant" versions (eg one
1880 that cross a major release boundary or several minor releases, or when
1881 several months have passed on the -current branch).
1883 Sometimes, obscure build problems are the result of environment
1884 poisoning. This can happen because the make utility reads its
1885 environment when searching for values for global variables. To run
1886 your build attempts in an "environmental clean room", prefix all make
1887 commands with 'env -i '. See the env(1) manual page for more details.
1889 When upgrading from one major version to another it is generally best to
1890 upgrade to the latest code in the currently installed branch first, then
1891 do an upgrade to the new branch. This is the best-tested upgrade path,
1892 and has the highest probability of being successful. Please try this
1893 approach if you encounter problems with a major version upgrade. Since
1894 the stable 4.x branch point, one has generally been able to upgrade from
1895 anywhere in the most recent stable branch to head / current (or even the
1896 last couple of stable branches). See the top of this file when there's
1899 When upgrading a live system, having a root shell around before
1900 installing anything can help undo problems. Not having a root shell
1901 around can lead to problems if pam has changed too much from your
1902 starting point to allow continued authentication after the upgrade.
1904 This file should be read as a log of events. When a later event changes
1905 information of a prior event, the prior event should not be deleted.
1906 Instead, a pointer to the entry with the new information should be
1907 placed in the old entry. Readers of this file should also sanity check
1908 older entries before relying on them blindly. Authors of new entries
1909 should write them with this in mind.
1913 When upgrading the boot ZFS pool to a new version, always follow
1916 1.) recompile and reinstall the ZFS boot loader and boot block
1917 (this is part of "make buildworld" and "make installworld")
1919 2.) update the ZFS boot block on your boot drive
1921 The following example updates the ZFS boot block on the first
1922 partition (freebsd-boot) of a GPT partitioned drive ada0:
1923 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1925 Non-boot pools do not need these updates.
1929 If you are updating from a prior version of FreeBSD (even one just
1930 a few days old), you should follow this procedure. It is the most
1931 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1933 make kernel-toolchain
1934 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1935 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1937 To test a kernel once
1938 ---------------------
1939 If you just want to boot a kernel once (because you are not sure
1940 if it works, or if you want to boot a known bad kernel to provide
1941 debugging information) run
1942 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1943 nextboot -k testkernel
1945 To rebuild everything and install it on the current system.
1946 -----------------------------------------------------------
1947 # Note: sometimes if you are running current you gotta do more than
1948 # is listed here if you are upgrading from a really old current.
1950 <make sure you have good level 0 dumps>
1952 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1953 make installkernel KERNCONF=YOUR_KERNEL_HERE
1955 <reboot in single user> [3]
1962 To cross-install current onto a separate partition
1963 --------------------------------------------------
1964 # In this approach we use a separate partition to hold
1965 # current's root, 'usr', and 'var' directories. A partition
1966 # holding "/", "/usr" and "/var" should be about 2GB in
1969 <make sure you have good level 0 dumps>
1972 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1973 <maybe newfs current's root partition>
1974 <mount current's root partition on directory ${CURRENT_ROOT}>
1975 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1976 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1977 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1978 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1979 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1980 <reboot into current>
1981 <do a "native" rebuild/install as described in the previous section>
1982 <maybe install compatibility libraries from ports/misc/compat*>
1986 To upgrade in-place from stable to current
1987 ----------------------------------------------
1988 <make sure you have good level 0 dumps>
1990 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1991 make installkernel KERNCONF=YOUR_KERNEL_HERE
1993 <reboot in single user> [3]
2000 Make sure that you've read the UPDATING file to understand the
2001 tweaks to various things you need. At this point in the life
2002 cycle of current, things change often and you are on your own
2003 to cope. The defaults can also change, so please read ALL of
2004 the UPDATING entries.
2006 Also, if you are tracking -current, you must be subscribed to
2007 freebsd-current@freebsd.org. Make sure that before you update
2008 your sources that you have read and understood all the recent
2009 messages there. If in doubt, please track -stable which has
2010 much fewer pitfalls.
2012 [1] If you have third party modules, such as vmware, you
2013 should disable them at this point so they don't crash your
2016 [3] From the bootblocks, boot -s, and then do
2021 adjkerntz -i # if CMOS is wall time
2022 Also, when doing a major release upgrade, it is required that
2023 you boot into single user mode to do the installworld.
2025 [4] Note: This step is non-optional. Failure to do this step
2026 can result in a significant reduction in the functionality of the
2027 system. Attempting to do it by hand is not recommended and those
2028 that pursue this avenue should read this file carefully, as well
2029 as the archives of freebsd-current and freebsd-hackers mailing lists
2030 for potential gotchas. The -U option is also useful to consider.
2031 See mergemaster(8) for more information.
2033 [5] Usually this step is a no-op. However, from time to time
2034 you may need to do this if you get unknown user in the following
2035 step. It never hurts to do it all the time. You may need to
2036 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2037 install) after the buildworld before this step if you last updated
2038 from current before 20130425 or from -stable before 20130430.
2040 [6] This only deletes old files and directories. Old libraries
2041 can be deleted by "make delete-old-libs", but you have to make
2042 sure that no program is using those libraries anymore.
2044 [8] The new kernel must be able to run existing binaries used by
2045 an installworld. When upgrading across major versions, the new
2046 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2047 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2048 binaries). Failure to do so may leave you with a system that is
2049 hard to boot to recover. A GENERIC kernel will include suitable
2050 compatibility options to run binaries from older branches.
2052 Make sure that you merge any new devices from GENERIC since the
2053 last time you updated your kernel config file.
2055 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2056 "?=" instead of the "=" assignment operator, so that buildworld can
2057 override the CPUTYPE if it needs to.
2059 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2060 not on the command line, or in /etc/make.conf. buildworld will
2061 warn if it is improperly defined.
2064 This file contains a list, in reverse chronological order, of major
2065 breakages in tracking -current. It is not guaranteed to be a complete
2066 list of such breakages, and only contains entries since September 23, 2011.
2067 If you need to see UPDATING entries from before that date, you will need
2068 to fetch an UPDATING file from an older FreeBSD release.
2070 Copyright information:
2072 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2074 Redistribution, publication, translation and use, with or without
2075 modification, in full or in part, in any form or format of this
2076 document are permitted without further permission from the author.
2078 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2079 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2080 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2081 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2082 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2083 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2084 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2085 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2086 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2087 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2088 POSSIBILITY OF SUCH DAMAGE.
2090 Contact Warner Losh if you have any questions about your use of