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 20190619 p6 FreeBSD-EN-19:11.net
22 Fix incorrect locking in networking stack [EN-19:11.net]
24 Add ability to limit split map entries to prevent resource exhaustion
25 in non-default RACK TCP stack [SA-19:08.rack]
27 20190515 p5 FreeBSD-SA-19:07.mds [revised]
29 Fixed error in patch causing panic on i386 architecture. [SA-19:07.mds]
32 20190514 p4 FreeBSD-EN-19:08.tzdata
33 FreeBSD-EN-19:09.xinstall
41 Import tzdata 2019a. [EN-19:08.tzdata]
43 Fix install with partially matching relative paths. [EN-19:09.xinstall]
45 Fix filename validation in scp. [EN-19:10.scp]
47 Fix multiple vulnerabilities in hostapd/wpa_supplicant. [SA-19:03.wpa]
49 Fix authenticated denial of service in ntpd. [SA-19:04.ntp]
51 Fix IPv6 fragment reassembly in pf. [SA-19:05.pf]
53 Fix ICMP/ICMP6 packet filter bypass in pf. [SA-19:06.pf]
55 Add mitigations for Microarchitectural Data Sampling. [SA-19:07.mds]
58 20190205: p3 FreeBSD-SA-19:01.syscall
60 FreeBSD-EN-19:06.dtrace
63 amd64: clear callee-preserved registers on syscall exit
66 Avoid leaking fp references when truncating SCM_RIGHTS control messages.
69 dtrace: fix userspace access on boxes with SMAP [EN-19:06.dtrace]
71 Fix an LLE lookup race [EN-19:07.lle]
73 20190109: p2 FreeBSD-EN-19:01.cc_cubic
75 FreeBSD-EN-19:03.sqlite
76 FreeBSD-EN-19:04.tzdata
78 Revert CC Cubic: fix underflow for cubic_cwnd() [EN-19:01.cc_cubic]
80 Fix a TCP handling of received segments. [EN-19:02.tcp]
82 Update sqlite3-3.23.1 --> sqlite3-3.26.0 (3260000) [EN-19:03.sqlite]
84 Import tzdata 2018h, 2018i [EN-19:04.tzdata]
86 20181219: p1 FreeBSD-SA-18:15.bootpd
88 bootpd: validate hardware type [SA-18:15.bootpd]
94 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
95 has been converted to a port (misc/ctm) and will be removed from
96 FreeBSD-13. A depreciation warning will be printed to stderr by
97 the ctm command, but the functionality will remain in base for all
101 The stable/12 branch has been created in subversion from head
105 Ports for the DRM modules have been simplified. Now, amd64 users should
106 just install the drm-kmod port. All others should install
109 Graphics hardware that's newer than about 2010 usually works with
110 drm-kmod. For hardware older than 2013, however, some users will need
111 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
112 than 2008 usually only works in drm-legacy-kmod. The graphics team can
113 only commit to hardware made since 2013 due to the complexity of the
114 market and difficulty to test all the older cards effectively. If you
115 have hardware supported by drm-kmod, you are strongly encouraged to use
116 that as you will get better support.
118 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
119 elsewhere, the drm and drm2 modules will be eliminated from the src base
120 soon (with a limited exception for arm). Please update to the package asap
121 and report any issues to x11@freebsd.org.
123 Generally, anybody using the drm*-kmod packages should add
124 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
125 cross-threading surprises, especially with automatic driver
126 loading from X11 startup. These will become the defaults in 13-current
130 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
131 custom kernel and module loading configuration files must be updated
132 accordingly. Moreover, interfaces previous presented as ixlvN to the
133 system are now exposed as iavfN and network configuration files must
134 be adjusted as necessary.
137 OpenSSL has been updated to version 1.1.1. This update included
138 additional various API changes througout the base system. It is
139 important to rebuild third-party software after upgrading. The value
140 of __FreeBSD_version has been bumped accordingly.
143 The legacy DRM modules and drivers have now been added to the loader's
144 module blacklist, in favor of loading them with kld_list in rc.conf(5).
145 The module blacklist may be overridden with the loader.conf(5)
146 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
150 The cam(4) based nda(4) driver will be used over nvd(4) by default on
151 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
152 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
153 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
157 Reproducible build mode is now on by default, in preparation for
158 FreeBSD 12.0. This eliminates build metadata such as the user,
159 host, and time from the kernel (and uname), unless the working tree
160 corresponds to a modified checkout from a version control system.
161 The previous behavior can be obtained by setting the /etc/src.conf
162 knob WITHOUT_REPRODUCIBLE_BUILD.
165 The Yarrow CSPRNG has been removed from the kernel as it has not been
166 supported by its designers since at least 2003. Fortuna has been the
167 default since FreeBSD-11.
170 devctl freeze/thaw have gone into the tree, the rc scripts have been
171 updated to use them and devmatch has been changed. You should update
172 kernel, userland and rc scripts all at the same time.
175 The default interpreter has been switched from 4th to Lua.
176 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
177 interpreter. If you have custom FORTH code you will need to set
178 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
179 src.conf for the build. This will create default hard links between
180 loader and loader_4th instead of loader and loader_lua, the new default.
181 If you are using UEFI it will create the proper hard link to loader.efi.
183 bhyve uses userboot.so. It remains 4th-only until some issues are solved
184 regarding coexisting with multiple versions of FreeBSD are resolved.
187 ls(1) now respects the COLORTERM environment variable used in other
188 systems and software to indicate that a colored terminal is both
189 supported and desired. If ls(1) is suddenly emitting colors, they may
190 be disabled again by either removing the unwanted COLORTERM from your
191 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
192 may not be observed in a future release.
195 The default pager for most commands has been changed to "less". To
196 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
200 The jedec_ts(4) driver has been removed. A superset of its functionality
201 is available in the jedec_dimm(4) driver, and the manpage for that
202 driver includes migration instructions. If you have "device jedec_ts"
203 in your kernel configuration file, it must be removed.
206 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
207 This should have no effect if the kernel is booted via BIOS/legacy boot.
208 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
209 has a buggy firmware that prevents a successful boot due to use of
213 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
214 support has been removed from the tree. These ports were
215 obsolete and/or known to be broken for many years.
218 loader.efi has been augmented to participate more fully in the
219 UEFI boot manager protocol. loader.efi will now look at the
220 BootXXXX environment variable to determine if a specific kernel
221 or root partition was specified. XXXX is derived from BootCurrent.
222 efibootmgr(8) manages these standard UEFI variables.
225 zfsloader's functionality has now been folded into loader.
226 zfsloader is no longer necessary once you've updated your
227 boot blocks. For a transition period, we will install a
228 hardlink for zfsloader to loader to allow a smooth transition
229 until the boot blocks can be updated (hard link because old
230 zfs boot blocks don't understand symlinks).
233 ARM64 now have efifb support, if you want to have serial console
234 on your arm64 board when an screen is connected and the bootloader
235 setup a frambuffer for us to use, just add :
239 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
240 an screen connected as the firmware will setup a framebuffer are that
241 u-boot will expose as an EFI framebuffer.
244 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
245 or take steps to update /etc/passwd before doing installworld on
246 existing systems. Do not skip the "mergemaster -Fp" step before
247 installworld, as described in the update procedures near the bottom
248 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
249 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
250 the ntp config file contain options that change file/dir locations.
251 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
252 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
253 taking steps to ensure that all required files/dirs are accessible
257 Big endian arm support has been removed.
260 The static environment setup in kernel configs is no longer mutually
261 exclusive with the loader(8) environment by default. In order to
262 restore the previous default behavior of disabling the loader(8)
263 environment if a static environment is present, you must specify
264 loader_env.disabled=1 in the static environment.
267 The ABI of syscalls used by management tools like sockstat and
268 netstat has been broken to allow 32-bit binaries to work on
269 64-bit kernels without modification. These programs will need
270 to match the kernel in order to function. External programs may
271 require minor modifications to accommodate a change of type in
272 structures from pointers to 64-bit virtual addresses.
275 On i386 and amd64 atomics are now inlined. Out of tree modules using
276 atomics will need to be rebuilt.
279 The '%I' format in the kern.corefile sysctl limits the number of
280 core files that a process can generate to the number stored in the
281 debug.ncores sysctl. The '%I' format is replaced by the single digit
282 index. Previously, if all indexes were taken the kernel would overwrite
283 only a core file with the highest index in a filename.
284 Currently the system will create a new core file if there is a free
285 index or if all slots are taken it will overwrite the oldest one.
288 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
289 6.0.1. Please see the 20141231 entry below for information about
290 prerequisites and upgrading, if you are not already using clang 3.5.0
294 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
295 needed to be changed to work with it. This change was made with r335763
296 and requires a mergemaster / etcupdate / etc to update the installed file.
299 r334930 changed the interface between the NFS modules, so they all
300 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
303 As of r334391 lld is the default amd64 system linker; it is installed
304 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
308 The kernel / userland interface for devinfo changed, so you'll
309 need a new kernel and userland as a pair for it to work (rebuilding
310 lib/libdevinfo is all that's required). devinfo and devmatch will
311 not work, but everything else will when there's a mismatch.
314 The on-disk format for hwpmc callchain records has changed to include
315 threadid corresponding to a given record. This changes the field offsets
316 and thus requires that libpmcstat be rebuilt before using a kernel
320 The vxge(4) driver has been removed. This driver was introduced into
321 HEAD one week before the Exar left the Ethernet market and is not
322 known to be used. If you have device vxge in your kernel config file
326 The amd64 kernel now requires a ld that supports ifunc to produce a
327 working kernel, either lld or a newer binutils. lld is built by default
328 on amd64, and the 'buildkernel' target uses it automatically. However,
329 it is not the default linker, so building the kernel the traditional
330 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
331 binutils port/package). lld will soon be default, and this requirement
334 NOTE: As of r334391 lld is the default system linker on amd64, and no
335 workaround is necessary.
338 The nxge(4) driver has been removed. This driver was for PCI-X 10g
339 cards made by s2io/Neterion. The company was aquired by Exar and
340 no longer sells or supports Ethernet products. If you have device
341 nxge in your kernel config file it must be removed.
344 The tz database (tzdb) has been updated to 2018e. This version more
345 correctly models time stamps in time zones with negative DST such as
346 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
347 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
348 time zone abbreviations and the tm_isdst flag.
351 The ixgb(4) driver has been removed. This driver was for an early and
352 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
353 quickly shifted to the long lived ixgbe family. If you have device
354 ixgb in your kernel config file it must be removed.
357 The lmc(4) driver has been removed. This was a WAN interface
358 card that was already reportedly rare in 2003, and had an ambiguous
359 license. If you have device lmc in your kernel config file it must
363 Support for Arcnet networks has been removed. If you have device
364 arcnet or device cm in your kernel config file they must be
368 Support for FDDI networks has been removed. If you have device
369 fddi or device fpa in your kernel config file they must be
373 In addition to supporting RFC 3164 formatted messages, the
374 syslogd(8) service is now capable of parsing RFC 5424 formatted
375 log messages. The main benefit of using RFC 5424 is that clients
376 may now send log messages with timestamps containing year numbers,
377 microseconds and time zone offsets.
379 Similarly, the syslog(3) C library function has been altered to
380 send RFC 5424 formatted messages to the local system logging
381 daemon. On systems using syslogd(8), this change should have no
382 negative impact, as long as syslogd(8) and the C library are
383 updated at the same time. On systems using a different system
384 logging daemon, it may be necessary to make configuration
385 adjustments, depending on the software used.
387 When using syslog-ng, add the 'syslog-protocol' flag to local
388 input sources to enable parsing of RFC 5424 formatted messages:
391 unix-dgram("/var/run/log" flags(syslog-protocol));
394 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
395 of the 'imuxsock' module to let messages be processed by the
396 regular RFC 3164/5424 parsing pipeline:
398 module(load="imuxsock" SysSock.UseSpecialParser="off")
400 Do note that these changes only affect communication between local
401 applications and syslogd(8). The format that syslogd(8) uses to
402 store messages on disk or forward messages to other systems
403 remains unchanged. syslogd(8) still uses RFC 3164 for these
404 purposes. Options to customize this behaviour will be added in the
405 future. Utilities that process log files stored in /var/log are
406 thus expected to continue to function as before.
408 __FreeBSD_version has been incremented to 1200061 to denote this
412 Support for token ring networks has been removed. If you
413 have "device token" in your kernel config you should remove
414 it. No device drivers supported token ring.
417 makefs was modified to be able to tag ISO9660 El Torito boot catalog
418 entries as EFI instead of overloading the i386 tag as done previously.
419 The amd64 mkisoimages.sh script used to build amd64 ISO images for
420 release was updated to use this. This may mean that makefs must be
421 updated before "make cdrom" can be run in the release directory. This
422 should be as simple as:
424 $ cd $SRCDIR/usr.sbin/makefs
425 $ make depend all install
428 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
429 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
430 Co-existance for the transition period will come shortly. Booting is a
431 complex environment and test coverage for Lua-enabled loaders has been
432 thin, so it would be prudent to assume it might not work and make
433 provisions for backup boot methods.
436 devmatch functionality has been turned on in devd. It will automatically
437 load drivers for unattached devices. This may cause unexpected drivers to
438 be loaded. Please report any problems to current@ and imp@freebsd.org.
441 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
442 6.0.0. Please see the 20141231 entry below for information about
443 prerequisites and upgrading, if you are not already using clang 3.5.0
447 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
448 This means it is used to link the kernel and userland libraries and
449 executables, but is not yet installed as /usr/bin/ld by default.
451 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
452 WITHOUT_LLD_BOOTSTRAP=yes
455 On i386, pmtimer has been removed. Its functionality has been folded
456 into apm. It was a no-op on ACPI in current for a while now (but was still
457 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
458 from kernel config files.
461 The use of RSS hash from the network card aka flowid has been
462 disabled by default for lagg(4) as it's currently incompatible with
463 the lacp and loadbalance protocols.
465 This can be re-enabled by setting the following in loader.conf:
466 net.link.lagg.default_use_flowid="1"
469 The SW_WATCHDOG option is no longer necessary to enable the
470 hardclock-based software watchdog if no hardware watchdog is
471 configured. As before, SW_WATCHDOG will cause the software
472 watchdog to be enabled even if a hardware watchdog is configured.
475 r326887 fixes the issue described in the 20171214 UPDATING entry.
476 r326888 flips the switch back to building GELI support always.
479 r362593 broke ZFS + GELI support for reasons unknown. However,
480 it also broke ZFS support generally, so GELI has been turned off
481 by default as the lesser evil in r326857. If you boot off ZFS and/or
482 GELI, it might not be a good time to update.
485 PowerPC users must update loader(8) by rebuilding world before
486 installing a new kernel, as the protocol connecting them has
487 changed. Without the update, loader metadata will not be passed
488 successfully to the kernel and users will have to enter their
489 root partition at the kernel mountroot prompt to continue booting.
490 Newer versions of loader can boot old kernels without issue.
493 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
494 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
495 to WITH/OUT_LOADER_GELI.
498 The naive and non-compliant support of posix_fallocate(2) in ZFS
499 has been removed as of r325320. The system call now returns EINVAL
500 when used on a ZFS file. Although the new behavior complies with the
501 standard, some consumers are not prepared to cope with it.
502 One known victim is lld prior to r325420.
505 Building in a FreeBSD src checkout will automatically create object
506 directories now rather than store files in the current directory if
507 'make obj' was not ran. Calling 'make obj' is no longer necessary.
508 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
509 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
513 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
514 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
515 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
516 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
517 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
518 The UNIFIED_OBJDIR option is a transitional feature that will be
519 removed for 12.0 release; please migrate to the new format for any
520 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
521 than hardcoding paths.
524 The native-xtools target no longer installs the files by default to the
525 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
526 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
529 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
530 options are changing from controlling the build if defined / undefined
531 to controlling the build with explicit 'yes' or 'no' values. They will
532 shift to WITH/WITHOUT options to match other options in the system.
535 libstand has turned into a private library for sys/boot use only.
536 It is no longer supported as a public interface outside of sys/boot.
539 The arm port has split armv6 into armv6 and armv7. armv7 is now
540 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
541 and are running a kernel from before r324363, you will need to add
542 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
545 When building multiple kernels using KERNCONF, non-existent KERNCONF
546 files will produce an error and buildkernel will fail. Previously
547 missing KERNCONF files silently failed giving no indication as to
548 why, only to subsequently discover during installkernel that the
549 desired kernel was never built in the first place.
552 The default serial number format for CTL LUNs has changed. This will
553 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
554 or iSCSI clients care about their LUNs' serial numbers. Users who
555 require serial number stability should hardcode serial numbers in
559 For 32-bit arm compiled for hard-float support, soft-floating point
560 binaries now always get their shared libraries from
561 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
562 /usr/libsoft also existed). Only users with a hard-float ld.so, but
563 soft-float everything else should be affected.
566 The geli password typed at boot is now hidden. To restore the previous
567 behavior, see geli(8) for configuration options.
570 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
571 sysctl values. Minor nit, but requires a rebuild of both world/kernel
575 "make check" behavior (made in ^/head@r295380) has been changed to
576 execute from a limited sandbox, as opposed to executing from
580 - The "beforecheck" and "aftercheck" targets are now specified.
581 - ${CHECKDIR} (added in commit noted above) has been removed.
582 - Legacy behavior can be enabled by setting
583 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
585 If the limited sandbox mode is enabled, "make check" will execute
586 "make distribution", then install, execute the tests, and clean up the
587 sandbox if successful.
589 The "make distribution" and "make install" targets are typically run as
590 root to set appropriate permissions and ownership at installation time.
591 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
592 environment if executing "make check" with limited sandbox mode using
593 an unprivileged user.
596 Since the switch to GPT disk labels, fsck for UFS/FFS has been
597 unable to automatically find alternate superblocks. As of r322297,
598 the information needed to find alternate superblocks has been
599 moved to the end of the area reserved for the boot block.
600 Filesystems created with a newfs of this vintage or later
601 will create the recovery information. If you have a filesystem
602 created prior to this change and wish to have a recovery block
603 created for your filesystem, you can do so by running fsck in
604 foreground mode (i.e., do not use the -p or -y options). As it
605 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
606 to which you should answer yes.
609 As of r321665, an NFSv4 server configuration that services
610 Kerberos mounts or clients that do not support the uid/gid in
611 owner/owner_group string capability, must explicitly enable
612 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
613 machine's /etc/rc.conf file.
616 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
617 Please see the 20141231 entry below for information about prerequisites
618 and upgrading, if you are not already using clang 3.5.0 or higher.
621 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
622 r-commands (rlogin, rsh, etc.) to be built with the base system.
625 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
626 a very major ABI incompatible change, so users of FreeBSD/powerpc must
627 be careful when performing source upgrades. It is best to run
628 'make installworld' from an alternate root system, either a live
629 CD/memory stick, or a temporary root partition. Additionally, all ports
630 must be recompiled. powerpc64 is largely unaffected, except in the case
631 of 32-bit compatibility. All 32-bit binaries will be affected.
634 Forward compatibility for the "ino64" project have been committed. This
635 will allow most new binaries to run on older kernels in a limited
636 fashion. This prevents many of the common foot-shooting actions in the
637 upgrade as well as the limited ability to roll back the kernel across
638 the ino64 upgrade. Complicated use cases may not work properly, though
639 enough simpler ones work to allow recovery in most situations.
642 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
643 if you require the GPL compiler.
646 The internal ABI used for communication between the NFS kernel modules
647 was changed by r320085, so __FreeBSD_version was bumped to
648 ensure all the NFS related modules are updated together.
651 The ABI of struct event was changed by extending the data
652 member to 64bit and adding ext fields. For upgrade, same
653 precautions as for the entry 20170523 "ino64" must be
657 The GNU roff toolchain has been removed from base. To render manpages
658 which are not supported by mandoc(1), man(1) can fallback on GNU roff
659 from ports (and recommends to install it).
660 To render roff(7) documents, consider using GNU roff from ports or the
661 heirloom doctools roff toolchain from ports via pkg install groff or
662 via pkg install heirloom-doctools.
665 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
666 smaller runtime footprint builds. This is useful for embedded systems
667 which only require one chipset support.
669 If you load it as a module, make sure this is in /boot/loader.conf:
673 This will load the HAL, all chip/RF backends and if_ath_pci.
674 If you have if_ath_pci in /boot/loader.conf, ensure it is after
675 if_ath or it will not load any HAL chipset support.
677 If you want to selectively load things (eg on ye cheape ARM/MIPS
678 platforms where RAM is at a premium) you should:
681 * load the chip modules in question
682 * load ath_rate, ath_dfs
684 * load if_ath_pci and/or if_ath_ahb depending upon your particular
685 bus bind type - this is where probe/attach is done.
687 For further comments/feedback, poke adrian@ .
690 The "ino64" 64-bit inode project has been committed, which extends
691 a number of types to 64 bits. Upgrading in place requires care and
692 adherence to the documented upgrade procedure.
694 If using a custom kernel configuration ensure that the
695 COMPAT_FREEBSD11 option is included (as during the upgrade the
696 system will be running the ino64 kernel with the existing world).
698 For the safest in-place upgrade begin by removing previous build
699 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
700 full procedure documented below under the heading "To rebuild
701 everything and install it on the current system." Specifically,
702 a reboot is required after installing the new kernel before
706 The NATM framework including the en(4), fatm(4), hatm(4), and
707 patm(4) devices has been removed. Consumers should plan a
708 migration before the end-of-life date for FreeBSD 11.
711 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
712 diff has not been implemented, if those are needed a newer version of
713 GNU diff is available via the diffutils package under the gdiff name.
716 As of r316810 for ipfilter, keep frags is no longer assumed when
717 keep state is specified in a rule. r316810 aligns ipfilter with
718 documentation in man pages separating keep frags from keep state.
719 This allows keep state to be specified without forcing keep frags
720 and allows keep frags to be specified independently of keep state.
721 To maintain previous behaviour, also specify keep frags with
722 keep state (as documented in ipf.conf.5).
725 arm64 builds now use the base system LLD 4.0.0 linker by default,
726 instead of requiring that the aarch64-binutils port or package be
727 installed. To continue using aarch64-binutils, set
728 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
731 The UDP optimization in entry 20160818 that added the sysctl
732 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
733 packets will no longer be treated as L3 broadcast packets.
736 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
737 use any explicitly assigned loopback address available in the jail
738 instead of using the first assigned address of the jail.
741 The ctl.ko module no longer implements the iSCSI target frontend:
742 cfiscsi.ko does instead.
744 If building cfiscsi.ko as a kernel module, the module can be loaded
745 via one of the following methods:
746 - `cfiscsi_load="YES"` in loader.conf(5).
747 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
748 - ctladm(8)/ctld(8), when compiled with iSCSI support
749 (`WITH_ISCSI=yes` in src.conf(5))
751 Please see cfiscsi(4) for more details.
754 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
755 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
756 same source (previously, the dependency of mmcsd.ko on mmc.ko was
757 missing, but mmcsd.ko now will refuse to load if it is incompatible
761 The syntax of ipfw(8) named states was changed to avoid ambiguity.
762 If you have used named states in the firewall rules, you need to modify
763 them after installworld and before rebooting. Now named states must
764 be prefixed with colon.
767 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
768 removed as the userland we provide cannot use them. The KMS version
769 (sys/dev/drm2) supports the same hardware.
772 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
773 Please see the 20141231 entry below for information about prerequisites
774 and upgrading, if you are not already using clang 3.5.0 or higher.
777 The code that provides support for ZFS .zfs/ directory functionality
778 has been reimplemented. It's not possible now to create a snapshot
779 by mkdir under .zfs/snapshot/. That should be the only user visible
783 EISA bus support has been removed. The WITH_EISA option is no longer
787 MCA bus support has been removed.
790 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
791 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
794 The EM_MULTIQUEUE kernel configuration option is deprecated now that
795 the em(4) driver conforms to iflib specifications.
798 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
799 IFLIB. If you have a custom kernel configuration that excludes em(4)
800 but you use igb(4), you need to re-add em(4) to your custom configuration.
803 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
804 Please see the 20141231 entry below for information about prerequisites
805 and upgrading, if you are not already using clang 3.5.0 or higher.
808 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
809 Please see the 20141231 entry below for information about prerequisites
810 and upgrading, if you are not already using clang 3.5.0 or higher.
813 The layout of the pmap structure has changed for powerpc to put the pmap
814 statistics at the front for all CPU variations. libkvm(3) and all tools
815 that link against it need to be recompiled.
818 isl(4) and cyapa(4) drivers now require a new driver,
819 chromebook_platform(4), to work properly on Chromebook-class hardware.
820 On other types of hardware the drivers may need to be configured using
821 device hints. Please see the corresponding manual pages for details.
824 The urtwn(4) driver was merged into rtwn(4) and now consists of
825 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
827 Also, firmware for RTL8188CE was renamed due to possible name
828 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
831 GNU rcs has been removed from base. It is available as packages:
832 - rcs: Latest GPLv3 GNU rcs version.
833 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
837 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
838 modules now requires that the kernel configuration contain the
839 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
842 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
843 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
846 Relocatable object files with the extension of .So have been renamed
847 to use an extension of .pico instead. The purpose of this change is
848 to avoid a name clash with shared libraries on case-insensitive file
849 systems. On those file systems, foo.So is the same file as foo.so.
852 GNU rcs has been turned off by default. It can (temporarily) be built
853 again by adding WITH_RCS knob in src.conf.
854 Otherwise, GNU rcs is available from packages:
855 - rcs: Latest GPLv3 GNU rcs version.
856 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
859 The backup_uses_rcs functionality has been removed from rc.subr.
862 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
863 two separate components, QUEUE_MACRO_DEBUG_TRACE and
864 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
865 QUEUE_MACRO_DEBUG behavior.
868 r304787 changed some ioctl interfaces between the iSCSI userspace
869 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
870 rebuilt to work with new kernels. __FreeBSD_version has been bumped
874 The UDP receive code has been updated to only treat incoming UDP
875 packets that were addressed to an L2 broadcast address as L3
876 broadcast packets. It is not expected that this will affect any
877 standards-conforming UDP application. The new behaviour can be
878 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
882 Remove the openbsd_poll system call.
883 __FreeBSD_version has been bumped because of this.
886 The stable/11 branch has been created from head@r302406.
889 The libc stub for the pipe(2) system call has been replaced with
890 a wrapper that calls the pipe2(2) system call and the pipe(2)
891 system call is now only implemented by the kernels that include
892 "options COMPAT_FREEBSD10" in their config file (this is the
893 default). Users should ensure that this option is enabled in
894 their kernel or upgrade userspace to r302092 before upgrading their
898 CAM will now strip leading spaces from SCSI disks' serial numbers.
899 This will affect users who create UFS filesystems on SCSI disks using
900 those disk's diskid device nodes. For example, if /etc/fstab
901 previously contained a line like
902 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
903 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
904 transforms like gmirror may also be affected. ZFS users should
908 The bitstring(3) API has been updated with new functionality and
909 improved performance. But it is binary-incompatible with the old API.
910 Objects built with the new headers may not be linked against objects
911 built with the old headers.
914 The brk and sbrk functions have been removed from libc on arm64.
915 Binutils from ports has been updated to not link to these
916 functions and should be updated to the latest version before
917 installing a new libc.
920 The armv6 port now defaults to hard float ABI. Limited support
921 for running both hardfloat and soft float on the same system
922 is available using the libraries installed with -DWITH_LIBSOFT.
923 This has only been tested as an upgrade path for installworld
924 and packages may fail or need manual intervention to run. New
925 packages will be needed.
927 To update an existing self-hosted armv6hf system, you must add
928 TARGET_ARCH=armv6 on the make command line for both the build
929 and the install steps.
932 Kernel modules compiled outside of a kernel build now default to
933 installing to /boot/modules instead of /boot/kernel. Many kernel
934 modules built this way (such as those in ports) already overrode
935 KMODDIR explicitly to install into /boot/modules. However,
936 manually building and installing a module from /sys/modules will
937 now install to /boot/modules instead of /boot/kernel.
940 The CAM I/O scheduler has been committed to the kernel. There should be
941 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
942 list of known rogues that claim support for this but actually corrupt
943 data is believed to be complete, be on the lookout for data
944 corruption. The known rogue list is believed to be complete:
946 o Crucial MX100, M550 drives with MU01 firmware.
947 o Micron M510 and M550 drives with MU01 firmware.
948 o Micron M500 prior to MU07 firmware
949 o Samsung 830, 840, and 850 all firmwares
950 o FCCT M500 all firmwares
952 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
953 with working NCQ TRIM. For Micron branded drives, see your sales rep for
954 updated firmware. Black listed drives will work correctly because these
955 drives work correctly so long as no NCQ TRIMs are sent to them. Given
956 this list is the same as found in Linux, it's believed there are no
957 other rogues in the market place. All other models from the above
960 To be safe, if you are at all concerned, you can quirk each of your
961 drives to prevent NCQ from being sent by setting:
962 kern.cam.ada.X.quirks="0x2"
963 in loader.conf. If the drive requires the 4k sector quirk, set the
967 The FAST_DEPEND build option has been removed and its functionality is
968 now the one true way. The old mkdep(1) style of 'make depend' has
969 been removed. See 20160311 for further details.
972 Resource range types have grown from unsigned long to uintmax_t. All
973 drivers, and anything using libdevinfo, need to be recompiled.
976 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
977 builds. It no longer runs mkdep(1) during 'make depend', and the
978 'make depend' stage can safely be skipped now as it is auto ran
979 when building 'make all' and will generate all SRCS and DPSRCS before
980 building anything else. Dependencies are gathered at compile time with
981 -MF flags kept in separate .depend files per object file. Users should
982 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
986 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
987 kernel modules. Therefore, if you load any kernel modules at boot time,
988 please install the boot loaders after you install the kernel, but before
992 make buildkernel KERNCONF=YOUR_KERNEL_HERE
993 make installkernel KERNCONF=YOUR_KERNEL_HERE
994 make -C sys/boot install
995 <reboot in single user>
997 Then follow the usual steps, described in the General Notes section,
1001 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1002 see the 20141231 entry below for information about prerequisites and
1003 upgrading, if you are not already using clang 3.5.0 or higher.
1006 The AIO subsystem is now a standard part of the kernel. The
1007 VFS_AIO kernel option and aio.ko kernel module have been removed.
1008 Due to stability concerns, asynchronous I/O requests are only
1009 permitted on sockets and raw disks by default. To enable
1010 asynchronous I/O requests on all file types, set the
1011 vfs.aio.enable_unsafe sysctl to a non-zero value.
1014 The ELF object manipulation tool objcopy is now provided by the
1015 ELF Tool Chain project rather than by GNU binutils. It should be a
1016 drop-in replacement, with the addition of arm64 support. The
1017 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1018 to obtain the GNU version if necessary.
1021 Building ZFS pools on top of zvols is prohibited by default. That
1022 feature has never worked safely; it's always been prone to deadlocks.
1023 Using a zvol as the backing store for a VM guest's virtual disk will
1024 still work, even if the guest is using ZFS. Legacy behavior can be
1025 restored by setting vfs.zfs.vol.recursive=1.
1028 The NONE and HPN patches has been removed from OpenSSH. They are
1029 still available in the security/openssh-portable port.
1032 With the addition of ypldap(8), a new _ypldap user is now required
1033 during installworld. "mergemaster -p" can be used to add the user
1034 prior to installworld, as documented in the handbook.
1037 The tftp loader (pxeboot) now uses the option root-path directive. As a
1038 consequence it no longer looks for a pxeboot.4th file on the tftp
1039 server. Instead it uses the regular /boot infrastructure as with the
1043 The code to start recording plug and play data into the modules has
1044 been committed. While the old tools will properly build a new kernel,
1045 a number of warnings about "unknown metadata record 4" will be produced
1046 for an older kldxref. To avoid such warnings, make sure to rebuild
1047 the kernel toolchain (or world). Make sure that you have r292078 or
1048 later when trying to build 292077 or later before rebuilding.
1051 Debug data files are now built by default with 'make buildworld' and
1052 installed with 'make installworld'. This facilitates debugging but
1053 requires more disk space both during the build and for the installed
1054 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1058 r291527 changed the internal interface between the nfsd.ko and
1059 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1060 __FreeBSD_version has been bumped because of this.
1063 Add support for unicode collation strings leads to a change of
1064 order of files listed by ls(1) for example. To get back to the old
1065 behaviour, set LC_COLLATE environment variable to "C".
1067 Databases administrators will need to reindex their databases given
1068 collation results will be different.
1070 Due to a bug in install(1) it is recommended to remove the ancient
1071 locales before running make installworld.
1073 rm -rf /usr/share/locale/*
1076 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1077 libcrypto.so.7 or libssl.so.7 must be recompiled.
1080 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1081 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1082 should be replaced with isp_2400 and isp_2500 modules respectively.
1085 The build previously allowed using 'make -n' to not recurse into
1086 sub-directories while showing what commands would be executed, and
1087 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1088 and 'make -N' will not.
1091 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1092 and etcupdate will now use this file. A custom sendmail.cf is now
1093 updated via this mechanism rather than via installworld. If you had
1094 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1095 want to remove the exclusion or change it to "always install".
1096 /etc/mail/sendmail.cf is now managed the same way regardless of
1097 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1098 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1101 Compatibility shims for legacy ATA device names have been removed.
1102 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1103 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1104 environment variables, /dev/ad* and /dev/ar* symbolic links.
1107 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1108 Please see the 20141231 entry below for information about prerequisites
1109 and upgrading, if you are not already using clang 3.5.0 or higher.
1112 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1113 and renamed from .symbols to .debug. This reduces the size requirements
1114 on the boot partition or file system and provides consistency with
1115 userland debug files.
1117 When using the supported kernel installation method the
1118 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1119 as is done with /boot/kernel.
1121 Developers wishing to maintain the historical behavior of installing
1122 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1125 The wireless drivers had undergone changes that remove the 'parent
1126 interface' from the ifconfig -l output. The rc.d network scripts
1127 used to check presence of a parent interface in the list, so old
1128 scripts would fail to start wireless networking. Thus, etcupdate(3)
1129 or mergemaster(8) run is required after kernel update, to update your
1130 rc.d scripts in /etc.
1133 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1134 These configurations are now automatically interpreted as
1135 'scrub fragment reassemble'.
1138 Kernel-loadable modules for the random(4) device are back. To use
1139 them, the kernel must have
1142 options RANDOM_LOADABLE
1144 kldload(8) can then be used to load random_fortuna.ko
1145 or random_yarrow.ko. Please note that due to the indirect
1146 function calls that the loadable modules need to provide,
1147 the build-in variants will be slightly more efficient.
1149 The random(4) kernel option RANDOM_DUMMY has been retired due to
1150 unpopularity. It was not all that useful anyway.
1153 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1154 Control over building the ELF Tool Chain tools is now provided by
1155 the WITHOUT_TOOLCHAIN knob.
1158 The polarity of Pulse Per Second (PPS) capture events with the
1159 uart(4) driver has been corrected. Prior to this change the PPS
1160 "assert" event corresponded to the trailing edge of a positive PPS
1161 pulse and the "clear" event was the leading edge of the next pulse.
1163 As the width of a PPS pulse in a typical GPS receiver is on the
1164 order of 1 millisecond, most users will not notice any significant
1165 difference with this change.
1167 Anyone who has compensated for the historical polarity reversal by
1168 configuring a negative offset equal to the pulse width will need to
1169 remove that workaround.
1172 The default group assigned to /dev/dri entries has been changed
1173 from 'wheel' to 'video' with the id of '44'. If you want to have
1174 access to the dri devices please add yourself to the video group
1177 # pw groupmod video -m $USER
1180 The menu.rc and loader.rc files will now be replaced during
1181 upgrades. Please migrate local changes to menu.rc.local and
1182 loader.rc.local instead.
1185 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1186 strings and strip have been removed. The src.conf(5) knob
1187 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1190 As ZFS requires more kernel stack pages than is the default on some
1191 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1192 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1194 Please consider using 'options KSTACK_PAGES=X' where X is greater
1195 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1198 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1199 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1200 default, i.e., they will not contain "::". For example, instead
1201 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1202 to have a more specific match, such as different map entries for
1203 IPv6:0:0 vs IPv6:0. This change requires that configuration
1204 data (including maps, files, classes, custom ruleset, etc.) must
1205 use the same format, so make certain such configuration data is
1206 upgrading. As a very simple check search for patterns like
1207 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1208 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1209 the cf option UseCompressedIPv6Addresses.
1212 The default kernel entropy-processing algorithm is now
1213 Fortuna, replacing Yarrow.
1215 Assuming you have 'device random' in your kernel config
1216 file, the configurations allow a kernel option to override
1217 this default. You may choose *ONE* of:
1219 options RANDOM_YARROW # Legacy /dev/random algorithm.
1220 options RANDOM_DUMMY # Blocking-only driver.
1222 If you have neither, you get Fortuna. For most people,
1223 read no further, Fortuna will give a /dev/random that works
1224 like it always used to, and the difference will be irrelevant.
1226 If you remove 'device random', you get *NO* kernel-processed
1227 entropy at all. This may be acceptable to folks building
1228 embedded systems, but has complications. Carry on reading,
1229 and it is assumed you know what you need.
1231 *PLEASE* read random(4) and random(9) if you are in the
1232 habit of tweaking kernel configs, and/or if you are a member
1233 of the embedded community, wanting specific and not-usual
1234 behaviour from your security subsystems.
1236 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1237 random', you will NOT have a functioning /dev/random, and
1238 many cryptographic features will not work, including SSH.
1239 You may also find strange behaviour from the random(3) set
1240 of library functions, in particular sranddev(3), srandomdev(3)
1241 and arc4random(3). The reason for this is that the KERN_ARND
1242 sysctl only returns entropy if it thinks it has some to
1243 share, and with RANDOM_DUMMY or no 'device random' this
1247 An additional fix for the issue described in the 20150614 sendmail
1248 entry below has been committed in revision 284717.
1251 FreeBSD's old make (fmake) has been removed from the system. It is
1252 available as the devel/fmake port or via pkg install fmake.
1255 The fix for the issue described in the 20150614 sendmail entry
1256 below has been committed in revision 284436. The work
1257 around described in that entry is no longer needed unless the
1258 default setting is overridden by a confDH_PARAMETERS configuration
1259 setting of '5' or pointing to a 512 bit DH parameter file.
1262 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1263 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1264 and devel/kyua to version 0.20+ and adjust any calling code to work
1265 with Kyuafile and kyua.
1268 The import of openssl to address the FreeBSD-SA-15:10.openssl
1269 security advisory includes a change which rejects handshakes
1270 with DH parameters below 768 bits. sendmail releases prior
1271 to 8.15.2 (not yet released), defaulted to a 512 bit
1272 DH parameter setting for client connections. To work around
1273 this interoperability, sendmail can be configured to use a
1274 2048 bit DH parameter by:
1276 1. Edit /etc/mail/`hostname`.mc
1277 2. If a setting for confDH_PARAMETERS does not exist or
1278 exists and is set to a string beginning with '5',
1279 replace it with '2'.
1280 3. If a setting for confDH_PARAMETERS exists and is set to
1281 a file path, create a new file with:
1282 openssl dhparam -out /path/to/file 2048
1283 4. Rebuild the .cf file:
1284 cd /etc/mail/; make; make install
1285 5. Restart sendmail:
1286 cd /etc/mail/; make restart
1288 A sendmail patch is coming, at which time this file will be
1292 Generation of legacy formatted entries have been disabled by default
1293 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1294 entries were converted to use the new format by default when the new,
1295 machine independent format have been added and supported since FreeBSD
1298 Please see the pwd_mkdb(8) manual page for further details.
1301 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1302 20141231 entry below for information about prerequisites and upgrading,
1303 if you are not already using 3.5.0 or higher.
1306 TI platform code switched to using vendor DTS files and this update
1307 may break existing systems running on Beaglebone, Beaglebone Black,
1310 - dtb files should be regenerated/reinstalled. Filenames are the
1311 same but content is different now
1312 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1313 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1314 addressing scheme is now pin 25 on /dev/gpioc3.
1315 - Pandaboard: /etc/ttys should be updated, serial console device is
1316 now /dev/ttyu2, not /dev/ttyu0
1319 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1320 If you need the GNU extension from groff soelim(1), install groff
1321 from package: pkg install groff, or via ports: textproc/groff.
1324 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1325 defined in symlink(7); previously symlinks were silently ignored.
1328 The const qualifier has been removed from iconv(3) to comply with
1329 POSIX. The ports tree is aware of this from r384038 onwards.
1332 Libraries specified by LIBADD in Makefiles must have a corresponding
1333 DPADD_<lib> variable to ensure correct dependencies. This is now
1334 enforced in src.libnames.mk.
1337 From legacy ata(4) driver was removed support for SATA controllers
1338 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1339 Kernel modules ataahci and ataadaptec were removed completely,
1340 replaced by ahci and mvs modules respectively.
1343 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1344 the 20141231 entry below for information about prerequisites and
1345 upgrading, if you are not already using 3.5.0 or higher.
1348 The 32-bit PowerPC kernel has been changed to a position-independent
1349 executable. This can only be booted with a version of loader(8)
1350 newer than January 31, 2015, so make sure to update both world and
1351 kernel before rebooting.
1354 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1355 but before r278950, the RNG was not seeded properly. Immediately
1356 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1357 ssh keys or openssl keys) that were generated w/ a kernel from that
1358 range. This does not affect programs that directly used /dev/random
1359 or /dev/urandom. All userland uses of arc4random(3) are affected.
1362 The autofs(4) ABI was changed in order to restore binary compatibility
1363 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1364 with the new kernel.
1367 The powerpc64 kernel has been changed to a position-independent
1368 executable. This can only be booted with a new version of loader(8),
1369 so make sure to update both world and kernel before rebooting.
1372 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1373 only release, no new features have been added. Please see the 20141231
1374 entry below for information about prerequisites and upgrading, if you
1375 are not already using 3.5.0.
1378 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1379 taken from the ELF Tool Chain project rather than GNU binutils. They
1380 should be drop-in replacements, with the addition of arm64 support.
1381 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1382 binutils tools, if necessary. See 20150805 for updated information.
1385 The default Unbound configuration now enables remote control
1386 using a local socket. Users who have already enabled the
1387 local_unbound service should regenerate their configuration
1388 by running "service local_unbound setup" as root.
1391 The GNU texinfo and GNU info pages have been removed.
1392 To be able to view GNU info pages please install texinfo from ports.
1395 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1397 As of this release, a prerequisite for building clang, llvm and lldb is
1398 a C++11 capable compiler and C++11 standard library. This means that to
1399 be able to successfully build the cross-tools stage of buildworld, with
1400 clang as the bootstrap compiler, your system compiler or cross compiler
1401 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1402 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1405 On any standard FreeBSD 10.x or 11.x installation, where clang and
1406 libc++ are on by default (that is, on x86 or arm), this should work out
1409 On 9.x installations where clang is enabled by default, e.g. on x86 and
1410 powerpc, libc++ will not be enabled by default, so libc++ should be
1411 built (with clang) and installed first. If both clang and libc++ are
1412 missing, build clang first, then use it to build libc++.
1414 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1415 the instructions for 9.x above.
1417 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1418 default, and do not build clang.
1420 Many embedded systems are resource constrained, and will not be able to
1421 build clang in a reasonable time, or in some cases at all. In those
1422 cases, cross building bootable systems on amd64 is a workaround.
1424 This new version of clang introduces a number of new warnings, of which
1425 the following are most likely to appear:
1429 This warns in two cases, for both C and C++:
1430 * When the code is trying to take the absolute value of an unsigned
1431 quantity, which is effectively a no-op, and almost never what was
1432 intended. The code should be fixed, if at all possible. If you are
1433 sure that the unsigned quantity can be safely cast to signed, without
1434 loss of information or undefined behavior, you can add an explicit
1435 cast, or disable the warning.
1437 * When the code is trying to take an absolute value, but the called
1438 abs() variant is for the wrong type, which can lead to truncation.
1439 If you want to disable the warning instead of fixing the code, please
1440 make sure that truncation will not occur, or it might lead to unwanted
1443 -Wtautological-undefined-compare and
1444 -Wundefined-bool-conversion
1446 These warn when C++ code is trying to compare 'this' against NULL, while
1447 'this' should never be NULL in well-defined C++ code. However, there is
1448 some legacy (pre C++11) code out there, which actively abuses this
1449 feature, which was less strictly defined in previous C++ versions.
1451 Squid and openjdk do this, for example. The warning can be turned off
1452 for C++98 and earlier, but compiling the code in C++11 mode might result
1453 in unexpected behavior; for example, the parts of the program that are
1454 unreachable could be optimized away.
1457 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1458 kernel sources have been removed. The .h files remain, since some
1459 utilities include them. This will need to be fixed later.
1460 If "mount -t oldnfs ..." is attempted, it will fail.
1461 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1462 the utilities will report errors.
1465 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1466 directories to top level SUBDIR variable when their parent
1467 directory is included in LOCAL_DIRS. Users with build systems with
1468 such hierarchies and without SUBDIR entries in the parent
1469 directory Makefiles should add them or add the directories to
1473 faith(4) and faithd(8) have been removed from the base system. Faith
1474 has been obsolete for a very long time.
1477 vt(4), the new console driver, is enabled by default. It brings
1478 support for Unicode and double-width characters, as well as
1479 support for UEFI and integration with the KMS kernel video
1482 You may need to update your console settings in /etc/rc.conf,
1483 most probably the keymap. During boot, /etc/rc.d/syscons will
1484 indicate what you need to do.
1486 vt(4) still has issues and lacks some features compared to
1487 syscons(4). See the wiki for up-to-date information:
1488 https://wiki.freebsd.org/Newcons
1490 If you want to keep using syscons(4), you can do so by adding
1491 the following line to /boot/loader.conf:
1495 pjdfstest has been integrated into kyua as an opt-in test suite.
1496 Please see share/doc/pjdfstest/README for more details on how to
1500 gperf has been removed from the base system for architectures
1501 that use clang. Ports that require gperf will obtain it from the
1505 pjdfstest has been moved from tools/regression/pjdfstest to
1509 At svn r271982, The default linux compat kernel ABI has been adjusted
1510 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1511 update. If you wish to continue using the linux-f10 compat ports,
1512 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1513 encouraged to update their linux-compat packages to linux-c6 during
1514 their next update cycle.
1517 The ofwfb driver, used to provide a graphics console on PowerPC when
1518 using vt(4), no longer allows mmap() of all physical memory. This
1519 will prevent Xorg on PowerPC with some ATI graphics cards from
1520 initializing properly unless x11-servers/xorg-server is updated to
1524 The xdev targets have been converted to using TARGET and
1525 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1528 The default unbound configuration has been modified to address
1529 issues with reverse lookups on networks that use private
1530 address ranges. If you use the local_unbound service, run
1531 "service local_unbound setup" as root to regenerate your
1532 configuration, then "service local_unbound reload" to load the
1536 The GNU texinfo and GNU info pages are not built and installed
1537 anymore, WITH_INFO knob has been added to allow to built and install
1539 UPDATE: see 20150102 entry on texinfo's removal
1542 The GNU readline library is now an INTERNALLIB - that is, it is
1543 statically linked into consumers (GDB and variants) in the base
1544 system, and the shared library is no longer installed. The
1545 devel/readline port is available for third party software that
1549 The Itanium architecture (ia64) has been removed from the list of
1550 known architectures. This is the first step in the removal of the
1554 Commit r268115 has added NFSv4.1 server support, merged from
1555 projects/nfsv4.1-server. Since this includes changes to the
1556 internal interfaces between the NFS related modules, a full
1557 build of the kernel and modules will be necessary.
1558 __FreeBSD_version has been bumped.
1561 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1562 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1563 which differs from the behaviour controlled by this knob.)
1566 Maximal length of the serial number in CTL was increased from 16 to
1567 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1568 and ctld, need to be rebuilt to work with a new kernel.
1571 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1572 1 respectively to match the upstream numbers. They were out of
1573 sync because, when they were originally added to FreeBSD, the
1574 upstream versions were not respected. These libraries are private
1575 and not yet built by default, so renumbering them should be a
1576 non-issue. However, unclean source trees will yield broken test
1577 programs once the operator executes "make delete-old-libs" after a
1578 "make installworld".
1580 Additionally, the atf-sh binary was made private by moving it into
1581 /usr/libexec/. Already-built shell test programs will keep the
1582 path to the old binary so they will break after "make delete-old"
1585 If you are using WITH_TESTS=yes (not the default), wipe the object
1586 tree and rebuild from scratch to prevent spurious test failures.
1587 This is only needed once: the misnumbered libraries and misplaced
1588 binaries have been added to OptionalObsoleteFiles.inc so they will
1589 be removed during a clean upgrade.
1592 Clang and llvm have been upgraded to 3.4.1 release.
1595 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1596 be removed to avoid issues in the future (and has been added to
1600 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1601 past, it affected all builds that used the bsd.*.mk files. The old
1602 behavior was a bug, but people may have relied upon it. To get this
1603 behavior back, you can .include /etc/src.conf from /etc/make.conf
1604 (which is still global and isn't changed). This also changes the
1605 behavior of incremental builds inside the tree of individual
1606 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1607 Although this has survived make universe and some upgrade scenarios,
1608 other upgrade scenarios may have broken. At least one form of
1609 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1610 as well... In cases where MAKESYSPATH isn't working with this
1611 setting, you'll need to set it to the full path to your tree.
1613 One side effect of all this cleaning up is that bsd.compiler.mk
1614 is no longer implicitly included by bsd.own.mk. If you wish to
1615 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1619 The lindev device has been removed since /dev/full has been made a
1620 standard device. __FreeBSD_version has been bumped.
1623 The knob WITHOUT_VI was added to the base system, which controls
1624 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1625 in order to reorder files share/termcap and didn't build ex(1) as a
1626 build tool, so building/installing with WITH_VI is highly advised for
1627 build hosts for older releases.
1629 This issue has been fixed in stable/9 and stable/10 in r277022 and
1630 r276991, respectively.
1633 The YES_HESIOD knob has been removed. It has been obsolete for
1634 a decade. Please move to using WITH_HESIOD instead or your builds
1635 will silently lack HESIOD.
1638 The uart(4) driver has been changed with respect to its handling
1639 of the low-level console. Previously the uart(4) driver prevented
1640 any process from changing the baudrate or the CLOCAL and HUPCL
1641 control flags. By removing the restrictions, operators can make
1642 changes to the serial console port without having to reboot.
1643 However, when getty(8) is started on the serial device that is
1644 associated with the low-level console, a misconfigured terminal
1645 line in /etc/ttys will now have a real impact.
1646 Before upgrading the kernel, make sure that /etc/ttys has the
1647 serial console device configured as 3wire without baudrate to
1648 preserve the previous behaviour. E.g:
1649 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1652 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1653 to improve performance. To re-enable it, if needed, run rpcbind
1654 with command line option -W.
1657 Switched back to the GPL dtc compiler due to updates in the upstream
1658 dts files not being supported by the BSDL dtc compiler. You will need
1659 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1660 may result while building dtb files during a kernel build if you fail
1661 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1664 Clang and llvm have been upgraded to 3.4 release.
1667 The nve(4) driver has been removed. Please use the nfe(4) driver
1668 for NVIDIA nForce MCP Ethernet adapters instead.
1671 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1672 This could cause certain C++ applications using shared libraries built
1673 against the previous version of libc++ to crash. The incompatibility
1674 has now been fixed, but any C++ applications or shared libraries built
1675 between r261283 and r261801 should be recompiled.
1678 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1679 capability mode support. Please note that enabling the feature in
1680 kernel is still highly recommended.
1683 OpenSSH is now built with sandbox support, and will use sandbox as
1684 the default privilege separation method. This requires Capsicum
1685 capability mode support in kernel.
1688 The libelf and libdwarf libraries have been updated to newer
1689 versions from upstream. Shared library version numbers for
1690 these two libraries were bumped. Any ports or binaries
1691 requiring these two libraries should be recompiled.
1692 __FreeBSD_version is bumped to 1100006.
1695 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1696 instead of providing an explicit one, this would prevent such
1697 Makefile from providing its own Kyuafile in the future during
1698 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1699 intervention is needed to clean an objdir if you use NO_CLEAN:
1700 # find /usr/obj -name Kyuafile | xargs rm -f
1703 The behavior of gss_pseudo_random() for the krb5 mechanism
1704 has changed, for applications requesting a longer random string
1705 than produced by the underlying enctype's pseudo-random() function.
1706 In particular, the random string produced from a session key of
1707 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1708 be different at the 17th octet and later, after this change.
1709 The counter used in the PRF+ construction is now encoded as a
1710 big-endian integer in accordance with RFC 4402.
1711 __FreeBSD_version is bumped to 1100004.
1714 The WITHOUT_ATF build knob has been removed and its functionality
1715 has been subsumed into the more generic WITHOUT_TESTS. If you were
1716 using the former to disable the build of the ATF libraries, you
1717 should change your settings to use the latter.
1720 The default version of mtree is nmtree which is obtained from
1721 NetBSD. The output is generally the same, but may vary
1722 slightly. If you found you need identical output adding
1723 "-F freebsd9" to the command line should do the trick. For the
1724 time being, the old mtree is available as fmtree.
1727 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1728 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1729 1.1.4_8 and verify bsdyml not linked in, before running "make
1731 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1733 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1736 The stable/10 branch has been created in subversion from head
1743 Avoid using make -j when upgrading. While generally safe, there are
1744 sometimes problems using -j to upgrade. If your upgrade fails with
1745 -j, please try again without -j. From time to time in the past there
1746 have been problems using -j with buildworld and/or installworld. This
1747 is especially true when upgrading between "distant" versions (eg one
1748 that cross a major release boundary or several minor releases, or when
1749 several months have passed on the -current branch).
1751 Sometimes, obscure build problems are the result of environment
1752 poisoning. This can happen because the make utility reads its
1753 environment when searching for values for global variables. To run
1754 your build attempts in an "environmental clean room", prefix all make
1755 commands with 'env -i '. See the env(1) manual page for more details.
1757 When upgrading from one major version to another it is generally best to
1758 upgrade to the latest code in the currently installed branch first, then
1759 do an upgrade to the new branch. This is the best-tested upgrade path,
1760 and has the highest probability of being successful. Please try this
1761 approach if you encounter problems with a major version upgrade. Since
1762 the stable 4.x branch point, one has generally been able to upgrade from
1763 anywhere in the most recent stable branch to head / current (or even the
1764 last couple of stable branches). See the top of this file when there's
1767 When upgrading a live system, having a root shell around before
1768 installing anything can help undo problems. Not having a root shell
1769 around can lead to problems if pam has changed too much from your
1770 starting point to allow continued authentication after the upgrade.
1772 This file should be read as a log of events. When a later event changes
1773 information of a prior event, the prior event should not be deleted.
1774 Instead, a pointer to the entry with the new information should be
1775 placed in the old entry. Readers of this file should also sanity check
1776 older entries before relying on them blindly. Authors of new entries
1777 should write them with this in mind.
1781 When upgrading the boot ZFS pool to a new version, always follow
1784 1.) recompile and reinstall the ZFS boot loader and boot block
1785 (this is part of "make buildworld" and "make installworld")
1787 2.) update the ZFS boot block on your boot drive
1789 The following example updates the ZFS boot block on the first
1790 partition (freebsd-boot) of a GPT partitioned drive ada0:
1791 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1793 Non-boot pools do not need these updates.
1797 If you are updating from a prior version of FreeBSD (even one just
1798 a few days old), you should follow this procedure. It is the most
1799 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1801 make kernel-toolchain
1802 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1803 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1805 To test a kernel once
1806 ---------------------
1807 If you just want to boot a kernel once (because you are not sure
1808 if it works, or if you want to boot a known bad kernel to provide
1809 debugging information) run
1810 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1811 nextboot -k testkernel
1813 To rebuild everything and install it on the current system.
1814 -----------------------------------------------------------
1815 # Note: sometimes if you are running current you gotta do more than
1816 # is listed here if you are upgrading from a really old current.
1818 <make sure you have good level 0 dumps>
1820 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1821 make installkernel KERNCONF=YOUR_KERNEL_HERE
1823 <reboot in single user> [3]
1830 To cross-install current onto a separate partition
1831 --------------------------------------------------
1832 # In this approach we use a separate partition to hold
1833 # current's root, 'usr', and 'var' directories. A partition
1834 # holding "/", "/usr" and "/var" should be about 2GB in
1837 <make sure you have good level 0 dumps>
1840 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1841 <maybe newfs current's root partition>
1842 <mount current's root partition on directory ${CURRENT_ROOT}>
1843 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1844 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1845 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1846 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1847 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1848 <reboot into current>
1849 <do a "native" rebuild/install as described in the previous section>
1850 <maybe install compatibility libraries from ports/misc/compat*>
1854 To upgrade in-place from stable to current
1855 ----------------------------------------------
1856 <make sure you have good level 0 dumps>
1858 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1859 make installkernel KERNCONF=YOUR_KERNEL_HERE
1861 <reboot in single user> [3]
1868 Make sure that you've read the UPDATING file to understand the
1869 tweaks to various things you need. At this point in the life
1870 cycle of current, things change often and you are on your own
1871 to cope. The defaults can also change, so please read ALL of
1872 the UPDATING entries.
1874 Also, if you are tracking -current, you must be subscribed to
1875 freebsd-current@freebsd.org. Make sure that before you update
1876 your sources that you have read and understood all the recent
1877 messages there. If in doubt, please track -stable which has
1878 much fewer pitfalls.
1880 [1] If you have third party modules, such as vmware, you
1881 should disable them at this point so they don't crash your
1884 [3] From the bootblocks, boot -s, and then do
1889 adjkerntz -i # if CMOS is wall time
1890 Also, when doing a major release upgrade, it is required that
1891 you boot into single user mode to do the installworld.
1893 [4] Note: This step is non-optional. Failure to do this step
1894 can result in a significant reduction in the functionality of the
1895 system. Attempting to do it by hand is not recommended and those
1896 that pursue this avenue should read this file carefully, as well
1897 as the archives of freebsd-current and freebsd-hackers mailing lists
1898 for potential gotchas. The -U option is also useful to consider.
1899 See mergemaster(8) for more information.
1901 [5] Usually this step is a no-op. However, from time to time
1902 you may need to do this if you get unknown user in the following
1903 step. It never hurts to do it all the time. You may need to
1904 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1905 install) after the buildworld before this step if you last updated
1906 from current before 20130425 or from -stable before 20130430.
1908 [6] This only deletes old files and directories. Old libraries
1909 can be deleted by "make delete-old-libs", but you have to make
1910 sure that no program is using those libraries anymore.
1912 [8] In order to have a kernel that can run the 4.x binaries needed to
1913 do an installworld, you must include the COMPAT_FREEBSD4 option in
1914 your kernel. Failure to do so may leave you with a system that is
1915 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1916 required to run the 5.x binaries on more recent kernels. And so on
1917 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1919 Make sure that you merge any new devices from GENERIC since the
1920 last time you updated your kernel config file.
1922 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1923 "?=" instead of the "=" assignment operator, so that buildworld can
1924 override the CPUTYPE if it needs to.
1926 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1927 not on the command line, or in /etc/make.conf. buildworld will
1928 warn if it is improperly defined.
1931 This file contains a list, in reverse chronological order, of major
1932 breakages in tracking -current. It is not guaranteed to be a complete
1933 list of such breakages, and only contains entries since September 23, 2011.
1934 If you need to see UPDATING entries from before that date, you will need
1935 to fetch an UPDATING file from an older FreeBSD release.
1937 Copyright information:
1939 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1941 Redistribution, publication, translation and use, with or without
1942 modification, in full or in part, in any form or format of this
1943 document are permitted without further permission from the author.
1945 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1946 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1947 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1948 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1949 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1950 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1951 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1952 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1953 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1954 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1955 POSSIBILITY OF SUCH DAMAGE.
1957 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob