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