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.
19 20200421 p4 FreeBSD-EN-20:07.quotad
21 FreeBSD-SA-20:11.openssl
23 Fix regression in rpc.rquotad with certain NFS servers [EN-20:07.quotad]
25 Fix ipfw invalid mbuf handling [SA-20:10.ipfw]
27 Fix OpenSSL remote denial of service vulnerability [SA-20:11.openssl]
29 20200319 p3 FreeBSD-EN-20:03.sshd
30 FreeBSD-EN-20:05.mlx5en
33 FreeBSD-SA-20:05.if_oce_ioctl
34 FreeBSD-SA-20:06.if_ixl_ioctl
35 FreeBSD-SA-20:07.epair
39 Fix misleading log messages upon successful sshd login [EN-20:03.sshd]
41 Fix packet forwarding performance in mlx5en(4) driver [EN-20:05.mlx5en]
43 Fix incorrect checksum calculations with IPv6 extension headers [EN-20:06.ipv6]
45 Fix TCP IPv6 SYN cache kernel information disclosure [SA-20:04.tcp]
47 Fix insufficient oce(4) ioctl(2) privilege checking [SA-20:05.if_oce_ioctl]
49 Fix insufficient ixl(4) ioctl(2) privilege checking [SA-20:06.if_ixl_ioctl]
51 Fix incorrect user-controlled pointer use in epair [SA-20:07.epair]
53 Fix kernel memory disclosure with nested jails [SA-20:08.jail]
55 Fix multiple denial of service in ntpd [SA-20:09.ntp]
57 20200128 p2 FreeBSD-EN-20:01.ssp
58 FreeBSD-SA-20:01.libfetch
59 FreeBSD-SA-20:03.thrmisc
61 Fix imprecise ordering of SSP canary initialization [EN-20:01.ssp]
63 Fix libfetch buffer overflow [SA-20:01.libfetch]
65 Fix kernel stack data disclosure [SA-20:03.thrmisc]
67 20191112 p1 FreeBSD-EN-19:19.loader
68 FreeBSD-SA-19:25.mcepsc
70 Fix UEFI Loader Memory Fragmentation [EN-19:19.loader]
72 Fix Machine Check Exception on Page Size Change [SA-19:25.mcepsc]
78 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
79 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
80 been removed from mount_fusefs(8). You can safely remove them from
81 your scripts, because they had no effect.
83 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
84 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
85 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
86 sysctls have been removed. If you felt the need to set any of them to
87 a non-default value, please tell asomers@FreeBSD.org why.
90 The fuse(4) module has been renamed to fusefs(4) for consistency with
91 other filesystems. You should update any kld_load="fuse" entries in
92 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
93 "options FUSE" enties in kernel config files.
96 Default permissions on the /var/account/acct file (and copies of it
97 rotated by periodic daily scripts) are changed from 0644 to 0640
98 because the file contains sensitive information that should not be
99 world-readable. If the /var/account directory must be created by
100 rc.d/accounting, the mode used is now 0750. Admins who use the
101 accounting feature are encouraged to change the mode of an existing
102 /var/account directory to 0750 or 0700.
105 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
106 been upgraded to 8.0.1. Please see the 20141231 entry below for
107 information about prerequisites and upgrading, if you are not already
108 using clang 3.5.0 or higher.
111 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
112 functionality needed for the RETPOLINE option should work properly
113 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
116 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
117 8.0.0. Please see the 20141231 entry below for information about
118 prerequisites and upgrading, if you are not already using clang 3.5.0
122 The RETPOLINE option produces non-functional ifunc-using binaries
123 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
124 Once Clang 8 is merged it may be enabled again.
127 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
128 7.0.1. Please see the 20141231 entry below for information about
129 prerequisites and upgrading, if you are not already using clang 3.5.0
133 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
134 compiled into your custom kernel, add 'device xz' statement to the
138 Iflib is no longer unconditionally compiled into the kernel. Drivers
139 using iflib and statically compiled into the kernel, now require
140 the 'device iflib' config option. For the same drivers loaded as
141 modules on kernels not having 'device iflib', the iflib.ko module
142 is loaded automatically.
145 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
146 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
147 servers that have vfs.nfsd.nfs_privport set will only allow mounts
148 from clients using a reserved port#. Since both the FreeBSD and Linux
149 NFSv4 clients use reserved port#s by default, this should not affect
153 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
154 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
155 it produces broken binaries when ifuncs are in use. Users needing
156 GNU ld should install the binutils port or package.
159 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
160 has been converted to a port (misc/ctm) and will be removed from
161 FreeBSD-13. A depreciation warning will be printed to stderr by
162 the ctm command, but the functionality will remain in base for all
166 The stable/12 branch has been created in subversion from head
170 Ports for the DRM modules have been simplified. Now, amd64 users should
171 just install the drm-kmod port. All others should install
174 Graphics hardware that's newer than about 2010 usually works with
175 drm-kmod. For hardware older than 2013, however, some users will need
176 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
177 than 2008 usually only works in drm-legacy-kmod. The graphics team can
178 only commit to hardware made since 2013 due to the complexity of the
179 market and difficulty to test all the older cards effectively. If you
180 have hardware supported by drm-kmod, you are strongly encouraged to use
181 that as you will get better support.
183 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
184 elsewhere, the drm and drm2 modules will be eliminated from the src base
185 soon (with a limited exception for arm). Please update to the package asap
186 and report any issues to x11@freebsd.org.
188 Generally, anybody using the drm*-kmod packages should add
189 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
190 cross-threading surprises, especially with automatic driver
191 loading from X11 startup. These will become the defaults in 13-current
195 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
196 custom kernel and module loading configuration files must be updated
197 accordingly. Moreover, interfaces previous presented as ixlvN to the
198 system are now exposed as iavfN and network configuration files must
199 be adjusted as necessary.
202 OpenSSL has been updated to version 1.1.1. This update included
203 additional various API changes througout the base system. It is
204 important to rebuild third-party software after upgrading. The value
205 of __FreeBSD_version has been bumped accordingly.
208 The legacy DRM modules and drivers have now been added to the loader's
209 module blacklist, in favor of loading them with kld_list in rc.conf(5).
210 The module blacklist may be overridden with the loader.conf(5)
211 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
215 The cam(4) based nda(4) driver will be used over nvd(4) by default on
216 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
217 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
218 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
222 Reproducible build mode is now on by default, in preparation for
223 FreeBSD 12.0. This eliminates build metadata such as the user,
224 host, and time from the kernel (and uname), unless the working tree
225 corresponds to a modified checkout from a version control system.
226 The previous behavior can be obtained by setting the /etc/src.conf
227 knob WITHOUT_REPRODUCIBLE_BUILD.
230 The Yarrow CSPRNG has been removed from the kernel as it has not been
231 supported by its designers since at least 2003. Fortuna has been the
232 default since FreeBSD-11.
235 devctl freeze/thaw have gone into the tree, the rc scripts have been
236 updated to use them and devmatch has been changed. You should update
237 kernel, userland and rc scripts all at the same time.
240 The default interpreter has been switched from 4th to Lua.
241 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
242 interpreter. If you have custom FORTH code you will need to set
243 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
244 src.conf for the build. This will create default hard links between
245 loader and loader_4th instead of loader and loader_lua, the new default.
246 If you are using UEFI it will create the proper hard link to loader.efi.
248 bhyve uses userboot.so. It remains 4th-only until some issues are solved
249 regarding coexisting with multiple versions of FreeBSD are resolved.
252 ls(1) now respects the COLORTERM environment variable used in other
253 systems and software to indicate that a colored terminal is both
254 supported and desired. If ls(1) is suddenly emitting colors, they may
255 be disabled again by either removing the unwanted COLORTERM from your
256 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
257 may not be observed in a future release.
260 The default pager for most commands has been changed to "less". To
261 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
265 The jedec_ts(4) driver has been removed. A superset of its functionality
266 is available in the jedec_dimm(4) driver, and the manpage for that
267 driver includes migration instructions. If you have "device jedec_ts"
268 in your kernel configuration file, it must be removed.
271 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
272 This should have no effect if the kernel is booted via BIOS/legacy boot.
273 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
274 has a buggy firmware that prevents a successful boot due to use of
278 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
279 support has been removed from the tree. These ports were
280 obsolete and/or known to be broken for many years.
283 loader.efi has been augmented to participate more fully in the
284 UEFI boot manager protocol. loader.efi will now look at the
285 BootXXXX environment variable to determine if a specific kernel
286 or root partition was specified. XXXX is derived from BootCurrent.
287 efibootmgr(8) manages these standard UEFI variables.
290 zfsloader's functionality has now been folded into loader.
291 zfsloader is no longer necessary once you've updated your
292 boot blocks. For a transition period, we will install a
293 hardlink for zfsloader to loader to allow a smooth transition
294 until the boot blocks can be updated (hard link because old
295 zfs boot blocks don't understand symlinks).
298 ARM64 now have efifb support, if you want to have serial console
299 on your arm64 board when an screen is connected and the bootloader
300 setup a frambuffer for us to use, just add :
304 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
305 an screen connected as the firmware will setup a framebuffer are that
306 u-boot will expose as an EFI framebuffer.
309 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
310 or take steps to update /etc/passwd before doing installworld on
311 existing systems. Do not skip the "mergemaster -Fp" step before
312 installworld, as described in the update procedures near the bottom
313 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
314 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
315 the ntp config file contain options that change file/dir locations.
316 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
317 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
318 taking steps to ensure that all required files/dirs are accessible
322 Big endian arm support has been removed.
325 The static environment setup in kernel configs is no longer mutually
326 exclusive with the loader(8) environment by default. In order to
327 restore the previous default behavior of disabling the loader(8)
328 environment if a static environment is present, you must specify
329 loader_env.disabled=1 in the static environment.
332 The ABI of syscalls used by management tools like sockstat and
333 netstat has been broken to allow 32-bit binaries to work on
334 64-bit kernels without modification. These programs will need
335 to match the kernel in order to function. External programs may
336 require minor modifications to accommodate a change of type in
337 structures from pointers to 64-bit virtual addresses.
340 On i386 and amd64 atomics are now inlined. Out of tree modules using
341 atomics will need to be rebuilt.
344 The '%I' format in the kern.corefile sysctl limits the number of
345 core files that a process can generate to the number stored in the
346 debug.ncores sysctl. The '%I' format is replaced by the single digit
347 index. Previously, if all indexes were taken the kernel would overwrite
348 only a core file with the highest index in a filename.
349 Currently the system will create a new core file if there is a free
350 index or if all slots are taken it will overwrite the oldest one.
353 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
354 6.0.1. Please see the 20141231 entry below for information about
355 prerequisites and upgrading, if you are not already using clang 3.5.0
359 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
360 needed to be changed to work with it. This change was made with r335763
361 and requires a mergemaster / etcupdate / etc to update the installed file.
364 r334930 changed the interface between the NFS modules, so they all
365 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
368 As of r334391 lld is the default amd64 system linker; it is installed
369 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
373 The kernel / userland interface for devinfo changed, so you'll
374 need a new kernel and userland as a pair for it to work (rebuilding
375 lib/libdevinfo is all that's required). devinfo and devmatch will
376 not work, but everything else will when there's a mismatch.
379 The on-disk format for hwpmc callchain records has changed to include
380 threadid corresponding to a given record. This changes the field offsets
381 and thus requires that libpmcstat be rebuilt before using a kernel
385 The vxge(4) driver has been removed. This driver was introduced into
386 HEAD one week before the Exar left the Ethernet market and is not
387 known to be used. If you have device vxge in your kernel config file
391 The amd64 kernel now requires a ld that supports ifunc to produce a
392 working kernel, either lld or a newer binutils. lld is built by default
393 on amd64, and the 'buildkernel' target uses it automatically. However,
394 it is not the default linker, so building the kernel the traditional
395 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
396 binutils port/package). lld will soon be default, and this requirement
399 NOTE: As of r334391 lld is the default system linker on amd64, and no
400 workaround is necessary.
403 The nxge(4) driver has been removed. This driver was for PCI-X 10g
404 cards made by s2io/Neterion. The company was aquired by Exar and
405 no longer sells or supports Ethernet products. If you have device
406 nxge in your kernel config file it must be removed.
409 The tz database (tzdb) has been updated to 2018e. This version more
410 correctly models time stamps in time zones with negative DST such as
411 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
412 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
413 time zone abbreviations and the tm_isdst flag.
416 The ixgb(4) driver has been removed. This driver was for an early and
417 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
418 quickly shifted to the long lived ixgbe family. If you have device
419 ixgb in your kernel config file it must be removed.
422 The lmc(4) driver has been removed. This was a WAN interface
423 card that was already reportedly rare in 2003, and had an ambiguous
424 license. If you have device lmc in your kernel config file it must
428 Support for Arcnet networks has been removed. If you have device
429 arcnet or device cm in your kernel config file they must be
433 Support for FDDI networks has been removed. If you have device
434 fddi or device fpa in your kernel config file they must be
438 In addition to supporting RFC 3164 formatted messages, the
439 syslogd(8) service is now capable of parsing RFC 5424 formatted
440 log messages. The main benefit of using RFC 5424 is that clients
441 may now send log messages with timestamps containing year numbers,
442 microseconds and time zone offsets.
444 Similarly, the syslog(3) C library function has been altered to
445 send RFC 5424 formatted messages to the local system logging
446 daemon. On systems using syslogd(8), this change should have no
447 negative impact, as long as syslogd(8) and the C library are
448 updated at the same time. On systems using a different system
449 logging daemon, it may be necessary to make configuration
450 adjustments, depending on the software used.
452 When using syslog-ng, add the 'syslog-protocol' flag to local
453 input sources to enable parsing of RFC 5424 formatted messages:
456 unix-dgram("/var/run/log" flags(syslog-protocol));
459 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
460 of the 'imuxsock' module to let messages be processed by the
461 regular RFC 3164/5424 parsing pipeline:
463 module(load="imuxsock" SysSock.UseSpecialParser="off")
465 Do note that these changes only affect communication between local
466 applications and syslogd(8). The format that syslogd(8) uses to
467 store messages on disk or forward messages to other systems
468 remains unchanged. syslogd(8) still uses RFC 3164 for these
469 purposes. Options to customize this behaviour will be added in the
470 future. Utilities that process log files stored in /var/log are
471 thus expected to continue to function as before.
473 __FreeBSD_version has been incremented to 1200061 to denote this
477 Support for token ring networks has been removed. If you
478 have "device token" in your kernel config you should remove
479 it. No device drivers supported token ring.
482 makefs was modified to be able to tag ISO9660 El Torito boot catalog
483 entries as EFI instead of overloading the i386 tag as done previously.
484 The amd64 mkisoimages.sh script used to build amd64 ISO images for
485 release was updated to use this. This may mean that makefs must be
486 updated before "make cdrom" can be run in the release directory. This
487 should be as simple as:
489 $ cd $SRCDIR/usr.sbin/makefs
490 $ make depend all install
493 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
494 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
495 Co-existance for the transition period will come shortly. Booting is a
496 complex environment and test coverage for Lua-enabled loaders has been
497 thin, so it would be prudent to assume it might not work and make
498 provisions for backup boot methods.
501 devmatch functionality has been turned on in devd. It will automatically
502 load drivers for unattached devices. This may cause unexpected drivers to
503 be loaded. Please report any problems to current@ and imp@freebsd.org.
506 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
507 6.0.0. Please see the 20141231 entry below for information about
508 prerequisites and upgrading, if you are not already using clang 3.5.0
512 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
513 This means it is used to link the kernel and userland libraries and
514 executables, but is not yet installed as /usr/bin/ld by default.
516 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
517 WITHOUT_LLD_BOOTSTRAP=yes
520 On i386, pmtimer has been removed. Its functionality has been folded
521 into apm. It was a no-op on ACPI in current for a while now (but was still
522 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
523 from kernel config files.
526 The use of RSS hash from the network card aka flowid has been
527 disabled by default for lagg(4) as it's currently incompatible with
528 the lacp and loadbalance protocols.
530 This can be re-enabled by setting the following in loader.conf:
531 net.link.lagg.default_use_flowid="1"
534 The SW_WATCHDOG option is no longer necessary to enable the
535 hardclock-based software watchdog if no hardware watchdog is
536 configured. As before, SW_WATCHDOG will cause the software
537 watchdog to be enabled even if a hardware watchdog is configured.
540 r326887 fixes the issue described in the 20171214 UPDATING entry.
541 r326888 flips the switch back to building GELI support always.
544 r362593 broke ZFS + GELI support for reasons unknown. However,
545 it also broke ZFS support generally, so GELI has been turned off
546 by default as the lesser evil in r326857. If you boot off ZFS and/or
547 GELI, it might not be a good time to update.
550 PowerPC users must update loader(8) by rebuilding world before
551 installing a new kernel, as the protocol connecting them has
552 changed. Without the update, loader metadata will not be passed
553 successfully to the kernel and users will have to enter their
554 root partition at the kernel mountroot prompt to continue booting.
555 Newer versions of loader can boot old kernels without issue.
558 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
559 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
560 to WITH/OUT_LOADER_GELI.
563 The naive and non-compliant support of posix_fallocate(2) in ZFS
564 has been removed as of r325320. The system call now returns EINVAL
565 when used on a ZFS file. Although the new behavior complies with the
566 standard, some consumers are not prepared to cope with it.
567 One known victim is lld prior to r325420.
570 Building in a FreeBSD src checkout will automatically create object
571 directories now rather than store files in the current directory if
572 'make obj' was not ran. Calling 'make obj' is no longer necessary.
573 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
574 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
578 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
579 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
580 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
581 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
582 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
583 The UNIFIED_OBJDIR option is a transitional feature that will be
584 removed for 12.0 release; please migrate to the new format for any
585 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
586 than hardcoding paths.
589 The native-xtools target no longer installs the files by default to the
590 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
591 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
594 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
595 options are changing from controlling the build if defined / undefined
596 to controlling the build with explicit 'yes' or 'no' values. They will
597 shift to WITH/WITHOUT options to match other options in the system.
600 libstand has turned into a private library for sys/boot use only.
601 It is no longer supported as a public interface outside of sys/boot.
604 The arm port has split armv6 into armv6 and armv7. armv7 is now
605 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
606 and are running a kernel from before r324363, you will need to add
607 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
610 When building multiple kernels using KERNCONF, non-existent KERNCONF
611 files will produce an error and buildkernel will fail. Previously
612 missing KERNCONF files silently failed giving no indication as to
613 why, only to subsequently discover during installkernel that the
614 desired kernel was never built in the first place.
617 The default serial number format for CTL LUNs has changed. This will
618 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
619 or iSCSI clients care about their LUNs' serial numbers. Users who
620 require serial number stability should hardcode serial numbers in
624 For 32-bit arm compiled for hard-float support, soft-floating point
625 binaries now always get their shared libraries from
626 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
627 /usr/libsoft also existed). Only users with a hard-float ld.so, but
628 soft-float everything else should be affected.
631 The geli password typed at boot is now hidden. To restore the previous
632 behavior, see geli(8) for configuration options.
635 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
636 sysctl values. Minor nit, but requires a rebuild of both world/kernel
640 "make check" behavior (made in ^/head@r295380) has been changed to
641 execute from a limited sandbox, as opposed to executing from
645 - The "beforecheck" and "aftercheck" targets are now specified.
646 - ${CHECKDIR} (added in commit noted above) has been removed.
647 - Legacy behavior can be enabled by setting
648 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
650 If the limited sandbox mode is enabled, "make check" will execute
651 "make distribution", then install, execute the tests, and clean up the
652 sandbox if successful.
654 The "make distribution" and "make install" targets are typically run as
655 root to set appropriate permissions and ownership at installation time.
656 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
657 environment if executing "make check" with limited sandbox mode using
658 an unprivileged user.
661 Since the switch to GPT disk labels, fsck for UFS/FFS has been
662 unable to automatically find alternate superblocks. As of r322297,
663 the information needed to find alternate superblocks has been
664 moved to the end of the area reserved for the boot block.
665 Filesystems created with a newfs of this vintage or later
666 will create the recovery information. If you have a filesystem
667 created prior to this change and wish to have a recovery block
668 created for your filesystem, you can do so by running fsck in
669 foreground mode (i.e., do not use the -p or -y options). As it
670 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
671 to which you should answer yes.
674 As of r321665, an NFSv4 server configuration that services
675 Kerberos mounts or clients that do not support the uid/gid in
676 owner/owner_group string capability, must explicitly enable
677 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
678 machine's /etc/rc.conf file.
681 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
682 Please see the 20141231 entry below for information about prerequisites
683 and upgrading, if you are not already using clang 3.5.0 or higher.
686 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
687 r-commands (rlogin, rsh, etc.) to be built with the base system.
690 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
691 a very major ABI incompatible change, so users of FreeBSD/powerpc must
692 be careful when performing source upgrades. It is best to run
693 'make installworld' from an alternate root system, either a live
694 CD/memory stick, or a temporary root partition. Additionally, all ports
695 must be recompiled. powerpc64 is largely unaffected, except in the case
696 of 32-bit compatibility. All 32-bit binaries will be affected.
699 Forward compatibility for the "ino64" project have been committed. This
700 will allow most new binaries to run on older kernels in a limited
701 fashion. This prevents many of the common foot-shooting actions in the
702 upgrade as well as the limited ability to roll back the kernel across
703 the ino64 upgrade. Complicated use cases may not work properly, though
704 enough simpler ones work to allow recovery in most situations.
707 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
708 if you require the GPL compiler.
711 The internal ABI used for communication between the NFS kernel modules
712 was changed by r320085, so __FreeBSD_version was bumped to
713 ensure all the NFS related modules are updated together.
716 The ABI of struct event was changed by extending the data
717 member to 64bit and adding ext fields. For upgrade, same
718 precautions as for the entry 20170523 "ino64" must be
722 The GNU roff toolchain has been removed from base. To render manpages
723 which are not supported by mandoc(1), man(1) can fallback on GNU roff
724 from ports (and recommends to install it).
725 To render roff(7) documents, consider using GNU roff from ports or the
726 heirloom doctools roff toolchain from ports via pkg install groff or
727 via pkg install heirloom-doctools.
730 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
731 smaller runtime footprint builds. This is useful for embedded systems
732 which only require one chipset support.
734 If you load it as a module, make sure this is in /boot/loader.conf:
738 This will load the HAL, all chip/RF backends and if_ath_pci.
739 If you have if_ath_pci in /boot/loader.conf, ensure it is after
740 if_ath or it will not load any HAL chipset support.
742 If you want to selectively load things (eg on ye cheape ARM/MIPS
743 platforms where RAM is at a premium) you should:
746 * load the chip modules in question
747 * load ath_rate, ath_dfs
749 * load if_ath_pci and/or if_ath_ahb depending upon your particular
750 bus bind type - this is where probe/attach is done.
752 For further comments/feedback, poke adrian@ .
755 The "ino64" 64-bit inode project has been committed, which extends
756 a number of types to 64 bits. Upgrading in place requires care and
757 adherence to the documented upgrade procedure.
759 If using a custom kernel configuration ensure that the
760 COMPAT_FREEBSD11 option is included (as during the upgrade the
761 system will be running the ino64 kernel with the existing world).
763 For the safest in-place upgrade begin by removing previous build
764 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
765 full procedure documented below under the heading "To rebuild
766 everything and install it on the current system." Specifically,
767 a reboot is required after installing the new kernel before
771 The NATM framework including the en(4), fatm(4), hatm(4), and
772 patm(4) devices has been removed. Consumers should plan a
773 migration before the end-of-life date for FreeBSD 11.
776 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
777 diff has not been implemented, if those are needed a newer version of
778 GNU diff is available via the diffutils package under the gdiff name.
781 As of r316810 for ipfilter, keep frags is no longer assumed when
782 keep state is specified in a rule. r316810 aligns ipfilter with
783 documentation in man pages separating keep frags from keep state.
784 This allows keep state to be specified without forcing keep frags
785 and allows keep frags to be specified independently of keep state.
786 To maintain previous behaviour, also specify keep frags with
787 keep state (as documented in ipf.conf.5).
790 arm64 builds now use the base system LLD 4.0.0 linker by default,
791 instead of requiring that the aarch64-binutils port or package be
792 installed. To continue using aarch64-binutils, set
793 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
796 The UDP optimization in entry 20160818 that added the sysctl
797 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
798 packets will no longer be treated as L3 broadcast packets.
801 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
802 use any explicitly assigned loopback address available in the jail
803 instead of using the first assigned address of the jail.
806 The ctl.ko module no longer implements the iSCSI target frontend:
807 cfiscsi.ko does instead.
809 If building cfiscsi.ko as a kernel module, the module can be loaded
810 via one of the following methods:
811 - `cfiscsi_load="YES"` in loader.conf(5).
812 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
813 - ctladm(8)/ctld(8), when compiled with iSCSI support
814 (`WITH_ISCSI=yes` in src.conf(5))
816 Please see cfiscsi(4) for more details.
819 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
820 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
821 same source (previously, the dependency of mmcsd.ko on mmc.ko was
822 missing, but mmcsd.ko now will refuse to load if it is incompatible
826 The syntax of ipfw(8) named states was changed to avoid ambiguity.
827 If you have used named states in the firewall rules, you need to modify
828 them after installworld and before rebooting. Now named states must
829 be prefixed with colon.
832 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
833 removed as the userland we provide cannot use them. The KMS version
834 (sys/dev/drm2) supports the same hardware.
837 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
838 Please see the 20141231 entry below for information about prerequisites
839 and upgrading, if you are not already using clang 3.5.0 or higher.
842 The code that provides support for ZFS .zfs/ directory functionality
843 has been reimplemented. It's not possible now to create a snapshot
844 by mkdir under .zfs/snapshot/. That should be the only user visible
848 EISA bus support has been removed. The WITH_EISA option is no longer
852 MCA bus support has been removed.
855 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
856 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
859 The EM_MULTIQUEUE kernel configuration option is deprecated now that
860 the em(4) driver conforms to iflib specifications.
863 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
864 IFLIB. If you have a custom kernel configuration that excludes em(4)
865 but you use igb(4), you need to re-add em(4) to your custom configuration.
868 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
869 Please see the 20141231 entry below for information about prerequisites
870 and upgrading, if you are not already using clang 3.5.0 or higher.
873 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
874 Please see the 20141231 entry below for information about prerequisites
875 and upgrading, if you are not already using clang 3.5.0 or higher.
878 The layout of the pmap structure has changed for powerpc to put the pmap
879 statistics at the front for all CPU variations. libkvm(3) and all tools
880 that link against it need to be recompiled.
883 isl(4) and cyapa(4) drivers now require a new driver,
884 chromebook_platform(4), to work properly on Chromebook-class hardware.
885 On other types of hardware the drivers may need to be configured using
886 device hints. Please see the corresponding manual pages for details.
889 The urtwn(4) driver was merged into rtwn(4) and now consists of
890 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
892 Also, firmware for RTL8188CE was renamed due to possible name
893 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
896 GNU rcs has been removed from base. It is available as packages:
897 - rcs: Latest GPLv3 GNU rcs version.
898 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
902 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
903 modules now requires that the kernel configuration contain the
904 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
907 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
908 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
911 Relocatable object files with the extension of .So have been renamed
912 to use an extension of .pico instead. The purpose of this change is
913 to avoid a name clash with shared libraries on case-insensitive file
914 systems. On those file systems, foo.So is the same file as foo.so.
917 GNU rcs has been turned off by default. It can (temporarily) be built
918 again by adding WITH_RCS knob in src.conf.
919 Otherwise, GNU rcs is available from packages:
920 - rcs: Latest GPLv3 GNU rcs version.
921 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
924 The backup_uses_rcs functionality has been removed from rc.subr.
927 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
928 two separate components, QUEUE_MACRO_DEBUG_TRACE and
929 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
930 QUEUE_MACRO_DEBUG behavior.
933 r304787 changed some ioctl interfaces between the iSCSI userspace
934 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
935 rebuilt to work with new kernels. __FreeBSD_version has been bumped
939 The UDP receive code has been updated to only treat incoming UDP
940 packets that were addressed to an L2 broadcast address as L3
941 broadcast packets. It is not expected that this will affect any
942 standards-conforming UDP application. The new behaviour can be
943 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
947 Remove the openbsd_poll system call.
948 __FreeBSD_version has been bumped because of this.
951 The stable/11 branch has been created from head@r302406.
954 The libc stub for the pipe(2) system call has been replaced with
955 a wrapper that calls the pipe2(2) system call and the pipe(2)
956 system call is now only implemented by the kernels that include
957 "options COMPAT_FREEBSD10" in their config file (this is the
958 default). Users should ensure that this option is enabled in
959 their kernel or upgrade userspace to r302092 before upgrading their
963 CAM will now strip leading spaces from SCSI disks' serial numbers.
964 This will affect users who create UFS filesystems on SCSI disks using
965 those disk's diskid device nodes. For example, if /etc/fstab
966 previously contained a line like
967 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
968 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
969 transforms like gmirror may also be affected. ZFS users should
973 The bitstring(3) API has been updated with new functionality and
974 improved performance. But it is binary-incompatible with the old API.
975 Objects built with the new headers may not be linked against objects
976 built with the old headers.
979 The brk and sbrk functions have been removed from libc on arm64.
980 Binutils from ports has been updated to not link to these
981 functions and should be updated to the latest version before
982 installing a new libc.
985 The armv6 port now defaults to hard float ABI. Limited support
986 for running both hardfloat and soft float on the same system
987 is available using the libraries installed with -DWITH_LIBSOFT.
988 This has only been tested as an upgrade path for installworld
989 and packages may fail or need manual intervention to run. New
990 packages will be needed.
992 To update an existing self-hosted armv6hf system, you must add
993 TARGET_ARCH=armv6 on the make command line for both the build
994 and the install steps.
997 Kernel modules compiled outside of a kernel build now default to
998 installing to /boot/modules instead of /boot/kernel. Many kernel
999 modules built this way (such as those in ports) already overrode
1000 KMODDIR explicitly to install into /boot/modules. However,
1001 manually building and installing a module from /sys/modules will
1002 now install to /boot/modules instead of /boot/kernel.
1005 The CAM I/O scheduler has been committed to the kernel. There should be
1006 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1007 list of known rogues that claim support for this but actually corrupt
1008 data is believed to be complete, be on the lookout for data
1009 corruption. The known rogue list is believed to be complete:
1011 o Crucial MX100, M550 drives with MU01 firmware.
1012 o Micron M510 and M550 drives with MU01 firmware.
1013 o Micron M500 prior to MU07 firmware
1014 o Samsung 830, 840, and 850 all firmwares
1015 o FCCT M500 all firmwares
1017 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1018 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1019 updated firmware. Black listed drives will work correctly because these
1020 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1021 this list is the same as found in Linux, it's believed there are no
1022 other rogues in the market place. All other models from the above
1025 To be safe, if you are at all concerned, you can quirk each of your
1026 drives to prevent NCQ from being sent by setting:
1027 kern.cam.ada.X.quirks="0x2"
1028 in loader.conf. If the drive requires the 4k sector quirk, set the
1029 quirks entry to 0x3.
1032 The FAST_DEPEND build option has been removed and its functionality is
1033 now the one true way. The old mkdep(1) style of 'make depend' has
1034 been removed. See 20160311 for further details.
1037 Resource range types have grown from unsigned long to uintmax_t. All
1038 drivers, and anything using libdevinfo, need to be recompiled.
1041 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1042 builds. It no longer runs mkdep(1) during 'make depend', and the
1043 'make depend' stage can safely be skipped now as it is auto ran
1044 when building 'make all' and will generate all SRCS and DPSRCS before
1045 building anything else. Dependencies are gathered at compile time with
1046 -MF flags kept in separate .depend files per object file. Users should
1047 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1048 stale .depend files.
1051 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1052 kernel modules. Therefore, if you load any kernel modules at boot time,
1053 please install the boot loaders after you install the kernel, but before
1057 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1058 make installkernel KERNCONF=YOUR_KERNEL_HERE
1059 make -C sys/boot install
1060 <reboot in single user>
1062 Then follow the usual steps, described in the General Notes section,
1066 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1067 see the 20141231 entry below for information about prerequisites and
1068 upgrading, if you are not already using clang 3.5.0 or higher.
1071 The AIO subsystem is now a standard part of the kernel. The
1072 VFS_AIO kernel option and aio.ko kernel module have been removed.
1073 Due to stability concerns, asynchronous I/O requests are only
1074 permitted on sockets and raw disks by default. To enable
1075 asynchronous I/O requests on all file types, set the
1076 vfs.aio.enable_unsafe sysctl to a non-zero value.
1079 The ELF object manipulation tool objcopy is now provided by the
1080 ELF Tool Chain project rather than by GNU binutils. It should be a
1081 drop-in replacement, with the addition of arm64 support. The
1082 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1083 to obtain the GNU version if necessary.
1086 Building ZFS pools on top of zvols is prohibited by default. That
1087 feature has never worked safely; it's always been prone to deadlocks.
1088 Using a zvol as the backing store for a VM guest's virtual disk will
1089 still work, even if the guest is using ZFS. Legacy behavior can be
1090 restored by setting vfs.zfs.vol.recursive=1.
1093 The NONE and HPN patches has been removed from OpenSSH. They are
1094 still available in the security/openssh-portable port.
1097 With the addition of ypldap(8), a new _ypldap user is now required
1098 during installworld. "mergemaster -p" can be used to add the user
1099 prior to installworld, as documented in the handbook.
1102 The tftp loader (pxeboot) now uses the option root-path directive. As a
1103 consequence it no longer looks for a pxeboot.4th file on the tftp
1104 server. Instead it uses the regular /boot infrastructure as with the
1108 The code to start recording plug and play data into the modules has
1109 been committed. While the old tools will properly build a new kernel,
1110 a number of warnings about "unknown metadata record 4" will be produced
1111 for an older kldxref. To avoid such warnings, make sure to rebuild
1112 the kernel toolchain (or world). Make sure that you have r292078 or
1113 later when trying to build 292077 or later before rebuilding.
1116 Debug data files are now built by default with 'make buildworld' and
1117 installed with 'make installworld'. This facilitates debugging but
1118 requires more disk space both during the build and for the installed
1119 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1123 r291527 changed the internal interface between the nfsd.ko and
1124 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1125 __FreeBSD_version has been bumped because of this.
1128 Add support for unicode collation strings leads to a change of
1129 order of files listed by ls(1) for example. To get back to the old
1130 behaviour, set LC_COLLATE environment variable to "C".
1132 Databases administrators will need to reindex their databases given
1133 collation results will be different.
1135 Due to a bug in install(1) it is recommended to remove the ancient
1136 locales before running make installworld.
1138 rm -rf /usr/share/locale/*
1141 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1142 libcrypto.so.7 or libssl.so.7 must be recompiled.
1145 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1146 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1147 should be replaced with isp_2400 and isp_2500 modules respectively.
1150 The build previously allowed using 'make -n' to not recurse into
1151 sub-directories while showing what commands would be executed, and
1152 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1153 and 'make -N' will not.
1156 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1157 and etcupdate will now use this file. A custom sendmail.cf is now
1158 updated via this mechanism rather than via installworld. If you had
1159 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1160 want to remove the exclusion or change it to "always install".
1161 /etc/mail/sendmail.cf is now managed the same way regardless of
1162 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1163 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1166 Compatibility shims for legacy ATA device names have been removed.
1167 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1168 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1169 environment variables, /dev/ad* and /dev/ar* symbolic links.
1172 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1173 Please see the 20141231 entry below for information about prerequisites
1174 and upgrading, if you are not already using clang 3.5.0 or higher.
1177 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1178 and renamed from .symbols to .debug. This reduces the size requirements
1179 on the boot partition or file system and provides consistency with
1180 userland debug files.
1182 When using the supported kernel installation method the
1183 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1184 as is done with /boot/kernel.
1186 Developers wishing to maintain the historical behavior of installing
1187 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1190 The wireless drivers had undergone changes that remove the 'parent
1191 interface' from the ifconfig -l output. The rc.d network scripts
1192 used to check presence of a parent interface in the list, so old
1193 scripts would fail to start wireless networking. Thus, etcupdate(3)
1194 or mergemaster(8) run is required after kernel update, to update your
1195 rc.d scripts in /etc.
1198 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1199 These configurations are now automatically interpreted as
1200 'scrub fragment reassemble'.
1203 Kernel-loadable modules for the random(4) device are back. To use
1204 them, the kernel must have
1207 options RANDOM_LOADABLE
1209 kldload(8) can then be used to load random_fortuna.ko
1210 or random_yarrow.ko. Please note that due to the indirect
1211 function calls that the loadable modules need to provide,
1212 the build-in variants will be slightly more efficient.
1214 The random(4) kernel option RANDOM_DUMMY has been retired due to
1215 unpopularity. It was not all that useful anyway.
1218 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1219 Control over building the ELF Tool Chain tools is now provided by
1220 the WITHOUT_TOOLCHAIN knob.
1223 The polarity of Pulse Per Second (PPS) capture events with the
1224 uart(4) driver has been corrected. Prior to this change the PPS
1225 "assert" event corresponded to the trailing edge of a positive PPS
1226 pulse and the "clear" event was the leading edge of the next pulse.
1228 As the width of a PPS pulse in a typical GPS receiver is on the
1229 order of 1 millisecond, most users will not notice any significant
1230 difference with this change.
1232 Anyone who has compensated for the historical polarity reversal by
1233 configuring a negative offset equal to the pulse width will need to
1234 remove that workaround.
1237 The default group assigned to /dev/dri entries has been changed
1238 from 'wheel' to 'video' with the id of '44'. If you want to have
1239 access to the dri devices please add yourself to the video group
1242 # pw groupmod video -m $USER
1245 The menu.rc and loader.rc files will now be replaced during
1246 upgrades. Please migrate local changes to menu.rc.local and
1247 loader.rc.local instead.
1250 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1251 strings and strip have been removed. The src.conf(5) knob
1252 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1255 As ZFS requires more kernel stack pages than is the default on some
1256 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1257 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1259 Please consider using 'options KSTACK_PAGES=X' where X is greater
1260 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1263 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1264 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1265 default, i.e., they will not contain "::". For example, instead
1266 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1267 to have a more specific match, such as different map entries for
1268 IPv6:0:0 vs IPv6:0. This change requires that configuration
1269 data (including maps, files, classes, custom ruleset, etc.) must
1270 use the same format, so make certain such configuration data is
1271 upgrading. As a very simple check search for patterns like
1272 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1273 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1274 the cf option UseCompressedIPv6Addresses.
1277 The default kernel entropy-processing algorithm is now
1278 Fortuna, replacing Yarrow.
1280 Assuming you have 'device random' in your kernel config
1281 file, the configurations allow a kernel option to override
1282 this default. You may choose *ONE* of:
1284 options RANDOM_YARROW # Legacy /dev/random algorithm.
1285 options RANDOM_DUMMY # Blocking-only driver.
1287 If you have neither, you get Fortuna. For most people,
1288 read no further, Fortuna will give a /dev/random that works
1289 like it always used to, and the difference will be irrelevant.
1291 If you remove 'device random', you get *NO* kernel-processed
1292 entropy at all. This may be acceptable to folks building
1293 embedded systems, but has complications. Carry on reading,
1294 and it is assumed you know what you need.
1296 *PLEASE* read random(4) and random(9) if you are in the
1297 habit of tweaking kernel configs, and/or if you are a member
1298 of the embedded community, wanting specific and not-usual
1299 behaviour from your security subsystems.
1301 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1302 random', you will NOT have a functioning /dev/random, and
1303 many cryptographic features will not work, including SSH.
1304 You may also find strange behaviour from the random(3) set
1305 of library functions, in particular sranddev(3), srandomdev(3)
1306 and arc4random(3). The reason for this is that the KERN_ARND
1307 sysctl only returns entropy if it thinks it has some to
1308 share, and with RANDOM_DUMMY or no 'device random' this
1312 An additional fix for the issue described in the 20150614 sendmail
1313 entry below has been committed in revision 284717.
1316 FreeBSD's old make (fmake) has been removed from the system. It is
1317 available as the devel/fmake port or via pkg install fmake.
1320 The fix for the issue described in the 20150614 sendmail entry
1321 below has been committed in revision 284436. The work
1322 around described in that entry is no longer needed unless the
1323 default setting is overridden by a confDH_PARAMETERS configuration
1324 setting of '5' or pointing to a 512 bit DH parameter file.
1327 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1328 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1329 and devel/kyua to version 0.20+ and adjust any calling code to work
1330 with Kyuafile and kyua.
1333 The import of openssl to address the FreeBSD-SA-15:10.openssl
1334 security advisory includes a change which rejects handshakes
1335 with DH parameters below 768 bits. sendmail releases prior
1336 to 8.15.2 (not yet released), defaulted to a 512 bit
1337 DH parameter setting for client connections. To work around
1338 this interoperability, sendmail can be configured to use a
1339 2048 bit DH parameter by:
1341 1. Edit /etc/mail/`hostname`.mc
1342 2. If a setting for confDH_PARAMETERS does not exist or
1343 exists and is set to a string beginning with '5',
1344 replace it with '2'.
1345 3. If a setting for confDH_PARAMETERS exists and is set to
1346 a file path, create a new file with:
1347 openssl dhparam -out /path/to/file 2048
1348 4. Rebuild the .cf file:
1349 cd /etc/mail/; make; make install
1350 5. Restart sendmail:
1351 cd /etc/mail/; make restart
1353 A sendmail patch is coming, at which time this file will be
1357 Generation of legacy formatted entries have been disabled by default
1358 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1359 entries were converted to use the new format by default when the new,
1360 machine independent format have been added and supported since FreeBSD
1363 Please see the pwd_mkdb(8) manual page for further details.
1366 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1367 20141231 entry below for information about prerequisites and upgrading,
1368 if you are not already using 3.5.0 or higher.
1371 TI platform code switched to using vendor DTS files and this update
1372 may break existing systems running on Beaglebone, Beaglebone Black,
1375 - dtb files should be regenerated/reinstalled. Filenames are the
1376 same but content is different now
1377 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1378 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1379 addressing scheme is now pin 25 on /dev/gpioc3.
1380 - Pandaboard: /etc/ttys should be updated, serial console device is
1381 now /dev/ttyu2, not /dev/ttyu0
1384 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1385 If you need the GNU extension from groff soelim(1), install groff
1386 from package: pkg install groff, or via ports: textproc/groff.
1389 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1390 defined in symlink(7); previously symlinks were silently ignored.
1393 The const qualifier has been removed from iconv(3) to comply with
1394 POSIX. The ports tree is aware of this from r384038 onwards.
1397 Libraries specified by LIBADD in Makefiles must have a corresponding
1398 DPADD_<lib> variable to ensure correct dependencies. This is now
1399 enforced in src.libnames.mk.
1402 From legacy ata(4) driver was removed support for SATA controllers
1403 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1404 Kernel modules ataahci and ataadaptec were removed completely,
1405 replaced by ahci and mvs modules respectively.
1408 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1409 the 20141231 entry below for information about prerequisites and
1410 upgrading, if you are not already using 3.5.0 or higher.
1413 The 32-bit PowerPC kernel has been changed to a position-independent
1414 executable. This can only be booted with a version of loader(8)
1415 newer than January 31, 2015, so make sure to update both world and
1416 kernel before rebooting.
1419 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1420 but before r278950, the RNG was not seeded properly. Immediately
1421 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1422 ssh keys or openssl keys) that were generated w/ a kernel from that
1423 range. This does not affect programs that directly used /dev/random
1424 or /dev/urandom. All userland uses of arc4random(3) are affected.
1427 The autofs(4) ABI was changed in order to restore binary compatibility
1428 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1429 with the new kernel.
1432 The powerpc64 kernel has been changed to a position-independent
1433 executable. This can only be booted with a new version of loader(8),
1434 so make sure to update both world and kernel before rebooting.
1437 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1438 only release, no new features have been added. Please see the 20141231
1439 entry below for information about prerequisites and upgrading, if you
1440 are not already using 3.5.0.
1443 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1444 taken from the ELF Tool Chain project rather than GNU binutils. They
1445 should be drop-in replacements, with the addition of arm64 support.
1446 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1447 binutils tools, if necessary. See 20150805 for updated information.
1450 The default Unbound configuration now enables remote control
1451 using a local socket. Users who have already enabled the
1452 local_unbound service should regenerate their configuration
1453 by running "service local_unbound setup" as root.
1456 The GNU texinfo and GNU info pages have been removed.
1457 To be able to view GNU info pages please install texinfo from ports.
1460 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1462 As of this release, a prerequisite for building clang, llvm and lldb is
1463 a C++11 capable compiler and C++11 standard library. This means that to
1464 be able to successfully build the cross-tools stage of buildworld, with
1465 clang as the bootstrap compiler, your system compiler or cross compiler
1466 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1467 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1470 On any standard FreeBSD 10.x or 11.x installation, where clang and
1471 libc++ are on by default (that is, on x86 or arm), this should work out
1474 On 9.x installations where clang is enabled by default, e.g. on x86 and
1475 powerpc, libc++ will not be enabled by default, so libc++ should be
1476 built (with clang) and installed first. If both clang and libc++ are
1477 missing, build clang first, then use it to build libc++.
1479 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1480 the instructions for 9.x above.
1482 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1483 default, and do not build clang.
1485 Many embedded systems are resource constrained, and will not be able to
1486 build clang in a reasonable time, or in some cases at all. In those
1487 cases, cross building bootable systems on amd64 is a workaround.
1489 This new version of clang introduces a number of new warnings, of which
1490 the following are most likely to appear:
1494 This warns in two cases, for both C and C++:
1495 * When the code is trying to take the absolute value of an unsigned
1496 quantity, which is effectively a no-op, and almost never what was
1497 intended. The code should be fixed, if at all possible. If you are
1498 sure that the unsigned quantity can be safely cast to signed, without
1499 loss of information or undefined behavior, you can add an explicit
1500 cast, or disable the warning.
1502 * When the code is trying to take an absolute value, but the called
1503 abs() variant is for the wrong type, which can lead to truncation.
1504 If you want to disable the warning instead of fixing the code, please
1505 make sure that truncation will not occur, or it might lead to unwanted
1508 -Wtautological-undefined-compare and
1509 -Wundefined-bool-conversion
1511 These warn when C++ code is trying to compare 'this' against NULL, while
1512 'this' should never be NULL in well-defined C++ code. However, there is
1513 some legacy (pre C++11) code out there, which actively abuses this
1514 feature, which was less strictly defined in previous C++ versions.
1516 Squid and openjdk do this, for example. The warning can be turned off
1517 for C++98 and earlier, but compiling the code in C++11 mode might result
1518 in unexpected behavior; for example, the parts of the program that are
1519 unreachable could be optimized away.
1522 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1523 kernel sources have been removed. The .h files remain, since some
1524 utilities include them. This will need to be fixed later.
1525 If "mount -t oldnfs ..." is attempted, it will fail.
1526 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1527 the utilities will report errors.
1530 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1531 directories to top level SUBDIR variable when their parent
1532 directory is included in LOCAL_DIRS. Users with build systems with
1533 such hierarchies and without SUBDIR entries in the parent
1534 directory Makefiles should add them or add the directories to
1538 faith(4) and faithd(8) have been removed from the base system. Faith
1539 has been obsolete for a very long time.
1542 vt(4), the new console driver, is enabled by default. It brings
1543 support for Unicode and double-width characters, as well as
1544 support for UEFI and integration with the KMS kernel video
1547 You may need to update your console settings in /etc/rc.conf,
1548 most probably the keymap. During boot, /etc/rc.d/syscons will
1549 indicate what you need to do.
1551 vt(4) still has issues and lacks some features compared to
1552 syscons(4). See the wiki for up-to-date information:
1553 https://wiki.freebsd.org/Newcons
1555 If you want to keep using syscons(4), you can do so by adding
1556 the following line to /boot/loader.conf:
1560 pjdfstest has been integrated into kyua as an opt-in test suite.
1561 Please see share/doc/pjdfstest/README for more details on how to
1565 gperf has been removed from the base system for architectures
1566 that use clang. Ports that require gperf will obtain it from the
1570 pjdfstest has been moved from tools/regression/pjdfstest to
1574 At svn r271982, The default linux compat kernel ABI has been adjusted
1575 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1576 update. If you wish to continue using the linux-f10 compat ports,
1577 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1578 encouraged to update their linux-compat packages to linux-c6 during
1579 their next update cycle.
1582 The ofwfb driver, used to provide a graphics console on PowerPC when
1583 using vt(4), no longer allows mmap() of all physical memory. This
1584 will prevent Xorg on PowerPC with some ATI graphics cards from
1585 initializing properly unless x11-servers/xorg-server is updated to
1589 The xdev targets have been converted to using TARGET and
1590 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1593 The default unbound configuration has been modified to address
1594 issues with reverse lookups on networks that use private
1595 address ranges. If you use the local_unbound service, run
1596 "service local_unbound setup" as root to regenerate your
1597 configuration, then "service local_unbound reload" to load the
1601 The GNU texinfo and GNU info pages are not built and installed
1602 anymore, WITH_INFO knob has been added to allow to built and install
1604 UPDATE: see 20150102 entry on texinfo's removal
1607 The GNU readline library is now an INTERNALLIB - that is, it is
1608 statically linked into consumers (GDB and variants) in the base
1609 system, and the shared library is no longer installed. The
1610 devel/readline port is available for third party software that
1614 The Itanium architecture (ia64) has been removed from the list of
1615 known architectures. This is the first step in the removal of the
1619 Commit r268115 has added NFSv4.1 server support, merged from
1620 projects/nfsv4.1-server. Since this includes changes to the
1621 internal interfaces between the NFS related modules, a full
1622 build of the kernel and modules will be necessary.
1623 __FreeBSD_version has been bumped.
1626 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1627 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1628 which differs from the behaviour controlled by this knob.)
1631 Maximal length of the serial number in CTL was increased from 16 to
1632 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1633 and ctld, need to be rebuilt to work with a new kernel.
1636 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1637 1 respectively to match the upstream numbers. They were out of
1638 sync because, when they were originally added to FreeBSD, the
1639 upstream versions were not respected. These libraries are private
1640 and not yet built by default, so renumbering them should be a
1641 non-issue. However, unclean source trees will yield broken test
1642 programs once the operator executes "make delete-old-libs" after a
1643 "make installworld".
1645 Additionally, the atf-sh binary was made private by moving it into
1646 /usr/libexec/. Already-built shell test programs will keep the
1647 path to the old binary so they will break after "make delete-old"
1650 If you are using WITH_TESTS=yes (not the default), wipe the object
1651 tree and rebuild from scratch to prevent spurious test failures.
1652 This is only needed once: the misnumbered libraries and misplaced
1653 binaries have been added to OptionalObsoleteFiles.inc so they will
1654 be removed during a clean upgrade.
1657 Clang and llvm have been upgraded to 3.4.1 release.
1660 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1661 be removed to avoid issues in the future (and has been added to
1665 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1666 past, it affected all builds that used the bsd.*.mk files. The old
1667 behavior was a bug, but people may have relied upon it. To get this
1668 behavior back, you can .include /etc/src.conf from /etc/make.conf
1669 (which is still global and isn't changed). This also changes the
1670 behavior of incremental builds inside the tree of individual
1671 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1672 Although this has survived make universe and some upgrade scenarios,
1673 other upgrade scenarios may have broken. At least one form of
1674 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1675 as well... In cases where MAKESYSPATH isn't working with this
1676 setting, you'll need to set it to the full path to your tree.
1678 One side effect of all this cleaning up is that bsd.compiler.mk
1679 is no longer implicitly included by bsd.own.mk. If you wish to
1680 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1684 The lindev device has been removed since /dev/full has been made a
1685 standard device. __FreeBSD_version has been bumped.
1688 The knob WITHOUT_VI was added to the base system, which controls
1689 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1690 in order to reorder files share/termcap and didn't build ex(1) as a
1691 build tool, so building/installing with WITH_VI is highly advised for
1692 build hosts for older releases.
1694 This issue has been fixed in stable/9 and stable/10 in r277022 and
1695 r276991, respectively.
1698 The YES_HESIOD knob has been removed. It has been obsolete for
1699 a decade. Please move to using WITH_HESIOD instead or your builds
1700 will silently lack HESIOD.
1703 The uart(4) driver has been changed with respect to its handling
1704 of the low-level console. Previously the uart(4) driver prevented
1705 any process from changing the baudrate or the CLOCAL and HUPCL
1706 control flags. By removing the restrictions, operators can make
1707 changes to the serial console port without having to reboot.
1708 However, when getty(8) is started on the serial device that is
1709 associated with the low-level console, a misconfigured terminal
1710 line in /etc/ttys will now have a real impact.
1711 Before upgrading the kernel, make sure that /etc/ttys has the
1712 serial console device configured as 3wire without baudrate to
1713 preserve the previous behaviour. E.g:
1714 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1717 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1718 to improve performance. To re-enable it, if needed, run rpcbind
1719 with command line option -W.
1722 Switched back to the GPL dtc compiler due to updates in the upstream
1723 dts files not being supported by the BSDL dtc compiler. You will need
1724 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1725 may result while building dtb files during a kernel build if you fail
1726 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1729 Clang and llvm have been upgraded to 3.4 release.
1732 The nve(4) driver has been removed. Please use the nfe(4) driver
1733 for NVIDIA nForce MCP Ethernet adapters instead.
1736 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1737 This could cause certain C++ applications using shared libraries built
1738 against the previous version of libc++ to crash. The incompatibility
1739 has now been fixed, but any C++ applications or shared libraries built
1740 between r261283 and r261801 should be recompiled.
1743 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1744 capability mode support. Please note that enabling the feature in
1745 kernel is still highly recommended.
1748 OpenSSH is now built with sandbox support, and will use sandbox as
1749 the default privilege separation method. This requires Capsicum
1750 capability mode support in kernel.
1753 The libelf and libdwarf libraries have been updated to newer
1754 versions from upstream. Shared library version numbers for
1755 these two libraries were bumped. Any ports or binaries
1756 requiring these two libraries should be recompiled.
1757 __FreeBSD_version is bumped to 1100006.
1760 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1761 instead of providing an explicit one, this would prevent such
1762 Makefile from providing its own Kyuafile in the future during
1763 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1764 intervention is needed to clean an objdir if you use NO_CLEAN:
1765 # find /usr/obj -name Kyuafile | xargs rm -f
1768 The behavior of gss_pseudo_random() for the krb5 mechanism
1769 has changed, for applications requesting a longer random string
1770 than produced by the underlying enctype's pseudo-random() function.
1771 In particular, the random string produced from a session key of
1772 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1773 be different at the 17th octet and later, after this change.
1774 The counter used in the PRF+ construction is now encoded as a
1775 big-endian integer in accordance with RFC 4402.
1776 __FreeBSD_version is bumped to 1100004.
1779 The WITHOUT_ATF build knob has been removed and its functionality
1780 has been subsumed into the more generic WITHOUT_TESTS. If you were
1781 using the former to disable the build of the ATF libraries, you
1782 should change your settings to use the latter.
1785 The default version of mtree is nmtree which is obtained from
1786 NetBSD. The output is generally the same, but may vary
1787 slightly. If you found you need identical output adding
1788 "-F freebsd9" to the command line should do the trick. For the
1789 time being, the old mtree is available as fmtree.
1792 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1793 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1794 1.1.4_8 and verify bsdyml not linked in, before running "make
1796 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1798 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1801 The stable/10 branch has been created in subversion from head
1808 Avoid using make -j when upgrading. While generally safe, there are
1809 sometimes problems using -j to upgrade. If your upgrade fails with
1810 -j, please try again without -j. From time to time in the past there
1811 have been problems using -j with buildworld and/or installworld. This
1812 is especially true when upgrading between "distant" versions (eg one
1813 that cross a major release boundary or several minor releases, or when
1814 several months have passed on the -current branch).
1816 Sometimes, obscure build problems are the result of environment
1817 poisoning. This can happen because the make utility reads its
1818 environment when searching for values for global variables. To run
1819 your build attempts in an "environmental clean room", prefix all make
1820 commands with 'env -i '. See the env(1) manual page for more details.
1822 When upgrading from one major version to another it is generally best to
1823 upgrade to the latest code in the currently installed branch first, then
1824 do an upgrade to the new branch. This is the best-tested upgrade path,
1825 and has the highest probability of being successful. Please try this
1826 approach if you encounter problems with a major version upgrade. Since
1827 the stable 4.x branch point, one has generally been able to upgrade from
1828 anywhere in the most recent stable branch to head / current (or even the
1829 last couple of stable branches). See the top of this file when there's
1832 When upgrading a live system, having a root shell around before
1833 installing anything can help undo problems. Not having a root shell
1834 around can lead to problems if pam has changed too much from your
1835 starting point to allow continued authentication after the upgrade.
1837 This file should be read as a log of events. When a later event changes
1838 information of a prior event, the prior event should not be deleted.
1839 Instead, a pointer to the entry with the new information should be
1840 placed in the old entry. Readers of this file should also sanity check
1841 older entries before relying on them blindly. Authors of new entries
1842 should write them with this in mind.
1846 When upgrading the boot ZFS pool to a new version, always follow
1849 1.) recompile and reinstall the ZFS boot loader and boot block
1850 (this is part of "make buildworld" and "make installworld")
1852 2.) update the ZFS boot block on your boot drive
1854 The following example updates the ZFS boot block on the first
1855 partition (freebsd-boot) of a GPT partitioned drive ada0:
1856 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1858 Non-boot pools do not need these updates.
1862 If you are updating from a prior version of FreeBSD (even one just
1863 a few days old), you should follow this procedure. It is the most
1864 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1866 make kernel-toolchain
1867 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1868 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1870 To test a kernel once
1871 ---------------------
1872 If you just want to boot a kernel once (because you are not sure
1873 if it works, or if you want to boot a known bad kernel to provide
1874 debugging information) run
1875 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1876 nextboot -k testkernel
1878 To rebuild everything and install it on the current system.
1879 -----------------------------------------------------------
1880 # Note: sometimes if you are running current you gotta do more than
1881 # is listed here if you are upgrading from a really old current.
1883 <make sure you have good level 0 dumps>
1885 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1886 make installkernel KERNCONF=YOUR_KERNEL_HERE
1888 <reboot in single user> [3]
1895 To cross-install current onto a separate partition
1896 --------------------------------------------------
1897 # In this approach we use a separate partition to hold
1898 # current's root, 'usr', and 'var' directories. A partition
1899 # holding "/", "/usr" and "/var" should be about 2GB in
1902 <make sure you have good level 0 dumps>
1905 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1906 <maybe newfs current's root partition>
1907 <mount current's root partition on directory ${CURRENT_ROOT}>
1908 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1909 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1910 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1911 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1912 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1913 <reboot into current>
1914 <do a "native" rebuild/install as described in the previous section>
1915 <maybe install compatibility libraries from ports/misc/compat*>
1919 To upgrade in-place from stable to current
1920 ----------------------------------------------
1921 <make sure you have good level 0 dumps>
1923 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1924 make installkernel KERNCONF=YOUR_KERNEL_HERE
1926 <reboot in single user> [3]
1933 Make sure that you've read the UPDATING file to understand the
1934 tweaks to various things you need. At this point in the life
1935 cycle of current, things change often and you are on your own
1936 to cope. The defaults can also change, so please read ALL of
1937 the UPDATING entries.
1939 Also, if you are tracking -current, you must be subscribed to
1940 freebsd-current@freebsd.org. Make sure that before you update
1941 your sources that you have read and understood all the recent
1942 messages there. If in doubt, please track -stable which has
1943 much fewer pitfalls.
1945 [1] If you have third party modules, such as vmware, you
1946 should disable them at this point so they don't crash your
1949 [3] From the bootblocks, boot -s, and then do
1954 adjkerntz -i # if CMOS is wall time
1955 Also, when doing a major release upgrade, it is required that
1956 you boot into single user mode to do the installworld.
1958 [4] Note: This step is non-optional. Failure to do this step
1959 can result in a significant reduction in the functionality of the
1960 system. Attempting to do it by hand is not recommended and those
1961 that pursue this avenue should read this file carefully, as well
1962 as the archives of freebsd-current and freebsd-hackers mailing lists
1963 for potential gotchas. The -U option is also useful to consider.
1964 See mergemaster(8) for more information.
1966 [5] Usually this step is a no-op. However, from time to time
1967 you may need to do this if you get unknown user in the following
1968 step. It never hurts to do it all the time. You may need to
1969 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1970 install) after the buildworld before this step if you last updated
1971 from current before 20130425 or from -stable before 20130430.
1973 [6] This only deletes old files and directories. Old libraries
1974 can be deleted by "make delete-old-libs", but you have to make
1975 sure that no program is using those libraries anymore.
1977 [8] The new kernel must be able to run existing binaries used by
1978 an installworld. When upgrading across major versions, the new
1979 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1980 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1981 binaries). Failure to do so may leave you with a system that is
1982 hard to boot to recover. A GENERIC kernel will include suitable
1983 compatibility options to run binaries from older branches.
1985 Make sure that you merge any new devices from GENERIC since the
1986 last time you updated your kernel config file.
1988 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1989 "?=" instead of the "=" assignment operator, so that buildworld can
1990 override the CPUTYPE if it needs to.
1992 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1993 not on the command line, or in /etc/make.conf. buildworld will
1994 warn if it is improperly defined.
1997 This file contains a list, in reverse chronological order, of major
1998 breakages in tracking -current. It is not guaranteed to be a complete
1999 list of such breakages, and only contains entries since September 23, 2011.
2000 If you need to see UPDATING entries from before that date, you will need
2001 to fetch an UPDATING file from an older FreeBSD release.
2003 Copyright information:
2005 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2007 Redistribution, publication, translation and use, with or without
2008 modification, in full or in part, in any form or format of this
2009 document are permitted without further permission from the author.
2011 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2012 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2013 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2014 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2015 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2016 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2017 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2018 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2019 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2020 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2021 POSSIBILITY OF SUCH DAMAGE.
2023 Contact Warner Losh if you have any questions about your use of