1 Updating Information for FreeBSD stable/12 users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
22 20200915: p1 FreeBSD-SA-20:27.ure
23 FreeBSD-SA-20:28.bhyve_vmcs
24 FreeBSD-SA-20:29.bhyve_svm
27 Fix ure device driver susceptible to packet-in-packet attack.
30 Fix bhyve privilege escalation via VMCS access. [SA-20:28.bhyve_vmcs]
32 Fix bhyve SVM guest escape. [SA-20:29.bhyve_svm]
34 Fix ftpd privilege escalation via ftpchroot. [SA-20:30.ftpd]
37 The make.conf(5) MALLOC_PRODUCTION variable, used for disabling and
38 enabling assertions and statistics gathering in malloc(3), has been
39 migrated to a src.conf(5) WITH/WITHOUT_MALLOC_PRODUCTION option.
41 On stable branches, WITH_MALLOC_PRODUCTION is set by default, which
42 means that malloc(3) has assertions and statistics gathering disabled,
43 for improved performance.
45 For backwards compatibility, the make.conf(5) MALLOC_PRODUCTION is still
46 honored, but it is now deprecated and undocumented.
49 The resume code now notifies devd with the 'kernel' system
50 rather than the old 'kern' subsystem to be consistent with
51 other use. The old notification will be created as well, but
52 will be removed prior to FreeBSD 14.0.
55 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
56 been upgraded to 10.0.1. Please see the 20141231 entry below for
57 information about prerequisites and upgrading, if you are not already
58 using clang 3.5.0 or higher.
61 read(2) of a directory fd is now rejected by default. root may
62 re-enable it for the entire system with the
63 security.bsd.allow_read_dir sysctl(8) MIB.
65 It may be advised to setup aliases for grep to default to `-d skip` if
66 commonly non-recursively grepping a list that includes directories and
67 the potential for the resulting stderr output is not tolerable. Example
68 aliases are now installed, commented out, in /root/.cshrc.
71 Upstream DTS from Linux 5.6 was merged and they now have the SID
72 and THS (Secure ID controller and THermal Sensor) node present.
73 The DTB overlays have now been removed from the tree for the H3/H5 and
74 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
75 deal with upstream DTS. If you are using those overlays you need to
76 remove them from loader.conf and update the DTBs on the FAT partition.
79 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
80 been upgraded to 10.0.0. 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 root certificates of the Mozilla CA Certificate Store have been
86 imported into the base system and can be managed with the certctl(8)
87 utility. If you have installed the security/ca_root_nss port or package
88 with the ETCSYMLINK option (the default), be advised that there may be
89 differences between those included in the port and those included in
90 base due to differences in nss branch used as well as general update
91 frequency. Note also that certctl(8) cannot manage certs in the
92 format used by the security/ca_root_nss port.
95 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
96 been upgraded to 9.0.1. Please see the 20141231 entry below for
97 information about prerequisites and upgrading, if you are not already
98 using clang 3.5.0 or higher.
101 The nctgpio and wbwd drivers have been moved to the superio bus.
102 If you have one of these drivers in a kernel configuration, then
103 you should add device superio to it. If you use one of these drivers
104 as a module and you compile a custom set of modules, then you should
105 add superio to the set.
108 The tap(4) driver has been folded into tun(4), and the module has been
109 renamed to tuntap. You should update any kld_list="if_tap" or
110 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
111 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
112 module instead, and "device tap" or "device tun" entries in kernel
113 config files to select the tuntap device instead.
116 ntpd no longer by default locks its pages in memory, allowing them
117 to be paged out by the kernel. Use rlimit memlock to restore
118 historic BSD behaviour. For example, add "rlimit memlock 32"
119 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
122 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
123 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
124 been removed from mount_fusefs(8). You can safely remove them from
125 your scripts, because they had no effect.
127 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
128 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
129 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
130 sysctls have been removed. If you felt the need to set any of them to
131 a non-default value, please tell asomers@FreeBSD.org why.
134 The fuse(4) module has been renamed to fusefs(4) for consistency with
135 other filesystems. You should update any kld_load="fuse" entries in
136 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
137 "options FUSE" enties in kernel config files.
140 Default permissions on the /var/account/acct file (and copies of it
141 rotated by periodic daily scripts) are changed from 0644 to 0640
142 because the file contains sensitive information that should not be
143 world-readable. If the /var/account directory must be created by
144 rc.d/accounting, the mode used is now 0750. Admins who use the
145 accounting feature are encouraged to change the mode of an existing
146 /var/account directory to 0750 or 0700.
149 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
150 been upgraded to 8.0.1. Please see the 20141231 entry below for
151 information about prerequisites and upgrading, if you are not already
152 using clang 3.5.0 or higher.
155 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
156 functionality needed for the RETPOLINE option should work properly
157 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
160 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
161 8.0.0. Please see the 20141231 entry below for information about
162 prerequisites and upgrading, if you are not already using clang 3.5.0
166 The RETPOLINE option produces non-functional ifunc-using binaries
167 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
168 Once Clang 8 is merged it may be enabled again.
171 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
172 7.0.1. Please see the 20141231 entry below for information about
173 prerequisites and upgrading, if you are not already using clang 3.5.0
177 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
178 compiled into your custom kernel, add 'device xz' statement to the
182 Iflib is no longer unconditionally compiled into the kernel. Drivers
183 using iflib and statically compiled into the kernel, now require
184 the 'device iflib' config option. For the same drivers loaded as
185 modules on kernels not having 'device iflib', the iflib.ko module
186 is loaded automatically.
189 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
190 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
191 servers that have vfs.nfsd.nfs_privport set will only allow mounts
192 from clients using a reserved port#. Since both the FreeBSD and Linux
193 NFSv4 clients use reserved port#s by default, this should not affect
197 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
198 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
199 it produces broken binaries when ifuncs are in use. Users needing
200 GNU ld should install the binutils port or package.
203 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
204 has been converted to a port (misc/ctm) and will be removed from
205 FreeBSD-13. A depreciation warning will be printed to stderr by
206 the ctm command, but the functionality will remain in base for all
210 The stable/12 branch has been created in subversion from head
214 Ports for the DRM modules have been simplified. Now, amd64 users should
215 just install the drm-kmod port. All others should install
218 Graphics hardware that's newer than about 2010 usually works with
219 drm-kmod. For hardware older than 2013, however, some users will need
220 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
221 than 2008 usually only works in drm-legacy-kmod. The graphics team can
222 only commit to hardware made since 2013 due to the complexity of the
223 market and difficulty to test all the older cards effectively. If you
224 have hardware supported by drm-kmod, you are strongly encouraged to use
225 that as you will get better support.
227 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
228 elsewhere, the drm and drm2 modules will be eliminated from the src base
229 soon (with a limited exception for arm). Please update to the package asap
230 and report any issues to x11@freebsd.org.
232 Generally, anybody using the drm*-kmod packages should add
233 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
234 cross-threading surprises, especially with automatic driver
235 loading from X11 startup. These will become the defaults in 13-current
239 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
240 custom kernel and module loading configuration files must be updated
241 accordingly. Moreover, interfaces previous presented as ixlvN to the
242 system are now exposed as iavfN and network configuration files must
243 be adjusted as necessary.
246 OpenSSL has been updated to version 1.1.1. This update included
247 additional various API changes througout the base system. It is
248 important to rebuild third-party software after upgrading. The value
249 of __FreeBSD_version has been bumped accordingly.
252 The legacy DRM modules and drivers have now been added to the loader's
253 module blacklist, in favor of loading them with kld_list in rc.conf(5).
254 The module blacklist may be overridden with the loader.conf(5)
255 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
259 The cam(4) based nda(4) driver will be used over nvd(4) by default on
260 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
261 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
262 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
266 Reproducible build mode is now on by default, in preparation for
267 FreeBSD 12.0. This eliminates build metadata such as the user,
268 host, and time from the kernel (and uname), unless the working tree
269 corresponds to a modified checkout from a version control system.
270 The previous behavior can be obtained by setting the /etc/src.conf
271 knob WITHOUT_REPRODUCIBLE_BUILD.
274 The Yarrow CSPRNG has been removed from the kernel as it has not been
275 supported by its designers since at least 2003. Fortuna has been the
276 default since FreeBSD-11.
279 devctl freeze/thaw have gone into the tree, the rc scripts have been
280 updated to use them and devmatch has been changed. You should update
281 kernel, userland and rc scripts all at the same time.
284 The default interpreter has been switched from 4th to Lua.
285 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
286 interpreter. If you have custom FORTH code you will need to set
287 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
288 src.conf for the build. This will create default hard links between
289 loader and loader_4th instead of loader and loader_lua, the new default.
290 If you are using UEFI it will create the proper hard link to loader.efi.
292 bhyve uses userboot.so. It remains 4th-only until some issues are solved
293 regarding coexisting with multiple versions of FreeBSD are resolved.
296 ls(1) now respects the COLORTERM environment variable used in other
297 systems and software to indicate that a colored terminal is both
298 supported and desired. If ls(1) is suddenly emitting colors, they may
299 be disabled again by either removing the unwanted COLORTERM from your
300 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
301 may not be observed in a future release.
304 The default pager for most commands has been changed to "less". To
305 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
309 The jedec_ts(4) driver has been removed. A superset of its functionality
310 is available in the jedec_dimm(4) driver, and the manpage for that
311 driver includes migration instructions. If you have "device jedec_ts"
312 in your kernel configuration file, it must be removed.
315 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
316 This should have no effect if the kernel is booted via BIOS/legacy boot.
317 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
318 has a buggy firmware that prevents a successful boot due to use of
322 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
323 support has been removed from the tree. These ports were
324 obsolete and/or known to be broken for many years.
327 loader.efi has been augmented to participate more fully in the
328 UEFI boot manager protocol. loader.efi will now look at the
329 BootXXXX environment variable to determine if a specific kernel
330 or root partition was specified. XXXX is derived from BootCurrent.
331 efibootmgr(8) manages these standard UEFI variables.
334 zfsloader's functionality has now been folded into loader.
335 zfsloader is no longer necessary once you've updated your
336 boot blocks. For a transition period, we will install a
337 hardlink for zfsloader to loader to allow a smooth transition
338 until the boot blocks can be updated (hard link because old
339 zfs boot blocks don't understand symlinks).
342 ARM64 now have efifb support, if you want to have serial console
343 on your arm64 board when an screen is connected and the bootloader
344 setup a frambuffer for us to use, just add :
348 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
349 an screen connected as the firmware will setup a framebuffer are that
350 u-boot will expose as an EFI framebuffer.
353 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
354 or take steps to update /etc/passwd before doing installworld on
355 existing systems. Do not skip the "mergemaster -Fp" step before
356 installworld, as described in the update procedures near the bottom
357 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
358 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
359 the ntp config file contain options that change file/dir locations.
360 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
361 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
362 taking steps to ensure that all required files/dirs are accessible
366 Big endian arm support has been removed.
369 The static environment setup in kernel configs is no longer mutually
370 exclusive with the loader(8) environment by default. In order to
371 restore the previous default behavior of disabling the loader(8)
372 environment if a static environment is present, you must specify
373 loader_env.disabled=1 in the static environment.
376 The ABI of syscalls used by management tools like sockstat and
377 netstat has been broken to allow 32-bit binaries to work on
378 64-bit kernels without modification. These programs will need
379 to match the kernel in order to function. External programs may
380 require minor modifications to accommodate a change of type in
381 structures from pointers to 64-bit virtual addresses.
384 On i386 and amd64 atomics are now inlined. Out of tree modules using
385 atomics will need to be rebuilt.
388 The '%I' format in the kern.corefile sysctl limits the number of
389 core files that a process can generate to the number stored in the
390 debug.ncores sysctl. The '%I' format is replaced by the single digit
391 index. Previously, if all indexes were taken the kernel would overwrite
392 only a core file with the highest index in a filename.
393 Currently the system will create a new core file if there is a free
394 index or if all slots are taken it will overwrite the oldest one.
397 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
398 6.0.1. Please see the 20141231 entry below for information about
399 prerequisites and upgrading, if you are not already using clang 3.5.0
403 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
404 needed to be changed to work with it. This change was made with r335763
405 and requires a mergemaster / etcupdate / etc to update the installed file.
408 r334930 changed the interface between the NFS modules, so they all
409 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
412 As of r334391 lld is the default amd64 system linker; it is installed
413 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
417 The kernel / userland interface for devinfo changed, so you'll
418 need a new kernel and userland as a pair for it to work (rebuilding
419 lib/libdevinfo is all that's required). devinfo and devmatch will
420 not work, but everything else will when there's a mismatch.
423 The on-disk format for hwpmc callchain records has changed to include
424 threadid corresponding to a given record. This changes the field offsets
425 and thus requires that libpmcstat be rebuilt before using a kernel
429 The vxge(4) driver has been removed. This driver was introduced into
430 HEAD one week before the Exar left the Ethernet market and is not
431 known to be used. If you have device vxge in your kernel config file
435 The amd64 kernel now requires a ld that supports ifunc to produce a
436 working kernel, either lld or a newer binutils. lld is built by default
437 on amd64, and the 'buildkernel' target uses it automatically. However,
438 it is not the default linker, so building the kernel the traditional
439 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
440 binutils port/package). lld will soon be default, and this requirement
443 NOTE: As of r334391 lld is the default system linker on amd64, and no
444 workaround is necessary.
447 The nxge(4) driver has been removed. This driver was for PCI-X 10g
448 cards made by s2io/Neterion. The company was aquired by Exar and
449 no longer sells or supports Ethernet products. If you have device
450 nxge in your kernel config file it must be removed.
453 The tz database (tzdb) has been updated to 2018e. This version more
454 correctly models time stamps in time zones with negative DST such as
455 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
456 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
457 time zone abbreviations and the tm_isdst flag.
460 The ixgb(4) driver has been removed. This driver was for an early and
461 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
462 quickly shifted to the long lived ixgbe family. If you have device
463 ixgb in your kernel config file it must be removed.
466 The lmc(4) driver has been removed. This was a WAN interface
467 card that was already reportedly rare in 2003, and had an ambiguous
468 license. If you have device lmc in your kernel config file it must
472 Support for Arcnet networks has been removed. If you have device
473 arcnet or device cm in your kernel config file they must be
477 Support for FDDI networks has been removed. If you have device
478 fddi or device fpa in your kernel config file they must be
482 In addition to supporting RFC 3164 formatted messages, the
483 syslogd(8) service is now capable of parsing RFC 5424 formatted
484 log messages. The main benefit of using RFC 5424 is that clients
485 may now send log messages with timestamps containing year numbers,
486 microseconds and time zone offsets.
488 Similarly, the syslog(3) C library function has been altered to
489 send RFC 5424 formatted messages to the local system logging
490 daemon. On systems using syslogd(8), this change should have no
491 negative impact, as long as syslogd(8) and the C library are
492 updated at the same time. On systems using a different system
493 logging daemon, it may be necessary to make configuration
494 adjustments, depending on the software used.
496 When using syslog-ng, add the 'syslog-protocol' flag to local
497 input sources to enable parsing of RFC 5424 formatted messages:
500 unix-dgram("/var/run/log" flags(syslog-protocol));
503 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
504 of the 'imuxsock' module to let messages be processed by the
505 regular RFC 3164/5424 parsing pipeline:
507 module(load="imuxsock" SysSock.UseSpecialParser="off")
509 Do note that these changes only affect communication between local
510 applications and syslogd(8). The format that syslogd(8) uses to
511 store messages on disk or forward messages to other systems
512 remains unchanged. syslogd(8) still uses RFC 3164 for these
513 purposes. Options to customize this behaviour will be added in the
514 future. Utilities that process log files stored in /var/log are
515 thus expected to continue to function as before.
517 __FreeBSD_version has been incremented to 1200061 to denote this
521 Support for token ring networks has been removed. If you
522 have "device token" in your kernel config you should remove
523 it. No device drivers supported token ring.
526 makefs was modified to be able to tag ISO9660 El Torito boot catalog
527 entries as EFI instead of overloading the i386 tag as done previously.
528 The amd64 mkisoimages.sh script used to build amd64 ISO images for
529 release was updated to use this. This may mean that makefs must be
530 updated before "make cdrom" can be run in the release directory. This
531 should be as simple as:
533 $ cd $SRCDIR/usr.sbin/makefs
534 $ make depend all install
537 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
538 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
539 Co-existance for the transition period will come shortly. Booting is a
540 complex environment and test coverage for Lua-enabled loaders has been
541 thin, so it would be prudent to assume it might not work and make
542 provisions for backup boot methods.
545 devmatch functionality has been turned on in devd. It will automatically
546 load drivers for unattached devices. This may cause unexpected drivers to
547 be loaded. Please report any problems to current@ and imp@freebsd.org.
550 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
551 6.0.0. Please see the 20141231 entry below for information about
552 prerequisites and upgrading, if you are not already using clang 3.5.0
556 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
557 This means it is used to link the kernel and userland libraries and
558 executables, but is not yet installed as /usr/bin/ld by default.
560 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
561 WITHOUT_LLD_BOOTSTRAP=yes
564 On i386, pmtimer has been removed. Its functionality has been folded
565 into apm. It was a no-op on ACPI in current for a while now (but was still
566 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
567 from kernel config files.
570 The use of RSS hash from the network card aka flowid has been
571 disabled by default for lagg(4) as it's currently incompatible with
572 the lacp and loadbalance protocols.
574 This can be re-enabled by setting the following in loader.conf:
575 net.link.lagg.default_use_flowid="1"
578 The SW_WATCHDOG option is no longer necessary to enable the
579 hardclock-based software watchdog if no hardware watchdog is
580 configured. As before, SW_WATCHDOG will cause the software
581 watchdog to be enabled even if a hardware watchdog is configured.
584 r326887 fixes the issue described in the 20171214 UPDATING entry.
585 r326888 flips the switch back to building GELI support always.
588 r362593 broke ZFS + GELI support for reasons unknown. However,
589 it also broke ZFS support generally, so GELI has been turned off
590 by default as the lesser evil in r326857. If you boot off ZFS and/or
591 GELI, it might not be a good time to update.
594 PowerPC users must update loader(8) by rebuilding world before
595 installing a new kernel, as the protocol connecting them has
596 changed. Without the update, loader metadata will not be passed
597 successfully to the kernel and users will have to enter their
598 root partition at the kernel mountroot prompt to continue booting.
599 Newer versions of loader can boot old kernels without issue.
602 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
603 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
604 to WITH/OUT_LOADER_GELI.
607 The naive and non-compliant support of posix_fallocate(2) in ZFS
608 has been removed as of r325320. The system call now returns EINVAL
609 when used on a ZFS file. Although the new behavior complies with the
610 standard, some consumers are not prepared to cope with it.
611 One known victim is lld prior to r325420.
614 Building in a FreeBSD src checkout will automatically create object
615 directories now rather than store files in the current directory if
616 'make obj' was not ran. Calling 'make obj' is no longer necessary.
617 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
618 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
622 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
623 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
624 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
625 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
626 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
627 The UNIFIED_OBJDIR option is a transitional feature that will be
628 removed for 12.0 release; please migrate to the new format for any
629 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
630 than hardcoding paths.
633 The native-xtools target no longer installs the files by default to the
634 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
635 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
638 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
639 options are changing from controlling the build if defined / undefined
640 to controlling the build with explicit 'yes' or 'no' values. They will
641 shift to WITH/WITHOUT options to match other options in the system.
644 libstand has turned into a private library for sys/boot use only.
645 It is no longer supported as a public interface outside of sys/boot.
648 The arm port has split armv6 into armv6 and armv7. armv7 is now
649 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
650 and are running a kernel from before r324363, you will need to add
651 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
654 When building multiple kernels using KERNCONF, non-existent KERNCONF
655 files will produce an error and buildkernel will fail. Previously
656 missing KERNCONF files silently failed giving no indication as to
657 why, only to subsequently discover during installkernel that the
658 desired kernel was never built in the first place.
661 The default serial number format for CTL LUNs has changed. This will
662 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
663 or iSCSI clients care about their LUNs' serial numbers. Users who
664 require serial number stability should hardcode serial numbers in
668 For 32-bit arm compiled for hard-float support, soft-floating point
669 binaries now always get their shared libraries from
670 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
671 /usr/libsoft also existed). Only users with a hard-float ld.so, but
672 soft-float everything else should be affected.
675 The geli password typed at boot is now hidden. To restore the previous
676 behavior, see geli(8) for configuration options.
679 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
680 sysctl values. Minor nit, but requires a rebuild of both world/kernel
684 "make check" behavior (made in ^/head@r295380) has been changed to
685 execute from a limited sandbox, as opposed to executing from
689 - The "beforecheck" and "aftercheck" targets are now specified.
690 - ${CHECKDIR} (added in commit noted above) has been removed.
691 - Legacy behavior can be enabled by setting
692 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
694 If the limited sandbox mode is enabled, "make check" will execute
695 "make distribution", then install, execute the tests, and clean up the
696 sandbox if successful.
698 The "make distribution" and "make install" targets are typically run as
699 root to set appropriate permissions and ownership at installation time.
700 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
701 environment if executing "make check" with limited sandbox mode using
702 an unprivileged user.
705 Since the switch to GPT disk labels, fsck for UFS/FFS has been
706 unable to automatically find alternate superblocks. As of r322297,
707 the information needed to find alternate superblocks has been
708 moved to the end of the area reserved for the boot block.
709 Filesystems created with a newfs of this vintage or later
710 will create the recovery information. If you have a filesystem
711 created prior to this change and wish to have a recovery block
712 created for your filesystem, you can do so by running fsck in
713 foreground mode (i.e., do not use the -p or -y options). As it
714 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
715 to which you should answer yes.
718 As of r321665, an NFSv4 server configuration that services
719 Kerberos mounts or clients that do not support the uid/gid in
720 owner/owner_group string capability, must explicitly enable
721 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
722 machine's /etc/rc.conf file.
725 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
726 Please see the 20141231 entry below for information about prerequisites
727 and upgrading, if you are not already using clang 3.5.0 or higher.
730 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
731 r-commands (rlogin, rsh, etc.) to be built with the base system.
734 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
735 a very major ABI incompatible change, so users of FreeBSD/powerpc must
736 be careful when performing source upgrades. It is best to run
737 'make installworld' from an alternate root system, either a live
738 CD/memory stick, or a temporary root partition. Additionally, all ports
739 must be recompiled. powerpc64 is largely unaffected, except in the case
740 of 32-bit compatibility. All 32-bit binaries will be affected.
743 Forward compatibility for the "ino64" project have been committed. This
744 will allow most new binaries to run on older kernels in a limited
745 fashion. This prevents many of the common foot-shooting actions in the
746 upgrade as well as the limited ability to roll back the kernel across
747 the ino64 upgrade. Complicated use cases may not work properly, though
748 enough simpler ones work to allow recovery in most situations.
751 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
752 if you require the GPL compiler.
755 The internal ABI used for communication between the NFS kernel modules
756 was changed by r320085, so __FreeBSD_version was bumped to
757 ensure all the NFS related modules are updated together.
760 The ABI of struct event was changed by extending the data
761 member to 64bit and adding ext fields. For upgrade, same
762 precautions as for the entry 20170523 "ino64" must be
766 The GNU roff toolchain has been removed from base. To render manpages
767 which are not supported by mandoc(1), man(1) can fallback on GNU roff
768 from ports (and recommends to install it).
769 To render roff(7) documents, consider using GNU roff from ports or the
770 heirloom doctools roff toolchain from ports via pkg install groff or
771 via pkg install heirloom-doctools.
774 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
775 smaller runtime footprint builds. This is useful for embedded systems
776 which only require one chipset support.
778 If you load it as a module, make sure this is in /boot/loader.conf:
782 This will load the HAL, all chip/RF backends and if_ath_pci.
783 If you have if_ath_pci in /boot/loader.conf, ensure it is after
784 if_ath or it will not load any HAL chipset support.
786 If you want to selectively load things (eg on ye cheape ARM/MIPS
787 platforms where RAM is at a premium) you should:
790 * load the chip modules in question
791 * load ath_rate, ath_dfs
793 * load if_ath_pci and/or if_ath_ahb depending upon your particular
794 bus bind type - this is where probe/attach is done.
796 For further comments/feedback, poke adrian@ .
799 The "ino64" 64-bit inode project has been committed, which extends
800 a number of types to 64 bits. Upgrading in place requires care and
801 adherence to the documented upgrade procedure.
803 If using a custom kernel configuration ensure that the
804 COMPAT_FREEBSD11 option is included (as during the upgrade the
805 system will be running the ino64 kernel with the existing world).
807 For the safest in-place upgrade begin by removing previous build
808 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
809 full procedure documented below under the heading "To rebuild
810 everything and install it on the current system." Specifically,
811 a reboot is required after installing the new kernel before
815 The NATM framework including the en(4), fatm(4), hatm(4), and
816 patm(4) devices has been removed. Consumers should plan a
817 migration before the end-of-life date for FreeBSD 11.
820 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
821 diff has not been implemented, if those are needed a newer version of
822 GNU diff is available via the diffutils package under the gdiff name.
825 As of r316810 for ipfilter, keep frags is no longer assumed when
826 keep state is specified in a rule. r316810 aligns ipfilter with
827 documentation in man pages separating keep frags from keep state.
828 This allows keep state to be specified without forcing keep frags
829 and allows keep frags to be specified independently of keep state.
830 To maintain previous behaviour, also specify keep frags with
831 keep state (as documented in ipf.conf.5).
834 arm64 builds now use the base system LLD 4.0.0 linker by default,
835 instead of requiring that the aarch64-binutils port or package be
836 installed. To continue using aarch64-binutils, set
837 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
840 The UDP optimization in entry 20160818 that added the sysctl
841 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
842 packets will no longer be treated as L3 broadcast packets.
845 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
846 use any explicitly assigned loopback address available in the jail
847 instead of using the first assigned address of the jail.
850 The ctl.ko module no longer implements the iSCSI target frontend:
851 cfiscsi.ko does instead.
853 If building cfiscsi.ko as a kernel module, the module can be loaded
854 via one of the following methods:
855 - `cfiscsi_load="YES"` in loader.conf(5).
856 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
857 - ctladm(8)/ctld(8), when compiled with iSCSI support
858 (`WITH_ISCSI=yes` in src.conf(5))
860 Please see cfiscsi(4) for more details.
863 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
864 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
865 same source (previously, the dependency of mmcsd.ko on mmc.ko was
866 missing, but mmcsd.ko now will refuse to load if it is incompatible
870 The syntax of ipfw(8) named states was changed to avoid ambiguity.
871 If you have used named states in the firewall rules, you need to modify
872 them after installworld and before rebooting. Now named states must
873 be prefixed with colon.
876 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
877 removed as the userland we provide cannot use them. The KMS version
878 (sys/dev/drm2) supports the same hardware.
881 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
882 Please see the 20141231 entry below for information about prerequisites
883 and upgrading, if you are not already using clang 3.5.0 or higher.
886 The code that provides support for ZFS .zfs/ directory functionality
887 has been reimplemented. It's not possible now to create a snapshot
888 by mkdir under .zfs/snapshot/. That should be the only user visible
892 EISA bus support has been removed. The WITH_EISA option is no longer
896 MCA bus support has been removed.
899 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
900 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
903 The EM_MULTIQUEUE kernel configuration option is deprecated now that
904 the em(4) driver conforms to iflib specifications.
907 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
908 IFLIB. If you have a custom kernel configuration that excludes em(4)
909 but you use igb(4), you need to re-add em(4) to your custom configuration.
912 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
913 Please see the 20141231 entry below for information about prerequisites
914 and upgrading, if you are not already using clang 3.5.0 or higher.
917 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
918 Please see the 20141231 entry below for information about prerequisites
919 and upgrading, if you are not already using clang 3.5.0 or higher.
922 The layout of the pmap structure has changed for powerpc to put the pmap
923 statistics at the front for all CPU variations. libkvm(3) and all tools
924 that link against it need to be recompiled.
927 isl(4) and cyapa(4) drivers now require a new driver,
928 chromebook_platform(4), to work properly on Chromebook-class hardware.
929 On other types of hardware the drivers may need to be configured using
930 device hints. Please see the corresponding manual pages for details.
933 The urtwn(4) driver was merged into rtwn(4) and now consists of
934 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
936 Also, firmware for RTL8188CE was renamed due to possible name
937 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
940 GNU rcs has been removed from base. It is available as packages:
941 - rcs: Latest GPLv3 GNU rcs version.
942 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
946 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
947 modules now requires that the kernel configuration contain the
948 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
951 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
952 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
955 Relocatable object files with the extension of .So have been renamed
956 to use an extension of .pico instead. The purpose of this change is
957 to avoid a name clash with shared libraries on case-insensitive file
958 systems. On those file systems, foo.So is the same file as foo.so.
961 GNU rcs has been turned off by default. It can (temporarily) be built
962 again by adding WITH_RCS knob in src.conf.
963 Otherwise, GNU rcs is available from packages:
964 - rcs: Latest GPLv3 GNU rcs version.
965 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
968 The backup_uses_rcs functionality has been removed from rc.subr.
971 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
972 two separate components, QUEUE_MACRO_DEBUG_TRACE and
973 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
974 QUEUE_MACRO_DEBUG behavior.
977 r304787 changed some ioctl interfaces between the iSCSI userspace
978 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
979 rebuilt to work with new kernels. __FreeBSD_version has been bumped
983 The UDP receive code has been updated to only treat incoming UDP
984 packets that were addressed to an L2 broadcast address as L3
985 broadcast packets. It is not expected that this will affect any
986 standards-conforming UDP application. The new behaviour can be
987 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
991 Remove the openbsd_poll system call.
992 __FreeBSD_version has been bumped because of this.
995 The stable/11 branch has been created from head@r302406.
998 The libc stub for the pipe(2) system call has been replaced with
999 a wrapper that calls the pipe2(2) system call and the pipe(2)
1000 system call is now only implemented by the kernels that include
1001 "options COMPAT_FREEBSD10" in their config file (this is the
1002 default). Users should ensure that this option is enabled in
1003 their kernel or upgrade userspace to r302092 before upgrading their
1007 CAM will now strip leading spaces from SCSI disks' serial numbers.
1008 This will affect users who create UFS filesystems on SCSI disks using
1009 those disk's diskid device nodes. For example, if /etc/fstab
1010 previously contained a line like
1011 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1012 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1013 transforms like gmirror may also be affected. ZFS users should
1017 The bitstring(3) API has been updated with new functionality and
1018 improved performance. But it is binary-incompatible with the old API.
1019 Objects built with the new headers may not be linked against objects
1020 built with the old headers.
1023 The brk and sbrk functions have been removed from libc on arm64.
1024 Binutils from ports has been updated to not link to these
1025 functions and should be updated to the latest version before
1026 installing a new libc.
1029 The armv6 port now defaults to hard float ABI. Limited support
1030 for running both hardfloat and soft float on the same system
1031 is available using the libraries installed with -DWITH_LIBSOFT.
1032 This has only been tested as an upgrade path for installworld
1033 and packages may fail or need manual intervention to run. New
1034 packages will be needed.
1036 To update an existing self-hosted armv6hf system, you must add
1037 TARGET_ARCH=armv6 on the make command line for both the build
1038 and the install steps.
1041 Kernel modules compiled outside of a kernel build now default to
1042 installing to /boot/modules instead of /boot/kernel. Many kernel
1043 modules built this way (such as those in ports) already overrode
1044 KMODDIR explicitly to install into /boot/modules. However,
1045 manually building and installing a module from /sys/modules will
1046 now install to /boot/modules instead of /boot/kernel.
1049 The CAM I/O scheduler has been committed to the kernel. There should be
1050 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1051 list of known rogues that claim support for this but actually corrupt
1052 data is believed to be complete, be on the lookout for data
1053 corruption. The known rogue list is believed to be complete:
1055 o Crucial MX100, M550 drives with MU01 firmware.
1056 o Micron M510 and M550 drives with MU01 firmware.
1057 o Micron M500 prior to MU07 firmware
1058 o Samsung 830, 840, and 850 all firmwares
1059 o FCCT M500 all firmwares
1061 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1062 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1063 updated firmware. Black listed drives will work correctly because these
1064 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1065 this list is the same as found in Linux, it's believed there are no
1066 other rogues in the market place. All other models from the above
1069 To be safe, if you are at all concerned, you can quirk each of your
1070 drives to prevent NCQ from being sent by setting:
1071 kern.cam.ada.X.quirks="0x2"
1072 in loader.conf. If the drive requires the 4k sector quirk, set the
1073 quirks entry to 0x3.
1076 The FAST_DEPEND build option has been removed and its functionality is
1077 now the one true way. The old mkdep(1) style of 'make depend' has
1078 been removed. See 20160311 for further details.
1081 Resource range types have grown from unsigned long to uintmax_t. All
1082 drivers, and anything using libdevinfo, need to be recompiled.
1085 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1086 builds. It no longer runs mkdep(1) during 'make depend', and the
1087 'make depend' stage can safely be skipped now as it is auto ran
1088 when building 'make all' and will generate all SRCS and DPSRCS before
1089 building anything else. Dependencies are gathered at compile time with
1090 -MF flags kept in separate .depend files per object file. Users should
1091 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1092 stale .depend files.
1095 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1096 kernel modules. Therefore, if you load any kernel modules at boot time,
1097 please install the boot loaders after you install the kernel, but before
1101 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1102 make installkernel KERNCONF=YOUR_KERNEL_HERE
1103 make -C sys/boot install
1104 <reboot in single user>
1106 Then follow the usual steps, described in the General Notes section,
1110 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1111 see the 20141231 entry below for information about prerequisites and
1112 upgrading, if you are not already using clang 3.5.0 or higher.
1115 The AIO subsystem is now a standard part of the kernel. The
1116 VFS_AIO kernel option and aio.ko kernel module have been removed.
1117 Due to stability concerns, asynchronous I/O requests are only
1118 permitted on sockets and raw disks by default. To enable
1119 asynchronous I/O requests on all file types, set the
1120 vfs.aio.enable_unsafe sysctl to a non-zero value.
1123 The ELF object manipulation tool objcopy is now provided by the
1124 ELF Tool Chain project rather than by GNU binutils. It should be a
1125 drop-in replacement, with the addition of arm64 support. The
1126 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1127 to obtain the GNU version if necessary.
1130 Building ZFS pools on top of zvols is prohibited by default. That
1131 feature has never worked safely; it's always been prone to deadlocks.
1132 Using a zvol as the backing store for a VM guest's virtual disk will
1133 still work, even if the guest is using ZFS. Legacy behavior can be
1134 restored by setting vfs.zfs.vol.recursive=1.
1137 The NONE and HPN patches has been removed from OpenSSH. They are
1138 still available in the security/openssh-portable port.
1141 With the addition of ypldap(8), a new _ypldap user is now required
1142 during installworld. "mergemaster -p" can be used to add the user
1143 prior to installworld, as documented in the handbook.
1146 The tftp loader (pxeboot) now uses the option root-path directive. As a
1147 consequence it no longer looks for a pxeboot.4th file on the tftp
1148 server. Instead it uses the regular /boot infrastructure as with the
1152 The code to start recording plug and play data into the modules has
1153 been committed. While the old tools will properly build a new kernel,
1154 a number of warnings about "unknown metadata record 4" will be produced
1155 for an older kldxref. To avoid such warnings, make sure to rebuild
1156 the kernel toolchain (or world). Make sure that you have r292078 or
1157 later when trying to build 292077 or later before rebuilding.
1160 Debug data files are now built by default with 'make buildworld' and
1161 installed with 'make installworld'. This facilitates debugging but
1162 requires more disk space both during the build and for the installed
1163 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1167 r291527 changed the internal interface between the nfsd.ko and
1168 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1169 __FreeBSD_version has been bumped because of this.
1172 Add support for unicode collation strings leads to a change of
1173 order of files listed by ls(1) for example. To get back to the old
1174 behaviour, set LC_COLLATE environment variable to "C".
1176 Databases administrators will need to reindex their databases given
1177 collation results will be different.
1179 Due to a bug in install(1) it is recommended to remove the ancient
1180 locales before running make installworld.
1182 rm -rf /usr/share/locale/*
1185 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1186 libcrypto.so.7 or libssl.so.7 must be recompiled.
1189 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1190 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1191 should be replaced with isp_2400 and isp_2500 modules respectively.
1194 The build previously allowed using 'make -n' to not recurse into
1195 sub-directories while showing what commands would be executed, and
1196 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1197 and 'make -N' will not.
1200 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1201 and etcupdate will now use this file. A custom sendmail.cf is now
1202 updated via this mechanism rather than via installworld. If you had
1203 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1204 want to remove the exclusion or change it to "always install".
1205 /etc/mail/sendmail.cf is now managed the same way regardless of
1206 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1207 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1210 Compatibility shims for legacy ATA device names have been removed.
1211 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1212 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1213 environment variables, /dev/ad* and /dev/ar* symbolic links.
1216 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1217 Please see the 20141231 entry below for information about prerequisites
1218 and upgrading, if you are not already using clang 3.5.0 or higher.
1221 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1222 and renamed from .symbols to .debug. This reduces the size requirements
1223 on the boot partition or file system and provides consistency with
1224 userland debug files.
1226 When using the supported kernel installation method the
1227 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1228 as is done with /boot/kernel.
1230 Developers wishing to maintain the historical behavior of installing
1231 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1234 The wireless drivers had undergone changes that remove the 'parent
1235 interface' from the ifconfig -l output. The rc.d network scripts
1236 used to check presence of a parent interface in the list, so old
1237 scripts would fail to start wireless networking. Thus, etcupdate(3)
1238 or mergemaster(8) run is required after kernel update, to update your
1239 rc.d scripts in /etc.
1242 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1243 These configurations are now automatically interpreted as
1244 'scrub fragment reassemble'.
1247 Kernel-loadable modules for the random(4) device are back. To use
1248 them, the kernel must have
1251 options RANDOM_LOADABLE
1253 kldload(8) can then be used to load random_fortuna.ko
1254 or random_yarrow.ko. Please note that due to the indirect
1255 function calls that the loadable modules need to provide,
1256 the build-in variants will be slightly more efficient.
1258 The random(4) kernel option RANDOM_DUMMY has been retired due to
1259 unpopularity. It was not all that useful anyway.
1262 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1263 Control over building the ELF Tool Chain tools is now provided by
1264 the WITHOUT_TOOLCHAIN knob.
1267 The polarity of Pulse Per Second (PPS) capture events with the
1268 uart(4) driver has been corrected. Prior to this change the PPS
1269 "assert" event corresponded to the trailing edge of a positive PPS
1270 pulse and the "clear" event was the leading edge of the next pulse.
1272 As the width of a PPS pulse in a typical GPS receiver is on the
1273 order of 1 millisecond, most users will not notice any significant
1274 difference with this change.
1276 Anyone who has compensated for the historical polarity reversal by
1277 configuring a negative offset equal to the pulse width will need to
1278 remove that workaround.
1281 The default group assigned to /dev/dri entries has been changed
1282 from 'wheel' to 'video' with the id of '44'. If you want to have
1283 access to the dri devices please add yourself to the video group
1286 # pw groupmod video -m $USER
1289 The menu.rc and loader.rc files will now be replaced during
1290 upgrades. Please migrate local changes to menu.rc.local and
1291 loader.rc.local instead.
1294 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1295 strings and strip have been removed. The src.conf(5) knob
1296 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1299 As ZFS requires more kernel stack pages than is the default on some
1300 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1301 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1303 Please consider using 'options KSTACK_PAGES=X' where X is greater
1304 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1307 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1308 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1309 default, i.e., they will not contain "::". For example, instead
1310 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1311 to have a more specific match, such as different map entries for
1312 IPv6:0:0 vs IPv6:0. This change requires that configuration
1313 data (including maps, files, classes, custom ruleset, etc.) must
1314 use the same format, so make certain such configuration data is
1315 upgrading. As a very simple check search for patterns like
1316 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1317 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1318 the cf option UseCompressedIPv6Addresses.
1321 The default kernel entropy-processing algorithm is now
1322 Fortuna, replacing Yarrow.
1324 Assuming you have 'device random' in your kernel config
1325 file, the configurations allow a kernel option to override
1326 this default. You may choose *ONE* of:
1328 options RANDOM_YARROW # Legacy /dev/random algorithm.
1329 options RANDOM_DUMMY # Blocking-only driver.
1331 If you have neither, you get Fortuna. For most people,
1332 read no further, Fortuna will give a /dev/random that works
1333 like it always used to, and the difference will be irrelevant.
1335 If you remove 'device random', you get *NO* kernel-processed
1336 entropy at all. This may be acceptable to folks building
1337 embedded systems, but has complications. Carry on reading,
1338 and it is assumed you know what you need.
1340 *PLEASE* read random(4) and random(9) if you are in the
1341 habit of tweaking kernel configs, and/or if you are a member
1342 of the embedded community, wanting specific and not-usual
1343 behaviour from your security subsystems.
1345 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1346 random', you will NOT have a functioning /dev/random, and
1347 many cryptographic features will not work, including SSH.
1348 You may also find strange behaviour from the random(3) set
1349 of library functions, in particular sranddev(3), srandomdev(3)
1350 and arc4random(3). The reason for this is that the KERN_ARND
1351 sysctl only returns entropy if it thinks it has some to
1352 share, and with RANDOM_DUMMY or no 'device random' this
1356 An additional fix for the issue described in the 20150614 sendmail
1357 entry below has been committed in revision 284717.
1360 FreeBSD's old make (fmake) has been removed from the system. It is
1361 available as the devel/fmake port or via pkg install fmake.
1364 The fix for the issue described in the 20150614 sendmail entry
1365 below has been committed in revision 284436. The work
1366 around described in that entry is no longer needed unless the
1367 default setting is overridden by a confDH_PARAMETERS configuration
1368 setting of '5' or pointing to a 512 bit DH parameter file.
1371 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1372 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1373 and devel/kyua to version 0.20+ and adjust any calling code to work
1374 with Kyuafile and kyua.
1377 The import of openssl to address the FreeBSD-SA-15:10.openssl
1378 security advisory includes a change which rejects handshakes
1379 with DH parameters below 768 bits. sendmail releases prior
1380 to 8.15.2 (not yet released), defaulted to a 512 bit
1381 DH parameter setting for client connections. To work around
1382 this interoperability, sendmail can be configured to use a
1383 2048 bit DH parameter by:
1385 1. Edit /etc/mail/`hostname`.mc
1386 2. If a setting for confDH_PARAMETERS does not exist or
1387 exists and is set to a string beginning with '5',
1388 replace it with '2'.
1389 3. If a setting for confDH_PARAMETERS exists and is set to
1390 a file path, create a new file with:
1391 openssl dhparam -out /path/to/file 2048
1392 4. Rebuild the .cf file:
1393 cd /etc/mail/; make; make install
1394 5. Restart sendmail:
1395 cd /etc/mail/; make restart
1397 A sendmail patch is coming, at which time this file will be
1401 Generation of legacy formatted entries have been disabled by default
1402 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1403 entries were converted to use the new format by default when the new,
1404 machine independent format have been added and supported since FreeBSD
1407 Please see the pwd_mkdb(8) manual page for further details.
1410 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1411 20141231 entry below for information about prerequisites and upgrading,
1412 if you are not already using 3.5.0 or higher.
1415 TI platform code switched to using vendor DTS files and this update
1416 may break existing systems running on Beaglebone, Beaglebone Black,
1419 - dtb files should be regenerated/reinstalled. Filenames are the
1420 same but content is different now
1421 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1422 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1423 addressing scheme is now pin 25 on /dev/gpioc3.
1424 - Pandaboard: /etc/ttys should be updated, serial console device is
1425 now /dev/ttyu2, not /dev/ttyu0
1428 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1429 If you need the GNU extension from groff soelim(1), install groff
1430 from package: pkg install groff, or via ports: textproc/groff.
1433 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1434 defined in symlink(7); previously symlinks were silently ignored.
1437 The const qualifier has been removed from iconv(3) to comply with
1438 POSIX. The ports tree is aware of this from r384038 onwards.
1441 Libraries specified by LIBADD in Makefiles must have a corresponding
1442 DPADD_<lib> variable to ensure correct dependencies. This is now
1443 enforced in src.libnames.mk.
1446 From legacy ata(4) driver was removed support for SATA controllers
1447 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1448 Kernel modules ataahci and ataadaptec were removed completely,
1449 replaced by ahci and mvs modules respectively.
1452 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1453 the 20141231 entry below for information about prerequisites and
1454 upgrading, if you are not already using 3.5.0 or higher.
1457 The 32-bit PowerPC kernel has been changed to a position-independent
1458 executable. This can only be booted with a version of loader(8)
1459 newer than January 31, 2015, so make sure to update both world and
1460 kernel before rebooting.
1463 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1464 but before r278950, the RNG was not seeded properly. Immediately
1465 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1466 ssh keys or openssl keys) that were generated w/ a kernel from that
1467 range. This does not affect programs that directly used /dev/random
1468 or /dev/urandom. All userland uses of arc4random(3) are affected.
1471 The autofs(4) ABI was changed in order to restore binary compatibility
1472 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1473 with the new kernel.
1476 The powerpc64 kernel has been changed to a position-independent
1477 executable. This can only be booted with a new version of loader(8),
1478 so make sure to update both world and kernel before rebooting.
1481 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1482 only release, no new features have been added. Please see the 20141231
1483 entry below for information about prerequisites and upgrading, if you
1484 are not already using 3.5.0.
1487 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1488 taken from the ELF Tool Chain project rather than GNU binutils. They
1489 should be drop-in replacements, with the addition of arm64 support.
1490 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1491 binutils tools, if necessary. See 20150805 for updated information.
1494 The default Unbound configuration now enables remote control
1495 using a local socket. Users who have already enabled the
1496 local_unbound service should regenerate their configuration
1497 by running "service local_unbound setup" as root.
1500 The GNU texinfo and GNU info pages have been removed.
1501 To be able to view GNU info pages please install texinfo from ports.
1504 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1506 As of this release, a prerequisite for building clang, llvm and lldb is
1507 a C++11 capable compiler and C++11 standard library. This means that to
1508 be able to successfully build the cross-tools stage of buildworld, with
1509 clang as the bootstrap compiler, your system compiler or cross compiler
1510 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1511 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1514 On any standard FreeBSD 10.x or 11.x installation, where clang and
1515 libc++ are on by default (that is, on x86 or arm), this should work out
1518 On 9.x installations where clang is enabled by default, e.g. on x86 and
1519 powerpc, libc++ will not be enabled by default, so libc++ should be
1520 built (with clang) and installed first. If both clang and libc++ are
1521 missing, build clang first, then use it to build libc++.
1523 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1524 the instructions for 9.x above.
1526 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1527 default, and do not build clang.
1529 Many embedded systems are resource constrained, and will not be able to
1530 build clang in a reasonable time, or in some cases at all. In those
1531 cases, cross building bootable systems on amd64 is a workaround.
1533 This new version of clang introduces a number of new warnings, of which
1534 the following are most likely to appear:
1538 This warns in two cases, for both C and C++:
1539 * When the code is trying to take the absolute value of an unsigned
1540 quantity, which is effectively a no-op, and almost never what was
1541 intended. The code should be fixed, if at all possible. If you are
1542 sure that the unsigned quantity can be safely cast to signed, without
1543 loss of information or undefined behavior, you can add an explicit
1544 cast, or disable the warning.
1546 * When the code is trying to take an absolute value, but the called
1547 abs() variant is for the wrong type, which can lead to truncation.
1548 If you want to disable the warning instead of fixing the code, please
1549 make sure that truncation will not occur, or it might lead to unwanted
1552 -Wtautological-undefined-compare and
1553 -Wundefined-bool-conversion
1555 These warn when C++ code is trying to compare 'this' against NULL, while
1556 'this' should never be NULL in well-defined C++ code. However, there is
1557 some legacy (pre C++11) code out there, which actively abuses this
1558 feature, which was less strictly defined in previous C++ versions.
1560 Squid and openjdk do this, for example. The warning can be turned off
1561 for C++98 and earlier, but compiling the code in C++11 mode might result
1562 in unexpected behavior; for example, the parts of the program that are
1563 unreachable could be optimized away.
1566 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1567 kernel sources have been removed. The .h files remain, since some
1568 utilities include them. This will need to be fixed later.
1569 If "mount -t oldnfs ..." is attempted, it will fail.
1570 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1571 the utilities will report errors.
1574 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1575 directories to top level SUBDIR variable when their parent
1576 directory is included in LOCAL_DIRS. Users with build systems with
1577 such hierarchies and without SUBDIR entries in the parent
1578 directory Makefiles should add them or add the directories to
1582 faith(4) and faithd(8) have been removed from the base system. Faith
1583 has been obsolete for a very long time.
1586 vt(4), the new console driver, is enabled by default. It brings
1587 support for Unicode and double-width characters, as well as
1588 support for UEFI and integration with the KMS kernel video
1591 You may need to update your console settings in /etc/rc.conf,
1592 most probably the keymap. During boot, /etc/rc.d/syscons will
1593 indicate what you need to do.
1595 vt(4) still has issues and lacks some features compared to
1596 syscons(4). See the wiki for up-to-date information:
1597 https://wiki.freebsd.org/Newcons
1599 If you want to keep using syscons(4), you can do so by adding
1600 the following line to /boot/loader.conf:
1604 pjdfstest has been integrated into kyua as an opt-in test suite.
1605 Please see share/doc/pjdfstest/README for more details on how to
1609 gperf has been removed from the base system for architectures
1610 that use clang. Ports that require gperf will obtain it from the
1614 pjdfstest has been moved from tools/regression/pjdfstest to
1618 At svn r271982, The default linux compat kernel ABI has been adjusted
1619 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1620 update. If you wish to continue using the linux-f10 compat ports,
1621 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1622 encouraged to update their linux-compat packages to linux-c6 during
1623 their next update cycle.
1626 The ofwfb driver, used to provide a graphics console on PowerPC when
1627 using vt(4), no longer allows mmap() of all physical memory. This
1628 will prevent Xorg on PowerPC with some ATI graphics cards from
1629 initializing properly unless x11-servers/xorg-server is updated to
1633 The xdev targets have been converted to using TARGET and
1634 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1637 The default unbound configuration has been modified to address
1638 issues with reverse lookups on networks that use private
1639 address ranges. If you use the local_unbound service, run
1640 "service local_unbound setup" as root to regenerate your
1641 configuration, then "service local_unbound reload" to load the
1645 The GNU texinfo and GNU info pages are not built and installed
1646 anymore, WITH_INFO knob has been added to allow to built and install
1648 UPDATE: see 20150102 entry on texinfo's removal
1651 The GNU readline library is now an INTERNALLIB - that is, it is
1652 statically linked into consumers (GDB and variants) in the base
1653 system, and the shared library is no longer installed. The
1654 devel/readline port is available for third party software that
1658 The Itanium architecture (ia64) has been removed from the list of
1659 known architectures. This is the first step in the removal of the
1663 Commit r268115 has added NFSv4.1 server support, merged from
1664 projects/nfsv4.1-server. Since this includes changes to the
1665 internal interfaces between the NFS related modules, a full
1666 build of the kernel and modules will be necessary.
1667 __FreeBSD_version has been bumped.
1670 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1671 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1672 which differs from the behaviour controlled by this knob.)
1675 Maximal length of the serial number in CTL was increased from 16 to
1676 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1677 and ctld, need to be rebuilt to work with a new kernel.
1680 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1681 1 respectively to match the upstream numbers. They were out of
1682 sync because, when they were originally added to FreeBSD, the
1683 upstream versions were not respected. These libraries are private
1684 and not yet built by default, so renumbering them should be a
1685 non-issue. However, unclean source trees will yield broken test
1686 programs once the operator executes "make delete-old-libs" after a
1687 "make installworld".
1689 Additionally, the atf-sh binary was made private by moving it into
1690 /usr/libexec/. Already-built shell test programs will keep the
1691 path to the old binary so they will break after "make delete-old"
1694 If you are using WITH_TESTS=yes (not the default), wipe the object
1695 tree and rebuild from scratch to prevent spurious test failures.
1696 This is only needed once: the misnumbered libraries and misplaced
1697 binaries have been added to OptionalObsoleteFiles.inc so they will
1698 be removed during a clean upgrade.
1701 Clang and llvm have been upgraded to 3.4.1 release.
1704 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1705 be removed to avoid issues in the future (and has been added to
1709 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1710 past, it affected all builds that used the bsd.*.mk files. The old
1711 behavior was a bug, but people may have relied upon it. To get this
1712 behavior back, you can .include /etc/src.conf from /etc/make.conf
1713 (which is still global and isn't changed). This also changes the
1714 behavior of incremental builds inside the tree of individual
1715 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1716 Although this has survived make universe and some upgrade scenarios,
1717 other upgrade scenarios may have broken. At least one form of
1718 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1719 as well... In cases where MAKESYSPATH isn't working with this
1720 setting, you'll need to set it to the full path to your tree.
1722 One side effect of all this cleaning up is that bsd.compiler.mk
1723 is no longer implicitly included by bsd.own.mk. If you wish to
1724 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1728 The lindev device has been removed since /dev/full has been made a
1729 standard device. __FreeBSD_version has been bumped.
1732 The knob WITHOUT_VI was added to the base system, which controls
1733 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1734 in order to reorder files share/termcap and didn't build ex(1) as a
1735 build tool, so building/installing with WITH_VI is highly advised for
1736 build hosts for older releases.
1738 This issue has been fixed in stable/9 and stable/10 in r277022 and
1739 r276991, respectively.
1742 The YES_HESIOD knob has been removed. It has been obsolete for
1743 a decade. Please move to using WITH_HESIOD instead or your builds
1744 will silently lack HESIOD.
1747 The uart(4) driver has been changed with respect to its handling
1748 of the low-level console. Previously the uart(4) driver prevented
1749 any process from changing the baudrate or the CLOCAL and HUPCL
1750 control flags. By removing the restrictions, operators can make
1751 changes to the serial console port without having to reboot.
1752 However, when getty(8) is started on the serial device that is
1753 associated with the low-level console, a misconfigured terminal
1754 line in /etc/ttys will now have a real impact.
1755 Before upgrading the kernel, make sure that /etc/ttys has the
1756 serial console device configured as 3wire without baudrate to
1757 preserve the previous behaviour. E.g:
1758 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1761 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1762 to improve performance. To re-enable it, if needed, run rpcbind
1763 with command line option -W.
1766 Switched back to the GPL dtc compiler due to updates in the upstream
1767 dts files not being supported by the BSDL dtc compiler. You will need
1768 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1769 may result while building dtb files during a kernel build if you fail
1770 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1773 Clang and llvm have been upgraded to 3.4 release.
1776 The nve(4) driver has been removed. Please use the nfe(4) driver
1777 for NVIDIA nForce MCP Ethernet adapters instead.
1780 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1781 This could cause certain C++ applications using shared libraries built
1782 against the previous version of libc++ to crash. The incompatibility
1783 has now been fixed, but any C++ applications or shared libraries built
1784 between r261283 and r261801 should be recompiled.
1787 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1788 capability mode support. Please note that enabling the feature in
1789 kernel is still highly recommended.
1792 OpenSSH is now built with sandbox support, and will use sandbox as
1793 the default privilege separation method. This requires Capsicum
1794 capability mode support in kernel.
1797 The libelf and libdwarf libraries have been updated to newer
1798 versions from upstream. Shared library version numbers for
1799 these two libraries were bumped. Any ports or binaries
1800 requiring these two libraries should be recompiled.
1801 __FreeBSD_version is bumped to 1100006.
1804 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1805 instead of providing an explicit one, this would prevent such
1806 Makefile from providing its own Kyuafile in the future during
1807 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1808 intervention is needed to clean an objdir if you use NO_CLEAN:
1809 # find /usr/obj -name Kyuafile | xargs rm -f
1812 The behavior of gss_pseudo_random() for the krb5 mechanism
1813 has changed, for applications requesting a longer random string
1814 than produced by the underlying enctype's pseudo-random() function.
1815 In particular, the random string produced from a session key of
1816 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1817 be different at the 17th octet and later, after this change.
1818 The counter used in the PRF+ construction is now encoded as a
1819 big-endian integer in accordance with RFC 4402.
1820 __FreeBSD_version is bumped to 1100004.
1823 The WITHOUT_ATF build knob has been removed and its functionality
1824 has been subsumed into the more generic WITHOUT_TESTS. If you were
1825 using the former to disable the build of the ATF libraries, you
1826 should change your settings to use the latter.
1829 The default version of mtree is nmtree which is obtained from
1830 NetBSD. The output is generally the same, but may vary
1831 slightly. If you found you need identical output adding
1832 "-F freebsd9" to the command line should do the trick. For the
1833 time being, the old mtree is available as fmtree.
1836 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1837 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1838 1.1.4_8 and verify bsdyml not linked in, before running "make
1840 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1842 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1845 The stable/10 branch has been created in subversion from head
1852 Avoid using make -j when upgrading. While generally safe, there are
1853 sometimes problems using -j to upgrade. If your upgrade fails with
1854 -j, please try again without -j. From time to time in the past there
1855 have been problems using -j with buildworld and/or installworld. This
1856 is especially true when upgrading between "distant" versions (eg one
1857 that cross a major release boundary or several minor releases, or when
1858 several months have passed on the -current branch).
1860 Sometimes, obscure build problems are the result of environment
1861 poisoning. This can happen because the make utility reads its
1862 environment when searching for values for global variables. To run
1863 your build attempts in an "environmental clean room", prefix all make
1864 commands with 'env -i '. See the env(1) manual page for more details.
1866 When upgrading from one major version to another it is generally best to
1867 upgrade to the latest code in the currently installed branch first, then
1868 do an upgrade to the new branch. This is the best-tested upgrade path,
1869 and has the highest probability of being successful. Please try this
1870 approach if you encounter problems with a major version upgrade. Since
1871 the stable 4.x branch point, one has generally been able to upgrade from
1872 anywhere in the most recent stable branch to head / current (or even the
1873 last couple of stable branches). See the top of this file when there's
1876 When upgrading a live system, having a root shell around before
1877 installing anything can help undo problems. Not having a root shell
1878 around can lead to problems if pam has changed too much from your
1879 starting point to allow continued authentication after the upgrade.
1881 This file should be read as a log of events. When a later event changes
1882 information of a prior event, the prior event should not be deleted.
1883 Instead, a pointer to the entry with the new information should be
1884 placed in the old entry. Readers of this file should also sanity check
1885 older entries before relying on them blindly. Authors of new entries
1886 should write them with this in mind.
1890 When upgrading the boot ZFS pool to a new version, always follow
1893 1.) recompile and reinstall the ZFS boot loader and boot block
1894 (this is part of "make buildworld" and "make installworld")
1896 2.) update the ZFS boot block on your boot drive
1898 The following example updates the ZFS boot block on the first
1899 partition (freebsd-boot) of a GPT partitioned drive ada0:
1900 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1902 Non-boot pools do not need these updates.
1906 If you are updating from a prior version of FreeBSD (even one just
1907 a few days old), you should follow this procedure. It is the most
1908 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1910 make kernel-toolchain
1911 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1912 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1914 To test a kernel once
1915 ---------------------
1916 If you just want to boot a kernel once (because you are not sure
1917 if it works, or if you want to boot a known bad kernel to provide
1918 debugging information) run
1919 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1920 nextboot -k testkernel
1922 To rebuild everything and install it on the current system.
1923 -----------------------------------------------------------
1924 # Note: sometimes if you are running current you gotta do more than
1925 # is listed here if you are upgrading from a really old current.
1927 <make sure you have good level 0 dumps>
1929 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1930 make installkernel KERNCONF=YOUR_KERNEL_HERE
1932 <reboot in single user> [3]
1939 To cross-install current onto a separate partition
1940 --------------------------------------------------
1941 # In this approach we use a separate partition to hold
1942 # current's root, 'usr', and 'var' directories. A partition
1943 # holding "/", "/usr" and "/var" should be about 2GB in
1946 <make sure you have good level 0 dumps>
1949 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1950 <maybe newfs current's root partition>
1951 <mount current's root partition on directory ${CURRENT_ROOT}>
1952 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1953 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1954 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1955 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1956 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1957 <reboot into current>
1958 <do a "native" rebuild/install as described in the previous section>
1959 <maybe install compatibility libraries from ports/misc/compat*>
1963 To upgrade in-place from stable to current
1964 ----------------------------------------------
1965 <make sure you have good level 0 dumps>
1967 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1968 make installkernel KERNCONF=YOUR_KERNEL_HERE
1970 <reboot in single user> [3]
1977 Make sure that you've read the UPDATING file to understand the
1978 tweaks to various things you need. At this point in the life
1979 cycle of current, things change often and you are on your own
1980 to cope. The defaults can also change, so please read ALL of
1981 the UPDATING entries.
1983 Also, if you are tracking -current, you must be subscribed to
1984 freebsd-current@freebsd.org. Make sure that before you update
1985 your sources that you have read and understood all the recent
1986 messages there. If in doubt, please track -stable which has
1987 much fewer pitfalls.
1989 [1] If you have third party modules, such as vmware, you
1990 should disable them at this point so they don't crash your
1993 [3] From the bootblocks, boot -s, and then do
1998 adjkerntz -i # if CMOS is wall time
1999 Also, when doing a major release upgrade, it is required that
2000 you boot into single user mode to do the installworld.
2002 [4] Note: This step is non-optional. Failure to do this step
2003 can result in a significant reduction in the functionality of the
2004 system. Attempting to do it by hand is not recommended and those
2005 that pursue this avenue should read this file carefully, as well
2006 as the archives of freebsd-current and freebsd-hackers mailing lists
2007 for potential gotchas. The -U option is also useful to consider.
2008 See mergemaster(8) for more information.
2010 [5] Usually this step is a no-op. However, from time to time
2011 you may need to do this if you get unknown user in the following
2012 step. It never hurts to do it all the time. You may need to
2013 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2014 install) after the buildworld before this step if you last updated
2015 from current before 20130425 or from -stable before 20130430.
2017 [6] This only deletes old files and directories. Old libraries
2018 can be deleted by "make delete-old-libs", but you have to make
2019 sure that no program is using those libraries anymore.
2021 [8] The new kernel must be able to run existing binaries used by
2022 an installworld. When upgrading across major versions, the new
2023 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2024 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2025 binaries). Failure to do so may leave you with a system that is
2026 hard to boot to recover. A GENERIC kernel will include suitable
2027 compatibility options to run binaries from older branches.
2029 Make sure that you merge any new devices from GENERIC since the
2030 last time you updated your kernel config file.
2032 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2033 "?=" instead of the "=" assignment operator, so that buildworld can
2034 override the CPUTYPE if it needs to.
2036 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2037 not on the command line, or in /etc/make.conf. buildworld will
2038 warn if it is improperly defined.
2041 This file contains a list, in reverse chronological order, of major
2042 breakages in tracking -current. It is not guaranteed to be a complete
2043 list of such breakages, and only contains entries since September 23, 2011.
2044 If you need to see UPDATING entries from before that date, you will need
2045 to fetch an UPDATING file from an older FreeBSD release.
2047 Copyright information:
2049 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2051 Redistribution, publication, translation and use, with or without
2052 modification, in full or in part, in any form or format of this
2053 document are permitted without further permission from the author.
2055 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2056 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2057 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2058 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2059 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2060 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2061 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2062 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2063 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2064 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2065 POSSIBILITY OF SUCH DAMAGE.
2067 Contact Warner Losh if you have any questions about your use of