1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
20 FreeBSD 13.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
36 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
37 been removed from mount_fusefs(8). You can safely remove them from
38 your scripts, because they had no effect.
40 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize, and
41 vfs.fusefs.refresh_size sysctls have been removed. If you felt the
42 need to set any of them to a non-default value, please tell
43 asomers@FreeBSD.org why.
46 The IPSEC option has been removed from GENERIC. Users requiring
47 ipsec(4) must now load the ipsec(4) kernel module.
50 The tap(4) driver has been folded into tun(4), and the module has been
51 renamed to tuntap. You should update any kld_load="if_tap" or
52 kld_load="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
53 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
54 module instead, and "device tap" or "device tun" entries in kernel
55 config files to select the tuntap device instead.
58 The following knobs have been added related to tradeoffs between
59 safe use of the random device and availability in the absence of
62 kern.random.initial_seeding.bypass_before_seeding: tunable; set
63 non-zero to bypass the random device prior to seeding, or zero to
64 block random requests until the random device is initially seeded.
65 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
66 availability properties.
68 kern.random.initial_seeding.read_random_bypassed_before_seeding:
69 read-only diagnostic sysctl that is set when bypass is enabled and
70 read_random(9) is bypassed, to enable programmatic handling of this
71 initial condition, if desired.
73 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
74 Similar to the above, but for for arc4random(9) initial seeding.
76 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
77 non-zero to disable warnings in dmesg when the same conditions are
78 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
79 produce warnings in dmesg when the conditions are met.
82 The tunable "security.stack_protect.permit_nonrandom_cookies" may be
83 set to a non-zero value to boot systems that do not provide early
84 entropy. Otherwise, such systems may see the panic message:
85 "cannot initialize stack cookies because random device is not yet
89 The loadable random module KPI has changed; the random_infra_init()
90 routine now requires a 3rd function pointer for a bool (*)(void)
91 method that returns true if the random device is seeded (and
95 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
96 built from head sources between r320757 (July 6, 2017) and
97 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
98 is added to the command line.
99 nfsuserd daemons built from head sources that are post-r338192 are
100 not affected and should continue to work.
103 The fuse(4) module has been renamed to fusefs(4) for consistency with
104 other filesystems. You should update any kld_load="fuse" entries in
105 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
106 "options FUSE" entries in kernel config files.
109 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
110 8.0.0. Please see the 20141231 entry below for information about
111 prerequisites and upgrading, if you are not already using clang 3.5.0
115 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
116 compiled into your custom kernel, add 'device xz' statement to the
120 drm and drm2 have been removed from the tree. Please see
121 https://wiki.freebsd.org/Graphics for the latest information on
122 migrating to the drm ports.
125 Iflib is no longer unconditionally compiled into the kernel. Drivers
126 using iflib and statically compiled into the kernel, now require
127 the 'device iflib' config option. For the same drivers loaded as
128 modules on kernels not having 'device iflib', the iflib.ko module
129 is loaded automatically.
132 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
133 options no longer exist since r343219 and r343427 respectively;
134 nothing uses them, so they should be just removed from custom
138 r342635 changes the way efibootmgr(8) works by requiring users to add
139 the -b (bootnum) parameter for commands where the bootnum was previously
140 specified with each option. For example 'efibootmgr -B 0001' is now
141 'efibootmgr -B -b 0001'.
144 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
145 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
146 servers that have vfs.nfsd.nfs_privport set will only allow mounts
147 from clients using a reserved port#. Since both the FreeBSD and Linux
148 NFSv4 clients use reserved port#s by default, this should not affect
152 The XLP config has been removed. We can't support 64-bit atomics in this
153 kernel because it is running in 32-bit mode. XLP users must transition
154 to running a 64-bit kernel (XLP64 or XLPN32).
156 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
157 the preferred emulator today and we don't need two different ones.
159 The old sibyte / swarm / Broadcom BCM1250 support has been
160 removed from the mips port.
163 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
164 7.0.1. Please see the 20141231 entry below for information about
165 prerequisites and upgrading, if you are not already using clang 3.5.0
169 Remove the timed and netdate programs from the base tree. Setting
170 the time with these daemons has been obsolete for over a decade.
173 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
174 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
175 it produces broken binaries when ifuncs are in use. Users needing
176 GNU ld should install the binutils port or package.
179 The BSD crtbegin and crtend code has been enabled by default. It has
180 had extensive testing on amd64, arm64, and i386. It can be disabled
181 by building a world with -DWITHOUT_BSD_CRTBEGIN.
184 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
185 has been converted to a port (misc/ctm) and will be removed from
186 FreeBSD-13. It is available as a package (ctm) for all supported
190 The default newsyslog.conf(5) file has been changed to only include
191 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
192 the filenames end in '.conf' and do not begin with a '.'.
194 You should check the configuration files in these two directories match
195 this naming convention. You can verify which configuration files are
196 being included using the command:
200 Ports for the DRM modules have been simplified. Now, amd64 users should
201 just install the drm-kmod port. All others should install
204 Graphics hardware that's newer than about 2010 usually works with
205 drm-kmod. For hardware older than 2013, however, some users will need
206 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
207 than 2008 usually only works in drm-legacy-kmod. The graphics team can
208 only commit to hardware made since 2013 due to the complexity of the
209 market and difficulty to test all the older cards effectively. If you
210 have hardware supported by drm-kmod, you are strongly encouraged to use
211 that as you will get better support.
213 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
214 elsewhere, the drm and drm2 modules will be eliminated from the src base
215 soon (with a limited exception for arm). Please update to the package
216 asap and report any issues to x11@freebsd.org.
218 Generally, anybody using the drm*-kmod packages should add
219 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
220 cross-threading surprises, especially with automatic driver
221 loading from X11 startup. These will become the defaults in 13-current
225 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
226 custom kernel and module loading configuration files must be updated
227 accordingly. Moreover, interfaces previous presented as ixlvN to the
228 system are now exposed as iavfN and network configuration files must
229 be adjusted as necessary.
232 OpenSSL has been updated to version 1.1.1. This update included
233 additional various API changes throughout the base system. It is
234 important to rebuild third-party software after upgrading. The value
235 of __FreeBSD_version has been bumped accordingly.
238 The legacy DRM modules and drivers have now been added to the loader's
239 module blacklist, in favor of loading them with kld_list in rc.conf(5).
240 The module blacklist may be overridden with the loader.conf(5)
241 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
245 The cam(4) based nda(4) driver will be used over nvd(4) by default on
246 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
247 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
248 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
252 Reproducible build mode is now on by default, in preparation for
253 FreeBSD 12.0. This eliminates build metadata such as the user,
254 host, and time from the kernel (and uname), unless the working tree
255 corresponds to a modified checkout from a version control system.
256 The previous behavior can be obtained by setting the /etc/src.conf
257 knob WITHOUT_REPRODUCIBLE_BUILD.
260 The Yarrow CSPRNG has been removed from the kernel as it has not been
261 supported by its designers since at least 2003. Fortuna has been the
262 default since FreeBSD-11.
265 devctl freeze/thaw have gone into the tree, the rc scripts have been
266 updated to use them and devmatch has been changed. You should update
267 kernel, userland and rc scripts all at the same time.
270 The default interpreter has been switched from 4th to Lua.
271 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
272 interpreter. If you have custom FORTH code you will need to set
273 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
274 src.conf for the build. This will create default hard links between
275 loader and loader_4th instead of loader and loader_lua, the new default.
276 If you are using UEFI it will create the proper hard link to loader.efi.
278 bhyve uses userboot.so. It remains 4th-only until some issues are solved
279 regarding coexisting with multiple versions of FreeBSD are resolved.
282 ls(1) now respects the COLORTERM environment variable used in other
283 systems and software to indicate that a colored terminal is both
284 supported and desired. If ls(1) is suddenly emitting colors, they may
285 be disabled again by either removing the unwanted COLORTERM from your
286 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
287 may not be observed in a future release.
290 The default pager for most commands has been changed to "less". To
291 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
295 The jedec_ts(4) driver has been removed. A superset of its functionality
296 is available in the jedec_dimm(4) driver, and the manpage for that
297 driver includes migration instructions. If you have "device jedec_ts"
298 in your kernel configuration file, it must be removed.
301 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
302 This should have no effect if the kernel is booted via BIOS/legacy boot.
303 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
304 has a buggy firmware that prevents a successful boot due to use of
308 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
309 support has been removed from the tree. These ports were
310 obsolete and/or known to be broken for many years.
313 loader.efi has been augmented to participate more fully in the
314 UEFI boot manager protocol. loader.efi will now look at the
315 BootXXXX environment variable to determine if a specific kernel
316 or root partition was specified. XXXX is derived from BootCurrent.
317 efibootmgr(8) manages these standard UEFI variables.
320 zfsloader's functionality has now been folded into loader.
321 zfsloader is no longer necessary once you've updated your
322 boot blocks. For a transition period, we will install a
323 hardlink for zfsloader to loader to allow a smooth transition
324 until the boot blocks can be updated (hard link because old
325 zfs boot blocks don't understand symlinks).
328 ARM64 now have efifb support, if you want to have serial console
329 on your arm64 board when an screen is connected and the bootloader
330 setup a frame buffer for us to use, just add :
334 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
335 an screen connected as the firmware will setup a frame buffer are that
336 u-boot will expose as an EFI frame buffer.
339 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
340 or take steps to update /etc/passwd before doing installworld on
341 existing systems. Do not skip the "mergemaster -Fp" step before
342 installworld, as described in the update procedures near the bottom
343 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
344 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
345 the ntp config file contain options that change file/dir locations.
346 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
347 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
348 taking steps to ensure that all required files/dirs are accessible
352 Big endian arm support has been removed.
355 The static environment setup in kernel configs is no longer mutually
356 exclusive with the loader(8) environment by default. In order to
357 restore the previous default behavior of disabling the loader(8)
358 environment if a static environment is present, you must specify
359 loader_env.disabled=1 in the static environment.
362 The ABI of syscalls used by management tools like sockstat and
363 netstat has been broken to allow 32-bit binaries to work on
364 64-bit kernels without modification. These programs will need
365 to match the kernel in order to function. External programs may
366 require minor modifications to accommodate a change of type in
367 structures from pointers to 64-bit virtual addresses.
370 On i386 and amd64 atomics are now inlined. Out of tree modules using
371 atomics will need to be rebuilt.
374 The '%I' format in the kern.corefile sysctl limits the number of
375 core files that a process can generate to the number stored in the
376 debug.ncores sysctl. The '%I' format is replaced by the single digit
377 index. Previously, if all indexes were taken the kernel would overwrite
378 only a core file with the highest index in a filename.
379 Currently the system will create a new core file if there is a free
380 index or if all slots are taken it will overwrite the oldest one.
383 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
384 6.0.1. Please see the 20141231 entry below for information about
385 prerequisites and upgrading, if you are not already using clang 3.5.0
389 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
390 needed to be changed to work with it. This change was made with r335763
391 and requires a mergemaster / etcupdate / etc to update the installed
395 r334930 changed the interface between the NFS modules, so they all
396 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
399 As of r334391 lld is the default amd64 system linker; it is installed
400 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
404 The kernel / userland interface for devinfo changed, so you'll
405 need a new kernel and userland as a pair for it to work (rebuilding
406 lib/libdevinfo is all that's required). devinfo and devmatch will
407 not work, but everything else will when there's a mismatch.
410 The on-disk format for hwpmc callchain records has changed to include
411 threadid corresponding to a given record. This changes the field offsets
412 and thus requires that libpmcstat be rebuilt before using a kernel
416 The vxge(4) driver has been removed. This driver was introduced into
417 HEAD one week before the Exar left the Ethernet market and is not
418 known to be used. If you have device vxge in your kernel config file
422 The amd64 kernel now requires a ld that supports ifunc to produce a
423 working kernel, either lld or a newer binutils. lld is built by default
424 on amd64, and the 'buildkernel' target uses it automatically. However,
425 it is not the default linker, so building the kernel the traditional
426 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
427 binutils port/package). lld will soon be default, and this requirement
430 NOTE: As of r334391 lld is the default system linker on amd64, and no
431 workaround is necessary.
434 The nxge(4) driver has been removed. This driver was for PCI-X 10g
435 cards made by s2io/Neterion. The company was acquired by Exar and
436 no longer sells or supports Ethernet products. If you have device
437 nxge in your kernel config file it must be removed.
440 The tz database (tzdb) has been updated to 2018e. This version more
441 correctly models time stamps in time zones with negative DST such as
442 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
443 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
444 time zone abbreviations and the tm_isdst flag.
447 The ixgb(4) driver has been removed. This driver was for an early and
448 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
449 quickly shifted to the long lived ixgbe family. If you have device
450 ixgb in your kernel config file it must be removed.
453 The lmc(4) driver has been removed. This was a WAN interface
454 card that was already reportedly rare in 2003, and had an ambiguous
455 license. If you have device lmc in your kernel config file it must
459 Support for Arcnet networks has been removed. If you have device
460 arcnet or device cm in your kernel config file they must be
464 Support for FDDI networks has been removed. If you have device
465 fddi or device fpa in your kernel config file they must be
469 In addition to supporting RFC 3164 formatted messages, the
470 syslogd(8) service is now capable of parsing RFC 5424 formatted
471 log messages. The main benefit of using RFC 5424 is that clients
472 may now send log messages with timestamps containing year numbers,
473 microseconds and time zone offsets.
475 Similarly, the syslog(3) C library function has been altered to
476 send RFC 5424 formatted messages to the local system logging
477 daemon. On systems using syslogd(8), this change should have no
478 negative impact, as long as syslogd(8) and the C library are
479 updated at the same time. On systems using a different system
480 logging daemon, it may be necessary to make configuration
481 adjustments, depending on the software used.
483 When using syslog-ng, add the 'syslog-protocol' flag to local
484 input sources to enable parsing of RFC 5424 formatted messages:
487 unix-dgram("/var/run/log" flags(syslog-protocol));
490 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
491 of the 'imuxsock' module to let messages be processed by the
492 regular RFC 3164/5424 parsing pipeline:
494 module(load="imuxsock" SysSock.UseSpecialParser="off")
496 Do note that these changes only affect communication between local
497 applications and syslogd(8). The format that syslogd(8) uses to
498 store messages on disk or forward messages to other systems
499 remains unchanged. syslogd(8) still uses RFC 3164 for these
500 purposes. Options to customize this behaviour will be added in the
501 future. Utilities that process log files stored in /var/log are
502 thus expected to continue to function as before.
504 __FreeBSD_version has been incremented to 1200061 to denote this
508 Support for token ring networks has been removed. If you
509 have "device token" in your kernel config you should remove
510 it. No device drivers supported token ring.
513 makefs was modified to be able to tag ISO9660 El Torito boot catalog
514 entries as EFI instead of overloading the i386 tag as done previously.
515 The amd64 mkisoimages.sh script used to build amd64 ISO images for
516 release was updated to use this. This may mean that makefs must be
517 updated before "make cdrom" can be run in the release directory. This
518 should be as simple as:
520 $ cd $SRCDIR/usr.sbin/makefs
521 $ make depend all install
524 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
525 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
526 Co-existence for the transition period will come shortly. Booting is a
527 complex environment and test coverage for Lua-enabled loaders has been
528 thin, so it would be prudent to assume it might not work and make
529 provisions for backup boot methods.
532 devmatch functionality has been turned on in devd. It will automatically
533 load drivers for unattached devices. This may cause unexpected drivers
534 to be loaded. Please report any problems to current@ and
538 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
539 6.0.0. Please see the 20141231 entry below for information about
540 prerequisites and upgrading, if you are not already using clang 3.5.0
544 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
545 This means it is used to link the kernel and userland libraries and
546 executables, but is not yet installed as /usr/bin/ld by default.
548 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
549 WITHOUT_LLD_BOOTSTRAP=yes
552 On i386, pmtimer has been removed. Its functionality has been folded
553 into apm. It was a no-op on ACPI in current for a while now (but was
554 still needed on i386 in FreeBSD 11 and earlier). Users may need to
555 remove it from kernel config files.
558 The use of RSS hash from the network card aka flowid has been
559 disabled by default for lagg(4) as it's currently incompatible with
560 the lacp and loadbalance protocols.
562 This can be re-enabled by setting the following in loader.conf:
563 net.link.lagg.default_use_flowid="1"
566 The SW_WATCHDOG option is no longer necessary to enable the
567 hardclock-based software watchdog if no hardware watchdog is
568 configured. As before, SW_WATCHDOG will cause the software
569 watchdog to be enabled even if a hardware watchdog is configured.
572 r326887 fixes the issue described in the 20171214 UPDATING entry.
573 r326888 flips the switch back to building GELI support always.
576 r362593 broke ZFS + GELI support for reasons unknown. However,
577 it also broke ZFS support generally, so GELI has been turned off
578 by default as the lesser evil in r326857. If you boot off ZFS and/or
579 GELI, it might not be a good time to update.
582 PowerPC users must update loader(8) by rebuilding world before
583 installing a new kernel, as the protocol connecting them has
584 changed. Without the update, loader metadata will not be passed
585 successfully to the kernel and users will have to enter their
586 root partition at the kernel mountroot prompt to continue booting.
587 Newer versions of loader can boot old kernels without issue.
590 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
591 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
592 to WITH/OUT_LOADER_GELI.
595 The naive and non-compliant support of posix_fallocate(2) in ZFS
596 has been removed as of r325320. The system call now returns EINVAL
597 when used on a ZFS file. Although the new behavior complies with the
598 standard, some consumers are not prepared to cope with it.
599 One known victim is lld prior to r325420.
602 Building in a FreeBSD src checkout will automatically create object
603 directories now rather than store files in the current directory if
604 'make obj' was not ran. Calling 'make obj' is no longer necessary.
605 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
606 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
610 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
611 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
612 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
613 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
614 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
615 The UNIFIED_OBJDIR option is a transitional feature that will be
616 removed for 12.0 release; please migrate to the new format for any
617 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
618 than hardcoding paths.
621 The native-xtools target no longer installs the files by default to the
622 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
623 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
626 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
627 options are changing from controlling the build if defined / undefined
628 to controlling the build with explicit 'yes' or 'no' values. They will
629 shift to WITH/WITHOUT options to match other options in the system.
632 libstand has turned into a private library for sys/boot use only.
633 It is no longer supported as a public interface outside of sys/boot.
636 The arm port has split armv6 into armv6 and armv7. armv7 is now
637 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
638 and are running a kernel from before r324363, you will need to add
639 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
642 When building multiple kernels using KERNCONF, non-existent KERNCONF
643 files will produce an error and buildkernel will fail. Previously
644 missing KERNCONF files silently failed giving no indication as to
645 why, only to subsequently discover during installkernel that the
646 desired kernel was never built in the first place.
649 The default serial number format for CTL LUNs has changed. This will
650 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
651 or iSCSI clients care about their LUNs' serial numbers. Users who
652 require serial number stability should hardcode serial numbers in
656 For 32-bit arm compiled for hard-float support, soft-floating point
657 binaries now always get their shared libraries from
658 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
659 /usr/libsoft also existed). Only users with a hard-float ld.so, but
660 soft-float everything else should be affected.
663 The geli password typed at boot is now hidden. To restore the previous
664 behavior, see geli(8) for configuration options.
667 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
668 sysctl values. Minor nit, but requires a rebuild of both world/kernel
672 "make check" behavior (made in ^/head@r295380) has been changed to
673 execute from a limited sandbox, as opposed to executing from
677 - The "beforecheck" and "aftercheck" targets are now specified.
678 - ${CHECKDIR} (added in commit noted above) has been removed.
679 - Legacy behavior can be enabled by setting
680 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
682 If the limited sandbox mode is enabled, "make check" will execute
683 "make distribution", then install, execute the tests, and clean up the
684 sandbox if successful.
686 The "make distribution" and "make install" targets are typically run as
687 root to set appropriate permissions and ownership at installation time.
688 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
689 environment if executing "make check" with limited sandbox mode using
690 an unprivileged user.
693 Since the switch to GPT disk labels, fsck for UFS/FFS has been
694 unable to automatically find alternate superblocks. As of r322297,
695 the information needed to find alternate superblocks has been
696 moved to the end of the area reserved for the boot block.
697 Filesystems created with a newfs of this vintage or later
698 will create the recovery information. If you have a filesystem
699 created prior to this change and wish to have a recovery block
700 created for your filesystem, you can do so by running fsck in
701 foreground mode (i.e., do not use the -p or -y options). As it
702 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
703 to which you should answer yes.
706 As of r321665, an NFSv4 server configuration that services
707 Kerberos mounts or clients that do not support the uid/gid in
708 owner/owner_group string capability, must explicitly enable
709 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
710 machine's /etc/rc.conf file.
713 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
714 Please see the 20141231 entry below for information about prerequisites
715 and upgrading, if you are not already using clang 3.5.0 or higher.
718 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
719 r-commands (rlogin, rsh, etc.) to be built with the base system.
722 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
723 a very major ABI incompatible change, so users of FreeBSD/powerpc must
724 be careful when performing source upgrades. It is best to run
725 'make installworld' from an alternate root system, either a live
726 CD/memory stick, or a temporary root partition. Additionally, all ports
727 must be recompiled. powerpc64 is largely unaffected, except in the case
728 of 32-bit compatibility. All 32-bit binaries will be affected.
731 Forward compatibility for the "ino64" project have been committed. This
732 will allow most new binaries to run on older kernels in a limited
733 fashion. This prevents many of the common foot-shooting actions in the
734 upgrade as well as the limited ability to roll back the kernel across
735 the ino64 upgrade. Complicated use cases may not work properly, though
736 enough simpler ones work to allow recovery in most situations.
739 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
740 if you require the GPL compiler.
743 The internal ABI used for communication between the NFS kernel modules
744 was changed by r320085, so __FreeBSD_version was bumped to
745 ensure all the NFS related modules are updated together.
748 The ABI of struct event was changed by extending the data
749 member to 64bit and adding ext fields. For upgrade, same
750 precautions as for the entry 20170523 "ino64" must be
754 The GNU roff toolchain has been removed from base. To render manpages
755 which are not supported by mandoc(1), man(1) can fallback on GNU roff
756 from ports (and recommends to install it).
757 To render roff(7) documents, consider using GNU roff from ports or the
758 heirloom doctools roff toolchain from ports via pkg install groff or
759 via pkg install heirloom-doctools.
762 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
763 smaller runtime footprint builds. This is useful for embedded systems
764 which only require one chipset support.
766 If you load it as a module, make sure this is in /boot/loader.conf:
770 This will load the HAL, all chip/RF backends and if_ath_pci.
771 If you have if_ath_pci in /boot/loader.conf, ensure it is after
772 if_ath or it will not load any HAL chipset support.
774 If you want to selectively load things (eg on ye cheape ARM/MIPS
775 platforms where RAM is at a premium) you should:
778 * load the chip modules in question
779 * load ath_rate, ath_dfs
781 * load if_ath_pci and/or if_ath_ahb depending upon your particular
782 bus bind type - this is where probe/attach is done.
784 For further comments/feedback, poke adrian@ .
787 The "ino64" 64-bit inode project has been committed, which extends
788 a number of types to 64 bits. Upgrading in place requires care and
789 adherence to the documented upgrade procedure.
791 If using a custom kernel configuration ensure that the
792 COMPAT_FREEBSD11 option is included (as during the upgrade the
793 system will be running the ino64 kernel with the existing world).
795 For the safest in-place upgrade begin by removing previous build
796 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
797 procedure documented below under the heading "To rebuild everything and
798 install it on the current system." Specifically, a reboot is required
799 after installing the new kernel before installing world. While an
800 installworld normally works by accident from multiuser after rebooting
801 the proper kernel, there are many cases where this will fail across this
802 upgrade and installworld from single user is required.
805 The NATM framework including the en(4), fatm(4), hatm(4), and
806 patm(4) devices has been removed. Consumers should plan a
807 migration before the end-of-life date for FreeBSD 11.
810 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
811 diff has not been implemented, if those are needed a newer version of
812 GNU diff is available via the diffutils package under the gdiff name.
815 As of r316810 for ipfilter, keep frags is no longer assumed when
816 keep state is specified in a rule. r316810 aligns ipfilter with
817 documentation in man pages separating keep frags from keep state.
818 This allows keep state to be specified without forcing keep frags
819 and allows keep frags to be specified independently of keep state.
820 To maintain previous behaviour, also specify keep frags with
821 keep state (as documented in ipf.conf.5).
824 arm64 builds now use the base system LLD 4.0.0 linker by default,
825 instead of requiring that the aarch64-binutils port or package be
826 installed. To continue using aarch64-binutils, set
827 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
830 The UDP optimization in entry 20160818 that added the sysctl
831 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
832 packets will no longer be treated as L3 broadcast packets.
835 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
836 use any explicitly assigned loopback address available in the jail
837 instead of using the first assigned address of the jail.
840 The ctl.ko module no longer implements the iSCSI target frontend:
841 cfiscsi.ko does instead.
843 If building cfiscsi.ko as a kernel module, the module can be loaded
844 via one of the following methods:
845 - `cfiscsi_load="YES"` in loader.conf(5).
846 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
847 - ctladm(8)/ctld(8), when compiled with iSCSI support
848 (`WITH_ISCSI=yes` in src.conf(5))
850 Please see cfiscsi(4) for more details.
853 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
854 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
855 same source (previously, the dependency of mmcsd.ko on mmc.ko was
856 missing, but mmcsd.ko now will refuse to load if it is incompatible
860 The syntax of ipfw(8) named states was changed to avoid ambiguity.
861 If you have used named states in the firewall rules, you need to modify
862 them after installworld and before rebooting. Now named states must
863 be prefixed with colon.
866 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
867 removed as the userland we provide cannot use them. The KMS version
868 (sys/dev/drm2) supports the same hardware.
871 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
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 The code that provides support for ZFS .zfs/ directory functionality
877 has been reimplemented. It's not possible now to create a snapshot
878 by mkdir under .zfs/snapshot/. That should be the only user visible
882 EISA bus support has been removed. The WITH_EISA option is no longer
886 MCA bus support has been removed.
889 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
890 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
893 The EM_MULTIQUEUE kernel configuration option is deprecated now that
894 the em(4) driver conforms to iflib specifications.
897 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
898 IFLIB. If you have a custom kernel configuration that excludes em(4)
899 but you use igb(4), you need to re-add em(4) to your custom
903 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
904 Please see the 20141231 entry below for information about prerequisites
905 and upgrading, if you are not already using clang 3.5.0 or higher.
908 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
909 Please see the 20141231 entry below for information about prerequisites
910 and upgrading, if you are not already using clang 3.5.0 or higher.
913 The layout of the pmap structure has changed for powerpc to put the pmap
914 statistics at the front for all CPU variations. libkvm(3) and all tools
915 that link against it need to be recompiled.
918 isl(4) and cyapa(4) drivers now require a new driver,
919 chromebook_platform(4), to work properly on Chromebook-class hardware.
920 On other types of hardware the drivers may need to be configured using
921 device hints. Please see the corresponding manual pages for details.
924 The urtwn(4) driver was merged into rtwn(4) and now consists of
925 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
927 Also, firmware for RTL8188CE was renamed due to possible name
928 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
931 GNU rcs has been removed from base. It is available as packages:
932 - rcs: Latest GPLv3 GNU rcs version.
933 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
937 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
938 modules now requires that the kernel configuration contain the
939 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
942 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
943 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
946 Relocatable object files with the extension of .So have been renamed
947 to use an extension of .pico instead. The purpose of this change is
948 to avoid a name clash with shared libraries on case-insensitive file
949 systems. On those file systems, foo.So is the same file as foo.so.
952 GNU rcs has been turned off by default. It can (temporarily) be built
953 again by adding WITH_RCS knob in src.conf.
954 Otherwise, GNU rcs is available from packages:
955 - rcs: Latest GPLv3 GNU rcs version.
956 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
959 The backup_uses_rcs functionality has been removed from rc.subr.
962 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
963 two separate components, QUEUE_MACRO_DEBUG_TRACE and
964 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
965 QUEUE_MACRO_DEBUG behavior.
968 r304787 changed some ioctl interfaces between the iSCSI userspace
969 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
970 rebuilt to work with new kernels. __FreeBSD_version has been bumped
974 The UDP receive code has been updated to only treat incoming UDP
975 packets that were addressed to an L2 broadcast address as L3
976 broadcast packets. It is not expected that this will affect any
977 standards-conforming UDP application. The new behaviour can be
978 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
982 Remove the openbsd_poll system call.
983 __FreeBSD_version has been bumped because of this.
986 The stable/11 branch has been created from head@r302406.
989 The libc stub for the pipe(2) system call has been replaced with
990 a wrapper that calls the pipe2(2) system call and the pipe(2)
991 system call is now only implemented by the kernels that include
992 "options COMPAT_FREEBSD10" in their config file (this is the
993 default). Users should ensure that this option is enabled in
994 their kernel or upgrade userspace to r302092 before upgrading their
998 CAM will now strip leading spaces from SCSI disks' serial numbers.
999 This will affect users who create UFS filesystems on SCSI disks using
1000 those disk's diskid device nodes. For example, if /etc/fstab
1001 previously contained a line like
1002 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1003 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1004 transforms like gmirror may also be affected. ZFS users should
1008 The bitstring(3) API has been updated with new functionality and
1009 improved performance. But it is binary-incompatible with the old API.
1010 Objects built with the new headers may not be linked against objects
1011 built with the old headers.
1014 The brk and sbrk functions have been removed from libc on arm64.
1015 Binutils from ports has been updated to not link to these
1016 functions and should be updated to the latest version before
1017 installing a new libc.
1020 The armv6 port now defaults to hard float ABI. Limited support
1021 for running both hardfloat and soft float on the same system
1022 is available using the libraries installed with -DWITH_LIBSOFT.
1023 This has only been tested as an upgrade path for installworld
1024 and packages may fail or need manual intervention to run. New
1025 packages will be needed.
1027 To update an existing self-hosted armv6hf system, you must add
1028 TARGET_ARCH=armv6 on the make command line for both the build
1029 and the install steps.
1032 Kernel modules compiled outside of a kernel build now default to
1033 installing to /boot/modules instead of /boot/kernel. Many kernel
1034 modules built this way (such as those in ports) already overrode
1035 KMODDIR explicitly to install into /boot/modules. However,
1036 manually building and installing a module from /sys/modules will
1037 now install to /boot/modules instead of /boot/kernel.
1040 The CAM I/O scheduler has been committed to the kernel. There should be
1041 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1042 list of known rogues that claim support for this but actually corrupt
1043 data is believed to be complete, be on the lookout for data
1044 corruption. The known rogue list is believed to be complete:
1046 o Crucial MX100, M550 drives with MU01 firmware.
1047 o Micron M510 and M550 drives with MU01 firmware.
1048 o Micron M500 prior to MU07 firmware
1049 o Samsung 830, 840, and 850 all firmwares
1050 o FCCT M500 all firmwares
1052 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1053 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1054 updated firmware. Black listed drives will work correctly because these
1055 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1056 this list is the same as found in Linux, it's believed there are no
1057 other rogues in the market place. All other models from the above
1060 To be safe, if you are at all concerned, you can quirk each of your
1061 drives to prevent NCQ from being sent by setting:
1062 kern.cam.ada.X.quirks="0x2"
1063 in loader.conf. If the drive requires the 4k sector quirk, set the
1064 quirks entry to 0x3.
1067 The FAST_DEPEND build option has been removed and its functionality is
1068 now the one true way. The old mkdep(1) style of 'make depend' has
1069 been removed. See 20160311 for further details.
1072 Resource range types have grown from unsigned long to uintmax_t. All
1073 drivers, and anything using libdevinfo, need to be recompiled.
1076 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1077 builds. It no longer runs mkdep(1) during 'make depend', and the
1078 'make depend' stage can safely be skipped now as it is auto ran
1079 when building 'make all' and will generate all SRCS and DPSRCS before
1080 building anything else. Dependencies are gathered at compile time with
1081 -MF flags kept in separate .depend files per object file. Users should
1082 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1083 stale .depend files.
1086 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1087 kernel modules. Therefore, if you load any kernel modules at boot time,
1088 please install the boot loaders after you install the kernel, but before
1092 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1093 make installkernel KERNCONF=YOUR_KERNEL_HERE
1094 make -C sys/boot install
1095 <reboot in single user>
1097 Then follow the usual steps, described in the General Notes section,
1101 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1102 see the 20141231 entry below for information about prerequisites and
1103 upgrading, if you are not already using clang 3.5.0 or higher.
1106 The AIO subsystem is now a standard part of the kernel. The
1107 VFS_AIO kernel option and aio.ko kernel module have been removed.
1108 Due to stability concerns, asynchronous I/O requests are only
1109 permitted on sockets and raw disks by default. To enable
1110 asynchronous I/O requests on all file types, set the
1111 vfs.aio.enable_unsafe sysctl to a non-zero value.
1114 The ELF object manipulation tool objcopy is now provided by the
1115 ELF Tool Chain project rather than by GNU binutils. It should be a
1116 drop-in replacement, with the addition of arm64 support. The
1117 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1118 to obtain the GNU version if necessary.
1121 Building ZFS pools on top of zvols is prohibited by default. That
1122 feature has never worked safely; it's always been prone to deadlocks.
1123 Using a zvol as the backing store for a VM guest's virtual disk will
1124 still work, even if the guest is using ZFS. Legacy behavior can be
1125 restored by setting vfs.zfs.vol.recursive=1.
1128 The NONE and HPN patches has been removed from OpenSSH. They are
1129 still available in the security/openssh-portable port.
1132 With the addition of ypldap(8), a new _ypldap user is now required
1133 during installworld. "mergemaster -p" can be used to add the user
1134 prior to installworld, as documented in the handbook.
1137 The tftp loader (pxeboot) now uses the option root-path directive. As a
1138 consequence it no longer looks for a pxeboot.4th file on the tftp
1139 server. Instead it uses the regular /boot infrastructure as with the
1143 The code to start recording plug and play data into the modules has
1144 been committed. While the old tools will properly build a new kernel,
1145 a number of warnings about "unknown metadata record 4" will be produced
1146 for an older kldxref. To avoid such warnings, make sure to rebuild
1147 the kernel toolchain (or world). Make sure that you have r292078 or
1148 later when trying to build 292077 or later before rebuilding.
1151 Debug data files are now built by default with 'make buildworld' and
1152 installed with 'make installworld'. This facilitates debugging but
1153 requires more disk space both during the build and for the installed
1154 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1158 r291527 changed the internal interface between the nfsd.ko and
1159 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1160 __FreeBSD_version has been bumped because of this.
1163 Add support for unicode collation strings leads to a change of
1164 order of files listed by ls(1) for example. To get back to the old
1165 behaviour, set LC_COLLATE environment variable to "C".
1167 Databases administrators will need to reindex their databases given
1168 collation results will be different.
1170 Due to a bug in install(1) it is recommended to remove the ancient
1171 locales before running make installworld.
1173 rm -rf /usr/share/locale/*
1176 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1177 libcrypto.so.7 or libssl.so.7 must be recompiled.
1180 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1181 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1182 should be replaced with isp_2400 and isp_2500 modules respectively.
1185 The build previously allowed using 'make -n' to not recurse into
1186 sub-directories while showing what commands would be executed, and
1187 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1188 and 'make -N' will not.
1191 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1192 and etcupdate will now use this file. A custom sendmail.cf is now
1193 updated via this mechanism rather than via installworld. If you had
1194 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1195 want to remove the exclusion or change it to "always install".
1196 /etc/mail/sendmail.cf is now managed the same way regardless of
1197 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1198 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1201 Compatibility shims for legacy ATA device names have been removed.
1202 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1203 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1204 environment variables, /dev/ad* and /dev/ar* symbolic links.
1207 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1208 Please see the 20141231 entry below for information about prerequisites
1209 and upgrading, if you are not already using clang 3.5.0 or higher.
1212 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1213 and renamed from .symbols to .debug. This reduces the size requirements
1214 on the boot partition or file system and provides consistency with
1215 userland debug files.
1217 When using the supported kernel installation method the
1218 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1219 as is done with /boot/kernel.
1221 Developers wishing to maintain the historical behavior of installing
1222 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1225 The wireless drivers had undergone changes that remove the 'parent
1226 interface' from the ifconfig -l output. The rc.d network scripts
1227 used to check presence of a parent interface in the list, so old
1228 scripts would fail to start wireless networking. Thus, etcupdate(3)
1229 or mergemaster(8) run is required after kernel update, to update your
1230 rc.d scripts in /etc.
1233 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1234 These configurations are now automatically interpreted as
1235 'scrub fragment reassemble'.
1238 Kernel-loadable modules for the random(4) device are back. To use
1239 them, the kernel must have
1242 options RANDOM_LOADABLE
1244 kldload(8) can then be used to load random_fortuna.ko
1245 or random_yarrow.ko. Please note that due to the indirect
1246 function calls that the loadable modules need to provide,
1247 the build-in variants will be slightly more efficient.
1249 The random(4) kernel option RANDOM_DUMMY has been retired due to
1250 unpopularity. It was not all that useful anyway.
1253 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1254 Control over building the ELF Tool Chain tools is now provided by
1255 the WITHOUT_TOOLCHAIN knob.
1258 The polarity of Pulse Per Second (PPS) capture events with the
1259 uart(4) driver has been corrected. Prior to this change the PPS
1260 "assert" event corresponded to the trailing edge of a positive PPS
1261 pulse and the "clear" event was the leading edge of the next pulse.
1263 As the width of a PPS pulse in a typical GPS receiver is on the
1264 order of 1 millisecond, most users will not notice any significant
1265 difference with this change.
1267 Anyone who has compensated for the historical polarity reversal by
1268 configuring a negative offset equal to the pulse width will need to
1269 remove that workaround.
1272 The default group assigned to /dev/dri entries has been changed
1273 from 'wheel' to 'video' with the id of '44'. If you want to have
1274 access to the dri devices please add yourself to the video group
1277 # pw groupmod video -m $USER
1280 The menu.rc and loader.rc files will now be replaced during
1281 upgrades. Please migrate local changes to menu.rc.local and
1282 loader.rc.local instead.
1285 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1286 strings and strip have been removed. The src.conf(5) knob
1287 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1290 As ZFS requires more kernel stack pages than is the default on some
1291 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1292 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1294 Please consider using 'options KSTACK_PAGES=X' where X is greater
1295 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1298 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1299 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1300 default, i.e., they will not contain "::". For example, instead
1301 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1302 to have a more specific match, such as different map entries for
1303 IPv6:0:0 vs IPv6:0. This change requires that configuration
1304 data (including maps, files, classes, custom ruleset, etc.) must
1305 use the same format, so make certain such configuration data is
1306 upgrading. As a very simple check search for patterns like
1307 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1308 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1309 the cf option UseCompressedIPv6Addresses.
1312 The default kernel entropy-processing algorithm is now
1313 Fortuna, replacing Yarrow.
1315 Assuming you have 'device random' in your kernel config
1316 file, the configurations allow a kernel option to override
1317 this default. You may choose *ONE* of:
1319 options RANDOM_YARROW # Legacy /dev/random algorithm.
1320 options RANDOM_DUMMY # Blocking-only driver.
1322 If you have neither, you get Fortuna. For most people,
1323 read no further, Fortuna will give a /dev/random that works
1324 like it always used to, and the difference will be irrelevant.
1326 If you remove 'device random', you get *NO* kernel-processed
1327 entropy at all. This may be acceptable to folks building
1328 embedded systems, but has complications. Carry on reading,
1329 and it is assumed you know what you need.
1331 *PLEASE* read random(4) and random(9) if you are in the
1332 habit of tweaking kernel configs, and/or if you are a member
1333 of the embedded community, wanting specific and not-usual
1334 behaviour from your security subsystems.
1336 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1337 random', you will NOT have a functioning /dev/random, and
1338 many cryptographic features will not work, including SSH.
1339 You may also find strange behaviour from the random(3) set
1340 of library functions, in particular sranddev(3), srandomdev(3)
1341 and arc4random(3). The reason for this is that the KERN_ARND
1342 sysctl only returns entropy if it thinks it has some to
1343 share, and with RANDOM_DUMMY or no 'device random' this
1347 An additional fix for the issue described in the 20150614 sendmail
1348 entry below has been committed in revision 284717.
1351 FreeBSD's old make (fmake) has been removed from the system. It is
1352 available as the devel/fmake port or via pkg install fmake.
1355 The fix for the issue described in the 20150614 sendmail entry
1356 below has been committed in revision 284436. The work
1357 around described in that entry is no longer needed unless the
1358 default setting is overridden by a confDH_PARAMETERS configuration
1359 setting of '5' or pointing to a 512 bit DH parameter file.
1362 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1363 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1364 and devel/kyua to version 0.20+ and adjust any calling code to work
1365 with Kyuafile and kyua.
1368 The import of openssl to address the FreeBSD-SA-15:10.openssl
1369 security advisory includes a change which rejects handshakes
1370 with DH parameters below 768 bits. sendmail releases prior
1371 to 8.15.2 (not yet released), defaulted to a 512 bit
1372 DH parameter setting for client connections. To work around
1373 this interoperability, sendmail can be configured to use a
1374 2048 bit DH parameter by:
1376 1. Edit /etc/mail/`hostname`.mc
1377 2. If a setting for confDH_PARAMETERS does not exist or
1378 exists and is set to a string beginning with '5',
1379 replace it with '2'.
1380 3. If a setting for confDH_PARAMETERS exists and is set to
1381 a file path, create a new file with:
1382 openssl dhparam -out /path/to/file 2048
1383 4. Rebuild the .cf file:
1384 cd /etc/mail/; make; make install
1385 5. Restart sendmail:
1386 cd /etc/mail/; make restart
1388 A sendmail patch is coming, at which time this file will be
1392 Generation of legacy formatted entries have been disabled by default
1393 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1394 entries were converted to use the new format by default when the new,
1395 machine independent format have been added and supported since FreeBSD
1398 Please see the pwd_mkdb(8) manual page for further details.
1401 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1402 20141231 entry below for information about prerequisites and upgrading,
1403 if you are not already using 3.5.0 or higher.
1406 TI platform code switched to using vendor DTS files and this update
1407 may break existing systems running on Beaglebone, Beaglebone Black,
1410 - dtb files should be regenerated/reinstalled. Filenames are the
1411 same but content is different now
1412 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1413 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1414 addressing scheme is now pin 25 on /dev/gpioc3.
1415 - Pandaboard: /etc/ttys should be updated, serial console device is
1416 now /dev/ttyu2, not /dev/ttyu0
1419 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1420 If you need the GNU extension from groff soelim(1), install groff
1421 from package: pkg install groff, or via ports: textproc/groff.
1424 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1425 defined in symlink(7); previously symlinks were silently ignored.
1428 The const qualifier has been removed from iconv(3) to comply with
1429 POSIX. The ports tree is aware of this from r384038 onwards.
1432 Libraries specified by LIBADD in Makefiles must have a corresponding
1433 DPADD_<lib> variable to ensure correct dependencies. This is now
1434 enforced in src.libnames.mk.
1437 From legacy ata(4) driver was removed support for SATA controllers
1438 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1439 Kernel modules ataahci and ataadaptec were removed completely,
1440 replaced by ahci and mvs modules respectively.
1443 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1444 the 20141231 entry below for information about prerequisites and
1445 upgrading, if you are not already using 3.5.0 or higher.
1448 The 32-bit PowerPC kernel has been changed to a position-independent
1449 executable. This can only be booted with a version of loader(8)
1450 newer than January 31, 2015, so make sure to update both world and
1451 kernel before rebooting.
1454 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1455 but before r278950, the RNG was not seeded properly. Immediately
1456 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1457 ssh keys or openssl keys) that were generated w/ a kernel from that
1458 range. This does not affect programs that directly used /dev/random
1459 or /dev/urandom. All userland uses of arc4random(3) are affected.
1462 The autofs(4) ABI was changed in order to restore binary compatibility
1463 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1464 with the new kernel.
1467 The powerpc64 kernel has been changed to a position-independent
1468 executable. This can only be booted with a new version of loader(8),
1469 so make sure to update both world and kernel before rebooting.
1472 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1473 only release, no new features have been added. Please see the 20141231
1474 entry below for information about prerequisites and upgrading, if you
1475 are not already using 3.5.0.
1478 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1479 taken from the ELF Tool Chain project rather than GNU binutils. They
1480 should be drop-in replacements, with the addition of arm64 support.
1481 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1482 binutils tools, if necessary. See 20150805 for updated information.
1485 The default Unbound configuration now enables remote control
1486 using a local socket. Users who have already enabled the
1487 local_unbound service should regenerate their configuration
1488 by running "service local_unbound setup" as root.
1491 The GNU texinfo and GNU info pages have been removed.
1492 To be able to view GNU info pages please install texinfo from ports.
1495 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1497 As of this release, a prerequisite for building clang, llvm and lldb is
1498 a C++11 capable compiler and C++11 standard library. This means that to
1499 be able to successfully build the cross-tools stage of buildworld, with
1500 clang as the bootstrap compiler, your system compiler or cross compiler
1501 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1502 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1505 On any standard FreeBSD 10.x or 11.x installation, where clang and
1506 libc++ are on by default (that is, on x86 or arm), this should work out
1509 On 9.x installations where clang is enabled by default, e.g. on x86 and
1510 powerpc, libc++ will not be enabled by default, so libc++ should be
1511 built (with clang) and installed first. If both clang and libc++ are
1512 missing, build clang first, then use it to build libc++.
1514 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1515 the instructions for 9.x above.
1517 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1518 default, and do not build clang.
1520 Many embedded systems are resource constrained, and will not be able to
1521 build clang in a reasonable time, or in some cases at all. In those
1522 cases, cross building bootable systems on amd64 is a workaround.
1524 This new version of clang introduces a number of new warnings, of which
1525 the following are most likely to appear:
1529 This warns in two cases, for both C and C++:
1530 * When the code is trying to take the absolute value of an unsigned
1531 quantity, which is effectively a no-op, and almost never what was
1532 intended. The code should be fixed, if at all possible. If you are
1533 sure that the unsigned quantity can be safely cast to signed, without
1534 loss of information or undefined behavior, you can add an explicit
1535 cast, or disable the warning.
1537 * When the code is trying to take an absolute value, but the called
1538 abs() variant is for the wrong type, which can lead to truncation.
1539 If you want to disable the warning instead of fixing the code, please
1540 make sure that truncation will not occur, or it might lead to unwanted
1543 -Wtautological-undefined-compare and
1544 -Wundefined-bool-conversion
1546 These warn when C++ code is trying to compare 'this' against NULL, while
1547 'this' should never be NULL in well-defined C++ code. However, there is
1548 some legacy (pre C++11) code out there, which actively abuses this
1549 feature, which was less strictly defined in previous C++ versions.
1551 Squid and openjdk do this, for example. The warning can be turned off
1552 for C++98 and earlier, but compiling the code in C++11 mode might result
1553 in unexpected behavior; for example, the parts of the program that are
1554 unreachable could be optimized away.
1557 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1558 kernel sources have been removed. The .h files remain, since some
1559 utilities include them. This will need to be fixed later.
1560 If "mount -t oldnfs ..." is attempted, it will fail.
1561 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1562 the utilities will report errors.
1565 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1566 directories to top level SUBDIR variable when their parent
1567 directory is included in LOCAL_DIRS. Users with build systems with
1568 such hierarchies and without SUBDIR entries in the parent
1569 directory Makefiles should add them or add the directories to
1573 faith(4) and faithd(8) have been removed from the base system. Faith
1574 has been obsolete for a very long time.
1577 vt(4), the new console driver, is enabled by default. It brings
1578 support for Unicode and double-width characters, as well as
1579 support for UEFI and integration with the KMS kernel video
1582 You may need to update your console settings in /etc/rc.conf,
1583 most probably the keymap. During boot, /etc/rc.d/syscons will
1584 indicate what you need to do.
1586 vt(4) still has issues and lacks some features compared to
1587 syscons(4). See the wiki for up-to-date information:
1588 https://wiki.freebsd.org/Newcons
1590 If you want to keep using syscons(4), you can do so by adding
1591 the following line to /boot/loader.conf:
1595 pjdfstest has been integrated into kyua as an opt-in test suite.
1596 Please see share/doc/pjdfstest/README for more details on how to
1600 gperf has been removed from the base system for architectures
1601 that use clang. Ports that require gperf will obtain it from the
1605 pjdfstest has been moved from tools/regression/pjdfstest to
1609 At svn r271982, The default linux compat kernel ABI has been adjusted
1610 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1611 update. If you wish to continue using the linux-f10 compat ports,
1612 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1613 encouraged to update their linux-compat packages to linux-c6 during
1614 their next update cycle.
1617 The ofwfb driver, used to provide a graphics console on PowerPC when
1618 using vt(4), no longer allows mmap() of all physical memory. This
1619 will prevent Xorg on PowerPC with some ATI graphics cards from
1620 initializing properly unless x11-servers/xorg-server is updated to
1624 The xdev targets have been converted to using TARGET and
1625 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1628 The default unbound configuration has been modified to address
1629 issues with reverse lookups on networks that use private
1630 address ranges. If you use the local_unbound service, run
1631 "service local_unbound setup" as root to regenerate your
1632 configuration, then "service local_unbound reload" to load the
1636 The GNU texinfo and GNU info pages are not built and installed
1637 anymore, WITH_INFO knob has been added to allow to built and install
1639 UPDATE: see 20150102 entry on texinfo's removal
1642 The GNU readline library is now an INTERNALLIB - that is, it is
1643 statically linked into consumers (GDB and variants) in the base
1644 system, and the shared library is no longer installed. The
1645 devel/readline port is available for third party software that
1649 The Itanium architecture (ia64) has been removed from the list of
1650 known architectures. This is the first step in the removal of the
1654 Commit r268115 has added NFSv4.1 server support, merged from
1655 projects/nfsv4.1-server. Since this includes changes to the
1656 internal interfaces between the NFS related modules, a full
1657 build of the kernel and modules will be necessary.
1658 __FreeBSD_version has been bumped.
1661 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1662 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1663 which differs from the behaviour controlled by this knob.)
1666 Maximal length of the serial number in CTL was increased from 16 to
1667 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1668 and ctld, need to be rebuilt to work with a new kernel.
1671 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1672 1 respectively to match the upstream numbers. They were out of
1673 sync because, when they were originally added to FreeBSD, the
1674 upstream versions were not respected. These libraries are private
1675 and not yet built by default, so renumbering them should be a
1676 non-issue. However, unclean source trees will yield broken test
1677 programs once the operator executes "make delete-old-libs" after a
1678 "make installworld".
1680 Additionally, the atf-sh binary was made private by moving it into
1681 /usr/libexec/. Already-built shell test programs will keep the
1682 path to the old binary so they will break after "make delete-old"
1685 If you are using WITH_TESTS=yes (not the default), wipe the object
1686 tree and rebuild from scratch to prevent spurious test failures.
1687 This is only needed once: the misnumbered libraries and misplaced
1688 binaries have been added to OptionalObsoleteFiles.inc so they will
1689 be removed during a clean upgrade.
1692 Clang and llvm have been upgraded to 3.4.1 release.
1695 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1696 be removed to avoid issues in the future (and has been added to
1700 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1701 past, it affected all builds that used the bsd.*.mk files. The old
1702 behavior was a bug, but people may have relied upon it. To get this
1703 behavior back, you can .include /etc/src.conf from /etc/make.conf
1704 (which is still global and isn't changed). This also changes the
1705 behavior of incremental builds inside the tree of individual
1706 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1707 Although this has survived make universe and some upgrade scenarios,
1708 other upgrade scenarios may have broken. At least one form of
1709 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1710 as well... In cases where MAKESYSPATH isn't working with this
1711 setting, you'll need to set it to the full path to your tree.
1713 One side effect of all this cleaning up is that bsd.compiler.mk
1714 is no longer implicitly included by bsd.own.mk. If you wish to
1715 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1719 The lindev device has been removed since /dev/full has been made a
1720 standard device. __FreeBSD_version has been bumped.
1723 The knob WITHOUT_VI was added to the base system, which controls
1724 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1725 in order to reorder files share/termcap and didn't build ex(1) as a
1726 build tool, so building/installing with WITH_VI is highly advised for
1727 build hosts for older releases.
1729 This issue has been fixed in stable/9 and stable/10 in r277022 and
1730 r276991, respectively.
1733 The YES_HESIOD knob has been removed. It has been obsolete for
1734 a decade. Please move to using WITH_HESIOD instead or your builds
1735 will silently lack HESIOD.
1738 The uart(4) driver has been changed with respect to its handling
1739 of the low-level console. Previously the uart(4) driver prevented
1740 any process from changing the baudrate or the CLOCAL and HUPCL
1741 control flags. By removing the restrictions, operators can make
1742 changes to the serial console port without having to reboot.
1743 However, when getty(8) is started on the serial device that is
1744 associated with the low-level console, a misconfigured terminal
1745 line in /etc/ttys will now have a real impact.
1746 Before upgrading the kernel, make sure that /etc/ttys has the
1747 serial console device configured as 3wire without baudrate to
1748 preserve the previous behaviour. E.g:
1749 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1752 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1753 to improve performance. To re-enable it, if needed, run rpcbind
1754 with command line option -W.
1757 Switched back to the GPL dtc compiler due to updates in the upstream
1758 dts files not being supported by the BSDL dtc compiler. You will need
1759 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1760 may result while building dtb files during a kernel build if you fail
1761 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1764 Clang and llvm have been upgraded to 3.4 release.
1767 The nve(4) driver has been removed. Please use the nfe(4) driver
1768 for NVIDIA nForce MCP Ethernet adapters instead.
1771 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1772 This could cause certain C++ applications using shared libraries built
1773 against the previous version of libc++ to crash. The incompatibility
1774 has now been fixed, but any C++ applications or shared libraries built
1775 between r261283 and r261801 should be recompiled.
1778 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1779 capability mode support. Please note that enabling the feature in
1780 kernel is still highly recommended.
1783 OpenSSH is now built with sandbox support, and will use sandbox as
1784 the default privilege separation method. This requires Capsicum
1785 capability mode support in kernel.
1788 The libelf and libdwarf libraries have been updated to newer
1789 versions from upstream. Shared library version numbers for
1790 these two libraries were bumped. Any ports or binaries
1791 requiring these two libraries should be recompiled.
1792 __FreeBSD_version is bumped to 1100006.
1795 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1796 instead of providing an explicit one, this would prevent such
1797 Makefile from providing its own Kyuafile in the future during
1798 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1799 intervention is needed to clean an objdir if you use NO_CLEAN:
1800 # find /usr/obj -name Kyuafile | xargs rm -f
1803 The behavior of gss_pseudo_random() for the krb5 mechanism
1804 has changed, for applications requesting a longer random string
1805 than produced by the underlying enctype's pseudo-random() function.
1806 In particular, the random string produced from a session key of
1807 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1808 be different at the 17th octet and later, after this change.
1809 The counter used in the PRF+ construction is now encoded as a
1810 big-endian integer in accordance with RFC 4402.
1811 __FreeBSD_version is bumped to 1100004.
1814 The WITHOUT_ATF build knob has been removed and its functionality
1815 has been subsumed into the more generic WITHOUT_TESTS. If you were
1816 using the former to disable the build of the ATF libraries, you
1817 should change your settings to use the latter.
1820 The default version of mtree is nmtree which is obtained from
1821 NetBSD. The output is generally the same, but may vary
1822 slightly. If you found you need identical output adding
1823 "-F freebsd9" to the command line should do the trick. For the
1824 time being, the old mtree is available as fmtree.
1827 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1828 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1829 1.1.4_8 and verify bsdyml not linked in, before running "make
1831 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1833 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1836 The stable/10 branch has been created in subversion from head
1843 Avoid using make -j when upgrading. While generally safe, there are
1844 sometimes problems using -j to upgrade. If your upgrade fails with
1845 -j, please try again without -j. From time to time in the past there
1846 have been problems using -j with buildworld and/or installworld. This
1847 is especially true when upgrading between "distant" versions (eg one
1848 that cross a major release boundary or several minor releases, or when
1849 several months have passed on the -current branch).
1851 Sometimes, obscure build problems are the result of environment
1852 poisoning. This can happen because the make utility reads its
1853 environment when searching for values for global variables. To run
1854 your build attempts in an "environmental clean room", prefix all make
1855 commands with 'env -i '. See the env(1) manual page for more details.
1857 When upgrading from one major version to another it is generally best to
1858 upgrade to the latest code in the currently installed branch first, then
1859 do an upgrade to the new branch. This is the best-tested upgrade path,
1860 and has the highest probability of being successful. Please try this
1861 approach if you encounter problems with a major version upgrade. Since
1862 the stable 4.x branch point, one has generally been able to upgrade from
1863 anywhere in the most recent stable branch to head / current (or even the
1864 last couple of stable branches). See the top of this file when there's
1867 When upgrading a live system, having a root shell around before
1868 installing anything can help undo problems. Not having a root shell
1869 around can lead to problems if pam has changed too much from your
1870 starting point to allow continued authentication after the upgrade.
1872 This file should be read as a log of events. When a later event changes
1873 information of a prior event, the prior event should not be deleted.
1874 Instead, a pointer to the entry with the new information should be
1875 placed in the old entry. Readers of this file should also sanity check
1876 older entries before relying on them blindly. Authors of new entries
1877 should write them with this in mind.
1881 When upgrading the boot ZFS pool to a new version, always follow
1884 1.) recompile and reinstall the ZFS boot loader and boot block
1885 (this is part of "make buildworld" and "make installworld")
1887 2.) update the ZFS boot block on your boot drive
1889 The following example updates the ZFS boot block on the first
1890 partition (freebsd-boot) of a GPT partitioned drive ada0:
1891 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1893 Non-boot pools do not need these updates.
1897 If you are updating from a prior version of FreeBSD (even one just
1898 a few days old), you should follow this procedure. It is the most
1899 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1901 make kernel-toolchain
1902 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1903 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1905 To test a kernel once
1906 ---------------------
1907 If you just want to boot a kernel once (because you are not sure
1908 if it works, or if you want to boot a known bad kernel to provide
1909 debugging information) run
1910 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1911 nextboot -k testkernel
1913 To rebuild everything and install it on the current system.
1914 -----------------------------------------------------------
1915 # Note: sometimes if you are running current you gotta do more than
1916 # is listed here if you are upgrading from a really old current.
1918 <make sure you have good level 0 dumps>
1920 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1921 make installkernel KERNCONF=YOUR_KERNEL_HERE
1923 <reboot in single user> [3]
1930 To cross-install current onto a separate partition
1931 --------------------------------------------------
1932 # In this approach we use a separate partition to hold
1933 # current's root, 'usr', and 'var' directories. A partition
1934 # holding "/", "/usr" and "/var" should be about 2GB in
1937 <make sure you have good level 0 dumps>
1940 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1941 <maybe newfs current's root partition>
1942 <mount current's root partition on directory ${CURRENT_ROOT}>
1943 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1944 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1945 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1946 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1947 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1948 <reboot into current>
1949 <do a "native" rebuild/install as described in the previous section>
1950 <maybe install compatibility libraries from ports/misc/compat*>
1954 To upgrade in-place from stable to current
1955 ----------------------------------------------
1956 <make sure you have good level 0 dumps>
1958 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1959 make installkernel KERNCONF=YOUR_KERNEL_HERE
1961 <reboot in single user> [3]
1968 Make sure that you've read the UPDATING file to understand the
1969 tweaks to various things you need. At this point in the life
1970 cycle of current, things change often and you are on your own
1971 to cope. The defaults can also change, so please read ALL of
1972 the UPDATING entries.
1974 Also, if you are tracking -current, you must be subscribed to
1975 freebsd-current@freebsd.org. Make sure that before you update
1976 your sources that you have read and understood all the recent
1977 messages there. If in doubt, please track -stable which has
1978 much fewer pitfalls.
1980 [1] If you have third party modules, such as vmware, you
1981 should disable them at this point so they don't crash your
1984 [3] From the bootblocks, boot -s, and then do
1988 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
1989 cd src # full path to source
1990 adjkerntz -i # if CMOS is wall time
1991 Also, when doing a major release upgrade, it is required that
1992 you boot into single user mode to do the installworld.
1994 [4] Note: This step is non-optional. Failure to do this step
1995 can result in a significant reduction in the functionality of the
1996 system. Attempting to do it by hand is not recommended and those
1997 that pursue this avenue should read this file carefully, as well
1998 as the archives of freebsd-current and freebsd-hackers mailing lists
1999 for potential gotchas. The -U option is also useful to consider.
2000 See mergemaster(8) for more information.
2002 [5] Usually this step is a no-op. However, from time to time
2003 you may need to do this if you get unknown user in the following
2004 step. It never hurts to do it all the time. You may need to
2005 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2006 install) after the buildworld before this step if you last updated
2007 from current before 20130425 or from -stable before 20130430.
2009 [6] This only deletes old files and directories. Old libraries
2010 can be deleted by "make delete-old-libs", but you have to make
2011 sure that no program is using those libraries anymore.
2013 [8] The new kernel must be able to run existing binaries used by an
2014 installworld. When upgrading across major versions, the new kernel's
2015 configuration must include the correct COMPAT_FREEBSD<n> option for
2016 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2017 to do so may leave you with a system that is hard to boot to recover. A
2018 GENERIC kernel will include suitable compatibility options to run
2019 binaries from older branches. Note that the ability to run binaries
2020 from unsupported branches is not guaranteed.
2022 Make sure that you merge any new devices from GENERIC since the
2023 last time you updated your kernel config file. Options also
2024 change over time, so you may need to adjust your custom kernels
2027 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2028 "?=" instead of the "=" assignment operator, so that buildworld can
2029 override the CPUTYPE if it needs to.
2031 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2032 not on the command line, or in /etc/make.conf. buildworld will
2033 warn if it is improperly defined.
2036 This file contains a list, in reverse chronological order, of major
2037 breakages in tracking -current. It is not guaranteed to be a complete
2038 list of such breakages, and only contains entries since September 23, 2011.
2039 If you need to see UPDATING entries from before that date, you will need
2040 to fetch an UPDATING file from an older FreeBSD release.
2042 Copyright information:
2044 Copyright 1998-2009 M. Warner Losh.
2046 Redistribution, publication, translation and use, with or without
2047 modification, in full or in part, in any form or format of this
2048 document are permitted without further permission from the author.
2050 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2051 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2052 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2053 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2054 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2055 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2056 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2057 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2058 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2059 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2060 POSSIBILITY OF SUCH DAMAGE.
2062 Contact Warner Losh if you have any questions about your use of