1 Updating Information for FreeBSD stable/12 users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before 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 Upstream DTS from Linux 5.6 was merged and they now have the SID
21 and THS (Secure ID controller and THermal Sensor) node present.
22 The DTB overlays have now been removed from the tree for the H3/H5 and
23 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
24 deal with upstream DTS. If you are using those overlays you need to
25 remove them from loader.conf and update the DTBs on the FAT partition.
28 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
29 been upgraded to 10.0.0. Please see the 20141231 entry below for
30 information about prerequisites and upgrading, if you are not already
31 using clang 3.5.0 or higher.
34 The root certificates of the Mozilla CA Certificate Store have been
35 imported into the base system and can be managed with the certctl(8)
36 utility. If you have installed the security/ca_root_nss port or package
37 with the ETCSYMLINK option (the default), be advised that there may be
38 differences between those included in the port and those included in
39 base due to differences in nss branch used as well as general update
40 frequency. Note also that certctl(8) cannot manage certs in the
41 format used by the security/ca_root_nss port.
44 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
45 been upgraded to 9.0.1. Please see the 20141231 entry below for
46 information about prerequisites and upgrading, if you are not already
47 using clang 3.5.0 or higher.
50 The nctgpio and wbwd drivers have been moved to the superio bus.
51 If you have one of these drivers in a kernel configuration, then
52 you should add device superio to it. If you use one of these drivers
53 as a module and you compile a custom set of modules, then you should
54 add superio to the set.
57 The tap(4) driver has been folded into tun(4), and the module has been
58 renamed to tuntap. You should update any kld_list="if_tap" or
59 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
60 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
61 module instead, and "device tap" or "device tun" entries in kernel
62 config files to select the tuntap device instead.
65 ntpd no longer by default locks its pages in memory, allowing them
66 to be paged out by the kernel. Use rlimit memlock to restore
67 historic BSD behaviour. For example, add "rlimit memlock 32"
68 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
71 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
72 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
73 been removed from mount_fusefs(8). You can safely remove them from
74 your scripts, because they had no effect.
76 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
77 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
78 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
79 sysctls have been removed. If you felt the need to set any of them to
80 a non-default value, please tell asomers@FreeBSD.org why.
83 The fuse(4) module has been renamed to fusefs(4) for consistency with
84 other filesystems. You should update any kld_load="fuse" entries in
85 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
86 "options FUSE" enties in kernel config files.
89 Default permissions on the /var/account/acct file (and copies of it
90 rotated by periodic daily scripts) are changed from 0644 to 0640
91 because the file contains sensitive information that should not be
92 world-readable. If the /var/account directory must be created by
93 rc.d/accounting, the mode used is now 0750. Admins who use the
94 accounting feature are encouraged to change the mode of an existing
95 /var/account directory to 0750 or 0700.
98 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
99 been upgraded to 8.0.1. Please see the 20141231 entry below for
100 information about prerequisites and upgrading, if you are not already
101 using clang 3.5.0 or higher.
104 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
105 functionality needed for the RETPOLINE option should work properly
106 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
109 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
110 8.0.0. Please see the 20141231 entry below for information about
111 prerequisites and upgrading, if you are not already using clang 3.5.0
115 The RETPOLINE option produces non-functional ifunc-using binaries
116 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
117 Once Clang 8 is merged it may be enabled again.
120 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
121 7.0.1. Please see the 20141231 entry below for information about
122 prerequisites and upgrading, if you are not already using clang 3.5.0
126 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
127 compiled into your custom kernel, add 'device xz' statement to the
131 Iflib is no longer unconditionally compiled into the kernel. Drivers
132 using iflib and statically compiled into the kernel, now require
133 the 'device iflib' config option. For the same drivers loaded as
134 modules on kernels not having 'device iflib', the iflib.ko module
135 is loaded automatically.
138 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
139 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
140 servers that have vfs.nfsd.nfs_privport set will only allow mounts
141 from clients using a reserved port#. Since both the FreeBSD and Linux
142 NFSv4 clients use reserved port#s by default, this should not affect
146 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
147 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
148 it produces broken binaries when ifuncs are in use. Users needing
149 GNU ld should install the binutils port or package.
152 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
153 has been converted to a port (misc/ctm) and will be removed from
154 FreeBSD-13. A depreciation warning will be printed to stderr by
155 the ctm command, but the functionality will remain in base for all
159 The stable/12 branch has been created in subversion from head
163 Ports for the DRM modules have been simplified. Now, amd64 users should
164 just install the drm-kmod port. All others should install
167 Graphics hardware that's newer than about 2010 usually works with
168 drm-kmod. For hardware older than 2013, however, some users will need
169 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
170 than 2008 usually only works in drm-legacy-kmod. The graphics team can
171 only commit to hardware made since 2013 due to the complexity of the
172 market and difficulty to test all the older cards effectively. If you
173 have hardware supported by drm-kmod, you are strongly encouraged to use
174 that as you will get better support.
176 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
177 elsewhere, the drm and drm2 modules will be eliminated from the src base
178 soon (with a limited exception for arm). Please update to the package asap
179 and report any issues to x11@freebsd.org.
181 Generally, anybody using the drm*-kmod packages should add
182 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
183 cross-threading surprises, especially with automatic driver
184 loading from X11 startup. These will become the defaults in 13-current
188 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
189 custom kernel and module loading configuration files must be updated
190 accordingly. Moreover, interfaces previous presented as ixlvN to the
191 system are now exposed as iavfN and network configuration files must
192 be adjusted as necessary.
195 OpenSSL has been updated to version 1.1.1. This update included
196 additional various API changes througout the base system. It is
197 important to rebuild third-party software after upgrading. The value
198 of __FreeBSD_version has been bumped accordingly.
201 The legacy DRM modules and drivers have now been added to the loader's
202 module blacklist, in favor of loading them with kld_list in rc.conf(5).
203 The module blacklist may be overridden with the loader.conf(5)
204 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
208 The cam(4) based nda(4) driver will be used over nvd(4) by default on
209 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
210 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
211 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
215 Reproducible build mode is now on by default, in preparation for
216 FreeBSD 12.0. This eliminates build metadata such as the user,
217 host, and time from the kernel (and uname), unless the working tree
218 corresponds to a modified checkout from a version control system.
219 The previous behavior can be obtained by setting the /etc/src.conf
220 knob WITHOUT_REPRODUCIBLE_BUILD.
223 The Yarrow CSPRNG has been removed from the kernel as it has not been
224 supported by its designers since at least 2003. Fortuna has been the
225 default since FreeBSD-11.
228 devctl freeze/thaw have gone into the tree, the rc scripts have been
229 updated to use them and devmatch has been changed. You should update
230 kernel, userland and rc scripts all at the same time.
233 The default interpreter has been switched from 4th to Lua.
234 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
235 interpreter. If you have custom FORTH code you will need to set
236 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
237 src.conf for the build. This will create default hard links between
238 loader and loader_4th instead of loader and loader_lua, the new default.
239 If you are using UEFI it will create the proper hard link to loader.efi.
241 bhyve uses userboot.so. It remains 4th-only until some issues are solved
242 regarding coexisting with multiple versions of FreeBSD are resolved.
245 ls(1) now respects the COLORTERM environment variable used in other
246 systems and software to indicate that a colored terminal is both
247 supported and desired. If ls(1) is suddenly emitting colors, they may
248 be disabled again by either removing the unwanted COLORTERM from your
249 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
250 may not be observed in a future release.
253 The default pager for most commands has been changed to "less". To
254 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
258 The jedec_ts(4) driver has been removed. A superset of its functionality
259 is available in the jedec_dimm(4) driver, and the manpage for that
260 driver includes migration instructions. If you have "device jedec_ts"
261 in your kernel configuration file, it must be removed.
264 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
265 This should have no effect if the kernel is booted via BIOS/legacy boot.
266 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
267 has a buggy firmware that prevents a successful boot due to use of
271 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
272 support has been removed from the tree. These ports were
273 obsolete and/or known to be broken for many years.
276 loader.efi has been augmented to participate more fully in the
277 UEFI boot manager protocol. loader.efi will now look at the
278 BootXXXX environment variable to determine if a specific kernel
279 or root partition was specified. XXXX is derived from BootCurrent.
280 efibootmgr(8) manages these standard UEFI variables.
283 zfsloader's functionality has now been folded into loader.
284 zfsloader is no longer necessary once you've updated your
285 boot blocks. For a transition period, we will install a
286 hardlink for zfsloader to loader to allow a smooth transition
287 until the boot blocks can be updated (hard link because old
288 zfs boot blocks don't understand symlinks).
291 ARM64 now have efifb support, if you want to have serial console
292 on your arm64 board when an screen is connected and the bootloader
293 setup a frambuffer for us to use, just add :
297 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
298 an screen connected as the firmware will setup a framebuffer are that
299 u-boot will expose as an EFI framebuffer.
302 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
303 or take steps to update /etc/passwd before doing installworld on
304 existing systems. Do not skip the "mergemaster -Fp" step before
305 installworld, as described in the update procedures near the bottom
306 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
307 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
308 the ntp config file contain options that change file/dir locations.
309 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
310 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
311 taking steps to ensure that all required files/dirs are accessible
315 Big endian arm support has been removed.
318 The static environment setup in kernel configs is no longer mutually
319 exclusive with the loader(8) environment by default. In order to
320 restore the previous default behavior of disabling the loader(8)
321 environment if a static environment is present, you must specify
322 loader_env.disabled=1 in the static environment.
325 The ABI of syscalls used by management tools like sockstat and
326 netstat has been broken to allow 32-bit binaries to work on
327 64-bit kernels without modification. These programs will need
328 to match the kernel in order to function. External programs may
329 require minor modifications to accommodate a change of type in
330 structures from pointers to 64-bit virtual addresses.
333 On i386 and amd64 atomics are now inlined. Out of tree modules using
334 atomics will need to be rebuilt.
337 The '%I' format in the kern.corefile sysctl limits the number of
338 core files that a process can generate to the number stored in the
339 debug.ncores sysctl. The '%I' format is replaced by the single digit
340 index. Previously, if all indexes were taken the kernel would overwrite
341 only a core file with the highest index in a filename.
342 Currently the system will create a new core file if there is a free
343 index or if all slots are taken it will overwrite the oldest one.
346 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
347 6.0.1. Please see the 20141231 entry below for information about
348 prerequisites and upgrading, if you are not already using clang 3.5.0
352 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
353 needed to be changed to work with it. This change was made with r335763
354 and requires a mergemaster / etcupdate / etc to update the installed file.
357 r334930 changed the interface between the NFS modules, so they all
358 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
361 As of r334391 lld is the default amd64 system linker; it is installed
362 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
366 The kernel / userland interface for devinfo changed, so you'll
367 need a new kernel and userland as a pair for it to work (rebuilding
368 lib/libdevinfo is all that's required). devinfo and devmatch will
369 not work, but everything else will when there's a mismatch.
372 The on-disk format for hwpmc callchain records has changed to include
373 threadid corresponding to a given record. This changes the field offsets
374 and thus requires that libpmcstat be rebuilt before using a kernel
378 The vxge(4) driver has been removed. This driver was introduced into
379 HEAD one week before the Exar left the Ethernet market and is not
380 known to be used. If you have device vxge in your kernel config file
384 The amd64 kernel now requires a ld that supports ifunc to produce a
385 working kernel, either lld or a newer binutils. lld is built by default
386 on amd64, and the 'buildkernel' target uses it automatically. However,
387 it is not the default linker, so building the kernel the traditional
388 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
389 binutils port/package). lld will soon be default, and this requirement
392 NOTE: As of r334391 lld is the default system linker on amd64, and no
393 workaround is necessary.
396 The nxge(4) driver has been removed. This driver was for PCI-X 10g
397 cards made by s2io/Neterion. The company was aquired by Exar and
398 no longer sells or supports Ethernet products. If you have device
399 nxge in your kernel config file it must be removed.
402 The tz database (tzdb) has been updated to 2018e. This version more
403 correctly models time stamps in time zones with negative DST such as
404 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
405 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
406 time zone abbreviations and the tm_isdst flag.
409 The ixgb(4) driver has been removed. This driver was for an early and
410 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
411 quickly shifted to the long lived ixgbe family. If you have device
412 ixgb in your kernel config file it must be removed.
415 The lmc(4) driver has been removed. This was a WAN interface
416 card that was already reportedly rare in 2003, and had an ambiguous
417 license. If you have device lmc in your kernel config file it must
421 Support for Arcnet networks has been removed. If you have device
422 arcnet or device cm in your kernel config file they must be
426 Support for FDDI networks has been removed. If you have device
427 fddi or device fpa in your kernel config file they must be
431 In addition to supporting RFC 3164 formatted messages, the
432 syslogd(8) service is now capable of parsing RFC 5424 formatted
433 log messages. The main benefit of using RFC 5424 is that clients
434 may now send log messages with timestamps containing year numbers,
435 microseconds and time zone offsets.
437 Similarly, the syslog(3) C library function has been altered to
438 send RFC 5424 formatted messages to the local system logging
439 daemon. On systems using syslogd(8), this change should have no
440 negative impact, as long as syslogd(8) and the C library are
441 updated at the same time. On systems using a different system
442 logging daemon, it may be necessary to make configuration
443 adjustments, depending on the software used.
445 When using syslog-ng, add the 'syslog-protocol' flag to local
446 input sources to enable parsing of RFC 5424 formatted messages:
449 unix-dgram("/var/run/log" flags(syslog-protocol));
452 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
453 of the 'imuxsock' module to let messages be processed by the
454 regular RFC 3164/5424 parsing pipeline:
456 module(load="imuxsock" SysSock.UseSpecialParser="off")
458 Do note that these changes only affect communication between local
459 applications and syslogd(8). The format that syslogd(8) uses to
460 store messages on disk or forward messages to other systems
461 remains unchanged. syslogd(8) still uses RFC 3164 for these
462 purposes. Options to customize this behaviour will be added in the
463 future. Utilities that process log files stored in /var/log are
464 thus expected to continue to function as before.
466 __FreeBSD_version has been incremented to 1200061 to denote this
470 Support for token ring networks has been removed. If you
471 have "device token" in your kernel config you should remove
472 it. No device drivers supported token ring.
475 makefs was modified to be able to tag ISO9660 El Torito boot catalog
476 entries as EFI instead of overloading the i386 tag as done previously.
477 The amd64 mkisoimages.sh script used to build amd64 ISO images for
478 release was updated to use this. This may mean that makefs must be
479 updated before "make cdrom" can be run in the release directory. This
480 should be as simple as:
482 $ cd $SRCDIR/usr.sbin/makefs
483 $ make depend all install
486 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
487 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
488 Co-existance for the transition period will come shortly. Booting is a
489 complex environment and test coverage for Lua-enabled loaders has been
490 thin, so it would be prudent to assume it might not work and make
491 provisions for backup boot methods.
494 devmatch functionality has been turned on in devd. It will automatically
495 load drivers for unattached devices. This may cause unexpected drivers to
496 be loaded. Please report any problems to current@ and imp@freebsd.org.
499 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
500 6.0.0. Please see the 20141231 entry below for information about
501 prerequisites and upgrading, if you are not already using clang 3.5.0
505 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
506 This means it is used to link the kernel and userland libraries and
507 executables, but is not yet installed as /usr/bin/ld by default.
509 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
510 WITHOUT_LLD_BOOTSTRAP=yes
513 On i386, pmtimer has been removed. Its functionality has been folded
514 into apm. It was a no-op on ACPI in current for a while now (but was still
515 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
516 from kernel config files.
519 The use of RSS hash from the network card aka flowid has been
520 disabled by default for lagg(4) as it's currently incompatible with
521 the lacp and loadbalance protocols.
523 This can be re-enabled by setting the following in loader.conf:
524 net.link.lagg.default_use_flowid="1"
527 The SW_WATCHDOG option is no longer necessary to enable the
528 hardclock-based software watchdog if no hardware watchdog is
529 configured. As before, SW_WATCHDOG will cause the software
530 watchdog to be enabled even if a hardware watchdog is configured.
533 r326887 fixes the issue described in the 20171214 UPDATING entry.
534 r326888 flips the switch back to building GELI support always.
537 r362593 broke ZFS + GELI support for reasons unknown. However,
538 it also broke ZFS support generally, so GELI has been turned off
539 by default as the lesser evil in r326857. If you boot off ZFS and/or
540 GELI, it might not be a good time to update.
543 PowerPC users must update loader(8) by rebuilding world before
544 installing a new kernel, as the protocol connecting them has
545 changed. Without the update, loader metadata will not be passed
546 successfully to the kernel and users will have to enter their
547 root partition at the kernel mountroot prompt to continue booting.
548 Newer versions of loader can boot old kernels without issue.
551 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
552 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
553 to WITH/OUT_LOADER_GELI.
556 The naive and non-compliant support of posix_fallocate(2) in ZFS
557 has been removed as of r325320. The system call now returns EINVAL
558 when used on a ZFS file. Although the new behavior complies with the
559 standard, some consumers are not prepared to cope with it.
560 One known victim is lld prior to r325420.
563 Building in a FreeBSD src checkout will automatically create object
564 directories now rather than store files in the current directory if
565 'make obj' was not ran. Calling 'make obj' is no longer necessary.
566 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
567 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
571 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
572 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
573 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
574 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
575 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
576 The UNIFIED_OBJDIR option is a transitional feature that will be
577 removed for 12.0 release; please migrate to the new format for any
578 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
579 than hardcoding paths.
582 The native-xtools target no longer installs the files by default to the
583 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
584 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
587 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
588 options are changing from controlling the build if defined / undefined
589 to controlling the build with explicit 'yes' or 'no' values. They will
590 shift to WITH/WITHOUT options to match other options in the system.
593 libstand has turned into a private library for sys/boot use only.
594 It is no longer supported as a public interface outside of sys/boot.
597 The arm port has split armv6 into armv6 and armv7. armv7 is now
598 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
599 and are running a kernel from before r324363, you will need to add
600 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
603 When building multiple kernels using KERNCONF, non-existent KERNCONF
604 files will produce an error and buildkernel will fail. Previously
605 missing KERNCONF files silently failed giving no indication as to
606 why, only to subsequently discover during installkernel that the
607 desired kernel was never built in the first place.
610 The default serial number format for CTL LUNs has changed. This will
611 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
612 or iSCSI clients care about their LUNs' serial numbers. Users who
613 require serial number stability should hardcode serial numbers in
617 For 32-bit arm compiled for hard-float support, soft-floating point
618 binaries now always get their shared libraries from
619 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
620 /usr/libsoft also existed). Only users with a hard-float ld.so, but
621 soft-float everything else should be affected.
624 The geli password typed at boot is now hidden. To restore the previous
625 behavior, see geli(8) for configuration options.
628 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
629 sysctl values. Minor nit, but requires a rebuild of both world/kernel
633 "make check" behavior (made in ^/head@r295380) has been changed to
634 execute from a limited sandbox, as opposed to executing from
638 - The "beforecheck" and "aftercheck" targets are now specified.
639 - ${CHECKDIR} (added in commit noted above) has been removed.
640 - Legacy behavior can be enabled by setting
641 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
643 If the limited sandbox mode is enabled, "make check" will execute
644 "make distribution", then install, execute the tests, and clean up the
645 sandbox if successful.
647 The "make distribution" and "make install" targets are typically run as
648 root to set appropriate permissions and ownership at installation time.
649 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
650 environment if executing "make check" with limited sandbox mode using
651 an unprivileged user.
654 Since the switch to GPT disk labels, fsck for UFS/FFS has been
655 unable to automatically find alternate superblocks. As of r322297,
656 the information needed to find alternate superblocks has been
657 moved to the end of the area reserved for the boot block.
658 Filesystems created with a newfs of this vintage or later
659 will create the recovery information. If you have a filesystem
660 created prior to this change and wish to have a recovery block
661 created for your filesystem, you can do so by running fsck in
662 foreground mode (i.e., do not use the -p or -y options). As it
663 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
664 to which you should answer yes.
667 As of r321665, an NFSv4 server configuration that services
668 Kerberos mounts or clients that do not support the uid/gid in
669 owner/owner_group string capability, must explicitly enable
670 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
671 machine's /etc/rc.conf file.
674 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
675 Please see the 20141231 entry below for information about prerequisites
676 and upgrading, if you are not already using clang 3.5.0 or higher.
679 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
680 r-commands (rlogin, rsh, etc.) to be built with the base system.
683 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
684 a very major ABI incompatible change, so users of FreeBSD/powerpc must
685 be careful when performing source upgrades. It is best to run
686 'make installworld' from an alternate root system, either a live
687 CD/memory stick, or a temporary root partition. Additionally, all ports
688 must be recompiled. powerpc64 is largely unaffected, except in the case
689 of 32-bit compatibility. All 32-bit binaries will be affected.
692 Forward compatibility for the "ino64" project have been committed. This
693 will allow most new binaries to run on older kernels in a limited
694 fashion. This prevents many of the common foot-shooting actions in the
695 upgrade as well as the limited ability to roll back the kernel across
696 the ino64 upgrade. Complicated use cases may not work properly, though
697 enough simpler ones work to allow recovery in most situations.
700 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
701 if you require the GPL compiler.
704 The internal ABI used for communication between the NFS kernel modules
705 was changed by r320085, so __FreeBSD_version was bumped to
706 ensure all the NFS related modules are updated together.
709 The ABI of struct event was changed by extending the data
710 member to 64bit and adding ext fields. For upgrade, same
711 precautions as for the entry 20170523 "ino64" must be
715 The GNU roff toolchain has been removed from base. To render manpages
716 which are not supported by mandoc(1), man(1) can fallback on GNU roff
717 from ports (and recommends to install it).
718 To render roff(7) documents, consider using GNU roff from ports or the
719 heirloom doctools roff toolchain from ports via pkg install groff or
720 via pkg install heirloom-doctools.
723 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
724 smaller runtime footprint builds. This is useful for embedded systems
725 which only require one chipset support.
727 If you load it as a module, make sure this is in /boot/loader.conf:
731 This will load the HAL, all chip/RF backends and if_ath_pci.
732 If you have if_ath_pci in /boot/loader.conf, ensure it is after
733 if_ath or it will not load any HAL chipset support.
735 If you want to selectively load things (eg on ye cheape ARM/MIPS
736 platforms where RAM is at a premium) you should:
739 * load the chip modules in question
740 * load ath_rate, ath_dfs
742 * load if_ath_pci and/or if_ath_ahb depending upon your particular
743 bus bind type - this is where probe/attach is done.
745 For further comments/feedback, poke adrian@ .
748 The "ino64" 64-bit inode project has been committed, which extends
749 a number of types to 64 bits. Upgrading in place requires care and
750 adherence to the documented upgrade procedure.
752 If using a custom kernel configuration ensure that the
753 COMPAT_FREEBSD11 option is included (as during the upgrade the
754 system will be running the ino64 kernel with the existing world).
756 For the safest in-place upgrade begin by removing previous build
757 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
758 full procedure documented below under the heading "To rebuild
759 everything and install it on the current system." Specifically,
760 a reboot is required after installing the new kernel before
764 The NATM framework including the en(4), fatm(4), hatm(4), and
765 patm(4) devices has been removed. Consumers should plan a
766 migration before the end-of-life date for FreeBSD 11.
769 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
770 diff has not been implemented, if those are needed a newer version of
771 GNU diff is available via the diffutils package under the gdiff name.
774 As of r316810 for ipfilter, keep frags is no longer assumed when
775 keep state is specified in a rule. r316810 aligns ipfilter with
776 documentation in man pages separating keep frags from keep state.
777 This allows keep state to be specified without forcing keep frags
778 and allows keep frags to be specified independently of keep state.
779 To maintain previous behaviour, also specify keep frags with
780 keep state (as documented in ipf.conf.5).
783 arm64 builds now use the base system LLD 4.0.0 linker by default,
784 instead of requiring that the aarch64-binutils port or package be
785 installed. To continue using aarch64-binutils, set
786 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
789 The UDP optimization in entry 20160818 that added the sysctl
790 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
791 packets will no longer be treated as L3 broadcast packets.
794 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
795 use any explicitly assigned loopback address available in the jail
796 instead of using the first assigned address of the jail.
799 The ctl.ko module no longer implements the iSCSI target frontend:
800 cfiscsi.ko does instead.
802 If building cfiscsi.ko as a kernel module, the module can be loaded
803 via one of the following methods:
804 - `cfiscsi_load="YES"` in loader.conf(5).
805 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
806 - ctladm(8)/ctld(8), when compiled with iSCSI support
807 (`WITH_ISCSI=yes` in src.conf(5))
809 Please see cfiscsi(4) for more details.
812 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
813 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
814 same source (previously, the dependency of mmcsd.ko on mmc.ko was
815 missing, but mmcsd.ko now will refuse to load if it is incompatible
819 The syntax of ipfw(8) named states was changed to avoid ambiguity.
820 If you have used named states in the firewall rules, you need to modify
821 them after installworld and before rebooting. Now named states must
822 be prefixed with colon.
825 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
826 removed as the userland we provide cannot use them. The KMS version
827 (sys/dev/drm2) supports the same hardware.
830 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
831 Please see the 20141231 entry below for information about prerequisites
832 and upgrading, if you are not already using clang 3.5.0 or higher.
835 The code that provides support for ZFS .zfs/ directory functionality
836 has been reimplemented. It's not possible now to create a snapshot
837 by mkdir under .zfs/snapshot/. That should be the only user visible
841 EISA bus support has been removed. The WITH_EISA option is no longer
845 MCA bus support has been removed.
848 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
849 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
852 The EM_MULTIQUEUE kernel configuration option is deprecated now that
853 the em(4) driver conforms to iflib specifications.
856 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
857 IFLIB. If you have a custom kernel configuration that excludes em(4)
858 but you use igb(4), you need to re-add em(4) to your custom configuration.
861 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
862 Please see the 20141231 entry below for information about prerequisites
863 and upgrading, if you are not already using clang 3.5.0 or higher.
866 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
867 Please see the 20141231 entry below for information about prerequisites
868 and upgrading, if you are not already using clang 3.5.0 or higher.
871 The layout of the pmap structure has changed for powerpc to put the pmap
872 statistics at the front for all CPU variations. libkvm(3) and all tools
873 that link against it need to be recompiled.
876 isl(4) and cyapa(4) drivers now require a new driver,
877 chromebook_platform(4), to work properly on Chromebook-class hardware.
878 On other types of hardware the drivers may need to be configured using
879 device hints. Please see the corresponding manual pages for details.
882 The urtwn(4) driver was merged into rtwn(4) and now consists of
883 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
885 Also, firmware for RTL8188CE was renamed due to possible name
886 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
889 GNU rcs has been removed from base. It is available as packages:
890 - rcs: Latest GPLv3 GNU rcs version.
891 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
895 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
896 modules now requires that the kernel configuration contain the
897 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
900 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
901 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
904 Relocatable object files with the extension of .So have been renamed
905 to use an extension of .pico instead. The purpose of this change is
906 to avoid a name clash with shared libraries on case-insensitive file
907 systems. On those file systems, foo.So is the same file as foo.so.
910 GNU rcs has been turned off by default. It can (temporarily) be built
911 again by adding WITH_RCS knob in src.conf.
912 Otherwise, GNU rcs is available from packages:
913 - rcs: Latest GPLv3 GNU rcs version.
914 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
917 The backup_uses_rcs functionality has been removed from rc.subr.
920 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
921 two separate components, QUEUE_MACRO_DEBUG_TRACE and
922 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
923 QUEUE_MACRO_DEBUG behavior.
926 r304787 changed some ioctl interfaces between the iSCSI userspace
927 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
928 rebuilt to work with new kernels. __FreeBSD_version has been bumped
932 The UDP receive code has been updated to only treat incoming UDP
933 packets that were addressed to an L2 broadcast address as L3
934 broadcast packets. It is not expected that this will affect any
935 standards-conforming UDP application. The new behaviour can be
936 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
940 Remove the openbsd_poll system call.
941 __FreeBSD_version has been bumped because of this.
944 The stable/11 branch has been created from head@r302406.
947 The libc stub for the pipe(2) system call has been replaced with
948 a wrapper that calls the pipe2(2) system call and the pipe(2)
949 system call is now only implemented by the kernels that include
950 "options COMPAT_FREEBSD10" in their config file (this is the
951 default). Users should ensure that this option is enabled in
952 their kernel or upgrade userspace to r302092 before upgrading their
956 CAM will now strip leading spaces from SCSI disks' serial numbers.
957 This will affect users who create UFS filesystems on SCSI disks using
958 those disk's diskid device nodes. For example, if /etc/fstab
959 previously contained a line like
960 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
961 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
962 transforms like gmirror may also be affected. ZFS users should
966 The bitstring(3) API has been updated with new functionality and
967 improved performance. But it is binary-incompatible with the old API.
968 Objects built with the new headers may not be linked against objects
969 built with the old headers.
972 The brk and sbrk functions have been removed from libc on arm64.
973 Binutils from ports has been updated to not link to these
974 functions and should be updated to the latest version before
975 installing a new libc.
978 The armv6 port now defaults to hard float ABI. Limited support
979 for running both hardfloat and soft float on the same system
980 is available using the libraries installed with -DWITH_LIBSOFT.
981 This has only been tested as an upgrade path for installworld
982 and packages may fail or need manual intervention to run. New
983 packages will be needed.
985 To update an existing self-hosted armv6hf system, you must add
986 TARGET_ARCH=armv6 on the make command line for both the build
987 and the install steps.
990 Kernel modules compiled outside of a kernel build now default to
991 installing to /boot/modules instead of /boot/kernel. Many kernel
992 modules built this way (such as those in ports) already overrode
993 KMODDIR explicitly to install into /boot/modules. However,
994 manually building and installing a module from /sys/modules will
995 now install to /boot/modules instead of /boot/kernel.
998 The CAM I/O scheduler has been committed to the kernel. There should be
999 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1000 list of known rogues that claim support for this but actually corrupt
1001 data is believed to be complete, be on the lookout for data
1002 corruption. The known rogue list is believed to be complete:
1004 o Crucial MX100, M550 drives with MU01 firmware.
1005 o Micron M510 and M550 drives with MU01 firmware.
1006 o Micron M500 prior to MU07 firmware
1007 o Samsung 830, 840, and 850 all firmwares
1008 o FCCT M500 all firmwares
1010 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1011 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1012 updated firmware. Black listed drives will work correctly because these
1013 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1014 this list is the same as found in Linux, it's believed there are no
1015 other rogues in the market place. All other models from the above
1018 To be safe, if you are at all concerned, you can quirk each of your
1019 drives to prevent NCQ from being sent by setting:
1020 kern.cam.ada.X.quirks="0x2"
1021 in loader.conf. If the drive requires the 4k sector quirk, set the
1022 quirks entry to 0x3.
1025 The FAST_DEPEND build option has been removed and its functionality is
1026 now the one true way. The old mkdep(1) style of 'make depend' has
1027 been removed. See 20160311 for further details.
1030 Resource range types have grown from unsigned long to uintmax_t. All
1031 drivers, and anything using libdevinfo, need to be recompiled.
1034 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1035 builds. It no longer runs mkdep(1) during 'make depend', and the
1036 'make depend' stage can safely be skipped now as it is auto ran
1037 when building 'make all' and will generate all SRCS and DPSRCS before
1038 building anything else. Dependencies are gathered at compile time with
1039 -MF flags kept in separate .depend files per object file. Users should
1040 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1041 stale .depend files.
1044 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1045 kernel modules. Therefore, if you load any kernel modules at boot time,
1046 please install the boot loaders after you install the kernel, but before
1050 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1051 make installkernel KERNCONF=YOUR_KERNEL_HERE
1052 make -C sys/boot install
1053 <reboot in single user>
1055 Then follow the usual steps, described in the General Notes section,
1059 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1060 see the 20141231 entry below for information about prerequisites and
1061 upgrading, if you are not already using clang 3.5.0 or higher.
1064 The AIO subsystem is now a standard part of the kernel. The
1065 VFS_AIO kernel option and aio.ko kernel module have been removed.
1066 Due to stability concerns, asynchronous I/O requests are only
1067 permitted on sockets and raw disks by default. To enable
1068 asynchronous I/O requests on all file types, set the
1069 vfs.aio.enable_unsafe sysctl to a non-zero value.
1072 The ELF object manipulation tool objcopy is now provided by the
1073 ELF Tool Chain project rather than by GNU binutils. It should be a
1074 drop-in replacement, with the addition of arm64 support. The
1075 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1076 to obtain the GNU version if necessary.
1079 Building ZFS pools on top of zvols is prohibited by default. That
1080 feature has never worked safely; it's always been prone to deadlocks.
1081 Using a zvol as the backing store for a VM guest's virtual disk will
1082 still work, even if the guest is using ZFS. Legacy behavior can be
1083 restored by setting vfs.zfs.vol.recursive=1.
1086 The NONE and HPN patches has been removed from OpenSSH. They are
1087 still available in the security/openssh-portable port.
1090 With the addition of ypldap(8), a new _ypldap user is now required
1091 during installworld. "mergemaster -p" can be used to add the user
1092 prior to installworld, as documented in the handbook.
1095 The tftp loader (pxeboot) now uses the option root-path directive. As a
1096 consequence it no longer looks for a pxeboot.4th file on the tftp
1097 server. Instead it uses the regular /boot infrastructure as with the
1101 The code to start recording plug and play data into the modules has
1102 been committed. While the old tools will properly build a new kernel,
1103 a number of warnings about "unknown metadata record 4" will be produced
1104 for an older kldxref. To avoid such warnings, make sure to rebuild
1105 the kernel toolchain (or world). Make sure that you have r292078 or
1106 later when trying to build 292077 or later before rebuilding.
1109 Debug data files are now built by default with 'make buildworld' and
1110 installed with 'make installworld'. This facilitates debugging but
1111 requires more disk space both during the build and for the installed
1112 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1116 r291527 changed the internal interface between the nfsd.ko and
1117 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1118 __FreeBSD_version has been bumped because of this.
1121 Add support for unicode collation strings leads to a change of
1122 order of files listed by ls(1) for example. To get back to the old
1123 behaviour, set LC_COLLATE environment variable to "C".
1125 Databases administrators will need to reindex their databases given
1126 collation results will be different.
1128 Due to a bug in install(1) it is recommended to remove the ancient
1129 locales before running make installworld.
1131 rm -rf /usr/share/locale/*
1134 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1135 libcrypto.so.7 or libssl.so.7 must be recompiled.
1138 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1139 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1140 should be replaced with isp_2400 and isp_2500 modules respectively.
1143 The build previously allowed using 'make -n' to not recurse into
1144 sub-directories while showing what commands would be executed, and
1145 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1146 and 'make -N' will not.
1149 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1150 and etcupdate will now use this file. A custom sendmail.cf is now
1151 updated via this mechanism rather than via installworld. If you had
1152 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1153 want to remove the exclusion or change it to "always install".
1154 /etc/mail/sendmail.cf is now managed the same way regardless of
1155 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1156 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1159 Compatibility shims for legacy ATA device names have been removed.
1160 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1161 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1162 environment variables, /dev/ad* and /dev/ar* symbolic links.
1165 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1166 Please see the 20141231 entry below for information about prerequisites
1167 and upgrading, if you are not already using clang 3.5.0 or higher.
1170 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1171 and renamed from .symbols to .debug. This reduces the size requirements
1172 on the boot partition or file system and provides consistency with
1173 userland debug files.
1175 When using the supported kernel installation method the
1176 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1177 as is done with /boot/kernel.
1179 Developers wishing to maintain the historical behavior of installing
1180 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1183 The wireless drivers had undergone changes that remove the 'parent
1184 interface' from the ifconfig -l output. The rc.d network scripts
1185 used to check presence of a parent interface in the list, so old
1186 scripts would fail to start wireless networking. Thus, etcupdate(3)
1187 or mergemaster(8) run is required after kernel update, to update your
1188 rc.d scripts in /etc.
1191 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1192 These configurations are now automatically interpreted as
1193 'scrub fragment reassemble'.
1196 Kernel-loadable modules for the random(4) device are back. To use
1197 them, the kernel must have
1200 options RANDOM_LOADABLE
1202 kldload(8) can then be used to load random_fortuna.ko
1203 or random_yarrow.ko. Please note that due to the indirect
1204 function calls that the loadable modules need to provide,
1205 the build-in variants will be slightly more efficient.
1207 The random(4) kernel option RANDOM_DUMMY has been retired due to
1208 unpopularity. It was not all that useful anyway.
1211 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1212 Control over building the ELF Tool Chain tools is now provided by
1213 the WITHOUT_TOOLCHAIN knob.
1216 The polarity of Pulse Per Second (PPS) capture events with the
1217 uart(4) driver has been corrected. Prior to this change the PPS
1218 "assert" event corresponded to the trailing edge of a positive PPS
1219 pulse and the "clear" event was the leading edge of the next pulse.
1221 As the width of a PPS pulse in a typical GPS receiver is on the
1222 order of 1 millisecond, most users will not notice any significant
1223 difference with this change.
1225 Anyone who has compensated for the historical polarity reversal by
1226 configuring a negative offset equal to the pulse width will need to
1227 remove that workaround.
1230 The default group assigned to /dev/dri entries has been changed
1231 from 'wheel' to 'video' with the id of '44'. If you want to have
1232 access to the dri devices please add yourself to the video group
1235 # pw groupmod video -m $USER
1238 The menu.rc and loader.rc files will now be replaced during
1239 upgrades. Please migrate local changes to menu.rc.local and
1240 loader.rc.local instead.
1243 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1244 strings and strip have been removed. The src.conf(5) knob
1245 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1248 As ZFS requires more kernel stack pages than is the default on some
1249 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1250 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1252 Please consider using 'options KSTACK_PAGES=X' where X is greater
1253 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1256 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1257 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1258 default, i.e., they will not contain "::". For example, instead
1259 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1260 to have a more specific match, such as different map entries for
1261 IPv6:0:0 vs IPv6:0. This change requires that configuration
1262 data (including maps, files, classes, custom ruleset, etc.) must
1263 use the same format, so make certain such configuration data is
1264 upgrading. As a very simple check search for patterns like
1265 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1266 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1267 the cf option UseCompressedIPv6Addresses.
1270 The default kernel entropy-processing algorithm is now
1271 Fortuna, replacing Yarrow.
1273 Assuming you have 'device random' in your kernel config
1274 file, the configurations allow a kernel option to override
1275 this default. You may choose *ONE* of:
1277 options RANDOM_YARROW # Legacy /dev/random algorithm.
1278 options RANDOM_DUMMY # Blocking-only driver.
1280 If you have neither, you get Fortuna. For most people,
1281 read no further, Fortuna will give a /dev/random that works
1282 like it always used to, and the difference will be irrelevant.
1284 If you remove 'device random', you get *NO* kernel-processed
1285 entropy at all. This may be acceptable to folks building
1286 embedded systems, but has complications. Carry on reading,
1287 and it is assumed you know what you need.
1289 *PLEASE* read random(4) and random(9) if you are in the
1290 habit of tweaking kernel configs, and/or if you are a member
1291 of the embedded community, wanting specific and not-usual
1292 behaviour from your security subsystems.
1294 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1295 random', you will NOT have a functioning /dev/random, and
1296 many cryptographic features will not work, including SSH.
1297 You may also find strange behaviour from the random(3) set
1298 of library functions, in particular sranddev(3), srandomdev(3)
1299 and arc4random(3). The reason for this is that the KERN_ARND
1300 sysctl only returns entropy if it thinks it has some to
1301 share, and with RANDOM_DUMMY or no 'device random' this
1305 An additional fix for the issue described in the 20150614 sendmail
1306 entry below has been committed in revision 284717.
1309 FreeBSD's old make (fmake) has been removed from the system. It is
1310 available as the devel/fmake port or via pkg install fmake.
1313 The fix for the issue described in the 20150614 sendmail entry
1314 below has been committed in revision 284436. The work
1315 around described in that entry is no longer needed unless the
1316 default setting is overridden by a confDH_PARAMETERS configuration
1317 setting of '5' or pointing to a 512 bit DH parameter file.
1320 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1321 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1322 and devel/kyua to version 0.20+ and adjust any calling code to work
1323 with Kyuafile and kyua.
1326 The import of openssl to address the FreeBSD-SA-15:10.openssl
1327 security advisory includes a change which rejects handshakes
1328 with DH parameters below 768 bits. sendmail releases prior
1329 to 8.15.2 (not yet released), defaulted to a 512 bit
1330 DH parameter setting for client connections. To work around
1331 this interoperability, sendmail can be configured to use a
1332 2048 bit DH parameter by:
1334 1. Edit /etc/mail/`hostname`.mc
1335 2. If a setting for confDH_PARAMETERS does not exist or
1336 exists and is set to a string beginning with '5',
1337 replace it with '2'.
1338 3. If a setting for confDH_PARAMETERS exists and is set to
1339 a file path, create a new file with:
1340 openssl dhparam -out /path/to/file 2048
1341 4. Rebuild the .cf file:
1342 cd /etc/mail/; make; make install
1343 5. Restart sendmail:
1344 cd /etc/mail/; make restart
1346 A sendmail patch is coming, at which time this file will be
1350 Generation of legacy formatted entries have been disabled by default
1351 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1352 entries were converted to use the new format by default when the new,
1353 machine independent format have been added and supported since FreeBSD
1356 Please see the pwd_mkdb(8) manual page for further details.
1359 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1360 20141231 entry below for information about prerequisites and upgrading,
1361 if you are not already using 3.5.0 or higher.
1364 TI platform code switched to using vendor DTS files and this update
1365 may break existing systems running on Beaglebone, Beaglebone Black,
1368 - dtb files should be regenerated/reinstalled. Filenames are the
1369 same but content is different now
1370 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1371 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1372 addressing scheme is now pin 25 on /dev/gpioc3.
1373 - Pandaboard: /etc/ttys should be updated, serial console device is
1374 now /dev/ttyu2, not /dev/ttyu0
1377 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1378 If you need the GNU extension from groff soelim(1), install groff
1379 from package: pkg install groff, or via ports: textproc/groff.
1382 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1383 defined in symlink(7); previously symlinks were silently ignored.
1386 The const qualifier has been removed from iconv(3) to comply with
1387 POSIX. The ports tree is aware of this from r384038 onwards.
1390 Libraries specified by LIBADD in Makefiles must have a corresponding
1391 DPADD_<lib> variable to ensure correct dependencies. This is now
1392 enforced in src.libnames.mk.
1395 From legacy ata(4) driver was removed support for SATA controllers
1396 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1397 Kernel modules ataahci and ataadaptec were removed completely,
1398 replaced by ahci and mvs modules respectively.
1401 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1402 the 20141231 entry below for information about prerequisites and
1403 upgrading, if you are not already using 3.5.0 or higher.
1406 The 32-bit PowerPC kernel has been changed to a position-independent
1407 executable. This can only be booted with a version of loader(8)
1408 newer than January 31, 2015, so make sure to update both world and
1409 kernel before rebooting.
1412 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1413 but before r278950, the RNG was not seeded properly. Immediately
1414 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1415 ssh keys or openssl keys) that were generated w/ a kernel from that
1416 range. This does not affect programs that directly used /dev/random
1417 or /dev/urandom. All userland uses of arc4random(3) are affected.
1420 The autofs(4) ABI was changed in order to restore binary compatibility
1421 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1422 with the new kernel.
1425 The powerpc64 kernel has been changed to a position-independent
1426 executable. This can only be booted with a new version of loader(8),
1427 so make sure to update both world and kernel before rebooting.
1430 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1431 only release, no new features have been added. Please see the 20141231
1432 entry below for information about prerequisites and upgrading, if you
1433 are not already using 3.5.0.
1436 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1437 taken from the ELF Tool Chain project rather than GNU binutils. They
1438 should be drop-in replacements, with the addition of arm64 support.
1439 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1440 binutils tools, if necessary. See 20150805 for updated information.
1443 The default Unbound configuration now enables remote control
1444 using a local socket. Users who have already enabled the
1445 local_unbound service should regenerate their configuration
1446 by running "service local_unbound setup" as root.
1449 The GNU texinfo and GNU info pages have been removed.
1450 To be able to view GNU info pages please install texinfo from ports.
1453 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1455 As of this release, a prerequisite for building clang, llvm and lldb is
1456 a C++11 capable compiler and C++11 standard library. This means that to
1457 be able to successfully build the cross-tools stage of buildworld, with
1458 clang as the bootstrap compiler, your system compiler or cross compiler
1459 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1460 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1463 On any standard FreeBSD 10.x or 11.x installation, where clang and
1464 libc++ are on by default (that is, on x86 or arm), this should work out
1467 On 9.x installations where clang is enabled by default, e.g. on x86 and
1468 powerpc, libc++ will not be enabled by default, so libc++ should be
1469 built (with clang) and installed first. If both clang and libc++ are
1470 missing, build clang first, then use it to build libc++.
1472 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1473 the instructions for 9.x above.
1475 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1476 default, and do not build clang.
1478 Many embedded systems are resource constrained, and will not be able to
1479 build clang in a reasonable time, or in some cases at all. In those
1480 cases, cross building bootable systems on amd64 is a workaround.
1482 This new version of clang introduces a number of new warnings, of which
1483 the following are most likely to appear:
1487 This warns in two cases, for both C and C++:
1488 * When the code is trying to take the absolute value of an unsigned
1489 quantity, which is effectively a no-op, and almost never what was
1490 intended. The code should be fixed, if at all possible. If you are
1491 sure that the unsigned quantity can be safely cast to signed, without
1492 loss of information or undefined behavior, you can add an explicit
1493 cast, or disable the warning.
1495 * When the code is trying to take an absolute value, but the called
1496 abs() variant is for the wrong type, which can lead to truncation.
1497 If you want to disable the warning instead of fixing the code, please
1498 make sure that truncation will not occur, or it might lead to unwanted
1501 -Wtautological-undefined-compare and
1502 -Wundefined-bool-conversion
1504 These warn when C++ code is trying to compare 'this' against NULL, while
1505 'this' should never be NULL in well-defined C++ code. However, there is
1506 some legacy (pre C++11) code out there, which actively abuses this
1507 feature, which was less strictly defined in previous C++ versions.
1509 Squid and openjdk do this, for example. The warning can be turned off
1510 for C++98 and earlier, but compiling the code in C++11 mode might result
1511 in unexpected behavior; for example, the parts of the program that are
1512 unreachable could be optimized away.
1515 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1516 kernel sources have been removed. The .h files remain, since some
1517 utilities include them. This will need to be fixed later.
1518 If "mount -t oldnfs ..." is attempted, it will fail.
1519 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1520 the utilities will report errors.
1523 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1524 directories to top level SUBDIR variable when their parent
1525 directory is included in LOCAL_DIRS. Users with build systems with
1526 such hierarchies and without SUBDIR entries in the parent
1527 directory Makefiles should add them or add the directories to
1531 faith(4) and faithd(8) have been removed from the base system. Faith
1532 has been obsolete for a very long time.
1535 vt(4), the new console driver, is enabled by default. It brings
1536 support for Unicode and double-width characters, as well as
1537 support for UEFI and integration with the KMS kernel video
1540 You may need to update your console settings in /etc/rc.conf,
1541 most probably the keymap. During boot, /etc/rc.d/syscons will
1542 indicate what you need to do.
1544 vt(4) still has issues and lacks some features compared to
1545 syscons(4). See the wiki for up-to-date information:
1546 https://wiki.freebsd.org/Newcons
1548 If you want to keep using syscons(4), you can do so by adding
1549 the following line to /boot/loader.conf:
1553 pjdfstest has been integrated into kyua as an opt-in test suite.
1554 Please see share/doc/pjdfstest/README for more details on how to
1558 gperf has been removed from the base system for architectures
1559 that use clang. Ports that require gperf will obtain it from the
1563 pjdfstest has been moved from tools/regression/pjdfstest to
1567 At svn r271982, The default linux compat kernel ABI has been adjusted
1568 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1569 update. If you wish to continue using the linux-f10 compat ports,
1570 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1571 encouraged to update their linux-compat packages to linux-c6 during
1572 their next update cycle.
1575 The ofwfb driver, used to provide a graphics console on PowerPC when
1576 using vt(4), no longer allows mmap() of all physical memory. This
1577 will prevent Xorg on PowerPC with some ATI graphics cards from
1578 initializing properly unless x11-servers/xorg-server is updated to
1582 The xdev targets have been converted to using TARGET and
1583 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1586 The default unbound configuration has been modified to address
1587 issues with reverse lookups on networks that use private
1588 address ranges. If you use the local_unbound service, run
1589 "service local_unbound setup" as root to regenerate your
1590 configuration, then "service local_unbound reload" to load the
1594 The GNU texinfo and GNU info pages are not built and installed
1595 anymore, WITH_INFO knob has been added to allow to built and install
1597 UPDATE: see 20150102 entry on texinfo's removal
1600 The GNU readline library is now an INTERNALLIB - that is, it is
1601 statically linked into consumers (GDB and variants) in the base
1602 system, and the shared library is no longer installed. The
1603 devel/readline port is available for third party software that
1607 The Itanium architecture (ia64) has been removed from the list of
1608 known architectures. This is the first step in the removal of the
1612 Commit r268115 has added NFSv4.1 server support, merged from
1613 projects/nfsv4.1-server. Since this includes changes to the
1614 internal interfaces between the NFS related modules, a full
1615 build of the kernel and modules will be necessary.
1616 __FreeBSD_version has been bumped.
1619 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1620 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1621 which differs from the behaviour controlled by this knob.)
1624 Maximal length of the serial number in CTL was increased from 16 to
1625 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1626 and ctld, need to be rebuilt to work with a new kernel.
1629 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1630 1 respectively to match the upstream numbers. They were out of
1631 sync because, when they were originally added to FreeBSD, the
1632 upstream versions were not respected. These libraries are private
1633 and not yet built by default, so renumbering them should be a
1634 non-issue. However, unclean source trees will yield broken test
1635 programs once the operator executes "make delete-old-libs" after a
1636 "make installworld".
1638 Additionally, the atf-sh binary was made private by moving it into
1639 /usr/libexec/. Already-built shell test programs will keep the
1640 path to the old binary so they will break after "make delete-old"
1643 If you are using WITH_TESTS=yes (not the default), wipe the object
1644 tree and rebuild from scratch to prevent spurious test failures.
1645 This is only needed once: the misnumbered libraries and misplaced
1646 binaries have been added to OptionalObsoleteFiles.inc so they will
1647 be removed during a clean upgrade.
1650 Clang and llvm have been upgraded to 3.4.1 release.
1653 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1654 be removed to avoid issues in the future (and has been added to
1658 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1659 past, it affected all builds that used the bsd.*.mk files. The old
1660 behavior was a bug, but people may have relied upon it. To get this
1661 behavior back, you can .include /etc/src.conf from /etc/make.conf
1662 (which is still global and isn't changed). This also changes the
1663 behavior of incremental builds inside the tree of individual
1664 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1665 Although this has survived make universe and some upgrade scenarios,
1666 other upgrade scenarios may have broken. At least one form of
1667 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1668 as well... In cases where MAKESYSPATH isn't working with this
1669 setting, you'll need to set it to the full path to your tree.
1671 One side effect of all this cleaning up is that bsd.compiler.mk
1672 is no longer implicitly included by bsd.own.mk. If you wish to
1673 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1677 The lindev device has been removed since /dev/full has been made a
1678 standard device. __FreeBSD_version has been bumped.
1681 The knob WITHOUT_VI was added to the base system, which controls
1682 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1683 in order to reorder files share/termcap and didn't build ex(1) as a
1684 build tool, so building/installing with WITH_VI is highly advised for
1685 build hosts for older releases.
1687 This issue has been fixed in stable/9 and stable/10 in r277022 and
1688 r276991, respectively.
1691 The YES_HESIOD knob has been removed. It has been obsolete for
1692 a decade. Please move to using WITH_HESIOD instead or your builds
1693 will silently lack HESIOD.
1696 The uart(4) driver has been changed with respect to its handling
1697 of the low-level console. Previously the uart(4) driver prevented
1698 any process from changing the baudrate or the CLOCAL and HUPCL
1699 control flags. By removing the restrictions, operators can make
1700 changes to the serial console port without having to reboot.
1701 However, when getty(8) is started on the serial device that is
1702 associated with the low-level console, a misconfigured terminal
1703 line in /etc/ttys will now have a real impact.
1704 Before upgrading the kernel, make sure that /etc/ttys has the
1705 serial console device configured as 3wire without baudrate to
1706 preserve the previous behaviour. E.g:
1707 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1710 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1711 to improve performance. To re-enable it, if needed, run rpcbind
1712 with command line option -W.
1715 Switched back to the GPL dtc compiler due to updates in the upstream
1716 dts files not being supported by the BSDL dtc compiler. You will need
1717 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1718 may result while building dtb files during a kernel build if you fail
1719 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1722 Clang and llvm have been upgraded to 3.4 release.
1725 The nve(4) driver has been removed. Please use the nfe(4) driver
1726 for NVIDIA nForce MCP Ethernet adapters instead.
1729 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1730 This could cause certain C++ applications using shared libraries built
1731 against the previous version of libc++ to crash. The incompatibility
1732 has now been fixed, but any C++ applications or shared libraries built
1733 between r261283 and r261801 should be recompiled.
1736 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1737 capability mode support. Please note that enabling the feature in
1738 kernel is still highly recommended.
1741 OpenSSH is now built with sandbox support, and will use sandbox as
1742 the default privilege separation method. This requires Capsicum
1743 capability mode support in kernel.
1746 The libelf and libdwarf libraries have been updated to newer
1747 versions from upstream. Shared library version numbers for
1748 these two libraries were bumped. Any ports or binaries
1749 requiring these two libraries should be recompiled.
1750 __FreeBSD_version is bumped to 1100006.
1753 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1754 instead of providing an explicit one, this would prevent such
1755 Makefile from providing its own Kyuafile in the future during
1756 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1757 intervention is needed to clean an objdir if you use NO_CLEAN:
1758 # find /usr/obj -name Kyuafile | xargs rm -f
1761 The behavior of gss_pseudo_random() for the krb5 mechanism
1762 has changed, for applications requesting a longer random string
1763 than produced by the underlying enctype's pseudo-random() function.
1764 In particular, the random string produced from a session key of
1765 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1766 be different at the 17th octet and later, after this change.
1767 The counter used in the PRF+ construction is now encoded as a
1768 big-endian integer in accordance with RFC 4402.
1769 __FreeBSD_version is bumped to 1100004.
1772 The WITHOUT_ATF build knob has been removed and its functionality
1773 has been subsumed into the more generic WITHOUT_TESTS. If you were
1774 using the former to disable the build of the ATF libraries, you
1775 should change your settings to use the latter.
1778 The default version of mtree is nmtree which is obtained from
1779 NetBSD. The output is generally the same, but may vary
1780 slightly. If you found you need identical output adding
1781 "-F freebsd9" to the command line should do the trick. For the
1782 time being, the old mtree is available as fmtree.
1785 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1786 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1787 1.1.4_8 and verify bsdyml not linked in, before running "make
1789 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1791 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1794 The stable/10 branch has been created in subversion from head
1801 Avoid using make -j when upgrading. While generally safe, there are
1802 sometimes problems using -j to upgrade. If your upgrade fails with
1803 -j, please try again without -j. From time to time in the past there
1804 have been problems using -j with buildworld and/or installworld. This
1805 is especially true when upgrading between "distant" versions (eg one
1806 that cross a major release boundary or several minor releases, or when
1807 several months have passed on the -current branch).
1809 Sometimes, obscure build problems are the result of environment
1810 poisoning. This can happen because the make utility reads its
1811 environment when searching for values for global variables. To run
1812 your build attempts in an "environmental clean room", prefix all make
1813 commands with 'env -i '. See the env(1) manual page for more details.
1815 When upgrading from one major version to another it is generally best to
1816 upgrade to the latest code in the currently installed branch first, then
1817 do an upgrade to the new branch. This is the best-tested upgrade path,
1818 and has the highest probability of being successful. Please try this
1819 approach if you encounter problems with a major version upgrade. Since
1820 the stable 4.x branch point, one has generally been able to upgrade from
1821 anywhere in the most recent stable branch to head / current (or even the
1822 last couple of stable branches). See the top of this file when there's
1825 When upgrading a live system, having a root shell around before
1826 installing anything can help undo problems. Not having a root shell
1827 around can lead to problems if pam has changed too much from your
1828 starting point to allow continued authentication after the upgrade.
1830 This file should be read as a log of events. When a later event changes
1831 information of a prior event, the prior event should not be deleted.
1832 Instead, a pointer to the entry with the new information should be
1833 placed in the old entry. Readers of this file should also sanity check
1834 older entries before relying on them blindly. Authors of new entries
1835 should write them with this in mind.
1839 When upgrading the boot ZFS pool to a new version, always follow
1842 1.) recompile and reinstall the ZFS boot loader and boot block
1843 (this is part of "make buildworld" and "make installworld")
1845 2.) update the ZFS boot block on your boot drive
1847 The following example updates the ZFS boot block on the first
1848 partition (freebsd-boot) of a GPT partitioned drive ada0:
1849 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1851 Non-boot pools do not need these updates.
1855 If you are updating from a prior version of FreeBSD (even one just
1856 a few days old), you should follow this procedure. It is the most
1857 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1859 make kernel-toolchain
1860 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1861 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1863 To test a kernel once
1864 ---------------------
1865 If you just want to boot a kernel once (because you are not sure
1866 if it works, or if you want to boot a known bad kernel to provide
1867 debugging information) run
1868 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1869 nextboot -k testkernel
1871 To rebuild everything and install it on the current system.
1872 -----------------------------------------------------------
1873 # Note: sometimes if you are running current you gotta do more than
1874 # is listed here if you are upgrading from a really old current.
1876 <make sure you have good level 0 dumps>
1878 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1879 make installkernel KERNCONF=YOUR_KERNEL_HERE
1881 <reboot in single user> [3]
1888 To cross-install current onto a separate partition
1889 --------------------------------------------------
1890 # In this approach we use a separate partition to hold
1891 # current's root, 'usr', and 'var' directories. A partition
1892 # holding "/", "/usr" and "/var" should be about 2GB in
1895 <make sure you have good level 0 dumps>
1898 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1899 <maybe newfs current's root partition>
1900 <mount current's root partition on directory ${CURRENT_ROOT}>
1901 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1902 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1903 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1904 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1905 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1906 <reboot into current>
1907 <do a "native" rebuild/install as described in the previous section>
1908 <maybe install compatibility libraries from ports/misc/compat*>
1912 To upgrade in-place from stable to current
1913 ----------------------------------------------
1914 <make sure you have good level 0 dumps>
1916 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1917 make installkernel KERNCONF=YOUR_KERNEL_HERE
1919 <reboot in single user> [3]
1926 Make sure that you've read the UPDATING file to understand the
1927 tweaks to various things you need. At this point in the life
1928 cycle of current, things change often and you are on your own
1929 to cope. The defaults can also change, so please read ALL of
1930 the UPDATING entries.
1932 Also, if you are tracking -current, you must be subscribed to
1933 freebsd-current@freebsd.org. Make sure that before you update
1934 your sources that you have read and understood all the recent
1935 messages there. If in doubt, please track -stable which has
1936 much fewer pitfalls.
1938 [1] If you have third party modules, such as vmware, you
1939 should disable them at this point so they don't crash your
1942 [3] From the bootblocks, boot -s, and then do
1947 adjkerntz -i # if CMOS is wall time
1948 Also, when doing a major release upgrade, it is required that
1949 you boot into single user mode to do the installworld.
1951 [4] Note: This step is non-optional. Failure to do this step
1952 can result in a significant reduction in the functionality of the
1953 system. Attempting to do it by hand is not recommended and those
1954 that pursue this avenue should read this file carefully, as well
1955 as the archives of freebsd-current and freebsd-hackers mailing lists
1956 for potential gotchas. The -U option is also useful to consider.
1957 See mergemaster(8) for more information.
1959 [5] Usually this step is a no-op. However, from time to time
1960 you may need to do this if you get unknown user in the following
1961 step. It never hurts to do it all the time. You may need to
1962 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1963 install) after the buildworld before this step if you last updated
1964 from current before 20130425 or from -stable before 20130430.
1966 [6] This only deletes old files and directories. Old libraries
1967 can be deleted by "make delete-old-libs", but you have to make
1968 sure that no program is using those libraries anymore.
1970 [8] The new kernel must be able to run existing binaries used by
1971 an installworld. When upgrading across major versions, the new
1972 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1973 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1974 binaries). Failure to do so may leave you with a system that is
1975 hard to boot to recover. A GENERIC kernel will include suitable
1976 compatibility options to run binaries from older branches.
1978 Make sure that you merge any new devices from GENERIC since the
1979 last time you updated your kernel config file.
1981 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1982 "?=" instead of the "=" assignment operator, so that buildworld can
1983 override the CPUTYPE if it needs to.
1985 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1986 not on the command line, or in /etc/make.conf. buildworld will
1987 warn if it is improperly defined.
1990 This file contains a list, in reverse chronological order, of major
1991 breakages in tracking -current. It is not guaranteed to be a complete
1992 list of such breakages, and only contains entries since September 23, 2011.
1993 If you need to see UPDATING entries from before that date, you will need
1994 to fetch an UPDATING file from an older FreeBSD release.
1996 Copyright information:
1998 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2000 Redistribution, publication, translation and use, with or without
2001 modification, in full or in part, in any form or format of this
2002 document are permitted without further permission from the author.
2004 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2005 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2006 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2007 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2008 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2009 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2010 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2011 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2012 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2013 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2014 POSSIBILITY OF SUCH DAMAGE.
2016 Contact Warner Losh if you have any questions about your use of