1 Updating Information for FreeBSD stable/12 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.
20 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
21 been upgraded to 10.0.1. Please see the 20141231 entry below for
22 information about prerequisites and upgrading, if you are not already
23 using clang 3.5.0 or higher.
26 read(2) of a directory fd is now rejected by default. root may
27 re-enable it for the entire system with the
28 security.bsd.allow_read_dir sysctl(8) MIB.
30 It may be advised to setup aliases for grep to default to `-d skip` if
31 commonly non-recursively grepping a list that includes directories and
32 the potential for the resulting stderr output is not tolerable. Example
33 aliases are now installed, commented out, in /root/.cshrc.
36 Upstream DTS from Linux 5.6 was merged and they now have the SID
37 and THS (Secure ID controller and THermal Sensor) node present.
38 The DTB overlays have now been removed from the tree for the H3/H5 and
39 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
40 deal with upstream DTS. If you are using those overlays you need to
41 remove them from loader.conf and update the DTBs on the FAT partition.
44 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
45 been upgraded to 10.0.0. Please see the 20141231 entry below for
46 information about prerequisites and upgrading, if you are not already
47 using clang 3.5.0 or higher.
50 The root certificates of the Mozilla CA Certificate Store have been
51 imported into the base system and can be managed with the certctl(8)
52 utility. If you have installed the security/ca_root_nss port or package
53 with the ETCSYMLINK option (the default), be advised that there may be
54 differences between those included in the port and those included in
55 base due to differences in nss branch used as well as general update
56 frequency. Note also that certctl(8) cannot manage certs in the
57 format used by the security/ca_root_nss port.
60 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
61 been upgraded to 9.0.1. Please see the 20141231 entry below for
62 information about prerequisites and upgrading, if you are not already
63 using clang 3.5.0 or higher.
66 The nctgpio and wbwd drivers have been moved to the superio bus.
67 If you have one of these drivers in a kernel configuration, then
68 you should add device superio to it. If you use one of these drivers
69 as a module and you compile a custom set of modules, then you should
70 add superio to the set.
73 The tap(4) driver has been folded into tun(4), and the module has been
74 renamed to tuntap. You should update any kld_list="if_tap" or
75 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
76 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
77 module instead, and "device tap" or "device tun" entries in kernel
78 config files to select the tuntap device instead.
81 ntpd no longer by default locks its pages in memory, allowing them
82 to be paged out by the kernel. Use rlimit memlock to restore
83 historic BSD behaviour. For example, add "rlimit memlock 32"
84 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
87 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
88 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
89 been removed from mount_fusefs(8). You can safely remove them from
90 your scripts, because they had no effect.
92 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
93 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
94 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
95 sysctls have been removed. If you felt the need to set any of them to
96 a non-default value, please tell asomers@FreeBSD.org why.
99 The fuse(4) module has been renamed to fusefs(4) for consistency with
100 other filesystems. You should update any kld_load="fuse" entries in
101 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
102 "options FUSE" enties in kernel config files.
105 Default permissions on the /var/account/acct file (and copies of it
106 rotated by periodic daily scripts) are changed from 0644 to 0640
107 because the file contains sensitive information that should not be
108 world-readable. If the /var/account directory must be created by
109 rc.d/accounting, the mode used is now 0750. Admins who use the
110 accounting feature are encouraged to change the mode of an existing
111 /var/account directory to 0750 or 0700.
114 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
115 been upgraded to 8.0.1. Please see the 20141231 entry below for
116 information about prerequisites and upgrading, if you are not already
117 using clang 3.5.0 or higher.
120 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc
121 functionality needed for the RETPOLINE option should work properly
122 again. The RETPOLINE option has been removed from BROKEN_OPTIONS.
125 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
126 8.0.0. Please see the 20141231 entry below for information about
127 prerequisites and upgrading, if you are not already using clang 3.5.0
131 The RETPOLINE option produces non-functional ifunc-using binaries
132 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
133 Once Clang 8 is merged it may be enabled again.
136 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
137 7.0.1. Please see the 20141231 entry below for information about
138 prerequisites and upgrading, if you are not already using clang 3.5.0
142 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
143 compiled into your custom kernel, add 'device xz' statement to the
147 Iflib is no longer unconditionally compiled into the kernel. Drivers
148 using iflib and statically compiled into the kernel, now require
149 the 'device iflib' config option. For the same drivers loaded as
150 modules on kernels not having 'device iflib', the iflib.ko module
151 is loaded automatically.
154 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
155 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
156 servers that have vfs.nfsd.nfs_privport set will only allow mounts
157 from clients using a reserved port#. Since both the FreeBSD and Linux
158 NFSv4 clients use reserved port#s by default, this should not affect
162 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
163 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
164 it produces broken binaries when ifuncs are in use. Users needing
165 GNU ld should install the binutils port or package.
168 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
169 has been converted to a port (misc/ctm) and will be removed from
170 FreeBSD-13. A depreciation warning will be printed to stderr by
171 the ctm command, but the functionality will remain in base for all
175 The stable/12 branch has been created in subversion from head
179 Ports for the DRM modules have been simplified. Now, amd64 users should
180 just install the drm-kmod port. All others should install
183 Graphics hardware that's newer than about 2010 usually works with
184 drm-kmod. For hardware older than 2013, however, some users will need
185 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
186 than 2008 usually only works in drm-legacy-kmod. The graphics team can
187 only commit to hardware made since 2013 due to the complexity of the
188 market and difficulty to test all the older cards effectively. If you
189 have hardware supported by drm-kmod, you are strongly encouraged to use
190 that as you will get better support.
192 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
193 elsewhere, the drm and drm2 modules will be eliminated from the src base
194 soon (with a limited exception for arm). Please update to the package asap
195 and report any issues to x11@freebsd.org.
197 Generally, anybody using the drm*-kmod packages should add
198 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
199 cross-threading surprises, especially with automatic driver
200 loading from X11 startup. These will become the defaults in 13-current
204 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
205 custom kernel and module loading configuration files must be updated
206 accordingly. Moreover, interfaces previous presented as ixlvN to the
207 system are now exposed as iavfN and network configuration files must
208 be adjusted as necessary.
211 OpenSSL has been updated to version 1.1.1. This update included
212 additional various API changes througout the base system. It is
213 important to rebuild third-party software after upgrading. The value
214 of __FreeBSD_version has been bumped accordingly.
217 The legacy DRM modules and drivers have now been added to the loader's
218 module blacklist, in favor of loading them with kld_list in rc.conf(5).
219 The module blacklist may be overridden with the loader.conf(5)
220 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
224 The cam(4) based nda(4) driver will be used over nvd(4) by default on
225 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
226 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
227 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
231 Reproducible build mode is now on by default, in preparation for
232 FreeBSD 12.0. This eliminates build metadata such as the user,
233 host, and time from the kernel (and uname), unless the working tree
234 corresponds to a modified checkout from a version control system.
235 The previous behavior can be obtained by setting the /etc/src.conf
236 knob WITHOUT_REPRODUCIBLE_BUILD.
239 The Yarrow CSPRNG has been removed from the kernel as it has not been
240 supported by its designers since at least 2003. Fortuna has been the
241 default since FreeBSD-11.
244 devctl freeze/thaw have gone into the tree, the rc scripts have been
245 updated to use them and devmatch has been changed. You should update
246 kernel, userland and rc scripts all at the same time.
249 The default interpreter has been switched from 4th to Lua.
250 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
251 interpreter. If you have custom FORTH code you will need to set
252 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
253 src.conf for the build. This will create default hard links between
254 loader and loader_4th instead of loader and loader_lua, the new default.
255 If you are using UEFI it will create the proper hard link to loader.efi.
257 bhyve uses userboot.so. It remains 4th-only until some issues are solved
258 regarding coexisting with multiple versions of FreeBSD are resolved.
261 ls(1) now respects the COLORTERM environment variable used in other
262 systems and software to indicate that a colored terminal is both
263 supported and desired. If ls(1) is suddenly emitting colors, they may
264 be disabled again by either removing the unwanted COLORTERM from your
265 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
266 may not be observed in a future release.
269 The default pager for most commands has been changed to "less". To
270 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
274 The jedec_ts(4) driver has been removed. A superset of its functionality
275 is available in the jedec_dimm(4) driver, and the manpage for that
276 driver includes migration instructions. If you have "device jedec_ts"
277 in your kernel configuration file, it must be removed.
280 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
281 This should have no effect if the kernel is booted via BIOS/legacy boot.
282 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
283 has a buggy firmware that prevents a successful boot due to use of
287 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
288 support has been removed from the tree. These ports were
289 obsolete and/or known to be broken for many years.
292 loader.efi has been augmented to participate more fully in the
293 UEFI boot manager protocol. loader.efi will now look at the
294 BootXXXX environment variable to determine if a specific kernel
295 or root partition was specified. XXXX is derived from BootCurrent.
296 efibootmgr(8) manages these standard UEFI variables.
299 zfsloader's functionality has now been folded into loader.
300 zfsloader is no longer necessary once you've updated your
301 boot blocks. For a transition period, we will install a
302 hardlink for zfsloader to loader to allow a smooth transition
303 until the boot blocks can be updated (hard link because old
304 zfs boot blocks don't understand symlinks).
307 ARM64 now have efifb support, if you want to have serial console
308 on your arm64 board when an screen is connected and the bootloader
309 setup a frambuffer for us to use, just add :
313 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
314 an screen connected as the firmware will setup a framebuffer are that
315 u-boot will expose as an EFI framebuffer.
318 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
319 or take steps to update /etc/passwd before doing installworld on
320 existing systems. Do not skip the "mergemaster -Fp" step before
321 installworld, as described in the update procedures near the bottom
322 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
323 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
324 the ntp config file contain options that change file/dir locations.
325 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
326 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
327 taking steps to ensure that all required files/dirs are accessible
331 Big endian arm support has been removed.
334 The static environment setup in kernel configs is no longer mutually
335 exclusive with the loader(8) environment by default. In order to
336 restore the previous default behavior of disabling the loader(8)
337 environment if a static environment is present, you must specify
338 loader_env.disabled=1 in the static environment.
341 The ABI of syscalls used by management tools like sockstat and
342 netstat has been broken to allow 32-bit binaries to work on
343 64-bit kernels without modification. These programs will need
344 to match the kernel in order to function. External programs may
345 require minor modifications to accommodate a change of type in
346 structures from pointers to 64-bit virtual addresses.
349 On i386 and amd64 atomics are now inlined. Out of tree modules using
350 atomics will need to be rebuilt.
353 The '%I' format in the kern.corefile sysctl limits the number of
354 core files that a process can generate to the number stored in the
355 debug.ncores sysctl. The '%I' format is replaced by the single digit
356 index. Previously, if all indexes were taken the kernel would overwrite
357 only a core file with the highest index in a filename.
358 Currently the system will create a new core file if there is a free
359 index or if all slots are taken it will overwrite the oldest one.
362 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
363 6.0.1. Please see the 20141231 entry below for information about
364 prerequisites and upgrading, if you are not already using clang 3.5.0
368 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
369 needed to be changed to work with it. This change was made with r335763
370 and requires a mergemaster / etcupdate / etc to update the installed file.
373 r334930 changed the interface between the NFS modules, so they all
374 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
377 As of r334391 lld is the default amd64 system linker; it is installed
378 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
382 The kernel / userland interface for devinfo changed, so you'll
383 need a new kernel and userland as a pair for it to work (rebuilding
384 lib/libdevinfo is all that's required). devinfo and devmatch will
385 not work, but everything else will when there's a mismatch.
388 The on-disk format for hwpmc callchain records has changed to include
389 threadid corresponding to a given record. This changes the field offsets
390 and thus requires that libpmcstat be rebuilt before using a kernel
394 The vxge(4) driver has been removed. This driver was introduced into
395 HEAD one week before the Exar left the Ethernet market and is not
396 known to be used. If you have device vxge in your kernel config file
400 The amd64 kernel now requires a ld that supports ifunc to produce a
401 working kernel, either lld or a newer binutils. lld is built by default
402 on amd64, and the 'buildkernel' target uses it automatically. However,
403 it is not the default linker, so building the kernel the traditional
404 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
405 binutils port/package). lld will soon be default, and this requirement
408 NOTE: As of r334391 lld is the default system linker on amd64, and no
409 workaround is necessary.
412 The nxge(4) driver has been removed. This driver was for PCI-X 10g
413 cards made by s2io/Neterion. The company was aquired by Exar and
414 no longer sells or supports Ethernet products. If you have device
415 nxge in your kernel config file it must be removed.
418 The tz database (tzdb) has been updated to 2018e. This version more
419 correctly models time stamps in time zones with negative DST such as
420 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
421 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
422 time zone abbreviations and the tm_isdst flag.
425 The ixgb(4) driver has been removed. This driver was for an early and
426 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
427 quickly shifted to the long lived ixgbe family. If you have device
428 ixgb in your kernel config file it must be removed.
431 The lmc(4) driver has been removed. This was a WAN interface
432 card that was already reportedly rare in 2003, and had an ambiguous
433 license. If you have device lmc in your kernel config file it must
437 Support for Arcnet networks has been removed. If you have device
438 arcnet or device cm in your kernel config file they must be
442 Support for FDDI networks has been removed. If you have device
443 fddi or device fpa in your kernel config file they must be
447 In addition to supporting RFC 3164 formatted messages, the
448 syslogd(8) service is now capable of parsing RFC 5424 formatted
449 log messages. The main benefit of using RFC 5424 is that clients
450 may now send log messages with timestamps containing year numbers,
451 microseconds and time zone offsets.
453 Similarly, the syslog(3) C library function has been altered to
454 send RFC 5424 formatted messages to the local system logging
455 daemon. On systems using syslogd(8), this change should have no
456 negative impact, as long as syslogd(8) and the C library are
457 updated at the same time. On systems using a different system
458 logging daemon, it may be necessary to make configuration
459 adjustments, depending on the software used.
461 When using syslog-ng, add the 'syslog-protocol' flag to local
462 input sources to enable parsing of RFC 5424 formatted messages:
465 unix-dgram("/var/run/log" flags(syslog-protocol));
468 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
469 of the 'imuxsock' module to let messages be processed by the
470 regular RFC 3164/5424 parsing pipeline:
472 module(load="imuxsock" SysSock.UseSpecialParser="off")
474 Do note that these changes only affect communication between local
475 applications and syslogd(8). The format that syslogd(8) uses to
476 store messages on disk or forward messages to other systems
477 remains unchanged. syslogd(8) still uses RFC 3164 for these
478 purposes. Options to customize this behaviour will be added in the
479 future. Utilities that process log files stored in /var/log are
480 thus expected to continue to function as before.
482 __FreeBSD_version has been incremented to 1200061 to denote this
486 Support for token ring networks has been removed. If you
487 have "device token" in your kernel config you should remove
488 it. No device drivers supported token ring.
491 makefs was modified to be able to tag ISO9660 El Torito boot catalog
492 entries as EFI instead of overloading the i386 tag as done previously.
493 The amd64 mkisoimages.sh script used to build amd64 ISO images for
494 release was updated to use this. This may mean that makefs must be
495 updated before "make cdrom" can be run in the release directory. This
496 should be as simple as:
498 $ cd $SRCDIR/usr.sbin/makefs
499 $ make depend all install
502 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
503 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
504 Co-existance for the transition period will come shortly. Booting is a
505 complex environment and test coverage for Lua-enabled loaders has been
506 thin, so it would be prudent to assume it might not work and make
507 provisions for backup boot methods.
510 devmatch functionality has been turned on in devd. It will automatically
511 load drivers for unattached devices. This may cause unexpected drivers to
512 be loaded. Please report any problems to current@ and imp@freebsd.org.
515 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
516 6.0.0. Please see the 20141231 entry below for information about
517 prerequisites and upgrading, if you are not already using clang 3.5.0
521 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
522 This means it is used to link the kernel and userland libraries and
523 executables, but is not yet installed as /usr/bin/ld by default.
525 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
526 WITHOUT_LLD_BOOTSTRAP=yes
529 On i386, pmtimer has been removed. Its functionality has been folded
530 into apm. It was a no-op on ACPI in current for a while now (but was still
531 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
532 from kernel config files.
535 The use of RSS hash from the network card aka flowid has been
536 disabled by default for lagg(4) as it's currently incompatible with
537 the lacp and loadbalance protocols.
539 This can be re-enabled by setting the following in loader.conf:
540 net.link.lagg.default_use_flowid="1"
543 The SW_WATCHDOG option is no longer necessary to enable the
544 hardclock-based software watchdog if no hardware watchdog is
545 configured. As before, SW_WATCHDOG will cause the software
546 watchdog to be enabled even if a hardware watchdog is configured.
549 r326887 fixes the issue described in the 20171214 UPDATING entry.
550 r326888 flips the switch back to building GELI support always.
553 r362593 broke ZFS + GELI support for reasons unknown. However,
554 it also broke ZFS support generally, so GELI has been turned off
555 by default as the lesser evil in r326857. If you boot off ZFS and/or
556 GELI, it might not be a good time to update.
559 PowerPC users must update loader(8) by rebuilding world before
560 installing a new kernel, as the protocol connecting them has
561 changed. Without the update, loader metadata will not be passed
562 successfully to the kernel and users will have to enter their
563 root partition at the kernel mountroot prompt to continue booting.
564 Newer versions of loader can boot old kernels without issue.
567 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
568 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
569 to WITH/OUT_LOADER_GELI.
572 The naive and non-compliant support of posix_fallocate(2) in ZFS
573 has been removed as of r325320. The system call now returns EINVAL
574 when used on a ZFS file. Although the new behavior complies with the
575 standard, some consumers are not prepared to cope with it.
576 One known victim is lld prior to r325420.
579 Building in a FreeBSD src checkout will automatically create object
580 directories now rather than store files in the current directory if
581 'make obj' was not ran. Calling 'make obj' is no longer necessary.
582 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
583 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
587 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
588 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
589 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
590 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
591 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
592 The UNIFIED_OBJDIR option is a transitional feature that will be
593 removed for 12.0 release; please migrate to the new format for any
594 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
595 than hardcoding paths.
598 The native-xtools target no longer installs the files by default to the
599 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
600 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
603 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
604 options are changing from controlling the build if defined / undefined
605 to controlling the build with explicit 'yes' or 'no' values. They will
606 shift to WITH/WITHOUT options to match other options in the system.
609 libstand has turned into a private library for sys/boot use only.
610 It is no longer supported as a public interface outside of sys/boot.
613 The arm port has split armv6 into armv6 and armv7. armv7 is now
614 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
615 and are running a kernel from before r324363, you will need to add
616 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
619 When building multiple kernels using KERNCONF, non-existent KERNCONF
620 files will produce an error and buildkernel will fail. Previously
621 missing KERNCONF files silently failed giving no indication as to
622 why, only to subsequently discover during installkernel that the
623 desired kernel was never built in the first place.
626 The default serial number format for CTL LUNs has changed. This will
627 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
628 or iSCSI clients care about their LUNs' serial numbers. Users who
629 require serial number stability should hardcode serial numbers in
633 For 32-bit arm compiled for hard-float support, soft-floating point
634 binaries now always get their shared libraries from
635 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
636 /usr/libsoft also existed). Only users with a hard-float ld.so, but
637 soft-float everything else should be affected.
640 The geli password typed at boot is now hidden. To restore the previous
641 behavior, see geli(8) for configuration options.
644 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
645 sysctl values. Minor nit, but requires a rebuild of both world/kernel
649 "make check" behavior (made in ^/head@r295380) has been changed to
650 execute from a limited sandbox, as opposed to executing from
654 - The "beforecheck" and "aftercheck" targets are now specified.
655 - ${CHECKDIR} (added in commit noted above) has been removed.
656 - Legacy behavior can be enabled by setting
657 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
659 If the limited sandbox mode is enabled, "make check" will execute
660 "make distribution", then install, execute the tests, and clean up the
661 sandbox if successful.
663 The "make distribution" and "make install" targets are typically run as
664 root to set appropriate permissions and ownership at installation time.
665 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
666 environment if executing "make check" with limited sandbox mode using
667 an unprivileged user.
670 Since the switch to GPT disk labels, fsck for UFS/FFS has been
671 unable to automatically find alternate superblocks. As of r322297,
672 the information needed to find alternate superblocks has been
673 moved to the end of the area reserved for the boot block.
674 Filesystems created with a newfs of this vintage or later
675 will create the recovery information. If you have a filesystem
676 created prior to this change and wish to have a recovery block
677 created for your filesystem, you can do so by running fsck in
678 foreground mode (i.e., do not use the -p or -y options). As it
679 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
680 to which you should answer yes.
683 As of r321665, an NFSv4 server configuration that services
684 Kerberos mounts or clients that do not support the uid/gid in
685 owner/owner_group string capability, must explicitly enable
686 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
687 machine's /etc/rc.conf file.
690 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
691 Please see the 20141231 entry below for information about prerequisites
692 and upgrading, if you are not already using clang 3.5.0 or higher.
695 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
696 r-commands (rlogin, rsh, etc.) to be built with the base system.
699 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
700 a very major ABI incompatible change, so users of FreeBSD/powerpc must
701 be careful when performing source upgrades. It is best to run
702 'make installworld' from an alternate root system, either a live
703 CD/memory stick, or a temporary root partition. Additionally, all ports
704 must be recompiled. powerpc64 is largely unaffected, except in the case
705 of 32-bit compatibility. All 32-bit binaries will be affected.
708 Forward compatibility for the "ino64" project have been committed. This
709 will allow most new binaries to run on older kernels in a limited
710 fashion. This prevents many of the common foot-shooting actions in the
711 upgrade as well as the limited ability to roll back the kernel across
712 the ino64 upgrade. Complicated use cases may not work properly, though
713 enough simpler ones work to allow recovery in most situations.
716 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
717 if you require the GPL compiler.
720 The internal ABI used for communication between the NFS kernel modules
721 was changed by r320085, so __FreeBSD_version was bumped to
722 ensure all the NFS related modules are updated together.
725 The ABI of struct event was changed by extending the data
726 member to 64bit and adding ext fields. For upgrade, same
727 precautions as for the entry 20170523 "ino64" must be
731 The GNU roff toolchain has been removed from base. To render manpages
732 which are not supported by mandoc(1), man(1) can fallback on GNU roff
733 from ports (and recommends to install it).
734 To render roff(7) documents, consider using GNU roff from ports or the
735 heirloom doctools roff toolchain from ports via pkg install groff or
736 via pkg install heirloom-doctools.
739 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
740 smaller runtime footprint builds. This is useful for embedded systems
741 which only require one chipset support.
743 If you load it as a module, make sure this is in /boot/loader.conf:
747 This will load the HAL, all chip/RF backends and if_ath_pci.
748 If you have if_ath_pci in /boot/loader.conf, ensure it is after
749 if_ath or it will not load any HAL chipset support.
751 If you want to selectively load things (eg on ye cheape ARM/MIPS
752 platforms where RAM is at a premium) you should:
755 * load the chip modules in question
756 * load ath_rate, ath_dfs
758 * load if_ath_pci and/or if_ath_ahb depending upon your particular
759 bus bind type - this is where probe/attach is done.
761 For further comments/feedback, poke adrian@ .
764 The "ino64" 64-bit inode project has been committed, which extends
765 a number of types to 64 bits. Upgrading in place requires care and
766 adherence to the documented upgrade procedure.
768 If using a custom kernel configuration ensure that the
769 COMPAT_FREEBSD11 option is included (as during the upgrade the
770 system will be running the ino64 kernel with the existing world).
772 For the safest in-place upgrade begin by removing previous build
773 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
774 full procedure documented below under the heading "To rebuild
775 everything and install it on the current system." Specifically,
776 a reboot is required after installing the new kernel before
780 The NATM framework including the en(4), fatm(4), hatm(4), and
781 patm(4) devices has been removed. Consumers should plan a
782 migration before the end-of-life date for FreeBSD 11.
785 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
786 diff has not been implemented, if those are needed a newer version of
787 GNU diff is available via the diffutils package under the gdiff name.
790 As of r316810 for ipfilter, keep frags is no longer assumed when
791 keep state is specified in a rule. r316810 aligns ipfilter with
792 documentation in man pages separating keep frags from keep state.
793 This allows keep state to be specified without forcing keep frags
794 and allows keep frags to be specified independently of keep state.
795 To maintain previous behaviour, also specify keep frags with
796 keep state (as documented in ipf.conf.5).
799 arm64 builds now use the base system LLD 4.0.0 linker by default,
800 instead of requiring that the aarch64-binutils port or package be
801 installed. To continue using aarch64-binutils, set
802 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
805 The UDP optimization in entry 20160818 that added the sysctl
806 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
807 packets will no longer be treated as L3 broadcast packets.
810 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
811 use any explicitly assigned loopback address available in the jail
812 instead of using the first assigned address of the jail.
815 The ctl.ko module no longer implements the iSCSI target frontend:
816 cfiscsi.ko does instead.
818 If building cfiscsi.ko as a kernel module, the module can be loaded
819 via one of the following methods:
820 - `cfiscsi_load="YES"` in loader.conf(5).
821 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
822 - ctladm(8)/ctld(8), when compiled with iSCSI support
823 (`WITH_ISCSI=yes` in src.conf(5))
825 Please see cfiscsi(4) for more details.
828 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
829 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
830 same source (previously, the dependency of mmcsd.ko on mmc.ko was
831 missing, but mmcsd.ko now will refuse to load if it is incompatible
835 The syntax of ipfw(8) named states was changed to avoid ambiguity.
836 If you have used named states in the firewall rules, you need to modify
837 them after installworld and before rebooting. Now named states must
838 be prefixed with colon.
841 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
842 removed as the userland we provide cannot use them. The KMS version
843 (sys/dev/drm2) supports the same hardware.
846 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
847 Please see the 20141231 entry below for information about prerequisites
848 and upgrading, if you are not already using clang 3.5.0 or higher.
851 The code that provides support for ZFS .zfs/ directory functionality
852 has been reimplemented. It's not possible now to create a snapshot
853 by mkdir under .zfs/snapshot/. That should be the only user visible
857 EISA bus support has been removed. The WITH_EISA option is no longer
861 MCA bus support has been removed.
864 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
865 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
868 The EM_MULTIQUEUE kernel configuration option is deprecated now that
869 the em(4) driver conforms to iflib specifications.
872 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
873 IFLIB. If you have a custom kernel configuration that excludes em(4)
874 but you use igb(4), you need to re-add em(4) to your custom configuration.
877 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
878 Please see the 20141231 entry below for information about prerequisites
879 and upgrading, if you are not already using clang 3.5.0 or higher.
882 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
883 Please see the 20141231 entry below for information about prerequisites
884 and upgrading, if you are not already using clang 3.5.0 or higher.
887 The layout of the pmap structure has changed for powerpc to put the pmap
888 statistics at the front for all CPU variations. libkvm(3) and all tools
889 that link against it need to be recompiled.
892 isl(4) and cyapa(4) drivers now require a new driver,
893 chromebook_platform(4), to work properly on Chromebook-class hardware.
894 On other types of hardware the drivers may need to be configured using
895 device hints. Please see the corresponding manual pages for details.
898 The urtwn(4) driver was merged into rtwn(4) and now consists of
899 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
901 Also, firmware for RTL8188CE was renamed due to possible name
902 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
905 GNU rcs has been removed from base. It is available as packages:
906 - rcs: Latest GPLv3 GNU rcs version.
907 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
911 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
912 modules now requires that the kernel configuration contain the
913 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
916 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
917 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
920 Relocatable object files with the extension of .So have been renamed
921 to use an extension of .pico instead. The purpose of this change is
922 to avoid a name clash with shared libraries on case-insensitive file
923 systems. On those file systems, foo.So is the same file as foo.so.
926 GNU rcs has been turned off by default. It can (temporarily) be built
927 again by adding WITH_RCS knob in src.conf.
928 Otherwise, GNU rcs is available from packages:
929 - rcs: Latest GPLv3 GNU rcs version.
930 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
933 The backup_uses_rcs functionality has been removed from rc.subr.
936 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
937 two separate components, QUEUE_MACRO_DEBUG_TRACE and
938 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
939 QUEUE_MACRO_DEBUG behavior.
942 r304787 changed some ioctl interfaces between the iSCSI userspace
943 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
944 rebuilt to work with new kernels. __FreeBSD_version has been bumped
948 The UDP receive code has been updated to only treat incoming UDP
949 packets that were addressed to an L2 broadcast address as L3
950 broadcast packets. It is not expected that this will affect any
951 standards-conforming UDP application. The new behaviour can be
952 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
956 Remove the openbsd_poll system call.
957 __FreeBSD_version has been bumped because of this.
960 The stable/11 branch has been created from head@r302406.
963 The libc stub for the pipe(2) system call has been replaced with
964 a wrapper that calls the pipe2(2) system call and the pipe(2)
965 system call is now only implemented by the kernels that include
966 "options COMPAT_FREEBSD10" in their config file (this is the
967 default). Users should ensure that this option is enabled in
968 their kernel or upgrade userspace to r302092 before upgrading their
972 CAM will now strip leading spaces from SCSI disks' serial numbers.
973 This will affect users who create UFS filesystems on SCSI disks using
974 those disk's diskid device nodes. For example, if /etc/fstab
975 previously contained a line like
976 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
977 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
978 transforms like gmirror may also be affected. ZFS users should
982 The bitstring(3) API has been updated with new functionality and
983 improved performance. But it is binary-incompatible with the old API.
984 Objects built with the new headers may not be linked against objects
985 built with the old headers.
988 The brk and sbrk functions have been removed from libc on arm64.
989 Binutils from ports has been updated to not link to these
990 functions and should be updated to the latest version before
991 installing a new libc.
994 The armv6 port now defaults to hard float ABI. Limited support
995 for running both hardfloat and soft float on the same system
996 is available using the libraries installed with -DWITH_LIBSOFT.
997 This has only been tested as an upgrade path for installworld
998 and packages may fail or need manual intervention to run. New
999 packages will be needed.
1001 To update an existing self-hosted armv6hf system, you must add
1002 TARGET_ARCH=armv6 on the make command line for both the build
1003 and the install steps.
1006 Kernel modules compiled outside of a kernel build now default to
1007 installing to /boot/modules instead of /boot/kernel. Many kernel
1008 modules built this way (such as those in ports) already overrode
1009 KMODDIR explicitly to install into /boot/modules. However,
1010 manually building and installing a module from /sys/modules will
1011 now install to /boot/modules instead of /boot/kernel.
1014 The CAM I/O scheduler has been committed to the kernel. There should be
1015 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1016 list of known rogues that claim support for this but actually corrupt
1017 data is believed to be complete, be on the lookout for data
1018 corruption. The known rogue list is believed to be complete:
1020 o Crucial MX100, M550 drives with MU01 firmware.
1021 o Micron M510 and M550 drives with MU01 firmware.
1022 o Micron M500 prior to MU07 firmware
1023 o Samsung 830, 840, and 850 all firmwares
1024 o FCCT M500 all firmwares
1026 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1027 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1028 updated firmware. Black listed drives will work correctly because these
1029 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1030 this list is the same as found in Linux, it's believed there are no
1031 other rogues in the market place. All other models from the above
1034 To be safe, if you are at all concerned, you can quirk each of your
1035 drives to prevent NCQ from being sent by setting:
1036 kern.cam.ada.X.quirks="0x2"
1037 in loader.conf. If the drive requires the 4k sector quirk, set the
1038 quirks entry to 0x3.
1041 The FAST_DEPEND build option has been removed and its functionality is
1042 now the one true way. The old mkdep(1) style of 'make depend' has
1043 been removed. See 20160311 for further details.
1046 Resource range types have grown from unsigned long to uintmax_t. All
1047 drivers, and anything using libdevinfo, need to be recompiled.
1050 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1051 builds. It no longer runs mkdep(1) during 'make depend', and the
1052 'make depend' stage can safely be skipped now as it is auto ran
1053 when building 'make all' and will generate all SRCS and DPSRCS before
1054 building anything else. Dependencies are gathered at compile time with
1055 -MF flags kept in separate .depend files per object file. Users should
1056 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1057 stale .depend files.
1060 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1061 kernel modules. Therefore, if you load any kernel modules at boot time,
1062 please install the boot loaders after you install the kernel, but before
1066 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1067 make installkernel KERNCONF=YOUR_KERNEL_HERE
1068 make -C sys/boot install
1069 <reboot in single user>
1071 Then follow the usual steps, described in the General Notes section,
1075 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1076 see the 20141231 entry below for information about prerequisites and
1077 upgrading, if you are not already using clang 3.5.0 or higher.
1080 The AIO subsystem is now a standard part of the kernel. The
1081 VFS_AIO kernel option and aio.ko kernel module have been removed.
1082 Due to stability concerns, asynchronous I/O requests are only
1083 permitted on sockets and raw disks by default. To enable
1084 asynchronous I/O requests on all file types, set the
1085 vfs.aio.enable_unsafe sysctl to a non-zero value.
1088 The ELF object manipulation tool objcopy is now provided by the
1089 ELF Tool Chain project rather than by GNU binutils. It should be a
1090 drop-in replacement, with the addition of arm64 support. The
1091 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1092 to obtain the GNU version if necessary.
1095 Building ZFS pools on top of zvols is prohibited by default. That
1096 feature has never worked safely; it's always been prone to deadlocks.
1097 Using a zvol as the backing store for a VM guest's virtual disk will
1098 still work, even if the guest is using ZFS. Legacy behavior can be
1099 restored by setting vfs.zfs.vol.recursive=1.
1102 The NONE and HPN patches has been removed from OpenSSH. They are
1103 still available in the security/openssh-portable port.
1106 With the addition of ypldap(8), a new _ypldap user is now required
1107 during installworld. "mergemaster -p" can be used to add the user
1108 prior to installworld, as documented in the handbook.
1111 The tftp loader (pxeboot) now uses the option root-path directive. As a
1112 consequence it no longer looks for a pxeboot.4th file on the tftp
1113 server. Instead it uses the regular /boot infrastructure as with the
1117 The code to start recording plug and play data into the modules has
1118 been committed. While the old tools will properly build a new kernel,
1119 a number of warnings about "unknown metadata record 4" will be produced
1120 for an older kldxref. To avoid such warnings, make sure to rebuild
1121 the kernel toolchain (or world). Make sure that you have r292078 or
1122 later when trying to build 292077 or later before rebuilding.
1125 Debug data files are now built by default with 'make buildworld' and
1126 installed with 'make installworld'. This facilitates debugging but
1127 requires more disk space both during the build and for the installed
1128 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1132 r291527 changed the internal interface between the nfsd.ko and
1133 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1134 __FreeBSD_version has been bumped because of this.
1137 Add support for unicode collation strings leads to a change of
1138 order of files listed by ls(1) for example. To get back to the old
1139 behaviour, set LC_COLLATE environment variable to "C".
1141 Databases administrators will need to reindex their databases given
1142 collation results will be different.
1144 Due to a bug in install(1) it is recommended to remove the ancient
1145 locales before running make installworld.
1147 rm -rf /usr/share/locale/*
1150 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1151 libcrypto.so.7 or libssl.so.7 must be recompiled.
1154 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1155 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1156 should be replaced with isp_2400 and isp_2500 modules respectively.
1159 The build previously allowed using 'make -n' to not recurse into
1160 sub-directories while showing what commands would be executed, and
1161 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1162 and 'make -N' will not.
1165 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1166 and etcupdate will now use this file. A custom sendmail.cf is now
1167 updated via this mechanism rather than via installworld. If you had
1168 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1169 want to remove the exclusion or change it to "always install".
1170 /etc/mail/sendmail.cf is now managed the same way regardless of
1171 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1172 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1175 Compatibility shims for legacy ATA device names have been removed.
1176 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1177 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1178 environment variables, /dev/ad* and /dev/ar* symbolic links.
1181 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1182 Please see the 20141231 entry below for information about prerequisites
1183 and upgrading, if you are not already using clang 3.5.0 or higher.
1186 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1187 and renamed from .symbols to .debug. This reduces the size requirements
1188 on the boot partition or file system and provides consistency with
1189 userland debug files.
1191 When using the supported kernel installation method the
1192 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1193 as is done with /boot/kernel.
1195 Developers wishing to maintain the historical behavior of installing
1196 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1199 The wireless drivers had undergone changes that remove the 'parent
1200 interface' from the ifconfig -l output. The rc.d network scripts
1201 used to check presence of a parent interface in the list, so old
1202 scripts would fail to start wireless networking. Thus, etcupdate(3)
1203 or mergemaster(8) run is required after kernel update, to update your
1204 rc.d scripts in /etc.
1207 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1208 These configurations are now automatically interpreted as
1209 'scrub fragment reassemble'.
1212 Kernel-loadable modules for the random(4) device are back. To use
1213 them, the kernel must have
1216 options RANDOM_LOADABLE
1218 kldload(8) can then be used to load random_fortuna.ko
1219 or random_yarrow.ko. Please note that due to the indirect
1220 function calls that the loadable modules need to provide,
1221 the build-in variants will be slightly more efficient.
1223 The random(4) kernel option RANDOM_DUMMY has been retired due to
1224 unpopularity. It was not all that useful anyway.
1227 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1228 Control over building the ELF Tool Chain tools is now provided by
1229 the WITHOUT_TOOLCHAIN knob.
1232 The polarity of Pulse Per Second (PPS) capture events with the
1233 uart(4) driver has been corrected. Prior to this change the PPS
1234 "assert" event corresponded to the trailing edge of a positive PPS
1235 pulse and the "clear" event was the leading edge of the next pulse.
1237 As the width of a PPS pulse in a typical GPS receiver is on the
1238 order of 1 millisecond, most users will not notice any significant
1239 difference with this change.
1241 Anyone who has compensated for the historical polarity reversal by
1242 configuring a negative offset equal to the pulse width will need to
1243 remove that workaround.
1246 The default group assigned to /dev/dri entries has been changed
1247 from 'wheel' to 'video' with the id of '44'. If you want to have
1248 access to the dri devices please add yourself to the video group
1251 # pw groupmod video -m $USER
1254 The menu.rc and loader.rc files will now be replaced during
1255 upgrades. Please migrate local changes to menu.rc.local and
1256 loader.rc.local instead.
1259 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1260 strings and strip have been removed. The src.conf(5) knob
1261 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1264 As ZFS requires more kernel stack pages than is the default on some
1265 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1266 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1268 Please consider using 'options KSTACK_PAGES=X' where X is greater
1269 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1272 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1273 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1274 default, i.e., they will not contain "::". For example, instead
1275 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1276 to have a more specific match, such as different map entries for
1277 IPv6:0:0 vs IPv6:0. This change requires that configuration
1278 data (including maps, files, classes, custom ruleset, etc.) must
1279 use the same format, so make certain such configuration data is
1280 upgrading. As a very simple check search for patterns like
1281 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1282 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1283 the cf option UseCompressedIPv6Addresses.
1286 The default kernel entropy-processing algorithm is now
1287 Fortuna, replacing Yarrow.
1289 Assuming you have 'device random' in your kernel config
1290 file, the configurations allow a kernel option to override
1291 this default. You may choose *ONE* of:
1293 options RANDOM_YARROW # Legacy /dev/random algorithm.
1294 options RANDOM_DUMMY # Blocking-only driver.
1296 If you have neither, you get Fortuna. For most people,
1297 read no further, Fortuna will give a /dev/random that works
1298 like it always used to, and the difference will be irrelevant.
1300 If you remove 'device random', you get *NO* kernel-processed
1301 entropy at all. This may be acceptable to folks building
1302 embedded systems, but has complications. Carry on reading,
1303 and it is assumed you know what you need.
1305 *PLEASE* read random(4) and random(9) if you are in the
1306 habit of tweaking kernel configs, and/or if you are a member
1307 of the embedded community, wanting specific and not-usual
1308 behaviour from your security subsystems.
1310 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1311 random', you will NOT have a functioning /dev/random, and
1312 many cryptographic features will not work, including SSH.
1313 You may also find strange behaviour from the random(3) set
1314 of library functions, in particular sranddev(3), srandomdev(3)
1315 and arc4random(3). The reason for this is that the KERN_ARND
1316 sysctl only returns entropy if it thinks it has some to
1317 share, and with RANDOM_DUMMY or no 'device random' this
1321 An additional fix for the issue described in the 20150614 sendmail
1322 entry below has been committed in revision 284717.
1325 FreeBSD's old make (fmake) has been removed from the system. It is
1326 available as the devel/fmake port or via pkg install fmake.
1329 The fix for the issue described in the 20150614 sendmail entry
1330 below has been committed in revision 284436. The work
1331 around described in that entry is no longer needed unless the
1332 default setting is overridden by a confDH_PARAMETERS configuration
1333 setting of '5' or pointing to a 512 bit DH parameter file.
1336 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1337 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1338 and devel/kyua to version 0.20+ and adjust any calling code to work
1339 with Kyuafile and kyua.
1342 The import of openssl to address the FreeBSD-SA-15:10.openssl
1343 security advisory includes a change which rejects handshakes
1344 with DH parameters below 768 bits. sendmail releases prior
1345 to 8.15.2 (not yet released), defaulted to a 512 bit
1346 DH parameter setting for client connections. To work around
1347 this interoperability, sendmail can be configured to use a
1348 2048 bit DH parameter by:
1350 1. Edit /etc/mail/`hostname`.mc
1351 2. If a setting for confDH_PARAMETERS does not exist or
1352 exists and is set to a string beginning with '5',
1353 replace it with '2'.
1354 3. If a setting for confDH_PARAMETERS exists and is set to
1355 a file path, create a new file with:
1356 openssl dhparam -out /path/to/file 2048
1357 4. Rebuild the .cf file:
1358 cd /etc/mail/; make; make install
1359 5. Restart sendmail:
1360 cd /etc/mail/; make restart
1362 A sendmail patch is coming, at which time this file will be
1366 Generation of legacy formatted entries have been disabled by default
1367 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1368 entries were converted to use the new format by default when the new,
1369 machine independent format have been added and supported since FreeBSD
1372 Please see the pwd_mkdb(8) manual page for further details.
1375 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1376 20141231 entry below for information about prerequisites and upgrading,
1377 if you are not already using 3.5.0 or higher.
1380 TI platform code switched to using vendor DTS files and this update
1381 may break existing systems running on Beaglebone, Beaglebone Black,
1384 - dtb files should be regenerated/reinstalled. Filenames are the
1385 same but content is different now
1386 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1387 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1388 addressing scheme is now pin 25 on /dev/gpioc3.
1389 - Pandaboard: /etc/ttys should be updated, serial console device is
1390 now /dev/ttyu2, not /dev/ttyu0
1393 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1394 If you need the GNU extension from groff soelim(1), install groff
1395 from package: pkg install groff, or via ports: textproc/groff.
1398 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1399 defined in symlink(7); previously symlinks were silently ignored.
1402 The const qualifier has been removed from iconv(3) to comply with
1403 POSIX. The ports tree is aware of this from r384038 onwards.
1406 Libraries specified by LIBADD in Makefiles must have a corresponding
1407 DPADD_<lib> variable to ensure correct dependencies. This is now
1408 enforced in src.libnames.mk.
1411 From legacy ata(4) driver was removed support for SATA controllers
1412 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1413 Kernel modules ataahci and ataadaptec were removed completely,
1414 replaced by ahci and mvs modules respectively.
1417 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1418 the 20141231 entry below for information about prerequisites and
1419 upgrading, if you are not already using 3.5.0 or higher.
1422 The 32-bit PowerPC kernel has been changed to a position-independent
1423 executable. This can only be booted with a version of loader(8)
1424 newer than January 31, 2015, so make sure to update both world and
1425 kernel before rebooting.
1428 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1429 but before r278950, the RNG was not seeded properly. Immediately
1430 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1431 ssh keys or openssl keys) that were generated w/ a kernel from that
1432 range. This does not affect programs that directly used /dev/random
1433 or /dev/urandom. All userland uses of arc4random(3) are affected.
1436 The autofs(4) ABI was changed in order to restore binary compatibility
1437 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1438 with the new kernel.
1441 The powerpc64 kernel has been changed to a position-independent
1442 executable. This can only be booted with a new version of loader(8),
1443 so make sure to update both world and kernel before rebooting.
1446 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1447 only release, no new features have been added. Please see the 20141231
1448 entry below for information about prerequisites and upgrading, if you
1449 are not already using 3.5.0.
1452 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1453 taken from the ELF Tool Chain project rather than GNU binutils. They
1454 should be drop-in replacements, with the addition of arm64 support.
1455 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1456 binutils tools, if necessary. See 20150805 for updated information.
1459 The default Unbound configuration now enables remote control
1460 using a local socket. Users who have already enabled the
1461 local_unbound service should regenerate their configuration
1462 by running "service local_unbound setup" as root.
1465 The GNU texinfo and GNU info pages have been removed.
1466 To be able to view GNU info pages please install texinfo from ports.
1469 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1471 As of this release, a prerequisite for building clang, llvm and lldb is
1472 a C++11 capable compiler and C++11 standard library. This means that to
1473 be able to successfully build the cross-tools stage of buildworld, with
1474 clang as the bootstrap compiler, your system compiler or cross compiler
1475 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1476 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1479 On any standard FreeBSD 10.x or 11.x installation, where clang and
1480 libc++ are on by default (that is, on x86 or arm), this should work out
1483 On 9.x installations where clang is enabled by default, e.g. on x86 and
1484 powerpc, libc++ will not be enabled by default, so libc++ should be
1485 built (with clang) and installed first. If both clang and libc++ are
1486 missing, build clang first, then use it to build libc++.
1488 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1489 the instructions for 9.x above.
1491 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1492 default, and do not build clang.
1494 Many embedded systems are resource constrained, and will not be able to
1495 build clang in a reasonable time, or in some cases at all. In those
1496 cases, cross building bootable systems on amd64 is a workaround.
1498 This new version of clang introduces a number of new warnings, of which
1499 the following are most likely to appear:
1503 This warns in two cases, for both C and C++:
1504 * When the code is trying to take the absolute value of an unsigned
1505 quantity, which is effectively a no-op, and almost never what was
1506 intended. The code should be fixed, if at all possible. If you are
1507 sure that the unsigned quantity can be safely cast to signed, without
1508 loss of information or undefined behavior, you can add an explicit
1509 cast, or disable the warning.
1511 * When the code is trying to take an absolute value, but the called
1512 abs() variant is for the wrong type, which can lead to truncation.
1513 If you want to disable the warning instead of fixing the code, please
1514 make sure that truncation will not occur, or it might lead to unwanted
1517 -Wtautological-undefined-compare and
1518 -Wundefined-bool-conversion
1520 These warn when C++ code is trying to compare 'this' against NULL, while
1521 'this' should never be NULL in well-defined C++ code. However, there is
1522 some legacy (pre C++11) code out there, which actively abuses this
1523 feature, which was less strictly defined in previous C++ versions.
1525 Squid and openjdk do this, for example. The warning can be turned off
1526 for C++98 and earlier, but compiling the code in C++11 mode might result
1527 in unexpected behavior; for example, the parts of the program that are
1528 unreachable could be optimized away.
1531 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1532 kernel sources have been removed. The .h files remain, since some
1533 utilities include them. This will need to be fixed later.
1534 If "mount -t oldnfs ..." is attempted, it will fail.
1535 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1536 the utilities will report errors.
1539 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1540 directories to top level SUBDIR variable when their parent
1541 directory is included in LOCAL_DIRS. Users with build systems with
1542 such hierarchies and without SUBDIR entries in the parent
1543 directory Makefiles should add them or add the directories to
1547 faith(4) and faithd(8) have been removed from the base system. Faith
1548 has been obsolete for a very long time.
1551 vt(4), the new console driver, is enabled by default. It brings
1552 support for Unicode and double-width characters, as well as
1553 support for UEFI and integration with the KMS kernel video
1556 You may need to update your console settings in /etc/rc.conf,
1557 most probably the keymap. During boot, /etc/rc.d/syscons will
1558 indicate what you need to do.
1560 vt(4) still has issues and lacks some features compared to
1561 syscons(4). See the wiki for up-to-date information:
1562 https://wiki.freebsd.org/Newcons
1564 If you want to keep using syscons(4), you can do so by adding
1565 the following line to /boot/loader.conf:
1569 pjdfstest has been integrated into kyua as an opt-in test suite.
1570 Please see share/doc/pjdfstest/README for more details on how to
1574 gperf has been removed from the base system for architectures
1575 that use clang. Ports that require gperf will obtain it from the
1579 pjdfstest has been moved from tools/regression/pjdfstest to
1583 At svn r271982, The default linux compat kernel ABI has been adjusted
1584 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1585 update. If you wish to continue using the linux-f10 compat ports,
1586 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1587 encouraged to update their linux-compat packages to linux-c6 during
1588 their next update cycle.
1591 The ofwfb driver, used to provide a graphics console on PowerPC when
1592 using vt(4), no longer allows mmap() of all physical memory. This
1593 will prevent Xorg on PowerPC with some ATI graphics cards from
1594 initializing properly unless x11-servers/xorg-server is updated to
1598 The xdev targets have been converted to using TARGET and
1599 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1602 The default unbound configuration has been modified to address
1603 issues with reverse lookups on networks that use private
1604 address ranges. If you use the local_unbound service, run
1605 "service local_unbound setup" as root to regenerate your
1606 configuration, then "service local_unbound reload" to load the
1610 The GNU texinfo and GNU info pages are not built and installed
1611 anymore, WITH_INFO knob has been added to allow to built and install
1613 UPDATE: see 20150102 entry on texinfo's removal
1616 The GNU readline library is now an INTERNALLIB - that is, it is
1617 statically linked into consumers (GDB and variants) in the base
1618 system, and the shared library is no longer installed. The
1619 devel/readline port is available for third party software that
1623 The Itanium architecture (ia64) has been removed from the list of
1624 known architectures. This is the first step in the removal of the
1628 Commit r268115 has added NFSv4.1 server support, merged from
1629 projects/nfsv4.1-server. Since this includes changes to the
1630 internal interfaces between the NFS related modules, a full
1631 build of the kernel and modules will be necessary.
1632 __FreeBSD_version has been bumped.
1635 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1636 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1637 which differs from the behaviour controlled by this knob.)
1640 Maximal length of the serial number in CTL was increased from 16 to
1641 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1642 and ctld, need to be rebuilt to work with a new kernel.
1645 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1646 1 respectively to match the upstream numbers. They were out of
1647 sync because, when they were originally added to FreeBSD, the
1648 upstream versions were not respected. These libraries are private
1649 and not yet built by default, so renumbering them should be a
1650 non-issue. However, unclean source trees will yield broken test
1651 programs once the operator executes "make delete-old-libs" after a
1652 "make installworld".
1654 Additionally, the atf-sh binary was made private by moving it into
1655 /usr/libexec/. Already-built shell test programs will keep the
1656 path to the old binary so they will break after "make delete-old"
1659 If you are using WITH_TESTS=yes (not the default), wipe the object
1660 tree and rebuild from scratch to prevent spurious test failures.
1661 This is only needed once: the misnumbered libraries and misplaced
1662 binaries have been added to OptionalObsoleteFiles.inc so they will
1663 be removed during a clean upgrade.
1666 Clang and llvm have been upgraded to 3.4.1 release.
1669 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1670 be removed to avoid issues in the future (and has been added to
1674 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1675 past, it affected all builds that used the bsd.*.mk files. The old
1676 behavior was a bug, but people may have relied upon it. To get this
1677 behavior back, you can .include /etc/src.conf from /etc/make.conf
1678 (which is still global and isn't changed). This also changes the
1679 behavior of incremental builds inside the tree of individual
1680 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1681 Although this has survived make universe and some upgrade scenarios,
1682 other upgrade scenarios may have broken. At least one form of
1683 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1684 as well... In cases where MAKESYSPATH isn't working with this
1685 setting, you'll need to set it to the full path to your tree.
1687 One side effect of all this cleaning up is that bsd.compiler.mk
1688 is no longer implicitly included by bsd.own.mk. If you wish to
1689 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1693 The lindev device has been removed since /dev/full has been made a
1694 standard device. __FreeBSD_version has been bumped.
1697 The knob WITHOUT_VI was added to the base system, which controls
1698 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1699 in order to reorder files share/termcap and didn't build ex(1) as a
1700 build tool, so building/installing with WITH_VI is highly advised for
1701 build hosts for older releases.
1703 This issue has been fixed in stable/9 and stable/10 in r277022 and
1704 r276991, respectively.
1707 The YES_HESIOD knob has been removed. It has been obsolete for
1708 a decade. Please move to using WITH_HESIOD instead or your builds
1709 will silently lack HESIOD.
1712 The uart(4) driver has been changed with respect to its handling
1713 of the low-level console. Previously the uart(4) driver prevented
1714 any process from changing the baudrate or the CLOCAL and HUPCL
1715 control flags. By removing the restrictions, operators can make
1716 changes to the serial console port without having to reboot.
1717 However, when getty(8) is started on the serial device that is
1718 associated with the low-level console, a misconfigured terminal
1719 line in /etc/ttys will now have a real impact.
1720 Before upgrading the kernel, make sure that /etc/ttys has the
1721 serial console device configured as 3wire without baudrate to
1722 preserve the previous behaviour. E.g:
1723 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1726 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1727 to improve performance. To re-enable it, if needed, run rpcbind
1728 with command line option -W.
1731 Switched back to the GPL dtc compiler due to updates in the upstream
1732 dts files not being supported by the BSDL dtc compiler. You will need
1733 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1734 may result while building dtb files during a kernel build if you fail
1735 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1738 Clang and llvm have been upgraded to 3.4 release.
1741 The nve(4) driver has been removed. Please use the nfe(4) driver
1742 for NVIDIA nForce MCP Ethernet adapters instead.
1745 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1746 This could cause certain C++ applications using shared libraries built
1747 against the previous version of libc++ to crash. The incompatibility
1748 has now been fixed, but any C++ applications or shared libraries built
1749 between r261283 and r261801 should be recompiled.
1752 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1753 capability mode support. Please note that enabling the feature in
1754 kernel is still highly recommended.
1757 OpenSSH is now built with sandbox support, and will use sandbox as
1758 the default privilege separation method. This requires Capsicum
1759 capability mode support in kernel.
1762 The libelf and libdwarf libraries have been updated to newer
1763 versions from upstream. Shared library version numbers for
1764 these two libraries were bumped. Any ports or binaries
1765 requiring these two libraries should be recompiled.
1766 __FreeBSD_version is bumped to 1100006.
1769 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1770 instead of providing an explicit one, this would prevent such
1771 Makefile from providing its own Kyuafile in the future during
1772 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1773 intervention is needed to clean an objdir if you use NO_CLEAN:
1774 # find /usr/obj -name Kyuafile | xargs rm -f
1777 The behavior of gss_pseudo_random() for the krb5 mechanism
1778 has changed, for applications requesting a longer random string
1779 than produced by the underlying enctype's pseudo-random() function.
1780 In particular, the random string produced from a session key of
1781 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1782 be different at the 17th octet and later, after this change.
1783 The counter used in the PRF+ construction is now encoded as a
1784 big-endian integer in accordance with RFC 4402.
1785 __FreeBSD_version is bumped to 1100004.
1788 The WITHOUT_ATF build knob has been removed and its functionality
1789 has been subsumed into the more generic WITHOUT_TESTS. If you were
1790 using the former to disable the build of the ATF libraries, you
1791 should change your settings to use the latter.
1794 The default version of mtree is nmtree which is obtained from
1795 NetBSD. The output is generally the same, but may vary
1796 slightly. If you found you need identical output adding
1797 "-F freebsd9" to the command line should do the trick. For the
1798 time being, the old mtree is available as fmtree.
1801 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1802 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1803 1.1.4_8 and verify bsdyml not linked in, before running "make
1805 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1807 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1810 The stable/10 branch has been created in subversion from head
1817 Avoid using make -j when upgrading. While generally safe, there are
1818 sometimes problems using -j to upgrade. If your upgrade fails with
1819 -j, please try again without -j. From time to time in the past there
1820 have been problems using -j with buildworld and/or installworld. This
1821 is especially true when upgrading between "distant" versions (eg one
1822 that cross a major release boundary or several minor releases, or when
1823 several months have passed on the -current branch).
1825 Sometimes, obscure build problems are the result of environment
1826 poisoning. This can happen because the make utility reads its
1827 environment when searching for values for global variables. To run
1828 your build attempts in an "environmental clean room", prefix all make
1829 commands with 'env -i '. See the env(1) manual page for more details.
1831 When upgrading from one major version to another it is generally best to
1832 upgrade to the latest code in the currently installed branch first, then
1833 do an upgrade to the new branch. This is the best-tested upgrade path,
1834 and has the highest probability of being successful. Please try this
1835 approach if you encounter problems with a major version upgrade. Since
1836 the stable 4.x branch point, one has generally been able to upgrade from
1837 anywhere in the most recent stable branch to head / current (or even the
1838 last couple of stable branches). See the top of this file when there's
1841 When upgrading a live system, having a root shell around before
1842 installing anything can help undo problems. Not having a root shell
1843 around can lead to problems if pam has changed too much from your
1844 starting point to allow continued authentication after the upgrade.
1846 This file should be read as a log of events. When a later event changes
1847 information of a prior event, the prior event should not be deleted.
1848 Instead, a pointer to the entry with the new information should be
1849 placed in the old entry. Readers of this file should also sanity check
1850 older entries before relying on them blindly. Authors of new entries
1851 should write them with this in mind.
1855 When upgrading the boot ZFS pool to a new version, always follow
1858 1.) recompile and reinstall the ZFS boot loader and boot block
1859 (this is part of "make buildworld" and "make installworld")
1861 2.) update the ZFS boot block on your boot drive
1863 The following example updates the ZFS boot block on the first
1864 partition (freebsd-boot) of a GPT partitioned drive ada0:
1865 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1867 Non-boot pools do not need these updates.
1871 If you are updating from a prior version of FreeBSD (even one just
1872 a few days old), you should follow this procedure. It is the most
1873 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1875 make kernel-toolchain
1876 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1877 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1879 To test a kernel once
1880 ---------------------
1881 If you just want to boot a kernel once (because you are not sure
1882 if it works, or if you want to boot a known bad kernel to provide
1883 debugging information) run
1884 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1885 nextboot -k testkernel
1887 To rebuild everything and install it on the current system.
1888 -----------------------------------------------------------
1889 # Note: sometimes if you are running current you gotta do more than
1890 # is listed here if you are upgrading from a really old current.
1892 <make sure you have good level 0 dumps>
1894 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1895 make installkernel KERNCONF=YOUR_KERNEL_HERE
1897 <reboot in single user> [3]
1904 To cross-install current onto a separate partition
1905 --------------------------------------------------
1906 # In this approach we use a separate partition to hold
1907 # current's root, 'usr', and 'var' directories. A partition
1908 # holding "/", "/usr" and "/var" should be about 2GB in
1911 <make sure you have good level 0 dumps>
1914 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1915 <maybe newfs current's root partition>
1916 <mount current's root partition on directory ${CURRENT_ROOT}>
1917 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1918 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1919 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1920 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1921 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1922 <reboot into current>
1923 <do a "native" rebuild/install as described in the previous section>
1924 <maybe install compatibility libraries from ports/misc/compat*>
1928 To upgrade in-place from stable to current
1929 ----------------------------------------------
1930 <make sure you have good level 0 dumps>
1932 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1933 make installkernel KERNCONF=YOUR_KERNEL_HERE
1935 <reboot in single user> [3]
1942 Make sure that you've read the UPDATING file to understand the
1943 tweaks to various things you need. At this point in the life
1944 cycle of current, things change often and you are on your own
1945 to cope. The defaults can also change, so please read ALL of
1946 the UPDATING entries.
1948 Also, if you are tracking -current, you must be subscribed to
1949 freebsd-current@freebsd.org. Make sure that before you update
1950 your sources that you have read and understood all the recent
1951 messages there. If in doubt, please track -stable which has
1952 much fewer pitfalls.
1954 [1] If you have third party modules, such as vmware, you
1955 should disable them at this point so they don't crash your
1958 [3] From the bootblocks, boot -s, and then do
1963 adjkerntz -i # if CMOS is wall time
1964 Also, when doing a major release upgrade, it is required that
1965 you boot into single user mode to do the installworld.
1967 [4] Note: This step is non-optional. Failure to do this step
1968 can result in a significant reduction in the functionality of the
1969 system. Attempting to do it by hand is not recommended and those
1970 that pursue this avenue should read this file carefully, as well
1971 as the archives of freebsd-current and freebsd-hackers mailing lists
1972 for potential gotchas. The -U option is also useful to consider.
1973 See mergemaster(8) for more information.
1975 [5] Usually this step is a no-op. However, from time to time
1976 you may need to do this if you get unknown user in the following
1977 step. It never hurts to do it all the time. You may need to
1978 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1979 install) after the buildworld before this step if you last updated
1980 from current before 20130425 or from -stable before 20130430.
1982 [6] This only deletes old files and directories. Old libraries
1983 can be deleted by "make delete-old-libs", but you have to make
1984 sure that no program is using those libraries anymore.
1986 [8] The new kernel must be able to run existing binaries used by
1987 an installworld. When upgrading across major versions, the new
1988 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1989 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1990 binaries). Failure to do so may leave you with a system that is
1991 hard to boot to recover. A GENERIC kernel will include suitable
1992 compatibility options to run binaries from older branches.
1994 Make sure that you merge any new devices from GENERIC since the
1995 last time you updated your kernel config file.
1997 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1998 "?=" instead of the "=" assignment operator, so that buildworld can
1999 override the CPUTYPE if it needs to.
2001 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2002 not on the command line, or in /etc/make.conf. buildworld will
2003 warn if it is improperly defined.
2006 This file contains a list, in reverse chronological order, of major
2007 breakages in tracking -current. It is not guaranteed to be a complete
2008 list of such breakages, and only contains entries since September 23, 2011.
2009 If you need to see UPDATING entries from before that date, you will need
2010 to fetch an UPDATING file from an older FreeBSD release.
2012 Copyright information:
2014 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2016 Redistribution, publication, translation and use, with or without
2017 modification, in full or in part, in any form or format of this
2018 document are permitted without further permission from the author.
2020 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2021 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2022 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2023 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2024 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2025 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2026 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2027 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2028 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2029 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2030 POSSIBILITY OF SUCH DAMAGE.
2032 Contact Warner Losh if you have any questions about your use of