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