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