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 20200708 p7 FreeBSD-EN-20:13.bhyve
20 FreeBSD-EN-20:14.linuxkpi
22 FreeBSD-SA-20:19.unbound
25 Fix host crash in bhyve with PCI device passthrough. [EN-20:13.bhyve]
27 Fix kernel panic in LinuxKPI subsystem. [EN-20:14.linuxpki]
29 Fix kernel panic in mps(4) driver. [EN-20:15.mps]
31 Fix multiple vulnerabilities in unbound. [SA-20:19.unbound]
33 Fix IPv6 socket option race condition and use after free. [SA-20:20.ipv6]
35 20200609 p6 FreeBSD-EN-20:11.ena
36 FreeBSD-EN-20:12.iflib
39 Fix stability issues in ena(4) driver. [EN-20:11.ena]
41 Fix iflib watchdog timeout resetting idle queues. [EN-20:12.iflib]
43 Fix USB HID descriptor parsing error. [SA-20:17.usb]
45 20200512 p5 FreeBSD-EN-20:08.tzdata
47 FreeBSD-EN-20:10.build
48 FreeBSD-SA-20:12.libalias
49 FreeBSD-SA-20:13.libalias
50 FreeBSD-SA-20:15.cryptodev
51 FreeBSD-SA-20:16.cryptodev
53 Import tzdata 2020a. [EN-20:08.tzdata]
55 Fix igb interfaces failing to switch to inactive state [EN-20:09.igb]
57 Fix incorrect build host Clang version detection [EN-20:10.build]
59 Fix insufficient packet length validation in libalias [SA-20:12.libalias]
61 Fix memory disclosure vulnerability in libalias [SA-20:13.libalias]
63 Fix use after free in cryptodev module [SA-20:15.cryptodev]
65 Fix insufficient cryptodev MAC key length check [SA-20:16.cryptodev]
67 20200421 p4 FreeBSD-EN-20:07.quotad
69 FreeBSD-SA-20:11.openssl
71 Fix regression in rpc.rquotad with certain NFS servers [EN-20:07.quotad]
73 Fix ipfw invalid mbuf handling [SA-20:10.ipfw]
75 Fix OpenSSL remote denial of service vulnerability [SA-20:11.openssl]
77 20200319 p3 FreeBSD-EN-20:03.sshd
78 FreeBSD-EN-20:05.mlx5en
81 FreeBSD-SA-20:05.if_oce_ioctl
82 FreeBSD-SA-20:06.if_ixl_ioctl
83 FreeBSD-SA-20:07.epair
87 Fix misleading log messages upon successful sshd login [EN-20:03.sshd]
89 Fix packet forwarding performance in mlx5en(4) driver [EN-20:05.mlx5en]
91 Fix incorrect checksum calculations with IPv6 extension headers [EN-20:06.ipv6]
93 Fix TCP IPv6 SYN cache kernel information disclosure [SA-20:04.tcp]
95 Fix insufficient oce(4) ioctl(2) privilege checking [SA-20:05.if_oce_ioctl]
97 Fix insufficient ixl(4) ioctl(2) privilege checking [SA-20:06.if_ixl_ioctl]
99 Fix incorrect user-controlled pointer use in epair [SA-20:07.epair]
101 Fix kernel memory disclosure with nested jails [SA-20:08.jail]
103 Fix multiple denial of service in ntpd [SA-20:09.ntp]
105 20200128 p2 FreeBSD-EN-20:01.ssp
106 FreeBSD-SA-20:01.libfetch
107 FreeBSD-SA-20:03.thrmisc
109 Fix imprecise ordering of SSP canary initialization [EN-20:01.ssp]
111 Fix libfetch buffer overflow [SA-20:01.libfetch]
113 Fix kernel stack data disclosure [SA-20:03.thrmisc]
115 20191112 p1 FreeBSD-EN-19:19.loader
116 FreeBSD-SA-19:25.mcepsc
118 Fix UEFI Loader Memory Fragmentation [EN-19:19.loader]
120 Fix Machine Check Exception on Page Size Change [SA-19:25.mcepsc]
126 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
127 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
128 been removed from mount_fusefs(8). You can safely remove them from
129 your scripts, because they had no effect.
131 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
132 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
133 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
134 sysctls have been removed. If you felt the need to set any of them to
135 a non-default value, please tell asomers@FreeBSD.org why.
138 The fuse(4) module has been renamed to fusefs(4) for consistency with
139 other filesystems. You should update any kld_load="fuse" entries in
140 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
141 "options FUSE" enties in kernel config files.
144 Default permissions on the /var/account/acct file (and copies of it
145 rotated by periodic daily scripts) are changed from 0644 to 0640
146 because the file contains sensitive information that should not be
147 world-readable. If the /var/account directory must be created by
148 rc.d/accounting, the mode used is now 0750. Admins who use the
149 accounting feature are encouraged to change the mode of an existing
150 /var/account directory to 0750 or 0700.
153 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
154 been upgraded to 8.0.1. Please see the 20141231 entry below for
155 information about prerequisites and upgrading, if you are not already
156 using clang 3.5.0 or higher.
159 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
160 functionality needed for the RETPOLINE option should work properly
161 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
164 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
165 8.0.0. Please see the 20141231 entry below for information about
166 prerequisites and upgrading, if you are not already using clang 3.5.0
170 The RETPOLINE option produces non-functional ifunc-using binaries
171 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
172 Once Clang 8 is merged it may be enabled again.
175 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
176 7.0.1. Please see the 20141231 entry below for information about
177 prerequisites and upgrading, if you are not already using clang 3.5.0
181 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
182 compiled into your custom kernel, add 'device xz' statement to the
186 Iflib is no longer unconditionally compiled into the kernel. Drivers
187 using iflib and statically compiled into the kernel, now require
188 the 'device iflib' config option. For the same drivers loaded as
189 modules on kernels not having 'device iflib', the iflib.ko module
190 is loaded automatically.
193 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
194 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
195 servers that have vfs.nfsd.nfs_privport set will only allow mounts
196 from clients using a reserved port#. Since both the FreeBSD and Linux
197 NFSv4 clients use reserved port#s by default, this should not affect
201 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
202 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
203 it produces broken binaries when ifuncs are in use. Users needing
204 GNU ld should install the binutils port or package.
207 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
208 has been converted to a port (misc/ctm) and will be removed from
209 FreeBSD-13. A depreciation warning will be printed to stderr by
210 the ctm command, but the functionality will remain in base for all
214 The stable/12 branch has been created in subversion from head
218 Ports for the DRM modules have been simplified. Now, amd64 users should
219 just install the drm-kmod port. All others should install
222 Graphics hardware that's newer than about 2010 usually works with
223 drm-kmod. For hardware older than 2013, however, some users will need
224 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
225 than 2008 usually only works in drm-legacy-kmod. The graphics team can
226 only commit to hardware made since 2013 due to the complexity of the
227 market and difficulty to test all the older cards effectively. If you
228 have hardware supported by drm-kmod, you are strongly encouraged to use
229 that as you will get better support.
231 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
232 elsewhere, the drm and drm2 modules will be eliminated from the src base
233 soon (with a limited exception for arm). Please update to the package asap
234 and report any issues to x11@freebsd.org.
236 Generally, anybody using the drm*-kmod packages should add
237 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
238 cross-threading surprises, especially with automatic driver
239 loading from X11 startup. These will become the defaults in 13-current
243 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
244 custom kernel and module loading configuration files must be updated
245 accordingly. Moreover, interfaces previous presented as ixlvN to the
246 system are now exposed as iavfN and network configuration files must
247 be adjusted as necessary.
250 OpenSSL has been updated to version 1.1.1. This update included
251 additional various API changes througout the base system. It is
252 important to rebuild third-party software after upgrading. The value
253 of __FreeBSD_version has been bumped accordingly.
256 The legacy DRM modules and drivers have now been added to the loader's
257 module blacklist, in favor of loading them with kld_list in rc.conf(5).
258 The module blacklist may be overridden with the loader.conf(5)
259 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
263 The cam(4) based nda(4) driver will be used over nvd(4) by default on
264 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
265 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
266 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
270 Reproducible build mode is now on by default, in preparation for
271 FreeBSD 12.0. This eliminates build metadata such as the user,
272 host, and time from the kernel (and uname), unless the working tree
273 corresponds to a modified checkout from a version control system.
274 The previous behavior can be obtained by setting the /etc/src.conf
275 knob WITHOUT_REPRODUCIBLE_BUILD.
278 The Yarrow CSPRNG has been removed from the kernel as it has not been
279 supported by its designers since at least 2003. Fortuna has been the
280 default since FreeBSD-11.
283 devctl freeze/thaw have gone into the tree, the rc scripts have been
284 updated to use them and devmatch has been changed. You should update
285 kernel, userland and rc scripts all at the same time.
288 The default interpreter has been switched from 4th to Lua.
289 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
290 interpreter. If you have custom FORTH code you will need to set
291 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
292 src.conf for the build. This will create default hard links between
293 loader and loader_4th instead of loader and loader_lua, the new default.
294 If you are using UEFI it will create the proper hard link to loader.efi.
296 bhyve uses userboot.so. It remains 4th-only until some issues are solved
297 regarding coexisting with multiple versions of FreeBSD are resolved.
300 ls(1) now respects the COLORTERM environment variable used in other
301 systems and software to indicate that a colored terminal is both
302 supported and desired. If ls(1) is suddenly emitting colors, they may
303 be disabled again by either removing the unwanted COLORTERM from your
304 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
305 may not be observed in a future release.
308 The default pager for most commands has been changed to "less". To
309 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
313 The jedec_ts(4) driver has been removed. A superset of its functionality
314 is available in the jedec_dimm(4) driver, and the manpage for that
315 driver includes migration instructions. If you have "device jedec_ts"
316 in your kernel configuration file, it must be removed.
319 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
320 This should have no effect if the kernel is booted via BIOS/legacy boot.
321 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
322 has a buggy firmware that prevents a successful boot due to use of
326 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
327 support has been removed from the tree. These ports were
328 obsolete and/or known to be broken for many years.
331 loader.efi has been augmented to participate more fully in the
332 UEFI boot manager protocol. loader.efi will now look at the
333 BootXXXX environment variable to determine if a specific kernel
334 or root partition was specified. XXXX is derived from BootCurrent.
335 efibootmgr(8) manages these standard UEFI variables.
338 zfsloader's functionality has now been folded into loader.
339 zfsloader is no longer necessary once you've updated your
340 boot blocks. For a transition period, we will install a
341 hardlink for zfsloader to loader to allow a smooth transition
342 until the boot blocks can be updated (hard link because old
343 zfs boot blocks don't understand symlinks).
346 ARM64 now have efifb support, if you want to have serial console
347 on your arm64 board when an screen is connected and the bootloader
348 setup a frambuffer for us to use, just add :
352 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
353 an screen connected as the firmware will setup a framebuffer are that
354 u-boot will expose as an EFI framebuffer.
357 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
358 or take steps to update /etc/passwd before doing installworld on
359 existing systems. Do not skip the "mergemaster -Fp" step before
360 installworld, as described in the update procedures near the bottom
361 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
362 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
363 the ntp config file contain options that change file/dir locations.
364 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
365 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
366 taking steps to ensure that all required files/dirs are accessible
370 Big endian arm support has been removed.
373 The static environment setup in kernel configs is no longer mutually
374 exclusive with the loader(8) environment by default. In order to
375 restore the previous default behavior of disabling the loader(8)
376 environment if a static environment is present, you must specify
377 loader_env.disabled=1 in the static environment.
380 The ABI of syscalls used by management tools like sockstat and
381 netstat has been broken to allow 32-bit binaries to work on
382 64-bit kernels without modification. These programs will need
383 to match the kernel in order to function. External programs may
384 require minor modifications to accommodate a change of type in
385 structures from pointers to 64-bit virtual addresses.
388 On i386 and amd64 atomics are now inlined. Out of tree modules using
389 atomics will need to be rebuilt.
392 The '%I' format in the kern.corefile sysctl limits the number of
393 core files that a process can generate to the number stored in the
394 debug.ncores sysctl. The '%I' format is replaced by the single digit
395 index. Previously, if all indexes were taken the kernel would overwrite
396 only a core file with the highest index in a filename.
397 Currently the system will create a new core file if there is a free
398 index or if all slots are taken it will overwrite the oldest one.
401 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
402 6.0.1. Please see the 20141231 entry below for information about
403 prerequisites and upgrading, if you are not already using clang 3.5.0
407 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
408 needed to be changed to work with it. This change was made with r335763
409 and requires a mergemaster / etcupdate / etc to update the installed file.
412 r334930 changed the interface between the NFS modules, so they all
413 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
416 As of r334391 lld is the default amd64 system linker; it is installed
417 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
421 The kernel / userland interface for devinfo changed, so you'll
422 need a new kernel and userland as a pair for it to work (rebuilding
423 lib/libdevinfo is all that's required). devinfo and devmatch will
424 not work, but everything else will when there's a mismatch.
427 The on-disk format for hwpmc callchain records has changed to include
428 threadid corresponding to a given record. This changes the field offsets
429 and thus requires that libpmcstat be rebuilt before using a kernel
433 The vxge(4) driver has been removed. This driver was introduced into
434 HEAD one week before the Exar left the Ethernet market and is not
435 known to be used. If you have device vxge in your kernel config file
439 The amd64 kernel now requires a ld that supports ifunc to produce a
440 working kernel, either lld or a newer binutils. lld is built by default
441 on amd64, and the 'buildkernel' target uses it automatically. However,
442 it is not the default linker, so building the kernel the traditional
443 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
444 binutils port/package). lld will soon be default, and this requirement
447 NOTE: As of r334391 lld is the default system linker on amd64, and no
448 workaround is necessary.
451 The nxge(4) driver has been removed. This driver was for PCI-X 10g
452 cards made by s2io/Neterion. The company was aquired by Exar and
453 no longer sells or supports Ethernet products. If you have device
454 nxge in your kernel config file it must be removed.
457 The tz database (tzdb) has been updated to 2018e. This version more
458 correctly models time stamps in time zones with negative DST such as
459 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
460 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
461 time zone abbreviations and the tm_isdst flag.
464 The ixgb(4) driver has been removed. This driver was for an early and
465 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
466 quickly shifted to the long lived ixgbe family. If you have device
467 ixgb in your kernel config file it must be removed.
470 The lmc(4) driver has been removed. This was a WAN interface
471 card that was already reportedly rare in 2003, and had an ambiguous
472 license. If you have device lmc in your kernel config file it must
476 Support for Arcnet networks has been removed. If you have device
477 arcnet or device cm in your kernel config file they must be
481 Support for FDDI networks has been removed. If you have device
482 fddi or device fpa in your kernel config file they must be
486 In addition to supporting RFC 3164 formatted messages, the
487 syslogd(8) service is now capable of parsing RFC 5424 formatted
488 log messages. The main benefit of using RFC 5424 is that clients
489 may now send log messages with timestamps containing year numbers,
490 microseconds and time zone offsets.
492 Similarly, the syslog(3) C library function has been altered to
493 send RFC 5424 formatted messages to the local system logging
494 daemon. On systems using syslogd(8), this change should have no
495 negative impact, as long as syslogd(8) and the C library are
496 updated at the same time. On systems using a different system
497 logging daemon, it may be necessary to make configuration
498 adjustments, depending on the software used.
500 When using syslog-ng, add the 'syslog-protocol' flag to local
501 input sources to enable parsing of RFC 5424 formatted messages:
504 unix-dgram("/var/run/log" flags(syslog-protocol));
507 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
508 of the 'imuxsock' module to let messages be processed by the
509 regular RFC 3164/5424 parsing pipeline:
511 module(load="imuxsock" SysSock.UseSpecialParser="off")
513 Do note that these changes only affect communication between local
514 applications and syslogd(8). The format that syslogd(8) uses to
515 store messages on disk or forward messages to other systems
516 remains unchanged. syslogd(8) still uses RFC 3164 for these
517 purposes. Options to customize this behaviour will be added in the
518 future. Utilities that process log files stored in /var/log are
519 thus expected to continue to function as before.
521 __FreeBSD_version has been incremented to 1200061 to denote this
525 Support for token ring networks has been removed. If you
526 have "device token" in your kernel config you should remove
527 it. No device drivers supported token ring.
530 makefs was modified to be able to tag ISO9660 El Torito boot catalog
531 entries as EFI instead of overloading the i386 tag as done previously.
532 The amd64 mkisoimages.sh script used to build amd64 ISO images for
533 release was updated to use this. This may mean that makefs must be
534 updated before "make cdrom" can be run in the release directory. This
535 should be as simple as:
537 $ cd $SRCDIR/usr.sbin/makefs
538 $ make depend all install
541 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
542 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
543 Co-existance for the transition period will come shortly. Booting is a
544 complex environment and test coverage for Lua-enabled loaders has been
545 thin, so it would be prudent to assume it might not work and make
546 provisions for backup boot methods.
549 devmatch functionality has been turned on in devd. It will automatically
550 load drivers for unattached devices. This may cause unexpected drivers to
551 be loaded. Please report any problems to current@ and imp@freebsd.org.
554 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
555 6.0.0. Please see the 20141231 entry below for information about
556 prerequisites and upgrading, if you are not already using clang 3.5.0
560 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
561 This means it is used to link the kernel and userland libraries and
562 executables, but is not yet installed as /usr/bin/ld by default.
564 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
565 WITHOUT_LLD_BOOTSTRAP=yes
568 On i386, pmtimer has been removed. Its functionality has been folded
569 into apm. It was a no-op on ACPI in current for a while now (but was still
570 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
571 from kernel config files.
574 The use of RSS hash from the network card aka flowid has been
575 disabled by default for lagg(4) as it's currently incompatible with
576 the lacp and loadbalance protocols.
578 This can be re-enabled by setting the following in loader.conf:
579 net.link.lagg.default_use_flowid="1"
582 The SW_WATCHDOG option is no longer necessary to enable the
583 hardclock-based software watchdog if no hardware watchdog is
584 configured. As before, SW_WATCHDOG will cause the software
585 watchdog to be enabled even if a hardware watchdog is configured.
588 r326887 fixes the issue described in the 20171214 UPDATING entry.
589 r326888 flips the switch back to building GELI support always.
592 r362593 broke ZFS + GELI support for reasons unknown. However,
593 it also broke ZFS support generally, so GELI has been turned off
594 by default as the lesser evil in r326857. If you boot off ZFS and/or
595 GELI, it might not be a good time to update.
598 PowerPC users must update loader(8) by rebuilding world before
599 installing a new kernel, as the protocol connecting them has
600 changed. Without the update, loader metadata will not be passed
601 successfully to the kernel and users will have to enter their
602 root partition at the kernel mountroot prompt to continue booting.
603 Newer versions of loader can boot old kernels without issue.
606 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
607 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
608 to WITH/OUT_LOADER_GELI.
611 The naive and non-compliant support of posix_fallocate(2) in ZFS
612 has been removed as of r325320. The system call now returns EINVAL
613 when used on a ZFS file. Although the new behavior complies with the
614 standard, some consumers are not prepared to cope with it.
615 One known victim is lld prior to r325420.
618 Building in a FreeBSD src checkout will automatically create object
619 directories now rather than store files in the current directory if
620 'make obj' was not ran. Calling 'make obj' is no longer necessary.
621 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
622 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
626 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
627 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
628 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
629 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
630 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
631 The UNIFIED_OBJDIR option is a transitional feature that will be
632 removed for 12.0 release; please migrate to the new format for any
633 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
634 than hardcoding paths.
637 The native-xtools target no longer installs the files by default to the
638 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
639 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
642 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
643 options are changing from controlling the build if defined / undefined
644 to controlling the build with explicit 'yes' or 'no' values. They will
645 shift to WITH/WITHOUT options to match other options in the system.
648 libstand has turned into a private library for sys/boot use only.
649 It is no longer supported as a public interface outside of sys/boot.
652 The arm port has split armv6 into armv6 and armv7. armv7 is now
653 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
654 and are running a kernel from before r324363, you will need to add
655 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
658 When building multiple kernels using KERNCONF, non-existent KERNCONF
659 files will produce an error and buildkernel will fail. Previously
660 missing KERNCONF files silently failed giving no indication as to
661 why, only to subsequently discover during installkernel that the
662 desired kernel was never built in the first place.
665 The default serial number format for CTL LUNs has changed. This will
666 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
667 or iSCSI clients care about their LUNs' serial numbers. Users who
668 require serial number stability should hardcode serial numbers in
672 For 32-bit arm compiled for hard-float support, soft-floating point
673 binaries now always get their shared libraries from
674 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
675 /usr/libsoft also existed). Only users with a hard-float ld.so, but
676 soft-float everything else should be affected.
679 The geli password typed at boot is now hidden. To restore the previous
680 behavior, see geli(8) for configuration options.
683 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
684 sysctl values. Minor nit, but requires a rebuild of both world/kernel
688 "make check" behavior (made in ^/head@r295380) has been changed to
689 execute from a limited sandbox, as opposed to executing from
693 - The "beforecheck" and "aftercheck" targets are now specified.
694 - ${CHECKDIR} (added in commit noted above) has been removed.
695 - Legacy behavior can be enabled by setting
696 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
698 If the limited sandbox mode is enabled, "make check" will execute
699 "make distribution", then install, execute the tests, and clean up the
700 sandbox if successful.
702 The "make distribution" and "make install" targets are typically run as
703 root to set appropriate permissions and ownership at installation time.
704 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
705 environment if executing "make check" with limited sandbox mode using
706 an unprivileged user.
709 Since the switch to GPT disk labels, fsck for UFS/FFS has been
710 unable to automatically find alternate superblocks. As of r322297,
711 the information needed to find alternate superblocks has been
712 moved to the end of the area reserved for the boot block.
713 Filesystems created with a newfs of this vintage or later
714 will create the recovery information. If you have a filesystem
715 created prior to this change and wish to have a recovery block
716 created for your filesystem, you can do so by running fsck in
717 foreground mode (i.e., do not use the -p or -y options). As it
718 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
719 to which you should answer yes.
722 As of r321665, an NFSv4 server configuration that services
723 Kerberos mounts or clients that do not support the uid/gid in
724 owner/owner_group string capability, must explicitly enable
725 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
726 machine's /etc/rc.conf file.
729 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
730 Please see the 20141231 entry below for information about prerequisites
731 and upgrading, if you are not already using clang 3.5.0 or higher.
734 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
735 r-commands (rlogin, rsh, etc.) to be built with the base system.
738 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
739 a very major ABI incompatible change, so users of FreeBSD/powerpc must
740 be careful when performing source upgrades. It is best to run
741 'make installworld' from an alternate root system, either a live
742 CD/memory stick, or a temporary root partition. Additionally, all ports
743 must be recompiled. powerpc64 is largely unaffected, except in the case
744 of 32-bit compatibility. All 32-bit binaries will be affected.
747 Forward compatibility for the "ino64" project have been committed. This
748 will allow most new binaries to run on older kernels in a limited
749 fashion. This prevents many of the common foot-shooting actions in the
750 upgrade as well as the limited ability to roll back the kernel across
751 the ino64 upgrade. Complicated use cases may not work properly, though
752 enough simpler ones work to allow recovery in most situations.
755 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
756 if you require the GPL compiler.
759 The internal ABI used for communication between the NFS kernel modules
760 was changed by r320085, so __FreeBSD_version was bumped to
761 ensure all the NFS related modules are updated together.
764 The ABI of struct event was changed by extending the data
765 member to 64bit and adding ext fields. For upgrade, same
766 precautions as for the entry 20170523 "ino64" must be
770 The GNU roff toolchain has been removed from base. To render manpages
771 which are not supported by mandoc(1), man(1) can fallback on GNU roff
772 from ports (and recommends to install it).
773 To render roff(7) documents, consider using GNU roff from ports or the
774 heirloom doctools roff toolchain from ports via pkg install groff or
775 via pkg install heirloom-doctools.
778 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
779 smaller runtime footprint builds. This is useful for embedded systems
780 which only require one chipset support.
782 If you load it as a module, make sure this is in /boot/loader.conf:
786 This will load the HAL, all chip/RF backends and if_ath_pci.
787 If you have if_ath_pci in /boot/loader.conf, ensure it is after
788 if_ath or it will not load any HAL chipset support.
790 If you want to selectively load things (eg on ye cheape ARM/MIPS
791 platforms where RAM is at a premium) you should:
794 * load the chip modules in question
795 * load ath_rate, ath_dfs
797 * load if_ath_pci and/or if_ath_ahb depending upon your particular
798 bus bind type - this is where probe/attach is done.
800 For further comments/feedback, poke adrian@ .
803 The "ino64" 64-bit inode project has been committed, which extends
804 a number of types to 64 bits. Upgrading in place requires care and
805 adherence to the documented upgrade procedure.
807 If using a custom kernel configuration ensure that the
808 COMPAT_FREEBSD11 option is included (as during the upgrade the
809 system will be running the ino64 kernel with the existing world).
811 For the safest in-place upgrade begin by removing previous build
812 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
813 full procedure documented below under the heading "To rebuild
814 everything and install it on the current system." Specifically,
815 a reboot is required after installing the new kernel before
819 The NATM framework including the en(4), fatm(4), hatm(4), and
820 patm(4) devices has been removed. Consumers should plan a
821 migration before the end-of-life date for FreeBSD 11.
824 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
825 diff has not been implemented, if those are needed a newer version of
826 GNU diff is available via the diffutils package under the gdiff name.
829 As of r316810 for ipfilter, keep frags is no longer assumed when
830 keep state is specified in a rule. r316810 aligns ipfilter with
831 documentation in man pages separating keep frags from keep state.
832 This allows keep state to be specified without forcing keep frags
833 and allows keep frags to be specified independently of keep state.
834 To maintain previous behaviour, also specify keep frags with
835 keep state (as documented in ipf.conf.5).
838 arm64 builds now use the base system LLD 4.0.0 linker by default,
839 instead of requiring that the aarch64-binutils port or package be
840 installed. To continue using aarch64-binutils, set
841 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
844 The UDP optimization in entry 20160818 that added the sysctl
845 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
846 packets will no longer be treated as L3 broadcast packets.
849 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
850 use any explicitly assigned loopback address available in the jail
851 instead of using the first assigned address of the jail.
854 The ctl.ko module no longer implements the iSCSI target frontend:
855 cfiscsi.ko does instead.
857 If building cfiscsi.ko as a kernel module, the module can be loaded
858 via one of the following methods:
859 - `cfiscsi_load="YES"` in loader.conf(5).
860 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
861 - ctladm(8)/ctld(8), when compiled with iSCSI support
862 (`WITH_ISCSI=yes` in src.conf(5))
864 Please see cfiscsi(4) for more details.
867 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
868 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
869 same source (previously, the dependency of mmcsd.ko on mmc.ko was
870 missing, but mmcsd.ko now will refuse to load if it is incompatible
874 The syntax of ipfw(8) named states was changed to avoid ambiguity.
875 If you have used named states in the firewall rules, you need to modify
876 them after installworld and before rebooting. Now named states must
877 be prefixed with colon.
880 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
881 removed as the userland we provide cannot use them. The KMS version
882 (sys/dev/drm2) supports the same hardware.
885 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
886 Please see the 20141231 entry below for information about prerequisites
887 and upgrading, if you are not already using clang 3.5.0 or higher.
890 The code that provides support for ZFS .zfs/ directory functionality
891 has been reimplemented. It's not possible now to create a snapshot
892 by mkdir under .zfs/snapshot/. That should be the only user visible
896 EISA bus support has been removed. The WITH_EISA option is no longer
900 MCA bus support has been removed.
903 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
904 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
907 The EM_MULTIQUEUE kernel configuration option is deprecated now that
908 the em(4) driver conforms to iflib specifications.
911 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
912 IFLIB. If you have a custom kernel configuration that excludes em(4)
913 but you use igb(4), you need to re-add em(4) to your custom configuration.
916 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
917 Please see the 20141231 entry below for information about prerequisites
918 and upgrading, if you are not already using clang 3.5.0 or higher.
921 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
922 Please see the 20141231 entry below for information about prerequisites
923 and upgrading, if you are not already using clang 3.5.0 or higher.
926 The layout of the pmap structure has changed for powerpc to put the pmap
927 statistics at the front for all CPU variations. libkvm(3) and all tools
928 that link against it need to be recompiled.
931 isl(4) and cyapa(4) drivers now require a new driver,
932 chromebook_platform(4), to work properly on Chromebook-class hardware.
933 On other types of hardware the drivers may need to be configured using
934 device hints. Please see the corresponding manual pages for details.
937 The urtwn(4) driver was merged into rtwn(4) and now consists of
938 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
940 Also, firmware for RTL8188CE was renamed due to possible name
941 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
944 GNU rcs has been removed from base. It is available as packages:
945 - rcs: Latest GPLv3 GNU rcs version.
946 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
950 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
951 modules now requires that the kernel configuration contain the
952 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
955 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
956 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
959 Relocatable object files with the extension of .So have been renamed
960 to use an extension of .pico instead. The purpose of this change is
961 to avoid a name clash with shared libraries on case-insensitive file
962 systems. On those file systems, foo.So is the same file as foo.so.
965 GNU rcs has been turned off by default. It can (temporarily) be built
966 again by adding WITH_RCS knob in src.conf.
967 Otherwise, GNU rcs is available from packages:
968 - rcs: Latest GPLv3 GNU rcs version.
969 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
972 The backup_uses_rcs functionality has been removed from rc.subr.
975 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
976 two separate components, QUEUE_MACRO_DEBUG_TRACE and
977 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
978 QUEUE_MACRO_DEBUG behavior.
981 r304787 changed some ioctl interfaces between the iSCSI userspace
982 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
983 rebuilt to work with new kernels. __FreeBSD_version has been bumped
987 The UDP receive code has been updated to only treat incoming UDP
988 packets that were addressed to an L2 broadcast address as L3
989 broadcast packets. It is not expected that this will affect any
990 standards-conforming UDP application. The new behaviour can be
991 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
995 Remove the openbsd_poll system call.
996 __FreeBSD_version has been bumped because of this.
999 The stable/11 branch has been created from head@r302406.
1002 The libc stub for the pipe(2) system call has been replaced with
1003 a wrapper that calls the pipe2(2) system call and the pipe(2)
1004 system call is now only implemented by the kernels that include
1005 "options COMPAT_FREEBSD10" in their config file (this is the
1006 default). Users should ensure that this option is enabled in
1007 their kernel or upgrade userspace to r302092 before upgrading their
1011 CAM will now strip leading spaces from SCSI disks' serial numbers.
1012 This will affect users who create UFS filesystems on SCSI disks using
1013 those disk's diskid device nodes. For example, if /etc/fstab
1014 previously contained a line like
1015 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1016 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1017 transforms like gmirror may also be affected. ZFS users should
1021 The bitstring(3) API has been updated with new functionality and
1022 improved performance. But it is binary-incompatible with the old API.
1023 Objects built with the new headers may not be linked against objects
1024 built with the old headers.
1027 The brk and sbrk functions have been removed from libc on arm64.
1028 Binutils from ports has been updated to not link to these
1029 functions and should be updated to the latest version before
1030 installing a new libc.
1033 The armv6 port now defaults to hard float ABI. Limited support
1034 for running both hardfloat and soft float on the same system
1035 is available using the libraries installed with -DWITH_LIBSOFT.
1036 This has only been tested as an upgrade path for installworld
1037 and packages may fail or need manual intervention to run. New
1038 packages will be needed.
1040 To update an existing self-hosted armv6hf system, you must add
1041 TARGET_ARCH=armv6 on the make command line for both the build
1042 and the install steps.
1045 Kernel modules compiled outside of a kernel build now default to
1046 installing to /boot/modules instead of /boot/kernel. Many kernel
1047 modules built this way (such as those in ports) already overrode
1048 KMODDIR explicitly to install into /boot/modules. However,
1049 manually building and installing a module from /sys/modules will
1050 now install to /boot/modules instead of /boot/kernel.
1053 The CAM I/O scheduler has been committed to the kernel. There should be
1054 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1055 list of known rogues that claim support for this but actually corrupt
1056 data is believed to be complete, be on the lookout for data
1057 corruption. The known rogue list is believed to be complete:
1059 o Crucial MX100, M550 drives with MU01 firmware.
1060 o Micron M510 and M550 drives with MU01 firmware.
1061 o Micron M500 prior to MU07 firmware
1062 o Samsung 830, 840, and 850 all firmwares
1063 o FCCT M500 all firmwares
1065 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1066 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1067 updated firmware. Black listed drives will work correctly because these
1068 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1069 this list is the same as found in Linux, it's believed there are no
1070 other rogues in the market place. All other models from the above
1073 To be safe, if you are at all concerned, you can quirk each of your
1074 drives to prevent NCQ from being sent by setting:
1075 kern.cam.ada.X.quirks="0x2"
1076 in loader.conf. If the drive requires the 4k sector quirk, set the
1077 quirks entry to 0x3.
1080 The FAST_DEPEND build option has been removed and its functionality is
1081 now the one true way. The old mkdep(1) style of 'make depend' has
1082 been removed. See 20160311 for further details.
1085 Resource range types have grown from unsigned long to uintmax_t. All
1086 drivers, and anything using libdevinfo, need to be recompiled.
1089 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1090 builds. It no longer runs mkdep(1) during 'make depend', and the
1091 'make depend' stage can safely be skipped now as it is auto ran
1092 when building 'make all' and will generate all SRCS and DPSRCS before
1093 building anything else. Dependencies are gathered at compile time with
1094 -MF flags kept in separate .depend files per object file. Users should
1095 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1096 stale .depend files.
1099 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1100 kernel modules. Therefore, if you load any kernel modules at boot time,
1101 please install the boot loaders after you install the kernel, but before
1105 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1106 make installkernel KERNCONF=YOUR_KERNEL_HERE
1107 make -C sys/boot install
1108 <reboot in single user>
1110 Then follow the usual steps, described in the General Notes section,
1114 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1115 see the 20141231 entry below for information about prerequisites and
1116 upgrading, if you are not already using clang 3.5.0 or higher.
1119 The AIO subsystem is now a standard part of the kernel. The
1120 VFS_AIO kernel option and aio.ko kernel module have been removed.
1121 Due to stability concerns, asynchronous I/O requests are only
1122 permitted on sockets and raw disks by default. To enable
1123 asynchronous I/O requests on all file types, set the
1124 vfs.aio.enable_unsafe sysctl to a non-zero value.
1127 The ELF object manipulation tool objcopy is now provided by the
1128 ELF Tool Chain project rather than by GNU binutils. It should be a
1129 drop-in replacement, with the addition of arm64 support. The
1130 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1131 to obtain the GNU version if necessary.
1134 Building ZFS pools on top of zvols is prohibited by default. That
1135 feature has never worked safely; it's always been prone to deadlocks.
1136 Using a zvol as the backing store for a VM guest's virtual disk will
1137 still work, even if the guest is using ZFS. Legacy behavior can be
1138 restored by setting vfs.zfs.vol.recursive=1.
1141 The NONE and HPN patches has been removed from OpenSSH. They are
1142 still available in the security/openssh-portable port.
1145 With the addition of ypldap(8), a new _ypldap user is now required
1146 during installworld. "mergemaster -p" can be used to add the user
1147 prior to installworld, as documented in the handbook.
1150 The tftp loader (pxeboot) now uses the option root-path directive. As a
1151 consequence it no longer looks for a pxeboot.4th file on the tftp
1152 server. Instead it uses the regular /boot infrastructure as with the
1156 The code to start recording plug and play data into the modules has
1157 been committed. While the old tools will properly build a new kernel,
1158 a number of warnings about "unknown metadata record 4" will be produced
1159 for an older kldxref. To avoid such warnings, make sure to rebuild
1160 the kernel toolchain (or world). Make sure that you have r292078 or
1161 later when trying to build 292077 or later before rebuilding.
1164 Debug data files are now built by default with 'make buildworld' and
1165 installed with 'make installworld'. This facilitates debugging but
1166 requires more disk space both during the build and for the installed
1167 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1171 r291527 changed the internal interface between the nfsd.ko and
1172 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1173 __FreeBSD_version has been bumped because of this.
1176 Add support for unicode collation strings leads to a change of
1177 order of files listed by ls(1) for example. To get back to the old
1178 behaviour, set LC_COLLATE environment variable to "C".
1180 Databases administrators will need to reindex their databases given
1181 collation results will be different.
1183 Due to a bug in install(1) it is recommended to remove the ancient
1184 locales before running make installworld.
1186 rm -rf /usr/share/locale/*
1189 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1190 libcrypto.so.7 or libssl.so.7 must be recompiled.
1193 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1194 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1195 should be replaced with isp_2400 and isp_2500 modules respectively.
1198 The build previously allowed using 'make -n' to not recurse into
1199 sub-directories while showing what commands would be executed, and
1200 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1201 and 'make -N' will not.
1204 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1205 and etcupdate will now use this file. A custom sendmail.cf is now
1206 updated via this mechanism rather than via installworld. If you had
1207 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1208 want to remove the exclusion or change it to "always install".
1209 /etc/mail/sendmail.cf is now managed the same way regardless of
1210 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1211 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1214 Compatibility shims for legacy ATA device names have been removed.
1215 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1216 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1217 environment variables, /dev/ad* and /dev/ar* symbolic links.
1220 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1221 Please see the 20141231 entry below for information about prerequisites
1222 and upgrading, if you are not already using clang 3.5.0 or higher.
1225 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1226 and renamed from .symbols to .debug. This reduces the size requirements
1227 on the boot partition or file system and provides consistency with
1228 userland debug files.
1230 When using the supported kernel installation method the
1231 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1232 as is done with /boot/kernel.
1234 Developers wishing to maintain the historical behavior of installing
1235 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1238 The wireless drivers had undergone changes that remove the 'parent
1239 interface' from the ifconfig -l output. The rc.d network scripts
1240 used to check presence of a parent interface in the list, so old
1241 scripts would fail to start wireless networking. Thus, etcupdate(3)
1242 or mergemaster(8) run is required after kernel update, to update your
1243 rc.d scripts in /etc.
1246 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1247 These configurations are now automatically interpreted as
1248 'scrub fragment reassemble'.
1251 Kernel-loadable modules for the random(4) device are back. To use
1252 them, the kernel must have
1255 options RANDOM_LOADABLE
1257 kldload(8) can then be used to load random_fortuna.ko
1258 or random_yarrow.ko. Please note that due to the indirect
1259 function calls that the loadable modules need to provide,
1260 the build-in variants will be slightly more efficient.
1262 The random(4) kernel option RANDOM_DUMMY has been retired due to
1263 unpopularity. It was not all that useful anyway.
1266 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1267 Control over building the ELF Tool Chain tools is now provided by
1268 the WITHOUT_TOOLCHAIN knob.
1271 The polarity of Pulse Per Second (PPS) capture events with the
1272 uart(4) driver has been corrected. Prior to this change the PPS
1273 "assert" event corresponded to the trailing edge of a positive PPS
1274 pulse and the "clear" event was the leading edge of the next pulse.
1276 As the width of a PPS pulse in a typical GPS receiver is on the
1277 order of 1 millisecond, most users will not notice any significant
1278 difference with this change.
1280 Anyone who has compensated for the historical polarity reversal by
1281 configuring a negative offset equal to the pulse width will need to
1282 remove that workaround.
1285 The default group assigned to /dev/dri entries has been changed
1286 from 'wheel' to 'video' with the id of '44'. If you want to have
1287 access to the dri devices please add yourself to the video group
1290 # pw groupmod video -m $USER
1293 The menu.rc and loader.rc files will now be replaced during
1294 upgrades. Please migrate local changes to menu.rc.local and
1295 loader.rc.local instead.
1298 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1299 strings and strip have been removed. The src.conf(5) knob
1300 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1303 As ZFS requires more kernel stack pages than is the default on some
1304 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1305 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1307 Please consider using 'options KSTACK_PAGES=X' where X is greater
1308 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1311 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1312 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1313 default, i.e., they will not contain "::". For example, instead
1314 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1315 to have a more specific match, such as different map entries for
1316 IPv6:0:0 vs IPv6:0. This change requires that configuration
1317 data (including maps, files, classes, custom ruleset, etc.) must
1318 use the same format, so make certain such configuration data is
1319 upgrading. As a very simple check search for patterns like
1320 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1321 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1322 the cf option UseCompressedIPv6Addresses.
1325 The default kernel entropy-processing algorithm is now
1326 Fortuna, replacing Yarrow.
1328 Assuming you have 'device random' in your kernel config
1329 file, the configurations allow a kernel option to override
1330 this default. You may choose *ONE* of:
1332 options RANDOM_YARROW # Legacy /dev/random algorithm.
1333 options RANDOM_DUMMY # Blocking-only driver.
1335 If you have neither, you get Fortuna. For most people,
1336 read no further, Fortuna will give a /dev/random that works
1337 like it always used to, and the difference will be irrelevant.
1339 If you remove 'device random', you get *NO* kernel-processed
1340 entropy at all. This may be acceptable to folks building
1341 embedded systems, but has complications. Carry on reading,
1342 and it is assumed you know what you need.
1344 *PLEASE* read random(4) and random(9) if you are in the
1345 habit of tweaking kernel configs, and/or if you are a member
1346 of the embedded community, wanting specific and not-usual
1347 behaviour from your security subsystems.
1349 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1350 random', you will NOT have a functioning /dev/random, and
1351 many cryptographic features will not work, including SSH.
1352 You may also find strange behaviour from the random(3) set
1353 of library functions, in particular sranddev(3), srandomdev(3)
1354 and arc4random(3). The reason for this is that the KERN_ARND
1355 sysctl only returns entropy if it thinks it has some to
1356 share, and with RANDOM_DUMMY or no 'device random' this
1360 An additional fix for the issue described in the 20150614 sendmail
1361 entry below has been committed in revision 284717.
1364 FreeBSD's old make (fmake) has been removed from the system. It is
1365 available as the devel/fmake port or via pkg install fmake.
1368 The fix for the issue described in the 20150614 sendmail entry
1369 below has been committed in revision 284436. The work
1370 around described in that entry is no longer needed unless the
1371 default setting is overridden by a confDH_PARAMETERS configuration
1372 setting of '5' or pointing to a 512 bit DH parameter file.
1375 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1376 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1377 and devel/kyua to version 0.20+ and adjust any calling code to work
1378 with Kyuafile and kyua.
1381 The import of openssl to address the FreeBSD-SA-15:10.openssl
1382 security advisory includes a change which rejects handshakes
1383 with DH parameters below 768 bits. sendmail releases prior
1384 to 8.15.2 (not yet released), defaulted to a 512 bit
1385 DH parameter setting for client connections. To work around
1386 this interoperability, sendmail can be configured to use a
1387 2048 bit DH parameter by:
1389 1. Edit /etc/mail/`hostname`.mc
1390 2. If a setting for confDH_PARAMETERS does not exist or
1391 exists and is set to a string beginning with '5',
1392 replace it with '2'.
1393 3. If a setting for confDH_PARAMETERS exists and is set to
1394 a file path, create a new file with:
1395 openssl dhparam -out /path/to/file 2048
1396 4. Rebuild the .cf file:
1397 cd /etc/mail/; make; make install
1398 5. Restart sendmail:
1399 cd /etc/mail/; make restart
1401 A sendmail patch is coming, at which time this file will be
1405 Generation of legacy formatted entries have been disabled by default
1406 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1407 entries were converted to use the new format by default when the new,
1408 machine independent format have been added and supported since FreeBSD
1411 Please see the pwd_mkdb(8) manual page for further details.
1414 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1415 20141231 entry below for information about prerequisites and upgrading,
1416 if you are not already using 3.5.0 or higher.
1419 TI platform code switched to using vendor DTS files and this update
1420 may break existing systems running on Beaglebone, Beaglebone Black,
1423 - dtb files should be regenerated/reinstalled. Filenames are the
1424 same but content is different now
1425 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1426 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1427 addressing scheme is now pin 25 on /dev/gpioc3.
1428 - Pandaboard: /etc/ttys should be updated, serial console device is
1429 now /dev/ttyu2, not /dev/ttyu0
1432 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1433 If you need the GNU extension from groff soelim(1), install groff
1434 from package: pkg install groff, or via ports: textproc/groff.
1437 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1438 defined in symlink(7); previously symlinks were silently ignored.
1441 The const qualifier has been removed from iconv(3) to comply with
1442 POSIX. The ports tree is aware of this from r384038 onwards.
1445 Libraries specified by LIBADD in Makefiles must have a corresponding
1446 DPADD_<lib> variable to ensure correct dependencies. This is now
1447 enforced in src.libnames.mk.
1450 From legacy ata(4) driver was removed support for SATA controllers
1451 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1452 Kernel modules ataahci and ataadaptec were removed completely,
1453 replaced by ahci and mvs modules respectively.
1456 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1457 the 20141231 entry below for information about prerequisites and
1458 upgrading, if you are not already using 3.5.0 or higher.
1461 The 32-bit PowerPC kernel has been changed to a position-independent
1462 executable. This can only be booted with a version of loader(8)
1463 newer than January 31, 2015, so make sure to update both world and
1464 kernel before rebooting.
1467 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1468 but before r278950, the RNG was not seeded properly. Immediately
1469 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1470 ssh keys or openssl keys) that were generated w/ a kernel from that
1471 range. This does not affect programs that directly used /dev/random
1472 or /dev/urandom. All userland uses of arc4random(3) are affected.
1475 The autofs(4) ABI was changed in order to restore binary compatibility
1476 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1477 with the new kernel.
1480 The powerpc64 kernel has been changed to a position-independent
1481 executable. This can only be booted with a new version of loader(8),
1482 so make sure to update both world and kernel before rebooting.
1485 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1486 only release, no new features have been added. Please see the 20141231
1487 entry below for information about prerequisites and upgrading, if you
1488 are not already using 3.5.0.
1491 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1492 taken from the ELF Tool Chain project rather than GNU binutils. They
1493 should be drop-in replacements, with the addition of arm64 support.
1494 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1495 binutils tools, if necessary. See 20150805 for updated information.
1498 The default Unbound configuration now enables remote control
1499 using a local socket. Users who have already enabled the
1500 local_unbound service should regenerate their configuration
1501 by running "service local_unbound setup" as root.
1504 The GNU texinfo and GNU info pages have been removed.
1505 To be able to view GNU info pages please install texinfo from ports.
1508 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1510 As of this release, a prerequisite for building clang, llvm and lldb is
1511 a C++11 capable compiler and C++11 standard library. This means that to
1512 be able to successfully build the cross-tools stage of buildworld, with
1513 clang as the bootstrap compiler, your system compiler or cross compiler
1514 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1515 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1518 On any standard FreeBSD 10.x or 11.x installation, where clang and
1519 libc++ are on by default (that is, on x86 or arm), this should work out
1522 On 9.x installations where clang is enabled by default, e.g. on x86 and
1523 powerpc, libc++ will not be enabled by default, so libc++ should be
1524 built (with clang) and installed first. If both clang and libc++ are
1525 missing, build clang first, then use it to build libc++.
1527 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1528 the instructions for 9.x above.
1530 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1531 default, and do not build clang.
1533 Many embedded systems are resource constrained, and will not be able to
1534 build clang in a reasonable time, or in some cases at all. In those
1535 cases, cross building bootable systems on amd64 is a workaround.
1537 This new version of clang introduces a number of new warnings, of which
1538 the following are most likely to appear:
1542 This warns in two cases, for both C and C++:
1543 * When the code is trying to take the absolute value of an unsigned
1544 quantity, which is effectively a no-op, and almost never what was
1545 intended. The code should be fixed, if at all possible. If you are
1546 sure that the unsigned quantity can be safely cast to signed, without
1547 loss of information or undefined behavior, you can add an explicit
1548 cast, or disable the warning.
1550 * When the code is trying to take an absolute value, but the called
1551 abs() variant is for the wrong type, which can lead to truncation.
1552 If you want to disable the warning instead of fixing the code, please
1553 make sure that truncation will not occur, or it might lead to unwanted
1556 -Wtautological-undefined-compare and
1557 -Wundefined-bool-conversion
1559 These warn when C++ code is trying to compare 'this' against NULL, while
1560 'this' should never be NULL in well-defined C++ code. However, there is
1561 some legacy (pre C++11) code out there, which actively abuses this
1562 feature, which was less strictly defined in previous C++ versions.
1564 Squid and openjdk do this, for example. The warning can be turned off
1565 for C++98 and earlier, but compiling the code in C++11 mode might result
1566 in unexpected behavior; for example, the parts of the program that are
1567 unreachable could be optimized away.
1570 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1571 kernel sources have been removed. The .h files remain, since some
1572 utilities include them. This will need to be fixed later.
1573 If "mount -t oldnfs ..." is attempted, it will fail.
1574 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1575 the utilities will report errors.
1578 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1579 directories to top level SUBDIR variable when their parent
1580 directory is included in LOCAL_DIRS. Users with build systems with
1581 such hierarchies and without SUBDIR entries in the parent
1582 directory Makefiles should add them or add the directories to
1586 faith(4) and faithd(8) have been removed from the base system. Faith
1587 has been obsolete for a very long time.
1590 vt(4), the new console driver, is enabled by default. It brings
1591 support for Unicode and double-width characters, as well as
1592 support for UEFI and integration with the KMS kernel video
1595 You may need to update your console settings in /etc/rc.conf,
1596 most probably the keymap. During boot, /etc/rc.d/syscons will
1597 indicate what you need to do.
1599 vt(4) still has issues and lacks some features compared to
1600 syscons(4). See the wiki for up-to-date information:
1601 https://wiki.freebsd.org/Newcons
1603 If you want to keep using syscons(4), you can do so by adding
1604 the following line to /boot/loader.conf:
1608 pjdfstest has been integrated into kyua as an opt-in test suite.
1609 Please see share/doc/pjdfstest/README for more details on how to
1613 gperf has been removed from the base system for architectures
1614 that use clang. Ports that require gperf will obtain it from the
1618 pjdfstest has been moved from tools/regression/pjdfstest to
1622 At svn r271982, The default linux compat kernel ABI has been adjusted
1623 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1624 update. If you wish to continue using the linux-f10 compat ports,
1625 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1626 encouraged to update their linux-compat packages to linux-c6 during
1627 their next update cycle.
1630 The ofwfb driver, used to provide a graphics console on PowerPC when
1631 using vt(4), no longer allows mmap() of all physical memory. This
1632 will prevent Xorg on PowerPC with some ATI graphics cards from
1633 initializing properly unless x11-servers/xorg-server is updated to
1637 The xdev targets have been converted to using TARGET and
1638 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1641 The default unbound configuration has been modified to address
1642 issues with reverse lookups on networks that use private
1643 address ranges. If you use the local_unbound service, run
1644 "service local_unbound setup" as root to regenerate your
1645 configuration, then "service local_unbound reload" to load the
1649 The GNU texinfo and GNU info pages are not built and installed
1650 anymore, WITH_INFO knob has been added to allow to built and install
1652 UPDATE: see 20150102 entry on texinfo's removal
1655 The GNU readline library is now an INTERNALLIB - that is, it is
1656 statically linked into consumers (GDB and variants) in the base
1657 system, and the shared library is no longer installed. The
1658 devel/readline port is available for third party software that
1662 The Itanium architecture (ia64) has been removed from the list of
1663 known architectures. This is the first step in the removal of the
1667 Commit r268115 has added NFSv4.1 server support, merged from
1668 projects/nfsv4.1-server. Since this includes changes to the
1669 internal interfaces between the NFS related modules, a full
1670 build of the kernel and modules will be necessary.
1671 __FreeBSD_version has been bumped.
1674 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1675 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1676 which differs from the behaviour controlled by this knob.)
1679 Maximal length of the serial number in CTL was increased from 16 to
1680 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1681 and ctld, need to be rebuilt to work with a new kernel.
1684 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1685 1 respectively to match the upstream numbers. They were out of
1686 sync because, when they were originally added to FreeBSD, the
1687 upstream versions were not respected. These libraries are private
1688 and not yet built by default, so renumbering them should be a
1689 non-issue. However, unclean source trees will yield broken test
1690 programs once the operator executes "make delete-old-libs" after a
1691 "make installworld".
1693 Additionally, the atf-sh binary was made private by moving it into
1694 /usr/libexec/. Already-built shell test programs will keep the
1695 path to the old binary so they will break after "make delete-old"
1698 If you are using WITH_TESTS=yes (not the default), wipe the object
1699 tree and rebuild from scratch to prevent spurious test failures.
1700 This is only needed once: the misnumbered libraries and misplaced
1701 binaries have been added to OptionalObsoleteFiles.inc so they will
1702 be removed during a clean upgrade.
1705 Clang and llvm have been upgraded to 3.4.1 release.
1708 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1709 be removed to avoid issues in the future (and has been added to
1713 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1714 past, it affected all builds that used the bsd.*.mk files. The old
1715 behavior was a bug, but people may have relied upon it. To get this
1716 behavior back, you can .include /etc/src.conf from /etc/make.conf
1717 (which is still global and isn't changed). This also changes the
1718 behavior of incremental builds inside the tree of individual
1719 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1720 Although this has survived make universe and some upgrade scenarios,
1721 other upgrade scenarios may have broken. At least one form of
1722 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1723 as well... In cases where MAKESYSPATH isn't working with this
1724 setting, you'll need to set it to the full path to your tree.
1726 One side effect of all this cleaning up is that bsd.compiler.mk
1727 is no longer implicitly included by bsd.own.mk. If you wish to
1728 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1732 The lindev device has been removed since /dev/full has been made a
1733 standard device. __FreeBSD_version has been bumped.
1736 The knob WITHOUT_VI was added to the base system, which controls
1737 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1738 in order to reorder files share/termcap and didn't build ex(1) as a
1739 build tool, so building/installing with WITH_VI is highly advised for
1740 build hosts for older releases.
1742 This issue has been fixed in stable/9 and stable/10 in r277022 and
1743 r276991, respectively.
1746 The YES_HESIOD knob has been removed. It has been obsolete for
1747 a decade. Please move to using WITH_HESIOD instead or your builds
1748 will silently lack HESIOD.
1751 The uart(4) driver has been changed with respect to its handling
1752 of the low-level console. Previously the uart(4) driver prevented
1753 any process from changing the baudrate or the CLOCAL and HUPCL
1754 control flags. By removing the restrictions, operators can make
1755 changes to the serial console port without having to reboot.
1756 However, when getty(8) is started on the serial device that is
1757 associated with the low-level console, a misconfigured terminal
1758 line in /etc/ttys will now have a real impact.
1759 Before upgrading the kernel, make sure that /etc/ttys has the
1760 serial console device configured as 3wire without baudrate to
1761 preserve the previous behaviour. E.g:
1762 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1765 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1766 to improve performance. To re-enable it, if needed, run rpcbind
1767 with command line option -W.
1770 Switched back to the GPL dtc compiler due to updates in the upstream
1771 dts files not being supported by the BSDL dtc compiler. You will need
1772 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1773 may result while building dtb files during a kernel build if you fail
1774 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1777 Clang and llvm have been upgraded to 3.4 release.
1780 The nve(4) driver has been removed. Please use the nfe(4) driver
1781 for NVIDIA nForce MCP Ethernet adapters instead.
1784 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1785 This could cause certain C++ applications using shared libraries built
1786 against the previous version of libc++ to crash. The incompatibility
1787 has now been fixed, but any C++ applications or shared libraries built
1788 between r261283 and r261801 should be recompiled.
1791 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1792 capability mode support. Please note that enabling the feature in
1793 kernel is still highly recommended.
1796 OpenSSH is now built with sandbox support, and will use sandbox as
1797 the default privilege separation method. This requires Capsicum
1798 capability mode support in kernel.
1801 The libelf and libdwarf libraries have been updated to newer
1802 versions from upstream. Shared library version numbers for
1803 these two libraries were bumped. Any ports or binaries
1804 requiring these two libraries should be recompiled.
1805 __FreeBSD_version is bumped to 1100006.
1808 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1809 instead of providing an explicit one, this would prevent such
1810 Makefile from providing its own Kyuafile in the future during
1811 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1812 intervention is needed to clean an objdir if you use NO_CLEAN:
1813 # find /usr/obj -name Kyuafile | xargs rm -f
1816 The behavior of gss_pseudo_random() for the krb5 mechanism
1817 has changed, for applications requesting a longer random string
1818 than produced by the underlying enctype's pseudo-random() function.
1819 In particular, the random string produced from a session key of
1820 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1821 be different at the 17th octet and later, after this change.
1822 The counter used in the PRF+ construction is now encoded as a
1823 big-endian integer in accordance with RFC 4402.
1824 __FreeBSD_version is bumped to 1100004.
1827 The WITHOUT_ATF build knob has been removed and its functionality
1828 has been subsumed into the more generic WITHOUT_TESTS. If you were
1829 using the former to disable the build of the ATF libraries, you
1830 should change your settings to use the latter.
1833 The default version of mtree is nmtree which is obtained from
1834 NetBSD. The output is generally the same, but may vary
1835 slightly. If you found you need identical output adding
1836 "-F freebsd9" to the command line should do the trick. For the
1837 time being, the old mtree is available as fmtree.
1840 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1841 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1842 1.1.4_8 and verify bsdyml not linked in, before running "make
1844 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1846 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1849 The stable/10 branch has been created in subversion from head
1856 Avoid using make -j when upgrading. While generally safe, there are
1857 sometimes problems using -j to upgrade. If your upgrade fails with
1858 -j, please try again without -j. From time to time in the past there
1859 have been problems using -j with buildworld and/or installworld. This
1860 is especially true when upgrading between "distant" versions (eg one
1861 that cross a major release boundary or several minor releases, or when
1862 several months have passed on the -current branch).
1864 Sometimes, obscure build problems are the result of environment
1865 poisoning. This can happen because the make utility reads its
1866 environment when searching for values for global variables. To run
1867 your build attempts in an "environmental clean room", prefix all make
1868 commands with 'env -i '. See the env(1) manual page for more details.
1870 When upgrading from one major version to another it is generally best to
1871 upgrade to the latest code in the currently installed branch first, then
1872 do an upgrade to the new branch. This is the best-tested upgrade path,
1873 and has the highest probability of being successful. Please try this
1874 approach if you encounter problems with a major version upgrade. Since
1875 the stable 4.x branch point, one has generally been able to upgrade from
1876 anywhere in the most recent stable branch to head / current (or even the
1877 last couple of stable branches). See the top of this file when there's
1880 When upgrading a live system, having a root shell around before
1881 installing anything can help undo problems. Not having a root shell
1882 around can lead to problems if pam has changed too much from your
1883 starting point to allow continued authentication after the upgrade.
1885 This file should be read as a log of events. When a later event changes
1886 information of a prior event, the prior event should not be deleted.
1887 Instead, a pointer to the entry with the new information should be
1888 placed in the old entry. Readers of this file should also sanity check
1889 older entries before relying on them blindly. Authors of new entries
1890 should write them with this in mind.
1894 When upgrading the boot ZFS pool to a new version, always follow
1897 1.) recompile and reinstall the ZFS boot loader and boot block
1898 (this is part of "make buildworld" and "make installworld")
1900 2.) update the ZFS boot block on your boot drive
1902 The following example updates the ZFS boot block on the first
1903 partition (freebsd-boot) of a GPT partitioned drive ada0:
1904 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1906 Non-boot pools do not need these updates.
1910 If you are updating from a prior version of FreeBSD (even one just
1911 a few days old), you should follow this procedure. It is the most
1912 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1914 make kernel-toolchain
1915 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1916 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1918 To test a kernel once
1919 ---------------------
1920 If you just want to boot a kernel once (because you are not sure
1921 if it works, or if you want to boot a known bad kernel to provide
1922 debugging information) run
1923 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1924 nextboot -k testkernel
1926 To rebuild everything and install it on the current system.
1927 -----------------------------------------------------------
1928 # Note: sometimes if you are running current you gotta do more than
1929 # is listed here if you are upgrading from a really old current.
1931 <make sure you have good level 0 dumps>
1933 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1934 make installkernel KERNCONF=YOUR_KERNEL_HERE
1936 <reboot in single user> [3]
1943 To cross-install current onto a separate partition
1944 --------------------------------------------------
1945 # In this approach we use a separate partition to hold
1946 # current's root, 'usr', and 'var' directories. A partition
1947 # holding "/", "/usr" and "/var" should be about 2GB in
1950 <make sure you have good level 0 dumps>
1953 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1954 <maybe newfs current's root partition>
1955 <mount current's root partition on directory ${CURRENT_ROOT}>
1956 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1957 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1958 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1959 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1960 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1961 <reboot into current>
1962 <do a "native" rebuild/install as described in the previous section>
1963 <maybe install compatibility libraries from ports/misc/compat*>
1967 To upgrade in-place from stable to current
1968 ----------------------------------------------
1969 <make sure you have good level 0 dumps>
1971 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1972 make installkernel KERNCONF=YOUR_KERNEL_HERE
1974 <reboot in single user> [3]
1981 Make sure that you've read the UPDATING file to understand the
1982 tweaks to various things you need. At this point in the life
1983 cycle of current, things change often and you are on your own
1984 to cope. The defaults can also change, so please read ALL of
1985 the UPDATING entries.
1987 Also, if you are tracking -current, you must be subscribed to
1988 freebsd-current@freebsd.org. Make sure that before you update
1989 your sources that you have read and understood all the recent
1990 messages there. If in doubt, please track -stable which has
1991 much fewer pitfalls.
1993 [1] If you have third party modules, such as vmware, you
1994 should disable them at this point so they don't crash your
1997 [3] From the bootblocks, boot -s, and then do
2002 adjkerntz -i # if CMOS is wall time
2003 Also, when doing a major release upgrade, it is required that
2004 you boot into single user mode to do the installworld.
2006 [4] Note: This step is non-optional. Failure to do this step
2007 can result in a significant reduction in the functionality of the
2008 system. Attempting to do it by hand is not recommended and those
2009 that pursue this avenue should read this file carefully, as well
2010 as the archives of freebsd-current and freebsd-hackers mailing lists
2011 for potential gotchas. The -U option is also useful to consider.
2012 See mergemaster(8) for more information.
2014 [5] Usually this step is a no-op. However, from time to time
2015 you may need to do this if you get unknown user in the following
2016 step. It never hurts to do it all the time. You may need to
2017 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2018 install) after the buildworld before this step if you last updated
2019 from current before 20130425 or from -stable before 20130430.
2021 [6] This only deletes old files and directories. Old libraries
2022 can be deleted by "make delete-old-libs", but you have to make
2023 sure that no program is using those libraries anymore.
2025 [8] The new kernel must be able to run existing binaries used by
2026 an installworld. When upgrading across major versions, the new
2027 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2028 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2029 binaries). Failure to do so may leave you with a system that is
2030 hard to boot to recover. A GENERIC kernel will include suitable
2031 compatibility options to run binaries from older branches.
2033 Make sure that you merge any new devices from GENERIC since the
2034 last time you updated your kernel config file.
2036 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2037 "?=" instead of the "=" assignment operator, so that buildworld can
2038 override the CPUTYPE if it needs to.
2040 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2041 not on the command line, or in /etc/make.conf. buildworld will
2042 warn if it is improperly defined.
2045 This file contains a list, in reverse chronological order, of major
2046 breakages in tracking -current. It is not guaranteed to be a complete
2047 list of such breakages, and only contains entries since September 23, 2011.
2048 If you need to see UPDATING entries from before that date, you will need
2049 to fetch an UPDATING file from an older FreeBSD release.
2051 Copyright information:
2053 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2055 Redistribution, publication, translation and use, with or without
2056 modification, in full or in part, in any form or format of this
2057 document are permitted without further permission from the author.
2059 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2060 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2061 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2062 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2063 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2064 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2065 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2066 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2067 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2068 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2069 POSSIBILITY OF SUCH DAMAGE.
2071 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob