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