1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
20 FreeBSD 13.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 A fix was applied to i386 kernel modules to avoid panics with
36 dpcpu or vnet. Users need to recompile i386 kernel modules
37 having pcpu or vnet sections or they will refuse to load.
40 User-wired pages now have their own counter,
41 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
42 to vm.max_user_wired and changed from an unsigned int to an unsigned
43 long. bhyve VMs wired with the -S are now subject to the user
44 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
45 avoid running into the limit.
48 The IPSEC option has been removed from GENERIC. Users requiring
49 ipsec(4) must now load the ipsec(4) kernel module.
52 The tap(4) driver has been folded into tun(4), and the module has been
53 renamed to tuntap. You should update any kld_load="if_tap" or
54 kld_load="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
55 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
56 module instead, and "device tap" or "device tun" entries in kernel
57 config files to select the tuntap device instead.
60 The following knobs have been added related to tradeoffs between
61 safe use of the random device and availability in the absence of
64 kern.random.initial_seeding.bypass_before_seeding: tunable; set
65 non-zero to bypass the random device prior to seeding, or zero to
66 block random requests until the random device is initially seeded.
67 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
68 availability properties.
70 kern.random.initial_seeding.read_random_bypassed_before_seeding:
71 read-only diagnostic sysctl that is set when bypass is enabled and
72 read_random(9) is bypassed, to enable programmatic handling of this
73 initial condition, if desired.
75 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
76 Similar to the above, but for for arc4random(9) initial seeding.
78 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
79 non-zero to disable warnings in dmesg when the same conditions are
80 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
81 produce warnings in dmesg when the conditions are met.
84 The loadable random module KPI has changed; the random_infra_init()
85 routine now requires a 3rd function pointer for a bool (*)(void)
86 method that returns true if the random device is seeded (and
90 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
91 built from head sources between r320757 (July 6, 2017) and
92 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
93 is added to the command line.
94 nfsuserd daemons built from head sources that are post-r338192 are
95 not affected and should continue to work.
98 The fuse(4) module has been renamed to fusefs(4) for consistency with
99 other filesystems. You should update any kld_load="fuse" entries in
100 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
101 "options FUSE" entries in kernel config files.
104 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
105 8.0.0. Please see the 20141231 entry below for information about
106 prerequisites and upgrading, if you are not already using clang 3.5.0
110 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
111 compiled into your custom kernel, add 'device xz' statement to the
115 drm and drm2 have been removed from the tree. Please see
116 https://wiki.freebsd.org/Graphics for the latest information on
117 migrating to the drm ports.
120 Iflib is no longer unconditionally compiled into the kernel. Drivers
121 using iflib and statically compiled into the kernel, now require
122 the 'device iflib' config option. For the same drivers loaded as
123 modules on kernels not having 'device iflib', the iflib.ko module
124 is loaded automatically.
127 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
128 options no longer exist since r343219 and r343427 respectively;
129 nothing uses them, so they should be just removed from custom
133 r342635 changes the way efibootmgr(8) works by requiring users to add
134 the -b (bootnum) parameter for commands where the bootnum was previously
135 specified with each option. For example 'efibootmgr -B 0001' is now
136 'efibootmgr -B -b 0001'.
139 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
140 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
141 servers that have vfs.nfsd.nfs_privport set will only allow mounts
142 from clients using a reserved port#. Since both the FreeBSD and Linux
143 NFSv4 clients use reserved port#s by default, this should not affect
147 The XLP config has been removed. We can't support 64-bit atomics in this
148 kernel because it is running in 32-bit mode. XLP users must transition
149 to running a 64-bit kernel (XLP64 or XLPN32).
151 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
152 the preferred emulator today and we don't need two different ones.
154 The old sibyte / swarm / Broadcom BCM1250 support has been
155 removed from the mips port.
158 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
159 7.0.1. Please see the 20141231 entry below for information about
160 prerequisites and upgrading, if you are not already using clang 3.5.0
164 Remove the timed and netdate programs from the base tree. Setting
165 the time with these daemons has been obsolete for over a decade.
168 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
169 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
170 it produces broken binaries when ifuncs are in use. Users needing
171 GNU ld should install the binutils port or package.
174 The BSD crtbegin and crtend code has been enabled by default. It has
175 had extensive testing on amd64, arm64, and i386. It can be disabled
176 by building a world with -DWITHOUT_BSD_CRTBEGIN.
179 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
180 has been converted to a port (misc/ctm) and will be removed from
181 FreeBSD-13. It is available as a package (ctm) for all supported
185 The default newsyslog.conf(5) file has been changed to only include
186 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
187 the filenames end in '.conf' and do not begin with a '.'.
189 You should check the configuration files in these two directories match
190 this naming convention. You can verify which configuration files are
191 being included using the command:
195 Ports for the DRM modules have been simplified. Now, amd64 users should
196 just install the drm-kmod port. All others should install
199 Graphics hardware that's newer than about 2010 usually works with
200 drm-kmod. For hardware older than 2013, however, some users will need
201 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
202 than 2008 usually only works in drm-legacy-kmod. The graphics team can
203 only commit to hardware made since 2013 due to the complexity of the
204 market and difficulty to test all the older cards effectively. If you
205 have hardware supported by drm-kmod, you are strongly encouraged to use
206 that as you will get better support.
208 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
209 elsewhere, the drm and drm2 modules will be eliminated from the src base
210 soon (with a limited exception for arm). Please update to the package
211 asap and report any issues to x11@freebsd.org.
213 Generally, anybody using the drm*-kmod packages should add
214 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
215 cross-threading surprises, especially with automatic driver
216 loading from X11 startup. These will become the defaults in 13-current
220 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
221 custom kernel and module loading configuration files must be updated
222 accordingly. Moreover, interfaces previous presented as ixlvN to the
223 system are now exposed as iavfN and network configuration files must
224 be adjusted as necessary.
227 OpenSSL has been updated to version 1.1.1. This update included
228 additional various API changes throughout the base system. It is
229 important to rebuild third-party software after upgrading. The value
230 of __FreeBSD_version has been bumped accordingly.
233 The legacy DRM modules and drivers have now been added to the loader's
234 module blacklist, in favor of loading them with kld_list in rc.conf(5).
235 The module blacklist may be overridden with the loader.conf(5)
236 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
240 The cam(4) based nda(4) driver will be used over nvd(4) by default on
241 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
242 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
243 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
247 Reproducible build mode is now on by default, in preparation for
248 FreeBSD 12.0. This eliminates build metadata such as the user,
249 host, and time from the kernel (and uname), unless the working tree
250 corresponds to a modified checkout from a version control system.
251 The previous behavior can be obtained by setting the /etc/src.conf
252 knob WITHOUT_REPRODUCIBLE_BUILD.
255 The Yarrow CSPRNG has been removed from the kernel as it has not been
256 supported by its designers since at least 2003. Fortuna has been the
257 default since FreeBSD-11.
260 devctl freeze/thaw have gone into the tree, the rc scripts have been
261 updated to use them and devmatch has been changed. You should update
262 kernel, userland and rc scripts all at the same time.
265 The default interpreter has been switched from 4th to Lua.
266 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
267 interpreter. If you have custom FORTH code you will need to set
268 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
269 src.conf for the build. This will create default hard links between
270 loader and loader_4th instead of loader and loader_lua, the new default.
271 If you are using UEFI it will create the proper hard link to loader.efi.
273 bhyve uses userboot.so. It remains 4th-only until some issues are solved
274 regarding coexisting with multiple versions of FreeBSD are resolved.
277 ls(1) now respects the COLORTERM environment variable used in other
278 systems and software to indicate that a colored terminal is both
279 supported and desired. If ls(1) is suddenly emitting colors, they may
280 be disabled again by either removing the unwanted COLORTERM from your
281 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
282 may not be observed in a future release.
285 The default pager for most commands has been changed to "less". To
286 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
290 The jedec_ts(4) driver has been removed. A superset of its functionality
291 is available in the jedec_dimm(4) driver, and the manpage for that
292 driver includes migration instructions. If you have "device jedec_ts"
293 in your kernel configuration file, it must be removed.
296 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
297 This should have no effect if the kernel is booted via BIOS/legacy boot.
298 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
299 has a buggy firmware that prevents a successful boot due to use of
303 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
304 support has been removed from the tree. These ports were
305 obsolete and/or known to be broken for many years.
308 loader.efi has been augmented to participate more fully in the
309 UEFI boot manager protocol. loader.efi will now look at the
310 BootXXXX environment variable to determine if a specific kernel
311 or root partition was specified. XXXX is derived from BootCurrent.
312 efibootmgr(8) manages these standard UEFI variables.
315 zfsloader's functionality has now been folded into loader.
316 zfsloader is no longer necessary once you've updated your
317 boot blocks. For a transition period, we will install a
318 hardlink for zfsloader to loader to allow a smooth transition
319 until the boot blocks can be updated (hard link because old
320 zfs boot blocks don't understand symlinks).
323 ARM64 now have efifb support, if you want to have serial console
324 on your arm64 board when an screen is connected and the bootloader
325 setup a frame buffer for us to use, just add :
329 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
330 an screen connected as the firmware will setup a frame buffer are that
331 u-boot will expose as an EFI frame buffer.
334 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
335 or take steps to update /etc/passwd before doing installworld on
336 existing systems. Do not skip the "mergemaster -Fp" step before
337 installworld, as described in the update procedures near the bottom
338 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
339 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
340 the ntp config file contain options that change file/dir locations.
341 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
342 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
343 taking steps to ensure that all required files/dirs are accessible
347 Big endian arm support has been removed.
350 The static environment setup in kernel configs is no longer mutually
351 exclusive with the loader(8) environment by default. In order to
352 restore the previous default behavior of disabling the loader(8)
353 environment if a static environment is present, you must specify
354 loader_env.disabled=1 in the static environment.
357 The ABI of syscalls used by management tools like sockstat and
358 netstat has been broken to allow 32-bit binaries to work on
359 64-bit kernels without modification. These programs will need
360 to match the kernel in order to function. External programs may
361 require minor modifications to accommodate a change of type in
362 structures from pointers to 64-bit virtual addresses.
365 On i386 and amd64 atomics are now inlined. Out of tree modules using
366 atomics will need to be rebuilt.
369 The '%I' format in the kern.corefile sysctl limits the number of
370 core files that a process can generate to the number stored in the
371 debug.ncores sysctl. The '%I' format is replaced by the single digit
372 index. Previously, if all indexes were taken the kernel would overwrite
373 only a core file with the highest index in a filename.
374 Currently the system will create a new core file if there is a free
375 index or if all slots are taken it will overwrite the oldest one.
378 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
379 6.0.1. Please see the 20141231 entry below for information about
380 prerequisites and upgrading, if you are not already using clang 3.5.0
384 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
385 needed to be changed to work with it. This change was made with r335763
386 and requires a mergemaster / etcupdate / etc to update the installed
390 r334930 changed the interface between the NFS modules, so they all
391 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
394 As of r334391 lld is the default amd64 system linker; it is installed
395 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
399 The kernel / userland interface for devinfo changed, so you'll
400 need a new kernel and userland as a pair for it to work (rebuilding
401 lib/libdevinfo is all that's required). devinfo and devmatch will
402 not work, but everything else will when there's a mismatch.
405 The on-disk format for hwpmc callchain records has changed to include
406 threadid corresponding to a given record. This changes the field offsets
407 and thus requires that libpmcstat be rebuilt before using a kernel
411 The vxge(4) driver has been removed. This driver was introduced into
412 HEAD one week before the Exar left the Ethernet market and is not
413 known to be used. If you have device vxge in your kernel config file
417 The amd64 kernel now requires a ld that supports ifunc to produce a
418 working kernel, either lld or a newer binutils. lld is built by default
419 on amd64, and the 'buildkernel' target uses it automatically. However,
420 it is not the default linker, so building the kernel the traditional
421 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
422 binutils port/package). lld will soon be default, and this requirement
425 NOTE: As of r334391 lld is the default system linker on amd64, and no
426 workaround is necessary.
429 The nxge(4) driver has been removed. This driver was for PCI-X 10g
430 cards made by s2io/Neterion. The company was acquired by Exar and
431 no longer sells or supports Ethernet products. If you have device
432 nxge in your kernel config file it must be removed.
435 The tz database (tzdb) has been updated to 2018e. This version more
436 correctly models time stamps in time zones with negative DST such as
437 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
438 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
439 time zone abbreviations and the tm_isdst flag.
442 The ixgb(4) driver has been removed. This driver was for an early and
443 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
444 quickly shifted to the long lived ixgbe family. If you have device
445 ixgb in your kernel config file it must be removed.
448 The lmc(4) driver has been removed. This was a WAN interface
449 card that was already reportedly rare in 2003, and had an ambiguous
450 license. If you have device lmc in your kernel config file it must
454 Support for Arcnet networks has been removed. If you have device
455 arcnet or device cm in your kernel config file they must be
459 Support for FDDI networks has been removed. If you have device
460 fddi or device fpa in your kernel config file they must be
464 In addition to supporting RFC 3164 formatted messages, the
465 syslogd(8) service is now capable of parsing RFC 5424 formatted
466 log messages. The main benefit of using RFC 5424 is that clients
467 may now send log messages with timestamps containing year numbers,
468 microseconds and time zone offsets.
470 Similarly, the syslog(3) C library function has been altered to
471 send RFC 5424 formatted messages to the local system logging
472 daemon. On systems using syslogd(8), this change should have no
473 negative impact, as long as syslogd(8) and the C library are
474 updated at the same time. On systems using a different system
475 logging daemon, it may be necessary to make configuration
476 adjustments, depending on the software used.
478 When using syslog-ng, add the 'syslog-protocol' flag to local
479 input sources to enable parsing of RFC 5424 formatted messages:
482 unix-dgram("/var/run/log" flags(syslog-protocol));
485 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
486 of the 'imuxsock' module to let messages be processed by the
487 regular RFC 3164/5424 parsing pipeline:
489 module(load="imuxsock" SysSock.UseSpecialParser="off")
491 Do note that these changes only affect communication between local
492 applications and syslogd(8). The format that syslogd(8) uses to
493 store messages on disk or forward messages to other systems
494 remains unchanged. syslogd(8) still uses RFC 3164 for these
495 purposes. Options to customize this behaviour will be added in the
496 future. Utilities that process log files stored in /var/log are
497 thus expected to continue to function as before.
499 __FreeBSD_version has been incremented to 1200061 to denote this
503 Support for token ring networks has been removed. If you
504 have "device token" in your kernel config you should remove
505 it. No device drivers supported token ring.
508 makefs was modified to be able to tag ISO9660 El Torito boot catalog
509 entries as EFI instead of overloading the i386 tag as done previously.
510 The amd64 mkisoimages.sh script used to build amd64 ISO images for
511 release was updated to use this. This may mean that makefs must be
512 updated before "make cdrom" can be run in the release directory. This
513 should be as simple as:
515 $ cd $SRCDIR/usr.sbin/makefs
516 $ make depend all install
519 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
520 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
521 Co-existence for the transition period will come shortly. Booting is a
522 complex environment and test coverage for Lua-enabled loaders has been
523 thin, so it would be prudent to assume it might not work and make
524 provisions for backup boot methods.
527 devmatch functionality has been turned on in devd. It will automatically
528 load drivers for unattached devices. This may cause unexpected drivers
529 to be loaded. Please report any problems to current@ and
533 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
534 6.0.0. Please see the 20141231 entry below for information about
535 prerequisites and upgrading, if you are not already using clang 3.5.0
539 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
540 This means it is used to link the kernel and userland libraries and
541 executables, but is not yet installed as /usr/bin/ld by default.
543 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
544 WITHOUT_LLD_BOOTSTRAP=yes
547 On i386, pmtimer has been removed. Its functionality has been folded
548 into apm. It was a no-op on ACPI in current for a while now (but was
549 still needed on i386 in FreeBSD 11 and earlier). Users may need to
550 remove it from kernel config files.
553 The use of RSS hash from the network card aka flowid has been
554 disabled by default for lagg(4) as it's currently incompatible with
555 the lacp and loadbalance protocols.
557 This can be re-enabled by setting the following in loader.conf:
558 net.link.lagg.default_use_flowid="1"
561 The SW_WATCHDOG option is no longer necessary to enable the
562 hardclock-based software watchdog if no hardware watchdog is
563 configured. As before, SW_WATCHDOG will cause the software
564 watchdog to be enabled even if a hardware watchdog is configured.
567 r326887 fixes the issue described in the 20171214 UPDATING entry.
568 r326888 flips the switch back to building GELI support always.
571 r362593 broke ZFS + GELI support for reasons unknown. However,
572 it also broke ZFS support generally, so GELI has been turned off
573 by default as the lesser evil in r326857. If you boot off ZFS and/or
574 GELI, it might not be a good time to update.
577 PowerPC users must update loader(8) by rebuilding world before
578 installing a new kernel, as the protocol connecting them has
579 changed. Without the update, loader metadata will not be passed
580 successfully to the kernel and users will have to enter their
581 root partition at the kernel mountroot prompt to continue booting.
582 Newer versions of loader can boot old kernels without issue.
585 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
586 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
587 to WITH/OUT_LOADER_GELI.
590 The naive and non-compliant support of posix_fallocate(2) in ZFS
591 has been removed as of r325320. The system call now returns EINVAL
592 when used on a ZFS file. Although the new behavior complies with the
593 standard, some consumers are not prepared to cope with it.
594 One known victim is lld prior to r325420.
597 Building in a FreeBSD src checkout will automatically create object
598 directories now rather than store files in the current directory if
599 'make obj' was not ran. Calling 'make obj' is no longer necessary.
600 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
601 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
605 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
606 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
607 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
608 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
609 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
610 The UNIFIED_OBJDIR option is a transitional feature that will be
611 removed for 12.0 release; please migrate to the new format for any
612 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
613 than hardcoding paths.
616 The native-xtools target no longer installs the files by default to the
617 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
618 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
621 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
622 options are changing from controlling the build if defined / undefined
623 to controlling the build with explicit 'yes' or 'no' values. They will
624 shift to WITH/WITHOUT options to match other options in the system.
627 libstand has turned into a private library for sys/boot use only.
628 It is no longer supported as a public interface outside of sys/boot.
631 The arm port has split armv6 into armv6 and armv7. armv7 is now
632 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
633 and are running a kernel from before r324363, you will need to add
634 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
637 When building multiple kernels using KERNCONF, non-existent KERNCONF
638 files will produce an error and buildkernel will fail. Previously
639 missing KERNCONF files silently failed giving no indication as to
640 why, only to subsequently discover during installkernel that the
641 desired kernel was never built in the first place.
644 The default serial number format for CTL LUNs has changed. This will
645 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
646 or iSCSI clients care about their LUNs' serial numbers. Users who
647 require serial number stability should hardcode serial numbers in
651 For 32-bit arm compiled for hard-float support, soft-floating point
652 binaries now always get their shared libraries from
653 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
654 /usr/libsoft also existed). Only users with a hard-float ld.so, but
655 soft-float everything else should be affected.
658 The geli password typed at boot is now hidden. To restore the previous
659 behavior, see geli(8) for configuration options.
662 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
663 sysctl values. Minor nit, but requires a rebuild of both world/kernel
667 "make check" behavior (made in ^/head@r295380) has been changed to
668 execute from a limited sandbox, as opposed to executing from
672 - The "beforecheck" and "aftercheck" targets are now specified.
673 - ${CHECKDIR} (added in commit noted above) has been removed.
674 - Legacy behavior can be enabled by setting
675 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
677 If the limited sandbox mode is enabled, "make check" will execute
678 "make distribution", then install, execute the tests, and clean up the
679 sandbox if successful.
681 The "make distribution" and "make install" targets are typically run as
682 root to set appropriate permissions and ownership at installation time.
683 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
684 environment if executing "make check" with limited sandbox mode using
685 an unprivileged user.
688 Since the switch to GPT disk labels, fsck for UFS/FFS has been
689 unable to automatically find alternate superblocks. As of r322297,
690 the information needed to find alternate superblocks has been
691 moved to the end of the area reserved for the boot block.
692 Filesystems created with a newfs of this vintage or later
693 will create the recovery information. If you have a filesystem
694 created prior to this change and wish to have a recovery block
695 created for your filesystem, you can do so by running fsck in
696 foreground mode (i.e., do not use the -p or -y options). As it
697 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
698 to which you should answer yes.
701 As of r321665, an NFSv4 server configuration that services
702 Kerberos mounts or clients that do not support the uid/gid in
703 owner/owner_group string capability, must explicitly enable
704 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
705 machine's /etc/rc.conf file.
708 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
709 Please see the 20141231 entry below for information about prerequisites
710 and upgrading, if you are not already using clang 3.5.0 or higher.
713 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
714 r-commands (rlogin, rsh, etc.) to be built with the base system.
717 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
718 a very major ABI incompatible change, so users of FreeBSD/powerpc must
719 be careful when performing source upgrades. It is best to run
720 'make installworld' from an alternate root system, either a live
721 CD/memory stick, or a temporary root partition. Additionally, all ports
722 must be recompiled. powerpc64 is largely unaffected, except in the case
723 of 32-bit compatibility. All 32-bit binaries will be affected.
726 Forward compatibility for the "ino64" project have been committed. This
727 will allow most new binaries to run on older kernels in a limited
728 fashion. This prevents many of the common foot-shooting actions in the
729 upgrade as well as the limited ability to roll back the kernel across
730 the ino64 upgrade. Complicated use cases may not work properly, though
731 enough simpler ones work to allow recovery in most situations.
734 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
735 if you require the GPL compiler.
738 The internal ABI used for communication between the NFS kernel modules
739 was changed by r320085, so __FreeBSD_version was bumped to
740 ensure all the NFS related modules are updated together.
743 The ABI of struct event was changed by extending the data
744 member to 64bit and adding ext fields. For upgrade, same
745 precautions as for the entry 20170523 "ino64" must be
749 The GNU roff toolchain has been removed from base. To render manpages
750 which are not supported by mandoc(1), man(1) can fallback on GNU roff
751 from ports (and recommends to install it).
752 To render roff(7) documents, consider using GNU roff from ports or the
753 heirloom doctools roff toolchain from ports via pkg install groff or
754 via pkg install heirloom-doctools.
757 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
758 smaller runtime footprint builds. This is useful for embedded systems
759 which only require one chipset support.
761 If you load it as a module, make sure this is in /boot/loader.conf:
765 This will load the HAL, all chip/RF backends and if_ath_pci.
766 If you have if_ath_pci in /boot/loader.conf, ensure it is after
767 if_ath or it will not load any HAL chipset support.
769 If you want to selectively load things (eg on ye cheape ARM/MIPS
770 platforms where RAM is at a premium) you should:
773 * load the chip modules in question
774 * load ath_rate, ath_dfs
776 * load if_ath_pci and/or if_ath_ahb depending upon your particular
777 bus bind type - this is where probe/attach is done.
779 For further comments/feedback, poke adrian@ .
782 The "ino64" 64-bit inode project has been committed, which extends
783 a number of types to 64 bits. Upgrading in place requires care and
784 adherence to the documented upgrade procedure.
786 If using a custom kernel configuration ensure that the
787 COMPAT_FREEBSD11 option is included (as during the upgrade the
788 system will be running the ino64 kernel with the existing world).
790 For the safest in-place upgrade begin by removing previous build
791 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
792 procedure documented below under the heading "To rebuild everything and
793 install it on the current system." Specifically, a reboot is required
794 after installing the new kernel before installing world. While an
795 installworld normally works by accident from multiuser after rebooting
796 the proper kernel, there are many cases where this will fail across this
797 upgrade and installworld from single user is required.
800 The NATM framework including the en(4), fatm(4), hatm(4), and
801 patm(4) devices has been removed. Consumers should plan a
802 migration before the end-of-life date for FreeBSD 11.
805 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
806 diff has not been implemented, if those are needed a newer version of
807 GNU diff is available via the diffutils package under the gdiff name.
810 As of r316810 for ipfilter, keep frags is no longer assumed when
811 keep state is specified in a rule. r316810 aligns ipfilter with
812 documentation in man pages separating keep frags from keep state.
813 This allows keep state to be specified without forcing keep frags
814 and allows keep frags to be specified independently of keep state.
815 To maintain previous behaviour, also specify keep frags with
816 keep state (as documented in ipf.conf.5).
819 arm64 builds now use the base system LLD 4.0.0 linker by default,
820 instead of requiring that the aarch64-binutils port or package be
821 installed. To continue using aarch64-binutils, set
822 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
825 The UDP optimization in entry 20160818 that added the sysctl
826 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
827 packets will no longer be treated as L3 broadcast packets.
830 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
831 use any explicitly assigned loopback address available in the jail
832 instead of using the first assigned address of the jail.
835 The ctl.ko module no longer implements the iSCSI target frontend:
836 cfiscsi.ko does instead.
838 If building cfiscsi.ko as a kernel module, the module can be loaded
839 via one of the following methods:
840 - `cfiscsi_load="YES"` in loader.conf(5).
841 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
842 - ctladm(8)/ctld(8), when compiled with iSCSI support
843 (`WITH_ISCSI=yes` in src.conf(5))
845 Please see cfiscsi(4) for more details.
848 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
849 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
850 same source (previously, the dependency of mmcsd.ko on mmc.ko was
851 missing, but mmcsd.ko now will refuse to load if it is incompatible
855 The syntax of ipfw(8) named states was changed to avoid ambiguity.
856 If you have used named states in the firewall rules, you need to modify
857 them after installworld and before rebooting. Now named states must
858 be prefixed with colon.
861 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
862 removed as the userland we provide cannot use them. The KMS version
863 (sys/dev/drm2) supports the same hardware.
866 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
867 Please see the 20141231 entry below for information about prerequisites
868 and upgrading, if you are not already using clang 3.5.0 or higher.
871 The code that provides support for ZFS .zfs/ directory functionality
872 has been reimplemented. It's not possible now to create a snapshot
873 by mkdir under .zfs/snapshot/. That should be the only user visible
877 EISA bus support has been removed. The WITH_EISA option is no longer
881 MCA bus support has been removed.
884 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
885 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
888 The EM_MULTIQUEUE kernel configuration option is deprecated now that
889 the em(4) driver conforms to iflib specifications.
892 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
893 IFLIB. If you have a custom kernel configuration that excludes em(4)
894 but you use igb(4), you need to re-add em(4) to your custom
898 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
899 Please see the 20141231 entry below for information about prerequisites
900 and upgrading, if you are not already using clang 3.5.0 or higher.
903 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
904 Please see the 20141231 entry below for information about prerequisites
905 and upgrading, if you are not already using clang 3.5.0 or higher.
908 The layout of the pmap structure has changed for powerpc to put the pmap
909 statistics at the front for all CPU variations. libkvm(3) and all tools
910 that link against it need to be recompiled.
913 isl(4) and cyapa(4) drivers now require a new driver,
914 chromebook_platform(4), to work properly on Chromebook-class hardware.
915 On other types of hardware the drivers may need to be configured using
916 device hints. Please see the corresponding manual pages for details.
919 The urtwn(4) driver was merged into rtwn(4) and now consists of
920 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
922 Also, firmware for RTL8188CE was renamed due to possible name
923 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
926 GNU rcs has been removed from base. It is available as packages:
927 - rcs: Latest GPLv3 GNU rcs version.
928 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
932 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
933 modules now requires that the kernel configuration contain the
934 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
937 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
938 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
941 Relocatable object files with the extension of .So have been renamed
942 to use an extension of .pico instead. The purpose of this change is
943 to avoid a name clash with shared libraries on case-insensitive file
944 systems. On those file systems, foo.So is the same file as foo.so.
947 GNU rcs has been turned off by default. It can (temporarily) be built
948 again by adding WITH_RCS knob in src.conf.
949 Otherwise, GNU rcs is available from packages:
950 - rcs: Latest GPLv3 GNU rcs version.
951 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
954 The backup_uses_rcs functionality has been removed from rc.subr.
957 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
958 two separate components, QUEUE_MACRO_DEBUG_TRACE and
959 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
960 QUEUE_MACRO_DEBUG behavior.
963 r304787 changed some ioctl interfaces between the iSCSI userspace
964 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
965 rebuilt to work with new kernels. __FreeBSD_version has been bumped
969 The UDP receive code has been updated to only treat incoming UDP
970 packets that were addressed to an L2 broadcast address as L3
971 broadcast packets. It is not expected that this will affect any
972 standards-conforming UDP application. The new behaviour can be
973 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
977 Remove the openbsd_poll system call.
978 __FreeBSD_version has been bumped because of this.
981 The stable/11 branch has been created from head@r302406.
984 The libc stub for the pipe(2) system call has been replaced with
985 a wrapper that calls the pipe2(2) system call and the pipe(2)
986 system call is now only implemented by the kernels that include
987 "options COMPAT_FREEBSD10" in their config file (this is the
988 default). Users should ensure that this option is enabled in
989 their kernel or upgrade userspace to r302092 before upgrading their
993 CAM will now strip leading spaces from SCSI disks' serial numbers.
994 This will affect users who create UFS filesystems on SCSI disks using
995 those disk's diskid device nodes. For example, if /etc/fstab
996 previously contained a line like
997 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
998 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
999 transforms like gmirror may also be affected. ZFS users should
1003 The bitstring(3) API has been updated with new functionality and
1004 improved performance. But it is binary-incompatible with the old API.
1005 Objects built with the new headers may not be linked against objects
1006 built with the old headers.
1009 The brk and sbrk functions have been removed from libc on arm64.
1010 Binutils from ports has been updated to not link to these
1011 functions and should be updated to the latest version before
1012 installing a new libc.
1015 The armv6 port now defaults to hard float ABI. Limited support
1016 for running both hardfloat and soft float on the same system
1017 is available using the libraries installed with -DWITH_LIBSOFT.
1018 This has only been tested as an upgrade path for installworld
1019 and packages may fail or need manual intervention to run. New
1020 packages will be needed.
1022 To update an existing self-hosted armv6hf system, you must add
1023 TARGET_ARCH=armv6 on the make command line for both the build
1024 and the install steps.
1027 Kernel modules compiled outside of a kernel build now default to
1028 installing to /boot/modules instead of /boot/kernel. Many kernel
1029 modules built this way (such as those in ports) already overrode
1030 KMODDIR explicitly to install into /boot/modules. However,
1031 manually building and installing a module from /sys/modules will
1032 now install to /boot/modules instead of /boot/kernel.
1035 The CAM I/O scheduler has been committed to the kernel. There should be
1036 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1037 list of known rogues that claim support for this but actually corrupt
1038 data is believed to be complete, be on the lookout for data
1039 corruption. The known rogue list is believed to be complete:
1041 o Crucial MX100, M550 drives with MU01 firmware.
1042 o Micron M510 and M550 drives with MU01 firmware.
1043 o Micron M500 prior to MU07 firmware
1044 o Samsung 830, 840, and 850 all firmwares
1045 o FCCT M500 all firmwares
1047 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1048 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1049 updated firmware. Black listed drives will work correctly because these
1050 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1051 this list is the same as found in Linux, it's believed there are no
1052 other rogues in the market place. All other models from the above
1055 To be safe, if you are at all concerned, you can quirk each of your
1056 drives to prevent NCQ from being sent by setting:
1057 kern.cam.ada.X.quirks="0x2"
1058 in loader.conf. If the drive requires the 4k sector quirk, set the
1059 quirks entry to 0x3.
1062 The FAST_DEPEND build option has been removed and its functionality is
1063 now the one true way. The old mkdep(1) style of 'make depend' has
1064 been removed. See 20160311 for further details.
1067 Resource range types have grown from unsigned long to uintmax_t. All
1068 drivers, and anything using libdevinfo, need to be recompiled.
1071 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1072 builds. It no longer runs mkdep(1) during 'make depend', and the
1073 'make depend' stage can safely be skipped now as it is auto ran
1074 when building 'make all' and will generate all SRCS and DPSRCS before
1075 building anything else. Dependencies are gathered at compile time with
1076 -MF flags kept in separate .depend files per object file. Users should
1077 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1078 stale .depend files.
1081 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1082 kernel modules. Therefore, if you load any kernel modules at boot time,
1083 please install the boot loaders after you install the kernel, but before
1087 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1088 make installkernel KERNCONF=YOUR_KERNEL_HERE
1089 make -C sys/boot install
1090 <reboot in single user>
1092 Then follow the usual steps, described in the General Notes section,
1096 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1097 see the 20141231 entry below for information about prerequisites and
1098 upgrading, if you are not already using clang 3.5.0 or higher.
1101 The AIO subsystem is now a standard part of the kernel. The
1102 VFS_AIO kernel option and aio.ko kernel module have been removed.
1103 Due to stability concerns, asynchronous I/O requests are only
1104 permitted on sockets and raw disks by default. To enable
1105 asynchronous I/O requests on all file types, set the
1106 vfs.aio.enable_unsafe sysctl to a non-zero value.
1109 The ELF object manipulation tool objcopy is now provided by the
1110 ELF Tool Chain project rather than by GNU binutils. It should be a
1111 drop-in replacement, with the addition of arm64 support. The
1112 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1113 to obtain the GNU version if necessary.
1116 Building ZFS pools on top of zvols is prohibited by default. That
1117 feature has never worked safely; it's always been prone to deadlocks.
1118 Using a zvol as the backing store for a VM guest's virtual disk will
1119 still work, even if the guest is using ZFS. Legacy behavior can be
1120 restored by setting vfs.zfs.vol.recursive=1.
1123 The NONE and HPN patches has been removed from OpenSSH. They are
1124 still available in the security/openssh-portable port.
1127 With the addition of ypldap(8), a new _ypldap user is now required
1128 during installworld. "mergemaster -p" can be used to add the user
1129 prior to installworld, as documented in the handbook.
1132 The tftp loader (pxeboot) now uses the option root-path directive. As a
1133 consequence it no longer looks for a pxeboot.4th file on the tftp
1134 server. Instead it uses the regular /boot infrastructure as with the
1138 The code to start recording plug and play data into the modules has
1139 been committed. While the old tools will properly build a new kernel,
1140 a number of warnings about "unknown metadata record 4" will be produced
1141 for an older kldxref. To avoid such warnings, make sure to rebuild
1142 the kernel toolchain (or world). Make sure that you have r292078 or
1143 later when trying to build 292077 or later before rebuilding.
1146 Debug data files are now built by default with 'make buildworld' and
1147 installed with 'make installworld'. This facilitates debugging but
1148 requires more disk space both during the build and for the installed
1149 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1153 r291527 changed the internal interface between the nfsd.ko and
1154 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1155 __FreeBSD_version has been bumped because of this.
1158 Add support for unicode collation strings leads to a change of
1159 order of files listed by ls(1) for example. To get back to the old
1160 behaviour, set LC_COLLATE environment variable to "C".
1162 Databases administrators will need to reindex their databases given
1163 collation results will be different.
1165 Due to a bug in install(1) it is recommended to remove the ancient
1166 locales before running make installworld.
1168 rm -rf /usr/share/locale/*
1171 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1172 libcrypto.so.7 or libssl.so.7 must be recompiled.
1175 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1176 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1177 should be replaced with isp_2400 and isp_2500 modules respectively.
1180 The build previously allowed using 'make -n' to not recurse into
1181 sub-directories while showing what commands would be executed, and
1182 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1183 and 'make -N' will not.
1186 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1187 and etcupdate will now use this file. A custom sendmail.cf is now
1188 updated via this mechanism rather than via installworld. If you had
1189 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1190 want to remove the exclusion or change it to "always install".
1191 /etc/mail/sendmail.cf is now managed the same way regardless of
1192 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1193 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1196 Compatibility shims for legacy ATA device names have been removed.
1197 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1198 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1199 environment variables, /dev/ad* and /dev/ar* symbolic links.
1202 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1203 Please see the 20141231 entry below for information about prerequisites
1204 and upgrading, if you are not already using clang 3.5.0 or higher.
1207 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1208 and renamed from .symbols to .debug. This reduces the size requirements
1209 on the boot partition or file system and provides consistency with
1210 userland debug files.
1212 When using the supported kernel installation method the
1213 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1214 as is done with /boot/kernel.
1216 Developers wishing to maintain the historical behavior of installing
1217 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1220 The wireless drivers had undergone changes that remove the 'parent
1221 interface' from the ifconfig -l output. The rc.d network scripts
1222 used to check presence of a parent interface in the list, so old
1223 scripts would fail to start wireless networking. Thus, etcupdate(3)
1224 or mergemaster(8) run is required after kernel update, to update your
1225 rc.d scripts in /etc.
1228 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1229 These configurations are now automatically interpreted as
1230 'scrub fragment reassemble'.
1233 Kernel-loadable modules for the random(4) device are back. To use
1234 them, the kernel must have
1237 options RANDOM_LOADABLE
1239 kldload(8) can then be used to load random_fortuna.ko
1240 or random_yarrow.ko. Please note that due to the indirect
1241 function calls that the loadable modules need to provide,
1242 the build-in variants will be slightly more efficient.
1244 The random(4) kernel option RANDOM_DUMMY has been retired due to
1245 unpopularity. It was not all that useful anyway.
1248 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1249 Control over building the ELF Tool Chain tools is now provided by
1250 the WITHOUT_TOOLCHAIN knob.
1253 The polarity of Pulse Per Second (PPS) capture events with the
1254 uart(4) driver has been corrected. Prior to this change the PPS
1255 "assert" event corresponded to the trailing edge of a positive PPS
1256 pulse and the "clear" event was the leading edge of the next pulse.
1258 As the width of a PPS pulse in a typical GPS receiver is on the
1259 order of 1 millisecond, most users will not notice any significant
1260 difference with this change.
1262 Anyone who has compensated for the historical polarity reversal by
1263 configuring a negative offset equal to the pulse width will need to
1264 remove that workaround.
1267 The default group assigned to /dev/dri entries has been changed
1268 from 'wheel' to 'video' with the id of '44'. If you want to have
1269 access to the dri devices please add yourself to the video group
1272 # pw groupmod video -m $USER
1275 The menu.rc and loader.rc files will now be replaced during
1276 upgrades. Please migrate local changes to menu.rc.local and
1277 loader.rc.local instead.
1280 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1281 strings and strip have been removed. The src.conf(5) knob
1282 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1285 As ZFS requires more kernel stack pages than is the default on some
1286 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1287 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1289 Please consider using 'options KSTACK_PAGES=X' where X is greater
1290 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1293 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1294 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1295 default, i.e., they will not contain "::". For example, instead
1296 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1297 to have a more specific match, such as different map entries for
1298 IPv6:0:0 vs IPv6:0. This change requires that configuration
1299 data (including maps, files, classes, custom ruleset, etc.) must
1300 use the same format, so make certain such configuration data is
1301 upgrading. As a very simple check search for patterns like
1302 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1303 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1304 the cf option UseCompressedIPv6Addresses.
1307 The default kernel entropy-processing algorithm is now
1308 Fortuna, replacing Yarrow.
1310 Assuming you have 'device random' in your kernel config
1311 file, the configurations allow a kernel option to override
1312 this default. You may choose *ONE* of:
1314 options RANDOM_YARROW # Legacy /dev/random algorithm.
1315 options RANDOM_DUMMY # Blocking-only driver.
1317 If you have neither, you get Fortuna. For most people,
1318 read no further, Fortuna will give a /dev/random that works
1319 like it always used to, and the difference will be irrelevant.
1321 If you remove 'device random', you get *NO* kernel-processed
1322 entropy at all. This may be acceptable to folks building
1323 embedded systems, but has complications. Carry on reading,
1324 and it is assumed you know what you need.
1326 *PLEASE* read random(4) and random(9) if you are in the
1327 habit of tweaking kernel configs, and/or if you are a member
1328 of the embedded community, wanting specific and not-usual
1329 behaviour from your security subsystems.
1331 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1332 random', you will NOT have a functioning /dev/random, and
1333 many cryptographic features will not work, including SSH.
1334 You may also find strange behaviour from the random(3) set
1335 of library functions, in particular sranddev(3), srandomdev(3)
1336 and arc4random(3). The reason for this is that the KERN_ARND
1337 sysctl only returns entropy if it thinks it has some to
1338 share, and with RANDOM_DUMMY or no 'device random' this
1342 An additional fix for the issue described in the 20150614 sendmail
1343 entry below has been committed in revision 284717.
1346 FreeBSD's old make (fmake) has been removed from the system. It is
1347 available as the devel/fmake port or via pkg install fmake.
1350 The fix for the issue described in the 20150614 sendmail entry
1351 below has been committed in revision 284436. The work
1352 around described in that entry is no longer needed unless the
1353 default setting is overridden by a confDH_PARAMETERS configuration
1354 setting of '5' or pointing to a 512 bit DH parameter file.
1357 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1358 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1359 and devel/kyua to version 0.20+ and adjust any calling code to work
1360 with Kyuafile and kyua.
1363 The import of openssl to address the FreeBSD-SA-15:10.openssl
1364 security advisory includes a change which rejects handshakes
1365 with DH parameters below 768 bits. sendmail releases prior
1366 to 8.15.2 (not yet released), defaulted to a 512 bit
1367 DH parameter setting for client connections. To work around
1368 this interoperability, sendmail can be configured to use a
1369 2048 bit DH parameter by:
1371 1. Edit /etc/mail/`hostname`.mc
1372 2. If a setting for confDH_PARAMETERS does not exist or
1373 exists and is set to a string beginning with '5',
1374 replace it with '2'.
1375 3. If a setting for confDH_PARAMETERS exists and is set to
1376 a file path, create a new file with:
1377 openssl dhparam -out /path/to/file 2048
1378 4. Rebuild the .cf file:
1379 cd /etc/mail/; make; make install
1380 5. Restart sendmail:
1381 cd /etc/mail/; make restart
1383 A sendmail patch is coming, at which time this file will be
1387 Generation of legacy formatted entries have been disabled by default
1388 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1389 entries were converted to use the new format by default when the new,
1390 machine independent format have been added and supported since FreeBSD
1393 Please see the pwd_mkdb(8) manual page for further details.
1396 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1397 20141231 entry below for information about prerequisites and upgrading,
1398 if you are not already using 3.5.0 or higher.
1401 TI platform code switched to using vendor DTS files and this update
1402 may break existing systems running on Beaglebone, Beaglebone Black,
1405 - dtb files should be regenerated/reinstalled. Filenames are the
1406 same but content is different now
1407 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1408 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1409 addressing scheme is now pin 25 on /dev/gpioc3.
1410 - Pandaboard: /etc/ttys should be updated, serial console device is
1411 now /dev/ttyu2, not /dev/ttyu0
1414 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1415 If you need the GNU extension from groff soelim(1), install groff
1416 from package: pkg install groff, or via ports: textproc/groff.
1419 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1420 defined in symlink(7); previously symlinks were silently ignored.
1423 The const qualifier has been removed from iconv(3) to comply with
1424 POSIX. The ports tree is aware of this from r384038 onwards.
1427 Libraries specified by LIBADD in Makefiles must have a corresponding
1428 DPADD_<lib> variable to ensure correct dependencies. This is now
1429 enforced in src.libnames.mk.
1432 From legacy ata(4) driver was removed support for SATA controllers
1433 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1434 Kernel modules ataahci and ataadaptec were removed completely,
1435 replaced by ahci and mvs modules respectively.
1438 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1439 the 20141231 entry below for information about prerequisites and
1440 upgrading, if you are not already using 3.5.0 or higher.
1443 The 32-bit PowerPC kernel has been changed to a position-independent
1444 executable. This can only be booted with a version of loader(8)
1445 newer than January 31, 2015, so make sure to update both world and
1446 kernel before rebooting.
1449 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1450 but before r278950, the RNG was not seeded properly. Immediately
1451 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1452 ssh keys or openssl keys) that were generated w/ a kernel from that
1453 range. This does not affect programs that directly used /dev/random
1454 or /dev/urandom. All userland uses of arc4random(3) are affected.
1457 The autofs(4) ABI was changed in order to restore binary compatibility
1458 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1459 with the new kernel.
1462 The powerpc64 kernel has been changed to a position-independent
1463 executable. This can only be booted with a new version of loader(8),
1464 so make sure to update both world and kernel before rebooting.
1467 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1468 only release, no new features have been added. Please see the 20141231
1469 entry below for information about prerequisites and upgrading, if you
1470 are not already using 3.5.0.
1473 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1474 taken from the ELF Tool Chain project rather than GNU binutils. They
1475 should be drop-in replacements, with the addition of arm64 support.
1476 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1477 binutils tools, if necessary. See 20150805 for updated information.
1480 The default Unbound configuration now enables remote control
1481 using a local socket. Users who have already enabled the
1482 local_unbound service should regenerate their configuration
1483 by running "service local_unbound setup" as root.
1486 The GNU texinfo and GNU info pages have been removed.
1487 To be able to view GNU info pages please install texinfo from ports.
1490 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1492 As of this release, a prerequisite for building clang, llvm and lldb is
1493 a C++11 capable compiler and C++11 standard library. This means that to
1494 be able to successfully build the cross-tools stage of buildworld, with
1495 clang as the bootstrap compiler, your system compiler or cross compiler
1496 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1497 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1500 On any standard FreeBSD 10.x or 11.x installation, where clang and
1501 libc++ are on by default (that is, on x86 or arm), this should work out
1504 On 9.x installations where clang is enabled by default, e.g. on x86 and
1505 powerpc, libc++ will not be enabled by default, so libc++ should be
1506 built (with clang) and installed first. If both clang and libc++ are
1507 missing, build clang first, then use it to build libc++.
1509 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1510 the instructions for 9.x above.
1512 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1513 default, and do not build clang.
1515 Many embedded systems are resource constrained, and will not be able to
1516 build clang in a reasonable time, or in some cases at all. In those
1517 cases, cross building bootable systems on amd64 is a workaround.
1519 This new version of clang introduces a number of new warnings, of which
1520 the following are most likely to appear:
1524 This warns in two cases, for both C and C++:
1525 * When the code is trying to take the absolute value of an unsigned
1526 quantity, which is effectively a no-op, and almost never what was
1527 intended. The code should be fixed, if at all possible. If you are
1528 sure that the unsigned quantity can be safely cast to signed, without
1529 loss of information or undefined behavior, you can add an explicit
1530 cast, or disable the warning.
1532 * When the code is trying to take an absolute value, but the called
1533 abs() variant is for the wrong type, which can lead to truncation.
1534 If you want to disable the warning instead of fixing the code, please
1535 make sure that truncation will not occur, or it might lead to unwanted
1538 -Wtautological-undefined-compare and
1539 -Wundefined-bool-conversion
1541 These warn when C++ code is trying to compare 'this' against NULL, while
1542 'this' should never be NULL in well-defined C++ code. However, there is
1543 some legacy (pre C++11) code out there, which actively abuses this
1544 feature, which was less strictly defined in previous C++ versions.
1546 Squid and openjdk do this, for example. The warning can be turned off
1547 for C++98 and earlier, but compiling the code in C++11 mode might result
1548 in unexpected behavior; for example, the parts of the program that are
1549 unreachable could be optimized away.
1552 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1553 kernel sources have been removed. The .h files remain, since some
1554 utilities include them. This will need to be fixed later.
1555 If "mount -t oldnfs ..." is attempted, it will fail.
1556 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1557 the utilities will report errors.
1560 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1561 directories to top level SUBDIR variable when their parent
1562 directory is included in LOCAL_DIRS. Users with build systems with
1563 such hierarchies and without SUBDIR entries in the parent
1564 directory Makefiles should add them or add the directories to
1568 faith(4) and faithd(8) have been removed from the base system. Faith
1569 has been obsolete for a very long time.
1572 vt(4), the new console driver, is enabled by default. It brings
1573 support for Unicode and double-width characters, as well as
1574 support for UEFI and integration with the KMS kernel video
1577 You may need to update your console settings in /etc/rc.conf,
1578 most probably the keymap. During boot, /etc/rc.d/syscons will
1579 indicate what you need to do.
1581 vt(4) still has issues and lacks some features compared to
1582 syscons(4). See the wiki for up-to-date information:
1583 https://wiki.freebsd.org/Newcons
1585 If you want to keep using syscons(4), you can do so by adding
1586 the following line to /boot/loader.conf:
1590 pjdfstest has been integrated into kyua as an opt-in test suite.
1591 Please see share/doc/pjdfstest/README for more details on how to
1595 gperf has been removed from the base system for architectures
1596 that use clang. Ports that require gperf will obtain it from the
1600 pjdfstest has been moved from tools/regression/pjdfstest to
1604 At svn r271982, The default linux compat kernel ABI has been adjusted
1605 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1606 update. If you wish to continue using the linux-f10 compat ports,
1607 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1608 encouraged to update their linux-compat packages to linux-c6 during
1609 their next update cycle.
1612 The ofwfb driver, used to provide a graphics console on PowerPC when
1613 using vt(4), no longer allows mmap() of all physical memory. This
1614 will prevent Xorg on PowerPC with some ATI graphics cards from
1615 initializing properly unless x11-servers/xorg-server is updated to
1619 The xdev targets have been converted to using TARGET and
1620 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1623 The default unbound configuration has been modified to address
1624 issues with reverse lookups on networks that use private
1625 address ranges. If you use the local_unbound service, run
1626 "service local_unbound setup" as root to regenerate your
1627 configuration, then "service local_unbound reload" to load the
1631 The GNU texinfo and GNU info pages are not built and installed
1632 anymore, WITH_INFO knob has been added to allow to built and install
1634 UPDATE: see 20150102 entry on texinfo's removal
1637 The GNU readline library is now an INTERNALLIB - that is, it is
1638 statically linked into consumers (GDB and variants) in the base
1639 system, and the shared library is no longer installed. The
1640 devel/readline port is available for third party software that
1644 The Itanium architecture (ia64) has been removed from the list of
1645 known architectures. This is the first step in the removal of the
1649 Commit r268115 has added NFSv4.1 server support, merged from
1650 projects/nfsv4.1-server. Since this includes changes to the
1651 internal interfaces between the NFS related modules, a full
1652 build of the kernel and modules will be necessary.
1653 __FreeBSD_version has been bumped.
1656 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1657 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1658 which differs from the behaviour controlled by this knob.)
1661 Maximal length of the serial number in CTL was increased from 16 to
1662 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1663 and ctld, need to be rebuilt to work with a new kernel.
1666 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1667 1 respectively to match the upstream numbers. They were out of
1668 sync because, when they were originally added to FreeBSD, the
1669 upstream versions were not respected. These libraries are private
1670 and not yet built by default, so renumbering them should be a
1671 non-issue. However, unclean source trees will yield broken test
1672 programs once the operator executes "make delete-old-libs" after a
1673 "make installworld".
1675 Additionally, the atf-sh binary was made private by moving it into
1676 /usr/libexec/. Already-built shell test programs will keep the
1677 path to the old binary so they will break after "make delete-old"
1680 If you are using WITH_TESTS=yes (not the default), wipe the object
1681 tree and rebuild from scratch to prevent spurious test failures.
1682 This is only needed once: the misnumbered libraries and misplaced
1683 binaries have been added to OptionalObsoleteFiles.inc so they will
1684 be removed during a clean upgrade.
1687 Clang and llvm have been upgraded to 3.4.1 release.
1690 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1691 be removed to avoid issues in the future (and has been added to
1695 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1696 past, it affected all builds that used the bsd.*.mk files. The old
1697 behavior was a bug, but people may have relied upon it. To get this
1698 behavior back, you can .include /etc/src.conf from /etc/make.conf
1699 (which is still global and isn't changed). This also changes the
1700 behavior of incremental builds inside the tree of individual
1701 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1702 Although this has survived make universe and some upgrade scenarios,
1703 other upgrade scenarios may have broken. At least one form of
1704 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1705 as well... In cases where MAKESYSPATH isn't working with this
1706 setting, you'll need to set it to the full path to your tree.
1708 One side effect of all this cleaning up is that bsd.compiler.mk
1709 is no longer implicitly included by bsd.own.mk. If you wish to
1710 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1714 The lindev device has been removed since /dev/full has been made a
1715 standard device. __FreeBSD_version has been bumped.
1718 The knob WITHOUT_VI was added to the base system, which controls
1719 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1720 in order to reorder files share/termcap and didn't build ex(1) as a
1721 build tool, so building/installing with WITH_VI is highly advised for
1722 build hosts for older releases.
1724 This issue has been fixed in stable/9 and stable/10 in r277022 and
1725 r276991, respectively.
1728 The YES_HESIOD knob has been removed. It has been obsolete for
1729 a decade. Please move to using WITH_HESIOD instead or your builds
1730 will silently lack HESIOD.
1733 The uart(4) driver has been changed with respect to its handling
1734 of the low-level console. Previously the uart(4) driver prevented
1735 any process from changing the baudrate or the CLOCAL and HUPCL
1736 control flags. By removing the restrictions, operators can make
1737 changes to the serial console port without having to reboot.
1738 However, when getty(8) is started on the serial device that is
1739 associated with the low-level console, a misconfigured terminal
1740 line in /etc/ttys will now have a real impact.
1741 Before upgrading the kernel, make sure that /etc/ttys has the
1742 serial console device configured as 3wire without baudrate to
1743 preserve the previous behaviour. E.g:
1744 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1747 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1748 to improve performance. To re-enable it, if needed, run rpcbind
1749 with command line option -W.
1752 Switched back to the GPL dtc compiler due to updates in the upstream
1753 dts files not being supported by the BSDL dtc compiler. You will need
1754 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1755 may result while building dtb files during a kernel build if you fail
1756 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1759 Clang and llvm have been upgraded to 3.4 release.
1762 The nve(4) driver has been removed. Please use the nfe(4) driver
1763 for NVIDIA nForce MCP Ethernet adapters instead.
1766 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1767 This could cause certain C++ applications using shared libraries built
1768 against the previous version of libc++ to crash. The incompatibility
1769 has now been fixed, but any C++ applications or shared libraries built
1770 between r261283 and r261801 should be recompiled.
1773 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1774 capability mode support. Please note that enabling the feature in
1775 kernel is still highly recommended.
1778 OpenSSH is now built with sandbox support, and will use sandbox as
1779 the default privilege separation method. This requires Capsicum
1780 capability mode support in kernel.
1783 The libelf and libdwarf libraries have been updated to newer
1784 versions from upstream. Shared library version numbers for
1785 these two libraries were bumped. Any ports or binaries
1786 requiring these two libraries should be recompiled.
1787 __FreeBSD_version is bumped to 1100006.
1790 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1791 instead of providing an explicit one, this would prevent such
1792 Makefile from providing its own Kyuafile in the future during
1793 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1794 intervention is needed to clean an objdir if you use NO_CLEAN:
1795 # find /usr/obj -name Kyuafile | xargs rm -f
1798 The behavior of gss_pseudo_random() for the krb5 mechanism
1799 has changed, for applications requesting a longer random string
1800 than produced by the underlying enctype's pseudo-random() function.
1801 In particular, the random string produced from a session key of
1802 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1803 be different at the 17th octet and later, after this change.
1804 The counter used in the PRF+ construction is now encoded as a
1805 big-endian integer in accordance with RFC 4402.
1806 __FreeBSD_version is bumped to 1100004.
1809 The WITHOUT_ATF build knob has been removed and its functionality
1810 has been subsumed into the more generic WITHOUT_TESTS. If you were
1811 using the former to disable the build of the ATF libraries, you
1812 should change your settings to use the latter.
1815 The default version of mtree is nmtree which is obtained from
1816 NetBSD. The output is generally the same, but may vary
1817 slightly. If you found you need identical output adding
1818 "-F freebsd9" to the command line should do the trick. For the
1819 time being, the old mtree is available as fmtree.
1822 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1823 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1824 1.1.4_8 and verify bsdyml not linked in, before running "make
1826 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1828 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1831 The stable/10 branch has been created in subversion from head
1838 Avoid using make -j when upgrading. While generally safe, there are
1839 sometimes problems using -j to upgrade. If your upgrade fails with
1840 -j, please try again without -j. From time to time in the past there
1841 have been problems using -j with buildworld and/or installworld. This
1842 is especially true when upgrading between "distant" versions (eg one
1843 that cross a major release boundary or several minor releases, or when
1844 several months have passed on the -current branch).
1846 Sometimes, obscure build problems are the result of environment
1847 poisoning. This can happen because the make utility reads its
1848 environment when searching for values for global variables. To run
1849 your build attempts in an "environmental clean room", prefix all make
1850 commands with 'env -i '. See the env(1) manual page for more details.
1852 When upgrading from one major version to another it is generally best to
1853 upgrade to the latest code in the currently installed branch first, then
1854 do an upgrade to the new branch. This is the best-tested upgrade path,
1855 and has the highest probability of being successful. Please try this
1856 approach if you encounter problems with a major version upgrade. Since
1857 the stable 4.x branch point, one has generally been able to upgrade from
1858 anywhere in the most recent stable branch to head / current (or even the
1859 last couple of stable branches). See the top of this file when there's
1862 When upgrading a live system, having a root shell around before
1863 installing anything can help undo problems. Not having a root shell
1864 around can lead to problems if pam has changed too much from your
1865 starting point to allow continued authentication after the upgrade.
1867 This file should be read as a log of events. When a later event changes
1868 information of a prior event, the prior event should not be deleted.
1869 Instead, a pointer to the entry with the new information should be
1870 placed in the old entry. Readers of this file should also sanity check
1871 older entries before relying on them blindly. Authors of new entries
1872 should write them with this in mind.
1876 When upgrading the boot ZFS pool to a new version, always follow
1879 1.) recompile and reinstall the ZFS boot loader and boot block
1880 (this is part of "make buildworld" and "make installworld")
1882 2.) update the ZFS boot block on your boot drive
1884 The following example updates the ZFS boot block on the first
1885 partition (freebsd-boot) of a GPT partitioned drive ada0:
1886 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1888 Non-boot pools do not need these updates.
1892 If you are updating from a prior version of FreeBSD (even one just
1893 a few days old), you should follow this procedure. It is the most
1894 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1896 make kernel-toolchain
1897 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1898 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1900 To test a kernel once
1901 ---------------------
1902 If you just want to boot a kernel once (because you are not sure
1903 if it works, or if you want to boot a known bad kernel to provide
1904 debugging information) run
1905 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1906 nextboot -k testkernel
1908 To rebuild everything and install it on the current system.
1909 -----------------------------------------------------------
1910 # Note: sometimes if you are running current you gotta do more than
1911 # is listed here if you are upgrading from a really old current.
1913 <make sure you have good level 0 dumps>
1915 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1916 make installkernel KERNCONF=YOUR_KERNEL_HERE
1918 <reboot in single user> [3]
1925 To cross-install current onto a separate partition
1926 --------------------------------------------------
1927 # In this approach we use a separate partition to hold
1928 # current's root, 'usr', and 'var' directories. A partition
1929 # holding "/", "/usr" and "/var" should be about 2GB in
1932 <make sure you have good level 0 dumps>
1935 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1936 <maybe newfs current's root partition>
1937 <mount current's root partition on directory ${CURRENT_ROOT}>
1938 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1939 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1940 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1941 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1942 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1943 <reboot into current>
1944 <do a "native" rebuild/install as described in the previous section>
1945 <maybe install compatibility libraries from ports/misc/compat*>
1949 To upgrade in-place from stable to current
1950 ----------------------------------------------
1951 <make sure you have good level 0 dumps>
1953 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1954 make installkernel KERNCONF=YOUR_KERNEL_HERE
1956 <reboot in single user> [3]
1963 Make sure that you've read the UPDATING file to understand the
1964 tweaks to various things you need. At this point in the life
1965 cycle of current, things change often and you are on your own
1966 to cope. The defaults can also change, so please read ALL of
1967 the UPDATING entries.
1969 Also, if you are tracking -current, you must be subscribed to
1970 freebsd-current@freebsd.org. Make sure that before you update
1971 your sources that you have read and understood all the recent
1972 messages there. If in doubt, please track -stable which has
1973 much fewer pitfalls.
1975 [1] If you have third party modules, such as vmware, you
1976 should disable them at this point so they don't crash your
1979 [3] From the bootblocks, boot -s, and then do
1983 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
1984 cd src # full path to source
1985 adjkerntz -i # if CMOS is wall time
1986 Also, when doing a major release upgrade, it is required that
1987 you boot into single user mode to do the installworld.
1989 [4] Note: This step is non-optional. Failure to do this step
1990 can result in a significant reduction in the functionality of the
1991 system. Attempting to do it by hand is not recommended and those
1992 that pursue this avenue should read this file carefully, as well
1993 as the archives of freebsd-current and freebsd-hackers mailing lists
1994 for potential gotchas. The -U option is also useful to consider.
1995 See mergemaster(8) for more information.
1997 [5] Usually this step is a no-op. However, from time to time
1998 you may need to do this if you get unknown user in the following
1999 step. It never hurts to do it all the time. You may need to
2000 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2001 install) after the buildworld before this step if you last updated
2002 from current before 20130425 or from -stable before 20130430.
2004 [6] This only deletes old files and directories. Old libraries
2005 can be deleted by "make delete-old-libs", but you have to make
2006 sure that no program is using those libraries anymore.
2008 [8] The new kernel must be able to run existing binaries used by an
2009 installworld. When upgrading across major versions, the new kernel's
2010 configuration must include the correct COMPAT_FREEBSD<n> option for
2011 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2012 to do so may leave you with a system that is hard to boot to recover. A
2013 GENERIC kernel will include suitable compatibility options to run
2014 binaries from older branches. Note that the ability to run binaries
2015 from unsupported branches is not guaranteed.
2017 Make sure that you merge any new devices from GENERIC since the
2018 last time you updated your kernel config file. Options also
2019 change over time, so you may need to adjust your custom kernels
2022 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2023 "?=" instead of the "=" assignment operator, so that buildworld can
2024 override the CPUTYPE if it needs to.
2026 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2027 not on the command line, or in /etc/make.conf. buildworld will
2028 warn if it is improperly defined.
2031 This file contains a list, in reverse chronological order, of major
2032 breakages in tracking -current. It is not guaranteed to be a complete
2033 list of such breakages, and only contains entries since September 23, 2011.
2034 If you need to see UPDATING entries from before that date, you will need
2035 to fetch an UPDATING file from an older FreeBSD release.
2037 Copyright information:
2039 Copyright 1998-2009 M. Warner Losh.
2041 Redistribution, publication, translation and use, with or without
2042 modification, in full or in part, in any form or format of this
2043 document are permitted without further permission from the author.
2045 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2046 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2047 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2048 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2049 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2050 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2051 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2052 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2053 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2054 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2055 POSSIBILITY OF SUCH DAMAGE.
2057 Contact Warner Losh if you have any questions about your use of