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