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 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
31 been upgraded to 10.0.0. Please see the 20141231 entry below for
32 information about prerequisites and upgrading, if you are not already
33 using clang 3.5.0 or higher.
36 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
37 is used by all supported CPU architectures.
40 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
41 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
42 Users who wish to build FreeBSD with GCC must use the external toolchain
46 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
47 has changed, users will have to rebuild all the ports that are linked to
51 The size of struct vnet and the magic cookie have changed.
52 Users need to recompile libkvm and all modules using VIMAGE
53 together with their new kernel.
56 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
57 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
58 your Makefiles and scripts to define MK_<var>=no instead as required.
60 One exception to this is that program or library Makefiles should
61 define MAN to empty rather than setting MK_MAN=no.
64 Clang/LLVM is now the default compiler and LLD the default
68 make universe no longer uses GCC 4.2.1 on any architectures.
69 Architectures not supported by in-tree Clang/LLVM require an
70 external toolchain package.
73 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
74 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
75 options default to off for all supported CPU architectures. As a
76 short-term transition aid they may be enabled via WITH_* options.
77 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
80 Support for armv5 has been disconnected and is being removed. The
81 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
82 You must now use a MACHINE_ARCH of armv6 or armv7. The default
83 MACHINE_ARCH for MACHINE=arm is now armv7.
86 Clang/LLVM is now the default compiler for all powerpc architectures.
87 LLD is now the default linker for powerpc64. The change for powerpc64
88 also includes a change to the ELFv2 ABI, incompatible with the existing
92 Kernel-loadable random(4) modules are no longer unloadable.
95 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
96 been upgraded to 9.0.1. Please see the 20141231 entry below for
97 information about prerequisites and upgrading, if you are not already
98 using clang 3.5.0 or higher.
101 r355677 has modified the internal interface used between the
102 NFS modules in the kernel. As such, they must all be upgraded
103 simultaneously. I will do a version bump for this.
106 The root certificates of the Mozilla CA Certificate Store have been
107 imported into the base system and can be managed with the certctl(8)
108 utility. If you have installed the security/ca_root_nss port or package
109 with the ETCSYMLINK option (the default), be advised that there may be
110 differences between those included in the port and those included in
111 base due to differences in nss branch used as well as general update
112 frequency. Note also that certctl(8) cannot manage certs in the
113 format used by the security/ca_root_nss port.
116 The amd(8) automount daemon has been disabled by default, and will be
117 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
121 The nctgpio and wbwd drivers have been moved to the superio bus.
122 If you have one of these drivers in a kernel configuration, then
123 you should add device superio to it. If you use one of these drivers
124 as a module and you compile a custom set of modules, then you should
125 add superio to the set.
128 KPIs for network drivers to access interface addresses have changed.
129 Users need to recompile NIC driver modules together with kernel.
132 The net.link.tap.user_open sysctl no longer prevents user opening of
133 already created /dev/tapNN devices. Access is still controlled by
134 node permissions, just like tun devices. The net.link.tap.user_open
135 sysctl is now used only to allow users to perform devfs cloning of
136 tap devices, and the subsequent open may not succeed if the user is not
137 in the appropriate group. This sysctl may be deprecated/removed
138 completely in the future.
141 mips, powerpc, and sparc64 are no longer built as part of
142 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
143 not defined, mips, powerpc, and sparc64 builds will look for
144 the xtoolchain binaries and if installed use them for universe
145 builds. As llvm 9.0 becomes vetted for these architectures, they
146 will be removed from the list.
149 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
150 been upgraded to 9.0.0. Please see the 20141231 entry below for
151 information about prerequisites and upgrading, if you are not already
152 using clang 3.5.0 or higher.
155 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
156 GENERIC. They are available as modules and can be loaded by adding
157 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
158 hptnr_load="YES", or hptrr_load="YES", respectively.
161 ntpd no longer by default locks its pages in memory, allowing them
162 to be paged out by the kernel. Use rlimit memlock to restore
163 historic BSD behaviour. For example, add "rlimit memlock 32"
164 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
167 Several of ping6's options have been renamed for better consistency
168 with ping. If you use any of -ARWXaghmrtwx, you must update your
169 scripts. See ping6(8) for details.
172 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
173 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
174 been removed from mount_fusefs(8). You can safely remove them from
175 your scripts, because they had no effect.
177 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
178 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
179 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
180 sysctls have been removed. If you felt the need to set any of them to
181 a non-default value, please tell asomers@FreeBSD.org why.
184 Default permissions on the /var/account/acct file (and copies of it
185 rotated by periodic daily scripts) are changed from 0644 to 0640
186 because the file contains sensitive information that should not be
187 world-readable. If the /var/account directory must be created by
188 rc.d/accounting, the mode used is now 0750. Admins who use the
189 accounting feature are encouraged to change the mode of an existing
190 /var/account directory to 0750 or 0700.
193 Entropy collection and the /dev/random device are no longer optional
194 components. The "device random" option has been removed.
195 Implementations of distilling algorithms can still be made loadable
196 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
199 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
200 been upgraded to 8.0.1. Please see the 20141231 entry below for
201 information about prerequisites and upgrading, if you are not already
202 using clang 3.5.0 or higher.
205 A fix was applied to i386 kernel modules to avoid panics with
206 dpcpu or vnet. Users need to recompile i386 kernel modules
207 having pcpu or vnet sections or they will refuse to load.
210 User-wired pages now have their own counter,
211 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
212 to vm.max_user_wired and changed from an unsigned int to an unsigned
213 long. bhyve VMs wired with the -S are now subject to the user
214 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
215 avoid running into the limit.
218 The IPSEC option has been removed from GENERIC. Users requiring
219 ipsec(4) must now load the ipsec(4) kernel module.
222 The tap(4) driver has been folded into tun(4), and the module has been
223 renamed to tuntap. You should update any kld_list="if_tap" or
224 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
225 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
226 module instead, and "device tap" or "device tun" entries in kernel
227 config files to select the tuntap device instead.
230 The following knobs have been added related to tradeoffs between
231 safe use of the random device and availability in the absence of
234 kern.random.initial_seeding.bypass_before_seeding: tunable; set
235 non-zero to bypass the random device prior to seeding, or zero to
236 block random requests until the random device is initially seeded.
237 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
238 availability properties.
240 kern.random.initial_seeding.read_random_bypassed_before_seeding:
241 read-only diagnostic sysctl that is set when bypass is enabled and
242 read_random(9) is bypassed, to enable programmatic handling of this
243 initial condition, if desired.
245 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
246 Similar to the above, but for for arc4random(9) initial seeding.
248 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
249 non-zero to disable warnings in dmesg when the same conditions are
250 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
251 produce warnings in dmesg when the conditions are met.
254 The loadable random module KPI has changed; the random_infra_init()
255 routine now requires a 3rd function pointer for a bool (*)(void)
256 method that returns true if the random device is seeded (and
257 therefore unblocked).
260 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
261 built from head sources between r320757 (July 6, 2017) and
262 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
263 is added to the command line.
264 nfsuserd daemons built from head sources that are post-r338192 are
265 not affected and should continue to work.
268 The fuse(4) module has been renamed to fusefs(4) for consistency with
269 other filesystems. You should update any kld_load="fuse" entries in
270 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
271 "options FUSE" entries in kernel config files.
274 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
275 8.0.0. Please see the 20141231 entry below for information about
276 prerequisites and upgrading, if you are not already using clang 3.5.0
280 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
281 compiled into your custom kernel, add 'device xz' statement to the
285 drm and drm2 have been removed from the tree. Please see
286 https://wiki.freebsd.org/Graphics for the latest information on
287 migrating to the drm ports.
290 Iflib is no longer unconditionally compiled into the kernel. Drivers
291 using iflib and statically compiled into the kernel, now require
292 the 'device iflib' config option. For the same drivers loaded as
293 modules on kernels not having 'device iflib', the iflib.ko module
294 is loaded automatically.
297 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
298 options no longer exist since r343219 and r343427 respectively;
299 nothing uses them, so they should be just removed from custom
303 r342635 changes the way efibootmgr(8) works by requiring users to add
304 the -b (bootnum) parameter for commands where the bootnum was previously
305 specified with each option. For example 'efibootmgr -B 0001' is now
306 'efibootmgr -B -b 0001'.
309 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
310 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
311 servers that have vfs.nfsd.nfs_privport set will only allow mounts
312 from clients using a reserved port#. Since both the FreeBSD and Linux
313 NFSv4 clients use reserved port#s by default, this should not affect
317 The XLP config has been removed. We can't support 64-bit atomics in this
318 kernel because it is running in 32-bit mode. XLP users must transition
319 to running a 64-bit kernel (XLP64 or XLPN32).
321 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
322 the preferred emulator today and we don't need two different ones.
324 The old sibyte / swarm / Broadcom BCM1250 support has been
325 removed from the mips port.
328 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
329 7.0.1. Please see the 20141231 entry below for information about
330 prerequisites and upgrading, if you are not already using clang 3.5.0
334 Remove the timed and netdate programs from the base tree. Setting
335 the time with these daemons has been obsolete for over a decade.
338 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
339 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
340 it produces broken binaries when ifuncs are in use. Users needing
341 GNU ld should install the binutils port or package.
344 The BSD crtbegin and crtend code has been enabled by default. It has
345 had extensive testing on amd64, arm64, and i386. It can be disabled
346 by building a world with -DWITHOUT_BSD_CRTBEGIN.
349 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
350 has been converted to a port (misc/ctm) and will be removed from
351 FreeBSD-13. It is available as a package (ctm) for all supported
355 The default newsyslog.conf(5) file has been changed to only include
356 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
357 the filenames end in '.conf' and do not begin with a '.'.
359 You should check the configuration files in these two directories match
360 this naming convention. You can verify which configuration files are
361 being included using the command:
365 Ports for the DRM modules have been simplified. Now, amd64 users should
366 just install the drm-kmod port. All others should install
369 Graphics hardware that's newer than about 2010 usually works with
370 drm-kmod. For hardware older than 2013, however, some users will need
371 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
372 than 2008 usually only works in drm-legacy-kmod. The graphics team can
373 only commit to hardware made since 2013 due to the complexity of the
374 market and difficulty to test all the older cards effectively. If you
375 have hardware supported by drm-kmod, you are strongly encouraged to use
376 that as you will get better support.
378 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
379 elsewhere, the drm and drm2 modules will be eliminated from the src base
380 soon (with a limited exception for arm). Please update to the package
381 asap and report any issues to x11@freebsd.org.
383 Generally, anybody using the drm*-kmod packages should add
384 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
385 cross-threading surprises, especially with automatic driver
386 loading from X11 startup. These will become the defaults in 13-current
390 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
391 custom kernel and module loading configuration files must be updated
392 accordingly. Moreover, interfaces previous presented as ixlvN to the
393 system are now exposed as iavfN and network configuration files must
394 be adjusted as necessary.
397 OpenSSL has been updated to version 1.1.1. This update included
398 additional various API changes throughout the base system. It is
399 important to rebuild third-party software after upgrading. The value
400 of __FreeBSD_version has been bumped accordingly.
403 The legacy DRM modules and drivers have now been added to the loader's
404 module blacklist, in favor of loading them with kld_list in rc.conf(5).
405 The module blacklist may be overridden with the loader.conf(5)
406 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
410 The cam(4) based nda(4) driver will be used over nvd(4) by default on
411 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
412 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
413 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
417 Reproducible build mode is now on by default, in preparation for
418 FreeBSD 12.0. This eliminates build metadata such as the user,
419 host, and time from the kernel (and uname), unless the working tree
420 corresponds to a modified checkout from a version control system.
421 The previous behavior can be obtained by setting the /etc/src.conf
422 knob WITHOUT_REPRODUCIBLE_BUILD.
425 The Yarrow CSPRNG has been removed from the kernel as it has not been
426 supported by its designers since at least 2003. Fortuna has been the
427 default since FreeBSD-11.
430 devctl freeze/thaw have gone into the tree, the rc scripts have been
431 updated to use them and devmatch has been changed. You should update
432 kernel, userland and rc scripts all at the same time.
435 The default interpreter has been switched from 4th to Lua.
436 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
437 interpreter. If you have custom FORTH code you will need to set
438 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
439 src.conf for the build. This will create default hard links between
440 loader and loader_4th instead of loader and loader_lua, the new default.
441 If you are using UEFI it will create the proper hard link to loader.efi.
443 bhyve uses userboot.so. It remains 4th-only until some issues are solved
444 regarding coexisting with multiple versions of FreeBSD are resolved.
447 ls(1) now respects the COLORTERM environment variable used in other
448 systems and software to indicate that a colored terminal is both
449 supported and desired. If ls(1) is suddenly emitting colors, they may
450 be disabled again by either removing the unwanted COLORTERM from your
451 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
452 may not be observed in a future release.
455 The default pager for most commands has been changed to "less". To
456 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
460 The jedec_ts(4) driver has been removed. A superset of its functionality
461 is available in the jedec_dimm(4) driver, and the manpage for that
462 driver includes migration instructions. If you have "device jedec_ts"
463 in your kernel configuration file, it must be removed.
466 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
467 This should have no effect if the kernel is booted via BIOS/legacy boot.
468 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
469 has a buggy firmware that prevents a successful boot due to use of
473 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
474 support has been removed from the tree. These ports were
475 obsolete and/or known to be broken for many years.
478 loader.efi has been augmented to participate more fully in the
479 UEFI boot manager protocol. loader.efi will now look at the
480 BootXXXX environment variable to determine if a specific kernel
481 or root partition was specified. XXXX is derived from BootCurrent.
482 efibootmgr(8) manages these standard UEFI variables.
485 zfsloader's functionality has now been folded into loader.
486 zfsloader is no longer necessary once you've updated your
487 boot blocks. For a transition period, we will install a
488 hardlink for zfsloader to loader to allow a smooth transition
489 until the boot blocks can be updated (hard link because old
490 zfs boot blocks don't understand symlinks).
493 ARM64 now have efifb support, if you want to have serial console
494 on your arm64 board when an screen is connected and the bootloader
495 setup a frame buffer for us to use, just add :
499 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
500 an screen connected as the firmware will setup a frame buffer are that
501 u-boot will expose as an EFI frame buffer.
504 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
505 or take steps to update /etc/passwd before doing installworld on
506 existing systems. Do not skip the "mergemaster -Fp" step before
507 installworld, as described in the update procedures near the bottom
508 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
509 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
510 the ntp config file contain options that change file/dir locations.
511 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
512 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
513 taking steps to ensure that all required files/dirs are accessible
517 Big endian arm support has been removed.
520 The static environment setup in kernel configs is no longer mutually
521 exclusive with the loader(8) environment by default. In order to
522 restore the previous default behavior of disabling the loader(8)
523 environment if a static environment is present, you must specify
524 loader_env.disabled=1 in the static environment.
527 The ABI of syscalls used by management tools like sockstat and
528 netstat has been broken to allow 32-bit binaries to work on
529 64-bit kernels without modification. These programs will need
530 to match the kernel in order to function. External programs may
531 require minor modifications to accommodate a change of type in
532 structures from pointers to 64-bit virtual addresses.
535 On i386 and amd64 atomics are now inlined. Out of tree modules using
536 atomics will need to be rebuilt.
539 The '%I' format in the kern.corefile sysctl limits the number of
540 core files that a process can generate to the number stored in the
541 debug.ncores sysctl. The '%I' format is replaced by the single digit
542 index. Previously, if all indexes were taken the kernel would overwrite
543 only a core file with the highest index in a filename.
544 Currently the system will create a new core file if there is a free
545 index or if all slots are taken it will overwrite the oldest one.
548 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
549 6.0.1. Please see the 20141231 entry below for information about
550 prerequisites and upgrading, if you are not already using clang 3.5.0
554 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
555 needed to be changed to work with it. This change was made with r335763
556 and requires a mergemaster / etcupdate / etc to update the installed
560 r334930 changed the interface between the NFS modules, so they all
561 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
564 As of r334391 lld is the default amd64 system linker; it is installed
565 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
569 The kernel / userland interface for devinfo changed, so you'll
570 need a new kernel and userland as a pair for it to work (rebuilding
571 lib/libdevinfo is all that's required). devinfo and devmatch will
572 not work, but everything else will when there's a mismatch.
575 The on-disk format for hwpmc callchain records has changed to include
576 threadid corresponding to a given record. This changes the field offsets
577 and thus requires that libpmcstat be rebuilt before using a kernel
581 The vxge(4) driver has been removed. This driver was introduced into
582 HEAD one week before the Exar left the Ethernet market and is not
583 known to be used. If you have device vxge in your kernel config file
587 The amd64 kernel now requires a ld that supports ifunc to produce a
588 working kernel, either lld or a newer binutils. lld is built by default
589 on amd64, and the 'buildkernel' target uses it automatically. However,
590 it is not the default linker, so building the kernel the traditional
591 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
592 binutils port/package). lld will soon be default, and this requirement
595 NOTE: As of r334391 lld is the default system linker on amd64, and no
596 workaround is necessary.
599 The nxge(4) driver has been removed. This driver was for PCI-X 10g
600 cards made by s2io/Neterion. The company was acquired by Exar and
601 no longer sells or supports Ethernet products. If you have device
602 nxge in your kernel config file it must be removed.
605 The tz database (tzdb) has been updated to 2018e. This version more
606 correctly models time stamps in time zones with negative DST such as
607 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
608 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
609 time zone abbreviations and the tm_isdst flag.
612 The ixgb(4) driver has been removed. This driver was for an early and
613 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
614 quickly shifted to the long lived ixgbe family. If you have device
615 ixgb in your kernel config file it must be removed.
618 The lmc(4) driver has been removed. This was a WAN interface
619 card that was already reportedly rare in 2003, and had an ambiguous
620 license. If you have device lmc in your kernel config file it must
624 Support for Arcnet networks has been removed. If you have device
625 arcnet or device cm in your kernel config file they must be
629 Support for FDDI networks has been removed. If you have device
630 fddi or device fpa in your kernel config file they must be
634 In addition to supporting RFC 3164 formatted messages, the
635 syslogd(8) service is now capable of parsing RFC 5424 formatted
636 log messages. The main benefit of using RFC 5424 is that clients
637 may now send log messages with timestamps containing year numbers,
638 microseconds and time zone offsets.
640 Similarly, the syslog(3) C library function has been altered to
641 send RFC 5424 formatted messages to the local system logging
642 daemon. On systems using syslogd(8), this change should have no
643 negative impact, as long as syslogd(8) and the C library are
644 updated at the same time. On systems using a different system
645 logging daemon, it may be necessary to make configuration
646 adjustments, depending on the software used.
648 When using syslog-ng, add the 'syslog-protocol' flag to local
649 input sources to enable parsing of RFC 5424 formatted messages:
652 unix-dgram("/var/run/log" flags(syslog-protocol));
655 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
656 of the 'imuxsock' module to let messages be processed by the
657 regular RFC 3164/5424 parsing pipeline:
659 module(load="imuxsock" SysSock.UseSpecialParser="off")
661 Do note that these changes only affect communication between local
662 applications and syslogd(8). The format that syslogd(8) uses to
663 store messages on disk or forward messages to other systems
664 remains unchanged. syslogd(8) still uses RFC 3164 for these
665 purposes. Options to customize this behaviour will be added in the
666 future. Utilities that process log files stored in /var/log are
667 thus expected to continue to function as before.
669 __FreeBSD_version has been incremented to 1200061 to denote this
673 Support for token ring networks has been removed. If you
674 have "device token" in your kernel config you should remove
675 it. No device drivers supported token ring.
678 makefs was modified to be able to tag ISO9660 El Torito boot catalog
679 entries as EFI instead of overloading the i386 tag as done previously.
680 The amd64 mkisoimages.sh script used to build amd64 ISO images for
681 release was updated to use this. This may mean that makefs must be
682 updated before "make cdrom" can be run in the release directory. This
683 should be as simple as:
685 $ cd $SRCDIR/usr.sbin/makefs
686 $ make depend all install
689 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
690 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
691 Co-existence for the transition period will come shortly. Booting is a
692 complex environment and test coverage for Lua-enabled loaders has been
693 thin, so it would be prudent to assume it might not work and make
694 provisions for backup boot methods.
697 devmatch functionality has been turned on in devd. It will automatically
698 load drivers for unattached devices. This may cause unexpected drivers
699 to be loaded. Please report any problems to current@ and
703 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
704 6.0.0. Please see the 20141231 entry below for information about
705 prerequisites and upgrading, if you are not already using clang 3.5.0
709 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
710 This means it is used to link the kernel and userland libraries and
711 executables, but is not yet installed as /usr/bin/ld by default.
713 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
714 WITHOUT_LLD_BOOTSTRAP=yes
717 On i386, pmtimer has been removed. Its functionality has been folded
718 into apm. It was a no-op on ACPI in current for a while now (but was
719 still needed on i386 in FreeBSD 11 and earlier). Users may need to
720 remove it from kernel config files.
723 The use of RSS hash from the network card aka flowid has been
724 disabled by default for lagg(4) as it's currently incompatible with
725 the lacp and loadbalance protocols.
727 This can be re-enabled by setting the following in loader.conf:
728 net.link.lagg.default_use_flowid="1"
731 The SW_WATCHDOG option is no longer necessary to enable the
732 hardclock-based software watchdog if no hardware watchdog is
733 configured. As before, SW_WATCHDOG will cause the software
734 watchdog to be enabled even if a hardware watchdog is configured.
737 r326887 fixes the issue described in the 20171214 UPDATING entry.
738 r326888 flips the switch back to building GELI support always.
741 r362593 broke ZFS + GELI support for reasons unknown. However,
742 it also broke ZFS support generally, so GELI has been turned off
743 by default as the lesser evil in r326857. If you boot off ZFS and/or
744 GELI, it might not be a good time to update.
747 PowerPC users must update loader(8) by rebuilding world before
748 installing a new kernel, as the protocol connecting them has
749 changed. Without the update, loader metadata will not be passed
750 successfully to the kernel and users will have to enter their
751 root partition at the kernel mountroot prompt to continue booting.
752 Newer versions of loader can boot old kernels without issue.
755 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
756 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
757 to WITH/OUT_LOADER_GELI.
760 The naive and non-compliant support of posix_fallocate(2) in ZFS
761 has been removed as of r325320. The system call now returns EINVAL
762 when used on a ZFS file. Although the new behavior complies with the
763 standard, some consumers are not prepared to cope with it.
764 One known victim is lld prior to r325420.
767 Building in a FreeBSD src checkout will automatically create object
768 directories now rather than store files in the current directory if
769 'make obj' was not ran. Calling 'make obj' is no longer necessary.
770 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
771 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
775 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
776 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
777 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
778 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
779 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
780 The UNIFIED_OBJDIR option is a transitional feature that will be
781 removed for 12.0 release; please migrate to the new format for any
782 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
783 than hardcoding paths.
786 The native-xtools target no longer installs the files by default to the
787 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
788 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
791 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
792 options are changing from controlling the build if defined / undefined
793 to controlling the build with explicit 'yes' or 'no' values. They will
794 shift to WITH/WITHOUT options to match other options in the system.
797 libstand has turned into a private library for sys/boot use only.
798 It is no longer supported as a public interface outside of sys/boot.
801 The arm port has split armv6 into armv6 and armv7. armv7 is now
802 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
803 and are running a kernel from before r324363, you will need to add
804 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
807 When building multiple kernels using KERNCONF, non-existent KERNCONF
808 files will produce an error and buildkernel will fail. Previously
809 missing KERNCONF files silently failed giving no indication as to
810 why, only to subsequently discover during installkernel that the
811 desired kernel was never built in the first place.
814 The default serial number format for CTL LUNs has changed. This will
815 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
816 or iSCSI clients care about their LUNs' serial numbers. Users who
817 require serial number stability should hardcode serial numbers in
821 For 32-bit arm compiled for hard-float support, soft-floating point
822 binaries now always get their shared libraries from
823 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
824 /usr/libsoft also existed). Only users with a hard-float ld.so, but
825 soft-float everything else should be affected.
828 The geli password typed at boot is now hidden. To restore the previous
829 behavior, see geli(8) for configuration options.
832 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
833 sysctl values. Minor nit, but requires a rebuild of both world/kernel
837 "make check" behavior (made in ^/head@r295380) has been changed to
838 execute from a limited sandbox, as opposed to executing from
842 - The "beforecheck" and "aftercheck" targets are now specified.
843 - ${CHECKDIR} (added in commit noted above) has been removed.
844 - Legacy behavior can be enabled by setting
845 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
847 If the limited sandbox mode is enabled, "make check" will execute
848 "make distribution", then install, execute the tests, and clean up the
849 sandbox if successful.
851 The "make distribution" and "make install" targets are typically run as
852 root to set appropriate permissions and ownership at installation time.
853 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
854 environment if executing "make check" with limited sandbox mode using
855 an unprivileged user.
858 Since the switch to GPT disk labels, fsck for UFS/FFS has been
859 unable to automatically find alternate superblocks. As of r322297,
860 the information needed to find alternate superblocks has been
861 moved to the end of the area reserved for the boot block.
862 Filesystems created with a newfs of this vintage or later
863 will create the recovery information. If you have a filesystem
864 created prior to this change and wish to have a recovery block
865 created for your filesystem, you can do so by running fsck in
866 foreground mode (i.e., do not use the -p or -y options). As it
867 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
868 to which you should answer yes.
871 As of r321665, an NFSv4 server configuration that services
872 Kerberos mounts or clients that do not support the uid/gid in
873 owner/owner_group string capability, must explicitly enable
874 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
875 machine's /etc/rc.conf file.
878 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
879 Please see the 20141231 entry below for information about prerequisites
880 and upgrading, if you are not already using clang 3.5.0 or higher.
883 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
884 r-commands (rlogin, rsh, etc.) to be built with the base system.
887 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
888 a very major ABI incompatible change, so users of FreeBSD/powerpc must
889 be careful when performing source upgrades. It is best to run
890 'make installworld' from an alternate root system, either a live
891 CD/memory stick, or a temporary root partition. Additionally, all ports
892 must be recompiled. powerpc64 is largely unaffected, except in the case
893 of 32-bit compatibility. All 32-bit binaries will be affected.
896 Forward compatibility for the "ino64" project have been committed. This
897 will allow most new binaries to run on older kernels in a limited
898 fashion. This prevents many of the common foot-shooting actions in the
899 upgrade as well as the limited ability to roll back the kernel across
900 the ino64 upgrade. Complicated use cases may not work properly, though
901 enough simpler ones work to allow recovery in most situations.
904 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
905 if you require the GPL compiler.
908 The internal ABI used for communication between the NFS kernel modules
909 was changed by r320085, so __FreeBSD_version was bumped to
910 ensure all the NFS related modules are updated together.
913 The ABI of struct event was changed by extending the data
914 member to 64bit and adding ext fields. For upgrade, same
915 precautions as for the entry 20170523 "ino64" must be
919 The GNU roff toolchain has been removed from base. To render manpages
920 which are not supported by mandoc(1), man(1) can fallback on GNU roff
921 from ports (and recommends to install it).
922 To render roff(7) documents, consider using GNU roff from ports or the
923 heirloom doctools roff toolchain from ports via pkg install groff or
924 via pkg install heirloom-doctools.
927 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
928 smaller runtime footprint builds. This is useful for embedded systems
929 which only require one chipset support.
931 If you load it as a module, make sure this is in /boot/loader.conf:
935 This will load the HAL, all chip/RF backends and if_ath_pci.
936 If you have if_ath_pci in /boot/loader.conf, ensure it is after
937 if_ath or it will not load any HAL chipset support.
939 If you want to selectively load things (eg on ye cheape ARM/MIPS
940 platforms where RAM is at a premium) you should:
943 * load the chip modules in question
944 * load ath_rate, ath_dfs
946 * load if_ath_pci and/or if_ath_ahb depending upon your particular
947 bus bind type - this is where probe/attach is done.
949 For further comments/feedback, poke adrian@ .
952 The "ino64" 64-bit inode project has been committed, which extends
953 a number of types to 64 bits. Upgrading in place requires care and
954 adherence to the documented upgrade procedure.
956 If using a custom kernel configuration ensure that the
957 COMPAT_FREEBSD11 option is included (as during the upgrade the
958 system will be running the ino64 kernel with the existing world).
960 For the safest in-place upgrade begin by removing previous build
961 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
962 procedure documented below under the heading "To rebuild everything and
963 install it on the current system." Specifically, a reboot is required
964 after installing the new kernel before installing world. While an
965 installworld normally works by accident from multiuser after rebooting
966 the proper kernel, there are many cases where this will fail across this
967 upgrade and installworld from single user is required.
970 The NATM framework including the en(4), fatm(4), hatm(4), and
971 patm(4) devices has been removed. Consumers should plan a
972 migration before the end-of-life date for FreeBSD 11.
975 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
976 diff has not been implemented, if those are needed a newer version of
977 GNU diff is available via the diffutils package under the gdiff name.
980 As of r316810 for ipfilter, keep frags is no longer assumed when
981 keep state is specified in a rule. r316810 aligns ipfilter with
982 documentation in man pages separating keep frags from keep state.
983 This allows keep state to be specified without forcing keep frags
984 and allows keep frags to be specified independently of keep state.
985 To maintain previous behaviour, also specify keep frags with
986 keep state (as documented in ipf.conf.5).
989 arm64 builds now use the base system LLD 4.0.0 linker by default,
990 instead of requiring that the aarch64-binutils port or package be
991 installed. To continue using aarch64-binutils, set
992 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
995 The UDP optimization in entry 20160818 that added the sysctl
996 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
997 packets will no longer be treated as L3 broadcast packets.
1000 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1001 use any explicitly assigned loopback address available in the jail
1002 instead of using the first assigned address of the jail.
1005 The ctl.ko module no longer implements the iSCSI target frontend:
1006 cfiscsi.ko does instead.
1008 If building cfiscsi.ko as a kernel module, the module can be loaded
1009 via one of the following methods:
1010 - `cfiscsi_load="YES"` in loader.conf(5).
1011 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1012 - ctladm(8)/ctld(8), when compiled with iSCSI support
1013 (`WITH_ISCSI=yes` in src.conf(5))
1015 Please see cfiscsi(4) for more details.
1018 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1019 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1020 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1021 missing, but mmcsd.ko now will refuse to load if it is incompatible
1025 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1026 If you have used named states in the firewall rules, you need to modify
1027 them after installworld and before rebooting. Now named states must
1028 be prefixed with colon.
1031 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1032 removed as the userland we provide cannot use them. The KMS version
1033 (sys/dev/drm2) supports the same hardware.
1036 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1037 Please see the 20141231 entry below for information about prerequisites
1038 and upgrading, if you are not already using clang 3.5.0 or higher.
1041 The code that provides support for ZFS .zfs/ directory functionality
1042 has been reimplemented. It's not possible now to create a snapshot
1043 by mkdir under .zfs/snapshot/. That should be the only user visible
1047 EISA bus support has been removed. The WITH_EISA option is no longer
1051 MCA bus support has been removed.
1054 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1055 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1058 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1059 the em(4) driver conforms to iflib specifications.
1062 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1063 IFLIB. If you have a custom kernel configuration that excludes em(4)
1064 but you use igb(4), you need to re-add em(4) to your custom
1068 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1069 Please see the 20141231 entry below for information about prerequisites
1070 and upgrading, if you are not already using clang 3.5.0 or higher.
1073 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1074 Please see the 20141231 entry below for information about prerequisites
1075 and upgrading, if you are not already using clang 3.5.0 or higher.
1078 The layout of the pmap structure has changed for powerpc to put the pmap
1079 statistics at the front for all CPU variations. libkvm(3) and all tools
1080 that link against it need to be recompiled.
1083 isl(4) and cyapa(4) drivers now require a new driver,
1084 chromebook_platform(4), to work properly on Chromebook-class hardware.
1085 On other types of hardware the drivers may need to be configured using
1086 device hints. Please see the corresponding manual pages for details.
1089 The urtwn(4) driver was merged into rtwn(4) and now consists of
1090 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1092 Also, firmware for RTL8188CE was renamed due to possible name
1093 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1096 GNU rcs has been removed from base. It is available as packages:
1097 - rcs: Latest GPLv3 GNU rcs version.
1098 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1102 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1103 modules now requires that the kernel configuration contain the
1104 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1107 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1108 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1111 Relocatable object files with the extension of .So have been renamed
1112 to use an extension of .pico instead. The purpose of this change is
1113 to avoid a name clash with shared libraries on case-insensitive file
1114 systems. On those file systems, foo.So is the same file as foo.so.
1117 GNU rcs has been turned off by default. It can (temporarily) be built
1118 again by adding WITH_RCS knob in src.conf.
1119 Otherwise, GNU rcs is available from packages:
1120 - rcs: Latest GPLv3 GNU rcs version.
1121 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1124 The backup_uses_rcs functionality has been removed from rc.subr.
1127 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1128 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1129 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1130 QUEUE_MACRO_DEBUG behavior.
1133 r304787 changed some ioctl interfaces between the iSCSI userspace
1134 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1135 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1139 The UDP receive code has been updated to only treat incoming UDP
1140 packets that were addressed to an L2 broadcast address as L3
1141 broadcast packets. It is not expected that this will affect any
1142 standards-conforming UDP application. The new behaviour can be
1143 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1147 Remove the openbsd_poll system call.
1148 __FreeBSD_version has been bumped because of this.
1151 The stable/11 branch has been created from head@r302406.
1154 The libc stub for the pipe(2) system call has been replaced with
1155 a wrapper that calls the pipe2(2) system call and the pipe(2)
1156 system call is now only implemented by the kernels that include
1157 "options COMPAT_FREEBSD10" in their config file (this is the
1158 default). Users should ensure that this option is enabled in
1159 their kernel or upgrade userspace to r302092 before upgrading their
1163 CAM will now strip leading spaces from SCSI disks' serial numbers.
1164 This will affect users who create UFS filesystems on SCSI disks using
1165 those disk's diskid device nodes. For example, if /etc/fstab
1166 previously contained a line like
1167 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1168 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1169 transforms like gmirror may also be affected. ZFS users should
1173 The bitstring(3) API has been updated with new functionality and
1174 improved performance. But it is binary-incompatible with the old API.
1175 Objects built with the new headers may not be linked against objects
1176 built with the old headers.
1179 The brk and sbrk functions have been removed from libc on arm64.
1180 Binutils from ports has been updated to not link to these
1181 functions and should be updated to the latest version before
1182 installing a new libc.
1185 The armv6 port now defaults to hard float ABI. Limited support
1186 for running both hardfloat and soft float on the same system
1187 is available using the libraries installed with -DWITH_LIBSOFT.
1188 This has only been tested as an upgrade path for installworld
1189 and packages may fail or need manual intervention to run. New
1190 packages will be needed.
1192 To update an existing self-hosted armv6hf system, you must add
1193 TARGET_ARCH=armv6 on the make command line for both the build
1194 and the install steps.
1197 Kernel modules compiled outside of a kernel build now default to
1198 installing to /boot/modules instead of /boot/kernel. Many kernel
1199 modules built this way (such as those in ports) already overrode
1200 KMODDIR explicitly to install into /boot/modules. However,
1201 manually building and installing a module from /sys/modules will
1202 now install to /boot/modules instead of /boot/kernel.
1205 The CAM I/O scheduler has been committed to the kernel. There should be
1206 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1207 list of known rogues that claim support for this but actually corrupt
1208 data is believed to be complete, be on the lookout for data
1209 corruption. The known rogue list is believed to be complete:
1211 o Crucial MX100, M550 drives with MU01 firmware.
1212 o Micron M510 and M550 drives with MU01 firmware.
1213 o Micron M500 prior to MU07 firmware
1214 o Samsung 830, 840, and 850 all firmwares
1215 o FCCT M500 all firmwares
1217 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1218 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1219 updated firmware. Black listed drives will work correctly because these
1220 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1221 this list is the same as found in Linux, it's believed there are no
1222 other rogues in the market place. All other models from the above
1225 To be safe, if you are at all concerned, you can quirk each of your
1226 drives to prevent NCQ from being sent by setting:
1227 kern.cam.ada.X.quirks="0x2"
1228 in loader.conf. If the drive requires the 4k sector quirk, set the
1229 quirks entry to 0x3.
1232 The FAST_DEPEND build option has been removed and its functionality is
1233 now the one true way. The old mkdep(1) style of 'make depend' has
1234 been removed. See 20160311 for further details.
1237 Resource range types have grown from unsigned long to uintmax_t. All
1238 drivers, and anything using libdevinfo, need to be recompiled.
1241 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1242 builds. It no longer runs mkdep(1) during 'make depend', and the
1243 'make depend' stage can safely be skipped now as it is auto ran
1244 when building 'make all' and will generate all SRCS and DPSRCS before
1245 building anything else. Dependencies are gathered at compile time with
1246 -MF flags kept in separate .depend files per object file. Users should
1247 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1248 stale .depend files.
1251 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1252 kernel modules. Therefore, if you load any kernel modules at boot time,
1253 please install the boot loaders after you install the kernel, but before
1257 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1258 make installkernel KERNCONF=YOUR_KERNEL_HERE
1259 make -C sys/boot install
1260 <reboot in single user>
1262 Then follow the usual steps, described in the General Notes section,
1266 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1267 see the 20141231 entry below for information about prerequisites and
1268 upgrading, if you are not already using clang 3.5.0 or higher.
1271 The AIO subsystem is now a standard part of the kernel. The
1272 VFS_AIO kernel option and aio.ko kernel module have been removed.
1273 Due to stability concerns, asynchronous I/O requests are only
1274 permitted on sockets and raw disks by default. To enable
1275 asynchronous I/O requests on all file types, set the
1276 vfs.aio.enable_unsafe sysctl to a non-zero value.
1279 The ELF object manipulation tool objcopy is now provided by the
1280 ELF Tool Chain project rather than by GNU binutils. It should be a
1281 drop-in replacement, with the addition of arm64 support. The
1282 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1283 to obtain the GNU version if necessary.
1286 Building ZFS pools on top of zvols is prohibited by default. That
1287 feature has never worked safely; it's always been prone to deadlocks.
1288 Using a zvol as the backing store for a VM guest's virtual disk will
1289 still work, even if the guest is using ZFS. Legacy behavior can be
1290 restored by setting vfs.zfs.vol.recursive=1.
1293 The NONE and HPN patches has been removed from OpenSSH. They are
1294 still available in the security/openssh-portable port.
1297 With the addition of ypldap(8), a new _ypldap user is now required
1298 during installworld. "mergemaster -p" can be used to add the user
1299 prior to installworld, as documented in the handbook.
1302 The tftp loader (pxeboot) now uses the option root-path directive. As a
1303 consequence it no longer looks for a pxeboot.4th file on the tftp
1304 server. Instead it uses the regular /boot infrastructure as with the
1308 The code to start recording plug and play data into the modules has
1309 been committed. While the old tools will properly build a new kernel,
1310 a number of warnings about "unknown metadata record 4" will be produced
1311 for an older kldxref. To avoid such warnings, make sure to rebuild
1312 the kernel toolchain (or world). Make sure that you have r292078 or
1313 later when trying to build 292077 or later before rebuilding.
1316 Debug data files are now built by default with 'make buildworld' and
1317 installed with 'make installworld'. This facilitates debugging but
1318 requires more disk space both during the build and for the installed
1319 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1323 r291527 changed the internal interface between the nfsd.ko and
1324 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1325 __FreeBSD_version has been bumped because of this.
1328 Add support for unicode collation strings leads to a change of
1329 order of files listed by ls(1) for example. To get back to the old
1330 behaviour, set LC_COLLATE environment variable to "C".
1332 Databases administrators will need to reindex their databases given
1333 collation results will be different.
1335 Due to a bug in install(1) it is recommended to remove the ancient
1336 locales before running make installworld.
1338 rm -rf /usr/share/locale/*
1341 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1342 libcrypto.so.7 or libssl.so.7 must be recompiled.
1345 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1346 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1347 should be replaced with isp_2400 and isp_2500 modules respectively.
1350 The build previously allowed using 'make -n' to not recurse into
1351 sub-directories while showing what commands would be executed, and
1352 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1353 and 'make -N' will not.
1356 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1357 and etcupdate will now use this file. A custom sendmail.cf is now
1358 updated via this mechanism rather than via installworld. If you had
1359 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1360 want to remove the exclusion or change it to "always install".
1361 /etc/mail/sendmail.cf is now managed the same way regardless of
1362 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1363 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1366 Compatibility shims for legacy ATA device names have been removed.
1367 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1368 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1369 environment variables, /dev/ad* and /dev/ar* symbolic links.
1372 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1373 Please see the 20141231 entry below for information about prerequisites
1374 and upgrading, if you are not already using clang 3.5.0 or higher.
1377 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1378 and renamed from .symbols to .debug. This reduces the size requirements
1379 on the boot partition or file system and provides consistency with
1380 userland debug files.
1382 When using the supported kernel installation method the
1383 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1384 as is done with /boot/kernel.
1386 Developers wishing to maintain the historical behavior of installing
1387 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1390 The wireless drivers had undergone changes that remove the 'parent
1391 interface' from the ifconfig -l output. The rc.d network scripts
1392 used to check presence of a parent interface in the list, so old
1393 scripts would fail to start wireless networking. Thus, etcupdate(3)
1394 or mergemaster(8) run is required after kernel update, to update your
1395 rc.d scripts in /etc.
1398 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1399 These configurations are now automatically interpreted as
1400 'scrub fragment reassemble'.
1403 Kernel-loadable modules for the random(4) device are back. To use
1404 them, the kernel must have
1407 options RANDOM_LOADABLE
1409 kldload(8) can then be used to load random_fortuna.ko
1410 or random_yarrow.ko. Please note that due to the indirect
1411 function calls that the loadable modules need to provide,
1412 the build-in variants will be slightly more efficient.
1414 The random(4) kernel option RANDOM_DUMMY has been retired due to
1415 unpopularity. It was not all that useful anyway.
1418 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1419 Control over building the ELF Tool Chain tools is now provided by
1420 the WITHOUT_TOOLCHAIN knob.
1423 The polarity of Pulse Per Second (PPS) capture events with the
1424 uart(4) driver has been corrected. Prior to this change the PPS
1425 "assert" event corresponded to the trailing edge of a positive PPS
1426 pulse and the "clear" event was the leading edge of the next pulse.
1428 As the width of a PPS pulse in a typical GPS receiver is on the
1429 order of 1 millisecond, most users will not notice any significant
1430 difference with this change.
1432 Anyone who has compensated for the historical polarity reversal by
1433 configuring a negative offset equal to the pulse width will need to
1434 remove that workaround.
1437 The default group assigned to /dev/dri entries has been changed
1438 from 'wheel' to 'video' with the id of '44'. If you want to have
1439 access to the dri devices please add yourself to the video group
1442 # pw groupmod video -m $USER
1445 The menu.rc and loader.rc files will now be replaced during
1446 upgrades. Please migrate local changes to menu.rc.local and
1447 loader.rc.local instead.
1450 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1451 strings and strip have been removed. The src.conf(5) knob
1452 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1455 As ZFS requires more kernel stack pages than is the default on some
1456 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1457 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1459 Please consider using 'options KSTACK_PAGES=X' where X is greater
1460 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1463 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1464 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1465 default, i.e., they will not contain "::". For example, instead
1466 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1467 to have a more specific match, such as different map entries for
1468 IPv6:0:0 vs IPv6:0. This change requires that configuration
1469 data (including maps, files, classes, custom ruleset, etc.) must
1470 use the same format, so make certain such configuration data is
1471 upgrading. As a very simple check search for patterns like
1472 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1473 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1474 the cf option UseCompressedIPv6Addresses.
1477 The default kernel entropy-processing algorithm is now
1478 Fortuna, replacing Yarrow.
1480 Assuming you have 'device random' in your kernel config
1481 file, the configurations allow a kernel option to override
1482 this default. You may choose *ONE* of:
1484 options RANDOM_YARROW # Legacy /dev/random algorithm.
1485 options RANDOM_DUMMY # Blocking-only driver.
1487 If you have neither, you get Fortuna. For most people,
1488 read no further, Fortuna will give a /dev/random that works
1489 like it always used to, and the difference will be irrelevant.
1491 If you remove 'device random', you get *NO* kernel-processed
1492 entropy at all. This may be acceptable to folks building
1493 embedded systems, but has complications. Carry on reading,
1494 and it is assumed you know what you need.
1496 *PLEASE* read random(4) and random(9) if you are in the
1497 habit of tweaking kernel configs, and/or if you are a member
1498 of the embedded community, wanting specific and not-usual
1499 behaviour from your security subsystems.
1501 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1502 random', you will NOT have a functioning /dev/random, and
1503 many cryptographic features will not work, including SSH.
1504 You may also find strange behaviour from the random(3) set
1505 of library functions, in particular sranddev(3), srandomdev(3)
1506 and arc4random(3). The reason for this is that the KERN_ARND
1507 sysctl only returns entropy if it thinks it has some to
1508 share, and with RANDOM_DUMMY or no 'device random' this
1512 An additional fix for the issue described in the 20150614 sendmail
1513 entry below has been committed in revision 284717.
1516 FreeBSD's old make (fmake) has been removed from the system. It is
1517 available as the devel/fmake port or via pkg install fmake.
1520 The fix for the issue described in the 20150614 sendmail entry
1521 below has been committed in revision 284436. The work
1522 around described in that entry is no longer needed unless the
1523 default setting is overridden by a confDH_PARAMETERS configuration
1524 setting of '5' or pointing to a 512 bit DH parameter file.
1527 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1528 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1529 and devel/kyua to version 0.20+ and adjust any calling code to work
1530 with Kyuafile and kyua.
1533 The import of openssl to address the FreeBSD-SA-15:10.openssl
1534 security advisory includes a change which rejects handshakes
1535 with DH parameters below 768 bits. sendmail releases prior
1536 to 8.15.2 (not yet released), defaulted to a 512 bit
1537 DH parameter setting for client connections. To work around
1538 this interoperability, sendmail can be configured to use a
1539 2048 bit DH parameter by:
1541 1. Edit /etc/mail/`hostname`.mc
1542 2. If a setting for confDH_PARAMETERS does not exist or
1543 exists and is set to a string beginning with '5',
1544 replace it with '2'.
1545 3. If a setting for confDH_PARAMETERS exists and is set to
1546 a file path, create a new file with:
1547 openssl dhparam -out /path/to/file 2048
1548 4. Rebuild the .cf file:
1549 cd /etc/mail/; make; make install
1550 5. Restart sendmail:
1551 cd /etc/mail/; make restart
1553 A sendmail patch is coming, at which time this file will be
1557 Generation of legacy formatted entries have been disabled by default
1558 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1559 entries were converted to use the new format by default when the new,
1560 machine independent format have been added and supported since FreeBSD
1563 Please see the pwd_mkdb(8) manual page for further details.
1566 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1567 20141231 entry below for information about prerequisites and upgrading,
1568 if you are not already using 3.5.0 or higher.
1571 TI platform code switched to using vendor DTS files and this update
1572 may break existing systems running on Beaglebone, Beaglebone Black,
1575 - dtb files should be regenerated/reinstalled. Filenames are the
1576 same but content is different now
1577 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1578 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1579 addressing scheme is now pin 25 on /dev/gpioc3.
1580 - Pandaboard: /etc/ttys should be updated, serial console device is
1581 now /dev/ttyu2, not /dev/ttyu0
1584 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1585 If you need the GNU extension from groff soelim(1), install groff
1586 from package: pkg install groff, or via ports: textproc/groff.
1589 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1590 defined in symlink(7); previously symlinks were silently ignored.
1593 The const qualifier has been removed from iconv(3) to comply with
1594 POSIX. The ports tree is aware of this from r384038 onwards.
1597 Libraries specified by LIBADD in Makefiles must have a corresponding
1598 DPADD_<lib> variable to ensure correct dependencies. This is now
1599 enforced in src.libnames.mk.
1602 From legacy ata(4) driver was removed support for SATA controllers
1603 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1604 Kernel modules ataahci and ataadaptec were removed completely,
1605 replaced by ahci and mvs modules respectively.
1608 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1609 the 20141231 entry below for information about prerequisites and
1610 upgrading, if you are not already using 3.5.0 or higher.
1613 The 32-bit PowerPC kernel has been changed to a position-independent
1614 executable. This can only be booted with a version of loader(8)
1615 newer than January 31, 2015, so make sure to update both world and
1616 kernel before rebooting.
1619 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1620 but before r278950, the RNG was not seeded properly. Immediately
1621 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1622 ssh keys or openssl keys) that were generated w/ a kernel from that
1623 range. This does not affect programs that directly used /dev/random
1624 or /dev/urandom. All userland uses of arc4random(3) are affected.
1627 The autofs(4) ABI was changed in order to restore binary compatibility
1628 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1629 with the new kernel.
1632 The powerpc64 kernel has been changed to a position-independent
1633 executable. This can only be booted with a new version of loader(8),
1634 so make sure to update both world and kernel before rebooting.
1637 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1638 only release, no new features have been added. Please see the 20141231
1639 entry below for information about prerequisites and upgrading, if you
1640 are not already using 3.5.0.
1643 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1644 taken from the ELF Tool Chain project rather than GNU binutils. They
1645 should be drop-in replacements, with the addition of arm64 support.
1646 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1647 binutils tools, if necessary. See 20150805 for updated information.
1650 The default Unbound configuration now enables remote control
1651 using a local socket. Users who have already enabled the
1652 local_unbound service should regenerate their configuration
1653 by running "service local_unbound setup" as root.
1656 The GNU texinfo and GNU info pages have been removed.
1657 To be able to view GNU info pages please install texinfo from ports.
1660 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1662 As of this release, a prerequisite for building clang, llvm and lldb is
1663 a C++11 capable compiler and C++11 standard library. This means that to
1664 be able to successfully build the cross-tools stage of buildworld, with
1665 clang as the bootstrap compiler, your system compiler or cross compiler
1666 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1667 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1670 On any standard FreeBSD 10.x or 11.x installation, where clang and
1671 libc++ are on by default (that is, on x86 or arm), this should work out
1674 On 9.x installations where clang is enabled by default, e.g. on x86 and
1675 powerpc, libc++ will not be enabled by default, so libc++ should be
1676 built (with clang) and installed first. If both clang and libc++ are
1677 missing, build clang first, then use it to build libc++.
1679 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1680 the instructions for 9.x above.
1682 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1683 default, and do not build clang.
1685 Many embedded systems are resource constrained, and will not be able to
1686 build clang in a reasonable time, or in some cases at all. In those
1687 cases, cross building bootable systems on amd64 is a workaround.
1689 This new version of clang introduces a number of new warnings, of which
1690 the following are most likely to appear:
1694 This warns in two cases, for both C and C++:
1695 * When the code is trying to take the absolute value of an unsigned
1696 quantity, which is effectively a no-op, and almost never what was
1697 intended. The code should be fixed, if at all possible. If you are
1698 sure that the unsigned quantity can be safely cast to signed, without
1699 loss of information or undefined behavior, you can add an explicit
1700 cast, or disable the warning.
1702 * When the code is trying to take an absolute value, but the called
1703 abs() variant is for the wrong type, which can lead to truncation.
1704 If you want to disable the warning instead of fixing the code, please
1705 make sure that truncation will not occur, or it might lead to unwanted
1708 -Wtautological-undefined-compare and
1709 -Wundefined-bool-conversion
1711 These warn when C++ code is trying to compare 'this' against NULL, while
1712 'this' should never be NULL in well-defined C++ code. However, there is
1713 some legacy (pre C++11) code out there, which actively abuses this
1714 feature, which was less strictly defined in previous C++ versions.
1716 Squid and openjdk do this, for example. The warning can be turned off
1717 for C++98 and earlier, but compiling the code in C++11 mode might result
1718 in unexpected behavior; for example, the parts of the program that are
1719 unreachable could be optimized away.
1722 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1723 kernel sources have been removed. The .h files remain, since some
1724 utilities include them. This will need to be fixed later.
1725 If "mount -t oldnfs ..." is attempted, it will fail.
1726 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1727 the utilities will report errors.
1730 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1731 directories to top level SUBDIR variable when their parent
1732 directory is included in LOCAL_DIRS. Users with build systems with
1733 such hierarchies and without SUBDIR entries in the parent
1734 directory Makefiles should add them or add the directories to
1738 faith(4) and faithd(8) have been removed from the base system. Faith
1739 has been obsolete for a very long time.
1742 vt(4), the new console driver, is enabled by default. It brings
1743 support for Unicode and double-width characters, as well as
1744 support for UEFI and integration with the KMS kernel video
1747 You may need to update your console settings in /etc/rc.conf,
1748 most probably the keymap. During boot, /etc/rc.d/syscons will
1749 indicate what you need to do.
1751 vt(4) still has issues and lacks some features compared to
1752 syscons(4). See the wiki for up-to-date information:
1753 https://wiki.freebsd.org/Newcons
1755 If you want to keep using syscons(4), you can do so by adding
1756 the following line to /boot/loader.conf:
1760 pjdfstest has been integrated into kyua as an opt-in test suite.
1761 Please see share/doc/pjdfstest/README for more details on how to
1765 gperf has been removed from the base system for architectures
1766 that use clang. Ports that require gperf will obtain it from the
1770 pjdfstest has been moved from tools/regression/pjdfstest to
1774 At svn r271982, The default linux compat kernel ABI has been adjusted
1775 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1776 update. If you wish to continue using the linux-f10 compat ports,
1777 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1778 encouraged to update their linux-compat packages to linux-c6 during
1779 their next update cycle.
1782 The ofwfb driver, used to provide a graphics console on PowerPC when
1783 using vt(4), no longer allows mmap() of all physical memory. This
1784 will prevent Xorg on PowerPC with some ATI graphics cards from
1785 initializing properly unless x11-servers/xorg-server is updated to
1789 The xdev targets have been converted to using TARGET and
1790 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1793 The default unbound configuration has been modified to address
1794 issues with reverse lookups on networks that use private
1795 address ranges. If you use the local_unbound service, run
1796 "service local_unbound setup" as root to regenerate your
1797 configuration, then "service local_unbound reload" to load the
1801 The GNU texinfo and GNU info pages are not built and installed
1802 anymore, WITH_INFO knob has been added to allow to built and install
1804 UPDATE: see 20150102 entry on texinfo's removal
1807 The GNU readline library is now an INTERNALLIB - that is, it is
1808 statically linked into consumers (GDB and variants) in the base
1809 system, and the shared library is no longer installed. The
1810 devel/readline port is available for third party software that
1814 The Itanium architecture (ia64) has been removed from the list of
1815 known architectures. This is the first step in the removal of the
1819 Commit r268115 has added NFSv4.1 server support, merged from
1820 projects/nfsv4.1-server. Since this includes changes to the
1821 internal interfaces between the NFS related modules, a full
1822 build of the kernel and modules will be necessary.
1823 __FreeBSD_version has been bumped.
1826 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1827 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1828 which differs from the behaviour controlled by this knob.)
1831 Maximal length of the serial number in CTL was increased from 16 to
1832 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1833 and ctld, need to be rebuilt to work with a new kernel.
1836 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1837 1 respectively to match the upstream numbers. They were out of
1838 sync because, when they were originally added to FreeBSD, the
1839 upstream versions were not respected. These libraries are private
1840 and not yet built by default, so renumbering them should be a
1841 non-issue. However, unclean source trees will yield broken test
1842 programs once the operator executes "make delete-old-libs" after a
1843 "make installworld".
1845 Additionally, the atf-sh binary was made private by moving it into
1846 /usr/libexec/. Already-built shell test programs will keep the
1847 path to the old binary so they will break after "make delete-old"
1850 If you are using WITH_TESTS=yes (not the default), wipe the object
1851 tree and rebuild from scratch to prevent spurious test failures.
1852 This is only needed once: the misnumbered libraries and misplaced
1853 binaries have been added to OptionalObsoleteFiles.inc so they will
1854 be removed during a clean upgrade.
1857 Clang and llvm have been upgraded to 3.4.1 release.
1860 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1861 be removed to avoid issues in the future (and has been added to
1865 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1866 past, it affected all builds that used the bsd.*.mk files. The old
1867 behavior was a bug, but people may have relied upon it. To get this
1868 behavior back, you can .include /etc/src.conf from /etc/make.conf
1869 (which is still global and isn't changed). This also changes the
1870 behavior of incremental builds inside the tree of individual
1871 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1872 Although this has survived make universe and some upgrade scenarios,
1873 other upgrade scenarios may have broken. At least one form of
1874 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1875 as well... In cases where MAKESYSPATH isn't working with this
1876 setting, you'll need to set it to the full path to your tree.
1878 One side effect of all this cleaning up is that bsd.compiler.mk
1879 is no longer implicitly included by bsd.own.mk. If you wish to
1880 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1884 The lindev device has been removed since /dev/full has been made a
1885 standard device. __FreeBSD_version has been bumped.
1888 The knob WITHOUT_VI was added to the base system, which controls
1889 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1890 in order to reorder files share/termcap and didn't build ex(1) as a
1891 build tool, so building/installing with WITH_VI is highly advised for
1892 build hosts for older releases.
1894 This issue has been fixed in stable/9 and stable/10 in r277022 and
1895 r276991, respectively.
1898 The YES_HESIOD knob has been removed. It has been obsolete for
1899 a decade. Please move to using WITH_HESIOD instead or your builds
1900 will silently lack HESIOD.
1903 The uart(4) driver has been changed with respect to its handling
1904 of the low-level console. Previously the uart(4) driver prevented
1905 any process from changing the baudrate or the CLOCAL and HUPCL
1906 control flags. By removing the restrictions, operators can make
1907 changes to the serial console port without having to reboot.
1908 However, when getty(8) is started on the serial device that is
1909 associated with the low-level console, a misconfigured terminal
1910 line in /etc/ttys will now have a real impact.
1911 Before upgrading the kernel, make sure that /etc/ttys has the
1912 serial console device configured as 3wire without baudrate to
1913 preserve the previous behaviour. E.g:
1914 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1917 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1918 to improve performance. To re-enable it, if needed, run rpcbind
1919 with command line option -W.
1922 Switched back to the GPL dtc compiler due to updates in the upstream
1923 dts files not being supported by the BSDL dtc compiler. You will need
1924 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1925 may result while building dtb files during a kernel build if you fail
1926 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1929 Clang and llvm have been upgraded to 3.4 release.
1932 The nve(4) driver has been removed. Please use the nfe(4) driver
1933 for NVIDIA nForce MCP Ethernet adapters instead.
1936 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1937 This could cause certain C++ applications using shared libraries built
1938 against the previous version of libc++ to crash. The incompatibility
1939 has now been fixed, but any C++ applications or shared libraries built
1940 between r261283 and r261801 should be recompiled.
1943 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1944 capability mode support. Please note that enabling the feature in
1945 kernel is still highly recommended.
1948 OpenSSH is now built with sandbox support, and will use sandbox as
1949 the default privilege separation method. This requires Capsicum
1950 capability mode support in kernel.
1953 The libelf and libdwarf libraries have been updated to newer
1954 versions from upstream. Shared library version numbers for
1955 these two libraries were bumped. Any ports or binaries
1956 requiring these two libraries should be recompiled.
1957 __FreeBSD_version is bumped to 1100006.
1960 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1961 instead of providing an explicit one, this would prevent such
1962 Makefile from providing its own Kyuafile in the future during
1963 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1964 intervention is needed to clean an objdir if you use NO_CLEAN:
1965 # find /usr/obj -name Kyuafile | xargs rm -f
1968 The behavior of gss_pseudo_random() for the krb5 mechanism
1969 has changed, for applications requesting a longer random string
1970 than produced by the underlying enctype's pseudo-random() function.
1971 In particular, the random string produced from a session key of
1972 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1973 be different at the 17th octet and later, after this change.
1974 The counter used in the PRF+ construction is now encoded as a
1975 big-endian integer in accordance with RFC 4402.
1976 __FreeBSD_version is bumped to 1100004.
1979 The WITHOUT_ATF build knob has been removed and its functionality
1980 has been subsumed into the more generic WITHOUT_TESTS. If you were
1981 using the former to disable the build of the ATF libraries, you
1982 should change your settings to use the latter.
1985 The default version of mtree is nmtree which is obtained from
1986 NetBSD. The output is generally the same, but may vary
1987 slightly. If you found you need identical output adding
1988 "-F freebsd9" to the command line should do the trick. For the
1989 time being, the old mtree is available as fmtree.
1992 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1993 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1994 1.1.4_8 and verify bsdyml not linked in, before running "make
1996 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1998 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2001 The stable/10 branch has been created in subversion from head
2008 Sometimes, obscure build problems are the result of environment
2009 poisoning. This can happen because the make utility reads its
2010 environment when searching for values for global variables. To run
2011 your build attempts in an "environmental clean room", prefix all make
2012 commands with 'env -i '. See the env(1) manual page for more details.
2013 Occasionally a build failure will occur with "make -j" due to a race
2014 condition. If this happens try building again without -j, and please
2015 report a bug if it happens consistently.
2017 When upgrading from one major version to another it is generally best to
2018 upgrade to the latest code in the currently installed branch first, then
2019 do an upgrade to the new branch. This is the best-tested upgrade path,
2020 and has the highest probability of being successful. Please try this
2021 approach if you encounter problems with a major version upgrade. Since
2022 the stable 4.x branch point, one has generally been able to upgrade from
2023 anywhere in the most recent stable branch to head / current (or even the
2024 last couple of stable branches). See the top of this file when there's
2027 The update process will emit an error on an attempt to perform a build
2028 or install from a FreeBSD version below the earliest supported version.
2029 When updating from an older version the update should be performed one
2030 major release at a time, including running `make delete-old` at each
2033 When upgrading a live system, having a root shell around before
2034 installing anything can help undo problems. Not having a root shell
2035 around can lead to problems if pam has changed too much from your
2036 starting point to allow continued authentication after the upgrade.
2038 This file should be read as a log of events. When a later event changes
2039 information of a prior event, the prior event should not be deleted.
2040 Instead, a pointer to the entry with the new information should be
2041 placed in the old entry. Readers of this file should also sanity check
2042 older entries before relying on them blindly. Authors of new entries
2043 should write them with this in mind.
2047 When upgrading the boot ZFS pool to a new version, always follow
2050 1.) recompile and reinstall the ZFS boot loader and boot block
2051 (this is part of "make buildworld" and "make installworld")
2053 2.) update the ZFS boot block on your boot drive
2055 The following example updates the ZFS boot block on the first
2056 partition (freebsd-boot) of a GPT partitioned drive ada0:
2057 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2059 Non-boot pools do not need these updates.
2063 If you are updating from a prior version of FreeBSD (even one just
2064 a few days old), you should follow this procedure. It is the most
2065 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2067 make kernel-toolchain
2068 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2069 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2071 To test a kernel once
2072 ---------------------
2073 If you just want to boot a kernel once (because you are not sure
2074 if it works, or if you want to boot a known bad kernel to provide
2075 debugging information) run
2076 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2077 nextboot -k testkernel
2079 To rebuild everything and install it on the current system.
2080 -----------------------------------------------------------
2081 # Note: sometimes if you are running current you gotta do more than
2082 # is listed here if you are upgrading from a really old current.
2084 <make sure you have good level 0 dumps>
2086 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2087 make installkernel KERNCONF=YOUR_KERNEL_HERE
2089 <reboot in single user> [3]
2096 To cross-install current onto a separate partition
2097 --------------------------------------------------
2098 # In this approach we use a separate partition to hold
2099 # current's root, 'usr', and 'var' directories. A partition
2100 # holding "/", "/usr" and "/var" should be about 2GB in
2103 <make sure you have good level 0 dumps>
2106 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2107 <maybe newfs current's root partition>
2108 <mount current's root partition on directory ${CURRENT_ROOT}>
2109 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2110 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2111 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2112 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2113 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2114 <reboot into current>
2115 <do a "native" rebuild/install as described in the previous section>
2116 <maybe install compatibility libraries from ports/misc/compat*>
2120 To upgrade in-place from stable to current
2121 ----------------------------------------------
2122 <make sure you have good level 0 dumps>
2124 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2125 make installkernel KERNCONF=YOUR_KERNEL_HERE
2127 <reboot in single user> [3]
2134 Make sure that you've read the UPDATING file to understand the
2135 tweaks to various things you need. At this point in the life
2136 cycle of current, things change often and you are on your own
2137 to cope. The defaults can also change, so please read ALL of
2138 the UPDATING entries.
2140 Also, if you are tracking -current, you must be subscribed to
2141 freebsd-current@freebsd.org. Make sure that before you update
2142 your sources that you have read and understood all the recent
2143 messages there. If in doubt, please track -stable which has
2144 much fewer pitfalls.
2146 [1] If you have third party modules, such as vmware, you
2147 should disable them at this point so they don't crash your
2150 [3] From the bootblocks, boot -s, and then do
2154 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2155 cd src # full path to source
2156 adjkerntz -i # if CMOS is wall time
2157 Also, when doing a major release upgrade, it is required that
2158 you boot into single user mode to do the installworld.
2160 [4] Note: This step is non-optional. Failure to do this step
2161 can result in a significant reduction in the functionality of the
2162 system. Attempting to do it by hand is not recommended and those
2163 that pursue this avenue should read this file carefully, as well
2164 as the archives of freebsd-current and freebsd-hackers mailing lists
2165 for potential gotchas. The -U option is also useful to consider.
2166 See mergemaster(8) for more information.
2168 [5] Usually this step is a no-op. However, from time to time
2169 you may need to do this if you get unknown user in the following
2170 step. It never hurts to do it all the time. You may need to
2171 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2172 install) after the buildworld before this step if you last updated
2173 from current before 20130425 or from -stable before 20130430.
2175 [6] This only deletes old files and directories. Old libraries
2176 can be deleted by "make delete-old-libs", but you have to make
2177 sure that no program is using those libraries anymore.
2179 [8] The new kernel must be able to run existing binaries used by an
2180 installworld. When upgrading across major versions, the new kernel's
2181 configuration must include the correct COMPAT_FREEBSD<n> option for
2182 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2183 to do so may leave you with a system that is hard to boot to recover. A
2184 GENERIC kernel will include suitable compatibility options to run
2185 binaries from older branches. Note that the ability to run binaries
2186 from unsupported branches is not guaranteed.
2188 Make sure that you merge any new devices from GENERIC since the
2189 last time you updated your kernel config file. Options also
2190 change over time, so you may need to adjust your custom kernels
2193 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2194 "?=" instead of the "=" assignment operator, so that buildworld can
2195 override the CPUTYPE if it needs to.
2197 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2198 not on the command line, or in /etc/make.conf. buildworld will
2199 warn if it is improperly defined.
2202 This file contains a list, in reverse chronological order, of major
2203 breakages in tracking -current. It is not guaranteed to be a complete
2204 list of such breakages, and only contains entries since September 23, 2011.
2205 If you need to see UPDATING entries from before that date, you will need
2206 to fetch an UPDATING file from an older FreeBSD release.
2208 Copyright information:
2210 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2212 Redistribution, publication, translation and use, with or without
2213 modification, in full or in part, in any form or format of this
2214 document are permitted without further permission from the author.
2216 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2217 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2218 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2219 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2220 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2221 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2222 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2223 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2224 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2225 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2226 POSSIBILITY OF SUCH DAMAGE.
2228 Contact Warner Losh if you have any questions about your use of