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