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