1 Updating Information for FreeBSD stable/12 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 The tap(4) driver has been folded into tun(4), and the module has been
21 renamed to tuntap. You should update any kld_list="if_tap" or
22 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
23 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
24 module instead, and "device tap" or "device tun" entries in kernel
25 config files to select the tuntap device instead.
28 ntpd no longer by default locks its pages in memory, allowing them
29 to be paged out by the kernel. Use rlimit memlock to restore
30 historic BSD behaviour. For example, add "rlimit memlock 32"
31 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
34 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
35 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
36 been removed from mount_fusefs(8). You can safely remove them from
37 your scripts, because they had no effect.
39 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
40 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
41 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
42 sysctls have been removed. If you felt the need to set any of them to
43 a non-default value, please tell asomers@FreeBSD.org why.
46 The fuse(4) module has been renamed to fusefs(4) for consistency with
47 other filesystems. You should update any kld_load="fuse" entries in
48 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
49 "options FUSE" enties in kernel config files.
52 Default permissions on the /var/account/acct file (and copies of it
53 rotated by periodic daily scripts) are changed from 0644 to 0640
54 because the file contains sensitive information that should not be
55 world-readable. If the /var/account directory must be created by
56 rc.d/accounting, the mode used is now 0750. Admins who use the
57 accounting feature are encouraged to change the mode of an existing
58 /var/account directory to 0750 or 0700.
61 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
62 been upgraded to 8.0.1. Please see the 20141231 entry below for
63 information about prerequisites and upgrading, if you are not already
64 using clang 3.5.0 or higher.
67 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
68 functionality needed for the RETPOLINE option should work properly
69 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
72 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
73 8.0.0. Please see the 20141231 entry below for information about
74 prerequisites and upgrading, if you are not already using clang 3.5.0
78 The RETPOLINE option produces non-functional ifunc-using binaries
79 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
80 Once Clang 8 is merged it may be enabled again.
83 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
84 7.0.1. Please see the 20141231 entry below for information about
85 prerequisites and upgrading, if you are not already using clang 3.5.0
89 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
90 compiled into your custom kernel, add 'device xz' statement to the
94 Iflib is no longer unconditionally compiled into the kernel. Drivers
95 using iflib and statically compiled into the kernel, now require
96 the 'device iflib' config option. For the same drivers loaded as
97 modules on kernels not having 'device iflib', the iflib.ko module
98 is loaded automatically.
101 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
102 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
103 servers that have vfs.nfsd.nfs_privport set will only allow mounts
104 from clients using a reserved port#. Since both the FreeBSD and Linux
105 NFSv4 clients use reserved port#s by default, this should not affect
109 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
110 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
111 it produces broken binaries when ifuncs are in use. Users needing
112 GNU ld should install the binutils port or package.
115 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
116 has been converted to a port (misc/ctm) and will be removed from
117 FreeBSD-13. A depreciation warning will be printed to stderr by
118 the ctm command, but the functionality will remain in base for all
122 The stable/12 branch has been created in subversion from head
126 Ports for the DRM modules have been simplified. Now, amd64 users should
127 just install the drm-kmod port. All others should install
130 Graphics hardware that's newer than about 2010 usually works with
131 drm-kmod. For hardware older than 2013, however, some users will need
132 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
133 than 2008 usually only works in drm-legacy-kmod. The graphics team can
134 only commit to hardware made since 2013 due to the complexity of the
135 market and difficulty to test all the older cards effectively. If you
136 have hardware supported by drm-kmod, you are strongly encouraged to use
137 that as you will get better support.
139 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
140 elsewhere, the drm and drm2 modules will be eliminated from the src base
141 soon (with a limited exception for arm). Please update to the package asap
142 and report any issues to x11@freebsd.org.
144 Generally, anybody using the drm*-kmod packages should add
145 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
146 cross-threading surprises, especially with automatic driver
147 loading from X11 startup. These will become the defaults in 13-current
151 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
152 custom kernel and module loading configuration files must be updated
153 accordingly. Moreover, interfaces previous presented as ixlvN to the
154 system are now exposed as iavfN and network configuration files must
155 be adjusted as necessary.
158 OpenSSL has been updated to version 1.1.1. This update included
159 additional various API changes througout the base system. It is
160 important to rebuild third-party software after upgrading. The value
161 of __FreeBSD_version has been bumped accordingly.
164 The legacy DRM modules and drivers have now been added to the loader's
165 module blacklist, in favor of loading them with kld_list in rc.conf(5).
166 The module blacklist may be overridden with the loader.conf(5)
167 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
171 The cam(4) based nda(4) driver will be used over nvd(4) by default on
172 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
173 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
174 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
178 Reproducible build mode is now on by default, in preparation for
179 FreeBSD 12.0. This eliminates build metadata such as the user,
180 host, and time from the kernel (and uname), unless the working tree
181 corresponds to a modified checkout from a version control system.
182 The previous behavior can be obtained by setting the /etc/src.conf
183 knob WITHOUT_REPRODUCIBLE_BUILD.
186 The Yarrow CSPRNG has been removed from the kernel as it has not been
187 supported by its designers since at least 2003. Fortuna has been the
188 default since FreeBSD-11.
191 devctl freeze/thaw have gone into the tree, the rc scripts have been
192 updated to use them and devmatch has been changed. You should update
193 kernel, userland and rc scripts all at the same time.
196 The default interpreter has been switched from 4th to Lua.
197 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
198 interpreter. If you have custom FORTH code you will need to set
199 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
200 src.conf for the build. This will create default hard links between
201 loader and loader_4th instead of loader and loader_lua, the new default.
202 If you are using UEFI it will create the proper hard link to loader.efi.
204 bhyve uses userboot.so. It remains 4th-only until some issues are solved
205 regarding coexisting with multiple versions of FreeBSD are resolved.
208 ls(1) now respects the COLORTERM environment variable used in other
209 systems and software to indicate that a colored terminal is both
210 supported and desired. If ls(1) is suddenly emitting colors, they may
211 be disabled again by either removing the unwanted COLORTERM from your
212 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
213 may not be observed in a future release.
216 The default pager for most commands has been changed to "less". To
217 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
221 The jedec_ts(4) driver has been removed. A superset of its functionality
222 is available in the jedec_dimm(4) driver, and the manpage for that
223 driver includes migration instructions. If you have "device jedec_ts"
224 in your kernel configuration file, it must be removed.
227 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
228 This should have no effect if the kernel is booted via BIOS/legacy boot.
229 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
230 has a buggy firmware that prevents a successful boot due to use of
234 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
235 support has been removed from the tree. These ports were
236 obsolete and/or known to be broken for many years.
239 loader.efi has been augmented to participate more fully in the
240 UEFI boot manager protocol. loader.efi will now look at the
241 BootXXXX environment variable to determine if a specific kernel
242 or root partition was specified. XXXX is derived from BootCurrent.
243 efibootmgr(8) manages these standard UEFI variables.
246 zfsloader's functionality has now been folded into loader.
247 zfsloader is no longer necessary once you've updated your
248 boot blocks. For a transition period, we will install a
249 hardlink for zfsloader to loader to allow a smooth transition
250 until the boot blocks can be updated (hard link because old
251 zfs boot blocks don't understand symlinks).
254 ARM64 now have efifb support, if you want to have serial console
255 on your arm64 board when an screen is connected and the bootloader
256 setup a frambuffer for us to use, just add :
260 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
261 an screen connected as the firmware will setup a framebuffer are that
262 u-boot will expose as an EFI framebuffer.
265 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
266 or take steps to update /etc/passwd before doing installworld on
267 existing systems. Do not skip the "mergemaster -Fp" step before
268 installworld, as described in the update procedures near the bottom
269 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
270 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
271 the ntp config file contain options that change file/dir locations.
272 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
273 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
274 taking steps to ensure that all required files/dirs are accessible
278 Big endian arm support has been removed.
281 The static environment setup in kernel configs is no longer mutually
282 exclusive with the loader(8) environment by default. In order to
283 restore the previous default behavior of disabling the loader(8)
284 environment if a static environment is present, you must specify
285 loader_env.disabled=1 in the static environment.
288 The ABI of syscalls used by management tools like sockstat and
289 netstat has been broken to allow 32-bit binaries to work on
290 64-bit kernels without modification. These programs will need
291 to match the kernel in order to function. External programs may
292 require minor modifications to accommodate a change of type in
293 structures from pointers to 64-bit virtual addresses.
296 On i386 and amd64 atomics are now inlined. Out of tree modules using
297 atomics will need to be rebuilt.
300 The '%I' format in the kern.corefile sysctl limits the number of
301 core files that a process can generate to the number stored in the
302 debug.ncores sysctl. The '%I' format is replaced by the single digit
303 index. Previously, if all indexes were taken the kernel would overwrite
304 only a core file with the highest index in a filename.
305 Currently the system will create a new core file if there is a free
306 index or if all slots are taken it will overwrite the oldest one.
309 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
310 6.0.1. Please see the 20141231 entry below for information about
311 prerequisites and upgrading, if you are not already using clang 3.5.0
315 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
316 needed to be changed to work with it. This change was made with r335763
317 and requires a mergemaster / etcupdate / etc to update the installed file.
320 r334930 changed the interface between the NFS modules, so they all
321 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
324 As of r334391 lld is the default amd64 system linker; it is installed
325 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
329 The kernel / userland interface for devinfo changed, so you'll
330 need a new kernel and userland as a pair for it to work (rebuilding
331 lib/libdevinfo is all that's required). devinfo and devmatch will
332 not work, but everything else will when there's a mismatch.
335 The on-disk format for hwpmc callchain records has changed to include
336 threadid corresponding to a given record. This changes the field offsets
337 and thus requires that libpmcstat be rebuilt before using a kernel
341 The vxge(4) driver has been removed. This driver was introduced into
342 HEAD one week before the Exar left the Ethernet market and is not
343 known to be used. If you have device vxge in your kernel config file
347 The amd64 kernel now requires a ld that supports ifunc to produce a
348 working kernel, either lld or a newer binutils. lld is built by default
349 on amd64, and the 'buildkernel' target uses it automatically. However,
350 it is not the default linker, so building the kernel the traditional
351 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
352 binutils port/package). lld will soon be default, and this requirement
355 NOTE: As of r334391 lld is the default system linker on amd64, and no
356 workaround is necessary.
359 The nxge(4) driver has been removed. This driver was for PCI-X 10g
360 cards made by s2io/Neterion. The company was aquired by Exar and
361 no longer sells or supports Ethernet products. If you have device
362 nxge in your kernel config file it must be removed.
365 The tz database (tzdb) has been updated to 2018e. This version more
366 correctly models time stamps in time zones with negative DST such as
367 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
368 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
369 time zone abbreviations and the tm_isdst flag.
372 The ixgb(4) driver has been removed. This driver was for an early and
373 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
374 quickly shifted to the long lived ixgbe family. If you have device
375 ixgb in your kernel config file it must be removed.
378 The lmc(4) driver has been removed. This was a WAN interface
379 card that was already reportedly rare in 2003, and had an ambiguous
380 license. If you have device lmc in your kernel config file it must
384 Support for Arcnet networks has been removed. If you have device
385 arcnet or device cm in your kernel config file they must be
389 Support for FDDI networks has been removed. If you have device
390 fddi or device fpa in your kernel config file they must be
394 In addition to supporting RFC 3164 formatted messages, the
395 syslogd(8) service is now capable of parsing RFC 5424 formatted
396 log messages. The main benefit of using RFC 5424 is that clients
397 may now send log messages with timestamps containing year numbers,
398 microseconds and time zone offsets.
400 Similarly, the syslog(3) C library function has been altered to
401 send RFC 5424 formatted messages to the local system logging
402 daemon. On systems using syslogd(8), this change should have no
403 negative impact, as long as syslogd(8) and the C library are
404 updated at the same time. On systems using a different system
405 logging daemon, it may be necessary to make configuration
406 adjustments, depending on the software used.
408 When using syslog-ng, add the 'syslog-protocol' flag to local
409 input sources to enable parsing of RFC 5424 formatted messages:
412 unix-dgram("/var/run/log" flags(syslog-protocol));
415 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
416 of the 'imuxsock' module to let messages be processed by the
417 regular RFC 3164/5424 parsing pipeline:
419 module(load="imuxsock" SysSock.UseSpecialParser="off")
421 Do note that these changes only affect communication between local
422 applications and syslogd(8). The format that syslogd(8) uses to
423 store messages on disk or forward messages to other systems
424 remains unchanged. syslogd(8) still uses RFC 3164 for these
425 purposes. Options to customize this behaviour will be added in the
426 future. Utilities that process log files stored in /var/log are
427 thus expected to continue to function as before.
429 __FreeBSD_version has been incremented to 1200061 to denote this
433 Support for token ring networks has been removed. If you
434 have "device token" in your kernel config you should remove
435 it. No device drivers supported token ring.
438 makefs was modified to be able to tag ISO9660 El Torito boot catalog
439 entries as EFI instead of overloading the i386 tag as done previously.
440 The amd64 mkisoimages.sh script used to build amd64 ISO images for
441 release was updated to use this. This may mean that makefs must be
442 updated before "make cdrom" can be run in the release directory. This
443 should be as simple as:
445 $ cd $SRCDIR/usr.sbin/makefs
446 $ make depend all install
449 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
450 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
451 Co-existance for the transition period will come shortly. Booting is a
452 complex environment and test coverage for Lua-enabled loaders has been
453 thin, so it would be prudent to assume it might not work and make
454 provisions for backup boot methods.
457 devmatch functionality has been turned on in devd. It will automatically
458 load drivers for unattached devices. This may cause unexpected drivers to
459 be loaded. Please report any problems to current@ and imp@freebsd.org.
462 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
463 6.0.0. Please see the 20141231 entry below for information about
464 prerequisites and upgrading, if you are not already using clang 3.5.0
468 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
469 This means it is used to link the kernel and userland libraries and
470 executables, but is not yet installed as /usr/bin/ld by default.
472 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
473 WITHOUT_LLD_BOOTSTRAP=yes
476 On i386, pmtimer has been removed. Its functionality has been folded
477 into apm. It was a no-op on ACPI in current for a while now (but was still
478 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
479 from kernel config files.
482 The use of RSS hash from the network card aka flowid has been
483 disabled by default for lagg(4) as it's currently incompatible with
484 the lacp and loadbalance protocols.
486 This can be re-enabled by setting the following in loader.conf:
487 net.link.lagg.default_use_flowid="1"
490 The SW_WATCHDOG option is no longer necessary to enable the
491 hardclock-based software watchdog if no hardware watchdog is
492 configured. As before, SW_WATCHDOG will cause the software
493 watchdog to be enabled even if a hardware watchdog is configured.
496 r326887 fixes the issue described in the 20171214 UPDATING entry.
497 r326888 flips the switch back to building GELI support always.
500 r362593 broke ZFS + GELI support for reasons unknown. However,
501 it also broke ZFS support generally, so GELI has been turned off
502 by default as the lesser evil in r326857. If you boot off ZFS and/or
503 GELI, it might not be a good time to update.
506 PowerPC users must update loader(8) by rebuilding world before
507 installing a new kernel, as the protocol connecting them has
508 changed. Without the update, loader metadata will not be passed
509 successfully to the kernel and users will have to enter their
510 root partition at the kernel mountroot prompt to continue booting.
511 Newer versions of loader can boot old kernels without issue.
514 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
515 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
516 to WITH/OUT_LOADER_GELI.
519 The naive and non-compliant support of posix_fallocate(2) in ZFS
520 has been removed as of r325320. The system call now returns EINVAL
521 when used on a ZFS file. Although the new behavior complies with the
522 standard, some consumers are not prepared to cope with it.
523 One known victim is lld prior to r325420.
526 Building in a FreeBSD src checkout will automatically create object
527 directories now rather than store files in the current directory if
528 'make obj' was not ran. Calling 'make obj' is no longer necessary.
529 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
530 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
534 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
535 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
536 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
537 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
538 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
539 The UNIFIED_OBJDIR option is a transitional feature that will be
540 removed for 12.0 release; please migrate to the new format for any
541 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
542 than hardcoding paths.
545 The native-xtools target no longer installs the files by default to the
546 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
547 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
550 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
551 options are changing from controlling the build if defined / undefined
552 to controlling the build with explicit 'yes' or 'no' values. They will
553 shift to WITH/WITHOUT options to match other options in the system.
556 libstand has turned into a private library for sys/boot use only.
557 It is no longer supported as a public interface outside of sys/boot.
560 The arm port has split armv6 into armv6 and armv7. armv7 is now
561 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
562 and are running a kernel from before r324363, you will need to add
563 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
566 When building multiple kernels using KERNCONF, non-existent KERNCONF
567 files will produce an error and buildkernel will fail. Previously
568 missing KERNCONF files silently failed giving no indication as to
569 why, only to subsequently discover during installkernel that the
570 desired kernel was never built in the first place.
573 The default serial number format for CTL LUNs has changed. This will
574 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
575 or iSCSI clients care about their LUNs' serial numbers. Users who
576 require serial number stability should hardcode serial numbers in
580 For 32-bit arm compiled for hard-float support, soft-floating point
581 binaries now always get their shared libraries from
582 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
583 /usr/libsoft also existed). Only users with a hard-float ld.so, but
584 soft-float everything else should be affected.
587 The geli password typed at boot is now hidden. To restore the previous
588 behavior, see geli(8) for configuration options.
591 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
592 sysctl values. Minor nit, but requires a rebuild of both world/kernel
596 "make check" behavior (made in ^/head@r295380) has been changed to
597 execute from a limited sandbox, as opposed to executing from
601 - The "beforecheck" and "aftercheck" targets are now specified.
602 - ${CHECKDIR} (added in commit noted above) has been removed.
603 - Legacy behavior can be enabled by setting
604 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
606 If the limited sandbox mode is enabled, "make check" will execute
607 "make distribution", then install, execute the tests, and clean up the
608 sandbox if successful.
610 The "make distribution" and "make install" targets are typically run as
611 root to set appropriate permissions and ownership at installation time.
612 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
613 environment if executing "make check" with limited sandbox mode using
614 an unprivileged user.
617 Since the switch to GPT disk labels, fsck for UFS/FFS has been
618 unable to automatically find alternate superblocks. As of r322297,
619 the information needed to find alternate superblocks has been
620 moved to the end of the area reserved for the boot block.
621 Filesystems created with a newfs of this vintage or later
622 will create the recovery information. If you have a filesystem
623 created prior to this change and wish to have a recovery block
624 created for your filesystem, you can do so by running fsck in
625 foreground mode (i.e., do not use the -p or -y options). As it
626 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
627 to which you should answer yes.
630 As of r321665, an NFSv4 server configuration that services
631 Kerberos mounts or clients that do not support the uid/gid in
632 owner/owner_group string capability, must explicitly enable
633 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
634 machine's /etc/rc.conf file.
637 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
638 Please see the 20141231 entry below for information about prerequisites
639 and upgrading, if you are not already using clang 3.5.0 or higher.
642 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
643 r-commands (rlogin, rsh, etc.) to be built with the base system.
646 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
647 a very major ABI incompatible change, so users of FreeBSD/powerpc must
648 be careful when performing source upgrades. It is best to run
649 'make installworld' from an alternate root system, either a live
650 CD/memory stick, or a temporary root partition. Additionally, all ports
651 must be recompiled. powerpc64 is largely unaffected, except in the case
652 of 32-bit compatibility. All 32-bit binaries will be affected.
655 Forward compatibility for the "ino64" project have been committed. This
656 will allow most new binaries to run on older kernels in a limited
657 fashion. This prevents many of the common foot-shooting actions in the
658 upgrade as well as the limited ability to roll back the kernel across
659 the ino64 upgrade. Complicated use cases may not work properly, though
660 enough simpler ones work to allow recovery in most situations.
663 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
664 if you require the GPL compiler.
667 The internal ABI used for communication between the NFS kernel modules
668 was changed by r320085, so __FreeBSD_version was bumped to
669 ensure all the NFS related modules are updated together.
672 The ABI of struct event was changed by extending the data
673 member to 64bit and adding ext fields. For upgrade, same
674 precautions as for the entry 20170523 "ino64" must be
678 The GNU roff toolchain has been removed from base. To render manpages
679 which are not supported by mandoc(1), man(1) can fallback on GNU roff
680 from ports (and recommends to install it).
681 To render roff(7) documents, consider using GNU roff from ports or the
682 heirloom doctools roff toolchain from ports via pkg install groff or
683 via pkg install heirloom-doctools.
686 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
687 smaller runtime footprint builds. This is useful for embedded systems
688 which only require one chipset support.
690 If you load it as a module, make sure this is in /boot/loader.conf:
694 This will load the HAL, all chip/RF backends and if_ath_pci.
695 If you have if_ath_pci in /boot/loader.conf, ensure it is after
696 if_ath or it will not load any HAL chipset support.
698 If you want to selectively load things (eg on ye cheape ARM/MIPS
699 platforms where RAM is at a premium) you should:
702 * load the chip modules in question
703 * load ath_rate, ath_dfs
705 * load if_ath_pci and/or if_ath_ahb depending upon your particular
706 bus bind type - this is where probe/attach is done.
708 For further comments/feedback, poke adrian@ .
711 The "ino64" 64-bit inode project has been committed, which extends
712 a number of types to 64 bits. Upgrading in place requires care and
713 adherence to the documented upgrade procedure.
715 If using a custom kernel configuration ensure that the
716 COMPAT_FREEBSD11 option is included (as during the upgrade the
717 system will be running the ino64 kernel with the existing world).
719 For the safest in-place upgrade begin by removing previous build
720 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
721 full procedure documented below under the heading "To rebuild
722 everything and install it on the current system." Specifically,
723 a reboot is required after installing the new kernel before
727 The NATM framework including the en(4), fatm(4), hatm(4), and
728 patm(4) devices has been removed. Consumers should plan a
729 migration before the end-of-life date for FreeBSD 11.
732 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
733 diff has not been implemented, if those are needed a newer version of
734 GNU diff is available via the diffutils package under the gdiff name.
737 As of r316810 for ipfilter, keep frags is no longer assumed when
738 keep state is specified in a rule. r316810 aligns ipfilter with
739 documentation in man pages separating keep frags from keep state.
740 This allows keep state to be specified without forcing keep frags
741 and allows keep frags to be specified independently of keep state.
742 To maintain previous behaviour, also specify keep frags with
743 keep state (as documented in ipf.conf.5).
746 arm64 builds now use the base system LLD 4.0.0 linker by default,
747 instead of requiring that the aarch64-binutils port or package be
748 installed. To continue using aarch64-binutils, set
749 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
752 The UDP optimization in entry 20160818 that added the sysctl
753 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
754 packets will no longer be treated as L3 broadcast packets.
757 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
758 use any explicitly assigned loopback address available in the jail
759 instead of using the first assigned address of the jail.
762 The ctl.ko module no longer implements the iSCSI target frontend:
763 cfiscsi.ko does instead.
765 If building cfiscsi.ko as a kernel module, the module can be loaded
766 via one of the following methods:
767 - `cfiscsi_load="YES"` in loader.conf(5).
768 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
769 - ctladm(8)/ctld(8), when compiled with iSCSI support
770 (`WITH_ISCSI=yes` in src.conf(5))
772 Please see cfiscsi(4) for more details.
775 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
776 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
777 same source (previously, the dependency of mmcsd.ko on mmc.ko was
778 missing, but mmcsd.ko now will refuse to load if it is incompatible
782 The syntax of ipfw(8) named states was changed to avoid ambiguity.
783 If you have used named states in the firewall rules, you need to modify
784 them after installworld and before rebooting. Now named states must
785 be prefixed with colon.
788 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
789 removed as the userland we provide cannot use them. The KMS version
790 (sys/dev/drm2) supports the same hardware.
793 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
794 Please see the 20141231 entry below for information about prerequisites
795 and upgrading, if you are not already using clang 3.5.0 or higher.
798 The code that provides support for ZFS .zfs/ directory functionality
799 has been reimplemented. It's not possible now to create a snapshot
800 by mkdir under .zfs/snapshot/. That should be the only user visible
804 EISA bus support has been removed. The WITH_EISA option is no longer
808 MCA bus support has been removed.
811 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
812 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
815 The EM_MULTIQUEUE kernel configuration option is deprecated now that
816 the em(4) driver conforms to iflib specifications.
819 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
820 IFLIB. If you have a custom kernel configuration that excludes em(4)
821 but you use igb(4), you need to re-add em(4) to your custom configuration.
824 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
825 Please see the 20141231 entry below for information about prerequisites
826 and upgrading, if you are not already using clang 3.5.0 or higher.
829 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
830 Please see the 20141231 entry below for information about prerequisites
831 and upgrading, if you are not already using clang 3.5.0 or higher.
834 The layout of the pmap structure has changed for powerpc to put the pmap
835 statistics at the front for all CPU variations. libkvm(3) and all tools
836 that link against it need to be recompiled.
839 isl(4) and cyapa(4) drivers now require a new driver,
840 chromebook_platform(4), to work properly on Chromebook-class hardware.
841 On other types of hardware the drivers may need to be configured using
842 device hints. Please see the corresponding manual pages for details.
845 The urtwn(4) driver was merged into rtwn(4) and now consists of
846 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
848 Also, firmware for RTL8188CE was renamed due to possible name
849 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
852 GNU rcs has been removed from base. It is available as packages:
853 - rcs: Latest GPLv3 GNU rcs version.
854 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
858 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
859 modules now requires that the kernel configuration contain the
860 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
863 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
864 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
867 Relocatable object files with the extension of .So have been renamed
868 to use an extension of .pico instead. The purpose of this change is
869 to avoid a name clash with shared libraries on case-insensitive file
870 systems. On those file systems, foo.So is the same file as foo.so.
873 GNU rcs has been turned off by default. It can (temporarily) be built
874 again by adding WITH_RCS knob in src.conf.
875 Otherwise, GNU rcs is available from packages:
876 - rcs: Latest GPLv3 GNU rcs version.
877 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
880 The backup_uses_rcs functionality has been removed from rc.subr.
883 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
884 two separate components, QUEUE_MACRO_DEBUG_TRACE and
885 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
886 QUEUE_MACRO_DEBUG behavior.
889 r304787 changed some ioctl interfaces between the iSCSI userspace
890 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
891 rebuilt to work with new kernels. __FreeBSD_version has been bumped
895 The UDP receive code has been updated to only treat incoming UDP
896 packets that were addressed to an L2 broadcast address as L3
897 broadcast packets. It is not expected that this will affect any
898 standards-conforming UDP application. The new behaviour can be
899 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
903 Remove the openbsd_poll system call.
904 __FreeBSD_version has been bumped because of this.
907 The stable/11 branch has been created from head@r302406.
910 The libc stub for the pipe(2) system call has been replaced with
911 a wrapper that calls the pipe2(2) system call and the pipe(2)
912 system call is now only implemented by the kernels that include
913 "options COMPAT_FREEBSD10" in their config file (this is the
914 default). Users should ensure that this option is enabled in
915 their kernel or upgrade userspace to r302092 before upgrading their
919 CAM will now strip leading spaces from SCSI disks' serial numbers.
920 This will affect users who create UFS filesystems on SCSI disks using
921 those disk's diskid device nodes. For example, if /etc/fstab
922 previously contained a line like
923 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
924 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
925 transforms like gmirror may also be affected. ZFS users should
929 The bitstring(3) API has been updated with new functionality and
930 improved performance. But it is binary-incompatible with the old API.
931 Objects built with the new headers may not be linked against objects
932 built with the old headers.
935 The brk and sbrk functions have been removed from libc on arm64.
936 Binutils from ports has been updated to not link to these
937 functions and should be updated to the latest version before
938 installing a new libc.
941 The armv6 port now defaults to hard float ABI. Limited support
942 for running both hardfloat and soft float on the same system
943 is available using the libraries installed with -DWITH_LIBSOFT.
944 This has only been tested as an upgrade path for installworld
945 and packages may fail or need manual intervention to run. New
946 packages will be needed.
948 To update an existing self-hosted armv6hf system, you must add
949 TARGET_ARCH=armv6 on the make command line for both the build
950 and the install steps.
953 Kernel modules compiled outside of a kernel build now default to
954 installing to /boot/modules instead of /boot/kernel. Many kernel
955 modules built this way (such as those in ports) already overrode
956 KMODDIR explicitly to install into /boot/modules. However,
957 manually building and installing a module from /sys/modules will
958 now install to /boot/modules instead of /boot/kernel.
961 The CAM I/O scheduler has been committed to the kernel. There should be
962 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
963 list of known rogues that claim support for this but actually corrupt
964 data is believed to be complete, be on the lookout for data
965 corruption. The known rogue list is believed to be complete:
967 o Crucial MX100, M550 drives with MU01 firmware.
968 o Micron M510 and M550 drives with MU01 firmware.
969 o Micron M500 prior to MU07 firmware
970 o Samsung 830, 840, and 850 all firmwares
971 o FCCT M500 all firmwares
973 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
974 with working NCQ TRIM. For Micron branded drives, see your sales rep for
975 updated firmware. Black listed drives will work correctly because these
976 drives work correctly so long as no NCQ TRIMs are sent to them. Given
977 this list is the same as found in Linux, it's believed there are no
978 other rogues in the market place. All other models from the above
981 To be safe, if you are at all concerned, you can quirk each of your
982 drives to prevent NCQ from being sent by setting:
983 kern.cam.ada.X.quirks="0x2"
984 in loader.conf. If the drive requires the 4k sector quirk, set the
988 The FAST_DEPEND build option has been removed and its functionality is
989 now the one true way. The old mkdep(1) style of 'make depend' has
990 been removed. See 20160311 for further details.
993 Resource range types have grown from unsigned long to uintmax_t. All
994 drivers, and anything using libdevinfo, need to be recompiled.
997 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
998 builds. It no longer runs mkdep(1) during 'make depend', and the
999 'make depend' stage can safely be skipped now as it is auto ran
1000 when building 'make all' and will generate all SRCS and DPSRCS before
1001 building anything else. Dependencies are gathered at compile time with
1002 -MF flags kept in separate .depend files per object file. Users should
1003 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1004 stale .depend files.
1007 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1008 kernel modules. Therefore, if you load any kernel modules at boot time,
1009 please install the boot loaders after you install the kernel, but before
1013 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1014 make installkernel KERNCONF=YOUR_KERNEL_HERE
1015 make -C sys/boot install
1016 <reboot in single user>
1018 Then follow the usual steps, described in the General Notes section,
1022 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1023 see the 20141231 entry below for information about prerequisites and
1024 upgrading, if you are not already using clang 3.5.0 or higher.
1027 The AIO subsystem is now a standard part of the kernel. The
1028 VFS_AIO kernel option and aio.ko kernel module have been removed.
1029 Due to stability concerns, asynchronous I/O requests are only
1030 permitted on sockets and raw disks by default. To enable
1031 asynchronous I/O requests on all file types, set the
1032 vfs.aio.enable_unsafe sysctl to a non-zero value.
1035 The ELF object manipulation tool objcopy is now provided by the
1036 ELF Tool Chain project rather than by GNU binutils. It should be a
1037 drop-in replacement, with the addition of arm64 support. The
1038 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1039 to obtain the GNU version if necessary.
1042 Building ZFS pools on top of zvols is prohibited by default. That
1043 feature has never worked safely; it's always been prone to deadlocks.
1044 Using a zvol as the backing store for a VM guest's virtual disk will
1045 still work, even if the guest is using ZFS. Legacy behavior can be
1046 restored by setting vfs.zfs.vol.recursive=1.
1049 The NONE and HPN patches has been removed from OpenSSH. They are
1050 still available in the security/openssh-portable port.
1053 With the addition of ypldap(8), a new _ypldap user is now required
1054 during installworld. "mergemaster -p" can be used to add the user
1055 prior to installworld, as documented in the handbook.
1058 The tftp loader (pxeboot) now uses the option root-path directive. As a
1059 consequence it no longer looks for a pxeboot.4th file on the tftp
1060 server. Instead it uses the regular /boot infrastructure as with the
1064 The code to start recording plug and play data into the modules has
1065 been committed. While the old tools will properly build a new kernel,
1066 a number of warnings about "unknown metadata record 4" will be produced
1067 for an older kldxref. To avoid such warnings, make sure to rebuild
1068 the kernel toolchain (or world). Make sure that you have r292078 or
1069 later when trying to build 292077 or later before rebuilding.
1072 Debug data files are now built by default with 'make buildworld' and
1073 installed with 'make installworld'. This facilitates debugging but
1074 requires more disk space both during the build and for the installed
1075 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1079 r291527 changed the internal interface between the nfsd.ko and
1080 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1081 __FreeBSD_version has been bumped because of this.
1084 Add support for unicode collation strings leads to a change of
1085 order of files listed by ls(1) for example. To get back to the old
1086 behaviour, set LC_COLLATE environment variable to "C".
1088 Databases administrators will need to reindex their databases given
1089 collation results will be different.
1091 Due to a bug in install(1) it is recommended to remove the ancient
1092 locales before running make installworld.
1094 rm -rf /usr/share/locale/*
1097 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1098 libcrypto.so.7 or libssl.so.7 must be recompiled.
1101 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1102 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1103 should be replaced with isp_2400 and isp_2500 modules respectively.
1106 The build previously allowed using 'make -n' to not recurse into
1107 sub-directories while showing what commands would be executed, and
1108 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1109 and 'make -N' will not.
1112 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1113 and etcupdate will now use this file. A custom sendmail.cf is now
1114 updated via this mechanism rather than via installworld. If you had
1115 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1116 want to remove the exclusion or change it to "always install".
1117 /etc/mail/sendmail.cf is now managed the same way regardless of
1118 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1119 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1122 Compatibility shims for legacy ATA device names have been removed.
1123 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1124 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1125 environment variables, /dev/ad* and /dev/ar* symbolic links.
1128 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1129 Please see the 20141231 entry below for information about prerequisites
1130 and upgrading, if you are not already using clang 3.5.0 or higher.
1133 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1134 and renamed from .symbols to .debug. This reduces the size requirements
1135 on the boot partition or file system and provides consistency with
1136 userland debug files.
1138 When using the supported kernel installation method the
1139 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1140 as is done with /boot/kernel.
1142 Developers wishing to maintain the historical behavior of installing
1143 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1146 The wireless drivers had undergone changes that remove the 'parent
1147 interface' from the ifconfig -l output. The rc.d network scripts
1148 used to check presence of a parent interface in the list, so old
1149 scripts would fail to start wireless networking. Thus, etcupdate(3)
1150 or mergemaster(8) run is required after kernel update, to update your
1151 rc.d scripts in /etc.
1154 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1155 These configurations are now automatically interpreted as
1156 'scrub fragment reassemble'.
1159 Kernel-loadable modules for the random(4) device are back. To use
1160 them, the kernel must have
1163 options RANDOM_LOADABLE
1165 kldload(8) can then be used to load random_fortuna.ko
1166 or random_yarrow.ko. Please note that due to the indirect
1167 function calls that the loadable modules need to provide,
1168 the build-in variants will be slightly more efficient.
1170 The random(4) kernel option RANDOM_DUMMY has been retired due to
1171 unpopularity. It was not all that useful anyway.
1174 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1175 Control over building the ELF Tool Chain tools is now provided by
1176 the WITHOUT_TOOLCHAIN knob.
1179 The polarity of Pulse Per Second (PPS) capture events with the
1180 uart(4) driver has been corrected. Prior to this change the PPS
1181 "assert" event corresponded to the trailing edge of a positive PPS
1182 pulse and the "clear" event was the leading edge of the next pulse.
1184 As the width of a PPS pulse in a typical GPS receiver is on the
1185 order of 1 millisecond, most users will not notice any significant
1186 difference with this change.
1188 Anyone who has compensated for the historical polarity reversal by
1189 configuring a negative offset equal to the pulse width will need to
1190 remove that workaround.
1193 The default group assigned to /dev/dri entries has been changed
1194 from 'wheel' to 'video' with the id of '44'. If you want to have
1195 access to the dri devices please add yourself to the video group
1198 # pw groupmod video -m $USER
1201 The menu.rc and loader.rc files will now be replaced during
1202 upgrades. Please migrate local changes to menu.rc.local and
1203 loader.rc.local instead.
1206 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1207 strings and strip have been removed. The src.conf(5) knob
1208 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1211 As ZFS requires more kernel stack pages than is the default on some
1212 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1213 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1215 Please consider using 'options KSTACK_PAGES=X' where X is greater
1216 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1219 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1220 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1221 default, i.e., they will not contain "::". For example, instead
1222 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1223 to have a more specific match, such as different map entries for
1224 IPv6:0:0 vs IPv6:0. This change requires that configuration
1225 data (including maps, files, classes, custom ruleset, etc.) must
1226 use the same format, so make certain such configuration data is
1227 upgrading. As a very simple check search for patterns like
1228 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1229 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1230 the cf option UseCompressedIPv6Addresses.
1233 The default kernel entropy-processing algorithm is now
1234 Fortuna, replacing Yarrow.
1236 Assuming you have 'device random' in your kernel config
1237 file, the configurations allow a kernel option to override
1238 this default. You may choose *ONE* of:
1240 options RANDOM_YARROW # Legacy /dev/random algorithm.
1241 options RANDOM_DUMMY # Blocking-only driver.
1243 If you have neither, you get Fortuna. For most people,
1244 read no further, Fortuna will give a /dev/random that works
1245 like it always used to, and the difference will be irrelevant.
1247 If you remove 'device random', you get *NO* kernel-processed
1248 entropy at all. This may be acceptable to folks building
1249 embedded systems, but has complications. Carry on reading,
1250 and it is assumed you know what you need.
1252 *PLEASE* read random(4) and random(9) if you are in the
1253 habit of tweaking kernel configs, and/or if you are a member
1254 of the embedded community, wanting specific and not-usual
1255 behaviour from your security subsystems.
1257 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1258 random', you will NOT have a functioning /dev/random, and
1259 many cryptographic features will not work, including SSH.
1260 You may also find strange behaviour from the random(3) set
1261 of library functions, in particular sranddev(3), srandomdev(3)
1262 and arc4random(3). The reason for this is that the KERN_ARND
1263 sysctl only returns entropy if it thinks it has some to
1264 share, and with RANDOM_DUMMY or no 'device random' this
1268 An additional fix for the issue described in the 20150614 sendmail
1269 entry below has been committed in revision 284717.
1272 FreeBSD's old make (fmake) has been removed from the system. It is
1273 available as the devel/fmake port or via pkg install fmake.
1276 The fix for the issue described in the 20150614 sendmail entry
1277 below has been committed in revision 284436. The work
1278 around described in that entry is no longer needed unless the
1279 default setting is overridden by a confDH_PARAMETERS configuration
1280 setting of '5' or pointing to a 512 bit DH parameter file.
1283 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1284 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1285 and devel/kyua to version 0.20+ and adjust any calling code to work
1286 with Kyuafile and kyua.
1289 The import of openssl to address the FreeBSD-SA-15:10.openssl
1290 security advisory includes a change which rejects handshakes
1291 with DH parameters below 768 bits. sendmail releases prior
1292 to 8.15.2 (not yet released), defaulted to a 512 bit
1293 DH parameter setting for client connections. To work around
1294 this interoperability, sendmail can be configured to use a
1295 2048 bit DH parameter by:
1297 1. Edit /etc/mail/`hostname`.mc
1298 2. If a setting for confDH_PARAMETERS does not exist or
1299 exists and is set to a string beginning with '5',
1300 replace it with '2'.
1301 3. If a setting for confDH_PARAMETERS exists and is set to
1302 a file path, create a new file with:
1303 openssl dhparam -out /path/to/file 2048
1304 4. Rebuild the .cf file:
1305 cd /etc/mail/; make; make install
1306 5. Restart sendmail:
1307 cd /etc/mail/; make restart
1309 A sendmail patch is coming, at which time this file will be
1313 Generation of legacy formatted entries have been disabled by default
1314 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1315 entries were converted to use the new format by default when the new,
1316 machine independent format have been added and supported since FreeBSD
1319 Please see the pwd_mkdb(8) manual page for further details.
1322 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1323 20141231 entry below for information about prerequisites and upgrading,
1324 if you are not already using 3.5.0 or higher.
1327 TI platform code switched to using vendor DTS files and this update
1328 may break existing systems running on Beaglebone, Beaglebone Black,
1331 - dtb files should be regenerated/reinstalled. Filenames are the
1332 same but content is different now
1333 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1334 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1335 addressing scheme is now pin 25 on /dev/gpioc3.
1336 - Pandaboard: /etc/ttys should be updated, serial console device is
1337 now /dev/ttyu2, not /dev/ttyu0
1340 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1341 If you need the GNU extension from groff soelim(1), install groff
1342 from package: pkg install groff, or via ports: textproc/groff.
1345 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1346 defined in symlink(7); previously symlinks were silently ignored.
1349 The const qualifier has been removed from iconv(3) to comply with
1350 POSIX. The ports tree is aware of this from r384038 onwards.
1353 Libraries specified by LIBADD in Makefiles must have a corresponding
1354 DPADD_<lib> variable to ensure correct dependencies. This is now
1355 enforced in src.libnames.mk.
1358 From legacy ata(4) driver was removed support for SATA controllers
1359 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1360 Kernel modules ataahci and ataadaptec were removed completely,
1361 replaced by ahci and mvs modules respectively.
1364 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1365 the 20141231 entry below for information about prerequisites and
1366 upgrading, if you are not already using 3.5.0 or higher.
1369 The 32-bit PowerPC kernel has been changed to a position-independent
1370 executable. This can only be booted with a version of loader(8)
1371 newer than January 31, 2015, so make sure to update both world and
1372 kernel before rebooting.
1375 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1376 but before r278950, the RNG was not seeded properly. Immediately
1377 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1378 ssh keys or openssl keys) that were generated w/ a kernel from that
1379 range. This does not affect programs that directly used /dev/random
1380 or /dev/urandom. All userland uses of arc4random(3) are affected.
1383 The autofs(4) ABI was changed in order to restore binary compatibility
1384 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1385 with the new kernel.
1388 The powerpc64 kernel has been changed to a position-independent
1389 executable. This can only be booted with a new version of loader(8),
1390 so make sure to update both world and kernel before rebooting.
1393 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1394 only release, no new features have been added. Please see the 20141231
1395 entry below for information about prerequisites and upgrading, if you
1396 are not already using 3.5.0.
1399 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1400 taken from the ELF Tool Chain project rather than GNU binutils. They
1401 should be drop-in replacements, with the addition of arm64 support.
1402 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1403 binutils tools, if necessary. See 20150805 for updated information.
1406 The default Unbound configuration now enables remote control
1407 using a local socket. Users who have already enabled the
1408 local_unbound service should regenerate their configuration
1409 by running "service local_unbound setup" as root.
1412 The GNU texinfo and GNU info pages have been removed.
1413 To be able to view GNU info pages please install texinfo from ports.
1416 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1418 As of this release, a prerequisite for building clang, llvm and lldb is
1419 a C++11 capable compiler and C++11 standard library. This means that to
1420 be able to successfully build the cross-tools stage of buildworld, with
1421 clang as the bootstrap compiler, your system compiler or cross compiler
1422 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1423 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1426 On any standard FreeBSD 10.x or 11.x installation, where clang and
1427 libc++ are on by default (that is, on x86 or arm), this should work out
1430 On 9.x installations where clang is enabled by default, e.g. on x86 and
1431 powerpc, libc++ will not be enabled by default, so libc++ should be
1432 built (with clang) and installed first. If both clang and libc++ are
1433 missing, build clang first, then use it to build libc++.
1435 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1436 the instructions for 9.x above.
1438 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1439 default, and do not build clang.
1441 Many embedded systems are resource constrained, and will not be able to
1442 build clang in a reasonable time, or in some cases at all. In those
1443 cases, cross building bootable systems on amd64 is a workaround.
1445 This new version of clang introduces a number of new warnings, of which
1446 the following are most likely to appear:
1450 This warns in two cases, for both C and C++:
1451 * When the code is trying to take the absolute value of an unsigned
1452 quantity, which is effectively a no-op, and almost never what was
1453 intended. The code should be fixed, if at all possible. If you are
1454 sure that the unsigned quantity can be safely cast to signed, without
1455 loss of information or undefined behavior, you can add an explicit
1456 cast, or disable the warning.
1458 * When the code is trying to take an absolute value, but the called
1459 abs() variant is for the wrong type, which can lead to truncation.
1460 If you want to disable the warning instead of fixing the code, please
1461 make sure that truncation will not occur, or it might lead to unwanted
1464 -Wtautological-undefined-compare and
1465 -Wundefined-bool-conversion
1467 These warn when C++ code is trying to compare 'this' against NULL, while
1468 'this' should never be NULL in well-defined C++ code. However, there is
1469 some legacy (pre C++11) code out there, which actively abuses this
1470 feature, which was less strictly defined in previous C++ versions.
1472 Squid and openjdk do this, for example. The warning can be turned off
1473 for C++98 and earlier, but compiling the code in C++11 mode might result
1474 in unexpected behavior; for example, the parts of the program that are
1475 unreachable could be optimized away.
1478 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1479 kernel sources have been removed. The .h files remain, since some
1480 utilities include them. This will need to be fixed later.
1481 If "mount -t oldnfs ..." is attempted, it will fail.
1482 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1483 the utilities will report errors.
1486 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1487 directories to top level SUBDIR variable when their parent
1488 directory is included in LOCAL_DIRS. Users with build systems with
1489 such hierarchies and without SUBDIR entries in the parent
1490 directory Makefiles should add them or add the directories to
1494 faith(4) and faithd(8) have been removed from the base system. Faith
1495 has been obsolete for a very long time.
1498 vt(4), the new console driver, is enabled by default. It brings
1499 support for Unicode and double-width characters, as well as
1500 support for UEFI and integration with the KMS kernel video
1503 You may need to update your console settings in /etc/rc.conf,
1504 most probably the keymap. During boot, /etc/rc.d/syscons will
1505 indicate what you need to do.
1507 vt(4) still has issues and lacks some features compared to
1508 syscons(4). See the wiki for up-to-date information:
1509 https://wiki.freebsd.org/Newcons
1511 If you want to keep using syscons(4), you can do so by adding
1512 the following line to /boot/loader.conf:
1516 pjdfstest has been integrated into kyua as an opt-in test suite.
1517 Please see share/doc/pjdfstest/README for more details on how to
1521 gperf has been removed from the base system for architectures
1522 that use clang. Ports that require gperf will obtain it from the
1526 pjdfstest has been moved from tools/regression/pjdfstest to
1530 At svn r271982, The default linux compat kernel ABI has been adjusted
1531 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1532 update. If you wish to continue using the linux-f10 compat ports,
1533 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1534 encouraged to update their linux-compat packages to linux-c6 during
1535 their next update cycle.
1538 The ofwfb driver, used to provide a graphics console on PowerPC when
1539 using vt(4), no longer allows mmap() of all physical memory. This
1540 will prevent Xorg on PowerPC with some ATI graphics cards from
1541 initializing properly unless x11-servers/xorg-server is updated to
1545 The xdev targets have been converted to using TARGET and
1546 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1549 The default unbound configuration has been modified to address
1550 issues with reverse lookups on networks that use private
1551 address ranges. If you use the local_unbound service, run
1552 "service local_unbound setup" as root to regenerate your
1553 configuration, then "service local_unbound reload" to load the
1557 The GNU texinfo and GNU info pages are not built and installed
1558 anymore, WITH_INFO knob has been added to allow to built and install
1560 UPDATE: see 20150102 entry on texinfo's removal
1563 The GNU readline library is now an INTERNALLIB - that is, it is
1564 statically linked into consumers (GDB and variants) in the base
1565 system, and the shared library is no longer installed. The
1566 devel/readline port is available for third party software that
1570 The Itanium architecture (ia64) has been removed from the list of
1571 known architectures. This is the first step in the removal of the
1575 Commit r268115 has added NFSv4.1 server support, merged from
1576 projects/nfsv4.1-server. Since this includes changes to the
1577 internal interfaces between the NFS related modules, a full
1578 build of the kernel and modules will be necessary.
1579 __FreeBSD_version has been bumped.
1582 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1583 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1584 which differs from the behaviour controlled by this knob.)
1587 Maximal length of the serial number in CTL was increased from 16 to
1588 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1589 and ctld, need to be rebuilt to work with a new kernel.
1592 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1593 1 respectively to match the upstream numbers. They were out of
1594 sync because, when they were originally added to FreeBSD, the
1595 upstream versions were not respected. These libraries are private
1596 and not yet built by default, so renumbering them should be a
1597 non-issue. However, unclean source trees will yield broken test
1598 programs once the operator executes "make delete-old-libs" after a
1599 "make installworld".
1601 Additionally, the atf-sh binary was made private by moving it into
1602 /usr/libexec/. Already-built shell test programs will keep the
1603 path to the old binary so they will break after "make delete-old"
1606 If you are using WITH_TESTS=yes (not the default), wipe the object
1607 tree and rebuild from scratch to prevent spurious test failures.
1608 This is only needed once: the misnumbered libraries and misplaced
1609 binaries have been added to OptionalObsoleteFiles.inc so they will
1610 be removed during a clean upgrade.
1613 Clang and llvm have been upgraded to 3.4.1 release.
1616 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1617 be removed to avoid issues in the future (and has been added to
1621 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1622 past, it affected all builds that used the bsd.*.mk files. The old
1623 behavior was a bug, but people may have relied upon it. To get this
1624 behavior back, you can .include /etc/src.conf from /etc/make.conf
1625 (which is still global and isn't changed). This also changes the
1626 behavior of incremental builds inside the tree of individual
1627 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1628 Although this has survived make universe and some upgrade scenarios,
1629 other upgrade scenarios may have broken. At least one form of
1630 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1631 as well... In cases where MAKESYSPATH isn't working with this
1632 setting, you'll need to set it to the full path to your tree.
1634 One side effect of all this cleaning up is that bsd.compiler.mk
1635 is no longer implicitly included by bsd.own.mk. If you wish to
1636 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1640 The lindev device has been removed since /dev/full has been made a
1641 standard device. __FreeBSD_version has been bumped.
1644 The knob WITHOUT_VI was added to the base system, which controls
1645 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1646 in order to reorder files share/termcap and didn't build ex(1) as a
1647 build tool, so building/installing with WITH_VI is highly advised for
1648 build hosts for older releases.
1650 This issue has been fixed in stable/9 and stable/10 in r277022 and
1651 r276991, respectively.
1654 The YES_HESIOD knob has been removed. It has been obsolete for
1655 a decade. Please move to using WITH_HESIOD instead or your builds
1656 will silently lack HESIOD.
1659 The uart(4) driver has been changed with respect to its handling
1660 of the low-level console. Previously the uart(4) driver prevented
1661 any process from changing the baudrate or the CLOCAL and HUPCL
1662 control flags. By removing the restrictions, operators can make
1663 changes to the serial console port without having to reboot.
1664 However, when getty(8) is started on the serial device that is
1665 associated with the low-level console, a misconfigured terminal
1666 line in /etc/ttys will now have a real impact.
1667 Before upgrading the kernel, make sure that /etc/ttys has the
1668 serial console device configured as 3wire without baudrate to
1669 preserve the previous behaviour. E.g:
1670 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1673 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1674 to improve performance. To re-enable it, if needed, run rpcbind
1675 with command line option -W.
1678 Switched back to the GPL dtc compiler due to updates in the upstream
1679 dts files not being supported by the BSDL dtc compiler. You will need
1680 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1681 may result while building dtb files during a kernel build if you fail
1682 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1685 Clang and llvm have been upgraded to 3.4 release.
1688 The nve(4) driver has been removed. Please use the nfe(4) driver
1689 for NVIDIA nForce MCP Ethernet adapters instead.
1692 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1693 This could cause certain C++ applications using shared libraries built
1694 against the previous version of libc++ to crash. The incompatibility
1695 has now been fixed, but any C++ applications or shared libraries built
1696 between r261283 and r261801 should be recompiled.
1699 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1700 capability mode support. Please note that enabling the feature in
1701 kernel is still highly recommended.
1704 OpenSSH is now built with sandbox support, and will use sandbox as
1705 the default privilege separation method. This requires Capsicum
1706 capability mode support in kernel.
1709 The libelf and libdwarf libraries have been updated to newer
1710 versions from upstream. Shared library version numbers for
1711 these two libraries were bumped. Any ports or binaries
1712 requiring these two libraries should be recompiled.
1713 __FreeBSD_version is bumped to 1100006.
1716 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1717 instead of providing an explicit one, this would prevent such
1718 Makefile from providing its own Kyuafile in the future during
1719 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1720 intervention is needed to clean an objdir if you use NO_CLEAN:
1721 # find /usr/obj -name Kyuafile | xargs rm -f
1724 The behavior of gss_pseudo_random() for the krb5 mechanism
1725 has changed, for applications requesting a longer random string
1726 than produced by the underlying enctype's pseudo-random() function.
1727 In particular, the random string produced from a session key of
1728 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1729 be different at the 17th octet and later, after this change.
1730 The counter used in the PRF+ construction is now encoded as a
1731 big-endian integer in accordance with RFC 4402.
1732 __FreeBSD_version is bumped to 1100004.
1735 The WITHOUT_ATF build knob has been removed and its functionality
1736 has been subsumed into the more generic WITHOUT_TESTS. If you were
1737 using the former to disable the build of the ATF libraries, you
1738 should change your settings to use the latter.
1741 The default version of mtree is nmtree which is obtained from
1742 NetBSD. The output is generally the same, but may vary
1743 slightly. If you found you need identical output adding
1744 "-F freebsd9" to the command line should do the trick. For the
1745 time being, the old mtree is available as fmtree.
1748 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1749 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1750 1.1.4_8 and verify bsdyml not linked in, before running "make
1752 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1754 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1757 The stable/10 branch has been created in subversion from head
1764 Avoid using make -j when upgrading. While generally safe, there are
1765 sometimes problems using -j to upgrade. If your upgrade fails with
1766 -j, please try again without -j. From time to time in the past there
1767 have been problems using -j with buildworld and/or installworld. This
1768 is especially true when upgrading between "distant" versions (eg one
1769 that cross a major release boundary or several minor releases, or when
1770 several months have passed on the -current branch).
1772 Sometimes, obscure build problems are the result of environment
1773 poisoning. This can happen because the make utility reads its
1774 environment when searching for values for global variables. To run
1775 your build attempts in an "environmental clean room", prefix all make
1776 commands with 'env -i '. See the env(1) manual page for more details.
1778 When upgrading from one major version to another it is generally best to
1779 upgrade to the latest code in the currently installed branch first, then
1780 do an upgrade to the new branch. This is the best-tested upgrade path,
1781 and has the highest probability of being successful. Please try this
1782 approach if you encounter problems with a major version upgrade. Since
1783 the stable 4.x branch point, one has generally been able to upgrade from
1784 anywhere in the most recent stable branch to head / current (or even the
1785 last couple of stable branches). See the top of this file when there's
1788 When upgrading a live system, having a root shell around before
1789 installing anything can help undo problems. Not having a root shell
1790 around can lead to problems if pam has changed too much from your
1791 starting point to allow continued authentication after the upgrade.
1793 This file should be read as a log of events. When a later event changes
1794 information of a prior event, the prior event should not be deleted.
1795 Instead, a pointer to the entry with the new information should be
1796 placed in the old entry. Readers of this file should also sanity check
1797 older entries before relying on them blindly. Authors of new entries
1798 should write them with this in mind.
1802 When upgrading the boot ZFS pool to a new version, always follow
1805 1.) recompile and reinstall the ZFS boot loader and boot block
1806 (this is part of "make buildworld" and "make installworld")
1808 2.) update the ZFS boot block on your boot drive
1810 The following example updates the ZFS boot block on the first
1811 partition (freebsd-boot) of a GPT partitioned drive ada0:
1812 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1814 Non-boot pools do not need these updates.
1818 If you are updating from a prior version of FreeBSD (even one just
1819 a few days old), you should follow this procedure. It is the most
1820 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1822 make kernel-toolchain
1823 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1824 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1826 To test a kernel once
1827 ---------------------
1828 If you just want to boot a kernel once (because you are not sure
1829 if it works, or if you want to boot a known bad kernel to provide
1830 debugging information) run
1831 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1832 nextboot -k testkernel
1834 To rebuild everything and install it on the current system.
1835 -----------------------------------------------------------
1836 # Note: sometimes if you are running current you gotta do more than
1837 # is listed here if you are upgrading from a really old current.
1839 <make sure you have good level 0 dumps>
1841 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1842 make installkernel KERNCONF=YOUR_KERNEL_HERE
1844 <reboot in single user> [3]
1851 To cross-install current onto a separate partition
1852 --------------------------------------------------
1853 # In this approach we use a separate partition to hold
1854 # current's root, 'usr', and 'var' directories. A partition
1855 # holding "/", "/usr" and "/var" should be about 2GB in
1858 <make sure you have good level 0 dumps>
1861 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1862 <maybe newfs current's root partition>
1863 <mount current's root partition on directory ${CURRENT_ROOT}>
1864 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1865 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1866 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1867 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1868 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1869 <reboot into current>
1870 <do a "native" rebuild/install as described in the previous section>
1871 <maybe install compatibility libraries from ports/misc/compat*>
1875 To upgrade in-place from stable to current
1876 ----------------------------------------------
1877 <make sure you have good level 0 dumps>
1879 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1880 make installkernel KERNCONF=YOUR_KERNEL_HERE
1882 <reboot in single user> [3]
1889 Make sure that you've read the UPDATING file to understand the
1890 tweaks to various things you need. At this point in the life
1891 cycle of current, things change often and you are on your own
1892 to cope. The defaults can also change, so please read ALL of
1893 the UPDATING entries.
1895 Also, if you are tracking -current, you must be subscribed to
1896 freebsd-current@freebsd.org. Make sure that before you update
1897 your sources that you have read and understood all the recent
1898 messages there. If in doubt, please track -stable which has
1899 much fewer pitfalls.
1901 [1] If you have third party modules, such as vmware, you
1902 should disable them at this point so they don't crash your
1905 [3] From the bootblocks, boot -s, and then do
1910 adjkerntz -i # if CMOS is wall time
1911 Also, when doing a major release upgrade, it is required that
1912 you boot into single user mode to do the installworld.
1914 [4] Note: This step is non-optional. Failure to do this step
1915 can result in a significant reduction in the functionality of the
1916 system. Attempting to do it by hand is not recommended and those
1917 that pursue this avenue should read this file carefully, as well
1918 as the archives of freebsd-current and freebsd-hackers mailing lists
1919 for potential gotchas. The -U option is also useful to consider.
1920 See mergemaster(8) for more information.
1922 [5] Usually this step is a no-op. However, from time to time
1923 you may need to do this if you get unknown user in the following
1924 step. It never hurts to do it all the time. You may need to
1925 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1926 install) after the buildworld before this step if you last updated
1927 from current before 20130425 or from -stable before 20130430.
1929 [6] This only deletes old files and directories. Old libraries
1930 can be deleted by "make delete-old-libs", but you have to make
1931 sure that no program is using those libraries anymore.
1933 [8] The new kernel must be able to run existing binaries used by
1934 an installworld. When upgrading across major versions, the new
1935 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1936 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1937 binaries). Failure to do so may leave you with a system that is
1938 hard to boot to recover. A GENERIC kernel will include suitable
1939 compatibility options to run binaries from older branches.
1941 Make sure that you merge any new devices from GENERIC since the
1942 last time you updated your kernel config file.
1944 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1945 "?=" instead of the "=" assignment operator, so that buildworld can
1946 override the CPUTYPE if it needs to.
1948 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1949 not on the command line, or in /etc/make.conf. buildworld will
1950 warn if it is improperly defined.
1953 This file contains a list, in reverse chronological order, of major
1954 breakages in tracking -current. It is not guaranteed to be a complete
1955 list of such breakages, and only contains entries since September 23, 2011.
1956 If you need to see UPDATING entries from before that date, you will need
1957 to fetch an UPDATING file from an older FreeBSD release.
1959 Copyright information:
1961 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1963 Redistribution, publication, translation and use, with or without
1964 modification, in full or in part, in any form or format of this
1965 document are permitted without further permission from the author.
1967 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1968 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1969 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1970 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1971 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1972 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1973 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1974 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1975 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1976 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1977 POSSIBILITY OF SUCH DAMAGE.
1979 Contact Warner Losh if you have any questions about your use of