1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://docs.freebsd.org/en/books/handbook/cutting-edge/#makeworld
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 TO PEOPLE WHO THINK THAT FreeBSD 14.x IS SLOW:
16 FreeBSD 14.x has many debugging features turned on, in both the kernel
17 and userland. These features attempt to detect incorrect use of
18 system primitives, and encourage loud failure through extra sanity
19 checking and fail stop semantics. They also substantially impact
20 system performance. If you want to do performance measurement,
21 benchmarking, and optimization, you'll want to turn them off. This
22 includes various WITNESS- related kernel options, INVARIANTS, malloc
23 debugging flags in userland, and various verbose features in the
24 kernel. Many developers choose to disable these features on build
25 machines to maximize performance. (To completely disable malloc
26 debugging, define WITH_MALLOC_PRODUCTION in /etc/src.conf and rebuild
27 world, or to merely disable the most expensive debugging functionality
28 at runtime, run "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
31 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
32 by default. Users can enable kernel TLS via the "KTLS" SSL
33 option. This can be enabled globally by using a custom
34 OpenSSL config file via OPENSSL_CONF or via an
35 application-specific configuration option for applications
36 which permit setting SSL options via SSL_CONF_cmd(3).
39 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
40 modules. Therefore, all need to be rebuilt from sources.
43 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
44 As of be70c7a50d32 it is no longer used by userspace, but it does mean
45 users may not be able to enumerate pf states if they update the kernel
46 past b69019c14cd8 without first updating userspace past be70c7a50d32.
49 As of commit 01ad0c007964 if_bridge member interfaces can no longer
50 change their MTU. Changing the MTU of the bridge itself will change the
51 MTU on all member interfaces instead.
54 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
55 and nfsd modules. Therefore, both need to be rebuilt from sources.
56 Bump __FreeBSD_version to 1400026 for this KAPI change.
59 The 20210707 awk update brought in a change in behavior. This has
60 been corrected as of d4d252c49976. Between these dates, if you
61 installed a new awk binary, you may not be able to build a new
62 kernel because the change in behavior affected the genoffset
63 script used to build the kernel. If you did update, the fix is
64 to update your sources past the above hash and do
67 % sudo -E make install
68 to enable building kernels again.
71 Commit 1e0a518d6548 changed the internal KAPI between the NFS
72 modules. They all need to be rebuilt from sources. I did not
73 bump __FreeBSD_version, since it was bumped recently.
76 awk has been updated to the latest one-true-awk version 20210215.
77 This contains a number of minor bug fixes.
80 The NFSv4 client now uses the highest minor version of NFSv4
81 supported by the NFSv4 server by default instead of minor version 0,
83 The "minorversion" mount option may be used to override this default.
86 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
87 Most notably netdev.h can change now as the (last) dependencies
88 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
92 The directory "blacklisted" under /usr/share/certs/ has been
93 renamed to "untrusted".
96 svnlite has been removed from base. Should you need svn for any reason
97 please install the svn package or port.
100 Commit e1a907a25cfa changed the internal KAPI between the krpc
101 and nfsserver. As such, both modules must be rebuilt from
102 sources. Bump __FreeBSD_version to 1400022.
105 The an(4) driver has been removed from FreeBSD.
108 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
109 start tracking OpenZFS upstream more closely. Please see
110 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
111 for details on how to correct any errors that might result. The
112 short version is that you need to remove the old branch locally:
113 git update-ref -d refs/remotes/freebsd/vendor/openzfs
114 (assuming your upstream origin is named 'freebsd').
117 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
118 which break drm-kmod. In addition various other additions where
119 comitted. Bump __FreeBSD_version to 1400015 to be able to detect this.
122 Commit ca179c4d74f2 changed the package in which the OpenSSL
123 libraries and utilities are packaged.
124 It is recommended for pkgbase user to do:
125 pkg install -f FreeBSD-openssl
126 before pkg upgrade otherwise some dependencies might not be met
127 and pkg will stop working as libssl will not be present anymore
131 Commit 875977314881 changed the internal KAPI between
132 the nfsd and nfscommon modules. As such these modules
133 need to be rebuilt from sources.
134 Without this patch in your NFSv4.1/4.2 server, enabling
135 delegations by setting vfs.nfsd.issue_delegations non-zero
139 Commit 7763814fc9c2 changed the internal KAPI between
140 the krpc and NFS. As such, the krpc, nfscommon and
141 nfscl modules must all be rebuilt from sources.
142 Without this patch, NFSv4.1/4.2 mounts should not
143 be done with the nfscbd(8) daemon running, to avoid
144 needing a working back channel for server->client RPCs.
147 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
148 handles binding of the back channel as required by RFC5661.
149 Until this patch is in your server, avoid use of the "nconnects"
150 mount option for Linux NFSv4.1/4.2 mounts.
153 For 64-bit architectures the base system is now built with Position
154 Independent Executable (PIE) support enabled by default. It may be
155 disabled using the WITHOUT_PIE knob. A clean build is required.
158 Various LinuxKPI functionality was added which conflicts with DRM.
159 Please update your drm-kmod port to after the __FreeBSD_verison 1400003
163 PC Card attachments for all devices have been removed. In the case of
164 wi and cmx, the entire drivers were removed because they were only
165 PC Card devices. FreeBSD_version 1300134 should be used for this
166 since it was bumped so recently.
169 Transport-independent parts of HID support have been split off the USB
170 code in to separate subsystem. Kernel configs which include one of
171 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
172 be updated with adding of "device hid" line.
175 ncurses installation has been modified to only keep the widechar
176 enabled version. Incremental build is broken for that change, so it
177 requires a clean build.
180 The FreeBSD project has migrated from Subversion to Git. Temporary
181 instructions can be found at
182 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
183 and other documents in that repo.
186 The services database has been updated to cover more of the basic
187 services expected in a modern system. The database is big enough
188 that it will cause issues in mergemaster in Releases previous to
189 12.2 and 11.3, or in very old current systems from before r358154.
192 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
193 may be installed from ports or packages.
196 ping6 has been merged into ping. It can now be called as "ping -6".
197 See ping(8) for details.
200 Default value of net.add_addr_allfibs has been changed to 0.
201 If you have multi-fib configuration and rely on existence of all
202 interface routes in every fib, you need to set the above sysctl to 1.
205 The internal pre-processor in the calendar(1) program has been
206 extended to support more C pre-processor commands (e.g. #ifdef, #else,
207 and #undef) and to detect unbalanced conditional statements.
208 Error messages have been extended to include the filename and line
209 number if processing stops to help fixing malformed data files.
212 All the data files for the calendar(1) program, except calendar.freebsd,
213 have been moved to the deskutils/calendar-data port, much like the
214 jewish calendar entries were moved to deskutils/hebcal years ago. After
215 make delete-old-files, you need to install it to retain full
216 functionality. calendar(1) will issue a reminder for files it can't
220 LINT files are no longer generated. We now include the relevant NOTES
221 files. Note: This may cause conflicts with updating in some cases.
222 find sys -name LINT\* -delete
223 is suggested across this commit to remove the generated LINT files.
225 If you have tried to update with generated files there, the svn
226 command you want to un-auger the tree is
229 and then do the above find from the top level. Substitute 'amd64'
230 above with where the error message indicates a conflict.
233 OpenZFS support has been integrated. Do not upgrade root pools until
234 the loader is updated to support zstd. Furthermore, we caution against
235 'zpool upgrade' for the next few weeks. The change should be transparent
236 unless you want to use new features.
238 Not all "NO_CLEAN" build scenarios work across these changes. Many
239 scenarios have been tested and fixed, but rebuilding kernels without
240 rebuilding world may fail.
242 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
243 upstream default. A fallback to /boot has been added for mountroot.
245 Pool auto import behavior at boot has been moved from the kernel module
246 to an explicit "zpool import -a" in one of the rc scripts enabled by
247 zfs_enable=YES. This means your non-root zpools won't auto import until
248 you upgrade your /etc/rc.d files.
251 The resume code now notifies devd with the 'kernel' system
252 rather than the old 'kern' subsystem to be consistent with
253 other use. The old notification will be created as well, but
254 will be removed prior to FreeBSD 14.0.
257 r362275 changed the internal API between the kernel RPC and the
258 NFS modules. As such, all the modules must be recompiled from
262 r364330 modified the internal API used between the NFS modules.
263 As such, all the NFS modules must be re-compiled from sources.
266 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
267 been upgraded to 11.0.0. Please see the 20141231 entry below for
268 information about prerequisites and upgrading, if you are not already
269 using clang 3.5.0 or higher.
272 r364092 modified the internal ABI used between the kernel NFS
273 modules. As such, all of these modules need to be rebuilt
274 from sources, so a version bump was done.
277 Makefile.inc has been updated to work around the issue documented in
278 20200729. It was a case where the optimization of using symbolic links
279 to point to binaries created a situation where we'd run new binaries
280 with old libraries starting midway through the installworld process.
283 r363679 has redefined some undefined behavior in regcomp(3); notably,
284 extraneous escapes of most ordinary characters will no longer be
285 accepted. An exp-run has identified all of the problems with this in
286 ports, but other non-ports software may need extra escapes removed to
287 continue to function.
289 Because of this change, installworld may encounter the following error
290 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
291 you do not halt installworld. Instead, let it run to completion (whether
292 successful or not) and run installworld once more.
295 A new implementation of bc and dc has been imported in r362681. This
296 implementation corrects non-conformant behavior of the previous bc
297 and adds GNU bc compatible options. It offers a number of extensions,
298 is much faster on large values, and has support for message catalogs
299 (a number of languages are already supported, contributions of further
300 languages welcome). The option WITHOUT_GH_BC can be used to build the
301 world with the previous versions of bc and dc.
304 r362639 changed the internal API used between the NFS kernel modules.
305 As such, they all need to be rebuilt from sources.
308 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
309 out of tree file systems need to be modified and rebuilt.
310 Also, any file systems that are modules must be rebuilt.
313 read(2) of a directory fd is now rejected by default. root may
314 re-enable it for system root only on non-ZFS filesystems with the
315 security.bsd.allow_read_dir sysctl(8) MIB if
316 security.bsd.suser_enabled=1.
318 It may be advised to setup aliases for grep to default to `-d skip` if
319 commonly non-recursively grepping a list that includes directories and
320 the potential for the resulting stderr output is not tolerable. Example
321 aliases are now installed, commented out, in /root/.cshrc and
325 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
326 been upgraded to 10.0.1. Please see the 20141231 entry below for
327 information about prerequisites and upgrading, if you are not already
328 using clang 3.5.0 or higher.
331 Support for obsolete compilers has been removed from the build system.
332 Clang 6 and GCC 6.4 are the minimum supported versions.
335 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
336 stub that calls close_range(2). If using a custom kernel configuration,
337 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
338 a slightly older -CURRENT userland and older FreeBSD userlands may not
339 be functional without closefrom(2).
342 Upstream DTS from Linux 5.6 was merged and they now have the SID
343 and THS (Secure ID controller and THermal Sensor) node present.
344 The DTB overlays have now been removed from the tree for the H3/H5 and
345 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
346 deal with upstream DTS. If you are using those overlays you need to
347 remove them from loader.conf and update the DTBs on the FAT partition.
350 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
351 been upgraded to 10.0.0. Please see the 20141231 entry below for
352 information about prerequisites and upgrading, if you are not already
353 using clang 3.5.0 or higher.
356 The amd(8) automount daemon has been removed from the source tree.
357 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
358 amd is still available in the sysutils/am-utils port.
361 Removed brooktree driver (bktr.4) from the tree.
364 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
365 compiler in usr.bin/dtc is used on all architectures which use dtc, and
366 the GPL dtc is available (if needed) from the sysutils/dtc port.
369 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
370 is used by all supported CPU architectures.
373 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
374 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
375 Users who wish to build FreeBSD with GCC must use the external toolchain
379 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
380 has changed, users will have to rebuild all the ports that are linked to
384 The size of struct vnet and the magic cookie have changed.
385 Users need to recompile libkvm and all modules using VIMAGE
386 together with their new kernel.
389 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
390 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
391 your Makefiles and scripts to define MK_<var>=no instead as required.
393 One exception to this is that program or library Makefiles should
394 define MAN to empty rather than setting MK_MAN=no.
397 Clang/LLVM is now the default compiler and LLD the default
401 make universe no longer uses GCC 4.2.1 on any architectures.
402 Architectures not supported by in-tree Clang/LLVM require an
403 external toolchain package.
406 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
407 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
408 options default to off for all supported CPU architectures. As a
409 short-term transition aid they may be enabled via WITH_* options.
410 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
413 Support for armv5 has been disconnected and is being removed. The
414 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
415 You must now use a MACHINE_ARCH of armv6 or armv7. The default
416 MACHINE_ARCH for MACHINE=arm is now armv7.
419 Clang/LLVM is now the default compiler for all powerpc architectures.
420 LLD is now the default linker for powerpc64. The change for powerpc64
421 also includes a change to the ELFv2 ABI, incompatible with the existing
425 Kernel-loadable random(4) modules are no longer unloadable.
428 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
429 been upgraded to 9.0.1. Please see the 20141231 entry below for
430 information about prerequisites and upgrading, if you are not already
431 using clang 3.5.0 or higher.
434 r355677 has modified the internal interface used between the
435 NFS modules in the kernel. As such, they must all be upgraded
436 simultaneously. I will do a version bump for this.
439 The root certificates of the Mozilla CA Certificate Store have been
440 imported into the base system and can be managed with the certctl(8)
441 utility. If you have installed the security/ca_root_nss port or package
442 with the ETCSYMLINK option (the default), be advised that there may be
443 differences between those included in the port and those included in
444 base due to differences in nss branch used as well as general update
445 frequency. Note also that certctl(8) cannot manage certs in the
446 format used by the security/ca_root_nss port.
449 The amd(8) automount daemon has been disabled by default, and will be
450 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
454 The nctgpio and wbwd drivers have been moved to the superio bus.
455 If you have one of these drivers in a kernel configuration, then
456 you should add device superio to it. If you use one of these drivers
457 as a module and you compile a custom set of modules, then you should
458 add superio to the set.
461 KPIs for network drivers to access interface addresses have changed.
462 Users need to recompile NIC driver modules together with kernel.
465 The net.link.tap.user_open sysctl no longer prevents user opening of
466 already created /dev/tapNN devices. Access is still controlled by
467 node permissions, just like tun devices. The net.link.tap.user_open
468 sysctl is now used only to allow users to perform devfs cloning of
469 tap devices, and the subsequent open may not succeed if the user is not
470 in the appropriate group. This sysctl may be deprecated/removed
471 completely in the future.
474 mips, powerpc, and sparc64 are no longer built as part of
475 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
476 not defined, mips, powerpc, and sparc64 builds will look for
477 the xtoolchain binaries and if installed use them for universe
478 builds. As llvm 9.0 becomes vetted for these architectures, they
479 will be removed from the list.
482 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
483 been upgraded to 9.0.0. Please see the 20141231 entry below for
484 information about prerequisites and upgrading, if you are not already
485 using clang 3.5.0 or higher.
488 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
489 GENERIC. They are available as modules and can be loaded by adding
490 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
491 hptnr_load="YES", or hptrr_load="YES", respectively.
494 ntpd no longer by default locks its pages in memory, allowing them
495 to be paged out by the kernel. Use rlimit memlock to restore
496 historic BSD behaviour. For example, add "rlimit memlock 32"
497 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
500 Several of ping6's options have been renamed for better consistency
501 with ping. If you use any of -ARWXaghmrtwx, you must update your
502 scripts. See ping6(8) for details.
505 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
506 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
507 been removed from mount_fusefs(8). You can safely remove them from
508 your scripts, because they had no effect.
510 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
511 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
512 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
513 sysctls have been removed. If you felt the need to set any of them to
514 a non-default value, please tell asomers@FreeBSD.org why.
517 Default permissions on the /var/account/acct file (and copies of it
518 rotated by periodic daily scripts) are changed from 0644 to 0640
519 because the file contains sensitive information that should not be
520 world-readable. If the /var/account directory must be created by
521 rc.d/accounting, the mode used is now 0750. Admins who use the
522 accounting feature are encouraged to change the mode of an existing
523 /var/account directory to 0750 or 0700.
526 Entropy collection and the /dev/random device are no longer optional
527 components. The "device random" option has been removed.
528 Implementations of distilling algorithms can still be made loadable
529 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
532 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
533 been upgraded to 8.0.1. Please see the 20141231 entry below for
534 information about prerequisites and upgrading, if you are not already
535 using clang 3.5.0 or higher.
538 A fix was applied to i386 kernel modules to avoid panics with
539 dpcpu or vnet. Users need to recompile i386 kernel modules
540 having pcpu or vnet sections or they will refuse to load.
543 User-wired pages now have their own counter,
544 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
545 to vm.max_user_wired and changed from an unsigned int to an unsigned
546 long. bhyve VMs wired with the -S are now subject to the user
547 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
548 avoid running into the limit.
551 The IPSEC option has been removed from GENERIC. Users requiring
552 ipsec(4) must now load the ipsec(4) kernel module.
555 The tap(4) driver has been folded into tun(4), and the module has been
556 renamed to tuntap. You should update any kld_list="if_tap" or
557 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
558 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
559 module instead, and "device tap" or "device tun" entries in kernel
560 config files to select the tuntap device instead.
563 The following knobs have been added related to tradeoffs between
564 safe use of the random device and availability in the absence of
567 kern.random.initial_seeding.bypass_before_seeding: tunable; set
568 non-zero to bypass the random device prior to seeding, or zero to
569 block random requests until the random device is initially seeded.
570 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
571 availability properties.
573 kern.random.initial_seeding.read_random_bypassed_before_seeding:
574 read-only diagnostic sysctl that is set when bypass is enabled and
575 read_random(9) is bypassed, to enable programmatic handling of this
576 initial condition, if desired.
578 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
579 Similar to the above, but for for arc4random(9) initial seeding.
581 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
582 non-zero to disable warnings in dmesg when the same conditions are
583 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
584 produce warnings in dmesg when the conditions are met.
587 The loadable random module KPI has changed; the random_infra_init()
588 routine now requires a 3rd function pointer for a bool (*)(void)
589 method that returns true if the random device is seeded (and
590 therefore unblocked).
593 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
594 built from head sources between r320757 (July 6, 2017) and
595 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
596 is added to the command line.
597 nfsuserd daemons built from head sources that are post-r338192 are
598 not affected and should continue to work.
601 The fuse(4) module has been renamed to fusefs(4) for consistency with
602 other filesystems. You should update any kld_load="fuse" entries in
603 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
604 "options FUSE" entries in kernel config files.
607 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
608 8.0.0. Please see the 20141231 entry below for information about
609 prerequisites and upgrading, if you are not already using clang 3.5.0
613 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
614 compiled into your custom kernel, add 'device xz' statement to the
618 drm and drm2 have been removed from the tree. Please see
619 https://wiki.freebsd.org/Graphics for the latest information on
620 migrating to the drm ports.
623 Iflib is no longer unconditionally compiled into the kernel. Drivers
624 using iflib and statically compiled into the kernel, now require
625 the 'device iflib' config option. For the same drivers loaded as
626 modules on kernels not having 'device iflib', the iflib.ko module
627 is loaded automatically.
630 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
631 options no longer exist since r343219 and r343427 respectively;
632 nothing uses them, so they should be just removed from custom
636 r342635 changes the way efibootmgr(8) works by requiring users to add
637 the -b (bootnum) parameter for commands where the bootnum was previously
638 specified with each option. For example 'efibootmgr -B 0001' is now
639 'efibootmgr -B -b 0001'.
642 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
643 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
644 servers that have vfs.nfsd.nfs_privport set will only allow mounts
645 from clients using a reserved port. Since both the FreeBSD and Linux
646 NFSv4 clients use reserved ports by default, this should not affect
650 The XLP config has been removed. We can't support 64-bit atomics in this
651 kernel because it is running in 32-bit mode. XLP users must transition
652 to running a 64-bit kernel (XLP64 or XLPN32).
654 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
655 the preferred emulator today and we don't need two different ones.
657 The old sibyte / swarm / Broadcom BCM1250 support has been
658 removed from the mips port.
661 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
662 7.0.1. Please see the 20141231 entry below for information about
663 prerequisites and upgrading, if you are not already using clang 3.5.0
667 Remove the timed and netdate programs from the base tree. Setting
668 the time with these daemons has been obsolete for over a decade.
671 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
672 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
673 it produces broken binaries when ifuncs are in use. Users needing
674 GNU ld should install the binutils port or package.
677 The BSD crtbegin and crtend code has been enabled by default. It has
678 had extensive testing on amd64, arm64, and i386. It can be disabled
679 by building a world with -DWITHOUT_BSD_CRTBEGIN.
682 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
683 has been converted to a port (misc/ctm) and will be removed from
684 FreeBSD-13. It is available as a package (ctm) for all supported
688 The default newsyslog.conf(5) file has been changed to only include
689 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
690 the filenames end in '.conf' and do not begin with a '.'.
692 You should check the configuration files in these two directories match
693 this naming convention. You can verify which configuration files are
694 being included using the command:
698 Ports for the DRM modules have been simplified. Now, amd64 users should
699 just install the drm-kmod port. All others should install
702 Graphics hardware that's newer than about 2010 usually works with
703 drm-kmod. For hardware older than 2013, however, some users will need
704 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
705 than 2008 usually only works in drm-legacy-kmod. The graphics team can
706 only commit to hardware made since 2013 due to the complexity of the
707 market and difficulty to test all the older cards effectively. If you
708 have hardware supported by drm-kmod, you are strongly encouraged to use
709 that as you will get better support.
711 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
712 elsewhere, the drm and drm2 modules will be eliminated from the src base
713 soon (with a limited exception for arm). Please update to the package
714 asap and report any issues to x11@freebsd.org.
716 Generally, anybody using the drm*-kmod packages should add
717 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
718 cross-threading surprises, especially with automatic driver
719 loading from X11 startup. These will become the defaults in 13-current
723 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
724 custom kernel and module loading configuration files must be updated
725 accordingly. Moreover, interfaces previous presented as ixlvN to the
726 system are now exposed as iavfN and network configuration files must
727 be adjusted as necessary.
730 OpenSSL has been updated to version 1.1.1. This update included
731 additional various API changes throughout the base system. It is
732 important to rebuild third-party software after upgrading. The value
733 of __FreeBSD_version has been bumped accordingly.
736 The legacy DRM modules and drivers have now been added to the loader's
737 module blacklist, in favor of loading them with kld_list in rc.conf(5).
738 The module blacklist may be overridden with the loader.conf(5)
739 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
743 The cam(4) based nda(4) driver will be used over nvd(4) by default on
744 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
745 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
746 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
750 Reproducible build mode is now on by default, in preparation for
751 FreeBSD 12.0. This eliminates build metadata such as the user,
752 host, and time from the kernel (and uname), unless the working tree
753 corresponds to a modified checkout from a version control system.
754 The previous behavior can be obtained by setting the /etc/src.conf
755 knob WITHOUT_REPRODUCIBLE_BUILD.
758 The Yarrow CSPRNG has been removed from the kernel as it has not been
759 supported by its designers since at least 2003. Fortuna has been the
760 default since FreeBSD-11.
763 devctl freeze/thaw have gone into the tree, the rc scripts have been
764 updated to use them and devmatch has been changed. You should update
765 kernel, userland and rc scripts all at the same time.
768 The default interpreter has been switched from 4th to Lua.
769 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
770 interpreter. If you have custom FORTH code you will need to set
771 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
772 src.conf for the build. This will create default hard links between
773 loader and loader_4th instead of loader and loader_lua, the new default.
774 If you are using UEFI it will create the proper hard link to loader.efi.
776 bhyve uses userboot.so. It remains 4th-only until some issues are solved
777 regarding coexisting with multiple versions of FreeBSD are resolved.
780 ls(1) now respects the COLORTERM environment variable used in other
781 systems and software to indicate that a colored terminal is both
782 supported and desired. If ls(1) is suddenly emitting colors, they may
783 be disabled again by either removing the unwanted COLORTERM from your
784 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
785 may not be observed in a future release.
788 The default pager for most commands has been changed to "less". To
789 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
793 The jedec_ts(4) driver has been removed. A superset of its functionality
794 is available in the jedec_dimm(4) driver, and the manpage for that
795 driver includes migration instructions. If you have "device jedec_ts"
796 in your kernel configuration file, it must be removed.
799 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
800 This should have no effect if the kernel is booted via BIOS/legacy boot.
801 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
802 has a buggy firmware that prevents a successful boot due to use of
806 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
807 support has been removed from the tree. These ports were
808 obsolete and/or known to be broken for many years.
811 loader.efi has been augmented to participate more fully in the
812 UEFI boot manager protocol. loader.efi will now look at the
813 BootXXXX environment variable to determine if a specific kernel
814 or root partition was specified. XXXX is derived from BootCurrent.
815 efibootmgr(8) manages these standard UEFI variables.
818 zfsloader's functionality has now been folded into loader.
819 zfsloader is no longer necessary once you've updated your
820 boot blocks. For a transition period, we will install a
821 hardlink for zfsloader to loader to allow a smooth transition
822 until the boot blocks can be updated (hard link because old
823 zfs boot blocks don't understand symlinks).
826 ARM64 now have efifb support, if you want to have serial console
827 on your arm64 board when an screen is connected and the bootloader
828 setup a frame buffer for us to use, just add :
832 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
833 an screen connected as the firmware will setup a frame buffer are that
834 u-boot will expose as an EFI frame buffer.
837 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
838 or take steps to update /etc/passwd before doing installworld on
839 existing systems. Do not skip the "mergemaster -Fp" step before
840 installworld, as described in the update procedures near the bottom
841 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
842 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
843 the ntp config file contain options that change file/dir locations.
844 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
845 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
846 taking steps to ensure that all required files/dirs are accessible
850 Big endian arm support has been removed.
853 The static environment setup in kernel configs is no longer mutually
854 exclusive with the loader(8) environment by default. In order to
855 restore the previous default behavior of disabling the loader(8)
856 environment if a static environment is present, you must specify
857 loader_env.disabled=1 in the static environment.
860 The ABI of syscalls used by management tools like sockstat and
861 netstat has been broken to allow 32-bit binaries to work on
862 64-bit kernels without modification. These programs will need
863 to match the kernel in order to function. External programs may
864 require minor modifications to accommodate a change of type in
865 structures from pointers to 64-bit virtual addresses.
868 On i386 and amd64 atomics are now inlined. Out of tree modules using
869 atomics will need to be rebuilt.
872 The '%I' format in the kern.corefile sysctl limits the number of
873 core files that a process can generate to the number stored in the
874 debug.ncores sysctl. The '%I' format is replaced by the single digit
875 index. Previously, if all indexes were taken the kernel would overwrite
876 only a core file with the highest index in a filename.
877 Currently the system will create a new core file if there is a free
878 index or if all slots are taken it will overwrite the oldest one.
881 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
882 6.0.1. Please see the 20141231 entry below for information about
883 prerequisites and upgrading, if you are not already using clang 3.5.0
887 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
888 needed to be changed to work with it. This change was made with r335763
889 and requires a mergemaster / etcupdate / etc to update the installed
893 r334930 changed the interface between the NFS modules, so they all
894 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
897 As of r334391 lld is the default amd64 system linker; it is installed
898 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
902 The kernel / userland interface for devinfo changed, so you'll
903 need a new kernel and userland as a pair for it to work (rebuilding
904 lib/libdevinfo is all that's required). devinfo and devmatch will
905 not work, but everything else will when there's a mismatch.
908 The on-disk format for hwpmc callchain records has changed to include
909 threadid corresponding to a given record. This changes the field offsets
910 and thus requires that libpmcstat be rebuilt before using a kernel
914 The vxge(4) driver has been removed. This driver was introduced into
915 HEAD one week before the Exar left the Ethernet market and is not
916 known to be used. If you have device vxge in your kernel config file
920 The amd64 kernel now requires a ld that supports ifunc to produce a
921 working kernel, either lld or a newer binutils. lld is built by default
922 on amd64, and the 'buildkernel' target uses it automatically. However,
923 it is not the default linker, so building the kernel the traditional
924 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
925 binutils port/package). lld will soon be default, and this requirement
928 NOTE: As of r334391 lld is the default system linker on amd64, and no
929 workaround is necessary.
932 The nxge(4) driver has been removed. This driver was for PCI-X 10g
933 cards made by s2io/Neterion. The company was acquired by Exar and
934 no longer sells or supports Ethernet products. If you have device
935 nxge in your kernel config file it must be removed.
938 The tz database (tzdb) has been updated to 2018e. This version more
939 correctly models time stamps in time zones with negative DST such as
940 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
941 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
942 time zone abbreviations and the tm_isdst flag.
945 The ixgb(4) driver has been removed. This driver was for an early and
946 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
947 quickly shifted to the long lived ixgbe family. If you have device
948 ixgb in your kernel config file it must be removed.
951 The lmc(4) driver has been removed. This was a WAN interface
952 card that was already reportedly rare in 2003, and had an ambiguous
953 license. If you have device lmc in your kernel config file it must
957 Support for Arcnet networks has been removed. If you have device
958 arcnet or device cm in your kernel config file they must be
962 Support for FDDI networks has been removed. If you have device
963 fddi or device fpa in your kernel config file they must be
967 In addition to supporting RFC 3164 formatted messages, the
968 syslogd(8) service is now capable of parsing RFC 5424 formatted
969 log messages. The main benefit of using RFC 5424 is that clients
970 may now send log messages with timestamps containing year numbers,
971 microseconds and time zone offsets.
973 Similarly, the syslog(3) C library function has been altered to
974 send RFC 5424 formatted messages to the local system logging
975 daemon. On systems using syslogd(8), this change should have no
976 negative impact, as long as syslogd(8) and the C library are
977 updated at the same time. On systems using a different system
978 logging daemon, it may be necessary to make configuration
979 adjustments, depending on the software used.
981 When using syslog-ng, add the 'syslog-protocol' flag to local
982 input sources to enable parsing of RFC 5424 formatted messages:
985 unix-dgram("/var/run/log" flags(syslog-protocol));
988 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
989 of the 'imuxsock' module to let messages be processed by the
990 regular RFC 3164/5424 parsing pipeline:
992 module(load="imuxsock" SysSock.UseSpecialParser="off")
994 Do note that these changes only affect communication between local
995 applications and syslogd(8). The format that syslogd(8) uses to
996 store messages on disk or forward messages to other systems
997 remains unchanged. syslogd(8) still uses RFC 3164 for these
998 purposes. Options to customize this behaviour will be added in the
999 future. Utilities that process log files stored in /var/log are
1000 thus expected to continue to function as before.
1002 __FreeBSD_version has been incremented to 1200061 to denote this
1006 Support for token ring networks has been removed. If you
1007 have "device token" in your kernel config you should remove
1008 it. No device drivers supported token ring.
1011 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1012 entries as EFI instead of overloading the i386 tag as done previously.
1013 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1014 release was updated to use this. This may mean that makefs must be
1015 updated before "make cdrom" can be run in the release directory. This
1016 should be as simple as:
1018 $ cd $SRCDIR/usr.sbin/makefs
1019 $ make depend all install
1022 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1023 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1024 Co-existence for the transition period will come shortly. Booting is a
1025 complex environment and test coverage for Lua-enabled loaders has been
1026 thin, so it would be prudent to assume it might not work and make
1027 provisions for backup boot methods.
1030 devmatch functionality has been turned on in devd. It will automatically
1031 load drivers for unattached devices. This may cause unexpected drivers
1032 to be loaded. Please report any problems to current@ and
1036 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1037 6.0.0. Please see the 20141231 entry below for information about
1038 prerequisites and upgrading, if you are not already using clang 3.5.0
1042 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1043 This means it is used to link the kernel and userland libraries and
1044 executables, but is not yet installed as /usr/bin/ld by default.
1046 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1047 WITHOUT_LLD_BOOTSTRAP=yes
1050 On i386, pmtimer has been removed. Its functionality has been folded
1051 into apm. It was a no-op on ACPI in current for a while now (but was
1052 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1053 remove it from kernel config files.
1056 The use of RSS hash from the network card aka flowid has been
1057 disabled by default for lagg(4) as it's currently incompatible with
1058 the lacp and loadbalance protocols.
1060 This can be re-enabled by setting the following in loader.conf:
1061 net.link.lagg.default_use_flowid="1"
1064 The SW_WATCHDOG option is no longer necessary to enable the
1065 hardclock-based software watchdog if no hardware watchdog is
1066 configured. As before, SW_WATCHDOG will cause the software
1067 watchdog to be enabled even if a hardware watchdog is configured.
1070 r326887 fixes the issue described in the 20171214 UPDATING entry.
1071 r326888 flips the switch back to building GELI support always.
1074 r362593 broke ZFS + GELI support for reasons unknown. However,
1075 it also broke ZFS support generally, so GELI has been turned off
1076 by default as the lesser evil in r326857. If you boot off ZFS and/or
1077 GELI, it might not be a good time to update.
1080 PowerPC users must update loader(8) by rebuilding world before
1081 installing a new kernel, as the protocol connecting them has
1082 changed. Without the update, loader metadata will not be passed
1083 successfully to the kernel and users will have to enter their
1084 root partition at the kernel mountroot prompt to continue booting.
1085 Newer versions of loader can boot old kernels without issue.
1088 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1089 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1090 to WITH/OUT_LOADER_GELI.
1093 The naive and non-compliant support of posix_fallocate(2) in ZFS
1094 has been removed as of r325320. The system call now returns EINVAL
1095 when used on a ZFS file. Although the new behavior complies with the
1096 standard, some consumers are not prepared to cope with it.
1097 One known victim is lld prior to r325420.
1100 Building in a FreeBSD src checkout will automatically create object
1101 directories now rather than store files in the current directory if
1102 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1103 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1104 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1108 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1109 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1110 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1111 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1112 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1113 The UNIFIED_OBJDIR option is a transitional feature that will be
1114 removed for 12.0 release; please migrate to the new format for any
1115 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1116 than hardcoding paths.
1119 The native-xtools target no longer installs the files by default to the
1120 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1121 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1124 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1125 options are changing from controlling the build if defined / undefined
1126 to controlling the build with explicit 'yes' or 'no' values. They will
1127 shift to WITH/WITHOUT options to match other options in the system.
1130 libstand has turned into a private library for sys/boot use only.
1131 It is no longer supported as a public interface outside of sys/boot.
1134 The arm port has split armv6 into armv6 and armv7. armv7 is now
1135 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1136 and are running a kernel from before r324363, you will need to add
1137 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1140 When building multiple kernels using KERNCONF, non-existent KERNCONF
1141 files will produce an error and buildkernel will fail. Previously
1142 missing KERNCONF files silently failed giving no indication as to
1143 why, only to subsequently discover during installkernel that the
1144 desired kernel was never built in the first place.
1147 The default serial number format for CTL LUNs has changed. This will
1148 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1149 or iSCSI clients care about their LUNs' serial numbers. Users who
1150 require serial number stability should hardcode serial numbers in
1154 For 32-bit arm compiled for hard-float support, soft-floating point
1155 binaries now always get their shared libraries from
1156 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1157 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1158 soft-float everything else should be affected.
1161 The geli password typed at boot is now hidden. To restore the previous
1162 behavior, see geli(8) for configuration options.
1165 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1166 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1170 "make check" behavior (made in ^/head@r295380) has been changed to
1171 execute from a limited sandbox, as opposed to executing from
1175 - The "beforecheck" and "aftercheck" targets are now specified.
1176 - ${CHECKDIR} (added in commit noted above) has been removed.
1177 - Legacy behavior can be enabled by setting
1178 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1180 If the limited sandbox mode is enabled, "make check" will execute
1181 "make distribution", then install, execute the tests, and clean up the
1182 sandbox if successful.
1184 The "make distribution" and "make install" targets are typically run as
1185 root to set appropriate permissions and ownership at installation time.
1186 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1187 environment if executing "make check" with limited sandbox mode using
1188 an unprivileged user.
1191 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1192 unable to automatically find alternate superblocks. As of r322297,
1193 the information needed to find alternate superblocks has been
1194 moved to the end of the area reserved for the boot block.
1195 Filesystems created with a newfs of this vintage or later
1196 will create the recovery information. If you have a filesystem
1197 created prior to this change and wish to have a recovery block
1198 created for your filesystem, you can do so by running fsck in
1199 foreground mode (i.e., do not use the -p or -y options). As it
1200 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1201 to which you should answer yes.
1204 As of r321665, an NFSv4 server configuration that services
1205 Kerberos mounts or clients that do not support the uid/gid in
1206 owner/owner_group string capability, must explicitly enable
1207 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1208 machine's /etc/rc.conf file.
1211 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1212 Please see the 20141231 entry below for information about prerequisites
1213 and upgrading, if you are not already using clang 3.5.0 or higher.
1216 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1217 r-commands (rlogin, rsh, etc.) to be built with the base system.
1220 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1221 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1222 be careful when performing source upgrades. It is best to run
1223 'make installworld' from an alternate root system, either a live
1224 CD/memory stick, or a temporary root partition. Additionally, all ports
1225 must be recompiled. powerpc64 is largely unaffected, except in the case
1226 of 32-bit compatibility. All 32-bit binaries will be affected.
1229 Forward compatibility for the "ino64" project have been committed. This
1230 will allow most new binaries to run on older kernels in a limited
1231 fashion. This prevents many of the common foot-shooting actions in the
1232 upgrade as well as the limited ability to roll back the kernel across
1233 the ino64 upgrade. Complicated use cases may not work properly, though
1234 enough simpler ones work to allow recovery in most situations.
1237 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1238 if you require the GPL compiler.
1241 The internal ABI used for communication between the NFS kernel modules
1242 was changed by r320085, so __FreeBSD_version was bumped to
1243 ensure all the NFS related modules are updated together.
1246 The ABI of struct event was changed by extending the data
1247 member to 64bit and adding ext fields. For upgrade, same
1248 precautions as for the entry 20170523 "ino64" must be
1252 The GNU roff toolchain has been removed from base. To render manpages
1253 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1254 from ports (and recommends to install it).
1255 To render roff(7) documents, consider using GNU roff from ports or the
1256 heirloom doctools roff toolchain from ports via pkg install groff or
1257 via pkg install heirloom-doctools.
1260 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1261 smaller runtime footprint builds. This is useful for embedded systems
1262 which only require one chipset support.
1264 If you load it as a module, make sure this is in /boot/loader.conf:
1268 This will load the HAL, all chip/RF backends and if_ath_pci.
1269 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1270 if_ath or it will not load any HAL chipset support.
1272 If you want to selectively load things (eg on cheaper ARM/MIPS
1273 platforms where RAM is at a premium) you should:
1276 * load the chip modules in question
1277 * load ath_rate, ath_dfs
1279 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1280 bus bind type - this is where probe/attach is done.
1282 For further comments/feedback, poke adrian@ .
1285 The "ino64" 64-bit inode project has been committed, which extends
1286 a number of types to 64 bits. Upgrading in place requires care and
1287 adherence to the documented upgrade procedure.
1289 If using a custom kernel configuration ensure that the
1290 COMPAT_FREEBSD11 option is included (as during the upgrade the
1291 system will be running the ino64 kernel with the existing world).
1293 For the safest in-place upgrade begin by removing previous build
1294 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1295 procedure documented below under the heading "To rebuild everything and
1296 install it on the current system." Specifically, a reboot is required
1297 after installing the new kernel before installing world. While an
1298 installworld normally works by accident from multiuser after rebooting
1299 the proper kernel, there are many cases where this will fail across this
1300 upgrade and installworld from single user is required.
1303 The NATM framework including the en(4), fatm(4), hatm(4), and
1304 patm(4) devices has been removed. Consumers should plan a
1305 migration before the end-of-life date for FreeBSD 11.
1308 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1309 diff has not been implemented, if those are needed a newer version of
1310 GNU diff is available via the diffutils package under the gdiff name.
1313 As of r316810 for ipfilter, keep frags is no longer assumed when
1314 keep state is specified in a rule. r316810 aligns ipfilter with
1315 documentation in man pages separating keep frags from keep state.
1316 This allows keep state to be specified without forcing keep frags
1317 and allows keep frags to be specified independently of keep state.
1318 To maintain previous behaviour, also specify keep frags with
1319 keep state (as documented in ipf.conf.5).
1322 arm64 builds now use the base system LLD 4.0.0 linker by default,
1323 instead of requiring that the aarch64-binutils port or package be
1324 installed. To continue using aarch64-binutils, set
1325 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1328 The UDP optimization in entry 20160818 that added the sysctl
1329 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1330 packets will no longer be treated as L3 broadcast packets.
1333 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1334 use any explicitly assigned loopback address available in the jail
1335 instead of using the first assigned address of the jail.
1338 The ctl.ko module no longer implements the iSCSI target frontend:
1339 cfiscsi.ko does instead.
1341 If building cfiscsi.ko as a kernel module, the module can be loaded
1342 via one of the following methods:
1343 - `cfiscsi_load="YES"` in loader.conf(5).
1344 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1345 - ctladm(8)/ctld(8), when compiled with iSCSI support
1346 (`WITH_ISCSI=yes` in src.conf(5))
1348 Please see cfiscsi(4) for more details.
1351 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1352 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1353 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1354 missing, but mmcsd.ko now will refuse to load if it is incompatible
1358 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1359 If you have used named states in the firewall rules, you need to modify
1360 them after installworld and before rebooting. Now named states must
1361 be prefixed with colon.
1364 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1365 removed as the userland we provide cannot use them. The KMS version
1366 (sys/dev/drm2) supports the same hardware.
1369 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1370 Please see the 20141231 entry below for information about prerequisites
1371 and upgrading, if you are not already using clang 3.5.0 or higher.
1374 The code that provides support for ZFS .zfs/ directory functionality
1375 has been reimplemented. It's not possible now to create a snapshot
1376 by mkdir under .zfs/snapshot/. That should be the only user visible
1380 EISA bus support has been removed. The WITH_EISA option is no longer
1384 MCA bus support has been removed.
1387 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1388 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1391 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1392 the em(4) driver conforms to iflib specifications.
1395 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1396 IFLIB. If you have a custom kernel configuration that excludes em(4)
1397 but you use igb(4), you need to re-add em(4) to your custom
1401 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1402 Please see the 20141231 entry below for information about prerequisites
1403 and upgrading, if you are not already using clang 3.5.0 or higher.
1406 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1407 Please see the 20141231 entry below for information about prerequisites
1408 and upgrading, if you are not already using clang 3.5.0 or higher.
1411 The layout of the pmap structure has changed for powerpc to put the pmap
1412 statistics at the front for all CPU variations. libkvm(3) and all tools
1413 that link against it need to be recompiled.
1416 isl(4) and cyapa(4) drivers now require a new driver,
1417 chromebook_platform(4), to work properly on Chromebook-class hardware.
1418 On other types of hardware the drivers may need to be configured using
1419 device hints. Please see the corresponding manual pages for details.
1422 The urtwn(4) driver was merged into rtwn(4) and now consists of
1423 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1425 Also, firmware for RTL8188CE was renamed due to possible name
1426 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1429 GNU rcs has been removed from base. It is available as packages:
1430 - rcs: Latest GPLv3 GNU rcs version.
1431 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1435 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1436 modules now requires that the kernel configuration contain the
1437 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1440 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1441 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1444 Relocatable object files with the extension of .So have been renamed
1445 to use an extension of .pico instead. The purpose of this change is
1446 to avoid a name clash with shared libraries on case-insensitive file
1447 systems. On those file systems, foo.So is the same file as foo.so.
1450 GNU rcs has been turned off by default. It can (temporarily) be built
1451 again by adding WITH_RCS knob in src.conf.
1452 Otherwise, GNU rcs is available from packages:
1453 - rcs: Latest GPLv3 GNU rcs version.
1454 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1457 The backup_uses_rcs functionality has been removed from rc.subr.
1460 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1461 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1462 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1463 QUEUE_MACRO_DEBUG behavior.
1466 r304787 changed some ioctl interfaces between the iSCSI userspace
1467 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1468 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1472 The UDP receive code has been updated to only treat incoming UDP
1473 packets that were addressed to an L2 broadcast address as L3
1474 broadcast packets. It is not expected that this will affect any
1475 standards-conforming UDP application. The new behaviour can be
1476 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1480 Remove the openbsd_poll system call.
1481 __FreeBSD_version has been bumped because of this.
1484 The stable/11 branch has been created from head@r302406.
1487 The libc stub for the pipe(2) system call has been replaced with
1488 a wrapper that calls the pipe2(2) system call and the pipe(2)
1489 system call is now only implemented by the kernels that include
1490 "options COMPAT_FREEBSD10" in their config file (this is the
1491 default). Users should ensure that this option is enabled in
1492 their kernel or upgrade userspace to r302092 before upgrading their
1496 CAM now strips the leading spaces from each SCSI disk's serial number.
1497 This will affect users who create UFS filesystems on SCSI disks using
1498 those disk's diskid device nodes. For example, if /etc/fstab
1499 previously contained a line like
1500 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1501 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1502 transforms like gmirror may also be affected. ZFS users should
1506 The bitstring(3) API has been updated with new functionality and
1507 improved performance. But it is binary-incompatible with the old API.
1508 Objects built with the new headers may not be linked against objects
1509 built with the old headers.
1512 The brk and sbrk functions have been removed from libc on arm64.
1513 Binutils from ports has been updated to not link to these
1514 functions and should be updated to the latest version before
1515 installing a new libc.
1518 The armv6 port now defaults to hard float ABI. Limited support
1519 for running both hardfloat and soft float on the same system
1520 is available using the libraries installed with -DWITH_LIBSOFT.
1521 This has only been tested as an upgrade path for installworld
1522 and packages may fail or need manual intervention to run. New
1523 packages will be needed.
1525 To update an existing self-hosted armv6hf system, you must add
1526 TARGET_ARCH=armv6 on the make command line for both the build
1527 and the install steps.
1530 Kernel modules compiled outside of a kernel build now default to
1531 installing to /boot/modules instead of /boot/kernel. Many kernel
1532 modules built this way (such as those in ports) already overrode
1533 KMODDIR explicitly to install into /boot/modules. However,
1534 manually building and installing a module from /sys/modules will
1535 now install to /boot/modules instead of /boot/kernel.
1538 The CAM I/O scheduler has been committed to the kernel. There should be
1539 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1540 list of known rogues that claim support for this but actually corrupt
1541 data is believed to be complete, be on the lookout for data
1542 corruption. The known rogue list is believed to be complete:
1544 o Crucial MX100, M550 drives with MU01 firmware.
1545 o Micron M510 and M550 drives with MU01 firmware.
1546 o Micron M500 prior to MU07 firmware
1547 o Samsung 830, 840, and 850 all firmwares
1548 o FCCT M500 all firmwares
1550 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1551 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1552 updated firmware. Black listed drives will work correctly because these
1553 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1554 this list is the same as found in Linux, it's believed there are no
1555 other rogues in the market place. All other models from the above
1558 To be safe, if you are at all concerned, you can quirk each of your
1559 drives to prevent NCQ from being sent by setting:
1560 kern.cam.ada.X.quirks="0x2"
1561 in loader.conf. If the drive requires the 4k sector quirk, set the
1562 quirks entry to 0x3.
1565 The FAST_DEPEND build option has been removed and its functionality is
1566 now the one true way. The old mkdep(1) style of 'make depend' has
1567 been removed. See 20160311 for further details.
1570 Resource range types have grown from unsigned long to uintmax_t. All
1571 drivers, and anything using libdevinfo, need to be recompiled.
1574 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1575 builds. It no longer runs mkdep(1) during 'make depend', and the
1576 'make depend' stage can safely be skipped now as it is auto ran
1577 when building 'make all' and will generate all SRCS and DPSRCS before
1578 building anything else. Dependencies are gathered at compile time with
1579 -MF flags kept in separate .depend files per object file. Users should
1580 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1581 stale .depend files.
1584 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1585 kernel modules. Therefore, if you load any kernel modules at boot time,
1586 please install the boot loaders after you install the kernel, but before
1590 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1591 make installkernel KERNCONF=YOUR_KERNEL_HERE
1592 make -C sys/boot install
1593 <reboot in single user>
1595 Then follow the usual steps, described in the General Notes section,
1599 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1600 see the 20141231 entry below for information about prerequisites and
1601 upgrading, if you are not already using clang 3.5.0 or higher.
1604 The AIO subsystem is now a standard part of the kernel. The
1605 VFS_AIO kernel option and aio.ko kernel module have been removed.
1606 Due to stability concerns, asynchronous I/O requests are only
1607 permitted on sockets and raw disks by default. To enable
1608 asynchronous I/O requests on all file types, set the
1609 vfs.aio.enable_unsafe sysctl to a non-zero value.
1612 The ELF object manipulation tool objcopy is now provided by the
1613 ELF Tool Chain project rather than by GNU binutils. It should be a
1614 drop-in replacement, with the addition of arm64 support. The
1615 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1616 to obtain the GNU version if necessary.
1619 Building ZFS pools on top of zvols is prohibited by default. That
1620 feature has never worked safely; it's always been prone to deadlocks.
1621 Using a zvol as the backing store for a VM guest's virtual disk will
1622 still work, even if the guest is using ZFS. Legacy behavior can be
1623 restored by setting vfs.zfs.vol.recursive=1.
1626 The NONE and HPN patches has been removed from OpenSSH. They are
1627 still available in the security/openssh-portable port.
1630 With the addition of ypldap(8), a new _ypldap user is now required
1631 during installworld. "mergemaster -p" can be used to add the user
1632 prior to installworld, as documented in the handbook.
1635 The tftp loader (pxeboot) now uses the option root-path directive. As a
1636 consequence it no longer looks for a pxeboot.4th file on the tftp
1637 server. Instead it uses the regular /boot infrastructure as with the
1641 The code to start recording plug and play data into the modules has
1642 been committed. While the old tools will properly build a new kernel,
1643 a number of warnings about "unknown metadata record 4" will be produced
1644 for an older kldxref. To avoid such warnings, make sure to rebuild
1645 the kernel toolchain (or world). Make sure that you have r292078 or
1646 later when trying to build 292077 or later before rebuilding.
1649 Debug data files are now built by default with 'make buildworld' and
1650 installed with 'make installworld'. This facilitates debugging but
1651 requires more disk space both during the build and for the installed
1652 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1656 r291527 changed the internal interface between the nfsd.ko and
1657 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1658 __FreeBSD_version has been bumped because of this.
1661 Add support for unicode collation strings leads to a change of
1662 order of files listed by ls(1) for example. To get back to the old
1663 behaviour, set LC_COLLATE environment variable to "C".
1665 Databases administrators will need to reindex their databases given
1666 collation results will be different.
1668 Due to a bug in install(1) it is recommended to remove the ancient
1669 locales before running make installworld.
1671 rm -rf /usr/share/locale/*
1674 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1675 libcrypto.so.7 or libssl.so.7 must be recompiled.
1678 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1679 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1680 should be replaced with isp_2400 and isp_2500 modules respectively.
1683 The build previously allowed using 'make -n' to not recurse into
1684 sub-directories while showing what commands would be executed, and
1685 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1686 and 'make -N' will not.
1689 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1690 and etcupdate will now use this file. A custom sendmail.cf is now
1691 updated via this mechanism rather than via installworld. If you had
1692 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1693 want to remove the exclusion or change it to "always install".
1694 /etc/mail/sendmail.cf is now managed the same way regardless of
1695 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1696 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1699 Compatibility shims for legacy ATA device names have been removed.
1700 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1701 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1702 environment variables, /dev/ad* and /dev/ar* symbolic links.
1705 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1706 Please see the 20141231 entry below for information about prerequisites
1707 and upgrading, if you are not already using clang 3.5.0 or higher.
1710 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1711 and renamed from .symbols to .debug. This reduces the size requirements
1712 on the boot partition or file system and provides consistency with
1713 userland debug files.
1715 When using the supported kernel installation method the
1716 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1717 as is done with /boot/kernel.
1719 Developers wishing to maintain the historical behavior of installing
1720 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1723 The wireless drivers had undergone changes that remove the 'parent
1724 interface' from the ifconfig -l output. The rc.d network scripts
1725 used to check presence of a parent interface in the list, so old
1726 scripts would fail to start wireless networking. Thus, etcupdate(3)
1727 or mergemaster(8) run is required after kernel update, to update your
1728 rc.d scripts in /etc.
1731 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1732 These configurations are now automatically interpreted as
1733 'scrub fragment reassemble'.
1736 Kernel-loadable modules for the random(4) device are back. To use
1737 them, the kernel must have
1740 options RANDOM_LOADABLE
1742 kldload(8) can then be used to load random_fortuna.ko
1743 or random_yarrow.ko. Please note that due to the indirect
1744 function calls that the loadable modules need to provide,
1745 the build-in variants will be slightly more efficient.
1747 The random(4) kernel option RANDOM_DUMMY has been retired due to
1748 unpopularity. It was not all that useful anyway.
1751 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1752 Control over building the ELF Tool Chain tools is now provided by
1753 the WITHOUT_TOOLCHAIN knob.
1756 The polarity of Pulse Per Second (PPS) capture events with the
1757 uart(4) driver has been corrected. Prior to this change the PPS
1758 "assert" event corresponded to the trailing edge of a positive PPS
1759 pulse and the "clear" event was the leading edge of the next pulse.
1761 As the width of a PPS pulse in a typical GPS receiver is on the
1762 order of 1 millisecond, most users will not notice any significant
1763 difference with this change.
1765 Anyone who has compensated for the historical polarity reversal by
1766 configuring a negative offset equal to the pulse width will need to
1767 remove that workaround.
1770 The default group assigned to /dev/dri entries has been changed
1771 from 'wheel' to 'video' with the id of '44'. If you want to have
1772 access to the dri devices please add yourself to the video group
1775 # pw groupmod video -m $USER
1778 The menu.rc and loader.rc files will now be replaced during
1779 upgrades. Please migrate local changes to menu.rc.local and
1780 loader.rc.local instead.
1783 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1784 strings and strip have been removed. The src.conf(5) knob
1785 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1788 As ZFS requires more kernel stack pages than is the default on some
1789 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1790 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1792 Please consider using 'options KSTACK_PAGES=X' where X is greater
1793 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1796 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1797 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1798 default, i.e., they will not contain "::". For example, instead
1799 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1800 to have a more specific match, such as different map entries for
1801 IPv6:0:0 vs IPv6:0. This change requires that configuration
1802 data (including maps, files, classes, custom ruleset, etc.) must
1803 use the same format, so make certain such configuration data is
1804 upgrading. As a very simple check search for patterns like
1805 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1806 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1807 the cf option UseCompressedIPv6Addresses.
1810 The default kernel entropy-processing algorithm is now
1811 Fortuna, replacing Yarrow.
1813 Assuming you have 'device random' in your kernel config
1814 file, the configurations allow a kernel option to override
1815 this default. You may choose *ONE* of:
1817 options RANDOM_YARROW # Legacy /dev/random algorithm.
1818 options RANDOM_DUMMY # Blocking-only driver.
1820 If you have neither, you get Fortuna. For most people,
1821 read no further, Fortuna will give a /dev/random that works
1822 like it always used to, and the difference will be irrelevant.
1824 If you remove 'device random', you get *NO* kernel-processed
1825 entropy at all. This may be acceptable to folks building
1826 embedded systems, but has complications. Carry on reading,
1827 and it is assumed you know what you need.
1829 *PLEASE* read random(4) and random(9) if you are in the
1830 habit of tweaking kernel configs, and/or if you are a member
1831 of the embedded community, wanting specific and not-usual
1832 behaviour from your security subsystems.
1834 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1835 random', you will NOT have a functioning /dev/random, and
1836 many cryptographic features will not work, including SSH.
1837 You may also find strange behaviour from the random(3) set
1838 of library functions, in particular sranddev(3), srandomdev(3)
1839 and arc4random(3). The reason for this is that the KERN_ARND
1840 sysctl only returns entropy if it thinks it has some to
1841 share, and with RANDOM_DUMMY or no 'device random' this
1845 An additional fix for the issue described in the 20150614 sendmail
1846 entry below has been committed in revision 284717.
1849 FreeBSD's old make (fmake) has been removed from the system. It is
1850 available as the devel/fmake port or via pkg install fmake.
1853 The fix for the issue described in the 20150614 sendmail entry
1854 below has been committed in revision 284436. The work
1855 around described in that entry is no longer needed unless the
1856 default setting is overridden by a confDH_PARAMETERS configuration
1857 setting of '5' or pointing to a 512 bit DH parameter file.
1860 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1861 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1862 and devel/kyua to version 0.20+ and adjust any calling code to work
1863 with Kyuafile and kyua.
1866 The import of openssl to address the FreeBSD-SA-15:10.openssl
1867 security advisory includes a change which rejects handshakes
1868 with DH parameters below 768 bits. sendmail releases prior
1869 to 8.15.2 (not yet released), defaulted to a 512 bit
1870 DH parameter setting for client connections. To work around
1871 this interoperability, sendmail can be configured to use a
1872 2048 bit DH parameter by:
1874 1. Edit /etc/mail/`hostname`.mc
1875 2. If a setting for confDH_PARAMETERS does not exist or
1876 exists and is set to a string beginning with '5',
1877 replace it with '2'.
1878 3. If a setting for confDH_PARAMETERS exists and is set to
1879 a file path, create a new file with:
1880 openssl dhparam -out /path/to/file 2048
1881 4. Rebuild the .cf file:
1882 cd /etc/mail/; make; make install
1883 5. Restart sendmail:
1884 cd /etc/mail/; make restart
1886 A sendmail patch is coming, at which time this file will be
1890 Generation of legacy formatted entries have been disabled by default
1891 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1892 entries were converted to use the new format by default when the new,
1893 machine independent format have been added and supported since FreeBSD
1896 Please see the pwd_mkdb(8) manual page for further details.
1899 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1900 20141231 entry below for information about prerequisites and upgrading,
1901 if you are not already using 3.5.0 or higher.
1904 TI platform code switched to using vendor DTS files and this update
1905 may break existing systems running on Beaglebone, Beaglebone Black,
1908 - dtb files should be regenerated/reinstalled. Filenames are the
1909 same but content is different now
1910 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1911 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1912 addressing scheme is now pin 25 on /dev/gpioc3.
1913 - Pandaboard: /etc/ttys should be updated, serial console device is
1914 now /dev/ttyu2, not /dev/ttyu0
1917 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1918 If you need the GNU extension from groff soelim(1), install groff
1919 from package: pkg install groff, or via ports: textproc/groff.
1922 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1923 defined in symlink(7); previously symlinks were silently ignored.
1926 The const qualifier has been removed from iconv(3) to comply with
1927 POSIX. The ports tree is aware of this from r384038 onwards.
1930 Libraries specified by LIBADD in Makefiles must have a corresponding
1931 DPADD_<lib> variable to ensure correct dependencies. This is now
1932 enforced in src.libnames.mk.
1935 From legacy ata(4) driver was removed support for SATA controllers
1936 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1937 Kernel modules ataahci and ataadaptec were removed completely,
1938 replaced by ahci and mvs modules respectively.
1941 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1942 the 20141231 entry below for information about prerequisites and
1943 upgrading, if you are not already using 3.5.0 or higher.
1946 The 32-bit PowerPC kernel has been changed to a position-independent
1947 executable. This can only be booted with a version of loader(8)
1948 newer than January 31, 2015, so make sure to update both world and
1949 kernel before rebooting.
1952 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1953 but before r278950, the RNG was not seeded properly. Immediately
1954 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1955 ssh keys or openssl keys) that were generated w/ a kernel from that
1956 range. This does not affect programs that directly used /dev/random
1957 or /dev/urandom. All userland uses of arc4random(3) are affected.
1960 The autofs(4) ABI was changed in order to restore binary compatibility
1961 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1962 with the new kernel.
1965 The powerpc64 kernel has been changed to a position-independent
1966 executable. This can only be booted with a new version of loader(8),
1967 so make sure to update both world and kernel before rebooting.
1970 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1971 only release, no new features have been added. Please see the 20141231
1972 entry below for information about prerequisites and upgrading, if you
1973 are not already using 3.5.0.
1976 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1977 taken from the ELF Tool Chain project rather than GNU binutils. They
1978 should be drop-in replacements, with the addition of arm64 support.
1979 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1980 binutils tools, if necessary. See 20150805 for updated information.
1983 The default Unbound configuration now enables remote control
1984 using a local socket. Users who have already enabled the
1985 local_unbound service should regenerate their configuration
1986 by running "service local_unbound setup" as root.
1989 The GNU texinfo and GNU info pages have been removed.
1990 To be able to view GNU info pages please install texinfo from ports.
1993 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1995 As of this release, a prerequisite for building clang, llvm and lldb is
1996 a C++11 capable compiler and C++11 standard library. This means that to
1997 be able to successfully build the cross-tools stage of buildworld, with
1998 clang as the bootstrap compiler, your system compiler or cross compiler
1999 should either be clang 3.3 or later, or gcc 4.8 or later, and your
2000 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
2003 On any standard FreeBSD 10.x or 11.x installation, where clang and
2004 libc++ are on by default (that is, on x86 or arm), this should work out
2007 On 9.x installations where clang is enabled by default, e.g. on x86 and
2008 powerpc, libc++ will not be enabled by default, so libc++ should be
2009 built (with clang) and installed first. If both clang and libc++ are
2010 missing, build clang first, then use it to build libc++.
2012 On 8.x and earlier installations, upgrade to 9.x first, and then follow
2013 the instructions for 9.x above.
2015 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
2016 default, and do not build clang.
2018 Many embedded systems are resource constrained, and will not be able to
2019 build clang in a reasonable time, or in some cases at all. In those
2020 cases, cross building bootable systems on amd64 is a workaround.
2022 This new version of clang introduces a number of new warnings, of which
2023 the following are most likely to appear:
2027 This warns in two cases, for both C and C++:
2028 * When the code is trying to take the absolute value of an unsigned
2029 quantity, which is effectively a no-op, and almost never what was
2030 intended. The code should be fixed, if at all possible. If you are
2031 sure that the unsigned quantity can be safely cast to signed, without
2032 loss of information or undefined behavior, you can add an explicit
2033 cast, or disable the warning.
2035 * When the code is trying to take an absolute value, but the called
2036 abs() variant is for the wrong type, which can lead to truncation.
2037 If you want to disable the warning instead of fixing the code, please
2038 make sure that truncation will not occur, or it might lead to unwanted
2041 -Wtautological-undefined-compare and
2042 -Wundefined-bool-conversion
2044 These warn when C++ code is trying to compare 'this' against NULL, while
2045 'this' should never be NULL in well-defined C++ code. However, there is
2046 some legacy (pre C++11) code out there, which actively abuses this
2047 feature, which was less strictly defined in previous C++ versions.
2049 Squid and openjdk do this, for example. The warning can be turned off
2050 for C++98 and earlier, but compiling the code in C++11 mode might result
2051 in unexpected behavior; for example, the parts of the program that are
2052 unreachable could be optimized away.
2055 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
2056 kernel sources have been removed. The .h files remain, since some
2057 utilities include them. This will need to be fixed later.
2058 If "mount -t oldnfs ..." is attempted, it will fail.
2059 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
2060 the utilities will report errors.
2063 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
2064 directories to top level SUBDIR variable when their parent
2065 directory is included in LOCAL_DIRS. Users with build systems with
2066 such hierarchies and without SUBDIR entries in the parent
2067 directory Makefiles should add them or add the directories to
2071 faith(4) and faithd(8) have been removed from the base system. Faith
2072 has been obsolete for a very long time.
2075 vt(4), the new console driver, is enabled by default. It brings
2076 support for Unicode and double-width characters, as well as
2077 support for UEFI and integration with the KMS kernel video
2080 You may need to update your console settings in /etc/rc.conf,
2081 most probably the keymap. During boot, /etc/rc.d/syscons will
2082 indicate what you need to do.
2084 vt(4) still has issues and lacks some features compared to
2085 syscons(4). See the wiki for up-to-date information:
2086 https://wiki.freebsd.org/Newcons
2088 If you want to keep using syscons(4), you can do so by adding
2089 the following line to /boot/loader.conf:
2093 pjdfstest has been integrated into kyua as an opt-in test suite.
2094 Please see share/doc/pjdfstest/README for more details on how to
2098 gperf has been removed from the base system for architectures
2099 that use clang. Ports that require gperf will obtain it from the
2103 pjdfstest has been moved from tools/regression/pjdfstest to
2107 At svn r271982, The default linux compat kernel ABI has been adjusted
2108 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2109 update. If you wish to continue using the linux-f10 compat ports,
2110 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2111 encouraged to update their linux-compat packages to linux-c6 during
2112 their next update cycle.
2115 The ofwfb driver, used to provide a graphics console on PowerPC when
2116 using vt(4), no longer allows mmap() of all physical memory. This
2117 will prevent Xorg on PowerPC with some ATI graphics cards from
2118 initializing properly unless x11-servers/xorg-server is updated to
2122 The xdev targets have been converted to using TARGET and
2123 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2126 The default unbound configuration has been modified to address
2127 issues with reverse lookups on networks that use private
2128 address ranges. If you use the local_unbound service, run
2129 "service local_unbound setup" as root to regenerate your
2130 configuration, then "service local_unbound reload" to load the
2134 The GNU texinfo and GNU info pages are not built and installed
2135 anymore, WITH_INFO knob has been added to allow to built and install
2137 UPDATE: see 20150102 entry on texinfo's removal
2140 The GNU readline library is now an INTERNALLIB - that is, it is
2141 statically linked into consumers (GDB and variants) in the base
2142 system, and the shared library is no longer installed. The
2143 devel/readline port is available for third party software that
2147 The Itanium architecture (ia64) has been removed from the list of
2148 known architectures. This is the first step in the removal of the
2152 Commit r268115 has added NFSv4.1 server support, merged from
2153 projects/nfsv4.1-server. Since this includes changes to the
2154 internal interfaces between the NFS related modules, a full
2155 build of the kernel and modules will be necessary.
2156 __FreeBSD_version has been bumped.
2159 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2160 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2161 which differs from the behaviour controlled by this knob.)
2164 Maximal length of the serial number in CTL was increased from 16 to
2165 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2166 and ctld, need to be rebuilt to work with a new kernel.
2169 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2170 1 respectively to match the upstream numbers. They were out of
2171 sync because, when they were originally added to FreeBSD, the
2172 upstream versions were not respected. These libraries are private
2173 and not yet built by default, so renumbering them should be a
2174 non-issue. However, unclean source trees will yield broken test
2175 programs once the operator executes "make delete-old-libs" after a
2176 "make installworld".
2178 Additionally, the atf-sh binary was made private by moving it into
2179 /usr/libexec/. Already-built shell test programs will keep the
2180 path to the old binary so they will break after "make delete-old"
2183 If you are using WITH_TESTS=yes (not the default), wipe the object
2184 tree and rebuild from scratch to prevent spurious test failures.
2185 This is only needed once: the misnumbered libraries and misplaced
2186 binaries have been added to OptionalObsoleteFiles.inc so they will
2187 be removed during a clean upgrade.
2190 Clang and llvm have been upgraded to 3.4.1 release.
2193 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2194 be removed to avoid issues in the future (and has been added to
2198 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2199 past, it affected all builds that used the bsd.*.mk files. The old
2200 behavior was a bug, but people may have relied upon it. To get this
2201 behavior back, you can .include /etc/src.conf from /etc/make.conf
2202 (which is still global and isn't changed). This also changes the
2203 behavior of incremental builds inside the tree of individual
2204 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2205 Although this has survived make universe and some upgrade scenarios,
2206 other upgrade scenarios may have broken. At least one form of
2207 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2208 as well... In cases where MAKESYSPATH isn't working with this
2209 setting, you'll need to set it to the full path to your tree.
2211 One side effect of all this cleaning up is that bsd.compiler.mk
2212 is no longer implicitly included by bsd.own.mk. If you wish to
2213 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2217 The lindev device has been removed since /dev/full has been made a
2218 standard device. __FreeBSD_version has been bumped.
2221 The knob WITHOUT_VI was added to the base system, which controls
2222 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2223 in order to reorder files share/termcap and didn't build ex(1) as a
2224 build tool, so building/installing with WITH_VI is highly advised for
2225 build hosts for older releases.
2227 This issue has been fixed in stable/9 and stable/10 in r277022 and
2228 r276991, respectively.
2231 The YES_HESIOD knob has been removed. It has been obsolete for
2232 a decade. Please move to using WITH_HESIOD instead or your builds
2233 will silently lack HESIOD.
2236 The uart(4) driver has been changed with respect to its handling
2237 of the low-level console. Previously the uart(4) driver prevented
2238 any process from changing the baudrate or the CLOCAL and HUPCL
2239 control flags. By removing the restrictions, operators can make
2240 changes to the serial console port without having to reboot.
2241 However, when getty(8) is started on the serial device that is
2242 associated with the low-level console, a misconfigured terminal
2243 line in /etc/ttys will now have a real impact.
2244 Before upgrading the kernel, make sure that /etc/ttys has the
2245 serial console device configured as 3wire without baudrate to
2246 preserve the previous behaviour. E.g:
2247 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2250 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2251 to improve performance. To re-enable it, if needed, run rpcbind
2252 with command line option -W.
2255 Switched back to the GPL dtc compiler due to updates in the upstream
2256 dts files not being supported by the BSDL dtc compiler. You will need
2257 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2258 may result while building dtb files during a kernel build if you fail
2259 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2262 Clang and llvm have been upgraded to 3.4 release.
2265 The nve(4) driver has been removed. Please use the nfe(4) driver
2266 for NVIDIA nForce MCP Ethernet adapters instead.
2269 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2270 This could cause certain C++ applications using shared libraries built
2271 against the previous version of libc++ to crash. The incompatibility
2272 has now been fixed, but any C++ applications or shared libraries built
2273 between r261283 and r261801 should be recompiled.
2276 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2277 capability mode support. Please note that enabling the feature in
2278 kernel is still highly recommended.
2281 OpenSSH is now built with sandbox support, and will use sandbox as
2282 the default privilege separation method. This requires Capsicum
2283 capability mode support in kernel.
2286 The libelf and libdwarf libraries have been updated to newer
2287 versions from upstream. Shared library version numbers for
2288 these two libraries were bumped. Any ports or binaries
2289 requiring these two libraries should be recompiled.
2290 __FreeBSD_version is bumped to 1100006.
2293 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2294 instead of providing an explicit one, this would prevent such
2295 Makefile from providing its own Kyuafile in the future during
2296 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2297 intervention is needed to clean an objdir if you use NO_CLEAN:
2298 # find /usr/obj -name Kyuafile | xargs rm -f
2301 The behavior of gss_pseudo_random() for the krb5 mechanism
2302 has changed, for applications requesting a longer random string
2303 than produced by the underlying enctype's pseudo-random() function.
2304 In particular, the random string produced from a session key of
2305 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2306 be different at the 17th octet and later, after this change.
2307 The counter used in the PRF+ construction is now encoded as a
2308 big-endian integer in accordance with RFC 4402.
2309 __FreeBSD_version is bumped to 1100004.
2312 The WITHOUT_ATF build knob has been removed and its functionality
2313 has been subsumed into the more generic WITHOUT_TESTS. If you were
2314 using the former to disable the build of the ATF libraries, you
2315 should change your settings to use the latter.
2318 The default version of mtree is nmtree which is obtained from
2319 NetBSD. The output is generally the same, but may vary
2320 slightly. If you found you need identical output adding
2321 "-F freebsd9" to the command line should do the trick. For the
2322 time being, the old mtree is available as fmtree.
2325 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2326 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2327 1.1.4_8 and verify bsdyml not linked in, before running "make
2329 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2331 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2334 The stable/10 branch has been created in subversion from head
2341 Sometimes, obscure build problems are the result of environment
2342 poisoning. This can happen because the make utility reads its
2343 environment when searching for values for global variables. To run
2344 your build attempts in an "environmental clean room", prefix all make
2345 commands with 'env -i '. See the env(1) manual page for more details.
2346 Occasionally a build failure will occur with "make -j" due to a race
2347 condition. If this happens try building again without -j, and please
2348 report a bug if it happens consistently.
2350 When upgrading from one major version to another it is generally best to
2351 upgrade to the latest code in the currently installed branch first, then
2352 do an upgrade to the new branch. This is the best-tested upgrade path,
2353 and has the highest probability of being successful. Please try this
2354 approach if you encounter problems with a major version upgrade. Since
2355 the stable 4.x branch point, one has generally been able to upgrade from
2356 anywhere in the most recent stable branch to head / current (or even the
2357 last couple of stable branches). See the top of this file when there's
2360 The update process will emit an error on an attempt to perform a build
2361 or install from a FreeBSD version below the earliest supported version.
2362 When updating from an older version the update should be performed one
2363 major release at a time, including running `make delete-old` at each
2366 When upgrading a live system, having a root shell around before
2367 installing anything can help undo problems. Not having a root shell
2368 around can lead to problems if pam has changed too much from your
2369 starting point to allow continued authentication after the upgrade.
2371 This file should be read as a log of events. When a later event changes
2372 information of a prior event, the prior event should not be deleted.
2373 Instead, a pointer to the entry with the new information should be
2374 placed in the old entry. Readers of this file should also sanity check
2375 older entries before relying on them blindly. Authors of new entries
2376 should write them with this in mind.
2380 When upgrading the boot ZFS pool to a new version, always follow
2383 1.) recompile and reinstall the ZFS boot loader and boot block
2384 (this is part of "make buildworld" and "make installworld")
2386 2.) update the ZFS boot block on your boot drive
2388 The following example updates the ZFS boot block on the
2389 freebsd-boot partition of a GPT partitioned drive ada0:
2390 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2391 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2394 Non-boot pools do not need these updates.
2398 If you are updating from a prior version of FreeBSD (even one just
2399 a few days old), you should follow this procedure. It is the most
2400 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2402 make kernel-toolchain
2403 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2404 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2406 To test a kernel once
2407 ---------------------
2408 If you just want to boot a kernel once (because you are not sure
2409 if it works, or if you want to boot a known bad kernel to provide
2410 debugging information) run
2411 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2412 nextboot -k testkernel
2414 To rebuild everything and install it on the current system.
2415 -----------------------------------------------------------
2416 # Note: sometimes if you are running current you gotta do more than
2417 # is listed here if you are upgrading from a really old current.
2419 <make sure you have good level 0 dumps>
2421 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2422 make installkernel KERNCONF=YOUR_KERNEL_HERE
2424 <reboot in single user> [3]
2431 To cross-install current onto a separate partition
2432 --------------------------------------------------
2433 # In this approach we use a separate partition to hold
2434 # current's root, 'usr', and 'var' directories. A partition
2435 # holding "/", "/usr" and "/var" should be about 2GB in
2438 <make sure you have good level 0 dumps>
2441 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2442 <maybe newfs current's root partition>
2443 <mount current's root partition on directory ${CURRENT_ROOT}>
2444 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2445 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2446 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2447 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2448 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2449 <reboot into current>
2450 <do a "native" rebuild/install as described in the previous section>
2451 <maybe install compatibility libraries from ports/misc/compat*>
2455 To upgrade in-place from stable to current
2456 ----------------------------------------------
2457 <make sure you have good level 0 dumps>
2459 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2460 make installkernel KERNCONF=YOUR_KERNEL_HERE
2462 <reboot in single user> [3]
2469 Make sure that you've read the UPDATING file to understand the
2470 tweaks to various things you need. At this point in the life
2471 cycle of current, things change often and you are on your own
2472 to cope. The defaults can also change, so please read ALL of
2473 the UPDATING entries.
2475 Also, if you are tracking -current, you must be subscribed to
2476 freebsd-current@freebsd.org. Make sure that before you update
2477 your sources that you have read and understood all the recent
2478 messages there. If in doubt, please track -stable which has
2479 much fewer pitfalls.
2481 [1] If you have third party modules, such as vmware, you should disable
2482 them at this point so they don't crash your system on
2483 reboot. Alternatively, you should rebuild all the modules you have in
2484 your system and install them as well. If you are running -current, you
2485 should seriously consider placing all sources to all the modules for
2486 your system (or symlinks to them) in /usr/local/sys/modules so this
2487 happens automatically. If all your modules come from ports, then adding
2488 the port origin directories to PORTS_MODULES instead is also automatic
2490 PORTS_MODULES+=x11/nvidia-driver
2492 [3] From the bootblocks, boot -s, and then do
2496 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2497 cd src # full path to source
2498 adjkerntz -i # if CMOS is wall time
2499 Also, when doing a major release upgrade, it is required that you boot
2500 into single user mode to do the installworld.
2502 [4] Note: This step is non-optional. Failure to do this step
2503 can result in a significant reduction in the functionality of the
2504 system. Attempting to do it by hand is not recommended and those
2505 that pursue this avenue should read this file carefully, as well
2506 as the archives of freebsd-current and freebsd-hackers mailing lists
2507 for potential gotchas. The -U option is also useful to consider.
2508 See mergemaster(8) for more information.
2510 [5] Usually this step is a no-op. However, from time to time
2511 you may need to do this if you get unknown user in the following
2512 step. It never hurts to do it all the time. You may need to
2513 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2514 install) after the buildworld before this step if you last updated
2515 from current before 20130425 or from -stable before 20130430.
2517 [6] This only deletes old files and directories. Old libraries
2518 can be deleted by "make delete-old-libs", but you have to make
2519 sure that no program is using those libraries anymore.
2521 [8] The new kernel must be able to run existing binaries used by an
2522 installworld. When upgrading across major versions, the new kernel's
2523 configuration must include the correct COMPAT_FREEBSD<n> option for
2524 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2525 to do so may leave you with a system that is hard to boot to recover. A
2526 GENERIC kernel will include suitable compatibility options to run
2527 binaries from older branches. Note that the ability to run binaries
2528 from unsupported branches is not guaranteed.
2530 Make sure that you merge any new devices from GENERIC since the
2531 last time you updated your kernel config file. Options also
2532 change over time, so you may need to adjust your custom kernels
2535 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2536 "?=" instead of the "=" assignment operator, so that buildworld can
2537 override the CPUTYPE if it needs to.
2539 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2540 not on the command line, or in /etc/make.conf. buildworld will
2541 warn if it is improperly defined.
2544 This file contains a list, in reverse chronological order, of major
2545 breakages in tracking -current. It is not guaranteed to be a complete
2546 list of such breakages, and only contains entries since September 23, 2011.
2547 If you need to see UPDATING entries from before that date, you will need
2548 to fetch an UPDATING file from an older FreeBSD release.
2550 Copyright information:
2552 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2554 Redistribution, publication, translation and use, with or without
2555 modification, in full or in part, in any form or format of this
2556 document are permitted without further permission from the author.
2558 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2559 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2560 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2561 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2562 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2563 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2564 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2565 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2566 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2567 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2568 POSSIBILITY OF SUCH DAMAGE.
2570 Contact Warner Losh if you have any questions about your use of