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 20191023 p11 FreeBSD-EN-19:18.tzdata
21 Import tzdata 2019c. [EN-19:18.tzdata]
23 20190820 p10 FreeBSD-EN-19:16.bhyve
26 FreeBSD-SA-19:24.mqueuefs
28 Bhyve instruction emulation improvements (opcode 03H and F7H).
31 Fix IPv6 remote denial of service. [SA-19:22.mbuf]
33 Fix kernel memory disclosure from /dev/midistat. [SA-19:23.midi]
35 Fix reference count overflow in mqueuefs. [SA-19:24.mqueuefs]
37 20190806 p9 FreeBSD-EN-19:14.epoch
38 FreeBSD-EN-19:15.libunwind
39 FreeBSD-SA-19:18.bzip2
40 FreeBSD-SA-19:19.mldv2
41 FreeBSD-SA-19:20.bsnmp
42 FreeBSD-SA-19:21.bhyve
44 Fix incorrect locking in epoch(9). [EN-19:14.epoch]
46 Fix incorrect exception handling. [EN-19:15.libunwind]
48 Fix multiple vulnerabilities in bzip2. [SA-19:18.bzip2]
50 Fix ICMPv6 / MLDv2 out-of-bounds memory access. [SA-19:19.mldv2]
52 Fix insufficient message length validation in bsnmp library.
55 Fix insufficient validation of guest-supplied data (e1000 device).
58 20190724 p8 FreeBSD-EN-19:13.mds
59 FreeBSD-SA-19:12.telnet
61 FreeBSD-SA-19:15.mqueuefs
62 FreeBSD-SA-19:16.bhyve
65 Fix panic from Intel CPU vulnerability mitigation. [EN-19:13.mds]
67 Fix multiple telnet client vulnerabilities. [SA-19:12.telnet]
69 Fix pts write-after-free. [SA-19:13.pts]
71 Fix reference count overflow in mqueuefs. [SA-19:15.mqueuefs]
73 Fix byhve out-of-bounds read in XHCI device. [SA-19:16.bhyve]
75 Fix file descriptor reference count leak. [SA-19:17.fd]
77 20190702 p7 FreeBSD-EN-19:12.tzdata
78 FreeBSD-SA-19:09.iconv
80 FreeBSD-SA-19:11.cd_ioctl
82 Import tzdata 2019b. [EN-19:12.tzdata]
84 Fix iconv buffer overflow. [SA-19:09.iconv]
86 Fix kernel stack disclosure in UFS/FFS. [SA-19:10.ufs]
88 Fix privilege escalation in cd(4) driver. [SA-19:11.cd_ioctl]
90 20190619 p6 FreeBSD-EN-19:11.net
93 Fix incorrect locking in networking stack [EN-19:11.net]
95 Add ability to limit split map entries to prevent resource exhaustion
96 in non-default RACK TCP stack [SA-19:08.rack]
98 20190515 p5 FreeBSD-SA-19:07.mds [revised]
100 Fixed error in patch causing panic on i386 architecture. [SA-19:07.mds]
103 20190514 p4 FreeBSD-EN-19:08.tzdata
104 FreeBSD-EN-19:09.xinstall
112 Import tzdata 2019a. [EN-19:08.tzdata]
114 Fix install with partially matching relative paths. [EN-19:09.xinstall]
116 Fix filename validation in scp. [EN-19:10.scp]
118 Fix multiple vulnerabilities in hostapd/wpa_supplicant. [SA-19:03.wpa]
120 Fix authenticated denial of service in ntpd. [SA-19:04.ntp]
122 Fix IPv6 fragment reassembly in pf. [SA-19:05.pf]
124 Fix ICMP/ICMP6 packet filter bypass in pf. [SA-19:06.pf]
126 Add mitigations for Microarchitectural Data Sampling. [SA-19:07.mds]
129 20190205: p3 FreeBSD-SA-19:01.syscall
131 FreeBSD-EN-19:06.dtrace
134 amd64: clear callee-preserved registers on syscall exit
137 Avoid leaking fp references when truncating SCM_RIGHTS control messages.
140 dtrace: fix userspace access on boxes with SMAP [EN-19:06.dtrace]
142 Fix an LLE lookup race [EN-19:07.lle]
144 20190109: p2 FreeBSD-EN-19:01.cc_cubic
146 FreeBSD-EN-19:03.sqlite
147 FreeBSD-EN-19:04.tzdata
149 Revert CC Cubic: fix underflow for cubic_cwnd() [EN-19:01.cc_cubic]
151 Fix a TCP handling of received segments. [EN-19:02.tcp]
153 Update sqlite3-3.23.1 --> sqlite3-3.26.0 (3260000) [EN-19:03.sqlite]
155 Import tzdata 2018h, 2018i [EN-19:04.tzdata]
157 20181219: p1 FreeBSD-SA-18:15.bootpd
159 bootpd: validate hardware type [SA-18:15.bootpd]
165 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
166 has been converted to a port (misc/ctm) and will be removed from
167 FreeBSD-13. A depreciation warning will be printed to stderr by
168 the ctm command, but the functionality will remain in base for all
172 The stable/12 branch has been created in subversion from head
176 Ports for the DRM modules have been simplified. Now, amd64 users should
177 just install the drm-kmod port. All others should install
180 Graphics hardware that's newer than about 2010 usually works with
181 drm-kmod. For hardware older than 2013, however, some users will need
182 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
183 than 2008 usually only works in drm-legacy-kmod. The graphics team can
184 only commit to hardware made since 2013 due to the complexity of the
185 market and difficulty to test all the older cards effectively. If you
186 have hardware supported by drm-kmod, you are strongly encouraged to use
187 that as you will get better support.
189 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
190 elsewhere, the drm and drm2 modules will be eliminated from the src base
191 soon (with a limited exception for arm). Please update to the package asap
192 and report any issues to x11@freebsd.org.
194 Generally, anybody using the drm*-kmod packages should add
195 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
196 cross-threading surprises, especially with automatic driver
197 loading from X11 startup. These will become the defaults in 13-current
201 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
202 custom kernel and module loading configuration files must be updated
203 accordingly. Moreover, interfaces previous presented as ixlvN to the
204 system are now exposed as iavfN and network configuration files must
205 be adjusted as necessary.
208 OpenSSL has been updated to version 1.1.1. This update included
209 additional various API changes througout the base system. It is
210 important to rebuild third-party software after upgrading. The value
211 of __FreeBSD_version has been bumped accordingly.
214 The legacy DRM modules and drivers have now been added to the loader's
215 module blacklist, in favor of loading them with kld_list in rc.conf(5).
216 The module blacklist may be overridden with the loader.conf(5)
217 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
221 The cam(4) based nda(4) driver will be used over nvd(4) by default on
222 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
223 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
224 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
228 Reproducible build mode is now on by default, in preparation for
229 FreeBSD 12.0. This eliminates build metadata such as the user,
230 host, and time from the kernel (and uname), unless the working tree
231 corresponds to a modified checkout from a version control system.
232 The previous behavior can be obtained by setting the /etc/src.conf
233 knob WITHOUT_REPRODUCIBLE_BUILD.
236 The Yarrow CSPRNG has been removed from the kernel as it has not been
237 supported by its designers since at least 2003. Fortuna has been the
238 default since FreeBSD-11.
241 devctl freeze/thaw have gone into the tree, the rc scripts have been
242 updated to use them and devmatch has been changed. You should update
243 kernel, userland and rc scripts all at the same time.
246 The default interpreter has been switched from 4th to Lua.
247 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
248 interpreter. If you have custom FORTH code you will need to set
249 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
250 src.conf for the build. This will create default hard links between
251 loader and loader_4th instead of loader and loader_lua, the new default.
252 If you are using UEFI it will create the proper hard link to loader.efi.
254 bhyve uses userboot.so. It remains 4th-only until some issues are solved
255 regarding coexisting with multiple versions of FreeBSD are resolved.
258 ls(1) now respects the COLORTERM environment variable used in other
259 systems and software to indicate that a colored terminal is both
260 supported and desired. If ls(1) is suddenly emitting colors, they may
261 be disabled again by either removing the unwanted COLORTERM from your
262 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
263 may not be observed in a future release.
266 The default pager for most commands has been changed to "less". To
267 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
271 The jedec_ts(4) driver has been removed. A superset of its functionality
272 is available in the jedec_dimm(4) driver, and the manpage for that
273 driver includes migration instructions. If you have "device jedec_ts"
274 in your kernel configuration file, it must be removed.
277 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
278 This should have no effect if the kernel is booted via BIOS/legacy boot.
279 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
280 has a buggy firmware that prevents a successful boot due to use of
284 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
285 support has been removed from the tree. These ports were
286 obsolete and/or known to be broken for many years.
289 loader.efi has been augmented to participate more fully in the
290 UEFI boot manager protocol. loader.efi will now look at the
291 BootXXXX environment variable to determine if a specific kernel
292 or root partition was specified. XXXX is derived from BootCurrent.
293 efibootmgr(8) manages these standard UEFI variables.
296 zfsloader's functionality has now been folded into loader.
297 zfsloader is no longer necessary once you've updated your
298 boot blocks. For a transition period, we will install a
299 hardlink for zfsloader to loader to allow a smooth transition
300 until the boot blocks can be updated (hard link because old
301 zfs boot blocks don't understand symlinks).
304 ARM64 now have efifb support, if you want to have serial console
305 on your arm64 board when an screen is connected and the bootloader
306 setup a frambuffer for us to use, just add :
310 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
311 an screen connected as the firmware will setup a framebuffer are that
312 u-boot will expose as an EFI framebuffer.
315 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
316 or take steps to update /etc/passwd before doing installworld on
317 existing systems. Do not skip the "mergemaster -Fp" step before
318 installworld, as described in the update procedures near the bottom
319 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
320 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
321 the ntp config file contain options that change file/dir locations.
322 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
323 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
324 taking steps to ensure that all required files/dirs are accessible
328 Big endian arm support has been removed.
331 The static environment setup in kernel configs is no longer mutually
332 exclusive with the loader(8) environment by default. In order to
333 restore the previous default behavior of disabling the loader(8)
334 environment if a static environment is present, you must specify
335 loader_env.disabled=1 in the static environment.
338 The ABI of syscalls used by management tools like sockstat and
339 netstat has been broken to allow 32-bit binaries to work on
340 64-bit kernels without modification. These programs will need
341 to match the kernel in order to function. External programs may
342 require minor modifications to accommodate a change of type in
343 structures from pointers to 64-bit virtual addresses.
346 On i386 and amd64 atomics are now inlined. Out of tree modules using
347 atomics will need to be rebuilt.
350 The '%I' format in the kern.corefile sysctl limits the number of
351 core files that a process can generate to the number stored in the
352 debug.ncores sysctl. The '%I' format is replaced by the single digit
353 index. Previously, if all indexes were taken the kernel would overwrite
354 only a core file with the highest index in a filename.
355 Currently the system will create a new core file if there is a free
356 index or if all slots are taken it will overwrite the oldest one.
359 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
360 6.0.1. Please see the 20141231 entry below for information about
361 prerequisites and upgrading, if you are not already using clang 3.5.0
365 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
366 needed to be changed to work with it. This change was made with r335763
367 and requires a mergemaster / etcupdate / etc to update the installed file.
370 r334930 changed the interface between the NFS modules, so they all
371 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
374 As of r334391 lld is the default amd64 system linker; it is installed
375 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
379 The kernel / userland interface for devinfo changed, so you'll
380 need a new kernel and userland as a pair for it to work (rebuilding
381 lib/libdevinfo is all that's required). devinfo and devmatch will
382 not work, but everything else will when there's a mismatch.
385 The on-disk format for hwpmc callchain records has changed to include
386 threadid corresponding to a given record. This changes the field offsets
387 and thus requires that libpmcstat be rebuilt before using a kernel
391 The vxge(4) driver has been removed. This driver was introduced into
392 HEAD one week before the Exar left the Ethernet market and is not
393 known to be used. If you have device vxge in your kernel config file
397 The amd64 kernel now requires a ld that supports ifunc to produce a
398 working kernel, either lld or a newer binutils. lld is built by default
399 on amd64, and the 'buildkernel' target uses it automatically. However,
400 it is not the default linker, so building the kernel the traditional
401 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
402 binutils port/package). lld will soon be default, and this requirement
405 NOTE: As of r334391 lld is the default system linker on amd64, and no
406 workaround is necessary.
409 The nxge(4) driver has been removed. This driver was for PCI-X 10g
410 cards made by s2io/Neterion. The company was aquired by Exar and
411 no longer sells or supports Ethernet products. If you have device
412 nxge in your kernel config file it must be removed.
415 The tz database (tzdb) has been updated to 2018e. This version more
416 correctly models time stamps in time zones with negative DST such as
417 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
418 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
419 time zone abbreviations and the tm_isdst flag.
422 The ixgb(4) driver has been removed. This driver was for an early and
423 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
424 quickly shifted to the long lived ixgbe family. If you have device
425 ixgb in your kernel config file it must be removed.
428 The lmc(4) driver has been removed. This was a WAN interface
429 card that was already reportedly rare in 2003, and had an ambiguous
430 license. If you have device lmc in your kernel config file it must
434 Support for Arcnet networks has been removed. If you have device
435 arcnet or device cm in your kernel config file they must be
439 Support for FDDI networks has been removed. If you have device
440 fddi or device fpa in your kernel config file they must be
444 In addition to supporting RFC 3164 formatted messages, the
445 syslogd(8) service is now capable of parsing RFC 5424 formatted
446 log messages. The main benefit of using RFC 5424 is that clients
447 may now send log messages with timestamps containing year numbers,
448 microseconds and time zone offsets.
450 Similarly, the syslog(3) C library function has been altered to
451 send RFC 5424 formatted messages to the local system logging
452 daemon. On systems using syslogd(8), this change should have no
453 negative impact, as long as syslogd(8) and the C library are
454 updated at the same time. On systems using a different system
455 logging daemon, it may be necessary to make configuration
456 adjustments, depending on the software used.
458 When using syslog-ng, add the 'syslog-protocol' flag to local
459 input sources to enable parsing of RFC 5424 formatted messages:
462 unix-dgram("/var/run/log" flags(syslog-protocol));
465 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
466 of the 'imuxsock' module to let messages be processed by the
467 regular RFC 3164/5424 parsing pipeline:
469 module(load="imuxsock" SysSock.UseSpecialParser="off")
471 Do note that these changes only affect communication between local
472 applications and syslogd(8). The format that syslogd(8) uses to
473 store messages on disk or forward messages to other systems
474 remains unchanged. syslogd(8) still uses RFC 3164 for these
475 purposes. Options to customize this behaviour will be added in the
476 future. Utilities that process log files stored in /var/log are
477 thus expected to continue to function as before.
479 __FreeBSD_version has been incremented to 1200061 to denote this
483 Support for token ring networks has been removed. If you
484 have "device token" in your kernel config you should remove
485 it. No device drivers supported token ring.
488 makefs was modified to be able to tag ISO9660 El Torito boot catalog
489 entries as EFI instead of overloading the i386 tag as done previously.
490 The amd64 mkisoimages.sh script used to build amd64 ISO images for
491 release was updated to use this. This may mean that makefs must be
492 updated before "make cdrom" can be run in the release directory. This
493 should be as simple as:
495 $ cd $SRCDIR/usr.sbin/makefs
496 $ make depend all install
499 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
500 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
501 Co-existance for the transition period will come shortly. Booting is a
502 complex environment and test coverage for Lua-enabled loaders has been
503 thin, so it would be prudent to assume it might not work and make
504 provisions for backup boot methods.
507 devmatch functionality has been turned on in devd. It will automatically
508 load drivers for unattached devices. This may cause unexpected drivers to
509 be loaded. Please report any problems to current@ and imp@freebsd.org.
512 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
513 6.0.0. Please see the 20141231 entry below for information about
514 prerequisites and upgrading, if you are not already using clang 3.5.0
518 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
519 This means it is used to link the kernel and userland libraries and
520 executables, but is not yet installed as /usr/bin/ld by default.
522 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
523 WITHOUT_LLD_BOOTSTRAP=yes
526 On i386, pmtimer has been removed. Its functionality has been folded
527 into apm. It was a no-op on ACPI in current for a while now (but was still
528 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
529 from kernel config files.
532 The use of RSS hash from the network card aka flowid has been
533 disabled by default for lagg(4) as it's currently incompatible with
534 the lacp and loadbalance protocols.
536 This can be re-enabled by setting the following in loader.conf:
537 net.link.lagg.default_use_flowid="1"
540 The SW_WATCHDOG option is no longer necessary to enable the
541 hardclock-based software watchdog if no hardware watchdog is
542 configured. As before, SW_WATCHDOG will cause the software
543 watchdog to be enabled even if a hardware watchdog is configured.
546 r326887 fixes the issue described in the 20171214 UPDATING entry.
547 r326888 flips the switch back to building GELI support always.
550 r362593 broke ZFS + GELI support for reasons unknown. However,
551 it also broke ZFS support generally, so GELI has been turned off
552 by default as the lesser evil in r326857. If you boot off ZFS and/or
553 GELI, it might not be a good time to update.
556 PowerPC users must update loader(8) by rebuilding world before
557 installing a new kernel, as the protocol connecting them has
558 changed. Without the update, loader metadata will not be passed
559 successfully to the kernel and users will have to enter their
560 root partition at the kernel mountroot prompt to continue booting.
561 Newer versions of loader can boot old kernels without issue.
564 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
565 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
566 to WITH/OUT_LOADER_GELI.
569 The naive and non-compliant support of posix_fallocate(2) in ZFS
570 has been removed as of r325320. The system call now returns EINVAL
571 when used on a ZFS file. Although the new behavior complies with the
572 standard, some consumers are not prepared to cope with it.
573 One known victim is lld prior to r325420.
576 Building in a FreeBSD src checkout will automatically create object
577 directories now rather than store files in the current directory if
578 'make obj' was not ran. Calling 'make obj' is no longer necessary.
579 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
580 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
584 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
585 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
586 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
587 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
588 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
589 The UNIFIED_OBJDIR option is a transitional feature that will be
590 removed for 12.0 release; please migrate to the new format for any
591 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
592 than hardcoding paths.
595 The native-xtools target no longer installs the files by default to the
596 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
597 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
600 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
601 options are changing from controlling the build if defined / undefined
602 to controlling the build with explicit 'yes' or 'no' values. They will
603 shift to WITH/WITHOUT options to match other options in the system.
606 libstand has turned into a private library for sys/boot use only.
607 It is no longer supported as a public interface outside of sys/boot.
610 The arm port has split armv6 into armv6 and armv7. armv7 is now
611 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
612 and are running a kernel from before r324363, you will need to add
613 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
616 When building multiple kernels using KERNCONF, non-existent KERNCONF
617 files will produce an error and buildkernel will fail. Previously
618 missing KERNCONF files silently failed giving no indication as to
619 why, only to subsequently discover during installkernel that the
620 desired kernel was never built in the first place.
623 The default serial number format for CTL LUNs has changed. This will
624 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
625 or iSCSI clients care about their LUNs' serial numbers. Users who
626 require serial number stability should hardcode serial numbers in
630 For 32-bit arm compiled for hard-float support, soft-floating point
631 binaries now always get their shared libraries from
632 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
633 /usr/libsoft also existed). Only users with a hard-float ld.so, but
634 soft-float everything else should be affected.
637 The geli password typed at boot is now hidden. To restore the previous
638 behavior, see geli(8) for configuration options.
641 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
642 sysctl values. Minor nit, but requires a rebuild of both world/kernel
646 "make check" behavior (made in ^/head@r295380) has been changed to
647 execute from a limited sandbox, as opposed to executing from
651 - The "beforecheck" and "aftercheck" targets are now specified.
652 - ${CHECKDIR} (added in commit noted above) has been removed.
653 - Legacy behavior can be enabled by setting
654 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
656 If the limited sandbox mode is enabled, "make check" will execute
657 "make distribution", then install, execute the tests, and clean up the
658 sandbox if successful.
660 The "make distribution" and "make install" targets are typically run as
661 root to set appropriate permissions and ownership at installation time.
662 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
663 environment if executing "make check" with limited sandbox mode using
664 an unprivileged user.
667 Since the switch to GPT disk labels, fsck for UFS/FFS has been
668 unable to automatically find alternate superblocks. As of r322297,
669 the information needed to find alternate superblocks has been
670 moved to the end of the area reserved for the boot block.
671 Filesystems created with a newfs of this vintage or later
672 will create the recovery information. If you have a filesystem
673 created prior to this change and wish to have a recovery block
674 created for your filesystem, you can do so by running fsck in
675 foreground mode (i.e., do not use the -p or -y options). As it
676 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
677 to which you should answer yes.
680 As of r321665, an NFSv4 server configuration that services
681 Kerberos mounts or clients that do not support the uid/gid in
682 owner/owner_group string capability, must explicitly enable
683 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
684 machine's /etc/rc.conf file.
687 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
688 Please see the 20141231 entry below for information about prerequisites
689 and upgrading, if you are not already using clang 3.5.0 or higher.
692 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
693 r-commands (rlogin, rsh, etc.) to be built with the base system.
696 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
697 a very major ABI incompatible change, so users of FreeBSD/powerpc must
698 be careful when performing source upgrades. It is best to run
699 'make installworld' from an alternate root system, either a live
700 CD/memory stick, or a temporary root partition. Additionally, all ports
701 must be recompiled. powerpc64 is largely unaffected, except in the case
702 of 32-bit compatibility. All 32-bit binaries will be affected.
705 Forward compatibility for the "ino64" project have been committed. This
706 will allow most new binaries to run on older kernels in a limited
707 fashion. This prevents many of the common foot-shooting actions in the
708 upgrade as well as the limited ability to roll back the kernel across
709 the ino64 upgrade. Complicated use cases may not work properly, though
710 enough simpler ones work to allow recovery in most situations.
713 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
714 if you require the GPL compiler.
717 The internal ABI used for communication between the NFS kernel modules
718 was changed by r320085, so __FreeBSD_version was bumped to
719 ensure all the NFS related modules are updated together.
722 The ABI of struct event was changed by extending the data
723 member to 64bit and adding ext fields. For upgrade, same
724 precautions as for the entry 20170523 "ino64" must be
728 The GNU roff toolchain has been removed from base. To render manpages
729 which are not supported by mandoc(1), man(1) can fallback on GNU roff
730 from ports (and recommends to install it).
731 To render roff(7) documents, consider using GNU roff from ports or the
732 heirloom doctools roff toolchain from ports via pkg install groff or
733 via pkg install heirloom-doctools.
736 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
737 smaller runtime footprint builds. This is useful for embedded systems
738 which only require one chipset support.
740 If you load it as a module, make sure this is in /boot/loader.conf:
744 This will load the HAL, all chip/RF backends and if_ath_pci.
745 If you have if_ath_pci in /boot/loader.conf, ensure it is after
746 if_ath or it will not load any HAL chipset support.
748 If you want to selectively load things (eg on ye cheape ARM/MIPS
749 platforms where RAM is at a premium) you should:
752 * load the chip modules in question
753 * load ath_rate, ath_dfs
755 * load if_ath_pci and/or if_ath_ahb depending upon your particular
756 bus bind type - this is where probe/attach is done.
758 For further comments/feedback, poke adrian@ .
761 The "ino64" 64-bit inode project has been committed, which extends
762 a number of types to 64 bits. Upgrading in place requires care and
763 adherence to the documented upgrade procedure.
765 If using a custom kernel configuration ensure that the
766 COMPAT_FREEBSD11 option is included (as during the upgrade the
767 system will be running the ino64 kernel with the existing world).
769 For the safest in-place upgrade begin by removing previous build
770 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
771 full procedure documented below under the heading "To rebuild
772 everything and install it on the current system." Specifically,
773 a reboot is required after installing the new kernel before
777 The NATM framework including the en(4), fatm(4), hatm(4), and
778 patm(4) devices has been removed. Consumers should plan a
779 migration before the end-of-life date for FreeBSD 11.
782 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
783 diff has not been implemented, if those are needed a newer version of
784 GNU diff is available via the diffutils package under the gdiff name.
787 As of r316810 for ipfilter, keep frags is no longer assumed when
788 keep state is specified in a rule. r316810 aligns ipfilter with
789 documentation in man pages separating keep frags from keep state.
790 This allows keep state to be specified without forcing keep frags
791 and allows keep frags to be specified independently of keep state.
792 To maintain previous behaviour, also specify keep frags with
793 keep state (as documented in ipf.conf.5).
796 arm64 builds now use the base system LLD 4.0.0 linker by default,
797 instead of requiring that the aarch64-binutils port or package be
798 installed. To continue using aarch64-binutils, set
799 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
802 The UDP optimization in entry 20160818 that added the sysctl
803 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
804 packets will no longer be treated as L3 broadcast packets.
807 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
808 use any explicitly assigned loopback address available in the jail
809 instead of using the first assigned address of the jail.
812 The ctl.ko module no longer implements the iSCSI target frontend:
813 cfiscsi.ko does instead.
815 If building cfiscsi.ko as a kernel module, the module can be loaded
816 via one of the following methods:
817 - `cfiscsi_load="YES"` in loader.conf(5).
818 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
819 - ctladm(8)/ctld(8), when compiled with iSCSI support
820 (`WITH_ISCSI=yes` in src.conf(5))
822 Please see cfiscsi(4) for more details.
825 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
826 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
827 same source (previously, the dependency of mmcsd.ko on mmc.ko was
828 missing, but mmcsd.ko now will refuse to load if it is incompatible
832 The syntax of ipfw(8) named states was changed to avoid ambiguity.
833 If you have used named states in the firewall rules, you need to modify
834 them after installworld and before rebooting. Now named states must
835 be prefixed with colon.
838 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
839 removed as the userland we provide cannot use them. The KMS version
840 (sys/dev/drm2) supports the same hardware.
843 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
844 Please see the 20141231 entry below for information about prerequisites
845 and upgrading, if you are not already using clang 3.5.0 or higher.
848 The code that provides support for ZFS .zfs/ directory functionality
849 has been reimplemented. It's not possible now to create a snapshot
850 by mkdir under .zfs/snapshot/. That should be the only user visible
854 EISA bus support has been removed. The WITH_EISA option is no longer
858 MCA bus support has been removed.
861 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
862 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
865 The EM_MULTIQUEUE kernel configuration option is deprecated now that
866 the em(4) driver conforms to iflib specifications.
869 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
870 IFLIB. If you have a custom kernel configuration that excludes em(4)
871 but you use igb(4), you need to re-add em(4) to your custom configuration.
874 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
875 Please see the 20141231 entry below for information about prerequisites
876 and upgrading, if you are not already using clang 3.5.0 or higher.
879 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
880 Please see the 20141231 entry below for information about prerequisites
881 and upgrading, if you are not already using clang 3.5.0 or higher.
884 The layout of the pmap structure has changed for powerpc to put the pmap
885 statistics at the front for all CPU variations. libkvm(3) and all tools
886 that link against it need to be recompiled.
889 isl(4) and cyapa(4) drivers now require a new driver,
890 chromebook_platform(4), to work properly on Chromebook-class hardware.
891 On other types of hardware the drivers may need to be configured using
892 device hints. Please see the corresponding manual pages for details.
895 The urtwn(4) driver was merged into rtwn(4) and now consists of
896 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
898 Also, firmware for RTL8188CE was renamed due to possible name
899 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
902 GNU rcs has been removed from base. It is available as packages:
903 - rcs: Latest GPLv3 GNU rcs version.
904 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
908 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
909 modules now requires that the kernel configuration contain the
910 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
913 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
914 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
917 Relocatable object files with the extension of .So have been renamed
918 to use an extension of .pico instead. The purpose of this change is
919 to avoid a name clash with shared libraries on case-insensitive file
920 systems. On those file systems, foo.So is the same file as foo.so.
923 GNU rcs has been turned off by default. It can (temporarily) be built
924 again by adding WITH_RCS knob in src.conf.
925 Otherwise, GNU rcs is available from packages:
926 - rcs: Latest GPLv3 GNU rcs version.
927 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
930 The backup_uses_rcs functionality has been removed from rc.subr.
933 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
934 two separate components, QUEUE_MACRO_DEBUG_TRACE and
935 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
936 QUEUE_MACRO_DEBUG behavior.
939 r304787 changed some ioctl interfaces between the iSCSI userspace
940 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
941 rebuilt to work with new kernels. __FreeBSD_version has been bumped
945 The UDP receive code has been updated to only treat incoming UDP
946 packets that were addressed to an L2 broadcast address as L3
947 broadcast packets. It is not expected that this will affect any
948 standards-conforming UDP application. The new behaviour can be
949 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
953 Remove the openbsd_poll system call.
954 __FreeBSD_version has been bumped because of this.
957 The stable/11 branch has been created from head@r302406.
960 The libc stub for the pipe(2) system call has been replaced with
961 a wrapper that calls the pipe2(2) system call and the pipe(2)
962 system call is now only implemented by the kernels that include
963 "options COMPAT_FREEBSD10" in their config file (this is the
964 default). Users should ensure that this option is enabled in
965 their kernel or upgrade userspace to r302092 before upgrading their
969 CAM will now strip leading spaces from SCSI disks' serial numbers.
970 This will affect users who create UFS filesystems on SCSI disks using
971 those disk's diskid device nodes. For example, if /etc/fstab
972 previously contained a line like
973 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
974 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
975 transforms like gmirror may also be affected. ZFS users should
979 The bitstring(3) API has been updated with new functionality and
980 improved performance. But it is binary-incompatible with the old API.
981 Objects built with the new headers may not be linked against objects
982 built with the old headers.
985 The brk and sbrk functions have been removed from libc on arm64.
986 Binutils from ports has been updated to not link to these
987 functions and should be updated to the latest version before
988 installing a new libc.
991 The armv6 port now defaults to hard float ABI. Limited support
992 for running both hardfloat and soft float on the same system
993 is available using the libraries installed with -DWITH_LIBSOFT.
994 This has only been tested as an upgrade path for installworld
995 and packages may fail or need manual intervention to run. New
996 packages will be needed.
998 To update an existing self-hosted armv6hf system, you must add
999 TARGET_ARCH=armv6 on the make command line for both the build
1000 and the install steps.
1003 Kernel modules compiled outside of a kernel build now default to
1004 installing to /boot/modules instead of /boot/kernel. Many kernel
1005 modules built this way (such as those in ports) already overrode
1006 KMODDIR explicitly to install into /boot/modules. However,
1007 manually building and installing a module from /sys/modules will
1008 now install to /boot/modules instead of /boot/kernel.
1011 The CAM I/O scheduler has been committed to the kernel. There should be
1012 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1013 list of known rogues that claim support for this but actually corrupt
1014 data is believed to be complete, be on the lookout for data
1015 corruption. The known rogue list is believed to be complete:
1017 o Crucial MX100, M550 drives with MU01 firmware.
1018 o Micron M510 and M550 drives with MU01 firmware.
1019 o Micron M500 prior to MU07 firmware
1020 o Samsung 830, 840, and 850 all firmwares
1021 o FCCT M500 all firmwares
1023 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1024 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1025 updated firmware. Black listed drives will work correctly because these
1026 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1027 this list is the same as found in Linux, it's believed there are no
1028 other rogues in the market place. All other models from the above
1031 To be safe, if you are at all concerned, you can quirk each of your
1032 drives to prevent NCQ from being sent by setting:
1033 kern.cam.ada.X.quirks="0x2"
1034 in loader.conf. If the drive requires the 4k sector quirk, set the
1035 quirks entry to 0x3.
1038 The FAST_DEPEND build option has been removed and its functionality is
1039 now the one true way. The old mkdep(1) style of 'make depend' has
1040 been removed. See 20160311 for further details.
1043 Resource range types have grown from unsigned long to uintmax_t. All
1044 drivers, and anything using libdevinfo, need to be recompiled.
1047 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1048 builds. It no longer runs mkdep(1) during 'make depend', and the
1049 'make depend' stage can safely be skipped now as it is auto ran
1050 when building 'make all' and will generate all SRCS and DPSRCS before
1051 building anything else. Dependencies are gathered at compile time with
1052 -MF flags kept in separate .depend files per object file. Users should
1053 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1054 stale .depend files.
1057 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1058 kernel modules. Therefore, if you load any kernel modules at boot time,
1059 please install the boot loaders after you install the kernel, but before
1063 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1064 make installkernel KERNCONF=YOUR_KERNEL_HERE
1065 make -C sys/boot install
1066 <reboot in single user>
1068 Then follow the usual steps, described in the General Notes section,
1072 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1073 see the 20141231 entry below for information about prerequisites and
1074 upgrading, if you are not already using clang 3.5.0 or higher.
1077 The AIO subsystem is now a standard part of the kernel. The
1078 VFS_AIO kernel option and aio.ko kernel module have been removed.
1079 Due to stability concerns, asynchronous I/O requests are only
1080 permitted on sockets and raw disks by default. To enable
1081 asynchronous I/O requests on all file types, set the
1082 vfs.aio.enable_unsafe sysctl to a non-zero value.
1085 The ELF object manipulation tool objcopy is now provided by the
1086 ELF Tool Chain project rather than by GNU binutils. It should be a
1087 drop-in replacement, with the addition of arm64 support. The
1088 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1089 to obtain the GNU version if necessary.
1092 Building ZFS pools on top of zvols is prohibited by default. That
1093 feature has never worked safely; it's always been prone to deadlocks.
1094 Using a zvol as the backing store for a VM guest's virtual disk will
1095 still work, even if the guest is using ZFS. Legacy behavior can be
1096 restored by setting vfs.zfs.vol.recursive=1.
1099 The NONE and HPN patches has been removed from OpenSSH. They are
1100 still available in the security/openssh-portable port.
1103 With the addition of ypldap(8), a new _ypldap user is now required
1104 during installworld. "mergemaster -p" can be used to add the user
1105 prior to installworld, as documented in the handbook.
1108 The tftp loader (pxeboot) now uses the option root-path directive. As a
1109 consequence it no longer looks for a pxeboot.4th file on the tftp
1110 server. Instead it uses the regular /boot infrastructure as with the
1114 The code to start recording plug and play data into the modules has
1115 been committed. While the old tools will properly build a new kernel,
1116 a number of warnings about "unknown metadata record 4" will be produced
1117 for an older kldxref. To avoid such warnings, make sure to rebuild
1118 the kernel toolchain (or world). Make sure that you have r292078 or
1119 later when trying to build 292077 or later before rebuilding.
1122 Debug data files are now built by default with 'make buildworld' and
1123 installed with 'make installworld'. This facilitates debugging but
1124 requires more disk space both during the build and for the installed
1125 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1129 r291527 changed the internal interface between the nfsd.ko and
1130 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1131 __FreeBSD_version has been bumped because of this.
1134 Add support for unicode collation strings leads to a change of
1135 order of files listed by ls(1) for example. To get back to the old
1136 behaviour, set LC_COLLATE environment variable to "C".
1138 Databases administrators will need to reindex their databases given
1139 collation results will be different.
1141 Due to a bug in install(1) it is recommended to remove the ancient
1142 locales before running make installworld.
1144 rm -rf /usr/share/locale/*
1147 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1148 libcrypto.so.7 or libssl.so.7 must be recompiled.
1151 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1152 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1153 should be replaced with isp_2400 and isp_2500 modules respectively.
1156 The build previously allowed using 'make -n' to not recurse into
1157 sub-directories while showing what commands would be executed, and
1158 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1159 and 'make -N' will not.
1162 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1163 and etcupdate will now use this file. A custom sendmail.cf is now
1164 updated via this mechanism rather than via installworld. If you had
1165 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1166 want to remove the exclusion or change it to "always install".
1167 /etc/mail/sendmail.cf is now managed the same way regardless of
1168 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1169 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1172 Compatibility shims for legacy ATA device names have been removed.
1173 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1174 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1175 environment variables, /dev/ad* and /dev/ar* symbolic links.
1178 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1179 Please see the 20141231 entry below for information about prerequisites
1180 and upgrading, if you are not already using clang 3.5.0 or higher.
1183 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1184 and renamed from .symbols to .debug. This reduces the size requirements
1185 on the boot partition or file system and provides consistency with
1186 userland debug files.
1188 When using the supported kernel installation method the
1189 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1190 as is done with /boot/kernel.
1192 Developers wishing to maintain the historical behavior of installing
1193 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1196 The wireless drivers had undergone changes that remove the 'parent
1197 interface' from the ifconfig -l output. The rc.d network scripts
1198 used to check presence of a parent interface in the list, so old
1199 scripts would fail to start wireless networking. Thus, etcupdate(3)
1200 or mergemaster(8) run is required after kernel update, to update your
1201 rc.d scripts in /etc.
1204 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1205 These configurations are now automatically interpreted as
1206 'scrub fragment reassemble'.
1209 Kernel-loadable modules for the random(4) device are back. To use
1210 them, the kernel must have
1213 options RANDOM_LOADABLE
1215 kldload(8) can then be used to load random_fortuna.ko
1216 or random_yarrow.ko. Please note that due to the indirect
1217 function calls that the loadable modules need to provide,
1218 the build-in variants will be slightly more efficient.
1220 The random(4) kernel option RANDOM_DUMMY has been retired due to
1221 unpopularity. It was not all that useful anyway.
1224 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1225 Control over building the ELF Tool Chain tools is now provided by
1226 the WITHOUT_TOOLCHAIN knob.
1229 The polarity of Pulse Per Second (PPS) capture events with the
1230 uart(4) driver has been corrected. Prior to this change the PPS
1231 "assert" event corresponded to the trailing edge of a positive PPS
1232 pulse and the "clear" event was the leading edge of the next pulse.
1234 As the width of a PPS pulse in a typical GPS receiver is on the
1235 order of 1 millisecond, most users will not notice any significant
1236 difference with this change.
1238 Anyone who has compensated for the historical polarity reversal by
1239 configuring a negative offset equal to the pulse width will need to
1240 remove that workaround.
1243 The default group assigned to /dev/dri entries has been changed
1244 from 'wheel' to 'video' with the id of '44'. If you want to have
1245 access to the dri devices please add yourself to the video group
1248 # pw groupmod video -m $USER
1251 The menu.rc and loader.rc files will now be replaced during
1252 upgrades. Please migrate local changes to menu.rc.local and
1253 loader.rc.local instead.
1256 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1257 strings and strip have been removed. The src.conf(5) knob
1258 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1261 As ZFS requires more kernel stack pages than is the default on some
1262 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1263 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1265 Please consider using 'options KSTACK_PAGES=X' where X is greater
1266 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1269 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1270 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1271 default, i.e., they will not contain "::". For example, instead
1272 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1273 to have a more specific match, such as different map entries for
1274 IPv6:0:0 vs IPv6:0. This change requires that configuration
1275 data (including maps, files, classes, custom ruleset, etc.) must
1276 use the same format, so make certain such configuration data is
1277 upgrading. As a very simple check search for patterns like
1278 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1279 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1280 the cf option UseCompressedIPv6Addresses.
1283 The default kernel entropy-processing algorithm is now
1284 Fortuna, replacing Yarrow.
1286 Assuming you have 'device random' in your kernel config
1287 file, the configurations allow a kernel option to override
1288 this default. You may choose *ONE* of:
1290 options RANDOM_YARROW # Legacy /dev/random algorithm.
1291 options RANDOM_DUMMY # Blocking-only driver.
1293 If you have neither, you get Fortuna. For most people,
1294 read no further, Fortuna will give a /dev/random that works
1295 like it always used to, and the difference will be irrelevant.
1297 If you remove 'device random', you get *NO* kernel-processed
1298 entropy at all. This may be acceptable to folks building
1299 embedded systems, but has complications. Carry on reading,
1300 and it is assumed you know what you need.
1302 *PLEASE* read random(4) and random(9) if you are in the
1303 habit of tweaking kernel configs, and/or if you are a member
1304 of the embedded community, wanting specific and not-usual
1305 behaviour from your security subsystems.
1307 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1308 random', you will NOT have a functioning /dev/random, and
1309 many cryptographic features will not work, including SSH.
1310 You may also find strange behaviour from the random(3) set
1311 of library functions, in particular sranddev(3), srandomdev(3)
1312 and arc4random(3). The reason for this is that the KERN_ARND
1313 sysctl only returns entropy if it thinks it has some to
1314 share, and with RANDOM_DUMMY or no 'device random' this
1318 An additional fix for the issue described in the 20150614 sendmail
1319 entry below has been committed in revision 284717.
1322 FreeBSD's old make (fmake) has been removed from the system. It is
1323 available as the devel/fmake port or via pkg install fmake.
1326 The fix for the issue described in the 20150614 sendmail entry
1327 below has been committed in revision 284436. The work
1328 around described in that entry is no longer needed unless the
1329 default setting is overridden by a confDH_PARAMETERS configuration
1330 setting of '5' or pointing to a 512 bit DH parameter file.
1333 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1334 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1335 and devel/kyua to version 0.20+ and adjust any calling code to work
1336 with Kyuafile and kyua.
1339 The import of openssl to address the FreeBSD-SA-15:10.openssl
1340 security advisory includes a change which rejects handshakes
1341 with DH parameters below 768 bits. sendmail releases prior
1342 to 8.15.2 (not yet released), defaulted to a 512 bit
1343 DH parameter setting for client connections. To work around
1344 this interoperability, sendmail can be configured to use a
1345 2048 bit DH parameter by:
1347 1. Edit /etc/mail/`hostname`.mc
1348 2. If a setting for confDH_PARAMETERS does not exist or
1349 exists and is set to a string beginning with '5',
1350 replace it with '2'.
1351 3. If a setting for confDH_PARAMETERS exists and is set to
1352 a file path, create a new file with:
1353 openssl dhparam -out /path/to/file 2048
1354 4. Rebuild the .cf file:
1355 cd /etc/mail/; make; make install
1356 5. Restart sendmail:
1357 cd /etc/mail/; make restart
1359 A sendmail patch is coming, at which time this file will be
1363 Generation of legacy formatted entries have been disabled by default
1364 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1365 entries were converted to use the new format by default when the new,
1366 machine independent format have been added and supported since FreeBSD
1369 Please see the pwd_mkdb(8) manual page for further details.
1372 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1373 20141231 entry below for information about prerequisites and upgrading,
1374 if you are not already using 3.5.0 or higher.
1377 TI platform code switched to using vendor DTS files and this update
1378 may break existing systems running on Beaglebone, Beaglebone Black,
1381 - dtb files should be regenerated/reinstalled. Filenames are the
1382 same but content is different now
1383 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1384 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1385 addressing scheme is now pin 25 on /dev/gpioc3.
1386 - Pandaboard: /etc/ttys should be updated, serial console device is
1387 now /dev/ttyu2, not /dev/ttyu0
1390 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1391 If you need the GNU extension from groff soelim(1), install groff
1392 from package: pkg install groff, or via ports: textproc/groff.
1395 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1396 defined in symlink(7); previously symlinks were silently ignored.
1399 The const qualifier has been removed from iconv(3) to comply with
1400 POSIX. The ports tree is aware of this from r384038 onwards.
1403 Libraries specified by LIBADD in Makefiles must have a corresponding
1404 DPADD_<lib> variable to ensure correct dependencies. This is now
1405 enforced in src.libnames.mk.
1408 From legacy ata(4) driver was removed support for SATA controllers
1409 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1410 Kernel modules ataahci and ataadaptec were removed completely,
1411 replaced by ahci and mvs modules respectively.
1414 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1415 the 20141231 entry below for information about prerequisites and
1416 upgrading, if you are not already using 3.5.0 or higher.
1419 The 32-bit PowerPC kernel has been changed to a position-independent
1420 executable. This can only be booted with a version of loader(8)
1421 newer than January 31, 2015, so make sure to update both world and
1422 kernel before rebooting.
1425 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1426 but before r278950, the RNG was not seeded properly. Immediately
1427 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1428 ssh keys or openssl keys) that were generated w/ a kernel from that
1429 range. This does not affect programs that directly used /dev/random
1430 or /dev/urandom. All userland uses of arc4random(3) are affected.
1433 The autofs(4) ABI was changed in order to restore binary compatibility
1434 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1435 with the new kernel.
1438 The powerpc64 kernel has been changed to a position-independent
1439 executable. This can only be booted with a new version of loader(8),
1440 so make sure to update both world and kernel before rebooting.
1443 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1444 only release, no new features have been added. Please see the 20141231
1445 entry below for information about prerequisites and upgrading, if you
1446 are not already using 3.5.0.
1449 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1450 taken from the ELF Tool Chain project rather than GNU binutils. They
1451 should be drop-in replacements, with the addition of arm64 support.
1452 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1453 binutils tools, if necessary. See 20150805 for updated information.
1456 The default Unbound configuration now enables remote control
1457 using a local socket. Users who have already enabled the
1458 local_unbound service should regenerate their configuration
1459 by running "service local_unbound setup" as root.
1462 The GNU texinfo and GNU info pages have been removed.
1463 To be able to view GNU info pages please install texinfo from ports.
1466 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1468 As of this release, a prerequisite for building clang, llvm and lldb is
1469 a C++11 capable compiler and C++11 standard library. This means that to
1470 be able to successfully build the cross-tools stage of buildworld, with
1471 clang as the bootstrap compiler, your system compiler or cross compiler
1472 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1473 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1476 On any standard FreeBSD 10.x or 11.x installation, where clang and
1477 libc++ are on by default (that is, on x86 or arm), this should work out
1480 On 9.x installations where clang is enabled by default, e.g. on x86 and
1481 powerpc, libc++ will not be enabled by default, so libc++ should be
1482 built (with clang) and installed first. If both clang and libc++ are
1483 missing, build clang first, then use it to build libc++.
1485 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1486 the instructions for 9.x above.
1488 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1489 default, and do not build clang.
1491 Many embedded systems are resource constrained, and will not be able to
1492 build clang in a reasonable time, or in some cases at all. In those
1493 cases, cross building bootable systems on amd64 is a workaround.
1495 This new version of clang introduces a number of new warnings, of which
1496 the following are most likely to appear:
1500 This warns in two cases, for both C and C++:
1501 * When the code is trying to take the absolute value of an unsigned
1502 quantity, which is effectively a no-op, and almost never what was
1503 intended. The code should be fixed, if at all possible. If you are
1504 sure that the unsigned quantity can be safely cast to signed, without
1505 loss of information or undefined behavior, you can add an explicit
1506 cast, or disable the warning.
1508 * When the code is trying to take an absolute value, but the called
1509 abs() variant is for the wrong type, which can lead to truncation.
1510 If you want to disable the warning instead of fixing the code, please
1511 make sure that truncation will not occur, or it might lead to unwanted
1514 -Wtautological-undefined-compare and
1515 -Wundefined-bool-conversion
1517 These warn when C++ code is trying to compare 'this' against NULL, while
1518 'this' should never be NULL in well-defined C++ code. However, there is
1519 some legacy (pre C++11) code out there, which actively abuses this
1520 feature, which was less strictly defined in previous C++ versions.
1522 Squid and openjdk do this, for example. The warning can be turned off
1523 for C++98 and earlier, but compiling the code in C++11 mode might result
1524 in unexpected behavior; for example, the parts of the program that are
1525 unreachable could be optimized away.
1528 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1529 kernel sources have been removed. The .h files remain, since some
1530 utilities include them. This will need to be fixed later.
1531 If "mount -t oldnfs ..." is attempted, it will fail.
1532 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1533 the utilities will report errors.
1536 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1537 directories to top level SUBDIR variable when their parent
1538 directory is included in LOCAL_DIRS. Users with build systems with
1539 such hierarchies and without SUBDIR entries in the parent
1540 directory Makefiles should add them or add the directories to
1544 faith(4) and faithd(8) have been removed from the base system. Faith
1545 has been obsolete for a very long time.
1548 vt(4), the new console driver, is enabled by default. It brings
1549 support for Unicode and double-width characters, as well as
1550 support for UEFI and integration with the KMS kernel video
1553 You may need to update your console settings in /etc/rc.conf,
1554 most probably the keymap. During boot, /etc/rc.d/syscons will
1555 indicate what you need to do.
1557 vt(4) still has issues and lacks some features compared to
1558 syscons(4). See the wiki for up-to-date information:
1559 https://wiki.freebsd.org/Newcons
1561 If you want to keep using syscons(4), you can do so by adding
1562 the following line to /boot/loader.conf:
1566 pjdfstest has been integrated into kyua as an opt-in test suite.
1567 Please see share/doc/pjdfstest/README for more details on how to
1571 gperf has been removed from the base system for architectures
1572 that use clang. Ports that require gperf will obtain it from the
1576 pjdfstest has been moved from tools/regression/pjdfstest to
1580 At svn r271982, The default linux compat kernel ABI has been adjusted
1581 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1582 update. If you wish to continue using the linux-f10 compat ports,
1583 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1584 encouraged to update their linux-compat packages to linux-c6 during
1585 their next update cycle.
1588 The ofwfb driver, used to provide a graphics console on PowerPC when
1589 using vt(4), no longer allows mmap() of all physical memory. This
1590 will prevent Xorg on PowerPC with some ATI graphics cards from
1591 initializing properly unless x11-servers/xorg-server is updated to
1595 The xdev targets have been converted to using TARGET and
1596 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1599 The default unbound configuration has been modified to address
1600 issues with reverse lookups on networks that use private
1601 address ranges. If you use the local_unbound service, run
1602 "service local_unbound setup" as root to regenerate your
1603 configuration, then "service local_unbound reload" to load the
1607 The GNU texinfo and GNU info pages are not built and installed
1608 anymore, WITH_INFO knob has been added to allow to built and install
1610 UPDATE: see 20150102 entry on texinfo's removal
1613 The GNU readline library is now an INTERNALLIB - that is, it is
1614 statically linked into consumers (GDB and variants) in the base
1615 system, and the shared library is no longer installed. The
1616 devel/readline port is available for third party software that
1620 The Itanium architecture (ia64) has been removed from the list of
1621 known architectures. This is the first step in the removal of the
1625 Commit r268115 has added NFSv4.1 server support, merged from
1626 projects/nfsv4.1-server. Since this includes changes to the
1627 internal interfaces between the NFS related modules, a full
1628 build of the kernel and modules will be necessary.
1629 __FreeBSD_version has been bumped.
1632 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1633 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1634 which differs from the behaviour controlled by this knob.)
1637 Maximal length of the serial number in CTL was increased from 16 to
1638 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1639 and ctld, need to be rebuilt to work with a new kernel.
1642 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1643 1 respectively to match the upstream numbers. They were out of
1644 sync because, when they were originally added to FreeBSD, the
1645 upstream versions were not respected. These libraries are private
1646 and not yet built by default, so renumbering them should be a
1647 non-issue. However, unclean source trees will yield broken test
1648 programs once the operator executes "make delete-old-libs" after a
1649 "make installworld".
1651 Additionally, the atf-sh binary was made private by moving it into
1652 /usr/libexec/. Already-built shell test programs will keep the
1653 path to the old binary so they will break after "make delete-old"
1656 If you are using WITH_TESTS=yes (not the default), wipe the object
1657 tree and rebuild from scratch to prevent spurious test failures.
1658 This is only needed once: the misnumbered libraries and misplaced
1659 binaries have been added to OptionalObsoleteFiles.inc so they will
1660 be removed during a clean upgrade.
1663 Clang and llvm have been upgraded to 3.4.1 release.
1666 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1667 be removed to avoid issues in the future (and has been added to
1671 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1672 past, it affected all builds that used the bsd.*.mk files. The old
1673 behavior was a bug, but people may have relied upon it. To get this
1674 behavior back, you can .include /etc/src.conf from /etc/make.conf
1675 (which is still global and isn't changed). This also changes the
1676 behavior of incremental builds inside the tree of individual
1677 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1678 Although this has survived make universe and some upgrade scenarios,
1679 other upgrade scenarios may have broken. At least one form of
1680 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1681 as well... In cases where MAKESYSPATH isn't working with this
1682 setting, you'll need to set it to the full path to your tree.
1684 One side effect of all this cleaning up is that bsd.compiler.mk
1685 is no longer implicitly included by bsd.own.mk. If you wish to
1686 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1690 The lindev device has been removed since /dev/full has been made a
1691 standard device. __FreeBSD_version has been bumped.
1694 The knob WITHOUT_VI was added to the base system, which controls
1695 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1696 in order to reorder files share/termcap and didn't build ex(1) as a
1697 build tool, so building/installing with WITH_VI is highly advised for
1698 build hosts for older releases.
1700 This issue has been fixed in stable/9 and stable/10 in r277022 and
1701 r276991, respectively.
1704 The YES_HESIOD knob has been removed. It has been obsolete for
1705 a decade. Please move to using WITH_HESIOD instead or your builds
1706 will silently lack HESIOD.
1709 The uart(4) driver has been changed with respect to its handling
1710 of the low-level console. Previously the uart(4) driver prevented
1711 any process from changing the baudrate or the CLOCAL and HUPCL
1712 control flags. By removing the restrictions, operators can make
1713 changes to the serial console port without having to reboot.
1714 However, when getty(8) is started on the serial device that is
1715 associated with the low-level console, a misconfigured terminal
1716 line in /etc/ttys will now have a real impact.
1717 Before upgrading the kernel, make sure that /etc/ttys has the
1718 serial console device configured as 3wire without baudrate to
1719 preserve the previous behaviour. E.g:
1720 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1723 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1724 to improve performance. To re-enable it, if needed, run rpcbind
1725 with command line option -W.
1728 Switched back to the GPL dtc compiler due to updates in the upstream
1729 dts files not being supported by the BSDL dtc compiler. You will need
1730 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1731 may result while building dtb files during a kernel build if you fail
1732 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1735 Clang and llvm have been upgraded to 3.4 release.
1738 The nve(4) driver has been removed. Please use the nfe(4) driver
1739 for NVIDIA nForce MCP Ethernet adapters instead.
1742 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1743 This could cause certain C++ applications using shared libraries built
1744 against the previous version of libc++ to crash. The incompatibility
1745 has now been fixed, but any C++ applications or shared libraries built
1746 between r261283 and r261801 should be recompiled.
1749 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1750 capability mode support. Please note that enabling the feature in
1751 kernel is still highly recommended.
1754 OpenSSH is now built with sandbox support, and will use sandbox as
1755 the default privilege separation method. This requires Capsicum
1756 capability mode support in kernel.
1759 The libelf and libdwarf libraries have been updated to newer
1760 versions from upstream. Shared library version numbers for
1761 these two libraries were bumped. Any ports or binaries
1762 requiring these two libraries should be recompiled.
1763 __FreeBSD_version is bumped to 1100006.
1766 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1767 instead of providing an explicit one, this would prevent such
1768 Makefile from providing its own Kyuafile in the future during
1769 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1770 intervention is needed to clean an objdir if you use NO_CLEAN:
1771 # find /usr/obj -name Kyuafile | xargs rm -f
1774 The behavior of gss_pseudo_random() for the krb5 mechanism
1775 has changed, for applications requesting a longer random string
1776 than produced by the underlying enctype's pseudo-random() function.
1777 In particular, the random string produced from a session key of
1778 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1779 be different at the 17th octet and later, after this change.
1780 The counter used in the PRF+ construction is now encoded as a
1781 big-endian integer in accordance with RFC 4402.
1782 __FreeBSD_version is bumped to 1100004.
1785 The WITHOUT_ATF build knob has been removed and its functionality
1786 has been subsumed into the more generic WITHOUT_TESTS. If you were
1787 using the former to disable the build of the ATF libraries, you
1788 should change your settings to use the latter.
1791 The default version of mtree is nmtree which is obtained from
1792 NetBSD. The output is generally the same, but may vary
1793 slightly. If you found you need identical output adding
1794 "-F freebsd9" to the command line should do the trick. For the
1795 time being, the old mtree is available as fmtree.
1798 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1799 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1800 1.1.4_8 and verify bsdyml not linked in, before running "make
1802 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1804 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1807 The stable/10 branch has been created in subversion from head
1814 Avoid using make -j when upgrading. While generally safe, there are
1815 sometimes problems using -j to upgrade. If your upgrade fails with
1816 -j, please try again without -j. From time to time in the past there
1817 have been problems using -j with buildworld and/or installworld. This
1818 is especially true when upgrading between "distant" versions (eg one
1819 that cross a major release boundary or several minor releases, or when
1820 several months have passed on the -current branch).
1822 Sometimes, obscure build problems are the result of environment
1823 poisoning. This can happen because the make utility reads its
1824 environment when searching for values for global variables. To run
1825 your build attempts in an "environmental clean room", prefix all make
1826 commands with 'env -i '. See the env(1) manual page for more details.
1828 When upgrading from one major version to another it is generally best to
1829 upgrade to the latest code in the currently installed branch first, then
1830 do an upgrade to the new branch. This is the best-tested upgrade path,
1831 and has the highest probability of being successful. Please try this
1832 approach if you encounter problems with a major version upgrade. Since
1833 the stable 4.x branch point, one has generally been able to upgrade from
1834 anywhere in the most recent stable branch to head / current (or even the
1835 last couple of stable branches). See the top of this file when there's
1838 When upgrading a live system, having a root shell around before
1839 installing anything can help undo problems. Not having a root shell
1840 around can lead to problems if pam has changed too much from your
1841 starting point to allow continued authentication after the upgrade.
1843 This file should be read as a log of events. When a later event changes
1844 information of a prior event, the prior event should not be deleted.
1845 Instead, a pointer to the entry with the new information should be
1846 placed in the old entry. Readers of this file should also sanity check
1847 older entries before relying on them blindly. Authors of new entries
1848 should write them with this in mind.
1852 When upgrading the boot ZFS pool to a new version, always follow
1855 1.) recompile and reinstall the ZFS boot loader and boot block
1856 (this is part of "make buildworld" and "make installworld")
1858 2.) update the ZFS boot block on your boot drive
1860 The following example updates the ZFS boot block on the first
1861 partition (freebsd-boot) of a GPT partitioned drive ada0:
1862 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1864 Non-boot pools do not need these updates.
1868 If you are updating from a prior version of FreeBSD (even one just
1869 a few days old), you should follow this procedure. It is the most
1870 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1872 make kernel-toolchain
1873 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1874 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1876 To test a kernel once
1877 ---------------------
1878 If you just want to boot a kernel once (because you are not sure
1879 if it works, or if you want to boot a known bad kernel to provide
1880 debugging information) run
1881 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1882 nextboot -k testkernel
1884 To rebuild everything and install it on the current system.
1885 -----------------------------------------------------------
1886 # Note: sometimes if you are running current you gotta do more than
1887 # is listed here if you are upgrading from a really old current.
1889 <make sure you have good level 0 dumps>
1891 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1892 make installkernel KERNCONF=YOUR_KERNEL_HERE
1894 <reboot in single user> [3]
1901 To cross-install current onto a separate partition
1902 --------------------------------------------------
1903 # In this approach we use a separate partition to hold
1904 # current's root, 'usr', and 'var' directories. A partition
1905 # holding "/", "/usr" and "/var" should be about 2GB in
1908 <make sure you have good level 0 dumps>
1911 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1912 <maybe newfs current's root partition>
1913 <mount current's root partition on directory ${CURRENT_ROOT}>
1914 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1915 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1916 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1917 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1918 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1919 <reboot into current>
1920 <do a "native" rebuild/install as described in the previous section>
1921 <maybe install compatibility libraries from ports/misc/compat*>
1925 To upgrade in-place from stable to current
1926 ----------------------------------------------
1927 <make sure you have good level 0 dumps>
1929 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1930 make installkernel KERNCONF=YOUR_KERNEL_HERE
1932 <reboot in single user> [3]
1939 Make sure that you've read the UPDATING file to understand the
1940 tweaks to various things you need. At this point in the life
1941 cycle of current, things change often and you are on your own
1942 to cope. The defaults can also change, so please read ALL of
1943 the UPDATING entries.
1945 Also, if you are tracking -current, you must be subscribed to
1946 freebsd-current@freebsd.org. Make sure that before you update
1947 your sources that you have read and understood all the recent
1948 messages there. If in doubt, please track -stable which has
1949 much fewer pitfalls.
1951 [1] If you have third party modules, such as vmware, you
1952 should disable them at this point so they don't crash your
1955 [3] From the bootblocks, boot -s, and then do
1960 adjkerntz -i # if CMOS is wall time
1961 Also, when doing a major release upgrade, it is required that
1962 you boot into single user mode to do the installworld.
1964 [4] Note: This step is non-optional. Failure to do this step
1965 can result in a significant reduction in the functionality of the
1966 system. Attempting to do it by hand is not recommended and those
1967 that pursue this avenue should read this file carefully, as well
1968 as the archives of freebsd-current and freebsd-hackers mailing lists
1969 for potential gotchas. The -U option is also useful to consider.
1970 See mergemaster(8) for more information.
1972 [5] Usually this step is a no-op. However, from time to time
1973 you may need to do this if you get unknown user in the following
1974 step. It never hurts to do it all the time. You may need to
1975 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1976 install) after the buildworld before this step if you last updated
1977 from current before 20130425 or from -stable before 20130430.
1979 [6] This only deletes old files and directories. Old libraries
1980 can be deleted by "make delete-old-libs", but you have to make
1981 sure that no program is using those libraries anymore.
1983 [8] In order to have a kernel that can run the 4.x binaries needed to
1984 do an installworld, you must include the COMPAT_FREEBSD4 option in
1985 your kernel. Failure to do so may leave you with a system that is
1986 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1987 required to run the 5.x binaries on more recent kernels. And so on
1988 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1990 Make sure that you merge any new devices from GENERIC since the
1991 last time you updated your kernel config file.
1993 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1994 "?=" instead of the "=" assignment operator, so that buildworld can
1995 override the CPUTYPE if it needs to.
1997 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1998 not on the command line, or in /etc/make.conf. buildworld will
1999 warn if it is improperly defined.
2002 This file contains a list, in reverse chronological order, of major
2003 breakages in tracking -current. It is not guaranteed to be a complete
2004 list of such breakages, and only contains entries since September 23, 2011.
2005 If you need to see UPDATING entries from before that date, you will need
2006 to fetch an UPDATING file from an older FreeBSD release.
2008 Copyright information:
2010 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2012 Redistribution, publication, translation and use, with or without
2013 modification, in full or in part, in any form or format of this
2014 document are permitted without further permission from the author.
2016 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2017 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2018 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2019 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2020 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2021 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2022 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2023 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2024 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2025 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2026 POSSIBILITY OF SUCH DAMAGE.
2028 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob