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 The IPSEC option has been removed from GENERIC. Users requiring
36 ipsec(4) must now load the ipsec(4) kernel module.
39 The tap(4) driver has been folded into tun(4), and the module has been
40 renamed to tuntap. You should update any kld_load="if_tap" or
41 kld_load="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
42 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
43 module instead, and "device tap" or "device tun" entries in kernel
44 config files to select the tuntap device instead.
47 The following knobs have been added related to tradeoffs between
48 safe use of the random device and availability in the absence of
51 kern.random.initial_seeding.bypass_before_seeding: tunable; set
52 non-zero to bypass the random device prior to seeding, or zero to
53 block random requests until the random device is initially seeded.
54 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
55 availability properties.
57 kern.random.initial_seeding.read_random_bypassed_before_seeding:
58 read-only diagnostic sysctl that is set when bypass is enabled and
59 read_random(9) is bypassed, to enable programmatic handling of this
60 initial condition, if desired.
62 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
63 Similar to the above, but for for arc4random(9) initial seeding.
65 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
66 non-zero to disable warnings in dmesg when the same conditions are
67 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
68 produce warnings in dmesg when the conditions are met.
71 The tunable "security.stack_protect.permit_nonrandom_cookies" may be
72 set to a non-zero value to boot systems that do not provide early
73 entropy. Otherwise, such systems may see the panic message:
74 "cannot initialize stack cookies because random device is not yet
78 The loadable random module KPI has changed; the random_infra_init()
79 routine now requires a 3rd function pointer for a bool (*)(void)
80 method that returns true if the random device is seeded (and
84 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
85 built from head sources between r320757 (July 6, 2017) and
86 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
87 is added to the command line.
88 nfsuserd daemons built from head sources that are post-r338192 are
89 not affected and should continue to work.
92 The fuse(4) module has been renamed to fusefs(4) for consistency with
93 other filesystems. You should update any kld_load="fuse" entries in
94 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
95 "options FUSE" entries in kernel config files.
98 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
99 8.0.0. Please see the 20141231 entry below for information about
100 prerequisites and upgrading, if you are not already using clang 3.5.0
104 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
105 compiled into your custom kernel, add 'device xz' statement to the
109 drm and drm2 have been removed from the tree. Please see
110 https://wiki.freebsd.org/Graphics for the latest information on
111 migrating to the drm ports.
114 Iflib is no longer unconditionally compiled into the kernel. Drivers
115 using iflib and statically compiled into the kernel, now require
116 the 'device iflib' config option. For the same drivers loaded as
117 modules on kernels not having 'device iflib', the iflib.ko module
118 is loaded automatically.
121 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
122 options no longer exist since r343219 and r343427 respectively;
123 nothing uses them, so they should be just removed from custom
127 r342635 changes the way efibootmgr(8) works by requiring users to add
128 the -b (bootnum) parameter for commands where the bootnum was previously
129 specified with each option. For example 'efibootmgr -B 0001' is now
130 'efibootmgr -B -b 0001'.
133 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
134 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
135 servers that have vfs.nfsd.nfs_privport set will only allow mounts
136 from clients using a reserved port#. Since both the FreeBSD and Linux
137 NFSv4 clients use reserved port#s by default, this should not affect
141 The XLP config has been removed. We can't support 64-bit atomics in this
142 kernel because it is running in 32-bit mode. XLP users must transition
143 to running a 64-bit kernel (XLP64 or XLPN32).
145 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
146 the preferred emulator today and we don't need two different ones.
148 The old sibyte / swarm / Broadcom BCM1250 support has been
149 removed from the mips port.
152 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
153 7.0.1. Please see the 20141231 entry below for information about
154 prerequisites and upgrading, if you are not already using clang 3.5.0
158 Remove the timed and netdate programs from the base tree. Setting
159 the time with these daemons has been obsolete for over a decade.
162 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
163 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
164 it produces broken binaries when ifuncs are in use. Users needing
165 GNU ld should install the binutils port or package.
168 The BSD crtbegin and crtend code has been enabled by default. It has
169 had extensive testing on amd64, arm64, and i386. It can be disabled
170 by building a world with -DWITHOUT_BSD_CRTBEGIN.
173 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
174 has been converted to a port (misc/ctm) and will be removed from
175 FreeBSD-13. It is available as a package (ctm) for all supported
179 The default newsyslog.conf(5) file has been changed to only include
180 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
181 the filenames end in '.conf' and do not begin with a '.'.
183 You should check the configuration files in these two directories match
184 this naming convention. You can verify which configuration files are
185 being included using the command:
189 Ports for the DRM modules have been simplified. Now, amd64 users should
190 just install the drm-kmod port. All others should install
193 Graphics hardware that's newer than about 2010 usually works with
194 drm-kmod. For hardware older than 2013, however, some users will need
195 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
196 than 2008 usually only works in drm-legacy-kmod. The graphics team can
197 only commit to hardware made since 2013 due to the complexity of the
198 market and difficulty to test all the older cards effectively. If you
199 have hardware supported by drm-kmod, you are strongly encouraged to use
200 that as you will get better support.
202 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
203 elsewhere, the drm and drm2 modules will be eliminated from the src base
204 soon (with a limited exception for arm). Please update to the package
205 asap and report any issues to x11@freebsd.org.
207 Generally, anybody using the drm*-kmod packages should add
208 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
209 cross-threading surprises, especially with automatic driver
210 loading from X11 startup. These will become the defaults in 13-current
214 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
215 custom kernel and module loading configuration files must be updated
216 accordingly. Moreover, interfaces previous presented as ixlvN to the
217 system are now exposed as iavfN and network configuration files must
218 be adjusted as necessary.
221 OpenSSL has been updated to version 1.1.1. This update included
222 additional various API changes throughout the base system. It is
223 important to rebuild third-party software after upgrading. The value
224 of __FreeBSD_version has been bumped accordingly.
227 The legacy DRM modules and drivers have now been added to the loader's
228 module blacklist, in favor of loading them with kld_list in rc.conf(5).
229 The module blacklist may be overridden with the loader.conf(5)
230 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
234 The cam(4) based nda(4) driver will be used over nvd(4) by default on
235 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
236 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
237 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
241 Reproducible build mode is now on by default, in preparation for
242 FreeBSD 12.0. This eliminates build metadata such as the user,
243 host, and time from the kernel (and uname), unless the working tree
244 corresponds to a modified checkout from a version control system.
245 The previous behavior can be obtained by setting the /etc/src.conf
246 knob WITHOUT_REPRODUCIBLE_BUILD.
249 The Yarrow CSPRNG has been removed from the kernel as it has not been
250 supported by its designers since at least 2003. Fortuna has been the
251 default since FreeBSD-11.
254 devctl freeze/thaw have gone into the tree, the rc scripts have been
255 updated to use them and devmatch has been changed. You should update
256 kernel, userland and rc scripts all at the same time.
259 The default interpreter has been switched from 4th to Lua.
260 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
261 interpreter. If you have custom FORTH code you will need to set
262 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
263 src.conf for the build. This will create default hard links between
264 loader and loader_4th instead of loader and loader_lua, the new default.
265 If you are using UEFI it will create the proper hard link to loader.efi.
267 bhyve uses userboot.so. It remains 4th-only until some issues are solved
268 regarding coexisting with multiple versions of FreeBSD are resolved.
271 ls(1) now respects the COLORTERM environment variable used in other
272 systems and software to indicate that a colored terminal is both
273 supported and desired. If ls(1) is suddenly emitting colors, they may
274 be disabled again by either removing the unwanted COLORTERM from your
275 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
276 may not be observed in a future release.
279 The default pager for most commands has been changed to "less". To
280 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
284 The jedec_ts(4) driver has been removed. A superset of its functionality
285 is available in the jedec_dimm(4) driver, and the manpage for that
286 driver includes migration instructions. If you have "device jedec_ts"
287 in your kernel configuration file, it must be removed.
290 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
291 This should have no effect if the kernel is booted via BIOS/legacy boot.
292 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
293 has a buggy firmware that prevents a successful boot due to use of
297 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
298 support has been removed from the tree. These ports were
299 obsolete and/or known to be broken for many years.
302 loader.efi has been augmented to participate more fully in the
303 UEFI boot manager protocol. loader.efi will now look at the
304 BootXXXX environment variable to determine if a specific kernel
305 or root partition was specified. XXXX is derived from BootCurrent.
306 efibootmgr(8) manages these standard UEFI variables.
309 zfsloader's functionality has now been folded into loader.
310 zfsloader is no longer necessary once you've updated your
311 boot blocks. For a transition period, we will install a
312 hardlink for zfsloader to loader to allow a smooth transition
313 until the boot blocks can be updated (hard link because old
314 zfs boot blocks don't understand symlinks).
317 ARM64 now have efifb support, if you want to have serial console
318 on your arm64 board when an screen is connected and the bootloader
319 setup a frame buffer for us to use, just add :
323 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
324 an screen connected as the firmware will setup a frame buffer are that
325 u-boot will expose as an EFI frame buffer.
328 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
329 or take steps to update /etc/passwd before doing installworld on
330 existing systems. Do not skip the "mergemaster -Fp" step before
331 installworld, as described in the update procedures near the bottom
332 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
333 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
334 the ntp config file contain options that change file/dir locations.
335 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
336 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
337 taking steps to ensure that all required files/dirs are accessible
341 Big endian arm support has been removed.
344 The static environment setup in kernel configs is no longer mutually
345 exclusive with the loader(8) environment by default. In order to
346 restore the previous default behavior of disabling the loader(8)
347 environment if a static environment is present, you must specify
348 loader_env.disabled=1 in the static environment.
351 The ABI of syscalls used by management tools like sockstat and
352 netstat has been broken to allow 32-bit binaries to work on
353 64-bit kernels without modification. These programs will need
354 to match the kernel in order to function. External programs may
355 require minor modifications to accommodate a change of type in
356 structures from pointers to 64-bit virtual addresses.
359 On i386 and amd64 atomics are now inlined. Out of tree modules using
360 atomics will need to be rebuilt.
363 The '%I' format in the kern.corefile sysctl limits the number of
364 core files that a process can generate to the number stored in the
365 debug.ncores sysctl. The '%I' format is replaced by the single digit
366 index. Previously, if all indexes were taken the kernel would overwrite
367 only a core file with the highest index in a filename.
368 Currently the system will create a new core file if there is a free
369 index or if all slots are taken it will overwrite the oldest one.
372 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
373 6.0.1. Please see the 20141231 entry below for information about
374 prerequisites and upgrading, if you are not already using clang 3.5.0
378 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
379 needed to be changed to work with it. This change was made with r335763
380 and requires a mergemaster / etcupdate / etc to update the installed
384 r334930 changed the interface between the NFS modules, so they all
385 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
388 As of r334391 lld is the default amd64 system linker; it is installed
389 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
393 The kernel / userland interface for devinfo changed, so you'll
394 need a new kernel and userland as a pair for it to work (rebuilding
395 lib/libdevinfo is all that's required). devinfo and devmatch will
396 not work, but everything else will when there's a mismatch.
399 The on-disk format for hwpmc callchain records has changed to include
400 threadid corresponding to a given record. This changes the field offsets
401 and thus requires that libpmcstat be rebuilt before using a kernel
405 The vxge(4) driver has been removed. This driver was introduced into
406 HEAD one week before the Exar left the Ethernet market and is not
407 known to be used. If you have device vxge in your kernel config file
411 The amd64 kernel now requires a ld that supports ifunc to produce a
412 working kernel, either lld or a newer binutils. lld is built by default
413 on amd64, and the 'buildkernel' target uses it automatically. However,
414 it is not the default linker, so building the kernel the traditional
415 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
416 binutils port/package). lld will soon be default, and this requirement
419 NOTE: As of r334391 lld is the default system linker on amd64, and no
420 workaround is necessary.
423 The nxge(4) driver has been removed. This driver was for PCI-X 10g
424 cards made by s2io/Neterion. The company was acquired by Exar and
425 no longer sells or supports Ethernet products. If you have device
426 nxge in your kernel config file it must be removed.
429 The tz database (tzdb) has been updated to 2018e. This version more
430 correctly models time stamps in time zones with negative DST such as
431 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
432 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
433 time zone abbreviations and the tm_isdst flag.
436 The ixgb(4) driver has been removed. This driver was for an early and
437 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
438 quickly shifted to the long lived ixgbe family. If you have device
439 ixgb in your kernel config file it must be removed.
442 The lmc(4) driver has been removed. This was a WAN interface
443 card that was already reportedly rare in 2003, and had an ambiguous
444 license. If you have device lmc in your kernel config file it must
448 Support for Arcnet networks has been removed. If you have device
449 arcnet or device cm in your kernel config file they must be
453 Support for FDDI networks has been removed. If you have device
454 fddi or device fpa in your kernel config file they must be
458 In addition to supporting RFC 3164 formatted messages, the
459 syslogd(8) service is now capable of parsing RFC 5424 formatted
460 log messages. The main benefit of using RFC 5424 is that clients
461 may now send log messages with timestamps containing year numbers,
462 microseconds and time zone offsets.
464 Similarly, the syslog(3) C library function has been altered to
465 send RFC 5424 formatted messages to the local system logging
466 daemon. On systems using syslogd(8), this change should have no
467 negative impact, as long as syslogd(8) and the C library are
468 updated at the same time. On systems using a different system
469 logging daemon, it may be necessary to make configuration
470 adjustments, depending on the software used.
472 When using syslog-ng, add the 'syslog-protocol' flag to local
473 input sources to enable parsing of RFC 5424 formatted messages:
476 unix-dgram("/var/run/log" flags(syslog-protocol));
479 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
480 of the 'imuxsock' module to let messages be processed by the
481 regular RFC 3164/5424 parsing pipeline:
483 module(load="imuxsock" SysSock.UseSpecialParser="off")
485 Do note that these changes only affect communication between local
486 applications and syslogd(8). The format that syslogd(8) uses to
487 store messages on disk or forward messages to other systems
488 remains unchanged. syslogd(8) still uses RFC 3164 for these
489 purposes. Options to customize this behaviour will be added in the
490 future. Utilities that process log files stored in /var/log are
491 thus expected to continue to function as before.
493 __FreeBSD_version has been incremented to 1200061 to denote this
497 Support for token ring networks has been removed. If you
498 have "device token" in your kernel config you should remove
499 it. No device drivers supported token ring.
502 makefs was modified to be able to tag ISO9660 El Torito boot catalog
503 entries as EFI instead of overloading the i386 tag as done previously.
504 The amd64 mkisoimages.sh script used to build amd64 ISO images for
505 release was updated to use this. This may mean that makefs must be
506 updated before "make cdrom" can be run in the release directory. This
507 should be as simple as:
509 $ cd $SRCDIR/usr.sbin/makefs
510 $ make depend all install
513 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
514 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
515 Co-existence for the transition period will come shortly. Booting is a
516 complex environment and test coverage for Lua-enabled loaders has been
517 thin, so it would be prudent to assume it might not work and make
518 provisions for backup boot methods.
521 devmatch functionality has been turned on in devd. It will automatically
522 load drivers for unattached devices. This may cause unexpected drivers
523 to be loaded. Please report any problems to current@ and
527 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
528 6.0.0. Please see the 20141231 entry below for information about
529 prerequisites and upgrading, if you are not already using clang 3.5.0
533 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
534 This means it is used to link the kernel and userland libraries and
535 executables, but is not yet installed as /usr/bin/ld by default.
537 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
538 WITHOUT_LLD_BOOTSTRAP=yes
541 On i386, pmtimer has been removed. Its functionality has been folded
542 into apm. It was a no-op on ACPI in current for a while now (but was
543 still needed on i386 in FreeBSD 11 and earlier). Users may need to
544 remove it from kernel config files.
547 The use of RSS hash from the network card aka flowid has been
548 disabled by default for lagg(4) as it's currently incompatible with
549 the lacp and loadbalance protocols.
551 This can be re-enabled by setting the following in loader.conf:
552 net.link.lagg.default_use_flowid="1"
555 The SW_WATCHDOG option is no longer necessary to enable the
556 hardclock-based software watchdog if no hardware watchdog is
557 configured. As before, SW_WATCHDOG will cause the software
558 watchdog to be enabled even if a hardware watchdog is configured.
561 r326887 fixes the issue described in the 20171214 UPDATING entry.
562 r326888 flips the switch back to building GELI support always.
565 r362593 broke ZFS + GELI support for reasons unknown. However,
566 it also broke ZFS support generally, so GELI has been turned off
567 by default as the lesser evil in r326857. If you boot off ZFS and/or
568 GELI, it might not be a good time to update.
571 PowerPC users must update loader(8) by rebuilding world before
572 installing a new kernel, as the protocol connecting them has
573 changed. Without the update, loader metadata will not be passed
574 successfully to the kernel and users will have to enter their
575 root partition at the kernel mountroot prompt to continue booting.
576 Newer versions of loader can boot old kernels without issue.
579 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
580 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
581 to WITH/OUT_LOADER_GELI.
584 The naive and non-compliant support of posix_fallocate(2) in ZFS
585 has been removed as of r325320. The system call now returns EINVAL
586 when used on a ZFS file. Although the new behavior complies with the
587 standard, some consumers are not prepared to cope with it.
588 One known victim is lld prior to r325420.
591 Building in a FreeBSD src checkout will automatically create object
592 directories now rather than store files in the current directory if
593 'make obj' was not ran. Calling 'make obj' is no longer necessary.
594 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
595 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
599 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
600 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
601 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
602 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
603 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
604 The UNIFIED_OBJDIR option is a transitional feature that will be
605 removed for 12.0 release; please migrate to the new format for any
606 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
607 than hardcoding paths.
610 The native-xtools target no longer installs the files by default to the
611 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
612 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
615 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
616 options are changing from controlling the build if defined / undefined
617 to controlling the build with explicit 'yes' or 'no' values. They will
618 shift to WITH/WITHOUT options to match other options in the system.
621 libstand has turned into a private library for sys/boot use only.
622 It is no longer supported as a public interface outside of sys/boot.
625 The arm port has split armv6 into armv6 and armv7. armv7 is now
626 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
627 and are running a kernel from before r324363, you will need to add
628 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
631 When building multiple kernels using KERNCONF, non-existent KERNCONF
632 files will produce an error and buildkernel will fail. Previously
633 missing KERNCONF files silently failed giving no indication as to
634 why, only to subsequently discover during installkernel that the
635 desired kernel was never built in the first place.
638 The default serial number format for CTL LUNs has changed. This will
639 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
640 or iSCSI clients care about their LUNs' serial numbers. Users who
641 require serial number stability should hardcode serial numbers in
645 For 32-bit arm compiled for hard-float support, soft-floating point
646 binaries now always get their shared libraries from
647 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
648 /usr/libsoft also existed). Only users with a hard-float ld.so, but
649 soft-float everything else should be affected.
652 The geli password typed at boot is now hidden. To restore the previous
653 behavior, see geli(8) for configuration options.
656 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
657 sysctl values. Minor nit, but requires a rebuild of both world/kernel
661 "make check" behavior (made in ^/head@r295380) has been changed to
662 execute from a limited sandbox, as opposed to executing from
666 - The "beforecheck" and "aftercheck" targets are now specified.
667 - ${CHECKDIR} (added in commit noted above) has been removed.
668 - Legacy behavior can be enabled by setting
669 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
671 If the limited sandbox mode is enabled, "make check" will execute
672 "make distribution", then install, execute the tests, and clean up the
673 sandbox if successful.
675 The "make distribution" and "make install" targets are typically run as
676 root to set appropriate permissions and ownership at installation time.
677 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
678 environment if executing "make check" with limited sandbox mode using
679 an unprivileged user.
682 Since the switch to GPT disk labels, fsck for UFS/FFS has been
683 unable to automatically find alternate superblocks. As of r322297,
684 the information needed to find alternate superblocks has been
685 moved to the end of the area reserved for the boot block.
686 Filesystems created with a newfs of this vintage or later
687 will create the recovery information. If you have a filesystem
688 created prior to this change and wish to have a recovery block
689 created for your filesystem, you can do so by running fsck in
690 foreground mode (i.e., do not use the -p or -y options). As it
691 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
692 to which you should answer yes.
695 As of r321665, an NFSv4 server configuration that services
696 Kerberos mounts or clients that do not support the uid/gid in
697 owner/owner_group string capability, must explicitly enable
698 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
699 machine's /etc/rc.conf file.
702 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
703 Please see the 20141231 entry below for information about prerequisites
704 and upgrading, if you are not already using clang 3.5.0 or higher.
707 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
708 r-commands (rlogin, rsh, etc.) to be built with the base system.
711 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
712 a very major ABI incompatible change, so users of FreeBSD/powerpc must
713 be careful when performing source upgrades. It is best to run
714 'make installworld' from an alternate root system, either a live
715 CD/memory stick, or a temporary root partition. Additionally, all ports
716 must be recompiled. powerpc64 is largely unaffected, except in the case
717 of 32-bit compatibility. All 32-bit binaries will be affected.
720 Forward compatibility for the "ino64" project have been committed. This
721 will allow most new binaries to run on older kernels in a limited
722 fashion. This prevents many of the common foot-shooting actions in the
723 upgrade as well as the limited ability to roll back the kernel across
724 the ino64 upgrade. Complicated use cases may not work properly, though
725 enough simpler ones work to allow recovery in most situations.
728 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
729 if you require the GPL compiler.
732 The internal ABI used for communication between the NFS kernel modules
733 was changed by r320085, so __FreeBSD_version was bumped to
734 ensure all the NFS related modules are updated together.
737 The ABI of struct event was changed by extending the data
738 member to 64bit and adding ext fields. For upgrade, same
739 precautions as for the entry 20170523 "ino64" must be
743 The GNU roff toolchain has been removed from base. To render manpages
744 which are not supported by mandoc(1), man(1) can fallback on GNU roff
745 from ports (and recommends to install it).
746 To render roff(7) documents, consider using GNU roff from ports or the
747 heirloom doctools roff toolchain from ports via pkg install groff or
748 via pkg install heirloom-doctools.
751 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
752 smaller runtime footprint builds. This is useful for embedded systems
753 which only require one chipset support.
755 If you load it as a module, make sure this is in /boot/loader.conf:
759 This will load the HAL, all chip/RF backends and if_ath_pci.
760 If you have if_ath_pci in /boot/loader.conf, ensure it is after
761 if_ath or it will not load any HAL chipset support.
763 If you want to selectively load things (eg on ye cheape ARM/MIPS
764 platforms where RAM is at a premium) you should:
767 * load the chip modules in question
768 * load ath_rate, ath_dfs
770 * load if_ath_pci and/or if_ath_ahb depending upon your particular
771 bus bind type - this is where probe/attach is done.
773 For further comments/feedback, poke adrian@ .
776 The "ino64" 64-bit inode project has been committed, which extends
777 a number of types to 64 bits. Upgrading in place requires care and
778 adherence to the documented upgrade procedure.
780 If using a custom kernel configuration ensure that the
781 COMPAT_FREEBSD11 option is included (as during the upgrade the
782 system will be running the ino64 kernel with the existing world).
784 For the safest in-place upgrade begin by removing previous build
785 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
786 procedure documented below under the heading "To rebuild everything and
787 install it on the current system." Specifically, a reboot is required
788 after installing the new kernel before installing world. While an
789 installworld normally works by accident from multiuser after rebooting
790 the proper kernel, there are many cases where this will fail across this
791 upgrade and installworld from single user is required.
794 The NATM framework including the en(4), fatm(4), hatm(4), and
795 patm(4) devices has been removed. Consumers should plan a
796 migration before the end-of-life date for FreeBSD 11.
799 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
800 diff has not been implemented, if those are needed a newer version of
801 GNU diff is available via the diffutils package under the gdiff name.
804 As of r316810 for ipfilter, keep frags is no longer assumed when
805 keep state is specified in a rule. r316810 aligns ipfilter with
806 documentation in man pages separating keep frags from keep state.
807 This allows keep state to be specified without forcing keep frags
808 and allows keep frags to be specified independently of keep state.
809 To maintain previous behaviour, also specify keep frags with
810 keep state (as documented in ipf.conf.5).
813 arm64 builds now use the base system LLD 4.0.0 linker by default,
814 instead of requiring that the aarch64-binutils port or package be
815 installed. To continue using aarch64-binutils, set
816 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
819 The UDP optimization in entry 20160818 that added the sysctl
820 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
821 packets will no longer be treated as L3 broadcast packets.
824 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
825 use any explicitly assigned loopback address available in the jail
826 instead of using the first assigned address of the jail.
829 The ctl.ko module no longer implements the iSCSI target frontend:
830 cfiscsi.ko does instead.
832 If building cfiscsi.ko as a kernel module, the module can be loaded
833 via one of the following methods:
834 - `cfiscsi_load="YES"` in loader.conf(5).
835 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
836 - ctladm(8)/ctld(8), when compiled with iSCSI support
837 (`WITH_ISCSI=yes` in src.conf(5))
839 Please see cfiscsi(4) for more details.
842 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
843 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
844 same source (previously, the dependency of mmcsd.ko on mmc.ko was
845 missing, but mmcsd.ko now will refuse to load if it is incompatible
849 The syntax of ipfw(8) named states was changed to avoid ambiguity.
850 If you have used named states in the firewall rules, you need to modify
851 them after installworld and before rebooting. Now named states must
852 be prefixed with colon.
855 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
856 removed as the userland we provide cannot use them. The KMS version
857 (sys/dev/drm2) supports the same hardware.
860 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
861 Please see the 20141231 entry below for information about prerequisites
862 and upgrading, if you are not already using clang 3.5.0 or higher.
865 The code that provides support for ZFS .zfs/ directory functionality
866 has been reimplemented. It's not possible now to create a snapshot
867 by mkdir under .zfs/snapshot/. That should be the only user visible
871 EISA bus support has been removed. The WITH_EISA option is no longer
875 MCA bus support has been removed.
878 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
879 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
882 The EM_MULTIQUEUE kernel configuration option is deprecated now that
883 the em(4) driver conforms to iflib specifications.
886 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
887 IFLIB. If you have a custom kernel configuration that excludes em(4)
888 but you use igb(4), you need to re-add em(4) to your custom
892 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
893 Please see the 20141231 entry below for information about prerequisites
894 and upgrading, if you are not already using clang 3.5.0 or higher.
897 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
898 Please see the 20141231 entry below for information about prerequisites
899 and upgrading, if you are not already using clang 3.5.0 or higher.
902 The layout of the pmap structure has changed for powerpc to put the pmap
903 statistics at the front for all CPU variations. libkvm(3) and all tools
904 that link against it need to be recompiled.
907 isl(4) and cyapa(4) drivers now require a new driver,
908 chromebook_platform(4), to work properly on Chromebook-class hardware.
909 On other types of hardware the drivers may need to be configured using
910 device hints. Please see the corresponding manual pages for details.
913 The urtwn(4) driver was merged into rtwn(4) and now consists of
914 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
916 Also, firmware for RTL8188CE was renamed due to possible name
917 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
920 GNU rcs has been removed from base. It is available as packages:
921 - rcs: Latest GPLv3 GNU rcs version.
922 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
926 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
927 modules now requires that the kernel configuration contain the
928 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
931 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
932 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
935 Relocatable object files with the extension of .So have been renamed
936 to use an extension of .pico instead. The purpose of this change is
937 to avoid a name clash with shared libraries on case-insensitive file
938 systems. On those file systems, foo.So is the same file as foo.so.
941 GNU rcs has been turned off by default. It can (temporarily) be built
942 again by adding WITH_RCS knob in src.conf.
943 Otherwise, GNU rcs is available from packages:
944 - rcs: Latest GPLv3 GNU rcs version.
945 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
948 The backup_uses_rcs functionality has been removed from rc.subr.
951 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
952 two separate components, QUEUE_MACRO_DEBUG_TRACE and
953 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
954 QUEUE_MACRO_DEBUG behavior.
957 r304787 changed some ioctl interfaces between the iSCSI userspace
958 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
959 rebuilt to work with new kernels. __FreeBSD_version has been bumped
963 The UDP receive code has been updated to only treat incoming UDP
964 packets that were addressed to an L2 broadcast address as L3
965 broadcast packets. It is not expected that this will affect any
966 standards-conforming UDP application. The new behaviour can be
967 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
971 Remove the openbsd_poll system call.
972 __FreeBSD_version has been bumped because of this.
975 The stable/11 branch has been created from head@r302406.
978 The libc stub for the pipe(2) system call has been replaced with
979 a wrapper that calls the pipe2(2) system call and the pipe(2)
980 system call is now only implemented by the kernels that include
981 "options COMPAT_FREEBSD10" in their config file (this is the
982 default). Users should ensure that this option is enabled in
983 their kernel or upgrade userspace to r302092 before upgrading their
987 CAM will now strip leading spaces from SCSI disks' serial numbers.
988 This will affect users who create UFS filesystems on SCSI disks using
989 those disk's diskid device nodes. For example, if /etc/fstab
990 previously contained a line like
991 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
992 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
993 transforms like gmirror may also be affected. ZFS users should
997 The bitstring(3) API has been updated with new functionality and
998 improved performance. But it is binary-incompatible with the old API.
999 Objects built with the new headers may not be linked against objects
1000 built with the old headers.
1003 The brk and sbrk functions have been removed from libc on arm64.
1004 Binutils from ports has been updated to not link to these
1005 functions and should be updated to the latest version before
1006 installing a new libc.
1009 The armv6 port now defaults to hard float ABI. Limited support
1010 for running both hardfloat and soft float on the same system
1011 is available using the libraries installed with -DWITH_LIBSOFT.
1012 This has only been tested as an upgrade path for installworld
1013 and packages may fail or need manual intervention to run. New
1014 packages will be needed.
1016 To update an existing self-hosted armv6hf system, you must add
1017 TARGET_ARCH=armv6 on the make command line for both the build
1018 and the install steps.
1021 Kernel modules compiled outside of a kernel build now default to
1022 installing to /boot/modules instead of /boot/kernel. Many kernel
1023 modules built this way (such as those in ports) already overrode
1024 KMODDIR explicitly to install into /boot/modules. However,
1025 manually building and installing a module from /sys/modules will
1026 now install to /boot/modules instead of /boot/kernel.
1029 The CAM I/O scheduler has been committed to the kernel. There should be
1030 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1031 list of known rogues that claim support for this but actually corrupt
1032 data is believed to be complete, be on the lookout for data
1033 corruption. The known rogue list is believed to be complete:
1035 o Crucial MX100, M550 drives with MU01 firmware.
1036 o Micron M510 and M550 drives with MU01 firmware.
1037 o Micron M500 prior to MU07 firmware
1038 o Samsung 830, 840, and 850 all firmwares
1039 o FCCT M500 all firmwares
1041 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1042 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1043 updated firmware. Black listed drives will work correctly because these
1044 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1045 this list is the same as found in Linux, it's believed there are no
1046 other rogues in the market place. All other models from the above
1049 To be safe, if you are at all concerned, you can quirk each of your
1050 drives to prevent NCQ from being sent by setting:
1051 kern.cam.ada.X.quirks="0x2"
1052 in loader.conf. If the drive requires the 4k sector quirk, set the
1053 quirks entry to 0x3.
1056 The FAST_DEPEND build option has been removed and its functionality is
1057 now the one true way. The old mkdep(1) style of 'make depend' has
1058 been removed. See 20160311 for further details.
1061 Resource range types have grown from unsigned long to uintmax_t. All
1062 drivers, and anything using libdevinfo, need to be recompiled.
1065 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1066 builds. It no longer runs mkdep(1) during 'make depend', and the
1067 'make depend' stage can safely be skipped now as it is auto ran
1068 when building 'make all' and will generate all SRCS and DPSRCS before
1069 building anything else. Dependencies are gathered at compile time with
1070 -MF flags kept in separate .depend files per object file. Users should
1071 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1072 stale .depend files.
1075 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1076 kernel modules. Therefore, if you load any kernel modules at boot time,
1077 please install the boot loaders after you install the kernel, but before
1081 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1082 make installkernel KERNCONF=YOUR_KERNEL_HERE
1083 make -C sys/boot install
1084 <reboot in single user>
1086 Then follow the usual steps, described in the General Notes section,
1090 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1091 see the 20141231 entry below for information about prerequisites and
1092 upgrading, if you are not already using clang 3.5.0 or higher.
1095 The AIO subsystem is now a standard part of the kernel. The
1096 VFS_AIO kernel option and aio.ko kernel module have been removed.
1097 Due to stability concerns, asynchronous I/O requests are only
1098 permitted on sockets and raw disks by default. To enable
1099 asynchronous I/O requests on all file types, set the
1100 vfs.aio.enable_unsafe sysctl to a non-zero value.
1103 The ELF object manipulation tool objcopy is now provided by the
1104 ELF Tool Chain project rather than by GNU binutils. It should be a
1105 drop-in replacement, with the addition of arm64 support. The
1106 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1107 to obtain the GNU version if necessary.
1110 Building ZFS pools on top of zvols is prohibited by default. That
1111 feature has never worked safely; it's always been prone to deadlocks.
1112 Using a zvol as the backing store for a VM guest's virtual disk will
1113 still work, even if the guest is using ZFS. Legacy behavior can be
1114 restored by setting vfs.zfs.vol.recursive=1.
1117 The NONE and HPN patches has been removed from OpenSSH. They are
1118 still available in the security/openssh-portable port.
1121 With the addition of ypldap(8), a new _ypldap user is now required
1122 during installworld. "mergemaster -p" can be used to add the user
1123 prior to installworld, as documented in the handbook.
1126 The tftp loader (pxeboot) now uses the option root-path directive. As a
1127 consequence it no longer looks for a pxeboot.4th file on the tftp
1128 server. Instead it uses the regular /boot infrastructure as with the
1132 The code to start recording plug and play data into the modules has
1133 been committed. While the old tools will properly build a new kernel,
1134 a number of warnings about "unknown metadata record 4" will be produced
1135 for an older kldxref. To avoid such warnings, make sure to rebuild
1136 the kernel toolchain (or world). Make sure that you have r292078 or
1137 later when trying to build 292077 or later before rebuilding.
1140 Debug data files are now built by default with 'make buildworld' and
1141 installed with 'make installworld'. This facilitates debugging but
1142 requires more disk space both during the build and for the installed
1143 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1147 r291527 changed the internal interface between the nfsd.ko and
1148 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1149 __FreeBSD_version has been bumped because of this.
1152 Add support for unicode collation strings leads to a change of
1153 order of files listed by ls(1) for example. To get back to the old
1154 behaviour, set LC_COLLATE environment variable to "C".
1156 Databases administrators will need to reindex their databases given
1157 collation results will be different.
1159 Due to a bug in install(1) it is recommended to remove the ancient
1160 locales before running make installworld.
1162 rm -rf /usr/share/locale/*
1165 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1166 libcrypto.so.7 or libssl.so.7 must be recompiled.
1169 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1170 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1171 should be replaced with isp_2400 and isp_2500 modules respectively.
1174 The build previously allowed using 'make -n' to not recurse into
1175 sub-directories while showing what commands would be executed, and
1176 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1177 and 'make -N' will not.
1180 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1181 and etcupdate will now use this file. A custom sendmail.cf is now
1182 updated via this mechanism rather than via installworld. If you had
1183 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1184 want to remove the exclusion or change it to "always install".
1185 /etc/mail/sendmail.cf is now managed the same way regardless of
1186 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1187 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1190 Compatibility shims for legacy ATA device names have been removed.
1191 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1192 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1193 environment variables, /dev/ad* and /dev/ar* symbolic links.
1196 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1197 Please see the 20141231 entry below for information about prerequisites
1198 and upgrading, if you are not already using clang 3.5.0 or higher.
1201 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1202 and renamed from .symbols to .debug. This reduces the size requirements
1203 on the boot partition or file system and provides consistency with
1204 userland debug files.
1206 When using the supported kernel installation method the
1207 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1208 as is done with /boot/kernel.
1210 Developers wishing to maintain the historical behavior of installing
1211 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1214 The wireless drivers had undergone changes that remove the 'parent
1215 interface' from the ifconfig -l output. The rc.d network scripts
1216 used to check presence of a parent interface in the list, so old
1217 scripts would fail to start wireless networking. Thus, etcupdate(3)
1218 or mergemaster(8) run is required after kernel update, to update your
1219 rc.d scripts in /etc.
1222 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1223 These configurations are now automatically interpreted as
1224 'scrub fragment reassemble'.
1227 Kernel-loadable modules for the random(4) device are back. To use
1228 them, the kernel must have
1231 options RANDOM_LOADABLE
1233 kldload(8) can then be used to load random_fortuna.ko
1234 or random_yarrow.ko. Please note that due to the indirect
1235 function calls that the loadable modules need to provide,
1236 the build-in variants will be slightly more efficient.
1238 The random(4) kernel option RANDOM_DUMMY has been retired due to
1239 unpopularity. It was not all that useful anyway.
1242 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1243 Control over building the ELF Tool Chain tools is now provided by
1244 the WITHOUT_TOOLCHAIN knob.
1247 The polarity of Pulse Per Second (PPS) capture events with the
1248 uart(4) driver has been corrected. Prior to this change the PPS
1249 "assert" event corresponded to the trailing edge of a positive PPS
1250 pulse and the "clear" event was the leading edge of the next pulse.
1252 As the width of a PPS pulse in a typical GPS receiver is on the
1253 order of 1 millisecond, most users will not notice any significant
1254 difference with this change.
1256 Anyone who has compensated for the historical polarity reversal by
1257 configuring a negative offset equal to the pulse width will need to
1258 remove that workaround.
1261 The default group assigned to /dev/dri entries has been changed
1262 from 'wheel' to 'video' with the id of '44'. If you want to have
1263 access to the dri devices please add yourself to the video group
1266 # pw groupmod video -m $USER
1269 The menu.rc and loader.rc files will now be replaced during
1270 upgrades. Please migrate local changes to menu.rc.local and
1271 loader.rc.local instead.
1274 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1275 strings and strip have been removed. The src.conf(5) knob
1276 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1279 As ZFS requires more kernel stack pages than is the default on some
1280 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1281 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1283 Please consider using 'options KSTACK_PAGES=X' where X is greater
1284 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1287 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1288 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1289 default, i.e., they will not contain "::". For example, instead
1290 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1291 to have a more specific match, such as different map entries for
1292 IPv6:0:0 vs IPv6:0. This change requires that configuration
1293 data (including maps, files, classes, custom ruleset, etc.) must
1294 use the same format, so make certain such configuration data is
1295 upgrading. As a very simple check search for patterns like
1296 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1297 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1298 the cf option UseCompressedIPv6Addresses.
1301 The default kernel entropy-processing algorithm is now
1302 Fortuna, replacing Yarrow.
1304 Assuming you have 'device random' in your kernel config
1305 file, the configurations allow a kernel option to override
1306 this default. You may choose *ONE* of:
1308 options RANDOM_YARROW # Legacy /dev/random algorithm.
1309 options RANDOM_DUMMY # Blocking-only driver.
1311 If you have neither, you get Fortuna. For most people,
1312 read no further, Fortuna will give a /dev/random that works
1313 like it always used to, and the difference will be irrelevant.
1315 If you remove 'device random', you get *NO* kernel-processed
1316 entropy at all. This may be acceptable to folks building
1317 embedded systems, but has complications. Carry on reading,
1318 and it is assumed you know what you need.
1320 *PLEASE* read random(4) and random(9) if you are in the
1321 habit of tweaking kernel configs, and/or if you are a member
1322 of the embedded community, wanting specific and not-usual
1323 behaviour from your security subsystems.
1325 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1326 random', you will NOT have a functioning /dev/random, and
1327 many cryptographic features will not work, including SSH.
1328 You may also find strange behaviour from the random(3) set
1329 of library functions, in particular sranddev(3), srandomdev(3)
1330 and arc4random(3). The reason for this is that the KERN_ARND
1331 sysctl only returns entropy if it thinks it has some to
1332 share, and with RANDOM_DUMMY or no 'device random' this
1336 An additional fix for the issue described in the 20150614 sendmail
1337 entry below has been committed in revision 284717.
1340 FreeBSD's old make (fmake) has been removed from the system. It is
1341 available as the devel/fmake port or via pkg install fmake.
1344 The fix for the issue described in the 20150614 sendmail entry
1345 below has been committed in revision 284436. The work
1346 around described in that entry is no longer needed unless the
1347 default setting is overridden by a confDH_PARAMETERS configuration
1348 setting of '5' or pointing to a 512 bit DH parameter file.
1351 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1352 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1353 and devel/kyua to version 0.20+ and adjust any calling code to work
1354 with Kyuafile and kyua.
1357 The import of openssl to address the FreeBSD-SA-15:10.openssl
1358 security advisory includes a change which rejects handshakes
1359 with DH parameters below 768 bits. sendmail releases prior
1360 to 8.15.2 (not yet released), defaulted to a 512 bit
1361 DH parameter setting for client connections. To work around
1362 this interoperability, sendmail can be configured to use a
1363 2048 bit DH parameter by:
1365 1. Edit /etc/mail/`hostname`.mc
1366 2. If a setting for confDH_PARAMETERS does not exist or
1367 exists and is set to a string beginning with '5',
1368 replace it with '2'.
1369 3. If a setting for confDH_PARAMETERS exists and is set to
1370 a file path, create a new file with:
1371 openssl dhparam -out /path/to/file 2048
1372 4. Rebuild the .cf file:
1373 cd /etc/mail/; make; make install
1374 5. Restart sendmail:
1375 cd /etc/mail/; make restart
1377 A sendmail patch is coming, at which time this file will be
1381 Generation of legacy formatted entries have been disabled by default
1382 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1383 entries were converted to use the new format by default when the new,
1384 machine independent format have been added and supported since FreeBSD
1387 Please see the pwd_mkdb(8) manual page for further details.
1390 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1391 20141231 entry below for information about prerequisites and upgrading,
1392 if you are not already using 3.5.0 or higher.
1395 TI platform code switched to using vendor DTS files and this update
1396 may break existing systems running on Beaglebone, Beaglebone Black,
1399 - dtb files should be regenerated/reinstalled. Filenames are the
1400 same but content is different now
1401 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1402 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1403 addressing scheme is now pin 25 on /dev/gpioc3.
1404 - Pandaboard: /etc/ttys should be updated, serial console device is
1405 now /dev/ttyu2, not /dev/ttyu0
1408 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1409 If you need the GNU extension from groff soelim(1), install groff
1410 from package: pkg install groff, or via ports: textproc/groff.
1413 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1414 defined in symlink(7); previously symlinks were silently ignored.
1417 The const qualifier has been removed from iconv(3) to comply with
1418 POSIX. The ports tree is aware of this from r384038 onwards.
1421 Libraries specified by LIBADD in Makefiles must have a corresponding
1422 DPADD_<lib> variable to ensure correct dependencies. This is now
1423 enforced in src.libnames.mk.
1426 From legacy ata(4) driver was removed support for SATA controllers
1427 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1428 Kernel modules ataahci and ataadaptec were removed completely,
1429 replaced by ahci and mvs modules respectively.
1432 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1433 the 20141231 entry below for information about prerequisites and
1434 upgrading, if you are not already using 3.5.0 or higher.
1437 The 32-bit PowerPC kernel has been changed to a position-independent
1438 executable. This can only be booted with a version of loader(8)
1439 newer than January 31, 2015, so make sure to update both world and
1440 kernel before rebooting.
1443 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1444 but before r278950, the RNG was not seeded properly. Immediately
1445 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1446 ssh keys or openssl keys) that were generated w/ a kernel from that
1447 range. This does not affect programs that directly used /dev/random
1448 or /dev/urandom. All userland uses of arc4random(3) are affected.
1451 The autofs(4) ABI was changed in order to restore binary compatibility
1452 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1453 with the new kernel.
1456 The powerpc64 kernel has been changed to a position-independent
1457 executable. This can only be booted with a new version of loader(8),
1458 so make sure to update both world and kernel before rebooting.
1461 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1462 only release, no new features have been added. Please see the 20141231
1463 entry below for information about prerequisites and upgrading, if you
1464 are not already using 3.5.0.
1467 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1468 taken from the ELF Tool Chain project rather than GNU binutils. They
1469 should be drop-in replacements, with the addition of arm64 support.
1470 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1471 binutils tools, if necessary. See 20150805 for updated information.
1474 The default Unbound configuration now enables remote control
1475 using a local socket. Users who have already enabled the
1476 local_unbound service should regenerate their configuration
1477 by running "service local_unbound setup" as root.
1480 The GNU texinfo and GNU info pages have been removed.
1481 To be able to view GNU info pages please install texinfo from ports.
1484 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1486 As of this release, a prerequisite for building clang, llvm and lldb is
1487 a C++11 capable compiler and C++11 standard library. This means that to
1488 be able to successfully build the cross-tools stage of buildworld, with
1489 clang as the bootstrap compiler, your system compiler or cross compiler
1490 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1491 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1494 On any standard FreeBSD 10.x or 11.x installation, where clang and
1495 libc++ are on by default (that is, on x86 or arm), this should work out
1498 On 9.x installations where clang is enabled by default, e.g. on x86 and
1499 powerpc, libc++ will not be enabled by default, so libc++ should be
1500 built (with clang) and installed first. If both clang and libc++ are
1501 missing, build clang first, then use it to build libc++.
1503 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1504 the instructions for 9.x above.
1506 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1507 default, and do not build clang.
1509 Many embedded systems are resource constrained, and will not be able to
1510 build clang in a reasonable time, or in some cases at all. In those
1511 cases, cross building bootable systems on amd64 is a workaround.
1513 This new version of clang introduces a number of new warnings, of which
1514 the following are most likely to appear:
1518 This warns in two cases, for both C and C++:
1519 * When the code is trying to take the absolute value of an unsigned
1520 quantity, which is effectively a no-op, and almost never what was
1521 intended. The code should be fixed, if at all possible. If you are
1522 sure that the unsigned quantity can be safely cast to signed, without
1523 loss of information or undefined behavior, you can add an explicit
1524 cast, or disable the warning.
1526 * When the code is trying to take an absolute value, but the called
1527 abs() variant is for the wrong type, which can lead to truncation.
1528 If you want to disable the warning instead of fixing the code, please
1529 make sure that truncation will not occur, or it might lead to unwanted
1532 -Wtautological-undefined-compare and
1533 -Wundefined-bool-conversion
1535 These warn when C++ code is trying to compare 'this' against NULL, while
1536 'this' should never be NULL in well-defined C++ code. However, there is
1537 some legacy (pre C++11) code out there, which actively abuses this
1538 feature, which was less strictly defined in previous C++ versions.
1540 Squid and openjdk do this, for example. The warning can be turned off
1541 for C++98 and earlier, but compiling the code in C++11 mode might result
1542 in unexpected behavior; for example, the parts of the program that are
1543 unreachable could be optimized away.
1546 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1547 kernel sources have been removed. The .h files remain, since some
1548 utilities include them. This will need to be fixed later.
1549 If "mount -t oldnfs ..." is attempted, it will fail.
1550 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1551 the utilities will report errors.
1554 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1555 directories to top level SUBDIR variable when their parent
1556 directory is included in LOCAL_DIRS. Users with build systems with
1557 such hierarchies and without SUBDIR entries in the parent
1558 directory Makefiles should add them or add the directories to
1562 faith(4) and faithd(8) have been removed from the base system. Faith
1563 has been obsolete for a very long time.
1566 vt(4), the new console driver, is enabled by default. It brings
1567 support for Unicode and double-width characters, as well as
1568 support for UEFI and integration with the KMS kernel video
1571 You may need to update your console settings in /etc/rc.conf,
1572 most probably the keymap. During boot, /etc/rc.d/syscons will
1573 indicate what you need to do.
1575 vt(4) still has issues and lacks some features compared to
1576 syscons(4). See the wiki for up-to-date information:
1577 https://wiki.freebsd.org/Newcons
1579 If you want to keep using syscons(4), you can do so by adding
1580 the following line to /boot/loader.conf:
1584 pjdfstest has been integrated into kyua as an opt-in test suite.
1585 Please see share/doc/pjdfstest/README for more details on how to
1589 gperf has been removed from the base system for architectures
1590 that use clang. Ports that require gperf will obtain it from the
1594 pjdfstest has been moved from tools/regression/pjdfstest to
1598 At svn r271982, The default linux compat kernel ABI has been adjusted
1599 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1600 update. If you wish to continue using the linux-f10 compat ports,
1601 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1602 encouraged to update their linux-compat packages to linux-c6 during
1603 their next update cycle.
1606 The ofwfb driver, used to provide a graphics console on PowerPC when
1607 using vt(4), no longer allows mmap() of all physical memory. This
1608 will prevent Xorg on PowerPC with some ATI graphics cards from
1609 initializing properly unless x11-servers/xorg-server is updated to
1613 The xdev targets have been converted to using TARGET and
1614 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1617 The default unbound configuration has been modified to address
1618 issues with reverse lookups on networks that use private
1619 address ranges. If you use the local_unbound service, run
1620 "service local_unbound setup" as root to regenerate your
1621 configuration, then "service local_unbound reload" to load the
1625 The GNU texinfo and GNU info pages are not built and installed
1626 anymore, WITH_INFO knob has been added to allow to built and install
1628 UPDATE: see 20150102 entry on texinfo's removal
1631 The GNU readline library is now an INTERNALLIB - that is, it is
1632 statically linked into consumers (GDB and variants) in the base
1633 system, and the shared library is no longer installed. The
1634 devel/readline port is available for third party software that
1638 The Itanium architecture (ia64) has been removed from the list of
1639 known architectures. This is the first step in the removal of the
1643 Commit r268115 has added NFSv4.1 server support, merged from
1644 projects/nfsv4.1-server. Since this includes changes to the
1645 internal interfaces between the NFS related modules, a full
1646 build of the kernel and modules will be necessary.
1647 __FreeBSD_version has been bumped.
1650 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1651 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1652 which differs from the behaviour controlled by this knob.)
1655 Maximal length of the serial number in CTL was increased from 16 to
1656 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1657 and ctld, need to be rebuilt to work with a new kernel.
1660 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1661 1 respectively to match the upstream numbers. They were out of
1662 sync because, when they were originally added to FreeBSD, the
1663 upstream versions were not respected. These libraries are private
1664 and not yet built by default, so renumbering them should be a
1665 non-issue. However, unclean source trees will yield broken test
1666 programs once the operator executes "make delete-old-libs" after a
1667 "make installworld".
1669 Additionally, the atf-sh binary was made private by moving it into
1670 /usr/libexec/. Already-built shell test programs will keep the
1671 path to the old binary so they will break after "make delete-old"
1674 If you are using WITH_TESTS=yes (not the default), wipe the object
1675 tree and rebuild from scratch to prevent spurious test failures.
1676 This is only needed once: the misnumbered libraries and misplaced
1677 binaries have been added to OptionalObsoleteFiles.inc so they will
1678 be removed during a clean upgrade.
1681 Clang and llvm have been upgraded to 3.4.1 release.
1684 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1685 be removed to avoid issues in the future (and has been added to
1689 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1690 past, it affected all builds that used the bsd.*.mk files. The old
1691 behavior was a bug, but people may have relied upon it. To get this
1692 behavior back, you can .include /etc/src.conf from /etc/make.conf
1693 (which is still global and isn't changed). This also changes the
1694 behavior of incremental builds inside the tree of individual
1695 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1696 Although this has survived make universe and some upgrade scenarios,
1697 other upgrade scenarios may have broken. At least one form of
1698 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1699 as well... In cases where MAKESYSPATH isn't working with this
1700 setting, you'll need to set it to the full path to your tree.
1702 One side effect of all this cleaning up is that bsd.compiler.mk
1703 is no longer implicitly included by bsd.own.mk. If you wish to
1704 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1708 The lindev device has been removed since /dev/full has been made a
1709 standard device. __FreeBSD_version has been bumped.
1712 The knob WITHOUT_VI was added to the base system, which controls
1713 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1714 in order to reorder files share/termcap and didn't build ex(1) as a
1715 build tool, so building/installing with WITH_VI is highly advised for
1716 build hosts for older releases.
1718 This issue has been fixed in stable/9 and stable/10 in r277022 and
1719 r276991, respectively.
1722 The YES_HESIOD knob has been removed. It has been obsolete for
1723 a decade. Please move to using WITH_HESIOD instead or your builds
1724 will silently lack HESIOD.
1727 The uart(4) driver has been changed with respect to its handling
1728 of the low-level console. Previously the uart(4) driver prevented
1729 any process from changing the baudrate or the CLOCAL and HUPCL
1730 control flags. By removing the restrictions, operators can make
1731 changes to the serial console port without having to reboot.
1732 However, when getty(8) is started on the serial device that is
1733 associated with the low-level console, a misconfigured terminal
1734 line in /etc/ttys will now have a real impact.
1735 Before upgrading the kernel, make sure that /etc/ttys has the
1736 serial console device configured as 3wire without baudrate to
1737 preserve the previous behaviour. E.g:
1738 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1741 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1742 to improve performance. To re-enable it, if needed, run rpcbind
1743 with command line option -W.
1746 Switched back to the GPL dtc compiler due to updates in the upstream
1747 dts files not being supported by the BSDL dtc compiler. You will need
1748 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1749 may result while building dtb files during a kernel build if you fail
1750 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1753 Clang and llvm have been upgraded to 3.4 release.
1756 The nve(4) driver has been removed. Please use the nfe(4) driver
1757 for NVIDIA nForce MCP Ethernet adapters instead.
1760 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1761 This could cause certain C++ applications using shared libraries built
1762 against the previous version of libc++ to crash. The incompatibility
1763 has now been fixed, but any C++ applications or shared libraries built
1764 between r261283 and r261801 should be recompiled.
1767 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1768 capability mode support. Please note that enabling the feature in
1769 kernel is still highly recommended.
1772 OpenSSH is now built with sandbox support, and will use sandbox as
1773 the default privilege separation method. This requires Capsicum
1774 capability mode support in kernel.
1777 The libelf and libdwarf libraries have been updated to newer
1778 versions from upstream. Shared library version numbers for
1779 these two libraries were bumped. Any ports or binaries
1780 requiring these two libraries should be recompiled.
1781 __FreeBSD_version is bumped to 1100006.
1784 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1785 instead of providing an explicit one, this would prevent such
1786 Makefile from providing its own Kyuafile in the future during
1787 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1788 intervention is needed to clean an objdir if you use NO_CLEAN:
1789 # find /usr/obj -name Kyuafile | xargs rm -f
1792 The behavior of gss_pseudo_random() for the krb5 mechanism
1793 has changed, for applications requesting a longer random string
1794 than produced by the underlying enctype's pseudo-random() function.
1795 In particular, the random string produced from a session key of
1796 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1797 be different at the 17th octet and later, after this change.
1798 The counter used in the PRF+ construction is now encoded as a
1799 big-endian integer in accordance with RFC 4402.
1800 __FreeBSD_version is bumped to 1100004.
1803 The WITHOUT_ATF build knob has been removed and its functionality
1804 has been subsumed into the more generic WITHOUT_TESTS. If you were
1805 using the former to disable the build of the ATF libraries, you
1806 should change your settings to use the latter.
1809 The default version of mtree is nmtree which is obtained from
1810 NetBSD. The output is generally the same, but may vary
1811 slightly. If you found you need identical output adding
1812 "-F freebsd9" to the command line should do the trick. For the
1813 time being, the old mtree is available as fmtree.
1816 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1817 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1818 1.1.4_8 and verify bsdyml not linked in, before running "make
1820 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1822 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1825 The stable/10 branch has been created in subversion from head
1832 Avoid using make -j when upgrading. While generally safe, there are
1833 sometimes problems using -j to upgrade. If your upgrade fails with
1834 -j, please try again without -j. From time to time in the past there
1835 have been problems using -j with buildworld and/or installworld. This
1836 is especially true when upgrading between "distant" versions (eg one
1837 that cross a major release boundary or several minor releases, or when
1838 several months have passed on the -current branch).
1840 Sometimes, obscure build problems are the result of environment
1841 poisoning. This can happen because the make utility reads its
1842 environment when searching for values for global variables. To run
1843 your build attempts in an "environmental clean room", prefix all make
1844 commands with 'env -i '. See the env(1) manual page for more details.
1846 When upgrading from one major version to another it is generally best to
1847 upgrade to the latest code in the currently installed branch first, then
1848 do an upgrade to the new branch. This is the best-tested upgrade path,
1849 and has the highest probability of being successful. Please try this
1850 approach if you encounter problems with a major version upgrade. Since
1851 the stable 4.x branch point, one has generally been able to upgrade from
1852 anywhere in the most recent stable branch to head / current (or even the
1853 last couple of stable branches). See the top of this file when there's
1856 When upgrading a live system, having a root shell around before
1857 installing anything can help undo problems. Not having a root shell
1858 around can lead to problems if pam has changed too much from your
1859 starting point to allow continued authentication after the upgrade.
1861 This file should be read as a log of events. When a later event changes
1862 information of a prior event, the prior event should not be deleted.
1863 Instead, a pointer to the entry with the new information should be
1864 placed in the old entry. Readers of this file should also sanity check
1865 older entries before relying on them blindly. Authors of new entries
1866 should write them with this in mind.
1870 When upgrading the boot ZFS pool to a new version, always follow
1873 1.) recompile and reinstall the ZFS boot loader and boot block
1874 (this is part of "make buildworld" and "make installworld")
1876 2.) update the ZFS boot block on your boot drive
1878 The following example updates the ZFS boot block on the first
1879 partition (freebsd-boot) of a GPT partitioned drive ada0:
1880 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1882 Non-boot pools do not need these updates.
1886 If you are updating from a prior version of FreeBSD (even one just
1887 a few days old), you should follow this procedure. It is the most
1888 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1890 make kernel-toolchain
1891 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1892 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1894 To test a kernel once
1895 ---------------------
1896 If you just want to boot a kernel once (because you are not sure
1897 if it works, or if you want to boot a known bad kernel to provide
1898 debugging information) run
1899 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1900 nextboot -k testkernel
1902 To rebuild everything and install it on the current system.
1903 -----------------------------------------------------------
1904 # Note: sometimes if you are running current you gotta do more than
1905 # is listed here if you are upgrading from a really old current.
1907 <make sure you have good level 0 dumps>
1909 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1910 make installkernel KERNCONF=YOUR_KERNEL_HERE
1912 <reboot in single user> [3]
1919 To cross-install current onto a separate partition
1920 --------------------------------------------------
1921 # In this approach we use a separate partition to hold
1922 # current's root, 'usr', and 'var' directories. A partition
1923 # holding "/", "/usr" and "/var" should be about 2GB in
1926 <make sure you have good level 0 dumps>
1929 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1930 <maybe newfs current's root partition>
1931 <mount current's root partition on directory ${CURRENT_ROOT}>
1932 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1933 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1934 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1935 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1936 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1937 <reboot into current>
1938 <do a "native" rebuild/install as described in the previous section>
1939 <maybe install compatibility libraries from ports/misc/compat*>
1943 To upgrade in-place from stable to current
1944 ----------------------------------------------
1945 <make sure you have good level 0 dumps>
1947 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1948 make installkernel KERNCONF=YOUR_KERNEL_HERE
1950 <reboot in single user> [3]
1957 Make sure that you've read the UPDATING file to understand the
1958 tweaks to various things you need. At this point in the life
1959 cycle of current, things change often and you are on your own
1960 to cope. The defaults can also change, so please read ALL of
1961 the UPDATING entries.
1963 Also, if you are tracking -current, you must be subscribed to
1964 freebsd-current@freebsd.org. Make sure that before you update
1965 your sources that you have read and understood all the recent
1966 messages there. If in doubt, please track -stable which has
1967 much fewer pitfalls.
1969 [1] If you have third party modules, such as vmware, you
1970 should disable them at this point so they don't crash your
1973 [3] From the bootblocks, boot -s, and then do
1977 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
1978 cd src # full path to source
1979 adjkerntz -i # if CMOS is wall time
1980 Also, when doing a major release upgrade, it is required that
1981 you boot into single user mode to do the installworld.
1983 [4] Note: This step is non-optional. Failure to do this step
1984 can result in a significant reduction in the functionality of the
1985 system. Attempting to do it by hand is not recommended and those
1986 that pursue this avenue should read this file carefully, as well
1987 as the archives of freebsd-current and freebsd-hackers mailing lists
1988 for potential gotchas. The -U option is also useful to consider.
1989 See mergemaster(8) for more information.
1991 [5] Usually this step is a no-op. However, from time to time
1992 you may need to do this if you get unknown user in the following
1993 step. It never hurts to do it all the time. You may need to
1994 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1995 install) after the buildworld before this step if you last updated
1996 from current before 20130425 or from -stable before 20130430.
1998 [6] This only deletes old files and directories. Old libraries
1999 can be deleted by "make delete-old-libs", but you have to make
2000 sure that no program is using those libraries anymore.
2002 [8] The new kernel must be able to run existing binaries used by an
2003 installworld. When upgrading across major versions, the new kernel's
2004 configuration must include the correct COMPAT_FREEBSD<n> option for
2005 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2006 to do so may leave you with a system that is hard to boot to recover. A
2007 GENERIC kernel will include suitable compatibility options to run
2008 binaries from older branches. Note that the ability to run binaries
2009 from unsupported branches is not guaranteed.
2011 Make sure that you merge any new devices from GENERIC since the
2012 last time you updated your kernel config file. Options also
2013 change over time, so you may need to adjust your custom kernels
2016 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2017 "?=" instead of the "=" assignment operator, so that buildworld can
2018 override the CPUTYPE if it needs to.
2020 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2021 not on the command line, or in /etc/make.conf. buildworld will
2022 warn if it is improperly defined.
2025 This file contains a list, in reverse chronological order, of major
2026 breakages in tracking -current. It is not guaranteed to be a complete
2027 list of such breakages, and only contains entries since September 23, 2011.
2028 If you need to see UPDATING entries from before that date, you will need
2029 to fetch an UPDATING file from an older FreeBSD release.
2031 Copyright information:
2033 Copyright 1998-2009 M. Warner Losh.
2035 Redistribution, publication, translation and use, with or without
2036 modification, in full or in part, in any form or format of this
2037 document are permitted without further permission from the author.
2039 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2040 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2041 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2042 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2043 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2044 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2045 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2046 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2047 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2048 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2049 POSSIBILITY OF SUCH DAMAGE.
2051 Contact Warner Losh if you have any questions about your use of