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 20200512 p5 FreeBSD-EN-20:08.tzdata
21 FreeBSD-EN-20:10.build
22 FreeBSD-SA-20:12.libalias
23 FreeBSD-SA-20:13.libalias
24 FreeBSD-SA-20:15.cryptodev
25 FreeBSD-SA-20:16.cryptodev
27 Import tzdata 2020a. [EN-20:08.tzdata]
29 Fix igb interfaces failing to switch to inactive state [EN-20:09.igb]
31 Fix incorrect build host Clang version detection [EN-20:10.build]
33 Fix insufficient packet length validation in libalias [SA-20:12.libalias]
35 Fix memory disclosure vulnerability in libalias [SA-20:13.libalias]
37 Fix use after free in cryptodev module [SA-20:15.cryptodev]
39 Fix insufficient cryptodev MAC key length check [SA-20:16.cryptodev]
41 20200421 p4 FreeBSD-EN-20:07.quotad
43 FreeBSD-SA-20:11.openssl
45 Fix regression in rpc.rquotad with certain NFS servers [EN-20:07.quotad]
47 Fix ipfw invalid mbuf handling [SA-20:10.ipfw]
49 Fix OpenSSL remote denial of service vulnerability [SA-20:11.openssl]
51 20200319 p3 FreeBSD-EN-20:03.sshd
52 FreeBSD-EN-20:05.mlx5en
55 FreeBSD-SA-20:05.if_oce_ioctl
56 FreeBSD-SA-20:06.if_ixl_ioctl
57 FreeBSD-SA-20:07.epair
61 Fix misleading log messages upon successful sshd login [EN-20:03.sshd]
63 Fix packet forwarding performance in mlx5en(4) driver [EN-20:05.mlx5en]
65 Fix incorrect checksum calculations with IPv6 extension headers [EN-20:06.ipv6]
67 Fix TCP IPv6 SYN cache kernel information disclosure [SA-20:04.tcp]
69 Fix insufficient oce(4) ioctl(2) privilege checking [SA-20:05.if_oce_ioctl]
71 Fix insufficient ixl(4) ioctl(2) privilege checking [SA-20:06.if_ixl_ioctl]
73 Fix incorrect user-controlled pointer use in epair [SA-20:07.epair]
75 Fix kernel memory disclosure with nested jails [SA-20:08.jail]
77 Fix multiple denial of service in ntpd [SA-20:09.ntp]
79 20200128 p2 FreeBSD-EN-20:01.ssp
80 FreeBSD-SA-20:01.libfetch
81 FreeBSD-SA-20:03.thrmisc
83 Fix imprecise ordering of SSP canary initialization [EN-20:01.ssp]
85 Fix libfetch buffer overflow [SA-20:01.libfetch]
87 Fix kernel stack data disclosure [SA-20:03.thrmisc]
89 20191112 p1 FreeBSD-EN-19:19.loader
90 FreeBSD-SA-19:25.mcepsc
92 Fix UEFI Loader Memory Fragmentation [EN-19:19.loader]
94 Fix Machine Check Exception on Page Size Change [SA-19:25.mcepsc]
100 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
101 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
102 been removed from mount_fusefs(8). You can safely remove them from
103 your scripts, because they had no effect.
105 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
106 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
107 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
108 sysctls have been removed. If you felt the need to set any of them to
109 a non-default value, please tell asomers@FreeBSD.org why.
112 The fuse(4) module has been renamed to fusefs(4) for consistency with
113 other filesystems. You should update any kld_load="fuse" entries in
114 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
115 "options FUSE" enties in kernel config files.
118 Default permissions on the /var/account/acct file (and copies of it
119 rotated by periodic daily scripts) are changed from 0644 to 0640
120 because the file contains sensitive information that should not be
121 world-readable. If the /var/account directory must be created by
122 rc.d/accounting, the mode used is now 0750. Admins who use the
123 accounting feature are encouraged to change the mode of an existing
124 /var/account directory to 0750 or 0700.
127 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
128 been upgraded to 8.0.1. Please see the 20141231 entry below for
129 information about prerequisites and upgrading, if you are not already
130 using clang 3.5.0 or higher.
133 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
134 functionality needed for the RETPOLINE option should work properly
135 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
138 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
139 8.0.0. Please see the 20141231 entry below for information about
140 prerequisites and upgrading, if you are not already using clang 3.5.0
144 The RETPOLINE option produces non-functional ifunc-using binaries
145 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
146 Once Clang 8 is merged it may be enabled again.
149 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
150 7.0.1. Please see the 20141231 entry below for information about
151 prerequisites and upgrading, if you are not already using clang 3.5.0
155 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
156 compiled into your custom kernel, add 'device xz' statement to the
160 Iflib is no longer unconditionally compiled into the kernel. Drivers
161 using iflib and statically compiled into the kernel, now require
162 the 'device iflib' config option. For the same drivers loaded as
163 modules on kernels not having 'device iflib', the iflib.ko module
164 is loaded automatically.
167 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
168 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
169 servers that have vfs.nfsd.nfs_privport set will only allow mounts
170 from clients using a reserved port#. Since both the FreeBSD and Linux
171 NFSv4 clients use reserved port#s by default, this should not affect
175 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
176 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
177 it produces broken binaries when ifuncs are in use. Users needing
178 GNU ld should install the binutils port or package.
181 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
182 has been converted to a port (misc/ctm) and will be removed from
183 FreeBSD-13. A depreciation warning will be printed to stderr by
184 the ctm command, but the functionality will remain in base for all
188 The stable/12 branch has been created in subversion from head
192 Ports for the DRM modules have been simplified. Now, amd64 users should
193 just install the drm-kmod port. All others should install
196 Graphics hardware that's newer than about 2010 usually works with
197 drm-kmod. For hardware older than 2013, however, some users will need
198 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
199 than 2008 usually only works in drm-legacy-kmod. The graphics team can
200 only commit to hardware made since 2013 due to the complexity of the
201 market and difficulty to test all the older cards effectively. If you
202 have hardware supported by drm-kmod, you are strongly encouraged to use
203 that as you will get better support.
205 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
206 elsewhere, the drm and drm2 modules will be eliminated from the src base
207 soon (with a limited exception for arm). Please update to the package asap
208 and report any issues to x11@freebsd.org.
210 Generally, anybody using the drm*-kmod packages should add
211 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
212 cross-threading surprises, especially with automatic driver
213 loading from X11 startup. These will become the defaults in 13-current
217 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
218 custom kernel and module loading configuration files must be updated
219 accordingly. Moreover, interfaces previous presented as ixlvN to the
220 system are now exposed as iavfN and network configuration files must
221 be adjusted as necessary.
224 OpenSSL has been updated to version 1.1.1. This update included
225 additional various API changes througout the base system. It is
226 important to rebuild third-party software after upgrading. The value
227 of __FreeBSD_version has been bumped accordingly.
230 The legacy DRM modules and drivers have now been added to the loader's
231 module blacklist, in favor of loading them with kld_list in rc.conf(5).
232 The module blacklist may be overridden with the loader.conf(5)
233 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
237 The cam(4) based nda(4) driver will be used over nvd(4) by default on
238 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
239 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
240 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
244 Reproducible build mode is now on by default, in preparation for
245 FreeBSD 12.0. This eliminates build metadata such as the user,
246 host, and time from the kernel (and uname), unless the working tree
247 corresponds to a modified checkout from a version control system.
248 The previous behavior can be obtained by setting the /etc/src.conf
249 knob WITHOUT_REPRODUCIBLE_BUILD.
252 The Yarrow CSPRNG has been removed from the kernel as it has not been
253 supported by its designers since at least 2003. Fortuna has been the
254 default since FreeBSD-11.
257 devctl freeze/thaw have gone into the tree, the rc scripts have been
258 updated to use them and devmatch has been changed. You should update
259 kernel, userland and rc scripts all at the same time.
262 The default interpreter has been switched from 4th to Lua.
263 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
264 interpreter. If you have custom FORTH code you will need to set
265 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
266 src.conf for the build. This will create default hard links between
267 loader and loader_4th instead of loader and loader_lua, the new default.
268 If you are using UEFI it will create the proper hard link to loader.efi.
270 bhyve uses userboot.so. It remains 4th-only until some issues are solved
271 regarding coexisting with multiple versions of FreeBSD are resolved.
274 ls(1) now respects the COLORTERM environment variable used in other
275 systems and software to indicate that a colored terminal is both
276 supported and desired. If ls(1) is suddenly emitting colors, they may
277 be disabled again by either removing the unwanted COLORTERM from your
278 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
279 may not be observed in a future release.
282 The default pager for most commands has been changed to "less". To
283 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
287 The jedec_ts(4) driver has been removed. A superset of its functionality
288 is available in the jedec_dimm(4) driver, and the manpage for that
289 driver includes migration instructions. If you have "device jedec_ts"
290 in your kernel configuration file, it must be removed.
293 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
294 This should have no effect if the kernel is booted via BIOS/legacy boot.
295 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
296 has a buggy firmware that prevents a successful boot due to use of
300 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
301 support has been removed from the tree. These ports were
302 obsolete and/or known to be broken for many years.
305 loader.efi has been augmented to participate more fully in the
306 UEFI boot manager protocol. loader.efi will now look at the
307 BootXXXX environment variable to determine if a specific kernel
308 or root partition was specified. XXXX is derived from BootCurrent.
309 efibootmgr(8) manages these standard UEFI variables.
312 zfsloader's functionality has now been folded into loader.
313 zfsloader is no longer necessary once you've updated your
314 boot blocks. For a transition period, we will install a
315 hardlink for zfsloader to loader to allow a smooth transition
316 until the boot blocks can be updated (hard link because old
317 zfs boot blocks don't understand symlinks).
320 ARM64 now have efifb support, if you want to have serial console
321 on your arm64 board when an screen is connected and the bootloader
322 setup a frambuffer for us to use, just add :
326 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
327 an screen connected as the firmware will setup a framebuffer are that
328 u-boot will expose as an EFI framebuffer.
331 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
332 or take steps to update /etc/passwd before doing installworld on
333 existing systems. Do not skip the "mergemaster -Fp" step before
334 installworld, as described in the update procedures near the bottom
335 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
336 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
337 the ntp config file contain options that change file/dir locations.
338 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
339 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
340 taking steps to ensure that all required files/dirs are accessible
344 Big endian arm support has been removed.
347 The static environment setup in kernel configs is no longer mutually
348 exclusive with the loader(8) environment by default. In order to
349 restore the previous default behavior of disabling the loader(8)
350 environment if a static environment is present, you must specify
351 loader_env.disabled=1 in the static environment.
354 The ABI of syscalls used by management tools like sockstat and
355 netstat has been broken to allow 32-bit binaries to work on
356 64-bit kernels without modification. These programs will need
357 to match the kernel in order to function. External programs may
358 require minor modifications to accommodate a change of type in
359 structures from pointers to 64-bit virtual addresses.
362 On i386 and amd64 atomics are now inlined. Out of tree modules using
363 atomics will need to be rebuilt.
366 The '%I' format in the kern.corefile sysctl limits the number of
367 core files that a process can generate to the number stored in the
368 debug.ncores sysctl. The '%I' format is replaced by the single digit
369 index. Previously, if all indexes were taken the kernel would overwrite
370 only a core file with the highest index in a filename.
371 Currently the system will create a new core file if there is a free
372 index or if all slots are taken it will overwrite the oldest one.
375 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
376 6.0.1. Please see the 20141231 entry below for information about
377 prerequisites and upgrading, if you are not already using clang 3.5.0
381 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
382 needed to be changed to work with it. This change was made with r335763
383 and requires a mergemaster / etcupdate / etc to update the installed file.
386 r334930 changed the interface between the NFS modules, so they all
387 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
390 As of r334391 lld is the default amd64 system linker; it is installed
391 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
395 The kernel / userland interface for devinfo changed, so you'll
396 need a new kernel and userland as a pair for it to work (rebuilding
397 lib/libdevinfo is all that's required). devinfo and devmatch will
398 not work, but everything else will when there's a mismatch.
401 The on-disk format for hwpmc callchain records has changed to include
402 threadid corresponding to a given record. This changes the field offsets
403 and thus requires that libpmcstat be rebuilt before using a kernel
407 The vxge(4) driver has been removed. This driver was introduced into
408 HEAD one week before the Exar left the Ethernet market and is not
409 known to be used. If you have device vxge in your kernel config file
413 The amd64 kernel now requires a ld that supports ifunc to produce a
414 working kernel, either lld or a newer binutils. lld is built by default
415 on amd64, and the 'buildkernel' target uses it automatically. However,
416 it is not the default linker, so building the kernel the traditional
417 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
418 binutils port/package). lld will soon be default, and this requirement
421 NOTE: As of r334391 lld is the default system linker on amd64, and no
422 workaround is necessary.
425 The nxge(4) driver has been removed. This driver was for PCI-X 10g
426 cards made by s2io/Neterion. The company was aquired by Exar and
427 no longer sells or supports Ethernet products. If you have device
428 nxge in your kernel config file it must be removed.
431 The tz database (tzdb) has been updated to 2018e. This version more
432 correctly models time stamps in time zones with negative DST such as
433 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
434 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
435 time zone abbreviations and the tm_isdst flag.
438 The ixgb(4) driver has been removed. This driver was for an early and
439 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
440 quickly shifted to the long lived ixgbe family. If you have device
441 ixgb in your kernel config file it must be removed.
444 The lmc(4) driver has been removed. This was a WAN interface
445 card that was already reportedly rare in 2003, and had an ambiguous
446 license. If you have device lmc in your kernel config file it must
450 Support for Arcnet networks has been removed. If you have device
451 arcnet or device cm in your kernel config file they must be
455 Support for FDDI networks has been removed. If you have device
456 fddi or device fpa in your kernel config file they must be
460 In addition to supporting RFC 3164 formatted messages, the
461 syslogd(8) service is now capable of parsing RFC 5424 formatted
462 log messages. The main benefit of using RFC 5424 is that clients
463 may now send log messages with timestamps containing year numbers,
464 microseconds and time zone offsets.
466 Similarly, the syslog(3) C library function has been altered to
467 send RFC 5424 formatted messages to the local system logging
468 daemon. On systems using syslogd(8), this change should have no
469 negative impact, as long as syslogd(8) and the C library are
470 updated at the same time. On systems using a different system
471 logging daemon, it may be necessary to make configuration
472 adjustments, depending on the software used.
474 When using syslog-ng, add the 'syslog-protocol' flag to local
475 input sources to enable parsing of RFC 5424 formatted messages:
478 unix-dgram("/var/run/log" flags(syslog-protocol));
481 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
482 of the 'imuxsock' module to let messages be processed by the
483 regular RFC 3164/5424 parsing pipeline:
485 module(load="imuxsock" SysSock.UseSpecialParser="off")
487 Do note that these changes only affect communication between local
488 applications and syslogd(8). The format that syslogd(8) uses to
489 store messages on disk or forward messages to other systems
490 remains unchanged. syslogd(8) still uses RFC 3164 for these
491 purposes. Options to customize this behaviour will be added in the
492 future. Utilities that process log files stored in /var/log are
493 thus expected to continue to function as before.
495 __FreeBSD_version has been incremented to 1200061 to denote this
499 Support for token ring networks has been removed. If you
500 have "device token" in your kernel config you should remove
501 it. No device drivers supported token ring.
504 makefs was modified to be able to tag ISO9660 El Torito boot catalog
505 entries as EFI instead of overloading the i386 tag as done previously.
506 The amd64 mkisoimages.sh script used to build amd64 ISO images for
507 release was updated to use this. This may mean that makefs must be
508 updated before "make cdrom" can be run in the release directory. This
509 should be as simple as:
511 $ cd $SRCDIR/usr.sbin/makefs
512 $ make depend all install
515 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
516 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
517 Co-existance for the transition period will come shortly. Booting is a
518 complex environment and test coverage for Lua-enabled loaders has been
519 thin, so it would be prudent to assume it might not work and make
520 provisions for backup boot methods.
523 devmatch functionality has been turned on in devd. It will automatically
524 load drivers for unattached devices. This may cause unexpected drivers to
525 be loaded. Please report any problems to current@ and imp@freebsd.org.
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 still
544 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
545 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
787 full procedure documented below under the heading "To rebuild
788 everything and install it on the current system." Specifically,
789 a reboot is required after installing the new kernel before
793 The NATM framework including the en(4), fatm(4), hatm(4), and
794 patm(4) devices has been removed. Consumers should plan a
795 migration before the end-of-life date for FreeBSD 11.
798 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
799 diff has not been implemented, if those are needed a newer version of
800 GNU diff is available via the diffutils package under the gdiff name.
803 As of r316810 for ipfilter, keep frags is no longer assumed when
804 keep state is specified in a rule. r316810 aligns ipfilter with
805 documentation in man pages separating keep frags from keep state.
806 This allows keep state to be specified without forcing keep frags
807 and allows keep frags to be specified independently of keep state.
808 To maintain previous behaviour, also specify keep frags with
809 keep state (as documented in ipf.conf.5).
812 arm64 builds now use the base system LLD 4.0.0 linker by default,
813 instead of requiring that the aarch64-binutils port or package be
814 installed. To continue using aarch64-binutils, set
815 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
818 The UDP optimization in entry 20160818 that added the sysctl
819 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
820 packets will no longer be treated as L3 broadcast packets.
823 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
824 use any explicitly assigned loopback address available in the jail
825 instead of using the first assigned address of the jail.
828 The ctl.ko module no longer implements the iSCSI target frontend:
829 cfiscsi.ko does instead.
831 If building cfiscsi.ko as a kernel module, the module can be loaded
832 via one of the following methods:
833 - `cfiscsi_load="YES"` in loader.conf(5).
834 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
835 - ctladm(8)/ctld(8), when compiled with iSCSI support
836 (`WITH_ISCSI=yes` in src.conf(5))
838 Please see cfiscsi(4) for more details.
841 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
842 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
843 same source (previously, the dependency of mmcsd.ko on mmc.ko was
844 missing, but mmcsd.ko now will refuse to load if it is incompatible
848 The syntax of ipfw(8) named states was changed to avoid ambiguity.
849 If you have used named states in the firewall rules, you need to modify
850 them after installworld and before rebooting. Now named states must
851 be prefixed with colon.
854 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
855 removed as the userland we provide cannot use them. The KMS version
856 (sys/dev/drm2) supports the same hardware.
859 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
860 Please see the 20141231 entry below for information about prerequisites
861 and upgrading, if you are not already using clang 3.5.0 or higher.
864 The code that provides support for ZFS .zfs/ directory functionality
865 has been reimplemented. It's not possible now to create a snapshot
866 by mkdir under .zfs/snapshot/. That should be the only user visible
870 EISA bus support has been removed. The WITH_EISA option is no longer
874 MCA bus support has been removed.
877 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
878 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
881 The EM_MULTIQUEUE kernel configuration option is deprecated now that
882 the em(4) driver conforms to iflib specifications.
885 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
886 IFLIB. If you have a custom kernel configuration that excludes em(4)
887 but you use igb(4), you need to re-add em(4) to your custom configuration.
890 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
891 Please see the 20141231 entry below for information about prerequisites
892 and upgrading, if you are not already using clang 3.5.0 or higher.
895 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
896 Please see the 20141231 entry below for information about prerequisites
897 and upgrading, if you are not already using clang 3.5.0 or higher.
900 The layout of the pmap structure has changed for powerpc to put the pmap
901 statistics at the front for all CPU variations. libkvm(3) and all tools
902 that link against it need to be recompiled.
905 isl(4) and cyapa(4) drivers now require a new driver,
906 chromebook_platform(4), to work properly on Chromebook-class hardware.
907 On other types of hardware the drivers may need to be configured using
908 device hints. Please see the corresponding manual pages for details.
911 The urtwn(4) driver was merged into rtwn(4) and now consists of
912 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
914 Also, firmware for RTL8188CE was renamed due to possible name
915 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
918 GNU rcs has been removed from base. It is available as packages:
919 - rcs: Latest GPLv3 GNU rcs version.
920 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
924 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
925 modules now requires that the kernel configuration contain the
926 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
929 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
930 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
933 Relocatable object files with the extension of .So have been renamed
934 to use an extension of .pico instead. The purpose of this change is
935 to avoid a name clash with shared libraries on case-insensitive file
936 systems. On those file systems, foo.So is the same file as foo.so.
939 GNU rcs has been turned off by default. It can (temporarily) be built
940 again by adding WITH_RCS knob in src.conf.
941 Otherwise, GNU rcs is available from packages:
942 - rcs: Latest GPLv3 GNU rcs version.
943 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
946 The backup_uses_rcs functionality has been removed from rc.subr.
949 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
950 two separate components, QUEUE_MACRO_DEBUG_TRACE and
951 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
952 QUEUE_MACRO_DEBUG behavior.
955 r304787 changed some ioctl interfaces between the iSCSI userspace
956 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
957 rebuilt to work with new kernels. __FreeBSD_version has been bumped
961 The UDP receive code has been updated to only treat incoming UDP
962 packets that were addressed to an L2 broadcast address as L3
963 broadcast packets. It is not expected that this will affect any
964 standards-conforming UDP application. The new behaviour can be
965 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
969 Remove the openbsd_poll system call.
970 __FreeBSD_version has been bumped because of this.
973 The stable/11 branch has been created from head@r302406.
976 The libc stub for the pipe(2) system call has been replaced with
977 a wrapper that calls the pipe2(2) system call and the pipe(2)
978 system call is now only implemented by the kernels that include
979 "options COMPAT_FREEBSD10" in their config file (this is the
980 default). Users should ensure that this option is enabled in
981 their kernel or upgrade userspace to r302092 before upgrading their
985 CAM will now strip leading spaces from SCSI disks' serial numbers.
986 This will affect users who create UFS filesystems on SCSI disks using
987 those disk's diskid device nodes. For example, if /etc/fstab
988 previously contained a line like
989 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
990 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
991 transforms like gmirror may also be affected. ZFS users should
995 The bitstring(3) API has been updated with new functionality and
996 improved performance. But it is binary-incompatible with the old API.
997 Objects built with the new headers may not be linked against objects
998 built with the old headers.
1001 The brk and sbrk functions have been removed from libc on arm64.
1002 Binutils from ports has been updated to not link to these
1003 functions and should be updated to the latest version before
1004 installing a new libc.
1007 The armv6 port now defaults to hard float ABI. Limited support
1008 for running both hardfloat and soft float on the same system
1009 is available using the libraries installed with -DWITH_LIBSOFT.
1010 This has only been tested as an upgrade path for installworld
1011 and packages may fail or need manual intervention to run. New
1012 packages will be needed.
1014 To update an existing self-hosted armv6hf system, you must add
1015 TARGET_ARCH=armv6 on the make command line for both the build
1016 and the install steps.
1019 Kernel modules compiled outside of a kernel build now default to
1020 installing to /boot/modules instead of /boot/kernel. Many kernel
1021 modules built this way (such as those in ports) already overrode
1022 KMODDIR explicitly to install into /boot/modules. However,
1023 manually building and installing a module from /sys/modules will
1024 now install to /boot/modules instead of /boot/kernel.
1027 The CAM I/O scheduler has been committed to the kernel. There should be
1028 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1029 list of known rogues that claim support for this but actually corrupt
1030 data is believed to be complete, be on the lookout for data
1031 corruption. The known rogue list is believed to be complete:
1033 o Crucial MX100, M550 drives with MU01 firmware.
1034 o Micron M510 and M550 drives with MU01 firmware.
1035 o Micron M500 prior to MU07 firmware
1036 o Samsung 830, 840, and 850 all firmwares
1037 o FCCT M500 all firmwares
1039 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1040 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1041 updated firmware. Black listed drives will work correctly because these
1042 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1043 this list is the same as found in Linux, it's believed there are no
1044 other rogues in the market place. All other models from the above
1047 To be safe, if you are at all concerned, you can quirk each of your
1048 drives to prevent NCQ from being sent by setting:
1049 kern.cam.ada.X.quirks="0x2"
1050 in loader.conf. If the drive requires the 4k sector quirk, set the
1051 quirks entry to 0x3.
1054 The FAST_DEPEND build option has been removed and its functionality is
1055 now the one true way. The old mkdep(1) style of 'make depend' has
1056 been removed. See 20160311 for further details.
1059 Resource range types have grown from unsigned long to uintmax_t. All
1060 drivers, and anything using libdevinfo, need to be recompiled.
1063 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1064 builds. It no longer runs mkdep(1) during 'make depend', and the
1065 'make depend' stage can safely be skipped now as it is auto ran
1066 when building 'make all' and will generate all SRCS and DPSRCS before
1067 building anything else. Dependencies are gathered at compile time with
1068 -MF flags kept in separate .depend files per object file. Users should
1069 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1070 stale .depend files.
1073 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1074 kernel modules. Therefore, if you load any kernel modules at boot time,
1075 please install the boot loaders after you install the kernel, but before
1079 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1080 make installkernel KERNCONF=YOUR_KERNEL_HERE
1081 make -C sys/boot install
1082 <reboot in single user>
1084 Then follow the usual steps, described in the General Notes section,
1088 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1089 see the 20141231 entry below for information about prerequisites and
1090 upgrading, if you are not already using clang 3.5.0 or higher.
1093 The AIO subsystem is now a standard part of the kernel. The
1094 VFS_AIO kernel option and aio.ko kernel module have been removed.
1095 Due to stability concerns, asynchronous I/O requests are only
1096 permitted on sockets and raw disks by default. To enable
1097 asynchronous I/O requests on all file types, set the
1098 vfs.aio.enable_unsafe sysctl to a non-zero value.
1101 The ELF object manipulation tool objcopy is now provided by the
1102 ELF Tool Chain project rather than by GNU binutils. It should be a
1103 drop-in replacement, with the addition of arm64 support. The
1104 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1105 to obtain the GNU version if necessary.
1108 Building ZFS pools on top of zvols is prohibited by default. That
1109 feature has never worked safely; it's always been prone to deadlocks.
1110 Using a zvol as the backing store for a VM guest's virtual disk will
1111 still work, even if the guest is using ZFS. Legacy behavior can be
1112 restored by setting vfs.zfs.vol.recursive=1.
1115 The NONE and HPN patches has been removed from OpenSSH. They are
1116 still available in the security/openssh-portable port.
1119 With the addition of ypldap(8), a new _ypldap user is now required
1120 during installworld. "mergemaster -p" can be used to add the user
1121 prior to installworld, as documented in the handbook.
1124 The tftp loader (pxeboot) now uses the option root-path directive. As a
1125 consequence it no longer looks for a pxeboot.4th file on the tftp
1126 server. Instead it uses the regular /boot infrastructure as with the
1130 The code to start recording plug and play data into the modules has
1131 been committed. While the old tools will properly build a new kernel,
1132 a number of warnings about "unknown metadata record 4" will be produced
1133 for an older kldxref. To avoid such warnings, make sure to rebuild
1134 the kernel toolchain (or world). Make sure that you have r292078 or
1135 later when trying to build 292077 or later before rebuilding.
1138 Debug data files are now built by default with 'make buildworld' and
1139 installed with 'make installworld'. This facilitates debugging but
1140 requires more disk space both during the build and for the installed
1141 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1145 r291527 changed the internal interface between the nfsd.ko and
1146 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1147 __FreeBSD_version has been bumped because of this.
1150 Add support for unicode collation strings leads to a change of
1151 order of files listed by ls(1) for example. To get back to the old
1152 behaviour, set LC_COLLATE environment variable to "C".
1154 Databases administrators will need to reindex their databases given
1155 collation results will be different.
1157 Due to a bug in install(1) it is recommended to remove the ancient
1158 locales before running make installworld.
1160 rm -rf /usr/share/locale/*
1163 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1164 libcrypto.so.7 or libssl.so.7 must be recompiled.
1167 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1168 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1169 should be replaced with isp_2400 and isp_2500 modules respectively.
1172 The build previously allowed using 'make -n' to not recurse into
1173 sub-directories while showing what commands would be executed, and
1174 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1175 and 'make -N' will not.
1178 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1179 and etcupdate will now use this file. A custom sendmail.cf is now
1180 updated via this mechanism rather than via installworld. If you had
1181 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1182 want to remove the exclusion or change it to "always install".
1183 /etc/mail/sendmail.cf is now managed the same way regardless of
1184 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1185 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1188 Compatibility shims for legacy ATA device names have been removed.
1189 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1190 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1191 environment variables, /dev/ad* and /dev/ar* symbolic links.
1194 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1195 Please see the 20141231 entry below for information about prerequisites
1196 and upgrading, if you are not already using clang 3.5.0 or higher.
1199 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1200 and renamed from .symbols to .debug. This reduces the size requirements
1201 on the boot partition or file system and provides consistency with
1202 userland debug files.
1204 When using the supported kernel installation method the
1205 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1206 as is done with /boot/kernel.
1208 Developers wishing to maintain the historical behavior of installing
1209 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1212 The wireless drivers had undergone changes that remove the 'parent
1213 interface' from the ifconfig -l output. The rc.d network scripts
1214 used to check presence of a parent interface in the list, so old
1215 scripts would fail to start wireless networking. Thus, etcupdate(3)
1216 or mergemaster(8) run is required after kernel update, to update your
1217 rc.d scripts in /etc.
1220 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1221 These configurations are now automatically interpreted as
1222 'scrub fragment reassemble'.
1225 Kernel-loadable modules for the random(4) device are back. To use
1226 them, the kernel must have
1229 options RANDOM_LOADABLE
1231 kldload(8) can then be used to load random_fortuna.ko
1232 or random_yarrow.ko. Please note that due to the indirect
1233 function calls that the loadable modules need to provide,
1234 the build-in variants will be slightly more efficient.
1236 The random(4) kernel option RANDOM_DUMMY has been retired due to
1237 unpopularity. It was not all that useful anyway.
1240 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1241 Control over building the ELF Tool Chain tools is now provided by
1242 the WITHOUT_TOOLCHAIN knob.
1245 The polarity of Pulse Per Second (PPS) capture events with the
1246 uart(4) driver has been corrected. Prior to this change the PPS
1247 "assert" event corresponded to the trailing edge of a positive PPS
1248 pulse and the "clear" event was the leading edge of the next pulse.
1250 As the width of a PPS pulse in a typical GPS receiver is on the
1251 order of 1 millisecond, most users will not notice any significant
1252 difference with this change.
1254 Anyone who has compensated for the historical polarity reversal by
1255 configuring a negative offset equal to the pulse width will need to
1256 remove that workaround.
1259 The default group assigned to /dev/dri entries has been changed
1260 from 'wheel' to 'video' with the id of '44'. If you want to have
1261 access to the dri devices please add yourself to the video group
1264 # pw groupmod video -m $USER
1267 The menu.rc and loader.rc files will now be replaced during
1268 upgrades. Please migrate local changes to menu.rc.local and
1269 loader.rc.local instead.
1272 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1273 strings and strip have been removed. The src.conf(5) knob
1274 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1277 As ZFS requires more kernel stack pages than is the default on some
1278 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1279 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1281 Please consider using 'options KSTACK_PAGES=X' where X is greater
1282 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1285 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1286 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1287 default, i.e., they will not contain "::". For example, instead
1288 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1289 to have a more specific match, such as different map entries for
1290 IPv6:0:0 vs IPv6:0. This change requires that configuration
1291 data (including maps, files, classes, custom ruleset, etc.) must
1292 use the same format, so make certain such configuration data is
1293 upgrading. As a very simple check search for patterns like
1294 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1295 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1296 the cf option UseCompressedIPv6Addresses.
1299 The default kernel entropy-processing algorithm is now
1300 Fortuna, replacing Yarrow.
1302 Assuming you have 'device random' in your kernel config
1303 file, the configurations allow a kernel option to override
1304 this default. You may choose *ONE* of:
1306 options RANDOM_YARROW # Legacy /dev/random algorithm.
1307 options RANDOM_DUMMY # Blocking-only driver.
1309 If you have neither, you get Fortuna. For most people,
1310 read no further, Fortuna will give a /dev/random that works
1311 like it always used to, and the difference will be irrelevant.
1313 If you remove 'device random', you get *NO* kernel-processed
1314 entropy at all. This may be acceptable to folks building
1315 embedded systems, but has complications. Carry on reading,
1316 and it is assumed you know what you need.
1318 *PLEASE* read random(4) and random(9) if you are in the
1319 habit of tweaking kernel configs, and/or if you are a member
1320 of the embedded community, wanting specific and not-usual
1321 behaviour from your security subsystems.
1323 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1324 random', you will NOT have a functioning /dev/random, and
1325 many cryptographic features will not work, including SSH.
1326 You may also find strange behaviour from the random(3) set
1327 of library functions, in particular sranddev(3), srandomdev(3)
1328 and arc4random(3). The reason for this is that the KERN_ARND
1329 sysctl only returns entropy if it thinks it has some to
1330 share, and with RANDOM_DUMMY or no 'device random' this
1334 An additional fix for the issue described in the 20150614 sendmail
1335 entry below has been committed in revision 284717.
1338 FreeBSD's old make (fmake) has been removed from the system. It is
1339 available as the devel/fmake port or via pkg install fmake.
1342 The fix for the issue described in the 20150614 sendmail entry
1343 below has been committed in revision 284436. The work
1344 around described in that entry is no longer needed unless the
1345 default setting is overridden by a confDH_PARAMETERS configuration
1346 setting of '5' or pointing to a 512 bit DH parameter file.
1349 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1350 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1351 and devel/kyua to version 0.20+ and adjust any calling code to work
1352 with Kyuafile and kyua.
1355 The import of openssl to address the FreeBSD-SA-15:10.openssl
1356 security advisory includes a change which rejects handshakes
1357 with DH parameters below 768 bits. sendmail releases prior
1358 to 8.15.2 (not yet released), defaulted to a 512 bit
1359 DH parameter setting for client connections. To work around
1360 this interoperability, sendmail can be configured to use a
1361 2048 bit DH parameter by:
1363 1. Edit /etc/mail/`hostname`.mc
1364 2. If a setting for confDH_PARAMETERS does not exist or
1365 exists and is set to a string beginning with '5',
1366 replace it with '2'.
1367 3. If a setting for confDH_PARAMETERS exists and is set to
1368 a file path, create a new file with:
1369 openssl dhparam -out /path/to/file 2048
1370 4. Rebuild the .cf file:
1371 cd /etc/mail/; make; make install
1372 5. Restart sendmail:
1373 cd /etc/mail/; make restart
1375 A sendmail patch is coming, at which time this file will be
1379 Generation of legacy formatted entries have been disabled by default
1380 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1381 entries were converted to use the new format by default when the new,
1382 machine independent format have been added and supported since FreeBSD
1385 Please see the pwd_mkdb(8) manual page for further details.
1388 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1389 20141231 entry below for information about prerequisites and upgrading,
1390 if you are not already using 3.5.0 or higher.
1393 TI platform code switched to using vendor DTS files and this update
1394 may break existing systems running on Beaglebone, Beaglebone Black,
1397 - dtb files should be regenerated/reinstalled. Filenames are the
1398 same but content is different now
1399 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1400 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1401 addressing scheme is now pin 25 on /dev/gpioc3.
1402 - Pandaboard: /etc/ttys should be updated, serial console device is
1403 now /dev/ttyu2, not /dev/ttyu0
1406 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1407 If you need the GNU extension from groff soelim(1), install groff
1408 from package: pkg install groff, or via ports: textproc/groff.
1411 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1412 defined in symlink(7); previously symlinks were silently ignored.
1415 The const qualifier has been removed from iconv(3) to comply with
1416 POSIX. The ports tree is aware of this from r384038 onwards.
1419 Libraries specified by LIBADD in Makefiles must have a corresponding
1420 DPADD_<lib> variable to ensure correct dependencies. This is now
1421 enforced in src.libnames.mk.
1424 From legacy ata(4) driver was removed support for SATA controllers
1425 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1426 Kernel modules ataahci and ataadaptec were removed completely,
1427 replaced by ahci and mvs modules respectively.
1430 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1431 the 20141231 entry below for information about prerequisites and
1432 upgrading, if you are not already using 3.5.0 or higher.
1435 The 32-bit PowerPC kernel has been changed to a position-independent
1436 executable. This can only be booted with a version of loader(8)
1437 newer than January 31, 2015, so make sure to update both world and
1438 kernel before rebooting.
1441 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1442 but before r278950, the RNG was not seeded properly. Immediately
1443 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1444 ssh keys or openssl keys) that were generated w/ a kernel from that
1445 range. This does not affect programs that directly used /dev/random
1446 or /dev/urandom. All userland uses of arc4random(3) are affected.
1449 The autofs(4) ABI was changed in order to restore binary compatibility
1450 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1451 with the new kernel.
1454 The powerpc64 kernel has been changed to a position-independent
1455 executable. This can only be booted with a new version of loader(8),
1456 so make sure to update both world and kernel before rebooting.
1459 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1460 only release, no new features have been added. Please see the 20141231
1461 entry below for information about prerequisites and upgrading, if you
1462 are not already using 3.5.0.
1465 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1466 taken from the ELF Tool Chain project rather than GNU binutils. They
1467 should be drop-in replacements, with the addition of arm64 support.
1468 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1469 binutils tools, if necessary. See 20150805 for updated information.
1472 The default Unbound configuration now enables remote control
1473 using a local socket. Users who have already enabled the
1474 local_unbound service should regenerate their configuration
1475 by running "service local_unbound setup" as root.
1478 The GNU texinfo and GNU info pages have been removed.
1479 To be able to view GNU info pages please install texinfo from ports.
1482 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1484 As of this release, a prerequisite for building clang, llvm and lldb is
1485 a C++11 capable compiler and C++11 standard library. This means that to
1486 be able to successfully build the cross-tools stage of buildworld, with
1487 clang as the bootstrap compiler, your system compiler or cross compiler
1488 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1489 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1492 On any standard FreeBSD 10.x or 11.x installation, where clang and
1493 libc++ are on by default (that is, on x86 or arm), this should work out
1496 On 9.x installations where clang is enabled by default, e.g. on x86 and
1497 powerpc, libc++ will not be enabled by default, so libc++ should be
1498 built (with clang) and installed first. If both clang and libc++ are
1499 missing, build clang first, then use it to build libc++.
1501 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1502 the instructions for 9.x above.
1504 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1505 default, and do not build clang.
1507 Many embedded systems are resource constrained, and will not be able to
1508 build clang in a reasonable time, or in some cases at all. In those
1509 cases, cross building bootable systems on amd64 is a workaround.
1511 This new version of clang introduces a number of new warnings, of which
1512 the following are most likely to appear:
1516 This warns in two cases, for both C and C++:
1517 * When the code is trying to take the absolute value of an unsigned
1518 quantity, which is effectively a no-op, and almost never what was
1519 intended. The code should be fixed, if at all possible. If you are
1520 sure that the unsigned quantity can be safely cast to signed, without
1521 loss of information or undefined behavior, you can add an explicit
1522 cast, or disable the warning.
1524 * When the code is trying to take an absolute value, but the called
1525 abs() variant is for the wrong type, which can lead to truncation.
1526 If you want to disable the warning instead of fixing the code, please
1527 make sure that truncation will not occur, or it might lead to unwanted
1530 -Wtautological-undefined-compare and
1531 -Wundefined-bool-conversion
1533 These warn when C++ code is trying to compare 'this' against NULL, while
1534 'this' should never be NULL in well-defined C++ code. However, there is
1535 some legacy (pre C++11) code out there, which actively abuses this
1536 feature, which was less strictly defined in previous C++ versions.
1538 Squid and openjdk do this, for example. The warning can be turned off
1539 for C++98 and earlier, but compiling the code in C++11 mode might result
1540 in unexpected behavior; for example, the parts of the program that are
1541 unreachable could be optimized away.
1544 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1545 kernel sources have been removed. The .h files remain, since some
1546 utilities include them. This will need to be fixed later.
1547 If "mount -t oldnfs ..." is attempted, it will fail.
1548 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1549 the utilities will report errors.
1552 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1553 directories to top level SUBDIR variable when their parent
1554 directory is included in LOCAL_DIRS. Users with build systems with
1555 such hierarchies and without SUBDIR entries in the parent
1556 directory Makefiles should add them or add the directories to
1560 faith(4) and faithd(8) have been removed from the base system. Faith
1561 has been obsolete for a very long time.
1564 vt(4), the new console driver, is enabled by default. It brings
1565 support for Unicode and double-width characters, as well as
1566 support for UEFI and integration with the KMS kernel video
1569 You may need to update your console settings in /etc/rc.conf,
1570 most probably the keymap. During boot, /etc/rc.d/syscons will
1571 indicate what you need to do.
1573 vt(4) still has issues and lacks some features compared to
1574 syscons(4). See the wiki for up-to-date information:
1575 https://wiki.freebsd.org/Newcons
1577 If you want to keep using syscons(4), you can do so by adding
1578 the following line to /boot/loader.conf:
1582 pjdfstest has been integrated into kyua as an opt-in test suite.
1583 Please see share/doc/pjdfstest/README for more details on how to
1587 gperf has been removed from the base system for architectures
1588 that use clang. Ports that require gperf will obtain it from the
1592 pjdfstest has been moved from tools/regression/pjdfstest to
1596 At svn r271982, The default linux compat kernel ABI has been adjusted
1597 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1598 update. If you wish to continue using the linux-f10 compat ports,
1599 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1600 encouraged to update their linux-compat packages to linux-c6 during
1601 their next update cycle.
1604 The ofwfb driver, used to provide a graphics console on PowerPC when
1605 using vt(4), no longer allows mmap() of all physical memory. This
1606 will prevent Xorg on PowerPC with some ATI graphics cards from
1607 initializing properly unless x11-servers/xorg-server is updated to
1611 The xdev targets have been converted to using TARGET and
1612 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1615 The default unbound configuration has been modified to address
1616 issues with reverse lookups on networks that use private
1617 address ranges. If you use the local_unbound service, run
1618 "service local_unbound setup" as root to regenerate your
1619 configuration, then "service local_unbound reload" to load the
1623 The GNU texinfo and GNU info pages are not built and installed
1624 anymore, WITH_INFO knob has been added to allow to built and install
1626 UPDATE: see 20150102 entry on texinfo's removal
1629 The GNU readline library is now an INTERNALLIB - that is, it is
1630 statically linked into consumers (GDB and variants) in the base
1631 system, and the shared library is no longer installed. The
1632 devel/readline port is available for third party software that
1636 The Itanium architecture (ia64) has been removed from the list of
1637 known architectures. This is the first step in the removal of the
1641 Commit r268115 has added NFSv4.1 server support, merged from
1642 projects/nfsv4.1-server. Since this includes changes to the
1643 internal interfaces between the NFS related modules, a full
1644 build of the kernel and modules will be necessary.
1645 __FreeBSD_version has been bumped.
1648 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1649 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1650 which differs from the behaviour controlled by this knob.)
1653 Maximal length of the serial number in CTL was increased from 16 to
1654 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1655 and ctld, need to be rebuilt to work with a new kernel.
1658 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1659 1 respectively to match the upstream numbers. They were out of
1660 sync because, when they were originally added to FreeBSD, the
1661 upstream versions were not respected. These libraries are private
1662 and not yet built by default, so renumbering them should be a
1663 non-issue. However, unclean source trees will yield broken test
1664 programs once the operator executes "make delete-old-libs" after a
1665 "make installworld".
1667 Additionally, the atf-sh binary was made private by moving it into
1668 /usr/libexec/. Already-built shell test programs will keep the
1669 path to the old binary so they will break after "make delete-old"
1672 If you are using WITH_TESTS=yes (not the default), wipe the object
1673 tree and rebuild from scratch to prevent spurious test failures.
1674 This is only needed once: the misnumbered libraries and misplaced
1675 binaries have been added to OptionalObsoleteFiles.inc so they will
1676 be removed during a clean upgrade.
1679 Clang and llvm have been upgraded to 3.4.1 release.
1682 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1683 be removed to avoid issues in the future (and has been added to
1687 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1688 past, it affected all builds that used the bsd.*.mk files. The old
1689 behavior was a bug, but people may have relied upon it. To get this
1690 behavior back, you can .include /etc/src.conf from /etc/make.conf
1691 (which is still global and isn't changed). This also changes the
1692 behavior of incremental builds inside the tree of individual
1693 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1694 Although this has survived make universe and some upgrade scenarios,
1695 other upgrade scenarios may have broken. At least one form of
1696 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1697 as well... In cases where MAKESYSPATH isn't working with this
1698 setting, you'll need to set it to the full path to your tree.
1700 One side effect of all this cleaning up is that bsd.compiler.mk
1701 is no longer implicitly included by bsd.own.mk. If you wish to
1702 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1706 The lindev device has been removed since /dev/full has been made a
1707 standard device. __FreeBSD_version has been bumped.
1710 The knob WITHOUT_VI was added to the base system, which controls
1711 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1712 in order to reorder files share/termcap and didn't build ex(1) as a
1713 build tool, so building/installing with WITH_VI is highly advised for
1714 build hosts for older releases.
1716 This issue has been fixed in stable/9 and stable/10 in r277022 and
1717 r276991, respectively.
1720 The YES_HESIOD knob has been removed. It has been obsolete for
1721 a decade. Please move to using WITH_HESIOD instead or your builds
1722 will silently lack HESIOD.
1725 The uart(4) driver has been changed with respect to its handling
1726 of the low-level console. Previously the uart(4) driver prevented
1727 any process from changing the baudrate or the CLOCAL and HUPCL
1728 control flags. By removing the restrictions, operators can make
1729 changes to the serial console port without having to reboot.
1730 However, when getty(8) is started on the serial device that is
1731 associated with the low-level console, a misconfigured terminal
1732 line in /etc/ttys will now have a real impact.
1733 Before upgrading the kernel, make sure that /etc/ttys has the
1734 serial console device configured as 3wire without baudrate to
1735 preserve the previous behaviour. E.g:
1736 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1739 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1740 to improve performance. To re-enable it, if needed, run rpcbind
1741 with command line option -W.
1744 Switched back to the GPL dtc compiler due to updates in the upstream
1745 dts files not being supported by the BSDL dtc compiler. You will need
1746 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1747 may result while building dtb files during a kernel build if you fail
1748 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1751 Clang and llvm have been upgraded to 3.4 release.
1754 The nve(4) driver has been removed. Please use the nfe(4) driver
1755 for NVIDIA nForce MCP Ethernet adapters instead.
1758 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1759 This could cause certain C++ applications using shared libraries built
1760 against the previous version of libc++ to crash. The incompatibility
1761 has now been fixed, but any C++ applications or shared libraries built
1762 between r261283 and r261801 should be recompiled.
1765 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1766 capability mode support. Please note that enabling the feature in
1767 kernel is still highly recommended.
1770 OpenSSH is now built with sandbox support, and will use sandbox as
1771 the default privilege separation method. This requires Capsicum
1772 capability mode support in kernel.
1775 The libelf and libdwarf libraries have been updated to newer
1776 versions from upstream. Shared library version numbers for
1777 these two libraries were bumped. Any ports or binaries
1778 requiring these two libraries should be recompiled.
1779 __FreeBSD_version is bumped to 1100006.
1782 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1783 instead of providing an explicit one, this would prevent such
1784 Makefile from providing its own Kyuafile in the future during
1785 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1786 intervention is needed to clean an objdir if you use NO_CLEAN:
1787 # find /usr/obj -name Kyuafile | xargs rm -f
1790 The behavior of gss_pseudo_random() for the krb5 mechanism
1791 has changed, for applications requesting a longer random string
1792 than produced by the underlying enctype's pseudo-random() function.
1793 In particular, the random string produced from a session key of
1794 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1795 be different at the 17th octet and later, after this change.
1796 The counter used in the PRF+ construction is now encoded as a
1797 big-endian integer in accordance with RFC 4402.
1798 __FreeBSD_version is bumped to 1100004.
1801 The WITHOUT_ATF build knob has been removed and its functionality
1802 has been subsumed into the more generic WITHOUT_TESTS. If you were
1803 using the former to disable the build of the ATF libraries, you
1804 should change your settings to use the latter.
1807 The default version of mtree is nmtree which is obtained from
1808 NetBSD. The output is generally the same, but may vary
1809 slightly. If you found you need identical output adding
1810 "-F freebsd9" to the command line should do the trick. For the
1811 time being, the old mtree is available as fmtree.
1814 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1815 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1816 1.1.4_8 and verify bsdyml not linked in, before running "make
1818 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1820 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1823 The stable/10 branch has been created in subversion from head
1830 Avoid using make -j when upgrading. While generally safe, there are
1831 sometimes problems using -j to upgrade. If your upgrade fails with
1832 -j, please try again without -j. From time to time in the past there
1833 have been problems using -j with buildworld and/or installworld. This
1834 is especially true when upgrading between "distant" versions (eg one
1835 that cross a major release boundary or several minor releases, or when
1836 several months have passed on the -current branch).
1838 Sometimes, obscure build problems are the result of environment
1839 poisoning. This can happen because the make utility reads its
1840 environment when searching for values for global variables. To run
1841 your build attempts in an "environmental clean room", prefix all make
1842 commands with 'env -i '. See the env(1) manual page for more details.
1844 When upgrading from one major version to another it is generally best to
1845 upgrade to the latest code in the currently installed branch first, then
1846 do an upgrade to the new branch. This is the best-tested upgrade path,
1847 and has the highest probability of being successful. Please try this
1848 approach if you encounter problems with a major version upgrade. Since
1849 the stable 4.x branch point, one has generally been able to upgrade from
1850 anywhere in the most recent stable branch to head / current (or even the
1851 last couple of stable branches). See the top of this file when there's
1854 When upgrading a live system, having a root shell around before
1855 installing anything can help undo problems. Not having a root shell
1856 around can lead to problems if pam has changed too much from your
1857 starting point to allow continued authentication after the upgrade.
1859 This file should be read as a log of events. When a later event changes
1860 information of a prior event, the prior event should not be deleted.
1861 Instead, a pointer to the entry with the new information should be
1862 placed in the old entry. Readers of this file should also sanity check
1863 older entries before relying on them blindly. Authors of new entries
1864 should write them with this in mind.
1868 When upgrading the boot ZFS pool to a new version, always follow
1871 1.) recompile and reinstall the ZFS boot loader and boot block
1872 (this is part of "make buildworld" and "make installworld")
1874 2.) update the ZFS boot block on your boot drive
1876 The following example updates the ZFS boot block on the first
1877 partition (freebsd-boot) of a GPT partitioned drive ada0:
1878 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1880 Non-boot pools do not need these updates.
1884 If you are updating from a prior version of FreeBSD (even one just
1885 a few days old), you should follow this procedure. It is the most
1886 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1888 make kernel-toolchain
1889 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1890 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1892 To test a kernel once
1893 ---------------------
1894 If you just want to boot a kernel once (because you are not sure
1895 if it works, or if you want to boot a known bad kernel to provide
1896 debugging information) run
1897 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1898 nextboot -k testkernel
1900 To rebuild everything and install it on the current system.
1901 -----------------------------------------------------------
1902 # Note: sometimes if you are running current you gotta do more than
1903 # is listed here if you are upgrading from a really old current.
1905 <make sure you have good level 0 dumps>
1907 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1908 make installkernel KERNCONF=YOUR_KERNEL_HERE
1910 <reboot in single user> [3]
1917 To cross-install current onto a separate partition
1918 --------------------------------------------------
1919 # In this approach we use a separate partition to hold
1920 # current's root, 'usr', and 'var' directories. A partition
1921 # holding "/", "/usr" and "/var" should be about 2GB in
1924 <make sure you have good level 0 dumps>
1927 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1928 <maybe newfs current's root partition>
1929 <mount current's root partition on directory ${CURRENT_ROOT}>
1930 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1931 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1932 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1933 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1934 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1935 <reboot into current>
1936 <do a "native" rebuild/install as described in the previous section>
1937 <maybe install compatibility libraries from ports/misc/compat*>
1941 To upgrade in-place from stable to current
1942 ----------------------------------------------
1943 <make sure you have good level 0 dumps>
1945 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1946 make installkernel KERNCONF=YOUR_KERNEL_HERE
1948 <reboot in single user> [3]
1955 Make sure that you've read the UPDATING file to understand the
1956 tweaks to various things you need. At this point in the life
1957 cycle of current, things change often and you are on your own
1958 to cope. The defaults can also change, so please read ALL of
1959 the UPDATING entries.
1961 Also, if you are tracking -current, you must be subscribed to
1962 freebsd-current@freebsd.org. Make sure that before you update
1963 your sources that you have read and understood all the recent
1964 messages there. If in doubt, please track -stable which has
1965 much fewer pitfalls.
1967 [1] If you have third party modules, such as vmware, you
1968 should disable them at this point so they don't crash your
1971 [3] From the bootblocks, boot -s, and then do
1976 adjkerntz -i # if CMOS is wall time
1977 Also, when doing a major release upgrade, it is required that
1978 you boot into single user mode to do the installworld.
1980 [4] Note: This step is non-optional. Failure to do this step
1981 can result in a significant reduction in the functionality of the
1982 system. Attempting to do it by hand is not recommended and those
1983 that pursue this avenue should read this file carefully, as well
1984 as the archives of freebsd-current and freebsd-hackers mailing lists
1985 for potential gotchas. The -U option is also useful to consider.
1986 See mergemaster(8) for more information.
1988 [5] Usually this step is a no-op. However, from time to time
1989 you may need to do this if you get unknown user in the following
1990 step. It never hurts to do it all the time. You may need to
1991 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1992 install) after the buildworld before this step if you last updated
1993 from current before 20130425 or from -stable before 20130430.
1995 [6] This only deletes old files and directories. Old libraries
1996 can be deleted by "make delete-old-libs", but you have to make
1997 sure that no program is using those libraries anymore.
1999 [8] The new kernel must be able to run existing binaries used by
2000 an installworld. When upgrading across major versions, the new
2001 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2002 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2003 binaries). Failure to do so may leave you with a system that is
2004 hard to boot to recover. A GENERIC kernel will include suitable
2005 compatibility options to run binaries from older branches.
2007 Make sure that you merge any new devices from GENERIC since the
2008 last time you updated your kernel config file.
2010 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2011 "?=" instead of the "=" assignment operator, so that buildworld can
2012 override the CPUTYPE if it needs to.
2014 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2015 not on the command line, or in /etc/make.conf. buildworld will
2016 warn if it is improperly defined.
2019 This file contains a list, in reverse chronological order, of major
2020 breakages in tracking -current. It is not guaranteed to be a complete
2021 list of such breakages, and only contains entries since September 23, 2011.
2022 If you need to see UPDATING entries from before that date, you will need
2023 to fetch an UPDATING file from an older FreeBSD release.
2025 Copyright information:
2027 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2029 Redistribution, publication, translation and use, with or without
2030 modification, in full or in part, in any form or format of this
2031 document are permitted without further permission from the author.
2033 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2034 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2035 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2036 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2037 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2038 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2039 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2040 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2041 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2042 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2043 POSSIBILITY OF SUCH DAMAGE.
2045 Contact Warner Losh if you have any questions about your use of