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