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