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 mips, powerpc, and sparc64 are no longer built as part of
31 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
32 not defined, mips, powerpc, and sparc64 builds will look for
33 the xtoolchain binaries and if installed use them for universe
34 builds. As llvm 9.0 becomes vetted for these architectures, they
35 will be removed from the list.
38 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
39 been upgraded to 9.0.0. Please see the 20141231 entry below for
40 information about prerequisites and upgrading, if you are not already
41 using clang 3.5.0 or higher.
44 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
45 GENERIC. They are available as modules and can be loaded by adding
46 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
47 hptnr_load="YES", or hptrr_load="YES", respectively.
50 ntpd no longer by default locks its pages in memory, allowing them
51 to be paged out by the kernel. Use rlimit memlock to restore
52 historic BSD behaviour. For example, add "rlimit memlock 32"
53 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
56 Several of ping6's options have been renamed for better consistency
57 with ping. If you use any of -ARWXaghmrtwx, you must update your
58 scripts. See ping6(8) for details.
61 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
62 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
63 been removed from mount_fusefs(8). You can safely remove them from
64 your scripts, because they had no effect.
66 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
67 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
68 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
69 sysctls have been removed. If you felt the need to set any of them to
70 a non-default value, please tell asomers@FreeBSD.org why.
73 Default permissions on the /var/account/acct file (and copies of it
74 rotated by periodic daily scripts) are changed from 0644 to 0640
75 because the file contains sensitive information that should not be
76 world-readable. If the /var/account directory must be created by
77 rc.d/accounting, the mode used is now 0750. Admins who use the
78 accounting feature are encouraged to change the mode of an existing
79 /var/account directory to 0750 or 0700.
82 Entropy collection and the /dev/random device are no longer optional
83 components. The "device random" option has been removed.
84 Implementations of distilling algorithms can still be made loadable
85 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
88 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
89 been upgraded to 8.0.1. Please see the 20141231 entry below for
90 information about prerequisites and upgrading, if you are not already
91 using clang 3.5.0 or higher.
94 A fix was applied to i386 kernel modules to avoid panics with
95 dpcpu or vnet. Users need to recompile i386 kernel modules
96 having pcpu or vnet sections or they will refuse to load.
99 User-wired pages now have their own counter,
100 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
101 to vm.max_user_wired and changed from an unsigned int to an unsigned
102 long. bhyve VMs wired with the -S are now subject to the user
103 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
104 avoid running into the limit.
107 The IPSEC option has been removed from GENERIC. Users requiring
108 ipsec(4) must now load the ipsec(4) kernel module.
111 The tap(4) driver has been folded into tun(4), and the module has been
112 renamed to tuntap. You should update any kld_list="if_tap" or
113 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
114 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
115 module instead, and "device tap" or "device tun" entries in kernel
116 config files to select the tuntap device instead.
119 The following knobs have been added related to tradeoffs between
120 safe use of the random device and availability in the absence of
123 kern.random.initial_seeding.bypass_before_seeding: tunable; set
124 non-zero to bypass the random device prior to seeding, or zero to
125 block random requests until the random device is initially seeded.
126 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
127 availability properties.
129 kern.random.initial_seeding.read_random_bypassed_before_seeding:
130 read-only diagnostic sysctl that is set when bypass is enabled and
131 read_random(9) is bypassed, to enable programmatic handling of this
132 initial condition, if desired.
134 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
135 Similar to the above, but for for arc4random(9) initial seeding.
137 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
138 non-zero to disable warnings in dmesg when the same conditions are
139 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
140 produce warnings in dmesg when the conditions are met.
143 The loadable random module KPI has changed; the random_infra_init()
144 routine now requires a 3rd function pointer for a bool (*)(void)
145 method that returns true if the random device is seeded (and
146 therefore unblocked).
149 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
150 built from head sources between r320757 (July 6, 2017) and
151 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
152 is added to the command line.
153 nfsuserd daemons built from head sources that are post-r338192 are
154 not affected and should continue to work.
157 The fuse(4) module has been renamed to fusefs(4) for consistency with
158 other filesystems. You should update any kld_load="fuse" entries in
159 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
160 "options FUSE" entries in kernel config files.
163 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
164 8.0.0. Please see the 20141231 entry below for information about
165 prerequisites and upgrading, if you are not already using clang 3.5.0
169 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
170 compiled into your custom kernel, add 'device xz' statement to the
174 drm and drm2 have been removed from the tree. Please see
175 https://wiki.freebsd.org/Graphics for the latest information on
176 migrating to the drm ports.
179 Iflib is no longer unconditionally compiled into the kernel. Drivers
180 using iflib and statically compiled into the kernel, now require
181 the 'device iflib' config option. For the same drivers loaded as
182 modules on kernels not having 'device iflib', the iflib.ko module
183 is loaded automatically.
186 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
187 options no longer exist since r343219 and r343427 respectively;
188 nothing uses them, so they should be just removed from custom
192 r342635 changes the way efibootmgr(8) works by requiring users to add
193 the -b (bootnum) parameter for commands where the bootnum was previously
194 specified with each option. For example 'efibootmgr -B 0001' is now
195 'efibootmgr -B -b 0001'.
198 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
199 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
200 servers that have vfs.nfsd.nfs_privport set will only allow mounts
201 from clients using a reserved port#. Since both the FreeBSD and Linux
202 NFSv4 clients use reserved port#s by default, this should not affect
206 The XLP config has been removed. We can't support 64-bit atomics in this
207 kernel because it is running in 32-bit mode. XLP users must transition
208 to running a 64-bit kernel (XLP64 or XLPN32).
210 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
211 the preferred emulator today and we don't need two different ones.
213 The old sibyte / swarm / Broadcom BCM1250 support has been
214 removed from the mips port.
217 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
218 7.0.1. Please see the 20141231 entry below for information about
219 prerequisites and upgrading, if you are not already using clang 3.5.0
223 Remove the timed and netdate programs from the base tree. Setting
224 the time with these daemons has been obsolete for over a decade.
227 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
228 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
229 it produces broken binaries when ifuncs are in use. Users needing
230 GNU ld should install the binutils port or package.
233 The BSD crtbegin and crtend code has been enabled by default. It has
234 had extensive testing on amd64, arm64, and i386. It can be disabled
235 by building a world with -DWITHOUT_BSD_CRTBEGIN.
238 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
239 has been converted to a port (misc/ctm) and will be removed from
240 FreeBSD-13. It is available as a package (ctm) for all supported
244 The default newsyslog.conf(5) file has been changed to only include
245 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
246 the filenames end in '.conf' and do not begin with a '.'.
248 You should check the configuration files in these two directories match
249 this naming convention. You can verify which configuration files are
250 being included using the command:
254 Ports for the DRM modules have been simplified. Now, amd64 users should
255 just install the drm-kmod port. All others should install
258 Graphics hardware that's newer than about 2010 usually works with
259 drm-kmod. For hardware older than 2013, however, some users will need
260 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
261 than 2008 usually only works in drm-legacy-kmod. The graphics team can
262 only commit to hardware made since 2013 due to the complexity of the
263 market and difficulty to test all the older cards effectively. If you
264 have hardware supported by drm-kmod, you are strongly encouraged to use
265 that as you will get better support.
267 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
268 elsewhere, the drm and drm2 modules will be eliminated from the src base
269 soon (with a limited exception for arm). Please update to the package
270 asap and report any issues to x11@freebsd.org.
272 Generally, anybody using the drm*-kmod packages should add
273 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
274 cross-threading surprises, especially with automatic driver
275 loading from X11 startup. These will become the defaults in 13-current
279 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
280 custom kernel and module loading configuration files must be updated
281 accordingly. Moreover, interfaces previous presented as ixlvN to the
282 system are now exposed as iavfN and network configuration files must
283 be adjusted as necessary.
286 OpenSSL has been updated to version 1.1.1. This update included
287 additional various API changes throughout the base system. It is
288 important to rebuild third-party software after upgrading. The value
289 of __FreeBSD_version has been bumped accordingly.
292 The legacy DRM modules and drivers have now been added to the loader's
293 module blacklist, in favor of loading them with kld_list in rc.conf(5).
294 The module blacklist may be overridden with the loader.conf(5)
295 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
299 The cam(4) based nda(4) driver will be used over nvd(4) by default on
300 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
301 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
302 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
306 Reproducible build mode is now on by default, in preparation for
307 FreeBSD 12.0. This eliminates build metadata such as the user,
308 host, and time from the kernel (and uname), unless the working tree
309 corresponds to a modified checkout from a version control system.
310 The previous behavior can be obtained by setting the /etc/src.conf
311 knob WITHOUT_REPRODUCIBLE_BUILD.
314 The Yarrow CSPRNG has been removed from the kernel as it has not been
315 supported by its designers since at least 2003. Fortuna has been the
316 default since FreeBSD-11.
319 devctl freeze/thaw have gone into the tree, the rc scripts have been
320 updated to use them and devmatch has been changed. You should update
321 kernel, userland and rc scripts all at the same time.
324 The default interpreter has been switched from 4th to Lua.
325 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
326 interpreter. If you have custom FORTH code you will need to set
327 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
328 src.conf for the build. This will create default hard links between
329 loader and loader_4th instead of loader and loader_lua, the new default.
330 If you are using UEFI it will create the proper hard link to loader.efi.
332 bhyve uses userboot.so. It remains 4th-only until some issues are solved
333 regarding coexisting with multiple versions of FreeBSD are resolved.
336 ls(1) now respects the COLORTERM environment variable used in other
337 systems and software to indicate that a colored terminal is both
338 supported and desired. If ls(1) is suddenly emitting colors, they may
339 be disabled again by either removing the unwanted COLORTERM from your
340 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
341 may not be observed in a future release.
344 The default pager for most commands has been changed to "less". To
345 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
349 The jedec_ts(4) driver has been removed. A superset of its functionality
350 is available in the jedec_dimm(4) driver, and the manpage for that
351 driver includes migration instructions. If you have "device jedec_ts"
352 in your kernel configuration file, it must be removed.
355 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
356 This should have no effect if the kernel is booted via BIOS/legacy boot.
357 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
358 has a buggy firmware that prevents a successful boot due to use of
362 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
363 support has been removed from the tree. These ports were
364 obsolete and/or known to be broken for many years.
367 loader.efi has been augmented to participate more fully in the
368 UEFI boot manager protocol. loader.efi will now look at the
369 BootXXXX environment variable to determine if a specific kernel
370 or root partition was specified. XXXX is derived from BootCurrent.
371 efibootmgr(8) manages these standard UEFI variables.
374 zfsloader's functionality has now been folded into loader.
375 zfsloader is no longer necessary once you've updated your
376 boot blocks. For a transition period, we will install a
377 hardlink for zfsloader to loader to allow a smooth transition
378 until the boot blocks can be updated (hard link because old
379 zfs boot blocks don't understand symlinks).
382 ARM64 now have efifb support, if you want to have serial console
383 on your arm64 board when an screen is connected and the bootloader
384 setup a frame buffer for us to use, just add :
388 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
389 an screen connected as the firmware will setup a frame buffer are that
390 u-boot will expose as an EFI frame buffer.
393 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
394 or take steps to update /etc/passwd before doing installworld on
395 existing systems. Do not skip the "mergemaster -Fp" step before
396 installworld, as described in the update procedures near the bottom
397 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
398 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
399 the ntp config file contain options that change file/dir locations.
400 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
401 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
402 taking steps to ensure that all required files/dirs are accessible
406 Big endian arm support has been removed.
409 The static environment setup in kernel configs is no longer mutually
410 exclusive with the loader(8) environment by default. In order to
411 restore the previous default behavior of disabling the loader(8)
412 environment if a static environment is present, you must specify
413 loader_env.disabled=1 in the static environment.
416 The ABI of syscalls used by management tools like sockstat and
417 netstat has been broken to allow 32-bit binaries to work on
418 64-bit kernels without modification. These programs will need
419 to match the kernel in order to function. External programs may
420 require minor modifications to accommodate a change of type in
421 structures from pointers to 64-bit virtual addresses.
424 On i386 and amd64 atomics are now inlined. Out of tree modules using
425 atomics will need to be rebuilt.
428 The '%I' format in the kern.corefile sysctl limits the number of
429 core files that a process can generate to the number stored in the
430 debug.ncores sysctl. The '%I' format is replaced by the single digit
431 index. Previously, if all indexes were taken the kernel would overwrite
432 only a core file with the highest index in a filename.
433 Currently the system will create a new core file if there is a free
434 index or if all slots are taken it will overwrite the oldest one.
437 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
438 6.0.1. Please see the 20141231 entry below for information about
439 prerequisites and upgrading, if you are not already using clang 3.5.0
443 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
444 needed to be changed to work with it. This change was made with r335763
445 and requires a mergemaster / etcupdate / etc to update the installed
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 acquired 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-existence 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
588 to be loaded. Please report any problems to current@ and
592 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
593 6.0.0. Please see the 20141231 entry below for information about
594 prerequisites and upgrading, if you are not already using clang 3.5.0
598 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
599 This means it is used to link the kernel and userland libraries and
600 executables, but is not yet installed as /usr/bin/ld by default.
602 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
603 WITHOUT_LLD_BOOTSTRAP=yes
606 On i386, pmtimer has been removed. Its functionality has been folded
607 into apm. It was a no-op on ACPI in current for a while now (but was
608 still needed on i386 in FreeBSD 11 and earlier). Users may need to
609 remove it from kernel config files.
612 The use of RSS hash from the network card aka flowid has been
613 disabled by default for lagg(4) as it's currently incompatible with
614 the lacp and loadbalance protocols.
616 This can be re-enabled by setting the following in loader.conf:
617 net.link.lagg.default_use_flowid="1"
620 The SW_WATCHDOG option is no longer necessary to enable the
621 hardclock-based software watchdog if no hardware watchdog is
622 configured. As before, SW_WATCHDOG will cause the software
623 watchdog to be enabled even if a hardware watchdog is configured.
626 r326887 fixes the issue described in the 20171214 UPDATING entry.
627 r326888 flips the switch back to building GELI support always.
630 r362593 broke ZFS + GELI support for reasons unknown. However,
631 it also broke ZFS support generally, so GELI has been turned off
632 by default as the lesser evil in r326857. If you boot off ZFS and/or
633 GELI, it might not be a good time to update.
636 PowerPC users must update loader(8) by rebuilding world before
637 installing a new kernel, as the protocol connecting them has
638 changed. Without the update, loader metadata will not be passed
639 successfully to the kernel and users will have to enter their
640 root partition at the kernel mountroot prompt to continue booting.
641 Newer versions of loader can boot old kernels without issue.
644 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
645 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
646 to WITH/OUT_LOADER_GELI.
649 The naive and non-compliant support of posix_fallocate(2) in ZFS
650 has been removed as of r325320. The system call now returns EINVAL
651 when used on a ZFS file. Although the new behavior complies with the
652 standard, some consumers are not prepared to cope with it.
653 One known victim is lld prior to r325420.
656 Building in a FreeBSD src checkout will automatically create object
657 directories now rather than store files in the current directory if
658 'make obj' was not ran. Calling 'make obj' is no longer necessary.
659 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
660 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
664 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
665 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
666 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
667 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
668 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
669 The UNIFIED_OBJDIR option is a transitional feature that will be
670 removed for 12.0 release; please migrate to the new format for any
671 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
672 than hardcoding paths.
675 The native-xtools target no longer installs the files by default to the
676 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
677 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
680 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
681 options are changing from controlling the build if defined / undefined
682 to controlling the build with explicit 'yes' or 'no' values. They will
683 shift to WITH/WITHOUT options to match other options in the system.
686 libstand has turned into a private library for sys/boot use only.
687 It is no longer supported as a public interface outside of sys/boot.
690 The arm port has split armv6 into armv6 and armv7. armv7 is now
691 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
692 and are running a kernel from before r324363, you will need to add
693 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
696 When building multiple kernels using KERNCONF, non-existent KERNCONF
697 files will produce an error and buildkernel will fail. Previously
698 missing KERNCONF files silently failed giving no indication as to
699 why, only to subsequently discover during installkernel that the
700 desired kernel was never built in the first place.
703 The default serial number format for CTL LUNs has changed. This will
704 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
705 or iSCSI clients care about their LUNs' serial numbers. Users who
706 require serial number stability should hardcode serial numbers in
710 For 32-bit arm compiled for hard-float support, soft-floating point
711 binaries now always get their shared libraries from
712 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
713 /usr/libsoft also existed). Only users with a hard-float ld.so, but
714 soft-float everything else should be affected.
717 The geli password typed at boot is now hidden. To restore the previous
718 behavior, see geli(8) for configuration options.
721 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
722 sysctl values. Minor nit, but requires a rebuild of both world/kernel
726 "make check" behavior (made in ^/head@r295380) has been changed to
727 execute from a limited sandbox, as opposed to executing from
731 - The "beforecheck" and "aftercheck" targets are now specified.
732 - ${CHECKDIR} (added in commit noted above) has been removed.
733 - Legacy behavior can be enabled by setting
734 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
736 If the limited sandbox mode is enabled, "make check" will execute
737 "make distribution", then install, execute the tests, and clean up the
738 sandbox if successful.
740 The "make distribution" and "make install" targets are typically run as
741 root to set appropriate permissions and ownership at installation time.
742 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
743 environment if executing "make check" with limited sandbox mode using
744 an unprivileged user.
747 Since the switch to GPT disk labels, fsck for UFS/FFS has been
748 unable to automatically find alternate superblocks. As of r322297,
749 the information needed to find alternate superblocks has been
750 moved to the end of the area reserved for the boot block.
751 Filesystems created with a newfs of this vintage or later
752 will create the recovery information. If you have a filesystem
753 created prior to this change and wish to have a recovery block
754 created for your filesystem, you can do so by running fsck in
755 foreground mode (i.e., do not use the -p or -y options). As it
756 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
757 to which you should answer yes.
760 As of r321665, an NFSv4 server configuration that services
761 Kerberos mounts or clients that do not support the uid/gid in
762 owner/owner_group string capability, must explicitly enable
763 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
764 machine's /etc/rc.conf file.
767 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
768 Please see the 20141231 entry below for information about prerequisites
769 and upgrading, if you are not already using clang 3.5.0 or higher.
772 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
773 r-commands (rlogin, rsh, etc.) to be built with the base system.
776 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
777 a very major ABI incompatible change, so users of FreeBSD/powerpc must
778 be careful when performing source upgrades. It is best to run
779 'make installworld' from an alternate root system, either a live
780 CD/memory stick, or a temporary root partition. Additionally, all ports
781 must be recompiled. powerpc64 is largely unaffected, except in the case
782 of 32-bit compatibility. All 32-bit binaries will be affected.
785 Forward compatibility for the "ino64" project have been committed. This
786 will allow most new binaries to run on older kernels in a limited
787 fashion. This prevents many of the common foot-shooting actions in the
788 upgrade as well as the limited ability to roll back the kernel across
789 the ino64 upgrade. Complicated use cases may not work properly, though
790 enough simpler ones work to allow recovery in most situations.
793 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
794 if you require the GPL compiler.
797 The internal ABI used for communication between the NFS kernel modules
798 was changed by r320085, so __FreeBSD_version was bumped to
799 ensure all the NFS related modules are updated together.
802 The ABI of struct event was changed by extending the data
803 member to 64bit and adding ext fields. For upgrade, same
804 precautions as for the entry 20170523 "ino64" must be
808 The GNU roff toolchain has been removed from base. To render manpages
809 which are not supported by mandoc(1), man(1) can fallback on GNU roff
810 from ports (and recommends to install it).
811 To render roff(7) documents, consider using GNU roff from ports or the
812 heirloom doctools roff toolchain from ports via pkg install groff or
813 via pkg install heirloom-doctools.
816 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
817 smaller runtime footprint builds. This is useful for embedded systems
818 which only require one chipset support.
820 If you load it as a module, make sure this is in /boot/loader.conf:
824 This will load the HAL, all chip/RF backends and if_ath_pci.
825 If you have if_ath_pci in /boot/loader.conf, ensure it is after
826 if_ath or it will not load any HAL chipset support.
828 If you want to selectively load things (eg on ye cheape ARM/MIPS
829 platforms where RAM is at a premium) you should:
832 * load the chip modules in question
833 * load ath_rate, ath_dfs
835 * load if_ath_pci and/or if_ath_ahb depending upon your particular
836 bus bind type - this is where probe/attach is done.
838 For further comments/feedback, poke adrian@ .
841 The "ino64" 64-bit inode project has been committed, which extends
842 a number of types to 64 bits. Upgrading in place requires care and
843 adherence to the documented upgrade procedure.
845 If using a custom kernel configuration ensure that the
846 COMPAT_FREEBSD11 option is included (as during the upgrade the
847 system will be running the ino64 kernel with the existing world).
849 For the safest in-place upgrade begin by removing previous build
850 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
851 procedure documented below under the heading "To rebuild everything and
852 install it on the current system." Specifically, a reboot is required
853 after installing the new kernel before installing world. While an
854 installworld normally works by accident from multiuser after rebooting
855 the proper kernel, there are many cases where this will fail across this
856 upgrade and installworld from single user is required.
859 The NATM framework including the en(4), fatm(4), hatm(4), and
860 patm(4) devices has been removed. Consumers should plan a
861 migration before the end-of-life date for FreeBSD 11.
864 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
865 diff has not been implemented, if those are needed a newer version of
866 GNU diff is available via the diffutils package under the gdiff name.
869 As of r316810 for ipfilter, keep frags is no longer assumed when
870 keep state is specified in a rule. r316810 aligns ipfilter with
871 documentation in man pages separating keep frags from keep state.
872 This allows keep state to be specified without forcing keep frags
873 and allows keep frags to be specified independently of keep state.
874 To maintain previous behaviour, also specify keep frags with
875 keep state (as documented in ipf.conf.5).
878 arm64 builds now use the base system LLD 4.0.0 linker by default,
879 instead of requiring that the aarch64-binutils port or package be
880 installed. To continue using aarch64-binutils, set
881 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
884 The UDP optimization in entry 20160818 that added the sysctl
885 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
886 packets will no longer be treated as L3 broadcast packets.
889 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
890 use any explicitly assigned loopback address available in the jail
891 instead of using the first assigned address of the jail.
894 The ctl.ko module no longer implements the iSCSI target frontend:
895 cfiscsi.ko does instead.
897 If building cfiscsi.ko as a kernel module, the module can be loaded
898 via one of the following methods:
899 - `cfiscsi_load="YES"` in loader.conf(5).
900 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
901 - ctladm(8)/ctld(8), when compiled with iSCSI support
902 (`WITH_ISCSI=yes` in src.conf(5))
904 Please see cfiscsi(4) for more details.
907 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
908 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
909 same source (previously, the dependency of mmcsd.ko on mmc.ko was
910 missing, but mmcsd.ko now will refuse to load if it is incompatible
914 The syntax of ipfw(8) named states was changed to avoid ambiguity.
915 If you have used named states in the firewall rules, you need to modify
916 them after installworld and before rebooting. Now named states must
917 be prefixed with colon.
920 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
921 removed as the userland we provide cannot use them. The KMS version
922 (sys/dev/drm2) supports the same hardware.
925 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
926 Please see the 20141231 entry below for information about prerequisites
927 and upgrading, if you are not already using clang 3.5.0 or higher.
930 The code that provides support for ZFS .zfs/ directory functionality
931 has been reimplemented. It's not possible now to create a snapshot
932 by mkdir under .zfs/snapshot/. That should be the only user visible
936 EISA bus support has been removed. The WITH_EISA option is no longer
940 MCA bus support has been removed.
943 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
944 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
947 The EM_MULTIQUEUE kernel configuration option is deprecated now that
948 the em(4) driver conforms to iflib specifications.
951 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
952 IFLIB. If you have a custom kernel configuration that excludes em(4)
953 but you use igb(4), you need to re-add em(4) to your custom
957 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
958 Please see the 20141231 entry below for information about prerequisites
959 and upgrading, if you are not already using clang 3.5.0 or higher.
962 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
963 Please see the 20141231 entry below for information about prerequisites
964 and upgrading, if you are not already using clang 3.5.0 or higher.
967 The layout of the pmap structure has changed for powerpc to put the pmap
968 statistics at the front for all CPU variations. libkvm(3) and all tools
969 that link against it need to be recompiled.
972 isl(4) and cyapa(4) drivers now require a new driver,
973 chromebook_platform(4), to work properly on Chromebook-class hardware.
974 On other types of hardware the drivers may need to be configured using
975 device hints. Please see the corresponding manual pages for details.
978 The urtwn(4) driver was merged into rtwn(4) and now consists of
979 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
981 Also, firmware for RTL8188CE was renamed due to possible name
982 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
985 GNU rcs has been removed from base. It is available as packages:
986 - rcs: Latest GPLv3 GNU rcs version.
987 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
991 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
992 modules now requires that the kernel configuration contain the
993 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
996 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
997 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1000 Relocatable object files with the extension of .So have been renamed
1001 to use an extension of .pico instead. The purpose of this change is
1002 to avoid a name clash with shared libraries on case-insensitive file
1003 systems. On those file systems, foo.So is the same file as foo.so.
1006 GNU rcs has been turned off by default. It can (temporarily) be built
1007 again by adding WITH_RCS knob in src.conf.
1008 Otherwise, GNU rcs is available from packages:
1009 - rcs: Latest GPLv3 GNU rcs version.
1010 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1013 The backup_uses_rcs functionality has been removed from rc.subr.
1016 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1017 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1018 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1019 QUEUE_MACRO_DEBUG behavior.
1022 r304787 changed some ioctl interfaces between the iSCSI userspace
1023 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1024 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1028 The UDP receive code has been updated to only treat incoming UDP
1029 packets that were addressed to an L2 broadcast address as L3
1030 broadcast packets. It is not expected that this will affect any
1031 standards-conforming UDP application. The new behaviour can be
1032 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1036 Remove the openbsd_poll system call.
1037 __FreeBSD_version has been bumped because of this.
1040 The stable/11 branch has been created from head@r302406.
1043 The libc stub for the pipe(2) system call has been replaced with
1044 a wrapper that calls the pipe2(2) system call and the pipe(2)
1045 system call is now only implemented by the kernels that include
1046 "options COMPAT_FREEBSD10" in their config file (this is the
1047 default). Users should ensure that this option is enabled in
1048 their kernel or upgrade userspace to r302092 before upgrading their
1052 CAM will now strip leading spaces from SCSI disks' serial numbers.
1053 This will affect users who create UFS filesystems on SCSI disks using
1054 those disk's diskid device nodes. For example, if /etc/fstab
1055 previously contained a line like
1056 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1057 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1058 transforms like gmirror may also be affected. ZFS users should
1062 The bitstring(3) API has been updated with new functionality and
1063 improved performance. But it is binary-incompatible with the old API.
1064 Objects built with the new headers may not be linked against objects
1065 built with the old headers.
1068 The brk and sbrk functions have been removed from libc on arm64.
1069 Binutils from ports has been updated to not link to these
1070 functions and should be updated to the latest version before
1071 installing a new libc.
1074 The armv6 port now defaults to hard float ABI. Limited support
1075 for running both hardfloat and soft float on the same system
1076 is available using the libraries installed with -DWITH_LIBSOFT.
1077 This has only been tested as an upgrade path for installworld
1078 and packages may fail or need manual intervention to run. New
1079 packages will be needed.
1081 To update an existing self-hosted armv6hf system, you must add
1082 TARGET_ARCH=armv6 on the make command line for both the build
1083 and the install steps.
1086 Kernel modules compiled outside of a kernel build now default to
1087 installing to /boot/modules instead of /boot/kernel. Many kernel
1088 modules built this way (such as those in ports) already overrode
1089 KMODDIR explicitly to install into /boot/modules. However,
1090 manually building and installing a module from /sys/modules will
1091 now install to /boot/modules instead of /boot/kernel.
1094 The CAM I/O scheduler has been committed to the kernel. There should be
1095 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1096 list of known rogues that claim support for this but actually corrupt
1097 data is believed to be complete, be on the lookout for data
1098 corruption. The known rogue list is believed to be complete:
1100 o Crucial MX100, M550 drives with MU01 firmware.
1101 o Micron M510 and M550 drives with MU01 firmware.
1102 o Micron M500 prior to MU07 firmware
1103 o Samsung 830, 840, and 850 all firmwares
1104 o FCCT M500 all firmwares
1106 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1107 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1108 updated firmware. Black listed drives will work correctly because these
1109 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1110 this list is the same as found in Linux, it's believed there are no
1111 other rogues in the market place. All other models from the above
1114 To be safe, if you are at all concerned, you can quirk each of your
1115 drives to prevent NCQ from being sent by setting:
1116 kern.cam.ada.X.quirks="0x2"
1117 in loader.conf. If the drive requires the 4k sector quirk, set the
1118 quirks entry to 0x3.
1121 The FAST_DEPEND build option has been removed and its functionality is
1122 now the one true way. The old mkdep(1) style of 'make depend' has
1123 been removed. See 20160311 for further details.
1126 Resource range types have grown from unsigned long to uintmax_t. All
1127 drivers, and anything using libdevinfo, need to be recompiled.
1130 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1131 builds. It no longer runs mkdep(1) during 'make depend', and the
1132 'make depend' stage can safely be skipped now as it is auto ran
1133 when building 'make all' and will generate all SRCS and DPSRCS before
1134 building anything else. Dependencies are gathered at compile time with
1135 -MF flags kept in separate .depend files per object file. Users should
1136 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1137 stale .depend files.
1140 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1141 kernel modules. Therefore, if you load any kernel modules at boot time,
1142 please install the boot loaders after you install the kernel, but before
1146 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1147 make installkernel KERNCONF=YOUR_KERNEL_HERE
1148 make -C sys/boot install
1149 <reboot in single user>
1151 Then follow the usual steps, described in the General Notes section,
1155 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1156 see the 20141231 entry below for information about prerequisites and
1157 upgrading, if you are not already using clang 3.5.0 or higher.
1160 The AIO subsystem is now a standard part of the kernel. The
1161 VFS_AIO kernel option and aio.ko kernel module have been removed.
1162 Due to stability concerns, asynchronous I/O requests are only
1163 permitted on sockets and raw disks by default. To enable
1164 asynchronous I/O requests on all file types, set the
1165 vfs.aio.enable_unsafe sysctl to a non-zero value.
1168 The ELF object manipulation tool objcopy is now provided by the
1169 ELF Tool Chain project rather than by GNU binutils. It should be a
1170 drop-in replacement, with the addition of arm64 support. The
1171 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1172 to obtain the GNU version if necessary.
1175 Building ZFS pools on top of zvols is prohibited by default. That
1176 feature has never worked safely; it's always been prone to deadlocks.
1177 Using a zvol as the backing store for a VM guest's virtual disk will
1178 still work, even if the guest is using ZFS. Legacy behavior can be
1179 restored by setting vfs.zfs.vol.recursive=1.
1182 The NONE and HPN patches has been removed from OpenSSH. They are
1183 still available in the security/openssh-portable port.
1186 With the addition of ypldap(8), a new _ypldap user is now required
1187 during installworld. "mergemaster -p" can be used to add the user
1188 prior to installworld, as documented in the handbook.
1191 The tftp loader (pxeboot) now uses the option root-path directive. As a
1192 consequence it no longer looks for a pxeboot.4th file on the tftp
1193 server. Instead it uses the regular /boot infrastructure as with the
1197 The code to start recording plug and play data into the modules has
1198 been committed. While the old tools will properly build a new kernel,
1199 a number of warnings about "unknown metadata record 4" will be produced
1200 for an older kldxref. To avoid such warnings, make sure to rebuild
1201 the kernel toolchain (or world). Make sure that you have r292078 or
1202 later when trying to build 292077 or later before rebuilding.
1205 Debug data files are now built by default with 'make buildworld' and
1206 installed with 'make installworld'. This facilitates debugging but
1207 requires more disk space both during the build and for the installed
1208 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1212 r291527 changed the internal interface between the nfsd.ko and
1213 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1214 __FreeBSD_version has been bumped because of this.
1217 Add support for unicode collation strings leads to a change of
1218 order of files listed by ls(1) for example. To get back to the old
1219 behaviour, set LC_COLLATE environment variable to "C".
1221 Databases administrators will need to reindex their databases given
1222 collation results will be different.
1224 Due to a bug in install(1) it is recommended to remove the ancient
1225 locales before running make installworld.
1227 rm -rf /usr/share/locale/*
1230 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1231 libcrypto.so.7 or libssl.so.7 must be recompiled.
1234 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1235 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1236 should be replaced with isp_2400 and isp_2500 modules respectively.
1239 The build previously allowed using 'make -n' to not recurse into
1240 sub-directories while showing what commands would be executed, and
1241 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1242 and 'make -N' will not.
1245 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1246 and etcupdate will now use this file. A custom sendmail.cf is now
1247 updated via this mechanism rather than via installworld. If you had
1248 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1249 want to remove the exclusion or change it to "always install".
1250 /etc/mail/sendmail.cf is now managed the same way regardless of
1251 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1252 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1255 Compatibility shims for legacy ATA device names have been removed.
1256 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1257 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1258 environment variables, /dev/ad* and /dev/ar* symbolic links.
1261 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1262 Please see the 20141231 entry below for information about prerequisites
1263 and upgrading, if you are not already using clang 3.5.0 or higher.
1266 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1267 and renamed from .symbols to .debug. This reduces the size requirements
1268 on the boot partition or file system and provides consistency with
1269 userland debug files.
1271 When using the supported kernel installation method the
1272 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1273 as is done with /boot/kernel.
1275 Developers wishing to maintain the historical behavior of installing
1276 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1279 The wireless drivers had undergone changes that remove the 'parent
1280 interface' from the ifconfig -l output. The rc.d network scripts
1281 used to check presence of a parent interface in the list, so old
1282 scripts would fail to start wireless networking. Thus, etcupdate(3)
1283 or mergemaster(8) run is required after kernel update, to update your
1284 rc.d scripts in /etc.
1287 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1288 These configurations are now automatically interpreted as
1289 'scrub fragment reassemble'.
1292 Kernel-loadable modules for the random(4) device are back. To use
1293 them, the kernel must have
1296 options RANDOM_LOADABLE
1298 kldload(8) can then be used to load random_fortuna.ko
1299 or random_yarrow.ko. Please note that due to the indirect
1300 function calls that the loadable modules need to provide,
1301 the build-in variants will be slightly more efficient.
1303 The random(4) kernel option RANDOM_DUMMY has been retired due to
1304 unpopularity. It was not all that useful anyway.
1307 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1308 Control over building the ELF Tool Chain tools is now provided by
1309 the WITHOUT_TOOLCHAIN knob.
1312 The polarity of Pulse Per Second (PPS) capture events with the
1313 uart(4) driver has been corrected. Prior to this change the PPS
1314 "assert" event corresponded to the trailing edge of a positive PPS
1315 pulse and the "clear" event was the leading edge of the next pulse.
1317 As the width of a PPS pulse in a typical GPS receiver is on the
1318 order of 1 millisecond, most users will not notice any significant
1319 difference with this change.
1321 Anyone who has compensated for the historical polarity reversal by
1322 configuring a negative offset equal to the pulse width will need to
1323 remove that workaround.
1326 The default group assigned to /dev/dri entries has been changed
1327 from 'wheel' to 'video' with the id of '44'. If you want to have
1328 access to the dri devices please add yourself to the video group
1331 # pw groupmod video -m $USER
1334 The menu.rc and loader.rc files will now be replaced during
1335 upgrades. Please migrate local changes to menu.rc.local and
1336 loader.rc.local instead.
1339 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1340 strings and strip have been removed. The src.conf(5) knob
1341 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1344 As ZFS requires more kernel stack pages than is the default on some
1345 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1346 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1348 Please consider using 'options KSTACK_PAGES=X' where X is greater
1349 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1352 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1353 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1354 default, i.e., they will not contain "::". For example, instead
1355 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1356 to have a more specific match, such as different map entries for
1357 IPv6:0:0 vs IPv6:0. This change requires that configuration
1358 data (including maps, files, classes, custom ruleset, etc.) must
1359 use the same format, so make certain such configuration data is
1360 upgrading. As a very simple check search for patterns like
1361 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1362 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1363 the cf option UseCompressedIPv6Addresses.
1366 The default kernel entropy-processing algorithm is now
1367 Fortuna, replacing Yarrow.
1369 Assuming you have 'device random' in your kernel config
1370 file, the configurations allow a kernel option to override
1371 this default. You may choose *ONE* of:
1373 options RANDOM_YARROW # Legacy /dev/random algorithm.
1374 options RANDOM_DUMMY # Blocking-only driver.
1376 If you have neither, you get Fortuna. For most people,
1377 read no further, Fortuna will give a /dev/random that works
1378 like it always used to, and the difference will be irrelevant.
1380 If you remove 'device random', you get *NO* kernel-processed
1381 entropy at all. This may be acceptable to folks building
1382 embedded systems, but has complications. Carry on reading,
1383 and it is assumed you know what you need.
1385 *PLEASE* read random(4) and random(9) if you are in the
1386 habit of tweaking kernel configs, and/or if you are a member
1387 of the embedded community, wanting specific and not-usual
1388 behaviour from your security subsystems.
1390 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1391 random', you will NOT have a functioning /dev/random, and
1392 many cryptographic features will not work, including SSH.
1393 You may also find strange behaviour from the random(3) set
1394 of library functions, in particular sranddev(3), srandomdev(3)
1395 and arc4random(3). The reason for this is that the KERN_ARND
1396 sysctl only returns entropy if it thinks it has some to
1397 share, and with RANDOM_DUMMY or no 'device random' this
1401 An additional fix for the issue described in the 20150614 sendmail
1402 entry below has been committed in revision 284717.
1405 FreeBSD's old make (fmake) has been removed from the system. It is
1406 available as the devel/fmake port or via pkg install fmake.
1409 The fix for the issue described in the 20150614 sendmail entry
1410 below has been committed in revision 284436. The work
1411 around described in that entry is no longer needed unless the
1412 default setting is overridden by a confDH_PARAMETERS configuration
1413 setting of '5' or pointing to a 512 bit DH parameter file.
1416 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1417 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1418 and devel/kyua to version 0.20+ and adjust any calling code to work
1419 with Kyuafile and kyua.
1422 The import of openssl to address the FreeBSD-SA-15:10.openssl
1423 security advisory includes a change which rejects handshakes
1424 with DH parameters below 768 bits. sendmail releases prior
1425 to 8.15.2 (not yet released), defaulted to a 512 bit
1426 DH parameter setting for client connections. To work around
1427 this interoperability, sendmail can be configured to use a
1428 2048 bit DH parameter by:
1430 1. Edit /etc/mail/`hostname`.mc
1431 2. If a setting for confDH_PARAMETERS does not exist or
1432 exists and is set to a string beginning with '5',
1433 replace it with '2'.
1434 3. If a setting for confDH_PARAMETERS exists and is set to
1435 a file path, create a new file with:
1436 openssl dhparam -out /path/to/file 2048
1437 4. Rebuild the .cf file:
1438 cd /etc/mail/; make; make install
1439 5. Restart sendmail:
1440 cd /etc/mail/; make restart
1442 A sendmail patch is coming, at which time this file will be
1446 Generation of legacy formatted entries have been disabled by default
1447 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1448 entries were converted to use the new format by default when the new,
1449 machine independent format have been added and supported since FreeBSD
1452 Please see the pwd_mkdb(8) manual page for further details.
1455 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1456 20141231 entry below for information about prerequisites and upgrading,
1457 if you are not already using 3.5.0 or higher.
1460 TI platform code switched to using vendor DTS files and this update
1461 may break existing systems running on Beaglebone, Beaglebone Black,
1464 - dtb files should be regenerated/reinstalled. Filenames are the
1465 same but content is different now
1466 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1467 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1468 addressing scheme is now pin 25 on /dev/gpioc3.
1469 - Pandaboard: /etc/ttys should be updated, serial console device is
1470 now /dev/ttyu2, not /dev/ttyu0
1473 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1474 If you need the GNU extension from groff soelim(1), install groff
1475 from package: pkg install groff, or via ports: textproc/groff.
1478 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1479 defined in symlink(7); previously symlinks were silently ignored.
1482 The const qualifier has been removed from iconv(3) to comply with
1483 POSIX. The ports tree is aware of this from r384038 onwards.
1486 Libraries specified by LIBADD in Makefiles must have a corresponding
1487 DPADD_<lib> variable to ensure correct dependencies. This is now
1488 enforced in src.libnames.mk.
1491 From legacy ata(4) driver was removed support for SATA controllers
1492 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1493 Kernel modules ataahci and ataadaptec were removed completely,
1494 replaced by ahci and mvs modules respectively.
1497 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1498 the 20141231 entry below for information about prerequisites and
1499 upgrading, if you are not already using 3.5.0 or higher.
1502 The 32-bit PowerPC kernel has been changed to a position-independent
1503 executable. This can only be booted with a version of loader(8)
1504 newer than January 31, 2015, so make sure to update both world and
1505 kernel before rebooting.
1508 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1509 but before r278950, the RNG was not seeded properly. Immediately
1510 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1511 ssh keys or openssl keys) that were generated w/ a kernel from that
1512 range. This does not affect programs that directly used /dev/random
1513 or /dev/urandom. All userland uses of arc4random(3) are affected.
1516 The autofs(4) ABI was changed in order to restore binary compatibility
1517 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1518 with the new kernel.
1521 The powerpc64 kernel has been changed to a position-independent
1522 executable. This can only be booted with a new version of loader(8),
1523 so make sure to update both world and kernel before rebooting.
1526 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1527 only release, no new features have been added. Please see the 20141231
1528 entry below for information about prerequisites and upgrading, if you
1529 are not already using 3.5.0.
1532 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1533 taken from the ELF Tool Chain project rather than GNU binutils. They
1534 should be drop-in replacements, with the addition of arm64 support.
1535 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1536 binutils tools, if necessary. See 20150805 for updated information.
1539 The default Unbound configuration now enables remote control
1540 using a local socket. Users who have already enabled the
1541 local_unbound service should regenerate their configuration
1542 by running "service local_unbound setup" as root.
1545 The GNU texinfo and GNU info pages have been removed.
1546 To be able to view GNU info pages please install texinfo from ports.
1549 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1551 As of this release, a prerequisite for building clang, llvm and lldb is
1552 a C++11 capable compiler and C++11 standard library. This means that to
1553 be able to successfully build the cross-tools stage of buildworld, with
1554 clang as the bootstrap compiler, your system compiler or cross compiler
1555 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1556 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1559 On any standard FreeBSD 10.x or 11.x installation, where clang and
1560 libc++ are on by default (that is, on x86 or arm), this should work out
1563 On 9.x installations where clang is enabled by default, e.g. on x86 and
1564 powerpc, libc++ will not be enabled by default, so libc++ should be
1565 built (with clang) and installed first. If both clang and libc++ are
1566 missing, build clang first, then use it to build libc++.
1568 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1569 the instructions for 9.x above.
1571 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1572 default, and do not build clang.
1574 Many embedded systems are resource constrained, and will not be able to
1575 build clang in a reasonable time, or in some cases at all. In those
1576 cases, cross building bootable systems on amd64 is a workaround.
1578 This new version of clang introduces a number of new warnings, of which
1579 the following are most likely to appear:
1583 This warns in two cases, for both C and C++:
1584 * When the code is trying to take the absolute value of an unsigned
1585 quantity, which is effectively a no-op, and almost never what was
1586 intended. The code should be fixed, if at all possible. If you are
1587 sure that the unsigned quantity can be safely cast to signed, without
1588 loss of information or undefined behavior, you can add an explicit
1589 cast, or disable the warning.
1591 * When the code is trying to take an absolute value, but the called
1592 abs() variant is for the wrong type, which can lead to truncation.
1593 If you want to disable the warning instead of fixing the code, please
1594 make sure that truncation will not occur, or it might lead to unwanted
1597 -Wtautological-undefined-compare and
1598 -Wundefined-bool-conversion
1600 These warn when C++ code is trying to compare 'this' against NULL, while
1601 'this' should never be NULL in well-defined C++ code. However, there is
1602 some legacy (pre C++11) code out there, which actively abuses this
1603 feature, which was less strictly defined in previous C++ versions.
1605 Squid and openjdk do this, for example. The warning can be turned off
1606 for C++98 and earlier, but compiling the code in C++11 mode might result
1607 in unexpected behavior; for example, the parts of the program that are
1608 unreachable could be optimized away.
1611 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1612 kernel sources have been removed. The .h files remain, since some
1613 utilities include them. This will need to be fixed later.
1614 If "mount -t oldnfs ..." is attempted, it will fail.
1615 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1616 the utilities will report errors.
1619 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1620 directories to top level SUBDIR variable when their parent
1621 directory is included in LOCAL_DIRS. Users with build systems with
1622 such hierarchies and without SUBDIR entries in the parent
1623 directory Makefiles should add them or add the directories to
1627 faith(4) and faithd(8) have been removed from the base system. Faith
1628 has been obsolete for a very long time.
1631 vt(4), the new console driver, is enabled by default. It brings
1632 support for Unicode and double-width characters, as well as
1633 support for UEFI and integration with the KMS kernel video
1636 You may need to update your console settings in /etc/rc.conf,
1637 most probably the keymap. During boot, /etc/rc.d/syscons will
1638 indicate what you need to do.
1640 vt(4) still has issues and lacks some features compared to
1641 syscons(4). See the wiki for up-to-date information:
1642 https://wiki.freebsd.org/Newcons
1644 If you want to keep using syscons(4), you can do so by adding
1645 the following line to /boot/loader.conf:
1649 pjdfstest has been integrated into kyua as an opt-in test suite.
1650 Please see share/doc/pjdfstest/README for more details on how to
1654 gperf has been removed from the base system for architectures
1655 that use clang. Ports that require gperf will obtain it from the
1659 pjdfstest has been moved from tools/regression/pjdfstest to
1663 At svn r271982, The default linux compat kernel ABI has been adjusted
1664 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1665 update. If you wish to continue using the linux-f10 compat ports,
1666 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1667 encouraged to update their linux-compat packages to linux-c6 during
1668 their next update cycle.
1671 The ofwfb driver, used to provide a graphics console on PowerPC when
1672 using vt(4), no longer allows mmap() of all physical memory. This
1673 will prevent Xorg on PowerPC with some ATI graphics cards from
1674 initializing properly unless x11-servers/xorg-server is updated to
1678 The xdev targets have been converted to using TARGET and
1679 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1682 The default unbound configuration has been modified to address
1683 issues with reverse lookups on networks that use private
1684 address ranges. If you use the local_unbound service, run
1685 "service local_unbound setup" as root to regenerate your
1686 configuration, then "service local_unbound reload" to load the
1690 The GNU texinfo and GNU info pages are not built and installed
1691 anymore, WITH_INFO knob has been added to allow to built and install
1693 UPDATE: see 20150102 entry on texinfo's removal
1696 The GNU readline library is now an INTERNALLIB - that is, it is
1697 statically linked into consumers (GDB and variants) in the base
1698 system, and the shared library is no longer installed. The
1699 devel/readline port is available for third party software that
1703 The Itanium architecture (ia64) has been removed from the list of
1704 known architectures. This is the first step in the removal of the
1708 Commit r268115 has added NFSv4.1 server support, merged from
1709 projects/nfsv4.1-server. Since this includes changes to the
1710 internal interfaces between the NFS related modules, a full
1711 build of the kernel and modules will be necessary.
1712 __FreeBSD_version has been bumped.
1715 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1716 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1717 which differs from the behaviour controlled by this knob.)
1720 Maximal length of the serial number in CTL was increased from 16 to
1721 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1722 and ctld, need to be rebuilt to work with a new kernel.
1725 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1726 1 respectively to match the upstream numbers. They were out of
1727 sync because, when they were originally added to FreeBSD, the
1728 upstream versions were not respected. These libraries are private
1729 and not yet built by default, so renumbering them should be a
1730 non-issue. However, unclean source trees will yield broken test
1731 programs once the operator executes "make delete-old-libs" after a
1732 "make installworld".
1734 Additionally, the atf-sh binary was made private by moving it into
1735 /usr/libexec/. Already-built shell test programs will keep the
1736 path to the old binary so they will break after "make delete-old"
1739 If you are using WITH_TESTS=yes (not the default), wipe the object
1740 tree and rebuild from scratch to prevent spurious test failures.
1741 This is only needed once: the misnumbered libraries and misplaced
1742 binaries have been added to OptionalObsoleteFiles.inc so they will
1743 be removed during a clean upgrade.
1746 Clang and llvm have been upgraded to 3.4.1 release.
1749 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1750 be removed to avoid issues in the future (and has been added to
1754 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1755 past, it affected all builds that used the bsd.*.mk files. The old
1756 behavior was a bug, but people may have relied upon it. To get this
1757 behavior back, you can .include /etc/src.conf from /etc/make.conf
1758 (which is still global and isn't changed). This also changes the
1759 behavior of incremental builds inside the tree of individual
1760 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1761 Although this has survived make universe and some upgrade scenarios,
1762 other upgrade scenarios may have broken. At least one form of
1763 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1764 as well... In cases where MAKESYSPATH isn't working with this
1765 setting, you'll need to set it to the full path to your tree.
1767 One side effect of all this cleaning up is that bsd.compiler.mk
1768 is no longer implicitly included by bsd.own.mk. If you wish to
1769 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1773 The lindev device has been removed since /dev/full has been made a
1774 standard device. __FreeBSD_version has been bumped.
1777 The knob WITHOUT_VI was added to the base system, which controls
1778 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1779 in order to reorder files share/termcap and didn't build ex(1) as a
1780 build tool, so building/installing with WITH_VI is highly advised for
1781 build hosts for older releases.
1783 This issue has been fixed in stable/9 and stable/10 in r277022 and
1784 r276991, respectively.
1787 The YES_HESIOD knob has been removed. It has been obsolete for
1788 a decade. Please move to using WITH_HESIOD instead or your builds
1789 will silently lack HESIOD.
1792 The uart(4) driver has been changed with respect to its handling
1793 of the low-level console. Previously the uart(4) driver prevented
1794 any process from changing the baudrate or the CLOCAL and HUPCL
1795 control flags. By removing the restrictions, operators can make
1796 changes to the serial console port without having to reboot.
1797 However, when getty(8) is started on the serial device that is
1798 associated with the low-level console, a misconfigured terminal
1799 line in /etc/ttys will now have a real impact.
1800 Before upgrading the kernel, make sure that /etc/ttys has the
1801 serial console device configured as 3wire without baudrate to
1802 preserve the previous behaviour. E.g:
1803 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1806 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1807 to improve performance. To re-enable it, if needed, run rpcbind
1808 with command line option -W.
1811 Switched back to the GPL dtc compiler due to updates in the upstream
1812 dts files not being supported by the BSDL dtc compiler. You will need
1813 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1814 may result while building dtb files during a kernel build if you fail
1815 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1818 Clang and llvm have been upgraded to 3.4 release.
1821 The nve(4) driver has been removed. Please use the nfe(4) driver
1822 for NVIDIA nForce MCP Ethernet adapters instead.
1825 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1826 This could cause certain C++ applications using shared libraries built
1827 against the previous version of libc++ to crash. The incompatibility
1828 has now been fixed, but any C++ applications or shared libraries built
1829 between r261283 and r261801 should be recompiled.
1832 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1833 capability mode support. Please note that enabling the feature in
1834 kernel is still highly recommended.
1837 OpenSSH is now built with sandbox support, and will use sandbox as
1838 the default privilege separation method. This requires Capsicum
1839 capability mode support in kernel.
1842 The libelf and libdwarf libraries have been updated to newer
1843 versions from upstream. Shared library version numbers for
1844 these two libraries were bumped. Any ports or binaries
1845 requiring these two libraries should be recompiled.
1846 __FreeBSD_version is bumped to 1100006.
1849 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1850 instead of providing an explicit one, this would prevent such
1851 Makefile from providing its own Kyuafile in the future during
1852 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1853 intervention is needed to clean an objdir if you use NO_CLEAN:
1854 # find /usr/obj -name Kyuafile | xargs rm -f
1857 The behavior of gss_pseudo_random() for the krb5 mechanism
1858 has changed, for applications requesting a longer random string
1859 than produced by the underlying enctype's pseudo-random() function.
1860 In particular, the random string produced from a session key of
1861 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1862 be different at the 17th octet and later, after this change.
1863 The counter used in the PRF+ construction is now encoded as a
1864 big-endian integer in accordance with RFC 4402.
1865 __FreeBSD_version is bumped to 1100004.
1868 The WITHOUT_ATF build knob has been removed and its functionality
1869 has been subsumed into the more generic WITHOUT_TESTS. If you were
1870 using the former to disable the build of the ATF libraries, you
1871 should change your settings to use the latter.
1874 The default version of mtree is nmtree which is obtained from
1875 NetBSD. The output is generally the same, but may vary
1876 slightly. If you found you need identical output adding
1877 "-F freebsd9" to the command line should do the trick. For the
1878 time being, the old mtree is available as fmtree.
1881 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1882 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1883 1.1.4_8 and verify bsdyml not linked in, before running "make
1885 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1887 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1890 The stable/10 branch has been created in subversion from head
1897 Avoid using make -j when upgrading. While generally safe, there are
1898 sometimes problems using -j to upgrade. If your upgrade fails with
1899 -j, please try again without -j. From time to time in the past there
1900 have been problems using -j with buildworld and/or installworld. This
1901 is especially true when upgrading between "distant" versions (eg one
1902 that cross a major release boundary or several minor releases, or when
1903 several months have passed on the -current branch).
1905 Sometimes, obscure build problems are the result of environment
1906 poisoning. This can happen because the make utility reads its
1907 environment when searching for values for global variables. To run
1908 your build attempts in an "environmental clean room", prefix all make
1909 commands with 'env -i '. See the env(1) manual page for more details.
1911 When upgrading from one major version to another it is generally best to
1912 upgrade to the latest code in the currently installed branch first, then
1913 do an upgrade to the new branch. This is the best-tested upgrade path,
1914 and has the highest probability of being successful. Please try this
1915 approach if you encounter problems with a major version upgrade. Since
1916 the stable 4.x branch point, one has generally been able to upgrade from
1917 anywhere in the most recent stable branch to head / current (or even the
1918 last couple of stable branches). See the top of this file when there's
1921 When upgrading a live system, having a root shell around before
1922 installing anything can help undo problems. Not having a root shell
1923 around can lead to problems if pam has changed too much from your
1924 starting point to allow continued authentication after the upgrade.
1926 This file should be read as a log of events. When a later event changes
1927 information of a prior event, the prior event should not be deleted.
1928 Instead, a pointer to the entry with the new information should be
1929 placed in the old entry. Readers of this file should also sanity check
1930 older entries before relying on them blindly. Authors of new entries
1931 should write them with this in mind.
1935 When upgrading the boot ZFS pool to a new version, always follow
1938 1.) recompile and reinstall the ZFS boot loader and boot block
1939 (this is part of "make buildworld" and "make installworld")
1941 2.) update the ZFS boot block on your boot drive
1943 The following example updates the ZFS boot block on the first
1944 partition (freebsd-boot) of a GPT partitioned drive ada0:
1945 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1947 Non-boot pools do not need these updates.
1951 If you are updating from a prior version of FreeBSD (even one just
1952 a few days old), you should follow this procedure. It is the most
1953 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1955 make kernel-toolchain
1956 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1957 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1959 To test a kernel once
1960 ---------------------
1961 If you just want to boot a kernel once (because you are not sure
1962 if it works, or if you want to boot a known bad kernel to provide
1963 debugging information) run
1964 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1965 nextboot -k testkernel
1967 To rebuild everything and install it on the current system.
1968 -----------------------------------------------------------
1969 # Note: sometimes if you are running current you gotta do more than
1970 # is listed here if you are upgrading from a really old current.
1972 <make sure you have good level 0 dumps>
1974 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1975 make installkernel KERNCONF=YOUR_KERNEL_HERE
1977 <reboot in single user> [3]
1984 To cross-install current onto a separate partition
1985 --------------------------------------------------
1986 # In this approach we use a separate partition to hold
1987 # current's root, 'usr', and 'var' directories. A partition
1988 # holding "/", "/usr" and "/var" should be about 2GB in
1991 <make sure you have good level 0 dumps>
1994 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1995 <maybe newfs current's root partition>
1996 <mount current's root partition on directory ${CURRENT_ROOT}>
1997 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1998 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1999 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2000 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2001 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2002 <reboot into current>
2003 <do a "native" rebuild/install as described in the previous section>
2004 <maybe install compatibility libraries from ports/misc/compat*>
2008 To upgrade in-place from stable to current
2009 ----------------------------------------------
2010 <make sure you have good level 0 dumps>
2012 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2013 make installkernel KERNCONF=YOUR_KERNEL_HERE
2015 <reboot in single user> [3]
2022 Make sure that you've read the UPDATING file to understand the
2023 tweaks to various things you need. At this point in the life
2024 cycle of current, things change often and you are on your own
2025 to cope. The defaults can also change, so please read ALL of
2026 the UPDATING entries.
2028 Also, if you are tracking -current, you must be subscribed to
2029 freebsd-current@freebsd.org. Make sure that before you update
2030 your sources that you have read and understood all the recent
2031 messages there. If in doubt, please track -stable which has
2032 much fewer pitfalls.
2034 [1] If you have third party modules, such as vmware, you
2035 should disable them at this point so they don't crash your
2038 [3] From the bootblocks, boot -s, and then do
2042 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2043 cd src # full path to source
2044 adjkerntz -i # if CMOS is wall time
2045 Also, when doing a major release upgrade, it is required that
2046 you boot into single user mode to do the installworld.
2048 [4] Note: This step is non-optional. Failure to do this step
2049 can result in a significant reduction in the functionality of the
2050 system. Attempting to do it by hand is not recommended and those
2051 that pursue this avenue should read this file carefully, as well
2052 as the archives of freebsd-current and freebsd-hackers mailing lists
2053 for potential gotchas. The -U option is also useful to consider.
2054 See mergemaster(8) for more information.
2056 [5] Usually this step is a no-op. However, from time to time
2057 you may need to do this if you get unknown user in the following
2058 step. It never hurts to do it all the time. You may need to
2059 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2060 install) after the buildworld before this step if you last updated
2061 from current before 20130425 or from -stable before 20130430.
2063 [6] This only deletes old files and directories. Old libraries
2064 can be deleted by "make delete-old-libs", but you have to make
2065 sure that no program is using those libraries anymore.
2067 [8] The new kernel must be able to run existing binaries used by an
2068 installworld. When upgrading across major versions, the new kernel's
2069 configuration must include the correct COMPAT_FREEBSD<n> option for
2070 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2071 to do so may leave you with a system that is hard to boot to recover. A
2072 GENERIC kernel will include suitable compatibility options to run
2073 binaries from older branches. Note that the ability to run binaries
2074 from unsupported branches is not guaranteed.
2076 Make sure that you merge any new devices from GENERIC since the
2077 last time you updated your kernel config file. Options also
2078 change over time, so you may need to adjust your custom kernels
2081 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2082 "?=" instead of the "=" assignment operator, so that buildworld can
2083 override the CPUTYPE if it needs to.
2085 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2086 not on the command line, or in /etc/make.conf. buildworld will
2087 warn if it is improperly defined.
2090 This file contains a list, in reverse chronological order, of major
2091 breakages in tracking -current. It is not guaranteed to be a complete
2092 list of such breakages, and only contains entries since September 23, 2011.
2093 If you need to see UPDATING entries from before that date, you will need
2094 to fetch an UPDATING file from an older FreeBSD release.
2096 Copyright information:
2098 Copyright 1998-2009 M. Warner Losh.
2100 Redistribution, publication, translation and use, with or without
2101 modification, in full or in part, in any form or format of this
2102 document are permitted without further permission from the author.
2104 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2105 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2106 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2107 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2108 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2109 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2110 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2111 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2112 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2113 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2114 POSSIBILITY OF SUCH DAMAGE.
2116 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob