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