1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
20 FreeBSD 13.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 The tunable "security.stack_protect.permit_nonrandom_cookies" may be
36 set to a non-zero value to boot systems that do not provide early
37 entropy. Otherwise, such systems may see the panic message:
38 "cannot initialize stack cookies because random device is not yet
42 The loadable random module KPI has changed; the random_infra_init()
43 routine now requires a 3rd function pointer for a bool (*)(void)
44 method that returns true if the random device is seeded (and
48 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
49 built from head sources between r320757 (July 6, 2017) and
50 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
51 is added to the command line.
52 nfsuserd daemons built from head sources that are post-r338192 are
53 not affected and should continue to work.
56 The fuse(4) module has been renamed to fusefs(4) for consistency with
57 other filesystems. You should update any kld_load="fuse" entries in
58 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
59 "options FUSE" enties in kernel config files.
62 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
63 8.0.0. Please see the 20141231 entry below for information about
64 prerequisites and upgrading, if you are not already using clang 3.5.0
68 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
69 compiled into your custom kernel, add 'device xz' statement to the
73 drm and drm2 have been removed from the tree. Please see
74 https://wiki.freebsd.org/Graphics for the latest information on
75 migrating to the drm ports.
78 Iflib is no longer unconditionally compiled into the kernel. Drivers
79 using iflib and statically compiled into the kernel, now require
80 the 'device iflib' config option. For the same drivers loaded as
81 modules on kernels not having 'device iflib', the iflib.ko module
82 is loaded automatically.
85 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
86 options no longer exist since r343219 and r343427 respectively;
87 nothing uses them, so they should be just removed from custom
91 r342635 changes the way efibootmgr(8) works by requiring users to add
92 the -b (bootnum) parameter for commands where the bootnum was previously
93 specified with each option. For example 'efibootmgr -B 0001' is now
94 'efibootmgr -B -b 0001'.
97 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
98 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
99 servers that have vfs.nfsd.nfs_privport set will only allow mounts
100 from clients using a reserved port#. Since both the FreeBSD and Linux
101 NFSv4 clients use reserved port#s by default, this should not affect
105 The XLP config has been removed. We can't support 64-bit atomics in this
106 kernel because it is running in 32-bit mode. XLP users must transition
107 to running a 64-bit kernel (XLP64 or XLPN32).
109 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
110 the preferred emulator today and we don't need two different ones.
112 The old sibyte / swarm / Broadcom BCM1250 support has been
113 removed from the mips port.
116 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
117 7.0.1. Please see the 20141231 entry below for information about
118 prerequisites and upgrading, if you are not already using clang 3.5.0
122 Remove the timed and netdate programs from the base tree. Setting
123 the time with these deamons has been obsolete for over a decade.
126 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
127 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
128 it produces broken binaries when ifuncs are in use. Users needing
129 GNU ld should install the binutils port or package.
132 The BSD crtbegin and crtend code has been enabled by default. It has
133 had extensive testing on amd64, arm64, and i386. It can be disabled
134 by building a world with -DWITHOUT_BSD_CRTBEGIN.
137 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
138 has been converted to a port (misc/ctm) and will be removed from
139 FreeBSD-13. It is available as a package (ctm) for all supported
143 The default newsyslog.conf(5) file has been changed to only include
144 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
145 the filenames end in '.conf' and do not begin with a '.'.
147 You should check the configuration files in these two directories match
148 this naming convention. You can verify which configuration files are
149 being included using the command:
153 Ports for the DRM modules have been simplified. Now, amd64 users should
154 just install the drm-kmod port. All others should install
157 Graphics hardware that's newer than about 2010 usually works with
158 drm-kmod. For hardware older than 2013, however, some users will need
159 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
160 than 2008 usually only works in drm-legacy-kmod. The graphics team can
161 only commit to hardware made since 2013 due to the complexity of the
162 market and difficulty to test all the older cards effectively. If you
163 have hardware supported by drm-kmod, you are strongly encouraged to use
164 that as you will get better support.
166 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
167 elsewhere, the drm and drm2 modules will be eliminated from the src base
168 soon (with a limited exception for arm). Please update to the package
169 asap and report any issues to x11@freebsd.org.
171 Generally, anybody using the drm*-kmod packages should add
172 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
173 cross-threading surprises, especially with automatic driver
174 loading from X11 startup. These will become the defaults in 13-current
178 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
179 custom kernel and module loading configuration files must be updated
180 accordingly. Moreover, interfaces previous presented as ixlvN to the
181 system are now exposed as iavfN and network configuration files must
182 be adjusted as necessary.
185 OpenSSL has been updated to version 1.1.1. This update included
186 additional various API changes througout the base system. It is
187 important to rebuild third-party software after upgrading. The value
188 of __FreeBSD_version has been bumped accordingly.
191 The legacy DRM modules and drivers have now been added to the loader's
192 module blacklist, in favor of loading them with kld_list in rc.conf(5).
193 The module blacklist may be overridden with the loader.conf(5)
194 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
198 The cam(4) based nda(4) driver will be used over nvd(4) by default on
199 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
200 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
201 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
205 Reproducible build mode is now on by default, in preparation for
206 FreeBSD 12.0. This eliminates build metadata such as the user,
207 host, and time from the kernel (and uname), unless the working tree
208 corresponds to a modified checkout from a version control system.
209 The previous behavior can be obtained by setting the /etc/src.conf
210 knob WITHOUT_REPRODUCIBLE_BUILD.
213 The Yarrow CSPRNG has been removed from the kernel as it has not been
214 supported by its designers since at least 2003. Fortuna has been the
215 default since FreeBSD-11.
218 devctl freeze/thaw have gone into the tree, the rc scripts have been
219 updated to use them and devmatch has been changed. You should update
220 kernel, userland and rc scripts all at the same time.
223 The default interpreter has been switched from 4th to Lua.
224 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
225 interpreter. If you have custom FORTH code you will need to set
226 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
227 src.conf for the build. This will create default hard links between
228 loader and loader_4th instead of loader and loader_lua, the new default.
229 If you are using UEFI it will create the proper hard link to loader.efi.
231 bhyve uses userboot.so. It remains 4th-only until some issues are solved
232 regarding coexisting with multiple versions of FreeBSD are resolved.
235 ls(1) now respects the COLORTERM environment variable used in other
236 systems and software to indicate that a colored terminal is both
237 supported and desired. If ls(1) is suddenly emitting colors, they may
238 be disabled again by either removing the unwanted COLORTERM from your
239 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
240 may not be observed in a future release.
243 The default pager for most commands has been changed to "less". To
244 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
248 The jedec_ts(4) driver has been removed. A superset of its functionality
249 is available in the jedec_dimm(4) driver, and the manpage for that
250 driver includes migration instructions. If you have "device jedec_ts"
251 in your kernel configuration file, it must be removed.
254 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
255 This should have no effect if the kernel is booted via BIOS/legacy boot.
256 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
257 has a buggy firmware that prevents a successful boot due to use of
261 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
262 support has been removed from the tree. These ports were
263 obsolete and/or known to be broken for many years.
266 loader.efi has been augmented to participate more fully in the
267 UEFI boot manager protocol. loader.efi will now look at the
268 BootXXXX environment variable to determine if a specific kernel
269 or root partition was specified. XXXX is derived from BootCurrent.
270 efibootmgr(8) manages these standard UEFI variables.
273 zfsloader's functionality has now been folded into loader.
274 zfsloader is no longer necessary once you've updated your
275 boot blocks. For a transition period, we will install a
276 hardlink for zfsloader to loader to allow a smooth transition
277 until the boot blocks can be updated (hard link because old
278 zfs boot blocks don't understand symlinks).
281 ARM64 now have efifb support, if you want to have serial console
282 on your arm64 board when an screen is connected and the bootloader
283 setup a framebuffer for us to use, just add :
287 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
288 an screen connected as the firmware will setup a framebuffer are that
289 u-boot will expose as an EFI framebuffer.
292 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
293 or take steps to update /etc/passwd before doing installworld on
294 existing systems. Do not skip the "mergemaster -Fp" step before
295 installworld, as described in the update procedures near the bottom
296 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
297 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
298 the ntp config file contain options that change file/dir locations.
299 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
300 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
301 taking steps to ensure that all required files/dirs are accessible
305 Big endian arm support has been removed.
308 The static environment setup in kernel configs is no longer mutually
309 exclusive with the loader(8) environment by default. In order to
310 restore the previous default behavior of disabling the loader(8)
311 environment if a static environment is present, you must specify
312 loader_env.disabled=1 in the static environment.
315 The ABI of syscalls used by management tools like sockstat and
316 netstat has been broken to allow 32-bit binaries to work on
317 64-bit kernels without modification. These programs will need
318 to match the kernel in order to function. External programs may
319 require minor modifications to accommodate a change of type in
320 structures from pointers to 64-bit virtual addresses.
323 On i386 and amd64 atomics are now inlined. Out of tree modules using
324 atomics will need to be rebuilt.
327 The '%I' format in the kern.corefile sysctl limits the number of
328 core files that a process can generate to the number stored in the
329 debug.ncores sysctl. The '%I' format is replaced by the single digit
330 index. Previously, if all indexes were taken the kernel would overwrite
331 only a core file with the highest index in a filename.
332 Currently the system will create a new core file if there is a free
333 index or if all slots are taken it will overwrite the oldest one.
336 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
337 6.0.1. Please see the 20141231 entry below for information about
338 prerequisites and upgrading, if you are not already using clang 3.5.0
342 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
343 needed to be changed to work with it. This change was made with r335763
344 and requires a mergemaster / etcupdate / etc to update the installed
348 r334930 changed the interface between the NFS modules, so they all
349 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
352 As of r334391 lld is the default amd64 system linker; it is installed
353 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
357 The kernel / userland interface for devinfo changed, so you'll
358 need a new kernel and userland as a pair for it to work (rebuilding
359 lib/libdevinfo is all that's required). devinfo and devmatch will
360 not work, but everything else will when there's a mismatch.
363 The on-disk format for hwpmc callchain records has changed to include
364 threadid corresponding to a given record. This changes the field offsets
365 and thus requires that libpmcstat be rebuilt before using a kernel
369 The vxge(4) driver has been removed. This driver was introduced into
370 HEAD one week before the Exar left the Ethernet market and is not
371 known to be used. If you have device vxge in your kernel config file
375 The amd64 kernel now requires a ld that supports ifunc to produce a
376 working kernel, either lld or a newer binutils. lld is built by default
377 on amd64, and the 'buildkernel' target uses it automatically. However,
378 it is not the default linker, so building the kernel the traditional
379 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
380 binutils port/package). lld will soon be default, and this requirement
383 NOTE: As of r334391 lld is the default system linker on amd64, and no
384 workaround is necessary.
387 The nxge(4) driver has been removed. This driver was for PCI-X 10g
388 cards made by s2io/Neterion. The company was aquired by Exar and
389 no longer sells or supports Ethernet products. If you have device
390 nxge in your kernel config file it must be removed.
393 The tz database (tzdb) has been updated to 2018e. This version more
394 correctly models time stamps in time zones with negative DST such as
395 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
396 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
397 time zone abbreviations and the tm_isdst flag.
400 The ixgb(4) driver has been removed. This driver was for an early and
401 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
402 quickly shifted to the long lived ixgbe family. If you have device
403 ixgb in your kernel config file it must be removed.
406 The lmc(4) driver has been removed. This was a WAN interface
407 card that was already reportedly rare in 2003, and had an ambiguous
408 license. If you have device lmc in your kernel config file it must
412 Support for Arcnet networks has been removed. If you have device
413 arcnet or device cm in your kernel config file they must be
417 Support for FDDI networks has been removed. If you have device
418 fddi or device fpa in your kernel config file they must be
422 In addition to supporting RFC 3164 formatted messages, the
423 syslogd(8) service is now capable of parsing RFC 5424 formatted
424 log messages. The main benefit of using RFC 5424 is that clients
425 may now send log messages with timestamps containing year numbers,
426 microseconds and time zone offsets.
428 Similarly, the syslog(3) C library function has been altered to
429 send RFC 5424 formatted messages to the local system logging
430 daemon. On systems using syslogd(8), this change should have no
431 negative impact, as long as syslogd(8) and the C library are
432 updated at the same time. On systems using a different system
433 logging daemon, it may be necessary to make configuration
434 adjustments, depending on the software used.
436 When using syslog-ng, add the 'syslog-protocol' flag to local
437 input sources to enable parsing of RFC 5424 formatted messages:
440 unix-dgram("/var/run/log" flags(syslog-protocol));
443 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
444 of the 'imuxsock' module to let messages be processed by the
445 regular RFC 3164/5424 parsing pipeline:
447 module(load="imuxsock" SysSock.UseSpecialParser="off")
449 Do note that these changes only affect communication between local
450 applications and syslogd(8). The format that syslogd(8) uses to
451 store messages on disk or forward messages to other systems
452 remains unchanged. syslogd(8) still uses RFC 3164 for these
453 purposes. Options to customize this behaviour will be added in the
454 future. Utilities that process log files stored in /var/log are
455 thus expected to continue to function as before.
457 __FreeBSD_version has been incremented to 1200061 to denote this
461 Support for token ring networks has been removed. If you
462 have "device token" in your kernel config you should remove
463 it. No device drivers supported token ring.
466 makefs was modified to be able to tag ISO9660 El Torito boot catalog
467 entries as EFI instead of overloading the i386 tag as done previously.
468 The amd64 mkisoimages.sh script used to build amd64 ISO images for
469 release was updated to use this. This may mean that makefs must be
470 updated before "make cdrom" can be run in the release directory. This
471 should be as simple as:
473 $ cd $SRCDIR/usr.sbin/makefs
474 $ make depend all install
477 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
478 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
479 Co-existance for the transition period will come shortly. Booting is a
480 complex environment and test coverage for Lua-enabled loaders has been
481 thin, so it would be prudent to assume it might not work and make
482 provisions for backup boot methods.
485 devmatch functionality has been turned on in devd. It will automatically
486 load drivers for unattached devices. This may cause unexpected drivers
487 to be loaded. Please report any problems to current@ and
491 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
492 6.0.0. Please see the 20141231 entry below for information about
493 prerequisites and upgrading, if you are not already using clang 3.5.0
497 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
498 This means it is used to link the kernel and userland libraries and
499 executables, but is not yet installed as /usr/bin/ld by default.
501 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
502 WITHOUT_LLD_BOOTSTRAP=yes
505 On i386, pmtimer has been removed. Its functionality has been folded
506 into apm. It was a no-op on ACPI in current for a while now (but was
507 still needed on i386 in FreeBSD 11 and earlier). Users may need to
508 remove it from kernel config files.
511 The use of RSS hash from the network card aka flowid has been
512 disabled by default for lagg(4) as it's currently incompatible with
513 the lacp and loadbalance protocols.
515 This can be re-enabled by setting the following in loader.conf:
516 net.link.lagg.default_use_flowid="1"
519 The SW_WATCHDOG option is no longer necessary to enable the
520 hardclock-based software watchdog if no hardware watchdog is
521 configured. As before, SW_WATCHDOG will cause the software
522 watchdog to be enabled even if a hardware watchdog is configured.
525 r326887 fixes the issue described in the 20171214 UPDATING entry.
526 r326888 flips the switch back to building GELI support always.
529 r362593 broke ZFS + GELI support for reasons unknown. However,
530 it also broke ZFS support generally, so GELI has been turned off
531 by default as the lesser evil in r326857. If you boot off ZFS and/or
532 GELI, it might not be a good time to update.
535 PowerPC users must update loader(8) by rebuilding world before
536 installing a new kernel, as the protocol connecting them has
537 changed. Without the update, loader metadata will not be passed
538 successfully to the kernel and users will have to enter their
539 root partition at the kernel mountroot prompt to continue booting.
540 Newer versions of loader can boot old kernels without issue.
543 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
544 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
545 to WITH/OUT_LOADER_GELI.
548 The naive and non-compliant support of posix_fallocate(2) in ZFS
549 has been removed as of r325320. The system call now returns EINVAL
550 when used on a ZFS file. Although the new behavior complies with the
551 standard, some consumers are not prepared to cope with it.
552 One known victim is lld prior to r325420.
555 Building in a FreeBSD src checkout will automatically create object
556 directories now rather than store files in the current directory if
557 'make obj' was not ran. Calling 'make obj' is no longer necessary.
558 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
559 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
563 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
564 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
565 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
566 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
567 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
568 The UNIFIED_OBJDIR option is a transitional feature that will be
569 removed for 12.0 release; please migrate to the new format for any
570 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
571 than hardcoding paths.
574 The native-xtools target no longer installs the files by default to the
575 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
576 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
579 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
580 options are changing from controlling the build if defined / undefined
581 to controlling the build with explicit 'yes' or 'no' values. They will
582 shift to WITH/WITHOUT options to match other options in the system.
585 libstand has turned into a private library for sys/boot use only.
586 It is no longer supported as a public interface outside of sys/boot.
589 The arm port has split armv6 into armv6 and armv7. armv7 is now
590 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
591 and are running a kernel from before r324363, you will need to add
592 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
595 When building multiple kernels using KERNCONF, non-existent KERNCONF
596 files will produce an error and buildkernel will fail. Previously
597 missing KERNCONF files silently failed giving no indication as to
598 why, only to subsequently discover during installkernel that the
599 desired kernel was never built in the first place.
602 The default serial number format for CTL LUNs has changed. This will
603 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
604 or iSCSI clients care about their LUNs' serial numbers. Users who
605 require serial number stability should hardcode serial numbers in
609 For 32-bit arm compiled for hard-float support, soft-floating point
610 binaries now always get their shared libraries from
611 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
612 /usr/libsoft also existed). Only users with a hard-float ld.so, but
613 soft-float everything else should be affected.
616 The geli password typed at boot is now hidden. To restore the previous
617 behavior, see geli(8) for configuration options.
620 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
621 sysctl values. Minor nit, but requires a rebuild of both world/kernel
625 "make check" behavior (made in ^/head@r295380) has been changed to
626 execute from a limited sandbox, as opposed to executing from
630 - The "beforecheck" and "aftercheck" targets are now specified.
631 - ${CHECKDIR} (added in commit noted above) has been removed.
632 - Legacy behavior can be enabled by setting
633 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
635 If the limited sandbox mode is enabled, "make check" will execute
636 "make distribution", then install, execute the tests, and clean up the
637 sandbox if successful.
639 The "make distribution" and "make install" targets are typically run as
640 root to set appropriate permissions and ownership at installation time.
641 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
642 environment if executing "make check" with limited sandbox mode using
643 an unprivileged user.
646 Since the switch to GPT disk labels, fsck for UFS/FFS has been
647 unable to automatically find alternate superblocks. As of r322297,
648 the information needed to find alternate superblocks has been
649 moved to the end of the area reserved for the boot block.
650 Filesystems created with a newfs of this vintage or later
651 will create the recovery information. If you have a filesystem
652 created prior to this change and wish to have a recovery block
653 created for your filesystem, you can do so by running fsck in
654 foreground mode (i.e., do not use the -p or -y options). As it
655 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
656 to which you should answer yes.
659 As of r321665, an NFSv4 server configuration that services
660 Kerberos mounts or clients that do not support the uid/gid in
661 owner/owner_group string capability, must explicitly enable
662 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
663 machine's /etc/rc.conf file.
666 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
667 Please see the 20141231 entry below for information about prerequisites
668 and upgrading, if you are not already using clang 3.5.0 or higher.
671 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
672 r-commands (rlogin, rsh, etc.) to be built with the base system.
675 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
676 a very major ABI incompatible change, so users of FreeBSD/powerpc must
677 be careful when performing source upgrades. It is best to run
678 'make installworld' from an alternate root system, either a live
679 CD/memory stick, or a temporary root partition. Additionally, all ports
680 must be recompiled. powerpc64 is largely unaffected, except in the case
681 of 32-bit compatibility. All 32-bit binaries will be affected.
684 Forward compatibility for the "ino64" project have been committed. This
685 will allow most new binaries to run on older kernels in a limited
686 fashion. This prevents many of the common foot-shooting actions in the
687 upgrade as well as the limited ability to roll back the kernel across
688 the ino64 upgrade. Complicated use cases may not work properly, though
689 enough simpler ones work to allow recovery in most situations.
692 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
693 if you require the GPL compiler.
696 The internal ABI used for communication between the NFS kernel modules
697 was changed by r320085, so __FreeBSD_version was bumped to
698 ensure all the NFS related modules are updated together.
701 The ABI of struct event was changed by extending the data
702 member to 64bit and adding ext fields. For upgrade, same
703 precautions as for the entry 20170523 "ino64" must be
707 The GNU roff toolchain has been removed from base. To render manpages
708 which are not supported by mandoc(1), man(1) can fallback on GNU roff
709 from ports (and recommends to install it).
710 To render roff(7) documents, consider using GNU roff from ports or the
711 heirloom doctools roff toolchain from ports via pkg install groff or
712 via pkg install heirloom-doctools.
715 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
716 smaller runtime footprint builds. This is useful for embedded systems
717 which only require one chipset support.
719 If you load it as a module, make sure this is in /boot/loader.conf:
723 This will load the HAL, all chip/RF backends and if_ath_pci.
724 If you have if_ath_pci in /boot/loader.conf, ensure it is after
725 if_ath or it will not load any HAL chipset support.
727 If you want to selectively load things (eg on ye cheape ARM/MIPS
728 platforms where RAM is at a premium) you should:
731 * load the chip modules in question
732 * load ath_rate, ath_dfs
734 * load if_ath_pci and/or if_ath_ahb depending upon your particular
735 bus bind type - this is where probe/attach is done.
737 For further comments/feedback, poke adrian@ .
740 The "ino64" 64-bit inode project has been committed, which extends
741 a number of types to 64 bits. Upgrading in place requires care and
742 adherence to the documented upgrade procedure.
744 If using a custom kernel configuration ensure that the
745 COMPAT_FREEBSD11 option is included (as during the upgrade the
746 system will be running the ino64 kernel with the existing world).
748 For the safest in-place upgrade begin by removing previous build
749 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
750 procedure documented below under the heading "To rebuild everything and
751 install it on the current system." Specifically, a reboot is required
752 after installing the new kernel before installing world. While an
753 installworld normally works by accident from multiuser after rebooting
754 the proper kernel, there are many cases where this will fail across this
755 upgrade and installworld from single user is required.
758 The NATM framework including the en(4), fatm(4), hatm(4), and
759 patm(4) devices has been removed. Consumers should plan a
760 migration before the end-of-life date for FreeBSD 11.
763 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
764 diff has not been implemented, if those are needed a newer version of
765 GNU diff is available via the diffutils package under the gdiff name.
768 As of r316810 for ipfilter, keep frags is no longer assumed when
769 keep state is specified in a rule. r316810 aligns ipfilter with
770 documentation in man pages separating keep frags from keep state.
771 This allows keep state to be specified without forcing keep frags
772 and allows keep frags to be specified independently of keep state.
773 To maintain previous behaviour, also specify keep frags with
774 keep state (as documented in ipf.conf.5).
777 arm64 builds now use the base system LLD 4.0.0 linker by default,
778 instead of requiring that the aarch64-binutils port or package be
779 installed. To continue using aarch64-binutils, set
780 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
783 The UDP optimization in entry 20160818 that added the sysctl
784 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
785 packets will no longer be treated as L3 broadcast packets.
788 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
789 use any explicitly assigned loopback address available in the jail
790 instead of using the first assigned address of the jail.
793 The ctl.ko module no longer implements the iSCSI target frontend:
794 cfiscsi.ko does instead.
796 If building cfiscsi.ko as a kernel module, the module can be loaded
797 via one of the following methods:
798 - `cfiscsi_load="YES"` in loader.conf(5).
799 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
800 - ctladm(8)/ctld(8), when compiled with iSCSI support
801 (`WITH_ISCSI=yes` in src.conf(5))
803 Please see cfiscsi(4) for more details.
806 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
807 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
808 same source (previously, the dependency of mmcsd.ko on mmc.ko was
809 missing, but mmcsd.ko now will refuse to load if it is incompatible
813 The syntax of ipfw(8) named states was changed to avoid ambiguity.
814 If you have used named states in the firewall rules, you need to modify
815 them after installworld and before rebooting. Now named states must
816 be prefixed with colon.
819 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
820 removed as the userland we provide cannot use them. The KMS version
821 (sys/dev/drm2) supports the same hardware.
824 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
825 Please see the 20141231 entry below for information about prerequisites
826 and upgrading, if you are not already using clang 3.5.0 or higher.
829 The code that provides support for ZFS .zfs/ directory functionality
830 has been reimplemented. It's not possible now to create a snapshot
831 by mkdir under .zfs/snapshot/. That should be the only user visible
835 EISA bus support has been removed. The WITH_EISA option is no longer
839 MCA bus support has been removed.
842 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
843 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
846 The EM_MULTIQUEUE kernel configuration option is deprecated now that
847 the em(4) driver conforms to iflib specifications.
850 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
851 IFLIB. If you have a custom kernel configuration that excludes em(4)
852 but you use igb(4), you need to re-add em(4) to your custom
856 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
857 Please see the 20141231 entry below for information about prerequisites
858 and upgrading, if you are not already using clang 3.5.0 or higher.
861 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
862 Please see the 20141231 entry below for information about prerequisites
863 and upgrading, if you are not already using clang 3.5.0 or higher.
866 The layout of the pmap structure has changed for powerpc to put the pmap
867 statistics at the front for all CPU variations. libkvm(3) and all tools
868 that link against it need to be recompiled.
871 isl(4) and cyapa(4) drivers now require a new driver,
872 chromebook_platform(4), to work properly on Chromebook-class hardware.
873 On other types of hardware the drivers may need to be configured using
874 device hints. Please see the corresponding manual pages for details.
877 The urtwn(4) driver was merged into rtwn(4) and now consists of
878 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
880 Also, firmware for RTL8188CE was renamed due to possible name
881 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
884 GNU rcs has been removed from base. It is available as packages:
885 - rcs: Latest GPLv3 GNU rcs version.
886 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
890 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
891 modules now requires that the kernel configuration contain the
892 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
895 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
896 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
899 Relocatable object files with the extension of .So have been renamed
900 to use an extension of .pico instead. The purpose of this change is
901 to avoid a name clash with shared libraries on case-insensitive file
902 systems. On those file systems, foo.So is the same file as foo.so.
905 GNU rcs has been turned off by default. It can (temporarily) be built
906 again by adding WITH_RCS knob in src.conf.
907 Otherwise, GNU rcs is available from packages:
908 - rcs: Latest GPLv3 GNU rcs version.
909 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
912 The backup_uses_rcs functionality has been removed from rc.subr.
915 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
916 two separate components, QUEUE_MACRO_DEBUG_TRACE and
917 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
918 QUEUE_MACRO_DEBUG behavior.
921 r304787 changed some ioctl interfaces between the iSCSI userspace
922 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
923 rebuilt to work with new kernels. __FreeBSD_version has been bumped
927 The UDP receive code has been updated to only treat incoming UDP
928 packets that were addressed to an L2 broadcast address as L3
929 broadcast packets. It is not expected that this will affect any
930 standards-conforming UDP application. The new behaviour can be
931 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
935 Remove the openbsd_poll system call.
936 __FreeBSD_version has been bumped because of this.
939 The stable/11 branch has been created from head@r302406.
942 The libc stub for the pipe(2) system call has been replaced with
943 a wrapper that calls the pipe2(2) system call and the pipe(2)
944 system call is now only implemented by the kernels that include
945 "options COMPAT_FREEBSD10" in their config file (this is the
946 default). Users should ensure that this option is enabled in
947 their kernel or upgrade userspace to r302092 before upgrading their
951 CAM will now strip leading spaces from SCSI disks' serial numbers.
952 This will affect users who create UFS filesystems on SCSI disks using
953 those disk's diskid device nodes. For example, if /etc/fstab
954 previously contained a line like
955 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
956 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
957 transforms like gmirror may also be affected. ZFS users should
961 The bitstring(3) API has been updated with new functionality and
962 improved performance. But it is binary-incompatible with the old API.
963 Objects built with the new headers may not be linked against objects
964 built with the old headers.
967 The brk and sbrk functions have been removed from libc on arm64.
968 Binutils from ports has been updated to not link to these
969 functions and should be updated to the latest version before
970 installing a new libc.
973 The armv6 port now defaults to hard float ABI. Limited support
974 for running both hardfloat and soft float on the same system
975 is available using the libraries installed with -DWITH_LIBSOFT.
976 This has only been tested as an upgrade path for installworld
977 and packages may fail or need manual intervention to run. New
978 packages will be needed.
980 To update an existing self-hosted armv6hf system, you must add
981 TARGET_ARCH=armv6 on the make command line for both the build
982 and the install steps.
985 Kernel modules compiled outside of a kernel build now default to
986 installing to /boot/modules instead of /boot/kernel. Many kernel
987 modules built this way (such as those in ports) already overrode
988 KMODDIR explicitly to install into /boot/modules. However,
989 manually building and installing a module from /sys/modules will
990 now install to /boot/modules instead of /boot/kernel.
993 The CAM I/O scheduler has been committed to the kernel. There should be
994 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
995 list of known rogues that claim support for this but actually corrupt
996 data is believed to be complete, be on the lookout for data
997 corruption. The known rogue list is believed to be complete:
999 o Crucial MX100, M550 drives with MU01 firmware.
1000 o Micron M510 and M550 drives with MU01 firmware.
1001 o Micron M500 prior to MU07 firmware
1002 o Samsung 830, 840, and 850 all firmwares
1003 o FCCT M500 all firmwares
1005 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1006 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1007 updated firmware. Black listed drives will work correctly because these
1008 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1009 this list is the same as found in Linux, it's believed there are no
1010 other rogues in the market place. All other models from the above
1013 To be safe, if you are at all concerned, you can quirk each of your
1014 drives to prevent NCQ from being sent by setting:
1015 kern.cam.ada.X.quirks="0x2"
1016 in loader.conf. If the drive requires the 4k sector quirk, set the
1017 quirks entry to 0x3.
1020 The FAST_DEPEND build option has been removed and its functionality is
1021 now the one true way. The old mkdep(1) style of 'make depend' has
1022 been removed. See 20160311 for further details.
1025 Resource range types have grown from unsigned long to uintmax_t. All
1026 drivers, and anything using libdevinfo, need to be recompiled.
1029 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1030 builds. It no longer runs mkdep(1) during 'make depend', and the
1031 'make depend' stage can safely be skipped now as it is auto ran
1032 when building 'make all' and will generate all SRCS and DPSRCS before
1033 building anything else. Dependencies are gathered at compile time with
1034 -MF flags kept in separate .depend files per object file. Users should
1035 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1036 stale .depend files.
1039 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1040 kernel modules. Therefore, if you load any kernel modules at boot time,
1041 please install the boot loaders after you install the kernel, but before
1045 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1046 make installkernel KERNCONF=YOUR_KERNEL_HERE
1047 make -C sys/boot install
1048 <reboot in single user>
1050 Then follow the usual steps, described in the General Notes section,
1054 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1055 see the 20141231 entry below for information about prerequisites and
1056 upgrading, if you are not already using clang 3.5.0 or higher.
1059 The AIO subsystem is now a standard part of the kernel. The
1060 VFS_AIO kernel option and aio.ko kernel module have been removed.
1061 Due to stability concerns, asynchronous I/O requests are only
1062 permitted on sockets and raw disks by default. To enable
1063 asynchronous I/O requests on all file types, set the
1064 vfs.aio.enable_unsafe sysctl to a non-zero value.
1067 The ELF object manipulation tool objcopy is now provided by the
1068 ELF Tool Chain project rather than by GNU binutils. It should be a
1069 drop-in replacement, with the addition of arm64 support. The
1070 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1071 to obtain the GNU version if necessary.
1074 Building ZFS pools on top of zvols is prohibited by default. That
1075 feature has never worked safely; it's always been prone to deadlocks.
1076 Using a zvol as the backing store for a VM guest's virtual disk will
1077 still work, even if the guest is using ZFS. Legacy behavior can be
1078 restored by setting vfs.zfs.vol.recursive=1.
1081 The NONE and HPN patches has been removed from OpenSSH. They are
1082 still available in the security/openssh-portable port.
1085 With the addition of ypldap(8), a new _ypldap user is now required
1086 during installworld. "mergemaster -p" can be used to add the user
1087 prior to installworld, as documented in the handbook.
1090 The tftp loader (pxeboot) now uses the option root-path directive. As a
1091 consequence it no longer looks for a pxeboot.4th file on the tftp
1092 server. Instead it uses the regular /boot infrastructure as with the
1096 The code to start recording plug and play data into the modules has
1097 been committed. While the old tools will properly build a new kernel,
1098 a number of warnings about "unknown metadata record 4" will be produced
1099 for an older kldxref. To avoid such warnings, make sure to rebuild
1100 the kernel toolchain (or world). Make sure that you have r292078 or
1101 later when trying to build 292077 or later before rebuilding.
1104 Debug data files are now built by default with 'make buildworld' and
1105 installed with 'make installworld'. This facilitates debugging but
1106 requires more disk space both during the build and for the installed
1107 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1111 r291527 changed the internal interface between the nfsd.ko and
1112 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1113 __FreeBSD_version has been bumped because of this.
1116 Add support for unicode collation strings leads to a change of
1117 order of files listed by ls(1) for example. To get back to the old
1118 behaviour, set LC_COLLATE environment variable to "C".
1120 Databases administrators will need to reindex their databases given
1121 collation results will be different.
1123 Due to a bug in install(1) it is recommended to remove the ancient
1124 locales before running make installworld.
1126 rm -rf /usr/share/locale/*
1129 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1130 libcrypto.so.7 or libssl.so.7 must be recompiled.
1133 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1134 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1135 should be replaced with isp_2400 and isp_2500 modules respectively.
1138 The build previously allowed using 'make -n' to not recurse into
1139 sub-directories while showing what commands would be executed, and
1140 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1141 and 'make -N' will not.
1144 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1145 and etcupdate will now use this file. A custom sendmail.cf is now
1146 updated via this mechanism rather than via installworld. If you had
1147 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1148 want to remove the exclusion or change it to "always install".
1149 /etc/mail/sendmail.cf is now managed the same way regardless of
1150 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1151 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1154 Compatibility shims for legacy ATA device names have been removed.
1155 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1156 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1157 environment variables, /dev/ad* and /dev/ar* symbolic links.
1160 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1161 Please see the 20141231 entry below for information about prerequisites
1162 and upgrading, if you are not already using clang 3.5.0 or higher.
1165 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1166 and renamed from .symbols to .debug. This reduces the size requirements
1167 on the boot partition or file system and provides consistency with
1168 userland debug files.
1170 When using the supported kernel installation method the
1171 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1172 as is done with /boot/kernel.
1174 Developers wishing to maintain the historical behavior of installing
1175 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1178 The wireless drivers had undergone changes that remove the 'parent
1179 interface' from the ifconfig -l output. The rc.d network scripts
1180 used to check presence of a parent interface in the list, so old
1181 scripts would fail to start wireless networking. Thus, etcupdate(3)
1182 or mergemaster(8) run is required after kernel update, to update your
1183 rc.d scripts in /etc.
1186 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1187 These configurations are now automatically interpreted as
1188 'scrub fragment reassemble'.
1191 Kernel-loadable modules for the random(4) device are back. To use
1192 them, the kernel must have
1195 options RANDOM_LOADABLE
1197 kldload(8) can then be used to load random_fortuna.ko
1198 or random_yarrow.ko. Please note that due to the indirect
1199 function calls that the loadable modules need to provide,
1200 the build-in variants will be slightly more efficient.
1202 The random(4) kernel option RANDOM_DUMMY has been retired due to
1203 unpopularity. It was not all that useful anyway.
1206 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1207 Control over building the ELF Tool Chain tools is now provided by
1208 the WITHOUT_TOOLCHAIN knob.
1211 The polarity of Pulse Per Second (PPS) capture events with the
1212 uart(4) driver has been corrected. Prior to this change the PPS
1213 "assert" event corresponded to the trailing edge of a positive PPS
1214 pulse and the "clear" event was the leading edge of the next pulse.
1216 As the width of a PPS pulse in a typical GPS receiver is on the
1217 order of 1 millisecond, most users will not notice any significant
1218 difference with this change.
1220 Anyone who has compensated for the historical polarity reversal by
1221 configuring a negative offset equal to the pulse width will need to
1222 remove that workaround.
1225 The default group assigned to /dev/dri entries has been changed
1226 from 'wheel' to 'video' with the id of '44'. If you want to have
1227 access to the dri devices please add yourself to the video group
1230 # pw groupmod video -m $USER
1233 The menu.rc and loader.rc files will now be replaced during
1234 upgrades. Please migrate local changes to menu.rc.local and
1235 loader.rc.local instead.
1238 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1239 strings and strip have been removed. The src.conf(5) knob
1240 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1243 As ZFS requires more kernel stack pages than is the default on some
1244 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1245 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1247 Please consider using 'options KSTACK_PAGES=X' where X is greater
1248 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1251 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1252 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1253 default, i.e., they will not contain "::". For example, instead
1254 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1255 to have a more specific match, such as different map entries for
1256 IPv6:0:0 vs IPv6:0. This change requires that configuration
1257 data (including maps, files, classes, custom ruleset, etc.) must
1258 use the same format, so make certain such configuration data is
1259 upgrading. As a very simple check search for patterns like
1260 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1261 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1262 the cf option UseCompressedIPv6Addresses.
1265 The default kernel entropy-processing algorithm is now
1266 Fortuna, replacing Yarrow.
1268 Assuming you have 'device random' in your kernel config
1269 file, the configurations allow a kernel option to override
1270 this default. You may choose *ONE* of:
1272 options RANDOM_YARROW # Legacy /dev/random algorithm.
1273 options RANDOM_DUMMY # Blocking-only driver.
1275 If you have neither, you get Fortuna. For most people,
1276 read no further, Fortuna will give a /dev/random that works
1277 like it always used to, and the difference will be irrelevant.
1279 If you remove 'device random', you get *NO* kernel-processed
1280 entropy at all. This may be acceptable to folks building
1281 embedded systems, but has complications. Carry on reading,
1282 and it is assumed you know what you need.
1284 *PLEASE* read random(4) and random(9) if you are in the
1285 habit of tweaking kernel configs, and/or if you are a member
1286 of the embedded community, wanting specific and not-usual
1287 behaviour from your security subsystems.
1289 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1290 random', you will NOT have a functioning /dev/random, and
1291 many cryptographic features will not work, including SSH.
1292 You may also find strange behaviour from the random(3) set
1293 of library functions, in particular sranddev(3), srandomdev(3)
1294 and arc4random(3). The reason for this is that the KERN_ARND
1295 sysctl only returns entropy if it thinks it has some to
1296 share, and with RANDOM_DUMMY or no 'device random' this
1300 An additional fix for the issue described in the 20150614 sendmail
1301 entry below has been committed in revision 284717.
1304 FreeBSD's old make (fmake) has been removed from the system. It is
1305 available as the devel/fmake port or via pkg install fmake.
1308 The fix for the issue described in the 20150614 sendmail entry
1309 below has been committed in revision 284436. The work
1310 around described in that entry is no longer needed unless the
1311 default setting is overridden by a confDH_PARAMETERS configuration
1312 setting of '5' or pointing to a 512 bit DH parameter file.
1315 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1316 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1317 and devel/kyua to version 0.20+ and adjust any calling code to work
1318 with Kyuafile and kyua.
1321 The import of openssl to address the FreeBSD-SA-15:10.openssl
1322 security advisory includes a change which rejects handshakes
1323 with DH parameters below 768 bits. sendmail releases prior
1324 to 8.15.2 (not yet released), defaulted to a 512 bit
1325 DH parameter setting for client connections. To work around
1326 this interoperability, sendmail can be configured to use a
1327 2048 bit DH parameter by:
1329 1. Edit /etc/mail/`hostname`.mc
1330 2. If a setting for confDH_PARAMETERS does not exist or
1331 exists and is set to a string beginning with '5',
1332 replace it with '2'.
1333 3. If a setting for confDH_PARAMETERS exists and is set to
1334 a file path, create a new file with:
1335 openssl dhparam -out /path/to/file 2048
1336 4. Rebuild the .cf file:
1337 cd /etc/mail/; make; make install
1338 5. Restart sendmail:
1339 cd /etc/mail/; make restart
1341 A sendmail patch is coming, at which time this file will be
1345 Generation of legacy formatted entries have been disabled by default
1346 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1347 entries were converted to use the new format by default when the new,
1348 machine independent format have been added and supported since FreeBSD
1351 Please see the pwd_mkdb(8) manual page for further details.
1354 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1355 20141231 entry below for information about prerequisites and upgrading,
1356 if you are not already using 3.5.0 or higher.
1359 TI platform code switched to using vendor DTS files and this update
1360 may break existing systems running on Beaglebone, Beaglebone Black,
1363 - dtb files should be regenerated/reinstalled. Filenames are the
1364 same but content is different now
1365 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1366 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1367 addressing scheme is now pin 25 on /dev/gpioc3.
1368 - Pandaboard: /etc/ttys should be updated, serial console device is
1369 now /dev/ttyu2, not /dev/ttyu0
1372 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1373 If you need the GNU extension from groff soelim(1), install groff
1374 from package: pkg install groff, or via ports: textproc/groff.
1377 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1378 defined in symlink(7); previously symlinks were silently ignored.
1381 The const qualifier has been removed from iconv(3) to comply with
1382 POSIX. The ports tree is aware of this from r384038 onwards.
1385 Libraries specified by LIBADD in Makefiles must have a corresponding
1386 DPADD_<lib> variable to ensure correct dependencies. This is now
1387 enforced in src.libnames.mk.
1390 From legacy ata(4) driver was removed support for SATA controllers
1391 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1392 Kernel modules ataahci and ataadaptec were removed completely,
1393 replaced by ahci and mvs modules respectively.
1396 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1397 the 20141231 entry below for information about prerequisites and
1398 upgrading, if you are not already using 3.5.0 or higher.
1401 The 32-bit PowerPC kernel has been changed to a position-independent
1402 executable. This can only be booted with a version of loader(8)
1403 newer than January 31, 2015, so make sure to update both world and
1404 kernel before rebooting.
1407 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1408 but before r278950, the RNG was not seeded properly. Immediately
1409 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1410 ssh keys or openssl keys) that were generated w/ a kernel from that
1411 range. This does not affect programs that directly used /dev/random
1412 or /dev/urandom. All userland uses of arc4random(3) are affected.
1415 The autofs(4) ABI was changed in order to restore binary compatibility
1416 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1417 with the new kernel.
1420 The powerpc64 kernel has been changed to a position-independent
1421 executable. This can only be booted with a new version of loader(8),
1422 so make sure to update both world and kernel before rebooting.
1425 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1426 only release, no new features have been added. Please see the 20141231
1427 entry below for information about prerequisites and upgrading, if you
1428 are not already using 3.5.0.
1431 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1432 taken from the ELF Tool Chain project rather than GNU binutils. They
1433 should be drop-in replacements, with the addition of arm64 support.
1434 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1435 binutils tools, if necessary. See 20150805 for updated information.
1438 The default Unbound configuration now enables remote control
1439 using a local socket. Users who have already enabled the
1440 local_unbound service should regenerate their configuration
1441 by running "service local_unbound setup" as root.
1444 The GNU texinfo and GNU info pages have been removed.
1445 To be able to view GNU info pages please install texinfo from ports.
1448 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1450 As of this release, a prerequisite for building clang, llvm and lldb is
1451 a C++11 capable compiler and C++11 standard library. This means that to
1452 be able to successfully build the cross-tools stage of buildworld, with
1453 clang as the bootstrap compiler, your system compiler or cross compiler
1454 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1455 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1458 On any standard FreeBSD 10.x or 11.x installation, where clang and
1459 libc++ are on by default (that is, on x86 or arm), this should work out
1462 On 9.x installations where clang is enabled by default, e.g. on x86 and
1463 powerpc, libc++ will not be enabled by default, so libc++ should be
1464 built (with clang) and installed first. If both clang and libc++ are
1465 missing, build clang first, then use it to build libc++.
1467 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1468 the instructions for 9.x above.
1470 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1471 default, and do not build clang.
1473 Many embedded systems are resource constrained, and will not be able to
1474 build clang in a reasonable time, or in some cases at all. In those
1475 cases, cross building bootable systems on amd64 is a workaround.
1477 This new version of clang introduces a number of new warnings, of which
1478 the following are most likely to appear:
1482 This warns in two cases, for both C and C++:
1483 * When the code is trying to take the absolute value of an unsigned
1484 quantity, which is effectively a no-op, and almost never what was
1485 intended. The code should be fixed, if at all possible. If you are
1486 sure that the unsigned quantity can be safely cast to signed, without
1487 loss of information or undefined behavior, you can add an explicit
1488 cast, or disable the warning.
1490 * When the code is trying to take an absolute value, but the called
1491 abs() variant is for the wrong type, which can lead to truncation.
1492 If you want to disable the warning instead of fixing the code, please
1493 make sure that truncation will not occur, or it might lead to unwanted
1496 -Wtautological-undefined-compare and
1497 -Wundefined-bool-conversion
1499 These warn when C++ code is trying to compare 'this' against NULL, while
1500 'this' should never be NULL in well-defined C++ code. However, there is
1501 some legacy (pre C++11) code out there, which actively abuses this
1502 feature, which was less strictly defined in previous C++ versions.
1504 Squid and openjdk do this, for example. The warning can be turned off
1505 for C++98 and earlier, but compiling the code in C++11 mode might result
1506 in unexpected behavior; for example, the parts of the program that are
1507 unreachable could be optimized away.
1510 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1511 kernel sources have been removed. The .h files remain, since some
1512 utilities include them. This will need to be fixed later.
1513 If "mount -t oldnfs ..." is attempted, it will fail.
1514 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1515 the utilities will report errors.
1518 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1519 directories to top level SUBDIR variable when their parent
1520 directory is included in LOCAL_DIRS. Users with build systems with
1521 such hierarchies and without SUBDIR entries in the parent
1522 directory Makefiles should add them or add the directories to
1526 faith(4) and faithd(8) have been removed from the base system. Faith
1527 has been obsolete for a very long time.
1530 vt(4), the new console driver, is enabled by default. It brings
1531 support for Unicode and double-width characters, as well as
1532 support for UEFI and integration with the KMS kernel video
1535 You may need to update your console settings in /etc/rc.conf,
1536 most probably the keymap. During boot, /etc/rc.d/syscons will
1537 indicate what you need to do.
1539 vt(4) still has issues and lacks some features compared to
1540 syscons(4). See the wiki for up-to-date information:
1541 https://wiki.freebsd.org/Newcons
1543 If you want to keep using syscons(4), you can do so by adding
1544 the following line to /boot/loader.conf:
1548 pjdfstest has been integrated into kyua as an opt-in test suite.
1549 Please see share/doc/pjdfstest/README for more details on how to
1553 gperf has been removed from the base system for architectures
1554 that use clang. Ports that require gperf will obtain it from the
1558 pjdfstest has been moved from tools/regression/pjdfstest to
1562 At svn r271982, The default linux compat kernel ABI has been adjusted
1563 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1564 update. If you wish to continue using the linux-f10 compat ports,
1565 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1566 encouraged to update their linux-compat packages to linux-c6 during
1567 their next update cycle.
1570 The ofwfb driver, used to provide a graphics console on PowerPC when
1571 using vt(4), no longer allows mmap() of all physical memory. This
1572 will prevent Xorg on PowerPC with some ATI graphics cards from
1573 initializing properly unless x11-servers/xorg-server is updated to
1577 The xdev targets have been converted to using TARGET and
1578 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1581 The default unbound configuration has been modified to address
1582 issues with reverse lookups on networks that use private
1583 address ranges. If you use the local_unbound service, run
1584 "service local_unbound setup" as root to regenerate your
1585 configuration, then "service local_unbound reload" to load the
1589 The GNU texinfo and GNU info pages are not built and installed
1590 anymore, WITH_INFO knob has been added to allow to built and install
1592 UPDATE: see 20150102 entry on texinfo's removal
1595 The GNU readline library is now an INTERNALLIB - that is, it is
1596 statically linked into consumers (GDB and variants) in the base
1597 system, and the shared library is no longer installed. The
1598 devel/readline port is available for third party software that
1602 The Itanium architecture (ia64) has been removed from the list of
1603 known architectures. This is the first step in the removal of the
1607 Commit r268115 has added NFSv4.1 server support, merged from
1608 projects/nfsv4.1-server. Since this includes changes to the
1609 internal interfaces between the NFS related modules, a full
1610 build of the kernel and modules will be necessary.
1611 __FreeBSD_version has been bumped.
1614 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1615 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1616 which differs from the behaviour controlled by this knob.)
1619 Maximal length of the serial number in CTL was increased from 16 to
1620 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1621 and ctld, need to be rebuilt to work with a new kernel.
1624 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1625 1 respectively to match the upstream numbers. They were out of
1626 sync because, when they were originally added to FreeBSD, the
1627 upstream versions were not respected. These libraries are private
1628 and not yet built by default, so renumbering them should be a
1629 non-issue. However, unclean source trees will yield broken test
1630 programs once the operator executes "make delete-old-libs" after a
1631 "make installworld".
1633 Additionally, the atf-sh binary was made private by moving it into
1634 /usr/libexec/. Already-built shell test programs will keep the
1635 path to the old binary so they will break after "make delete-old"
1638 If you are using WITH_TESTS=yes (not the default), wipe the object
1639 tree and rebuild from scratch to prevent spurious test failures.
1640 This is only needed once: the misnumbered libraries and misplaced
1641 binaries have been added to OptionalObsoleteFiles.inc so they will
1642 be removed during a clean upgrade.
1645 Clang and llvm have been upgraded to 3.4.1 release.
1648 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1649 be removed to avoid issues in the future (and has been added to
1653 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1654 past, it affected all builds that used the bsd.*.mk files. The old
1655 behavior was a bug, but people may have relied upon it. To get this
1656 behavior back, you can .include /etc/src.conf from /etc/make.conf
1657 (which is still global and isn't changed). This also changes the
1658 behavior of incremental builds inside the tree of individual
1659 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1660 Although this has survived make universe and some upgrade scenarios,
1661 other upgrade scenarios may have broken. At least one form of
1662 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1663 as well... In cases where MAKESYSPATH isn't working with this
1664 setting, you'll need to set it to the full path to your tree.
1666 One side effect of all this cleaning up is that bsd.compiler.mk
1667 is no longer implicitly included by bsd.own.mk. If you wish to
1668 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1672 The lindev device has been removed since /dev/full has been made a
1673 standard device. __FreeBSD_version has been bumped.
1676 The knob WITHOUT_VI was added to the base system, which controls
1677 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1678 in order to reorder files share/termcap and didn't build ex(1) as a
1679 build tool, so building/installing with WITH_VI is highly advised for
1680 build hosts for older releases.
1682 This issue has been fixed in stable/9 and stable/10 in r277022 and
1683 r276991, respectively.
1686 The YES_HESIOD knob has been removed. It has been obsolete for
1687 a decade. Please move to using WITH_HESIOD instead or your builds
1688 will silently lack HESIOD.
1691 The uart(4) driver has been changed with respect to its handling
1692 of the low-level console. Previously the uart(4) driver prevented
1693 any process from changing the baudrate or the CLOCAL and HUPCL
1694 control flags. By removing the restrictions, operators can make
1695 changes to the serial console port without having to reboot.
1696 However, when getty(8) is started on the serial device that is
1697 associated with the low-level console, a misconfigured terminal
1698 line in /etc/ttys will now have a real impact.
1699 Before upgrading the kernel, make sure that /etc/ttys has the
1700 serial console device configured as 3wire without baudrate to
1701 preserve the previous behaviour. E.g:
1702 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1705 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1706 to improve performance. To re-enable it, if needed, run rpcbind
1707 with command line option -W.
1710 Switched back to the GPL dtc compiler due to updates in the upstream
1711 dts files not being supported by the BSDL dtc compiler. You will need
1712 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1713 may result while building dtb files during a kernel build if you fail
1714 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1717 Clang and llvm have been upgraded to 3.4 release.
1720 The nve(4) driver has been removed. Please use the nfe(4) driver
1721 for NVIDIA nForce MCP Ethernet adapters instead.
1724 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1725 This could cause certain C++ applications using shared libraries built
1726 against the previous version of libc++ to crash. The incompatibility
1727 has now been fixed, but any C++ applications or shared libraries built
1728 between r261283 and r261801 should be recompiled.
1731 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1732 capability mode support. Please note that enabling the feature in
1733 kernel is still highly recommended.
1736 OpenSSH is now built with sandbox support, and will use sandbox as
1737 the default privilege separation method. This requires Capsicum
1738 capability mode support in kernel.
1741 The libelf and libdwarf libraries have been updated to newer
1742 versions from upstream. Shared library version numbers for
1743 these two libraries were bumped. Any ports or binaries
1744 requiring these two libraries should be recompiled.
1745 __FreeBSD_version is bumped to 1100006.
1748 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1749 instead of providing an explicit one, this would prevent such
1750 Makefile from providing its own Kyuafile in the future during
1751 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1752 intervention is needed to clean an objdir if you use NO_CLEAN:
1753 # find /usr/obj -name Kyuafile | xargs rm -f
1756 The behavior of gss_pseudo_random() for the krb5 mechanism
1757 has changed, for applications requesting a longer random string
1758 than produced by the underlying enctype's pseudo-random() function.
1759 In particular, the random string produced from a session key of
1760 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1761 be different at the 17th octet and later, after this change.
1762 The counter used in the PRF+ construction is now encoded as a
1763 big-endian integer in accordance with RFC 4402.
1764 __FreeBSD_version is bumped to 1100004.
1767 The WITHOUT_ATF build knob has been removed and its functionality
1768 has been subsumed into the more generic WITHOUT_TESTS. If you were
1769 using the former to disable the build of the ATF libraries, you
1770 should change your settings to use the latter.
1773 The default version of mtree is nmtree which is obtained from
1774 NetBSD. The output is generally the same, but may vary
1775 slightly. If you found you need identical output adding
1776 "-F freebsd9" to the command line should do the trick. For the
1777 time being, the old mtree is available as fmtree.
1780 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1781 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1782 1.1.4_8 and verify bsdyml not linked in, before running "make
1784 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1786 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1789 The stable/10 branch has been created in subversion from head
1796 Avoid using make -j when upgrading. While generally safe, there are
1797 sometimes problems using -j to upgrade. If your upgrade fails with
1798 -j, please try again without -j. From time to time in the past there
1799 have been problems using -j with buildworld and/or installworld. This
1800 is especially true when upgrading between "distant" versions (eg one
1801 that cross a major release boundary or several minor releases, or when
1802 several months have passed on the -current branch).
1804 Sometimes, obscure build problems are the result of environment
1805 poisoning. This can happen because the make utility reads its
1806 environment when searching for values for global variables. To run
1807 your build attempts in an "environmental clean room", prefix all make
1808 commands with 'env -i '. See the env(1) manual page for more details.
1810 When upgrading from one major version to another it is generally best to
1811 upgrade to the latest code in the currently installed branch first, then
1812 do an upgrade to the new branch. This is the best-tested upgrade path,
1813 and has the highest probability of being successful. Please try this
1814 approach if you encounter problems with a major version upgrade. Since
1815 the stable 4.x branch point, one has generally been able to upgrade from
1816 anywhere in the most recent stable branch to head / current (or even the
1817 last couple of stable branches). See the top of this file when there's
1820 When upgrading a live system, having a root shell around before
1821 installing anything can help undo problems. Not having a root shell
1822 around can lead to problems if pam has changed too much from your
1823 starting point to allow continued authentication after the upgrade.
1825 This file should be read as a log of events. When a later event changes
1826 information of a prior event, the prior event should not be deleted.
1827 Instead, a pointer to the entry with the new information should be
1828 placed in the old entry. Readers of this file should also sanity check
1829 older entries before relying on them blindly. Authors of new entries
1830 should write them with this in mind.
1834 When upgrading the boot ZFS pool to a new version, always follow
1837 1.) recompile and reinstall the ZFS boot loader and boot block
1838 (this is part of "make buildworld" and "make installworld")
1840 2.) update the ZFS boot block on your boot drive
1842 The following example updates the ZFS boot block on the first
1843 partition (freebsd-boot) of a GPT partitioned drive ada0:
1844 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1846 Non-boot pools do not need these updates.
1850 If you are updating from a prior version of FreeBSD (even one just
1851 a few days old), you should follow this procedure. It is the most
1852 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1854 make kernel-toolchain
1855 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1856 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1858 To test a kernel once
1859 ---------------------
1860 If you just want to boot a kernel once (because you are not sure
1861 if it works, or if you want to boot a known bad kernel to provide
1862 debugging information) run
1863 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1864 nextboot -k testkernel
1866 To rebuild everything and install it on the current system.
1867 -----------------------------------------------------------
1868 # Note: sometimes if you are running current you gotta do more than
1869 # is listed here if you are upgrading from a really old current.
1871 <make sure you have good level 0 dumps>
1873 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1874 make installkernel KERNCONF=YOUR_KERNEL_HERE
1876 <reboot in single user> [3]
1883 To cross-install current onto a separate partition
1884 --------------------------------------------------
1885 # In this approach we use a separate partition to hold
1886 # current's root, 'usr', and 'var' directories. A partition
1887 # holding "/", "/usr" and "/var" should be about 2GB in
1890 <make sure you have good level 0 dumps>
1893 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1894 <maybe newfs current's root partition>
1895 <mount current's root partition on directory ${CURRENT_ROOT}>
1896 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1897 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1898 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1899 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1900 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1901 <reboot into current>
1902 <do a "native" rebuild/install as described in the previous section>
1903 <maybe install compatibility libraries from ports/misc/compat*>
1907 To upgrade in-place from stable to current
1908 ----------------------------------------------
1909 <make sure you have good level 0 dumps>
1911 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1912 make installkernel KERNCONF=YOUR_KERNEL_HERE
1914 <reboot in single user> [3]
1921 Make sure that you've read the UPDATING file to understand the
1922 tweaks to various things you need. At this point in the life
1923 cycle of current, things change often and you are on your own
1924 to cope. The defaults can also change, so please read ALL of
1925 the UPDATING entries.
1927 Also, if you are tracking -current, you must be subscribed to
1928 freebsd-current@freebsd.org. Make sure that before you update
1929 your sources that you have read and understood all the recent
1930 messages there. If in doubt, please track -stable which has
1931 much fewer pitfalls.
1933 [1] If you have third party modules, such as vmware, you
1934 should disable them at this point so they don't crash your
1937 [3] From the bootblocks, boot -s, and then do
1941 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
1942 cd src # full path to source
1943 adjkerntz -i # if CMOS is wall time
1944 Also, when doing a major release upgrade, it is required that
1945 you boot into single user mode to do the installworld.
1947 [4] Note: This step is non-optional. Failure to do this step
1948 can result in a significant reduction in the functionality of the
1949 system. Attempting to do it by hand is not recommended and those
1950 that pursue this avenue should read this file carefully, as well
1951 as the archives of freebsd-current and freebsd-hackers mailing lists
1952 for potential gotchas. The -U option is also useful to consider.
1953 See mergemaster(8) for more information.
1955 [5] Usually this step is a no-op. However, from time to time
1956 you may need to do this if you get unknown user in the following
1957 step. It never hurts to do it all the time. You may need to
1958 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1959 install) after the buildworld before this step if you last updated
1960 from current before 20130425 or from -stable before 20130430.
1962 [6] This only deletes old files and directories. Old libraries
1963 can be deleted by "make delete-old-libs", but you have to make
1964 sure that no program is using those libraries anymore.
1966 [8] The new kernel must be able to run existing binaries used by an
1967 installworld. When upgrading across major versions, the new kernel's
1968 configuration must include the correct COMPAT_FREEBSD<n> option for
1969 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
1970 to do so may leave you with a system that is hard to boot to recover. A
1971 GENERIC kernel will include suitable compatibility options to run
1972 binaries from older branches. Note that the ability to run binaries
1973 from unsupported branches is not guaranteed.
1975 Make sure that you merge any new devices from GENERIC since the
1976 last time you updated your kernel config file. Options also
1977 change over time, so you may need to adjust your custom kernels
1980 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1981 "?=" instead of the "=" assignment operator, so that buildworld can
1982 override the CPUTYPE if it needs to.
1984 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1985 not on the command line, or in /etc/make.conf. buildworld will
1986 warn if it is improperly defined.
1989 This file contains a list, in reverse chronological order, of major
1990 breakages in tracking -current. It is not guaranteed to be a complete
1991 list of such breakages, and only contains entries since September 23, 2011.
1992 If you need to see UPDATING entries from before that date, you will need
1993 to fetch an UPDATING file from an older FreeBSD release.
1995 Copyright information:
1997 Copyright 1998-2009 M. Warner Losh.
1999 Redistribution, publication, translation and use, with or without
2000 modification, in full or in part, in any form or format of this
2001 document are permitted without further permission from the author.
2003 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2004 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2005 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2006 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2007 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2008 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2009 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2010 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2011 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2012 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2013 POSSIBILITY OF SUCH DAMAGE.
2015 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob