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