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 20200319 p3 FreeBSD-EN-20:03.sshd
20 FreeBSD-EN-20:05.mlx5en
23 FreeBSD-SA-20:05.if_oce_ioctl
24 FreeBSD-SA-20:06.if_ixl_ioctl
25 FreeBSD-SA-20:07.epair
29 Fix misleading log messages upon successful sshd login [EN-20:03.sshd]
31 Fix packet forwarding performance in mlx5en(4) driver [EN-20:05.mlx5en]
33 Fix incorrect checksum calculations with IPv6 extension headers [EN-20:06.ipv6]
35 Fix TCP IPv6 SYN cache kernel information disclosure [SA-20:04.tcp]
37 Fix insufficient oce(4) ioctl(2) privilege checking [SA-20:05.if_oce_ioctl]
39 Fix insufficient ixl(4) ioctl(2) privilege checking [SA-20:06.if_ixl_ioctl]
41 Fix incorrect user-controlled pointer use in epair [SA-20:07.epair]
43 Fix kernel memory disclosure with nested jails [SA-20:08.jail]
45 Fix multiple denial of service in ntpd [SA-20:09.ntp]
47 20200128 p2 FreeBSD-EN-20:01.ssp
48 FreeBSD-SA-20:01.libfetch
49 FreeBSD-SA-20:03.thrmisc
51 Fix imprecise ordering of SSP canary initialization [EN-20:01.ssp]
53 Fix libfetch buffer overflow [SA-20:01.libfetch]
55 Fix kernel stack data disclosure [SA-20:03.thrmisc]
57 20191112 p1 FreeBSD-EN-19:19.loader
58 FreeBSD-SA-19:25.mcepsc
60 Fix UEFI Loader Memory Fragmentation [EN-19:19.loader]
62 Fix Machine Check Exception on Page Size Change [SA-19:25.mcepsc]
68 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
69 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
70 been removed from mount_fusefs(8). You can safely remove them from
71 your scripts, because they had no effect.
73 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
74 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
75 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
76 sysctls have been removed. If you felt the need to set any of them to
77 a non-default value, please tell asomers@FreeBSD.org why.
80 The fuse(4) module has been renamed to fusefs(4) for consistency with
81 other filesystems. You should update any kld_load="fuse" entries in
82 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
83 "options FUSE" enties in kernel config files.
86 Default permissions on the /var/account/acct file (and copies of it
87 rotated by periodic daily scripts) are changed from 0644 to 0640
88 because the file contains sensitive information that should not be
89 world-readable. If the /var/account directory must be created by
90 rc.d/accounting, the mode used is now 0750. Admins who use the
91 accounting feature are encouraged to change the mode of an existing
92 /var/account directory to 0750 or 0700.
95 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
96 been upgraded to 8.0.1. Please see the 20141231 entry below for
97 information about prerequisites and upgrading, if you are not already
98 using clang 3.5.0 or higher.
101 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
102 functionality needed for the RETPOLINE option should work properly
103 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
106 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
107 8.0.0. Please see the 20141231 entry below for information about
108 prerequisites and upgrading, if you are not already using clang 3.5.0
112 The RETPOLINE option produces non-functional ifunc-using binaries
113 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
114 Once Clang 8 is merged it may be enabled again.
117 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
118 7.0.1. Please see the 20141231 entry below for information about
119 prerequisites and upgrading, if you are not already using clang 3.5.0
123 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
124 compiled into your custom kernel, add 'device xz' statement to the
128 Iflib is no longer unconditionally compiled into the kernel. Drivers
129 using iflib and statically compiled into the kernel, now require
130 the 'device iflib' config option. For the same drivers loaded as
131 modules on kernels not having 'device iflib', the iflib.ko module
132 is loaded automatically.
135 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
136 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
137 servers that have vfs.nfsd.nfs_privport set will only allow mounts
138 from clients using a reserved port#. Since both the FreeBSD and Linux
139 NFSv4 clients use reserved port#s by default, this should not affect
143 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
144 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
145 it produces broken binaries when ifuncs are in use. Users needing
146 GNU ld should install the binutils port or package.
149 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
150 has been converted to a port (misc/ctm) and will be removed from
151 FreeBSD-13. A depreciation warning will be printed to stderr by
152 the ctm command, but the functionality will remain in base for all
156 The stable/12 branch has been created in subversion from head
160 Ports for the DRM modules have been simplified. Now, amd64 users should
161 just install the drm-kmod port. All others should install
164 Graphics hardware that's newer than about 2010 usually works with
165 drm-kmod. For hardware older than 2013, however, some users will need
166 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
167 than 2008 usually only works in drm-legacy-kmod. The graphics team can
168 only commit to hardware made since 2013 due to the complexity of the
169 market and difficulty to test all the older cards effectively. If you
170 have hardware supported by drm-kmod, you are strongly encouraged to use
171 that as you will get better support.
173 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
174 elsewhere, the drm and drm2 modules will be eliminated from the src base
175 soon (with a limited exception for arm). Please update to the package asap
176 and report any issues to x11@freebsd.org.
178 Generally, anybody using the drm*-kmod packages should add
179 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
180 cross-threading surprises, especially with automatic driver
181 loading from X11 startup. These will become the defaults in 13-current
185 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
186 custom kernel and module loading configuration files must be updated
187 accordingly. Moreover, interfaces previous presented as ixlvN to the
188 system are now exposed as iavfN and network configuration files must
189 be adjusted as necessary.
192 OpenSSL has been updated to version 1.1.1. This update included
193 additional various API changes througout the base system. It is
194 important to rebuild third-party software after upgrading. The value
195 of __FreeBSD_version has been bumped accordingly.
198 The legacy DRM modules and drivers have now been added to the loader's
199 module blacklist, in favor of loading them with kld_list in rc.conf(5).
200 The module blacklist may be overridden with the loader.conf(5)
201 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
205 The cam(4) based nda(4) driver will be used over nvd(4) by default on
206 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
207 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
208 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
212 Reproducible build mode is now on by default, in preparation for
213 FreeBSD 12.0. This eliminates build metadata such as the user,
214 host, and time from the kernel (and uname), unless the working tree
215 corresponds to a modified checkout from a version control system.
216 The previous behavior can be obtained by setting the /etc/src.conf
217 knob WITHOUT_REPRODUCIBLE_BUILD.
220 The Yarrow CSPRNG has been removed from the kernel as it has not been
221 supported by its designers since at least 2003. Fortuna has been the
222 default since FreeBSD-11.
225 devctl freeze/thaw have gone into the tree, the rc scripts have been
226 updated to use them and devmatch has been changed. You should update
227 kernel, userland and rc scripts all at the same time.
230 The default interpreter has been switched from 4th to Lua.
231 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
232 interpreter. If you have custom FORTH code you will need to set
233 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
234 src.conf for the build. This will create default hard links between
235 loader and loader_4th instead of loader and loader_lua, the new default.
236 If you are using UEFI it will create the proper hard link to loader.efi.
238 bhyve uses userboot.so. It remains 4th-only until some issues are solved
239 regarding coexisting with multiple versions of FreeBSD are resolved.
242 ls(1) now respects the COLORTERM environment variable used in other
243 systems and software to indicate that a colored terminal is both
244 supported and desired. If ls(1) is suddenly emitting colors, they may
245 be disabled again by either removing the unwanted COLORTERM from your
246 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
247 may not be observed in a future release.
250 The default pager for most commands has been changed to "less". To
251 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
255 The jedec_ts(4) driver has been removed. A superset of its functionality
256 is available in the jedec_dimm(4) driver, and the manpage for that
257 driver includes migration instructions. If you have "device jedec_ts"
258 in your kernel configuration file, it must be removed.
261 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
262 This should have no effect if the kernel is booted via BIOS/legacy boot.
263 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
264 has a buggy firmware that prevents a successful boot due to use of
268 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
269 support has been removed from the tree. These ports were
270 obsolete and/or known to be broken for many years.
273 loader.efi has been augmented to participate more fully in the
274 UEFI boot manager protocol. loader.efi will now look at the
275 BootXXXX environment variable to determine if a specific kernel
276 or root partition was specified. XXXX is derived from BootCurrent.
277 efibootmgr(8) manages these standard UEFI variables.
280 zfsloader's functionality has now been folded into loader.
281 zfsloader is no longer necessary once you've updated your
282 boot blocks. For a transition period, we will install a
283 hardlink for zfsloader to loader to allow a smooth transition
284 until the boot blocks can be updated (hard link because old
285 zfs boot blocks don't understand symlinks).
288 ARM64 now have efifb support, if you want to have serial console
289 on your arm64 board when an screen is connected and the bootloader
290 setup a frambuffer for us to use, just add :
294 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
295 an screen connected as the firmware will setup a framebuffer are that
296 u-boot will expose as an EFI framebuffer.
299 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
300 or take steps to update /etc/passwd before doing installworld on
301 existing systems. Do not skip the "mergemaster -Fp" step before
302 installworld, as described in the update procedures near the bottom
303 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
304 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
305 the ntp config file contain options that change file/dir locations.
306 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
307 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
308 taking steps to ensure that all required files/dirs are accessible
312 Big endian arm support has been removed.
315 The static environment setup in kernel configs is no longer mutually
316 exclusive with the loader(8) environment by default. In order to
317 restore the previous default behavior of disabling the loader(8)
318 environment if a static environment is present, you must specify
319 loader_env.disabled=1 in the static environment.
322 The ABI of syscalls used by management tools like sockstat and
323 netstat has been broken to allow 32-bit binaries to work on
324 64-bit kernels without modification. These programs will need
325 to match the kernel in order to function. External programs may
326 require minor modifications to accommodate a change of type in
327 structures from pointers to 64-bit virtual addresses.
330 On i386 and amd64 atomics are now inlined. Out of tree modules using
331 atomics will need to be rebuilt.
334 The '%I' format in the kern.corefile sysctl limits the number of
335 core files that a process can generate to the number stored in the
336 debug.ncores sysctl. The '%I' format is replaced by the single digit
337 index. Previously, if all indexes were taken the kernel would overwrite
338 only a core file with the highest index in a filename.
339 Currently the system will create a new core file if there is a free
340 index or if all slots are taken it will overwrite the oldest one.
343 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
344 6.0.1. Please see the 20141231 entry below for information about
345 prerequisites and upgrading, if you are not already using clang 3.5.0
349 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
350 needed to be changed to work with it. This change was made with r335763
351 and requires a mergemaster / etcupdate / etc to update the installed file.
354 r334930 changed the interface between the NFS modules, so they all
355 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
358 As of r334391 lld is the default amd64 system linker; it is installed
359 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
363 The kernel / userland interface for devinfo changed, so you'll
364 need a new kernel and userland as a pair for it to work (rebuilding
365 lib/libdevinfo is all that's required). devinfo and devmatch will
366 not work, but everything else will when there's a mismatch.
369 The on-disk format for hwpmc callchain records has changed to include
370 threadid corresponding to a given record. This changes the field offsets
371 and thus requires that libpmcstat be rebuilt before using a kernel
375 The vxge(4) driver has been removed. This driver was introduced into
376 HEAD one week before the Exar left the Ethernet market and is not
377 known to be used. If you have device vxge in your kernel config file
381 The amd64 kernel now requires a ld that supports ifunc to produce a
382 working kernel, either lld or a newer binutils. lld is built by default
383 on amd64, and the 'buildkernel' target uses it automatically. However,
384 it is not the default linker, so building the kernel the traditional
385 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
386 binutils port/package). lld will soon be default, and this requirement
389 NOTE: As of r334391 lld is the default system linker on amd64, and no
390 workaround is necessary.
393 The nxge(4) driver has been removed. This driver was for PCI-X 10g
394 cards made by s2io/Neterion. The company was aquired by Exar and
395 no longer sells or supports Ethernet products. If you have device
396 nxge in your kernel config file it must be removed.
399 The tz database (tzdb) has been updated to 2018e. This version more
400 correctly models time stamps in time zones with negative DST such as
401 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
402 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
403 time zone abbreviations and the tm_isdst flag.
406 The ixgb(4) driver has been removed. This driver was for an early and
407 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
408 quickly shifted to the long lived ixgbe family. If you have device
409 ixgb in your kernel config file it must be removed.
412 The lmc(4) driver has been removed. This was a WAN interface
413 card that was already reportedly rare in 2003, and had an ambiguous
414 license. If you have device lmc in your kernel config file it must
418 Support for Arcnet networks has been removed. If you have device
419 arcnet or device cm in your kernel config file they must be
423 Support for FDDI networks has been removed. If you have device
424 fddi or device fpa in your kernel config file they must be
428 In addition to supporting RFC 3164 formatted messages, the
429 syslogd(8) service is now capable of parsing RFC 5424 formatted
430 log messages. The main benefit of using RFC 5424 is that clients
431 may now send log messages with timestamps containing year numbers,
432 microseconds and time zone offsets.
434 Similarly, the syslog(3) C library function has been altered to
435 send RFC 5424 formatted messages to the local system logging
436 daemon. On systems using syslogd(8), this change should have no
437 negative impact, as long as syslogd(8) and the C library are
438 updated at the same time. On systems using a different system
439 logging daemon, it may be necessary to make configuration
440 adjustments, depending on the software used.
442 When using syslog-ng, add the 'syslog-protocol' flag to local
443 input sources to enable parsing of RFC 5424 formatted messages:
446 unix-dgram("/var/run/log" flags(syslog-protocol));
449 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
450 of the 'imuxsock' module to let messages be processed by the
451 regular RFC 3164/5424 parsing pipeline:
453 module(load="imuxsock" SysSock.UseSpecialParser="off")
455 Do note that these changes only affect communication between local
456 applications and syslogd(8). The format that syslogd(8) uses to
457 store messages on disk or forward messages to other systems
458 remains unchanged. syslogd(8) still uses RFC 3164 for these
459 purposes. Options to customize this behaviour will be added in the
460 future. Utilities that process log files stored in /var/log are
461 thus expected to continue to function as before.
463 __FreeBSD_version has been incremented to 1200061 to denote this
467 Support for token ring networks has been removed. If you
468 have "device token" in your kernel config you should remove
469 it. No device drivers supported token ring.
472 makefs was modified to be able to tag ISO9660 El Torito boot catalog
473 entries as EFI instead of overloading the i386 tag as done previously.
474 The amd64 mkisoimages.sh script used to build amd64 ISO images for
475 release was updated to use this. This may mean that makefs must be
476 updated before "make cdrom" can be run in the release directory. This
477 should be as simple as:
479 $ cd $SRCDIR/usr.sbin/makefs
480 $ make depend all install
483 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
484 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
485 Co-existance for the transition period will come shortly. Booting is a
486 complex environment and test coverage for Lua-enabled loaders has been
487 thin, so it would be prudent to assume it might not work and make
488 provisions for backup boot methods.
491 devmatch functionality has been turned on in devd. It will automatically
492 load drivers for unattached devices. This may cause unexpected drivers to
493 be loaded. Please report any problems to current@ and imp@freebsd.org.
496 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
497 6.0.0. Please see the 20141231 entry below for information about
498 prerequisites and upgrading, if you are not already using clang 3.5.0
502 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
503 This means it is used to link the kernel and userland libraries and
504 executables, but is not yet installed as /usr/bin/ld by default.
506 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
507 WITHOUT_LLD_BOOTSTRAP=yes
510 On i386, pmtimer has been removed. Its functionality has been folded
511 into apm. It was a no-op on ACPI in current for a while now (but was still
512 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
513 from kernel config files.
516 The use of RSS hash from the network card aka flowid has been
517 disabled by default for lagg(4) as it's currently incompatible with
518 the lacp and loadbalance protocols.
520 This can be re-enabled by setting the following in loader.conf:
521 net.link.lagg.default_use_flowid="1"
524 The SW_WATCHDOG option is no longer necessary to enable the
525 hardclock-based software watchdog if no hardware watchdog is
526 configured. As before, SW_WATCHDOG will cause the software
527 watchdog to be enabled even if a hardware watchdog is configured.
530 r326887 fixes the issue described in the 20171214 UPDATING entry.
531 r326888 flips the switch back to building GELI support always.
534 r362593 broke ZFS + GELI support for reasons unknown. However,
535 it also broke ZFS support generally, so GELI has been turned off
536 by default as the lesser evil in r326857. If you boot off ZFS and/or
537 GELI, it might not be a good time to update.
540 PowerPC users must update loader(8) by rebuilding world before
541 installing a new kernel, as the protocol connecting them has
542 changed. Without the update, loader metadata will not be passed
543 successfully to the kernel and users will have to enter their
544 root partition at the kernel mountroot prompt to continue booting.
545 Newer versions of loader can boot old kernels without issue.
548 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
549 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
550 to WITH/OUT_LOADER_GELI.
553 The naive and non-compliant support of posix_fallocate(2) in ZFS
554 has been removed as of r325320. The system call now returns EINVAL
555 when used on a ZFS file. Although the new behavior complies with the
556 standard, some consumers are not prepared to cope with it.
557 One known victim is lld prior to r325420.
560 Building in a FreeBSD src checkout will automatically create object
561 directories now rather than store files in the current directory if
562 'make obj' was not ran. Calling 'make obj' is no longer necessary.
563 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
564 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
568 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
569 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
570 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
571 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
572 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
573 The UNIFIED_OBJDIR option is a transitional feature that will be
574 removed for 12.0 release; please migrate to the new format for any
575 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
576 than hardcoding paths.
579 The native-xtools target no longer installs the files by default to the
580 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
581 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
584 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
585 options are changing from controlling the build if defined / undefined
586 to controlling the build with explicit 'yes' or 'no' values. They will
587 shift to WITH/WITHOUT options to match other options in the system.
590 libstand has turned into a private library for sys/boot use only.
591 It is no longer supported as a public interface outside of sys/boot.
594 The arm port has split armv6 into armv6 and armv7. armv7 is now
595 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
596 and are running a kernel from before r324363, you will need to add
597 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
600 When building multiple kernels using KERNCONF, non-existent KERNCONF
601 files will produce an error and buildkernel will fail. Previously
602 missing KERNCONF files silently failed giving no indication as to
603 why, only to subsequently discover during installkernel that the
604 desired kernel was never built in the first place.
607 The default serial number format for CTL LUNs has changed. This will
608 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
609 or iSCSI clients care about their LUNs' serial numbers. Users who
610 require serial number stability should hardcode serial numbers in
614 For 32-bit arm compiled for hard-float support, soft-floating point
615 binaries now always get their shared libraries from
616 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
617 /usr/libsoft also existed). Only users with a hard-float ld.so, but
618 soft-float everything else should be affected.
621 The geli password typed at boot is now hidden. To restore the previous
622 behavior, see geli(8) for configuration options.
625 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
626 sysctl values. Minor nit, but requires a rebuild of both world/kernel
630 "make check" behavior (made in ^/head@r295380) has been changed to
631 execute from a limited sandbox, as opposed to executing from
635 - The "beforecheck" and "aftercheck" targets are now specified.
636 - ${CHECKDIR} (added in commit noted above) has been removed.
637 - Legacy behavior can be enabled by setting
638 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
640 If the limited sandbox mode is enabled, "make check" will execute
641 "make distribution", then install, execute the tests, and clean up the
642 sandbox if successful.
644 The "make distribution" and "make install" targets are typically run as
645 root to set appropriate permissions and ownership at installation time.
646 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
647 environment if executing "make check" with limited sandbox mode using
648 an unprivileged user.
651 Since the switch to GPT disk labels, fsck for UFS/FFS has been
652 unable to automatically find alternate superblocks. As of r322297,
653 the information needed to find alternate superblocks has been
654 moved to the end of the area reserved for the boot block.
655 Filesystems created with a newfs of this vintage or later
656 will create the recovery information. If you have a filesystem
657 created prior to this change and wish to have a recovery block
658 created for your filesystem, you can do so by running fsck in
659 foreground mode (i.e., do not use the -p or -y options). As it
660 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
661 to which you should answer yes.
664 As of r321665, an NFSv4 server configuration that services
665 Kerberos mounts or clients that do not support the uid/gid in
666 owner/owner_group string capability, must explicitly enable
667 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
668 machine's /etc/rc.conf file.
671 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
672 Please see the 20141231 entry below for information about prerequisites
673 and upgrading, if you are not already using clang 3.5.0 or higher.
676 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
677 r-commands (rlogin, rsh, etc.) to be built with the base system.
680 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
681 a very major ABI incompatible change, so users of FreeBSD/powerpc must
682 be careful when performing source upgrades. It is best to run
683 'make installworld' from an alternate root system, either a live
684 CD/memory stick, or a temporary root partition. Additionally, all ports
685 must be recompiled. powerpc64 is largely unaffected, except in the case
686 of 32-bit compatibility. All 32-bit binaries will be affected.
689 Forward compatibility for the "ino64" project have been committed. This
690 will allow most new binaries to run on older kernels in a limited
691 fashion. This prevents many of the common foot-shooting actions in the
692 upgrade as well as the limited ability to roll back the kernel across
693 the ino64 upgrade. Complicated use cases may not work properly, though
694 enough simpler ones work to allow recovery in most situations.
697 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
698 if you require the GPL compiler.
701 The internal ABI used for communication between the NFS kernel modules
702 was changed by r320085, so __FreeBSD_version was bumped to
703 ensure all the NFS related modules are updated together.
706 The ABI of struct event was changed by extending the data
707 member to 64bit and adding ext fields. For upgrade, same
708 precautions as for the entry 20170523 "ino64" must be
712 The GNU roff toolchain has been removed from base. To render manpages
713 which are not supported by mandoc(1), man(1) can fallback on GNU roff
714 from ports (and recommends to install it).
715 To render roff(7) documents, consider using GNU roff from ports or the
716 heirloom doctools roff toolchain from ports via pkg install groff or
717 via pkg install heirloom-doctools.
720 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
721 smaller runtime footprint builds. This is useful for embedded systems
722 which only require one chipset support.
724 If you load it as a module, make sure this is in /boot/loader.conf:
728 This will load the HAL, all chip/RF backends and if_ath_pci.
729 If you have if_ath_pci in /boot/loader.conf, ensure it is after
730 if_ath or it will not load any HAL chipset support.
732 If you want to selectively load things (eg on ye cheape ARM/MIPS
733 platforms where RAM is at a premium) you should:
736 * load the chip modules in question
737 * load ath_rate, ath_dfs
739 * load if_ath_pci and/or if_ath_ahb depending upon your particular
740 bus bind type - this is where probe/attach is done.
742 For further comments/feedback, poke adrian@ .
745 The "ino64" 64-bit inode project has been committed, which extends
746 a number of types to 64 bits. Upgrading in place requires care and
747 adherence to the documented upgrade procedure.
749 If using a custom kernel configuration ensure that the
750 COMPAT_FREEBSD11 option is included (as during the upgrade the
751 system will be running the ino64 kernel with the existing world).
753 For the safest in-place upgrade begin by removing previous build
754 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
755 full procedure documented below under the heading "To rebuild
756 everything and install it on the current system." Specifically,
757 a reboot is required after installing the new kernel before
761 The NATM framework including the en(4), fatm(4), hatm(4), and
762 patm(4) devices has been removed. Consumers should plan a
763 migration before the end-of-life date for FreeBSD 11.
766 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
767 diff has not been implemented, if those are needed a newer version of
768 GNU diff is available via the diffutils package under the gdiff name.
771 As of r316810 for ipfilter, keep frags is no longer assumed when
772 keep state is specified in a rule. r316810 aligns ipfilter with
773 documentation in man pages separating keep frags from keep state.
774 This allows keep state to be specified without forcing keep frags
775 and allows keep frags to be specified independently of keep state.
776 To maintain previous behaviour, also specify keep frags with
777 keep state (as documented in ipf.conf.5).
780 arm64 builds now use the base system LLD 4.0.0 linker by default,
781 instead of requiring that the aarch64-binutils port or package be
782 installed. To continue using aarch64-binutils, set
783 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
786 The UDP optimization in entry 20160818 that added the sysctl
787 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
788 packets will no longer be treated as L3 broadcast packets.
791 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
792 use any explicitly assigned loopback address available in the jail
793 instead of using the first assigned address of the jail.
796 The ctl.ko module no longer implements the iSCSI target frontend:
797 cfiscsi.ko does instead.
799 If building cfiscsi.ko as a kernel module, the module can be loaded
800 via one of the following methods:
801 - `cfiscsi_load="YES"` in loader.conf(5).
802 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
803 - ctladm(8)/ctld(8), when compiled with iSCSI support
804 (`WITH_ISCSI=yes` in src.conf(5))
806 Please see cfiscsi(4) for more details.
809 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
810 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
811 same source (previously, the dependency of mmcsd.ko on mmc.ko was
812 missing, but mmcsd.ko now will refuse to load if it is incompatible
816 The syntax of ipfw(8) named states was changed to avoid ambiguity.
817 If you have used named states in the firewall rules, you need to modify
818 them after installworld and before rebooting. Now named states must
819 be prefixed with colon.
822 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
823 removed as the userland we provide cannot use them. The KMS version
824 (sys/dev/drm2) supports the same hardware.
827 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
828 Please see the 20141231 entry below for information about prerequisites
829 and upgrading, if you are not already using clang 3.5.0 or higher.
832 The code that provides support for ZFS .zfs/ directory functionality
833 has been reimplemented. It's not possible now to create a snapshot
834 by mkdir under .zfs/snapshot/. That should be the only user visible
838 EISA bus support has been removed. The WITH_EISA option is no longer
842 MCA bus support has been removed.
845 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
846 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
849 The EM_MULTIQUEUE kernel configuration option is deprecated now that
850 the em(4) driver conforms to iflib specifications.
853 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
854 IFLIB. If you have a custom kernel configuration that excludes em(4)
855 but you use igb(4), you need to re-add em(4) to your custom configuration.
858 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
859 Please see the 20141231 entry below for information about prerequisites
860 and upgrading, if you are not already using clang 3.5.0 or higher.
863 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
864 Please see the 20141231 entry below for information about prerequisites
865 and upgrading, if you are not already using clang 3.5.0 or higher.
868 The layout of the pmap structure has changed for powerpc to put the pmap
869 statistics at the front for all CPU variations. libkvm(3) and all tools
870 that link against it need to be recompiled.
873 isl(4) and cyapa(4) drivers now require a new driver,
874 chromebook_platform(4), to work properly on Chromebook-class hardware.
875 On other types of hardware the drivers may need to be configured using
876 device hints. Please see the corresponding manual pages for details.
879 The urtwn(4) driver was merged into rtwn(4) and now consists of
880 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
882 Also, firmware for RTL8188CE was renamed due to possible name
883 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
886 GNU rcs has been removed from base. It is available as packages:
887 - rcs: Latest GPLv3 GNU rcs version.
888 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
892 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
893 modules now requires that the kernel configuration contain the
894 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
897 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
898 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
901 Relocatable object files with the extension of .So have been renamed
902 to use an extension of .pico instead. The purpose of this change is
903 to avoid a name clash with shared libraries on case-insensitive file
904 systems. On those file systems, foo.So is the same file as foo.so.
907 GNU rcs has been turned off by default. It can (temporarily) be built
908 again by adding WITH_RCS knob in src.conf.
909 Otherwise, GNU rcs is available from packages:
910 - rcs: Latest GPLv3 GNU rcs version.
911 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
914 The backup_uses_rcs functionality has been removed from rc.subr.
917 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
918 two separate components, QUEUE_MACRO_DEBUG_TRACE and
919 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
920 QUEUE_MACRO_DEBUG behavior.
923 r304787 changed some ioctl interfaces between the iSCSI userspace
924 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
925 rebuilt to work with new kernels. __FreeBSD_version has been bumped
929 The UDP receive code has been updated to only treat incoming UDP
930 packets that were addressed to an L2 broadcast address as L3
931 broadcast packets. It is not expected that this will affect any
932 standards-conforming UDP application. The new behaviour can be
933 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
937 Remove the openbsd_poll system call.
938 __FreeBSD_version has been bumped because of this.
941 The stable/11 branch has been created from head@r302406.
944 The libc stub for the pipe(2) system call has been replaced with
945 a wrapper that calls the pipe2(2) system call and the pipe(2)
946 system call is now only implemented by the kernels that include
947 "options COMPAT_FREEBSD10" in their config file (this is the
948 default). Users should ensure that this option is enabled in
949 their kernel or upgrade userspace to r302092 before upgrading their
953 CAM will now strip leading spaces from SCSI disks' serial numbers.
954 This will affect users who create UFS filesystems on SCSI disks using
955 those disk's diskid device nodes. For example, if /etc/fstab
956 previously contained a line like
957 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
958 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
959 transforms like gmirror may also be affected. ZFS users should
963 The bitstring(3) API has been updated with new functionality and
964 improved performance. But it is binary-incompatible with the old API.
965 Objects built with the new headers may not be linked against objects
966 built with the old headers.
969 The brk and sbrk functions have been removed from libc on arm64.
970 Binutils from ports has been updated to not link to these
971 functions and should be updated to the latest version before
972 installing a new libc.
975 The armv6 port now defaults to hard float ABI. Limited support
976 for running both hardfloat and soft float on the same system
977 is available using the libraries installed with -DWITH_LIBSOFT.
978 This has only been tested as an upgrade path for installworld
979 and packages may fail or need manual intervention to run. New
980 packages will be needed.
982 To update an existing self-hosted armv6hf system, you must add
983 TARGET_ARCH=armv6 on the make command line for both the build
984 and the install steps.
987 Kernel modules compiled outside of a kernel build now default to
988 installing to /boot/modules instead of /boot/kernel. Many kernel
989 modules built this way (such as those in ports) already overrode
990 KMODDIR explicitly to install into /boot/modules. However,
991 manually building and installing a module from /sys/modules will
992 now install to /boot/modules instead of /boot/kernel.
995 The CAM I/O scheduler has been committed to the kernel. There should be
996 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
997 list of known rogues that claim support for this but actually corrupt
998 data is believed to be complete, be on the lookout for data
999 corruption. The known rogue list is believed to be complete:
1001 o Crucial MX100, M550 drives with MU01 firmware.
1002 o Micron M510 and M550 drives with MU01 firmware.
1003 o Micron M500 prior to MU07 firmware
1004 o Samsung 830, 840, and 850 all firmwares
1005 o FCCT M500 all firmwares
1007 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1008 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1009 updated firmware. Black listed drives will work correctly because these
1010 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1011 this list is the same as found in Linux, it's believed there are no
1012 other rogues in the market place. All other models from the above
1015 To be safe, if you are at all concerned, you can quirk each of your
1016 drives to prevent NCQ from being sent by setting:
1017 kern.cam.ada.X.quirks="0x2"
1018 in loader.conf. If the drive requires the 4k sector quirk, set the
1019 quirks entry to 0x3.
1022 The FAST_DEPEND build option has been removed and its functionality is
1023 now the one true way. The old mkdep(1) style of 'make depend' has
1024 been removed. See 20160311 for further details.
1027 Resource range types have grown from unsigned long to uintmax_t. All
1028 drivers, and anything using libdevinfo, need to be recompiled.
1031 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1032 builds. It no longer runs mkdep(1) during 'make depend', and the
1033 'make depend' stage can safely be skipped now as it is auto ran
1034 when building 'make all' and will generate all SRCS and DPSRCS before
1035 building anything else. Dependencies are gathered at compile time with
1036 -MF flags kept in separate .depend files per object file. Users should
1037 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1038 stale .depend files.
1041 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1042 kernel modules. Therefore, if you load any kernel modules at boot time,
1043 please install the boot loaders after you install the kernel, but before
1047 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1048 make installkernel KERNCONF=YOUR_KERNEL_HERE
1049 make -C sys/boot install
1050 <reboot in single user>
1052 Then follow the usual steps, described in the General Notes section,
1056 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1057 see the 20141231 entry below for information about prerequisites and
1058 upgrading, if you are not already using clang 3.5.0 or higher.
1061 The AIO subsystem is now a standard part of the kernel. The
1062 VFS_AIO kernel option and aio.ko kernel module have been removed.
1063 Due to stability concerns, asynchronous I/O requests are only
1064 permitted on sockets and raw disks by default. To enable
1065 asynchronous I/O requests on all file types, set the
1066 vfs.aio.enable_unsafe sysctl to a non-zero value.
1069 The ELF object manipulation tool objcopy is now provided by the
1070 ELF Tool Chain project rather than by GNU binutils. It should be a
1071 drop-in replacement, with the addition of arm64 support. The
1072 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1073 to obtain the GNU version if necessary.
1076 Building ZFS pools on top of zvols is prohibited by default. That
1077 feature has never worked safely; it's always been prone to deadlocks.
1078 Using a zvol as the backing store for a VM guest's virtual disk will
1079 still work, even if the guest is using ZFS. Legacy behavior can be
1080 restored by setting vfs.zfs.vol.recursive=1.
1083 The NONE and HPN patches has been removed from OpenSSH. They are
1084 still available in the security/openssh-portable port.
1087 With the addition of ypldap(8), a new _ypldap user is now required
1088 during installworld. "mergemaster -p" can be used to add the user
1089 prior to installworld, as documented in the handbook.
1092 The tftp loader (pxeboot) now uses the option root-path directive. As a
1093 consequence it no longer looks for a pxeboot.4th file on the tftp
1094 server. Instead it uses the regular /boot infrastructure as with the
1098 The code to start recording plug and play data into the modules has
1099 been committed. While the old tools will properly build a new kernel,
1100 a number of warnings about "unknown metadata record 4" will be produced
1101 for an older kldxref. To avoid such warnings, make sure to rebuild
1102 the kernel toolchain (or world). Make sure that you have r292078 or
1103 later when trying to build 292077 or later before rebuilding.
1106 Debug data files are now built by default with 'make buildworld' and
1107 installed with 'make installworld'. This facilitates debugging but
1108 requires more disk space both during the build and for the installed
1109 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1113 r291527 changed the internal interface between the nfsd.ko and
1114 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1115 __FreeBSD_version has been bumped because of this.
1118 Add support for unicode collation strings leads to a change of
1119 order of files listed by ls(1) for example. To get back to the old
1120 behaviour, set LC_COLLATE environment variable to "C".
1122 Databases administrators will need to reindex their databases given
1123 collation results will be different.
1125 Due to a bug in install(1) it is recommended to remove the ancient
1126 locales before running make installworld.
1128 rm -rf /usr/share/locale/*
1131 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1132 libcrypto.so.7 or libssl.so.7 must be recompiled.
1135 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1136 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1137 should be replaced with isp_2400 and isp_2500 modules respectively.
1140 The build previously allowed using 'make -n' to not recurse into
1141 sub-directories while showing what commands would be executed, and
1142 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1143 and 'make -N' will not.
1146 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1147 and etcupdate will now use this file. A custom sendmail.cf is now
1148 updated via this mechanism rather than via installworld. If you had
1149 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1150 want to remove the exclusion or change it to "always install".
1151 /etc/mail/sendmail.cf is now managed the same way regardless of
1152 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1153 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1156 Compatibility shims for legacy ATA device names have been removed.
1157 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1158 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1159 environment variables, /dev/ad* and /dev/ar* symbolic links.
1162 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1163 Please see the 20141231 entry below for information about prerequisites
1164 and upgrading, if you are not already using clang 3.5.0 or higher.
1167 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1168 and renamed from .symbols to .debug. This reduces the size requirements
1169 on the boot partition or file system and provides consistency with
1170 userland debug files.
1172 When using the supported kernel installation method the
1173 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1174 as is done with /boot/kernel.
1176 Developers wishing to maintain the historical behavior of installing
1177 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1180 The wireless drivers had undergone changes that remove the 'parent
1181 interface' from the ifconfig -l output. The rc.d network scripts
1182 used to check presence of a parent interface in the list, so old
1183 scripts would fail to start wireless networking. Thus, etcupdate(3)
1184 or mergemaster(8) run is required after kernel update, to update your
1185 rc.d scripts in /etc.
1188 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1189 These configurations are now automatically interpreted as
1190 'scrub fragment reassemble'.
1193 Kernel-loadable modules for the random(4) device are back. To use
1194 them, the kernel must have
1197 options RANDOM_LOADABLE
1199 kldload(8) can then be used to load random_fortuna.ko
1200 or random_yarrow.ko. Please note that due to the indirect
1201 function calls that the loadable modules need to provide,
1202 the build-in variants will be slightly more efficient.
1204 The random(4) kernel option RANDOM_DUMMY has been retired due to
1205 unpopularity. It was not all that useful anyway.
1208 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1209 Control over building the ELF Tool Chain tools is now provided by
1210 the WITHOUT_TOOLCHAIN knob.
1213 The polarity of Pulse Per Second (PPS) capture events with the
1214 uart(4) driver has been corrected. Prior to this change the PPS
1215 "assert" event corresponded to the trailing edge of a positive PPS
1216 pulse and the "clear" event was the leading edge of the next pulse.
1218 As the width of a PPS pulse in a typical GPS receiver is on the
1219 order of 1 millisecond, most users will not notice any significant
1220 difference with this change.
1222 Anyone who has compensated for the historical polarity reversal by
1223 configuring a negative offset equal to the pulse width will need to
1224 remove that workaround.
1227 The default group assigned to /dev/dri entries has been changed
1228 from 'wheel' to 'video' with the id of '44'. If you want to have
1229 access to the dri devices please add yourself to the video group
1232 # pw groupmod video -m $USER
1235 The menu.rc and loader.rc files will now be replaced during
1236 upgrades. Please migrate local changes to menu.rc.local and
1237 loader.rc.local instead.
1240 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1241 strings and strip have been removed. The src.conf(5) knob
1242 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1245 As ZFS requires more kernel stack pages than is the default on some
1246 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1247 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1249 Please consider using 'options KSTACK_PAGES=X' where X is greater
1250 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1253 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1254 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1255 default, i.e., they will not contain "::". For example, instead
1256 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1257 to have a more specific match, such as different map entries for
1258 IPv6:0:0 vs IPv6:0. This change requires that configuration
1259 data (including maps, files, classes, custom ruleset, etc.) must
1260 use the same format, so make certain such configuration data is
1261 upgrading. As a very simple check search for patterns like
1262 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1263 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1264 the cf option UseCompressedIPv6Addresses.
1267 The default kernel entropy-processing algorithm is now
1268 Fortuna, replacing Yarrow.
1270 Assuming you have 'device random' in your kernel config
1271 file, the configurations allow a kernel option to override
1272 this default. You may choose *ONE* of:
1274 options RANDOM_YARROW # Legacy /dev/random algorithm.
1275 options RANDOM_DUMMY # Blocking-only driver.
1277 If you have neither, you get Fortuna. For most people,
1278 read no further, Fortuna will give a /dev/random that works
1279 like it always used to, and the difference will be irrelevant.
1281 If you remove 'device random', you get *NO* kernel-processed
1282 entropy at all. This may be acceptable to folks building
1283 embedded systems, but has complications. Carry on reading,
1284 and it is assumed you know what you need.
1286 *PLEASE* read random(4) and random(9) if you are in the
1287 habit of tweaking kernel configs, and/or if you are a member
1288 of the embedded community, wanting specific and not-usual
1289 behaviour from your security subsystems.
1291 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1292 random', you will NOT have a functioning /dev/random, and
1293 many cryptographic features will not work, including SSH.
1294 You may also find strange behaviour from the random(3) set
1295 of library functions, in particular sranddev(3), srandomdev(3)
1296 and arc4random(3). The reason for this is that the KERN_ARND
1297 sysctl only returns entropy if it thinks it has some to
1298 share, and with RANDOM_DUMMY or no 'device random' this
1302 An additional fix for the issue described in the 20150614 sendmail
1303 entry below has been committed in revision 284717.
1306 FreeBSD's old make (fmake) has been removed from the system. It is
1307 available as the devel/fmake port or via pkg install fmake.
1310 The fix for the issue described in the 20150614 sendmail entry
1311 below has been committed in revision 284436. The work
1312 around described in that entry is no longer needed unless the
1313 default setting is overridden by a confDH_PARAMETERS configuration
1314 setting of '5' or pointing to a 512 bit DH parameter file.
1317 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1318 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1319 and devel/kyua to version 0.20+ and adjust any calling code to work
1320 with Kyuafile and kyua.
1323 The import of openssl to address the FreeBSD-SA-15:10.openssl
1324 security advisory includes a change which rejects handshakes
1325 with DH parameters below 768 bits. sendmail releases prior
1326 to 8.15.2 (not yet released), defaulted to a 512 bit
1327 DH parameter setting for client connections. To work around
1328 this interoperability, sendmail can be configured to use a
1329 2048 bit DH parameter by:
1331 1. Edit /etc/mail/`hostname`.mc
1332 2. If a setting for confDH_PARAMETERS does not exist or
1333 exists and is set to a string beginning with '5',
1334 replace it with '2'.
1335 3. If a setting for confDH_PARAMETERS exists and is set to
1336 a file path, create a new file with:
1337 openssl dhparam -out /path/to/file 2048
1338 4. Rebuild the .cf file:
1339 cd /etc/mail/; make; make install
1340 5. Restart sendmail:
1341 cd /etc/mail/; make restart
1343 A sendmail patch is coming, at which time this file will be
1347 Generation of legacy formatted entries have been disabled by default
1348 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1349 entries were converted to use the new format by default when the new,
1350 machine independent format have been added and supported since FreeBSD
1353 Please see the pwd_mkdb(8) manual page for further details.
1356 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1357 20141231 entry below for information about prerequisites and upgrading,
1358 if you are not already using 3.5.0 or higher.
1361 TI platform code switched to using vendor DTS files and this update
1362 may break existing systems running on Beaglebone, Beaglebone Black,
1365 - dtb files should be regenerated/reinstalled. Filenames are the
1366 same but content is different now
1367 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1368 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1369 addressing scheme is now pin 25 on /dev/gpioc3.
1370 - Pandaboard: /etc/ttys should be updated, serial console device is
1371 now /dev/ttyu2, not /dev/ttyu0
1374 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1375 If you need the GNU extension from groff soelim(1), install groff
1376 from package: pkg install groff, or via ports: textproc/groff.
1379 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1380 defined in symlink(7); previously symlinks were silently ignored.
1383 The const qualifier has been removed from iconv(3) to comply with
1384 POSIX. The ports tree is aware of this from r384038 onwards.
1387 Libraries specified by LIBADD in Makefiles must have a corresponding
1388 DPADD_<lib> variable to ensure correct dependencies. This is now
1389 enforced in src.libnames.mk.
1392 From legacy ata(4) driver was removed support for SATA controllers
1393 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1394 Kernel modules ataahci and ataadaptec were removed completely,
1395 replaced by ahci and mvs modules respectively.
1398 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1399 the 20141231 entry below for information about prerequisites and
1400 upgrading, if you are not already using 3.5.0 or higher.
1403 The 32-bit PowerPC kernel has been changed to a position-independent
1404 executable. This can only be booted with a version of loader(8)
1405 newer than January 31, 2015, so make sure to update both world and
1406 kernel before rebooting.
1409 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1410 but before r278950, the RNG was not seeded properly. Immediately
1411 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1412 ssh keys or openssl keys) that were generated w/ a kernel from that
1413 range. This does not affect programs that directly used /dev/random
1414 or /dev/urandom. All userland uses of arc4random(3) are affected.
1417 The autofs(4) ABI was changed in order to restore binary compatibility
1418 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1419 with the new kernel.
1422 The powerpc64 kernel has been changed to a position-independent
1423 executable. This can only be booted with a new version of loader(8),
1424 so make sure to update both world and kernel before rebooting.
1427 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1428 only release, no new features have been added. Please see the 20141231
1429 entry below for information about prerequisites and upgrading, if you
1430 are not already using 3.5.0.
1433 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1434 taken from the ELF Tool Chain project rather than GNU binutils. They
1435 should be drop-in replacements, with the addition of arm64 support.
1436 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1437 binutils tools, if necessary. See 20150805 for updated information.
1440 The default Unbound configuration now enables remote control
1441 using a local socket. Users who have already enabled the
1442 local_unbound service should regenerate their configuration
1443 by running "service local_unbound setup" as root.
1446 The GNU texinfo and GNU info pages have been removed.
1447 To be able to view GNU info pages please install texinfo from ports.
1450 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1452 As of this release, a prerequisite for building clang, llvm and lldb is
1453 a C++11 capable compiler and C++11 standard library. This means that to
1454 be able to successfully build the cross-tools stage of buildworld, with
1455 clang as the bootstrap compiler, your system compiler or cross compiler
1456 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1457 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1460 On any standard FreeBSD 10.x or 11.x installation, where clang and
1461 libc++ are on by default (that is, on x86 or arm), this should work out
1464 On 9.x installations where clang is enabled by default, e.g. on x86 and
1465 powerpc, libc++ will not be enabled by default, so libc++ should be
1466 built (with clang) and installed first. If both clang and libc++ are
1467 missing, build clang first, then use it to build libc++.
1469 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1470 the instructions for 9.x above.
1472 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1473 default, and do not build clang.
1475 Many embedded systems are resource constrained, and will not be able to
1476 build clang in a reasonable time, or in some cases at all. In those
1477 cases, cross building bootable systems on amd64 is a workaround.
1479 This new version of clang introduces a number of new warnings, of which
1480 the following are most likely to appear:
1484 This warns in two cases, for both C and C++:
1485 * When the code is trying to take the absolute value of an unsigned
1486 quantity, which is effectively a no-op, and almost never what was
1487 intended. The code should be fixed, if at all possible. If you are
1488 sure that the unsigned quantity can be safely cast to signed, without
1489 loss of information or undefined behavior, you can add an explicit
1490 cast, or disable the warning.
1492 * When the code is trying to take an absolute value, but the called
1493 abs() variant is for the wrong type, which can lead to truncation.
1494 If you want to disable the warning instead of fixing the code, please
1495 make sure that truncation will not occur, or it might lead to unwanted
1498 -Wtautological-undefined-compare and
1499 -Wundefined-bool-conversion
1501 These warn when C++ code is trying to compare 'this' against NULL, while
1502 'this' should never be NULL in well-defined C++ code. However, there is
1503 some legacy (pre C++11) code out there, which actively abuses this
1504 feature, which was less strictly defined in previous C++ versions.
1506 Squid and openjdk do this, for example. The warning can be turned off
1507 for C++98 and earlier, but compiling the code in C++11 mode might result
1508 in unexpected behavior; for example, the parts of the program that are
1509 unreachable could be optimized away.
1512 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1513 kernel sources have been removed. The .h files remain, since some
1514 utilities include them. This will need to be fixed later.
1515 If "mount -t oldnfs ..." is attempted, it will fail.
1516 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1517 the utilities will report errors.
1520 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1521 directories to top level SUBDIR variable when their parent
1522 directory is included in LOCAL_DIRS. Users with build systems with
1523 such hierarchies and without SUBDIR entries in the parent
1524 directory Makefiles should add them or add the directories to
1528 faith(4) and faithd(8) have been removed from the base system. Faith
1529 has been obsolete for a very long time.
1532 vt(4), the new console driver, is enabled by default. It brings
1533 support for Unicode and double-width characters, as well as
1534 support for UEFI and integration with the KMS kernel video
1537 You may need to update your console settings in /etc/rc.conf,
1538 most probably the keymap. During boot, /etc/rc.d/syscons will
1539 indicate what you need to do.
1541 vt(4) still has issues and lacks some features compared to
1542 syscons(4). See the wiki for up-to-date information:
1543 https://wiki.freebsd.org/Newcons
1545 If you want to keep using syscons(4), you can do so by adding
1546 the following line to /boot/loader.conf:
1550 pjdfstest has been integrated into kyua as an opt-in test suite.
1551 Please see share/doc/pjdfstest/README for more details on how to
1555 gperf has been removed from the base system for architectures
1556 that use clang. Ports that require gperf will obtain it from the
1560 pjdfstest has been moved from tools/regression/pjdfstest to
1564 At svn r271982, The default linux compat kernel ABI has been adjusted
1565 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1566 update. If you wish to continue using the linux-f10 compat ports,
1567 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1568 encouraged to update their linux-compat packages to linux-c6 during
1569 their next update cycle.
1572 The ofwfb driver, used to provide a graphics console on PowerPC when
1573 using vt(4), no longer allows mmap() of all physical memory. This
1574 will prevent Xorg on PowerPC with some ATI graphics cards from
1575 initializing properly unless x11-servers/xorg-server is updated to
1579 The xdev targets have been converted to using TARGET and
1580 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1583 The default unbound configuration has been modified to address
1584 issues with reverse lookups on networks that use private
1585 address ranges. If you use the local_unbound service, run
1586 "service local_unbound setup" as root to regenerate your
1587 configuration, then "service local_unbound reload" to load the
1591 The GNU texinfo and GNU info pages are not built and installed
1592 anymore, WITH_INFO knob has been added to allow to built and install
1594 UPDATE: see 20150102 entry on texinfo's removal
1597 The GNU readline library is now an INTERNALLIB - that is, it is
1598 statically linked into consumers (GDB and variants) in the base
1599 system, and the shared library is no longer installed. The
1600 devel/readline port is available for third party software that
1604 The Itanium architecture (ia64) has been removed from the list of
1605 known architectures. This is the first step in the removal of the
1609 Commit r268115 has added NFSv4.1 server support, merged from
1610 projects/nfsv4.1-server. Since this includes changes to the
1611 internal interfaces between the NFS related modules, a full
1612 build of the kernel and modules will be necessary.
1613 __FreeBSD_version has been bumped.
1616 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1617 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1618 which differs from the behaviour controlled by this knob.)
1621 Maximal length of the serial number in CTL was increased from 16 to
1622 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1623 and ctld, need to be rebuilt to work with a new kernel.
1626 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1627 1 respectively to match the upstream numbers. They were out of
1628 sync because, when they were originally added to FreeBSD, the
1629 upstream versions were not respected. These libraries are private
1630 and not yet built by default, so renumbering them should be a
1631 non-issue. However, unclean source trees will yield broken test
1632 programs once the operator executes "make delete-old-libs" after a
1633 "make installworld".
1635 Additionally, the atf-sh binary was made private by moving it into
1636 /usr/libexec/. Already-built shell test programs will keep the
1637 path to the old binary so they will break after "make delete-old"
1640 If you are using WITH_TESTS=yes (not the default), wipe the object
1641 tree and rebuild from scratch to prevent spurious test failures.
1642 This is only needed once: the misnumbered libraries and misplaced
1643 binaries have been added to OptionalObsoleteFiles.inc so they will
1644 be removed during a clean upgrade.
1647 Clang and llvm have been upgraded to 3.4.1 release.
1650 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1651 be removed to avoid issues in the future (and has been added to
1655 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1656 past, it affected all builds that used the bsd.*.mk files. The old
1657 behavior was a bug, but people may have relied upon it. To get this
1658 behavior back, you can .include /etc/src.conf from /etc/make.conf
1659 (which is still global and isn't changed). This also changes the
1660 behavior of incremental builds inside the tree of individual
1661 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1662 Although this has survived make universe and some upgrade scenarios,
1663 other upgrade scenarios may have broken. At least one form of
1664 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1665 as well... In cases where MAKESYSPATH isn't working with this
1666 setting, you'll need to set it to the full path to your tree.
1668 One side effect of all this cleaning up is that bsd.compiler.mk
1669 is no longer implicitly included by bsd.own.mk. If you wish to
1670 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1674 The lindev device has been removed since /dev/full has been made a
1675 standard device. __FreeBSD_version has been bumped.
1678 The knob WITHOUT_VI was added to the base system, which controls
1679 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1680 in order to reorder files share/termcap and didn't build ex(1) as a
1681 build tool, so building/installing with WITH_VI is highly advised for
1682 build hosts for older releases.
1684 This issue has been fixed in stable/9 and stable/10 in r277022 and
1685 r276991, respectively.
1688 The YES_HESIOD knob has been removed. It has been obsolete for
1689 a decade. Please move to using WITH_HESIOD instead or your builds
1690 will silently lack HESIOD.
1693 The uart(4) driver has been changed with respect to its handling
1694 of the low-level console. Previously the uart(4) driver prevented
1695 any process from changing the baudrate or the CLOCAL and HUPCL
1696 control flags. By removing the restrictions, operators can make
1697 changes to the serial console port without having to reboot.
1698 However, when getty(8) is started on the serial device that is
1699 associated with the low-level console, a misconfigured terminal
1700 line in /etc/ttys will now have a real impact.
1701 Before upgrading the kernel, make sure that /etc/ttys has the
1702 serial console device configured as 3wire without baudrate to
1703 preserve the previous behaviour. E.g:
1704 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1707 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1708 to improve performance. To re-enable it, if needed, run rpcbind
1709 with command line option -W.
1712 Switched back to the GPL dtc compiler due to updates in the upstream
1713 dts files not being supported by the BSDL dtc compiler. You will need
1714 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1715 may result while building dtb files during a kernel build if you fail
1716 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1719 Clang and llvm have been upgraded to 3.4 release.
1722 The nve(4) driver has been removed. Please use the nfe(4) driver
1723 for NVIDIA nForce MCP Ethernet adapters instead.
1726 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1727 This could cause certain C++ applications using shared libraries built
1728 against the previous version of libc++ to crash. The incompatibility
1729 has now been fixed, but any C++ applications or shared libraries built
1730 between r261283 and r261801 should be recompiled.
1733 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1734 capability mode support. Please note that enabling the feature in
1735 kernel is still highly recommended.
1738 OpenSSH is now built with sandbox support, and will use sandbox as
1739 the default privilege separation method. This requires Capsicum
1740 capability mode support in kernel.
1743 The libelf and libdwarf libraries have been updated to newer
1744 versions from upstream. Shared library version numbers for
1745 these two libraries were bumped. Any ports or binaries
1746 requiring these two libraries should be recompiled.
1747 __FreeBSD_version is bumped to 1100006.
1750 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1751 instead of providing an explicit one, this would prevent such
1752 Makefile from providing its own Kyuafile in the future during
1753 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1754 intervention is needed to clean an objdir if you use NO_CLEAN:
1755 # find /usr/obj -name Kyuafile | xargs rm -f
1758 The behavior of gss_pseudo_random() for the krb5 mechanism
1759 has changed, for applications requesting a longer random string
1760 than produced by the underlying enctype's pseudo-random() function.
1761 In particular, the random string produced from a session key of
1762 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1763 be different at the 17th octet and later, after this change.
1764 The counter used in the PRF+ construction is now encoded as a
1765 big-endian integer in accordance with RFC 4402.
1766 __FreeBSD_version is bumped to 1100004.
1769 The WITHOUT_ATF build knob has been removed and its functionality
1770 has been subsumed into the more generic WITHOUT_TESTS. If you were
1771 using the former to disable the build of the ATF libraries, you
1772 should change your settings to use the latter.
1775 The default version of mtree is nmtree which is obtained from
1776 NetBSD. The output is generally the same, but may vary
1777 slightly. If you found you need identical output adding
1778 "-F freebsd9" to the command line should do the trick. For the
1779 time being, the old mtree is available as fmtree.
1782 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1783 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1784 1.1.4_8 and verify bsdyml not linked in, before running "make
1786 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1788 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1791 The stable/10 branch has been created in subversion from head
1798 Avoid using make -j when upgrading. While generally safe, there are
1799 sometimes problems using -j to upgrade. If your upgrade fails with
1800 -j, please try again without -j. From time to time in the past there
1801 have been problems using -j with buildworld and/or installworld. This
1802 is especially true when upgrading between "distant" versions (eg one
1803 that cross a major release boundary or several minor releases, or when
1804 several months have passed on the -current branch).
1806 Sometimes, obscure build problems are the result of environment
1807 poisoning. This can happen because the make utility reads its
1808 environment when searching for values for global variables. To run
1809 your build attempts in an "environmental clean room", prefix all make
1810 commands with 'env -i '. See the env(1) manual page for more details.
1812 When upgrading from one major version to another it is generally best to
1813 upgrade to the latest code in the currently installed branch first, then
1814 do an upgrade to the new branch. This is the best-tested upgrade path,
1815 and has the highest probability of being successful. Please try this
1816 approach if you encounter problems with a major version upgrade. Since
1817 the stable 4.x branch point, one has generally been able to upgrade from
1818 anywhere in the most recent stable branch to head / current (or even the
1819 last couple of stable branches). See the top of this file when there's
1822 When upgrading a live system, having a root shell around before
1823 installing anything can help undo problems. Not having a root shell
1824 around can lead to problems if pam has changed too much from your
1825 starting point to allow continued authentication after the upgrade.
1827 This file should be read as a log of events. When a later event changes
1828 information of a prior event, the prior event should not be deleted.
1829 Instead, a pointer to the entry with the new information should be
1830 placed in the old entry. Readers of this file should also sanity check
1831 older entries before relying on them blindly. Authors of new entries
1832 should write them with this in mind.
1836 When upgrading the boot ZFS pool to a new version, always follow
1839 1.) recompile and reinstall the ZFS boot loader and boot block
1840 (this is part of "make buildworld" and "make installworld")
1842 2.) update the ZFS boot block on your boot drive
1844 The following example updates the ZFS boot block on the first
1845 partition (freebsd-boot) of a GPT partitioned drive ada0:
1846 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1848 Non-boot pools do not need these updates.
1852 If you are updating from a prior version of FreeBSD (even one just
1853 a few days old), you should follow this procedure. It is the most
1854 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1856 make kernel-toolchain
1857 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1858 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1860 To test a kernel once
1861 ---------------------
1862 If you just want to boot a kernel once (because you are not sure
1863 if it works, or if you want to boot a known bad kernel to provide
1864 debugging information) run
1865 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1866 nextboot -k testkernel
1868 To rebuild everything and install it on the current system.
1869 -----------------------------------------------------------
1870 # Note: sometimes if you are running current you gotta do more than
1871 # is listed here if you are upgrading from a really old current.
1873 <make sure you have good level 0 dumps>
1875 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1876 make installkernel KERNCONF=YOUR_KERNEL_HERE
1878 <reboot in single user> [3]
1885 To cross-install current onto a separate partition
1886 --------------------------------------------------
1887 # In this approach we use a separate partition to hold
1888 # current's root, 'usr', and 'var' directories. A partition
1889 # holding "/", "/usr" and "/var" should be about 2GB in
1892 <make sure you have good level 0 dumps>
1895 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1896 <maybe newfs current's root partition>
1897 <mount current's root partition on directory ${CURRENT_ROOT}>
1898 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1899 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1900 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1901 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1902 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1903 <reboot into current>
1904 <do a "native" rebuild/install as described in the previous section>
1905 <maybe install compatibility libraries from ports/misc/compat*>
1909 To upgrade in-place from stable to current
1910 ----------------------------------------------
1911 <make sure you have good level 0 dumps>
1913 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1914 make installkernel KERNCONF=YOUR_KERNEL_HERE
1916 <reboot in single user> [3]
1923 Make sure that you've read the UPDATING file to understand the
1924 tweaks to various things you need. At this point in the life
1925 cycle of current, things change often and you are on your own
1926 to cope. The defaults can also change, so please read ALL of
1927 the UPDATING entries.
1929 Also, if you are tracking -current, you must be subscribed to
1930 freebsd-current@freebsd.org. Make sure that before you update
1931 your sources that you have read and understood all the recent
1932 messages there. If in doubt, please track -stable which has
1933 much fewer pitfalls.
1935 [1] If you have third party modules, such as vmware, you
1936 should disable them at this point so they don't crash your
1939 [3] From the bootblocks, boot -s, and then do
1944 adjkerntz -i # if CMOS is wall time
1945 Also, when doing a major release upgrade, it is required that
1946 you boot into single user mode to do the installworld.
1948 [4] Note: This step is non-optional. Failure to do this step
1949 can result in a significant reduction in the functionality of the
1950 system. Attempting to do it by hand is not recommended and those
1951 that pursue this avenue should read this file carefully, as well
1952 as the archives of freebsd-current and freebsd-hackers mailing lists
1953 for potential gotchas. The -U option is also useful to consider.
1954 See mergemaster(8) for more information.
1956 [5] Usually this step is a no-op. However, from time to time
1957 you may need to do this if you get unknown user in the following
1958 step. It never hurts to do it all the time. You may need to
1959 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1960 install) after the buildworld before this step if you last updated
1961 from current before 20130425 or from -stable before 20130430.
1963 [6] This only deletes old files and directories. Old libraries
1964 can be deleted by "make delete-old-libs", but you have to make
1965 sure that no program is using those libraries anymore.
1967 [8] The new kernel must be able to run existing binaries used by
1968 an installworld. When upgrading across major versions, the new
1969 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1970 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1971 binaries). Failure to do so may leave you with a system that is
1972 hard to boot to recover. A GENERIC kernel will include suitable
1973 compatibility options to run binaries from older branches.
1975 Make sure that you merge any new devices from GENERIC since the
1976 last time you updated your kernel config file.
1978 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1979 "?=" instead of the "=" assignment operator, so that buildworld can
1980 override the CPUTYPE if it needs to.
1982 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1983 not on the command line, or in /etc/make.conf. buildworld will
1984 warn if it is improperly defined.
1987 This file contains a list, in reverse chronological order, of major
1988 breakages in tracking -current. It is not guaranteed to be a complete
1989 list of such breakages, and only contains entries since September 23, 2011.
1990 If you need to see UPDATING entries from before that date, you will need
1991 to fetch an UPDATING file from an older FreeBSD release.
1993 Copyright information:
1995 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1997 Redistribution, publication, translation and use, with or without
1998 modification, in full or in part, in any form or format of this
1999 document are permitted without further permission from the author.
2001 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2002 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2003 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2004 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2005 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2006 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2007 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2008 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2009 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2010 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2011 POSSIBILITY OF SUCH DAMAGE.
2013 Contact Warner Losh if you have any questions about your use of