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