1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
20 Default permissions on the /var/account/acct file (and copies of it
21 rotated by periodic daily scripts) are changed from 0644 to 0640
22 because the file contains sensitive information that should not be
23 world-readable. If the /var/account directory must be created by
24 rc.d/accounting, the mode used is now 0750. Admins who use the
25 accounting feature are encouraged to change the mode of an existing
26 /var/account directory to 0750 or 0700.
29 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
30 been upgraded to 8.0.1. Please see the 20141231 entry below for
31 information about prerequisites and upgrading, if you are not already
32 using clang 3.5.0 or higher.
35 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
36 functionality needed for the RETPOLINE option should work properly
37 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
40 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
41 8.0.0. Please see the 20141231 entry below for information about
42 prerequisites and upgrading, if you are not already using clang 3.5.0
46 The RETPOLINE option produces non-functional ifunc-using binaries
47 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
48 Once Clang 8 is merged it may be enabled again.
51 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
52 7.0.1. Please see the 20141231 entry below for information about
53 prerequisites and upgrading, if you are not already using clang 3.5.0
57 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
58 compiled into your custom kernel, add 'device xz' statement to the
62 Iflib is no longer unconditionally compiled into the kernel. Drivers
63 using iflib and statically compiled into the kernel, now require
64 the 'device iflib' config option. For the same drivers loaded as
65 modules on kernels not having 'device iflib', the iflib.ko module
66 is loaded automatically.
69 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
70 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
71 servers that have vfs.nfsd.nfs_privport set will only allow mounts
72 from clients using a reserved port#. Since both the FreeBSD and Linux
73 NFSv4 clients use reserved port#s by default, this should not affect
77 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
78 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
79 it produces broken binaries when ifuncs are in use. Users needing
80 GNU ld should install the binutils port or package.
83 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
84 has been converted to a port (misc/ctm) and will be removed from
85 FreeBSD-13. A depreciation warning will be printed to stderr by
86 the ctm command, but the functionality will remain in base for all
90 The stable/12 branch has been created in subversion from head
94 Ports for the DRM modules have been simplified. Now, amd64 users should
95 just install the drm-kmod port. All others should install
98 Graphics hardware that's newer than about 2010 usually works with
99 drm-kmod. For hardware older than 2013, however, some users will need
100 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
101 than 2008 usually only works in drm-legacy-kmod. The graphics team can
102 only commit to hardware made since 2013 due to the complexity of the
103 market and difficulty to test all the older cards effectively. If you
104 have hardware supported by drm-kmod, you are strongly encouraged to use
105 that as you will get better support.
107 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
108 elsewhere, the drm and drm2 modules will be eliminated from the src base
109 soon (with a limited exception for arm). Please update to the package asap
110 and report any issues to x11@freebsd.org.
112 Generally, anybody using the drm*-kmod packages should add
113 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
114 cross-threading surprises, especially with automatic driver
115 loading from X11 startup. These will become the defaults in 13-current
119 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
120 custom kernel and module loading configuration files must be updated
121 accordingly. Moreover, interfaces previous presented as ixlvN to the
122 system are now exposed as iavfN and network configuration files must
123 be adjusted as necessary.
126 OpenSSL has been updated to version 1.1.1. This update included
127 additional various API changes througout the base system. It is
128 important to rebuild third-party software after upgrading. The value
129 of __FreeBSD_version has been bumped accordingly.
132 The legacy DRM modules and drivers have now been added to the loader's
133 module blacklist, in favor of loading them with kld_list in rc.conf(5).
134 The module blacklist may be overridden with the loader.conf(5)
135 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
139 The cam(4) based nda(4) driver will be used over nvd(4) by default on
140 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
141 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
142 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
146 Reproducible build mode is now on by default, in preparation for
147 FreeBSD 12.0. This eliminates build metadata such as the user,
148 host, and time from the kernel (and uname), unless the working tree
149 corresponds to a modified checkout from a version control system.
150 The previous behavior can be obtained by setting the /etc/src.conf
151 knob WITHOUT_REPRODUCIBLE_BUILD.
154 The Yarrow CSPRNG has been removed from the kernel as it has not been
155 supported by its designers since at least 2003. Fortuna has been the
156 default since FreeBSD-11.
159 devctl freeze/thaw have gone into the tree, the rc scripts have been
160 updated to use them and devmatch has been changed. You should update
161 kernel, userland and rc scripts all at the same time.
164 The default interpreter has been switched from 4th to Lua.
165 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
166 interpreter. If you have custom FORTH code you will need to set
167 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
168 src.conf for the build. This will create default hard links between
169 loader and loader_4th instead of loader and loader_lua, the new default.
170 If you are using UEFI it will create the proper hard link to loader.efi.
172 bhyve uses userboot.so. It remains 4th-only until some issues are solved
173 regarding coexisting with multiple versions of FreeBSD are resolved.
176 ls(1) now respects the COLORTERM environment variable used in other
177 systems and software to indicate that a colored terminal is both
178 supported and desired. If ls(1) is suddenly emitting colors, they may
179 be disabled again by either removing the unwanted COLORTERM from your
180 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
181 may not be observed in a future release.
184 The default pager for most commands has been changed to "less". To
185 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
189 The jedec_ts(4) driver has been removed. A superset of its functionality
190 is available in the jedec_dimm(4) driver, and the manpage for that
191 driver includes migration instructions. If you have "device jedec_ts"
192 in your kernel configuration file, it must be removed.
195 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
196 This should have no effect if the kernel is booted via BIOS/legacy boot.
197 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
198 has a buggy firmware that prevents a successful boot due to use of
202 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
203 support has been removed from the tree. These ports were
204 obsolete and/or known to be broken for many years.
207 loader.efi has been augmented to participate more fully in the
208 UEFI boot manager protocol. loader.efi will now look at the
209 BootXXXX environment variable to determine if a specific kernel
210 or root partition was specified. XXXX is derived from BootCurrent.
211 efibootmgr(8) manages these standard UEFI variables.
214 zfsloader's functionality has now been folded into loader.
215 zfsloader is no longer necessary once you've updated your
216 boot blocks. For a transition period, we will install a
217 hardlink for zfsloader to loader to allow a smooth transition
218 until the boot blocks can be updated (hard link because old
219 zfs boot blocks don't understand symlinks).
222 ARM64 now have efifb support, if you want to have serial console
223 on your arm64 board when an screen is connected and the bootloader
224 setup a frambuffer for us to use, just add :
228 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
229 an screen connected as the firmware will setup a framebuffer are that
230 u-boot will expose as an EFI framebuffer.
233 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
234 or take steps to update /etc/passwd before doing installworld on
235 existing systems. Do not skip the "mergemaster -Fp" step before
236 installworld, as described in the update procedures near the bottom
237 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
238 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
239 the ntp config file contain options that change file/dir locations.
240 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
241 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
242 taking steps to ensure that all required files/dirs are accessible
246 Big endian arm support has been removed.
249 The static environment setup in kernel configs is no longer mutually
250 exclusive with the loader(8) environment by default. In order to
251 restore the previous default behavior of disabling the loader(8)
252 environment if a static environment is present, you must specify
253 loader_env.disabled=1 in the static environment.
256 The ABI of syscalls used by management tools like sockstat and
257 netstat has been broken to allow 32-bit binaries to work on
258 64-bit kernels without modification. These programs will need
259 to match the kernel in order to function. External programs may
260 require minor modifications to accommodate a change of type in
261 structures from pointers to 64-bit virtual addresses.
264 On i386 and amd64 atomics are now inlined. Out of tree modules using
265 atomics will need to be rebuilt.
268 The '%I' format in the kern.corefile sysctl limits the number of
269 core files that a process can generate to the number stored in the
270 debug.ncores sysctl. The '%I' format is replaced by the single digit
271 index. Previously, if all indexes were taken the kernel would overwrite
272 only a core file with the highest index in a filename.
273 Currently the system will create a new core file if there is a free
274 index or if all slots are taken it will overwrite the oldest one.
277 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
278 6.0.1. Please see the 20141231 entry below for information about
279 prerequisites and upgrading, if you are not already using clang 3.5.0
283 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
284 needed to be changed to work with it. This change was made with r335763
285 and requires a mergemaster / etcupdate / etc to update the installed file.
288 r334930 changed the interface between the NFS modules, so they all
289 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
292 As of r334391 lld is the default amd64 system linker; it is installed
293 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
297 The kernel / userland interface for devinfo changed, so you'll
298 need a new kernel and userland as a pair for it to work (rebuilding
299 lib/libdevinfo is all that's required). devinfo and devmatch will
300 not work, but everything else will when there's a mismatch.
303 The on-disk format for hwpmc callchain records has changed to include
304 threadid corresponding to a given record. This changes the field offsets
305 and thus requires that libpmcstat be rebuilt before using a kernel
309 The vxge(4) driver has been removed. This driver was introduced into
310 HEAD one week before the Exar left the Ethernet market and is not
311 known to be used. If you have device vxge in your kernel config file
315 The amd64 kernel now requires a ld that supports ifunc to produce a
316 working kernel, either lld or a newer binutils. lld is built by default
317 on amd64, and the 'buildkernel' target uses it automatically. However,
318 it is not the default linker, so building the kernel the traditional
319 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
320 binutils port/package). lld will soon be default, and this requirement
323 NOTE: As of r334391 lld is the default system linker on amd64, and no
324 workaround is necessary.
327 The nxge(4) driver has been removed. This driver was for PCI-X 10g
328 cards made by s2io/Neterion. The company was aquired by Exar and
329 no longer sells or supports Ethernet products. If you have device
330 nxge in your kernel config file it must be removed.
333 The tz database (tzdb) has been updated to 2018e. This version more
334 correctly models time stamps in time zones with negative DST such as
335 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
336 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
337 time zone abbreviations and the tm_isdst flag.
340 The ixgb(4) driver has been removed. This driver was for an early and
341 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
342 quickly shifted to the long lived ixgbe family. If you have device
343 ixgb in your kernel config file it must be removed.
346 The lmc(4) driver has been removed. This was a WAN interface
347 card that was already reportedly rare in 2003, and had an ambiguous
348 license. If you have device lmc in your kernel config file it must
352 Support for Arcnet networks has been removed. If you have device
353 arcnet or device cm in your kernel config file they must be
357 Support for FDDI networks has been removed. If you have device
358 fddi or device fpa in your kernel config file they must be
362 In addition to supporting RFC 3164 formatted messages, the
363 syslogd(8) service is now capable of parsing RFC 5424 formatted
364 log messages. The main benefit of using RFC 5424 is that clients
365 may now send log messages with timestamps containing year numbers,
366 microseconds and time zone offsets.
368 Similarly, the syslog(3) C library function has been altered to
369 send RFC 5424 formatted messages to the local system logging
370 daemon. On systems using syslogd(8), this change should have no
371 negative impact, as long as syslogd(8) and the C library are
372 updated at the same time. On systems using a different system
373 logging daemon, it may be necessary to make configuration
374 adjustments, depending on the software used.
376 When using syslog-ng, add the 'syslog-protocol' flag to local
377 input sources to enable parsing of RFC 5424 formatted messages:
380 unix-dgram("/var/run/log" flags(syslog-protocol));
383 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
384 of the 'imuxsock' module to let messages be processed by the
385 regular RFC 3164/5424 parsing pipeline:
387 module(load="imuxsock" SysSock.UseSpecialParser="off")
389 Do note that these changes only affect communication between local
390 applications and syslogd(8). The format that syslogd(8) uses to
391 store messages on disk or forward messages to other systems
392 remains unchanged. syslogd(8) still uses RFC 3164 for these
393 purposes. Options to customize this behaviour will be added in the
394 future. Utilities that process log files stored in /var/log are
395 thus expected to continue to function as before.
397 __FreeBSD_version has been incremented to 1200061 to denote this
401 Support for token ring networks has been removed. If you
402 have "device token" in your kernel config you should remove
403 it. No device drivers supported token ring.
406 makefs was modified to be able to tag ISO9660 El Torito boot catalog
407 entries as EFI instead of overloading the i386 tag as done previously.
408 The amd64 mkisoimages.sh script used to build amd64 ISO images for
409 release was updated to use this. This may mean that makefs must be
410 updated before "make cdrom" can be run in the release directory. This
411 should be as simple as:
413 $ cd $SRCDIR/usr.sbin/makefs
414 $ make depend all install
417 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
418 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
419 Co-existance for the transition period will come shortly. Booting is a
420 complex environment and test coverage for Lua-enabled loaders has been
421 thin, so it would be prudent to assume it might not work and make
422 provisions for backup boot methods.
425 devmatch functionality has been turned on in devd. It will automatically
426 load drivers for unattached devices. This may cause unexpected drivers to
427 be loaded. Please report any problems to current@ and imp@freebsd.org.
430 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
431 6.0.0. Please see the 20141231 entry below for information about
432 prerequisites and upgrading, if you are not already using clang 3.5.0
436 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
437 This means it is used to link the kernel and userland libraries and
438 executables, but is not yet installed as /usr/bin/ld by default.
440 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
441 WITHOUT_LLD_BOOTSTRAP=yes
444 On i386, pmtimer has been removed. Its functionality has been folded
445 into apm. It was a no-op on ACPI in current for a while now (but was still
446 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
447 from kernel config files.
450 The use of RSS hash from the network card aka flowid has been
451 disabled by default for lagg(4) as it's currently incompatible with
452 the lacp and loadbalance protocols.
454 This can be re-enabled by setting the following in loader.conf:
455 net.link.lagg.default_use_flowid="1"
458 The SW_WATCHDOG option is no longer necessary to enable the
459 hardclock-based software watchdog if no hardware watchdog is
460 configured. As before, SW_WATCHDOG will cause the software
461 watchdog to be enabled even if a hardware watchdog is configured.
464 r326887 fixes the issue described in the 20171214 UPDATING entry.
465 r326888 flips the switch back to building GELI support always.
468 r362593 broke ZFS + GELI support for reasons unknown. However,
469 it also broke ZFS support generally, so GELI has been turned off
470 by default as the lesser evil in r326857. If you boot off ZFS and/or
471 GELI, it might not be a good time to update.
474 PowerPC users must update loader(8) by rebuilding world before
475 installing a new kernel, as the protocol connecting them has
476 changed. Without the update, loader metadata will not be passed
477 successfully to the kernel and users will have to enter their
478 root partition at the kernel mountroot prompt to continue booting.
479 Newer versions of loader can boot old kernels without issue.
482 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
483 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
484 to WITH/OUT_LOADER_GELI.
487 The naive and non-compliant support of posix_fallocate(2) in ZFS
488 has been removed as of r325320. The system call now returns EINVAL
489 when used on a ZFS file. Although the new behavior complies with the
490 standard, some consumers are not prepared to cope with it.
491 One known victim is lld prior to r325420.
494 Building in a FreeBSD src checkout will automatically create object
495 directories now rather than store files in the current directory if
496 'make obj' was not ran. Calling 'make obj' is no longer necessary.
497 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
498 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
502 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
503 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
504 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
505 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
506 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
507 The UNIFIED_OBJDIR option is a transitional feature that will be
508 removed for 12.0 release; please migrate to the new format for any
509 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
510 than hardcoding paths.
513 The native-xtools target no longer installs the files by default to the
514 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
515 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
518 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
519 options are changing from controlling the build if defined / undefined
520 to controlling the build with explicit 'yes' or 'no' values. They will
521 shift to WITH/WITHOUT options to match other options in the system.
524 libstand has turned into a private library for sys/boot use only.
525 It is no longer supported as a public interface outside of sys/boot.
528 The arm port has split armv6 into armv6 and armv7. armv7 is now
529 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
530 and are running a kernel from before r324363, you will need to add
531 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
534 When building multiple kernels using KERNCONF, non-existent KERNCONF
535 files will produce an error and buildkernel will fail. Previously
536 missing KERNCONF files silently failed giving no indication as to
537 why, only to subsequently discover during installkernel that the
538 desired kernel was never built in the first place.
541 The default serial number format for CTL LUNs has changed. This will
542 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
543 or iSCSI clients care about their LUNs' serial numbers. Users who
544 require serial number stability should hardcode serial numbers in
548 For 32-bit arm compiled for hard-float support, soft-floating point
549 binaries now always get their shared libraries from
550 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
551 /usr/libsoft also existed). Only users with a hard-float ld.so, but
552 soft-float everything else should be affected.
555 The geli password typed at boot is now hidden. To restore the previous
556 behavior, see geli(8) for configuration options.
559 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
560 sysctl values. Minor nit, but requires a rebuild of both world/kernel
564 "make check" behavior (made in ^/head@r295380) has been changed to
565 execute from a limited sandbox, as opposed to executing from
569 - The "beforecheck" and "aftercheck" targets are now specified.
570 - ${CHECKDIR} (added in commit noted above) has been removed.
571 - Legacy behavior can be enabled by setting
572 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
574 If the limited sandbox mode is enabled, "make check" will execute
575 "make distribution", then install, execute the tests, and clean up the
576 sandbox if successful.
578 The "make distribution" and "make install" targets are typically run as
579 root to set appropriate permissions and ownership at installation time.
580 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
581 environment if executing "make check" with limited sandbox mode using
582 an unprivileged user.
585 Since the switch to GPT disk labels, fsck for UFS/FFS has been
586 unable to automatically find alternate superblocks. As of r322297,
587 the information needed to find alternate superblocks has been
588 moved to the end of the area reserved for the boot block.
589 Filesystems created with a newfs of this vintage or later
590 will create the recovery information. If you have a filesystem
591 created prior to this change and wish to have a recovery block
592 created for your filesystem, you can do so by running fsck in
593 foreground mode (i.e., do not use the -p or -y options). As it
594 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
595 to which you should answer yes.
598 As of r321665, an NFSv4 server configuration that services
599 Kerberos mounts or clients that do not support the uid/gid in
600 owner/owner_group string capability, must explicitly enable
601 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
602 machine's /etc/rc.conf file.
605 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
606 Please see the 20141231 entry below for information about prerequisites
607 and upgrading, if you are not already using clang 3.5.0 or higher.
610 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
611 r-commands (rlogin, rsh, etc.) to be built with the base system.
614 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
615 a very major ABI incompatible change, so users of FreeBSD/powerpc must
616 be careful when performing source upgrades. It is best to run
617 'make installworld' from an alternate root system, either a live
618 CD/memory stick, or a temporary root partition. Additionally, all ports
619 must be recompiled. powerpc64 is largely unaffected, except in the case
620 of 32-bit compatibility. All 32-bit binaries will be affected.
623 Forward compatibility for the "ino64" project have been committed. This
624 will allow most new binaries to run on older kernels in a limited
625 fashion. This prevents many of the common foot-shooting actions in the
626 upgrade as well as the limited ability to roll back the kernel across
627 the ino64 upgrade. Complicated use cases may not work properly, though
628 enough simpler ones work to allow recovery in most situations.
631 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
632 if you require the GPL compiler.
635 The internal ABI used for communication between the NFS kernel modules
636 was changed by r320085, so __FreeBSD_version was bumped to
637 ensure all the NFS related modules are updated together.
640 The ABI of struct event was changed by extending the data
641 member to 64bit and adding ext fields. For upgrade, same
642 precautions as for the entry 20170523 "ino64" must be
646 The GNU roff toolchain has been removed from base. To render manpages
647 which are not supported by mandoc(1), man(1) can fallback on GNU roff
648 from ports (and recommends to install it).
649 To render roff(7) documents, consider using GNU roff from ports or the
650 heirloom doctools roff toolchain from ports via pkg install groff or
651 via pkg install heirloom-doctools.
654 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
655 smaller runtime footprint builds. This is useful for embedded systems
656 which only require one chipset support.
658 If you load it as a module, make sure this is in /boot/loader.conf:
662 This will load the HAL, all chip/RF backends and if_ath_pci.
663 If you have if_ath_pci in /boot/loader.conf, ensure it is after
664 if_ath or it will not load any HAL chipset support.
666 If you want to selectively load things (eg on ye cheape ARM/MIPS
667 platforms where RAM is at a premium) you should:
670 * load the chip modules in question
671 * load ath_rate, ath_dfs
673 * load if_ath_pci and/or if_ath_ahb depending upon your particular
674 bus bind type - this is where probe/attach is done.
676 For further comments/feedback, poke adrian@ .
679 The "ino64" 64-bit inode project has been committed, which extends
680 a number of types to 64 bits. Upgrading in place requires care and
681 adherence to the documented upgrade procedure.
683 If using a custom kernel configuration ensure that the
684 COMPAT_FREEBSD11 option is included (as during the upgrade the
685 system will be running the ino64 kernel with the existing world).
687 For the safest in-place upgrade begin by removing previous build
688 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
689 full procedure documented below under the heading "To rebuild
690 everything and install it on the current system." Specifically,
691 a reboot is required after installing the new kernel before
695 The NATM framework including the en(4), fatm(4), hatm(4), and
696 patm(4) devices has been removed. Consumers should plan a
697 migration before the end-of-life date for FreeBSD 11.
700 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
701 diff has not been implemented, if those are needed a newer version of
702 GNU diff is available via the diffutils package under the gdiff name.
705 As of r316810 for ipfilter, keep frags is no longer assumed when
706 keep state is specified in a rule. r316810 aligns ipfilter with
707 documentation in man pages separating keep frags from keep state.
708 This allows keep state to be specified without forcing keep frags
709 and allows keep frags to be specified independently of keep state.
710 To maintain previous behaviour, also specify keep frags with
711 keep state (as documented in ipf.conf.5).
714 arm64 builds now use the base system LLD 4.0.0 linker by default,
715 instead of requiring that the aarch64-binutils port or package be
716 installed. To continue using aarch64-binutils, set
717 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
720 The UDP optimization in entry 20160818 that added the sysctl
721 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
722 packets will no longer be treated as L3 broadcast packets.
725 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
726 use any explicitly assigned loopback address available in the jail
727 instead of using the first assigned address of the jail.
730 The ctl.ko module no longer implements the iSCSI target frontend:
731 cfiscsi.ko does instead.
733 If building cfiscsi.ko as a kernel module, the module can be loaded
734 via one of the following methods:
735 - `cfiscsi_load="YES"` in loader.conf(5).
736 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
737 - ctladm(8)/ctld(8), when compiled with iSCSI support
738 (`WITH_ISCSI=yes` in src.conf(5))
740 Please see cfiscsi(4) for more details.
743 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
744 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
745 same source (previously, the dependency of mmcsd.ko on mmc.ko was
746 missing, but mmcsd.ko now will refuse to load if it is incompatible
750 The syntax of ipfw(8) named states was changed to avoid ambiguity.
751 If you have used named states in the firewall rules, you need to modify
752 them after installworld and before rebooting. Now named states must
753 be prefixed with colon.
756 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
757 removed as the userland we provide cannot use them. The KMS version
758 (sys/dev/drm2) supports the same hardware.
761 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
762 Please see the 20141231 entry below for information about prerequisites
763 and upgrading, if you are not already using clang 3.5.0 or higher.
766 The code that provides support for ZFS .zfs/ directory functionality
767 has been reimplemented. It's not possible now to create a snapshot
768 by mkdir under .zfs/snapshot/. That should be the only user visible
772 EISA bus support has been removed. The WITH_EISA option is no longer
776 MCA bus support has been removed.
779 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
780 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
783 The EM_MULTIQUEUE kernel configuration option is deprecated now that
784 the em(4) driver conforms to iflib specifications.
787 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
788 IFLIB. If you have a custom kernel configuration that excludes em(4)
789 but you use igb(4), you need to re-add em(4) to your custom configuration.
792 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
793 Please see the 20141231 entry below for information about prerequisites
794 and upgrading, if you are not already using clang 3.5.0 or higher.
797 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
798 Please see the 20141231 entry below for information about prerequisites
799 and upgrading, if you are not already using clang 3.5.0 or higher.
802 The layout of the pmap structure has changed for powerpc to put the pmap
803 statistics at the front for all CPU variations. libkvm(3) and all tools
804 that link against it need to be recompiled.
807 isl(4) and cyapa(4) drivers now require a new driver,
808 chromebook_platform(4), to work properly on Chromebook-class hardware.
809 On other types of hardware the drivers may need to be configured using
810 device hints. Please see the corresponding manual pages for details.
813 The urtwn(4) driver was merged into rtwn(4) and now consists of
814 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
816 Also, firmware for RTL8188CE was renamed due to possible name
817 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
820 GNU rcs has been removed from base. It is available as packages:
821 - rcs: Latest GPLv3 GNU rcs version.
822 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
826 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
827 modules now requires that the kernel configuration contain the
828 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
831 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
832 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
835 Relocatable object files with the extension of .So have been renamed
836 to use an extension of .pico instead. The purpose of this change is
837 to avoid a name clash with shared libraries on case-insensitive file
838 systems. On those file systems, foo.So is the same file as foo.so.
841 GNU rcs has been turned off by default. It can (temporarily) be built
842 again by adding WITH_RCS knob in src.conf.
843 Otherwise, GNU rcs is available from packages:
844 - rcs: Latest GPLv3 GNU rcs version.
845 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
848 The backup_uses_rcs functionality has been removed from rc.subr.
851 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
852 two separate components, QUEUE_MACRO_DEBUG_TRACE and
853 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
854 QUEUE_MACRO_DEBUG behavior.
857 r304787 changed some ioctl interfaces between the iSCSI userspace
858 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
859 rebuilt to work with new kernels. __FreeBSD_version has been bumped
863 The UDP receive code has been updated to only treat incoming UDP
864 packets that were addressed to an L2 broadcast address as L3
865 broadcast packets. It is not expected that this will affect any
866 standards-conforming UDP application. The new behaviour can be
867 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
871 Remove the openbsd_poll system call.
872 __FreeBSD_version has been bumped because of this.
875 The stable/11 branch has been created from head@r302406.
878 The libc stub for the pipe(2) system call has been replaced with
879 a wrapper that calls the pipe2(2) system call and the pipe(2)
880 system call is now only implemented by the kernels that include
881 "options COMPAT_FREEBSD10" in their config file (this is the
882 default). Users should ensure that this option is enabled in
883 their kernel or upgrade userspace to r302092 before upgrading their
887 CAM will now strip leading spaces from SCSI disks' serial numbers.
888 This will affect users who create UFS filesystems on SCSI disks using
889 those disk's diskid device nodes. For example, if /etc/fstab
890 previously contained a line like
891 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
892 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
893 transforms like gmirror may also be affected. ZFS users should
897 The bitstring(3) API has been updated with new functionality and
898 improved performance. But it is binary-incompatible with the old API.
899 Objects built with the new headers may not be linked against objects
900 built with the old headers.
903 The brk and sbrk functions have been removed from libc on arm64.
904 Binutils from ports has been updated to not link to these
905 functions and should be updated to the latest version before
906 installing a new libc.
909 The armv6 port now defaults to hard float ABI. Limited support
910 for running both hardfloat and soft float on the same system
911 is available using the libraries installed with -DWITH_LIBSOFT.
912 This has only been tested as an upgrade path for installworld
913 and packages may fail or need manual intervention to run. New
914 packages will be needed.
916 To update an existing self-hosted armv6hf system, you must add
917 TARGET_ARCH=armv6 on the make command line for both the build
918 and the install steps.
921 Kernel modules compiled outside of a kernel build now default to
922 installing to /boot/modules instead of /boot/kernel. Many kernel
923 modules built this way (such as those in ports) already overrode
924 KMODDIR explicitly to install into /boot/modules. However,
925 manually building and installing a module from /sys/modules will
926 now install to /boot/modules instead of /boot/kernel.
929 The CAM I/O scheduler has been committed to the kernel. There should be
930 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
931 list of known rogues that claim support for this but actually corrupt
932 data is believed to be complete, be on the lookout for data
933 corruption. The known rogue list is believed to be complete:
935 o Crucial MX100, M550 drives with MU01 firmware.
936 o Micron M510 and M550 drives with MU01 firmware.
937 o Micron M500 prior to MU07 firmware
938 o Samsung 830, 840, and 850 all firmwares
939 o FCCT M500 all firmwares
941 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
942 with working NCQ TRIM. For Micron branded drives, see your sales rep for
943 updated firmware. Black listed drives will work correctly because these
944 drives work correctly so long as no NCQ TRIMs are sent to them. Given
945 this list is the same as found in Linux, it's believed there are no
946 other rogues in the market place. All other models from the above
949 To be safe, if you are at all concerned, you can quirk each of your
950 drives to prevent NCQ from being sent by setting:
951 kern.cam.ada.X.quirks="0x2"
952 in loader.conf. If the drive requires the 4k sector quirk, set the
956 The FAST_DEPEND build option has been removed and its functionality is
957 now the one true way. The old mkdep(1) style of 'make depend' has
958 been removed. See 20160311 for further details.
961 Resource range types have grown from unsigned long to uintmax_t. All
962 drivers, and anything using libdevinfo, need to be recompiled.
965 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
966 builds. It no longer runs mkdep(1) during 'make depend', and the
967 'make depend' stage can safely be skipped now as it is auto ran
968 when building 'make all' and will generate all SRCS and DPSRCS before
969 building anything else. Dependencies are gathered at compile time with
970 -MF flags kept in separate .depend files per object file. Users should
971 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
975 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
976 kernel modules. Therefore, if you load any kernel modules at boot time,
977 please install the boot loaders after you install the kernel, but before
981 make buildkernel KERNCONF=YOUR_KERNEL_HERE
982 make installkernel KERNCONF=YOUR_KERNEL_HERE
983 make -C sys/boot install
984 <reboot in single user>
986 Then follow the usual steps, described in the General Notes section,
990 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
991 see the 20141231 entry below for information about prerequisites and
992 upgrading, if you are not already using clang 3.5.0 or higher.
995 The AIO subsystem is now a standard part of the kernel. The
996 VFS_AIO kernel option and aio.ko kernel module have been removed.
997 Due to stability concerns, asynchronous I/O requests are only
998 permitted on sockets and raw disks by default. To enable
999 asynchronous I/O requests on all file types, set the
1000 vfs.aio.enable_unsafe sysctl to a non-zero value.
1003 The ELF object manipulation tool objcopy is now provided by the
1004 ELF Tool Chain project rather than by GNU binutils. It should be a
1005 drop-in replacement, with the addition of arm64 support. The
1006 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1007 to obtain the GNU version if necessary.
1010 Building ZFS pools on top of zvols is prohibited by default. That
1011 feature has never worked safely; it's always been prone to deadlocks.
1012 Using a zvol as the backing store for a VM guest's virtual disk will
1013 still work, even if the guest is using ZFS. Legacy behavior can be
1014 restored by setting vfs.zfs.vol.recursive=1.
1017 The NONE and HPN patches has been removed from OpenSSH. They are
1018 still available in the security/openssh-portable port.
1021 With the addition of ypldap(8), a new _ypldap user is now required
1022 during installworld. "mergemaster -p" can be used to add the user
1023 prior to installworld, as documented in the handbook.
1026 The tftp loader (pxeboot) now uses the option root-path directive. As a
1027 consequence it no longer looks for a pxeboot.4th file on the tftp
1028 server. Instead it uses the regular /boot infrastructure as with the
1032 The code to start recording plug and play data into the modules has
1033 been committed. While the old tools will properly build a new kernel,
1034 a number of warnings about "unknown metadata record 4" will be produced
1035 for an older kldxref. To avoid such warnings, make sure to rebuild
1036 the kernel toolchain (or world). Make sure that you have r292078 or
1037 later when trying to build 292077 or later before rebuilding.
1040 Debug data files are now built by default with 'make buildworld' and
1041 installed with 'make installworld'. This facilitates debugging but
1042 requires more disk space both during the build and for the installed
1043 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1047 r291527 changed the internal interface between the nfsd.ko and
1048 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1049 __FreeBSD_version has been bumped because of this.
1052 Add support for unicode collation strings leads to a change of
1053 order of files listed by ls(1) for example. To get back to the old
1054 behaviour, set LC_COLLATE environment variable to "C".
1056 Databases administrators will need to reindex their databases given
1057 collation results will be different.
1059 Due to a bug in install(1) it is recommended to remove the ancient
1060 locales before running make installworld.
1062 rm -rf /usr/share/locale/*
1065 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1066 libcrypto.so.7 or libssl.so.7 must be recompiled.
1069 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1070 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1071 should be replaced with isp_2400 and isp_2500 modules respectively.
1074 The build previously allowed using 'make -n' to not recurse into
1075 sub-directories while showing what commands would be executed, and
1076 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1077 and 'make -N' will not.
1080 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1081 and etcupdate will now use this file. A custom sendmail.cf is now
1082 updated via this mechanism rather than via installworld. If you had
1083 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1084 want to remove the exclusion or change it to "always install".
1085 /etc/mail/sendmail.cf is now managed the same way regardless of
1086 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1087 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1090 Compatibility shims for legacy ATA device names have been removed.
1091 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1092 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1093 environment variables, /dev/ad* and /dev/ar* symbolic links.
1096 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1097 Please see the 20141231 entry below for information about prerequisites
1098 and upgrading, if you are not already using clang 3.5.0 or higher.
1101 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1102 and renamed from .symbols to .debug. This reduces the size requirements
1103 on the boot partition or file system and provides consistency with
1104 userland debug files.
1106 When using the supported kernel installation method the
1107 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1108 as is done with /boot/kernel.
1110 Developers wishing to maintain the historical behavior of installing
1111 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1114 The wireless drivers had undergone changes that remove the 'parent
1115 interface' from the ifconfig -l output. The rc.d network scripts
1116 used to check presence of a parent interface in the list, so old
1117 scripts would fail to start wireless networking. Thus, etcupdate(3)
1118 or mergemaster(8) run is required after kernel update, to update your
1119 rc.d scripts in /etc.
1122 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1123 These configurations are now automatically interpreted as
1124 'scrub fragment reassemble'.
1127 Kernel-loadable modules for the random(4) device are back. To use
1128 them, the kernel must have
1131 options RANDOM_LOADABLE
1133 kldload(8) can then be used to load random_fortuna.ko
1134 or random_yarrow.ko. Please note that due to the indirect
1135 function calls that the loadable modules need to provide,
1136 the build-in variants will be slightly more efficient.
1138 The random(4) kernel option RANDOM_DUMMY has been retired due to
1139 unpopularity. It was not all that useful anyway.
1142 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1143 Control over building the ELF Tool Chain tools is now provided by
1144 the WITHOUT_TOOLCHAIN knob.
1147 The polarity of Pulse Per Second (PPS) capture events with the
1148 uart(4) driver has been corrected. Prior to this change the PPS
1149 "assert" event corresponded to the trailing edge of a positive PPS
1150 pulse and the "clear" event was the leading edge of the next pulse.
1152 As the width of a PPS pulse in a typical GPS receiver is on the
1153 order of 1 millisecond, most users will not notice any significant
1154 difference with this change.
1156 Anyone who has compensated for the historical polarity reversal by
1157 configuring a negative offset equal to the pulse width will need to
1158 remove that workaround.
1161 The default group assigned to /dev/dri entries has been changed
1162 from 'wheel' to 'video' with the id of '44'. If you want to have
1163 access to the dri devices please add yourself to the video group
1166 # pw groupmod video -m $USER
1169 The menu.rc and loader.rc files will now be replaced during
1170 upgrades. Please migrate local changes to menu.rc.local and
1171 loader.rc.local instead.
1174 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1175 strings and strip have been removed. The src.conf(5) knob
1176 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1179 As ZFS requires more kernel stack pages than is the default on some
1180 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1181 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1183 Please consider using 'options KSTACK_PAGES=X' where X is greater
1184 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1187 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1188 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1189 default, i.e., they will not contain "::". For example, instead
1190 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1191 to have a more specific match, such as different map entries for
1192 IPv6:0:0 vs IPv6:0. This change requires that configuration
1193 data (including maps, files, classes, custom ruleset, etc.) must
1194 use the same format, so make certain such configuration data is
1195 upgrading. As a very simple check search for patterns like
1196 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1197 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1198 the cf option UseCompressedIPv6Addresses.
1201 The default kernel entropy-processing algorithm is now
1202 Fortuna, replacing Yarrow.
1204 Assuming you have 'device random' in your kernel config
1205 file, the configurations allow a kernel option to override
1206 this default. You may choose *ONE* of:
1208 options RANDOM_YARROW # Legacy /dev/random algorithm.
1209 options RANDOM_DUMMY # Blocking-only driver.
1211 If you have neither, you get Fortuna. For most people,
1212 read no further, Fortuna will give a /dev/random that works
1213 like it always used to, and the difference will be irrelevant.
1215 If you remove 'device random', you get *NO* kernel-processed
1216 entropy at all. This may be acceptable to folks building
1217 embedded systems, but has complications. Carry on reading,
1218 and it is assumed you know what you need.
1220 *PLEASE* read random(4) and random(9) if you are in the
1221 habit of tweaking kernel configs, and/or if you are a member
1222 of the embedded community, wanting specific and not-usual
1223 behaviour from your security subsystems.
1225 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1226 random', you will NOT have a functioning /dev/random, and
1227 many cryptographic features will not work, including SSH.
1228 You may also find strange behaviour from the random(3) set
1229 of library functions, in particular sranddev(3), srandomdev(3)
1230 and arc4random(3). The reason for this is that the KERN_ARND
1231 sysctl only returns entropy if it thinks it has some to
1232 share, and with RANDOM_DUMMY or no 'device random' this
1236 An additional fix for the issue described in the 20150614 sendmail
1237 entry below has been committed in revision 284717.
1240 FreeBSD's old make (fmake) has been removed from the system. It is
1241 available as the devel/fmake port or via pkg install fmake.
1244 The fix for the issue described in the 20150614 sendmail entry
1245 below has been committed in revision 284436. The work
1246 around described in that entry is no longer needed unless the
1247 default setting is overridden by a confDH_PARAMETERS configuration
1248 setting of '5' or pointing to a 512 bit DH parameter file.
1251 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1252 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1253 and devel/kyua to version 0.20+ and adjust any calling code to work
1254 with Kyuafile and kyua.
1257 The import of openssl to address the FreeBSD-SA-15:10.openssl
1258 security advisory includes a change which rejects handshakes
1259 with DH parameters below 768 bits. sendmail releases prior
1260 to 8.15.2 (not yet released), defaulted to a 512 bit
1261 DH parameter setting for client connections. To work around
1262 this interoperability, sendmail can be configured to use a
1263 2048 bit DH parameter by:
1265 1. Edit /etc/mail/`hostname`.mc
1266 2. If a setting for confDH_PARAMETERS does not exist or
1267 exists and is set to a string beginning with '5',
1268 replace it with '2'.
1269 3. If a setting for confDH_PARAMETERS exists and is set to
1270 a file path, create a new file with:
1271 openssl dhparam -out /path/to/file 2048
1272 4. Rebuild the .cf file:
1273 cd /etc/mail/; make; make install
1274 5. Restart sendmail:
1275 cd /etc/mail/; make restart
1277 A sendmail patch is coming, at which time this file will be
1281 Generation of legacy formatted entries have been disabled by default
1282 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1283 entries were converted to use the new format by default when the new,
1284 machine independent format have been added and supported since FreeBSD
1287 Please see the pwd_mkdb(8) manual page for further details.
1290 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1291 20141231 entry below for information about prerequisites and upgrading,
1292 if you are not already using 3.5.0 or higher.
1295 TI platform code switched to using vendor DTS files and this update
1296 may break existing systems running on Beaglebone, Beaglebone Black,
1299 - dtb files should be regenerated/reinstalled. Filenames are the
1300 same but content is different now
1301 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1302 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1303 addressing scheme is now pin 25 on /dev/gpioc3.
1304 - Pandaboard: /etc/ttys should be updated, serial console device is
1305 now /dev/ttyu2, not /dev/ttyu0
1308 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1309 If you need the GNU extension from groff soelim(1), install groff
1310 from package: pkg install groff, or via ports: textproc/groff.
1313 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1314 defined in symlink(7); previously symlinks were silently ignored.
1317 The const qualifier has been removed from iconv(3) to comply with
1318 POSIX. The ports tree is aware of this from r384038 onwards.
1321 Libraries specified by LIBADD in Makefiles must have a corresponding
1322 DPADD_<lib> variable to ensure correct dependencies. This is now
1323 enforced in src.libnames.mk.
1326 From legacy ata(4) driver was removed support for SATA controllers
1327 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1328 Kernel modules ataahci and ataadaptec were removed completely,
1329 replaced by ahci and mvs modules respectively.
1332 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1333 the 20141231 entry below for information about prerequisites and
1334 upgrading, if you are not already using 3.5.0 or higher.
1337 The 32-bit PowerPC kernel has been changed to a position-independent
1338 executable. This can only be booted with a version of loader(8)
1339 newer than January 31, 2015, so make sure to update both world and
1340 kernel before rebooting.
1343 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1344 but before r278950, the RNG was not seeded properly. Immediately
1345 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1346 ssh keys or openssl keys) that were generated w/ a kernel from that
1347 range. This does not affect programs that directly used /dev/random
1348 or /dev/urandom. All userland uses of arc4random(3) are affected.
1351 The autofs(4) ABI was changed in order to restore binary compatibility
1352 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1353 with the new kernel.
1356 The powerpc64 kernel has been changed to a position-independent
1357 executable. This can only be booted with a new version of loader(8),
1358 so make sure to update both world and kernel before rebooting.
1361 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1362 only release, no new features have been added. Please see the 20141231
1363 entry below for information about prerequisites and upgrading, if you
1364 are not already using 3.5.0.
1367 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1368 taken from the ELF Tool Chain project rather than GNU binutils. They
1369 should be drop-in replacements, with the addition of arm64 support.
1370 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1371 binutils tools, if necessary. See 20150805 for updated information.
1374 The default Unbound configuration now enables remote control
1375 using a local socket. Users who have already enabled the
1376 local_unbound service should regenerate their configuration
1377 by running "service local_unbound setup" as root.
1380 The GNU texinfo and GNU info pages have been removed.
1381 To be able to view GNU info pages please install texinfo from ports.
1384 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1386 As of this release, a prerequisite for building clang, llvm and lldb is
1387 a C++11 capable compiler and C++11 standard library. This means that to
1388 be able to successfully build the cross-tools stage of buildworld, with
1389 clang as the bootstrap compiler, your system compiler or cross compiler
1390 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1391 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1394 On any standard FreeBSD 10.x or 11.x installation, where clang and
1395 libc++ are on by default (that is, on x86 or arm), this should work out
1398 On 9.x installations where clang is enabled by default, e.g. on x86 and
1399 powerpc, libc++ will not be enabled by default, so libc++ should be
1400 built (with clang) and installed first. If both clang and libc++ are
1401 missing, build clang first, then use it to build libc++.
1403 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1404 the instructions for 9.x above.
1406 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1407 default, and do not build clang.
1409 Many embedded systems are resource constrained, and will not be able to
1410 build clang in a reasonable time, or in some cases at all. In those
1411 cases, cross building bootable systems on amd64 is a workaround.
1413 This new version of clang introduces a number of new warnings, of which
1414 the following are most likely to appear:
1418 This warns in two cases, for both C and C++:
1419 * When the code is trying to take the absolute value of an unsigned
1420 quantity, which is effectively a no-op, and almost never what was
1421 intended. The code should be fixed, if at all possible. If you are
1422 sure that the unsigned quantity can be safely cast to signed, without
1423 loss of information or undefined behavior, you can add an explicit
1424 cast, or disable the warning.
1426 * When the code is trying to take an absolute value, but the called
1427 abs() variant is for the wrong type, which can lead to truncation.
1428 If you want to disable the warning instead of fixing the code, please
1429 make sure that truncation will not occur, or it might lead to unwanted
1432 -Wtautological-undefined-compare and
1433 -Wundefined-bool-conversion
1435 These warn when C++ code is trying to compare 'this' against NULL, while
1436 'this' should never be NULL in well-defined C++ code. However, there is
1437 some legacy (pre C++11) code out there, which actively abuses this
1438 feature, which was less strictly defined in previous C++ versions.
1440 Squid and openjdk do this, for example. The warning can be turned off
1441 for C++98 and earlier, but compiling the code in C++11 mode might result
1442 in unexpected behavior; for example, the parts of the program that are
1443 unreachable could be optimized away.
1446 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1447 kernel sources have been removed. The .h files remain, since some
1448 utilities include them. This will need to be fixed later.
1449 If "mount -t oldnfs ..." is attempted, it will fail.
1450 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1451 the utilities will report errors.
1454 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1455 directories to top level SUBDIR variable when their parent
1456 directory is included in LOCAL_DIRS. Users with build systems with
1457 such hierarchies and without SUBDIR entries in the parent
1458 directory Makefiles should add them or add the directories to
1462 faith(4) and faithd(8) have been removed from the base system. Faith
1463 has been obsolete for a very long time.
1466 vt(4), the new console driver, is enabled by default. It brings
1467 support for Unicode and double-width characters, as well as
1468 support for UEFI and integration with the KMS kernel video
1471 You may need to update your console settings in /etc/rc.conf,
1472 most probably the keymap. During boot, /etc/rc.d/syscons will
1473 indicate what you need to do.
1475 vt(4) still has issues and lacks some features compared to
1476 syscons(4). See the wiki for up-to-date information:
1477 https://wiki.freebsd.org/Newcons
1479 If you want to keep using syscons(4), you can do so by adding
1480 the following line to /boot/loader.conf:
1484 pjdfstest has been integrated into kyua as an opt-in test suite.
1485 Please see share/doc/pjdfstest/README for more details on how to
1489 gperf has been removed from the base system for architectures
1490 that use clang. Ports that require gperf will obtain it from the
1494 pjdfstest has been moved from tools/regression/pjdfstest to
1498 At svn r271982, The default linux compat kernel ABI has been adjusted
1499 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1500 update. If you wish to continue using the linux-f10 compat ports,
1501 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1502 encouraged to update their linux-compat packages to linux-c6 during
1503 their next update cycle.
1506 The ofwfb driver, used to provide a graphics console on PowerPC when
1507 using vt(4), no longer allows mmap() of all physical memory. This
1508 will prevent Xorg on PowerPC with some ATI graphics cards from
1509 initializing properly unless x11-servers/xorg-server is updated to
1513 The xdev targets have been converted to using TARGET and
1514 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1517 The default unbound configuration has been modified to address
1518 issues with reverse lookups on networks that use private
1519 address ranges. If you use the local_unbound service, run
1520 "service local_unbound setup" as root to regenerate your
1521 configuration, then "service local_unbound reload" to load the
1525 The GNU texinfo and GNU info pages are not built and installed
1526 anymore, WITH_INFO knob has been added to allow to built and install
1528 UPDATE: see 20150102 entry on texinfo's removal
1531 The GNU readline library is now an INTERNALLIB - that is, it is
1532 statically linked into consumers (GDB and variants) in the base
1533 system, and the shared library is no longer installed. The
1534 devel/readline port is available for third party software that
1538 The Itanium architecture (ia64) has been removed from the list of
1539 known architectures. This is the first step in the removal of the
1543 Commit r268115 has added NFSv4.1 server support, merged from
1544 projects/nfsv4.1-server. Since this includes changes to the
1545 internal interfaces between the NFS related modules, a full
1546 build of the kernel and modules will be necessary.
1547 __FreeBSD_version has been bumped.
1550 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1551 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1552 which differs from the behaviour controlled by this knob.)
1555 Maximal length of the serial number in CTL was increased from 16 to
1556 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1557 and ctld, need to be rebuilt to work with a new kernel.
1560 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1561 1 respectively to match the upstream numbers. They were out of
1562 sync because, when they were originally added to FreeBSD, the
1563 upstream versions were not respected. These libraries are private
1564 and not yet built by default, so renumbering them should be a
1565 non-issue. However, unclean source trees will yield broken test
1566 programs once the operator executes "make delete-old-libs" after a
1567 "make installworld".
1569 Additionally, the atf-sh binary was made private by moving it into
1570 /usr/libexec/. Already-built shell test programs will keep the
1571 path to the old binary so they will break after "make delete-old"
1574 If you are using WITH_TESTS=yes (not the default), wipe the object
1575 tree and rebuild from scratch to prevent spurious test failures.
1576 This is only needed once: the misnumbered libraries and misplaced
1577 binaries have been added to OptionalObsoleteFiles.inc so they will
1578 be removed during a clean upgrade.
1581 Clang and llvm have been upgraded to 3.4.1 release.
1584 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1585 be removed to avoid issues in the future (and has been added to
1589 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1590 past, it affected all builds that used the bsd.*.mk files. The old
1591 behavior was a bug, but people may have relied upon it. To get this
1592 behavior back, you can .include /etc/src.conf from /etc/make.conf
1593 (which is still global and isn't changed). This also changes the
1594 behavior of incremental builds inside the tree of individual
1595 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1596 Although this has survived make universe and some upgrade scenarios,
1597 other upgrade scenarios may have broken. At least one form of
1598 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1599 as well... In cases where MAKESYSPATH isn't working with this
1600 setting, you'll need to set it to the full path to your tree.
1602 One side effect of all this cleaning up is that bsd.compiler.mk
1603 is no longer implicitly included by bsd.own.mk. If you wish to
1604 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1608 The lindev device has been removed since /dev/full has been made a
1609 standard device. __FreeBSD_version has been bumped.
1612 The knob WITHOUT_VI was added to the base system, which controls
1613 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1614 in order to reorder files share/termcap and didn't build ex(1) as a
1615 build tool, so building/installing with WITH_VI is highly advised for
1616 build hosts for older releases.
1618 This issue has been fixed in stable/9 and stable/10 in r277022 and
1619 r276991, respectively.
1622 The YES_HESIOD knob has been removed. It has been obsolete for
1623 a decade. Please move to using WITH_HESIOD instead or your builds
1624 will silently lack HESIOD.
1627 The uart(4) driver has been changed with respect to its handling
1628 of the low-level console. Previously the uart(4) driver prevented
1629 any process from changing the baudrate or the CLOCAL and HUPCL
1630 control flags. By removing the restrictions, operators can make
1631 changes to the serial console port without having to reboot.
1632 However, when getty(8) is started on the serial device that is
1633 associated with the low-level console, a misconfigured terminal
1634 line in /etc/ttys will now have a real impact.
1635 Before upgrading the kernel, make sure that /etc/ttys has the
1636 serial console device configured as 3wire without baudrate to
1637 preserve the previous behaviour. E.g:
1638 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1641 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1642 to improve performance. To re-enable it, if needed, run rpcbind
1643 with command line option -W.
1646 Switched back to the GPL dtc compiler due to updates in the upstream
1647 dts files not being supported by the BSDL dtc compiler. You will need
1648 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1649 may result while building dtb files during a kernel build if you fail
1650 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1653 Clang and llvm have been upgraded to 3.4 release.
1656 The nve(4) driver has been removed. Please use the nfe(4) driver
1657 for NVIDIA nForce MCP Ethernet adapters instead.
1660 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1661 This could cause certain C++ applications using shared libraries built
1662 against the previous version of libc++ to crash. The incompatibility
1663 has now been fixed, but any C++ applications or shared libraries built
1664 between r261283 and r261801 should be recompiled.
1667 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1668 capability mode support. Please note that enabling the feature in
1669 kernel is still highly recommended.
1672 OpenSSH is now built with sandbox support, and will use sandbox as
1673 the default privilege separation method. This requires Capsicum
1674 capability mode support in kernel.
1677 The libelf and libdwarf libraries have been updated to newer
1678 versions from upstream. Shared library version numbers for
1679 these two libraries were bumped. Any ports or binaries
1680 requiring these two libraries should be recompiled.
1681 __FreeBSD_version is bumped to 1100006.
1684 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1685 instead of providing an explicit one, this would prevent such
1686 Makefile from providing its own Kyuafile in the future during
1687 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1688 intervention is needed to clean an objdir if you use NO_CLEAN:
1689 # find /usr/obj -name Kyuafile | xargs rm -f
1692 The behavior of gss_pseudo_random() for the krb5 mechanism
1693 has changed, for applications requesting a longer random string
1694 than produced by the underlying enctype's pseudo-random() function.
1695 In particular, the random string produced from a session key of
1696 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1697 be different at the 17th octet and later, after this change.
1698 The counter used in the PRF+ construction is now encoded as a
1699 big-endian integer in accordance with RFC 4402.
1700 __FreeBSD_version is bumped to 1100004.
1703 The WITHOUT_ATF build knob has been removed and its functionality
1704 has been subsumed into the more generic WITHOUT_TESTS. If you were
1705 using the former to disable the build of the ATF libraries, you
1706 should change your settings to use the latter.
1709 The default version of mtree is nmtree which is obtained from
1710 NetBSD. The output is generally the same, but may vary
1711 slightly. If you found you need identical output adding
1712 "-F freebsd9" to the command line should do the trick. For the
1713 time being, the old mtree is available as fmtree.
1716 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1717 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1718 1.1.4_8 and verify bsdyml not linked in, before running "make
1720 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1722 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1725 The stable/10 branch has been created in subversion from head
1732 Avoid using make -j when upgrading. While generally safe, there are
1733 sometimes problems using -j to upgrade. If your upgrade fails with
1734 -j, please try again without -j. From time to time in the past there
1735 have been problems using -j with buildworld and/or installworld. This
1736 is especially true when upgrading between "distant" versions (eg one
1737 that cross a major release boundary or several minor releases, or when
1738 several months have passed on the -current branch).
1740 Sometimes, obscure build problems are the result of environment
1741 poisoning. This can happen because the make utility reads its
1742 environment when searching for values for global variables. To run
1743 your build attempts in an "environmental clean room", prefix all make
1744 commands with 'env -i '. See the env(1) manual page for more details.
1746 When upgrading from one major version to another it is generally best to
1747 upgrade to the latest code in the currently installed branch first, then
1748 do an upgrade to the new branch. This is the best-tested upgrade path,
1749 and has the highest probability of being successful. Please try this
1750 approach if you encounter problems with a major version upgrade. Since
1751 the stable 4.x branch point, one has generally been able to upgrade from
1752 anywhere in the most recent stable branch to head / current (or even the
1753 last couple of stable branches). See the top of this file when there's
1756 When upgrading a live system, having a root shell around before
1757 installing anything can help undo problems. Not having a root shell
1758 around can lead to problems if pam has changed too much from your
1759 starting point to allow continued authentication after the upgrade.
1761 This file should be read as a log of events. When a later event changes
1762 information of a prior event, the prior event should not be deleted.
1763 Instead, a pointer to the entry with the new information should be
1764 placed in the old entry. Readers of this file should also sanity check
1765 older entries before relying on them blindly. Authors of new entries
1766 should write them with this in mind.
1770 When upgrading the boot ZFS pool to a new version, always follow
1773 1.) recompile and reinstall the ZFS boot loader and boot block
1774 (this is part of "make buildworld" and "make installworld")
1776 2.) update the ZFS boot block on your boot drive
1778 The following example updates the ZFS boot block on the first
1779 partition (freebsd-boot) of a GPT partitioned drive ada0:
1780 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1782 Non-boot pools do not need these updates.
1786 If you are updating from a prior version of FreeBSD (even one just
1787 a few days old), you should follow this procedure. It is the most
1788 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1790 make kernel-toolchain
1791 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1792 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1794 To test a kernel once
1795 ---------------------
1796 If you just want to boot a kernel once (because you are not sure
1797 if it works, or if you want to boot a known bad kernel to provide
1798 debugging information) run
1799 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1800 nextboot -k testkernel
1802 To rebuild everything and install it on the current system.
1803 -----------------------------------------------------------
1804 # Note: sometimes if you are running current you gotta do more than
1805 # is listed here if you are upgrading from a really old current.
1807 <make sure you have good level 0 dumps>
1809 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1810 make installkernel KERNCONF=YOUR_KERNEL_HERE
1812 <reboot in single user> [3]
1819 To cross-install current onto a separate partition
1820 --------------------------------------------------
1821 # In this approach we use a separate partition to hold
1822 # current's root, 'usr', and 'var' directories. A partition
1823 # holding "/", "/usr" and "/var" should be about 2GB in
1826 <make sure you have good level 0 dumps>
1829 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1830 <maybe newfs current's root partition>
1831 <mount current's root partition on directory ${CURRENT_ROOT}>
1832 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1833 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1834 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1835 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1836 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1837 <reboot into current>
1838 <do a "native" rebuild/install as described in the previous section>
1839 <maybe install compatibility libraries from ports/misc/compat*>
1843 To upgrade in-place from stable to current
1844 ----------------------------------------------
1845 <make sure you have good level 0 dumps>
1847 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1848 make installkernel KERNCONF=YOUR_KERNEL_HERE
1850 <reboot in single user> [3]
1857 Make sure that you've read the UPDATING file to understand the
1858 tweaks to various things you need. At this point in the life
1859 cycle of current, things change often and you are on your own
1860 to cope. The defaults can also change, so please read ALL of
1861 the UPDATING entries.
1863 Also, if you are tracking -current, you must be subscribed to
1864 freebsd-current@freebsd.org. Make sure that before you update
1865 your sources that you have read and understood all the recent
1866 messages there. If in doubt, please track -stable which has
1867 much fewer pitfalls.
1869 [1] If you have third party modules, such as vmware, you
1870 should disable them at this point so they don't crash your
1873 [3] From the bootblocks, boot -s, and then do
1878 adjkerntz -i # if CMOS is wall time
1879 Also, when doing a major release upgrade, it is required that
1880 you boot into single user mode to do the installworld.
1882 [4] Note: This step is non-optional. Failure to do this step
1883 can result in a significant reduction in the functionality of the
1884 system. Attempting to do it by hand is not recommended and those
1885 that pursue this avenue should read this file carefully, as well
1886 as the archives of freebsd-current and freebsd-hackers mailing lists
1887 for potential gotchas. The -U option is also useful to consider.
1888 See mergemaster(8) for more information.
1890 [5] Usually this step is a no-op. However, from time to time
1891 you may need to do this if you get unknown user in the following
1892 step. It never hurts to do it all the time. You may need to
1893 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1894 install) after the buildworld before this step if you last updated
1895 from current before 20130425 or from -stable before 20130430.
1897 [6] This only deletes old files and directories. Old libraries
1898 can be deleted by "make delete-old-libs", but you have to make
1899 sure that no program is using those libraries anymore.
1901 [8] The new kernel must be able to run existing binaries used by
1902 an installworld. When upgrading across major versions, the new
1903 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1904 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1905 binaries). Failure to do so may leave you with a system that is
1906 hard to boot to recover. A GENERIC kernel will include suitable
1907 compatibility options to run binaries from older branches.
1909 Make sure that you merge any new devices from GENERIC since the
1910 last time you updated your kernel config file.
1912 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1913 "?=" instead of the "=" assignment operator, so that buildworld can
1914 override the CPUTYPE if it needs to.
1916 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1917 not on the command line, or in /etc/make.conf. buildworld will
1918 warn if it is improperly defined.
1921 This file contains a list, in reverse chronological order, of major
1922 breakages in tracking -current. It is not guaranteed to be a complete
1923 list of such breakages, and only contains entries since September 23, 2011.
1924 If you need to see UPDATING entries from before that date, you will need
1925 to fetch an UPDATING file from an older FreeBSD release.
1927 Copyright information:
1929 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1931 Redistribution, publication, translation and use, with or without
1932 modification, in full or in part, in any form or format of this
1933 document are permitted without further permission from the author.
1935 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1936 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1937 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1938 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1939 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1940 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1941 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1942 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1943 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1944 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1945 POSSIBILITY OF SUCH DAMAGE.
1947 Contact Warner Losh if you have any questions about your use of