1 Updating Information for FreeBSD current 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 20201208: p12 FreeBSD-SA-20:33.openssl
21 Fix OpenSSL NULL pointer de-reference. [SA-20:33.openssl]
23 20201201: p11 FreeBSD-EN-20:20.tzdata
24 FreeBSD-SA-20:31.icmp6
25 FreeBSD-SA-20:32.rtsold
27 Update timezone database information. [EN-20:20.tzdata]
29 Fix ICMPv6 use-after-free in error message handling. [SA-20:31.icmp6]
31 Fix multiple vulnerabilities in rtsold. [SA-20:32.rtsold]
33 20200915 p10 FreeBSD-SA-20:27.ure
34 FreeBSD-SA-20:28.bhyve_vmcs
35 FreeBSD-SA-20:29.bhyve_svm
38 Fix ure device driver susceptible to packet-in-packet attack.
41 Fix bhyve privilege escalation via VMCS access. [SA-20:28.bhyve_vmcs]
43 Fix bhyve SVM guest escape. [SA-20:29.bhyve_svm]
45 Fix ftpd privilege escalation via ftpchroot. [SA-20:30.ftpd]
47 20200902 p9 FreeBSD-EN-20:17.linuxthread
49 FreeBSD-SA-20:26.dhclient
51 Fix FreeBSD Linux ABI kernel panic. [EN-20:17.linuxthread]
53 Fix SCTP socket use-after-free. [SA-20:25.sctp]
55 Fix dhclient heap overflow. [SA-20:26.dhclient]
57 20200805 p8 FreeBSD-EN-20:16.vmx
58 FreeBSD-SA-20:21.usb_net
59 FreeBSD-SA-20:22.unbound
62 Fix vmx driver packet loss and degraded performance. [EN-20:16.vmx]
64 Fix memory corruption in USB network device drivers. [SA-20:21.usb_net]
66 Fix multiple vulnerabilities in sqlite3. [SA-20:22.sqlite]
68 Fix sendmsg(2) privilege escalation. [SA-20:23.sendmsg]
70 20200708 p7 FreeBSD-EN-20:13.bhyve
71 FreeBSD-EN-20:14.linuxkpi
73 FreeBSD-SA-20:19.unbound
76 Fix host crash in bhyve with PCI device passthrough. [EN-20:13.bhyve]
78 Fix kernel panic in LinuxKPI subsystem. [EN-20:14.linuxpki]
80 Fix kernel panic in mps(4) driver. [EN-20:15.mps]
82 Fix multiple vulnerabilities in unbound. [SA-20:19.unbound]
84 Fix IPv6 socket option race condition and use after free. [SA-20:20.ipv6]
86 20200609 p6 FreeBSD-EN-20:11.ena
87 FreeBSD-EN-20:12.iflib
90 Fix stability issues in ena(4) driver. [EN-20:11.ena]
92 Fix iflib watchdog timeout resetting idle queues. [EN-20:12.iflib]
94 Fix USB HID descriptor parsing error. [SA-20:17.usb]
96 20200512 p5 FreeBSD-EN-20:08.tzdata
98 FreeBSD-EN-20:10.build
99 FreeBSD-SA-20:12.libalias
100 FreeBSD-SA-20:13.libalias
101 FreeBSD-SA-20:15.cryptodev
102 FreeBSD-SA-20:16.cryptodev
104 Import tzdata 2020a. [EN-20:08.tzdata]
106 Fix igb interfaces failing to switch to inactive state [EN-20:09.igb]
108 Fix incorrect build host Clang version detection [EN-20:10.build]
110 Fix insufficient packet length validation in libalias [SA-20:12.libalias]
112 Fix memory disclosure vulnerability in libalias [SA-20:13.libalias]
114 Fix use after free in cryptodev module [SA-20:15.cryptodev]
116 Fix insufficient cryptodev MAC key length check [SA-20:16.cryptodev]
118 20200421 p4 FreeBSD-EN-20:07.quotad
119 FreeBSD-SA-20:10.ipfw
120 FreeBSD-SA-20:11.openssl
122 Fix regression in rpc.rquotad with certain NFS servers [EN-20:07.quotad]
124 Fix ipfw invalid mbuf handling [SA-20:10.ipfw]
126 Fix OpenSSL remote denial of service vulnerability [SA-20:11.openssl]
128 20200319 p3 FreeBSD-EN-20:03.sshd
129 FreeBSD-EN-20:05.mlx5en
130 FreeBSD-EN-20:06.ipv6
132 FreeBSD-SA-20:05.if_oce_ioctl
133 FreeBSD-SA-20:06.if_ixl_ioctl
134 FreeBSD-SA-20:07.epair
135 FreeBSD-SA-20:08.jail
138 Fix misleading log messages upon successful sshd login [EN-20:03.sshd]
140 Fix packet forwarding performance in mlx5en(4) driver [EN-20:05.mlx5en]
142 Fix incorrect checksum calculations with IPv6 extension headers [EN-20:06.ipv6]
144 Fix TCP IPv6 SYN cache kernel information disclosure [SA-20:04.tcp]
146 Fix insufficient oce(4) ioctl(2) privilege checking [SA-20:05.if_oce_ioctl]
148 Fix insufficient ixl(4) ioctl(2) privilege checking [SA-20:06.if_ixl_ioctl]
150 Fix incorrect user-controlled pointer use in epair [SA-20:07.epair]
152 Fix kernel memory disclosure with nested jails [SA-20:08.jail]
154 Fix multiple denial of service in ntpd [SA-20:09.ntp]
156 20200128 p2 FreeBSD-EN-20:01.ssp
157 FreeBSD-SA-20:01.libfetch
158 FreeBSD-SA-20:03.thrmisc
160 Fix imprecise ordering of SSP canary initialization [EN-20:01.ssp]
162 Fix libfetch buffer overflow [SA-20:01.libfetch]
164 Fix kernel stack data disclosure [SA-20:03.thrmisc]
166 20191112 p1 FreeBSD-EN-19:19.loader
167 FreeBSD-SA-19:25.mcepsc
169 Fix UEFI Loader Memory Fragmentation [EN-19:19.loader]
171 Fix Machine Check Exception on Page Size Change [SA-19:25.mcepsc]
177 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
178 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
179 been removed from mount_fusefs(8). You can safely remove them from
180 your scripts, because they had no effect.
182 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
183 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
184 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
185 sysctls have been removed. If you felt the need to set any of them to
186 a non-default value, please tell asomers@FreeBSD.org why.
189 The fuse(4) module has been renamed to fusefs(4) for consistency with
190 other filesystems. You should update any kld_load="fuse" entries in
191 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
192 "options FUSE" enties in kernel config files.
195 Default permissions on the /var/account/acct file (and copies of it
196 rotated by periodic daily scripts) are changed from 0644 to 0640
197 because the file contains sensitive information that should not be
198 world-readable. If the /var/account directory must be created by
199 rc.d/accounting, the mode used is now 0750. Admins who use the
200 accounting feature are encouraged to change the mode of an existing
201 /var/account directory to 0750 or 0700.
204 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
205 been upgraded to 8.0.1. Please see the 20141231 entry below for
206 information about prerequisites and upgrading, if you are not already
207 using clang 3.5.0 or higher.
210 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
211 functionality needed for the RETPOLINE option should work properly
212 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
215 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
216 8.0.0. Please see the 20141231 entry below for information about
217 prerequisites and upgrading, if you are not already using clang 3.5.0
221 The RETPOLINE option produces non-functional ifunc-using binaries
222 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
223 Once Clang 8 is merged it may be enabled again.
226 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
227 7.0.1. Please see the 20141231 entry below for information about
228 prerequisites and upgrading, if you are not already using clang 3.5.0
232 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
233 compiled into your custom kernel, add 'device xz' statement to the
237 Iflib is no longer unconditionally compiled into the kernel. Drivers
238 using iflib and statically compiled into the kernel, now require
239 the 'device iflib' config option. For the same drivers loaded as
240 modules on kernels not having 'device iflib', the iflib.ko module
241 is loaded automatically.
244 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
245 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
246 servers that have vfs.nfsd.nfs_privport set will only allow mounts
247 from clients using a reserved port#. Since both the FreeBSD and Linux
248 NFSv4 clients use reserved port#s by default, this should not affect
252 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
253 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
254 it produces broken binaries when ifuncs are in use. Users needing
255 GNU ld should install the binutils port or package.
258 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
259 has been converted to a port (misc/ctm) and will be removed from
260 FreeBSD-13. A depreciation warning will be printed to stderr by
261 the ctm command, but the functionality will remain in base for all
265 The stable/12 branch has been created in subversion from head
269 Ports for the DRM modules have been simplified. Now, amd64 users should
270 just install the drm-kmod port. All others should install
273 Graphics hardware that's newer than about 2010 usually works with
274 drm-kmod. For hardware older than 2013, however, some users will need
275 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
276 than 2008 usually only works in drm-legacy-kmod. The graphics team can
277 only commit to hardware made since 2013 due to the complexity of the
278 market and difficulty to test all the older cards effectively. If you
279 have hardware supported by drm-kmod, you are strongly encouraged to use
280 that as you will get better support.
282 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
283 elsewhere, the drm and drm2 modules will be eliminated from the src base
284 soon (with a limited exception for arm). Please update to the package asap
285 and report any issues to x11@freebsd.org.
287 Generally, anybody using the drm*-kmod packages should add
288 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
289 cross-threading surprises, especially with automatic driver
290 loading from X11 startup. These will become the defaults in 13-current
294 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
295 custom kernel and module loading configuration files must be updated
296 accordingly. Moreover, interfaces previous presented as ixlvN to the
297 system are now exposed as iavfN and network configuration files must
298 be adjusted as necessary.
301 OpenSSL has been updated to version 1.1.1. This update included
302 additional various API changes througout the base system. It is
303 important to rebuild third-party software after upgrading. The value
304 of __FreeBSD_version has been bumped accordingly.
307 The legacy DRM modules and drivers have now been added to the loader's
308 module blacklist, in favor of loading them with kld_list in rc.conf(5).
309 The module blacklist may be overridden with the loader.conf(5)
310 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
314 The cam(4) based nda(4) driver will be used over nvd(4) by default on
315 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
316 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
317 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
321 Reproducible build mode is now on by default, in preparation for
322 FreeBSD 12.0. This eliminates build metadata such as the user,
323 host, and time from the kernel (and uname), unless the working tree
324 corresponds to a modified checkout from a version control system.
325 The previous behavior can be obtained by setting the /etc/src.conf
326 knob WITHOUT_REPRODUCIBLE_BUILD.
329 The Yarrow CSPRNG has been removed from the kernel as it has not been
330 supported by its designers since at least 2003. Fortuna has been the
331 default since FreeBSD-11.
334 devctl freeze/thaw have gone into the tree, the rc scripts have been
335 updated to use them and devmatch has been changed. You should update
336 kernel, userland and rc scripts all at the same time.
339 The default interpreter has been switched from 4th to Lua.
340 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
341 interpreter. If you have custom FORTH code you will need to set
342 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
343 src.conf for the build. This will create default hard links between
344 loader and loader_4th instead of loader and loader_lua, the new default.
345 If you are using UEFI it will create the proper hard link to loader.efi.
347 bhyve uses userboot.so. It remains 4th-only until some issues are solved
348 regarding coexisting with multiple versions of FreeBSD are resolved.
351 ls(1) now respects the COLORTERM environment variable used in other
352 systems and software to indicate that a colored terminal is both
353 supported and desired. If ls(1) is suddenly emitting colors, they may
354 be disabled again by either removing the unwanted COLORTERM from your
355 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
356 may not be observed in a future release.
359 The default pager for most commands has been changed to "less". To
360 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
364 The jedec_ts(4) driver has been removed. A superset of its functionality
365 is available in the jedec_dimm(4) driver, and the manpage for that
366 driver includes migration instructions. If you have "device jedec_ts"
367 in your kernel configuration file, it must be removed.
370 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
371 This should have no effect if the kernel is booted via BIOS/legacy boot.
372 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
373 has a buggy firmware that prevents a successful boot due to use of
377 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
378 support has been removed from the tree. These ports were
379 obsolete and/or known to be broken for many years.
382 loader.efi has been augmented to participate more fully in the
383 UEFI boot manager protocol. loader.efi will now look at the
384 BootXXXX environment variable to determine if a specific kernel
385 or root partition was specified. XXXX is derived from BootCurrent.
386 efibootmgr(8) manages these standard UEFI variables.
389 zfsloader's functionality has now been folded into loader.
390 zfsloader is no longer necessary once you've updated your
391 boot blocks. For a transition period, we will install a
392 hardlink for zfsloader to loader to allow a smooth transition
393 until the boot blocks can be updated (hard link because old
394 zfs boot blocks don't understand symlinks).
397 ARM64 now have efifb support, if you want to have serial console
398 on your arm64 board when an screen is connected and the bootloader
399 setup a frambuffer for us to use, just add :
403 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
404 an screen connected as the firmware will setup a framebuffer are that
405 u-boot will expose as an EFI framebuffer.
408 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
409 or take steps to update /etc/passwd before doing installworld on
410 existing systems. Do not skip the "mergemaster -Fp" step before
411 installworld, as described in the update procedures near the bottom
412 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
413 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
414 the ntp config file contain options that change file/dir locations.
415 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
416 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
417 taking steps to ensure that all required files/dirs are accessible
421 Big endian arm support has been removed.
424 The static environment setup in kernel configs is no longer mutually
425 exclusive with the loader(8) environment by default. In order to
426 restore the previous default behavior of disabling the loader(8)
427 environment if a static environment is present, you must specify
428 loader_env.disabled=1 in the static environment.
431 The ABI of syscalls used by management tools like sockstat and
432 netstat has been broken to allow 32-bit binaries to work on
433 64-bit kernels without modification. These programs will need
434 to match the kernel in order to function. External programs may
435 require minor modifications to accommodate a change of type in
436 structures from pointers to 64-bit virtual addresses.
439 On i386 and amd64 atomics are now inlined. Out of tree modules using
440 atomics will need to be rebuilt.
443 The '%I' format in the kern.corefile sysctl limits the number of
444 core files that a process can generate to the number stored in the
445 debug.ncores sysctl. The '%I' format is replaced by the single digit
446 index. Previously, if all indexes were taken the kernel would overwrite
447 only a core file with the highest index in a filename.
448 Currently the system will create a new core file if there is a free
449 index or if all slots are taken it will overwrite the oldest one.
452 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
453 6.0.1. Please see the 20141231 entry below for information about
454 prerequisites and upgrading, if you are not already using clang 3.5.0
458 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
459 needed to be changed to work with it. This change was made with r335763
460 and requires a mergemaster / etcupdate / etc to update the installed file.
463 r334930 changed the interface between the NFS modules, so they all
464 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
467 As of r334391 lld is the default amd64 system linker; it is installed
468 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
472 The kernel / userland interface for devinfo changed, so you'll
473 need a new kernel and userland as a pair for it to work (rebuilding
474 lib/libdevinfo is all that's required). devinfo and devmatch will
475 not work, but everything else will when there's a mismatch.
478 The on-disk format for hwpmc callchain records has changed to include
479 threadid corresponding to a given record. This changes the field offsets
480 and thus requires that libpmcstat be rebuilt before using a kernel
484 The vxge(4) driver has been removed. This driver was introduced into
485 HEAD one week before the Exar left the Ethernet market and is not
486 known to be used. If you have device vxge in your kernel config file
490 The amd64 kernel now requires a ld that supports ifunc to produce a
491 working kernel, either lld or a newer binutils. lld is built by default
492 on amd64, and the 'buildkernel' target uses it automatically. However,
493 it is not the default linker, so building the kernel the traditional
494 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
495 binutils port/package). lld will soon be default, and this requirement
498 NOTE: As of r334391 lld is the default system linker on amd64, and no
499 workaround is necessary.
502 The nxge(4) driver has been removed. This driver was for PCI-X 10g
503 cards made by s2io/Neterion. The company was aquired by Exar and
504 no longer sells or supports Ethernet products. If you have device
505 nxge in your kernel config file it must be removed.
508 The tz database (tzdb) has been updated to 2018e. This version more
509 correctly models time stamps in time zones with negative DST such as
510 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
511 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
512 time zone abbreviations and the tm_isdst flag.
515 The ixgb(4) driver has been removed. This driver was for an early and
516 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
517 quickly shifted to the long lived ixgbe family. If you have device
518 ixgb in your kernel config file it must be removed.
521 The lmc(4) driver has been removed. This was a WAN interface
522 card that was already reportedly rare in 2003, and had an ambiguous
523 license. If you have device lmc in your kernel config file it must
527 Support for Arcnet networks has been removed. If you have device
528 arcnet or device cm in your kernel config file they must be
532 Support for FDDI networks has been removed. If you have device
533 fddi or device fpa in your kernel config file they must be
537 In addition to supporting RFC 3164 formatted messages, the
538 syslogd(8) service is now capable of parsing RFC 5424 formatted
539 log messages. The main benefit of using RFC 5424 is that clients
540 may now send log messages with timestamps containing year numbers,
541 microseconds and time zone offsets.
543 Similarly, the syslog(3) C library function has been altered to
544 send RFC 5424 formatted messages to the local system logging
545 daemon. On systems using syslogd(8), this change should have no
546 negative impact, as long as syslogd(8) and the C library are
547 updated at the same time. On systems using a different system
548 logging daemon, it may be necessary to make configuration
549 adjustments, depending on the software used.
551 When using syslog-ng, add the 'syslog-protocol' flag to local
552 input sources to enable parsing of RFC 5424 formatted messages:
555 unix-dgram("/var/run/log" flags(syslog-protocol));
558 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
559 of the 'imuxsock' module to let messages be processed by the
560 regular RFC 3164/5424 parsing pipeline:
562 module(load="imuxsock" SysSock.UseSpecialParser="off")
564 Do note that these changes only affect communication between local
565 applications and syslogd(8). The format that syslogd(8) uses to
566 store messages on disk or forward messages to other systems
567 remains unchanged. syslogd(8) still uses RFC 3164 for these
568 purposes. Options to customize this behaviour will be added in the
569 future. Utilities that process log files stored in /var/log are
570 thus expected to continue to function as before.
572 __FreeBSD_version has been incremented to 1200061 to denote this
576 Support for token ring networks has been removed. If you
577 have "device token" in your kernel config you should remove
578 it. No device drivers supported token ring.
581 makefs was modified to be able to tag ISO9660 El Torito boot catalog
582 entries as EFI instead of overloading the i386 tag as done previously.
583 The amd64 mkisoimages.sh script used to build amd64 ISO images for
584 release was updated to use this. This may mean that makefs must be
585 updated before "make cdrom" can be run in the release directory. This
586 should be as simple as:
588 $ cd $SRCDIR/usr.sbin/makefs
589 $ make depend all install
592 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
593 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
594 Co-existance for the transition period will come shortly. Booting is a
595 complex environment and test coverage for Lua-enabled loaders has been
596 thin, so it would be prudent to assume it might not work and make
597 provisions for backup boot methods.
600 devmatch functionality has been turned on in devd. It will automatically
601 load drivers for unattached devices. This may cause unexpected drivers to
602 be loaded. Please report any problems to current@ and imp@freebsd.org.
605 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
606 6.0.0. Please see the 20141231 entry below for information about
607 prerequisites and upgrading, if you are not already using clang 3.5.0
611 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
612 This means it is used to link the kernel and userland libraries and
613 executables, but is not yet installed as /usr/bin/ld by default.
615 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
616 WITHOUT_LLD_BOOTSTRAP=yes
619 On i386, pmtimer has been removed. Its functionality has been folded
620 into apm. It was a no-op on ACPI in current for a while now (but was still
621 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
622 from kernel config files.
625 The use of RSS hash from the network card aka flowid has been
626 disabled by default for lagg(4) as it's currently incompatible with
627 the lacp and loadbalance protocols.
629 This can be re-enabled by setting the following in loader.conf:
630 net.link.lagg.default_use_flowid="1"
633 The SW_WATCHDOG option is no longer necessary to enable the
634 hardclock-based software watchdog if no hardware watchdog is
635 configured. As before, SW_WATCHDOG will cause the software
636 watchdog to be enabled even if a hardware watchdog is configured.
639 r326887 fixes the issue described in the 20171214 UPDATING entry.
640 r326888 flips the switch back to building GELI support always.
643 r362593 broke ZFS + GELI support for reasons unknown. However,
644 it also broke ZFS support generally, so GELI has been turned off
645 by default as the lesser evil in r326857. If you boot off ZFS and/or
646 GELI, it might not be a good time to update.
649 PowerPC users must update loader(8) by rebuilding world before
650 installing a new kernel, as the protocol connecting them has
651 changed. Without the update, loader metadata will not be passed
652 successfully to the kernel and users will have to enter their
653 root partition at the kernel mountroot prompt to continue booting.
654 Newer versions of loader can boot old kernels without issue.
657 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
658 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
659 to WITH/OUT_LOADER_GELI.
662 The naive and non-compliant support of posix_fallocate(2) in ZFS
663 has been removed as of r325320. The system call now returns EINVAL
664 when used on a ZFS file. Although the new behavior complies with the
665 standard, some consumers are not prepared to cope with it.
666 One known victim is lld prior to r325420.
669 Building in a FreeBSD src checkout will automatically create object
670 directories now rather than store files in the current directory if
671 'make obj' was not ran. Calling 'make obj' is no longer necessary.
672 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
673 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
677 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
678 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
679 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
680 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
681 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
682 The UNIFIED_OBJDIR option is a transitional feature that will be
683 removed for 12.0 release; please migrate to the new format for any
684 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
685 than hardcoding paths.
688 The native-xtools target no longer installs the files by default to the
689 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
690 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
693 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
694 options are changing from controlling the build if defined / undefined
695 to controlling the build with explicit 'yes' or 'no' values. They will
696 shift to WITH/WITHOUT options to match other options in the system.
699 libstand has turned into a private library for sys/boot use only.
700 It is no longer supported as a public interface outside of sys/boot.
703 The arm port has split armv6 into armv6 and armv7. armv7 is now
704 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
705 and are running a kernel from before r324363, you will need to add
706 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
709 When building multiple kernels using KERNCONF, non-existent KERNCONF
710 files will produce an error and buildkernel will fail. Previously
711 missing KERNCONF files silently failed giving no indication as to
712 why, only to subsequently discover during installkernel that the
713 desired kernel was never built in the first place.
716 The default serial number format for CTL LUNs has changed. This will
717 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
718 or iSCSI clients care about their LUNs' serial numbers. Users who
719 require serial number stability should hardcode serial numbers in
723 For 32-bit arm compiled for hard-float support, soft-floating point
724 binaries now always get their shared libraries from
725 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
726 /usr/libsoft also existed). Only users with a hard-float ld.so, but
727 soft-float everything else should be affected.
730 The geli password typed at boot is now hidden. To restore the previous
731 behavior, see geli(8) for configuration options.
734 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
735 sysctl values. Minor nit, but requires a rebuild of both world/kernel
739 "make check" behavior (made in ^/head@r295380) has been changed to
740 execute from a limited sandbox, as opposed to executing from
744 - The "beforecheck" and "aftercheck" targets are now specified.
745 - ${CHECKDIR} (added in commit noted above) has been removed.
746 - Legacy behavior can be enabled by setting
747 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
749 If the limited sandbox mode is enabled, "make check" will execute
750 "make distribution", then install, execute the tests, and clean up the
751 sandbox if successful.
753 The "make distribution" and "make install" targets are typically run as
754 root to set appropriate permissions and ownership at installation time.
755 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
756 environment if executing "make check" with limited sandbox mode using
757 an unprivileged user.
760 Since the switch to GPT disk labels, fsck for UFS/FFS has been
761 unable to automatically find alternate superblocks. As of r322297,
762 the information needed to find alternate superblocks has been
763 moved to the end of the area reserved for the boot block.
764 Filesystems created with a newfs of this vintage or later
765 will create the recovery information. If you have a filesystem
766 created prior to this change and wish to have a recovery block
767 created for your filesystem, you can do so by running fsck in
768 foreground mode (i.e., do not use the -p or -y options). As it
769 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
770 to which you should answer yes.
773 As of r321665, an NFSv4 server configuration that services
774 Kerberos mounts or clients that do not support the uid/gid in
775 owner/owner_group string capability, must explicitly enable
776 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
777 machine's /etc/rc.conf file.
780 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
781 Please see the 20141231 entry below for information about prerequisites
782 and upgrading, if you are not already using clang 3.5.0 or higher.
785 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
786 r-commands (rlogin, rsh, etc.) to be built with the base system.
789 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
790 a very major ABI incompatible change, so users of FreeBSD/powerpc must
791 be careful when performing source upgrades. It is best to run
792 'make installworld' from an alternate root system, either a live
793 CD/memory stick, or a temporary root partition. Additionally, all ports
794 must be recompiled. powerpc64 is largely unaffected, except in the case
795 of 32-bit compatibility. All 32-bit binaries will be affected.
798 Forward compatibility for the "ino64" project have been committed. This
799 will allow most new binaries to run on older kernels in a limited
800 fashion. This prevents many of the common foot-shooting actions in the
801 upgrade as well as the limited ability to roll back the kernel across
802 the ino64 upgrade. Complicated use cases may not work properly, though
803 enough simpler ones work to allow recovery in most situations.
806 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
807 if you require the GPL compiler.
810 The internal ABI used for communication between the NFS kernel modules
811 was changed by r320085, so __FreeBSD_version was bumped to
812 ensure all the NFS related modules are updated together.
815 The ABI of struct event was changed by extending the data
816 member to 64bit and adding ext fields. For upgrade, same
817 precautions as for the entry 20170523 "ino64" must be
821 The GNU roff toolchain has been removed from base. To render manpages
822 which are not supported by mandoc(1), man(1) can fallback on GNU roff
823 from ports (and recommends to install it).
824 To render roff(7) documents, consider using GNU roff from ports or the
825 heirloom doctools roff toolchain from ports via pkg install groff or
826 via pkg install heirloom-doctools.
829 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
830 smaller runtime footprint builds. This is useful for embedded systems
831 which only require one chipset support.
833 If you load it as a module, make sure this is in /boot/loader.conf:
837 This will load the HAL, all chip/RF backends and if_ath_pci.
838 If you have if_ath_pci in /boot/loader.conf, ensure it is after
839 if_ath or it will not load any HAL chipset support.
841 If you want to selectively load things (eg on ye cheape ARM/MIPS
842 platforms where RAM is at a premium) you should:
845 * load the chip modules in question
846 * load ath_rate, ath_dfs
848 * load if_ath_pci and/or if_ath_ahb depending upon your particular
849 bus bind type - this is where probe/attach is done.
851 For further comments/feedback, poke adrian@ .
854 The "ino64" 64-bit inode project has been committed, which extends
855 a number of types to 64 bits. Upgrading in place requires care and
856 adherence to the documented upgrade procedure.
858 If using a custom kernel configuration ensure that the
859 COMPAT_FREEBSD11 option is included (as during the upgrade the
860 system will be running the ino64 kernel with the existing world).
862 For the safest in-place upgrade begin by removing previous build
863 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
864 full procedure documented below under the heading "To rebuild
865 everything and install it on the current system." Specifically,
866 a reboot is required after installing the new kernel before
870 The NATM framework including the en(4), fatm(4), hatm(4), and
871 patm(4) devices has been removed. Consumers should plan a
872 migration before the end-of-life date for FreeBSD 11.
875 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
876 diff has not been implemented, if those are needed a newer version of
877 GNU diff is available via the diffutils package under the gdiff name.
880 As of r316810 for ipfilter, keep frags is no longer assumed when
881 keep state is specified in a rule. r316810 aligns ipfilter with
882 documentation in man pages separating keep frags from keep state.
883 This allows keep state to be specified without forcing keep frags
884 and allows keep frags to be specified independently of keep state.
885 To maintain previous behaviour, also specify keep frags with
886 keep state (as documented in ipf.conf.5).
889 arm64 builds now use the base system LLD 4.0.0 linker by default,
890 instead of requiring that the aarch64-binutils port or package be
891 installed. To continue using aarch64-binutils, set
892 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
895 The UDP optimization in entry 20160818 that added the sysctl
896 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
897 packets will no longer be treated as L3 broadcast packets.
900 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
901 use any explicitly assigned loopback address available in the jail
902 instead of using the first assigned address of the jail.
905 The ctl.ko module no longer implements the iSCSI target frontend:
906 cfiscsi.ko does instead.
908 If building cfiscsi.ko as a kernel module, the module can be loaded
909 via one of the following methods:
910 - `cfiscsi_load="YES"` in loader.conf(5).
911 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
912 - ctladm(8)/ctld(8), when compiled with iSCSI support
913 (`WITH_ISCSI=yes` in src.conf(5))
915 Please see cfiscsi(4) for more details.
918 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
919 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
920 same source (previously, the dependency of mmcsd.ko on mmc.ko was
921 missing, but mmcsd.ko now will refuse to load if it is incompatible
925 The syntax of ipfw(8) named states was changed to avoid ambiguity.
926 If you have used named states in the firewall rules, you need to modify
927 them after installworld and before rebooting. Now named states must
928 be prefixed with colon.
931 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
932 removed as the userland we provide cannot use them. The KMS version
933 (sys/dev/drm2) supports the same hardware.
936 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
937 Please see the 20141231 entry below for information about prerequisites
938 and upgrading, if you are not already using clang 3.5.0 or higher.
941 The code that provides support for ZFS .zfs/ directory functionality
942 has been reimplemented. It's not possible now to create a snapshot
943 by mkdir under .zfs/snapshot/. That should be the only user visible
947 EISA bus support has been removed. The WITH_EISA option is no longer
951 MCA bus support has been removed.
954 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
955 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
958 The EM_MULTIQUEUE kernel configuration option is deprecated now that
959 the em(4) driver conforms to iflib specifications.
962 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
963 IFLIB. If you have a custom kernel configuration that excludes em(4)
964 but you use igb(4), you need to re-add em(4) to your custom configuration.
967 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
968 Please see the 20141231 entry below for information about prerequisites
969 and upgrading, if you are not already using clang 3.5.0 or higher.
972 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
973 Please see the 20141231 entry below for information about prerequisites
974 and upgrading, if you are not already using clang 3.5.0 or higher.
977 The layout of the pmap structure has changed for powerpc to put the pmap
978 statistics at the front for all CPU variations. libkvm(3) and all tools
979 that link against it need to be recompiled.
982 isl(4) and cyapa(4) drivers now require a new driver,
983 chromebook_platform(4), to work properly on Chromebook-class hardware.
984 On other types of hardware the drivers may need to be configured using
985 device hints. Please see the corresponding manual pages for details.
988 The urtwn(4) driver was merged into rtwn(4) and now consists of
989 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
991 Also, firmware for RTL8188CE was renamed due to possible name
992 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
995 GNU rcs has been removed from base. It is available as packages:
996 - rcs: Latest GPLv3 GNU rcs version.
997 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1001 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1002 modules now requires that the kernel configuration contain the
1003 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1006 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1007 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1010 Relocatable object files with the extension of .So have been renamed
1011 to use an extension of .pico instead. The purpose of this change is
1012 to avoid a name clash with shared libraries on case-insensitive file
1013 systems. On those file systems, foo.So is the same file as foo.so.
1016 GNU rcs has been turned off by default. It can (temporarily) be built
1017 again by adding WITH_RCS knob in src.conf.
1018 Otherwise, GNU rcs is available from packages:
1019 - rcs: Latest GPLv3 GNU rcs version.
1020 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1023 The backup_uses_rcs functionality has been removed from rc.subr.
1026 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1027 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1028 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1029 QUEUE_MACRO_DEBUG behavior.
1032 r304787 changed some ioctl interfaces between the iSCSI userspace
1033 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1034 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1038 The UDP receive code has been updated to only treat incoming UDP
1039 packets that were addressed to an L2 broadcast address as L3
1040 broadcast packets. It is not expected that this will affect any
1041 standards-conforming UDP application. The new behaviour can be
1042 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1046 Remove the openbsd_poll system call.
1047 __FreeBSD_version has been bumped because of this.
1050 The stable/11 branch has been created from head@r302406.
1053 The libc stub for the pipe(2) system call has been replaced with
1054 a wrapper that calls the pipe2(2) system call and the pipe(2)
1055 system call is now only implemented by the kernels that include
1056 "options COMPAT_FREEBSD10" in their config file (this is the
1057 default). Users should ensure that this option is enabled in
1058 their kernel or upgrade userspace to r302092 before upgrading their
1062 CAM will now strip leading spaces from SCSI disks' serial numbers.
1063 This will affect users who create UFS filesystems on SCSI disks using
1064 those disk's diskid device nodes. For example, if /etc/fstab
1065 previously contained a line like
1066 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1067 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1068 transforms like gmirror may also be affected. ZFS users should
1072 The bitstring(3) API has been updated with new functionality and
1073 improved performance. But it is binary-incompatible with the old API.
1074 Objects built with the new headers may not be linked against objects
1075 built with the old headers.
1078 The brk and sbrk functions have been removed from libc on arm64.
1079 Binutils from ports has been updated to not link to these
1080 functions and should be updated to the latest version before
1081 installing a new libc.
1084 The armv6 port now defaults to hard float ABI. Limited support
1085 for running both hardfloat and soft float on the same system
1086 is available using the libraries installed with -DWITH_LIBSOFT.
1087 This has only been tested as an upgrade path for installworld
1088 and packages may fail or need manual intervention to run. New
1089 packages will be needed.
1091 To update an existing self-hosted armv6hf system, you must add
1092 TARGET_ARCH=armv6 on the make command line for both the build
1093 and the install steps.
1096 Kernel modules compiled outside of a kernel build now default to
1097 installing to /boot/modules instead of /boot/kernel. Many kernel
1098 modules built this way (such as those in ports) already overrode
1099 KMODDIR explicitly to install into /boot/modules. However,
1100 manually building and installing a module from /sys/modules will
1101 now install to /boot/modules instead of /boot/kernel.
1104 The CAM I/O scheduler has been committed to the kernel. There should be
1105 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1106 list of known rogues that claim support for this but actually corrupt
1107 data is believed to be complete, be on the lookout for data
1108 corruption. The known rogue list is believed to be complete:
1110 o Crucial MX100, M550 drives with MU01 firmware.
1111 o Micron M510 and M550 drives with MU01 firmware.
1112 o Micron M500 prior to MU07 firmware
1113 o Samsung 830, 840, and 850 all firmwares
1114 o FCCT M500 all firmwares
1116 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1117 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1118 updated firmware. Black listed drives will work correctly because these
1119 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1120 this list is the same as found in Linux, it's believed there are no
1121 other rogues in the market place. All other models from the above
1124 To be safe, if you are at all concerned, you can quirk each of your
1125 drives to prevent NCQ from being sent by setting:
1126 kern.cam.ada.X.quirks="0x2"
1127 in loader.conf. If the drive requires the 4k sector quirk, set the
1128 quirks entry to 0x3.
1131 The FAST_DEPEND build option has been removed and its functionality is
1132 now the one true way. The old mkdep(1) style of 'make depend' has
1133 been removed. See 20160311 for further details.
1136 Resource range types have grown from unsigned long to uintmax_t. All
1137 drivers, and anything using libdevinfo, need to be recompiled.
1140 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1141 builds. It no longer runs mkdep(1) during 'make depend', and the
1142 'make depend' stage can safely be skipped now as it is auto ran
1143 when building 'make all' and will generate all SRCS and DPSRCS before
1144 building anything else. Dependencies are gathered at compile time with
1145 -MF flags kept in separate .depend files per object file. Users should
1146 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1147 stale .depend files.
1150 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1151 kernel modules. Therefore, if you load any kernel modules at boot time,
1152 please install the boot loaders after you install the kernel, but before
1156 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1157 make installkernel KERNCONF=YOUR_KERNEL_HERE
1158 make -C sys/boot install
1159 <reboot in single user>
1161 Then follow the usual steps, described in the General Notes section,
1165 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1166 see the 20141231 entry below for information about prerequisites and
1167 upgrading, if you are not already using clang 3.5.0 or higher.
1170 The AIO subsystem is now a standard part of the kernel. The
1171 VFS_AIO kernel option and aio.ko kernel module have been removed.
1172 Due to stability concerns, asynchronous I/O requests are only
1173 permitted on sockets and raw disks by default. To enable
1174 asynchronous I/O requests on all file types, set the
1175 vfs.aio.enable_unsafe sysctl to a non-zero value.
1178 The ELF object manipulation tool objcopy is now provided by the
1179 ELF Tool Chain project rather than by GNU binutils. It should be a
1180 drop-in replacement, with the addition of arm64 support. The
1181 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1182 to obtain the GNU version if necessary.
1185 Building ZFS pools on top of zvols is prohibited by default. That
1186 feature has never worked safely; it's always been prone to deadlocks.
1187 Using a zvol as the backing store for a VM guest's virtual disk will
1188 still work, even if the guest is using ZFS. Legacy behavior can be
1189 restored by setting vfs.zfs.vol.recursive=1.
1192 The NONE and HPN patches has been removed from OpenSSH. They are
1193 still available in the security/openssh-portable port.
1196 With the addition of ypldap(8), a new _ypldap user is now required
1197 during installworld. "mergemaster -p" can be used to add the user
1198 prior to installworld, as documented in the handbook.
1201 The tftp loader (pxeboot) now uses the option root-path directive. As a
1202 consequence it no longer looks for a pxeboot.4th file on the tftp
1203 server. Instead it uses the regular /boot infrastructure as with the
1207 The code to start recording plug and play data into the modules has
1208 been committed. While the old tools will properly build a new kernel,
1209 a number of warnings about "unknown metadata record 4" will be produced
1210 for an older kldxref. To avoid such warnings, make sure to rebuild
1211 the kernel toolchain (or world). Make sure that you have r292078 or
1212 later when trying to build 292077 or later before rebuilding.
1215 Debug data files are now built by default with 'make buildworld' and
1216 installed with 'make installworld'. This facilitates debugging but
1217 requires more disk space both during the build and for the installed
1218 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1222 r291527 changed the internal interface between the nfsd.ko and
1223 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1224 __FreeBSD_version has been bumped because of this.
1227 Add support for unicode collation strings leads to a change of
1228 order of files listed by ls(1) for example. To get back to the old
1229 behaviour, set LC_COLLATE environment variable to "C".
1231 Databases administrators will need to reindex their databases given
1232 collation results will be different.
1234 Due to a bug in install(1) it is recommended to remove the ancient
1235 locales before running make installworld.
1237 rm -rf /usr/share/locale/*
1240 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1241 libcrypto.so.7 or libssl.so.7 must be recompiled.
1244 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1245 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1246 should be replaced with isp_2400 and isp_2500 modules respectively.
1249 The build previously allowed using 'make -n' to not recurse into
1250 sub-directories while showing what commands would be executed, and
1251 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1252 and 'make -N' will not.
1255 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1256 and etcupdate will now use this file. A custom sendmail.cf is now
1257 updated via this mechanism rather than via installworld. If you had
1258 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1259 want to remove the exclusion or change it to "always install".
1260 /etc/mail/sendmail.cf is now managed the same way regardless of
1261 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1262 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1265 Compatibility shims for legacy ATA device names have been removed.
1266 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1267 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1268 environment variables, /dev/ad* and /dev/ar* symbolic links.
1271 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1272 Please see the 20141231 entry below for information about prerequisites
1273 and upgrading, if you are not already using clang 3.5.0 or higher.
1276 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1277 and renamed from .symbols to .debug. This reduces the size requirements
1278 on the boot partition or file system and provides consistency with
1279 userland debug files.
1281 When using the supported kernel installation method the
1282 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1283 as is done with /boot/kernel.
1285 Developers wishing to maintain the historical behavior of installing
1286 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1289 The wireless drivers had undergone changes that remove the 'parent
1290 interface' from the ifconfig -l output. The rc.d network scripts
1291 used to check presence of a parent interface in the list, so old
1292 scripts would fail to start wireless networking. Thus, etcupdate(3)
1293 or mergemaster(8) run is required after kernel update, to update your
1294 rc.d scripts in /etc.
1297 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1298 These configurations are now automatically interpreted as
1299 'scrub fragment reassemble'.
1302 Kernel-loadable modules for the random(4) device are back. To use
1303 them, the kernel must have
1306 options RANDOM_LOADABLE
1308 kldload(8) can then be used to load random_fortuna.ko
1309 or random_yarrow.ko. Please note that due to the indirect
1310 function calls that the loadable modules need to provide,
1311 the build-in variants will be slightly more efficient.
1313 The random(4) kernel option RANDOM_DUMMY has been retired due to
1314 unpopularity. It was not all that useful anyway.
1317 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1318 Control over building the ELF Tool Chain tools is now provided by
1319 the WITHOUT_TOOLCHAIN knob.
1322 The polarity of Pulse Per Second (PPS) capture events with the
1323 uart(4) driver has been corrected. Prior to this change the PPS
1324 "assert" event corresponded to the trailing edge of a positive PPS
1325 pulse and the "clear" event was the leading edge of the next pulse.
1327 As the width of a PPS pulse in a typical GPS receiver is on the
1328 order of 1 millisecond, most users will not notice any significant
1329 difference with this change.
1331 Anyone who has compensated for the historical polarity reversal by
1332 configuring a negative offset equal to the pulse width will need to
1333 remove that workaround.
1336 The default group assigned to /dev/dri entries has been changed
1337 from 'wheel' to 'video' with the id of '44'. If you want to have
1338 access to the dri devices please add yourself to the video group
1341 # pw groupmod video -m $USER
1344 The menu.rc and loader.rc files will now be replaced during
1345 upgrades. Please migrate local changes to menu.rc.local and
1346 loader.rc.local instead.
1349 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1350 strings and strip have been removed. The src.conf(5) knob
1351 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1354 As ZFS requires more kernel stack pages than is the default on some
1355 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1356 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1358 Please consider using 'options KSTACK_PAGES=X' where X is greater
1359 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1362 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1363 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1364 default, i.e., they will not contain "::". For example, instead
1365 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1366 to have a more specific match, such as different map entries for
1367 IPv6:0:0 vs IPv6:0. This change requires that configuration
1368 data (including maps, files, classes, custom ruleset, etc.) must
1369 use the same format, so make certain such configuration data is
1370 upgrading. As a very simple check search for patterns like
1371 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1372 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1373 the cf option UseCompressedIPv6Addresses.
1376 The default kernel entropy-processing algorithm is now
1377 Fortuna, replacing Yarrow.
1379 Assuming you have 'device random' in your kernel config
1380 file, the configurations allow a kernel option to override
1381 this default. You may choose *ONE* of:
1383 options RANDOM_YARROW # Legacy /dev/random algorithm.
1384 options RANDOM_DUMMY # Blocking-only driver.
1386 If you have neither, you get Fortuna. For most people,
1387 read no further, Fortuna will give a /dev/random that works
1388 like it always used to, and the difference will be irrelevant.
1390 If you remove 'device random', you get *NO* kernel-processed
1391 entropy at all. This may be acceptable to folks building
1392 embedded systems, but has complications. Carry on reading,
1393 and it is assumed you know what you need.
1395 *PLEASE* read random(4) and random(9) if you are in the
1396 habit of tweaking kernel configs, and/or if you are a member
1397 of the embedded community, wanting specific and not-usual
1398 behaviour from your security subsystems.
1400 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1401 random', you will NOT have a functioning /dev/random, and
1402 many cryptographic features will not work, including SSH.
1403 You may also find strange behaviour from the random(3) set
1404 of library functions, in particular sranddev(3), srandomdev(3)
1405 and arc4random(3). The reason for this is that the KERN_ARND
1406 sysctl only returns entropy if it thinks it has some to
1407 share, and with RANDOM_DUMMY or no 'device random' this
1411 An additional fix for the issue described in the 20150614 sendmail
1412 entry below has been committed in revision 284717.
1415 FreeBSD's old make (fmake) has been removed from the system. It is
1416 available as the devel/fmake port or via pkg install fmake.
1419 The fix for the issue described in the 20150614 sendmail entry
1420 below has been committed in revision 284436. The work
1421 around described in that entry is no longer needed unless the
1422 default setting is overridden by a confDH_PARAMETERS configuration
1423 setting of '5' or pointing to a 512 bit DH parameter file.
1426 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1427 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1428 and devel/kyua to version 0.20+ and adjust any calling code to work
1429 with Kyuafile and kyua.
1432 The import of openssl to address the FreeBSD-SA-15:10.openssl
1433 security advisory includes a change which rejects handshakes
1434 with DH parameters below 768 bits. sendmail releases prior
1435 to 8.15.2 (not yet released), defaulted to a 512 bit
1436 DH parameter setting for client connections. To work around
1437 this interoperability, sendmail can be configured to use a
1438 2048 bit DH parameter by:
1440 1. Edit /etc/mail/`hostname`.mc
1441 2. If a setting for confDH_PARAMETERS does not exist or
1442 exists and is set to a string beginning with '5',
1443 replace it with '2'.
1444 3. If a setting for confDH_PARAMETERS exists and is set to
1445 a file path, create a new file with:
1446 openssl dhparam -out /path/to/file 2048
1447 4. Rebuild the .cf file:
1448 cd /etc/mail/; make; make install
1449 5. Restart sendmail:
1450 cd /etc/mail/; make restart
1452 A sendmail patch is coming, at which time this file will be
1456 Generation of legacy formatted entries have been disabled by default
1457 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1458 entries were converted to use the new format by default when the new,
1459 machine independent format have been added and supported since FreeBSD
1462 Please see the pwd_mkdb(8) manual page for further details.
1465 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1466 20141231 entry below for information about prerequisites and upgrading,
1467 if you are not already using 3.5.0 or higher.
1470 TI platform code switched to using vendor DTS files and this update
1471 may break existing systems running on Beaglebone, Beaglebone Black,
1474 - dtb files should be regenerated/reinstalled. Filenames are the
1475 same but content is different now
1476 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1477 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1478 addressing scheme is now pin 25 on /dev/gpioc3.
1479 - Pandaboard: /etc/ttys should be updated, serial console device is
1480 now /dev/ttyu2, not /dev/ttyu0
1483 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1484 If you need the GNU extension from groff soelim(1), install groff
1485 from package: pkg install groff, or via ports: textproc/groff.
1488 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1489 defined in symlink(7); previously symlinks were silently ignored.
1492 The const qualifier has been removed from iconv(3) to comply with
1493 POSIX. The ports tree is aware of this from r384038 onwards.
1496 Libraries specified by LIBADD in Makefiles must have a corresponding
1497 DPADD_<lib> variable to ensure correct dependencies. This is now
1498 enforced in src.libnames.mk.
1501 From legacy ata(4) driver was removed support for SATA controllers
1502 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1503 Kernel modules ataahci and ataadaptec were removed completely,
1504 replaced by ahci and mvs modules respectively.
1507 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1508 the 20141231 entry below for information about prerequisites and
1509 upgrading, if you are not already using 3.5.0 or higher.
1512 The 32-bit PowerPC kernel has been changed to a position-independent
1513 executable. This can only be booted with a version of loader(8)
1514 newer than January 31, 2015, so make sure to update both world and
1515 kernel before rebooting.
1518 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1519 but before r278950, the RNG was not seeded properly. Immediately
1520 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1521 ssh keys or openssl keys) that were generated w/ a kernel from that
1522 range. This does not affect programs that directly used /dev/random
1523 or /dev/urandom. All userland uses of arc4random(3) are affected.
1526 The autofs(4) ABI was changed in order to restore binary compatibility
1527 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1528 with the new kernel.
1531 The powerpc64 kernel has been changed to a position-independent
1532 executable. This can only be booted with a new version of loader(8),
1533 so make sure to update both world and kernel before rebooting.
1536 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1537 only release, no new features have been added. Please see the 20141231
1538 entry below for information about prerequisites and upgrading, if you
1539 are not already using 3.5.0.
1542 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1543 taken from the ELF Tool Chain project rather than GNU binutils. They
1544 should be drop-in replacements, with the addition of arm64 support.
1545 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1546 binutils tools, if necessary. See 20150805 for updated information.
1549 The default Unbound configuration now enables remote control
1550 using a local socket. Users who have already enabled the
1551 local_unbound service should regenerate their configuration
1552 by running "service local_unbound setup" as root.
1555 The GNU texinfo and GNU info pages have been removed.
1556 To be able to view GNU info pages please install texinfo from ports.
1559 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1561 As of this release, a prerequisite for building clang, llvm and lldb is
1562 a C++11 capable compiler and C++11 standard library. This means that to
1563 be able to successfully build the cross-tools stage of buildworld, with
1564 clang as the bootstrap compiler, your system compiler or cross compiler
1565 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1566 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1569 On any standard FreeBSD 10.x or 11.x installation, where clang and
1570 libc++ are on by default (that is, on x86 or arm), this should work out
1573 On 9.x installations where clang is enabled by default, e.g. on x86 and
1574 powerpc, libc++ will not be enabled by default, so libc++ should be
1575 built (with clang) and installed first. If both clang and libc++ are
1576 missing, build clang first, then use it to build libc++.
1578 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1579 the instructions for 9.x above.
1581 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1582 default, and do not build clang.
1584 Many embedded systems are resource constrained, and will not be able to
1585 build clang in a reasonable time, or in some cases at all. In those
1586 cases, cross building bootable systems on amd64 is a workaround.
1588 This new version of clang introduces a number of new warnings, of which
1589 the following are most likely to appear:
1593 This warns in two cases, for both C and C++:
1594 * When the code is trying to take the absolute value of an unsigned
1595 quantity, which is effectively a no-op, and almost never what was
1596 intended. The code should be fixed, if at all possible. If you are
1597 sure that the unsigned quantity can be safely cast to signed, without
1598 loss of information or undefined behavior, you can add an explicit
1599 cast, or disable the warning.
1601 * When the code is trying to take an absolute value, but the called
1602 abs() variant is for the wrong type, which can lead to truncation.
1603 If you want to disable the warning instead of fixing the code, please
1604 make sure that truncation will not occur, or it might lead to unwanted
1607 -Wtautological-undefined-compare and
1608 -Wundefined-bool-conversion
1610 These warn when C++ code is trying to compare 'this' against NULL, while
1611 'this' should never be NULL in well-defined C++ code. However, there is
1612 some legacy (pre C++11) code out there, which actively abuses this
1613 feature, which was less strictly defined in previous C++ versions.
1615 Squid and openjdk do this, for example. The warning can be turned off
1616 for C++98 and earlier, but compiling the code in C++11 mode might result
1617 in unexpected behavior; for example, the parts of the program that are
1618 unreachable could be optimized away.
1621 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1622 kernel sources have been removed. The .h files remain, since some
1623 utilities include them. This will need to be fixed later.
1624 If "mount -t oldnfs ..." is attempted, it will fail.
1625 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1626 the utilities will report errors.
1629 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1630 directories to top level SUBDIR variable when their parent
1631 directory is included in LOCAL_DIRS. Users with build systems with
1632 such hierarchies and without SUBDIR entries in the parent
1633 directory Makefiles should add them or add the directories to
1637 faith(4) and faithd(8) have been removed from the base system. Faith
1638 has been obsolete for a very long time.
1641 vt(4), the new console driver, is enabled by default. It brings
1642 support for Unicode and double-width characters, as well as
1643 support for UEFI and integration with the KMS kernel video
1646 You may need to update your console settings in /etc/rc.conf,
1647 most probably the keymap. During boot, /etc/rc.d/syscons will
1648 indicate what you need to do.
1650 vt(4) still has issues and lacks some features compared to
1651 syscons(4). See the wiki for up-to-date information:
1652 https://wiki.freebsd.org/Newcons
1654 If you want to keep using syscons(4), you can do so by adding
1655 the following line to /boot/loader.conf:
1659 pjdfstest has been integrated into kyua as an opt-in test suite.
1660 Please see share/doc/pjdfstest/README for more details on how to
1664 gperf has been removed from the base system for architectures
1665 that use clang. Ports that require gperf will obtain it from the
1669 pjdfstest has been moved from tools/regression/pjdfstest to
1673 At svn r271982, The default linux compat kernel ABI has been adjusted
1674 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1675 update. If you wish to continue using the linux-f10 compat ports,
1676 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1677 encouraged to update their linux-compat packages to linux-c6 during
1678 their next update cycle.
1681 The ofwfb driver, used to provide a graphics console on PowerPC when
1682 using vt(4), no longer allows mmap() of all physical memory. This
1683 will prevent Xorg on PowerPC with some ATI graphics cards from
1684 initializing properly unless x11-servers/xorg-server is updated to
1688 The xdev targets have been converted to using TARGET and
1689 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1692 The default unbound configuration has been modified to address
1693 issues with reverse lookups on networks that use private
1694 address ranges. If you use the local_unbound service, run
1695 "service local_unbound setup" as root to regenerate your
1696 configuration, then "service local_unbound reload" to load the
1700 The GNU texinfo and GNU info pages are not built and installed
1701 anymore, WITH_INFO knob has been added to allow to built and install
1703 UPDATE: see 20150102 entry on texinfo's removal
1706 The GNU readline library is now an INTERNALLIB - that is, it is
1707 statically linked into consumers (GDB and variants) in the base
1708 system, and the shared library is no longer installed. The
1709 devel/readline port is available for third party software that
1713 The Itanium architecture (ia64) has been removed from the list of
1714 known architectures. This is the first step in the removal of the
1718 Commit r268115 has added NFSv4.1 server support, merged from
1719 projects/nfsv4.1-server. Since this includes changes to the
1720 internal interfaces between the NFS related modules, a full
1721 build of the kernel and modules will be necessary.
1722 __FreeBSD_version has been bumped.
1725 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1726 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1727 which differs from the behaviour controlled by this knob.)
1730 Maximal length of the serial number in CTL was increased from 16 to
1731 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1732 and ctld, need to be rebuilt to work with a new kernel.
1735 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1736 1 respectively to match the upstream numbers. They were out of
1737 sync because, when they were originally added to FreeBSD, the
1738 upstream versions were not respected. These libraries are private
1739 and not yet built by default, so renumbering them should be a
1740 non-issue. However, unclean source trees will yield broken test
1741 programs once the operator executes "make delete-old-libs" after a
1742 "make installworld".
1744 Additionally, the atf-sh binary was made private by moving it into
1745 /usr/libexec/. Already-built shell test programs will keep the
1746 path to the old binary so they will break after "make delete-old"
1749 If you are using WITH_TESTS=yes (not the default), wipe the object
1750 tree and rebuild from scratch to prevent spurious test failures.
1751 This is only needed once: the misnumbered libraries and misplaced
1752 binaries have been added to OptionalObsoleteFiles.inc so they will
1753 be removed during a clean upgrade.
1756 Clang and llvm have been upgraded to 3.4.1 release.
1759 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1760 be removed to avoid issues in the future (and has been added to
1764 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1765 past, it affected all builds that used the bsd.*.mk files. The old
1766 behavior was a bug, but people may have relied upon it. To get this
1767 behavior back, you can .include /etc/src.conf from /etc/make.conf
1768 (which is still global and isn't changed). This also changes the
1769 behavior of incremental builds inside the tree of individual
1770 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1771 Although this has survived make universe and some upgrade scenarios,
1772 other upgrade scenarios may have broken. At least one form of
1773 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1774 as well... In cases where MAKESYSPATH isn't working with this
1775 setting, you'll need to set it to the full path to your tree.
1777 One side effect of all this cleaning up is that bsd.compiler.mk
1778 is no longer implicitly included by bsd.own.mk. If you wish to
1779 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1783 The lindev device has been removed since /dev/full has been made a
1784 standard device. __FreeBSD_version has been bumped.
1787 The knob WITHOUT_VI was added to the base system, which controls
1788 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1789 in order to reorder files share/termcap and didn't build ex(1) as a
1790 build tool, so building/installing with WITH_VI is highly advised for
1791 build hosts for older releases.
1793 This issue has been fixed in stable/9 and stable/10 in r277022 and
1794 r276991, respectively.
1797 The YES_HESIOD knob has been removed. It has been obsolete for
1798 a decade. Please move to using WITH_HESIOD instead or your builds
1799 will silently lack HESIOD.
1802 The uart(4) driver has been changed with respect to its handling
1803 of the low-level console. Previously the uart(4) driver prevented
1804 any process from changing the baudrate or the CLOCAL and HUPCL
1805 control flags. By removing the restrictions, operators can make
1806 changes to the serial console port without having to reboot.
1807 However, when getty(8) is started on the serial device that is
1808 associated with the low-level console, a misconfigured terminal
1809 line in /etc/ttys will now have a real impact.
1810 Before upgrading the kernel, make sure that /etc/ttys has the
1811 serial console device configured as 3wire without baudrate to
1812 preserve the previous behaviour. E.g:
1813 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1816 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1817 to improve performance. To re-enable it, if needed, run rpcbind
1818 with command line option -W.
1821 Switched back to the GPL dtc compiler due to updates in the upstream
1822 dts files not being supported by the BSDL dtc compiler. You will need
1823 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1824 may result while building dtb files during a kernel build if you fail
1825 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1828 Clang and llvm have been upgraded to 3.4 release.
1831 The nve(4) driver has been removed. Please use the nfe(4) driver
1832 for NVIDIA nForce MCP Ethernet adapters instead.
1835 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1836 This could cause certain C++ applications using shared libraries built
1837 against the previous version of libc++ to crash. The incompatibility
1838 has now been fixed, but any C++ applications or shared libraries built
1839 between r261283 and r261801 should be recompiled.
1842 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1843 capability mode support. Please note that enabling the feature in
1844 kernel is still highly recommended.
1847 OpenSSH is now built with sandbox support, and will use sandbox as
1848 the default privilege separation method. This requires Capsicum
1849 capability mode support in kernel.
1852 The libelf and libdwarf libraries have been updated to newer
1853 versions from upstream. Shared library version numbers for
1854 these two libraries were bumped. Any ports or binaries
1855 requiring these two libraries should be recompiled.
1856 __FreeBSD_version is bumped to 1100006.
1859 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1860 instead of providing an explicit one, this would prevent such
1861 Makefile from providing its own Kyuafile in the future during
1862 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1863 intervention is needed to clean an objdir if you use NO_CLEAN:
1864 # find /usr/obj -name Kyuafile | xargs rm -f
1867 The behavior of gss_pseudo_random() for the krb5 mechanism
1868 has changed, for applications requesting a longer random string
1869 than produced by the underlying enctype's pseudo-random() function.
1870 In particular, the random string produced from a session key of
1871 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1872 be different at the 17th octet and later, after this change.
1873 The counter used in the PRF+ construction is now encoded as a
1874 big-endian integer in accordance with RFC 4402.
1875 __FreeBSD_version is bumped to 1100004.
1878 The WITHOUT_ATF build knob has been removed and its functionality
1879 has been subsumed into the more generic WITHOUT_TESTS. If you were
1880 using the former to disable the build of the ATF libraries, you
1881 should change your settings to use the latter.
1884 The default version of mtree is nmtree which is obtained from
1885 NetBSD. The output is generally the same, but may vary
1886 slightly. If you found you need identical output adding
1887 "-F freebsd9" to the command line should do the trick. For the
1888 time being, the old mtree is available as fmtree.
1891 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1892 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1893 1.1.4_8 and verify bsdyml not linked in, before running "make
1895 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1897 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1900 The stable/10 branch has been created in subversion from head
1907 Avoid using make -j when upgrading. While generally safe, there are
1908 sometimes problems using -j to upgrade. If your upgrade fails with
1909 -j, please try again without -j. From time to time in the past there
1910 have been problems using -j with buildworld and/or installworld. This
1911 is especially true when upgrading between "distant" versions (eg one
1912 that cross a major release boundary or several minor releases, or when
1913 several months have passed on the -current branch).
1915 Sometimes, obscure build problems are the result of environment
1916 poisoning. This can happen because the make utility reads its
1917 environment when searching for values for global variables. To run
1918 your build attempts in an "environmental clean room", prefix all make
1919 commands with 'env -i '. See the env(1) manual page for more details.
1921 When upgrading from one major version to another it is generally best to
1922 upgrade to the latest code in the currently installed branch first, then
1923 do an upgrade to the new branch. This is the best-tested upgrade path,
1924 and has the highest probability of being successful. Please try this
1925 approach if you encounter problems with a major version upgrade. Since
1926 the stable 4.x branch point, one has generally been able to upgrade from
1927 anywhere in the most recent stable branch to head / current (or even the
1928 last couple of stable branches). See the top of this file when there's
1931 When upgrading a live system, having a root shell around before
1932 installing anything can help undo problems. Not having a root shell
1933 around can lead to problems if pam has changed too much from your
1934 starting point to allow continued authentication after the upgrade.
1936 This file should be read as a log of events. When a later event changes
1937 information of a prior event, the prior event should not be deleted.
1938 Instead, a pointer to the entry with the new information should be
1939 placed in the old entry. Readers of this file should also sanity check
1940 older entries before relying on them blindly. Authors of new entries
1941 should write them with this in mind.
1945 When upgrading the boot ZFS pool to a new version, always follow
1948 1.) recompile and reinstall the ZFS boot loader and boot block
1949 (this is part of "make buildworld" and "make installworld")
1951 2.) update the ZFS boot block on your boot drive
1953 The following example updates the ZFS boot block on the first
1954 partition (freebsd-boot) of a GPT partitioned drive ada0:
1955 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1957 Non-boot pools do not need these updates.
1961 If you are updating from a prior version of FreeBSD (even one just
1962 a few days old), you should follow this procedure. It is the most
1963 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1965 make kernel-toolchain
1966 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1967 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1969 To test a kernel once
1970 ---------------------
1971 If you just want to boot a kernel once (because you are not sure
1972 if it works, or if you want to boot a known bad kernel to provide
1973 debugging information) run
1974 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1975 nextboot -k testkernel
1977 To rebuild everything and install it on the current system.
1978 -----------------------------------------------------------
1979 # Note: sometimes if you are running current you gotta do more than
1980 # is listed here if you are upgrading from a really old current.
1982 <make sure you have good level 0 dumps>
1984 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1985 make installkernel KERNCONF=YOUR_KERNEL_HERE
1987 <reboot in single user> [3]
1994 To cross-install current onto a separate partition
1995 --------------------------------------------------
1996 # In this approach we use a separate partition to hold
1997 # current's root, 'usr', and 'var' directories. A partition
1998 # holding "/", "/usr" and "/var" should be about 2GB in
2001 <make sure you have good level 0 dumps>
2004 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2005 <maybe newfs current's root partition>
2006 <mount current's root partition on directory ${CURRENT_ROOT}>
2007 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2008 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2009 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2010 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2011 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2012 <reboot into current>
2013 <do a "native" rebuild/install as described in the previous section>
2014 <maybe install compatibility libraries from ports/misc/compat*>
2018 To upgrade in-place from stable to current
2019 ----------------------------------------------
2020 <make sure you have good level 0 dumps>
2022 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2023 make installkernel KERNCONF=YOUR_KERNEL_HERE
2025 <reboot in single user> [3]
2032 Make sure that you've read the UPDATING file to understand the
2033 tweaks to various things you need. At this point in the life
2034 cycle of current, things change often and you are on your own
2035 to cope. The defaults can also change, so please read ALL of
2036 the UPDATING entries.
2038 Also, if you are tracking -current, you must be subscribed to
2039 freebsd-current@freebsd.org. Make sure that before you update
2040 your sources that you have read and understood all the recent
2041 messages there. If in doubt, please track -stable which has
2042 much fewer pitfalls.
2044 [1] If you have third party modules, such as vmware, you
2045 should disable them at this point so they don't crash your
2048 [3] From the bootblocks, boot -s, and then do
2053 adjkerntz -i # if CMOS is wall time
2054 Also, when doing a major release upgrade, it is required that
2055 you boot into single user mode to do the installworld.
2057 [4] Note: This step is non-optional. Failure to do this step
2058 can result in a significant reduction in the functionality of the
2059 system. Attempting to do it by hand is not recommended and those
2060 that pursue this avenue should read this file carefully, as well
2061 as the archives of freebsd-current and freebsd-hackers mailing lists
2062 for potential gotchas. The -U option is also useful to consider.
2063 See mergemaster(8) for more information.
2065 [5] Usually this step is a no-op. However, from time to time
2066 you may need to do this if you get unknown user in the following
2067 step. It never hurts to do it all the time. You may need to
2068 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2069 install) after the buildworld before this step if you last updated
2070 from current before 20130425 or from -stable before 20130430.
2072 [6] This only deletes old files and directories. Old libraries
2073 can be deleted by "make delete-old-libs", but you have to make
2074 sure that no program is using those libraries anymore.
2076 [8] The new kernel must be able to run existing binaries used by
2077 an installworld. When upgrading across major versions, the new
2078 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2079 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2080 binaries). Failure to do so may leave you with a system that is
2081 hard to boot to recover. A GENERIC kernel will include suitable
2082 compatibility options to run binaries from older branches.
2084 Make sure that you merge any new devices from GENERIC since the
2085 last time you updated your kernel config file.
2087 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2088 "?=" instead of the "=" assignment operator, so that buildworld can
2089 override the CPUTYPE if it needs to.
2091 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2092 not on the command line, or in /etc/make.conf. buildworld will
2093 warn if it is improperly defined.
2096 This file contains a list, in reverse chronological order, of major
2097 breakages in tracking -current. It is not guaranteed to be a complete
2098 list of such breakages, and only contains entries since September 23, 2011.
2099 If you need to see UPDATING entries from before that date, you will need
2100 to fetch an UPDATING file from an older FreeBSD release.
2102 Copyright information:
2104 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2106 Redistribution, publication, translation and use, with or without
2107 modification, in full or in part, in any form or format of this
2108 document are permitted without further permission from the author.
2110 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2111 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2112 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2113 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2114 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2115 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2116 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2117 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2118 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2119 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2120 POSSIBILITY OF SUCH DAMAGE.
2122 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob