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 resume code now notifies devd with the 'kernel' system
21 rather than the old 'kern' subsystem to be consistent with
22 other use. The old notification will be created as well, but
23 will be removed prior to FreeBSD 14.0.
26 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
27 been upgraded to 10.0.1. Please see the 20141231 entry below for
28 information about prerequisites and upgrading, if you are not already
29 using clang 3.5.0 or higher.
32 read(2) of a directory fd is now rejected by default. root may
33 re-enable it for the entire system with the
34 security.bsd.allow_read_dir sysctl(8) MIB.
36 It may be advised to setup aliases for grep to default to `-d skip` if
37 commonly non-recursively grepping a list that includes directories and
38 the potential for the resulting stderr output is not tolerable. Example
39 aliases are now installed, commented out, in /root/.cshrc.
42 Upstream DTS from Linux 5.6 was merged and they now have the SID
43 and THS (Secure ID controller and THermal Sensor) node present.
44 The DTB overlays have now been removed from the tree for the H3/H5 and
45 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
46 deal with upstream DTS. If you are using those overlays you need to
47 remove them from loader.conf and update the DTBs on the FAT partition.
50 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
51 been upgraded to 10.0.0. Please see the 20141231 entry below for
52 information about prerequisites and upgrading, if you are not already
53 using clang 3.5.0 or higher.
56 The root certificates of the Mozilla CA Certificate Store have been
57 imported into the base system and can be managed with the certctl(8)
58 utility. If you have installed the security/ca_root_nss port or package
59 with the ETCSYMLINK option (the default), be advised that there may be
60 differences between those included in the port and those included in
61 base due to differences in nss branch used as well as general update
62 frequency. Note also that certctl(8) cannot manage certs in the
63 format used by the security/ca_root_nss port.
66 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
67 been upgraded to 9.0.1. Please see the 20141231 entry below for
68 information about prerequisites and upgrading, if you are not already
69 using clang 3.5.0 or higher.
72 The nctgpio and wbwd drivers have been moved to the superio bus.
73 If you have one of these drivers in a kernel configuration, then
74 you should add device superio to it. If you use one of these drivers
75 as a module and you compile a custom set of modules, then you should
76 add superio to the set.
79 The tap(4) driver has been folded into tun(4), and the module has been
80 renamed to tuntap. You should update any kld_list="if_tap" or
81 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
82 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
83 module instead, and "device tap" or "device tun" entries in kernel
84 config files to select the tuntap device instead.
87 ntpd no longer by default locks its pages in memory, allowing them
88 to be paged out by the kernel. Use rlimit memlock to restore
89 historic BSD behaviour. For example, add "rlimit memlock 32"
90 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
93 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
94 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
95 been removed from mount_fusefs(8). You can safely remove them from
96 your scripts, because they had no effect.
98 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
99 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
100 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
101 sysctls have been removed. If you felt the need to set any of them to
102 a non-default value, please tell asomers@FreeBSD.org why.
105 The fuse(4) module has been renamed to fusefs(4) for consistency with
106 other filesystems. You should update any kld_load="fuse" entries in
107 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
108 "options FUSE" enties in kernel config files.
111 Default permissions on the /var/account/acct file (and copies of it
112 rotated by periodic daily scripts) are changed from 0644 to 0640
113 because the file contains sensitive information that should not be
114 world-readable. If the /var/account directory must be created by
115 rc.d/accounting, the mode used is now 0750. Admins who use the
116 accounting feature are encouraged to change the mode of an existing
117 /var/account directory to 0750 or 0700.
120 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
121 been upgraded to 8.0.1. Please see the 20141231 entry below for
122 information about prerequisites and upgrading, if you are not already
123 using clang 3.5.0 or higher.
126 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
127 functionality needed for the RETPOLINE option should work properly
128 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
131 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
132 8.0.0. Please see the 20141231 entry below for information about
133 prerequisites and upgrading, if you are not already using clang 3.5.0
137 The RETPOLINE option produces non-functional ifunc-using binaries
138 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
139 Once Clang 8 is merged it may be enabled again.
142 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
143 7.0.1. Please see the 20141231 entry below for information about
144 prerequisites and upgrading, if you are not already using clang 3.5.0
148 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
149 compiled into your custom kernel, add 'device xz' statement to the
153 Iflib is no longer unconditionally compiled into the kernel. Drivers
154 using iflib and statically compiled into the kernel, now require
155 the 'device iflib' config option. For the same drivers loaded as
156 modules on kernels not having 'device iflib', the iflib.ko module
157 is loaded automatically.
160 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
161 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
162 servers that have vfs.nfsd.nfs_privport set will only allow mounts
163 from clients using a reserved port#. Since both the FreeBSD and Linux
164 NFSv4 clients use reserved port#s by default, this should not affect
168 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
169 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
170 it produces broken binaries when ifuncs are in use. Users needing
171 GNU ld should install the binutils port or package.
174 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
175 has been converted to a port (misc/ctm) and will be removed from
176 FreeBSD-13. A depreciation warning will be printed to stderr by
177 the ctm command, but the functionality will remain in base for all
181 The stable/12 branch has been created in subversion from head
185 Ports for the DRM modules have been simplified. Now, amd64 users should
186 just install the drm-kmod port. All others should install
189 Graphics hardware that's newer than about 2010 usually works with
190 drm-kmod. For hardware older than 2013, however, some users will need
191 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
192 than 2008 usually only works in drm-legacy-kmod. The graphics team can
193 only commit to hardware made since 2013 due to the complexity of the
194 market and difficulty to test all the older cards effectively. If you
195 have hardware supported by drm-kmod, you are strongly encouraged to use
196 that as you will get better support.
198 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
199 elsewhere, the drm and drm2 modules will be eliminated from the src base
200 soon (with a limited exception for arm). Please update to the package asap
201 and report any issues to x11@freebsd.org.
203 Generally, anybody using the drm*-kmod packages should add
204 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
205 cross-threading surprises, especially with automatic driver
206 loading from X11 startup. These will become the defaults in 13-current
210 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
211 custom kernel and module loading configuration files must be updated
212 accordingly. Moreover, interfaces previous presented as ixlvN to the
213 system are now exposed as iavfN and network configuration files must
214 be adjusted as necessary.
217 OpenSSL has been updated to version 1.1.1. This update included
218 additional various API changes througout the base system. It is
219 important to rebuild third-party software after upgrading. The value
220 of __FreeBSD_version has been bumped accordingly.
223 The legacy DRM modules and drivers have now been added to the loader's
224 module blacklist, in favor of loading them with kld_list in rc.conf(5).
225 The module blacklist may be overridden with the loader.conf(5)
226 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
230 The cam(4) based nda(4) driver will be used over nvd(4) by default on
231 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
232 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
233 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
237 Reproducible build mode is now on by default, in preparation for
238 FreeBSD 12.0. This eliminates build metadata such as the user,
239 host, and time from the kernel (and uname), unless the working tree
240 corresponds to a modified checkout from a version control system.
241 The previous behavior can be obtained by setting the /etc/src.conf
242 knob WITHOUT_REPRODUCIBLE_BUILD.
245 The Yarrow CSPRNG has been removed from the kernel as it has not been
246 supported by its designers since at least 2003. Fortuna has been the
247 default since FreeBSD-11.
250 devctl freeze/thaw have gone into the tree, the rc scripts have been
251 updated to use them and devmatch has been changed. You should update
252 kernel, userland and rc scripts all at the same time.
255 The default interpreter has been switched from 4th to Lua.
256 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
257 interpreter. If you have custom FORTH code you will need to set
258 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
259 src.conf for the build. This will create default hard links between
260 loader and loader_4th instead of loader and loader_lua, the new default.
261 If you are using UEFI it will create the proper hard link to loader.efi.
263 bhyve uses userboot.so. It remains 4th-only until some issues are solved
264 regarding coexisting with multiple versions of FreeBSD are resolved.
267 ls(1) now respects the COLORTERM environment variable used in other
268 systems and software to indicate that a colored terminal is both
269 supported and desired. If ls(1) is suddenly emitting colors, they may
270 be disabled again by either removing the unwanted COLORTERM from your
271 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
272 may not be observed in a future release.
275 The default pager for most commands has been changed to "less". To
276 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
280 The jedec_ts(4) driver has been removed. A superset of its functionality
281 is available in the jedec_dimm(4) driver, and the manpage for that
282 driver includes migration instructions. If you have "device jedec_ts"
283 in your kernel configuration file, it must be removed.
286 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
287 This should have no effect if the kernel is booted via BIOS/legacy boot.
288 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
289 has a buggy firmware that prevents a successful boot due to use of
293 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
294 support has been removed from the tree. These ports were
295 obsolete and/or known to be broken for many years.
298 loader.efi has been augmented to participate more fully in the
299 UEFI boot manager protocol. loader.efi will now look at the
300 BootXXXX environment variable to determine if a specific kernel
301 or root partition was specified. XXXX is derived from BootCurrent.
302 efibootmgr(8) manages these standard UEFI variables.
305 zfsloader's functionality has now been folded into loader.
306 zfsloader is no longer necessary once you've updated your
307 boot blocks. For a transition period, we will install a
308 hardlink for zfsloader to loader to allow a smooth transition
309 until the boot blocks can be updated (hard link because old
310 zfs boot blocks don't understand symlinks).
313 ARM64 now have efifb support, if you want to have serial console
314 on your arm64 board when an screen is connected and the bootloader
315 setup a frambuffer for us to use, just add :
319 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
320 an screen connected as the firmware will setup a framebuffer are that
321 u-boot will expose as an EFI framebuffer.
324 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
325 or take steps to update /etc/passwd before doing installworld on
326 existing systems. Do not skip the "mergemaster -Fp" step before
327 installworld, as described in the update procedures near the bottom
328 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
329 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
330 the ntp config file contain options that change file/dir locations.
331 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
332 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
333 taking steps to ensure that all required files/dirs are accessible
337 Big endian arm support has been removed.
340 The static environment setup in kernel configs is no longer mutually
341 exclusive with the loader(8) environment by default. In order to
342 restore the previous default behavior of disabling the loader(8)
343 environment if a static environment is present, you must specify
344 loader_env.disabled=1 in the static environment.
347 The ABI of syscalls used by management tools like sockstat and
348 netstat has been broken to allow 32-bit binaries to work on
349 64-bit kernels without modification. These programs will need
350 to match the kernel in order to function. External programs may
351 require minor modifications to accommodate a change of type in
352 structures from pointers to 64-bit virtual addresses.
355 On i386 and amd64 atomics are now inlined. Out of tree modules using
356 atomics will need to be rebuilt.
359 The '%I' format in the kern.corefile sysctl limits the number of
360 core files that a process can generate to the number stored in the
361 debug.ncores sysctl. The '%I' format is replaced by the single digit
362 index. Previously, if all indexes were taken the kernel would overwrite
363 only a core file with the highest index in a filename.
364 Currently the system will create a new core file if there is a free
365 index or if all slots are taken it will overwrite the oldest one.
368 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
369 6.0.1. Please see the 20141231 entry below for information about
370 prerequisites and upgrading, if you are not already using clang 3.5.0
374 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
375 needed to be changed to work with it. This change was made with r335763
376 and requires a mergemaster / etcupdate / etc to update the installed file.
379 r334930 changed the interface between the NFS modules, so they all
380 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
383 As of r334391 lld is the default amd64 system linker; it is installed
384 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
388 The kernel / userland interface for devinfo changed, so you'll
389 need a new kernel and userland as a pair for it to work (rebuilding
390 lib/libdevinfo is all that's required). devinfo and devmatch will
391 not work, but everything else will when there's a mismatch.
394 The on-disk format for hwpmc callchain records has changed to include
395 threadid corresponding to a given record. This changes the field offsets
396 and thus requires that libpmcstat be rebuilt before using a kernel
400 The vxge(4) driver has been removed. This driver was introduced into
401 HEAD one week before the Exar left the Ethernet market and is not
402 known to be used. If you have device vxge in your kernel config file
406 The amd64 kernel now requires a ld that supports ifunc to produce a
407 working kernel, either lld or a newer binutils. lld is built by default
408 on amd64, and the 'buildkernel' target uses it automatically. However,
409 it is not the default linker, so building the kernel the traditional
410 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
411 binutils port/package). lld will soon be default, and this requirement
414 NOTE: As of r334391 lld is the default system linker on amd64, and no
415 workaround is necessary.
418 The nxge(4) driver has been removed. This driver was for PCI-X 10g
419 cards made by s2io/Neterion. The company was aquired by Exar and
420 no longer sells or supports Ethernet products. If you have device
421 nxge in your kernel config file it must be removed.
424 The tz database (tzdb) has been updated to 2018e. This version more
425 correctly models time stamps in time zones with negative DST such as
426 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
427 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
428 time zone abbreviations and the tm_isdst flag.
431 The ixgb(4) driver has been removed. This driver was for an early and
432 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
433 quickly shifted to the long lived ixgbe family. If you have device
434 ixgb in your kernel config file it must be removed.
437 The lmc(4) driver has been removed. This was a WAN interface
438 card that was already reportedly rare in 2003, and had an ambiguous
439 license. If you have device lmc in your kernel config file it must
443 Support for Arcnet networks has been removed. If you have device
444 arcnet or device cm in your kernel config file they must be
448 Support for FDDI networks has been removed. If you have device
449 fddi or device fpa in your kernel config file they must be
453 In addition to supporting RFC 3164 formatted messages, the
454 syslogd(8) service is now capable of parsing RFC 5424 formatted
455 log messages. The main benefit of using RFC 5424 is that clients
456 may now send log messages with timestamps containing year numbers,
457 microseconds and time zone offsets.
459 Similarly, the syslog(3) C library function has been altered to
460 send RFC 5424 formatted messages to the local system logging
461 daemon. On systems using syslogd(8), this change should have no
462 negative impact, as long as syslogd(8) and the C library are
463 updated at the same time. On systems using a different system
464 logging daemon, it may be necessary to make configuration
465 adjustments, depending on the software used.
467 When using syslog-ng, add the 'syslog-protocol' flag to local
468 input sources to enable parsing of RFC 5424 formatted messages:
471 unix-dgram("/var/run/log" flags(syslog-protocol));
474 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
475 of the 'imuxsock' module to let messages be processed by the
476 regular RFC 3164/5424 parsing pipeline:
478 module(load="imuxsock" SysSock.UseSpecialParser="off")
480 Do note that these changes only affect communication between local
481 applications and syslogd(8). The format that syslogd(8) uses to
482 store messages on disk or forward messages to other systems
483 remains unchanged. syslogd(8) still uses RFC 3164 for these
484 purposes. Options to customize this behaviour will be added in the
485 future. Utilities that process log files stored in /var/log are
486 thus expected to continue to function as before.
488 __FreeBSD_version has been incremented to 1200061 to denote this
492 Support for token ring networks has been removed. If you
493 have "device token" in your kernel config you should remove
494 it. No device drivers supported token ring.
497 makefs was modified to be able to tag ISO9660 El Torito boot catalog
498 entries as EFI instead of overloading the i386 tag as done previously.
499 The amd64 mkisoimages.sh script used to build amd64 ISO images for
500 release was updated to use this. This may mean that makefs must be
501 updated before "make cdrom" can be run in the release directory. This
502 should be as simple as:
504 $ cd $SRCDIR/usr.sbin/makefs
505 $ make depend all install
508 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
509 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
510 Co-existance for the transition period will come shortly. Booting is a
511 complex environment and test coverage for Lua-enabled loaders has been
512 thin, so it would be prudent to assume it might not work and make
513 provisions for backup boot methods.
516 devmatch functionality has been turned on in devd. It will automatically
517 load drivers for unattached devices. This may cause unexpected drivers to
518 be loaded. Please report any problems to current@ and imp@freebsd.org.
521 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
522 6.0.0. Please see the 20141231 entry below for information about
523 prerequisites and upgrading, if you are not already using clang 3.5.0
527 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
528 This means it is used to link the kernel and userland libraries and
529 executables, but is not yet installed as /usr/bin/ld by default.
531 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
532 WITHOUT_LLD_BOOTSTRAP=yes
535 On i386, pmtimer has been removed. Its functionality has been folded
536 into apm. It was a no-op on ACPI in current for a while now (but was still
537 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
538 from kernel config files.
541 The use of RSS hash from the network card aka flowid has been
542 disabled by default for lagg(4) as it's currently incompatible with
543 the lacp and loadbalance protocols.
545 This can be re-enabled by setting the following in loader.conf:
546 net.link.lagg.default_use_flowid="1"
549 The SW_WATCHDOG option is no longer necessary to enable the
550 hardclock-based software watchdog if no hardware watchdog is
551 configured. As before, SW_WATCHDOG will cause the software
552 watchdog to be enabled even if a hardware watchdog is configured.
555 r326887 fixes the issue described in the 20171214 UPDATING entry.
556 r326888 flips the switch back to building GELI support always.
559 r362593 broke ZFS + GELI support for reasons unknown. However,
560 it also broke ZFS support generally, so GELI has been turned off
561 by default as the lesser evil in r326857. If you boot off ZFS and/or
562 GELI, it might not be a good time to update.
565 PowerPC users must update loader(8) by rebuilding world before
566 installing a new kernel, as the protocol connecting them has
567 changed. Without the update, loader metadata will not be passed
568 successfully to the kernel and users will have to enter their
569 root partition at the kernel mountroot prompt to continue booting.
570 Newer versions of loader can boot old kernels without issue.
573 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
574 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
575 to WITH/OUT_LOADER_GELI.
578 The naive and non-compliant support of posix_fallocate(2) in ZFS
579 has been removed as of r325320. The system call now returns EINVAL
580 when used on a ZFS file. Although the new behavior complies with the
581 standard, some consumers are not prepared to cope with it.
582 One known victim is lld prior to r325420.
585 Building in a FreeBSD src checkout will automatically create object
586 directories now rather than store files in the current directory if
587 'make obj' was not ran. Calling 'make obj' is no longer necessary.
588 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
589 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
593 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
594 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
595 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
596 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
597 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
598 The UNIFIED_OBJDIR option is a transitional feature that will be
599 removed for 12.0 release; please migrate to the new format for any
600 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
601 than hardcoding paths.
604 The native-xtools target no longer installs the files by default to the
605 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
606 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
609 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
610 options are changing from controlling the build if defined / undefined
611 to controlling the build with explicit 'yes' or 'no' values. They will
612 shift to WITH/WITHOUT options to match other options in the system.
615 libstand has turned into a private library for sys/boot use only.
616 It is no longer supported as a public interface outside of sys/boot.
619 The arm port has split armv6 into armv6 and armv7. armv7 is now
620 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
621 and are running a kernel from before r324363, you will need to add
622 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
625 When building multiple kernels using KERNCONF, non-existent KERNCONF
626 files will produce an error and buildkernel will fail. Previously
627 missing KERNCONF files silently failed giving no indication as to
628 why, only to subsequently discover during installkernel that the
629 desired kernel was never built in the first place.
632 The default serial number format for CTL LUNs has changed. This will
633 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
634 or iSCSI clients care about their LUNs' serial numbers. Users who
635 require serial number stability should hardcode serial numbers in
639 For 32-bit arm compiled for hard-float support, soft-floating point
640 binaries now always get their shared libraries from
641 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
642 /usr/libsoft also existed). Only users with a hard-float ld.so, but
643 soft-float everything else should be affected.
646 The geli password typed at boot is now hidden. To restore the previous
647 behavior, see geli(8) for configuration options.
650 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
651 sysctl values. Minor nit, but requires a rebuild of both world/kernel
655 "make check" behavior (made in ^/head@r295380) has been changed to
656 execute from a limited sandbox, as opposed to executing from
660 - The "beforecheck" and "aftercheck" targets are now specified.
661 - ${CHECKDIR} (added in commit noted above) has been removed.
662 - Legacy behavior can be enabled by setting
663 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
665 If the limited sandbox mode is enabled, "make check" will execute
666 "make distribution", then install, execute the tests, and clean up the
667 sandbox if successful.
669 The "make distribution" and "make install" targets are typically run as
670 root to set appropriate permissions and ownership at installation time.
671 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
672 environment if executing "make check" with limited sandbox mode using
673 an unprivileged user.
676 Since the switch to GPT disk labels, fsck for UFS/FFS has been
677 unable to automatically find alternate superblocks. As of r322297,
678 the information needed to find alternate superblocks has been
679 moved to the end of the area reserved for the boot block.
680 Filesystems created with a newfs of this vintage or later
681 will create the recovery information. If you have a filesystem
682 created prior to this change and wish to have a recovery block
683 created for your filesystem, you can do so by running fsck in
684 foreground mode (i.e., do not use the -p or -y options). As it
685 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
686 to which you should answer yes.
689 As of r321665, an NFSv4 server configuration that services
690 Kerberos mounts or clients that do not support the uid/gid in
691 owner/owner_group string capability, must explicitly enable
692 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
693 machine's /etc/rc.conf file.
696 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
697 Please see the 20141231 entry below for information about prerequisites
698 and upgrading, if you are not already using clang 3.5.0 or higher.
701 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
702 r-commands (rlogin, rsh, etc.) to be built with the base system.
705 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
706 a very major ABI incompatible change, so users of FreeBSD/powerpc must
707 be careful when performing source upgrades. It is best to run
708 'make installworld' from an alternate root system, either a live
709 CD/memory stick, or a temporary root partition. Additionally, all ports
710 must be recompiled. powerpc64 is largely unaffected, except in the case
711 of 32-bit compatibility. All 32-bit binaries will be affected.
714 Forward compatibility for the "ino64" project have been committed. This
715 will allow most new binaries to run on older kernels in a limited
716 fashion. This prevents many of the common foot-shooting actions in the
717 upgrade as well as the limited ability to roll back the kernel across
718 the ino64 upgrade. Complicated use cases may not work properly, though
719 enough simpler ones work to allow recovery in most situations.
722 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
723 if you require the GPL compiler.
726 The internal ABI used for communication between the NFS kernel modules
727 was changed by r320085, so __FreeBSD_version was bumped to
728 ensure all the NFS related modules are updated together.
731 The ABI of struct event was changed by extending the data
732 member to 64bit and adding ext fields. For upgrade, same
733 precautions as for the entry 20170523 "ino64" must be
737 The GNU roff toolchain has been removed from base. To render manpages
738 which are not supported by mandoc(1), man(1) can fallback on GNU roff
739 from ports (and recommends to install it).
740 To render roff(7) documents, consider using GNU roff from ports or the
741 heirloom doctools roff toolchain from ports via pkg install groff or
742 via pkg install heirloom-doctools.
745 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
746 smaller runtime footprint builds. This is useful for embedded systems
747 which only require one chipset support.
749 If you load it as a module, make sure this is in /boot/loader.conf:
753 This will load the HAL, all chip/RF backends and if_ath_pci.
754 If you have if_ath_pci in /boot/loader.conf, ensure it is after
755 if_ath or it will not load any HAL chipset support.
757 If you want to selectively load things (eg on ye cheape ARM/MIPS
758 platforms where RAM is at a premium) you should:
761 * load the chip modules in question
762 * load ath_rate, ath_dfs
764 * load if_ath_pci and/or if_ath_ahb depending upon your particular
765 bus bind type - this is where probe/attach is done.
767 For further comments/feedback, poke adrian@ .
770 The "ino64" 64-bit inode project has been committed, which extends
771 a number of types to 64 bits. Upgrading in place requires care and
772 adherence to the documented upgrade procedure.
774 If using a custom kernel configuration ensure that the
775 COMPAT_FREEBSD11 option is included (as during the upgrade the
776 system will be running the ino64 kernel with the existing world).
778 For the safest in-place upgrade begin by removing previous build
779 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
780 full procedure documented below under the heading "To rebuild
781 everything and install it on the current system." Specifically,
782 a reboot is required after installing the new kernel before
786 The NATM framework including the en(4), fatm(4), hatm(4), and
787 patm(4) devices has been removed. Consumers should plan a
788 migration before the end-of-life date for FreeBSD 11.
791 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
792 diff has not been implemented, if those are needed a newer version of
793 GNU diff is available via the diffutils package under the gdiff name.
796 As of r316810 for ipfilter, keep frags is no longer assumed when
797 keep state is specified in a rule. r316810 aligns ipfilter with
798 documentation in man pages separating keep frags from keep state.
799 This allows keep state to be specified without forcing keep frags
800 and allows keep frags to be specified independently of keep state.
801 To maintain previous behaviour, also specify keep frags with
802 keep state (as documented in ipf.conf.5).
805 arm64 builds now use the base system LLD 4.0.0 linker by default,
806 instead of requiring that the aarch64-binutils port or package be
807 installed. To continue using aarch64-binutils, set
808 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
811 The UDP optimization in entry 20160818 that added the sysctl
812 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
813 packets will no longer be treated as L3 broadcast packets.
816 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
817 use any explicitly assigned loopback address available in the jail
818 instead of using the first assigned address of the jail.
821 The ctl.ko module no longer implements the iSCSI target frontend:
822 cfiscsi.ko does instead.
824 If building cfiscsi.ko as a kernel module, the module can be loaded
825 via one of the following methods:
826 - `cfiscsi_load="YES"` in loader.conf(5).
827 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
828 - ctladm(8)/ctld(8), when compiled with iSCSI support
829 (`WITH_ISCSI=yes` in src.conf(5))
831 Please see cfiscsi(4) for more details.
834 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
835 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
836 same source (previously, the dependency of mmcsd.ko on mmc.ko was
837 missing, but mmcsd.ko now will refuse to load if it is incompatible
841 The syntax of ipfw(8) named states was changed to avoid ambiguity.
842 If you have used named states in the firewall rules, you need to modify
843 them after installworld and before rebooting. Now named states must
844 be prefixed with colon.
847 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
848 removed as the userland we provide cannot use them. The KMS version
849 (sys/dev/drm2) supports the same hardware.
852 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
853 Please see the 20141231 entry below for information about prerequisites
854 and upgrading, if you are not already using clang 3.5.0 or higher.
857 The code that provides support for ZFS .zfs/ directory functionality
858 has been reimplemented. It's not possible now to create a snapshot
859 by mkdir under .zfs/snapshot/. That should be the only user visible
863 EISA bus support has been removed. The WITH_EISA option is no longer
867 MCA bus support has been removed.
870 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
871 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
874 The EM_MULTIQUEUE kernel configuration option is deprecated now that
875 the em(4) driver conforms to iflib specifications.
878 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
879 IFLIB. If you have a custom kernel configuration that excludes em(4)
880 but you use igb(4), you need to re-add em(4) to your custom configuration.
883 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
884 Please see the 20141231 entry below for information about prerequisites
885 and upgrading, if you are not already using clang 3.5.0 or higher.
888 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
889 Please see the 20141231 entry below for information about prerequisites
890 and upgrading, if you are not already using clang 3.5.0 or higher.
893 The layout of the pmap structure has changed for powerpc to put the pmap
894 statistics at the front for all CPU variations. libkvm(3) and all tools
895 that link against it need to be recompiled.
898 isl(4) and cyapa(4) drivers now require a new driver,
899 chromebook_platform(4), to work properly on Chromebook-class hardware.
900 On other types of hardware the drivers may need to be configured using
901 device hints. Please see the corresponding manual pages for details.
904 The urtwn(4) driver was merged into rtwn(4) and now consists of
905 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
907 Also, firmware for RTL8188CE was renamed due to possible name
908 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
911 GNU rcs has been removed from base. It is available as packages:
912 - rcs: Latest GPLv3 GNU rcs version.
913 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
917 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
918 modules now requires that the kernel configuration contain the
919 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
922 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
923 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
926 Relocatable object files with the extension of .So have been renamed
927 to use an extension of .pico instead. The purpose of this change is
928 to avoid a name clash with shared libraries on case-insensitive file
929 systems. On those file systems, foo.So is the same file as foo.so.
932 GNU rcs has been turned off by default. It can (temporarily) be built
933 again by adding WITH_RCS knob in src.conf.
934 Otherwise, GNU rcs is available from packages:
935 - rcs: Latest GPLv3 GNU rcs version.
936 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
939 The backup_uses_rcs functionality has been removed from rc.subr.
942 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
943 two separate components, QUEUE_MACRO_DEBUG_TRACE and
944 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
945 QUEUE_MACRO_DEBUG behavior.
948 r304787 changed some ioctl interfaces between the iSCSI userspace
949 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
950 rebuilt to work with new kernels. __FreeBSD_version has been bumped
954 The UDP receive code has been updated to only treat incoming UDP
955 packets that were addressed to an L2 broadcast address as L3
956 broadcast packets. It is not expected that this will affect any
957 standards-conforming UDP application. The new behaviour can be
958 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
962 Remove the openbsd_poll system call.
963 __FreeBSD_version has been bumped because of this.
966 The stable/11 branch has been created from head@r302406.
969 The libc stub for the pipe(2) system call has been replaced with
970 a wrapper that calls the pipe2(2) system call and the pipe(2)
971 system call is now only implemented by the kernels that include
972 "options COMPAT_FREEBSD10" in their config file (this is the
973 default). Users should ensure that this option is enabled in
974 their kernel or upgrade userspace to r302092 before upgrading their
978 CAM will now strip leading spaces from SCSI disks' serial numbers.
979 This will affect users who create UFS filesystems on SCSI disks using
980 those disk's diskid device nodes. For example, if /etc/fstab
981 previously contained a line like
982 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
983 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
984 transforms like gmirror may also be affected. ZFS users should
988 The bitstring(3) API has been updated with new functionality and
989 improved performance. But it is binary-incompatible with the old API.
990 Objects built with the new headers may not be linked against objects
991 built with the old headers.
994 The brk and sbrk functions have been removed from libc on arm64.
995 Binutils from ports has been updated to not link to these
996 functions and should be updated to the latest version before
997 installing a new libc.
1000 The armv6 port now defaults to hard float ABI. Limited support
1001 for running both hardfloat and soft float on the same system
1002 is available using the libraries installed with -DWITH_LIBSOFT.
1003 This has only been tested as an upgrade path for installworld
1004 and packages may fail or need manual intervention to run. New
1005 packages will be needed.
1007 To update an existing self-hosted armv6hf system, you must add
1008 TARGET_ARCH=armv6 on the make command line for both the build
1009 and the install steps.
1012 Kernel modules compiled outside of a kernel build now default to
1013 installing to /boot/modules instead of /boot/kernel. Many kernel
1014 modules built this way (such as those in ports) already overrode
1015 KMODDIR explicitly to install into /boot/modules. However,
1016 manually building and installing a module from /sys/modules will
1017 now install to /boot/modules instead of /boot/kernel.
1020 The CAM I/O scheduler has been committed to the kernel. There should be
1021 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1022 list of known rogues that claim support for this but actually corrupt
1023 data is believed to be complete, be on the lookout for data
1024 corruption. The known rogue list is believed to be complete:
1026 o Crucial MX100, M550 drives with MU01 firmware.
1027 o Micron M510 and M550 drives with MU01 firmware.
1028 o Micron M500 prior to MU07 firmware
1029 o Samsung 830, 840, and 850 all firmwares
1030 o FCCT M500 all firmwares
1032 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1033 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1034 updated firmware. Black listed drives will work correctly because these
1035 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1036 this list is the same as found in Linux, it's believed there are no
1037 other rogues in the market place. All other models from the above
1040 To be safe, if you are at all concerned, you can quirk each of your
1041 drives to prevent NCQ from being sent by setting:
1042 kern.cam.ada.X.quirks="0x2"
1043 in loader.conf. If the drive requires the 4k sector quirk, set the
1044 quirks entry to 0x3.
1047 The FAST_DEPEND build option has been removed and its functionality is
1048 now the one true way. The old mkdep(1) style of 'make depend' has
1049 been removed. See 20160311 for further details.
1052 Resource range types have grown from unsigned long to uintmax_t. All
1053 drivers, and anything using libdevinfo, need to be recompiled.
1056 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1057 builds. It no longer runs mkdep(1) during 'make depend', and the
1058 'make depend' stage can safely be skipped now as it is auto ran
1059 when building 'make all' and will generate all SRCS and DPSRCS before
1060 building anything else. Dependencies are gathered at compile time with
1061 -MF flags kept in separate .depend files per object file. Users should
1062 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1063 stale .depend files.
1066 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1067 kernel modules. Therefore, if you load any kernel modules at boot time,
1068 please install the boot loaders after you install the kernel, but before
1072 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1073 make installkernel KERNCONF=YOUR_KERNEL_HERE
1074 make -C sys/boot install
1075 <reboot in single user>
1077 Then follow the usual steps, described in the General Notes section,
1081 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1082 see the 20141231 entry below for information about prerequisites and
1083 upgrading, if you are not already using clang 3.5.0 or higher.
1086 The AIO subsystem is now a standard part of the kernel. The
1087 VFS_AIO kernel option and aio.ko kernel module have been removed.
1088 Due to stability concerns, asynchronous I/O requests are only
1089 permitted on sockets and raw disks by default. To enable
1090 asynchronous I/O requests on all file types, set the
1091 vfs.aio.enable_unsafe sysctl to a non-zero value.
1094 The ELF object manipulation tool objcopy is now provided by the
1095 ELF Tool Chain project rather than by GNU binutils. It should be a
1096 drop-in replacement, with the addition of arm64 support. The
1097 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1098 to obtain the GNU version if necessary.
1101 Building ZFS pools on top of zvols is prohibited by default. That
1102 feature has never worked safely; it's always been prone to deadlocks.
1103 Using a zvol as the backing store for a VM guest's virtual disk will
1104 still work, even if the guest is using ZFS. Legacy behavior can be
1105 restored by setting vfs.zfs.vol.recursive=1.
1108 The NONE and HPN patches has been removed from OpenSSH. They are
1109 still available in the security/openssh-portable port.
1112 With the addition of ypldap(8), a new _ypldap user is now required
1113 during installworld. "mergemaster -p" can be used to add the user
1114 prior to installworld, as documented in the handbook.
1117 The tftp loader (pxeboot) now uses the option root-path directive. As a
1118 consequence it no longer looks for a pxeboot.4th file on the tftp
1119 server. Instead it uses the regular /boot infrastructure as with the
1123 The code to start recording plug and play data into the modules has
1124 been committed. While the old tools will properly build a new kernel,
1125 a number of warnings about "unknown metadata record 4" will be produced
1126 for an older kldxref. To avoid such warnings, make sure to rebuild
1127 the kernel toolchain (or world). Make sure that you have r292078 or
1128 later when trying to build 292077 or later before rebuilding.
1131 Debug data files are now built by default with 'make buildworld' and
1132 installed with 'make installworld'. This facilitates debugging but
1133 requires more disk space both during the build and for the installed
1134 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1138 r291527 changed the internal interface between the nfsd.ko and
1139 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1140 __FreeBSD_version has been bumped because of this.
1143 Add support for unicode collation strings leads to a change of
1144 order of files listed by ls(1) for example. To get back to the old
1145 behaviour, set LC_COLLATE environment variable to "C".
1147 Databases administrators will need to reindex their databases given
1148 collation results will be different.
1150 Due to a bug in install(1) it is recommended to remove the ancient
1151 locales before running make installworld.
1153 rm -rf /usr/share/locale/*
1156 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1157 libcrypto.so.7 or libssl.so.7 must be recompiled.
1160 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1161 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1162 should be replaced with isp_2400 and isp_2500 modules respectively.
1165 The build previously allowed using 'make -n' to not recurse into
1166 sub-directories while showing what commands would be executed, and
1167 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1168 and 'make -N' will not.
1171 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1172 and etcupdate will now use this file. A custom sendmail.cf is now
1173 updated via this mechanism rather than via installworld. If you had
1174 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1175 want to remove the exclusion or change it to "always install".
1176 /etc/mail/sendmail.cf is now managed the same way regardless of
1177 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1178 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1181 Compatibility shims for legacy ATA device names have been removed.
1182 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1183 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1184 environment variables, /dev/ad* and /dev/ar* symbolic links.
1187 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1188 Please see the 20141231 entry below for information about prerequisites
1189 and upgrading, if you are not already using clang 3.5.0 or higher.
1192 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1193 and renamed from .symbols to .debug. This reduces the size requirements
1194 on the boot partition or file system and provides consistency with
1195 userland debug files.
1197 When using the supported kernel installation method the
1198 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1199 as is done with /boot/kernel.
1201 Developers wishing to maintain the historical behavior of installing
1202 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1205 The wireless drivers had undergone changes that remove the 'parent
1206 interface' from the ifconfig -l output. The rc.d network scripts
1207 used to check presence of a parent interface in the list, so old
1208 scripts would fail to start wireless networking. Thus, etcupdate(3)
1209 or mergemaster(8) run is required after kernel update, to update your
1210 rc.d scripts in /etc.
1213 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1214 These configurations are now automatically interpreted as
1215 'scrub fragment reassemble'.
1218 Kernel-loadable modules for the random(4) device are back. To use
1219 them, the kernel must have
1222 options RANDOM_LOADABLE
1224 kldload(8) can then be used to load random_fortuna.ko
1225 or random_yarrow.ko. Please note that due to the indirect
1226 function calls that the loadable modules need to provide,
1227 the build-in variants will be slightly more efficient.
1229 The random(4) kernel option RANDOM_DUMMY has been retired due to
1230 unpopularity. It was not all that useful anyway.
1233 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1234 Control over building the ELF Tool Chain tools is now provided by
1235 the WITHOUT_TOOLCHAIN knob.
1238 The polarity of Pulse Per Second (PPS) capture events with the
1239 uart(4) driver has been corrected. Prior to this change the PPS
1240 "assert" event corresponded to the trailing edge of a positive PPS
1241 pulse and the "clear" event was the leading edge of the next pulse.
1243 As the width of a PPS pulse in a typical GPS receiver is on the
1244 order of 1 millisecond, most users will not notice any significant
1245 difference with this change.
1247 Anyone who has compensated for the historical polarity reversal by
1248 configuring a negative offset equal to the pulse width will need to
1249 remove that workaround.
1252 The default group assigned to /dev/dri entries has been changed
1253 from 'wheel' to 'video' with the id of '44'. If you want to have
1254 access to the dri devices please add yourself to the video group
1257 # pw groupmod video -m $USER
1260 The menu.rc and loader.rc files will now be replaced during
1261 upgrades. Please migrate local changes to menu.rc.local and
1262 loader.rc.local instead.
1265 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1266 strings and strip have been removed. The src.conf(5) knob
1267 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1270 As ZFS requires more kernel stack pages than is the default on some
1271 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1272 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1274 Please consider using 'options KSTACK_PAGES=X' where X is greater
1275 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1278 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1279 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1280 default, i.e., they will not contain "::". For example, instead
1281 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1282 to have a more specific match, such as different map entries for
1283 IPv6:0:0 vs IPv6:0. This change requires that configuration
1284 data (including maps, files, classes, custom ruleset, etc.) must
1285 use the same format, so make certain such configuration data is
1286 upgrading. As a very simple check search for patterns like
1287 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1288 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1289 the cf option UseCompressedIPv6Addresses.
1292 The default kernel entropy-processing algorithm is now
1293 Fortuna, replacing Yarrow.
1295 Assuming you have 'device random' in your kernel config
1296 file, the configurations allow a kernel option to override
1297 this default. You may choose *ONE* of:
1299 options RANDOM_YARROW # Legacy /dev/random algorithm.
1300 options RANDOM_DUMMY # Blocking-only driver.
1302 If you have neither, you get Fortuna. For most people,
1303 read no further, Fortuna will give a /dev/random that works
1304 like it always used to, and the difference will be irrelevant.
1306 If you remove 'device random', you get *NO* kernel-processed
1307 entropy at all. This may be acceptable to folks building
1308 embedded systems, but has complications. Carry on reading,
1309 and it is assumed you know what you need.
1311 *PLEASE* read random(4) and random(9) if you are in the
1312 habit of tweaking kernel configs, and/or if you are a member
1313 of the embedded community, wanting specific and not-usual
1314 behaviour from your security subsystems.
1316 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1317 random', you will NOT have a functioning /dev/random, and
1318 many cryptographic features will not work, including SSH.
1319 You may also find strange behaviour from the random(3) set
1320 of library functions, in particular sranddev(3), srandomdev(3)
1321 and arc4random(3). The reason for this is that the KERN_ARND
1322 sysctl only returns entropy if it thinks it has some to
1323 share, and with RANDOM_DUMMY or no 'device random' this
1327 An additional fix for the issue described in the 20150614 sendmail
1328 entry below has been committed in revision 284717.
1331 FreeBSD's old make (fmake) has been removed from the system. It is
1332 available as the devel/fmake port or via pkg install fmake.
1335 The fix for the issue described in the 20150614 sendmail entry
1336 below has been committed in revision 284436. The work
1337 around described in that entry is no longer needed unless the
1338 default setting is overridden by a confDH_PARAMETERS configuration
1339 setting of '5' or pointing to a 512 bit DH parameter file.
1342 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1343 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1344 and devel/kyua to version 0.20+ and adjust any calling code to work
1345 with Kyuafile and kyua.
1348 The import of openssl to address the FreeBSD-SA-15:10.openssl
1349 security advisory includes a change which rejects handshakes
1350 with DH parameters below 768 bits. sendmail releases prior
1351 to 8.15.2 (not yet released), defaulted to a 512 bit
1352 DH parameter setting for client connections. To work around
1353 this interoperability, sendmail can be configured to use a
1354 2048 bit DH parameter by:
1356 1. Edit /etc/mail/`hostname`.mc
1357 2. If a setting for confDH_PARAMETERS does not exist or
1358 exists and is set to a string beginning with '5',
1359 replace it with '2'.
1360 3. If a setting for confDH_PARAMETERS exists and is set to
1361 a file path, create a new file with:
1362 openssl dhparam -out /path/to/file 2048
1363 4. Rebuild the .cf file:
1364 cd /etc/mail/; make; make install
1365 5. Restart sendmail:
1366 cd /etc/mail/; make restart
1368 A sendmail patch is coming, at which time this file will be
1372 Generation of legacy formatted entries have been disabled by default
1373 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1374 entries were converted to use the new format by default when the new,
1375 machine independent format have been added and supported since FreeBSD
1378 Please see the pwd_mkdb(8) manual page for further details.
1381 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1382 20141231 entry below for information about prerequisites and upgrading,
1383 if you are not already using 3.5.0 or higher.
1386 TI platform code switched to using vendor DTS files and this update
1387 may break existing systems running on Beaglebone, Beaglebone Black,
1390 - dtb files should be regenerated/reinstalled. Filenames are the
1391 same but content is different now
1392 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1393 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1394 addressing scheme is now pin 25 on /dev/gpioc3.
1395 - Pandaboard: /etc/ttys should be updated, serial console device is
1396 now /dev/ttyu2, not /dev/ttyu0
1399 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1400 If you need the GNU extension from groff soelim(1), install groff
1401 from package: pkg install groff, or via ports: textproc/groff.
1404 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1405 defined in symlink(7); previously symlinks were silently ignored.
1408 The const qualifier has been removed from iconv(3) to comply with
1409 POSIX. The ports tree is aware of this from r384038 onwards.
1412 Libraries specified by LIBADD in Makefiles must have a corresponding
1413 DPADD_<lib> variable to ensure correct dependencies. This is now
1414 enforced in src.libnames.mk.
1417 From legacy ata(4) driver was removed support for SATA controllers
1418 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1419 Kernel modules ataahci and ataadaptec were removed completely,
1420 replaced by ahci and mvs modules respectively.
1423 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1424 the 20141231 entry below for information about prerequisites and
1425 upgrading, if you are not already using 3.5.0 or higher.
1428 The 32-bit PowerPC kernel has been changed to a position-independent
1429 executable. This can only be booted with a version of loader(8)
1430 newer than January 31, 2015, so make sure to update both world and
1431 kernel before rebooting.
1434 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1435 but before r278950, the RNG was not seeded properly. Immediately
1436 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1437 ssh keys or openssl keys) that were generated w/ a kernel from that
1438 range. This does not affect programs that directly used /dev/random
1439 or /dev/urandom. All userland uses of arc4random(3) are affected.
1442 The autofs(4) ABI was changed in order to restore binary compatibility
1443 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1444 with the new kernel.
1447 The powerpc64 kernel has been changed to a position-independent
1448 executable. This can only be booted with a new version of loader(8),
1449 so make sure to update both world and kernel before rebooting.
1452 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1453 only release, no new features have been added. Please see the 20141231
1454 entry below for information about prerequisites and upgrading, if you
1455 are not already using 3.5.0.
1458 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1459 taken from the ELF Tool Chain project rather than GNU binutils. They
1460 should be drop-in replacements, with the addition of arm64 support.
1461 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1462 binutils tools, if necessary. See 20150805 for updated information.
1465 The default Unbound configuration now enables remote control
1466 using a local socket. Users who have already enabled the
1467 local_unbound service should regenerate their configuration
1468 by running "service local_unbound setup" as root.
1471 The GNU texinfo and GNU info pages have been removed.
1472 To be able to view GNU info pages please install texinfo from ports.
1475 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1477 As of this release, a prerequisite for building clang, llvm and lldb is
1478 a C++11 capable compiler and C++11 standard library. This means that to
1479 be able to successfully build the cross-tools stage of buildworld, with
1480 clang as the bootstrap compiler, your system compiler or cross compiler
1481 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1482 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1485 On any standard FreeBSD 10.x or 11.x installation, where clang and
1486 libc++ are on by default (that is, on x86 or arm), this should work out
1489 On 9.x installations where clang is enabled by default, e.g. on x86 and
1490 powerpc, libc++ will not be enabled by default, so libc++ should be
1491 built (with clang) and installed first. If both clang and libc++ are
1492 missing, build clang first, then use it to build libc++.
1494 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1495 the instructions for 9.x above.
1497 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1498 default, and do not build clang.
1500 Many embedded systems are resource constrained, and will not be able to
1501 build clang in a reasonable time, or in some cases at all. In those
1502 cases, cross building bootable systems on amd64 is a workaround.
1504 This new version of clang introduces a number of new warnings, of which
1505 the following are most likely to appear:
1509 This warns in two cases, for both C and C++:
1510 * When the code is trying to take the absolute value of an unsigned
1511 quantity, which is effectively a no-op, and almost never what was
1512 intended. The code should be fixed, if at all possible. If you are
1513 sure that the unsigned quantity can be safely cast to signed, without
1514 loss of information or undefined behavior, you can add an explicit
1515 cast, or disable the warning.
1517 * When the code is trying to take an absolute value, but the called
1518 abs() variant is for the wrong type, which can lead to truncation.
1519 If you want to disable the warning instead of fixing the code, please
1520 make sure that truncation will not occur, or it might lead to unwanted
1523 -Wtautological-undefined-compare and
1524 -Wundefined-bool-conversion
1526 These warn when C++ code is trying to compare 'this' against NULL, while
1527 'this' should never be NULL in well-defined C++ code. However, there is
1528 some legacy (pre C++11) code out there, which actively abuses this
1529 feature, which was less strictly defined in previous C++ versions.
1531 Squid and openjdk do this, for example. The warning can be turned off
1532 for C++98 and earlier, but compiling the code in C++11 mode might result
1533 in unexpected behavior; for example, the parts of the program that are
1534 unreachable could be optimized away.
1537 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1538 kernel sources have been removed. The .h files remain, since some
1539 utilities include them. This will need to be fixed later.
1540 If "mount -t oldnfs ..." is attempted, it will fail.
1541 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1542 the utilities will report errors.
1545 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1546 directories to top level SUBDIR variable when their parent
1547 directory is included in LOCAL_DIRS. Users with build systems with
1548 such hierarchies and without SUBDIR entries in the parent
1549 directory Makefiles should add them or add the directories to
1553 faith(4) and faithd(8) have been removed from the base system. Faith
1554 has been obsolete for a very long time.
1557 vt(4), the new console driver, is enabled by default. It brings
1558 support for Unicode and double-width characters, as well as
1559 support for UEFI and integration with the KMS kernel video
1562 You may need to update your console settings in /etc/rc.conf,
1563 most probably the keymap. During boot, /etc/rc.d/syscons will
1564 indicate what you need to do.
1566 vt(4) still has issues and lacks some features compared to
1567 syscons(4). See the wiki for up-to-date information:
1568 https://wiki.freebsd.org/Newcons
1570 If you want to keep using syscons(4), you can do so by adding
1571 the following line to /boot/loader.conf:
1575 pjdfstest has been integrated into kyua as an opt-in test suite.
1576 Please see share/doc/pjdfstest/README for more details on how to
1580 gperf has been removed from the base system for architectures
1581 that use clang. Ports that require gperf will obtain it from the
1585 pjdfstest has been moved from tools/regression/pjdfstest to
1589 At svn r271982, The default linux compat kernel ABI has been adjusted
1590 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1591 update. If you wish to continue using the linux-f10 compat ports,
1592 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1593 encouraged to update their linux-compat packages to linux-c6 during
1594 their next update cycle.
1597 The ofwfb driver, used to provide a graphics console on PowerPC when
1598 using vt(4), no longer allows mmap() of all physical memory. This
1599 will prevent Xorg on PowerPC with some ATI graphics cards from
1600 initializing properly unless x11-servers/xorg-server is updated to
1604 The xdev targets have been converted to using TARGET and
1605 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1608 The default unbound configuration has been modified to address
1609 issues with reverse lookups on networks that use private
1610 address ranges. If you use the local_unbound service, run
1611 "service local_unbound setup" as root to regenerate your
1612 configuration, then "service local_unbound reload" to load the
1616 The GNU texinfo and GNU info pages are not built and installed
1617 anymore, WITH_INFO knob has been added to allow to built and install
1619 UPDATE: see 20150102 entry on texinfo's removal
1622 The GNU readline library is now an INTERNALLIB - that is, it is
1623 statically linked into consumers (GDB and variants) in the base
1624 system, and the shared library is no longer installed. The
1625 devel/readline port is available for third party software that
1629 The Itanium architecture (ia64) has been removed from the list of
1630 known architectures. This is the first step in the removal of the
1634 Commit r268115 has added NFSv4.1 server support, merged from
1635 projects/nfsv4.1-server. Since this includes changes to the
1636 internal interfaces between the NFS related modules, a full
1637 build of the kernel and modules will be necessary.
1638 __FreeBSD_version has been bumped.
1641 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1642 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1643 which differs from the behaviour controlled by this knob.)
1646 Maximal length of the serial number in CTL was increased from 16 to
1647 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1648 and ctld, need to be rebuilt to work with a new kernel.
1651 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1652 1 respectively to match the upstream numbers. They were out of
1653 sync because, when they were originally added to FreeBSD, the
1654 upstream versions were not respected. These libraries are private
1655 and not yet built by default, so renumbering them should be a
1656 non-issue. However, unclean source trees will yield broken test
1657 programs once the operator executes "make delete-old-libs" after a
1658 "make installworld".
1660 Additionally, the atf-sh binary was made private by moving it into
1661 /usr/libexec/. Already-built shell test programs will keep the
1662 path to the old binary so they will break after "make delete-old"
1665 If you are using WITH_TESTS=yes (not the default), wipe the object
1666 tree and rebuild from scratch to prevent spurious test failures.
1667 This is only needed once: the misnumbered libraries and misplaced
1668 binaries have been added to OptionalObsoleteFiles.inc so they will
1669 be removed during a clean upgrade.
1672 Clang and llvm have been upgraded to 3.4.1 release.
1675 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1676 be removed to avoid issues in the future (and has been added to
1680 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1681 past, it affected all builds that used the bsd.*.mk files. The old
1682 behavior was a bug, but people may have relied upon it. To get this
1683 behavior back, you can .include /etc/src.conf from /etc/make.conf
1684 (which is still global and isn't changed). This also changes the
1685 behavior of incremental builds inside the tree of individual
1686 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1687 Although this has survived make universe and some upgrade scenarios,
1688 other upgrade scenarios may have broken. At least one form of
1689 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1690 as well... In cases where MAKESYSPATH isn't working with this
1691 setting, you'll need to set it to the full path to your tree.
1693 One side effect of all this cleaning up is that bsd.compiler.mk
1694 is no longer implicitly included by bsd.own.mk. If you wish to
1695 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1699 The lindev device has been removed since /dev/full has been made a
1700 standard device. __FreeBSD_version has been bumped.
1703 The knob WITHOUT_VI was added to the base system, which controls
1704 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1705 in order to reorder files share/termcap and didn't build ex(1) as a
1706 build tool, so building/installing with WITH_VI is highly advised for
1707 build hosts for older releases.
1709 This issue has been fixed in stable/9 and stable/10 in r277022 and
1710 r276991, respectively.
1713 The YES_HESIOD knob has been removed. It has been obsolete for
1714 a decade. Please move to using WITH_HESIOD instead or your builds
1715 will silently lack HESIOD.
1718 The uart(4) driver has been changed with respect to its handling
1719 of the low-level console. Previously the uart(4) driver prevented
1720 any process from changing the baudrate or the CLOCAL and HUPCL
1721 control flags. By removing the restrictions, operators can make
1722 changes to the serial console port without having to reboot.
1723 However, when getty(8) is started on the serial device that is
1724 associated with the low-level console, a misconfigured terminal
1725 line in /etc/ttys will now have a real impact.
1726 Before upgrading the kernel, make sure that /etc/ttys has the
1727 serial console device configured as 3wire without baudrate to
1728 preserve the previous behaviour. E.g:
1729 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1732 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1733 to improve performance. To re-enable it, if needed, run rpcbind
1734 with command line option -W.
1737 Switched back to the GPL dtc compiler due to updates in the upstream
1738 dts files not being supported by the BSDL dtc compiler. You will need
1739 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1740 may result while building dtb files during a kernel build if you fail
1741 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1744 Clang and llvm have been upgraded to 3.4 release.
1747 The nve(4) driver has been removed. Please use the nfe(4) driver
1748 for NVIDIA nForce MCP Ethernet adapters instead.
1751 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1752 This could cause certain C++ applications using shared libraries built
1753 against the previous version of libc++ to crash. The incompatibility
1754 has now been fixed, but any C++ applications or shared libraries built
1755 between r261283 and r261801 should be recompiled.
1758 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1759 capability mode support. Please note that enabling the feature in
1760 kernel is still highly recommended.
1763 OpenSSH is now built with sandbox support, and will use sandbox as
1764 the default privilege separation method. This requires Capsicum
1765 capability mode support in kernel.
1768 The libelf and libdwarf libraries have been updated to newer
1769 versions from upstream. Shared library version numbers for
1770 these two libraries were bumped. Any ports or binaries
1771 requiring these two libraries should be recompiled.
1772 __FreeBSD_version is bumped to 1100006.
1775 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1776 instead of providing an explicit one, this would prevent such
1777 Makefile from providing its own Kyuafile in the future during
1778 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1779 intervention is needed to clean an objdir if you use NO_CLEAN:
1780 # find /usr/obj -name Kyuafile | xargs rm -f
1783 The behavior of gss_pseudo_random() for the krb5 mechanism
1784 has changed, for applications requesting a longer random string
1785 than produced by the underlying enctype's pseudo-random() function.
1786 In particular, the random string produced from a session key of
1787 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1788 be different at the 17th octet and later, after this change.
1789 The counter used in the PRF+ construction is now encoded as a
1790 big-endian integer in accordance with RFC 4402.
1791 __FreeBSD_version is bumped to 1100004.
1794 The WITHOUT_ATF build knob has been removed and its functionality
1795 has been subsumed into the more generic WITHOUT_TESTS. If you were
1796 using the former to disable the build of the ATF libraries, you
1797 should change your settings to use the latter.
1800 The default version of mtree is nmtree which is obtained from
1801 NetBSD. The output is generally the same, but may vary
1802 slightly. If you found you need identical output adding
1803 "-F freebsd9" to the command line should do the trick. For the
1804 time being, the old mtree is available as fmtree.
1807 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1808 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1809 1.1.4_8 and verify bsdyml not linked in, before running "make
1811 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1813 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1816 The stable/10 branch has been created in subversion from head
1823 Avoid using make -j when upgrading. While generally safe, there are
1824 sometimes problems using -j to upgrade. If your upgrade fails with
1825 -j, please try again without -j. From time to time in the past there
1826 have been problems using -j with buildworld and/or installworld. This
1827 is especially true when upgrading between "distant" versions (eg one
1828 that cross a major release boundary or several minor releases, or when
1829 several months have passed on the -current branch).
1831 Sometimes, obscure build problems are the result of environment
1832 poisoning. This can happen because the make utility reads its
1833 environment when searching for values for global variables. To run
1834 your build attempts in an "environmental clean room", prefix all make
1835 commands with 'env -i '. See the env(1) manual page for more details.
1837 When upgrading from one major version to another it is generally best to
1838 upgrade to the latest code in the currently installed branch first, then
1839 do an upgrade to the new branch. This is the best-tested upgrade path,
1840 and has the highest probability of being successful. Please try this
1841 approach if you encounter problems with a major version upgrade. Since
1842 the stable 4.x branch point, one has generally been able to upgrade from
1843 anywhere in the most recent stable branch to head / current (or even the
1844 last couple of stable branches). See the top of this file when there's
1847 When upgrading a live system, having a root shell around before
1848 installing anything can help undo problems. Not having a root shell
1849 around can lead to problems if pam has changed too much from your
1850 starting point to allow continued authentication after the upgrade.
1852 This file should be read as a log of events. When a later event changes
1853 information of a prior event, the prior event should not be deleted.
1854 Instead, a pointer to the entry with the new information should be
1855 placed in the old entry. Readers of this file should also sanity check
1856 older entries before relying on them blindly. Authors of new entries
1857 should write them with this in mind.
1861 When upgrading the boot ZFS pool to a new version, always follow
1864 1.) recompile and reinstall the ZFS boot loader and boot block
1865 (this is part of "make buildworld" and "make installworld")
1867 2.) update the ZFS boot block on your boot drive
1869 The following example updates the ZFS boot block on the first
1870 partition (freebsd-boot) of a GPT partitioned drive ada0:
1871 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1873 Non-boot pools do not need these updates.
1877 If you are updating from a prior version of FreeBSD (even one just
1878 a few days old), you should follow this procedure. It is the most
1879 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1881 make kernel-toolchain
1882 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1883 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1885 To test a kernel once
1886 ---------------------
1887 If you just want to boot a kernel once (because you are not sure
1888 if it works, or if you want to boot a known bad kernel to provide
1889 debugging information) run
1890 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1891 nextboot -k testkernel
1893 To rebuild everything and install it on the current system.
1894 -----------------------------------------------------------
1895 # Note: sometimes if you are running current you gotta do more than
1896 # is listed here if you are upgrading from a really old current.
1898 <make sure you have good level 0 dumps>
1900 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1901 make installkernel KERNCONF=YOUR_KERNEL_HERE
1903 <reboot in single user> [3]
1910 To cross-install current onto a separate partition
1911 --------------------------------------------------
1912 # In this approach we use a separate partition to hold
1913 # current's root, 'usr', and 'var' directories. A partition
1914 # holding "/", "/usr" and "/var" should be about 2GB in
1917 <make sure you have good level 0 dumps>
1920 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1921 <maybe newfs current's root partition>
1922 <mount current's root partition on directory ${CURRENT_ROOT}>
1923 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1924 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1925 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1926 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1927 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1928 <reboot into current>
1929 <do a "native" rebuild/install as described in the previous section>
1930 <maybe install compatibility libraries from ports/misc/compat*>
1934 To upgrade in-place from stable to current
1935 ----------------------------------------------
1936 <make sure you have good level 0 dumps>
1938 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1939 make installkernel KERNCONF=YOUR_KERNEL_HERE
1941 <reboot in single user> [3]
1948 Make sure that you've read the UPDATING file to understand the
1949 tweaks to various things you need. At this point in the life
1950 cycle of current, things change often and you are on your own
1951 to cope. The defaults can also change, so please read ALL of
1952 the UPDATING entries.
1954 Also, if you are tracking -current, you must be subscribed to
1955 freebsd-current@freebsd.org. Make sure that before you update
1956 your sources that you have read and understood all the recent
1957 messages there. If in doubt, please track -stable which has
1958 much fewer pitfalls.
1960 [1] If you have third party modules, such as vmware, you
1961 should disable them at this point so they don't crash your
1964 [3] From the bootblocks, boot -s, and then do
1969 adjkerntz -i # if CMOS is wall time
1970 Also, when doing a major release upgrade, it is required that
1971 you boot into single user mode to do the installworld.
1973 [4] Note: This step is non-optional. Failure to do this step
1974 can result in a significant reduction in the functionality of the
1975 system. Attempting to do it by hand is not recommended and those
1976 that pursue this avenue should read this file carefully, as well
1977 as the archives of freebsd-current and freebsd-hackers mailing lists
1978 for potential gotchas. The -U option is also useful to consider.
1979 See mergemaster(8) for more information.
1981 [5] Usually this step is a no-op. However, from time to time
1982 you may need to do this if you get unknown user in the following
1983 step. It never hurts to do it all the time. You may need to
1984 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1985 install) after the buildworld before this step if you last updated
1986 from current before 20130425 or from -stable before 20130430.
1988 [6] This only deletes old files and directories. Old libraries
1989 can be deleted by "make delete-old-libs", but you have to make
1990 sure that no program is using those libraries anymore.
1992 [8] The new kernel must be able to run existing binaries used by
1993 an installworld. When upgrading across major versions, the new
1994 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1995 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1996 binaries). Failure to do so may leave you with a system that is
1997 hard to boot to recover. A GENERIC kernel will include suitable
1998 compatibility options to run binaries from older branches.
2000 Make sure that you merge any new devices from GENERIC since the
2001 last time you updated your kernel config file.
2003 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2004 "?=" instead of the "=" assignment operator, so that buildworld can
2005 override the CPUTYPE if it needs to.
2007 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2008 not on the command line, or in /etc/make.conf. buildworld will
2009 warn if it is improperly defined.
2012 This file contains a list, in reverse chronological order, of major
2013 breakages in tracking -current. It is not guaranteed to be a complete
2014 list of such breakages, and only contains entries since September 23, 2011.
2015 If you need to see UPDATING entries from before that date, you will need
2016 to fetch an UPDATING file from an older FreeBSD release.
2018 Copyright information:
2020 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2022 Redistribution, publication, translation and use, with or without
2023 modification, in full or in part, in any form or format of this
2024 document are permitted without further permission from the author.
2026 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2027 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2028 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2029 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2030 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2031 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2032 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2033 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2034 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2035 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2036 POSSIBILITY OF SUCH DAMAGE.
2038 Contact Warner Losh if you have any questions about your use of