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: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 20200915 p10 FreeBSD-SA-20:27.ure
20 FreeBSD-SA-20:28.bhyve_vmcs
21 FreeBSD-SA-20:29.bhyve_svm
24 Fix ure device driver susceptible to packet-in-packet attack.
27 Fix bhyve privilege escalation via VMCS access. [SA-20:28.bhyve_vmcs]
29 Fix bhyve SVM guest escape. [SA-20:29.bhyve_svm]
31 Fix ftpd privilege escalation via ftpchroot. [SA-20:30.ftpd]
33 20200902 p9 FreeBSD-EN-20:17.linuxthread
35 FreeBSD-SA-20:26.dhclient
37 Fix FreeBSD Linux ABI kernel panic. [EN-20:17.linuxthread]
39 Fix SCTP socket use-after-free. [SA-20:25.sctp]
41 Fix dhclient heap overflow. [SA-20:26.dhclient]
43 20200805 p8 FreeBSD-EN-20:16.vmx
44 FreeBSD-SA-20:21.usb_net
45 FreeBSD-SA-20:22.unbound
48 Fix vmx driver packet loss and degraded performance. [EN-20:16.vmx]
50 Fix memory corruption in USB network device drivers. [SA-20:21.usb_net]
52 Fix multiple vulnerabilities in sqlite3. [SA-20:22.sqlite]
54 Fix sendmsg(2) privilege escalation. [SA-20:23.sendmsg]
56 20200708 p7 FreeBSD-EN-20:13.bhyve
57 FreeBSD-EN-20:14.linuxkpi
59 FreeBSD-SA-20:19.unbound
62 Fix host crash in bhyve with PCI device passthrough. [EN-20:13.bhyve]
64 Fix kernel panic in LinuxKPI subsystem. [EN-20:14.linuxpki]
66 Fix kernel panic in mps(4) driver. [EN-20:15.mps]
68 Fix multiple vulnerabilities in unbound. [SA-20:19.unbound]
70 Fix IPv6 socket option race condition and use after free. [SA-20:20.ipv6]
72 20200609 p6 FreeBSD-EN-20:11.ena
73 FreeBSD-EN-20:12.iflib
76 Fix stability issues in ena(4) driver. [EN-20:11.ena]
78 Fix iflib watchdog timeout resetting idle queues. [EN-20:12.iflib]
80 Fix USB HID descriptor parsing error. [SA-20:17.usb]
82 20200512 p5 FreeBSD-EN-20:08.tzdata
84 FreeBSD-EN-20:10.build
85 FreeBSD-SA-20:12.libalias
86 FreeBSD-SA-20:13.libalias
87 FreeBSD-SA-20:15.cryptodev
88 FreeBSD-SA-20:16.cryptodev
90 Import tzdata 2020a. [EN-20:08.tzdata]
92 Fix igb interfaces failing to switch to inactive state [EN-20:09.igb]
94 Fix incorrect build host Clang version detection [EN-20:10.build]
96 Fix insufficient packet length validation in libalias [SA-20:12.libalias]
98 Fix memory disclosure vulnerability in libalias [SA-20:13.libalias]
100 Fix use after free in cryptodev module [SA-20:15.cryptodev]
102 Fix insufficient cryptodev MAC key length check [SA-20:16.cryptodev]
104 20200421 p4 FreeBSD-EN-20:07.quotad
105 FreeBSD-SA-20:10.ipfw
106 FreeBSD-SA-20:11.openssl
108 Fix regression in rpc.rquotad with certain NFS servers [EN-20:07.quotad]
110 Fix ipfw invalid mbuf handling [SA-20:10.ipfw]
112 Fix OpenSSL remote denial of service vulnerability [SA-20:11.openssl]
114 20200319 p3 FreeBSD-EN-20:03.sshd
115 FreeBSD-EN-20:05.mlx5en
116 FreeBSD-EN-20:06.ipv6
118 FreeBSD-SA-20:05.if_oce_ioctl
119 FreeBSD-SA-20:06.if_ixl_ioctl
120 FreeBSD-SA-20:07.epair
121 FreeBSD-SA-20:08.jail
124 Fix misleading log messages upon successful sshd login [EN-20:03.sshd]
126 Fix packet forwarding performance in mlx5en(4) driver [EN-20:05.mlx5en]
128 Fix incorrect checksum calculations with IPv6 extension headers [EN-20:06.ipv6]
130 Fix TCP IPv6 SYN cache kernel information disclosure [SA-20:04.tcp]
132 Fix insufficient oce(4) ioctl(2) privilege checking [SA-20:05.if_oce_ioctl]
134 Fix insufficient ixl(4) ioctl(2) privilege checking [SA-20:06.if_ixl_ioctl]
136 Fix incorrect user-controlled pointer use in epair [SA-20:07.epair]
138 Fix kernel memory disclosure with nested jails [SA-20:08.jail]
140 Fix multiple denial of service in ntpd [SA-20:09.ntp]
142 20200128 p2 FreeBSD-EN-20:01.ssp
143 FreeBSD-SA-20:01.libfetch
144 FreeBSD-SA-20:03.thrmisc
146 Fix imprecise ordering of SSP canary initialization [EN-20:01.ssp]
148 Fix libfetch buffer overflow [SA-20:01.libfetch]
150 Fix kernel stack data disclosure [SA-20:03.thrmisc]
152 20191112 p1 FreeBSD-EN-19:19.loader
153 FreeBSD-SA-19:25.mcepsc
155 Fix UEFI Loader Memory Fragmentation [EN-19:19.loader]
157 Fix Machine Check Exception on Page Size Change [SA-19:25.mcepsc]
163 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
164 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
165 been removed from mount_fusefs(8). You can safely remove them from
166 your scripts, because they had no effect.
168 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
169 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
170 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
171 sysctls have been removed. If you felt the need to set any of them to
172 a non-default value, please tell asomers@FreeBSD.org why.
175 The fuse(4) module has been renamed to fusefs(4) for consistency with
176 other filesystems. You should update any kld_load="fuse" entries in
177 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
178 "options FUSE" enties in kernel config files.
181 Default permissions on the /var/account/acct file (and copies of it
182 rotated by periodic daily scripts) are changed from 0644 to 0640
183 because the file contains sensitive information that should not be
184 world-readable. If the /var/account directory must be created by
185 rc.d/accounting, the mode used is now 0750. Admins who use the
186 accounting feature are encouraged to change the mode of an existing
187 /var/account directory to 0750 or 0700.
190 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
191 been upgraded to 8.0.1. Please see the 20141231 entry below for
192 information about prerequisites and upgrading, if you are not already
193 using clang 3.5.0 or higher.
196 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
197 functionality needed for the RETPOLINE option should work properly
198 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
201 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
202 8.0.0. Please see the 20141231 entry below for information about
203 prerequisites and upgrading, if you are not already using clang 3.5.0
207 The RETPOLINE option produces non-functional ifunc-using binaries
208 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
209 Once Clang 8 is merged it may be enabled again.
212 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
213 7.0.1. Please see the 20141231 entry below for information about
214 prerequisites and upgrading, if you are not already using clang 3.5.0
218 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
219 compiled into your custom kernel, add 'device xz' statement to the
223 Iflib is no longer unconditionally compiled into the kernel. Drivers
224 using iflib and statically compiled into the kernel, now require
225 the 'device iflib' config option. For the same drivers loaded as
226 modules on kernels not having 'device iflib', the iflib.ko module
227 is loaded automatically.
230 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
231 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
232 servers that have vfs.nfsd.nfs_privport set will only allow mounts
233 from clients using a reserved port#. Since both the FreeBSD and Linux
234 NFSv4 clients use reserved port#s by default, this should not affect
238 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
239 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
240 it produces broken binaries when ifuncs are in use. Users needing
241 GNU ld should install the binutils port or package.
244 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
245 has been converted to a port (misc/ctm) and will be removed from
246 FreeBSD-13. A depreciation warning will be printed to stderr by
247 the ctm command, but the functionality will remain in base for all
251 The stable/12 branch has been created in subversion from head
255 Ports for the DRM modules have been simplified. Now, amd64 users should
256 just install the drm-kmod port. All others should install
259 Graphics hardware that's newer than about 2010 usually works with
260 drm-kmod. For hardware older than 2013, however, some users will need
261 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
262 than 2008 usually only works in drm-legacy-kmod. The graphics team can
263 only commit to hardware made since 2013 due to the complexity of the
264 market and difficulty to test all the older cards effectively. If you
265 have hardware supported by drm-kmod, you are strongly encouraged to use
266 that as you will get better support.
268 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
269 elsewhere, the drm and drm2 modules will be eliminated from the src base
270 soon (with a limited exception for arm). Please update to the package asap
271 and report any issues to x11@freebsd.org.
273 Generally, anybody using the drm*-kmod packages should add
274 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
275 cross-threading surprises, especially with automatic driver
276 loading from X11 startup. These will become the defaults in 13-current
280 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
281 custom kernel and module loading configuration files must be updated
282 accordingly. Moreover, interfaces previous presented as ixlvN to the
283 system are now exposed as iavfN and network configuration files must
284 be adjusted as necessary.
287 OpenSSL has been updated to version 1.1.1. This update included
288 additional various API changes througout the base system. It is
289 important to rebuild third-party software after upgrading. The value
290 of __FreeBSD_version has been bumped accordingly.
293 The legacy DRM modules and drivers have now been added to the loader's
294 module blacklist, in favor of loading them with kld_list in rc.conf(5).
295 The module blacklist may be overridden with the loader.conf(5)
296 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
300 The cam(4) based nda(4) driver will be used over nvd(4) by default on
301 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
302 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
303 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
307 Reproducible build mode is now on by default, in preparation for
308 FreeBSD 12.0. This eliminates build metadata such as the user,
309 host, and time from the kernel (and uname), unless the working tree
310 corresponds to a modified checkout from a version control system.
311 The previous behavior can be obtained by setting the /etc/src.conf
312 knob WITHOUT_REPRODUCIBLE_BUILD.
315 The Yarrow CSPRNG has been removed from the kernel as it has not been
316 supported by its designers since at least 2003. Fortuna has been the
317 default since FreeBSD-11.
320 devctl freeze/thaw have gone into the tree, the rc scripts have been
321 updated to use them and devmatch has been changed. You should update
322 kernel, userland and rc scripts all at the same time.
325 The default interpreter has been switched from 4th to Lua.
326 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
327 interpreter. If you have custom FORTH code you will need to set
328 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
329 src.conf for the build. This will create default hard links between
330 loader and loader_4th instead of loader and loader_lua, the new default.
331 If you are using UEFI it will create the proper hard link to loader.efi.
333 bhyve uses userboot.so. It remains 4th-only until some issues are solved
334 regarding coexisting with multiple versions of FreeBSD are resolved.
337 ls(1) now respects the COLORTERM environment variable used in other
338 systems and software to indicate that a colored terminal is both
339 supported and desired. If ls(1) is suddenly emitting colors, they may
340 be disabled again by either removing the unwanted COLORTERM from your
341 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
342 may not be observed in a future release.
345 The default pager for most commands has been changed to "less". To
346 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
350 The jedec_ts(4) driver has been removed. A superset of its functionality
351 is available in the jedec_dimm(4) driver, and the manpage for that
352 driver includes migration instructions. If you have "device jedec_ts"
353 in your kernel configuration file, it must be removed.
356 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
357 This should have no effect if the kernel is booted via BIOS/legacy boot.
358 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
359 has a buggy firmware that prevents a successful boot due to use of
363 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
364 support has been removed from the tree. These ports were
365 obsolete and/or known to be broken for many years.
368 loader.efi has been augmented to participate more fully in the
369 UEFI boot manager protocol. loader.efi will now look at the
370 BootXXXX environment variable to determine if a specific kernel
371 or root partition was specified. XXXX is derived from BootCurrent.
372 efibootmgr(8) manages these standard UEFI variables.
375 zfsloader's functionality has now been folded into loader.
376 zfsloader is no longer necessary once you've updated your
377 boot blocks. For a transition period, we will install a
378 hardlink for zfsloader to loader to allow a smooth transition
379 until the boot blocks can be updated (hard link because old
380 zfs boot blocks don't understand symlinks).
383 ARM64 now have efifb support, if you want to have serial console
384 on your arm64 board when an screen is connected and the bootloader
385 setup a frambuffer for us to use, just add :
389 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
390 an screen connected as the firmware will setup a framebuffer are that
391 u-boot will expose as an EFI framebuffer.
394 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
395 or take steps to update /etc/passwd before doing installworld on
396 existing systems. Do not skip the "mergemaster -Fp" step before
397 installworld, as described in the update procedures near the bottom
398 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
399 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
400 the ntp config file contain options that change file/dir locations.
401 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
402 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
403 taking steps to ensure that all required files/dirs are accessible
407 Big endian arm support has been removed.
410 The static environment setup in kernel configs is no longer mutually
411 exclusive with the loader(8) environment by default. In order to
412 restore the previous default behavior of disabling the loader(8)
413 environment if a static environment is present, you must specify
414 loader_env.disabled=1 in the static environment.
417 The ABI of syscalls used by management tools like sockstat and
418 netstat has been broken to allow 32-bit binaries to work on
419 64-bit kernels without modification. These programs will need
420 to match the kernel in order to function. External programs may
421 require minor modifications to accommodate a change of type in
422 structures from pointers to 64-bit virtual addresses.
425 On i386 and amd64 atomics are now inlined. Out of tree modules using
426 atomics will need to be rebuilt.
429 The '%I' format in the kern.corefile sysctl limits the number of
430 core files that a process can generate to the number stored in the
431 debug.ncores sysctl. The '%I' format is replaced by the single digit
432 index. Previously, if all indexes were taken the kernel would overwrite
433 only a core file with the highest index in a filename.
434 Currently the system will create a new core file if there is a free
435 index or if all slots are taken it will overwrite the oldest one.
438 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
439 6.0.1. Please see the 20141231 entry below for information about
440 prerequisites and upgrading, if you are not already using clang 3.5.0
444 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
445 needed to be changed to work with it. This change was made with r335763
446 and requires a mergemaster / etcupdate / etc to update the installed file.
449 r334930 changed the interface between the NFS modules, so they all
450 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
453 As of r334391 lld is the default amd64 system linker; it is installed
454 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
458 The kernel / userland interface for devinfo changed, so you'll
459 need a new kernel and userland as a pair for it to work (rebuilding
460 lib/libdevinfo is all that's required). devinfo and devmatch will
461 not work, but everything else will when there's a mismatch.
464 The on-disk format for hwpmc callchain records has changed to include
465 threadid corresponding to a given record. This changes the field offsets
466 and thus requires that libpmcstat be rebuilt before using a kernel
470 The vxge(4) driver has been removed. This driver was introduced into
471 HEAD one week before the Exar left the Ethernet market and is not
472 known to be used. If you have device vxge in your kernel config file
476 The amd64 kernel now requires a ld that supports ifunc to produce a
477 working kernel, either lld or a newer binutils. lld is built by default
478 on amd64, and the 'buildkernel' target uses it automatically. However,
479 it is not the default linker, so building the kernel the traditional
480 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
481 binutils port/package). lld will soon be default, and this requirement
484 NOTE: As of r334391 lld is the default system linker on amd64, and no
485 workaround is necessary.
488 The nxge(4) driver has been removed. This driver was for PCI-X 10g
489 cards made by s2io/Neterion. The company was aquired by Exar and
490 no longer sells or supports Ethernet products. If you have device
491 nxge in your kernel config file it must be removed.
494 The tz database (tzdb) has been updated to 2018e. This version more
495 correctly models time stamps in time zones with negative DST such as
496 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
497 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
498 time zone abbreviations and the tm_isdst flag.
501 The ixgb(4) driver has been removed. This driver was for an early and
502 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
503 quickly shifted to the long lived ixgbe family. If you have device
504 ixgb in your kernel config file it must be removed.
507 The lmc(4) driver has been removed. This was a WAN interface
508 card that was already reportedly rare in 2003, and had an ambiguous
509 license. If you have device lmc in your kernel config file it must
513 Support for Arcnet networks has been removed. If you have device
514 arcnet or device cm in your kernel config file they must be
518 Support for FDDI networks has been removed. If you have device
519 fddi or device fpa in your kernel config file they must be
523 In addition to supporting RFC 3164 formatted messages, the
524 syslogd(8) service is now capable of parsing RFC 5424 formatted
525 log messages. The main benefit of using RFC 5424 is that clients
526 may now send log messages with timestamps containing year numbers,
527 microseconds and time zone offsets.
529 Similarly, the syslog(3) C library function has been altered to
530 send RFC 5424 formatted messages to the local system logging
531 daemon. On systems using syslogd(8), this change should have no
532 negative impact, as long as syslogd(8) and the C library are
533 updated at the same time. On systems using a different system
534 logging daemon, it may be necessary to make configuration
535 adjustments, depending on the software used.
537 When using syslog-ng, add the 'syslog-protocol' flag to local
538 input sources to enable parsing of RFC 5424 formatted messages:
541 unix-dgram("/var/run/log" flags(syslog-protocol));
544 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
545 of the 'imuxsock' module to let messages be processed by the
546 regular RFC 3164/5424 parsing pipeline:
548 module(load="imuxsock" SysSock.UseSpecialParser="off")
550 Do note that these changes only affect communication between local
551 applications and syslogd(8). The format that syslogd(8) uses to
552 store messages on disk or forward messages to other systems
553 remains unchanged. syslogd(8) still uses RFC 3164 for these
554 purposes. Options to customize this behaviour will be added in the
555 future. Utilities that process log files stored in /var/log are
556 thus expected to continue to function as before.
558 __FreeBSD_version has been incremented to 1200061 to denote this
562 Support for token ring networks has been removed. If you
563 have "device token" in your kernel config you should remove
564 it. No device drivers supported token ring.
567 makefs was modified to be able to tag ISO9660 El Torito boot catalog
568 entries as EFI instead of overloading the i386 tag as done previously.
569 The amd64 mkisoimages.sh script used to build amd64 ISO images for
570 release was updated to use this. This may mean that makefs must be
571 updated before "make cdrom" can be run in the release directory. This
572 should be as simple as:
574 $ cd $SRCDIR/usr.sbin/makefs
575 $ make depend all install
578 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
579 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
580 Co-existance for the transition period will come shortly. Booting is a
581 complex environment and test coverage for Lua-enabled loaders has been
582 thin, so it would be prudent to assume it might not work and make
583 provisions for backup boot methods.
586 devmatch functionality has been turned on in devd. It will automatically
587 load drivers for unattached devices. This may cause unexpected drivers to
588 be loaded. Please report any problems to current@ and imp@freebsd.org.
591 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
592 6.0.0. Please see the 20141231 entry below for information about
593 prerequisites and upgrading, if you are not already using clang 3.5.0
597 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
598 This means it is used to link the kernel and userland libraries and
599 executables, but is not yet installed as /usr/bin/ld by default.
601 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
602 WITHOUT_LLD_BOOTSTRAP=yes
605 On i386, pmtimer has been removed. Its functionality has been folded
606 into apm. It was a no-op on ACPI in current for a while now (but was still
607 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
608 from kernel config files.
611 The use of RSS hash from the network card aka flowid has been
612 disabled by default for lagg(4) as it's currently incompatible with
613 the lacp and loadbalance protocols.
615 This can be re-enabled by setting the following in loader.conf:
616 net.link.lagg.default_use_flowid="1"
619 The SW_WATCHDOG option is no longer necessary to enable the
620 hardclock-based software watchdog if no hardware watchdog is
621 configured. As before, SW_WATCHDOG will cause the software
622 watchdog to be enabled even if a hardware watchdog is configured.
625 r326887 fixes the issue described in the 20171214 UPDATING entry.
626 r326888 flips the switch back to building GELI support always.
629 r362593 broke ZFS + GELI support for reasons unknown. However,
630 it also broke ZFS support generally, so GELI has been turned off
631 by default as the lesser evil in r326857. If you boot off ZFS and/or
632 GELI, it might not be a good time to update.
635 PowerPC users must update loader(8) by rebuilding world before
636 installing a new kernel, as the protocol connecting them has
637 changed. Without the update, loader metadata will not be passed
638 successfully to the kernel and users will have to enter their
639 root partition at the kernel mountroot prompt to continue booting.
640 Newer versions of loader can boot old kernels without issue.
643 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
644 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
645 to WITH/OUT_LOADER_GELI.
648 The naive and non-compliant support of posix_fallocate(2) in ZFS
649 has been removed as of r325320. The system call now returns EINVAL
650 when used on a ZFS file. Although the new behavior complies with the
651 standard, some consumers are not prepared to cope with it.
652 One known victim is lld prior to r325420.
655 Building in a FreeBSD src checkout will automatically create object
656 directories now rather than store files in the current directory if
657 'make obj' was not ran. Calling 'make obj' is no longer necessary.
658 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
659 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
663 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
664 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
665 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
666 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
667 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
668 The UNIFIED_OBJDIR option is a transitional feature that will be
669 removed for 12.0 release; please migrate to the new format for any
670 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
671 than hardcoding paths.
674 The native-xtools target no longer installs the files by default to the
675 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
676 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
679 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
680 options are changing from controlling the build if defined / undefined
681 to controlling the build with explicit 'yes' or 'no' values. They will
682 shift to WITH/WITHOUT options to match other options in the system.
685 libstand has turned into a private library for sys/boot use only.
686 It is no longer supported as a public interface outside of sys/boot.
689 The arm port has split armv6 into armv6 and armv7. armv7 is now
690 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
691 and are running a kernel from before r324363, you will need to add
692 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
695 When building multiple kernels using KERNCONF, non-existent KERNCONF
696 files will produce an error and buildkernel will fail. Previously
697 missing KERNCONF files silently failed giving no indication as to
698 why, only to subsequently discover during installkernel that the
699 desired kernel was never built in the first place.
702 The default serial number format for CTL LUNs has changed. This will
703 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
704 or iSCSI clients care about their LUNs' serial numbers. Users who
705 require serial number stability should hardcode serial numbers in
709 For 32-bit arm compiled for hard-float support, soft-floating point
710 binaries now always get their shared libraries from
711 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
712 /usr/libsoft also existed). Only users with a hard-float ld.so, but
713 soft-float everything else should be affected.
716 The geli password typed at boot is now hidden. To restore the previous
717 behavior, see geli(8) for configuration options.
720 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
721 sysctl values. Minor nit, but requires a rebuild of both world/kernel
725 "make check" behavior (made in ^/head@r295380) has been changed to
726 execute from a limited sandbox, as opposed to executing from
730 - The "beforecheck" and "aftercheck" targets are now specified.
731 - ${CHECKDIR} (added in commit noted above) has been removed.
732 - Legacy behavior can be enabled by setting
733 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
735 If the limited sandbox mode is enabled, "make check" will execute
736 "make distribution", then install, execute the tests, and clean up the
737 sandbox if successful.
739 The "make distribution" and "make install" targets are typically run as
740 root to set appropriate permissions and ownership at installation time.
741 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
742 environment if executing "make check" with limited sandbox mode using
743 an unprivileged user.
746 Since the switch to GPT disk labels, fsck for UFS/FFS has been
747 unable to automatically find alternate superblocks. As of r322297,
748 the information needed to find alternate superblocks has been
749 moved to the end of the area reserved for the boot block.
750 Filesystems created with a newfs of this vintage or later
751 will create the recovery information. If you have a filesystem
752 created prior to this change and wish to have a recovery block
753 created for your filesystem, you can do so by running fsck in
754 foreground mode (i.e., do not use the -p or -y options). As it
755 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
756 to which you should answer yes.
759 As of r321665, an NFSv4 server configuration that services
760 Kerberos mounts or clients that do not support the uid/gid in
761 owner/owner_group string capability, must explicitly enable
762 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
763 machine's /etc/rc.conf file.
766 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
767 Please see the 20141231 entry below for information about prerequisites
768 and upgrading, if you are not already using clang 3.5.0 or higher.
771 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
772 r-commands (rlogin, rsh, etc.) to be built with the base system.
775 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
776 a very major ABI incompatible change, so users of FreeBSD/powerpc must
777 be careful when performing source upgrades. It is best to run
778 'make installworld' from an alternate root system, either a live
779 CD/memory stick, or a temporary root partition. Additionally, all ports
780 must be recompiled. powerpc64 is largely unaffected, except in the case
781 of 32-bit compatibility. All 32-bit binaries will be affected.
784 Forward compatibility for the "ino64" project have been committed. This
785 will allow most new binaries to run on older kernels in a limited
786 fashion. This prevents many of the common foot-shooting actions in the
787 upgrade as well as the limited ability to roll back the kernel across
788 the ino64 upgrade. Complicated use cases may not work properly, though
789 enough simpler ones work to allow recovery in most situations.
792 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
793 if you require the GPL compiler.
796 The internal ABI used for communication between the NFS kernel modules
797 was changed by r320085, so __FreeBSD_version was bumped to
798 ensure all the NFS related modules are updated together.
801 The ABI of struct event was changed by extending the data
802 member to 64bit and adding ext fields. For upgrade, same
803 precautions as for the entry 20170523 "ino64" must be
807 The GNU roff toolchain has been removed from base. To render manpages
808 which are not supported by mandoc(1), man(1) can fallback on GNU roff
809 from ports (and recommends to install it).
810 To render roff(7) documents, consider using GNU roff from ports or the
811 heirloom doctools roff toolchain from ports via pkg install groff or
812 via pkg install heirloom-doctools.
815 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
816 smaller runtime footprint builds. This is useful for embedded systems
817 which only require one chipset support.
819 If you load it as a module, make sure this is in /boot/loader.conf:
823 This will load the HAL, all chip/RF backends and if_ath_pci.
824 If you have if_ath_pci in /boot/loader.conf, ensure it is after
825 if_ath or it will not load any HAL chipset support.
827 If you want to selectively load things (eg on ye cheape ARM/MIPS
828 platforms where RAM is at a premium) you should:
831 * load the chip modules in question
832 * load ath_rate, ath_dfs
834 * load if_ath_pci and/or if_ath_ahb depending upon your particular
835 bus bind type - this is where probe/attach is done.
837 For further comments/feedback, poke adrian@ .
840 The "ino64" 64-bit inode project has been committed, which extends
841 a number of types to 64 bits. Upgrading in place requires care and
842 adherence to the documented upgrade procedure.
844 If using a custom kernel configuration ensure that the
845 COMPAT_FREEBSD11 option is included (as during the upgrade the
846 system will be running the ino64 kernel with the existing world).
848 For the safest in-place upgrade begin by removing previous build
849 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
850 full procedure documented below under the heading "To rebuild
851 everything and install it on the current system." Specifically,
852 a reboot is required after installing the new kernel before
856 The NATM framework including the en(4), fatm(4), hatm(4), and
857 patm(4) devices has been removed. Consumers should plan a
858 migration before the end-of-life date for FreeBSD 11.
861 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
862 diff has not been implemented, if those are needed a newer version of
863 GNU diff is available via the diffutils package under the gdiff name.
866 As of r316810 for ipfilter, keep frags is no longer assumed when
867 keep state is specified in a rule. r316810 aligns ipfilter with
868 documentation in man pages separating keep frags from keep state.
869 This allows keep state to be specified without forcing keep frags
870 and allows keep frags to be specified independently of keep state.
871 To maintain previous behaviour, also specify keep frags with
872 keep state (as documented in ipf.conf.5).
875 arm64 builds now use the base system LLD 4.0.0 linker by default,
876 instead of requiring that the aarch64-binutils port or package be
877 installed. To continue using aarch64-binutils, set
878 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
881 The UDP optimization in entry 20160818 that added the sysctl
882 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
883 packets will no longer be treated as L3 broadcast packets.
886 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
887 use any explicitly assigned loopback address available in the jail
888 instead of using the first assigned address of the jail.
891 The ctl.ko module no longer implements the iSCSI target frontend:
892 cfiscsi.ko does instead.
894 If building cfiscsi.ko as a kernel module, the module can be loaded
895 via one of the following methods:
896 - `cfiscsi_load="YES"` in loader.conf(5).
897 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
898 - ctladm(8)/ctld(8), when compiled with iSCSI support
899 (`WITH_ISCSI=yes` in src.conf(5))
901 Please see cfiscsi(4) for more details.
904 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
905 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
906 same source (previously, the dependency of mmcsd.ko on mmc.ko was
907 missing, but mmcsd.ko now will refuse to load if it is incompatible
911 The syntax of ipfw(8) named states was changed to avoid ambiguity.
912 If you have used named states in the firewall rules, you need to modify
913 them after installworld and before rebooting. Now named states must
914 be prefixed with colon.
917 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
918 removed as the userland we provide cannot use them. The KMS version
919 (sys/dev/drm2) supports the same hardware.
922 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
923 Please see the 20141231 entry below for information about prerequisites
924 and upgrading, if you are not already using clang 3.5.0 or higher.
927 The code that provides support for ZFS .zfs/ directory functionality
928 has been reimplemented. It's not possible now to create a snapshot
929 by mkdir under .zfs/snapshot/. That should be the only user visible
933 EISA bus support has been removed. The WITH_EISA option is no longer
937 MCA bus support has been removed.
940 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
941 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
944 The EM_MULTIQUEUE kernel configuration option is deprecated now that
945 the em(4) driver conforms to iflib specifications.
948 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
949 IFLIB. If you have a custom kernel configuration that excludes em(4)
950 but you use igb(4), you need to re-add em(4) to your custom configuration.
953 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
954 Please see the 20141231 entry below for information about prerequisites
955 and upgrading, if you are not already using clang 3.5.0 or higher.
958 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.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 layout of the pmap structure has changed for powerpc to put the pmap
964 statistics at the front for all CPU variations. libkvm(3) and all tools
965 that link against it need to be recompiled.
968 isl(4) and cyapa(4) drivers now require a new driver,
969 chromebook_platform(4), to work properly on Chromebook-class hardware.
970 On other types of hardware the drivers may need to be configured using
971 device hints. Please see the corresponding manual pages for details.
974 The urtwn(4) driver was merged into rtwn(4) and now consists of
975 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
977 Also, firmware for RTL8188CE was renamed due to possible name
978 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
981 GNU rcs has been removed from base. It is available as packages:
982 - rcs: Latest GPLv3 GNU rcs version.
983 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
987 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
988 modules now requires that the kernel configuration contain the
989 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
992 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
993 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
996 Relocatable object files with the extension of .So have been renamed
997 to use an extension of .pico instead. The purpose of this change is
998 to avoid a name clash with shared libraries on case-insensitive file
999 systems. On those file systems, foo.So is the same file as foo.so.
1002 GNU rcs has been turned off by default. It can (temporarily) be built
1003 again by adding WITH_RCS knob in src.conf.
1004 Otherwise, GNU rcs is available from packages:
1005 - rcs: Latest GPLv3 GNU rcs version.
1006 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1009 The backup_uses_rcs functionality has been removed from rc.subr.
1012 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1013 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1014 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1015 QUEUE_MACRO_DEBUG behavior.
1018 r304787 changed some ioctl interfaces between the iSCSI userspace
1019 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1020 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1024 The UDP receive code has been updated to only treat incoming UDP
1025 packets that were addressed to an L2 broadcast address as L3
1026 broadcast packets. It is not expected that this will affect any
1027 standards-conforming UDP application. The new behaviour can be
1028 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1032 Remove the openbsd_poll system call.
1033 __FreeBSD_version has been bumped because of this.
1036 The stable/11 branch has been created from head@r302406.
1039 The libc stub for the pipe(2) system call has been replaced with
1040 a wrapper that calls the pipe2(2) system call and the pipe(2)
1041 system call is now only implemented by the kernels that include
1042 "options COMPAT_FREEBSD10" in their config file (this is the
1043 default). Users should ensure that this option is enabled in
1044 their kernel or upgrade userspace to r302092 before upgrading their
1048 CAM will now strip leading spaces from SCSI disks' serial numbers.
1049 This will affect users who create UFS filesystems on SCSI disks using
1050 those disk's diskid device nodes. For example, if /etc/fstab
1051 previously contained a line like
1052 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1053 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1054 transforms like gmirror may also be affected. ZFS users should
1058 The bitstring(3) API has been updated with new functionality and
1059 improved performance. But it is binary-incompatible with the old API.
1060 Objects built with the new headers may not be linked against objects
1061 built with the old headers.
1064 The brk and sbrk functions have been removed from libc on arm64.
1065 Binutils from ports has been updated to not link to these
1066 functions and should be updated to the latest version before
1067 installing a new libc.
1070 The armv6 port now defaults to hard float ABI. Limited support
1071 for running both hardfloat and soft float on the same system
1072 is available using the libraries installed with -DWITH_LIBSOFT.
1073 This has only been tested as an upgrade path for installworld
1074 and packages may fail or need manual intervention to run. New
1075 packages will be needed.
1077 To update an existing self-hosted armv6hf system, you must add
1078 TARGET_ARCH=armv6 on the make command line for both the build
1079 and the install steps.
1082 Kernel modules compiled outside of a kernel build now default to
1083 installing to /boot/modules instead of /boot/kernel. Many kernel
1084 modules built this way (such as those in ports) already overrode
1085 KMODDIR explicitly to install into /boot/modules. However,
1086 manually building and installing a module from /sys/modules will
1087 now install to /boot/modules instead of /boot/kernel.
1090 The CAM I/O scheduler has been committed to the kernel. There should be
1091 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1092 list of known rogues that claim support for this but actually corrupt
1093 data is believed to be complete, be on the lookout for data
1094 corruption. The known rogue list is believed to be complete:
1096 o Crucial MX100, M550 drives with MU01 firmware.
1097 o Micron M510 and M550 drives with MU01 firmware.
1098 o Micron M500 prior to MU07 firmware
1099 o Samsung 830, 840, and 850 all firmwares
1100 o FCCT M500 all firmwares
1102 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1103 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1104 updated firmware. Black listed drives will work correctly because these
1105 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1106 this list is the same as found in Linux, it's believed there are no
1107 other rogues in the market place. All other models from the above
1110 To be safe, if you are at all concerned, you can quirk each of your
1111 drives to prevent NCQ from being sent by setting:
1112 kern.cam.ada.X.quirks="0x2"
1113 in loader.conf. If the drive requires the 4k sector quirk, set the
1114 quirks entry to 0x3.
1117 The FAST_DEPEND build option has been removed and its functionality is
1118 now the one true way. The old mkdep(1) style of 'make depend' has
1119 been removed. See 20160311 for further details.
1122 Resource range types have grown from unsigned long to uintmax_t. All
1123 drivers, and anything using libdevinfo, need to be recompiled.
1126 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1127 builds. It no longer runs mkdep(1) during 'make depend', and the
1128 'make depend' stage can safely be skipped now as it is auto ran
1129 when building 'make all' and will generate all SRCS and DPSRCS before
1130 building anything else. Dependencies are gathered at compile time with
1131 -MF flags kept in separate .depend files per object file. Users should
1132 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1133 stale .depend files.
1136 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1137 kernel modules. Therefore, if you load any kernel modules at boot time,
1138 please install the boot loaders after you install the kernel, but before
1142 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1143 make installkernel KERNCONF=YOUR_KERNEL_HERE
1144 make -C sys/boot install
1145 <reboot in single user>
1147 Then follow the usual steps, described in the General Notes section,
1151 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1152 see the 20141231 entry below for information about prerequisites and
1153 upgrading, if you are not already using clang 3.5.0 or higher.
1156 The AIO subsystem is now a standard part of the kernel. The
1157 VFS_AIO kernel option and aio.ko kernel module have been removed.
1158 Due to stability concerns, asynchronous I/O requests are only
1159 permitted on sockets and raw disks by default. To enable
1160 asynchronous I/O requests on all file types, set the
1161 vfs.aio.enable_unsafe sysctl to a non-zero value.
1164 The ELF object manipulation tool objcopy is now provided by the
1165 ELF Tool Chain project rather than by GNU binutils. It should be a
1166 drop-in replacement, with the addition of arm64 support. The
1167 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1168 to obtain the GNU version if necessary.
1171 Building ZFS pools on top of zvols is prohibited by default. That
1172 feature has never worked safely; it's always been prone to deadlocks.
1173 Using a zvol as the backing store for a VM guest's virtual disk will
1174 still work, even if the guest is using ZFS. Legacy behavior can be
1175 restored by setting vfs.zfs.vol.recursive=1.
1178 The NONE and HPN patches has been removed from OpenSSH. They are
1179 still available in the security/openssh-portable port.
1182 With the addition of ypldap(8), a new _ypldap user is now required
1183 during installworld. "mergemaster -p" can be used to add the user
1184 prior to installworld, as documented in the handbook.
1187 The tftp loader (pxeboot) now uses the option root-path directive. As a
1188 consequence it no longer looks for a pxeboot.4th file on the tftp
1189 server. Instead it uses the regular /boot infrastructure as with the
1193 The code to start recording plug and play data into the modules has
1194 been committed. While the old tools will properly build a new kernel,
1195 a number of warnings about "unknown metadata record 4" will be produced
1196 for an older kldxref. To avoid such warnings, make sure to rebuild
1197 the kernel toolchain (or world). Make sure that you have r292078 or
1198 later when trying to build 292077 or later before rebuilding.
1201 Debug data files are now built by default with 'make buildworld' and
1202 installed with 'make installworld'. This facilitates debugging but
1203 requires more disk space both during the build and for the installed
1204 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1208 r291527 changed the internal interface between the nfsd.ko and
1209 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1210 __FreeBSD_version has been bumped because of this.
1213 Add support for unicode collation strings leads to a change of
1214 order of files listed by ls(1) for example. To get back to the old
1215 behaviour, set LC_COLLATE environment variable to "C".
1217 Databases administrators will need to reindex their databases given
1218 collation results will be different.
1220 Due to a bug in install(1) it is recommended to remove the ancient
1221 locales before running make installworld.
1223 rm -rf /usr/share/locale/*
1226 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1227 libcrypto.so.7 or libssl.so.7 must be recompiled.
1230 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1231 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1232 should be replaced with isp_2400 and isp_2500 modules respectively.
1235 The build previously allowed using 'make -n' to not recurse into
1236 sub-directories while showing what commands would be executed, and
1237 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1238 and 'make -N' will not.
1241 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1242 and etcupdate will now use this file. A custom sendmail.cf is now
1243 updated via this mechanism rather than via installworld. If you had
1244 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1245 want to remove the exclusion or change it to "always install".
1246 /etc/mail/sendmail.cf is now managed the same way regardless of
1247 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1248 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1251 Compatibility shims for legacy ATA device names have been removed.
1252 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1253 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1254 environment variables, /dev/ad* and /dev/ar* symbolic links.
1257 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1258 Please see the 20141231 entry below for information about prerequisites
1259 and upgrading, if you are not already using clang 3.5.0 or higher.
1262 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1263 and renamed from .symbols to .debug. This reduces the size requirements
1264 on the boot partition or file system and provides consistency with
1265 userland debug files.
1267 When using the supported kernel installation method the
1268 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1269 as is done with /boot/kernel.
1271 Developers wishing to maintain the historical behavior of installing
1272 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1275 The wireless drivers had undergone changes that remove the 'parent
1276 interface' from the ifconfig -l output. The rc.d network scripts
1277 used to check presence of a parent interface in the list, so old
1278 scripts would fail to start wireless networking. Thus, etcupdate(3)
1279 or mergemaster(8) run is required after kernel update, to update your
1280 rc.d scripts in /etc.
1283 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1284 These configurations are now automatically interpreted as
1285 'scrub fragment reassemble'.
1288 Kernel-loadable modules for the random(4) device are back. To use
1289 them, the kernel must have
1292 options RANDOM_LOADABLE
1294 kldload(8) can then be used to load random_fortuna.ko
1295 or random_yarrow.ko. Please note that due to the indirect
1296 function calls that the loadable modules need to provide,
1297 the build-in variants will be slightly more efficient.
1299 The random(4) kernel option RANDOM_DUMMY has been retired due to
1300 unpopularity. It was not all that useful anyway.
1303 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1304 Control over building the ELF Tool Chain tools is now provided by
1305 the WITHOUT_TOOLCHAIN knob.
1308 The polarity of Pulse Per Second (PPS) capture events with the
1309 uart(4) driver has been corrected. Prior to this change the PPS
1310 "assert" event corresponded to the trailing edge of a positive PPS
1311 pulse and the "clear" event was the leading edge of the next pulse.
1313 As the width of a PPS pulse in a typical GPS receiver is on the
1314 order of 1 millisecond, most users will not notice any significant
1315 difference with this change.
1317 Anyone who has compensated for the historical polarity reversal by
1318 configuring a negative offset equal to the pulse width will need to
1319 remove that workaround.
1322 The default group assigned to /dev/dri entries has been changed
1323 from 'wheel' to 'video' with the id of '44'. If you want to have
1324 access to the dri devices please add yourself to the video group
1327 # pw groupmod video -m $USER
1330 The menu.rc and loader.rc files will now be replaced during
1331 upgrades. Please migrate local changes to menu.rc.local and
1332 loader.rc.local instead.
1335 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1336 strings and strip have been removed. The src.conf(5) knob
1337 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1340 As ZFS requires more kernel stack pages than is the default on some
1341 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1342 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1344 Please consider using 'options KSTACK_PAGES=X' where X is greater
1345 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1348 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1349 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1350 default, i.e., they will not contain "::". For example, instead
1351 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1352 to have a more specific match, such as different map entries for
1353 IPv6:0:0 vs IPv6:0. This change requires that configuration
1354 data (including maps, files, classes, custom ruleset, etc.) must
1355 use the same format, so make certain such configuration data is
1356 upgrading. As a very simple check search for patterns like
1357 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1358 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1359 the cf option UseCompressedIPv6Addresses.
1362 The default kernel entropy-processing algorithm is now
1363 Fortuna, replacing Yarrow.
1365 Assuming you have 'device random' in your kernel config
1366 file, the configurations allow a kernel option to override
1367 this default. You may choose *ONE* of:
1369 options RANDOM_YARROW # Legacy /dev/random algorithm.
1370 options RANDOM_DUMMY # Blocking-only driver.
1372 If you have neither, you get Fortuna. For most people,
1373 read no further, Fortuna will give a /dev/random that works
1374 like it always used to, and the difference will be irrelevant.
1376 If you remove 'device random', you get *NO* kernel-processed
1377 entropy at all. This may be acceptable to folks building
1378 embedded systems, but has complications. Carry on reading,
1379 and it is assumed you know what you need.
1381 *PLEASE* read random(4) and random(9) if you are in the
1382 habit of tweaking kernel configs, and/or if you are a member
1383 of the embedded community, wanting specific and not-usual
1384 behaviour from your security subsystems.
1386 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1387 random', you will NOT have a functioning /dev/random, and
1388 many cryptographic features will not work, including SSH.
1389 You may also find strange behaviour from the random(3) set
1390 of library functions, in particular sranddev(3), srandomdev(3)
1391 and arc4random(3). The reason for this is that the KERN_ARND
1392 sysctl only returns entropy if it thinks it has some to
1393 share, and with RANDOM_DUMMY or no 'device random' this
1397 An additional fix for the issue described in the 20150614 sendmail
1398 entry below has been committed in revision 284717.
1401 FreeBSD's old make (fmake) has been removed from the system. It is
1402 available as the devel/fmake port or via pkg install fmake.
1405 The fix for the issue described in the 20150614 sendmail entry
1406 below has been committed in revision 284436. The work
1407 around described in that entry is no longer needed unless the
1408 default setting is overridden by a confDH_PARAMETERS configuration
1409 setting of '5' or pointing to a 512 bit DH parameter file.
1412 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1413 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1414 and devel/kyua to version 0.20+ and adjust any calling code to work
1415 with Kyuafile and kyua.
1418 The import of openssl to address the FreeBSD-SA-15:10.openssl
1419 security advisory includes a change which rejects handshakes
1420 with DH parameters below 768 bits. sendmail releases prior
1421 to 8.15.2 (not yet released), defaulted to a 512 bit
1422 DH parameter setting for client connections. To work around
1423 this interoperability, sendmail can be configured to use a
1424 2048 bit DH parameter by:
1426 1. Edit /etc/mail/`hostname`.mc
1427 2. If a setting for confDH_PARAMETERS does not exist or
1428 exists and is set to a string beginning with '5',
1429 replace it with '2'.
1430 3. If a setting for confDH_PARAMETERS exists and is set to
1431 a file path, create a new file with:
1432 openssl dhparam -out /path/to/file 2048
1433 4. Rebuild the .cf file:
1434 cd /etc/mail/; make; make install
1435 5. Restart sendmail:
1436 cd /etc/mail/; make restart
1438 A sendmail patch is coming, at which time this file will be
1442 Generation of legacy formatted entries have been disabled by default
1443 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1444 entries were converted to use the new format by default when the new,
1445 machine independent format have been added and supported since FreeBSD
1448 Please see the pwd_mkdb(8) manual page for further details.
1451 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1452 20141231 entry below for information about prerequisites and upgrading,
1453 if you are not already using 3.5.0 or higher.
1456 TI platform code switched to using vendor DTS files and this update
1457 may break existing systems running on Beaglebone, Beaglebone Black,
1460 - dtb files should be regenerated/reinstalled. Filenames are the
1461 same but content is different now
1462 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1463 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1464 addressing scheme is now pin 25 on /dev/gpioc3.
1465 - Pandaboard: /etc/ttys should be updated, serial console device is
1466 now /dev/ttyu2, not /dev/ttyu0
1469 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1470 If you need the GNU extension from groff soelim(1), install groff
1471 from package: pkg install groff, or via ports: textproc/groff.
1474 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1475 defined in symlink(7); previously symlinks were silently ignored.
1478 The const qualifier has been removed from iconv(3) to comply with
1479 POSIX. The ports tree is aware of this from r384038 onwards.
1482 Libraries specified by LIBADD in Makefiles must have a corresponding
1483 DPADD_<lib> variable to ensure correct dependencies. This is now
1484 enforced in src.libnames.mk.
1487 From legacy ata(4) driver was removed support for SATA controllers
1488 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1489 Kernel modules ataahci and ataadaptec were removed completely,
1490 replaced by ahci and mvs modules respectively.
1493 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1494 the 20141231 entry below for information about prerequisites and
1495 upgrading, if you are not already using 3.5.0 or higher.
1498 The 32-bit PowerPC kernel has been changed to a position-independent
1499 executable. This can only be booted with a version of loader(8)
1500 newer than January 31, 2015, so make sure to update both world and
1501 kernel before rebooting.
1504 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1505 but before r278950, the RNG was not seeded properly. Immediately
1506 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1507 ssh keys or openssl keys) that were generated w/ a kernel from that
1508 range. This does not affect programs that directly used /dev/random
1509 or /dev/urandom. All userland uses of arc4random(3) are affected.
1512 The autofs(4) ABI was changed in order to restore binary compatibility
1513 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1514 with the new kernel.
1517 The powerpc64 kernel has been changed to a position-independent
1518 executable. This can only be booted with a new version of loader(8),
1519 so make sure to update both world and kernel before rebooting.
1522 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1523 only release, no new features have been added. Please see the 20141231
1524 entry below for information about prerequisites and upgrading, if you
1525 are not already using 3.5.0.
1528 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1529 taken from the ELF Tool Chain project rather than GNU binutils. They
1530 should be drop-in replacements, with the addition of arm64 support.
1531 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1532 binutils tools, if necessary. See 20150805 for updated information.
1535 The default Unbound configuration now enables remote control
1536 using a local socket. Users who have already enabled the
1537 local_unbound service should regenerate their configuration
1538 by running "service local_unbound setup" as root.
1541 The GNU texinfo and GNU info pages have been removed.
1542 To be able to view GNU info pages please install texinfo from ports.
1545 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1547 As of this release, a prerequisite for building clang, llvm and lldb is
1548 a C++11 capable compiler and C++11 standard library. This means that to
1549 be able to successfully build the cross-tools stage of buildworld, with
1550 clang as the bootstrap compiler, your system compiler or cross compiler
1551 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1552 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1555 On any standard FreeBSD 10.x or 11.x installation, where clang and
1556 libc++ are on by default (that is, on x86 or arm), this should work out
1559 On 9.x installations where clang is enabled by default, e.g. on x86 and
1560 powerpc, libc++ will not be enabled by default, so libc++ should be
1561 built (with clang) and installed first. If both clang and libc++ are
1562 missing, build clang first, then use it to build libc++.
1564 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1565 the instructions for 9.x above.
1567 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1568 default, and do not build clang.
1570 Many embedded systems are resource constrained, and will not be able to
1571 build clang in a reasonable time, or in some cases at all. In those
1572 cases, cross building bootable systems on amd64 is a workaround.
1574 This new version of clang introduces a number of new warnings, of which
1575 the following are most likely to appear:
1579 This warns in two cases, for both C and C++:
1580 * When the code is trying to take the absolute value of an unsigned
1581 quantity, which is effectively a no-op, and almost never what was
1582 intended. The code should be fixed, if at all possible. If you are
1583 sure that the unsigned quantity can be safely cast to signed, without
1584 loss of information or undefined behavior, you can add an explicit
1585 cast, or disable the warning.
1587 * When the code is trying to take an absolute value, but the called
1588 abs() variant is for the wrong type, which can lead to truncation.
1589 If you want to disable the warning instead of fixing the code, please
1590 make sure that truncation will not occur, or it might lead to unwanted
1593 -Wtautological-undefined-compare and
1594 -Wundefined-bool-conversion
1596 These warn when C++ code is trying to compare 'this' against NULL, while
1597 'this' should never be NULL in well-defined C++ code. However, there is
1598 some legacy (pre C++11) code out there, which actively abuses this
1599 feature, which was less strictly defined in previous C++ versions.
1601 Squid and openjdk do this, for example. The warning can be turned off
1602 for C++98 and earlier, but compiling the code in C++11 mode might result
1603 in unexpected behavior; for example, the parts of the program that are
1604 unreachable could be optimized away.
1607 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1608 kernel sources have been removed. The .h files remain, since some
1609 utilities include them. This will need to be fixed later.
1610 If "mount -t oldnfs ..." is attempted, it will fail.
1611 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1612 the utilities will report errors.
1615 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1616 directories to top level SUBDIR variable when their parent
1617 directory is included in LOCAL_DIRS. Users with build systems with
1618 such hierarchies and without SUBDIR entries in the parent
1619 directory Makefiles should add them or add the directories to
1623 faith(4) and faithd(8) have been removed from the base system. Faith
1624 has been obsolete for a very long time.
1627 vt(4), the new console driver, is enabled by default. It brings
1628 support for Unicode and double-width characters, as well as
1629 support for UEFI and integration with the KMS kernel video
1632 You may need to update your console settings in /etc/rc.conf,
1633 most probably the keymap. During boot, /etc/rc.d/syscons will
1634 indicate what you need to do.
1636 vt(4) still has issues and lacks some features compared to
1637 syscons(4). See the wiki for up-to-date information:
1638 https://wiki.freebsd.org/Newcons
1640 If you want to keep using syscons(4), you can do so by adding
1641 the following line to /boot/loader.conf:
1645 pjdfstest has been integrated into kyua as an opt-in test suite.
1646 Please see share/doc/pjdfstest/README for more details on how to
1650 gperf has been removed from the base system for architectures
1651 that use clang. Ports that require gperf will obtain it from the
1655 pjdfstest has been moved from tools/regression/pjdfstest to
1659 At svn r271982, The default linux compat kernel ABI has been adjusted
1660 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1661 update. If you wish to continue using the linux-f10 compat ports,
1662 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1663 encouraged to update their linux-compat packages to linux-c6 during
1664 their next update cycle.
1667 The ofwfb driver, used to provide a graphics console on PowerPC when
1668 using vt(4), no longer allows mmap() of all physical memory. This
1669 will prevent Xorg on PowerPC with some ATI graphics cards from
1670 initializing properly unless x11-servers/xorg-server is updated to
1674 The xdev targets have been converted to using TARGET and
1675 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1678 The default unbound configuration has been modified to address
1679 issues with reverse lookups on networks that use private
1680 address ranges. If you use the local_unbound service, run
1681 "service local_unbound setup" as root to regenerate your
1682 configuration, then "service local_unbound reload" to load the
1686 The GNU texinfo and GNU info pages are not built and installed
1687 anymore, WITH_INFO knob has been added to allow to built and install
1689 UPDATE: see 20150102 entry on texinfo's removal
1692 The GNU readline library is now an INTERNALLIB - that is, it is
1693 statically linked into consumers (GDB and variants) in the base
1694 system, and the shared library is no longer installed. The
1695 devel/readline port is available for third party software that
1699 The Itanium architecture (ia64) has been removed from the list of
1700 known architectures. This is the first step in the removal of the
1704 Commit r268115 has added NFSv4.1 server support, merged from
1705 projects/nfsv4.1-server. Since this includes changes to the
1706 internal interfaces between the NFS related modules, a full
1707 build of the kernel and modules will be necessary.
1708 __FreeBSD_version has been bumped.
1711 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1712 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1713 which differs from the behaviour controlled by this knob.)
1716 Maximal length of the serial number in CTL was increased from 16 to
1717 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1718 and ctld, need to be rebuilt to work with a new kernel.
1721 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1722 1 respectively to match the upstream numbers. They were out of
1723 sync because, when they were originally added to FreeBSD, the
1724 upstream versions were not respected. These libraries are private
1725 and not yet built by default, so renumbering them should be a
1726 non-issue. However, unclean source trees will yield broken test
1727 programs once the operator executes "make delete-old-libs" after a
1728 "make installworld".
1730 Additionally, the atf-sh binary was made private by moving it into
1731 /usr/libexec/. Already-built shell test programs will keep the
1732 path to the old binary so they will break after "make delete-old"
1735 If you are using WITH_TESTS=yes (not the default), wipe the object
1736 tree and rebuild from scratch to prevent spurious test failures.
1737 This is only needed once: the misnumbered libraries and misplaced
1738 binaries have been added to OptionalObsoleteFiles.inc so they will
1739 be removed during a clean upgrade.
1742 Clang and llvm have been upgraded to 3.4.1 release.
1745 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1746 be removed to avoid issues in the future (and has been added to
1750 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1751 past, it affected all builds that used the bsd.*.mk files. The old
1752 behavior was a bug, but people may have relied upon it. To get this
1753 behavior back, you can .include /etc/src.conf from /etc/make.conf
1754 (which is still global and isn't changed). This also changes the
1755 behavior of incremental builds inside the tree of individual
1756 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1757 Although this has survived make universe and some upgrade scenarios,
1758 other upgrade scenarios may have broken. At least one form of
1759 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1760 as well... In cases where MAKESYSPATH isn't working with this
1761 setting, you'll need to set it to the full path to your tree.
1763 One side effect of all this cleaning up is that bsd.compiler.mk
1764 is no longer implicitly included by bsd.own.mk. If you wish to
1765 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1769 The lindev device has been removed since /dev/full has been made a
1770 standard device. __FreeBSD_version has been bumped.
1773 The knob WITHOUT_VI was added to the base system, which controls
1774 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1775 in order to reorder files share/termcap and didn't build ex(1) as a
1776 build tool, so building/installing with WITH_VI is highly advised for
1777 build hosts for older releases.
1779 This issue has been fixed in stable/9 and stable/10 in r277022 and
1780 r276991, respectively.
1783 The YES_HESIOD knob has been removed. It has been obsolete for
1784 a decade. Please move to using WITH_HESIOD instead or your builds
1785 will silently lack HESIOD.
1788 The uart(4) driver has been changed with respect to its handling
1789 of the low-level console. Previously the uart(4) driver prevented
1790 any process from changing the baudrate or the CLOCAL and HUPCL
1791 control flags. By removing the restrictions, operators can make
1792 changes to the serial console port without having to reboot.
1793 However, when getty(8) is started on the serial device that is
1794 associated with the low-level console, a misconfigured terminal
1795 line in /etc/ttys will now have a real impact.
1796 Before upgrading the kernel, make sure that /etc/ttys has the
1797 serial console device configured as 3wire without baudrate to
1798 preserve the previous behaviour. E.g:
1799 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1802 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1803 to improve performance. To re-enable it, if needed, run rpcbind
1804 with command line option -W.
1807 Switched back to the GPL dtc compiler due to updates in the upstream
1808 dts files not being supported by the BSDL dtc compiler. You will need
1809 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1810 may result while building dtb files during a kernel build if you fail
1811 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1814 Clang and llvm have been upgraded to 3.4 release.
1817 The nve(4) driver has been removed. Please use the nfe(4) driver
1818 for NVIDIA nForce MCP Ethernet adapters instead.
1821 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1822 This could cause certain C++ applications using shared libraries built
1823 against the previous version of libc++ to crash. The incompatibility
1824 has now been fixed, but any C++ applications or shared libraries built
1825 between r261283 and r261801 should be recompiled.
1828 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1829 capability mode support. Please note that enabling the feature in
1830 kernel is still highly recommended.
1833 OpenSSH is now built with sandbox support, and will use sandbox as
1834 the default privilege separation method. This requires Capsicum
1835 capability mode support in kernel.
1838 The libelf and libdwarf libraries have been updated to newer
1839 versions from upstream. Shared library version numbers for
1840 these two libraries were bumped. Any ports or binaries
1841 requiring these two libraries should be recompiled.
1842 __FreeBSD_version is bumped to 1100006.
1845 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1846 instead of providing an explicit one, this would prevent such
1847 Makefile from providing its own Kyuafile in the future during
1848 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1849 intervention is needed to clean an objdir if you use NO_CLEAN:
1850 # find /usr/obj -name Kyuafile | xargs rm -f
1853 The behavior of gss_pseudo_random() for the krb5 mechanism
1854 has changed, for applications requesting a longer random string
1855 than produced by the underlying enctype's pseudo-random() function.
1856 In particular, the random string produced from a session key of
1857 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1858 be different at the 17th octet and later, after this change.
1859 The counter used in the PRF+ construction is now encoded as a
1860 big-endian integer in accordance with RFC 4402.
1861 __FreeBSD_version is bumped to 1100004.
1864 The WITHOUT_ATF build knob has been removed and its functionality
1865 has been subsumed into the more generic WITHOUT_TESTS. If you were
1866 using the former to disable the build of the ATF libraries, you
1867 should change your settings to use the latter.
1870 The default version of mtree is nmtree which is obtained from
1871 NetBSD. The output is generally the same, but may vary
1872 slightly. If you found you need identical output adding
1873 "-F freebsd9" to the command line should do the trick. For the
1874 time being, the old mtree is available as fmtree.
1877 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1878 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1879 1.1.4_8 and verify bsdyml not linked in, before running "make
1881 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1883 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1886 The stable/10 branch has been created in subversion from head
1893 Avoid using make -j when upgrading. While generally safe, there are
1894 sometimes problems using -j to upgrade. If your upgrade fails with
1895 -j, please try again without -j. From time to time in the past there
1896 have been problems using -j with buildworld and/or installworld. This
1897 is especially true when upgrading between "distant" versions (eg one
1898 that cross a major release boundary or several minor releases, or when
1899 several months have passed on the -current branch).
1901 Sometimes, obscure build problems are the result of environment
1902 poisoning. This can happen because the make utility reads its
1903 environment when searching for values for global variables. To run
1904 your build attempts in an "environmental clean room", prefix all make
1905 commands with 'env -i '. See the env(1) manual page for more details.
1907 When upgrading from one major version to another it is generally best to
1908 upgrade to the latest code in the currently installed branch first, then
1909 do an upgrade to the new branch. This is the best-tested upgrade path,
1910 and has the highest probability of being successful. Please try this
1911 approach if you encounter problems with a major version upgrade. Since
1912 the stable 4.x branch point, one has generally been able to upgrade from
1913 anywhere in the most recent stable branch to head / current (or even the
1914 last couple of stable branches). See the top of this file when there's
1917 When upgrading a live system, having a root shell around before
1918 installing anything can help undo problems. Not having a root shell
1919 around can lead to problems if pam has changed too much from your
1920 starting point to allow continued authentication after the upgrade.
1922 This file should be read as a log of events. When a later event changes
1923 information of a prior event, the prior event should not be deleted.
1924 Instead, a pointer to the entry with the new information should be
1925 placed in the old entry. Readers of this file should also sanity check
1926 older entries before relying on them blindly. Authors of new entries
1927 should write them with this in mind.
1931 When upgrading the boot ZFS pool to a new version, always follow
1934 1.) recompile and reinstall the ZFS boot loader and boot block
1935 (this is part of "make buildworld" and "make installworld")
1937 2.) update the ZFS boot block on your boot drive
1939 The following example updates the ZFS boot block on the first
1940 partition (freebsd-boot) of a GPT partitioned drive ada0:
1941 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1943 Non-boot pools do not need these updates.
1947 If you are updating from a prior version of FreeBSD (even one just
1948 a few days old), you should follow this procedure. It is the most
1949 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1951 make kernel-toolchain
1952 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1953 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1955 To test a kernel once
1956 ---------------------
1957 If you just want to boot a kernel once (because you are not sure
1958 if it works, or if you want to boot a known bad kernel to provide
1959 debugging information) run
1960 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1961 nextboot -k testkernel
1963 To rebuild everything and install it on the current system.
1964 -----------------------------------------------------------
1965 # Note: sometimes if you are running current you gotta do more than
1966 # is listed here if you are upgrading from a really old current.
1968 <make sure you have good level 0 dumps>
1970 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1971 make installkernel KERNCONF=YOUR_KERNEL_HERE
1973 <reboot in single user> [3]
1980 To cross-install current onto a separate partition
1981 --------------------------------------------------
1982 # In this approach we use a separate partition to hold
1983 # current's root, 'usr', and 'var' directories. A partition
1984 # holding "/", "/usr" and "/var" should be about 2GB in
1987 <make sure you have good level 0 dumps>
1990 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1991 <maybe newfs current's root partition>
1992 <mount current's root partition on directory ${CURRENT_ROOT}>
1993 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1994 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1995 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1996 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1997 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1998 <reboot into current>
1999 <do a "native" rebuild/install as described in the previous section>
2000 <maybe install compatibility libraries from ports/misc/compat*>
2004 To upgrade in-place from stable to current
2005 ----------------------------------------------
2006 <make sure you have good level 0 dumps>
2008 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2009 make installkernel KERNCONF=YOUR_KERNEL_HERE
2011 <reboot in single user> [3]
2018 Make sure that you've read the UPDATING file to understand the
2019 tweaks to various things you need. At this point in the life
2020 cycle of current, things change often and you are on your own
2021 to cope. The defaults can also change, so please read ALL of
2022 the UPDATING entries.
2024 Also, if you are tracking -current, you must be subscribed to
2025 freebsd-current@freebsd.org. Make sure that before you update
2026 your sources that you have read and understood all the recent
2027 messages there. If in doubt, please track -stable which has
2028 much fewer pitfalls.
2030 [1] If you have third party modules, such as vmware, you
2031 should disable them at this point so they don't crash your
2034 [3] From the bootblocks, boot -s, and then do
2039 adjkerntz -i # if CMOS is wall time
2040 Also, when doing a major release upgrade, it is required that
2041 you boot into single user mode to do the installworld.
2043 [4] Note: This step is non-optional. Failure to do this step
2044 can result in a significant reduction in the functionality of the
2045 system. Attempting to do it by hand is not recommended and those
2046 that pursue this avenue should read this file carefully, as well
2047 as the archives of freebsd-current and freebsd-hackers mailing lists
2048 for potential gotchas. The -U option is also useful to consider.
2049 See mergemaster(8) for more information.
2051 [5] Usually this step is a no-op. However, from time to time
2052 you may need to do this if you get unknown user in the following
2053 step. It never hurts to do it all the time. You may need to
2054 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2055 install) after the buildworld before this step if you last updated
2056 from current before 20130425 or from -stable before 20130430.
2058 [6] This only deletes old files and directories. Old libraries
2059 can be deleted by "make delete-old-libs", but you have to make
2060 sure that no program is using those libraries anymore.
2062 [8] The new kernel must be able to run existing binaries used by
2063 an installworld. When upgrading across major versions, the new
2064 kernel's configuration must include the correct COMPAT_FREEBSD<n>
2065 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
2066 binaries). Failure to do so may leave you with a system that is
2067 hard to boot to recover. A GENERIC kernel will include suitable
2068 compatibility options to run binaries from older branches.
2070 Make sure that you merge any new devices from GENERIC since the
2071 last time you updated your kernel config file.
2073 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2074 "?=" instead of the "=" assignment operator, so that buildworld can
2075 override the CPUTYPE if it needs to.
2077 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2078 not on the command line, or in /etc/make.conf. buildworld will
2079 warn if it is improperly defined.
2082 This file contains a list, in reverse chronological order, of major
2083 breakages in tracking -current. It is not guaranteed to be a complete
2084 list of such breakages, and only contains entries since September 23, 2011.
2085 If you need to see UPDATING entries from before that date, you will need
2086 to fetch an UPDATING file from an older FreeBSD release.
2088 Copyright information:
2090 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2092 Redistribution, publication, translation and use, with or without
2093 modification, in full or in part, in any form or format of this
2094 document are permitted without further permission from the author.
2096 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2097 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2098 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2099 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2100 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2101 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2102 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2103 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2104 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2105 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2106 POSSIBILITY OF SUCH DAMAGE.
2108 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob