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.
20 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
21 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
22 been removed from mount_fusefs(8). You can safely remove them from
23 your scripts, because they had no effect.
25 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
26 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
27 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
28 sysctls have been removed. If you felt the need to set any of them to
29 a non-default value, please tell asomers@FreeBSD.org why.
32 The fuse(4) module has been renamed to fusefs(4) for consistency with
33 other filesystems. You should update any kld_load="fuse" entries in
34 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
35 "options FUSE" enties in kernel config files.
38 Default permissions on the /var/account/acct file (and copies of it
39 rotated by periodic daily scripts) are changed from 0644 to 0640
40 because the file contains sensitive information that should not be
41 world-readable. If the /var/account directory must be created by
42 rc.d/accounting, the mode used is now 0750. Admins who use the
43 accounting feature are encouraged to change the mode of an existing
44 /var/account directory to 0750 or 0700.
47 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
48 been upgraded to 8.0.1. Please see the 20141231 entry below for
49 information about prerequisites and upgrading, if you are not already
50 using clang 3.5.0 or higher.
53 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
54 functionality needed for the RETPOLINE option should work properly
55 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
58 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
59 8.0.0. Please see the 20141231 entry below for information about
60 prerequisites and upgrading, if you are not already using clang 3.5.0
64 The RETPOLINE option produces non-functional ifunc-using binaries
65 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
66 Once Clang 8 is merged it may be enabled again.
69 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
70 7.0.1. Please see the 20141231 entry below for information about
71 prerequisites and upgrading, if you are not already using clang 3.5.0
75 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
76 compiled into your custom kernel, add 'device xz' statement to the
80 Iflib is no longer unconditionally compiled into the kernel. Drivers
81 using iflib and statically compiled into the kernel, now require
82 the 'device iflib' config option. For the same drivers loaded as
83 modules on kernels not having 'device iflib', the iflib.ko module
84 is loaded automatically.
87 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
88 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
89 servers that have vfs.nfsd.nfs_privport set will only allow mounts
90 from clients using a reserved port#. Since both the FreeBSD and Linux
91 NFSv4 clients use reserved port#s by default, this should not affect
95 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
96 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
97 it produces broken binaries when ifuncs are in use. Users needing
98 GNU ld should install the binutils port or package.
101 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
102 has been converted to a port (misc/ctm) and will be removed from
103 FreeBSD-13. A depreciation warning will be printed to stderr by
104 the ctm command, but the functionality will remain in base for all
108 The stable/12 branch has been created in subversion from head
112 Ports for the DRM modules have been simplified. Now, amd64 users should
113 just install the drm-kmod port. All others should install
116 Graphics hardware that's newer than about 2010 usually works with
117 drm-kmod. For hardware older than 2013, however, some users will need
118 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
119 than 2008 usually only works in drm-legacy-kmod. The graphics team can
120 only commit to hardware made since 2013 due to the complexity of the
121 market and difficulty to test all the older cards effectively. If you
122 have hardware supported by drm-kmod, you are strongly encouraged to use
123 that as you will get better support.
125 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
126 elsewhere, the drm and drm2 modules will be eliminated from the src base
127 soon (with a limited exception for arm). Please update to the package asap
128 and report any issues to x11@freebsd.org.
130 Generally, anybody using the drm*-kmod packages should add
131 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
132 cross-threading surprises, especially with automatic driver
133 loading from X11 startup. These will become the defaults in 13-current
137 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
138 custom kernel and module loading configuration files must be updated
139 accordingly. Moreover, interfaces previous presented as ixlvN to the
140 system are now exposed as iavfN and network configuration files must
141 be adjusted as necessary.
144 OpenSSL has been updated to version 1.1.1. This update included
145 additional various API changes througout the base system. It is
146 important to rebuild third-party software after upgrading. The value
147 of __FreeBSD_version has been bumped accordingly.
150 The legacy DRM modules and drivers have now been added to the loader's
151 module blacklist, in favor of loading them with kld_list in rc.conf(5).
152 The module blacklist may be overridden with the loader.conf(5)
153 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
157 The cam(4) based nda(4) driver will be used over nvd(4) by default on
158 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
159 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
160 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
164 Reproducible build mode is now on by default, in preparation for
165 FreeBSD 12.0. This eliminates build metadata such as the user,
166 host, and time from the kernel (and uname), unless the working tree
167 corresponds to a modified checkout from a version control system.
168 The previous behavior can be obtained by setting the /etc/src.conf
169 knob WITHOUT_REPRODUCIBLE_BUILD.
172 The Yarrow CSPRNG has been removed from the kernel as it has not been
173 supported by its designers since at least 2003. Fortuna has been the
174 default since FreeBSD-11.
177 devctl freeze/thaw have gone into the tree, the rc scripts have been
178 updated to use them and devmatch has been changed. You should update
179 kernel, userland and rc scripts all at the same time.
182 The default interpreter has been switched from 4th to Lua.
183 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
184 interpreter. If you have custom FORTH code you will need to set
185 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
186 src.conf for the build. This will create default hard links between
187 loader and loader_4th instead of loader and loader_lua, the new default.
188 If you are using UEFI it will create the proper hard link to loader.efi.
190 bhyve uses userboot.so. It remains 4th-only until some issues are solved
191 regarding coexisting with multiple versions of FreeBSD are resolved.
194 ls(1) now respects the COLORTERM environment variable used in other
195 systems and software to indicate that a colored terminal is both
196 supported and desired. If ls(1) is suddenly emitting colors, they may
197 be disabled again by either removing the unwanted COLORTERM from your
198 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
199 may not be observed in a future release.
202 The default pager for most commands has been changed to "less". To
203 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
207 The jedec_ts(4) driver has been removed. A superset of its functionality
208 is available in the jedec_dimm(4) driver, and the manpage for that
209 driver includes migration instructions. If you have "device jedec_ts"
210 in your kernel configuration file, it must be removed.
213 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
214 This should have no effect if the kernel is booted via BIOS/legacy boot.
215 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
216 has a buggy firmware that prevents a successful boot due to use of
220 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
221 support has been removed from the tree. These ports were
222 obsolete and/or known to be broken for many years.
225 loader.efi has been augmented to participate more fully in the
226 UEFI boot manager protocol. loader.efi will now look at the
227 BootXXXX environment variable to determine if a specific kernel
228 or root partition was specified. XXXX is derived from BootCurrent.
229 efibootmgr(8) manages these standard UEFI variables.
232 zfsloader's functionality has now been folded into loader.
233 zfsloader is no longer necessary once you've updated your
234 boot blocks. For a transition period, we will install a
235 hardlink for zfsloader to loader to allow a smooth transition
236 until the boot blocks can be updated (hard link because old
237 zfs boot blocks don't understand symlinks).
240 ARM64 now have efifb support, if you want to have serial console
241 on your arm64 board when an screen is connected and the bootloader
242 setup a frambuffer for us to use, just add :
246 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
247 an screen connected as the firmware will setup a framebuffer are that
248 u-boot will expose as an EFI framebuffer.
251 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
252 or take steps to update /etc/passwd before doing installworld on
253 existing systems. Do not skip the "mergemaster -Fp" step before
254 installworld, as described in the update procedures near the bottom
255 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
256 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
257 the ntp config file contain options that change file/dir locations.
258 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
259 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
260 taking steps to ensure that all required files/dirs are accessible
264 Big endian arm support has been removed.
267 The static environment setup in kernel configs is no longer mutually
268 exclusive with the loader(8) environment by default. In order to
269 restore the previous default behavior of disabling the loader(8)
270 environment if a static environment is present, you must specify
271 loader_env.disabled=1 in the static environment.
274 The ABI of syscalls used by management tools like sockstat and
275 netstat has been broken to allow 32-bit binaries to work on
276 64-bit kernels without modification. These programs will need
277 to match the kernel in order to function. External programs may
278 require minor modifications to accommodate a change of type in
279 structures from pointers to 64-bit virtual addresses.
282 On i386 and amd64 atomics are now inlined. Out of tree modules using
283 atomics will need to be rebuilt.
286 The '%I' format in the kern.corefile sysctl limits the number of
287 core files that a process can generate to the number stored in the
288 debug.ncores sysctl. The '%I' format is replaced by the single digit
289 index. Previously, if all indexes were taken the kernel would overwrite
290 only a core file with the highest index in a filename.
291 Currently the system will create a new core file if there is a free
292 index or if all slots are taken it will overwrite the oldest one.
295 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
296 6.0.1. Please see the 20141231 entry below for information about
297 prerequisites and upgrading, if you are not already using clang 3.5.0
301 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
302 needed to be changed to work with it. This change was made with r335763
303 and requires a mergemaster / etcupdate / etc to update the installed file.
306 r334930 changed the interface between the NFS modules, so they all
307 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
310 As of r334391 lld is the default amd64 system linker; it is installed
311 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
315 The kernel / userland interface for devinfo changed, so you'll
316 need a new kernel and userland as a pair for it to work (rebuilding
317 lib/libdevinfo is all that's required). devinfo and devmatch will
318 not work, but everything else will when there's a mismatch.
321 The on-disk format for hwpmc callchain records has changed to include
322 threadid corresponding to a given record. This changes the field offsets
323 and thus requires that libpmcstat be rebuilt before using a kernel
327 The vxge(4) driver has been removed. This driver was introduced into
328 HEAD one week before the Exar left the Ethernet market and is not
329 known to be used. If you have device vxge in your kernel config file
333 The amd64 kernel now requires a ld that supports ifunc to produce a
334 working kernel, either lld or a newer binutils. lld is built by default
335 on amd64, and the 'buildkernel' target uses it automatically. However,
336 it is not the default linker, so building the kernel the traditional
337 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
338 binutils port/package). lld will soon be default, and this requirement
341 NOTE: As of r334391 lld is the default system linker on amd64, and no
342 workaround is necessary.
345 The nxge(4) driver has been removed. This driver was for PCI-X 10g
346 cards made by s2io/Neterion. The company was aquired by Exar and
347 no longer sells or supports Ethernet products. If you have device
348 nxge in your kernel config file it must be removed.
351 The tz database (tzdb) has been updated to 2018e. This version more
352 correctly models time stamps in time zones with negative DST such as
353 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
354 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
355 time zone abbreviations and the tm_isdst flag.
358 The ixgb(4) driver has been removed. This driver was for an early and
359 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
360 quickly shifted to the long lived ixgbe family. If you have device
361 ixgb in your kernel config file it must be removed.
364 The lmc(4) driver has been removed. This was a WAN interface
365 card that was already reportedly rare in 2003, and had an ambiguous
366 license. If you have device lmc in your kernel config file it must
370 Support for Arcnet networks has been removed. If you have device
371 arcnet or device cm in your kernel config file they must be
375 Support for FDDI networks has been removed. If you have device
376 fddi or device fpa in your kernel config file they must be
380 In addition to supporting RFC 3164 formatted messages, the
381 syslogd(8) service is now capable of parsing RFC 5424 formatted
382 log messages. The main benefit of using RFC 5424 is that clients
383 may now send log messages with timestamps containing year numbers,
384 microseconds and time zone offsets.
386 Similarly, the syslog(3) C library function has been altered to
387 send RFC 5424 formatted messages to the local system logging
388 daemon. On systems using syslogd(8), this change should have no
389 negative impact, as long as syslogd(8) and the C library are
390 updated at the same time. On systems using a different system
391 logging daemon, it may be necessary to make configuration
392 adjustments, depending on the software used.
394 When using syslog-ng, add the 'syslog-protocol' flag to local
395 input sources to enable parsing of RFC 5424 formatted messages:
398 unix-dgram("/var/run/log" flags(syslog-protocol));
401 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
402 of the 'imuxsock' module to let messages be processed by the
403 regular RFC 3164/5424 parsing pipeline:
405 module(load="imuxsock" SysSock.UseSpecialParser="off")
407 Do note that these changes only affect communication between local
408 applications and syslogd(8). The format that syslogd(8) uses to
409 store messages on disk or forward messages to other systems
410 remains unchanged. syslogd(8) still uses RFC 3164 for these
411 purposes. Options to customize this behaviour will be added in the
412 future. Utilities that process log files stored in /var/log are
413 thus expected to continue to function as before.
415 __FreeBSD_version has been incremented to 1200061 to denote this
419 Support for token ring networks has been removed. If you
420 have "device token" in your kernel config you should remove
421 it. No device drivers supported token ring.
424 makefs was modified to be able to tag ISO9660 El Torito boot catalog
425 entries as EFI instead of overloading the i386 tag as done previously.
426 The amd64 mkisoimages.sh script used to build amd64 ISO images for
427 release was updated to use this. This may mean that makefs must be
428 updated before "make cdrom" can be run in the release directory. This
429 should be as simple as:
431 $ cd $SRCDIR/usr.sbin/makefs
432 $ make depend all install
435 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
436 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
437 Co-existance for the transition period will come shortly. Booting is a
438 complex environment and test coverage for Lua-enabled loaders has been
439 thin, so it would be prudent to assume it might not work and make
440 provisions for backup boot methods.
443 devmatch functionality has been turned on in devd. It will automatically
444 load drivers for unattached devices. This may cause unexpected drivers to
445 be loaded. Please report any problems to current@ and imp@freebsd.org.
448 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
449 6.0.0. Please see the 20141231 entry below for information about
450 prerequisites and upgrading, if you are not already using clang 3.5.0
454 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
455 This means it is used to link the kernel and userland libraries and
456 executables, but is not yet installed as /usr/bin/ld by default.
458 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
459 WITHOUT_LLD_BOOTSTRAP=yes
462 On i386, pmtimer has been removed. Its functionality has been folded
463 into apm. It was a no-op on ACPI in current for a while now (but was still
464 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
465 from kernel config files.
468 The use of RSS hash from the network card aka flowid has been
469 disabled by default for lagg(4) as it's currently incompatible with
470 the lacp and loadbalance protocols.
472 This can be re-enabled by setting the following in loader.conf:
473 net.link.lagg.default_use_flowid="1"
476 The SW_WATCHDOG option is no longer necessary to enable the
477 hardclock-based software watchdog if no hardware watchdog is
478 configured. As before, SW_WATCHDOG will cause the software
479 watchdog to be enabled even if a hardware watchdog is configured.
482 r326887 fixes the issue described in the 20171214 UPDATING entry.
483 r326888 flips the switch back to building GELI support always.
486 r362593 broke ZFS + GELI support for reasons unknown. However,
487 it also broke ZFS support generally, so GELI has been turned off
488 by default as the lesser evil in r326857. If you boot off ZFS and/or
489 GELI, it might not be a good time to update.
492 PowerPC users must update loader(8) by rebuilding world before
493 installing a new kernel, as the protocol connecting them has
494 changed. Without the update, loader metadata will not be passed
495 successfully to the kernel and users will have to enter their
496 root partition at the kernel mountroot prompt to continue booting.
497 Newer versions of loader can boot old kernels without issue.
500 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
501 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
502 to WITH/OUT_LOADER_GELI.
505 The naive and non-compliant support of posix_fallocate(2) in ZFS
506 has been removed as of r325320. The system call now returns EINVAL
507 when used on a ZFS file. Although the new behavior complies with the
508 standard, some consumers are not prepared to cope with it.
509 One known victim is lld prior to r325420.
512 Building in a FreeBSD src checkout will automatically create object
513 directories now rather than store files in the current directory if
514 'make obj' was not ran. Calling 'make obj' is no longer necessary.
515 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
516 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
520 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
521 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
522 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
523 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
524 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
525 The UNIFIED_OBJDIR option is a transitional feature that will be
526 removed for 12.0 release; please migrate to the new format for any
527 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
528 than hardcoding paths.
531 The native-xtools target no longer installs the files by default to the
532 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
533 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
536 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
537 options are changing from controlling the build if defined / undefined
538 to controlling the build with explicit 'yes' or 'no' values. They will
539 shift to WITH/WITHOUT options to match other options in the system.
542 libstand has turned into a private library for sys/boot use only.
543 It is no longer supported as a public interface outside of sys/boot.
546 The arm port has split armv6 into armv6 and armv7. armv7 is now
547 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
548 and are running a kernel from before r324363, you will need to add
549 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
552 When building multiple kernels using KERNCONF, non-existent KERNCONF
553 files will produce an error and buildkernel will fail. Previously
554 missing KERNCONF files silently failed giving no indication as to
555 why, only to subsequently discover during installkernel that the
556 desired kernel was never built in the first place.
559 The default serial number format for CTL LUNs has changed. This will
560 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
561 or iSCSI clients care about their LUNs' serial numbers. Users who
562 require serial number stability should hardcode serial numbers in
566 For 32-bit arm compiled for hard-float support, soft-floating point
567 binaries now always get their shared libraries from
568 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
569 /usr/libsoft also existed). Only users with a hard-float ld.so, but
570 soft-float everything else should be affected.
573 The geli password typed at boot is now hidden. To restore the previous
574 behavior, see geli(8) for configuration options.
577 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
578 sysctl values. Minor nit, but requires a rebuild of both world/kernel
582 "make check" behavior (made in ^/head@r295380) has been changed to
583 execute from a limited sandbox, as opposed to executing from
587 - The "beforecheck" and "aftercheck" targets are now specified.
588 - ${CHECKDIR} (added in commit noted above) has been removed.
589 - Legacy behavior can be enabled by setting
590 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
592 If the limited sandbox mode is enabled, "make check" will execute
593 "make distribution", then install, execute the tests, and clean up the
594 sandbox if successful.
596 The "make distribution" and "make install" targets are typically run as
597 root to set appropriate permissions and ownership at installation time.
598 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
599 environment if executing "make check" with limited sandbox mode using
600 an unprivileged user.
603 Since the switch to GPT disk labels, fsck for UFS/FFS has been
604 unable to automatically find alternate superblocks. As of r322297,
605 the information needed to find alternate superblocks has been
606 moved to the end of the area reserved for the boot block.
607 Filesystems created with a newfs of this vintage or later
608 will create the recovery information. If you have a filesystem
609 created prior to this change and wish to have a recovery block
610 created for your filesystem, you can do so by running fsck in
611 foreground mode (i.e., do not use the -p or -y options). As it
612 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
613 to which you should answer yes.
616 As of r321665, an NFSv4 server configuration that services
617 Kerberos mounts or clients that do not support the uid/gid in
618 owner/owner_group string capability, must explicitly enable
619 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
620 machine's /etc/rc.conf file.
623 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
624 Please see the 20141231 entry below for information about prerequisites
625 and upgrading, if you are not already using clang 3.5.0 or higher.
628 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
629 r-commands (rlogin, rsh, etc.) to be built with the base system.
632 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
633 a very major ABI incompatible change, so users of FreeBSD/powerpc must
634 be careful when performing source upgrades. It is best to run
635 'make installworld' from an alternate root system, either a live
636 CD/memory stick, or a temporary root partition. Additionally, all ports
637 must be recompiled. powerpc64 is largely unaffected, except in the case
638 of 32-bit compatibility. All 32-bit binaries will be affected.
641 Forward compatibility for the "ino64" project have been committed. This
642 will allow most new binaries to run on older kernels in a limited
643 fashion. This prevents many of the common foot-shooting actions in the
644 upgrade as well as the limited ability to roll back the kernel across
645 the ino64 upgrade. Complicated use cases may not work properly, though
646 enough simpler ones work to allow recovery in most situations.
649 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
650 if you require the GPL compiler.
653 The internal ABI used for communication between the NFS kernel modules
654 was changed by r320085, so __FreeBSD_version was bumped to
655 ensure all the NFS related modules are updated together.
658 The ABI of struct event was changed by extending the data
659 member to 64bit and adding ext fields. For upgrade, same
660 precautions as for the entry 20170523 "ino64" must be
664 The GNU roff toolchain has been removed from base. To render manpages
665 which are not supported by mandoc(1), man(1) can fallback on GNU roff
666 from ports (and recommends to install it).
667 To render roff(7) documents, consider using GNU roff from ports or the
668 heirloom doctools roff toolchain from ports via pkg install groff or
669 via pkg install heirloom-doctools.
672 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
673 smaller runtime footprint builds. This is useful for embedded systems
674 which only require one chipset support.
676 If you load it as a module, make sure this is in /boot/loader.conf:
680 This will load the HAL, all chip/RF backends and if_ath_pci.
681 If you have if_ath_pci in /boot/loader.conf, ensure it is after
682 if_ath or it will not load any HAL chipset support.
684 If you want to selectively load things (eg on ye cheape ARM/MIPS
685 platforms where RAM is at a premium) you should:
688 * load the chip modules in question
689 * load ath_rate, ath_dfs
691 * load if_ath_pci and/or if_ath_ahb depending upon your particular
692 bus bind type - this is where probe/attach is done.
694 For further comments/feedback, poke adrian@ .
697 The "ino64" 64-bit inode project has been committed, which extends
698 a number of types to 64 bits. Upgrading in place requires care and
699 adherence to the documented upgrade procedure.
701 If using a custom kernel configuration ensure that the
702 COMPAT_FREEBSD11 option is included (as during the upgrade the
703 system will be running the ino64 kernel with the existing world).
705 For the safest in-place upgrade begin by removing previous build
706 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
707 full procedure documented below under the heading "To rebuild
708 everything and install it on the current system." Specifically,
709 a reboot is required after installing the new kernel before
713 The NATM framework including the en(4), fatm(4), hatm(4), and
714 patm(4) devices has been removed. Consumers should plan a
715 migration before the end-of-life date for FreeBSD 11.
718 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
719 diff has not been implemented, if those are needed a newer version of
720 GNU diff is available via the diffutils package under the gdiff name.
723 As of r316810 for ipfilter, keep frags is no longer assumed when
724 keep state is specified in a rule. r316810 aligns ipfilter with
725 documentation in man pages separating keep frags from keep state.
726 This allows keep state to be specified without forcing keep frags
727 and allows keep frags to be specified independently of keep state.
728 To maintain previous behaviour, also specify keep frags with
729 keep state (as documented in ipf.conf.5).
732 arm64 builds now use the base system LLD 4.0.0 linker by default,
733 instead of requiring that the aarch64-binutils port or package be
734 installed. To continue using aarch64-binutils, set
735 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
738 The UDP optimization in entry 20160818 that added the sysctl
739 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
740 packets will no longer be treated as L3 broadcast packets.
743 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
744 use any explicitly assigned loopback address available in the jail
745 instead of using the first assigned address of the jail.
748 The ctl.ko module no longer implements the iSCSI target frontend:
749 cfiscsi.ko does instead.
751 If building cfiscsi.ko as a kernel module, the module can be loaded
752 via one of the following methods:
753 - `cfiscsi_load="YES"` in loader.conf(5).
754 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
755 - ctladm(8)/ctld(8), when compiled with iSCSI support
756 (`WITH_ISCSI=yes` in src.conf(5))
758 Please see cfiscsi(4) for more details.
761 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
762 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
763 same source (previously, the dependency of mmcsd.ko on mmc.ko was
764 missing, but mmcsd.ko now will refuse to load if it is incompatible
768 The syntax of ipfw(8) named states was changed to avoid ambiguity.
769 If you have used named states in the firewall rules, you need to modify
770 them after installworld and before rebooting. Now named states must
771 be prefixed with colon.
774 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
775 removed as the userland we provide cannot use them. The KMS version
776 (sys/dev/drm2) supports the same hardware.
779 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
780 Please see the 20141231 entry below for information about prerequisites
781 and upgrading, if you are not already using clang 3.5.0 or higher.
784 The code that provides support for ZFS .zfs/ directory functionality
785 has been reimplemented. It's not possible now to create a snapshot
786 by mkdir under .zfs/snapshot/. That should be the only user visible
790 EISA bus support has been removed. The WITH_EISA option is no longer
794 MCA bus support has been removed.
797 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
798 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
801 The EM_MULTIQUEUE kernel configuration option is deprecated now that
802 the em(4) driver conforms to iflib specifications.
805 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
806 IFLIB. If you have a custom kernel configuration that excludes em(4)
807 but you use igb(4), you need to re-add em(4) to your custom configuration.
810 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
811 Please see the 20141231 entry below for information about prerequisites
812 and upgrading, if you are not already using clang 3.5.0 or higher.
815 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
816 Please see the 20141231 entry below for information about prerequisites
817 and upgrading, if you are not already using clang 3.5.0 or higher.
820 The layout of the pmap structure has changed for powerpc to put the pmap
821 statistics at the front for all CPU variations. libkvm(3) and all tools
822 that link against it need to be recompiled.
825 isl(4) and cyapa(4) drivers now require a new driver,
826 chromebook_platform(4), to work properly on Chromebook-class hardware.
827 On other types of hardware the drivers may need to be configured using
828 device hints. Please see the corresponding manual pages for details.
831 The urtwn(4) driver was merged into rtwn(4) and now consists of
832 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
834 Also, firmware for RTL8188CE was renamed due to possible name
835 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
838 GNU rcs has been removed from base. It is available as packages:
839 - rcs: Latest GPLv3 GNU rcs version.
840 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
844 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
845 modules now requires that the kernel configuration contain the
846 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
849 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
850 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
853 Relocatable object files with the extension of .So have been renamed
854 to use an extension of .pico instead. The purpose of this change is
855 to avoid a name clash with shared libraries on case-insensitive file
856 systems. On those file systems, foo.So is the same file as foo.so.
859 GNU rcs has been turned off by default. It can (temporarily) be built
860 again by adding WITH_RCS knob in src.conf.
861 Otherwise, GNU rcs is available from packages:
862 - rcs: Latest GPLv3 GNU rcs version.
863 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
866 The backup_uses_rcs functionality has been removed from rc.subr.
869 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
870 two separate components, QUEUE_MACRO_DEBUG_TRACE and
871 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
872 QUEUE_MACRO_DEBUG behavior.
875 r304787 changed some ioctl interfaces between the iSCSI userspace
876 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
877 rebuilt to work with new kernels. __FreeBSD_version has been bumped
881 The UDP receive code has been updated to only treat incoming UDP
882 packets that were addressed to an L2 broadcast address as L3
883 broadcast packets. It is not expected that this will affect any
884 standards-conforming UDP application. The new behaviour can be
885 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
889 Remove the openbsd_poll system call.
890 __FreeBSD_version has been bumped because of this.
893 The stable/11 branch has been created from head@r302406.
896 The libc stub for the pipe(2) system call has been replaced with
897 a wrapper that calls the pipe2(2) system call and the pipe(2)
898 system call is now only implemented by the kernels that include
899 "options COMPAT_FREEBSD10" in their config file (this is the
900 default). Users should ensure that this option is enabled in
901 their kernel or upgrade userspace to r302092 before upgrading their
905 CAM will now strip leading spaces from SCSI disks' serial numbers.
906 This will affect users who create UFS filesystems on SCSI disks using
907 those disk's diskid device nodes. For example, if /etc/fstab
908 previously contained a line like
909 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
910 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
911 transforms like gmirror may also be affected. ZFS users should
915 The bitstring(3) API has been updated with new functionality and
916 improved performance. But it is binary-incompatible with the old API.
917 Objects built with the new headers may not be linked against objects
918 built with the old headers.
921 The brk and sbrk functions have been removed from libc on arm64.
922 Binutils from ports has been updated to not link to these
923 functions and should be updated to the latest version before
924 installing a new libc.
927 The armv6 port now defaults to hard float ABI. Limited support
928 for running both hardfloat and soft float on the same system
929 is available using the libraries installed with -DWITH_LIBSOFT.
930 This has only been tested as an upgrade path for installworld
931 and packages may fail or need manual intervention to run. New
932 packages will be needed.
934 To update an existing self-hosted armv6hf system, you must add
935 TARGET_ARCH=armv6 on the make command line for both the build
936 and the install steps.
939 Kernel modules compiled outside of a kernel build now default to
940 installing to /boot/modules instead of /boot/kernel. Many kernel
941 modules built this way (such as those in ports) already overrode
942 KMODDIR explicitly to install into /boot/modules. However,
943 manually building and installing a module from /sys/modules will
944 now install to /boot/modules instead of /boot/kernel.
947 The CAM I/O scheduler has been committed to the kernel. There should be
948 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
949 list of known rogues that claim support for this but actually corrupt
950 data is believed to be complete, be on the lookout for data
951 corruption. The known rogue list is believed to be complete:
953 o Crucial MX100, M550 drives with MU01 firmware.
954 o Micron M510 and M550 drives with MU01 firmware.
955 o Micron M500 prior to MU07 firmware
956 o Samsung 830, 840, and 850 all firmwares
957 o FCCT M500 all firmwares
959 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
960 with working NCQ TRIM. For Micron branded drives, see your sales rep for
961 updated firmware. Black listed drives will work correctly because these
962 drives work correctly so long as no NCQ TRIMs are sent to them. Given
963 this list is the same as found in Linux, it's believed there are no
964 other rogues in the market place. All other models from the above
967 To be safe, if you are at all concerned, you can quirk each of your
968 drives to prevent NCQ from being sent by setting:
969 kern.cam.ada.X.quirks="0x2"
970 in loader.conf. If the drive requires the 4k sector quirk, set the
974 The FAST_DEPEND build option has been removed and its functionality is
975 now the one true way. The old mkdep(1) style of 'make depend' has
976 been removed. See 20160311 for further details.
979 Resource range types have grown from unsigned long to uintmax_t. All
980 drivers, and anything using libdevinfo, need to be recompiled.
983 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
984 builds. It no longer runs mkdep(1) during 'make depend', and the
985 'make depend' stage can safely be skipped now as it is auto ran
986 when building 'make all' and will generate all SRCS and DPSRCS before
987 building anything else. Dependencies are gathered at compile time with
988 -MF flags kept in separate .depend files per object file. Users should
989 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
993 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
994 kernel modules. Therefore, if you load any kernel modules at boot time,
995 please install the boot loaders after you install the kernel, but before
999 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1000 make installkernel KERNCONF=YOUR_KERNEL_HERE
1001 make -C sys/boot install
1002 <reboot in single user>
1004 Then follow the usual steps, described in the General Notes section,
1008 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1009 see the 20141231 entry below for information about prerequisites and
1010 upgrading, if you are not already using clang 3.5.0 or higher.
1013 The AIO subsystem is now a standard part of the kernel. The
1014 VFS_AIO kernel option and aio.ko kernel module have been removed.
1015 Due to stability concerns, asynchronous I/O requests are only
1016 permitted on sockets and raw disks by default. To enable
1017 asynchronous I/O requests on all file types, set the
1018 vfs.aio.enable_unsafe sysctl to a non-zero value.
1021 The ELF object manipulation tool objcopy is now provided by the
1022 ELF Tool Chain project rather than by GNU binutils. It should be a
1023 drop-in replacement, with the addition of arm64 support. The
1024 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1025 to obtain the GNU version if necessary.
1028 Building ZFS pools on top of zvols is prohibited by default. That
1029 feature has never worked safely; it's always been prone to deadlocks.
1030 Using a zvol as the backing store for a VM guest's virtual disk will
1031 still work, even if the guest is using ZFS. Legacy behavior can be
1032 restored by setting vfs.zfs.vol.recursive=1.
1035 The NONE and HPN patches has been removed from OpenSSH. They are
1036 still available in the security/openssh-portable port.
1039 With the addition of ypldap(8), a new _ypldap user is now required
1040 during installworld. "mergemaster -p" can be used to add the user
1041 prior to installworld, as documented in the handbook.
1044 The tftp loader (pxeboot) now uses the option root-path directive. As a
1045 consequence it no longer looks for a pxeboot.4th file on the tftp
1046 server. Instead it uses the regular /boot infrastructure as with the
1050 The code to start recording plug and play data into the modules has
1051 been committed. While the old tools will properly build a new kernel,
1052 a number of warnings about "unknown metadata record 4" will be produced
1053 for an older kldxref. To avoid such warnings, make sure to rebuild
1054 the kernel toolchain (or world). Make sure that you have r292078 or
1055 later when trying to build 292077 or later before rebuilding.
1058 Debug data files are now built by default with 'make buildworld' and
1059 installed with 'make installworld'. This facilitates debugging but
1060 requires more disk space both during the build and for the installed
1061 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1065 r291527 changed the internal interface between the nfsd.ko and
1066 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1067 __FreeBSD_version has been bumped because of this.
1070 Add support for unicode collation strings leads to a change of
1071 order of files listed by ls(1) for example. To get back to the old
1072 behaviour, set LC_COLLATE environment variable to "C".
1074 Databases administrators will need to reindex their databases given
1075 collation results will be different.
1077 Due to a bug in install(1) it is recommended to remove the ancient
1078 locales before running make installworld.
1080 rm -rf /usr/share/locale/*
1083 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1084 libcrypto.so.7 or libssl.so.7 must be recompiled.
1087 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1088 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1089 should be replaced with isp_2400 and isp_2500 modules respectively.
1092 The build previously allowed using 'make -n' to not recurse into
1093 sub-directories while showing what commands would be executed, and
1094 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1095 and 'make -N' will not.
1098 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1099 and etcupdate will now use this file. A custom sendmail.cf is now
1100 updated via this mechanism rather than via installworld. If you had
1101 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1102 want to remove the exclusion or change it to "always install".
1103 /etc/mail/sendmail.cf is now managed the same way regardless of
1104 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1105 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1108 Compatibility shims for legacy ATA device names have been removed.
1109 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1110 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1111 environment variables, /dev/ad* and /dev/ar* symbolic links.
1114 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1115 Please see the 20141231 entry below for information about prerequisites
1116 and upgrading, if you are not already using clang 3.5.0 or higher.
1119 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1120 and renamed from .symbols to .debug. This reduces the size requirements
1121 on the boot partition or file system and provides consistency with
1122 userland debug files.
1124 When using the supported kernel installation method the
1125 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1126 as is done with /boot/kernel.
1128 Developers wishing to maintain the historical behavior of installing
1129 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1132 The wireless drivers had undergone changes that remove the 'parent
1133 interface' from the ifconfig -l output. The rc.d network scripts
1134 used to check presence of a parent interface in the list, so old
1135 scripts would fail to start wireless networking. Thus, etcupdate(3)
1136 or mergemaster(8) run is required after kernel update, to update your
1137 rc.d scripts in /etc.
1140 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1141 These configurations are now automatically interpreted as
1142 'scrub fragment reassemble'.
1145 Kernel-loadable modules for the random(4) device are back. To use
1146 them, the kernel must have
1149 options RANDOM_LOADABLE
1151 kldload(8) can then be used to load random_fortuna.ko
1152 or random_yarrow.ko. Please note that due to the indirect
1153 function calls that the loadable modules need to provide,
1154 the build-in variants will be slightly more efficient.
1156 The random(4) kernel option RANDOM_DUMMY has been retired due to
1157 unpopularity. It was not all that useful anyway.
1160 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1161 Control over building the ELF Tool Chain tools is now provided by
1162 the WITHOUT_TOOLCHAIN knob.
1165 The polarity of Pulse Per Second (PPS) capture events with the
1166 uart(4) driver has been corrected. Prior to this change the PPS
1167 "assert" event corresponded to the trailing edge of a positive PPS
1168 pulse and the "clear" event was the leading edge of the next pulse.
1170 As the width of a PPS pulse in a typical GPS receiver is on the
1171 order of 1 millisecond, most users will not notice any significant
1172 difference with this change.
1174 Anyone who has compensated for the historical polarity reversal by
1175 configuring a negative offset equal to the pulse width will need to
1176 remove that workaround.
1179 The default group assigned to /dev/dri entries has been changed
1180 from 'wheel' to 'video' with the id of '44'. If you want to have
1181 access to the dri devices please add yourself to the video group
1184 # pw groupmod video -m $USER
1187 The menu.rc and loader.rc files will now be replaced during
1188 upgrades. Please migrate local changes to menu.rc.local and
1189 loader.rc.local instead.
1192 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1193 strings and strip have been removed. The src.conf(5) knob
1194 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1197 As ZFS requires more kernel stack pages than is the default on some
1198 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1199 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1201 Please consider using 'options KSTACK_PAGES=X' where X is greater
1202 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1205 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1206 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1207 default, i.e., they will not contain "::". For example, instead
1208 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1209 to have a more specific match, such as different map entries for
1210 IPv6:0:0 vs IPv6:0. This change requires that configuration
1211 data (including maps, files, classes, custom ruleset, etc.) must
1212 use the same format, so make certain such configuration data is
1213 upgrading. As a very simple check search for patterns like
1214 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1215 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1216 the cf option UseCompressedIPv6Addresses.
1219 The default kernel entropy-processing algorithm is now
1220 Fortuna, replacing Yarrow.
1222 Assuming you have 'device random' in your kernel config
1223 file, the configurations allow a kernel option to override
1224 this default. You may choose *ONE* of:
1226 options RANDOM_YARROW # Legacy /dev/random algorithm.
1227 options RANDOM_DUMMY # Blocking-only driver.
1229 If you have neither, you get Fortuna. For most people,
1230 read no further, Fortuna will give a /dev/random that works
1231 like it always used to, and the difference will be irrelevant.
1233 If you remove 'device random', you get *NO* kernel-processed
1234 entropy at all. This may be acceptable to folks building
1235 embedded systems, but has complications. Carry on reading,
1236 and it is assumed you know what you need.
1238 *PLEASE* read random(4) and random(9) if you are in the
1239 habit of tweaking kernel configs, and/or if you are a member
1240 of the embedded community, wanting specific and not-usual
1241 behaviour from your security subsystems.
1243 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1244 random', you will NOT have a functioning /dev/random, and
1245 many cryptographic features will not work, including SSH.
1246 You may also find strange behaviour from the random(3) set
1247 of library functions, in particular sranddev(3), srandomdev(3)
1248 and arc4random(3). The reason for this is that the KERN_ARND
1249 sysctl only returns entropy if it thinks it has some to
1250 share, and with RANDOM_DUMMY or no 'device random' this
1254 An additional fix for the issue described in the 20150614 sendmail
1255 entry below has been committed in revision 284717.
1258 FreeBSD's old make (fmake) has been removed from the system. It is
1259 available as the devel/fmake port or via pkg install fmake.
1262 The fix for the issue described in the 20150614 sendmail entry
1263 below has been committed in revision 284436. The work
1264 around described in that entry is no longer needed unless the
1265 default setting is overridden by a confDH_PARAMETERS configuration
1266 setting of '5' or pointing to a 512 bit DH parameter file.
1269 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1270 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1271 and devel/kyua to version 0.20+ and adjust any calling code to work
1272 with Kyuafile and kyua.
1275 The import of openssl to address the FreeBSD-SA-15:10.openssl
1276 security advisory includes a change which rejects handshakes
1277 with DH parameters below 768 bits. sendmail releases prior
1278 to 8.15.2 (not yet released), defaulted to a 512 bit
1279 DH parameter setting for client connections. To work around
1280 this interoperability, sendmail can be configured to use a
1281 2048 bit DH parameter by:
1283 1. Edit /etc/mail/`hostname`.mc
1284 2. If a setting for confDH_PARAMETERS does not exist or
1285 exists and is set to a string beginning with '5',
1286 replace it with '2'.
1287 3. If a setting for confDH_PARAMETERS exists and is set to
1288 a file path, create a new file with:
1289 openssl dhparam -out /path/to/file 2048
1290 4. Rebuild the .cf file:
1291 cd /etc/mail/; make; make install
1292 5. Restart sendmail:
1293 cd /etc/mail/; make restart
1295 A sendmail patch is coming, at which time this file will be
1299 Generation of legacy formatted entries have been disabled by default
1300 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1301 entries were converted to use the new format by default when the new,
1302 machine independent format have been added and supported since FreeBSD
1305 Please see the pwd_mkdb(8) manual page for further details.
1308 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1309 20141231 entry below for information about prerequisites and upgrading,
1310 if you are not already using 3.5.0 or higher.
1313 TI platform code switched to using vendor DTS files and this update
1314 may break existing systems running on Beaglebone, Beaglebone Black,
1317 - dtb files should be regenerated/reinstalled. Filenames are the
1318 same but content is different now
1319 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1320 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1321 addressing scheme is now pin 25 on /dev/gpioc3.
1322 - Pandaboard: /etc/ttys should be updated, serial console device is
1323 now /dev/ttyu2, not /dev/ttyu0
1326 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1327 If you need the GNU extension from groff soelim(1), install groff
1328 from package: pkg install groff, or via ports: textproc/groff.
1331 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1332 defined in symlink(7); previously symlinks were silently ignored.
1335 The const qualifier has been removed from iconv(3) to comply with
1336 POSIX. The ports tree is aware of this from r384038 onwards.
1339 Libraries specified by LIBADD in Makefiles must have a corresponding
1340 DPADD_<lib> variable to ensure correct dependencies. This is now
1341 enforced in src.libnames.mk.
1344 From legacy ata(4) driver was removed support for SATA controllers
1345 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1346 Kernel modules ataahci and ataadaptec were removed completely,
1347 replaced by ahci and mvs modules respectively.
1350 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1351 the 20141231 entry below for information about prerequisites and
1352 upgrading, if you are not already using 3.5.0 or higher.
1355 The 32-bit PowerPC kernel has been changed to a position-independent
1356 executable. This can only be booted with a version of loader(8)
1357 newer than January 31, 2015, so make sure to update both world and
1358 kernel before rebooting.
1361 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1362 but before r278950, the RNG was not seeded properly. Immediately
1363 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1364 ssh keys or openssl keys) that were generated w/ a kernel from that
1365 range. This does not affect programs that directly used /dev/random
1366 or /dev/urandom. All userland uses of arc4random(3) are affected.
1369 The autofs(4) ABI was changed in order to restore binary compatibility
1370 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1371 with the new kernel.
1374 The powerpc64 kernel has been changed to a position-independent
1375 executable. This can only be booted with a new version of loader(8),
1376 so make sure to update both world and kernel before rebooting.
1379 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1380 only release, no new features have been added. Please see the 20141231
1381 entry below for information about prerequisites and upgrading, if you
1382 are not already using 3.5.0.
1385 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1386 taken from the ELF Tool Chain project rather than GNU binutils. They
1387 should be drop-in replacements, with the addition of arm64 support.
1388 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1389 binutils tools, if necessary. See 20150805 for updated information.
1392 The default Unbound configuration now enables remote control
1393 using a local socket. Users who have already enabled the
1394 local_unbound service should regenerate their configuration
1395 by running "service local_unbound setup" as root.
1398 The GNU texinfo and GNU info pages have been removed.
1399 To be able to view GNU info pages please install texinfo from ports.
1402 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1404 As of this release, a prerequisite for building clang, llvm and lldb is
1405 a C++11 capable compiler and C++11 standard library. This means that to
1406 be able to successfully build the cross-tools stage of buildworld, with
1407 clang as the bootstrap compiler, your system compiler or cross compiler
1408 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1409 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1412 On any standard FreeBSD 10.x or 11.x installation, where clang and
1413 libc++ are on by default (that is, on x86 or arm), this should work out
1416 On 9.x installations where clang is enabled by default, e.g. on x86 and
1417 powerpc, libc++ will not be enabled by default, so libc++ should be
1418 built (with clang) and installed first. If both clang and libc++ are
1419 missing, build clang first, then use it to build libc++.
1421 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1422 the instructions for 9.x above.
1424 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1425 default, and do not build clang.
1427 Many embedded systems are resource constrained, and will not be able to
1428 build clang in a reasonable time, or in some cases at all. In those
1429 cases, cross building bootable systems on amd64 is a workaround.
1431 This new version of clang introduces a number of new warnings, of which
1432 the following are most likely to appear:
1436 This warns in two cases, for both C and C++:
1437 * When the code is trying to take the absolute value of an unsigned
1438 quantity, which is effectively a no-op, and almost never what was
1439 intended. The code should be fixed, if at all possible. If you are
1440 sure that the unsigned quantity can be safely cast to signed, without
1441 loss of information or undefined behavior, you can add an explicit
1442 cast, or disable the warning.
1444 * When the code is trying to take an absolute value, but the called
1445 abs() variant is for the wrong type, which can lead to truncation.
1446 If you want to disable the warning instead of fixing the code, please
1447 make sure that truncation will not occur, or it might lead to unwanted
1450 -Wtautological-undefined-compare and
1451 -Wundefined-bool-conversion
1453 These warn when C++ code is trying to compare 'this' against NULL, while
1454 'this' should never be NULL in well-defined C++ code. However, there is
1455 some legacy (pre C++11) code out there, which actively abuses this
1456 feature, which was less strictly defined in previous C++ versions.
1458 Squid and openjdk do this, for example. The warning can be turned off
1459 for C++98 and earlier, but compiling the code in C++11 mode might result
1460 in unexpected behavior; for example, the parts of the program that are
1461 unreachable could be optimized away.
1464 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1465 kernel sources have been removed. The .h files remain, since some
1466 utilities include them. This will need to be fixed later.
1467 If "mount -t oldnfs ..." is attempted, it will fail.
1468 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1469 the utilities will report errors.
1472 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1473 directories to top level SUBDIR variable when their parent
1474 directory is included in LOCAL_DIRS. Users with build systems with
1475 such hierarchies and without SUBDIR entries in the parent
1476 directory Makefiles should add them or add the directories to
1480 faith(4) and faithd(8) have been removed from the base system. Faith
1481 has been obsolete for a very long time.
1484 vt(4), the new console driver, is enabled by default. It brings
1485 support for Unicode and double-width characters, as well as
1486 support for UEFI and integration with the KMS kernel video
1489 You may need to update your console settings in /etc/rc.conf,
1490 most probably the keymap. During boot, /etc/rc.d/syscons will
1491 indicate what you need to do.
1493 vt(4) still has issues and lacks some features compared to
1494 syscons(4). See the wiki for up-to-date information:
1495 https://wiki.freebsd.org/Newcons
1497 If you want to keep using syscons(4), you can do so by adding
1498 the following line to /boot/loader.conf:
1502 pjdfstest has been integrated into kyua as an opt-in test suite.
1503 Please see share/doc/pjdfstest/README for more details on how to
1507 gperf has been removed from the base system for architectures
1508 that use clang. Ports that require gperf will obtain it from the
1512 pjdfstest has been moved from tools/regression/pjdfstest to
1516 At svn r271982, The default linux compat kernel ABI has been adjusted
1517 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1518 update. If you wish to continue using the linux-f10 compat ports,
1519 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1520 encouraged to update their linux-compat packages to linux-c6 during
1521 their next update cycle.
1524 The ofwfb driver, used to provide a graphics console on PowerPC when
1525 using vt(4), no longer allows mmap() of all physical memory. This
1526 will prevent Xorg on PowerPC with some ATI graphics cards from
1527 initializing properly unless x11-servers/xorg-server is updated to
1531 The xdev targets have been converted to using TARGET and
1532 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1535 The default unbound configuration has been modified to address
1536 issues with reverse lookups on networks that use private
1537 address ranges. If you use the local_unbound service, run
1538 "service local_unbound setup" as root to regenerate your
1539 configuration, then "service local_unbound reload" to load the
1543 The GNU texinfo and GNU info pages are not built and installed
1544 anymore, WITH_INFO knob has been added to allow to built and install
1546 UPDATE: see 20150102 entry on texinfo's removal
1549 The GNU readline library is now an INTERNALLIB - that is, it is
1550 statically linked into consumers (GDB and variants) in the base
1551 system, and the shared library is no longer installed. The
1552 devel/readline port is available for third party software that
1556 The Itanium architecture (ia64) has been removed from the list of
1557 known architectures. This is the first step in the removal of the
1561 Commit r268115 has added NFSv4.1 server support, merged from
1562 projects/nfsv4.1-server. Since this includes changes to the
1563 internal interfaces between the NFS related modules, a full
1564 build of the kernel and modules will be necessary.
1565 __FreeBSD_version has been bumped.
1568 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1569 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1570 which differs from the behaviour controlled by this knob.)
1573 Maximal length of the serial number in CTL was increased from 16 to
1574 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1575 and ctld, need to be rebuilt to work with a new kernel.
1578 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1579 1 respectively to match the upstream numbers. They were out of
1580 sync because, when they were originally added to FreeBSD, the
1581 upstream versions were not respected. These libraries are private
1582 and not yet built by default, so renumbering them should be a
1583 non-issue. However, unclean source trees will yield broken test
1584 programs once the operator executes "make delete-old-libs" after a
1585 "make installworld".
1587 Additionally, the atf-sh binary was made private by moving it into
1588 /usr/libexec/. Already-built shell test programs will keep the
1589 path to the old binary so they will break after "make delete-old"
1592 If you are using WITH_TESTS=yes (not the default), wipe the object
1593 tree and rebuild from scratch to prevent spurious test failures.
1594 This is only needed once: the misnumbered libraries and misplaced
1595 binaries have been added to OptionalObsoleteFiles.inc so they will
1596 be removed during a clean upgrade.
1599 Clang and llvm have been upgraded to 3.4.1 release.
1602 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1603 be removed to avoid issues in the future (and has been added to
1607 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1608 past, it affected all builds that used the bsd.*.mk files. The old
1609 behavior was a bug, but people may have relied upon it. To get this
1610 behavior back, you can .include /etc/src.conf from /etc/make.conf
1611 (which is still global and isn't changed). This also changes the
1612 behavior of incremental builds inside the tree of individual
1613 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1614 Although this has survived make universe and some upgrade scenarios,
1615 other upgrade scenarios may have broken. At least one form of
1616 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1617 as well... In cases where MAKESYSPATH isn't working with this
1618 setting, you'll need to set it to the full path to your tree.
1620 One side effect of all this cleaning up is that bsd.compiler.mk
1621 is no longer implicitly included by bsd.own.mk. If you wish to
1622 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1626 The lindev device has been removed since /dev/full has been made a
1627 standard device. __FreeBSD_version has been bumped.
1630 The knob WITHOUT_VI was added to the base system, which controls
1631 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1632 in order to reorder files share/termcap and didn't build ex(1) as a
1633 build tool, so building/installing with WITH_VI is highly advised for
1634 build hosts for older releases.
1636 This issue has been fixed in stable/9 and stable/10 in r277022 and
1637 r276991, respectively.
1640 The YES_HESIOD knob has been removed. It has been obsolete for
1641 a decade. Please move to using WITH_HESIOD instead or your builds
1642 will silently lack HESIOD.
1645 The uart(4) driver has been changed with respect to its handling
1646 of the low-level console. Previously the uart(4) driver prevented
1647 any process from changing the baudrate or the CLOCAL and HUPCL
1648 control flags. By removing the restrictions, operators can make
1649 changes to the serial console port without having to reboot.
1650 However, when getty(8) is started on the serial device that is
1651 associated with the low-level console, a misconfigured terminal
1652 line in /etc/ttys will now have a real impact.
1653 Before upgrading the kernel, make sure that /etc/ttys has the
1654 serial console device configured as 3wire without baudrate to
1655 preserve the previous behaviour. E.g:
1656 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1659 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1660 to improve performance. To re-enable it, if needed, run rpcbind
1661 with command line option -W.
1664 Switched back to the GPL dtc compiler due to updates in the upstream
1665 dts files not being supported by the BSDL dtc compiler. You will need
1666 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1667 may result while building dtb files during a kernel build if you fail
1668 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1671 Clang and llvm have been upgraded to 3.4 release.
1674 The nve(4) driver has been removed. Please use the nfe(4) driver
1675 for NVIDIA nForce MCP Ethernet adapters instead.
1678 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1679 This could cause certain C++ applications using shared libraries built
1680 against the previous version of libc++ to crash. The incompatibility
1681 has now been fixed, but any C++ applications or shared libraries built
1682 between r261283 and r261801 should be recompiled.
1685 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1686 capability mode support. Please note that enabling the feature in
1687 kernel is still highly recommended.
1690 OpenSSH is now built with sandbox support, and will use sandbox as
1691 the default privilege separation method. This requires Capsicum
1692 capability mode support in kernel.
1695 The libelf and libdwarf libraries have been updated to newer
1696 versions from upstream. Shared library version numbers for
1697 these two libraries were bumped. Any ports or binaries
1698 requiring these two libraries should be recompiled.
1699 __FreeBSD_version is bumped to 1100006.
1702 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1703 instead of providing an explicit one, this would prevent such
1704 Makefile from providing its own Kyuafile in the future during
1705 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1706 intervention is needed to clean an objdir if you use NO_CLEAN:
1707 # find /usr/obj -name Kyuafile | xargs rm -f
1710 The behavior of gss_pseudo_random() for the krb5 mechanism
1711 has changed, for applications requesting a longer random string
1712 than produced by the underlying enctype's pseudo-random() function.
1713 In particular, the random string produced from a session key of
1714 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1715 be different at the 17th octet and later, after this change.
1716 The counter used in the PRF+ construction is now encoded as a
1717 big-endian integer in accordance with RFC 4402.
1718 __FreeBSD_version is bumped to 1100004.
1721 The WITHOUT_ATF build knob has been removed and its functionality
1722 has been subsumed into the more generic WITHOUT_TESTS. If you were
1723 using the former to disable the build of the ATF libraries, you
1724 should change your settings to use the latter.
1727 The default version of mtree is nmtree which is obtained from
1728 NetBSD. The output is generally the same, but may vary
1729 slightly. If you found you need identical output adding
1730 "-F freebsd9" to the command line should do the trick. For the
1731 time being, the old mtree is available as fmtree.
1734 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1735 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1736 1.1.4_8 and verify bsdyml not linked in, before running "make
1738 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1740 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1743 The stable/10 branch has been created in subversion from head
1750 Avoid using make -j when upgrading. While generally safe, there are
1751 sometimes problems using -j to upgrade. If your upgrade fails with
1752 -j, please try again without -j. From time to time in the past there
1753 have been problems using -j with buildworld and/or installworld. This
1754 is especially true when upgrading between "distant" versions (eg one
1755 that cross a major release boundary or several minor releases, or when
1756 several months have passed on the -current branch).
1758 Sometimes, obscure build problems are the result of environment
1759 poisoning. This can happen because the make utility reads its
1760 environment when searching for values for global variables. To run
1761 your build attempts in an "environmental clean room", prefix all make
1762 commands with 'env -i '. See the env(1) manual page for more details.
1764 When upgrading from one major version to another it is generally best to
1765 upgrade to the latest code in the currently installed branch first, then
1766 do an upgrade to the new branch. This is the best-tested upgrade path,
1767 and has the highest probability of being successful. Please try this
1768 approach if you encounter problems with a major version upgrade. Since
1769 the stable 4.x branch point, one has generally been able to upgrade from
1770 anywhere in the most recent stable branch to head / current (or even the
1771 last couple of stable branches). See the top of this file when there's
1774 When upgrading a live system, having a root shell around before
1775 installing anything can help undo problems. Not having a root shell
1776 around can lead to problems if pam has changed too much from your
1777 starting point to allow continued authentication after the upgrade.
1779 This file should be read as a log of events. When a later event changes
1780 information of a prior event, the prior event should not be deleted.
1781 Instead, a pointer to the entry with the new information should be
1782 placed in the old entry. Readers of this file should also sanity check
1783 older entries before relying on them blindly. Authors of new entries
1784 should write them with this in mind.
1788 When upgrading the boot ZFS pool to a new version, always follow
1791 1.) recompile and reinstall the ZFS boot loader and boot block
1792 (this is part of "make buildworld" and "make installworld")
1794 2.) update the ZFS boot block on your boot drive
1796 The following example updates the ZFS boot block on the first
1797 partition (freebsd-boot) of a GPT partitioned drive ada0:
1798 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1800 Non-boot pools do not need these updates.
1804 If you are updating from a prior version of FreeBSD (even one just
1805 a few days old), you should follow this procedure. It is the most
1806 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1808 make kernel-toolchain
1809 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1810 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1812 To test a kernel once
1813 ---------------------
1814 If you just want to boot a kernel once (because you are not sure
1815 if it works, or if you want to boot a known bad kernel to provide
1816 debugging information) run
1817 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1818 nextboot -k testkernel
1820 To rebuild everything and install it on the current system.
1821 -----------------------------------------------------------
1822 # Note: sometimes if you are running current you gotta do more than
1823 # is listed here if you are upgrading from a really old current.
1825 <make sure you have good level 0 dumps>
1827 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1828 make installkernel KERNCONF=YOUR_KERNEL_HERE
1830 <reboot in single user> [3]
1837 To cross-install current onto a separate partition
1838 --------------------------------------------------
1839 # In this approach we use a separate partition to hold
1840 # current's root, 'usr', and 'var' directories. A partition
1841 # holding "/", "/usr" and "/var" should be about 2GB in
1844 <make sure you have good level 0 dumps>
1847 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1848 <maybe newfs current's root partition>
1849 <mount current's root partition on directory ${CURRENT_ROOT}>
1850 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1851 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1852 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1853 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1854 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1855 <reboot into current>
1856 <do a "native" rebuild/install as described in the previous section>
1857 <maybe install compatibility libraries from ports/misc/compat*>
1861 To upgrade in-place from stable to current
1862 ----------------------------------------------
1863 <make sure you have good level 0 dumps>
1865 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1866 make installkernel KERNCONF=YOUR_KERNEL_HERE
1868 <reboot in single user> [3]
1875 Make sure that you've read the UPDATING file to understand the
1876 tweaks to various things you need. At this point in the life
1877 cycle of current, things change often and you are on your own
1878 to cope. The defaults can also change, so please read ALL of
1879 the UPDATING entries.
1881 Also, if you are tracking -current, you must be subscribed to
1882 freebsd-current@freebsd.org. Make sure that before you update
1883 your sources that you have read and understood all the recent
1884 messages there. If in doubt, please track -stable which has
1885 much fewer pitfalls.
1887 [1] If you have third party modules, such as vmware, you
1888 should disable them at this point so they don't crash your
1891 [3] From the bootblocks, boot -s, and then do
1896 adjkerntz -i # if CMOS is wall time
1897 Also, when doing a major release upgrade, it is required that
1898 you boot into single user mode to do the installworld.
1900 [4] Note: This step is non-optional. Failure to do this step
1901 can result in a significant reduction in the functionality of the
1902 system. Attempting to do it by hand is not recommended and those
1903 that pursue this avenue should read this file carefully, as well
1904 as the archives of freebsd-current and freebsd-hackers mailing lists
1905 for potential gotchas. The -U option is also useful to consider.
1906 See mergemaster(8) for more information.
1908 [5] Usually this step is a no-op. However, from time to time
1909 you may need to do this if you get unknown user in the following
1910 step. It never hurts to do it all the time. You may need to
1911 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1912 install) after the buildworld before this step if you last updated
1913 from current before 20130425 or from -stable before 20130430.
1915 [6] This only deletes old files and directories. Old libraries
1916 can be deleted by "make delete-old-libs", but you have to make
1917 sure that no program is using those libraries anymore.
1919 [8] The new kernel must be able to run existing binaries used by
1920 an installworld. When upgrading across major versions, the new
1921 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1922 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1923 binaries). Failure to do so may leave you with a system that is
1924 hard to boot to recover. A GENERIC kernel will include suitable
1925 compatibility options to run binaries from older branches.
1927 Make sure that you merge any new devices from GENERIC since the
1928 last time you updated your kernel config file.
1930 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1931 "?=" instead of the "=" assignment operator, so that buildworld can
1932 override the CPUTYPE if it needs to.
1934 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1935 not on the command line, or in /etc/make.conf. buildworld will
1936 warn if it is improperly defined.
1939 This file contains a list, in reverse chronological order, of major
1940 breakages in tracking -current. It is not guaranteed to be a complete
1941 list of such breakages, and only contains entries since September 23, 2011.
1942 If you need to see UPDATING entries from before that date, you will need
1943 to fetch an UPDATING file from an older FreeBSD release.
1945 Copyright information:
1947 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1949 Redistribution, publication, translation and use, with or without
1950 modification, in full or in part, in any form or format of this
1951 document are permitted without further permission from the author.
1953 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1954 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1955 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1956 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1957 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1958 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1959 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1960 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1961 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1962 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1963 POSSIBILITY OF SUCH DAMAGE.
1965 Contact Warner Losh if you have any questions about your use of