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