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 20190724 p1 FreeBSD-EN-19:13.mds
20 FreeBSD-SA-19:12.telnet
22 FreeBSD-SA-19:14.freebsd32
23 FreeBSD-SA-19:15.mqueuefs
24 FreeBSD-SA-19:16.bhyve
27 Fix panic from Intel CPU vulnerability mitigation. [EN-19:13.mds]
29 Fix multiple telnet client vulnerabilities. [SA-19:12.telnet]
31 Fix pts write-after-free. [SA-19:13.pts]
33 Fix kernel memory disclosure in freebsd32_ioctl. [SA-19:14.freebsd32]
35 Fix reference count overflow in mqueuefs. [SA-19:15.mqueuefs]
37 Fix byhve out-of-bounds read in XHCI device. [SA-19:16.bhyve]
39 Fix file descriptor reference count leak. [SA-19:17.fd]
44 20190702 FreeBSD-EN-19:12.tzdata
45 FreeBSD-SA-19:09.iconv
46 FreeBSD-SA-19:11.cd_ioctl
48 Import tzdata 2019b. [EN-19:12.tzdata]
50 Fix iconv buffer overflow. [SA-19:09.iconv]
52 Fix privilege escalation in cd(4) driver. [SA-19:11.cd_ioctl]
55 CARP now sets DSCP value CS7(Network Traffic) in the flowlabel field
56 of packets by default instead of only setting TOS_LOWDELAY in IPv4,
57 which was deprecated in 1998. Original behavior can be restored by
58 setting sysctl net.inet.carp.dscp=4.
61 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
62 8.0.0. Please see the 20141231 entry below for information about
63 prerequisites and upgrading, if you are not already using clang 3.5.0
67 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
68 compiled into your custom kernel, add 'device xz' statement to the
72 Co-existance for Forth and Lua interpreters in bootloaders has now been
73 merged to ease testing of lualoader. LOADER_DEFAULT_INTERP, documented
74 in build(7), may be used to control which interpreter flavor is used in
75 the default loader to be installed. For systems where Lua and Forth
76 coexist, this switch can also be made on a running system by creating a
77 link from /boot/loader{,.efi} to /boot/loader_${flavor}{,.efi} rather
78 than requiring a rebuild.
80 The default flavor in this branch will remain Forth. As indicated in
81 the 20190216 UPDATING entry, booting is a complex environment; it would
82 be prudent to assume that lualoader may not work for your setup and make
83 provisions for backup boot methods.
86 zfsloader's functionality has now been folded into loader.
87 zfsloader is no longer necesasary once you've updated your
88 boot blocks. For a transition period, we will install a
89 hardlink for zfsloader to loader to allow a smooth transition
90 until the boot blocks can be updated (hard link because old
91 zfs boot blocks don't understand symlinks).
94 Lualoader has been merged to facilitate testing on this branch. It's
95 purely opt-in for now by building WITH_LOADER_LUA and WITHOUT_FORTH in
96 /etc/src.conf, but co-existance will come shortly. Booting is a complex
97 environment and test coverage for Lua-enabled loaders has been thin, so
98 it would be prudent to assume it might not work and make provisions for
102 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
103 7.0.1. Please see the 20141231 entry below for information about
104 prerequisites and upgrading, if you are not already using clang 3.5.0
108 r342562 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
109 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
110 servers that have vfs.nfsd.nfs_privport set will only allow mounts
111 from clients using a reserved port#. Since both the FreeBSD and Linux
112 NFSv4 clients use reserved port#s by default, this should not affect
116 The '%I' format in the kern.corefile sysctl limits the number of
117 core files that a process can generate to the number stored in the
118 debug.ncores sysctl. The '%I' format is replaced by the single digit
119 index. Previously, if all indexes were taken the kernel would overwrite
120 only a core file with the highest index in a filename.
121 Currently the system will create a new core file if there is a free
122 index or if all slots are taken it will overwrite the oldest one.
125 WITH_OFED option now only enables the build for the OFED libraries
126 and some fundamental client utilities. OpenSM and rest of the
127 debugging tools are enabled by WITH_OFED_EXTRA build switch.
128 WITH_OFED is turned on by default on amd64.
131 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
132 6.0.1. Please see the 20141231 entry below for information about
133 prerequisites and upgrading, if you are not already using clang 3.5.0
137 The releng/11.2 branch has been created from stable/11@r334458.
140 The tz database (tzdb) has been updated to 2018e. This version more
141 correctly models time stamps in time zones with negative DST such as
142 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
143 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
144 time zone abbreviations and the tm_isdst flag.
147 The use of RSS hash from the network card aka flowid has been
148 disabled by default for lagg(4) as it's currently incompatible with
149 the lacp and loadbalance protocols.
151 This can be re-enabled by setting the following in loader.conf:
152 net.link.lagg.default_use_flowid="1"
155 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
156 6.0.0. Please see the 20141231 entry below for information about
157 prerequisites and upgrading, if you are not already using clang 3.5.0
161 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
162 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
163 to WITH/OUT_LOADER_GELI.
166 The geli password typed at boot is now hidden. To restore the previous
167 behavior, see geli(8) for configuration options.
169 The SW_WATCHDOG option is no longer necessary to enable the
170 hardclock-based software watchdog if no hardware watchdog is
171 configured. As before, SW_WATCHDOG will cause the software
172 watchdog to be enabled even if a hardware watchdog is configured.
175 lint(1) binaries and library are no longer built by default. To
176 enable building them, define WITH_LINT in src.conf. If you are using
177 a FreeBSD 12 or later system to build 11-stable, you may need to
178 install a lint(1) binary to use WITH_LINT.
181 When building multiple kernels using KERNCONF, non-existent KERNCONF
182 files will produce an error and buildkernel will fail. Previously
183 missing KERNCONF files silently failed giving no indication as to
184 why, only to subsequently discover during installkernel that the
185 desired kernel was never built in the first place.
188 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
189 Please see the 20141231 entry below for information about prerequisites
190 and upgrading, if you are not already using clang 3.5.0 or higher.
193 Since the switch to GPT disk labels, fsck for UFS/FFS has been
194 unable to automatically find alternate superblocks. As of r322806,
195 the information needed to find alternate superblocks has been
196 moved to the end of the area reserved for the boot block.
197 Filesystems created with a newfs of this vintage or later
198 will create the recovery information. If you have a filesystem
199 created prior to this change and wish to have a recovery block
200 created for your filesystem, you can do so by running fsck in
201 forground mode (i.e., do not use the -p or -y options). As it
202 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
203 to which you should answer yes.
206 The releng/11.1 branch has been created from stable/11@r320475.
209 arm64 builds now use the base system LLD 4.0.0 linker by default,
210 instead of requiring that the aarch64-binutils port or package be
211 installed. To continue using aarch64-binutils, set
212 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
215 The ctl.ko module no longer implements the iSCSI target frontend:
216 cfiscsi.ko does instead.
218 If building cfiscsi.ko as a kernel module, the module can be loaded
219 via one of the following methods:
220 - `cfiscsi_load="YES"` in loader.conf(5).
221 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
222 - ctladm(8)/ctld(8), when compiled with iSCSI support
223 (`WITH_ISCSI=yes` in src.conf(5))
225 Please see cfiscsi(4) for more details.
228 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
229 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
230 same source (previously, the dependency of mmcsd.ko on mmc.ko was
231 missing, but mmcsd.ko now will refuse to load if it is incompatible
235 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
236 use any explicitly assigned loopback address available in the jail
237 instead of using the first assigned address of the jail.
240 As of r316810 for ipfilter, keep frags is no longer assumed when
241 keep state is specified in a rule. r316810 aligns ipfilter with
242 documentation in man pages separating keep frags from keep state.
243 This allows keep state to specified without forcing keep frags
244 and allows keep frags to be specified independently of keep state.
245 To maintain previous behaviour, also specify keep frags with
246 keep state (as documented in ipf.conf.5).
249 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
250 Please see the 20141231 entry below for information about prerequisites
251 and upgrading, if you are not already using clang 3.5.0 or higher.
254 The code that provides support for ZFS .zfs/ directory functionality
255 has been reimplemented. It's not possible now to create a snapshot
256 by mkdir under .zfs/snapshot/. That should be the only user visible
260 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
261 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
262 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
263 and now NAT-T is supported by default. Security associations now use
264 the single namespace for SPI allocation, so if you use several manually
265 configured security associations with the same SPI, this configuration
269 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
270 Please see the 20141231 entry below for information about prerequisites
271 and upgrading, if you are not already using clang 3.5.0 or higher.
274 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
275 Please see the 20141231 entry below for information about prerequisites
276 and upgrading, if you are not already using clang 3.5.0 or higher.
279 The layout of the pmap structure has changed for powerpc to put the pmap
280 statistics at the front for all CPU variations. libkvm(3) and all tools
281 that link against it need to be recompiled.
284 isl(4) and cyapa(4) drivers now require a new driver,
285 chromebook_platform(4), to work properly on Chromebook-class hardware.
286 On other types of hardware the drivers may need to be configured using
287 device hints. Please see the corresponding manual pages for details.
290 Relocatable object files with the extension of .So have been renamed
291 to use an extension of .pico instead. The purpose of this change is
292 to avoid a name clash with shared libraries on case-insensitive file
293 systems. On those file systems, foo.So is the same file as foo.so.
296 The releng/11.0 branch has been created from stable/11@r303970.
299 The stable/11 branch has been created from head@r302406.
302 The libc stub for the pipe(2) system call has been replaced with
303 a wrapper that calls the pipe2(2) system call and the pipe(2)
304 system call is now only implemented by the kernels that include
305 "options COMPAT_FREEBSD10" in their config file (this is the
306 default). Users should ensure that this option is enabled in
307 their kernel or upgrade userspace to r302092 before upgrading their
311 CAM will now strip leading spaces from SCSI disks' serial numbers.
312 This will effect users who create UFS filesystems on SCSI disks using
313 those disk's diskid device nodes. For example, if /etc/fstab
314 previously contained a line like
315 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
316 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
317 transforms like gmirror may also be affected. ZFS users should
321 The bitstring(3) API has been updated with new functionality and
322 improved performance. But it is binary-incompatible with the old API.
323 Objects built with the new headers may not be linked against objects
324 built with the old headers.
327 The brk and sbrk functions have been removed from libc on arm64.
328 Binutils from ports has been updated to not link to these
329 functions and should be updated to the latest version before
330 installing a new libc.
333 The armv6 port now defaults to hard float ABI. Limited support
334 for running both hardfloat and soft float on the same system
335 is available using the libraries installed with -DWITH_LIBSOFT.
336 This has only been tested as an upgrade path for installworld
337 and packages may fail or need manual intervention to run. New
338 packages will be needed.
340 To update an existing self-hosted armv6hf system, you must add
341 TARGET_ARCH=armv6 on the make command line for both the build
342 and the install steps.
345 Kernel modules compiled outside of a kernel build now default to
346 installing to /boot/modules instead of /boot/kernel. Many kernel
347 modules built this way (such as those in ports) already overrode
348 KMODDIR explicitly to install into /boot/modules. However,
349 manually building and installing a module from /sys/modules will
350 now install to /boot/modules instead of /boot/kernel.
353 The CAM I/O scheduler has been committed to the kernel. There should be
354 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
355 list of known rogues that claim support for this but actually corrupt
356 data is believed to be complete, be on the lookout for data
357 corruption. The known rogue list is believed to be complete:
359 o Crucial MX100, M550 drives with MU01 firmware.
360 o Micron M510 and M550 drives with MU01 firmware.
361 o Micron M500 prior to MU07 firmware
362 o Samsung 830, 840, and 850 all firmwares
363 o FCCT M500 all firmwares
365 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
366 with working NCQ TRIM. For Micron branded drives, see your sales rep for
367 updated firmware. Black listed drives will work correctly because these
368 drives work correctly so long as no NCQ TRIMs are sent to them. Given
369 this list is the same as found in Linux, it's believed there are no
370 other rogues in the market place. All other models from the above
373 To be safe, if you are at all concerned, you can quirk each of your
374 drives to prevent NCQ from being sent by setting:
375 kern.cam.ada.X.quirks="0x2"
376 in loader.conf. If the drive requires the 4k sector quirk, set the
380 The FAST_DEPEND build option has been removed and its functionality is
381 now the one true way. The old mkdep(1) style of 'make depend' has
382 been removed. See 20160311 for further details.
385 Resource range types have grown from unsigned long to uintmax_t. All
386 drivers, and anything using libdevinfo, need to be recompiled.
389 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
390 builds. It no longer runs mkdep(1) during 'make depend', and the
391 'make depend' stage can safely be skipped now as it is auto ran
392 when building 'make all' and will generate all SRCS and DPSRCS before
393 building anything else. Dependencies are gathered at compile time with
394 -MF flags kept in separate .depend files per object file. Users should
395 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
399 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
400 kernel modules. Therefore, if you load any kernel modules at boot time,
401 please install the boot loaders after you install the kernel, but before
405 make kernel KERNCONF=YOUR_KERNEL_HERE
406 make -C sys/boot install
407 <reboot in single user>
409 Then follow the usual steps, described in the General Notes section,
413 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
414 see the 20141231 entry below for information about prerequisites and
415 upgrading, if you are not already using clang 3.5.0 or higher.
418 The AIO subsystem is now a standard part of the kernel. The
419 VFS_AIO kernel option and aio.ko kernel module have been removed.
420 Due to stability concerns, asynchronous I/O requests are only
421 permitted on sockets and raw disks by default. To enable
422 asynchronous I/O requests on all file types, set the
423 vfs.aio.enable_unsafe sysctl to a non-zero value.
426 The ELF object manipulation tool objcopy is now provided by the
427 ELF Tool Chain project rather than by GNU binutils. It should be a
428 drop-in replacement, with the addition of arm64 support. The
429 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
430 to obtain the GNU version if necessary.
433 Building ZFS pools on top of zvols is prohibited by default. That
434 feature has never worked safely; it's always been prone to deadlocks.
435 Using a zvol as the backing store for a VM guest's virtual disk will
436 still work, even if the guest is using ZFS. Legacy behavior can be
437 restored by setting vfs.zfs.vol.recursive=1.
440 The NONE and HPN patches has been removed from OpenSSH. They are
441 still available in the security/openssh-portable port.
444 With the addition of ypldap(8), a new _ypldap user is now required
445 during installworld. "mergemaster -p" can be used to add the user
446 prior to installworld, as documented in the handbook.
449 The tftp loader (pxeboot) now uses the option root-path directive. As a
450 consequence it no longer looks for a pxeboot.4th file on the tftp
451 server. Instead it uses the regular /boot infrastructure as with the
455 The code to start recording plug and play data into the modules has
456 been committed. While the old tools will properly build a new kernel,
457 a number of warnings about "unknown metadata record 4" will be produced
458 for an older kldxref. To avoid such warnings, make sure to rebuild
459 the kernel toolchain (or world). Make sure that you have r292078 or
460 later when trying to build 292077 or later before rebuilding.
463 Debug data files are now built by default with 'make buildworld' and
464 installed with 'make installworld'. This facilitates debugging but
465 requires more disk space both during the build and for the installed
466 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
470 r291527 changed the internal interface between the nfsd.ko and
471 nfscommon.ko modules. As such, they must both be upgraded to-gether.
472 __FreeBSD_version has been bumped because of this.
475 Add support for unicode collation strings leads to a change of
476 order of files listed by ls(1) for example. To get back to the old
477 behaviour, set LC_COLLATE environment variable to "C".
479 Databases administrators will need to reindex their databases given
480 collation results will be different.
482 Due to a bug in install(1) it is recommended to remove the ancient
483 locales before running make installworld.
485 rm -rf /usr/share/locale/*
488 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
489 libcrypto.so.7 or libssl.so.7 must be recompiled.
492 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
493 Kernel modules isp_2400_multi and isp_2500_multi were removed and
494 should be replaced with isp_2400 and isp_2500 modules respectively.
497 The build previously allowed using 'make -n' to not recurse into
498 sub-directories while showing what commands would be executed, and
499 'make -n -n' to recursively show commands. Now 'make -n' will recurse
500 and 'make -N' will not.
503 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
504 and etcupdate will now use this file. A custom sendmail.cf is now
505 updated via this mechanism rather than via installworld. If you had
506 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
507 want to remove the exclusion or change it to "always install".
508 /etc/mail/sendmail.cf is now managed the same way regardless of
509 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
510 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
513 Compatibility shims for legacy ATA device names have been removed.
514 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
515 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
516 environment variables, /dev/ad* and /dev/ar* symbolic links.
519 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
520 Please see the 20141231 entry below for information about prerequisites
521 and upgrading, if you are not already using clang 3.5.0 or higher.
524 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
525 and renamed from .symbols to .debug. This reduces the size requirements
526 on the boot partition or file system and provides consistency with
527 userland debug files.
529 When using the supported kernel installation method the
530 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
531 as is done with /boot/kernel.
533 Developers wishing to maintain the historical behavior of installing
534 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
537 The wireless drivers had undergone changes that remove the 'parent
538 interface' from the ifconfig -l output. The rc.d network scripts
539 used to check presence of a parent interface in the list, so old
540 scripts would fail to start wireless networking. Thus, etcupdate(3)
541 or mergemaster(8) run is required after kernel update, to update your
542 rc.d scripts in /etc.
545 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
546 These configurations are now automatically interpreted as
547 'scrub fragment reassemble'.
550 Kernel-loadable modules for the random(4) device are back. To use
551 them, the kernel must have
554 options RANDOM_LOADABLE
556 kldload(8) can then be used to load random_fortuna.ko
557 or random_yarrow.ko. Please note that due to the indirect
558 function calls that the loadable modules need to provide,
559 the build-in variants will be slightly more efficient.
561 The random(4) kernel option RANDOM_DUMMY has been retired due to
562 unpopularity. It was not all that useful anyway.
565 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
566 Control over building the ELF Tool Chain tools is now provided by
567 the WITHOUT_TOOLCHAIN knob.
570 The polarity of Pulse Per Second (PPS) capture events with the
571 uart(4) driver has been corrected. Prior to this change the PPS
572 "assert" event corresponded to the trailing edge of a positive PPS
573 pulse and the "clear" event was the leading edge of the next pulse.
575 As the width of a PPS pulse in a typical GPS receiver is on the
576 order of 1 millisecond, most users will not notice any significant
577 difference with this change.
579 Anyone who has compensated for the historical polarity reversal by
580 configuring a negative offset equal to the pulse width will need to
581 remove that workaround.
584 The default group assigned to /dev/dri entries has been changed
585 from 'wheel' to 'video' with the id of '44'. If you want to have
586 access to the dri devices please add yourself to the video group
589 # pw groupmod video -m $USER
592 The menu.rc and loader.rc files will now be replaced during
593 upgrades. Please migrate local changes to menu.rc.local and
594 loader.rc.local instead.
597 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
598 strings and strip have been removed. The src.conf(5) knob
599 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
602 As ZFS requires more kernel stack pages than is the default on some
603 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
604 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
606 Please consider using 'options KSTACK_PAGES=X' where X is greater
607 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
610 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
611 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
612 default, i.e., they will not contain "::". For example, instead
613 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
614 to have a more specific match, such as different map entries for
615 IPv6:0:0 vs IPv6:0. This change requires that configuration
616 data (including maps, files, classes, custom ruleset, etc.) must
617 use the same format, so make certain such configuration data is
618 upgrading. As a very simple check search for patterns like
619 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
620 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
621 the cf option UseCompressedIPv6Addresses.
624 The default kernel entropy-processing algorithm is now
625 Fortuna, replacing Yarrow.
627 Assuming you have 'device random' in your kernel config
628 file, the configurations allow a kernel option to override
629 this default. You may choose *ONE* of:
631 options RANDOM_YARROW # Legacy /dev/random algorithm.
632 options RANDOM_DUMMY # Blocking-only driver.
634 If you have neither, you get Fortuna. For most people,
635 read no further, Fortuna will give a /dev/random that works
636 like it always used to, and the difference will be irrelevant.
638 If you remove 'device random', you get *NO* kernel-processed
639 entropy at all. This may be acceptable to folks building
640 embedded systems, but has complications. Carry on reading,
641 and it is assumed you know what you need.
643 *PLEASE* read random(4) and random(9) if you are in the
644 habit of tweaking kernel configs, and/or if you are a member
645 of the embedded community, wanting specific and not-usual
646 behaviour from your security subsystems.
648 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
649 random', you will NOT have a functioning /dev/random, and
650 many cryptographic features will not work, including SSH.
651 You may also find strange behaviour from the random(3) set
652 of library functions, in particular sranddev(3), srandomdev(3)
653 and arc4random(3). The reason for this is that the KERN_ARND
654 sysctl only returns entropy if it thinks it has some to
655 share, and with RANDOM_DUMMY or no 'device random' this
659 An additional fix for the issue described in the 20150614 sendmail
660 entry below has been been committed in revision 284717.
663 FreeBSD's old make (fmake) has been removed from the system. It is
664 available as the devel/fmake port or via pkg install fmake.
667 The fix for the issue described in the 20150614 sendmail entry
668 below has been been committed in revision 284436. The work
669 around described in that entry is no longer needed unless the
670 default setting is overridden by a confDH_PARAMETERS configuration
671 setting of '5' or pointing to a 512 bit DH parameter file.
674 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
675 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
676 and devel/kyua to version 0.20+ and adjust any calling code to work
677 with Kyuafile and kyua.
680 The import of openssl to address the FreeBSD-SA-15:10.openssl
681 security advisory includes a change which rejects handshakes
682 with DH parameters below 768 bits. sendmail releases prior
683 to 8.15.2 (not yet released), defaulted to a 512 bit
684 DH parameter setting for client connections. To work around
685 this interoperability, sendmail can be configured to use a
686 2048 bit DH parameter by:
688 1. Edit /etc/mail/`hostname`.mc
689 2. If a setting for confDH_PARAMETERS does not exist or
690 exists and is set to a string beginning with '5',
692 3. If a setting for confDH_PARAMETERS exists and is set to
693 a file path, create a new file with:
694 openssl dhparam -out /path/to/file 2048
695 4. Rebuild the .cf file:
696 cd /etc/mail/; make; make install
698 cd /etc/mail/; make restart
700 A sendmail patch is coming, at which time this file will be
704 Generation of legacy formatted entries have been disabled by default
705 in pwd_mkdb(8), as all base system consumers of the legacy formatted
706 entries were converted to use the new format by default when the new,
707 machine independent format have been added and supported since FreeBSD
710 Please see the pwd_mkdb(8) manual page for further details.
713 Clang and llvm have been upgraded to 3.6.1 release. Please see the
714 20141231 entry below for information about prerequisites and upgrading,
715 if you are not already using 3.5.0 or higher.
718 TI platform code switched to using vendor DTS files and this update
719 may break existing systems running on Beaglebone, Beaglebone Black,
722 - dtb files should be regenerated/reinstalled. Filenames are the
723 same but content is different now
724 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
725 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
726 addressing scheme is now pin 25 on /dev/gpioc3.
727 - Pandaboard: /etc/ttys should be updated, serial console device is
728 now /dev/ttyu2, not /dev/ttyu0
731 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
732 If you need the GNU extension from groff soelim(1), install groff
733 from package: pkg install groff, or via ports: textproc/groff.
736 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
737 defined in symlink(7); previously symlinks were silently ignored.
740 The const qualifier has been removed from iconv(3) to comply with
741 POSIX. The ports tree is aware of this from r384038 onwards.
744 Libraries specified by LIBADD in Makefiles must have a corresponding
745 DPADD_<lib> variable to ensure correct dependencies. This is now
746 enforced in src.libnames.mk.
749 From legacy ata(4) driver was removed support for SATA controllers
750 supported by more functional drivers ahci(4), siis(4) and mvs(4).
751 Kernel modules ataahci and ataadaptec were removed completely,
752 replaced by ahci and mvs modules respectively.
755 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
756 the 20141231 entry below for information about prerequisites and
757 upgrading, if you are not already using 3.5.0 or higher.
760 The 32-bit PowerPC kernel has been changed to a position-independent
761 executable. This can only be booted with a version of loader(8)
762 newer than January 31, 2015, so make sure to update both world and
763 kernel before rebooting.
766 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
767 but before r278950, the RNG was not seeded properly. Immediately
768 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
769 ssh keys or openssl keys) that were generated w/ a kernel from that
770 range. This does not affect programs that directly used /dev/random
771 or /dev/urandom. All userland uses of arc4random(3) are affected.
774 The autofs(4) ABI was changed in order to restore binary compatibility
775 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
779 The powerpc64 kernel has been changed to a position-independent
780 executable. This can only be booted with a new version of loader(8),
781 so make sure to update both world and kernel before rebooting.
784 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
785 only release, no new features have been added. Please see the 20141231
786 entry below for information about prerequisites and upgrading, if you
787 are not already using 3.5.0.
790 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
791 taken from the ELF Tool Chain project rather than GNU binutils. They
792 should be drop-in replacements, with the addition of arm64 support.
793 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
794 binutils tools, if necessary. See 20150805 for updated information.
797 The default Unbound configuration now enables remote control
798 using a local socket. Users who have already enabled the
799 local_unbound service should regenerate their configuration
800 by running "service local_unbound setup" as root.
803 The GNU texinfo and GNU info pages have been removed.
804 To be able to view GNU info pages please install texinfo from ports.
807 Clang, llvm and lldb have been upgraded to 3.5.0 release.
809 As of this release, a prerequisite for building clang, llvm and lldb is
810 a C++11 capable compiler and C++11 standard library. This means that to
811 be able to successfully build the cross-tools stage of buildworld, with
812 clang as the bootstrap compiler, your system compiler or cross compiler
813 should either be clang 3.3 or later, or gcc 4.8 or later, and your
814 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
817 On any standard FreeBSD 10.x or 11.x installation, where clang and
818 libc++ are on by default (that is, on x86 or arm), this should work out
821 On 9.x installations where clang is enabled by default, e.g. on x86 and
822 powerpc, libc++ will not be enabled by default, so libc++ should be
823 built (with clang) and installed first. If both clang and libc++ are
824 missing, build clang first, then use it to build libc++.
826 On 8.x and earlier installations, upgrade to 9.x first, and then follow
827 the instructions for 9.x above.
829 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
830 default, and do not build clang.
832 Many embedded systems are resource constrained, and will not be able to
833 build clang in a reasonable time, or in some cases at all. In those
834 cases, cross building bootable systems on amd64 is a workaround.
836 This new version of clang introduces a number of new warnings, of which
837 the following are most likely to appear:
841 This warns in two cases, for both C and C++:
842 * When the code is trying to take the absolute value of an unsigned
843 quantity, which is effectively a no-op, and almost never what was
844 intended. The code should be fixed, if at all possible. If you are
845 sure that the unsigned quantity can be safely cast to signed, without
846 loss of information or undefined behavior, you can add an explicit
847 cast, or disable the warning.
849 * When the code is trying to take an absolute value, but the called
850 abs() variant is for the wrong type, which can lead to truncation.
851 If you want to disable the warning instead of fixing the code, please
852 make sure that truncation will not occur, or it might lead to unwanted
855 -Wtautological-undefined-compare and
856 -Wundefined-bool-conversion
858 These warn when C++ code is trying to compare 'this' against NULL, while
859 'this' should never be NULL in well-defined C++ code. However, there is
860 some legacy (pre C++11) code out there, which actively abuses this
861 feature, which was less strictly defined in previous C++ versions.
863 Squid and openjdk do this, for example. The warning can be turned off
864 for C++98 and earlier, but compiling the code in C++11 mode might result
865 in unexpected behavior; for example, the parts of the program that are
866 unreachable could be optimized away.
869 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
870 kernel sources have been removed. The .h files remain, since some
871 utilities include them. This will need to be fixed later.
872 If "mount -t oldnfs ..." is attempted, it will fail.
873 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
874 the utilities will report errors.
877 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
878 directories to top level SUBDIR variable when their parent
879 directory is included in LOCAL_DIRS. Users with build systems with
880 such hierarchies and without SUBDIR entries in the parent
881 directory Makefiles should add them or add the directories to
885 faith(4) and faithd(8) have been removed from the base system. Faith
886 has been obsolete for a very long time.
889 vt(4), the new console driver, is enabled by default. It brings
890 support for Unicode and double-width characters, as well as
891 support for UEFI and integration with the KMS kernel video
894 You may need to update your console settings in /etc/rc.conf,
895 most probably the keymap. During boot, /etc/rc.d/syscons will
896 indicate what you need to do.
898 vt(4) still has issues and lacks some features compared to
899 syscons(4). See the wiki for up-to-date information:
900 https://wiki.freebsd.org/Newcons
902 If you want to keep using syscons(4), you can do so by adding
903 the following line to /boot/loader.conf:
907 pjdfstest has been integrated into kyua as an opt-in test suite.
908 Please see share/doc/pjdfstest/README for more details on how to
912 gperf has been removed from the base system for architectures
913 that use clang. Ports that require gperf will obtain it from the
917 pjdfstest has been moved from tools/regression/pjdfstest to
921 At svn r271982, The default linux compat kernel ABI has been adjusted
922 to 2.6.18 in support of the linux-c6 compat ports infrastructure
923 update. If you wish to continue using the linux-f10 compat ports,
924 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
925 encouraged to update their linux-compat packages to linux-c6 during
926 their next update cycle.
929 The ofwfb driver, used to provide a graphics console on PowerPC when
930 using vt(4), no longer allows mmap() of all physical memory. This
931 will prevent Xorg on PowerPC with some ATI graphics cards from
932 initializing properly unless x11-servers/xorg-server is updated to
936 The xdev targets have been converted to using TARGET and
937 TARGET_ARCH instead of XDEV and XDEV_ARCH.
940 The default unbound configuration has been modified to address
941 issues with reverse lookups on networks that use private
942 address ranges. If you use the local_unbound service, run
943 "service local_unbound setup" as root to regenerate your
944 configuration, then "service local_unbound reload" to load the
948 The GNU texinfo and GNU info pages are not built and installed
949 anymore, WITH_INFO knob has been added to allow to built and install
951 UPDATE: see 20150102 entry on texinfo's removal
954 The GNU readline library is now an INTERNALLIB - that is, it is
955 statically linked into consumers (GDB and variants) in the base
956 system, and the shared library is no longer installed. The
957 devel/readline port is available for third party software that
961 The Itanium architecture (ia64) has been removed from the list of
962 known architectures. This is the first step in the removal of the
966 Commit r268115 has added NFSv4.1 server support, merged from
967 projects/nfsv4.1-server. Since this includes changes to the
968 internal interfaces between the NFS related modules, a full
969 build of the kernel and modules will be necessary.
970 __FreeBSD_version has been bumped.
973 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
974 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
975 which differs from the behaviour controlled by this knob.)
978 Maximal length of the serial number in CTL was increased from 16 to
979 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
980 and ctld, need to be rebuilt to work with a new kernel.
983 The libatf-c and libatf-c++ major versions were downgraded to 0 and
984 1 respectively to match the upstream numbers. They were out of
985 sync because, when they were originally added to FreeBSD, the
986 upstream versions were not respected. These libraries are private
987 and not yet built by default, so renumbering them should be a
988 non-issue. However, unclean source trees will yield broken test
989 programs once the operator executes "make delete-old-libs" after a
992 Additionally, the atf-sh binary was made private by moving it into
993 /usr/libexec/. Already-built shell test programs will keep the
994 path to the old binary so they will break after "make delete-old"
997 If you are using WITH_TESTS=yes (not the default), wipe the object
998 tree and rebuild from scratch to prevent spurious test failures.
999 This is only needed once: the misnumbered libraries and misplaced
1000 binaries have been added to OptionalObsoleteFiles.inc so they will
1001 be removed during a clean upgrade.
1004 Clang and llvm have been upgraded to 3.4.1 release.
1007 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1008 be removed to avoid issues in the future (and has been added to
1012 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1013 past, it affected all builds that used the bsd.*.mk files. The old
1014 behavior was a bug, but people may have relied upon it. To get this
1015 behavior back, you can .include /etc/src.conf from /etc/make.conf
1016 (which is still global and isn't changed). This also changes the
1017 behavior of incremental builds inside the tree of individual
1018 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1019 Although this has survived make universe and some upgrade scenarios,
1020 other upgrade scenarios may have broken. At least one form of
1021 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1022 as well... In cases where MAKESYSPATH isn't working with this
1023 setting, you'll need to set it to the full path to your tree.
1025 One side effect of all this cleaning up is that bsd.compiler.mk
1026 is no longer implicitly included by bsd.own.mk. If you wish to
1027 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1031 The lindev device has been removed since /dev/full has been made a
1032 standard device. __FreeBSD_version has been bumped.
1035 The knob WITHOUT_VI was added to the base system, which controls
1036 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1037 in order to reorder files share/termcap and didn't build ex(1) as a
1038 build tool, so building/installing with WITH_VI is highly advised for
1039 build hosts for older releases.
1041 This issue has been fixed in stable/9 and stable/10 in r277022 and
1042 r276991, respectively.
1045 The YES_HESIOD knob has been removed. It has been obsolete for
1046 a decade. Please move to using WITH_HESIOD instead or your builds
1047 will silently lack HESIOD.
1050 The uart(4) driver has been changed with respect to its handling
1051 of the low-level console. Previously the uart(4) driver prevented
1052 any process from changing the baudrate or the CLOCAL and HUPCL
1053 control flags. By removing the restrictions, operators can make
1054 changes to the serial console port without having to reboot.
1055 However, when getty(8) is started on the serial device that is
1056 associated with the low-level console, a misconfigured terminal
1057 line in /etc/ttys will now have a real impact.
1058 Before upgrading the kernel, make sure that /etc/ttys has the
1059 serial console device configured as 3wire without baudrate to
1060 preserve the previous behaviour. E.g:
1061 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1064 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1065 to improve performance. To re-enable it, if needed, run rpcbind
1066 with command line option -W.
1069 Switched back to the GPL dtc compiler due to updates in the upstream
1070 dts files not being supported by the BSDL dtc compiler. You will need
1071 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1072 may result while building dtb files during a kernel build if you fail
1073 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1076 Clang and llvm have been upgraded to 3.4 release.
1079 The nve(4) driver has been removed. Please use the nfe(4) driver
1080 for NVIDIA nForce MCP Ethernet adapters instead.
1083 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1084 This could cause certain C++ applications using shared libraries built
1085 against the previous version of libc++ to crash. The incompatibility
1086 has now been fixed, but any C++ applications or shared libraries built
1087 between r261283 and r261801 should be recompiled.
1090 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1091 capability mode support. Please note that enabling the feature in
1092 kernel is still highly recommended.
1095 OpenSSH is now built with sandbox support, and will use sandbox as
1096 the default privilege separation method. This requires Capsicum
1097 capability mode support in kernel.
1100 The libelf and libdwarf libraries have been updated to newer
1101 versions from upstream. Shared library version numbers for
1102 these two libraries were bumped. Any ports or binaries
1103 requiring these two libraries should be recompiled.
1104 __FreeBSD_version is bumped to 1100006.
1107 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1108 instead of providing an explicit one, this would prevent such
1109 Makefile from providing its own Kyuafile in the future during
1110 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1111 intervention is needed to clean an objdir if you use NO_CLEAN:
1112 # find /usr/obj -name Kyuafile | xargs rm -f
1115 The behavior of gss_pseudo_random() for the krb5 mechanism
1116 has changed, for applications requesting a longer random string
1117 than produced by the underlying enctype's pseudo-random() function.
1118 In particular, the random string produced from a session key of
1119 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1120 be different at the 17th octet and later, after this change.
1121 The counter used in the PRF+ construction is now encoded as a
1122 big-endian integer in accordance with RFC 4402.
1123 __FreeBSD_version is bumped to 1100004.
1126 The WITHOUT_ATF build knob has been removed and its functionality
1127 has been subsumed into the more generic WITHOUT_TESTS. If you were
1128 using the former to disable the build of the ATF libraries, you
1129 should change your settings to use the latter.
1132 The default version of mtree is nmtree which is obtained from
1133 NetBSD. The output is generally the same, but may vary
1134 slightly. If you found you need identical output adding
1135 "-F freebsd9" to the command line should do the trick. For the
1136 time being, the old mtree is available as fmtree.
1139 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1140 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1141 1.1.4_8 and verify bsdyml not linked in, before running "make
1143 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1145 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1148 The stable/10 branch has been created in subversion from head
1152 The rc.d/jail script has been updated to support jail(8)
1153 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1154 for per-jail configuration are automatically converted to
1155 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1156 This is transparently backward compatible. See below about some
1157 incompatibilities and rc.conf(5) manual page for more details.
1159 These variables are now deprecated in favor of jail(8) configuration
1160 file. One can use "rc.d/jail config <jname>" command to generate
1161 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1162 running the jail(8) utility. The default pathname of the
1163 configuration file is /etc/jail.conf and can be specified by
1164 using $jail_conf or $jail_<jname>_conf variables.
1166 Please note that jail_devfs_ruleset accepts an integer at
1167 this moment. Please consider to rewrite the ruleset name
1171 BIND has been removed from the base system. If all you need
1172 is a local resolver, simply enable and start the local_unbound
1173 service instead. Otherwise, several versions of BIND are
1174 available in the ports tree. The dns/bind99 port is one example.
1176 With this change, nslookup(1) and dig(1) are no longer in the base
1177 system. Users should instead use host(1) and drill(1) which are
1178 in the base system. Alternatively, nslookup and dig can
1179 be obtained by installing the dns/bind-tools port.
1182 With the addition of unbound(8), a new unbound user is now
1183 required during installworld. "mergemaster -p" can be used to
1184 add the user prior to installworld, as documented in the handbook.
1187 OpenSSH is now built with DNSSEC support, and will by default
1188 silently trust signed SSHFP records. This can be controlled with
1189 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1190 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1193 The GNU Compiler Collection and C++ standard library (libstdc++)
1194 are no longer built by default on platforms where clang is the system
1195 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1196 options in src.conf.
1199 The PROCDESC kernel option is now part of the GENERIC kernel
1200 configuration and is required for the rwhod(8) to work.
1201 If you are using custom kernel configuration, you should include
1205 The API and ABI related to the Capsicum framework was modified
1206 in backward incompatible way. The userland libraries and programs
1207 have to be recompiled to work with the new kernel. This includes the
1208 following libraries and programs, but the whole buildworld is
1209 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1210 kdump, procstat, rwho, rwhod, uniq.
1213 AES-NI intrinsic support has been added to gcc. The AES-NI module
1214 has been updated to use this support. A new gcc is required to build
1215 the aesni module on both i386 and amd64.
1218 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1219 Thus "device padlock_rng" and "device rdrand_rng" should be
1220 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1223 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1224 enables just the iconv* functionality and is now on by default.
1225 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1226 compatibility. Set WITHOUT_ICONV to build the old way.
1227 If you have been using WITH_ICONV before, you will very likely
1228 need to turn on WITH_LIBICONV_COMPAT.
1231 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1232 Illumos origin, including ZFS. If you have INVARIANTS in your
1233 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1235 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1236 locks if WITNESS option was set. Because that generated a lot of
1237 witness(9) reports and all of them were believed to be false
1238 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1239 can be used to achieve the previous behavior.
1242 Timer values in IPv6 data structures now use time_uptime instead
1243 of time_second. Although this is not a user-visible functional
1244 change, userland utilities which directly use them---ndp(8),
1245 rtadvd(8), and rtsold(8) in the base system---need to be updated
1246 to r253970 or later.
1249 find -delete can now delete the pathnames given as arguments,
1250 instead of only files found below them or if the pathname did
1251 not contain any slashes. Formerly, the following error message
1254 find: -delete: <path>: relative path potentially not safe
1256 Deleting the pathnames given as arguments can be prevented
1257 without error messages using -mindepth 1 or by changing
1258 directory and passing "." as argument to find. This works in the
1259 old as well as the new version of find.
1262 Behavior of devfs rules path matching has been changed.
1263 Pattern is now always matched against fully qualified devfs
1264 path and slash characters must be explicitly matched by
1265 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1266 subdirectories must be reviewed.
1269 The default ARM ABI has changed to the ARM EABI. The old ABI is
1270 incompatible with the ARM EABI and all programs and modules will
1271 need to be rebuilt to work with a new kernel.
1273 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1275 NOTE: Support for the old ABI will be removed in the future and
1276 users are advised to upgrade.
1279 pkg_install has been disconnected from the build if you really need it
1280 you should add WITH_PKGTOOLS in your src.conf(5).
1283 Most of network statistics structures were changed to be able
1284 keep 64-bits counters. Thus all tools, that work with networking
1285 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1288 Fix a bug that allowed a tracing process (e.g. gdb) to write
1289 to a memory-mapped file in the traced process's address space
1290 even if neither the traced process nor the tracing process had
1291 write access to that file.
1294 CVS has been removed from the base system. An exact copy
1295 of the code is available from the devel/cvs port.
1298 Some people report the following error after the switch to bmake:
1300 make: illegal option -- J
1301 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1303 *** [buildworld] Error code 2
1305 this likely due to an old instance of make in
1306 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1307 which src/Makefile will use that blindly, if it exists, so if
1308 you see the above error:
1310 rm -rf `make -V MAKEPATH`
1315 Use bmake by default.
1316 Whereas before one could choose to build with bmake via
1317 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1318 make. The goal is to remove these knobs for 10-RELEASE.
1320 It is worth noting that bmake (like gmake) treats the command
1321 line as the unit of failure, rather than statements within the
1322 command line. Thus '(cd some/where && dosomething)' is safer
1323 than 'cd some/where; dosomething'. The '()' allows consistent
1324 behavior in parallel build.
1327 Fix a bug that allows NFS clients to issue READDIR on files.
1330 The WITHOUT_IDEA option has been removed because
1331 the IDEA patent expired.
1334 The sysctl which controls TRIM support under ZFS has been renamed
1335 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1339 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1340 rather than creating it's own in the temporary directory in
1341 order allow access to bootstrapped versions of tools such as
1342 install and mtree. When upgrading from version of FreeBSD where
1343 the install command does not support -l, you will need to
1344 install a new mergemaster command if mergemaster -p is required.
1345 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1349 Legacy ATA stack, disabled and replaced by new CAM-based one since
1350 FreeBSD 9.0, completely removed from the sources. Kernel modules
1351 atadisk and atapi*, user-level tools atacontrol and burncd are
1352 removed. Kernel option `options ATA_CAM` is now permanently enabled
1356 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1357 and socketpair(2). Software, in particular Kerberos, may
1358 automatically detect and use these during building. The resulting
1359 binaries will not work on older kernels.
1362 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1363 information, see the respective 20130304 entry).
1366 Recent commits to callout(9) changed the size of struct callout,
1367 so the KBI is probably heavily disturbed. Also, some functions
1368 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1369 by macros. Every kernel module using it won't load, so rebuild
1372 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1373 but does not initialize by default (because of the new CTL_DISABLE
1374 option) to save memory. To re-enable it, remove the CTL_DISABLE
1375 option from the kernel config file or set kern.cam.ctl.disable=0
1376 in /boot/loader.conf.
1379 The ctl device has been disabled in GENERIC for i386 and amd64.
1380 This was done due to the extra memory being allocated at system
1381 initialisation time by the ctl driver which was only used if
1382 a CAM target device was created. This makes a FreeBSD system
1383 unusable on 128MB or less of RAM.
1386 A new compression method (lz4) has been merged to -HEAD. Please
1387 refer to zpool-features(7) for more information.
1389 Please refer to the "ZFS notes" section of this file for information
1390 on upgrading boot ZFS pools.
1393 A BSD-licensed patch(1) variant has been added and is installed
1394 as bsdpatch, being the GNU version the default patch.
1395 To inverse the logic and use the BSD-licensed one as default,
1396 while having the GNU version installed as gnupatch, rebuild
1397 and install world with the WITH_BSD_PATCH knob set.
1400 Due to the use of the new -l option to install(1) during build
1401 and install, you must take care not to directly set the INSTALL
1402 make variable in your /etc/make.conf, /etc/src.conf, or on the
1403 command line. If you wish to use the -C flag for all installs
1404 you may be able to add INSTALL+=-C to /etc/make.conf or
1408 The install(1) option -M has changed meaning and now takes an
1409 argument that is a file or path to append logs to. In the
1410 unlikely event that -M was the last option on the command line
1411 and the command line contained at least two files and a target
1412 directory the first file will have logs appended to it. The -M
1413 option served little practical purpose in the last decade so its
1414 use is expected to be extremely rare.
1417 After switching to Clang as the default compiler some users of ZFS
1418 on i386 systems started to experience stack overflow kernel panics.
1419 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1422 GEOM_LABEL now mangles label names read from file system metadata.
1423 Mangling affect labels containing spaces, non-printable characters,
1424 '%' or '"'. Device names in /etc/fstab and other places may need to
1428 By default, only the 10 most recent kernel dumps will be saved. To
1429 restore the previous behaviour (no limit on the number of kernel dumps
1430 stored in the dump directory) add the following line to /etc/rc.conf:
1435 With the addition of auditdistd(8), a new auditdistd user is now
1436 required during installworld. "mergemaster -p" can be used to
1437 add the user prior to installworld, as documented in the handbook.
1440 The sin6_scope_id member variable in struct sockaddr_in6 is now
1441 filled by the kernel before passing the structure to the userland via
1442 sysctl or routing socket. This means the KAME-specific embedded scope
1443 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1444 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1445 __FreeBSD_version is bumped to 1000025.
1448 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1449 This means that the world and kernel will be compiled with clang
1450 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1451 and /usr/bin/cpp. To disable this behavior and revert to building
1452 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1453 of current may need to bootstrap WITHOUT_CLANG first if the clang
1454 build fails (its compatibility window doesn't extend to the 9 stable
1458 The IPFIREWALL_FORWARD kernel option has been removed. Its
1459 functionality now turned on by default.
1462 The ZERO_COPY_SOCKET kernel option has been removed and
1463 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1464 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1465 mechanism which is not safe and may result in kernel crashes.
1466 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1467 driver supports disposeable external page sized mbuf storage.
1468 Proper replacements for both zero-copy mechanisms are under
1469 consideration and will eventually lead to complete removal
1470 of the two kernel options.
1473 The IPv4 network stack has been converted to network byte
1474 order. The following modules need to be recompiled together
1475 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1476 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1479 Support for non-MPSAFE filesystems was removed from VFS. The
1480 VFS_VERSION was bumped, all filesystem modules shall be
1484 All the non-MPSAFE filesystems have been disconnected from
1485 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1486 portalfs, smbfs, xfs.
1489 The interface cloning API and ABI has changed. The following
1490 modules need to be recompiled together with kernel:
1491 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1492 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1493 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1496 The sdhci driver was split in two parts: sdhci (generic SD Host
1497 Controller logic) and sdhci_pci (actual hardware driver).
1498 No kernel config modifications are required, but if you
1499 load sdhc as a module you must switch to sdhci_pci instead.
1502 Import the FUSE kernel and userland support into base system.
1505 The GNU sort(1) program has been removed since the BSD-licensed
1506 sort(1) has been the default for quite some time and no serious
1507 problems have been reported. The corresponding WITH_GNU_SORT
1511 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1512 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1516 The net80211(4) ABI has been changed to allow for improved driver
1517 PS-POLL and power-save support. All wireless drivers need to be
1518 recompiled to work with the new kernel.
1521 The random(4) support for the VIA hardware random number
1522 generator (`PADLOCK') is no longer enabled unconditionally.
1523 Add the padlock_rng device in the custom kernel config if
1524 needed. The GENERIC kernels on i386 and amd64 do include the
1525 device, so the change only affects the custom kernel
1529 The pf(4) packet filter ABI has been changed. pfctl(8) and
1530 snmp_pf module need to be recompiled to work with new kernel.
1533 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1534 to -HEAD. Pools that have empty_bpobj in active state can not be
1535 imported read-write with ZFS implementations that do not support
1536 this feature. For more information read the zpool-features(5)
1540 The sparc64 ZFS loader has been changed to no longer try to auto-
1541 detect ZFS providers based on diskN aliases but now requires these
1542 to be explicitly listed in the OFW boot-device environment variable.
1545 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1546 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1547 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1550 The following sysctls and tunables have been renamed for consistency
1551 with other variables:
1552 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1553 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1556 The sort utility has been replaced with BSD sort. For now, GNU sort
1557 is also available as "gnusort" or the default can be set back to
1558 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1559 installed as "bsdsort".
1562 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1563 Starting with this version the old system of ZFS pool versioning
1564 is superseded by "feature flags". This concept enables forward
1565 compatibility against certain future changes in functionality of ZFS
1566 pools. The first read-only compatible "feature flag" for ZFS pools
1567 is named "com.delphix:async_destroy". For more information
1568 read the new zpool-features(5) manual page.
1569 Please refer to the "ZFS notes" section of this file for information
1570 on upgrading boot ZFS pools.
1573 The malloc(3) implementation embedded in libc now uses sources imported
1574 as contrib/jemalloc. The most disruptive API change is to
1575 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1576 delete it prior to installworld, and optionally re-create it using the
1577 new format after rebooting. See malloc.conf(5) for details
1578 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1582 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1583 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1584 now spelled mips. This is to aid compatibility with third-party
1585 software that expects this naming scheme in uname(3). Little-endian
1586 settings are unchanged. If you are updating a big-endian mips64 machine
1587 from before this change, you may need to set MACHINE_ARCH=mips64 in
1588 your environment before the new build system will recognize your machine.
1591 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1595 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1596 nullfs(5) did not pass through all behaviours to the underlying layer,
1597 as a result if we bound to a socket on the lower layer we could connect
1598 only to the lower path; if we bound to the upper layer we could connect
1599 only to the upper path. The new behavior is one can connect to both the
1600 lower and the upper paths regardless what layer path one binds to.
1603 The getifaddrs upgrade path broken with 20111215 has been restored.
1604 If you have upgraded in between 20111215 and 20120209 you need to
1605 recompile libc again with your kernel. You still need to recompile
1606 world to be able to configure CARP but this restriction already
1607 comes from 20111215.
1610 The set_rcvar() function has been removed from /etc/rc.subr. All
1611 base and ports rc.d scripts have been updated, so if you have a
1612 port installed with a script in /usr/local/etc/rc.d you can either
1613 hand-edit the rcvar= line, or reinstall the port.
1615 An easy way to handle the mass-update of /etc/rc.d:
1616 rm /etc/rc.d/* && mergemaster -i
1619 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1620 on the current CPU and prevents other threads from running.
1621 This behavior can be reverted using the kern.stop_scheduler_on_panic
1623 The new behavior can be incompatible with kern.sync_on_panic.
1626 The carp(4) facility has been changed significantly. Configuration
1627 of the CARP protocol via ifconfig(8) has changed, as well as format
1628 of CARP events submitted to devd(8) has changed. See manual pages
1629 for more information. The arpbalance feature of carp(4) is currently
1630 not supported anymore.
1632 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1633 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1634 need to be recompiled.
1637 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1641 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1642 explicitely support non-MPSAFE filesystems.
1643 It is on by default for all supported platform at this present
1647 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1648 i386 and pc98 GENERIC kernel configuration files.
1651 sysinstall has been removed
1654 The stable/9 branch created in subversion. This corresponds to the
1655 RELENG_9 branch in CVS.
1661 Avoid using make -j when upgrading. While generally safe, there are
1662 sometimes problems using -j to upgrade. If your upgrade fails with
1663 -j, please try again without -j. From time to time in the past there
1664 have been problems using -j with buildworld and/or installworld. This
1665 is especially true when upgrading between "distant" versions (eg one
1666 that cross a major release boundary or several minor releases, or when
1667 several months have passed on the -current branch).
1669 Sometimes, obscure build problems are the result of environment
1670 poisoning. This can happen because the make utility reads its
1671 environment when searching for values for global variables. To run
1672 your build attempts in an "environmental clean room", prefix all make
1673 commands with 'env -i '. See the env(1) manual page for more details.
1675 When upgrading from one major version to another it is generally best
1676 to upgrade to the latest code in the currently installed branch first,
1677 then do an upgrade to the new branch. This is the best-tested upgrade
1678 path, and has the highest probability of being successful. Please try
1679 this approach before reporting problems with a major version upgrade.
1681 When upgrading a live system, having a root shell around before
1682 installing anything can help undo problems. Not having a root shell
1683 around can lead to problems if pam has changed too much from your
1684 starting point to allow continued authentication after the upgrade.
1686 This file should be read as a log of events. When a later event changes
1687 information of a prior event, the prior event should not be deleted.
1688 Instead, a pointer to the entry with the new information should be
1689 placed in the old entry. Readers of this file should also sanity check
1690 older entries before relying on them blindly. Authors of new entries
1691 should write them with this in mind.
1695 When upgrading the boot ZFS pool to a new version, always follow
1698 1.) recompile and reinstall the ZFS boot loader and boot block
1699 (this is part of "make buildworld" and "make installworld")
1701 2.) update the ZFS boot block on your boot drive
1703 The following example updates the ZFS boot block on the first
1704 partition (freebsd-boot) of a GPT partitioned drive ada0:
1705 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1707 Non-boot pools do not need these updates.
1711 If you are updating from a prior version of FreeBSD (even one just
1712 a few days old), you should follow this procedure. It is the most
1713 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1715 make kernel-toolchain
1716 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1717 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1719 To test a kernel once
1720 ---------------------
1721 If you just want to boot a kernel once (because you are not sure
1722 if it works, or if you want to boot a known bad kernel to provide
1723 debugging information) run
1724 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1725 nextboot -k testkernel
1727 To just build a kernel when you know that it won't mess you up
1728 --------------------------------------------------------------
1729 This assumes you are already running a CURRENT system. Replace
1730 ${arch} with the architecture of your machine (e.g. "i386",
1731 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1733 cd src/sys/${arch}/conf
1734 config KERNEL_NAME_HERE
1735 cd ../compile/KERNEL_NAME_HERE
1740 If this fails, go to the "To build a kernel" section.
1742 To rebuild everything and install it on the current system.
1743 -----------------------------------------------------------
1744 # Note: sometimes if you are running current you gotta do more than
1745 # is listed here if you are upgrading from a really old current.
1747 <make sure you have good level 0 dumps>
1749 make kernel KERNCONF=YOUR_KERNEL_HERE
1751 <reboot in single user> [3]
1758 To cross-install current onto a separate partition
1759 --------------------------------------------------
1760 # In this approach we use a separate partition to hold
1761 # current's root, 'usr', and 'var' directories. A partition
1762 # holding "/", "/usr" and "/var" should be about 2GB in
1765 <make sure you have good level 0 dumps>
1768 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1769 <maybe newfs current's root partition>
1770 <mount current's root partition on directory ${CURRENT_ROOT}>
1771 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1772 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1773 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1774 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1775 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1776 <reboot into current>
1777 <do a "native" rebuild/install as described in the previous section>
1778 <maybe install compatibility libraries from ports/misc/compat*>
1782 To upgrade in-place from stable to current
1783 ----------------------------------------------
1784 <make sure you have good level 0 dumps>
1786 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1788 <reboot in single user> [3]
1795 Make sure that you've read the UPDATING file to understand the
1796 tweaks to various things you need. At this point in the life
1797 cycle of current, things change often and you are on your own
1798 to cope. The defaults can also change, so please read ALL of
1799 the UPDATING entries.
1801 Also, if you are tracking -current, you must be subscribed to
1802 freebsd-current@freebsd.org. Make sure that before you update
1803 your sources that you have read and understood all the recent
1804 messages there. If in doubt, please track -stable which has
1805 much fewer pitfalls.
1807 [1] If you have third party modules, such as vmware, you
1808 should disable them at this point so they don't crash your
1811 [3] From the bootblocks, boot -s, and then do
1816 adjkerntz -i # if CMOS is wall time
1817 Also, when doing a major release upgrade, it is required that
1818 you boot into single user mode to do the installworld.
1820 [4] Note: This step is non-optional. Failure to do this step
1821 can result in a significant reduction in the functionality of the
1822 system. Attempting to do it by hand is not recommended and those
1823 that pursue this avenue should read this file carefully, as well
1824 as the archives of freebsd-current and freebsd-hackers mailing lists
1825 for potential gotchas. The -U option is also useful to consider.
1826 See mergemaster(8) for more information.
1828 [5] Usually this step is a noop. However, from time to time
1829 you may need to do this if you get unknown user in the following
1830 step. It never hurts to do it all the time. You may need to
1831 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1832 install) after the buildworld before this step if you last updated
1833 from current before 20130425 or from -stable before 20130430.
1835 [6] This only deletes old files and directories. Old libraries
1836 can be deleted by "make delete-old-libs", but you have to make
1837 sure that no program is using those libraries anymore.
1839 [8] The new kernel must be able to run existing binaries used by
1840 an installworld. When upgrading across major versions, the new
1841 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1842 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1843 binaries). Failure to do so may leave you with a system that is
1844 hard to boot to recover. A GENERIC kernel will include suitable
1845 compatibility options to run binaries from older branches.
1847 Make sure that you merge any new devices from GENERIC since the
1848 last time you updated your kernel config file.
1850 [9] When checking out sources, you must include the -P flag to have
1851 cvs prune empty directories.
1853 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1854 "?=" instead of the "=" assignment operator, so that buildworld can
1855 override the CPUTYPE if it needs to.
1857 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1858 not on the command line, or in /etc/make.conf. buildworld will
1859 warn if it is improperly defined.
1862 This file contains a list, in reverse chronological order, of major
1863 breakages in tracking -current. It is not guaranteed to be a complete
1864 list of such breakages, and only contains entries since September 23, 2011.
1865 If you need to see UPDATING entries from before that date, you will need
1866 to fetch an UPDATING file from an older FreeBSD release.
1868 Copyright information:
1870 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1872 Redistribution, publication, translation and use, with or without
1873 modification, in full or in part, in any form or format of this
1874 document are permitted without further permission from the author.
1876 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1877 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1878 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1879 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1880 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1881 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1882 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1883 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1884 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1885 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1886 POSSIBILITY OF SUCH DAMAGE.
1888 Contact Warner Losh if you have any questions about your use of