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 20200805 p8 FreeBSD-EN-20:16.vmx
20 FreeBSD-SA-20:21.usb_net
21 FreeBSD-SA-20:22.unbound
24 Fix vmx driver packet loss and degraded performance. [EN-20:16.vmx]
26 Fix memory corruption in USB network device drivers. [SA-20:21.usb_net]
28 Fix multiple vulnerabilities in sqlite3. [SA-20:22.sqlite]
30 Fix sendmsg(2) privilege escalation. [SA-20:23.sendmsg]
32 20200708 p7 FreeBSD-EN-20:13.bhyve
33 FreeBSD-EN-20:14.linuxkpi
35 FreeBSD-SA-20:19.unbound
38 Fix host crash in bhyve with PCI device passthrough. [EN-20:13.bhyve]
40 Fix kernel panic in LinuxKPI subsystem. [EN-20:14.linuxpki]
42 Fix kernel panic in mps(4) driver. [EN-20:15.mps]
44 Fix multiple vulnerabilities in unbound. [SA-20:19.unbound]
46 Fix IPv6 socket option race condition and use after free. [SA-20:20.ipv6]
48 20200609 p6 FreeBSD-EN-20:11.ena
49 FreeBSD-EN-20:12.iflib
52 Fix stability issues in ena(4) driver. [EN-20:11.ena]
54 Fix iflib watchdog timeout resetting idle queues. [EN-20:12.iflib]
56 Fix USB HID descriptor parsing error. [SA-20:17.usb]
58 20200512 p5 FreeBSD-EN-20:08.tzdata
60 FreeBSD-EN-20:10.build
61 FreeBSD-SA-20:12.libalias
62 FreeBSD-SA-20:13.libalias
63 FreeBSD-SA-20:15.cryptodev
64 FreeBSD-SA-20:16.cryptodev
66 Import tzdata 2020a. [EN-20:08.tzdata]
68 Fix igb interfaces failing to switch to inactive state [EN-20:09.igb]
70 Fix incorrect build host Clang version detection [EN-20:10.build]
72 Fix insufficient packet length validation in libalias [SA-20:12.libalias]
74 Fix memory disclosure vulnerability in libalias [SA-20:13.libalias]
76 Fix use after free in cryptodev module [SA-20:15.cryptodev]
78 Fix insufficient cryptodev MAC key length check [SA-20:16.cryptodev]
80 20200421 p4 FreeBSD-EN-20:07.quotad
82 FreeBSD-SA-20:11.openssl
84 Fix regression in rpc.rquotad with certain NFS servers [EN-20:07.quotad]
86 Fix ipfw invalid mbuf handling [SA-20:10.ipfw]
88 Fix OpenSSL remote denial of service vulnerability [SA-20:11.openssl]
90 20200319 p3 FreeBSD-EN-20:03.sshd
91 FreeBSD-EN-20:05.mlx5en
94 FreeBSD-SA-20:05.if_oce_ioctl
95 FreeBSD-SA-20:06.if_ixl_ioctl
96 FreeBSD-SA-20:07.epair
100 Fix misleading log messages upon successful sshd login [EN-20:03.sshd]
102 Fix packet forwarding performance in mlx5en(4) driver [EN-20:05.mlx5en]
104 Fix incorrect checksum calculations with IPv6 extension headers [EN-20:06.ipv6]
106 Fix TCP IPv6 SYN cache kernel information disclosure [SA-20:04.tcp]
108 Fix insufficient oce(4) ioctl(2) privilege checking [SA-20:05.if_oce_ioctl]
110 Fix insufficient ixl(4) ioctl(2) privilege checking [SA-20:06.if_ixl_ioctl]
112 Fix incorrect user-controlled pointer use in epair [SA-20:07.epair]
114 Fix kernel memory disclosure with nested jails [SA-20:08.jail]
116 Fix multiple denial of service in ntpd [SA-20:09.ntp]
118 20200128 p2 FreeBSD-EN-20:01.ssp
119 FreeBSD-SA-20:01.libfetch
120 FreeBSD-SA-20:03.thrmisc
122 Fix imprecise ordering of SSP canary initialization [EN-20:01.ssp]
124 Fix libfetch buffer overflow [SA-20:01.libfetch]
126 Fix kernel stack data disclosure [SA-20:03.thrmisc]
128 20191112 p1 FreeBSD-EN-19:19.loader
129 FreeBSD-SA-19:25.mcepsc
131 Fix UEFI Loader Memory Fragmentation [EN-19:19.loader]
133 Fix Machine Check Exception on Page Size Change [SA-19:25.mcepsc]
139 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
140 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
141 been removed from mount_fusefs(8). You can safely remove them from
142 your scripts, because they had no effect.
144 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
145 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
146 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
147 sysctls have been removed. If you felt the need to set any of them to
148 a non-default value, please tell asomers@FreeBSD.org why.
151 The fuse(4) module has been renamed to fusefs(4) for consistency with
152 other filesystems. You should update any kld_load="fuse" entries in
153 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
154 "options FUSE" enties in kernel config files.
157 Default permissions on the /var/account/acct file (and copies of it
158 rotated by periodic daily scripts) are changed from 0644 to 0640
159 because the file contains sensitive information that should not be
160 world-readable. If the /var/account directory must be created by
161 rc.d/accounting, the mode used is now 0750. Admins who use the
162 accounting feature are encouraged to change the mode of an existing
163 /var/account directory to 0750 or 0700.
166 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
167 been upgraded to 8.0.1. Please see the 20141231 entry below for
168 information about prerequisites and upgrading, if you are not already
169 using clang 3.5.0 or higher.
172 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
173 functionality needed for the RETPOLINE option should work properly
174 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
177 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
178 8.0.0. Please see the 20141231 entry below for information about
179 prerequisites and upgrading, if you are not already using clang 3.5.0
183 The RETPOLINE option produces non-functional ifunc-using binaries
184 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
185 Once Clang 8 is merged it may be enabled again.
188 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
189 7.0.1. Please see the 20141231 entry below for information about
190 prerequisites and upgrading, if you are not already using clang 3.5.0
194 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
195 compiled into your custom kernel, add 'device xz' statement to the
199 Iflib is no longer unconditionally compiled into the kernel. Drivers
200 using iflib and statically compiled into the kernel, now require
201 the 'device iflib' config option. For the same drivers loaded as
202 modules on kernels not having 'device iflib', the iflib.ko module
203 is loaded automatically.
206 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
207 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
208 servers that have vfs.nfsd.nfs_privport set will only allow mounts
209 from clients using a reserved port#. Since both the FreeBSD and Linux
210 NFSv4 clients use reserved port#s by default, this should not affect
214 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
215 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
216 it produces broken binaries when ifuncs are in use. Users needing
217 GNU ld should install the binutils port or package.
220 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
221 has been converted to a port (misc/ctm) and will be removed from
222 FreeBSD-13. A depreciation warning will be printed to stderr by
223 the ctm command, but the functionality will remain in base for all
227 The stable/12 branch has been created in subversion from head
231 Ports for the DRM modules have been simplified. Now, amd64 users should
232 just install the drm-kmod port. All others should install
235 Graphics hardware that's newer than about 2010 usually works with
236 drm-kmod. For hardware older than 2013, however, some users will need
237 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
238 than 2008 usually only works in drm-legacy-kmod. The graphics team can
239 only commit to hardware made since 2013 due to the complexity of the
240 market and difficulty to test all the older cards effectively. If you
241 have hardware supported by drm-kmod, you are strongly encouraged to use
242 that as you will get better support.
244 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
245 elsewhere, the drm and drm2 modules will be eliminated from the src base
246 soon (with a limited exception for arm). Please update to the package asap
247 and report any issues to x11@freebsd.org.
249 Generally, anybody using the drm*-kmod packages should add
250 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
251 cross-threading surprises, especially with automatic driver
252 loading from X11 startup. These will become the defaults in 13-current
256 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
257 custom kernel and module loading configuration files must be updated
258 accordingly. Moreover, interfaces previous presented as ixlvN to the
259 system are now exposed as iavfN and network configuration files must
260 be adjusted as necessary.
263 OpenSSL has been updated to version 1.1.1. This update included
264 additional various API changes througout the base system. It is
265 important to rebuild third-party software after upgrading. The value
266 of __FreeBSD_version has been bumped accordingly.
269 The legacy DRM modules and drivers have now been added to the loader's
270 module blacklist, in favor of loading them with kld_list in rc.conf(5).
271 The module blacklist may be overridden with the loader.conf(5)
272 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
276 The cam(4) based nda(4) driver will be used over nvd(4) by default on
277 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
278 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
279 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
283 Reproducible build mode is now on by default, in preparation for
284 FreeBSD 12.0. This eliminates build metadata such as the user,
285 host, and time from the kernel (and uname), unless the working tree
286 corresponds to a modified checkout from a version control system.
287 The previous behavior can be obtained by setting the /etc/src.conf
288 knob WITHOUT_REPRODUCIBLE_BUILD.
291 The Yarrow CSPRNG has been removed from the kernel as it has not been
292 supported by its designers since at least 2003. Fortuna has been the
293 default since FreeBSD-11.
296 devctl freeze/thaw have gone into the tree, the rc scripts have been
297 updated to use them and devmatch has been changed. You should update
298 kernel, userland and rc scripts all at the same time.
301 The default interpreter has been switched from 4th to Lua.
302 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
303 interpreter. If you have custom FORTH code you will need to set
304 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
305 src.conf for the build. This will create default hard links between
306 loader and loader_4th instead of loader and loader_lua, the new default.
307 If you are using UEFI it will create the proper hard link to loader.efi.
309 bhyve uses userboot.so. It remains 4th-only until some issues are solved
310 regarding coexisting with multiple versions of FreeBSD are resolved.
313 ls(1) now respects the COLORTERM environment variable used in other
314 systems and software to indicate that a colored terminal is both
315 supported and desired. If ls(1) is suddenly emitting colors, they may
316 be disabled again by either removing the unwanted COLORTERM from your
317 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
318 may not be observed in a future release.
321 The default pager for most commands has been changed to "less". To
322 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
326 The jedec_ts(4) driver has been removed. A superset of its functionality
327 is available in the jedec_dimm(4) driver, and the manpage for that
328 driver includes migration instructions. If you have "device jedec_ts"
329 in your kernel configuration file, it must be removed.
332 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
333 This should have no effect if the kernel is booted via BIOS/legacy boot.
334 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
335 has a buggy firmware that prevents a successful boot due to use of
339 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
340 support has been removed from the tree. These ports were
341 obsolete and/or known to be broken for many years.
344 loader.efi has been augmented to participate more fully in the
345 UEFI boot manager protocol. loader.efi will now look at the
346 BootXXXX environment variable to determine if a specific kernel
347 or root partition was specified. XXXX is derived from BootCurrent.
348 efibootmgr(8) manages these standard UEFI variables.
351 zfsloader's functionality has now been folded into loader.
352 zfsloader is no longer necessary once you've updated your
353 boot blocks. For a transition period, we will install a
354 hardlink for zfsloader to loader to allow a smooth transition
355 until the boot blocks can be updated (hard link because old
356 zfs boot blocks don't understand symlinks).
359 ARM64 now have efifb support, if you want to have serial console
360 on your arm64 board when an screen is connected and the bootloader
361 setup a frambuffer for us to use, just add :
365 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
366 an screen connected as the firmware will setup a framebuffer are that
367 u-boot will expose as an EFI framebuffer.
370 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
371 or take steps to update /etc/passwd before doing installworld on
372 existing systems. Do not skip the "mergemaster -Fp" step before
373 installworld, as described in the update procedures near the bottom
374 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
375 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
376 the ntp config file contain options that change file/dir locations.
377 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
378 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
379 taking steps to ensure that all required files/dirs are accessible
383 Big endian arm support has been removed.
386 The static environment setup in kernel configs is no longer mutually
387 exclusive with the loader(8) environment by default. In order to
388 restore the previous default behavior of disabling the loader(8)
389 environment if a static environment is present, you must specify
390 loader_env.disabled=1 in the static environment.
393 The ABI of syscalls used by management tools like sockstat and
394 netstat has been broken to allow 32-bit binaries to work on
395 64-bit kernels without modification. These programs will need
396 to match the kernel in order to function. External programs may
397 require minor modifications to accommodate a change of type in
398 structures from pointers to 64-bit virtual addresses.
401 On i386 and amd64 atomics are now inlined. Out of tree modules using
402 atomics will need to be rebuilt.
405 The '%I' format in the kern.corefile sysctl limits the number of
406 core files that a process can generate to the number stored in the
407 debug.ncores sysctl. The '%I' format is replaced by the single digit
408 index. Previously, if all indexes were taken the kernel would overwrite
409 only a core file with the highest index in a filename.
410 Currently the system will create a new core file if there is a free
411 index or if all slots are taken it will overwrite the oldest one.
414 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
415 6.0.1. Please see the 20141231 entry below for information about
416 prerequisites and upgrading, if you are not already using clang 3.5.0
420 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
421 needed to be changed to work with it. This change was made with r335763
422 and requires a mergemaster / etcupdate / etc to update the installed file.
425 r334930 changed the interface between the NFS modules, so they all
426 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
429 As of r334391 lld is the default amd64 system linker; it is installed
430 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
434 The kernel / userland interface for devinfo changed, so you'll
435 need a new kernel and userland as a pair for it to work (rebuilding
436 lib/libdevinfo is all that's required). devinfo and devmatch will
437 not work, but everything else will when there's a mismatch.
440 The on-disk format for hwpmc callchain records has changed to include
441 threadid corresponding to a given record. This changes the field offsets
442 and thus requires that libpmcstat be rebuilt before using a kernel
446 The vxge(4) driver has been removed. This driver was introduced into
447 HEAD one week before the Exar left the Ethernet market and is not
448 known to be used. If you have device vxge in your kernel config file
452 The amd64 kernel now requires a ld that supports ifunc to produce a
453 working kernel, either lld or a newer binutils. lld is built by default
454 on amd64, and the 'buildkernel' target uses it automatically. However,
455 it is not the default linker, so building the kernel the traditional
456 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
457 binutils port/package). lld will soon be default, and this requirement
460 NOTE: As of r334391 lld is the default system linker on amd64, and no
461 workaround is necessary.
464 The nxge(4) driver has been removed. This driver was for PCI-X 10g
465 cards made by s2io/Neterion. The company was aquired by Exar and
466 no longer sells or supports Ethernet products. If you have device
467 nxge in your kernel config file it must be removed.
470 The tz database (tzdb) has been updated to 2018e. This version more
471 correctly models time stamps in time zones with negative DST such as
472 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
473 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
474 time zone abbreviations and the tm_isdst flag.
477 The ixgb(4) driver has been removed. This driver was for an early and
478 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
479 quickly shifted to the long lived ixgbe family. If you have device
480 ixgb in your kernel config file it must be removed.
483 The lmc(4) driver has been removed. This was a WAN interface
484 card that was already reportedly rare in 2003, and had an ambiguous
485 license. If you have device lmc in your kernel config file it must
489 Support for Arcnet networks has been removed. If you have device
490 arcnet or device cm in your kernel config file they must be
494 Support for FDDI networks has been removed. If you have device
495 fddi or device fpa in your kernel config file they must be
499 In addition to supporting RFC 3164 formatted messages, the
500 syslogd(8) service is now capable of parsing RFC 5424 formatted
501 log messages. The main benefit of using RFC 5424 is that clients
502 may now send log messages with timestamps containing year numbers,
503 microseconds and time zone offsets.
505 Similarly, the syslog(3) C library function has been altered to
506 send RFC 5424 formatted messages to the local system logging
507 daemon. On systems using syslogd(8), this change should have no
508 negative impact, as long as syslogd(8) and the C library are
509 updated at the same time. On systems using a different system
510 logging daemon, it may be necessary to make configuration
511 adjustments, depending on the software used.
513 When using syslog-ng, add the 'syslog-protocol' flag to local
514 input sources to enable parsing of RFC 5424 formatted messages:
517 unix-dgram("/var/run/log" flags(syslog-protocol));
520 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
521 of the 'imuxsock' module to let messages be processed by the
522 regular RFC 3164/5424 parsing pipeline:
524 module(load="imuxsock" SysSock.UseSpecialParser="off")
526 Do note that these changes only affect communication between local
527 applications and syslogd(8). The format that syslogd(8) uses to
528 store messages on disk or forward messages to other systems
529 remains unchanged. syslogd(8) still uses RFC 3164 for these
530 purposes. Options to customize this behaviour will be added in the
531 future. Utilities that process log files stored in /var/log are
532 thus expected to continue to function as before.
534 __FreeBSD_version has been incremented to 1200061 to denote this
538 Support for token ring networks has been removed. If you
539 have "device token" in your kernel config you should remove
540 it. No device drivers supported token ring.
543 makefs was modified to be able to tag ISO9660 El Torito boot catalog
544 entries as EFI instead of overloading the i386 tag as done previously.
545 The amd64 mkisoimages.sh script used to build amd64 ISO images for
546 release was updated to use this. This may mean that makefs must be
547 updated before "make cdrom" can be run in the release directory. This
548 should be as simple as:
550 $ cd $SRCDIR/usr.sbin/makefs
551 $ make depend all install
554 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
555 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
556 Co-existance for the transition period will come shortly. Booting is a
557 complex environment and test coverage for Lua-enabled loaders has been
558 thin, so it would be prudent to assume it might not work and make
559 provisions for backup boot methods.
562 devmatch functionality has been turned on in devd. It will automatically
563 load drivers for unattached devices. This may cause unexpected drivers to
564 be loaded. Please report any problems to current@ and imp@freebsd.org.
567 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
568 6.0.0. Please see the 20141231 entry below for information about
569 prerequisites and upgrading, if you are not already using clang 3.5.0
573 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
574 This means it is used to link the kernel and userland libraries and
575 executables, but is not yet installed as /usr/bin/ld by default.
577 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
578 WITHOUT_LLD_BOOTSTRAP=yes
581 On i386, pmtimer has been removed. Its functionality has been folded
582 into apm. It was a no-op on ACPI in current for a while now (but was still
583 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
584 from kernel config files.
587 The use of RSS hash from the network card aka flowid has been
588 disabled by default for lagg(4) as it's currently incompatible with
589 the lacp and loadbalance protocols.
591 This can be re-enabled by setting the following in loader.conf:
592 net.link.lagg.default_use_flowid="1"
595 The SW_WATCHDOG option is no longer necessary to enable the
596 hardclock-based software watchdog if no hardware watchdog is
597 configured. As before, SW_WATCHDOG will cause the software
598 watchdog to be enabled even if a hardware watchdog is configured.
601 r326887 fixes the issue described in the 20171214 UPDATING entry.
602 r326888 flips the switch back to building GELI support always.
605 r362593 broke ZFS + GELI support for reasons unknown. However,
606 it also broke ZFS support generally, so GELI has been turned off
607 by default as the lesser evil in r326857. If you boot off ZFS and/or
608 GELI, it might not be a good time to update.
611 PowerPC users must update loader(8) by rebuilding world before
612 installing a new kernel, as the protocol connecting them has
613 changed. Without the update, loader metadata will not be passed
614 successfully to the kernel and users will have to enter their
615 root partition at the kernel mountroot prompt to continue booting.
616 Newer versions of loader can boot old kernels without issue.
619 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
620 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
621 to WITH/OUT_LOADER_GELI.
624 The naive and non-compliant support of posix_fallocate(2) in ZFS
625 has been removed as of r325320. The system call now returns EINVAL
626 when used on a ZFS file. Although the new behavior complies with the
627 standard, some consumers are not prepared to cope with it.
628 One known victim is lld prior to r325420.
631 Building in a FreeBSD src checkout will automatically create object
632 directories now rather than store files in the current directory if
633 'make obj' was not ran. Calling 'make obj' is no longer necessary.
634 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
635 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
639 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
640 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
641 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
642 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
643 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
644 The UNIFIED_OBJDIR option is a transitional feature that will be
645 removed for 12.0 release; please migrate to the new format for any
646 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
647 than hardcoding paths.
650 The native-xtools target no longer installs the files by default to the
651 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
652 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
655 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
656 options are changing from controlling the build if defined / undefined
657 to controlling the build with explicit 'yes' or 'no' values. They will
658 shift to WITH/WITHOUT options to match other options in the system.
661 libstand has turned into a private library for sys/boot use only.
662 It is no longer supported as a public interface outside of sys/boot.
665 The arm port has split armv6 into armv6 and armv7. armv7 is now
666 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
667 and are running a kernel from before r324363, you will need to add
668 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
671 When building multiple kernels using KERNCONF, non-existent KERNCONF
672 files will produce an error and buildkernel will fail. Previously
673 missing KERNCONF files silently failed giving no indication as to
674 why, only to subsequently discover during installkernel that the
675 desired kernel was never built in the first place.
678 The default serial number format for CTL LUNs has changed. This will
679 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
680 or iSCSI clients care about their LUNs' serial numbers. Users who
681 require serial number stability should hardcode serial numbers in
685 For 32-bit arm compiled for hard-float support, soft-floating point
686 binaries now always get their shared libraries from
687 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
688 /usr/libsoft also existed). Only users with a hard-float ld.so, but
689 soft-float everything else should be affected.
692 The geli password typed at boot is now hidden. To restore the previous
693 behavior, see geli(8) for configuration options.
696 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
697 sysctl values. Minor nit, but requires a rebuild of both world/kernel
701 "make check" behavior (made in ^/head@r295380) has been changed to
702 execute from a limited sandbox, as opposed to executing from
706 - The "beforecheck" and "aftercheck" targets are now specified.
707 - ${CHECKDIR} (added in commit noted above) has been removed.
708 - Legacy behavior can be enabled by setting
709 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
711 If the limited sandbox mode is enabled, "make check" will execute
712 "make distribution", then install, execute the tests, and clean up the
713 sandbox if successful.
715 The "make distribution" and "make install" targets are typically run as
716 root to set appropriate permissions and ownership at installation time.
717 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
718 environment if executing "make check" with limited sandbox mode using
719 an unprivileged user.
722 Since the switch to GPT disk labels, fsck for UFS/FFS has been
723 unable to automatically find alternate superblocks. As of r322297,
724 the information needed to find alternate superblocks has been
725 moved to the end of the area reserved for the boot block.
726 Filesystems created with a newfs of this vintage or later
727 will create the recovery information. If you have a filesystem
728 created prior to this change and wish to have a recovery block
729 created for your filesystem, you can do so by running fsck in
730 foreground mode (i.e., do not use the -p or -y options). As it
731 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
732 to which you should answer yes.
735 As of r321665, an NFSv4 server configuration that services
736 Kerberos mounts or clients that do not support the uid/gid in
737 owner/owner_group string capability, must explicitly enable
738 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
739 machine's /etc/rc.conf file.
742 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
743 Please see the 20141231 entry below for information about prerequisites
744 and upgrading, if you are not already using clang 3.5.0 or higher.
747 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
748 r-commands (rlogin, rsh, etc.) to be built with the base system.
751 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
752 a very major ABI incompatible change, so users of FreeBSD/powerpc must
753 be careful when performing source upgrades. It is best to run
754 'make installworld' from an alternate root system, either a live
755 CD/memory stick, or a temporary root partition. Additionally, all ports
756 must be recompiled. powerpc64 is largely unaffected, except in the case
757 of 32-bit compatibility. All 32-bit binaries will be affected.
760 Forward compatibility for the "ino64" project have been committed. This
761 will allow most new binaries to run on older kernels in a limited
762 fashion. This prevents many of the common foot-shooting actions in the
763 upgrade as well as the limited ability to roll back the kernel across
764 the ino64 upgrade. Complicated use cases may not work properly, though
765 enough simpler ones work to allow recovery in most situations.
768 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
769 if you require the GPL compiler.
772 The internal ABI used for communication between the NFS kernel modules
773 was changed by r320085, so __FreeBSD_version was bumped to
774 ensure all the NFS related modules are updated together.
777 The ABI of struct event was changed by extending the data
778 member to 64bit and adding ext fields. For upgrade, same
779 precautions as for the entry 20170523 "ino64" must be
783 The GNU roff toolchain has been removed from base. To render manpages
784 which are not supported by mandoc(1), man(1) can fallback on GNU roff
785 from ports (and recommends to install it).
786 To render roff(7) documents, consider using GNU roff from ports or the
787 heirloom doctools roff toolchain from ports via pkg install groff or
788 via pkg install heirloom-doctools.
791 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
792 smaller runtime footprint builds. This is useful for embedded systems
793 which only require one chipset support.
795 If you load it as a module, make sure this is in /boot/loader.conf:
799 This will load the HAL, all chip/RF backends and if_ath_pci.
800 If you have if_ath_pci in /boot/loader.conf, ensure it is after
801 if_ath or it will not load any HAL chipset support.
803 If you want to selectively load things (eg on ye cheape ARM/MIPS
804 platforms where RAM is at a premium) you should:
807 * load the chip modules in question
808 * load ath_rate, ath_dfs
810 * load if_ath_pci and/or if_ath_ahb depending upon your particular
811 bus bind type - this is where probe/attach is done.
813 For further comments/feedback, poke adrian@ .
816 The "ino64" 64-bit inode project has been committed, which extends
817 a number of types to 64 bits. Upgrading in place requires care and
818 adherence to the documented upgrade procedure.
820 If using a custom kernel configuration ensure that the
821 COMPAT_FREEBSD11 option is included (as during the upgrade the
822 system will be running the ino64 kernel with the existing world).
824 For the safest in-place upgrade begin by removing previous build
825 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
826 full procedure documented below under the heading "To rebuild
827 everything and install it on the current system." Specifically,
828 a reboot is required after installing the new kernel before
832 The NATM framework including the en(4), fatm(4), hatm(4), and
833 patm(4) devices has been removed. Consumers should plan a
834 migration before the end-of-life date for FreeBSD 11.
837 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
838 diff has not been implemented, if those are needed a newer version of
839 GNU diff is available via the diffutils package under the gdiff name.
842 As of r316810 for ipfilter, keep frags is no longer assumed when
843 keep state is specified in a rule. r316810 aligns ipfilter with
844 documentation in man pages separating keep frags from keep state.
845 This allows keep state to be specified without forcing keep frags
846 and allows keep frags to be specified independently of keep state.
847 To maintain previous behaviour, also specify keep frags with
848 keep state (as documented in ipf.conf.5).
851 arm64 builds now use the base system LLD 4.0.0 linker by default,
852 instead of requiring that the aarch64-binutils port or package be
853 installed. To continue using aarch64-binutils, set
854 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
857 The UDP optimization in entry 20160818 that added the sysctl
858 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
859 packets will no longer be treated as L3 broadcast packets.
862 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
863 use any explicitly assigned loopback address available in the jail
864 instead of using the first assigned address of the jail.
867 The ctl.ko module no longer implements the iSCSI target frontend:
868 cfiscsi.ko does instead.
870 If building cfiscsi.ko as a kernel module, the module can be loaded
871 via one of the following methods:
872 - `cfiscsi_load="YES"` in loader.conf(5).
873 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
874 - ctladm(8)/ctld(8), when compiled with iSCSI support
875 (`WITH_ISCSI=yes` in src.conf(5))
877 Please see cfiscsi(4) for more details.
880 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
881 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
882 same source (previously, the dependency of mmcsd.ko on mmc.ko was
883 missing, but mmcsd.ko now will refuse to load if it is incompatible
887 The syntax of ipfw(8) named states was changed to avoid ambiguity.
888 If you have used named states in the firewall rules, you need to modify
889 them after installworld and before rebooting. Now named states must
890 be prefixed with colon.
893 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
894 removed as the userland we provide cannot use them. The KMS version
895 (sys/dev/drm2) supports the same hardware.
898 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
899 Please see the 20141231 entry below for information about prerequisites
900 and upgrading, if you are not already using clang 3.5.0 or higher.
903 The code that provides support for ZFS .zfs/ directory functionality
904 has been reimplemented. It's not possible now to create a snapshot
905 by mkdir under .zfs/snapshot/. That should be the only user visible
909 EISA bus support has been removed. The WITH_EISA option is no longer
913 MCA bus support has been removed.
916 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
917 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
920 The EM_MULTIQUEUE kernel configuration option is deprecated now that
921 the em(4) driver conforms to iflib specifications.
924 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
925 IFLIB. If you have a custom kernel configuration that excludes em(4)
926 but you use igb(4), you need to re-add em(4) to your custom configuration.
929 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
930 Please see the 20141231 entry below for information about prerequisites
931 and upgrading, if you are not already using clang 3.5.0 or higher.
934 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
935 Please see the 20141231 entry below for information about prerequisites
936 and upgrading, if you are not already using clang 3.5.0 or higher.
939 The layout of the pmap structure has changed for powerpc to put the pmap
940 statistics at the front for all CPU variations. libkvm(3) and all tools
941 that link against it need to be recompiled.
944 isl(4) and cyapa(4) drivers now require a new driver,
945 chromebook_platform(4), to work properly on Chromebook-class hardware.
946 On other types of hardware the drivers may need to be configured using
947 device hints. Please see the corresponding manual pages for details.
950 The urtwn(4) driver was merged into rtwn(4) and now consists of
951 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
953 Also, firmware for RTL8188CE was renamed due to possible name
954 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
957 GNU rcs has been removed from base. It is available as packages:
958 - rcs: Latest GPLv3 GNU rcs version.
959 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
963 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
964 modules now requires that the kernel configuration contain the
965 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
968 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
969 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
972 Relocatable object files with the extension of .So have been renamed
973 to use an extension of .pico instead. The purpose of this change is
974 to avoid a name clash with shared libraries on case-insensitive file
975 systems. On those file systems, foo.So is the same file as foo.so.
978 GNU rcs has been turned off by default. It can (temporarily) be built
979 again by adding WITH_RCS knob in src.conf.
980 Otherwise, GNU rcs is available from packages:
981 - rcs: Latest GPLv3 GNU rcs version.
982 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
985 The backup_uses_rcs functionality has been removed from rc.subr.
988 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
989 two separate components, QUEUE_MACRO_DEBUG_TRACE and
990 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
991 QUEUE_MACRO_DEBUG behavior.
994 r304787 changed some ioctl interfaces between the iSCSI userspace
995 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
996 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1000 The UDP receive code has been updated to only treat incoming UDP
1001 packets that were addressed to an L2 broadcast address as L3
1002 broadcast packets. It is not expected that this will affect any
1003 standards-conforming UDP application. The new behaviour can be
1004 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1008 Remove the openbsd_poll system call.
1009 __FreeBSD_version has been bumped because of this.
1012 The stable/11 branch has been created from head@r302406.
1015 The libc stub for the pipe(2) system call has been replaced with
1016 a wrapper that calls the pipe2(2) system call and the pipe(2)
1017 system call is now only implemented by the kernels that include
1018 "options COMPAT_FREEBSD10" in their config file (this is the
1019 default). Users should ensure that this option is enabled in
1020 their kernel or upgrade userspace to r302092 before upgrading their
1024 CAM will now strip leading spaces from SCSI disks' serial numbers.
1025 This will affect users who create UFS filesystems on SCSI disks using
1026 those disk's diskid device nodes. For example, if /etc/fstab
1027 previously contained a line like
1028 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1029 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1030 transforms like gmirror may also be affected. ZFS users should
1034 The bitstring(3) API has been updated with new functionality and
1035 improved performance. But it is binary-incompatible with the old API.
1036 Objects built with the new headers may not be linked against objects
1037 built with the old headers.
1040 The brk and sbrk functions have been removed from libc on arm64.
1041 Binutils from ports has been updated to not link to these
1042 functions and should be updated to the latest version before
1043 installing a new libc.
1046 The armv6 port now defaults to hard float ABI. Limited support
1047 for running both hardfloat and soft float on the same system
1048 is available using the libraries installed with -DWITH_LIBSOFT.
1049 This has only been tested as an upgrade path for installworld
1050 and packages may fail or need manual intervention to run. New
1051 packages will be needed.
1053 To update an existing self-hosted armv6hf system, you must add
1054 TARGET_ARCH=armv6 on the make command line for both the build
1055 and the install steps.
1058 Kernel modules compiled outside of a kernel build now default to
1059 installing to /boot/modules instead of /boot/kernel. Many kernel
1060 modules built this way (such as those in ports) already overrode
1061 KMODDIR explicitly to install into /boot/modules. However,
1062 manually building and installing a module from /sys/modules will
1063 now install to /boot/modules instead of /boot/kernel.
1066 The CAM I/O scheduler has been committed to the kernel. There should be
1067 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1068 list of known rogues that claim support for this but actually corrupt
1069 data is believed to be complete, be on the lookout for data
1070 corruption. The known rogue list is believed to be complete:
1072 o Crucial MX100, M550 drives with MU01 firmware.
1073 o Micron M510 and M550 drives with MU01 firmware.
1074 o Micron M500 prior to MU07 firmware
1075 o Samsung 830, 840, and 850 all firmwares
1076 o FCCT M500 all firmwares
1078 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1079 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1080 updated firmware. Black listed drives will work correctly because these
1081 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1082 this list is the same as found in Linux, it's believed there are no
1083 other rogues in the market place. All other models from the above
1086 To be safe, if you are at all concerned, you can quirk each of your
1087 drives to prevent NCQ from being sent by setting:
1088 kern.cam.ada.X.quirks="0x2"
1089 in loader.conf. If the drive requires the 4k sector quirk, set the
1090 quirks entry to 0x3.
1093 The FAST_DEPEND build option has been removed and its functionality is
1094 now the one true way. The old mkdep(1) style of 'make depend' has
1095 been removed. See 20160311 for further details.
1098 Resource range types have grown from unsigned long to uintmax_t. All
1099 drivers, and anything using libdevinfo, need to be recompiled.
1102 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1103 builds. It no longer runs mkdep(1) during 'make depend', and the
1104 'make depend' stage can safely be skipped now as it is auto ran
1105 when building 'make all' and will generate all SRCS and DPSRCS before
1106 building anything else. Dependencies are gathered at compile time with
1107 -MF flags kept in separate .depend files per object file. Users should
1108 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1109 stale .depend files.
1112 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1113 kernel modules. Therefore, if you load any kernel modules at boot time,
1114 please install the boot loaders after you install the kernel, but before
1118 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1119 make installkernel KERNCONF=YOUR_KERNEL_HERE
1120 make -C sys/boot install
1121 <reboot in single user>
1123 Then follow the usual steps, described in the General Notes section,
1127 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1128 see the 20141231 entry below for information about prerequisites and
1129 upgrading, if you are not already using clang 3.5.0 or higher.
1132 The AIO subsystem is now a standard part of the kernel. The
1133 VFS_AIO kernel option and aio.ko kernel module have been removed.
1134 Due to stability concerns, asynchronous I/O requests are only
1135 permitted on sockets and raw disks by default. To enable
1136 asynchronous I/O requests on all file types, set the
1137 vfs.aio.enable_unsafe sysctl to a non-zero value.
1140 The ELF object manipulation tool objcopy is now provided by the
1141 ELF Tool Chain project rather than by GNU binutils. It should be a
1142 drop-in replacement, with the addition of arm64 support. The
1143 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1144 to obtain the GNU version if necessary.
1147 Building ZFS pools on top of zvols is prohibited by default. That
1148 feature has never worked safely; it's always been prone to deadlocks.
1149 Using a zvol as the backing store for a VM guest's virtual disk will
1150 still work, even if the guest is using ZFS. Legacy behavior can be
1151 restored by setting vfs.zfs.vol.recursive=1.
1154 The NONE and HPN patches has been removed from OpenSSH. They are
1155 still available in the security/openssh-portable port.
1158 With the addition of ypldap(8), a new _ypldap user is now required
1159 during installworld. "mergemaster -p" can be used to add the user
1160 prior to installworld, as documented in the handbook.
1163 The tftp loader (pxeboot) now uses the option root-path directive. As a
1164 consequence it no longer looks for a pxeboot.4th file on the tftp
1165 server. Instead it uses the regular /boot infrastructure as with the
1169 The code to start recording plug and play data into the modules has
1170 been committed. While the old tools will properly build a new kernel,
1171 a number of warnings about "unknown metadata record 4" will be produced
1172 for an older kldxref. To avoid such warnings, make sure to rebuild
1173 the kernel toolchain (or world). Make sure that you have r292078 or
1174 later when trying to build 292077 or later before rebuilding.
1177 Debug data files are now built by default with 'make buildworld' and
1178 installed with 'make installworld'. This facilitates debugging but
1179 requires more disk space both during the build and for the installed
1180 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1184 r291527 changed the internal interface between the nfsd.ko and
1185 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1186 __FreeBSD_version has been bumped because of this.
1189 Add support for unicode collation strings leads to a change of
1190 order of files listed by ls(1) for example. To get back to the old
1191 behaviour, set LC_COLLATE environment variable to "C".
1193 Databases administrators will need to reindex their databases given
1194 collation results will be different.
1196 Due to a bug in install(1) it is recommended to remove the ancient
1197 locales before running make installworld.
1199 rm -rf /usr/share/locale/*
1202 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1203 libcrypto.so.7 or libssl.so.7 must be recompiled.
1206 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1207 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1208 should be replaced with isp_2400 and isp_2500 modules respectively.
1211 The build previously allowed using 'make -n' to not recurse into
1212 sub-directories while showing what commands would be executed, and
1213 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1214 and 'make -N' will not.
1217 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1218 and etcupdate will now use this file. A custom sendmail.cf is now
1219 updated via this mechanism rather than via installworld. If you had
1220 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1221 want to remove the exclusion or change it to "always install".
1222 /etc/mail/sendmail.cf is now managed the same way regardless of
1223 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1224 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1227 Compatibility shims for legacy ATA device names have been removed.
1228 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1229 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1230 environment variables, /dev/ad* and /dev/ar* symbolic links.
1233 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1234 Please see the 20141231 entry below for information about prerequisites
1235 and upgrading, if you are not already using clang 3.5.0 or higher.
1238 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1239 and renamed from .symbols to .debug. This reduces the size requirements
1240 on the boot partition or file system and provides consistency with
1241 userland debug files.
1243 When using the supported kernel installation method the
1244 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1245 as is done with /boot/kernel.
1247 Developers wishing to maintain the historical behavior of installing
1248 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1251 The wireless drivers had undergone changes that remove the 'parent
1252 interface' from the ifconfig -l output. The rc.d network scripts
1253 used to check presence of a parent interface in the list, so old
1254 scripts would fail to start wireless networking. Thus, etcupdate(3)
1255 or mergemaster(8) run is required after kernel update, to update your
1256 rc.d scripts in /etc.
1259 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1260 These configurations are now automatically interpreted as
1261 'scrub fragment reassemble'.
1264 Kernel-loadable modules for the random(4) device are back. To use
1265 them, the kernel must have
1268 options RANDOM_LOADABLE
1270 kldload(8) can then be used to load random_fortuna.ko
1271 or random_yarrow.ko. Please note that due to the indirect
1272 function calls that the loadable modules need to provide,
1273 the build-in variants will be slightly more efficient.
1275 The random(4) kernel option RANDOM_DUMMY has been retired due to
1276 unpopularity. It was not all that useful anyway.
1279 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1280 Control over building the ELF Tool Chain tools is now provided by
1281 the WITHOUT_TOOLCHAIN knob.
1284 The polarity of Pulse Per Second (PPS) capture events with the
1285 uart(4) driver has been corrected. Prior to this change the PPS
1286 "assert" event corresponded to the trailing edge of a positive PPS
1287 pulse and the "clear" event was the leading edge of the next pulse.
1289 As the width of a PPS pulse in a typical GPS receiver is on the
1290 order of 1 millisecond, most users will not notice any significant
1291 difference with this change.
1293 Anyone who has compensated for the historical polarity reversal by
1294 configuring a negative offset equal to the pulse width will need to
1295 remove that workaround.
1298 The default group assigned to /dev/dri entries has been changed
1299 from 'wheel' to 'video' with the id of '44'. If you want to have
1300 access to the dri devices please add yourself to the video group
1303 # pw groupmod video -m $USER
1306 The menu.rc and loader.rc files will now be replaced during
1307 upgrades. Please migrate local changes to menu.rc.local and
1308 loader.rc.local instead.
1311 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1312 strings and strip have been removed. The src.conf(5) knob
1313 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1316 As ZFS requires more kernel stack pages than is the default on some
1317 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1318 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1320 Please consider using 'options KSTACK_PAGES=X' where X is greater
1321 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1324 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1325 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1326 default, i.e., they will not contain "::". For example, instead
1327 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1328 to have a more specific match, such as different map entries for
1329 IPv6:0:0 vs IPv6:0. This change requires that configuration
1330 data (including maps, files, classes, custom ruleset, etc.) must
1331 use the same format, so make certain such configuration data is
1332 upgrading. As a very simple check search for patterns like
1333 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1334 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1335 the cf option UseCompressedIPv6Addresses.
1338 The default kernel entropy-processing algorithm is now
1339 Fortuna, replacing Yarrow.
1341 Assuming you have 'device random' in your kernel config
1342 file, the configurations allow a kernel option to override
1343 this default. You may choose *ONE* of:
1345 options RANDOM_YARROW # Legacy /dev/random algorithm.
1346 options RANDOM_DUMMY # Blocking-only driver.
1348 If you have neither, you get Fortuna. For most people,
1349 read no further, Fortuna will give a /dev/random that works
1350 like it always used to, and the difference will be irrelevant.
1352 If you remove 'device random', you get *NO* kernel-processed
1353 entropy at all. This may be acceptable to folks building
1354 embedded systems, but has complications. Carry on reading,
1355 and it is assumed you know what you need.
1357 *PLEASE* read random(4) and random(9) if you are in the
1358 habit of tweaking kernel configs, and/or if you are a member
1359 of the embedded community, wanting specific and not-usual
1360 behaviour from your security subsystems.
1362 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1363 random', you will NOT have a functioning /dev/random, and
1364 many cryptographic features will not work, including SSH.
1365 You may also find strange behaviour from the random(3) set
1366 of library functions, in particular sranddev(3), srandomdev(3)
1367 and arc4random(3). The reason for this is that the KERN_ARND
1368 sysctl only returns entropy if it thinks it has some to
1369 share, and with RANDOM_DUMMY or no 'device random' this
1373 An additional fix for the issue described in the 20150614 sendmail
1374 entry below has been committed in revision 284717.
1377 FreeBSD's old make (fmake) has been removed from the system. It is
1378 available as the devel/fmake port or via pkg install fmake.
1381 The fix for the issue described in the 20150614 sendmail entry
1382 below has been committed in revision 284436. The work
1383 around described in that entry is no longer needed unless the
1384 default setting is overridden by a confDH_PARAMETERS configuration
1385 setting of '5' or pointing to a 512 bit DH parameter file.
1388 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1389 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1390 and devel/kyua to version 0.20+ and adjust any calling code to work
1391 with Kyuafile and kyua.
1394 The import of openssl to address the FreeBSD-SA-15:10.openssl
1395 security advisory includes a change which rejects handshakes
1396 with DH parameters below 768 bits. sendmail releases prior
1397 to 8.15.2 (not yet released), defaulted to a 512 bit
1398 DH parameter setting for client connections. To work around
1399 this interoperability, sendmail can be configured to use a
1400 2048 bit DH parameter by:
1402 1. Edit /etc/mail/`hostname`.mc
1403 2. If a setting for confDH_PARAMETERS does not exist or
1404 exists and is set to a string beginning with '5',
1405 replace it with '2'.
1406 3. If a setting for confDH_PARAMETERS exists and is set to
1407 a file path, create a new file with:
1408 openssl dhparam -out /path/to/file 2048
1409 4. Rebuild the .cf file:
1410 cd /etc/mail/; make; make install
1411 5. Restart sendmail:
1412 cd /etc/mail/; make restart
1414 A sendmail patch is coming, at which time this file will be
1418 Generation of legacy formatted entries have been disabled by default
1419 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1420 entries were converted to use the new format by default when the new,
1421 machine independent format have been added and supported since FreeBSD
1424 Please see the pwd_mkdb(8) manual page for further details.
1427 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1428 20141231 entry below for information about prerequisites and upgrading,
1429 if you are not already using 3.5.0 or higher.
1432 TI platform code switched to using vendor DTS files and this update
1433 may break existing systems running on Beaglebone, Beaglebone Black,
1436 - dtb files should be regenerated/reinstalled. Filenames are the
1437 same but content is different now
1438 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1439 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1440 addressing scheme is now pin 25 on /dev/gpioc3.
1441 - Pandaboard: /etc/ttys should be updated, serial console device is
1442 now /dev/ttyu2, not /dev/ttyu0
1445 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1446 If you need the GNU extension from groff soelim(1), install groff
1447 from package: pkg install groff, or via ports: textproc/groff.
1450 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1451 defined in symlink(7); previously symlinks were silently ignored.
1454 The const qualifier has been removed from iconv(3) to comply with
1455 POSIX. The ports tree is aware of this from r384038 onwards.
1458 Libraries specified by LIBADD in Makefiles must have a corresponding
1459 DPADD_<lib> variable to ensure correct dependencies. This is now
1460 enforced in src.libnames.mk.
1463 From legacy ata(4) driver was removed support for SATA controllers
1464 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1465 Kernel modules ataahci and ataadaptec were removed completely,
1466 replaced by ahci and mvs modules respectively.
1469 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1470 the 20141231 entry below for information about prerequisites and
1471 upgrading, if you are not already using 3.5.0 or higher.
1474 The 32-bit PowerPC kernel has been changed to a position-independent
1475 executable. This can only be booted with a version of loader(8)
1476 newer than January 31, 2015, so make sure to update both world and
1477 kernel before rebooting.
1480 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1481 but before r278950, the RNG was not seeded properly. Immediately
1482 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1483 ssh keys or openssl keys) that were generated w/ a kernel from that
1484 range. This does not affect programs that directly used /dev/random
1485 or /dev/urandom. All userland uses of arc4random(3) are affected.
1488 The autofs(4) ABI was changed in order to restore binary compatibility
1489 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1490 with the new kernel.
1493 The powerpc64 kernel has been changed to a position-independent
1494 executable. This can only be booted with a new version of loader(8),
1495 so make sure to update both world and kernel before rebooting.
1498 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1499 only release, no new features have been added. Please see the 20141231
1500 entry below for information about prerequisites and upgrading, if you
1501 are not already using 3.5.0.
1504 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1505 taken from the ELF Tool Chain project rather than GNU binutils. They
1506 should be drop-in replacements, with the addition of arm64 support.
1507 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1508 binutils tools, if necessary. See 20150805 for updated information.
1511 The default Unbound configuration now enables remote control
1512 using a local socket. Users who have already enabled the
1513 local_unbound service should regenerate their configuration
1514 by running "service local_unbound setup" as root.
1517 The GNU texinfo and GNU info pages have been removed.
1518 To be able to view GNU info pages please install texinfo from ports.
1521 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1523 As of this release, a prerequisite for building clang, llvm and lldb is
1524 a C++11 capable compiler and C++11 standard library. This means that to
1525 be able to successfully build the cross-tools stage of buildworld, with
1526 clang as the bootstrap compiler, your system compiler or cross compiler
1527 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1528 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1531 On any standard FreeBSD 10.x or 11.x installation, where clang and
1532 libc++ are on by default (that is, on x86 or arm), this should work out
1535 On 9.x installations where clang is enabled by default, e.g. on x86 and
1536 powerpc, libc++ will not be enabled by default, so libc++ should be
1537 built (with clang) and installed first. If both clang and libc++ are
1538 missing, build clang first, then use it to build libc++.
1540 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1541 the instructions for 9.x above.
1543 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1544 default, and do not build clang.
1546 Many embedded systems are resource constrained, and will not be able to
1547 build clang in a reasonable time, or in some cases at all. In those
1548 cases, cross building bootable systems on amd64 is a workaround.
1550 This new version of clang introduces a number of new warnings, of which
1551 the following are most likely to appear:
1555 This warns in two cases, for both C and C++:
1556 * When the code is trying to take the absolute value of an unsigned
1557 quantity, which is effectively a no-op, and almost never what was
1558 intended. The code should be fixed, if at all possible. If you are
1559 sure that the unsigned quantity can be safely cast to signed, without
1560 loss of information or undefined behavior, you can add an explicit
1561 cast, or disable the warning.
1563 * When the code is trying to take an absolute value, but the called
1564 abs() variant is for the wrong type, which can lead to truncation.
1565 If you want to disable the warning instead of fixing the code, please
1566 make sure that truncation will not occur, or it might lead to unwanted
1569 -Wtautological-undefined-compare and
1570 -Wundefined-bool-conversion
1572 These warn when C++ code is trying to compare 'this' against NULL, while
1573 'this' should never be NULL in well-defined C++ code. However, there is
1574 some legacy (pre C++11) code out there, which actively abuses this
1575 feature, which was less strictly defined in previous C++ versions.
1577 Squid and openjdk do this, for example. The warning can be turned off
1578 for C++98 and earlier, but compiling the code in C++11 mode might result
1579 in unexpected behavior; for example, the parts of the program that are
1580 unreachable could be optimized away.
1583 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1584 kernel sources have been removed. The .h files remain, since some
1585 utilities include them. This will need to be fixed later.
1586 If "mount -t oldnfs ..." is attempted, it will fail.
1587 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1588 the utilities will report errors.
1591 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1592 directories to top level SUBDIR variable when their parent
1593 directory is included in LOCAL_DIRS. Users with build systems with
1594 such hierarchies and without SUBDIR entries in the parent
1595 directory Makefiles should add them or add the directories to
1599 faith(4) and faithd(8) have been removed from the base system. Faith
1600 has been obsolete for a very long time.
1603 vt(4), the new console driver, is enabled by default. It brings
1604 support for Unicode and double-width characters, as well as
1605 support for UEFI and integration with the KMS kernel video
1608 You may need to update your console settings in /etc/rc.conf,
1609 most probably the keymap. During boot, /etc/rc.d/syscons will
1610 indicate what you need to do.
1612 vt(4) still has issues and lacks some features compared to
1613 syscons(4). See the wiki for up-to-date information:
1614 https://wiki.freebsd.org/Newcons
1616 If you want to keep using syscons(4), you can do so by adding
1617 the following line to /boot/loader.conf:
1621 pjdfstest has been integrated into kyua as an opt-in test suite.
1622 Please see share/doc/pjdfstest/README for more details on how to
1626 gperf has been removed from the base system for architectures
1627 that use clang. Ports that require gperf will obtain it from the
1631 pjdfstest has been moved from tools/regression/pjdfstest to
1635 At svn r271982, The default linux compat kernel ABI has been adjusted
1636 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1637 update. If you wish to continue using the linux-f10 compat ports,
1638 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1639 encouraged to update their linux-compat packages to linux-c6 during
1640 their next update cycle.
1643 The ofwfb driver, used to provide a graphics console on PowerPC when
1644 using vt(4), no longer allows mmap() of all physical memory. This
1645 will prevent Xorg on PowerPC with some ATI graphics cards from
1646 initializing properly unless x11-servers/xorg-server is updated to
1650 The xdev targets have been converted to using TARGET and
1651 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1654 The default unbound configuration has been modified to address
1655 issues with reverse lookups on networks that use private
1656 address ranges. If you use the local_unbound service, run
1657 "service local_unbound setup" as root to regenerate your
1658 configuration, then "service local_unbound reload" to load the
1662 The GNU texinfo and GNU info pages are not built and installed
1663 anymore, WITH_INFO knob has been added to allow to built and install
1665 UPDATE: see 20150102 entry on texinfo's removal
1668 The GNU readline library is now an INTERNALLIB - that is, it is
1669 statically linked into consumers (GDB and variants) in the base
1670 system, and the shared library is no longer installed. The
1671 devel/readline port is available for third party software that
1675 The Itanium architecture (ia64) has been removed from the list of
1676 known architectures. This is the first step in the removal of the
1680 Commit r268115 has added NFSv4.1 server support, merged from
1681 projects/nfsv4.1-server. Since this includes changes to the
1682 internal interfaces between the NFS related modules, a full
1683 build of the kernel and modules will be necessary.
1684 __FreeBSD_version has been bumped.
1687 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1688 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1689 which differs from the behaviour controlled by this knob.)
1692 Maximal length of the serial number in CTL was increased from 16 to
1693 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1694 and ctld, need to be rebuilt to work with a new kernel.
1697 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1698 1 respectively to match the upstream numbers. They were out of
1699 sync because, when they were originally added to FreeBSD, the
1700 upstream versions were not respected. These libraries are private
1701 and not yet built by default, so renumbering them should be a
1702 non-issue. However, unclean source trees will yield broken test
1703 programs once the operator executes "make delete-old-libs" after a
1704 "make installworld".
1706 Additionally, the atf-sh binary was made private by moving it into
1707 /usr/libexec/. Already-built shell test programs will keep the
1708 path to the old binary so they will break after "make delete-old"
1711 If you are using WITH_TESTS=yes (not the default), wipe the object
1712 tree and rebuild from scratch to prevent spurious test failures.
1713 This is only needed once: the misnumbered libraries and misplaced
1714 binaries have been added to OptionalObsoleteFiles.inc so they will
1715 be removed during a clean upgrade.
1718 Clang and llvm have been upgraded to 3.4.1 release.
1721 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1722 be removed to avoid issues in the future (and has been added to
1726 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1727 past, it affected all builds that used the bsd.*.mk files. The old
1728 behavior was a bug, but people may have relied upon it. To get this
1729 behavior back, you can .include /etc/src.conf from /etc/make.conf
1730 (which is still global and isn't changed). This also changes the
1731 behavior of incremental builds inside the tree of individual
1732 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1733 Although this has survived make universe and some upgrade scenarios,
1734 other upgrade scenarios may have broken. At least one form of
1735 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1736 as well... In cases where MAKESYSPATH isn't working with this
1737 setting, you'll need to set it to the full path to your tree.
1739 One side effect of all this cleaning up is that bsd.compiler.mk
1740 is no longer implicitly included by bsd.own.mk. If you wish to
1741 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1745 The lindev device has been removed since /dev/full has been made a
1746 standard device. __FreeBSD_version has been bumped.
1749 The knob WITHOUT_VI was added to the base system, which controls
1750 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1751 in order to reorder files share/termcap and didn't build ex(1) as a
1752 build tool, so building/installing with WITH_VI is highly advised for
1753 build hosts for older releases.
1755 This issue has been fixed in stable/9 and stable/10 in r277022 and
1756 r276991, respectively.
1759 The YES_HESIOD knob has been removed. It has been obsolete for
1760 a decade. Please move to using WITH_HESIOD instead or your builds
1761 will silently lack HESIOD.
1764 The uart(4) driver has been changed with respect to its handling
1765 of the low-level console. Previously the uart(4) driver prevented
1766 any process from changing the baudrate or the CLOCAL and HUPCL
1767 control flags. By removing the restrictions, operators can make
1768 changes to the serial console port without having to reboot.
1769 However, when getty(8) is started on the serial device that is
1770 associated with the low-level console, a misconfigured terminal
1771 line in /etc/ttys will now have a real impact.
1772 Before upgrading the kernel, make sure that /etc/ttys has the
1773 serial console device configured as 3wire without baudrate to
1774 preserve the previous behaviour. E.g:
1775 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1778 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1779 to improve performance. To re-enable it, if needed, run rpcbind
1780 with command line option -W.
1783 Switched back to the GPL dtc compiler due to updates in the upstream
1784 dts files not being supported by the BSDL dtc compiler. You will need
1785 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1786 may result while building dtb files during a kernel build if you fail
1787 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1790 Clang and llvm have been upgraded to 3.4 release.
1793 The nve(4) driver has been removed. Please use the nfe(4) driver
1794 for NVIDIA nForce MCP Ethernet adapters instead.
1797 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1798 This could cause certain C++ applications using shared libraries built
1799 against the previous version of libc++ to crash. The incompatibility
1800 has now been fixed, but any C++ applications or shared libraries built
1801 between r261283 and r261801 should be recompiled.
1804 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1805 capability mode support. Please note that enabling the feature in
1806 kernel is still highly recommended.
1809 OpenSSH is now built with sandbox support, and will use sandbox as
1810 the default privilege separation method. This requires Capsicum
1811 capability mode support in kernel.
1814 The libelf and libdwarf libraries have been updated to newer
1815 versions from upstream. Shared library version numbers for
1816 these two libraries were bumped. Any ports or binaries
1817 requiring these two libraries should be recompiled.
1818 __FreeBSD_version is bumped to 1100006.
1821 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1822 instead of providing an explicit one, this would prevent such
1823 Makefile from providing its own Kyuafile in the future during
1824 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1825 intervention is needed to clean an objdir if you use NO_CLEAN:
1826 # find /usr/obj -name Kyuafile | xargs rm -f
1829 The behavior of gss_pseudo_random() for the krb5 mechanism
1830 has changed, for applications requesting a longer random string
1831 than produced by the underlying enctype's pseudo-random() function.
1832 In particular, the random string produced from a session key of
1833 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1834 be different at the 17th octet and later, after this change.
1835 The counter used in the PRF+ construction is now encoded as a
1836 big-endian integer in accordance with RFC 4402.
1837 __FreeBSD_version is bumped to 1100004.
1840 The WITHOUT_ATF build knob has been removed and its functionality
1841 has been subsumed into the more generic WITHOUT_TESTS. If you were
1842 using the former to disable the build of the ATF libraries, you
1843 should change your settings to use the latter.
1846 The default version of mtree is nmtree which is obtained from
1847 NetBSD. The output is generally the same, but may vary
1848 slightly. If you found you need identical output adding
1849 "-F freebsd9" to the command line should do the trick. For the
1850 time being, the old mtree is available as fmtree.
1853 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1854 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1855 1.1.4_8 and verify bsdyml not linked in, before running "make
1857 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1859 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1862 The stable/10 branch has been created in subversion from head
1869 Avoid using make -j when upgrading. While generally safe, there are
1870 sometimes problems using -j to upgrade. If your upgrade fails with
1871 -j, please try again without -j. From time to time in the past there
1872 have been problems using -j with buildworld and/or installworld. This
1873 is especially true when upgrading between "distant" versions (eg one
1874 that cross a major release boundary or several minor releases, or when
1875 several months have passed on the -current branch).
1877 Sometimes, obscure build problems are the result of environment
1878 poisoning. This can happen because the make utility reads its
1879 environment when searching for values for global variables. To run
1880 your build attempts in an "environmental clean room", prefix all make
1881 commands with 'env -i '. See the env(1) manual page for more details.
1883 When upgrading from one major version to another it is generally best to
1884 upgrade to the latest code in the currently installed branch first, then
1885 do an upgrade to the new branch. This is the best-tested upgrade path,
1886 and has the highest probability of being successful. Please try this
1887 approach if you encounter problems with a major version upgrade. Since
1888 the stable 4.x branch point, one has generally been able to upgrade from
1889 anywhere in the most recent stable branch to head / current (or even the
1890 last couple of stable branches). See the top of this file when there's
1893 When upgrading a live system, having a root shell around before
1894 installing anything can help undo problems. Not having a root shell
1895 around can lead to problems if pam has changed too much from your
1896 starting point to allow continued authentication after the upgrade.
1898 This file should be read as a log of events. When a later event changes
1899 information of a prior event, the prior event should not be deleted.
1900 Instead, a pointer to the entry with the new information should be
1901 placed in the old entry. Readers of this file should also sanity check
1902 older entries before relying on them blindly. Authors of new entries
1903 should write them with this in mind.
1907 When upgrading the boot ZFS pool to a new version, always follow
1910 1.) recompile and reinstall the ZFS boot loader and boot block
1911 (this is part of "make buildworld" and "make installworld")
1913 2.) update the ZFS boot block on your boot drive
1915 The following example updates the ZFS boot block on the first
1916 partition (freebsd-boot) of a GPT partitioned drive ada0:
1917 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1919 Non-boot pools do not need these updates.
1923 If you are updating from a prior version of FreeBSD (even one just
1924 a few days old), you should follow this procedure. It is the most
1925 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1927 make kernel-toolchain
1928 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1929 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1931 To test a kernel once
1932 ---------------------
1933 If you just want to boot a kernel once (because you are not sure
1934 if it works, or if you want to boot a known bad kernel to provide
1935 debugging information) run
1936 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1937 nextboot -k testkernel
1939 To rebuild everything and install it on the current system.
1940 -----------------------------------------------------------
1941 # Note: sometimes if you are running current you gotta do more than
1942 # is listed here if you are upgrading from a really old current.
1944 <make sure you have good level 0 dumps>
1946 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1947 make installkernel KERNCONF=YOUR_KERNEL_HERE
1949 <reboot in single user> [3]
1956 To cross-install current onto a separate partition
1957 --------------------------------------------------
1958 # In this approach we use a separate partition to hold
1959 # current's root, 'usr', and 'var' directories. A partition
1960 # holding "/", "/usr" and "/var" should be about 2GB in
1963 <make sure you have good level 0 dumps>
1966 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1967 <maybe newfs current's root partition>
1968 <mount current's root partition on directory ${CURRENT_ROOT}>
1969 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1970 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1971 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1972 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1973 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1974 <reboot into current>
1975 <do a "native" rebuild/install as described in the previous section>
1976 <maybe install compatibility libraries from ports/misc/compat*>
1980 To upgrade in-place from stable to current
1981 ----------------------------------------------
1982 <make sure you have good level 0 dumps>
1984 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1985 make installkernel KERNCONF=YOUR_KERNEL_HERE
1987 <reboot in single user> [3]
1994 Make sure that you've read the UPDATING file to understand the
1995 tweaks to various things you need. At this point in the life
1996 cycle of current, things change often and you are on your own
1997 to cope. The defaults can also change, so please read ALL of
1998 the UPDATING entries.
2000 Also, if you are tracking -current, you must be subscribed to
2001 freebsd-current@freebsd.org. Make sure that before you update
2002 your sources that you have read and understood all the recent
2003 messages there. If in doubt, please track -stable which has
2004 much fewer pitfalls.
2006 [1] If you have third party modules, such as vmware, you
2007 should disable them at this point so they don't crash your
2010 [3] From the bootblocks, boot -s, and then do
2015 adjkerntz -i # if CMOS is wall time
2016 Also, when doing a major release upgrade, it is required that
2017 you boot into single user mode to do the installworld.
2019 [4] Note: This step is non-optional. Failure to do this step
2020 can result in a significant reduction in the functionality of the
2021 system. Attempting to do it by hand is not recommended and those
2022 that pursue this avenue should read this file carefully, as well
2023 as the archives of freebsd-current and freebsd-hackers mailing lists
2024 for potential gotchas. The -U option is also useful to consider.
2025 See mergemaster(8) for more information.
2027 [5] Usually this step is a no-op. However, from time to time
2028 you may need to do this if you get unknown user in the following
2029 step. It never hurts to do it all the time. You may need to
2030 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2031 install) after the buildworld before this step if you last updated
2032 from current before 20130425 or from -stable before 20130430.
2034 [6] This only deletes old files and directories. Old libraries
2035 can be deleted by "make delete-old-libs", but you have to make
2036 sure that no program is using those libraries anymore.
2038 [8] The new kernel must be able to run existing binaries used by
2039 an installworld. When upgrading across major versions, the new
2040 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2041 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2042 binaries). Failure to do so may leave you with a system that is
2043 hard to boot to recover. A GENERIC kernel will include suitable
2044 compatibility options to run binaries from older branches.
2046 Make sure that you merge any new devices from GENERIC since the
2047 last time you updated your kernel config file.
2049 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2050 "?=" instead of the "=" assignment operator, so that buildworld can
2051 override the CPUTYPE if it needs to.
2053 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2054 not on the command line, or in /etc/make.conf. buildworld will
2055 warn if it is improperly defined.
2058 This file contains a list, in reverse chronological order, of major
2059 breakages in tracking -current. It is not guaranteed to be a complete
2060 list of such breakages, and only contains entries since September 23, 2011.
2061 If you need to see UPDATING entries from before that date, you will need
2062 to fetch an UPDATING file from an older FreeBSD release.
2064 Copyright information:
2066 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2068 Redistribution, publication, translation and use, with or without
2069 modification, in full or in part, in any form or format of this
2070 document are permitted without further permission from the author.
2072 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2073 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2074 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2075 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2076 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2077 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2078 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2079 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2080 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2081 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2082 POSSIBILITY OF SUCH DAMAGE.
2084 Contact Warner Losh if you have any questions about your use of