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 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
20 FreeBSD 13.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
36 8.0.0. Please see the 20141231 entry below for information about
37 prerequisites and upgrading, if you are not already using clang 3.5.0
41 Iflib is no longer unconditionally compiled into the kernel. Drivers
42 using iflib and statically compiled into the kernel, now require
43 the 'device iflib' config option. For the same drivers loaded as
44 modules on kernels not having 'device iflib', the iflib.ko module
45 is loaded automatically.
48 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
49 options no longer exist since r343219 and r343427 respectively;
50 nothing uses them, so they should be just removed from custom
54 r342635 changes the way efibootmgr(8) works by requiring users to add
55 the -b (bootnum) parameter for commands where the bootnum was previously
56 specified with each option. For example 'efibootmgr -B 0001' is now
57 'efibootmgr -B -b 0001'.
60 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
61 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
62 servers that have vfs.nfsd.nfs_privport set will only allow mounts
63 from clients using a reserved port#. Since both the FreeBSD and Linux
64 NFSv4 clients use reserved port#s by default, this should not affect
68 The XLP config has been removed. We can't support 64-bit atomics in this
69 kernel because it is running in 32-bit mode. XLP users must transition
70 to running a 64-bit kernel (XLP64 or XLPN32).
72 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
73 the preferred emulator today and we don't need two different ones.
75 The old sibyte / swarm / Broadcom BCM1250 support has been
76 removed from the mips port.
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 Remove the timed and netdate programs from the base tree. Setting
86 the time with these deamons has been obsolete for over a decade.
89 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
90 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
91 it produces broken binaries when ifuncs are in use. Users needing
92 GNU ld should install the binutils port or package.
95 The BSD crtbegin and crtend code has been enabled by default. It has
96 had extensive testing on amd64, arm64, and i386. It can be disabled
97 by building a world with -DWITHOUT_BSD_CRTBEGIN.
100 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
101 has been converted to a port (misc/ctm) and will be removed from
102 FreeBSD-13. It is available as a package (ctm) for all supported
106 The default newsyslog.conf(5) file has been changed to only include
107 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
108 the filenames end in '.conf' and do not begin with a '.'.
110 You should check the configuration files in these two directories match
111 this naming convention. You can verify which configuration files are
112 being included using the command:
116 Ports for the DRM modules have been simplified. Now, amd64 users should
117 just install the drm-kmod port. All others should install
120 Graphics hardware that's newer than about 2010 usually works with
121 drm-kmod. For hardware older than 2013, however, some users will need
122 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
123 than 2008 usually only works in drm-legacy-kmod. The graphics team can
124 only commit to hardware made since 2013 due to the complexity of the
125 market and difficulty to test all the older cards effectively. If you
126 have hardware supported by drm-kmod, you are strongly encouraged to use
127 that as you will get better support.
129 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
130 elsewhere, the drm and drm2 modules will be eliminated from the src base
131 soon (with a limited exception for arm). Please update to the package asap
132 and report any issues to x11@freebsd.org.
134 Generally, anybody using the drm*-kmod packages should add
135 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
136 cross-threading surprises, especially with automatic driver
137 loading from X11 startup. These will become the defaults in 13-current
141 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
142 custom kernel and module loading configuration files must be updated
143 accordingly. Moreover, interfaces previous presented as ixlvN to the
144 system are now exposed as iavfN and network configuration files must
145 be adjusted as necessary.
148 OpenSSL has been updated to version 1.1.1. This update included
149 additional various API changes througout the base system. It is
150 important to rebuild third-party software after upgrading. The value
151 of __FreeBSD_version has been bumped accordingly.
154 The legacy DRM modules and drivers have now been added to the loader's
155 module blacklist, in favor of loading them with kld_list in rc.conf(5).
156 The module blacklist may be overridden with the loader.conf(5)
157 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
161 The cam(4) based nda(4) driver will be used over nvd(4) by default on
162 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
163 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
164 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
168 Reproducible build mode is now on by default, in preparation for
169 FreeBSD 12.0. This eliminates build metadata such as the user,
170 host, and time from the kernel (and uname), unless the working tree
171 corresponds to a modified checkout from a version control system.
172 The previous behavior can be obtained by setting the /etc/src.conf
173 knob WITHOUT_REPRODUCIBLE_BUILD.
176 The Yarrow CSPRNG has been removed from the kernel as it has not been
177 supported by its designers since at least 2003. Fortuna has been the
178 default since FreeBSD-11.
181 devctl freeze/thaw have gone into the tree, the rc scripts have been
182 updated to use them and devmatch has been changed. You should update
183 kernel, userland and rc scripts all at the same time.
186 The default interpreter has been switched from 4th to Lua.
187 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
188 interpreter. If you have custom FORTH code you will need to set
189 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
190 src.conf for the build. This will create default hard links between
191 loader and loader_4th instead of loader and loader_lua, the new default.
192 If you are using UEFI it will create the proper hard link to loader.efi.
194 bhyve uses userboot.so. It remains 4th-only until some issues are solved
195 regarding coexisting with multiple versions of FreeBSD are resolved.
198 ls(1) now respects the COLORTERM environment variable used in other
199 systems and software to indicate that a colored terminal is both
200 supported and desired. If ls(1) is suddenly emitting colors, they may
201 be disabled again by either removing the unwanted COLORTERM from your
202 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
203 may not be observed in a future release.
206 The default pager for most commands has been changed to "less". To
207 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
211 The jedec_ts(4) driver has been removed. A superset of its functionality
212 is available in the jedec_dimm(4) driver, and the manpage for that
213 driver includes migration instructions. If you have "device jedec_ts"
214 in your kernel configuration file, it must be removed.
217 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
218 This should have no effect if the kernel is booted via BIOS/legacy boot.
219 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
220 has a buggy firmware that prevents a successful boot due to use of
224 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
225 support has been removed from the tree. These ports were
226 obsolete and/or known to be broken for many years.
229 loader.efi has been augmented to participate more fully in the
230 UEFI boot manager protocol. loader.efi will now look at the
231 BootXXXX environment variable to determine if a specific kernel
232 or root partition was specified. XXXX is derived from BootCurrent.
233 efibootmgr(8) manages these standard UEFI variables.
236 zfsloader's functionality has now been folded into loader.
237 zfsloader is no longer necessary once you've updated your
238 boot blocks. For a transition period, we will install a
239 hardlink for zfsloader to loader to allow a smooth transition
240 until the boot blocks can be updated (hard link because old
241 zfs boot blocks don't understand symlinks).
244 ARM64 now have efifb support, if you want to have serial console
245 on your arm64 board when an screen is connected and the bootloader
246 setup a framebuffer for us to use, just add :
250 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
251 an screen connected as the firmware will setup a framebuffer are that
252 u-boot will expose as an EFI framebuffer.
255 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
256 or take steps to update /etc/passwd before doing installworld on
257 existing systems. Do not skip the "mergemaster -Fp" step before
258 installworld, as described in the update procedures near the bottom
259 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
260 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
261 the ntp config file contain options that change file/dir locations.
262 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
263 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
264 taking steps to ensure that all required files/dirs are accessible
268 Big endian arm support has been removed.
271 The static environment setup in kernel configs is no longer mutually
272 exclusive with the loader(8) environment by default. In order to
273 restore the previous default behavior of disabling the loader(8)
274 environment if a static environment is present, you must specify
275 loader_env.disabled=1 in the static environment.
278 The ABI of syscalls used by management tools like sockstat and
279 netstat has been broken to allow 32-bit binaries to work on
280 64-bit kernels without modification. These programs will need
281 to match the kernel in order to function. External programs may
282 require minor modifications to accommodate a change of type in
283 structures from pointers to 64-bit virtual addresses.
286 On i386 and amd64 atomics are now inlined. Out of tree modules using
287 atomics will need to be rebuilt.
290 The '%I' format in the kern.corefile sysctl limits the number of
291 core files that a process can generate to the number stored in the
292 debug.ncores sysctl. The '%I' format is replaced by the single digit
293 index. Previously, if all indexes were taken the kernel would overwrite
294 only a core file with the highest index in a filename.
295 Currently the system will create a new core file if there is a free
296 index or if all slots are taken it will overwrite the oldest one.
299 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
300 6.0.1. Please see the 20141231 entry below for information about
301 prerequisites and upgrading, if you are not already using clang 3.5.0
305 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
306 needed to be changed to work with it. This change was made with r335763
307 and requires a mergemaster / etcupdate / etc to update the installed file.
310 r334930 changed the interface between the NFS modules, so they all
311 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
314 As of r334391 lld is the default amd64 system linker; it is installed
315 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
319 The kernel / userland interface for devinfo changed, so you'll
320 need a new kernel and userland as a pair for it to work (rebuilding
321 lib/libdevinfo is all that's required). devinfo and devmatch will
322 not work, but everything else will when there's a mismatch.
325 The on-disk format for hwpmc callchain records has changed to include
326 threadid corresponding to a given record. This changes the field offsets
327 and thus requires that libpmcstat be rebuilt before using a kernel
331 The vxge(4) driver has been removed. This driver was introduced into
332 HEAD one week before the Exar left the Ethernet market and is not
333 known to be used. If you have device vxge in your kernel config file
337 The amd64 kernel now requires a ld that supports ifunc to produce a
338 working kernel, either lld or a newer binutils. lld is built by default
339 on amd64, and the 'buildkernel' target uses it automatically. However,
340 it is not the default linker, so building the kernel the traditional
341 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
342 binutils port/package). lld will soon be default, and this requirement
345 NOTE: As of r334391 lld is the default system linker on amd64, and no
346 workaround is necessary.
349 The nxge(4) driver has been removed. This driver was for PCI-X 10g
350 cards made by s2io/Neterion. The company was aquired by Exar and
351 no longer sells or supports Ethernet products. If you have device
352 nxge in your kernel config file it must be removed.
355 The tz database (tzdb) has been updated to 2018e. This version more
356 correctly models time stamps in time zones with negative DST such as
357 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
358 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
359 time zone abbreviations and the tm_isdst flag.
362 The ixgb(4) driver has been removed. This driver was for an early and
363 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
364 quickly shifted to the long lived ixgbe family. If you have device
365 ixgb in your kernel config file it must be removed.
368 The lmc(4) driver has been removed. This was a WAN interface
369 card that was already reportedly rare in 2003, and had an ambiguous
370 license. If you have device lmc in your kernel config file it must
374 Support for Arcnet networks has been removed. If you have device
375 arcnet or device cm in your kernel config file they must be
379 Support for FDDI networks has been removed. If you have device
380 fddi or device fpa in your kernel config file they must be
384 In addition to supporting RFC 3164 formatted messages, the
385 syslogd(8) service is now capable of parsing RFC 5424 formatted
386 log messages. The main benefit of using RFC 5424 is that clients
387 may now send log messages with timestamps containing year numbers,
388 microseconds and time zone offsets.
390 Similarly, the syslog(3) C library function has been altered to
391 send RFC 5424 formatted messages to the local system logging
392 daemon. On systems using syslogd(8), this change should have no
393 negative impact, as long as syslogd(8) and the C library are
394 updated at the same time. On systems using a different system
395 logging daemon, it may be necessary to make configuration
396 adjustments, depending on the software used.
398 When using syslog-ng, add the 'syslog-protocol' flag to local
399 input sources to enable parsing of RFC 5424 formatted messages:
402 unix-dgram("/var/run/log" flags(syslog-protocol));
405 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
406 of the 'imuxsock' module to let messages be processed by the
407 regular RFC 3164/5424 parsing pipeline:
409 module(load="imuxsock" SysSock.UseSpecialParser="off")
411 Do note that these changes only affect communication between local
412 applications and syslogd(8). The format that syslogd(8) uses to
413 store messages on disk or forward messages to other systems
414 remains unchanged. syslogd(8) still uses RFC 3164 for these
415 purposes. Options to customize this behaviour will be added in the
416 future. Utilities that process log files stored in /var/log are
417 thus expected to continue to function as before.
419 __FreeBSD_version has been incremented to 1200061 to denote this
423 Support for token ring networks has been removed. If you
424 have "device token" in your kernel config you should remove
425 it. No device drivers supported token ring.
428 makefs was modified to be able to tag ISO9660 El Torito boot catalog
429 entries as EFI instead of overloading the i386 tag as done previously.
430 The amd64 mkisoimages.sh script used to build amd64 ISO images for
431 release was updated to use this. This may mean that makefs must be
432 updated before "make cdrom" can be run in the release directory. This
433 should be as simple as:
435 $ cd $SRCDIR/usr.sbin/makefs
436 $ make depend all install
439 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
440 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
441 Co-existance for the transition period will come shortly. Booting is a
442 complex environment and test coverage for Lua-enabled loaders has been
443 thin, so it would be prudent to assume it might not work and make
444 provisions for backup boot methods.
447 devmatch functionality has been turned on in devd. It will automatically
448 load drivers for unattached devices. This may cause unexpected drivers to
449 be loaded. Please report any problems to current@ and imp@freebsd.org.
452 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
453 6.0.0. Please see the 20141231 entry below for information about
454 prerequisites and upgrading, if you are not already using clang 3.5.0
458 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
459 This means it is used to link the kernel and userland libraries and
460 executables, but is not yet installed as /usr/bin/ld by default.
462 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
463 WITHOUT_LLD_BOOTSTRAP=yes
466 On i386, pmtimer has been removed. Its functionality has been folded
467 into apm. It was a no-op on ACPI in current for a while now (but was still
468 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
469 from kernel config files.
472 The use of RSS hash from the network card aka flowid has been
473 disabled by default for lagg(4) as it's currently incompatible with
474 the lacp and loadbalance protocols.
476 This can be re-enabled by setting the following in loader.conf:
477 net.link.lagg.default_use_flowid="1"
480 The SW_WATCHDOG option is no longer necessary to enable the
481 hardclock-based software watchdog if no hardware watchdog is
482 configured. As before, SW_WATCHDOG will cause the software
483 watchdog to be enabled even if a hardware watchdog is configured.
486 r326887 fixes the issue described in the 20171214 UPDATING entry.
487 r326888 flips the switch back to building GELI support always.
490 r362593 broke ZFS + GELI support for reasons unknown. However,
491 it also broke ZFS support generally, so GELI has been turned off
492 by default as the lesser evil in r326857. If you boot off ZFS and/or
493 GELI, it might not be a good time to update.
496 PowerPC users must update loader(8) by rebuilding world before
497 installing a new kernel, as the protocol connecting them has
498 changed. Without the update, loader metadata will not be passed
499 successfully to the kernel and users will have to enter their
500 root partition at the kernel mountroot prompt to continue booting.
501 Newer versions of loader can boot old kernels without issue.
504 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
505 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
506 to WITH/OUT_LOADER_GELI.
509 The naive and non-compliant support of posix_fallocate(2) in ZFS
510 has been removed as of r325320. The system call now returns EINVAL
511 when used on a ZFS file. Although the new behavior complies with the
512 standard, some consumers are not prepared to cope with it.
513 One known victim is lld prior to r325420.
516 Building in a FreeBSD src checkout will automatically create object
517 directories now rather than store files in the current directory if
518 'make obj' was not ran. Calling 'make obj' is no longer necessary.
519 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
520 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
524 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
525 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
526 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
527 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
528 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
529 The UNIFIED_OBJDIR option is a transitional feature that will be
530 removed for 12.0 release; please migrate to the new format for any
531 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
532 than hardcoding paths.
535 The native-xtools target no longer installs the files by default to the
536 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
537 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
540 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
541 options are changing from controlling the build if defined / undefined
542 to controlling the build with explicit 'yes' or 'no' values. They will
543 shift to WITH/WITHOUT options to match other options in the system.
546 libstand has turned into a private library for sys/boot use only.
547 It is no longer supported as a public interface outside of sys/boot.
550 The arm port has split armv6 into armv6 and armv7. armv7 is now
551 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
552 and are running a kernel from before r324363, you will need to add
553 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
556 When building multiple kernels using KERNCONF, non-existent KERNCONF
557 files will produce an error and buildkernel will fail. Previously
558 missing KERNCONF files silently failed giving no indication as to
559 why, only to subsequently discover during installkernel that the
560 desired kernel was never built in the first place.
563 The default serial number format for CTL LUNs has changed. This will
564 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
565 or iSCSI clients care about their LUNs' serial numbers. Users who
566 require serial number stability should hardcode serial numbers in
570 For 32-bit arm compiled for hard-float support, soft-floating point
571 binaries now always get their shared libraries from
572 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
573 /usr/libsoft also existed). Only users with a hard-float ld.so, but
574 soft-float everything else should be affected.
577 The geli password typed at boot is now hidden. To restore the previous
578 behavior, see geli(8) for configuration options.
581 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
582 sysctl values. Minor nit, but requires a rebuild of both world/kernel
586 "make check" behavior (made in ^/head@r295380) has been changed to
587 execute from a limited sandbox, as opposed to executing from
591 - The "beforecheck" and "aftercheck" targets are now specified.
592 - ${CHECKDIR} (added in commit noted above) has been removed.
593 - Legacy behavior can be enabled by setting
594 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
596 If the limited sandbox mode is enabled, "make check" will execute
597 "make distribution", then install, execute the tests, and clean up the
598 sandbox if successful.
600 The "make distribution" and "make install" targets are typically run as
601 root to set appropriate permissions and ownership at installation time.
602 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
603 environment if executing "make check" with limited sandbox mode using
604 an unprivileged user.
607 Since the switch to GPT disk labels, fsck for UFS/FFS has been
608 unable to automatically find alternate superblocks. As of r322297,
609 the information needed to find alternate superblocks has been
610 moved to the end of the area reserved for the boot block.
611 Filesystems created with a newfs of this vintage or later
612 will create the recovery information. If you have a filesystem
613 created prior to this change and wish to have a recovery block
614 created for your filesystem, you can do so by running fsck in
615 foreground mode (i.e., do not use the -p or -y options). As it
616 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
617 to which you should answer yes.
620 As of r321665, an NFSv4 server configuration that services
621 Kerberos mounts or clients that do not support the uid/gid in
622 owner/owner_group string capability, must explicitly enable
623 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
624 machine's /etc/rc.conf file.
627 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
628 Please see the 20141231 entry below for information about prerequisites
629 and upgrading, if you are not already using clang 3.5.0 or higher.
632 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
633 r-commands (rlogin, rsh, etc.) to be built with the base system.
636 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
637 a very major ABI incompatible change, so users of FreeBSD/powerpc must
638 be careful when performing source upgrades. It is best to run
639 'make installworld' from an alternate root system, either a live
640 CD/memory stick, or a temporary root partition. Additionally, all ports
641 must be recompiled. powerpc64 is largely unaffected, except in the case
642 of 32-bit compatibility. All 32-bit binaries will be affected.
645 Forward compatibility for the "ino64" project have been committed. This
646 will allow most new binaries to run on older kernels in a limited
647 fashion. This prevents many of the common foot-shooting actions in the
648 upgrade as well as the limited ability to roll back the kernel across
649 the ino64 upgrade. Complicated use cases may not work properly, though
650 enough simpler ones work to allow recovery in most situations.
653 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
654 if you require the GPL compiler.
657 The internal ABI used for communication between the NFS kernel modules
658 was changed by r320085, so __FreeBSD_version was bumped to
659 ensure all the NFS related modules are updated together.
662 The ABI of struct event was changed by extending the data
663 member to 64bit and adding ext fields. For upgrade, same
664 precautions as for the entry 20170523 "ino64" must be
668 The GNU roff toolchain has been removed from base. To render manpages
669 which are not supported by mandoc(1), man(1) can fallback on GNU roff
670 from ports (and recommends to install it).
671 To render roff(7) documents, consider using GNU roff from ports or the
672 heirloom doctools roff toolchain from ports via pkg install groff or
673 via pkg install heirloom-doctools.
676 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
677 smaller runtime footprint builds. This is useful for embedded systems
678 which only require one chipset support.
680 If you load it as a module, make sure this is in /boot/loader.conf:
684 This will load the HAL, all chip/RF backends and if_ath_pci.
685 If you have if_ath_pci in /boot/loader.conf, ensure it is after
686 if_ath or it will not load any HAL chipset support.
688 If you want to selectively load things (eg on ye cheape ARM/MIPS
689 platforms where RAM is at a premium) you should:
692 * load the chip modules in question
693 * load ath_rate, ath_dfs
695 * load if_ath_pci and/or if_ath_ahb depending upon your particular
696 bus bind type - this is where probe/attach is done.
698 For further comments/feedback, poke adrian@ .
701 The "ino64" 64-bit inode project has been committed, which extends
702 a number of types to 64 bits. Upgrading in place requires care and
703 adherence to the documented upgrade procedure.
705 If using a custom kernel configuration ensure that the
706 COMPAT_FREEBSD11 option is included (as during the upgrade the
707 system will be running the ino64 kernel with the existing world).
709 For the safest in-place upgrade begin by removing previous build
710 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
711 full procedure documented below under the heading "To rebuild
712 everything and install it on the current system." Specifically,
713 a reboot is required after installing the new kernel before
717 The NATM framework including the en(4), fatm(4), hatm(4), and
718 patm(4) devices has been removed. Consumers should plan a
719 migration before the end-of-life date for FreeBSD 11.
722 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
723 diff has not been implemented, if those are needed a newer version of
724 GNU diff is available via the diffutils package under the gdiff name.
727 As of r316810 for ipfilter, keep frags is no longer assumed when
728 keep state is specified in a rule. r316810 aligns ipfilter with
729 documentation in man pages separating keep frags from keep state.
730 This allows keep state to be specified without forcing keep frags
731 and allows keep frags to be specified independently of keep state.
732 To maintain previous behaviour, also specify keep frags with
733 keep state (as documented in ipf.conf.5).
736 arm64 builds now use the base system LLD 4.0.0 linker by default,
737 instead of requiring that the aarch64-binutils port or package be
738 installed. To continue using aarch64-binutils, set
739 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
742 The UDP optimization in entry 20160818 that added the sysctl
743 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
744 packets will no longer be treated as L3 broadcast packets.
747 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
748 use any explicitly assigned loopback address available in the jail
749 instead of using the first assigned address of the jail.
752 The ctl.ko module no longer implements the iSCSI target frontend:
753 cfiscsi.ko does instead.
755 If building cfiscsi.ko as a kernel module, the module can be loaded
756 via one of the following methods:
757 - `cfiscsi_load="YES"` in loader.conf(5).
758 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
759 - ctladm(8)/ctld(8), when compiled with iSCSI support
760 (`WITH_ISCSI=yes` in src.conf(5))
762 Please see cfiscsi(4) for more details.
765 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
766 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
767 same source (previously, the dependency of mmcsd.ko on mmc.ko was
768 missing, but mmcsd.ko now will refuse to load if it is incompatible
772 The syntax of ipfw(8) named states was changed to avoid ambiguity.
773 If you have used named states in the firewall rules, you need to modify
774 them after installworld and before rebooting. Now named states must
775 be prefixed with colon.
778 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
779 removed as the userland we provide cannot use them. The KMS version
780 (sys/dev/drm2) supports the same hardware.
783 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
784 Please see the 20141231 entry below for information about prerequisites
785 and upgrading, if you are not already using clang 3.5.0 or higher.
788 The code that provides support for ZFS .zfs/ directory functionality
789 has been reimplemented. It's not possible now to create a snapshot
790 by mkdir under .zfs/snapshot/. That should be the only user visible
794 EISA bus support has been removed. The WITH_EISA option is no longer
798 MCA bus support has been removed.
801 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
802 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
805 The EM_MULTIQUEUE kernel configuration option is deprecated now that
806 the em(4) driver conforms to iflib specifications.
809 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
810 IFLIB. If you have a custom kernel configuration that excludes em(4)
811 but you use igb(4), you need to re-add em(4) to your custom configuration.
814 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
815 Please see the 20141231 entry below for information about prerequisites
816 and upgrading, if you are not already using clang 3.5.0 or higher.
819 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
820 Please see the 20141231 entry below for information about prerequisites
821 and upgrading, if you are not already using clang 3.5.0 or higher.
824 The layout of the pmap structure has changed for powerpc to put the pmap
825 statistics at the front for all CPU variations. libkvm(3) and all tools
826 that link against it need to be recompiled.
829 isl(4) and cyapa(4) drivers now require a new driver,
830 chromebook_platform(4), to work properly on Chromebook-class hardware.
831 On other types of hardware the drivers may need to be configured using
832 device hints. Please see the corresponding manual pages for details.
835 The urtwn(4) driver was merged into rtwn(4) and now consists of
836 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
838 Also, firmware for RTL8188CE was renamed due to possible name
839 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
842 GNU rcs has been removed from base. It is available as packages:
843 - rcs: Latest GPLv3 GNU rcs version.
844 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
848 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
849 modules now requires that the kernel configuration contain the
850 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
853 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
854 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
857 Relocatable object files with the extension of .So have been renamed
858 to use an extension of .pico instead. The purpose of this change is
859 to avoid a name clash with shared libraries on case-insensitive file
860 systems. On those file systems, foo.So is the same file as foo.so.
863 GNU rcs has been turned off by default. It can (temporarily) be built
864 again by adding WITH_RCS knob in src.conf.
865 Otherwise, GNU rcs is available from packages:
866 - rcs: Latest GPLv3 GNU rcs version.
867 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
870 The backup_uses_rcs functionality has been removed from rc.subr.
873 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
874 two separate components, QUEUE_MACRO_DEBUG_TRACE and
875 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
876 QUEUE_MACRO_DEBUG behavior.
879 r304787 changed some ioctl interfaces between the iSCSI userspace
880 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
881 rebuilt to work with new kernels. __FreeBSD_version has been bumped
885 The UDP receive code has been updated to only treat incoming UDP
886 packets that were addressed to an L2 broadcast address as L3
887 broadcast packets. It is not expected that this will affect any
888 standards-conforming UDP application. The new behaviour can be
889 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
893 Remove the openbsd_poll system call.
894 __FreeBSD_version has been bumped because of this.
897 The stable/11 branch has been created from head@r302406.
900 The libc stub for the pipe(2) system call has been replaced with
901 a wrapper that calls the pipe2(2) system call and the pipe(2)
902 system call is now only implemented by the kernels that include
903 "options COMPAT_FREEBSD10" in their config file (this is the
904 default). Users should ensure that this option is enabled in
905 their kernel or upgrade userspace to r302092 before upgrading their
909 CAM will now strip leading spaces from SCSI disks' serial numbers.
910 This will affect users who create UFS filesystems on SCSI disks using
911 those disk's diskid device nodes. For example, if /etc/fstab
912 previously contained a line like
913 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
914 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
915 transforms like gmirror may also be affected. ZFS users should
919 The bitstring(3) API has been updated with new functionality and
920 improved performance. But it is binary-incompatible with the old API.
921 Objects built with the new headers may not be linked against objects
922 built with the old headers.
925 The brk and sbrk functions have been removed from libc on arm64.
926 Binutils from ports has been updated to not link to these
927 functions and should be updated to the latest version before
928 installing a new libc.
931 The armv6 port now defaults to hard float ABI. Limited support
932 for running both hardfloat and soft float on the same system
933 is available using the libraries installed with -DWITH_LIBSOFT.
934 This has only been tested as an upgrade path for installworld
935 and packages may fail or need manual intervention to run. New
936 packages will be needed.
938 To update an existing self-hosted armv6hf system, you must add
939 TARGET_ARCH=armv6 on the make command line for both the build
940 and the install steps.
943 Kernel modules compiled outside of a kernel build now default to
944 installing to /boot/modules instead of /boot/kernel. Many kernel
945 modules built this way (such as those in ports) already overrode
946 KMODDIR explicitly to install into /boot/modules. However,
947 manually building and installing a module from /sys/modules will
948 now install to /boot/modules instead of /boot/kernel.
951 The CAM I/O scheduler has been committed to the kernel. There should be
952 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
953 list of known rogues that claim support for this but actually corrupt
954 data is believed to be complete, be on the lookout for data
955 corruption. The known rogue list is believed to be complete:
957 o Crucial MX100, M550 drives with MU01 firmware.
958 o Micron M510 and M550 drives with MU01 firmware.
959 o Micron M500 prior to MU07 firmware
960 o Samsung 830, 840, and 850 all firmwares
961 o FCCT M500 all firmwares
963 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
964 with working NCQ TRIM. For Micron branded drives, see your sales rep for
965 updated firmware. Black listed drives will work correctly because these
966 drives work correctly so long as no NCQ TRIMs are sent to them. Given
967 this list is the same as found in Linux, it's believed there are no
968 other rogues in the market place. All other models from the above
971 To be safe, if you are at all concerned, you can quirk each of your
972 drives to prevent NCQ from being sent by setting:
973 kern.cam.ada.X.quirks="0x2"
974 in loader.conf. If the drive requires the 4k sector quirk, set the
978 The FAST_DEPEND build option has been removed and its functionality is
979 now the one true way. The old mkdep(1) style of 'make depend' has
980 been removed. See 20160311 for further details.
983 Resource range types have grown from unsigned long to uintmax_t. All
984 drivers, and anything using libdevinfo, need to be recompiled.
987 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
988 builds. It no longer runs mkdep(1) during 'make depend', and the
989 'make depend' stage can safely be skipped now as it is auto ran
990 when building 'make all' and will generate all SRCS and DPSRCS before
991 building anything else. Dependencies are gathered at compile time with
992 -MF flags kept in separate .depend files per object file. Users should
993 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
997 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
998 kernel modules. Therefore, if you load any kernel modules at boot time,
999 please install the boot loaders after you install the kernel, but before
1003 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1004 make installkernel KERNCONF=YOUR_KERNEL_HERE
1005 make -C sys/boot install
1006 <reboot in single user>
1008 Then follow the usual steps, described in the General Notes section,
1012 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1013 see the 20141231 entry below for information about prerequisites and
1014 upgrading, if you are not already using clang 3.5.0 or higher.
1017 The AIO subsystem is now a standard part of the kernel. The
1018 VFS_AIO kernel option and aio.ko kernel module have been removed.
1019 Due to stability concerns, asynchronous I/O requests are only
1020 permitted on sockets and raw disks by default. To enable
1021 asynchronous I/O requests on all file types, set the
1022 vfs.aio.enable_unsafe sysctl to a non-zero value.
1025 The ELF object manipulation tool objcopy is now provided by the
1026 ELF Tool Chain project rather than by GNU binutils. It should be a
1027 drop-in replacement, with the addition of arm64 support. The
1028 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1029 to obtain the GNU version if necessary.
1032 Building ZFS pools on top of zvols is prohibited by default. That
1033 feature has never worked safely; it's always been prone to deadlocks.
1034 Using a zvol as the backing store for a VM guest's virtual disk will
1035 still work, even if the guest is using ZFS. Legacy behavior can be
1036 restored by setting vfs.zfs.vol.recursive=1.
1039 The NONE and HPN patches has been removed from OpenSSH. They are
1040 still available in the security/openssh-portable port.
1043 With the addition of ypldap(8), a new _ypldap user is now required
1044 during installworld. "mergemaster -p" can be used to add the user
1045 prior to installworld, as documented in the handbook.
1048 The tftp loader (pxeboot) now uses the option root-path directive. As a
1049 consequence it no longer looks for a pxeboot.4th file on the tftp
1050 server. Instead it uses the regular /boot infrastructure as with the
1054 The code to start recording plug and play data into the modules has
1055 been committed. While the old tools will properly build a new kernel,
1056 a number of warnings about "unknown metadata record 4" will be produced
1057 for an older kldxref. To avoid such warnings, make sure to rebuild
1058 the kernel toolchain (or world). Make sure that you have r292078 or
1059 later when trying to build 292077 or later before rebuilding.
1062 Debug data files are now built by default with 'make buildworld' and
1063 installed with 'make installworld'. This facilitates debugging but
1064 requires more disk space both during the build and for the installed
1065 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1069 r291527 changed the internal interface between the nfsd.ko and
1070 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1071 __FreeBSD_version has been bumped because of this.
1074 Add support for unicode collation strings leads to a change of
1075 order of files listed by ls(1) for example. To get back to the old
1076 behaviour, set LC_COLLATE environment variable to "C".
1078 Databases administrators will need to reindex their databases given
1079 collation results will be different.
1081 Due to a bug in install(1) it is recommended to remove the ancient
1082 locales before running make installworld.
1084 rm -rf /usr/share/locale/*
1087 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1088 libcrypto.so.7 or libssl.so.7 must be recompiled.
1091 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1092 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1093 should be replaced with isp_2400 and isp_2500 modules respectively.
1096 The build previously allowed using 'make -n' to not recurse into
1097 sub-directories while showing what commands would be executed, and
1098 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1099 and 'make -N' will not.
1102 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1103 and etcupdate will now use this file. A custom sendmail.cf is now
1104 updated via this mechanism rather than via installworld. If you had
1105 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1106 want to remove the exclusion or change it to "always install".
1107 /etc/mail/sendmail.cf is now managed the same way regardless of
1108 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1109 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1112 Compatibility shims for legacy ATA device names have been removed.
1113 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1114 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1115 environment variables, /dev/ad* and /dev/ar* symbolic links.
1118 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1119 Please see the 20141231 entry below for information about prerequisites
1120 and upgrading, if you are not already using clang 3.5.0 or higher.
1123 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1124 and renamed from .symbols to .debug. This reduces the size requirements
1125 on the boot partition or file system and provides consistency with
1126 userland debug files.
1128 When using the supported kernel installation method the
1129 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1130 as is done with /boot/kernel.
1132 Developers wishing to maintain the historical behavior of installing
1133 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1136 The wireless drivers had undergone changes that remove the 'parent
1137 interface' from the ifconfig -l output. The rc.d network scripts
1138 used to check presence of a parent interface in the list, so old
1139 scripts would fail to start wireless networking. Thus, etcupdate(3)
1140 or mergemaster(8) run is required after kernel update, to update your
1141 rc.d scripts in /etc.
1144 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1145 These configurations are now automatically interpreted as
1146 'scrub fragment reassemble'.
1149 Kernel-loadable modules for the random(4) device are back. To use
1150 them, the kernel must have
1153 options RANDOM_LOADABLE
1155 kldload(8) can then be used to load random_fortuna.ko
1156 or random_yarrow.ko. Please note that due to the indirect
1157 function calls that the loadable modules need to provide,
1158 the build-in variants will be slightly more efficient.
1160 The random(4) kernel option RANDOM_DUMMY has been retired due to
1161 unpopularity. It was not all that useful anyway.
1164 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1165 Control over building the ELF Tool Chain tools is now provided by
1166 the WITHOUT_TOOLCHAIN knob.
1169 The polarity of Pulse Per Second (PPS) capture events with the
1170 uart(4) driver has been corrected. Prior to this change the PPS
1171 "assert" event corresponded to the trailing edge of a positive PPS
1172 pulse and the "clear" event was the leading edge of the next pulse.
1174 As the width of a PPS pulse in a typical GPS receiver is on the
1175 order of 1 millisecond, most users will not notice any significant
1176 difference with this change.
1178 Anyone who has compensated for the historical polarity reversal by
1179 configuring a negative offset equal to the pulse width will need to
1180 remove that workaround.
1183 The default group assigned to /dev/dri entries has been changed
1184 from 'wheel' to 'video' with the id of '44'. If you want to have
1185 access to the dri devices please add yourself to the video group
1188 # pw groupmod video -m $USER
1191 The menu.rc and loader.rc files will now be replaced during
1192 upgrades. Please migrate local changes to menu.rc.local and
1193 loader.rc.local instead.
1196 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1197 strings and strip have been removed. The src.conf(5) knob
1198 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1201 As ZFS requires more kernel stack pages than is the default on some
1202 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1203 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1205 Please consider using 'options KSTACK_PAGES=X' where X is greater
1206 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1209 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1210 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1211 default, i.e., they will not contain "::". For example, instead
1212 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1213 to have a more specific match, such as different map entries for
1214 IPv6:0:0 vs IPv6:0. This change requires that configuration
1215 data (including maps, files, classes, custom ruleset, etc.) must
1216 use the same format, so make certain such configuration data is
1217 upgrading. As a very simple check search for patterns like
1218 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1219 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1220 the cf option UseCompressedIPv6Addresses.
1223 The default kernel entropy-processing algorithm is now
1224 Fortuna, replacing Yarrow.
1226 Assuming you have 'device random' in your kernel config
1227 file, the configurations allow a kernel option to override
1228 this default. You may choose *ONE* of:
1230 options RANDOM_YARROW # Legacy /dev/random algorithm.
1231 options RANDOM_DUMMY # Blocking-only driver.
1233 If you have neither, you get Fortuna. For most people,
1234 read no further, Fortuna will give a /dev/random that works
1235 like it always used to, and the difference will be irrelevant.
1237 If you remove 'device random', you get *NO* kernel-processed
1238 entropy at all. This may be acceptable to folks building
1239 embedded systems, but has complications. Carry on reading,
1240 and it is assumed you know what you need.
1242 *PLEASE* read random(4) and random(9) if you are in the
1243 habit of tweaking kernel configs, and/or if you are a member
1244 of the embedded community, wanting specific and not-usual
1245 behaviour from your security subsystems.
1247 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1248 random', you will NOT have a functioning /dev/random, and
1249 many cryptographic features will not work, including SSH.
1250 You may also find strange behaviour from the random(3) set
1251 of library functions, in particular sranddev(3), srandomdev(3)
1252 and arc4random(3). The reason for this is that the KERN_ARND
1253 sysctl only returns entropy if it thinks it has some to
1254 share, and with RANDOM_DUMMY or no 'device random' this
1258 An additional fix for the issue described in the 20150614 sendmail
1259 entry below has been committed in revision 284717.
1262 FreeBSD's old make (fmake) has been removed from the system. It is
1263 available as the devel/fmake port or via pkg install fmake.
1266 The fix for the issue described in the 20150614 sendmail entry
1267 below has been committed in revision 284436. The work
1268 around described in that entry is no longer needed unless the
1269 default setting is overridden by a confDH_PARAMETERS configuration
1270 setting of '5' or pointing to a 512 bit DH parameter file.
1273 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1274 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1275 and devel/kyua to version 0.20+ and adjust any calling code to work
1276 with Kyuafile and kyua.
1279 The import of openssl to address the FreeBSD-SA-15:10.openssl
1280 security advisory includes a change which rejects handshakes
1281 with DH parameters below 768 bits. sendmail releases prior
1282 to 8.15.2 (not yet released), defaulted to a 512 bit
1283 DH parameter setting for client connections. To work around
1284 this interoperability, sendmail can be configured to use a
1285 2048 bit DH parameter by:
1287 1. Edit /etc/mail/`hostname`.mc
1288 2. If a setting for confDH_PARAMETERS does not exist or
1289 exists and is set to a string beginning with '5',
1290 replace it with '2'.
1291 3. If a setting for confDH_PARAMETERS exists and is set to
1292 a file path, create a new file with:
1293 openssl dhparam -out /path/to/file 2048
1294 4. Rebuild the .cf file:
1295 cd /etc/mail/; make; make install
1296 5. Restart sendmail:
1297 cd /etc/mail/; make restart
1299 A sendmail patch is coming, at which time this file will be
1303 Generation of legacy formatted entries have been disabled by default
1304 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1305 entries were converted to use the new format by default when the new,
1306 machine independent format have been added and supported since FreeBSD
1309 Please see the pwd_mkdb(8) manual page for further details.
1312 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1313 20141231 entry below for information about prerequisites and upgrading,
1314 if you are not already using 3.5.0 or higher.
1317 TI platform code switched to using vendor DTS files and this update
1318 may break existing systems running on Beaglebone, Beaglebone Black,
1321 - dtb files should be regenerated/reinstalled. Filenames are the
1322 same but content is different now
1323 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1324 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1325 addressing scheme is now pin 25 on /dev/gpioc3.
1326 - Pandaboard: /etc/ttys should be updated, serial console device is
1327 now /dev/ttyu2, not /dev/ttyu0
1330 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1331 If you need the GNU extension from groff soelim(1), install groff
1332 from package: pkg install groff, or via ports: textproc/groff.
1335 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1336 defined in symlink(7); previously symlinks were silently ignored.
1339 The const qualifier has been removed from iconv(3) to comply with
1340 POSIX. The ports tree is aware of this from r384038 onwards.
1343 Libraries specified by LIBADD in Makefiles must have a corresponding
1344 DPADD_<lib> variable to ensure correct dependencies. This is now
1345 enforced in src.libnames.mk.
1348 From legacy ata(4) driver was removed support for SATA controllers
1349 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1350 Kernel modules ataahci and ataadaptec were removed completely,
1351 replaced by ahci and mvs modules respectively.
1354 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1355 the 20141231 entry below for information about prerequisites and
1356 upgrading, if you are not already using 3.5.0 or higher.
1359 The 32-bit PowerPC kernel has been changed to a position-independent
1360 executable. This can only be booted with a version of loader(8)
1361 newer than January 31, 2015, so make sure to update both world and
1362 kernel before rebooting.
1365 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1366 but before r278950, the RNG was not seeded properly. Immediately
1367 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1368 ssh keys or openssl keys) that were generated w/ a kernel from that
1369 range. This does not affect programs that directly used /dev/random
1370 or /dev/urandom. All userland uses of arc4random(3) are affected.
1373 The autofs(4) ABI was changed in order to restore binary compatibility
1374 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1375 with the new kernel.
1378 The powerpc64 kernel has been changed to a position-independent
1379 executable. This can only be booted with a new version of loader(8),
1380 so make sure to update both world and kernel before rebooting.
1383 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1384 only release, no new features have been added. Please see the 20141231
1385 entry below for information about prerequisites and upgrading, if you
1386 are not already using 3.5.0.
1389 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1390 taken from the ELF Tool Chain project rather than GNU binutils. They
1391 should be drop-in replacements, with the addition of arm64 support.
1392 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1393 binutils tools, if necessary. See 20150805 for updated information.
1396 The default Unbound configuration now enables remote control
1397 using a local socket. Users who have already enabled the
1398 local_unbound service should regenerate their configuration
1399 by running "service local_unbound setup" as root.
1402 The GNU texinfo and GNU info pages have been removed.
1403 To be able to view GNU info pages please install texinfo from ports.
1406 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1408 As of this release, a prerequisite for building clang, llvm and lldb is
1409 a C++11 capable compiler and C++11 standard library. This means that to
1410 be able to successfully build the cross-tools stage of buildworld, with
1411 clang as the bootstrap compiler, your system compiler or cross compiler
1412 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1413 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1416 On any standard FreeBSD 10.x or 11.x installation, where clang and
1417 libc++ are on by default (that is, on x86 or arm), this should work out
1420 On 9.x installations where clang is enabled by default, e.g. on x86 and
1421 powerpc, libc++ will not be enabled by default, so libc++ should be
1422 built (with clang) and installed first. If both clang and libc++ are
1423 missing, build clang first, then use it to build libc++.
1425 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1426 the instructions for 9.x above.
1428 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1429 default, and do not build clang.
1431 Many embedded systems are resource constrained, and will not be able to
1432 build clang in a reasonable time, or in some cases at all. In those
1433 cases, cross building bootable systems on amd64 is a workaround.
1435 This new version of clang introduces a number of new warnings, of which
1436 the following are most likely to appear:
1440 This warns in two cases, for both C and C++:
1441 * When the code is trying to take the absolute value of an unsigned
1442 quantity, which is effectively a no-op, and almost never what was
1443 intended. The code should be fixed, if at all possible. If you are
1444 sure that the unsigned quantity can be safely cast to signed, without
1445 loss of information or undefined behavior, you can add an explicit
1446 cast, or disable the warning.
1448 * When the code is trying to take an absolute value, but the called
1449 abs() variant is for the wrong type, which can lead to truncation.
1450 If you want to disable the warning instead of fixing the code, please
1451 make sure that truncation will not occur, or it might lead to unwanted
1454 -Wtautological-undefined-compare and
1455 -Wundefined-bool-conversion
1457 These warn when C++ code is trying to compare 'this' against NULL, while
1458 'this' should never be NULL in well-defined C++ code. However, there is
1459 some legacy (pre C++11) code out there, which actively abuses this
1460 feature, which was less strictly defined in previous C++ versions.
1462 Squid and openjdk do this, for example. The warning can be turned off
1463 for C++98 and earlier, but compiling the code in C++11 mode might result
1464 in unexpected behavior; for example, the parts of the program that are
1465 unreachable could be optimized away.
1468 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1469 kernel sources have been removed. The .h files remain, since some
1470 utilities include them. This will need to be fixed later.
1471 If "mount -t oldnfs ..." is attempted, it will fail.
1472 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1473 the utilities will report errors.
1476 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1477 directories to top level SUBDIR variable when their parent
1478 directory is included in LOCAL_DIRS. Users with build systems with
1479 such hierarchies and without SUBDIR entries in the parent
1480 directory Makefiles should add them or add the directories to
1484 faith(4) and faithd(8) have been removed from the base system. Faith
1485 has been obsolete for a very long time.
1488 vt(4), the new console driver, is enabled by default. It brings
1489 support for Unicode and double-width characters, as well as
1490 support for UEFI and integration with the KMS kernel video
1493 You may need to update your console settings in /etc/rc.conf,
1494 most probably the keymap. During boot, /etc/rc.d/syscons will
1495 indicate what you need to do.
1497 vt(4) still has issues and lacks some features compared to
1498 syscons(4). See the wiki for up-to-date information:
1499 https://wiki.freebsd.org/Newcons
1501 If you want to keep using syscons(4), you can do so by adding
1502 the following line to /boot/loader.conf:
1506 pjdfstest has been integrated into kyua as an opt-in test suite.
1507 Please see share/doc/pjdfstest/README for more details on how to
1511 gperf has been removed from the base system for architectures
1512 that use clang. Ports that require gperf will obtain it from the
1516 pjdfstest has been moved from tools/regression/pjdfstest to
1520 At svn r271982, The default linux compat kernel ABI has been adjusted
1521 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1522 update. If you wish to continue using the linux-f10 compat ports,
1523 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1524 encouraged to update their linux-compat packages to linux-c6 during
1525 their next update cycle.
1528 The ofwfb driver, used to provide a graphics console on PowerPC when
1529 using vt(4), no longer allows mmap() of all physical memory. This
1530 will prevent Xorg on PowerPC with some ATI graphics cards from
1531 initializing properly unless x11-servers/xorg-server is updated to
1535 The xdev targets have been converted to using TARGET and
1536 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1539 The default unbound configuration has been modified to address
1540 issues with reverse lookups on networks that use private
1541 address ranges. If you use the local_unbound service, run
1542 "service local_unbound setup" as root to regenerate your
1543 configuration, then "service local_unbound reload" to load the
1547 The GNU texinfo and GNU info pages are not built and installed
1548 anymore, WITH_INFO knob has been added to allow to built and install
1550 UPDATE: see 20150102 entry on texinfo's removal
1553 The GNU readline library is now an INTERNALLIB - that is, it is
1554 statically linked into consumers (GDB and variants) in the base
1555 system, and the shared library is no longer installed. The
1556 devel/readline port is available for third party software that
1560 The Itanium architecture (ia64) has been removed from the list of
1561 known architectures. This is the first step in the removal of the
1565 Commit r268115 has added NFSv4.1 server support, merged from
1566 projects/nfsv4.1-server. Since this includes changes to the
1567 internal interfaces between the NFS related modules, a full
1568 build of the kernel and modules will be necessary.
1569 __FreeBSD_version has been bumped.
1572 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1573 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1574 which differs from the behaviour controlled by this knob.)
1577 Maximal length of the serial number in CTL was increased from 16 to
1578 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1579 and ctld, need to be rebuilt to work with a new kernel.
1582 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1583 1 respectively to match the upstream numbers. They were out of
1584 sync because, when they were originally added to FreeBSD, the
1585 upstream versions were not respected. These libraries are private
1586 and not yet built by default, so renumbering them should be a
1587 non-issue. However, unclean source trees will yield broken test
1588 programs once the operator executes "make delete-old-libs" after a
1589 "make installworld".
1591 Additionally, the atf-sh binary was made private by moving it into
1592 /usr/libexec/. Already-built shell test programs will keep the
1593 path to the old binary so they will break after "make delete-old"
1596 If you are using WITH_TESTS=yes (not the default), wipe the object
1597 tree and rebuild from scratch to prevent spurious test failures.
1598 This is only needed once: the misnumbered libraries and misplaced
1599 binaries have been added to OptionalObsoleteFiles.inc so they will
1600 be removed during a clean upgrade.
1603 Clang and llvm have been upgraded to 3.4.1 release.
1606 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1607 be removed to avoid issues in the future (and has been added to
1611 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1612 past, it affected all builds that used the bsd.*.mk files. The old
1613 behavior was a bug, but people may have relied upon it. To get this
1614 behavior back, you can .include /etc/src.conf from /etc/make.conf
1615 (which is still global and isn't changed). This also changes the
1616 behavior of incremental builds inside the tree of individual
1617 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1618 Although this has survived make universe and some upgrade scenarios,
1619 other upgrade scenarios may have broken. At least one form of
1620 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1621 as well... In cases where MAKESYSPATH isn't working with this
1622 setting, you'll need to set it to the full path to your tree.
1624 One side effect of all this cleaning up is that bsd.compiler.mk
1625 is no longer implicitly included by bsd.own.mk. If you wish to
1626 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1630 The lindev device has been removed since /dev/full has been made a
1631 standard device. __FreeBSD_version has been bumped.
1634 The knob WITHOUT_VI was added to the base system, which controls
1635 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1636 in order to reorder files share/termcap and didn't build ex(1) as a
1637 build tool, so building/installing with WITH_VI is highly advised for
1638 build hosts for older releases.
1640 This issue has been fixed in stable/9 and stable/10 in r277022 and
1641 r276991, respectively.
1644 The YES_HESIOD knob has been removed. It has been obsolete for
1645 a decade. Please move to using WITH_HESIOD instead or your builds
1646 will silently lack HESIOD.
1649 The uart(4) driver has been changed with respect to its handling
1650 of the low-level console. Previously the uart(4) driver prevented
1651 any process from changing the baudrate or the CLOCAL and HUPCL
1652 control flags. By removing the restrictions, operators can make
1653 changes to the serial console port without having to reboot.
1654 However, when getty(8) is started on the serial device that is
1655 associated with the low-level console, a misconfigured terminal
1656 line in /etc/ttys will now have a real impact.
1657 Before upgrading the kernel, make sure that /etc/ttys has the
1658 serial console device configured as 3wire without baudrate to
1659 preserve the previous behaviour. E.g:
1660 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1663 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1664 to improve performance. To re-enable it, if needed, run rpcbind
1665 with command line option -W.
1668 Switched back to the GPL dtc compiler due to updates in the upstream
1669 dts files not being supported by the BSDL dtc compiler. You will need
1670 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1671 may result while building dtb files during a kernel build if you fail
1672 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1675 Clang and llvm have been upgraded to 3.4 release.
1678 The nve(4) driver has been removed. Please use the nfe(4) driver
1679 for NVIDIA nForce MCP Ethernet adapters instead.
1682 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1683 This could cause certain C++ applications using shared libraries built
1684 against the previous version of libc++ to crash. The incompatibility
1685 has now been fixed, but any C++ applications or shared libraries built
1686 between r261283 and r261801 should be recompiled.
1689 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1690 capability mode support. Please note that enabling the feature in
1691 kernel is still highly recommended.
1694 OpenSSH is now built with sandbox support, and will use sandbox as
1695 the default privilege separation method. This requires Capsicum
1696 capability mode support in kernel.
1699 The libelf and libdwarf libraries have been updated to newer
1700 versions from upstream. Shared library version numbers for
1701 these two libraries were bumped. Any ports or binaries
1702 requiring these two libraries should be recompiled.
1703 __FreeBSD_version is bumped to 1100006.
1706 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1707 instead of providing an explicit one, this would prevent such
1708 Makefile from providing its own Kyuafile in the future during
1709 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1710 intervention is needed to clean an objdir if you use NO_CLEAN:
1711 # find /usr/obj -name Kyuafile | xargs rm -f
1714 The behavior of gss_pseudo_random() for the krb5 mechanism
1715 has changed, for applications requesting a longer random string
1716 than produced by the underlying enctype's pseudo-random() function.
1717 In particular, the random string produced from a session key of
1718 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1719 be different at the 17th octet and later, after this change.
1720 The counter used in the PRF+ construction is now encoded as a
1721 big-endian integer in accordance with RFC 4402.
1722 __FreeBSD_version is bumped to 1100004.
1725 The WITHOUT_ATF build knob has been removed and its functionality
1726 has been subsumed into the more generic WITHOUT_TESTS. If you were
1727 using the former to disable the build of the ATF libraries, you
1728 should change your settings to use the latter.
1731 The default version of mtree is nmtree which is obtained from
1732 NetBSD. The output is generally the same, but may vary
1733 slightly. If you found you need identical output adding
1734 "-F freebsd9" to the command line should do the trick. For the
1735 time being, the old mtree is available as fmtree.
1738 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1739 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1740 1.1.4_8 and verify bsdyml not linked in, before running "make
1742 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1744 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1747 The stable/10 branch has been created in subversion from head
1754 Avoid using make -j when upgrading. While generally safe, there are
1755 sometimes problems using -j to upgrade. If your upgrade fails with
1756 -j, please try again without -j. From time to time in the past there
1757 have been problems using -j with buildworld and/or installworld. This
1758 is especially true when upgrading between "distant" versions (eg one
1759 that cross a major release boundary or several minor releases, or when
1760 several months have passed on the -current branch).
1762 Sometimes, obscure build problems are the result of environment
1763 poisoning. This can happen because the make utility reads its
1764 environment when searching for values for global variables. To run
1765 your build attempts in an "environmental clean room", prefix all make
1766 commands with 'env -i '. See the env(1) manual page for more details.
1768 When upgrading from one major version to another it is generally best to
1769 upgrade to the latest code in the currently installed branch first, then
1770 do an upgrade to the new branch. This is the best-tested upgrade path,
1771 and has the highest probability of being successful. Please try this
1772 approach if you encounter problems with a major version upgrade. Since
1773 the stable 4.x branch point, one has generally been able to upgrade from
1774 anywhere in the most recent stable branch to head / current (or even the
1775 last couple of stable branches). See the top of this file when there's
1778 When upgrading a live system, having a root shell around before
1779 installing anything can help undo problems. Not having a root shell
1780 around can lead to problems if pam has changed too much from your
1781 starting point to allow continued authentication after the upgrade.
1783 This file should be read as a log of events. When a later event changes
1784 information of a prior event, the prior event should not be deleted.
1785 Instead, a pointer to the entry with the new information should be
1786 placed in the old entry. Readers of this file should also sanity check
1787 older entries before relying on them blindly. Authors of new entries
1788 should write them with this in mind.
1792 When upgrading the boot ZFS pool to a new version, always follow
1795 1.) recompile and reinstall the ZFS boot loader and boot block
1796 (this is part of "make buildworld" and "make installworld")
1798 2.) update the ZFS boot block on your boot drive
1800 The following example updates the ZFS boot block on the first
1801 partition (freebsd-boot) of a GPT partitioned drive ada0:
1802 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1804 Non-boot pools do not need these updates.
1808 If you are updating from a prior version of FreeBSD (even one just
1809 a few days old), you should follow this procedure. It is the most
1810 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1812 make kernel-toolchain
1813 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1814 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1816 To test a kernel once
1817 ---------------------
1818 If you just want to boot a kernel once (because you are not sure
1819 if it works, or if you want to boot a known bad kernel to provide
1820 debugging information) run
1821 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1822 nextboot -k testkernel
1824 To rebuild everything and install it on the current system.
1825 -----------------------------------------------------------
1826 # Note: sometimes if you are running current you gotta do more than
1827 # is listed here if you are upgrading from a really old current.
1829 <make sure you have good level 0 dumps>
1831 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1832 make installkernel KERNCONF=YOUR_KERNEL_HERE
1834 <reboot in single user> [3]
1841 To cross-install current onto a separate partition
1842 --------------------------------------------------
1843 # In this approach we use a separate partition to hold
1844 # current's root, 'usr', and 'var' directories. A partition
1845 # holding "/", "/usr" and "/var" should be about 2GB in
1848 <make sure you have good level 0 dumps>
1851 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1852 <maybe newfs current's root partition>
1853 <mount current's root partition on directory ${CURRENT_ROOT}>
1854 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1855 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1856 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1857 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1858 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1859 <reboot into current>
1860 <do a "native" rebuild/install as described in the previous section>
1861 <maybe install compatibility libraries from ports/misc/compat*>
1865 To upgrade in-place from stable to current
1866 ----------------------------------------------
1867 <make sure you have good level 0 dumps>
1869 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1870 make installkernel KERNCONF=YOUR_KERNEL_HERE
1872 <reboot in single user> [3]
1879 Make sure that you've read the UPDATING file to understand the
1880 tweaks to various things you need. At this point in the life
1881 cycle of current, things change often and you are on your own
1882 to cope. The defaults can also change, so please read ALL of
1883 the UPDATING entries.
1885 Also, if you are tracking -current, you must be subscribed to
1886 freebsd-current@freebsd.org. Make sure that before you update
1887 your sources that you have read and understood all the recent
1888 messages there. If in doubt, please track -stable which has
1889 much fewer pitfalls.
1891 [1] If you have third party modules, such as vmware, you
1892 should disable them at this point so they don't crash your
1895 [3] From the bootblocks, boot -s, and then do
1900 adjkerntz -i # if CMOS is wall time
1901 Also, when doing a major release upgrade, it is required that
1902 you boot into single user mode to do the installworld.
1904 [4] Note: This step is non-optional. Failure to do this step
1905 can result in a significant reduction in the functionality of the
1906 system. Attempting to do it by hand is not recommended and those
1907 that pursue this avenue should read this file carefully, as well
1908 as the archives of freebsd-current and freebsd-hackers mailing lists
1909 for potential gotchas. The -U option is also useful to consider.
1910 See mergemaster(8) for more information.
1912 [5] Usually this step is a no-op. However, from time to time
1913 you may need to do this if you get unknown user in the following
1914 step. It never hurts to do it all the time. You may need to
1915 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1916 install) after the buildworld before this step if you last updated
1917 from current before 20130425 or from -stable before 20130430.
1919 [6] This only deletes old files and directories. Old libraries
1920 can be deleted by "make delete-old-libs", but you have to make
1921 sure that no program is using those libraries anymore.
1923 [8] The new kernel must be able to run existing binaries used by
1924 an installworld. When upgrading across major versions, the new
1925 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1926 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1927 binaries). Failure to do so may leave you with a system that is
1928 hard to boot to recover. A GENERIC kernel will include suitable
1929 compatibility options to run binaries from older branches.
1931 Make sure that you merge any new devices from GENERIC since the
1932 last time you updated your kernel config file.
1934 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1935 "?=" instead of the "=" assignment operator, so that buildworld can
1936 override the CPUTYPE if it needs to.
1938 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1939 not on the command line, or in /etc/make.conf. buildworld will
1940 warn if it is improperly defined.
1943 This file contains a list, in reverse chronological order, of major
1944 breakages in tracking -current. It is not guaranteed to be a complete
1945 list of such breakages, and only contains entries since September 23, 2011.
1946 If you need to see UPDATING entries from before that date, you will need
1947 to fetch an UPDATING file from an older FreeBSD release.
1949 Copyright information:
1951 Copyright 1998-2009 M. Warner Losh.
1953 Redistribution, publication, translation and use, with or without
1954 modification, in full or in part, in any form or format of this
1955 document are permitted without further permission from the author.
1957 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1958 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1959 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1960 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1961 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1962 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1963 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1964 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1965 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1966 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1967 POSSIBILITY OF SUCH DAMAGE.
1969 Contact Warner Losh if you have any questions about your use of