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