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 updating system packages
15 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
16 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
17 the tip of head, and then rebuild without this option. The bootstrap process
18 from older version of current across the gcc/clang cutover is a bit fragile.
21 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
22 As of be70c7a50d32 it is no longer used by userspace, but it does mean
23 users may not be able to enumerate pf states if they update the kernel
24 past c021ff986e2b without first updating userspace past be70c7a50d32.
27 The 20210707 awk update brought in a change in behavior. This has
28 been corrected as of d4d252c49976. Between these dates, if you
29 installed a new awk binary, you may not be able to build a new
30 kernel because the change in behavior affected the genoffset
31 script used to build the kernel. If you did update, the fix is
32 to update your sources past the above hash and do
35 % sudo -E make install
36 to enable building kernels again.
39 awk has been updated to the latest one-true-awk version 20210215.
40 This contains a number of minor bug fixes.
43 Commit 6ae32cc8182f changed the internal KAPI between the krpc and
44 nfsd modules. As such, both need to be rebuilt from sources.
45 Bump __FreeBSD_version to 1202508.
48 Commit e9959506d2cc changed the internal KAPI between the
49 nscl.ko and nfscommon.ko modules, so they both need to be
53 Commit 0a1fdb867c72 changed the internal KAPI between
54 the krpc and NFS. As such, the krpc, nfscommon and
55 nfscl modules must all be rebuilt from sources.
56 Without this patch, NFSv4.1 mounts should not
57 be done with the nfscbd(8) daemon running, to avoid
58 needing a working back channel for server->client RPCs.
61 The make.conf(5) MALLOC_PRODUCTION variable, used for disabling and
62 enabling assertions and statistics gathering in malloc(3), has been
63 migrated to a src.conf(5) WITH/WITHOUT_MALLOC_PRODUCTION option.
65 On stable branches, WITH_MALLOC_PRODUCTION is set by default, which
66 means that malloc(3) has assertions and statistics gathering disabled,
67 for improved performance.
69 For backwards compatibility, the make.conf(5) MALLOC_PRODUCTION is still
70 honored, but it is now deprecated and undocumented.
73 The resume code now notifies devd with the 'kernel' system
74 rather than the old 'kern' subsystem to be consistent with
75 other use. The old notification will be created as well, but
76 will be removed prior to FreeBSD 14.0.
79 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
80 been upgraded to 10.0.1. Please see the 20141231 entry below for
81 information about prerequisites and upgrading, if you are not already
82 using clang 3.5.0 or higher.
85 read(2) of a directory fd is now rejected by default. root may
86 re-enable it for the entire system with the
87 security.bsd.allow_read_dir sysctl(8) MIB.
89 It may be advised to setup aliases for grep to default to `-d skip` if
90 commonly non-recursively grepping a list that includes directories and
91 the potential for the resulting stderr output is not tolerable. Example
92 aliases are now installed, commented out, in /root/.cshrc.
95 Upstream DTS from Linux 5.6 was merged and they now have the SID
96 and THS (Secure ID controller and THermal Sensor) node present.
97 The DTB overlays have now been removed from the tree for the H3/H5 and
98 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
99 deal with upstream DTS. If you are using those overlays you need to
100 remove them from loader.conf and update the DTBs on the FAT partition.
103 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
104 been upgraded to 10.0.0. Please see the 20141231 entry below for
105 information about prerequisites and upgrading, if you are not already
106 using clang 3.5.0 or higher.
109 The root certificates of the Mozilla CA Certificate Store have been
110 imported into the base system and can be managed with the certctl(8)
111 utility. If you have installed the security/ca_root_nss port or package
112 with the ETCSYMLINK option (the default), be advised that there may be
113 differences between those included in the port and those included in
114 base due to differences in nss branch used as well as general update
115 frequency. Note also that certctl(8) cannot manage certs in the
116 format used by the security/ca_root_nss port.
119 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
120 been upgraded to 9.0.1. Please see the 20141231 entry below for
121 information about prerequisites and upgrading, if you are not already
122 using clang 3.5.0 or higher.
125 The nctgpio and wbwd drivers have been moved to the superio bus.
126 If you have one of these drivers in a kernel configuration, then
127 you should add device superio to it. If you use one of these drivers
128 as a module and you compile a custom set of modules, then you should
129 add superio to the set.
132 The tap(4) driver has been folded into tun(4), and the module has been
133 renamed to tuntap. You should update any kld_list="if_tap" or
134 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
135 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
136 module instead, and "device tap" or "device tun" entries in kernel
137 config files to select the tuntap device instead.
140 ntpd no longer by default locks its pages in memory, allowing them
141 to be paged out by the kernel. Use rlimit memlock to restore
142 historic BSD behaviour. For example, add "rlimit memlock 32"
143 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
146 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
147 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
148 been removed from mount_fusefs(8). You can safely remove them from
149 your scripts, because they had no effect.
151 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
152 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
153 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
154 sysctls have been removed. If you felt the need to set any of them to
155 a non-default value, please tell asomers@FreeBSD.org why.
158 The fuse(4) module has been renamed to fusefs(4) for consistency with
159 other filesystems. You should update any kld_load="fuse" entries in
160 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
161 "options FUSE" enties in kernel config files.
164 Default permissions on the /var/account/acct file (and copies of it
165 rotated by periodic daily scripts) are changed from 0644 to 0640
166 because the file contains sensitive information that should not be
167 world-readable. If the /var/account directory must be created by
168 rc.d/accounting, the mode used is now 0750. Admins who use the
169 accounting feature are encouraged to change the mode of an existing
170 /var/account directory to 0750 or 0700.
173 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
174 been upgraded to 8.0.1. Please see the 20141231 entry below for
175 information about prerequisites and upgrading, if you are not already
176 using clang 3.5.0 or higher.
179 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
180 functionality needed for the RETPOLINE option should work properly
181 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
184 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
185 8.0.0. Please see the 20141231 entry below for information about
186 prerequisites and upgrading, if you are not already using clang 3.5.0
190 The RETPOLINE option produces non-functional ifunc-using binaries
191 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
192 Once Clang 8 is merged it may be enabled again.
195 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
196 7.0.1. Please see the 20141231 entry below for information about
197 prerequisites and upgrading, if you are not already using clang 3.5.0
201 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
202 compiled into your custom kernel, add 'device xz' statement to the
206 Iflib is no longer unconditionally compiled into the kernel. Drivers
207 using iflib and statically compiled into the kernel, now require
208 the 'device iflib' config option. For the same drivers loaded as
209 modules on kernels not having 'device iflib', the iflib.ko module
210 is loaded automatically.
213 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
214 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
215 servers that have vfs.nfsd.nfs_privport set will only allow mounts
216 from clients using a reserved port#. Since both the FreeBSD and Linux
217 NFSv4 clients use reserved port#s by default, this should not affect
221 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
222 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
223 it produces broken binaries when ifuncs are in use. Users needing
224 GNU ld should install the binutils port or package.
227 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
228 has been converted to a port (misc/ctm) and will be removed from
229 FreeBSD-13. A depreciation warning will be printed to stderr by
230 the ctm command, but the functionality will remain in base for all
234 The stable/12 branch has been created in subversion from head
238 Ports for the DRM modules have been simplified. Now, amd64 users should
239 just install the drm-kmod port. All others should install
242 Graphics hardware that's newer than about 2010 usually works with
243 drm-kmod. For hardware older than 2013, however, some users will need
244 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
245 than 2008 usually only works in drm-legacy-kmod. The graphics team can
246 only commit to hardware made since 2013 due to the complexity of the
247 market and difficulty to test all the older cards effectively. If you
248 have hardware supported by drm-kmod, you are strongly encouraged to use
249 that as you will get better support.
251 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
252 elsewhere, the drm and drm2 modules will be eliminated from the src base
253 soon (with a limited exception for arm). Please update to the package asap
254 and report any issues to x11@freebsd.org.
256 Generally, anybody using the drm*-kmod packages should add
257 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
258 cross-threading surprises, especially with automatic driver
259 loading from X11 startup. These will become the defaults in 13-current
263 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
264 custom kernel and module loading configuration files must be updated
265 accordingly. Moreover, interfaces previous presented as ixlvN to the
266 system are now exposed as iavfN and network configuration files must
267 be adjusted as necessary.
270 OpenSSL has been updated to version 1.1.1. This update included
271 additional various API changes througout the base system. It is
272 important to rebuild third-party software after upgrading. The value
273 of __FreeBSD_version has been bumped accordingly.
276 The legacy DRM modules and drivers have now been added to the loader's
277 module blacklist, in favor of loading them with kld_list in rc.conf(5).
278 The module blacklist may be overridden with the loader.conf(5)
279 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
283 The cam(4) based nda(4) driver will be used over nvd(4) by default on
284 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
285 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
286 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
290 Reproducible build mode is now on by default, in preparation for
291 FreeBSD 12.0. This eliminates build metadata such as the user,
292 host, and time from the kernel (and uname), unless the working tree
293 corresponds to a modified checkout from a version control system.
294 The previous behavior can be obtained by setting the /etc/src.conf
295 knob WITHOUT_REPRODUCIBLE_BUILD.
298 The Yarrow CSPRNG has been removed from the kernel as it has not been
299 supported by its designers since at least 2003. Fortuna has been the
300 default since FreeBSD-11.
303 devctl freeze/thaw have gone into the tree, the rc scripts have been
304 updated to use them and devmatch has been changed. You should update
305 kernel, userland and rc scripts all at the same time.
308 The default interpreter has been switched from 4th to Lua.
309 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
310 interpreter. If you have custom FORTH code you will need to set
311 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
312 src.conf for the build. This will create default hard links between
313 loader and loader_4th instead of loader and loader_lua, the new default.
314 If you are using UEFI it will create the proper hard link to loader.efi.
316 bhyve uses userboot.so. It remains 4th-only until some issues are solved
317 regarding coexisting with multiple versions of FreeBSD are resolved.
320 ls(1) now respects the COLORTERM environment variable used in other
321 systems and software to indicate that a colored terminal is both
322 supported and desired. If ls(1) is suddenly emitting colors, they may
323 be disabled again by either removing the unwanted COLORTERM from your
324 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
325 may not be observed in a future release.
328 The default pager for most commands has been changed to "less". To
329 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
333 The jedec_ts(4) driver has been removed. A superset of its functionality
334 is available in the jedec_dimm(4) driver, and the manpage for that
335 driver includes migration instructions. If you have "device jedec_ts"
336 in your kernel configuration file, it must be removed.
339 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
340 This should have no effect if the kernel is booted via BIOS/legacy boot.
341 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
342 has a buggy firmware that prevents a successful boot due to use of
346 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
347 support has been removed from the tree. These ports were
348 obsolete and/or known to be broken for many years.
351 loader.efi has been augmented to participate more fully in the
352 UEFI boot manager protocol. loader.efi will now look at the
353 BootXXXX environment variable to determine if a specific kernel
354 or root partition was specified. XXXX is derived from BootCurrent.
355 efibootmgr(8) manages these standard UEFI variables.
358 zfsloader's functionality has now been folded into loader.
359 zfsloader is no longer necessary once you've updated your
360 boot blocks. For a transition period, we will install a
361 hardlink for zfsloader to loader to allow a smooth transition
362 until the boot blocks can be updated (hard link because old
363 zfs boot blocks don't understand symlinks).
366 ARM64 now have efifb support, if you want to have serial console
367 on your arm64 board when an screen is connected and the bootloader
368 setup a frambuffer for us to use, just add :
372 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
373 an screen connected as the firmware will setup a framebuffer are that
374 u-boot will expose as an EFI framebuffer.
377 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
378 or take steps to update /etc/passwd before doing installworld on
379 existing systems. Do not skip the "mergemaster -Fp" step before
380 installworld, as described in the update procedures near the bottom
381 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
382 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
383 the ntp config file contain options that change file/dir locations.
384 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
385 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
386 taking steps to ensure that all required files/dirs are accessible
390 Big endian arm support has been removed.
393 The static environment setup in kernel configs is no longer mutually
394 exclusive with the loader(8) environment by default. In order to
395 restore the previous default behavior of disabling the loader(8)
396 environment if a static environment is present, you must specify
397 loader_env.disabled=1 in the static environment.
400 The ABI of syscalls used by management tools like sockstat and
401 netstat has been broken to allow 32-bit binaries to work on
402 64-bit kernels without modification. These programs will need
403 to match the kernel in order to function. External programs may
404 require minor modifications to accommodate a change of type in
405 structures from pointers to 64-bit virtual addresses.
408 On i386 and amd64 atomics are now inlined. Out of tree modules using
409 atomics will need to be rebuilt.
412 The '%I' format in the kern.corefile sysctl limits the number of
413 core files that a process can generate to the number stored in the
414 debug.ncores sysctl. The '%I' format is replaced by the single digit
415 index. Previously, if all indexes were taken the kernel would overwrite
416 only a core file with the highest index in a filename.
417 Currently the system will create a new core file if there is a free
418 index or if all slots are taken it will overwrite the oldest one.
421 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
422 6.0.1. Please see the 20141231 entry below for information about
423 prerequisites and upgrading, if you are not already using clang 3.5.0
427 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
428 needed to be changed to work with it. This change was made with r335763
429 and requires a mergemaster / etcupdate / etc to update the installed file.
432 r334930 changed the interface between the NFS modules, so they all
433 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
436 As of r334391 lld is the default amd64 system linker; it is installed
437 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
441 The kernel / userland interface for devinfo changed, so you'll
442 need a new kernel and userland as a pair for it to work (rebuilding
443 lib/libdevinfo is all that's required). devinfo and devmatch will
444 not work, but everything else will when there's a mismatch.
447 The on-disk format for hwpmc callchain records has changed to include
448 threadid corresponding to a given record. This changes the field offsets
449 and thus requires that libpmcstat be rebuilt before using a kernel
453 The vxge(4) driver has been removed. This driver was introduced into
454 HEAD one week before the Exar left the Ethernet market and is not
455 known to be used. If you have device vxge in your kernel config file
459 The amd64 kernel now requires a ld that supports ifunc to produce a
460 working kernel, either lld or a newer binutils. lld is built by default
461 on amd64, and the 'buildkernel' target uses it automatically. However,
462 it is not the default linker, so building the kernel the traditional
463 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
464 binutils port/package). lld will soon be default, and this requirement
467 NOTE: As of r334391 lld is the default system linker on amd64, and no
468 workaround is necessary.
471 The nxge(4) driver has been removed. This driver was for PCI-X 10g
472 cards made by s2io/Neterion. The company was aquired by Exar and
473 no longer sells or supports Ethernet products. If you have device
474 nxge in your kernel config file it must be removed.
477 The tz database (tzdb) has been updated to 2018e. This version more
478 correctly models time stamps in time zones with negative DST such as
479 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
480 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
481 time zone abbreviations and the tm_isdst flag.
484 The ixgb(4) driver has been removed. This driver was for an early and
485 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
486 quickly shifted to the long lived ixgbe family. If you have device
487 ixgb in your kernel config file it must be removed.
490 The lmc(4) driver has been removed. This was a WAN interface
491 card that was already reportedly rare in 2003, and had an ambiguous
492 license. If you have device lmc in your kernel config file it must
496 Support for Arcnet networks has been removed. If you have device
497 arcnet or device cm in your kernel config file they must be
501 Support for FDDI networks has been removed. If you have device
502 fddi or device fpa in your kernel config file they must be
506 In addition to supporting RFC 3164 formatted messages, the
507 syslogd(8) service is now capable of parsing RFC 5424 formatted
508 log messages. The main benefit of using RFC 5424 is that clients
509 may now send log messages with timestamps containing year numbers,
510 microseconds and time zone offsets.
512 Similarly, the syslog(3) C library function has been altered to
513 send RFC 5424 formatted messages to the local system logging
514 daemon. On systems using syslogd(8), this change should have no
515 negative impact, as long as syslogd(8) and the C library are
516 updated at the same time. On systems using a different system
517 logging daemon, it may be necessary to make configuration
518 adjustments, depending on the software used.
520 When using syslog-ng, add the 'syslog-protocol' flag to local
521 input sources to enable parsing of RFC 5424 formatted messages:
524 unix-dgram("/var/run/log" flags(syslog-protocol));
527 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
528 of the 'imuxsock' module to let messages be processed by the
529 regular RFC 3164/5424 parsing pipeline:
531 module(load="imuxsock" SysSock.UseSpecialParser="off")
533 Do note that these changes only affect communication between local
534 applications and syslogd(8). The format that syslogd(8) uses to
535 store messages on disk or forward messages to other systems
536 remains unchanged. syslogd(8) still uses RFC 3164 for these
537 purposes. Options to customize this behaviour will be added in the
538 future. Utilities that process log files stored in /var/log are
539 thus expected to continue to function as before.
541 __FreeBSD_version has been incremented to 1200061 to denote this
545 Support for token ring networks has been removed. If you
546 have "device token" in your kernel config you should remove
547 it. No device drivers supported token ring.
550 makefs was modified to be able to tag ISO9660 El Torito boot catalog
551 entries as EFI instead of overloading the i386 tag as done previously.
552 The amd64 mkisoimages.sh script used to build amd64 ISO images for
553 release was updated to use this. This may mean that makefs must be
554 updated before "make cdrom" can be run in the release directory. This
555 should be as simple as:
557 $ cd $SRCDIR/usr.sbin/makefs
558 $ make depend all install
561 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
562 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
563 Co-existance for the transition period will come shortly. Booting is a
564 complex environment and test coverage for Lua-enabled loaders has been
565 thin, so it would be prudent to assume it might not work and make
566 provisions for backup boot methods.
569 devmatch functionality has been turned on in devd. It will automatically
570 load drivers for unattached devices. This may cause unexpected drivers to
571 be loaded. Please report any problems to current@ and imp@freebsd.org.
574 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
575 6.0.0. Please see the 20141231 entry below for information about
576 prerequisites and upgrading, if you are not already using clang 3.5.0
580 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
581 This means it is used to link the kernel and userland libraries and
582 executables, but is not yet installed as /usr/bin/ld by default.
584 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
585 WITHOUT_LLD_BOOTSTRAP=yes
588 On i386, pmtimer has been removed. Its functionality has been folded
589 into apm. It was a no-op on ACPI in current for a while now (but was still
590 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
591 from kernel config files.
594 The use of RSS hash from the network card aka flowid has been
595 disabled by default for lagg(4) as it's currently incompatible with
596 the lacp and loadbalance protocols.
598 This can be re-enabled by setting the following in loader.conf:
599 net.link.lagg.default_use_flowid="1"
602 The SW_WATCHDOG option is no longer necessary to enable the
603 hardclock-based software watchdog if no hardware watchdog is
604 configured. As before, SW_WATCHDOG will cause the software
605 watchdog to be enabled even if a hardware watchdog is configured.
608 r326887 fixes the issue described in the 20171214 UPDATING entry.
609 r326888 flips the switch back to building GELI support always.
612 r362593 broke ZFS + GELI support for reasons unknown. However,
613 it also broke ZFS support generally, so GELI has been turned off
614 by default as the lesser evil in r326857. If you boot off ZFS and/or
615 GELI, it might not be a good time to update.
618 PowerPC users must update loader(8) by rebuilding world before
619 installing a new kernel, as the protocol connecting them has
620 changed. Without the update, loader metadata will not be passed
621 successfully to the kernel and users will have to enter their
622 root partition at the kernel mountroot prompt to continue booting.
623 Newer versions of loader can boot old kernels without issue.
626 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
627 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
628 to WITH/OUT_LOADER_GELI.
631 The naive and non-compliant support of posix_fallocate(2) in ZFS
632 has been removed as of r325320. The system call now returns EINVAL
633 when used on a ZFS file. Although the new behavior complies with the
634 standard, some consumers are not prepared to cope with it.
635 One known victim is lld prior to r325420.
638 Building in a FreeBSD src checkout will automatically create object
639 directories now rather than store files in the current directory if
640 'make obj' was not ran. Calling 'make obj' is no longer necessary.
641 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
642 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
646 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
647 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
648 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
649 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
650 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
651 The UNIFIED_OBJDIR option is a transitional feature that will be
652 removed for 12.0 release; please migrate to the new format for any
653 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
654 than hardcoding paths.
657 The native-xtools target no longer installs the files by default to the
658 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
659 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
662 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
663 options are changing from controlling the build if defined / undefined
664 to controlling the build with explicit 'yes' or 'no' values. They will
665 shift to WITH/WITHOUT options to match other options in the system.
668 libstand has turned into a private library for sys/boot use only.
669 It is no longer supported as a public interface outside of sys/boot.
672 The arm port has split armv6 into armv6 and armv7. armv7 is now
673 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
674 and are running a kernel from before r324363, you will need to add
675 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
678 When building multiple kernels using KERNCONF, non-existent KERNCONF
679 files will produce an error and buildkernel will fail. Previously
680 missing KERNCONF files silently failed giving no indication as to
681 why, only to subsequently discover during installkernel that the
682 desired kernel was never built in the first place.
685 The default serial number format for CTL LUNs has changed. This will
686 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
687 or iSCSI clients care about their LUNs' serial numbers. Users who
688 require serial number stability should hardcode serial numbers in
692 For 32-bit arm compiled for hard-float support, soft-floating point
693 binaries now always get their shared libraries from
694 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
695 /usr/libsoft also existed). Only users with a hard-float ld.so, but
696 soft-float everything else should be affected.
699 The geli password typed at boot is now hidden. To restore the previous
700 behavior, see geli(8) for configuration options.
703 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
704 sysctl values. Minor nit, but requires a rebuild of both world/kernel
708 "make check" behavior (made in ^/head@r295380) has been changed to
709 execute from a limited sandbox, as opposed to executing from
713 - The "beforecheck" and "aftercheck" targets are now specified.
714 - ${CHECKDIR} (added in commit noted above) has been removed.
715 - Legacy behavior can be enabled by setting
716 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
718 If the limited sandbox mode is enabled, "make check" will execute
719 "make distribution", then install, execute the tests, and clean up the
720 sandbox if successful.
722 The "make distribution" and "make install" targets are typically run as
723 root to set appropriate permissions and ownership at installation time.
724 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
725 environment if executing "make check" with limited sandbox mode using
726 an unprivileged user.
729 Since the switch to GPT disk labels, fsck for UFS/FFS has been
730 unable to automatically find alternate superblocks. As of r322297,
731 the information needed to find alternate superblocks has been
732 moved to the end of the area reserved for the boot block.
733 Filesystems created with a newfs of this vintage or later
734 will create the recovery information. If you have a filesystem
735 created prior to this change and wish to have a recovery block
736 created for your filesystem, you can do so by running fsck in
737 foreground mode (i.e., do not use the -p or -y options). As it
738 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
739 to which you should answer yes.
742 As of r321665, an NFSv4 server configuration that services
743 Kerberos mounts or clients that do not support the uid/gid in
744 owner/owner_group string capability, must explicitly enable
745 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
746 machine's /etc/rc.conf file.
749 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
750 Please see the 20141231 entry below for information about prerequisites
751 and upgrading, if you are not already using clang 3.5.0 or higher.
754 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
755 r-commands (rlogin, rsh, etc.) to be built with the base system.
758 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
759 a very major ABI incompatible change, so users of FreeBSD/powerpc must
760 be careful when performing source upgrades. It is best to run
761 'make installworld' from an alternate root system, either a live
762 CD/memory stick, or a temporary root partition. Additionally, all ports
763 must be recompiled. powerpc64 is largely unaffected, except in the case
764 of 32-bit compatibility. All 32-bit binaries will be affected.
767 Forward compatibility for the "ino64" project have been committed. This
768 will allow most new binaries to run on older kernels in a limited
769 fashion. This prevents many of the common foot-shooting actions in the
770 upgrade as well as the limited ability to roll back the kernel across
771 the ino64 upgrade. Complicated use cases may not work properly, though
772 enough simpler ones work to allow recovery in most situations.
775 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
776 if you require the GPL compiler.
779 The internal ABI used for communication between the NFS kernel modules
780 was changed by r320085, so __FreeBSD_version was bumped to
781 ensure all the NFS related modules are updated together.
784 The ABI of struct event was changed by extending the data
785 member to 64bit and adding ext fields. For upgrade, same
786 precautions as for the entry 20170523 "ino64" must be
790 The GNU roff toolchain has been removed from base. To render manpages
791 which are not supported by mandoc(1), man(1) can fallback on GNU roff
792 from ports (and recommends to install it).
793 To render roff(7) documents, consider using GNU roff from ports or the
794 heirloom doctools roff toolchain from ports via pkg install groff or
795 via pkg install heirloom-doctools.
798 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
799 smaller runtime footprint builds. This is useful for embedded systems
800 which only require one chipset support.
802 If you load it as a module, make sure this is in /boot/loader.conf:
806 This will load the HAL, all chip/RF backends and if_ath_pci.
807 If you have if_ath_pci in /boot/loader.conf, ensure it is after
808 if_ath or it will not load any HAL chipset support.
810 If you want to selectively load things (eg on ye cheape ARM/MIPS
811 platforms where RAM is at a premium) you should:
814 * load the chip modules in question
815 * load ath_rate, ath_dfs
817 * load if_ath_pci and/or if_ath_ahb depending upon your particular
818 bus bind type - this is where probe/attach is done.
820 For further comments/feedback, poke adrian@ .
823 The "ino64" 64-bit inode project has been committed, which extends
824 a number of types to 64 bits. Upgrading in place requires care and
825 adherence to the documented upgrade procedure.
827 If using a custom kernel configuration ensure that the
828 COMPAT_FREEBSD11 option is included (as during the upgrade the
829 system will be running the ino64 kernel with the existing world).
831 For the safest in-place upgrade begin by removing previous build
832 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
833 full procedure documented below under the heading "To rebuild
834 everything and install it on the current system." Specifically,
835 a reboot is required after installing the new kernel before
839 The NATM framework including the en(4), fatm(4), hatm(4), and
840 patm(4) devices has been removed. Consumers should plan a
841 migration before the end-of-life date for FreeBSD 11.
844 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
845 diff has not been implemented, if those are needed a newer version of
846 GNU diff is available via the diffutils package under the gdiff name.
849 As of r316810 for ipfilter, keep frags is no longer assumed when
850 keep state is specified in a rule. r316810 aligns ipfilter with
851 documentation in man pages separating keep frags from keep state.
852 This allows keep state to be specified without forcing keep frags
853 and allows keep frags to be specified independently of keep state.
854 To maintain previous behaviour, also specify keep frags with
855 keep state (as documented in ipf.conf.5).
858 arm64 builds now use the base system LLD 4.0.0 linker by default,
859 instead of requiring that the aarch64-binutils port or package be
860 installed. To continue using aarch64-binutils, set
861 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
864 The UDP optimization in entry 20160818 that added the sysctl
865 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
866 packets will no longer be treated as L3 broadcast packets.
869 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
870 use any explicitly assigned loopback address available in the jail
871 instead of using the first assigned address of the jail.
874 The ctl.ko module no longer implements the iSCSI target frontend:
875 cfiscsi.ko does instead.
877 If building cfiscsi.ko as a kernel module, the module can be loaded
878 via one of the following methods:
879 - `cfiscsi_load="YES"` in loader.conf(5).
880 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
881 - ctladm(8)/ctld(8), when compiled with iSCSI support
882 (`WITH_ISCSI=yes` in src.conf(5))
884 Please see cfiscsi(4) for more details.
887 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
888 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
889 same source (previously, the dependency of mmcsd.ko on mmc.ko was
890 missing, but mmcsd.ko now will refuse to load if it is incompatible
894 The syntax of ipfw(8) named states was changed to avoid ambiguity.
895 If you have used named states in the firewall rules, you need to modify
896 them after installworld and before rebooting. Now named states must
897 be prefixed with colon.
900 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
901 removed as the userland we provide cannot use them. The KMS version
902 (sys/dev/drm2) supports the same hardware.
905 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
906 Please see the 20141231 entry below for information about prerequisites
907 and upgrading, if you are not already using clang 3.5.0 or higher.
910 The code that provides support for ZFS .zfs/ directory functionality
911 has been reimplemented. It's not possible now to create a snapshot
912 by mkdir under .zfs/snapshot/. That should be the only user visible
916 EISA bus support has been removed. The WITH_EISA option is no longer
920 MCA bus support has been removed.
923 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
924 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
927 The EM_MULTIQUEUE kernel configuration option is deprecated now that
928 the em(4) driver conforms to iflib specifications.
931 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
932 IFLIB. If you have a custom kernel configuration that excludes em(4)
933 but you use igb(4), you need to re-add em(4) to your custom configuration.
936 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
937 Please see the 20141231 entry below for information about prerequisites
938 and upgrading, if you are not already using clang 3.5.0 or higher.
941 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
942 Please see the 20141231 entry below for information about prerequisites
943 and upgrading, if you are not already using clang 3.5.0 or higher.
946 The layout of the pmap structure has changed for powerpc to put the pmap
947 statistics at the front for all CPU variations. libkvm(3) and all tools
948 that link against it need to be recompiled.
951 isl(4) and cyapa(4) drivers now require a new driver,
952 chromebook_platform(4), to work properly on Chromebook-class hardware.
953 On other types of hardware the drivers may need to be configured using
954 device hints. Please see the corresponding manual pages for details.
957 The urtwn(4) driver was merged into rtwn(4) and now consists of
958 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
960 Also, firmware for RTL8188CE was renamed due to possible name
961 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
964 GNU rcs has been removed from base. It is available as packages:
965 - rcs: Latest GPLv3 GNU rcs version.
966 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
970 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
971 modules now requires that the kernel configuration contain the
972 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
975 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
976 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
979 Relocatable object files with the extension of .So have been renamed
980 to use an extension of .pico instead. The purpose of this change is
981 to avoid a name clash with shared libraries on case-insensitive file
982 systems. On those file systems, foo.So is the same file as foo.so.
985 GNU rcs has been turned off by default. It can (temporarily) be built
986 again by adding WITH_RCS knob in src.conf.
987 Otherwise, GNU rcs is available from packages:
988 - rcs: Latest GPLv3 GNU rcs version.
989 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
992 The backup_uses_rcs functionality has been removed from rc.subr.
995 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
996 two separate components, QUEUE_MACRO_DEBUG_TRACE and
997 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
998 QUEUE_MACRO_DEBUG behavior.
1001 r304787 changed some ioctl interfaces between the iSCSI userspace
1002 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1003 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1007 The UDP receive code has been updated to only treat incoming UDP
1008 packets that were addressed to an L2 broadcast address as L3
1009 broadcast packets. It is not expected that this will affect any
1010 standards-conforming UDP application. The new behaviour can be
1011 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1015 Remove the openbsd_poll system call.
1016 __FreeBSD_version has been bumped because of this.
1019 The stable/11 branch has been created from head@r302406.
1022 The libc stub for the pipe(2) system call has been replaced with
1023 a wrapper that calls the pipe2(2) system call and the pipe(2)
1024 system call is now only implemented by the kernels that include
1025 "options COMPAT_FREEBSD10" in their config file (this is the
1026 default). Users should ensure that this option is enabled in
1027 their kernel or upgrade userspace to r302092 before upgrading their
1031 CAM will now strip leading spaces from SCSI disks' serial numbers.
1032 This will affect users who create UFS filesystems on SCSI disks using
1033 those disk's diskid device nodes. For example, if /etc/fstab
1034 previously contained a line like
1035 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1036 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1037 transforms like gmirror may also be affected. ZFS users should
1041 The bitstring(3) API has been updated with new functionality and
1042 improved performance. But it is binary-incompatible with the old API.
1043 Objects built with the new headers may not be linked against objects
1044 built with the old headers.
1047 The brk and sbrk functions have been removed from libc on arm64.
1048 Binutils from ports has been updated to not link to these
1049 functions and should be updated to the latest version before
1050 installing a new libc.
1053 The armv6 port now defaults to hard float ABI. Limited support
1054 for running both hardfloat and soft float on the same system
1055 is available using the libraries installed with -DWITH_LIBSOFT.
1056 This has only been tested as an upgrade path for installworld
1057 and packages may fail or need manual intervention to run. New
1058 packages will be needed.
1060 To update an existing self-hosted armv6hf system, you must add
1061 TARGET_ARCH=armv6 on the make command line for both the build
1062 and the install steps.
1065 Kernel modules compiled outside of a kernel build now default to
1066 installing to /boot/modules instead of /boot/kernel. Many kernel
1067 modules built this way (such as those in ports) already overrode
1068 KMODDIR explicitly to install into /boot/modules. However,
1069 manually building and installing a module from /sys/modules will
1070 now install to /boot/modules instead of /boot/kernel.
1073 The CAM I/O scheduler has been committed to the kernel. There should be
1074 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1075 list of known rogues that claim support for this but actually corrupt
1076 data is believed to be complete, be on the lookout for data
1077 corruption. The known rogue list is believed to be complete:
1079 o Crucial MX100, M550 drives with MU01 firmware.
1080 o Micron M510 and M550 drives with MU01 firmware.
1081 o Micron M500 prior to MU07 firmware
1082 o Samsung 830, 840, and 850 all firmwares
1083 o FCCT M500 all firmwares
1085 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1086 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1087 updated firmware. Black listed drives will work correctly because these
1088 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1089 this list is the same as found in Linux, it's believed there are no
1090 other rogues in the market place. All other models from the above
1093 To be safe, if you are at all concerned, you can quirk each of your
1094 drives to prevent NCQ from being sent by setting:
1095 kern.cam.ada.X.quirks="0x2"
1096 in loader.conf. If the drive requires the 4k sector quirk, set the
1097 quirks entry to 0x3.
1100 The FAST_DEPEND build option has been removed and its functionality is
1101 now the one true way. The old mkdep(1) style of 'make depend' has
1102 been removed. See 20160311 for further details.
1105 Resource range types have grown from unsigned long to uintmax_t. All
1106 drivers, and anything using libdevinfo, need to be recompiled.
1109 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1110 builds. It no longer runs mkdep(1) during 'make depend', and the
1111 'make depend' stage can safely be skipped now as it is auto ran
1112 when building 'make all' and will generate all SRCS and DPSRCS before
1113 building anything else. Dependencies are gathered at compile time with
1114 -MF flags kept in separate .depend files per object file. Users should
1115 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1116 stale .depend files.
1119 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1120 kernel modules. Therefore, if you load any kernel modules at boot time,
1121 please install the boot loaders after you install the kernel, but before
1125 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1126 make installkernel KERNCONF=YOUR_KERNEL_HERE
1127 make -C sys/boot install
1128 <reboot in single user>
1130 Then follow the usual steps, described in the General Notes section,
1134 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1135 see the 20141231 entry below for information about prerequisites and
1136 upgrading, if you are not already using clang 3.5.0 or higher.
1139 The AIO subsystem is now a standard part of the kernel. The
1140 VFS_AIO kernel option and aio.ko kernel module have been removed.
1141 Due to stability concerns, asynchronous I/O requests are only
1142 permitted on sockets and raw disks by default. To enable
1143 asynchronous I/O requests on all file types, set the
1144 vfs.aio.enable_unsafe sysctl to a non-zero value.
1147 The ELF object manipulation tool objcopy is now provided by the
1148 ELF Tool Chain project rather than by GNU binutils. It should be a
1149 drop-in replacement, with the addition of arm64 support. The
1150 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1151 to obtain the GNU version if necessary.
1154 Building ZFS pools on top of zvols is prohibited by default. That
1155 feature has never worked safely; it's always been prone to deadlocks.
1156 Using a zvol as the backing store for a VM guest's virtual disk will
1157 still work, even if the guest is using ZFS. Legacy behavior can be
1158 restored by setting vfs.zfs.vol.recursive=1.
1161 The NONE and HPN patches has been removed from OpenSSH. They are
1162 still available in the security/openssh-portable port.
1165 With the addition of ypldap(8), a new _ypldap user is now required
1166 during installworld. "mergemaster -p" can be used to add the user
1167 prior to installworld, as documented in the handbook.
1170 The tftp loader (pxeboot) now uses the option root-path directive. As a
1171 consequence it no longer looks for a pxeboot.4th file on the tftp
1172 server. Instead it uses the regular /boot infrastructure as with the
1176 The code to start recording plug and play data into the modules has
1177 been committed. While the old tools will properly build a new kernel,
1178 a number of warnings about "unknown metadata record 4" will be produced
1179 for an older kldxref. To avoid such warnings, make sure to rebuild
1180 the kernel toolchain (or world). Make sure that you have r292078 or
1181 later when trying to build 292077 or later before rebuilding.
1184 Debug data files are now built by default with 'make buildworld' and
1185 installed with 'make installworld'. This facilitates debugging but
1186 requires more disk space both during the build and for the installed
1187 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1191 r291527 changed the internal interface between the nfsd.ko and
1192 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1193 __FreeBSD_version has been bumped because of this.
1196 Add support for unicode collation strings leads to a change of
1197 order of files listed by ls(1) for example. To get back to the old
1198 behaviour, set LC_COLLATE environment variable to "C".
1200 Databases administrators will need to reindex their databases given
1201 collation results will be different.
1203 Due to a bug in install(1) it is recommended to remove the ancient
1204 locales before running make installworld.
1206 rm -rf /usr/share/locale/*
1209 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1210 libcrypto.so.7 or libssl.so.7 must be recompiled.
1213 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1214 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1215 should be replaced with isp_2400 and isp_2500 modules respectively.
1218 The build previously allowed using 'make -n' to not recurse into
1219 sub-directories while showing what commands would be executed, and
1220 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1221 and 'make -N' will not.
1224 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1225 and etcupdate will now use this file. A custom sendmail.cf is now
1226 updated via this mechanism rather than via installworld. If you had
1227 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1228 want to remove the exclusion or change it to "always install".
1229 /etc/mail/sendmail.cf is now managed the same way regardless of
1230 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1231 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1234 Compatibility shims for legacy ATA device names have been removed.
1235 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1236 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1237 environment variables, /dev/ad* and /dev/ar* symbolic links.
1240 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1241 Please see the 20141231 entry below for information about prerequisites
1242 and upgrading, if you are not already using clang 3.5.0 or higher.
1245 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1246 and renamed from .symbols to .debug. This reduces the size requirements
1247 on the boot partition or file system and provides consistency with
1248 userland debug files.
1250 When using the supported kernel installation method the
1251 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1252 as is done with /boot/kernel.
1254 Developers wishing to maintain the historical behavior of installing
1255 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1258 The wireless drivers had undergone changes that remove the 'parent
1259 interface' from the ifconfig -l output. The rc.d network scripts
1260 used to check presence of a parent interface in the list, so old
1261 scripts would fail to start wireless networking. Thus, etcupdate(3)
1262 or mergemaster(8) run is required after kernel update, to update your
1263 rc.d scripts in /etc.
1266 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1267 These configurations are now automatically interpreted as
1268 'scrub fragment reassemble'.
1271 Kernel-loadable modules for the random(4) device are back. To use
1272 them, the kernel must have
1275 options RANDOM_LOADABLE
1277 kldload(8) can then be used to load random_fortuna.ko
1278 or random_yarrow.ko. Please note that due to the indirect
1279 function calls that the loadable modules need to provide,
1280 the build-in variants will be slightly more efficient.
1282 The random(4) kernel option RANDOM_DUMMY has been retired due to
1283 unpopularity. It was not all that useful anyway.
1286 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1287 Control over building the ELF Tool Chain tools is now provided by
1288 the WITHOUT_TOOLCHAIN knob.
1291 The polarity of Pulse Per Second (PPS) capture events with the
1292 uart(4) driver has been corrected. Prior to this change the PPS
1293 "assert" event corresponded to the trailing edge of a positive PPS
1294 pulse and the "clear" event was the leading edge of the next pulse.
1296 As the width of a PPS pulse in a typical GPS receiver is on the
1297 order of 1 millisecond, most users will not notice any significant
1298 difference with this change.
1300 Anyone who has compensated for the historical polarity reversal by
1301 configuring a negative offset equal to the pulse width will need to
1302 remove that workaround.
1305 The default group assigned to /dev/dri entries has been changed
1306 from 'wheel' to 'video' with the id of '44'. If you want to have
1307 access to the dri devices please add yourself to the video group
1310 # pw groupmod video -m $USER
1313 The menu.rc and loader.rc files will now be replaced during
1314 upgrades. Please migrate local changes to menu.rc.local and
1315 loader.rc.local instead.
1318 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1319 strings and strip have been removed. The src.conf(5) knob
1320 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1323 As ZFS requires more kernel stack pages than is the default on some
1324 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1325 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1327 Please consider using 'options KSTACK_PAGES=X' where X is greater
1328 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1331 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1332 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1333 default, i.e., they will not contain "::". For example, instead
1334 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1335 to have a more specific match, such as different map entries for
1336 IPv6:0:0 vs IPv6:0. This change requires that configuration
1337 data (including maps, files, classes, custom ruleset, etc.) must
1338 use the same format, so make certain such configuration data is
1339 upgrading. As a very simple check search for patterns like
1340 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1341 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1342 the cf option UseCompressedIPv6Addresses.
1345 The default kernel entropy-processing algorithm is now
1346 Fortuna, replacing Yarrow.
1348 Assuming you have 'device random' in your kernel config
1349 file, the configurations allow a kernel option to override
1350 this default. You may choose *ONE* of:
1352 options RANDOM_YARROW # Legacy /dev/random algorithm.
1353 options RANDOM_DUMMY # Blocking-only driver.
1355 If you have neither, you get Fortuna. For most people,
1356 read no further, Fortuna will give a /dev/random that works
1357 like it always used to, and the difference will be irrelevant.
1359 If you remove 'device random', you get *NO* kernel-processed
1360 entropy at all. This may be acceptable to folks building
1361 embedded systems, but has complications. Carry on reading,
1362 and it is assumed you know what you need.
1364 *PLEASE* read random(4) and random(9) if you are in the
1365 habit of tweaking kernel configs, and/or if you are a member
1366 of the embedded community, wanting specific and not-usual
1367 behaviour from your security subsystems.
1369 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1370 random', you will NOT have a functioning /dev/random, and
1371 many cryptographic features will not work, including SSH.
1372 You may also find strange behaviour from the random(3) set
1373 of library functions, in particular sranddev(3), srandomdev(3)
1374 and arc4random(3). The reason for this is that the KERN_ARND
1375 sysctl only returns entropy if it thinks it has some to
1376 share, and with RANDOM_DUMMY or no 'device random' this
1380 An additional fix for the issue described in the 20150614 sendmail
1381 entry below has been committed in revision 284717.
1384 FreeBSD's old make (fmake) has been removed from the system. It is
1385 available as the devel/fmake port or via pkg install fmake.
1388 The fix for the issue described in the 20150614 sendmail entry
1389 below has been committed in revision 284436. The work
1390 around described in that entry is no longer needed unless the
1391 default setting is overridden by a confDH_PARAMETERS configuration
1392 setting of '5' or pointing to a 512 bit DH parameter file.
1395 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1396 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1397 and devel/kyua to version 0.20+ and adjust any calling code to work
1398 with Kyuafile and kyua.
1401 The import of openssl to address the FreeBSD-SA-15:10.openssl
1402 security advisory includes a change which rejects handshakes
1403 with DH parameters below 768 bits. sendmail releases prior
1404 to 8.15.2 (not yet released), defaulted to a 512 bit
1405 DH parameter setting for client connections. To work around
1406 this interoperability, sendmail can be configured to use a
1407 2048 bit DH parameter by:
1409 1. Edit /etc/mail/`hostname`.mc
1410 2. If a setting for confDH_PARAMETERS does not exist or
1411 exists and is set to a string beginning with '5',
1412 replace it with '2'.
1413 3. If a setting for confDH_PARAMETERS exists and is set to
1414 a file path, create a new file with:
1415 openssl dhparam -out /path/to/file 2048
1416 4. Rebuild the .cf file:
1417 cd /etc/mail/; make; make install
1418 5. Restart sendmail:
1419 cd /etc/mail/; make restart
1421 A sendmail patch is coming, at which time this file will be
1425 Generation of legacy formatted entries have been disabled by default
1426 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1427 entries were converted to use the new format by default when the new,
1428 machine independent format have been added and supported since FreeBSD
1431 Please see the pwd_mkdb(8) manual page for further details.
1434 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1435 20141231 entry below for information about prerequisites and upgrading,
1436 if you are not already using 3.5.0 or higher.
1439 TI platform code switched to using vendor DTS files and this update
1440 may break existing systems running on Beaglebone, Beaglebone Black,
1443 - dtb files should be regenerated/reinstalled. Filenames are the
1444 same but content is different now
1445 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1446 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1447 addressing scheme is now pin 25 on /dev/gpioc3.
1448 - Pandaboard: /etc/ttys should be updated, serial console device is
1449 now /dev/ttyu2, not /dev/ttyu0
1452 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1453 If you need the GNU extension from groff soelim(1), install groff
1454 from package: pkg install groff, or via ports: textproc/groff.
1457 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1458 defined in symlink(7); previously symlinks were silently ignored.
1461 The const qualifier has been removed from iconv(3) to comply with
1462 POSIX. The ports tree is aware of this from r384038 onwards.
1465 Libraries specified by LIBADD in Makefiles must have a corresponding
1466 DPADD_<lib> variable to ensure correct dependencies. This is now
1467 enforced in src.libnames.mk.
1470 From legacy ata(4) driver was removed support for SATA controllers
1471 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1472 Kernel modules ataahci and ataadaptec were removed completely,
1473 replaced by ahci and mvs modules respectively.
1476 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1477 the 20141231 entry below for information about prerequisites and
1478 upgrading, if you are not already using 3.5.0 or higher.
1481 The 32-bit PowerPC kernel has been changed to a position-independent
1482 executable. This can only be booted with a version of loader(8)
1483 newer than January 31, 2015, so make sure to update both world and
1484 kernel before rebooting.
1487 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1488 but before r278950, the RNG was not seeded properly. Immediately
1489 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1490 ssh keys or openssl keys) that were generated w/ a kernel from that
1491 range. This does not affect programs that directly used /dev/random
1492 or /dev/urandom. All userland uses of arc4random(3) are affected.
1495 The autofs(4) ABI was changed in order to restore binary compatibility
1496 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1497 with the new kernel.
1500 The powerpc64 kernel has been changed to a position-independent
1501 executable. This can only be booted with a new version of loader(8),
1502 so make sure to update both world and kernel before rebooting.
1505 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1506 only release, no new features have been added. Please see the 20141231
1507 entry below for information about prerequisites and upgrading, if you
1508 are not already using 3.5.0.
1511 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1512 taken from the ELF Tool Chain project rather than GNU binutils. They
1513 should be drop-in replacements, with the addition of arm64 support.
1514 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1515 binutils tools, if necessary. See 20150805 for updated information.
1518 The default Unbound configuration now enables remote control
1519 using a local socket. Users who have already enabled the
1520 local_unbound service should regenerate their configuration
1521 by running "service local_unbound setup" as root.
1524 The GNU texinfo and GNU info pages have been removed.
1525 To be able to view GNU info pages please install texinfo from ports.
1528 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1530 As of this release, a prerequisite for building clang, llvm and lldb is
1531 a C++11 capable compiler and C++11 standard library. This means that to
1532 be able to successfully build the cross-tools stage of buildworld, with
1533 clang as the bootstrap compiler, your system compiler or cross compiler
1534 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1535 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1538 On any standard FreeBSD 10.x or 11.x installation, where clang and
1539 libc++ are on by default (that is, on x86 or arm), this should work out
1542 On 9.x installations where clang is enabled by default, e.g. on x86 and
1543 powerpc, libc++ will not be enabled by default, so libc++ should be
1544 built (with clang) and installed first. If both clang and libc++ are
1545 missing, build clang first, then use it to build libc++.
1547 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1548 the instructions for 9.x above.
1550 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1551 default, and do not build clang.
1553 Many embedded systems are resource constrained, and will not be able to
1554 build clang in a reasonable time, or in some cases at all. In those
1555 cases, cross building bootable systems on amd64 is a workaround.
1557 This new version of clang introduces a number of new warnings, of which
1558 the following are most likely to appear:
1562 This warns in two cases, for both C and C++:
1563 * When the code is trying to take the absolute value of an unsigned
1564 quantity, which is effectively a no-op, and almost never what was
1565 intended. The code should be fixed, if at all possible. If you are
1566 sure that the unsigned quantity can be safely cast to signed, without
1567 loss of information or undefined behavior, you can add an explicit
1568 cast, or disable the warning.
1570 * When the code is trying to take an absolute value, but the called
1571 abs() variant is for the wrong type, which can lead to truncation.
1572 If you want to disable the warning instead of fixing the code, please
1573 make sure that truncation will not occur, or it might lead to unwanted
1576 -Wtautological-undefined-compare and
1577 -Wundefined-bool-conversion
1579 These warn when C++ code is trying to compare 'this' against NULL, while
1580 'this' should never be NULL in well-defined C++ code. However, there is
1581 some legacy (pre C++11) code out there, which actively abuses this
1582 feature, which was less strictly defined in previous C++ versions.
1584 Squid and openjdk do this, for example. The warning can be turned off
1585 for C++98 and earlier, but compiling the code in C++11 mode might result
1586 in unexpected behavior; for example, the parts of the program that are
1587 unreachable could be optimized away.
1590 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1591 kernel sources have been removed. The .h files remain, since some
1592 utilities include them. This will need to be fixed later.
1593 If "mount -t oldnfs ..." is attempted, it will fail.
1594 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1595 the utilities will report errors.
1598 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1599 directories to top level SUBDIR variable when their parent
1600 directory is included in LOCAL_DIRS. Users with build systems with
1601 such hierarchies and without SUBDIR entries in the parent
1602 directory Makefiles should add them or add the directories to
1606 faith(4) and faithd(8) have been removed from the base system. Faith
1607 has been obsolete for a very long time.
1610 vt(4), the new console driver, is enabled by default. It brings
1611 support for Unicode and double-width characters, as well as
1612 support for UEFI and integration with the KMS kernel video
1615 You may need to update your console settings in /etc/rc.conf,
1616 most probably the keymap. During boot, /etc/rc.d/syscons will
1617 indicate what you need to do.
1619 vt(4) still has issues and lacks some features compared to
1620 syscons(4). See the wiki for up-to-date information:
1621 https://wiki.freebsd.org/Newcons
1623 If you want to keep using syscons(4), you can do so by adding
1624 the following line to /boot/loader.conf:
1628 pjdfstest has been integrated into kyua as an opt-in test suite.
1629 Please see share/doc/pjdfstest/README for more details on how to
1633 gperf has been removed from the base system for architectures
1634 that use clang. Ports that require gperf will obtain it from the
1638 pjdfstest has been moved from tools/regression/pjdfstest to
1642 At svn r271982, The default linux compat kernel ABI has been adjusted
1643 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1644 update. If you wish to continue using the linux-f10 compat ports,
1645 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1646 encouraged to update their linux-compat packages to linux-c6 during
1647 their next update cycle.
1650 The ofwfb driver, used to provide a graphics console on PowerPC when
1651 using vt(4), no longer allows mmap() of all physical memory. This
1652 will prevent Xorg on PowerPC with some ATI graphics cards from
1653 initializing properly unless x11-servers/xorg-server is updated to
1657 The xdev targets have been converted to using TARGET and
1658 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1661 The default unbound configuration has been modified to address
1662 issues with reverse lookups on networks that use private
1663 address ranges. If you use the local_unbound service, run
1664 "service local_unbound setup" as root to regenerate your
1665 configuration, then "service local_unbound reload" to load the
1669 The GNU texinfo and GNU info pages are not built and installed
1670 anymore, WITH_INFO knob has been added to allow to built and install
1672 UPDATE: see 20150102 entry on texinfo's removal
1675 The GNU readline library is now an INTERNALLIB - that is, it is
1676 statically linked into consumers (GDB and variants) in the base
1677 system, and the shared library is no longer installed. The
1678 devel/readline port is available for third party software that
1682 The Itanium architecture (ia64) has been removed from the list of
1683 known architectures. This is the first step in the removal of the
1687 Commit r268115 has added NFSv4.1 server support, merged from
1688 projects/nfsv4.1-server. Since this includes changes to the
1689 internal interfaces between the NFS related modules, a full
1690 build of the kernel and modules will be necessary.
1691 __FreeBSD_version has been bumped.
1694 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1695 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1696 which differs from the behaviour controlled by this knob.)
1699 Maximal length of the serial number in CTL was increased from 16 to
1700 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1701 and ctld, need to be rebuilt to work with a new kernel.
1704 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1705 1 respectively to match the upstream numbers. They were out of
1706 sync because, when they were originally added to FreeBSD, the
1707 upstream versions were not respected. These libraries are private
1708 and not yet built by default, so renumbering them should be a
1709 non-issue. However, unclean source trees will yield broken test
1710 programs once the operator executes "make delete-old-libs" after a
1711 "make installworld".
1713 Additionally, the atf-sh binary was made private by moving it into
1714 /usr/libexec/. Already-built shell test programs will keep the
1715 path to the old binary so they will break after "make delete-old"
1718 If you are using WITH_TESTS=yes (not the default), wipe the object
1719 tree and rebuild from scratch to prevent spurious test failures.
1720 This is only needed once: the misnumbered libraries and misplaced
1721 binaries have been added to OptionalObsoleteFiles.inc so they will
1722 be removed during a clean upgrade.
1725 Clang and llvm have been upgraded to 3.4.1 release.
1728 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1729 be removed to avoid issues in the future (and has been added to
1733 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1734 past, it affected all builds that used the bsd.*.mk files. The old
1735 behavior was a bug, but people may have relied upon it. To get this
1736 behavior back, you can .include /etc/src.conf from /etc/make.conf
1737 (which is still global and isn't changed). This also changes the
1738 behavior of incremental builds inside the tree of individual
1739 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1740 Although this has survived make universe and some upgrade scenarios,
1741 other upgrade scenarios may have broken. At least one form of
1742 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1743 as well... In cases where MAKESYSPATH isn't working with this
1744 setting, you'll need to set it to the full path to your tree.
1746 One side effect of all this cleaning up is that bsd.compiler.mk
1747 is no longer implicitly included by bsd.own.mk. If you wish to
1748 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1752 The lindev device has been removed since /dev/full has been made a
1753 standard device. __FreeBSD_version has been bumped.
1756 The knob WITHOUT_VI was added to the base system, which controls
1757 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1758 in order to reorder files share/termcap and didn't build ex(1) as a
1759 build tool, so building/installing with WITH_VI is highly advised for
1760 build hosts for older releases.
1762 This issue has been fixed in stable/9 and stable/10 in r277022 and
1763 r276991, respectively.
1766 The YES_HESIOD knob has been removed. It has been obsolete for
1767 a decade. Please move to using WITH_HESIOD instead or your builds
1768 will silently lack HESIOD.
1771 The uart(4) driver has been changed with respect to its handling
1772 of the low-level console. Previously the uart(4) driver prevented
1773 any process from changing the baudrate or the CLOCAL and HUPCL
1774 control flags. By removing the restrictions, operators can make
1775 changes to the serial console port without having to reboot.
1776 However, when getty(8) is started on the serial device that is
1777 associated with the low-level console, a misconfigured terminal
1778 line in /etc/ttys will now have a real impact.
1779 Before upgrading the kernel, make sure that /etc/ttys has the
1780 serial console device configured as 3wire without baudrate to
1781 preserve the previous behaviour. E.g:
1782 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1785 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1786 to improve performance. To re-enable it, if needed, run rpcbind
1787 with command line option -W.
1790 Switched back to the GPL dtc compiler due to updates in the upstream
1791 dts files not being supported by the BSDL dtc compiler. You will need
1792 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1793 may result while building dtb files during a kernel build if you fail
1794 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1797 Clang and llvm have been upgraded to 3.4 release.
1800 The nve(4) driver has been removed. Please use the nfe(4) driver
1801 for NVIDIA nForce MCP Ethernet adapters instead.
1804 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1805 This could cause certain C++ applications using shared libraries built
1806 against the previous version of libc++ to crash. The incompatibility
1807 has now been fixed, but any C++ applications or shared libraries built
1808 between r261283 and r261801 should be recompiled.
1811 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1812 capability mode support. Please note that enabling the feature in
1813 kernel is still highly recommended.
1816 OpenSSH is now built with sandbox support, and will use sandbox as
1817 the default privilege separation method. This requires Capsicum
1818 capability mode support in kernel.
1821 The libelf and libdwarf libraries have been updated to newer
1822 versions from upstream. Shared library version numbers for
1823 these two libraries were bumped. Any ports or binaries
1824 requiring these two libraries should be recompiled.
1825 __FreeBSD_version is bumped to 1100006.
1828 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1829 instead of providing an explicit one, this would prevent such
1830 Makefile from providing its own Kyuafile in the future during
1831 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1832 intervention is needed to clean an objdir if you use NO_CLEAN:
1833 # find /usr/obj -name Kyuafile | xargs rm -f
1836 The behavior of gss_pseudo_random() for the krb5 mechanism
1837 has changed, for applications requesting a longer random string
1838 than produced by the underlying enctype's pseudo-random() function.
1839 In particular, the random string produced from a session key of
1840 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1841 be different at the 17th octet and later, after this change.
1842 The counter used in the PRF+ construction is now encoded as a
1843 big-endian integer in accordance with RFC 4402.
1844 __FreeBSD_version is bumped to 1100004.
1847 The WITHOUT_ATF build knob has been removed and its functionality
1848 has been subsumed into the more generic WITHOUT_TESTS. If you were
1849 using the former to disable the build of the ATF libraries, you
1850 should change your settings to use the latter.
1853 The default version of mtree is nmtree which is obtained from
1854 NetBSD. The output is generally the same, but may vary
1855 slightly. If you found you need identical output adding
1856 "-F freebsd9" to the command line should do the trick. For the
1857 time being, the old mtree is available as fmtree.
1860 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1861 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1862 1.1.4_8 and verify bsdyml not linked in, before running "make
1864 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1866 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1869 The stable/10 branch has been created in subversion from head
1876 Avoid using make -j when upgrading. While generally safe, there are
1877 sometimes problems using -j to upgrade. If your upgrade fails with
1878 -j, please try again without -j. From time to time in the past there
1879 have been problems using -j with buildworld and/or installworld. This
1880 is especially true when upgrading between "distant" versions (eg one
1881 that cross a major release boundary or several minor releases, or when
1882 several months have passed on the -current branch).
1884 Sometimes, obscure build problems are the result of environment
1885 poisoning. This can happen because the make utility reads its
1886 environment when searching for values for global variables. To run
1887 your build attempts in an "environmental clean room", prefix all make
1888 commands with 'env -i '. See the env(1) manual page for more details.
1890 When upgrading from one major version to another it is generally best to
1891 upgrade to the latest code in the currently installed branch first, then
1892 do an upgrade to the new branch. This is the best-tested upgrade path,
1893 and has the highest probability of being successful. Please try this
1894 approach if you encounter problems with a major version upgrade. Since
1895 the stable 4.x branch point, one has generally been able to upgrade from
1896 anywhere in the most recent stable branch to head / current (or even the
1897 last couple of stable branches). See the top of this file when there's
1900 When upgrading a live system, having a root shell around before
1901 installing anything can help undo problems. Not having a root shell
1902 around can lead to problems if pam has changed too much from your
1903 starting point to allow continued authentication after the upgrade.
1905 This file should be read as a log of events. When a later event changes
1906 information of a prior event, the prior event should not be deleted.
1907 Instead, a pointer to the entry with the new information should be
1908 placed in the old entry. Readers of this file should also sanity check
1909 older entries before relying on them blindly. Authors of new entries
1910 should write them with this in mind.
1914 When upgrading the boot ZFS pool to a new version, always follow
1917 1.) recompile and reinstall the ZFS boot loader and boot block
1918 (this is part of "make buildworld" and "make installworld")
1920 2.) update the ZFS boot block on your boot drive
1922 The following example updates the ZFS boot block on the first
1923 partition (freebsd-boot) of a GPT partitioned drive ada0:
1924 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1926 Non-boot pools do not need these updates.
1930 If you are updating from a prior version of FreeBSD (even one just
1931 a few days old), you should follow this procedure. It is the most
1932 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1934 make kernel-toolchain
1935 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1936 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1938 To test a kernel once
1939 ---------------------
1940 If you just want to boot a kernel once (because you are not sure
1941 if it works, or if you want to boot a known bad kernel to provide
1942 debugging information) run
1943 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1944 nextboot -k testkernel
1946 To rebuild everything and install it on the current system.
1947 -----------------------------------------------------------
1948 # Note: sometimes if you are running current you gotta do more than
1949 # is listed here if you are upgrading from a really old current.
1951 <make sure you have good level 0 dumps>
1953 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1954 make installkernel KERNCONF=YOUR_KERNEL_HERE
1956 <reboot in single user> [3]
1963 To cross-install current onto a separate partition
1964 --------------------------------------------------
1965 # In this approach we use a separate partition to hold
1966 # current's root, 'usr', and 'var' directories. A partition
1967 # holding "/", "/usr" and "/var" should be about 2GB in
1970 <make sure you have good level 0 dumps>
1973 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1974 <maybe newfs current's root partition>
1975 <mount current's root partition on directory ${CURRENT_ROOT}>
1976 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1977 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1978 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1979 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1980 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1981 <reboot into current>
1982 <do a "native" rebuild/install as described in the previous section>
1983 <maybe install compatibility libraries from ports/misc/compat*>
1987 To upgrade in-place from stable to current
1988 ----------------------------------------------
1989 <make sure you have good level 0 dumps>
1991 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1992 make installkernel KERNCONF=YOUR_KERNEL_HERE
1994 <reboot in single user> [3]
2001 Make sure that you've read the UPDATING file to understand the
2002 tweaks to various things you need. At this point in the life
2003 cycle of current, things change often and you are on your own
2004 to cope. The defaults can also change, so please read ALL of
2005 the UPDATING entries.
2007 Also, if you are tracking -current, you must be subscribed to
2008 freebsd-current@freebsd.org. Make sure that before you update
2009 your sources that you have read and understood all the recent
2010 messages there. If in doubt, please track -stable which has
2011 much fewer pitfalls.
2013 [1] If you have third party modules, such as vmware, you
2014 should disable them at this point so they don't crash your
2017 [3] From the bootblocks, boot -s, and then do
2022 adjkerntz -i # if CMOS is wall time
2023 Also, when doing a major release upgrade, it is required that
2024 you boot into single user mode to do the installworld.
2026 [4] Note: This step is non-optional. Failure to do this step
2027 can result in a significant reduction in the functionality of the
2028 system. Attempting to do it by hand is not recommended and those
2029 that pursue this avenue should read this file carefully, as well
2030 as the archives of freebsd-current and freebsd-hackers mailing lists
2031 for potential gotchas. The -U option is also useful to consider.
2032 See mergemaster(8) for more information.
2034 [5] Usually this step is a no-op. However, from time to time
2035 you may need to do this if you get unknown user in the following
2036 step. It never hurts to do it all the time. You may need to
2037 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2038 install) after the buildworld before this step if you last updated
2039 from current before 20130425 or from -stable before 20130430.
2041 [6] This only deletes old files and directories. Old libraries
2042 can be deleted by "make delete-old-libs", but you have to make
2043 sure that no program is using those libraries anymore.
2045 [8] The new kernel must be able to run existing binaries used by
2046 an installworld. When upgrading across major versions, the new
2047 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2048 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2049 binaries). Failure to do so may leave you with a system that is
2050 hard to boot to recover. A GENERIC kernel will include suitable
2051 compatibility options to run binaries from older branches.
2053 Make sure that you merge any new devices from GENERIC since the
2054 last time you updated your kernel config file.
2056 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2057 "?=" instead of the "=" assignment operator, so that buildworld can
2058 override the CPUTYPE if it needs to.
2060 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2061 not on the command line, or in /etc/make.conf. buildworld will
2062 warn if it is improperly defined.
2065 This file contains a list, in reverse chronological order, of major
2066 breakages in tracking -current. It is not guaranteed to be a complete
2067 list of such breakages, and only contains entries since September 23, 2011.
2068 If you need to see UPDATING entries from before that date, you will need
2069 to fetch an UPDATING file from an older FreeBSD release.
2071 Copyright information:
2073 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2075 Redistribution, publication, translation and use, with or without
2076 modification, in full or in part, in any form or format of this
2077 document are permitted without further permission from the author.
2079 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2080 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2081 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2082 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2083 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2084 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2085 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2086 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2087 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2088 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2089 POSSIBILITY OF SUCH DAMAGE.
2091 Contact Warner Losh if you have any questions about your use of