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