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