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-p5 FreeBSD-SA-22:04.netmap
22 FreeBSD-SA-22:05.bhyve
23 FreeBSD-SA-22:06.ioctl
24 FreeBSD-SA-22:07.wifi_meshid
27 Potential jail escape vulnerabilities in netmap [SA-22:04.netmap]
29 Bhyve e82545 device emulation out-of-bounds write [SA-22:05.bhyve]
31 mpr/mps/mpt driver ioctl heap out-of-bounds write [SA-22:06.ioctl]
33 802.11 heap buffer overflow [SA-22:07.wifi_meshid]
35 zlib compression out-of-bounds write [SA-22:08.zlib]
38 12.3-RELEASE-p4 FreeBSD-EN-22:14.tzdata
40 Timezone database information update. [EN-22:14.tzdata]
43 12.3-RELEASE-p3 FreeBSD-EN-22:09.freebsd-update
45 FreeBSD-SA-22:03.openssl
47 freebsd-update creating erroneous boot environments [FreeBSD-EN-22:09.freebsd-update]
49 Multiple WiFi issues [FreeBSD-SA-22:02.wifi]
51 OpenSSL certificate parsing infinite loop [FreeBSD-SA-22:03.openssl]
54 12.3-RELEASE-p2 FreeBSD-EN-22:08.i386
56 Fix regression in i386 TLB invalidation logic. [FreeBSD-EN-22:08.i386]
59 12.3-RELEASE-p1 FreeBSD-EN-22:02.xsave
60 FreeBSD-EN-22:03.hyperv
62 FreeBSD-EN-22:06.libalias
65 Correct size of the amd64 SSE area in the xsave layout [FreeBSD-EN-22:02.xsave]
67 Prepopulate Hyper-V PCI device bars [FreeBSD-EN-22:03.hyperv]
69 Fix amd64 pmap PCID mode invalidations [FreeBSD-EN-22:04.pcid]
71 Fix fragmented UDP packets handling [FreeBSD-EN-22:06.libalias]
73 Fix vt console buffer overflow [FreeBSD-SA-22:01.vt]
79 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
80 As of be70c7a50d32 it is no longer used by userspace, but it does mean
81 users may not be able to enumerate pf states if they update the kernel
82 past c021ff986e2b without first updating userspace past be70c7a50d32.
85 The 20210707 awk update brought in a change in behavior. This has
86 been corrected as of d4d252c49976. Between these dates, if you
87 installed a new awk binary, you may not be able to build a new
88 kernel because the change in behavior affected the genoffset
89 script used to build the kernel. If you did update, the fix is
90 to update your sources past the above hash and do
93 % sudo -E make install
94 to enable building kernels again.
97 awk has been updated to the latest one-true-awk version 20210215.
98 This contains a number of minor bug fixes.
101 Commit 6ae32cc8182f changed the internal KAPI between the krpc and
102 nfsd modules. As such, both need to be rebuilt from sources.
103 Bump __FreeBSD_version to 1202508.
106 Commit e9959506d2cc changed the internal KAPI between the
107 nscl.ko and nfscommon.ko modules, so they both need to be
108 rebuilt from sources.
111 Commit 0a1fdb867c72 changed the internal KAPI between
112 the krpc and NFS. As such, the krpc, nfscommon and
113 nfscl modules must all be rebuilt from sources.
114 Without this patch, NFSv4.1 mounts should not
115 be done with the nfscbd(8) daemon running, to avoid
116 needing a working back channel for server->client RPCs.
119 The make.conf(5) MALLOC_PRODUCTION variable, used for disabling and
120 enabling assertions and statistics gathering in malloc(3), has been
121 migrated to a src.conf(5) WITH/WITHOUT_MALLOC_PRODUCTION option.
123 On stable branches, WITH_MALLOC_PRODUCTION is set by default, which
124 means that malloc(3) has assertions and statistics gathering disabled,
125 for improved performance.
127 For backwards compatibility, the make.conf(5) MALLOC_PRODUCTION is still
128 honored, but it is now deprecated and undocumented.
131 The resume code now notifies devd with the 'kernel' system
132 rather than the old 'kern' subsystem to be consistent with
133 other use. The old notification will be created as well, but
134 will be removed prior to FreeBSD 14.0.
137 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
138 been upgraded to 10.0.1. Please see the 20141231 entry below for
139 information about prerequisites and upgrading, if you are not already
140 using clang 3.5.0 or higher.
143 read(2) of a directory fd is now rejected by default. root may
144 re-enable it for the entire system with the
145 security.bsd.allow_read_dir sysctl(8) MIB.
147 It may be advised to setup aliases for grep to default to `-d skip` if
148 commonly non-recursively grepping a list that includes directories and
149 the potential for the resulting stderr output is not tolerable. Example
150 aliases are now installed, commented out, in /root/.cshrc.
153 Upstream DTS from Linux 5.6 was merged and they now have the SID
154 and THS (Secure ID controller and THermal Sensor) node present.
155 The DTB overlays have now been removed from the tree for the H3/H5 and
156 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
157 deal with upstream DTS. If you are using those overlays you need to
158 remove them from loader.conf and update the DTBs on the FAT partition.
161 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
162 been upgraded to 10.0.0. Please see the 20141231 entry below for
163 information about prerequisites and upgrading, if you are not already
164 using clang 3.5.0 or higher.
167 The root certificates of the Mozilla CA Certificate Store have been
168 imported into the base system and can be managed with the certctl(8)
169 utility. If you have installed the security/ca_root_nss port or package
170 with the ETCSYMLINK option (the default), be advised that there may be
171 differences between those included in the port and those included in
172 base due to differences in nss branch used as well as general update
173 frequency. Note also that certctl(8) cannot manage certs in the
174 format used by the security/ca_root_nss port.
177 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
178 been upgraded to 9.0.1. Please see the 20141231 entry below for
179 information about prerequisites and upgrading, if you are not already
180 using clang 3.5.0 or higher.
183 The nctgpio and wbwd drivers have been moved to the superio bus.
184 If you have one of these drivers in a kernel configuration, then
185 you should add device superio to it. If you use one of these drivers
186 as a module and you compile a custom set of modules, then you should
187 add superio to the set.
190 The tap(4) driver has been folded into tun(4), and the module has been
191 renamed to tuntap. You should update any kld_list="if_tap" or
192 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
193 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
194 module instead, and "device tap" or "device tun" entries in kernel
195 config files to select the tuntap device instead.
198 ntpd no longer by default locks its pages in memory, allowing them
199 to be paged out by the kernel. Use rlimit memlock to restore
200 historic BSD behaviour. For example, add "rlimit memlock 32"
201 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
204 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
205 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
206 been removed from mount_fusefs(8). You can safely remove them from
207 your scripts, because they had no effect.
209 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
210 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
211 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
212 sysctls have been removed. If you felt the need to set any of them to
213 a non-default value, please tell asomers@FreeBSD.org why.
216 The fuse(4) module has been renamed to fusefs(4) for consistency with
217 other filesystems. You should update any kld_load="fuse" entries in
218 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
219 "options FUSE" enties in kernel config files.
222 Default permissions on the /var/account/acct file (and copies of it
223 rotated by periodic daily scripts) are changed from 0644 to 0640
224 because the file contains sensitive information that should not be
225 world-readable. If the /var/account directory must be created by
226 rc.d/accounting, the mode used is now 0750. Admins who use the
227 accounting feature are encouraged to change the mode of an existing
228 /var/account directory to 0750 or 0700.
231 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
232 been upgraded to 8.0.1. Please see the 20141231 entry below for
233 information about prerequisites and upgrading, if you are not already
234 using clang 3.5.0 or higher.
237 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
238 functionality needed for the RETPOLINE option should work properly
239 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
242 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
243 8.0.0. Please see the 20141231 entry below for information about
244 prerequisites and upgrading, if you are not already using clang 3.5.0
248 The RETPOLINE option produces non-functional ifunc-using binaries
249 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
250 Once Clang 8 is merged it may be enabled again.
253 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
254 7.0.1. Please see the 20141231 entry below for information about
255 prerequisites and upgrading, if you are not already using clang 3.5.0
259 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
260 compiled into your custom kernel, add 'device xz' statement to the
264 Iflib is no longer unconditionally compiled into the kernel. Drivers
265 using iflib and statically compiled into the kernel, now require
266 the 'device iflib' config option. For the same drivers loaded as
267 modules on kernels not having 'device iflib', the iflib.ko module
268 is loaded automatically.
271 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
272 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
273 servers that have vfs.nfsd.nfs_privport set will only allow mounts
274 from clients using a reserved port#. Since both the FreeBSD and Linux
275 NFSv4 clients use reserved port#s by default, this should not affect
279 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
280 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
281 it produces broken binaries when ifuncs are in use. Users needing
282 GNU ld should install the binutils port or package.
285 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
286 has been converted to a port (misc/ctm) and will be removed from
287 FreeBSD-13. A depreciation warning will be printed to stderr by
288 the ctm command, but the functionality will remain in base for all
292 The stable/12 branch has been created in subversion from head
296 Ports for the DRM modules have been simplified. Now, amd64 users should
297 just install the drm-kmod port. All others should install
300 Graphics hardware that's newer than about 2010 usually works with
301 drm-kmod. For hardware older than 2013, however, some users will need
302 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
303 than 2008 usually only works in drm-legacy-kmod. The graphics team can
304 only commit to hardware made since 2013 due to the complexity of the
305 market and difficulty to test all the older cards effectively. If you
306 have hardware supported by drm-kmod, you are strongly encouraged to use
307 that as you will get better support.
309 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
310 elsewhere, the drm and drm2 modules will be eliminated from the src base
311 soon (with a limited exception for arm). Please update to the package asap
312 and report any issues to x11@freebsd.org.
314 Generally, anybody using the drm*-kmod packages should add
315 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
316 cross-threading surprises, especially with automatic driver
317 loading from X11 startup. These will become the defaults in 13-current
321 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
322 custom kernel and module loading configuration files must be updated
323 accordingly. Moreover, interfaces previous presented as ixlvN to the
324 system are now exposed as iavfN and network configuration files must
325 be adjusted as necessary.
328 OpenSSL has been updated to version 1.1.1. This update included
329 additional various API changes througout the base system. It is
330 important to rebuild third-party software after upgrading. The value
331 of __FreeBSD_version has been bumped accordingly.
334 The legacy DRM modules and drivers have now been added to the loader's
335 module blacklist, in favor of loading them with kld_list in rc.conf(5).
336 The module blacklist may be overridden with the loader.conf(5)
337 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
341 The cam(4) based nda(4) driver will be used over nvd(4) by default on
342 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
343 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
344 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
348 Reproducible build mode is now on by default, in preparation for
349 FreeBSD 12.0. This eliminates build metadata such as the user,
350 host, and time from the kernel (and uname), unless the working tree
351 corresponds to a modified checkout from a version control system.
352 The previous behavior can be obtained by setting the /etc/src.conf
353 knob WITHOUT_REPRODUCIBLE_BUILD.
356 The Yarrow CSPRNG has been removed from the kernel as it has not been
357 supported by its designers since at least 2003. Fortuna has been the
358 default since FreeBSD-11.
361 devctl freeze/thaw have gone into the tree, the rc scripts have been
362 updated to use them and devmatch has been changed. You should update
363 kernel, userland and rc scripts all at the same time.
366 The default interpreter has been switched from 4th to Lua.
367 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
368 interpreter. If you have custom FORTH code you will need to set
369 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
370 src.conf for the build. This will create default hard links between
371 loader and loader_4th instead of loader and loader_lua, the new default.
372 If you are using UEFI it will create the proper hard link to loader.efi.
374 bhyve uses userboot.so. It remains 4th-only until some issues are solved
375 regarding coexisting with multiple versions of FreeBSD are resolved.
378 ls(1) now respects the COLORTERM environment variable used in other
379 systems and software to indicate that a colored terminal is both
380 supported and desired. If ls(1) is suddenly emitting colors, they may
381 be disabled again by either removing the unwanted COLORTERM from your
382 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
383 may not be observed in a future release.
386 The default pager for most commands has been changed to "less". To
387 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
391 The jedec_ts(4) driver has been removed. A superset of its functionality
392 is available in the jedec_dimm(4) driver, and the manpage for that
393 driver includes migration instructions. If you have "device jedec_ts"
394 in your kernel configuration file, it must be removed.
397 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
398 This should have no effect if the kernel is booted via BIOS/legacy boot.
399 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
400 has a buggy firmware that prevents a successful boot due to use of
404 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
405 support has been removed from the tree. These ports were
406 obsolete and/or known to be broken for many years.
409 loader.efi has been augmented to participate more fully in the
410 UEFI boot manager protocol. loader.efi will now look at the
411 BootXXXX environment variable to determine if a specific kernel
412 or root partition was specified. XXXX is derived from BootCurrent.
413 efibootmgr(8) manages these standard UEFI variables.
416 zfsloader's functionality has now been folded into loader.
417 zfsloader is no longer necessary once you've updated your
418 boot blocks. For a transition period, we will install a
419 hardlink for zfsloader to loader to allow a smooth transition
420 until the boot blocks can be updated (hard link because old
421 zfs boot blocks don't understand symlinks).
424 ARM64 now have efifb support, if you want to have serial console
425 on your arm64 board when an screen is connected and the bootloader
426 setup a frambuffer for us to use, just add :
430 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
431 an screen connected as the firmware will setup a framebuffer are that
432 u-boot will expose as an EFI framebuffer.
435 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
436 or take steps to update /etc/passwd before doing installworld on
437 existing systems. Do not skip the "mergemaster -Fp" step before
438 installworld, as described in the update procedures near the bottom
439 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
440 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
441 the ntp config file contain options that change file/dir locations.
442 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
443 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
444 taking steps to ensure that all required files/dirs are accessible
448 Big endian arm support has been removed.
451 The static environment setup in kernel configs is no longer mutually
452 exclusive with the loader(8) environment by default. In order to
453 restore the previous default behavior of disabling the loader(8)
454 environment if a static environment is present, you must specify
455 loader_env.disabled=1 in the static environment.
458 The ABI of syscalls used by management tools like sockstat and
459 netstat has been broken to allow 32-bit binaries to work on
460 64-bit kernels without modification. These programs will need
461 to match the kernel in order to function. External programs may
462 require minor modifications to accommodate a change of type in
463 structures from pointers to 64-bit virtual addresses.
466 On i386 and amd64 atomics are now inlined. Out of tree modules using
467 atomics will need to be rebuilt.
470 The '%I' format in the kern.corefile sysctl limits the number of
471 core files that a process can generate to the number stored in the
472 debug.ncores sysctl. The '%I' format is replaced by the single digit
473 index. Previously, if all indexes were taken the kernel would overwrite
474 only a core file with the highest index in a filename.
475 Currently the system will create a new core file if there is a free
476 index or if all slots are taken it will overwrite the oldest one.
479 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
480 6.0.1. Please see the 20141231 entry below for information about
481 prerequisites and upgrading, if you are not already using clang 3.5.0
485 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
486 needed to be changed to work with it. This change was made with r335763
487 and requires a mergemaster / etcupdate / etc to update the installed file.
490 r334930 changed the interface between the NFS modules, so they all
491 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
494 As of r334391 lld is the default amd64 system linker; it is installed
495 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
499 The kernel / userland interface for devinfo changed, so you'll
500 need a new kernel and userland as a pair for it to work (rebuilding
501 lib/libdevinfo is all that's required). devinfo and devmatch will
502 not work, but everything else will when there's a mismatch.
505 The on-disk format for hwpmc callchain records has changed to include
506 threadid corresponding to a given record. This changes the field offsets
507 and thus requires that libpmcstat be rebuilt before using a kernel
511 The vxge(4) driver has been removed. This driver was introduced into
512 HEAD one week before the Exar left the Ethernet market and is not
513 known to be used. If you have device vxge in your kernel config file
517 The amd64 kernel now requires a ld that supports ifunc to produce a
518 working kernel, either lld or a newer binutils. lld is built by default
519 on amd64, and the 'buildkernel' target uses it automatically. However,
520 it is not the default linker, so building the kernel the traditional
521 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
522 binutils port/package). lld will soon be default, and this requirement
525 NOTE: As of r334391 lld is the default system linker on amd64, and no
526 workaround is necessary.
529 The nxge(4) driver has been removed. This driver was for PCI-X 10g
530 cards made by s2io/Neterion. The company was aquired by Exar and
531 no longer sells or supports Ethernet products. If you have device
532 nxge in your kernel config file it must be removed.
535 The tz database (tzdb) has been updated to 2018e. This version more
536 correctly models time stamps in time zones with negative DST such as
537 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
538 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
539 time zone abbreviations and the tm_isdst flag.
542 The ixgb(4) driver has been removed. This driver was for an early and
543 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
544 quickly shifted to the long lived ixgbe family. If you have device
545 ixgb in your kernel config file it must be removed.
548 The lmc(4) driver has been removed. This was a WAN interface
549 card that was already reportedly rare in 2003, and had an ambiguous
550 license. If you have device lmc in your kernel config file it must
554 Support for Arcnet networks has been removed. If you have device
555 arcnet or device cm in your kernel config file they must be
559 Support for FDDI networks has been removed. If you have device
560 fddi or device fpa in your kernel config file they must be
564 In addition to supporting RFC 3164 formatted messages, the
565 syslogd(8) service is now capable of parsing RFC 5424 formatted
566 log messages. The main benefit of using RFC 5424 is that clients
567 may now send log messages with timestamps containing year numbers,
568 microseconds and time zone offsets.
570 Similarly, the syslog(3) C library function has been altered to
571 send RFC 5424 formatted messages to the local system logging
572 daemon. On systems using syslogd(8), this change should have no
573 negative impact, as long as syslogd(8) and the C library are
574 updated at the same time. On systems using a different system
575 logging daemon, it may be necessary to make configuration
576 adjustments, depending on the software used.
578 When using syslog-ng, add the 'syslog-protocol' flag to local
579 input sources to enable parsing of RFC 5424 formatted messages:
582 unix-dgram("/var/run/log" flags(syslog-protocol));
585 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
586 of the 'imuxsock' module to let messages be processed by the
587 regular RFC 3164/5424 parsing pipeline:
589 module(load="imuxsock" SysSock.UseSpecialParser="off")
591 Do note that these changes only affect communication between local
592 applications and syslogd(8). The format that syslogd(8) uses to
593 store messages on disk or forward messages to other systems
594 remains unchanged. syslogd(8) still uses RFC 3164 for these
595 purposes. Options to customize this behaviour will be added in the
596 future. Utilities that process log files stored in /var/log are
597 thus expected to continue to function as before.
599 __FreeBSD_version has been incremented to 1200061 to denote this
603 Support for token ring networks has been removed. If you
604 have "device token" in your kernel config you should remove
605 it. No device drivers supported token ring.
608 makefs was modified to be able to tag ISO9660 El Torito boot catalog
609 entries as EFI instead of overloading the i386 tag as done previously.
610 The amd64 mkisoimages.sh script used to build amd64 ISO images for
611 release was updated to use this. This may mean that makefs must be
612 updated before "make cdrom" can be run in the release directory. This
613 should be as simple as:
615 $ cd $SRCDIR/usr.sbin/makefs
616 $ make depend all install
619 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
620 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
621 Co-existance for the transition period will come shortly. Booting is a
622 complex environment and test coverage for Lua-enabled loaders has been
623 thin, so it would be prudent to assume it might not work and make
624 provisions for backup boot methods.
627 devmatch functionality has been turned on in devd. It will automatically
628 load drivers for unattached devices. This may cause unexpected drivers to
629 be loaded. Please report any problems to current@ and imp@freebsd.org.
632 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
633 6.0.0. Please see the 20141231 entry below for information about
634 prerequisites and upgrading, if you are not already using clang 3.5.0
638 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
639 This means it is used to link the kernel and userland libraries and
640 executables, but is not yet installed as /usr/bin/ld by default.
642 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
643 WITHOUT_LLD_BOOTSTRAP=yes
646 On i386, pmtimer has been removed. Its functionality has been folded
647 into apm. It was a no-op on ACPI in current for a while now (but was still
648 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
649 from kernel config files.
652 The use of RSS hash from the network card aka flowid has been
653 disabled by default for lagg(4) as it's currently incompatible with
654 the lacp and loadbalance protocols.
656 This can be re-enabled by setting the following in loader.conf:
657 net.link.lagg.default_use_flowid="1"
660 The SW_WATCHDOG option is no longer necessary to enable the
661 hardclock-based software watchdog if no hardware watchdog is
662 configured. As before, SW_WATCHDOG will cause the software
663 watchdog to be enabled even if a hardware watchdog is configured.
666 r326887 fixes the issue described in the 20171214 UPDATING entry.
667 r326888 flips the switch back to building GELI support always.
670 r362593 broke ZFS + GELI support for reasons unknown. However,
671 it also broke ZFS support generally, so GELI has been turned off
672 by default as the lesser evil in r326857. If you boot off ZFS and/or
673 GELI, it might not be a good time to update.
676 PowerPC users must update loader(8) by rebuilding world before
677 installing a new kernel, as the protocol connecting them has
678 changed. Without the update, loader metadata will not be passed
679 successfully to the kernel and users will have to enter their
680 root partition at the kernel mountroot prompt to continue booting.
681 Newer versions of loader can boot old kernels without issue.
684 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
685 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
686 to WITH/OUT_LOADER_GELI.
689 The naive and non-compliant support of posix_fallocate(2) in ZFS
690 has been removed as of r325320. The system call now returns EINVAL
691 when used on a ZFS file. Although the new behavior complies with the
692 standard, some consumers are not prepared to cope with it.
693 One known victim is lld prior to r325420.
696 Building in a FreeBSD src checkout will automatically create object
697 directories now rather than store files in the current directory if
698 'make obj' was not ran. Calling 'make obj' is no longer necessary.
699 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
700 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
704 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
705 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
706 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
707 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
708 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
709 The UNIFIED_OBJDIR option is a transitional feature that will be
710 removed for 12.0 release; please migrate to the new format for any
711 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
712 than hardcoding paths.
715 The native-xtools target no longer installs the files by default to the
716 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
717 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
720 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
721 options are changing from controlling the build if defined / undefined
722 to controlling the build with explicit 'yes' or 'no' values. They will
723 shift to WITH/WITHOUT options to match other options in the system.
726 libstand has turned into a private library for sys/boot use only.
727 It is no longer supported as a public interface outside of sys/boot.
730 The arm port has split armv6 into armv6 and armv7. armv7 is now
731 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
732 and are running a kernel from before r324363, you will need to add
733 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
736 When building multiple kernels using KERNCONF, non-existent KERNCONF
737 files will produce an error and buildkernel will fail. Previously
738 missing KERNCONF files silently failed giving no indication as to
739 why, only to subsequently discover during installkernel that the
740 desired kernel was never built in the first place.
743 The default serial number format for CTL LUNs has changed. This will
744 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
745 or iSCSI clients care about their LUNs' serial numbers. Users who
746 require serial number stability should hardcode serial numbers in
750 For 32-bit arm compiled for hard-float support, soft-floating point
751 binaries now always get their shared libraries from
752 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
753 /usr/libsoft also existed). Only users with a hard-float ld.so, but
754 soft-float everything else should be affected.
757 The geli password typed at boot is now hidden. To restore the previous
758 behavior, see geli(8) for configuration options.
761 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
762 sysctl values. Minor nit, but requires a rebuild of both world/kernel
766 "make check" behavior (made in ^/head@r295380) has been changed to
767 execute from a limited sandbox, as opposed to executing from
771 - The "beforecheck" and "aftercheck" targets are now specified.
772 - ${CHECKDIR} (added in commit noted above) has been removed.
773 - Legacy behavior can be enabled by setting
774 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
776 If the limited sandbox mode is enabled, "make check" will execute
777 "make distribution", then install, execute the tests, and clean up the
778 sandbox if successful.
780 The "make distribution" and "make install" targets are typically run as
781 root to set appropriate permissions and ownership at installation time.
782 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
783 environment if executing "make check" with limited sandbox mode using
784 an unprivileged user.
787 Since the switch to GPT disk labels, fsck for UFS/FFS has been
788 unable to automatically find alternate superblocks. As of r322297,
789 the information needed to find alternate superblocks has been
790 moved to the end of the area reserved for the boot block.
791 Filesystems created with a newfs of this vintage or later
792 will create the recovery information. If you have a filesystem
793 created prior to this change and wish to have a recovery block
794 created for your filesystem, you can do so by running fsck in
795 foreground mode (i.e., do not use the -p or -y options). As it
796 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
797 to which you should answer yes.
800 As of r321665, an NFSv4 server configuration that services
801 Kerberos mounts or clients that do not support the uid/gid in
802 owner/owner_group string capability, must explicitly enable
803 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
804 machine's /etc/rc.conf file.
807 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
808 Please see the 20141231 entry below for information about prerequisites
809 and upgrading, if you are not already using clang 3.5.0 or higher.
812 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
813 r-commands (rlogin, rsh, etc.) to be built with the base system.
816 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
817 a very major ABI incompatible change, so users of FreeBSD/powerpc must
818 be careful when performing source upgrades. It is best to run
819 'make installworld' from an alternate root system, either a live
820 CD/memory stick, or a temporary root partition. Additionally, all ports
821 must be recompiled. powerpc64 is largely unaffected, except in the case
822 of 32-bit compatibility. All 32-bit binaries will be affected.
825 Forward compatibility for the "ino64" project have been committed. This
826 will allow most new binaries to run on older kernels in a limited
827 fashion. This prevents many of the common foot-shooting actions in the
828 upgrade as well as the limited ability to roll back the kernel across
829 the ino64 upgrade. Complicated use cases may not work properly, though
830 enough simpler ones work to allow recovery in most situations.
833 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
834 if you require the GPL compiler.
837 The internal ABI used for communication between the NFS kernel modules
838 was changed by r320085, so __FreeBSD_version was bumped to
839 ensure all the NFS related modules are updated together.
842 The ABI of struct event was changed by extending the data
843 member to 64bit and adding ext fields. For upgrade, same
844 precautions as for the entry 20170523 "ino64" must be
848 The GNU roff toolchain has been removed from base. To render manpages
849 which are not supported by mandoc(1), man(1) can fallback on GNU roff
850 from ports (and recommends to install it).
851 To render roff(7) documents, consider using GNU roff from ports or the
852 heirloom doctools roff toolchain from ports via pkg install groff or
853 via pkg install heirloom-doctools.
856 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
857 smaller runtime footprint builds. This is useful for embedded systems
858 which only require one chipset support.
860 If you load it as a module, make sure this is in /boot/loader.conf:
864 This will load the HAL, all chip/RF backends and if_ath_pci.
865 If you have if_ath_pci in /boot/loader.conf, ensure it is after
866 if_ath or it will not load any HAL chipset support.
868 If you want to selectively load things (eg on ye cheape ARM/MIPS
869 platforms where RAM is at a premium) you should:
872 * load the chip modules in question
873 * load ath_rate, ath_dfs
875 * load if_ath_pci and/or if_ath_ahb depending upon your particular
876 bus bind type - this is where probe/attach is done.
878 For further comments/feedback, poke adrian@ .
881 The "ino64" 64-bit inode project has been committed, which extends
882 a number of types to 64 bits. Upgrading in place requires care and
883 adherence to the documented upgrade procedure.
885 If using a custom kernel configuration ensure that the
886 COMPAT_FREEBSD11 option is included (as during the upgrade the
887 system will be running the ino64 kernel with the existing world).
889 For the safest in-place upgrade begin by removing previous build
890 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
891 full procedure documented below under the heading "To rebuild
892 everything and install it on the current system." Specifically,
893 a reboot is required after installing the new kernel before
897 The NATM framework including the en(4), fatm(4), hatm(4), and
898 patm(4) devices has been removed. Consumers should plan a
899 migration before the end-of-life date for FreeBSD 11.
902 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
903 diff has not been implemented, if those are needed a newer version of
904 GNU diff is available via the diffutils package under the gdiff name.
907 As of r316810 for ipfilter, keep frags is no longer assumed when
908 keep state is specified in a rule. r316810 aligns ipfilter with
909 documentation in man pages separating keep frags from keep state.
910 This allows keep state to be specified without forcing keep frags
911 and allows keep frags to be specified independently of keep state.
912 To maintain previous behaviour, also specify keep frags with
913 keep state (as documented in ipf.conf.5).
916 arm64 builds now use the base system LLD 4.0.0 linker by default,
917 instead of requiring that the aarch64-binutils port or package be
918 installed. To continue using aarch64-binutils, set
919 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
922 The UDP optimization in entry 20160818 that added the sysctl
923 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
924 packets will no longer be treated as L3 broadcast packets.
927 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
928 use any explicitly assigned loopback address available in the jail
929 instead of using the first assigned address of the jail.
932 The ctl.ko module no longer implements the iSCSI target frontend:
933 cfiscsi.ko does instead.
935 If building cfiscsi.ko as a kernel module, the module can be loaded
936 via one of the following methods:
937 - `cfiscsi_load="YES"` in loader.conf(5).
938 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
939 - ctladm(8)/ctld(8), when compiled with iSCSI support
940 (`WITH_ISCSI=yes` in src.conf(5))
942 Please see cfiscsi(4) for more details.
945 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
946 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
947 same source (previously, the dependency of mmcsd.ko on mmc.ko was
948 missing, but mmcsd.ko now will refuse to load if it is incompatible
952 The syntax of ipfw(8) named states was changed to avoid ambiguity.
953 If you have used named states in the firewall rules, you need to modify
954 them after installworld and before rebooting. Now named states must
955 be prefixed with colon.
958 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
959 removed as the userland we provide cannot use them. The KMS version
960 (sys/dev/drm2) supports the same hardware.
963 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
964 Please see the 20141231 entry below for information about prerequisites
965 and upgrading, if you are not already using clang 3.5.0 or higher.
968 The code that provides support for ZFS .zfs/ directory functionality
969 has been reimplemented. It's not possible now to create a snapshot
970 by mkdir under .zfs/snapshot/. That should be the only user visible
974 EISA bus support has been removed. The WITH_EISA option is no longer
978 MCA bus support has been removed.
981 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
982 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
985 The EM_MULTIQUEUE kernel configuration option is deprecated now that
986 the em(4) driver conforms to iflib specifications.
989 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
990 IFLIB. If you have a custom kernel configuration that excludes em(4)
991 but you use igb(4), you need to re-add em(4) to your custom configuration.
994 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
995 Please see the 20141231 entry below for information about prerequisites
996 and upgrading, if you are not already using clang 3.5.0 or higher.
999 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1000 Please see the 20141231 entry below for information about prerequisites
1001 and upgrading, if you are not already using clang 3.5.0 or higher.
1004 The layout of the pmap structure has changed for powerpc to put the pmap
1005 statistics at the front for all CPU variations. libkvm(3) and all tools
1006 that link against it need to be recompiled.
1009 isl(4) and cyapa(4) drivers now require a new driver,
1010 chromebook_platform(4), to work properly on Chromebook-class hardware.
1011 On other types of hardware the drivers may need to be configured using
1012 device hints. Please see the corresponding manual pages for details.
1015 The urtwn(4) driver was merged into rtwn(4) and now consists of
1016 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1018 Also, firmware for RTL8188CE was renamed due to possible name
1019 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1022 GNU rcs has been removed from base. It is available as packages:
1023 - rcs: Latest GPLv3 GNU rcs version.
1024 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1028 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1029 modules now requires that the kernel configuration contain the
1030 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1033 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1034 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1037 Relocatable object files with the extension of .So have been renamed
1038 to use an extension of .pico instead. The purpose of this change is
1039 to avoid a name clash with shared libraries on case-insensitive file
1040 systems. On those file systems, foo.So is the same file as foo.so.
1043 GNU rcs has been turned off by default. It can (temporarily) be built
1044 again by adding WITH_RCS knob in src.conf.
1045 Otherwise, GNU rcs is available from packages:
1046 - rcs: Latest GPLv3 GNU rcs version.
1047 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1050 The backup_uses_rcs functionality has been removed from rc.subr.
1053 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1054 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1055 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1056 QUEUE_MACRO_DEBUG behavior.
1059 r304787 changed some ioctl interfaces between the iSCSI userspace
1060 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1061 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1065 The UDP receive code has been updated to only treat incoming UDP
1066 packets that were addressed to an L2 broadcast address as L3
1067 broadcast packets. It is not expected that this will affect any
1068 standards-conforming UDP application. The new behaviour can be
1069 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1073 Remove the openbsd_poll system call.
1074 __FreeBSD_version has been bumped because of this.
1077 The stable/11 branch has been created from head@r302406.
1080 The libc stub for the pipe(2) system call has been replaced with
1081 a wrapper that calls the pipe2(2) system call and the pipe(2)
1082 system call is now only implemented by the kernels that include
1083 "options COMPAT_FREEBSD10" in their config file (this is the
1084 default). Users should ensure that this option is enabled in
1085 their kernel or upgrade userspace to r302092 before upgrading their
1089 CAM will now strip leading spaces from SCSI disks' serial numbers.
1090 This will affect users who create UFS filesystems on SCSI disks using
1091 those disk's diskid device nodes. For example, if /etc/fstab
1092 previously contained a line like
1093 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1094 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1095 transforms like gmirror may also be affected. ZFS users should
1099 The bitstring(3) API has been updated with new functionality and
1100 improved performance. But it is binary-incompatible with the old API.
1101 Objects built with the new headers may not be linked against objects
1102 built with the old headers.
1105 The brk and sbrk functions have been removed from libc on arm64.
1106 Binutils from ports has been updated to not link to these
1107 functions and should be updated to the latest version before
1108 installing a new libc.
1111 The armv6 port now defaults to hard float ABI. Limited support
1112 for running both hardfloat and soft float on the same system
1113 is available using the libraries installed with -DWITH_LIBSOFT.
1114 This has only been tested as an upgrade path for installworld
1115 and packages may fail or need manual intervention to run. New
1116 packages will be needed.
1118 To update an existing self-hosted armv6hf system, you must add
1119 TARGET_ARCH=armv6 on the make command line for both the build
1120 and the install steps.
1123 Kernel modules compiled outside of a kernel build now default to
1124 installing to /boot/modules instead of /boot/kernel. Many kernel
1125 modules built this way (such as those in ports) already overrode
1126 KMODDIR explicitly to install into /boot/modules. However,
1127 manually building and installing a module from /sys/modules will
1128 now install to /boot/modules instead of /boot/kernel.
1131 The CAM I/O scheduler has been committed to the kernel. There should be
1132 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1133 list of known rogues that claim support for this but actually corrupt
1134 data is believed to be complete, be on the lookout for data
1135 corruption. The known rogue list is believed to be complete:
1137 o Crucial MX100, M550 drives with MU01 firmware.
1138 o Micron M510 and M550 drives with MU01 firmware.
1139 o Micron M500 prior to MU07 firmware
1140 o Samsung 830, 840, and 850 all firmwares
1141 o FCCT M500 all firmwares
1143 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1144 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1145 updated firmware. Black listed drives will work correctly because these
1146 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1147 this list is the same as found in Linux, it's believed there are no
1148 other rogues in the market place. All other models from the above
1151 To be safe, if you are at all concerned, you can quirk each of your
1152 drives to prevent NCQ from being sent by setting:
1153 kern.cam.ada.X.quirks="0x2"
1154 in loader.conf. If the drive requires the 4k sector quirk, set the
1155 quirks entry to 0x3.
1158 The FAST_DEPEND build option has been removed and its functionality is
1159 now the one true way. The old mkdep(1) style of 'make depend' has
1160 been removed. See 20160311 for further details.
1163 Resource range types have grown from unsigned long to uintmax_t. All
1164 drivers, and anything using libdevinfo, need to be recompiled.
1167 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1168 builds. It no longer runs mkdep(1) during 'make depend', and the
1169 'make depend' stage can safely be skipped now as it is auto ran
1170 when building 'make all' and will generate all SRCS and DPSRCS before
1171 building anything else. Dependencies are gathered at compile time with
1172 -MF flags kept in separate .depend files per object file. Users should
1173 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1174 stale .depend files.
1177 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1178 kernel modules. Therefore, if you load any kernel modules at boot time,
1179 please install the boot loaders after you install the kernel, but before
1183 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1184 make installkernel KERNCONF=YOUR_KERNEL_HERE
1185 make -C sys/boot install
1186 <reboot in single user>
1188 Then follow the usual steps, described in the General Notes section,
1192 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1193 see the 20141231 entry below for information about prerequisites and
1194 upgrading, if you are not already using clang 3.5.0 or higher.
1197 The AIO subsystem is now a standard part of the kernel. The
1198 VFS_AIO kernel option and aio.ko kernel module have been removed.
1199 Due to stability concerns, asynchronous I/O requests are only
1200 permitted on sockets and raw disks by default. To enable
1201 asynchronous I/O requests on all file types, set the
1202 vfs.aio.enable_unsafe sysctl to a non-zero value.
1205 The ELF object manipulation tool objcopy is now provided by the
1206 ELF Tool Chain project rather than by GNU binutils. It should be a
1207 drop-in replacement, with the addition of arm64 support. The
1208 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1209 to obtain the GNU version if necessary.
1212 Building ZFS pools on top of zvols is prohibited by default. That
1213 feature has never worked safely; it's always been prone to deadlocks.
1214 Using a zvol as the backing store for a VM guest's virtual disk will
1215 still work, even if the guest is using ZFS. Legacy behavior can be
1216 restored by setting vfs.zfs.vol.recursive=1.
1219 The NONE and HPN patches has been removed from OpenSSH. They are
1220 still available in the security/openssh-portable port.
1223 With the addition of ypldap(8), a new _ypldap user is now required
1224 during installworld. "mergemaster -p" can be used to add the user
1225 prior to installworld, as documented in the handbook.
1228 The tftp loader (pxeboot) now uses the option root-path directive. As a
1229 consequence it no longer looks for a pxeboot.4th file on the tftp
1230 server. Instead it uses the regular /boot infrastructure as with the
1234 The code to start recording plug and play data into the modules has
1235 been committed. While the old tools will properly build a new kernel,
1236 a number of warnings about "unknown metadata record 4" will be produced
1237 for an older kldxref. To avoid such warnings, make sure to rebuild
1238 the kernel toolchain (or world). Make sure that you have r292078 or
1239 later when trying to build 292077 or later before rebuilding.
1242 Debug data files are now built by default with 'make buildworld' and
1243 installed with 'make installworld'. This facilitates debugging but
1244 requires more disk space both during the build and for the installed
1245 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1249 r291527 changed the internal interface between the nfsd.ko and
1250 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1251 __FreeBSD_version has been bumped because of this.
1254 Add support for unicode collation strings leads to a change of
1255 order of files listed by ls(1) for example. To get back to the old
1256 behaviour, set LC_COLLATE environment variable to "C".
1258 Databases administrators will need to reindex their databases given
1259 collation results will be different.
1261 Due to a bug in install(1) it is recommended to remove the ancient
1262 locales before running make installworld.
1264 rm -rf /usr/share/locale/*
1267 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1268 libcrypto.so.7 or libssl.so.7 must be recompiled.
1271 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1272 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1273 should be replaced with isp_2400 and isp_2500 modules respectively.
1276 The build previously allowed using 'make -n' to not recurse into
1277 sub-directories while showing what commands would be executed, and
1278 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1279 and 'make -N' will not.
1282 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1283 and etcupdate will now use this file. A custom sendmail.cf is now
1284 updated via this mechanism rather than via installworld. If you had
1285 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1286 want to remove the exclusion or change it to "always install".
1287 /etc/mail/sendmail.cf is now managed the same way regardless of
1288 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1289 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1292 Compatibility shims for legacy ATA device names have been removed.
1293 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1294 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1295 environment variables, /dev/ad* and /dev/ar* symbolic links.
1298 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1299 Please see the 20141231 entry below for information about prerequisites
1300 and upgrading, if you are not already using clang 3.5.0 or higher.
1303 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1304 and renamed from .symbols to .debug. This reduces the size requirements
1305 on the boot partition or file system and provides consistency with
1306 userland debug files.
1308 When using the supported kernel installation method the
1309 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1310 as is done with /boot/kernel.
1312 Developers wishing to maintain the historical behavior of installing
1313 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1316 The wireless drivers had undergone changes that remove the 'parent
1317 interface' from the ifconfig -l output. The rc.d network scripts
1318 used to check presence of a parent interface in the list, so old
1319 scripts would fail to start wireless networking. Thus, etcupdate(3)
1320 or mergemaster(8) run is required after kernel update, to update your
1321 rc.d scripts in /etc.
1324 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1325 These configurations are now automatically interpreted as
1326 'scrub fragment reassemble'.
1329 Kernel-loadable modules for the random(4) device are back. To use
1330 them, the kernel must have
1333 options RANDOM_LOADABLE
1335 kldload(8) can then be used to load random_fortuna.ko
1336 or random_yarrow.ko. Please note that due to the indirect
1337 function calls that the loadable modules need to provide,
1338 the build-in variants will be slightly more efficient.
1340 The random(4) kernel option RANDOM_DUMMY has been retired due to
1341 unpopularity. It was not all that useful anyway.
1344 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1345 Control over building the ELF Tool Chain tools is now provided by
1346 the WITHOUT_TOOLCHAIN knob.
1349 The polarity of Pulse Per Second (PPS) capture events with the
1350 uart(4) driver has been corrected. Prior to this change the PPS
1351 "assert" event corresponded to the trailing edge of a positive PPS
1352 pulse and the "clear" event was the leading edge of the next pulse.
1354 As the width of a PPS pulse in a typical GPS receiver is on the
1355 order of 1 millisecond, most users will not notice any significant
1356 difference with this change.
1358 Anyone who has compensated for the historical polarity reversal by
1359 configuring a negative offset equal to the pulse width will need to
1360 remove that workaround.
1363 The default group assigned to /dev/dri entries has been changed
1364 from 'wheel' to 'video' with the id of '44'. If you want to have
1365 access to the dri devices please add yourself to the video group
1368 # pw groupmod video -m $USER
1371 The menu.rc and loader.rc files will now be replaced during
1372 upgrades. Please migrate local changes to menu.rc.local and
1373 loader.rc.local instead.
1376 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1377 strings and strip have been removed. The src.conf(5) knob
1378 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1381 As ZFS requires more kernel stack pages than is the default on some
1382 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1383 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1385 Please consider using 'options KSTACK_PAGES=X' where X is greater
1386 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1389 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1390 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1391 default, i.e., they will not contain "::". For example, instead
1392 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1393 to have a more specific match, such as different map entries for
1394 IPv6:0:0 vs IPv6:0. This change requires that configuration
1395 data (including maps, files, classes, custom ruleset, etc.) must
1396 use the same format, so make certain such configuration data is
1397 upgrading. As a very simple check search for patterns like
1398 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1399 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1400 the cf option UseCompressedIPv6Addresses.
1403 The default kernel entropy-processing algorithm is now
1404 Fortuna, replacing Yarrow.
1406 Assuming you have 'device random' in your kernel config
1407 file, the configurations allow a kernel option to override
1408 this default. You may choose *ONE* of:
1410 options RANDOM_YARROW # Legacy /dev/random algorithm.
1411 options RANDOM_DUMMY # Blocking-only driver.
1413 If you have neither, you get Fortuna. For most people,
1414 read no further, Fortuna will give a /dev/random that works
1415 like it always used to, and the difference will be irrelevant.
1417 If you remove 'device random', you get *NO* kernel-processed
1418 entropy at all. This may be acceptable to folks building
1419 embedded systems, but has complications. Carry on reading,
1420 and it is assumed you know what you need.
1422 *PLEASE* read random(4) and random(9) if you are in the
1423 habit of tweaking kernel configs, and/or if you are a member
1424 of the embedded community, wanting specific and not-usual
1425 behaviour from your security subsystems.
1427 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1428 random', you will NOT have a functioning /dev/random, and
1429 many cryptographic features will not work, including SSH.
1430 You may also find strange behaviour from the random(3) set
1431 of library functions, in particular sranddev(3), srandomdev(3)
1432 and arc4random(3). The reason for this is that the KERN_ARND
1433 sysctl only returns entropy if it thinks it has some to
1434 share, and with RANDOM_DUMMY or no 'device random' this
1438 An additional fix for the issue described in the 20150614 sendmail
1439 entry below has been committed in revision 284717.
1442 FreeBSD's old make (fmake) has been removed from the system. It is
1443 available as the devel/fmake port or via pkg install fmake.
1446 The fix for the issue described in the 20150614 sendmail entry
1447 below has been committed in revision 284436. The work
1448 around described in that entry is no longer needed unless the
1449 default setting is overridden by a confDH_PARAMETERS configuration
1450 setting of '5' or pointing to a 512 bit DH parameter file.
1453 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1454 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1455 and devel/kyua to version 0.20+ and adjust any calling code to work
1456 with Kyuafile and kyua.
1459 The import of openssl to address the FreeBSD-SA-15:10.openssl
1460 security advisory includes a change which rejects handshakes
1461 with DH parameters below 768 bits. sendmail releases prior
1462 to 8.15.2 (not yet released), defaulted to a 512 bit
1463 DH parameter setting for client connections. To work around
1464 this interoperability, sendmail can be configured to use a
1465 2048 bit DH parameter by:
1467 1. Edit /etc/mail/`hostname`.mc
1468 2. If a setting for confDH_PARAMETERS does not exist or
1469 exists and is set to a string beginning with '5',
1470 replace it with '2'.
1471 3. If a setting for confDH_PARAMETERS exists and is set to
1472 a file path, create a new file with:
1473 openssl dhparam -out /path/to/file 2048
1474 4. Rebuild the .cf file:
1475 cd /etc/mail/; make; make install
1476 5. Restart sendmail:
1477 cd /etc/mail/; make restart
1479 A sendmail patch is coming, at which time this file will be
1483 Generation of legacy formatted entries have been disabled by default
1484 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1485 entries were converted to use the new format by default when the new,
1486 machine independent format have been added and supported since FreeBSD
1489 Please see the pwd_mkdb(8) manual page for further details.
1492 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1493 20141231 entry below for information about prerequisites and upgrading,
1494 if you are not already using 3.5.0 or higher.
1497 TI platform code switched to using vendor DTS files and this update
1498 may break existing systems running on Beaglebone, Beaglebone Black,
1501 - dtb files should be regenerated/reinstalled. Filenames are the
1502 same but content is different now
1503 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1504 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1505 addressing scheme is now pin 25 on /dev/gpioc3.
1506 - Pandaboard: /etc/ttys should be updated, serial console device is
1507 now /dev/ttyu2, not /dev/ttyu0
1510 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1511 If you need the GNU extension from groff soelim(1), install groff
1512 from package: pkg install groff, or via ports: textproc/groff.
1515 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1516 defined in symlink(7); previously symlinks were silently ignored.
1519 The const qualifier has been removed from iconv(3) to comply with
1520 POSIX. The ports tree is aware of this from r384038 onwards.
1523 Libraries specified by LIBADD in Makefiles must have a corresponding
1524 DPADD_<lib> variable to ensure correct dependencies. This is now
1525 enforced in src.libnames.mk.
1528 From legacy ata(4) driver was removed support for SATA controllers
1529 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1530 Kernel modules ataahci and ataadaptec were removed completely,
1531 replaced by ahci and mvs modules respectively.
1534 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1535 the 20141231 entry below for information about prerequisites and
1536 upgrading, if you are not already using 3.5.0 or higher.
1539 The 32-bit PowerPC kernel has been changed to a position-independent
1540 executable. This can only be booted with a version of loader(8)
1541 newer than January 31, 2015, so make sure to update both world and
1542 kernel before rebooting.
1545 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1546 but before r278950, the RNG was not seeded properly. Immediately
1547 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1548 ssh keys or openssl keys) that were generated w/ a kernel from that
1549 range. This does not affect programs that directly used /dev/random
1550 or /dev/urandom. All userland uses of arc4random(3) are affected.
1553 The autofs(4) ABI was changed in order to restore binary compatibility
1554 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1555 with the new kernel.
1558 The powerpc64 kernel has been changed to a position-independent
1559 executable. This can only be booted with a new version of loader(8),
1560 so make sure to update both world and kernel before rebooting.
1563 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1564 only release, no new features have been added. Please see the 20141231
1565 entry below for information about prerequisites and upgrading, if you
1566 are not already using 3.5.0.
1569 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1570 taken from the ELF Tool Chain project rather than GNU binutils. They
1571 should be drop-in replacements, with the addition of arm64 support.
1572 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1573 binutils tools, if necessary. See 20150805 for updated information.
1576 The default Unbound configuration now enables remote control
1577 using a local socket. Users who have already enabled the
1578 local_unbound service should regenerate their configuration
1579 by running "service local_unbound setup" as root.
1582 The GNU texinfo and GNU info pages have been removed.
1583 To be able to view GNU info pages please install texinfo from ports.
1586 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1588 As of this release, a prerequisite for building clang, llvm and lldb is
1589 a C++11 capable compiler and C++11 standard library. This means that to
1590 be able to successfully build the cross-tools stage of buildworld, with
1591 clang as the bootstrap compiler, your system compiler or cross compiler
1592 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1593 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1596 On any standard FreeBSD 10.x or 11.x installation, where clang and
1597 libc++ are on by default (that is, on x86 or arm), this should work out
1600 On 9.x installations where clang is enabled by default, e.g. on x86 and
1601 powerpc, libc++ will not be enabled by default, so libc++ should be
1602 built (with clang) and installed first. If both clang and libc++ are
1603 missing, build clang first, then use it to build libc++.
1605 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1606 the instructions for 9.x above.
1608 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1609 default, and do not build clang.
1611 Many embedded systems are resource constrained, and will not be able to
1612 build clang in a reasonable time, or in some cases at all. In those
1613 cases, cross building bootable systems on amd64 is a workaround.
1615 This new version of clang introduces a number of new warnings, of which
1616 the following are most likely to appear:
1620 This warns in two cases, for both C and C++:
1621 * When the code is trying to take the absolute value of an unsigned
1622 quantity, which is effectively a no-op, and almost never what was
1623 intended. The code should be fixed, if at all possible. If you are
1624 sure that the unsigned quantity can be safely cast to signed, without
1625 loss of information or undefined behavior, you can add an explicit
1626 cast, or disable the warning.
1628 * When the code is trying to take an absolute value, but the called
1629 abs() variant is for the wrong type, which can lead to truncation.
1630 If you want to disable the warning instead of fixing the code, please
1631 make sure that truncation will not occur, or it might lead to unwanted
1634 -Wtautological-undefined-compare and
1635 -Wundefined-bool-conversion
1637 These warn when C++ code is trying to compare 'this' against NULL, while
1638 'this' should never be NULL in well-defined C++ code. However, there is
1639 some legacy (pre C++11) code out there, which actively abuses this
1640 feature, which was less strictly defined in previous C++ versions.
1642 Squid and openjdk do this, for example. The warning can be turned off
1643 for C++98 and earlier, but compiling the code in C++11 mode might result
1644 in unexpected behavior; for example, the parts of the program that are
1645 unreachable could be optimized away.
1648 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1649 kernel sources have been removed. The .h files remain, since some
1650 utilities include them. This will need to be fixed later.
1651 If "mount -t oldnfs ..." is attempted, it will fail.
1652 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1653 the utilities will report errors.
1656 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1657 directories to top level SUBDIR variable when their parent
1658 directory is included in LOCAL_DIRS. Users with build systems with
1659 such hierarchies and without SUBDIR entries in the parent
1660 directory Makefiles should add them or add the directories to
1664 faith(4) and faithd(8) have been removed from the base system. Faith
1665 has been obsolete for a very long time.
1668 vt(4), the new console driver, is enabled by default. It brings
1669 support for Unicode and double-width characters, as well as
1670 support for UEFI and integration with the KMS kernel video
1673 You may need to update your console settings in /etc/rc.conf,
1674 most probably the keymap. During boot, /etc/rc.d/syscons will
1675 indicate what you need to do.
1677 vt(4) still has issues and lacks some features compared to
1678 syscons(4). See the wiki for up-to-date information:
1679 https://wiki.freebsd.org/Newcons
1681 If you want to keep using syscons(4), you can do so by adding
1682 the following line to /boot/loader.conf:
1686 pjdfstest has been integrated into kyua as an opt-in test suite.
1687 Please see share/doc/pjdfstest/README for more details on how to
1691 gperf has been removed from the base system for architectures
1692 that use clang. Ports that require gperf will obtain it from the
1696 pjdfstest has been moved from tools/regression/pjdfstest to
1700 At svn r271982, The default linux compat kernel ABI has been adjusted
1701 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1702 update. If you wish to continue using the linux-f10 compat ports,
1703 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1704 encouraged to update their linux-compat packages to linux-c6 during
1705 their next update cycle.
1708 The ofwfb driver, used to provide a graphics console on PowerPC when
1709 using vt(4), no longer allows mmap() of all physical memory. This
1710 will prevent Xorg on PowerPC with some ATI graphics cards from
1711 initializing properly unless x11-servers/xorg-server is updated to
1715 The xdev targets have been converted to using TARGET and
1716 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1719 The default unbound configuration has been modified to address
1720 issues with reverse lookups on networks that use private
1721 address ranges. If you use the local_unbound service, run
1722 "service local_unbound setup" as root to regenerate your
1723 configuration, then "service local_unbound reload" to load the
1727 The GNU texinfo and GNU info pages are not built and installed
1728 anymore, WITH_INFO knob has been added to allow to built and install
1730 UPDATE: see 20150102 entry on texinfo's removal
1733 The GNU readline library is now an INTERNALLIB - that is, it is
1734 statically linked into consumers (GDB and variants) in the base
1735 system, and the shared library is no longer installed. The
1736 devel/readline port is available for third party software that
1740 The Itanium architecture (ia64) has been removed from the list of
1741 known architectures. This is the first step in the removal of the
1745 Commit r268115 has added NFSv4.1 server support, merged from
1746 projects/nfsv4.1-server. Since this includes changes to the
1747 internal interfaces between the NFS related modules, a full
1748 build of the kernel and modules will be necessary.
1749 __FreeBSD_version has been bumped.
1752 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1753 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1754 which differs from the behaviour controlled by this knob.)
1757 Maximal length of the serial number in CTL was increased from 16 to
1758 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1759 and ctld, need to be rebuilt to work with a new kernel.
1762 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1763 1 respectively to match the upstream numbers. They were out of
1764 sync because, when they were originally added to FreeBSD, the
1765 upstream versions were not respected. These libraries are private
1766 and not yet built by default, so renumbering them should be a
1767 non-issue. However, unclean source trees will yield broken test
1768 programs once the operator executes "make delete-old-libs" after a
1769 "make installworld".
1771 Additionally, the atf-sh binary was made private by moving it into
1772 /usr/libexec/. Already-built shell test programs will keep the
1773 path to the old binary so they will break after "make delete-old"
1776 If you are using WITH_TESTS=yes (not the default), wipe the object
1777 tree and rebuild from scratch to prevent spurious test failures.
1778 This is only needed once: the misnumbered libraries and misplaced
1779 binaries have been added to OptionalObsoleteFiles.inc so they will
1780 be removed during a clean upgrade.
1783 Clang and llvm have been upgraded to 3.4.1 release.
1786 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1787 be removed to avoid issues in the future (and has been added to
1791 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1792 past, it affected all builds that used the bsd.*.mk files. The old
1793 behavior was a bug, but people may have relied upon it. To get this
1794 behavior back, you can .include /etc/src.conf from /etc/make.conf
1795 (which is still global and isn't changed). This also changes the
1796 behavior of incremental builds inside the tree of individual
1797 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1798 Although this has survived make universe and some upgrade scenarios,
1799 other upgrade scenarios may have broken. At least one form of
1800 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1801 as well... In cases where MAKESYSPATH isn't working with this
1802 setting, you'll need to set it to the full path to your tree.
1804 One side effect of all this cleaning up is that bsd.compiler.mk
1805 is no longer implicitly included by bsd.own.mk. If you wish to
1806 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1810 The lindev device has been removed since /dev/full has been made a
1811 standard device. __FreeBSD_version has been bumped.
1814 The knob WITHOUT_VI was added to the base system, which controls
1815 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1816 in order to reorder files share/termcap and didn't build ex(1) as a
1817 build tool, so building/installing with WITH_VI is highly advised for
1818 build hosts for older releases.
1820 This issue has been fixed in stable/9 and stable/10 in r277022 and
1821 r276991, respectively.
1824 The YES_HESIOD knob has been removed. It has been obsolete for
1825 a decade. Please move to using WITH_HESIOD instead or your builds
1826 will silently lack HESIOD.
1829 The uart(4) driver has been changed with respect to its handling
1830 of the low-level console. Previously the uart(4) driver prevented
1831 any process from changing the baudrate or the CLOCAL and HUPCL
1832 control flags. By removing the restrictions, operators can make
1833 changes to the serial console port without having to reboot.
1834 However, when getty(8) is started on the serial device that is
1835 associated with the low-level console, a misconfigured terminal
1836 line in /etc/ttys will now have a real impact.
1837 Before upgrading the kernel, make sure that /etc/ttys has the
1838 serial console device configured as 3wire without baudrate to
1839 preserve the previous behaviour. E.g:
1840 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1843 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1844 to improve performance. To re-enable it, if needed, run rpcbind
1845 with command line option -W.
1848 Switched back to the GPL dtc compiler due to updates in the upstream
1849 dts files not being supported by the BSDL dtc compiler. You will need
1850 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1851 may result while building dtb files during a kernel build if you fail
1852 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1855 Clang and llvm have been upgraded to 3.4 release.
1858 The nve(4) driver has been removed. Please use the nfe(4) driver
1859 for NVIDIA nForce MCP Ethernet adapters instead.
1862 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1863 This could cause certain C++ applications using shared libraries built
1864 against the previous version of libc++ to crash. The incompatibility
1865 has now been fixed, but any C++ applications or shared libraries built
1866 between r261283 and r261801 should be recompiled.
1869 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1870 capability mode support. Please note that enabling the feature in
1871 kernel is still highly recommended.
1874 OpenSSH is now built with sandbox support, and will use sandbox as
1875 the default privilege separation method. This requires Capsicum
1876 capability mode support in kernel.
1879 The libelf and libdwarf libraries have been updated to newer
1880 versions from upstream. Shared library version numbers for
1881 these two libraries were bumped. Any ports or binaries
1882 requiring these two libraries should be recompiled.
1883 __FreeBSD_version is bumped to 1100006.
1886 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1887 instead of providing an explicit one, this would prevent such
1888 Makefile from providing its own Kyuafile in the future during
1889 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1890 intervention is needed to clean an objdir if you use NO_CLEAN:
1891 # find /usr/obj -name Kyuafile | xargs rm -f
1894 The behavior of gss_pseudo_random() for the krb5 mechanism
1895 has changed, for applications requesting a longer random string
1896 than produced by the underlying enctype's pseudo-random() function.
1897 In particular, the random string produced from a session key of
1898 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1899 be different at the 17th octet and later, after this change.
1900 The counter used in the PRF+ construction is now encoded as a
1901 big-endian integer in accordance with RFC 4402.
1902 __FreeBSD_version is bumped to 1100004.
1905 The WITHOUT_ATF build knob has been removed and its functionality
1906 has been subsumed into the more generic WITHOUT_TESTS. If you were
1907 using the former to disable the build of the ATF libraries, you
1908 should change your settings to use the latter.
1911 The default version of mtree is nmtree which is obtained from
1912 NetBSD. The output is generally the same, but may vary
1913 slightly. If you found you need identical output adding
1914 "-F freebsd9" to the command line should do the trick. For the
1915 time being, the old mtree is available as fmtree.
1918 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1919 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1920 1.1.4_8 and verify bsdyml not linked in, before running "make
1922 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1924 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1927 The stable/10 branch has been created in subversion from head
1934 Avoid using make -j when upgrading. While generally safe, there are
1935 sometimes problems using -j to upgrade. If your upgrade fails with
1936 -j, please try again without -j. From time to time in the past there
1937 have been problems using -j with buildworld and/or installworld. This
1938 is especially true when upgrading between "distant" versions (eg one
1939 that cross a major release boundary or several minor releases, or when
1940 several months have passed on the -current branch).
1942 Sometimes, obscure build problems are the result of environment
1943 poisoning. This can happen because the make utility reads its
1944 environment when searching for values for global variables. To run
1945 your build attempts in an "environmental clean room", prefix all make
1946 commands with 'env -i '. See the env(1) manual page for more details.
1948 When upgrading from one major version to another it is generally best to
1949 upgrade to the latest code in the currently installed branch first, then
1950 do an upgrade to the new branch. This is the best-tested upgrade path,
1951 and has the highest probability of being successful. Please try this
1952 approach if you encounter problems with a major version upgrade. Since
1953 the stable 4.x branch point, one has generally been able to upgrade from
1954 anywhere in the most recent stable branch to head / current (or even the
1955 last couple of stable branches). See the top of this file when there's
1958 When upgrading a live system, having a root shell around before
1959 installing anything can help undo problems. Not having a root shell
1960 around can lead to problems if pam has changed too much from your
1961 starting point to allow continued authentication after the upgrade.
1963 This file should be read as a log of events. When a later event changes
1964 information of a prior event, the prior event should not be deleted.
1965 Instead, a pointer to the entry with the new information should be
1966 placed in the old entry. Readers of this file should also sanity check
1967 older entries before relying on them blindly. Authors of new entries
1968 should write them with this in mind.
1972 When upgrading the boot ZFS pool to a new version, always follow
1975 1.) recompile and reinstall the ZFS boot loader and boot block
1976 (this is part of "make buildworld" and "make installworld")
1978 2.) update the ZFS boot block on your boot drive
1980 The following example updates the ZFS boot block on the first
1981 partition (freebsd-boot) of a GPT partitioned drive ada0:
1982 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1984 Non-boot pools do not need these updates.
1988 If you are updating from a prior version of FreeBSD (even one just
1989 a few days old), you should follow this procedure. It is the most
1990 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1992 make kernel-toolchain
1993 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1994 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1996 To test a kernel once
1997 ---------------------
1998 If you just want to boot a kernel once (because you are not sure
1999 if it works, or if you want to boot a known bad kernel to provide
2000 debugging information) run
2001 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2002 nextboot -k testkernel
2004 To rebuild everything and install it on the current system.
2005 -----------------------------------------------------------
2006 # Note: sometimes if you are running current you gotta do more than
2007 # is listed here if you are upgrading from a really old current.
2009 <make sure you have good level 0 dumps>
2011 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2012 make installkernel KERNCONF=YOUR_KERNEL_HERE
2014 <reboot in single user> [3]
2021 To cross-install current onto a separate partition
2022 --------------------------------------------------
2023 # In this approach we use a separate partition to hold
2024 # current's root, 'usr', and 'var' directories. A partition
2025 # holding "/", "/usr" and "/var" should be about 2GB in
2028 <make sure you have good level 0 dumps>
2031 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2032 <maybe newfs current's root partition>
2033 <mount current's root partition on directory ${CURRENT_ROOT}>
2034 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2035 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2036 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2037 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2038 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2039 <reboot into current>
2040 <do a "native" rebuild/install as described in the previous section>
2041 <maybe install compatibility libraries from ports/misc/compat*>
2045 To upgrade in-place from stable to current
2046 ----------------------------------------------
2047 <make sure you have good level 0 dumps>
2049 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2050 make installkernel KERNCONF=YOUR_KERNEL_HERE
2052 <reboot in single user> [3]
2059 Make sure that you've read the UPDATING file to understand the
2060 tweaks to various things you need. At this point in the life
2061 cycle of current, things change often and you are on your own
2062 to cope. The defaults can also change, so please read ALL of
2063 the UPDATING entries.
2065 Also, if you are tracking -current, you must be subscribed to
2066 freebsd-current@freebsd.org. Make sure that before you update
2067 your sources that you have read and understood all the recent
2068 messages there. If in doubt, please track -stable which has
2069 much fewer pitfalls.
2071 [1] If you have third party modules, such as vmware, you
2072 should disable them at this point so they don't crash your
2075 [3] From the bootblocks, boot -s, and then do
2080 adjkerntz -i # if CMOS is wall time
2081 Also, when doing a major release upgrade, it is required that
2082 you boot into single user mode to do the installworld.
2084 [4] Note: This step is non-optional. Failure to do this step
2085 can result in a significant reduction in the functionality of the
2086 system. Attempting to do it by hand is not recommended and those
2087 that pursue this avenue should read this file carefully, as well
2088 as the archives of freebsd-current and freebsd-hackers mailing lists
2089 for potential gotchas. The -U option is also useful to consider.
2090 See mergemaster(8) for more information.
2092 [5] Usually this step is a no-op. However, from time to time
2093 you may need to do this if you get unknown user in the following
2094 step. It never hurts to do it all the time. You may need to
2095 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2096 install) after the buildworld before this step if you last updated
2097 from current before 20130425 or from -stable before 20130430.
2099 [6] This only deletes old files and directories. Old libraries
2100 can be deleted by "make delete-old-libs", but you have to make
2101 sure that no program is using those libraries anymore.
2103 [8] The new kernel must be able to run existing binaries used by
2104 an installworld. When upgrading across major versions, the new
2105 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2106 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2107 binaries). Failure to do so may leave you with a system that is
2108 hard to boot to recover. A GENERIC kernel will include suitable
2109 compatibility options to run binaries from older branches.
2111 Make sure that you merge any new devices from GENERIC since the
2112 last time you updated your kernel config file.
2114 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2115 "?=" instead of the "=" assignment operator, so that buildworld can
2116 override the CPUTYPE if it needs to.
2118 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2119 not on the command line, or in /etc/make.conf. buildworld will
2120 warn if it is improperly defined.
2123 This file contains a list, in reverse chronological order, of major
2124 breakages in tracking -current. It is not guaranteed to be a complete
2125 list of such breakages, and only contains entries since September 23, 2011.
2126 If you need to see UPDATING entries from before that date, you will need
2127 to fetch an UPDATING file from an older FreeBSD release.
2129 Copyright information:
2131 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2133 Redistribution, publication, translation and use, with or without
2134 modification, in full or in part, in any form or format of this
2135 document are permitted without further permission from the author.
2137 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2138 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2139 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2140 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2141 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2142 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2143 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2144 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2145 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2146 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2147 POSSIBILITY OF SUCH DAMAGE.
2149 Contact Warner Losh if you have any questions about your use of