1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
20 FreeBSD 13.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
36 8.0.0. Please see the 20141231 entry below for information about
37 prerequisites and upgrading, if you are not already using clang 3.5.0
41 r342635 changes the way efibootmgr(8) works by requiring users to add
42 the -b (bootnum) parameter for commands where the bootnum was previously
43 specified with each option. For example 'efibootmgr -B 0001' is now
44 'efibootmgr -B -b 0001'.
47 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
48 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
49 servers that have vfs.nfsd.nfs_privport set will only allow mounts
50 from clients using a reserved port#. Since both the FreeBSD and Linux
51 NFSv4 clients use reserved port#s by default, this should not affect
55 The XLP config has been removed. We can't support 64-bit atomics in this
56 kernel because it is running in 32-bit mode. XLP users must transition
57 to running a 64-bit kernel (XLP64 or XLPN32).
59 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
60 the preferred emulator today and we don't need two different ones.
62 The old sibyte / swarm / Broadcom BCM1250 support has been
63 removed from the mips port.
66 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
67 7.0.1. Please see the 20141231 entry below for information about
68 prerequisites and upgrading, if you are not already using clang 3.5.0
72 Remove the timed and netdate programs from the base tree. Setting
73 the time with these deamons has been obsolete for over a decade.
76 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
77 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
78 it produces broken binaries when ifuncs are in use. Users needing
79 GNU ld should install the binutils port or package.
82 The BSD crtbegin and crtend code has been enabled by default. It has
83 had extensive testing on amd64, arm64, and i386. It can be disabled
84 by building a world with -DWITHOUT_BSD_CRTBEGIN.
87 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
88 has been converted to a port (misc/ctm) and will be removed from
89 FreeBSD-13. It is available as a package (ctm) for all supported
93 The default newsyslog.conf(5) file has been changed to only include
94 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
95 the filenames end in '.conf' and do not begin with a '.'.
97 You should check the configuration files in these two directories match
98 this naming convention. You can verify which configuration files are
99 being included using the command:
103 Ports for the DRM modules have been simplified. Now, amd64 users should
104 just install the drm-kmod port. All others should install
107 Graphics hardware that's newer than about 2010 usually works with
108 drm-kmod. For hardware older than 2013, however, some users will need
109 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
110 than 2008 usually only works in drm-legacy-kmod. The graphics team can
111 only commit to hardware made since 2013 due to the complexity of the
112 market and difficulty to test all the older cards effectively. If you
113 have hardware supported by drm-kmod, you are strongly encouraged to use
114 that as you will get better support.
116 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
117 elsewhere, the drm and drm2 modules will be eliminated from the src base
118 soon (with a limited exception for arm). Please update to the package asap
119 and report any issues to x11@freebsd.org.
121 Generally, anybody using the drm*-kmod packages should add
122 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
123 cross-threading surprises, especially with automatic driver
124 loading from X11 startup. These will become the defaults in 13-current
128 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
129 custom kernel and module loading configuration files must be updated
130 accordingly. Moreover, interfaces previous presented as ixlvN to the
131 system are now exposed as iavfN and network configuration files must
132 be adjusted as necessary.
135 OpenSSL has been updated to version 1.1.1. This update included
136 additional various API changes througout the base system. It is
137 important to rebuild third-party software after upgrading. The value
138 of __FreeBSD_version has been bumped accordingly.
141 The legacy DRM modules and drivers have now been added to the loader's
142 module blacklist, in favor of loading them with kld_list in rc.conf(5).
143 The module blacklist may be overridden with the loader.conf(5)
144 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
148 The cam(4) based nda(4) driver will be used over nvd(4) by default on
149 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
150 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
151 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
155 Reproducible build mode is now on by default, in preparation for
156 FreeBSD 12.0. This eliminates build metadata such as the user,
157 host, and time from the kernel (and uname), unless the working tree
158 corresponds to a modified checkout from a version control system.
159 The previous behavior can be obtained by setting the /etc/src.conf
160 knob WITHOUT_REPRODUCIBLE_BUILD.
163 The Yarrow CSPRNG has been removed from the kernel as it has not been
164 supported by its designers since at least 2003. Fortuna has been the
165 default since FreeBSD-11.
168 devctl freeze/thaw have gone into the tree, the rc scripts have been
169 updated to use them and devmatch has been changed. You should update
170 kernel, userland and rc scripts all at the same time.
173 The default interpreter has been switched from 4th to Lua.
174 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
175 interpreter. If you have custom FORTH code you will need to set
176 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
177 src.conf for the build. This will create default hard links between
178 loader and loader_4th instead of loader and loader_lua, the new default.
179 If you are using UEFI it will create the proper hard link to loader.efi.
181 bhyve uses userboot.so. It remains 4th-only until some issues are solved
182 regarding coexisting with multiple versions of FreeBSD are resolved.
185 ls(1) now respects the COLORTERM environment variable used in other
186 systems and software to indicate that a colored terminal is both
187 supported and desired. If ls(1) is suddenly emitting colors, they may
188 be disabled again by either removing the unwanted COLORTERM from your
189 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
190 may not be observed in a future release.
193 The default pager for most commands has been changed to "less". To
194 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
198 The jedec_ts(4) driver has been removed. A superset of its functionality
199 is available in the jedec_dimm(4) driver, and the manpage for that
200 driver includes migration instructions. If you have "device jedec_ts"
201 in your kernel configuration file, it must be removed.
204 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
205 This should have no effect if the kernel is booted via BIOS/legacy boot.
206 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
207 has a buggy firmware that prevents a successful boot due to use of
211 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
212 support has been removed from the tree. These ports were
213 obsolete and/or known to be broken for many years.
216 loader.efi has been augmented to participate more fully in the
217 UEFI boot manager protocol. loader.efi will now look at the
218 BootXXXX environment variable to determine if a specific kernel
219 or root partition was specified. XXXX is derived from BootCurrent.
220 efibootmgr(8) manages these standard UEFI variables.
223 zfsloader's functionality has now been folded into loader.
224 zfsloader is no longer necessary once you've updated your
225 boot blocks. For a transition period, we will install a
226 hardlink for zfsloader to loader to allow a smooth transition
227 until the boot blocks can be updated (hard link because old
228 zfs boot blocks don't understand symlinks).
231 ARM64 now have efifb support, if you want to have serial console
232 on your arm64 board when an screen is connected and the bootloader
233 setup a frambuffer for us to use, just add :
237 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
238 an screen connected as the firmware will setup a framebuffer are that
239 u-boot will expose as an EFI framebuffer.
242 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
243 or take steps to update /etc/passwd before doing installworld on
244 existing systems. Do not skip the "mergemaster -Fp" step before
245 installworld, as described in the update procedures near the bottom
246 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
247 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
248 the ntp config file contain options that change file/dir locations.
249 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
250 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
251 taking steps to ensure that all required files/dirs are accessible
255 Big endian arm support has been removed.
258 The static environment setup in kernel configs is no longer mutually
259 exclusive with the loader(8) environment by default. In order to
260 restore the previous default behavior of disabling the loader(8)
261 environment if a static environment is present, you must specify
262 loader_env.disabled=1 in the static environment.
265 The ABI of syscalls used by management tools like sockstat and
266 netstat has been broken to allow 32-bit binaries to work on
267 64-bit kernels without modification. These programs will need
268 to match the kernel in order to function. External programs may
269 require minor modifications to accommodate a change of type in
270 structures from pointers to 64-bit virtual addresses.
273 On i386 and amd64 atomics are now inlined. Out of tree modules using
274 atomics will need to be rebuilt.
277 The '%I' format in the kern.corefile sysctl limits the number of
278 core files that a process can generate to the number stored in the
279 debug.ncores sysctl. The '%I' format is replaced by the single digit
280 index. Previously, if all indexes were taken the kernel would overwrite
281 only a core file with the highest index in a filename.
282 Currently the system will create a new core file if there is a free
283 index or if all slots are taken it will overwrite the oldest one.
286 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
287 6.0.1. Please see the 20141231 entry below for information about
288 prerequisites and upgrading, if you are not already using clang 3.5.0
292 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
293 needed to be changed to work with it. This change was made with r335763
294 and requires a mergemaster / etcupdate / etc to update the installed file.
297 r334930 changed the interface between the NFS modules, so they all
298 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
301 As of r334391 lld is the default amd64 system linker; it is installed
302 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
306 The kernel / userland interface for devinfo changed, so you'll
307 need a new kernel and userland as a pair for it to work (rebuilding
308 lib/libdevinfo is all that's required). devinfo and devmatch will
309 not work, but everything else will when there's a mismatch.
312 The on-disk format for hwpmc callchain records has changed to include
313 threadid corresponding to a given record. This changes the field offsets
314 and thus requires that libpmcstat be rebuilt before using a kernel
318 The vxge(4) driver has been removed. This driver was introduced into
319 HEAD one week before the Exar left the Ethernet market and is not
320 known to be used. If you have device vxge in your kernel config file
324 The amd64 kernel now requires a ld that supports ifunc to produce a
325 working kernel, either lld or a newer binutils. lld is built by default
326 on amd64, and the 'buildkernel' target uses it automatically. However,
327 it is not the default linker, so building the kernel the traditional
328 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
329 binutils port/package). lld will soon be default, and this requirement
332 NOTE: As of r334391 lld is the default system linker on amd64, and no
333 workaround is necessary.
336 The nxge(4) driver has been removed. This driver was for PCI-X 10g
337 cards made by s2io/Neterion. The company was aquired by Exar and
338 no longer sells or supports Ethernet products. If you have device
339 nxge in your kernel config file it must be removed.
342 The tz database (tzdb) has been updated to 2018e. This version more
343 correctly models time stamps in time zones with negative DST such as
344 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
345 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
346 time zone abbreviations and the tm_isdst flag.
349 The ixgb(4) driver has been removed. This driver was for an early and
350 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
351 quickly shifted to the long lived ixgbe family. If you have device
352 ixgb in your kernel config file it must be removed.
355 The lmc(4) driver has been removed. This was a WAN interface
356 card that was already reportedly rare in 2003, and had an ambiguous
357 license. If you have device lmc in your kernel config file it must
361 Support for Arcnet networks has been removed. If you have device
362 arcnet or device cm in your kernel config file they must be
366 Support for FDDI networks has been removed. If you have device
367 fddi or device fpa in your kernel config file they must be
371 In addition to supporting RFC 3164 formatted messages, the
372 syslogd(8) service is now capable of parsing RFC 5424 formatted
373 log messages. The main benefit of using RFC 5424 is that clients
374 may now send log messages with timestamps containing year numbers,
375 microseconds and time zone offsets.
377 Similarly, the syslog(3) C library function has been altered to
378 send RFC 5424 formatted messages to the local system logging
379 daemon. On systems using syslogd(8), this change should have no
380 negative impact, as long as syslogd(8) and the C library are
381 updated at the same time. On systems using a different system
382 logging daemon, it may be necessary to make configuration
383 adjustments, depending on the software used.
385 When using syslog-ng, add the 'syslog-protocol' flag to local
386 input sources to enable parsing of RFC 5424 formatted messages:
389 unix-dgram("/var/run/log" flags(syslog-protocol));
392 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
393 of the 'imuxsock' module to let messages be processed by the
394 regular RFC 3164/5424 parsing pipeline:
396 module(load="imuxsock" SysSock.UseSpecialParser="off")
398 Do note that these changes only affect communication between local
399 applications and syslogd(8). The format that syslogd(8) uses to
400 store messages on disk or forward messages to other systems
401 remains unchanged. syslogd(8) still uses RFC 3164 for these
402 purposes. Options to customize this behaviour will be added in the
403 future. Utilities that process log files stored in /var/log are
404 thus expected to continue to function as before.
406 __FreeBSD_version has been incremented to 1200061 to denote this
410 Support for token ring networks has been removed. If you
411 have "device token" in your kernel config you should remove
412 it. No device drivers supported token ring.
415 makefs was modified to be able to tag ISO9660 El Torito boot catalog
416 entries as EFI instead of overloading the i386 tag as done previously.
417 The amd64 mkisoimages.sh script used to build amd64 ISO images for
418 release was updated to use this. This may mean that makefs must be
419 updated before "make cdrom" can be run in the release directory. This
420 should be as simple as:
422 $ cd $SRCDIR/usr.sbin/makefs
423 $ make depend all install
426 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
427 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
428 Co-existance for the transition period will come shortly. Booting is a
429 complex environment and test coverage for Lua-enabled loaders has been
430 thin, so it would be prudent to assume it might not work and make
431 provisions for backup boot methods.
434 devmatch functionality has been turned on in devd. It will automatically
435 load drivers for unattached devices. This may cause unexpected drivers to
436 be loaded. Please report any problems to current@ and imp@freebsd.org.
439 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
440 6.0.0. Please see the 20141231 entry below for information about
441 prerequisites and upgrading, if you are not already using clang 3.5.0
445 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
446 This means it is used to link the kernel and userland libraries and
447 executables, but is not yet installed as /usr/bin/ld by default.
449 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
450 WITHOUT_LLD_BOOTSTRAP=yes
453 On i386, pmtimer has been removed. Its functionality has been folded
454 into apm. It was a no-op on ACPI in current for a while now (but was still
455 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
456 from kernel config files.
459 The use of RSS hash from the network card aka flowid has been
460 disabled by default for lagg(4) as it's currently incompatible with
461 the lacp and loadbalance protocols.
463 This can be re-enabled by setting the following in loader.conf:
464 net.link.lagg.default_use_flowid="1"
467 The SW_WATCHDOG option is no longer necessary to enable the
468 hardclock-based software watchdog if no hardware watchdog is
469 configured. As before, SW_WATCHDOG will cause the software
470 watchdog to be enabled even if a hardware watchdog is configured.
473 r326887 fixes the issue described in the 20171214 UPDATING entry.
474 r326888 flips the switch back to building GELI support always.
477 r362593 broke ZFS + GELI support for reasons unknown. However,
478 it also broke ZFS support generally, so GELI has been turned off
479 by default as the lesser evil in r326857. If you boot off ZFS and/or
480 GELI, it might not be a good time to update.
483 PowerPC users must update loader(8) by rebuilding world before
484 installing a new kernel, as the protocol connecting them has
485 changed. Without the update, loader metadata will not be passed
486 successfully to the kernel and users will have to enter their
487 root partition at the kernel mountroot prompt to continue booting.
488 Newer versions of loader can boot old kernels without issue.
491 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
492 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
493 to WITH/OUT_LOADER_GELI.
496 The naive and non-compliant support of posix_fallocate(2) in ZFS
497 has been removed as of r325320. The system call now returns EINVAL
498 when used on a ZFS file. Although the new behavior complies with the
499 standard, some consumers are not prepared to cope with it.
500 One known victim is lld prior to r325420.
503 Building in a FreeBSD src checkout will automatically create object
504 directories now rather than store files in the current directory if
505 'make obj' was not ran. Calling 'make obj' is no longer necessary.
506 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
507 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
511 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
512 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
513 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
514 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
515 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
516 The UNIFIED_OBJDIR option is a transitional feature that will be
517 removed for 12.0 release; please migrate to the new format for any
518 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
519 than hardcoding paths.
522 The native-xtools target no longer installs the files by default to the
523 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
524 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
527 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
528 options are changing from controlling the build if defined / undefined
529 to controlling the build with explicit 'yes' or 'no' values. They will
530 shift to WITH/WITHOUT options to match other options in the system.
533 libstand has turned into a private library for sys/boot use only.
534 It is no longer supported as a public interface outside of sys/boot.
537 The arm port has split armv6 into armv6 and armv7. armv7 is now
538 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
539 and are running a kernel from before r324363, you will need to add
540 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
543 When building multiple kernels using KERNCONF, non-existent KERNCONF
544 files will produce an error and buildkernel will fail. Previously
545 missing KERNCONF files silently failed giving no indication as to
546 why, only to subsequently discover during installkernel that the
547 desired kernel was never built in the first place.
550 The default serial number format for CTL LUNs has changed. This will
551 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
552 or iSCSI clients care about their LUNs' serial numbers. Users who
553 require serial number stability should hardcode serial numbers in
557 For 32-bit arm compiled for hard-float support, soft-floating point
558 binaries now always get their shared libraries from
559 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
560 /usr/libsoft also existed). Only users with a hard-float ld.so, but
561 soft-float everything else should be affected.
564 The geli password typed at boot is now hidden. To restore the previous
565 behavior, see geli(8) for configuration options.
568 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
569 sysctl values. Minor nit, but requires a rebuild of both world/kernel
573 "make check" behavior (made in ^/head@r295380) has been changed to
574 execute from a limited sandbox, as opposed to executing from
578 - The "beforecheck" and "aftercheck" targets are now specified.
579 - ${CHECKDIR} (added in commit noted above) has been removed.
580 - Legacy behavior can be enabled by setting
581 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
583 If the limited sandbox mode is enabled, "make check" will execute
584 "make distribution", then install, execute the tests, and clean up the
585 sandbox if successful.
587 The "make distribution" and "make install" targets are typically run as
588 root to set appropriate permissions and ownership at installation time.
589 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
590 environment if executing "make check" with limited sandbox mode using
591 an unprivileged user.
594 Since the switch to GPT disk labels, fsck for UFS/FFS has been
595 unable to automatically find alternate superblocks. As of r322297,
596 the information needed to find alternate superblocks has been
597 moved to the end of the area reserved for the boot block.
598 Filesystems created with a newfs of this vintage or later
599 will create the recovery information. If you have a filesystem
600 created prior to this change and wish to have a recovery block
601 created for your filesystem, you can do so by running fsck in
602 foreground mode (i.e., do not use the -p or -y options). As it
603 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
604 to which you should answer yes.
607 As of r321665, an NFSv4 server configuration that services
608 Kerberos mounts or clients that do not support the uid/gid in
609 owner/owner_group string capability, must explicitly enable
610 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
611 machine's /etc/rc.conf file.
614 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
615 Please see the 20141231 entry below for information about prerequisites
616 and upgrading, if you are not already using clang 3.5.0 or higher.
619 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
620 r-commands (rlogin, rsh, etc.) to be built with the base system.
623 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
624 a very major ABI incompatible change, so users of FreeBSD/powerpc must
625 be careful when performing source upgrades. It is best to run
626 'make installworld' from an alternate root system, either a live
627 CD/memory stick, or a temporary root partition. Additionally, all ports
628 must be recompiled. powerpc64 is largely unaffected, except in the case
629 of 32-bit compatibility. All 32-bit binaries will be affected.
632 Forward compatibility for the "ino64" project have been committed. This
633 will allow most new binaries to run on older kernels in a limited
634 fashion. This prevents many of the common foot-shooting actions in the
635 upgrade as well as the limited ability to roll back the kernel across
636 the ino64 upgrade. Complicated use cases may not work properly, though
637 enough simpler ones work to allow recovery in most situations.
640 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
641 if you require the GPL compiler.
644 The internal ABI used for communication between the NFS kernel modules
645 was changed by r320085, so __FreeBSD_version was bumped to
646 ensure all the NFS related modules are updated together.
649 The ABI of struct event was changed by extending the data
650 member to 64bit and adding ext fields. For upgrade, same
651 precautions as for the entry 20170523 "ino64" must be
655 The GNU roff toolchain has been removed from base. To render manpages
656 which are not supported by mandoc(1), man(1) can fallback on GNU roff
657 from ports (and recommends to install it).
658 To render roff(7) documents, consider using GNU roff from ports or the
659 heirloom doctools roff toolchain from ports via pkg install groff or
660 via pkg install heirloom-doctools.
663 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
664 smaller runtime footprint builds. This is useful for embedded systems
665 which only require one chipset support.
667 If you load it as a module, make sure this is in /boot/loader.conf:
671 This will load the HAL, all chip/RF backends and if_ath_pci.
672 If you have if_ath_pci in /boot/loader.conf, ensure it is after
673 if_ath or it will not load any HAL chipset support.
675 If you want to selectively load things (eg on ye cheape ARM/MIPS
676 platforms where RAM is at a premium) you should:
679 * load the chip modules in question
680 * load ath_rate, ath_dfs
682 * load if_ath_pci and/or if_ath_ahb depending upon your particular
683 bus bind type - this is where probe/attach is done.
685 For further comments/feedback, poke adrian@ .
688 The "ino64" 64-bit inode project has been committed, which extends
689 a number of types to 64 bits. Upgrading in place requires care and
690 adherence to the documented upgrade procedure.
692 If using a custom kernel configuration ensure that the
693 COMPAT_FREEBSD11 option is included (as during the upgrade the
694 system will be running the ino64 kernel with the existing world).
696 For the safest in-place upgrade begin by removing previous build
697 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
698 full procedure documented below under the heading "To rebuild
699 everything and install it on the current system." Specifically,
700 a reboot is required after installing the new kernel before
704 The NATM framework including the en(4), fatm(4), hatm(4), and
705 patm(4) devices has been removed. Consumers should plan a
706 migration before the end-of-life date for FreeBSD 11.
709 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
710 diff has not been implemented, if those are needed a newer version of
711 GNU diff is available via the diffutils package under the gdiff name.
714 As of r316810 for ipfilter, keep frags is no longer assumed when
715 keep state is specified in a rule. r316810 aligns ipfilter with
716 documentation in man pages separating keep frags from keep state.
717 This allows keep state to be specified without forcing keep frags
718 and allows keep frags to be specified independently of keep state.
719 To maintain previous behaviour, also specify keep frags with
720 keep state (as documented in ipf.conf.5).
723 arm64 builds now use the base system LLD 4.0.0 linker by default,
724 instead of requiring that the aarch64-binutils port or package be
725 installed. To continue using aarch64-binutils, set
726 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
729 The UDP optimization in entry 20160818 that added the sysctl
730 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
731 packets will no longer be treated as L3 broadcast packets.
734 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
735 use any explicitly assigned loopback address available in the jail
736 instead of using the first assigned address of the jail.
739 The ctl.ko module no longer implements the iSCSI target frontend:
740 cfiscsi.ko does instead.
742 If building cfiscsi.ko as a kernel module, the module can be loaded
743 via one of the following methods:
744 - `cfiscsi_load="YES"` in loader.conf(5).
745 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
746 - ctladm(8)/ctld(8), when compiled with iSCSI support
747 (`WITH_ISCSI=yes` in src.conf(5))
749 Please see cfiscsi(4) for more details.
752 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
753 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
754 same source (previously, the dependency of mmcsd.ko on mmc.ko was
755 missing, but mmcsd.ko now will refuse to load if it is incompatible
759 The syntax of ipfw(8) named states was changed to avoid ambiguity.
760 If you have used named states in the firewall rules, you need to modify
761 them after installworld and before rebooting. Now named states must
762 be prefixed with colon.
765 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
766 removed as the userland we provide cannot use them. The KMS version
767 (sys/dev/drm2) supports the same hardware.
770 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
771 Please see the 20141231 entry below for information about prerequisites
772 and upgrading, if you are not already using clang 3.5.0 or higher.
775 The code that provides support for ZFS .zfs/ directory functionality
776 has been reimplemented. It's not possible now to create a snapshot
777 by mkdir under .zfs/snapshot/. That should be the only user visible
781 EISA bus support has been removed. The WITH_EISA option is no longer
785 MCA bus support has been removed.
788 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
789 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
792 The EM_MULTIQUEUE kernel configuration option is deprecated now that
793 the em(4) driver conforms to iflib specifications.
796 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
797 IFLIB. If you have a custom kernel configuration that excludes em(4)
798 but you use igb(4), you need to re-add em(4) to your custom configuration.
801 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
802 Please see the 20141231 entry below for information about prerequisites
803 and upgrading, if you are not already using clang 3.5.0 or higher.
806 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
807 Please see the 20141231 entry below for information about prerequisites
808 and upgrading, if you are not already using clang 3.5.0 or higher.
811 The layout of the pmap structure has changed for powerpc to put the pmap
812 statistics at the front for all CPU variations. libkvm(3) and all tools
813 that link against it need to be recompiled.
816 isl(4) and cyapa(4) drivers now require a new driver,
817 chromebook_platform(4), to work properly on Chromebook-class hardware.
818 On other types of hardware the drivers may need to be configured using
819 device hints. Please see the corresponding manual pages for details.
822 The urtwn(4) driver was merged into rtwn(4) and now consists of
823 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
825 Also, firmware for RTL8188CE was renamed due to possible name
826 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
829 GNU rcs has been removed from base. It is available as packages:
830 - rcs: Latest GPLv3 GNU rcs version.
831 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
835 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
836 modules now requires that the kernel configuration contain the
837 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
840 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
841 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
844 Relocatable object files with the extension of .So have been renamed
845 to use an extension of .pico instead. The purpose of this change is
846 to avoid a name clash with shared libraries on case-insensitive file
847 systems. On those file systems, foo.So is the same file as foo.so.
850 GNU rcs has been turned off by default. It can (temporarily) be built
851 again by adding WITH_RCS knob in src.conf.
852 Otherwise, GNU rcs is available from packages:
853 - rcs: Latest GPLv3 GNU rcs version.
854 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
857 The backup_uses_rcs functionality has been removed from rc.subr.
860 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
861 two separate components, QUEUE_MACRO_DEBUG_TRACE and
862 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
863 QUEUE_MACRO_DEBUG behavior.
866 r304787 changed some ioctl interfaces between the iSCSI userspace
867 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
868 rebuilt to work with new kernels. __FreeBSD_version has been bumped
872 The UDP receive code has been updated to only treat incoming UDP
873 packets that were addressed to an L2 broadcast address as L3
874 broadcast packets. It is not expected that this will affect any
875 standards-conforming UDP application. The new behaviour can be
876 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
880 Remove the openbsd_poll system call.
881 __FreeBSD_version has been bumped because of this.
884 The stable/11 branch has been created from head@r302406.
887 The libc stub for the pipe(2) system call has been replaced with
888 a wrapper that calls the pipe2(2) system call and the pipe(2)
889 system call is now only implemented by the kernels that include
890 "options COMPAT_FREEBSD10" in their config file (this is the
891 default). Users should ensure that this option is enabled in
892 their kernel or upgrade userspace to r302092 before upgrading their
896 CAM will now strip leading spaces from SCSI disks' serial numbers.
897 This will affect users who create UFS filesystems on SCSI disks using
898 those disk's diskid device nodes. For example, if /etc/fstab
899 previously contained a line like
900 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
901 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
902 transforms like gmirror may also be affected. ZFS users should
906 The bitstring(3) API has been updated with new functionality and
907 improved performance. But it is binary-incompatible with the old API.
908 Objects built with the new headers may not be linked against objects
909 built with the old headers.
912 The brk and sbrk functions have been removed from libc on arm64.
913 Binutils from ports has been updated to not link to these
914 functions and should be updated to the latest version before
915 installing a new libc.
918 The armv6 port now defaults to hard float ABI. Limited support
919 for running both hardfloat and soft float on the same system
920 is available using the libraries installed with -DWITH_LIBSOFT.
921 This has only been tested as an upgrade path for installworld
922 and packages may fail or need manual intervention to run. New
923 packages will be needed.
925 To update an existing self-hosted armv6hf system, you must add
926 TARGET_ARCH=armv6 on the make command line for both the build
927 and the install steps.
930 Kernel modules compiled outside of a kernel build now default to
931 installing to /boot/modules instead of /boot/kernel. Many kernel
932 modules built this way (such as those in ports) already overrode
933 KMODDIR explicitly to install into /boot/modules. However,
934 manually building and installing a module from /sys/modules will
935 now install to /boot/modules instead of /boot/kernel.
938 The CAM I/O scheduler has been committed to the kernel. There should be
939 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
940 list of known rogues that claim support for this but actually corrupt
941 data is believed to be complete, be on the lookout for data
942 corruption. The known rogue list is believed to be complete:
944 o Crucial MX100, M550 drives with MU01 firmware.
945 o Micron M510 and M550 drives with MU01 firmware.
946 o Micron M500 prior to MU07 firmware
947 o Samsung 830, 840, and 850 all firmwares
948 o FCCT M500 all firmwares
950 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
951 with working NCQ TRIM. For Micron branded drives, see your sales rep for
952 updated firmware. Black listed drives will work correctly because these
953 drives work correctly so long as no NCQ TRIMs are sent to them. Given
954 this list is the same as found in Linux, it's believed there are no
955 other rogues in the market place. All other models from the above
958 To be safe, if you are at all concerned, you can quirk each of your
959 drives to prevent NCQ from being sent by setting:
960 kern.cam.ada.X.quirks="0x2"
961 in loader.conf. If the drive requires the 4k sector quirk, set the
965 The FAST_DEPEND build option has been removed and its functionality is
966 now the one true way. The old mkdep(1) style of 'make depend' has
967 been removed. See 20160311 for further details.
970 Resource range types have grown from unsigned long to uintmax_t. All
971 drivers, and anything using libdevinfo, need to be recompiled.
974 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
975 builds. It no longer runs mkdep(1) during 'make depend', and the
976 'make depend' stage can safely be skipped now as it is auto ran
977 when building 'make all' and will generate all SRCS and DPSRCS before
978 building anything else. Dependencies are gathered at compile time with
979 -MF flags kept in separate .depend files per object file. Users should
980 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
984 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
985 kernel modules. Therefore, if you load any kernel modules at boot time,
986 please install the boot loaders after you install the kernel, but before
990 make buildkernel KERNCONF=YOUR_KERNEL_HERE
991 make installkernel KERNCONF=YOUR_KERNEL_HERE
992 make -C sys/boot install
993 <reboot in single user>
995 Then follow the usual steps, described in the General Notes section,
999 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1000 see the 20141231 entry below for information about prerequisites and
1001 upgrading, if you are not already using clang 3.5.0 or higher.
1004 The AIO subsystem is now a standard part of the kernel. The
1005 VFS_AIO kernel option and aio.ko kernel module have been removed.
1006 Due to stability concerns, asynchronous I/O requests are only
1007 permitted on sockets and raw disks by default. To enable
1008 asynchronous I/O requests on all file types, set the
1009 vfs.aio.enable_unsafe sysctl to a non-zero value.
1012 The ELF object manipulation tool objcopy is now provided by the
1013 ELF Tool Chain project rather than by GNU binutils. It should be a
1014 drop-in replacement, with the addition of arm64 support. The
1015 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1016 to obtain the GNU version if necessary.
1019 Building ZFS pools on top of zvols is prohibited by default. That
1020 feature has never worked safely; it's always been prone to deadlocks.
1021 Using a zvol as the backing store for a VM guest's virtual disk will
1022 still work, even if the guest is using ZFS. Legacy behavior can be
1023 restored by setting vfs.zfs.vol.recursive=1.
1026 The NONE and HPN patches has been removed from OpenSSH. They are
1027 still available in the security/openssh-portable port.
1030 With the addition of ypldap(8), a new _ypldap user is now required
1031 during installworld. "mergemaster -p" can be used to add the user
1032 prior to installworld, as documented in the handbook.
1035 The tftp loader (pxeboot) now uses the option root-path directive. As a
1036 consequence it no longer looks for a pxeboot.4th file on the tftp
1037 server. Instead it uses the regular /boot infrastructure as with the
1041 The code to start recording plug and play data into the modules has
1042 been committed. While the old tools will properly build a new kernel,
1043 a number of warnings about "unknown metadata record 4" will be produced
1044 for an older kldxref. To avoid such warnings, make sure to rebuild
1045 the kernel toolchain (or world). Make sure that you have r292078 or
1046 later when trying to build 292077 or later before rebuilding.
1049 Debug data files are now built by default with 'make buildworld' and
1050 installed with 'make installworld'. This facilitates debugging but
1051 requires more disk space both during the build and for the installed
1052 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1056 r291527 changed the internal interface between the nfsd.ko and
1057 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1058 __FreeBSD_version has been bumped because of this.
1061 Add support for unicode collation strings leads to a change of
1062 order of files listed by ls(1) for example. To get back to the old
1063 behaviour, set LC_COLLATE environment variable to "C".
1065 Databases administrators will need to reindex their databases given
1066 collation results will be different.
1068 Due to a bug in install(1) it is recommended to remove the ancient
1069 locales before running make installworld.
1071 rm -rf /usr/share/locale/*
1074 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1075 libcrypto.so.7 or libssl.so.7 must be recompiled.
1078 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1079 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1080 should be replaced with isp_2400 and isp_2500 modules respectively.
1083 The build previously allowed using 'make -n' to not recurse into
1084 sub-directories while showing what commands would be executed, and
1085 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1086 and 'make -N' will not.
1089 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1090 and etcupdate will now use this file. A custom sendmail.cf is now
1091 updated via this mechanism rather than via installworld. If you had
1092 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1093 want to remove the exclusion or change it to "always install".
1094 /etc/mail/sendmail.cf is now managed the same way regardless of
1095 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1096 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1099 Compatibility shims for legacy ATA device names have been removed.
1100 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1101 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1102 environment variables, /dev/ad* and /dev/ar* symbolic links.
1105 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1106 Please see the 20141231 entry below for information about prerequisites
1107 and upgrading, if you are not already using clang 3.5.0 or higher.
1110 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1111 and renamed from .symbols to .debug. This reduces the size requirements
1112 on the boot partition or file system and provides consistency with
1113 userland debug files.
1115 When using the supported kernel installation method the
1116 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1117 as is done with /boot/kernel.
1119 Developers wishing to maintain the historical behavior of installing
1120 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1123 The wireless drivers had undergone changes that remove the 'parent
1124 interface' from the ifconfig -l output. The rc.d network scripts
1125 used to check presence of a parent interface in the list, so old
1126 scripts would fail to start wireless networking. Thus, etcupdate(3)
1127 or mergemaster(8) run is required after kernel update, to update your
1128 rc.d scripts in /etc.
1131 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1132 These configurations are now automatically interpreted as
1133 'scrub fragment reassemble'.
1136 Kernel-loadable modules for the random(4) device are back. To use
1137 them, the kernel must have
1140 options RANDOM_LOADABLE
1142 kldload(8) can then be used to load random_fortuna.ko
1143 or random_yarrow.ko. Please note that due to the indirect
1144 function calls that the loadable modules need to provide,
1145 the build-in variants will be slightly more efficient.
1147 The random(4) kernel option RANDOM_DUMMY has been retired due to
1148 unpopularity. It was not all that useful anyway.
1151 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1152 Control over building the ELF Tool Chain tools is now provided by
1153 the WITHOUT_TOOLCHAIN knob.
1156 The polarity of Pulse Per Second (PPS) capture events with the
1157 uart(4) driver has been corrected. Prior to this change the PPS
1158 "assert" event corresponded to the trailing edge of a positive PPS
1159 pulse and the "clear" event was the leading edge of the next pulse.
1161 As the width of a PPS pulse in a typical GPS receiver is on the
1162 order of 1 millisecond, most users will not notice any significant
1163 difference with this change.
1165 Anyone who has compensated for the historical polarity reversal by
1166 configuring a negative offset equal to the pulse width will need to
1167 remove that workaround.
1170 The default group assigned to /dev/dri entries has been changed
1171 from 'wheel' to 'video' with the id of '44'. If you want to have
1172 access to the dri devices please add yourself to the video group
1175 # pw groupmod video -m $USER
1178 The menu.rc and loader.rc files will now be replaced during
1179 upgrades. Please migrate local changes to menu.rc.local and
1180 loader.rc.local instead.
1183 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1184 strings and strip have been removed. The src.conf(5) knob
1185 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1188 As ZFS requires more kernel stack pages than is the default on some
1189 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1190 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1192 Please consider using 'options KSTACK_PAGES=X' where X is greater
1193 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1196 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1197 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1198 default, i.e., they will not contain "::". For example, instead
1199 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1200 to have a more specific match, such as different map entries for
1201 IPv6:0:0 vs IPv6:0. This change requires that configuration
1202 data (including maps, files, classes, custom ruleset, etc.) must
1203 use the same format, so make certain such configuration data is
1204 upgrading. As a very simple check search for patterns like
1205 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1206 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1207 the cf option UseCompressedIPv6Addresses.
1210 The default kernel entropy-processing algorithm is now
1211 Fortuna, replacing Yarrow.
1213 Assuming you have 'device random' in your kernel config
1214 file, the configurations allow a kernel option to override
1215 this default. You may choose *ONE* of:
1217 options RANDOM_YARROW # Legacy /dev/random algorithm.
1218 options RANDOM_DUMMY # Blocking-only driver.
1220 If you have neither, you get Fortuna. For most people,
1221 read no further, Fortuna will give a /dev/random that works
1222 like it always used to, and the difference will be irrelevant.
1224 If you remove 'device random', you get *NO* kernel-processed
1225 entropy at all. This may be acceptable to folks building
1226 embedded systems, but has complications. Carry on reading,
1227 and it is assumed you know what you need.
1229 *PLEASE* read random(4) and random(9) if you are in the
1230 habit of tweaking kernel configs, and/or if you are a member
1231 of the embedded community, wanting specific and not-usual
1232 behaviour from your security subsystems.
1234 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1235 random', you will NOT have a functioning /dev/random, and
1236 many cryptographic features will not work, including SSH.
1237 You may also find strange behaviour from the random(3) set
1238 of library functions, in particular sranddev(3), srandomdev(3)
1239 and arc4random(3). The reason for this is that the KERN_ARND
1240 sysctl only returns entropy if it thinks it has some to
1241 share, and with RANDOM_DUMMY or no 'device random' this
1245 An additional fix for the issue described in the 20150614 sendmail
1246 entry below has been committed in revision 284717.
1249 FreeBSD's old make (fmake) has been removed from the system. It is
1250 available as the devel/fmake port or via pkg install fmake.
1253 The fix for the issue described in the 20150614 sendmail entry
1254 below has been committed in revision 284436. The work
1255 around described in that entry is no longer needed unless the
1256 default setting is overridden by a confDH_PARAMETERS configuration
1257 setting of '5' or pointing to a 512 bit DH parameter file.
1260 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1261 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1262 and devel/kyua to version 0.20+ and adjust any calling code to work
1263 with Kyuafile and kyua.
1266 The import of openssl to address the FreeBSD-SA-15:10.openssl
1267 security advisory includes a change which rejects handshakes
1268 with DH parameters below 768 bits. sendmail releases prior
1269 to 8.15.2 (not yet released), defaulted to a 512 bit
1270 DH parameter setting for client connections. To work around
1271 this interoperability, sendmail can be configured to use a
1272 2048 bit DH parameter by:
1274 1. Edit /etc/mail/`hostname`.mc
1275 2. If a setting for confDH_PARAMETERS does not exist or
1276 exists and is set to a string beginning with '5',
1277 replace it with '2'.
1278 3. If a setting for confDH_PARAMETERS exists and is set to
1279 a file path, create a new file with:
1280 openssl dhparam -out /path/to/file 2048
1281 4. Rebuild the .cf file:
1282 cd /etc/mail/; make; make install
1283 5. Restart sendmail:
1284 cd /etc/mail/; make restart
1286 A sendmail patch is coming, at which time this file will be
1290 Generation of legacy formatted entries have been disabled by default
1291 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1292 entries were converted to use the new format by default when the new,
1293 machine independent format have been added and supported since FreeBSD
1296 Please see the pwd_mkdb(8) manual page for further details.
1299 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1300 20141231 entry below for information about prerequisites and upgrading,
1301 if you are not already using 3.5.0 or higher.
1304 TI platform code switched to using vendor DTS files and this update
1305 may break existing systems running on Beaglebone, Beaglebone Black,
1308 - dtb files should be regenerated/reinstalled. Filenames are the
1309 same but content is different now
1310 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1311 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1312 addressing scheme is now pin 25 on /dev/gpioc3.
1313 - Pandaboard: /etc/ttys should be updated, serial console device is
1314 now /dev/ttyu2, not /dev/ttyu0
1317 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1318 If you need the GNU extension from groff soelim(1), install groff
1319 from package: pkg install groff, or via ports: textproc/groff.
1322 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1323 defined in symlink(7); previously symlinks were silently ignored.
1326 The const qualifier has been removed from iconv(3) to comply with
1327 POSIX. The ports tree is aware of this from r384038 onwards.
1330 Libraries specified by LIBADD in Makefiles must have a corresponding
1331 DPADD_<lib> variable to ensure correct dependencies. This is now
1332 enforced in src.libnames.mk.
1335 From legacy ata(4) driver was removed support for SATA controllers
1336 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1337 Kernel modules ataahci and ataadaptec were removed completely,
1338 replaced by ahci and mvs modules respectively.
1341 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1342 the 20141231 entry below for information about prerequisites and
1343 upgrading, if you are not already using 3.5.0 or higher.
1346 The 32-bit PowerPC kernel has been changed to a position-independent
1347 executable. This can only be booted with a version of loader(8)
1348 newer than January 31, 2015, so make sure to update both world and
1349 kernel before rebooting.
1352 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1353 but before r278950, the RNG was not seeded properly. Immediately
1354 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1355 ssh keys or openssl keys) that were generated w/ a kernel from that
1356 range. This does not affect programs that directly used /dev/random
1357 or /dev/urandom. All userland uses of arc4random(3) are affected.
1360 The autofs(4) ABI was changed in order to restore binary compatibility
1361 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1362 with the new kernel.
1365 The powerpc64 kernel has been changed to a position-independent
1366 executable. This can only be booted with a new version of loader(8),
1367 so make sure to update both world and kernel before rebooting.
1370 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1371 only release, no new features have been added. Please see the 20141231
1372 entry below for information about prerequisites and upgrading, if you
1373 are not already using 3.5.0.
1376 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1377 taken from the ELF Tool Chain project rather than GNU binutils. They
1378 should be drop-in replacements, with the addition of arm64 support.
1379 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1380 binutils tools, if necessary. See 20150805 for updated information.
1383 The default Unbound configuration now enables remote control
1384 using a local socket. Users who have already enabled the
1385 local_unbound service should regenerate their configuration
1386 by running "service local_unbound setup" as root.
1389 The GNU texinfo and GNU info pages have been removed.
1390 To be able to view GNU info pages please install texinfo from ports.
1393 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1395 As of this release, a prerequisite for building clang, llvm and lldb is
1396 a C++11 capable compiler and C++11 standard library. This means that to
1397 be able to successfully build the cross-tools stage of buildworld, with
1398 clang as the bootstrap compiler, your system compiler or cross compiler
1399 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1400 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1403 On any standard FreeBSD 10.x or 11.x installation, where clang and
1404 libc++ are on by default (that is, on x86 or arm), this should work out
1407 On 9.x installations where clang is enabled by default, e.g. on x86 and
1408 powerpc, libc++ will not be enabled by default, so libc++ should be
1409 built (with clang) and installed first. If both clang and libc++ are
1410 missing, build clang first, then use it to build libc++.
1412 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1413 the instructions for 9.x above.
1415 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1416 default, and do not build clang.
1418 Many embedded systems are resource constrained, and will not be able to
1419 build clang in a reasonable time, or in some cases at all. In those
1420 cases, cross building bootable systems on amd64 is a workaround.
1422 This new version of clang introduces a number of new warnings, of which
1423 the following are most likely to appear:
1427 This warns in two cases, for both C and C++:
1428 * When the code is trying to take the absolute value of an unsigned
1429 quantity, which is effectively a no-op, and almost never what was
1430 intended. The code should be fixed, if at all possible. If you are
1431 sure that the unsigned quantity can be safely cast to signed, without
1432 loss of information or undefined behavior, you can add an explicit
1433 cast, or disable the warning.
1435 * When the code is trying to take an absolute value, but the called
1436 abs() variant is for the wrong type, which can lead to truncation.
1437 If you want to disable the warning instead of fixing the code, please
1438 make sure that truncation will not occur, or it might lead to unwanted
1441 -Wtautological-undefined-compare and
1442 -Wundefined-bool-conversion
1444 These warn when C++ code is trying to compare 'this' against NULL, while
1445 'this' should never be NULL in well-defined C++ code. However, there is
1446 some legacy (pre C++11) code out there, which actively abuses this
1447 feature, which was less strictly defined in previous C++ versions.
1449 Squid and openjdk do this, for example. The warning can be turned off
1450 for C++98 and earlier, but compiling the code in C++11 mode might result
1451 in unexpected behavior; for example, the parts of the program that are
1452 unreachable could be optimized away.
1455 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1456 kernel sources have been removed. The .h files remain, since some
1457 utilities include them. This will need to be fixed later.
1458 If "mount -t oldnfs ..." is attempted, it will fail.
1459 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1460 the utilities will report errors.
1463 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1464 directories to top level SUBDIR variable when their parent
1465 directory is included in LOCAL_DIRS. Users with build systems with
1466 such hierarchies and without SUBDIR entries in the parent
1467 directory Makefiles should add them or add the directories to
1471 faith(4) and faithd(8) have been removed from the base system. Faith
1472 has been obsolete for a very long time.
1475 vt(4), the new console driver, is enabled by default. It brings
1476 support for Unicode and double-width characters, as well as
1477 support for UEFI and integration with the KMS kernel video
1480 You may need to update your console settings in /etc/rc.conf,
1481 most probably the keymap. During boot, /etc/rc.d/syscons will
1482 indicate what you need to do.
1484 vt(4) still has issues and lacks some features compared to
1485 syscons(4). See the wiki for up-to-date information:
1486 https://wiki.freebsd.org/Newcons
1488 If you want to keep using syscons(4), you can do so by adding
1489 the following line to /boot/loader.conf:
1493 pjdfstest has been integrated into kyua as an opt-in test suite.
1494 Please see share/doc/pjdfstest/README for more details on how to
1498 gperf has been removed from the base system for architectures
1499 that use clang. Ports that require gperf will obtain it from the
1503 pjdfstest has been moved from tools/regression/pjdfstest to
1507 At svn r271982, The default linux compat kernel ABI has been adjusted
1508 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1509 update. If you wish to continue using the linux-f10 compat ports,
1510 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1511 encouraged to update their linux-compat packages to linux-c6 during
1512 their next update cycle.
1515 The ofwfb driver, used to provide a graphics console on PowerPC when
1516 using vt(4), no longer allows mmap() of all physical memory. This
1517 will prevent Xorg on PowerPC with some ATI graphics cards from
1518 initializing properly unless x11-servers/xorg-server is updated to
1522 The xdev targets have been converted to using TARGET and
1523 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1526 The default unbound configuration has been modified to address
1527 issues with reverse lookups on networks that use private
1528 address ranges. If you use the local_unbound service, run
1529 "service local_unbound setup" as root to regenerate your
1530 configuration, then "service local_unbound reload" to load the
1534 The GNU texinfo and GNU info pages are not built and installed
1535 anymore, WITH_INFO knob has been added to allow to built and install
1537 UPDATE: see 20150102 entry on texinfo's removal
1540 The GNU readline library is now an INTERNALLIB - that is, it is
1541 statically linked into consumers (GDB and variants) in the base
1542 system, and the shared library is no longer installed. The
1543 devel/readline port is available for third party software that
1547 The Itanium architecture (ia64) has been removed from the list of
1548 known architectures. This is the first step in the removal of the
1552 Commit r268115 has added NFSv4.1 server support, merged from
1553 projects/nfsv4.1-server. Since this includes changes to the
1554 internal interfaces between the NFS related modules, a full
1555 build of the kernel and modules will be necessary.
1556 __FreeBSD_version has been bumped.
1559 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1560 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1561 which differs from the behaviour controlled by this knob.)
1564 Maximal length of the serial number in CTL was increased from 16 to
1565 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1566 and ctld, need to be rebuilt to work with a new kernel.
1569 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1570 1 respectively to match the upstream numbers. They were out of
1571 sync because, when they were originally added to FreeBSD, the
1572 upstream versions were not respected. These libraries are private
1573 and not yet built by default, so renumbering them should be a
1574 non-issue. However, unclean source trees will yield broken test
1575 programs once the operator executes "make delete-old-libs" after a
1576 "make installworld".
1578 Additionally, the atf-sh binary was made private by moving it into
1579 /usr/libexec/. Already-built shell test programs will keep the
1580 path to the old binary so they will break after "make delete-old"
1583 If you are using WITH_TESTS=yes (not the default), wipe the object
1584 tree and rebuild from scratch to prevent spurious test failures.
1585 This is only needed once: the misnumbered libraries and misplaced
1586 binaries have been added to OptionalObsoleteFiles.inc so they will
1587 be removed during a clean upgrade.
1590 Clang and llvm have been upgraded to 3.4.1 release.
1593 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1594 be removed to avoid issues in the future (and has been added to
1598 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1599 past, it affected all builds that used the bsd.*.mk files. The old
1600 behavior was a bug, but people may have relied upon it. To get this
1601 behavior back, you can .include /etc/src.conf from /etc/make.conf
1602 (which is still global and isn't changed). This also changes the
1603 behavior of incremental builds inside the tree of individual
1604 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1605 Although this has survived make universe and some upgrade scenarios,
1606 other upgrade scenarios may have broken. At least one form of
1607 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1608 as well... In cases where MAKESYSPATH isn't working with this
1609 setting, you'll need to set it to the full path to your tree.
1611 One side effect of all this cleaning up is that bsd.compiler.mk
1612 is no longer implicitly included by bsd.own.mk. If you wish to
1613 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1617 The lindev device has been removed since /dev/full has been made a
1618 standard device. __FreeBSD_version has been bumped.
1621 The knob WITHOUT_VI was added to the base system, which controls
1622 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1623 in order to reorder files share/termcap and didn't build ex(1) as a
1624 build tool, so building/installing with WITH_VI is highly advised for
1625 build hosts for older releases.
1627 This issue has been fixed in stable/9 and stable/10 in r277022 and
1628 r276991, respectively.
1631 The YES_HESIOD knob has been removed. It has been obsolete for
1632 a decade. Please move to using WITH_HESIOD instead or your builds
1633 will silently lack HESIOD.
1636 The uart(4) driver has been changed with respect to its handling
1637 of the low-level console. Previously the uart(4) driver prevented
1638 any process from changing the baudrate or the CLOCAL and HUPCL
1639 control flags. By removing the restrictions, operators can make
1640 changes to the serial console port without having to reboot.
1641 However, when getty(8) is started on the serial device that is
1642 associated with the low-level console, a misconfigured terminal
1643 line in /etc/ttys will now have a real impact.
1644 Before upgrading the kernel, make sure that /etc/ttys has the
1645 serial console device configured as 3wire without baudrate to
1646 preserve the previous behaviour. E.g:
1647 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1650 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1651 to improve performance. To re-enable it, if needed, run rpcbind
1652 with command line option -W.
1655 Switched back to the GPL dtc compiler due to updates in the upstream
1656 dts files not being supported by the BSDL dtc compiler. You will need
1657 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1658 may result while building dtb files during a kernel build if you fail
1659 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1662 Clang and llvm have been upgraded to 3.4 release.
1665 The nve(4) driver has been removed. Please use the nfe(4) driver
1666 for NVIDIA nForce MCP Ethernet adapters instead.
1669 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1670 This could cause certain C++ applications using shared libraries built
1671 against the previous version of libc++ to crash. The incompatibility
1672 has now been fixed, but any C++ applications or shared libraries built
1673 between r261283 and r261801 should be recompiled.
1676 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1677 capability mode support. Please note that enabling the feature in
1678 kernel is still highly recommended.
1681 OpenSSH is now built with sandbox support, and will use sandbox as
1682 the default privilege separation method. This requires Capsicum
1683 capability mode support in kernel.
1686 The libelf and libdwarf libraries have been updated to newer
1687 versions from upstream. Shared library version numbers for
1688 these two libraries were bumped. Any ports or binaries
1689 requiring these two libraries should be recompiled.
1690 __FreeBSD_version is bumped to 1100006.
1693 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1694 instead of providing an explicit one, this would prevent such
1695 Makefile from providing its own Kyuafile in the future during
1696 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1697 intervention is needed to clean an objdir if you use NO_CLEAN:
1698 # find /usr/obj -name Kyuafile | xargs rm -f
1701 The behavior of gss_pseudo_random() for the krb5 mechanism
1702 has changed, for applications requesting a longer random string
1703 than produced by the underlying enctype's pseudo-random() function.
1704 In particular, the random string produced from a session key of
1705 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1706 be different at the 17th octet and later, after this change.
1707 The counter used in the PRF+ construction is now encoded as a
1708 big-endian integer in accordance with RFC 4402.
1709 __FreeBSD_version is bumped to 1100004.
1712 The WITHOUT_ATF build knob has been removed and its functionality
1713 has been subsumed into the more generic WITHOUT_TESTS. If you were
1714 using the former to disable the build of the ATF libraries, you
1715 should change your settings to use the latter.
1718 The default version of mtree is nmtree which is obtained from
1719 NetBSD. The output is generally the same, but may vary
1720 slightly. If you found you need identical output adding
1721 "-F freebsd9" to the command line should do the trick. For the
1722 time being, the old mtree is available as fmtree.
1725 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1726 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1727 1.1.4_8 and verify bsdyml not linked in, before running "make
1729 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1731 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1734 The stable/10 branch has been created in subversion from head
1741 Avoid using make -j when upgrading. While generally safe, there are
1742 sometimes problems using -j to upgrade. If your upgrade fails with
1743 -j, please try again without -j. From time to time in the past there
1744 have been problems using -j with buildworld and/or installworld. This
1745 is especially true when upgrading between "distant" versions (eg one
1746 that cross a major release boundary or several minor releases, or when
1747 several months have passed on the -current branch).
1749 Sometimes, obscure build problems are the result of environment
1750 poisoning. This can happen because the make utility reads its
1751 environment when searching for values for global variables. To run
1752 your build attempts in an "environmental clean room", prefix all make
1753 commands with 'env -i '. See the env(1) manual page for more details.
1755 When upgrading from one major version to another it is generally best to
1756 upgrade to the latest code in the currently installed branch first, then
1757 do an upgrade to the new branch. This is the best-tested upgrade path,
1758 and has the highest probability of being successful. Please try this
1759 approach if you encounter problems with a major version upgrade. Since
1760 the stable 4.x branch point, one has generally been able to upgrade from
1761 anywhere in the most recent stable branch to head / current (or even the
1762 last couple of stable branches). See the top of this file when there's
1765 When upgrading a live system, having a root shell around before
1766 installing anything can help undo problems. Not having a root shell
1767 around can lead to problems if pam has changed too much from your
1768 starting point to allow continued authentication after the upgrade.
1770 This file should be read as a log of events. When a later event changes
1771 information of a prior event, the prior event should not be deleted.
1772 Instead, a pointer to the entry with the new information should be
1773 placed in the old entry. Readers of this file should also sanity check
1774 older entries before relying on them blindly. Authors of new entries
1775 should write them with this in mind.
1779 When upgrading the boot ZFS pool to a new version, always follow
1782 1.) recompile and reinstall the ZFS boot loader and boot block
1783 (this is part of "make buildworld" and "make installworld")
1785 2.) update the ZFS boot block on your boot drive
1787 The following example updates the ZFS boot block on the first
1788 partition (freebsd-boot) of a GPT partitioned drive ada0:
1789 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1791 Non-boot pools do not need these updates.
1795 If you are updating from a prior version of FreeBSD (even one just
1796 a few days old), you should follow this procedure. It is the most
1797 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1799 make kernel-toolchain
1800 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1801 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1803 To test a kernel once
1804 ---------------------
1805 If you just want to boot a kernel once (because you are not sure
1806 if it works, or if you want to boot a known bad kernel to provide
1807 debugging information) run
1808 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1809 nextboot -k testkernel
1811 To rebuild everything and install it on the current system.
1812 -----------------------------------------------------------
1813 # Note: sometimes if you are running current you gotta do more than
1814 # is listed here if you are upgrading from a really old current.
1816 <make sure you have good level 0 dumps>
1818 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1819 make installkernel KERNCONF=YOUR_KERNEL_HERE
1821 <reboot in single user> [3]
1828 To cross-install current onto a separate partition
1829 --------------------------------------------------
1830 # In this approach we use a separate partition to hold
1831 # current's root, 'usr', and 'var' directories. A partition
1832 # holding "/", "/usr" and "/var" should be about 2GB in
1835 <make sure you have good level 0 dumps>
1838 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1839 <maybe newfs current's root partition>
1840 <mount current's root partition on directory ${CURRENT_ROOT}>
1841 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1842 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1843 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1844 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1845 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1846 <reboot into current>
1847 <do a "native" rebuild/install as described in the previous section>
1848 <maybe install compatibility libraries from ports/misc/compat*>
1852 To upgrade in-place from stable to current
1853 ----------------------------------------------
1854 <make sure you have good level 0 dumps>
1856 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1857 make installkernel KERNCONF=YOUR_KERNEL_HERE
1859 <reboot in single user> [3]
1866 Make sure that you've read the UPDATING file to understand the
1867 tweaks to various things you need. At this point in the life
1868 cycle of current, things change often and you are on your own
1869 to cope. The defaults can also change, so please read ALL of
1870 the UPDATING entries.
1872 Also, if you are tracking -current, you must be subscribed to
1873 freebsd-current@freebsd.org. Make sure that before you update
1874 your sources that you have read and understood all the recent
1875 messages there. If in doubt, please track -stable which has
1876 much fewer pitfalls.
1878 [1] If you have third party modules, such as vmware, you
1879 should disable them at this point so they don't crash your
1882 [3] From the bootblocks, boot -s, and then do
1887 adjkerntz -i # if CMOS is wall time
1888 Also, when doing a major release upgrade, it is required that
1889 you boot into single user mode to do the installworld.
1891 [4] Note: This step is non-optional. Failure to do this step
1892 can result in a significant reduction in the functionality of the
1893 system. Attempting to do it by hand is not recommended and those
1894 that pursue this avenue should read this file carefully, as well
1895 as the archives of freebsd-current and freebsd-hackers mailing lists
1896 for potential gotchas. The -U option is also useful to consider.
1897 See mergemaster(8) for more information.
1899 [5] Usually this step is a no-op. However, from time to time
1900 you may need to do this if you get unknown user in the following
1901 step. It never hurts to do it all the time. You may need to
1902 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1903 install) after the buildworld before this step if you last updated
1904 from current before 20130425 or from -stable before 20130430.
1906 [6] This only deletes old files and directories. Old libraries
1907 can be deleted by "make delete-old-libs", but you have to make
1908 sure that no program is using those libraries anymore.
1910 [8] The new kernel must be able to run existing binaries used by
1911 an installworld. When upgrading across major versions, the new
1912 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1913 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1914 binaries). Failure to do so may leave you with a system that is
1915 hard to boot to recover. A GENERIC kernel will include suitable
1916 compatibility options to run binaries from older branches.
1918 Make sure that you merge any new devices from GENERIC since the
1919 last time you updated your kernel config file.
1921 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1922 "?=" instead of the "=" assignment operator, so that buildworld can
1923 override the CPUTYPE if it needs to.
1925 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1926 not on the command line, or in /etc/make.conf. buildworld will
1927 warn if it is improperly defined.
1930 This file contains a list, in reverse chronological order, of major
1931 breakages in tracking -current. It is not guaranteed to be a complete
1932 list of such breakages, and only contains entries since September 23, 2011.
1933 If you need to see UPDATING entries from before that date, you will need
1934 to fetch an UPDATING file from an older FreeBSD release.
1936 Copyright information:
1938 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1940 Redistribution, publication, translation and use, with or without
1941 modification, in full or in part, in any form or format of this
1942 document are permitted without further permission from the author.
1944 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1945 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1946 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1947 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1948 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1949 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1950 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1951 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1952 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1953 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1954 POSSIBILITY OF SUCH DAMAGE.
1956 Contact Warner Losh if you have any questions about your use of