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