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.
24 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
25 As of be70c7a50d32 it is no longer used by userspace, but it does mean
26 users may not be able to enumerate pf states if they update the kernel
27 past c021ff986e2b without first updating userspace past be70c7a50d32.
30 The 20210707 awk update brought in a change in behavior. This has
31 been corrected as of d4d252c49976. Between these dates, if you
32 installed a new awk binary, you may not be able to build a new
33 kernel because the change in behavior affected the genoffset
34 script used to build the kernel. If you did update, the fix is
35 to update your sources past the above hash and do
38 % sudo -E make install
39 to enable building kernels again.
42 awk has been updated to the latest one-true-awk version 20210215.
43 This contains a number of minor bug fixes.
46 Commit 6ae32cc8182f changed the internal KAPI between the krpc and
47 nfsd modules. As such, both need to be rebuilt from sources.
48 Bump __FreeBSD_version to 1202508.
51 Commit e9959506d2cc changed the internal KAPI between the
52 nscl.ko and nfscommon.ko modules, so they both need to be
56 Commit 0a1fdb867c72 changed the internal KAPI between
57 the krpc and NFS. As such, the krpc, nfscommon and
58 nfscl modules must all be rebuilt from sources.
59 Without this patch, NFSv4.1 mounts should not
60 be done with the nfscbd(8) daemon running, to avoid
61 needing a working back channel for server->client RPCs.
64 The make.conf(5) MALLOC_PRODUCTION variable, used for disabling and
65 enabling assertions and statistics gathering in malloc(3), has been
66 migrated to a src.conf(5) WITH/WITHOUT_MALLOC_PRODUCTION option.
68 On stable branches, WITH_MALLOC_PRODUCTION is set by default, which
69 means that malloc(3) has assertions and statistics gathering disabled,
70 for improved performance.
72 For backwards compatibility, the make.conf(5) MALLOC_PRODUCTION is still
73 honored, but it is now deprecated and undocumented.
76 The resume code now notifies devd with the 'kernel' system
77 rather than the old 'kern' subsystem to be consistent with
78 other use. The old notification will be created as well, but
79 will be removed prior to FreeBSD 14.0.
82 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
83 been upgraded to 10.0.1. Please see the 20141231 entry below for
84 information about prerequisites and upgrading, if you are not already
85 using clang 3.5.0 or higher.
88 read(2) of a directory fd is now rejected by default. root may
89 re-enable it for the entire system with the
90 security.bsd.allow_read_dir sysctl(8) MIB.
92 It may be advised to setup aliases for grep to default to `-d skip` if
93 commonly non-recursively grepping a list that includes directories and
94 the potential for the resulting stderr output is not tolerable. Example
95 aliases are now installed, commented out, in /root/.cshrc.
98 Upstream DTS from Linux 5.6 was merged and they now have the SID
99 and THS (Secure ID controller and THermal Sensor) node present.
100 The DTB overlays have now been removed from the tree for the H3/H5 and
101 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
102 deal with upstream DTS. If you are using those overlays you need to
103 remove them from loader.conf and update the DTBs on the FAT partition.
106 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
107 been upgraded to 10.0.0. Please see the 20141231 entry below for
108 information about prerequisites and upgrading, if you are not already
109 using clang 3.5.0 or higher.
112 The root certificates of the Mozilla CA Certificate Store have been
113 imported into the base system and can be managed with the certctl(8)
114 utility. If you have installed the security/ca_root_nss port or package
115 with the ETCSYMLINK option (the default), be advised that there may be
116 differences between those included in the port and those included in
117 base due to differences in nss branch used as well as general update
118 frequency. Note also that certctl(8) cannot manage certs in the
119 format used by the security/ca_root_nss port.
122 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
123 been upgraded to 9.0.1. Please see the 20141231 entry below for
124 information about prerequisites and upgrading, if you are not already
125 using clang 3.5.0 or higher.
128 The nctgpio and wbwd drivers have been moved to the superio bus.
129 If you have one of these drivers in a kernel configuration, then
130 you should add device superio to it. If you use one of these drivers
131 as a module and you compile a custom set of modules, then you should
132 add superio to the set.
135 The tap(4) driver has been folded into tun(4), and the module has been
136 renamed to tuntap. You should update any kld_list="if_tap" or
137 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
138 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
139 module instead, and "device tap" or "device tun" entries in kernel
140 config files to select the tuntap device instead.
143 ntpd no longer by default locks its pages in memory, allowing them
144 to be paged out by the kernel. Use rlimit memlock to restore
145 historic BSD behaviour. For example, add "rlimit memlock 32"
146 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
149 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
150 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
151 been removed from mount_fusefs(8). You can safely remove them from
152 your scripts, because they had no effect.
154 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
155 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
156 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
157 sysctls have been removed. If you felt the need to set any of them to
158 a non-default value, please tell asomers@FreeBSD.org why.
161 The fuse(4) module has been renamed to fusefs(4) for consistency with
162 other filesystems. You should update any kld_load="fuse" entries in
163 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
164 "options FUSE" enties in kernel config files.
167 Default permissions on the /var/account/acct file (and copies of it
168 rotated by periodic daily scripts) are changed from 0644 to 0640
169 because the file contains sensitive information that should not be
170 world-readable. If the /var/account directory must be created by
171 rc.d/accounting, the mode used is now 0750. Admins who use the
172 accounting feature are encouraged to change the mode of an existing
173 /var/account directory to 0750 or 0700.
176 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
177 been upgraded to 8.0.1. Please see the 20141231 entry below for
178 information about prerequisites and upgrading, if you are not already
179 using clang 3.5.0 or higher.
182 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
183 functionality needed for the RETPOLINE option should work properly
184 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
187 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
188 8.0.0. Please see the 20141231 entry below for information about
189 prerequisites and upgrading, if you are not already using clang 3.5.0
193 The RETPOLINE option produces non-functional ifunc-using binaries
194 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
195 Once Clang 8 is merged it may be enabled again.
198 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
199 7.0.1. Please see the 20141231 entry below for information about
200 prerequisites and upgrading, if you are not already using clang 3.5.0
204 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
205 compiled into your custom kernel, add 'device xz' statement to the
209 Iflib is no longer unconditionally compiled into the kernel. Drivers
210 using iflib and statically compiled into the kernel, now require
211 the 'device iflib' config option. For the same drivers loaded as
212 modules on kernels not having 'device iflib', the iflib.ko module
213 is loaded automatically.
216 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
217 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
218 servers that have vfs.nfsd.nfs_privport set will only allow mounts
219 from clients using a reserved port#. Since both the FreeBSD and Linux
220 NFSv4 clients use reserved port#s by default, this should not affect
224 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
225 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
226 it produces broken binaries when ifuncs are in use. Users needing
227 GNU ld should install the binutils port or package.
230 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
231 has been converted to a port (misc/ctm) and will be removed from
232 FreeBSD-13. A depreciation warning will be printed to stderr by
233 the ctm command, but the functionality will remain in base for all
237 The stable/12 branch has been created in subversion from head
241 Ports for the DRM modules have been simplified. Now, amd64 users should
242 just install the drm-kmod port. All others should install
245 Graphics hardware that's newer than about 2010 usually works with
246 drm-kmod. For hardware older than 2013, however, some users will need
247 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
248 than 2008 usually only works in drm-legacy-kmod. The graphics team can
249 only commit to hardware made since 2013 due to the complexity of the
250 market and difficulty to test all the older cards effectively. If you
251 have hardware supported by drm-kmod, you are strongly encouraged to use
252 that as you will get better support.
254 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
255 elsewhere, the drm and drm2 modules will be eliminated from the src base
256 soon (with a limited exception for arm). Please update to the package asap
257 and report any issues to x11@freebsd.org.
259 Generally, anybody using the drm*-kmod packages should add
260 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
261 cross-threading surprises, especially with automatic driver
262 loading from X11 startup. These will become the defaults in 13-current
266 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
267 custom kernel and module loading configuration files must be updated
268 accordingly. Moreover, interfaces previous presented as ixlvN to the
269 system are now exposed as iavfN and network configuration files must
270 be adjusted as necessary.
273 OpenSSL has been updated to version 1.1.1. This update included
274 additional various API changes througout the base system. It is
275 important to rebuild third-party software after upgrading. The value
276 of __FreeBSD_version has been bumped accordingly.
279 The legacy DRM modules and drivers have now been added to the loader's
280 module blacklist, in favor of loading them with kld_list in rc.conf(5).
281 The module blacklist may be overridden with the loader.conf(5)
282 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
286 The cam(4) based nda(4) driver will be used over nvd(4) by default on
287 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
288 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
289 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
293 Reproducible build mode is now on by default, in preparation for
294 FreeBSD 12.0. This eliminates build metadata such as the user,
295 host, and time from the kernel (and uname), unless the working tree
296 corresponds to a modified checkout from a version control system.
297 The previous behavior can be obtained by setting the /etc/src.conf
298 knob WITHOUT_REPRODUCIBLE_BUILD.
301 The Yarrow CSPRNG has been removed from the kernel as it has not been
302 supported by its designers since at least 2003. Fortuna has been the
303 default since FreeBSD-11.
306 devctl freeze/thaw have gone into the tree, the rc scripts have been
307 updated to use them and devmatch has been changed. You should update
308 kernel, userland and rc scripts all at the same time.
311 The default interpreter has been switched from 4th to Lua.
312 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
313 interpreter. If you have custom FORTH code you will need to set
314 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
315 src.conf for the build. This will create default hard links between
316 loader and loader_4th instead of loader and loader_lua, the new default.
317 If you are using UEFI it will create the proper hard link to loader.efi.
319 bhyve uses userboot.so. It remains 4th-only until some issues are solved
320 regarding coexisting with multiple versions of FreeBSD are resolved.
323 ls(1) now respects the COLORTERM environment variable used in other
324 systems and software to indicate that a colored terminal is both
325 supported and desired. If ls(1) is suddenly emitting colors, they may
326 be disabled again by either removing the unwanted COLORTERM from your
327 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
328 may not be observed in a future release.
331 The default pager for most commands has been changed to "less". To
332 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
336 The jedec_ts(4) driver has been removed. A superset of its functionality
337 is available in the jedec_dimm(4) driver, and the manpage for that
338 driver includes migration instructions. If you have "device jedec_ts"
339 in your kernel configuration file, it must be removed.
342 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
343 This should have no effect if the kernel is booted via BIOS/legacy boot.
344 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
345 has a buggy firmware that prevents a successful boot due to use of
349 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
350 support has been removed from the tree. These ports were
351 obsolete and/or known to be broken for many years.
354 loader.efi has been augmented to participate more fully in the
355 UEFI boot manager protocol. loader.efi will now look at the
356 BootXXXX environment variable to determine if a specific kernel
357 or root partition was specified. XXXX is derived from BootCurrent.
358 efibootmgr(8) manages these standard UEFI variables.
361 zfsloader's functionality has now been folded into loader.
362 zfsloader is no longer necessary once you've updated your
363 boot blocks. For a transition period, we will install a
364 hardlink for zfsloader to loader to allow a smooth transition
365 until the boot blocks can be updated (hard link because old
366 zfs boot blocks don't understand symlinks).
369 ARM64 now have efifb support, if you want to have serial console
370 on your arm64 board when an screen is connected and the bootloader
371 setup a frambuffer for us to use, just add :
375 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
376 an screen connected as the firmware will setup a framebuffer are that
377 u-boot will expose as an EFI framebuffer.
380 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
381 or take steps to update /etc/passwd before doing installworld on
382 existing systems. Do not skip the "mergemaster -Fp" step before
383 installworld, as described in the update procedures near the bottom
384 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
385 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
386 the ntp config file contain options that change file/dir locations.
387 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
388 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
389 taking steps to ensure that all required files/dirs are accessible
393 Big endian arm support has been removed.
396 The static environment setup in kernel configs is no longer mutually
397 exclusive with the loader(8) environment by default. In order to
398 restore the previous default behavior of disabling the loader(8)
399 environment if a static environment is present, you must specify
400 loader_env.disabled=1 in the static environment.
403 The ABI of syscalls used by management tools like sockstat and
404 netstat has been broken to allow 32-bit binaries to work on
405 64-bit kernels without modification. These programs will need
406 to match the kernel in order to function. External programs may
407 require minor modifications to accommodate a change of type in
408 structures from pointers to 64-bit virtual addresses.
411 On i386 and amd64 atomics are now inlined. Out of tree modules using
412 atomics will need to be rebuilt.
415 The '%I' format in the kern.corefile sysctl limits the number of
416 core files that a process can generate to the number stored in the
417 debug.ncores sysctl. The '%I' format is replaced by the single digit
418 index. Previously, if all indexes were taken the kernel would overwrite
419 only a core file with the highest index in a filename.
420 Currently the system will create a new core file if there is a free
421 index or if all slots are taken it will overwrite the oldest one.
424 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
425 6.0.1. Please see the 20141231 entry below for information about
426 prerequisites and upgrading, if you are not already using clang 3.5.0
430 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
431 needed to be changed to work with it. This change was made with r335763
432 and requires a mergemaster / etcupdate / etc to update the installed file.
435 r334930 changed the interface between the NFS modules, so they all
436 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
439 As of r334391 lld is the default amd64 system linker; it is installed
440 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
444 The kernel / userland interface for devinfo changed, so you'll
445 need a new kernel and userland as a pair for it to work (rebuilding
446 lib/libdevinfo is all that's required). devinfo and devmatch will
447 not work, but everything else will when there's a mismatch.
450 The on-disk format for hwpmc callchain records has changed to include
451 threadid corresponding to a given record. This changes the field offsets
452 and thus requires that libpmcstat be rebuilt before using a kernel
456 The vxge(4) driver has been removed. This driver was introduced into
457 HEAD one week before the Exar left the Ethernet market and is not
458 known to be used. If you have device vxge in your kernel config file
462 The amd64 kernel now requires a ld that supports ifunc to produce a
463 working kernel, either lld or a newer binutils. lld is built by default
464 on amd64, and the 'buildkernel' target uses it automatically. However,
465 it is not the default linker, so building the kernel the traditional
466 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
467 binutils port/package). lld will soon be default, and this requirement
470 NOTE: As of r334391 lld is the default system linker on amd64, and no
471 workaround is necessary.
474 The nxge(4) driver has been removed. This driver was for PCI-X 10g
475 cards made by s2io/Neterion. The company was aquired by Exar and
476 no longer sells or supports Ethernet products. If you have device
477 nxge in your kernel config file it must be removed.
480 The tz database (tzdb) has been updated to 2018e. This version more
481 correctly models time stamps in time zones with negative DST such as
482 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
483 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
484 time zone abbreviations and the tm_isdst flag.
487 The ixgb(4) driver has been removed. This driver was for an early and
488 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
489 quickly shifted to the long lived ixgbe family. If you have device
490 ixgb in your kernel config file it must be removed.
493 The lmc(4) driver has been removed. This was a WAN interface
494 card that was already reportedly rare in 2003, and had an ambiguous
495 license. If you have device lmc in your kernel config file it must
499 Support for Arcnet networks has been removed. If you have device
500 arcnet or device cm in your kernel config file they must be
504 Support for FDDI networks has been removed. If you have device
505 fddi or device fpa in your kernel config file they must be
509 In addition to supporting RFC 3164 formatted messages, the
510 syslogd(8) service is now capable of parsing RFC 5424 formatted
511 log messages. The main benefit of using RFC 5424 is that clients
512 may now send log messages with timestamps containing year numbers,
513 microseconds and time zone offsets.
515 Similarly, the syslog(3) C library function has been altered to
516 send RFC 5424 formatted messages to the local system logging
517 daemon. On systems using syslogd(8), this change should have no
518 negative impact, as long as syslogd(8) and the C library are
519 updated at the same time. On systems using a different system
520 logging daemon, it may be necessary to make configuration
521 adjustments, depending on the software used.
523 When using syslog-ng, add the 'syslog-protocol' flag to local
524 input sources to enable parsing of RFC 5424 formatted messages:
527 unix-dgram("/var/run/log" flags(syslog-protocol));
530 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
531 of the 'imuxsock' module to let messages be processed by the
532 regular RFC 3164/5424 parsing pipeline:
534 module(load="imuxsock" SysSock.UseSpecialParser="off")
536 Do note that these changes only affect communication between local
537 applications and syslogd(8). The format that syslogd(8) uses to
538 store messages on disk or forward messages to other systems
539 remains unchanged. syslogd(8) still uses RFC 3164 for these
540 purposes. Options to customize this behaviour will be added in the
541 future. Utilities that process log files stored in /var/log are
542 thus expected to continue to function as before.
544 __FreeBSD_version has been incremented to 1200061 to denote this
548 Support for token ring networks has been removed. If you
549 have "device token" in your kernel config you should remove
550 it. No device drivers supported token ring.
553 makefs was modified to be able to tag ISO9660 El Torito boot catalog
554 entries as EFI instead of overloading the i386 tag as done previously.
555 The amd64 mkisoimages.sh script used to build amd64 ISO images for
556 release was updated to use this. This may mean that makefs must be
557 updated before "make cdrom" can be run in the release directory. This
558 should be as simple as:
560 $ cd $SRCDIR/usr.sbin/makefs
561 $ make depend all install
564 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
565 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
566 Co-existance for the transition period will come shortly. Booting is a
567 complex environment and test coverage for Lua-enabled loaders has been
568 thin, so it would be prudent to assume it might not work and make
569 provisions for backup boot methods.
572 devmatch functionality has been turned on in devd. It will automatically
573 load drivers for unattached devices. This may cause unexpected drivers to
574 be loaded. Please report any problems to current@ and imp@freebsd.org.
577 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
578 6.0.0. Please see the 20141231 entry below for information about
579 prerequisites and upgrading, if you are not already using clang 3.5.0
583 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
584 This means it is used to link the kernel and userland libraries and
585 executables, but is not yet installed as /usr/bin/ld by default.
587 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
588 WITHOUT_LLD_BOOTSTRAP=yes
591 On i386, pmtimer has been removed. Its functionality has been folded
592 into apm. It was a no-op on ACPI in current for a while now (but was still
593 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
594 from kernel config files.
597 The use of RSS hash from the network card aka flowid has been
598 disabled by default for lagg(4) as it's currently incompatible with
599 the lacp and loadbalance protocols.
601 This can be re-enabled by setting the following in loader.conf:
602 net.link.lagg.default_use_flowid="1"
605 The SW_WATCHDOG option is no longer necessary to enable the
606 hardclock-based software watchdog if no hardware watchdog is
607 configured. As before, SW_WATCHDOG will cause the software
608 watchdog to be enabled even if a hardware watchdog is configured.
611 r326887 fixes the issue described in the 20171214 UPDATING entry.
612 r326888 flips the switch back to building GELI support always.
615 r362593 broke ZFS + GELI support for reasons unknown. However,
616 it also broke ZFS support generally, so GELI has been turned off
617 by default as the lesser evil in r326857. If you boot off ZFS and/or
618 GELI, it might not be a good time to update.
621 PowerPC users must update loader(8) by rebuilding world before
622 installing a new kernel, as the protocol connecting them has
623 changed. Without the update, loader metadata will not be passed
624 successfully to the kernel and users will have to enter their
625 root partition at the kernel mountroot prompt to continue booting.
626 Newer versions of loader can boot old kernels without issue.
629 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
630 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
631 to WITH/OUT_LOADER_GELI.
634 The naive and non-compliant support of posix_fallocate(2) in ZFS
635 has been removed as of r325320. The system call now returns EINVAL
636 when used on a ZFS file. Although the new behavior complies with the
637 standard, some consumers are not prepared to cope with it.
638 One known victim is lld prior to r325420.
641 Building in a FreeBSD src checkout will automatically create object
642 directories now rather than store files in the current directory if
643 'make obj' was not ran. Calling 'make obj' is no longer necessary.
644 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
645 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
649 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
650 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
651 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
652 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
653 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
654 The UNIFIED_OBJDIR option is a transitional feature that will be
655 removed for 12.0 release; please migrate to the new format for any
656 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
657 than hardcoding paths.
660 The native-xtools target no longer installs the files by default to the
661 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
662 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
665 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
666 options are changing from controlling the build if defined / undefined
667 to controlling the build with explicit 'yes' or 'no' values. They will
668 shift to WITH/WITHOUT options to match other options in the system.
671 libstand has turned into a private library for sys/boot use only.
672 It is no longer supported as a public interface outside of sys/boot.
675 The arm port has split armv6 into armv6 and armv7. armv7 is now
676 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
677 and are running a kernel from before r324363, you will need to add
678 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
681 When building multiple kernels using KERNCONF, non-existent KERNCONF
682 files will produce an error and buildkernel will fail. Previously
683 missing KERNCONF files silently failed giving no indication as to
684 why, only to subsequently discover during installkernel that the
685 desired kernel was never built in the first place.
688 The default serial number format for CTL LUNs has changed. This will
689 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
690 or iSCSI clients care about their LUNs' serial numbers. Users who
691 require serial number stability should hardcode serial numbers in
695 For 32-bit arm compiled for hard-float support, soft-floating point
696 binaries now always get their shared libraries from
697 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
698 /usr/libsoft also existed). Only users with a hard-float ld.so, but
699 soft-float everything else should be affected.
702 The geli password typed at boot is now hidden. To restore the previous
703 behavior, see geli(8) for configuration options.
706 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
707 sysctl values. Minor nit, but requires a rebuild of both world/kernel
711 "make check" behavior (made in ^/head@r295380) has been changed to
712 execute from a limited sandbox, as opposed to executing from
716 - The "beforecheck" and "aftercheck" targets are now specified.
717 - ${CHECKDIR} (added in commit noted above) has been removed.
718 - Legacy behavior can be enabled by setting
719 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
721 If the limited sandbox mode is enabled, "make check" will execute
722 "make distribution", then install, execute the tests, and clean up the
723 sandbox if successful.
725 The "make distribution" and "make install" targets are typically run as
726 root to set appropriate permissions and ownership at installation time.
727 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
728 environment if executing "make check" with limited sandbox mode using
729 an unprivileged user.
732 Since the switch to GPT disk labels, fsck for UFS/FFS has been
733 unable to automatically find alternate superblocks. As of r322297,
734 the information needed to find alternate superblocks has been
735 moved to the end of the area reserved for the boot block.
736 Filesystems created with a newfs of this vintage or later
737 will create the recovery information. If you have a filesystem
738 created prior to this change and wish to have a recovery block
739 created for your filesystem, you can do so by running fsck in
740 foreground mode (i.e., do not use the -p or -y options). As it
741 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
742 to which you should answer yes.
745 As of r321665, an NFSv4 server configuration that services
746 Kerberos mounts or clients that do not support the uid/gid in
747 owner/owner_group string capability, must explicitly enable
748 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
749 machine's /etc/rc.conf file.
752 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
753 Please see the 20141231 entry below for information about prerequisites
754 and upgrading, if you are not already using clang 3.5.0 or higher.
757 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
758 r-commands (rlogin, rsh, etc.) to be built with the base system.
761 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
762 a very major ABI incompatible change, so users of FreeBSD/powerpc must
763 be careful when performing source upgrades. It is best to run
764 'make installworld' from an alternate root system, either a live
765 CD/memory stick, or a temporary root partition. Additionally, all ports
766 must be recompiled. powerpc64 is largely unaffected, except in the case
767 of 32-bit compatibility. All 32-bit binaries will be affected.
770 Forward compatibility for the "ino64" project have been committed. This
771 will allow most new binaries to run on older kernels in a limited
772 fashion. This prevents many of the common foot-shooting actions in the
773 upgrade as well as the limited ability to roll back the kernel across
774 the ino64 upgrade. Complicated use cases may not work properly, though
775 enough simpler ones work to allow recovery in most situations.
778 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
779 if you require the GPL compiler.
782 The internal ABI used for communication between the NFS kernel modules
783 was changed by r320085, so __FreeBSD_version was bumped to
784 ensure all the NFS related modules are updated together.
787 The ABI of struct event was changed by extending the data
788 member to 64bit and adding ext fields. For upgrade, same
789 precautions as for the entry 20170523 "ino64" must be
793 The GNU roff toolchain has been removed from base. To render manpages
794 which are not supported by mandoc(1), man(1) can fallback on GNU roff
795 from ports (and recommends to install it).
796 To render roff(7) documents, consider using GNU roff from ports or the
797 heirloom doctools roff toolchain from ports via pkg install groff or
798 via pkg install heirloom-doctools.
801 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
802 smaller runtime footprint builds. This is useful for embedded systems
803 which only require one chipset support.
805 If you load it as a module, make sure this is in /boot/loader.conf:
809 This will load the HAL, all chip/RF backends and if_ath_pci.
810 If you have if_ath_pci in /boot/loader.conf, ensure it is after
811 if_ath or it will not load any HAL chipset support.
813 If you want to selectively load things (eg on ye cheape ARM/MIPS
814 platforms where RAM is at a premium) you should:
817 * load the chip modules in question
818 * load ath_rate, ath_dfs
820 * load if_ath_pci and/or if_ath_ahb depending upon your particular
821 bus bind type - this is where probe/attach is done.
823 For further comments/feedback, poke adrian@ .
826 The "ino64" 64-bit inode project has been committed, which extends
827 a number of types to 64 bits. Upgrading in place requires care and
828 adherence to the documented upgrade procedure.
830 If using a custom kernel configuration ensure that the
831 COMPAT_FREEBSD11 option is included (as during the upgrade the
832 system will be running the ino64 kernel with the existing world).
834 For the safest in-place upgrade begin by removing previous build
835 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
836 full procedure documented below under the heading "To rebuild
837 everything and install it on the current system." Specifically,
838 a reboot is required after installing the new kernel before
842 The NATM framework including the en(4), fatm(4), hatm(4), and
843 patm(4) devices has been removed. Consumers should plan a
844 migration before the end-of-life date for FreeBSD 11.
847 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
848 diff has not been implemented, if those are needed a newer version of
849 GNU diff is available via the diffutils package under the gdiff name.
852 As of r316810 for ipfilter, keep frags is no longer assumed when
853 keep state is specified in a rule. r316810 aligns ipfilter with
854 documentation in man pages separating keep frags from keep state.
855 This allows keep state to be specified without forcing keep frags
856 and allows keep frags to be specified independently of keep state.
857 To maintain previous behaviour, also specify keep frags with
858 keep state (as documented in ipf.conf.5).
861 arm64 builds now use the base system LLD 4.0.0 linker by default,
862 instead of requiring that the aarch64-binutils port or package be
863 installed. To continue using aarch64-binutils, set
864 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
867 The UDP optimization in entry 20160818 that added the sysctl
868 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
869 packets will no longer be treated as L3 broadcast packets.
872 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
873 use any explicitly assigned loopback address available in the jail
874 instead of using the first assigned address of the jail.
877 The ctl.ko module no longer implements the iSCSI target frontend:
878 cfiscsi.ko does instead.
880 If building cfiscsi.ko as a kernel module, the module can be loaded
881 via one of the following methods:
882 - `cfiscsi_load="YES"` in loader.conf(5).
883 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
884 - ctladm(8)/ctld(8), when compiled with iSCSI support
885 (`WITH_ISCSI=yes` in src.conf(5))
887 Please see cfiscsi(4) for more details.
890 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
891 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
892 same source (previously, the dependency of mmcsd.ko on mmc.ko was
893 missing, but mmcsd.ko now will refuse to load if it is incompatible
897 The syntax of ipfw(8) named states was changed to avoid ambiguity.
898 If you have used named states in the firewall rules, you need to modify
899 them after installworld and before rebooting. Now named states must
900 be prefixed with colon.
903 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
904 removed as the userland we provide cannot use them. The KMS version
905 (sys/dev/drm2) supports the same hardware.
908 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
909 Please see the 20141231 entry below for information about prerequisites
910 and upgrading, if you are not already using clang 3.5.0 or higher.
913 The code that provides support for ZFS .zfs/ directory functionality
914 has been reimplemented. It's not possible now to create a snapshot
915 by mkdir under .zfs/snapshot/. That should be the only user visible
919 EISA bus support has been removed. The WITH_EISA option is no longer
923 MCA bus support has been removed.
926 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
927 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
930 The EM_MULTIQUEUE kernel configuration option is deprecated now that
931 the em(4) driver conforms to iflib specifications.
934 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
935 IFLIB. If you have a custom kernel configuration that excludes em(4)
936 but you use igb(4), you need to re-add em(4) to your custom configuration.
939 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
940 Please see the 20141231 entry below for information about prerequisites
941 and upgrading, if you are not already using clang 3.5.0 or higher.
944 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
945 Please see the 20141231 entry below for information about prerequisites
946 and upgrading, if you are not already using clang 3.5.0 or higher.
949 The layout of the pmap structure has changed for powerpc to put the pmap
950 statistics at the front for all CPU variations. libkvm(3) and all tools
951 that link against it need to be recompiled.
954 isl(4) and cyapa(4) drivers now require a new driver,
955 chromebook_platform(4), to work properly on Chromebook-class hardware.
956 On other types of hardware the drivers may need to be configured using
957 device hints. Please see the corresponding manual pages for details.
960 The urtwn(4) driver was merged into rtwn(4) and now consists of
961 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
963 Also, firmware for RTL8188CE was renamed due to possible name
964 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
967 GNU rcs has been removed from base. It is available as packages:
968 - rcs: Latest GPLv3 GNU rcs version.
969 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
973 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
974 modules now requires that the kernel configuration contain the
975 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
978 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
979 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
982 Relocatable object files with the extension of .So have been renamed
983 to use an extension of .pico instead. The purpose of this change is
984 to avoid a name clash with shared libraries on case-insensitive file
985 systems. On those file systems, foo.So is the same file as foo.so.
988 GNU rcs has been turned off by default. It can (temporarily) be built
989 again by adding WITH_RCS knob in src.conf.
990 Otherwise, GNU rcs is available from packages:
991 - rcs: Latest GPLv3 GNU rcs version.
992 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
995 The backup_uses_rcs functionality has been removed from rc.subr.
998 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
999 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1000 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1001 QUEUE_MACRO_DEBUG behavior.
1004 r304787 changed some ioctl interfaces between the iSCSI userspace
1005 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1006 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1010 The UDP receive code has been updated to only treat incoming UDP
1011 packets that were addressed to an L2 broadcast address as L3
1012 broadcast packets. It is not expected that this will affect any
1013 standards-conforming UDP application. The new behaviour can be
1014 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1018 Remove the openbsd_poll system call.
1019 __FreeBSD_version has been bumped because of this.
1022 The stable/11 branch has been created from head@r302406.
1025 The libc stub for the pipe(2) system call has been replaced with
1026 a wrapper that calls the pipe2(2) system call and the pipe(2)
1027 system call is now only implemented by the kernels that include
1028 "options COMPAT_FREEBSD10" in their config file (this is the
1029 default). Users should ensure that this option is enabled in
1030 their kernel or upgrade userspace to r302092 before upgrading their
1034 CAM will now strip leading spaces from SCSI disks' serial numbers.
1035 This will affect users who create UFS filesystems on SCSI disks using
1036 those disk's diskid device nodes. For example, if /etc/fstab
1037 previously contained a line like
1038 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1039 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1040 transforms like gmirror may also be affected. ZFS users should
1044 The bitstring(3) API has been updated with new functionality and
1045 improved performance. But it is binary-incompatible with the old API.
1046 Objects built with the new headers may not be linked against objects
1047 built with the old headers.
1050 The brk and sbrk functions have been removed from libc on arm64.
1051 Binutils from ports has been updated to not link to these
1052 functions and should be updated to the latest version before
1053 installing a new libc.
1056 The armv6 port now defaults to hard float ABI. Limited support
1057 for running both hardfloat and soft float on the same system
1058 is available using the libraries installed with -DWITH_LIBSOFT.
1059 This has only been tested as an upgrade path for installworld
1060 and packages may fail or need manual intervention to run. New
1061 packages will be needed.
1063 To update an existing self-hosted armv6hf system, you must add
1064 TARGET_ARCH=armv6 on the make command line for both the build
1065 and the install steps.
1068 Kernel modules compiled outside of a kernel build now default to
1069 installing to /boot/modules instead of /boot/kernel. Many kernel
1070 modules built this way (such as those in ports) already overrode
1071 KMODDIR explicitly to install into /boot/modules. However,
1072 manually building and installing a module from /sys/modules will
1073 now install to /boot/modules instead of /boot/kernel.
1076 The CAM I/O scheduler has been committed to the kernel. There should be
1077 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1078 list of known rogues that claim support for this but actually corrupt
1079 data is believed to be complete, be on the lookout for data
1080 corruption. The known rogue list is believed to be complete:
1082 o Crucial MX100, M550 drives with MU01 firmware.
1083 o Micron M510 and M550 drives with MU01 firmware.
1084 o Micron M500 prior to MU07 firmware
1085 o Samsung 830, 840, and 850 all firmwares
1086 o FCCT M500 all firmwares
1088 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1089 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1090 updated firmware. Black listed drives will work correctly because these
1091 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1092 this list is the same as found in Linux, it's believed there are no
1093 other rogues in the market place. All other models from the above
1096 To be safe, if you are at all concerned, you can quirk each of your
1097 drives to prevent NCQ from being sent by setting:
1098 kern.cam.ada.X.quirks="0x2"
1099 in loader.conf. If the drive requires the 4k sector quirk, set the
1100 quirks entry to 0x3.
1103 The FAST_DEPEND build option has been removed and its functionality is
1104 now the one true way. The old mkdep(1) style of 'make depend' has
1105 been removed. See 20160311 for further details.
1108 Resource range types have grown from unsigned long to uintmax_t. All
1109 drivers, and anything using libdevinfo, need to be recompiled.
1112 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1113 builds. It no longer runs mkdep(1) during 'make depend', and the
1114 'make depend' stage can safely be skipped now as it is auto ran
1115 when building 'make all' and will generate all SRCS and DPSRCS before
1116 building anything else. Dependencies are gathered at compile time with
1117 -MF flags kept in separate .depend files per object file. Users should
1118 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1119 stale .depend files.
1122 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1123 kernel modules. Therefore, if you load any kernel modules at boot time,
1124 please install the boot loaders after you install the kernel, but before
1128 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1129 make installkernel KERNCONF=YOUR_KERNEL_HERE
1130 make -C sys/boot install
1131 <reboot in single user>
1133 Then follow the usual steps, described in the General Notes section,
1137 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1138 see the 20141231 entry below for information about prerequisites and
1139 upgrading, if you are not already using clang 3.5.0 or higher.
1142 The AIO subsystem is now a standard part of the kernel. The
1143 VFS_AIO kernel option and aio.ko kernel module have been removed.
1144 Due to stability concerns, asynchronous I/O requests are only
1145 permitted on sockets and raw disks by default. To enable
1146 asynchronous I/O requests on all file types, set the
1147 vfs.aio.enable_unsafe sysctl to a non-zero value.
1150 The ELF object manipulation tool objcopy is now provided by the
1151 ELF Tool Chain project rather than by GNU binutils. It should be a
1152 drop-in replacement, with the addition of arm64 support. The
1153 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1154 to obtain the GNU version if necessary.
1157 Building ZFS pools on top of zvols is prohibited by default. That
1158 feature has never worked safely; it's always been prone to deadlocks.
1159 Using a zvol as the backing store for a VM guest's virtual disk will
1160 still work, even if the guest is using ZFS. Legacy behavior can be
1161 restored by setting vfs.zfs.vol.recursive=1.
1164 The NONE and HPN patches has been removed from OpenSSH. They are
1165 still available in the security/openssh-portable port.
1168 With the addition of ypldap(8), a new _ypldap user is now required
1169 during installworld. "mergemaster -p" can be used to add the user
1170 prior to installworld, as documented in the handbook.
1173 The tftp loader (pxeboot) now uses the option root-path directive. As a
1174 consequence it no longer looks for a pxeboot.4th file on the tftp
1175 server. Instead it uses the regular /boot infrastructure as with the
1179 The code to start recording plug and play data into the modules has
1180 been committed. While the old tools will properly build a new kernel,
1181 a number of warnings about "unknown metadata record 4" will be produced
1182 for an older kldxref. To avoid such warnings, make sure to rebuild
1183 the kernel toolchain (or world). Make sure that you have r292078 or
1184 later when trying to build 292077 or later before rebuilding.
1187 Debug data files are now built by default with 'make buildworld' and
1188 installed with 'make installworld'. This facilitates debugging but
1189 requires more disk space both during the build and for the installed
1190 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1194 r291527 changed the internal interface between the nfsd.ko and
1195 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1196 __FreeBSD_version has been bumped because of this.
1199 Add support for unicode collation strings leads to a change of
1200 order of files listed by ls(1) for example. To get back to the old
1201 behaviour, set LC_COLLATE environment variable to "C".
1203 Databases administrators will need to reindex their databases given
1204 collation results will be different.
1206 Due to a bug in install(1) it is recommended to remove the ancient
1207 locales before running make installworld.
1209 rm -rf /usr/share/locale/*
1212 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1213 libcrypto.so.7 or libssl.so.7 must be recompiled.
1216 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1217 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1218 should be replaced with isp_2400 and isp_2500 modules respectively.
1221 The build previously allowed using 'make -n' to not recurse into
1222 sub-directories while showing what commands would be executed, and
1223 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1224 and 'make -N' will not.
1227 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1228 and etcupdate will now use this file. A custom sendmail.cf is now
1229 updated via this mechanism rather than via installworld. If you had
1230 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1231 want to remove the exclusion or change it to "always install".
1232 /etc/mail/sendmail.cf is now managed the same way regardless of
1233 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1234 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1237 Compatibility shims for legacy ATA device names have been removed.
1238 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1239 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1240 environment variables, /dev/ad* and /dev/ar* symbolic links.
1243 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1244 Please see the 20141231 entry below for information about prerequisites
1245 and upgrading, if you are not already using clang 3.5.0 or higher.
1248 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1249 and renamed from .symbols to .debug. This reduces the size requirements
1250 on the boot partition or file system and provides consistency with
1251 userland debug files.
1253 When using the supported kernel installation method the
1254 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1255 as is done with /boot/kernel.
1257 Developers wishing to maintain the historical behavior of installing
1258 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1261 The wireless drivers had undergone changes that remove the 'parent
1262 interface' from the ifconfig -l output. The rc.d network scripts
1263 used to check presence of a parent interface in the list, so old
1264 scripts would fail to start wireless networking. Thus, etcupdate(3)
1265 or mergemaster(8) run is required after kernel update, to update your
1266 rc.d scripts in /etc.
1269 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1270 These configurations are now automatically interpreted as
1271 'scrub fragment reassemble'.
1274 Kernel-loadable modules for the random(4) device are back. To use
1275 them, the kernel must have
1278 options RANDOM_LOADABLE
1280 kldload(8) can then be used to load random_fortuna.ko
1281 or random_yarrow.ko. Please note that due to the indirect
1282 function calls that the loadable modules need to provide,
1283 the build-in variants will be slightly more efficient.
1285 The random(4) kernel option RANDOM_DUMMY has been retired due to
1286 unpopularity. It was not all that useful anyway.
1289 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1290 Control over building the ELF Tool Chain tools is now provided by
1291 the WITHOUT_TOOLCHAIN knob.
1294 The polarity of Pulse Per Second (PPS) capture events with the
1295 uart(4) driver has been corrected. Prior to this change the PPS
1296 "assert" event corresponded to the trailing edge of a positive PPS
1297 pulse and the "clear" event was the leading edge of the next pulse.
1299 As the width of a PPS pulse in a typical GPS receiver is on the
1300 order of 1 millisecond, most users will not notice any significant
1301 difference with this change.
1303 Anyone who has compensated for the historical polarity reversal by
1304 configuring a negative offset equal to the pulse width will need to
1305 remove that workaround.
1308 The default group assigned to /dev/dri entries has been changed
1309 from 'wheel' to 'video' with the id of '44'. If you want to have
1310 access to the dri devices please add yourself to the video group
1313 # pw groupmod video -m $USER
1316 The menu.rc and loader.rc files will now be replaced during
1317 upgrades. Please migrate local changes to menu.rc.local and
1318 loader.rc.local instead.
1321 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1322 strings and strip have been removed. The src.conf(5) knob
1323 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1326 As ZFS requires more kernel stack pages than is the default on some
1327 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1328 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1330 Please consider using 'options KSTACK_PAGES=X' where X is greater
1331 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1334 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1335 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1336 default, i.e., they will not contain "::". For example, instead
1337 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1338 to have a more specific match, such as different map entries for
1339 IPv6:0:0 vs IPv6:0. This change requires that configuration
1340 data (including maps, files, classes, custom ruleset, etc.) must
1341 use the same format, so make certain such configuration data is
1342 upgrading. As a very simple check search for patterns like
1343 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1344 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1345 the cf option UseCompressedIPv6Addresses.
1348 The default kernel entropy-processing algorithm is now
1349 Fortuna, replacing Yarrow.
1351 Assuming you have 'device random' in your kernel config
1352 file, the configurations allow a kernel option to override
1353 this default. You may choose *ONE* of:
1355 options RANDOM_YARROW # Legacy /dev/random algorithm.
1356 options RANDOM_DUMMY # Blocking-only driver.
1358 If you have neither, you get Fortuna. For most people,
1359 read no further, Fortuna will give a /dev/random that works
1360 like it always used to, and the difference will be irrelevant.
1362 If you remove 'device random', you get *NO* kernel-processed
1363 entropy at all. This may be acceptable to folks building
1364 embedded systems, but has complications. Carry on reading,
1365 and it is assumed you know what you need.
1367 *PLEASE* read random(4) and random(9) if you are in the
1368 habit of tweaking kernel configs, and/or if you are a member
1369 of the embedded community, wanting specific and not-usual
1370 behaviour from your security subsystems.
1372 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1373 random', you will NOT have a functioning /dev/random, and
1374 many cryptographic features will not work, including SSH.
1375 You may also find strange behaviour from the random(3) set
1376 of library functions, in particular sranddev(3), srandomdev(3)
1377 and arc4random(3). The reason for this is that the KERN_ARND
1378 sysctl only returns entropy if it thinks it has some to
1379 share, and with RANDOM_DUMMY or no 'device random' this
1383 An additional fix for the issue described in the 20150614 sendmail
1384 entry below has been committed in revision 284717.
1387 FreeBSD's old make (fmake) has been removed from the system. It is
1388 available as the devel/fmake port or via pkg install fmake.
1391 The fix for the issue described in the 20150614 sendmail entry
1392 below has been committed in revision 284436. The work
1393 around described in that entry is no longer needed unless the
1394 default setting is overridden by a confDH_PARAMETERS configuration
1395 setting of '5' or pointing to a 512 bit DH parameter file.
1398 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1399 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1400 and devel/kyua to version 0.20+ and adjust any calling code to work
1401 with Kyuafile and kyua.
1404 The import of openssl to address the FreeBSD-SA-15:10.openssl
1405 security advisory includes a change which rejects handshakes
1406 with DH parameters below 768 bits. sendmail releases prior
1407 to 8.15.2 (not yet released), defaulted to a 512 bit
1408 DH parameter setting for client connections. To work around
1409 this interoperability, sendmail can be configured to use a
1410 2048 bit DH parameter by:
1412 1. Edit /etc/mail/`hostname`.mc
1413 2. If a setting for confDH_PARAMETERS does not exist or
1414 exists and is set to a string beginning with '5',
1415 replace it with '2'.
1416 3. If a setting for confDH_PARAMETERS exists and is set to
1417 a file path, create a new file with:
1418 openssl dhparam -out /path/to/file 2048
1419 4. Rebuild the .cf file:
1420 cd /etc/mail/; make; make install
1421 5. Restart sendmail:
1422 cd /etc/mail/; make restart
1424 A sendmail patch is coming, at which time this file will be
1428 Generation of legacy formatted entries have been disabled by default
1429 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1430 entries were converted to use the new format by default when the new,
1431 machine independent format have been added and supported since FreeBSD
1434 Please see the pwd_mkdb(8) manual page for further details.
1437 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1438 20141231 entry below for information about prerequisites and upgrading,
1439 if you are not already using 3.5.0 or higher.
1442 TI platform code switched to using vendor DTS files and this update
1443 may break existing systems running on Beaglebone, Beaglebone Black,
1446 - dtb files should be regenerated/reinstalled. Filenames are the
1447 same but content is different now
1448 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1449 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1450 addressing scheme is now pin 25 on /dev/gpioc3.
1451 - Pandaboard: /etc/ttys should be updated, serial console device is
1452 now /dev/ttyu2, not /dev/ttyu0
1455 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1456 If you need the GNU extension from groff soelim(1), install groff
1457 from package: pkg install groff, or via ports: textproc/groff.
1460 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1461 defined in symlink(7); previously symlinks were silently ignored.
1464 The const qualifier has been removed from iconv(3) to comply with
1465 POSIX. The ports tree is aware of this from r384038 onwards.
1468 Libraries specified by LIBADD in Makefiles must have a corresponding
1469 DPADD_<lib> variable to ensure correct dependencies. This is now
1470 enforced in src.libnames.mk.
1473 From legacy ata(4) driver was removed support for SATA controllers
1474 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1475 Kernel modules ataahci and ataadaptec were removed completely,
1476 replaced by ahci and mvs modules respectively.
1479 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1480 the 20141231 entry below for information about prerequisites and
1481 upgrading, if you are not already using 3.5.0 or higher.
1484 The 32-bit PowerPC kernel has been changed to a position-independent
1485 executable. This can only be booted with a version of loader(8)
1486 newer than January 31, 2015, so make sure to update both world and
1487 kernel before rebooting.
1490 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1491 but before r278950, the RNG was not seeded properly. Immediately
1492 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1493 ssh keys or openssl keys) that were generated w/ a kernel from that
1494 range. This does not affect programs that directly used /dev/random
1495 or /dev/urandom. All userland uses of arc4random(3) are affected.
1498 The autofs(4) ABI was changed in order to restore binary compatibility
1499 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1500 with the new kernel.
1503 The powerpc64 kernel has been changed to a position-independent
1504 executable. This can only be booted with a new version of loader(8),
1505 so make sure to update both world and kernel before rebooting.
1508 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1509 only release, no new features have been added. Please see the 20141231
1510 entry below for information about prerequisites and upgrading, if you
1511 are not already using 3.5.0.
1514 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1515 taken from the ELF Tool Chain project rather than GNU binutils. They
1516 should be drop-in replacements, with the addition of arm64 support.
1517 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1518 binutils tools, if necessary. See 20150805 for updated information.
1521 The default Unbound configuration now enables remote control
1522 using a local socket. Users who have already enabled the
1523 local_unbound service should regenerate their configuration
1524 by running "service local_unbound setup" as root.
1527 The GNU texinfo and GNU info pages have been removed.
1528 To be able to view GNU info pages please install texinfo from ports.
1531 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1533 As of this release, a prerequisite for building clang, llvm and lldb is
1534 a C++11 capable compiler and C++11 standard library. This means that to
1535 be able to successfully build the cross-tools stage of buildworld, with
1536 clang as the bootstrap compiler, your system compiler or cross compiler
1537 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1538 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1541 On any standard FreeBSD 10.x or 11.x installation, where clang and
1542 libc++ are on by default (that is, on x86 or arm), this should work out
1545 On 9.x installations where clang is enabled by default, e.g. on x86 and
1546 powerpc, libc++ will not be enabled by default, so libc++ should be
1547 built (with clang) and installed first. If both clang and libc++ are
1548 missing, build clang first, then use it to build libc++.
1550 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1551 the instructions for 9.x above.
1553 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1554 default, and do not build clang.
1556 Many embedded systems are resource constrained, and will not be able to
1557 build clang in a reasonable time, or in some cases at all. In those
1558 cases, cross building bootable systems on amd64 is a workaround.
1560 This new version of clang introduces a number of new warnings, of which
1561 the following are most likely to appear:
1565 This warns in two cases, for both C and C++:
1566 * When the code is trying to take the absolute value of an unsigned
1567 quantity, which is effectively a no-op, and almost never what was
1568 intended. The code should be fixed, if at all possible. If you are
1569 sure that the unsigned quantity can be safely cast to signed, without
1570 loss of information or undefined behavior, you can add an explicit
1571 cast, or disable the warning.
1573 * When the code is trying to take an absolute value, but the called
1574 abs() variant is for the wrong type, which can lead to truncation.
1575 If you want to disable the warning instead of fixing the code, please
1576 make sure that truncation will not occur, or it might lead to unwanted
1579 -Wtautological-undefined-compare and
1580 -Wundefined-bool-conversion
1582 These warn when C++ code is trying to compare 'this' against NULL, while
1583 'this' should never be NULL in well-defined C++ code. However, there is
1584 some legacy (pre C++11) code out there, which actively abuses this
1585 feature, which was less strictly defined in previous C++ versions.
1587 Squid and openjdk do this, for example. The warning can be turned off
1588 for C++98 and earlier, but compiling the code in C++11 mode might result
1589 in unexpected behavior; for example, the parts of the program that are
1590 unreachable could be optimized away.
1593 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1594 kernel sources have been removed. The .h files remain, since some
1595 utilities include them. This will need to be fixed later.
1596 If "mount -t oldnfs ..." is attempted, it will fail.
1597 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1598 the utilities will report errors.
1601 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1602 directories to top level SUBDIR variable when their parent
1603 directory is included in LOCAL_DIRS. Users with build systems with
1604 such hierarchies and without SUBDIR entries in the parent
1605 directory Makefiles should add them or add the directories to
1609 faith(4) and faithd(8) have been removed from the base system. Faith
1610 has been obsolete for a very long time.
1613 vt(4), the new console driver, is enabled by default. It brings
1614 support for Unicode and double-width characters, as well as
1615 support for UEFI and integration with the KMS kernel video
1618 You may need to update your console settings in /etc/rc.conf,
1619 most probably the keymap. During boot, /etc/rc.d/syscons will
1620 indicate what you need to do.
1622 vt(4) still has issues and lacks some features compared to
1623 syscons(4). See the wiki for up-to-date information:
1624 https://wiki.freebsd.org/Newcons
1626 If you want to keep using syscons(4), you can do so by adding
1627 the following line to /boot/loader.conf:
1631 pjdfstest has been integrated into kyua as an opt-in test suite.
1632 Please see share/doc/pjdfstest/README for more details on how to
1636 gperf has been removed from the base system for architectures
1637 that use clang. Ports that require gperf will obtain it from the
1641 pjdfstest has been moved from tools/regression/pjdfstest to
1645 At svn r271982, The default linux compat kernel ABI has been adjusted
1646 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1647 update. If you wish to continue using the linux-f10 compat ports,
1648 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1649 encouraged to update their linux-compat packages to linux-c6 during
1650 their next update cycle.
1653 The ofwfb driver, used to provide a graphics console on PowerPC when
1654 using vt(4), no longer allows mmap() of all physical memory. This
1655 will prevent Xorg on PowerPC with some ATI graphics cards from
1656 initializing properly unless x11-servers/xorg-server is updated to
1660 The xdev targets have been converted to using TARGET and
1661 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1664 The default unbound configuration has been modified to address
1665 issues with reverse lookups on networks that use private
1666 address ranges. If you use the local_unbound service, run
1667 "service local_unbound setup" as root to regenerate your
1668 configuration, then "service local_unbound reload" to load the
1672 The GNU texinfo and GNU info pages are not built and installed
1673 anymore, WITH_INFO knob has been added to allow to built and install
1675 UPDATE: see 20150102 entry on texinfo's removal
1678 The GNU readline library is now an INTERNALLIB - that is, it is
1679 statically linked into consumers (GDB and variants) in the base
1680 system, and the shared library is no longer installed. The
1681 devel/readline port is available for third party software that
1685 The Itanium architecture (ia64) has been removed from the list of
1686 known architectures. This is the first step in the removal of the
1690 Commit r268115 has added NFSv4.1 server support, merged from
1691 projects/nfsv4.1-server. Since this includes changes to the
1692 internal interfaces between the NFS related modules, a full
1693 build of the kernel and modules will be necessary.
1694 __FreeBSD_version has been bumped.
1697 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1698 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1699 which differs from the behaviour controlled by this knob.)
1702 Maximal length of the serial number in CTL was increased from 16 to
1703 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1704 and ctld, need to be rebuilt to work with a new kernel.
1707 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1708 1 respectively to match the upstream numbers. They were out of
1709 sync because, when they were originally added to FreeBSD, the
1710 upstream versions were not respected. These libraries are private
1711 and not yet built by default, so renumbering them should be a
1712 non-issue. However, unclean source trees will yield broken test
1713 programs once the operator executes "make delete-old-libs" after a
1714 "make installworld".
1716 Additionally, the atf-sh binary was made private by moving it into
1717 /usr/libexec/. Already-built shell test programs will keep the
1718 path to the old binary so they will break after "make delete-old"
1721 If you are using WITH_TESTS=yes (not the default), wipe the object
1722 tree and rebuild from scratch to prevent spurious test failures.
1723 This is only needed once: the misnumbered libraries and misplaced
1724 binaries have been added to OptionalObsoleteFiles.inc so they will
1725 be removed during a clean upgrade.
1728 Clang and llvm have been upgraded to 3.4.1 release.
1731 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1732 be removed to avoid issues in the future (and has been added to
1736 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1737 past, it affected all builds that used the bsd.*.mk files. The old
1738 behavior was a bug, but people may have relied upon it. To get this
1739 behavior back, you can .include /etc/src.conf from /etc/make.conf
1740 (which is still global and isn't changed). This also changes the
1741 behavior of incremental builds inside the tree of individual
1742 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1743 Although this has survived make universe and some upgrade scenarios,
1744 other upgrade scenarios may have broken. At least one form of
1745 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1746 as well... In cases where MAKESYSPATH isn't working with this
1747 setting, you'll need to set it to the full path to your tree.
1749 One side effect of all this cleaning up is that bsd.compiler.mk
1750 is no longer implicitly included by bsd.own.mk. If you wish to
1751 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1755 The lindev device has been removed since /dev/full has been made a
1756 standard device. __FreeBSD_version has been bumped.
1759 The knob WITHOUT_VI was added to the base system, which controls
1760 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1761 in order to reorder files share/termcap and didn't build ex(1) as a
1762 build tool, so building/installing with WITH_VI is highly advised for
1763 build hosts for older releases.
1765 This issue has been fixed in stable/9 and stable/10 in r277022 and
1766 r276991, respectively.
1769 The YES_HESIOD knob has been removed. It has been obsolete for
1770 a decade. Please move to using WITH_HESIOD instead or your builds
1771 will silently lack HESIOD.
1774 The uart(4) driver has been changed with respect to its handling
1775 of the low-level console. Previously the uart(4) driver prevented
1776 any process from changing the baudrate or the CLOCAL and HUPCL
1777 control flags. By removing the restrictions, operators can make
1778 changes to the serial console port without having to reboot.
1779 However, when getty(8) is started on the serial device that is
1780 associated with the low-level console, a misconfigured terminal
1781 line in /etc/ttys will now have a real impact.
1782 Before upgrading the kernel, make sure that /etc/ttys has the
1783 serial console device configured as 3wire without baudrate to
1784 preserve the previous behaviour. E.g:
1785 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1788 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1789 to improve performance. To re-enable it, if needed, run rpcbind
1790 with command line option -W.
1793 Switched back to the GPL dtc compiler due to updates in the upstream
1794 dts files not being supported by the BSDL dtc compiler. You will need
1795 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1796 may result while building dtb files during a kernel build if you fail
1797 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1800 Clang and llvm have been upgraded to 3.4 release.
1803 The nve(4) driver has been removed. Please use the nfe(4) driver
1804 for NVIDIA nForce MCP Ethernet adapters instead.
1807 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1808 This could cause certain C++ applications using shared libraries built
1809 against the previous version of libc++ to crash. The incompatibility
1810 has now been fixed, but any C++ applications or shared libraries built
1811 between r261283 and r261801 should be recompiled.
1814 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1815 capability mode support. Please note that enabling the feature in
1816 kernel is still highly recommended.
1819 OpenSSH is now built with sandbox support, and will use sandbox as
1820 the default privilege separation method. This requires Capsicum
1821 capability mode support in kernel.
1824 The libelf and libdwarf libraries have been updated to newer
1825 versions from upstream. Shared library version numbers for
1826 these two libraries were bumped. Any ports or binaries
1827 requiring these two libraries should be recompiled.
1828 __FreeBSD_version is bumped to 1100006.
1831 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1832 instead of providing an explicit one, this would prevent such
1833 Makefile from providing its own Kyuafile in the future during
1834 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1835 intervention is needed to clean an objdir if you use NO_CLEAN:
1836 # find /usr/obj -name Kyuafile | xargs rm -f
1839 The behavior of gss_pseudo_random() for the krb5 mechanism
1840 has changed, for applications requesting a longer random string
1841 than produced by the underlying enctype's pseudo-random() function.
1842 In particular, the random string produced from a session key of
1843 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1844 be different at the 17th octet and later, after this change.
1845 The counter used in the PRF+ construction is now encoded as a
1846 big-endian integer in accordance with RFC 4402.
1847 __FreeBSD_version is bumped to 1100004.
1850 The WITHOUT_ATF build knob has been removed and its functionality
1851 has been subsumed into the more generic WITHOUT_TESTS. If you were
1852 using the former to disable the build of the ATF libraries, you
1853 should change your settings to use the latter.
1856 The default version of mtree is nmtree which is obtained from
1857 NetBSD. The output is generally the same, but may vary
1858 slightly. If you found you need identical output adding
1859 "-F freebsd9" to the command line should do the trick. For the
1860 time being, the old mtree is available as fmtree.
1863 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1864 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1865 1.1.4_8 and verify bsdyml not linked in, before running "make
1867 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1869 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1872 The stable/10 branch has been created in subversion from head
1879 Avoid using make -j when upgrading. While generally safe, there are
1880 sometimes problems using -j to upgrade. If your upgrade fails with
1881 -j, please try again without -j. From time to time in the past there
1882 have been problems using -j with buildworld and/or installworld. This
1883 is especially true when upgrading between "distant" versions (eg one
1884 that cross a major release boundary or several minor releases, or when
1885 several months have passed on the -current branch).
1887 Sometimes, obscure build problems are the result of environment
1888 poisoning. This can happen because the make utility reads its
1889 environment when searching for values for global variables. To run
1890 your build attempts in an "environmental clean room", prefix all make
1891 commands with 'env -i '. See the env(1) manual page for more details.
1893 When upgrading from one major version to another it is generally best to
1894 upgrade to the latest code in the currently installed branch first, then
1895 do an upgrade to the new branch. This is the best-tested upgrade path,
1896 and has the highest probability of being successful. Please try this
1897 approach if you encounter problems with a major version upgrade. Since
1898 the stable 4.x branch point, one has generally been able to upgrade from
1899 anywhere in the most recent stable branch to head / current (or even the
1900 last couple of stable branches). See the top of this file when there's
1903 When upgrading a live system, having a root shell around before
1904 installing anything can help undo problems. Not having a root shell
1905 around can lead to problems if pam has changed too much from your
1906 starting point to allow continued authentication after the upgrade.
1908 This file should be read as a log of events. When a later event changes
1909 information of a prior event, the prior event should not be deleted.
1910 Instead, a pointer to the entry with the new information should be
1911 placed in the old entry. Readers of this file should also sanity check
1912 older entries before relying on them blindly. Authors of new entries
1913 should write them with this in mind.
1917 When upgrading the boot ZFS pool to a new version, always follow
1920 1.) recompile and reinstall the ZFS boot loader and boot block
1921 (this is part of "make buildworld" and "make installworld")
1923 2.) update the ZFS boot block on your boot drive
1925 The following example updates the ZFS boot block on the first
1926 partition (freebsd-boot) of a GPT partitioned drive ada0:
1927 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1929 Non-boot pools do not need these updates.
1933 If you are updating from a prior version of FreeBSD (even one just
1934 a few days old), you should follow this procedure. It is the most
1935 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1937 make kernel-toolchain
1938 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1939 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1941 To test a kernel once
1942 ---------------------
1943 If you just want to boot a kernel once (because you are not sure
1944 if it works, or if you want to boot a known bad kernel to provide
1945 debugging information) run
1946 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1947 nextboot -k testkernel
1949 To rebuild everything and install it on the current system.
1950 -----------------------------------------------------------
1951 # Note: sometimes if you are running current you gotta do more than
1952 # is listed here if you are upgrading from a really old current.
1954 <make sure you have good level 0 dumps>
1956 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1957 make installkernel KERNCONF=YOUR_KERNEL_HERE
1959 <reboot in single user> [3]
1966 To cross-install current onto a separate partition
1967 --------------------------------------------------
1968 # In this approach we use a separate partition to hold
1969 # current's root, 'usr', and 'var' directories. A partition
1970 # holding "/", "/usr" and "/var" should be about 2GB in
1973 <make sure you have good level 0 dumps>
1976 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1977 <maybe newfs current's root partition>
1978 <mount current's root partition on directory ${CURRENT_ROOT}>
1979 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1980 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1981 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1982 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1983 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1984 <reboot into current>
1985 <do a "native" rebuild/install as described in the previous section>
1986 <maybe install compatibility libraries from ports/misc/compat*>
1990 To upgrade in-place from stable to current
1991 ----------------------------------------------
1992 <make sure you have good level 0 dumps>
1994 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1995 make installkernel KERNCONF=YOUR_KERNEL_HERE
1997 <reboot in single user> [3]
2004 Make sure that you've read the UPDATING file to understand the
2005 tweaks to various things you need. At this point in the life
2006 cycle of current, things change often and you are on your own
2007 to cope. The defaults can also change, so please read ALL of
2008 the UPDATING entries.
2010 Also, if you are tracking -current, you must be subscribed to
2011 freebsd-current@freebsd.org. Make sure that before you update
2012 your sources that you have read and understood all the recent
2013 messages there. If in doubt, please track -stable which has
2014 much fewer pitfalls.
2016 [1] If you have third party modules, such as vmware, you
2017 should disable them at this point so they don't crash your
2020 [3] From the bootblocks, boot -s, and then do
2025 adjkerntz -i # if CMOS is wall time
2026 Also, when doing a major release upgrade, it is required that
2027 you boot into single user mode to do the installworld.
2029 [4] Note: This step is non-optional. Failure to do this step
2030 can result in a significant reduction in the functionality of the
2031 system. Attempting to do it by hand is not recommended and those
2032 that pursue this avenue should read this file carefully, as well
2033 as the archives of freebsd-current and freebsd-hackers mailing lists
2034 for potential gotchas. The -U option is also useful to consider.
2035 See mergemaster(8) for more information.
2037 [5] Usually this step is a no-op. However, from time to time
2038 you may need to do this if you get unknown user in the following
2039 step. It never hurts to do it all the time. You may need to
2040 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2041 install) after the buildworld before this step if you last updated
2042 from current before 20130425 or from -stable before 20130430.
2044 [6] This only deletes old files and directories. Old libraries
2045 can be deleted by "make delete-old-libs", but you have to make
2046 sure that no program is using those libraries anymore.
2048 [8] The new kernel must be able to run existing binaries used by
2049 an installworld. When upgrading across major versions, the new
2050 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2051 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2052 binaries). Failure to do so may leave you with a system that is
2053 hard to boot to recover. A GENERIC kernel will include suitable
2054 compatibility options to run binaries from older branches.
2056 Make sure that you merge any new devices from GENERIC since the
2057 last time you updated your kernel config file.
2059 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2060 "?=" instead of the "=" assignment operator, so that buildworld can
2061 override the CPUTYPE if it needs to.
2063 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2064 not on the command line, or in /etc/make.conf. buildworld will
2065 warn if it is improperly defined.
2068 This file contains a list, in reverse chronological order, of major
2069 breakages in tracking -current. It is not guaranteed to be a complete
2070 list of such breakages, and only contains entries since September 23, 2011.
2071 If you need to see UPDATING entries from before that date, you will need
2072 to fetch an UPDATING file from an older FreeBSD release.
2074 Copyright information:
2076 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2078 Redistribution, publication, translation and use, with or without
2079 modification, in full or in part, in any form or format of this
2080 document are permitted without further permission from the author.
2082 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2083 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2084 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2085 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2086 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2087 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2088 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2089 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2090 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2091 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2092 POSSIBILITY OF SUCH DAMAGE.
2094 Contact Warner Losh if you have any questions about your use of