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 updating system packages
15 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
16 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
17 the tip of head, and then rebuild without this option. The bootstrap process
18 from older version of current across the gcc/clang cutover is a bit fragile.
21 Commit e9959506d2cc changed the internal KAPI between the
22 nscl.ko and nfscommon.ko modules, so they both need to be
26 Commit 0a1fdb867c72 changed the internal KAPI between
27 the krpc and NFS. As such, the krpc, nfscommon and
28 nfscl modules must all be rebuilt from sources.
29 Without this patch, NFSv4.1 mounts should not
30 be done with the nfscbd(8) daemon running, to avoid
31 needing a working back channel for server->client RPCs.
34 The make.conf(5) MALLOC_PRODUCTION variable, used for disabling and
35 enabling assertions and statistics gathering in malloc(3), has been
36 migrated to a src.conf(5) WITH/WITHOUT_MALLOC_PRODUCTION option.
38 On stable branches, WITH_MALLOC_PRODUCTION is set by default, which
39 means that malloc(3) has assertions and statistics gathering disabled,
40 for improved performance.
42 For backwards compatibility, the make.conf(5) MALLOC_PRODUCTION is still
43 honored, but it is now deprecated and undocumented.
46 The resume code now notifies devd with the 'kernel' system
47 rather than the old 'kern' subsystem to be consistent with
48 other use. The old notification will be created as well, but
49 will be removed prior to FreeBSD 14.0.
52 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
53 been upgraded to 10.0.1. Please see the 20141231 entry below for
54 information about prerequisites and upgrading, if you are not already
55 using clang 3.5.0 or higher.
58 read(2) of a directory fd is now rejected by default. root may
59 re-enable it for the entire system with the
60 security.bsd.allow_read_dir sysctl(8) MIB.
62 It may be advised to setup aliases for grep to default to `-d skip` if
63 commonly non-recursively grepping a list that includes directories and
64 the potential for the resulting stderr output is not tolerable. Example
65 aliases are now installed, commented out, in /root/.cshrc.
68 Upstream DTS from Linux 5.6 was merged and they now have the SID
69 and THS (Secure ID controller and THermal Sensor) node present.
70 The DTB overlays have now been removed from the tree for the H3/H5 and
71 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
72 deal with upstream DTS. If you are using those overlays you need to
73 remove them from loader.conf and update the DTBs on the FAT partition.
76 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
77 been upgraded to 10.0.0. Please see the 20141231 entry below for
78 information about prerequisites and upgrading, if you are not already
79 using clang 3.5.0 or higher.
82 The root certificates of the Mozilla CA Certificate Store have been
83 imported into the base system and can be managed with the certctl(8)
84 utility. If you have installed the security/ca_root_nss port or package
85 with the ETCSYMLINK option (the default), be advised that there may be
86 differences between those included in the port and those included in
87 base due to differences in nss branch used as well as general update
88 frequency. Note also that certctl(8) cannot manage certs in the
89 format used by the security/ca_root_nss port.
92 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
93 been upgraded to 9.0.1. Please see the 20141231 entry below for
94 information about prerequisites and upgrading, if you are not already
95 using clang 3.5.0 or higher.
98 The nctgpio and wbwd drivers have been moved to the superio bus.
99 If you have one of these drivers in a kernel configuration, then
100 you should add device superio to it. If you use one of these drivers
101 as a module and you compile a custom set of modules, then you should
102 add superio to the set.
105 The tap(4) driver has been folded into tun(4), and the module has been
106 renamed to tuntap. You should update any kld_list="if_tap" or
107 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
108 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
109 module instead, and "device tap" or "device tun" entries in kernel
110 config files to select the tuntap device instead.
113 ntpd no longer by default locks its pages in memory, allowing them
114 to be paged out by the kernel. Use rlimit memlock to restore
115 historic BSD behaviour. For example, add "rlimit memlock 32"
116 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
119 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
120 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
121 been removed from mount_fusefs(8). You can safely remove them from
122 your scripts, because they had no effect.
124 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
125 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
126 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
127 sysctls have been removed. If you felt the need to set any of them to
128 a non-default value, please tell asomers@FreeBSD.org why.
131 The fuse(4) module has been renamed to fusefs(4) for consistency with
132 other filesystems. You should update any kld_load="fuse" entries in
133 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
134 "options FUSE" enties in kernel config files.
137 Default permissions on the /var/account/acct file (and copies of it
138 rotated by periodic daily scripts) are changed from 0644 to 0640
139 because the file contains sensitive information that should not be
140 world-readable. If the /var/account directory must be created by
141 rc.d/accounting, the mode used is now 0750. Admins who use the
142 accounting feature are encouraged to change the mode of an existing
143 /var/account directory to 0750 or 0700.
146 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
147 been upgraded to 8.0.1. Please see the 20141231 entry below for
148 information about prerequisites and upgrading, if you are not already
149 using clang 3.5.0 or higher.
152 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
153 functionality needed for the RETPOLINE option should work properly
154 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
157 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
158 8.0.0. Please see the 20141231 entry below for information about
159 prerequisites and upgrading, if you are not already using clang 3.5.0
163 The RETPOLINE option produces non-functional ifunc-using binaries
164 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
165 Once Clang 8 is merged it may be enabled again.
168 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
169 7.0.1. Please see the 20141231 entry below for information about
170 prerequisites and upgrading, if you are not already using clang 3.5.0
174 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
175 compiled into your custom kernel, add 'device xz' statement to the
179 Iflib is no longer unconditionally compiled into the kernel. Drivers
180 using iflib and statically compiled into the kernel, now require
181 the 'device iflib' config option. For the same drivers loaded as
182 modules on kernels not having 'device iflib', the iflib.ko module
183 is loaded automatically.
186 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
187 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
188 servers that have vfs.nfsd.nfs_privport set will only allow mounts
189 from clients using a reserved port#. Since both the FreeBSD and Linux
190 NFSv4 clients use reserved port#s by default, this should not affect
194 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
195 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
196 it produces broken binaries when ifuncs are in use. Users needing
197 GNU ld should install the binutils port or package.
200 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
201 has been converted to a port (misc/ctm) and will be removed from
202 FreeBSD-13. A depreciation warning will be printed to stderr by
203 the ctm command, but the functionality will remain in base for all
207 The stable/12 branch has been created in subversion from head
211 Ports for the DRM modules have been simplified. Now, amd64 users should
212 just install the drm-kmod port. All others should install
215 Graphics hardware that's newer than about 2010 usually works with
216 drm-kmod. For hardware older than 2013, however, some users will need
217 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
218 than 2008 usually only works in drm-legacy-kmod. The graphics team can
219 only commit to hardware made since 2013 due to the complexity of the
220 market and difficulty to test all the older cards effectively. If you
221 have hardware supported by drm-kmod, you are strongly encouraged to use
222 that as you will get better support.
224 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
225 elsewhere, the drm and drm2 modules will be eliminated from the src base
226 soon (with a limited exception for arm). Please update to the package asap
227 and report any issues to x11@freebsd.org.
229 Generally, anybody using the drm*-kmod packages should add
230 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
231 cross-threading surprises, especially with automatic driver
232 loading from X11 startup. These will become the defaults in 13-current
236 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
237 custom kernel and module loading configuration files must be updated
238 accordingly. Moreover, interfaces previous presented as ixlvN to the
239 system are now exposed as iavfN and network configuration files must
240 be adjusted as necessary.
243 OpenSSL has been updated to version 1.1.1. This update included
244 additional various API changes througout the base system. It is
245 important to rebuild third-party software after upgrading. The value
246 of __FreeBSD_version has been bumped accordingly.
249 The legacy DRM modules and drivers have now been added to the loader's
250 module blacklist, in favor of loading them with kld_list in rc.conf(5).
251 The module blacklist may be overridden with the loader.conf(5)
252 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
256 The cam(4) based nda(4) driver will be used over nvd(4) by default on
257 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
258 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
259 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
263 Reproducible build mode is now on by default, in preparation for
264 FreeBSD 12.0. This eliminates build metadata such as the user,
265 host, and time from the kernel (and uname), unless the working tree
266 corresponds to a modified checkout from a version control system.
267 The previous behavior can be obtained by setting the /etc/src.conf
268 knob WITHOUT_REPRODUCIBLE_BUILD.
271 The Yarrow CSPRNG has been removed from the kernel as it has not been
272 supported by its designers since at least 2003. Fortuna has been the
273 default since FreeBSD-11.
276 devctl freeze/thaw have gone into the tree, the rc scripts have been
277 updated to use them and devmatch has been changed. You should update
278 kernel, userland and rc scripts all at the same time.
281 The default interpreter has been switched from 4th to Lua.
282 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
283 interpreter. If you have custom FORTH code you will need to set
284 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
285 src.conf for the build. This will create default hard links between
286 loader and loader_4th instead of loader and loader_lua, the new default.
287 If you are using UEFI it will create the proper hard link to loader.efi.
289 bhyve uses userboot.so. It remains 4th-only until some issues are solved
290 regarding coexisting with multiple versions of FreeBSD are resolved.
293 ls(1) now respects the COLORTERM environment variable used in other
294 systems and software to indicate that a colored terminal is both
295 supported and desired. If ls(1) is suddenly emitting colors, they may
296 be disabled again by either removing the unwanted COLORTERM from your
297 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
298 may not be observed in a future release.
301 The default pager for most commands has been changed to "less". To
302 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
306 The jedec_ts(4) driver has been removed. A superset of its functionality
307 is available in the jedec_dimm(4) driver, and the manpage for that
308 driver includes migration instructions. If you have "device jedec_ts"
309 in your kernel configuration file, it must be removed.
312 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
313 This should have no effect if the kernel is booted via BIOS/legacy boot.
314 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
315 has a buggy firmware that prevents a successful boot due to use of
319 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
320 support has been removed from the tree. These ports were
321 obsolete and/or known to be broken for many years.
324 loader.efi has been augmented to participate more fully in the
325 UEFI boot manager protocol. loader.efi will now look at the
326 BootXXXX environment variable to determine if a specific kernel
327 or root partition was specified. XXXX is derived from BootCurrent.
328 efibootmgr(8) manages these standard UEFI variables.
331 zfsloader's functionality has now been folded into loader.
332 zfsloader is no longer necessary once you've updated your
333 boot blocks. For a transition period, we will install a
334 hardlink for zfsloader to loader to allow a smooth transition
335 until the boot blocks can be updated (hard link because old
336 zfs boot blocks don't understand symlinks).
339 ARM64 now have efifb support, if you want to have serial console
340 on your arm64 board when an screen is connected and the bootloader
341 setup a frambuffer for us to use, just add :
345 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
346 an screen connected as the firmware will setup a framebuffer are that
347 u-boot will expose as an EFI framebuffer.
350 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
351 or take steps to update /etc/passwd before doing installworld on
352 existing systems. Do not skip the "mergemaster -Fp" step before
353 installworld, as described in the update procedures near the bottom
354 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
355 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
356 the ntp config file contain options that change file/dir locations.
357 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
358 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
359 taking steps to ensure that all required files/dirs are accessible
363 Big endian arm support has been removed.
366 The static environment setup in kernel configs is no longer mutually
367 exclusive with the loader(8) environment by default. In order to
368 restore the previous default behavior of disabling the loader(8)
369 environment if a static environment is present, you must specify
370 loader_env.disabled=1 in the static environment.
373 The ABI of syscalls used by management tools like sockstat and
374 netstat has been broken to allow 32-bit binaries to work on
375 64-bit kernels without modification. These programs will need
376 to match the kernel in order to function. External programs may
377 require minor modifications to accommodate a change of type in
378 structures from pointers to 64-bit virtual addresses.
381 On i386 and amd64 atomics are now inlined. Out of tree modules using
382 atomics will need to be rebuilt.
385 The '%I' format in the kern.corefile sysctl limits the number of
386 core files that a process can generate to the number stored in the
387 debug.ncores sysctl. The '%I' format is replaced by the single digit
388 index. Previously, if all indexes were taken the kernel would overwrite
389 only a core file with the highest index in a filename.
390 Currently the system will create a new core file if there is a free
391 index or if all slots are taken it will overwrite the oldest one.
394 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
395 6.0.1. Please see the 20141231 entry below for information about
396 prerequisites and upgrading, if you are not already using clang 3.5.0
400 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
401 needed to be changed to work with it. This change was made with r335763
402 and requires a mergemaster / etcupdate / etc to update the installed file.
405 r334930 changed the interface between the NFS modules, so they all
406 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
409 As of r334391 lld is the default amd64 system linker; it is installed
410 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
414 The kernel / userland interface for devinfo changed, so you'll
415 need a new kernel and userland as a pair for it to work (rebuilding
416 lib/libdevinfo is all that's required). devinfo and devmatch will
417 not work, but everything else will when there's a mismatch.
420 The on-disk format for hwpmc callchain records has changed to include
421 threadid corresponding to a given record. This changes the field offsets
422 and thus requires that libpmcstat be rebuilt before using a kernel
426 The vxge(4) driver has been removed. This driver was introduced into
427 HEAD one week before the Exar left the Ethernet market and is not
428 known to be used. If you have device vxge in your kernel config file
432 The amd64 kernel now requires a ld that supports ifunc to produce a
433 working kernel, either lld or a newer binutils. lld is built by default
434 on amd64, and the 'buildkernel' target uses it automatically. However,
435 it is not the default linker, so building the kernel the traditional
436 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
437 binutils port/package). lld will soon be default, and this requirement
440 NOTE: As of r334391 lld is the default system linker on amd64, and no
441 workaround is necessary.
444 The nxge(4) driver has been removed. This driver was for PCI-X 10g
445 cards made by s2io/Neterion. The company was aquired by Exar and
446 no longer sells or supports Ethernet products. If you have device
447 nxge in your kernel config file it must be removed.
450 The tz database (tzdb) has been updated to 2018e. This version more
451 correctly models time stamps in time zones with negative DST such as
452 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
453 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
454 time zone abbreviations and the tm_isdst flag.
457 The ixgb(4) driver has been removed. This driver was for an early and
458 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
459 quickly shifted to the long lived ixgbe family. If you have device
460 ixgb in your kernel config file it must be removed.
463 The lmc(4) driver has been removed. This was a WAN interface
464 card that was already reportedly rare in 2003, and had an ambiguous
465 license. If you have device lmc in your kernel config file it must
469 Support for Arcnet networks has been removed. If you have device
470 arcnet or device cm in your kernel config file they must be
474 Support for FDDI networks has been removed. If you have device
475 fddi or device fpa in your kernel config file they must be
479 In addition to supporting RFC 3164 formatted messages, the
480 syslogd(8) service is now capable of parsing RFC 5424 formatted
481 log messages. The main benefit of using RFC 5424 is that clients
482 may now send log messages with timestamps containing year numbers,
483 microseconds and time zone offsets.
485 Similarly, the syslog(3) C library function has been altered to
486 send RFC 5424 formatted messages to the local system logging
487 daemon. On systems using syslogd(8), this change should have no
488 negative impact, as long as syslogd(8) and the C library are
489 updated at the same time. On systems using a different system
490 logging daemon, it may be necessary to make configuration
491 adjustments, depending on the software used.
493 When using syslog-ng, add the 'syslog-protocol' flag to local
494 input sources to enable parsing of RFC 5424 formatted messages:
497 unix-dgram("/var/run/log" flags(syslog-protocol));
500 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
501 of the 'imuxsock' module to let messages be processed by the
502 regular RFC 3164/5424 parsing pipeline:
504 module(load="imuxsock" SysSock.UseSpecialParser="off")
506 Do note that these changes only affect communication between local
507 applications and syslogd(8). The format that syslogd(8) uses to
508 store messages on disk or forward messages to other systems
509 remains unchanged. syslogd(8) still uses RFC 3164 for these
510 purposes. Options to customize this behaviour will be added in the
511 future. Utilities that process log files stored in /var/log are
512 thus expected to continue to function as before.
514 __FreeBSD_version has been incremented to 1200061 to denote this
518 Support for token ring networks has been removed. If you
519 have "device token" in your kernel config you should remove
520 it. No device drivers supported token ring.
523 makefs was modified to be able to tag ISO9660 El Torito boot catalog
524 entries as EFI instead of overloading the i386 tag as done previously.
525 The amd64 mkisoimages.sh script used to build amd64 ISO images for
526 release was updated to use this. This may mean that makefs must be
527 updated before "make cdrom" can be run in the release directory. This
528 should be as simple as:
530 $ cd $SRCDIR/usr.sbin/makefs
531 $ make depend all install
534 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
535 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
536 Co-existance for the transition period will come shortly. Booting is a
537 complex environment and test coverage for Lua-enabled loaders has been
538 thin, so it would be prudent to assume it might not work and make
539 provisions for backup boot methods.
542 devmatch functionality has been turned on in devd. It will automatically
543 load drivers for unattached devices. This may cause unexpected drivers to
544 be loaded. Please report any problems to current@ and imp@freebsd.org.
547 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
548 6.0.0. Please see the 20141231 entry below for information about
549 prerequisites and upgrading, if you are not already using clang 3.5.0
553 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
554 This means it is used to link the kernel and userland libraries and
555 executables, but is not yet installed as /usr/bin/ld by default.
557 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
558 WITHOUT_LLD_BOOTSTRAP=yes
561 On i386, pmtimer has been removed. Its functionality has been folded
562 into apm. It was a no-op on ACPI in current for a while now (but was still
563 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
564 from kernel config files.
567 The use of RSS hash from the network card aka flowid has been
568 disabled by default for lagg(4) as it's currently incompatible with
569 the lacp and loadbalance protocols.
571 This can be re-enabled by setting the following in loader.conf:
572 net.link.lagg.default_use_flowid="1"
575 The SW_WATCHDOG option is no longer necessary to enable the
576 hardclock-based software watchdog if no hardware watchdog is
577 configured. As before, SW_WATCHDOG will cause the software
578 watchdog to be enabled even if a hardware watchdog is configured.
581 r326887 fixes the issue described in the 20171214 UPDATING entry.
582 r326888 flips the switch back to building GELI support always.
585 r362593 broke ZFS + GELI support for reasons unknown. However,
586 it also broke ZFS support generally, so GELI has been turned off
587 by default as the lesser evil in r326857. If you boot off ZFS and/or
588 GELI, it might not be a good time to update.
591 PowerPC users must update loader(8) by rebuilding world before
592 installing a new kernel, as the protocol connecting them has
593 changed. Without the update, loader metadata will not be passed
594 successfully to the kernel and users will have to enter their
595 root partition at the kernel mountroot prompt to continue booting.
596 Newer versions of loader can boot old kernels without issue.
599 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
600 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
601 to WITH/OUT_LOADER_GELI.
604 The naive and non-compliant support of posix_fallocate(2) in ZFS
605 has been removed as of r325320. The system call now returns EINVAL
606 when used on a ZFS file. Although the new behavior complies with the
607 standard, some consumers are not prepared to cope with it.
608 One known victim is lld prior to r325420.
611 Building in a FreeBSD src checkout will automatically create object
612 directories now rather than store files in the current directory if
613 'make obj' was not ran. Calling 'make obj' is no longer necessary.
614 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
615 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
619 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
620 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
621 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
622 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
623 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
624 The UNIFIED_OBJDIR option is a transitional feature that will be
625 removed for 12.0 release; please migrate to the new format for any
626 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
627 than hardcoding paths.
630 The native-xtools target no longer installs the files by default to the
631 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
632 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
635 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
636 options are changing from controlling the build if defined / undefined
637 to controlling the build with explicit 'yes' or 'no' values. They will
638 shift to WITH/WITHOUT options to match other options in the system.
641 libstand has turned into a private library for sys/boot use only.
642 It is no longer supported as a public interface outside of sys/boot.
645 The arm port has split armv6 into armv6 and armv7. armv7 is now
646 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
647 and are running a kernel from before r324363, you will need to add
648 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
651 When building multiple kernels using KERNCONF, non-existent KERNCONF
652 files will produce an error and buildkernel will fail. Previously
653 missing KERNCONF files silently failed giving no indication as to
654 why, only to subsequently discover during installkernel that the
655 desired kernel was never built in the first place.
658 The default serial number format for CTL LUNs has changed. This will
659 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
660 or iSCSI clients care about their LUNs' serial numbers. Users who
661 require serial number stability should hardcode serial numbers in
665 For 32-bit arm compiled for hard-float support, soft-floating point
666 binaries now always get their shared libraries from
667 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
668 /usr/libsoft also existed). Only users with a hard-float ld.so, but
669 soft-float everything else should be affected.
672 The geli password typed at boot is now hidden. To restore the previous
673 behavior, see geli(8) for configuration options.
676 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
677 sysctl values. Minor nit, but requires a rebuild of both world/kernel
681 "make check" behavior (made in ^/head@r295380) has been changed to
682 execute from a limited sandbox, as opposed to executing from
686 - The "beforecheck" and "aftercheck" targets are now specified.
687 - ${CHECKDIR} (added in commit noted above) has been removed.
688 - Legacy behavior can be enabled by setting
689 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
691 If the limited sandbox mode is enabled, "make check" will execute
692 "make distribution", then install, execute the tests, and clean up the
693 sandbox if successful.
695 The "make distribution" and "make install" targets are typically run as
696 root to set appropriate permissions and ownership at installation time.
697 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
698 environment if executing "make check" with limited sandbox mode using
699 an unprivileged user.
702 Since the switch to GPT disk labels, fsck for UFS/FFS has been
703 unable to automatically find alternate superblocks. As of r322297,
704 the information needed to find alternate superblocks has been
705 moved to the end of the area reserved for the boot block.
706 Filesystems created with a newfs of this vintage or later
707 will create the recovery information. If you have a filesystem
708 created prior to this change and wish to have a recovery block
709 created for your filesystem, you can do so by running fsck in
710 foreground mode (i.e., do not use the -p or -y options). As it
711 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
712 to which you should answer yes.
715 As of r321665, an NFSv4 server configuration that services
716 Kerberos mounts or clients that do not support the uid/gid in
717 owner/owner_group string capability, must explicitly enable
718 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
719 machine's /etc/rc.conf file.
722 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
723 Please see the 20141231 entry below for information about prerequisites
724 and upgrading, if you are not already using clang 3.5.0 or higher.
727 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
728 r-commands (rlogin, rsh, etc.) to be built with the base system.
731 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
732 a very major ABI incompatible change, so users of FreeBSD/powerpc must
733 be careful when performing source upgrades. It is best to run
734 'make installworld' from an alternate root system, either a live
735 CD/memory stick, or a temporary root partition. Additionally, all ports
736 must be recompiled. powerpc64 is largely unaffected, except in the case
737 of 32-bit compatibility. All 32-bit binaries will be affected.
740 Forward compatibility for the "ino64" project have been committed. This
741 will allow most new binaries to run on older kernels in a limited
742 fashion. This prevents many of the common foot-shooting actions in the
743 upgrade as well as the limited ability to roll back the kernel across
744 the ino64 upgrade. Complicated use cases may not work properly, though
745 enough simpler ones work to allow recovery in most situations.
748 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
749 if you require the GPL compiler.
752 The internal ABI used for communication between the NFS kernel modules
753 was changed by r320085, so __FreeBSD_version was bumped to
754 ensure all the NFS related modules are updated together.
757 The ABI of struct event was changed by extending the data
758 member to 64bit and adding ext fields. For upgrade, same
759 precautions as for the entry 20170523 "ino64" must be
763 The GNU roff toolchain has been removed from base. To render manpages
764 which are not supported by mandoc(1), man(1) can fallback on GNU roff
765 from ports (and recommends to install it).
766 To render roff(7) documents, consider using GNU roff from ports or the
767 heirloom doctools roff toolchain from ports via pkg install groff or
768 via pkg install heirloom-doctools.
771 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
772 smaller runtime footprint builds. This is useful for embedded systems
773 which only require one chipset support.
775 If you load it as a module, make sure this is in /boot/loader.conf:
779 This will load the HAL, all chip/RF backends and if_ath_pci.
780 If you have if_ath_pci in /boot/loader.conf, ensure it is after
781 if_ath or it will not load any HAL chipset support.
783 If you want to selectively load things (eg on ye cheape ARM/MIPS
784 platforms where RAM is at a premium) you should:
787 * load the chip modules in question
788 * load ath_rate, ath_dfs
790 * load if_ath_pci and/or if_ath_ahb depending upon your particular
791 bus bind type - this is where probe/attach is done.
793 For further comments/feedback, poke adrian@ .
796 The "ino64" 64-bit inode project has been committed, which extends
797 a number of types to 64 bits. Upgrading in place requires care and
798 adherence to the documented upgrade procedure.
800 If using a custom kernel configuration ensure that the
801 COMPAT_FREEBSD11 option is included (as during the upgrade the
802 system will be running the ino64 kernel with the existing world).
804 For the safest in-place upgrade begin by removing previous build
805 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
806 full procedure documented below under the heading "To rebuild
807 everything and install it on the current system." Specifically,
808 a reboot is required after installing the new kernel before
812 The NATM framework including the en(4), fatm(4), hatm(4), and
813 patm(4) devices has been removed. Consumers should plan a
814 migration before the end-of-life date for FreeBSD 11.
817 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
818 diff has not been implemented, if those are needed a newer version of
819 GNU diff is available via the diffutils package under the gdiff name.
822 As of r316810 for ipfilter, keep frags is no longer assumed when
823 keep state is specified in a rule. r316810 aligns ipfilter with
824 documentation in man pages separating keep frags from keep state.
825 This allows keep state to be specified without forcing keep frags
826 and allows keep frags to be specified independently of keep state.
827 To maintain previous behaviour, also specify keep frags with
828 keep state (as documented in ipf.conf.5).
831 arm64 builds now use the base system LLD 4.0.0 linker by default,
832 instead of requiring that the aarch64-binutils port or package be
833 installed. To continue using aarch64-binutils, set
834 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
837 The UDP optimization in entry 20160818 that added the sysctl
838 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
839 packets will no longer be treated as L3 broadcast packets.
842 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
843 use any explicitly assigned loopback address available in the jail
844 instead of using the first assigned address of the jail.
847 The ctl.ko module no longer implements the iSCSI target frontend:
848 cfiscsi.ko does instead.
850 If building cfiscsi.ko as a kernel module, the module can be loaded
851 via one of the following methods:
852 - `cfiscsi_load="YES"` in loader.conf(5).
853 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
854 - ctladm(8)/ctld(8), when compiled with iSCSI support
855 (`WITH_ISCSI=yes` in src.conf(5))
857 Please see cfiscsi(4) for more details.
860 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
861 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
862 same source (previously, the dependency of mmcsd.ko on mmc.ko was
863 missing, but mmcsd.ko now will refuse to load if it is incompatible
867 The syntax of ipfw(8) named states was changed to avoid ambiguity.
868 If you have used named states in the firewall rules, you need to modify
869 them after installworld and before rebooting. Now named states must
870 be prefixed with colon.
873 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
874 removed as the userland we provide cannot use them. The KMS version
875 (sys/dev/drm2) supports the same hardware.
878 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
879 Please see the 20141231 entry below for information about prerequisites
880 and upgrading, if you are not already using clang 3.5.0 or higher.
883 The code that provides support for ZFS .zfs/ directory functionality
884 has been reimplemented. It's not possible now to create a snapshot
885 by mkdir under .zfs/snapshot/. That should be the only user visible
889 EISA bus support has been removed. The WITH_EISA option is no longer
893 MCA bus support has been removed.
896 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
897 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
900 The EM_MULTIQUEUE kernel configuration option is deprecated now that
901 the em(4) driver conforms to iflib specifications.
904 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
905 IFLIB. If you have a custom kernel configuration that excludes em(4)
906 but you use igb(4), you need to re-add em(4) to your custom configuration.
909 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
910 Please see the 20141231 entry below for information about prerequisites
911 and upgrading, if you are not already using clang 3.5.0 or higher.
914 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
915 Please see the 20141231 entry below for information about prerequisites
916 and upgrading, if you are not already using clang 3.5.0 or higher.
919 The layout of the pmap structure has changed for powerpc to put the pmap
920 statistics at the front for all CPU variations. libkvm(3) and all tools
921 that link against it need to be recompiled.
924 isl(4) and cyapa(4) drivers now require a new driver,
925 chromebook_platform(4), to work properly on Chromebook-class hardware.
926 On other types of hardware the drivers may need to be configured using
927 device hints. Please see the corresponding manual pages for details.
930 The urtwn(4) driver was merged into rtwn(4) and now consists of
931 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
933 Also, firmware for RTL8188CE was renamed due to possible name
934 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
937 GNU rcs has been removed from base. It is available as packages:
938 - rcs: Latest GPLv3 GNU rcs version.
939 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
943 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
944 modules now requires that the kernel configuration contain the
945 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
948 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
949 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
952 Relocatable object files with the extension of .So have been renamed
953 to use an extension of .pico instead. The purpose of this change is
954 to avoid a name clash with shared libraries on case-insensitive file
955 systems. On those file systems, foo.So is the same file as foo.so.
958 GNU rcs has been turned off by default. It can (temporarily) be built
959 again by adding WITH_RCS knob in src.conf.
960 Otherwise, GNU rcs is available from packages:
961 - rcs: Latest GPLv3 GNU rcs version.
962 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
965 The backup_uses_rcs functionality has been removed from rc.subr.
968 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
969 two separate components, QUEUE_MACRO_DEBUG_TRACE and
970 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
971 QUEUE_MACRO_DEBUG behavior.
974 r304787 changed some ioctl interfaces between the iSCSI userspace
975 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
976 rebuilt to work with new kernels. __FreeBSD_version has been bumped
980 The UDP receive code has been updated to only treat incoming UDP
981 packets that were addressed to an L2 broadcast address as L3
982 broadcast packets. It is not expected that this will affect any
983 standards-conforming UDP application. The new behaviour can be
984 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
988 Remove the openbsd_poll system call.
989 __FreeBSD_version has been bumped because of this.
992 The stable/11 branch has been created from head@r302406.
995 The libc stub for the pipe(2) system call has been replaced with
996 a wrapper that calls the pipe2(2) system call and the pipe(2)
997 system call is now only implemented by the kernels that include
998 "options COMPAT_FREEBSD10" in their config file (this is the
999 default). Users should ensure that this option is enabled in
1000 their kernel or upgrade userspace to r302092 before upgrading their
1004 CAM will now strip leading spaces from SCSI disks' serial numbers.
1005 This will affect users who create UFS filesystems on SCSI disks using
1006 those disk's diskid device nodes. For example, if /etc/fstab
1007 previously contained a line like
1008 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1009 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1010 transforms like gmirror may also be affected. ZFS users should
1014 The bitstring(3) API has been updated with new functionality and
1015 improved performance. But it is binary-incompatible with the old API.
1016 Objects built with the new headers may not be linked against objects
1017 built with the old headers.
1020 The brk and sbrk functions have been removed from libc on arm64.
1021 Binutils from ports has been updated to not link to these
1022 functions and should be updated to the latest version before
1023 installing a new libc.
1026 The armv6 port now defaults to hard float ABI. Limited support
1027 for running both hardfloat and soft float on the same system
1028 is available using the libraries installed with -DWITH_LIBSOFT.
1029 This has only been tested as an upgrade path for installworld
1030 and packages may fail or need manual intervention to run. New
1031 packages will be needed.
1033 To update an existing self-hosted armv6hf system, you must add
1034 TARGET_ARCH=armv6 on the make command line for both the build
1035 and the install steps.
1038 Kernel modules compiled outside of a kernel build now default to
1039 installing to /boot/modules instead of /boot/kernel. Many kernel
1040 modules built this way (such as those in ports) already overrode
1041 KMODDIR explicitly to install into /boot/modules. However,
1042 manually building and installing a module from /sys/modules will
1043 now install to /boot/modules instead of /boot/kernel.
1046 The CAM I/O scheduler has been committed to the kernel. There should be
1047 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1048 list of known rogues that claim support for this but actually corrupt
1049 data is believed to be complete, be on the lookout for data
1050 corruption. The known rogue list is believed to be complete:
1052 o Crucial MX100, M550 drives with MU01 firmware.
1053 o Micron M510 and M550 drives with MU01 firmware.
1054 o Micron M500 prior to MU07 firmware
1055 o Samsung 830, 840, and 850 all firmwares
1056 o FCCT M500 all firmwares
1058 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1059 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1060 updated firmware. Black listed drives will work correctly because these
1061 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1062 this list is the same as found in Linux, it's believed there are no
1063 other rogues in the market place. All other models from the above
1066 To be safe, if you are at all concerned, you can quirk each of your
1067 drives to prevent NCQ from being sent by setting:
1068 kern.cam.ada.X.quirks="0x2"
1069 in loader.conf. If the drive requires the 4k sector quirk, set the
1070 quirks entry to 0x3.
1073 The FAST_DEPEND build option has been removed and its functionality is
1074 now the one true way. The old mkdep(1) style of 'make depend' has
1075 been removed. See 20160311 for further details.
1078 Resource range types have grown from unsigned long to uintmax_t. All
1079 drivers, and anything using libdevinfo, need to be recompiled.
1082 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1083 builds. It no longer runs mkdep(1) during 'make depend', and the
1084 'make depend' stage can safely be skipped now as it is auto ran
1085 when building 'make all' and will generate all SRCS and DPSRCS before
1086 building anything else. Dependencies are gathered at compile time with
1087 -MF flags kept in separate .depend files per object file. Users should
1088 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1089 stale .depend files.
1092 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1093 kernel modules. Therefore, if you load any kernel modules at boot time,
1094 please install the boot loaders after you install the kernel, but before
1098 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1099 make installkernel KERNCONF=YOUR_KERNEL_HERE
1100 make -C sys/boot install
1101 <reboot in single user>
1103 Then follow the usual steps, described in the General Notes section,
1107 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1108 see the 20141231 entry below for information about prerequisites and
1109 upgrading, if you are not already using clang 3.5.0 or higher.
1112 The AIO subsystem is now a standard part of the kernel. The
1113 VFS_AIO kernel option and aio.ko kernel module have been removed.
1114 Due to stability concerns, asynchronous I/O requests are only
1115 permitted on sockets and raw disks by default. To enable
1116 asynchronous I/O requests on all file types, set the
1117 vfs.aio.enable_unsafe sysctl to a non-zero value.
1120 The ELF object manipulation tool objcopy is now provided by the
1121 ELF Tool Chain project rather than by GNU binutils. It should be a
1122 drop-in replacement, with the addition of arm64 support. The
1123 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1124 to obtain the GNU version if necessary.
1127 Building ZFS pools on top of zvols is prohibited by default. That
1128 feature has never worked safely; it's always been prone to deadlocks.
1129 Using a zvol as the backing store for a VM guest's virtual disk will
1130 still work, even if the guest is using ZFS. Legacy behavior can be
1131 restored by setting vfs.zfs.vol.recursive=1.
1134 The NONE and HPN patches has been removed from OpenSSH. They are
1135 still available in the security/openssh-portable port.
1138 With the addition of ypldap(8), a new _ypldap user is now required
1139 during installworld. "mergemaster -p" can be used to add the user
1140 prior to installworld, as documented in the handbook.
1143 The tftp loader (pxeboot) now uses the option root-path directive. As a
1144 consequence it no longer looks for a pxeboot.4th file on the tftp
1145 server. Instead it uses the regular /boot infrastructure as with the
1149 The code to start recording plug and play data into the modules has
1150 been committed. While the old tools will properly build a new kernel,
1151 a number of warnings about "unknown metadata record 4" will be produced
1152 for an older kldxref. To avoid such warnings, make sure to rebuild
1153 the kernel toolchain (or world). Make sure that you have r292078 or
1154 later when trying to build 292077 or later before rebuilding.
1157 Debug data files are now built by default with 'make buildworld' and
1158 installed with 'make installworld'. This facilitates debugging but
1159 requires more disk space both during the build and for the installed
1160 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1164 r291527 changed the internal interface between the nfsd.ko and
1165 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1166 __FreeBSD_version has been bumped because of this.
1169 Add support for unicode collation strings leads to a change of
1170 order of files listed by ls(1) for example. To get back to the old
1171 behaviour, set LC_COLLATE environment variable to "C".
1173 Databases administrators will need to reindex their databases given
1174 collation results will be different.
1176 Due to a bug in install(1) it is recommended to remove the ancient
1177 locales before running make installworld.
1179 rm -rf /usr/share/locale/*
1182 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1183 libcrypto.so.7 or libssl.so.7 must be recompiled.
1186 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1187 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1188 should be replaced with isp_2400 and isp_2500 modules respectively.
1191 The build previously allowed using 'make -n' to not recurse into
1192 sub-directories while showing what commands would be executed, and
1193 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1194 and 'make -N' will not.
1197 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1198 and etcupdate will now use this file. A custom sendmail.cf is now
1199 updated via this mechanism rather than via installworld. If you had
1200 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1201 want to remove the exclusion or change it to "always install".
1202 /etc/mail/sendmail.cf is now managed the same way regardless of
1203 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1204 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1207 Compatibility shims for legacy ATA device names have been removed.
1208 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1209 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1210 environment variables, /dev/ad* and /dev/ar* symbolic links.
1213 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1214 Please see the 20141231 entry below for information about prerequisites
1215 and upgrading, if you are not already using clang 3.5.0 or higher.
1218 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1219 and renamed from .symbols to .debug. This reduces the size requirements
1220 on the boot partition or file system and provides consistency with
1221 userland debug files.
1223 When using the supported kernel installation method the
1224 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1225 as is done with /boot/kernel.
1227 Developers wishing to maintain the historical behavior of installing
1228 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1231 The wireless drivers had undergone changes that remove the 'parent
1232 interface' from the ifconfig -l output. The rc.d network scripts
1233 used to check presence of a parent interface in the list, so old
1234 scripts would fail to start wireless networking. Thus, etcupdate(3)
1235 or mergemaster(8) run is required after kernel update, to update your
1236 rc.d scripts in /etc.
1239 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1240 These configurations are now automatically interpreted as
1241 'scrub fragment reassemble'.
1244 Kernel-loadable modules for the random(4) device are back. To use
1245 them, the kernel must have
1248 options RANDOM_LOADABLE
1250 kldload(8) can then be used to load random_fortuna.ko
1251 or random_yarrow.ko. Please note that due to the indirect
1252 function calls that the loadable modules need to provide,
1253 the build-in variants will be slightly more efficient.
1255 The random(4) kernel option RANDOM_DUMMY has been retired due to
1256 unpopularity. It was not all that useful anyway.
1259 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1260 Control over building the ELF Tool Chain tools is now provided by
1261 the WITHOUT_TOOLCHAIN knob.
1264 The polarity of Pulse Per Second (PPS) capture events with the
1265 uart(4) driver has been corrected. Prior to this change the PPS
1266 "assert" event corresponded to the trailing edge of a positive PPS
1267 pulse and the "clear" event was the leading edge of the next pulse.
1269 As the width of a PPS pulse in a typical GPS receiver is on the
1270 order of 1 millisecond, most users will not notice any significant
1271 difference with this change.
1273 Anyone who has compensated for the historical polarity reversal by
1274 configuring a negative offset equal to the pulse width will need to
1275 remove that workaround.
1278 The default group assigned to /dev/dri entries has been changed
1279 from 'wheel' to 'video' with the id of '44'. If you want to have
1280 access to the dri devices please add yourself to the video group
1283 # pw groupmod video -m $USER
1286 The menu.rc and loader.rc files will now be replaced during
1287 upgrades. Please migrate local changes to menu.rc.local and
1288 loader.rc.local instead.
1291 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1292 strings and strip have been removed. The src.conf(5) knob
1293 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1296 As ZFS requires more kernel stack pages than is the default on some
1297 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1298 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1300 Please consider using 'options KSTACK_PAGES=X' where X is greater
1301 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1304 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1305 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1306 default, i.e., they will not contain "::". For example, instead
1307 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1308 to have a more specific match, such as different map entries for
1309 IPv6:0:0 vs IPv6:0. This change requires that configuration
1310 data (including maps, files, classes, custom ruleset, etc.) must
1311 use the same format, so make certain such configuration data is
1312 upgrading. As a very simple check search for patterns like
1313 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1314 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1315 the cf option UseCompressedIPv6Addresses.
1318 The default kernel entropy-processing algorithm is now
1319 Fortuna, replacing Yarrow.
1321 Assuming you have 'device random' in your kernel config
1322 file, the configurations allow a kernel option to override
1323 this default. You may choose *ONE* of:
1325 options RANDOM_YARROW # Legacy /dev/random algorithm.
1326 options RANDOM_DUMMY # Blocking-only driver.
1328 If you have neither, you get Fortuna. For most people,
1329 read no further, Fortuna will give a /dev/random that works
1330 like it always used to, and the difference will be irrelevant.
1332 If you remove 'device random', you get *NO* kernel-processed
1333 entropy at all. This may be acceptable to folks building
1334 embedded systems, but has complications. Carry on reading,
1335 and it is assumed you know what you need.
1337 *PLEASE* read random(4) and random(9) if you are in the
1338 habit of tweaking kernel configs, and/or if you are a member
1339 of the embedded community, wanting specific and not-usual
1340 behaviour from your security subsystems.
1342 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1343 random', you will NOT have a functioning /dev/random, and
1344 many cryptographic features will not work, including SSH.
1345 You may also find strange behaviour from the random(3) set
1346 of library functions, in particular sranddev(3), srandomdev(3)
1347 and arc4random(3). The reason for this is that the KERN_ARND
1348 sysctl only returns entropy if it thinks it has some to
1349 share, and with RANDOM_DUMMY or no 'device random' this
1353 An additional fix for the issue described in the 20150614 sendmail
1354 entry below has been committed in revision 284717.
1357 FreeBSD's old make (fmake) has been removed from the system. It is
1358 available as the devel/fmake port or via pkg install fmake.
1361 The fix for the issue described in the 20150614 sendmail entry
1362 below has been committed in revision 284436. The work
1363 around described in that entry is no longer needed unless the
1364 default setting is overridden by a confDH_PARAMETERS configuration
1365 setting of '5' or pointing to a 512 bit DH parameter file.
1368 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1369 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1370 and devel/kyua to version 0.20+ and adjust any calling code to work
1371 with Kyuafile and kyua.
1374 The import of openssl to address the FreeBSD-SA-15:10.openssl
1375 security advisory includes a change which rejects handshakes
1376 with DH parameters below 768 bits. sendmail releases prior
1377 to 8.15.2 (not yet released), defaulted to a 512 bit
1378 DH parameter setting for client connections. To work around
1379 this interoperability, sendmail can be configured to use a
1380 2048 bit DH parameter by:
1382 1. Edit /etc/mail/`hostname`.mc
1383 2. If a setting for confDH_PARAMETERS does not exist or
1384 exists and is set to a string beginning with '5',
1385 replace it with '2'.
1386 3. If a setting for confDH_PARAMETERS exists and is set to
1387 a file path, create a new file with:
1388 openssl dhparam -out /path/to/file 2048
1389 4. Rebuild the .cf file:
1390 cd /etc/mail/; make; make install
1391 5. Restart sendmail:
1392 cd /etc/mail/; make restart
1394 A sendmail patch is coming, at which time this file will be
1398 Generation of legacy formatted entries have been disabled by default
1399 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1400 entries were converted to use the new format by default when the new,
1401 machine independent format have been added and supported since FreeBSD
1404 Please see the pwd_mkdb(8) manual page for further details.
1407 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1408 20141231 entry below for information about prerequisites and upgrading,
1409 if you are not already using 3.5.0 or higher.
1412 TI platform code switched to using vendor DTS files and this update
1413 may break existing systems running on Beaglebone, Beaglebone Black,
1416 - dtb files should be regenerated/reinstalled. Filenames are the
1417 same but content is different now
1418 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1419 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1420 addressing scheme is now pin 25 on /dev/gpioc3.
1421 - Pandaboard: /etc/ttys should be updated, serial console device is
1422 now /dev/ttyu2, not /dev/ttyu0
1425 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1426 If you need the GNU extension from groff soelim(1), install groff
1427 from package: pkg install groff, or via ports: textproc/groff.
1430 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1431 defined in symlink(7); previously symlinks were silently ignored.
1434 The const qualifier has been removed from iconv(3) to comply with
1435 POSIX. The ports tree is aware of this from r384038 onwards.
1438 Libraries specified by LIBADD in Makefiles must have a corresponding
1439 DPADD_<lib> variable to ensure correct dependencies. This is now
1440 enforced in src.libnames.mk.
1443 From legacy ata(4) driver was removed support for SATA controllers
1444 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1445 Kernel modules ataahci and ataadaptec were removed completely,
1446 replaced by ahci and mvs modules respectively.
1449 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1450 the 20141231 entry below for information about prerequisites and
1451 upgrading, if you are not already using 3.5.0 or higher.
1454 The 32-bit PowerPC kernel has been changed to a position-independent
1455 executable. This can only be booted with a version of loader(8)
1456 newer than January 31, 2015, so make sure to update both world and
1457 kernel before rebooting.
1460 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1461 but before r278950, the RNG was not seeded properly. Immediately
1462 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1463 ssh keys or openssl keys) that were generated w/ a kernel from that
1464 range. This does not affect programs that directly used /dev/random
1465 or /dev/urandom. All userland uses of arc4random(3) are affected.
1468 The autofs(4) ABI was changed in order to restore binary compatibility
1469 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1470 with the new kernel.
1473 The powerpc64 kernel has been changed to a position-independent
1474 executable. This can only be booted with a new version of loader(8),
1475 so make sure to update both world and kernel before rebooting.
1478 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1479 only release, no new features have been added. Please see the 20141231
1480 entry below for information about prerequisites and upgrading, if you
1481 are not already using 3.5.0.
1484 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1485 taken from the ELF Tool Chain project rather than GNU binutils. They
1486 should be drop-in replacements, with the addition of arm64 support.
1487 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1488 binutils tools, if necessary. See 20150805 for updated information.
1491 The default Unbound configuration now enables remote control
1492 using a local socket. Users who have already enabled the
1493 local_unbound service should regenerate their configuration
1494 by running "service local_unbound setup" as root.
1497 The GNU texinfo and GNU info pages have been removed.
1498 To be able to view GNU info pages please install texinfo from ports.
1501 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1503 As of this release, a prerequisite for building clang, llvm and lldb is
1504 a C++11 capable compiler and C++11 standard library. This means that to
1505 be able to successfully build the cross-tools stage of buildworld, with
1506 clang as the bootstrap compiler, your system compiler or cross compiler
1507 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1508 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1511 On any standard FreeBSD 10.x or 11.x installation, where clang and
1512 libc++ are on by default (that is, on x86 or arm), this should work out
1515 On 9.x installations where clang is enabled by default, e.g. on x86 and
1516 powerpc, libc++ will not be enabled by default, so libc++ should be
1517 built (with clang) and installed first. If both clang and libc++ are
1518 missing, build clang first, then use it to build libc++.
1520 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1521 the instructions for 9.x above.
1523 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1524 default, and do not build clang.
1526 Many embedded systems are resource constrained, and will not be able to
1527 build clang in a reasonable time, or in some cases at all. In those
1528 cases, cross building bootable systems on amd64 is a workaround.
1530 This new version of clang introduces a number of new warnings, of which
1531 the following are most likely to appear:
1535 This warns in two cases, for both C and C++:
1536 * When the code is trying to take the absolute value of an unsigned
1537 quantity, which is effectively a no-op, and almost never what was
1538 intended. The code should be fixed, if at all possible. If you are
1539 sure that the unsigned quantity can be safely cast to signed, without
1540 loss of information or undefined behavior, you can add an explicit
1541 cast, or disable the warning.
1543 * When the code is trying to take an absolute value, but the called
1544 abs() variant is for the wrong type, which can lead to truncation.
1545 If you want to disable the warning instead of fixing the code, please
1546 make sure that truncation will not occur, or it might lead to unwanted
1549 -Wtautological-undefined-compare and
1550 -Wundefined-bool-conversion
1552 These warn when C++ code is trying to compare 'this' against NULL, while
1553 'this' should never be NULL in well-defined C++ code. However, there is
1554 some legacy (pre C++11) code out there, which actively abuses this
1555 feature, which was less strictly defined in previous C++ versions.
1557 Squid and openjdk do this, for example. The warning can be turned off
1558 for C++98 and earlier, but compiling the code in C++11 mode might result
1559 in unexpected behavior; for example, the parts of the program that are
1560 unreachable could be optimized away.
1563 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1564 kernel sources have been removed. The .h files remain, since some
1565 utilities include them. This will need to be fixed later.
1566 If "mount -t oldnfs ..." is attempted, it will fail.
1567 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1568 the utilities will report errors.
1571 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1572 directories to top level SUBDIR variable when their parent
1573 directory is included in LOCAL_DIRS. Users with build systems with
1574 such hierarchies and without SUBDIR entries in the parent
1575 directory Makefiles should add them or add the directories to
1579 faith(4) and faithd(8) have been removed from the base system. Faith
1580 has been obsolete for a very long time.
1583 vt(4), the new console driver, is enabled by default. It brings
1584 support for Unicode and double-width characters, as well as
1585 support for UEFI and integration with the KMS kernel video
1588 You may need to update your console settings in /etc/rc.conf,
1589 most probably the keymap. During boot, /etc/rc.d/syscons will
1590 indicate what you need to do.
1592 vt(4) still has issues and lacks some features compared to
1593 syscons(4). See the wiki for up-to-date information:
1594 https://wiki.freebsd.org/Newcons
1596 If you want to keep using syscons(4), you can do so by adding
1597 the following line to /boot/loader.conf:
1601 pjdfstest has been integrated into kyua as an opt-in test suite.
1602 Please see share/doc/pjdfstest/README for more details on how to
1606 gperf has been removed from the base system for architectures
1607 that use clang. Ports that require gperf will obtain it from the
1611 pjdfstest has been moved from tools/regression/pjdfstest to
1615 At svn r271982, The default linux compat kernel ABI has been adjusted
1616 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1617 update. If you wish to continue using the linux-f10 compat ports,
1618 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1619 encouraged to update their linux-compat packages to linux-c6 during
1620 their next update cycle.
1623 The ofwfb driver, used to provide a graphics console on PowerPC when
1624 using vt(4), no longer allows mmap() of all physical memory. This
1625 will prevent Xorg on PowerPC with some ATI graphics cards from
1626 initializing properly unless x11-servers/xorg-server is updated to
1630 The xdev targets have been converted to using TARGET and
1631 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1634 The default unbound configuration has been modified to address
1635 issues with reverse lookups on networks that use private
1636 address ranges. If you use the local_unbound service, run
1637 "service local_unbound setup" as root to regenerate your
1638 configuration, then "service local_unbound reload" to load the
1642 The GNU texinfo and GNU info pages are not built and installed
1643 anymore, WITH_INFO knob has been added to allow to built and install
1645 UPDATE: see 20150102 entry on texinfo's removal
1648 The GNU readline library is now an INTERNALLIB - that is, it is
1649 statically linked into consumers (GDB and variants) in the base
1650 system, and the shared library is no longer installed. The
1651 devel/readline port is available for third party software that
1655 The Itanium architecture (ia64) has been removed from the list of
1656 known architectures. This is the first step in the removal of the
1660 Commit r268115 has added NFSv4.1 server support, merged from
1661 projects/nfsv4.1-server. Since this includes changes to the
1662 internal interfaces between the NFS related modules, a full
1663 build of the kernel and modules will be necessary.
1664 __FreeBSD_version has been bumped.
1667 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1668 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1669 which differs from the behaviour controlled by this knob.)
1672 Maximal length of the serial number in CTL was increased from 16 to
1673 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1674 and ctld, need to be rebuilt to work with a new kernel.
1677 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1678 1 respectively to match the upstream numbers. They were out of
1679 sync because, when they were originally added to FreeBSD, the
1680 upstream versions were not respected. These libraries are private
1681 and not yet built by default, so renumbering them should be a
1682 non-issue. However, unclean source trees will yield broken test
1683 programs once the operator executes "make delete-old-libs" after a
1684 "make installworld".
1686 Additionally, the atf-sh binary was made private by moving it into
1687 /usr/libexec/. Already-built shell test programs will keep the
1688 path to the old binary so they will break after "make delete-old"
1691 If you are using WITH_TESTS=yes (not the default), wipe the object
1692 tree and rebuild from scratch to prevent spurious test failures.
1693 This is only needed once: the misnumbered libraries and misplaced
1694 binaries have been added to OptionalObsoleteFiles.inc so they will
1695 be removed during a clean upgrade.
1698 Clang and llvm have been upgraded to 3.4.1 release.
1701 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1702 be removed to avoid issues in the future (and has been added to
1706 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1707 past, it affected all builds that used the bsd.*.mk files. The old
1708 behavior was a bug, but people may have relied upon it. To get this
1709 behavior back, you can .include /etc/src.conf from /etc/make.conf
1710 (which is still global and isn't changed). This also changes the
1711 behavior of incremental builds inside the tree of individual
1712 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1713 Although this has survived make universe and some upgrade scenarios,
1714 other upgrade scenarios may have broken. At least one form of
1715 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1716 as well... In cases where MAKESYSPATH isn't working with this
1717 setting, you'll need to set it to the full path to your tree.
1719 One side effect of all this cleaning up is that bsd.compiler.mk
1720 is no longer implicitly included by bsd.own.mk. If you wish to
1721 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1725 The lindev device has been removed since /dev/full has been made a
1726 standard device. __FreeBSD_version has been bumped.
1729 The knob WITHOUT_VI was added to the base system, which controls
1730 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1731 in order to reorder files share/termcap and didn't build ex(1) as a
1732 build tool, so building/installing with WITH_VI is highly advised for
1733 build hosts for older releases.
1735 This issue has been fixed in stable/9 and stable/10 in r277022 and
1736 r276991, respectively.
1739 The YES_HESIOD knob has been removed. It has been obsolete for
1740 a decade. Please move to using WITH_HESIOD instead or your builds
1741 will silently lack HESIOD.
1744 The uart(4) driver has been changed with respect to its handling
1745 of the low-level console. Previously the uart(4) driver prevented
1746 any process from changing the baudrate or the CLOCAL and HUPCL
1747 control flags. By removing the restrictions, operators can make
1748 changes to the serial console port without having to reboot.
1749 However, when getty(8) is started on the serial device that is
1750 associated with the low-level console, a misconfigured terminal
1751 line in /etc/ttys will now have a real impact.
1752 Before upgrading the kernel, make sure that /etc/ttys has the
1753 serial console device configured as 3wire without baudrate to
1754 preserve the previous behaviour. E.g:
1755 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1758 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1759 to improve performance. To re-enable it, if needed, run rpcbind
1760 with command line option -W.
1763 Switched back to the GPL dtc compiler due to updates in the upstream
1764 dts files not being supported by the BSDL dtc compiler. You will need
1765 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1766 may result while building dtb files during a kernel build if you fail
1767 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1770 Clang and llvm have been upgraded to 3.4 release.
1773 The nve(4) driver has been removed. Please use the nfe(4) driver
1774 for NVIDIA nForce MCP Ethernet adapters instead.
1777 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1778 This could cause certain C++ applications using shared libraries built
1779 against the previous version of libc++ to crash. The incompatibility
1780 has now been fixed, but any C++ applications or shared libraries built
1781 between r261283 and r261801 should be recompiled.
1784 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1785 capability mode support. Please note that enabling the feature in
1786 kernel is still highly recommended.
1789 OpenSSH is now built with sandbox support, and will use sandbox as
1790 the default privilege separation method. This requires Capsicum
1791 capability mode support in kernel.
1794 The libelf and libdwarf libraries have been updated to newer
1795 versions from upstream. Shared library version numbers for
1796 these two libraries were bumped. Any ports or binaries
1797 requiring these two libraries should be recompiled.
1798 __FreeBSD_version is bumped to 1100006.
1801 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1802 instead of providing an explicit one, this would prevent such
1803 Makefile from providing its own Kyuafile in the future during
1804 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1805 intervention is needed to clean an objdir if you use NO_CLEAN:
1806 # find /usr/obj -name Kyuafile | xargs rm -f
1809 The behavior of gss_pseudo_random() for the krb5 mechanism
1810 has changed, for applications requesting a longer random string
1811 than produced by the underlying enctype's pseudo-random() function.
1812 In particular, the random string produced from a session key of
1813 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1814 be different at the 17th octet and later, after this change.
1815 The counter used in the PRF+ construction is now encoded as a
1816 big-endian integer in accordance with RFC 4402.
1817 __FreeBSD_version is bumped to 1100004.
1820 The WITHOUT_ATF build knob has been removed and its functionality
1821 has been subsumed into the more generic WITHOUT_TESTS. If you were
1822 using the former to disable the build of the ATF libraries, you
1823 should change your settings to use the latter.
1826 The default version of mtree is nmtree which is obtained from
1827 NetBSD. The output is generally the same, but may vary
1828 slightly. If you found you need identical output adding
1829 "-F freebsd9" to the command line should do the trick. For the
1830 time being, the old mtree is available as fmtree.
1833 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1834 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1835 1.1.4_8 and verify bsdyml not linked in, before running "make
1837 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1839 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1842 The stable/10 branch has been created in subversion from head
1849 Avoid using make -j when upgrading. While generally safe, there are
1850 sometimes problems using -j to upgrade. If your upgrade fails with
1851 -j, please try again without -j. From time to time in the past there
1852 have been problems using -j with buildworld and/or installworld. This
1853 is especially true when upgrading between "distant" versions (eg one
1854 that cross a major release boundary or several minor releases, or when
1855 several months have passed on the -current branch).
1857 Sometimes, obscure build problems are the result of environment
1858 poisoning. This can happen because the make utility reads its
1859 environment when searching for values for global variables. To run
1860 your build attempts in an "environmental clean room", prefix all make
1861 commands with 'env -i '. See the env(1) manual page for more details.
1863 When upgrading from one major version to another it is generally best to
1864 upgrade to the latest code in the currently installed branch first, then
1865 do an upgrade to the new branch. This is the best-tested upgrade path,
1866 and has the highest probability of being successful. Please try this
1867 approach if you encounter problems with a major version upgrade. Since
1868 the stable 4.x branch point, one has generally been able to upgrade from
1869 anywhere in the most recent stable branch to head / current (or even the
1870 last couple of stable branches). See the top of this file when there's
1873 When upgrading a live system, having a root shell around before
1874 installing anything can help undo problems. Not having a root shell
1875 around can lead to problems if pam has changed too much from your
1876 starting point to allow continued authentication after the upgrade.
1878 This file should be read as a log of events. When a later event changes
1879 information of a prior event, the prior event should not be deleted.
1880 Instead, a pointer to the entry with the new information should be
1881 placed in the old entry. Readers of this file should also sanity check
1882 older entries before relying on them blindly. Authors of new entries
1883 should write them with this in mind.
1887 When upgrading the boot ZFS pool to a new version, always follow
1890 1.) recompile and reinstall the ZFS boot loader and boot block
1891 (this is part of "make buildworld" and "make installworld")
1893 2.) update the ZFS boot block on your boot drive
1895 The following example updates the ZFS boot block on the first
1896 partition (freebsd-boot) of a GPT partitioned drive ada0:
1897 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1899 Non-boot pools do not need these updates.
1903 If you are updating from a prior version of FreeBSD (even one just
1904 a few days old), you should follow this procedure. It is the most
1905 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1907 make kernel-toolchain
1908 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1909 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1911 To test a kernel once
1912 ---------------------
1913 If you just want to boot a kernel once (because you are not sure
1914 if it works, or if you want to boot a known bad kernel to provide
1915 debugging information) run
1916 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1917 nextboot -k testkernel
1919 To rebuild everything and install it on the current system.
1920 -----------------------------------------------------------
1921 # Note: sometimes if you are running current you gotta do more than
1922 # is listed here if you are upgrading from a really old current.
1924 <make sure you have good level 0 dumps>
1926 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1927 make installkernel KERNCONF=YOUR_KERNEL_HERE
1929 <reboot in single user> [3]
1936 To cross-install current onto a separate partition
1937 --------------------------------------------------
1938 # In this approach we use a separate partition to hold
1939 # current's root, 'usr', and 'var' directories. A partition
1940 # holding "/", "/usr" and "/var" should be about 2GB in
1943 <make sure you have good level 0 dumps>
1946 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1947 <maybe newfs current's root partition>
1948 <mount current's root partition on directory ${CURRENT_ROOT}>
1949 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1950 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1951 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1952 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1953 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1954 <reboot into current>
1955 <do a "native" rebuild/install as described in the previous section>
1956 <maybe install compatibility libraries from ports/misc/compat*>
1960 To upgrade in-place from stable to current
1961 ----------------------------------------------
1962 <make sure you have good level 0 dumps>
1964 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1965 make installkernel KERNCONF=YOUR_KERNEL_HERE
1967 <reboot in single user> [3]
1974 Make sure that you've read the UPDATING file to understand the
1975 tweaks to various things you need. At this point in the life
1976 cycle of current, things change often and you are on your own
1977 to cope. The defaults can also change, so please read ALL of
1978 the UPDATING entries.
1980 Also, if you are tracking -current, you must be subscribed to
1981 freebsd-current@freebsd.org. Make sure that before you update
1982 your sources that you have read and understood all the recent
1983 messages there. If in doubt, please track -stable which has
1984 much fewer pitfalls.
1986 [1] If you have third party modules, such as vmware, you
1987 should disable them at this point so they don't crash your
1990 [3] From the bootblocks, boot -s, and then do
1995 adjkerntz -i # if CMOS is wall time
1996 Also, when doing a major release upgrade, it is required that
1997 you boot into single user mode to do the installworld.
1999 [4] Note: This step is non-optional. Failure to do this step
2000 can result in a significant reduction in the functionality of the
2001 system. Attempting to do it by hand is not recommended and those
2002 that pursue this avenue should read this file carefully, as well
2003 as the archives of freebsd-current and freebsd-hackers mailing lists
2004 for potential gotchas. The -U option is also useful to consider.
2005 See mergemaster(8) for more information.
2007 [5] Usually this step is a no-op. However, from time to time
2008 you may need to do this if you get unknown user in the following
2009 step. It never hurts to do it all the time. You may need to
2010 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2011 install) after the buildworld before this step if you last updated
2012 from current before 20130425 or from -stable before 20130430.
2014 [6] This only deletes old files and directories. Old libraries
2015 can be deleted by "make delete-old-libs", but you have to make
2016 sure that no program is using those libraries anymore.
2018 [8] The new kernel must be able to run existing binaries used by
2019 an installworld. When upgrading across major versions, the new
2020 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2021 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2022 binaries). Failure to do so may leave you with a system that is
2023 hard to boot to recover. A GENERIC kernel will include suitable
2024 compatibility options to run binaries from older branches.
2026 Make sure that you merge any new devices from GENERIC since the
2027 last time you updated your kernel config file.
2029 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2030 "?=" instead of the "=" assignment operator, so that buildworld can
2031 override the CPUTYPE if it needs to.
2033 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2034 not on the command line, or in /etc/make.conf. buildworld will
2035 warn if it is improperly defined.
2038 This file contains a list, in reverse chronological order, of major
2039 breakages in tracking -current. It is not guaranteed to be a complete
2040 list of such breakages, and only contains entries since September 23, 2011.
2041 If you need to see UPDATING entries from before that date, you will need
2042 to fetch an UPDATING file from an older FreeBSD release.
2044 Copyright information:
2046 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2048 Redistribution, publication, translation and use, with or without
2049 modification, in full or in part, in any form or format of this
2050 document are permitted without further permission from the author.
2052 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2053 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2054 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2055 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2056 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2057 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2058 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2059 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2060 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2061 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2062 POSSIBILITY OF SUCH DAMAGE.
2064 Contact Warner Losh if you have any questions about your use of