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 tap(4) driver has been folded into tun(4), and the module has been
36 renamed to tuntap. You should update any kld_load="if_tap" or
37 kld_load="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
38 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
39 module instead, and "device tap" or "device tun" entries in kernel
40 config files to select the tuntap device instead.
43 The following knobs have been added related to tradeoffs between
44 safe use of the random device and availability in the absence of
47 kern.random.initial_seeding.bypass_before_seeding: tunable; set
48 non-zero to bypass the random device prior to seeding, or zero to
49 block random requests until the random device is initially seeded.
50 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
51 availability properties.
53 kern.random.initial_seeding.read_random_bypassed_before_seeding:
54 read-only diagnostic sysctl that is set when bypass is enabled and
55 read_random(9) is bypassed, to enable programmatic handling of this
56 initial condition, if desired.
58 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
59 Similar to the above, but for for arc4random(9) initial seeding.
61 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
62 non-zero to disable warnings in dmesg when the same conditions are
63 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
64 produce warnings in dmesg when the conditions are met.
67 The tunable "security.stack_protect.permit_nonrandom_cookies" may be
68 set to a non-zero value to boot systems that do not provide early
69 entropy. Otherwise, such systems may see the panic message:
70 "cannot initialize stack cookies because random device is not yet
74 The loadable random module KPI has changed; the random_infra_init()
75 routine now requires a 3rd function pointer for a bool (*)(void)
76 method that returns true if the random device is seeded (and
80 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
81 built from head sources between r320757 (July 6, 2017) and
82 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
83 is added to the command line.
84 nfsuserd daemons built from head sources that are post-r338192 are
85 not affected and should continue to work.
88 The fuse(4) module has been renamed to fusefs(4) for consistency with
89 other filesystems. You should update any kld_load="fuse" entries in
90 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
91 "options FUSE" enties in kernel config files.
94 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
95 8.0.0. Please see the 20141231 entry below for information about
96 prerequisites and upgrading, if you are not already using clang 3.5.0
100 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
101 compiled into your custom kernel, add 'device xz' statement to the
105 drm and drm2 have been removed from the tree. Please see
106 https://wiki.freebsd.org/Graphics for the latest information on
107 migrating to the drm ports.
110 Iflib is no longer unconditionally compiled into the kernel. Drivers
111 using iflib and statically compiled into the kernel, now require
112 the 'device iflib' config option. For the same drivers loaded as
113 modules on kernels not having 'device iflib', the iflib.ko module
114 is loaded automatically.
117 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
118 options no longer exist since r343219 and r343427 respectively;
119 nothing uses them, so they should be just removed from custom
123 r342635 changes the way efibootmgr(8) works by requiring users to add
124 the -b (bootnum) parameter for commands where the bootnum was previously
125 specified with each option. For example 'efibootmgr -B 0001' is now
126 'efibootmgr -B -b 0001'.
129 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
130 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
131 servers that have vfs.nfsd.nfs_privport set will only allow mounts
132 from clients using a reserved port#. Since both the FreeBSD and Linux
133 NFSv4 clients use reserved port#s by default, this should not affect
137 The XLP config has been removed. We can't support 64-bit atomics in this
138 kernel because it is running in 32-bit mode. XLP users must transition
139 to running a 64-bit kernel (XLP64 or XLPN32).
141 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
142 the preferred emulator today and we don't need two different ones.
144 The old sibyte / swarm / Broadcom BCM1250 support has been
145 removed from the mips port.
148 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
149 7.0.1. Please see the 20141231 entry below for information about
150 prerequisites and upgrading, if you are not already using clang 3.5.0
154 Remove the timed and netdate programs from the base tree. Setting
155 the time with these deamons has been obsolete for over a decade.
158 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
159 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
160 it produces broken binaries when ifuncs are in use. Users needing
161 GNU ld should install the binutils port or package.
164 The BSD crtbegin and crtend code has been enabled by default. It has
165 had extensive testing on amd64, arm64, and i386. It can be disabled
166 by building a world with -DWITHOUT_BSD_CRTBEGIN.
169 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
170 has been converted to a port (misc/ctm) and will be removed from
171 FreeBSD-13. It is available as a package (ctm) for all supported
175 The default newsyslog.conf(5) file has been changed to only include
176 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
177 the filenames end in '.conf' and do not begin with a '.'.
179 You should check the configuration files in these two directories match
180 this naming convention. You can verify which configuration files are
181 being included using the command:
185 Ports for the DRM modules have been simplified. Now, amd64 users should
186 just install the drm-kmod port. All others should install
189 Graphics hardware that's newer than about 2010 usually works with
190 drm-kmod. For hardware older than 2013, however, some users will need
191 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
192 than 2008 usually only works in drm-legacy-kmod. The graphics team can
193 only commit to hardware made since 2013 due to the complexity of the
194 market and difficulty to test all the older cards effectively. If you
195 have hardware supported by drm-kmod, you are strongly encouraged to use
196 that as you will get better support.
198 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
199 elsewhere, the drm and drm2 modules will be eliminated from the src base
200 soon (with a limited exception for arm). Please update to the package
201 asap and report any issues to x11@freebsd.org.
203 Generally, anybody using the drm*-kmod packages should add
204 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
205 cross-threading surprises, especially with automatic driver
206 loading from X11 startup. These will become the defaults in 13-current
210 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
211 custom kernel and module loading configuration files must be updated
212 accordingly. Moreover, interfaces previous presented as ixlvN to the
213 system are now exposed as iavfN and network configuration files must
214 be adjusted as necessary.
217 OpenSSL has been updated to version 1.1.1. This update included
218 additional various API changes througout the base system. It is
219 important to rebuild third-party software after upgrading. The value
220 of __FreeBSD_version has been bumped accordingly.
223 The legacy DRM modules and drivers have now been added to the loader's
224 module blacklist, in favor of loading them with kld_list in rc.conf(5).
225 The module blacklist may be overridden with the loader.conf(5)
226 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
230 The cam(4) based nda(4) driver will be used over nvd(4) by default on
231 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
232 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
233 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
237 Reproducible build mode is now on by default, in preparation for
238 FreeBSD 12.0. This eliminates build metadata such as the user,
239 host, and time from the kernel (and uname), unless the working tree
240 corresponds to a modified checkout from a version control system.
241 The previous behavior can be obtained by setting the /etc/src.conf
242 knob WITHOUT_REPRODUCIBLE_BUILD.
245 The Yarrow CSPRNG has been removed from the kernel as it has not been
246 supported by its designers since at least 2003. Fortuna has been the
247 default since FreeBSD-11.
250 devctl freeze/thaw have gone into the tree, the rc scripts have been
251 updated to use them and devmatch has been changed. You should update
252 kernel, userland and rc scripts all at the same time.
255 The default interpreter has been switched from 4th to Lua.
256 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
257 interpreter. If you have custom FORTH code you will need to set
258 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
259 src.conf for the build. This will create default hard links between
260 loader and loader_4th instead of loader and loader_lua, the new default.
261 If you are using UEFI it will create the proper hard link to loader.efi.
263 bhyve uses userboot.so. It remains 4th-only until some issues are solved
264 regarding coexisting with multiple versions of FreeBSD are resolved.
267 ls(1) now respects the COLORTERM environment variable used in other
268 systems and software to indicate that a colored terminal is both
269 supported and desired. If ls(1) is suddenly emitting colors, they may
270 be disabled again by either removing the unwanted COLORTERM from your
271 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
272 may not be observed in a future release.
275 The default pager for most commands has been changed to "less". To
276 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
280 The jedec_ts(4) driver has been removed. A superset of its functionality
281 is available in the jedec_dimm(4) driver, and the manpage for that
282 driver includes migration instructions. If you have "device jedec_ts"
283 in your kernel configuration file, it must be removed.
286 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
287 This should have no effect if the kernel is booted via BIOS/legacy boot.
288 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
289 has a buggy firmware that prevents a successful boot due to use of
293 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
294 support has been removed from the tree. These ports were
295 obsolete and/or known to be broken for many years.
298 loader.efi has been augmented to participate more fully in the
299 UEFI boot manager protocol. loader.efi will now look at the
300 BootXXXX environment variable to determine if a specific kernel
301 or root partition was specified. XXXX is derived from BootCurrent.
302 efibootmgr(8) manages these standard UEFI variables.
305 zfsloader's functionality has now been folded into loader.
306 zfsloader is no longer necessary once you've updated your
307 boot blocks. For a transition period, we will install a
308 hardlink for zfsloader to loader to allow a smooth transition
309 until the boot blocks can be updated (hard link because old
310 zfs boot blocks don't understand symlinks).
313 ARM64 now have efifb support, if you want to have serial console
314 on your arm64 board when an screen is connected and the bootloader
315 setup a framebuffer for us to use, just add :
319 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
320 an screen connected as the firmware will setup a framebuffer are that
321 u-boot will expose as an EFI framebuffer.
324 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
325 or take steps to update /etc/passwd before doing installworld on
326 existing systems. Do not skip the "mergemaster -Fp" step before
327 installworld, as described in the update procedures near the bottom
328 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
329 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
330 the ntp config file contain options that change file/dir locations.
331 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
332 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
333 taking steps to ensure that all required files/dirs are accessible
337 Big endian arm support has been removed.
340 The static environment setup in kernel configs is no longer mutually
341 exclusive with the loader(8) environment by default. In order to
342 restore the previous default behavior of disabling the loader(8)
343 environment if a static environment is present, you must specify
344 loader_env.disabled=1 in the static environment.
347 The ABI of syscalls used by management tools like sockstat and
348 netstat has been broken to allow 32-bit binaries to work on
349 64-bit kernels without modification. These programs will need
350 to match the kernel in order to function. External programs may
351 require minor modifications to accommodate a change of type in
352 structures from pointers to 64-bit virtual addresses.
355 On i386 and amd64 atomics are now inlined. Out of tree modules using
356 atomics will need to be rebuilt.
359 The '%I' format in the kern.corefile sysctl limits the number of
360 core files that a process can generate to the number stored in the
361 debug.ncores sysctl. The '%I' format is replaced by the single digit
362 index. Previously, if all indexes were taken the kernel would overwrite
363 only a core file with the highest index in a filename.
364 Currently the system will create a new core file if there is a free
365 index or if all slots are taken it will overwrite the oldest one.
368 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
369 6.0.1. Please see the 20141231 entry below for information about
370 prerequisites and upgrading, if you are not already using clang 3.5.0
374 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
375 needed to be changed to work with it. This change was made with r335763
376 and requires a mergemaster / etcupdate / etc to update the installed
380 r334930 changed the interface between the NFS modules, so they all
381 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
384 As of r334391 lld is the default amd64 system linker; it is installed
385 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
389 The kernel / userland interface for devinfo changed, so you'll
390 need a new kernel and userland as a pair for it to work (rebuilding
391 lib/libdevinfo is all that's required). devinfo and devmatch will
392 not work, but everything else will when there's a mismatch.
395 The on-disk format for hwpmc callchain records has changed to include
396 threadid corresponding to a given record. This changes the field offsets
397 and thus requires that libpmcstat be rebuilt before using a kernel
401 The vxge(4) driver has been removed. This driver was introduced into
402 HEAD one week before the Exar left the Ethernet market and is not
403 known to be used. If you have device vxge in your kernel config file
407 The amd64 kernel now requires a ld that supports ifunc to produce a
408 working kernel, either lld or a newer binutils. lld is built by default
409 on amd64, and the 'buildkernel' target uses it automatically. However,
410 it is not the default linker, so building the kernel the traditional
411 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
412 binutils port/package). lld will soon be default, and this requirement
415 NOTE: As of r334391 lld is the default system linker on amd64, and no
416 workaround is necessary.
419 The nxge(4) driver has been removed. This driver was for PCI-X 10g
420 cards made by s2io/Neterion. The company was aquired by Exar and
421 no longer sells or supports Ethernet products. If you have device
422 nxge in your kernel config file it must be removed.
425 The tz database (tzdb) has been updated to 2018e. This version more
426 correctly models time stamps in time zones with negative DST such as
427 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
428 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
429 time zone abbreviations and the tm_isdst flag.
432 The ixgb(4) driver has been removed. This driver was for an early and
433 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
434 quickly shifted to the long lived ixgbe family. If you have device
435 ixgb in your kernel config file it must be removed.
438 The lmc(4) driver has been removed. This was a WAN interface
439 card that was already reportedly rare in 2003, and had an ambiguous
440 license. If you have device lmc in your kernel config file it must
444 Support for Arcnet networks has been removed. If you have device
445 arcnet or device cm in your kernel config file they must be
449 Support for FDDI networks has been removed. If you have device
450 fddi or device fpa in your kernel config file they must be
454 In addition to supporting RFC 3164 formatted messages, the
455 syslogd(8) service is now capable of parsing RFC 5424 formatted
456 log messages. The main benefit of using RFC 5424 is that clients
457 may now send log messages with timestamps containing year numbers,
458 microseconds and time zone offsets.
460 Similarly, the syslog(3) C library function has been altered to
461 send RFC 5424 formatted messages to the local system logging
462 daemon. On systems using syslogd(8), this change should have no
463 negative impact, as long as syslogd(8) and the C library are
464 updated at the same time. On systems using a different system
465 logging daemon, it may be necessary to make configuration
466 adjustments, depending on the software used.
468 When using syslog-ng, add the 'syslog-protocol' flag to local
469 input sources to enable parsing of RFC 5424 formatted messages:
472 unix-dgram("/var/run/log" flags(syslog-protocol));
475 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
476 of the 'imuxsock' module to let messages be processed by the
477 regular RFC 3164/5424 parsing pipeline:
479 module(load="imuxsock" SysSock.UseSpecialParser="off")
481 Do note that these changes only affect communication between local
482 applications and syslogd(8). The format that syslogd(8) uses to
483 store messages on disk or forward messages to other systems
484 remains unchanged. syslogd(8) still uses RFC 3164 for these
485 purposes. Options to customize this behaviour will be added in the
486 future. Utilities that process log files stored in /var/log are
487 thus expected to continue to function as before.
489 __FreeBSD_version has been incremented to 1200061 to denote this
493 Support for token ring networks has been removed. If you
494 have "device token" in your kernel config you should remove
495 it. No device drivers supported token ring.
498 makefs was modified to be able to tag ISO9660 El Torito boot catalog
499 entries as EFI instead of overloading the i386 tag as done previously.
500 The amd64 mkisoimages.sh script used to build amd64 ISO images for
501 release was updated to use this. This may mean that makefs must be
502 updated before "make cdrom" can be run in the release directory. This
503 should be as simple as:
505 $ cd $SRCDIR/usr.sbin/makefs
506 $ make depend all install
509 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
510 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
511 Co-existance for the transition period will come shortly. Booting is a
512 complex environment and test coverage for Lua-enabled loaders has been
513 thin, so it would be prudent to assume it might not work and make
514 provisions for backup boot methods.
517 devmatch functionality has been turned on in devd. It will automatically
518 load drivers for unattached devices. This may cause unexpected drivers
519 to be loaded. Please report any problems to current@ and
523 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
524 6.0.0. Please see the 20141231 entry below for information about
525 prerequisites and upgrading, if you are not already using clang 3.5.0
529 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
530 This means it is used to link the kernel and userland libraries and
531 executables, but is not yet installed as /usr/bin/ld by default.
533 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
534 WITHOUT_LLD_BOOTSTRAP=yes
537 On i386, pmtimer has been removed. Its functionality has been folded
538 into apm. It was a no-op on ACPI in current for a while now (but was
539 still needed on i386 in FreeBSD 11 and earlier). Users may need to
540 remove it from kernel config files.
543 The use of RSS hash from the network card aka flowid has been
544 disabled by default for lagg(4) as it's currently incompatible with
545 the lacp and loadbalance protocols.
547 This can be re-enabled by setting the following in loader.conf:
548 net.link.lagg.default_use_flowid="1"
551 The SW_WATCHDOG option is no longer necessary to enable the
552 hardclock-based software watchdog if no hardware watchdog is
553 configured. As before, SW_WATCHDOG will cause the software
554 watchdog to be enabled even if a hardware watchdog is configured.
557 r326887 fixes the issue described in the 20171214 UPDATING entry.
558 r326888 flips the switch back to building GELI support always.
561 r362593 broke ZFS + GELI support for reasons unknown. However,
562 it also broke ZFS support generally, so GELI has been turned off
563 by default as the lesser evil in r326857. If you boot off ZFS and/or
564 GELI, it might not be a good time to update.
567 PowerPC users must update loader(8) by rebuilding world before
568 installing a new kernel, as the protocol connecting them has
569 changed. Without the update, loader metadata will not be passed
570 successfully to the kernel and users will have to enter their
571 root partition at the kernel mountroot prompt to continue booting.
572 Newer versions of loader can boot old kernels without issue.
575 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
576 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
577 to WITH/OUT_LOADER_GELI.
580 The naive and non-compliant support of posix_fallocate(2) in ZFS
581 has been removed as of r325320. The system call now returns EINVAL
582 when used on a ZFS file. Although the new behavior complies with the
583 standard, some consumers are not prepared to cope with it.
584 One known victim is lld prior to r325420.
587 Building in a FreeBSD src checkout will automatically create object
588 directories now rather than store files in the current directory if
589 'make obj' was not ran. Calling 'make obj' is no longer necessary.
590 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
591 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
595 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
596 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
597 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
598 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
599 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
600 The UNIFIED_OBJDIR option is a transitional feature that will be
601 removed for 12.0 release; please migrate to the new format for any
602 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
603 than hardcoding paths.
606 The native-xtools target no longer installs the files by default to the
607 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
608 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
611 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
612 options are changing from controlling the build if defined / undefined
613 to controlling the build with explicit 'yes' or 'no' values. They will
614 shift to WITH/WITHOUT options to match other options in the system.
617 libstand has turned into a private library for sys/boot use only.
618 It is no longer supported as a public interface outside of sys/boot.
621 The arm port has split armv6 into armv6 and armv7. armv7 is now
622 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
623 and are running a kernel from before r324363, you will need to add
624 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
627 When building multiple kernels using KERNCONF, non-existent KERNCONF
628 files will produce an error and buildkernel will fail. Previously
629 missing KERNCONF files silently failed giving no indication as to
630 why, only to subsequently discover during installkernel that the
631 desired kernel was never built in the first place.
634 The default serial number format for CTL LUNs has changed. This will
635 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
636 or iSCSI clients care about their LUNs' serial numbers. Users who
637 require serial number stability should hardcode serial numbers in
641 For 32-bit arm compiled for hard-float support, soft-floating point
642 binaries now always get their shared libraries from
643 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
644 /usr/libsoft also existed). Only users with a hard-float ld.so, but
645 soft-float everything else should be affected.
648 The geli password typed at boot is now hidden. To restore the previous
649 behavior, see geli(8) for configuration options.
652 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
653 sysctl values. Minor nit, but requires a rebuild of both world/kernel
657 "make check" behavior (made in ^/head@r295380) has been changed to
658 execute from a limited sandbox, as opposed to executing from
662 - The "beforecheck" and "aftercheck" targets are now specified.
663 - ${CHECKDIR} (added in commit noted above) has been removed.
664 - Legacy behavior can be enabled by setting
665 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
667 If the limited sandbox mode is enabled, "make check" will execute
668 "make distribution", then install, execute the tests, and clean up the
669 sandbox if successful.
671 The "make distribution" and "make install" targets are typically run as
672 root to set appropriate permissions and ownership at installation time.
673 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
674 environment if executing "make check" with limited sandbox mode using
675 an unprivileged user.
678 Since the switch to GPT disk labels, fsck for UFS/FFS has been
679 unable to automatically find alternate superblocks. As of r322297,
680 the information needed to find alternate superblocks has been
681 moved to the end of the area reserved for the boot block.
682 Filesystems created with a newfs of this vintage or later
683 will create the recovery information. If you have a filesystem
684 created prior to this change and wish to have a recovery block
685 created for your filesystem, you can do so by running fsck in
686 foreground mode (i.e., do not use the -p or -y options). As it
687 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
688 to which you should answer yes.
691 As of r321665, an NFSv4 server configuration that services
692 Kerberos mounts or clients that do not support the uid/gid in
693 owner/owner_group string capability, must explicitly enable
694 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
695 machine's /etc/rc.conf file.
698 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
699 Please see the 20141231 entry below for information about prerequisites
700 and upgrading, if you are not already using clang 3.5.0 or higher.
703 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
704 r-commands (rlogin, rsh, etc.) to be built with the base system.
707 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
708 a very major ABI incompatible change, so users of FreeBSD/powerpc must
709 be careful when performing source upgrades. It is best to run
710 'make installworld' from an alternate root system, either a live
711 CD/memory stick, or a temporary root partition. Additionally, all ports
712 must be recompiled. powerpc64 is largely unaffected, except in the case
713 of 32-bit compatibility. All 32-bit binaries will be affected.
716 Forward compatibility for the "ino64" project have been committed. This
717 will allow most new binaries to run on older kernels in a limited
718 fashion. This prevents many of the common foot-shooting actions in the
719 upgrade as well as the limited ability to roll back the kernel across
720 the ino64 upgrade. Complicated use cases may not work properly, though
721 enough simpler ones work to allow recovery in most situations.
724 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
725 if you require the GPL compiler.
728 The internal ABI used for communication between the NFS kernel modules
729 was changed by r320085, so __FreeBSD_version was bumped to
730 ensure all the NFS related modules are updated together.
733 The ABI of struct event was changed by extending the data
734 member to 64bit and adding ext fields. For upgrade, same
735 precautions as for the entry 20170523 "ino64" must be
739 The GNU roff toolchain has been removed from base. To render manpages
740 which are not supported by mandoc(1), man(1) can fallback on GNU roff
741 from ports (and recommends to install it).
742 To render roff(7) documents, consider using GNU roff from ports or the
743 heirloom doctools roff toolchain from ports via pkg install groff or
744 via pkg install heirloom-doctools.
747 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
748 smaller runtime footprint builds. This is useful for embedded systems
749 which only require one chipset support.
751 If you load it as a module, make sure this is in /boot/loader.conf:
755 This will load the HAL, all chip/RF backends and if_ath_pci.
756 If you have if_ath_pci in /boot/loader.conf, ensure it is after
757 if_ath or it will not load any HAL chipset support.
759 If you want to selectively load things (eg on ye cheape ARM/MIPS
760 platforms where RAM is at a premium) you should:
763 * load the chip modules in question
764 * load ath_rate, ath_dfs
766 * load if_ath_pci and/or if_ath_ahb depending upon your particular
767 bus bind type - this is where probe/attach is done.
769 For further comments/feedback, poke adrian@ .
772 The "ino64" 64-bit inode project has been committed, which extends
773 a number of types to 64 bits. Upgrading in place requires care and
774 adherence to the documented upgrade procedure.
776 If using a custom kernel configuration ensure that the
777 COMPAT_FREEBSD11 option is included (as during the upgrade the
778 system will be running the ino64 kernel with the existing world).
780 For the safest in-place upgrade begin by removing previous build
781 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
782 procedure documented below under the heading "To rebuild everything and
783 install it on the current system." Specifically, a reboot is required
784 after installing the new kernel before installing world. While an
785 installworld normally works by accident from multiuser after rebooting
786 the proper kernel, there are many cases where this will fail across this
787 upgrade and installworld from single user is required.
790 The NATM framework including the en(4), fatm(4), hatm(4), and
791 patm(4) devices has been removed. Consumers should plan a
792 migration before the end-of-life date for FreeBSD 11.
795 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
796 diff has not been implemented, if those are needed a newer version of
797 GNU diff is available via the diffutils package under the gdiff name.
800 As of r316810 for ipfilter, keep frags is no longer assumed when
801 keep state is specified in a rule. r316810 aligns ipfilter with
802 documentation in man pages separating keep frags from keep state.
803 This allows keep state to be specified without forcing keep frags
804 and allows keep frags to be specified independently of keep state.
805 To maintain previous behaviour, also specify keep frags with
806 keep state (as documented in ipf.conf.5).
809 arm64 builds now use the base system LLD 4.0.0 linker by default,
810 instead of requiring that the aarch64-binutils port or package be
811 installed. To continue using aarch64-binutils, set
812 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
815 The UDP optimization in entry 20160818 that added the sysctl
816 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
817 packets will no longer be treated as L3 broadcast packets.
820 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
821 use any explicitly assigned loopback address available in the jail
822 instead of using the first assigned address of the jail.
825 The ctl.ko module no longer implements the iSCSI target frontend:
826 cfiscsi.ko does instead.
828 If building cfiscsi.ko as a kernel module, the module can be loaded
829 via one of the following methods:
830 - `cfiscsi_load="YES"` in loader.conf(5).
831 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
832 - ctladm(8)/ctld(8), when compiled with iSCSI support
833 (`WITH_ISCSI=yes` in src.conf(5))
835 Please see cfiscsi(4) for more details.
838 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
839 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
840 same source (previously, the dependency of mmcsd.ko on mmc.ko was
841 missing, but mmcsd.ko now will refuse to load if it is incompatible
845 The syntax of ipfw(8) named states was changed to avoid ambiguity.
846 If you have used named states in the firewall rules, you need to modify
847 them after installworld and before rebooting. Now named states must
848 be prefixed with colon.
851 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
852 removed as the userland we provide cannot use them. The KMS version
853 (sys/dev/drm2) supports the same hardware.
856 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
857 Please see the 20141231 entry below for information about prerequisites
858 and upgrading, if you are not already using clang 3.5.0 or higher.
861 The code that provides support for ZFS .zfs/ directory functionality
862 has been reimplemented. It's not possible now to create a snapshot
863 by mkdir under .zfs/snapshot/. That should be the only user visible
867 EISA bus support has been removed. The WITH_EISA option is no longer
871 MCA bus support has been removed.
874 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
875 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
878 The EM_MULTIQUEUE kernel configuration option is deprecated now that
879 the em(4) driver conforms to iflib specifications.
882 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
883 IFLIB. If you have a custom kernel configuration that excludes em(4)
884 but you use igb(4), you need to re-add em(4) to your custom
888 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
889 Please see the 20141231 entry below for information about prerequisites
890 and upgrading, if you are not already using clang 3.5.0 or higher.
893 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
894 Please see the 20141231 entry below for information about prerequisites
895 and upgrading, if you are not already using clang 3.5.0 or higher.
898 The layout of the pmap structure has changed for powerpc to put the pmap
899 statistics at the front for all CPU variations. libkvm(3) and all tools
900 that link against it need to be recompiled.
903 isl(4) and cyapa(4) drivers now require a new driver,
904 chromebook_platform(4), to work properly on Chromebook-class hardware.
905 On other types of hardware the drivers may need to be configured using
906 device hints. Please see the corresponding manual pages for details.
909 The urtwn(4) driver was merged into rtwn(4) and now consists of
910 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
912 Also, firmware for RTL8188CE was renamed due to possible name
913 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
916 GNU rcs has been removed from base. It is available as packages:
917 - rcs: Latest GPLv3 GNU rcs version.
918 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
922 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
923 modules now requires that the kernel configuration contain the
924 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
927 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
928 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
931 Relocatable object files with the extension of .So have been renamed
932 to use an extension of .pico instead. The purpose of this change is
933 to avoid a name clash with shared libraries on case-insensitive file
934 systems. On those file systems, foo.So is the same file as foo.so.
937 GNU rcs has been turned off by default. It can (temporarily) be built
938 again by adding WITH_RCS knob in src.conf.
939 Otherwise, GNU rcs is available from packages:
940 - rcs: Latest GPLv3 GNU rcs version.
941 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
944 The backup_uses_rcs functionality has been removed from rc.subr.
947 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
948 two separate components, QUEUE_MACRO_DEBUG_TRACE and
949 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
950 QUEUE_MACRO_DEBUG behavior.
953 r304787 changed some ioctl interfaces between the iSCSI userspace
954 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
955 rebuilt to work with new kernels. __FreeBSD_version has been bumped
959 The UDP receive code has been updated to only treat incoming UDP
960 packets that were addressed to an L2 broadcast address as L3
961 broadcast packets. It is not expected that this will affect any
962 standards-conforming UDP application. The new behaviour can be
963 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
967 Remove the openbsd_poll system call.
968 __FreeBSD_version has been bumped because of this.
971 The stable/11 branch has been created from head@r302406.
974 The libc stub for the pipe(2) system call has been replaced with
975 a wrapper that calls the pipe2(2) system call and the pipe(2)
976 system call is now only implemented by the kernels that include
977 "options COMPAT_FREEBSD10" in their config file (this is the
978 default). Users should ensure that this option is enabled in
979 their kernel or upgrade userspace to r302092 before upgrading their
983 CAM will now strip leading spaces from SCSI disks' serial numbers.
984 This will affect users who create UFS filesystems on SCSI disks using
985 those disk's diskid device nodes. For example, if /etc/fstab
986 previously contained a line like
987 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
988 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
989 transforms like gmirror may also be affected. ZFS users should
993 The bitstring(3) API has been updated with new functionality and
994 improved performance. But it is binary-incompatible with the old API.
995 Objects built with the new headers may not be linked against objects
996 built with the old headers.
999 The brk and sbrk functions have been removed from libc on arm64.
1000 Binutils from ports has been updated to not link to these
1001 functions and should be updated to the latest version before
1002 installing a new libc.
1005 The armv6 port now defaults to hard float ABI. Limited support
1006 for running both hardfloat and soft float on the same system
1007 is available using the libraries installed with -DWITH_LIBSOFT.
1008 This has only been tested as an upgrade path for installworld
1009 and packages may fail or need manual intervention to run. New
1010 packages will be needed.
1012 To update an existing self-hosted armv6hf system, you must add
1013 TARGET_ARCH=armv6 on the make command line for both the build
1014 and the install steps.
1017 Kernel modules compiled outside of a kernel build now default to
1018 installing to /boot/modules instead of /boot/kernel. Many kernel
1019 modules built this way (such as those in ports) already overrode
1020 KMODDIR explicitly to install into /boot/modules. However,
1021 manually building and installing a module from /sys/modules will
1022 now install to /boot/modules instead of /boot/kernel.
1025 The CAM I/O scheduler has been committed to the kernel. There should be
1026 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1027 list of known rogues that claim support for this but actually corrupt
1028 data is believed to be complete, be on the lookout for data
1029 corruption. The known rogue list is believed to be complete:
1031 o Crucial MX100, M550 drives with MU01 firmware.
1032 o Micron M510 and M550 drives with MU01 firmware.
1033 o Micron M500 prior to MU07 firmware
1034 o Samsung 830, 840, and 850 all firmwares
1035 o FCCT M500 all firmwares
1037 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1038 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1039 updated firmware. Black listed drives will work correctly because these
1040 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1041 this list is the same as found in Linux, it's believed there are no
1042 other rogues in the market place. All other models from the above
1045 To be safe, if you are at all concerned, you can quirk each of your
1046 drives to prevent NCQ from being sent by setting:
1047 kern.cam.ada.X.quirks="0x2"
1048 in loader.conf. If the drive requires the 4k sector quirk, set the
1049 quirks entry to 0x3.
1052 The FAST_DEPEND build option has been removed and its functionality is
1053 now the one true way. The old mkdep(1) style of 'make depend' has
1054 been removed. See 20160311 for further details.
1057 Resource range types have grown from unsigned long to uintmax_t. All
1058 drivers, and anything using libdevinfo, need to be recompiled.
1061 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1062 builds. It no longer runs mkdep(1) during 'make depend', and the
1063 'make depend' stage can safely be skipped now as it is auto ran
1064 when building 'make all' and will generate all SRCS and DPSRCS before
1065 building anything else. Dependencies are gathered at compile time with
1066 -MF flags kept in separate .depend files per object file. Users should
1067 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1068 stale .depend files.
1071 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1072 kernel modules. Therefore, if you load any kernel modules at boot time,
1073 please install the boot loaders after you install the kernel, but before
1077 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1078 make installkernel KERNCONF=YOUR_KERNEL_HERE
1079 make -C sys/boot install
1080 <reboot in single user>
1082 Then follow the usual steps, described in the General Notes section,
1086 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1087 see the 20141231 entry below for information about prerequisites and
1088 upgrading, if you are not already using clang 3.5.0 or higher.
1091 The AIO subsystem is now a standard part of the kernel. The
1092 VFS_AIO kernel option and aio.ko kernel module have been removed.
1093 Due to stability concerns, asynchronous I/O requests are only
1094 permitted on sockets and raw disks by default. To enable
1095 asynchronous I/O requests on all file types, set the
1096 vfs.aio.enable_unsafe sysctl to a non-zero value.
1099 The ELF object manipulation tool objcopy is now provided by the
1100 ELF Tool Chain project rather than by GNU binutils. It should be a
1101 drop-in replacement, with the addition of arm64 support. The
1102 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1103 to obtain the GNU version if necessary.
1106 Building ZFS pools on top of zvols is prohibited by default. That
1107 feature has never worked safely; it's always been prone to deadlocks.
1108 Using a zvol as the backing store for a VM guest's virtual disk will
1109 still work, even if the guest is using ZFS. Legacy behavior can be
1110 restored by setting vfs.zfs.vol.recursive=1.
1113 The NONE and HPN patches has been removed from OpenSSH. They are
1114 still available in the security/openssh-portable port.
1117 With the addition of ypldap(8), a new _ypldap user is now required
1118 during installworld. "mergemaster -p" can be used to add the user
1119 prior to installworld, as documented in the handbook.
1122 The tftp loader (pxeboot) now uses the option root-path directive. As a
1123 consequence it no longer looks for a pxeboot.4th file on the tftp
1124 server. Instead it uses the regular /boot infrastructure as with the
1128 The code to start recording plug and play data into the modules has
1129 been committed. While the old tools will properly build a new kernel,
1130 a number of warnings about "unknown metadata record 4" will be produced
1131 for an older kldxref. To avoid such warnings, make sure to rebuild
1132 the kernel toolchain (or world). Make sure that you have r292078 or
1133 later when trying to build 292077 or later before rebuilding.
1136 Debug data files are now built by default with 'make buildworld' and
1137 installed with 'make installworld'. This facilitates debugging but
1138 requires more disk space both during the build and for the installed
1139 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1143 r291527 changed the internal interface between the nfsd.ko and
1144 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1145 __FreeBSD_version has been bumped because of this.
1148 Add support for unicode collation strings leads to a change of
1149 order of files listed by ls(1) for example. To get back to the old
1150 behaviour, set LC_COLLATE environment variable to "C".
1152 Databases administrators will need to reindex their databases given
1153 collation results will be different.
1155 Due to a bug in install(1) it is recommended to remove the ancient
1156 locales before running make installworld.
1158 rm -rf /usr/share/locale/*
1161 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1162 libcrypto.so.7 or libssl.so.7 must be recompiled.
1165 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1166 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1167 should be replaced with isp_2400 and isp_2500 modules respectively.
1170 The build previously allowed using 'make -n' to not recurse into
1171 sub-directories while showing what commands would be executed, and
1172 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1173 and 'make -N' will not.
1176 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1177 and etcupdate will now use this file. A custom sendmail.cf is now
1178 updated via this mechanism rather than via installworld. If you had
1179 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1180 want to remove the exclusion or change it to "always install".
1181 /etc/mail/sendmail.cf is now managed the same way regardless of
1182 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1183 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1186 Compatibility shims for legacy ATA device names have been removed.
1187 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1188 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1189 environment variables, /dev/ad* and /dev/ar* symbolic links.
1192 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1193 Please see the 20141231 entry below for information about prerequisites
1194 and upgrading, if you are not already using clang 3.5.0 or higher.
1197 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1198 and renamed from .symbols to .debug. This reduces the size requirements
1199 on the boot partition or file system and provides consistency with
1200 userland debug files.
1202 When using the supported kernel installation method the
1203 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1204 as is done with /boot/kernel.
1206 Developers wishing to maintain the historical behavior of installing
1207 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1210 The wireless drivers had undergone changes that remove the 'parent
1211 interface' from the ifconfig -l output. The rc.d network scripts
1212 used to check presence of a parent interface in the list, so old
1213 scripts would fail to start wireless networking. Thus, etcupdate(3)
1214 or mergemaster(8) run is required after kernel update, to update your
1215 rc.d scripts in /etc.
1218 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1219 These configurations are now automatically interpreted as
1220 'scrub fragment reassemble'.
1223 Kernel-loadable modules for the random(4) device are back. To use
1224 them, the kernel must have
1227 options RANDOM_LOADABLE
1229 kldload(8) can then be used to load random_fortuna.ko
1230 or random_yarrow.ko. Please note that due to the indirect
1231 function calls that the loadable modules need to provide,
1232 the build-in variants will be slightly more efficient.
1234 The random(4) kernel option RANDOM_DUMMY has been retired due to
1235 unpopularity. It was not all that useful anyway.
1238 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1239 Control over building the ELF Tool Chain tools is now provided by
1240 the WITHOUT_TOOLCHAIN knob.
1243 The polarity of Pulse Per Second (PPS) capture events with the
1244 uart(4) driver has been corrected. Prior to this change the PPS
1245 "assert" event corresponded to the trailing edge of a positive PPS
1246 pulse and the "clear" event was the leading edge of the next pulse.
1248 As the width of a PPS pulse in a typical GPS receiver is on the
1249 order of 1 millisecond, most users will not notice any significant
1250 difference with this change.
1252 Anyone who has compensated for the historical polarity reversal by
1253 configuring a negative offset equal to the pulse width will need to
1254 remove that workaround.
1257 The default group assigned to /dev/dri entries has been changed
1258 from 'wheel' to 'video' with the id of '44'. If you want to have
1259 access to the dri devices please add yourself to the video group
1262 # pw groupmod video -m $USER
1265 The menu.rc and loader.rc files will now be replaced during
1266 upgrades. Please migrate local changes to menu.rc.local and
1267 loader.rc.local instead.
1270 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1271 strings and strip have been removed. The src.conf(5) knob
1272 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1275 As ZFS requires more kernel stack pages than is the default on some
1276 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1277 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1279 Please consider using 'options KSTACK_PAGES=X' where X is greater
1280 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1283 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1284 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1285 default, i.e., they will not contain "::". For example, instead
1286 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1287 to have a more specific match, such as different map entries for
1288 IPv6:0:0 vs IPv6:0. This change requires that configuration
1289 data (including maps, files, classes, custom ruleset, etc.) must
1290 use the same format, so make certain such configuration data is
1291 upgrading. As a very simple check search for patterns like
1292 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1293 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1294 the cf option UseCompressedIPv6Addresses.
1297 The default kernel entropy-processing algorithm is now
1298 Fortuna, replacing Yarrow.
1300 Assuming you have 'device random' in your kernel config
1301 file, the configurations allow a kernel option to override
1302 this default. You may choose *ONE* of:
1304 options RANDOM_YARROW # Legacy /dev/random algorithm.
1305 options RANDOM_DUMMY # Blocking-only driver.
1307 If you have neither, you get Fortuna. For most people,
1308 read no further, Fortuna will give a /dev/random that works
1309 like it always used to, and the difference will be irrelevant.
1311 If you remove 'device random', you get *NO* kernel-processed
1312 entropy at all. This may be acceptable to folks building
1313 embedded systems, but has complications. Carry on reading,
1314 and it is assumed you know what you need.
1316 *PLEASE* read random(4) and random(9) if you are in the
1317 habit of tweaking kernel configs, and/or if you are a member
1318 of the embedded community, wanting specific and not-usual
1319 behaviour from your security subsystems.
1321 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1322 random', you will NOT have a functioning /dev/random, and
1323 many cryptographic features will not work, including SSH.
1324 You may also find strange behaviour from the random(3) set
1325 of library functions, in particular sranddev(3), srandomdev(3)
1326 and arc4random(3). The reason for this is that the KERN_ARND
1327 sysctl only returns entropy if it thinks it has some to
1328 share, and with RANDOM_DUMMY or no 'device random' this
1332 An additional fix for the issue described in the 20150614 sendmail
1333 entry below has been committed in revision 284717.
1336 FreeBSD's old make (fmake) has been removed from the system. It is
1337 available as the devel/fmake port or via pkg install fmake.
1340 The fix for the issue described in the 20150614 sendmail entry
1341 below has been committed in revision 284436. The work
1342 around described in that entry is no longer needed unless the
1343 default setting is overridden by a confDH_PARAMETERS configuration
1344 setting of '5' or pointing to a 512 bit DH parameter file.
1347 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1348 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1349 and devel/kyua to version 0.20+ and adjust any calling code to work
1350 with Kyuafile and kyua.
1353 The import of openssl to address the FreeBSD-SA-15:10.openssl
1354 security advisory includes a change which rejects handshakes
1355 with DH parameters below 768 bits. sendmail releases prior
1356 to 8.15.2 (not yet released), defaulted to a 512 bit
1357 DH parameter setting for client connections. To work around
1358 this interoperability, sendmail can be configured to use a
1359 2048 bit DH parameter by:
1361 1. Edit /etc/mail/`hostname`.mc
1362 2. If a setting for confDH_PARAMETERS does not exist or
1363 exists and is set to a string beginning with '5',
1364 replace it with '2'.
1365 3. If a setting for confDH_PARAMETERS exists and is set to
1366 a file path, create a new file with:
1367 openssl dhparam -out /path/to/file 2048
1368 4. Rebuild the .cf file:
1369 cd /etc/mail/; make; make install
1370 5. Restart sendmail:
1371 cd /etc/mail/; make restart
1373 A sendmail patch is coming, at which time this file will be
1377 Generation of legacy formatted entries have been disabled by default
1378 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1379 entries were converted to use the new format by default when the new,
1380 machine independent format have been added and supported since FreeBSD
1383 Please see the pwd_mkdb(8) manual page for further details.
1386 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1387 20141231 entry below for information about prerequisites and upgrading,
1388 if you are not already using 3.5.0 or higher.
1391 TI platform code switched to using vendor DTS files and this update
1392 may break existing systems running on Beaglebone, Beaglebone Black,
1395 - dtb files should be regenerated/reinstalled. Filenames are the
1396 same but content is different now
1397 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1398 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1399 addressing scheme is now pin 25 on /dev/gpioc3.
1400 - Pandaboard: /etc/ttys should be updated, serial console device is
1401 now /dev/ttyu2, not /dev/ttyu0
1404 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1405 If you need the GNU extension from groff soelim(1), install groff
1406 from package: pkg install groff, or via ports: textproc/groff.
1409 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1410 defined in symlink(7); previously symlinks were silently ignored.
1413 The const qualifier has been removed from iconv(3) to comply with
1414 POSIX. The ports tree is aware of this from r384038 onwards.
1417 Libraries specified by LIBADD in Makefiles must have a corresponding
1418 DPADD_<lib> variable to ensure correct dependencies. This is now
1419 enforced in src.libnames.mk.
1422 From legacy ata(4) driver was removed support for SATA controllers
1423 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1424 Kernel modules ataahci and ataadaptec were removed completely,
1425 replaced by ahci and mvs modules respectively.
1428 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1429 the 20141231 entry below for information about prerequisites and
1430 upgrading, if you are not already using 3.5.0 or higher.
1433 The 32-bit PowerPC kernel has been changed to a position-independent
1434 executable. This can only be booted with a version of loader(8)
1435 newer than January 31, 2015, so make sure to update both world and
1436 kernel before rebooting.
1439 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1440 but before r278950, the RNG was not seeded properly. Immediately
1441 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1442 ssh keys or openssl keys) that were generated w/ a kernel from that
1443 range. This does not affect programs that directly used /dev/random
1444 or /dev/urandom. All userland uses of arc4random(3) are affected.
1447 The autofs(4) ABI was changed in order to restore binary compatibility
1448 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1449 with the new kernel.
1452 The powerpc64 kernel has been changed to a position-independent
1453 executable. This can only be booted with a new version of loader(8),
1454 so make sure to update both world and kernel before rebooting.
1457 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1458 only release, no new features have been added. Please see the 20141231
1459 entry below for information about prerequisites and upgrading, if you
1460 are not already using 3.5.0.
1463 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1464 taken from the ELF Tool Chain project rather than GNU binutils. They
1465 should be drop-in replacements, with the addition of arm64 support.
1466 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1467 binutils tools, if necessary. See 20150805 for updated information.
1470 The default Unbound configuration now enables remote control
1471 using a local socket. Users who have already enabled the
1472 local_unbound service should regenerate their configuration
1473 by running "service local_unbound setup" as root.
1476 The GNU texinfo and GNU info pages have been removed.
1477 To be able to view GNU info pages please install texinfo from ports.
1480 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1482 As of this release, a prerequisite for building clang, llvm and lldb is
1483 a C++11 capable compiler and C++11 standard library. This means that to
1484 be able to successfully build the cross-tools stage of buildworld, with
1485 clang as the bootstrap compiler, your system compiler or cross compiler
1486 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1487 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1490 On any standard FreeBSD 10.x or 11.x installation, where clang and
1491 libc++ are on by default (that is, on x86 or arm), this should work out
1494 On 9.x installations where clang is enabled by default, e.g. on x86 and
1495 powerpc, libc++ will not be enabled by default, so libc++ should be
1496 built (with clang) and installed first. If both clang and libc++ are
1497 missing, build clang first, then use it to build libc++.
1499 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1500 the instructions for 9.x above.
1502 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1503 default, and do not build clang.
1505 Many embedded systems are resource constrained, and will not be able to
1506 build clang in a reasonable time, or in some cases at all. In those
1507 cases, cross building bootable systems on amd64 is a workaround.
1509 This new version of clang introduces a number of new warnings, of which
1510 the following are most likely to appear:
1514 This warns in two cases, for both C and C++:
1515 * When the code is trying to take the absolute value of an unsigned
1516 quantity, which is effectively a no-op, and almost never what was
1517 intended. The code should be fixed, if at all possible. If you are
1518 sure that the unsigned quantity can be safely cast to signed, without
1519 loss of information or undefined behavior, you can add an explicit
1520 cast, or disable the warning.
1522 * When the code is trying to take an absolute value, but the called
1523 abs() variant is for the wrong type, which can lead to truncation.
1524 If you want to disable the warning instead of fixing the code, please
1525 make sure that truncation will not occur, or it might lead to unwanted
1528 -Wtautological-undefined-compare and
1529 -Wundefined-bool-conversion
1531 These warn when C++ code is trying to compare 'this' against NULL, while
1532 'this' should never be NULL in well-defined C++ code. However, there is
1533 some legacy (pre C++11) code out there, which actively abuses this
1534 feature, which was less strictly defined in previous C++ versions.
1536 Squid and openjdk do this, for example. The warning can be turned off
1537 for C++98 and earlier, but compiling the code in C++11 mode might result
1538 in unexpected behavior; for example, the parts of the program that are
1539 unreachable could be optimized away.
1542 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1543 kernel sources have been removed. The .h files remain, since some
1544 utilities include them. This will need to be fixed later.
1545 If "mount -t oldnfs ..." is attempted, it will fail.
1546 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1547 the utilities will report errors.
1550 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1551 directories to top level SUBDIR variable when their parent
1552 directory is included in LOCAL_DIRS. Users with build systems with
1553 such hierarchies and without SUBDIR entries in the parent
1554 directory Makefiles should add them or add the directories to
1558 faith(4) and faithd(8) have been removed from the base system. Faith
1559 has been obsolete for a very long time.
1562 vt(4), the new console driver, is enabled by default. It brings
1563 support for Unicode and double-width characters, as well as
1564 support for UEFI and integration with the KMS kernel video
1567 You may need to update your console settings in /etc/rc.conf,
1568 most probably the keymap. During boot, /etc/rc.d/syscons will
1569 indicate what you need to do.
1571 vt(4) still has issues and lacks some features compared to
1572 syscons(4). See the wiki for up-to-date information:
1573 https://wiki.freebsd.org/Newcons
1575 If you want to keep using syscons(4), you can do so by adding
1576 the following line to /boot/loader.conf:
1580 pjdfstest has been integrated into kyua as an opt-in test suite.
1581 Please see share/doc/pjdfstest/README for more details on how to
1585 gperf has been removed from the base system for architectures
1586 that use clang. Ports that require gperf will obtain it from the
1590 pjdfstest has been moved from tools/regression/pjdfstest to
1594 At svn r271982, The default linux compat kernel ABI has been adjusted
1595 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1596 update. If you wish to continue using the linux-f10 compat ports,
1597 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1598 encouraged to update their linux-compat packages to linux-c6 during
1599 their next update cycle.
1602 The ofwfb driver, used to provide a graphics console on PowerPC when
1603 using vt(4), no longer allows mmap() of all physical memory. This
1604 will prevent Xorg on PowerPC with some ATI graphics cards from
1605 initializing properly unless x11-servers/xorg-server is updated to
1609 The xdev targets have been converted to using TARGET and
1610 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1613 The default unbound configuration has been modified to address
1614 issues with reverse lookups on networks that use private
1615 address ranges. If you use the local_unbound service, run
1616 "service local_unbound setup" as root to regenerate your
1617 configuration, then "service local_unbound reload" to load the
1621 The GNU texinfo and GNU info pages are not built and installed
1622 anymore, WITH_INFO knob has been added to allow to built and install
1624 UPDATE: see 20150102 entry on texinfo's removal
1627 The GNU readline library is now an INTERNALLIB - that is, it is
1628 statically linked into consumers (GDB and variants) in the base
1629 system, and the shared library is no longer installed. The
1630 devel/readline port is available for third party software that
1634 The Itanium architecture (ia64) has been removed from the list of
1635 known architectures. This is the first step in the removal of the
1639 Commit r268115 has added NFSv4.1 server support, merged from
1640 projects/nfsv4.1-server. Since this includes changes to the
1641 internal interfaces between the NFS related modules, a full
1642 build of the kernel and modules will be necessary.
1643 __FreeBSD_version has been bumped.
1646 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1647 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1648 which differs from the behaviour controlled by this knob.)
1651 Maximal length of the serial number in CTL was increased from 16 to
1652 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1653 and ctld, need to be rebuilt to work with a new kernel.
1656 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1657 1 respectively to match the upstream numbers. They were out of
1658 sync because, when they were originally added to FreeBSD, the
1659 upstream versions were not respected. These libraries are private
1660 and not yet built by default, so renumbering them should be a
1661 non-issue. However, unclean source trees will yield broken test
1662 programs once the operator executes "make delete-old-libs" after a
1663 "make installworld".
1665 Additionally, the atf-sh binary was made private by moving it into
1666 /usr/libexec/. Already-built shell test programs will keep the
1667 path to the old binary so they will break after "make delete-old"
1670 If you are using WITH_TESTS=yes (not the default), wipe the object
1671 tree and rebuild from scratch to prevent spurious test failures.
1672 This is only needed once: the misnumbered libraries and misplaced
1673 binaries have been added to OptionalObsoleteFiles.inc so they will
1674 be removed during a clean upgrade.
1677 Clang and llvm have been upgraded to 3.4.1 release.
1680 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1681 be removed to avoid issues in the future (and has been added to
1685 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1686 past, it affected all builds that used the bsd.*.mk files. The old
1687 behavior was a bug, but people may have relied upon it. To get this
1688 behavior back, you can .include /etc/src.conf from /etc/make.conf
1689 (which is still global and isn't changed). This also changes the
1690 behavior of incremental builds inside the tree of individual
1691 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1692 Although this has survived make universe and some upgrade scenarios,
1693 other upgrade scenarios may have broken. At least one form of
1694 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1695 as well... In cases where MAKESYSPATH isn't working with this
1696 setting, you'll need to set it to the full path to your tree.
1698 One side effect of all this cleaning up is that bsd.compiler.mk
1699 is no longer implicitly included by bsd.own.mk. If you wish to
1700 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1704 The lindev device has been removed since /dev/full has been made a
1705 standard device. __FreeBSD_version has been bumped.
1708 The knob WITHOUT_VI was added to the base system, which controls
1709 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1710 in order to reorder files share/termcap and didn't build ex(1) as a
1711 build tool, so building/installing with WITH_VI is highly advised for
1712 build hosts for older releases.
1714 This issue has been fixed in stable/9 and stable/10 in r277022 and
1715 r276991, respectively.
1718 The YES_HESIOD knob has been removed. It has been obsolete for
1719 a decade. Please move to using WITH_HESIOD instead or your builds
1720 will silently lack HESIOD.
1723 The uart(4) driver has been changed with respect to its handling
1724 of the low-level console. Previously the uart(4) driver prevented
1725 any process from changing the baudrate or the CLOCAL and HUPCL
1726 control flags. By removing the restrictions, operators can make
1727 changes to the serial console port without having to reboot.
1728 However, when getty(8) is started on the serial device that is
1729 associated with the low-level console, a misconfigured terminal
1730 line in /etc/ttys will now have a real impact.
1731 Before upgrading the kernel, make sure that /etc/ttys has the
1732 serial console device configured as 3wire without baudrate to
1733 preserve the previous behaviour. E.g:
1734 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1737 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1738 to improve performance. To re-enable it, if needed, run rpcbind
1739 with command line option -W.
1742 Switched back to the GPL dtc compiler due to updates in the upstream
1743 dts files not being supported by the BSDL dtc compiler. You will need
1744 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1745 may result while building dtb files during a kernel build if you fail
1746 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1749 Clang and llvm have been upgraded to 3.4 release.
1752 The nve(4) driver has been removed. Please use the nfe(4) driver
1753 for NVIDIA nForce MCP Ethernet adapters instead.
1756 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1757 This could cause certain C++ applications using shared libraries built
1758 against the previous version of libc++ to crash. The incompatibility
1759 has now been fixed, but any C++ applications or shared libraries built
1760 between r261283 and r261801 should be recompiled.
1763 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1764 capability mode support. Please note that enabling the feature in
1765 kernel is still highly recommended.
1768 OpenSSH is now built with sandbox support, and will use sandbox as
1769 the default privilege separation method. This requires Capsicum
1770 capability mode support in kernel.
1773 The libelf and libdwarf libraries have been updated to newer
1774 versions from upstream. Shared library version numbers for
1775 these two libraries were bumped. Any ports or binaries
1776 requiring these two libraries should be recompiled.
1777 __FreeBSD_version is bumped to 1100006.
1780 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1781 instead of providing an explicit one, this would prevent such
1782 Makefile from providing its own Kyuafile in the future during
1783 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1784 intervention is needed to clean an objdir if you use NO_CLEAN:
1785 # find /usr/obj -name Kyuafile | xargs rm -f
1788 The behavior of gss_pseudo_random() for the krb5 mechanism
1789 has changed, for applications requesting a longer random string
1790 than produced by the underlying enctype's pseudo-random() function.
1791 In particular, the random string produced from a session key of
1792 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1793 be different at the 17th octet and later, after this change.
1794 The counter used in the PRF+ construction is now encoded as a
1795 big-endian integer in accordance with RFC 4402.
1796 __FreeBSD_version is bumped to 1100004.
1799 The WITHOUT_ATF build knob has been removed and its functionality
1800 has been subsumed into the more generic WITHOUT_TESTS. If you were
1801 using the former to disable the build of the ATF libraries, you
1802 should change your settings to use the latter.
1805 The default version of mtree is nmtree which is obtained from
1806 NetBSD. The output is generally the same, but may vary
1807 slightly. If you found you need identical output adding
1808 "-F freebsd9" to the command line should do the trick. For the
1809 time being, the old mtree is available as fmtree.
1812 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1813 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1814 1.1.4_8 and verify bsdyml not linked in, before running "make
1816 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1818 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1821 The stable/10 branch has been created in subversion from head
1828 Avoid using make -j when upgrading. While generally safe, there are
1829 sometimes problems using -j to upgrade. If your upgrade fails with
1830 -j, please try again without -j. From time to time in the past there
1831 have been problems using -j with buildworld and/or installworld. This
1832 is especially true when upgrading between "distant" versions (eg one
1833 that cross a major release boundary or several minor releases, or when
1834 several months have passed on the -current branch).
1836 Sometimes, obscure build problems are the result of environment
1837 poisoning. This can happen because the make utility reads its
1838 environment when searching for values for global variables. To run
1839 your build attempts in an "environmental clean room", prefix all make
1840 commands with 'env -i '. See the env(1) manual page for more details.
1842 When upgrading from one major version to another it is generally best to
1843 upgrade to the latest code in the currently installed branch first, then
1844 do an upgrade to the new branch. This is the best-tested upgrade path,
1845 and has the highest probability of being successful. Please try this
1846 approach if you encounter problems with a major version upgrade. Since
1847 the stable 4.x branch point, one has generally been able to upgrade from
1848 anywhere in the most recent stable branch to head / current (or even the
1849 last couple of stable branches). See the top of this file when there's
1852 When upgrading a live system, having a root shell around before
1853 installing anything can help undo problems. Not having a root shell
1854 around can lead to problems if pam has changed too much from your
1855 starting point to allow continued authentication after the upgrade.
1857 This file should be read as a log of events. When a later event changes
1858 information of a prior event, the prior event should not be deleted.
1859 Instead, a pointer to the entry with the new information should be
1860 placed in the old entry. Readers of this file should also sanity check
1861 older entries before relying on them blindly. Authors of new entries
1862 should write them with this in mind.
1866 When upgrading the boot ZFS pool to a new version, always follow
1869 1.) recompile and reinstall the ZFS boot loader and boot block
1870 (this is part of "make buildworld" and "make installworld")
1872 2.) update the ZFS boot block on your boot drive
1874 The following example updates the ZFS boot block on the first
1875 partition (freebsd-boot) of a GPT partitioned drive ada0:
1876 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1878 Non-boot pools do not need these updates.
1882 If you are updating from a prior version of FreeBSD (even one just
1883 a few days old), you should follow this procedure. It is the most
1884 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1886 make kernel-toolchain
1887 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1888 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1890 To test a kernel once
1891 ---------------------
1892 If you just want to boot a kernel once (because you are not sure
1893 if it works, or if you want to boot a known bad kernel to provide
1894 debugging information) run
1895 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1896 nextboot -k testkernel
1898 To rebuild everything and install it on the current system.
1899 -----------------------------------------------------------
1900 # Note: sometimes if you are running current you gotta do more than
1901 # is listed here if you are upgrading from a really old current.
1903 <make sure you have good level 0 dumps>
1905 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1906 make installkernel KERNCONF=YOUR_KERNEL_HERE
1908 <reboot in single user> [3]
1915 To cross-install current onto a separate partition
1916 --------------------------------------------------
1917 # In this approach we use a separate partition to hold
1918 # current's root, 'usr', and 'var' directories. A partition
1919 # holding "/", "/usr" and "/var" should be about 2GB in
1922 <make sure you have good level 0 dumps>
1925 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1926 <maybe newfs current's root partition>
1927 <mount current's root partition on directory ${CURRENT_ROOT}>
1928 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1929 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1930 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1931 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1932 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1933 <reboot into current>
1934 <do a "native" rebuild/install as described in the previous section>
1935 <maybe install compatibility libraries from ports/misc/compat*>
1939 To upgrade in-place from stable to current
1940 ----------------------------------------------
1941 <make sure you have good level 0 dumps>
1943 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1944 make installkernel KERNCONF=YOUR_KERNEL_HERE
1946 <reboot in single user> [3]
1953 Make sure that you've read the UPDATING file to understand the
1954 tweaks to various things you need. At this point in the life
1955 cycle of current, things change often and you are on your own
1956 to cope. The defaults can also change, so please read ALL of
1957 the UPDATING entries.
1959 Also, if you are tracking -current, you must be subscribed to
1960 freebsd-current@freebsd.org. Make sure that before you update
1961 your sources that you have read and understood all the recent
1962 messages there. If in doubt, please track -stable which has
1963 much fewer pitfalls.
1965 [1] If you have third party modules, such as vmware, you
1966 should disable them at this point so they don't crash your
1969 [3] From the bootblocks, boot -s, and then do
1973 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
1974 cd src # full path to source
1975 adjkerntz -i # if CMOS is wall time
1976 Also, when doing a major release upgrade, it is required that
1977 you boot into single user mode to do the installworld.
1979 [4] Note: This step is non-optional. Failure to do this step
1980 can result in a significant reduction in the functionality of the
1981 system. Attempting to do it by hand is not recommended and those
1982 that pursue this avenue should read this file carefully, as well
1983 as the archives of freebsd-current and freebsd-hackers mailing lists
1984 for potential gotchas. The -U option is also useful to consider.
1985 See mergemaster(8) for more information.
1987 [5] Usually this step is a no-op. However, from time to time
1988 you may need to do this if you get unknown user in the following
1989 step. It never hurts to do it all the time. You may need to
1990 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1991 install) after the buildworld before this step if you last updated
1992 from current before 20130425 or from -stable before 20130430.
1994 [6] This only deletes old files and directories. Old libraries
1995 can be deleted by "make delete-old-libs", but you have to make
1996 sure that no program is using those libraries anymore.
1998 [8] The new kernel must be able to run existing binaries used by an
1999 installworld. When upgrading across major versions, the new kernel's
2000 configuration must include the correct COMPAT_FREEBSD<n> option for
2001 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2002 to do so may leave you with a system that is hard to boot to recover. A
2003 GENERIC kernel will include suitable compatibility options to run
2004 binaries from older branches. Note that the ability to run binaries
2005 from unsupported branches is not guaranteed.
2007 Make sure that you merge any new devices from GENERIC since the
2008 last time you updated your kernel config file. Options also
2009 change over time, so you may need to adjust your custom kernels
2012 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2013 "?=" instead of the "=" assignment operator, so that buildworld can
2014 override the CPUTYPE if it needs to.
2016 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2017 not on the command line, or in /etc/make.conf. buildworld will
2018 warn if it is improperly defined.
2021 This file contains a list, in reverse chronological order, of major
2022 breakages in tracking -current. It is not guaranteed to be a complete
2023 list of such breakages, and only contains entries since September 23, 2011.
2024 If you need to see UPDATING entries from before that date, you will need
2025 to fetch an UPDATING file from an older FreeBSD release.
2027 Copyright information:
2029 Copyright 1998-2009 M. Warner Losh.
2031 Redistribution, publication, translation and use, with or without
2032 modification, in full or in part, in any form or format of this
2033 document are permitted without further permission from the author.
2035 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2036 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2037 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2038 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2039 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2040 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2041 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2042 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2043 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2044 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2045 POSSIBILITY OF SUCH DAMAGE.
2047 Contact Warner Losh if you have any questions about your use of