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 The loadable random module KPI has changed; the random_infra_init()
36 routine now requires a 3rd function pointer for a bool (*)(void)
37 method that returns true if the random device is seeded (and
41 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
42 built from head sources between r320757 (July 6, 2017) and
43 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
44 is added to the command line.
45 nfsuserd daemons built from head sources that are post-r338192 are
46 not affected and should continue to work.
49 The fuse(4) module has been renamed to fusefs(4) for consistency with
50 other filesystems. You should update any kld_load="fuse" entries in
51 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
52 "options FUSE" enties in kernel config files.
55 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
56 8.0.0. Please see the 20141231 entry below for information about
57 prerequisites and upgrading, if you are not already using clang 3.5.0
61 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
62 compiled into your custom kernel, add 'device xz' statement to the
66 drm and drm2 have been removed from the tree. Please see
67 https://wiki.freebsd.org/Graphics for the latest information on
68 migrating to the drm ports.
71 Iflib is no longer unconditionally compiled into the kernel. Drivers
72 using iflib and statically compiled into the kernel, now require
73 the 'device iflib' config option. For the same drivers loaded as
74 modules on kernels not having 'device iflib', the iflib.ko module
75 is loaded automatically.
78 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
79 options no longer exist since r343219 and r343427 respectively;
80 nothing uses them, so they should be just removed from custom
84 r342635 changes the way efibootmgr(8) works by requiring users to add
85 the -b (bootnum) parameter for commands where the bootnum was previously
86 specified with each option. For example 'efibootmgr -B 0001' is now
87 'efibootmgr -B -b 0001'.
90 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
91 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
92 servers that have vfs.nfsd.nfs_privport set will only allow mounts
93 from clients using a reserved port#. Since both the FreeBSD and Linux
94 NFSv4 clients use reserved port#s by default, this should not affect
98 The XLP config has been removed. We can't support 64-bit atomics in this
99 kernel because it is running in 32-bit mode. XLP users must transition
100 to running a 64-bit kernel (XLP64 or XLPN32).
102 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
103 the preferred emulator today and we don't need two different ones.
105 The old sibyte / swarm / Broadcom BCM1250 support has been
106 removed from the mips port.
109 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
110 7.0.1. Please see the 20141231 entry below for information about
111 prerequisites and upgrading, if you are not already using clang 3.5.0
115 Remove the timed and netdate programs from the base tree. Setting
116 the time with these deamons has been obsolete for over a decade.
119 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
120 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
121 it produces broken binaries when ifuncs are in use. Users needing
122 GNU ld should install the binutils port or package.
125 The BSD crtbegin and crtend code has been enabled by default. It has
126 had extensive testing on amd64, arm64, and i386. It can be disabled
127 by building a world with -DWITHOUT_BSD_CRTBEGIN.
130 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
131 has been converted to a port (misc/ctm) and will be removed from
132 FreeBSD-13. It is available as a package (ctm) for all supported
136 The default newsyslog.conf(5) file has been changed to only include
137 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
138 the filenames end in '.conf' and do not begin with a '.'.
140 You should check the configuration files in these two directories match
141 this naming convention. You can verify which configuration files are
142 being included using the command:
146 Ports for the DRM modules have been simplified. Now, amd64 users should
147 just install the drm-kmod port. All others should install
150 Graphics hardware that's newer than about 2010 usually works with
151 drm-kmod. For hardware older than 2013, however, some users will need
152 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
153 than 2008 usually only works in drm-legacy-kmod. The graphics team can
154 only commit to hardware made since 2013 due to the complexity of the
155 market and difficulty to test all the older cards effectively. If you
156 have hardware supported by drm-kmod, you are strongly encouraged to use
157 that as you will get better support.
159 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
160 elsewhere, the drm and drm2 modules will be eliminated from the src base
161 soon (with a limited exception for arm). Please update to the package
162 asap and report any issues to x11@freebsd.org.
164 Generally, anybody using the drm*-kmod packages should add
165 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
166 cross-threading surprises, especially with automatic driver
167 loading from X11 startup. These will become the defaults in 13-current
171 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
172 custom kernel and module loading configuration files must be updated
173 accordingly. Moreover, interfaces previous presented as ixlvN to the
174 system are now exposed as iavfN and network configuration files must
175 be adjusted as necessary.
178 OpenSSL has been updated to version 1.1.1. This update included
179 additional various API changes througout the base system. It is
180 important to rebuild third-party software after upgrading. The value
181 of __FreeBSD_version has been bumped accordingly.
184 The legacy DRM modules and drivers have now been added to the loader's
185 module blacklist, in favor of loading them with kld_list in rc.conf(5).
186 The module blacklist may be overridden with the loader.conf(5)
187 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
191 The cam(4) based nda(4) driver will be used over nvd(4) by default on
192 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
193 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
194 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
198 Reproducible build mode is now on by default, in preparation for
199 FreeBSD 12.0. This eliminates build metadata such as the user,
200 host, and time from the kernel (and uname), unless the working tree
201 corresponds to a modified checkout from a version control system.
202 The previous behavior can be obtained by setting the /etc/src.conf
203 knob WITHOUT_REPRODUCIBLE_BUILD.
206 The Yarrow CSPRNG has been removed from the kernel as it has not been
207 supported by its designers since at least 2003. Fortuna has been the
208 default since FreeBSD-11.
211 devctl freeze/thaw have gone into the tree, the rc scripts have been
212 updated to use them and devmatch has been changed. You should update
213 kernel, userland and rc scripts all at the same time.
216 The default interpreter has been switched from 4th to Lua.
217 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
218 interpreter. If you have custom FORTH code you will need to set
219 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
220 src.conf for the build. This will create default hard links between
221 loader and loader_4th instead of loader and loader_lua, the new default.
222 If you are using UEFI it will create the proper hard link to loader.efi.
224 bhyve uses userboot.so. It remains 4th-only until some issues are solved
225 regarding coexisting with multiple versions of FreeBSD are resolved.
228 ls(1) now respects the COLORTERM environment variable used in other
229 systems and software to indicate that a colored terminal is both
230 supported and desired. If ls(1) is suddenly emitting colors, they may
231 be disabled again by either removing the unwanted COLORTERM from your
232 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
233 may not be observed in a future release.
236 The default pager for most commands has been changed to "less". To
237 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
241 The jedec_ts(4) driver has been removed. A superset of its functionality
242 is available in the jedec_dimm(4) driver, and the manpage for that
243 driver includes migration instructions. If you have "device jedec_ts"
244 in your kernel configuration file, it must be removed.
247 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
248 This should have no effect if the kernel is booted via BIOS/legacy boot.
249 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
250 has a buggy firmware that prevents a successful boot due to use of
254 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
255 support has been removed from the tree. These ports were
256 obsolete and/or known to be broken for many years.
259 loader.efi has been augmented to participate more fully in the
260 UEFI boot manager protocol. loader.efi will now look at the
261 BootXXXX environment variable to determine if a specific kernel
262 or root partition was specified. XXXX is derived from BootCurrent.
263 efibootmgr(8) manages these standard UEFI variables.
266 zfsloader's functionality has now been folded into loader.
267 zfsloader is no longer necessary once you've updated your
268 boot blocks. For a transition period, we will install a
269 hardlink for zfsloader to loader to allow a smooth transition
270 until the boot blocks can be updated (hard link because old
271 zfs boot blocks don't understand symlinks).
274 ARM64 now have efifb support, if you want to have serial console
275 on your arm64 board when an screen is connected and the bootloader
276 setup a framebuffer for us to use, just add :
280 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
281 an screen connected as the firmware will setup a framebuffer are that
282 u-boot will expose as an EFI framebuffer.
285 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
286 or take steps to update /etc/passwd before doing installworld on
287 existing systems. Do not skip the "mergemaster -Fp" step before
288 installworld, as described in the update procedures near the bottom
289 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
290 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
291 the ntp config file contain options that change file/dir locations.
292 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
293 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
294 taking steps to ensure that all required files/dirs are accessible
298 Big endian arm support has been removed.
301 The static environment setup in kernel configs is no longer mutually
302 exclusive with the loader(8) environment by default. In order to
303 restore the previous default behavior of disabling the loader(8)
304 environment if a static environment is present, you must specify
305 loader_env.disabled=1 in the static environment.
308 The ABI of syscalls used by management tools like sockstat and
309 netstat has been broken to allow 32-bit binaries to work on
310 64-bit kernels without modification. These programs will need
311 to match the kernel in order to function. External programs may
312 require minor modifications to accommodate a change of type in
313 structures from pointers to 64-bit virtual addresses.
316 On i386 and amd64 atomics are now inlined. Out of tree modules using
317 atomics will need to be rebuilt.
320 The '%I' format in the kern.corefile sysctl limits the number of
321 core files that a process can generate to the number stored in the
322 debug.ncores sysctl. The '%I' format is replaced by the single digit
323 index. Previously, if all indexes were taken the kernel would overwrite
324 only a core file with the highest index in a filename.
325 Currently the system will create a new core file if there is a free
326 index or if all slots are taken it will overwrite the oldest one.
329 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
330 6.0.1. Please see the 20141231 entry below for information about
331 prerequisites and upgrading, if you are not already using clang 3.5.0
335 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
336 needed to be changed to work with it. This change was made with r335763
337 and requires a mergemaster / etcupdate / etc to update the installed
341 r334930 changed the interface between the NFS modules, so they all
342 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
345 As of r334391 lld is the default amd64 system linker; it is installed
346 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
350 The kernel / userland interface for devinfo changed, so you'll
351 need a new kernel and userland as a pair for it to work (rebuilding
352 lib/libdevinfo is all that's required). devinfo and devmatch will
353 not work, but everything else will when there's a mismatch.
356 The on-disk format for hwpmc callchain records has changed to include
357 threadid corresponding to a given record. This changes the field offsets
358 and thus requires that libpmcstat be rebuilt before using a kernel
362 The vxge(4) driver has been removed. This driver was introduced into
363 HEAD one week before the Exar left the Ethernet market and is not
364 known to be used. If you have device vxge in your kernel config file
368 The amd64 kernel now requires a ld that supports ifunc to produce a
369 working kernel, either lld or a newer binutils. lld is built by default
370 on amd64, and the 'buildkernel' target uses it automatically. However,
371 it is not the default linker, so building the kernel the traditional
372 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
373 binutils port/package). lld will soon be default, and this requirement
376 NOTE: As of r334391 lld is the default system linker on amd64, and no
377 workaround is necessary.
380 The nxge(4) driver has been removed. This driver was for PCI-X 10g
381 cards made by s2io/Neterion. The company was aquired by Exar and
382 no longer sells or supports Ethernet products. If you have device
383 nxge in your kernel config file it must be removed.
386 The tz database (tzdb) has been updated to 2018e. This version more
387 correctly models time stamps in time zones with negative DST such as
388 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
389 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
390 time zone abbreviations and the tm_isdst flag.
393 The ixgb(4) driver has been removed. This driver was for an early and
394 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
395 quickly shifted to the long lived ixgbe family. If you have device
396 ixgb in your kernel config file it must be removed.
399 The lmc(4) driver has been removed. This was a WAN interface
400 card that was already reportedly rare in 2003, and had an ambiguous
401 license. If you have device lmc in your kernel config file it must
405 Support for Arcnet networks has been removed. If you have device
406 arcnet or device cm in your kernel config file they must be
410 Support for FDDI networks has been removed. If you have device
411 fddi or device fpa in your kernel config file they must be
415 In addition to supporting RFC 3164 formatted messages, the
416 syslogd(8) service is now capable of parsing RFC 5424 formatted
417 log messages. The main benefit of using RFC 5424 is that clients
418 may now send log messages with timestamps containing year numbers,
419 microseconds and time zone offsets.
421 Similarly, the syslog(3) C library function has been altered to
422 send RFC 5424 formatted messages to the local system logging
423 daemon. On systems using syslogd(8), this change should have no
424 negative impact, as long as syslogd(8) and the C library are
425 updated at the same time. On systems using a different system
426 logging daemon, it may be necessary to make configuration
427 adjustments, depending on the software used.
429 When using syslog-ng, add the 'syslog-protocol' flag to local
430 input sources to enable parsing of RFC 5424 formatted messages:
433 unix-dgram("/var/run/log" flags(syslog-protocol));
436 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
437 of the 'imuxsock' module to let messages be processed by the
438 regular RFC 3164/5424 parsing pipeline:
440 module(load="imuxsock" SysSock.UseSpecialParser="off")
442 Do note that these changes only affect communication between local
443 applications and syslogd(8). The format that syslogd(8) uses to
444 store messages on disk or forward messages to other systems
445 remains unchanged. syslogd(8) still uses RFC 3164 for these
446 purposes. Options to customize this behaviour will be added in the
447 future. Utilities that process log files stored in /var/log are
448 thus expected to continue to function as before.
450 __FreeBSD_version has been incremented to 1200061 to denote this
454 Support for token ring networks has been removed. If you
455 have "device token" in your kernel config you should remove
456 it. No device drivers supported token ring.
459 makefs was modified to be able to tag ISO9660 El Torito boot catalog
460 entries as EFI instead of overloading the i386 tag as done previously.
461 The amd64 mkisoimages.sh script used to build amd64 ISO images for
462 release was updated to use this. This may mean that makefs must be
463 updated before "make cdrom" can be run in the release directory. This
464 should be as simple as:
466 $ cd $SRCDIR/usr.sbin/makefs
467 $ make depend all install
470 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
471 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
472 Co-existance for the transition period will come shortly. Booting is a
473 complex environment and test coverage for Lua-enabled loaders has been
474 thin, so it would be prudent to assume it might not work and make
475 provisions for backup boot methods.
478 devmatch functionality has been turned on in devd. It will automatically
479 load drivers for unattached devices. This may cause unexpected drivers
480 to be loaded. Please report any problems to current@ and
484 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
485 6.0.0. Please see the 20141231 entry below for information about
486 prerequisites and upgrading, if you are not already using clang 3.5.0
490 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
491 This means it is used to link the kernel and userland libraries and
492 executables, but is not yet installed as /usr/bin/ld by default.
494 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
495 WITHOUT_LLD_BOOTSTRAP=yes
498 On i386, pmtimer has been removed. Its functionality has been folded
499 into apm. It was a no-op on ACPI in current for a while now (but was
500 still needed on i386 in FreeBSD 11 and earlier). Users may need to
501 remove it from kernel config files.
504 The use of RSS hash from the network card aka flowid has been
505 disabled by default for lagg(4) as it's currently incompatible with
506 the lacp and loadbalance protocols.
508 This can be re-enabled by setting the following in loader.conf:
509 net.link.lagg.default_use_flowid="1"
512 The SW_WATCHDOG option is no longer necessary to enable the
513 hardclock-based software watchdog if no hardware watchdog is
514 configured. As before, SW_WATCHDOG will cause the software
515 watchdog to be enabled even if a hardware watchdog is configured.
518 r326887 fixes the issue described in the 20171214 UPDATING entry.
519 r326888 flips the switch back to building GELI support always.
522 r362593 broke ZFS + GELI support for reasons unknown. However,
523 it also broke ZFS support generally, so GELI has been turned off
524 by default as the lesser evil in r326857. If you boot off ZFS and/or
525 GELI, it might not be a good time to update.
528 PowerPC users must update loader(8) by rebuilding world before
529 installing a new kernel, as the protocol connecting them has
530 changed. Without the update, loader metadata will not be passed
531 successfully to the kernel and users will have to enter their
532 root partition at the kernel mountroot prompt to continue booting.
533 Newer versions of loader can boot old kernels without issue.
536 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
537 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
538 to WITH/OUT_LOADER_GELI.
541 The naive and non-compliant support of posix_fallocate(2) in ZFS
542 has been removed as of r325320. The system call now returns EINVAL
543 when used on a ZFS file. Although the new behavior complies with the
544 standard, some consumers are not prepared to cope with it.
545 One known victim is lld prior to r325420.
548 Building in a FreeBSD src checkout will automatically create object
549 directories now rather than store files in the current directory if
550 'make obj' was not ran. Calling 'make obj' is no longer necessary.
551 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
552 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
556 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
557 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
558 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
559 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
560 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
561 The UNIFIED_OBJDIR option is a transitional feature that will be
562 removed for 12.0 release; please migrate to the new format for any
563 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
564 than hardcoding paths.
567 The native-xtools target no longer installs the files by default to the
568 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
569 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
572 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
573 options are changing from controlling the build if defined / undefined
574 to controlling the build with explicit 'yes' or 'no' values. They will
575 shift to WITH/WITHOUT options to match other options in the system.
578 libstand has turned into a private library for sys/boot use only.
579 It is no longer supported as a public interface outside of sys/boot.
582 The arm port has split armv6 into armv6 and armv7. armv7 is now
583 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
584 and are running a kernel from before r324363, you will need to add
585 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
588 When building multiple kernels using KERNCONF, non-existent KERNCONF
589 files will produce an error and buildkernel will fail. Previously
590 missing KERNCONF files silently failed giving no indication as to
591 why, only to subsequently discover during installkernel that the
592 desired kernel was never built in the first place.
595 The default serial number format for CTL LUNs has changed. This will
596 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
597 or iSCSI clients care about their LUNs' serial numbers. Users who
598 require serial number stability should hardcode serial numbers in
602 For 32-bit arm compiled for hard-float support, soft-floating point
603 binaries now always get their shared libraries from
604 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
605 /usr/libsoft also existed). Only users with a hard-float ld.so, but
606 soft-float everything else should be affected.
609 The geli password typed at boot is now hidden. To restore the previous
610 behavior, see geli(8) for configuration options.
613 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
614 sysctl values. Minor nit, but requires a rebuild of both world/kernel
618 "make check" behavior (made in ^/head@r295380) has been changed to
619 execute from a limited sandbox, as opposed to executing from
623 - The "beforecheck" and "aftercheck" targets are now specified.
624 - ${CHECKDIR} (added in commit noted above) has been removed.
625 - Legacy behavior can be enabled by setting
626 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
628 If the limited sandbox mode is enabled, "make check" will execute
629 "make distribution", then install, execute the tests, and clean up the
630 sandbox if successful.
632 The "make distribution" and "make install" targets are typically run as
633 root to set appropriate permissions and ownership at installation time.
634 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
635 environment if executing "make check" with limited sandbox mode using
636 an unprivileged user.
639 Since the switch to GPT disk labels, fsck for UFS/FFS has been
640 unable to automatically find alternate superblocks. As of r322297,
641 the information needed to find alternate superblocks has been
642 moved to the end of the area reserved for the boot block.
643 Filesystems created with a newfs of this vintage or later
644 will create the recovery information. If you have a filesystem
645 created prior to this change and wish to have a recovery block
646 created for your filesystem, you can do so by running fsck in
647 foreground mode (i.e., do not use the -p or -y options). As it
648 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
649 to which you should answer yes.
652 As of r321665, an NFSv4 server configuration that services
653 Kerberos mounts or clients that do not support the uid/gid in
654 owner/owner_group string capability, must explicitly enable
655 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
656 machine's /etc/rc.conf file.
659 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
660 Please see the 20141231 entry below for information about prerequisites
661 and upgrading, if you are not already using clang 3.5.0 or higher.
664 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
665 r-commands (rlogin, rsh, etc.) to be built with the base system.
668 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
669 a very major ABI incompatible change, so users of FreeBSD/powerpc must
670 be careful when performing source upgrades. It is best to run
671 'make installworld' from an alternate root system, either a live
672 CD/memory stick, or a temporary root partition. Additionally, all ports
673 must be recompiled. powerpc64 is largely unaffected, except in the case
674 of 32-bit compatibility. All 32-bit binaries will be affected.
677 Forward compatibility for the "ino64" project have been committed. This
678 will allow most new binaries to run on older kernels in a limited
679 fashion. This prevents many of the common foot-shooting actions in the
680 upgrade as well as the limited ability to roll back the kernel across
681 the ino64 upgrade. Complicated use cases may not work properly, though
682 enough simpler ones work to allow recovery in most situations.
685 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
686 if you require the GPL compiler.
689 The internal ABI used for communication between the NFS kernel modules
690 was changed by r320085, so __FreeBSD_version was bumped to
691 ensure all the NFS related modules are updated together.
694 The ABI of struct event was changed by extending the data
695 member to 64bit and adding ext fields. For upgrade, same
696 precautions as for the entry 20170523 "ino64" must be
700 The GNU roff toolchain has been removed from base. To render manpages
701 which are not supported by mandoc(1), man(1) can fallback on GNU roff
702 from ports (and recommends to install it).
703 To render roff(7) documents, consider using GNU roff from ports or the
704 heirloom doctools roff toolchain from ports via pkg install groff or
705 via pkg install heirloom-doctools.
708 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
709 smaller runtime footprint builds. This is useful for embedded systems
710 which only require one chipset support.
712 If you load it as a module, make sure this is in /boot/loader.conf:
716 This will load the HAL, all chip/RF backends and if_ath_pci.
717 If you have if_ath_pci in /boot/loader.conf, ensure it is after
718 if_ath or it will not load any HAL chipset support.
720 If you want to selectively load things (eg on ye cheape ARM/MIPS
721 platforms where RAM is at a premium) you should:
724 * load the chip modules in question
725 * load ath_rate, ath_dfs
727 * load if_ath_pci and/or if_ath_ahb depending upon your particular
728 bus bind type - this is where probe/attach is done.
730 For further comments/feedback, poke adrian@ .
733 The "ino64" 64-bit inode project has been committed, which extends
734 a number of types to 64 bits. Upgrading in place requires care and
735 adherence to the documented upgrade procedure.
737 If using a custom kernel configuration ensure that the
738 COMPAT_FREEBSD11 option is included (as during the upgrade the
739 system will be running the ino64 kernel with the existing world).
741 For the safest in-place upgrade begin by removing previous build
742 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
743 procedure documented below under the heading "To rebuild everything and
744 install it on the current system." Specifically, a reboot is required
745 after installing the new kernel before installing world. While an
746 installworld normally works by accident from multiuser after rebooting
747 the proper kernel, there are many cases where this will fail across this
748 upgrade and installworld from single user is required.
751 The NATM framework including the en(4), fatm(4), hatm(4), and
752 patm(4) devices has been removed. Consumers should plan a
753 migration before the end-of-life date for FreeBSD 11.
756 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
757 diff has not been implemented, if those are needed a newer version of
758 GNU diff is available via the diffutils package under the gdiff name.
761 As of r316810 for ipfilter, keep frags is no longer assumed when
762 keep state is specified in a rule. r316810 aligns ipfilter with
763 documentation in man pages separating keep frags from keep state.
764 This allows keep state to be specified without forcing keep frags
765 and allows keep frags to be specified independently of keep state.
766 To maintain previous behaviour, also specify keep frags with
767 keep state (as documented in ipf.conf.5).
770 arm64 builds now use the base system LLD 4.0.0 linker by default,
771 instead of requiring that the aarch64-binutils port or package be
772 installed. To continue using aarch64-binutils, set
773 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
776 The UDP optimization in entry 20160818 that added the sysctl
777 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
778 packets will no longer be treated as L3 broadcast packets.
781 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
782 use any explicitly assigned loopback address available in the jail
783 instead of using the first assigned address of the jail.
786 The ctl.ko module no longer implements the iSCSI target frontend:
787 cfiscsi.ko does instead.
789 If building cfiscsi.ko as a kernel module, the module can be loaded
790 via one of the following methods:
791 - `cfiscsi_load="YES"` in loader.conf(5).
792 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
793 - ctladm(8)/ctld(8), when compiled with iSCSI support
794 (`WITH_ISCSI=yes` in src.conf(5))
796 Please see cfiscsi(4) for more details.
799 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
800 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
801 same source (previously, the dependency of mmcsd.ko on mmc.ko was
802 missing, but mmcsd.ko now will refuse to load if it is incompatible
806 The syntax of ipfw(8) named states was changed to avoid ambiguity.
807 If you have used named states in the firewall rules, you need to modify
808 them after installworld and before rebooting. Now named states must
809 be prefixed with colon.
812 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
813 removed as the userland we provide cannot use them. The KMS version
814 (sys/dev/drm2) supports the same hardware.
817 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
818 Please see the 20141231 entry below for information about prerequisites
819 and upgrading, if you are not already using clang 3.5.0 or higher.
822 The code that provides support for ZFS .zfs/ directory functionality
823 has been reimplemented. It's not possible now to create a snapshot
824 by mkdir under .zfs/snapshot/. That should be the only user visible
828 EISA bus support has been removed. The WITH_EISA option is no longer
832 MCA bus support has been removed.
835 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
836 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
839 The EM_MULTIQUEUE kernel configuration option is deprecated now that
840 the em(4) driver conforms to iflib specifications.
843 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
844 IFLIB. If you have a custom kernel configuration that excludes em(4)
845 but you use igb(4), you need to re-add em(4) to your custom
849 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
850 Please see the 20141231 entry below for information about prerequisites
851 and upgrading, if you are not already using clang 3.5.0 or higher.
854 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
855 Please see the 20141231 entry below for information about prerequisites
856 and upgrading, if you are not already using clang 3.5.0 or higher.
859 The layout of the pmap structure has changed for powerpc to put the pmap
860 statistics at the front for all CPU variations. libkvm(3) and all tools
861 that link against it need to be recompiled.
864 isl(4) and cyapa(4) drivers now require a new driver,
865 chromebook_platform(4), to work properly on Chromebook-class hardware.
866 On other types of hardware the drivers may need to be configured using
867 device hints. Please see the corresponding manual pages for details.
870 The urtwn(4) driver was merged into rtwn(4) and now consists of
871 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
873 Also, firmware for RTL8188CE was renamed due to possible name
874 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
877 GNU rcs has been removed from base. It is available as packages:
878 - rcs: Latest GPLv3 GNU rcs version.
879 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
883 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
884 modules now requires that the kernel configuration contain the
885 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
888 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
889 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
892 Relocatable object files with the extension of .So have been renamed
893 to use an extension of .pico instead. The purpose of this change is
894 to avoid a name clash with shared libraries on case-insensitive file
895 systems. On those file systems, foo.So is the same file as foo.so.
898 GNU rcs has been turned off by default. It can (temporarily) be built
899 again by adding WITH_RCS knob in src.conf.
900 Otherwise, GNU rcs is available from packages:
901 - rcs: Latest GPLv3 GNU rcs version.
902 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
905 The backup_uses_rcs functionality has been removed from rc.subr.
908 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
909 two separate components, QUEUE_MACRO_DEBUG_TRACE and
910 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
911 QUEUE_MACRO_DEBUG behavior.
914 r304787 changed some ioctl interfaces between the iSCSI userspace
915 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
916 rebuilt to work with new kernels. __FreeBSD_version has been bumped
920 The UDP receive code has been updated to only treat incoming UDP
921 packets that were addressed to an L2 broadcast address as L3
922 broadcast packets. It is not expected that this will affect any
923 standards-conforming UDP application. The new behaviour can be
924 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
928 Remove the openbsd_poll system call.
929 __FreeBSD_version has been bumped because of this.
932 The stable/11 branch has been created from head@r302406.
935 The libc stub for the pipe(2) system call has been replaced with
936 a wrapper that calls the pipe2(2) system call and the pipe(2)
937 system call is now only implemented by the kernels that include
938 "options COMPAT_FREEBSD10" in their config file (this is the
939 default). Users should ensure that this option is enabled in
940 their kernel or upgrade userspace to r302092 before upgrading their
944 CAM will now strip leading spaces from SCSI disks' serial numbers.
945 This will affect users who create UFS filesystems on SCSI disks using
946 those disk's diskid device nodes. For example, if /etc/fstab
947 previously contained a line like
948 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
949 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
950 transforms like gmirror may also be affected. ZFS users should
954 The bitstring(3) API has been updated with new functionality and
955 improved performance. But it is binary-incompatible with the old API.
956 Objects built with the new headers may not be linked against objects
957 built with the old headers.
960 The brk and sbrk functions have been removed from libc on arm64.
961 Binutils from ports has been updated to not link to these
962 functions and should be updated to the latest version before
963 installing a new libc.
966 The armv6 port now defaults to hard float ABI. Limited support
967 for running both hardfloat and soft float on the same system
968 is available using the libraries installed with -DWITH_LIBSOFT.
969 This has only been tested as an upgrade path for installworld
970 and packages may fail or need manual intervention to run. New
971 packages will be needed.
973 To update an existing self-hosted armv6hf system, you must add
974 TARGET_ARCH=armv6 on the make command line for both the build
975 and the install steps.
978 Kernel modules compiled outside of a kernel build now default to
979 installing to /boot/modules instead of /boot/kernel. Many kernel
980 modules built this way (such as those in ports) already overrode
981 KMODDIR explicitly to install into /boot/modules. However,
982 manually building and installing a module from /sys/modules will
983 now install to /boot/modules instead of /boot/kernel.
986 The CAM I/O scheduler has been committed to the kernel. There should be
987 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
988 list of known rogues that claim support for this but actually corrupt
989 data is believed to be complete, be on the lookout for data
990 corruption. The known rogue list is believed to be complete:
992 o Crucial MX100, M550 drives with MU01 firmware.
993 o Micron M510 and M550 drives with MU01 firmware.
994 o Micron M500 prior to MU07 firmware
995 o Samsung 830, 840, and 850 all firmwares
996 o FCCT M500 all firmwares
998 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
999 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1000 updated firmware. Black listed drives will work correctly because these
1001 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1002 this list is the same as found in Linux, it's believed there are no
1003 other rogues in the market place. All other models from the above
1006 To be safe, if you are at all concerned, you can quirk each of your
1007 drives to prevent NCQ from being sent by setting:
1008 kern.cam.ada.X.quirks="0x2"
1009 in loader.conf. If the drive requires the 4k sector quirk, set the
1010 quirks entry to 0x3.
1013 The FAST_DEPEND build option has been removed and its functionality is
1014 now the one true way. The old mkdep(1) style of 'make depend' has
1015 been removed. See 20160311 for further details.
1018 Resource range types have grown from unsigned long to uintmax_t. All
1019 drivers, and anything using libdevinfo, need to be recompiled.
1022 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1023 builds. It no longer runs mkdep(1) during 'make depend', and the
1024 'make depend' stage can safely be skipped now as it is auto ran
1025 when building 'make all' and will generate all SRCS and DPSRCS before
1026 building anything else. Dependencies are gathered at compile time with
1027 -MF flags kept in separate .depend files per object file. Users should
1028 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1029 stale .depend files.
1032 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1033 kernel modules. Therefore, if you load any kernel modules at boot time,
1034 please install the boot loaders after you install the kernel, but before
1038 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1039 make installkernel KERNCONF=YOUR_KERNEL_HERE
1040 make -C sys/boot install
1041 <reboot in single user>
1043 Then follow the usual steps, described in the General Notes section,
1047 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1048 see the 20141231 entry below for information about prerequisites and
1049 upgrading, if you are not already using clang 3.5.0 or higher.
1052 The AIO subsystem is now a standard part of the kernel. The
1053 VFS_AIO kernel option and aio.ko kernel module have been removed.
1054 Due to stability concerns, asynchronous I/O requests are only
1055 permitted on sockets and raw disks by default. To enable
1056 asynchronous I/O requests on all file types, set the
1057 vfs.aio.enable_unsafe sysctl to a non-zero value.
1060 The ELF object manipulation tool objcopy is now provided by the
1061 ELF Tool Chain project rather than by GNU binutils. It should be a
1062 drop-in replacement, with the addition of arm64 support. The
1063 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1064 to obtain the GNU version if necessary.
1067 Building ZFS pools on top of zvols is prohibited by default. That
1068 feature has never worked safely; it's always been prone to deadlocks.
1069 Using a zvol as the backing store for a VM guest's virtual disk will
1070 still work, even if the guest is using ZFS. Legacy behavior can be
1071 restored by setting vfs.zfs.vol.recursive=1.
1074 The NONE and HPN patches has been removed from OpenSSH. They are
1075 still available in the security/openssh-portable port.
1078 With the addition of ypldap(8), a new _ypldap user is now required
1079 during installworld. "mergemaster -p" can be used to add the user
1080 prior to installworld, as documented in the handbook.
1083 The tftp loader (pxeboot) now uses the option root-path directive. As a
1084 consequence it no longer looks for a pxeboot.4th file on the tftp
1085 server. Instead it uses the regular /boot infrastructure as with the
1089 The code to start recording plug and play data into the modules has
1090 been committed. While the old tools will properly build a new kernel,
1091 a number of warnings about "unknown metadata record 4" will be produced
1092 for an older kldxref. To avoid such warnings, make sure to rebuild
1093 the kernel toolchain (or world). Make sure that you have r292078 or
1094 later when trying to build 292077 or later before rebuilding.
1097 Debug data files are now built by default with 'make buildworld' and
1098 installed with 'make installworld'. This facilitates debugging but
1099 requires more disk space both during the build and for the installed
1100 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1104 r291527 changed the internal interface between the nfsd.ko and
1105 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1106 __FreeBSD_version has been bumped because of this.
1109 Add support for unicode collation strings leads to a change of
1110 order of files listed by ls(1) for example. To get back to the old
1111 behaviour, set LC_COLLATE environment variable to "C".
1113 Databases administrators will need to reindex their databases given
1114 collation results will be different.
1116 Due to a bug in install(1) it is recommended to remove the ancient
1117 locales before running make installworld.
1119 rm -rf /usr/share/locale/*
1122 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1123 libcrypto.so.7 or libssl.so.7 must be recompiled.
1126 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1127 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1128 should be replaced with isp_2400 and isp_2500 modules respectively.
1131 The build previously allowed using 'make -n' to not recurse into
1132 sub-directories while showing what commands would be executed, and
1133 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1134 and 'make -N' will not.
1137 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1138 and etcupdate will now use this file. A custom sendmail.cf is now
1139 updated via this mechanism rather than via installworld. If you had
1140 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1141 want to remove the exclusion or change it to "always install".
1142 /etc/mail/sendmail.cf is now managed the same way regardless of
1143 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1144 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1147 Compatibility shims for legacy ATA device names have been removed.
1148 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1149 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1150 environment variables, /dev/ad* and /dev/ar* symbolic links.
1153 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1154 Please see the 20141231 entry below for information about prerequisites
1155 and upgrading, if you are not already using clang 3.5.0 or higher.
1158 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1159 and renamed from .symbols to .debug. This reduces the size requirements
1160 on the boot partition or file system and provides consistency with
1161 userland debug files.
1163 When using the supported kernel installation method the
1164 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1165 as is done with /boot/kernel.
1167 Developers wishing to maintain the historical behavior of installing
1168 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1171 The wireless drivers had undergone changes that remove the 'parent
1172 interface' from the ifconfig -l output. The rc.d network scripts
1173 used to check presence of a parent interface in the list, so old
1174 scripts would fail to start wireless networking. Thus, etcupdate(3)
1175 or mergemaster(8) run is required after kernel update, to update your
1176 rc.d scripts in /etc.
1179 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1180 These configurations are now automatically interpreted as
1181 'scrub fragment reassemble'.
1184 Kernel-loadable modules for the random(4) device are back. To use
1185 them, the kernel must have
1188 options RANDOM_LOADABLE
1190 kldload(8) can then be used to load random_fortuna.ko
1191 or random_yarrow.ko. Please note that due to the indirect
1192 function calls that the loadable modules need to provide,
1193 the build-in variants will be slightly more efficient.
1195 The random(4) kernel option RANDOM_DUMMY has been retired due to
1196 unpopularity. It was not all that useful anyway.
1199 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1200 Control over building the ELF Tool Chain tools is now provided by
1201 the WITHOUT_TOOLCHAIN knob.
1204 The polarity of Pulse Per Second (PPS) capture events with the
1205 uart(4) driver has been corrected. Prior to this change the PPS
1206 "assert" event corresponded to the trailing edge of a positive PPS
1207 pulse and the "clear" event was the leading edge of the next pulse.
1209 As the width of a PPS pulse in a typical GPS receiver is on the
1210 order of 1 millisecond, most users will not notice any significant
1211 difference with this change.
1213 Anyone who has compensated for the historical polarity reversal by
1214 configuring a negative offset equal to the pulse width will need to
1215 remove that workaround.
1218 The default group assigned to /dev/dri entries has been changed
1219 from 'wheel' to 'video' with the id of '44'. If you want to have
1220 access to the dri devices please add yourself to the video group
1223 # pw groupmod video -m $USER
1226 The menu.rc and loader.rc files will now be replaced during
1227 upgrades. Please migrate local changes to menu.rc.local and
1228 loader.rc.local instead.
1231 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1232 strings and strip have been removed. The src.conf(5) knob
1233 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1236 As ZFS requires more kernel stack pages than is the default on some
1237 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1238 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1240 Please consider using 'options KSTACK_PAGES=X' where X is greater
1241 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1244 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1245 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1246 default, i.e., they will not contain "::". For example, instead
1247 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1248 to have a more specific match, such as different map entries for
1249 IPv6:0:0 vs IPv6:0. This change requires that configuration
1250 data (including maps, files, classes, custom ruleset, etc.) must
1251 use the same format, so make certain such configuration data is
1252 upgrading. As a very simple check search for patterns like
1253 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1254 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1255 the cf option UseCompressedIPv6Addresses.
1258 The default kernel entropy-processing algorithm is now
1259 Fortuna, replacing Yarrow.
1261 Assuming you have 'device random' in your kernel config
1262 file, the configurations allow a kernel option to override
1263 this default. You may choose *ONE* of:
1265 options RANDOM_YARROW # Legacy /dev/random algorithm.
1266 options RANDOM_DUMMY # Blocking-only driver.
1268 If you have neither, you get Fortuna. For most people,
1269 read no further, Fortuna will give a /dev/random that works
1270 like it always used to, and the difference will be irrelevant.
1272 If you remove 'device random', you get *NO* kernel-processed
1273 entropy at all. This may be acceptable to folks building
1274 embedded systems, but has complications. Carry on reading,
1275 and it is assumed you know what you need.
1277 *PLEASE* read random(4) and random(9) if you are in the
1278 habit of tweaking kernel configs, and/or if you are a member
1279 of the embedded community, wanting specific and not-usual
1280 behaviour from your security subsystems.
1282 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1283 random', you will NOT have a functioning /dev/random, and
1284 many cryptographic features will not work, including SSH.
1285 You may also find strange behaviour from the random(3) set
1286 of library functions, in particular sranddev(3), srandomdev(3)
1287 and arc4random(3). The reason for this is that the KERN_ARND
1288 sysctl only returns entropy if it thinks it has some to
1289 share, and with RANDOM_DUMMY or no 'device random' this
1293 An additional fix for the issue described in the 20150614 sendmail
1294 entry below has been committed in revision 284717.
1297 FreeBSD's old make (fmake) has been removed from the system. It is
1298 available as the devel/fmake port or via pkg install fmake.
1301 The fix for the issue described in the 20150614 sendmail entry
1302 below has been committed in revision 284436. The work
1303 around described in that entry is no longer needed unless the
1304 default setting is overridden by a confDH_PARAMETERS configuration
1305 setting of '5' or pointing to a 512 bit DH parameter file.
1308 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1309 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1310 and devel/kyua to version 0.20+ and adjust any calling code to work
1311 with Kyuafile and kyua.
1314 The import of openssl to address the FreeBSD-SA-15:10.openssl
1315 security advisory includes a change which rejects handshakes
1316 with DH parameters below 768 bits. sendmail releases prior
1317 to 8.15.2 (not yet released), defaulted to a 512 bit
1318 DH parameter setting for client connections. To work around
1319 this interoperability, sendmail can be configured to use a
1320 2048 bit DH parameter by:
1322 1. Edit /etc/mail/`hostname`.mc
1323 2. If a setting for confDH_PARAMETERS does not exist or
1324 exists and is set to a string beginning with '5',
1325 replace it with '2'.
1326 3. If a setting for confDH_PARAMETERS exists and is set to
1327 a file path, create a new file with:
1328 openssl dhparam -out /path/to/file 2048
1329 4. Rebuild the .cf file:
1330 cd /etc/mail/; make; make install
1331 5. Restart sendmail:
1332 cd /etc/mail/; make restart
1334 A sendmail patch is coming, at which time this file will be
1338 Generation of legacy formatted entries have been disabled by default
1339 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1340 entries were converted to use the new format by default when the new,
1341 machine independent format have been added and supported since FreeBSD
1344 Please see the pwd_mkdb(8) manual page for further details.
1347 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1348 20141231 entry below for information about prerequisites and upgrading,
1349 if you are not already using 3.5.0 or higher.
1352 TI platform code switched to using vendor DTS files and this update
1353 may break existing systems running on Beaglebone, Beaglebone Black,
1356 - dtb files should be regenerated/reinstalled. Filenames are the
1357 same but content is different now
1358 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1359 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1360 addressing scheme is now pin 25 on /dev/gpioc3.
1361 - Pandaboard: /etc/ttys should be updated, serial console device is
1362 now /dev/ttyu2, not /dev/ttyu0
1365 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1366 If you need the GNU extension from groff soelim(1), install groff
1367 from package: pkg install groff, or via ports: textproc/groff.
1370 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1371 defined in symlink(7); previously symlinks were silently ignored.
1374 The const qualifier has been removed from iconv(3) to comply with
1375 POSIX. The ports tree is aware of this from r384038 onwards.
1378 Libraries specified by LIBADD in Makefiles must have a corresponding
1379 DPADD_<lib> variable to ensure correct dependencies. This is now
1380 enforced in src.libnames.mk.
1383 From legacy ata(4) driver was removed support for SATA controllers
1384 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1385 Kernel modules ataahci and ataadaptec were removed completely,
1386 replaced by ahci and mvs modules respectively.
1389 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1390 the 20141231 entry below for information about prerequisites and
1391 upgrading, if you are not already using 3.5.0 or higher.
1394 The 32-bit PowerPC kernel has been changed to a position-independent
1395 executable. This can only be booted with a version of loader(8)
1396 newer than January 31, 2015, so make sure to update both world and
1397 kernel before rebooting.
1400 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1401 but before r278950, the RNG was not seeded properly. Immediately
1402 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1403 ssh keys or openssl keys) that were generated w/ a kernel from that
1404 range. This does not affect programs that directly used /dev/random
1405 or /dev/urandom. All userland uses of arc4random(3) are affected.
1408 The autofs(4) ABI was changed in order to restore binary compatibility
1409 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1410 with the new kernel.
1413 The powerpc64 kernel has been changed to a position-independent
1414 executable. This can only be booted with a new version of loader(8),
1415 so make sure to update both world and kernel before rebooting.
1418 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1419 only release, no new features have been added. Please see the 20141231
1420 entry below for information about prerequisites and upgrading, if you
1421 are not already using 3.5.0.
1424 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1425 taken from the ELF Tool Chain project rather than GNU binutils. They
1426 should be drop-in replacements, with the addition of arm64 support.
1427 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1428 binutils tools, if necessary. See 20150805 for updated information.
1431 The default Unbound configuration now enables remote control
1432 using a local socket. Users who have already enabled the
1433 local_unbound service should regenerate their configuration
1434 by running "service local_unbound setup" as root.
1437 The GNU texinfo and GNU info pages have been removed.
1438 To be able to view GNU info pages please install texinfo from ports.
1441 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1443 As of this release, a prerequisite for building clang, llvm and lldb is
1444 a C++11 capable compiler and C++11 standard library. This means that to
1445 be able to successfully build the cross-tools stage of buildworld, with
1446 clang as the bootstrap compiler, your system compiler or cross compiler
1447 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1448 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1451 On any standard FreeBSD 10.x or 11.x installation, where clang and
1452 libc++ are on by default (that is, on x86 or arm), this should work out
1455 On 9.x installations where clang is enabled by default, e.g. on x86 and
1456 powerpc, libc++ will not be enabled by default, so libc++ should be
1457 built (with clang) and installed first. If both clang and libc++ are
1458 missing, build clang first, then use it to build libc++.
1460 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1461 the instructions for 9.x above.
1463 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1464 default, and do not build clang.
1466 Many embedded systems are resource constrained, and will not be able to
1467 build clang in a reasonable time, or in some cases at all. In those
1468 cases, cross building bootable systems on amd64 is a workaround.
1470 This new version of clang introduces a number of new warnings, of which
1471 the following are most likely to appear:
1475 This warns in two cases, for both C and C++:
1476 * When the code is trying to take the absolute value of an unsigned
1477 quantity, which is effectively a no-op, and almost never what was
1478 intended. The code should be fixed, if at all possible. If you are
1479 sure that the unsigned quantity can be safely cast to signed, without
1480 loss of information or undefined behavior, you can add an explicit
1481 cast, or disable the warning.
1483 * When the code is trying to take an absolute value, but the called
1484 abs() variant is for the wrong type, which can lead to truncation.
1485 If you want to disable the warning instead of fixing the code, please
1486 make sure that truncation will not occur, or it might lead to unwanted
1489 -Wtautological-undefined-compare and
1490 -Wundefined-bool-conversion
1492 These warn when C++ code is trying to compare 'this' against NULL, while
1493 'this' should never be NULL in well-defined C++ code. However, there is
1494 some legacy (pre C++11) code out there, which actively abuses this
1495 feature, which was less strictly defined in previous C++ versions.
1497 Squid and openjdk do this, for example. The warning can be turned off
1498 for C++98 and earlier, but compiling the code in C++11 mode might result
1499 in unexpected behavior; for example, the parts of the program that are
1500 unreachable could be optimized away.
1503 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1504 kernel sources have been removed. The .h files remain, since some
1505 utilities include them. This will need to be fixed later.
1506 If "mount -t oldnfs ..." is attempted, it will fail.
1507 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1508 the utilities will report errors.
1511 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1512 directories to top level SUBDIR variable when their parent
1513 directory is included in LOCAL_DIRS. Users with build systems with
1514 such hierarchies and without SUBDIR entries in the parent
1515 directory Makefiles should add them or add the directories to
1519 faith(4) and faithd(8) have been removed from the base system. Faith
1520 has been obsolete for a very long time.
1523 vt(4), the new console driver, is enabled by default. It brings
1524 support for Unicode and double-width characters, as well as
1525 support for UEFI and integration with the KMS kernel video
1528 You may need to update your console settings in /etc/rc.conf,
1529 most probably the keymap. During boot, /etc/rc.d/syscons will
1530 indicate what you need to do.
1532 vt(4) still has issues and lacks some features compared to
1533 syscons(4). See the wiki for up-to-date information:
1534 https://wiki.freebsd.org/Newcons
1536 If you want to keep using syscons(4), you can do so by adding
1537 the following line to /boot/loader.conf:
1541 pjdfstest has been integrated into kyua as an opt-in test suite.
1542 Please see share/doc/pjdfstest/README for more details on how to
1546 gperf has been removed from the base system for architectures
1547 that use clang. Ports that require gperf will obtain it from the
1551 pjdfstest has been moved from tools/regression/pjdfstest to
1555 At svn r271982, The default linux compat kernel ABI has been adjusted
1556 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1557 update. If you wish to continue using the linux-f10 compat ports,
1558 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1559 encouraged to update their linux-compat packages to linux-c6 during
1560 their next update cycle.
1563 The ofwfb driver, used to provide a graphics console on PowerPC when
1564 using vt(4), no longer allows mmap() of all physical memory. This
1565 will prevent Xorg on PowerPC with some ATI graphics cards from
1566 initializing properly unless x11-servers/xorg-server is updated to
1570 The xdev targets have been converted to using TARGET and
1571 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1574 The default unbound configuration has been modified to address
1575 issues with reverse lookups on networks that use private
1576 address ranges. If you use the local_unbound service, run
1577 "service local_unbound setup" as root to regenerate your
1578 configuration, then "service local_unbound reload" to load the
1582 The GNU texinfo and GNU info pages are not built and installed
1583 anymore, WITH_INFO knob has been added to allow to built and install
1585 UPDATE: see 20150102 entry on texinfo's removal
1588 The GNU readline library is now an INTERNALLIB - that is, it is
1589 statically linked into consumers (GDB and variants) in the base
1590 system, and the shared library is no longer installed. The
1591 devel/readline port is available for third party software that
1595 The Itanium architecture (ia64) has been removed from the list of
1596 known architectures. This is the first step in the removal of the
1600 Commit r268115 has added NFSv4.1 server support, merged from
1601 projects/nfsv4.1-server. Since this includes changes to the
1602 internal interfaces between the NFS related modules, a full
1603 build of the kernel and modules will be necessary.
1604 __FreeBSD_version has been bumped.
1607 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1608 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1609 which differs from the behaviour controlled by this knob.)
1612 Maximal length of the serial number in CTL was increased from 16 to
1613 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1614 and ctld, need to be rebuilt to work with a new kernel.
1617 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1618 1 respectively to match the upstream numbers. They were out of
1619 sync because, when they were originally added to FreeBSD, the
1620 upstream versions were not respected. These libraries are private
1621 and not yet built by default, so renumbering them should be a
1622 non-issue. However, unclean source trees will yield broken test
1623 programs once the operator executes "make delete-old-libs" after a
1624 "make installworld".
1626 Additionally, the atf-sh binary was made private by moving it into
1627 /usr/libexec/. Already-built shell test programs will keep the
1628 path to the old binary so they will break after "make delete-old"
1631 If you are using WITH_TESTS=yes (not the default), wipe the object
1632 tree and rebuild from scratch to prevent spurious test failures.
1633 This is only needed once: the misnumbered libraries and misplaced
1634 binaries have been added to OptionalObsoleteFiles.inc so they will
1635 be removed during a clean upgrade.
1638 Clang and llvm have been upgraded to 3.4.1 release.
1641 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1642 be removed to avoid issues in the future (and has been added to
1646 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1647 past, it affected all builds that used the bsd.*.mk files. The old
1648 behavior was a bug, but people may have relied upon it. To get this
1649 behavior back, you can .include /etc/src.conf from /etc/make.conf
1650 (which is still global and isn't changed). This also changes the
1651 behavior of incremental builds inside the tree of individual
1652 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1653 Although this has survived make universe and some upgrade scenarios,
1654 other upgrade scenarios may have broken. At least one form of
1655 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1656 as well... In cases where MAKESYSPATH isn't working with this
1657 setting, you'll need to set it to the full path to your tree.
1659 One side effect of all this cleaning up is that bsd.compiler.mk
1660 is no longer implicitly included by bsd.own.mk. If you wish to
1661 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1665 The lindev device has been removed since /dev/full has been made a
1666 standard device. __FreeBSD_version has been bumped.
1669 The knob WITHOUT_VI was added to the base system, which controls
1670 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1671 in order to reorder files share/termcap and didn't build ex(1) as a
1672 build tool, so building/installing with WITH_VI is highly advised for
1673 build hosts for older releases.
1675 This issue has been fixed in stable/9 and stable/10 in r277022 and
1676 r276991, respectively.
1679 The YES_HESIOD knob has been removed. It has been obsolete for
1680 a decade. Please move to using WITH_HESIOD instead or your builds
1681 will silently lack HESIOD.
1684 The uart(4) driver has been changed with respect to its handling
1685 of the low-level console. Previously the uart(4) driver prevented
1686 any process from changing the baudrate or the CLOCAL and HUPCL
1687 control flags. By removing the restrictions, operators can make
1688 changes to the serial console port without having to reboot.
1689 However, when getty(8) is started on the serial device that is
1690 associated with the low-level console, a misconfigured terminal
1691 line in /etc/ttys will now have a real impact.
1692 Before upgrading the kernel, make sure that /etc/ttys has the
1693 serial console device configured as 3wire without baudrate to
1694 preserve the previous behaviour. E.g:
1695 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1698 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1699 to improve performance. To re-enable it, if needed, run rpcbind
1700 with command line option -W.
1703 Switched back to the GPL dtc compiler due to updates in the upstream
1704 dts files not being supported by the BSDL dtc compiler. You will need
1705 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1706 may result while building dtb files during a kernel build if you fail
1707 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1710 Clang and llvm have been upgraded to 3.4 release.
1713 The nve(4) driver has been removed. Please use the nfe(4) driver
1714 for NVIDIA nForce MCP Ethernet adapters instead.
1717 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1718 This could cause certain C++ applications using shared libraries built
1719 against the previous version of libc++ to crash. The incompatibility
1720 has now been fixed, but any C++ applications or shared libraries built
1721 between r261283 and r261801 should be recompiled.
1724 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1725 capability mode support. Please note that enabling the feature in
1726 kernel is still highly recommended.
1729 OpenSSH is now built with sandbox support, and will use sandbox as
1730 the default privilege separation method. This requires Capsicum
1731 capability mode support in kernel.
1734 The libelf and libdwarf libraries have been updated to newer
1735 versions from upstream. Shared library version numbers for
1736 these two libraries were bumped. Any ports or binaries
1737 requiring these two libraries should be recompiled.
1738 __FreeBSD_version is bumped to 1100006.
1741 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1742 instead of providing an explicit one, this would prevent such
1743 Makefile from providing its own Kyuafile in the future during
1744 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1745 intervention is needed to clean an objdir if you use NO_CLEAN:
1746 # find /usr/obj -name Kyuafile | xargs rm -f
1749 The behavior of gss_pseudo_random() for the krb5 mechanism
1750 has changed, for applications requesting a longer random string
1751 than produced by the underlying enctype's pseudo-random() function.
1752 In particular, the random string produced from a session key of
1753 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1754 be different at the 17th octet and later, after this change.
1755 The counter used in the PRF+ construction is now encoded as a
1756 big-endian integer in accordance with RFC 4402.
1757 __FreeBSD_version is bumped to 1100004.
1760 The WITHOUT_ATF build knob has been removed and its functionality
1761 has been subsumed into the more generic WITHOUT_TESTS. If you were
1762 using the former to disable the build of the ATF libraries, you
1763 should change your settings to use the latter.
1766 The default version of mtree is nmtree which is obtained from
1767 NetBSD. The output is generally the same, but may vary
1768 slightly. If you found you need identical output adding
1769 "-F freebsd9" to the command line should do the trick. For the
1770 time being, the old mtree is available as fmtree.
1773 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1774 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1775 1.1.4_8 and verify bsdyml not linked in, before running "make
1777 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1779 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1782 The stable/10 branch has been created in subversion from head
1789 Avoid using make -j when upgrading. While generally safe, there are
1790 sometimes problems using -j to upgrade. If your upgrade fails with
1791 -j, please try again without -j. From time to time in the past there
1792 have been problems using -j with buildworld and/or installworld. This
1793 is especially true when upgrading between "distant" versions (eg one
1794 that cross a major release boundary or several minor releases, or when
1795 several months have passed on the -current branch).
1797 Sometimes, obscure build problems are the result of environment
1798 poisoning. This can happen because the make utility reads its
1799 environment when searching for values for global variables. To run
1800 your build attempts in an "environmental clean room", prefix all make
1801 commands with 'env -i '. See the env(1) manual page for more details.
1803 When upgrading from one major version to another it is generally best to
1804 upgrade to the latest code in the currently installed branch first, then
1805 do an upgrade to the new branch. This is the best-tested upgrade path,
1806 and has the highest probability of being successful. Please try this
1807 approach if you encounter problems with a major version upgrade. Since
1808 the stable 4.x branch point, one has generally been able to upgrade from
1809 anywhere in the most recent stable branch to head / current (or even the
1810 last couple of stable branches). See the top of this file when there's
1813 When upgrading a live system, having a root shell around before
1814 installing anything can help undo problems. Not having a root shell
1815 around can lead to problems if pam has changed too much from your
1816 starting point to allow continued authentication after the upgrade.
1818 This file should be read as a log of events. When a later event changes
1819 information of a prior event, the prior event should not be deleted.
1820 Instead, a pointer to the entry with the new information should be
1821 placed in the old entry. Readers of this file should also sanity check
1822 older entries before relying on them blindly. Authors of new entries
1823 should write them with this in mind.
1827 When upgrading the boot ZFS pool to a new version, always follow
1830 1.) recompile and reinstall the ZFS boot loader and boot block
1831 (this is part of "make buildworld" and "make installworld")
1833 2.) update the ZFS boot block on your boot drive
1835 The following example updates the ZFS boot block on the first
1836 partition (freebsd-boot) of a GPT partitioned drive ada0:
1837 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1839 Non-boot pools do not need these updates.
1843 If you are updating from a prior version of FreeBSD (even one just
1844 a few days old), you should follow this procedure. It is the most
1845 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1847 make kernel-toolchain
1848 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1849 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1851 To test a kernel once
1852 ---------------------
1853 If you just want to boot a kernel once (because you are not sure
1854 if it works, or if you want to boot a known bad kernel to provide
1855 debugging information) run
1856 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1857 nextboot -k testkernel
1859 To rebuild everything and install it on the current system.
1860 -----------------------------------------------------------
1861 # Note: sometimes if you are running current you gotta do more than
1862 # is listed here if you are upgrading from a really old current.
1864 <make sure you have good level 0 dumps>
1866 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1867 make installkernel KERNCONF=YOUR_KERNEL_HERE
1869 <reboot in single user> [3]
1876 To cross-install current onto a separate partition
1877 --------------------------------------------------
1878 # In this approach we use a separate partition to hold
1879 # current's root, 'usr', and 'var' directories. A partition
1880 # holding "/", "/usr" and "/var" should be about 2GB in
1883 <make sure you have good level 0 dumps>
1886 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1887 <maybe newfs current's root partition>
1888 <mount current's root partition on directory ${CURRENT_ROOT}>
1889 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1890 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1891 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1892 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1893 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1894 <reboot into current>
1895 <do a "native" rebuild/install as described in the previous section>
1896 <maybe install compatibility libraries from ports/misc/compat*>
1900 To upgrade in-place from stable to current
1901 ----------------------------------------------
1902 <make sure you have good level 0 dumps>
1904 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1905 make installkernel KERNCONF=YOUR_KERNEL_HERE
1907 <reboot in single user> [3]
1914 Make sure that you've read the UPDATING file to understand the
1915 tweaks to various things you need. At this point in the life
1916 cycle of current, things change often and you are on your own
1917 to cope. The defaults can also change, so please read ALL of
1918 the UPDATING entries.
1920 Also, if you are tracking -current, you must be subscribed to
1921 freebsd-current@freebsd.org. Make sure that before you update
1922 your sources that you have read and understood all the recent
1923 messages there. If in doubt, please track -stable which has
1924 much fewer pitfalls.
1926 [1] If you have third party modules, such as vmware, you
1927 should disable them at this point so they don't crash your
1930 [3] From the bootblocks, boot -s, and then do
1934 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
1935 cd src # full path to source
1936 adjkerntz -i # if CMOS is wall time
1937 Also, when doing a major release upgrade, it is required that
1938 you boot into single user mode to do the installworld.
1940 [4] Note: This step is non-optional. Failure to do this step
1941 can result in a significant reduction in the functionality of the
1942 system. Attempting to do it by hand is not recommended and those
1943 that pursue this avenue should read this file carefully, as well
1944 as the archives of freebsd-current and freebsd-hackers mailing lists
1945 for potential gotchas. The -U option is also useful to consider.
1946 See mergemaster(8) for more information.
1948 [5] Usually this step is a no-op. However, from time to time
1949 you may need to do this if you get unknown user in the following
1950 step. It never hurts to do it all the time. You may need to
1951 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1952 install) after the buildworld before this step if you last updated
1953 from current before 20130425 or from -stable before 20130430.
1955 [6] This only deletes old files and directories. Old libraries
1956 can be deleted by "make delete-old-libs", but you have to make
1957 sure that no program is using those libraries anymore.
1959 [8] The new kernel must be able to run existing binaries used by an
1960 installworld. When upgrading across major versions, the new kernel's
1961 configuration must include the correct COMPAT_FREEBSD<n> option for
1962 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
1963 to do so may leave you with a system that is hard to boot to recover. A
1964 GENERIC kernel will include suitable compatibility options to run
1965 binaries from older branches. Note that the ability to run binaries
1966 from unsupported branches is not guaranteed.
1968 Make sure that you merge any new devices from GENERIC since the
1969 last time you updated your kernel config file. Options also
1970 change over time, so you may need to adjust your custom kernels
1973 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1974 "?=" instead of the "=" assignment operator, so that buildworld can
1975 override the CPUTYPE if it needs to.
1977 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1978 not on the command line, or in /etc/make.conf. buildworld will
1979 warn if it is improperly defined.
1982 This file contains a list, in reverse chronological order, of major
1983 breakages in tracking -current. It is not guaranteed to be a complete
1984 list of such breakages, and only contains entries since September 23, 2011.
1985 If you need to see UPDATING entries from before that date, you will need
1986 to fetch an UPDATING file from an older FreeBSD release.
1988 Copyright information:
1990 Copyright 1998-2009 M. Warner Losh.
1992 Redistribution, publication, translation and use, with or without
1993 modification, in full or in part, in any form or format of this
1994 document are permitted without further permission from the author.
1996 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1997 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1998 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1999 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2000 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2001 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2002 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2003 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2004 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2005 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2006 POSSIBILITY OF SUCH DAMAGE.
2008 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob