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