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.
20 ntpd no longer by default locks its pages in memory, allowing them
21 to be paged out by the kernel. Use rlimit memlock to restore
22 historic BSD behaviour. For example, add "rlimit memlock 32"
23 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
26 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
27 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
28 been removed from mount_fusefs(8). You can safely remove them from
29 your scripts, because they had no effect.
31 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
32 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
33 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
34 sysctls have been removed. If you felt the need to set any of them to
35 a non-default value, please tell asomers@FreeBSD.org why.
38 The fuse(4) module has been renamed to fusefs(4) for consistency with
39 other filesystems. You should update any kld_load="fuse" entries in
40 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
41 "options FUSE" enties in kernel config files.
44 Default permissions on the /var/account/acct file (and copies of it
45 rotated by periodic daily scripts) are changed from 0644 to 0640
46 because the file contains sensitive information that should not be
47 world-readable. If the /var/account directory must be created by
48 rc.d/accounting, the mode used is now 0750. Admins who use the
49 accounting feature are encouraged to change the mode of an existing
50 /var/account directory to 0750 or 0700.
53 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
54 been upgraded to 8.0.1. Please see the 20141231 entry below for
55 information about prerequisites and upgrading, if you are not already
56 using clang 3.5.0 or higher.
59 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
60 functionality needed for the RETPOLINE option should work properly
61 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
64 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
65 8.0.0. Please see the 20141231 entry below for information about
66 prerequisites and upgrading, if you are not already using clang 3.5.0
70 The RETPOLINE option produces non-functional ifunc-using binaries
71 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
72 Once Clang 8 is merged it may be enabled again.
75 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
76 7.0.1. Please see the 20141231 entry below for information about
77 prerequisites and upgrading, if you are not already using clang 3.5.0
81 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
82 compiled into your custom kernel, add 'device xz' statement to the
86 Iflib is no longer unconditionally compiled into the kernel. Drivers
87 using iflib and statically compiled into the kernel, now require
88 the 'device iflib' config option. For the same drivers loaded as
89 modules on kernels not having 'device iflib', the iflib.ko module
90 is loaded automatically.
93 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
94 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
95 servers that have vfs.nfsd.nfs_privport set will only allow mounts
96 from clients using a reserved port#. Since both the FreeBSD and Linux
97 NFSv4 clients use reserved port#s by default, this should not affect
101 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
102 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
103 it produces broken binaries when ifuncs are in use. Users needing
104 GNU ld should install the binutils port or package.
107 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
108 has been converted to a port (misc/ctm) and will be removed from
109 FreeBSD-13. A depreciation warning will be printed to stderr by
110 the ctm command, but the functionality will remain in base for all
114 The stable/12 branch has been created in subversion from head
118 Ports for the DRM modules have been simplified. Now, amd64 users should
119 just install the drm-kmod port. All others should install
122 Graphics hardware that's newer than about 2010 usually works with
123 drm-kmod. For hardware older than 2013, however, some users will need
124 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
125 than 2008 usually only works in drm-legacy-kmod. The graphics team can
126 only commit to hardware made since 2013 due to the complexity of the
127 market and difficulty to test all the older cards effectively. If you
128 have hardware supported by drm-kmod, you are strongly encouraged to use
129 that as you will get better support.
131 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
132 elsewhere, the drm and drm2 modules will be eliminated from the src base
133 soon (with a limited exception for arm). Please update to the package asap
134 and report any issues to x11@freebsd.org.
136 Generally, anybody using the drm*-kmod packages should add
137 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
138 cross-threading surprises, especially with automatic driver
139 loading from X11 startup. These will become the defaults in 13-current
143 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
144 custom kernel and module loading configuration files must be updated
145 accordingly. Moreover, interfaces previous presented as ixlvN to the
146 system are now exposed as iavfN and network configuration files must
147 be adjusted as necessary.
150 OpenSSL has been updated to version 1.1.1. This update included
151 additional various API changes througout the base system. It is
152 important to rebuild third-party software after upgrading. The value
153 of __FreeBSD_version has been bumped accordingly.
156 The legacy DRM modules and drivers have now been added to the loader's
157 module blacklist, in favor of loading them with kld_list in rc.conf(5).
158 The module blacklist may be overridden with the loader.conf(5)
159 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
163 The cam(4) based nda(4) driver will be used over nvd(4) by default on
164 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
165 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
166 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
170 Reproducible build mode is now on by default, in preparation for
171 FreeBSD 12.0. This eliminates build metadata such as the user,
172 host, and time from the kernel (and uname), unless the working tree
173 corresponds to a modified checkout from a version control system.
174 The previous behavior can be obtained by setting the /etc/src.conf
175 knob WITHOUT_REPRODUCIBLE_BUILD.
178 The Yarrow CSPRNG has been removed from the kernel as it has not been
179 supported by its designers since at least 2003. Fortuna has been the
180 default since FreeBSD-11.
183 devctl freeze/thaw have gone into the tree, the rc scripts have been
184 updated to use them and devmatch has been changed. You should update
185 kernel, userland and rc scripts all at the same time.
188 The default interpreter has been switched from 4th to Lua.
189 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
190 interpreter. If you have custom FORTH code you will need to set
191 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
192 src.conf for the build. This will create default hard links between
193 loader and loader_4th instead of loader and loader_lua, the new default.
194 If you are using UEFI it will create the proper hard link to loader.efi.
196 bhyve uses userboot.so. It remains 4th-only until some issues are solved
197 regarding coexisting with multiple versions of FreeBSD are resolved.
200 ls(1) now respects the COLORTERM environment variable used in other
201 systems and software to indicate that a colored terminal is both
202 supported and desired. If ls(1) is suddenly emitting colors, they may
203 be disabled again by either removing the unwanted COLORTERM from your
204 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
205 may not be observed in a future release.
208 The default pager for most commands has been changed to "less". To
209 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
213 The jedec_ts(4) driver has been removed. A superset of its functionality
214 is available in the jedec_dimm(4) driver, and the manpage for that
215 driver includes migration instructions. If you have "device jedec_ts"
216 in your kernel configuration file, it must be removed.
219 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
220 This should have no effect if the kernel is booted via BIOS/legacy boot.
221 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
222 has a buggy firmware that prevents a successful boot due to use of
226 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
227 support has been removed from the tree. These ports were
228 obsolete and/or known to be broken for many years.
231 loader.efi has been augmented to participate more fully in the
232 UEFI boot manager protocol. loader.efi will now look at the
233 BootXXXX environment variable to determine if a specific kernel
234 or root partition was specified. XXXX is derived from BootCurrent.
235 efibootmgr(8) manages these standard UEFI variables.
238 zfsloader's functionality has now been folded into loader.
239 zfsloader is no longer necessary once you've updated your
240 boot blocks. For a transition period, we will install a
241 hardlink for zfsloader to loader to allow a smooth transition
242 until the boot blocks can be updated (hard link because old
243 zfs boot blocks don't understand symlinks).
246 ARM64 now have efifb support, if you want to have serial console
247 on your arm64 board when an screen is connected and the bootloader
248 setup a frambuffer for us to use, just add :
252 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
253 an screen connected as the firmware will setup a framebuffer are that
254 u-boot will expose as an EFI framebuffer.
257 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
258 or take steps to update /etc/passwd before doing installworld on
259 existing systems. Do not skip the "mergemaster -Fp" step before
260 installworld, as described in the update procedures near the bottom
261 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
262 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
263 the ntp config file contain options that change file/dir locations.
264 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
265 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
266 taking steps to ensure that all required files/dirs are accessible
270 Big endian arm support has been removed.
273 The static environment setup in kernel configs is no longer mutually
274 exclusive with the loader(8) environment by default. In order to
275 restore the previous default behavior of disabling the loader(8)
276 environment if a static environment is present, you must specify
277 loader_env.disabled=1 in the static environment.
280 The ABI of syscalls used by management tools like sockstat and
281 netstat has been broken to allow 32-bit binaries to work on
282 64-bit kernels without modification. These programs will need
283 to match the kernel in order to function. External programs may
284 require minor modifications to accommodate a change of type in
285 structures from pointers to 64-bit virtual addresses.
288 On i386 and amd64 atomics are now inlined. Out of tree modules using
289 atomics will need to be rebuilt.
292 The '%I' format in the kern.corefile sysctl limits the number of
293 core files that a process can generate to the number stored in the
294 debug.ncores sysctl. The '%I' format is replaced by the single digit
295 index. Previously, if all indexes were taken the kernel would overwrite
296 only a core file with the highest index in a filename.
297 Currently the system will create a new core file if there is a free
298 index or if all slots are taken it will overwrite the oldest one.
301 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
302 6.0.1. Please see the 20141231 entry below for information about
303 prerequisites and upgrading, if you are not already using clang 3.5.0
307 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
308 needed to be changed to work with it. This change was made with r335763
309 and requires a mergemaster / etcupdate / etc to update the installed file.
312 r334930 changed the interface between the NFS modules, so they all
313 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
316 As of r334391 lld is the default amd64 system linker; it is installed
317 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
321 The kernel / userland interface for devinfo changed, so you'll
322 need a new kernel and userland as a pair for it to work (rebuilding
323 lib/libdevinfo is all that's required). devinfo and devmatch will
324 not work, but everything else will when there's a mismatch.
327 The on-disk format for hwpmc callchain records has changed to include
328 threadid corresponding to a given record. This changes the field offsets
329 and thus requires that libpmcstat be rebuilt before using a kernel
333 The vxge(4) driver has been removed. This driver was introduced into
334 HEAD one week before the Exar left the Ethernet market and is not
335 known to be used. If you have device vxge in your kernel config file
339 The amd64 kernel now requires a ld that supports ifunc to produce a
340 working kernel, either lld or a newer binutils. lld is built by default
341 on amd64, and the 'buildkernel' target uses it automatically. However,
342 it is not the default linker, so building the kernel the traditional
343 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
344 binutils port/package). lld will soon be default, and this requirement
347 NOTE: As of r334391 lld is the default system linker on amd64, and no
348 workaround is necessary.
351 The nxge(4) driver has been removed. This driver was for PCI-X 10g
352 cards made by s2io/Neterion. The company was aquired by Exar and
353 no longer sells or supports Ethernet products. If you have device
354 nxge in your kernel config file it must be removed.
357 The tz database (tzdb) has been updated to 2018e. This version more
358 correctly models time stamps in time zones with negative DST such as
359 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
360 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
361 time zone abbreviations and the tm_isdst flag.
364 The ixgb(4) driver has been removed. This driver was for an early and
365 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
366 quickly shifted to the long lived ixgbe family. If you have device
367 ixgb in your kernel config file it must be removed.
370 The lmc(4) driver has been removed. This was a WAN interface
371 card that was already reportedly rare in 2003, and had an ambiguous
372 license. If you have device lmc in your kernel config file it must
376 Support for Arcnet networks has been removed. If you have device
377 arcnet or device cm in your kernel config file they must be
381 Support for FDDI networks has been removed. If you have device
382 fddi or device fpa in your kernel config file they must be
386 In addition to supporting RFC 3164 formatted messages, the
387 syslogd(8) service is now capable of parsing RFC 5424 formatted
388 log messages. The main benefit of using RFC 5424 is that clients
389 may now send log messages with timestamps containing year numbers,
390 microseconds and time zone offsets.
392 Similarly, the syslog(3) C library function has been altered to
393 send RFC 5424 formatted messages to the local system logging
394 daemon. On systems using syslogd(8), this change should have no
395 negative impact, as long as syslogd(8) and the C library are
396 updated at the same time. On systems using a different system
397 logging daemon, it may be necessary to make configuration
398 adjustments, depending on the software used.
400 When using syslog-ng, add the 'syslog-protocol' flag to local
401 input sources to enable parsing of RFC 5424 formatted messages:
404 unix-dgram("/var/run/log" flags(syslog-protocol));
407 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
408 of the 'imuxsock' module to let messages be processed by the
409 regular RFC 3164/5424 parsing pipeline:
411 module(load="imuxsock" SysSock.UseSpecialParser="off")
413 Do note that these changes only affect communication between local
414 applications and syslogd(8). The format that syslogd(8) uses to
415 store messages on disk or forward messages to other systems
416 remains unchanged. syslogd(8) still uses RFC 3164 for these
417 purposes. Options to customize this behaviour will be added in the
418 future. Utilities that process log files stored in /var/log are
419 thus expected to continue to function as before.
421 __FreeBSD_version has been incremented to 1200061 to denote this
425 Support for token ring networks has been removed. If you
426 have "device token" in your kernel config you should remove
427 it. No device drivers supported token ring.
430 makefs was modified to be able to tag ISO9660 El Torito boot catalog
431 entries as EFI instead of overloading the i386 tag as done previously.
432 The amd64 mkisoimages.sh script used to build amd64 ISO images for
433 release was updated to use this. This may mean that makefs must be
434 updated before "make cdrom" can be run in the release directory. This
435 should be as simple as:
437 $ cd $SRCDIR/usr.sbin/makefs
438 $ make depend all install
441 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
442 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
443 Co-existance for the transition period will come shortly. Booting is a
444 complex environment and test coverage for Lua-enabled loaders has been
445 thin, so it would be prudent to assume it might not work and make
446 provisions for backup boot methods.
449 devmatch functionality has been turned on in devd. It will automatically
450 load drivers for unattached devices. This may cause unexpected drivers to
451 be loaded. Please report any problems to current@ and imp@freebsd.org.
454 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
455 6.0.0. Please see the 20141231 entry below for information about
456 prerequisites and upgrading, if you are not already using clang 3.5.0
460 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
461 This means it is used to link the kernel and userland libraries and
462 executables, but is not yet installed as /usr/bin/ld by default.
464 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
465 WITHOUT_LLD_BOOTSTRAP=yes
468 On i386, pmtimer has been removed. Its functionality has been folded
469 into apm. It was a no-op on ACPI in current for a while now (but was still
470 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
471 from kernel config files.
474 The use of RSS hash from the network card aka flowid has been
475 disabled by default for lagg(4) as it's currently incompatible with
476 the lacp and loadbalance protocols.
478 This can be re-enabled by setting the following in loader.conf:
479 net.link.lagg.default_use_flowid="1"
482 The SW_WATCHDOG option is no longer necessary to enable the
483 hardclock-based software watchdog if no hardware watchdog is
484 configured. As before, SW_WATCHDOG will cause the software
485 watchdog to be enabled even if a hardware watchdog is configured.
488 r326887 fixes the issue described in the 20171214 UPDATING entry.
489 r326888 flips the switch back to building GELI support always.
492 r362593 broke ZFS + GELI support for reasons unknown. However,
493 it also broke ZFS support generally, so GELI has been turned off
494 by default as the lesser evil in r326857. If you boot off ZFS and/or
495 GELI, it might not be a good time to update.
498 PowerPC users must update loader(8) by rebuilding world before
499 installing a new kernel, as the protocol connecting them has
500 changed. Without the update, loader metadata will not be passed
501 successfully to the kernel and users will have to enter their
502 root partition at the kernel mountroot prompt to continue booting.
503 Newer versions of loader can boot old kernels without issue.
506 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
507 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
508 to WITH/OUT_LOADER_GELI.
511 The naive and non-compliant support of posix_fallocate(2) in ZFS
512 has been removed as of r325320. The system call now returns EINVAL
513 when used on a ZFS file. Although the new behavior complies with the
514 standard, some consumers are not prepared to cope with it.
515 One known victim is lld prior to r325420.
518 Building in a FreeBSD src checkout will automatically create object
519 directories now rather than store files in the current directory if
520 'make obj' was not ran. Calling 'make obj' is no longer necessary.
521 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
522 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
526 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
527 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
528 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
529 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
530 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
531 The UNIFIED_OBJDIR option is a transitional feature that will be
532 removed for 12.0 release; please migrate to the new format for any
533 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
534 than hardcoding paths.
537 The native-xtools target no longer installs the files by default to the
538 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
539 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
542 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
543 options are changing from controlling the build if defined / undefined
544 to controlling the build with explicit 'yes' or 'no' values. They will
545 shift to WITH/WITHOUT options to match other options in the system.
548 libstand has turned into a private library for sys/boot use only.
549 It is no longer supported as a public interface outside of sys/boot.
552 The arm port has split armv6 into armv6 and armv7. armv7 is now
553 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
554 and are running a kernel from before r324363, you will need to add
555 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
558 When building multiple kernels using KERNCONF, non-existent KERNCONF
559 files will produce an error and buildkernel will fail. Previously
560 missing KERNCONF files silently failed giving no indication as to
561 why, only to subsequently discover during installkernel that the
562 desired kernel was never built in the first place.
565 The default serial number format for CTL LUNs has changed. This will
566 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
567 or iSCSI clients care about their LUNs' serial numbers. Users who
568 require serial number stability should hardcode serial numbers in
572 For 32-bit arm compiled for hard-float support, soft-floating point
573 binaries now always get their shared libraries from
574 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
575 /usr/libsoft also existed). Only users with a hard-float ld.so, but
576 soft-float everything else should be affected.
579 The geli password typed at boot is now hidden. To restore the previous
580 behavior, see geli(8) for configuration options.
583 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
584 sysctl values. Minor nit, but requires a rebuild of both world/kernel
588 "make check" behavior (made in ^/head@r295380) has been changed to
589 execute from a limited sandbox, as opposed to executing from
593 - The "beforecheck" and "aftercheck" targets are now specified.
594 - ${CHECKDIR} (added in commit noted above) has been removed.
595 - Legacy behavior can be enabled by setting
596 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
598 If the limited sandbox mode is enabled, "make check" will execute
599 "make distribution", then install, execute the tests, and clean up the
600 sandbox if successful.
602 The "make distribution" and "make install" targets are typically run as
603 root to set appropriate permissions and ownership at installation time.
604 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
605 environment if executing "make check" with limited sandbox mode using
606 an unprivileged user.
609 Since the switch to GPT disk labels, fsck for UFS/FFS has been
610 unable to automatically find alternate superblocks. As of r322297,
611 the information needed to find alternate superblocks has been
612 moved to the end of the area reserved for the boot block.
613 Filesystems created with a newfs of this vintage or later
614 will create the recovery information. If you have a filesystem
615 created prior to this change and wish to have a recovery block
616 created for your filesystem, you can do so by running fsck in
617 foreground mode (i.e., do not use the -p or -y options). As it
618 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
619 to which you should answer yes.
622 As of r321665, an NFSv4 server configuration that services
623 Kerberos mounts or clients that do not support the uid/gid in
624 owner/owner_group string capability, must explicitly enable
625 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
626 machine's /etc/rc.conf file.
629 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
630 Please see the 20141231 entry below for information about prerequisites
631 and upgrading, if you are not already using clang 3.5.0 or higher.
634 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
635 r-commands (rlogin, rsh, etc.) to be built with the base system.
638 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
639 a very major ABI incompatible change, so users of FreeBSD/powerpc must
640 be careful when performing source upgrades. It is best to run
641 'make installworld' from an alternate root system, either a live
642 CD/memory stick, or a temporary root partition. Additionally, all ports
643 must be recompiled. powerpc64 is largely unaffected, except in the case
644 of 32-bit compatibility. All 32-bit binaries will be affected.
647 Forward compatibility for the "ino64" project have been committed. This
648 will allow most new binaries to run on older kernels in a limited
649 fashion. This prevents many of the common foot-shooting actions in the
650 upgrade as well as the limited ability to roll back the kernel across
651 the ino64 upgrade. Complicated use cases may not work properly, though
652 enough simpler ones work to allow recovery in most situations.
655 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
656 if you require the GPL compiler.
659 The internal ABI used for communication between the NFS kernel modules
660 was changed by r320085, so __FreeBSD_version was bumped to
661 ensure all the NFS related modules are updated together.
664 The ABI of struct event was changed by extending the data
665 member to 64bit and adding ext fields. For upgrade, same
666 precautions as for the entry 20170523 "ino64" must be
670 The GNU roff toolchain has been removed from base. To render manpages
671 which are not supported by mandoc(1), man(1) can fallback on GNU roff
672 from ports (and recommends to install it).
673 To render roff(7) documents, consider using GNU roff from ports or the
674 heirloom doctools roff toolchain from ports via pkg install groff or
675 via pkg install heirloom-doctools.
678 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
679 smaller runtime footprint builds. This is useful for embedded systems
680 which only require one chipset support.
682 If you load it as a module, make sure this is in /boot/loader.conf:
686 This will load the HAL, all chip/RF backends and if_ath_pci.
687 If you have if_ath_pci in /boot/loader.conf, ensure it is after
688 if_ath or it will not load any HAL chipset support.
690 If you want to selectively load things (eg on ye cheape ARM/MIPS
691 platforms where RAM is at a premium) you should:
694 * load the chip modules in question
695 * load ath_rate, ath_dfs
697 * load if_ath_pci and/or if_ath_ahb depending upon your particular
698 bus bind type - this is where probe/attach is done.
700 For further comments/feedback, poke adrian@ .
703 The "ino64" 64-bit inode project has been committed, which extends
704 a number of types to 64 bits. Upgrading in place requires care and
705 adherence to the documented upgrade procedure.
707 If using a custom kernel configuration ensure that the
708 COMPAT_FREEBSD11 option is included (as during the upgrade the
709 system will be running the ino64 kernel with the existing world).
711 For the safest in-place upgrade begin by removing previous build
712 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
713 full procedure documented below under the heading "To rebuild
714 everything and install it on the current system." Specifically,
715 a reboot is required after installing the new kernel before
719 The NATM framework including the en(4), fatm(4), hatm(4), and
720 patm(4) devices has been removed. Consumers should plan a
721 migration before the end-of-life date for FreeBSD 11.
724 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
725 diff has not been implemented, if those are needed a newer version of
726 GNU diff is available via the diffutils package under the gdiff name.
729 As of r316810 for ipfilter, keep frags is no longer assumed when
730 keep state is specified in a rule. r316810 aligns ipfilter with
731 documentation in man pages separating keep frags from keep state.
732 This allows keep state to be specified without forcing keep frags
733 and allows keep frags to be specified independently of keep state.
734 To maintain previous behaviour, also specify keep frags with
735 keep state (as documented in ipf.conf.5).
738 arm64 builds now use the base system LLD 4.0.0 linker by default,
739 instead of requiring that the aarch64-binutils port or package be
740 installed. To continue using aarch64-binutils, set
741 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
744 The UDP optimization in entry 20160818 that added the sysctl
745 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
746 packets will no longer be treated as L3 broadcast packets.
749 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
750 use any explicitly assigned loopback address available in the jail
751 instead of using the first assigned address of the jail.
754 The ctl.ko module no longer implements the iSCSI target frontend:
755 cfiscsi.ko does instead.
757 If building cfiscsi.ko as a kernel module, the module can be loaded
758 via one of the following methods:
759 - `cfiscsi_load="YES"` in loader.conf(5).
760 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
761 - ctladm(8)/ctld(8), when compiled with iSCSI support
762 (`WITH_ISCSI=yes` in src.conf(5))
764 Please see cfiscsi(4) for more details.
767 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
768 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
769 same source (previously, the dependency of mmcsd.ko on mmc.ko was
770 missing, but mmcsd.ko now will refuse to load if it is incompatible
774 The syntax of ipfw(8) named states was changed to avoid ambiguity.
775 If you have used named states in the firewall rules, you need to modify
776 them after installworld and before rebooting. Now named states must
777 be prefixed with colon.
780 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
781 removed as the userland we provide cannot use them. The KMS version
782 (sys/dev/drm2) supports the same hardware.
785 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
786 Please see the 20141231 entry below for information about prerequisites
787 and upgrading, if you are not already using clang 3.5.0 or higher.
790 The code that provides support for ZFS .zfs/ directory functionality
791 has been reimplemented. It's not possible now to create a snapshot
792 by mkdir under .zfs/snapshot/. That should be the only user visible
796 EISA bus support has been removed. The WITH_EISA option is no longer
800 MCA bus support has been removed.
803 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
804 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
807 The EM_MULTIQUEUE kernel configuration option is deprecated now that
808 the em(4) driver conforms to iflib specifications.
811 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
812 IFLIB. If you have a custom kernel configuration that excludes em(4)
813 but you use igb(4), you need to re-add em(4) to your custom configuration.
816 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
817 Please see the 20141231 entry below for information about prerequisites
818 and upgrading, if you are not already using clang 3.5.0 or higher.
821 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
822 Please see the 20141231 entry below for information about prerequisites
823 and upgrading, if you are not already using clang 3.5.0 or higher.
826 The layout of the pmap structure has changed for powerpc to put the pmap
827 statistics at the front for all CPU variations. libkvm(3) and all tools
828 that link against it need to be recompiled.
831 isl(4) and cyapa(4) drivers now require a new driver,
832 chromebook_platform(4), to work properly on Chromebook-class hardware.
833 On other types of hardware the drivers may need to be configured using
834 device hints. Please see the corresponding manual pages for details.
837 The urtwn(4) driver was merged into rtwn(4) and now consists of
838 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
840 Also, firmware for RTL8188CE was renamed due to possible name
841 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
844 GNU rcs has been removed from base. It is available as packages:
845 - rcs: Latest GPLv3 GNU rcs version.
846 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
850 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
851 modules now requires that the kernel configuration contain the
852 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
855 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
856 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
859 Relocatable object files with the extension of .So have been renamed
860 to use an extension of .pico instead. The purpose of this change is
861 to avoid a name clash with shared libraries on case-insensitive file
862 systems. On those file systems, foo.So is the same file as foo.so.
865 GNU rcs has been turned off by default. It can (temporarily) be built
866 again by adding WITH_RCS knob in src.conf.
867 Otherwise, GNU rcs is available from packages:
868 - rcs: Latest GPLv3 GNU rcs version.
869 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
872 The backup_uses_rcs functionality has been removed from rc.subr.
875 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
876 two separate components, QUEUE_MACRO_DEBUG_TRACE and
877 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
878 QUEUE_MACRO_DEBUG behavior.
881 r304787 changed some ioctl interfaces between the iSCSI userspace
882 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
883 rebuilt to work with new kernels. __FreeBSD_version has been bumped
887 The UDP receive code has been updated to only treat incoming UDP
888 packets that were addressed to an L2 broadcast address as L3
889 broadcast packets. It is not expected that this will affect any
890 standards-conforming UDP application. The new behaviour can be
891 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
895 Remove the openbsd_poll system call.
896 __FreeBSD_version has been bumped because of this.
899 The stable/11 branch has been created from head@r302406.
902 The libc stub for the pipe(2) system call has been replaced with
903 a wrapper that calls the pipe2(2) system call and the pipe(2)
904 system call is now only implemented by the kernels that include
905 "options COMPAT_FREEBSD10" in their config file (this is the
906 default). Users should ensure that this option is enabled in
907 their kernel or upgrade userspace to r302092 before upgrading their
911 CAM will now strip leading spaces from SCSI disks' serial numbers.
912 This will affect users who create UFS filesystems on SCSI disks using
913 those disk's diskid device nodes. For example, if /etc/fstab
914 previously contained a line like
915 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
916 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
917 transforms like gmirror may also be affected. ZFS users should
921 The bitstring(3) API has been updated with new functionality and
922 improved performance. But it is binary-incompatible with the old API.
923 Objects built with the new headers may not be linked against objects
924 built with the old headers.
927 The brk and sbrk functions have been removed from libc on arm64.
928 Binutils from ports has been updated to not link to these
929 functions and should be updated to the latest version before
930 installing a new libc.
933 The armv6 port now defaults to hard float ABI. Limited support
934 for running both hardfloat and soft float on the same system
935 is available using the libraries installed with -DWITH_LIBSOFT.
936 This has only been tested as an upgrade path for installworld
937 and packages may fail or need manual intervention to run. New
938 packages will be needed.
940 To update an existing self-hosted armv6hf system, you must add
941 TARGET_ARCH=armv6 on the make command line for both the build
942 and the install steps.
945 Kernel modules compiled outside of a kernel build now default to
946 installing to /boot/modules instead of /boot/kernel. Many kernel
947 modules built this way (such as those in ports) already overrode
948 KMODDIR explicitly to install into /boot/modules. However,
949 manually building and installing a module from /sys/modules will
950 now install to /boot/modules instead of /boot/kernel.
953 The CAM I/O scheduler has been committed to the kernel. There should be
954 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
955 list of known rogues that claim support for this but actually corrupt
956 data is believed to be complete, be on the lookout for data
957 corruption. The known rogue list is believed to be complete:
959 o Crucial MX100, M550 drives with MU01 firmware.
960 o Micron M510 and M550 drives with MU01 firmware.
961 o Micron M500 prior to MU07 firmware
962 o Samsung 830, 840, and 850 all firmwares
963 o FCCT M500 all firmwares
965 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
966 with working NCQ TRIM. For Micron branded drives, see your sales rep for
967 updated firmware. Black listed drives will work correctly because these
968 drives work correctly so long as no NCQ TRIMs are sent to them. Given
969 this list is the same as found in Linux, it's believed there are no
970 other rogues in the market place. All other models from the above
973 To be safe, if you are at all concerned, you can quirk each of your
974 drives to prevent NCQ from being sent by setting:
975 kern.cam.ada.X.quirks="0x2"
976 in loader.conf. If the drive requires the 4k sector quirk, set the
980 The FAST_DEPEND build option has been removed and its functionality is
981 now the one true way. The old mkdep(1) style of 'make depend' has
982 been removed. See 20160311 for further details.
985 Resource range types have grown from unsigned long to uintmax_t. All
986 drivers, and anything using libdevinfo, need to be recompiled.
989 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
990 builds. It no longer runs mkdep(1) during 'make depend', and the
991 'make depend' stage can safely be skipped now as it is auto ran
992 when building 'make all' and will generate all SRCS and DPSRCS before
993 building anything else. Dependencies are gathered at compile time with
994 -MF flags kept in separate .depend files per object file. Users should
995 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
999 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1000 kernel modules. Therefore, if you load any kernel modules at boot time,
1001 please install the boot loaders after you install the kernel, but before
1005 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1006 make installkernel KERNCONF=YOUR_KERNEL_HERE
1007 make -C sys/boot install
1008 <reboot in single user>
1010 Then follow the usual steps, described in the General Notes section,
1014 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1015 see the 20141231 entry below for information about prerequisites and
1016 upgrading, if you are not already using clang 3.5.0 or higher.
1019 The AIO subsystem is now a standard part of the kernel. The
1020 VFS_AIO kernel option and aio.ko kernel module have been removed.
1021 Due to stability concerns, asynchronous I/O requests are only
1022 permitted on sockets and raw disks by default. To enable
1023 asynchronous I/O requests on all file types, set the
1024 vfs.aio.enable_unsafe sysctl to a non-zero value.
1027 The ELF object manipulation tool objcopy is now provided by the
1028 ELF Tool Chain project rather than by GNU binutils. It should be a
1029 drop-in replacement, with the addition of arm64 support. The
1030 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1031 to obtain the GNU version if necessary.
1034 Building ZFS pools on top of zvols is prohibited by default. That
1035 feature has never worked safely; it's always been prone to deadlocks.
1036 Using a zvol as the backing store for a VM guest's virtual disk will
1037 still work, even if the guest is using ZFS. Legacy behavior can be
1038 restored by setting vfs.zfs.vol.recursive=1.
1041 The NONE and HPN patches has been removed from OpenSSH. They are
1042 still available in the security/openssh-portable port.
1045 With the addition of ypldap(8), a new _ypldap user is now required
1046 during installworld. "mergemaster -p" can be used to add the user
1047 prior to installworld, as documented in the handbook.
1050 The tftp loader (pxeboot) now uses the option root-path directive. As a
1051 consequence it no longer looks for a pxeboot.4th file on the tftp
1052 server. Instead it uses the regular /boot infrastructure as with the
1056 The code to start recording plug and play data into the modules has
1057 been committed. While the old tools will properly build a new kernel,
1058 a number of warnings about "unknown metadata record 4" will be produced
1059 for an older kldxref. To avoid such warnings, make sure to rebuild
1060 the kernel toolchain (or world). Make sure that you have r292078 or
1061 later when trying to build 292077 or later before rebuilding.
1064 Debug data files are now built by default with 'make buildworld' and
1065 installed with 'make installworld'. This facilitates debugging but
1066 requires more disk space both during the build and for the installed
1067 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1071 r291527 changed the internal interface between the nfsd.ko and
1072 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1073 __FreeBSD_version has been bumped because of this.
1076 Add support for unicode collation strings leads to a change of
1077 order of files listed by ls(1) for example. To get back to the old
1078 behaviour, set LC_COLLATE environment variable to "C".
1080 Databases administrators will need to reindex their databases given
1081 collation results will be different.
1083 Due to a bug in install(1) it is recommended to remove the ancient
1084 locales before running make installworld.
1086 rm -rf /usr/share/locale/*
1089 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1090 libcrypto.so.7 or libssl.so.7 must be recompiled.
1093 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1094 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1095 should be replaced with isp_2400 and isp_2500 modules respectively.
1098 The build previously allowed using 'make -n' to not recurse into
1099 sub-directories while showing what commands would be executed, and
1100 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1101 and 'make -N' will not.
1104 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1105 and etcupdate will now use this file. A custom sendmail.cf is now
1106 updated via this mechanism rather than via installworld. If you had
1107 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1108 want to remove the exclusion or change it to "always install".
1109 /etc/mail/sendmail.cf is now managed the same way regardless of
1110 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1111 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1114 Compatibility shims for legacy ATA device names have been removed.
1115 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1116 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1117 environment variables, /dev/ad* and /dev/ar* symbolic links.
1120 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1121 Please see the 20141231 entry below for information about prerequisites
1122 and upgrading, if you are not already using clang 3.5.0 or higher.
1125 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1126 and renamed from .symbols to .debug. This reduces the size requirements
1127 on the boot partition or file system and provides consistency with
1128 userland debug files.
1130 When using the supported kernel installation method the
1131 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1132 as is done with /boot/kernel.
1134 Developers wishing to maintain the historical behavior of installing
1135 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1138 The wireless drivers had undergone changes that remove the 'parent
1139 interface' from the ifconfig -l output. The rc.d network scripts
1140 used to check presence of a parent interface in the list, so old
1141 scripts would fail to start wireless networking. Thus, etcupdate(3)
1142 or mergemaster(8) run is required after kernel update, to update your
1143 rc.d scripts in /etc.
1146 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1147 These configurations are now automatically interpreted as
1148 'scrub fragment reassemble'.
1151 Kernel-loadable modules for the random(4) device are back. To use
1152 them, the kernel must have
1155 options RANDOM_LOADABLE
1157 kldload(8) can then be used to load random_fortuna.ko
1158 or random_yarrow.ko. Please note that due to the indirect
1159 function calls that the loadable modules need to provide,
1160 the build-in variants will be slightly more efficient.
1162 The random(4) kernel option RANDOM_DUMMY has been retired due to
1163 unpopularity. It was not all that useful anyway.
1166 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1167 Control over building the ELF Tool Chain tools is now provided by
1168 the WITHOUT_TOOLCHAIN knob.
1171 The polarity of Pulse Per Second (PPS) capture events with the
1172 uart(4) driver has been corrected. Prior to this change the PPS
1173 "assert" event corresponded to the trailing edge of a positive PPS
1174 pulse and the "clear" event was the leading edge of the next pulse.
1176 As the width of a PPS pulse in a typical GPS receiver is on the
1177 order of 1 millisecond, most users will not notice any significant
1178 difference with this change.
1180 Anyone who has compensated for the historical polarity reversal by
1181 configuring a negative offset equal to the pulse width will need to
1182 remove that workaround.
1185 The default group assigned to /dev/dri entries has been changed
1186 from 'wheel' to 'video' with the id of '44'. If you want to have
1187 access to the dri devices please add yourself to the video group
1190 # pw groupmod video -m $USER
1193 The menu.rc and loader.rc files will now be replaced during
1194 upgrades. Please migrate local changes to menu.rc.local and
1195 loader.rc.local instead.
1198 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1199 strings and strip have been removed. The src.conf(5) knob
1200 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1203 As ZFS requires more kernel stack pages than is the default on some
1204 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1205 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1207 Please consider using 'options KSTACK_PAGES=X' where X is greater
1208 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1211 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1212 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1213 default, i.e., they will not contain "::". For example, instead
1214 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1215 to have a more specific match, such as different map entries for
1216 IPv6:0:0 vs IPv6:0. This change requires that configuration
1217 data (including maps, files, classes, custom ruleset, etc.) must
1218 use the same format, so make certain such configuration data is
1219 upgrading. As a very simple check search for patterns like
1220 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1221 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1222 the cf option UseCompressedIPv6Addresses.
1225 The default kernel entropy-processing algorithm is now
1226 Fortuna, replacing Yarrow.
1228 Assuming you have 'device random' in your kernel config
1229 file, the configurations allow a kernel option to override
1230 this default. You may choose *ONE* of:
1232 options RANDOM_YARROW # Legacy /dev/random algorithm.
1233 options RANDOM_DUMMY # Blocking-only driver.
1235 If you have neither, you get Fortuna. For most people,
1236 read no further, Fortuna will give a /dev/random that works
1237 like it always used to, and the difference will be irrelevant.
1239 If you remove 'device random', you get *NO* kernel-processed
1240 entropy at all. This may be acceptable to folks building
1241 embedded systems, but has complications. Carry on reading,
1242 and it is assumed you know what you need.
1244 *PLEASE* read random(4) and random(9) if you are in the
1245 habit of tweaking kernel configs, and/or if you are a member
1246 of the embedded community, wanting specific and not-usual
1247 behaviour from your security subsystems.
1249 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1250 random', you will NOT have a functioning /dev/random, and
1251 many cryptographic features will not work, including SSH.
1252 You may also find strange behaviour from the random(3) set
1253 of library functions, in particular sranddev(3), srandomdev(3)
1254 and arc4random(3). The reason for this is that the KERN_ARND
1255 sysctl only returns entropy if it thinks it has some to
1256 share, and with RANDOM_DUMMY or no 'device random' this
1260 An additional fix for the issue described in the 20150614 sendmail
1261 entry below has been committed in revision 284717.
1264 FreeBSD's old make (fmake) has been removed from the system. It is
1265 available as the devel/fmake port or via pkg install fmake.
1268 The fix for the issue described in the 20150614 sendmail entry
1269 below has been committed in revision 284436. The work
1270 around described in that entry is no longer needed unless the
1271 default setting is overridden by a confDH_PARAMETERS configuration
1272 setting of '5' or pointing to a 512 bit DH parameter file.
1275 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1276 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1277 and devel/kyua to version 0.20+ and adjust any calling code to work
1278 with Kyuafile and kyua.
1281 The import of openssl to address the FreeBSD-SA-15:10.openssl
1282 security advisory includes a change which rejects handshakes
1283 with DH parameters below 768 bits. sendmail releases prior
1284 to 8.15.2 (not yet released), defaulted to a 512 bit
1285 DH parameter setting for client connections. To work around
1286 this interoperability, sendmail can be configured to use a
1287 2048 bit DH parameter by:
1289 1. Edit /etc/mail/`hostname`.mc
1290 2. If a setting for confDH_PARAMETERS does not exist or
1291 exists and is set to a string beginning with '5',
1292 replace it with '2'.
1293 3. If a setting for confDH_PARAMETERS exists and is set to
1294 a file path, create a new file with:
1295 openssl dhparam -out /path/to/file 2048
1296 4. Rebuild the .cf file:
1297 cd /etc/mail/; make; make install
1298 5. Restart sendmail:
1299 cd /etc/mail/; make restart
1301 A sendmail patch is coming, at which time this file will be
1305 Generation of legacy formatted entries have been disabled by default
1306 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1307 entries were converted to use the new format by default when the new,
1308 machine independent format have been added and supported since FreeBSD
1311 Please see the pwd_mkdb(8) manual page for further details.
1314 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1315 20141231 entry below for information about prerequisites and upgrading,
1316 if you are not already using 3.5.0 or higher.
1319 TI platform code switched to using vendor DTS files and this update
1320 may break existing systems running on Beaglebone, Beaglebone Black,
1323 - dtb files should be regenerated/reinstalled. Filenames are the
1324 same but content is different now
1325 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1326 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1327 addressing scheme is now pin 25 on /dev/gpioc3.
1328 - Pandaboard: /etc/ttys should be updated, serial console device is
1329 now /dev/ttyu2, not /dev/ttyu0
1332 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1333 If you need the GNU extension from groff soelim(1), install groff
1334 from package: pkg install groff, or via ports: textproc/groff.
1337 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1338 defined in symlink(7); previously symlinks were silently ignored.
1341 The const qualifier has been removed from iconv(3) to comply with
1342 POSIX. The ports tree is aware of this from r384038 onwards.
1345 Libraries specified by LIBADD in Makefiles must have a corresponding
1346 DPADD_<lib> variable to ensure correct dependencies. This is now
1347 enforced in src.libnames.mk.
1350 From legacy ata(4) driver was removed support for SATA controllers
1351 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1352 Kernel modules ataahci and ataadaptec were removed completely,
1353 replaced by ahci and mvs modules respectively.
1356 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1357 the 20141231 entry below for information about prerequisites and
1358 upgrading, if you are not already using 3.5.0 or higher.
1361 The 32-bit PowerPC kernel has been changed to a position-independent
1362 executable. This can only be booted with a version of loader(8)
1363 newer than January 31, 2015, so make sure to update both world and
1364 kernel before rebooting.
1367 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1368 but before r278950, the RNG was not seeded properly. Immediately
1369 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1370 ssh keys or openssl keys) that were generated w/ a kernel from that
1371 range. This does not affect programs that directly used /dev/random
1372 or /dev/urandom. All userland uses of arc4random(3) are affected.
1375 The autofs(4) ABI was changed in order to restore binary compatibility
1376 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1377 with the new kernel.
1380 The powerpc64 kernel has been changed to a position-independent
1381 executable. This can only be booted with a new version of loader(8),
1382 so make sure to update both world and kernel before rebooting.
1385 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1386 only release, no new features have been added. Please see the 20141231
1387 entry below for information about prerequisites and upgrading, if you
1388 are not already using 3.5.0.
1391 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1392 taken from the ELF Tool Chain project rather than GNU binutils. They
1393 should be drop-in replacements, with the addition of arm64 support.
1394 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1395 binutils tools, if necessary. See 20150805 for updated information.
1398 The default Unbound configuration now enables remote control
1399 using a local socket. Users who have already enabled the
1400 local_unbound service should regenerate their configuration
1401 by running "service local_unbound setup" as root.
1404 The GNU texinfo and GNU info pages have been removed.
1405 To be able to view GNU info pages please install texinfo from ports.
1408 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1410 As of this release, a prerequisite for building clang, llvm and lldb is
1411 a C++11 capable compiler and C++11 standard library. This means that to
1412 be able to successfully build the cross-tools stage of buildworld, with
1413 clang as the bootstrap compiler, your system compiler or cross compiler
1414 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1415 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1418 On any standard FreeBSD 10.x or 11.x installation, where clang and
1419 libc++ are on by default (that is, on x86 or arm), this should work out
1422 On 9.x installations where clang is enabled by default, e.g. on x86 and
1423 powerpc, libc++ will not be enabled by default, so libc++ should be
1424 built (with clang) and installed first. If both clang and libc++ are
1425 missing, build clang first, then use it to build libc++.
1427 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1428 the instructions for 9.x above.
1430 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1431 default, and do not build clang.
1433 Many embedded systems are resource constrained, and will not be able to
1434 build clang in a reasonable time, or in some cases at all. In those
1435 cases, cross building bootable systems on amd64 is a workaround.
1437 This new version of clang introduces a number of new warnings, of which
1438 the following are most likely to appear:
1442 This warns in two cases, for both C and C++:
1443 * When the code is trying to take the absolute value of an unsigned
1444 quantity, which is effectively a no-op, and almost never what was
1445 intended. The code should be fixed, if at all possible. If you are
1446 sure that the unsigned quantity can be safely cast to signed, without
1447 loss of information or undefined behavior, you can add an explicit
1448 cast, or disable the warning.
1450 * When the code is trying to take an absolute value, but the called
1451 abs() variant is for the wrong type, which can lead to truncation.
1452 If you want to disable the warning instead of fixing the code, please
1453 make sure that truncation will not occur, or it might lead to unwanted
1456 -Wtautological-undefined-compare and
1457 -Wundefined-bool-conversion
1459 These warn when C++ code is trying to compare 'this' against NULL, while
1460 'this' should never be NULL in well-defined C++ code. However, there is
1461 some legacy (pre C++11) code out there, which actively abuses this
1462 feature, which was less strictly defined in previous C++ versions.
1464 Squid and openjdk do this, for example. The warning can be turned off
1465 for C++98 and earlier, but compiling the code in C++11 mode might result
1466 in unexpected behavior; for example, the parts of the program that are
1467 unreachable could be optimized away.
1470 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1471 kernel sources have been removed. The .h files remain, since some
1472 utilities include them. This will need to be fixed later.
1473 If "mount -t oldnfs ..." is attempted, it will fail.
1474 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1475 the utilities will report errors.
1478 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1479 directories to top level SUBDIR variable when their parent
1480 directory is included in LOCAL_DIRS. Users with build systems with
1481 such hierarchies and without SUBDIR entries in the parent
1482 directory Makefiles should add them or add the directories to
1486 faith(4) and faithd(8) have been removed from the base system. Faith
1487 has been obsolete for a very long time.
1490 vt(4), the new console driver, is enabled by default. It brings
1491 support for Unicode and double-width characters, as well as
1492 support for UEFI and integration with the KMS kernel video
1495 You may need to update your console settings in /etc/rc.conf,
1496 most probably the keymap. During boot, /etc/rc.d/syscons will
1497 indicate what you need to do.
1499 vt(4) still has issues and lacks some features compared to
1500 syscons(4). See the wiki for up-to-date information:
1501 https://wiki.freebsd.org/Newcons
1503 If you want to keep using syscons(4), you can do so by adding
1504 the following line to /boot/loader.conf:
1508 pjdfstest has been integrated into kyua as an opt-in test suite.
1509 Please see share/doc/pjdfstest/README for more details on how to
1513 gperf has been removed from the base system for architectures
1514 that use clang. Ports that require gperf will obtain it from the
1518 pjdfstest has been moved from tools/regression/pjdfstest to
1522 At svn r271982, The default linux compat kernel ABI has been adjusted
1523 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1524 update. If you wish to continue using the linux-f10 compat ports,
1525 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1526 encouraged to update their linux-compat packages to linux-c6 during
1527 their next update cycle.
1530 The ofwfb driver, used to provide a graphics console on PowerPC when
1531 using vt(4), no longer allows mmap() of all physical memory. This
1532 will prevent Xorg on PowerPC with some ATI graphics cards from
1533 initializing properly unless x11-servers/xorg-server is updated to
1537 The xdev targets have been converted to using TARGET and
1538 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1541 The default unbound configuration has been modified to address
1542 issues with reverse lookups on networks that use private
1543 address ranges. If you use the local_unbound service, run
1544 "service local_unbound setup" as root to regenerate your
1545 configuration, then "service local_unbound reload" to load the
1549 The GNU texinfo and GNU info pages are not built and installed
1550 anymore, WITH_INFO knob has been added to allow to built and install
1552 UPDATE: see 20150102 entry on texinfo's removal
1555 The GNU readline library is now an INTERNALLIB - that is, it is
1556 statically linked into consumers (GDB and variants) in the base
1557 system, and the shared library is no longer installed. The
1558 devel/readline port is available for third party software that
1562 The Itanium architecture (ia64) has been removed from the list of
1563 known architectures. This is the first step in the removal of the
1567 Commit r268115 has added NFSv4.1 server support, merged from
1568 projects/nfsv4.1-server. Since this includes changes to the
1569 internal interfaces between the NFS related modules, a full
1570 build of the kernel and modules will be necessary.
1571 __FreeBSD_version has been bumped.
1574 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1575 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1576 which differs from the behaviour controlled by this knob.)
1579 Maximal length of the serial number in CTL was increased from 16 to
1580 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1581 and ctld, need to be rebuilt to work with a new kernel.
1584 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1585 1 respectively to match the upstream numbers. They were out of
1586 sync because, when they were originally added to FreeBSD, the
1587 upstream versions were not respected. These libraries are private
1588 and not yet built by default, so renumbering them should be a
1589 non-issue. However, unclean source trees will yield broken test
1590 programs once the operator executes "make delete-old-libs" after a
1591 "make installworld".
1593 Additionally, the atf-sh binary was made private by moving it into
1594 /usr/libexec/. Already-built shell test programs will keep the
1595 path to the old binary so they will break after "make delete-old"
1598 If you are using WITH_TESTS=yes (not the default), wipe the object
1599 tree and rebuild from scratch to prevent spurious test failures.
1600 This is only needed once: the misnumbered libraries and misplaced
1601 binaries have been added to OptionalObsoleteFiles.inc so they will
1602 be removed during a clean upgrade.
1605 Clang and llvm have been upgraded to 3.4.1 release.
1608 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1609 be removed to avoid issues in the future (and has been added to
1613 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1614 past, it affected all builds that used the bsd.*.mk files. The old
1615 behavior was a bug, but people may have relied upon it. To get this
1616 behavior back, you can .include /etc/src.conf from /etc/make.conf
1617 (which is still global and isn't changed). This also changes the
1618 behavior of incremental builds inside the tree of individual
1619 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1620 Although this has survived make universe and some upgrade scenarios,
1621 other upgrade scenarios may have broken. At least one form of
1622 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1623 as well... In cases where MAKESYSPATH isn't working with this
1624 setting, you'll need to set it to the full path to your tree.
1626 One side effect of all this cleaning up is that bsd.compiler.mk
1627 is no longer implicitly included by bsd.own.mk. If you wish to
1628 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1632 The lindev device has been removed since /dev/full has been made a
1633 standard device. __FreeBSD_version has been bumped.
1636 The knob WITHOUT_VI was added to the base system, which controls
1637 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1638 in order to reorder files share/termcap and didn't build ex(1) as a
1639 build tool, so building/installing with WITH_VI is highly advised for
1640 build hosts for older releases.
1642 This issue has been fixed in stable/9 and stable/10 in r277022 and
1643 r276991, respectively.
1646 The YES_HESIOD knob has been removed. It has been obsolete for
1647 a decade. Please move to using WITH_HESIOD instead or your builds
1648 will silently lack HESIOD.
1651 The uart(4) driver has been changed with respect to its handling
1652 of the low-level console. Previously the uart(4) driver prevented
1653 any process from changing the baudrate or the CLOCAL and HUPCL
1654 control flags. By removing the restrictions, operators can make
1655 changes to the serial console port without having to reboot.
1656 However, when getty(8) is started on the serial device that is
1657 associated with the low-level console, a misconfigured terminal
1658 line in /etc/ttys will now have a real impact.
1659 Before upgrading the kernel, make sure that /etc/ttys has the
1660 serial console device configured as 3wire without baudrate to
1661 preserve the previous behaviour. E.g:
1662 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1665 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1666 to improve performance. To re-enable it, if needed, run rpcbind
1667 with command line option -W.
1670 Switched back to the GPL dtc compiler due to updates in the upstream
1671 dts files not being supported by the BSDL dtc compiler. You will need
1672 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1673 may result while building dtb files during a kernel build if you fail
1674 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1677 Clang and llvm have been upgraded to 3.4 release.
1680 The nve(4) driver has been removed. Please use the nfe(4) driver
1681 for NVIDIA nForce MCP Ethernet adapters instead.
1684 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1685 This could cause certain C++ applications using shared libraries built
1686 against the previous version of libc++ to crash. The incompatibility
1687 has now been fixed, but any C++ applications or shared libraries built
1688 between r261283 and r261801 should be recompiled.
1691 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1692 capability mode support. Please note that enabling the feature in
1693 kernel is still highly recommended.
1696 OpenSSH is now built with sandbox support, and will use sandbox as
1697 the default privilege separation method. This requires Capsicum
1698 capability mode support in kernel.
1701 The libelf and libdwarf libraries have been updated to newer
1702 versions from upstream. Shared library version numbers for
1703 these two libraries were bumped. Any ports or binaries
1704 requiring these two libraries should be recompiled.
1705 __FreeBSD_version is bumped to 1100006.
1708 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1709 instead of providing an explicit one, this would prevent such
1710 Makefile from providing its own Kyuafile in the future during
1711 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1712 intervention is needed to clean an objdir if you use NO_CLEAN:
1713 # find /usr/obj -name Kyuafile | xargs rm -f
1716 The behavior of gss_pseudo_random() for the krb5 mechanism
1717 has changed, for applications requesting a longer random string
1718 than produced by the underlying enctype's pseudo-random() function.
1719 In particular, the random string produced from a session key of
1720 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1721 be different at the 17th octet and later, after this change.
1722 The counter used in the PRF+ construction is now encoded as a
1723 big-endian integer in accordance with RFC 4402.
1724 __FreeBSD_version is bumped to 1100004.
1727 The WITHOUT_ATF build knob has been removed and its functionality
1728 has been subsumed into the more generic WITHOUT_TESTS. If you were
1729 using the former to disable the build of the ATF libraries, you
1730 should change your settings to use the latter.
1733 The default version of mtree is nmtree which is obtained from
1734 NetBSD. The output is generally the same, but may vary
1735 slightly. If you found you need identical output adding
1736 "-F freebsd9" to the command line should do the trick. For the
1737 time being, the old mtree is available as fmtree.
1740 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1741 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1742 1.1.4_8 and verify bsdyml not linked in, before running "make
1744 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1746 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1749 The stable/10 branch has been created in subversion from head
1756 Avoid using make -j when upgrading. While generally safe, there are
1757 sometimes problems using -j to upgrade. If your upgrade fails with
1758 -j, please try again without -j. From time to time in the past there
1759 have been problems using -j with buildworld and/or installworld. This
1760 is especially true when upgrading between "distant" versions (eg one
1761 that cross a major release boundary or several minor releases, or when
1762 several months have passed on the -current branch).
1764 Sometimes, obscure build problems are the result of environment
1765 poisoning. This can happen because the make utility reads its
1766 environment when searching for values for global variables. To run
1767 your build attempts in an "environmental clean room", prefix all make
1768 commands with 'env -i '. See the env(1) manual page for more details.
1770 When upgrading from one major version to another it is generally best to
1771 upgrade to the latest code in the currently installed branch first, then
1772 do an upgrade to the new branch. This is the best-tested upgrade path,
1773 and has the highest probability of being successful. Please try this
1774 approach if you encounter problems with a major version upgrade. Since
1775 the stable 4.x branch point, one has generally been able to upgrade from
1776 anywhere in the most recent stable branch to head / current (or even the
1777 last couple of stable branches). See the top of this file when there's
1780 When upgrading a live system, having a root shell around before
1781 installing anything can help undo problems. Not having a root shell
1782 around can lead to problems if pam has changed too much from your
1783 starting point to allow continued authentication after the upgrade.
1785 This file should be read as a log of events. When a later event changes
1786 information of a prior event, the prior event should not be deleted.
1787 Instead, a pointer to the entry with the new information should be
1788 placed in the old entry. Readers of this file should also sanity check
1789 older entries before relying on them blindly. Authors of new entries
1790 should write them with this in mind.
1794 When upgrading the boot ZFS pool to a new version, always follow
1797 1.) recompile and reinstall the ZFS boot loader and boot block
1798 (this is part of "make buildworld" and "make installworld")
1800 2.) update the ZFS boot block on your boot drive
1802 The following example updates the ZFS boot block on the first
1803 partition (freebsd-boot) of a GPT partitioned drive ada0:
1804 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1806 Non-boot pools do not need these updates.
1810 If you are updating from a prior version of FreeBSD (even one just
1811 a few days old), you should follow this procedure. It is the most
1812 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1814 make kernel-toolchain
1815 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1816 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1818 To test a kernel once
1819 ---------------------
1820 If you just want to boot a kernel once (because you are not sure
1821 if it works, or if you want to boot a known bad kernel to provide
1822 debugging information) run
1823 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1824 nextboot -k testkernel
1826 To rebuild everything and install it on the current system.
1827 -----------------------------------------------------------
1828 # Note: sometimes if you are running current you gotta do more than
1829 # is listed here if you are upgrading from a really old current.
1831 <make sure you have good level 0 dumps>
1833 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1834 make installkernel KERNCONF=YOUR_KERNEL_HERE
1836 <reboot in single user> [3]
1843 To cross-install current onto a separate partition
1844 --------------------------------------------------
1845 # In this approach we use a separate partition to hold
1846 # current's root, 'usr', and 'var' directories. A partition
1847 # holding "/", "/usr" and "/var" should be about 2GB in
1850 <make sure you have good level 0 dumps>
1853 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1854 <maybe newfs current's root partition>
1855 <mount current's root partition on directory ${CURRENT_ROOT}>
1856 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1857 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1858 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1859 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1860 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1861 <reboot into current>
1862 <do a "native" rebuild/install as described in the previous section>
1863 <maybe install compatibility libraries from ports/misc/compat*>
1867 To upgrade in-place from stable to current
1868 ----------------------------------------------
1869 <make sure you have good level 0 dumps>
1871 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1872 make installkernel KERNCONF=YOUR_KERNEL_HERE
1874 <reboot in single user> [3]
1881 Make sure that you've read the UPDATING file to understand the
1882 tweaks to various things you need. At this point in the life
1883 cycle of current, things change often and you are on your own
1884 to cope. The defaults can also change, so please read ALL of
1885 the UPDATING entries.
1887 Also, if you are tracking -current, you must be subscribed to
1888 freebsd-current@freebsd.org. Make sure that before you update
1889 your sources that you have read and understood all the recent
1890 messages there. If in doubt, please track -stable which has
1891 much fewer pitfalls.
1893 [1] If you have third party modules, such as vmware, you
1894 should disable them at this point so they don't crash your
1897 [3] From the bootblocks, boot -s, and then do
1902 adjkerntz -i # if CMOS is wall time
1903 Also, when doing a major release upgrade, it is required that
1904 you boot into single user mode to do the installworld.
1906 [4] Note: This step is non-optional. Failure to do this step
1907 can result in a significant reduction in the functionality of the
1908 system. Attempting to do it by hand is not recommended and those
1909 that pursue this avenue should read this file carefully, as well
1910 as the archives of freebsd-current and freebsd-hackers mailing lists
1911 for potential gotchas. The -U option is also useful to consider.
1912 See mergemaster(8) for more information.
1914 [5] Usually this step is a no-op. However, from time to time
1915 you may need to do this if you get unknown user in the following
1916 step. It never hurts to do it all the time. You may need to
1917 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1918 install) after the buildworld before this step if you last updated
1919 from current before 20130425 or from -stable before 20130430.
1921 [6] This only deletes old files and directories. Old libraries
1922 can be deleted by "make delete-old-libs", but you have to make
1923 sure that no program is using those libraries anymore.
1925 [8] The new kernel must be able to run existing binaries used by
1926 an installworld. When upgrading across major versions, the new
1927 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1928 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1929 binaries). Failure to do so may leave you with a system that is
1930 hard to boot to recover. A GENERIC kernel will include suitable
1931 compatibility options to run binaries from older branches.
1933 Make sure that you merge any new devices from GENERIC since the
1934 last time you updated your kernel config file.
1936 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1937 "?=" instead of the "=" assignment operator, so that buildworld can
1938 override the CPUTYPE if it needs to.
1940 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1941 not on the command line, or in /etc/make.conf. buildworld will
1942 warn if it is improperly defined.
1945 This file contains a list, in reverse chronological order, of major
1946 breakages in tracking -current. It is not guaranteed to be a complete
1947 list of such breakages, and only contains entries since September 23, 2011.
1948 If you need to see UPDATING entries from before that date, you will need
1949 to fetch an UPDATING file from an older FreeBSD release.
1951 Copyright information:
1953 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1955 Redistribution, publication, translation and use, with or without
1956 modification, in full or in part, in any form or format of this
1957 document are permitted without further permission from the author.
1959 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1960 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1961 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1962 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1963 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1964 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1965 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1966 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1967 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1968 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1969 POSSIBILITY OF SUCH DAMAGE.
1971 Contact Warner Losh if you have any questions about your use of