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.
20 Co-existance for Forth and Lua interpreters in bootloaders has now been
21 merged to ease testing of lualoader. LOADER_DEFAULT_INTERP, documented
22 in build(7), may be used to control which interpreter flavor is used in
23 the default loader to be installed. For systems where Lua and Forth
24 coexist, this switch can also be made on a running system by creating a
25 link from /boot/loader{,.efi} to /boot/loader_${flavor}{,.efi} rather
26 than requiring a rebuild.
28 The default flavor in this branch will remain Forth. As indicated in
29 the 20190216 UPDATING entry, booting is a complex environment; it would
30 be prudent to assume that lualoader may not work for your setup and make
31 provisions for backup boot methods.
34 zfsloader's functionality has now been folded into loader.
35 zfsloader is no longer necesasary once you've updated your
36 boot blocks. For a transition period, we will install a
37 hardlink for zfsloader to loader to allow a smooth transition
38 until the boot blocks can be updated (hard link because old
39 zfs boot blocks don't understand symlinks).
42 Lualoader has been merged to facilitate testing on this branch. It's
43 purely opt-in for now by building WITH_LOADER_LUA and WITHOUT_FORTH in
44 /etc/src.conf, but co-existance will come shortly. Booting is a complex
45 environment and test coverage for Lua-enabled loaders has been thin, so
46 it would be prudent to assume it might not work and make provisions for
50 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
51 7.0.1. Please see the 20141231 entry below for information about
52 prerequisites and upgrading, if you are not already using clang 3.5.0
56 r342562 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
57 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
58 servers that have vfs.nfsd.nfs_privport set will only allow mounts
59 from clients using a reserved port#. Since both the FreeBSD and Linux
60 NFSv4 clients use reserved port#s by default, this should not affect
64 The '%I' format in the kern.corefile sysctl limits the number of
65 core files that a process can generate to the number stored in the
66 debug.ncores sysctl. The '%I' format is replaced by the single digit
67 index. Previously, if all indexes were taken the kernel would overwrite
68 only a core file with the highest index in a filename.
69 Currently the system will create a new core file if there is a free
70 index or if all slots are taken it will overwrite the oldest one.
73 WITH_OFED option now only enables the build for the OFED libraries
74 and some fundamental client utilities. OpenSM and rest of the
75 debugging tools are enabled by WITH_OFED_EXTRA build switch.
76 WITH_OFED is turned on by default on amd64.
79 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
80 6.0.1. Please see the 20141231 entry below for information about
81 prerequisites and upgrading, if you are not already using clang 3.5.0
85 The releng/11.2 branch has been created from stable/11@r334458.
88 The tz database (tzdb) has been updated to 2018e. This version more
89 correctly models time stamps in time zones with negative DST such as
90 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
91 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
92 time zone abbreviations and the tm_isdst flag.
95 The use of RSS hash from the network card aka flowid has been
96 disabled by default for lagg(4) as it's currently incompatible with
97 the lacp and loadbalance protocols.
99 This can be re-enabled by setting the following in loader.conf:
100 net.link.lagg.default_use_flowid="1"
103 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
104 6.0.0. Please see the 20141231 entry below for information about
105 prerequisites and upgrading, if you are not already using clang 3.5.0
109 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
110 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
111 to WITH/OUT_LOADER_GELI.
114 The geli password typed at boot is now hidden. To restore the previous
115 behavior, see geli(8) for configuration options.
117 The SW_WATCHDOG option is no longer necessary to enable the
118 hardclock-based software watchdog if no hardware watchdog is
119 configured. As before, SW_WATCHDOG will cause the software
120 watchdog to be enabled even if a hardware watchdog is configured.
123 lint(1) binaries and library are no longer built by default. To
124 enable building them, define WITH_LINT in src.conf. If you are using
125 a FreeBSD 12 or later system to build 11-stable, you may need to
126 install a lint(1) binary to use WITH_LINT.
129 When building multiple kernels using KERNCONF, non-existent KERNCONF
130 files will produce an error and buildkernel will fail. Previously
131 missing KERNCONF files silently failed giving no indication as to
132 why, only to subsequently discover during installkernel that the
133 desired kernel was never built in the first place.
136 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
137 Please see the 20141231 entry below for information about prerequisites
138 and upgrading, if you are not already using clang 3.5.0 or higher.
141 Since the switch to GPT disk labels, fsck for UFS/FFS has been
142 unable to automatically find alternate superblocks. As of r322806,
143 the information needed to find alternate superblocks has been
144 moved to the end of the area reserved for the boot block.
145 Filesystems created with a newfs of this vintage or later
146 will create the recovery information. If you have a filesystem
147 created prior to this change and wish to have a recovery block
148 created for your filesystem, you can do so by running fsck in
149 forground mode (i.e., do not use the -p or -y options). As it
150 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
151 to which you should answer yes.
154 The releng/11.1 branch has been created from stable/11@r320475.
157 arm64 builds now use the base system LLD 4.0.0 linker by default,
158 instead of requiring that the aarch64-binutils port or package be
159 installed. To continue using aarch64-binutils, set
160 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
163 The ctl.ko module no longer implements the iSCSI target frontend:
164 cfiscsi.ko does instead.
166 If building cfiscsi.ko as a kernel module, the module can be loaded
167 via one of the following methods:
168 - `cfiscsi_load="YES"` in loader.conf(5).
169 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
170 - ctladm(8)/ctld(8), when compiled with iSCSI support
171 (`WITH_ISCSI=yes` in src.conf(5))
173 Please see cfiscsi(4) for more details.
176 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
177 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
178 same source (previously, the dependency of mmcsd.ko on mmc.ko was
179 missing, but mmcsd.ko now will refuse to load if it is incompatible
183 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
184 use any explicitly assigned loopback address available in the jail
185 instead of using the first assigned address of the jail.
188 As of r316810 for ipfilter, keep frags is no longer assumed when
189 keep state is specified in a rule. r316810 aligns ipfilter with
190 documentation in man pages separating keep frags from keep state.
191 This allows keep state to specified without forcing keep frags
192 and allows keep frags to be specified independently of keep state.
193 To maintain previous behaviour, also specify keep frags with
194 keep state (as documented in ipf.conf.5).
197 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
198 Please see the 20141231 entry below for information about prerequisites
199 and upgrading, if you are not already using clang 3.5.0 or higher.
202 The code that provides support for ZFS .zfs/ directory functionality
203 has been reimplemented. It's not possible now to create a snapshot
204 by mkdir under .zfs/snapshot/. That should be the only user visible
208 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
209 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
210 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
211 and now NAT-T is supported by default. Security associations now use
212 the single namespace for SPI allocation, so if you use several manually
213 configured security associations with the same SPI, this configuration
217 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
218 Please see the 20141231 entry below for information about prerequisites
219 and upgrading, if you are not already using clang 3.5.0 or higher.
222 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
223 Please see the 20141231 entry below for information about prerequisites
224 and upgrading, if you are not already using clang 3.5.0 or higher.
227 The layout of the pmap structure has changed for powerpc to put the pmap
228 statistics at the front for all CPU variations. libkvm(3) and all tools
229 that link against it need to be recompiled.
232 isl(4) and cyapa(4) drivers now require a new driver,
233 chromebook_platform(4), to work properly on Chromebook-class hardware.
234 On other types of hardware the drivers may need to be configured using
235 device hints. Please see the corresponding manual pages for details.
238 Relocatable object files with the extension of .So have been renamed
239 to use an extension of .pico instead. The purpose of this change is
240 to avoid a name clash with shared libraries on case-insensitive file
241 systems. On those file systems, foo.So is the same file as foo.so.
244 The releng/11.0 branch has been created from stable/11@r303970.
247 The stable/11 branch has been created from head@r302406.
250 The libc stub for the pipe(2) system call has been replaced with
251 a wrapper that calls the pipe2(2) system call and the pipe(2)
252 system call is now only implemented by the kernels that include
253 "options COMPAT_FREEBSD10" in their config file (this is the
254 default). Users should ensure that this option is enabled in
255 their kernel or upgrade userspace to r302092 before upgrading their
259 CAM will now strip leading spaces from SCSI disks' serial numbers.
260 This will effect users who create UFS filesystems on SCSI disks using
261 those disk's diskid device nodes. For example, if /etc/fstab
262 previously contained a line like
263 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
264 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
265 transforms like gmirror may also be affected. ZFS users should
269 The bitstring(3) API has been updated with new functionality and
270 improved performance. But it is binary-incompatible with the old API.
271 Objects built with the new headers may not be linked against objects
272 built with the old headers.
275 The brk and sbrk functions have been removed from libc on arm64.
276 Binutils from ports has been updated to not link to these
277 functions and should be updated to the latest version before
278 installing a new libc.
281 The armv6 port now defaults to hard float ABI. Limited support
282 for running both hardfloat and soft float on the same system
283 is available using the libraries installed with -DWITH_LIBSOFT.
284 This has only been tested as an upgrade path for installworld
285 and packages may fail or need manual intervention to run. New
286 packages will be needed.
288 To update an existing self-hosted armv6hf system, you must add
289 TARGET_ARCH=armv6 on the make command line for both the build
290 and the install steps.
293 Kernel modules compiled outside of a kernel build now default to
294 installing to /boot/modules instead of /boot/kernel. Many kernel
295 modules built this way (such as those in ports) already overrode
296 KMODDIR explicitly to install into /boot/modules. However,
297 manually building and installing a module from /sys/modules will
298 now install to /boot/modules instead of /boot/kernel.
301 The CAM I/O scheduler has been committed to the kernel. There should be
302 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
303 list of known rogues that claim support for this but actually corrupt
304 data is believed to be complete, be on the lookout for data
305 corruption. The known rogue list is believed to be complete:
307 o Crucial MX100, M550 drives with MU01 firmware.
308 o Micron M510 and M550 drives with MU01 firmware.
309 o Micron M500 prior to MU07 firmware
310 o Samsung 830, 840, and 850 all firmwares
311 o FCCT M500 all firmwares
313 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
314 with working NCQ TRIM. For Micron branded drives, see your sales rep for
315 updated firmware. Black listed drives will work correctly because these
316 drives work correctly so long as no NCQ TRIMs are sent to them. Given
317 this list is the same as found in Linux, it's believed there are no
318 other rogues in the market place. All other models from the above
321 To be safe, if you are at all concerned, you can quirk each of your
322 drives to prevent NCQ from being sent by setting:
323 kern.cam.ada.X.quirks="0x2"
324 in loader.conf. If the drive requires the 4k sector quirk, set the
328 The FAST_DEPEND build option has been removed and its functionality is
329 now the one true way. The old mkdep(1) style of 'make depend' has
330 been removed. See 20160311 for further details.
333 Resource range types have grown from unsigned long to uintmax_t. All
334 drivers, and anything using libdevinfo, need to be recompiled.
337 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
338 builds. It no longer runs mkdep(1) during 'make depend', and the
339 'make depend' stage can safely be skipped now as it is auto ran
340 when building 'make all' and will generate all SRCS and DPSRCS before
341 building anything else. Dependencies are gathered at compile time with
342 -MF flags kept in separate .depend files per object file. Users should
343 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
347 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
348 kernel modules. Therefore, if you load any kernel modules at boot time,
349 please install the boot loaders after you install the kernel, but before
353 make kernel KERNCONF=YOUR_KERNEL_HERE
354 make -C sys/boot install
355 <reboot in single user>
357 Then follow the usual steps, described in the General Notes section,
361 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
362 see the 20141231 entry below for information about prerequisites and
363 upgrading, if you are not already using clang 3.5.0 or higher.
366 The AIO subsystem is now a standard part of the kernel. The
367 VFS_AIO kernel option and aio.ko kernel module have been removed.
368 Due to stability concerns, asynchronous I/O requests are only
369 permitted on sockets and raw disks by default. To enable
370 asynchronous I/O requests on all file types, set the
371 vfs.aio.enable_unsafe sysctl to a non-zero value.
374 The ELF object manipulation tool objcopy is now provided by the
375 ELF Tool Chain project rather than by GNU binutils. It should be a
376 drop-in replacement, with the addition of arm64 support. The
377 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
378 to obtain the GNU version if necessary.
381 Building ZFS pools on top of zvols is prohibited by default. That
382 feature has never worked safely; it's always been prone to deadlocks.
383 Using a zvol as the backing store for a VM guest's virtual disk will
384 still work, even if the guest is using ZFS. Legacy behavior can be
385 restored by setting vfs.zfs.vol.recursive=1.
388 The NONE and HPN patches has been removed from OpenSSH. They are
389 still available in the security/openssh-portable port.
392 With the addition of ypldap(8), a new _ypldap user is now required
393 during installworld. "mergemaster -p" can be used to add the user
394 prior to installworld, as documented in the handbook.
397 The tftp loader (pxeboot) now uses the option root-path directive. As a
398 consequence it no longer looks for a pxeboot.4th file on the tftp
399 server. Instead it uses the regular /boot infrastructure as with the
403 The code to start recording plug and play data into the modules has
404 been committed. While the old tools will properly build a new kernel,
405 a number of warnings about "unknown metadata record 4" will be produced
406 for an older kldxref. To avoid such warnings, make sure to rebuild
407 the kernel toolchain (or world). Make sure that you have r292078 or
408 later when trying to build 292077 or later before rebuilding.
411 Debug data files are now built by default with 'make buildworld' and
412 installed with 'make installworld'. This facilitates debugging but
413 requires more disk space both during the build and for the installed
414 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
418 r291527 changed the internal interface between the nfsd.ko and
419 nfscommon.ko modules. As such, they must both be upgraded to-gether.
420 __FreeBSD_version has been bumped because of this.
423 Add support for unicode collation strings leads to a change of
424 order of files listed by ls(1) for example. To get back to the old
425 behaviour, set LC_COLLATE environment variable to "C".
427 Databases administrators will need to reindex their databases given
428 collation results will be different.
430 Due to a bug in install(1) it is recommended to remove the ancient
431 locales before running make installworld.
433 rm -rf /usr/share/locale/*
436 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
437 libcrypto.so.7 or libssl.so.7 must be recompiled.
440 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
441 Kernel modules isp_2400_multi and isp_2500_multi were removed and
442 should be replaced with isp_2400 and isp_2500 modules respectively.
445 The build previously allowed using 'make -n' to not recurse into
446 sub-directories while showing what commands would be executed, and
447 'make -n -n' to recursively show commands. Now 'make -n' will recurse
448 and 'make -N' will not.
451 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
452 and etcupdate will now use this file. A custom sendmail.cf is now
453 updated via this mechanism rather than via installworld. If you had
454 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
455 want to remove the exclusion or change it to "always install".
456 /etc/mail/sendmail.cf is now managed the same way regardless of
457 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
458 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
461 Compatibility shims for legacy ATA device names have been removed.
462 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
463 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
464 environment variables, /dev/ad* and /dev/ar* symbolic links.
467 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
468 Please see the 20141231 entry below for information about prerequisites
469 and upgrading, if you are not already using clang 3.5.0 or higher.
472 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
473 and renamed from .symbols to .debug. This reduces the size requirements
474 on the boot partition or file system and provides consistency with
475 userland debug files.
477 When using the supported kernel installation method the
478 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
479 as is done with /boot/kernel.
481 Developers wishing to maintain the historical behavior of installing
482 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
485 The wireless drivers had undergone changes that remove the 'parent
486 interface' from the ifconfig -l output. The rc.d network scripts
487 used to check presence of a parent interface in the list, so old
488 scripts would fail to start wireless networking. Thus, etcupdate(3)
489 or mergemaster(8) run is required after kernel update, to update your
490 rc.d scripts in /etc.
493 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
494 These configurations are now automatically interpreted as
495 'scrub fragment reassemble'.
498 Kernel-loadable modules for the random(4) device are back. To use
499 them, the kernel must have
502 options RANDOM_LOADABLE
504 kldload(8) can then be used to load random_fortuna.ko
505 or random_yarrow.ko. Please note that due to the indirect
506 function calls that the loadable modules need to provide,
507 the build-in variants will be slightly more efficient.
509 The random(4) kernel option RANDOM_DUMMY has been retired due to
510 unpopularity. It was not all that useful anyway.
513 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
514 Control over building the ELF Tool Chain tools is now provided by
515 the WITHOUT_TOOLCHAIN knob.
518 The polarity of Pulse Per Second (PPS) capture events with the
519 uart(4) driver has been corrected. Prior to this change the PPS
520 "assert" event corresponded to the trailing edge of a positive PPS
521 pulse and the "clear" event was the leading edge of the next pulse.
523 As the width of a PPS pulse in a typical GPS receiver is on the
524 order of 1 millisecond, most users will not notice any significant
525 difference with this change.
527 Anyone who has compensated for the historical polarity reversal by
528 configuring a negative offset equal to the pulse width will need to
529 remove that workaround.
532 The default group assigned to /dev/dri entries has been changed
533 from 'wheel' to 'video' with the id of '44'. If you want to have
534 access to the dri devices please add yourself to the video group
537 # pw groupmod video -m $USER
540 The menu.rc and loader.rc files will now be replaced during
541 upgrades. Please migrate local changes to menu.rc.local and
542 loader.rc.local instead.
545 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
546 strings and strip have been removed. The src.conf(5) knob
547 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
550 As ZFS requires more kernel stack pages than is the default on some
551 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
552 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
554 Please consider using 'options KSTACK_PAGES=X' where X is greater
555 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
558 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
559 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
560 default, i.e., they will not contain "::". For example, instead
561 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
562 to have a more specific match, such as different map entries for
563 IPv6:0:0 vs IPv6:0. This change requires that configuration
564 data (including maps, files, classes, custom ruleset, etc.) must
565 use the same format, so make certain such configuration data is
566 upgrading. As a very simple check search for patterns like
567 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
568 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
569 the cf option UseCompressedIPv6Addresses.
572 The default kernel entropy-processing algorithm is now
573 Fortuna, replacing Yarrow.
575 Assuming you have 'device random' in your kernel config
576 file, the configurations allow a kernel option to override
577 this default. You may choose *ONE* of:
579 options RANDOM_YARROW # Legacy /dev/random algorithm.
580 options RANDOM_DUMMY # Blocking-only driver.
582 If you have neither, you get Fortuna. For most people,
583 read no further, Fortuna will give a /dev/random that works
584 like it always used to, and the difference will be irrelevant.
586 If you remove 'device random', you get *NO* kernel-processed
587 entropy at all. This may be acceptable to folks building
588 embedded systems, but has complications. Carry on reading,
589 and it is assumed you know what you need.
591 *PLEASE* read random(4) and random(9) if you are in the
592 habit of tweaking kernel configs, and/or if you are a member
593 of the embedded community, wanting specific and not-usual
594 behaviour from your security subsystems.
596 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
597 random', you will NOT have a functioning /dev/random, and
598 many cryptographic features will not work, including SSH.
599 You may also find strange behaviour from the random(3) set
600 of library functions, in particular sranddev(3), srandomdev(3)
601 and arc4random(3). The reason for this is that the KERN_ARND
602 sysctl only returns entropy if it thinks it has some to
603 share, and with RANDOM_DUMMY or no 'device random' this
607 An additional fix for the issue described in the 20150614 sendmail
608 entry below has been been committed in revision 284717.
611 FreeBSD's old make (fmake) has been removed from the system. It is
612 available as the devel/fmake port or via pkg install fmake.
615 The fix for the issue described in the 20150614 sendmail entry
616 below has been been committed in revision 284436. The work
617 around described in that entry is no longer needed unless the
618 default setting is overridden by a confDH_PARAMETERS configuration
619 setting of '5' or pointing to a 512 bit DH parameter file.
622 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
623 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
624 and devel/kyua to version 0.20+ and adjust any calling code to work
625 with Kyuafile and kyua.
628 The import of openssl to address the FreeBSD-SA-15:10.openssl
629 security advisory includes a change which rejects handshakes
630 with DH parameters below 768 bits. sendmail releases prior
631 to 8.15.2 (not yet released), defaulted to a 512 bit
632 DH parameter setting for client connections. To work around
633 this interoperability, sendmail can be configured to use a
634 2048 bit DH parameter by:
636 1. Edit /etc/mail/`hostname`.mc
637 2. If a setting for confDH_PARAMETERS does not exist or
638 exists and is set to a string beginning with '5',
640 3. If a setting for confDH_PARAMETERS exists and is set to
641 a file path, create a new file with:
642 openssl dhparam -out /path/to/file 2048
643 4. Rebuild the .cf file:
644 cd /etc/mail/; make; make install
646 cd /etc/mail/; make restart
648 A sendmail patch is coming, at which time this file will be
652 Generation of legacy formatted entries have been disabled by default
653 in pwd_mkdb(8), as all base system consumers of the legacy formatted
654 entries were converted to use the new format by default when the new,
655 machine independent format have been added and supported since FreeBSD
658 Please see the pwd_mkdb(8) manual page for further details.
661 Clang and llvm have been upgraded to 3.6.1 release. Please see the
662 20141231 entry below for information about prerequisites and upgrading,
663 if you are not already using 3.5.0 or higher.
666 TI platform code switched to using vendor DTS files and this update
667 may break existing systems running on Beaglebone, Beaglebone Black,
670 - dtb files should be regenerated/reinstalled. Filenames are the
671 same but content is different now
672 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
673 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
674 addressing scheme is now pin 25 on /dev/gpioc3.
675 - Pandaboard: /etc/ttys should be updated, serial console device is
676 now /dev/ttyu2, not /dev/ttyu0
679 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
680 If you need the GNU extension from groff soelim(1), install groff
681 from package: pkg install groff, or via ports: textproc/groff.
684 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
685 defined in symlink(7); previously symlinks were silently ignored.
688 The const qualifier has been removed from iconv(3) to comply with
689 POSIX. The ports tree is aware of this from r384038 onwards.
692 Libraries specified by LIBADD in Makefiles must have a corresponding
693 DPADD_<lib> variable to ensure correct dependencies. This is now
694 enforced in src.libnames.mk.
697 From legacy ata(4) driver was removed support for SATA controllers
698 supported by more functional drivers ahci(4), siis(4) and mvs(4).
699 Kernel modules ataahci and ataadaptec were removed completely,
700 replaced by ahci and mvs modules respectively.
703 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
704 the 20141231 entry below for information about prerequisites and
705 upgrading, if you are not already using 3.5.0 or higher.
708 The 32-bit PowerPC kernel has been changed to a position-independent
709 executable. This can only be booted with a version of loader(8)
710 newer than January 31, 2015, so make sure to update both world and
711 kernel before rebooting.
714 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
715 but before r278950, the RNG was not seeded properly. Immediately
716 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
717 ssh keys or openssl keys) that were generated w/ a kernel from that
718 range. This does not affect programs that directly used /dev/random
719 or /dev/urandom. All userland uses of arc4random(3) are affected.
722 The autofs(4) ABI was changed in order to restore binary compatibility
723 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
727 The powerpc64 kernel has been changed to a position-independent
728 executable. This can only be booted with a new version of loader(8),
729 so make sure to update both world and kernel before rebooting.
732 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
733 only release, no new features have been added. Please see the 20141231
734 entry below for information about prerequisites and upgrading, if you
735 are not already using 3.5.0.
738 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
739 taken from the ELF Tool Chain project rather than GNU binutils. They
740 should be drop-in replacements, with the addition of arm64 support.
741 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
742 binutils tools, if necessary. See 20150805 for updated information.
745 The default Unbound configuration now enables remote control
746 using a local socket. Users who have already enabled the
747 local_unbound service should regenerate their configuration
748 by running "service local_unbound setup" as root.
751 The GNU texinfo and GNU info pages have been removed.
752 To be able to view GNU info pages please install texinfo from ports.
755 Clang, llvm and lldb have been upgraded to 3.5.0 release.
757 As of this release, a prerequisite for building clang, llvm and lldb is
758 a C++11 capable compiler and C++11 standard library. This means that to
759 be able to successfully build the cross-tools stage of buildworld, with
760 clang as the bootstrap compiler, your system compiler or cross compiler
761 should either be clang 3.3 or later, or gcc 4.8 or later, and your
762 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
765 On any standard FreeBSD 10.x or 11.x installation, where clang and
766 libc++ are on by default (that is, on x86 or arm), this should work out
769 On 9.x installations where clang is enabled by default, e.g. on x86 and
770 powerpc, libc++ will not be enabled by default, so libc++ should be
771 built (with clang) and installed first. If both clang and libc++ are
772 missing, build clang first, then use it to build libc++.
774 On 8.x and earlier installations, upgrade to 9.x first, and then follow
775 the instructions for 9.x above.
777 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
778 default, and do not build clang.
780 Many embedded systems are resource constrained, and will not be able to
781 build clang in a reasonable time, or in some cases at all. In those
782 cases, cross building bootable systems on amd64 is a workaround.
784 This new version of clang introduces a number of new warnings, of which
785 the following are most likely to appear:
789 This warns in two cases, for both C and C++:
790 * When the code is trying to take the absolute value of an unsigned
791 quantity, which is effectively a no-op, and almost never what was
792 intended. The code should be fixed, if at all possible. If you are
793 sure that the unsigned quantity can be safely cast to signed, without
794 loss of information or undefined behavior, you can add an explicit
795 cast, or disable the warning.
797 * When the code is trying to take an absolute value, but the called
798 abs() variant is for the wrong type, which can lead to truncation.
799 If you want to disable the warning instead of fixing the code, please
800 make sure that truncation will not occur, or it might lead to unwanted
803 -Wtautological-undefined-compare and
804 -Wundefined-bool-conversion
806 These warn when C++ code is trying to compare 'this' against NULL, while
807 'this' should never be NULL in well-defined C++ code. However, there is
808 some legacy (pre C++11) code out there, which actively abuses this
809 feature, which was less strictly defined in previous C++ versions.
811 Squid and openjdk do this, for example. The warning can be turned off
812 for C++98 and earlier, but compiling the code in C++11 mode might result
813 in unexpected behavior; for example, the parts of the program that are
814 unreachable could be optimized away.
817 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
818 kernel sources have been removed. The .h files remain, since some
819 utilities include them. This will need to be fixed later.
820 If "mount -t oldnfs ..." is attempted, it will fail.
821 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
822 the utilities will report errors.
825 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
826 directories to top level SUBDIR variable when their parent
827 directory is included in LOCAL_DIRS. Users with build systems with
828 such hierarchies and without SUBDIR entries in the parent
829 directory Makefiles should add them or add the directories to
833 faith(4) and faithd(8) have been removed from the base system. Faith
834 has been obsolete for a very long time.
837 vt(4), the new console driver, is enabled by default. It brings
838 support for Unicode and double-width characters, as well as
839 support for UEFI and integration with the KMS kernel video
842 You may need to update your console settings in /etc/rc.conf,
843 most probably the keymap. During boot, /etc/rc.d/syscons will
844 indicate what you need to do.
846 vt(4) still has issues and lacks some features compared to
847 syscons(4). See the wiki for up-to-date information:
848 https://wiki.freebsd.org/Newcons
850 If you want to keep using syscons(4), you can do so by adding
851 the following line to /boot/loader.conf:
855 pjdfstest has been integrated into kyua as an opt-in test suite.
856 Please see share/doc/pjdfstest/README for more details on how to
860 gperf has been removed from the base system for architectures
861 that use clang. Ports that require gperf will obtain it from the
865 pjdfstest has been moved from tools/regression/pjdfstest to
869 At svn r271982, The default linux compat kernel ABI has been adjusted
870 to 2.6.18 in support of the linux-c6 compat ports infrastructure
871 update. If you wish to continue using the linux-f10 compat ports,
872 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
873 encouraged to update their linux-compat packages to linux-c6 during
874 their next update cycle.
877 The ofwfb driver, used to provide a graphics console on PowerPC when
878 using vt(4), no longer allows mmap() of all physical memory. This
879 will prevent Xorg on PowerPC with some ATI graphics cards from
880 initializing properly unless x11-servers/xorg-server is updated to
884 The xdev targets have been converted to using TARGET and
885 TARGET_ARCH instead of XDEV and XDEV_ARCH.
888 The default unbound configuration has been modified to address
889 issues with reverse lookups on networks that use private
890 address ranges. If you use the local_unbound service, run
891 "service local_unbound setup" as root to regenerate your
892 configuration, then "service local_unbound reload" to load the
896 The GNU texinfo and GNU info pages are not built and installed
897 anymore, WITH_INFO knob has been added to allow to built and install
899 UPDATE: see 20150102 entry on texinfo's removal
902 The GNU readline library is now an INTERNALLIB - that is, it is
903 statically linked into consumers (GDB and variants) in the base
904 system, and the shared library is no longer installed. The
905 devel/readline port is available for third party software that
909 The Itanium architecture (ia64) has been removed from the list of
910 known architectures. This is the first step in the removal of the
914 Commit r268115 has added NFSv4.1 server support, merged from
915 projects/nfsv4.1-server. Since this includes changes to the
916 internal interfaces between the NFS related modules, a full
917 build of the kernel and modules will be necessary.
918 __FreeBSD_version has been bumped.
921 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
922 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
923 which differs from the behaviour controlled by this knob.)
926 Maximal length of the serial number in CTL was increased from 16 to
927 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
928 and ctld, need to be rebuilt to work with a new kernel.
931 The libatf-c and libatf-c++ major versions were downgraded to 0 and
932 1 respectively to match the upstream numbers. They were out of
933 sync because, when they were originally added to FreeBSD, the
934 upstream versions were not respected. These libraries are private
935 and not yet built by default, so renumbering them should be a
936 non-issue. However, unclean source trees will yield broken test
937 programs once the operator executes "make delete-old-libs" after a
940 Additionally, the atf-sh binary was made private by moving it into
941 /usr/libexec/. Already-built shell test programs will keep the
942 path to the old binary so they will break after "make delete-old"
945 If you are using WITH_TESTS=yes (not the default), wipe the object
946 tree and rebuild from scratch to prevent spurious test failures.
947 This is only needed once: the misnumbered libraries and misplaced
948 binaries have been added to OptionalObsoleteFiles.inc so they will
949 be removed during a clean upgrade.
952 Clang and llvm have been upgraded to 3.4.1 release.
955 We bogusly installed src.opts.mk in /usr/share/mk. This file should
956 be removed to avoid issues in the future (and has been added to
960 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
961 past, it affected all builds that used the bsd.*.mk files. The old
962 behavior was a bug, but people may have relied upon it. To get this
963 behavior back, you can .include /etc/src.conf from /etc/make.conf
964 (which is still global and isn't changed). This also changes the
965 behavior of incremental builds inside the tree of individual
966 directories. Set MAKESYSPATH to ".../share/mk" to do that.
967 Although this has survived make universe and some upgrade scenarios,
968 other upgrade scenarios may have broken. At least one form of
969 temporary breakage was fixed with MAKESYSPATH settings for buildworld
970 as well... In cases where MAKESYSPATH isn't working with this
971 setting, you'll need to set it to the full path to your tree.
973 One side effect of all this cleaning up is that bsd.compiler.mk
974 is no longer implicitly included by bsd.own.mk. If you wish to
975 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
979 The lindev device has been removed since /dev/full has been made a
980 standard device. __FreeBSD_version has been bumped.
983 The knob WITHOUT_VI was added to the base system, which controls
984 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
985 in order to reorder files share/termcap and didn't build ex(1) as a
986 build tool, so building/installing with WITH_VI is highly advised for
987 build hosts for older releases.
989 This issue has been fixed in stable/9 and stable/10 in r277022 and
990 r276991, respectively.
993 The YES_HESIOD knob has been removed. It has been obsolete for
994 a decade. Please move to using WITH_HESIOD instead or your builds
995 will silently lack HESIOD.
998 The uart(4) driver has been changed with respect to its handling
999 of the low-level console. Previously the uart(4) driver prevented
1000 any process from changing the baudrate or the CLOCAL and HUPCL
1001 control flags. By removing the restrictions, operators can make
1002 changes to the serial console port without having to reboot.
1003 However, when getty(8) is started on the serial device that is
1004 associated with the low-level console, a misconfigured terminal
1005 line in /etc/ttys will now have a real impact.
1006 Before upgrading the kernel, make sure that /etc/ttys has the
1007 serial console device configured as 3wire without baudrate to
1008 preserve the previous behaviour. E.g:
1009 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1012 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1013 to improve performance. To re-enable it, if needed, run rpcbind
1014 with command line option -W.
1017 Switched back to the GPL dtc compiler due to updates in the upstream
1018 dts files not being supported by the BSDL dtc compiler. You will need
1019 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1020 may result while building dtb files during a kernel build if you fail
1021 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1024 Clang and llvm have been upgraded to 3.4 release.
1027 The nve(4) driver has been removed. Please use the nfe(4) driver
1028 for NVIDIA nForce MCP Ethernet adapters instead.
1031 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1032 This could cause certain C++ applications using shared libraries built
1033 against the previous version of libc++ to crash. The incompatibility
1034 has now been fixed, but any C++ applications or shared libraries built
1035 between r261283 and r261801 should be recompiled.
1038 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1039 capability mode support. Please note that enabling the feature in
1040 kernel is still highly recommended.
1043 OpenSSH is now built with sandbox support, and will use sandbox as
1044 the default privilege separation method. This requires Capsicum
1045 capability mode support in kernel.
1048 The libelf and libdwarf libraries have been updated to newer
1049 versions from upstream. Shared library version numbers for
1050 these two libraries were bumped. Any ports or binaries
1051 requiring these two libraries should be recompiled.
1052 __FreeBSD_version is bumped to 1100006.
1055 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1056 instead of providing an explicit one, this would prevent such
1057 Makefile from providing its own Kyuafile in the future during
1058 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1059 intervention is needed to clean an objdir if you use NO_CLEAN:
1060 # find /usr/obj -name Kyuafile | xargs rm -f
1063 The behavior of gss_pseudo_random() for the krb5 mechanism
1064 has changed, for applications requesting a longer random string
1065 than produced by the underlying enctype's pseudo-random() function.
1066 In particular, the random string produced from a session key of
1067 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1068 be different at the 17th octet and later, after this change.
1069 The counter used in the PRF+ construction is now encoded as a
1070 big-endian integer in accordance with RFC 4402.
1071 __FreeBSD_version is bumped to 1100004.
1074 The WITHOUT_ATF build knob has been removed and its functionality
1075 has been subsumed into the more generic WITHOUT_TESTS. If you were
1076 using the former to disable the build of the ATF libraries, you
1077 should change your settings to use the latter.
1080 The default version of mtree is nmtree which is obtained from
1081 NetBSD. The output is generally the same, but may vary
1082 slightly. If you found you need identical output adding
1083 "-F freebsd9" to the command line should do the trick. For the
1084 time being, the old mtree is available as fmtree.
1087 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1088 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1089 1.1.4_8 and verify bsdyml not linked in, before running "make
1091 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1093 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1096 The stable/10 branch has been created in subversion from head
1100 The rc.d/jail script has been updated to support jail(8)
1101 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1102 for per-jail configuration are automatically converted to
1103 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1104 This is transparently backward compatible. See below about some
1105 incompatibilities and rc.conf(5) manual page for more details.
1107 These variables are now deprecated in favor of jail(8) configuration
1108 file. One can use "rc.d/jail config <jname>" command to generate
1109 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1110 running the jail(8) utility. The default pathname of the
1111 configuration file is /etc/jail.conf and can be specified by
1112 using $jail_conf or $jail_<jname>_conf variables.
1114 Please note that jail_devfs_ruleset accepts an integer at
1115 this moment. Please consider to rewrite the ruleset name
1119 BIND has been removed from the base system. If all you need
1120 is a local resolver, simply enable and start the local_unbound
1121 service instead. Otherwise, several versions of BIND are
1122 available in the ports tree. The dns/bind99 port is one example.
1124 With this change, nslookup(1) and dig(1) are no longer in the base
1125 system. Users should instead use host(1) and drill(1) which are
1126 in the base system. Alternatively, nslookup and dig can
1127 be obtained by installing the dns/bind-tools port.
1130 With the addition of unbound(8), a new unbound user is now
1131 required during installworld. "mergemaster -p" can be used to
1132 add the user prior to installworld, as documented in the handbook.
1135 OpenSSH is now built with DNSSEC support, and will by default
1136 silently trust signed SSHFP records. This can be controlled with
1137 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1138 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1141 The GNU Compiler Collection and C++ standard library (libstdc++)
1142 are no longer built by default on platforms where clang is the system
1143 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1144 options in src.conf.
1147 The PROCDESC kernel option is now part of the GENERIC kernel
1148 configuration and is required for the rwhod(8) to work.
1149 If you are using custom kernel configuration, you should include
1153 The API and ABI related to the Capsicum framework was modified
1154 in backward incompatible way. The userland libraries and programs
1155 have to be recompiled to work with the new kernel. This includes the
1156 following libraries and programs, but the whole buildworld is
1157 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1158 kdump, procstat, rwho, rwhod, uniq.
1161 AES-NI intrinsic support has been added to gcc. The AES-NI module
1162 has been updated to use this support. A new gcc is required to build
1163 the aesni module on both i386 and amd64.
1166 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1167 Thus "device padlock_rng" and "device rdrand_rng" should be
1168 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1171 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1172 enables just the iconv* functionality and is now on by default.
1173 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1174 compatibility. Set WITHOUT_ICONV to build the old way.
1175 If you have been using WITH_ICONV before, you will very likely
1176 need to turn on WITH_LIBICONV_COMPAT.
1179 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1180 Illumos origin, including ZFS. If you have INVARIANTS in your
1181 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1183 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1184 locks if WITNESS option was set. Because that generated a lot of
1185 witness(9) reports and all of them were believed to be false
1186 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1187 can be used to achieve the previous behavior.
1190 Timer values in IPv6 data structures now use time_uptime instead
1191 of time_second. Although this is not a user-visible functional
1192 change, userland utilities which directly use them---ndp(8),
1193 rtadvd(8), and rtsold(8) in the base system---need to be updated
1194 to r253970 or later.
1197 find -delete can now delete the pathnames given as arguments,
1198 instead of only files found below them or if the pathname did
1199 not contain any slashes. Formerly, the following error message
1202 find: -delete: <path>: relative path potentially not safe
1204 Deleting the pathnames given as arguments can be prevented
1205 without error messages using -mindepth 1 or by changing
1206 directory and passing "." as argument to find. This works in the
1207 old as well as the new version of find.
1210 Behavior of devfs rules path matching has been changed.
1211 Pattern is now always matched against fully qualified devfs
1212 path and slash characters must be explicitly matched by
1213 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1214 subdirectories must be reviewed.
1217 The default ARM ABI has changed to the ARM EABI. The old ABI is
1218 incompatible with the ARM EABI and all programs and modules will
1219 need to be rebuilt to work with a new kernel.
1221 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1223 NOTE: Support for the old ABI will be removed in the future and
1224 users are advised to upgrade.
1227 pkg_install has been disconnected from the build if you really need it
1228 you should add WITH_PKGTOOLS in your src.conf(5).
1231 Most of network statistics structures were changed to be able
1232 keep 64-bits counters. Thus all tools, that work with networking
1233 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1236 Fix a bug that allowed a tracing process (e.g. gdb) to write
1237 to a memory-mapped file in the traced process's address space
1238 even if neither the traced process nor the tracing process had
1239 write access to that file.
1242 CVS has been removed from the base system. An exact copy
1243 of the code is available from the devel/cvs port.
1246 Some people report the following error after the switch to bmake:
1248 make: illegal option -- J
1249 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1251 *** [buildworld] Error code 2
1253 this likely due to an old instance of make in
1254 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1255 which src/Makefile will use that blindly, if it exists, so if
1256 you see the above error:
1258 rm -rf `make -V MAKEPATH`
1263 Use bmake by default.
1264 Whereas before one could choose to build with bmake via
1265 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1266 make. The goal is to remove these knobs for 10-RELEASE.
1268 It is worth noting that bmake (like gmake) treats the command
1269 line as the unit of failure, rather than statements within the
1270 command line. Thus '(cd some/where && dosomething)' is safer
1271 than 'cd some/where; dosomething'. The '()' allows consistent
1272 behavior in parallel build.
1275 Fix a bug that allows NFS clients to issue READDIR on files.
1278 The WITHOUT_IDEA option has been removed because
1279 the IDEA patent expired.
1282 The sysctl which controls TRIM support under ZFS has been renamed
1283 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1287 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1288 rather than creating it's own in the temporary directory in
1289 order allow access to bootstrapped versions of tools such as
1290 install and mtree. When upgrading from version of FreeBSD where
1291 the install command does not support -l, you will need to
1292 install a new mergemaster command if mergemaster -p is required.
1293 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1297 Legacy ATA stack, disabled and replaced by new CAM-based one since
1298 FreeBSD 9.0, completely removed from the sources. Kernel modules
1299 atadisk and atapi*, user-level tools atacontrol and burncd are
1300 removed. Kernel option `options ATA_CAM` is now permanently enabled
1304 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1305 and socketpair(2). Software, in particular Kerberos, may
1306 automatically detect and use these during building. The resulting
1307 binaries will not work on older kernels.
1310 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1311 information, see the respective 20130304 entry).
1314 Recent commits to callout(9) changed the size of struct callout,
1315 so the KBI is probably heavily disturbed. Also, some functions
1316 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1317 by macros. Every kernel module using it won't load, so rebuild
1320 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1321 but does not initialize by default (because of the new CTL_DISABLE
1322 option) to save memory. To re-enable it, remove the CTL_DISABLE
1323 option from the kernel config file or set kern.cam.ctl.disable=0
1324 in /boot/loader.conf.
1327 The ctl device has been disabled in GENERIC for i386 and amd64.
1328 This was done due to the extra memory being allocated at system
1329 initialisation time by the ctl driver which was only used if
1330 a CAM target device was created. This makes a FreeBSD system
1331 unusable on 128MB or less of RAM.
1334 A new compression method (lz4) has been merged to -HEAD. Please
1335 refer to zpool-features(7) for more information.
1337 Please refer to the "ZFS notes" section of this file for information
1338 on upgrading boot ZFS pools.
1341 A BSD-licensed patch(1) variant has been added and is installed
1342 as bsdpatch, being the GNU version the default patch.
1343 To inverse the logic and use the BSD-licensed one as default,
1344 while having the GNU version installed as gnupatch, rebuild
1345 and install world with the WITH_BSD_PATCH knob set.
1348 Due to the use of the new -l option to install(1) during build
1349 and install, you must take care not to directly set the INSTALL
1350 make variable in your /etc/make.conf, /etc/src.conf, or on the
1351 command line. If you wish to use the -C flag for all installs
1352 you may be able to add INSTALL+=-C to /etc/make.conf or
1356 The install(1) option -M has changed meaning and now takes an
1357 argument that is a file or path to append logs to. In the
1358 unlikely event that -M was the last option on the command line
1359 and the command line contained at least two files and a target
1360 directory the first file will have logs appended to it. The -M
1361 option served little practical purpose in the last decade so its
1362 use is expected to be extremely rare.
1365 After switching to Clang as the default compiler some users of ZFS
1366 on i386 systems started to experience stack overflow kernel panics.
1367 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1370 GEOM_LABEL now mangles label names read from file system metadata.
1371 Mangling affect labels containing spaces, non-printable characters,
1372 '%' or '"'. Device names in /etc/fstab and other places may need to
1376 By default, only the 10 most recent kernel dumps will be saved. To
1377 restore the previous behaviour (no limit on the number of kernel dumps
1378 stored in the dump directory) add the following line to /etc/rc.conf:
1383 With the addition of auditdistd(8), a new auditdistd user is now
1384 required during installworld. "mergemaster -p" can be used to
1385 add the user prior to installworld, as documented in the handbook.
1388 The sin6_scope_id member variable in struct sockaddr_in6 is now
1389 filled by the kernel before passing the structure to the userland via
1390 sysctl or routing socket. This means the KAME-specific embedded scope
1391 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1392 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1393 __FreeBSD_version is bumped to 1000025.
1396 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1397 This means that the world and kernel will be compiled with clang
1398 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1399 and /usr/bin/cpp. To disable this behavior and revert to building
1400 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1401 of current may need to bootstrap WITHOUT_CLANG first if the clang
1402 build fails (its compatibility window doesn't extend to the 9 stable
1406 The IPFIREWALL_FORWARD kernel option has been removed. Its
1407 functionality now turned on by default.
1410 The ZERO_COPY_SOCKET kernel option has been removed and
1411 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1412 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1413 mechanism which is not safe and may result in kernel crashes.
1414 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1415 driver supports disposeable external page sized mbuf storage.
1416 Proper replacements for both zero-copy mechanisms are under
1417 consideration and will eventually lead to complete removal
1418 of the two kernel options.
1421 The IPv4 network stack has been converted to network byte
1422 order. The following modules need to be recompiled together
1423 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1424 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1427 Support for non-MPSAFE filesystems was removed from VFS. The
1428 VFS_VERSION was bumped, all filesystem modules shall be
1432 All the non-MPSAFE filesystems have been disconnected from
1433 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1434 portalfs, smbfs, xfs.
1437 The interface cloning API and ABI has changed. The following
1438 modules need to be recompiled together with kernel:
1439 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1440 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1441 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1444 The sdhci driver was split in two parts: sdhci (generic SD Host
1445 Controller logic) and sdhci_pci (actual hardware driver).
1446 No kernel config modifications are required, but if you
1447 load sdhc as a module you must switch to sdhci_pci instead.
1450 Import the FUSE kernel and userland support into base system.
1453 The GNU sort(1) program has been removed since the BSD-licensed
1454 sort(1) has been the default for quite some time and no serious
1455 problems have been reported. The corresponding WITH_GNU_SORT
1459 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1460 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1464 The net80211(4) ABI has been changed to allow for improved driver
1465 PS-POLL and power-save support. All wireless drivers need to be
1466 recompiled to work with the new kernel.
1469 The random(4) support for the VIA hardware random number
1470 generator (`PADLOCK') is no longer enabled unconditionally.
1471 Add the padlock_rng device in the custom kernel config if
1472 needed. The GENERIC kernels on i386 and amd64 do include the
1473 device, so the change only affects the custom kernel
1477 The pf(4) packet filter ABI has been changed. pfctl(8) and
1478 snmp_pf module need to be recompiled to work with new kernel.
1481 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1482 to -HEAD. Pools that have empty_bpobj in active state can not be
1483 imported read-write with ZFS implementations that do not support
1484 this feature. For more information read the zpool-features(5)
1488 The sparc64 ZFS loader has been changed to no longer try to auto-
1489 detect ZFS providers based on diskN aliases but now requires these
1490 to be explicitly listed in the OFW boot-device environment variable.
1493 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1494 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1495 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1498 The following sysctls and tunables have been renamed for consistency
1499 with other variables:
1500 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1501 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1504 The sort utility has been replaced with BSD sort. For now, GNU sort
1505 is also available as "gnusort" or the default can be set back to
1506 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1507 installed as "bsdsort".
1510 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1511 Starting with this version the old system of ZFS pool versioning
1512 is superseded by "feature flags". This concept enables forward
1513 compatibility against certain future changes in functionality of ZFS
1514 pools. The first read-only compatible "feature flag" for ZFS pools
1515 is named "com.delphix:async_destroy". For more information
1516 read the new zpool-features(5) manual page.
1517 Please refer to the "ZFS notes" section of this file for information
1518 on upgrading boot ZFS pools.
1521 The malloc(3) implementation embedded in libc now uses sources imported
1522 as contrib/jemalloc. The most disruptive API change is to
1523 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1524 delete it prior to installworld, and optionally re-create it using the
1525 new format after rebooting. See malloc.conf(5) for details
1526 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1530 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1531 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1532 now spelled mips. This is to aid compatibility with third-party
1533 software that expects this naming scheme in uname(3). Little-endian
1534 settings are unchanged. If you are updating a big-endian mips64 machine
1535 from before this change, you may need to set MACHINE_ARCH=mips64 in
1536 your environment before the new build system will recognize your machine.
1539 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1543 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1544 nullfs(5) did not pass through all behaviours to the underlying layer,
1545 as a result if we bound to a socket on the lower layer we could connect
1546 only to the lower path; if we bound to the upper layer we could connect
1547 only to the upper path. The new behavior is one can connect to both the
1548 lower and the upper paths regardless what layer path one binds to.
1551 The getifaddrs upgrade path broken with 20111215 has been restored.
1552 If you have upgraded in between 20111215 and 20120209 you need to
1553 recompile libc again with your kernel. You still need to recompile
1554 world to be able to configure CARP but this restriction already
1555 comes from 20111215.
1558 The set_rcvar() function has been removed from /etc/rc.subr. All
1559 base and ports rc.d scripts have been updated, so if you have a
1560 port installed with a script in /usr/local/etc/rc.d you can either
1561 hand-edit the rcvar= line, or reinstall the port.
1563 An easy way to handle the mass-update of /etc/rc.d:
1564 rm /etc/rc.d/* && mergemaster -i
1567 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1568 on the current CPU and prevents other threads from running.
1569 This behavior can be reverted using the kern.stop_scheduler_on_panic
1571 The new behavior can be incompatible with kern.sync_on_panic.
1574 The carp(4) facility has been changed significantly. Configuration
1575 of the CARP protocol via ifconfig(8) has changed, as well as format
1576 of CARP events submitted to devd(8) has changed. See manual pages
1577 for more information. The arpbalance feature of carp(4) is currently
1578 not supported anymore.
1580 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1581 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1582 need to be recompiled.
1585 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1589 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1590 explicitely support non-MPSAFE filesystems.
1591 It is on by default for all supported platform at this present
1595 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1596 i386 and pc98 GENERIC kernel configuration files.
1599 sysinstall has been removed
1602 The stable/9 branch created in subversion. This corresponds to the
1603 RELENG_9 branch in CVS.
1609 Avoid using make -j when upgrading. While generally safe, there are
1610 sometimes problems using -j to upgrade. If your upgrade fails with
1611 -j, please try again without -j. From time to time in the past there
1612 have been problems using -j with buildworld and/or installworld. This
1613 is especially true when upgrading between "distant" versions (eg one
1614 that cross a major release boundary or several minor releases, or when
1615 several months have passed on the -current branch).
1617 Sometimes, obscure build problems are the result of environment
1618 poisoning. This can happen because the make utility reads its
1619 environment when searching for values for global variables. To run
1620 your build attempts in an "environmental clean room", prefix all make
1621 commands with 'env -i '. See the env(1) manual page for more details.
1623 When upgrading from one major version to another it is generally best
1624 to upgrade to the latest code in the currently installed branch first,
1625 then do an upgrade to the new branch. This is the best-tested upgrade
1626 path, and has the highest probability of being successful. Please try
1627 this approach before reporting problems with a major version upgrade.
1629 When upgrading a live system, having a root shell around before
1630 installing anything can help undo problems. Not having a root shell
1631 around can lead to problems if pam has changed too much from your
1632 starting point to allow continued authentication after the upgrade.
1634 This file should be read as a log of events. When a later event changes
1635 information of a prior event, the prior event should not be deleted.
1636 Instead, a pointer to the entry with the new information should be
1637 placed in the old entry. Readers of this file should also sanity check
1638 older entries before relying on them blindly. Authors of new entries
1639 should write them with this in mind.
1643 When upgrading the boot ZFS pool to a new version, always follow
1646 1.) recompile and reinstall the ZFS boot loader and boot block
1647 (this is part of "make buildworld" and "make installworld")
1649 2.) update the ZFS boot block on your boot drive
1651 The following example updates the ZFS boot block on the first
1652 partition (freebsd-boot) of a GPT partitioned drive ada0:
1653 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1655 Non-boot pools do not need these updates.
1659 If you are updating from a prior version of FreeBSD (even one just
1660 a few days old), you should follow this procedure. It is the most
1661 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1663 make kernel-toolchain
1664 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1665 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1667 To test a kernel once
1668 ---------------------
1669 If you just want to boot a kernel once (because you are not sure
1670 if it works, or if you want to boot a known bad kernel to provide
1671 debugging information) run
1672 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1673 nextboot -k testkernel
1675 To just build a kernel when you know that it won't mess you up
1676 --------------------------------------------------------------
1677 This assumes you are already running a CURRENT system. Replace
1678 ${arch} with the architecture of your machine (e.g. "i386",
1679 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1681 cd src/sys/${arch}/conf
1682 config KERNEL_NAME_HERE
1683 cd ../compile/KERNEL_NAME_HERE
1688 If this fails, go to the "To build a kernel" section.
1690 To rebuild everything and install it on the current system.
1691 -----------------------------------------------------------
1692 # Note: sometimes if you are running current you gotta do more than
1693 # is listed here if you are upgrading from a really old current.
1695 <make sure you have good level 0 dumps>
1697 make kernel KERNCONF=YOUR_KERNEL_HERE
1699 <reboot in single user> [3]
1706 To cross-install current onto a separate partition
1707 --------------------------------------------------
1708 # In this approach we use a separate partition to hold
1709 # current's root, 'usr', and 'var' directories. A partition
1710 # holding "/", "/usr" and "/var" should be about 2GB in
1713 <make sure you have good level 0 dumps>
1716 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1717 <maybe newfs current's root partition>
1718 <mount current's root partition on directory ${CURRENT_ROOT}>
1719 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1720 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1721 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1722 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1723 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1724 <reboot into current>
1725 <do a "native" rebuild/install as described in the previous section>
1726 <maybe install compatibility libraries from ports/misc/compat*>
1730 To upgrade in-place from stable to current
1731 ----------------------------------------------
1732 <make sure you have good level 0 dumps>
1734 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1736 <reboot in single user> [3]
1743 Make sure that you've read the UPDATING file to understand the
1744 tweaks to various things you need. At this point in the life
1745 cycle of current, things change often and you are on your own
1746 to cope. The defaults can also change, so please read ALL of
1747 the UPDATING entries.
1749 Also, if you are tracking -current, you must be subscribed to
1750 freebsd-current@freebsd.org. Make sure that before you update
1751 your sources that you have read and understood all the recent
1752 messages there. If in doubt, please track -stable which has
1753 much fewer pitfalls.
1755 [1] If you have third party modules, such as vmware, you
1756 should disable them at this point so they don't crash your
1759 [3] From the bootblocks, boot -s, and then do
1764 adjkerntz -i # if CMOS is wall time
1765 Also, when doing a major release upgrade, it is required that
1766 you boot into single user mode to do the installworld.
1768 [4] Note: This step is non-optional. Failure to do this step
1769 can result in a significant reduction in the functionality of the
1770 system. Attempting to do it by hand is not recommended and those
1771 that pursue this avenue should read this file carefully, as well
1772 as the archives of freebsd-current and freebsd-hackers mailing lists
1773 for potential gotchas. The -U option is also useful to consider.
1774 See mergemaster(8) for more information.
1776 [5] Usually this step is a noop. However, from time to time
1777 you may need to do this if you get unknown user in the following
1778 step. It never hurts to do it all the time. You may need to
1779 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1780 install) after the buildworld before this step if you last updated
1781 from current before 20130425 or from -stable before 20130430.
1783 [6] This only deletes old files and directories. Old libraries
1784 can be deleted by "make delete-old-libs", but you have to make
1785 sure that no program is using those libraries anymore.
1787 [8] In order to have a kernel that can run the 4.x binaries needed to
1788 do an installworld, you must include the COMPAT_FREEBSD4 option in
1789 your kernel. Failure to do so may leave you with a system that is
1790 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1791 required to run the 5.x binaries on more recent kernels. And so on
1792 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1794 Make sure that you merge any new devices from GENERIC since the
1795 last time you updated your kernel config file.
1797 [9] When checking out sources, you must include the -P flag to have
1798 cvs prune empty directories.
1800 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1801 "?=" instead of the "=" assignment operator, so that buildworld can
1802 override the CPUTYPE if it needs to.
1804 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1805 not on the command line, or in /etc/make.conf. buildworld will
1806 warn if it is improperly defined.
1809 This file contains a list, in reverse chronological order, of major
1810 breakages in tracking -current. It is not guaranteed to be a complete
1811 list of such breakages, and only contains entries since September 23, 2011.
1812 If you need to see UPDATING entries from before that date, you will need
1813 to fetch an UPDATING file from an older FreeBSD release.
1815 Copyright information:
1817 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1819 Redistribution, publication, translation and use, with or without
1820 modification, in full or in part, in any form or format of this
1821 document are permitted without further permission from the author.
1823 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1824 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1825 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1826 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1827 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1828 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1829 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1830 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1831 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1832 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1833 POSSIBILITY OF SUCH DAMAGE.
1835 Contact Warner Losh if you have any questions about your use of