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