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