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.
19 20210223: p4 FreeBSD-SA-21:03.pam_login_access
20 FreeBSD-SA-21:04.jail_remove
21 FreeBSD-SA-21:05.jail_chdir
23 FreeBSD-EN-21:06.microcode
24 FreeBSD-EN-21:07.caroot
25 FreeBSD-EN-21:08.freebsd-update
27 login.access fails to apply rules [SA-21:03.pam_login_access]
29 jail_remove(2) fails to kill all jailed processes [SA-21:04.jail_remove]
31 jail_attach(2) relies on the caller to change the cwd [SA-21:05.jail_chdir]
33 Xen grant mapping error handling issues [SA-21:06.xen]
35 Boot-time microcode loading causes a boot hang [EN-21:06.microcode]
37 Root certificate bundle update [EN-21:07.caroot]
39 freebsd-update passwd regeneration [EN-21:08.freebsd-update]
41 20210128: p3 FreeBSD-EN-21:01.tzdata
44 FreeBSD-SA-21:01.fsdisclosure
45 FreeBSD-SA-21:02.xenoom
47 Update timezone database information [EN-21:01.tzdata]
49 Panic when destroying VNET and epair simultaneously [EN-21:03.vnet]
51 zfs recv fails to propagate snapshot deletion [EN-21:04.zfs]
53 Uninitialized file system kernel stack leaks [SA-21:01.fsdisclosure]
55 Xen guest-triggered out of memory [SA-21:02.xenoom]
57 20201208: p2 FreeBSD-SA-20:33.openssl
59 Fix OpenSSL NULL pointer de-reference. [SA-20:33.openssl]
61 20201201: p1 FreeBSD-EN-20:19.audit
62 FreeBSD-EN-20:20.tzdata
64 FreeBSD-EN-20:22.callout
65 FreeBSD-SA-20:31.icmp6
66 FreeBSD-SA-20:32.rtsold
68 Fix execve/fexecve system call auditing. [EN-20:19.audit]
70 Update timezone database information. [EN-20:20.tzdata]
72 Fix uninitialized variable in ipfw. [EN-20:21.ipfw]
74 Fix race condition in callout CPU migration. [EN-20:22.callout]
76 Fix ICMPv6 use-after-free in error message handling. [SA-20:31.icmp6]
78 Fix multiple vulnerabilities in rtsold. [SA-20:32.rtsold]
83 20200915: p1 FreeBSD-SA-20:27.ure
84 FreeBSD-SA-20:28.bhyve_vmcs
85 FreeBSD-SA-20:29.bhyve_svm
88 Fix ure device driver susceptible to packet-in-packet attack.
91 Fix bhyve privilege escalation via VMCS access. [SA-20:28.bhyve_vmcs]
93 Fix bhyve SVM guest escape. [SA-20:29.bhyve_svm]
95 Fix ftpd privilege escalation via ftpchroot. [SA-20:30.ftpd]
98 The make.conf(5) MALLOC_PRODUCTION variable, used for disabling and
99 enabling assertions and statistics gathering in malloc(3), has been
100 migrated to a src.conf(5) WITH/WITHOUT_MALLOC_PRODUCTION option.
102 On stable branches, WITH_MALLOC_PRODUCTION is set by default, which
103 means that malloc(3) has assertions and statistics gathering disabled,
104 for improved performance.
106 For backwards compatibility, the make.conf(5) MALLOC_PRODUCTION is still
107 honored, but it is now deprecated and undocumented.
110 The resume code now notifies devd with the 'kernel' system
111 rather than the old 'kern' subsystem to be consistent with
112 other use. The old notification will be created as well, but
113 will be removed prior to FreeBSD 14.0.
116 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
117 been upgraded to 10.0.1. Please see the 20141231 entry below for
118 information about prerequisites and upgrading, if you are not already
119 using clang 3.5.0 or higher.
122 read(2) of a directory fd is now rejected by default. root may
123 re-enable it for the entire system with the
124 security.bsd.allow_read_dir sysctl(8) MIB.
126 It may be advised to setup aliases for grep to default to `-d skip` if
127 commonly non-recursively grepping a list that includes directories and
128 the potential for the resulting stderr output is not tolerable. Example
129 aliases are now installed, commented out, in /root/.cshrc.
132 Upstream DTS from Linux 5.6 was merged and they now have the SID
133 and THS (Secure ID controller and THermal Sensor) node present.
134 The DTB overlays have now been removed from the tree for the H3/H5 and
135 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
136 deal with upstream DTS. If you are using those overlays you need to
137 remove them from loader.conf and update the DTBs on the FAT partition.
140 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
141 been upgraded to 10.0.0. Please see the 20141231 entry below for
142 information about prerequisites and upgrading, if you are not already
143 using clang 3.5.0 or higher.
146 The root certificates of the Mozilla CA Certificate Store have been
147 imported into the base system and can be managed with the certctl(8)
148 utility. If you have installed the security/ca_root_nss port or package
149 with the ETCSYMLINK option (the default), be advised that there may be
150 differences between those included in the port and those included in
151 base due to differences in nss branch used as well as general update
152 frequency. Note also that certctl(8) cannot manage certs in the
153 format used by the security/ca_root_nss port.
156 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
157 been upgraded to 9.0.1. Please see the 20141231 entry below for
158 information about prerequisites and upgrading, if you are not already
159 using clang 3.5.0 or higher.
162 The nctgpio and wbwd drivers have been moved to the superio bus.
163 If you have one of these drivers in a kernel configuration, then
164 you should add device superio to it. If you use one of these drivers
165 as a module and you compile a custom set of modules, then you should
166 add superio to the set.
169 The tap(4) driver has been folded into tun(4), and the module has been
170 renamed to tuntap. You should update any kld_list="if_tap" or
171 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
172 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
173 module instead, and "device tap" or "device tun" entries in kernel
174 config files to select the tuntap device instead.
177 ntpd no longer by default locks its pages in memory, allowing them
178 to be paged out by the kernel. Use rlimit memlock to restore
179 historic BSD behaviour. For example, add "rlimit memlock 32"
180 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
183 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
184 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
185 been removed from mount_fusefs(8). You can safely remove them from
186 your scripts, because they had no effect.
188 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
189 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
190 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
191 sysctls have been removed. If you felt the need to set any of them to
192 a non-default value, please tell asomers@FreeBSD.org why.
195 The fuse(4) module has been renamed to fusefs(4) for consistency with
196 other filesystems. You should update any kld_load="fuse" entries in
197 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
198 "options FUSE" enties in kernel config files.
201 Default permissions on the /var/account/acct file (and copies of it
202 rotated by periodic daily scripts) are changed from 0644 to 0640
203 because the file contains sensitive information that should not be
204 world-readable. If the /var/account directory must be created by
205 rc.d/accounting, the mode used is now 0750. Admins who use the
206 accounting feature are encouraged to change the mode of an existing
207 /var/account directory to 0750 or 0700.
210 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
211 been upgraded to 8.0.1. Please see the 20141231 entry below for
212 information about prerequisites and upgrading, if you are not already
213 using clang 3.5.0 or higher.
216 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
217 functionality needed for the RETPOLINE option should work properly
218 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
221 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
222 8.0.0. Please see the 20141231 entry below for information about
223 prerequisites and upgrading, if you are not already using clang 3.5.0
227 The RETPOLINE option produces non-functional ifunc-using binaries
228 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
229 Once Clang 8 is merged it may be enabled again.
232 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
233 7.0.1. Please see the 20141231 entry below for information about
234 prerequisites and upgrading, if you are not already using clang 3.5.0
238 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
239 compiled into your custom kernel, add 'device xz' statement to the
243 Iflib is no longer unconditionally compiled into the kernel. Drivers
244 using iflib and statically compiled into the kernel, now require
245 the 'device iflib' config option. For the same drivers loaded as
246 modules on kernels not having 'device iflib', the iflib.ko module
247 is loaded automatically.
250 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
251 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
252 servers that have vfs.nfsd.nfs_privport set will only allow mounts
253 from clients using a reserved port#. Since both the FreeBSD and Linux
254 NFSv4 clients use reserved port#s by default, this should not affect
258 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
259 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
260 it produces broken binaries when ifuncs are in use. Users needing
261 GNU ld should install the binutils port or package.
264 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
265 has been converted to a port (misc/ctm) and will be removed from
266 FreeBSD-13. A depreciation warning will be printed to stderr by
267 the ctm command, but the functionality will remain in base for all
271 The stable/12 branch has been created in subversion from head
275 Ports for the DRM modules have been simplified. Now, amd64 users should
276 just install the drm-kmod port. All others should install
279 Graphics hardware that's newer than about 2010 usually works with
280 drm-kmod. For hardware older than 2013, however, some users will need
281 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
282 than 2008 usually only works in drm-legacy-kmod. The graphics team can
283 only commit to hardware made since 2013 due to the complexity of the
284 market and difficulty to test all the older cards effectively. If you
285 have hardware supported by drm-kmod, you are strongly encouraged to use
286 that as you will get better support.
288 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
289 elsewhere, the drm and drm2 modules will be eliminated from the src base
290 soon (with a limited exception for arm). Please update to the package asap
291 and report any issues to x11@freebsd.org.
293 Generally, anybody using the drm*-kmod packages should add
294 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
295 cross-threading surprises, especially with automatic driver
296 loading from X11 startup. These will become the defaults in 13-current
300 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
301 custom kernel and module loading configuration files must be updated
302 accordingly. Moreover, interfaces previous presented as ixlvN to the
303 system are now exposed as iavfN and network configuration files must
304 be adjusted as necessary.
307 OpenSSL has been updated to version 1.1.1. This update included
308 additional various API changes througout the base system. It is
309 important to rebuild third-party software after upgrading. The value
310 of __FreeBSD_version has been bumped accordingly.
313 The legacy DRM modules and drivers have now been added to the loader's
314 module blacklist, in favor of loading them with kld_list in rc.conf(5).
315 The module blacklist may be overridden with the loader.conf(5)
316 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
320 The cam(4) based nda(4) driver will be used over nvd(4) by default on
321 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
322 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
323 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
327 Reproducible build mode is now on by default, in preparation for
328 FreeBSD 12.0. This eliminates build metadata such as the user,
329 host, and time from the kernel (and uname), unless the working tree
330 corresponds to a modified checkout from a version control system.
331 The previous behavior can be obtained by setting the /etc/src.conf
332 knob WITHOUT_REPRODUCIBLE_BUILD.
335 The Yarrow CSPRNG has been removed from the kernel as it has not been
336 supported by its designers since at least 2003. Fortuna has been the
337 default since FreeBSD-11.
340 devctl freeze/thaw have gone into the tree, the rc scripts have been
341 updated to use them and devmatch has been changed. You should update
342 kernel, userland and rc scripts all at the same time.
345 The default interpreter has been switched from 4th to Lua.
346 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
347 interpreter. If you have custom FORTH code you will need to set
348 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
349 src.conf for the build. This will create default hard links between
350 loader and loader_4th instead of loader and loader_lua, the new default.
351 If you are using UEFI it will create the proper hard link to loader.efi.
353 bhyve uses userboot.so. It remains 4th-only until some issues are solved
354 regarding coexisting with multiple versions of FreeBSD are resolved.
357 ls(1) now respects the COLORTERM environment variable used in other
358 systems and software to indicate that a colored terminal is both
359 supported and desired. If ls(1) is suddenly emitting colors, they may
360 be disabled again by either removing the unwanted COLORTERM from your
361 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
362 may not be observed in a future release.
365 The default pager for most commands has been changed to "less". To
366 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
370 The jedec_ts(4) driver has been removed. A superset of its functionality
371 is available in the jedec_dimm(4) driver, and the manpage for that
372 driver includes migration instructions. If you have "device jedec_ts"
373 in your kernel configuration file, it must be removed.
376 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
377 This should have no effect if the kernel is booted via BIOS/legacy boot.
378 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
379 has a buggy firmware that prevents a successful boot due to use of
383 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
384 support has been removed from the tree. These ports were
385 obsolete and/or known to be broken for many years.
388 loader.efi has been augmented to participate more fully in the
389 UEFI boot manager protocol. loader.efi will now look at the
390 BootXXXX environment variable to determine if a specific kernel
391 or root partition was specified. XXXX is derived from BootCurrent.
392 efibootmgr(8) manages these standard UEFI variables.
395 zfsloader's functionality has now been folded into loader.
396 zfsloader is no longer necessary once you've updated your
397 boot blocks. For a transition period, we will install a
398 hardlink for zfsloader to loader to allow a smooth transition
399 until the boot blocks can be updated (hard link because old
400 zfs boot blocks don't understand symlinks).
403 ARM64 now have efifb support, if you want to have serial console
404 on your arm64 board when an screen is connected and the bootloader
405 setup a frambuffer for us to use, just add :
409 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
410 an screen connected as the firmware will setup a framebuffer are that
411 u-boot will expose as an EFI framebuffer.
414 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
415 or take steps to update /etc/passwd before doing installworld on
416 existing systems. Do not skip the "mergemaster -Fp" step before
417 installworld, as described in the update procedures near the bottom
418 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
419 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
420 the ntp config file contain options that change file/dir locations.
421 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
422 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
423 taking steps to ensure that all required files/dirs are accessible
427 Big endian arm support has been removed.
430 The static environment setup in kernel configs is no longer mutually
431 exclusive with the loader(8) environment by default. In order to
432 restore the previous default behavior of disabling the loader(8)
433 environment if a static environment is present, you must specify
434 loader_env.disabled=1 in the static environment.
437 The ABI of syscalls used by management tools like sockstat and
438 netstat has been broken to allow 32-bit binaries to work on
439 64-bit kernels without modification. These programs will need
440 to match the kernel in order to function. External programs may
441 require minor modifications to accommodate a change of type in
442 structures from pointers to 64-bit virtual addresses.
445 On i386 and amd64 atomics are now inlined. Out of tree modules using
446 atomics will need to be rebuilt.
449 The '%I' format in the kern.corefile sysctl limits the number of
450 core files that a process can generate to the number stored in the
451 debug.ncores sysctl. The '%I' format is replaced by the single digit
452 index. Previously, if all indexes were taken the kernel would overwrite
453 only a core file with the highest index in a filename.
454 Currently the system will create a new core file if there is a free
455 index or if all slots are taken it will overwrite the oldest one.
458 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
459 6.0.1. Please see the 20141231 entry below for information about
460 prerequisites and upgrading, if you are not already using clang 3.5.0
464 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
465 needed to be changed to work with it. This change was made with r335763
466 and requires a mergemaster / etcupdate / etc to update the installed file.
469 r334930 changed the interface between the NFS modules, so they all
470 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
473 As of r334391 lld is the default amd64 system linker; it is installed
474 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
478 The kernel / userland interface for devinfo changed, so you'll
479 need a new kernel and userland as a pair for it to work (rebuilding
480 lib/libdevinfo is all that's required). devinfo and devmatch will
481 not work, but everything else will when there's a mismatch.
484 The on-disk format for hwpmc callchain records has changed to include
485 threadid corresponding to a given record. This changes the field offsets
486 and thus requires that libpmcstat be rebuilt before using a kernel
490 The vxge(4) driver has been removed. This driver was introduced into
491 HEAD one week before the Exar left the Ethernet market and is not
492 known to be used. If you have device vxge in your kernel config file
496 The amd64 kernel now requires a ld that supports ifunc to produce a
497 working kernel, either lld or a newer binutils. lld is built by default
498 on amd64, and the 'buildkernel' target uses it automatically. However,
499 it is not the default linker, so building the kernel the traditional
500 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
501 binutils port/package). lld will soon be default, and this requirement
504 NOTE: As of r334391 lld is the default system linker on amd64, and no
505 workaround is necessary.
508 The nxge(4) driver has been removed. This driver was for PCI-X 10g
509 cards made by s2io/Neterion. The company was aquired by Exar and
510 no longer sells or supports Ethernet products. If you have device
511 nxge in your kernel config file it must be removed.
514 The tz database (tzdb) has been updated to 2018e. This version more
515 correctly models time stamps in time zones with negative DST such as
516 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
517 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
518 time zone abbreviations and the tm_isdst flag.
521 The ixgb(4) driver has been removed. This driver was for an early and
522 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
523 quickly shifted to the long lived ixgbe family. If you have device
524 ixgb in your kernel config file it must be removed.
527 The lmc(4) driver has been removed. This was a WAN interface
528 card that was already reportedly rare in 2003, and had an ambiguous
529 license. If you have device lmc in your kernel config file it must
533 Support for Arcnet networks has been removed. If you have device
534 arcnet or device cm in your kernel config file they must be
538 Support for FDDI networks has been removed. If you have device
539 fddi or device fpa in your kernel config file they must be
543 In addition to supporting RFC 3164 formatted messages, the
544 syslogd(8) service is now capable of parsing RFC 5424 formatted
545 log messages. The main benefit of using RFC 5424 is that clients
546 may now send log messages with timestamps containing year numbers,
547 microseconds and time zone offsets.
549 Similarly, the syslog(3) C library function has been altered to
550 send RFC 5424 formatted messages to the local system logging
551 daemon. On systems using syslogd(8), this change should have no
552 negative impact, as long as syslogd(8) and the C library are
553 updated at the same time. On systems using a different system
554 logging daemon, it may be necessary to make configuration
555 adjustments, depending on the software used.
557 When using syslog-ng, add the 'syslog-protocol' flag to local
558 input sources to enable parsing of RFC 5424 formatted messages:
561 unix-dgram("/var/run/log" flags(syslog-protocol));
564 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
565 of the 'imuxsock' module to let messages be processed by the
566 regular RFC 3164/5424 parsing pipeline:
568 module(load="imuxsock" SysSock.UseSpecialParser="off")
570 Do note that these changes only affect communication between local
571 applications and syslogd(8). The format that syslogd(8) uses to
572 store messages on disk or forward messages to other systems
573 remains unchanged. syslogd(8) still uses RFC 3164 for these
574 purposes. Options to customize this behaviour will be added in the
575 future. Utilities that process log files stored in /var/log are
576 thus expected to continue to function as before.
578 __FreeBSD_version has been incremented to 1200061 to denote this
582 Support for token ring networks has been removed. If you
583 have "device token" in your kernel config you should remove
584 it. No device drivers supported token ring.
587 makefs was modified to be able to tag ISO9660 El Torito boot catalog
588 entries as EFI instead of overloading the i386 tag as done previously.
589 The amd64 mkisoimages.sh script used to build amd64 ISO images for
590 release was updated to use this. This may mean that makefs must be
591 updated before "make cdrom" can be run in the release directory. This
592 should be as simple as:
594 $ cd $SRCDIR/usr.sbin/makefs
595 $ make depend all install
598 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
599 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
600 Co-existance for the transition period will come shortly. Booting is a
601 complex environment and test coverage for Lua-enabled loaders has been
602 thin, so it would be prudent to assume it might not work and make
603 provisions for backup boot methods.
606 devmatch functionality has been turned on in devd. It will automatically
607 load drivers for unattached devices. This may cause unexpected drivers to
608 be loaded. Please report any problems to current@ and imp@freebsd.org.
611 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
612 6.0.0. Please see the 20141231 entry below for information about
613 prerequisites and upgrading, if you are not already using clang 3.5.0
617 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
618 This means it is used to link the kernel and userland libraries and
619 executables, but is not yet installed as /usr/bin/ld by default.
621 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
622 WITHOUT_LLD_BOOTSTRAP=yes
625 On i386, pmtimer has been removed. Its functionality has been folded
626 into apm. It was a no-op on ACPI in current for a while now (but was still
627 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
628 from kernel config files.
631 The use of RSS hash from the network card aka flowid has been
632 disabled by default for lagg(4) as it's currently incompatible with
633 the lacp and loadbalance protocols.
635 This can be re-enabled by setting the following in loader.conf:
636 net.link.lagg.default_use_flowid="1"
639 The SW_WATCHDOG option is no longer necessary to enable the
640 hardclock-based software watchdog if no hardware watchdog is
641 configured. As before, SW_WATCHDOG will cause the software
642 watchdog to be enabled even if a hardware watchdog is configured.
645 r326887 fixes the issue described in the 20171214 UPDATING entry.
646 r326888 flips the switch back to building GELI support always.
649 r362593 broke ZFS + GELI support for reasons unknown. However,
650 it also broke ZFS support generally, so GELI has been turned off
651 by default as the lesser evil in r326857. If you boot off ZFS and/or
652 GELI, it might not be a good time to update.
655 PowerPC users must update loader(8) by rebuilding world before
656 installing a new kernel, as the protocol connecting them has
657 changed. Without the update, loader metadata will not be passed
658 successfully to the kernel and users will have to enter their
659 root partition at the kernel mountroot prompt to continue booting.
660 Newer versions of loader can boot old kernels without issue.
663 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
664 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
665 to WITH/OUT_LOADER_GELI.
668 The naive and non-compliant support of posix_fallocate(2) in ZFS
669 has been removed as of r325320. The system call now returns EINVAL
670 when used on a ZFS file. Although the new behavior complies with the
671 standard, some consumers are not prepared to cope with it.
672 One known victim is lld prior to r325420.
675 Building in a FreeBSD src checkout will automatically create object
676 directories now rather than store files in the current directory if
677 'make obj' was not ran. Calling 'make obj' is no longer necessary.
678 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
679 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
683 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
684 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
685 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
686 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
687 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
688 The UNIFIED_OBJDIR option is a transitional feature that will be
689 removed for 12.0 release; please migrate to the new format for any
690 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
691 than hardcoding paths.
694 The native-xtools target no longer installs the files by default to the
695 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
696 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
699 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
700 options are changing from controlling the build if defined / undefined
701 to controlling the build with explicit 'yes' or 'no' values. They will
702 shift to WITH/WITHOUT options to match other options in the system.
705 libstand has turned into a private library for sys/boot use only.
706 It is no longer supported as a public interface outside of sys/boot.
709 The arm port has split armv6 into armv6 and armv7. armv7 is now
710 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
711 and are running a kernel from before r324363, you will need to add
712 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
715 When building multiple kernels using KERNCONF, non-existent KERNCONF
716 files will produce an error and buildkernel will fail. Previously
717 missing KERNCONF files silently failed giving no indication as to
718 why, only to subsequently discover during installkernel that the
719 desired kernel was never built in the first place.
722 The default serial number format for CTL LUNs has changed. This will
723 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
724 or iSCSI clients care about their LUNs' serial numbers. Users who
725 require serial number stability should hardcode serial numbers in
729 For 32-bit arm compiled for hard-float support, soft-floating point
730 binaries now always get their shared libraries from
731 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
732 /usr/libsoft also existed). Only users with a hard-float ld.so, but
733 soft-float everything else should be affected.
736 The geli password typed at boot is now hidden. To restore the previous
737 behavior, see geli(8) for configuration options.
740 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
741 sysctl values. Minor nit, but requires a rebuild of both world/kernel
745 "make check" behavior (made in ^/head@r295380) has been changed to
746 execute from a limited sandbox, as opposed to executing from
750 - The "beforecheck" and "aftercheck" targets are now specified.
751 - ${CHECKDIR} (added in commit noted above) has been removed.
752 - Legacy behavior can be enabled by setting
753 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
755 If the limited sandbox mode is enabled, "make check" will execute
756 "make distribution", then install, execute the tests, and clean up the
757 sandbox if successful.
759 The "make distribution" and "make install" targets are typically run as
760 root to set appropriate permissions and ownership at installation time.
761 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
762 environment if executing "make check" with limited sandbox mode using
763 an unprivileged user.
766 Since the switch to GPT disk labels, fsck for UFS/FFS has been
767 unable to automatically find alternate superblocks. As of r322297,
768 the information needed to find alternate superblocks has been
769 moved to the end of the area reserved for the boot block.
770 Filesystems created with a newfs of this vintage or later
771 will create the recovery information. If you have a filesystem
772 created prior to this change and wish to have a recovery block
773 created for your filesystem, you can do so by running fsck in
774 foreground mode (i.e., do not use the -p or -y options). As it
775 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
776 to which you should answer yes.
779 As of r321665, an NFSv4 server configuration that services
780 Kerberos mounts or clients that do not support the uid/gid in
781 owner/owner_group string capability, must explicitly enable
782 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
783 machine's /etc/rc.conf file.
786 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
787 Please see the 20141231 entry below for information about prerequisites
788 and upgrading, if you are not already using clang 3.5.0 or higher.
791 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
792 r-commands (rlogin, rsh, etc.) to be built with the base system.
795 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
796 a very major ABI incompatible change, so users of FreeBSD/powerpc must
797 be careful when performing source upgrades. It is best to run
798 'make installworld' from an alternate root system, either a live
799 CD/memory stick, or a temporary root partition. Additionally, all ports
800 must be recompiled. powerpc64 is largely unaffected, except in the case
801 of 32-bit compatibility. All 32-bit binaries will be affected.
804 Forward compatibility for the "ino64" project have been committed. This
805 will allow most new binaries to run on older kernels in a limited
806 fashion. This prevents many of the common foot-shooting actions in the
807 upgrade as well as the limited ability to roll back the kernel across
808 the ino64 upgrade. Complicated use cases may not work properly, though
809 enough simpler ones work to allow recovery in most situations.
812 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
813 if you require the GPL compiler.
816 The internal ABI used for communication between the NFS kernel modules
817 was changed by r320085, so __FreeBSD_version was bumped to
818 ensure all the NFS related modules are updated together.
821 The ABI of struct event was changed by extending the data
822 member to 64bit and adding ext fields. For upgrade, same
823 precautions as for the entry 20170523 "ino64" must be
827 The GNU roff toolchain has been removed from base. To render manpages
828 which are not supported by mandoc(1), man(1) can fallback on GNU roff
829 from ports (and recommends to install it).
830 To render roff(7) documents, consider using GNU roff from ports or the
831 heirloom doctools roff toolchain from ports via pkg install groff or
832 via pkg install heirloom-doctools.
835 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
836 smaller runtime footprint builds. This is useful for embedded systems
837 which only require one chipset support.
839 If you load it as a module, make sure this is in /boot/loader.conf:
843 This will load the HAL, all chip/RF backends and if_ath_pci.
844 If you have if_ath_pci in /boot/loader.conf, ensure it is after
845 if_ath or it will not load any HAL chipset support.
847 If you want to selectively load things (eg on ye cheape ARM/MIPS
848 platforms where RAM is at a premium) you should:
851 * load the chip modules in question
852 * load ath_rate, ath_dfs
854 * load if_ath_pci and/or if_ath_ahb depending upon your particular
855 bus bind type - this is where probe/attach is done.
857 For further comments/feedback, poke adrian@ .
860 The "ino64" 64-bit inode project has been committed, which extends
861 a number of types to 64 bits. Upgrading in place requires care and
862 adherence to the documented upgrade procedure.
864 If using a custom kernel configuration ensure that the
865 COMPAT_FREEBSD11 option is included (as during the upgrade the
866 system will be running the ino64 kernel with the existing world).
868 For the safest in-place upgrade begin by removing previous build
869 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
870 full procedure documented below under the heading "To rebuild
871 everything and install it on the current system." Specifically,
872 a reboot is required after installing the new kernel before
876 The NATM framework including the en(4), fatm(4), hatm(4), and
877 patm(4) devices has been removed. Consumers should plan a
878 migration before the end-of-life date for FreeBSD 11.
881 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
882 diff has not been implemented, if those are needed a newer version of
883 GNU diff is available via the diffutils package under the gdiff name.
886 As of r316810 for ipfilter, keep frags is no longer assumed when
887 keep state is specified in a rule. r316810 aligns ipfilter with
888 documentation in man pages separating keep frags from keep state.
889 This allows keep state to be specified without forcing keep frags
890 and allows keep frags to be specified independently of keep state.
891 To maintain previous behaviour, also specify keep frags with
892 keep state (as documented in ipf.conf.5).
895 arm64 builds now use the base system LLD 4.0.0 linker by default,
896 instead of requiring that the aarch64-binutils port or package be
897 installed. To continue using aarch64-binutils, set
898 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
901 The UDP optimization in entry 20160818 that added the sysctl
902 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
903 packets will no longer be treated as L3 broadcast packets.
906 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
907 use any explicitly assigned loopback address available in the jail
908 instead of using the first assigned address of the jail.
911 The ctl.ko module no longer implements the iSCSI target frontend:
912 cfiscsi.ko does instead.
914 If building cfiscsi.ko as a kernel module, the module can be loaded
915 via one of the following methods:
916 - `cfiscsi_load="YES"` in loader.conf(5).
917 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
918 - ctladm(8)/ctld(8), when compiled with iSCSI support
919 (`WITH_ISCSI=yes` in src.conf(5))
921 Please see cfiscsi(4) for more details.
924 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
925 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
926 same source (previously, the dependency of mmcsd.ko on mmc.ko was
927 missing, but mmcsd.ko now will refuse to load if it is incompatible
931 The syntax of ipfw(8) named states was changed to avoid ambiguity.
932 If you have used named states in the firewall rules, you need to modify
933 them after installworld and before rebooting. Now named states must
934 be prefixed with colon.
937 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
938 removed as the userland we provide cannot use them. The KMS version
939 (sys/dev/drm2) supports the same hardware.
942 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
943 Please see the 20141231 entry below for information about prerequisites
944 and upgrading, if you are not already using clang 3.5.0 or higher.
947 The code that provides support for ZFS .zfs/ directory functionality
948 has been reimplemented. It's not possible now to create a snapshot
949 by mkdir under .zfs/snapshot/. That should be the only user visible
953 EISA bus support has been removed. The WITH_EISA option is no longer
957 MCA bus support has been removed.
960 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
961 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
964 The EM_MULTIQUEUE kernel configuration option is deprecated now that
965 the em(4) driver conforms to iflib specifications.
968 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
969 IFLIB. If you have a custom kernel configuration that excludes em(4)
970 but you use igb(4), you need to re-add em(4) to your custom configuration.
973 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
974 Please see the 20141231 entry below for information about prerequisites
975 and upgrading, if you are not already using clang 3.5.0 or higher.
978 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
979 Please see the 20141231 entry below for information about prerequisites
980 and upgrading, if you are not already using clang 3.5.0 or higher.
983 The layout of the pmap structure has changed for powerpc to put the pmap
984 statistics at the front for all CPU variations. libkvm(3) and all tools
985 that link against it need to be recompiled.
988 isl(4) and cyapa(4) drivers now require a new driver,
989 chromebook_platform(4), to work properly on Chromebook-class hardware.
990 On other types of hardware the drivers may need to be configured using
991 device hints. Please see the corresponding manual pages for details.
994 The urtwn(4) driver was merged into rtwn(4) and now consists of
995 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
997 Also, firmware for RTL8188CE was renamed due to possible name
998 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1001 GNU rcs has been removed from base. It is available as packages:
1002 - rcs: Latest GPLv3 GNU rcs version.
1003 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1007 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1008 modules now requires that the kernel configuration contain the
1009 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1012 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1013 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1016 Relocatable object files with the extension of .So have been renamed
1017 to use an extension of .pico instead. The purpose of this change is
1018 to avoid a name clash with shared libraries on case-insensitive file
1019 systems. On those file systems, foo.So is the same file as foo.so.
1022 GNU rcs has been turned off by default. It can (temporarily) be built
1023 again by adding WITH_RCS knob in src.conf.
1024 Otherwise, GNU rcs is available from packages:
1025 - rcs: Latest GPLv3 GNU rcs version.
1026 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1029 The backup_uses_rcs functionality has been removed from rc.subr.
1032 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1033 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1034 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1035 QUEUE_MACRO_DEBUG behavior.
1038 r304787 changed some ioctl interfaces between the iSCSI userspace
1039 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1040 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1044 The UDP receive code has been updated to only treat incoming UDP
1045 packets that were addressed to an L2 broadcast address as L3
1046 broadcast packets. It is not expected that this will affect any
1047 standards-conforming UDP application. The new behaviour can be
1048 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1052 Remove the openbsd_poll system call.
1053 __FreeBSD_version has been bumped because of this.
1056 The stable/11 branch has been created from head@r302406.
1059 The libc stub for the pipe(2) system call has been replaced with
1060 a wrapper that calls the pipe2(2) system call and the pipe(2)
1061 system call is now only implemented by the kernels that include
1062 "options COMPAT_FREEBSD10" in their config file (this is the
1063 default). Users should ensure that this option is enabled in
1064 their kernel or upgrade userspace to r302092 before upgrading their
1068 CAM will now strip leading spaces from SCSI disks' serial numbers.
1069 This will affect users who create UFS filesystems on SCSI disks using
1070 those disk's diskid device nodes. For example, if /etc/fstab
1071 previously contained a line like
1072 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1073 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1074 transforms like gmirror may also be affected. ZFS users should
1078 The bitstring(3) API has been updated with new functionality and
1079 improved performance. But it is binary-incompatible with the old API.
1080 Objects built with the new headers may not be linked against objects
1081 built with the old headers.
1084 The brk and sbrk functions have been removed from libc on arm64.
1085 Binutils from ports has been updated to not link to these
1086 functions and should be updated to the latest version before
1087 installing a new libc.
1090 The armv6 port now defaults to hard float ABI. Limited support
1091 for running both hardfloat and soft float on the same system
1092 is available using the libraries installed with -DWITH_LIBSOFT.
1093 This has only been tested as an upgrade path for installworld
1094 and packages may fail or need manual intervention to run. New
1095 packages will be needed.
1097 To update an existing self-hosted armv6hf system, you must add
1098 TARGET_ARCH=armv6 on the make command line for both the build
1099 and the install steps.
1102 Kernel modules compiled outside of a kernel build now default to
1103 installing to /boot/modules instead of /boot/kernel. Many kernel
1104 modules built this way (such as those in ports) already overrode
1105 KMODDIR explicitly to install into /boot/modules. However,
1106 manually building and installing a module from /sys/modules will
1107 now install to /boot/modules instead of /boot/kernel.
1110 The CAM I/O scheduler has been committed to the kernel. There should be
1111 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1112 list of known rogues that claim support for this but actually corrupt
1113 data is believed to be complete, be on the lookout for data
1114 corruption. The known rogue list is believed to be complete:
1116 o Crucial MX100, M550 drives with MU01 firmware.
1117 o Micron M510 and M550 drives with MU01 firmware.
1118 o Micron M500 prior to MU07 firmware
1119 o Samsung 830, 840, and 850 all firmwares
1120 o FCCT M500 all firmwares
1122 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1123 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1124 updated firmware. Black listed drives will work correctly because these
1125 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1126 this list is the same as found in Linux, it's believed there are no
1127 other rogues in the market place. All other models from the above
1130 To be safe, if you are at all concerned, you can quirk each of your
1131 drives to prevent NCQ from being sent by setting:
1132 kern.cam.ada.X.quirks="0x2"
1133 in loader.conf. If the drive requires the 4k sector quirk, set the
1134 quirks entry to 0x3.
1137 The FAST_DEPEND build option has been removed and its functionality is
1138 now the one true way. The old mkdep(1) style of 'make depend' has
1139 been removed. See 20160311 for further details.
1142 Resource range types have grown from unsigned long to uintmax_t. All
1143 drivers, and anything using libdevinfo, need to be recompiled.
1146 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1147 builds. It no longer runs mkdep(1) during 'make depend', and the
1148 'make depend' stage can safely be skipped now as it is auto ran
1149 when building 'make all' and will generate all SRCS and DPSRCS before
1150 building anything else. Dependencies are gathered at compile time with
1151 -MF flags kept in separate .depend files per object file. Users should
1152 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1153 stale .depend files.
1156 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1157 kernel modules. Therefore, if you load any kernel modules at boot time,
1158 please install the boot loaders after you install the kernel, but before
1162 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1163 make installkernel KERNCONF=YOUR_KERNEL_HERE
1164 make -C sys/boot install
1165 <reboot in single user>
1167 Then follow the usual steps, described in the General Notes section,
1171 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1172 see the 20141231 entry below for information about prerequisites and
1173 upgrading, if you are not already using clang 3.5.0 or higher.
1176 The AIO subsystem is now a standard part of the kernel. The
1177 VFS_AIO kernel option and aio.ko kernel module have been removed.
1178 Due to stability concerns, asynchronous I/O requests are only
1179 permitted on sockets and raw disks by default. To enable
1180 asynchronous I/O requests on all file types, set the
1181 vfs.aio.enable_unsafe sysctl to a non-zero value.
1184 The ELF object manipulation tool objcopy is now provided by the
1185 ELF Tool Chain project rather than by GNU binutils. It should be a
1186 drop-in replacement, with the addition of arm64 support. The
1187 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1188 to obtain the GNU version if necessary.
1191 Building ZFS pools on top of zvols is prohibited by default. That
1192 feature has never worked safely; it's always been prone to deadlocks.
1193 Using a zvol as the backing store for a VM guest's virtual disk will
1194 still work, even if the guest is using ZFS. Legacy behavior can be
1195 restored by setting vfs.zfs.vol.recursive=1.
1198 The NONE and HPN patches has been removed from OpenSSH. They are
1199 still available in the security/openssh-portable port.
1202 With the addition of ypldap(8), a new _ypldap user is now required
1203 during installworld. "mergemaster -p" can be used to add the user
1204 prior to installworld, as documented in the handbook.
1207 The tftp loader (pxeboot) now uses the option root-path directive. As a
1208 consequence it no longer looks for a pxeboot.4th file on the tftp
1209 server. Instead it uses the regular /boot infrastructure as with the
1213 The code to start recording plug and play data into the modules has
1214 been committed. While the old tools will properly build a new kernel,
1215 a number of warnings about "unknown metadata record 4" will be produced
1216 for an older kldxref. To avoid such warnings, make sure to rebuild
1217 the kernel toolchain (or world). Make sure that you have r292078 or
1218 later when trying to build 292077 or later before rebuilding.
1221 Debug data files are now built by default with 'make buildworld' and
1222 installed with 'make installworld'. This facilitates debugging but
1223 requires more disk space both during the build and for the installed
1224 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1228 r291527 changed the internal interface between the nfsd.ko and
1229 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1230 __FreeBSD_version has been bumped because of this.
1233 Add support for unicode collation strings leads to a change of
1234 order of files listed by ls(1) for example. To get back to the old
1235 behaviour, set LC_COLLATE environment variable to "C".
1237 Databases administrators will need to reindex their databases given
1238 collation results will be different.
1240 Due to a bug in install(1) it is recommended to remove the ancient
1241 locales before running make installworld.
1243 rm -rf /usr/share/locale/*
1246 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1247 libcrypto.so.7 or libssl.so.7 must be recompiled.
1250 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1251 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1252 should be replaced with isp_2400 and isp_2500 modules respectively.
1255 The build previously allowed using 'make -n' to not recurse into
1256 sub-directories while showing what commands would be executed, and
1257 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1258 and 'make -N' will not.
1261 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1262 and etcupdate will now use this file. A custom sendmail.cf is now
1263 updated via this mechanism rather than via installworld. If you had
1264 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1265 want to remove the exclusion or change it to "always install".
1266 /etc/mail/sendmail.cf is now managed the same way regardless of
1267 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1268 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1271 Compatibility shims for legacy ATA device names have been removed.
1272 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1273 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1274 environment variables, /dev/ad* and /dev/ar* symbolic links.
1277 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1278 Please see the 20141231 entry below for information about prerequisites
1279 and upgrading, if you are not already using clang 3.5.0 or higher.
1282 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1283 and renamed from .symbols to .debug. This reduces the size requirements
1284 on the boot partition or file system and provides consistency with
1285 userland debug files.
1287 When using the supported kernel installation method the
1288 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1289 as is done with /boot/kernel.
1291 Developers wishing to maintain the historical behavior of installing
1292 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1295 The wireless drivers had undergone changes that remove the 'parent
1296 interface' from the ifconfig -l output. The rc.d network scripts
1297 used to check presence of a parent interface in the list, so old
1298 scripts would fail to start wireless networking. Thus, etcupdate(3)
1299 or mergemaster(8) run is required after kernel update, to update your
1300 rc.d scripts in /etc.
1303 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1304 These configurations are now automatically interpreted as
1305 'scrub fragment reassemble'.
1308 Kernel-loadable modules for the random(4) device are back. To use
1309 them, the kernel must have
1312 options RANDOM_LOADABLE
1314 kldload(8) can then be used to load random_fortuna.ko
1315 or random_yarrow.ko. Please note that due to the indirect
1316 function calls that the loadable modules need to provide,
1317 the build-in variants will be slightly more efficient.
1319 The random(4) kernel option RANDOM_DUMMY has been retired due to
1320 unpopularity. It was not all that useful anyway.
1323 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1324 Control over building the ELF Tool Chain tools is now provided by
1325 the WITHOUT_TOOLCHAIN knob.
1328 The polarity of Pulse Per Second (PPS) capture events with the
1329 uart(4) driver has been corrected. Prior to this change the PPS
1330 "assert" event corresponded to the trailing edge of a positive PPS
1331 pulse and the "clear" event was the leading edge of the next pulse.
1333 As the width of a PPS pulse in a typical GPS receiver is on the
1334 order of 1 millisecond, most users will not notice any significant
1335 difference with this change.
1337 Anyone who has compensated for the historical polarity reversal by
1338 configuring a negative offset equal to the pulse width will need to
1339 remove that workaround.
1342 The default group assigned to /dev/dri entries has been changed
1343 from 'wheel' to 'video' with the id of '44'. If you want to have
1344 access to the dri devices please add yourself to the video group
1347 # pw groupmod video -m $USER
1350 The menu.rc and loader.rc files will now be replaced during
1351 upgrades. Please migrate local changes to menu.rc.local and
1352 loader.rc.local instead.
1355 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1356 strings and strip have been removed. The src.conf(5) knob
1357 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1360 As ZFS requires more kernel stack pages than is the default on some
1361 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1362 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1364 Please consider using 'options KSTACK_PAGES=X' where X is greater
1365 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1368 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1369 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1370 default, i.e., they will not contain "::". For example, instead
1371 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1372 to have a more specific match, such as different map entries for
1373 IPv6:0:0 vs IPv6:0. This change requires that configuration
1374 data (including maps, files, classes, custom ruleset, etc.) must
1375 use the same format, so make certain such configuration data is
1376 upgrading. As a very simple check search for patterns like
1377 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1378 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1379 the cf option UseCompressedIPv6Addresses.
1382 The default kernel entropy-processing algorithm is now
1383 Fortuna, replacing Yarrow.
1385 Assuming you have 'device random' in your kernel config
1386 file, the configurations allow a kernel option to override
1387 this default. You may choose *ONE* of:
1389 options RANDOM_YARROW # Legacy /dev/random algorithm.
1390 options RANDOM_DUMMY # Blocking-only driver.
1392 If you have neither, you get Fortuna. For most people,
1393 read no further, Fortuna will give a /dev/random that works
1394 like it always used to, and the difference will be irrelevant.
1396 If you remove 'device random', you get *NO* kernel-processed
1397 entropy at all. This may be acceptable to folks building
1398 embedded systems, but has complications. Carry on reading,
1399 and it is assumed you know what you need.
1401 *PLEASE* read random(4) and random(9) if you are in the
1402 habit of tweaking kernel configs, and/or if you are a member
1403 of the embedded community, wanting specific and not-usual
1404 behaviour from your security subsystems.
1406 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1407 random', you will NOT have a functioning /dev/random, and
1408 many cryptographic features will not work, including SSH.
1409 You may also find strange behaviour from the random(3) set
1410 of library functions, in particular sranddev(3), srandomdev(3)
1411 and arc4random(3). The reason for this is that the KERN_ARND
1412 sysctl only returns entropy if it thinks it has some to
1413 share, and with RANDOM_DUMMY or no 'device random' this
1417 An additional fix for the issue described in the 20150614 sendmail
1418 entry below has been committed in revision 284717.
1421 FreeBSD's old make (fmake) has been removed from the system. It is
1422 available as the devel/fmake port or via pkg install fmake.
1425 The fix for the issue described in the 20150614 sendmail entry
1426 below has been committed in revision 284436. The work
1427 around described in that entry is no longer needed unless the
1428 default setting is overridden by a confDH_PARAMETERS configuration
1429 setting of '5' or pointing to a 512 bit DH parameter file.
1432 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1433 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1434 and devel/kyua to version 0.20+ and adjust any calling code to work
1435 with Kyuafile and kyua.
1438 The import of openssl to address the FreeBSD-SA-15:10.openssl
1439 security advisory includes a change which rejects handshakes
1440 with DH parameters below 768 bits. sendmail releases prior
1441 to 8.15.2 (not yet released), defaulted to a 512 bit
1442 DH parameter setting for client connections. To work around
1443 this interoperability, sendmail can be configured to use a
1444 2048 bit DH parameter by:
1446 1. Edit /etc/mail/`hostname`.mc
1447 2. If a setting for confDH_PARAMETERS does not exist or
1448 exists and is set to a string beginning with '5',
1449 replace it with '2'.
1450 3. If a setting for confDH_PARAMETERS exists and is set to
1451 a file path, create a new file with:
1452 openssl dhparam -out /path/to/file 2048
1453 4. Rebuild the .cf file:
1454 cd /etc/mail/; make; make install
1455 5. Restart sendmail:
1456 cd /etc/mail/; make restart
1458 A sendmail patch is coming, at which time this file will be
1462 Generation of legacy formatted entries have been disabled by default
1463 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1464 entries were converted to use the new format by default when the new,
1465 machine independent format have been added and supported since FreeBSD
1468 Please see the pwd_mkdb(8) manual page for further details.
1471 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1472 20141231 entry below for information about prerequisites and upgrading,
1473 if you are not already using 3.5.0 or higher.
1476 TI platform code switched to using vendor DTS files and this update
1477 may break existing systems running on Beaglebone, Beaglebone Black,
1480 - dtb files should be regenerated/reinstalled. Filenames are the
1481 same but content is different now
1482 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1483 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1484 addressing scheme is now pin 25 on /dev/gpioc3.
1485 - Pandaboard: /etc/ttys should be updated, serial console device is
1486 now /dev/ttyu2, not /dev/ttyu0
1489 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1490 If you need the GNU extension from groff soelim(1), install groff
1491 from package: pkg install groff, or via ports: textproc/groff.
1494 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1495 defined in symlink(7); previously symlinks were silently ignored.
1498 The const qualifier has been removed from iconv(3) to comply with
1499 POSIX. The ports tree is aware of this from r384038 onwards.
1502 Libraries specified by LIBADD in Makefiles must have a corresponding
1503 DPADD_<lib> variable to ensure correct dependencies. This is now
1504 enforced in src.libnames.mk.
1507 From legacy ata(4) driver was removed support for SATA controllers
1508 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1509 Kernel modules ataahci and ataadaptec were removed completely,
1510 replaced by ahci and mvs modules respectively.
1513 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1514 the 20141231 entry below for information about prerequisites and
1515 upgrading, if you are not already using 3.5.0 or higher.
1518 The 32-bit PowerPC kernel has been changed to a position-independent
1519 executable. This can only be booted with a version of loader(8)
1520 newer than January 31, 2015, so make sure to update both world and
1521 kernel before rebooting.
1524 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1525 but before r278950, the RNG was not seeded properly. Immediately
1526 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1527 ssh keys or openssl keys) that were generated w/ a kernel from that
1528 range. This does not affect programs that directly used /dev/random
1529 or /dev/urandom. All userland uses of arc4random(3) are affected.
1532 The autofs(4) ABI was changed in order to restore binary compatibility
1533 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1534 with the new kernel.
1537 The powerpc64 kernel has been changed to a position-independent
1538 executable. This can only be booted with a new version of loader(8),
1539 so make sure to update both world and kernel before rebooting.
1542 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1543 only release, no new features have been added. Please see the 20141231
1544 entry below for information about prerequisites and upgrading, if you
1545 are not already using 3.5.0.
1548 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1549 taken from the ELF Tool Chain project rather than GNU binutils. They
1550 should be drop-in replacements, with the addition of arm64 support.
1551 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1552 binutils tools, if necessary. See 20150805 for updated information.
1555 The default Unbound configuration now enables remote control
1556 using a local socket. Users who have already enabled the
1557 local_unbound service should regenerate their configuration
1558 by running "service local_unbound setup" as root.
1561 The GNU texinfo and GNU info pages have been removed.
1562 To be able to view GNU info pages please install texinfo from ports.
1565 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1567 As of this release, a prerequisite for building clang, llvm and lldb is
1568 a C++11 capable compiler and C++11 standard library. This means that to
1569 be able to successfully build the cross-tools stage of buildworld, with
1570 clang as the bootstrap compiler, your system compiler or cross compiler
1571 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1572 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1575 On any standard FreeBSD 10.x or 11.x installation, where clang and
1576 libc++ are on by default (that is, on x86 or arm), this should work out
1579 On 9.x installations where clang is enabled by default, e.g. on x86 and
1580 powerpc, libc++ will not be enabled by default, so libc++ should be
1581 built (with clang) and installed first. If both clang and libc++ are
1582 missing, build clang first, then use it to build libc++.
1584 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1585 the instructions for 9.x above.
1587 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1588 default, and do not build clang.
1590 Many embedded systems are resource constrained, and will not be able to
1591 build clang in a reasonable time, or in some cases at all. In those
1592 cases, cross building bootable systems on amd64 is a workaround.
1594 This new version of clang introduces a number of new warnings, of which
1595 the following are most likely to appear:
1599 This warns in two cases, for both C and C++:
1600 * When the code is trying to take the absolute value of an unsigned
1601 quantity, which is effectively a no-op, and almost never what was
1602 intended. The code should be fixed, if at all possible. If you are
1603 sure that the unsigned quantity can be safely cast to signed, without
1604 loss of information or undefined behavior, you can add an explicit
1605 cast, or disable the warning.
1607 * When the code is trying to take an absolute value, but the called
1608 abs() variant is for the wrong type, which can lead to truncation.
1609 If you want to disable the warning instead of fixing the code, please
1610 make sure that truncation will not occur, or it might lead to unwanted
1613 -Wtautological-undefined-compare and
1614 -Wundefined-bool-conversion
1616 These warn when C++ code is trying to compare 'this' against NULL, while
1617 'this' should never be NULL in well-defined C++ code. However, there is
1618 some legacy (pre C++11) code out there, which actively abuses this
1619 feature, which was less strictly defined in previous C++ versions.
1621 Squid and openjdk do this, for example. The warning can be turned off
1622 for C++98 and earlier, but compiling the code in C++11 mode might result
1623 in unexpected behavior; for example, the parts of the program that are
1624 unreachable could be optimized away.
1627 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1628 kernel sources have been removed. The .h files remain, since some
1629 utilities include them. This will need to be fixed later.
1630 If "mount -t oldnfs ..." is attempted, it will fail.
1631 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1632 the utilities will report errors.
1635 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1636 directories to top level SUBDIR variable when their parent
1637 directory is included in LOCAL_DIRS. Users with build systems with
1638 such hierarchies and without SUBDIR entries in the parent
1639 directory Makefiles should add them or add the directories to
1643 faith(4) and faithd(8) have been removed from the base system. Faith
1644 has been obsolete for a very long time.
1647 vt(4), the new console driver, is enabled by default. It brings
1648 support for Unicode and double-width characters, as well as
1649 support for UEFI and integration with the KMS kernel video
1652 You may need to update your console settings in /etc/rc.conf,
1653 most probably the keymap. During boot, /etc/rc.d/syscons will
1654 indicate what you need to do.
1656 vt(4) still has issues and lacks some features compared to
1657 syscons(4). See the wiki for up-to-date information:
1658 https://wiki.freebsd.org/Newcons
1660 If you want to keep using syscons(4), you can do so by adding
1661 the following line to /boot/loader.conf:
1665 pjdfstest has been integrated into kyua as an opt-in test suite.
1666 Please see share/doc/pjdfstest/README for more details on how to
1670 gperf has been removed from the base system for architectures
1671 that use clang. Ports that require gperf will obtain it from the
1675 pjdfstest has been moved from tools/regression/pjdfstest to
1679 At svn r271982, The default linux compat kernel ABI has been adjusted
1680 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1681 update. If you wish to continue using the linux-f10 compat ports,
1682 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1683 encouraged to update their linux-compat packages to linux-c6 during
1684 their next update cycle.
1687 The ofwfb driver, used to provide a graphics console on PowerPC when
1688 using vt(4), no longer allows mmap() of all physical memory. This
1689 will prevent Xorg on PowerPC with some ATI graphics cards from
1690 initializing properly unless x11-servers/xorg-server is updated to
1694 The xdev targets have been converted to using TARGET and
1695 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1698 The default unbound configuration has been modified to address
1699 issues with reverse lookups on networks that use private
1700 address ranges. If you use the local_unbound service, run
1701 "service local_unbound setup" as root to regenerate your
1702 configuration, then "service local_unbound reload" to load the
1706 The GNU texinfo and GNU info pages are not built and installed
1707 anymore, WITH_INFO knob has been added to allow to built and install
1709 UPDATE: see 20150102 entry on texinfo's removal
1712 The GNU readline library is now an INTERNALLIB - that is, it is
1713 statically linked into consumers (GDB and variants) in the base
1714 system, and the shared library is no longer installed. The
1715 devel/readline port is available for third party software that
1719 The Itanium architecture (ia64) has been removed from the list of
1720 known architectures. This is the first step in the removal of the
1724 Commit r268115 has added NFSv4.1 server support, merged from
1725 projects/nfsv4.1-server. Since this includes changes to the
1726 internal interfaces between the NFS related modules, a full
1727 build of the kernel and modules will be necessary.
1728 __FreeBSD_version has been bumped.
1731 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1732 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1733 which differs from the behaviour controlled by this knob.)
1736 Maximal length of the serial number in CTL was increased from 16 to
1737 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1738 and ctld, need to be rebuilt to work with a new kernel.
1741 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1742 1 respectively to match the upstream numbers. They were out of
1743 sync because, when they were originally added to FreeBSD, the
1744 upstream versions were not respected. These libraries are private
1745 and not yet built by default, so renumbering them should be a
1746 non-issue. However, unclean source trees will yield broken test
1747 programs once the operator executes "make delete-old-libs" after a
1748 "make installworld".
1750 Additionally, the atf-sh binary was made private by moving it into
1751 /usr/libexec/. Already-built shell test programs will keep the
1752 path to the old binary so they will break after "make delete-old"
1755 If you are using WITH_TESTS=yes (not the default), wipe the object
1756 tree and rebuild from scratch to prevent spurious test failures.
1757 This is only needed once: the misnumbered libraries and misplaced
1758 binaries have been added to OptionalObsoleteFiles.inc so they will
1759 be removed during a clean upgrade.
1762 Clang and llvm have been upgraded to 3.4.1 release.
1765 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1766 be removed to avoid issues in the future (and has been added to
1770 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1771 past, it affected all builds that used the bsd.*.mk files. The old
1772 behavior was a bug, but people may have relied upon it. To get this
1773 behavior back, you can .include /etc/src.conf from /etc/make.conf
1774 (which is still global and isn't changed). This also changes the
1775 behavior of incremental builds inside the tree of individual
1776 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1777 Although this has survived make universe and some upgrade scenarios,
1778 other upgrade scenarios may have broken. At least one form of
1779 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1780 as well... In cases where MAKESYSPATH isn't working with this
1781 setting, you'll need to set it to the full path to your tree.
1783 One side effect of all this cleaning up is that bsd.compiler.mk
1784 is no longer implicitly included by bsd.own.mk. If you wish to
1785 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1789 The lindev device has been removed since /dev/full has been made a
1790 standard device. __FreeBSD_version has been bumped.
1793 The knob WITHOUT_VI was added to the base system, which controls
1794 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1795 in order to reorder files share/termcap and didn't build ex(1) as a
1796 build tool, so building/installing with WITH_VI is highly advised for
1797 build hosts for older releases.
1799 This issue has been fixed in stable/9 and stable/10 in r277022 and
1800 r276991, respectively.
1803 The YES_HESIOD knob has been removed. It has been obsolete for
1804 a decade. Please move to using WITH_HESIOD instead or your builds
1805 will silently lack HESIOD.
1808 The uart(4) driver has been changed with respect to its handling
1809 of the low-level console. Previously the uart(4) driver prevented
1810 any process from changing the baudrate or the CLOCAL and HUPCL
1811 control flags. By removing the restrictions, operators can make
1812 changes to the serial console port without having to reboot.
1813 However, when getty(8) is started on the serial device that is
1814 associated with the low-level console, a misconfigured terminal
1815 line in /etc/ttys will now have a real impact.
1816 Before upgrading the kernel, make sure that /etc/ttys has the
1817 serial console device configured as 3wire without baudrate to
1818 preserve the previous behaviour. E.g:
1819 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1822 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1823 to improve performance. To re-enable it, if needed, run rpcbind
1824 with command line option -W.
1827 Switched back to the GPL dtc compiler due to updates in the upstream
1828 dts files not being supported by the BSDL dtc compiler. You will need
1829 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1830 may result while building dtb files during a kernel build if you fail
1831 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1834 Clang and llvm have been upgraded to 3.4 release.
1837 The nve(4) driver has been removed. Please use the nfe(4) driver
1838 for NVIDIA nForce MCP Ethernet adapters instead.
1841 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1842 This could cause certain C++ applications using shared libraries built
1843 against the previous version of libc++ to crash. The incompatibility
1844 has now been fixed, but any C++ applications or shared libraries built
1845 between r261283 and r261801 should be recompiled.
1848 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1849 capability mode support. Please note that enabling the feature in
1850 kernel is still highly recommended.
1853 OpenSSH is now built with sandbox support, and will use sandbox as
1854 the default privilege separation method. This requires Capsicum
1855 capability mode support in kernel.
1858 The libelf and libdwarf libraries have been updated to newer
1859 versions from upstream. Shared library version numbers for
1860 these two libraries were bumped. Any ports or binaries
1861 requiring these two libraries should be recompiled.
1862 __FreeBSD_version is bumped to 1100006.
1865 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1866 instead of providing an explicit one, this would prevent such
1867 Makefile from providing its own Kyuafile in the future during
1868 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1869 intervention is needed to clean an objdir if you use NO_CLEAN:
1870 # find /usr/obj -name Kyuafile | xargs rm -f
1873 The behavior of gss_pseudo_random() for the krb5 mechanism
1874 has changed, for applications requesting a longer random string
1875 than produced by the underlying enctype's pseudo-random() function.
1876 In particular, the random string produced from a session key of
1877 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1878 be different at the 17th octet and later, after this change.
1879 The counter used in the PRF+ construction is now encoded as a
1880 big-endian integer in accordance with RFC 4402.
1881 __FreeBSD_version is bumped to 1100004.
1884 The WITHOUT_ATF build knob has been removed and its functionality
1885 has been subsumed into the more generic WITHOUT_TESTS. If you were
1886 using the former to disable the build of the ATF libraries, you
1887 should change your settings to use the latter.
1890 The default version of mtree is nmtree which is obtained from
1891 NetBSD. The output is generally the same, but may vary
1892 slightly. If you found you need identical output adding
1893 "-F freebsd9" to the command line should do the trick. For the
1894 time being, the old mtree is available as fmtree.
1897 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1898 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1899 1.1.4_8 and verify bsdyml not linked in, before running "make
1901 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1903 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1906 The stable/10 branch has been created in subversion from head
1913 Avoid using make -j when upgrading. While generally safe, there are
1914 sometimes problems using -j to upgrade. If your upgrade fails with
1915 -j, please try again without -j. From time to time in the past there
1916 have been problems using -j with buildworld and/or installworld. This
1917 is especially true when upgrading between "distant" versions (eg one
1918 that cross a major release boundary or several minor releases, or when
1919 several months have passed on the -current branch).
1921 Sometimes, obscure build problems are the result of environment
1922 poisoning. This can happen because the make utility reads its
1923 environment when searching for values for global variables. To run
1924 your build attempts in an "environmental clean room", prefix all make
1925 commands with 'env -i '. See the env(1) manual page for more details.
1927 When upgrading from one major version to another it is generally best to
1928 upgrade to the latest code in the currently installed branch first, then
1929 do an upgrade to the new branch. This is the best-tested upgrade path,
1930 and has the highest probability of being successful. Please try this
1931 approach if you encounter problems with a major version upgrade. Since
1932 the stable 4.x branch point, one has generally been able to upgrade from
1933 anywhere in the most recent stable branch to head / current (or even the
1934 last couple of stable branches). See the top of this file when there's
1937 When upgrading a live system, having a root shell around before
1938 installing anything can help undo problems. Not having a root shell
1939 around can lead to problems if pam has changed too much from your
1940 starting point to allow continued authentication after the upgrade.
1942 This file should be read as a log of events. When a later event changes
1943 information of a prior event, the prior event should not be deleted.
1944 Instead, a pointer to the entry with the new information should be
1945 placed in the old entry. Readers of this file should also sanity check
1946 older entries before relying on them blindly. Authors of new entries
1947 should write them with this in mind.
1951 When upgrading the boot ZFS pool to a new version, always follow
1954 1.) recompile and reinstall the ZFS boot loader and boot block
1955 (this is part of "make buildworld" and "make installworld")
1957 2.) update the ZFS boot block on your boot drive
1959 The following example updates the ZFS boot block on the first
1960 partition (freebsd-boot) of a GPT partitioned drive ada0:
1961 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1963 Non-boot pools do not need these updates.
1967 If you are updating from a prior version of FreeBSD (even one just
1968 a few days old), you should follow this procedure. It is the most
1969 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1971 make kernel-toolchain
1972 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1973 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1975 To test a kernel once
1976 ---------------------
1977 If you just want to boot a kernel once (because you are not sure
1978 if it works, or if you want to boot a known bad kernel to provide
1979 debugging information) run
1980 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1981 nextboot -k testkernel
1983 To rebuild everything and install it on the current system.
1984 -----------------------------------------------------------
1985 # Note: sometimes if you are running current you gotta do more than
1986 # is listed here if you are upgrading from a really old current.
1988 <make sure you have good level 0 dumps>
1990 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1991 make installkernel KERNCONF=YOUR_KERNEL_HERE
1993 <reboot in single user> [3]
2000 To cross-install current onto a separate partition
2001 --------------------------------------------------
2002 # In this approach we use a separate partition to hold
2003 # current's root, 'usr', and 'var' directories. A partition
2004 # holding "/", "/usr" and "/var" should be about 2GB in
2007 <make sure you have good level 0 dumps>
2010 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2011 <maybe newfs current's root partition>
2012 <mount current's root partition on directory ${CURRENT_ROOT}>
2013 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2014 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2015 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2016 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2017 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2018 <reboot into current>
2019 <do a "native" rebuild/install as described in the previous section>
2020 <maybe install compatibility libraries from ports/misc/compat*>
2024 To upgrade in-place from stable to current
2025 ----------------------------------------------
2026 <make sure you have good level 0 dumps>
2028 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2029 make installkernel KERNCONF=YOUR_KERNEL_HERE
2031 <reboot in single user> [3]
2038 Make sure that you've read the UPDATING file to understand the
2039 tweaks to various things you need. At this point in the life
2040 cycle of current, things change often and you are on your own
2041 to cope. The defaults can also change, so please read ALL of
2042 the UPDATING entries.
2044 Also, if you are tracking -current, you must be subscribed to
2045 freebsd-current@freebsd.org. Make sure that before you update
2046 your sources that you have read and understood all the recent
2047 messages there. If in doubt, please track -stable which has
2048 much fewer pitfalls.
2050 [1] If you have third party modules, such as vmware, you
2051 should disable them at this point so they don't crash your
2054 [3] From the bootblocks, boot -s, and then do
2059 adjkerntz -i # if CMOS is wall time
2060 Also, when doing a major release upgrade, it is required that
2061 you boot into single user mode to do the installworld.
2063 [4] Note: This step is non-optional. Failure to do this step
2064 can result in a significant reduction in the functionality of the
2065 system. Attempting to do it by hand is not recommended and those
2066 that pursue this avenue should read this file carefully, as well
2067 as the archives of freebsd-current and freebsd-hackers mailing lists
2068 for potential gotchas. The -U option is also useful to consider.
2069 See mergemaster(8) for more information.
2071 [5] Usually this step is a no-op. However, from time to time
2072 you may need to do this if you get unknown user in the following
2073 step. It never hurts to do it all the time. You may need to
2074 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2075 install) after the buildworld before this step if you last updated
2076 from current before 20130425 or from -stable before 20130430.
2078 [6] This only deletes old files and directories. Old libraries
2079 can be deleted by "make delete-old-libs", but you have to make
2080 sure that no program is using those libraries anymore.
2082 [8] The new kernel must be able to run existing binaries used by
2083 an installworld. When upgrading across major versions, the new
2084 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2085 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2086 binaries). Failure to do so may leave you with a system that is
2087 hard to boot to recover. A GENERIC kernel will include suitable
2088 compatibility options to run binaries from older branches.
2090 Make sure that you merge any new devices from GENERIC since the
2091 last time you updated your kernel config file.
2093 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2094 "?=" instead of the "=" assignment operator, so that buildworld can
2095 override the CPUTYPE if it needs to.
2097 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2098 not on the command line, or in /etc/make.conf. buildworld will
2099 warn if it is improperly defined.
2102 This file contains a list, in reverse chronological order, of major
2103 breakages in tracking -current. It is not guaranteed to be a complete
2104 list of such breakages, and only contains entries since September 23, 2011.
2105 If you need to see UPDATING entries from before that date, you will need
2106 to fetch an UPDATING file from an older FreeBSD release.
2108 Copyright information:
2110 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2112 Redistribution, publication, translation and use, with or without
2113 modification, in full or in part, in any form or format of this
2114 document are permitted without further permission from the author.
2116 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2117 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2118 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2119 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2120 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2121 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2122 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2123 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2124 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2125 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2126 POSSIBILITY OF SUCH DAMAGE.
2128 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob