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