1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
15 FreeBSD 13.x has many debugging features turned on, in both the kernel
16 and userland. These features attempt to detect incorrect use of
17 system primitives, and encourage loud failure through extra sanity
18 checking and fail stop semantics. They also substantially impact
19 system performance. If you want to do performance measurement,
20 benchmarking, and optimization, you'll want to turn them off. This
21 includes various WITNESS- related kernel options, INVARIANTS, malloc
22 debugging flags in userland, and various verbose features in the
23 kernel. Many developers choose to disable these features on build
24 machines to maximize performance. (To completely disable malloc
25 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
26 disable the most expensive debugging functionality run
27 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
30 The amd(8) automount daemon has been removed from the source tree.
31 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
32 amd is still available in the sysutils/am-utils port.
35 Removed brooktree driver (bktr.4) from the tree.
38 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
39 compiler in usr.bin/dtc is used on all architectures which use dtc, and
40 the GPL dtc is available (if needed) from the sysutils/dtc port.
43 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
44 is used by all supported CPU architectures.
47 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
48 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
49 Users who wish to build FreeBSD with GCC must use the external toolchain
53 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
54 has changed, users will have to rebuild all the ports that are linked to
58 The size of struct vnet and the magic cookie have changed.
59 Users need to recompile libkvm and all modules using VIMAGE
60 together with their new kernel.
63 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
64 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
65 your Makefiles and scripts to define MK_<var>=no instead as required.
67 One exception to this is that program or library Makefiles should
68 define MAN to empty rather than setting MK_MAN=no.
71 Clang/LLVM is now the default compiler and LLD the default
75 make universe no longer uses GCC 4.2.1 on any architectures.
76 Architectures not supported by in-tree Clang/LLVM require an
77 external toolchain package.
80 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
81 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
82 options default to off for all supported CPU architectures. As a
83 short-term transition aid they may be enabled via WITH_* options.
84 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
87 Support for armv5 has been disconnected and is being removed. The
88 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
89 You must now use a MACHINE_ARCH of armv6 or armv7. The default
90 MACHINE_ARCH for MACHINE=arm is now armv7.
93 Clang/LLVM is now the default compiler for all powerpc architectures.
94 LLD is now the default linker for powerpc64. The change for powerpc64
95 also includes a change to the ELFv2 ABI, incompatible with the existing
99 Kernel-loadable random(4) modules are no longer unloadable.
102 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
103 been upgraded to 9.0.1. Please see the 20141231 entry below for
104 information about prerequisites and upgrading, if you are not already
105 using clang 3.5.0 or higher.
108 r355677 has modified the internal interface used between the
109 NFS modules in the kernel. As such, they must all be upgraded
110 simultaneously. I will do a version bump for this.
113 The root certificates of the Mozilla CA Certificate Store have been
114 imported into the base system and can be managed with the certctl(8)
115 utility. If you have installed the security/ca_root_nss port or package
116 with the ETCSYMLINK option (the default), be advised that there may be
117 differences between those included in the port and those included in
118 base due to differences in nss branch used as well as general update
119 frequency. Note also that certctl(8) cannot manage certs in the
120 format used by the security/ca_root_nss port.
123 The amd(8) automount daemon has been disabled by default, and will be
124 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
128 The nctgpio and wbwd drivers have been moved to the superio bus.
129 If you have one of these drivers in a kernel configuration, then
130 you should add device superio to it. If you use one of these drivers
131 as a module and you compile a custom set of modules, then you should
132 add superio to the set.
135 KPIs for network drivers to access interface addresses have changed.
136 Users need to recompile NIC driver modules together with kernel.
139 The net.link.tap.user_open sysctl no longer prevents user opening of
140 already created /dev/tapNN devices. Access is still controlled by
141 node permissions, just like tun devices. The net.link.tap.user_open
142 sysctl is now used only to allow users to perform devfs cloning of
143 tap devices, and the subsequent open may not succeed if the user is not
144 in the appropriate group. This sysctl may be deprecated/removed
145 completely in the future.
148 mips, powerpc, and sparc64 are no longer built as part of
149 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
150 not defined, mips, powerpc, and sparc64 builds will look for
151 the xtoolchain binaries and if installed use them for universe
152 builds. As llvm 9.0 becomes vetted for these architectures, they
153 will be removed from the list.
156 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
157 been upgraded to 9.0.0. Please see the 20141231 entry below for
158 information about prerequisites and upgrading, if you are not already
159 using clang 3.5.0 or higher.
162 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
163 GENERIC. They are available as modules and can be loaded by adding
164 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
165 hptnr_load="YES", or hptrr_load="YES", respectively.
168 ntpd no longer by default locks its pages in memory, allowing them
169 to be paged out by the kernel. Use rlimit memlock to restore
170 historic BSD behaviour. For example, add "rlimit memlock 32"
171 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
174 Several of ping6's options have been renamed for better consistency
175 with ping. If you use any of -ARWXaghmrtwx, you must update your
176 scripts. See ping6(8) for details.
179 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
180 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
181 been removed from mount_fusefs(8). You can safely remove them from
182 your scripts, because they had no effect.
184 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
185 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
186 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
187 sysctls have been removed. If you felt the need to set any of them to
188 a non-default value, please tell asomers@FreeBSD.org why.
191 Default permissions on the /var/account/acct file (and copies of it
192 rotated by periodic daily scripts) are changed from 0644 to 0640
193 because the file contains sensitive information that should not be
194 world-readable. If the /var/account directory must be created by
195 rc.d/accounting, the mode used is now 0750. Admins who use the
196 accounting feature are encouraged to change the mode of an existing
197 /var/account directory to 0750 or 0700.
200 Entropy collection and the /dev/random device are no longer optional
201 components. The "device random" option has been removed.
202 Implementations of distilling algorithms can still be made loadable
203 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
206 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
207 been upgraded to 8.0.1. Please see the 20141231 entry below for
208 information about prerequisites and upgrading, if you are not already
209 using clang 3.5.0 or higher.
212 A fix was applied to i386 kernel modules to avoid panics with
213 dpcpu or vnet. Users need to recompile i386 kernel modules
214 having pcpu or vnet sections or they will refuse to load.
217 User-wired pages now have their own counter,
218 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
219 to vm.max_user_wired and changed from an unsigned int to an unsigned
220 long. bhyve VMs wired with the -S are now subject to the user
221 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
222 avoid running into the limit.
225 The IPSEC option has been removed from GENERIC. Users requiring
226 ipsec(4) must now load the ipsec(4) kernel module.
229 The tap(4) driver has been folded into tun(4), and the module has been
230 renamed to tuntap. You should update any kld_list="if_tap" or
231 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
232 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
233 module instead, and "device tap" or "device tun" entries in kernel
234 config files to select the tuntap device instead.
237 The following knobs have been added related to tradeoffs between
238 safe use of the random device and availability in the absence of
241 kern.random.initial_seeding.bypass_before_seeding: tunable; set
242 non-zero to bypass the random device prior to seeding, or zero to
243 block random requests until the random device is initially seeded.
244 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
245 availability properties.
247 kern.random.initial_seeding.read_random_bypassed_before_seeding:
248 read-only diagnostic sysctl that is set when bypass is enabled and
249 read_random(9) is bypassed, to enable programmatic handling of this
250 initial condition, if desired.
252 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
253 Similar to the above, but for for arc4random(9) initial seeding.
255 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
256 non-zero to disable warnings in dmesg when the same conditions are
257 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
258 produce warnings in dmesg when the conditions are met.
261 The loadable random module KPI has changed; the random_infra_init()
262 routine now requires a 3rd function pointer for a bool (*)(void)
263 method that returns true if the random device is seeded (and
264 therefore unblocked).
267 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
268 built from head sources between r320757 (July 6, 2017) and
269 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
270 is added to the command line.
271 nfsuserd daemons built from head sources that are post-r338192 are
272 not affected and should continue to work.
275 The fuse(4) module has been renamed to fusefs(4) for consistency with
276 other filesystems. You should update any kld_load="fuse" entries in
277 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
278 "options FUSE" entries in kernel config files.
281 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
282 8.0.0. Please see the 20141231 entry below for information about
283 prerequisites and upgrading, if you are not already using clang 3.5.0
287 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
288 compiled into your custom kernel, add 'device xz' statement to the
292 drm and drm2 have been removed from the tree. Please see
293 https://wiki.freebsd.org/Graphics for the latest information on
294 migrating to the drm ports.
297 Iflib is no longer unconditionally compiled into the kernel. Drivers
298 using iflib and statically compiled into the kernel, now require
299 the 'device iflib' config option. For the same drivers loaded as
300 modules on kernels not having 'device iflib', the iflib.ko module
301 is loaded automatically.
304 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
305 options no longer exist since r343219 and r343427 respectively;
306 nothing uses them, so they should be just removed from custom
310 r342635 changes the way efibootmgr(8) works by requiring users to add
311 the -b (bootnum) parameter for commands where the bootnum was previously
312 specified with each option. For example 'efibootmgr -B 0001' is now
313 'efibootmgr -B -b 0001'.
316 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
317 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
318 servers that have vfs.nfsd.nfs_privport set will only allow mounts
319 from clients using a reserved port#. Since both the FreeBSD and Linux
320 NFSv4 clients use reserved port#s by default, this should not affect
324 The XLP config has been removed. We can't support 64-bit atomics in this
325 kernel because it is running in 32-bit mode. XLP users must transition
326 to running a 64-bit kernel (XLP64 or XLPN32).
328 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
329 the preferred emulator today and we don't need two different ones.
331 The old sibyte / swarm / Broadcom BCM1250 support has been
332 removed from the mips port.
335 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
336 7.0.1. Please see the 20141231 entry below for information about
337 prerequisites and upgrading, if you are not already using clang 3.5.0
341 Remove the timed and netdate programs from the base tree. Setting
342 the time with these daemons has been obsolete for over a decade.
345 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
346 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
347 it produces broken binaries when ifuncs are in use. Users needing
348 GNU ld should install the binutils port or package.
351 The BSD crtbegin and crtend code has been enabled by default. It has
352 had extensive testing on amd64, arm64, and i386. It can be disabled
353 by building a world with -DWITHOUT_BSD_CRTBEGIN.
356 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
357 has been converted to a port (misc/ctm) and will be removed from
358 FreeBSD-13. It is available as a package (ctm) for all supported
362 The default newsyslog.conf(5) file has been changed to only include
363 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
364 the filenames end in '.conf' and do not begin with a '.'.
366 You should check the configuration files in these two directories match
367 this naming convention. You can verify which configuration files are
368 being included using the command:
372 Ports for the DRM modules have been simplified. Now, amd64 users should
373 just install the drm-kmod port. All others should install
376 Graphics hardware that's newer than about 2010 usually works with
377 drm-kmod. For hardware older than 2013, however, some users will need
378 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
379 than 2008 usually only works in drm-legacy-kmod. The graphics team can
380 only commit to hardware made since 2013 due to the complexity of the
381 market and difficulty to test all the older cards effectively. If you
382 have hardware supported by drm-kmod, you are strongly encouraged to use
383 that as you will get better support.
385 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
386 elsewhere, the drm and drm2 modules will be eliminated from the src base
387 soon (with a limited exception for arm). Please update to the package
388 asap and report any issues to x11@freebsd.org.
390 Generally, anybody using the drm*-kmod packages should add
391 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
392 cross-threading surprises, especially with automatic driver
393 loading from X11 startup. These will become the defaults in 13-current
397 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
398 custom kernel and module loading configuration files must be updated
399 accordingly. Moreover, interfaces previous presented as ixlvN to the
400 system are now exposed as iavfN and network configuration files must
401 be adjusted as necessary.
404 OpenSSL has been updated to version 1.1.1. This update included
405 additional various API changes throughout the base system. It is
406 important to rebuild third-party software after upgrading. The value
407 of __FreeBSD_version has been bumped accordingly.
410 The legacy DRM modules and drivers have now been added to the loader's
411 module blacklist, in favor of loading them with kld_list in rc.conf(5).
412 The module blacklist may be overridden with the loader.conf(5)
413 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
417 The cam(4) based nda(4) driver will be used over nvd(4) by default on
418 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
419 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
420 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
424 Reproducible build mode is now on by default, in preparation for
425 FreeBSD 12.0. This eliminates build metadata such as the user,
426 host, and time from the kernel (and uname), unless the working tree
427 corresponds to a modified checkout from a version control system.
428 The previous behavior can be obtained by setting the /etc/src.conf
429 knob WITHOUT_REPRODUCIBLE_BUILD.
432 The Yarrow CSPRNG has been removed from the kernel as it has not been
433 supported by its designers since at least 2003. Fortuna has been the
434 default since FreeBSD-11.
437 devctl freeze/thaw have gone into the tree, the rc scripts have been
438 updated to use them and devmatch has been changed. You should update
439 kernel, userland and rc scripts all at the same time.
442 The default interpreter has been switched from 4th to Lua.
443 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
444 interpreter. If you have custom FORTH code you will need to set
445 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
446 src.conf for the build. This will create default hard links between
447 loader and loader_4th instead of loader and loader_lua, the new default.
448 If you are using UEFI it will create the proper hard link to loader.efi.
450 bhyve uses userboot.so. It remains 4th-only until some issues are solved
451 regarding coexisting with multiple versions of FreeBSD are resolved.
454 ls(1) now respects the COLORTERM environment variable used in other
455 systems and software to indicate that a colored terminal is both
456 supported and desired. If ls(1) is suddenly emitting colors, they may
457 be disabled again by either removing the unwanted COLORTERM from your
458 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
459 may not be observed in a future release.
462 The default pager for most commands has been changed to "less". To
463 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
467 The jedec_ts(4) driver has been removed. A superset of its functionality
468 is available in the jedec_dimm(4) driver, and the manpage for that
469 driver includes migration instructions. If you have "device jedec_ts"
470 in your kernel configuration file, it must be removed.
473 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
474 This should have no effect if the kernel is booted via BIOS/legacy boot.
475 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
476 has a buggy firmware that prevents a successful boot due to use of
480 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
481 support has been removed from the tree. These ports were
482 obsolete and/or known to be broken for many years.
485 loader.efi has been augmented to participate more fully in the
486 UEFI boot manager protocol. loader.efi will now look at the
487 BootXXXX environment variable to determine if a specific kernel
488 or root partition was specified. XXXX is derived from BootCurrent.
489 efibootmgr(8) manages these standard UEFI variables.
492 zfsloader's functionality has now been folded into loader.
493 zfsloader is no longer necessary once you've updated your
494 boot blocks. For a transition period, we will install a
495 hardlink for zfsloader to loader to allow a smooth transition
496 until the boot blocks can be updated (hard link because old
497 zfs boot blocks don't understand symlinks).
500 ARM64 now have efifb support, if you want to have serial console
501 on your arm64 board when an screen is connected and the bootloader
502 setup a frame buffer for us to use, just add :
506 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
507 an screen connected as the firmware will setup a frame buffer are that
508 u-boot will expose as an EFI frame buffer.
511 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
512 or take steps to update /etc/passwd before doing installworld on
513 existing systems. Do not skip the "mergemaster -Fp" step before
514 installworld, as described in the update procedures near the bottom
515 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
516 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
517 the ntp config file contain options that change file/dir locations.
518 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
519 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
520 taking steps to ensure that all required files/dirs are accessible
524 Big endian arm support has been removed.
527 The static environment setup in kernel configs is no longer mutually
528 exclusive with the loader(8) environment by default. In order to
529 restore the previous default behavior of disabling the loader(8)
530 environment if a static environment is present, you must specify
531 loader_env.disabled=1 in the static environment.
534 The ABI of syscalls used by management tools like sockstat and
535 netstat has been broken to allow 32-bit binaries to work on
536 64-bit kernels without modification. These programs will need
537 to match the kernel in order to function. External programs may
538 require minor modifications to accommodate a change of type in
539 structures from pointers to 64-bit virtual addresses.
542 On i386 and amd64 atomics are now inlined. Out of tree modules using
543 atomics will need to be rebuilt.
546 The '%I' format in the kern.corefile sysctl limits the number of
547 core files that a process can generate to the number stored in the
548 debug.ncores sysctl. The '%I' format is replaced by the single digit
549 index. Previously, if all indexes were taken the kernel would overwrite
550 only a core file with the highest index in a filename.
551 Currently the system will create a new core file if there is a free
552 index or if all slots are taken it will overwrite the oldest one.
555 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
556 6.0.1. Please see the 20141231 entry below for information about
557 prerequisites and upgrading, if you are not already using clang 3.5.0
561 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
562 needed to be changed to work with it. This change was made with r335763
563 and requires a mergemaster / etcupdate / etc to update the installed
567 r334930 changed the interface between the NFS modules, so they all
568 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
571 As of r334391 lld is the default amd64 system linker; it is installed
572 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
576 The kernel / userland interface for devinfo changed, so you'll
577 need a new kernel and userland as a pair for it to work (rebuilding
578 lib/libdevinfo is all that's required). devinfo and devmatch will
579 not work, but everything else will when there's a mismatch.
582 The on-disk format for hwpmc callchain records has changed to include
583 threadid corresponding to a given record. This changes the field offsets
584 and thus requires that libpmcstat be rebuilt before using a kernel
588 The vxge(4) driver has been removed. This driver was introduced into
589 HEAD one week before the Exar left the Ethernet market and is not
590 known to be used. If you have device vxge in your kernel config file
594 The amd64 kernel now requires a ld that supports ifunc to produce a
595 working kernel, either lld or a newer binutils. lld is built by default
596 on amd64, and the 'buildkernel' target uses it automatically. However,
597 it is not the default linker, so building the kernel the traditional
598 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
599 binutils port/package). lld will soon be default, and this requirement
602 NOTE: As of r334391 lld is the default system linker on amd64, and no
603 workaround is necessary.
606 The nxge(4) driver has been removed. This driver was for PCI-X 10g
607 cards made by s2io/Neterion. The company was acquired by Exar and
608 no longer sells or supports Ethernet products. If you have device
609 nxge in your kernel config file it must be removed.
612 The tz database (tzdb) has been updated to 2018e. This version more
613 correctly models time stamps in time zones with negative DST such as
614 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
615 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
616 time zone abbreviations and the tm_isdst flag.
619 The ixgb(4) driver has been removed. This driver was for an early and
620 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
621 quickly shifted to the long lived ixgbe family. If you have device
622 ixgb in your kernel config file it must be removed.
625 The lmc(4) driver has been removed. This was a WAN interface
626 card that was already reportedly rare in 2003, and had an ambiguous
627 license. If you have device lmc in your kernel config file it must
631 Support for Arcnet networks has been removed. If you have device
632 arcnet or device cm in your kernel config file they must be
636 Support for FDDI networks has been removed. If you have device
637 fddi or device fpa in your kernel config file they must be
641 In addition to supporting RFC 3164 formatted messages, the
642 syslogd(8) service is now capable of parsing RFC 5424 formatted
643 log messages. The main benefit of using RFC 5424 is that clients
644 may now send log messages with timestamps containing year numbers,
645 microseconds and time zone offsets.
647 Similarly, the syslog(3) C library function has been altered to
648 send RFC 5424 formatted messages to the local system logging
649 daemon. On systems using syslogd(8), this change should have no
650 negative impact, as long as syslogd(8) and the C library are
651 updated at the same time. On systems using a different system
652 logging daemon, it may be necessary to make configuration
653 adjustments, depending on the software used.
655 When using syslog-ng, add the 'syslog-protocol' flag to local
656 input sources to enable parsing of RFC 5424 formatted messages:
659 unix-dgram("/var/run/log" flags(syslog-protocol));
662 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
663 of the 'imuxsock' module to let messages be processed by the
664 regular RFC 3164/5424 parsing pipeline:
666 module(load="imuxsock" SysSock.UseSpecialParser="off")
668 Do note that these changes only affect communication between local
669 applications and syslogd(8). The format that syslogd(8) uses to
670 store messages on disk or forward messages to other systems
671 remains unchanged. syslogd(8) still uses RFC 3164 for these
672 purposes. Options to customize this behaviour will be added in the
673 future. Utilities that process log files stored in /var/log are
674 thus expected to continue to function as before.
676 __FreeBSD_version has been incremented to 1200061 to denote this
680 Support for token ring networks has been removed. If you
681 have "device token" in your kernel config you should remove
682 it. No device drivers supported token ring.
685 makefs was modified to be able to tag ISO9660 El Torito boot catalog
686 entries as EFI instead of overloading the i386 tag as done previously.
687 The amd64 mkisoimages.sh script used to build amd64 ISO images for
688 release was updated to use this. This may mean that makefs must be
689 updated before "make cdrom" can be run in the release directory. This
690 should be as simple as:
692 $ cd $SRCDIR/usr.sbin/makefs
693 $ make depend all install
696 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
697 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
698 Co-existence for the transition period will come shortly. Booting is a
699 complex environment and test coverage for Lua-enabled loaders has been
700 thin, so it would be prudent to assume it might not work and make
701 provisions for backup boot methods.
704 devmatch functionality has been turned on in devd. It will automatically
705 load drivers for unattached devices. This may cause unexpected drivers
706 to be loaded. Please report any problems to current@ and
710 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
711 6.0.0. Please see the 20141231 entry below for information about
712 prerequisites and upgrading, if you are not already using clang 3.5.0
716 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
717 This means it is used to link the kernel and userland libraries and
718 executables, but is not yet installed as /usr/bin/ld by default.
720 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
721 WITHOUT_LLD_BOOTSTRAP=yes
724 On i386, pmtimer has been removed. Its functionality has been folded
725 into apm. It was a no-op on ACPI in current for a while now (but was
726 still needed on i386 in FreeBSD 11 and earlier). Users may need to
727 remove it from kernel config files.
730 The use of RSS hash from the network card aka flowid has been
731 disabled by default for lagg(4) as it's currently incompatible with
732 the lacp and loadbalance protocols.
734 This can be re-enabled by setting the following in loader.conf:
735 net.link.lagg.default_use_flowid="1"
738 The SW_WATCHDOG option is no longer necessary to enable the
739 hardclock-based software watchdog if no hardware watchdog is
740 configured. As before, SW_WATCHDOG will cause the software
741 watchdog to be enabled even if a hardware watchdog is configured.
744 r326887 fixes the issue described in the 20171214 UPDATING entry.
745 r326888 flips the switch back to building GELI support always.
748 r362593 broke ZFS + GELI support for reasons unknown. However,
749 it also broke ZFS support generally, so GELI has been turned off
750 by default as the lesser evil in r326857. If you boot off ZFS and/or
751 GELI, it might not be a good time to update.
754 PowerPC users must update loader(8) by rebuilding world before
755 installing a new kernel, as the protocol connecting them has
756 changed. Without the update, loader metadata will not be passed
757 successfully to the kernel and users will have to enter their
758 root partition at the kernel mountroot prompt to continue booting.
759 Newer versions of loader can boot old kernels without issue.
762 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
763 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
764 to WITH/OUT_LOADER_GELI.
767 The naive and non-compliant support of posix_fallocate(2) in ZFS
768 has been removed as of r325320. The system call now returns EINVAL
769 when used on a ZFS file. Although the new behavior complies with the
770 standard, some consumers are not prepared to cope with it.
771 One known victim is lld prior to r325420.
774 Building in a FreeBSD src checkout will automatically create object
775 directories now rather than store files in the current directory if
776 'make obj' was not ran. Calling 'make obj' is no longer necessary.
777 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
778 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
782 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
783 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
784 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
785 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
786 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
787 The UNIFIED_OBJDIR option is a transitional feature that will be
788 removed for 12.0 release; please migrate to the new format for any
789 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
790 than hardcoding paths.
793 The native-xtools target no longer installs the files by default to the
794 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
795 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
798 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
799 options are changing from controlling the build if defined / undefined
800 to controlling the build with explicit 'yes' or 'no' values. They will
801 shift to WITH/WITHOUT options to match other options in the system.
804 libstand has turned into a private library for sys/boot use only.
805 It is no longer supported as a public interface outside of sys/boot.
808 The arm port has split armv6 into armv6 and armv7. armv7 is now
809 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
810 and are running a kernel from before r324363, you will need to add
811 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
814 When building multiple kernels using KERNCONF, non-existent KERNCONF
815 files will produce an error and buildkernel will fail. Previously
816 missing KERNCONF files silently failed giving no indication as to
817 why, only to subsequently discover during installkernel that the
818 desired kernel was never built in the first place.
821 The default serial number format for CTL LUNs has changed. This will
822 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
823 or iSCSI clients care about their LUNs' serial numbers. Users who
824 require serial number stability should hardcode serial numbers in
828 For 32-bit arm compiled for hard-float support, soft-floating point
829 binaries now always get their shared libraries from
830 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
831 /usr/libsoft also existed). Only users with a hard-float ld.so, but
832 soft-float everything else should be affected.
835 The geli password typed at boot is now hidden. To restore the previous
836 behavior, see geli(8) for configuration options.
839 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
840 sysctl values. Minor nit, but requires a rebuild of both world/kernel
844 "make check" behavior (made in ^/head@r295380) has been changed to
845 execute from a limited sandbox, as opposed to executing from
849 - The "beforecheck" and "aftercheck" targets are now specified.
850 - ${CHECKDIR} (added in commit noted above) has been removed.
851 - Legacy behavior can be enabled by setting
852 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
854 If the limited sandbox mode is enabled, "make check" will execute
855 "make distribution", then install, execute the tests, and clean up the
856 sandbox if successful.
858 The "make distribution" and "make install" targets are typically run as
859 root to set appropriate permissions and ownership at installation time.
860 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
861 environment if executing "make check" with limited sandbox mode using
862 an unprivileged user.
865 Since the switch to GPT disk labels, fsck for UFS/FFS has been
866 unable to automatically find alternate superblocks. As of r322297,
867 the information needed to find alternate superblocks has been
868 moved to the end of the area reserved for the boot block.
869 Filesystems created with a newfs of this vintage or later
870 will create the recovery information. If you have a filesystem
871 created prior to this change and wish to have a recovery block
872 created for your filesystem, you can do so by running fsck in
873 foreground mode (i.e., do not use the -p or -y options). As it
874 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
875 to which you should answer yes.
878 As of r321665, an NFSv4 server configuration that services
879 Kerberos mounts or clients that do not support the uid/gid in
880 owner/owner_group string capability, must explicitly enable
881 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
882 machine's /etc/rc.conf file.
885 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
886 Please see the 20141231 entry below for information about prerequisites
887 and upgrading, if you are not already using clang 3.5.0 or higher.
890 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
891 r-commands (rlogin, rsh, etc.) to be built with the base system.
894 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
895 a very major ABI incompatible change, so users of FreeBSD/powerpc must
896 be careful when performing source upgrades. It is best to run
897 'make installworld' from an alternate root system, either a live
898 CD/memory stick, or a temporary root partition. Additionally, all ports
899 must be recompiled. powerpc64 is largely unaffected, except in the case
900 of 32-bit compatibility. All 32-bit binaries will be affected.
903 Forward compatibility for the "ino64" project have been committed. This
904 will allow most new binaries to run on older kernels in a limited
905 fashion. This prevents many of the common foot-shooting actions in the
906 upgrade as well as the limited ability to roll back the kernel across
907 the ino64 upgrade. Complicated use cases may not work properly, though
908 enough simpler ones work to allow recovery in most situations.
911 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
912 if you require the GPL compiler.
915 The internal ABI used for communication between the NFS kernel modules
916 was changed by r320085, so __FreeBSD_version was bumped to
917 ensure all the NFS related modules are updated together.
920 The ABI of struct event was changed by extending the data
921 member to 64bit and adding ext fields. For upgrade, same
922 precautions as for the entry 20170523 "ino64" must be
926 The GNU roff toolchain has been removed from base. To render manpages
927 which are not supported by mandoc(1), man(1) can fallback on GNU roff
928 from ports (and recommends to install it).
929 To render roff(7) documents, consider using GNU roff from ports or the
930 heirloom doctools roff toolchain from ports via pkg install groff or
931 via pkg install heirloom-doctools.
934 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
935 smaller runtime footprint builds. This is useful for embedded systems
936 which only require one chipset support.
938 If you load it as a module, make sure this is in /boot/loader.conf:
942 This will load the HAL, all chip/RF backends and if_ath_pci.
943 If you have if_ath_pci in /boot/loader.conf, ensure it is after
944 if_ath or it will not load any HAL chipset support.
946 If you want to selectively load things (eg on ye cheape ARM/MIPS
947 platforms where RAM is at a premium) you should:
950 * load the chip modules in question
951 * load ath_rate, ath_dfs
953 * load if_ath_pci and/or if_ath_ahb depending upon your particular
954 bus bind type - this is where probe/attach is done.
956 For further comments/feedback, poke adrian@ .
959 The "ino64" 64-bit inode project has been committed, which extends
960 a number of types to 64 bits. Upgrading in place requires care and
961 adherence to the documented upgrade procedure.
963 If using a custom kernel configuration ensure that the
964 COMPAT_FREEBSD11 option is included (as during the upgrade the
965 system will be running the ino64 kernel with the existing world).
967 For the safest in-place upgrade begin by removing previous build
968 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
969 procedure documented below under the heading "To rebuild everything and
970 install it on the current system." Specifically, a reboot is required
971 after installing the new kernel before installing world. While an
972 installworld normally works by accident from multiuser after rebooting
973 the proper kernel, there are many cases where this will fail across this
974 upgrade and installworld from single user is required.
977 The NATM framework including the en(4), fatm(4), hatm(4), and
978 patm(4) devices has been removed. Consumers should plan a
979 migration before the end-of-life date for FreeBSD 11.
982 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
983 diff has not been implemented, if those are needed a newer version of
984 GNU diff is available via the diffutils package under the gdiff name.
987 As of r316810 for ipfilter, keep frags is no longer assumed when
988 keep state is specified in a rule. r316810 aligns ipfilter with
989 documentation in man pages separating keep frags from keep state.
990 This allows keep state to be specified without forcing keep frags
991 and allows keep frags to be specified independently of keep state.
992 To maintain previous behaviour, also specify keep frags with
993 keep state (as documented in ipf.conf.5).
996 arm64 builds now use the base system LLD 4.0.0 linker by default,
997 instead of requiring that the aarch64-binutils port or package be
998 installed. To continue using aarch64-binutils, set
999 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1002 The UDP optimization in entry 20160818 that added the sysctl
1003 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1004 packets will no longer be treated as L3 broadcast packets.
1007 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1008 use any explicitly assigned loopback address available in the jail
1009 instead of using the first assigned address of the jail.
1012 The ctl.ko module no longer implements the iSCSI target frontend:
1013 cfiscsi.ko does instead.
1015 If building cfiscsi.ko as a kernel module, the module can be loaded
1016 via one of the following methods:
1017 - `cfiscsi_load="YES"` in loader.conf(5).
1018 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1019 - ctladm(8)/ctld(8), when compiled with iSCSI support
1020 (`WITH_ISCSI=yes` in src.conf(5))
1022 Please see cfiscsi(4) for more details.
1025 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1026 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1027 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1028 missing, but mmcsd.ko now will refuse to load if it is incompatible
1032 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1033 If you have used named states in the firewall rules, you need to modify
1034 them after installworld and before rebooting. Now named states must
1035 be prefixed with colon.
1038 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1039 removed as the userland we provide cannot use them. The KMS version
1040 (sys/dev/drm2) supports the same hardware.
1043 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1044 Please see the 20141231 entry below for information about prerequisites
1045 and upgrading, if you are not already using clang 3.5.0 or higher.
1048 The code that provides support for ZFS .zfs/ directory functionality
1049 has been reimplemented. It's not possible now to create a snapshot
1050 by mkdir under .zfs/snapshot/. That should be the only user visible
1054 EISA bus support has been removed. The WITH_EISA option is no longer
1058 MCA bus support has been removed.
1061 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1062 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1065 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1066 the em(4) driver conforms to iflib specifications.
1069 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1070 IFLIB. If you have a custom kernel configuration that excludes em(4)
1071 but you use igb(4), you need to re-add em(4) to your custom
1075 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1076 Please see the 20141231 entry below for information about prerequisites
1077 and upgrading, if you are not already using clang 3.5.0 or higher.
1080 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1081 Please see the 20141231 entry below for information about prerequisites
1082 and upgrading, if you are not already using clang 3.5.0 or higher.
1085 The layout of the pmap structure has changed for powerpc to put the pmap
1086 statistics at the front for all CPU variations. libkvm(3) and all tools
1087 that link against it need to be recompiled.
1090 isl(4) and cyapa(4) drivers now require a new driver,
1091 chromebook_platform(4), to work properly on Chromebook-class hardware.
1092 On other types of hardware the drivers may need to be configured using
1093 device hints. Please see the corresponding manual pages for details.
1096 The urtwn(4) driver was merged into rtwn(4) and now consists of
1097 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1099 Also, firmware for RTL8188CE was renamed due to possible name
1100 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1103 GNU rcs has been removed from base. It is available as packages:
1104 - rcs: Latest GPLv3 GNU rcs version.
1105 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1109 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1110 modules now requires that the kernel configuration contain the
1111 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1114 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1115 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1118 Relocatable object files with the extension of .So have been renamed
1119 to use an extension of .pico instead. The purpose of this change is
1120 to avoid a name clash with shared libraries on case-insensitive file
1121 systems. On those file systems, foo.So is the same file as foo.so.
1124 GNU rcs has been turned off by default. It can (temporarily) be built
1125 again by adding WITH_RCS knob in src.conf.
1126 Otherwise, GNU rcs is available from packages:
1127 - rcs: Latest GPLv3 GNU rcs version.
1128 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1131 The backup_uses_rcs functionality has been removed from rc.subr.
1134 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1135 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1136 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1137 QUEUE_MACRO_DEBUG behavior.
1140 r304787 changed some ioctl interfaces between the iSCSI userspace
1141 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1142 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1146 The UDP receive code has been updated to only treat incoming UDP
1147 packets that were addressed to an L2 broadcast address as L3
1148 broadcast packets. It is not expected that this will affect any
1149 standards-conforming UDP application. The new behaviour can be
1150 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1154 Remove the openbsd_poll system call.
1155 __FreeBSD_version has been bumped because of this.
1158 The stable/11 branch has been created from head@r302406.
1161 The libc stub for the pipe(2) system call has been replaced with
1162 a wrapper that calls the pipe2(2) system call and the pipe(2)
1163 system call is now only implemented by the kernels that include
1164 "options COMPAT_FREEBSD10" in their config file (this is the
1165 default). Users should ensure that this option is enabled in
1166 their kernel or upgrade userspace to r302092 before upgrading their
1170 CAM will now strip leading spaces from SCSI disks' serial numbers.
1171 This will affect users who create UFS filesystems on SCSI disks using
1172 those disk's diskid device nodes. For example, if /etc/fstab
1173 previously contained a line like
1174 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1175 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1176 transforms like gmirror may also be affected. ZFS users should
1180 The bitstring(3) API has been updated with new functionality and
1181 improved performance. But it is binary-incompatible with the old API.
1182 Objects built with the new headers may not be linked against objects
1183 built with the old headers.
1186 The brk and sbrk functions have been removed from libc on arm64.
1187 Binutils from ports has been updated to not link to these
1188 functions and should be updated to the latest version before
1189 installing a new libc.
1192 The armv6 port now defaults to hard float ABI. Limited support
1193 for running both hardfloat and soft float on the same system
1194 is available using the libraries installed with -DWITH_LIBSOFT.
1195 This has only been tested as an upgrade path for installworld
1196 and packages may fail or need manual intervention to run. New
1197 packages will be needed.
1199 To update an existing self-hosted armv6hf system, you must add
1200 TARGET_ARCH=armv6 on the make command line for both the build
1201 and the install steps.
1204 Kernel modules compiled outside of a kernel build now default to
1205 installing to /boot/modules instead of /boot/kernel. Many kernel
1206 modules built this way (such as those in ports) already overrode
1207 KMODDIR explicitly to install into /boot/modules. However,
1208 manually building and installing a module from /sys/modules will
1209 now install to /boot/modules instead of /boot/kernel.
1212 The CAM I/O scheduler has been committed to the kernel. There should be
1213 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1214 list of known rogues that claim support for this but actually corrupt
1215 data is believed to be complete, be on the lookout for data
1216 corruption. The known rogue list is believed to be complete:
1218 o Crucial MX100, M550 drives with MU01 firmware.
1219 o Micron M510 and M550 drives with MU01 firmware.
1220 o Micron M500 prior to MU07 firmware
1221 o Samsung 830, 840, and 850 all firmwares
1222 o FCCT M500 all firmwares
1224 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1225 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1226 updated firmware. Black listed drives will work correctly because these
1227 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1228 this list is the same as found in Linux, it's believed there are no
1229 other rogues in the market place. All other models from the above
1232 To be safe, if you are at all concerned, you can quirk each of your
1233 drives to prevent NCQ from being sent by setting:
1234 kern.cam.ada.X.quirks="0x2"
1235 in loader.conf. If the drive requires the 4k sector quirk, set the
1236 quirks entry to 0x3.
1239 The FAST_DEPEND build option has been removed and its functionality is
1240 now the one true way. The old mkdep(1) style of 'make depend' has
1241 been removed. See 20160311 for further details.
1244 Resource range types have grown from unsigned long to uintmax_t. All
1245 drivers, and anything using libdevinfo, need to be recompiled.
1248 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1249 builds. It no longer runs mkdep(1) during 'make depend', and the
1250 'make depend' stage can safely be skipped now as it is auto ran
1251 when building 'make all' and will generate all SRCS and DPSRCS before
1252 building anything else. Dependencies are gathered at compile time with
1253 -MF flags kept in separate .depend files per object file. Users should
1254 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1255 stale .depend files.
1258 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1259 kernel modules. Therefore, if you load any kernel modules at boot time,
1260 please install the boot loaders after you install the kernel, but before
1264 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1265 make installkernel KERNCONF=YOUR_KERNEL_HERE
1266 make -C sys/boot install
1267 <reboot in single user>
1269 Then follow the usual steps, described in the General Notes section,
1273 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1274 see the 20141231 entry below for information about prerequisites and
1275 upgrading, if you are not already using clang 3.5.0 or higher.
1278 The AIO subsystem is now a standard part of the kernel. The
1279 VFS_AIO kernel option and aio.ko kernel module have been removed.
1280 Due to stability concerns, asynchronous I/O requests are only
1281 permitted on sockets and raw disks by default. To enable
1282 asynchronous I/O requests on all file types, set the
1283 vfs.aio.enable_unsafe sysctl to a non-zero value.
1286 The ELF object manipulation tool objcopy is now provided by the
1287 ELF Tool Chain project rather than by GNU binutils. It should be a
1288 drop-in replacement, with the addition of arm64 support. The
1289 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1290 to obtain the GNU version if necessary.
1293 Building ZFS pools on top of zvols is prohibited by default. That
1294 feature has never worked safely; it's always been prone to deadlocks.
1295 Using a zvol as the backing store for a VM guest's virtual disk will
1296 still work, even if the guest is using ZFS. Legacy behavior can be
1297 restored by setting vfs.zfs.vol.recursive=1.
1300 The NONE and HPN patches has been removed from OpenSSH. They are
1301 still available in the security/openssh-portable port.
1304 With the addition of ypldap(8), a new _ypldap user is now required
1305 during installworld. "mergemaster -p" can be used to add the user
1306 prior to installworld, as documented in the handbook.
1309 The tftp loader (pxeboot) now uses the option root-path directive. As a
1310 consequence it no longer looks for a pxeboot.4th file on the tftp
1311 server. Instead it uses the regular /boot infrastructure as with the
1315 The code to start recording plug and play data into the modules has
1316 been committed. While the old tools will properly build a new kernel,
1317 a number of warnings about "unknown metadata record 4" will be produced
1318 for an older kldxref. To avoid such warnings, make sure to rebuild
1319 the kernel toolchain (or world). Make sure that you have r292078 or
1320 later when trying to build 292077 or later before rebuilding.
1323 Debug data files are now built by default with 'make buildworld' and
1324 installed with 'make installworld'. This facilitates debugging but
1325 requires more disk space both during the build and for the installed
1326 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1330 r291527 changed the internal interface between the nfsd.ko and
1331 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1332 __FreeBSD_version has been bumped because of this.
1335 Add support for unicode collation strings leads to a change of
1336 order of files listed by ls(1) for example. To get back to the old
1337 behaviour, set LC_COLLATE environment variable to "C".
1339 Databases administrators will need to reindex their databases given
1340 collation results will be different.
1342 Due to a bug in install(1) it is recommended to remove the ancient
1343 locales before running make installworld.
1345 rm -rf /usr/share/locale/*
1348 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1349 libcrypto.so.7 or libssl.so.7 must be recompiled.
1352 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1353 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1354 should be replaced with isp_2400 and isp_2500 modules respectively.
1357 The build previously allowed using 'make -n' to not recurse into
1358 sub-directories while showing what commands would be executed, and
1359 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1360 and 'make -N' will not.
1363 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1364 and etcupdate will now use this file. A custom sendmail.cf is now
1365 updated via this mechanism rather than via installworld. If you had
1366 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1367 want to remove the exclusion or change it to "always install".
1368 /etc/mail/sendmail.cf is now managed the same way regardless of
1369 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1370 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1373 Compatibility shims for legacy ATA device names have been removed.
1374 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1375 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1376 environment variables, /dev/ad* and /dev/ar* symbolic links.
1379 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1380 Please see the 20141231 entry below for information about prerequisites
1381 and upgrading, if you are not already using clang 3.5.0 or higher.
1384 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1385 and renamed from .symbols to .debug. This reduces the size requirements
1386 on the boot partition or file system and provides consistency with
1387 userland debug files.
1389 When using the supported kernel installation method the
1390 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1391 as is done with /boot/kernel.
1393 Developers wishing to maintain the historical behavior of installing
1394 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1397 The wireless drivers had undergone changes that remove the 'parent
1398 interface' from the ifconfig -l output. The rc.d network scripts
1399 used to check presence of a parent interface in the list, so old
1400 scripts would fail to start wireless networking. Thus, etcupdate(3)
1401 or mergemaster(8) run is required after kernel update, to update your
1402 rc.d scripts in /etc.
1405 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1406 These configurations are now automatically interpreted as
1407 'scrub fragment reassemble'.
1410 Kernel-loadable modules for the random(4) device are back. To use
1411 them, the kernel must have
1414 options RANDOM_LOADABLE
1416 kldload(8) can then be used to load random_fortuna.ko
1417 or random_yarrow.ko. Please note that due to the indirect
1418 function calls that the loadable modules need to provide,
1419 the build-in variants will be slightly more efficient.
1421 The random(4) kernel option RANDOM_DUMMY has been retired due to
1422 unpopularity. It was not all that useful anyway.
1425 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1426 Control over building the ELF Tool Chain tools is now provided by
1427 the WITHOUT_TOOLCHAIN knob.
1430 The polarity of Pulse Per Second (PPS) capture events with the
1431 uart(4) driver has been corrected. Prior to this change the PPS
1432 "assert" event corresponded to the trailing edge of a positive PPS
1433 pulse and the "clear" event was the leading edge of the next pulse.
1435 As the width of a PPS pulse in a typical GPS receiver is on the
1436 order of 1 millisecond, most users will not notice any significant
1437 difference with this change.
1439 Anyone who has compensated for the historical polarity reversal by
1440 configuring a negative offset equal to the pulse width will need to
1441 remove that workaround.
1444 The default group assigned to /dev/dri entries has been changed
1445 from 'wheel' to 'video' with the id of '44'. If you want to have
1446 access to the dri devices please add yourself to the video group
1449 # pw groupmod video -m $USER
1452 The menu.rc and loader.rc files will now be replaced during
1453 upgrades. Please migrate local changes to menu.rc.local and
1454 loader.rc.local instead.
1457 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1458 strings and strip have been removed. The src.conf(5) knob
1459 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1462 As ZFS requires more kernel stack pages than is the default on some
1463 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1464 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1466 Please consider using 'options KSTACK_PAGES=X' where X is greater
1467 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1470 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1471 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1472 default, i.e., they will not contain "::". For example, instead
1473 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1474 to have a more specific match, such as different map entries for
1475 IPv6:0:0 vs IPv6:0. This change requires that configuration
1476 data (including maps, files, classes, custom ruleset, etc.) must
1477 use the same format, so make certain such configuration data is
1478 upgrading. As a very simple check search for patterns like
1479 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1480 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1481 the cf option UseCompressedIPv6Addresses.
1484 The default kernel entropy-processing algorithm is now
1485 Fortuna, replacing Yarrow.
1487 Assuming you have 'device random' in your kernel config
1488 file, the configurations allow a kernel option to override
1489 this default. You may choose *ONE* of:
1491 options RANDOM_YARROW # Legacy /dev/random algorithm.
1492 options RANDOM_DUMMY # Blocking-only driver.
1494 If you have neither, you get Fortuna. For most people,
1495 read no further, Fortuna will give a /dev/random that works
1496 like it always used to, and the difference will be irrelevant.
1498 If you remove 'device random', you get *NO* kernel-processed
1499 entropy at all. This may be acceptable to folks building
1500 embedded systems, but has complications. Carry on reading,
1501 and it is assumed you know what you need.
1503 *PLEASE* read random(4) and random(9) if you are in the
1504 habit of tweaking kernel configs, and/or if you are a member
1505 of the embedded community, wanting specific and not-usual
1506 behaviour from your security subsystems.
1508 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1509 random', you will NOT have a functioning /dev/random, and
1510 many cryptographic features will not work, including SSH.
1511 You may also find strange behaviour from the random(3) set
1512 of library functions, in particular sranddev(3), srandomdev(3)
1513 and arc4random(3). The reason for this is that the KERN_ARND
1514 sysctl only returns entropy if it thinks it has some to
1515 share, and with RANDOM_DUMMY or no 'device random' this
1519 An additional fix for the issue described in the 20150614 sendmail
1520 entry below has been committed in revision 284717.
1523 FreeBSD's old make (fmake) has been removed from the system. It is
1524 available as the devel/fmake port or via pkg install fmake.
1527 The fix for the issue described in the 20150614 sendmail entry
1528 below has been committed in revision 284436. The work
1529 around described in that entry is no longer needed unless the
1530 default setting is overridden by a confDH_PARAMETERS configuration
1531 setting of '5' or pointing to a 512 bit DH parameter file.
1534 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1535 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1536 and devel/kyua to version 0.20+ and adjust any calling code to work
1537 with Kyuafile and kyua.
1540 The import of openssl to address the FreeBSD-SA-15:10.openssl
1541 security advisory includes a change which rejects handshakes
1542 with DH parameters below 768 bits. sendmail releases prior
1543 to 8.15.2 (not yet released), defaulted to a 512 bit
1544 DH parameter setting for client connections. To work around
1545 this interoperability, sendmail can be configured to use a
1546 2048 bit DH parameter by:
1548 1. Edit /etc/mail/`hostname`.mc
1549 2. If a setting for confDH_PARAMETERS does not exist or
1550 exists and is set to a string beginning with '5',
1551 replace it with '2'.
1552 3. If a setting for confDH_PARAMETERS exists and is set to
1553 a file path, create a new file with:
1554 openssl dhparam -out /path/to/file 2048
1555 4. Rebuild the .cf file:
1556 cd /etc/mail/; make; make install
1557 5. Restart sendmail:
1558 cd /etc/mail/; make restart
1560 A sendmail patch is coming, at which time this file will be
1564 Generation of legacy formatted entries have been disabled by default
1565 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1566 entries were converted to use the new format by default when the new,
1567 machine independent format have been added and supported since FreeBSD
1570 Please see the pwd_mkdb(8) manual page for further details.
1573 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1574 20141231 entry below for information about prerequisites and upgrading,
1575 if you are not already using 3.5.0 or higher.
1578 TI platform code switched to using vendor DTS files and this update
1579 may break existing systems running on Beaglebone, Beaglebone Black,
1582 - dtb files should be regenerated/reinstalled. Filenames are the
1583 same but content is different now
1584 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1585 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1586 addressing scheme is now pin 25 on /dev/gpioc3.
1587 - Pandaboard: /etc/ttys should be updated, serial console device is
1588 now /dev/ttyu2, not /dev/ttyu0
1591 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1592 If you need the GNU extension from groff soelim(1), install groff
1593 from package: pkg install groff, or via ports: textproc/groff.
1596 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1597 defined in symlink(7); previously symlinks were silently ignored.
1600 The const qualifier has been removed from iconv(3) to comply with
1601 POSIX. The ports tree is aware of this from r384038 onwards.
1604 Libraries specified by LIBADD in Makefiles must have a corresponding
1605 DPADD_<lib> variable to ensure correct dependencies. This is now
1606 enforced in src.libnames.mk.
1609 From legacy ata(4) driver was removed support for SATA controllers
1610 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1611 Kernel modules ataahci and ataadaptec were removed completely,
1612 replaced by ahci and mvs modules respectively.
1615 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1616 the 20141231 entry below for information about prerequisites and
1617 upgrading, if you are not already using 3.5.0 or higher.
1620 The 32-bit PowerPC kernel has been changed to a position-independent
1621 executable. This can only be booted with a version of loader(8)
1622 newer than January 31, 2015, so make sure to update both world and
1623 kernel before rebooting.
1626 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1627 but before r278950, the RNG was not seeded properly. Immediately
1628 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1629 ssh keys or openssl keys) that were generated w/ a kernel from that
1630 range. This does not affect programs that directly used /dev/random
1631 or /dev/urandom. All userland uses of arc4random(3) are affected.
1634 The autofs(4) ABI was changed in order to restore binary compatibility
1635 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1636 with the new kernel.
1639 The powerpc64 kernel has been changed to a position-independent
1640 executable. This can only be booted with a new version of loader(8),
1641 so make sure to update both world and kernel before rebooting.
1644 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1645 only release, no new features have been added. Please see the 20141231
1646 entry below for information about prerequisites and upgrading, if you
1647 are not already using 3.5.0.
1650 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1651 taken from the ELF Tool Chain project rather than GNU binutils. They
1652 should be drop-in replacements, with the addition of arm64 support.
1653 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1654 binutils tools, if necessary. See 20150805 for updated information.
1657 The default Unbound configuration now enables remote control
1658 using a local socket. Users who have already enabled the
1659 local_unbound service should regenerate their configuration
1660 by running "service local_unbound setup" as root.
1663 The GNU texinfo and GNU info pages have been removed.
1664 To be able to view GNU info pages please install texinfo from ports.
1667 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1669 As of this release, a prerequisite for building clang, llvm and lldb is
1670 a C++11 capable compiler and C++11 standard library. This means that to
1671 be able to successfully build the cross-tools stage of buildworld, with
1672 clang as the bootstrap compiler, your system compiler or cross compiler
1673 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1674 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1677 On any standard FreeBSD 10.x or 11.x installation, where clang and
1678 libc++ are on by default (that is, on x86 or arm), this should work out
1681 On 9.x installations where clang is enabled by default, e.g. on x86 and
1682 powerpc, libc++ will not be enabled by default, so libc++ should be
1683 built (with clang) and installed first. If both clang and libc++ are
1684 missing, build clang first, then use it to build libc++.
1686 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1687 the instructions for 9.x above.
1689 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1690 default, and do not build clang.
1692 Many embedded systems are resource constrained, and will not be able to
1693 build clang in a reasonable time, or in some cases at all. In those
1694 cases, cross building bootable systems on amd64 is a workaround.
1696 This new version of clang introduces a number of new warnings, of which
1697 the following are most likely to appear:
1701 This warns in two cases, for both C and C++:
1702 * When the code is trying to take the absolute value of an unsigned
1703 quantity, which is effectively a no-op, and almost never what was
1704 intended. The code should be fixed, if at all possible. If you are
1705 sure that the unsigned quantity can be safely cast to signed, without
1706 loss of information or undefined behavior, you can add an explicit
1707 cast, or disable the warning.
1709 * When the code is trying to take an absolute value, but the called
1710 abs() variant is for the wrong type, which can lead to truncation.
1711 If you want to disable the warning instead of fixing the code, please
1712 make sure that truncation will not occur, or it might lead to unwanted
1715 -Wtautological-undefined-compare and
1716 -Wundefined-bool-conversion
1718 These warn when C++ code is trying to compare 'this' against NULL, while
1719 'this' should never be NULL in well-defined C++ code. However, there is
1720 some legacy (pre C++11) code out there, which actively abuses this
1721 feature, which was less strictly defined in previous C++ versions.
1723 Squid and openjdk do this, for example. The warning can be turned off
1724 for C++98 and earlier, but compiling the code in C++11 mode might result
1725 in unexpected behavior; for example, the parts of the program that are
1726 unreachable could be optimized away.
1729 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1730 kernel sources have been removed. The .h files remain, since some
1731 utilities include them. This will need to be fixed later.
1732 If "mount -t oldnfs ..." is attempted, it will fail.
1733 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1734 the utilities will report errors.
1737 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1738 directories to top level SUBDIR variable when their parent
1739 directory is included in LOCAL_DIRS. Users with build systems with
1740 such hierarchies and without SUBDIR entries in the parent
1741 directory Makefiles should add them or add the directories to
1745 faith(4) and faithd(8) have been removed from the base system. Faith
1746 has been obsolete for a very long time.
1749 vt(4), the new console driver, is enabled by default. It brings
1750 support for Unicode and double-width characters, as well as
1751 support for UEFI and integration with the KMS kernel video
1754 You may need to update your console settings in /etc/rc.conf,
1755 most probably the keymap. During boot, /etc/rc.d/syscons will
1756 indicate what you need to do.
1758 vt(4) still has issues and lacks some features compared to
1759 syscons(4). See the wiki for up-to-date information:
1760 https://wiki.freebsd.org/Newcons
1762 If you want to keep using syscons(4), you can do so by adding
1763 the following line to /boot/loader.conf:
1767 pjdfstest has been integrated into kyua as an opt-in test suite.
1768 Please see share/doc/pjdfstest/README for more details on how to
1772 gperf has been removed from the base system for architectures
1773 that use clang. Ports that require gperf will obtain it from the
1777 pjdfstest has been moved from tools/regression/pjdfstest to
1781 At svn r271982, The default linux compat kernel ABI has been adjusted
1782 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1783 update. If you wish to continue using the linux-f10 compat ports,
1784 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1785 encouraged to update their linux-compat packages to linux-c6 during
1786 their next update cycle.
1789 The ofwfb driver, used to provide a graphics console on PowerPC when
1790 using vt(4), no longer allows mmap() of all physical memory. This
1791 will prevent Xorg on PowerPC with some ATI graphics cards from
1792 initializing properly unless x11-servers/xorg-server is updated to
1796 The xdev targets have been converted to using TARGET and
1797 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1800 The default unbound configuration has been modified to address
1801 issues with reverse lookups on networks that use private
1802 address ranges. If you use the local_unbound service, run
1803 "service local_unbound setup" as root to regenerate your
1804 configuration, then "service local_unbound reload" to load the
1808 The GNU texinfo and GNU info pages are not built and installed
1809 anymore, WITH_INFO knob has been added to allow to built and install
1811 UPDATE: see 20150102 entry on texinfo's removal
1814 The GNU readline library is now an INTERNALLIB - that is, it is
1815 statically linked into consumers (GDB and variants) in the base
1816 system, and the shared library is no longer installed. The
1817 devel/readline port is available for third party software that
1821 The Itanium architecture (ia64) has been removed from the list of
1822 known architectures. This is the first step in the removal of the
1826 Commit r268115 has added NFSv4.1 server support, merged from
1827 projects/nfsv4.1-server. Since this includes changes to the
1828 internal interfaces between the NFS related modules, a full
1829 build of the kernel and modules will be necessary.
1830 __FreeBSD_version has been bumped.
1833 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1834 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1835 which differs from the behaviour controlled by this knob.)
1838 Maximal length of the serial number in CTL was increased from 16 to
1839 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1840 and ctld, need to be rebuilt to work with a new kernel.
1843 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1844 1 respectively to match the upstream numbers. They were out of
1845 sync because, when they were originally added to FreeBSD, the
1846 upstream versions were not respected. These libraries are private
1847 and not yet built by default, so renumbering them should be a
1848 non-issue. However, unclean source trees will yield broken test
1849 programs once the operator executes "make delete-old-libs" after a
1850 "make installworld".
1852 Additionally, the atf-sh binary was made private by moving it into
1853 /usr/libexec/. Already-built shell test programs will keep the
1854 path to the old binary so they will break after "make delete-old"
1857 If you are using WITH_TESTS=yes (not the default), wipe the object
1858 tree and rebuild from scratch to prevent spurious test failures.
1859 This is only needed once: the misnumbered libraries and misplaced
1860 binaries have been added to OptionalObsoleteFiles.inc so they will
1861 be removed during a clean upgrade.
1864 Clang and llvm have been upgraded to 3.4.1 release.
1867 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1868 be removed to avoid issues in the future (and has been added to
1872 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1873 past, it affected all builds that used the bsd.*.mk files. The old
1874 behavior was a bug, but people may have relied upon it. To get this
1875 behavior back, you can .include /etc/src.conf from /etc/make.conf
1876 (which is still global and isn't changed). This also changes the
1877 behavior of incremental builds inside the tree of individual
1878 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1879 Although this has survived make universe and some upgrade scenarios,
1880 other upgrade scenarios may have broken. At least one form of
1881 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1882 as well... In cases where MAKESYSPATH isn't working with this
1883 setting, you'll need to set it to the full path to your tree.
1885 One side effect of all this cleaning up is that bsd.compiler.mk
1886 is no longer implicitly included by bsd.own.mk. If you wish to
1887 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1891 The lindev device has been removed since /dev/full has been made a
1892 standard device. __FreeBSD_version has been bumped.
1895 The knob WITHOUT_VI was added to the base system, which controls
1896 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1897 in order to reorder files share/termcap and didn't build ex(1) as a
1898 build tool, so building/installing with WITH_VI is highly advised for
1899 build hosts for older releases.
1901 This issue has been fixed in stable/9 and stable/10 in r277022 and
1902 r276991, respectively.
1905 The YES_HESIOD knob has been removed. It has been obsolete for
1906 a decade. Please move to using WITH_HESIOD instead or your builds
1907 will silently lack HESIOD.
1910 The uart(4) driver has been changed with respect to its handling
1911 of the low-level console. Previously the uart(4) driver prevented
1912 any process from changing the baudrate or the CLOCAL and HUPCL
1913 control flags. By removing the restrictions, operators can make
1914 changes to the serial console port without having to reboot.
1915 However, when getty(8) is started on the serial device that is
1916 associated with the low-level console, a misconfigured terminal
1917 line in /etc/ttys will now have a real impact.
1918 Before upgrading the kernel, make sure that /etc/ttys has the
1919 serial console device configured as 3wire without baudrate to
1920 preserve the previous behaviour. E.g:
1921 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1924 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1925 to improve performance. To re-enable it, if needed, run rpcbind
1926 with command line option -W.
1929 Switched back to the GPL dtc compiler due to updates in the upstream
1930 dts files not being supported by the BSDL dtc compiler. You will need
1931 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1932 may result while building dtb files during a kernel build if you fail
1933 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1936 Clang and llvm have been upgraded to 3.4 release.
1939 The nve(4) driver has been removed. Please use the nfe(4) driver
1940 for NVIDIA nForce MCP Ethernet adapters instead.
1943 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1944 This could cause certain C++ applications using shared libraries built
1945 against the previous version of libc++ to crash. The incompatibility
1946 has now been fixed, but any C++ applications or shared libraries built
1947 between r261283 and r261801 should be recompiled.
1950 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1951 capability mode support. Please note that enabling the feature in
1952 kernel is still highly recommended.
1955 OpenSSH is now built with sandbox support, and will use sandbox as
1956 the default privilege separation method. This requires Capsicum
1957 capability mode support in kernel.
1960 The libelf and libdwarf libraries have been updated to newer
1961 versions from upstream. Shared library version numbers for
1962 these two libraries were bumped. Any ports or binaries
1963 requiring these two libraries should be recompiled.
1964 __FreeBSD_version is bumped to 1100006.
1967 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1968 instead of providing an explicit one, this would prevent such
1969 Makefile from providing its own Kyuafile in the future during
1970 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1971 intervention is needed to clean an objdir if you use NO_CLEAN:
1972 # find /usr/obj -name Kyuafile | xargs rm -f
1975 The behavior of gss_pseudo_random() for the krb5 mechanism
1976 has changed, for applications requesting a longer random string
1977 than produced by the underlying enctype's pseudo-random() function.
1978 In particular, the random string produced from a session key of
1979 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1980 be different at the 17th octet and later, after this change.
1981 The counter used in the PRF+ construction is now encoded as a
1982 big-endian integer in accordance with RFC 4402.
1983 __FreeBSD_version is bumped to 1100004.
1986 The WITHOUT_ATF build knob has been removed and its functionality
1987 has been subsumed into the more generic WITHOUT_TESTS. If you were
1988 using the former to disable the build of the ATF libraries, you
1989 should change your settings to use the latter.
1992 The default version of mtree is nmtree which is obtained from
1993 NetBSD. The output is generally the same, but may vary
1994 slightly. If you found you need identical output adding
1995 "-F freebsd9" to the command line should do the trick. For the
1996 time being, the old mtree is available as fmtree.
1999 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2000 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2001 1.1.4_8 and verify bsdyml not linked in, before running "make
2003 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2005 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2008 The stable/10 branch has been created in subversion from head
2015 Sometimes, obscure build problems are the result of environment
2016 poisoning. This can happen because the make utility reads its
2017 environment when searching for values for global variables. To run
2018 your build attempts in an "environmental clean room", prefix all make
2019 commands with 'env -i '. See the env(1) manual page for more details.
2020 Occasionally a build failure will occur with "make -j" due to a race
2021 condition. If this happens try building again without -j, and please
2022 report a bug if it happens consistently.
2024 When upgrading from one major version to another it is generally best to
2025 upgrade to the latest code in the currently installed branch first, then
2026 do an upgrade to the new branch. This is the best-tested upgrade path,
2027 and has the highest probability of being successful. Please try this
2028 approach if you encounter problems with a major version upgrade. Since
2029 the stable 4.x branch point, one has generally been able to upgrade from
2030 anywhere in the most recent stable branch to head / current (or even the
2031 last couple of stable branches). See the top of this file when there's
2034 The update process will emit an error on an attempt to perform a build
2035 or install from a FreeBSD version below the earliest supported version.
2036 When updating from an older version the update should be performed one
2037 major release at a time, including running `make delete-old` at each
2040 When upgrading a live system, having a root shell around before
2041 installing anything can help undo problems. Not having a root shell
2042 around can lead to problems if pam has changed too much from your
2043 starting point to allow continued authentication after the upgrade.
2045 This file should be read as a log of events. When a later event changes
2046 information of a prior event, the prior event should not be deleted.
2047 Instead, a pointer to the entry with the new information should be
2048 placed in the old entry. Readers of this file should also sanity check
2049 older entries before relying on them blindly. Authors of new entries
2050 should write them with this in mind.
2054 When upgrading the boot ZFS pool to a new version, always follow
2057 1.) recompile and reinstall the ZFS boot loader and boot block
2058 (this is part of "make buildworld" and "make installworld")
2060 2.) update the ZFS boot block on your boot drive
2062 The following example updates the ZFS boot block on the first
2063 partition (freebsd-boot) of a GPT partitioned drive ada0:
2064 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2066 Non-boot pools do not need these updates.
2070 If you are updating from a prior version of FreeBSD (even one just
2071 a few days old), you should follow this procedure. It is the most
2072 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2074 make kernel-toolchain
2075 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2076 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2078 To test a kernel once
2079 ---------------------
2080 If you just want to boot a kernel once (because you are not sure
2081 if it works, or if you want to boot a known bad kernel to provide
2082 debugging information) run
2083 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2084 nextboot -k testkernel
2086 To rebuild everything and install it on the current system.
2087 -----------------------------------------------------------
2088 # Note: sometimes if you are running current you gotta do more than
2089 # is listed here if you are upgrading from a really old current.
2091 <make sure you have good level 0 dumps>
2093 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2094 make installkernel KERNCONF=YOUR_KERNEL_HERE
2096 <reboot in single user> [3]
2103 To cross-install current onto a separate partition
2104 --------------------------------------------------
2105 # In this approach we use a separate partition to hold
2106 # current's root, 'usr', and 'var' directories. A partition
2107 # holding "/", "/usr" and "/var" should be about 2GB in
2110 <make sure you have good level 0 dumps>
2113 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2114 <maybe newfs current's root partition>
2115 <mount current's root partition on directory ${CURRENT_ROOT}>
2116 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2117 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2118 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2119 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2120 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2121 <reboot into current>
2122 <do a "native" rebuild/install as described in the previous section>
2123 <maybe install compatibility libraries from ports/misc/compat*>
2127 To upgrade in-place from stable to current
2128 ----------------------------------------------
2129 <make sure you have good level 0 dumps>
2131 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2132 make installkernel KERNCONF=YOUR_KERNEL_HERE
2134 <reboot in single user> [3]
2141 Make sure that you've read the UPDATING file to understand the
2142 tweaks to various things you need. At this point in the life
2143 cycle of current, things change often and you are on your own
2144 to cope. The defaults can also change, so please read ALL of
2145 the UPDATING entries.
2147 Also, if you are tracking -current, you must be subscribed to
2148 freebsd-current@freebsd.org. Make sure that before you update
2149 your sources that you have read and understood all the recent
2150 messages there. If in doubt, please track -stable which has
2151 much fewer pitfalls.
2153 [1] If you have third party modules, such as vmware, you
2154 should disable them at this point so they don't crash your
2157 [3] From the bootblocks, boot -s, and then do
2161 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2162 cd src # full path to source
2163 adjkerntz -i # if CMOS is wall time
2164 Also, when doing a major release upgrade, it is required that
2165 you boot into single user mode to do the installworld.
2167 [4] Note: This step is non-optional. Failure to do this step
2168 can result in a significant reduction in the functionality of the
2169 system. Attempting to do it by hand is not recommended and those
2170 that pursue this avenue should read this file carefully, as well
2171 as the archives of freebsd-current and freebsd-hackers mailing lists
2172 for potential gotchas. The -U option is also useful to consider.
2173 See mergemaster(8) for more information.
2175 [5] Usually this step is a no-op. However, from time to time
2176 you may need to do this if you get unknown user in the following
2177 step. It never hurts to do it all the time. You may need to
2178 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2179 install) after the buildworld before this step if you last updated
2180 from current before 20130425 or from -stable before 20130430.
2182 [6] This only deletes old files and directories. Old libraries
2183 can be deleted by "make delete-old-libs", but you have to make
2184 sure that no program is using those libraries anymore.
2186 [8] The new kernel must be able to run existing binaries used by an
2187 installworld. When upgrading across major versions, the new kernel's
2188 configuration must include the correct COMPAT_FREEBSD<n> option for
2189 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2190 to do so may leave you with a system that is hard to boot to recover. A
2191 GENERIC kernel will include suitable compatibility options to run
2192 binaries from older branches. Note that the ability to run binaries
2193 from unsupported branches is not guaranteed.
2195 Make sure that you merge any new devices from GENERIC since the
2196 last time you updated your kernel config file. Options also
2197 change over time, so you may need to adjust your custom kernels
2200 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2201 "?=" instead of the "=" assignment operator, so that buildworld can
2202 override the CPUTYPE if it needs to.
2204 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2205 not on the command line, or in /etc/make.conf. buildworld will
2206 warn if it is improperly defined.
2209 This file contains a list, in reverse chronological order, of major
2210 breakages in tracking -current. It is not guaranteed to be a complete
2211 list of such breakages, and only contains entries since September 23, 2011.
2212 If you need to see UPDATING entries from before that date, you will need
2213 to fetch an UPDATING file from an older FreeBSD release.
2215 Copyright information:
2217 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2219 Redistribution, publication, translation and use, with or without
2220 modification, in full or in part, in any form or format of this
2221 document are permitted without further permission from the author.
2223 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2224 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2225 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2226 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2227 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2228 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2229 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2230 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2231 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2232 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2233 POSSIBILITY OF SUCH DAMAGE.
2235 Contact Warner Losh if you have any questions about your use of