1 Updating Information for FreeBSD stable/12 users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
20 The make.conf(5) MALLOC_PRODUCTION variable, used for disabling and
21 enabling assertions and statistics gathering in malloc(3), has been
22 migrated to a src.conf(5) WITH/WITHOUT_MALLOC_PRODUCTION option.
24 On stable branches, WITH_MALLOC_PRODUCTION is set by default, which
25 means that malloc(3) has assertions and statistics gathering disabled,
26 for improved performance.
28 For backwards compatibility, the make.conf(5) MALLOC_PRODUCTION is still
29 honored, but it is now deprecated and undocumented.
32 The resume code now notifies devd with the 'kernel' system
33 rather than the old 'kern' subsystem to be consistent with
34 other use. The old notification will be created as well, but
35 will be removed prior to FreeBSD 14.0.
38 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
39 been upgraded to 10.0.1. Please see the 20141231 entry below for
40 information about prerequisites and upgrading, if you are not already
41 using clang 3.5.0 or higher.
44 read(2) of a directory fd is now rejected by default. root may
45 re-enable it for the entire system with the
46 security.bsd.allow_read_dir sysctl(8) MIB.
48 It may be advised to setup aliases for grep to default to `-d skip` if
49 commonly non-recursively grepping a list that includes directories and
50 the potential for the resulting stderr output is not tolerable. Example
51 aliases are now installed, commented out, in /root/.cshrc.
54 Upstream DTS from Linux 5.6 was merged and they now have the SID
55 and THS (Secure ID controller and THermal Sensor) node present.
56 The DTB overlays have now been removed from the tree for the H3/H5 and
57 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
58 deal with upstream DTS. If you are using those overlays you need to
59 remove them from loader.conf and update the DTBs on the FAT partition.
62 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
63 been upgraded to 10.0.0. Please see the 20141231 entry below for
64 information about prerequisites and upgrading, if you are not already
65 using clang 3.5.0 or higher.
68 The root certificates of the Mozilla CA Certificate Store have been
69 imported into the base system and can be managed with the certctl(8)
70 utility. If you have installed the security/ca_root_nss port or package
71 with the ETCSYMLINK option (the default), be advised that there may be
72 differences between those included in the port and those included in
73 base due to differences in nss branch used as well as general update
74 frequency. Note also that certctl(8) cannot manage certs in the
75 format used by the security/ca_root_nss port.
78 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
79 been upgraded to 9.0.1. Please see the 20141231 entry below for
80 information about prerequisites and upgrading, if you are not already
81 using clang 3.5.0 or higher.
84 The nctgpio and wbwd drivers have been moved to the superio bus.
85 If you have one of these drivers in a kernel configuration, then
86 you should add device superio to it. If you use one of these drivers
87 as a module and you compile a custom set of modules, then you should
88 add superio to the set.
91 The tap(4) driver has been folded into tun(4), and the module has been
92 renamed to tuntap. You should update any kld_list="if_tap" or
93 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
94 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
95 module instead, and "device tap" or "device tun" entries in kernel
96 config files to select the tuntap device instead.
99 ntpd no longer by default locks its pages in memory, allowing them
100 to be paged out by the kernel. Use rlimit memlock to restore
101 historic BSD behaviour. For example, add "rlimit memlock 32"
102 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
105 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
106 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
107 been removed from mount_fusefs(8). You can safely remove them from
108 your scripts, because they had no effect.
110 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
111 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
112 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
113 sysctls have been removed. If you felt the need to set any of them to
114 a non-default value, please tell asomers@FreeBSD.org why.
117 The fuse(4) module has been renamed to fusefs(4) for consistency with
118 other filesystems. You should update any kld_load="fuse" entries in
119 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
120 "options FUSE" enties in kernel config files.
123 Default permissions on the /var/account/acct file (and copies of it
124 rotated by periodic daily scripts) are changed from 0644 to 0640
125 because the file contains sensitive information that should not be
126 world-readable. If the /var/account directory must be created by
127 rc.d/accounting, the mode used is now 0750. Admins who use the
128 accounting feature are encouraged to change the mode of an existing
129 /var/account directory to 0750 or 0700.
132 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
133 been upgraded to 8.0.1. Please see the 20141231 entry below for
134 information about prerequisites and upgrading, if you are not already
135 using clang 3.5.0 or higher.
138 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
139 functionality needed for the RETPOLINE option should work properly
140 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
143 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
144 8.0.0. Please see the 20141231 entry below for information about
145 prerequisites and upgrading, if you are not already using clang 3.5.0
149 The RETPOLINE option produces non-functional ifunc-using binaries
150 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
151 Once Clang 8 is merged it may be enabled again.
154 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
155 7.0.1. Please see the 20141231 entry below for information about
156 prerequisites and upgrading, if you are not already using clang 3.5.0
160 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
161 compiled into your custom kernel, add 'device xz' statement to the
165 Iflib is no longer unconditionally compiled into the kernel. Drivers
166 using iflib and statically compiled into the kernel, now require
167 the 'device iflib' config option. For the same drivers loaded as
168 modules on kernels not having 'device iflib', the iflib.ko module
169 is loaded automatically.
172 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
173 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
174 servers that have vfs.nfsd.nfs_privport set will only allow mounts
175 from clients using a reserved port#. Since both the FreeBSD and Linux
176 NFSv4 clients use reserved port#s by default, this should not affect
180 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
181 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
182 it produces broken binaries when ifuncs are in use. Users needing
183 GNU ld should install the binutils port or package.
186 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
187 has been converted to a port (misc/ctm) and will be removed from
188 FreeBSD-13. A depreciation warning will be printed to stderr by
189 the ctm command, but the functionality will remain in base for all
193 The stable/12 branch has been created in subversion from head
197 Ports for the DRM modules have been simplified. Now, amd64 users should
198 just install the drm-kmod port. All others should install
201 Graphics hardware that's newer than about 2010 usually works with
202 drm-kmod. For hardware older than 2013, however, some users will need
203 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
204 than 2008 usually only works in drm-legacy-kmod. The graphics team can
205 only commit to hardware made since 2013 due to the complexity of the
206 market and difficulty to test all the older cards effectively. If you
207 have hardware supported by drm-kmod, you are strongly encouraged to use
208 that as you will get better support.
210 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
211 elsewhere, the drm and drm2 modules will be eliminated from the src base
212 soon (with a limited exception for arm). Please update to the package asap
213 and report any issues to x11@freebsd.org.
215 Generally, anybody using the drm*-kmod packages should add
216 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
217 cross-threading surprises, especially with automatic driver
218 loading from X11 startup. These will become the defaults in 13-current
222 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
223 custom kernel and module loading configuration files must be updated
224 accordingly. Moreover, interfaces previous presented as ixlvN to the
225 system are now exposed as iavfN and network configuration files must
226 be adjusted as necessary.
229 OpenSSL has been updated to version 1.1.1. This update included
230 additional various API changes througout the base system. It is
231 important to rebuild third-party software after upgrading. The value
232 of __FreeBSD_version has been bumped accordingly.
235 The legacy DRM modules and drivers have now been added to the loader's
236 module blacklist, in favor of loading them with kld_list in rc.conf(5).
237 The module blacklist may be overridden with the loader.conf(5)
238 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
242 The cam(4) based nda(4) driver will be used over nvd(4) by default on
243 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
244 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
245 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
249 Reproducible build mode is now on by default, in preparation for
250 FreeBSD 12.0. This eliminates build metadata such as the user,
251 host, and time from the kernel (and uname), unless the working tree
252 corresponds to a modified checkout from a version control system.
253 The previous behavior can be obtained by setting the /etc/src.conf
254 knob WITHOUT_REPRODUCIBLE_BUILD.
257 The Yarrow CSPRNG has been removed from the kernel as it has not been
258 supported by its designers since at least 2003. Fortuna has been the
259 default since FreeBSD-11.
262 devctl freeze/thaw have gone into the tree, the rc scripts have been
263 updated to use them and devmatch has been changed. You should update
264 kernel, userland and rc scripts all at the same time.
267 The default interpreter has been switched from 4th to Lua.
268 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
269 interpreter. If you have custom FORTH code you will need to set
270 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
271 src.conf for the build. This will create default hard links between
272 loader and loader_4th instead of loader and loader_lua, the new default.
273 If you are using UEFI it will create the proper hard link to loader.efi.
275 bhyve uses userboot.so. It remains 4th-only until some issues are solved
276 regarding coexisting with multiple versions of FreeBSD are resolved.
279 ls(1) now respects the COLORTERM environment variable used in other
280 systems and software to indicate that a colored terminal is both
281 supported and desired. If ls(1) is suddenly emitting colors, they may
282 be disabled again by either removing the unwanted COLORTERM from your
283 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
284 may not be observed in a future release.
287 The default pager for most commands has been changed to "less". To
288 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
292 The jedec_ts(4) driver has been removed. A superset of its functionality
293 is available in the jedec_dimm(4) driver, and the manpage for that
294 driver includes migration instructions. If you have "device jedec_ts"
295 in your kernel configuration file, it must be removed.
298 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
299 This should have no effect if the kernel is booted via BIOS/legacy boot.
300 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
301 has a buggy firmware that prevents a successful boot due to use of
305 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
306 support has been removed from the tree. These ports were
307 obsolete and/or known to be broken for many years.
310 loader.efi has been augmented to participate more fully in the
311 UEFI boot manager protocol. loader.efi will now look at the
312 BootXXXX environment variable to determine if a specific kernel
313 or root partition was specified. XXXX is derived from BootCurrent.
314 efibootmgr(8) manages these standard UEFI variables.
317 zfsloader's functionality has now been folded into loader.
318 zfsloader is no longer necessary once you've updated your
319 boot blocks. For a transition period, we will install a
320 hardlink for zfsloader to loader to allow a smooth transition
321 until the boot blocks can be updated (hard link because old
322 zfs boot blocks don't understand symlinks).
325 ARM64 now have efifb support, if you want to have serial console
326 on your arm64 board when an screen is connected and the bootloader
327 setup a frambuffer for us to use, just add :
331 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
332 an screen connected as the firmware will setup a framebuffer are that
333 u-boot will expose as an EFI framebuffer.
336 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
337 or take steps to update /etc/passwd before doing installworld on
338 existing systems. Do not skip the "mergemaster -Fp" step before
339 installworld, as described in the update procedures near the bottom
340 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
341 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
342 the ntp config file contain options that change file/dir locations.
343 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
344 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
345 taking steps to ensure that all required files/dirs are accessible
349 Big endian arm support has been removed.
352 The static environment setup in kernel configs is no longer mutually
353 exclusive with the loader(8) environment by default. In order to
354 restore the previous default behavior of disabling the loader(8)
355 environment if a static environment is present, you must specify
356 loader_env.disabled=1 in the static environment.
359 The ABI of syscalls used by management tools like sockstat and
360 netstat has been broken to allow 32-bit binaries to work on
361 64-bit kernels without modification. These programs will need
362 to match the kernel in order to function. External programs may
363 require minor modifications to accommodate a change of type in
364 structures from pointers to 64-bit virtual addresses.
367 On i386 and amd64 atomics are now inlined. Out of tree modules using
368 atomics will need to be rebuilt.
371 The '%I' format in the kern.corefile sysctl limits the number of
372 core files that a process can generate to the number stored in the
373 debug.ncores sysctl. The '%I' format is replaced by the single digit
374 index. Previously, if all indexes were taken the kernel would overwrite
375 only a core file with the highest index in a filename.
376 Currently the system will create a new core file if there is a free
377 index or if all slots are taken it will overwrite the oldest one.
380 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
381 6.0.1. Please see the 20141231 entry below for information about
382 prerequisites and upgrading, if you are not already using clang 3.5.0
386 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
387 needed to be changed to work with it. This change was made with r335763
388 and requires a mergemaster / etcupdate / etc to update the installed file.
391 r334930 changed the interface between the NFS modules, so they all
392 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
395 As of r334391 lld is the default amd64 system linker; it is installed
396 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
400 The kernel / userland interface for devinfo changed, so you'll
401 need a new kernel and userland as a pair for it to work (rebuilding
402 lib/libdevinfo is all that's required). devinfo and devmatch will
403 not work, but everything else will when there's a mismatch.
406 The on-disk format for hwpmc callchain records has changed to include
407 threadid corresponding to a given record. This changes the field offsets
408 and thus requires that libpmcstat be rebuilt before using a kernel
412 The vxge(4) driver has been removed. This driver was introduced into
413 HEAD one week before the Exar left the Ethernet market and is not
414 known to be used. If you have device vxge in your kernel config file
418 The amd64 kernel now requires a ld that supports ifunc to produce a
419 working kernel, either lld or a newer binutils. lld is built by default
420 on amd64, and the 'buildkernel' target uses it automatically. However,
421 it is not the default linker, so building the kernel the traditional
422 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
423 binutils port/package). lld will soon be default, and this requirement
426 NOTE: As of r334391 lld is the default system linker on amd64, and no
427 workaround is necessary.
430 The nxge(4) driver has been removed. This driver was for PCI-X 10g
431 cards made by s2io/Neterion. The company was aquired by Exar and
432 no longer sells or supports Ethernet products. If you have device
433 nxge in your kernel config file it must be removed.
436 The tz database (tzdb) has been updated to 2018e. This version more
437 correctly models time stamps in time zones with negative DST such as
438 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
439 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
440 time zone abbreviations and the tm_isdst flag.
443 The ixgb(4) driver has been removed. This driver was for an early and
444 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
445 quickly shifted to the long lived ixgbe family. If you have device
446 ixgb in your kernel config file it must be removed.
449 The lmc(4) driver has been removed. This was a WAN interface
450 card that was already reportedly rare in 2003, and had an ambiguous
451 license. If you have device lmc in your kernel config file it must
455 Support for Arcnet networks has been removed. If you have device
456 arcnet or device cm in your kernel config file they must be
460 Support for FDDI networks has been removed. If you have device
461 fddi or device fpa in your kernel config file they must be
465 In addition to supporting RFC 3164 formatted messages, the
466 syslogd(8) service is now capable of parsing RFC 5424 formatted
467 log messages. The main benefit of using RFC 5424 is that clients
468 may now send log messages with timestamps containing year numbers,
469 microseconds and time zone offsets.
471 Similarly, the syslog(3) C library function has been altered to
472 send RFC 5424 formatted messages to the local system logging
473 daemon. On systems using syslogd(8), this change should have no
474 negative impact, as long as syslogd(8) and the C library are
475 updated at the same time. On systems using a different system
476 logging daemon, it may be necessary to make configuration
477 adjustments, depending on the software used.
479 When using syslog-ng, add the 'syslog-protocol' flag to local
480 input sources to enable parsing of RFC 5424 formatted messages:
483 unix-dgram("/var/run/log" flags(syslog-protocol));
486 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
487 of the 'imuxsock' module to let messages be processed by the
488 regular RFC 3164/5424 parsing pipeline:
490 module(load="imuxsock" SysSock.UseSpecialParser="off")
492 Do note that these changes only affect communication between local
493 applications and syslogd(8). The format that syslogd(8) uses to
494 store messages on disk or forward messages to other systems
495 remains unchanged. syslogd(8) still uses RFC 3164 for these
496 purposes. Options to customize this behaviour will be added in the
497 future. Utilities that process log files stored in /var/log are
498 thus expected to continue to function as before.
500 __FreeBSD_version has been incremented to 1200061 to denote this
504 Support for token ring networks has been removed. If you
505 have "device token" in your kernel config you should remove
506 it. No device drivers supported token ring.
509 makefs was modified to be able to tag ISO9660 El Torito boot catalog
510 entries as EFI instead of overloading the i386 tag as done previously.
511 The amd64 mkisoimages.sh script used to build amd64 ISO images for
512 release was updated to use this. This may mean that makefs must be
513 updated before "make cdrom" can be run in the release directory. This
514 should be as simple as:
516 $ cd $SRCDIR/usr.sbin/makefs
517 $ make depend all install
520 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
521 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
522 Co-existance for the transition period will come shortly. Booting is a
523 complex environment and test coverage for Lua-enabled loaders has been
524 thin, so it would be prudent to assume it might not work and make
525 provisions for backup boot methods.
528 devmatch functionality has been turned on in devd. It will automatically
529 load drivers for unattached devices. This may cause unexpected drivers to
530 be loaded. Please report any problems to current@ and imp@freebsd.org.
533 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
534 6.0.0. Please see the 20141231 entry below for information about
535 prerequisites and upgrading, if you are not already using clang 3.5.0
539 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
540 This means it is used to link the kernel and userland libraries and
541 executables, but is not yet installed as /usr/bin/ld by default.
543 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
544 WITHOUT_LLD_BOOTSTRAP=yes
547 On i386, pmtimer has been removed. Its functionality has been folded
548 into apm. It was a no-op on ACPI in current for a while now (but was still
549 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
550 from kernel config files.
553 The use of RSS hash from the network card aka flowid has been
554 disabled by default for lagg(4) as it's currently incompatible with
555 the lacp and loadbalance protocols.
557 This can be re-enabled by setting the following in loader.conf:
558 net.link.lagg.default_use_flowid="1"
561 The SW_WATCHDOG option is no longer necessary to enable the
562 hardclock-based software watchdog if no hardware watchdog is
563 configured. As before, SW_WATCHDOG will cause the software
564 watchdog to be enabled even if a hardware watchdog is configured.
567 r326887 fixes the issue described in the 20171214 UPDATING entry.
568 r326888 flips the switch back to building GELI support always.
571 r362593 broke ZFS + GELI support for reasons unknown. However,
572 it also broke ZFS support generally, so GELI has been turned off
573 by default as the lesser evil in r326857. If you boot off ZFS and/or
574 GELI, it might not be a good time to update.
577 PowerPC users must update loader(8) by rebuilding world before
578 installing a new kernel, as the protocol connecting them has
579 changed. Without the update, loader metadata will not be passed
580 successfully to the kernel and users will have to enter their
581 root partition at the kernel mountroot prompt to continue booting.
582 Newer versions of loader can boot old kernels without issue.
585 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
586 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
587 to WITH/OUT_LOADER_GELI.
590 The naive and non-compliant support of posix_fallocate(2) in ZFS
591 has been removed as of r325320. The system call now returns EINVAL
592 when used on a ZFS file. Although the new behavior complies with the
593 standard, some consumers are not prepared to cope with it.
594 One known victim is lld prior to r325420.
597 Building in a FreeBSD src checkout will automatically create object
598 directories now rather than store files in the current directory if
599 'make obj' was not ran. Calling 'make obj' is no longer necessary.
600 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
601 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
605 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
606 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
607 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
608 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
609 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
610 The UNIFIED_OBJDIR option is a transitional feature that will be
611 removed for 12.0 release; please migrate to the new format for any
612 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
613 than hardcoding paths.
616 The native-xtools target no longer installs the files by default to the
617 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
618 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
621 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
622 options are changing from controlling the build if defined / undefined
623 to controlling the build with explicit 'yes' or 'no' values. They will
624 shift to WITH/WITHOUT options to match other options in the system.
627 libstand has turned into a private library for sys/boot use only.
628 It is no longer supported as a public interface outside of sys/boot.
631 The arm port has split armv6 into armv6 and armv7. armv7 is now
632 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
633 and are running a kernel from before r324363, you will need to add
634 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
637 When building multiple kernels using KERNCONF, non-existent KERNCONF
638 files will produce an error and buildkernel will fail. Previously
639 missing KERNCONF files silently failed giving no indication as to
640 why, only to subsequently discover during installkernel that the
641 desired kernel was never built in the first place.
644 The default serial number format for CTL LUNs has changed. This will
645 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
646 or iSCSI clients care about their LUNs' serial numbers. Users who
647 require serial number stability should hardcode serial numbers in
651 For 32-bit arm compiled for hard-float support, soft-floating point
652 binaries now always get their shared libraries from
653 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
654 /usr/libsoft also existed). Only users with a hard-float ld.so, but
655 soft-float everything else should be affected.
658 The geli password typed at boot is now hidden. To restore the previous
659 behavior, see geli(8) for configuration options.
662 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
663 sysctl values. Minor nit, but requires a rebuild of both world/kernel
667 "make check" behavior (made in ^/head@r295380) has been changed to
668 execute from a limited sandbox, as opposed to executing from
672 - The "beforecheck" and "aftercheck" targets are now specified.
673 - ${CHECKDIR} (added in commit noted above) has been removed.
674 - Legacy behavior can be enabled by setting
675 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
677 If the limited sandbox mode is enabled, "make check" will execute
678 "make distribution", then install, execute the tests, and clean up the
679 sandbox if successful.
681 The "make distribution" and "make install" targets are typically run as
682 root to set appropriate permissions and ownership at installation time.
683 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
684 environment if executing "make check" with limited sandbox mode using
685 an unprivileged user.
688 Since the switch to GPT disk labels, fsck for UFS/FFS has been
689 unable to automatically find alternate superblocks. As of r322297,
690 the information needed to find alternate superblocks has been
691 moved to the end of the area reserved for the boot block.
692 Filesystems created with a newfs of this vintage or later
693 will create the recovery information. If you have a filesystem
694 created prior to this change and wish to have a recovery block
695 created for your filesystem, you can do so by running fsck in
696 foreground mode (i.e., do not use the -p or -y options). As it
697 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
698 to which you should answer yes.
701 As of r321665, an NFSv4 server configuration that services
702 Kerberos mounts or clients that do not support the uid/gid in
703 owner/owner_group string capability, must explicitly enable
704 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
705 machine's /etc/rc.conf file.
708 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
709 Please see the 20141231 entry below for information about prerequisites
710 and upgrading, if you are not already using clang 3.5.0 or higher.
713 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
714 r-commands (rlogin, rsh, etc.) to be built with the base system.
717 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
718 a very major ABI incompatible change, so users of FreeBSD/powerpc must
719 be careful when performing source upgrades. It is best to run
720 'make installworld' from an alternate root system, either a live
721 CD/memory stick, or a temporary root partition. Additionally, all ports
722 must be recompiled. powerpc64 is largely unaffected, except in the case
723 of 32-bit compatibility. All 32-bit binaries will be affected.
726 Forward compatibility for the "ino64" project have been committed. This
727 will allow most new binaries to run on older kernels in a limited
728 fashion. This prevents many of the common foot-shooting actions in the
729 upgrade as well as the limited ability to roll back the kernel across
730 the ino64 upgrade. Complicated use cases may not work properly, though
731 enough simpler ones work to allow recovery in most situations.
734 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
735 if you require the GPL compiler.
738 The internal ABI used for communication between the NFS kernel modules
739 was changed by r320085, so __FreeBSD_version was bumped to
740 ensure all the NFS related modules are updated together.
743 The ABI of struct event was changed by extending the data
744 member to 64bit and adding ext fields. For upgrade, same
745 precautions as for the entry 20170523 "ino64" must be
749 The GNU roff toolchain has been removed from base. To render manpages
750 which are not supported by mandoc(1), man(1) can fallback on GNU roff
751 from ports (and recommends to install it).
752 To render roff(7) documents, consider using GNU roff from ports or the
753 heirloom doctools roff toolchain from ports via pkg install groff or
754 via pkg install heirloom-doctools.
757 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
758 smaller runtime footprint builds. This is useful for embedded systems
759 which only require one chipset support.
761 If you load it as a module, make sure this is in /boot/loader.conf:
765 This will load the HAL, all chip/RF backends and if_ath_pci.
766 If you have if_ath_pci in /boot/loader.conf, ensure it is after
767 if_ath or it will not load any HAL chipset support.
769 If you want to selectively load things (eg on ye cheape ARM/MIPS
770 platforms where RAM is at a premium) you should:
773 * load the chip modules in question
774 * load ath_rate, ath_dfs
776 * load if_ath_pci and/or if_ath_ahb depending upon your particular
777 bus bind type - this is where probe/attach is done.
779 For further comments/feedback, poke adrian@ .
782 The "ino64" 64-bit inode project has been committed, which extends
783 a number of types to 64 bits. Upgrading in place requires care and
784 adherence to the documented upgrade procedure.
786 If using a custom kernel configuration ensure that the
787 COMPAT_FREEBSD11 option is included (as during the upgrade the
788 system will be running the ino64 kernel with the existing world).
790 For the safest in-place upgrade begin by removing previous build
791 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
792 full procedure documented below under the heading "To rebuild
793 everything and install it on the current system." Specifically,
794 a reboot is required after installing the new kernel before
798 The NATM framework including the en(4), fatm(4), hatm(4), and
799 patm(4) devices has been removed. Consumers should plan a
800 migration before the end-of-life date for FreeBSD 11.
803 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
804 diff has not been implemented, if those are needed a newer version of
805 GNU diff is available via the diffutils package under the gdiff name.
808 As of r316810 for ipfilter, keep frags is no longer assumed when
809 keep state is specified in a rule. r316810 aligns ipfilter with
810 documentation in man pages separating keep frags from keep state.
811 This allows keep state to be specified without forcing keep frags
812 and allows keep frags to be specified independently of keep state.
813 To maintain previous behaviour, also specify keep frags with
814 keep state (as documented in ipf.conf.5).
817 arm64 builds now use the base system LLD 4.0.0 linker by default,
818 instead of requiring that the aarch64-binutils port or package be
819 installed. To continue using aarch64-binutils, set
820 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
823 The UDP optimization in entry 20160818 that added the sysctl
824 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
825 packets will no longer be treated as L3 broadcast packets.
828 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
829 use any explicitly assigned loopback address available in the jail
830 instead of using the first assigned address of the jail.
833 The ctl.ko module no longer implements the iSCSI target frontend:
834 cfiscsi.ko does instead.
836 If building cfiscsi.ko as a kernel module, the module can be loaded
837 via one of the following methods:
838 - `cfiscsi_load="YES"` in loader.conf(5).
839 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
840 - ctladm(8)/ctld(8), when compiled with iSCSI support
841 (`WITH_ISCSI=yes` in src.conf(5))
843 Please see cfiscsi(4) for more details.
846 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
847 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
848 same source (previously, the dependency of mmcsd.ko on mmc.ko was
849 missing, but mmcsd.ko now will refuse to load if it is incompatible
853 The syntax of ipfw(8) named states was changed to avoid ambiguity.
854 If you have used named states in the firewall rules, you need to modify
855 them after installworld and before rebooting. Now named states must
856 be prefixed with colon.
859 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
860 removed as the userland we provide cannot use them. The KMS version
861 (sys/dev/drm2) supports the same hardware.
864 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
865 Please see the 20141231 entry below for information about prerequisites
866 and upgrading, if you are not already using clang 3.5.0 or higher.
869 The code that provides support for ZFS .zfs/ directory functionality
870 has been reimplemented. It's not possible now to create a snapshot
871 by mkdir under .zfs/snapshot/. That should be the only user visible
875 EISA bus support has been removed. The WITH_EISA option is no longer
879 MCA bus support has been removed.
882 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
883 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
886 The EM_MULTIQUEUE kernel configuration option is deprecated now that
887 the em(4) driver conforms to iflib specifications.
890 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
891 IFLIB. If you have a custom kernel configuration that excludes em(4)
892 but you use igb(4), you need to re-add em(4) to your custom configuration.
895 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
896 Please see the 20141231 entry below for information about prerequisites
897 and upgrading, if you are not already using clang 3.5.0 or higher.
900 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
901 Please see the 20141231 entry below for information about prerequisites
902 and upgrading, if you are not already using clang 3.5.0 or higher.
905 The layout of the pmap structure has changed for powerpc to put the pmap
906 statistics at the front for all CPU variations. libkvm(3) and all tools
907 that link against it need to be recompiled.
910 isl(4) and cyapa(4) drivers now require a new driver,
911 chromebook_platform(4), to work properly on Chromebook-class hardware.
912 On other types of hardware the drivers may need to be configured using
913 device hints. Please see the corresponding manual pages for details.
916 The urtwn(4) driver was merged into rtwn(4) and now consists of
917 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
919 Also, firmware for RTL8188CE was renamed due to possible name
920 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
923 GNU rcs has been removed from base. It is available as packages:
924 - rcs: Latest GPLv3 GNU rcs version.
925 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
929 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
930 modules now requires that the kernel configuration contain the
931 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
934 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
935 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
938 Relocatable object files with the extension of .So have been renamed
939 to use an extension of .pico instead. The purpose of this change is
940 to avoid a name clash with shared libraries on case-insensitive file
941 systems. On those file systems, foo.So is the same file as foo.so.
944 GNU rcs has been turned off by default. It can (temporarily) be built
945 again by adding WITH_RCS knob in src.conf.
946 Otherwise, GNU rcs is available from packages:
947 - rcs: Latest GPLv3 GNU rcs version.
948 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
951 The backup_uses_rcs functionality has been removed from rc.subr.
954 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
955 two separate components, QUEUE_MACRO_DEBUG_TRACE and
956 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
957 QUEUE_MACRO_DEBUG behavior.
960 r304787 changed some ioctl interfaces between the iSCSI userspace
961 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
962 rebuilt to work with new kernels. __FreeBSD_version has been bumped
966 The UDP receive code has been updated to only treat incoming UDP
967 packets that were addressed to an L2 broadcast address as L3
968 broadcast packets. It is not expected that this will affect any
969 standards-conforming UDP application. The new behaviour can be
970 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
974 Remove the openbsd_poll system call.
975 __FreeBSD_version has been bumped because of this.
978 The stable/11 branch has been created from head@r302406.
981 The libc stub for the pipe(2) system call has been replaced with
982 a wrapper that calls the pipe2(2) system call and the pipe(2)
983 system call is now only implemented by the kernels that include
984 "options COMPAT_FREEBSD10" in their config file (this is the
985 default). Users should ensure that this option is enabled in
986 their kernel or upgrade userspace to r302092 before upgrading their
990 CAM will now strip leading spaces from SCSI disks' serial numbers.
991 This will affect users who create UFS filesystems on SCSI disks using
992 those disk's diskid device nodes. For example, if /etc/fstab
993 previously contained a line like
994 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
995 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
996 transforms like gmirror may also be affected. ZFS users should
1000 The bitstring(3) API has been updated with new functionality and
1001 improved performance. But it is binary-incompatible with the old API.
1002 Objects built with the new headers may not be linked against objects
1003 built with the old headers.
1006 The brk and sbrk functions have been removed from libc on arm64.
1007 Binutils from ports has been updated to not link to these
1008 functions and should be updated to the latest version before
1009 installing a new libc.
1012 The armv6 port now defaults to hard float ABI. Limited support
1013 for running both hardfloat and soft float on the same system
1014 is available using the libraries installed with -DWITH_LIBSOFT.
1015 This has only been tested as an upgrade path for installworld
1016 and packages may fail or need manual intervention to run. New
1017 packages will be needed.
1019 To update an existing self-hosted armv6hf system, you must add
1020 TARGET_ARCH=armv6 on the make command line for both the build
1021 and the install steps.
1024 Kernel modules compiled outside of a kernel build now default to
1025 installing to /boot/modules instead of /boot/kernel. Many kernel
1026 modules built this way (such as those in ports) already overrode
1027 KMODDIR explicitly to install into /boot/modules. However,
1028 manually building and installing a module from /sys/modules will
1029 now install to /boot/modules instead of /boot/kernel.
1032 The CAM I/O scheduler has been committed to the kernel. There should be
1033 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1034 list of known rogues that claim support for this but actually corrupt
1035 data is believed to be complete, be on the lookout for data
1036 corruption. The known rogue list is believed to be complete:
1038 o Crucial MX100, M550 drives with MU01 firmware.
1039 o Micron M510 and M550 drives with MU01 firmware.
1040 o Micron M500 prior to MU07 firmware
1041 o Samsung 830, 840, and 850 all firmwares
1042 o FCCT M500 all firmwares
1044 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1045 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1046 updated firmware. Black listed drives will work correctly because these
1047 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1048 this list is the same as found in Linux, it's believed there are no
1049 other rogues in the market place. All other models from the above
1052 To be safe, if you are at all concerned, you can quirk each of your
1053 drives to prevent NCQ from being sent by setting:
1054 kern.cam.ada.X.quirks="0x2"
1055 in loader.conf. If the drive requires the 4k sector quirk, set the
1056 quirks entry to 0x3.
1059 The FAST_DEPEND build option has been removed and its functionality is
1060 now the one true way. The old mkdep(1) style of 'make depend' has
1061 been removed. See 20160311 for further details.
1064 Resource range types have grown from unsigned long to uintmax_t. All
1065 drivers, and anything using libdevinfo, need to be recompiled.
1068 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1069 builds. It no longer runs mkdep(1) during 'make depend', and the
1070 'make depend' stage can safely be skipped now as it is auto ran
1071 when building 'make all' and will generate all SRCS and DPSRCS before
1072 building anything else. Dependencies are gathered at compile time with
1073 -MF flags kept in separate .depend files per object file. Users should
1074 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1075 stale .depend files.
1078 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1079 kernel modules. Therefore, if you load any kernel modules at boot time,
1080 please install the boot loaders after you install the kernel, but before
1084 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1085 make installkernel KERNCONF=YOUR_KERNEL_HERE
1086 make -C sys/boot install
1087 <reboot in single user>
1089 Then follow the usual steps, described in the General Notes section,
1093 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1094 see the 20141231 entry below for information about prerequisites and
1095 upgrading, if you are not already using clang 3.5.0 or higher.
1098 The AIO subsystem is now a standard part of the kernel. The
1099 VFS_AIO kernel option and aio.ko kernel module have been removed.
1100 Due to stability concerns, asynchronous I/O requests are only
1101 permitted on sockets and raw disks by default. To enable
1102 asynchronous I/O requests on all file types, set the
1103 vfs.aio.enable_unsafe sysctl to a non-zero value.
1106 The ELF object manipulation tool objcopy is now provided by the
1107 ELF Tool Chain project rather than by GNU binutils. It should be a
1108 drop-in replacement, with the addition of arm64 support. The
1109 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1110 to obtain the GNU version if necessary.
1113 Building ZFS pools on top of zvols is prohibited by default. That
1114 feature has never worked safely; it's always been prone to deadlocks.
1115 Using a zvol as the backing store for a VM guest's virtual disk will
1116 still work, even if the guest is using ZFS. Legacy behavior can be
1117 restored by setting vfs.zfs.vol.recursive=1.
1120 The NONE and HPN patches has been removed from OpenSSH. They are
1121 still available in the security/openssh-portable port.
1124 With the addition of ypldap(8), a new _ypldap user is now required
1125 during installworld. "mergemaster -p" can be used to add the user
1126 prior to installworld, as documented in the handbook.
1129 The tftp loader (pxeboot) now uses the option root-path directive. As a
1130 consequence it no longer looks for a pxeboot.4th file on the tftp
1131 server. Instead it uses the regular /boot infrastructure as with the
1135 The code to start recording plug and play data into the modules has
1136 been committed. While the old tools will properly build a new kernel,
1137 a number of warnings about "unknown metadata record 4" will be produced
1138 for an older kldxref. To avoid such warnings, make sure to rebuild
1139 the kernel toolchain (or world). Make sure that you have r292078 or
1140 later when trying to build 292077 or later before rebuilding.
1143 Debug data files are now built by default with 'make buildworld' and
1144 installed with 'make installworld'. This facilitates debugging but
1145 requires more disk space both during the build and for the installed
1146 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1150 r291527 changed the internal interface between the nfsd.ko and
1151 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1152 __FreeBSD_version has been bumped because of this.
1155 Add support for unicode collation strings leads to a change of
1156 order of files listed by ls(1) for example. To get back to the old
1157 behaviour, set LC_COLLATE environment variable to "C".
1159 Databases administrators will need to reindex their databases given
1160 collation results will be different.
1162 Due to a bug in install(1) it is recommended to remove the ancient
1163 locales before running make installworld.
1165 rm -rf /usr/share/locale/*
1168 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1169 libcrypto.so.7 or libssl.so.7 must be recompiled.
1172 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1173 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1174 should be replaced with isp_2400 and isp_2500 modules respectively.
1177 The build previously allowed using 'make -n' to not recurse into
1178 sub-directories while showing what commands would be executed, and
1179 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1180 and 'make -N' will not.
1183 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1184 and etcupdate will now use this file. A custom sendmail.cf is now
1185 updated via this mechanism rather than via installworld. If you had
1186 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1187 want to remove the exclusion or change it to "always install".
1188 /etc/mail/sendmail.cf is now managed the same way regardless of
1189 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1190 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1193 Compatibility shims for legacy ATA device names have been removed.
1194 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1195 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1196 environment variables, /dev/ad* and /dev/ar* symbolic links.
1199 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1200 Please see the 20141231 entry below for information about prerequisites
1201 and upgrading, if you are not already using clang 3.5.0 or higher.
1204 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1205 and renamed from .symbols to .debug. This reduces the size requirements
1206 on the boot partition or file system and provides consistency with
1207 userland debug files.
1209 When using the supported kernel installation method the
1210 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1211 as is done with /boot/kernel.
1213 Developers wishing to maintain the historical behavior of installing
1214 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1217 The wireless drivers had undergone changes that remove the 'parent
1218 interface' from the ifconfig -l output. The rc.d network scripts
1219 used to check presence of a parent interface in the list, so old
1220 scripts would fail to start wireless networking. Thus, etcupdate(3)
1221 or mergemaster(8) run is required after kernel update, to update your
1222 rc.d scripts in /etc.
1225 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1226 These configurations are now automatically interpreted as
1227 'scrub fragment reassemble'.
1230 Kernel-loadable modules for the random(4) device are back. To use
1231 them, the kernel must have
1234 options RANDOM_LOADABLE
1236 kldload(8) can then be used to load random_fortuna.ko
1237 or random_yarrow.ko. Please note that due to the indirect
1238 function calls that the loadable modules need to provide,
1239 the build-in variants will be slightly more efficient.
1241 The random(4) kernel option RANDOM_DUMMY has been retired due to
1242 unpopularity. It was not all that useful anyway.
1245 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1246 Control over building the ELF Tool Chain tools is now provided by
1247 the WITHOUT_TOOLCHAIN knob.
1250 The polarity of Pulse Per Second (PPS) capture events with the
1251 uart(4) driver has been corrected. Prior to this change the PPS
1252 "assert" event corresponded to the trailing edge of a positive PPS
1253 pulse and the "clear" event was the leading edge of the next pulse.
1255 As the width of a PPS pulse in a typical GPS receiver is on the
1256 order of 1 millisecond, most users will not notice any significant
1257 difference with this change.
1259 Anyone who has compensated for the historical polarity reversal by
1260 configuring a negative offset equal to the pulse width will need to
1261 remove that workaround.
1264 The default group assigned to /dev/dri entries has been changed
1265 from 'wheel' to 'video' with the id of '44'. If you want to have
1266 access to the dri devices please add yourself to the video group
1269 # pw groupmod video -m $USER
1272 The menu.rc and loader.rc files will now be replaced during
1273 upgrades. Please migrate local changes to menu.rc.local and
1274 loader.rc.local instead.
1277 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1278 strings and strip have been removed. The src.conf(5) knob
1279 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1282 As ZFS requires more kernel stack pages than is the default on some
1283 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1284 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1286 Please consider using 'options KSTACK_PAGES=X' where X is greater
1287 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1290 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1291 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1292 default, i.e., they will not contain "::". For example, instead
1293 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1294 to have a more specific match, such as different map entries for
1295 IPv6:0:0 vs IPv6:0. This change requires that configuration
1296 data (including maps, files, classes, custom ruleset, etc.) must
1297 use the same format, so make certain such configuration data is
1298 upgrading. As a very simple check search for patterns like
1299 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1300 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1301 the cf option UseCompressedIPv6Addresses.
1304 The default kernel entropy-processing algorithm is now
1305 Fortuna, replacing Yarrow.
1307 Assuming you have 'device random' in your kernel config
1308 file, the configurations allow a kernel option to override
1309 this default. You may choose *ONE* of:
1311 options RANDOM_YARROW # Legacy /dev/random algorithm.
1312 options RANDOM_DUMMY # Blocking-only driver.
1314 If you have neither, you get Fortuna. For most people,
1315 read no further, Fortuna will give a /dev/random that works
1316 like it always used to, and the difference will be irrelevant.
1318 If you remove 'device random', you get *NO* kernel-processed
1319 entropy at all. This may be acceptable to folks building
1320 embedded systems, but has complications. Carry on reading,
1321 and it is assumed you know what you need.
1323 *PLEASE* read random(4) and random(9) if you are in the
1324 habit of tweaking kernel configs, and/or if you are a member
1325 of the embedded community, wanting specific and not-usual
1326 behaviour from your security subsystems.
1328 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1329 random', you will NOT have a functioning /dev/random, and
1330 many cryptographic features will not work, including SSH.
1331 You may also find strange behaviour from the random(3) set
1332 of library functions, in particular sranddev(3), srandomdev(3)
1333 and arc4random(3). The reason for this is that the KERN_ARND
1334 sysctl only returns entropy if it thinks it has some to
1335 share, and with RANDOM_DUMMY or no 'device random' this
1339 An additional fix for the issue described in the 20150614 sendmail
1340 entry below has been committed in revision 284717.
1343 FreeBSD's old make (fmake) has been removed from the system. It is
1344 available as the devel/fmake port or via pkg install fmake.
1347 The fix for the issue described in the 20150614 sendmail entry
1348 below has been committed in revision 284436. The work
1349 around described in that entry is no longer needed unless the
1350 default setting is overridden by a confDH_PARAMETERS configuration
1351 setting of '5' or pointing to a 512 bit DH parameter file.
1354 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1355 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1356 and devel/kyua to version 0.20+ and adjust any calling code to work
1357 with Kyuafile and kyua.
1360 The import of openssl to address the FreeBSD-SA-15:10.openssl
1361 security advisory includes a change which rejects handshakes
1362 with DH parameters below 768 bits. sendmail releases prior
1363 to 8.15.2 (not yet released), defaulted to a 512 bit
1364 DH parameter setting for client connections. To work around
1365 this interoperability, sendmail can be configured to use a
1366 2048 bit DH parameter by:
1368 1. Edit /etc/mail/`hostname`.mc
1369 2. If a setting for confDH_PARAMETERS does not exist or
1370 exists and is set to a string beginning with '5',
1371 replace it with '2'.
1372 3. If a setting for confDH_PARAMETERS exists and is set to
1373 a file path, create a new file with:
1374 openssl dhparam -out /path/to/file 2048
1375 4. Rebuild the .cf file:
1376 cd /etc/mail/; make; make install
1377 5. Restart sendmail:
1378 cd /etc/mail/; make restart
1380 A sendmail patch is coming, at which time this file will be
1384 Generation of legacy formatted entries have been disabled by default
1385 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1386 entries were converted to use the new format by default when the new,
1387 machine independent format have been added and supported since FreeBSD
1390 Please see the pwd_mkdb(8) manual page for further details.
1393 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1394 20141231 entry below for information about prerequisites and upgrading,
1395 if you are not already using 3.5.0 or higher.
1398 TI platform code switched to using vendor DTS files and this update
1399 may break existing systems running on Beaglebone, Beaglebone Black,
1402 - dtb files should be regenerated/reinstalled. Filenames are the
1403 same but content is different now
1404 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1405 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1406 addressing scheme is now pin 25 on /dev/gpioc3.
1407 - Pandaboard: /etc/ttys should be updated, serial console device is
1408 now /dev/ttyu2, not /dev/ttyu0
1411 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1412 If you need the GNU extension from groff soelim(1), install groff
1413 from package: pkg install groff, or via ports: textproc/groff.
1416 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1417 defined in symlink(7); previously symlinks were silently ignored.
1420 The const qualifier has been removed from iconv(3) to comply with
1421 POSIX. The ports tree is aware of this from r384038 onwards.
1424 Libraries specified by LIBADD in Makefiles must have a corresponding
1425 DPADD_<lib> variable to ensure correct dependencies. This is now
1426 enforced in src.libnames.mk.
1429 From legacy ata(4) driver was removed support for SATA controllers
1430 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1431 Kernel modules ataahci and ataadaptec were removed completely,
1432 replaced by ahci and mvs modules respectively.
1435 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1436 the 20141231 entry below for information about prerequisites and
1437 upgrading, if you are not already using 3.5.0 or higher.
1440 The 32-bit PowerPC kernel has been changed to a position-independent
1441 executable. This can only be booted with a version of loader(8)
1442 newer than January 31, 2015, so make sure to update both world and
1443 kernel before rebooting.
1446 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1447 but before r278950, the RNG was not seeded properly. Immediately
1448 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1449 ssh keys or openssl keys) that were generated w/ a kernel from that
1450 range. This does not affect programs that directly used /dev/random
1451 or /dev/urandom. All userland uses of arc4random(3) are affected.
1454 The autofs(4) ABI was changed in order to restore binary compatibility
1455 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1456 with the new kernel.
1459 The powerpc64 kernel has been changed to a position-independent
1460 executable. This can only be booted with a new version of loader(8),
1461 so make sure to update both world and kernel before rebooting.
1464 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1465 only release, no new features have been added. Please see the 20141231
1466 entry below for information about prerequisites and upgrading, if you
1467 are not already using 3.5.0.
1470 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1471 taken from the ELF Tool Chain project rather than GNU binutils. They
1472 should be drop-in replacements, with the addition of arm64 support.
1473 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1474 binutils tools, if necessary. See 20150805 for updated information.
1477 The default Unbound configuration now enables remote control
1478 using a local socket. Users who have already enabled the
1479 local_unbound service should regenerate their configuration
1480 by running "service local_unbound setup" as root.
1483 The GNU texinfo and GNU info pages have been removed.
1484 To be able to view GNU info pages please install texinfo from ports.
1487 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1489 As of this release, a prerequisite for building clang, llvm and lldb is
1490 a C++11 capable compiler and C++11 standard library. This means that to
1491 be able to successfully build the cross-tools stage of buildworld, with
1492 clang as the bootstrap compiler, your system compiler or cross compiler
1493 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1494 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1497 On any standard FreeBSD 10.x or 11.x installation, where clang and
1498 libc++ are on by default (that is, on x86 or arm), this should work out
1501 On 9.x installations where clang is enabled by default, e.g. on x86 and
1502 powerpc, libc++ will not be enabled by default, so libc++ should be
1503 built (with clang) and installed first. If both clang and libc++ are
1504 missing, build clang first, then use it to build libc++.
1506 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1507 the instructions for 9.x above.
1509 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1510 default, and do not build clang.
1512 Many embedded systems are resource constrained, and will not be able to
1513 build clang in a reasonable time, or in some cases at all. In those
1514 cases, cross building bootable systems on amd64 is a workaround.
1516 This new version of clang introduces a number of new warnings, of which
1517 the following are most likely to appear:
1521 This warns in two cases, for both C and C++:
1522 * When the code is trying to take the absolute value of an unsigned
1523 quantity, which is effectively a no-op, and almost never what was
1524 intended. The code should be fixed, if at all possible. If you are
1525 sure that the unsigned quantity can be safely cast to signed, without
1526 loss of information or undefined behavior, you can add an explicit
1527 cast, or disable the warning.
1529 * When the code is trying to take an absolute value, but the called
1530 abs() variant is for the wrong type, which can lead to truncation.
1531 If you want to disable the warning instead of fixing the code, please
1532 make sure that truncation will not occur, or it might lead to unwanted
1535 -Wtautological-undefined-compare and
1536 -Wundefined-bool-conversion
1538 These warn when C++ code is trying to compare 'this' against NULL, while
1539 'this' should never be NULL in well-defined C++ code. However, there is
1540 some legacy (pre C++11) code out there, which actively abuses this
1541 feature, which was less strictly defined in previous C++ versions.
1543 Squid and openjdk do this, for example. The warning can be turned off
1544 for C++98 and earlier, but compiling the code in C++11 mode might result
1545 in unexpected behavior; for example, the parts of the program that are
1546 unreachable could be optimized away.
1549 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1550 kernel sources have been removed. The .h files remain, since some
1551 utilities include them. This will need to be fixed later.
1552 If "mount -t oldnfs ..." is attempted, it will fail.
1553 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1554 the utilities will report errors.
1557 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1558 directories to top level SUBDIR variable when their parent
1559 directory is included in LOCAL_DIRS. Users with build systems with
1560 such hierarchies and without SUBDIR entries in the parent
1561 directory Makefiles should add them or add the directories to
1565 faith(4) and faithd(8) have been removed from the base system. Faith
1566 has been obsolete for a very long time.
1569 vt(4), the new console driver, is enabled by default. It brings
1570 support for Unicode and double-width characters, as well as
1571 support for UEFI and integration with the KMS kernel video
1574 You may need to update your console settings in /etc/rc.conf,
1575 most probably the keymap. During boot, /etc/rc.d/syscons will
1576 indicate what you need to do.
1578 vt(4) still has issues and lacks some features compared to
1579 syscons(4). See the wiki for up-to-date information:
1580 https://wiki.freebsd.org/Newcons
1582 If you want to keep using syscons(4), you can do so by adding
1583 the following line to /boot/loader.conf:
1587 pjdfstest has been integrated into kyua as an opt-in test suite.
1588 Please see share/doc/pjdfstest/README for more details on how to
1592 gperf has been removed from the base system for architectures
1593 that use clang. Ports that require gperf will obtain it from the
1597 pjdfstest has been moved from tools/regression/pjdfstest to
1601 At svn r271982, The default linux compat kernel ABI has been adjusted
1602 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1603 update. If you wish to continue using the linux-f10 compat ports,
1604 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1605 encouraged to update their linux-compat packages to linux-c6 during
1606 their next update cycle.
1609 The ofwfb driver, used to provide a graphics console on PowerPC when
1610 using vt(4), no longer allows mmap() of all physical memory. This
1611 will prevent Xorg on PowerPC with some ATI graphics cards from
1612 initializing properly unless x11-servers/xorg-server is updated to
1616 The xdev targets have been converted to using TARGET and
1617 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1620 The default unbound configuration has been modified to address
1621 issues with reverse lookups on networks that use private
1622 address ranges. If you use the local_unbound service, run
1623 "service local_unbound setup" as root to regenerate your
1624 configuration, then "service local_unbound reload" to load the
1628 The GNU texinfo and GNU info pages are not built and installed
1629 anymore, WITH_INFO knob has been added to allow to built and install
1631 UPDATE: see 20150102 entry on texinfo's removal
1634 The GNU readline library is now an INTERNALLIB - that is, it is
1635 statically linked into consumers (GDB and variants) in the base
1636 system, and the shared library is no longer installed. The
1637 devel/readline port is available for third party software that
1641 The Itanium architecture (ia64) has been removed from the list of
1642 known architectures. This is the first step in the removal of the
1646 Commit r268115 has added NFSv4.1 server support, merged from
1647 projects/nfsv4.1-server. Since this includes changes to the
1648 internal interfaces between the NFS related modules, a full
1649 build of the kernel and modules will be necessary.
1650 __FreeBSD_version has been bumped.
1653 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1654 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1655 which differs from the behaviour controlled by this knob.)
1658 Maximal length of the serial number in CTL was increased from 16 to
1659 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1660 and ctld, need to be rebuilt to work with a new kernel.
1663 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1664 1 respectively to match the upstream numbers. They were out of
1665 sync because, when they were originally added to FreeBSD, the
1666 upstream versions were not respected. These libraries are private
1667 and not yet built by default, so renumbering them should be a
1668 non-issue. However, unclean source trees will yield broken test
1669 programs once the operator executes "make delete-old-libs" after a
1670 "make installworld".
1672 Additionally, the atf-sh binary was made private by moving it into
1673 /usr/libexec/. Already-built shell test programs will keep the
1674 path to the old binary so they will break after "make delete-old"
1677 If you are using WITH_TESTS=yes (not the default), wipe the object
1678 tree and rebuild from scratch to prevent spurious test failures.
1679 This is only needed once: the misnumbered libraries and misplaced
1680 binaries have been added to OptionalObsoleteFiles.inc so they will
1681 be removed during a clean upgrade.
1684 Clang and llvm have been upgraded to 3.4.1 release.
1687 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1688 be removed to avoid issues in the future (and has been added to
1692 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1693 past, it affected all builds that used the bsd.*.mk files. The old
1694 behavior was a bug, but people may have relied upon it. To get this
1695 behavior back, you can .include /etc/src.conf from /etc/make.conf
1696 (which is still global and isn't changed). This also changes the
1697 behavior of incremental builds inside the tree of individual
1698 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1699 Although this has survived make universe and some upgrade scenarios,
1700 other upgrade scenarios may have broken. At least one form of
1701 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1702 as well... In cases where MAKESYSPATH isn't working with this
1703 setting, you'll need to set it to the full path to your tree.
1705 One side effect of all this cleaning up is that bsd.compiler.mk
1706 is no longer implicitly included by bsd.own.mk. If you wish to
1707 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1711 The lindev device has been removed since /dev/full has been made a
1712 standard device. __FreeBSD_version has been bumped.
1715 The knob WITHOUT_VI was added to the base system, which controls
1716 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1717 in order to reorder files share/termcap and didn't build ex(1) as a
1718 build tool, so building/installing with WITH_VI is highly advised for
1719 build hosts for older releases.
1721 This issue has been fixed in stable/9 and stable/10 in r277022 and
1722 r276991, respectively.
1725 The YES_HESIOD knob has been removed. It has been obsolete for
1726 a decade. Please move to using WITH_HESIOD instead or your builds
1727 will silently lack HESIOD.
1730 The uart(4) driver has been changed with respect to its handling
1731 of the low-level console. Previously the uart(4) driver prevented
1732 any process from changing the baudrate or the CLOCAL and HUPCL
1733 control flags. By removing the restrictions, operators can make
1734 changes to the serial console port without having to reboot.
1735 However, when getty(8) is started on the serial device that is
1736 associated with the low-level console, a misconfigured terminal
1737 line in /etc/ttys will now have a real impact.
1738 Before upgrading the kernel, make sure that /etc/ttys has the
1739 serial console device configured as 3wire without baudrate to
1740 preserve the previous behaviour. E.g:
1741 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1744 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1745 to improve performance. To re-enable it, if needed, run rpcbind
1746 with command line option -W.
1749 Switched back to the GPL dtc compiler due to updates in the upstream
1750 dts files not being supported by the BSDL dtc compiler. You will need
1751 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1752 may result while building dtb files during a kernel build if you fail
1753 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1756 Clang and llvm have been upgraded to 3.4 release.
1759 The nve(4) driver has been removed. Please use the nfe(4) driver
1760 for NVIDIA nForce MCP Ethernet adapters instead.
1763 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1764 This could cause certain C++ applications using shared libraries built
1765 against the previous version of libc++ to crash. The incompatibility
1766 has now been fixed, but any C++ applications or shared libraries built
1767 between r261283 and r261801 should be recompiled.
1770 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1771 capability mode support. Please note that enabling the feature in
1772 kernel is still highly recommended.
1775 OpenSSH is now built with sandbox support, and will use sandbox as
1776 the default privilege separation method. This requires Capsicum
1777 capability mode support in kernel.
1780 The libelf and libdwarf libraries have been updated to newer
1781 versions from upstream. Shared library version numbers for
1782 these two libraries were bumped. Any ports or binaries
1783 requiring these two libraries should be recompiled.
1784 __FreeBSD_version is bumped to 1100006.
1787 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1788 instead of providing an explicit one, this would prevent such
1789 Makefile from providing its own Kyuafile in the future during
1790 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1791 intervention is needed to clean an objdir if you use NO_CLEAN:
1792 # find /usr/obj -name Kyuafile | xargs rm -f
1795 The behavior of gss_pseudo_random() for the krb5 mechanism
1796 has changed, for applications requesting a longer random string
1797 than produced by the underlying enctype's pseudo-random() function.
1798 In particular, the random string produced from a session key of
1799 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1800 be different at the 17th octet and later, after this change.
1801 The counter used in the PRF+ construction is now encoded as a
1802 big-endian integer in accordance with RFC 4402.
1803 __FreeBSD_version is bumped to 1100004.
1806 The WITHOUT_ATF build knob has been removed and its functionality
1807 has been subsumed into the more generic WITHOUT_TESTS. If you were
1808 using the former to disable the build of the ATF libraries, you
1809 should change your settings to use the latter.
1812 The default version of mtree is nmtree which is obtained from
1813 NetBSD. The output is generally the same, but may vary
1814 slightly. If you found you need identical output adding
1815 "-F freebsd9" to the command line should do the trick. For the
1816 time being, the old mtree is available as fmtree.
1819 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1820 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1821 1.1.4_8 and verify bsdyml not linked in, before running "make
1823 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1825 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1828 The stable/10 branch has been created in subversion from head
1835 Avoid using make -j when upgrading. While generally safe, there are
1836 sometimes problems using -j to upgrade. If your upgrade fails with
1837 -j, please try again without -j. From time to time in the past there
1838 have been problems using -j with buildworld and/or installworld. This
1839 is especially true when upgrading between "distant" versions (eg one
1840 that cross a major release boundary or several minor releases, or when
1841 several months have passed on the -current branch).
1843 Sometimes, obscure build problems are the result of environment
1844 poisoning. This can happen because the make utility reads its
1845 environment when searching for values for global variables. To run
1846 your build attempts in an "environmental clean room", prefix all make
1847 commands with 'env -i '. See the env(1) manual page for more details.
1849 When upgrading from one major version to another it is generally best to
1850 upgrade to the latest code in the currently installed branch first, then
1851 do an upgrade to the new branch. This is the best-tested upgrade path,
1852 and has the highest probability of being successful. Please try this
1853 approach if you encounter problems with a major version upgrade. Since
1854 the stable 4.x branch point, one has generally been able to upgrade from
1855 anywhere in the most recent stable branch to head / current (or even the
1856 last couple of stable branches). See the top of this file when there's
1859 When upgrading a live system, having a root shell around before
1860 installing anything can help undo problems. Not having a root shell
1861 around can lead to problems if pam has changed too much from your
1862 starting point to allow continued authentication after the upgrade.
1864 This file should be read as a log of events. When a later event changes
1865 information of a prior event, the prior event should not be deleted.
1866 Instead, a pointer to the entry with the new information should be
1867 placed in the old entry. Readers of this file should also sanity check
1868 older entries before relying on them blindly. Authors of new entries
1869 should write them with this in mind.
1873 When upgrading the boot ZFS pool to a new version, always follow
1876 1.) recompile and reinstall the ZFS boot loader and boot block
1877 (this is part of "make buildworld" and "make installworld")
1879 2.) update the ZFS boot block on your boot drive
1881 The following example updates the ZFS boot block on the first
1882 partition (freebsd-boot) of a GPT partitioned drive ada0:
1883 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1885 Non-boot pools do not need these updates.
1889 If you are updating from a prior version of FreeBSD (even one just
1890 a few days old), you should follow this procedure. It is the most
1891 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1893 make kernel-toolchain
1894 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1895 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1897 To test a kernel once
1898 ---------------------
1899 If you just want to boot a kernel once (because you are not sure
1900 if it works, or if you want to boot a known bad kernel to provide
1901 debugging information) run
1902 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1903 nextboot -k testkernel
1905 To rebuild everything and install it on the current system.
1906 -----------------------------------------------------------
1907 # Note: sometimes if you are running current you gotta do more than
1908 # is listed here if you are upgrading from a really old current.
1910 <make sure you have good level 0 dumps>
1912 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1913 make installkernel KERNCONF=YOUR_KERNEL_HERE
1915 <reboot in single user> [3]
1922 To cross-install current onto a separate partition
1923 --------------------------------------------------
1924 # In this approach we use a separate partition to hold
1925 # current's root, 'usr', and 'var' directories. A partition
1926 # holding "/", "/usr" and "/var" should be about 2GB in
1929 <make sure you have good level 0 dumps>
1932 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1933 <maybe newfs current's root partition>
1934 <mount current's root partition on directory ${CURRENT_ROOT}>
1935 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1936 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1937 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1938 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1939 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1940 <reboot into current>
1941 <do a "native" rebuild/install as described in the previous section>
1942 <maybe install compatibility libraries from ports/misc/compat*>
1946 To upgrade in-place from stable to current
1947 ----------------------------------------------
1948 <make sure you have good level 0 dumps>
1950 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1951 make installkernel KERNCONF=YOUR_KERNEL_HERE
1953 <reboot in single user> [3]
1960 Make sure that you've read the UPDATING file to understand the
1961 tweaks to various things you need. At this point in the life
1962 cycle of current, things change often and you are on your own
1963 to cope. The defaults can also change, so please read ALL of
1964 the UPDATING entries.
1966 Also, if you are tracking -current, you must be subscribed to
1967 freebsd-current@freebsd.org. Make sure that before you update
1968 your sources that you have read and understood all the recent
1969 messages there. If in doubt, please track -stable which has
1970 much fewer pitfalls.
1972 [1] If you have third party modules, such as vmware, you
1973 should disable them at this point so they don't crash your
1976 [3] From the bootblocks, boot -s, and then do
1981 adjkerntz -i # if CMOS is wall time
1982 Also, when doing a major release upgrade, it is required that
1983 you boot into single user mode to do the installworld.
1985 [4] Note: This step is non-optional. Failure to do this step
1986 can result in a significant reduction in the functionality of the
1987 system. Attempting to do it by hand is not recommended and those
1988 that pursue this avenue should read this file carefully, as well
1989 as the archives of freebsd-current and freebsd-hackers mailing lists
1990 for potential gotchas. The -U option is also useful to consider.
1991 See mergemaster(8) for more information.
1993 [5] Usually this step is a no-op. However, from time to time
1994 you may need to do this if you get unknown user in the following
1995 step. It never hurts to do it all the time. You may need to
1996 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1997 install) after the buildworld before this step if you last updated
1998 from current before 20130425 or from -stable before 20130430.
2000 [6] This only deletes old files and directories. Old libraries
2001 can be deleted by "make delete-old-libs", but you have to make
2002 sure that no program is using those libraries anymore.
2004 [8] The new kernel must be able to run existing binaries used by
2005 an installworld. When upgrading across major versions, the new
2006 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2007 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2008 binaries). Failure to do so may leave you with a system that is
2009 hard to boot to recover. A GENERIC kernel will include suitable
2010 compatibility options to run binaries from older branches.
2012 Make sure that you merge any new devices from GENERIC since the
2013 last time you updated your kernel config file.
2015 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2016 "?=" instead of the "=" assignment operator, so that buildworld can
2017 override the CPUTYPE if it needs to.
2019 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2020 not on the command line, or in /etc/make.conf. buildworld will
2021 warn if it is improperly defined.
2024 This file contains a list, in reverse chronological order, of major
2025 breakages in tracking -current. It is not guaranteed to be a complete
2026 list of such breakages, and only contains entries since September 23, 2011.
2027 If you need to see UPDATING entries from before that date, you will need
2028 to fetch an UPDATING file from an older FreeBSD release.
2030 Copyright information:
2032 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2034 Redistribution, publication, translation and use, with or without
2035 modification, in full or in part, in any form or format of this
2036 document are permitted without further permission from the author.
2038 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2039 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2040 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2041 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2042 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2043 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2044 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2045 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2046 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2047 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2048 POSSIBILITY OF SUCH DAMAGE.
2050 Contact Warner Losh if you have any questions about your use of