1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
15 FreeBSD 13.x has many debugging features turned on, in both the kernel
16 and userland. These features attempt to detect incorrect use of
17 system primitives, and encourage loud failure through extra sanity
18 checking and fail stop semantics. They also substantially impact
19 system performance. If you want to do performance measurement,
20 benchmarking, and optimization, you'll want to turn them off. This
21 includes various WITNESS- related kernel options, INVARIANTS, malloc
22 debugging flags in userland, and various verbose features in the
23 kernel. Many developers choose to disable these features on build
24 machines to maximize performance. (To completely disable malloc
25 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
26 disable the most expensive debugging functionality run
27 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
30 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
31 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
32 been removed from mount_fusefs(8). You can safely remove them from
33 your scripts, because they had no effect.
35 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
36 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
37 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
38 sysctls have been removed. If you felt the need to set any of them to
39 a non-default value, please tell asomers@FreeBSD.org why.
42 Default permissions on the /var/account/acct file (and copies of it
43 rotated by periodic daily scripts) are changed from 0644 to 0640
44 because the file contains sensitive information that should not be
45 world-readable. If the /var/account directory must be created by
46 rc.d/accounting, the mode used is now 0750. Admins who use the
47 accounting feature are encouraged to change the mode of an existing
48 /var/account directory to 0750 or 0700.
51 Entropy collection and the /dev/random device are no longer optional
52 components. The "device random" option has been removed.
53 Implementations of distilling algorithms can still be made loadable
54 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
57 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
58 been upgraded to 8.0.1. Please see the 20141231 entry below for
59 information about prerequisites and upgrading, if you are not already
60 using clang 3.5.0 or higher.
63 A fix was applied to i386 kernel modules to avoid panics with
64 dpcpu or vnet. Users need to recompile i386 kernel modules
65 having pcpu or vnet sections or they will refuse to load.
68 User-wired pages now have their own counter,
69 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
70 to vm.max_user_wired and changed from an unsigned int to an unsigned
71 long. bhyve VMs wired with the -S are now subject to the user
72 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
73 avoid running into the limit.
76 The IPSEC option has been removed from GENERIC. Users requiring
77 ipsec(4) must now load the ipsec(4) kernel module.
80 The tap(4) driver has been folded into tun(4), and the module has been
81 renamed to tuntap. You should update any kld_load="if_tap" or
82 kld_load="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
83 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
84 module instead, and "device tap" or "device tun" entries in kernel
85 config files to select the tuntap device instead.
88 The following knobs have been added related to tradeoffs between
89 safe use of the random device and availability in the absence of
92 kern.random.initial_seeding.bypass_before_seeding: tunable; set
93 non-zero to bypass the random device prior to seeding, or zero to
94 block random requests until the random device is initially seeded.
95 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
96 availability properties.
98 kern.random.initial_seeding.read_random_bypassed_before_seeding:
99 read-only diagnostic sysctl that is set when bypass is enabled and
100 read_random(9) is bypassed, to enable programmatic handling of this
101 initial condition, if desired.
103 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
104 Similar to the above, but for for arc4random(9) initial seeding.
106 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
107 non-zero to disable warnings in dmesg when the same conditions are
108 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
109 produce warnings in dmesg when the conditions are met.
112 The loadable random module KPI has changed; the random_infra_init()
113 routine now requires a 3rd function pointer for a bool (*)(void)
114 method that returns true if the random device is seeded (and
115 therefore unblocked).
118 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
119 built from head sources between r320757 (July 6, 2017) and
120 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
121 is added to the command line.
122 nfsuserd daemons built from head sources that are post-r338192 are
123 not affected and should continue to work.
126 The fuse(4) module has been renamed to fusefs(4) for consistency with
127 other filesystems. You should update any kld_load="fuse" entries in
128 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
129 "options FUSE" entries in kernel config files.
132 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
133 8.0.0. Please see the 20141231 entry below for information about
134 prerequisites and upgrading, if you are not already using clang 3.5.0
138 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
139 compiled into your custom kernel, add 'device xz' statement to the
143 drm and drm2 have been removed from the tree. Please see
144 https://wiki.freebsd.org/Graphics for the latest information on
145 migrating to the drm ports.
148 Iflib is no longer unconditionally compiled into the kernel. Drivers
149 using iflib and statically compiled into the kernel, now require
150 the 'device iflib' config option. For the same drivers loaded as
151 modules on kernels not having 'device iflib', the iflib.ko module
152 is loaded automatically.
155 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
156 options no longer exist since r343219 and r343427 respectively;
157 nothing uses them, so they should be just removed from custom
161 r342635 changes the way efibootmgr(8) works by requiring users to add
162 the -b (bootnum) parameter for commands where the bootnum was previously
163 specified with each option. For example 'efibootmgr -B 0001' is now
164 'efibootmgr -B -b 0001'.
167 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
168 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
169 servers that have vfs.nfsd.nfs_privport set will only allow mounts
170 from clients using a reserved port#. Since both the FreeBSD and Linux
171 NFSv4 clients use reserved port#s by default, this should not affect
175 The XLP config has been removed. We can't support 64-bit atomics in this
176 kernel because it is running in 32-bit mode. XLP users must transition
177 to running a 64-bit kernel (XLP64 or XLPN32).
179 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
180 the preferred emulator today and we don't need two different ones.
182 The old sibyte / swarm / Broadcom BCM1250 support has been
183 removed from the mips port.
186 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
187 7.0.1. Please see the 20141231 entry below for information about
188 prerequisites and upgrading, if you are not already using clang 3.5.0
192 Remove the timed and netdate programs from the base tree. Setting
193 the time with these daemons has been obsolete for over a decade.
196 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
197 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
198 it produces broken binaries when ifuncs are in use. Users needing
199 GNU ld should install the binutils port or package.
202 The BSD crtbegin and crtend code has been enabled by default. It has
203 had extensive testing on amd64, arm64, and i386. It can be disabled
204 by building a world with -DWITHOUT_BSD_CRTBEGIN.
207 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
208 has been converted to a port (misc/ctm) and will be removed from
209 FreeBSD-13. It is available as a package (ctm) for all supported
213 The default newsyslog.conf(5) file has been changed to only include
214 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
215 the filenames end in '.conf' and do not begin with a '.'.
217 You should check the configuration files in these two directories match
218 this naming convention. You can verify which configuration files are
219 being included using the command:
223 Ports for the DRM modules have been simplified. Now, amd64 users should
224 just install the drm-kmod port. All others should install
227 Graphics hardware that's newer than about 2010 usually works with
228 drm-kmod. For hardware older than 2013, however, some users will need
229 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
230 than 2008 usually only works in drm-legacy-kmod. The graphics team can
231 only commit to hardware made since 2013 due to the complexity of the
232 market and difficulty to test all the older cards effectively. If you
233 have hardware supported by drm-kmod, you are strongly encouraged to use
234 that as you will get better support.
236 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
237 elsewhere, the drm and drm2 modules will be eliminated from the src base
238 soon (with a limited exception for arm). Please update to the package
239 asap and report any issues to x11@freebsd.org.
241 Generally, anybody using the drm*-kmod packages should add
242 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
243 cross-threading surprises, especially with automatic driver
244 loading from X11 startup. These will become the defaults in 13-current
248 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
249 custom kernel and module loading configuration files must be updated
250 accordingly. Moreover, interfaces previous presented as ixlvN to the
251 system are now exposed as iavfN and network configuration files must
252 be adjusted as necessary.
255 OpenSSL has been updated to version 1.1.1. This update included
256 additional various API changes throughout the base system. It is
257 important to rebuild third-party software after upgrading. The value
258 of __FreeBSD_version has been bumped accordingly.
261 The legacy DRM modules and drivers have now been added to the loader's
262 module blacklist, in favor of loading them with kld_list in rc.conf(5).
263 The module blacklist may be overridden with the loader.conf(5)
264 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
268 The cam(4) based nda(4) driver will be used over nvd(4) by default on
269 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
270 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
271 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
275 Reproducible build mode is now on by default, in preparation for
276 FreeBSD 12.0. This eliminates build metadata such as the user,
277 host, and time from the kernel (and uname), unless the working tree
278 corresponds to a modified checkout from a version control system.
279 The previous behavior can be obtained by setting the /etc/src.conf
280 knob WITHOUT_REPRODUCIBLE_BUILD.
283 The Yarrow CSPRNG has been removed from the kernel as it has not been
284 supported by its designers since at least 2003. Fortuna has been the
285 default since FreeBSD-11.
288 devctl freeze/thaw have gone into the tree, the rc scripts have been
289 updated to use them and devmatch has been changed. You should update
290 kernel, userland and rc scripts all at the same time.
293 The default interpreter has been switched from 4th to Lua.
294 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
295 interpreter. If you have custom FORTH code you will need to set
296 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
297 src.conf for the build. This will create default hard links between
298 loader and loader_4th instead of loader and loader_lua, the new default.
299 If you are using UEFI it will create the proper hard link to loader.efi.
301 bhyve uses userboot.so. It remains 4th-only until some issues are solved
302 regarding coexisting with multiple versions of FreeBSD are resolved.
305 ls(1) now respects the COLORTERM environment variable used in other
306 systems and software to indicate that a colored terminal is both
307 supported and desired. If ls(1) is suddenly emitting colors, they may
308 be disabled again by either removing the unwanted COLORTERM from your
309 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
310 may not be observed in a future release.
313 The default pager for most commands has been changed to "less". To
314 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
318 The jedec_ts(4) driver has been removed. A superset of its functionality
319 is available in the jedec_dimm(4) driver, and the manpage for that
320 driver includes migration instructions. If you have "device jedec_ts"
321 in your kernel configuration file, it must be removed.
324 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
325 This should have no effect if the kernel is booted via BIOS/legacy boot.
326 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
327 has a buggy firmware that prevents a successful boot due to use of
331 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
332 support has been removed from the tree. These ports were
333 obsolete and/or known to be broken for many years.
336 loader.efi has been augmented to participate more fully in the
337 UEFI boot manager protocol. loader.efi will now look at the
338 BootXXXX environment variable to determine if a specific kernel
339 or root partition was specified. XXXX is derived from BootCurrent.
340 efibootmgr(8) manages these standard UEFI variables.
343 zfsloader's functionality has now been folded into loader.
344 zfsloader is no longer necessary once you've updated your
345 boot blocks. For a transition period, we will install a
346 hardlink for zfsloader to loader to allow a smooth transition
347 until the boot blocks can be updated (hard link because old
348 zfs boot blocks don't understand symlinks).
351 ARM64 now have efifb support, if you want to have serial console
352 on your arm64 board when an screen is connected and the bootloader
353 setup a frame buffer for us to use, just add :
357 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
358 an screen connected as the firmware will setup a frame buffer are that
359 u-boot will expose as an EFI frame buffer.
362 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
363 or take steps to update /etc/passwd before doing installworld on
364 existing systems. Do not skip the "mergemaster -Fp" step before
365 installworld, as described in the update procedures near the bottom
366 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
367 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
368 the ntp config file contain options that change file/dir locations.
369 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
370 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
371 taking steps to ensure that all required files/dirs are accessible
375 Big endian arm support has been removed.
378 The static environment setup in kernel configs is no longer mutually
379 exclusive with the loader(8) environment by default. In order to
380 restore the previous default behavior of disabling the loader(8)
381 environment if a static environment is present, you must specify
382 loader_env.disabled=1 in the static environment.
385 The ABI of syscalls used by management tools like sockstat and
386 netstat has been broken to allow 32-bit binaries to work on
387 64-bit kernels without modification. These programs will need
388 to match the kernel in order to function. External programs may
389 require minor modifications to accommodate a change of type in
390 structures from pointers to 64-bit virtual addresses.
393 On i386 and amd64 atomics are now inlined. Out of tree modules using
394 atomics will need to be rebuilt.
397 The '%I' format in the kern.corefile sysctl limits the number of
398 core files that a process can generate to the number stored in the
399 debug.ncores sysctl. The '%I' format is replaced by the single digit
400 index. Previously, if all indexes were taken the kernel would overwrite
401 only a core file with the highest index in a filename.
402 Currently the system will create a new core file if there is a free
403 index or if all slots are taken it will overwrite the oldest one.
406 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
407 6.0.1. Please see the 20141231 entry below for information about
408 prerequisites and upgrading, if you are not already using clang 3.5.0
412 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
413 needed to be changed to work with it. This change was made with r335763
414 and requires a mergemaster / etcupdate / etc to update the installed
418 r334930 changed the interface between the NFS modules, so they all
419 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
422 As of r334391 lld is the default amd64 system linker; it is installed
423 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
427 The kernel / userland interface for devinfo changed, so you'll
428 need a new kernel and userland as a pair for it to work (rebuilding
429 lib/libdevinfo is all that's required). devinfo and devmatch will
430 not work, but everything else will when there's a mismatch.
433 The on-disk format for hwpmc callchain records has changed to include
434 threadid corresponding to a given record. This changes the field offsets
435 and thus requires that libpmcstat be rebuilt before using a kernel
439 The vxge(4) driver has been removed. This driver was introduced into
440 HEAD one week before the Exar left the Ethernet market and is not
441 known to be used. If you have device vxge in your kernel config file
445 The amd64 kernel now requires a ld that supports ifunc to produce a
446 working kernel, either lld or a newer binutils. lld is built by default
447 on amd64, and the 'buildkernel' target uses it automatically. However,
448 it is not the default linker, so building the kernel the traditional
449 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
450 binutils port/package). lld will soon be default, and this requirement
453 NOTE: As of r334391 lld is the default system linker on amd64, and no
454 workaround is necessary.
457 The nxge(4) driver has been removed. This driver was for PCI-X 10g
458 cards made by s2io/Neterion. The company was acquired by Exar and
459 no longer sells or supports Ethernet products. If you have device
460 nxge in your kernel config file it must be removed.
463 The tz database (tzdb) has been updated to 2018e. This version more
464 correctly models time stamps in time zones with negative DST such as
465 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
466 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
467 time zone abbreviations and the tm_isdst flag.
470 The ixgb(4) driver has been removed. This driver was for an early and
471 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
472 quickly shifted to the long lived ixgbe family. If you have device
473 ixgb in your kernel config file it must be removed.
476 The lmc(4) driver has been removed. This was a WAN interface
477 card that was already reportedly rare in 2003, and had an ambiguous
478 license. If you have device lmc in your kernel config file it must
482 Support for Arcnet networks has been removed. If you have device
483 arcnet or device cm in your kernel config file they must be
487 Support for FDDI networks has been removed. If you have device
488 fddi or device fpa in your kernel config file they must be
492 In addition to supporting RFC 3164 formatted messages, the
493 syslogd(8) service is now capable of parsing RFC 5424 formatted
494 log messages. The main benefit of using RFC 5424 is that clients
495 may now send log messages with timestamps containing year numbers,
496 microseconds and time zone offsets.
498 Similarly, the syslog(3) C library function has been altered to
499 send RFC 5424 formatted messages to the local system logging
500 daemon. On systems using syslogd(8), this change should have no
501 negative impact, as long as syslogd(8) and the C library are
502 updated at the same time. On systems using a different system
503 logging daemon, it may be necessary to make configuration
504 adjustments, depending on the software used.
506 When using syslog-ng, add the 'syslog-protocol' flag to local
507 input sources to enable parsing of RFC 5424 formatted messages:
510 unix-dgram("/var/run/log" flags(syslog-protocol));
513 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
514 of the 'imuxsock' module to let messages be processed by the
515 regular RFC 3164/5424 parsing pipeline:
517 module(load="imuxsock" SysSock.UseSpecialParser="off")
519 Do note that these changes only affect communication between local
520 applications and syslogd(8). The format that syslogd(8) uses to
521 store messages on disk or forward messages to other systems
522 remains unchanged. syslogd(8) still uses RFC 3164 for these
523 purposes. Options to customize this behaviour will be added in the
524 future. Utilities that process log files stored in /var/log are
525 thus expected to continue to function as before.
527 __FreeBSD_version has been incremented to 1200061 to denote this
531 Support for token ring networks has been removed. If you
532 have "device token" in your kernel config you should remove
533 it. No device drivers supported token ring.
536 makefs was modified to be able to tag ISO9660 El Torito boot catalog
537 entries as EFI instead of overloading the i386 tag as done previously.
538 The amd64 mkisoimages.sh script used to build amd64 ISO images for
539 release was updated to use this. This may mean that makefs must be
540 updated before "make cdrom" can be run in the release directory. This
541 should be as simple as:
543 $ cd $SRCDIR/usr.sbin/makefs
544 $ make depend all install
547 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
548 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
549 Co-existence for the transition period will come shortly. Booting is a
550 complex environment and test coverage for Lua-enabled loaders has been
551 thin, so it would be prudent to assume it might not work and make
552 provisions for backup boot methods.
555 devmatch functionality has been turned on in devd. It will automatically
556 load drivers for unattached devices. This may cause unexpected drivers
557 to be loaded. Please report any problems to current@ and
561 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
562 6.0.0. Please see the 20141231 entry below for information about
563 prerequisites and upgrading, if you are not already using clang 3.5.0
567 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
568 This means it is used to link the kernel and userland libraries and
569 executables, but is not yet installed as /usr/bin/ld by default.
571 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
572 WITHOUT_LLD_BOOTSTRAP=yes
575 On i386, pmtimer has been removed. Its functionality has been folded
576 into apm. It was a no-op on ACPI in current for a while now (but was
577 still needed on i386 in FreeBSD 11 and earlier). Users may need to
578 remove it from kernel config files.
581 The use of RSS hash from the network card aka flowid has been
582 disabled by default for lagg(4) as it's currently incompatible with
583 the lacp and loadbalance protocols.
585 This can be re-enabled by setting the following in loader.conf:
586 net.link.lagg.default_use_flowid="1"
589 The SW_WATCHDOG option is no longer necessary to enable the
590 hardclock-based software watchdog if no hardware watchdog is
591 configured. As before, SW_WATCHDOG will cause the software
592 watchdog to be enabled even if a hardware watchdog is configured.
595 r326887 fixes the issue described in the 20171214 UPDATING entry.
596 r326888 flips the switch back to building GELI support always.
599 r362593 broke ZFS + GELI support for reasons unknown. However,
600 it also broke ZFS support generally, so GELI has been turned off
601 by default as the lesser evil in r326857. If you boot off ZFS and/or
602 GELI, it might not be a good time to update.
605 PowerPC users must update loader(8) by rebuilding world before
606 installing a new kernel, as the protocol connecting them has
607 changed. Without the update, loader metadata will not be passed
608 successfully to the kernel and users will have to enter their
609 root partition at the kernel mountroot prompt to continue booting.
610 Newer versions of loader can boot old kernels without issue.
613 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
614 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
615 to WITH/OUT_LOADER_GELI.
618 The naive and non-compliant support of posix_fallocate(2) in ZFS
619 has been removed as of r325320. The system call now returns EINVAL
620 when used on a ZFS file. Although the new behavior complies with the
621 standard, some consumers are not prepared to cope with it.
622 One known victim is lld prior to r325420.
625 Building in a FreeBSD src checkout will automatically create object
626 directories now rather than store files in the current directory if
627 'make obj' was not ran. Calling 'make obj' is no longer necessary.
628 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
629 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
633 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
634 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
635 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
636 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
637 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
638 The UNIFIED_OBJDIR option is a transitional feature that will be
639 removed for 12.0 release; please migrate to the new format for any
640 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
641 than hardcoding paths.
644 The native-xtools target no longer installs the files by default to the
645 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
646 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
649 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
650 options are changing from controlling the build if defined / undefined
651 to controlling the build with explicit 'yes' or 'no' values. They will
652 shift to WITH/WITHOUT options to match other options in the system.
655 libstand has turned into a private library for sys/boot use only.
656 It is no longer supported as a public interface outside of sys/boot.
659 The arm port has split armv6 into armv6 and armv7. armv7 is now
660 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
661 and are running a kernel from before r324363, you will need to add
662 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
665 When building multiple kernels using KERNCONF, non-existent KERNCONF
666 files will produce an error and buildkernel will fail. Previously
667 missing KERNCONF files silently failed giving no indication as to
668 why, only to subsequently discover during installkernel that the
669 desired kernel was never built in the first place.
672 The default serial number format for CTL LUNs has changed. This will
673 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
674 or iSCSI clients care about their LUNs' serial numbers. Users who
675 require serial number stability should hardcode serial numbers in
679 For 32-bit arm compiled for hard-float support, soft-floating point
680 binaries now always get their shared libraries from
681 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
682 /usr/libsoft also existed). Only users with a hard-float ld.so, but
683 soft-float everything else should be affected.
686 The geli password typed at boot is now hidden. To restore the previous
687 behavior, see geli(8) for configuration options.
690 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
691 sysctl values. Minor nit, but requires a rebuild of both world/kernel
695 "make check" behavior (made in ^/head@r295380) has been changed to
696 execute from a limited sandbox, as opposed to executing from
700 - The "beforecheck" and "aftercheck" targets are now specified.
701 - ${CHECKDIR} (added in commit noted above) has been removed.
702 - Legacy behavior can be enabled by setting
703 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
705 If the limited sandbox mode is enabled, "make check" will execute
706 "make distribution", then install, execute the tests, and clean up the
707 sandbox if successful.
709 The "make distribution" and "make install" targets are typically run as
710 root to set appropriate permissions and ownership at installation time.
711 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
712 environment if executing "make check" with limited sandbox mode using
713 an unprivileged user.
716 Since the switch to GPT disk labels, fsck for UFS/FFS has been
717 unable to automatically find alternate superblocks. As of r322297,
718 the information needed to find alternate superblocks has been
719 moved to the end of the area reserved for the boot block.
720 Filesystems created with a newfs of this vintage or later
721 will create the recovery information. If you have a filesystem
722 created prior to this change and wish to have a recovery block
723 created for your filesystem, you can do so by running fsck in
724 foreground mode (i.e., do not use the -p or -y options). As it
725 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
726 to which you should answer yes.
729 As of r321665, an NFSv4 server configuration that services
730 Kerberos mounts or clients that do not support the uid/gid in
731 owner/owner_group string capability, must explicitly enable
732 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
733 machine's /etc/rc.conf file.
736 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
737 Please see the 20141231 entry below for information about prerequisites
738 and upgrading, if you are not already using clang 3.5.0 or higher.
741 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
742 r-commands (rlogin, rsh, etc.) to be built with the base system.
745 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
746 a very major ABI incompatible change, so users of FreeBSD/powerpc must
747 be careful when performing source upgrades. It is best to run
748 'make installworld' from an alternate root system, either a live
749 CD/memory stick, or a temporary root partition. Additionally, all ports
750 must be recompiled. powerpc64 is largely unaffected, except in the case
751 of 32-bit compatibility. All 32-bit binaries will be affected.
754 Forward compatibility for the "ino64" project have been committed. This
755 will allow most new binaries to run on older kernels in a limited
756 fashion. This prevents many of the common foot-shooting actions in the
757 upgrade as well as the limited ability to roll back the kernel across
758 the ino64 upgrade. Complicated use cases may not work properly, though
759 enough simpler ones work to allow recovery in most situations.
762 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
763 if you require the GPL compiler.
766 The internal ABI used for communication between the NFS kernel modules
767 was changed by r320085, so __FreeBSD_version was bumped to
768 ensure all the NFS related modules are updated together.
771 The ABI of struct event was changed by extending the data
772 member to 64bit and adding ext fields. For upgrade, same
773 precautions as for the entry 20170523 "ino64" must be
777 The GNU roff toolchain has been removed from base. To render manpages
778 which are not supported by mandoc(1), man(1) can fallback on GNU roff
779 from ports (and recommends to install it).
780 To render roff(7) documents, consider using GNU roff from ports or the
781 heirloom doctools roff toolchain from ports via pkg install groff or
782 via pkg install heirloom-doctools.
785 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
786 smaller runtime footprint builds. This is useful for embedded systems
787 which only require one chipset support.
789 If you load it as a module, make sure this is in /boot/loader.conf:
793 This will load the HAL, all chip/RF backends and if_ath_pci.
794 If you have if_ath_pci in /boot/loader.conf, ensure it is after
795 if_ath or it will not load any HAL chipset support.
797 If you want to selectively load things (eg on ye cheape ARM/MIPS
798 platforms where RAM is at a premium) you should:
801 * load the chip modules in question
802 * load ath_rate, ath_dfs
804 * load if_ath_pci and/or if_ath_ahb depending upon your particular
805 bus bind type - this is where probe/attach is done.
807 For further comments/feedback, poke adrian@ .
810 The "ino64" 64-bit inode project has been committed, which extends
811 a number of types to 64 bits. Upgrading in place requires care and
812 adherence to the documented upgrade procedure.
814 If using a custom kernel configuration ensure that the
815 COMPAT_FREEBSD11 option is included (as during the upgrade the
816 system will be running the ino64 kernel with the existing world).
818 For the safest in-place upgrade begin by removing previous build
819 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
820 procedure documented below under the heading "To rebuild everything and
821 install it on the current system." Specifically, a reboot is required
822 after installing the new kernel before installing world. While an
823 installworld normally works by accident from multiuser after rebooting
824 the proper kernel, there are many cases where this will fail across this
825 upgrade and installworld from single user is required.
828 The NATM framework including the en(4), fatm(4), hatm(4), and
829 patm(4) devices has been removed. Consumers should plan a
830 migration before the end-of-life date for FreeBSD 11.
833 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
834 diff has not been implemented, if those are needed a newer version of
835 GNU diff is available via the diffutils package under the gdiff name.
838 As of r316810 for ipfilter, keep frags is no longer assumed when
839 keep state is specified in a rule. r316810 aligns ipfilter with
840 documentation in man pages separating keep frags from keep state.
841 This allows keep state to be specified without forcing keep frags
842 and allows keep frags to be specified independently of keep state.
843 To maintain previous behaviour, also specify keep frags with
844 keep state (as documented in ipf.conf.5).
847 arm64 builds now use the base system LLD 4.0.0 linker by default,
848 instead of requiring that the aarch64-binutils port or package be
849 installed. To continue using aarch64-binutils, set
850 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
853 The UDP optimization in entry 20160818 that added the sysctl
854 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
855 packets will no longer be treated as L3 broadcast packets.
858 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
859 use any explicitly assigned loopback address available in the jail
860 instead of using the first assigned address of the jail.
863 The ctl.ko module no longer implements the iSCSI target frontend:
864 cfiscsi.ko does instead.
866 If building cfiscsi.ko as a kernel module, the module can be loaded
867 via one of the following methods:
868 - `cfiscsi_load="YES"` in loader.conf(5).
869 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
870 - ctladm(8)/ctld(8), when compiled with iSCSI support
871 (`WITH_ISCSI=yes` in src.conf(5))
873 Please see cfiscsi(4) for more details.
876 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
877 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
878 same source (previously, the dependency of mmcsd.ko on mmc.ko was
879 missing, but mmcsd.ko now will refuse to load if it is incompatible
883 The syntax of ipfw(8) named states was changed to avoid ambiguity.
884 If you have used named states in the firewall rules, you need to modify
885 them after installworld and before rebooting. Now named states must
886 be prefixed with colon.
889 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
890 removed as the userland we provide cannot use them. The KMS version
891 (sys/dev/drm2) supports the same hardware.
894 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
895 Please see the 20141231 entry below for information about prerequisites
896 and upgrading, if you are not already using clang 3.5.0 or higher.
899 The code that provides support for ZFS .zfs/ directory functionality
900 has been reimplemented. It's not possible now to create a snapshot
901 by mkdir under .zfs/snapshot/. That should be the only user visible
905 EISA bus support has been removed. The WITH_EISA option is no longer
909 MCA bus support has been removed.
912 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
913 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
916 The EM_MULTIQUEUE kernel configuration option is deprecated now that
917 the em(4) driver conforms to iflib specifications.
920 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
921 IFLIB. If you have a custom kernel configuration that excludes em(4)
922 but you use igb(4), you need to re-add em(4) to your custom
926 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
927 Please see the 20141231 entry below for information about prerequisites
928 and upgrading, if you are not already using clang 3.5.0 or higher.
931 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
932 Please see the 20141231 entry below for information about prerequisites
933 and upgrading, if you are not already using clang 3.5.0 or higher.
936 The layout of the pmap structure has changed for powerpc to put the pmap
937 statistics at the front for all CPU variations. libkvm(3) and all tools
938 that link against it need to be recompiled.
941 isl(4) and cyapa(4) drivers now require a new driver,
942 chromebook_platform(4), to work properly on Chromebook-class hardware.
943 On other types of hardware the drivers may need to be configured using
944 device hints. Please see the corresponding manual pages for details.
947 The urtwn(4) driver was merged into rtwn(4) and now consists of
948 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
950 Also, firmware for RTL8188CE was renamed due to possible name
951 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
954 GNU rcs has been removed from base. It is available as packages:
955 - rcs: Latest GPLv3 GNU rcs version.
956 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
960 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
961 modules now requires that the kernel configuration contain the
962 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
965 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
966 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
969 Relocatable object files with the extension of .So have been renamed
970 to use an extension of .pico instead. The purpose of this change is
971 to avoid a name clash with shared libraries on case-insensitive file
972 systems. On those file systems, foo.So is the same file as foo.so.
975 GNU rcs has been turned off by default. It can (temporarily) be built
976 again by adding WITH_RCS knob in src.conf.
977 Otherwise, GNU rcs is available from packages:
978 - rcs: Latest GPLv3 GNU rcs version.
979 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
982 The backup_uses_rcs functionality has been removed from rc.subr.
985 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
986 two separate components, QUEUE_MACRO_DEBUG_TRACE and
987 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
988 QUEUE_MACRO_DEBUG behavior.
991 r304787 changed some ioctl interfaces between the iSCSI userspace
992 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
993 rebuilt to work with new kernels. __FreeBSD_version has been bumped
997 The UDP receive code has been updated to only treat incoming UDP
998 packets that were addressed to an L2 broadcast address as L3
999 broadcast packets. It is not expected that this will affect any
1000 standards-conforming UDP application. The new behaviour can be
1001 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1005 Remove the openbsd_poll system call.
1006 __FreeBSD_version has been bumped because of this.
1009 The stable/11 branch has been created from head@r302406.
1012 The libc stub for the pipe(2) system call has been replaced with
1013 a wrapper that calls the pipe2(2) system call and the pipe(2)
1014 system call is now only implemented by the kernels that include
1015 "options COMPAT_FREEBSD10" in their config file (this is the
1016 default). Users should ensure that this option is enabled in
1017 their kernel or upgrade userspace to r302092 before upgrading their
1021 CAM will now strip leading spaces from SCSI disks' serial numbers.
1022 This will affect users who create UFS filesystems on SCSI disks using
1023 those disk's diskid device nodes. For example, if /etc/fstab
1024 previously contained a line like
1025 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1026 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1027 transforms like gmirror may also be affected. ZFS users should
1031 The bitstring(3) API has been updated with new functionality and
1032 improved performance. But it is binary-incompatible with the old API.
1033 Objects built with the new headers may not be linked against objects
1034 built with the old headers.
1037 The brk and sbrk functions have been removed from libc on arm64.
1038 Binutils from ports has been updated to not link to these
1039 functions and should be updated to the latest version before
1040 installing a new libc.
1043 The armv6 port now defaults to hard float ABI. Limited support
1044 for running both hardfloat and soft float on the same system
1045 is available using the libraries installed with -DWITH_LIBSOFT.
1046 This has only been tested as an upgrade path for installworld
1047 and packages may fail or need manual intervention to run. New
1048 packages will be needed.
1050 To update an existing self-hosted armv6hf system, you must add
1051 TARGET_ARCH=armv6 on the make command line for both the build
1052 and the install steps.
1055 Kernel modules compiled outside of a kernel build now default to
1056 installing to /boot/modules instead of /boot/kernel. Many kernel
1057 modules built this way (such as those in ports) already overrode
1058 KMODDIR explicitly to install into /boot/modules. However,
1059 manually building and installing a module from /sys/modules will
1060 now install to /boot/modules instead of /boot/kernel.
1063 The CAM I/O scheduler has been committed to the kernel. There should be
1064 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1065 list of known rogues that claim support for this but actually corrupt
1066 data is believed to be complete, be on the lookout for data
1067 corruption. The known rogue list is believed to be complete:
1069 o Crucial MX100, M550 drives with MU01 firmware.
1070 o Micron M510 and M550 drives with MU01 firmware.
1071 o Micron M500 prior to MU07 firmware
1072 o Samsung 830, 840, and 850 all firmwares
1073 o FCCT M500 all firmwares
1075 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1076 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1077 updated firmware. Black listed drives will work correctly because these
1078 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1079 this list is the same as found in Linux, it's believed there are no
1080 other rogues in the market place. All other models from the above
1083 To be safe, if you are at all concerned, you can quirk each of your
1084 drives to prevent NCQ from being sent by setting:
1085 kern.cam.ada.X.quirks="0x2"
1086 in loader.conf. If the drive requires the 4k sector quirk, set the
1087 quirks entry to 0x3.
1090 The FAST_DEPEND build option has been removed and its functionality is
1091 now the one true way. The old mkdep(1) style of 'make depend' has
1092 been removed. See 20160311 for further details.
1095 Resource range types have grown from unsigned long to uintmax_t. All
1096 drivers, and anything using libdevinfo, need to be recompiled.
1099 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1100 builds. It no longer runs mkdep(1) during 'make depend', and the
1101 'make depend' stage can safely be skipped now as it is auto ran
1102 when building 'make all' and will generate all SRCS and DPSRCS before
1103 building anything else. Dependencies are gathered at compile time with
1104 -MF flags kept in separate .depend files per object file. Users should
1105 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1106 stale .depend files.
1109 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1110 kernel modules. Therefore, if you load any kernel modules at boot time,
1111 please install the boot loaders after you install the kernel, but before
1115 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1116 make installkernel KERNCONF=YOUR_KERNEL_HERE
1117 make -C sys/boot install
1118 <reboot in single user>
1120 Then follow the usual steps, described in the General Notes section,
1124 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1125 see the 20141231 entry below for information about prerequisites and
1126 upgrading, if you are not already using clang 3.5.0 or higher.
1129 The AIO subsystem is now a standard part of the kernel. The
1130 VFS_AIO kernel option and aio.ko kernel module have been removed.
1131 Due to stability concerns, asynchronous I/O requests are only
1132 permitted on sockets and raw disks by default. To enable
1133 asynchronous I/O requests on all file types, set the
1134 vfs.aio.enable_unsafe sysctl to a non-zero value.
1137 The ELF object manipulation tool objcopy is now provided by the
1138 ELF Tool Chain project rather than by GNU binutils. It should be a
1139 drop-in replacement, with the addition of arm64 support. The
1140 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1141 to obtain the GNU version if necessary.
1144 Building ZFS pools on top of zvols is prohibited by default. That
1145 feature has never worked safely; it's always been prone to deadlocks.
1146 Using a zvol as the backing store for a VM guest's virtual disk will
1147 still work, even if the guest is using ZFS. Legacy behavior can be
1148 restored by setting vfs.zfs.vol.recursive=1.
1151 The NONE and HPN patches has been removed from OpenSSH. They are
1152 still available in the security/openssh-portable port.
1155 With the addition of ypldap(8), a new _ypldap user is now required
1156 during installworld. "mergemaster -p" can be used to add the user
1157 prior to installworld, as documented in the handbook.
1160 The tftp loader (pxeboot) now uses the option root-path directive. As a
1161 consequence it no longer looks for a pxeboot.4th file on the tftp
1162 server. Instead it uses the regular /boot infrastructure as with the
1166 The code to start recording plug and play data into the modules has
1167 been committed. While the old tools will properly build a new kernel,
1168 a number of warnings about "unknown metadata record 4" will be produced
1169 for an older kldxref. To avoid such warnings, make sure to rebuild
1170 the kernel toolchain (or world). Make sure that you have r292078 or
1171 later when trying to build 292077 or later before rebuilding.
1174 Debug data files are now built by default with 'make buildworld' and
1175 installed with 'make installworld'. This facilitates debugging but
1176 requires more disk space both during the build and for the installed
1177 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1181 r291527 changed the internal interface between the nfsd.ko and
1182 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1183 __FreeBSD_version has been bumped because of this.
1186 Add support for unicode collation strings leads to a change of
1187 order of files listed by ls(1) for example. To get back to the old
1188 behaviour, set LC_COLLATE environment variable to "C".
1190 Databases administrators will need to reindex their databases given
1191 collation results will be different.
1193 Due to a bug in install(1) it is recommended to remove the ancient
1194 locales before running make installworld.
1196 rm -rf /usr/share/locale/*
1199 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1200 libcrypto.so.7 or libssl.so.7 must be recompiled.
1203 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1204 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1205 should be replaced with isp_2400 and isp_2500 modules respectively.
1208 The build previously allowed using 'make -n' to not recurse into
1209 sub-directories while showing what commands would be executed, and
1210 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1211 and 'make -N' will not.
1214 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1215 and etcupdate will now use this file. A custom sendmail.cf is now
1216 updated via this mechanism rather than via installworld. If you had
1217 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1218 want to remove the exclusion or change it to "always install".
1219 /etc/mail/sendmail.cf is now managed the same way regardless of
1220 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1221 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1224 Compatibility shims for legacy ATA device names have been removed.
1225 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1226 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1227 environment variables, /dev/ad* and /dev/ar* symbolic links.
1230 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1231 Please see the 20141231 entry below for information about prerequisites
1232 and upgrading, if you are not already using clang 3.5.0 or higher.
1235 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1236 and renamed from .symbols to .debug. This reduces the size requirements
1237 on the boot partition or file system and provides consistency with
1238 userland debug files.
1240 When using the supported kernel installation method the
1241 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1242 as is done with /boot/kernel.
1244 Developers wishing to maintain the historical behavior of installing
1245 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1248 The wireless drivers had undergone changes that remove the 'parent
1249 interface' from the ifconfig -l output. The rc.d network scripts
1250 used to check presence of a parent interface in the list, so old
1251 scripts would fail to start wireless networking. Thus, etcupdate(3)
1252 or mergemaster(8) run is required after kernel update, to update your
1253 rc.d scripts in /etc.
1256 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1257 These configurations are now automatically interpreted as
1258 'scrub fragment reassemble'.
1261 Kernel-loadable modules for the random(4) device are back. To use
1262 them, the kernel must have
1265 options RANDOM_LOADABLE
1267 kldload(8) can then be used to load random_fortuna.ko
1268 or random_yarrow.ko. Please note that due to the indirect
1269 function calls that the loadable modules need to provide,
1270 the build-in variants will be slightly more efficient.
1272 The random(4) kernel option RANDOM_DUMMY has been retired due to
1273 unpopularity. It was not all that useful anyway.
1276 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1277 Control over building the ELF Tool Chain tools is now provided by
1278 the WITHOUT_TOOLCHAIN knob.
1281 The polarity of Pulse Per Second (PPS) capture events with the
1282 uart(4) driver has been corrected. Prior to this change the PPS
1283 "assert" event corresponded to the trailing edge of a positive PPS
1284 pulse and the "clear" event was the leading edge of the next pulse.
1286 As the width of a PPS pulse in a typical GPS receiver is on the
1287 order of 1 millisecond, most users will not notice any significant
1288 difference with this change.
1290 Anyone who has compensated for the historical polarity reversal by
1291 configuring a negative offset equal to the pulse width will need to
1292 remove that workaround.
1295 The default group assigned to /dev/dri entries has been changed
1296 from 'wheel' to 'video' with the id of '44'. If you want to have
1297 access to the dri devices please add yourself to the video group
1300 # pw groupmod video -m $USER
1303 The menu.rc and loader.rc files will now be replaced during
1304 upgrades. Please migrate local changes to menu.rc.local and
1305 loader.rc.local instead.
1308 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1309 strings and strip have been removed. The src.conf(5) knob
1310 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1313 As ZFS requires more kernel stack pages than is the default on some
1314 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1315 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1317 Please consider using 'options KSTACK_PAGES=X' where X is greater
1318 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1321 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1322 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1323 default, i.e., they will not contain "::". For example, instead
1324 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1325 to have a more specific match, such as different map entries for
1326 IPv6:0:0 vs IPv6:0. This change requires that configuration
1327 data (including maps, files, classes, custom ruleset, etc.) must
1328 use the same format, so make certain such configuration data is
1329 upgrading. As a very simple check search for patterns like
1330 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1331 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1332 the cf option UseCompressedIPv6Addresses.
1335 The default kernel entropy-processing algorithm is now
1336 Fortuna, replacing Yarrow.
1338 Assuming you have 'device random' in your kernel config
1339 file, the configurations allow a kernel option to override
1340 this default. You may choose *ONE* of:
1342 options RANDOM_YARROW # Legacy /dev/random algorithm.
1343 options RANDOM_DUMMY # Blocking-only driver.
1345 If you have neither, you get Fortuna. For most people,
1346 read no further, Fortuna will give a /dev/random that works
1347 like it always used to, and the difference will be irrelevant.
1349 If you remove 'device random', you get *NO* kernel-processed
1350 entropy at all. This may be acceptable to folks building
1351 embedded systems, but has complications. Carry on reading,
1352 and it is assumed you know what you need.
1354 *PLEASE* read random(4) and random(9) if you are in the
1355 habit of tweaking kernel configs, and/or if you are a member
1356 of the embedded community, wanting specific and not-usual
1357 behaviour from your security subsystems.
1359 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1360 random', you will NOT have a functioning /dev/random, and
1361 many cryptographic features will not work, including SSH.
1362 You may also find strange behaviour from the random(3) set
1363 of library functions, in particular sranddev(3), srandomdev(3)
1364 and arc4random(3). The reason for this is that the KERN_ARND
1365 sysctl only returns entropy if it thinks it has some to
1366 share, and with RANDOM_DUMMY or no 'device random' this
1370 An additional fix for the issue described in the 20150614 sendmail
1371 entry below has been committed in revision 284717.
1374 FreeBSD's old make (fmake) has been removed from the system. It is
1375 available as the devel/fmake port or via pkg install fmake.
1378 The fix for the issue described in the 20150614 sendmail entry
1379 below has been committed in revision 284436. The work
1380 around described in that entry is no longer needed unless the
1381 default setting is overridden by a confDH_PARAMETERS configuration
1382 setting of '5' or pointing to a 512 bit DH parameter file.
1385 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1386 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1387 and devel/kyua to version 0.20+ and adjust any calling code to work
1388 with Kyuafile and kyua.
1391 The import of openssl to address the FreeBSD-SA-15:10.openssl
1392 security advisory includes a change which rejects handshakes
1393 with DH parameters below 768 bits. sendmail releases prior
1394 to 8.15.2 (not yet released), defaulted to a 512 bit
1395 DH parameter setting for client connections. To work around
1396 this interoperability, sendmail can be configured to use a
1397 2048 bit DH parameter by:
1399 1. Edit /etc/mail/`hostname`.mc
1400 2. If a setting for confDH_PARAMETERS does not exist or
1401 exists and is set to a string beginning with '5',
1402 replace it with '2'.
1403 3. If a setting for confDH_PARAMETERS exists and is set to
1404 a file path, create a new file with:
1405 openssl dhparam -out /path/to/file 2048
1406 4. Rebuild the .cf file:
1407 cd /etc/mail/; make; make install
1408 5. Restart sendmail:
1409 cd /etc/mail/; make restart
1411 A sendmail patch is coming, at which time this file will be
1415 Generation of legacy formatted entries have been disabled by default
1416 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1417 entries were converted to use the new format by default when the new,
1418 machine independent format have been added and supported since FreeBSD
1421 Please see the pwd_mkdb(8) manual page for further details.
1424 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1425 20141231 entry below for information about prerequisites and upgrading,
1426 if you are not already using 3.5.0 or higher.
1429 TI platform code switched to using vendor DTS files and this update
1430 may break existing systems running on Beaglebone, Beaglebone Black,
1433 - dtb files should be regenerated/reinstalled. Filenames are the
1434 same but content is different now
1435 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1436 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1437 addressing scheme is now pin 25 on /dev/gpioc3.
1438 - Pandaboard: /etc/ttys should be updated, serial console device is
1439 now /dev/ttyu2, not /dev/ttyu0
1442 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1443 If you need the GNU extension from groff soelim(1), install groff
1444 from package: pkg install groff, or via ports: textproc/groff.
1447 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1448 defined in symlink(7); previously symlinks were silently ignored.
1451 The const qualifier has been removed from iconv(3) to comply with
1452 POSIX. The ports tree is aware of this from r384038 onwards.
1455 Libraries specified by LIBADD in Makefiles must have a corresponding
1456 DPADD_<lib> variable to ensure correct dependencies. This is now
1457 enforced in src.libnames.mk.
1460 From legacy ata(4) driver was removed support for SATA controllers
1461 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1462 Kernel modules ataahci and ataadaptec were removed completely,
1463 replaced by ahci and mvs modules respectively.
1466 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1467 the 20141231 entry below for information about prerequisites and
1468 upgrading, if you are not already using 3.5.0 or higher.
1471 The 32-bit PowerPC kernel has been changed to a position-independent
1472 executable. This can only be booted with a version of loader(8)
1473 newer than January 31, 2015, so make sure to update both world and
1474 kernel before rebooting.
1477 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1478 but before r278950, the RNG was not seeded properly. Immediately
1479 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1480 ssh keys or openssl keys) that were generated w/ a kernel from that
1481 range. This does not affect programs that directly used /dev/random
1482 or /dev/urandom. All userland uses of arc4random(3) are affected.
1485 The autofs(4) ABI was changed in order to restore binary compatibility
1486 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1487 with the new kernel.
1490 The powerpc64 kernel has been changed to a position-independent
1491 executable. This can only be booted with a new version of loader(8),
1492 so make sure to update both world and kernel before rebooting.
1495 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1496 only release, no new features have been added. Please see the 20141231
1497 entry below for information about prerequisites and upgrading, if you
1498 are not already using 3.5.0.
1501 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1502 taken from the ELF Tool Chain project rather than GNU binutils. They
1503 should be drop-in replacements, with the addition of arm64 support.
1504 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1505 binutils tools, if necessary. See 20150805 for updated information.
1508 The default Unbound configuration now enables remote control
1509 using a local socket. Users who have already enabled the
1510 local_unbound service should regenerate their configuration
1511 by running "service local_unbound setup" as root.
1514 The GNU texinfo and GNU info pages have been removed.
1515 To be able to view GNU info pages please install texinfo from ports.
1518 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1520 As of this release, a prerequisite for building clang, llvm and lldb is
1521 a C++11 capable compiler and C++11 standard library. This means that to
1522 be able to successfully build the cross-tools stage of buildworld, with
1523 clang as the bootstrap compiler, your system compiler or cross compiler
1524 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1525 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1528 On any standard FreeBSD 10.x or 11.x installation, where clang and
1529 libc++ are on by default (that is, on x86 or arm), this should work out
1532 On 9.x installations where clang is enabled by default, e.g. on x86 and
1533 powerpc, libc++ will not be enabled by default, so libc++ should be
1534 built (with clang) and installed first. If both clang and libc++ are
1535 missing, build clang first, then use it to build libc++.
1537 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1538 the instructions for 9.x above.
1540 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1541 default, and do not build clang.
1543 Many embedded systems are resource constrained, and will not be able to
1544 build clang in a reasonable time, or in some cases at all. In those
1545 cases, cross building bootable systems on amd64 is a workaround.
1547 This new version of clang introduces a number of new warnings, of which
1548 the following are most likely to appear:
1552 This warns in two cases, for both C and C++:
1553 * When the code is trying to take the absolute value of an unsigned
1554 quantity, which is effectively a no-op, and almost never what was
1555 intended. The code should be fixed, if at all possible. If you are
1556 sure that the unsigned quantity can be safely cast to signed, without
1557 loss of information or undefined behavior, you can add an explicit
1558 cast, or disable the warning.
1560 * When the code is trying to take an absolute value, but the called
1561 abs() variant is for the wrong type, which can lead to truncation.
1562 If you want to disable the warning instead of fixing the code, please
1563 make sure that truncation will not occur, or it might lead to unwanted
1566 -Wtautological-undefined-compare and
1567 -Wundefined-bool-conversion
1569 These warn when C++ code is trying to compare 'this' against NULL, while
1570 'this' should never be NULL in well-defined C++ code. However, there is
1571 some legacy (pre C++11) code out there, which actively abuses this
1572 feature, which was less strictly defined in previous C++ versions.
1574 Squid and openjdk do this, for example. The warning can be turned off
1575 for C++98 and earlier, but compiling the code in C++11 mode might result
1576 in unexpected behavior; for example, the parts of the program that are
1577 unreachable could be optimized away.
1580 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1581 kernel sources have been removed. The .h files remain, since some
1582 utilities include them. This will need to be fixed later.
1583 If "mount -t oldnfs ..." is attempted, it will fail.
1584 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1585 the utilities will report errors.
1588 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1589 directories to top level SUBDIR variable when their parent
1590 directory is included in LOCAL_DIRS. Users with build systems with
1591 such hierarchies and without SUBDIR entries in the parent
1592 directory Makefiles should add them or add the directories to
1596 faith(4) and faithd(8) have been removed from the base system. Faith
1597 has been obsolete for a very long time.
1600 vt(4), the new console driver, is enabled by default. It brings
1601 support for Unicode and double-width characters, as well as
1602 support for UEFI and integration with the KMS kernel video
1605 You may need to update your console settings in /etc/rc.conf,
1606 most probably the keymap. During boot, /etc/rc.d/syscons will
1607 indicate what you need to do.
1609 vt(4) still has issues and lacks some features compared to
1610 syscons(4). See the wiki for up-to-date information:
1611 https://wiki.freebsd.org/Newcons
1613 If you want to keep using syscons(4), you can do so by adding
1614 the following line to /boot/loader.conf:
1618 pjdfstest has been integrated into kyua as an opt-in test suite.
1619 Please see share/doc/pjdfstest/README for more details on how to
1623 gperf has been removed from the base system for architectures
1624 that use clang. Ports that require gperf will obtain it from the
1628 pjdfstest has been moved from tools/regression/pjdfstest to
1632 At svn r271982, The default linux compat kernel ABI has been adjusted
1633 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1634 update. If you wish to continue using the linux-f10 compat ports,
1635 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1636 encouraged to update their linux-compat packages to linux-c6 during
1637 their next update cycle.
1640 The ofwfb driver, used to provide a graphics console on PowerPC when
1641 using vt(4), no longer allows mmap() of all physical memory. This
1642 will prevent Xorg on PowerPC with some ATI graphics cards from
1643 initializing properly unless x11-servers/xorg-server is updated to
1647 The xdev targets have been converted to using TARGET and
1648 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1651 The default unbound configuration has been modified to address
1652 issues with reverse lookups on networks that use private
1653 address ranges. If you use the local_unbound service, run
1654 "service local_unbound setup" as root to regenerate your
1655 configuration, then "service local_unbound reload" to load the
1659 The GNU texinfo and GNU info pages are not built and installed
1660 anymore, WITH_INFO knob has been added to allow to built and install
1662 UPDATE: see 20150102 entry on texinfo's removal
1665 The GNU readline library is now an INTERNALLIB - that is, it is
1666 statically linked into consumers (GDB and variants) in the base
1667 system, and the shared library is no longer installed. The
1668 devel/readline port is available for third party software that
1672 The Itanium architecture (ia64) has been removed from the list of
1673 known architectures. This is the first step in the removal of the
1677 Commit r268115 has added NFSv4.1 server support, merged from
1678 projects/nfsv4.1-server. Since this includes changes to the
1679 internal interfaces between the NFS related modules, a full
1680 build of the kernel and modules will be necessary.
1681 __FreeBSD_version has been bumped.
1684 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1685 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1686 which differs from the behaviour controlled by this knob.)
1689 Maximal length of the serial number in CTL was increased from 16 to
1690 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1691 and ctld, need to be rebuilt to work with a new kernel.
1694 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1695 1 respectively to match the upstream numbers. They were out of
1696 sync because, when they were originally added to FreeBSD, the
1697 upstream versions were not respected. These libraries are private
1698 and not yet built by default, so renumbering them should be a
1699 non-issue. However, unclean source trees will yield broken test
1700 programs once the operator executes "make delete-old-libs" after a
1701 "make installworld".
1703 Additionally, the atf-sh binary was made private by moving it into
1704 /usr/libexec/. Already-built shell test programs will keep the
1705 path to the old binary so they will break after "make delete-old"
1708 If you are using WITH_TESTS=yes (not the default), wipe the object
1709 tree and rebuild from scratch to prevent spurious test failures.
1710 This is only needed once: the misnumbered libraries and misplaced
1711 binaries have been added to OptionalObsoleteFiles.inc so they will
1712 be removed during a clean upgrade.
1715 Clang and llvm have been upgraded to 3.4.1 release.
1718 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1719 be removed to avoid issues in the future (and has been added to
1723 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1724 past, it affected all builds that used the bsd.*.mk files. The old
1725 behavior was a bug, but people may have relied upon it. To get this
1726 behavior back, you can .include /etc/src.conf from /etc/make.conf
1727 (which is still global and isn't changed). This also changes the
1728 behavior of incremental builds inside the tree of individual
1729 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1730 Although this has survived make universe and some upgrade scenarios,
1731 other upgrade scenarios may have broken. At least one form of
1732 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1733 as well... In cases where MAKESYSPATH isn't working with this
1734 setting, you'll need to set it to the full path to your tree.
1736 One side effect of all this cleaning up is that bsd.compiler.mk
1737 is no longer implicitly included by bsd.own.mk. If you wish to
1738 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1742 The lindev device has been removed since /dev/full has been made a
1743 standard device. __FreeBSD_version has been bumped.
1746 The knob WITHOUT_VI was added to the base system, which controls
1747 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1748 in order to reorder files share/termcap and didn't build ex(1) as a
1749 build tool, so building/installing with WITH_VI is highly advised for
1750 build hosts for older releases.
1752 This issue has been fixed in stable/9 and stable/10 in r277022 and
1753 r276991, respectively.
1756 The YES_HESIOD knob has been removed. It has been obsolete for
1757 a decade. Please move to using WITH_HESIOD instead or your builds
1758 will silently lack HESIOD.
1761 The uart(4) driver has been changed with respect to its handling
1762 of the low-level console. Previously the uart(4) driver prevented
1763 any process from changing the baudrate or the CLOCAL and HUPCL
1764 control flags. By removing the restrictions, operators can make
1765 changes to the serial console port without having to reboot.
1766 However, when getty(8) is started on the serial device that is
1767 associated with the low-level console, a misconfigured terminal
1768 line in /etc/ttys will now have a real impact.
1769 Before upgrading the kernel, make sure that /etc/ttys has the
1770 serial console device configured as 3wire without baudrate to
1771 preserve the previous behaviour. E.g:
1772 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1775 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1776 to improve performance. To re-enable it, if needed, run rpcbind
1777 with command line option -W.
1780 Switched back to the GPL dtc compiler due to updates in the upstream
1781 dts files not being supported by the BSDL dtc compiler. You will need
1782 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1783 may result while building dtb files during a kernel build if you fail
1784 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1787 Clang and llvm have been upgraded to 3.4 release.
1790 The nve(4) driver has been removed. Please use the nfe(4) driver
1791 for NVIDIA nForce MCP Ethernet adapters instead.
1794 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1795 This could cause certain C++ applications using shared libraries built
1796 against the previous version of libc++ to crash. The incompatibility
1797 has now been fixed, but any C++ applications or shared libraries built
1798 between r261283 and r261801 should be recompiled.
1801 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1802 capability mode support. Please note that enabling the feature in
1803 kernel is still highly recommended.
1806 OpenSSH is now built with sandbox support, and will use sandbox as
1807 the default privilege separation method. This requires Capsicum
1808 capability mode support in kernel.
1811 The libelf and libdwarf libraries have been updated to newer
1812 versions from upstream. Shared library version numbers for
1813 these two libraries were bumped. Any ports or binaries
1814 requiring these two libraries should be recompiled.
1815 __FreeBSD_version is bumped to 1100006.
1818 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1819 instead of providing an explicit one, this would prevent such
1820 Makefile from providing its own Kyuafile in the future during
1821 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1822 intervention is needed to clean an objdir if you use NO_CLEAN:
1823 # find /usr/obj -name Kyuafile | xargs rm -f
1826 The behavior of gss_pseudo_random() for the krb5 mechanism
1827 has changed, for applications requesting a longer random string
1828 than produced by the underlying enctype's pseudo-random() function.
1829 In particular, the random string produced from a session key of
1830 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1831 be different at the 17th octet and later, after this change.
1832 The counter used in the PRF+ construction is now encoded as a
1833 big-endian integer in accordance with RFC 4402.
1834 __FreeBSD_version is bumped to 1100004.
1837 The WITHOUT_ATF build knob has been removed and its functionality
1838 has been subsumed into the more generic WITHOUT_TESTS. If you were
1839 using the former to disable the build of the ATF libraries, you
1840 should change your settings to use the latter.
1843 The default version of mtree is nmtree which is obtained from
1844 NetBSD. The output is generally the same, but may vary
1845 slightly. If you found you need identical output adding
1846 "-F freebsd9" to the command line should do the trick. For the
1847 time being, the old mtree is available as fmtree.
1850 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1851 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1852 1.1.4_8 and verify bsdyml not linked in, before running "make
1854 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1856 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1859 The stable/10 branch has been created in subversion from head
1866 Avoid using make -j when upgrading. While generally safe, there are
1867 sometimes problems using -j to upgrade. If your upgrade fails with
1868 -j, please try again without -j. From time to time in the past there
1869 have been problems using -j with buildworld and/or installworld. This
1870 is especially true when upgrading between "distant" versions (eg one
1871 that cross a major release boundary or several minor releases, or when
1872 several months have passed on the -current branch).
1874 Sometimes, obscure build problems are the result of environment
1875 poisoning. This can happen because the make utility reads its
1876 environment when searching for values for global variables. To run
1877 your build attempts in an "environmental clean room", prefix all make
1878 commands with 'env -i '. See the env(1) manual page for more details.
1880 When upgrading from one major version to another it is generally best to
1881 upgrade to the latest code in the currently installed branch first, then
1882 do an upgrade to the new branch. This is the best-tested upgrade path,
1883 and has the highest probability of being successful. Please try this
1884 approach if you encounter problems with a major version upgrade. Since
1885 the stable 4.x branch point, one has generally been able to upgrade from
1886 anywhere in the most recent stable branch to head / current (or even the
1887 last couple of stable branches). See the top of this file when there's
1890 When upgrading a live system, having a root shell around before
1891 installing anything can help undo problems. Not having a root shell
1892 around can lead to problems if pam has changed too much from your
1893 starting point to allow continued authentication after the upgrade.
1895 This file should be read as a log of events. When a later event changes
1896 information of a prior event, the prior event should not be deleted.
1897 Instead, a pointer to the entry with the new information should be
1898 placed in the old entry. Readers of this file should also sanity check
1899 older entries before relying on them blindly. Authors of new entries
1900 should write them with this in mind.
1904 When upgrading the boot ZFS pool to a new version, always follow
1907 1.) recompile and reinstall the ZFS boot loader and boot block
1908 (this is part of "make buildworld" and "make installworld")
1910 2.) update the ZFS boot block on your boot drive
1912 The following example updates the ZFS boot block on the first
1913 partition (freebsd-boot) of a GPT partitioned drive ada0:
1914 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1916 Non-boot pools do not need these updates.
1920 If you are updating from a prior version of FreeBSD (even one just
1921 a few days old), you should follow this procedure. It is the most
1922 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1924 make kernel-toolchain
1925 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1926 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1928 To test a kernel once
1929 ---------------------
1930 If you just want to boot a kernel once (because you are not sure
1931 if it works, or if you want to boot a known bad kernel to provide
1932 debugging information) run
1933 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1934 nextboot -k testkernel
1936 To rebuild everything and install it on the current system.
1937 -----------------------------------------------------------
1938 # Note: sometimes if you are running current you gotta do more than
1939 # is listed here if you are upgrading from a really old current.
1941 <make sure you have good level 0 dumps>
1943 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1944 make installkernel KERNCONF=YOUR_KERNEL_HERE
1946 <reboot in single user> [3]
1953 To cross-install current onto a separate partition
1954 --------------------------------------------------
1955 # In this approach we use a separate partition to hold
1956 # current's root, 'usr', and 'var' directories. A partition
1957 # holding "/", "/usr" and "/var" should be about 2GB in
1960 <make sure you have good level 0 dumps>
1963 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1964 <maybe newfs current's root partition>
1965 <mount current's root partition on directory ${CURRENT_ROOT}>
1966 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1967 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1968 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1969 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1970 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1971 <reboot into current>
1972 <do a "native" rebuild/install as described in the previous section>
1973 <maybe install compatibility libraries from ports/misc/compat*>
1977 To upgrade in-place from stable to current
1978 ----------------------------------------------
1979 <make sure you have good level 0 dumps>
1981 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1982 make installkernel KERNCONF=YOUR_KERNEL_HERE
1984 <reboot in single user> [3]
1991 Make sure that you've read the UPDATING file to understand the
1992 tweaks to various things you need. At this point in the life
1993 cycle of current, things change often and you are on your own
1994 to cope. The defaults can also change, so please read ALL of
1995 the UPDATING entries.
1997 Also, if you are tracking -current, you must be subscribed to
1998 freebsd-current@freebsd.org. Make sure that before you update
1999 your sources that you have read and understood all the recent
2000 messages there. If in doubt, please track -stable which has
2001 much fewer pitfalls.
2003 [1] If you have third party modules, such as vmware, you
2004 should disable them at this point so they don't crash your
2007 [3] From the bootblocks, boot -s, and then do
2011 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2012 cd src # full path to source
2013 adjkerntz -i # if CMOS is wall time
2014 Also, when doing a major release upgrade, it is required that
2015 you boot into single user mode to do the installworld.
2017 [4] Note: This step is non-optional. Failure to do this step
2018 can result in a significant reduction in the functionality of the
2019 system. Attempting to do it by hand is not recommended and those
2020 that pursue this avenue should read this file carefully, as well
2021 as the archives of freebsd-current and freebsd-hackers mailing lists
2022 for potential gotchas. The -U option is also useful to consider.
2023 See mergemaster(8) for more information.
2025 [5] Usually this step is a no-op. However, from time to time
2026 you may need to do this if you get unknown user in the following
2027 step. It never hurts to do it all the time. You may need to
2028 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2029 install) after the buildworld before this step if you last updated
2030 from current before 20130425 or from -stable before 20130430.
2032 [6] This only deletes old files and directories. Old libraries
2033 can be deleted by "make delete-old-libs", but you have to make
2034 sure that no program is using those libraries anymore.
2036 [8] The new kernel must be able to run existing binaries used by an
2037 installworld. When upgrading across major versions, the new kernel's
2038 configuration must include the correct COMPAT_FREEBSD<n> option for
2039 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2040 to do so may leave you with a system that is hard to boot to recover. A
2041 GENERIC kernel will include suitable compatibility options to run
2042 binaries from older branches. Note that the ability to run binaries
2043 from unsupported branches is not guaranteed.
2045 Make sure that you merge any new devices from GENERIC since the
2046 last time you updated your kernel config file. Options also
2047 change over time, so you may need to adjust your custom kernels
2050 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2051 "?=" instead of the "=" assignment operator, so that buildworld can
2052 override the CPUTYPE if it needs to.
2054 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2055 not on the command line, or in /etc/make.conf. buildworld will
2056 warn if it is improperly defined.
2059 This file contains a list, in reverse chronological order, of major
2060 breakages in tracking -current. It is not guaranteed to be a complete
2061 list of such breakages, and only contains entries since September 23, 2011.
2062 If you need to see UPDATING entries from before that date, you will need
2063 to fetch an UPDATING file from an older FreeBSD release.
2065 Copyright information:
2067 Copyright 1998-2009 M. Warner Losh.
2069 Redistribution, publication, translation and use, with or without
2070 modification, in full or in part, in any form or format of this
2071 document are permitted without further permission from the author.
2073 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2074 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2075 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2076 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2077 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2078 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2079 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2080 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2081 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2082 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2083 POSSIBILITY OF SUCH DAMAGE.
2085 Contact Warner Losh if you have any questions about your use of