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 r355677 has modified the internal interface used between the
31 NFS modules in the kernel. As such, they must all be upgraded
32 simultaneously. I will do a version bump for this.
35 The root certificates of the Mozilla CA Certificate Store have been
36 imported into the base system and can be managed with the certctl(8)
37 utility. If you have installed the security/ca_root_nss port or package
38 with the ETCSYMLINK option (the default), be advised that there may be
39 differences between those included in the port and those included in
40 base due to differences in nss branch used as well as general update
41 frequency. Note also that certctl(8) cannot manage certs in the
42 format used by the security/ca_root_nss port.
45 The amd(8) automount daemon has been disabled by default, and will be
46 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
50 The nctgpio and wbwd drivers have been moved to the superio bus.
51 If you have one of these drivers in a kernel configuration, then
52 you should add device superio to it. If you use one of these drivers
53 as a module and you compile a custom set of modules, then you should
54 add superio to the set.
57 KPIs for network drivers to access interface addresses have changed.
58 Users need to recompile NIC driver modules together with kernel.
61 The net.link.tap.user_open sysctl no longer prevents user opening of
62 already created /dev/tapNN devices. Access is still controlled by
63 node permissions, just like tun devices. The net.link.tap.user_open
64 sysctl is now used only to allow users to perform devfs cloning of
65 tap devices, and the subsequent open may not succeed if the user is not
66 in the appropriate group. This sysctl may be deprecated/removed
67 completely in the future.
70 mips, powerpc, and sparc64 are no longer built as part of
71 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
72 not defined, mips, powerpc, and sparc64 builds will look for
73 the xtoolchain binaries and if installed use them for universe
74 builds. As llvm 9.0 becomes vetted for these architectures, they
75 will be removed from the list.
78 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
79 been upgraded to 9.0.0. Please see the 20141231 entry below for
80 information about prerequisites and upgrading, if you are not already
81 using clang 3.5.0 or higher.
84 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
85 GENERIC. They are available as modules and can be loaded by adding
86 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
87 hptnr_load="YES", or hptrr_load="YES", respectively.
90 ntpd no longer by default locks its pages in memory, allowing them
91 to be paged out by the kernel. Use rlimit memlock to restore
92 historic BSD behaviour. For example, add "rlimit memlock 32"
93 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
96 Several of ping6's options have been renamed for better consistency
97 with ping. If you use any of -ARWXaghmrtwx, you must update your
98 scripts. See ping6(8) for details.
101 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
102 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
103 been removed from mount_fusefs(8). You can safely remove them from
104 your scripts, because they had no effect.
106 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
107 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
108 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
109 sysctls have been removed. If you felt the need to set any of them to
110 a non-default value, please tell asomers@FreeBSD.org why.
113 Default permissions on the /var/account/acct file (and copies of it
114 rotated by periodic daily scripts) are changed from 0644 to 0640
115 because the file contains sensitive information that should not be
116 world-readable. If the /var/account directory must be created by
117 rc.d/accounting, the mode used is now 0750. Admins who use the
118 accounting feature are encouraged to change the mode of an existing
119 /var/account directory to 0750 or 0700.
122 Entropy collection and the /dev/random device are no longer optional
123 components. The "device random" option has been removed.
124 Implementations of distilling algorithms can still be made loadable
125 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
128 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
129 been upgraded to 8.0.1. Please see the 20141231 entry below for
130 information about prerequisites and upgrading, if you are not already
131 using clang 3.5.0 or higher.
134 A fix was applied to i386 kernel modules to avoid panics with
135 dpcpu or vnet. Users need to recompile i386 kernel modules
136 having pcpu or vnet sections or they will refuse to load.
139 User-wired pages now have their own counter,
140 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
141 to vm.max_user_wired and changed from an unsigned int to an unsigned
142 long. bhyve VMs wired with the -S are now subject to the user
143 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
144 avoid running into the limit.
147 The IPSEC option has been removed from GENERIC. Users requiring
148 ipsec(4) must now load the ipsec(4) kernel module.
151 The tap(4) driver has been folded into tun(4), and the module has been
152 renamed to tuntap. You should update any kld_list="if_tap" or
153 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
154 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
155 module instead, and "device tap" or "device tun" entries in kernel
156 config files to select the tuntap device instead.
159 The following knobs have been added related to tradeoffs between
160 safe use of the random device and availability in the absence of
163 kern.random.initial_seeding.bypass_before_seeding: tunable; set
164 non-zero to bypass the random device prior to seeding, or zero to
165 block random requests until the random device is initially seeded.
166 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
167 availability properties.
169 kern.random.initial_seeding.read_random_bypassed_before_seeding:
170 read-only diagnostic sysctl that is set when bypass is enabled and
171 read_random(9) is bypassed, to enable programmatic handling of this
172 initial condition, if desired.
174 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
175 Similar to the above, but for for arc4random(9) initial seeding.
177 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
178 non-zero to disable warnings in dmesg when the same conditions are
179 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
180 produce warnings in dmesg when the conditions are met.
183 The loadable random module KPI has changed; the random_infra_init()
184 routine now requires a 3rd function pointer for a bool (*)(void)
185 method that returns true if the random device is seeded (and
186 therefore unblocked).
189 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
190 built from head sources between r320757 (July 6, 2017) and
191 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
192 is added to the command line.
193 nfsuserd daemons built from head sources that are post-r338192 are
194 not affected and should continue to work.
197 The fuse(4) module has been renamed to fusefs(4) for consistency with
198 other filesystems. You should update any kld_load="fuse" entries in
199 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
200 "options FUSE" entries in kernel config files.
203 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
204 8.0.0. Please see the 20141231 entry below for information about
205 prerequisites and upgrading, if you are not already using clang 3.5.0
209 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
210 compiled into your custom kernel, add 'device xz' statement to the
214 drm and drm2 have been removed from the tree. Please see
215 https://wiki.freebsd.org/Graphics for the latest information on
216 migrating to the drm ports.
219 Iflib is no longer unconditionally compiled into the kernel. Drivers
220 using iflib and statically compiled into the kernel, now require
221 the 'device iflib' config option. For the same drivers loaded as
222 modules on kernels not having 'device iflib', the iflib.ko module
223 is loaded automatically.
226 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
227 options no longer exist since r343219 and r343427 respectively;
228 nothing uses them, so they should be just removed from custom
232 r342635 changes the way efibootmgr(8) works by requiring users to add
233 the -b (bootnum) parameter for commands where the bootnum was previously
234 specified with each option. For example 'efibootmgr -B 0001' is now
235 'efibootmgr -B -b 0001'.
238 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
239 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
240 servers that have vfs.nfsd.nfs_privport set will only allow mounts
241 from clients using a reserved port#. Since both the FreeBSD and Linux
242 NFSv4 clients use reserved port#s by default, this should not affect
246 The XLP config has been removed. We can't support 64-bit atomics in this
247 kernel because it is running in 32-bit mode. XLP users must transition
248 to running a 64-bit kernel (XLP64 or XLPN32).
250 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
251 the preferred emulator today and we don't need two different ones.
253 The old sibyte / swarm / Broadcom BCM1250 support has been
254 removed from the mips port.
257 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
258 7.0.1. Please see the 20141231 entry below for information about
259 prerequisites and upgrading, if you are not already using clang 3.5.0
263 Remove the timed and netdate programs from the base tree. Setting
264 the time with these daemons has been obsolete for over a decade.
267 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
268 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
269 it produces broken binaries when ifuncs are in use. Users needing
270 GNU ld should install the binutils port or package.
273 The BSD crtbegin and crtend code has been enabled by default. It has
274 had extensive testing on amd64, arm64, and i386. It can be disabled
275 by building a world with -DWITHOUT_BSD_CRTBEGIN.
278 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
279 has been converted to a port (misc/ctm) and will be removed from
280 FreeBSD-13. It is available as a package (ctm) for all supported
284 The default newsyslog.conf(5) file has been changed to only include
285 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
286 the filenames end in '.conf' and do not begin with a '.'.
288 You should check the configuration files in these two directories match
289 this naming convention. You can verify which configuration files are
290 being included using the command:
294 Ports for the DRM modules have been simplified. Now, amd64 users should
295 just install the drm-kmod port. All others should install
298 Graphics hardware that's newer than about 2010 usually works with
299 drm-kmod. For hardware older than 2013, however, some users will need
300 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
301 than 2008 usually only works in drm-legacy-kmod. The graphics team can
302 only commit to hardware made since 2013 due to the complexity of the
303 market and difficulty to test all the older cards effectively. If you
304 have hardware supported by drm-kmod, you are strongly encouraged to use
305 that as you will get better support.
307 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
308 elsewhere, the drm and drm2 modules will be eliminated from the src base
309 soon (with a limited exception for arm). Please update to the package
310 asap and report any issues to x11@freebsd.org.
312 Generally, anybody using the drm*-kmod packages should add
313 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
314 cross-threading surprises, especially with automatic driver
315 loading from X11 startup. These will become the defaults in 13-current
319 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
320 custom kernel and module loading configuration files must be updated
321 accordingly. Moreover, interfaces previous presented as ixlvN to the
322 system are now exposed as iavfN and network configuration files must
323 be adjusted as necessary.
326 OpenSSL has been updated to version 1.1.1. This update included
327 additional various API changes throughout the base system. It is
328 important to rebuild third-party software after upgrading. The value
329 of __FreeBSD_version has been bumped accordingly.
332 The legacy DRM modules and drivers have now been added to the loader's
333 module blacklist, in favor of loading them with kld_list in rc.conf(5).
334 The module blacklist may be overridden with the loader.conf(5)
335 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
339 The cam(4) based nda(4) driver will be used over nvd(4) by default on
340 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
341 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
342 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
346 Reproducible build mode is now on by default, in preparation for
347 FreeBSD 12.0. This eliminates build metadata such as the user,
348 host, and time from the kernel (and uname), unless the working tree
349 corresponds to a modified checkout from a version control system.
350 The previous behavior can be obtained by setting the /etc/src.conf
351 knob WITHOUT_REPRODUCIBLE_BUILD.
354 The Yarrow CSPRNG has been removed from the kernel as it has not been
355 supported by its designers since at least 2003. Fortuna has been the
356 default since FreeBSD-11.
359 devctl freeze/thaw have gone into the tree, the rc scripts have been
360 updated to use them and devmatch has been changed. You should update
361 kernel, userland and rc scripts all at the same time.
364 The default interpreter has been switched from 4th to Lua.
365 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
366 interpreter. If you have custom FORTH code you will need to set
367 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
368 src.conf for the build. This will create default hard links between
369 loader and loader_4th instead of loader and loader_lua, the new default.
370 If you are using UEFI it will create the proper hard link to loader.efi.
372 bhyve uses userboot.so. It remains 4th-only until some issues are solved
373 regarding coexisting with multiple versions of FreeBSD are resolved.
376 ls(1) now respects the COLORTERM environment variable used in other
377 systems and software to indicate that a colored terminal is both
378 supported and desired. If ls(1) is suddenly emitting colors, they may
379 be disabled again by either removing the unwanted COLORTERM from your
380 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
381 may not be observed in a future release.
384 The default pager for most commands has been changed to "less". To
385 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
389 The jedec_ts(4) driver has been removed. A superset of its functionality
390 is available in the jedec_dimm(4) driver, and the manpage for that
391 driver includes migration instructions. If you have "device jedec_ts"
392 in your kernel configuration file, it must be removed.
395 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
396 This should have no effect if the kernel is booted via BIOS/legacy boot.
397 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
398 has a buggy firmware that prevents a successful boot due to use of
402 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
403 support has been removed from the tree. These ports were
404 obsolete and/or known to be broken for many years.
407 loader.efi has been augmented to participate more fully in the
408 UEFI boot manager protocol. loader.efi will now look at the
409 BootXXXX environment variable to determine if a specific kernel
410 or root partition was specified. XXXX is derived from BootCurrent.
411 efibootmgr(8) manages these standard UEFI variables.
414 zfsloader's functionality has now been folded into loader.
415 zfsloader is no longer necessary once you've updated your
416 boot blocks. For a transition period, we will install a
417 hardlink for zfsloader to loader to allow a smooth transition
418 until the boot blocks can be updated (hard link because old
419 zfs boot blocks don't understand symlinks).
422 ARM64 now have efifb support, if you want to have serial console
423 on your arm64 board when an screen is connected and the bootloader
424 setup a frame buffer for us to use, just add :
428 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
429 an screen connected as the firmware will setup a frame buffer are that
430 u-boot will expose as an EFI frame buffer.
433 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
434 or take steps to update /etc/passwd before doing installworld on
435 existing systems. Do not skip the "mergemaster -Fp" step before
436 installworld, as described in the update procedures near the bottom
437 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
438 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
439 the ntp config file contain options that change file/dir locations.
440 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
441 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
442 taking steps to ensure that all required files/dirs are accessible
446 Big endian arm support has been removed.
449 The static environment setup in kernel configs is no longer mutually
450 exclusive with the loader(8) environment by default. In order to
451 restore the previous default behavior of disabling the loader(8)
452 environment if a static environment is present, you must specify
453 loader_env.disabled=1 in the static environment.
456 The ABI of syscalls used by management tools like sockstat and
457 netstat has been broken to allow 32-bit binaries to work on
458 64-bit kernels without modification. These programs will need
459 to match the kernel in order to function. External programs may
460 require minor modifications to accommodate a change of type in
461 structures from pointers to 64-bit virtual addresses.
464 On i386 and amd64 atomics are now inlined. Out of tree modules using
465 atomics will need to be rebuilt.
468 The '%I' format in the kern.corefile sysctl limits the number of
469 core files that a process can generate to the number stored in the
470 debug.ncores sysctl. The '%I' format is replaced by the single digit
471 index. Previously, if all indexes were taken the kernel would overwrite
472 only a core file with the highest index in a filename.
473 Currently the system will create a new core file if there is a free
474 index or if all slots are taken it will overwrite the oldest one.
477 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
478 6.0.1. Please see the 20141231 entry below for information about
479 prerequisites and upgrading, if you are not already using clang 3.5.0
483 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
484 needed to be changed to work with it. This change was made with r335763
485 and requires a mergemaster / etcupdate / etc to update the installed
489 r334930 changed the interface between the NFS modules, so they all
490 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
493 As of r334391 lld is the default amd64 system linker; it is installed
494 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
498 The kernel / userland interface for devinfo changed, so you'll
499 need a new kernel and userland as a pair for it to work (rebuilding
500 lib/libdevinfo is all that's required). devinfo and devmatch will
501 not work, but everything else will when there's a mismatch.
504 The on-disk format for hwpmc callchain records has changed to include
505 threadid corresponding to a given record. This changes the field offsets
506 and thus requires that libpmcstat be rebuilt before using a kernel
510 The vxge(4) driver has been removed. This driver was introduced into
511 HEAD one week before the Exar left the Ethernet market and is not
512 known to be used. If you have device vxge in your kernel config file
516 The amd64 kernel now requires a ld that supports ifunc to produce a
517 working kernel, either lld or a newer binutils. lld is built by default
518 on amd64, and the 'buildkernel' target uses it automatically. However,
519 it is not the default linker, so building the kernel the traditional
520 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
521 binutils port/package). lld will soon be default, and this requirement
524 NOTE: As of r334391 lld is the default system linker on amd64, and no
525 workaround is necessary.
528 The nxge(4) driver has been removed. This driver was for PCI-X 10g
529 cards made by s2io/Neterion. The company was acquired by Exar and
530 no longer sells or supports Ethernet products. If you have device
531 nxge in your kernel config file it must be removed.
534 The tz database (tzdb) has been updated to 2018e. This version more
535 correctly models time stamps in time zones with negative DST such as
536 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
537 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
538 time zone abbreviations and the tm_isdst flag.
541 The ixgb(4) driver has been removed. This driver was for an early and
542 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
543 quickly shifted to the long lived ixgbe family. If you have device
544 ixgb in your kernel config file it must be removed.
547 The lmc(4) driver has been removed. This was a WAN interface
548 card that was already reportedly rare in 2003, and had an ambiguous
549 license. If you have device lmc in your kernel config file it must
553 Support for Arcnet networks has been removed. If you have device
554 arcnet or device cm in your kernel config file they must be
558 Support for FDDI networks has been removed. If you have device
559 fddi or device fpa in your kernel config file they must be
563 In addition to supporting RFC 3164 formatted messages, the
564 syslogd(8) service is now capable of parsing RFC 5424 formatted
565 log messages. The main benefit of using RFC 5424 is that clients
566 may now send log messages with timestamps containing year numbers,
567 microseconds and time zone offsets.
569 Similarly, the syslog(3) C library function has been altered to
570 send RFC 5424 formatted messages to the local system logging
571 daemon. On systems using syslogd(8), this change should have no
572 negative impact, as long as syslogd(8) and the C library are
573 updated at the same time. On systems using a different system
574 logging daemon, it may be necessary to make configuration
575 adjustments, depending on the software used.
577 When using syslog-ng, add the 'syslog-protocol' flag to local
578 input sources to enable parsing of RFC 5424 formatted messages:
581 unix-dgram("/var/run/log" flags(syslog-protocol));
584 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
585 of the 'imuxsock' module to let messages be processed by the
586 regular RFC 3164/5424 parsing pipeline:
588 module(load="imuxsock" SysSock.UseSpecialParser="off")
590 Do note that these changes only affect communication between local
591 applications and syslogd(8). The format that syslogd(8) uses to
592 store messages on disk or forward messages to other systems
593 remains unchanged. syslogd(8) still uses RFC 3164 for these
594 purposes. Options to customize this behaviour will be added in the
595 future. Utilities that process log files stored in /var/log are
596 thus expected to continue to function as before.
598 __FreeBSD_version has been incremented to 1200061 to denote this
602 Support for token ring networks has been removed. If you
603 have "device token" in your kernel config you should remove
604 it. No device drivers supported token ring.
607 makefs was modified to be able to tag ISO9660 El Torito boot catalog
608 entries as EFI instead of overloading the i386 tag as done previously.
609 The amd64 mkisoimages.sh script used to build amd64 ISO images for
610 release was updated to use this. This may mean that makefs must be
611 updated before "make cdrom" can be run in the release directory. This
612 should be as simple as:
614 $ cd $SRCDIR/usr.sbin/makefs
615 $ make depend all install
618 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
619 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
620 Co-existence for the transition period will come shortly. Booting is a
621 complex environment and test coverage for Lua-enabled loaders has been
622 thin, so it would be prudent to assume it might not work and make
623 provisions for backup boot methods.
626 devmatch functionality has been turned on in devd. It will automatically
627 load drivers for unattached devices. This may cause unexpected drivers
628 to be loaded. Please report any problems to current@ and
632 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
633 6.0.0. Please see the 20141231 entry below for information about
634 prerequisites and upgrading, if you are not already using clang 3.5.0
638 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
639 This means it is used to link the kernel and userland libraries and
640 executables, but is not yet installed as /usr/bin/ld by default.
642 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
643 WITHOUT_LLD_BOOTSTRAP=yes
646 On i386, pmtimer has been removed. Its functionality has been folded
647 into apm. It was a no-op on ACPI in current for a while now (but was
648 still needed on i386 in FreeBSD 11 and earlier). Users may need to
649 remove it from kernel config files.
652 The use of RSS hash from the network card aka flowid has been
653 disabled by default for lagg(4) as it's currently incompatible with
654 the lacp and loadbalance protocols.
656 This can be re-enabled by setting the following in loader.conf:
657 net.link.lagg.default_use_flowid="1"
660 The SW_WATCHDOG option is no longer necessary to enable the
661 hardclock-based software watchdog if no hardware watchdog is
662 configured. As before, SW_WATCHDOG will cause the software
663 watchdog to be enabled even if a hardware watchdog is configured.
666 r326887 fixes the issue described in the 20171214 UPDATING entry.
667 r326888 flips the switch back to building GELI support always.
670 r362593 broke ZFS + GELI support for reasons unknown. However,
671 it also broke ZFS support generally, so GELI has been turned off
672 by default as the lesser evil in r326857. If you boot off ZFS and/or
673 GELI, it might not be a good time to update.
676 PowerPC users must update loader(8) by rebuilding world before
677 installing a new kernel, as the protocol connecting them has
678 changed. Without the update, loader metadata will not be passed
679 successfully to the kernel and users will have to enter their
680 root partition at the kernel mountroot prompt to continue booting.
681 Newer versions of loader can boot old kernels without issue.
684 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
685 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
686 to WITH/OUT_LOADER_GELI.
689 The naive and non-compliant support of posix_fallocate(2) in ZFS
690 has been removed as of r325320. The system call now returns EINVAL
691 when used on a ZFS file. Although the new behavior complies with the
692 standard, some consumers are not prepared to cope with it.
693 One known victim is lld prior to r325420.
696 Building in a FreeBSD src checkout will automatically create object
697 directories now rather than store files in the current directory if
698 'make obj' was not ran. Calling 'make obj' is no longer necessary.
699 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
700 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
704 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
705 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
706 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
707 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
708 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
709 The UNIFIED_OBJDIR option is a transitional feature that will be
710 removed for 12.0 release; please migrate to the new format for any
711 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
712 than hardcoding paths.
715 The native-xtools target no longer installs the files by default to the
716 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
717 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
720 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
721 options are changing from controlling the build if defined / undefined
722 to controlling the build with explicit 'yes' or 'no' values. They will
723 shift to WITH/WITHOUT options to match other options in the system.
726 libstand has turned into a private library for sys/boot use only.
727 It is no longer supported as a public interface outside of sys/boot.
730 The arm port has split armv6 into armv6 and armv7. armv7 is now
731 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
732 and are running a kernel from before r324363, you will need to add
733 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
736 When building multiple kernels using KERNCONF, non-existent KERNCONF
737 files will produce an error and buildkernel will fail. Previously
738 missing KERNCONF files silently failed giving no indication as to
739 why, only to subsequently discover during installkernel that the
740 desired kernel was never built in the first place.
743 The default serial number format for CTL LUNs has changed. This will
744 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
745 or iSCSI clients care about their LUNs' serial numbers. Users who
746 require serial number stability should hardcode serial numbers in
750 For 32-bit arm compiled for hard-float support, soft-floating point
751 binaries now always get their shared libraries from
752 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
753 /usr/libsoft also existed). Only users with a hard-float ld.so, but
754 soft-float everything else should be affected.
757 The geli password typed at boot is now hidden. To restore the previous
758 behavior, see geli(8) for configuration options.
761 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
762 sysctl values. Minor nit, but requires a rebuild of both world/kernel
766 "make check" behavior (made in ^/head@r295380) has been changed to
767 execute from a limited sandbox, as opposed to executing from
771 - The "beforecheck" and "aftercheck" targets are now specified.
772 - ${CHECKDIR} (added in commit noted above) has been removed.
773 - Legacy behavior can be enabled by setting
774 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
776 If the limited sandbox mode is enabled, "make check" will execute
777 "make distribution", then install, execute the tests, and clean up the
778 sandbox if successful.
780 The "make distribution" and "make install" targets are typically run as
781 root to set appropriate permissions and ownership at installation time.
782 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
783 environment if executing "make check" with limited sandbox mode using
784 an unprivileged user.
787 Since the switch to GPT disk labels, fsck for UFS/FFS has been
788 unable to automatically find alternate superblocks. As of r322297,
789 the information needed to find alternate superblocks has been
790 moved to the end of the area reserved for the boot block.
791 Filesystems created with a newfs of this vintage or later
792 will create the recovery information. If you have a filesystem
793 created prior to this change and wish to have a recovery block
794 created for your filesystem, you can do so by running fsck in
795 foreground mode (i.e., do not use the -p or -y options). As it
796 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
797 to which you should answer yes.
800 As of r321665, an NFSv4 server configuration that services
801 Kerberos mounts or clients that do not support the uid/gid in
802 owner/owner_group string capability, must explicitly enable
803 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
804 machine's /etc/rc.conf file.
807 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
808 Please see the 20141231 entry below for information about prerequisites
809 and upgrading, if you are not already using clang 3.5.0 or higher.
812 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
813 r-commands (rlogin, rsh, etc.) to be built with the base system.
816 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
817 a very major ABI incompatible change, so users of FreeBSD/powerpc must
818 be careful when performing source upgrades. It is best to run
819 'make installworld' from an alternate root system, either a live
820 CD/memory stick, or a temporary root partition. Additionally, all ports
821 must be recompiled. powerpc64 is largely unaffected, except in the case
822 of 32-bit compatibility. All 32-bit binaries will be affected.
825 Forward compatibility for the "ino64" project have been committed. This
826 will allow most new binaries to run on older kernels in a limited
827 fashion. This prevents many of the common foot-shooting actions in the
828 upgrade as well as the limited ability to roll back the kernel across
829 the ino64 upgrade. Complicated use cases may not work properly, though
830 enough simpler ones work to allow recovery in most situations.
833 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
834 if you require the GPL compiler.
837 The internal ABI used for communication between the NFS kernel modules
838 was changed by r320085, so __FreeBSD_version was bumped to
839 ensure all the NFS related modules are updated together.
842 The ABI of struct event was changed by extending the data
843 member to 64bit and adding ext fields. For upgrade, same
844 precautions as for the entry 20170523 "ino64" must be
848 The GNU roff toolchain has been removed from base. To render manpages
849 which are not supported by mandoc(1), man(1) can fallback on GNU roff
850 from ports (and recommends to install it).
851 To render roff(7) documents, consider using GNU roff from ports or the
852 heirloom doctools roff toolchain from ports via pkg install groff or
853 via pkg install heirloom-doctools.
856 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
857 smaller runtime footprint builds. This is useful for embedded systems
858 which only require one chipset support.
860 If you load it as a module, make sure this is in /boot/loader.conf:
864 This will load the HAL, all chip/RF backends and if_ath_pci.
865 If you have if_ath_pci in /boot/loader.conf, ensure it is after
866 if_ath or it will not load any HAL chipset support.
868 If you want to selectively load things (eg on ye cheape ARM/MIPS
869 platforms where RAM is at a premium) you should:
872 * load the chip modules in question
873 * load ath_rate, ath_dfs
875 * load if_ath_pci and/or if_ath_ahb depending upon your particular
876 bus bind type - this is where probe/attach is done.
878 For further comments/feedback, poke adrian@ .
881 The "ino64" 64-bit inode project has been committed, which extends
882 a number of types to 64 bits. Upgrading in place requires care and
883 adherence to the documented upgrade procedure.
885 If using a custom kernel configuration ensure that the
886 COMPAT_FREEBSD11 option is included (as during the upgrade the
887 system will be running the ino64 kernel with the existing world).
889 For the safest in-place upgrade begin by removing previous build
890 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
891 procedure documented below under the heading "To rebuild everything and
892 install it on the current system." Specifically, a reboot is required
893 after installing the new kernel before installing world. While an
894 installworld normally works by accident from multiuser after rebooting
895 the proper kernel, there are many cases where this will fail across this
896 upgrade and installworld from single user is required.
899 The NATM framework including the en(4), fatm(4), hatm(4), and
900 patm(4) devices has been removed. Consumers should plan a
901 migration before the end-of-life date for FreeBSD 11.
904 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
905 diff has not been implemented, if those are needed a newer version of
906 GNU diff is available via the diffutils package under the gdiff name.
909 As of r316810 for ipfilter, keep frags is no longer assumed when
910 keep state is specified in a rule. r316810 aligns ipfilter with
911 documentation in man pages separating keep frags from keep state.
912 This allows keep state to be specified without forcing keep frags
913 and allows keep frags to be specified independently of keep state.
914 To maintain previous behaviour, also specify keep frags with
915 keep state (as documented in ipf.conf.5).
918 arm64 builds now use the base system LLD 4.0.0 linker by default,
919 instead of requiring that the aarch64-binutils port or package be
920 installed. To continue using aarch64-binutils, set
921 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
924 The UDP optimization in entry 20160818 that added the sysctl
925 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
926 packets will no longer be treated as L3 broadcast packets.
929 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
930 use any explicitly assigned loopback address available in the jail
931 instead of using the first assigned address of the jail.
934 The ctl.ko module no longer implements the iSCSI target frontend:
935 cfiscsi.ko does instead.
937 If building cfiscsi.ko as a kernel module, the module can be loaded
938 via one of the following methods:
939 - `cfiscsi_load="YES"` in loader.conf(5).
940 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
941 - ctladm(8)/ctld(8), when compiled with iSCSI support
942 (`WITH_ISCSI=yes` in src.conf(5))
944 Please see cfiscsi(4) for more details.
947 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
948 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
949 same source (previously, the dependency of mmcsd.ko on mmc.ko was
950 missing, but mmcsd.ko now will refuse to load if it is incompatible
954 The syntax of ipfw(8) named states was changed to avoid ambiguity.
955 If you have used named states in the firewall rules, you need to modify
956 them after installworld and before rebooting. Now named states must
957 be prefixed with colon.
960 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
961 removed as the userland we provide cannot use them. The KMS version
962 (sys/dev/drm2) supports the same hardware.
965 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
966 Please see the 20141231 entry below for information about prerequisites
967 and upgrading, if you are not already using clang 3.5.0 or higher.
970 The code that provides support for ZFS .zfs/ directory functionality
971 has been reimplemented. It's not possible now to create a snapshot
972 by mkdir under .zfs/snapshot/. That should be the only user visible
976 EISA bus support has been removed. The WITH_EISA option is no longer
980 MCA bus support has been removed.
983 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
984 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
987 The EM_MULTIQUEUE kernel configuration option is deprecated now that
988 the em(4) driver conforms to iflib specifications.
991 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
992 IFLIB. If you have a custom kernel configuration that excludes em(4)
993 but you use igb(4), you need to re-add em(4) to your custom
997 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
998 Please see the 20141231 entry below for information about prerequisites
999 and upgrading, if you are not already using clang 3.5.0 or higher.
1002 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1003 Please see the 20141231 entry below for information about prerequisites
1004 and upgrading, if you are not already using clang 3.5.0 or higher.
1007 The layout of the pmap structure has changed for powerpc to put the pmap
1008 statistics at the front for all CPU variations. libkvm(3) and all tools
1009 that link against it need to be recompiled.
1012 isl(4) and cyapa(4) drivers now require a new driver,
1013 chromebook_platform(4), to work properly on Chromebook-class hardware.
1014 On other types of hardware the drivers may need to be configured using
1015 device hints. Please see the corresponding manual pages for details.
1018 The urtwn(4) driver was merged into rtwn(4) and now consists of
1019 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1021 Also, firmware for RTL8188CE was renamed due to possible name
1022 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1025 GNU rcs has been removed from base. It is available as packages:
1026 - rcs: Latest GPLv3 GNU rcs version.
1027 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1031 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1032 modules now requires that the kernel configuration contain the
1033 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1036 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1037 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1040 Relocatable object files with the extension of .So have been renamed
1041 to use an extension of .pico instead. The purpose of this change is
1042 to avoid a name clash with shared libraries on case-insensitive file
1043 systems. On those file systems, foo.So is the same file as foo.so.
1046 GNU rcs has been turned off by default. It can (temporarily) be built
1047 again by adding WITH_RCS knob in src.conf.
1048 Otherwise, GNU rcs is available from packages:
1049 - rcs: Latest GPLv3 GNU rcs version.
1050 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1053 The backup_uses_rcs functionality has been removed from rc.subr.
1056 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1057 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1058 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1059 QUEUE_MACRO_DEBUG behavior.
1062 r304787 changed some ioctl interfaces between the iSCSI userspace
1063 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1064 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1068 The UDP receive code has been updated to only treat incoming UDP
1069 packets that were addressed to an L2 broadcast address as L3
1070 broadcast packets. It is not expected that this will affect any
1071 standards-conforming UDP application. The new behaviour can be
1072 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1076 Remove the openbsd_poll system call.
1077 __FreeBSD_version has been bumped because of this.
1080 The stable/11 branch has been created from head@r302406.
1083 The libc stub for the pipe(2) system call has been replaced with
1084 a wrapper that calls the pipe2(2) system call and the pipe(2)
1085 system call is now only implemented by the kernels that include
1086 "options COMPAT_FREEBSD10" in their config file (this is the
1087 default). Users should ensure that this option is enabled in
1088 their kernel or upgrade userspace to r302092 before upgrading their
1092 CAM will now strip leading spaces from SCSI disks' serial numbers.
1093 This will affect users who create UFS filesystems on SCSI disks using
1094 those disk's diskid device nodes. For example, if /etc/fstab
1095 previously contained a line like
1096 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1097 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1098 transforms like gmirror may also be affected. ZFS users should
1102 The bitstring(3) API has been updated with new functionality and
1103 improved performance. But it is binary-incompatible with the old API.
1104 Objects built with the new headers may not be linked against objects
1105 built with the old headers.
1108 The brk and sbrk functions have been removed from libc on arm64.
1109 Binutils from ports has been updated to not link to these
1110 functions and should be updated to the latest version before
1111 installing a new libc.
1114 The armv6 port now defaults to hard float ABI. Limited support
1115 for running both hardfloat and soft float on the same system
1116 is available using the libraries installed with -DWITH_LIBSOFT.
1117 This has only been tested as an upgrade path for installworld
1118 and packages may fail or need manual intervention to run. New
1119 packages will be needed.
1121 To update an existing self-hosted armv6hf system, you must add
1122 TARGET_ARCH=armv6 on the make command line for both the build
1123 and the install steps.
1126 Kernel modules compiled outside of a kernel build now default to
1127 installing to /boot/modules instead of /boot/kernel. Many kernel
1128 modules built this way (such as those in ports) already overrode
1129 KMODDIR explicitly to install into /boot/modules. However,
1130 manually building and installing a module from /sys/modules will
1131 now install to /boot/modules instead of /boot/kernel.
1134 The CAM I/O scheduler has been committed to the kernel. There should be
1135 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1136 list of known rogues that claim support for this but actually corrupt
1137 data is believed to be complete, be on the lookout for data
1138 corruption. The known rogue list is believed to be complete:
1140 o Crucial MX100, M550 drives with MU01 firmware.
1141 o Micron M510 and M550 drives with MU01 firmware.
1142 o Micron M500 prior to MU07 firmware
1143 o Samsung 830, 840, and 850 all firmwares
1144 o FCCT M500 all firmwares
1146 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1147 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1148 updated firmware. Black listed drives will work correctly because these
1149 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1150 this list is the same as found in Linux, it's believed there are no
1151 other rogues in the market place. All other models from the above
1154 To be safe, if you are at all concerned, you can quirk each of your
1155 drives to prevent NCQ from being sent by setting:
1156 kern.cam.ada.X.quirks="0x2"
1157 in loader.conf. If the drive requires the 4k sector quirk, set the
1158 quirks entry to 0x3.
1161 The FAST_DEPEND build option has been removed and its functionality is
1162 now the one true way. The old mkdep(1) style of 'make depend' has
1163 been removed. See 20160311 for further details.
1166 Resource range types have grown from unsigned long to uintmax_t. All
1167 drivers, and anything using libdevinfo, need to be recompiled.
1170 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1171 builds. It no longer runs mkdep(1) during 'make depend', and the
1172 'make depend' stage can safely be skipped now as it is auto ran
1173 when building 'make all' and will generate all SRCS and DPSRCS before
1174 building anything else. Dependencies are gathered at compile time with
1175 -MF flags kept in separate .depend files per object file. Users should
1176 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1177 stale .depend files.
1180 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1181 kernel modules. Therefore, if you load any kernel modules at boot time,
1182 please install the boot loaders after you install the kernel, but before
1186 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1187 make installkernel KERNCONF=YOUR_KERNEL_HERE
1188 make -C sys/boot install
1189 <reboot in single user>
1191 Then follow the usual steps, described in the General Notes section,
1195 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1196 see the 20141231 entry below for information about prerequisites and
1197 upgrading, if you are not already using clang 3.5.0 or higher.
1200 The AIO subsystem is now a standard part of the kernel. The
1201 VFS_AIO kernel option and aio.ko kernel module have been removed.
1202 Due to stability concerns, asynchronous I/O requests are only
1203 permitted on sockets and raw disks by default. To enable
1204 asynchronous I/O requests on all file types, set the
1205 vfs.aio.enable_unsafe sysctl to a non-zero value.
1208 The ELF object manipulation tool objcopy is now provided by the
1209 ELF Tool Chain project rather than by GNU binutils. It should be a
1210 drop-in replacement, with the addition of arm64 support. The
1211 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1212 to obtain the GNU version if necessary.
1215 Building ZFS pools on top of zvols is prohibited by default. That
1216 feature has never worked safely; it's always been prone to deadlocks.
1217 Using a zvol as the backing store for a VM guest's virtual disk will
1218 still work, even if the guest is using ZFS. Legacy behavior can be
1219 restored by setting vfs.zfs.vol.recursive=1.
1222 The NONE and HPN patches has been removed from OpenSSH. They are
1223 still available in the security/openssh-portable port.
1226 With the addition of ypldap(8), a new _ypldap user is now required
1227 during installworld. "mergemaster -p" can be used to add the user
1228 prior to installworld, as documented in the handbook.
1231 The tftp loader (pxeboot) now uses the option root-path directive. As a
1232 consequence it no longer looks for a pxeboot.4th file on the tftp
1233 server. Instead it uses the regular /boot infrastructure as with the
1237 The code to start recording plug and play data into the modules has
1238 been committed. While the old tools will properly build a new kernel,
1239 a number of warnings about "unknown metadata record 4" will be produced
1240 for an older kldxref. To avoid such warnings, make sure to rebuild
1241 the kernel toolchain (or world). Make sure that you have r292078 or
1242 later when trying to build 292077 or later before rebuilding.
1245 Debug data files are now built by default with 'make buildworld' and
1246 installed with 'make installworld'. This facilitates debugging but
1247 requires more disk space both during the build and for the installed
1248 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1252 r291527 changed the internal interface between the nfsd.ko and
1253 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1254 __FreeBSD_version has been bumped because of this.
1257 Add support for unicode collation strings leads to a change of
1258 order of files listed by ls(1) for example. To get back to the old
1259 behaviour, set LC_COLLATE environment variable to "C".
1261 Databases administrators will need to reindex their databases given
1262 collation results will be different.
1264 Due to a bug in install(1) it is recommended to remove the ancient
1265 locales before running make installworld.
1267 rm -rf /usr/share/locale/*
1270 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1271 libcrypto.so.7 or libssl.so.7 must be recompiled.
1274 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1275 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1276 should be replaced with isp_2400 and isp_2500 modules respectively.
1279 The build previously allowed using 'make -n' to not recurse into
1280 sub-directories while showing what commands would be executed, and
1281 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1282 and 'make -N' will not.
1285 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1286 and etcupdate will now use this file. A custom sendmail.cf is now
1287 updated via this mechanism rather than via installworld. If you had
1288 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1289 want to remove the exclusion or change it to "always install".
1290 /etc/mail/sendmail.cf is now managed the same way regardless of
1291 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1292 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1295 Compatibility shims for legacy ATA device names have been removed.
1296 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1297 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1298 environment variables, /dev/ad* and /dev/ar* symbolic links.
1301 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1302 Please see the 20141231 entry below for information about prerequisites
1303 and upgrading, if you are not already using clang 3.5.0 or higher.
1306 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1307 and renamed from .symbols to .debug. This reduces the size requirements
1308 on the boot partition or file system and provides consistency with
1309 userland debug files.
1311 When using the supported kernel installation method the
1312 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1313 as is done with /boot/kernel.
1315 Developers wishing to maintain the historical behavior of installing
1316 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1319 The wireless drivers had undergone changes that remove the 'parent
1320 interface' from the ifconfig -l output. The rc.d network scripts
1321 used to check presence of a parent interface in the list, so old
1322 scripts would fail to start wireless networking. Thus, etcupdate(3)
1323 or mergemaster(8) run is required after kernel update, to update your
1324 rc.d scripts in /etc.
1327 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1328 These configurations are now automatically interpreted as
1329 'scrub fragment reassemble'.
1332 Kernel-loadable modules for the random(4) device are back. To use
1333 them, the kernel must have
1336 options RANDOM_LOADABLE
1338 kldload(8) can then be used to load random_fortuna.ko
1339 or random_yarrow.ko. Please note that due to the indirect
1340 function calls that the loadable modules need to provide,
1341 the build-in variants will be slightly more efficient.
1343 The random(4) kernel option RANDOM_DUMMY has been retired due to
1344 unpopularity. It was not all that useful anyway.
1347 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1348 Control over building the ELF Tool Chain tools is now provided by
1349 the WITHOUT_TOOLCHAIN knob.
1352 The polarity of Pulse Per Second (PPS) capture events with the
1353 uart(4) driver has been corrected. Prior to this change the PPS
1354 "assert" event corresponded to the trailing edge of a positive PPS
1355 pulse and the "clear" event was the leading edge of the next pulse.
1357 As the width of a PPS pulse in a typical GPS receiver is on the
1358 order of 1 millisecond, most users will not notice any significant
1359 difference with this change.
1361 Anyone who has compensated for the historical polarity reversal by
1362 configuring a negative offset equal to the pulse width will need to
1363 remove that workaround.
1366 The default group assigned to /dev/dri entries has been changed
1367 from 'wheel' to 'video' with the id of '44'. If you want to have
1368 access to the dri devices please add yourself to the video group
1371 # pw groupmod video -m $USER
1374 The menu.rc and loader.rc files will now be replaced during
1375 upgrades. Please migrate local changes to menu.rc.local and
1376 loader.rc.local instead.
1379 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1380 strings and strip have been removed. The src.conf(5) knob
1381 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1384 As ZFS requires more kernel stack pages than is the default on some
1385 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1386 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1388 Please consider using 'options KSTACK_PAGES=X' where X is greater
1389 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1392 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1393 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1394 default, i.e., they will not contain "::". For example, instead
1395 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1396 to have a more specific match, such as different map entries for
1397 IPv6:0:0 vs IPv6:0. This change requires that configuration
1398 data (including maps, files, classes, custom ruleset, etc.) must
1399 use the same format, so make certain such configuration data is
1400 upgrading. As a very simple check search for patterns like
1401 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1402 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1403 the cf option UseCompressedIPv6Addresses.
1406 The default kernel entropy-processing algorithm is now
1407 Fortuna, replacing Yarrow.
1409 Assuming you have 'device random' in your kernel config
1410 file, the configurations allow a kernel option to override
1411 this default. You may choose *ONE* of:
1413 options RANDOM_YARROW # Legacy /dev/random algorithm.
1414 options RANDOM_DUMMY # Blocking-only driver.
1416 If you have neither, you get Fortuna. For most people,
1417 read no further, Fortuna will give a /dev/random that works
1418 like it always used to, and the difference will be irrelevant.
1420 If you remove 'device random', you get *NO* kernel-processed
1421 entropy at all. This may be acceptable to folks building
1422 embedded systems, but has complications. Carry on reading,
1423 and it is assumed you know what you need.
1425 *PLEASE* read random(4) and random(9) if you are in the
1426 habit of tweaking kernel configs, and/or if you are a member
1427 of the embedded community, wanting specific and not-usual
1428 behaviour from your security subsystems.
1430 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1431 random', you will NOT have a functioning /dev/random, and
1432 many cryptographic features will not work, including SSH.
1433 You may also find strange behaviour from the random(3) set
1434 of library functions, in particular sranddev(3), srandomdev(3)
1435 and arc4random(3). The reason for this is that the KERN_ARND
1436 sysctl only returns entropy if it thinks it has some to
1437 share, and with RANDOM_DUMMY or no 'device random' this
1441 An additional fix for the issue described in the 20150614 sendmail
1442 entry below has been committed in revision 284717.
1445 FreeBSD's old make (fmake) has been removed from the system. It is
1446 available as the devel/fmake port or via pkg install fmake.
1449 The fix for the issue described in the 20150614 sendmail entry
1450 below has been committed in revision 284436. The work
1451 around described in that entry is no longer needed unless the
1452 default setting is overridden by a confDH_PARAMETERS configuration
1453 setting of '5' or pointing to a 512 bit DH parameter file.
1456 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1457 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1458 and devel/kyua to version 0.20+ and adjust any calling code to work
1459 with Kyuafile and kyua.
1462 The import of openssl to address the FreeBSD-SA-15:10.openssl
1463 security advisory includes a change which rejects handshakes
1464 with DH parameters below 768 bits. sendmail releases prior
1465 to 8.15.2 (not yet released), defaulted to a 512 bit
1466 DH parameter setting for client connections. To work around
1467 this interoperability, sendmail can be configured to use a
1468 2048 bit DH parameter by:
1470 1. Edit /etc/mail/`hostname`.mc
1471 2. If a setting for confDH_PARAMETERS does not exist or
1472 exists and is set to a string beginning with '5',
1473 replace it with '2'.
1474 3. If a setting for confDH_PARAMETERS exists and is set to
1475 a file path, create a new file with:
1476 openssl dhparam -out /path/to/file 2048
1477 4. Rebuild the .cf file:
1478 cd /etc/mail/; make; make install
1479 5. Restart sendmail:
1480 cd /etc/mail/; make restart
1482 A sendmail patch is coming, at which time this file will be
1486 Generation of legacy formatted entries have been disabled by default
1487 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1488 entries were converted to use the new format by default when the new,
1489 machine independent format have been added and supported since FreeBSD
1492 Please see the pwd_mkdb(8) manual page for further details.
1495 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1496 20141231 entry below for information about prerequisites and upgrading,
1497 if you are not already using 3.5.0 or higher.
1500 TI platform code switched to using vendor DTS files and this update
1501 may break existing systems running on Beaglebone, Beaglebone Black,
1504 - dtb files should be regenerated/reinstalled. Filenames are the
1505 same but content is different now
1506 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1507 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1508 addressing scheme is now pin 25 on /dev/gpioc3.
1509 - Pandaboard: /etc/ttys should be updated, serial console device is
1510 now /dev/ttyu2, not /dev/ttyu0
1513 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1514 If you need the GNU extension from groff soelim(1), install groff
1515 from package: pkg install groff, or via ports: textproc/groff.
1518 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1519 defined in symlink(7); previously symlinks were silently ignored.
1522 The const qualifier has been removed from iconv(3) to comply with
1523 POSIX. The ports tree is aware of this from r384038 onwards.
1526 Libraries specified by LIBADD in Makefiles must have a corresponding
1527 DPADD_<lib> variable to ensure correct dependencies. This is now
1528 enforced in src.libnames.mk.
1531 From legacy ata(4) driver was removed support for SATA controllers
1532 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1533 Kernel modules ataahci and ataadaptec were removed completely,
1534 replaced by ahci and mvs modules respectively.
1537 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1538 the 20141231 entry below for information about prerequisites and
1539 upgrading, if you are not already using 3.5.0 or higher.
1542 The 32-bit PowerPC kernel has been changed to a position-independent
1543 executable. This can only be booted with a version of loader(8)
1544 newer than January 31, 2015, so make sure to update both world and
1545 kernel before rebooting.
1548 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1549 but before r278950, the RNG was not seeded properly. Immediately
1550 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1551 ssh keys or openssl keys) that were generated w/ a kernel from that
1552 range. This does not affect programs that directly used /dev/random
1553 or /dev/urandom. All userland uses of arc4random(3) are affected.
1556 The autofs(4) ABI was changed in order to restore binary compatibility
1557 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1558 with the new kernel.
1561 The powerpc64 kernel has been changed to a position-independent
1562 executable. This can only be booted with a new version of loader(8),
1563 so make sure to update both world and kernel before rebooting.
1566 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1567 only release, no new features have been added. Please see the 20141231
1568 entry below for information about prerequisites and upgrading, if you
1569 are not already using 3.5.0.
1572 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1573 taken from the ELF Tool Chain project rather than GNU binutils. They
1574 should be drop-in replacements, with the addition of arm64 support.
1575 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1576 binutils tools, if necessary. See 20150805 for updated information.
1579 The default Unbound configuration now enables remote control
1580 using a local socket. Users who have already enabled the
1581 local_unbound service should regenerate their configuration
1582 by running "service local_unbound setup" as root.
1585 The GNU texinfo and GNU info pages have been removed.
1586 To be able to view GNU info pages please install texinfo from ports.
1589 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1591 As of this release, a prerequisite for building clang, llvm and lldb is
1592 a C++11 capable compiler and C++11 standard library. This means that to
1593 be able to successfully build the cross-tools stage of buildworld, with
1594 clang as the bootstrap compiler, your system compiler or cross compiler
1595 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1596 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1599 On any standard FreeBSD 10.x or 11.x installation, where clang and
1600 libc++ are on by default (that is, on x86 or arm), this should work out
1603 On 9.x installations where clang is enabled by default, e.g. on x86 and
1604 powerpc, libc++ will not be enabled by default, so libc++ should be
1605 built (with clang) and installed first. If both clang and libc++ are
1606 missing, build clang first, then use it to build libc++.
1608 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1609 the instructions for 9.x above.
1611 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1612 default, and do not build clang.
1614 Many embedded systems are resource constrained, and will not be able to
1615 build clang in a reasonable time, or in some cases at all. In those
1616 cases, cross building bootable systems on amd64 is a workaround.
1618 This new version of clang introduces a number of new warnings, of which
1619 the following are most likely to appear:
1623 This warns in two cases, for both C and C++:
1624 * When the code is trying to take the absolute value of an unsigned
1625 quantity, which is effectively a no-op, and almost never what was
1626 intended. The code should be fixed, if at all possible. If you are
1627 sure that the unsigned quantity can be safely cast to signed, without
1628 loss of information or undefined behavior, you can add an explicit
1629 cast, or disable the warning.
1631 * When the code is trying to take an absolute value, but the called
1632 abs() variant is for the wrong type, which can lead to truncation.
1633 If you want to disable the warning instead of fixing the code, please
1634 make sure that truncation will not occur, or it might lead to unwanted
1637 -Wtautological-undefined-compare and
1638 -Wundefined-bool-conversion
1640 These warn when C++ code is trying to compare 'this' against NULL, while
1641 'this' should never be NULL in well-defined C++ code. However, there is
1642 some legacy (pre C++11) code out there, which actively abuses this
1643 feature, which was less strictly defined in previous C++ versions.
1645 Squid and openjdk do this, for example. The warning can be turned off
1646 for C++98 and earlier, but compiling the code in C++11 mode might result
1647 in unexpected behavior; for example, the parts of the program that are
1648 unreachable could be optimized away.
1651 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1652 kernel sources have been removed. The .h files remain, since some
1653 utilities include them. This will need to be fixed later.
1654 If "mount -t oldnfs ..." is attempted, it will fail.
1655 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1656 the utilities will report errors.
1659 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1660 directories to top level SUBDIR variable when their parent
1661 directory is included in LOCAL_DIRS. Users with build systems with
1662 such hierarchies and without SUBDIR entries in the parent
1663 directory Makefiles should add them or add the directories to
1667 faith(4) and faithd(8) have been removed from the base system. Faith
1668 has been obsolete for a very long time.
1671 vt(4), the new console driver, is enabled by default. It brings
1672 support for Unicode and double-width characters, as well as
1673 support for UEFI and integration with the KMS kernel video
1676 You may need to update your console settings in /etc/rc.conf,
1677 most probably the keymap. During boot, /etc/rc.d/syscons will
1678 indicate what you need to do.
1680 vt(4) still has issues and lacks some features compared to
1681 syscons(4). See the wiki for up-to-date information:
1682 https://wiki.freebsd.org/Newcons
1684 If you want to keep using syscons(4), you can do so by adding
1685 the following line to /boot/loader.conf:
1689 pjdfstest has been integrated into kyua as an opt-in test suite.
1690 Please see share/doc/pjdfstest/README for more details on how to
1694 gperf has been removed from the base system for architectures
1695 that use clang. Ports that require gperf will obtain it from the
1699 pjdfstest has been moved from tools/regression/pjdfstest to
1703 At svn r271982, The default linux compat kernel ABI has been adjusted
1704 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1705 update. If you wish to continue using the linux-f10 compat ports,
1706 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1707 encouraged to update their linux-compat packages to linux-c6 during
1708 their next update cycle.
1711 The ofwfb driver, used to provide a graphics console on PowerPC when
1712 using vt(4), no longer allows mmap() of all physical memory. This
1713 will prevent Xorg on PowerPC with some ATI graphics cards from
1714 initializing properly unless x11-servers/xorg-server is updated to
1718 The xdev targets have been converted to using TARGET and
1719 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1722 The default unbound configuration has been modified to address
1723 issues with reverse lookups on networks that use private
1724 address ranges. If you use the local_unbound service, run
1725 "service local_unbound setup" as root to regenerate your
1726 configuration, then "service local_unbound reload" to load the
1730 The GNU texinfo and GNU info pages are not built and installed
1731 anymore, WITH_INFO knob has been added to allow to built and install
1733 UPDATE: see 20150102 entry on texinfo's removal
1736 The GNU readline library is now an INTERNALLIB - that is, it is
1737 statically linked into consumers (GDB and variants) in the base
1738 system, and the shared library is no longer installed. The
1739 devel/readline port is available for third party software that
1743 The Itanium architecture (ia64) has been removed from the list of
1744 known architectures. This is the first step in the removal of the
1748 Commit r268115 has added NFSv4.1 server support, merged from
1749 projects/nfsv4.1-server. Since this includes changes to the
1750 internal interfaces between the NFS related modules, a full
1751 build of the kernel and modules will be necessary.
1752 __FreeBSD_version has been bumped.
1755 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1756 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1757 which differs from the behaviour controlled by this knob.)
1760 Maximal length of the serial number in CTL was increased from 16 to
1761 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1762 and ctld, need to be rebuilt to work with a new kernel.
1765 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1766 1 respectively to match the upstream numbers. They were out of
1767 sync because, when they were originally added to FreeBSD, the
1768 upstream versions were not respected. These libraries are private
1769 and not yet built by default, so renumbering them should be a
1770 non-issue. However, unclean source trees will yield broken test
1771 programs once the operator executes "make delete-old-libs" after a
1772 "make installworld".
1774 Additionally, the atf-sh binary was made private by moving it into
1775 /usr/libexec/. Already-built shell test programs will keep the
1776 path to the old binary so they will break after "make delete-old"
1779 If you are using WITH_TESTS=yes (not the default), wipe the object
1780 tree and rebuild from scratch to prevent spurious test failures.
1781 This is only needed once: the misnumbered libraries and misplaced
1782 binaries have been added to OptionalObsoleteFiles.inc so they will
1783 be removed during a clean upgrade.
1786 Clang and llvm have been upgraded to 3.4.1 release.
1789 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1790 be removed to avoid issues in the future (and has been added to
1794 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1795 past, it affected all builds that used the bsd.*.mk files. The old
1796 behavior was a bug, but people may have relied upon it. To get this
1797 behavior back, you can .include /etc/src.conf from /etc/make.conf
1798 (which is still global and isn't changed). This also changes the
1799 behavior of incremental builds inside the tree of individual
1800 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1801 Although this has survived make universe and some upgrade scenarios,
1802 other upgrade scenarios may have broken. At least one form of
1803 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1804 as well... In cases where MAKESYSPATH isn't working with this
1805 setting, you'll need to set it to the full path to your tree.
1807 One side effect of all this cleaning up is that bsd.compiler.mk
1808 is no longer implicitly included by bsd.own.mk. If you wish to
1809 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1813 The lindev device has been removed since /dev/full has been made a
1814 standard device. __FreeBSD_version has been bumped.
1817 The knob WITHOUT_VI was added to the base system, which controls
1818 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1819 in order to reorder files share/termcap and didn't build ex(1) as a
1820 build tool, so building/installing with WITH_VI is highly advised for
1821 build hosts for older releases.
1823 This issue has been fixed in stable/9 and stable/10 in r277022 and
1824 r276991, respectively.
1827 The YES_HESIOD knob has been removed. It has been obsolete for
1828 a decade. Please move to using WITH_HESIOD instead or your builds
1829 will silently lack HESIOD.
1832 The uart(4) driver has been changed with respect to its handling
1833 of the low-level console. Previously the uart(4) driver prevented
1834 any process from changing the baudrate or the CLOCAL and HUPCL
1835 control flags. By removing the restrictions, operators can make
1836 changes to the serial console port without having to reboot.
1837 However, when getty(8) is started on the serial device that is
1838 associated with the low-level console, a misconfigured terminal
1839 line in /etc/ttys will now have a real impact.
1840 Before upgrading the kernel, make sure that /etc/ttys has the
1841 serial console device configured as 3wire without baudrate to
1842 preserve the previous behaviour. E.g:
1843 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1846 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1847 to improve performance. To re-enable it, if needed, run rpcbind
1848 with command line option -W.
1851 Switched back to the GPL dtc compiler due to updates in the upstream
1852 dts files not being supported by the BSDL dtc compiler. You will need
1853 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1854 may result while building dtb files during a kernel build if you fail
1855 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1858 Clang and llvm have been upgraded to 3.4 release.
1861 The nve(4) driver has been removed. Please use the nfe(4) driver
1862 for NVIDIA nForce MCP Ethernet adapters instead.
1865 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1866 This could cause certain C++ applications using shared libraries built
1867 against the previous version of libc++ to crash. The incompatibility
1868 has now been fixed, but any C++ applications or shared libraries built
1869 between r261283 and r261801 should be recompiled.
1872 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1873 capability mode support. Please note that enabling the feature in
1874 kernel is still highly recommended.
1877 OpenSSH is now built with sandbox support, and will use sandbox as
1878 the default privilege separation method. This requires Capsicum
1879 capability mode support in kernel.
1882 The libelf and libdwarf libraries have been updated to newer
1883 versions from upstream. Shared library version numbers for
1884 these two libraries were bumped. Any ports or binaries
1885 requiring these two libraries should be recompiled.
1886 __FreeBSD_version is bumped to 1100006.
1889 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1890 instead of providing an explicit one, this would prevent such
1891 Makefile from providing its own Kyuafile in the future during
1892 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1893 intervention is needed to clean an objdir if you use NO_CLEAN:
1894 # find /usr/obj -name Kyuafile | xargs rm -f
1897 The behavior of gss_pseudo_random() for the krb5 mechanism
1898 has changed, for applications requesting a longer random string
1899 than produced by the underlying enctype's pseudo-random() function.
1900 In particular, the random string produced from a session key of
1901 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1902 be different at the 17th octet and later, after this change.
1903 The counter used in the PRF+ construction is now encoded as a
1904 big-endian integer in accordance with RFC 4402.
1905 __FreeBSD_version is bumped to 1100004.
1908 The WITHOUT_ATF build knob has been removed and its functionality
1909 has been subsumed into the more generic WITHOUT_TESTS. If you were
1910 using the former to disable the build of the ATF libraries, you
1911 should change your settings to use the latter.
1914 The default version of mtree is nmtree which is obtained from
1915 NetBSD. The output is generally the same, but may vary
1916 slightly. If you found you need identical output adding
1917 "-F freebsd9" to the command line should do the trick. For the
1918 time being, the old mtree is available as fmtree.
1921 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1922 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1923 1.1.4_8 and verify bsdyml not linked in, before running "make
1925 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1927 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1930 The stable/10 branch has been created in subversion from head
1937 Sometimes, obscure build problems are the result of environment
1938 poisoning. This can happen because the make utility reads its
1939 environment when searching for values for global variables. To run
1940 your build attempts in an "environmental clean room", prefix all make
1941 commands with 'env -i '. See the env(1) manual page for more details.
1942 Occasionally a build failure will occur with "make -j" due to a race
1943 condition. If this happens try building again without -j, and please
1944 report a bug if it happens consistently.
1946 When upgrading from one major version to another it is generally best to
1947 upgrade to the latest code in the currently installed branch first, then
1948 do an upgrade to the new branch. This is the best-tested upgrade path,
1949 and has the highest probability of being successful. Please try this
1950 approach if you encounter problems with a major version upgrade. Since
1951 the stable 4.x branch point, one has generally been able to upgrade from
1952 anywhere in the most recent stable branch to head / current (or even the
1953 last couple of stable branches). See the top of this file when there's
1956 When upgrading a live system, having a root shell around before
1957 installing anything can help undo problems. Not having a root shell
1958 around can lead to problems if pam has changed too much from your
1959 starting point to allow continued authentication after the upgrade.
1961 This file should be read as a log of events. When a later event changes
1962 information of a prior event, the prior event should not be deleted.
1963 Instead, a pointer to the entry with the new information should be
1964 placed in the old entry. Readers of this file should also sanity check
1965 older entries before relying on them blindly. Authors of new entries
1966 should write them with this in mind.
1970 When upgrading the boot ZFS pool to a new version, always follow
1973 1.) recompile and reinstall the ZFS boot loader and boot block
1974 (this is part of "make buildworld" and "make installworld")
1976 2.) update the ZFS boot block on your boot drive
1978 The following example updates the ZFS boot block on the first
1979 partition (freebsd-boot) of a GPT partitioned drive ada0:
1980 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1982 Non-boot pools do not need these updates.
1986 If you are updating from a prior version of FreeBSD (even one just
1987 a few days old), you should follow this procedure. It is the most
1988 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1990 make kernel-toolchain
1991 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1992 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1994 To test a kernel once
1995 ---------------------
1996 If you just want to boot a kernel once (because you are not sure
1997 if it works, or if you want to boot a known bad kernel to provide
1998 debugging information) run
1999 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2000 nextboot -k testkernel
2002 To rebuild everything and install it on the current system.
2003 -----------------------------------------------------------
2004 # Note: sometimes if you are running current you gotta do more than
2005 # is listed here if you are upgrading from a really old current.
2007 <make sure you have good level 0 dumps>
2009 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2010 make installkernel KERNCONF=YOUR_KERNEL_HERE
2012 <reboot in single user> [3]
2019 To cross-install current onto a separate partition
2020 --------------------------------------------------
2021 # In this approach we use a separate partition to hold
2022 # current's root, 'usr', and 'var' directories. A partition
2023 # holding "/", "/usr" and "/var" should be about 2GB in
2026 <make sure you have good level 0 dumps>
2029 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2030 <maybe newfs current's root partition>
2031 <mount current's root partition on directory ${CURRENT_ROOT}>
2032 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2033 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2034 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2035 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2036 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2037 <reboot into current>
2038 <do a "native" rebuild/install as described in the previous section>
2039 <maybe install compatibility libraries from ports/misc/compat*>
2043 To upgrade in-place from stable to current
2044 ----------------------------------------------
2045 <make sure you have good level 0 dumps>
2047 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2048 make installkernel KERNCONF=YOUR_KERNEL_HERE
2050 <reboot in single user> [3]
2057 Make sure that you've read the UPDATING file to understand the
2058 tweaks to various things you need. At this point in the life
2059 cycle of current, things change often and you are on your own
2060 to cope. The defaults can also change, so please read ALL of
2061 the UPDATING entries.
2063 Also, if you are tracking -current, you must be subscribed to
2064 freebsd-current@freebsd.org. Make sure that before you update
2065 your sources that you have read and understood all the recent
2066 messages there. If in doubt, please track -stable which has
2067 much fewer pitfalls.
2069 [1] If you have third party modules, such as vmware, you
2070 should disable them at this point so they don't crash your
2073 [3] From the bootblocks, boot -s, and then do
2077 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2078 cd src # full path to source
2079 adjkerntz -i # if CMOS is wall time
2080 Also, when doing a major release upgrade, it is required that
2081 you boot into single user mode to do the installworld.
2083 [4] Note: This step is non-optional. Failure to do this step
2084 can result in a significant reduction in the functionality of the
2085 system. Attempting to do it by hand is not recommended and those
2086 that pursue this avenue should read this file carefully, as well
2087 as the archives of freebsd-current and freebsd-hackers mailing lists
2088 for potential gotchas. The -U option is also useful to consider.
2089 See mergemaster(8) for more information.
2091 [5] Usually this step is a no-op. However, from time to time
2092 you may need to do this if you get unknown user in the following
2093 step. It never hurts to do it all the time. You may need to
2094 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2095 install) after the buildworld before this step if you last updated
2096 from current before 20130425 or from -stable before 20130430.
2098 [6] This only deletes old files and directories. Old libraries
2099 can be deleted by "make delete-old-libs", but you have to make
2100 sure that no program is using those libraries anymore.
2102 [8] The new kernel must be able to run existing binaries used by an
2103 installworld. When upgrading across major versions, the new kernel's
2104 configuration must include the correct COMPAT_FREEBSD<n> option for
2105 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2106 to do so may leave you with a system that is hard to boot to recover. A
2107 GENERIC kernel will include suitable compatibility options to run
2108 binaries from older branches. Note that the ability to run binaries
2109 from unsupported branches is not guaranteed.
2111 Make sure that you merge any new devices from GENERIC since the
2112 last time you updated your kernel config file. Options also
2113 change over time, so you may need to adjust your custom kernels
2116 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2117 "?=" instead of the "=" assignment operator, so that buildworld can
2118 override the CPUTYPE if it needs to.
2120 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2121 not on the command line, or in /etc/make.conf. buildworld will
2122 warn if it is improperly defined.
2125 This file contains a list, in reverse chronological order, of major
2126 breakages in tracking -current. It is not guaranteed to be a complete
2127 list of such breakages, and only contains entries since September 23, 2011.
2128 If you need to see UPDATING entries from before that date, you will need
2129 to fetch an UPDATING file from an older FreeBSD release.
2131 Copyright information:
2133 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2135 Redistribution, publication, translation and use, with or without
2136 modification, in full or in part, in any form or format of this
2137 document are permitted without further permission from the author.
2139 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2140 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2141 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2142 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2143 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2144 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2145 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2146 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2147 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2148 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2149 POSSIBILITY OF SUCH DAMAGE.
2151 Contact Warner Losh if you have any questions about your use of