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 20191112 p1 FreeBSD-EN-19:19.loader
20 FreeBSD-SA-19:25.mcepsc
22 Fix UEFI Loader Memory Fragmentation [EN-19:19.loader]
24 Fix Machine Check Exception on Page Size Change [SA-19:25.mcepsc]
30 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
31 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
32 been removed from mount_fusefs(8). You can safely remove them from
33 your scripts, because they had no effect.
35 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
36 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
37 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
38 sysctls have been removed. If you felt the need to set any of them to
39 a non-default value, please tell asomers@FreeBSD.org why.
42 The fuse(4) module has been renamed to fusefs(4) for consistency with
43 other filesystems. You should update any kld_load="fuse" entries in
44 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
45 "options FUSE" enties in kernel config files.
48 Default permissions on the /var/account/acct file (and copies of it
49 rotated by periodic daily scripts) are changed from 0644 to 0640
50 because the file contains sensitive information that should not be
51 world-readable. If the /var/account directory must be created by
52 rc.d/accounting, the mode used is now 0750. Admins who use the
53 accounting feature are encouraged to change the mode of an existing
54 /var/account directory to 0750 or 0700.
57 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
58 been upgraded to 8.0.1. Please see the 20141231 entry below for
59 information about prerequisites and upgrading, if you are not already
60 using clang 3.5.0 or higher.
63 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
64 functionality needed for the RETPOLINE option should work properly
65 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
68 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
69 8.0.0. Please see the 20141231 entry below for information about
70 prerequisites and upgrading, if you are not already using clang 3.5.0
74 The RETPOLINE option produces non-functional ifunc-using binaries
75 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
76 Once Clang 8 is merged it may be enabled again.
79 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
80 7.0.1. Please see the 20141231 entry below for information about
81 prerequisites and upgrading, if you are not already using clang 3.5.0
85 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
86 compiled into your custom kernel, add 'device xz' statement to the
90 Iflib is no longer unconditionally compiled into the kernel. Drivers
91 using iflib and statically compiled into the kernel, now require
92 the 'device iflib' config option. For the same drivers loaded as
93 modules on kernels not having 'device iflib', the iflib.ko module
94 is loaded automatically.
97 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
98 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
99 servers that have vfs.nfsd.nfs_privport set will only allow mounts
100 from clients using a reserved port#. Since both the FreeBSD and Linux
101 NFSv4 clients use reserved port#s by default, this should not affect
105 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
106 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
107 it produces broken binaries when ifuncs are in use. Users needing
108 GNU ld should install the binutils port or package.
111 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
112 has been converted to a port (misc/ctm) and will be removed from
113 FreeBSD-13. A depreciation warning will be printed to stderr by
114 the ctm command, but the functionality will remain in base for all
118 The stable/12 branch has been created in subversion from head
122 Ports for the DRM modules have been simplified. Now, amd64 users should
123 just install the drm-kmod port. All others should install
126 Graphics hardware that's newer than about 2010 usually works with
127 drm-kmod. For hardware older than 2013, however, some users will need
128 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
129 than 2008 usually only works in drm-legacy-kmod. The graphics team can
130 only commit to hardware made since 2013 due to the complexity of the
131 market and difficulty to test all the older cards effectively. If you
132 have hardware supported by drm-kmod, you are strongly encouraged to use
133 that as you will get better support.
135 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
136 elsewhere, the drm and drm2 modules will be eliminated from the src base
137 soon (with a limited exception for arm). Please update to the package asap
138 and report any issues to x11@freebsd.org.
140 Generally, anybody using the drm*-kmod packages should add
141 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
142 cross-threading surprises, especially with automatic driver
143 loading from X11 startup. These will become the defaults in 13-current
147 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
148 custom kernel and module loading configuration files must be updated
149 accordingly. Moreover, interfaces previous presented as ixlvN to the
150 system are now exposed as iavfN and network configuration files must
151 be adjusted as necessary.
154 OpenSSL has been updated to version 1.1.1. This update included
155 additional various API changes througout the base system. It is
156 important to rebuild third-party software after upgrading. The value
157 of __FreeBSD_version has been bumped accordingly.
160 The legacy DRM modules and drivers have now been added to the loader's
161 module blacklist, in favor of loading them with kld_list in rc.conf(5).
162 The module blacklist may be overridden with the loader.conf(5)
163 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
167 The cam(4) based nda(4) driver will be used over nvd(4) by default on
168 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
169 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
170 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
174 Reproducible build mode is now on by default, in preparation for
175 FreeBSD 12.0. This eliminates build metadata such as the user,
176 host, and time from the kernel (and uname), unless the working tree
177 corresponds to a modified checkout from a version control system.
178 The previous behavior can be obtained by setting the /etc/src.conf
179 knob WITHOUT_REPRODUCIBLE_BUILD.
182 The Yarrow CSPRNG has been removed from the kernel as it has not been
183 supported by its designers since at least 2003. Fortuna has been the
184 default since FreeBSD-11.
187 devctl freeze/thaw have gone into the tree, the rc scripts have been
188 updated to use them and devmatch has been changed. You should update
189 kernel, userland and rc scripts all at the same time.
192 The default interpreter has been switched from 4th to Lua.
193 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
194 interpreter. If you have custom FORTH code you will need to set
195 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
196 src.conf for the build. This will create default hard links between
197 loader and loader_4th instead of loader and loader_lua, the new default.
198 If you are using UEFI it will create the proper hard link to loader.efi.
200 bhyve uses userboot.so. It remains 4th-only until some issues are solved
201 regarding coexisting with multiple versions of FreeBSD are resolved.
204 ls(1) now respects the COLORTERM environment variable used in other
205 systems and software to indicate that a colored terminal is both
206 supported and desired. If ls(1) is suddenly emitting colors, they may
207 be disabled again by either removing the unwanted COLORTERM from your
208 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
209 may not be observed in a future release.
212 The default pager for most commands has been changed to "less". To
213 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
217 The jedec_ts(4) driver has been removed. A superset of its functionality
218 is available in the jedec_dimm(4) driver, and the manpage for that
219 driver includes migration instructions. If you have "device jedec_ts"
220 in your kernel configuration file, it must be removed.
223 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
224 This should have no effect if the kernel is booted via BIOS/legacy boot.
225 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
226 has a buggy firmware that prevents a successful boot due to use of
230 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
231 support has been removed from the tree. These ports were
232 obsolete and/or known to be broken for many years.
235 loader.efi has been augmented to participate more fully in the
236 UEFI boot manager protocol. loader.efi will now look at the
237 BootXXXX environment variable to determine if a specific kernel
238 or root partition was specified. XXXX is derived from BootCurrent.
239 efibootmgr(8) manages these standard UEFI variables.
242 zfsloader's functionality has now been folded into loader.
243 zfsloader is no longer necessary once you've updated your
244 boot blocks. For a transition period, we will install a
245 hardlink for zfsloader to loader to allow a smooth transition
246 until the boot blocks can be updated (hard link because old
247 zfs boot blocks don't understand symlinks).
250 ARM64 now have efifb support, if you want to have serial console
251 on your arm64 board when an screen is connected and the bootloader
252 setup a frambuffer for us to use, just add :
256 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
257 an screen connected as the firmware will setup a framebuffer are that
258 u-boot will expose as an EFI framebuffer.
261 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
262 or take steps to update /etc/passwd before doing installworld on
263 existing systems. Do not skip the "mergemaster -Fp" step before
264 installworld, as described in the update procedures near the bottom
265 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
266 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
267 the ntp config file contain options that change file/dir locations.
268 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
269 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
270 taking steps to ensure that all required files/dirs are accessible
274 Big endian arm support has been removed.
277 The static environment setup in kernel configs is no longer mutually
278 exclusive with the loader(8) environment by default. In order to
279 restore the previous default behavior of disabling the loader(8)
280 environment if a static environment is present, you must specify
281 loader_env.disabled=1 in the static environment.
284 The ABI of syscalls used by management tools like sockstat and
285 netstat has been broken to allow 32-bit binaries to work on
286 64-bit kernels without modification. These programs will need
287 to match the kernel in order to function. External programs may
288 require minor modifications to accommodate a change of type in
289 structures from pointers to 64-bit virtual addresses.
292 On i386 and amd64 atomics are now inlined. Out of tree modules using
293 atomics will need to be rebuilt.
296 The '%I' format in the kern.corefile sysctl limits the number of
297 core files that a process can generate to the number stored in the
298 debug.ncores sysctl. The '%I' format is replaced by the single digit
299 index. Previously, if all indexes were taken the kernel would overwrite
300 only a core file with the highest index in a filename.
301 Currently the system will create a new core file if there is a free
302 index or if all slots are taken it will overwrite the oldest one.
305 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
306 6.0.1. Please see the 20141231 entry below for information about
307 prerequisites and upgrading, if you are not already using clang 3.5.0
311 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
312 needed to be changed to work with it. This change was made with r335763
313 and requires a mergemaster / etcupdate / etc to update the installed file.
316 r334930 changed the interface between the NFS modules, so they all
317 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
320 As of r334391 lld is the default amd64 system linker; it is installed
321 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
325 The kernel / userland interface for devinfo changed, so you'll
326 need a new kernel and userland as a pair for it to work (rebuilding
327 lib/libdevinfo is all that's required). devinfo and devmatch will
328 not work, but everything else will when there's a mismatch.
331 The on-disk format for hwpmc callchain records has changed to include
332 threadid corresponding to a given record. This changes the field offsets
333 and thus requires that libpmcstat be rebuilt before using a kernel
337 The vxge(4) driver has been removed. This driver was introduced into
338 HEAD one week before the Exar left the Ethernet market and is not
339 known to be used. If you have device vxge in your kernel config file
343 The amd64 kernel now requires a ld that supports ifunc to produce a
344 working kernel, either lld or a newer binutils. lld is built by default
345 on amd64, and the 'buildkernel' target uses it automatically. However,
346 it is not the default linker, so building the kernel the traditional
347 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
348 binutils port/package). lld will soon be default, and this requirement
351 NOTE: As of r334391 lld is the default system linker on amd64, and no
352 workaround is necessary.
355 The nxge(4) driver has been removed. This driver was for PCI-X 10g
356 cards made by s2io/Neterion. The company was aquired by Exar and
357 no longer sells or supports Ethernet products. If you have device
358 nxge in your kernel config file it must be removed.
361 The tz database (tzdb) has been updated to 2018e. This version more
362 correctly models time stamps in time zones with negative DST such as
363 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
364 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
365 time zone abbreviations and the tm_isdst flag.
368 The ixgb(4) driver has been removed. This driver was for an early and
369 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
370 quickly shifted to the long lived ixgbe family. If you have device
371 ixgb in your kernel config file it must be removed.
374 The lmc(4) driver has been removed. This was a WAN interface
375 card that was already reportedly rare in 2003, and had an ambiguous
376 license. If you have device lmc in your kernel config file it must
380 Support for Arcnet networks has been removed. If you have device
381 arcnet or device cm in your kernel config file they must be
385 Support for FDDI networks has been removed. If you have device
386 fddi or device fpa in your kernel config file they must be
390 In addition to supporting RFC 3164 formatted messages, the
391 syslogd(8) service is now capable of parsing RFC 5424 formatted
392 log messages. The main benefit of using RFC 5424 is that clients
393 may now send log messages with timestamps containing year numbers,
394 microseconds and time zone offsets.
396 Similarly, the syslog(3) C library function has been altered to
397 send RFC 5424 formatted messages to the local system logging
398 daemon. On systems using syslogd(8), this change should have no
399 negative impact, as long as syslogd(8) and the C library are
400 updated at the same time. On systems using a different system
401 logging daemon, it may be necessary to make configuration
402 adjustments, depending on the software used.
404 When using syslog-ng, add the 'syslog-protocol' flag to local
405 input sources to enable parsing of RFC 5424 formatted messages:
408 unix-dgram("/var/run/log" flags(syslog-protocol));
411 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
412 of the 'imuxsock' module to let messages be processed by the
413 regular RFC 3164/5424 parsing pipeline:
415 module(load="imuxsock" SysSock.UseSpecialParser="off")
417 Do note that these changes only affect communication between local
418 applications and syslogd(8). The format that syslogd(8) uses to
419 store messages on disk or forward messages to other systems
420 remains unchanged. syslogd(8) still uses RFC 3164 for these
421 purposes. Options to customize this behaviour will be added in the
422 future. Utilities that process log files stored in /var/log are
423 thus expected to continue to function as before.
425 __FreeBSD_version has been incremented to 1200061 to denote this
429 Support for token ring networks has been removed. If you
430 have "device token" in your kernel config you should remove
431 it. No device drivers supported token ring.
434 makefs was modified to be able to tag ISO9660 El Torito boot catalog
435 entries as EFI instead of overloading the i386 tag as done previously.
436 The amd64 mkisoimages.sh script used to build amd64 ISO images for
437 release was updated to use this. This may mean that makefs must be
438 updated before "make cdrom" can be run in the release directory. This
439 should be as simple as:
441 $ cd $SRCDIR/usr.sbin/makefs
442 $ make depend all install
445 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
446 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
447 Co-existance for the transition period will come shortly. Booting is a
448 complex environment and test coverage for Lua-enabled loaders has been
449 thin, so it would be prudent to assume it might not work and make
450 provisions for backup boot methods.
453 devmatch functionality has been turned on in devd. It will automatically
454 load drivers for unattached devices. This may cause unexpected drivers to
455 be loaded. Please report any problems to current@ and imp@freebsd.org.
458 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
459 6.0.0. Please see the 20141231 entry below for information about
460 prerequisites and upgrading, if you are not already using clang 3.5.0
464 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
465 This means it is used to link the kernel and userland libraries and
466 executables, but is not yet installed as /usr/bin/ld by default.
468 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
469 WITHOUT_LLD_BOOTSTRAP=yes
472 On i386, pmtimer has been removed. Its functionality has been folded
473 into apm. It was a no-op on ACPI in current for a while now (but was still
474 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
475 from kernel config files.
478 The use of RSS hash from the network card aka flowid has been
479 disabled by default for lagg(4) as it's currently incompatible with
480 the lacp and loadbalance protocols.
482 This can be re-enabled by setting the following in loader.conf:
483 net.link.lagg.default_use_flowid="1"
486 The SW_WATCHDOG option is no longer necessary to enable the
487 hardclock-based software watchdog if no hardware watchdog is
488 configured. As before, SW_WATCHDOG will cause the software
489 watchdog to be enabled even if a hardware watchdog is configured.
492 r326887 fixes the issue described in the 20171214 UPDATING entry.
493 r326888 flips the switch back to building GELI support always.
496 r362593 broke ZFS + GELI support for reasons unknown. However,
497 it also broke ZFS support generally, so GELI has been turned off
498 by default as the lesser evil in r326857. If you boot off ZFS and/or
499 GELI, it might not be a good time to update.
502 PowerPC users must update loader(8) by rebuilding world before
503 installing a new kernel, as the protocol connecting them has
504 changed. Without the update, loader metadata will not be passed
505 successfully to the kernel and users will have to enter their
506 root partition at the kernel mountroot prompt to continue booting.
507 Newer versions of loader can boot old kernels without issue.
510 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
511 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
512 to WITH/OUT_LOADER_GELI.
515 The naive and non-compliant support of posix_fallocate(2) in ZFS
516 has been removed as of r325320. The system call now returns EINVAL
517 when used on a ZFS file. Although the new behavior complies with the
518 standard, some consumers are not prepared to cope with it.
519 One known victim is lld prior to r325420.
522 Building in a FreeBSD src checkout will automatically create object
523 directories now rather than store files in the current directory if
524 'make obj' was not ran. Calling 'make obj' is no longer necessary.
525 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
526 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
530 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
531 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
532 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
533 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
534 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
535 The UNIFIED_OBJDIR option is a transitional feature that will be
536 removed for 12.0 release; please migrate to the new format for any
537 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
538 than hardcoding paths.
541 The native-xtools target no longer installs the files by default to the
542 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
543 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
546 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
547 options are changing from controlling the build if defined / undefined
548 to controlling the build with explicit 'yes' or 'no' values. They will
549 shift to WITH/WITHOUT options to match other options in the system.
552 libstand has turned into a private library for sys/boot use only.
553 It is no longer supported as a public interface outside of sys/boot.
556 The arm port has split armv6 into armv6 and armv7. armv7 is now
557 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
558 and are running a kernel from before r324363, you will need to add
559 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
562 When building multiple kernels using KERNCONF, non-existent KERNCONF
563 files will produce an error and buildkernel will fail. Previously
564 missing KERNCONF files silently failed giving no indication as to
565 why, only to subsequently discover during installkernel that the
566 desired kernel was never built in the first place.
569 The default serial number format for CTL LUNs has changed. This will
570 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
571 or iSCSI clients care about their LUNs' serial numbers. Users who
572 require serial number stability should hardcode serial numbers in
576 For 32-bit arm compiled for hard-float support, soft-floating point
577 binaries now always get their shared libraries from
578 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
579 /usr/libsoft also existed). Only users with a hard-float ld.so, but
580 soft-float everything else should be affected.
583 The geli password typed at boot is now hidden. To restore the previous
584 behavior, see geli(8) for configuration options.
587 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
588 sysctl values. Minor nit, but requires a rebuild of both world/kernel
592 "make check" behavior (made in ^/head@r295380) has been changed to
593 execute from a limited sandbox, as opposed to executing from
597 - The "beforecheck" and "aftercheck" targets are now specified.
598 - ${CHECKDIR} (added in commit noted above) has been removed.
599 - Legacy behavior can be enabled by setting
600 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
602 If the limited sandbox mode is enabled, "make check" will execute
603 "make distribution", then install, execute the tests, and clean up the
604 sandbox if successful.
606 The "make distribution" and "make install" targets are typically run as
607 root to set appropriate permissions and ownership at installation time.
608 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
609 environment if executing "make check" with limited sandbox mode using
610 an unprivileged user.
613 Since the switch to GPT disk labels, fsck for UFS/FFS has been
614 unable to automatically find alternate superblocks. As of r322297,
615 the information needed to find alternate superblocks has been
616 moved to the end of the area reserved for the boot block.
617 Filesystems created with a newfs of this vintage or later
618 will create the recovery information. If you have a filesystem
619 created prior to this change and wish to have a recovery block
620 created for your filesystem, you can do so by running fsck in
621 foreground mode (i.e., do not use the -p or -y options). As it
622 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
623 to which you should answer yes.
626 As of r321665, an NFSv4 server configuration that services
627 Kerberos mounts or clients that do not support the uid/gid in
628 owner/owner_group string capability, must explicitly enable
629 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
630 machine's /etc/rc.conf file.
633 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
634 Please see the 20141231 entry below for information about prerequisites
635 and upgrading, if you are not already using clang 3.5.0 or higher.
638 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
639 r-commands (rlogin, rsh, etc.) to be built with the base system.
642 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
643 a very major ABI incompatible change, so users of FreeBSD/powerpc must
644 be careful when performing source upgrades. It is best to run
645 'make installworld' from an alternate root system, either a live
646 CD/memory stick, or a temporary root partition. Additionally, all ports
647 must be recompiled. powerpc64 is largely unaffected, except in the case
648 of 32-bit compatibility. All 32-bit binaries will be affected.
651 Forward compatibility for the "ino64" project have been committed. This
652 will allow most new binaries to run on older kernels in a limited
653 fashion. This prevents many of the common foot-shooting actions in the
654 upgrade as well as the limited ability to roll back the kernel across
655 the ino64 upgrade. Complicated use cases may not work properly, though
656 enough simpler ones work to allow recovery in most situations.
659 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
660 if you require the GPL compiler.
663 The internal ABI used for communication between the NFS kernel modules
664 was changed by r320085, so __FreeBSD_version was bumped to
665 ensure all the NFS related modules are updated together.
668 The ABI of struct event was changed by extending the data
669 member to 64bit and adding ext fields. For upgrade, same
670 precautions as for the entry 20170523 "ino64" must be
674 The GNU roff toolchain has been removed from base. To render manpages
675 which are not supported by mandoc(1), man(1) can fallback on GNU roff
676 from ports (and recommends to install it).
677 To render roff(7) documents, consider using GNU roff from ports or the
678 heirloom doctools roff toolchain from ports via pkg install groff or
679 via pkg install heirloom-doctools.
682 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
683 smaller runtime footprint builds. This is useful for embedded systems
684 which only require one chipset support.
686 If you load it as a module, make sure this is in /boot/loader.conf:
690 This will load the HAL, all chip/RF backends and if_ath_pci.
691 If you have if_ath_pci in /boot/loader.conf, ensure it is after
692 if_ath or it will not load any HAL chipset support.
694 If you want to selectively load things (eg on ye cheape ARM/MIPS
695 platforms where RAM is at a premium) you should:
698 * load the chip modules in question
699 * load ath_rate, ath_dfs
701 * load if_ath_pci and/or if_ath_ahb depending upon your particular
702 bus bind type - this is where probe/attach is done.
704 For further comments/feedback, poke adrian@ .
707 The "ino64" 64-bit inode project has been committed, which extends
708 a number of types to 64 bits. Upgrading in place requires care and
709 adherence to the documented upgrade procedure.
711 If using a custom kernel configuration ensure that the
712 COMPAT_FREEBSD11 option is included (as during the upgrade the
713 system will be running the ino64 kernel with the existing world).
715 For the safest in-place upgrade begin by removing previous build
716 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
717 full procedure documented below under the heading "To rebuild
718 everything and install it on the current system." Specifically,
719 a reboot is required after installing the new kernel before
723 The NATM framework including the en(4), fatm(4), hatm(4), and
724 patm(4) devices has been removed. Consumers should plan a
725 migration before the end-of-life date for FreeBSD 11.
728 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
729 diff has not been implemented, if those are needed a newer version of
730 GNU diff is available via the diffutils package under the gdiff name.
733 As of r316810 for ipfilter, keep frags is no longer assumed when
734 keep state is specified in a rule. r316810 aligns ipfilter with
735 documentation in man pages separating keep frags from keep state.
736 This allows keep state to be specified without forcing keep frags
737 and allows keep frags to be specified independently of keep state.
738 To maintain previous behaviour, also specify keep frags with
739 keep state (as documented in ipf.conf.5).
742 arm64 builds now use the base system LLD 4.0.0 linker by default,
743 instead of requiring that the aarch64-binutils port or package be
744 installed. To continue using aarch64-binutils, set
745 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
748 The UDP optimization in entry 20160818 that added the sysctl
749 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
750 packets will no longer be treated as L3 broadcast packets.
753 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
754 use any explicitly assigned loopback address available in the jail
755 instead of using the first assigned address of the jail.
758 The ctl.ko module no longer implements the iSCSI target frontend:
759 cfiscsi.ko does instead.
761 If building cfiscsi.ko as a kernel module, the module can be loaded
762 via one of the following methods:
763 - `cfiscsi_load="YES"` in loader.conf(5).
764 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
765 - ctladm(8)/ctld(8), when compiled with iSCSI support
766 (`WITH_ISCSI=yes` in src.conf(5))
768 Please see cfiscsi(4) for more details.
771 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
772 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
773 same source (previously, the dependency of mmcsd.ko on mmc.ko was
774 missing, but mmcsd.ko now will refuse to load if it is incompatible
778 The syntax of ipfw(8) named states was changed to avoid ambiguity.
779 If you have used named states in the firewall rules, you need to modify
780 them after installworld and before rebooting. Now named states must
781 be prefixed with colon.
784 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
785 removed as the userland we provide cannot use them. The KMS version
786 (sys/dev/drm2) supports the same hardware.
789 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
790 Please see the 20141231 entry below for information about prerequisites
791 and upgrading, if you are not already using clang 3.5.0 or higher.
794 The code that provides support for ZFS .zfs/ directory functionality
795 has been reimplemented. It's not possible now to create a snapshot
796 by mkdir under .zfs/snapshot/. That should be the only user visible
800 EISA bus support has been removed. The WITH_EISA option is no longer
804 MCA bus support has been removed.
807 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
808 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
811 The EM_MULTIQUEUE kernel configuration option is deprecated now that
812 the em(4) driver conforms to iflib specifications.
815 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
816 IFLIB. If you have a custom kernel configuration that excludes em(4)
817 but you use igb(4), you need to re-add em(4) to your custom configuration.
820 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
821 Please see the 20141231 entry below for information about prerequisites
822 and upgrading, if you are not already using clang 3.5.0 or higher.
825 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
826 Please see the 20141231 entry below for information about prerequisites
827 and upgrading, if you are not already using clang 3.5.0 or higher.
830 The layout of the pmap structure has changed for powerpc to put the pmap
831 statistics at the front for all CPU variations. libkvm(3) and all tools
832 that link against it need to be recompiled.
835 isl(4) and cyapa(4) drivers now require a new driver,
836 chromebook_platform(4), to work properly on Chromebook-class hardware.
837 On other types of hardware the drivers may need to be configured using
838 device hints. Please see the corresponding manual pages for details.
841 The urtwn(4) driver was merged into rtwn(4) and now consists of
842 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
844 Also, firmware for RTL8188CE was renamed due to possible name
845 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
848 GNU rcs has been removed from base. It is available as packages:
849 - rcs: Latest GPLv3 GNU rcs version.
850 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
854 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
855 modules now requires that the kernel configuration contain the
856 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
859 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
860 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
863 Relocatable object files with the extension of .So have been renamed
864 to use an extension of .pico instead. The purpose of this change is
865 to avoid a name clash with shared libraries on case-insensitive file
866 systems. On those file systems, foo.So is the same file as foo.so.
869 GNU rcs has been turned off by default. It can (temporarily) be built
870 again by adding WITH_RCS knob in src.conf.
871 Otherwise, GNU rcs is available from packages:
872 - rcs: Latest GPLv3 GNU rcs version.
873 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
876 The backup_uses_rcs functionality has been removed from rc.subr.
879 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
880 two separate components, QUEUE_MACRO_DEBUG_TRACE and
881 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
882 QUEUE_MACRO_DEBUG behavior.
885 r304787 changed some ioctl interfaces between the iSCSI userspace
886 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
887 rebuilt to work with new kernels. __FreeBSD_version has been bumped
891 The UDP receive code has been updated to only treat incoming UDP
892 packets that were addressed to an L2 broadcast address as L3
893 broadcast packets. It is not expected that this will affect any
894 standards-conforming UDP application. The new behaviour can be
895 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
899 Remove the openbsd_poll system call.
900 __FreeBSD_version has been bumped because of this.
903 The stable/11 branch has been created from head@r302406.
906 The libc stub for the pipe(2) system call has been replaced with
907 a wrapper that calls the pipe2(2) system call and the pipe(2)
908 system call is now only implemented by the kernels that include
909 "options COMPAT_FREEBSD10" in their config file (this is the
910 default). Users should ensure that this option is enabled in
911 their kernel or upgrade userspace to r302092 before upgrading their
915 CAM will now strip leading spaces from SCSI disks' serial numbers.
916 This will affect users who create UFS filesystems on SCSI disks using
917 those disk's diskid device nodes. For example, if /etc/fstab
918 previously contained a line like
919 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
920 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
921 transforms like gmirror may also be affected. ZFS users should
925 The bitstring(3) API has been updated with new functionality and
926 improved performance. But it is binary-incompatible with the old API.
927 Objects built with the new headers may not be linked against objects
928 built with the old headers.
931 The brk and sbrk functions have been removed from libc on arm64.
932 Binutils from ports has been updated to not link to these
933 functions and should be updated to the latest version before
934 installing a new libc.
937 The armv6 port now defaults to hard float ABI. Limited support
938 for running both hardfloat and soft float on the same system
939 is available using the libraries installed with -DWITH_LIBSOFT.
940 This has only been tested as an upgrade path for installworld
941 and packages may fail or need manual intervention to run. New
942 packages will be needed.
944 To update an existing self-hosted armv6hf system, you must add
945 TARGET_ARCH=armv6 on the make command line for both the build
946 and the install steps.
949 Kernel modules compiled outside of a kernel build now default to
950 installing to /boot/modules instead of /boot/kernel. Many kernel
951 modules built this way (such as those in ports) already overrode
952 KMODDIR explicitly to install into /boot/modules. However,
953 manually building and installing a module from /sys/modules will
954 now install to /boot/modules instead of /boot/kernel.
957 The CAM I/O scheduler has been committed to the kernel. There should be
958 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
959 list of known rogues that claim support for this but actually corrupt
960 data is believed to be complete, be on the lookout for data
961 corruption. The known rogue list is believed to be complete:
963 o Crucial MX100, M550 drives with MU01 firmware.
964 o Micron M510 and M550 drives with MU01 firmware.
965 o Micron M500 prior to MU07 firmware
966 o Samsung 830, 840, and 850 all firmwares
967 o FCCT M500 all firmwares
969 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
970 with working NCQ TRIM. For Micron branded drives, see your sales rep for
971 updated firmware. Black listed drives will work correctly because these
972 drives work correctly so long as no NCQ TRIMs are sent to them. Given
973 this list is the same as found in Linux, it's believed there are no
974 other rogues in the market place. All other models from the above
977 To be safe, if you are at all concerned, you can quirk each of your
978 drives to prevent NCQ from being sent by setting:
979 kern.cam.ada.X.quirks="0x2"
980 in loader.conf. If the drive requires the 4k sector quirk, set the
984 The FAST_DEPEND build option has been removed and its functionality is
985 now the one true way. The old mkdep(1) style of 'make depend' has
986 been removed. See 20160311 for further details.
989 Resource range types have grown from unsigned long to uintmax_t. All
990 drivers, and anything using libdevinfo, need to be recompiled.
993 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
994 builds. It no longer runs mkdep(1) during 'make depend', and the
995 'make depend' stage can safely be skipped now as it is auto ran
996 when building 'make all' and will generate all SRCS and DPSRCS before
997 building anything else. Dependencies are gathered at compile time with
998 -MF flags kept in separate .depend files per object file. Users should
999 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1000 stale .depend files.
1003 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1004 kernel modules. Therefore, if you load any kernel modules at boot time,
1005 please install the boot loaders after you install the kernel, but before
1009 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1010 make installkernel KERNCONF=YOUR_KERNEL_HERE
1011 make -C sys/boot install
1012 <reboot in single user>
1014 Then follow the usual steps, described in the General Notes section,
1018 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1019 see the 20141231 entry below for information about prerequisites and
1020 upgrading, if you are not already using clang 3.5.0 or higher.
1023 The AIO subsystem is now a standard part of the kernel. The
1024 VFS_AIO kernel option and aio.ko kernel module have been removed.
1025 Due to stability concerns, asynchronous I/O requests are only
1026 permitted on sockets and raw disks by default. To enable
1027 asynchronous I/O requests on all file types, set the
1028 vfs.aio.enable_unsafe sysctl to a non-zero value.
1031 The ELF object manipulation tool objcopy is now provided by the
1032 ELF Tool Chain project rather than by GNU binutils. It should be a
1033 drop-in replacement, with the addition of arm64 support. The
1034 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1035 to obtain the GNU version if necessary.
1038 Building ZFS pools on top of zvols is prohibited by default. That
1039 feature has never worked safely; it's always been prone to deadlocks.
1040 Using a zvol as the backing store for a VM guest's virtual disk will
1041 still work, even if the guest is using ZFS. Legacy behavior can be
1042 restored by setting vfs.zfs.vol.recursive=1.
1045 The NONE and HPN patches has been removed from OpenSSH. They are
1046 still available in the security/openssh-portable port.
1049 With the addition of ypldap(8), a new _ypldap user is now required
1050 during installworld. "mergemaster -p" can be used to add the user
1051 prior to installworld, as documented in the handbook.
1054 The tftp loader (pxeboot) now uses the option root-path directive. As a
1055 consequence it no longer looks for a pxeboot.4th file on the tftp
1056 server. Instead it uses the regular /boot infrastructure as with the
1060 The code to start recording plug and play data into the modules has
1061 been committed. While the old tools will properly build a new kernel,
1062 a number of warnings about "unknown metadata record 4" will be produced
1063 for an older kldxref. To avoid such warnings, make sure to rebuild
1064 the kernel toolchain (or world). Make sure that you have r292078 or
1065 later when trying to build 292077 or later before rebuilding.
1068 Debug data files are now built by default with 'make buildworld' and
1069 installed with 'make installworld'. This facilitates debugging but
1070 requires more disk space both during the build and for the installed
1071 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1075 r291527 changed the internal interface between the nfsd.ko and
1076 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1077 __FreeBSD_version has been bumped because of this.
1080 Add support for unicode collation strings leads to a change of
1081 order of files listed by ls(1) for example. To get back to the old
1082 behaviour, set LC_COLLATE environment variable to "C".
1084 Databases administrators will need to reindex their databases given
1085 collation results will be different.
1087 Due to a bug in install(1) it is recommended to remove the ancient
1088 locales before running make installworld.
1090 rm -rf /usr/share/locale/*
1093 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1094 libcrypto.so.7 or libssl.so.7 must be recompiled.
1097 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1098 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1099 should be replaced with isp_2400 and isp_2500 modules respectively.
1102 The build previously allowed using 'make -n' to not recurse into
1103 sub-directories while showing what commands would be executed, and
1104 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1105 and 'make -N' will not.
1108 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1109 and etcupdate will now use this file. A custom sendmail.cf is now
1110 updated via this mechanism rather than via installworld. If you had
1111 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1112 want to remove the exclusion or change it to "always install".
1113 /etc/mail/sendmail.cf is now managed the same way regardless of
1114 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1115 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1118 Compatibility shims for legacy ATA device names have been removed.
1119 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1120 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1121 environment variables, /dev/ad* and /dev/ar* symbolic links.
1124 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1125 Please see the 20141231 entry below for information about prerequisites
1126 and upgrading, if you are not already using clang 3.5.0 or higher.
1129 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1130 and renamed from .symbols to .debug. This reduces the size requirements
1131 on the boot partition or file system and provides consistency with
1132 userland debug files.
1134 When using the supported kernel installation method the
1135 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1136 as is done with /boot/kernel.
1138 Developers wishing to maintain the historical behavior of installing
1139 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1142 The wireless drivers had undergone changes that remove the 'parent
1143 interface' from the ifconfig -l output. The rc.d network scripts
1144 used to check presence of a parent interface in the list, so old
1145 scripts would fail to start wireless networking. Thus, etcupdate(3)
1146 or mergemaster(8) run is required after kernel update, to update your
1147 rc.d scripts in /etc.
1150 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1151 These configurations are now automatically interpreted as
1152 'scrub fragment reassemble'.
1155 Kernel-loadable modules for the random(4) device are back. To use
1156 them, the kernel must have
1159 options RANDOM_LOADABLE
1161 kldload(8) can then be used to load random_fortuna.ko
1162 or random_yarrow.ko. Please note that due to the indirect
1163 function calls that the loadable modules need to provide,
1164 the build-in variants will be slightly more efficient.
1166 The random(4) kernel option RANDOM_DUMMY has been retired due to
1167 unpopularity. It was not all that useful anyway.
1170 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1171 Control over building the ELF Tool Chain tools is now provided by
1172 the WITHOUT_TOOLCHAIN knob.
1175 The polarity of Pulse Per Second (PPS) capture events with the
1176 uart(4) driver has been corrected. Prior to this change the PPS
1177 "assert" event corresponded to the trailing edge of a positive PPS
1178 pulse and the "clear" event was the leading edge of the next pulse.
1180 As the width of a PPS pulse in a typical GPS receiver is on the
1181 order of 1 millisecond, most users will not notice any significant
1182 difference with this change.
1184 Anyone who has compensated for the historical polarity reversal by
1185 configuring a negative offset equal to the pulse width will need to
1186 remove that workaround.
1189 The default group assigned to /dev/dri entries has been changed
1190 from 'wheel' to 'video' with the id of '44'. If you want to have
1191 access to the dri devices please add yourself to the video group
1194 # pw groupmod video -m $USER
1197 The menu.rc and loader.rc files will now be replaced during
1198 upgrades. Please migrate local changes to menu.rc.local and
1199 loader.rc.local instead.
1202 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1203 strings and strip have been removed. The src.conf(5) knob
1204 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1207 As ZFS requires more kernel stack pages than is the default on some
1208 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1209 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1211 Please consider using 'options KSTACK_PAGES=X' where X is greater
1212 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1215 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1216 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1217 default, i.e., they will not contain "::". For example, instead
1218 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1219 to have a more specific match, such as different map entries for
1220 IPv6:0:0 vs IPv6:0. This change requires that configuration
1221 data (including maps, files, classes, custom ruleset, etc.) must
1222 use the same format, so make certain such configuration data is
1223 upgrading. As a very simple check search for patterns like
1224 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1225 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1226 the cf option UseCompressedIPv6Addresses.
1229 The default kernel entropy-processing algorithm is now
1230 Fortuna, replacing Yarrow.
1232 Assuming you have 'device random' in your kernel config
1233 file, the configurations allow a kernel option to override
1234 this default. You may choose *ONE* of:
1236 options RANDOM_YARROW # Legacy /dev/random algorithm.
1237 options RANDOM_DUMMY # Blocking-only driver.
1239 If you have neither, you get Fortuna. For most people,
1240 read no further, Fortuna will give a /dev/random that works
1241 like it always used to, and the difference will be irrelevant.
1243 If you remove 'device random', you get *NO* kernel-processed
1244 entropy at all. This may be acceptable to folks building
1245 embedded systems, but has complications. Carry on reading,
1246 and it is assumed you know what you need.
1248 *PLEASE* read random(4) and random(9) if you are in the
1249 habit of tweaking kernel configs, and/or if you are a member
1250 of the embedded community, wanting specific and not-usual
1251 behaviour from your security subsystems.
1253 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1254 random', you will NOT have a functioning /dev/random, and
1255 many cryptographic features will not work, including SSH.
1256 You may also find strange behaviour from the random(3) set
1257 of library functions, in particular sranddev(3), srandomdev(3)
1258 and arc4random(3). The reason for this is that the KERN_ARND
1259 sysctl only returns entropy if it thinks it has some to
1260 share, and with RANDOM_DUMMY or no 'device random' this
1264 An additional fix for the issue described in the 20150614 sendmail
1265 entry below has been committed in revision 284717.
1268 FreeBSD's old make (fmake) has been removed from the system. It is
1269 available as the devel/fmake port or via pkg install fmake.
1272 The fix for the issue described in the 20150614 sendmail entry
1273 below has been committed in revision 284436. The work
1274 around described in that entry is no longer needed unless the
1275 default setting is overridden by a confDH_PARAMETERS configuration
1276 setting of '5' or pointing to a 512 bit DH parameter file.
1279 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1280 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1281 and devel/kyua to version 0.20+ and adjust any calling code to work
1282 with Kyuafile and kyua.
1285 The import of openssl to address the FreeBSD-SA-15:10.openssl
1286 security advisory includes a change which rejects handshakes
1287 with DH parameters below 768 bits. sendmail releases prior
1288 to 8.15.2 (not yet released), defaulted to a 512 bit
1289 DH parameter setting for client connections. To work around
1290 this interoperability, sendmail can be configured to use a
1291 2048 bit DH parameter by:
1293 1. Edit /etc/mail/`hostname`.mc
1294 2. If a setting for confDH_PARAMETERS does not exist or
1295 exists and is set to a string beginning with '5',
1296 replace it with '2'.
1297 3. If a setting for confDH_PARAMETERS exists and is set to
1298 a file path, create a new file with:
1299 openssl dhparam -out /path/to/file 2048
1300 4. Rebuild the .cf file:
1301 cd /etc/mail/; make; make install
1302 5. Restart sendmail:
1303 cd /etc/mail/; make restart
1305 A sendmail patch is coming, at which time this file will be
1309 Generation of legacy formatted entries have been disabled by default
1310 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1311 entries were converted to use the new format by default when the new,
1312 machine independent format have been added and supported since FreeBSD
1315 Please see the pwd_mkdb(8) manual page for further details.
1318 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1319 20141231 entry below for information about prerequisites and upgrading,
1320 if you are not already using 3.5.0 or higher.
1323 TI platform code switched to using vendor DTS files and this update
1324 may break existing systems running on Beaglebone, Beaglebone Black,
1327 - dtb files should be regenerated/reinstalled. Filenames are the
1328 same but content is different now
1329 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1330 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1331 addressing scheme is now pin 25 on /dev/gpioc3.
1332 - Pandaboard: /etc/ttys should be updated, serial console device is
1333 now /dev/ttyu2, not /dev/ttyu0
1336 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1337 If you need the GNU extension from groff soelim(1), install groff
1338 from package: pkg install groff, or via ports: textproc/groff.
1341 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1342 defined in symlink(7); previously symlinks were silently ignored.
1345 The const qualifier has been removed from iconv(3) to comply with
1346 POSIX. The ports tree is aware of this from r384038 onwards.
1349 Libraries specified by LIBADD in Makefiles must have a corresponding
1350 DPADD_<lib> variable to ensure correct dependencies. This is now
1351 enforced in src.libnames.mk.
1354 From legacy ata(4) driver was removed support for SATA controllers
1355 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1356 Kernel modules ataahci and ataadaptec were removed completely,
1357 replaced by ahci and mvs modules respectively.
1360 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1361 the 20141231 entry below for information about prerequisites and
1362 upgrading, if you are not already using 3.5.0 or higher.
1365 The 32-bit PowerPC kernel has been changed to a position-independent
1366 executable. This can only be booted with a version of loader(8)
1367 newer than January 31, 2015, so make sure to update both world and
1368 kernel before rebooting.
1371 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1372 but before r278950, the RNG was not seeded properly. Immediately
1373 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1374 ssh keys or openssl keys) that were generated w/ a kernel from that
1375 range. This does not affect programs that directly used /dev/random
1376 or /dev/urandom. All userland uses of arc4random(3) are affected.
1379 The autofs(4) ABI was changed in order to restore binary compatibility
1380 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1381 with the new kernel.
1384 The powerpc64 kernel has been changed to a position-independent
1385 executable. This can only be booted with a new version of loader(8),
1386 so make sure to update both world and kernel before rebooting.
1389 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1390 only release, no new features have been added. Please see the 20141231
1391 entry below for information about prerequisites and upgrading, if you
1392 are not already using 3.5.0.
1395 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1396 taken from the ELF Tool Chain project rather than GNU binutils. They
1397 should be drop-in replacements, with the addition of arm64 support.
1398 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1399 binutils tools, if necessary. See 20150805 for updated information.
1402 The default Unbound configuration now enables remote control
1403 using a local socket. Users who have already enabled the
1404 local_unbound service should regenerate their configuration
1405 by running "service local_unbound setup" as root.
1408 The GNU texinfo and GNU info pages have been removed.
1409 To be able to view GNU info pages please install texinfo from ports.
1412 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1414 As of this release, a prerequisite for building clang, llvm and lldb is
1415 a C++11 capable compiler and C++11 standard library. This means that to
1416 be able to successfully build the cross-tools stage of buildworld, with
1417 clang as the bootstrap compiler, your system compiler or cross compiler
1418 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1419 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1422 On any standard FreeBSD 10.x or 11.x installation, where clang and
1423 libc++ are on by default (that is, on x86 or arm), this should work out
1426 On 9.x installations where clang is enabled by default, e.g. on x86 and
1427 powerpc, libc++ will not be enabled by default, so libc++ should be
1428 built (with clang) and installed first. If both clang and libc++ are
1429 missing, build clang first, then use it to build libc++.
1431 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1432 the instructions for 9.x above.
1434 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1435 default, and do not build clang.
1437 Many embedded systems are resource constrained, and will not be able to
1438 build clang in a reasonable time, or in some cases at all. In those
1439 cases, cross building bootable systems on amd64 is a workaround.
1441 This new version of clang introduces a number of new warnings, of which
1442 the following are most likely to appear:
1446 This warns in two cases, for both C and C++:
1447 * When the code is trying to take the absolute value of an unsigned
1448 quantity, which is effectively a no-op, and almost never what was
1449 intended. The code should be fixed, if at all possible. If you are
1450 sure that the unsigned quantity can be safely cast to signed, without
1451 loss of information or undefined behavior, you can add an explicit
1452 cast, or disable the warning.
1454 * When the code is trying to take an absolute value, but the called
1455 abs() variant is for the wrong type, which can lead to truncation.
1456 If you want to disable the warning instead of fixing the code, please
1457 make sure that truncation will not occur, or it might lead to unwanted
1460 -Wtautological-undefined-compare and
1461 -Wundefined-bool-conversion
1463 These warn when C++ code is trying to compare 'this' against NULL, while
1464 'this' should never be NULL in well-defined C++ code. However, there is
1465 some legacy (pre C++11) code out there, which actively abuses this
1466 feature, which was less strictly defined in previous C++ versions.
1468 Squid and openjdk do this, for example. The warning can be turned off
1469 for C++98 and earlier, but compiling the code in C++11 mode might result
1470 in unexpected behavior; for example, the parts of the program that are
1471 unreachable could be optimized away.
1474 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1475 kernel sources have been removed. The .h files remain, since some
1476 utilities include them. This will need to be fixed later.
1477 If "mount -t oldnfs ..." is attempted, it will fail.
1478 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1479 the utilities will report errors.
1482 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1483 directories to top level SUBDIR variable when their parent
1484 directory is included in LOCAL_DIRS. Users with build systems with
1485 such hierarchies and without SUBDIR entries in the parent
1486 directory Makefiles should add them or add the directories to
1490 faith(4) and faithd(8) have been removed from the base system. Faith
1491 has been obsolete for a very long time.
1494 vt(4), the new console driver, is enabled by default. It brings
1495 support for Unicode and double-width characters, as well as
1496 support for UEFI and integration with the KMS kernel video
1499 You may need to update your console settings in /etc/rc.conf,
1500 most probably the keymap. During boot, /etc/rc.d/syscons will
1501 indicate what you need to do.
1503 vt(4) still has issues and lacks some features compared to
1504 syscons(4). See the wiki for up-to-date information:
1505 https://wiki.freebsd.org/Newcons
1507 If you want to keep using syscons(4), you can do so by adding
1508 the following line to /boot/loader.conf:
1512 pjdfstest has been integrated into kyua as an opt-in test suite.
1513 Please see share/doc/pjdfstest/README for more details on how to
1517 gperf has been removed from the base system for architectures
1518 that use clang. Ports that require gperf will obtain it from the
1522 pjdfstest has been moved from tools/regression/pjdfstest to
1526 At svn r271982, The default linux compat kernel ABI has been adjusted
1527 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1528 update. If you wish to continue using the linux-f10 compat ports,
1529 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1530 encouraged to update their linux-compat packages to linux-c6 during
1531 their next update cycle.
1534 The ofwfb driver, used to provide a graphics console on PowerPC when
1535 using vt(4), no longer allows mmap() of all physical memory. This
1536 will prevent Xorg on PowerPC with some ATI graphics cards from
1537 initializing properly unless x11-servers/xorg-server is updated to
1541 The xdev targets have been converted to using TARGET and
1542 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1545 The default unbound configuration has been modified to address
1546 issues with reverse lookups on networks that use private
1547 address ranges. If you use the local_unbound service, run
1548 "service local_unbound setup" as root to regenerate your
1549 configuration, then "service local_unbound reload" to load the
1553 The GNU texinfo and GNU info pages are not built and installed
1554 anymore, WITH_INFO knob has been added to allow to built and install
1556 UPDATE: see 20150102 entry on texinfo's removal
1559 The GNU readline library is now an INTERNALLIB - that is, it is
1560 statically linked into consumers (GDB and variants) in the base
1561 system, and the shared library is no longer installed. The
1562 devel/readline port is available for third party software that
1566 The Itanium architecture (ia64) has been removed from the list of
1567 known architectures. This is the first step in the removal of the
1571 Commit r268115 has added NFSv4.1 server support, merged from
1572 projects/nfsv4.1-server. Since this includes changes to the
1573 internal interfaces between the NFS related modules, a full
1574 build of the kernel and modules will be necessary.
1575 __FreeBSD_version has been bumped.
1578 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1579 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1580 which differs from the behaviour controlled by this knob.)
1583 Maximal length of the serial number in CTL was increased from 16 to
1584 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1585 and ctld, need to be rebuilt to work with a new kernel.
1588 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1589 1 respectively to match the upstream numbers. They were out of
1590 sync because, when they were originally added to FreeBSD, the
1591 upstream versions were not respected. These libraries are private
1592 and not yet built by default, so renumbering them should be a
1593 non-issue. However, unclean source trees will yield broken test
1594 programs once the operator executes "make delete-old-libs" after a
1595 "make installworld".
1597 Additionally, the atf-sh binary was made private by moving it into
1598 /usr/libexec/. Already-built shell test programs will keep the
1599 path to the old binary so they will break after "make delete-old"
1602 If you are using WITH_TESTS=yes (not the default), wipe the object
1603 tree and rebuild from scratch to prevent spurious test failures.
1604 This is only needed once: the misnumbered libraries and misplaced
1605 binaries have been added to OptionalObsoleteFiles.inc so they will
1606 be removed during a clean upgrade.
1609 Clang and llvm have been upgraded to 3.4.1 release.
1612 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1613 be removed to avoid issues in the future (and has been added to
1617 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1618 past, it affected all builds that used the bsd.*.mk files. The old
1619 behavior was a bug, but people may have relied upon it. To get this
1620 behavior back, you can .include /etc/src.conf from /etc/make.conf
1621 (which is still global and isn't changed). This also changes the
1622 behavior of incremental builds inside the tree of individual
1623 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1624 Although this has survived make universe and some upgrade scenarios,
1625 other upgrade scenarios may have broken. At least one form of
1626 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1627 as well... In cases where MAKESYSPATH isn't working with this
1628 setting, you'll need to set it to the full path to your tree.
1630 One side effect of all this cleaning up is that bsd.compiler.mk
1631 is no longer implicitly included by bsd.own.mk. If you wish to
1632 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1636 The lindev device has been removed since /dev/full has been made a
1637 standard device. __FreeBSD_version has been bumped.
1640 The knob WITHOUT_VI was added to the base system, which controls
1641 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1642 in order to reorder files share/termcap and didn't build ex(1) as a
1643 build tool, so building/installing with WITH_VI is highly advised for
1644 build hosts for older releases.
1646 This issue has been fixed in stable/9 and stable/10 in r277022 and
1647 r276991, respectively.
1650 The YES_HESIOD knob has been removed. It has been obsolete for
1651 a decade. Please move to using WITH_HESIOD instead or your builds
1652 will silently lack HESIOD.
1655 The uart(4) driver has been changed with respect to its handling
1656 of the low-level console. Previously the uart(4) driver prevented
1657 any process from changing the baudrate or the CLOCAL and HUPCL
1658 control flags. By removing the restrictions, operators can make
1659 changes to the serial console port without having to reboot.
1660 However, when getty(8) is started on the serial device that is
1661 associated with the low-level console, a misconfigured terminal
1662 line in /etc/ttys will now have a real impact.
1663 Before upgrading the kernel, make sure that /etc/ttys has the
1664 serial console device configured as 3wire without baudrate to
1665 preserve the previous behaviour. E.g:
1666 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1669 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1670 to improve performance. To re-enable it, if needed, run rpcbind
1671 with command line option -W.
1674 Switched back to the GPL dtc compiler due to updates in the upstream
1675 dts files not being supported by the BSDL dtc compiler. You will need
1676 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1677 may result while building dtb files during a kernel build if you fail
1678 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1681 Clang and llvm have been upgraded to 3.4 release.
1684 The nve(4) driver has been removed. Please use the nfe(4) driver
1685 for NVIDIA nForce MCP Ethernet adapters instead.
1688 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1689 This could cause certain C++ applications using shared libraries built
1690 against the previous version of libc++ to crash. The incompatibility
1691 has now been fixed, but any C++ applications or shared libraries built
1692 between r261283 and r261801 should be recompiled.
1695 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1696 capability mode support. Please note that enabling the feature in
1697 kernel is still highly recommended.
1700 OpenSSH is now built with sandbox support, and will use sandbox as
1701 the default privilege separation method. This requires Capsicum
1702 capability mode support in kernel.
1705 The libelf and libdwarf libraries have been updated to newer
1706 versions from upstream. Shared library version numbers for
1707 these two libraries were bumped. Any ports or binaries
1708 requiring these two libraries should be recompiled.
1709 __FreeBSD_version is bumped to 1100006.
1712 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1713 instead of providing an explicit one, this would prevent such
1714 Makefile from providing its own Kyuafile in the future during
1715 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1716 intervention is needed to clean an objdir if you use NO_CLEAN:
1717 # find /usr/obj -name Kyuafile | xargs rm -f
1720 The behavior of gss_pseudo_random() for the krb5 mechanism
1721 has changed, for applications requesting a longer random string
1722 than produced by the underlying enctype's pseudo-random() function.
1723 In particular, the random string produced from a session key of
1724 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1725 be different at the 17th octet and later, after this change.
1726 The counter used in the PRF+ construction is now encoded as a
1727 big-endian integer in accordance with RFC 4402.
1728 __FreeBSD_version is bumped to 1100004.
1731 The WITHOUT_ATF build knob has been removed and its functionality
1732 has been subsumed into the more generic WITHOUT_TESTS. If you were
1733 using the former to disable the build of the ATF libraries, you
1734 should change your settings to use the latter.
1737 The default version of mtree is nmtree which is obtained from
1738 NetBSD. The output is generally the same, but may vary
1739 slightly. If you found you need identical output adding
1740 "-F freebsd9" to the command line should do the trick. For the
1741 time being, the old mtree is available as fmtree.
1744 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1745 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1746 1.1.4_8 and verify bsdyml not linked in, before running "make
1748 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1750 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1753 The stable/10 branch has been created in subversion from head
1760 Avoid using make -j when upgrading. While generally safe, there are
1761 sometimes problems using -j to upgrade. If your upgrade fails with
1762 -j, please try again without -j. From time to time in the past there
1763 have been problems using -j with buildworld and/or installworld. This
1764 is especially true when upgrading between "distant" versions (eg one
1765 that cross a major release boundary or several minor releases, or when
1766 several months have passed on the -current branch).
1768 Sometimes, obscure build problems are the result of environment
1769 poisoning. This can happen because the make utility reads its
1770 environment when searching for values for global variables. To run
1771 your build attempts in an "environmental clean room", prefix all make
1772 commands with 'env -i '. See the env(1) manual page for more details.
1774 When upgrading from one major version to another it is generally best to
1775 upgrade to the latest code in the currently installed branch first, then
1776 do an upgrade to the new branch. This is the best-tested upgrade path,
1777 and has the highest probability of being successful. Please try this
1778 approach if you encounter problems with a major version upgrade. Since
1779 the stable 4.x branch point, one has generally been able to upgrade from
1780 anywhere in the most recent stable branch to head / current (or even the
1781 last couple of stable branches). See the top of this file when there's
1784 When upgrading a live system, having a root shell around before
1785 installing anything can help undo problems. Not having a root shell
1786 around can lead to problems if pam has changed too much from your
1787 starting point to allow continued authentication after the upgrade.
1789 This file should be read as a log of events. When a later event changes
1790 information of a prior event, the prior event should not be deleted.
1791 Instead, a pointer to the entry with the new information should be
1792 placed in the old entry. Readers of this file should also sanity check
1793 older entries before relying on them blindly. Authors of new entries
1794 should write them with this in mind.
1798 When upgrading the boot ZFS pool to a new version, always follow
1801 1.) recompile and reinstall the ZFS boot loader and boot block
1802 (this is part of "make buildworld" and "make installworld")
1804 2.) update the ZFS boot block on your boot drive
1806 The following example updates the ZFS boot block on the first
1807 partition (freebsd-boot) of a GPT partitioned drive ada0:
1808 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1810 Non-boot pools do not need these updates.
1814 If you are updating from a prior version of FreeBSD (even one just
1815 a few days old), you should follow this procedure. It is the most
1816 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1818 make kernel-toolchain
1819 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1820 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1822 To test a kernel once
1823 ---------------------
1824 If you just want to boot a kernel once (because you are not sure
1825 if it works, or if you want to boot a known bad kernel to provide
1826 debugging information) run
1827 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1828 nextboot -k testkernel
1830 To rebuild everything and install it on the current system.
1831 -----------------------------------------------------------
1832 # Note: sometimes if you are running current you gotta do more than
1833 # is listed here if you are upgrading from a really old current.
1835 <make sure you have good level 0 dumps>
1837 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1838 make installkernel KERNCONF=YOUR_KERNEL_HERE
1840 <reboot in single user> [3]
1847 To cross-install current onto a separate partition
1848 --------------------------------------------------
1849 # In this approach we use a separate partition to hold
1850 # current's root, 'usr', and 'var' directories. A partition
1851 # holding "/", "/usr" and "/var" should be about 2GB in
1854 <make sure you have good level 0 dumps>
1857 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1858 <maybe newfs current's root partition>
1859 <mount current's root partition on directory ${CURRENT_ROOT}>
1860 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1861 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1862 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1863 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1864 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1865 <reboot into current>
1866 <do a "native" rebuild/install as described in the previous section>
1867 <maybe install compatibility libraries from ports/misc/compat*>
1871 To upgrade in-place from stable to current
1872 ----------------------------------------------
1873 <make sure you have good level 0 dumps>
1875 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1876 make installkernel KERNCONF=YOUR_KERNEL_HERE
1878 <reboot in single user> [3]
1885 Make sure that you've read the UPDATING file to understand the
1886 tweaks to various things you need. At this point in the life
1887 cycle of current, things change often and you are on your own
1888 to cope. The defaults can also change, so please read ALL of
1889 the UPDATING entries.
1891 Also, if you are tracking -current, you must be subscribed to
1892 freebsd-current@freebsd.org. Make sure that before you update
1893 your sources that you have read and understood all the recent
1894 messages there. If in doubt, please track -stable which has
1895 much fewer pitfalls.
1897 [1] If you have third party modules, such as vmware, you
1898 should disable them at this point so they don't crash your
1901 [3] From the bootblocks, boot -s, and then do
1906 adjkerntz -i # if CMOS is wall time
1907 Also, when doing a major release upgrade, it is required that
1908 you boot into single user mode to do the installworld.
1910 [4] Note: This step is non-optional. Failure to do this step
1911 can result in a significant reduction in the functionality of the
1912 system. Attempting to do it by hand is not recommended and those
1913 that pursue this avenue should read this file carefully, as well
1914 as the archives of freebsd-current and freebsd-hackers mailing lists
1915 for potential gotchas. The -U option is also useful to consider.
1916 See mergemaster(8) for more information.
1918 [5] Usually this step is a no-op. However, from time to time
1919 you may need to do this if you get unknown user in the following
1920 step. It never hurts to do it all the time. You may need to
1921 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1922 install) after the buildworld before this step if you last updated
1923 from current before 20130425 or from -stable before 20130430.
1925 [6] This only deletes old files and directories. Old libraries
1926 can be deleted by "make delete-old-libs", but you have to make
1927 sure that no program is using those libraries anymore.
1929 [8] The new kernel must be able to run existing binaries used by
1930 an installworld. When upgrading across major versions, the new
1931 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1932 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1933 binaries). Failure to do so may leave you with a system that is
1934 hard to boot to recover. A GENERIC kernel will include suitable
1935 compatibility options to run binaries from older branches.
1937 Make sure that you merge any new devices from GENERIC since the
1938 last time you updated your kernel config file.
1940 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1941 "?=" instead of the "=" assignment operator, so that buildworld can
1942 override the CPUTYPE if it needs to.
1944 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1945 not on the command line, or in /etc/make.conf. buildworld will
1946 warn if it is improperly defined.
1949 This file contains a list, in reverse chronological order, of major
1950 breakages in tracking -current. It is not guaranteed to be a complete
1951 list of such breakages, and only contains entries since September 23, 2011.
1952 If you need to see UPDATING entries from before that date, you will need
1953 to fetch an UPDATING file from an older FreeBSD release.
1955 Copyright information:
1957 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1959 Redistribution, publication, translation and use, with or without
1960 modification, in full or in part, in any form or format of this
1961 document are permitted without further permission from the author.
1963 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1964 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1965 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1966 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1967 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1968 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1969 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1970 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1971 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1972 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1973 POSSIBILITY OF SUCH DAMAGE.
1975 Contact Warner Losh if you have any questions about your use of