1 Updating Information for FreeBSD stable/12 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.
20 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
21 been upgraded to 9.0.0. Please see the 20141231 entry below for
22 information about prerequisites and upgrading, if you are not already
23 using clang 3.5.0 or higher.
26 The nctgpio and wbwd drivers have been moved to the superio bus.
27 If you have one of these drivers in a kernel configuration, then
28 you should add device superio to it. If you use one of these drivers
29 as a module and you compile a custom set of modules, then you should
30 add superio to the set.
33 The tap(4) driver has been folded into tun(4), and the module has been
34 renamed to tuntap. You should update any kld_list="if_tap" or
35 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
36 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
37 module instead, and "device tap" or "device tun" entries in kernel
38 config files to select the tuntap device instead.
41 ntpd no longer by default locks its pages in memory, allowing them
42 to be paged out by the kernel. Use rlimit memlock to restore
43 historic BSD behaviour. For example, add "rlimit memlock 32"
44 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
47 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
48 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
49 been removed from mount_fusefs(8). You can safely remove them from
50 your scripts, because they had no effect.
52 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
53 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
54 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
55 sysctls have been removed. If you felt the need to set any of them to
56 a non-default value, please tell asomers@FreeBSD.org why.
59 The fuse(4) module has been renamed to fusefs(4) for consistency with
60 other filesystems. You should update any kld_load="fuse" entries in
61 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
62 "options FUSE" enties in kernel config files.
65 Default permissions on the /var/account/acct file (and copies of it
66 rotated by periodic daily scripts) are changed from 0644 to 0640
67 because the file contains sensitive information that should not be
68 world-readable. If the /var/account directory must be created by
69 rc.d/accounting, the mode used is now 0750. Admins who use the
70 accounting feature are encouraged to change the mode of an existing
71 /var/account directory to 0750 or 0700.
74 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
75 been upgraded to 8.0.1. Please see the 20141231 entry below for
76 information about prerequisites and upgrading, if you are not already
77 using clang 3.5.0 or higher.
80 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
81 functionality needed for the RETPOLINE option should work properly
82 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
85 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
86 8.0.0. Please see the 20141231 entry below for information about
87 prerequisites and upgrading, if you are not already using clang 3.5.0
91 The RETPOLINE option produces non-functional ifunc-using binaries
92 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
93 Once Clang 8 is merged it may be enabled again.
96 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
97 7.0.1. Please see the 20141231 entry below for information about
98 prerequisites and upgrading, if you are not already using clang 3.5.0
102 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
103 compiled into your custom kernel, add 'device xz' statement to the
107 Iflib is no longer unconditionally compiled into the kernel. Drivers
108 using iflib and statically compiled into the kernel, now require
109 the 'device iflib' config option. For the same drivers loaded as
110 modules on kernels not having 'device iflib', the iflib.ko module
111 is loaded automatically.
114 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
115 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
116 servers that have vfs.nfsd.nfs_privport set will only allow mounts
117 from clients using a reserved port#. Since both the FreeBSD and Linux
118 NFSv4 clients use reserved port#s by default, this should not affect
122 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
123 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
124 it produces broken binaries when ifuncs are in use. Users needing
125 GNU ld should install the binutils port or package.
128 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
129 has been converted to a port (misc/ctm) and will be removed from
130 FreeBSD-13. A depreciation warning will be printed to stderr by
131 the ctm command, but the functionality will remain in base for all
135 The stable/12 branch has been created in subversion from head
139 Ports for the DRM modules have been simplified. Now, amd64 users should
140 just install the drm-kmod port. All others should install
143 Graphics hardware that's newer than about 2010 usually works with
144 drm-kmod. For hardware older than 2013, however, some users will need
145 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
146 than 2008 usually only works in drm-legacy-kmod. The graphics team can
147 only commit to hardware made since 2013 due to the complexity of the
148 market and difficulty to test all the older cards effectively. If you
149 have hardware supported by drm-kmod, you are strongly encouraged to use
150 that as you will get better support.
152 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
153 elsewhere, the drm and drm2 modules will be eliminated from the src base
154 soon (with a limited exception for arm). Please update to the package asap
155 and report any issues to x11@freebsd.org.
157 Generally, anybody using the drm*-kmod packages should add
158 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
159 cross-threading surprises, especially with automatic driver
160 loading from X11 startup. These will become the defaults in 13-current
164 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
165 custom kernel and module loading configuration files must be updated
166 accordingly. Moreover, interfaces previous presented as ixlvN to the
167 system are now exposed as iavfN and network configuration files must
168 be adjusted as necessary.
171 OpenSSL has been updated to version 1.1.1. This update included
172 additional various API changes througout the base system. It is
173 important to rebuild third-party software after upgrading. The value
174 of __FreeBSD_version has been bumped accordingly.
177 The legacy DRM modules and drivers have now been added to the loader's
178 module blacklist, in favor of loading them with kld_list in rc.conf(5).
179 The module blacklist may be overridden with the loader.conf(5)
180 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
184 The cam(4) based nda(4) driver will be used over nvd(4) by default on
185 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
186 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
187 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
191 Reproducible build mode is now on by default, in preparation for
192 FreeBSD 12.0. This eliminates build metadata such as the user,
193 host, and time from the kernel (and uname), unless the working tree
194 corresponds to a modified checkout from a version control system.
195 The previous behavior can be obtained by setting the /etc/src.conf
196 knob WITHOUT_REPRODUCIBLE_BUILD.
199 The Yarrow CSPRNG has been removed from the kernel as it has not been
200 supported by its designers since at least 2003. Fortuna has been the
201 default since FreeBSD-11.
204 devctl freeze/thaw have gone into the tree, the rc scripts have been
205 updated to use them and devmatch has been changed. You should update
206 kernel, userland and rc scripts all at the same time.
209 The default interpreter has been switched from 4th to Lua.
210 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
211 interpreter. If you have custom FORTH code you will need to set
212 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
213 src.conf for the build. This will create default hard links between
214 loader and loader_4th instead of loader and loader_lua, the new default.
215 If you are using UEFI it will create the proper hard link to loader.efi.
217 bhyve uses userboot.so. It remains 4th-only until some issues are solved
218 regarding coexisting with multiple versions of FreeBSD are resolved.
221 ls(1) now respects the COLORTERM environment variable used in other
222 systems and software to indicate that a colored terminal is both
223 supported and desired. If ls(1) is suddenly emitting colors, they may
224 be disabled again by either removing the unwanted COLORTERM from your
225 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
226 may not be observed in a future release.
229 The default pager for most commands has been changed to "less". To
230 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
234 The jedec_ts(4) driver has been removed. A superset of its functionality
235 is available in the jedec_dimm(4) driver, and the manpage for that
236 driver includes migration instructions. If you have "device jedec_ts"
237 in your kernel configuration file, it must be removed.
240 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
241 This should have no effect if the kernel is booted via BIOS/legacy boot.
242 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
243 has a buggy firmware that prevents a successful boot due to use of
247 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
248 support has been removed from the tree. These ports were
249 obsolete and/or known to be broken for many years.
252 loader.efi has been augmented to participate more fully in the
253 UEFI boot manager protocol. loader.efi will now look at the
254 BootXXXX environment variable to determine if a specific kernel
255 or root partition was specified. XXXX is derived from BootCurrent.
256 efibootmgr(8) manages these standard UEFI variables.
259 zfsloader's functionality has now been folded into loader.
260 zfsloader is no longer necessary once you've updated your
261 boot blocks. For a transition period, we will install a
262 hardlink for zfsloader to loader to allow a smooth transition
263 until the boot blocks can be updated (hard link because old
264 zfs boot blocks don't understand symlinks).
267 ARM64 now have efifb support, if you want to have serial console
268 on your arm64 board when an screen is connected and the bootloader
269 setup a frambuffer for us to use, just add :
273 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
274 an screen connected as the firmware will setup a framebuffer are that
275 u-boot will expose as an EFI framebuffer.
278 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
279 or take steps to update /etc/passwd before doing installworld on
280 existing systems. Do not skip the "mergemaster -Fp" step before
281 installworld, as described in the update procedures near the bottom
282 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
283 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
284 the ntp config file contain options that change file/dir locations.
285 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
286 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
287 taking steps to ensure that all required files/dirs are accessible
291 Big endian arm support has been removed.
294 The static environment setup in kernel configs is no longer mutually
295 exclusive with the loader(8) environment by default. In order to
296 restore the previous default behavior of disabling the loader(8)
297 environment if a static environment is present, you must specify
298 loader_env.disabled=1 in the static environment.
301 The ABI of syscalls used by management tools like sockstat and
302 netstat has been broken to allow 32-bit binaries to work on
303 64-bit kernels without modification. These programs will need
304 to match the kernel in order to function. External programs may
305 require minor modifications to accommodate a change of type in
306 structures from pointers to 64-bit virtual addresses.
309 On i386 and amd64 atomics are now inlined. Out of tree modules using
310 atomics will need to be rebuilt.
313 The '%I' format in the kern.corefile sysctl limits the number of
314 core files that a process can generate to the number stored in the
315 debug.ncores sysctl. The '%I' format is replaced by the single digit
316 index. Previously, if all indexes were taken the kernel would overwrite
317 only a core file with the highest index in a filename.
318 Currently the system will create a new core file if there is a free
319 index or if all slots are taken it will overwrite the oldest one.
322 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
323 6.0.1. Please see the 20141231 entry below for information about
324 prerequisites and upgrading, if you are not already using clang 3.5.0
328 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
329 needed to be changed to work with it. This change was made with r335763
330 and requires a mergemaster / etcupdate / etc to update the installed file.
333 r334930 changed the interface between the NFS modules, so they all
334 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
337 As of r334391 lld is the default amd64 system linker; it is installed
338 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
342 The kernel / userland interface for devinfo changed, so you'll
343 need a new kernel and userland as a pair for it to work (rebuilding
344 lib/libdevinfo is all that's required). devinfo and devmatch will
345 not work, but everything else will when there's a mismatch.
348 The on-disk format for hwpmc callchain records has changed to include
349 threadid corresponding to a given record. This changes the field offsets
350 and thus requires that libpmcstat be rebuilt before using a kernel
354 The vxge(4) driver has been removed. This driver was introduced into
355 HEAD one week before the Exar left the Ethernet market and is not
356 known to be used. If you have device vxge in your kernel config file
360 The amd64 kernel now requires a ld that supports ifunc to produce a
361 working kernel, either lld or a newer binutils. lld is built by default
362 on amd64, and the 'buildkernel' target uses it automatically. However,
363 it is not the default linker, so building the kernel the traditional
364 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
365 binutils port/package). lld will soon be default, and this requirement
368 NOTE: As of r334391 lld is the default system linker on amd64, and no
369 workaround is necessary.
372 The nxge(4) driver has been removed. This driver was for PCI-X 10g
373 cards made by s2io/Neterion. The company was aquired by Exar and
374 no longer sells or supports Ethernet products. If you have device
375 nxge in your kernel config file it must be removed.
378 The tz database (tzdb) has been updated to 2018e. This version more
379 correctly models time stamps in time zones with negative DST such as
380 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
381 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
382 time zone abbreviations and the tm_isdst flag.
385 The ixgb(4) driver has been removed. This driver was for an early and
386 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
387 quickly shifted to the long lived ixgbe family. If you have device
388 ixgb in your kernel config file it must be removed.
391 The lmc(4) driver has been removed. This was a WAN interface
392 card that was already reportedly rare in 2003, and had an ambiguous
393 license. If you have device lmc in your kernel config file it must
397 Support for Arcnet networks has been removed. If you have device
398 arcnet or device cm in your kernel config file they must be
402 Support for FDDI networks has been removed. If you have device
403 fddi or device fpa in your kernel config file they must be
407 In addition to supporting RFC 3164 formatted messages, the
408 syslogd(8) service is now capable of parsing RFC 5424 formatted
409 log messages. The main benefit of using RFC 5424 is that clients
410 may now send log messages with timestamps containing year numbers,
411 microseconds and time zone offsets.
413 Similarly, the syslog(3) C library function has been altered to
414 send RFC 5424 formatted messages to the local system logging
415 daemon. On systems using syslogd(8), this change should have no
416 negative impact, as long as syslogd(8) and the C library are
417 updated at the same time. On systems using a different system
418 logging daemon, it may be necessary to make configuration
419 adjustments, depending on the software used.
421 When using syslog-ng, add the 'syslog-protocol' flag to local
422 input sources to enable parsing of RFC 5424 formatted messages:
425 unix-dgram("/var/run/log" flags(syslog-protocol));
428 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
429 of the 'imuxsock' module to let messages be processed by the
430 regular RFC 3164/5424 parsing pipeline:
432 module(load="imuxsock" SysSock.UseSpecialParser="off")
434 Do note that these changes only affect communication between local
435 applications and syslogd(8). The format that syslogd(8) uses to
436 store messages on disk or forward messages to other systems
437 remains unchanged. syslogd(8) still uses RFC 3164 for these
438 purposes. Options to customize this behaviour will be added in the
439 future. Utilities that process log files stored in /var/log are
440 thus expected to continue to function as before.
442 __FreeBSD_version has been incremented to 1200061 to denote this
446 Support for token ring networks has been removed. If you
447 have "device token" in your kernel config you should remove
448 it. No device drivers supported token ring.
451 makefs was modified to be able to tag ISO9660 El Torito boot catalog
452 entries as EFI instead of overloading the i386 tag as done previously.
453 The amd64 mkisoimages.sh script used to build amd64 ISO images for
454 release was updated to use this. This may mean that makefs must be
455 updated before "make cdrom" can be run in the release directory. This
456 should be as simple as:
458 $ cd $SRCDIR/usr.sbin/makefs
459 $ make depend all install
462 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
463 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
464 Co-existance for the transition period will come shortly. Booting is a
465 complex environment and test coverage for Lua-enabled loaders has been
466 thin, so it would be prudent to assume it might not work and make
467 provisions for backup boot methods.
470 devmatch functionality has been turned on in devd. It will automatically
471 load drivers for unattached devices. This may cause unexpected drivers to
472 be loaded. Please report any problems to current@ and imp@freebsd.org.
475 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
476 6.0.0. Please see the 20141231 entry below for information about
477 prerequisites and upgrading, if you are not already using clang 3.5.0
481 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
482 This means it is used to link the kernel and userland libraries and
483 executables, but is not yet installed as /usr/bin/ld by default.
485 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
486 WITHOUT_LLD_BOOTSTRAP=yes
489 On i386, pmtimer has been removed. Its functionality has been folded
490 into apm. It was a no-op on ACPI in current for a while now (but was still
491 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
492 from kernel config files.
495 The use of RSS hash from the network card aka flowid has been
496 disabled by default for lagg(4) as it's currently incompatible with
497 the lacp and loadbalance protocols.
499 This can be re-enabled by setting the following in loader.conf:
500 net.link.lagg.default_use_flowid="1"
503 The SW_WATCHDOG option is no longer necessary to enable the
504 hardclock-based software watchdog if no hardware watchdog is
505 configured. As before, SW_WATCHDOG will cause the software
506 watchdog to be enabled even if a hardware watchdog is configured.
509 r326887 fixes the issue described in the 20171214 UPDATING entry.
510 r326888 flips the switch back to building GELI support always.
513 r362593 broke ZFS + GELI support for reasons unknown. However,
514 it also broke ZFS support generally, so GELI has been turned off
515 by default as the lesser evil in r326857. If you boot off ZFS and/or
516 GELI, it might not be a good time to update.
519 PowerPC users must update loader(8) by rebuilding world before
520 installing a new kernel, as the protocol connecting them has
521 changed. Without the update, loader metadata will not be passed
522 successfully to the kernel and users will have to enter their
523 root partition at the kernel mountroot prompt to continue booting.
524 Newer versions of loader can boot old kernels without issue.
527 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
528 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
529 to WITH/OUT_LOADER_GELI.
532 The naive and non-compliant support of posix_fallocate(2) in ZFS
533 has been removed as of r325320. The system call now returns EINVAL
534 when used on a ZFS file. Although the new behavior complies with the
535 standard, some consumers are not prepared to cope with it.
536 One known victim is lld prior to r325420.
539 Building in a FreeBSD src checkout will automatically create object
540 directories now rather than store files in the current directory if
541 'make obj' was not ran. Calling 'make obj' is no longer necessary.
542 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
543 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
547 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
548 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
549 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
550 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
551 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
552 The UNIFIED_OBJDIR option is a transitional feature that will be
553 removed for 12.0 release; please migrate to the new format for any
554 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
555 than hardcoding paths.
558 The native-xtools target no longer installs the files by default to the
559 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
560 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
563 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
564 options are changing from controlling the build if defined / undefined
565 to controlling the build with explicit 'yes' or 'no' values. They will
566 shift to WITH/WITHOUT options to match other options in the system.
569 libstand has turned into a private library for sys/boot use only.
570 It is no longer supported as a public interface outside of sys/boot.
573 The arm port has split armv6 into armv6 and armv7. armv7 is now
574 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
575 and are running a kernel from before r324363, you will need to add
576 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
579 When building multiple kernels using KERNCONF, non-existent KERNCONF
580 files will produce an error and buildkernel will fail. Previously
581 missing KERNCONF files silently failed giving no indication as to
582 why, only to subsequently discover during installkernel that the
583 desired kernel was never built in the first place.
586 The default serial number format for CTL LUNs has changed. This will
587 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
588 or iSCSI clients care about their LUNs' serial numbers. Users who
589 require serial number stability should hardcode serial numbers in
593 For 32-bit arm compiled for hard-float support, soft-floating point
594 binaries now always get their shared libraries from
595 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
596 /usr/libsoft also existed). Only users with a hard-float ld.so, but
597 soft-float everything else should be affected.
600 The geli password typed at boot is now hidden. To restore the previous
601 behavior, see geli(8) for configuration options.
604 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
605 sysctl values. Minor nit, but requires a rebuild of both world/kernel
609 "make check" behavior (made in ^/head@r295380) has been changed to
610 execute from a limited sandbox, as opposed to executing from
614 - The "beforecheck" and "aftercheck" targets are now specified.
615 - ${CHECKDIR} (added in commit noted above) has been removed.
616 - Legacy behavior can be enabled by setting
617 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
619 If the limited sandbox mode is enabled, "make check" will execute
620 "make distribution", then install, execute the tests, and clean up the
621 sandbox if successful.
623 The "make distribution" and "make install" targets are typically run as
624 root to set appropriate permissions and ownership at installation time.
625 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
626 environment if executing "make check" with limited sandbox mode using
627 an unprivileged user.
630 Since the switch to GPT disk labels, fsck for UFS/FFS has been
631 unable to automatically find alternate superblocks. As of r322297,
632 the information needed to find alternate superblocks has been
633 moved to the end of the area reserved for the boot block.
634 Filesystems created with a newfs of this vintage or later
635 will create the recovery information. If you have a filesystem
636 created prior to this change and wish to have a recovery block
637 created for your filesystem, you can do so by running fsck in
638 foreground mode (i.e., do not use the -p or -y options). As it
639 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
640 to which you should answer yes.
643 As of r321665, an NFSv4 server configuration that services
644 Kerberos mounts or clients that do not support the uid/gid in
645 owner/owner_group string capability, must explicitly enable
646 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
647 machine's /etc/rc.conf file.
650 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
651 Please see the 20141231 entry below for information about prerequisites
652 and upgrading, if you are not already using clang 3.5.0 or higher.
655 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
656 r-commands (rlogin, rsh, etc.) to be built with the base system.
659 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
660 a very major ABI incompatible change, so users of FreeBSD/powerpc must
661 be careful when performing source upgrades. It is best to run
662 'make installworld' from an alternate root system, either a live
663 CD/memory stick, or a temporary root partition. Additionally, all ports
664 must be recompiled. powerpc64 is largely unaffected, except in the case
665 of 32-bit compatibility. All 32-bit binaries will be affected.
668 Forward compatibility for the "ino64" project have been committed. This
669 will allow most new binaries to run on older kernels in a limited
670 fashion. This prevents many of the common foot-shooting actions in the
671 upgrade as well as the limited ability to roll back the kernel across
672 the ino64 upgrade. Complicated use cases may not work properly, though
673 enough simpler ones work to allow recovery in most situations.
676 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
677 if you require the GPL compiler.
680 The internal ABI used for communication between the NFS kernel modules
681 was changed by r320085, so __FreeBSD_version was bumped to
682 ensure all the NFS related modules are updated together.
685 The ABI of struct event was changed by extending the data
686 member to 64bit and adding ext fields. For upgrade, same
687 precautions as for the entry 20170523 "ino64" must be
691 The GNU roff toolchain has been removed from base. To render manpages
692 which are not supported by mandoc(1), man(1) can fallback on GNU roff
693 from ports (and recommends to install it).
694 To render roff(7) documents, consider using GNU roff from ports or the
695 heirloom doctools roff toolchain from ports via pkg install groff or
696 via pkg install heirloom-doctools.
699 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
700 smaller runtime footprint builds. This is useful for embedded systems
701 which only require one chipset support.
703 If you load it as a module, make sure this is in /boot/loader.conf:
707 This will load the HAL, all chip/RF backends and if_ath_pci.
708 If you have if_ath_pci in /boot/loader.conf, ensure it is after
709 if_ath or it will not load any HAL chipset support.
711 If you want to selectively load things (eg on ye cheape ARM/MIPS
712 platforms where RAM is at a premium) you should:
715 * load the chip modules in question
716 * load ath_rate, ath_dfs
718 * load if_ath_pci and/or if_ath_ahb depending upon your particular
719 bus bind type - this is where probe/attach is done.
721 For further comments/feedback, poke adrian@ .
724 The "ino64" 64-bit inode project has been committed, which extends
725 a number of types to 64 bits. Upgrading in place requires care and
726 adherence to the documented upgrade procedure.
728 If using a custom kernel configuration ensure that the
729 COMPAT_FREEBSD11 option is included (as during the upgrade the
730 system will be running the ino64 kernel with the existing world).
732 For the safest in-place upgrade begin by removing previous build
733 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
734 full procedure documented below under the heading "To rebuild
735 everything and install it on the current system." Specifically,
736 a reboot is required after installing the new kernel before
740 The NATM framework including the en(4), fatm(4), hatm(4), and
741 patm(4) devices has been removed. Consumers should plan a
742 migration before the end-of-life date for FreeBSD 11.
745 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
746 diff has not been implemented, if those are needed a newer version of
747 GNU diff is available via the diffutils package under the gdiff name.
750 As of r316810 for ipfilter, keep frags is no longer assumed when
751 keep state is specified in a rule. r316810 aligns ipfilter with
752 documentation in man pages separating keep frags from keep state.
753 This allows keep state to be specified without forcing keep frags
754 and allows keep frags to be specified independently of keep state.
755 To maintain previous behaviour, also specify keep frags with
756 keep state (as documented in ipf.conf.5).
759 arm64 builds now use the base system LLD 4.0.0 linker by default,
760 instead of requiring that the aarch64-binutils port or package be
761 installed. To continue using aarch64-binutils, set
762 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
765 The UDP optimization in entry 20160818 that added the sysctl
766 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
767 packets will no longer be treated as L3 broadcast packets.
770 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
771 use any explicitly assigned loopback address available in the jail
772 instead of using the first assigned address of the jail.
775 The ctl.ko module no longer implements the iSCSI target frontend:
776 cfiscsi.ko does instead.
778 If building cfiscsi.ko as a kernel module, the module can be loaded
779 via one of the following methods:
780 - `cfiscsi_load="YES"` in loader.conf(5).
781 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
782 - ctladm(8)/ctld(8), when compiled with iSCSI support
783 (`WITH_ISCSI=yes` in src.conf(5))
785 Please see cfiscsi(4) for more details.
788 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
789 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
790 same source (previously, the dependency of mmcsd.ko on mmc.ko was
791 missing, but mmcsd.ko now will refuse to load if it is incompatible
795 The syntax of ipfw(8) named states was changed to avoid ambiguity.
796 If you have used named states in the firewall rules, you need to modify
797 them after installworld and before rebooting. Now named states must
798 be prefixed with colon.
801 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
802 removed as the userland we provide cannot use them. The KMS version
803 (sys/dev/drm2) supports the same hardware.
806 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
807 Please see the 20141231 entry below for information about prerequisites
808 and upgrading, if you are not already using clang 3.5.0 or higher.
811 The code that provides support for ZFS .zfs/ directory functionality
812 has been reimplemented. It's not possible now to create a snapshot
813 by mkdir under .zfs/snapshot/. That should be the only user visible
817 EISA bus support has been removed. The WITH_EISA option is no longer
821 MCA bus support has been removed.
824 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
825 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
828 The EM_MULTIQUEUE kernel configuration option is deprecated now that
829 the em(4) driver conforms to iflib specifications.
832 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
833 IFLIB. If you have a custom kernel configuration that excludes em(4)
834 but you use igb(4), you need to re-add em(4) to your custom configuration.
837 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
838 Please see the 20141231 entry below for information about prerequisites
839 and upgrading, if you are not already using clang 3.5.0 or higher.
842 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
843 Please see the 20141231 entry below for information about prerequisites
844 and upgrading, if you are not already using clang 3.5.0 or higher.
847 The layout of the pmap structure has changed for powerpc to put the pmap
848 statistics at the front for all CPU variations. libkvm(3) and all tools
849 that link against it need to be recompiled.
852 isl(4) and cyapa(4) drivers now require a new driver,
853 chromebook_platform(4), to work properly on Chromebook-class hardware.
854 On other types of hardware the drivers may need to be configured using
855 device hints. Please see the corresponding manual pages for details.
858 The urtwn(4) driver was merged into rtwn(4) and now consists of
859 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
861 Also, firmware for RTL8188CE was renamed due to possible name
862 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
865 GNU rcs has been removed from base. It is available as packages:
866 - rcs: Latest GPLv3 GNU rcs version.
867 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
871 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
872 modules now requires that the kernel configuration contain the
873 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
876 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
877 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
880 Relocatable object files with the extension of .So have been renamed
881 to use an extension of .pico instead. The purpose of this change is
882 to avoid a name clash with shared libraries on case-insensitive file
883 systems. On those file systems, foo.So is the same file as foo.so.
886 GNU rcs has been turned off by default. It can (temporarily) be built
887 again by adding WITH_RCS knob in src.conf.
888 Otherwise, GNU rcs is available from packages:
889 - rcs: Latest GPLv3 GNU rcs version.
890 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
893 The backup_uses_rcs functionality has been removed from rc.subr.
896 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
897 two separate components, QUEUE_MACRO_DEBUG_TRACE and
898 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
899 QUEUE_MACRO_DEBUG behavior.
902 r304787 changed some ioctl interfaces between the iSCSI userspace
903 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
904 rebuilt to work with new kernels. __FreeBSD_version has been bumped
908 The UDP receive code has been updated to only treat incoming UDP
909 packets that were addressed to an L2 broadcast address as L3
910 broadcast packets. It is not expected that this will affect any
911 standards-conforming UDP application. The new behaviour can be
912 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
916 Remove the openbsd_poll system call.
917 __FreeBSD_version has been bumped because of this.
920 The stable/11 branch has been created from head@r302406.
923 The libc stub for the pipe(2) system call has been replaced with
924 a wrapper that calls the pipe2(2) system call and the pipe(2)
925 system call is now only implemented by the kernels that include
926 "options COMPAT_FREEBSD10" in their config file (this is the
927 default). Users should ensure that this option is enabled in
928 their kernel or upgrade userspace to r302092 before upgrading their
932 CAM will now strip leading spaces from SCSI disks' serial numbers.
933 This will affect users who create UFS filesystems on SCSI disks using
934 those disk's diskid device nodes. For example, if /etc/fstab
935 previously contained a line like
936 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
937 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
938 transforms like gmirror may also be affected. ZFS users should
942 The bitstring(3) API has been updated with new functionality and
943 improved performance. But it is binary-incompatible with the old API.
944 Objects built with the new headers may not be linked against objects
945 built with the old headers.
948 The brk and sbrk functions have been removed from libc on arm64.
949 Binutils from ports has been updated to not link to these
950 functions and should be updated to the latest version before
951 installing a new libc.
954 The armv6 port now defaults to hard float ABI. Limited support
955 for running both hardfloat and soft float on the same system
956 is available using the libraries installed with -DWITH_LIBSOFT.
957 This has only been tested as an upgrade path for installworld
958 and packages may fail or need manual intervention to run. New
959 packages will be needed.
961 To update an existing self-hosted armv6hf system, you must add
962 TARGET_ARCH=armv6 on the make command line for both the build
963 and the install steps.
966 Kernel modules compiled outside of a kernel build now default to
967 installing to /boot/modules instead of /boot/kernel. Many kernel
968 modules built this way (such as those in ports) already overrode
969 KMODDIR explicitly to install into /boot/modules. However,
970 manually building and installing a module from /sys/modules will
971 now install to /boot/modules instead of /boot/kernel.
974 The CAM I/O scheduler has been committed to the kernel. There should be
975 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
976 list of known rogues that claim support for this but actually corrupt
977 data is believed to be complete, be on the lookout for data
978 corruption. The known rogue list is believed to be complete:
980 o Crucial MX100, M550 drives with MU01 firmware.
981 o Micron M510 and M550 drives with MU01 firmware.
982 o Micron M500 prior to MU07 firmware
983 o Samsung 830, 840, and 850 all firmwares
984 o FCCT M500 all firmwares
986 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
987 with working NCQ TRIM. For Micron branded drives, see your sales rep for
988 updated firmware. Black listed drives will work correctly because these
989 drives work correctly so long as no NCQ TRIMs are sent to them. Given
990 this list is the same as found in Linux, it's believed there are no
991 other rogues in the market place. All other models from the above
994 To be safe, if you are at all concerned, you can quirk each of your
995 drives to prevent NCQ from being sent by setting:
996 kern.cam.ada.X.quirks="0x2"
997 in loader.conf. If the drive requires the 4k sector quirk, set the
1001 The FAST_DEPEND build option has been removed and its functionality is
1002 now the one true way. The old mkdep(1) style of 'make depend' has
1003 been removed. See 20160311 for further details.
1006 Resource range types have grown from unsigned long to uintmax_t. All
1007 drivers, and anything using libdevinfo, need to be recompiled.
1010 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1011 builds. It no longer runs mkdep(1) during 'make depend', and the
1012 'make depend' stage can safely be skipped now as it is auto ran
1013 when building 'make all' and will generate all SRCS and DPSRCS before
1014 building anything else. Dependencies are gathered at compile time with
1015 -MF flags kept in separate .depend files per object file. Users should
1016 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1017 stale .depend files.
1020 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1021 kernel modules. Therefore, if you load any kernel modules at boot time,
1022 please install the boot loaders after you install the kernel, but before
1026 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1027 make installkernel KERNCONF=YOUR_KERNEL_HERE
1028 make -C sys/boot install
1029 <reboot in single user>
1031 Then follow the usual steps, described in the General Notes section,
1035 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1036 see the 20141231 entry below for information about prerequisites and
1037 upgrading, if you are not already using clang 3.5.0 or higher.
1040 The AIO subsystem is now a standard part of the kernel. The
1041 VFS_AIO kernel option and aio.ko kernel module have been removed.
1042 Due to stability concerns, asynchronous I/O requests are only
1043 permitted on sockets and raw disks by default. To enable
1044 asynchronous I/O requests on all file types, set the
1045 vfs.aio.enable_unsafe sysctl to a non-zero value.
1048 The ELF object manipulation tool objcopy is now provided by the
1049 ELF Tool Chain project rather than by GNU binutils. It should be a
1050 drop-in replacement, with the addition of arm64 support. The
1051 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1052 to obtain the GNU version if necessary.
1055 Building ZFS pools on top of zvols is prohibited by default. That
1056 feature has never worked safely; it's always been prone to deadlocks.
1057 Using a zvol as the backing store for a VM guest's virtual disk will
1058 still work, even if the guest is using ZFS. Legacy behavior can be
1059 restored by setting vfs.zfs.vol.recursive=1.
1062 The NONE and HPN patches has been removed from OpenSSH. They are
1063 still available in the security/openssh-portable port.
1066 With the addition of ypldap(8), a new _ypldap user is now required
1067 during installworld. "mergemaster -p" can be used to add the user
1068 prior to installworld, as documented in the handbook.
1071 The tftp loader (pxeboot) now uses the option root-path directive. As a
1072 consequence it no longer looks for a pxeboot.4th file on the tftp
1073 server. Instead it uses the regular /boot infrastructure as with the
1077 The code to start recording plug and play data into the modules has
1078 been committed. While the old tools will properly build a new kernel,
1079 a number of warnings about "unknown metadata record 4" will be produced
1080 for an older kldxref. To avoid such warnings, make sure to rebuild
1081 the kernel toolchain (or world). Make sure that you have r292078 or
1082 later when trying to build 292077 or later before rebuilding.
1085 Debug data files are now built by default with 'make buildworld' and
1086 installed with 'make installworld'. This facilitates debugging but
1087 requires more disk space both during the build and for the installed
1088 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1092 r291527 changed the internal interface between the nfsd.ko and
1093 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1094 __FreeBSD_version has been bumped because of this.
1097 Add support for unicode collation strings leads to a change of
1098 order of files listed by ls(1) for example. To get back to the old
1099 behaviour, set LC_COLLATE environment variable to "C".
1101 Databases administrators will need to reindex their databases given
1102 collation results will be different.
1104 Due to a bug in install(1) it is recommended to remove the ancient
1105 locales before running make installworld.
1107 rm -rf /usr/share/locale/*
1110 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1111 libcrypto.so.7 or libssl.so.7 must be recompiled.
1114 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1115 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1116 should be replaced with isp_2400 and isp_2500 modules respectively.
1119 The build previously allowed using 'make -n' to not recurse into
1120 sub-directories while showing what commands would be executed, and
1121 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1122 and 'make -N' will not.
1125 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1126 and etcupdate will now use this file. A custom sendmail.cf is now
1127 updated via this mechanism rather than via installworld. If you had
1128 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1129 want to remove the exclusion or change it to "always install".
1130 /etc/mail/sendmail.cf is now managed the same way regardless of
1131 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1132 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1135 Compatibility shims for legacy ATA device names have been removed.
1136 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1137 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1138 environment variables, /dev/ad* and /dev/ar* symbolic links.
1141 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1142 Please see the 20141231 entry below for information about prerequisites
1143 and upgrading, if you are not already using clang 3.5.0 or higher.
1146 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1147 and renamed from .symbols to .debug. This reduces the size requirements
1148 on the boot partition or file system and provides consistency with
1149 userland debug files.
1151 When using the supported kernel installation method the
1152 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1153 as is done with /boot/kernel.
1155 Developers wishing to maintain the historical behavior of installing
1156 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1159 The wireless drivers had undergone changes that remove the 'parent
1160 interface' from the ifconfig -l output. The rc.d network scripts
1161 used to check presence of a parent interface in the list, so old
1162 scripts would fail to start wireless networking. Thus, etcupdate(3)
1163 or mergemaster(8) run is required after kernel update, to update your
1164 rc.d scripts in /etc.
1167 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1168 These configurations are now automatically interpreted as
1169 'scrub fragment reassemble'.
1172 Kernel-loadable modules for the random(4) device are back. To use
1173 them, the kernel must have
1176 options RANDOM_LOADABLE
1178 kldload(8) can then be used to load random_fortuna.ko
1179 or random_yarrow.ko. Please note that due to the indirect
1180 function calls that the loadable modules need to provide,
1181 the build-in variants will be slightly more efficient.
1183 The random(4) kernel option RANDOM_DUMMY has been retired due to
1184 unpopularity. It was not all that useful anyway.
1187 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1188 Control over building the ELF Tool Chain tools is now provided by
1189 the WITHOUT_TOOLCHAIN knob.
1192 The polarity of Pulse Per Second (PPS) capture events with the
1193 uart(4) driver has been corrected. Prior to this change the PPS
1194 "assert" event corresponded to the trailing edge of a positive PPS
1195 pulse and the "clear" event was the leading edge of the next pulse.
1197 As the width of a PPS pulse in a typical GPS receiver is on the
1198 order of 1 millisecond, most users will not notice any significant
1199 difference with this change.
1201 Anyone who has compensated for the historical polarity reversal by
1202 configuring a negative offset equal to the pulse width will need to
1203 remove that workaround.
1206 The default group assigned to /dev/dri entries has been changed
1207 from 'wheel' to 'video' with the id of '44'. If you want to have
1208 access to the dri devices please add yourself to the video group
1211 # pw groupmod video -m $USER
1214 The menu.rc and loader.rc files will now be replaced during
1215 upgrades. Please migrate local changes to menu.rc.local and
1216 loader.rc.local instead.
1219 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1220 strings and strip have been removed. The src.conf(5) knob
1221 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1224 As ZFS requires more kernel stack pages than is the default on some
1225 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1226 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1228 Please consider using 'options KSTACK_PAGES=X' where X is greater
1229 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1232 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1233 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1234 default, i.e., they will not contain "::". For example, instead
1235 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1236 to have a more specific match, such as different map entries for
1237 IPv6:0:0 vs IPv6:0. This change requires that configuration
1238 data (including maps, files, classes, custom ruleset, etc.) must
1239 use the same format, so make certain such configuration data is
1240 upgrading. As a very simple check search for patterns like
1241 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1242 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1243 the cf option UseCompressedIPv6Addresses.
1246 The default kernel entropy-processing algorithm is now
1247 Fortuna, replacing Yarrow.
1249 Assuming you have 'device random' in your kernel config
1250 file, the configurations allow a kernel option to override
1251 this default. You may choose *ONE* of:
1253 options RANDOM_YARROW # Legacy /dev/random algorithm.
1254 options RANDOM_DUMMY # Blocking-only driver.
1256 If you have neither, you get Fortuna. For most people,
1257 read no further, Fortuna will give a /dev/random that works
1258 like it always used to, and the difference will be irrelevant.
1260 If you remove 'device random', you get *NO* kernel-processed
1261 entropy at all. This may be acceptable to folks building
1262 embedded systems, but has complications. Carry on reading,
1263 and it is assumed you know what you need.
1265 *PLEASE* read random(4) and random(9) if you are in the
1266 habit of tweaking kernel configs, and/or if you are a member
1267 of the embedded community, wanting specific and not-usual
1268 behaviour from your security subsystems.
1270 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1271 random', you will NOT have a functioning /dev/random, and
1272 many cryptographic features will not work, including SSH.
1273 You may also find strange behaviour from the random(3) set
1274 of library functions, in particular sranddev(3), srandomdev(3)
1275 and arc4random(3). The reason for this is that the KERN_ARND
1276 sysctl only returns entropy if it thinks it has some to
1277 share, and with RANDOM_DUMMY or no 'device random' this
1281 An additional fix for the issue described in the 20150614 sendmail
1282 entry below has been committed in revision 284717.
1285 FreeBSD's old make (fmake) has been removed from the system. It is
1286 available as the devel/fmake port or via pkg install fmake.
1289 The fix for the issue described in the 20150614 sendmail entry
1290 below has been committed in revision 284436. The work
1291 around described in that entry is no longer needed unless the
1292 default setting is overridden by a confDH_PARAMETERS configuration
1293 setting of '5' or pointing to a 512 bit DH parameter file.
1296 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1297 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1298 and devel/kyua to version 0.20+ and adjust any calling code to work
1299 with Kyuafile and kyua.
1302 The import of openssl to address the FreeBSD-SA-15:10.openssl
1303 security advisory includes a change which rejects handshakes
1304 with DH parameters below 768 bits. sendmail releases prior
1305 to 8.15.2 (not yet released), defaulted to a 512 bit
1306 DH parameter setting for client connections. To work around
1307 this interoperability, sendmail can be configured to use a
1308 2048 bit DH parameter by:
1310 1. Edit /etc/mail/`hostname`.mc
1311 2. If a setting for confDH_PARAMETERS does not exist or
1312 exists and is set to a string beginning with '5',
1313 replace it with '2'.
1314 3. If a setting for confDH_PARAMETERS exists and is set to
1315 a file path, create a new file with:
1316 openssl dhparam -out /path/to/file 2048
1317 4. Rebuild the .cf file:
1318 cd /etc/mail/; make; make install
1319 5. Restart sendmail:
1320 cd /etc/mail/; make restart
1322 A sendmail patch is coming, at which time this file will be
1326 Generation of legacy formatted entries have been disabled by default
1327 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1328 entries were converted to use the new format by default when the new,
1329 machine independent format have been added and supported since FreeBSD
1332 Please see the pwd_mkdb(8) manual page for further details.
1335 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1336 20141231 entry below for information about prerequisites and upgrading,
1337 if you are not already using 3.5.0 or higher.
1340 TI platform code switched to using vendor DTS files and this update
1341 may break existing systems running on Beaglebone, Beaglebone Black,
1344 - dtb files should be regenerated/reinstalled. Filenames are the
1345 same but content is different now
1346 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1347 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1348 addressing scheme is now pin 25 on /dev/gpioc3.
1349 - Pandaboard: /etc/ttys should be updated, serial console device is
1350 now /dev/ttyu2, not /dev/ttyu0
1353 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1354 If you need the GNU extension from groff soelim(1), install groff
1355 from package: pkg install groff, or via ports: textproc/groff.
1358 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1359 defined in symlink(7); previously symlinks were silently ignored.
1362 The const qualifier has been removed from iconv(3) to comply with
1363 POSIX. The ports tree is aware of this from r384038 onwards.
1366 Libraries specified by LIBADD in Makefiles must have a corresponding
1367 DPADD_<lib> variable to ensure correct dependencies. This is now
1368 enforced in src.libnames.mk.
1371 From legacy ata(4) driver was removed support for SATA controllers
1372 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1373 Kernel modules ataahci and ataadaptec were removed completely,
1374 replaced by ahci and mvs modules respectively.
1377 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1378 the 20141231 entry below for information about prerequisites and
1379 upgrading, if you are not already using 3.5.0 or higher.
1382 The 32-bit PowerPC kernel has been changed to a position-independent
1383 executable. This can only be booted with a version of loader(8)
1384 newer than January 31, 2015, so make sure to update both world and
1385 kernel before rebooting.
1388 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1389 but before r278950, the RNG was not seeded properly. Immediately
1390 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1391 ssh keys or openssl keys) that were generated w/ a kernel from that
1392 range. This does not affect programs that directly used /dev/random
1393 or /dev/urandom. All userland uses of arc4random(3) are affected.
1396 The autofs(4) ABI was changed in order to restore binary compatibility
1397 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1398 with the new kernel.
1401 The powerpc64 kernel has been changed to a position-independent
1402 executable. This can only be booted with a new version of loader(8),
1403 so make sure to update both world and kernel before rebooting.
1406 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1407 only release, no new features have been added. Please see the 20141231
1408 entry below for information about prerequisites and upgrading, if you
1409 are not already using 3.5.0.
1412 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1413 taken from the ELF Tool Chain project rather than GNU binutils. They
1414 should be drop-in replacements, with the addition of arm64 support.
1415 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1416 binutils tools, if necessary. See 20150805 for updated information.
1419 The default Unbound configuration now enables remote control
1420 using a local socket. Users who have already enabled the
1421 local_unbound service should regenerate their configuration
1422 by running "service local_unbound setup" as root.
1425 The GNU texinfo and GNU info pages have been removed.
1426 To be able to view GNU info pages please install texinfo from ports.
1429 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1431 As of this release, a prerequisite for building clang, llvm and lldb is
1432 a C++11 capable compiler and C++11 standard library. This means that to
1433 be able to successfully build the cross-tools stage of buildworld, with
1434 clang as the bootstrap compiler, your system compiler or cross compiler
1435 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1436 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1439 On any standard FreeBSD 10.x or 11.x installation, where clang and
1440 libc++ are on by default (that is, on x86 or arm), this should work out
1443 On 9.x installations where clang is enabled by default, e.g. on x86 and
1444 powerpc, libc++ will not be enabled by default, so libc++ should be
1445 built (with clang) and installed first. If both clang and libc++ are
1446 missing, build clang first, then use it to build libc++.
1448 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1449 the instructions for 9.x above.
1451 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1452 default, and do not build clang.
1454 Many embedded systems are resource constrained, and will not be able to
1455 build clang in a reasonable time, or in some cases at all. In those
1456 cases, cross building bootable systems on amd64 is a workaround.
1458 This new version of clang introduces a number of new warnings, of which
1459 the following are most likely to appear:
1463 This warns in two cases, for both C and C++:
1464 * When the code is trying to take the absolute value of an unsigned
1465 quantity, which is effectively a no-op, and almost never what was
1466 intended. The code should be fixed, if at all possible. If you are
1467 sure that the unsigned quantity can be safely cast to signed, without
1468 loss of information or undefined behavior, you can add an explicit
1469 cast, or disable the warning.
1471 * When the code is trying to take an absolute value, but the called
1472 abs() variant is for the wrong type, which can lead to truncation.
1473 If you want to disable the warning instead of fixing the code, please
1474 make sure that truncation will not occur, or it might lead to unwanted
1477 -Wtautological-undefined-compare and
1478 -Wundefined-bool-conversion
1480 These warn when C++ code is trying to compare 'this' against NULL, while
1481 'this' should never be NULL in well-defined C++ code. However, there is
1482 some legacy (pre C++11) code out there, which actively abuses this
1483 feature, which was less strictly defined in previous C++ versions.
1485 Squid and openjdk do this, for example. The warning can be turned off
1486 for C++98 and earlier, but compiling the code in C++11 mode might result
1487 in unexpected behavior; for example, the parts of the program that are
1488 unreachable could be optimized away.
1491 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1492 kernel sources have been removed. The .h files remain, since some
1493 utilities include them. This will need to be fixed later.
1494 If "mount -t oldnfs ..." is attempted, it will fail.
1495 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1496 the utilities will report errors.
1499 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1500 directories to top level SUBDIR variable when their parent
1501 directory is included in LOCAL_DIRS. Users with build systems with
1502 such hierarchies and without SUBDIR entries in the parent
1503 directory Makefiles should add them or add the directories to
1507 faith(4) and faithd(8) have been removed from the base system. Faith
1508 has been obsolete for a very long time.
1511 vt(4), the new console driver, is enabled by default. It brings
1512 support for Unicode and double-width characters, as well as
1513 support for UEFI and integration with the KMS kernel video
1516 You may need to update your console settings in /etc/rc.conf,
1517 most probably the keymap. During boot, /etc/rc.d/syscons will
1518 indicate what you need to do.
1520 vt(4) still has issues and lacks some features compared to
1521 syscons(4). See the wiki for up-to-date information:
1522 https://wiki.freebsd.org/Newcons
1524 If you want to keep using syscons(4), you can do so by adding
1525 the following line to /boot/loader.conf:
1529 pjdfstest has been integrated into kyua as an opt-in test suite.
1530 Please see share/doc/pjdfstest/README for more details on how to
1534 gperf has been removed from the base system for architectures
1535 that use clang. Ports that require gperf will obtain it from the
1539 pjdfstest has been moved from tools/regression/pjdfstest to
1543 At svn r271982, The default linux compat kernel ABI has been adjusted
1544 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1545 update. If you wish to continue using the linux-f10 compat ports,
1546 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1547 encouraged to update their linux-compat packages to linux-c6 during
1548 their next update cycle.
1551 The ofwfb driver, used to provide a graphics console on PowerPC when
1552 using vt(4), no longer allows mmap() of all physical memory. This
1553 will prevent Xorg on PowerPC with some ATI graphics cards from
1554 initializing properly unless x11-servers/xorg-server is updated to
1558 The xdev targets have been converted to using TARGET and
1559 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1562 The default unbound configuration has been modified to address
1563 issues with reverse lookups on networks that use private
1564 address ranges. If you use the local_unbound service, run
1565 "service local_unbound setup" as root to regenerate your
1566 configuration, then "service local_unbound reload" to load the
1570 The GNU texinfo and GNU info pages are not built and installed
1571 anymore, WITH_INFO knob has been added to allow to built and install
1573 UPDATE: see 20150102 entry on texinfo's removal
1576 The GNU readline library is now an INTERNALLIB - that is, it is
1577 statically linked into consumers (GDB and variants) in the base
1578 system, and the shared library is no longer installed. The
1579 devel/readline port is available for third party software that
1583 The Itanium architecture (ia64) has been removed from the list of
1584 known architectures. This is the first step in the removal of the
1588 Commit r268115 has added NFSv4.1 server support, merged from
1589 projects/nfsv4.1-server. Since this includes changes to the
1590 internal interfaces between the NFS related modules, a full
1591 build of the kernel and modules will be necessary.
1592 __FreeBSD_version has been bumped.
1595 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1596 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1597 which differs from the behaviour controlled by this knob.)
1600 Maximal length of the serial number in CTL was increased from 16 to
1601 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1602 and ctld, need to be rebuilt to work with a new kernel.
1605 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1606 1 respectively to match the upstream numbers. They were out of
1607 sync because, when they were originally added to FreeBSD, the
1608 upstream versions were not respected. These libraries are private
1609 and not yet built by default, so renumbering them should be a
1610 non-issue. However, unclean source trees will yield broken test
1611 programs once the operator executes "make delete-old-libs" after a
1612 "make installworld".
1614 Additionally, the atf-sh binary was made private by moving it into
1615 /usr/libexec/. Already-built shell test programs will keep the
1616 path to the old binary so they will break after "make delete-old"
1619 If you are using WITH_TESTS=yes (not the default), wipe the object
1620 tree and rebuild from scratch to prevent spurious test failures.
1621 This is only needed once: the misnumbered libraries and misplaced
1622 binaries have been added to OptionalObsoleteFiles.inc so they will
1623 be removed during a clean upgrade.
1626 Clang and llvm have been upgraded to 3.4.1 release.
1629 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1630 be removed to avoid issues in the future (and has been added to
1634 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1635 past, it affected all builds that used the bsd.*.mk files. The old
1636 behavior was a bug, but people may have relied upon it. To get this
1637 behavior back, you can .include /etc/src.conf from /etc/make.conf
1638 (which is still global and isn't changed). This also changes the
1639 behavior of incremental builds inside the tree of individual
1640 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1641 Although this has survived make universe and some upgrade scenarios,
1642 other upgrade scenarios may have broken. At least one form of
1643 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1644 as well... In cases where MAKESYSPATH isn't working with this
1645 setting, you'll need to set it to the full path to your tree.
1647 One side effect of all this cleaning up is that bsd.compiler.mk
1648 is no longer implicitly included by bsd.own.mk. If you wish to
1649 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1653 The lindev device has been removed since /dev/full has been made a
1654 standard device. __FreeBSD_version has been bumped.
1657 The knob WITHOUT_VI was added to the base system, which controls
1658 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1659 in order to reorder files share/termcap and didn't build ex(1) as a
1660 build tool, so building/installing with WITH_VI is highly advised for
1661 build hosts for older releases.
1663 This issue has been fixed in stable/9 and stable/10 in r277022 and
1664 r276991, respectively.
1667 The YES_HESIOD knob has been removed. It has been obsolete for
1668 a decade. Please move to using WITH_HESIOD instead or your builds
1669 will silently lack HESIOD.
1672 The uart(4) driver has been changed with respect to its handling
1673 of the low-level console. Previously the uart(4) driver prevented
1674 any process from changing the baudrate or the CLOCAL and HUPCL
1675 control flags. By removing the restrictions, operators can make
1676 changes to the serial console port without having to reboot.
1677 However, when getty(8) is started on the serial device that is
1678 associated with the low-level console, a misconfigured terminal
1679 line in /etc/ttys will now have a real impact.
1680 Before upgrading the kernel, make sure that /etc/ttys has the
1681 serial console device configured as 3wire without baudrate to
1682 preserve the previous behaviour. E.g:
1683 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1686 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1687 to improve performance. To re-enable it, if needed, run rpcbind
1688 with command line option -W.
1691 Switched back to the GPL dtc compiler due to updates in the upstream
1692 dts files not being supported by the BSDL dtc compiler. You will need
1693 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1694 may result while building dtb files during a kernel build if you fail
1695 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1698 Clang and llvm have been upgraded to 3.4 release.
1701 The nve(4) driver has been removed. Please use the nfe(4) driver
1702 for NVIDIA nForce MCP Ethernet adapters instead.
1705 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1706 This could cause certain C++ applications using shared libraries built
1707 against the previous version of libc++ to crash. The incompatibility
1708 has now been fixed, but any C++ applications or shared libraries built
1709 between r261283 and r261801 should be recompiled.
1712 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1713 capability mode support. Please note that enabling the feature in
1714 kernel is still highly recommended.
1717 OpenSSH is now built with sandbox support, and will use sandbox as
1718 the default privilege separation method. This requires Capsicum
1719 capability mode support in kernel.
1722 The libelf and libdwarf libraries have been updated to newer
1723 versions from upstream. Shared library version numbers for
1724 these two libraries were bumped. Any ports or binaries
1725 requiring these two libraries should be recompiled.
1726 __FreeBSD_version is bumped to 1100006.
1729 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1730 instead of providing an explicit one, this would prevent such
1731 Makefile from providing its own Kyuafile in the future during
1732 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1733 intervention is needed to clean an objdir if you use NO_CLEAN:
1734 # find /usr/obj -name Kyuafile | xargs rm -f
1737 The behavior of gss_pseudo_random() for the krb5 mechanism
1738 has changed, for applications requesting a longer random string
1739 than produced by the underlying enctype's pseudo-random() function.
1740 In particular, the random string produced from a session key of
1741 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1742 be different at the 17th octet and later, after this change.
1743 The counter used in the PRF+ construction is now encoded as a
1744 big-endian integer in accordance with RFC 4402.
1745 __FreeBSD_version is bumped to 1100004.
1748 The WITHOUT_ATF build knob has been removed and its functionality
1749 has been subsumed into the more generic WITHOUT_TESTS. If you were
1750 using the former to disable the build of the ATF libraries, you
1751 should change your settings to use the latter.
1754 The default version of mtree is nmtree which is obtained from
1755 NetBSD. The output is generally the same, but may vary
1756 slightly. If you found you need identical output adding
1757 "-F freebsd9" to the command line should do the trick. For the
1758 time being, the old mtree is available as fmtree.
1761 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1762 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1763 1.1.4_8 and verify bsdyml not linked in, before running "make
1765 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1767 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1770 The stable/10 branch has been created in subversion from head
1777 Avoid using make -j when upgrading. While generally safe, there are
1778 sometimes problems using -j to upgrade. If your upgrade fails with
1779 -j, please try again without -j. From time to time in the past there
1780 have been problems using -j with buildworld and/or installworld. This
1781 is especially true when upgrading between "distant" versions (eg one
1782 that cross a major release boundary or several minor releases, or when
1783 several months have passed on the -current branch).
1785 Sometimes, obscure build problems are the result of environment
1786 poisoning. This can happen because the make utility reads its
1787 environment when searching for values for global variables. To run
1788 your build attempts in an "environmental clean room", prefix all make
1789 commands with 'env -i '. See the env(1) manual page for more details.
1791 When upgrading from one major version to another it is generally best to
1792 upgrade to the latest code in the currently installed branch first, then
1793 do an upgrade to the new branch. This is the best-tested upgrade path,
1794 and has the highest probability of being successful. Please try this
1795 approach if you encounter problems with a major version upgrade. Since
1796 the stable 4.x branch point, one has generally been able to upgrade from
1797 anywhere in the most recent stable branch to head / current (or even the
1798 last couple of stable branches). See the top of this file when there's
1801 When upgrading a live system, having a root shell around before
1802 installing anything can help undo problems. Not having a root shell
1803 around can lead to problems if pam has changed too much from your
1804 starting point to allow continued authentication after the upgrade.
1806 This file should be read as a log of events. When a later event changes
1807 information of a prior event, the prior event should not be deleted.
1808 Instead, a pointer to the entry with the new information should be
1809 placed in the old entry. Readers of this file should also sanity check
1810 older entries before relying on them blindly. Authors of new entries
1811 should write them with this in mind.
1815 When upgrading the boot ZFS pool to a new version, always follow
1818 1.) recompile and reinstall the ZFS boot loader and boot block
1819 (this is part of "make buildworld" and "make installworld")
1821 2.) update the ZFS boot block on your boot drive
1823 The following example updates the ZFS boot block on the first
1824 partition (freebsd-boot) of a GPT partitioned drive ada0:
1825 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1827 Non-boot pools do not need these updates.
1831 If you are updating from a prior version of FreeBSD (even one just
1832 a few days old), you should follow this procedure. It is the most
1833 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1835 make kernel-toolchain
1836 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1837 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1839 To test a kernel once
1840 ---------------------
1841 If you just want to boot a kernel once (because you are not sure
1842 if it works, or if you want to boot a known bad kernel to provide
1843 debugging information) run
1844 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1845 nextboot -k testkernel
1847 To rebuild everything and install it on the current system.
1848 -----------------------------------------------------------
1849 # Note: sometimes if you are running current you gotta do more than
1850 # is listed here if you are upgrading from a really old current.
1852 <make sure you have good level 0 dumps>
1854 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1855 make installkernel KERNCONF=YOUR_KERNEL_HERE
1857 <reboot in single user> [3]
1864 To cross-install current onto a separate partition
1865 --------------------------------------------------
1866 # In this approach we use a separate partition to hold
1867 # current's root, 'usr', and 'var' directories. A partition
1868 # holding "/", "/usr" and "/var" should be about 2GB in
1871 <make sure you have good level 0 dumps>
1874 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1875 <maybe newfs current's root partition>
1876 <mount current's root partition on directory ${CURRENT_ROOT}>
1877 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1878 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1879 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1880 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1881 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1882 <reboot into current>
1883 <do a "native" rebuild/install as described in the previous section>
1884 <maybe install compatibility libraries from ports/misc/compat*>
1888 To upgrade in-place from stable to current
1889 ----------------------------------------------
1890 <make sure you have good level 0 dumps>
1892 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1893 make installkernel KERNCONF=YOUR_KERNEL_HERE
1895 <reboot in single user> [3]
1902 Make sure that you've read the UPDATING file to understand the
1903 tweaks to various things you need. At this point in the life
1904 cycle of current, things change often and you are on your own
1905 to cope. The defaults can also change, so please read ALL of
1906 the UPDATING entries.
1908 Also, if you are tracking -current, you must be subscribed to
1909 freebsd-current@freebsd.org. Make sure that before you update
1910 your sources that you have read and understood all the recent
1911 messages there. If in doubt, please track -stable which has
1912 much fewer pitfalls.
1914 [1] If you have third party modules, such as vmware, you
1915 should disable them at this point so they don't crash your
1918 [3] From the bootblocks, boot -s, and then do
1923 adjkerntz -i # if CMOS is wall time
1924 Also, when doing a major release upgrade, it is required that
1925 you boot into single user mode to do the installworld.
1927 [4] Note: This step is non-optional. Failure to do this step
1928 can result in a significant reduction in the functionality of the
1929 system. Attempting to do it by hand is not recommended and those
1930 that pursue this avenue should read this file carefully, as well
1931 as the archives of freebsd-current and freebsd-hackers mailing lists
1932 for potential gotchas. The -U option is also useful to consider.
1933 See mergemaster(8) for more information.
1935 [5] Usually this step is a no-op. However, from time to time
1936 you may need to do this if you get unknown user in the following
1937 step. It never hurts to do it all the time. You may need to
1938 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1939 install) after the buildworld before this step if you last updated
1940 from current before 20130425 or from -stable before 20130430.
1942 [6] This only deletes old files and directories. Old libraries
1943 can be deleted by "make delete-old-libs", but you have to make
1944 sure that no program is using those libraries anymore.
1946 [8] The new kernel must be able to run existing binaries used by
1947 an installworld. When upgrading across major versions, the new
1948 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1949 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1950 binaries). Failure to do so may leave you with a system that is
1951 hard to boot to recover. A GENERIC kernel will include suitable
1952 compatibility options to run binaries from older branches.
1954 Make sure that you merge any new devices from GENERIC since the
1955 last time you updated your kernel config file.
1957 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1958 "?=" instead of the "=" assignment operator, so that buildworld can
1959 override the CPUTYPE if it needs to.
1961 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1962 not on the command line, or in /etc/make.conf. buildworld will
1963 warn if it is improperly defined.
1966 This file contains a list, in reverse chronological order, of major
1967 breakages in tracking -current. It is not guaranteed to be a complete
1968 list of such breakages, and only contains entries since September 23, 2011.
1969 If you need to see UPDATING entries from before that date, you will need
1970 to fetch an UPDATING file from an older FreeBSD release.
1972 Copyright information:
1974 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1976 Redistribution, publication, translation and use, with or without
1977 modification, in full or in part, in any form or format of this
1978 document are permitted without further permission from the author.
1980 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1981 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1982 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1983 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1984 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1985 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1986 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1987 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1988 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1989 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1990 POSSIBILITY OF SUCH DAMAGE.
1992 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob