1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 20201201: p11 FreeBSD-EN-20:20.tzdata
20 FreeBSD-SA-20:31.icmp6
21 FreeBSD-SA-20:32.rtsold
23 Update timezone database information. [EN-20:20.tzdata]
25 Fix ICMPv6 use-after-free in error message handling. [SA-20:31.icmp6]
27 Fix multiple vulnerabilities in rtsold. [SA-20:32.rtsold]
29 20200915 p10 FreeBSD-SA-20:27.ure
30 FreeBSD-SA-20:28.bhyve_vmcs
31 FreeBSD-SA-20:29.bhyve_svm
34 Fix ure device driver susceptible to packet-in-packet attack.
37 Fix bhyve privilege escalation via VMCS access. [SA-20:28.bhyve_vmcs]
39 Fix bhyve SVM guest escape. [SA-20:29.bhyve_svm]
41 Fix ftpd privilege escalation via ftpchroot. [SA-20:30.ftpd]
43 20200902 p9 FreeBSD-EN-20:17.linuxthread
45 FreeBSD-SA-20:26.dhclient
47 Fix FreeBSD Linux ABI kernel panic. [EN-20:17.linuxthread]
49 Fix SCTP socket use-after-free. [SA-20:25.sctp]
51 Fix dhclient heap overflow. [SA-20:26.dhclient]
53 20200805 p8 FreeBSD-EN-20:16.vmx
54 FreeBSD-SA-20:21.usb_net
55 FreeBSD-SA-20:22.unbound
58 Fix vmx driver packet loss and degraded performance. [EN-20:16.vmx]
60 Fix memory corruption in USB network device drivers. [SA-20:21.usb_net]
62 Fix multiple vulnerabilities in sqlite3. [SA-20:22.sqlite]
64 Fix sendmsg(2) privilege escalation. [SA-20:23.sendmsg]
66 20200708 p7 FreeBSD-EN-20:13.bhyve
67 FreeBSD-EN-20:14.linuxkpi
69 FreeBSD-SA-20:19.unbound
72 Fix host crash in bhyve with PCI device passthrough. [EN-20:13.bhyve]
74 Fix kernel panic in LinuxKPI subsystem. [EN-20:14.linuxpki]
76 Fix kernel panic in mps(4) driver. [EN-20:15.mps]
78 Fix multiple vulnerabilities in unbound. [SA-20:19.unbound]
80 Fix IPv6 socket option race condition and use after free. [SA-20:20.ipv6]
82 20200609 p6 FreeBSD-EN-20:11.ena
83 FreeBSD-EN-20:12.iflib
86 Fix stability issues in ena(4) driver. [EN-20:11.ena]
88 Fix iflib watchdog timeout resetting idle queues. [EN-20:12.iflib]
90 Fix USB HID descriptor parsing error. [SA-20:17.usb]
92 20200512 p5 FreeBSD-EN-20:08.tzdata
94 FreeBSD-EN-20:10.build
95 FreeBSD-SA-20:12.libalias
96 FreeBSD-SA-20:13.libalias
97 FreeBSD-SA-20:15.cryptodev
98 FreeBSD-SA-20:16.cryptodev
100 Import tzdata 2020a. [EN-20:08.tzdata]
102 Fix igb interfaces failing to switch to inactive state [EN-20:09.igb]
104 Fix incorrect build host Clang version detection [EN-20:10.build]
106 Fix insufficient packet length validation in libalias [SA-20:12.libalias]
108 Fix memory disclosure vulnerability in libalias [SA-20:13.libalias]
110 Fix use after free in cryptodev module [SA-20:15.cryptodev]
112 Fix insufficient cryptodev MAC key length check [SA-20:16.cryptodev]
114 20200421 p4 FreeBSD-EN-20:07.quotad
115 FreeBSD-SA-20:10.ipfw
116 FreeBSD-SA-20:11.openssl
118 Fix regression in rpc.rquotad with certain NFS servers [EN-20:07.quotad]
120 Fix ipfw invalid mbuf handling [SA-20:10.ipfw]
122 Fix OpenSSL remote denial of service vulnerability [SA-20:11.openssl]
124 20200319 p3 FreeBSD-EN-20:03.sshd
125 FreeBSD-EN-20:05.mlx5en
126 FreeBSD-EN-20:06.ipv6
128 FreeBSD-SA-20:05.if_oce_ioctl
129 FreeBSD-SA-20:06.if_ixl_ioctl
130 FreeBSD-SA-20:07.epair
131 FreeBSD-SA-20:08.jail
134 Fix misleading log messages upon successful sshd login [EN-20:03.sshd]
136 Fix packet forwarding performance in mlx5en(4) driver [EN-20:05.mlx5en]
138 Fix incorrect checksum calculations with IPv6 extension headers [EN-20:06.ipv6]
140 Fix TCP IPv6 SYN cache kernel information disclosure [SA-20:04.tcp]
142 Fix insufficient oce(4) ioctl(2) privilege checking [SA-20:05.if_oce_ioctl]
144 Fix insufficient ixl(4) ioctl(2) privilege checking [SA-20:06.if_ixl_ioctl]
146 Fix incorrect user-controlled pointer use in epair [SA-20:07.epair]
148 Fix kernel memory disclosure with nested jails [SA-20:08.jail]
150 Fix multiple denial of service in ntpd [SA-20:09.ntp]
152 20200128 p2 FreeBSD-EN-20:01.ssp
153 FreeBSD-SA-20:01.libfetch
154 FreeBSD-SA-20:03.thrmisc
156 Fix imprecise ordering of SSP canary initialization [EN-20:01.ssp]
158 Fix libfetch buffer overflow [SA-20:01.libfetch]
160 Fix kernel stack data disclosure [SA-20:03.thrmisc]
162 20191112 p1 FreeBSD-EN-19:19.loader
163 FreeBSD-SA-19:25.mcepsc
165 Fix UEFI Loader Memory Fragmentation [EN-19:19.loader]
167 Fix Machine Check Exception on Page Size Change [SA-19:25.mcepsc]
173 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
174 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
175 been removed from mount_fusefs(8). You can safely remove them from
176 your scripts, because they had no effect.
178 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
179 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
180 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
181 sysctls have been removed. If you felt the need to set any of them to
182 a non-default value, please tell asomers@FreeBSD.org why.
185 The fuse(4) module has been renamed to fusefs(4) for consistency with
186 other filesystems. You should update any kld_load="fuse" entries in
187 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
188 "options FUSE" enties in kernel config files.
191 Default permissions on the /var/account/acct file (and copies of it
192 rotated by periodic daily scripts) are changed from 0644 to 0640
193 because the file contains sensitive information that should not be
194 world-readable. If the /var/account directory must be created by
195 rc.d/accounting, the mode used is now 0750. Admins who use the
196 accounting feature are encouraged to change the mode of an existing
197 /var/account directory to 0750 or 0700.
200 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
201 been upgraded to 8.0.1. Please see the 20141231 entry below for
202 information about prerequisites and upgrading, if you are not already
203 using clang 3.5.0 or higher.
206 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
207 functionality needed for the RETPOLINE option should work properly
208 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
211 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
212 8.0.0. Please see the 20141231 entry below for information about
213 prerequisites and upgrading, if you are not already using clang 3.5.0
217 The RETPOLINE option produces non-functional ifunc-using binaries
218 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
219 Once Clang 8 is merged it may be enabled again.
222 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
223 7.0.1. Please see the 20141231 entry below for information about
224 prerequisites and upgrading, if you are not already using clang 3.5.0
228 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
229 compiled into your custom kernel, add 'device xz' statement to the
233 Iflib is no longer unconditionally compiled into the kernel. Drivers
234 using iflib and statically compiled into the kernel, now require
235 the 'device iflib' config option. For the same drivers loaded as
236 modules on kernels not having 'device iflib', the iflib.ko module
237 is loaded automatically.
240 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
241 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
242 servers that have vfs.nfsd.nfs_privport set will only allow mounts
243 from clients using a reserved port#. Since both the FreeBSD and Linux
244 NFSv4 clients use reserved port#s by default, this should not affect
248 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
249 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
250 it produces broken binaries when ifuncs are in use. Users needing
251 GNU ld should install the binutils port or package.
254 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
255 has been converted to a port (misc/ctm) and will be removed from
256 FreeBSD-13. A depreciation warning will be printed to stderr by
257 the ctm command, but the functionality will remain in base for all
261 The stable/12 branch has been created in subversion from head
265 Ports for the DRM modules have been simplified. Now, amd64 users should
266 just install the drm-kmod port. All others should install
269 Graphics hardware that's newer than about 2010 usually works with
270 drm-kmod. For hardware older than 2013, however, some users will need
271 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
272 than 2008 usually only works in drm-legacy-kmod. The graphics team can
273 only commit to hardware made since 2013 due to the complexity of the
274 market and difficulty to test all the older cards effectively. If you
275 have hardware supported by drm-kmod, you are strongly encouraged to use
276 that as you will get better support.
278 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
279 elsewhere, the drm and drm2 modules will be eliminated from the src base
280 soon (with a limited exception for arm). Please update to the package asap
281 and report any issues to x11@freebsd.org.
283 Generally, anybody using the drm*-kmod packages should add
284 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
285 cross-threading surprises, especially with automatic driver
286 loading from X11 startup. These will become the defaults in 13-current
290 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
291 custom kernel and module loading configuration files must be updated
292 accordingly. Moreover, interfaces previous presented as ixlvN to the
293 system are now exposed as iavfN and network configuration files must
294 be adjusted as necessary.
297 OpenSSL has been updated to version 1.1.1. This update included
298 additional various API changes througout the base system. It is
299 important to rebuild third-party software after upgrading. The value
300 of __FreeBSD_version has been bumped accordingly.
303 The legacy DRM modules and drivers have now been added to the loader's
304 module blacklist, in favor of loading them with kld_list in rc.conf(5).
305 The module blacklist may be overridden with the loader.conf(5)
306 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
310 The cam(4) based nda(4) driver will be used over nvd(4) by default on
311 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
312 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
313 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
317 Reproducible build mode is now on by default, in preparation for
318 FreeBSD 12.0. This eliminates build metadata such as the user,
319 host, and time from the kernel (and uname), unless the working tree
320 corresponds to a modified checkout from a version control system.
321 The previous behavior can be obtained by setting the /etc/src.conf
322 knob WITHOUT_REPRODUCIBLE_BUILD.
325 The Yarrow CSPRNG has been removed from the kernel as it has not been
326 supported by its designers since at least 2003. Fortuna has been the
327 default since FreeBSD-11.
330 devctl freeze/thaw have gone into the tree, the rc scripts have been
331 updated to use them and devmatch has been changed. You should update
332 kernel, userland and rc scripts all at the same time.
335 The default interpreter has been switched from 4th to Lua.
336 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
337 interpreter. If you have custom FORTH code you will need to set
338 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
339 src.conf for the build. This will create default hard links between
340 loader and loader_4th instead of loader and loader_lua, the new default.
341 If you are using UEFI it will create the proper hard link to loader.efi.
343 bhyve uses userboot.so. It remains 4th-only until some issues are solved
344 regarding coexisting with multiple versions of FreeBSD are resolved.
347 ls(1) now respects the COLORTERM environment variable used in other
348 systems and software to indicate that a colored terminal is both
349 supported and desired. If ls(1) is suddenly emitting colors, they may
350 be disabled again by either removing the unwanted COLORTERM from your
351 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
352 may not be observed in a future release.
355 The default pager for most commands has been changed to "less". To
356 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
360 The jedec_ts(4) driver has been removed. A superset of its functionality
361 is available in the jedec_dimm(4) driver, and the manpage for that
362 driver includes migration instructions. If you have "device jedec_ts"
363 in your kernel configuration file, it must be removed.
366 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
367 This should have no effect if the kernel is booted via BIOS/legacy boot.
368 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
369 has a buggy firmware that prevents a successful boot due to use of
373 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
374 support has been removed from the tree. These ports were
375 obsolete and/or known to be broken for many years.
378 loader.efi has been augmented to participate more fully in the
379 UEFI boot manager protocol. loader.efi will now look at the
380 BootXXXX environment variable to determine if a specific kernel
381 or root partition was specified. XXXX is derived from BootCurrent.
382 efibootmgr(8) manages these standard UEFI variables.
385 zfsloader's functionality has now been folded into loader.
386 zfsloader is no longer necessary once you've updated your
387 boot blocks. For a transition period, we will install a
388 hardlink for zfsloader to loader to allow a smooth transition
389 until the boot blocks can be updated (hard link because old
390 zfs boot blocks don't understand symlinks).
393 ARM64 now have efifb support, if you want to have serial console
394 on your arm64 board when an screen is connected and the bootloader
395 setup a frambuffer for us to use, just add :
399 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
400 an screen connected as the firmware will setup a framebuffer are that
401 u-boot will expose as an EFI framebuffer.
404 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
405 or take steps to update /etc/passwd before doing installworld on
406 existing systems. Do not skip the "mergemaster -Fp" step before
407 installworld, as described in the update procedures near the bottom
408 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
409 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
410 the ntp config file contain options that change file/dir locations.
411 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
412 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
413 taking steps to ensure that all required files/dirs are accessible
417 Big endian arm support has been removed.
420 The static environment setup in kernel configs is no longer mutually
421 exclusive with the loader(8) environment by default. In order to
422 restore the previous default behavior of disabling the loader(8)
423 environment if a static environment is present, you must specify
424 loader_env.disabled=1 in the static environment.
427 The ABI of syscalls used by management tools like sockstat and
428 netstat has been broken to allow 32-bit binaries to work on
429 64-bit kernels without modification. These programs will need
430 to match the kernel in order to function. External programs may
431 require minor modifications to accommodate a change of type in
432 structures from pointers to 64-bit virtual addresses.
435 On i386 and amd64 atomics are now inlined. Out of tree modules using
436 atomics will need to be rebuilt.
439 The '%I' format in the kern.corefile sysctl limits the number of
440 core files that a process can generate to the number stored in the
441 debug.ncores sysctl. The '%I' format is replaced by the single digit
442 index. Previously, if all indexes were taken the kernel would overwrite
443 only a core file with the highest index in a filename.
444 Currently the system will create a new core file if there is a free
445 index or if all slots are taken it will overwrite the oldest one.
448 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
449 6.0.1. Please see the 20141231 entry below for information about
450 prerequisites and upgrading, if you are not already using clang 3.5.0
454 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
455 needed to be changed to work with it. This change was made with r335763
456 and requires a mergemaster / etcupdate / etc to update the installed file.
459 r334930 changed the interface between the NFS modules, so they all
460 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
463 As of r334391 lld is the default amd64 system linker; it is installed
464 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
468 The kernel / userland interface for devinfo changed, so you'll
469 need a new kernel and userland as a pair for it to work (rebuilding
470 lib/libdevinfo is all that's required). devinfo and devmatch will
471 not work, but everything else will when there's a mismatch.
474 The on-disk format for hwpmc callchain records has changed to include
475 threadid corresponding to a given record. This changes the field offsets
476 and thus requires that libpmcstat be rebuilt before using a kernel
480 The vxge(4) driver has been removed. This driver was introduced into
481 HEAD one week before the Exar left the Ethernet market and is not
482 known to be used. If you have device vxge in your kernel config file
486 The amd64 kernel now requires a ld that supports ifunc to produce a
487 working kernel, either lld or a newer binutils. lld is built by default
488 on amd64, and the 'buildkernel' target uses it automatically. However,
489 it is not the default linker, so building the kernel the traditional
490 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
491 binutils port/package). lld will soon be default, and this requirement
494 NOTE: As of r334391 lld is the default system linker on amd64, and no
495 workaround is necessary.
498 The nxge(4) driver has been removed. This driver was for PCI-X 10g
499 cards made by s2io/Neterion. The company was aquired by Exar and
500 no longer sells or supports Ethernet products. If you have device
501 nxge in your kernel config file it must be removed.
504 The tz database (tzdb) has been updated to 2018e. This version more
505 correctly models time stamps in time zones with negative DST such as
506 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
507 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
508 time zone abbreviations and the tm_isdst flag.
511 The ixgb(4) driver has been removed. This driver was for an early and
512 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
513 quickly shifted to the long lived ixgbe family. If you have device
514 ixgb in your kernel config file it must be removed.
517 The lmc(4) driver has been removed. This was a WAN interface
518 card that was already reportedly rare in 2003, and had an ambiguous
519 license. If you have device lmc in your kernel config file it must
523 Support for Arcnet networks has been removed. If you have device
524 arcnet or device cm in your kernel config file they must be
528 Support for FDDI networks has been removed. If you have device
529 fddi or device fpa in your kernel config file they must be
533 In addition to supporting RFC 3164 formatted messages, the
534 syslogd(8) service is now capable of parsing RFC 5424 formatted
535 log messages. The main benefit of using RFC 5424 is that clients
536 may now send log messages with timestamps containing year numbers,
537 microseconds and time zone offsets.
539 Similarly, the syslog(3) C library function has been altered to
540 send RFC 5424 formatted messages to the local system logging
541 daemon. On systems using syslogd(8), this change should have no
542 negative impact, as long as syslogd(8) and the C library are
543 updated at the same time. On systems using a different system
544 logging daemon, it may be necessary to make configuration
545 adjustments, depending on the software used.
547 When using syslog-ng, add the 'syslog-protocol' flag to local
548 input sources to enable parsing of RFC 5424 formatted messages:
551 unix-dgram("/var/run/log" flags(syslog-protocol));
554 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
555 of the 'imuxsock' module to let messages be processed by the
556 regular RFC 3164/5424 parsing pipeline:
558 module(load="imuxsock" SysSock.UseSpecialParser="off")
560 Do note that these changes only affect communication between local
561 applications and syslogd(8). The format that syslogd(8) uses to
562 store messages on disk or forward messages to other systems
563 remains unchanged. syslogd(8) still uses RFC 3164 for these
564 purposes. Options to customize this behaviour will be added in the
565 future. Utilities that process log files stored in /var/log are
566 thus expected to continue to function as before.
568 __FreeBSD_version has been incremented to 1200061 to denote this
572 Support for token ring networks has been removed. If you
573 have "device token" in your kernel config you should remove
574 it. No device drivers supported token ring.
577 makefs was modified to be able to tag ISO9660 El Torito boot catalog
578 entries as EFI instead of overloading the i386 tag as done previously.
579 The amd64 mkisoimages.sh script used to build amd64 ISO images for
580 release was updated to use this. This may mean that makefs must be
581 updated before "make cdrom" can be run in the release directory. This
582 should be as simple as:
584 $ cd $SRCDIR/usr.sbin/makefs
585 $ make depend all install
588 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
589 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
590 Co-existance for the transition period will come shortly. Booting is a
591 complex environment and test coverage for Lua-enabled loaders has been
592 thin, so it would be prudent to assume it might not work and make
593 provisions for backup boot methods.
596 devmatch functionality has been turned on in devd. It will automatically
597 load drivers for unattached devices. This may cause unexpected drivers to
598 be loaded. Please report any problems to current@ and imp@freebsd.org.
601 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
602 6.0.0. Please see the 20141231 entry below for information about
603 prerequisites and upgrading, if you are not already using clang 3.5.0
607 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
608 This means it is used to link the kernel and userland libraries and
609 executables, but is not yet installed as /usr/bin/ld by default.
611 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
612 WITHOUT_LLD_BOOTSTRAP=yes
615 On i386, pmtimer has been removed. Its functionality has been folded
616 into apm. It was a no-op on ACPI in current for a while now (but was still
617 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
618 from kernel config files.
621 The use of RSS hash from the network card aka flowid has been
622 disabled by default for lagg(4) as it's currently incompatible with
623 the lacp and loadbalance protocols.
625 This can be re-enabled by setting the following in loader.conf:
626 net.link.lagg.default_use_flowid="1"
629 The SW_WATCHDOG option is no longer necessary to enable the
630 hardclock-based software watchdog if no hardware watchdog is
631 configured. As before, SW_WATCHDOG will cause the software
632 watchdog to be enabled even if a hardware watchdog is configured.
635 r326887 fixes the issue described in the 20171214 UPDATING entry.
636 r326888 flips the switch back to building GELI support always.
639 r362593 broke ZFS + GELI support for reasons unknown. However,
640 it also broke ZFS support generally, so GELI has been turned off
641 by default as the lesser evil in r326857. If you boot off ZFS and/or
642 GELI, it might not be a good time to update.
645 PowerPC users must update loader(8) by rebuilding world before
646 installing a new kernel, as the protocol connecting them has
647 changed. Without the update, loader metadata will not be passed
648 successfully to the kernel and users will have to enter their
649 root partition at the kernel mountroot prompt to continue booting.
650 Newer versions of loader can boot old kernels without issue.
653 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
654 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
655 to WITH/OUT_LOADER_GELI.
658 The naive and non-compliant support of posix_fallocate(2) in ZFS
659 has been removed as of r325320. The system call now returns EINVAL
660 when used on a ZFS file. Although the new behavior complies with the
661 standard, some consumers are not prepared to cope with it.
662 One known victim is lld prior to r325420.
665 Building in a FreeBSD src checkout will automatically create object
666 directories now rather than store files in the current directory if
667 'make obj' was not ran. Calling 'make obj' is no longer necessary.
668 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
669 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
673 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
674 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
675 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
676 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
677 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
678 The UNIFIED_OBJDIR option is a transitional feature that will be
679 removed for 12.0 release; please migrate to the new format for any
680 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
681 than hardcoding paths.
684 The native-xtools target no longer installs the files by default to the
685 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
686 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
689 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
690 options are changing from controlling the build if defined / undefined
691 to controlling the build with explicit 'yes' or 'no' values. They will
692 shift to WITH/WITHOUT options to match other options in the system.
695 libstand has turned into a private library for sys/boot use only.
696 It is no longer supported as a public interface outside of sys/boot.
699 The arm port has split armv6 into armv6 and armv7. armv7 is now
700 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
701 and are running a kernel from before r324363, you will need to add
702 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
705 When building multiple kernels using KERNCONF, non-existent KERNCONF
706 files will produce an error and buildkernel will fail. Previously
707 missing KERNCONF files silently failed giving no indication as to
708 why, only to subsequently discover during installkernel that the
709 desired kernel was never built in the first place.
712 The default serial number format for CTL LUNs has changed. This will
713 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
714 or iSCSI clients care about their LUNs' serial numbers. Users who
715 require serial number stability should hardcode serial numbers in
719 For 32-bit arm compiled for hard-float support, soft-floating point
720 binaries now always get their shared libraries from
721 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
722 /usr/libsoft also existed). Only users with a hard-float ld.so, but
723 soft-float everything else should be affected.
726 The geli password typed at boot is now hidden. To restore the previous
727 behavior, see geli(8) for configuration options.
730 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
731 sysctl values. Minor nit, but requires a rebuild of both world/kernel
735 "make check" behavior (made in ^/head@r295380) has been changed to
736 execute from a limited sandbox, as opposed to executing from
740 - The "beforecheck" and "aftercheck" targets are now specified.
741 - ${CHECKDIR} (added in commit noted above) has been removed.
742 - Legacy behavior can be enabled by setting
743 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
745 If the limited sandbox mode is enabled, "make check" will execute
746 "make distribution", then install, execute the tests, and clean up the
747 sandbox if successful.
749 The "make distribution" and "make install" targets are typically run as
750 root to set appropriate permissions and ownership at installation time.
751 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
752 environment if executing "make check" with limited sandbox mode using
753 an unprivileged user.
756 Since the switch to GPT disk labels, fsck for UFS/FFS has been
757 unable to automatically find alternate superblocks. As of r322297,
758 the information needed to find alternate superblocks has been
759 moved to the end of the area reserved for the boot block.
760 Filesystems created with a newfs of this vintage or later
761 will create the recovery information. If you have a filesystem
762 created prior to this change and wish to have a recovery block
763 created for your filesystem, you can do so by running fsck in
764 foreground mode (i.e., do not use the -p or -y options). As it
765 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
766 to which you should answer yes.
769 As of r321665, an NFSv4 server configuration that services
770 Kerberos mounts or clients that do not support the uid/gid in
771 owner/owner_group string capability, must explicitly enable
772 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
773 machine's /etc/rc.conf file.
776 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
777 Please see the 20141231 entry below for information about prerequisites
778 and upgrading, if you are not already using clang 3.5.0 or higher.
781 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
782 r-commands (rlogin, rsh, etc.) to be built with the base system.
785 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
786 a very major ABI incompatible change, so users of FreeBSD/powerpc must
787 be careful when performing source upgrades. It is best to run
788 'make installworld' from an alternate root system, either a live
789 CD/memory stick, or a temporary root partition. Additionally, all ports
790 must be recompiled. powerpc64 is largely unaffected, except in the case
791 of 32-bit compatibility. All 32-bit binaries will be affected.
794 Forward compatibility for the "ino64" project have been committed. This
795 will allow most new binaries to run on older kernels in a limited
796 fashion. This prevents many of the common foot-shooting actions in the
797 upgrade as well as the limited ability to roll back the kernel across
798 the ino64 upgrade. Complicated use cases may not work properly, though
799 enough simpler ones work to allow recovery in most situations.
802 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
803 if you require the GPL compiler.
806 The internal ABI used for communication between the NFS kernel modules
807 was changed by r320085, so __FreeBSD_version was bumped to
808 ensure all the NFS related modules are updated together.
811 The ABI of struct event was changed by extending the data
812 member to 64bit and adding ext fields. For upgrade, same
813 precautions as for the entry 20170523 "ino64" must be
817 The GNU roff toolchain has been removed from base. To render manpages
818 which are not supported by mandoc(1), man(1) can fallback on GNU roff
819 from ports (and recommends to install it).
820 To render roff(7) documents, consider using GNU roff from ports or the
821 heirloom doctools roff toolchain from ports via pkg install groff or
822 via pkg install heirloom-doctools.
825 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
826 smaller runtime footprint builds. This is useful for embedded systems
827 which only require one chipset support.
829 If you load it as a module, make sure this is in /boot/loader.conf:
833 This will load the HAL, all chip/RF backends and if_ath_pci.
834 If you have if_ath_pci in /boot/loader.conf, ensure it is after
835 if_ath or it will not load any HAL chipset support.
837 If you want to selectively load things (eg on ye cheape ARM/MIPS
838 platforms where RAM is at a premium) you should:
841 * load the chip modules in question
842 * load ath_rate, ath_dfs
844 * load if_ath_pci and/or if_ath_ahb depending upon your particular
845 bus bind type - this is where probe/attach is done.
847 For further comments/feedback, poke adrian@ .
850 The "ino64" 64-bit inode project has been committed, which extends
851 a number of types to 64 bits. Upgrading in place requires care and
852 adherence to the documented upgrade procedure.
854 If using a custom kernel configuration ensure that the
855 COMPAT_FREEBSD11 option is included (as during the upgrade the
856 system will be running the ino64 kernel with the existing world).
858 For the safest in-place upgrade begin by removing previous build
859 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
860 full procedure documented below under the heading "To rebuild
861 everything and install it on the current system." Specifically,
862 a reboot is required after installing the new kernel before
866 The NATM framework including the en(4), fatm(4), hatm(4), and
867 patm(4) devices has been removed. Consumers should plan a
868 migration before the end-of-life date for FreeBSD 11.
871 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
872 diff has not been implemented, if those are needed a newer version of
873 GNU diff is available via the diffutils package under the gdiff name.
876 As of r316810 for ipfilter, keep frags is no longer assumed when
877 keep state is specified in a rule. r316810 aligns ipfilter with
878 documentation in man pages separating keep frags from keep state.
879 This allows keep state to be specified without forcing keep frags
880 and allows keep frags to be specified independently of keep state.
881 To maintain previous behaviour, also specify keep frags with
882 keep state (as documented in ipf.conf.5).
885 arm64 builds now use the base system LLD 4.0.0 linker by default,
886 instead of requiring that the aarch64-binutils port or package be
887 installed. To continue using aarch64-binutils, set
888 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
891 The UDP optimization in entry 20160818 that added the sysctl
892 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
893 packets will no longer be treated as L3 broadcast packets.
896 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
897 use any explicitly assigned loopback address available in the jail
898 instead of using the first assigned address of the jail.
901 The ctl.ko module no longer implements the iSCSI target frontend:
902 cfiscsi.ko does instead.
904 If building cfiscsi.ko as a kernel module, the module can be loaded
905 via one of the following methods:
906 - `cfiscsi_load="YES"` in loader.conf(5).
907 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
908 - ctladm(8)/ctld(8), when compiled with iSCSI support
909 (`WITH_ISCSI=yes` in src.conf(5))
911 Please see cfiscsi(4) for more details.
914 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
915 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
916 same source (previously, the dependency of mmcsd.ko on mmc.ko was
917 missing, but mmcsd.ko now will refuse to load if it is incompatible
921 The syntax of ipfw(8) named states was changed to avoid ambiguity.
922 If you have used named states in the firewall rules, you need to modify
923 them after installworld and before rebooting. Now named states must
924 be prefixed with colon.
927 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
928 removed as the userland we provide cannot use them. The KMS version
929 (sys/dev/drm2) supports the same hardware.
932 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
933 Please see the 20141231 entry below for information about prerequisites
934 and upgrading, if you are not already using clang 3.5.0 or higher.
937 The code that provides support for ZFS .zfs/ directory functionality
938 has been reimplemented. It's not possible now to create a snapshot
939 by mkdir under .zfs/snapshot/. That should be the only user visible
943 EISA bus support has been removed. The WITH_EISA option is no longer
947 MCA bus support has been removed.
950 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
951 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
954 The EM_MULTIQUEUE kernel configuration option is deprecated now that
955 the em(4) driver conforms to iflib specifications.
958 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
959 IFLIB. If you have a custom kernel configuration that excludes em(4)
960 but you use igb(4), you need to re-add em(4) to your custom configuration.
963 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
964 Please see the 20141231 entry below for information about prerequisites
965 and upgrading, if you are not already using clang 3.5.0 or higher.
968 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
969 Please see the 20141231 entry below for information about prerequisites
970 and upgrading, if you are not already using clang 3.5.0 or higher.
973 The layout of the pmap structure has changed for powerpc to put the pmap
974 statistics at the front for all CPU variations. libkvm(3) and all tools
975 that link against it need to be recompiled.
978 isl(4) and cyapa(4) drivers now require a new driver,
979 chromebook_platform(4), to work properly on Chromebook-class hardware.
980 On other types of hardware the drivers may need to be configured using
981 device hints. Please see the corresponding manual pages for details.
984 The urtwn(4) driver was merged into rtwn(4) and now consists of
985 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
987 Also, firmware for RTL8188CE was renamed due to possible name
988 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
991 GNU rcs has been removed from base. It is available as packages:
992 - rcs: Latest GPLv3 GNU rcs version.
993 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
997 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
998 modules now requires that the kernel configuration contain the
999 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1002 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1003 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1006 Relocatable object files with the extension of .So have been renamed
1007 to use an extension of .pico instead. The purpose of this change is
1008 to avoid a name clash with shared libraries on case-insensitive file
1009 systems. On those file systems, foo.So is the same file as foo.so.
1012 GNU rcs has been turned off by default. It can (temporarily) be built
1013 again by adding WITH_RCS knob in src.conf.
1014 Otherwise, GNU rcs is available from packages:
1015 - rcs: Latest GPLv3 GNU rcs version.
1016 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1019 The backup_uses_rcs functionality has been removed from rc.subr.
1022 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1023 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1024 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1025 QUEUE_MACRO_DEBUG behavior.
1028 r304787 changed some ioctl interfaces between the iSCSI userspace
1029 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1030 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1034 The UDP receive code has been updated to only treat incoming UDP
1035 packets that were addressed to an L2 broadcast address as L3
1036 broadcast packets. It is not expected that this will affect any
1037 standards-conforming UDP application. The new behaviour can be
1038 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1042 Remove the openbsd_poll system call.
1043 __FreeBSD_version has been bumped because of this.
1046 The stable/11 branch has been created from head@r302406.
1049 The libc stub for the pipe(2) system call has been replaced with
1050 a wrapper that calls the pipe2(2) system call and the pipe(2)
1051 system call is now only implemented by the kernels that include
1052 "options COMPAT_FREEBSD10" in their config file (this is the
1053 default). Users should ensure that this option is enabled in
1054 their kernel or upgrade userspace to r302092 before upgrading their
1058 CAM will now strip leading spaces from SCSI disks' serial numbers.
1059 This will affect users who create UFS filesystems on SCSI disks using
1060 those disk's diskid device nodes. For example, if /etc/fstab
1061 previously contained a line like
1062 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1063 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1064 transforms like gmirror may also be affected. ZFS users should
1068 The bitstring(3) API has been updated with new functionality and
1069 improved performance. But it is binary-incompatible with the old API.
1070 Objects built with the new headers may not be linked against objects
1071 built with the old headers.
1074 The brk and sbrk functions have been removed from libc on arm64.
1075 Binutils from ports has been updated to not link to these
1076 functions and should be updated to the latest version before
1077 installing a new libc.
1080 The armv6 port now defaults to hard float ABI. Limited support
1081 for running both hardfloat and soft float on the same system
1082 is available using the libraries installed with -DWITH_LIBSOFT.
1083 This has only been tested as an upgrade path for installworld
1084 and packages may fail or need manual intervention to run. New
1085 packages will be needed.
1087 To update an existing self-hosted armv6hf system, you must add
1088 TARGET_ARCH=armv6 on the make command line for both the build
1089 and the install steps.
1092 Kernel modules compiled outside of a kernel build now default to
1093 installing to /boot/modules instead of /boot/kernel. Many kernel
1094 modules built this way (such as those in ports) already overrode
1095 KMODDIR explicitly to install into /boot/modules. However,
1096 manually building and installing a module from /sys/modules will
1097 now install to /boot/modules instead of /boot/kernel.
1100 The CAM I/O scheduler has been committed to the kernel. There should be
1101 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1102 list of known rogues that claim support for this but actually corrupt
1103 data is believed to be complete, be on the lookout for data
1104 corruption. The known rogue list is believed to be complete:
1106 o Crucial MX100, M550 drives with MU01 firmware.
1107 o Micron M510 and M550 drives with MU01 firmware.
1108 o Micron M500 prior to MU07 firmware
1109 o Samsung 830, 840, and 850 all firmwares
1110 o FCCT M500 all firmwares
1112 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1113 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1114 updated firmware. Black listed drives will work correctly because these
1115 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1116 this list is the same as found in Linux, it's believed there are no
1117 other rogues in the market place. All other models from the above
1120 To be safe, if you are at all concerned, you can quirk each of your
1121 drives to prevent NCQ from being sent by setting:
1122 kern.cam.ada.X.quirks="0x2"
1123 in loader.conf. If the drive requires the 4k sector quirk, set the
1124 quirks entry to 0x3.
1127 The FAST_DEPEND build option has been removed and its functionality is
1128 now the one true way. The old mkdep(1) style of 'make depend' has
1129 been removed. See 20160311 for further details.
1132 Resource range types have grown from unsigned long to uintmax_t. All
1133 drivers, and anything using libdevinfo, need to be recompiled.
1136 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1137 builds. It no longer runs mkdep(1) during 'make depend', and the
1138 'make depend' stage can safely be skipped now as it is auto ran
1139 when building 'make all' and will generate all SRCS and DPSRCS before
1140 building anything else. Dependencies are gathered at compile time with
1141 -MF flags kept in separate .depend files per object file. Users should
1142 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1143 stale .depend files.
1146 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1147 kernel modules. Therefore, if you load any kernel modules at boot time,
1148 please install the boot loaders after you install the kernel, but before
1152 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1153 make installkernel KERNCONF=YOUR_KERNEL_HERE
1154 make -C sys/boot install
1155 <reboot in single user>
1157 Then follow the usual steps, described in the General Notes section,
1161 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1162 see the 20141231 entry below for information about prerequisites and
1163 upgrading, if you are not already using clang 3.5.0 or higher.
1166 The AIO subsystem is now a standard part of the kernel. The
1167 VFS_AIO kernel option and aio.ko kernel module have been removed.
1168 Due to stability concerns, asynchronous I/O requests are only
1169 permitted on sockets and raw disks by default. To enable
1170 asynchronous I/O requests on all file types, set the
1171 vfs.aio.enable_unsafe sysctl to a non-zero value.
1174 The ELF object manipulation tool objcopy is now provided by the
1175 ELF Tool Chain project rather than by GNU binutils. It should be a
1176 drop-in replacement, with the addition of arm64 support. The
1177 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1178 to obtain the GNU version if necessary.
1181 Building ZFS pools on top of zvols is prohibited by default. That
1182 feature has never worked safely; it's always been prone to deadlocks.
1183 Using a zvol as the backing store for a VM guest's virtual disk will
1184 still work, even if the guest is using ZFS. Legacy behavior can be
1185 restored by setting vfs.zfs.vol.recursive=1.
1188 The NONE and HPN patches has been removed from OpenSSH. They are
1189 still available in the security/openssh-portable port.
1192 With the addition of ypldap(8), a new _ypldap user is now required
1193 during installworld. "mergemaster -p" can be used to add the user
1194 prior to installworld, as documented in the handbook.
1197 The tftp loader (pxeboot) now uses the option root-path directive. As a
1198 consequence it no longer looks for a pxeboot.4th file on the tftp
1199 server. Instead it uses the regular /boot infrastructure as with the
1203 The code to start recording plug and play data into the modules has
1204 been committed. While the old tools will properly build a new kernel,
1205 a number of warnings about "unknown metadata record 4" will be produced
1206 for an older kldxref. To avoid such warnings, make sure to rebuild
1207 the kernel toolchain (or world). Make sure that you have r292078 or
1208 later when trying to build 292077 or later before rebuilding.
1211 Debug data files are now built by default with 'make buildworld' and
1212 installed with 'make installworld'. This facilitates debugging but
1213 requires more disk space both during the build and for the installed
1214 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1218 r291527 changed the internal interface between the nfsd.ko and
1219 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1220 __FreeBSD_version has been bumped because of this.
1223 Add support for unicode collation strings leads to a change of
1224 order of files listed by ls(1) for example. To get back to the old
1225 behaviour, set LC_COLLATE environment variable to "C".
1227 Databases administrators will need to reindex their databases given
1228 collation results will be different.
1230 Due to a bug in install(1) it is recommended to remove the ancient
1231 locales before running make installworld.
1233 rm -rf /usr/share/locale/*
1236 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1237 libcrypto.so.7 or libssl.so.7 must be recompiled.
1240 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1241 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1242 should be replaced with isp_2400 and isp_2500 modules respectively.
1245 The build previously allowed using 'make -n' to not recurse into
1246 sub-directories while showing what commands would be executed, and
1247 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1248 and 'make -N' will not.
1251 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1252 and etcupdate will now use this file. A custom sendmail.cf is now
1253 updated via this mechanism rather than via installworld. If you had
1254 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1255 want to remove the exclusion or change it to "always install".
1256 /etc/mail/sendmail.cf is now managed the same way regardless of
1257 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1258 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1261 Compatibility shims for legacy ATA device names have been removed.
1262 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1263 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1264 environment variables, /dev/ad* and /dev/ar* symbolic links.
1267 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1268 Please see the 20141231 entry below for information about prerequisites
1269 and upgrading, if you are not already using clang 3.5.0 or higher.
1272 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1273 and renamed from .symbols to .debug. This reduces the size requirements
1274 on the boot partition or file system and provides consistency with
1275 userland debug files.
1277 When using the supported kernel installation method the
1278 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1279 as is done with /boot/kernel.
1281 Developers wishing to maintain the historical behavior of installing
1282 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1285 The wireless drivers had undergone changes that remove the 'parent
1286 interface' from the ifconfig -l output. The rc.d network scripts
1287 used to check presence of a parent interface in the list, so old
1288 scripts would fail to start wireless networking. Thus, etcupdate(3)
1289 or mergemaster(8) run is required after kernel update, to update your
1290 rc.d scripts in /etc.
1293 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1294 These configurations are now automatically interpreted as
1295 'scrub fragment reassemble'.
1298 Kernel-loadable modules for the random(4) device are back. To use
1299 them, the kernel must have
1302 options RANDOM_LOADABLE
1304 kldload(8) can then be used to load random_fortuna.ko
1305 or random_yarrow.ko. Please note that due to the indirect
1306 function calls that the loadable modules need to provide,
1307 the build-in variants will be slightly more efficient.
1309 The random(4) kernel option RANDOM_DUMMY has been retired due to
1310 unpopularity. It was not all that useful anyway.
1313 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1314 Control over building the ELF Tool Chain tools is now provided by
1315 the WITHOUT_TOOLCHAIN knob.
1318 The polarity of Pulse Per Second (PPS) capture events with the
1319 uart(4) driver has been corrected. Prior to this change the PPS
1320 "assert" event corresponded to the trailing edge of a positive PPS
1321 pulse and the "clear" event was the leading edge of the next pulse.
1323 As the width of a PPS pulse in a typical GPS receiver is on the
1324 order of 1 millisecond, most users will not notice any significant
1325 difference with this change.
1327 Anyone who has compensated for the historical polarity reversal by
1328 configuring a negative offset equal to the pulse width will need to
1329 remove that workaround.
1332 The default group assigned to /dev/dri entries has been changed
1333 from 'wheel' to 'video' with the id of '44'. If you want to have
1334 access to the dri devices please add yourself to the video group
1337 # pw groupmod video -m $USER
1340 The menu.rc and loader.rc files will now be replaced during
1341 upgrades. Please migrate local changes to menu.rc.local and
1342 loader.rc.local instead.
1345 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1346 strings and strip have been removed. The src.conf(5) knob
1347 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1350 As ZFS requires more kernel stack pages than is the default on some
1351 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1352 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1354 Please consider using 'options KSTACK_PAGES=X' where X is greater
1355 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1358 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1359 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1360 default, i.e., they will not contain "::". For example, instead
1361 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1362 to have a more specific match, such as different map entries for
1363 IPv6:0:0 vs IPv6:0. This change requires that configuration
1364 data (including maps, files, classes, custom ruleset, etc.) must
1365 use the same format, so make certain such configuration data is
1366 upgrading. As a very simple check search for patterns like
1367 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1368 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1369 the cf option UseCompressedIPv6Addresses.
1372 The default kernel entropy-processing algorithm is now
1373 Fortuna, replacing Yarrow.
1375 Assuming you have 'device random' in your kernel config
1376 file, the configurations allow a kernel option to override
1377 this default. You may choose *ONE* of:
1379 options RANDOM_YARROW # Legacy /dev/random algorithm.
1380 options RANDOM_DUMMY # Blocking-only driver.
1382 If you have neither, you get Fortuna. For most people,
1383 read no further, Fortuna will give a /dev/random that works
1384 like it always used to, and the difference will be irrelevant.
1386 If you remove 'device random', you get *NO* kernel-processed
1387 entropy at all. This may be acceptable to folks building
1388 embedded systems, but has complications. Carry on reading,
1389 and it is assumed you know what you need.
1391 *PLEASE* read random(4) and random(9) if you are in the
1392 habit of tweaking kernel configs, and/or if you are a member
1393 of the embedded community, wanting specific and not-usual
1394 behaviour from your security subsystems.
1396 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1397 random', you will NOT have a functioning /dev/random, and
1398 many cryptographic features will not work, including SSH.
1399 You may also find strange behaviour from the random(3) set
1400 of library functions, in particular sranddev(3), srandomdev(3)
1401 and arc4random(3). The reason for this is that the KERN_ARND
1402 sysctl only returns entropy if it thinks it has some to
1403 share, and with RANDOM_DUMMY or no 'device random' this
1407 An additional fix for the issue described in the 20150614 sendmail
1408 entry below has been committed in revision 284717.
1411 FreeBSD's old make (fmake) has been removed from the system. It is
1412 available as the devel/fmake port or via pkg install fmake.
1415 The fix for the issue described in the 20150614 sendmail entry
1416 below has been committed in revision 284436. The work
1417 around described in that entry is no longer needed unless the
1418 default setting is overridden by a confDH_PARAMETERS configuration
1419 setting of '5' or pointing to a 512 bit DH parameter file.
1422 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1423 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1424 and devel/kyua to version 0.20+ and adjust any calling code to work
1425 with Kyuafile and kyua.
1428 The import of openssl to address the FreeBSD-SA-15:10.openssl
1429 security advisory includes a change which rejects handshakes
1430 with DH parameters below 768 bits. sendmail releases prior
1431 to 8.15.2 (not yet released), defaulted to a 512 bit
1432 DH parameter setting for client connections. To work around
1433 this interoperability, sendmail can be configured to use a
1434 2048 bit DH parameter by:
1436 1. Edit /etc/mail/`hostname`.mc
1437 2. If a setting for confDH_PARAMETERS does not exist or
1438 exists and is set to a string beginning with '5',
1439 replace it with '2'.
1440 3. If a setting for confDH_PARAMETERS exists and is set to
1441 a file path, create a new file with:
1442 openssl dhparam -out /path/to/file 2048
1443 4. Rebuild the .cf file:
1444 cd /etc/mail/; make; make install
1445 5. Restart sendmail:
1446 cd /etc/mail/; make restart
1448 A sendmail patch is coming, at which time this file will be
1452 Generation of legacy formatted entries have been disabled by default
1453 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1454 entries were converted to use the new format by default when the new,
1455 machine independent format have been added and supported since FreeBSD
1458 Please see the pwd_mkdb(8) manual page for further details.
1461 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1462 20141231 entry below for information about prerequisites and upgrading,
1463 if you are not already using 3.5.0 or higher.
1466 TI platform code switched to using vendor DTS files and this update
1467 may break existing systems running on Beaglebone, Beaglebone Black,
1470 - dtb files should be regenerated/reinstalled. Filenames are the
1471 same but content is different now
1472 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1473 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1474 addressing scheme is now pin 25 on /dev/gpioc3.
1475 - Pandaboard: /etc/ttys should be updated, serial console device is
1476 now /dev/ttyu2, not /dev/ttyu0
1479 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1480 If you need the GNU extension from groff soelim(1), install groff
1481 from package: pkg install groff, or via ports: textproc/groff.
1484 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1485 defined in symlink(7); previously symlinks were silently ignored.
1488 The const qualifier has been removed from iconv(3) to comply with
1489 POSIX. The ports tree is aware of this from r384038 onwards.
1492 Libraries specified by LIBADD in Makefiles must have a corresponding
1493 DPADD_<lib> variable to ensure correct dependencies. This is now
1494 enforced in src.libnames.mk.
1497 From legacy ata(4) driver was removed support for SATA controllers
1498 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1499 Kernel modules ataahci and ataadaptec were removed completely,
1500 replaced by ahci and mvs modules respectively.
1503 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1504 the 20141231 entry below for information about prerequisites and
1505 upgrading, if you are not already using 3.5.0 or higher.
1508 The 32-bit PowerPC kernel has been changed to a position-independent
1509 executable. This can only be booted with a version of loader(8)
1510 newer than January 31, 2015, so make sure to update both world and
1511 kernel before rebooting.
1514 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1515 but before r278950, the RNG was not seeded properly. Immediately
1516 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1517 ssh keys or openssl keys) that were generated w/ a kernel from that
1518 range. This does not affect programs that directly used /dev/random
1519 or /dev/urandom. All userland uses of arc4random(3) are affected.
1522 The autofs(4) ABI was changed in order to restore binary compatibility
1523 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1524 with the new kernel.
1527 The powerpc64 kernel has been changed to a position-independent
1528 executable. This can only be booted with a new version of loader(8),
1529 so make sure to update both world and kernel before rebooting.
1532 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1533 only release, no new features have been added. Please see the 20141231
1534 entry below for information about prerequisites and upgrading, if you
1535 are not already using 3.5.0.
1538 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1539 taken from the ELF Tool Chain project rather than GNU binutils. They
1540 should be drop-in replacements, with the addition of arm64 support.
1541 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1542 binutils tools, if necessary. See 20150805 for updated information.
1545 The default Unbound configuration now enables remote control
1546 using a local socket. Users who have already enabled the
1547 local_unbound service should regenerate their configuration
1548 by running "service local_unbound setup" as root.
1551 The GNU texinfo and GNU info pages have been removed.
1552 To be able to view GNU info pages please install texinfo from ports.
1555 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1557 As of this release, a prerequisite for building clang, llvm and lldb is
1558 a C++11 capable compiler and C++11 standard library. This means that to
1559 be able to successfully build the cross-tools stage of buildworld, with
1560 clang as the bootstrap compiler, your system compiler or cross compiler
1561 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1562 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1565 On any standard FreeBSD 10.x or 11.x installation, where clang and
1566 libc++ are on by default (that is, on x86 or arm), this should work out
1569 On 9.x installations where clang is enabled by default, e.g. on x86 and
1570 powerpc, libc++ will not be enabled by default, so libc++ should be
1571 built (with clang) and installed first. If both clang and libc++ are
1572 missing, build clang first, then use it to build libc++.
1574 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1575 the instructions for 9.x above.
1577 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1578 default, and do not build clang.
1580 Many embedded systems are resource constrained, and will not be able to
1581 build clang in a reasonable time, or in some cases at all. In those
1582 cases, cross building bootable systems on amd64 is a workaround.
1584 This new version of clang introduces a number of new warnings, of which
1585 the following are most likely to appear:
1589 This warns in two cases, for both C and C++:
1590 * When the code is trying to take the absolute value of an unsigned
1591 quantity, which is effectively a no-op, and almost never what was
1592 intended. The code should be fixed, if at all possible. If you are
1593 sure that the unsigned quantity can be safely cast to signed, without
1594 loss of information or undefined behavior, you can add an explicit
1595 cast, or disable the warning.
1597 * When the code is trying to take an absolute value, but the called
1598 abs() variant is for the wrong type, which can lead to truncation.
1599 If you want to disable the warning instead of fixing the code, please
1600 make sure that truncation will not occur, or it might lead to unwanted
1603 -Wtautological-undefined-compare and
1604 -Wundefined-bool-conversion
1606 These warn when C++ code is trying to compare 'this' against NULL, while
1607 'this' should never be NULL in well-defined C++ code. However, there is
1608 some legacy (pre C++11) code out there, which actively abuses this
1609 feature, which was less strictly defined in previous C++ versions.
1611 Squid and openjdk do this, for example. The warning can be turned off
1612 for C++98 and earlier, but compiling the code in C++11 mode might result
1613 in unexpected behavior; for example, the parts of the program that are
1614 unreachable could be optimized away.
1617 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1618 kernel sources have been removed. The .h files remain, since some
1619 utilities include them. This will need to be fixed later.
1620 If "mount -t oldnfs ..." is attempted, it will fail.
1621 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1622 the utilities will report errors.
1625 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1626 directories to top level SUBDIR variable when their parent
1627 directory is included in LOCAL_DIRS. Users with build systems with
1628 such hierarchies and without SUBDIR entries in the parent
1629 directory Makefiles should add them or add the directories to
1633 faith(4) and faithd(8) have been removed from the base system. Faith
1634 has been obsolete for a very long time.
1637 vt(4), the new console driver, is enabled by default. It brings
1638 support for Unicode and double-width characters, as well as
1639 support for UEFI and integration with the KMS kernel video
1642 You may need to update your console settings in /etc/rc.conf,
1643 most probably the keymap. During boot, /etc/rc.d/syscons will
1644 indicate what you need to do.
1646 vt(4) still has issues and lacks some features compared to
1647 syscons(4). See the wiki for up-to-date information:
1648 https://wiki.freebsd.org/Newcons
1650 If you want to keep using syscons(4), you can do so by adding
1651 the following line to /boot/loader.conf:
1655 pjdfstest has been integrated into kyua as an opt-in test suite.
1656 Please see share/doc/pjdfstest/README for more details on how to
1660 gperf has been removed from the base system for architectures
1661 that use clang. Ports that require gperf will obtain it from the
1665 pjdfstest has been moved from tools/regression/pjdfstest to
1669 At svn r271982, The default linux compat kernel ABI has been adjusted
1670 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1671 update. If you wish to continue using the linux-f10 compat ports,
1672 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1673 encouraged to update their linux-compat packages to linux-c6 during
1674 their next update cycle.
1677 The ofwfb driver, used to provide a graphics console on PowerPC when
1678 using vt(4), no longer allows mmap() of all physical memory. This
1679 will prevent Xorg on PowerPC with some ATI graphics cards from
1680 initializing properly unless x11-servers/xorg-server is updated to
1684 The xdev targets have been converted to using TARGET and
1685 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1688 The default unbound configuration has been modified to address
1689 issues with reverse lookups on networks that use private
1690 address ranges. If you use the local_unbound service, run
1691 "service local_unbound setup" as root to regenerate your
1692 configuration, then "service local_unbound reload" to load the
1696 The GNU texinfo and GNU info pages are not built and installed
1697 anymore, WITH_INFO knob has been added to allow to built and install
1699 UPDATE: see 20150102 entry on texinfo's removal
1702 The GNU readline library is now an INTERNALLIB - that is, it is
1703 statically linked into consumers (GDB and variants) in the base
1704 system, and the shared library is no longer installed. The
1705 devel/readline port is available for third party software that
1709 The Itanium architecture (ia64) has been removed from the list of
1710 known architectures. This is the first step in the removal of the
1714 Commit r268115 has added NFSv4.1 server support, merged from
1715 projects/nfsv4.1-server. Since this includes changes to the
1716 internal interfaces between the NFS related modules, a full
1717 build of the kernel and modules will be necessary.
1718 __FreeBSD_version has been bumped.
1721 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1722 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1723 which differs from the behaviour controlled by this knob.)
1726 Maximal length of the serial number in CTL was increased from 16 to
1727 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1728 and ctld, need to be rebuilt to work with a new kernel.
1731 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1732 1 respectively to match the upstream numbers. They were out of
1733 sync because, when they were originally added to FreeBSD, the
1734 upstream versions were not respected. These libraries are private
1735 and not yet built by default, so renumbering them should be a
1736 non-issue. However, unclean source trees will yield broken test
1737 programs once the operator executes "make delete-old-libs" after a
1738 "make installworld".
1740 Additionally, the atf-sh binary was made private by moving it into
1741 /usr/libexec/. Already-built shell test programs will keep the
1742 path to the old binary so they will break after "make delete-old"
1745 If you are using WITH_TESTS=yes (not the default), wipe the object
1746 tree and rebuild from scratch to prevent spurious test failures.
1747 This is only needed once: the misnumbered libraries and misplaced
1748 binaries have been added to OptionalObsoleteFiles.inc so they will
1749 be removed during a clean upgrade.
1752 Clang and llvm have been upgraded to 3.4.1 release.
1755 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1756 be removed to avoid issues in the future (and has been added to
1760 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1761 past, it affected all builds that used the bsd.*.mk files. The old
1762 behavior was a bug, but people may have relied upon it. To get this
1763 behavior back, you can .include /etc/src.conf from /etc/make.conf
1764 (which is still global and isn't changed). This also changes the
1765 behavior of incremental builds inside the tree of individual
1766 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1767 Although this has survived make universe and some upgrade scenarios,
1768 other upgrade scenarios may have broken. At least one form of
1769 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1770 as well... In cases where MAKESYSPATH isn't working with this
1771 setting, you'll need to set it to the full path to your tree.
1773 One side effect of all this cleaning up is that bsd.compiler.mk
1774 is no longer implicitly included by bsd.own.mk. If you wish to
1775 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1779 The lindev device has been removed since /dev/full has been made a
1780 standard device. __FreeBSD_version has been bumped.
1783 The knob WITHOUT_VI was added to the base system, which controls
1784 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1785 in order to reorder files share/termcap and didn't build ex(1) as a
1786 build tool, so building/installing with WITH_VI is highly advised for
1787 build hosts for older releases.
1789 This issue has been fixed in stable/9 and stable/10 in r277022 and
1790 r276991, respectively.
1793 The YES_HESIOD knob has been removed. It has been obsolete for
1794 a decade. Please move to using WITH_HESIOD instead or your builds
1795 will silently lack HESIOD.
1798 The uart(4) driver has been changed with respect to its handling
1799 of the low-level console. Previously the uart(4) driver prevented
1800 any process from changing the baudrate or the CLOCAL and HUPCL
1801 control flags. By removing the restrictions, operators can make
1802 changes to the serial console port without having to reboot.
1803 However, when getty(8) is started on the serial device that is
1804 associated with the low-level console, a misconfigured terminal
1805 line in /etc/ttys will now have a real impact.
1806 Before upgrading the kernel, make sure that /etc/ttys has the
1807 serial console device configured as 3wire without baudrate to
1808 preserve the previous behaviour. E.g:
1809 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1812 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1813 to improve performance. To re-enable it, if needed, run rpcbind
1814 with command line option -W.
1817 Switched back to the GPL dtc compiler due to updates in the upstream
1818 dts files not being supported by the BSDL dtc compiler. You will need
1819 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1820 may result while building dtb files during a kernel build if you fail
1821 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1824 Clang and llvm have been upgraded to 3.4 release.
1827 The nve(4) driver has been removed. Please use the nfe(4) driver
1828 for NVIDIA nForce MCP Ethernet adapters instead.
1831 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1832 This could cause certain C++ applications using shared libraries built
1833 against the previous version of libc++ to crash. The incompatibility
1834 has now been fixed, but any C++ applications or shared libraries built
1835 between r261283 and r261801 should be recompiled.
1838 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1839 capability mode support. Please note that enabling the feature in
1840 kernel is still highly recommended.
1843 OpenSSH is now built with sandbox support, and will use sandbox as
1844 the default privilege separation method. This requires Capsicum
1845 capability mode support in kernel.
1848 The libelf and libdwarf libraries have been updated to newer
1849 versions from upstream. Shared library version numbers for
1850 these two libraries were bumped. Any ports or binaries
1851 requiring these two libraries should be recompiled.
1852 __FreeBSD_version is bumped to 1100006.
1855 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1856 instead of providing an explicit one, this would prevent such
1857 Makefile from providing its own Kyuafile in the future during
1858 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1859 intervention is needed to clean an objdir if you use NO_CLEAN:
1860 # find /usr/obj -name Kyuafile | xargs rm -f
1863 The behavior of gss_pseudo_random() for the krb5 mechanism
1864 has changed, for applications requesting a longer random string
1865 than produced by the underlying enctype's pseudo-random() function.
1866 In particular, the random string produced from a session key of
1867 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1868 be different at the 17th octet and later, after this change.
1869 The counter used in the PRF+ construction is now encoded as a
1870 big-endian integer in accordance with RFC 4402.
1871 __FreeBSD_version is bumped to 1100004.
1874 The WITHOUT_ATF build knob has been removed and its functionality
1875 has been subsumed into the more generic WITHOUT_TESTS. If you were
1876 using the former to disable the build of the ATF libraries, you
1877 should change your settings to use the latter.
1880 The default version of mtree is nmtree which is obtained from
1881 NetBSD. The output is generally the same, but may vary
1882 slightly. If you found you need identical output adding
1883 "-F freebsd9" to the command line should do the trick. For the
1884 time being, the old mtree is available as fmtree.
1887 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1888 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1889 1.1.4_8 and verify bsdyml not linked in, before running "make
1891 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1893 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1896 The stable/10 branch has been created in subversion from head
1903 Avoid using make -j when upgrading. While generally safe, there are
1904 sometimes problems using -j to upgrade. If your upgrade fails with
1905 -j, please try again without -j. From time to time in the past there
1906 have been problems using -j with buildworld and/or installworld. This
1907 is especially true when upgrading between "distant" versions (eg one
1908 that cross a major release boundary or several minor releases, or when
1909 several months have passed on the -current branch).
1911 Sometimes, obscure build problems are the result of environment
1912 poisoning. This can happen because the make utility reads its
1913 environment when searching for values for global variables. To run
1914 your build attempts in an "environmental clean room", prefix all make
1915 commands with 'env -i '. See the env(1) manual page for more details.
1917 When upgrading from one major version to another it is generally best to
1918 upgrade to the latest code in the currently installed branch first, then
1919 do an upgrade to the new branch. This is the best-tested upgrade path,
1920 and has the highest probability of being successful. Please try this
1921 approach if you encounter problems with a major version upgrade. Since
1922 the stable 4.x branch point, one has generally been able to upgrade from
1923 anywhere in the most recent stable branch to head / current (or even the
1924 last couple of stable branches). See the top of this file when there's
1927 When upgrading a live system, having a root shell around before
1928 installing anything can help undo problems. Not having a root shell
1929 around can lead to problems if pam has changed too much from your
1930 starting point to allow continued authentication after the upgrade.
1932 This file should be read as a log of events. When a later event changes
1933 information of a prior event, the prior event should not be deleted.
1934 Instead, a pointer to the entry with the new information should be
1935 placed in the old entry. Readers of this file should also sanity check
1936 older entries before relying on them blindly. Authors of new entries
1937 should write them with this in mind.
1941 When upgrading the boot ZFS pool to a new version, always follow
1944 1.) recompile and reinstall the ZFS boot loader and boot block
1945 (this is part of "make buildworld" and "make installworld")
1947 2.) update the ZFS boot block on your boot drive
1949 The following example updates the ZFS boot block on the first
1950 partition (freebsd-boot) of a GPT partitioned drive ada0:
1951 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1953 Non-boot pools do not need these updates.
1957 If you are updating from a prior version of FreeBSD (even one just
1958 a few days old), you should follow this procedure. It is the most
1959 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1961 make kernel-toolchain
1962 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1963 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1965 To test a kernel once
1966 ---------------------
1967 If you just want to boot a kernel once (because you are not sure
1968 if it works, or if you want to boot a known bad kernel to provide
1969 debugging information) run
1970 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1971 nextboot -k testkernel
1973 To rebuild everything and install it on the current system.
1974 -----------------------------------------------------------
1975 # Note: sometimes if you are running current you gotta do more than
1976 # is listed here if you are upgrading from a really old current.
1978 <make sure you have good level 0 dumps>
1980 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1981 make installkernel KERNCONF=YOUR_KERNEL_HERE
1983 <reboot in single user> [3]
1990 To cross-install current onto a separate partition
1991 --------------------------------------------------
1992 # In this approach we use a separate partition to hold
1993 # current's root, 'usr', and 'var' directories. A partition
1994 # holding "/", "/usr" and "/var" should be about 2GB in
1997 <make sure you have good level 0 dumps>
2000 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2001 <maybe newfs current's root partition>
2002 <mount current's root partition on directory ${CURRENT_ROOT}>
2003 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2004 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2005 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2006 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2007 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2008 <reboot into current>
2009 <do a "native" rebuild/install as described in the previous section>
2010 <maybe install compatibility libraries from ports/misc/compat*>
2014 To upgrade in-place from stable to current
2015 ----------------------------------------------
2016 <make sure you have good level 0 dumps>
2018 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2019 make installkernel KERNCONF=YOUR_KERNEL_HERE
2021 <reboot in single user> [3]
2028 Make sure that you've read the UPDATING file to understand the
2029 tweaks to various things you need. At this point in the life
2030 cycle of current, things change often and you are on your own
2031 to cope. The defaults can also change, so please read ALL of
2032 the UPDATING entries.
2034 Also, if you are tracking -current, you must be subscribed to
2035 freebsd-current@freebsd.org. Make sure that before you update
2036 your sources that you have read and understood all the recent
2037 messages there. If in doubt, please track -stable which has
2038 much fewer pitfalls.
2040 [1] If you have third party modules, such as vmware, you
2041 should disable them at this point so they don't crash your
2044 [3] From the bootblocks, boot -s, and then do
2049 adjkerntz -i # if CMOS is wall time
2050 Also, when doing a major release upgrade, it is required that
2051 you boot into single user mode to do the installworld.
2053 [4] Note: This step is non-optional. Failure to do this step
2054 can result in a significant reduction in the functionality of the
2055 system. Attempting to do it by hand is not recommended and those
2056 that pursue this avenue should read this file carefully, as well
2057 as the archives of freebsd-current and freebsd-hackers mailing lists
2058 for potential gotchas. The -U option is also useful to consider.
2059 See mergemaster(8) for more information.
2061 [5] Usually this step is a no-op. However, from time to time
2062 you may need to do this if you get unknown user in the following
2063 step. It never hurts to do it all the time. You may need to
2064 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2065 install) after the buildworld before this step if you last updated
2066 from current before 20130425 or from -stable before 20130430.
2068 [6] This only deletes old files and directories. Old libraries
2069 can be deleted by "make delete-old-libs", but you have to make
2070 sure that no program is using those libraries anymore.
2072 [8] The new kernel must be able to run existing binaries used by
2073 an installworld. When upgrading across major versions, the new
2074 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2075 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2076 binaries). Failure to do so may leave you with a system that is
2077 hard to boot to recover. A GENERIC kernel will include suitable
2078 compatibility options to run binaries from older branches.
2080 Make sure that you merge any new devices from GENERIC since the
2081 last time you updated your kernel config file.
2083 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2084 "?=" instead of the "=" assignment operator, so that buildworld can
2085 override the CPUTYPE if it needs to.
2087 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2088 not on the command line, or in /etc/make.conf. buildworld will
2089 warn if it is improperly defined.
2092 This file contains a list, in reverse chronological order, of major
2093 breakages in tracking -current. It is not guaranteed to be a complete
2094 list of such breakages, and only contains entries since September 23, 2011.
2095 If you need to see UPDATING entries from before that date, you will need
2096 to fetch an UPDATING file from an older FreeBSD release.
2098 Copyright information:
2100 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2102 Redistribution, publication, translation and use, with or without
2103 modification, in full or in part, in any form or format of this
2104 document are permitted without further permission from the author.
2106 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2107 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2108 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2109 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2110 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2111 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2112 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2113 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2114 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2115 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2116 POSSIBILITY OF SUCH DAMAGE.
2118 Contact Warner Losh if you have any questions about your use of