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 20210629: p9 FreeBSD-EN-21:19.libcasper
20 FreeBSD-EN-21:22.linux_futex
22 libcasper assertion failures [EN-21:19.libcasper]
24 Linux compatibility layer futex(2) system call vulnerability [EN-21:22.linux_futex]
26 20210601: p8 FreeBSD-EN-21:17.libradius
28 Incorrect validation in rad_get_attr(3) [FreeBSD-EN-21:17.libradius]
30 20210526: p7 FreeBSD-EN-21:11.aesni
33 FreeBSD-SA-21:12.libradius
35 Race condition in aesni(4) encrypt-then-auth operations [FreeBSD-EN-21:11.aesni]
37 pms(4) data corruption [FreeBSD-EN-21:14.pms]
39 SMAP bypass [FreeBSD-SA-21:11.smap]
41 Missing message validation in libradius(3) [FreeBSD-SA-21:12.libradius]
43 20210406: p6 FreeBSD-EN-21:09.pf
46 FreeBSD-SA-21:09.accept_filter
47 FreeBSD-SA-21:10.jail_mount
49 net.pf.request_maxcount not settable from loader.conf(5) [EN-21:09.pf]
51 lldb abort on print command [EN-21:10.lldb]
53 Memory disclosure by stale virtual memory mapping [SA-21:08.vm]
55 Double free in accept_filter(9) socket configuration interface [SA-21:09.accept_filter]
57 Jail escape possible by mounting over jail root [SA-21:10.jail_mount]
59 20210325: p5 FreeBSD-SA-21:07.openssl
61 Fix multiple OpenSSL issues [SA-21:07.openssl]
63 20210223: p4 FreeBSD-SA-21:03.pam_login_access
64 FreeBSD-SA-21:04.jail_remove
65 FreeBSD-SA-21:05.jail_chdir
67 FreeBSD-EN-21:06.microcode
68 FreeBSD-EN-21:07.caroot
69 FreeBSD-EN-21:08.freebsd-update
71 login.access fails to apply rules [SA-21:03.pam_login_access]
73 jail_remove(2) fails to kill all jailed processes [SA-21:04.jail_remove]
75 jail_attach(2) relies on the caller to change the cwd [SA-21:05.jail_chdir]
77 Xen grant mapping error handling issues [SA-21:06.xen]
79 Boot-time microcode loading causes a boot hang [EN-21:06.microcode]
81 Root certificate bundle update [EN-21:07.caroot]
83 freebsd-update passwd regeneration [EN-21:08.freebsd-update]
85 20210128: p3 FreeBSD-EN-21:01.tzdata
88 FreeBSD-SA-21:01.fsdisclosure
89 FreeBSD-SA-21:02.xenoom
91 Update timezone database information [EN-21:01.tzdata]
93 Panic when destroying VNET and epair simultaneously [EN-21:03.vnet]
95 zfs recv fails to propagate snapshot deletion [EN-21:04.zfs]
97 Uninitialized file system kernel stack leaks [SA-21:01.fsdisclosure]
99 Xen guest-triggered out of memory [SA-21:02.xenoom]
101 20201208: p2 FreeBSD-SA-20:33.openssl
103 Fix OpenSSL NULL pointer de-reference. [SA-20:33.openssl]
105 20201201: p1 FreeBSD-EN-20:19.audit
106 FreeBSD-EN-20:20.tzdata
107 FreeBSD-EN-20:21.ipfw
108 FreeBSD-EN-20:22.callout
109 FreeBSD-SA-20:31.icmp6
110 FreeBSD-SA-20:32.rtsold
112 Fix execve/fexecve system call auditing. [EN-20:19.audit]
114 Update timezone database information. [EN-20:20.tzdata]
116 Fix uninitialized variable in ipfw. [EN-20:21.ipfw]
118 Fix race condition in callout CPU migration. [EN-20:22.callout]
120 Fix ICMPv6 use-after-free in error message handling. [SA-20:31.icmp6]
122 Fix multiple vulnerabilities in rtsold. [SA-20:32.rtsold]
127 20200915: p1 FreeBSD-SA-20:27.ure
128 FreeBSD-SA-20:28.bhyve_vmcs
129 FreeBSD-SA-20:29.bhyve_svm
130 FreeBSD-SA-20:30.ftpd
132 Fix ure device driver susceptible to packet-in-packet attack.
135 Fix bhyve privilege escalation via VMCS access. [SA-20:28.bhyve_vmcs]
137 Fix bhyve SVM guest escape. [SA-20:29.bhyve_svm]
139 Fix ftpd privilege escalation via ftpchroot. [SA-20:30.ftpd]
142 The make.conf(5) MALLOC_PRODUCTION variable, used for disabling and
143 enabling assertions and statistics gathering in malloc(3), has been
144 migrated to a src.conf(5) WITH/WITHOUT_MALLOC_PRODUCTION option.
146 On stable branches, WITH_MALLOC_PRODUCTION is set by default, which
147 means that malloc(3) has assertions and statistics gathering disabled,
148 for improved performance.
150 For backwards compatibility, the make.conf(5) MALLOC_PRODUCTION is still
151 honored, but it is now deprecated and undocumented.
154 The resume code now notifies devd with the 'kernel' system
155 rather than the old 'kern' subsystem to be consistent with
156 other use. The old notification will be created as well, but
157 will be removed prior to FreeBSD 14.0.
160 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
161 been upgraded to 10.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 read(2) of a directory fd is now rejected by default. root may
167 re-enable it for the entire system with the
168 security.bsd.allow_read_dir sysctl(8) MIB.
170 It may be advised to setup aliases for grep to default to `-d skip` if
171 commonly non-recursively grepping a list that includes directories and
172 the potential for the resulting stderr output is not tolerable. Example
173 aliases are now installed, commented out, in /root/.cshrc.
176 Upstream DTS from Linux 5.6 was merged and they now have the SID
177 and THS (Secure ID controller and THermal Sensor) node present.
178 The DTB overlays have now been removed from the tree for the H3/H5 and
179 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
180 deal with upstream DTS. If you are using those overlays you need to
181 remove them from loader.conf and update the DTBs on the FAT partition.
184 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
185 been upgraded to 10.0.0. Please see the 20141231 entry below for
186 information about prerequisites and upgrading, if you are not already
187 using clang 3.5.0 or higher.
190 The root certificates of the Mozilla CA Certificate Store have been
191 imported into the base system and can be managed with the certctl(8)
192 utility. If you have installed the security/ca_root_nss port or package
193 with the ETCSYMLINK option (the default), be advised that there may be
194 differences between those included in the port and those included in
195 base due to differences in nss branch used as well as general update
196 frequency. Note also that certctl(8) cannot manage certs in the
197 format used by the security/ca_root_nss port.
200 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
201 been upgraded to 9.0.1. Please see the 20141231 entry below for
202 information about prerequisites and upgrading, if you are not already
203 using clang 3.5.0 or higher.
206 The nctgpio and wbwd drivers have been moved to the superio bus.
207 If you have one of these drivers in a kernel configuration, then
208 you should add device superio to it. If you use one of these drivers
209 as a module and you compile a custom set of modules, then you should
210 add superio to the set.
213 The tap(4) driver has been folded into tun(4), and the module has been
214 renamed to tuntap. You should update any kld_list="if_tap" or
215 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
216 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
217 module instead, and "device tap" or "device tun" entries in kernel
218 config files to select the tuntap device instead.
221 ntpd no longer by default locks its pages in memory, allowing them
222 to be paged out by the kernel. Use rlimit memlock to restore
223 historic BSD behaviour. For example, add "rlimit memlock 32"
224 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
227 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
228 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
229 been removed from mount_fusefs(8). You can safely remove them from
230 your scripts, because they had no effect.
232 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
233 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
234 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
235 sysctls have been removed. If you felt the need to set any of them to
236 a non-default value, please tell asomers@FreeBSD.org why.
239 The fuse(4) module has been renamed to fusefs(4) for consistency with
240 other filesystems. You should update any kld_load="fuse" entries in
241 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
242 "options FUSE" enties in kernel config files.
245 Default permissions on the /var/account/acct file (and copies of it
246 rotated by periodic daily scripts) are changed from 0644 to 0640
247 because the file contains sensitive information that should not be
248 world-readable. If the /var/account directory must be created by
249 rc.d/accounting, the mode used is now 0750. Admins who use the
250 accounting feature are encouraged to change the mode of an existing
251 /var/account directory to 0750 or 0700.
254 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
255 been upgraded to 8.0.1. Please see the 20141231 entry below for
256 information about prerequisites and upgrading, if you are not already
257 using clang 3.5.0 or higher.
260 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
261 functionality needed for the RETPOLINE option should work properly
262 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
265 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
266 8.0.0. Please see the 20141231 entry below for information about
267 prerequisites and upgrading, if you are not already using clang 3.5.0
271 The RETPOLINE option produces non-functional ifunc-using binaries
272 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
273 Once Clang 8 is merged it may be enabled again.
276 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
277 7.0.1. Please see the 20141231 entry below for information about
278 prerequisites and upgrading, if you are not already using clang 3.5.0
282 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
283 compiled into your custom kernel, add 'device xz' statement to the
287 Iflib is no longer unconditionally compiled into the kernel. Drivers
288 using iflib and statically compiled into the kernel, now require
289 the 'device iflib' config option. For the same drivers loaded as
290 modules on kernels not having 'device iflib', the iflib.ko module
291 is loaded automatically.
294 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
295 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
296 servers that have vfs.nfsd.nfs_privport set will only allow mounts
297 from clients using a reserved port#. Since both the FreeBSD and Linux
298 NFSv4 clients use reserved port#s by default, this should not affect
302 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
303 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
304 it produces broken binaries when ifuncs are in use. Users needing
305 GNU ld should install the binutils port or package.
308 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
309 has been converted to a port (misc/ctm) and will be removed from
310 FreeBSD-13. A depreciation warning will be printed to stderr by
311 the ctm command, but the functionality will remain in base for all
315 The stable/12 branch has been created in subversion from head
319 Ports for the DRM modules have been simplified. Now, amd64 users should
320 just install the drm-kmod port. All others should install
323 Graphics hardware that's newer than about 2010 usually works with
324 drm-kmod. For hardware older than 2013, however, some users will need
325 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
326 than 2008 usually only works in drm-legacy-kmod. The graphics team can
327 only commit to hardware made since 2013 due to the complexity of the
328 market and difficulty to test all the older cards effectively. If you
329 have hardware supported by drm-kmod, you are strongly encouraged to use
330 that as you will get better support.
332 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
333 elsewhere, the drm and drm2 modules will be eliminated from the src base
334 soon (with a limited exception for arm). Please update to the package asap
335 and report any issues to x11@freebsd.org.
337 Generally, anybody using the drm*-kmod packages should add
338 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
339 cross-threading surprises, especially with automatic driver
340 loading from X11 startup. These will become the defaults in 13-current
344 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
345 custom kernel and module loading configuration files must be updated
346 accordingly. Moreover, interfaces previous presented as ixlvN to the
347 system are now exposed as iavfN and network configuration files must
348 be adjusted as necessary.
351 OpenSSL has been updated to version 1.1.1. This update included
352 additional various API changes througout the base system. It is
353 important to rebuild third-party software after upgrading. The value
354 of __FreeBSD_version has been bumped accordingly.
357 The legacy DRM modules and drivers have now been added to the loader's
358 module blacklist, in favor of loading them with kld_list in rc.conf(5).
359 The module blacklist may be overridden with the loader.conf(5)
360 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
364 The cam(4) based nda(4) driver will be used over nvd(4) by default on
365 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
366 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
367 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
371 Reproducible build mode is now on by default, in preparation for
372 FreeBSD 12.0. This eliminates build metadata such as the user,
373 host, and time from the kernel (and uname), unless the working tree
374 corresponds to a modified checkout from a version control system.
375 The previous behavior can be obtained by setting the /etc/src.conf
376 knob WITHOUT_REPRODUCIBLE_BUILD.
379 The Yarrow CSPRNG has been removed from the kernel as it has not been
380 supported by its designers since at least 2003. Fortuna has been the
381 default since FreeBSD-11.
384 devctl freeze/thaw have gone into the tree, the rc scripts have been
385 updated to use them and devmatch has been changed. You should update
386 kernel, userland and rc scripts all at the same time.
389 The default interpreter has been switched from 4th to Lua.
390 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
391 interpreter. If you have custom FORTH code you will need to set
392 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
393 src.conf for the build. This will create default hard links between
394 loader and loader_4th instead of loader and loader_lua, the new default.
395 If you are using UEFI it will create the proper hard link to loader.efi.
397 bhyve uses userboot.so. It remains 4th-only until some issues are solved
398 regarding coexisting with multiple versions of FreeBSD are resolved.
401 ls(1) now respects the COLORTERM environment variable used in other
402 systems and software to indicate that a colored terminal is both
403 supported and desired. If ls(1) is suddenly emitting colors, they may
404 be disabled again by either removing the unwanted COLORTERM from your
405 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
406 may not be observed in a future release.
409 The default pager for most commands has been changed to "less". To
410 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
414 The jedec_ts(4) driver has been removed. A superset of its functionality
415 is available in the jedec_dimm(4) driver, and the manpage for that
416 driver includes migration instructions. If you have "device jedec_ts"
417 in your kernel configuration file, it must be removed.
420 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
421 This should have no effect if the kernel is booted via BIOS/legacy boot.
422 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
423 has a buggy firmware that prevents a successful boot due to use of
427 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
428 support has been removed from the tree. These ports were
429 obsolete and/or known to be broken for many years.
432 loader.efi has been augmented to participate more fully in the
433 UEFI boot manager protocol. loader.efi will now look at the
434 BootXXXX environment variable to determine if a specific kernel
435 or root partition was specified. XXXX is derived from BootCurrent.
436 efibootmgr(8) manages these standard UEFI variables.
439 zfsloader's functionality has now been folded into loader.
440 zfsloader is no longer necessary once you've updated your
441 boot blocks. For a transition period, we will install a
442 hardlink for zfsloader to loader to allow a smooth transition
443 until the boot blocks can be updated (hard link because old
444 zfs boot blocks don't understand symlinks).
447 ARM64 now have efifb support, if you want to have serial console
448 on your arm64 board when an screen is connected and the bootloader
449 setup a frambuffer for us to use, just add :
453 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
454 an screen connected as the firmware will setup a framebuffer are that
455 u-boot will expose as an EFI framebuffer.
458 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
459 or take steps to update /etc/passwd before doing installworld on
460 existing systems. Do not skip the "mergemaster -Fp" step before
461 installworld, as described in the update procedures near the bottom
462 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
463 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
464 the ntp config file contain options that change file/dir locations.
465 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
466 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
467 taking steps to ensure that all required files/dirs are accessible
471 Big endian arm support has been removed.
474 The static environment setup in kernel configs is no longer mutually
475 exclusive with the loader(8) environment by default. In order to
476 restore the previous default behavior of disabling the loader(8)
477 environment if a static environment is present, you must specify
478 loader_env.disabled=1 in the static environment.
481 The ABI of syscalls used by management tools like sockstat and
482 netstat has been broken to allow 32-bit binaries to work on
483 64-bit kernels without modification. These programs will need
484 to match the kernel in order to function. External programs may
485 require minor modifications to accommodate a change of type in
486 structures from pointers to 64-bit virtual addresses.
489 On i386 and amd64 atomics are now inlined. Out of tree modules using
490 atomics will need to be rebuilt.
493 The '%I' format in the kern.corefile sysctl limits the number of
494 core files that a process can generate to the number stored in the
495 debug.ncores sysctl. The '%I' format is replaced by the single digit
496 index. Previously, if all indexes were taken the kernel would overwrite
497 only a core file with the highest index in a filename.
498 Currently the system will create a new core file if there is a free
499 index or if all slots are taken it will overwrite the oldest one.
502 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
503 6.0.1. Please see the 20141231 entry below for information about
504 prerequisites and upgrading, if you are not already using clang 3.5.0
508 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
509 needed to be changed to work with it. This change was made with r335763
510 and requires a mergemaster / etcupdate / etc to update the installed file.
513 r334930 changed the interface between the NFS modules, so they all
514 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
517 As of r334391 lld is the default amd64 system linker; it is installed
518 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
522 The kernel / userland interface for devinfo changed, so you'll
523 need a new kernel and userland as a pair for it to work (rebuilding
524 lib/libdevinfo is all that's required). devinfo and devmatch will
525 not work, but everything else will when there's a mismatch.
528 The on-disk format for hwpmc callchain records has changed to include
529 threadid corresponding to a given record. This changes the field offsets
530 and thus requires that libpmcstat be rebuilt before using a kernel
534 The vxge(4) driver has been removed. This driver was introduced into
535 HEAD one week before the Exar left the Ethernet market and is not
536 known to be used. If you have device vxge in your kernel config file
540 The amd64 kernel now requires a ld that supports ifunc to produce a
541 working kernel, either lld or a newer binutils. lld is built by default
542 on amd64, and the 'buildkernel' target uses it automatically. However,
543 it is not the default linker, so building the kernel the traditional
544 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
545 binutils port/package). lld will soon be default, and this requirement
548 NOTE: As of r334391 lld is the default system linker on amd64, and no
549 workaround is necessary.
552 The nxge(4) driver has been removed. This driver was for PCI-X 10g
553 cards made by s2io/Neterion. The company was aquired by Exar and
554 no longer sells or supports Ethernet products. If you have device
555 nxge in your kernel config file it must be removed.
558 The tz database (tzdb) has been updated to 2018e. This version more
559 correctly models time stamps in time zones with negative DST such as
560 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
561 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
562 time zone abbreviations and the tm_isdst flag.
565 The ixgb(4) driver has been removed. This driver was for an early and
566 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
567 quickly shifted to the long lived ixgbe family. If you have device
568 ixgb in your kernel config file it must be removed.
571 The lmc(4) driver has been removed. This was a WAN interface
572 card that was already reportedly rare in 2003, and had an ambiguous
573 license. If you have device lmc in your kernel config file it must
577 Support for Arcnet networks has been removed. If you have device
578 arcnet or device cm in your kernel config file they must be
582 Support for FDDI networks has been removed. If you have device
583 fddi or device fpa in your kernel config file they must be
587 In addition to supporting RFC 3164 formatted messages, the
588 syslogd(8) service is now capable of parsing RFC 5424 formatted
589 log messages. The main benefit of using RFC 5424 is that clients
590 may now send log messages with timestamps containing year numbers,
591 microseconds and time zone offsets.
593 Similarly, the syslog(3) C library function has been altered to
594 send RFC 5424 formatted messages to the local system logging
595 daemon. On systems using syslogd(8), this change should have no
596 negative impact, as long as syslogd(8) and the C library are
597 updated at the same time. On systems using a different system
598 logging daemon, it may be necessary to make configuration
599 adjustments, depending on the software used.
601 When using syslog-ng, add the 'syslog-protocol' flag to local
602 input sources to enable parsing of RFC 5424 formatted messages:
605 unix-dgram("/var/run/log" flags(syslog-protocol));
608 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
609 of the 'imuxsock' module to let messages be processed by the
610 regular RFC 3164/5424 parsing pipeline:
612 module(load="imuxsock" SysSock.UseSpecialParser="off")
614 Do note that these changes only affect communication between local
615 applications and syslogd(8). The format that syslogd(8) uses to
616 store messages on disk or forward messages to other systems
617 remains unchanged. syslogd(8) still uses RFC 3164 for these
618 purposes. Options to customize this behaviour will be added in the
619 future. Utilities that process log files stored in /var/log are
620 thus expected to continue to function as before.
622 __FreeBSD_version has been incremented to 1200061 to denote this
626 Support for token ring networks has been removed. If you
627 have "device token" in your kernel config you should remove
628 it. No device drivers supported token ring.
631 makefs was modified to be able to tag ISO9660 El Torito boot catalog
632 entries as EFI instead of overloading the i386 tag as done previously.
633 The amd64 mkisoimages.sh script used to build amd64 ISO images for
634 release was updated to use this. This may mean that makefs must be
635 updated before "make cdrom" can be run in the release directory. This
636 should be as simple as:
638 $ cd $SRCDIR/usr.sbin/makefs
639 $ make depend all install
642 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
643 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
644 Co-existance for the transition period will come shortly. Booting is a
645 complex environment and test coverage for Lua-enabled loaders has been
646 thin, so it would be prudent to assume it might not work and make
647 provisions for backup boot methods.
650 devmatch functionality has been turned on in devd. It will automatically
651 load drivers for unattached devices. This may cause unexpected drivers to
652 be loaded. Please report any problems to current@ and imp@freebsd.org.
655 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
656 6.0.0. Please see the 20141231 entry below for information about
657 prerequisites and upgrading, if you are not already using clang 3.5.0
661 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
662 This means it is used to link the kernel and userland libraries and
663 executables, but is not yet installed as /usr/bin/ld by default.
665 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
666 WITHOUT_LLD_BOOTSTRAP=yes
669 On i386, pmtimer has been removed. Its functionality has been folded
670 into apm. It was a no-op on ACPI in current for a while now (but was still
671 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
672 from kernel config files.
675 The use of RSS hash from the network card aka flowid has been
676 disabled by default for lagg(4) as it's currently incompatible with
677 the lacp and loadbalance protocols.
679 This can be re-enabled by setting the following in loader.conf:
680 net.link.lagg.default_use_flowid="1"
683 The SW_WATCHDOG option is no longer necessary to enable the
684 hardclock-based software watchdog if no hardware watchdog is
685 configured. As before, SW_WATCHDOG will cause the software
686 watchdog to be enabled even if a hardware watchdog is configured.
689 r326887 fixes the issue described in the 20171214 UPDATING entry.
690 r326888 flips the switch back to building GELI support always.
693 r362593 broke ZFS + GELI support for reasons unknown. However,
694 it also broke ZFS support generally, so GELI has been turned off
695 by default as the lesser evil in r326857. If you boot off ZFS and/or
696 GELI, it might not be a good time to update.
699 PowerPC users must update loader(8) by rebuilding world before
700 installing a new kernel, as the protocol connecting them has
701 changed. Without the update, loader metadata will not be passed
702 successfully to the kernel and users will have to enter their
703 root partition at the kernel mountroot prompt to continue booting.
704 Newer versions of loader can boot old kernels without issue.
707 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
708 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
709 to WITH/OUT_LOADER_GELI.
712 The naive and non-compliant support of posix_fallocate(2) in ZFS
713 has been removed as of r325320. The system call now returns EINVAL
714 when used on a ZFS file. Although the new behavior complies with the
715 standard, some consumers are not prepared to cope with it.
716 One known victim is lld prior to r325420.
719 Building in a FreeBSD src checkout will automatically create object
720 directories now rather than store files in the current directory if
721 'make obj' was not ran. Calling 'make obj' is no longer necessary.
722 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
723 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
727 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
728 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
729 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
730 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
731 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
732 The UNIFIED_OBJDIR option is a transitional feature that will be
733 removed for 12.0 release; please migrate to the new format for any
734 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
735 than hardcoding paths.
738 The native-xtools target no longer installs the files by default to the
739 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
740 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
743 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
744 options are changing from controlling the build if defined / undefined
745 to controlling the build with explicit 'yes' or 'no' values. They will
746 shift to WITH/WITHOUT options to match other options in the system.
749 libstand has turned into a private library for sys/boot use only.
750 It is no longer supported as a public interface outside of sys/boot.
753 The arm port has split armv6 into armv6 and armv7. armv7 is now
754 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
755 and are running a kernel from before r324363, you will need to add
756 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
759 When building multiple kernels using KERNCONF, non-existent KERNCONF
760 files will produce an error and buildkernel will fail. Previously
761 missing KERNCONF files silently failed giving no indication as to
762 why, only to subsequently discover during installkernel that the
763 desired kernel was never built in the first place.
766 The default serial number format for CTL LUNs has changed. This will
767 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
768 or iSCSI clients care about their LUNs' serial numbers. Users who
769 require serial number stability should hardcode serial numbers in
773 For 32-bit arm compiled for hard-float support, soft-floating point
774 binaries now always get their shared libraries from
775 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
776 /usr/libsoft also existed). Only users with a hard-float ld.so, but
777 soft-float everything else should be affected.
780 The geli password typed at boot is now hidden. To restore the previous
781 behavior, see geli(8) for configuration options.
784 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
785 sysctl values. Minor nit, but requires a rebuild of both world/kernel
789 "make check" behavior (made in ^/head@r295380) has been changed to
790 execute from a limited sandbox, as opposed to executing from
794 - The "beforecheck" and "aftercheck" targets are now specified.
795 - ${CHECKDIR} (added in commit noted above) has been removed.
796 - Legacy behavior can be enabled by setting
797 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
799 If the limited sandbox mode is enabled, "make check" will execute
800 "make distribution", then install, execute the tests, and clean up the
801 sandbox if successful.
803 The "make distribution" and "make install" targets are typically run as
804 root to set appropriate permissions and ownership at installation time.
805 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
806 environment if executing "make check" with limited sandbox mode using
807 an unprivileged user.
810 Since the switch to GPT disk labels, fsck for UFS/FFS has been
811 unable to automatically find alternate superblocks. As of r322297,
812 the information needed to find alternate superblocks has been
813 moved to the end of the area reserved for the boot block.
814 Filesystems created with a newfs of this vintage or later
815 will create the recovery information. If you have a filesystem
816 created prior to this change and wish to have a recovery block
817 created for your filesystem, you can do so by running fsck in
818 foreground mode (i.e., do not use the -p or -y options). As it
819 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
820 to which you should answer yes.
823 As of r321665, an NFSv4 server configuration that services
824 Kerberos mounts or clients that do not support the uid/gid in
825 owner/owner_group string capability, must explicitly enable
826 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
827 machine's /etc/rc.conf file.
830 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
831 Please see the 20141231 entry below for information about prerequisites
832 and upgrading, if you are not already using clang 3.5.0 or higher.
835 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
836 r-commands (rlogin, rsh, etc.) to be built with the base system.
839 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
840 a very major ABI incompatible change, so users of FreeBSD/powerpc must
841 be careful when performing source upgrades. It is best to run
842 'make installworld' from an alternate root system, either a live
843 CD/memory stick, or a temporary root partition. Additionally, all ports
844 must be recompiled. powerpc64 is largely unaffected, except in the case
845 of 32-bit compatibility. All 32-bit binaries will be affected.
848 Forward compatibility for the "ino64" project have been committed. This
849 will allow most new binaries to run on older kernels in a limited
850 fashion. This prevents many of the common foot-shooting actions in the
851 upgrade as well as the limited ability to roll back the kernel across
852 the ino64 upgrade. Complicated use cases may not work properly, though
853 enough simpler ones work to allow recovery in most situations.
856 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
857 if you require the GPL compiler.
860 The internal ABI used for communication between the NFS kernel modules
861 was changed by r320085, so __FreeBSD_version was bumped to
862 ensure all the NFS related modules are updated together.
865 The ABI of struct event was changed by extending the data
866 member to 64bit and adding ext fields. For upgrade, same
867 precautions as for the entry 20170523 "ino64" must be
871 The GNU roff toolchain has been removed from base. To render manpages
872 which are not supported by mandoc(1), man(1) can fallback on GNU roff
873 from ports (and recommends to install it).
874 To render roff(7) documents, consider using GNU roff from ports or the
875 heirloom doctools roff toolchain from ports via pkg install groff or
876 via pkg install heirloom-doctools.
879 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
880 smaller runtime footprint builds. This is useful for embedded systems
881 which only require one chipset support.
883 If you load it as a module, make sure this is in /boot/loader.conf:
887 This will load the HAL, all chip/RF backends and if_ath_pci.
888 If you have if_ath_pci in /boot/loader.conf, ensure it is after
889 if_ath or it will not load any HAL chipset support.
891 If you want to selectively load things (eg on ye cheape ARM/MIPS
892 platforms where RAM is at a premium) you should:
895 * load the chip modules in question
896 * load ath_rate, ath_dfs
898 * load if_ath_pci and/or if_ath_ahb depending upon your particular
899 bus bind type - this is where probe/attach is done.
901 For further comments/feedback, poke adrian@ .
904 The "ino64" 64-bit inode project has been committed, which extends
905 a number of types to 64 bits. Upgrading in place requires care and
906 adherence to the documented upgrade procedure.
908 If using a custom kernel configuration ensure that the
909 COMPAT_FREEBSD11 option is included (as during the upgrade the
910 system will be running the ino64 kernel with the existing world).
912 For the safest in-place upgrade begin by removing previous build
913 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
914 full procedure documented below under the heading "To rebuild
915 everything and install it on the current system." Specifically,
916 a reboot is required after installing the new kernel before
920 The NATM framework including the en(4), fatm(4), hatm(4), and
921 patm(4) devices has been removed. Consumers should plan a
922 migration before the end-of-life date for FreeBSD 11.
925 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
926 diff has not been implemented, if those are needed a newer version of
927 GNU diff is available via the diffutils package under the gdiff name.
930 As of r316810 for ipfilter, keep frags is no longer assumed when
931 keep state is specified in a rule. r316810 aligns ipfilter with
932 documentation in man pages separating keep frags from keep state.
933 This allows keep state to be specified without forcing keep frags
934 and allows keep frags to be specified independently of keep state.
935 To maintain previous behaviour, also specify keep frags with
936 keep state (as documented in ipf.conf.5).
939 arm64 builds now use the base system LLD 4.0.0 linker by default,
940 instead of requiring that the aarch64-binutils port or package be
941 installed. To continue using aarch64-binutils, set
942 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
945 The UDP optimization in entry 20160818 that added the sysctl
946 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
947 packets will no longer be treated as L3 broadcast packets.
950 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
951 use any explicitly assigned loopback address available in the jail
952 instead of using the first assigned address of the jail.
955 The ctl.ko module no longer implements the iSCSI target frontend:
956 cfiscsi.ko does instead.
958 If building cfiscsi.ko as a kernel module, the module can be loaded
959 via one of the following methods:
960 - `cfiscsi_load="YES"` in loader.conf(5).
961 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
962 - ctladm(8)/ctld(8), when compiled with iSCSI support
963 (`WITH_ISCSI=yes` in src.conf(5))
965 Please see cfiscsi(4) for more details.
968 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
969 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
970 same source (previously, the dependency of mmcsd.ko on mmc.ko was
971 missing, but mmcsd.ko now will refuse to load if it is incompatible
975 The syntax of ipfw(8) named states was changed to avoid ambiguity.
976 If you have used named states in the firewall rules, you need to modify
977 them after installworld and before rebooting. Now named states must
978 be prefixed with colon.
981 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
982 removed as the userland we provide cannot use them. The KMS version
983 (sys/dev/drm2) supports the same hardware.
986 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
987 Please see the 20141231 entry below for information about prerequisites
988 and upgrading, if you are not already using clang 3.5.0 or higher.
991 The code that provides support for ZFS .zfs/ directory functionality
992 has been reimplemented. It's not possible now to create a snapshot
993 by mkdir under .zfs/snapshot/. That should be the only user visible
997 EISA bus support has been removed. The WITH_EISA option is no longer
1001 MCA bus support has been removed.
1004 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1005 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1008 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1009 the em(4) driver conforms to iflib specifications.
1012 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1013 IFLIB. If you have a custom kernel configuration that excludes em(4)
1014 but you use igb(4), you need to re-add em(4) to your custom configuration.
1017 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1018 Please see the 20141231 entry below for information about prerequisites
1019 and upgrading, if you are not already using clang 3.5.0 or higher.
1022 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1023 Please see the 20141231 entry below for information about prerequisites
1024 and upgrading, if you are not already using clang 3.5.0 or higher.
1027 The layout of the pmap structure has changed for powerpc to put the pmap
1028 statistics at the front for all CPU variations. libkvm(3) and all tools
1029 that link against it need to be recompiled.
1032 isl(4) and cyapa(4) drivers now require a new driver,
1033 chromebook_platform(4), to work properly on Chromebook-class hardware.
1034 On other types of hardware the drivers may need to be configured using
1035 device hints. Please see the corresponding manual pages for details.
1038 The urtwn(4) driver was merged into rtwn(4) and now consists of
1039 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1041 Also, firmware for RTL8188CE was renamed due to possible name
1042 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1045 GNU rcs has been removed from base. It is available as packages:
1046 - rcs: Latest GPLv3 GNU rcs version.
1047 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1051 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1052 modules now requires that the kernel configuration contain the
1053 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1056 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1057 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1060 Relocatable object files with the extension of .So have been renamed
1061 to use an extension of .pico instead. The purpose of this change is
1062 to avoid a name clash with shared libraries on case-insensitive file
1063 systems. On those file systems, foo.So is the same file as foo.so.
1066 GNU rcs has been turned off by default. It can (temporarily) be built
1067 again by adding WITH_RCS knob in src.conf.
1068 Otherwise, GNU rcs is available from packages:
1069 - rcs: Latest GPLv3 GNU rcs version.
1070 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1073 The backup_uses_rcs functionality has been removed from rc.subr.
1076 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1077 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1078 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1079 QUEUE_MACRO_DEBUG behavior.
1082 r304787 changed some ioctl interfaces between the iSCSI userspace
1083 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1084 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1088 The UDP receive code has been updated to only treat incoming UDP
1089 packets that were addressed to an L2 broadcast address as L3
1090 broadcast packets. It is not expected that this will affect any
1091 standards-conforming UDP application. The new behaviour can be
1092 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1096 Remove the openbsd_poll system call.
1097 __FreeBSD_version has been bumped because of this.
1100 The stable/11 branch has been created from head@r302406.
1103 The libc stub for the pipe(2) system call has been replaced with
1104 a wrapper that calls the pipe2(2) system call and the pipe(2)
1105 system call is now only implemented by the kernels that include
1106 "options COMPAT_FREEBSD10" in their config file (this is the
1107 default). Users should ensure that this option is enabled in
1108 their kernel or upgrade userspace to r302092 before upgrading their
1112 CAM will now strip leading spaces from SCSI disks' serial numbers.
1113 This will affect users who create UFS filesystems on SCSI disks using
1114 those disk's diskid device nodes. For example, if /etc/fstab
1115 previously contained a line like
1116 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1117 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1118 transforms like gmirror may also be affected. ZFS users should
1122 The bitstring(3) API has been updated with new functionality and
1123 improved performance. But it is binary-incompatible with the old API.
1124 Objects built with the new headers may not be linked against objects
1125 built with the old headers.
1128 The brk and sbrk functions have been removed from libc on arm64.
1129 Binutils from ports has been updated to not link to these
1130 functions and should be updated to the latest version before
1131 installing a new libc.
1134 The armv6 port now defaults to hard float ABI. Limited support
1135 for running both hardfloat and soft float on the same system
1136 is available using the libraries installed with -DWITH_LIBSOFT.
1137 This has only been tested as an upgrade path for installworld
1138 and packages may fail or need manual intervention to run. New
1139 packages will be needed.
1141 To update an existing self-hosted armv6hf system, you must add
1142 TARGET_ARCH=armv6 on the make command line for both the build
1143 and the install steps.
1146 Kernel modules compiled outside of a kernel build now default to
1147 installing to /boot/modules instead of /boot/kernel. Many kernel
1148 modules built this way (such as those in ports) already overrode
1149 KMODDIR explicitly to install into /boot/modules. However,
1150 manually building and installing a module from /sys/modules will
1151 now install to /boot/modules instead of /boot/kernel.
1154 The CAM I/O scheduler has been committed to the kernel. There should be
1155 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1156 list of known rogues that claim support for this but actually corrupt
1157 data is believed to be complete, be on the lookout for data
1158 corruption. The known rogue list is believed to be complete:
1160 o Crucial MX100, M550 drives with MU01 firmware.
1161 o Micron M510 and M550 drives with MU01 firmware.
1162 o Micron M500 prior to MU07 firmware
1163 o Samsung 830, 840, and 850 all firmwares
1164 o FCCT M500 all firmwares
1166 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1167 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1168 updated firmware. Black listed drives will work correctly because these
1169 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1170 this list is the same as found in Linux, it's believed there are no
1171 other rogues in the market place. All other models from the above
1174 To be safe, if you are at all concerned, you can quirk each of your
1175 drives to prevent NCQ from being sent by setting:
1176 kern.cam.ada.X.quirks="0x2"
1177 in loader.conf. If the drive requires the 4k sector quirk, set the
1178 quirks entry to 0x3.
1181 The FAST_DEPEND build option has been removed and its functionality is
1182 now the one true way. The old mkdep(1) style of 'make depend' has
1183 been removed. See 20160311 for further details.
1186 Resource range types have grown from unsigned long to uintmax_t. All
1187 drivers, and anything using libdevinfo, need to be recompiled.
1190 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1191 builds. It no longer runs mkdep(1) during 'make depend', and the
1192 'make depend' stage can safely be skipped now as it is auto ran
1193 when building 'make all' and will generate all SRCS and DPSRCS before
1194 building anything else. Dependencies are gathered at compile time with
1195 -MF flags kept in separate .depend files per object file. Users should
1196 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1197 stale .depend files.
1200 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1201 kernel modules. Therefore, if you load any kernel modules at boot time,
1202 please install the boot loaders after you install the kernel, but before
1206 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1207 make installkernel KERNCONF=YOUR_KERNEL_HERE
1208 make -C sys/boot install
1209 <reboot in single user>
1211 Then follow the usual steps, described in the General Notes section,
1215 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1216 see the 20141231 entry below for information about prerequisites and
1217 upgrading, if you are not already using clang 3.5.0 or higher.
1220 The AIO subsystem is now a standard part of the kernel. The
1221 VFS_AIO kernel option and aio.ko kernel module have been removed.
1222 Due to stability concerns, asynchronous I/O requests are only
1223 permitted on sockets and raw disks by default. To enable
1224 asynchronous I/O requests on all file types, set the
1225 vfs.aio.enable_unsafe sysctl to a non-zero value.
1228 The ELF object manipulation tool objcopy is now provided by the
1229 ELF Tool Chain project rather than by GNU binutils. It should be a
1230 drop-in replacement, with the addition of arm64 support. The
1231 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1232 to obtain the GNU version if necessary.
1235 Building ZFS pools on top of zvols is prohibited by default. That
1236 feature has never worked safely; it's always been prone to deadlocks.
1237 Using a zvol as the backing store for a VM guest's virtual disk will
1238 still work, even if the guest is using ZFS. Legacy behavior can be
1239 restored by setting vfs.zfs.vol.recursive=1.
1242 The NONE and HPN patches has been removed from OpenSSH. They are
1243 still available in the security/openssh-portable port.
1246 With the addition of ypldap(8), a new _ypldap user is now required
1247 during installworld. "mergemaster -p" can be used to add the user
1248 prior to installworld, as documented in the handbook.
1251 The tftp loader (pxeboot) now uses the option root-path directive. As a
1252 consequence it no longer looks for a pxeboot.4th file on the tftp
1253 server. Instead it uses the regular /boot infrastructure as with the
1257 The code to start recording plug and play data into the modules has
1258 been committed. While the old tools will properly build a new kernel,
1259 a number of warnings about "unknown metadata record 4" will be produced
1260 for an older kldxref. To avoid such warnings, make sure to rebuild
1261 the kernel toolchain (or world). Make sure that you have r292078 or
1262 later when trying to build 292077 or later before rebuilding.
1265 Debug data files are now built by default with 'make buildworld' and
1266 installed with 'make installworld'. This facilitates debugging but
1267 requires more disk space both during the build and for the installed
1268 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1272 r291527 changed the internal interface between the nfsd.ko and
1273 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1274 __FreeBSD_version has been bumped because of this.
1277 Add support for unicode collation strings leads to a change of
1278 order of files listed by ls(1) for example. To get back to the old
1279 behaviour, set LC_COLLATE environment variable to "C".
1281 Databases administrators will need to reindex their databases given
1282 collation results will be different.
1284 Due to a bug in install(1) it is recommended to remove the ancient
1285 locales before running make installworld.
1287 rm -rf /usr/share/locale/*
1290 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1291 libcrypto.so.7 or libssl.so.7 must be recompiled.
1294 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1295 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1296 should be replaced with isp_2400 and isp_2500 modules respectively.
1299 The build previously allowed using 'make -n' to not recurse into
1300 sub-directories while showing what commands would be executed, and
1301 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1302 and 'make -N' will not.
1305 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1306 and etcupdate will now use this file. A custom sendmail.cf is now
1307 updated via this mechanism rather than via installworld. If you had
1308 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1309 want to remove the exclusion or change it to "always install".
1310 /etc/mail/sendmail.cf is now managed the same way regardless of
1311 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1312 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1315 Compatibility shims for legacy ATA device names have been removed.
1316 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1317 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1318 environment variables, /dev/ad* and /dev/ar* symbolic links.
1321 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1322 Please see the 20141231 entry below for information about prerequisites
1323 and upgrading, if you are not already using clang 3.5.0 or higher.
1326 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1327 and renamed from .symbols to .debug. This reduces the size requirements
1328 on the boot partition or file system and provides consistency with
1329 userland debug files.
1331 When using the supported kernel installation method the
1332 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1333 as is done with /boot/kernel.
1335 Developers wishing to maintain the historical behavior of installing
1336 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1339 The wireless drivers had undergone changes that remove the 'parent
1340 interface' from the ifconfig -l output. The rc.d network scripts
1341 used to check presence of a parent interface in the list, so old
1342 scripts would fail to start wireless networking. Thus, etcupdate(3)
1343 or mergemaster(8) run is required after kernel update, to update your
1344 rc.d scripts in /etc.
1347 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1348 These configurations are now automatically interpreted as
1349 'scrub fragment reassemble'.
1352 Kernel-loadable modules for the random(4) device are back. To use
1353 them, the kernel must have
1356 options RANDOM_LOADABLE
1358 kldload(8) can then be used to load random_fortuna.ko
1359 or random_yarrow.ko. Please note that due to the indirect
1360 function calls that the loadable modules need to provide,
1361 the build-in variants will be slightly more efficient.
1363 The random(4) kernel option RANDOM_DUMMY has been retired due to
1364 unpopularity. It was not all that useful anyway.
1367 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1368 Control over building the ELF Tool Chain tools is now provided by
1369 the WITHOUT_TOOLCHAIN knob.
1372 The polarity of Pulse Per Second (PPS) capture events with the
1373 uart(4) driver has been corrected. Prior to this change the PPS
1374 "assert" event corresponded to the trailing edge of a positive PPS
1375 pulse and the "clear" event was the leading edge of the next pulse.
1377 As the width of a PPS pulse in a typical GPS receiver is on the
1378 order of 1 millisecond, most users will not notice any significant
1379 difference with this change.
1381 Anyone who has compensated for the historical polarity reversal by
1382 configuring a negative offset equal to the pulse width will need to
1383 remove that workaround.
1386 The default group assigned to /dev/dri entries has been changed
1387 from 'wheel' to 'video' with the id of '44'. If you want to have
1388 access to the dri devices please add yourself to the video group
1391 # pw groupmod video -m $USER
1394 The menu.rc and loader.rc files will now be replaced during
1395 upgrades. Please migrate local changes to menu.rc.local and
1396 loader.rc.local instead.
1399 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1400 strings and strip have been removed. The src.conf(5) knob
1401 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1404 As ZFS requires more kernel stack pages than is the default on some
1405 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1406 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1408 Please consider using 'options KSTACK_PAGES=X' where X is greater
1409 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1412 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1413 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1414 default, i.e., they will not contain "::". For example, instead
1415 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1416 to have a more specific match, such as different map entries for
1417 IPv6:0:0 vs IPv6:0. This change requires that configuration
1418 data (including maps, files, classes, custom ruleset, etc.) must
1419 use the same format, so make certain such configuration data is
1420 upgrading. As a very simple check search for patterns like
1421 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1422 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1423 the cf option UseCompressedIPv6Addresses.
1426 The default kernel entropy-processing algorithm is now
1427 Fortuna, replacing Yarrow.
1429 Assuming you have 'device random' in your kernel config
1430 file, the configurations allow a kernel option to override
1431 this default. You may choose *ONE* of:
1433 options RANDOM_YARROW # Legacy /dev/random algorithm.
1434 options RANDOM_DUMMY # Blocking-only driver.
1436 If you have neither, you get Fortuna. For most people,
1437 read no further, Fortuna will give a /dev/random that works
1438 like it always used to, and the difference will be irrelevant.
1440 If you remove 'device random', you get *NO* kernel-processed
1441 entropy at all. This may be acceptable to folks building
1442 embedded systems, but has complications. Carry on reading,
1443 and it is assumed you know what you need.
1445 *PLEASE* read random(4) and random(9) if you are in the
1446 habit of tweaking kernel configs, and/or if you are a member
1447 of the embedded community, wanting specific and not-usual
1448 behaviour from your security subsystems.
1450 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1451 random', you will NOT have a functioning /dev/random, and
1452 many cryptographic features will not work, including SSH.
1453 You may also find strange behaviour from the random(3) set
1454 of library functions, in particular sranddev(3), srandomdev(3)
1455 and arc4random(3). The reason for this is that the KERN_ARND
1456 sysctl only returns entropy if it thinks it has some to
1457 share, and with RANDOM_DUMMY or no 'device random' this
1461 An additional fix for the issue described in the 20150614 sendmail
1462 entry below has been committed in revision 284717.
1465 FreeBSD's old make (fmake) has been removed from the system. It is
1466 available as the devel/fmake port or via pkg install fmake.
1469 The fix for the issue described in the 20150614 sendmail entry
1470 below has been committed in revision 284436. The work
1471 around described in that entry is no longer needed unless the
1472 default setting is overridden by a confDH_PARAMETERS configuration
1473 setting of '5' or pointing to a 512 bit DH parameter file.
1476 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1477 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1478 and devel/kyua to version 0.20+ and adjust any calling code to work
1479 with Kyuafile and kyua.
1482 The import of openssl to address the FreeBSD-SA-15:10.openssl
1483 security advisory includes a change which rejects handshakes
1484 with DH parameters below 768 bits. sendmail releases prior
1485 to 8.15.2 (not yet released), defaulted to a 512 bit
1486 DH parameter setting for client connections. To work around
1487 this interoperability, sendmail can be configured to use a
1488 2048 bit DH parameter by:
1490 1. Edit /etc/mail/`hostname`.mc
1491 2. If a setting for confDH_PARAMETERS does not exist or
1492 exists and is set to a string beginning with '5',
1493 replace it with '2'.
1494 3. If a setting for confDH_PARAMETERS exists and is set to
1495 a file path, create a new file with:
1496 openssl dhparam -out /path/to/file 2048
1497 4. Rebuild the .cf file:
1498 cd /etc/mail/; make; make install
1499 5. Restart sendmail:
1500 cd /etc/mail/; make restart
1502 A sendmail patch is coming, at which time this file will be
1506 Generation of legacy formatted entries have been disabled by default
1507 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1508 entries were converted to use the new format by default when the new,
1509 machine independent format have been added and supported since FreeBSD
1512 Please see the pwd_mkdb(8) manual page for further details.
1515 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1516 20141231 entry below for information about prerequisites and upgrading,
1517 if you are not already using 3.5.0 or higher.
1520 TI platform code switched to using vendor DTS files and this update
1521 may break existing systems running on Beaglebone, Beaglebone Black,
1524 - dtb files should be regenerated/reinstalled. Filenames are the
1525 same but content is different now
1526 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1527 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1528 addressing scheme is now pin 25 on /dev/gpioc3.
1529 - Pandaboard: /etc/ttys should be updated, serial console device is
1530 now /dev/ttyu2, not /dev/ttyu0
1533 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1534 If you need the GNU extension from groff soelim(1), install groff
1535 from package: pkg install groff, or via ports: textproc/groff.
1538 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1539 defined in symlink(7); previously symlinks were silently ignored.
1542 The const qualifier has been removed from iconv(3) to comply with
1543 POSIX. The ports tree is aware of this from r384038 onwards.
1546 Libraries specified by LIBADD in Makefiles must have a corresponding
1547 DPADD_<lib> variable to ensure correct dependencies. This is now
1548 enforced in src.libnames.mk.
1551 From legacy ata(4) driver was removed support for SATA controllers
1552 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1553 Kernel modules ataahci and ataadaptec were removed completely,
1554 replaced by ahci and mvs modules respectively.
1557 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1558 the 20141231 entry below for information about prerequisites and
1559 upgrading, if you are not already using 3.5.0 or higher.
1562 The 32-bit PowerPC kernel has been changed to a position-independent
1563 executable. This can only be booted with a version of loader(8)
1564 newer than January 31, 2015, so make sure to update both world and
1565 kernel before rebooting.
1568 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1569 but before r278950, the RNG was not seeded properly. Immediately
1570 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1571 ssh keys or openssl keys) that were generated w/ a kernel from that
1572 range. This does not affect programs that directly used /dev/random
1573 or /dev/urandom. All userland uses of arc4random(3) are affected.
1576 The autofs(4) ABI was changed in order to restore binary compatibility
1577 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1578 with the new kernel.
1581 The powerpc64 kernel has been changed to a position-independent
1582 executable. This can only be booted with a new version of loader(8),
1583 so make sure to update both world and kernel before rebooting.
1586 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1587 only release, no new features have been added. Please see the 20141231
1588 entry below for information about prerequisites and upgrading, if you
1589 are not already using 3.5.0.
1592 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1593 taken from the ELF Tool Chain project rather than GNU binutils. They
1594 should be drop-in replacements, with the addition of arm64 support.
1595 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1596 binutils tools, if necessary. See 20150805 for updated information.
1599 The default Unbound configuration now enables remote control
1600 using a local socket. Users who have already enabled the
1601 local_unbound service should regenerate their configuration
1602 by running "service local_unbound setup" as root.
1605 The GNU texinfo and GNU info pages have been removed.
1606 To be able to view GNU info pages please install texinfo from ports.
1609 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1611 As of this release, a prerequisite for building clang, llvm and lldb is
1612 a C++11 capable compiler and C++11 standard library. This means that to
1613 be able to successfully build the cross-tools stage of buildworld, with
1614 clang as the bootstrap compiler, your system compiler or cross compiler
1615 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1616 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1619 On any standard FreeBSD 10.x or 11.x installation, where clang and
1620 libc++ are on by default (that is, on x86 or arm), this should work out
1623 On 9.x installations where clang is enabled by default, e.g. on x86 and
1624 powerpc, libc++ will not be enabled by default, so libc++ should be
1625 built (with clang) and installed first. If both clang and libc++ are
1626 missing, build clang first, then use it to build libc++.
1628 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1629 the instructions for 9.x above.
1631 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1632 default, and do not build clang.
1634 Many embedded systems are resource constrained, and will not be able to
1635 build clang in a reasonable time, or in some cases at all. In those
1636 cases, cross building bootable systems on amd64 is a workaround.
1638 This new version of clang introduces a number of new warnings, of which
1639 the following are most likely to appear:
1643 This warns in two cases, for both C and C++:
1644 * When the code is trying to take the absolute value of an unsigned
1645 quantity, which is effectively a no-op, and almost never what was
1646 intended. The code should be fixed, if at all possible. If you are
1647 sure that the unsigned quantity can be safely cast to signed, without
1648 loss of information or undefined behavior, you can add an explicit
1649 cast, or disable the warning.
1651 * When the code is trying to take an absolute value, but the called
1652 abs() variant is for the wrong type, which can lead to truncation.
1653 If you want to disable the warning instead of fixing the code, please
1654 make sure that truncation will not occur, or it might lead to unwanted
1657 -Wtautological-undefined-compare and
1658 -Wundefined-bool-conversion
1660 These warn when C++ code is trying to compare 'this' against NULL, while
1661 'this' should never be NULL in well-defined C++ code. However, there is
1662 some legacy (pre C++11) code out there, which actively abuses this
1663 feature, which was less strictly defined in previous C++ versions.
1665 Squid and openjdk do this, for example. The warning can be turned off
1666 for C++98 and earlier, but compiling the code in C++11 mode might result
1667 in unexpected behavior; for example, the parts of the program that are
1668 unreachable could be optimized away.
1671 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1672 kernel sources have been removed. The .h files remain, since some
1673 utilities include them. This will need to be fixed later.
1674 If "mount -t oldnfs ..." is attempted, it will fail.
1675 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1676 the utilities will report errors.
1679 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1680 directories to top level SUBDIR variable when their parent
1681 directory is included in LOCAL_DIRS. Users with build systems with
1682 such hierarchies and without SUBDIR entries in the parent
1683 directory Makefiles should add them or add the directories to
1687 faith(4) and faithd(8) have been removed from the base system. Faith
1688 has been obsolete for a very long time.
1691 vt(4), the new console driver, is enabled by default. It brings
1692 support for Unicode and double-width characters, as well as
1693 support for UEFI and integration with the KMS kernel video
1696 You may need to update your console settings in /etc/rc.conf,
1697 most probably the keymap. During boot, /etc/rc.d/syscons will
1698 indicate what you need to do.
1700 vt(4) still has issues and lacks some features compared to
1701 syscons(4). See the wiki for up-to-date information:
1702 https://wiki.freebsd.org/Newcons
1704 If you want to keep using syscons(4), you can do so by adding
1705 the following line to /boot/loader.conf:
1709 pjdfstest has been integrated into kyua as an opt-in test suite.
1710 Please see share/doc/pjdfstest/README for more details on how to
1714 gperf has been removed from the base system for architectures
1715 that use clang. Ports that require gperf will obtain it from the
1719 pjdfstest has been moved from tools/regression/pjdfstest to
1723 At svn r271982, The default linux compat kernel ABI has been adjusted
1724 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1725 update. If you wish to continue using the linux-f10 compat ports,
1726 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1727 encouraged to update their linux-compat packages to linux-c6 during
1728 their next update cycle.
1731 The ofwfb driver, used to provide a graphics console on PowerPC when
1732 using vt(4), no longer allows mmap() of all physical memory. This
1733 will prevent Xorg on PowerPC with some ATI graphics cards from
1734 initializing properly unless x11-servers/xorg-server is updated to
1738 The xdev targets have been converted to using TARGET and
1739 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1742 The default unbound configuration has been modified to address
1743 issues with reverse lookups on networks that use private
1744 address ranges. If you use the local_unbound service, run
1745 "service local_unbound setup" as root to regenerate your
1746 configuration, then "service local_unbound reload" to load the
1750 The GNU texinfo and GNU info pages are not built and installed
1751 anymore, WITH_INFO knob has been added to allow to built and install
1753 UPDATE: see 20150102 entry on texinfo's removal
1756 The GNU readline library is now an INTERNALLIB - that is, it is
1757 statically linked into consumers (GDB and variants) in the base
1758 system, and the shared library is no longer installed. The
1759 devel/readline port is available for third party software that
1763 The Itanium architecture (ia64) has been removed from the list of
1764 known architectures. This is the first step in the removal of the
1768 Commit r268115 has added NFSv4.1 server support, merged from
1769 projects/nfsv4.1-server. Since this includes changes to the
1770 internal interfaces between the NFS related modules, a full
1771 build of the kernel and modules will be necessary.
1772 __FreeBSD_version has been bumped.
1775 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1776 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1777 which differs from the behaviour controlled by this knob.)
1780 Maximal length of the serial number in CTL was increased from 16 to
1781 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1782 and ctld, need to be rebuilt to work with a new kernel.
1785 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1786 1 respectively to match the upstream numbers. They were out of
1787 sync because, when they were originally added to FreeBSD, the
1788 upstream versions were not respected. These libraries are private
1789 and not yet built by default, so renumbering them should be a
1790 non-issue. However, unclean source trees will yield broken test
1791 programs once the operator executes "make delete-old-libs" after a
1792 "make installworld".
1794 Additionally, the atf-sh binary was made private by moving it into
1795 /usr/libexec/. Already-built shell test programs will keep the
1796 path to the old binary so they will break after "make delete-old"
1799 If you are using WITH_TESTS=yes (not the default), wipe the object
1800 tree and rebuild from scratch to prevent spurious test failures.
1801 This is only needed once: the misnumbered libraries and misplaced
1802 binaries have been added to OptionalObsoleteFiles.inc so they will
1803 be removed during a clean upgrade.
1806 Clang and llvm have been upgraded to 3.4.1 release.
1809 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1810 be removed to avoid issues in the future (and has been added to
1814 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1815 past, it affected all builds that used the bsd.*.mk files. The old
1816 behavior was a bug, but people may have relied upon it. To get this
1817 behavior back, you can .include /etc/src.conf from /etc/make.conf
1818 (which is still global and isn't changed). This also changes the
1819 behavior of incremental builds inside the tree of individual
1820 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1821 Although this has survived make universe and some upgrade scenarios,
1822 other upgrade scenarios may have broken. At least one form of
1823 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1824 as well... In cases where MAKESYSPATH isn't working with this
1825 setting, you'll need to set it to the full path to your tree.
1827 One side effect of all this cleaning up is that bsd.compiler.mk
1828 is no longer implicitly included by bsd.own.mk. If you wish to
1829 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1833 The lindev device has been removed since /dev/full has been made a
1834 standard device. __FreeBSD_version has been bumped.
1837 The knob WITHOUT_VI was added to the base system, which controls
1838 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1839 in order to reorder files share/termcap and didn't build ex(1) as a
1840 build tool, so building/installing with WITH_VI is highly advised for
1841 build hosts for older releases.
1843 This issue has been fixed in stable/9 and stable/10 in r277022 and
1844 r276991, respectively.
1847 The YES_HESIOD knob has been removed. It has been obsolete for
1848 a decade. Please move to using WITH_HESIOD instead or your builds
1849 will silently lack HESIOD.
1852 The uart(4) driver has been changed with respect to its handling
1853 of the low-level console. Previously the uart(4) driver prevented
1854 any process from changing the baudrate or the CLOCAL and HUPCL
1855 control flags. By removing the restrictions, operators can make
1856 changes to the serial console port without having to reboot.
1857 However, when getty(8) is started on the serial device that is
1858 associated with the low-level console, a misconfigured terminal
1859 line in /etc/ttys will now have a real impact.
1860 Before upgrading the kernel, make sure that /etc/ttys has the
1861 serial console device configured as 3wire without baudrate to
1862 preserve the previous behaviour. E.g:
1863 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1866 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1867 to improve performance. To re-enable it, if needed, run rpcbind
1868 with command line option -W.
1871 Switched back to the GPL dtc compiler due to updates in the upstream
1872 dts files not being supported by the BSDL dtc compiler. You will need
1873 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1874 may result while building dtb files during a kernel build if you fail
1875 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1878 Clang and llvm have been upgraded to 3.4 release.
1881 The nve(4) driver has been removed. Please use the nfe(4) driver
1882 for NVIDIA nForce MCP Ethernet adapters instead.
1885 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1886 This could cause certain C++ applications using shared libraries built
1887 against the previous version of libc++ to crash. The incompatibility
1888 has now been fixed, but any C++ applications or shared libraries built
1889 between r261283 and r261801 should be recompiled.
1892 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1893 capability mode support. Please note that enabling the feature in
1894 kernel is still highly recommended.
1897 OpenSSH is now built with sandbox support, and will use sandbox as
1898 the default privilege separation method. This requires Capsicum
1899 capability mode support in kernel.
1902 The libelf and libdwarf libraries have been updated to newer
1903 versions from upstream. Shared library version numbers for
1904 these two libraries were bumped. Any ports or binaries
1905 requiring these two libraries should be recompiled.
1906 __FreeBSD_version is bumped to 1100006.
1909 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1910 instead of providing an explicit one, this would prevent such
1911 Makefile from providing its own Kyuafile in the future during
1912 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1913 intervention is needed to clean an objdir if you use NO_CLEAN:
1914 # find /usr/obj -name Kyuafile | xargs rm -f
1917 The behavior of gss_pseudo_random() for the krb5 mechanism
1918 has changed, for applications requesting a longer random string
1919 than produced by the underlying enctype's pseudo-random() function.
1920 In particular, the random string produced from a session key of
1921 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1922 be different at the 17th octet and later, after this change.
1923 The counter used in the PRF+ construction is now encoded as a
1924 big-endian integer in accordance with RFC 4402.
1925 __FreeBSD_version is bumped to 1100004.
1928 The WITHOUT_ATF build knob has been removed and its functionality
1929 has been subsumed into the more generic WITHOUT_TESTS. If you were
1930 using the former to disable the build of the ATF libraries, you
1931 should change your settings to use the latter.
1934 The default version of mtree is nmtree which is obtained from
1935 NetBSD. The output is generally the same, but may vary
1936 slightly. If you found you need identical output adding
1937 "-F freebsd9" to the command line should do the trick. For the
1938 time being, the old mtree is available as fmtree.
1941 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1942 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1943 1.1.4_8 and verify bsdyml not linked in, before running "make
1945 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1947 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1950 The stable/10 branch has been created in subversion from head
1957 Avoid using make -j when upgrading. While generally safe, there are
1958 sometimes problems using -j to upgrade. If your upgrade fails with
1959 -j, please try again without -j. From time to time in the past there
1960 have been problems using -j with buildworld and/or installworld. This
1961 is especially true when upgrading between "distant" versions (eg one
1962 that cross a major release boundary or several minor releases, or when
1963 several months have passed on the -current branch).
1965 Sometimes, obscure build problems are the result of environment
1966 poisoning. This can happen because the make utility reads its
1967 environment when searching for values for global variables. To run
1968 your build attempts in an "environmental clean room", prefix all make
1969 commands with 'env -i '. See the env(1) manual page for more details.
1971 When upgrading from one major version to another it is generally best to
1972 upgrade to the latest code in the currently installed branch first, then
1973 do an upgrade to the new branch. This is the best-tested upgrade path,
1974 and has the highest probability of being successful. Please try this
1975 approach if you encounter problems with a major version upgrade. Since
1976 the stable 4.x branch point, one has generally been able to upgrade from
1977 anywhere in the most recent stable branch to head / current (or even the
1978 last couple of stable branches). See the top of this file when there's
1981 When upgrading a live system, having a root shell around before
1982 installing anything can help undo problems. Not having a root shell
1983 around can lead to problems if pam has changed too much from your
1984 starting point to allow continued authentication after the upgrade.
1986 This file should be read as a log of events. When a later event changes
1987 information of a prior event, the prior event should not be deleted.
1988 Instead, a pointer to the entry with the new information should be
1989 placed in the old entry. Readers of this file should also sanity check
1990 older entries before relying on them blindly. Authors of new entries
1991 should write them with this in mind.
1995 When upgrading the boot ZFS pool to a new version, always follow
1998 1.) recompile and reinstall the ZFS boot loader and boot block
1999 (this is part of "make buildworld" and "make installworld")
2001 2.) update the ZFS boot block on your boot drive
2003 The following example updates the ZFS boot block on the first
2004 partition (freebsd-boot) of a GPT partitioned drive ada0:
2005 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2007 Non-boot pools do not need these updates.
2011 If you are updating from a prior version of FreeBSD (even one just
2012 a few days old), you should follow this procedure. It is the most
2013 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2015 make kernel-toolchain
2016 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2017 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2019 To test a kernel once
2020 ---------------------
2021 If you just want to boot a kernel once (because you are not sure
2022 if it works, or if you want to boot a known bad kernel to provide
2023 debugging information) run
2024 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2025 nextboot -k testkernel
2027 To rebuild everything and install it on the current system.
2028 -----------------------------------------------------------
2029 # Note: sometimes if you are running current you gotta do more than
2030 # is listed here if you are upgrading from a really old current.
2032 <make sure you have good level 0 dumps>
2034 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2035 make installkernel KERNCONF=YOUR_KERNEL_HERE
2037 <reboot in single user> [3]
2044 To cross-install current onto a separate partition
2045 --------------------------------------------------
2046 # In this approach we use a separate partition to hold
2047 # current's root, 'usr', and 'var' directories. A partition
2048 # holding "/", "/usr" and "/var" should be about 2GB in
2051 <make sure you have good level 0 dumps>
2054 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2055 <maybe newfs current's root partition>
2056 <mount current's root partition on directory ${CURRENT_ROOT}>
2057 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2058 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2059 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2060 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2061 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2062 <reboot into current>
2063 <do a "native" rebuild/install as described in the previous section>
2064 <maybe install compatibility libraries from ports/misc/compat*>
2068 To upgrade in-place from stable to current
2069 ----------------------------------------------
2070 <make sure you have good level 0 dumps>
2072 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2073 make installkernel KERNCONF=YOUR_KERNEL_HERE
2075 <reboot in single user> [3]
2082 Make sure that you've read the UPDATING file to understand the
2083 tweaks to various things you need. At this point in the life
2084 cycle of current, things change often and you are on your own
2085 to cope. The defaults can also change, so please read ALL of
2086 the UPDATING entries.
2088 Also, if you are tracking -current, you must be subscribed to
2089 freebsd-current@freebsd.org. Make sure that before you update
2090 your sources that you have read and understood all the recent
2091 messages there. If in doubt, please track -stable which has
2092 much fewer pitfalls.
2094 [1] If you have third party modules, such as vmware, you
2095 should disable them at this point so they don't crash your
2098 [3] From the bootblocks, boot -s, and then do
2103 adjkerntz -i # if CMOS is wall time
2104 Also, when doing a major release upgrade, it is required that
2105 you boot into single user mode to do the installworld.
2107 [4] Note: This step is non-optional. Failure to do this step
2108 can result in a significant reduction in the functionality of the
2109 system. Attempting to do it by hand is not recommended and those
2110 that pursue this avenue should read this file carefully, as well
2111 as the archives of freebsd-current and freebsd-hackers mailing lists
2112 for potential gotchas. The -U option is also useful to consider.
2113 See mergemaster(8) for more information.
2115 [5] Usually this step is a no-op. However, from time to time
2116 you may need to do this if you get unknown user in the following
2117 step. It never hurts to do it all the time. You may need to
2118 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2119 install) after the buildworld before this step if you last updated
2120 from current before 20130425 or from -stable before 20130430.
2122 [6] This only deletes old files and directories. Old libraries
2123 can be deleted by "make delete-old-libs", but you have to make
2124 sure that no program is using those libraries anymore.
2126 [8] The new kernel must be able to run existing binaries used by
2127 an installworld. When upgrading across major versions, the new
2128 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2129 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2130 binaries). Failure to do so may leave you with a system that is
2131 hard to boot to recover. A GENERIC kernel will include suitable
2132 compatibility options to run binaries from older branches.
2134 Make sure that you merge any new devices from GENERIC since the
2135 last time you updated your kernel config file.
2137 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2138 "?=" instead of the "=" assignment operator, so that buildworld can
2139 override the CPUTYPE if it needs to.
2141 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2142 not on the command line, or in /etc/make.conf. buildworld will
2143 warn if it is improperly defined.
2146 This file contains a list, in reverse chronological order, of major
2147 breakages in tracking -current. It is not guaranteed to be a complete
2148 list of such breakages, and only contains entries since September 23, 2011.
2149 If you need to see UPDATING entries from before that date, you will need
2150 to fetch an UPDATING file from an older FreeBSD release.
2152 Copyright information:
2154 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2156 Redistribution, publication, translation and use, with or without
2157 modification, in full or in part, in any form or format of this
2158 document are permitted without further permission from the author.
2160 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2161 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2162 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2163 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2164 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2165 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2166 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2167 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2168 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2169 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2170 POSSIBILITY OF SUCH DAMAGE.
2172 Contact Warner Losh if you have any questions about your use of