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 20190806 p2 FreeBSD-SA-19:18.bzip2
20 FreeBSD-SA-19:19.mldv2
21 FreeBSD-SA-19:20.bsnmp
22 FreeBSD-SA-19:21.bhyve
24 Fix multiple vulnerabilities in bzip2. [SA-19:18.bzip2]
26 Fix ICMPv6 / MLDv2 out-of-bounds memory access. [SA-19:19.mldv2]
28 Fix insufficient message length validation in bsnmp library.
31 Fix insufficient validation of guest-supplied data (e1000 device).
34 20190724 p1 FreeBSD-EN-19:13.mds
35 FreeBSD-SA-19:12.telnet
37 FreeBSD-SA-19:14.freebsd32
38 FreeBSD-SA-19:15.mqueuefs
39 FreeBSD-SA-19:16.bhyve
42 Fix panic from Intel CPU vulnerability mitigation. [EN-19:13.mds]
44 Fix multiple telnet client vulnerabilities. [SA-19:12.telnet]
46 Fix pts write-after-free. [SA-19:13.pts]
48 Fix kernel memory disclosure in freebsd32_ioctl. [SA-19:14.freebsd32]
50 Fix reference count overflow in mqueuefs. [SA-19:15.mqueuefs]
52 Fix byhve out-of-bounds read in XHCI device. [SA-19:16.bhyve]
54 Fix file descriptor reference count leak. [SA-19:17.fd]
59 20190702 FreeBSD-EN-19:12.tzdata
60 FreeBSD-SA-19:09.iconv
61 FreeBSD-SA-19:11.cd_ioctl
63 Import tzdata 2019b. [EN-19:12.tzdata]
65 Fix iconv buffer overflow. [SA-19:09.iconv]
67 Fix privilege escalation in cd(4) driver. [SA-19:11.cd_ioctl]
70 CARP now sets DSCP value CS7(Network Traffic) in the flowlabel field
71 of packets by default instead of only setting TOS_LOWDELAY in IPv4,
72 which was deprecated in 1998. Original behavior can be restored by
73 setting sysctl net.inet.carp.dscp=4.
76 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
77 8.0.0. Please see the 20141231 entry below for information about
78 prerequisites and upgrading, if you are not already using clang 3.5.0
82 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
83 compiled into your custom kernel, add 'device xz' statement to the
87 Co-existance for Forth and Lua interpreters in bootloaders has now been
88 merged to ease testing of lualoader. LOADER_DEFAULT_INTERP, documented
89 in build(7), may be used to control which interpreter flavor is used in
90 the default loader to be installed. For systems where Lua and Forth
91 coexist, this switch can also be made on a running system by creating a
92 link from /boot/loader{,.efi} to /boot/loader_${flavor}{,.efi} rather
93 than requiring a rebuild.
95 The default flavor in this branch will remain Forth. As indicated in
96 the 20190216 UPDATING entry, booting is a complex environment; it would
97 be prudent to assume that lualoader may not work for your setup and make
98 provisions for backup boot methods.
101 zfsloader's functionality has now been folded into loader.
102 zfsloader is no longer necesasary once you've updated your
103 boot blocks. For a transition period, we will install a
104 hardlink for zfsloader to loader to allow a smooth transition
105 until the boot blocks can be updated (hard link because old
106 zfs boot blocks don't understand symlinks).
109 Lualoader has been merged to facilitate testing on this branch. It's
110 purely opt-in for now by building WITH_LOADER_LUA and WITHOUT_FORTH in
111 /etc/src.conf, but co-existance will come shortly. Booting is a complex
112 environment and test coverage for Lua-enabled loaders has been thin, so
113 it would be prudent to assume it might not work and make provisions for
117 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
118 7.0.1. Please see the 20141231 entry below for information about
119 prerequisites and upgrading, if you are not already using clang 3.5.0
123 r342562 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
124 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
125 servers that have vfs.nfsd.nfs_privport set will only allow mounts
126 from clients using a reserved port#. Since both the FreeBSD and Linux
127 NFSv4 clients use reserved port#s by default, this should not affect
131 The '%I' format in the kern.corefile sysctl limits the number of
132 core files that a process can generate to the number stored in the
133 debug.ncores sysctl. The '%I' format is replaced by the single digit
134 index. Previously, if all indexes were taken the kernel would overwrite
135 only a core file with the highest index in a filename.
136 Currently the system will create a new core file if there is a free
137 index or if all slots are taken it will overwrite the oldest one.
140 WITH_OFED option now only enables the build for the OFED libraries
141 and some fundamental client utilities. OpenSM and rest of the
142 debugging tools are enabled by WITH_OFED_EXTRA build switch.
143 WITH_OFED is turned on by default on amd64.
146 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
147 6.0.1. Please see the 20141231 entry below for information about
148 prerequisites and upgrading, if you are not already using clang 3.5.0
152 The releng/11.2 branch has been created from stable/11@r334458.
155 The tz database (tzdb) has been updated to 2018e. This version more
156 correctly models time stamps in time zones with negative DST such as
157 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
158 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
159 time zone abbreviations and the tm_isdst flag.
162 The use of RSS hash from the network card aka flowid has been
163 disabled by default for lagg(4) as it's currently incompatible with
164 the lacp and loadbalance protocols.
166 This can be re-enabled by setting the following in loader.conf:
167 net.link.lagg.default_use_flowid="1"
170 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
171 6.0.0. Please see the 20141231 entry below for information about
172 prerequisites and upgrading, if you are not already using clang 3.5.0
176 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
177 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
178 to WITH/OUT_LOADER_GELI.
181 The geli password typed at boot is now hidden. To restore the previous
182 behavior, see geli(8) for configuration options.
184 The SW_WATCHDOG option is no longer necessary to enable the
185 hardclock-based software watchdog if no hardware watchdog is
186 configured. As before, SW_WATCHDOG will cause the software
187 watchdog to be enabled even if a hardware watchdog is configured.
190 lint(1) binaries and library are no longer built by default. To
191 enable building them, define WITH_LINT in src.conf. If you are using
192 a FreeBSD 12 or later system to build 11-stable, you may need to
193 install a lint(1) binary to use WITH_LINT.
196 When building multiple kernels using KERNCONF, non-existent KERNCONF
197 files will produce an error and buildkernel will fail. Previously
198 missing KERNCONF files silently failed giving no indication as to
199 why, only to subsequently discover during installkernel that the
200 desired kernel was never built in the first place.
203 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
204 Please see the 20141231 entry below for information about prerequisites
205 and upgrading, if you are not already using clang 3.5.0 or higher.
208 Since the switch to GPT disk labels, fsck for UFS/FFS has been
209 unable to automatically find alternate superblocks. As of r322806,
210 the information needed to find alternate superblocks has been
211 moved to the end of the area reserved for the boot block.
212 Filesystems created with a newfs of this vintage or later
213 will create the recovery information. If you have a filesystem
214 created prior to this change and wish to have a recovery block
215 created for your filesystem, you can do so by running fsck in
216 forground mode (i.e., do not use the -p or -y options). As it
217 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
218 to which you should answer yes.
221 The releng/11.1 branch has been created from stable/11@r320475.
224 arm64 builds now use the base system LLD 4.0.0 linker by default,
225 instead of requiring that the aarch64-binutils port or package be
226 installed. To continue using aarch64-binutils, set
227 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
230 The ctl.ko module no longer implements the iSCSI target frontend:
231 cfiscsi.ko does instead.
233 If building cfiscsi.ko as a kernel module, the module can be loaded
234 via one of the following methods:
235 - `cfiscsi_load="YES"` in loader.conf(5).
236 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
237 - ctladm(8)/ctld(8), when compiled with iSCSI support
238 (`WITH_ISCSI=yes` in src.conf(5))
240 Please see cfiscsi(4) for more details.
243 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
244 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
245 same source (previously, the dependency of mmcsd.ko on mmc.ko was
246 missing, but mmcsd.ko now will refuse to load if it is incompatible
250 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
251 use any explicitly assigned loopback address available in the jail
252 instead of using the first assigned address of the jail.
255 As of r316810 for ipfilter, keep frags is no longer assumed when
256 keep state is specified in a rule. r316810 aligns ipfilter with
257 documentation in man pages separating keep frags from keep state.
258 This allows keep state to specified without forcing keep frags
259 and allows keep frags to be specified independently of keep state.
260 To maintain previous behaviour, also specify keep frags with
261 keep state (as documented in ipf.conf.5).
264 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
265 Please see the 20141231 entry below for information about prerequisites
266 and upgrading, if you are not already using clang 3.5.0 or higher.
269 The code that provides support for ZFS .zfs/ directory functionality
270 has been reimplemented. It's not possible now to create a snapshot
271 by mkdir under .zfs/snapshot/. That should be the only user visible
275 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
276 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
277 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
278 and now NAT-T is supported by default. Security associations now use
279 the single namespace for SPI allocation, so if you use several manually
280 configured security associations with the same SPI, this configuration
284 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
285 Please see the 20141231 entry below for information about prerequisites
286 and upgrading, if you are not already using clang 3.5.0 or higher.
289 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
290 Please see the 20141231 entry below for information about prerequisites
291 and upgrading, if you are not already using clang 3.5.0 or higher.
294 The layout of the pmap structure has changed for powerpc to put the pmap
295 statistics at the front for all CPU variations. libkvm(3) and all tools
296 that link against it need to be recompiled.
299 isl(4) and cyapa(4) drivers now require a new driver,
300 chromebook_platform(4), to work properly on Chromebook-class hardware.
301 On other types of hardware the drivers may need to be configured using
302 device hints. Please see the corresponding manual pages for details.
305 Relocatable object files with the extension of .So have been renamed
306 to use an extension of .pico instead. The purpose of this change is
307 to avoid a name clash with shared libraries on case-insensitive file
308 systems. On those file systems, foo.So is the same file as foo.so.
311 The releng/11.0 branch has been created from stable/11@r303970.
314 The stable/11 branch has been created from head@r302406.
317 The libc stub for the pipe(2) system call has been replaced with
318 a wrapper that calls the pipe2(2) system call and the pipe(2)
319 system call is now only implemented by the kernels that include
320 "options COMPAT_FREEBSD10" in their config file (this is the
321 default). Users should ensure that this option is enabled in
322 their kernel or upgrade userspace to r302092 before upgrading their
326 CAM will now strip leading spaces from SCSI disks' serial numbers.
327 This will effect users who create UFS filesystems on SCSI disks using
328 those disk's diskid device nodes. For example, if /etc/fstab
329 previously contained a line like
330 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
331 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
332 transforms like gmirror may also be affected. ZFS users should
336 The bitstring(3) API has been updated with new functionality and
337 improved performance. But it is binary-incompatible with the old API.
338 Objects built with the new headers may not be linked against objects
339 built with the old headers.
342 The brk and sbrk functions have been removed from libc on arm64.
343 Binutils from ports has been updated to not link to these
344 functions and should be updated to the latest version before
345 installing a new libc.
348 The armv6 port now defaults to hard float ABI. Limited support
349 for running both hardfloat and soft float on the same system
350 is available using the libraries installed with -DWITH_LIBSOFT.
351 This has only been tested as an upgrade path for installworld
352 and packages may fail or need manual intervention to run. New
353 packages will be needed.
355 To update an existing self-hosted armv6hf system, you must add
356 TARGET_ARCH=armv6 on the make command line for both the build
357 and the install steps.
360 Kernel modules compiled outside of a kernel build now default to
361 installing to /boot/modules instead of /boot/kernel. Many kernel
362 modules built this way (such as those in ports) already overrode
363 KMODDIR explicitly to install into /boot/modules. However,
364 manually building and installing a module from /sys/modules will
365 now install to /boot/modules instead of /boot/kernel.
368 The CAM I/O scheduler has been committed to the kernel. There should be
369 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
370 list of known rogues that claim support for this but actually corrupt
371 data is believed to be complete, be on the lookout for data
372 corruption. The known rogue list is believed to be complete:
374 o Crucial MX100, M550 drives with MU01 firmware.
375 o Micron M510 and M550 drives with MU01 firmware.
376 o Micron M500 prior to MU07 firmware
377 o Samsung 830, 840, and 850 all firmwares
378 o FCCT M500 all firmwares
380 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
381 with working NCQ TRIM. For Micron branded drives, see your sales rep for
382 updated firmware. Black listed drives will work correctly because these
383 drives work correctly so long as no NCQ TRIMs are sent to them. Given
384 this list is the same as found in Linux, it's believed there are no
385 other rogues in the market place. All other models from the above
388 To be safe, if you are at all concerned, you can quirk each of your
389 drives to prevent NCQ from being sent by setting:
390 kern.cam.ada.X.quirks="0x2"
391 in loader.conf. If the drive requires the 4k sector quirk, set the
395 The FAST_DEPEND build option has been removed and its functionality is
396 now the one true way. The old mkdep(1) style of 'make depend' has
397 been removed. See 20160311 for further details.
400 Resource range types have grown from unsigned long to uintmax_t. All
401 drivers, and anything using libdevinfo, need to be recompiled.
404 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
405 builds. It no longer runs mkdep(1) during 'make depend', and the
406 'make depend' stage can safely be skipped now as it is auto ran
407 when building 'make all' and will generate all SRCS and DPSRCS before
408 building anything else. Dependencies are gathered at compile time with
409 -MF flags kept in separate .depend files per object file. Users should
410 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
414 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
415 kernel modules. Therefore, if you load any kernel modules at boot time,
416 please install the boot loaders after you install the kernel, but before
420 make kernel KERNCONF=YOUR_KERNEL_HERE
421 make -C sys/boot install
422 <reboot in single user>
424 Then follow the usual steps, described in the General Notes section,
428 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
429 see the 20141231 entry below for information about prerequisites and
430 upgrading, if you are not already using clang 3.5.0 or higher.
433 The AIO subsystem is now a standard part of the kernel. The
434 VFS_AIO kernel option and aio.ko kernel module have been removed.
435 Due to stability concerns, asynchronous I/O requests are only
436 permitted on sockets and raw disks by default. To enable
437 asynchronous I/O requests on all file types, set the
438 vfs.aio.enable_unsafe sysctl to a non-zero value.
441 The ELF object manipulation tool objcopy is now provided by the
442 ELF Tool Chain project rather than by GNU binutils. It should be a
443 drop-in replacement, with the addition of arm64 support. The
444 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
445 to obtain the GNU version if necessary.
448 Building ZFS pools on top of zvols is prohibited by default. That
449 feature has never worked safely; it's always been prone to deadlocks.
450 Using a zvol as the backing store for a VM guest's virtual disk will
451 still work, even if the guest is using ZFS. Legacy behavior can be
452 restored by setting vfs.zfs.vol.recursive=1.
455 The NONE and HPN patches has been removed from OpenSSH. They are
456 still available in the security/openssh-portable port.
459 With the addition of ypldap(8), a new _ypldap user is now required
460 during installworld. "mergemaster -p" can be used to add the user
461 prior to installworld, as documented in the handbook.
464 The tftp loader (pxeboot) now uses the option root-path directive. As a
465 consequence it no longer looks for a pxeboot.4th file on the tftp
466 server. Instead it uses the regular /boot infrastructure as with the
470 The code to start recording plug and play data into the modules has
471 been committed. While the old tools will properly build a new kernel,
472 a number of warnings about "unknown metadata record 4" will be produced
473 for an older kldxref. To avoid such warnings, make sure to rebuild
474 the kernel toolchain (or world). Make sure that you have r292078 or
475 later when trying to build 292077 or later before rebuilding.
478 Debug data files are now built by default with 'make buildworld' and
479 installed with 'make installworld'. This facilitates debugging but
480 requires more disk space both during the build and for the installed
481 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
485 r291527 changed the internal interface between the nfsd.ko and
486 nfscommon.ko modules. As such, they must both be upgraded to-gether.
487 __FreeBSD_version has been bumped because of this.
490 Add support for unicode collation strings leads to a change of
491 order of files listed by ls(1) for example. To get back to the old
492 behaviour, set LC_COLLATE environment variable to "C".
494 Databases administrators will need to reindex their databases given
495 collation results will be different.
497 Due to a bug in install(1) it is recommended to remove the ancient
498 locales before running make installworld.
500 rm -rf /usr/share/locale/*
503 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
504 libcrypto.so.7 or libssl.so.7 must be recompiled.
507 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
508 Kernel modules isp_2400_multi and isp_2500_multi were removed and
509 should be replaced with isp_2400 and isp_2500 modules respectively.
512 The build previously allowed using 'make -n' to not recurse into
513 sub-directories while showing what commands would be executed, and
514 'make -n -n' to recursively show commands. Now 'make -n' will recurse
515 and 'make -N' will not.
518 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
519 and etcupdate will now use this file. A custom sendmail.cf is now
520 updated via this mechanism rather than via installworld. If you had
521 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
522 want to remove the exclusion or change it to "always install".
523 /etc/mail/sendmail.cf is now managed the same way regardless of
524 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
525 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
528 Compatibility shims for legacy ATA device names have been removed.
529 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
530 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
531 environment variables, /dev/ad* and /dev/ar* symbolic links.
534 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
535 Please see the 20141231 entry below for information about prerequisites
536 and upgrading, if you are not already using clang 3.5.0 or higher.
539 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
540 and renamed from .symbols to .debug. This reduces the size requirements
541 on the boot partition or file system and provides consistency with
542 userland debug files.
544 When using the supported kernel installation method the
545 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
546 as is done with /boot/kernel.
548 Developers wishing to maintain the historical behavior of installing
549 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
552 The wireless drivers had undergone changes that remove the 'parent
553 interface' from the ifconfig -l output. The rc.d network scripts
554 used to check presence of a parent interface in the list, so old
555 scripts would fail to start wireless networking. Thus, etcupdate(3)
556 or mergemaster(8) run is required after kernel update, to update your
557 rc.d scripts in /etc.
560 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
561 These configurations are now automatically interpreted as
562 'scrub fragment reassemble'.
565 Kernel-loadable modules for the random(4) device are back. To use
566 them, the kernel must have
569 options RANDOM_LOADABLE
571 kldload(8) can then be used to load random_fortuna.ko
572 or random_yarrow.ko. Please note that due to the indirect
573 function calls that the loadable modules need to provide,
574 the build-in variants will be slightly more efficient.
576 The random(4) kernel option RANDOM_DUMMY has been retired due to
577 unpopularity. It was not all that useful anyway.
580 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
581 Control over building the ELF Tool Chain tools is now provided by
582 the WITHOUT_TOOLCHAIN knob.
585 The polarity of Pulse Per Second (PPS) capture events with the
586 uart(4) driver has been corrected. Prior to this change the PPS
587 "assert" event corresponded to the trailing edge of a positive PPS
588 pulse and the "clear" event was the leading edge of the next pulse.
590 As the width of a PPS pulse in a typical GPS receiver is on the
591 order of 1 millisecond, most users will not notice any significant
592 difference with this change.
594 Anyone who has compensated for the historical polarity reversal by
595 configuring a negative offset equal to the pulse width will need to
596 remove that workaround.
599 The default group assigned to /dev/dri entries has been changed
600 from 'wheel' to 'video' with the id of '44'. If you want to have
601 access to the dri devices please add yourself to the video group
604 # pw groupmod video -m $USER
607 The menu.rc and loader.rc files will now be replaced during
608 upgrades. Please migrate local changes to menu.rc.local and
609 loader.rc.local instead.
612 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
613 strings and strip have been removed. The src.conf(5) knob
614 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
617 As ZFS requires more kernel stack pages than is the default on some
618 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
619 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
621 Please consider using 'options KSTACK_PAGES=X' where X is greater
622 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
625 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
626 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
627 default, i.e., they will not contain "::". For example, instead
628 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
629 to have a more specific match, such as different map entries for
630 IPv6:0:0 vs IPv6:0. This change requires that configuration
631 data (including maps, files, classes, custom ruleset, etc.) must
632 use the same format, so make certain such configuration data is
633 upgrading. As a very simple check search for patterns like
634 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
635 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
636 the cf option UseCompressedIPv6Addresses.
639 The default kernel entropy-processing algorithm is now
640 Fortuna, replacing Yarrow.
642 Assuming you have 'device random' in your kernel config
643 file, the configurations allow a kernel option to override
644 this default. You may choose *ONE* of:
646 options RANDOM_YARROW # Legacy /dev/random algorithm.
647 options RANDOM_DUMMY # Blocking-only driver.
649 If you have neither, you get Fortuna. For most people,
650 read no further, Fortuna will give a /dev/random that works
651 like it always used to, and the difference will be irrelevant.
653 If you remove 'device random', you get *NO* kernel-processed
654 entropy at all. This may be acceptable to folks building
655 embedded systems, but has complications. Carry on reading,
656 and it is assumed you know what you need.
658 *PLEASE* read random(4) and random(9) if you are in the
659 habit of tweaking kernel configs, and/or if you are a member
660 of the embedded community, wanting specific and not-usual
661 behaviour from your security subsystems.
663 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
664 random', you will NOT have a functioning /dev/random, and
665 many cryptographic features will not work, including SSH.
666 You may also find strange behaviour from the random(3) set
667 of library functions, in particular sranddev(3), srandomdev(3)
668 and arc4random(3). The reason for this is that the KERN_ARND
669 sysctl only returns entropy if it thinks it has some to
670 share, and with RANDOM_DUMMY or no 'device random' this
674 An additional fix for the issue described in the 20150614 sendmail
675 entry below has been been committed in revision 284717.
678 FreeBSD's old make (fmake) has been removed from the system. It is
679 available as the devel/fmake port or via pkg install fmake.
682 The fix for the issue described in the 20150614 sendmail entry
683 below has been been committed in revision 284436. The work
684 around described in that entry is no longer needed unless the
685 default setting is overridden by a confDH_PARAMETERS configuration
686 setting of '5' or pointing to a 512 bit DH parameter file.
689 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
690 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
691 and devel/kyua to version 0.20+ and adjust any calling code to work
692 with Kyuafile and kyua.
695 The import of openssl to address the FreeBSD-SA-15:10.openssl
696 security advisory includes a change which rejects handshakes
697 with DH parameters below 768 bits. sendmail releases prior
698 to 8.15.2 (not yet released), defaulted to a 512 bit
699 DH parameter setting for client connections. To work around
700 this interoperability, sendmail can be configured to use a
701 2048 bit DH parameter by:
703 1. Edit /etc/mail/`hostname`.mc
704 2. If a setting for confDH_PARAMETERS does not exist or
705 exists and is set to a string beginning with '5',
707 3. If a setting for confDH_PARAMETERS exists and is set to
708 a file path, create a new file with:
709 openssl dhparam -out /path/to/file 2048
710 4. Rebuild the .cf file:
711 cd /etc/mail/; make; make install
713 cd /etc/mail/; make restart
715 A sendmail patch is coming, at which time this file will be
719 Generation of legacy formatted entries have been disabled by default
720 in pwd_mkdb(8), as all base system consumers of the legacy formatted
721 entries were converted to use the new format by default when the new,
722 machine independent format have been added and supported since FreeBSD
725 Please see the pwd_mkdb(8) manual page for further details.
728 Clang and llvm have been upgraded to 3.6.1 release. Please see the
729 20141231 entry below for information about prerequisites and upgrading,
730 if you are not already using 3.5.0 or higher.
733 TI platform code switched to using vendor DTS files and this update
734 may break existing systems running on Beaglebone, Beaglebone Black,
737 - dtb files should be regenerated/reinstalled. Filenames are the
738 same but content is different now
739 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
740 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
741 addressing scheme is now pin 25 on /dev/gpioc3.
742 - Pandaboard: /etc/ttys should be updated, serial console device is
743 now /dev/ttyu2, not /dev/ttyu0
746 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
747 If you need the GNU extension from groff soelim(1), install groff
748 from package: pkg install groff, or via ports: textproc/groff.
751 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
752 defined in symlink(7); previously symlinks were silently ignored.
755 The const qualifier has been removed from iconv(3) to comply with
756 POSIX. The ports tree is aware of this from r384038 onwards.
759 Libraries specified by LIBADD in Makefiles must have a corresponding
760 DPADD_<lib> variable to ensure correct dependencies. This is now
761 enforced in src.libnames.mk.
764 From legacy ata(4) driver was removed support for SATA controllers
765 supported by more functional drivers ahci(4), siis(4) and mvs(4).
766 Kernel modules ataahci and ataadaptec were removed completely,
767 replaced by ahci and mvs modules respectively.
770 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
771 the 20141231 entry below for information about prerequisites and
772 upgrading, if you are not already using 3.5.0 or higher.
775 The 32-bit PowerPC kernel has been changed to a position-independent
776 executable. This can only be booted with a version of loader(8)
777 newer than January 31, 2015, so make sure to update both world and
778 kernel before rebooting.
781 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
782 but before r278950, the RNG was not seeded properly. Immediately
783 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
784 ssh keys or openssl keys) that were generated w/ a kernel from that
785 range. This does not affect programs that directly used /dev/random
786 or /dev/urandom. All userland uses of arc4random(3) are affected.
789 The autofs(4) ABI was changed in order to restore binary compatibility
790 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
794 The powerpc64 kernel has been changed to a position-independent
795 executable. This can only be booted with a new version of loader(8),
796 so make sure to update both world and kernel before rebooting.
799 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
800 only release, no new features have been added. Please see the 20141231
801 entry below for information about prerequisites and upgrading, if you
802 are not already using 3.5.0.
805 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
806 taken from the ELF Tool Chain project rather than GNU binutils. They
807 should be drop-in replacements, with the addition of arm64 support.
808 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
809 binutils tools, if necessary. See 20150805 for updated information.
812 The default Unbound configuration now enables remote control
813 using a local socket. Users who have already enabled the
814 local_unbound service should regenerate their configuration
815 by running "service local_unbound setup" as root.
818 The GNU texinfo and GNU info pages have been removed.
819 To be able to view GNU info pages please install texinfo from ports.
822 Clang, llvm and lldb have been upgraded to 3.5.0 release.
824 As of this release, a prerequisite for building clang, llvm and lldb is
825 a C++11 capable compiler and C++11 standard library. This means that to
826 be able to successfully build the cross-tools stage of buildworld, with
827 clang as the bootstrap compiler, your system compiler or cross compiler
828 should either be clang 3.3 or later, or gcc 4.8 or later, and your
829 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
832 On any standard FreeBSD 10.x or 11.x installation, where clang and
833 libc++ are on by default (that is, on x86 or arm), this should work out
836 On 9.x installations where clang is enabled by default, e.g. on x86 and
837 powerpc, libc++ will not be enabled by default, so libc++ should be
838 built (with clang) and installed first. If both clang and libc++ are
839 missing, build clang first, then use it to build libc++.
841 On 8.x and earlier installations, upgrade to 9.x first, and then follow
842 the instructions for 9.x above.
844 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
845 default, and do not build clang.
847 Many embedded systems are resource constrained, and will not be able to
848 build clang in a reasonable time, or in some cases at all. In those
849 cases, cross building bootable systems on amd64 is a workaround.
851 This new version of clang introduces a number of new warnings, of which
852 the following are most likely to appear:
856 This warns in two cases, for both C and C++:
857 * When the code is trying to take the absolute value of an unsigned
858 quantity, which is effectively a no-op, and almost never what was
859 intended. The code should be fixed, if at all possible. If you are
860 sure that the unsigned quantity can be safely cast to signed, without
861 loss of information or undefined behavior, you can add an explicit
862 cast, or disable the warning.
864 * When the code is trying to take an absolute value, but the called
865 abs() variant is for the wrong type, which can lead to truncation.
866 If you want to disable the warning instead of fixing the code, please
867 make sure that truncation will not occur, or it might lead to unwanted
870 -Wtautological-undefined-compare and
871 -Wundefined-bool-conversion
873 These warn when C++ code is trying to compare 'this' against NULL, while
874 'this' should never be NULL in well-defined C++ code. However, there is
875 some legacy (pre C++11) code out there, which actively abuses this
876 feature, which was less strictly defined in previous C++ versions.
878 Squid and openjdk do this, for example. The warning can be turned off
879 for C++98 and earlier, but compiling the code in C++11 mode might result
880 in unexpected behavior; for example, the parts of the program that are
881 unreachable could be optimized away.
884 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
885 kernel sources have been removed. The .h files remain, since some
886 utilities include them. This will need to be fixed later.
887 If "mount -t oldnfs ..." is attempted, it will fail.
888 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
889 the utilities will report errors.
892 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
893 directories to top level SUBDIR variable when their parent
894 directory is included in LOCAL_DIRS. Users with build systems with
895 such hierarchies and without SUBDIR entries in the parent
896 directory Makefiles should add them or add the directories to
900 faith(4) and faithd(8) have been removed from the base system. Faith
901 has been obsolete for a very long time.
904 vt(4), the new console driver, is enabled by default. It brings
905 support for Unicode and double-width characters, as well as
906 support for UEFI and integration with the KMS kernel video
909 You may need to update your console settings in /etc/rc.conf,
910 most probably the keymap. During boot, /etc/rc.d/syscons will
911 indicate what you need to do.
913 vt(4) still has issues and lacks some features compared to
914 syscons(4). See the wiki for up-to-date information:
915 https://wiki.freebsd.org/Newcons
917 If you want to keep using syscons(4), you can do so by adding
918 the following line to /boot/loader.conf:
922 pjdfstest has been integrated into kyua as an opt-in test suite.
923 Please see share/doc/pjdfstest/README for more details on how to
927 gperf has been removed from the base system for architectures
928 that use clang. Ports that require gperf will obtain it from the
932 pjdfstest has been moved from tools/regression/pjdfstest to
936 At svn r271982, The default linux compat kernel ABI has been adjusted
937 to 2.6.18 in support of the linux-c6 compat ports infrastructure
938 update. If you wish to continue using the linux-f10 compat ports,
939 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
940 encouraged to update their linux-compat packages to linux-c6 during
941 their next update cycle.
944 The ofwfb driver, used to provide a graphics console on PowerPC when
945 using vt(4), no longer allows mmap() of all physical memory. This
946 will prevent Xorg on PowerPC with some ATI graphics cards from
947 initializing properly unless x11-servers/xorg-server is updated to
951 The xdev targets have been converted to using TARGET and
952 TARGET_ARCH instead of XDEV and XDEV_ARCH.
955 The default unbound configuration has been modified to address
956 issues with reverse lookups on networks that use private
957 address ranges. If you use the local_unbound service, run
958 "service local_unbound setup" as root to regenerate your
959 configuration, then "service local_unbound reload" to load the
963 The GNU texinfo and GNU info pages are not built and installed
964 anymore, WITH_INFO knob has been added to allow to built and install
966 UPDATE: see 20150102 entry on texinfo's removal
969 The GNU readline library is now an INTERNALLIB - that is, it is
970 statically linked into consumers (GDB and variants) in the base
971 system, and the shared library is no longer installed. The
972 devel/readline port is available for third party software that
976 The Itanium architecture (ia64) has been removed from the list of
977 known architectures. This is the first step in the removal of the
981 Commit r268115 has added NFSv4.1 server support, merged from
982 projects/nfsv4.1-server. Since this includes changes to the
983 internal interfaces between the NFS related modules, a full
984 build of the kernel and modules will be necessary.
985 __FreeBSD_version has been bumped.
988 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
989 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
990 which differs from the behaviour controlled by this knob.)
993 Maximal length of the serial number in CTL was increased from 16 to
994 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
995 and ctld, need to be rebuilt to work with a new kernel.
998 The libatf-c and libatf-c++ major versions were downgraded to 0 and
999 1 respectively to match the upstream numbers. They were out of
1000 sync because, when they were originally added to FreeBSD, the
1001 upstream versions were not respected. These libraries are private
1002 and not yet built by default, so renumbering them should be a
1003 non-issue. However, unclean source trees will yield broken test
1004 programs once the operator executes "make delete-old-libs" after a
1005 "make installworld".
1007 Additionally, the atf-sh binary was made private by moving it into
1008 /usr/libexec/. Already-built shell test programs will keep the
1009 path to the old binary so they will break after "make delete-old"
1012 If you are using WITH_TESTS=yes (not the default), wipe the object
1013 tree and rebuild from scratch to prevent spurious test failures.
1014 This is only needed once: the misnumbered libraries and misplaced
1015 binaries have been added to OptionalObsoleteFiles.inc so they will
1016 be removed during a clean upgrade.
1019 Clang and llvm have been upgraded to 3.4.1 release.
1022 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1023 be removed to avoid issues in the future (and has been added to
1027 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1028 past, it affected all builds that used the bsd.*.mk files. The old
1029 behavior was a bug, but people may have relied upon it. To get this
1030 behavior back, you can .include /etc/src.conf from /etc/make.conf
1031 (which is still global and isn't changed). This also changes the
1032 behavior of incremental builds inside the tree of individual
1033 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1034 Although this has survived make universe and some upgrade scenarios,
1035 other upgrade scenarios may have broken. At least one form of
1036 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1037 as well... In cases where MAKESYSPATH isn't working with this
1038 setting, you'll need to set it to the full path to your tree.
1040 One side effect of all this cleaning up is that bsd.compiler.mk
1041 is no longer implicitly included by bsd.own.mk. If you wish to
1042 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1046 The lindev device has been removed since /dev/full has been made a
1047 standard device. __FreeBSD_version has been bumped.
1050 The knob WITHOUT_VI was added to the base system, which controls
1051 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1052 in order to reorder files share/termcap and didn't build ex(1) as a
1053 build tool, so building/installing with WITH_VI is highly advised for
1054 build hosts for older releases.
1056 This issue has been fixed in stable/9 and stable/10 in r277022 and
1057 r276991, respectively.
1060 The YES_HESIOD knob has been removed. It has been obsolete for
1061 a decade. Please move to using WITH_HESIOD instead or your builds
1062 will silently lack HESIOD.
1065 The uart(4) driver has been changed with respect to its handling
1066 of the low-level console. Previously the uart(4) driver prevented
1067 any process from changing the baudrate or the CLOCAL and HUPCL
1068 control flags. By removing the restrictions, operators can make
1069 changes to the serial console port without having to reboot.
1070 However, when getty(8) is started on the serial device that is
1071 associated with the low-level console, a misconfigured terminal
1072 line in /etc/ttys will now have a real impact.
1073 Before upgrading the kernel, make sure that /etc/ttys has the
1074 serial console device configured as 3wire without baudrate to
1075 preserve the previous behaviour. E.g:
1076 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1079 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1080 to improve performance. To re-enable it, if needed, run rpcbind
1081 with command line option -W.
1084 Switched back to the GPL dtc compiler due to updates in the upstream
1085 dts files not being supported by the BSDL dtc compiler. You will need
1086 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1087 may result while building dtb files during a kernel build if you fail
1088 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1091 Clang and llvm have been upgraded to 3.4 release.
1094 The nve(4) driver has been removed. Please use the nfe(4) driver
1095 for NVIDIA nForce MCP Ethernet adapters instead.
1098 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1099 This could cause certain C++ applications using shared libraries built
1100 against the previous version of libc++ to crash. The incompatibility
1101 has now been fixed, but any C++ applications or shared libraries built
1102 between r261283 and r261801 should be recompiled.
1105 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1106 capability mode support. Please note that enabling the feature in
1107 kernel is still highly recommended.
1110 OpenSSH is now built with sandbox support, and will use sandbox as
1111 the default privilege separation method. This requires Capsicum
1112 capability mode support in kernel.
1115 The libelf and libdwarf libraries have been updated to newer
1116 versions from upstream. Shared library version numbers for
1117 these two libraries were bumped. Any ports or binaries
1118 requiring these two libraries should be recompiled.
1119 __FreeBSD_version is bumped to 1100006.
1122 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1123 instead of providing an explicit one, this would prevent such
1124 Makefile from providing its own Kyuafile in the future during
1125 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1126 intervention is needed to clean an objdir if you use NO_CLEAN:
1127 # find /usr/obj -name Kyuafile | xargs rm -f
1130 The behavior of gss_pseudo_random() for the krb5 mechanism
1131 has changed, for applications requesting a longer random string
1132 than produced by the underlying enctype's pseudo-random() function.
1133 In particular, the random string produced from a session key of
1134 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1135 be different at the 17th octet and later, after this change.
1136 The counter used in the PRF+ construction is now encoded as a
1137 big-endian integer in accordance with RFC 4402.
1138 __FreeBSD_version is bumped to 1100004.
1141 The WITHOUT_ATF build knob has been removed and its functionality
1142 has been subsumed into the more generic WITHOUT_TESTS. If you were
1143 using the former to disable the build of the ATF libraries, you
1144 should change your settings to use the latter.
1147 The default version of mtree is nmtree which is obtained from
1148 NetBSD. The output is generally the same, but may vary
1149 slightly. If you found you need identical output adding
1150 "-F freebsd9" to the command line should do the trick. For the
1151 time being, the old mtree is available as fmtree.
1154 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1155 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1156 1.1.4_8 and verify bsdyml not linked in, before running "make
1158 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1160 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1163 The stable/10 branch has been created in subversion from head
1167 The rc.d/jail script has been updated to support jail(8)
1168 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1169 for per-jail configuration are automatically converted to
1170 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1171 This is transparently backward compatible. See below about some
1172 incompatibilities and rc.conf(5) manual page for more details.
1174 These variables are now deprecated in favor of jail(8) configuration
1175 file. One can use "rc.d/jail config <jname>" command to generate
1176 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1177 running the jail(8) utility. The default pathname of the
1178 configuration file is /etc/jail.conf and can be specified by
1179 using $jail_conf or $jail_<jname>_conf variables.
1181 Please note that jail_devfs_ruleset accepts an integer at
1182 this moment. Please consider to rewrite the ruleset name
1186 BIND has been removed from the base system. If all you need
1187 is a local resolver, simply enable and start the local_unbound
1188 service instead. Otherwise, several versions of BIND are
1189 available in the ports tree. The dns/bind99 port is one example.
1191 With this change, nslookup(1) and dig(1) are no longer in the base
1192 system. Users should instead use host(1) and drill(1) which are
1193 in the base system. Alternatively, nslookup and dig can
1194 be obtained by installing the dns/bind-tools port.
1197 With the addition of unbound(8), a new unbound user is now
1198 required during installworld. "mergemaster -p" can be used to
1199 add the user prior to installworld, as documented in the handbook.
1202 OpenSSH is now built with DNSSEC support, and will by default
1203 silently trust signed SSHFP records. This can be controlled with
1204 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1205 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1208 The GNU Compiler Collection and C++ standard library (libstdc++)
1209 are no longer built by default on platforms where clang is the system
1210 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1211 options in src.conf.
1214 The PROCDESC kernel option is now part of the GENERIC kernel
1215 configuration and is required for the rwhod(8) to work.
1216 If you are using custom kernel configuration, you should include
1220 The API and ABI related to the Capsicum framework was modified
1221 in backward incompatible way. The userland libraries and programs
1222 have to be recompiled to work with the new kernel. This includes the
1223 following libraries and programs, but the whole buildworld is
1224 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1225 kdump, procstat, rwho, rwhod, uniq.
1228 AES-NI intrinsic support has been added to gcc. The AES-NI module
1229 has been updated to use this support. A new gcc is required to build
1230 the aesni module on both i386 and amd64.
1233 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1234 Thus "device padlock_rng" and "device rdrand_rng" should be
1235 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1238 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1239 enables just the iconv* functionality and is now on by default.
1240 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1241 compatibility. Set WITHOUT_ICONV to build the old way.
1242 If you have been using WITH_ICONV before, you will very likely
1243 need to turn on WITH_LIBICONV_COMPAT.
1246 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1247 Illumos origin, including ZFS. If you have INVARIANTS in your
1248 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1250 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1251 locks if WITNESS option was set. Because that generated a lot of
1252 witness(9) reports and all of them were believed to be false
1253 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1254 can be used to achieve the previous behavior.
1257 Timer values in IPv6 data structures now use time_uptime instead
1258 of time_second. Although this is not a user-visible functional
1259 change, userland utilities which directly use them---ndp(8),
1260 rtadvd(8), and rtsold(8) in the base system---need to be updated
1261 to r253970 or later.
1264 find -delete can now delete the pathnames given as arguments,
1265 instead of only files found below them or if the pathname did
1266 not contain any slashes. Formerly, the following error message
1269 find: -delete: <path>: relative path potentially not safe
1271 Deleting the pathnames given as arguments can be prevented
1272 without error messages using -mindepth 1 or by changing
1273 directory and passing "." as argument to find. This works in the
1274 old as well as the new version of find.
1277 Behavior of devfs rules path matching has been changed.
1278 Pattern is now always matched against fully qualified devfs
1279 path and slash characters must be explicitly matched by
1280 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1281 subdirectories must be reviewed.
1284 The default ARM ABI has changed to the ARM EABI. The old ABI is
1285 incompatible with the ARM EABI and all programs and modules will
1286 need to be rebuilt to work with a new kernel.
1288 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1290 NOTE: Support for the old ABI will be removed in the future and
1291 users are advised to upgrade.
1294 pkg_install has been disconnected from the build if you really need it
1295 you should add WITH_PKGTOOLS in your src.conf(5).
1298 Most of network statistics structures were changed to be able
1299 keep 64-bits counters. Thus all tools, that work with networking
1300 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1303 Fix a bug that allowed a tracing process (e.g. gdb) to write
1304 to a memory-mapped file in the traced process's address space
1305 even if neither the traced process nor the tracing process had
1306 write access to that file.
1309 CVS has been removed from the base system. An exact copy
1310 of the code is available from the devel/cvs port.
1313 Some people report the following error after the switch to bmake:
1315 make: illegal option -- J
1316 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1318 *** [buildworld] Error code 2
1320 this likely due to an old instance of make in
1321 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1322 which src/Makefile will use that blindly, if it exists, so if
1323 you see the above error:
1325 rm -rf `make -V MAKEPATH`
1330 Use bmake by default.
1331 Whereas before one could choose to build with bmake via
1332 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1333 make. The goal is to remove these knobs for 10-RELEASE.
1335 It is worth noting that bmake (like gmake) treats the command
1336 line as the unit of failure, rather than statements within the
1337 command line. Thus '(cd some/where && dosomething)' is safer
1338 than 'cd some/where; dosomething'. The '()' allows consistent
1339 behavior in parallel build.
1342 Fix a bug that allows NFS clients to issue READDIR on files.
1345 The WITHOUT_IDEA option has been removed because
1346 the IDEA patent expired.
1349 The sysctl which controls TRIM support under ZFS has been renamed
1350 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1354 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1355 rather than creating it's own in the temporary directory in
1356 order allow access to bootstrapped versions of tools such as
1357 install and mtree. When upgrading from version of FreeBSD where
1358 the install command does not support -l, you will need to
1359 install a new mergemaster command if mergemaster -p is required.
1360 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1364 Legacy ATA stack, disabled and replaced by new CAM-based one since
1365 FreeBSD 9.0, completely removed from the sources. Kernel modules
1366 atadisk and atapi*, user-level tools atacontrol and burncd are
1367 removed. Kernel option `options ATA_CAM` is now permanently enabled
1371 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1372 and socketpair(2). Software, in particular Kerberos, may
1373 automatically detect and use these during building. The resulting
1374 binaries will not work on older kernels.
1377 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1378 information, see the respective 20130304 entry).
1381 Recent commits to callout(9) changed the size of struct callout,
1382 so the KBI is probably heavily disturbed. Also, some functions
1383 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1384 by macros. Every kernel module using it won't load, so rebuild
1387 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1388 but does not initialize by default (because of the new CTL_DISABLE
1389 option) to save memory. To re-enable it, remove the CTL_DISABLE
1390 option from the kernel config file or set kern.cam.ctl.disable=0
1391 in /boot/loader.conf.
1394 The ctl device has been disabled in GENERIC for i386 and amd64.
1395 This was done due to the extra memory being allocated at system
1396 initialisation time by the ctl driver which was only used if
1397 a CAM target device was created. This makes a FreeBSD system
1398 unusable on 128MB or less of RAM.
1401 A new compression method (lz4) has been merged to -HEAD. Please
1402 refer to zpool-features(7) for more information.
1404 Please refer to the "ZFS notes" section of this file for information
1405 on upgrading boot ZFS pools.
1408 A BSD-licensed patch(1) variant has been added and is installed
1409 as bsdpatch, being the GNU version the default patch.
1410 To inverse the logic and use the BSD-licensed one as default,
1411 while having the GNU version installed as gnupatch, rebuild
1412 and install world with the WITH_BSD_PATCH knob set.
1415 Due to the use of the new -l option to install(1) during build
1416 and install, you must take care not to directly set the INSTALL
1417 make variable in your /etc/make.conf, /etc/src.conf, or on the
1418 command line. If you wish to use the -C flag for all installs
1419 you may be able to add INSTALL+=-C to /etc/make.conf or
1423 The install(1) option -M has changed meaning and now takes an
1424 argument that is a file or path to append logs to. In the
1425 unlikely event that -M was the last option on the command line
1426 and the command line contained at least two files and a target
1427 directory the first file will have logs appended to it. The -M
1428 option served little practical purpose in the last decade so its
1429 use is expected to be extremely rare.
1432 After switching to Clang as the default compiler some users of ZFS
1433 on i386 systems started to experience stack overflow kernel panics.
1434 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1437 GEOM_LABEL now mangles label names read from file system metadata.
1438 Mangling affect labels containing spaces, non-printable characters,
1439 '%' or '"'. Device names in /etc/fstab and other places may need to
1443 By default, only the 10 most recent kernel dumps will be saved. To
1444 restore the previous behaviour (no limit on the number of kernel dumps
1445 stored in the dump directory) add the following line to /etc/rc.conf:
1450 With the addition of auditdistd(8), a new auditdistd user is now
1451 required during installworld. "mergemaster -p" can be used to
1452 add the user prior to installworld, as documented in the handbook.
1455 The sin6_scope_id member variable in struct sockaddr_in6 is now
1456 filled by the kernel before passing the structure to the userland via
1457 sysctl or routing socket. This means the KAME-specific embedded scope
1458 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1459 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1460 __FreeBSD_version is bumped to 1000025.
1463 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1464 This means that the world and kernel will be compiled with clang
1465 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1466 and /usr/bin/cpp. To disable this behavior and revert to building
1467 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1468 of current may need to bootstrap WITHOUT_CLANG first if the clang
1469 build fails (its compatibility window doesn't extend to the 9 stable
1473 The IPFIREWALL_FORWARD kernel option has been removed. Its
1474 functionality now turned on by default.
1477 The ZERO_COPY_SOCKET kernel option has been removed and
1478 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1479 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1480 mechanism which is not safe and may result in kernel crashes.
1481 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1482 driver supports disposeable external page sized mbuf storage.
1483 Proper replacements for both zero-copy mechanisms are under
1484 consideration and will eventually lead to complete removal
1485 of the two kernel options.
1488 The IPv4 network stack has been converted to network byte
1489 order. The following modules need to be recompiled together
1490 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1491 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1494 Support for non-MPSAFE filesystems was removed from VFS. The
1495 VFS_VERSION was bumped, all filesystem modules shall be
1499 All the non-MPSAFE filesystems have been disconnected from
1500 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1501 portalfs, smbfs, xfs.
1504 The interface cloning API and ABI has changed. The following
1505 modules need to be recompiled together with kernel:
1506 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1507 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1508 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1511 The sdhci driver was split in two parts: sdhci (generic SD Host
1512 Controller logic) and sdhci_pci (actual hardware driver).
1513 No kernel config modifications are required, but if you
1514 load sdhc as a module you must switch to sdhci_pci instead.
1517 Import the FUSE kernel and userland support into base system.
1520 The GNU sort(1) program has been removed since the BSD-licensed
1521 sort(1) has been the default for quite some time and no serious
1522 problems have been reported. The corresponding WITH_GNU_SORT
1526 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1527 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1531 The net80211(4) ABI has been changed to allow for improved driver
1532 PS-POLL and power-save support. All wireless drivers need to be
1533 recompiled to work with the new kernel.
1536 The random(4) support for the VIA hardware random number
1537 generator (`PADLOCK') is no longer enabled unconditionally.
1538 Add the padlock_rng device in the custom kernel config if
1539 needed. The GENERIC kernels on i386 and amd64 do include the
1540 device, so the change only affects the custom kernel
1544 The pf(4) packet filter ABI has been changed. pfctl(8) and
1545 snmp_pf module need to be recompiled to work with new kernel.
1548 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1549 to -HEAD. Pools that have empty_bpobj in active state can not be
1550 imported read-write with ZFS implementations that do not support
1551 this feature. For more information read the zpool-features(5)
1555 The sparc64 ZFS loader has been changed to no longer try to auto-
1556 detect ZFS providers based on diskN aliases but now requires these
1557 to be explicitly listed in the OFW boot-device environment variable.
1560 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1561 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1562 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1565 The following sysctls and tunables have been renamed for consistency
1566 with other variables:
1567 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1568 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1571 The sort utility has been replaced with BSD sort. For now, GNU sort
1572 is also available as "gnusort" or the default can be set back to
1573 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1574 installed as "bsdsort".
1577 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1578 Starting with this version the old system of ZFS pool versioning
1579 is superseded by "feature flags". This concept enables forward
1580 compatibility against certain future changes in functionality of ZFS
1581 pools. The first read-only compatible "feature flag" for ZFS pools
1582 is named "com.delphix:async_destroy". For more information
1583 read the new zpool-features(5) manual page.
1584 Please refer to the "ZFS notes" section of this file for information
1585 on upgrading boot ZFS pools.
1588 The malloc(3) implementation embedded in libc now uses sources imported
1589 as contrib/jemalloc. The most disruptive API change is to
1590 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1591 delete it prior to installworld, and optionally re-create it using the
1592 new format after rebooting. See malloc.conf(5) for details
1593 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1597 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1598 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1599 now spelled mips. This is to aid compatibility with third-party
1600 software that expects this naming scheme in uname(3). Little-endian
1601 settings are unchanged. If you are updating a big-endian mips64 machine
1602 from before this change, you may need to set MACHINE_ARCH=mips64 in
1603 your environment before the new build system will recognize your machine.
1606 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1610 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1611 nullfs(5) did not pass through all behaviours to the underlying layer,
1612 as a result if we bound to a socket on the lower layer we could connect
1613 only to the lower path; if we bound to the upper layer we could connect
1614 only to the upper path. The new behavior is one can connect to both the
1615 lower and the upper paths regardless what layer path one binds to.
1618 The getifaddrs upgrade path broken with 20111215 has been restored.
1619 If you have upgraded in between 20111215 and 20120209 you need to
1620 recompile libc again with your kernel. You still need to recompile
1621 world to be able to configure CARP but this restriction already
1622 comes from 20111215.
1625 The set_rcvar() function has been removed from /etc/rc.subr. All
1626 base and ports rc.d scripts have been updated, so if you have a
1627 port installed with a script in /usr/local/etc/rc.d you can either
1628 hand-edit the rcvar= line, or reinstall the port.
1630 An easy way to handle the mass-update of /etc/rc.d:
1631 rm /etc/rc.d/* && mergemaster -i
1634 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1635 on the current CPU and prevents other threads from running.
1636 This behavior can be reverted using the kern.stop_scheduler_on_panic
1638 The new behavior can be incompatible with kern.sync_on_panic.
1641 The carp(4) facility has been changed significantly. Configuration
1642 of the CARP protocol via ifconfig(8) has changed, as well as format
1643 of CARP events submitted to devd(8) has changed. See manual pages
1644 for more information. The arpbalance feature of carp(4) is currently
1645 not supported anymore.
1647 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1648 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1649 need to be recompiled.
1652 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1656 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1657 explicitely support non-MPSAFE filesystems.
1658 It is on by default for all supported platform at this present
1662 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1663 i386 and pc98 GENERIC kernel configuration files.
1666 sysinstall has been removed
1669 The stable/9 branch created in subversion. This corresponds to the
1670 RELENG_9 branch in CVS.
1676 Avoid using make -j when upgrading. While generally safe, there are
1677 sometimes problems using -j to upgrade. If your upgrade fails with
1678 -j, please try again without -j. From time to time in the past there
1679 have been problems using -j with buildworld and/or installworld. This
1680 is especially true when upgrading between "distant" versions (eg one
1681 that cross a major release boundary or several minor releases, or when
1682 several months have passed on the -current branch).
1684 Sometimes, obscure build problems are the result of environment
1685 poisoning. This can happen because the make utility reads its
1686 environment when searching for values for global variables. To run
1687 your build attempts in an "environmental clean room", prefix all make
1688 commands with 'env -i '. See the env(1) manual page for more details.
1690 When upgrading from one major version to another it is generally best
1691 to upgrade to the latest code in the currently installed branch first,
1692 then do an upgrade to the new branch. This is the best-tested upgrade
1693 path, and has the highest probability of being successful. Please try
1694 this approach before reporting problems with a major version upgrade.
1696 When upgrading a live system, having a root shell around before
1697 installing anything can help undo problems. Not having a root shell
1698 around can lead to problems if pam has changed too much from your
1699 starting point to allow continued authentication after the upgrade.
1701 This file should be read as a log of events. When a later event changes
1702 information of a prior event, the prior event should not be deleted.
1703 Instead, a pointer to the entry with the new information should be
1704 placed in the old entry. Readers of this file should also sanity check
1705 older entries before relying on them blindly. Authors of new entries
1706 should write them with this in mind.
1710 When upgrading the boot ZFS pool to a new version, always follow
1713 1.) recompile and reinstall the ZFS boot loader and boot block
1714 (this is part of "make buildworld" and "make installworld")
1716 2.) update the ZFS boot block on your boot drive
1718 The following example updates the ZFS boot block on the first
1719 partition (freebsd-boot) of a GPT partitioned drive ada0:
1720 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1722 Non-boot pools do not need these updates.
1726 If you are updating from a prior version of FreeBSD (even one just
1727 a few days old), you should follow this procedure. It is the most
1728 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1730 make kernel-toolchain
1731 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1732 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1734 To test a kernel once
1735 ---------------------
1736 If you just want to boot a kernel once (because you are not sure
1737 if it works, or if you want to boot a known bad kernel to provide
1738 debugging information) run
1739 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1740 nextboot -k testkernel
1742 To just build a kernel when you know that it won't mess you up
1743 --------------------------------------------------------------
1744 This assumes you are already running a CURRENT system. Replace
1745 ${arch} with the architecture of your machine (e.g. "i386",
1746 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1748 cd src/sys/${arch}/conf
1749 config KERNEL_NAME_HERE
1750 cd ../compile/KERNEL_NAME_HERE
1755 If this fails, go to the "To build a kernel" section.
1757 To rebuild everything and install it on the current system.
1758 -----------------------------------------------------------
1759 # Note: sometimes if you are running current you gotta do more than
1760 # is listed here if you are upgrading from a really old current.
1762 <make sure you have good level 0 dumps>
1764 make kernel KERNCONF=YOUR_KERNEL_HERE
1766 <reboot in single user> [3]
1773 To cross-install current onto a separate partition
1774 --------------------------------------------------
1775 # In this approach we use a separate partition to hold
1776 # current's root, 'usr', and 'var' directories. A partition
1777 # holding "/", "/usr" and "/var" should be about 2GB in
1780 <make sure you have good level 0 dumps>
1783 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1784 <maybe newfs current's root partition>
1785 <mount current's root partition on directory ${CURRENT_ROOT}>
1786 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1787 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1788 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1789 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1790 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1791 <reboot into current>
1792 <do a "native" rebuild/install as described in the previous section>
1793 <maybe install compatibility libraries from ports/misc/compat*>
1797 To upgrade in-place from stable to current
1798 ----------------------------------------------
1799 <make sure you have good level 0 dumps>
1801 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1803 <reboot in single user> [3]
1810 Make sure that you've read the UPDATING file to understand the
1811 tweaks to various things you need. At this point in the life
1812 cycle of current, things change often and you are on your own
1813 to cope. The defaults can also change, so please read ALL of
1814 the UPDATING entries.
1816 Also, if you are tracking -current, you must be subscribed to
1817 freebsd-current@freebsd.org. Make sure that before you update
1818 your sources that you have read and understood all the recent
1819 messages there. If in doubt, please track -stable which has
1820 much fewer pitfalls.
1822 [1] If you have third party modules, such as vmware, you
1823 should disable them at this point so they don't crash your
1826 [3] From the bootblocks, boot -s, and then do
1831 adjkerntz -i # if CMOS is wall time
1832 Also, when doing a major release upgrade, it is required that
1833 you boot into single user mode to do the installworld.
1835 [4] Note: This step is non-optional. Failure to do this step
1836 can result in a significant reduction in the functionality of the
1837 system. Attempting to do it by hand is not recommended and those
1838 that pursue this avenue should read this file carefully, as well
1839 as the archives of freebsd-current and freebsd-hackers mailing lists
1840 for potential gotchas. The -U option is also useful to consider.
1841 See mergemaster(8) for more information.
1843 [5] Usually this step is a noop. However, from time to time
1844 you may need to do this if you get unknown user in the following
1845 step. It never hurts to do it all the time. You may need to
1846 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1847 install) after the buildworld before this step if you last updated
1848 from current before 20130425 or from -stable before 20130430.
1850 [6] This only deletes old files and directories. Old libraries
1851 can be deleted by "make delete-old-libs", but you have to make
1852 sure that no program is using those libraries anymore.
1854 [8] The new kernel must be able to run existing binaries used by
1855 an installworld. When upgrading across major versions, the new
1856 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1857 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1858 binaries). Failure to do so may leave you with a system that is
1859 hard to boot to recover. A GENERIC kernel will include suitable
1860 compatibility options to run binaries from older branches.
1862 Make sure that you merge any new devices from GENERIC since the
1863 last time you updated your kernel config file.
1865 [9] When checking out sources, you must include the -P flag to have
1866 cvs prune empty directories.
1868 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1869 "?=" instead of the "=" assignment operator, so that buildworld can
1870 override the CPUTYPE if it needs to.
1872 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1873 not on the command line, or in /etc/make.conf. buildworld will
1874 warn if it is improperly defined.
1877 This file contains a list, in reverse chronological order, of major
1878 breakages in tracking -current. It is not guaranteed to be a complete
1879 list of such breakages, and only contains entries since September 23, 2011.
1880 If you need to see UPDATING entries from before that date, you will need
1881 to fetch an UPDATING file from an older FreeBSD release.
1883 Copyright information:
1885 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1887 Redistribution, publication, translation and use, with or without
1888 modification, in full or in part, in any form or format of this
1889 document are permitted without further permission from the author.
1891 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1892 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1893 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1894 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1895 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1896 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1897 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1898 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1899 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1900 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1901 POSSIBILITY OF SUCH DAMAGE.
1903 Contact Warner Losh if you have any questions about your use of