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