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