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 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
36 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
37 your Makefiles and scripts to define MK_<var>=no instead as required.
39 One exception to this is that program or library Makefiles should
40 define MAN to empty rather than setting MK_MAN=no.
43 The nctgpio and wbwd drivers have been moved to the superio bus.
44 If you have one of these drivers in a kernel configuration, then
45 you should add device superio to it. If you use one of these drivers
46 as a module and you compile a custom set of modules, then you should
47 add superio to the set.
50 KPIs for network drivers to access interface addresses have changed.
51 Users need to recompile NIC driver modules together with kernel.
54 The net.link.tap.user_open sysctl no longer prevents user opening of
55 already created /dev/tapNN devices. Access is still controlled by
56 node permissions, just like tun devices. The net.link.tap.user_open
57 sysctl is now used only to allow users to perform devfs cloning of
58 tap devices, and the subsequent open may not succeed if the user is not
59 in the appropriate group. This sysctl may be deprecated/removed
60 completely in the future.
63 mips, powerpc, and sparc64 are no longer built as part of
64 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
65 not defined, mips, powerpc, and sparc64 builds will look for
66 the xtoolchain binaries and if installed use them for universe
67 builds. As llvm 9.0 becomes vetted for these architectures, they
68 will be removed from the list.
71 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
72 been upgraded to 9.0.0. Please see the 20141231 entry below for
73 information about prerequisites and upgrading, if you are not already
74 using clang 3.5.0 or higher.
77 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
78 GENERIC. They are available as modules and can be loaded by adding
79 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
80 hptnr_load="YES", or hptrr_load="YES", respectively.
83 ntpd no longer by default locks its pages in memory, allowing them
84 to be paged out by the kernel. Use rlimit memlock to restore
85 historic BSD behaviour. For example, add "rlimit memlock 32"
86 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
89 Several of ping6's options have been renamed for better consistency
90 with ping. If you use any of -ARWXaghmrtwx, you must update your
91 scripts. See ping6(8) for details.
94 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
95 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
96 been removed from mount_fusefs(8). You can safely remove them from
97 your scripts, because they had no effect.
99 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
100 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
101 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
102 sysctls have been removed. If you felt the need to set any of them to
103 a non-default value, please tell asomers@FreeBSD.org why.
106 Default permissions on the /var/account/acct file (and copies of it
107 rotated by periodic daily scripts) are changed from 0644 to 0640
108 because the file contains sensitive information that should not be
109 world-readable. If the /var/account directory must be created by
110 rc.d/accounting, the mode used is now 0750. Admins who use the
111 accounting feature are encouraged to change the mode of an existing
112 /var/account directory to 0750 or 0700.
115 Entropy collection and the /dev/random device are no longer optional
116 components. The "device random" option has been removed.
117 Implementations of distilling algorithms can still be made loadable
118 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
121 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
122 been upgraded to 8.0.1. Please see the 20141231 entry below for
123 information about prerequisites and upgrading, if you are not already
124 using clang 3.5.0 or higher.
127 A fix was applied to i386 kernel modules to avoid panics with
128 dpcpu or vnet. Users need to recompile i386 kernel modules
129 having pcpu or vnet sections or they will refuse to load.
132 User-wired pages now have their own counter,
133 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
134 to vm.max_user_wired and changed from an unsigned int to an unsigned
135 long. bhyve VMs wired with the -S are now subject to the user
136 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
137 avoid running into the limit.
140 The IPSEC option has been removed from GENERIC. Users requiring
141 ipsec(4) must now load the ipsec(4) kernel module.
144 The tap(4) driver has been folded into tun(4), and the module has been
145 renamed to tuntap. You should update any kld_list="if_tap" or
146 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
147 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
148 module instead, and "device tap" or "device tun" entries in kernel
149 config files to select the tuntap device instead.
152 The following knobs have been added related to tradeoffs between
153 safe use of the random device and availability in the absence of
156 kern.random.initial_seeding.bypass_before_seeding: tunable; set
157 non-zero to bypass the random device prior to seeding, or zero to
158 block random requests until the random device is initially seeded.
159 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
160 availability properties.
162 kern.random.initial_seeding.read_random_bypassed_before_seeding:
163 read-only diagnostic sysctl that is set when bypass is enabled and
164 read_random(9) is bypassed, to enable programmatic handling of this
165 initial condition, if desired.
167 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
168 Similar to the above, but for for arc4random(9) initial seeding.
170 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
171 non-zero to disable warnings in dmesg when the same conditions are
172 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
173 produce warnings in dmesg when the conditions are met.
176 The loadable random module KPI has changed; the random_infra_init()
177 routine now requires a 3rd function pointer for a bool (*)(void)
178 method that returns true if the random device is seeded (and
179 therefore unblocked).
182 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
183 built from head sources between r320757 (July 6, 2017) and
184 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
185 is added to the command line.
186 nfsuserd daemons built from head sources that are post-r338192 are
187 not affected and should continue to work.
190 The fuse(4) module has been renamed to fusefs(4) for consistency with
191 other filesystems. You should update any kld_load="fuse" entries in
192 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
193 "options FUSE" entries in kernel config files.
196 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
197 8.0.0. Please see the 20141231 entry below for information about
198 prerequisites and upgrading, if you are not already using clang 3.5.0
202 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
203 compiled into your custom kernel, add 'device xz' statement to the
207 drm and drm2 have been removed from the tree. Please see
208 https://wiki.freebsd.org/Graphics for the latest information on
209 migrating to the drm ports.
212 Iflib is no longer unconditionally compiled into the kernel. Drivers
213 using iflib and statically compiled into the kernel, now require
214 the 'device iflib' config option. For the same drivers loaded as
215 modules on kernels not having 'device iflib', the iflib.ko module
216 is loaded automatically.
219 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
220 options no longer exist since r343219 and r343427 respectively;
221 nothing uses them, so they should be just removed from custom
225 r342635 changes the way efibootmgr(8) works by requiring users to add
226 the -b (bootnum) parameter for commands where the bootnum was previously
227 specified with each option. For example 'efibootmgr -B 0001' is now
228 'efibootmgr -B -b 0001'.
231 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
232 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
233 servers that have vfs.nfsd.nfs_privport set will only allow mounts
234 from clients using a reserved port#. Since both the FreeBSD and Linux
235 NFSv4 clients use reserved port#s by default, this should not affect
239 The XLP config has been removed. We can't support 64-bit atomics in this
240 kernel because it is running in 32-bit mode. XLP users must transition
241 to running a 64-bit kernel (XLP64 or XLPN32).
243 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
244 the preferred emulator today and we don't need two different ones.
246 The old sibyte / swarm / Broadcom BCM1250 support has been
247 removed from the mips port.
250 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
251 7.0.1. Please see the 20141231 entry below for information about
252 prerequisites and upgrading, if you are not already using clang 3.5.0
256 Remove the timed and netdate programs from the base tree. Setting
257 the time with these daemons has been obsolete for over a decade.
260 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
261 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
262 it produces broken binaries when ifuncs are in use. Users needing
263 GNU ld should install the binutils port or package.
266 The BSD crtbegin and crtend code has been enabled by default. It has
267 had extensive testing on amd64, arm64, and i386. It can be disabled
268 by building a world with -DWITHOUT_BSD_CRTBEGIN.
271 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
272 has been converted to a port (misc/ctm) and will be removed from
273 FreeBSD-13. It is available as a package (ctm) for all supported
277 The default newsyslog.conf(5) file has been changed to only include
278 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
279 the filenames end in '.conf' and do not begin with a '.'.
281 You should check the configuration files in these two directories match
282 this naming convention. You can verify which configuration files are
283 being included using the command:
287 Ports for the DRM modules have been simplified. Now, amd64 users should
288 just install the drm-kmod port. All others should install
291 Graphics hardware that's newer than about 2010 usually works with
292 drm-kmod. For hardware older than 2013, however, some users will need
293 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
294 than 2008 usually only works in drm-legacy-kmod. The graphics team can
295 only commit to hardware made since 2013 due to the complexity of the
296 market and difficulty to test all the older cards effectively. If you
297 have hardware supported by drm-kmod, you are strongly encouraged to use
298 that as you will get better support.
300 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
301 elsewhere, the drm and drm2 modules will be eliminated from the src base
302 soon (with a limited exception for arm). Please update to the package
303 asap and report any issues to x11@freebsd.org.
305 Generally, anybody using the drm*-kmod packages should add
306 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
307 cross-threading surprises, especially with automatic driver
308 loading from X11 startup. These will become the defaults in 13-current
312 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
313 custom kernel and module loading configuration files must be updated
314 accordingly. Moreover, interfaces previous presented as ixlvN to the
315 system are now exposed as iavfN and network configuration files must
316 be adjusted as necessary.
319 OpenSSL has been updated to version 1.1.1. This update included
320 additional various API changes throughout the base system. It is
321 important to rebuild third-party software after upgrading. The value
322 of __FreeBSD_version has been bumped accordingly.
325 The legacy DRM modules and drivers have now been added to the loader's
326 module blacklist, in favor of loading them with kld_list in rc.conf(5).
327 The module blacklist may be overridden with the loader.conf(5)
328 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
332 The cam(4) based nda(4) driver will be used over nvd(4) by default on
333 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
334 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
335 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
339 Reproducible build mode is now on by default, in preparation for
340 FreeBSD 12.0. This eliminates build metadata such as the user,
341 host, and time from the kernel (and uname), unless the working tree
342 corresponds to a modified checkout from a version control system.
343 The previous behavior can be obtained by setting the /etc/src.conf
344 knob WITHOUT_REPRODUCIBLE_BUILD.
347 The Yarrow CSPRNG has been removed from the kernel as it has not been
348 supported by its designers since at least 2003. Fortuna has been the
349 default since FreeBSD-11.
352 devctl freeze/thaw have gone into the tree, the rc scripts have been
353 updated to use them and devmatch has been changed. You should update
354 kernel, userland and rc scripts all at the same time.
357 The default interpreter has been switched from 4th to Lua.
358 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
359 interpreter. If you have custom FORTH code you will need to set
360 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
361 src.conf for the build. This will create default hard links between
362 loader and loader_4th instead of loader and loader_lua, the new default.
363 If you are using UEFI it will create the proper hard link to loader.efi.
365 bhyve uses userboot.so. It remains 4th-only until some issues are solved
366 regarding coexisting with multiple versions of FreeBSD are resolved.
369 ls(1) now respects the COLORTERM environment variable used in other
370 systems and software to indicate that a colored terminal is both
371 supported and desired. If ls(1) is suddenly emitting colors, they may
372 be disabled again by either removing the unwanted COLORTERM from your
373 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
374 may not be observed in a future release.
377 The default pager for most commands has been changed to "less". To
378 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
382 The jedec_ts(4) driver has been removed. A superset of its functionality
383 is available in the jedec_dimm(4) driver, and the manpage for that
384 driver includes migration instructions. If you have "device jedec_ts"
385 in your kernel configuration file, it must be removed.
388 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
389 This should have no effect if the kernel is booted via BIOS/legacy boot.
390 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
391 has a buggy firmware that prevents a successful boot due to use of
395 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
396 support has been removed from the tree. These ports were
397 obsolete and/or known to be broken for many years.
400 loader.efi has been augmented to participate more fully in the
401 UEFI boot manager protocol. loader.efi will now look at the
402 BootXXXX environment variable to determine if a specific kernel
403 or root partition was specified. XXXX is derived from BootCurrent.
404 efibootmgr(8) manages these standard UEFI variables.
407 zfsloader's functionality has now been folded into loader.
408 zfsloader is no longer necessary once you've updated your
409 boot blocks. For a transition period, we will install a
410 hardlink for zfsloader to loader to allow a smooth transition
411 until the boot blocks can be updated (hard link because old
412 zfs boot blocks don't understand symlinks).
415 ARM64 now have efifb support, if you want to have serial console
416 on your arm64 board when an screen is connected and the bootloader
417 setup a frame buffer for us to use, just add :
421 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
422 an screen connected as the firmware will setup a frame buffer are that
423 u-boot will expose as an EFI frame buffer.
426 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
427 or take steps to update /etc/passwd before doing installworld on
428 existing systems. Do not skip the "mergemaster -Fp" step before
429 installworld, as described in the update procedures near the bottom
430 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
431 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
432 the ntp config file contain options that change file/dir locations.
433 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
434 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
435 taking steps to ensure that all required files/dirs are accessible
439 Big endian arm support has been removed.
442 The static environment setup in kernel configs is no longer mutually
443 exclusive with the loader(8) environment by default. In order to
444 restore the previous default behavior of disabling the loader(8)
445 environment if a static environment is present, you must specify
446 loader_env.disabled=1 in the static environment.
449 The ABI of syscalls used by management tools like sockstat and
450 netstat has been broken to allow 32-bit binaries to work on
451 64-bit kernels without modification. These programs will need
452 to match the kernel in order to function. External programs may
453 require minor modifications to accommodate a change of type in
454 structures from pointers to 64-bit virtual addresses.
457 On i386 and amd64 atomics are now inlined. Out of tree modules using
458 atomics will need to be rebuilt.
461 The '%I' format in the kern.corefile sysctl limits the number of
462 core files that a process can generate to the number stored in the
463 debug.ncores sysctl. The '%I' format is replaced by the single digit
464 index. Previously, if all indexes were taken the kernel would overwrite
465 only a core file with the highest index in a filename.
466 Currently the system will create a new core file if there is a free
467 index or if all slots are taken it will overwrite the oldest one.
470 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
471 6.0.1. Please see the 20141231 entry below for information about
472 prerequisites and upgrading, if you are not already using clang 3.5.0
476 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
477 needed to be changed to work with it. This change was made with r335763
478 and requires a mergemaster / etcupdate / etc to update the installed
482 r334930 changed the interface between the NFS modules, so they all
483 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
486 As of r334391 lld is the default amd64 system linker; it is installed
487 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
491 The kernel / userland interface for devinfo changed, so you'll
492 need a new kernel and userland as a pair for it to work (rebuilding
493 lib/libdevinfo is all that's required). devinfo and devmatch will
494 not work, but everything else will when there's a mismatch.
497 The on-disk format for hwpmc callchain records has changed to include
498 threadid corresponding to a given record. This changes the field offsets
499 and thus requires that libpmcstat be rebuilt before using a kernel
503 The vxge(4) driver has been removed. This driver was introduced into
504 HEAD one week before the Exar left the Ethernet market and is not
505 known to be used. If you have device vxge in your kernel config file
509 The amd64 kernel now requires a ld that supports ifunc to produce a
510 working kernel, either lld or a newer binutils. lld is built by default
511 on amd64, and the 'buildkernel' target uses it automatically. However,
512 it is not the default linker, so building the kernel the traditional
513 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
514 binutils port/package). lld will soon be default, and this requirement
517 NOTE: As of r334391 lld is the default system linker on amd64, and no
518 workaround is necessary.
521 The nxge(4) driver has been removed. This driver was for PCI-X 10g
522 cards made by s2io/Neterion. The company was acquired by Exar and
523 no longer sells or supports Ethernet products. If you have device
524 nxge in your kernel config file it must be removed.
527 The tz database (tzdb) has been updated to 2018e. This version more
528 correctly models time stamps in time zones with negative DST such as
529 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
530 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
531 time zone abbreviations and the tm_isdst flag.
534 The ixgb(4) driver has been removed. This driver was for an early and
535 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
536 quickly shifted to the long lived ixgbe family. If you have device
537 ixgb in your kernel config file it must be removed.
540 The lmc(4) driver has been removed. This was a WAN interface
541 card that was already reportedly rare in 2003, and had an ambiguous
542 license. If you have device lmc in your kernel config file it must
546 Support for Arcnet networks has been removed. If you have device
547 arcnet or device cm in your kernel config file they must be
551 Support for FDDI networks has been removed. If you have device
552 fddi or device fpa in your kernel config file they must be
556 In addition to supporting RFC 3164 formatted messages, the
557 syslogd(8) service is now capable of parsing RFC 5424 formatted
558 log messages. The main benefit of using RFC 5424 is that clients
559 may now send log messages with timestamps containing year numbers,
560 microseconds and time zone offsets.
562 Similarly, the syslog(3) C library function has been altered to
563 send RFC 5424 formatted messages to the local system logging
564 daemon. On systems using syslogd(8), this change should have no
565 negative impact, as long as syslogd(8) and the C library are
566 updated at the same time. On systems using a different system
567 logging daemon, it may be necessary to make configuration
568 adjustments, depending on the software used.
570 When using syslog-ng, add the 'syslog-protocol' flag to local
571 input sources to enable parsing of RFC 5424 formatted messages:
574 unix-dgram("/var/run/log" flags(syslog-protocol));
577 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
578 of the 'imuxsock' module to let messages be processed by the
579 regular RFC 3164/5424 parsing pipeline:
581 module(load="imuxsock" SysSock.UseSpecialParser="off")
583 Do note that these changes only affect communication between local
584 applications and syslogd(8). The format that syslogd(8) uses to
585 store messages on disk or forward messages to other systems
586 remains unchanged. syslogd(8) still uses RFC 3164 for these
587 purposes. Options to customize this behaviour will be added in the
588 future. Utilities that process log files stored in /var/log are
589 thus expected to continue to function as before.
591 __FreeBSD_version has been incremented to 1200061 to denote this
595 Support for token ring networks has been removed. If you
596 have "device token" in your kernel config you should remove
597 it. No device drivers supported token ring.
600 makefs was modified to be able to tag ISO9660 El Torito boot catalog
601 entries as EFI instead of overloading the i386 tag as done previously.
602 The amd64 mkisoimages.sh script used to build amd64 ISO images for
603 release was updated to use this. This may mean that makefs must be
604 updated before "make cdrom" can be run in the release directory. This
605 should be as simple as:
607 $ cd $SRCDIR/usr.sbin/makefs
608 $ make depend all install
611 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
612 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
613 Co-existence for the transition period will come shortly. Booting is a
614 complex environment and test coverage for Lua-enabled loaders has been
615 thin, so it would be prudent to assume it might not work and make
616 provisions for backup boot methods.
619 devmatch functionality has been turned on in devd. It will automatically
620 load drivers for unattached devices. This may cause unexpected drivers
621 to be loaded. Please report any problems to current@ and
625 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
626 6.0.0. Please see the 20141231 entry below for information about
627 prerequisites and upgrading, if you are not already using clang 3.5.0
631 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
632 This means it is used to link the kernel and userland libraries and
633 executables, but is not yet installed as /usr/bin/ld by default.
635 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
636 WITHOUT_LLD_BOOTSTRAP=yes
639 On i386, pmtimer has been removed. Its functionality has been folded
640 into apm. It was a no-op on ACPI in current for a while now (but was
641 still needed on i386 in FreeBSD 11 and earlier). Users may need to
642 remove it from kernel config files.
645 The use of RSS hash from the network card aka flowid has been
646 disabled by default for lagg(4) as it's currently incompatible with
647 the lacp and loadbalance protocols.
649 This can be re-enabled by setting the following in loader.conf:
650 net.link.lagg.default_use_flowid="1"
653 The SW_WATCHDOG option is no longer necessary to enable the
654 hardclock-based software watchdog if no hardware watchdog is
655 configured. As before, SW_WATCHDOG will cause the software
656 watchdog to be enabled even if a hardware watchdog is configured.
659 r326887 fixes the issue described in the 20171214 UPDATING entry.
660 r326888 flips the switch back to building GELI support always.
663 r362593 broke ZFS + GELI support for reasons unknown. However,
664 it also broke ZFS support generally, so GELI has been turned off
665 by default as the lesser evil in r326857. If you boot off ZFS and/or
666 GELI, it might not be a good time to update.
669 PowerPC users must update loader(8) by rebuilding world before
670 installing a new kernel, as the protocol connecting them has
671 changed. Without the update, loader metadata will not be passed
672 successfully to the kernel and users will have to enter their
673 root partition at the kernel mountroot prompt to continue booting.
674 Newer versions of loader can boot old kernels without issue.
677 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
678 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
679 to WITH/OUT_LOADER_GELI.
682 The naive and non-compliant support of posix_fallocate(2) in ZFS
683 has been removed as of r325320. The system call now returns EINVAL
684 when used on a ZFS file. Although the new behavior complies with the
685 standard, some consumers are not prepared to cope with it.
686 One known victim is lld prior to r325420.
689 Building in a FreeBSD src checkout will automatically create object
690 directories now rather than store files in the current directory if
691 'make obj' was not ran. Calling 'make obj' is no longer necessary.
692 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
693 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
697 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
698 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
699 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
700 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
701 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
702 The UNIFIED_OBJDIR option is a transitional feature that will be
703 removed for 12.0 release; please migrate to the new format for any
704 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
705 than hardcoding paths.
708 The native-xtools target no longer installs the files by default to the
709 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
710 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
713 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
714 options are changing from controlling the build if defined / undefined
715 to controlling the build with explicit 'yes' or 'no' values. They will
716 shift to WITH/WITHOUT options to match other options in the system.
719 libstand has turned into a private library for sys/boot use only.
720 It is no longer supported as a public interface outside of sys/boot.
723 The arm port has split armv6 into armv6 and armv7. armv7 is now
724 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
725 and are running a kernel from before r324363, you will need to add
726 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
729 When building multiple kernels using KERNCONF, non-existent KERNCONF
730 files will produce an error and buildkernel will fail. Previously
731 missing KERNCONF files silently failed giving no indication as to
732 why, only to subsequently discover during installkernel that the
733 desired kernel was never built in the first place.
736 The default serial number format for CTL LUNs has changed. This will
737 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
738 or iSCSI clients care about their LUNs' serial numbers. Users who
739 require serial number stability should hardcode serial numbers in
743 For 32-bit arm compiled for hard-float support, soft-floating point
744 binaries now always get their shared libraries from
745 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
746 /usr/libsoft also existed). Only users with a hard-float ld.so, but
747 soft-float everything else should be affected.
750 The geli password typed at boot is now hidden. To restore the previous
751 behavior, see geli(8) for configuration options.
754 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
755 sysctl values. Minor nit, but requires a rebuild of both world/kernel
759 "make check" behavior (made in ^/head@r295380) has been changed to
760 execute from a limited sandbox, as opposed to executing from
764 - The "beforecheck" and "aftercheck" targets are now specified.
765 - ${CHECKDIR} (added in commit noted above) has been removed.
766 - Legacy behavior can be enabled by setting
767 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
769 If the limited sandbox mode is enabled, "make check" will execute
770 "make distribution", then install, execute the tests, and clean up the
771 sandbox if successful.
773 The "make distribution" and "make install" targets are typically run as
774 root to set appropriate permissions and ownership at installation time.
775 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
776 environment if executing "make check" with limited sandbox mode using
777 an unprivileged user.
780 Since the switch to GPT disk labels, fsck for UFS/FFS has been
781 unable to automatically find alternate superblocks. As of r322297,
782 the information needed to find alternate superblocks has been
783 moved to the end of the area reserved for the boot block.
784 Filesystems created with a newfs of this vintage or later
785 will create the recovery information. If you have a filesystem
786 created prior to this change and wish to have a recovery block
787 created for your filesystem, you can do so by running fsck in
788 foreground mode (i.e., do not use the -p or -y options). As it
789 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
790 to which you should answer yes.
793 As of r321665, an NFSv4 server configuration that services
794 Kerberos mounts or clients that do not support the uid/gid in
795 owner/owner_group string capability, must explicitly enable
796 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
797 machine's /etc/rc.conf file.
800 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
801 Please see the 20141231 entry below for information about prerequisites
802 and upgrading, if you are not already using clang 3.5.0 or higher.
805 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
806 r-commands (rlogin, rsh, etc.) to be built with the base system.
809 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
810 a very major ABI incompatible change, so users of FreeBSD/powerpc must
811 be careful when performing source upgrades. It is best to run
812 'make installworld' from an alternate root system, either a live
813 CD/memory stick, or a temporary root partition. Additionally, all ports
814 must be recompiled. powerpc64 is largely unaffected, except in the case
815 of 32-bit compatibility. All 32-bit binaries will be affected.
818 Forward compatibility for the "ino64" project have been committed. This
819 will allow most new binaries to run on older kernels in a limited
820 fashion. This prevents many of the common foot-shooting actions in the
821 upgrade as well as the limited ability to roll back the kernel across
822 the ino64 upgrade. Complicated use cases may not work properly, though
823 enough simpler ones work to allow recovery in most situations.
826 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
827 if you require the GPL compiler.
830 The internal ABI used for communication between the NFS kernel modules
831 was changed by r320085, so __FreeBSD_version was bumped to
832 ensure all the NFS related modules are updated together.
835 The ABI of struct event was changed by extending the data
836 member to 64bit and adding ext fields. For upgrade, same
837 precautions as for the entry 20170523 "ino64" must be
841 The GNU roff toolchain has been removed from base. To render manpages
842 which are not supported by mandoc(1), man(1) can fallback on GNU roff
843 from ports (and recommends to install it).
844 To render roff(7) documents, consider using GNU roff from ports or the
845 heirloom doctools roff toolchain from ports via pkg install groff or
846 via pkg install heirloom-doctools.
849 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
850 smaller runtime footprint builds. This is useful for embedded systems
851 which only require one chipset support.
853 If you load it as a module, make sure this is in /boot/loader.conf:
857 This will load the HAL, all chip/RF backends and if_ath_pci.
858 If you have if_ath_pci in /boot/loader.conf, ensure it is after
859 if_ath or it will not load any HAL chipset support.
861 If you want to selectively load things (eg on ye cheape ARM/MIPS
862 platforms where RAM is at a premium) you should:
865 * load the chip modules in question
866 * load ath_rate, ath_dfs
868 * load if_ath_pci and/or if_ath_ahb depending upon your particular
869 bus bind type - this is where probe/attach is done.
871 For further comments/feedback, poke adrian@ .
874 The "ino64" 64-bit inode project has been committed, which extends
875 a number of types to 64 bits. Upgrading in place requires care and
876 adherence to the documented upgrade procedure.
878 If using a custom kernel configuration ensure that the
879 COMPAT_FREEBSD11 option is included (as during the upgrade the
880 system will be running the ino64 kernel with the existing world).
882 For the safest in-place upgrade begin by removing previous build
883 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
884 procedure documented below under the heading "To rebuild everything and
885 install it on the current system." Specifically, a reboot is required
886 after installing the new kernel before installing world. While an
887 installworld normally works by accident from multiuser after rebooting
888 the proper kernel, there are many cases where this will fail across this
889 upgrade and installworld from single user is required.
892 The NATM framework including the en(4), fatm(4), hatm(4), and
893 patm(4) devices has been removed. Consumers should plan a
894 migration before the end-of-life date for FreeBSD 11.
897 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
898 diff has not been implemented, if those are needed a newer version of
899 GNU diff is available via the diffutils package under the gdiff name.
902 As of r316810 for ipfilter, keep frags is no longer assumed when
903 keep state is specified in a rule. r316810 aligns ipfilter with
904 documentation in man pages separating keep frags from keep state.
905 This allows keep state to be specified without forcing keep frags
906 and allows keep frags to be specified independently of keep state.
907 To maintain previous behaviour, also specify keep frags with
908 keep state (as documented in ipf.conf.5).
911 arm64 builds now use the base system LLD 4.0.0 linker by default,
912 instead of requiring that the aarch64-binutils port or package be
913 installed. To continue using aarch64-binutils, set
914 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
917 The UDP optimization in entry 20160818 that added the sysctl
918 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
919 packets will no longer be treated as L3 broadcast packets.
922 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
923 use any explicitly assigned loopback address available in the jail
924 instead of using the first assigned address of the jail.
927 The ctl.ko module no longer implements the iSCSI target frontend:
928 cfiscsi.ko does instead.
930 If building cfiscsi.ko as a kernel module, the module can be loaded
931 via one of the following methods:
932 - `cfiscsi_load="YES"` in loader.conf(5).
933 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
934 - ctladm(8)/ctld(8), when compiled with iSCSI support
935 (`WITH_ISCSI=yes` in src.conf(5))
937 Please see cfiscsi(4) for more details.
940 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
941 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
942 same source (previously, the dependency of mmcsd.ko on mmc.ko was
943 missing, but mmcsd.ko now will refuse to load if it is incompatible
947 The syntax of ipfw(8) named states was changed to avoid ambiguity.
948 If you have used named states in the firewall rules, you need to modify
949 them after installworld and before rebooting. Now named states must
950 be prefixed with colon.
953 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
954 removed as the userland we provide cannot use them. The KMS version
955 (sys/dev/drm2) supports the same hardware.
958 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
959 Please see the 20141231 entry below for information about prerequisites
960 and upgrading, if you are not already using clang 3.5.0 or higher.
963 The code that provides support for ZFS .zfs/ directory functionality
964 has been reimplemented. It's not possible now to create a snapshot
965 by mkdir under .zfs/snapshot/. That should be the only user visible
969 EISA bus support has been removed. The WITH_EISA option is no longer
973 MCA bus support has been removed.
976 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
977 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
980 The EM_MULTIQUEUE kernel configuration option is deprecated now that
981 the em(4) driver conforms to iflib specifications.
984 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
985 IFLIB. If you have a custom kernel configuration that excludes em(4)
986 but you use igb(4), you need to re-add em(4) to your custom
990 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
991 Please see the 20141231 entry below for information about prerequisites
992 and upgrading, if you are not already using clang 3.5.0 or higher.
995 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
996 Please see the 20141231 entry below for information about prerequisites
997 and upgrading, if you are not already using clang 3.5.0 or higher.
1000 The layout of the pmap structure has changed for powerpc to put the pmap
1001 statistics at the front for all CPU variations. libkvm(3) and all tools
1002 that link against it need to be recompiled.
1005 isl(4) and cyapa(4) drivers now require a new driver,
1006 chromebook_platform(4), to work properly on Chromebook-class hardware.
1007 On other types of hardware the drivers may need to be configured using
1008 device hints. Please see the corresponding manual pages for details.
1011 The urtwn(4) driver was merged into rtwn(4) and now consists of
1012 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1014 Also, firmware for RTL8188CE was renamed due to possible name
1015 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1018 GNU rcs has been removed from base. It is available as packages:
1019 - rcs: Latest GPLv3 GNU rcs version.
1020 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1024 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1025 modules now requires that the kernel configuration contain the
1026 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1029 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1030 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1033 Relocatable object files with the extension of .So have been renamed
1034 to use an extension of .pico instead. The purpose of this change is
1035 to avoid a name clash with shared libraries on case-insensitive file
1036 systems. On those file systems, foo.So is the same file as foo.so.
1039 GNU rcs has been turned off by default. It can (temporarily) be built
1040 again by adding WITH_RCS knob in src.conf.
1041 Otherwise, GNU rcs is available from packages:
1042 - rcs: Latest GPLv3 GNU rcs version.
1043 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1046 The backup_uses_rcs functionality has been removed from rc.subr.
1049 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1050 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1051 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1052 QUEUE_MACRO_DEBUG behavior.
1055 r304787 changed some ioctl interfaces between the iSCSI userspace
1056 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1057 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1061 The UDP receive code has been updated to only treat incoming UDP
1062 packets that were addressed to an L2 broadcast address as L3
1063 broadcast packets. It is not expected that this will affect any
1064 standards-conforming UDP application. The new behaviour can be
1065 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1069 Remove the openbsd_poll system call.
1070 __FreeBSD_version has been bumped because of this.
1073 The stable/11 branch has been created from head@r302406.
1076 The libc stub for the pipe(2) system call has been replaced with
1077 a wrapper that calls the pipe2(2) system call and the pipe(2)
1078 system call is now only implemented by the kernels that include
1079 "options COMPAT_FREEBSD10" in their config file (this is the
1080 default). Users should ensure that this option is enabled in
1081 their kernel or upgrade userspace to r302092 before upgrading their
1085 CAM will now strip leading spaces from SCSI disks' serial numbers.
1086 This will affect users who create UFS filesystems on SCSI disks using
1087 those disk's diskid device nodes. For example, if /etc/fstab
1088 previously contained a line like
1089 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1090 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1091 transforms like gmirror may also be affected. ZFS users should
1095 The bitstring(3) API has been updated with new functionality and
1096 improved performance. But it is binary-incompatible with the old API.
1097 Objects built with the new headers may not be linked against objects
1098 built with the old headers.
1101 The brk and sbrk functions have been removed from libc on arm64.
1102 Binutils from ports has been updated to not link to these
1103 functions and should be updated to the latest version before
1104 installing a new libc.
1107 The armv6 port now defaults to hard float ABI. Limited support
1108 for running both hardfloat and soft float on the same system
1109 is available using the libraries installed with -DWITH_LIBSOFT.
1110 This has only been tested as an upgrade path for installworld
1111 and packages may fail or need manual intervention to run. New
1112 packages will be needed.
1114 To update an existing self-hosted armv6hf system, you must add
1115 TARGET_ARCH=armv6 on the make command line for both the build
1116 and the install steps.
1119 Kernel modules compiled outside of a kernel build now default to
1120 installing to /boot/modules instead of /boot/kernel. Many kernel
1121 modules built this way (such as those in ports) already overrode
1122 KMODDIR explicitly to install into /boot/modules. However,
1123 manually building and installing a module from /sys/modules will
1124 now install to /boot/modules instead of /boot/kernel.
1127 The CAM I/O scheduler has been committed to the kernel. There should be
1128 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1129 list of known rogues that claim support for this but actually corrupt
1130 data is believed to be complete, be on the lookout for data
1131 corruption. The known rogue list is believed to be complete:
1133 o Crucial MX100, M550 drives with MU01 firmware.
1134 o Micron M510 and M550 drives with MU01 firmware.
1135 o Micron M500 prior to MU07 firmware
1136 o Samsung 830, 840, and 850 all firmwares
1137 o FCCT M500 all firmwares
1139 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1140 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1141 updated firmware. Black listed drives will work correctly because these
1142 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1143 this list is the same as found in Linux, it's believed there are no
1144 other rogues in the market place. All other models from the above
1147 To be safe, if you are at all concerned, you can quirk each of your
1148 drives to prevent NCQ from being sent by setting:
1149 kern.cam.ada.X.quirks="0x2"
1150 in loader.conf. If the drive requires the 4k sector quirk, set the
1151 quirks entry to 0x3.
1154 The FAST_DEPEND build option has been removed and its functionality is
1155 now the one true way. The old mkdep(1) style of 'make depend' has
1156 been removed. See 20160311 for further details.
1159 Resource range types have grown from unsigned long to uintmax_t. All
1160 drivers, and anything using libdevinfo, need to be recompiled.
1163 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1164 builds. It no longer runs mkdep(1) during 'make depend', and the
1165 'make depend' stage can safely be skipped now as it is auto ran
1166 when building 'make all' and will generate all SRCS and DPSRCS before
1167 building anything else. Dependencies are gathered at compile time with
1168 -MF flags kept in separate .depend files per object file. Users should
1169 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1170 stale .depend files.
1173 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1174 kernel modules. Therefore, if you load any kernel modules at boot time,
1175 please install the boot loaders after you install the kernel, but before
1179 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1180 make installkernel KERNCONF=YOUR_KERNEL_HERE
1181 make -C sys/boot install
1182 <reboot in single user>
1184 Then follow the usual steps, described in the General Notes section,
1188 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1189 see the 20141231 entry below for information about prerequisites and
1190 upgrading, if you are not already using clang 3.5.0 or higher.
1193 The AIO subsystem is now a standard part of the kernel. The
1194 VFS_AIO kernel option and aio.ko kernel module have been removed.
1195 Due to stability concerns, asynchronous I/O requests are only
1196 permitted on sockets and raw disks by default. To enable
1197 asynchronous I/O requests on all file types, set the
1198 vfs.aio.enable_unsafe sysctl to a non-zero value.
1201 The ELF object manipulation tool objcopy is now provided by the
1202 ELF Tool Chain project rather than by GNU binutils. It should be a
1203 drop-in replacement, with the addition of arm64 support. The
1204 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1205 to obtain the GNU version if necessary.
1208 Building ZFS pools on top of zvols is prohibited by default. That
1209 feature has never worked safely; it's always been prone to deadlocks.
1210 Using a zvol as the backing store for a VM guest's virtual disk will
1211 still work, even if the guest is using ZFS. Legacy behavior can be
1212 restored by setting vfs.zfs.vol.recursive=1.
1215 The NONE and HPN patches has been removed from OpenSSH. They are
1216 still available in the security/openssh-portable port.
1219 With the addition of ypldap(8), a new _ypldap user is now required
1220 during installworld. "mergemaster -p" can be used to add the user
1221 prior to installworld, as documented in the handbook.
1224 The tftp loader (pxeboot) now uses the option root-path directive. As a
1225 consequence it no longer looks for a pxeboot.4th file on the tftp
1226 server. Instead it uses the regular /boot infrastructure as with the
1230 The code to start recording plug and play data into the modules has
1231 been committed. While the old tools will properly build a new kernel,
1232 a number of warnings about "unknown metadata record 4" will be produced
1233 for an older kldxref. To avoid such warnings, make sure to rebuild
1234 the kernel toolchain (or world). Make sure that you have r292078 or
1235 later when trying to build 292077 or later before rebuilding.
1238 Debug data files are now built by default with 'make buildworld' and
1239 installed with 'make installworld'. This facilitates debugging but
1240 requires more disk space both during the build and for the installed
1241 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1245 r291527 changed the internal interface between the nfsd.ko and
1246 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1247 __FreeBSD_version has been bumped because of this.
1250 Add support for unicode collation strings leads to a change of
1251 order of files listed by ls(1) for example. To get back to the old
1252 behaviour, set LC_COLLATE environment variable to "C".
1254 Databases administrators will need to reindex their databases given
1255 collation results will be different.
1257 Due to a bug in install(1) it is recommended to remove the ancient
1258 locales before running make installworld.
1260 rm -rf /usr/share/locale/*
1263 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1264 libcrypto.so.7 or libssl.so.7 must be recompiled.
1267 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1268 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1269 should be replaced with isp_2400 and isp_2500 modules respectively.
1272 The build previously allowed using 'make -n' to not recurse into
1273 sub-directories while showing what commands would be executed, and
1274 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1275 and 'make -N' will not.
1278 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1279 and etcupdate will now use this file. A custom sendmail.cf is now
1280 updated via this mechanism rather than via installworld. If you had
1281 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1282 want to remove the exclusion or change it to "always install".
1283 /etc/mail/sendmail.cf is now managed the same way regardless of
1284 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1285 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1288 Compatibility shims for legacy ATA device names have been removed.
1289 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1290 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1291 environment variables, /dev/ad* and /dev/ar* symbolic links.
1294 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1295 Please see the 20141231 entry below for information about prerequisites
1296 and upgrading, if you are not already using clang 3.5.0 or higher.
1299 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1300 and renamed from .symbols to .debug. This reduces the size requirements
1301 on the boot partition or file system and provides consistency with
1302 userland debug files.
1304 When using the supported kernel installation method the
1305 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1306 as is done with /boot/kernel.
1308 Developers wishing to maintain the historical behavior of installing
1309 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1312 The wireless drivers had undergone changes that remove the 'parent
1313 interface' from the ifconfig -l output. The rc.d network scripts
1314 used to check presence of a parent interface in the list, so old
1315 scripts would fail to start wireless networking. Thus, etcupdate(3)
1316 or mergemaster(8) run is required after kernel update, to update your
1317 rc.d scripts in /etc.
1320 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1321 These configurations are now automatically interpreted as
1322 'scrub fragment reassemble'.
1325 Kernel-loadable modules for the random(4) device are back. To use
1326 them, the kernel must have
1329 options RANDOM_LOADABLE
1331 kldload(8) can then be used to load random_fortuna.ko
1332 or random_yarrow.ko. Please note that due to the indirect
1333 function calls that the loadable modules need to provide,
1334 the build-in variants will be slightly more efficient.
1336 The random(4) kernel option RANDOM_DUMMY has been retired due to
1337 unpopularity. It was not all that useful anyway.
1340 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1341 Control over building the ELF Tool Chain tools is now provided by
1342 the WITHOUT_TOOLCHAIN knob.
1345 The polarity of Pulse Per Second (PPS) capture events with the
1346 uart(4) driver has been corrected. Prior to this change the PPS
1347 "assert" event corresponded to the trailing edge of a positive PPS
1348 pulse and the "clear" event was the leading edge of the next pulse.
1350 As the width of a PPS pulse in a typical GPS receiver is on the
1351 order of 1 millisecond, most users will not notice any significant
1352 difference with this change.
1354 Anyone who has compensated for the historical polarity reversal by
1355 configuring a negative offset equal to the pulse width will need to
1356 remove that workaround.
1359 The default group assigned to /dev/dri entries has been changed
1360 from 'wheel' to 'video' with the id of '44'. If you want to have
1361 access to the dri devices please add yourself to the video group
1364 # pw groupmod video -m $USER
1367 The menu.rc and loader.rc files will now be replaced during
1368 upgrades. Please migrate local changes to menu.rc.local and
1369 loader.rc.local instead.
1372 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1373 strings and strip have been removed. The src.conf(5) knob
1374 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1377 As ZFS requires more kernel stack pages than is the default on some
1378 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1379 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1381 Please consider using 'options KSTACK_PAGES=X' where X is greater
1382 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1385 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1386 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1387 default, i.e., they will not contain "::". For example, instead
1388 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1389 to have a more specific match, such as different map entries for
1390 IPv6:0:0 vs IPv6:0. This change requires that configuration
1391 data (including maps, files, classes, custom ruleset, etc.) must
1392 use the same format, so make certain such configuration data is
1393 upgrading. As a very simple check search for patterns like
1394 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1395 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1396 the cf option UseCompressedIPv6Addresses.
1399 The default kernel entropy-processing algorithm is now
1400 Fortuna, replacing Yarrow.
1402 Assuming you have 'device random' in your kernel config
1403 file, the configurations allow a kernel option to override
1404 this default. You may choose *ONE* of:
1406 options RANDOM_YARROW # Legacy /dev/random algorithm.
1407 options RANDOM_DUMMY # Blocking-only driver.
1409 If you have neither, you get Fortuna. For most people,
1410 read no further, Fortuna will give a /dev/random that works
1411 like it always used to, and the difference will be irrelevant.
1413 If you remove 'device random', you get *NO* kernel-processed
1414 entropy at all. This may be acceptable to folks building
1415 embedded systems, but has complications. Carry on reading,
1416 and it is assumed you know what you need.
1418 *PLEASE* read random(4) and random(9) if you are in the
1419 habit of tweaking kernel configs, and/or if you are a member
1420 of the embedded community, wanting specific and not-usual
1421 behaviour from your security subsystems.
1423 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1424 random', you will NOT have a functioning /dev/random, and
1425 many cryptographic features will not work, including SSH.
1426 You may also find strange behaviour from the random(3) set
1427 of library functions, in particular sranddev(3), srandomdev(3)
1428 and arc4random(3). The reason for this is that the KERN_ARND
1429 sysctl only returns entropy if it thinks it has some to
1430 share, and with RANDOM_DUMMY or no 'device random' this
1434 An additional fix for the issue described in the 20150614 sendmail
1435 entry below has been committed in revision 284717.
1438 FreeBSD's old make (fmake) has been removed from the system. It is
1439 available as the devel/fmake port or via pkg install fmake.
1442 The fix for the issue described in the 20150614 sendmail entry
1443 below has been committed in revision 284436. The work
1444 around described in that entry is no longer needed unless the
1445 default setting is overridden by a confDH_PARAMETERS configuration
1446 setting of '5' or pointing to a 512 bit DH parameter file.
1449 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1450 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1451 and devel/kyua to version 0.20+ and adjust any calling code to work
1452 with Kyuafile and kyua.
1455 The import of openssl to address the FreeBSD-SA-15:10.openssl
1456 security advisory includes a change which rejects handshakes
1457 with DH parameters below 768 bits. sendmail releases prior
1458 to 8.15.2 (not yet released), defaulted to a 512 bit
1459 DH parameter setting for client connections. To work around
1460 this interoperability, sendmail can be configured to use a
1461 2048 bit DH parameter by:
1463 1. Edit /etc/mail/`hostname`.mc
1464 2. If a setting for confDH_PARAMETERS does not exist or
1465 exists and is set to a string beginning with '5',
1466 replace it with '2'.
1467 3. If a setting for confDH_PARAMETERS exists and is set to
1468 a file path, create a new file with:
1469 openssl dhparam -out /path/to/file 2048
1470 4. Rebuild the .cf file:
1471 cd /etc/mail/; make; make install
1472 5. Restart sendmail:
1473 cd /etc/mail/; make restart
1475 A sendmail patch is coming, at which time this file will be
1479 Generation of legacy formatted entries have been disabled by default
1480 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1481 entries were converted to use the new format by default when the new,
1482 machine independent format have been added and supported since FreeBSD
1485 Please see the pwd_mkdb(8) manual page for further details.
1488 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1489 20141231 entry below for information about prerequisites and upgrading,
1490 if you are not already using 3.5.0 or higher.
1493 TI platform code switched to using vendor DTS files and this update
1494 may break existing systems running on Beaglebone, Beaglebone Black,
1497 - dtb files should be regenerated/reinstalled. Filenames are the
1498 same but content is different now
1499 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1500 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1501 addressing scheme is now pin 25 on /dev/gpioc3.
1502 - Pandaboard: /etc/ttys should be updated, serial console device is
1503 now /dev/ttyu2, not /dev/ttyu0
1506 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1507 If you need the GNU extension from groff soelim(1), install groff
1508 from package: pkg install groff, or via ports: textproc/groff.
1511 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1512 defined in symlink(7); previously symlinks were silently ignored.
1515 The const qualifier has been removed from iconv(3) to comply with
1516 POSIX. The ports tree is aware of this from r384038 onwards.
1519 Libraries specified by LIBADD in Makefiles must have a corresponding
1520 DPADD_<lib> variable to ensure correct dependencies. This is now
1521 enforced in src.libnames.mk.
1524 From legacy ata(4) driver was removed support for SATA controllers
1525 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1526 Kernel modules ataahci and ataadaptec were removed completely,
1527 replaced by ahci and mvs modules respectively.
1530 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1531 the 20141231 entry below for information about prerequisites and
1532 upgrading, if you are not already using 3.5.0 or higher.
1535 The 32-bit PowerPC kernel has been changed to a position-independent
1536 executable. This can only be booted with a version of loader(8)
1537 newer than January 31, 2015, so make sure to update both world and
1538 kernel before rebooting.
1541 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1542 but before r278950, the RNG was not seeded properly. Immediately
1543 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1544 ssh keys or openssl keys) that were generated w/ a kernel from that
1545 range. This does not affect programs that directly used /dev/random
1546 or /dev/urandom. All userland uses of arc4random(3) are affected.
1549 The autofs(4) ABI was changed in order to restore binary compatibility
1550 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1551 with the new kernel.
1554 The powerpc64 kernel has been changed to a position-independent
1555 executable. This can only be booted with a new version of loader(8),
1556 so make sure to update both world and kernel before rebooting.
1559 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1560 only release, no new features have been added. Please see the 20141231
1561 entry below for information about prerequisites and upgrading, if you
1562 are not already using 3.5.0.
1565 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1566 taken from the ELF Tool Chain project rather than GNU binutils. They
1567 should be drop-in replacements, with the addition of arm64 support.
1568 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1569 binutils tools, if necessary. See 20150805 for updated information.
1572 The default Unbound configuration now enables remote control
1573 using a local socket. Users who have already enabled the
1574 local_unbound service should regenerate their configuration
1575 by running "service local_unbound setup" as root.
1578 The GNU texinfo and GNU info pages have been removed.
1579 To be able to view GNU info pages please install texinfo from ports.
1582 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1584 As of this release, a prerequisite for building clang, llvm and lldb is
1585 a C++11 capable compiler and C++11 standard library. This means that to
1586 be able to successfully build the cross-tools stage of buildworld, with
1587 clang as the bootstrap compiler, your system compiler or cross compiler
1588 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1589 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1592 On any standard FreeBSD 10.x or 11.x installation, where clang and
1593 libc++ are on by default (that is, on x86 or arm), this should work out
1596 On 9.x installations where clang is enabled by default, e.g. on x86 and
1597 powerpc, libc++ will not be enabled by default, so libc++ should be
1598 built (with clang) and installed first. If both clang and libc++ are
1599 missing, build clang first, then use it to build libc++.
1601 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1602 the instructions for 9.x above.
1604 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1605 default, and do not build clang.
1607 Many embedded systems are resource constrained, and will not be able to
1608 build clang in a reasonable time, or in some cases at all. In those
1609 cases, cross building bootable systems on amd64 is a workaround.
1611 This new version of clang introduces a number of new warnings, of which
1612 the following are most likely to appear:
1616 This warns in two cases, for both C and C++:
1617 * When the code is trying to take the absolute value of an unsigned
1618 quantity, which is effectively a no-op, and almost never what was
1619 intended. The code should be fixed, if at all possible. If you are
1620 sure that the unsigned quantity can be safely cast to signed, without
1621 loss of information or undefined behavior, you can add an explicit
1622 cast, or disable the warning.
1624 * When the code is trying to take an absolute value, but the called
1625 abs() variant is for the wrong type, which can lead to truncation.
1626 If you want to disable the warning instead of fixing the code, please
1627 make sure that truncation will not occur, or it might lead to unwanted
1630 -Wtautological-undefined-compare and
1631 -Wundefined-bool-conversion
1633 These warn when C++ code is trying to compare 'this' against NULL, while
1634 'this' should never be NULL in well-defined C++ code. However, there is
1635 some legacy (pre C++11) code out there, which actively abuses this
1636 feature, which was less strictly defined in previous C++ versions.
1638 Squid and openjdk do this, for example. The warning can be turned off
1639 for C++98 and earlier, but compiling the code in C++11 mode might result
1640 in unexpected behavior; for example, the parts of the program that are
1641 unreachable could be optimized away.
1644 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1645 kernel sources have been removed. The .h files remain, since some
1646 utilities include them. This will need to be fixed later.
1647 If "mount -t oldnfs ..." is attempted, it will fail.
1648 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1649 the utilities will report errors.
1652 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1653 directories to top level SUBDIR variable when their parent
1654 directory is included in LOCAL_DIRS. Users with build systems with
1655 such hierarchies and without SUBDIR entries in the parent
1656 directory Makefiles should add them or add the directories to
1660 faith(4) and faithd(8) have been removed from the base system. Faith
1661 has been obsolete for a very long time.
1664 vt(4), the new console driver, is enabled by default. It brings
1665 support for Unicode and double-width characters, as well as
1666 support for UEFI and integration with the KMS kernel video
1669 You may need to update your console settings in /etc/rc.conf,
1670 most probably the keymap. During boot, /etc/rc.d/syscons will
1671 indicate what you need to do.
1673 vt(4) still has issues and lacks some features compared to
1674 syscons(4). See the wiki for up-to-date information:
1675 https://wiki.freebsd.org/Newcons
1677 If you want to keep using syscons(4), you can do so by adding
1678 the following line to /boot/loader.conf:
1682 pjdfstest has been integrated into kyua as an opt-in test suite.
1683 Please see share/doc/pjdfstest/README for more details on how to
1687 gperf has been removed from the base system for architectures
1688 that use clang. Ports that require gperf will obtain it from the
1692 pjdfstest has been moved from tools/regression/pjdfstest to
1696 At svn r271982, The default linux compat kernel ABI has been adjusted
1697 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1698 update. If you wish to continue using the linux-f10 compat ports,
1699 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1700 encouraged to update their linux-compat packages to linux-c6 during
1701 their next update cycle.
1704 The ofwfb driver, used to provide a graphics console on PowerPC when
1705 using vt(4), no longer allows mmap() of all physical memory. This
1706 will prevent Xorg on PowerPC with some ATI graphics cards from
1707 initializing properly unless x11-servers/xorg-server is updated to
1711 The xdev targets have been converted to using TARGET and
1712 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1715 The default unbound configuration has been modified to address
1716 issues with reverse lookups on networks that use private
1717 address ranges. If you use the local_unbound service, run
1718 "service local_unbound setup" as root to regenerate your
1719 configuration, then "service local_unbound reload" to load the
1723 The GNU texinfo and GNU info pages are not built and installed
1724 anymore, WITH_INFO knob has been added to allow to built and install
1726 UPDATE: see 20150102 entry on texinfo's removal
1729 The GNU readline library is now an INTERNALLIB - that is, it is
1730 statically linked into consumers (GDB and variants) in the base
1731 system, and the shared library is no longer installed. The
1732 devel/readline port is available for third party software that
1736 The Itanium architecture (ia64) has been removed from the list of
1737 known architectures. This is the first step in the removal of the
1741 Commit r268115 has added NFSv4.1 server support, merged from
1742 projects/nfsv4.1-server. Since this includes changes to the
1743 internal interfaces between the NFS related modules, a full
1744 build of the kernel and modules will be necessary.
1745 __FreeBSD_version has been bumped.
1748 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1749 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1750 which differs from the behaviour controlled by this knob.)
1753 Maximal length of the serial number in CTL was increased from 16 to
1754 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1755 and ctld, need to be rebuilt to work with a new kernel.
1758 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1759 1 respectively to match the upstream numbers. They were out of
1760 sync because, when they were originally added to FreeBSD, the
1761 upstream versions were not respected. These libraries are private
1762 and not yet built by default, so renumbering them should be a
1763 non-issue. However, unclean source trees will yield broken test
1764 programs once the operator executes "make delete-old-libs" after a
1765 "make installworld".
1767 Additionally, the atf-sh binary was made private by moving it into
1768 /usr/libexec/. Already-built shell test programs will keep the
1769 path to the old binary so they will break after "make delete-old"
1772 If you are using WITH_TESTS=yes (not the default), wipe the object
1773 tree and rebuild from scratch to prevent spurious test failures.
1774 This is only needed once: the misnumbered libraries and misplaced
1775 binaries have been added to OptionalObsoleteFiles.inc so they will
1776 be removed during a clean upgrade.
1779 Clang and llvm have been upgraded to 3.4.1 release.
1782 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1783 be removed to avoid issues in the future (and has been added to
1787 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1788 past, it affected all builds that used the bsd.*.mk files. The old
1789 behavior was a bug, but people may have relied upon it. To get this
1790 behavior back, you can .include /etc/src.conf from /etc/make.conf
1791 (which is still global and isn't changed). This also changes the
1792 behavior of incremental builds inside the tree of individual
1793 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1794 Although this has survived make universe and some upgrade scenarios,
1795 other upgrade scenarios may have broken. At least one form of
1796 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1797 as well... In cases where MAKESYSPATH isn't working with this
1798 setting, you'll need to set it to the full path to your tree.
1800 One side effect of all this cleaning up is that bsd.compiler.mk
1801 is no longer implicitly included by bsd.own.mk. If you wish to
1802 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1806 The lindev device has been removed since /dev/full has been made a
1807 standard device. __FreeBSD_version has been bumped.
1810 The knob WITHOUT_VI was added to the base system, which controls
1811 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1812 in order to reorder files share/termcap and didn't build ex(1) as a
1813 build tool, so building/installing with WITH_VI is highly advised for
1814 build hosts for older releases.
1816 This issue has been fixed in stable/9 and stable/10 in r277022 and
1817 r276991, respectively.
1820 The YES_HESIOD knob has been removed. It has been obsolete for
1821 a decade. Please move to using WITH_HESIOD instead or your builds
1822 will silently lack HESIOD.
1825 The uart(4) driver has been changed with respect to its handling
1826 of the low-level console. Previously the uart(4) driver prevented
1827 any process from changing the baudrate or the CLOCAL and HUPCL
1828 control flags. By removing the restrictions, operators can make
1829 changes to the serial console port without having to reboot.
1830 However, when getty(8) is started on the serial device that is
1831 associated with the low-level console, a misconfigured terminal
1832 line in /etc/ttys will now have a real impact.
1833 Before upgrading the kernel, make sure that /etc/ttys has the
1834 serial console device configured as 3wire without baudrate to
1835 preserve the previous behaviour. E.g:
1836 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1839 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1840 to improve performance. To re-enable it, if needed, run rpcbind
1841 with command line option -W.
1844 Switched back to the GPL dtc compiler due to updates in the upstream
1845 dts files not being supported by the BSDL dtc compiler. You will need
1846 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1847 may result while building dtb files during a kernel build if you fail
1848 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1851 Clang and llvm have been upgraded to 3.4 release.
1854 The nve(4) driver has been removed. Please use the nfe(4) driver
1855 for NVIDIA nForce MCP Ethernet adapters instead.
1858 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1859 This could cause certain C++ applications using shared libraries built
1860 against the previous version of libc++ to crash. The incompatibility
1861 has now been fixed, but any C++ applications or shared libraries built
1862 between r261283 and r261801 should be recompiled.
1865 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1866 capability mode support. Please note that enabling the feature in
1867 kernel is still highly recommended.
1870 OpenSSH is now built with sandbox support, and will use sandbox as
1871 the default privilege separation method. This requires Capsicum
1872 capability mode support in kernel.
1875 The libelf and libdwarf libraries have been updated to newer
1876 versions from upstream. Shared library version numbers for
1877 these two libraries were bumped. Any ports or binaries
1878 requiring these two libraries should be recompiled.
1879 __FreeBSD_version is bumped to 1100006.
1882 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1883 instead of providing an explicit one, this would prevent such
1884 Makefile from providing its own Kyuafile in the future during
1885 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1886 intervention is needed to clean an objdir if you use NO_CLEAN:
1887 # find /usr/obj -name Kyuafile | xargs rm -f
1890 The behavior of gss_pseudo_random() for the krb5 mechanism
1891 has changed, for applications requesting a longer random string
1892 than produced by the underlying enctype's pseudo-random() function.
1893 In particular, the random string produced from a session key of
1894 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1895 be different at the 17th octet and later, after this change.
1896 The counter used in the PRF+ construction is now encoded as a
1897 big-endian integer in accordance with RFC 4402.
1898 __FreeBSD_version is bumped to 1100004.
1901 The WITHOUT_ATF build knob has been removed and its functionality
1902 has been subsumed into the more generic WITHOUT_TESTS. If you were
1903 using the former to disable the build of the ATF libraries, you
1904 should change your settings to use the latter.
1907 The default version of mtree is nmtree which is obtained from
1908 NetBSD. The output is generally the same, but may vary
1909 slightly. If you found you need identical output adding
1910 "-F freebsd9" to the command line should do the trick. For the
1911 time being, the old mtree is available as fmtree.
1914 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1915 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1916 1.1.4_8 and verify bsdyml not linked in, before running "make
1918 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1920 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1923 The stable/10 branch has been created in subversion from head
1930 Avoid using make -j when upgrading. While generally safe, there are
1931 sometimes problems using -j to upgrade. If your upgrade fails with
1932 -j, please try again without -j. From time to time in the past there
1933 have been problems using -j with buildworld and/or installworld. This
1934 is especially true when upgrading between "distant" versions (eg one
1935 that cross a major release boundary or several minor releases, or when
1936 several months have passed on the -current branch).
1938 Sometimes, obscure build problems are the result of environment
1939 poisoning. This can happen because the make utility reads its
1940 environment when searching for values for global variables. To run
1941 your build attempts in an "environmental clean room", prefix all make
1942 commands with 'env -i '. See the env(1) manual page for more details.
1944 When upgrading from one major version to another it is generally best to
1945 upgrade to the latest code in the currently installed branch first, then
1946 do an upgrade to the new branch. This is the best-tested upgrade path,
1947 and has the highest probability of being successful. Please try this
1948 approach if you encounter problems with a major version upgrade. Since
1949 the stable 4.x branch point, one has generally been able to upgrade from
1950 anywhere in the most recent stable branch to head / current (or even the
1951 last couple of stable branches). See the top of this file when there's
1954 When upgrading a live system, having a root shell around before
1955 installing anything can help undo problems. Not having a root shell
1956 around can lead to problems if pam has changed too much from your
1957 starting point to allow continued authentication after the upgrade.
1959 This file should be read as a log of events. When a later event changes
1960 information of a prior event, the prior event should not be deleted.
1961 Instead, a pointer to the entry with the new information should be
1962 placed in the old entry. Readers of this file should also sanity check
1963 older entries before relying on them blindly. Authors of new entries
1964 should write them with this in mind.
1968 When upgrading the boot ZFS pool to a new version, always follow
1971 1.) recompile and reinstall the ZFS boot loader and boot block
1972 (this is part of "make buildworld" and "make installworld")
1974 2.) update the ZFS boot block on your boot drive
1976 The following example updates the ZFS boot block on the first
1977 partition (freebsd-boot) of a GPT partitioned drive ada0:
1978 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1980 Non-boot pools do not need these updates.
1984 If you are updating from a prior version of FreeBSD (even one just
1985 a few days old), you should follow this procedure. It is the most
1986 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1988 make kernel-toolchain
1989 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1990 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1992 To test a kernel once
1993 ---------------------
1994 If you just want to boot a kernel once (because you are not sure
1995 if it works, or if you want to boot a known bad kernel to provide
1996 debugging information) run
1997 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1998 nextboot -k testkernel
2000 To rebuild everything and install it on the current system.
2001 -----------------------------------------------------------
2002 # Note: sometimes if you are running current you gotta do more than
2003 # is listed here if you are upgrading from a really old current.
2005 <make sure you have good level 0 dumps>
2007 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2008 make installkernel KERNCONF=YOUR_KERNEL_HERE
2010 <reboot in single user> [3]
2017 To cross-install current onto a separate partition
2018 --------------------------------------------------
2019 # In this approach we use a separate partition to hold
2020 # current's root, 'usr', and 'var' directories. A partition
2021 # holding "/", "/usr" and "/var" should be about 2GB in
2024 <make sure you have good level 0 dumps>
2027 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2028 <maybe newfs current's root partition>
2029 <mount current's root partition on directory ${CURRENT_ROOT}>
2030 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2031 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2032 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2033 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2034 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2035 <reboot into current>
2036 <do a "native" rebuild/install as described in the previous section>
2037 <maybe install compatibility libraries from ports/misc/compat*>
2041 To upgrade in-place from stable to current
2042 ----------------------------------------------
2043 <make sure you have good level 0 dumps>
2045 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2046 make installkernel KERNCONF=YOUR_KERNEL_HERE
2048 <reboot in single user> [3]
2055 Make sure that you've read the UPDATING file to understand the
2056 tweaks to various things you need. At this point in the life
2057 cycle of current, things change often and you are on your own
2058 to cope. The defaults can also change, so please read ALL of
2059 the UPDATING entries.
2061 Also, if you are tracking -current, you must be subscribed to
2062 freebsd-current@freebsd.org. Make sure that before you update
2063 your sources that you have read and understood all the recent
2064 messages there. If in doubt, please track -stable which has
2065 much fewer pitfalls.
2067 [1] If you have third party modules, such as vmware, you
2068 should disable them at this point so they don't crash your
2071 [3] From the bootblocks, boot -s, and then do
2075 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2076 cd src # full path to source
2077 adjkerntz -i # if CMOS is wall time
2078 Also, when doing a major release upgrade, it is required that
2079 you boot into single user mode to do the installworld.
2081 [4] Note: This step is non-optional. Failure to do this step
2082 can result in a significant reduction in the functionality of the
2083 system. Attempting to do it by hand is not recommended and those
2084 that pursue this avenue should read this file carefully, as well
2085 as the archives of freebsd-current and freebsd-hackers mailing lists
2086 for potential gotchas. The -U option is also useful to consider.
2087 See mergemaster(8) for more information.
2089 [5] Usually this step is a no-op. However, from time to time
2090 you may need to do this if you get unknown user in the following
2091 step. It never hurts to do it all the time. You may need to
2092 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2093 install) after the buildworld before this step if you last updated
2094 from current before 20130425 or from -stable before 20130430.
2096 [6] This only deletes old files and directories. Old libraries
2097 can be deleted by "make delete-old-libs", but you have to make
2098 sure that no program is using those libraries anymore.
2100 [8] The new kernel must be able to run existing binaries used by an
2101 installworld. When upgrading across major versions, the new kernel's
2102 configuration must include the correct COMPAT_FREEBSD<n> option for
2103 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2104 to do so may leave you with a system that is hard to boot to recover. A
2105 GENERIC kernel will include suitable compatibility options to run
2106 binaries from older branches. Note that the ability to run binaries
2107 from unsupported branches is not guaranteed.
2109 Make sure that you merge any new devices from GENERIC since the
2110 last time you updated your kernel config file. Options also
2111 change over time, so you may need to adjust your custom kernels
2114 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2115 "?=" instead of the "=" assignment operator, so that buildworld can
2116 override the CPUTYPE if it needs to.
2118 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2119 not on the command line, or in /etc/make.conf. buildworld will
2120 warn if it is improperly defined.
2123 This file contains a list, in reverse chronological order, of major
2124 breakages in tracking -current. It is not guaranteed to be a complete
2125 list of such breakages, and only contains entries since September 23, 2011.
2126 If you need to see UPDATING entries from before that date, you will need
2127 to fetch an UPDATING file from an older FreeBSD release.
2129 Copyright information:
2131 Copyright 1998-2009 M. Warner Losh.
2133 Redistribution, publication, translation and use, with or without
2134 modification, in full or in part, in any form or format of this
2135 document are permitted without further permission from the author.
2137 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2138 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2139 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2140 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2141 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2142 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2143 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2144 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2145 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2146 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2147 POSSIBILITY OF SUCH DAMAGE.
2149 Contact Warner Losh if you have any questions about your use of