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