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