1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
15 FreeBSD 13.x has many debugging features turned on, in both the kernel
16 and userland. These features attempt to detect incorrect use of
17 system primitives, and encourage loud failure through extra sanity
18 checking and fail stop semantics. They also substantially impact
19 system performance. If you want to do performance measurement,
20 benchmarking, and optimization, you'll want to turn them off. This
21 includes various WITNESS- related kernel options, INVARIANTS, malloc
22 debugging flags in userland, and various verbose features in the
23 kernel. Many developers choose to disable these features on build
24 machines to maximize performance. (To completely disable malloc
25 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
26 disable the most expensive debugging functionality run
27 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
30 The amd(8) automount daemon has been disabled by default, and will be
31 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
35 The nctgpio and wbwd drivers have been moved to the superio bus.
36 If you have one of these drivers in a kernel configuration, then
37 you should add device superio to it. If you use one of these drivers
38 as a module and you compile a custom set of modules, then you should
39 add superio to the set.
42 KPIs for network drivers to access interface addresses have changed.
43 Users need to recompile NIC driver modules together with kernel.
46 The net.link.tap.user_open sysctl no longer prevents user opening of
47 already created /dev/tapNN devices. Access is still controlled by
48 node permissions, just like tun devices. The net.link.tap.user_open
49 sysctl is now used only to allow users to perform devfs cloning of
50 tap devices, and the subsequent open may not succeed if the user is not
51 in the appropriate group. This sysctl may be deprecated/removed
52 completely in the future.
55 mips, powerpc, and sparc64 are no longer built as part of
56 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
57 not defined, mips, powerpc, and sparc64 builds will look for
58 the xtoolchain binaries and if installed use them for universe
59 builds. As llvm 9.0 becomes vetted for these architectures, they
60 will be removed from the list.
63 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
64 been upgraded to 9.0.0. Please see the 20141231 entry below for
65 information about prerequisites and upgrading, if you are not already
66 using clang 3.5.0 or higher.
69 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
70 GENERIC. They are available as modules and can be loaded by adding
71 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
72 hptnr_load="YES", or hptrr_load="YES", respectively.
75 ntpd no longer by default locks its pages in memory, allowing them
76 to be paged out by the kernel. Use rlimit memlock to restore
77 historic BSD behaviour. For example, add "rlimit memlock 32"
78 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
81 Several of ping6's options have been renamed for better consistency
82 with ping. If you use any of -ARWXaghmrtwx, you must update your
83 scripts. See ping6(8) for details.
86 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
87 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
88 been removed from mount_fusefs(8). You can safely remove them from
89 your scripts, because they had no effect.
91 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
92 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
93 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
94 sysctls have been removed. If you felt the need to set any of them to
95 a non-default value, please tell asomers@FreeBSD.org why.
98 Default permissions on the /var/account/acct file (and copies of it
99 rotated by periodic daily scripts) are changed from 0644 to 0640
100 because the file contains sensitive information that should not be
101 world-readable. If the /var/account directory must be created by
102 rc.d/accounting, the mode used is now 0750. Admins who use the
103 accounting feature are encouraged to change the mode of an existing
104 /var/account directory to 0750 or 0700.
107 Entropy collection and the /dev/random device are no longer optional
108 components. The "device random" option has been removed.
109 Implementations of distilling algorithms can still be made loadable
110 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
113 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
114 been upgraded to 8.0.1. Please see the 20141231 entry below for
115 information about prerequisites and upgrading, if you are not already
116 using clang 3.5.0 or higher.
119 A fix was applied to i386 kernel modules to avoid panics with
120 dpcpu or vnet. Users need to recompile i386 kernel modules
121 having pcpu or vnet sections or they will refuse to load.
124 User-wired pages now have their own counter,
125 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
126 to vm.max_user_wired and changed from an unsigned int to an unsigned
127 long. bhyve VMs wired with the -S are now subject to the user
128 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
129 avoid running into the limit.
132 The IPSEC option has been removed from GENERIC. Users requiring
133 ipsec(4) must now load the ipsec(4) kernel module.
136 The tap(4) driver has been folded into tun(4), and the module has been
137 renamed to tuntap. You should update any kld_list="if_tap" or
138 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
139 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
140 module instead, and "device tap" or "device tun" entries in kernel
141 config files to select the tuntap device instead.
144 The following knobs have been added related to tradeoffs between
145 safe use of the random device and availability in the absence of
148 kern.random.initial_seeding.bypass_before_seeding: tunable; set
149 non-zero to bypass the random device prior to seeding, or zero to
150 block random requests until the random device is initially seeded.
151 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
152 availability properties.
154 kern.random.initial_seeding.read_random_bypassed_before_seeding:
155 read-only diagnostic sysctl that is set when bypass is enabled and
156 read_random(9) is bypassed, to enable programmatic handling of this
157 initial condition, if desired.
159 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
160 Similar to the above, but for for arc4random(9) initial seeding.
162 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
163 non-zero to disable warnings in dmesg when the same conditions are
164 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
165 produce warnings in dmesg when the conditions are met.
168 The loadable random module KPI has changed; the random_infra_init()
169 routine now requires a 3rd function pointer for a bool (*)(void)
170 method that returns true if the random device is seeded (and
171 therefore unblocked).
174 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
175 built from head sources between r320757 (July 6, 2017) and
176 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
177 is added to the command line.
178 nfsuserd daemons built from head sources that are post-r338192 are
179 not affected and should continue to work.
182 The fuse(4) module has been renamed to fusefs(4) for consistency with
183 other filesystems. You should update any kld_load="fuse" entries in
184 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
185 "options FUSE" entries in kernel config files.
188 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
189 8.0.0. Please see the 20141231 entry below for information about
190 prerequisites and upgrading, if you are not already using clang 3.5.0
194 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
195 compiled into your custom kernel, add 'device xz' statement to the
199 drm and drm2 have been removed from the tree. Please see
200 https://wiki.freebsd.org/Graphics for the latest information on
201 migrating to the drm ports.
204 Iflib is no longer unconditionally compiled into the kernel. Drivers
205 using iflib and statically compiled into the kernel, now require
206 the 'device iflib' config option. For the same drivers loaded as
207 modules on kernels not having 'device iflib', the iflib.ko module
208 is loaded automatically.
211 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
212 options no longer exist since r343219 and r343427 respectively;
213 nothing uses them, so they should be just removed from custom
217 r342635 changes the way efibootmgr(8) works by requiring users to add
218 the -b (bootnum) parameter for commands where the bootnum was previously
219 specified with each option. For example 'efibootmgr -B 0001' is now
220 'efibootmgr -B -b 0001'.
223 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
224 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
225 servers that have vfs.nfsd.nfs_privport set will only allow mounts
226 from clients using a reserved port#. Since both the FreeBSD and Linux
227 NFSv4 clients use reserved port#s by default, this should not affect
231 The XLP config has been removed. We can't support 64-bit atomics in this
232 kernel because it is running in 32-bit mode. XLP users must transition
233 to running a 64-bit kernel (XLP64 or XLPN32).
235 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
236 the preferred emulator today and we don't need two different ones.
238 The old sibyte / swarm / Broadcom BCM1250 support has been
239 removed from the mips port.
242 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
243 7.0.1. Please see the 20141231 entry below for information about
244 prerequisites and upgrading, if you are not already using clang 3.5.0
248 Remove the timed and netdate programs from the base tree. Setting
249 the time with these daemons has been obsolete for over a decade.
252 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
253 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
254 it produces broken binaries when ifuncs are in use. Users needing
255 GNU ld should install the binutils port or package.
258 The BSD crtbegin and crtend code has been enabled by default. It has
259 had extensive testing on amd64, arm64, and i386. It can be disabled
260 by building a world with -DWITHOUT_BSD_CRTBEGIN.
263 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
264 has been converted to a port (misc/ctm) and will be removed from
265 FreeBSD-13. It is available as a package (ctm) for all supported
269 The default newsyslog.conf(5) file has been changed to only include
270 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
271 the filenames end in '.conf' and do not begin with a '.'.
273 You should check the configuration files in these two directories match
274 this naming convention. You can verify which configuration files are
275 being included using the command:
279 Ports for the DRM modules have been simplified. Now, amd64 users should
280 just install the drm-kmod port. All others should install
283 Graphics hardware that's newer than about 2010 usually works with
284 drm-kmod. For hardware older than 2013, however, some users will need
285 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
286 than 2008 usually only works in drm-legacy-kmod. The graphics team can
287 only commit to hardware made since 2013 due to the complexity of the
288 market and difficulty to test all the older cards effectively. If you
289 have hardware supported by drm-kmod, you are strongly encouraged to use
290 that as you will get better support.
292 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
293 elsewhere, the drm and drm2 modules will be eliminated from the src base
294 soon (with a limited exception for arm). Please update to the package
295 asap and report any issues to x11@freebsd.org.
297 Generally, anybody using the drm*-kmod packages should add
298 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
299 cross-threading surprises, especially with automatic driver
300 loading from X11 startup. These will become the defaults in 13-current
304 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
305 custom kernel and module loading configuration files must be updated
306 accordingly. Moreover, interfaces previous presented as ixlvN to the
307 system are now exposed as iavfN and network configuration files must
308 be adjusted as necessary.
311 OpenSSL has been updated to version 1.1.1. This update included
312 additional various API changes throughout the base system. It is
313 important to rebuild third-party software after upgrading. The value
314 of __FreeBSD_version has been bumped accordingly.
317 The legacy DRM modules and drivers have now been added to the loader's
318 module blacklist, in favor of loading them with kld_list in rc.conf(5).
319 The module blacklist may be overridden with the loader.conf(5)
320 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
324 The cam(4) based nda(4) driver will be used over nvd(4) by default on
325 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
326 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
327 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
331 Reproducible build mode is now on by default, in preparation for
332 FreeBSD 12.0. This eliminates build metadata such as the user,
333 host, and time from the kernel (and uname), unless the working tree
334 corresponds to a modified checkout from a version control system.
335 The previous behavior can be obtained by setting the /etc/src.conf
336 knob WITHOUT_REPRODUCIBLE_BUILD.
339 The Yarrow CSPRNG has been removed from the kernel as it has not been
340 supported by its designers since at least 2003. Fortuna has been the
341 default since FreeBSD-11.
344 devctl freeze/thaw have gone into the tree, the rc scripts have been
345 updated to use them and devmatch has been changed. You should update
346 kernel, userland and rc scripts all at the same time.
349 The default interpreter has been switched from 4th to Lua.
350 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
351 interpreter. If you have custom FORTH code you will need to set
352 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
353 src.conf for the build. This will create default hard links between
354 loader and loader_4th instead of loader and loader_lua, the new default.
355 If you are using UEFI it will create the proper hard link to loader.efi.
357 bhyve uses userboot.so. It remains 4th-only until some issues are solved
358 regarding coexisting with multiple versions of FreeBSD are resolved.
361 ls(1) now respects the COLORTERM environment variable used in other
362 systems and software to indicate that a colored terminal is both
363 supported and desired. If ls(1) is suddenly emitting colors, they may
364 be disabled again by either removing the unwanted COLORTERM from your
365 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
366 may not be observed in a future release.
369 The default pager for most commands has been changed to "less". To
370 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
374 The jedec_ts(4) driver has been removed. A superset of its functionality
375 is available in the jedec_dimm(4) driver, and the manpage for that
376 driver includes migration instructions. If you have "device jedec_ts"
377 in your kernel configuration file, it must be removed.
380 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
381 This should have no effect if the kernel is booted via BIOS/legacy boot.
382 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
383 has a buggy firmware that prevents a successful boot due to use of
387 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
388 support has been removed from the tree. These ports were
389 obsolete and/or known to be broken for many years.
392 loader.efi has been augmented to participate more fully in the
393 UEFI boot manager protocol. loader.efi will now look at the
394 BootXXXX environment variable to determine if a specific kernel
395 or root partition was specified. XXXX is derived from BootCurrent.
396 efibootmgr(8) manages these standard UEFI variables.
399 zfsloader's functionality has now been folded into loader.
400 zfsloader is no longer necessary once you've updated your
401 boot blocks. For a transition period, we will install a
402 hardlink for zfsloader to loader to allow a smooth transition
403 until the boot blocks can be updated (hard link because old
404 zfs boot blocks don't understand symlinks).
407 ARM64 now have efifb support, if you want to have serial console
408 on your arm64 board when an screen is connected and the bootloader
409 setup a frame buffer for us to use, just add :
413 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
414 an screen connected as the firmware will setup a frame buffer are that
415 u-boot will expose as an EFI frame buffer.
418 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
419 or take steps to update /etc/passwd before doing installworld on
420 existing systems. Do not skip the "mergemaster -Fp" step before
421 installworld, as described in the update procedures near the bottom
422 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
423 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
424 the ntp config file contain options that change file/dir locations.
425 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
426 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
427 taking steps to ensure that all required files/dirs are accessible
431 Big endian arm support has been removed.
434 The static environment setup in kernel configs is no longer mutually
435 exclusive with the loader(8) environment by default. In order to
436 restore the previous default behavior of disabling the loader(8)
437 environment if a static environment is present, you must specify
438 loader_env.disabled=1 in the static environment.
441 The ABI of syscalls used by management tools like sockstat and
442 netstat has been broken to allow 32-bit binaries to work on
443 64-bit kernels without modification. These programs will need
444 to match the kernel in order to function. External programs may
445 require minor modifications to accommodate a change of type in
446 structures from pointers to 64-bit virtual addresses.
449 On i386 and amd64 atomics are now inlined. Out of tree modules using
450 atomics will need to be rebuilt.
453 The '%I' format in the kern.corefile sysctl limits the number of
454 core files that a process can generate to the number stored in the
455 debug.ncores sysctl. The '%I' format is replaced by the single digit
456 index. Previously, if all indexes were taken the kernel would overwrite
457 only a core file with the highest index in a filename.
458 Currently the system will create a new core file if there is a free
459 index or if all slots are taken it will overwrite the oldest one.
462 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
463 6.0.1. Please see the 20141231 entry below for information about
464 prerequisites and upgrading, if you are not already using clang 3.5.0
468 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
469 needed to be changed to work with it. This change was made with r335763
470 and requires a mergemaster / etcupdate / etc to update the installed
474 r334930 changed the interface between the NFS modules, so they all
475 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
478 As of r334391 lld is the default amd64 system linker; it is installed
479 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
483 The kernel / userland interface for devinfo changed, so you'll
484 need a new kernel and userland as a pair for it to work (rebuilding
485 lib/libdevinfo is all that's required). devinfo and devmatch will
486 not work, but everything else will when there's a mismatch.
489 The on-disk format for hwpmc callchain records has changed to include
490 threadid corresponding to a given record. This changes the field offsets
491 and thus requires that libpmcstat be rebuilt before using a kernel
495 The vxge(4) driver has been removed. This driver was introduced into
496 HEAD one week before the Exar left the Ethernet market and is not
497 known to be used. If you have device vxge in your kernel config file
501 The amd64 kernel now requires a ld that supports ifunc to produce a
502 working kernel, either lld or a newer binutils. lld is built by default
503 on amd64, and the 'buildkernel' target uses it automatically. However,
504 it is not the default linker, so building the kernel the traditional
505 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
506 binutils port/package). lld will soon be default, and this requirement
509 NOTE: As of r334391 lld is the default system linker on amd64, and no
510 workaround is necessary.
513 The nxge(4) driver has been removed. This driver was for PCI-X 10g
514 cards made by s2io/Neterion. The company was acquired by Exar and
515 no longer sells or supports Ethernet products. If you have device
516 nxge in your kernel config file it must be removed.
519 The tz database (tzdb) has been updated to 2018e. This version more
520 correctly models time stamps in time zones with negative DST such as
521 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
522 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
523 time zone abbreviations and the tm_isdst flag.
526 The ixgb(4) driver has been removed. This driver was for an early and
527 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
528 quickly shifted to the long lived ixgbe family. If you have device
529 ixgb in your kernel config file it must be removed.
532 The lmc(4) driver has been removed. This was a WAN interface
533 card that was already reportedly rare in 2003, and had an ambiguous
534 license. If you have device lmc in your kernel config file it must
538 Support for Arcnet networks has been removed. If you have device
539 arcnet or device cm in your kernel config file they must be
543 Support for FDDI networks has been removed. If you have device
544 fddi or device fpa in your kernel config file they must be
548 In addition to supporting RFC 3164 formatted messages, the
549 syslogd(8) service is now capable of parsing RFC 5424 formatted
550 log messages. The main benefit of using RFC 5424 is that clients
551 may now send log messages with timestamps containing year numbers,
552 microseconds and time zone offsets.
554 Similarly, the syslog(3) C library function has been altered to
555 send RFC 5424 formatted messages to the local system logging
556 daemon. On systems using syslogd(8), this change should have no
557 negative impact, as long as syslogd(8) and the C library are
558 updated at the same time. On systems using a different system
559 logging daemon, it may be necessary to make configuration
560 adjustments, depending on the software used.
562 When using syslog-ng, add the 'syslog-protocol' flag to local
563 input sources to enable parsing of RFC 5424 formatted messages:
566 unix-dgram("/var/run/log" flags(syslog-protocol));
569 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
570 of the 'imuxsock' module to let messages be processed by the
571 regular RFC 3164/5424 parsing pipeline:
573 module(load="imuxsock" SysSock.UseSpecialParser="off")
575 Do note that these changes only affect communication between local
576 applications and syslogd(8). The format that syslogd(8) uses to
577 store messages on disk or forward messages to other systems
578 remains unchanged. syslogd(8) still uses RFC 3164 for these
579 purposes. Options to customize this behaviour will be added in the
580 future. Utilities that process log files stored in /var/log are
581 thus expected to continue to function as before.
583 __FreeBSD_version has been incremented to 1200061 to denote this
587 Support for token ring networks has been removed. If you
588 have "device token" in your kernel config you should remove
589 it. No device drivers supported token ring.
592 makefs was modified to be able to tag ISO9660 El Torito boot catalog
593 entries as EFI instead of overloading the i386 tag as done previously.
594 The amd64 mkisoimages.sh script used to build amd64 ISO images for
595 release was updated to use this. This may mean that makefs must be
596 updated before "make cdrom" can be run in the release directory. This
597 should be as simple as:
599 $ cd $SRCDIR/usr.sbin/makefs
600 $ make depend all install
603 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
604 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
605 Co-existence for the transition period will come shortly. Booting is a
606 complex environment and test coverage for Lua-enabled loaders has been
607 thin, so it would be prudent to assume it might not work and make
608 provisions for backup boot methods.
611 devmatch functionality has been turned on in devd. It will automatically
612 load drivers for unattached devices. This may cause unexpected drivers
613 to be loaded. Please report any problems to current@ and
617 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
618 6.0.0. Please see the 20141231 entry below for information about
619 prerequisites and upgrading, if you are not already using clang 3.5.0
623 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
624 This means it is used to link the kernel and userland libraries and
625 executables, but is not yet installed as /usr/bin/ld by default.
627 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
628 WITHOUT_LLD_BOOTSTRAP=yes
631 On i386, pmtimer has been removed. Its functionality has been folded
632 into apm. It was a no-op on ACPI in current for a while now (but was
633 still needed on i386 in FreeBSD 11 and earlier). Users may need to
634 remove it from kernel config files.
637 The use of RSS hash from the network card aka flowid has been
638 disabled by default for lagg(4) as it's currently incompatible with
639 the lacp and loadbalance protocols.
641 This can be re-enabled by setting the following in loader.conf:
642 net.link.lagg.default_use_flowid="1"
645 The SW_WATCHDOG option is no longer necessary to enable the
646 hardclock-based software watchdog if no hardware watchdog is
647 configured. As before, SW_WATCHDOG will cause the software
648 watchdog to be enabled even if a hardware watchdog is configured.
651 r326887 fixes the issue described in the 20171214 UPDATING entry.
652 r326888 flips the switch back to building GELI support always.
655 r362593 broke ZFS + GELI support for reasons unknown. However,
656 it also broke ZFS support generally, so GELI has been turned off
657 by default as the lesser evil in r326857. If you boot off ZFS and/or
658 GELI, it might not be a good time to update.
661 PowerPC users must update loader(8) by rebuilding world before
662 installing a new kernel, as the protocol connecting them has
663 changed. Without the update, loader metadata will not be passed
664 successfully to the kernel and users will have to enter their
665 root partition at the kernel mountroot prompt to continue booting.
666 Newer versions of loader can boot old kernels without issue.
669 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
670 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
671 to WITH/OUT_LOADER_GELI.
674 The naive and non-compliant support of posix_fallocate(2) in ZFS
675 has been removed as of r325320. The system call now returns EINVAL
676 when used on a ZFS file. Although the new behavior complies with the
677 standard, some consumers are not prepared to cope with it.
678 One known victim is lld prior to r325420.
681 Building in a FreeBSD src checkout will automatically create object
682 directories now rather than store files in the current directory if
683 'make obj' was not ran. Calling 'make obj' is no longer necessary.
684 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
685 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
689 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
690 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
691 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
692 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
693 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
694 The UNIFIED_OBJDIR option is a transitional feature that will be
695 removed for 12.0 release; please migrate to the new format for any
696 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
697 than hardcoding paths.
700 The native-xtools target no longer installs the files by default to the
701 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
702 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
705 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
706 options are changing from controlling the build if defined / undefined
707 to controlling the build with explicit 'yes' or 'no' values. They will
708 shift to WITH/WITHOUT options to match other options in the system.
711 libstand has turned into a private library for sys/boot use only.
712 It is no longer supported as a public interface outside of sys/boot.
715 The arm port has split armv6 into armv6 and armv7. armv7 is now
716 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
717 and are running a kernel from before r324363, you will need to add
718 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
721 When building multiple kernels using KERNCONF, non-existent KERNCONF
722 files will produce an error and buildkernel will fail. Previously
723 missing KERNCONF files silently failed giving no indication as to
724 why, only to subsequently discover during installkernel that the
725 desired kernel was never built in the first place.
728 The default serial number format for CTL LUNs has changed. This will
729 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
730 or iSCSI clients care about their LUNs' serial numbers. Users who
731 require serial number stability should hardcode serial numbers in
735 For 32-bit arm compiled for hard-float support, soft-floating point
736 binaries now always get their shared libraries from
737 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
738 /usr/libsoft also existed). Only users with a hard-float ld.so, but
739 soft-float everything else should be affected.
742 The geli password typed at boot is now hidden. To restore the previous
743 behavior, see geli(8) for configuration options.
746 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
747 sysctl values. Minor nit, but requires a rebuild of both world/kernel
751 "make check" behavior (made in ^/head@r295380) has been changed to
752 execute from a limited sandbox, as opposed to executing from
756 - The "beforecheck" and "aftercheck" targets are now specified.
757 - ${CHECKDIR} (added in commit noted above) has been removed.
758 - Legacy behavior can be enabled by setting
759 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
761 If the limited sandbox mode is enabled, "make check" will execute
762 "make distribution", then install, execute the tests, and clean up the
763 sandbox if successful.
765 The "make distribution" and "make install" targets are typically run as
766 root to set appropriate permissions and ownership at installation time.
767 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
768 environment if executing "make check" with limited sandbox mode using
769 an unprivileged user.
772 Since the switch to GPT disk labels, fsck for UFS/FFS has been
773 unable to automatically find alternate superblocks. As of r322297,
774 the information needed to find alternate superblocks has been
775 moved to the end of the area reserved for the boot block.
776 Filesystems created with a newfs of this vintage or later
777 will create the recovery information. If you have a filesystem
778 created prior to this change and wish to have a recovery block
779 created for your filesystem, you can do so by running fsck in
780 foreground mode (i.e., do not use the -p or -y options). As it
781 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
782 to which you should answer yes.
785 As of r321665, an NFSv4 server configuration that services
786 Kerberos mounts or clients that do not support the uid/gid in
787 owner/owner_group string capability, must explicitly enable
788 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
789 machine's /etc/rc.conf file.
792 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
793 Please see the 20141231 entry below for information about prerequisites
794 and upgrading, if you are not already using clang 3.5.0 or higher.
797 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
798 r-commands (rlogin, rsh, etc.) to be built with the base system.
801 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
802 a very major ABI incompatible change, so users of FreeBSD/powerpc must
803 be careful when performing source upgrades. It is best to run
804 'make installworld' from an alternate root system, either a live
805 CD/memory stick, or a temporary root partition. Additionally, all ports
806 must be recompiled. powerpc64 is largely unaffected, except in the case
807 of 32-bit compatibility. All 32-bit binaries will be affected.
810 Forward compatibility for the "ino64" project have been committed. This
811 will allow most new binaries to run on older kernels in a limited
812 fashion. This prevents many of the common foot-shooting actions in the
813 upgrade as well as the limited ability to roll back the kernel across
814 the ino64 upgrade. Complicated use cases may not work properly, though
815 enough simpler ones work to allow recovery in most situations.
818 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
819 if you require the GPL compiler.
822 The internal ABI used for communication between the NFS kernel modules
823 was changed by r320085, so __FreeBSD_version was bumped to
824 ensure all the NFS related modules are updated together.
827 The ABI of struct event was changed by extending the data
828 member to 64bit and adding ext fields. For upgrade, same
829 precautions as for the entry 20170523 "ino64" must be
833 The GNU roff toolchain has been removed from base. To render manpages
834 which are not supported by mandoc(1), man(1) can fallback on GNU roff
835 from ports (and recommends to install it).
836 To render roff(7) documents, consider using GNU roff from ports or the
837 heirloom doctools roff toolchain from ports via pkg install groff or
838 via pkg install heirloom-doctools.
841 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
842 smaller runtime footprint builds. This is useful for embedded systems
843 which only require one chipset support.
845 If you load it as a module, make sure this is in /boot/loader.conf:
849 This will load the HAL, all chip/RF backends and if_ath_pci.
850 If you have if_ath_pci in /boot/loader.conf, ensure it is after
851 if_ath or it will not load any HAL chipset support.
853 If you want to selectively load things (eg on ye cheape ARM/MIPS
854 platforms where RAM is at a premium) you should:
857 * load the chip modules in question
858 * load ath_rate, ath_dfs
860 * load if_ath_pci and/or if_ath_ahb depending upon your particular
861 bus bind type - this is where probe/attach is done.
863 For further comments/feedback, poke adrian@ .
866 The "ino64" 64-bit inode project has been committed, which extends
867 a number of types to 64 bits. Upgrading in place requires care and
868 adherence to the documented upgrade procedure.
870 If using a custom kernel configuration ensure that the
871 COMPAT_FREEBSD11 option is included (as during the upgrade the
872 system will be running the ino64 kernel with the existing world).
874 For the safest in-place upgrade begin by removing previous build
875 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
876 procedure documented below under the heading "To rebuild everything and
877 install it on the current system." Specifically, a reboot is required
878 after installing the new kernel before installing world. While an
879 installworld normally works by accident from multiuser after rebooting
880 the proper kernel, there are many cases where this will fail across this
881 upgrade and installworld from single user is required.
884 The NATM framework including the en(4), fatm(4), hatm(4), and
885 patm(4) devices has been removed. Consumers should plan a
886 migration before the end-of-life date for FreeBSD 11.
889 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
890 diff has not been implemented, if those are needed a newer version of
891 GNU diff is available via the diffutils package under the gdiff name.
894 As of r316810 for ipfilter, keep frags is no longer assumed when
895 keep state is specified in a rule. r316810 aligns ipfilter with
896 documentation in man pages separating keep frags from keep state.
897 This allows keep state to be specified without forcing keep frags
898 and allows keep frags to be specified independently of keep state.
899 To maintain previous behaviour, also specify keep frags with
900 keep state (as documented in ipf.conf.5).
903 arm64 builds now use the base system LLD 4.0.0 linker by default,
904 instead of requiring that the aarch64-binutils port or package be
905 installed. To continue using aarch64-binutils, set
906 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
909 The UDP optimization in entry 20160818 that added the sysctl
910 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
911 packets will no longer be treated as L3 broadcast packets.
914 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
915 use any explicitly assigned loopback address available in the jail
916 instead of using the first assigned address of the jail.
919 The ctl.ko module no longer implements the iSCSI target frontend:
920 cfiscsi.ko does instead.
922 If building cfiscsi.ko as a kernel module, the module can be loaded
923 via one of the following methods:
924 - `cfiscsi_load="YES"` in loader.conf(5).
925 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
926 - ctladm(8)/ctld(8), when compiled with iSCSI support
927 (`WITH_ISCSI=yes` in src.conf(5))
929 Please see cfiscsi(4) for more details.
932 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
933 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
934 same source (previously, the dependency of mmcsd.ko on mmc.ko was
935 missing, but mmcsd.ko now will refuse to load if it is incompatible
939 The syntax of ipfw(8) named states was changed to avoid ambiguity.
940 If you have used named states in the firewall rules, you need to modify
941 them after installworld and before rebooting. Now named states must
942 be prefixed with colon.
945 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
946 removed as the userland we provide cannot use them. The KMS version
947 (sys/dev/drm2) supports the same hardware.
950 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
951 Please see the 20141231 entry below for information about prerequisites
952 and upgrading, if you are not already using clang 3.5.0 or higher.
955 The code that provides support for ZFS .zfs/ directory functionality
956 has been reimplemented. It's not possible now to create a snapshot
957 by mkdir under .zfs/snapshot/. That should be the only user visible
961 EISA bus support has been removed. The WITH_EISA option is no longer
965 MCA bus support has been removed.
968 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
969 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
972 The EM_MULTIQUEUE kernel configuration option is deprecated now that
973 the em(4) driver conforms to iflib specifications.
976 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
977 IFLIB. If you have a custom kernel configuration that excludes em(4)
978 but you use igb(4), you need to re-add em(4) to your custom
982 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
983 Please see the 20141231 entry below for information about prerequisites
984 and upgrading, if you are not already using clang 3.5.0 or higher.
987 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
988 Please see the 20141231 entry below for information about prerequisites
989 and upgrading, if you are not already using clang 3.5.0 or higher.
992 The layout of the pmap structure has changed for powerpc to put the pmap
993 statistics at the front for all CPU variations. libkvm(3) and all tools
994 that link against it need to be recompiled.
997 isl(4) and cyapa(4) drivers now require a new driver,
998 chromebook_platform(4), to work properly on Chromebook-class hardware.
999 On other types of hardware the drivers may need to be configured using
1000 device hints. Please see the corresponding manual pages for details.
1003 The urtwn(4) driver was merged into rtwn(4) and now consists of
1004 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1006 Also, firmware for RTL8188CE was renamed due to possible name
1007 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1010 GNU rcs has been removed from base. It is available as packages:
1011 - rcs: Latest GPLv3 GNU rcs version.
1012 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1016 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1017 modules now requires that the kernel configuration contain the
1018 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1021 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1022 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1025 Relocatable object files with the extension of .So have been renamed
1026 to use an extension of .pico instead. The purpose of this change is
1027 to avoid a name clash with shared libraries on case-insensitive file
1028 systems. On those file systems, foo.So is the same file as foo.so.
1031 GNU rcs has been turned off by default. It can (temporarily) be built
1032 again by adding WITH_RCS knob in src.conf.
1033 Otherwise, GNU rcs is available from packages:
1034 - rcs: Latest GPLv3 GNU rcs version.
1035 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1038 The backup_uses_rcs functionality has been removed from rc.subr.
1041 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1042 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1043 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1044 QUEUE_MACRO_DEBUG behavior.
1047 r304787 changed some ioctl interfaces between the iSCSI userspace
1048 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1049 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1053 The UDP receive code has been updated to only treat incoming UDP
1054 packets that were addressed to an L2 broadcast address as L3
1055 broadcast packets. It is not expected that this will affect any
1056 standards-conforming UDP application. The new behaviour can be
1057 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1061 Remove the openbsd_poll system call.
1062 __FreeBSD_version has been bumped because of this.
1065 The stable/11 branch has been created from head@r302406.
1068 The libc stub for the pipe(2) system call has been replaced with
1069 a wrapper that calls the pipe2(2) system call and the pipe(2)
1070 system call is now only implemented by the kernels that include
1071 "options COMPAT_FREEBSD10" in their config file (this is the
1072 default). Users should ensure that this option is enabled in
1073 their kernel or upgrade userspace to r302092 before upgrading their
1077 CAM will now strip leading spaces from SCSI disks' serial numbers.
1078 This will affect users who create UFS filesystems on SCSI disks using
1079 those disk's diskid device nodes. For example, if /etc/fstab
1080 previously contained a line like
1081 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1082 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1083 transforms like gmirror may also be affected. ZFS users should
1087 The bitstring(3) API has been updated with new functionality and
1088 improved performance. But it is binary-incompatible with the old API.
1089 Objects built with the new headers may not be linked against objects
1090 built with the old headers.
1093 The brk and sbrk functions have been removed from libc on arm64.
1094 Binutils from ports has been updated to not link to these
1095 functions and should be updated to the latest version before
1096 installing a new libc.
1099 The armv6 port now defaults to hard float ABI. Limited support
1100 for running both hardfloat and soft float on the same system
1101 is available using the libraries installed with -DWITH_LIBSOFT.
1102 This has only been tested as an upgrade path for installworld
1103 and packages may fail or need manual intervention to run. New
1104 packages will be needed.
1106 To update an existing self-hosted armv6hf system, you must add
1107 TARGET_ARCH=armv6 on the make command line for both the build
1108 and the install steps.
1111 Kernel modules compiled outside of a kernel build now default to
1112 installing to /boot/modules instead of /boot/kernel. Many kernel
1113 modules built this way (such as those in ports) already overrode
1114 KMODDIR explicitly to install into /boot/modules. However,
1115 manually building and installing a module from /sys/modules will
1116 now install to /boot/modules instead of /boot/kernel.
1119 The CAM I/O scheduler has been committed to the kernel. There should be
1120 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1121 list of known rogues that claim support for this but actually corrupt
1122 data is believed to be complete, be on the lookout for data
1123 corruption. The known rogue list is believed to be complete:
1125 o Crucial MX100, M550 drives with MU01 firmware.
1126 o Micron M510 and M550 drives with MU01 firmware.
1127 o Micron M500 prior to MU07 firmware
1128 o Samsung 830, 840, and 850 all firmwares
1129 o FCCT M500 all firmwares
1131 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1132 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1133 updated firmware. Black listed drives will work correctly because these
1134 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1135 this list is the same as found in Linux, it's believed there are no
1136 other rogues in the market place. All other models from the above
1139 To be safe, if you are at all concerned, you can quirk each of your
1140 drives to prevent NCQ from being sent by setting:
1141 kern.cam.ada.X.quirks="0x2"
1142 in loader.conf. If the drive requires the 4k sector quirk, set the
1143 quirks entry to 0x3.
1146 The FAST_DEPEND build option has been removed and its functionality is
1147 now the one true way. The old mkdep(1) style of 'make depend' has
1148 been removed. See 20160311 for further details.
1151 Resource range types have grown from unsigned long to uintmax_t. All
1152 drivers, and anything using libdevinfo, need to be recompiled.
1155 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1156 builds. It no longer runs mkdep(1) during 'make depend', and the
1157 'make depend' stage can safely be skipped now as it is auto ran
1158 when building 'make all' and will generate all SRCS and DPSRCS before
1159 building anything else. Dependencies are gathered at compile time with
1160 -MF flags kept in separate .depend files per object file. Users should
1161 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1162 stale .depend files.
1165 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1166 kernel modules. Therefore, if you load any kernel modules at boot time,
1167 please install the boot loaders after you install the kernel, but before
1171 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1172 make installkernel KERNCONF=YOUR_KERNEL_HERE
1173 make -C sys/boot install
1174 <reboot in single user>
1176 Then follow the usual steps, described in the General Notes section,
1180 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1181 see the 20141231 entry below for information about prerequisites and
1182 upgrading, if you are not already using clang 3.5.0 or higher.
1185 The AIO subsystem is now a standard part of the kernel. The
1186 VFS_AIO kernel option and aio.ko kernel module have been removed.
1187 Due to stability concerns, asynchronous I/O requests are only
1188 permitted on sockets and raw disks by default. To enable
1189 asynchronous I/O requests on all file types, set the
1190 vfs.aio.enable_unsafe sysctl to a non-zero value.
1193 The ELF object manipulation tool objcopy is now provided by the
1194 ELF Tool Chain project rather than by GNU binutils. It should be a
1195 drop-in replacement, with the addition of arm64 support. The
1196 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1197 to obtain the GNU version if necessary.
1200 Building ZFS pools on top of zvols is prohibited by default. That
1201 feature has never worked safely; it's always been prone to deadlocks.
1202 Using a zvol as the backing store for a VM guest's virtual disk will
1203 still work, even if the guest is using ZFS. Legacy behavior can be
1204 restored by setting vfs.zfs.vol.recursive=1.
1207 The NONE and HPN patches has been removed from OpenSSH. They are
1208 still available in the security/openssh-portable port.
1211 With the addition of ypldap(8), a new _ypldap user is now required
1212 during installworld. "mergemaster -p" can be used to add the user
1213 prior to installworld, as documented in the handbook.
1216 The tftp loader (pxeboot) now uses the option root-path directive. As a
1217 consequence it no longer looks for a pxeboot.4th file on the tftp
1218 server. Instead it uses the regular /boot infrastructure as with the
1222 The code to start recording plug and play data into the modules has
1223 been committed. While the old tools will properly build a new kernel,
1224 a number of warnings about "unknown metadata record 4" will be produced
1225 for an older kldxref. To avoid such warnings, make sure to rebuild
1226 the kernel toolchain (or world). Make sure that you have r292078 or
1227 later when trying to build 292077 or later before rebuilding.
1230 Debug data files are now built by default with 'make buildworld' and
1231 installed with 'make installworld'. This facilitates debugging but
1232 requires more disk space both during the build and for the installed
1233 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1237 r291527 changed the internal interface between the nfsd.ko and
1238 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1239 __FreeBSD_version has been bumped because of this.
1242 Add support for unicode collation strings leads to a change of
1243 order of files listed by ls(1) for example. To get back to the old
1244 behaviour, set LC_COLLATE environment variable to "C".
1246 Databases administrators will need to reindex their databases given
1247 collation results will be different.
1249 Due to a bug in install(1) it is recommended to remove the ancient
1250 locales before running make installworld.
1252 rm -rf /usr/share/locale/*
1255 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1256 libcrypto.so.7 or libssl.so.7 must be recompiled.
1259 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1260 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1261 should be replaced with isp_2400 and isp_2500 modules respectively.
1264 The build previously allowed using 'make -n' to not recurse into
1265 sub-directories while showing what commands would be executed, and
1266 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1267 and 'make -N' will not.
1270 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1271 and etcupdate will now use this file. A custom sendmail.cf is now
1272 updated via this mechanism rather than via installworld. If you had
1273 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1274 want to remove the exclusion or change it to "always install".
1275 /etc/mail/sendmail.cf is now managed the same way regardless of
1276 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1277 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1280 Compatibility shims for legacy ATA device names have been removed.
1281 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1282 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1283 environment variables, /dev/ad* and /dev/ar* symbolic links.
1286 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1287 Please see the 20141231 entry below for information about prerequisites
1288 and upgrading, if you are not already using clang 3.5.0 or higher.
1291 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1292 and renamed from .symbols to .debug. This reduces the size requirements
1293 on the boot partition or file system and provides consistency with
1294 userland debug files.
1296 When using the supported kernel installation method the
1297 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1298 as is done with /boot/kernel.
1300 Developers wishing to maintain the historical behavior of installing
1301 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1304 The wireless drivers had undergone changes that remove the 'parent
1305 interface' from the ifconfig -l output. The rc.d network scripts
1306 used to check presence of a parent interface in the list, so old
1307 scripts would fail to start wireless networking. Thus, etcupdate(3)
1308 or mergemaster(8) run is required after kernel update, to update your
1309 rc.d scripts in /etc.
1312 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1313 These configurations are now automatically interpreted as
1314 'scrub fragment reassemble'.
1317 Kernel-loadable modules for the random(4) device are back. To use
1318 them, the kernel must have
1321 options RANDOM_LOADABLE
1323 kldload(8) can then be used to load random_fortuna.ko
1324 or random_yarrow.ko. Please note that due to the indirect
1325 function calls that the loadable modules need to provide,
1326 the build-in variants will be slightly more efficient.
1328 The random(4) kernel option RANDOM_DUMMY has been retired due to
1329 unpopularity. It was not all that useful anyway.
1332 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1333 Control over building the ELF Tool Chain tools is now provided by
1334 the WITHOUT_TOOLCHAIN knob.
1337 The polarity of Pulse Per Second (PPS) capture events with the
1338 uart(4) driver has been corrected. Prior to this change the PPS
1339 "assert" event corresponded to the trailing edge of a positive PPS
1340 pulse and the "clear" event was the leading edge of the next pulse.
1342 As the width of a PPS pulse in a typical GPS receiver is on the
1343 order of 1 millisecond, most users will not notice any significant
1344 difference with this change.
1346 Anyone who has compensated for the historical polarity reversal by
1347 configuring a negative offset equal to the pulse width will need to
1348 remove that workaround.
1351 The default group assigned to /dev/dri entries has been changed
1352 from 'wheel' to 'video' with the id of '44'. If you want to have
1353 access to the dri devices please add yourself to the video group
1356 # pw groupmod video -m $USER
1359 The menu.rc and loader.rc files will now be replaced during
1360 upgrades. Please migrate local changes to menu.rc.local and
1361 loader.rc.local instead.
1364 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1365 strings and strip have been removed. The src.conf(5) knob
1366 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1369 As ZFS requires more kernel stack pages than is the default on some
1370 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1371 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1373 Please consider using 'options KSTACK_PAGES=X' where X is greater
1374 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1377 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1378 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1379 default, i.e., they will not contain "::". For example, instead
1380 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1381 to have a more specific match, such as different map entries for
1382 IPv6:0:0 vs IPv6:0. This change requires that configuration
1383 data (including maps, files, classes, custom ruleset, etc.) must
1384 use the same format, so make certain such configuration data is
1385 upgrading. As a very simple check search for patterns like
1386 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1387 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1388 the cf option UseCompressedIPv6Addresses.
1391 The default kernel entropy-processing algorithm is now
1392 Fortuna, replacing Yarrow.
1394 Assuming you have 'device random' in your kernel config
1395 file, the configurations allow a kernel option to override
1396 this default. You may choose *ONE* of:
1398 options RANDOM_YARROW # Legacy /dev/random algorithm.
1399 options RANDOM_DUMMY # Blocking-only driver.
1401 If you have neither, you get Fortuna. For most people,
1402 read no further, Fortuna will give a /dev/random that works
1403 like it always used to, and the difference will be irrelevant.
1405 If you remove 'device random', you get *NO* kernel-processed
1406 entropy at all. This may be acceptable to folks building
1407 embedded systems, but has complications. Carry on reading,
1408 and it is assumed you know what you need.
1410 *PLEASE* read random(4) and random(9) if you are in the
1411 habit of tweaking kernel configs, and/or if you are a member
1412 of the embedded community, wanting specific and not-usual
1413 behaviour from your security subsystems.
1415 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1416 random', you will NOT have a functioning /dev/random, and
1417 many cryptographic features will not work, including SSH.
1418 You may also find strange behaviour from the random(3) set
1419 of library functions, in particular sranddev(3), srandomdev(3)
1420 and arc4random(3). The reason for this is that the KERN_ARND
1421 sysctl only returns entropy if it thinks it has some to
1422 share, and with RANDOM_DUMMY or no 'device random' this
1426 An additional fix for the issue described in the 20150614 sendmail
1427 entry below has been committed in revision 284717.
1430 FreeBSD's old make (fmake) has been removed from the system. It is
1431 available as the devel/fmake port or via pkg install fmake.
1434 The fix for the issue described in the 20150614 sendmail entry
1435 below has been committed in revision 284436. The work
1436 around described in that entry is no longer needed unless the
1437 default setting is overridden by a confDH_PARAMETERS configuration
1438 setting of '5' or pointing to a 512 bit DH parameter file.
1441 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1442 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1443 and devel/kyua to version 0.20+ and adjust any calling code to work
1444 with Kyuafile and kyua.
1447 The import of openssl to address the FreeBSD-SA-15:10.openssl
1448 security advisory includes a change which rejects handshakes
1449 with DH parameters below 768 bits. sendmail releases prior
1450 to 8.15.2 (not yet released), defaulted to a 512 bit
1451 DH parameter setting for client connections. To work around
1452 this interoperability, sendmail can be configured to use a
1453 2048 bit DH parameter by:
1455 1. Edit /etc/mail/`hostname`.mc
1456 2. If a setting for confDH_PARAMETERS does not exist or
1457 exists and is set to a string beginning with '5',
1458 replace it with '2'.
1459 3. If a setting for confDH_PARAMETERS exists and is set to
1460 a file path, create a new file with:
1461 openssl dhparam -out /path/to/file 2048
1462 4. Rebuild the .cf file:
1463 cd /etc/mail/; make; make install
1464 5. Restart sendmail:
1465 cd /etc/mail/; make restart
1467 A sendmail patch is coming, at which time this file will be
1471 Generation of legacy formatted entries have been disabled by default
1472 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1473 entries were converted to use the new format by default when the new,
1474 machine independent format have been added and supported since FreeBSD
1477 Please see the pwd_mkdb(8) manual page for further details.
1480 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1481 20141231 entry below for information about prerequisites and upgrading,
1482 if you are not already using 3.5.0 or higher.
1485 TI platform code switched to using vendor DTS files and this update
1486 may break existing systems running on Beaglebone, Beaglebone Black,
1489 - dtb files should be regenerated/reinstalled. Filenames are the
1490 same but content is different now
1491 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1492 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1493 addressing scheme is now pin 25 on /dev/gpioc3.
1494 - Pandaboard: /etc/ttys should be updated, serial console device is
1495 now /dev/ttyu2, not /dev/ttyu0
1498 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1499 If you need the GNU extension from groff soelim(1), install groff
1500 from package: pkg install groff, or via ports: textproc/groff.
1503 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1504 defined in symlink(7); previously symlinks were silently ignored.
1507 The const qualifier has been removed from iconv(3) to comply with
1508 POSIX. The ports tree is aware of this from r384038 onwards.
1511 Libraries specified by LIBADD in Makefiles must have a corresponding
1512 DPADD_<lib> variable to ensure correct dependencies. This is now
1513 enforced in src.libnames.mk.
1516 From legacy ata(4) driver was removed support for SATA controllers
1517 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1518 Kernel modules ataahci and ataadaptec were removed completely,
1519 replaced by ahci and mvs modules respectively.
1522 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1523 the 20141231 entry below for information about prerequisites and
1524 upgrading, if you are not already using 3.5.0 or higher.
1527 The 32-bit PowerPC kernel has been changed to a position-independent
1528 executable. This can only be booted with a version of loader(8)
1529 newer than January 31, 2015, so make sure to update both world and
1530 kernel before rebooting.
1533 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1534 but before r278950, the RNG was not seeded properly. Immediately
1535 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1536 ssh keys or openssl keys) that were generated w/ a kernel from that
1537 range. This does not affect programs that directly used /dev/random
1538 or /dev/urandom. All userland uses of arc4random(3) are affected.
1541 The autofs(4) ABI was changed in order to restore binary compatibility
1542 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1543 with the new kernel.
1546 The powerpc64 kernel has been changed to a position-independent
1547 executable. This can only be booted with a new version of loader(8),
1548 so make sure to update both world and kernel before rebooting.
1551 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1552 only release, no new features have been added. Please see the 20141231
1553 entry below for information about prerequisites and upgrading, if you
1554 are not already using 3.5.0.
1557 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1558 taken from the ELF Tool Chain project rather than GNU binutils. They
1559 should be drop-in replacements, with the addition of arm64 support.
1560 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1561 binutils tools, if necessary. See 20150805 for updated information.
1564 The default Unbound configuration now enables remote control
1565 using a local socket. Users who have already enabled the
1566 local_unbound service should regenerate their configuration
1567 by running "service local_unbound setup" as root.
1570 The GNU texinfo and GNU info pages have been removed.
1571 To be able to view GNU info pages please install texinfo from ports.
1574 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1576 As of this release, a prerequisite for building clang, llvm and lldb is
1577 a C++11 capable compiler and C++11 standard library. This means that to
1578 be able to successfully build the cross-tools stage of buildworld, with
1579 clang as the bootstrap compiler, your system compiler or cross compiler
1580 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1581 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1584 On any standard FreeBSD 10.x or 11.x installation, where clang and
1585 libc++ are on by default (that is, on x86 or arm), this should work out
1588 On 9.x installations where clang is enabled by default, e.g. on x86 and
1589 powerpc, libc++ will not be enabled by default, so libc++ should be
1590 built (with clang) and installed first. If both clang and libc++ are
1591 missing, build clang first, then use it to build libc++.
1593 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1594 the instructions for 9.x above.
1596 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1597 default, and do not build clang.
1599 Many embedded systems are resource constrained, and will not be able to
1600 build clang in a reasonable time, or in some cases at all. In those
1601 cases, cross building bootable systems on amd64 is a workaround.
1603 This new version of clang introduces a number of new warnings, of which
1604 the following are most likely to appear:
1608 This warns in two cases, for both C and C++:
1609 * When the code is trying to take the absolute value of an unsigned
1610 quantity, which is effectively a no-op, and almost never what was
1611 intended. The code should be fixed, if at all possible. If you are
1612 sure that the unsigned quantity can be safely cast to signed, without
1613 loss of information or undefined behavior, you can add an explicit
1614 cast, or disable the warning.
1616 * When the code is trying to take an absolute value, but the called
1617 abs() variant is for the wrong type, which can lead to truncation.
1618 If you want to disable the warning instead of fixing the code, please
1619 make sure that truncation will not occur, or it might lead to unwanted
1622 -Wtautological-undefined-compare and
1623 -Wundefined-bool-conversion
1625 These warn when C++ code is trying to compare 'this' against NULL, while
1626 'this' should never be NULL in well-defined C++ code. However, there is
1627 some legacy (pre C++11) code out there, which actively abuses this
1628 feature, which was less strictly defined in previous C++ versions.
1630 Squid and openjdk do this, for example. The warning can be turned off
1631 for C++98 and earlier, but compiling the code in C++11 mode might result
1632 in unexpected behavior; for example, the parts of the program that are
1633 unreachable could be optimized away.
1636 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1637 kernel sources have been removed. The .h files remain, since some
1638 utilities include them. This will need to be fixed later.
1639 If "mount -t oldnfs ..." is attempted, it will fail.
1640 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1641 the utilities will report errors.
1644 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1645 directories to top level SUBDIR variable when their parent
1646 directory is included in LOCAL_DIRS. Users with build systems with
1647 such hierarchies and without SUBDIR entries in the parent
1648 directory Makefiles should add them or add the directories to
1652 faith(4) and faithd(8) have been removed from the base system. Faith
1653 has been obsolete for a very long time.
1656 vt(4), the new console driver, is enabled by default. It brings
1657 support for Unicode and double-width characters, as well as
1658 support for UEFI and integration with the KMS kernel video
1661 You may need to update your console settings in /etc/rc.conf,
1662 most probably the keymap. During boot, /etc/rc.d/syscons will
1663 indicate what you need to do.
1665 vt(4) still has issues and lacks some features compared to
1666 syscons(4). See the wiki for up-to-date information:
1667 https://wiki.freebsd.org/Newcons
1669 If you want to keep using syscons(4), you can do so by adding
1670 the following line to /boot/loader.conf:
1674 pjdfstest has been integrated into kyua as an opt-in test suite.
1675 Please see share/doc/pjdfstest/README for more details on how to
1679 gperf has been removed from the base system for architectures
1680 that use clang. Ports that require gperf will obtain it from the
1684 pjdfstest has been moved from tools/regression/pjdfstest to
1688 At svn r271982, The default linux compat kernel ABI has been adjusted
1689 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1690 update. If you wish to continue using the linux-f10 compat ports,
1691 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1692 encouraged to update their linux-compat packages to linux-c6 during
1693 their next update cycle.
1696 The ofwfb driver, used to provide a graphics console on PowerPC when
1697 using vt(4), no longer allows mmap() of all physical memory. This
1698 will prevent Xorg on PowerPC with some ATI graphics cards from
1699 initializing properly unless x11-servers/xorg-server is updated to
1703 The xdev targets have been converted to using TARGET and
1704 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1707 The default unbound configuration has been modified to address
1708 issues with reverse lookups on networks that use private
1709 address ranges. If you use the local_unbound service, run
1710 "service local_unbound setup" as root to regenerate your
1711 configuration, then "service local_unbound reload" to load the
1715 The GNU texinfo and GNU info pages are not built and installed
1716 anymore, WITH_INFO knob has been added to allow to built and install
1718 UPDATE: see 20150102 entry on texinfo's removal
1721 The GNU readline library is now an INTERNALLIB - that is, it is
1722 statically linked into consumers (GDB and variants) in the base
1723 system, and the shared library is no longer installed. The
1724 devel/readline port is available for third party software that
1728 The Itanium architecture (ia64) has been removed from the list of
1729 known architectures. This is the first step in the removal of the
1733 Commit r268115 has added NFSv4.1 server support, merged from
1734 projects/nfsv4.1-server. Since this includes changes to the
1735 internal interfaces between the NFS related modules, a full
1736 build of the kernel and modules will be necessary.
1737 __FreeBSD_version has been bumped.
1740 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1741 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1742 which differs from the behaviour controlled by this knob.)
1745 Maximal length of the serial number in CTL was increased from 16 to
1746 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1747 and ctld, need to be rebuilt to work with a new kernel.
1750 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1751 1 respectively to match the upstream numbers. They were out of
1752 sync because, when they were originally added to FreeBSD, the
1753 upstream versions were not respected. These libraries are private
1754 and not yet built by default, so renumbering them should be a
1755 non-issue. However, unclean source trees will yield broken test
1756 programs once the operator executes "make delete-old-libs" after a
1757 "make installworld".
1759 Additionally, the atf-sh binary was made private by moving it into
1760 /usr/libexec/. Already-built shell test programs will keep the
1761 path to the old binary so they will break after "make delete-old"
1764 If you are using WITH_TESTS=yes (not the default), wipe the object
1765 tree and rebuild from scratch to prevent spurious test failures.
1766 This is only needed once: the misnumbered libraries and misplaced
1767 binaries have been added to OptionalObsoleteFiles.inc so they will
1768 be removed during a clean upgrade.
1771 Clang and llvm have been upgraded to 3.4.1 release.
1774 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1775 be removed to avoid issues in the future (and has been added to
1779 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1780 past, it affected all builds that used the bsd.*.mk files. The old
1781 behavior was a bug, but people may have relied upon it. To get this
1782 behavior back, you can .include /etc/src.conf from /etc/make.conf
1783 (which is still global and isn't changed). This also changes the
1784 behavior of incremental builds inside the tree of individual
1785 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1786 Although this has survived make universe and some upgrade scenarios,
1787 other upgrade scenarios may have broken. At least one form of
1788 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1789 as well... In cases where MAKESYSPATH isn't working with this
1790 setting, you'll need to set it to the full path to your tree.
1792 One side effect of all this cleaning up is that bsd.compiler.mk
1793 is no longer implicitly included by bsd.own.mk. If you wish to
1794 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1798 The lindev device has been removed since /dev/full has been made a
1799 standard device. __FreeBSD_version has been bumped.
1802 The knob WITHOUT_VI was added to the base system, which controls
1803 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1804 in order to reorder files share/termcap and didn't build ex(1) as a
1805 build tool, so building/installing with WITH_VI is highly advised for
1806 build hosts for older releases.
1808 This issue has been fixed in stable/9 and stable/10 in r277022 and
1809 r276991, respectively.
1812 The YES_HESIOD knob has been removed. It has been obsolete for
1813 a decade. Please move to using WITH_HESIOD instead or your builds
1814 will silently lack HESIOD.
1817 The uart(4) driver has been changed with respect to its handling
1818 of the low-level console. Previously the uart(4) driver prevented
1819 any process from changing the baudrate or the CLOCAL and HUPCL
1820 control flags. By removing the restrictions, operators can make
1821 changes to the serial console port without having to reboot.
1822 However, when getty(8) is started on the serial device that is
1823 associated with the low-level console, a misconfigured terminal
1824 line in /etc/ttys will now have a real impact.
1825 Before upgrading the kernel, make sure that /etc/ttys has the
1826 serial console device configured as 3wire without baudrate to
1827 preserve the previous behaviour. E.g:
1828 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1831 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1832 to improve performance. To re-enable it, if needed, run rpcbind
1833 with command line option -W.
1836 Switched back to the GPL dtc compiler due to updates in the upstream
1837 dts files not being supported by the BSDL dtc compiler. You will need
1838 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1839 may result while building dtb files during a kernel build if you fail
1840 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1843 Clang and llvm have been upgraded to 3.4 release.
1846 The nve(4) driver has been removed. Please use the nfe(4) driver
1847 for NVIDIA nForce MCP Ethernet adapters instead.
1850 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1851 This could cause certain C++ applications using shared libraries built
1852 against the previous version of libc++ to crash. The incompatibility
1853 has now been fixed, but any C++ applications or shared libraries built
1854 between r261283 and r261801 should be recompiled.
1857 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1858 capability mode support. Please note that enabling the feature in
1859 kernel is still highly recommended.
1862 OpenSSH is now built with sandbox support, and will use sandbox as
1863 the default privilege separation method. This requires Capsicum
1864 capability mode support in kernel.
1867 The libelf and libdwarf libraries have been updated to newer
1868 versions from upstream. Shared library version numbers for
1869 these two libraries were bumped. Any ports or binaries
1870 requiring these two libraries should be recompiled.
1871 __FreeBSD_version is bumped to 1100006.
1874 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1875 instead of providing an explicit one, this would prevent such
1876 Makefile from providing its own Kyuafile in the future during
1877 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1878 intervention is needed to clean an objdir if you use NO_CLEAN:
1879 # find /usr/obj -name Kyuafile | xargs rm -f
1882 The behavior of gss_pseudo_random() for the krb5 mechanism
1883 has changed, for applications requesting a longer random string
1884 than produced by the underlying enctype's pseudo-random() function.
1885 In particular, the random string produced from a session key of
1886 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1887 be different at the 17th octet and later, after this change.
1888 The counter used in the PRF+ construction is now encoded as a
1889 big-endian integer in accordance with RFC 4402.
1890 __FreeBSD_version is bumped to 1100004.
1893 The WITHOUT_ATF build knob has been removed and its functionality
1894 has been subsumed into the more generic WITHOUT_TESTS. If you were
1895 using the former to disable the build of the ATF libraries, you
1896 should change your settings to use the latter.
1899 The default version of mtree is nmtree which is obtained from
1900 NetBSD. The output is generally the same, but may vary
1901 slightly. If you found you need identical output adding
1902 "-F freebsd9" to the command line should do the trick. For the
1903 time being, the old mtree is available as fmtree.
1906 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1907 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1908 1.1.4_8 and verify bsdyml not linked in, before running "make
1910 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1912 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1915 The stable/10 branch has been created in subversion from head
1922 Avoid using make -j when upgrading. While generally safe, there are
1923 sometimes problems using -j to upgrade. If your upgrade fails with
1924 -j, please try again without -j. From time to time in the past there
1925 have been problems using -j with buildworld and/or installworld. This
1926 is especially true when upgrading between "distant" versions (eg one
1927 that cross a major release boundary or several minor releases, or when
1928 several months have passed on the -current branch).
1930 Sometimes, obscure build problems are the result of environment
1931 poisoning. This can happen because the make utility reads its
1932 environment when searching for values for global variables. To run
1933 your build attempts in an "environmental clean room", prefix all make
1934 commands with 'env -i '. See the env(1) manual page for more details.
1936 When upgrading from one major version to another it is generally best to
1937 upgrade to the latest code in the currently installed branch first, then
1938 do an upgrade to the new branch. This is the best-tested upgrade path,
1939 and has the highest probability of being successful. Please try this
1940 approach if you encounter problems with a major version upgrade. Since
1941 the stable 4.x branch point, one has generally been able to upgrade from
1942 anywhere in the most recent stable branch to head / current (or even the
1943 last couple of stable branches). See the top of this file when there's
1946 When upgrading a live system, having a root shell around before
1947 installing anything can help undo problems. Not having a root shell
1948 around can lead to problems if pam has changed too much from your
1949 starting point to allow continued authentication after the upgrade.
1951 This file should be read as a log of events. When a later event changes
1952 information of a prior event, the prior event should not be deleted.
1953 Instead, a pointer to the entry with the new information should be
1954 placed in the old entry. Readers of this file should also sanity check
1955 older entries before relying on them blindly. Authors of new entries
1956 should write them with this in mind.
1960 When upgrading the boot ZFS pool to a new version, always follow
1963 1.) recompile and reinstall the ZFS boot loader and boot block
1964 (this is part of "make buildworld" and "make installworld")
1966 2.) update the ZFS boot block on your boot drive
1968 The following example updates the ZFS boot block on the first
1969 partition (freebsd-boot) of a GPT partitioned drive ada0:
1970 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1972 Non-boot pools do not need these updates.
1976 If you are updating from a prior version of FreeBSD (even one just
1977 a few days old), you should follow this procedure. It is the most
1978 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1980 make kernel-toolchain
1981 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1982 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1984 To test a kernel once
1985 ---------------------
1986 If you just want to boot a kernel once (because you are not sure
1987 if it works, or if you want to boot a known bad kernel to provide
1988 debugging information) run
1989 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1990 nextboot -k testkernel
1992 To rebuild everything and install it on the current system.
1993 -----------------------------------------------------------
1994 # Note: sometimes if you are running current you gotta do more than
1995 # is listed here if you are upgrading from a really old current.
1997 <make sure you have good level 0 dumps>
1999 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2000 make installkernel KERNCONF=YOUR_KERNEL_HERE
2002 <reboot in single user> [3]
2009 To cross-install current onto a separate partition
2010 --------------------------------------------------
2011 # In this approach we use a separate partition to hold
2012 # current's root, 'usr', and 'var' directories. A partition
2013 # holding "/", "/usr" and "/var" should be about 2GB in
2016 <make sure you have good level 0 dumps>
2019 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2020 <maybe newfs current's root partition>
2021 <mount current's root partition on directory ${CURRENT_ROOT}>
2022 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2023 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2024 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2025 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2026 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2027 <reboot into current>
2028 <do a "native" rebuild/install as described in the previous section>
2029 <maybe install compatibility libraries from ports/misc/compat*>
2033 To upgrade in-place from stable to current
2034 ----------------------------------------------
2035 <make sure you have good level 0 dumps>
2037 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2038 make installkernel KERNCONF=YOUR_KERNEL_HERE
2040 <reboot in single user> [3]
2047 Make sure that you've read the UPDATING file to understand the
2048 tweaks to various things you need. At this point in the life
2049 cycle of current, things change often and you are on your own
2050 to cope. The defaults can also change, so please read ALL of
2051 the UPDATING entries.
2053 Also, if you are tracking -current, you must be subscribed to
2054 freebsd-current@freebsd.org. Make sure that before you update
2055 your sources that you have read and understood all the recent
2056 messages there. If in doubt, please track -stable which has
2057 much fewer pitfalls.
2059 [1] If you have third party modules, such as vmware, you
2060 should disable them at this point so they don't crash your
2063 [3] From the bootblocks, boot -s, and then do
2067 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2068 cd src # full path to source
2069 adjkerntz -i # if CMOS is wall time
2070 Also, when doing a major release upgrade, it is required that
2071 you boot into single user mode to do the installworld.
2073 [4] Note: This step is non-optional. Failure to do this step
2074 can result in a significant reduction in the functionality of the
2075 system. Attempting to do it by hand is not recommended and those
2076 that pursue this avenue should read this file carefully, as well
2077 as the archives of freebsd-current and freebsd-hackers mailing lists
2078 for potential gotchas. The -U option is also useful to consider.
2079 See mergemaster(8) for more information.
2081 [5] Usually this step is a no-op. However, from time to time
2082 you may need to do this if you get unknown user in the following
2083 step. It never hurts to do it all the time. You may need to
2084 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2085 install) after the buildworld before this step if you last updated
2086 from current before 20130425 or from -stable before 20130430.
2088 [6] This only deletes old files and directories. Old libraries
2089 can be deleted by "make delete-old-libs", but you have to make
2090 sure that no program is using those libraries anymore.
2092 [8] The new kernel must be able to run existing binaries used by an
2093 installworld. When upgrading across major versions, the new kernel's
2094 configuration must include the correct COMPAT_FREEBSD<n> option for
2095 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2096 to do so may leave you with a system that is hard to boot to recover. A
2097 GENERIC kernel will include suitable compatibility options to run
2098 binaries from older branches. Note that the ability to run binaries
2099 from unsupported branches is not guaranteed.
2101 Make sure that you merge any new devices from GENERIC since the
2102 last time you updated your kernel config file. Options also
2103 change over time, so you may need to adjust your custom kernels
2106 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2107 "?=" instead of the "=" assignment operator, so that buildworld can
2108 override the CPUTYPE if it needs to.
2110 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2111 not on the command line, or in /etc/make.conf. buildworld will
2112 warn if it is improperly defined.
2115 This file contains a list, in reverse chronological order, of major
2116 breakages in tracking -current. It is not guaranteed to be a complete
2117 list of such breakages, and only contains entries since September 23, 2011.
2118 If you need to see UPDATING entries from before that date, you will need
2119 to fetch an UPDATING file from an older FreeBSD release.
2121 Copyright information:
2123 Copyright 1998-2009 M. Warner Losh.
2125 Redistribution, publication, translation and use, with or without
2126 modification, in full or in part, in any form or format of this
2127 document are permitted without further permission from the author.
2129 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2130 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2131 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2132 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2133 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2134 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2135 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2136 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2137 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2138 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2139 POSSIBILITY OF SUCH DAMAGE.
2141 Contact Warner Losh if you have any questions about your use of