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 ntpd no longer by default locks its pages in memory, allowing them
31 to be paged out by the kernel. Use rlimit memlock to restore
32 historic BSD behaviour. For example, add "rlimit memlock 32"
33 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
36 Several of ping6's options have been renamed for better consistency
37 with ping. If you use any of -ARWXaghmrtwx, you must update your
38 scripts. See ping6(8) for details.
41 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
42 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
43 been removed from mount_fusefs(8). You can safely remove them from
44 your scripts, because they had no effect.
46 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
47 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
48 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
49 sysctls have been removed. If you felt the need to set any of them to
50 a non-default value, please tell asomers@FreeBSD.org why.
53 Default permissions on the /var/account/acct file (and copies of it
54 rotated by periodic daily scripts) are changed from 0644 to 0640
55 because the file contains sensitive information that should not be
56 world-readable. If the /var/account directory must be created by
57 rc.d/accounting, the mode used is now 0750. Admins who use the
58 accounting feature are encouraged to change the mode of an existing
59 /var/account directory to 0750 or 0700.
62 Entropy collection and the /dev/random device are no longer optional
63 components. The "device random" option has been removed.
64 Implementations of distilling algorithms can still be made loadable
65 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
68 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
69 been upgraded to 8.0.1. Please see the 20141231 entry below for
70 information about prerequisites and upgrading, if you are not already
71 using clang 3.5.0 or higher.
74 A fix was applied to i386 kernel modules to avoid panics with
75 dpcpu or vnet. Users need to recompile i386 kernel modules
76 having pcpu or vnet sections or they will refuse to load.
79 User-wired pages now have their own counter,
80 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
81 to vm.max_user_wired and changed from an unsigned int to an unsigned
82 long. bhyve VMs wired with the -S are now subject to the user
83 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
84 avoid running into the limit.
87 The IPSEC option has been removed from GENERIC. Users requiring
88 ipsec(4) must now load the ipsec(4) kernel module.
91 The tap(4) driver has been folded into tun(4), and the module has been
92 renamed to tuntap. You should update any kld_list="if_tap" or
93 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
94 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
95 module instead, and "device tap" or "device tun" entries in kernel
96 config files to select the tuntap device instead.
99 The following knobs have been added related to tradeoffs between
100 safe use of the random device and availability in the absence of
103 kern.random.initial_seeding.bypass_before_seeding: tunable; set
104 non-zero to bypass the random device prior to seeding, or zero to
105 block random requests until the random device is initially seeded.
106 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
107 availability properties.
109 kern.random.initial_seeding.read_random_bypassed_before_seeding:
110 read-only diagnostic sysctl that is set when bypass is enabled and
111 read_random(9) is bypassed, to enable programmatic handling of this
112 initial condition, if desired.
114 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
115 Similar to the above, but for for arc4random(9) initial seeding.
117 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
118 non-zero to disable warnings in dmesg when the same conditions are
119 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
120 produce warnings in dmesg when the conditions are met.
123 The loadable random module KPI has changed; the random_infra_init()
124 routine now requires a 3rd function pointer for a bool (*)(void)
125 method that returns true if the random device is seeded (and
126 therefore unblocked).
129 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
130 built from head sources between r320757 (July 6, 2017) and
131 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
132 is added to the command line.
133 nfsuserd daemons built from head sources that are post-r338192 are
134 not affected and should continue to work.
137 The fuse(4) module has been renamed to fusefs(4) for consistency with
138 other filesystems. You should update any kld_load="fuse" entries in
139 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
140 "options FUSE" entries in kernel config files.
143 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
144 8.0.0. Please see the 20141231 entry below for information about
145 prerequisites and upgrading, if you are not already using clang 3.5.0
149 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
150 compiled into your custom kernel, add 'device xz' statement to the
154 drm and drm2 have been removed from the tree. Please see
155 https://wiki.freebsd.org/Graphics for the latest information on
156 migrating to the drm ports.
159 Iflib is no longer unconditionally compiled into the kernel. Drivers
160 using iflib and statically compiled into the kernel, now require
161 the 'device iflib' config option. For the same drivers loaded as
162 modules on kernels not having 'device iflib', the iflib.ko module
163 is loaded automatically.
166 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
167 options no longer exist since r343219 and r343427 respectively;
168 nothing uses them, so they should be just removed from custom
172 r342635 changes the way efibootmgr(8) works by requiring users to add
173 the -b (bootnum) parameter for commands where the bootnum was previously
174 specified with each option. For example 'efibootmgr -B 0001' is now
175 'efibootmgr -B -b 0001'.
178 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
179 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
180 servers that have vfs.nfsd.nfs_privport set will only allow mounts
181 from clients using a reserved port#. Since both the FreeBSD and Linux
182 NFSv4 clients use reserved port#s by default, this should not affect
186 The XLP config has been removed. We can't support 64-bit atomics in this
187 kernel because it is running in 32-bit mode. XLP users must transition
188 to running a 64-bit kernel (XLP64 or XLPN32).
190 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
191 the preferred emulator today and we don't need two different ones.
193 The old sibyte / swarm / Broadcom BCM1250 support has been
194 removed from the mips port.
197 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
198 7.0.1. Please see the 20141231 entry below for information about
199 prerequisites and upgrading, if you are not already using clang 3.5.0
203 Remove the timed and netdate programs from the base tree. Setting
204 the time with these daemons has been obsolete for over a decade.
207 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
208 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
209 it produces broken binaries when ifuncs are in use. Users needing
210 GNU ld should install the binutils port or package.
213 The BSD crtbegin and crtend code has been enabled by default. It has
214 had extensive testing on amd64, arm64, and i386. It can be disabled
215 by building a world with -DWITHOUT_BSD_CRTBEGIN.
218 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
219 has been converted to a port (misc/ctm) and will be removed from
220 FreeBSD-13. It is available as a package (ctm) for all supported
224 The default newsyslog.conf(5) file has been changed to only include
225 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
226 the filenames end in '.conf' and do not begin with a '.'.
228 You should check the configuration files in these two directories match
229 this naming convention. You can verify which configuration files are
230 being included using the command:
234 Ports for the DRM modules have been simplified. Now, amd64 users should
235 just install the drm-kmod port. All others should install
238 Graphics hardware that's newer than about 2010 usually works with
239 drm-kmod. For hardware older than 2013, however, some users will need
240 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
241 than 2008 usually only works in drm-legacy-kmod. The graphics team can
242 only commit to hardware made since 2013 due to the complexity of the
243 market and difficulty to test all the older cards effectively. If you
244 have hardware supported by drm-kmod, you are strongly encouraged to use
245 that as you will get better support.
247 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
248 elsewhere, the drm and drm2 modules will be eliminated from the src base
249 soon (with a limited exception for arm). Please update to the package
250 asap and report any issues to x11@freebsd.org.
252 Generally, anybody using the drm*-kmod packages should add
253 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
254 cross-threading surprises, especially with automatic driver
255 loading from X11 startup. These will become the defaults in 13-current
259 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
260 custom kernel and module loading configuration files must be updated
261 accordingly. Moreover, interfaces previous presented as ixlvN to the
262 system are now exposed as iavfN and network configuration files must
263 be adjusted as necessary.
266 OpenSSL has been updated to version 1.1.1. This update included
267 additional various API changes throughout the base system. It is
268 important to rebuild third-party software after upgrading. The value
269 of __FreeBSD_version has been bumped accordingly.
272 The legacy DRM modules and drivers have now been added to the loader's
273 module blacklist, in favor of loading them with kld_list in rc.conf(5).
274 The module blacklist may be overridden with the loader.conf(5)
275 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
279 The cam(4) based nda(4) driver will be used over nvd(4) by default on
280 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
281 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
282 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
286 Reproducible build mode is now on by default, in preparation for
287 FreeBSD 12.0. This eliminates build metadata such as the user,
288 host, and time from the kernel (and uname), unless the working tree
289 corresponds to a modified checkout from a version control system.
290 The previous behavior can be obtained by setting the /etc/src.conf
291 knob WITHOUT_REPRODUCIBLE_BUILD.
294 The Yarrow CSPRNG has been removed from the kernel as it has not been
295 supported by its designers since at least 2003. Fortuna has been the
296 default since FreeBSD-11.
299 devctl freeze/thaw have gone into the tree, the rc scripts have been
300 updated to use them and devmatch has been changed. You should update
301 kernel, userland and rc scripts all at the same time.
304 The default interpreter has been switched from 4th to Lua.
305 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
306 interpreter. If you have custom FORTH code you will need to set
307 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
308 src.conf for the build. This will create default hard links between
309 loader and loader_4th instead of loader and loader_lua, the new default.
310 If you are using UEFI it will create the proper hard link to loader.efi.
312 bhyve uses userboot.so. It remains 4th-only until some issues are solved
313 regarding coexisting with multiple versions of FreeBSD are resolved.
316 ls(1) now respects the COLORTERM environment variable used in other
317 systems and software to indicate that a colored terminal is both
318 supported and desired. If ls(1) is suddenly emitting colors, they may
319 be disabled again by either removing the unwanted COLORTERM from your
320 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
321 may not be observed in a future release.
324 The default pager for most commands has been changed to "less". To
325 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
329 The jedec_ts(4) driver has been removed. A superset of its functionality
330 is available in the jedec_dimm(4) driver, and the manpage for that
331 driver includes migration instructions. If you have "device jedec_ts"
332 in your kernel configuration file, it must be removed.
335 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
336 This should have no effect if the kernel is booted via BIOS/legacy boot.
337 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
338 has a buggy firmware that prevents a successful boot due to use of
342 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
343 support has been removed from the tree. These ports were
344 obsolete and/or known to be broken for many years.
347 loader.efi has been augmented to participate more fully in the
348 UEFI boot manager protocol. loader.efi will now look at the
349 BootXXXX environment variable to determine if a specific kernel
350 or root partition was specified. XXXX is derived from BootCurrent.
351 efibootmgr(8) manages these standard UEFI variables.
354 zfsloader's functionality has now been folded into loader.
355 zfsloader is no longer necessary once you've updated your
356 boot blocks. For a transition period, we will install a
357 hardlink for zfsloader to loader to allow a smooth transition
358 until the boot blocks can be updated (hard link because old
359 zfs boot blocks don't understand symlinks).
362 ARM64 now have efifb support, if you want to have serial console
363 on your arm64 board when an screen is connected and the bootloader
364 setup a frame buffer for us to use, just add :
368 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
369 an screen connected as the firmware will setup a frame buffer are that
370 u-boot will expose as an EFI frame buffer.
373 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
374 or take steps to update /etc/passwd before doing installworld on
375 existing systems. Do not skip the "mergemaster -Fp" step before
376 installworld, as described in the update procedures near the bottom
377 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
378 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
379 the ntp config file contain options that change file/dir locations.
380 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
381 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
382 taking steps to ensure that all required files/dirs are accessible
386 Big endian arm support has been removed.
389 The static environment setup in kernel configs is no longer mutually
390 exclusive with the loader(8) environment by default. In order to
391 restore the previous default behavior of disabling the loader(8)
392 environment if a static environment is present, you must specify
393 loader_env.disabled=1 in the static environment.
396 The ABI of syscalls used by management tools like sockstat and
397 netstat has been broken to allow 32-bit binaries to work on
398 64-bit kernels without modification. These programs will need
399 to match the kernel in order to function. External programs may
400 require minor modifications to accommodate a change of type in
401 structures from pointers to 64-bit virtual addresses.
404 On i386 and amd64 atomics are now inlined. Out of tree modules using
405 atomics will need to be rebuilt.
408 The '%I' format in the kern.corefile sysctl limits the number of
409 core files that a process can generate to the number stored in the
410 debug.ncores sysctl. The '%I' format is replaced by the single digit
411 index. Previously, if all indexes were taken the kernel would overwrite
412 only a core file with the highest index in a filename.
413 Currently the system will create a new core file if there is a free
414 index or if all slots are taken it will overwrite the oldest one.
417 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
418 6.0.1. Please see the 20141231 entry below for information about
419 prerequisites and upgrading, if you are not already using clang 3.5.0
423 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
424 needed to be changed to work with it. This change was made with r335763
425 and requires a mergemaster / etcupdate / etc to update the installed
429 r334930 changed the interface between the NFS modules, so they all
430 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
433 As of r334391 lld is the default amd64 system linker; it is installed
434 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
438 The kernel / userland interface for devinfo changed, so you'll
439 need a new kernel and userland as a pair for it to work (rebuilding
440 lib/libdevinfo is all that's required). devinfo and devmatch will
441 not work, but everything else will when there's a mismatch.
444 The on-disk format for hwpmc callchain records has changed to include
445 threadid corresponding to a given record. This changes the field offsets
446 and thus requires that libpmcstat be rebuilt before using a kernel
450 The vxge(4) driver has been removed. This driver was introduced into
451 HEAD one week before the Exar left the Ethernet market and is not
452 known to be used. If you have device vxge in your kernel config file
456 The amd64 kernel now requires a ld that supports ifunc to produce a
457 working kernel, either lld or a newer binutils. lld is built by default
458 on amd64, and the 'buildkernel' target uses it automatically. However,
459 it is not the default linker, so building the kernel the traditional
460 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
461 binutils port/package). lld will soon be default, and this requirement
464 NOTE: As of r334391 lld is the default system linker on amd64, and no
465 workaround is necessary.
468 The nxge(4) driver has been removed. This driver was for PCI-X 10g
469 cards made by s2io/Neterion. The company was acquired by Exar and
470 no longer sells or supports Ethernet products. If you have device
471 nxge in your kernel config file it must be removed.
474 The tz database (tzdb) has been updated to 2018e. This version more
475 correctly models time stamps in time zones with negative DST such as
476 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
477 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
478 time zone abbreviations and the tm_isdst flag.
481 The ixgb(4) driver has been removed. This driver was for an early and
482 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
483 quickly shifted to the long lived ixgbe family. If you have device
484 ixgb in your kernel config file it must be removed.
487 The lmc(4) driver has been removed. This was a WAN interface
488 card that was already reportedly rare in 2003, and had an ambiguous
489 license. If you have device lmc in your kernel config file it must
493 Support for Arcnet networks has been removed. If you have device
494 arcnet or device cm in your kernel config file they must be
498 Support for FDDI networks has been removed. If you have device
499 fddi or device fpa in your kernel config file they must be
503 In addition to supporting RFC 3164 formatted messages, the
504 syslogd(8) service is now capable of parsing RFC 5424 formatted
505 log messages. The main benefit of using RFC 5424 is that clients
506 may now send log messages with timestamps containing year numbers,
507 microseconds and time zone offsets.
509 Similarly, the syslog(3) C library function has been altered to
510 send RFC 5424 formatted messages to the local system logging
511 daemon. On systems using syslogd(8), this change should have no
512 negative impact, as long as syslogd(8) and the C library are
513 updated at the same time. On systems using a different system
514 logging daemon, it may be necessary to make configuration
515 adjustments, depending on the software used.
517 When using syslog-ng, add the 'syslog-protocol' flag to local
518 input sources to enable parsing of RFC 5424 formatted messages:
521 unix-dgram("/var/run/log" flags(syslog-protocol));
524 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
525 of the 'imuxsock' module to let messages be processed by the
526 regular RFC 3164/5424 parsing pipeline:
528 module(load="imuxsock" SysSock.UseSpecialParser="off")
530 Do note that these changes only affect communication between local
531 applications and syslogd(8). The format that syslogd(8) uses to
532 store messages on disk or forward messages to other systems
533 remains unchanged. syslogd(8) still uses RFC 3164 for these
534 purposes. Options to customize this behaviour will be added in the
535 future. Utilities that process log files stored in /var/log are
536 thus expected to continue to function as before.
538 __FreeBSD_version has been incremented to 1200061 to denote this
542 Support for token ring networks has been removed. If you
543 have "device token" in your kernel config you should remove
544 it. No device drivers supported token ring.
547 makefs was modified to be able to tag ISO9660 El Torito boot catalog
548 entries as EFI instead of overloading the i386 tag as done previously.
549 The amd64 mkisoimages.sh script used to build amd64 ISO images for
550 release was updated to use this. This may mean that makefs must be
551 updated before "make cdrom" can be run in the release directory. This
552 should be as simple as:
554 $ cd $SRCDIR/usr.sbin/makefs
555 $ make depend all install
558 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
559 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
560 Co-existence for the transition period will come shortly. Booting is a
561 complex environment and test coverage for Lua-enabled loaders has been
562 thin, so it would be prudent to assume it might not work and make
563 provisions for backup boot methods.
566 devmatch functionality has been turned on in devd. It will automatically
567 load drivers for unattached devices. This may cause unexpected drivers
568 to be loaded. Please report any problems to current@ and
572 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
573 6.0.0. Please see the 20141231 entry below for information about
574 prerequisites and upgrading, if you are not already using clang 3.5.0
578 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
579 This means it is used to link the kernel and userland libraries and
580 executables, but is not yet installed as /usr/bin/ld by default.
582 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
583 WITHOUT_LLD_BOOTSTRAP=yes
586 On i386, pmtimer has been removed. Its functionality has been folded
587 into apm. It was a no-op on ACPI in current for a while now (but was
588 still needed on i386 in FreeBSD 11 and earlier). Users may need to
589 remove it from kernel config files.
592 The use of RSS hash from the network card aka flowid has been
593 disabled by default for lagg(4) as it's currently incompatible with
594 the lacp and loadbalance protocols.
596 This can be re-enabled by setting the following in loader.conf:
597 net.link.lagg.default_use_flowid="1"
600 The SW_WATCHDOG option is no longer necessary to enable the
601 hardclock-based software watchdog if no hardware watchdog is
602 configured. As before, SW_WATCHDOG will cause the software
603 watchdog to be enabled even if a hardware watchdog is configured.
606 r326887 fixes the issue described in the 20171214 UPDATING entry.
607 r326888 flips the switch back to building GELI support always.
610 r362593 broke ZFS + GELI support for reasons unknown. However,
611 it also broke ZFS support generally, so GELI has been turned off
612 by default as the lesser evil in r326857. If you boot off ZFS and/or
613 GELI, it might not be a good time to update.
616 PowerPC users must update loader(8) by rebuilding world before
617 installing a new kernel, as the protocol connecting them has
618 changed. Without the update, loader metadata will not be passed
619 successfully to the kernel and users will have to enter their
620 root partition at the kernel mountroot prompt to continue booting.
621 Newer versions of loader can boot old kernels without issue.
624 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
625 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
626 to WITH/OUT_LOADER_GELI.
629 The naive and non-compliant support of posix_fallocate(2) in ZFS
630 has been removed as of r325320. The system call now returns EINVAL
631 when used on a ZFS file. Although the new behavior complies with the
632 standard, some consumers are not prepared to cope with it.
633 One known victim is lld prior to r325420.
636 Building in a FreeBSD src checkout will automatically create object
637 directories now rather than store files in the current directory if
638 'make obj' was not ran. Calling 'make obj' is no longer necessary.
639 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
640 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
644 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
645 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
646 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
647 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
648 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
649 The UNIFIED_OBJDIR option is a transitional feature that will be
650 removed for 12.0 release; please migrate to the new format for any
651 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
652 than hardcoding paths.
655 The native-xtools target no longer installs the files by default to the
656 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
657 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
660 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
661 options are changing from controlling the build if defined / undefined
662 to controlling the build with explicit 'yes' or 'no' values. They will
663 shift to WITH/WITHOUT options to match other options in the system.
666 libstand has turned into a private library for sys/boot use only.
667 It is no longer supported as a public interface outside of sys/boot.
670 The arm port has split armv6 into armv6 and armv7. armv7 is now
671 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
672 and are running a kernel from before r324363, you will need to add
673 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
676 When building multiple kernels using KERNCONF, non-existent KERNCONF
677 files will produce an error and buildkernel will fail. Previously
678 missing KERNCONF files silently failed giving no indication as to
679 why, only to subsequently discover during installkernel that the
680 desired kernel was never built in the first place.
683 The default serial number format for CTL LUNs has changed. This will
684 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
685 or iSCSI clients care about their LUNs' serial numbers. Users who
686 require serial number stability should hardcode serial numbers in
690 For 32-bit arm compiled for hard-float support, soft-floating point
691 binaries now always get their shared libraries from
692 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
693 /usr/libsoft also existed). Only users with a hard-float ld.so, but
694 soft-float everything else should be affected.
697 The geli password typed at boot is now hidden. To restore the previous
698 behavior, see geli(8) for configuration options.
701 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
702 sysctl values. Minor nit, but requires a rebuild of both world/kernel
706 "make check" behavior (made in ^/head@r295380) has been changed to
707 execute from a limited sandbox, as opposed to executing from
711 - The "beforecheck" and "aftercheck" targets are now specified.
712 - ${CHECKDIR} (added in commit noted above) has been removed.
713 - Legacy behavior can be enabled by setting
714 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
716 If the limited sandbox mode is enabled, "make check" will execute
717 "make distribution", then install, execute the tests, and clean up the
718 sandbox if successful.
720 The "make distribution" and "make install" targets are typically run as
721 root to set appropriate permissions and ownership at installation time.
722 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
723 environment if executing "make check" with limited sandbox mode using
724 an unprivileged user.
727 Since the switch to GPT disk labels, fsck for UFS/FFS has been
728 unable to automatically find alternate superblocks. As of r322297,
729 the information needed to find alternate superblocks has been
730 moved to the end of the area reserved for the boot block.
731 Filesystems created with a newfs of this vintage or later
732 will create the recovery information. If you have a filesystem
733 created prior to this change and wish to have a recovery block
734 created for your filesystem, you can do so by running fsck in
735 foreground mode (i.e., do not use the -p or -y options). As it
736 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
737 to which you should answer yes.
740 As of r321665, an NFSv4 server configuration that services
741 Kerberos mounts or clients that do not support the uid/gid in
742 owner/owner_group string capability, must explicitly enable
743 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
744 machine's /etc/rc.conf file.
747 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
748 Please see the 20141231 entry below for information about prerequisites
749 and upgrading, if you are not already using clang 3.5.0 or higher.
752 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
753 r-commands (rlogin, rsh, etc.) to be built with the base system.
756 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
757 a very major ABI incompatible change, so users of FreeBSD/powerpc must
758 be careful when performing source upgrades. It is best to run
759 'make installworld' from an alternate root system, either a live
760 CD/memory stick, or a temporary root partition. Additionally, all ports
761 must be recompiled. powerpc64 is largely unaffected, except in the case
762 of 32-bit compatibility. All 32-bit binaries will be affected.
765 Forward compatibility for the "ino64" project have been committed. This
766 will allow most new binaries to run on older kernels in a limited
767 fashion. This prevents many of the common foot-shooting actions in the
768 upgrade as well as the limited ability to roll back the kernel across
769 the ino64 upgrade. Complicated use cases may not work properly, though
770 enough simpler ones work to allow recovery in most situations.
773 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
774 if you require the GPL compiler.
777 The internal ABI used for communication between the NFS kernel modules
778 was changed by r320085, so __FreeBSD_version was bumped to
779 ensure all the NFS related modules are updated together.
782 The ABI of struct event was changed by extending the data
783 member to 64bit and adding ext fields. For upgrade, same
784 precautions as for the entry 20170523 "ino64" must be
788 The GNU roff toolchain has been removed from base. To render manpages
789 which are not supported by mandoc(1), man(1) can fallback on GNU roff
790 from ports (and recommends to install it).
791 To render roff(7) documents, consider using GNU roff from ports or the
792 heirloom doctools roff toolchain from ports via pkg install groff or
793 via pkg install heirloom-doctools.
796 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
797 smaller runtime footprint builds. This is useful for embedded systems
798 which only require one chipset support.
800 If you load it as a module, make sure this is in /boot/loader.conf:
804 This will load the HAL, all chip/RF backends and if_ath_pci.
805 If you have if_ath_pci in /boot/loader.conf, ensure it is after
806 if_ath or it will not load any HAL chipset support.
808 If you want to selectively load things (eg on ye cheape ARM/MIPS
809 platforms where RAM is at a premium) you should:
812 * load the chip modules in question
813 * load ath_rate, ath_dfs
815 * load if_ath_pci and/or if_ath_ahb depending upon your particular
816 bus bind type - this is where probe/attach is done.
818 For further comments/feedback, poke adrian@ .
821 The "ino64" 64-bit inode project has been committed, which extends
822 a number of types to 64 bits. Upgrading in place requires care and
823 adherence to the documented upgrade procedure.
825 If using a custom kernel configuration ensure that the
826 COMPAT_FREEBSD11 option is included (as during the upgrade the
827 system will be running the ino64 kernel with the existing world).
829 For the safest in-place upgrade begin by removing previous build
830 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
831 procedure documented below under the heading "To rebuild everything and
832 install it on the current system." Specifically, a reboot is required
833 after installing the new kernel before installing world. While an
834 installworld normally works by accident from multiuser after rebooting
835 the proper kernel, there are many cases where this will fail across this
836 upgrade and installworld from single user is required.
839 The NATM framework including the en(4), fatm(4), hatm(4), and
840 patm(4) devices has been removed. Consumers should plan a
841 migration before the end-of-life date for FreeBSD 11.
844 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
845 diff has not been implemented, if those are needed a newer version of
846 GNU diff is available via the diffutils package under the gdiff name.
849 As of r316810 for ipfilter, keep frags is no longer assumed when
850 keep state is specified in a rule. r316810 aligns ipfilter with
851 documentation in man pages separating keep frags from keep state.
852 This allows keep state to be specified without forcing keep frags
853 and allows keep frags to be specified independently of keep state.
854 To maintain previous behaviour, also specify keep frags with
855 keep state (as documented in ipf.conf.5).
858 arm64 builds now use the base system LLD 4.0.0 linker by default,
859 instead of requiring that the aarch64-binutils port or package be
860 installed. To continue using aarch64-binutils, set
861 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
864 The UDP optimization in entry 20160818 that added the sysctl
865 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
866 packets will no longer be treated as L3 broadcast packets.
869 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
870 use any explicitly assigned loopback address available in the jail
871 instead of using the first assigned address of the jail.
874 The ctl.ko module no longer implements the iSCSI target frontend:
875 cfiscsi.ko does instead.
877 If building cfiscsi.ko as a kernel module, the module can be loaded
878 via one of the following methods:
879 - `cfiscsi_load="YES"` in loader.conf(5).
880 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
881 - ctladm(8)/ctld(8), when compiled with iSCSI support
882 (`WITH_ISCSI=yes` in src.conf(5))
884 Please see cfiscsi(4) for more details.
887 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
888 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
889 same source (previously, the dependency of mmcsd.ko on mmc.ko was
890 missing, but mmcsd.ko now will refuse to load if it is incompatible
894 The syntax of ipfw(8) named states was changed to avoid ambiguity.
895 If you have used named states in the firewall rules, you need to modify
896 them after installworld and before rebooting. Now named states must
897 be prefixed with colon.
900 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
901 removed as the userland we provide cannot use them. The KMS version
902 (sys/dev/drm2) supports the same hardware.
905 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
906 Please see the 20141231 entry below for information about prerequisites
907 and upgrading, if you are not already using clang 3.5.0 or higher.
910 The code that provides support for ZFS .zfs/ directory functionality
911 has been reimplemented. It's not possible now to create a snapshot
912 by mkdir under .zfs/snapshot/. That should be the only user visible
916 EISA bus support has been removed. The WITH_EISA option is no longer
920 MCA bus support has been removed.
923 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
924 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
927 The EM_MULTIQUEUE kernel configuration option is deprecated now that
928 the em(4) driver conforms to iflib specifications.
931 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
932 IFLIB. If you have a custom kernel configuration that excludes em(4)
933 but you use igb(4), you need to re-add em(4) to your custom
937 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
938 Please see the 20141231 entry below for information about prerequisites
939 and upgrading, if you are not already using clang 3.5.0 or higher.
942 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
943 Please see the 20141231 entry below for information about prerequisites
944 and upgrading, if you are not already using clang 3.5.0 or higher.
947 The layout of the pmap structure has changed for powerpc to put the pmap
948 statistics at the front for all CPU variations. libkvm(3) and all tools
949 that link against it need to be recompiled.
952 isl(4) and cyapa(4) drivers now require a new driver,
953 chromebook_platform(4), to work properly on Chromebook-class hardware.
954 On other types of hardware the drivers may need to be configured using
955 device hints. Please see the corresponding manual pages for details.
958 The urtwn(4) driver was merged into rtwn(4) and now consists of
959 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
961 Also, firmware for RTL8188CE was renamed due to possible name
962 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
965 GNU rcs has been removed from base. It is available as packages:
966 - rcs: Latest GPLv3 GNU rcs version.
967 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
971 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
972 modules now requires that the kernel configuration contain the
973 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
976 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
977 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
980 Relocatable object files with the extension of .So have been renamed
981 to use an extension of .pico instead. The purpose of this change is
982 to avoid a name clash with shared libraries on case-insensitive file
983 systems. On those file systems, foo.So is the same file as foo.so.
986 GNU rcs has been turned off by default. It can (temporarily) be built
987 again by adding WITH_RCS knob in src.conf.
988 Otherwise, GNU rcs is available from packages:
989 - rcs: Latest GPLv3 GNU rcs version.
990 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
993 The backup_uses_rcs functionality has been removed from rc.subr.
996 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
997 two separate components, QUEUE_MACRO_DEBUG_TRACE and
998 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
999 QUEUE_MACRO_DEBUG behavior.
1002 r304787 changed some ioctl interfaces between the iSCSI userspace
1003 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1004 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1008 The UDP receive code has been updated to only treat incoming UDP
1009 packets that were addressed to an L2 broadcast address as L3
1010 broadcast packets. It is not expected that this will affect any
1011 standards-conforming UDP application. The new behaviour can be
1012 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1016 Remove the openbsd_poll system call.
1017 __FreeBSD_version has been bumped because of this.
1020 The stable/11 branch has been created from head@r302406.
1023 The libc stub for the pipe(2) system call has been replaced with
1024 a wrapper that calls the pipe2(2) system call and the pipe(2)
1025 system call is now only implemented by the kernels that include
1026 "options COMPAT_FREEBSD10" in their config file (this is the
1027 default). Users should ensure that this option is enabled in
1028 their kernel or upgrade userspace to r302092 before upgrading their
1032 CAM will now strip leading spaces from SCSI disks' serial numbers.
1033 This will affect users who create UFS filesystems on SCSI disks using
1034 those disk's diskid device nodes. For example, if /etc/fstab
1035 previously contained a line like
1036 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1037 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1038 transforms like gmirror may also be affected. ZFS users should
1042 The bitstring(3) API has been updated with new functionality and
1043 improved performance. But it is binary-incompatible with the old API.
1044 Objects built with the new headers may not be linked against objects
1045 built with the old headers.
1048 The brk and sbrk functions have been removed from libc on arm64.
1049 Binutils from ports has been updated to not link to these
1050 functions and should be updated to the latest version before
1051 installing a new libc.
1054 The armv6 port now defaults to hard float ABI. Limited support
1055 for running both hardfloat and soft float on the same system
1056 is available using the libraries installed with -DWITH_LIBSOFT.
1057 This has only been tested as an upgrade path for installworld
1058 and packages may fail or need manual intervention to run. New
1059 packages will be needed.
1061 To update an existing self-hosted armv6hf system, you must add
1062 TARGET_ARCH=armv6 on the make command line for both the build
1063 and the install steps.
1066 Kernel modules compiled outside of a kernel build now default to
1067 installing to /boot/modules instead of /boot/kernel. Many kernel
1068 modules built this way (such as those in ports) already overrode
1069 KMODDIR explicitly to install into /boot/modules. However,
1070 manually building and installing a module from /sys/modules will
1071 now install to /boot/modules instead of /boot/kernel.
1074 The CAM I/O scheduler has been committed to the kernel. There should be
1075 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1076 list of known rogues that claim support for this but actually corrupt
1077 data is believed to be complete, be on the lookout for data
1078 corruption. The known rogue list is believed to be complete:
1080 o Crucial MX100, M550 drives with MU01 firmware.
1081 o Micron M510 and M550 drives with MU01 firmware.
1082 o Micron M500 prior to MU07 firmware
1083 o Samsung 830, 840, and 850 all firmwares
1084 o FCCT M500 all firmwares
1086 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1087 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1088 updated firmware. Black listed drives will work correctly because these
1089 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1090 this list is the same as found in Linux, it's believed there are no
1091 other rogues in the market place. All other models from the above
1094 To be safe, if you are at all concerned, you can quirk each of your
1095 drives to prevent NCQ from being sent by setting:
1096 kern.cam.ada.X.quirks="0x2"
1097 in loader.conf. If the drive requires the 4k sector quirk, set the
1098 quirks entry to 0x3.
1101 The FAST_DEPEND build option has been removed and its functionality is
1102 now the one true way. The old mkdep(1) style of 'make depend' has
1103 been removed. See 20160311 for further details.
1106 Resource range types have grown from unsigned long to uintmax_t. All
1107 drivers, and anything using libdevinfo, need to be recompiled.
1110 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1111 builds. It no longer runs mkdep(1) during 'make depend', and the
1112 'make depend' stage can safely be skipped now as it is auto ran
1113 when building 'make all' and will generate all SRCS and DPSRCS before
1114 building anything else. Dependencies are gathered at compile time with
1115 -MF flags kept in separate .depend files per object file. Users should
1116 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1117 stale .depend files.
1120 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1121 kernel modules. Therefore, if you load any kernel modules at boot time,
1122 please install the boot loaders after you install the kernel, but before
1126 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1127 make installkernel KERNCONF=YOUR_KERNEL_HERE
1128 make -C sys/boot install
1129 <reboot in single user>
1131 Then follow the usual steps, described in the General Notes section,
1135 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1136 see the 20141231 entry below for information about prerequisites and
1137 upgrading, if you are not already using clang 3.5.0 or higher.
1140 The AIO subsystem is now a standard part of the kernel. The
1141 VFS_AIO kernel option and aio.ko kernel module have been removed.
1142 Due to stability concerns, asynchronous I/O requests are only
1143 permitted on sockets and raw disks by default. To enable
1144 asynchronous I/O requests on all file types, set the
1145 vfs.aio.enable_unsafe sysctl to a non-zero value.
1148 The ELF object manipulation tool objcopy is now provided by the
1149 ELF Tool Chain project rather than by GNU binutils. It should be a
1150 drop-in replacement, with the addition of arm64 support. The
1151 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1152 to obtain the GNU version if necessary.
1155 Building ZFS pools on top of zvols is prohibited by default. That
1156 feature has never worked safely; it's always been prone to deadlocks.
1157 Using a zvol as the backing store for a VM guest's virtual disk will
1158 still work, even if the guest is using ZFS. Legacy behavior can be
1159 restored by setting vfs.zfs.vol.recursive=1.
1162 The NONE and HPN patches has been removed from OpenSSH. They are
1163 still available in the security/openssh-portable port.
1166 With the addition of ypldap(8), a new _ypldap user is now required
1167 during installworld. "mergemaster -p" can be used to add the user
1168 prior to installworld, as documented in the handbook.
1171 The tftp loader (pxeboot) now uses the option root-path directive. As a
1172 consequence it no longer looks for a pxeboot.4th file on the tftp
1173 server. Instead it uses the regular /boot infrastructure as with the
1177 The code to start recording plug and play data into the modules has
1178 been committed. While the old tools will properly build a new kernel,
1179 a number of warnings about "unknown metadata record 4" will be produced
1180 for an older kldxref. To avoid such warnings, make sure to rebuild
1181 the kernel toolchain (or world). Make sure that you have r292078 or
1182 later when trying to build 292077 or later before rebuilding.
1185 Debug data files are now built by default with 'make buildworld' and
1186 installed with 'make installworld'. This facilitates debugging but
1187 requires more disk space both during the build and for the installed
1188 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1192 r291527 changed the internal interface between the nfsd.ko and
1193 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1194 __FreeBSD_version has been bumped because of this.
1197 Add support for unicode collation strings leads to a change of
1198 order of files listed by ls(1) for example. To get back to the old
1199 behaviour, set LC_COLLATE environment variable to "C".
1201 Databases administrators will need to reindex their databases given
1202 collation results will be different.
1204 Due to a bug in install(1) it is recommended to remove the ancient
1205 locales before running make installworld.
1207 rm -rf /usr/share/locale/*
1210 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1211 libcrypto.so.7 or libssl.so.7 must be recompiled.
1214 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1215 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1216 should be replaced with isp_2400 and isp_2500 modules respectively.
1219 The build previously allowed using 'make -n' to not recurse into
1220 sub-directories while showing what commands would be executed, and
1221 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1222 and 'make -N' will not.
1225 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1226 and etcupdate will now use this file. A custom sendmail.cf is now
1227 updated via this mechanism rather than via installworld. If you had
1228 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1229 want to remove the exclusion or change it to "always install".
1230 /etc/mail/sendmail.cf is now managed the same way regardless of
1231 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1232 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1235 Compatibility shims for legacy ATA device names have been removed.
1236 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1237 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1238 environment variables, /dev/ad* and /dev/ar* symbolic links.
1241 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1242 Please see the 20141231 entry below for information about prerequisites
1243 and upgrading, if you are not already using clang 3.5.0 or higher.
1246 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1247 and renamed from .symbols to .debug. This reduces the size requirements
1248 on the boot partition or file system and provides consistency with
1249 userland debug files.
1251 When using the supported kernel installation method the
1252 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1253 as is done with /boot/kernel.
1255 Developers wishing to maintain the historical behavior of installing
1256 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1259 The wireless drivers had undergone changes that remove the 'parent
1260 interface' from the ifconfig -l output. The rc.d network scripts
1261 used to check presence of a parent interface in the list, so old
1262 scripts would fail to start wireless networking. Thus, etcupdate(3)
1263 or mergemaster(8) run is required after kernel update, to update your
1264 rc.d scripts in /etc.
1267 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1268 These configurations are now automatically interpreted as
1269 'scrub fragment reassemble'.
1272 Kernel-loadable modules for the random(4) device are back. To use
1273 them, the kernel must have
1276 options RANDOM_LOADABLE
1278 kldload(8) can then be used to load random_fortuna.ko
1279 or random_yarrow.ko. Please note that due to the indirect
1280 function calls that the loadable modules need to provide,
1281 the build-in variants will be slightly more efficient.
1283 The random(4) kernel option RANDOM_DUMMY has been retired due to
1284 unpopularity. It was not all that useful anyway.
1287 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1288 Control over building the ELF Tool Chain tools is now provided by
1289 the WITHOUT_TOOLCHAIN knob.
1292 The polarity of Pulse Per Second (PPS) capture events with the
1293 uart(4) driver has been corrected. Prior to this change the PPS
1294 "assert" event corresponded to the trailing edge of a positive PPS
1295 pulse and the "clear" event was the leading edge of the next pulse.
1297 As the width of a PPS pulse in a typical GPS receiver is on the
1298 order of 1 millisecond, most users will not notice any significant
1299 difference with this change.
1301 Anyone who has compensated for the historical polarity reversal by
1302 configuring a negative offset equal to the pulse width will need to
1303 remove that workaround.
1306 The default group assigned to /dev/dri entries has been changed
1307 from 'wheel' to 'video' with the id of '44'. If you want to have
1308 access to the dri devices please add yourself to the video group
1311 # pw groupmod video -m $USER
1314 The menu.rc and loader.rc files will now be replaced during
1315 upgrades. Please migrate local changes to menu.rc.local and
1316 loader.rc.local instead.
1319 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1320 strings and strip have been removed. The src.conf(5) knob
1321 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1324 As ZFS requires more kernel stack pages than is the default on some
1325 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1326 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1328 Please consider using 'options KSTACK_PAGES=X' where X is greater
1329 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1332 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1333 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1334 default, i.e., they will not contain "::". For example, instead
1335 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1336 to have a more specific match, such as different map entries for
1337 IPv6:0:0 vs IPv6:0. This change requires that configuration
1338 data (including maps, files, classes, custom ruleset, etc.) must
1339 use the same format, so make certain such configuration data is
1340 upgrading. As a very simple check search for patterns like
1341 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1342 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1343 the cf option UseCompressedIPv6Addresses.
1346 The default kernel entropy-processing algorithm is now
1347 Fortuna, replacing Yarrow.
1349 Assuming you have 'device random' in your kernel config
1350 file, the configurations allow a kernel option to override
1351 this default. You may choose *ONE* of:
1353 options RANDOM_YARROW # Legacy /dev/random algorithm.
1354 options RANDOM_DUMMY # Blocking-only driver.
1356 If you have neither, you get Fortuna. For most people,
1357 read no further, Fortuna will give a /dev/random that works
1358 like it always used to, and the difference will be irrelevant.
1360 If you remove 'device random', you get *NO* kernel-processed
1361 entropy at all. This may be acceptable to folks building
1362 embedded systems, but has complications. Carry on reading,
1363 and it is assumed you know what you need.
1365 *PLEASE* read random(4) and random(9) if you are in the
1366 habit of tweaking kernel configs, and/or if you are a member
1367 of the embedded community, wanting specific and not-usual
1368 behaviour from your security subsystems.
1370 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1371 random', you will NOT have a functioning /dev/random, and
1372 many cryptographic features will not work, including SSH.
1373 You may also find strange behaviour from the random(3) set
1374 of library functions, in particular sranddev(3), srandomdev(3)
1375 and arc4random(3). The reason for this is that the KERN_ARND
1376 sysctl only returns entropy if it thinks it has some to
1377 share, and with RANDOM_DUMMY or no 'device random' this
1381 An additional fix for the issue described in the 20150614 sendmail
1382 entry below has been committed in revision 284717.
1385 FreeBSD's old make (fmake) has been removed from the system. It is
1386 available as the devel/fmake port or via pkg install fmake.
1389 The fix for the issue described in the 20150614 sendmail entry
1390 below has been committed in revision 284436. The work
1391 around described in that entry is no longer needed unless the
1392 default setting is overridden by a confDH_PARAMETERS configuration
1393 setting of '5' or pointing to a 512 bit DH parameter file.
1396 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1397 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1398 and devel/kyua to version 0.20+ and adjust any calling code to work
1399 with Kyuafile and kyua.
1402 The import of openssl to address the FreeBSD-SA-15:10.openssl
1403 security advisory includes a change which rejects handshakes
1404 with DH parameters below 768 bits. sendmail releases prior
1405 to 8.15.2 (not yet released), defaulted to a 512 bit
1406 DH parameter setting for client connections. To work around
1407 this interoperability, sendmail can be configured to use a
1408 2048 bit DH parameter by:
1410 1. Edit /etc/mail/`hostname`.mc
1411 2. If a setting for confDH_PARAMETERS does not exist or
1412 exists and is set to a string beginning with '5',
1413 replace it with '2'.
1414 3. If a setting for confDH_PARAMETERS exists and is set to
1415 a file path, create a new file with:
1416 openssl dhparam -out /path/to/file 2048
1417 4. Rebuild the .cf file:
1418 cd /etc/mail/; make; make install
1419 5. Restart sendmail:
1420 cd /etc/mail/; make restart
1422 A sendmail patch is coming, at which time this file will be
1426 Generation of legacy formatted entries have been disabled by default
1427 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1428 entries were converted to use the new format by default when the new,
1429 machine independent format have been added and supported since FreeBSD
1432 Please see the pwd_mkdb(8) manual page for further details.
1435 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1436 20141231 entry below for information about prerequisites and upgrading,
1437 if you are not already using 3.5.0 or higher.
1440 TI platform code switched to using vendor DTS files and this update
1441 may break existing systems running on Beaglebone, Beaglebone Black,
1444 - dtb files should be regenerated/reinstalled. Filenames are the
1445 same but content is different now
1446 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1447 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1448 addressing scheme is now pin 25 on /dev/gpioc3.
1449 - Pandaboard: /etc/ttys should be updated, serial console device is
1450 now /dev/ttyu2, not /dev/ttyu0
1453 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1454 If you need the GNU extension from groff soelim(1), install groff
1455 from package: pkg install groff, or via ports: textproc/groff.
1458 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1459 defined in symlink(7); previously symlinks were silently ignored.
1462 The const qualifier has been removed from iconv(3) to comply with
1463 POSIX. The ports tree is aware of this from r384038 onwards.
1466 Libraries specified by LIBADD in Makefiles must have a corresponding
1467 DPADD_<lib> variable to ensure correct dependencies. This is now
1468 enforced in src.libnames.mk.
1471 From legacy ata(4) driver was removed support for SATA controllers
1472 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1473 Kernel modules ataahci and ataadaptec were removed completely,
1474 replaced by ahci and mvs modules respectively.
1477 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1478 the 20141231 entry below for information about prerequisites and
1479 upgrading, if you are not already using 3.5.0 or higher.
1482 The 32-bit PowerPC kernel has been changed to a position-independent
1483 executable. This can only be booted with a version of loader(8)
1484 newer than January 31, 2015, so make sure to update both world and
1485 kernel before rebooting.
1488 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1489 but before r278950, the RNG was not seeded properly. Immediately
1490 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1491 ssh keys or openssl keys) that were generated w/ a kernel from that
1492 range. This does not affect programs that directly used /dev/random
1493 or /dev/urandom. All userland uses of arc4random(3) are affected.
1496 The autofs(4) ABI was changed in order to restore binary compatibility
1497 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1498 with the new kernel.
1501 The powerpc64 kernel has been changed to a position-independent
1502 executable. This can only be booted with a new version of loader(8),
1503 so make sure to update both world and kernel before rebooting.
1506 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1507 only release, no new features have been added. Please see the 20141231
1508 entry below for information about prerequisites and upgrading, if you
1509 are not already using 3.5.0.
1512 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1513 taken from the ELF Tool Chain project rather than GNU binutils. They
1514 should be drop-in replacements, with the addition of arm64 support.
1515 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1516 binutils tools, if necessary. See 20150805 for updated information.
1519 The default Unbound configuration now enables remote control
1520 using a local socket. Users who have already enabled the
1521 local_unbound service should regenerate their configuration
1522 by running "service local_unbound setup" as root.
1525 The GNU texinfo and GNU info pages have been removed.
1526 To be able to view GNU info pages please install texinfo from ports.
1529 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1531 As of this release, a prerequisite for building clang, llvm and lldb is
1532 a C++11 capable compiler and C++11 standard library. This means that to
1533 be able to successfully build the cross-tools stage of buildworld, with
1534 clang as the bootstrap compiler, your system compiler or cross compiler
1535 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1536 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1539 On any standard FreeBSD 10.x or 11.x installation, where clang and
1540 libc++ are on by default (that is, on x86 or arm), this should work out
1543 On 9.x installations where clang is enabled by default, e.g. on x86 and
1544 powerpc, libc++ will not be enabled by default, so libc++ should be
1545 built (with clang) and installed first. If both clang and libc++ are
1546 missing, build clang first, then use it to build libc++.
1548 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1549 the instructions for 9.x above.
1551 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1552 default, and do not build clang.
1554 Many embedded systems are resource constrained, and will not be able to
1555 build clang in a reasonable time, or in some cases at all. In those
1556 cases, cross building bootable systems on amd64 is a workaround.
1558 This new version of clang introduces a number of new warnings, of which
1559 the following are most likely to appear:
1563 This warns in two cases, for both C and C++:
1564 * When the code is trying to take the absolute value of an unsigned
1565 quantity, which is effectively a no-op, and almost never what was
1566 intended. The code should be fixed, if at all possible. If you are
1567 sure that the unsigned quantity can be safely cast to signed, without
1568 loss of information or undefined behavior, you can add an explicit
1569 cast, or disable the warning.
1571 * When the code is trying to take an absolute value, but the called
1572 abs() variant is for the wrong type, which can lead to truncation.
1573 If you want to disable the warning instead of fixing the code, please
1574 make sure that truncation will not occur, or it might lead to unwanted
1577 -Wtautological-undefined-compare and
1578 -Wundefined-bool-conversion
1580 These warn when C++ code is trying to compare 'this' against NULL, while
1581 'this' should never be NULL in well-defined C++ code. However, there is
1582 some legacy (pre C++11) code out there, which actively abuses this
1583 feature, which was less strictly defined in previous C++ versions.
1585 Squid and openjdk do this, for example. The warning can be turned off
1586 for C++98 and earlier, but compiling the code in C++11 mode might result
1587 in unexpected behavior; for example, the parts of the program that are
1588 unreachable could be optimized away.
1591 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1592 kernel sources have been removed. The .h files remain, since some
1593 utilities include them. This will need to be fixed later.
1594 If "mount -t oldnfs ..." is attempted, it will fail.
1595 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1596 the utilities will report errors.
1599 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1600 directories to top level SUBDIR variable when their parent
1601 directory is included in LOCAL_DIRS. Users with build systems with
1602 such hierarchies and without SUBDIR entries in the parent
1603 directory Makefiles should add them or add the directories to
1607 faith(4) and faithd(8) have been removed from the base system. Faith
1608 has been obsolete for a very long time.
1611 vt(4), the new console driver, is enabled by default. It brings
1612 support for Unicode and double-width characters, as well as
1613 support for UEFI and integration with the KMS kernel video
1616 You may need to update your console settings in /etc/rc.conf,
1617 most probably the keymap. During boot, /etc/rc.d/syscons will
1618 indicate what you need to do.
1620 vt(4) still has issues and lacks some features compared to
1621 syscons(4). See the wiki for up-to-date information:
1622 https://wiki.freebsd.org/Newcons
1624 If you want to keep using syscons(4), you can do so by adding
1625 the following line to /boot/loader.conf:
1629 pjdfstest has been integrated into kyua as an opt-in test suite.
1630 Please see share/doc/pjdfstest/README for more details on how to
1634 gperf has been removed from the base system for architectures
1635 that use clang. Ports that require gperf will obtain it from the
1639 pjdfstest has been moved from tools/regression/pjdfstest to
1643 At svn r271982, The default linux compat kernel ABI has been adjusted
1644 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1645 update. If you wish to continue using the linux-f10 compat ports,
1646 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1647 encouraged to update their linux-compat packages to linux-c6 during
1648 their next update cycle.
1651 The ofwfb driver, used to provide a graphics console on PowerPC when
1652 using vt(4), no longer allows mmap() of all physical memory. This
1653 will prevent Xorg on PowerPC with some ATI graphics cards from
1654 initializing properly unless x11-servers/xorg-server is updated to
1658 The xdev targets have been converted to using TARGET and
1659 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1662 The default unbound configuration has been modified to address
1663 issues with reverse lookups on networks that use private
1664 address ranges. If you use the local_unbound service, run
1665 "service local_unbound setup" as root to regenerate your
1666 configuration, then "service local_unbound reload" to load the
1670 The GNU texinfo and GNU info pages are not built and installed
1671 anymore, WITH_INFO knob has been added to allow to built and install
1673 UPDATE: see 20150102 entry on texinfo's removal
1676 The GNU readline library is now an INTERNALLIB - that is, it is
1677 statically linked into consumers (GDB and variants) in the base
1678 system, and the shared library is no longer installed. The
1679 devel/readline port is available for third party software that
1683 The Itanium architecture (ia64) has been removed from the list of
1684 known architectures. This is the first step in the removal of the
1688 Commit r268115 has added NFSv4.1 server support, merged from
1689 projects/nfsv4.1-server. Since this includes changes to the
1690 internal interfaces between the NFS related modules, a full
1691 build of the kernel and modules will be necessary.
1692 __FreeBSD_version has been bumped.
1695 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1696 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1697 which differs from the behaviour controlled by this knob.)
1700 Maximal length of the serial number in CTL was increased from 16 to
1701 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1702 and ctld, need to be rebuilt to work with a new kernel.
1705 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1706 1 respectively to match the upstream numbers. They were out of
1707 sync because, when they were originally added to FreeBSD, the
1708 upstream versions were not respected. These libraries are private
1709 and not yet built by default, so renumbering them should be a
1710 non-issue. However, unclean source trees will yield broken test
1711 programs once the operator executes "make delete-old-libs" after a
1712 "make installworld".
1714 Additionally, the atf-sh binary was made private by moving it into
1715 /usr/libexec/. Already-built shell test programs will keep the
1716 path to the old binary so they will break after "make delete-old"
1719 If you are using WITH_TESTS=yes (not the default), wipe the object
1720 tree and rebuild from scratch to prevent spurious test failures.
1721 This is only needed once: the misnumbered libraries and misplaced
1722 binaries have been added to OptionalObsoleteFiles.inc so they will
1723 be removed during a clean upgrade.
1726 Clang and llvm have been upgraded to 3.4.1 release.
1729 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1730 be removed to avoid issues in the future (and has been added to
1734 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1735 past, it affected all builds that used the bsd.*.mk files. The old
1736 behavior was a bug, but people may have relied upon it. To get this
1737 behavior back, you can .include /etc/src.conf from /etc/make.conf
1738 (which is still global and isn't changed). This also changes the
1739 behavior of incremental builds inside the tree of individual
1740 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1741 Although this has survived make universe and some upgrade scenarios,
1742 other upgrade scenarios may have broken. At least one form of
1743 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1744 as well... In cases where MAKESYSPATH isn't working with this
1745 setting, you'll need to set it to the full path to your tree.
1747 One side effect of all this cleaning up is that bsd.compiler.mk
1748 is no longer implicitly included by bsd.own.mk. If you wish to
1749 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1753 The lindev device has been removed since /dev/full has been made a
1754 standard device. __FreeBSD_version has been bumped.
1757 The knob WITHOUT_VI was added to the base system, which controls
1758 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1759 in order to reorder files share/termcap and didn't build ex(1) as a
1760 build tool, so building/installing with WITH_VI is highly advised for
1761 build hosts for older releases.
1763 This issue has been fixed in stable/9 and stable/10 in r277022 and
1764 r276991, respectively.
1767 The YES_HESIOD knob has been removed. It has been obsolete for
1768 a decade. Please move to using WITH_HESIOD instead or your builds
1769 will silently lack HESIOD.
1772 The uart(4) driver has been changed with respect to its handling
1773 of the low-level console. Previously the uart(4) driver prevented
1774 any process from changing the baudrate or the CLOCAL and HUPCL
1775 control flags. By removing the restrictions, operators can make
1776 changes to the serial console port without having to reboot.
1777 However, when getty(8) is started on the serial device that is
1778 associated with the low-level console, a misconfigured terminal
1779 line in /etc/ttys will now have a real impact.
1780 Before upgrading the kernel, make sure that /etc/ttys has the
1781 serial console device configured as 3wire without baudrate to
1782 preserve the previous behaviour. E.g:
1783 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1786 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1787 to improve performance. To re-enable it, if needed, run rpcbind
1788 with command line option -W.
1791 Switched back to the GPL dtc compiler due to updates in the upstream
1792 dts files not being supported by the BSDL dtc compiler. You will need
1793 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1794 may result while building dtb files during a kernel build if you fail
1795 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1798 Clang and llvm have been upgraded to 3.4 release.
1801 The nve(4) driver has been removed. Please use the nfe(4) driver
1802 for NVIDIA nForce MCP Ethernet adapters instead.
1805 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1806 This could cause certain C++ applications using shared libraries built
1807 against the previous version of libc++ to crash. The incompatibility
1808 has now been fixed, but any C++ applications or shared libraries built
1809 between r261283 and r261801 should be recompiled.
1812 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1813 capability mode support. Please note that enabling the feature in
1814 kernel is still highly recommended.
1817 OpenSSH is now built with sandbox support, and will use sandbox as
1818 the default privilege separation method. This requires Capsicum
1819 capability mode support in kernel.
1822 The libelf and libdwarf libraries have been updated to newer
1823 versions from upstream. Shared library version numbers for
1824 these two libraries were bumped. Any ports or binaries
1825 requiring these two libraries should be recompiled.
1826 __FreeBSD_version is bumped to 1100006.
1829 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1830 instead of providing an explicit one, this would prevent such
1831 Makefile from providing its own Kyuafile in the future during
1832 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1833 intervention is needed to clean an objdir if you use NO_CLEAN:
1834 # find /usr/obj -name Kyuafile | xargs rm -f
1837 The behavior of gss_pseudo_random() for the krb5 mechanism
1838 has changed, for applications requesting a longer random string
1839 than produced by the underlying enctype's pseudo-random() function.
1840 In particular, the random string produced from a session key of
1841 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1842 be different at the 17th octet and later, after this change.
1843 The counter used in the PRF+ construction is now encoded as a
1844 big-endian integer in accordance with RFC 4402.
1845 __FreeBSD_version is bumped to 1100004.
1848 The WITHOUT_ATF build knob has been removed and its functionality
1849 has been subsumed into the more generic WITHOUT_TESTS. If you were
1850 using the former to disable the build of the ATF libraries, you
1851 should change your settings to use the latter.
1854 The default version of mtree is nmtree which is obtained from
1855 NetBSD. The output is generally the same, but may vary
1856 slightly. If you found you need identical output adding
1857 "-F freebsd9" to the command line should do the trick. For the
1858 time being, the old mtree is available as fmtree.
1861 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1862 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1863 1.1.4_8 and verify bsdyml not linked in, before running "make
1865 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1867 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1870 The stable/10 branch has been created in subversion from head
1877 Avoid using make -j when upgrading. While generally safe, there are
1878 sometimes problems using -j to upgrade. If your upgrade fails with
1879 -j, please try again without -j. From time to time in the past there
1880 have been problems using -j with buildworld and/or installworld. This
1881 is especially true when upgrading between "distant" versions (eg one
1882 that cross a major release boundary or several minor releases, or when
1883 several months have passed on the -current branch).
1885 Sometimes, obscure build problems are the result of environment
1886 poisoning. This can happen because the make utility reads its
1887 environment when searching for values for global variables. To run
1888 your build attempts in an "environmental clean room", prefix all make
1889 commands with 'env -i '. See the env(1) manual page for more details.
1891 When upgrading from one major version to another it is generally best to
1892 upgrade to the latest code in the currently installed branch first, then
1893 do an upgrade to the new branch. This is the best-tested upgrade path,
1894 and has the highest probability of being successful. Please try this
1895 approach if you encounter problems with a major version upgrade. Since
1896 the stable 4.x branch point, one has generally been able to upgrade from
1897 anywhere in the most recent stable branch to head / current (or even the
1898 last couple of stable branches). See the top of this file when there's
1901 When upgrading a live system, having a root shell around before
1902 installing anything can help undo problems. Not having a root shell
1903 around can lead to problems if pam has changed too much from your
1904 starting point to allow continued authentication after the upgrade.
1906 This file should be read as a log of events. When a later event changes
1907 information of a prior event, the prior event should not be deleted.
1908 Instead, a pointer to the entry with the new information should be
1909 placed in the old entry. Readers of this file should also sanity check
1910 older entries before relying on them blindly. Authors of new entries
1911 should write them with this in mind.
1915 When upgrading the boot ZFS pool to a new version, always follow
1918 1.) recompile and reinstall the ZFS boot loader and boot block
1919 (this is part of "make buildworld" and "make installworld")
1921 2.) update the ZFS boot block on your boot drive
1923 The following example updates the ZFS boot block on the first
1924 partition (freebsd-boot) of a GPT partitioned drive ada0:
1925 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1927 Non-boot pools do not need these updates.
1931 If you are updating from a prior version of FreeBSD (even one just
1932 a few days old), you should follow this procedure. It is the most
1933 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1935 make kernel-toolchain
1936 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1937 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1939 To test a kernel once
1940 ---------------------
1941 If you just want to boot a kernel once (because you are not sure
1942 if it works, or if you want to boot a known bad kernel to provide
1943 debugging information) run
1944 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1945 nextboot -k testkernel
1947 To rebuild everything and install it on the current system.
1948 -----------------------------------------------------------
1949 # Note: sometimes if you are running current you gotta do more than
1950 # is listed here if you are upgrading from a really old current.
1952 <make sure you have good level 0 dumps>
1954 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1955 make installkernel KERNCONF=YOUR_KERNEL_HERE
1957 <reboot in single user> [3]
1964 To cross-install current onto a separate partition
1965 --------------------------------------------------
1966 # In this approach we use a separate partition to hold
1967 # current's root, 'usr', and 'var' directories. A partition
1968 # holding "/", "/usr" and "/var" should be about 2GB in
1971 <make sure you have good level 0 dumps>
1974 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1975 <maybe newfs current's root partition>
1976 <mount current's root partition on directory ${CURRENT_ROOT}>
1977 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1978 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1979 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1980 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1981 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1982 <reboot into current>
1983 <do a "native" rebuild/install as described in the previous section>
1984 <maybe install compatibility libraries from ports/misc/compat*>
1988 To upgrade in-place from stable to current
1989 ----------------------------------------------
1990 <make sure you have good level 0 dumps>
1992 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1993 make installkernel KERNCONF=YOUR_KERNEL_HERE
1995 <reboot in single user> [3]
2002 Make sure that you've read the UPDATING file to understand the
2003 tweaks to various things you need. At this point in the life
2004 cycle of current, things change often and you are on your own
2005 to cope. The defaults can also change, so please read ALL of
2006 the UPDATING entries.
2008 Also, if you are tracking -current, you must be subscribed to
2009 freebsd-current@freebsd.org. Make sure that before you update
2010 your sources that you have read and understood all the recent
2011 messages there. If in doubt, please track -stable which has
2012 much fewer pitfalls.
2014 [1] If you have third party modules, such as vmware, you
2015 should disable them at this point so they don't crash your
2018 [3] From the bootblocks, boot -s, and then do
2022 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2023 cd src # full path to source
2024 adjkerntz -i # if CMOS is wall time
2025 Also, when doing a major release upgrade, it is required that
2026 you boot into single user mode to do the installworld.
2028 [4] Note: This step is non-optional. Failure to do this step
2029 can result in a significant reduction in the functionality of the
2030 system. Attempting to do it by hand is not recommended and those
2031 that pursue this avenue should read this file carefully, as well
2032 as the archives of freebsd-current and freebsd-hackers mailing lists
2033 for potential gotchas. The -U option is also useful to consider.
2034 See mergemaster(8) for more information.
2036 [5] Usually this step is a no-op. However, from time to time
2037 you may need to do this if you get unknown user in the following
2038 step. It never hurts to do it all the time. You may need to
2039 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2040 install) after the buildworld before this step if you last updated
2041 from current before 20130425 or from -stable before 20130430.
2043 [6] This only deletes old files and directories. Old libraries
2044 can be deleted by "make delete-old-libs", but you have to make
2045 sure that no program is using those libraries anymore.
2047 [8] The new kernel must be able to run existing binaries used by an
2048 installworld. When upgrading across major versions, the new kernel's
2049 configuration must include the correct COMPAT_FREEBSD<n> option for
2050 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2051 to do so may leave you with a system that is hard to boot to recover. A
2052 GENERIC kernel will include suitable compatibility options to run
2053 binaries from older branches. Note that the ability to run binaries
2054 from unsupported branches is not guaranteed.
2056 Make sure that you merge any new devices from GENERIC since the
2057 last time you updated your kernel config file. Options also
2058 change over time, so you may need to adjust your custom kernels
2061 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2062 "?=" instead of the "=" assignment operator, so that buildworld can
2063 override the CPUTYPE if it needs to.
2065 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2066 not on the command line, or in /etc/make.conf. buildworld will
2067 warn if it is improperly defined.
2070 This file contains a list, in reverse chronological order, of major
2071 breakages in tracking -current. It is not guaranteed to be a complete
2072 list of such breakages, and only contains entries since September 23, 2011.
2073 If you need to see UPDATING entries from before that date, you will need
2074 to fetch an UPDATING file from an older FreeBSD release.
2076 Copyright information:
2078 Copyright 1998-2009 M. Warner Losh.
2080 Redistribution, publication, translation and use, with or without
2081 modification, in full or in part, in any form or format of this
2082 document are permitted without further permission from the author.
2084 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2085 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2086 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2087 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2088 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2089 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2090 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2091 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2092 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2093 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2094 POSSIBILITY OF SUCH DAMAGE.
2096 Contact Warner Losh if you have any questions about your use of