1 Updating Information for FreeBSD stable/12 users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
20 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
21 been upgraded to 10.0.0. Please see the 20141231 entry below for
22 information about prerequisites and upgrading, if you are not already
23 using clang 3.5.0 or higher.
26 The root certificates of the Mozilla CA Certificate Store have been
27 imported into the base system and can be managed with the certctl(8)
28 utility. If you have installed the security/ca_root_nss port or package
29 with the ETCSYMLINK option (the default), be advised that there may be
30 differences between those included in the port and those included in
31 base due to differences in nss branch used as well as general update
32 frequency. Note also that certctl(8) cannot manage certs in the
33 format used by the security/ca_root_nss port.
36 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
37 been upgraded to 9.0.1. Please see the 20141231 entry below for
38 information about prerequisites and upgrading, if you are not already
39 using clang 3.5.0 or higher.
42 The nctgpio and wbwd drivers have been moved to the superio bus.
43 If you have one of these drivers in a kernel configuration, then
44 you should add device superio to it. If you use one of these drivers
45 as a module and you compile a custom set of modules, then you should
46 add superio to the set.
49 The tap(4) driver has been folded into tun(4), and the module has been
50 renamed to tuntap. You should update any kld_list="if_tap" or
51 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
52 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
53 module instead, and "device tap" or "device tun" entries in kernel
54 config files to select the tuntap device instead.
57 ntpd no longer by default locks its pages in memory, allowing them
58 to be paged out by the kernel. Use rlimit memlock to restore
59 historic BSD behaviour. For example, add "rlimit memlock 32"
60 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
63 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
64 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
65 been removed from mount_fusefs(8). You can safely remove them from
66 your scripts, because they had no effect.
68 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
69 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
70 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
71 sysctls have been removed. If you felt the need to set any of them to
72 a non-default value, please tell asomers@FreeBSD.org why.
75 The fuse(4) module has been renamed to fusefs(4) for consistency with
76 other filesystems. You should update any kld_load="fuse" entries in
77 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
78 "options FUSE" enties in kernel config files.
81 Default permissions on the /var/account/acct file (and copies of it
82 rotated by periodic daily scripts) are changed from 0644 to 0640
83 because the file contains sensitive information that should not be
84 world-readable. If the /var/account directory must be created by
85 rc.d/accounting, the mode used is now 0750. Admins who use the
86 accounting feature are encouraged to change the mode of an existing
87 /var/account directory to 0750 or 0700.
90 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
91 been upgraded to 8.0.1. Please see the 20141231 entry below for
92 information about prerequisites and upgrading, if you are not already
93 using clang 3.5.0 or higher.
96 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
97 functionality needed for the RETPOLINE option should work properly
98 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
101 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
102 8.0.0. Please see the 20141231 entry below for information about
103 prerequisites and upgrading, if you are not already using clang 3.5.0
107 The RETPOLINE option produces non-functional ifunc-using binaries
108 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
109 Once Clang 8 is merged it may be enabled again.
112 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
113 7.0.1. Please see the 20141231 entry below for information about
114 prerequisites and upgrading, if you are not already using clang 3.5.0
118 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
119 compiled into your custom kernel, add 'device xz' statement to the
123 Iflib is no longer unconditionally compiled into the kernel. Drivers
124 using iflib and statically compiled into the kernel, now require
125 the 'device iflib' config option. For the same drivers loaded as
126 modules on kernels not having 'device iflib', the iflib.ko module
127 is loaded automatically.
130 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
131 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
132 servers that have vfs.nfsd.nfs_privport set will only allow mounts
133 from clients using a reserved port#. Since both the FreeBSD and Linux
134 NFSv4 clients use reserved port#s by default, this should not affect
138 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
139 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
140 it produces broken binaries when ifuncs are in use. Users needing
141 GNU ld should install the binutils port or package.
144 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
145 has been converted to a port (misc/ctm) and will be removed from
146 FreeBSD-13. A depreciation warning will be printed to stderr by
147 the ctm command, but the functionality will remain in base for all
151 The stable/12 branch has been created in subversion from head
155 Ports for the DRM modules have been simplified. Now, amd64 users should
156 just install the drm-kmod port. All others should install
159 Graphics hardware that's newer than about 2010 usually works with
160 drm-kmod. For hardware older than 2013, however, some users will need
161 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
162 than 2008 usually only works in drm-legacy-kmod. The graphics team can
163 only commit to hardware made since 2013 due to the complexity of the
164 market and difficulty to test all the older cards effectively. If you
165 have hardware supported by drm-kmod, you are strongly encouraged to use
166 that as you will get better support.
168 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
169 elsewhere, the drm and drm2 modules will be eliminated from the src base
170 soon (with a limited exception for arm). Please update to the package asap
171 and report any issues to x11@freebsd.org.
173 Generally, anybody using the drm*-kmod packages should add
174 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
175 cross-threading surprises, especially with automatic driver
176 loading from X11 startup. These will become the defaults in 13-current
180 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
181 custom kernel and module loading configuration files must be updated
182 accordingly. Moreover, interfaces previous presented as ixlvN to the
183 system are now exposed as iavfN and network configuration files must
184 be adjusted as necessary.
187 OpenSSL has been updated to version 1.1.1. This update included
188 additional various API changes througout the base system. It is
189 important to rebuild third-party software after upgrading. The value
190 of __FreeBSD_version has been bumped accordingly.
193 The legacy DRM modules and drivers have now been added to the loader's
194 module blacklist, in favor of loading them with kld_list in rc.conf(5).
195 The module blacklist may be overridden with the loader.conf(5)
196 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
200 The cam(4) based nda(4) driver will be used over nvd(4) by default on
201 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
202 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
203 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
207 Reproducible build mode is now on by default, in preparation for
208 FreeBSD 12.0. This eliminates build metadata such as the user,
209 host, and time from the kernel (and uname), unless the working tree
210 corresponds to a modified checkout from a version control system.
211 The previous behavior can be obtained by setting the /etc/src.conf
212 knob WITHOUT_REPRODUCIBLE_BUILD.
215 The Yarrow CSPRNG has been removed from the kernel as it has not been
216 supported by its designers since at least 2003. Fortuna has been the
217 default since FreeBSD-11.
220 devctl freeze/thaw have gone into the tree, the rc scripts have been
221 updated to use them and devmatch has been changed. You should update
222 kernel, userland and rc scripts all at the same time.
225 The default interpreter has been switched from 4th to Lua.
226 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
227 interpreter. If you have custom FORTH code you will need to set
228 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
229 src.conf for the build. This will create default hard links between
230 loader and loader_4th instead of loader and loader_lua, the new default.
231 If you are using UEFI it will create the proper hard link to loader.efi.
233 bhyve uses userboot.so. It remains 4th-only until some issues are solved
234 regarding coexisting with multiple versions of FreeBSD are resolved.
237 ls(1) now respects the COLORTERM environment variable used in other
238 systems and software to indicate that a colored terminal is both
239 supported and desired. If ls(1) is suddenly emitting colors, they may
240 be disabled again by either removing the unwanted COLORTERM from your
241 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
242 may not be observed in a future release.
245 The default pager for most commands has been changed to "less". To
246 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
250 The jedec_ts(4) driver has been removed. A superset of its functionality
251 is available in the jedec_dimm(4) driver, and the manpage for that
252 driver includes migration instructions. If you have "device jedec_ts"
253 in your kernel configuration file, it must be removed.
256 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
257 This should have no effect if the kernel is booted via BIOS/legacy boot.
258 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
259 has a buggy firmware that prevents a successful boot due to use of
263 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
264 support has been removed from the tree. These ports were
265 obsolete and/or known to be broken for many years.
268 loader.efi has been augmented to participate more fully in the
269 UEFI boot manager protocol. loader.efi will now look at the
270 BootXXXX environment variable to determine if a specific kernel
271 or root partition was specified. XXXX is derived from BootCurrent.
272 efibootmgr(8) manages these standard UEFI variables.
275 zfsloader's functionality has now been folded into loader.
276 zfsloader is no longer necessary once you've updated your
277 boot blocks. For a transition period, we will install a
278 hardlink for zfsloader to loader to allow a smooth transition
279 until the boot blocks can be updated (hard link because old
280 zfs boot blocks don't understand symlinks).
283 ARM64 now have efifb support, if you want to have serial console
284 on your arm64 board when an screen is connected and the bootloader
285 setup a frambuffer for us to use, just add :
289 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
290 an screen connected as the firmware will setup a framebuffer are that
291 u-boot will expose as an EFI framebuffer.
294 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
295 or take steps to update /etc/passwd before doing installworld on
296 existing systems. Do not skip the "mergemaster -Fp" step before
297 installworld, as described in the update procedures near the bottom
298 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
299 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
300 the ntp config file contain options that change file/dir locations.
301 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
302 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
303 taking steps to ensure that all required files/dirs are accessible
307 Big endian arm support has been removed.
310 The static environment setup in kernel configs is no longer mutually
311 exclusive with the loader(8) environment by default. In order to
312 restore the previous default behavior of disabling the loader(8)
313 environment if a static environment is present, you must specify
314 loader_env.disabled=1 in the static environment.
317 The ABI of syscalls used by management tools like sockstat and
318 netstat has been broken to allow 32-bit binaries to work on
319 64-bit kernels without modification. These programs will need
320 to match the kernel in order to function. External programs may
321 require minor modifications to accommodate a change of type in
322 structures from pointers to 64-bit virtual addresses.
325 On i386 and amd64 atomics are now inlined. Out of tree modules using
326 atomics will need to be rebuilt.
329 The '%I' format in the kern.corefile sysctl limits the number of
330 core files that a process can generate to the number stored in the
331 debug.ncores sysctl. The '%I' format is replaced by the single digit
332 index. Previously, if all indexes were taken the kernel would overwrite
333 only a core file with the highest index in a filename.
334 Currently the system will create a new core file if there is a free
335 index or if all slots are taken it will overwrite the oldest one.
338 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
339 6.0.1. Please see the 20141231 entry below for information about
340 prerequisites and upgrading, if you are not already using clang 3.5.0
344 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
345 needed to be changed to work with it. This change was made with r335763
346 and requires a mergemaster / etcupdate / etc to update the installed file.
349 r334930 changed the interface between the NFS modules, so they all
350 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
353 As of r334391 lld is the default amd64 system linker; it is installed
354 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
358 The kernel / userland interface for devinfo changed, so you'll
359 need a new kernel and userland as a pair for it to work (rebuilding
360 lib/libdevinfo is all that's required). devinfo and devmatch will
361 not work, but everything else will when there's a mismatch.
364 The on-disk format for hwpmc callchain records has changed to include
365 threadid corresponding to a given record. This changes the field offsets
366 and thus requires that libpmcstat be rebuilt before using a kernel
370 The vxge(4) driver has been removed. This driver was introduced into
371 HEAD one week before the Exar left the Ethernet market and is not
372 known to be used. If you have device vxge in your kernel config file
376 The amd64 kernel now requires a ld that supports ifunc to produce a
377 working kernel, either lld or a newer binutils. lld is built by default
378 on amd64, and the 'buildkernel' target uses it automatically. However,
379 it is not the default linker, so building the kernel the traditional
380 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
381 binutils port/package). lld will soon be default, and this requirement
384 NOTE: As of r334391 lld is the default system linker on amd64, and no
385 workaround is necessary.
388 The nxge(4) driver has been removed. This driver was for PCI-X 10g
389 cards made by s2io/Neterion. The company was aquired by Exar and
390 no longer sells or supports Ethernet products. If you have device
391 nxge in your kernel config file it must be removed.
394 The tz database (tzdb) has been updated to 2018e. This version more
395 correctly models time stamps in time zones with negative DST such as
396 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
397 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
398 time zone abbreviations and the tm_isdst flag.
401 The ixgb(4) driver has been removed. This driver was for an early and
402 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
403 quickly shifted to the long lived ixgbe family. If you have device
404 ixgb in your kernel config file it must be removed.
407 The lmc(4) driver has been removed. This was a WAN interface
408 card that was already reportedly rare in 2003, and had an ambiguous
409 license. If you have device lmc in your kernel config file it must
413 Support for Arcnet networks has been removed. If you have device
414 arcnet or device cm in your kernel config file they must be
418 Support for FDDI networks has been removed. If you have device
419 fddi or device fpa in your kernel config file they must be
423 In addition to supporting RFC 3164 formatted messages, the
424 syslogd(8) service is now capable of parsing RFC 5424 formatted
425 log messages. The main benefit of using RFC 5424 is that clients
426 may now send log messages with timestamps containing year numbers,
427 microseconds and time zone offsets.
429 Similarly, the syslog(3) C library function has been altered to
430 send RFC 5424 formatted messages to the local system logging
431 daemon. On systems using syslogd(8), this change should have no
432 negative impact, as long as syslogd(8) and the C library are
433 updated at the same time. On systems using a different system
434 logging daemon, it may be necessary to make configuration
435 adjustments, depending on the software used.
437 When using syslog-ng, add the 'syslog-protocol' flag to local
438 input sources to enable parsing of RFC 5424 formatted messages:
441 unix-dgram("/var/run/log" flags(syslog-protocol));
444 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
445 of the 'imuxsock' module to let messages be processed by the
446 regular RFC 3164/5424 parsing pipeline:
448 module(load="imuxsock" SysSock.UseSpecialParser="off")
450 Do note that these changes only affect communication between local
451 applications and syslogd(8). The format that syslogd(8) uses to
452 store messages on disk or forward messages to other systems
453 remains unchanged. syslogd(8) still uses RFC 3164 for these
454 purposes. Options to customize this behaviour will be added in the
455 future. Utilities that process log files stored in /var/log are
456 thus expected to continue to function as before.
458 __FreeBSD_version has been incremented to 1200061 to denote this
462 Support for token ring networks has been removed. If you
463 have "device token" in your kernel config you should remove
464 it. No device drivers supported token ring.
467 makefs was modified to be able to tag ISO9660 El Torito boot catalog
468 entries as EFI instead of overloading the i386 tag as done previously.
469 The amd64 mkisoimages.sh script used to build amd64 ISO images for
470 release was updated to use this. This may mean that makefs must be
471 updated before "make cdrom" can be run in the release directory. This
472 should be as simple as:
474 $ cd $SRCDIR/usr.sbin/makefs
475 $ make depend all install
478 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
479 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
480 Co-existance for the transition period will come shortly. Booting is a
481 complex environment and test coverage for Lua-enabled loaders has been
482 thin, so it would be prudent to assume it might not work and make
483 provisions for backup boot methods.
486 devmatch functionality has been turned on in devd. It will automatically
487 load drivers for unattached devices. This may cause unexpected drivers to
488 be loaded. Please report any problems to current@ and imp@freebsd.org.
491 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
492 6.0.0. Please see the 20141231 entry below for information about
493 prerequisites and upgrading, if you are not already using clang 3.5.0
497 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
498 This means it is used to link the kernel and userland libraries and
499 executables, but is not yet installed as /usr/bin/ld by default.
501 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
502 WITHOUT_LLD_BOOTSTRAP=yes
505 On i386, pmtimer has been removed. Its functionality has been folded
506 into apm. It was a no-op on ACPI in current for a while now (but was still
507 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
508 from kernel config files.
511 The use of RSS hash from the network card aka flowid has been
512 disabled by default for lagg(4) as it's currently incompatible with
513 the lacp and loadbalance protocols.
515 This can be re-enabled by setting the following in loader.conf:
516 net.link.lagg.default_use_flowid="1"
519 The SW_WATCHDOG option is no longer necessary to enable the
520 hardclock-based software watchdog if no hardware watchdog is
521 configured. As before, SW_WATCHDOG will cause the software
522 watchdog to be enabled even if a hardware watchdog is configured.
525 r326887 fixes the issue described in the 20171214 UPDATING entry.
526 r326888 flips the switch back to building GELI support always.
529 r362593 broke ZFS + GELI support for reasons unknown. However,
530 it also broke ZFS support generally, so GELI has been turned off
531 by default as the lesser evil in r326857. If you boot off ZFS and/or
532 GELI, it might not be a good time to update.
535 PowerPC users must update loader(8) by rebuilding world before
536 installing a new kernel, as the protocol connecting them has
537 changed. Without the update, loader metadata will not be passed
538 successfully to the kernel and users will have to enter their
539 root partition at the kernel mountroot prompt to continue booting.
540 Newer versions of loader can boot old kernels without issue.
543 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
544 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
545 to WITH/OUT_LOADER_GELI.
548 The naive and non-compliant support of posix_fallocate(2) in ZFS
549 has been removed as of r325320. The system call now returns EINVAL
550 when used on a ZFS file. Although the new behavior complies with the
551 standard, some consumers are not prepared to cope with it.
552 One known victim is lld prior to r325420.
555 Building in a FreeBSD src checkout will automatically create object
556 directories now rather than store files in the current directory if
557 'make obj' was not ran. Calling 'make obj' is no longer necessary.
558 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
559 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
563 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
564 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
565 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
566 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
567 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
568 The UNIFIED_OBJDIR option is a transitional feature that will be
569 removed for 12.0 release; please migrate to the new format for any
570 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
571 than hardcoding paths.
574 The native-xtools target no longer installs the files by default to the
575 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
576 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
579 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
580 options are changing from controlling the build if defined / undefined
581 to controlling the build with explicit 'yes' or 'no' values. They will
582 shift to WITH/WITHOUT options to match other options in the system.
585 libstand has turned into a private library for sys/boot use only.
586 It is no longer supported as a public interface outside of sys/boot.
589 The arm port has split armv6 into armv6 and armv7. armv7 is now
590 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
591 and are running a kernel from before r324363, you will need to add
592 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
595 When building multiple kernels using KERNCONF, non-existent KERNCONF
596 files will produce an error and buildkernel will fail. Previously
597 missing KERNCONF files silently failed giving no indication as to
598 why, only to subsequently discover during installkernel that the
599 desired kernel was never built in the first place.
602 The default serial number format for CTL LUNs has changed. This will
603 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
604 or iSCSI clients care about their LUNs' serial numbers. Users who
605 require serial number stability should hardcode serial numbers in
609 For 32-bit arm compiled for hard-float support, soft-floating point
610 binaries now always get their shared libraries from
611 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
612 /usr/libsoft also existed). Only users with a hard-float ld.so, but
613 soft-float everything else should be affected.
616 The geli password typed at boot is now hidden. To restore the previous
617 behavior, see geli(8) for configuration options.
620 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
621 sysctl values. Minor nit, but requires a rebuild of both world/kernel
625 "make check" behavior (made in ^/head@r295380) has been changed to
626 execute from a limited sandbox, as opposed to executing from
630 - The "beforecheck" and "aftercheck" targets are now specified.
631 - ${CHECKDIR} (added in commit noted above) has been removed.
632 - Legacy behavior can be enabled by setting
633 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
635 If the limited sandbox mode is enabled, "make check" will execute
636 "make distribution", then install, execute the tests, and clean up the
637 sandbox if successful.
639 The "make distribution" and "make install" targets are typically run as
640 root to set appropriate permissions and ownership at installation time.
641 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
642 environment if executing "make check" with limited sandbox mode using
643 an unprivileged user.
646 Since the switch to GPT disk labels, fsck for UFS/FFS has been
647 unable to automatically find alternate superblocks. As of r322297,
648 the information needed to find alternate superblocks has been
649 moved to the end of the area reserved for the boot block.
650 Filesystems created with a newfs of this vintage or later
651 will create the recovery information. If you have a filesystem
652 created prior to this change and wish to have a recovery block
653 created for your filesystem, you can do so by running fsck in
654 foreground mode (i.e., do not use the -p or -y options). As it
655 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
656 to which you should answer yes.
659 As of r321665, an NFSv4 server configuration that services
660 Kerberos mounts or clients that do not support the uid/gid in
661 owner/owner_group string capability, must explicitly enable
662 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
663 machine's /etc/rc.conf file.
666 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
667 Please see the 20141231 entry below for information about prerequisites
668 and upgrading, if you are not already using clang 3.5.0 or higher.
671 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
672 r-commands (rlogin, rsh, etc.) to be built with the base system.
675 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
676 a very major ABI incompatible change, so users of FreeBSD/powerpc must
677 be careful when performing source upgrades. It is best to run
678 'make installworld' from an alternate root system, either a live
679 CD/memory stick, or a temporary root partition. Additionally, all ports
680 must be recompiled. powerpc64 is largely unaffected, except in the case
681 of 32-bit compatibility. All 32-bit binaries will be affected.
684 Forward compatibility for the "ino64" project have been committed. This
685 will allow most new binaries to run on older kernels in a limited
686 fashion. This prevents many of the common foot-shooting actions in the
687 upgrade as well as the limited ability to roll back the kernel across
688 the ino64 upgrade. Complicated use cases may not work properly, though
689 enough simpler ones work to allow recovery in most situations.
692 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
693 if you require the GPL compiler.
696 The internal ABI used for communication between the NFS kernel modules
697 was changed by r320085, so __FreeBSD_version was bumped to
698 ensure all the NFS related modules are updated together.
701 The ABI of struct event was changed by extending the data
702 member to 64bit and adding ext fields. For upgrade, same
703 precautions as for the entry 20170523 "ino64" must be
707 The GNU roff toolchain has been removed from base. To render manpages
708 which are not supported by mandoc(1), man(1) can fallback on GNU roff
709 from ports (and recommends to install it).
710 To render roff(7) documents, consider using GNU roff from ports or the
711 heirloom doctools roff toolchain from ports via pkg install groff or
712 via pkg install heirloom-doctools.
715 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
716 smaller runtime footprint builds. This is useful for embedded systems
717 which only require one chipset support.
719 If you load it as a module, make sure this is in /boot/loader.conf:
723 This will load the HAL, all chip/RF backends and if_ath_pci.
724 If you have if_ath_pci in /boot/loader.conf, ensure it is after
725 if_ath or it will not load any HAL chipset support.
727 If you want to selectively load things (eg on ye cheape ARM/MIPS
728 platforms where RAM is at a premium) you should:
731 * load the chip modules in question
732 * load ath_rate, ath_dfs
734 * load if_ath_pci and/or if_ath_ahb depending upon your particular
735 bus bind type - this is where probe/attach is done.
737 For further comments/feedback, poke adrian@ .
740 The "ino64" 64-bit inode project has been committed, which extends
741 a number of types to 64 bits. Upgrading in place requires care and
742 adherence to the documented upgrade procedure.
744 If using a custom kernel configuration ensure that the
745 COMPAT_FREEBSD11 option is included (as during the upgrade the
746 system will be running the ino64 kernel with the existing world).
748 For the safest in-place upgrade begin by removing previous build
749 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
750 full procedure documented below under the heading "To rebuild
751 everything and install it on the current system." Specifically,
752 a reboot is required after installing the new kernel before
756 The NATM framework including the en(4), fatm(4), hatm(4), and
757 patm(4) devices has been removed. Consumers should plan a
758 migration before the end-of-life date for FreeBSD 11.
761 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
762 diff has not been implemented, if those are needed a newer version of
763 GNU diff is available via the diffutils package under the gdiff name.
766 As of r316810 for ipfilter, keep frags is no longer assumed when
767 keep state is specified in a rule. r316810 aligns ipfilter with
768 documentation in man pages separating keep frags from keep state.
769 This allows keep state to be specified without forcing keep frags
770 and allows keep frags to be specified independently of keep state.
771 To maintain previous behaviour, also specify keep frags with
772 keep state (as documented in ipf.conf.5).
775 arm64 builds now use the base system LLD 4.0.0 linker by default,
776 instead of requiring that the aarch64-binutils port or package be
777 installed. To continue using aarch64-binutils, set
778 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
781 The UDP optimization in entry 20160818 that added the sysctl
782 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
783 packets will no longer be treated as L3 broadcast packets.
786 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
787 use any explicitly assigned loopback address available in the jail
788 instead of using the first assigned address of the jail.
791 The ctl.ko module no longer implements the iSCSI target frontend:
792 cfiscsi.ko does instead.
794 If building cfiscsi.ko as a kernel module, the module can be loaded
795 via one of the following methods:
796 - `cfiscsi_load="YES"` in loader.conf(5).
797 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
798 - ctladm(8)/ctld(8), when compiled with iSCSI support
799 (`WITH_ISCSI=yes` in src.conf(5))
801 Please see cfiscsi(4) for more details.
804 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
805 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
806 same source (previously, the dependency of mmcsd.ko on mmc.ko was
807 missing, but mmcsd.ko now will refuse to load if it is incompatible
811 The syntax of ipfw(8) named states was changed to avoid ambiguity.
812 If you have used named states in the firewall rules, you need to modify
813 them after installworld and before rebooting. Now named states must
814 be prefixed with colon.
817 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
818 removed as the userland we provide cannot use them. The KMS version
819 (sys/dev/drm2) supports the same hardware.
822 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
823 Please see the 20141231 entry below for information about prerequisites
824 and upgrading, if you are not already using clang 3.5.0 or higher.
827 The code that provides support for ZFS .zfs/ directory functionality
828 has been reimplemented. It's not possible now to create a snapshot
829 by mkdir under .zfs/snapshot/. That should be the only user visible
833 EISA bus support has been removed. The WITH_EISA option is no longer
837 MCA bus support has been removed.
840 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
841 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
844 The EM_MULTIQUEUE kernel configuration option is deprecated now that
845 the em(4) driver conforms to iflib specifications.
848 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
849 IFLIB. If you have a custom kernel configuration that excludes em(4)
850 but you use igb(4), you need to re-add em(4) to your custom configuration.
853 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
854 Please see the 20141231 entry below for information about prerequisites
855 and upgrading, if you are not already using clang 3.5.0 or higher.
858 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
859 Please see the 20141231 entry below for information about prerequisites
860 and upgrading, if you are not already using clang 3.5.0 or higher.
863 The layout of the pmap structure has changed for powerpc to put the pmap
864 statistics at the front for all CPU variations. libkvm(3) and all tools
865 that link against it need to be recompiled.
868 isl(4) and cyapa(4) drivers now require a new driver,
869 chromebook_platform(4), to work properly on Chromebook-class hardware.
870 On other types of hardware the drivers may need to be configured using
871 device hints. Please see the corresponding manual pages for details.
874 The urtwn(4) driver was merged into rtwn(4) and now consists of
875 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
877 Also, firmware for RTL8188CE was renamed due to possible name
878 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
881 GNU rcs has been removed from base. It is available as packages:
882 - rcs: Latest GPLv3 GNU rcs version.
883 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
887 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
888 modules now requires that the kernel configuration contain the
889 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
892 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
893 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
896 Relocatable object files with the extension of .So have been renamed
897 to use an extension of .pico instead. The purpose of this change is
898 to avoid a name clash with shared libraries on case-insensitive file
899 systems. On those file systems, foo.So is the same file as foo.so.
902 GNU rcs has been turned off by default. It can (temporarily) be built
903 again by adding WITH_RCS knob in src.conf.
904 Otherwise, GNU rcs is available from packages:
905 - rcs: Latest GPLv3 GNU rcs version.
906 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
909 The backup_uses_rcs functionality has been removed from rc.subr.
912 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
913 two separate components, QUEUE_MACRO_DEBUG_TRACE and
914 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
915 QUEUE_MACRO_DEBUG behavior.
918 r304787 changed some ioctl interfaces between the iSCSI userspace
919 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
920 rebuilt to work with new kernels. __FreeBSD_version has been bumped
924 The UDP receive code has been updated to only treat incoming UDP
925 packets that were addressed to an L2 broadcast address as L3
926 broadcast packets. It is not expected that this will affect any
927 standards-conforming UDP application. The new behaviour can be
928 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
932 Remove the openbsd_poll system call.
933 __FreeBSD_version has been bumped because of this.
936 The stable/11 branch has been created from head@r302406.
939 The libc stub for the pipe(2) system call has been replaced with
940 a wrapper that calls the pipe2(2) system call and the pipe(2)
941 system call is now only implemented by the kernels that include
942 "options COMPAT_FREEBSD10" in their config file (this is the
943 default). Users should ensure that this option is enabled in
944 their kernel or upgrade userspace to r302092 before upgrading their
948 CAM will now strip leading spaces from SCSI disks' serial numbers.
949 This will affect users who create UFS filesystems on SCSI disks using
950 those disk's diskid device nodes. For example, if /etc/fstab
951 previously contained a line like
952 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
953 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
954 transforms like gmirror may also be affected. ZFS users should
958 The bitstring(3) API has been updated with new functionality and
959 improved performance. But it is binary-incompatible with the old API.
960 Objects built with the new headers may not be linked against objects
961 built with the old headers.
964 The brk and sbrk functions have been removed from libc on arm64.
965 Binutils from ports has been updated to not link to these
966 functions and should be updated to the latest version before
967 installing a new libc.
970 The armv6 port now defaults to hard float ABI. Limited support
971 for running both hardfloat and soft float on the same system
972 is available using the libraries installed with -DWITH_LIBSOFT.
973 This has only been tested as an upgrade path for installworld
974 and packages may fail or need manual intervention to run. New
975 packages will be needed.
977 To update an existing self-hosted armv6hf system, you must add
978 TARGET_ARCH=armv6 on the make command line for both the build
979 and the install steps.
982 Kernel modules compiled outside of a kernel build now default to
983 installing to /boot/modules instead of /boot/kernel. Many kernel
984 modules built this way (such as those in ports) already overrode
985 KMODDIR explicitly to install into /boot/modules. However,
986 manually building and installing a module from /sys/modules will
987 now install to /boot/modules instead of /boot/kernel.
990 The CAM I/O scheduler has been committed to the kernel. There should be
991 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
992 list of known rogues that claim support for this but actually corrupt
993 data is believed to be complete, be on the lookout for data
994 corruption. The known rogue list is believed to be complete:
996 o Crucial MX100, M550 drives with MU01 firmware.
997 o Micron M510 and M550 drives with MU01 firmware.
998 o Micron M500 prior to MU07 firmware
999 o Samsung 830, 840, and 850 all firmwares
1000 o FCCT M500 all firmwares
1002 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1003 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1004 updated firmware. Black listed drives will work correctly because these
1005 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1006 this list is the same as found in Linux, it's believed there are no
1007 other rogues in the market place. All other models from the above
1010 To be safe, if you are at all concerned, you can quirk each of your
1011 drives to prevent NCQ from being sent by setting:
1012 kern.cam.ada.X.quirks="0x2"
1013 in loader.conf. If the drive requires the 4k sector quirk, set the
1014 quirks entry to 0x3.
1017 The FAST_DEPEND build option has been removed and its functionality is
1018 now the one true way. The old mkdep(1) style of 'make depend' has
1019 been removed. See 20160311 for further details.
1022 Resource range types have grown from unsigned long to uintmax_t. All
1023 drivers, and anything using libdevinfo, need to be recompiled.
1026 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1027 builds. It no longer runs mkdep(1) during 'make depend', and the
1028 'make depend' stage can safely be skipped now as it is auto ran
1029 when building 'make all' and will generate all SRCS and DPSRCS before
1030 building anything else. Dependencies are gathered at compile time with
1031 -MF flags kept in separate .depend files per object file. Users should
1032 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1033 stale .depend files.
1036 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1037 kernel modules. Therefore, if you load any kernel modules at boot time,
1038 please install the boot loaders after you install the kernel, but before
1042 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1043 make installkernel KERNCONF=YOUR_KERNEL_HERE
1044 make -C sys/boot install
1045 <reboot in single user>
1047 Then follow the usual steps, described in the General Notes section,
1051 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1052 see the 20141231 entry below for information about prerequisites and
1053 upgrading, if you are not already using clang 3.5.0 or higher.
1056 The AIO subsystem is now a standard part of the kernel. The
1057 VFS_AIO kernel option and aio.ko kernel module have been removed.
1058 Due to stability concerns, asynchronous I/O requests are only
1059 permitted on sockets and raw disks by default. To enable
1060 asynchronous I/O requests on all file types, set the
1061 vfs.aio.enable_unsafe sysctl to a non-zero value.
1064 The ELF object manipulation tool objcopy is now provided by the
1065 ELF Tool Chain project rather than by GNU binutils. It should be a
1066 drop-in replacement, with the addition of arm64 support. The
1067 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1068 to obtain the GNU version if necessary.
1071 Building ZFS pools on top of zvols is prohibited by default. That
1072 feature has never worked safely; it's always been prone to deadlocks.
1073 Using a zvol as the backing store for a VM guest's virtual disk will
1074 still work, even if the guest is using ZFS. Legacy behavior can be
1075 restored by setting vfs.zfs.vol.recursive=1.
1078 The NONE and HPN patches has been removed from OpenSSH. They are
1079 still available in the security/openssh-portable port.
1082 With the addition of ypldap(8), a new _ypldap user is now required
1083 during installworld. "mergemaster -p" can be used to add the user
1084 prior to installworld, as documented in the handbook.
1087 The tftp loader (pxeboot) now uses the option root-path directive. As a
1088 consequence it no longer looks for a pxeboot.4th file on the tftp
1089 server. Instead it uses the regular /boot infrastructure as with the
1093 The code to start recording plug and play data into the modules has
1094 been committed. While the old tools will properly build a new kernel,
1095 a number of warnings about "unknown metadata record 4" will be produced
1096 for an older kldxref. To avoid such warnings, make sure to rebuild
1097 the kernel toolchain (or world). Make sure that you have r292078 or
1098 later when trying to build 292077 or later before rebuilding.
1101 Debug data files are now built by default with 'make buildworld' and
1102 installed with 'make installworld'. This facilitates debugging but
1103 requires more disk space both during the build and for the installed
1104 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1108 r291527 changed the internal interface between the nfsd.ko and
1109 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1110 __FreeBSD_version has been bumped because of this.
1113 Add support for unicode collation strings leads to a change of
1114 order of files listed by ls(1) for example. To get back to the old
1115 behaviour, set LC_COLLATE environment variable to "C".
1117 Databases administrators will need to reindex their databases given
1118 collation results will be different.
1120 Due to a bug in install(1) it is recommended to remove the ancient
1121 locales before running make installworld.
1123 rm -rf /usr/share/locale/*
1126 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1127 libcrypto.so.7 or libssl.so.7 must be recompiled.
1130 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1131 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1132 should be replaced with isp_2400 and isp_2500 modules respectively.
1135 The build previously allowed using 'make -n' to not recurse into
1136 sub-directories while showing what commands would be executed, and
1137 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1138 and 'make -N' will not.
1141 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1142 and etcupdate will now use this file. A custom sendmail.cf is now
1143 updated via this mechanism rather than via installworld. If you had
1144 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1145 want to remove the exclusion or change it to "always install".
1146 /etc/mail/sendmail.cf is now managed the same way regardless of
1147 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1148 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1151 Compatibility shims for legacy ATA device names have been removed.
1152 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1153 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1154 environment variables, /dev/ad* and /dev/ar* symbolic links.
1157 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1158 Please see the 20141231 entry below for information about prerequisites
1159 and upgrading, if you are not already using clang 3.5.0 or higher.
1162 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1163 and renamed from .symbols to .debug. This reduces the size requirements
1164 on the boot partition or file system and provides consistency with
1165 userland debug files.
1167 When using the supported kernel installation method the
1168 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1169 as is done with /boot/kernel.
1171 Developers wishing to maintain the historical behavior of installing
1172 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1175 The wireless drivers had undergone changes that remove the 'parent
1176 interface' from the ifconfig -l output. The rc.d network scripts
1177 used to check presence of a parent interface in the list, so old
1178 scripts would fail to start wireless networking. Thus, etcupdate(3)
1179 or mergemaster(8) run is required after kernel update, to update your
1180 rc.d scripts in /etc.
1183 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1184 These configurations are now automatically interpreted as
1185 'scrub fragment reassemble'.
1188 Kernel-loadable modules for the random(4) device are back. To use
1189 them, the kernel must have
1192 options RANDOM_LOADABLE
1194 kldload(8) can then be used to load random_fortuna.ko
1195 or random_yarrow.ko. Please note that due to the indirect
1196 function calls that the loadable modules need to provide,
1197 the build-in variants will be slightly more efficient.
1199 The random(4) kernel option RANDOM_DUMMY has been retired due to
1200 unpopularity. It was not all that useful anyway.
1203 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1204 Control over building the ELF Tool Chain tools is now provided by
1205 the WITHOUT_TOOLCHAIN knob.
1208 The polarity of Pulse Per Second (PPS) capture events with the
1209 uart(4) driver has been corrected. Prior to this change the PPS
1210 "assert" event corresponded to the trailing edge of a positive PPS
1211 pulse and the "clear" event was the leading edge of the next pulse.
1213 As the width of a PPS pulse in a typical GPS receiver is on the
1214 order of 1 millisecond, most users will not notice any significant
1215 difference with this change.
1217 Anyone who has compensated for the historical polarity reversal by
1218 configuring a negative offset equal to the pulse width will need to
1219 remove that workaround.
1222 The default group assigned to /dev/dri entries has been changed
1223 from 'wheel' to 'video' with the id of '44'. If you want to have
1224 access to the dri devices please add yourself to the video group
1227 # pw groupmod video -m $USER
1230 The menu.rc and loader.rc files will now be replaced during
1231 upgrades. Please migrate local changes to menu.rc.local and
1232 loader.rc.local instead.
1235 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1236 strings and strip have been removed. The src.conf(5) knob
1237 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1240 As ZFS requires more kernel stack pages than is the default on some
1241 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1242 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1244 Please consider using 'options KSTACK_PAGES=X' where X is greater
1245 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1248 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1249 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1250 default, i.e., they will not contain "::". For example, instead
1251 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1252 to have a more specific match, such as different map entries for
1253 IPv6:0:0 vs IPv6:0. This change requires that configuration
1254 data (including maps, files, classes, custom ruleset, etc.) must
1255 use the same format, so make certain such configuration data is
1256 upgrading. As a very simple check search for patterns like
1257 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1258 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1259 the cf option UseCompressedIPv6Addresses.
1262 The default kernel entropy-processing algorithm is now
1263 Fortuna, replacing Yarrow.
1265 Assuming you have 'device random' in your kernel config
1266 file, the configurations allow a kernel option to override
1267 this default. You may choose *ONE* of:
1269 options RANDOM_YARROW # Legacy /dev/random algorithm.
1270 options RANDOM_DUMMY # Blocking-only driver.
1272 If you have neither, you get Fortuna. For most people,
1273 read no further, Fortuna will give a /dev/random that works
1274 like it always used to, and the difference will be irrelevant.
1276 If you remove 'device random', you get *NO* kernel-processed
1277 entropy at all. This may be acceptable to folks building
1278 embedded systems, but has complications. Carry on reading,
1279 and it is assumed you know what you need.
1281 *PLEASE* read random(4) and random(9) if you are in the
1282 habit of tweaking kernel configs, and/or if you are a member
1283 of the embedded community, wanting specific and not-usual
1284 behaviour from your security subsystems.
1286 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1287 random', you will NOT have a functioning /dev/random, and
1288 many cryptographic features will not work, including SSH.
1289 You may also find strange behaviour from the random(3) set
1290 of library functions, in particular sranddev(3), srandomdev(3)
1291 and arc4random(3). The reason for this is that the KERN_ARND
1292 sysctl only returns entropy if it thinks it has some to
1293 share, and with RANDOM_DUMMY or no 'device random' this
1297 An additional fix for the issue described in the 20150614 sendmail
1298 entry below has been committed in revision 284717.
1301 FreeBSD's old make (fmake) has been removed from the system. It is
1302 available as the devel/fmake port or via pkg install fmake.
1305 The fix for the issue described in the 20150614 sendmail entry
1306 below has been committed in revision 284436. The work
1307 around described in that entry is no longer needed unless the
1308 default setting is overridden by a confDH_PARAMETERS configuration
1309 setting of '5' or pointing to a 512 bit DH parameter file.
1312 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1313 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1314 and devel/kyua to version 0.20+ and adjust any calling code to work
1315 with Kyuafile and kyua.
1318 The import of openssl to address the FreeBSD-SA-15:10.openssl
1319 security advisory includes a change which rejects handshakes
1320 with DH parameters below 768 bits. sendmail releases prior
1321 to 8.15.2 (not yet released), defaulted to a 512 bit
1322 DH parameter setting for client connections. To work around
1323 this interoperability, sendmail can be configured to use a
1324 2048 bit DH parameter by:
1326 1. Edit /etc/mail/`hostname`.mc
1327 2. If a setting for confDH_PARAMETERS does not exist or
1328 exists and is set to a string beginning with '5',
1329 replace it with '2'.
1330 3. If a setting for confDH_PARAMETERS exists and is set to
1331 a file path, create a new file with:
1332 openssl dhparam -out /path/to/file 2048
1333 4. Rebuild the .cf file:
1334 cd /etc/mail/; make; make install
1335 5. Restart sendmail:
1336 cd /etc/mail/; make restart
1338 A sendmail patch is coming, at which time this file will be
1342 Generation of legacy formatted entries have been disabled by default
1343 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1344 entries were converted to use the new format by default when the new,
1345 machine independent format have been added and supported since FreeBSD
1348 Please see the pwd_mkdb(8) manual page for further details.
1351 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1352 20141231 entry below for information about prerequisites and upgrading,
1353 if you are not already using 3.5.0 or higher.
1356 TI platform code switched to using vendor DTS files and this update
1357 may break existing systems running on Beaglebone, Beaglebone Black,
1360 - dtb files should be regenerated/reinstalled. Filenames are the
1361 same but content is different now
1362 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1363 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1364 addressing scheme is now pin 25 on /dev/gpioc3.
1365 - Pandaboard: /etc/ttys should be updated, serial console device is
1366 now /dev/ttyu2, not /dev/ttyu0
1369 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1370 If you need the GNU extension from groff soelim(1), install groff
1371 from package: pkg install groff, or via ports: textproc/groff.
1374 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1375 defined in symlink(7); previously symlinks were silently ignored.
1378 The const qualifier has been removed from iconv(3) to comply with
1379 POSIX. The ports tree is aware of this from r384038 onwards.
1382 Libraries specified by LIBADD in Makefiles must have a corresponding
1383 DPADD_<lib> variable to ensure correct dependencies. This is now
1384 enforced in src.libnames.mk.
1387 From legacy ata(4) driver was removed support for SATA controllers
1388 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1389 Kernel modules ataahci and ataadaptec were removed completely,
1390 replaced by ahci and mvs modules respectively.
1393 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1394 the 20141231 entry below for information about prerequisites and
1395 upgrading, if you are not already using 3.5.0 or higher.
1398 The 32-bit PowerPC kernel has been changed to a position-independent
1399 executable. This can only be booted with a version of loader(8)
1400 newer than January 31, 2015, so make sure to update both world and
1401 kernel before rebooting.
1404 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1405 but before r278950, the RNG was not seeded properly. Immediately
1406 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1407 ssh keys or openssl keys) that were generated w/ a kernel from that
1408 range. This does not affect programs that directly used /dev/random
1409 or /dev/urandom. All userland uses of arc4random(3) are affected.
1412 The autofs(4) ABI was changed in order to restore binary compatibility
1413 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1414 with the new kernel.
1417 The powerpc64 kernel has been changed to a position-independent
1418 executable. This can only be booted with a new version of loader(8),
1419 so make sure to update both world and kernel before rebooting.
1422 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1423 only release, no new features have been added. Please see the 20141231
1424 entry below for information about prerequisites and upgrading, if you
1425 are not already using 3.5.0.
1428 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1429 taken from the ELF Tool Chain project rather than GNU binutils. They
1430 should be drop-in replacements, with the addition of arm64 support.
1431 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1432 binutils tools, if necessary. See 20150805 for updated information.
1435 The default Unbound configuration now enables remote control
1436 using a local socket. Users who have already enabled the
1437 local_unbound service should regenerate their configuration
1438 by running "service local_unbound setup" as root.
1441 The GNU texinfo and GNU info pages have been removed.
1442 To be able to view GNU info pages please install texinfo from ports.
1445 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1447 As of this release, a prerequisite for building clang, llvm and lldb is
1448 a C++11 capable compiler and C++11 standard library. This means that to
1449 be able to successfully build the cross-tools stage of buildworld, with
1450 clang as the bootstrap compiler, your system compiler or cross compiler
1451 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1452 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1455 On any standard FreeBSD 10.x or 11.x installation, where clang and
1456 libc++ are on by default (that is, on x86 or arm), this should work out
1459 On 9.x installations where clang is enabled by default, e.g. on x86 and
1460 powerpc, libc++ will not be enabled by default, so libc++ should be
1461 built (with clang) and installed first. If both clang and libc++ are
1462 missing, build clang first, then use it to build libc++.
1464 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1465 the instructions for 9.x above.
1467 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1468 default, and do not build clang.
1470 Many embedded systems are resource constrained, and will not be able to
1471 build clang in a reasonable time, or in some cases at all. In those
1472 cases, cross building bootable systems on amd64 is a workaround.
1474 This new version of clang introduces a number of new warnings, of which
1475 the following are most likely to appear:
1479 This warns in two cases, for both C and C++:
1480 * When the code is trying to take the absolute value of an unsigned
1481 quantity, which is effectively a no-op, and almost never what was
1482 intended. The code should be fixed, if at all possible. If you are
1483 sure that the unsigned quantity can be safely cast to signed, without
1484 loss of information or undefined behavior, you can add an explicit
1485 cast, or disable the warning.
1487 * When the code is trying to take an absolute value, but the called
1488 abs() variant is for the wrong type, which can lead to truncation.
1489 If you want to disable the warning instead of fixing the code, please
1490 make sure that truncation will not occur, or it might lead to unwanted
1493 -Wtautological-undefined-compare and
1494 -Wundefined-bool-conversion
1496 These warn when C++ code is trying to compare 'this' against NULL, while
1497 'this' should never be NULL in well-defined C++ code. However, there is
1498 some legacy (pre C++11) code out there, which actively abuses this
1499 feature, which was less strictly defined in previous C++ versions.
1501 Squid and openjdk do this, for example. The warning can be turned off
1502 for C++98 and earlier, but compiling the code in C++11 mode might result
1503 in unexpected behavior; for example, the parts of the program that are
1504 unreachable could be optimized away.
1507 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1508 kernel sources have been removed. The .h files remain, since some
1509 utilities include them. This will need to be fixed later.
1510 If "mount -t oldnfs ..." is attempted, it will fail.
1511 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1512 the utilities will report errors.
1515 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1516 directories to top level SUBDIR variable when their parent
1517 directory is included in LOCAL_DIRS. Users with build systems with
1518 such hierarchies and without SUBDIR entries in the parent
1519 directory Makefiles should add them or add the directories to
1523 faith(4) and faithd(8) have been removed from the base system. Faith
1524 has been obsolete for a very long time.
1527 vt(4), the new console driver, is enabled by default. It brings
1528 support for Unicode and double-width characters, as well as
1529 support for UEFI and integration with the KMS kernel video
1532 You may need to update your console settings in /etc/rc.conf,
1533 most probably the keymap. During boot, /etc/rc.d/syscons will
1534 indicate what you need to do.
1536 vt(4) still has issues and lacks some features compared to
1537 syscons(4). See the wiki for up-to-date information:
1538 https://wiki.freebsd.org/Newcons
1540 If you want to keep using syscons(4), you can do so by adding
1541 the following line to /boot/loader.conf:
1545 pjdfstest has been integrated into kyua as an opt-in test suite.
1546 Please see share/doc/pjdfstest/README for more details on how to
1550 gperf has been removed from the base system for architectures
1551 that use clang. Ports that require gperf will obtain it from the
1555 pjdfstest has been moved from tools/regression/pjdfstest to
1559 At svn r271982, The default linux compat kernel ABI has been adjusted
1560 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1561 update. If you wish to continue using the linux-f10 compat ports,
1562 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1563 encouraged to update their linux-compat packages to linux-c6 during
1564 their next update cycle.
1567 The ofwfb driver, used to provide a graphics console on PowerPC when
1568 using vt(4), no longer allows mmap() of all physical memory. This
1569 will prevent Xorg on PowerPC with some ATI graphics cards from
1570 initializing properly unless x11-servers/xorg-server is updated to
1574 The xdev targets have been converted to using TARGET and
1575 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1578 The default unbound configuration has been modified to address
1579 issues with reverse lookups on networks that use private
1580 address ranges. If you use the local_unbound service, run
1581 "service local_unbound setup" as root to regenerate your
1582 configuration, then "service local_unbound reload" to load the
1586 The GNU texinfo and GNU info pages are not built and installed
1587 anymore, WITH_INFO knob has been added to allow to built and install
1589 UPDATE: see 20150102 entry on texinfo's removal
1592 The GNU readline library is now an INTERNALLIB - that is, it is
1593 statically linked into consumers (GDB and variants) in the base
1594 system, and the shared library is no longer installed. The
1595 devel/readline port is available for third party software that
1599 The Itanium architecture (ia64) has been removed from the list of
1600 known architectures. This is the first step in the removal of the
1604 Commit r268115 has added NFSv4.1 server support, merged from
1605 projects/nfsv4.1-server. Since this includes changes to the
1606 internal interfaces between the NFS related modules, a full
1607 build of the kernel and modules will be necessary.
1608 __FreeBSD_version has been bumped.
1611 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1612 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1613 which differs from the behaviour controlled by this knob.)
1616 Maximal length of the serial number in CTL was increased from 16 to
1617 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1618 and ctld, need to be rebuilt to work with a new kernel.
1621 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1622 1 respectively to match the upstream numbers. They were out of
1623 sync because, when they were originally added to FreeBSD, the
1624 upstream versions were not respected. These libraries are private
1625 and not yet built by default, so renumbering them should be a
1626 non-issue. However, unclean source trees will yield broken test
1627 programs once the operator executes "make delete-old-libs" after a
1628 "make installworld".
1630 Additionally, the atf-sh binary was made private by moving it into
1631 /usr/libexec/. Already-built shell test programs will keep the
1632 path to the old binary so they will break after "make delete-old"
1635 If you are using WITH_TESTS=yes (not the default), wipe the object
1636 tree and rebuild from scratch to prevent spurious test failures.
1637 This is only needed once: the misnumbered libraries and misplaced
1638 binaries have been added to OptionalObsoleteFiles.inc so they will
1639 be removed during a clean upgrade.
1642 Clang and llvm have been upgraded to 3.4.1 release.
1645 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1646 be removed to avoid issues in the future (and has been added to
1650 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1651 past, it affected all builds that used the bsd.*.mk files. The old
1652 behavior was a bug, but people may have relied upon it. To get this
1653 behavior back, you can .include /etc/src.conf from /etc/make.conf
1654 (which is still global and isn't changed). This also changes the
1655 behavior of incremental builds inside the tree of individual
1656 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1657 Although this has survived make universe and some upgrade scenarios,
1658 other upgrade scenarios may have broken. At least one form of
1659 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1660 as well... In cases where MAKESYSPATH isn't working with this
1661 setting, you'll need to set it to the full path to your tree.
1663 One side effect of all this cleaning up is that bsd.compiler.mk
1664 is no longer implicitly included by bsd.own.mk. If you wish to
1665 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1669 The lindev device has been removed since /dev/full has been made a
1670 standard device. __FreeBSD_version has been bumped.
1673 The knob WITHOUT_VI was added to the base system, which controls
1674 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1675 in order to reorder files share/termcap and didn't build ex(1) as a
1676 build tool, so building/installing with WITH_VI is highly advised for
1677 build hosts for older releases.
1679 This issue has been fixed in stable/9 and stable/10 in r277022 and
1680 r276991, respectively.
1683 The YES_HESIOD knob has been removed. It has been obsolete for
1684 a decade. Please move to using WITH_HESIOD instead or your builds
1685 will silently lack HESIOD.
1688 The uart(4) driver has been changed with respect to its handling
1689 of the low-level console. Previously the uart(4) driver prevented
1690 any process from changing the baudrate or the CLOCAL and HUPCL
1691 control flags. By removing the restrictions, operators can make
1692 changes to the serial console port without having to reboot.
1693 However, when getty(8) is started on the serial device that is
1694 associated with the low-level console, a misconfigured terminal
1695 line in /etc/ttys will now have a real impact.
1696 Before upgrading the kernel, make sure that /etc/ttys has the
1697 serial console device configured as 3wire without baudrate to
1698 preserve the previous behaviour. E.g:
1699 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1702 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1703 to improve performance. To re-enable it, if needed, run rpcbind
1704 with command line option -W.
1707 Switched back to the GPL dtc compiler due to updates in the upstream
1708 dts files not being supported by the BSDL dtc compiler. You will need
1709 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1710 may result while building dtb files during a kernel build if you fail
1711 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1714 Clang and llvm have been upgraded to 3.4 release.
1717 The nve(4) driver has been removed. Please use the nfe(4) driver
1718 for NVIDIA nForce MCP Ethernet adapters instead.
1721 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1722 This could cause certain C++ applications using shared libraries built
1723 against the previous version of libc++ to crash. The incompatibility
1724 has now been fixed, but any C++ applications or shared libraries built
1725 between r261283 and r261801 should be recompiled.
1728 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1729 capability mode support. Please note that enabling the feature in
1730 kernel is still highly recommended.
1733 OpenSSH is now built with sandbox support, and will use sandbox as
1734 the default privilege separation method. This requires Capsicum
1735 capability mode support in kernel.
1738 The libelf and libdwarf libraries have been updated to newer
1739 versions from upstream. Shared library version numbers for
1740 these two libraries were bumped. Any ports or binaries
1741 requiring these two libraries should be recompiled.
1742 __FreeBSD_version is bumped to 1100006.
1745 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1746 instead of providing an explicit one, this would prevent such
1747 Makefile from providing its own Kyuafile in the future during
1748 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1749 intervention is needed to clean an objdir if you use NO_CLEAN:
1750 # find /usr/obj -name Kyuafile | xargs rm -f
1753 The behavior of gss_pseudo_random() for the krb5 mechanism
1754 has changed, for applications requesting a longer random string
1755 than produced by the underlying enctype's pseudo-random() function.
1756 In particular, the random string produced from a session key of
1757 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1758 be different at the 17th octet and later, after this change.
1759 The counter used in the PRF+ construction is now encoded as a
1760 big-endian integer in accordance with RFC 4402.
1761 __FreeBSD_version is bumped to 1100004.
1764 The WITHOUT_ATF build knob has been removed and its functionality
1765 has been subsumed into the more generic WITHOUT_TESTS. If you were
1766 using the former to disable the build of the ATF libraries, you
1767 should change your settings to use the latter.
1770 The default version of mtree is nmtree which is obtained from
1771 NetBSD. The output is generally the same, but may vary
1772 slightly. If you found you need identical output adding
1773 "-F freebsd9" to the command line should do the trick. For the
1774 time being, the old mtree is available as fmtree.
1777 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1778 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1779 1.1.4_8 and verify bsdyml not linked in, before running "make
1781 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1783 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1786 The stable/10 branch has been created in subversion from head
1793 Avoid using make -j when upgrading. While generally safe, there are
1794 sometimes problems using -j to upgrade. If your upgrade fails with
1795 -j, please try again without -j. From time to time in the past there
1796 have been problems using -j with buildworld and/or installworld. This
1797 is especially true when upgrading between "distant" versions (eg one
1798 that cross a major release boundary or several minor releases, or when
1799 several months have passed on the -current branch).
1801 Sometimes, obscure build problems are the result of environment
1802 poisoning. This can happen because the make utility reads its
1803 environment when searching for values for global variables. To run
1804 your build attempts in an "environmental clean room", prefix all make
1805 commands with 'env -i '. See the env(1) manual page for more details.
1807 When upgrading from one major version to another it is generally best to
1808 upgrade to the latest code in the currently installed branch first, then
1809 do an upgrade to the new branch. This is the best-tested upgrade path,
1810 and has the highest probability of being successful. Please try this
1811 approach if you encounter problems with a major version upgrade. Since
1812 the stable 4.x branch point, one has generally been able to upgrade from
1813 anywhere in the most recent stable branch to head / current (or even the
1814 last couple of stable branches). See the top of this file when there's
1817 When upgrading a live system, having a root shell around before
1818 installing anything can help undo problems. Not having a root shell
1819 around can lead to problems if pam has changed too much from your
1820 starting point to allow continued authentication after the upgrade.
1822 This file should be read as a log of events. When a later event changes
1823 information of a prior event, the prior event should not be deleted.
1824 Instead, a pointer to the entry with the new information should be
1825 placed in the old entry. Readers of this file should also sanity check
1826 older entries before relying on them blindly. Authors of new entries
1827 should write them with this in mind.
1831 When upgrading the boot ZFS pool to a new version, always follow
1834 1.) recompile and reinstall the ZFS boot loader and boot block
1835 (this is part of "make buildworld" and "make installworld")
1837 2.) update the ZFS boot block on your boot drive
1839 The following example updates the ZFS boot block on the first
1840 partition (freebsd-boot) of a GPT partitioned drive ada0:
1841 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1843 Non-boot pools do not need these updates.
1847 If you are updating from a prior version of FreeBSD (even one just
1848 a few days old), you should follow this procedure. It is the most
1849 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1851 make kernel-toolchain
1852 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1853 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1855 To test a kernel once
1856 ---------------------
1857 If you just want to boot a kernel once (because you are not sure
1858 if it works, or if you want to boot a known bad kernel to provide
1859 debugging information) run
1860 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1861 nextboot -k testkernel
1863 To rebuild everything and install it on the current system.
1864 -----------------------------------------------------------
1865 # Note: sometimes if you are running current you gotta do more than
1866 # is listed here if you are upgrading from a really old current.
1868 <make sure you have good level 0 dumps>
1870 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1871 make installkernel KERNCONF=YOUR_KERNEL_HERE
1873 <reboot in single user> [3]
1880 To cross-install current onto a separate partition
1881 --------------------------------------------------
1882 # In this approach we use a separate partition to hold
1883 # current's root, 'usr', and 'var' directories. A partition
1884 # holding "/", "/usr" and "/var" should be about 2GB in
1887 <make sure you have good level 0 dumps>
1890 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1891 <maybe newfs current's root partition>
1892 <mount current's root partition on directory ${CURRENT_ROOT}>
1893 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1894 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1895 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1896 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1897 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1898 <reboot into current>
1899 <do a "native" rebuild/install as described in the previous section>
1900 <maybe install compatibility libraries from ports/misc/compat*>
1904 To upgrade in-place from stable to current
1905 ----------------------------------------------
1906 <make sure you have good level 0 dumps>
1908 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1909 make installkernel KERNCONF=YOUR_KERNEL_HERE
1911 <reboot in single user> [3]
1918 Make sure that you've read the UPDATING file to understand the
1919 tweaks to various things you need. At this point in the life
1920 cycle of current, things change often and you are on your own
1921 to cope. The defaults can also change, so please read ALL of
1922 the UPDATING entries.
1924 Also, if you are tracking -current, you must be subscribed to
1925 freebsd-current@freebsd.org. Make sure that before you update
1926 your sources that you have read and understood all the recent
1927 messages there. If in doubt, please track -stable which has
1928 much fewer pitfalls.
1930 [1] If you have third party modules, such as vmware, you
1931 should disable them at this point so they don't crash your
1934 [3] From the bootblocks, boot -s, and then do
1939 adjkerntz -i # if CMOS is wall time
1940 Also, when doing a major release upgrade, it is required that
1941 you boot into single user mode to do the installworld.
1943 [4] Note: This step is non-optional. Failure to do this step
1944 can result in a significant reduction in the functionality of the
1945 system. Attempting to do it by hand is not recommended and those
1946 that pursue this avenue should read this file carefully, as well
1947 as the archives of freebsd-current and freebsd-hackers mailing lists
1948 for potential gotchas. The -U option is also useful to consider.
1949 See mergemaster(8) for more information.
1951 [5] Usually this step is a no-op. However, from time to time
1952 you may need to do this if you get unknown user in the following
1953 step. It never hurts to do it all the time. You may need to
1954 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1955 install) after the buildworld before this step if you last updated
1956 from current before 20130425 or from -stable before 20130430.
1958 [6] This only deletes old files and directories. Old libraries
1959 can be deleted by "make delete-old-libs", but you have to make
1960 sure that no program is using those libraries anymore.
1962 [8] The new kernel must be able to run existing binaries used by
1963 an installworld. When upgrading across major versions, the new
1964 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1965 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1966 binaries). Failure to do so may leave you with a system that is
1967 hard to boot to recover. A GENERIC kernel will include suitable
1968 compatibility options to run binaries from older branches.
1970 Make sure that you merge any new devices from GENERIC since the
1971 last time you updated your kernel config file.
1973 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1974 "?=" instead of the "=" assignment operator, so that buildworld can
1975 override the CPUTYPE if it needs to.
1977 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1978 not on the command line, or in /etc/make.conf. buildworld will
1979 warn if it is improperly defined.
1982 This file contains a list, in reverse chronological order, of major
1983 breakages in tracking -current. It is not guaranteed to be a complete
1984 list of such breakages, and only contains entries since September 23, 2011.
1985 If you need to see UPDATING entries from before that date, you will need
1986 to fetch an UPDATING file from an older FreeBSD release.
1988 Copyright information:
1990 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1992 Redistribution, publication, translation and use, with or without
1993 modification, in full or in part, in any form or format of this
1994 document are permitted without further permission from the author.
1996 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1997 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1998 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1999 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2000 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2001 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2002 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2003 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2004 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2005 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2006 POSSIBILITY OF SUCH DAMAGE.
2008 Contact Warner Losh if you have any questions about your use of