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 CARP now sets DSCP value CS7(Network Traffic) in the flowlabel field
21 of packets by default instead of only setting TOS_LOWDELAY in IPv4,
22 which was deprecated in 1998. Original behavior can be restored by
23 setting sysctl net.inet.carp.dscp=4.
26 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
27 8.0.0. Please see the 20141231 entry below for information about
28 prerequisites and upgrading, if you are not already using clang 3.5.0
32 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
33 compiled into your custom kernel, add 'device xz' statement to the
37 Co-existance for Forth and Lua interpreters in bootloaders has now been
38 merged to ease testing of lualoader. LOADER_DEFAULT_INTERP, documented
39 in build(7), may be used to control which interpreter flavor is used in
40 the default loader to be installed. For systems where Lua and Forth
41 coexist, this switch can also be made on a running system by creating a
42 link from /boot/loader{,.efi} to /boot/loader_${flavor}{,.efi} rather
43 than requiring a rebuild.
45 The default flavor in this branch will remain Forth. As indicated in
46 the 20190216 UPDATING entry, booting is a complex environment; it would
47 be prudent to assume that lualoader may not work for your setup and make
48 provisions for backup boot methods.
51 zfsloader's functionality has now been folded into loader.
52 zfsloader is no longer necesasary once you've updated your
53 boot blocks. For a transition period, we will install a
54 hardlink for zfsloader to loader to allow a smooth transition
55 until the boot blocks can be updated (hard link because old
56 zfs boot blocks don't understand symlinks).
59 Lualoader has been merged to facilitate testing on this branch. It's
60 purely opt-in for now by building WITH_LOADER_LUA and WITHOUT_FORTH in
61 /etc/src.conf, but co-existance will come shortly. Booting is a complex
62 environment and test coverage for Lua-enabled loaders has been thin, so
63 it would be prudent to assume it might not work and make provisions for
67 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
68 7.0.1. Please see the 20141231 entry below for information about
69 prerequisites and upgrading, if you are not already using clang 3.5.0
73 r342562 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
74 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
75 servers that have vfs.nfsd.nfs_privport set will only allow mounts
76 from clients using a reserved port#. Since both the FreeBSD and Linux
77 NFSv4 clients use reserved port#s by default, this should not affect
81 The '%I' format in the kern.corefile sysctl limits the number of
82 core files that a process can generate to the number stored in the
83 debug.ncores sysctl. The '%I' format is replaced by the single digit
84 index. Previously, if all indexes were taken the kernel would overwrite
85 only a core file with the highest index in a filename.
86 Currently the system will create a new core file if there is a free
87 index or if all slots are taken it will overwrite the oldest one.
90 WITH_OFED option now only enables the build for the OFED libraries
91 and some fundamental client utilities. OpenSM and rest of the
92 debugging tools are enabled by WITH_OFED_EXTRA build switch.
93 WITH_OFED is turned on by default on amd64.
96 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
97 6.0.1. Please see the 20141231 entry below for information about
98 prerequisites and upgrading, if you are not already using clang 3.5.0
102 The releng/11.2 branch has been created from stable/11@r334458.
105 The tz database (tzdb) has been updated to 2018e. This version more
106 correctly models time stamps in time zones with negative DST such as
107 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
108 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
109 time zone abbreviations and the tm_isdst flag.
112 The use of RSS hash from the network card aka flowid has been
113 disabled by default for lagg(4) as it's currently incompatible with
114 the lacp and loadbalance protocols.
116 This can be re-enabled by setting the following in loader.conf:
117 net.link.lagg.default_use_flowid="1"
120 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
121 6.0.0. Please see the 20141231 entry below for information about
122 prerequisites and upgrading, if you are not already using clang 3.5.0
126 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
127 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
128 to WITH/OUT_LOADER_GELI.
131 The geli password typed at boot is now hidden. To restore the previous
132 behavior, see geli(8) for configuration options.
134 The SW_WATCHDOG option is no longer necessary to enable the
135 hardclock-based software watchdog if no hardware watchdog is
136 configured. As before, SW_WATCHDOG will cause the software
137 watchdog to be enabled even if a hardware watchdog is configured.
140 lint(1) binaries and library are no longer built by default. To
141 enable building them, define WITH_LINT in src.conf. If you are using
142 a FreeBSD 12 or later system to build 11-stable, you may need to
143 install a lint(1) binary to use WITH_LINT.
146 When building multiple kernels using KERNCONF, non-existent KERNCONF
147 files will produce an error and buildkernel will fail. Previously
148 missing KERNCONF files silently failed giving no indication as to
149 why, only to subsequently discover during installkernel that the
150 desired kernel was never built in the first place.
153 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
154 Please see the 20141231 entry below for information about prerequisites
155 and upgrading, if you are not already using clang 3.5.0 or higher.
158 Since the switch to GPT disk labels, fsck for UFS/FFS has been
159 unable to automatically find alternate superblocks. As of r322806,
160 the information needed to find alternate superblocks has been
161 moved to the end of the area reserved for the boot block.
162 Filesystems created with a newfs of this vintage or later
163 will create the recovery information. If you have a filesystem
164 created prior to this change and wish to have a recovery block
165 created for your filesystem, you can do so by running fsck in
166 forground mode (i.e., do not use the -p or -y options). As it
167 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
168 to which you should answer yes.
171 The releng/11.1 branch has been created from stable/11@r320475.
174 arm64 builds now use the base system LLD 4.0.0 linker by default,
175 instead of requiring that the aarch64-binutils port or package be
176 installed. To continue using aarch64-binutils, set
177 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
180 The ctl.ko module no longer implements the iSCSI target frontend:
181 cfiscsi.ko does instead.
183 If building cfiscsi.ko as a kernel module, the module can be loaded
184 via one of the following methods:
185 - `cfiscsi_load="YES"` in loader.conf(5).
186 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
187 - ctladm(8)/ctld(8), when compiled with iSCSI support
188 (`WITH_ISCSI=yes` in src.conf(5))
190 Please see cfiscsi(4) for more details.
193 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
194 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
195 same source (previously, the dependency of mmcsd.ko on mmc.ko was
196 missing, but mmcsd.ko now will refuse to load if it is incompatible
200 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
201 use any explicitly assigned loopback address available in the jail
202 instead of using the first assigned address of the jail.
205 As of r316810 for ipfilter, keep frags is no longer assumed when
206 keep state is specified in a rule. r316810 aligns ipfilter with
207 documentation in man pages separating keep frags from keep state.
208 This allows keep state to specified without forcing keep frags
209 and allows keep frags to be specified independently of keep state.
210 To maintain previous behaviour, also specify keep frags with
211 keep state (as documented in ipf.conf.5).
214 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
215 Please see the 20141231 entry below for information about prerequisites
216 and upgrading, if you are not already using clang 3.5.0 or higher.
219 The code that provides support for ZFS .zfs/ directory functionality
220 has been reimplemented. It's not possible now to create a snapshot
221 by mkdir under .zfs/snapshot/. That should be the only user visible
225 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
226 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
227 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
228 and now NAT-T is supported by default. Security associations now use
229 the single namespace for SPI allocation, so if you use several manually
230 configured security associations with the same SPI, this configuration
234 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
235 Please see the 20141231 entry below for information about prerequisites
236 and upgrading, if you are not already using clang 3.5.0 or higher.
239 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
240 Please see the 20141231 entry below for information about prerequisites
241 and upgrading, if you are not already using clang 3.5.0 or higher.
244 The layout of the pmap structure has changed for powerpc to put the pmap
245 statistics at the front for all CPU variations. libkvm(3) and all tools
246 that link against it need to be recompiled.
249 isl(4) and cyapa(4) drivers now require a new driver,
250 chromebook_platform(4), to work properly on Chromebook-class hardware.
251 On other types of hardware the drivers may need to be configured using
252 device hints. Please see the corresponding manual pages for details.
255 Relocatable object files with the extension of .So have been renamed
256 to use an extension of .pico instead. The purpose of this change is
257 to avoid a name clash with shared libraries on case-insensitive file
258 systems. On those file systems, foo.So is the same file as foo.so.
261 The releng/11.0 branch has been created from stable/11@r303970.
264 The stable/11 branch has been created from head@r302406.
267 The libc stub for the pipe(2) system call has been replaced with
268 a wrapper that calls the pipe2(2) system call and the pipe(2)
269 system call is now only implemented by the kernels that include
270 "options COMPAT_FREEBSD10" in their config file (this is the
271 default). Users should ensure that this option is enabled in
272 their kernel or upgrade userspace to r302092 before upgrading their
276 CAM will now strip leading spaces from SCSI disks' serial numbers.
277 This will effect users who create UFS filesystems on SCSI disks using
278 those disk's diskid device nodes. For example, if /etc/fstab
279 previously contained a line like
280 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
281 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
282 transforms like gmirror may also be affected. ZFS users should
286 The bitstring(3) API has been updated with new functionality and
287 improved performance. But it is binary-incompatible with the old API.
288 Objects built with the new headers may not be linked against objects
289 built with the old headers.
292 The brk and sbrk functions have been removed from libc on arm64.
293 Binutils from ports has been updated to not link to these
294 functions and should be updated to the latest version before
295 installing a new libc.
298 The armv6 port now defaults to hard float ABI. Limited support
299 for running both hardfloat and soft float on the same system
300 is available using the libraries installed with -DWITH_LIBSOFT.
301 This has only been tested as an upgrade path for installworld
302 and packages may fail or need manual intervention to run. New
303 packages will be needed.
305 To update an existing self-hosted armv6hf system, you must add
306 TARGET_ARCH=armv6 on the make command line for both the build
307 and the install steps.
310 Kernel modules compiled outside of a kernel build now default to
311 installing to /boot/modules instead of /boot/kernel. Many kernel
312 modules built this way (such as those in ports) already overrode
313 KMODDIR explicitly to install into /boot/modules. However,
314 manually building and installing a module from /sys/modules will
315 now install to /boot/modules instead of /boot/kernel.
318 The CAM I/O scheduler has been committed to the kernel. There should be
319 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
320 list of known rogues that claim support for this but actually corrupt
321 data is believed to be complete, be on the lookout for data
322 corruption. The known rogue list is believed to be complete:
324 o Crucial MX100, M550 drives with MU01 firmware.
325 o Micron M510 and M550 drives with MU01 firmware.
326 o Micron M500 prior to MU07 firmware
327 o Samsung 830, 840, and 850 all firmwares
328 o FCCT M500 all firmwares
330 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
331 with working NCQ TRIM. For Micron branded drives, see your sales rep for
332 updated firmware. Black listed drives will work correctly because these
333 drives work correctly so long as no NCQ TRIMs are sent to them. Given
334 this list is the same as found in Linux, it's believed there are no
335 other rogues in the market place. All other models from the above
338 To be safe, if you are at all concerned, you can quirk each of your
339 drives to prevent NCQ from being sent by setting:
340 kern.cam.ada.X.quirks="0x2"
341 in loader.conf. If the drive requires the 4k sector quirk, set the
345 The FAST_DEPEND build option has been removed and its functionality is
346 now the one true way. The old mkdep(1) style of 'make depend' has
347 been removed. See 20160311 for further details.
350 Resource range types have grown from unsigned long to uintmax_t. All
351 drivers, and anything using libdevinfo, need to be recompiled.
354 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
355 builds. It no longer runs mkdep(1) during 'make depend', and the
356 'make depend' stage can safely be skipped now as it is auto ran
357 when building 'make all' and will generate all SRCS and DPSRCS before
358 building anything else. Dependencies are gathered at compile time with
359 -MF flags kept in separate .depend files per object file. Users should
360 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
364 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
365 kernel modules. Therefore, if you load any kernel modules at boot time,
366 please install the boot loaders after you install the kernel, but before
370 make kernel KERNCONF=YOUR_KERNEL_HERE
371 make -C sys/boot install
372 <reboot in single user>
374 Then follow the usual steps, described in the General Notes section,
378 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
379 see the 20141231 entry below for information about prerequisites and
380 upgrading, if you are not already using clang 3.5.0 or higher.
383 The AIO subsystem is now a standard part of the kernel. The
384 VFS_AIO kernel option and aio.ko kernel module have been removed.
385 Due to stability concerns, asynchronous I/O requests are only
386 permitted on sockets and raw disks by default. To enable
387 asynchronous I/O requests on all file types, set the
388 vfs.aio.enable_unsafe sysctl to a non-zero value.
391 The ELF object manipulation tool objcopy is now provided by the
392 ELF Tool Chain project rather than by GNU binutils. It should be a
393 drop-in replacement, with the addition of arm64 support. The
394 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
395 to obtain the GNU version if necessary.
398 Building ZFS pools on top of zvols is prohibited by default. That
399 feature has never worked safely; it's always been prone to deadlocks.
400 Using a zvol as the backing store for a VM guest's virtual disk will
401 still work, even if the guest is using ZFS. Legacy behavior can be
402 restored by setting vfs.zfs.vol.recursive=1.
405 The NONE and HPN patches has been removed from OpenSSH. They are
406 still available in the security/openssh-portable port.
409 With the addition of ypldap(8), a new _ypldap user is now required
410 during installworld. "mergemaster -p" can be used to add the user
411 prior to installworld, as documented in the handbook.
414 The tftp loader (pxeboot) now uses the option root-path directive. As a
415 consequence it no longer looks for a pxeboot.4th file on the tftp
416 server. Instead it uses the regular /boot infrastructure as with the
420 The code to start recording plug and play data into the modules has
421 been committed. While the old tools will properly build a new kernel,
422 a number of warnings about "unknown metadata record 4" will be produced
423 for an older kldxref. To avoid such warnings, make sure to rebuild
424 the kernel toolchain (or world). Make sure that you have r292078 or
425 later when trying to build 292077 or later before rebuilding.
428 Debug data files are now built by default with 'make buildworld' and
429 installed with 'make installworld'. This facilitates debugging but
430 requires more disk space both during the build and for the installed
431 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
435 r291527 changed the internal interface between the nfsd.ko and
436 nfscommon.ko modules. As such, they must both be upgraded to-gether.
437 __FreeBSD_version has been bumped because of this.
440 Add support for unicode collation strings leads to a change of
441 order of files listed by ls(1) for example. To get back to the old
442 behaviour, set LC_COLLATE environment variable to "C".
444 Databases administrators will need to reindex their databases given
445 collation results will be different.
447 Due to a bug in install(1) it is recommended to remove the ancient
448 locales before running make installworld.
450 rm -rf /usr/share/locale/*
453 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
454 libcrypto.so.7 or libssl.so.7 must be recompiled.
457 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
458 Kernel modules isp_2400_multi and isp_2500_multi were removed and
459 should be replaced with isp_2400 and isp_2500 modules respectively.
462 The build previously allowed using 'make -n' to not recurse into
463 sub-directories while showing what commands would be executed, and
464 'make -n -n' to recursively show commands. Now 'make -n' will recurse
465 and 'make -N' will not.
468 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
469 and etcupdate will now use this file. A custom sendmail.cf is now
470 updated via this mechanism rather than via installworld. If you had
471 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
472 want to remove the exclusion or change it to "always install".
473 /etc/mail/sendmail.cf is now managed the same way regardless of
474 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
475 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
478 Compatibility shims for legacy ATA device names have been removed.
479 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
480 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
481 environment variables, /dev/ad* and /dev/ar* symbolic links.
484 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
485 Please see the 20141231 entry below for information about prerequisites
486 and upgrading, if you are not already using clang 3.5.0 or higher.
489 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
490 and renamed from .symbols to .debug. This reduces the size requirements
491 on the boot partition or file system and provides consistency with
492 userland debug files.
494 When using the supported kernel installation method the
495 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
496 as is done with /boot/kernel.
498 Developers wishing to maintain the historical behavior of installing
499 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
502 The wireless drivers had undergone changes that remove the 'parent
503 interface' from the ifconfig -l output. The rc.d network scripts
504 used to check presence of a parent interface in the list, so old
505 scripts would fail to start wireless networking. Thus, etcupdate(3)
506 or mergemaster(8) run is required after kernel update, to update your
507 rc.d scripts in /etc.
510 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
511 These configurations are now automatically interpreted as
512 'scrub fragment reassemble'.
515 Kernel-loadable modules for the random(4) device are back. To use
516 them, the kernel must have
519 options RANDOM_LOADABLE
521 kldload(8) can then be used to load random_fortuna.ko
522 or random_yarrow.ko. Please note that due to the indirect
523 function calls that the loadable modules need to provide,
524 the build-in variants will be slightly more efficient.
526 The random(4) kernel option RANDOM_DUMMY has been retired due to
527 unpopularity. It was not all that useful anyway.
530 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
531 Control over building the ELF Tool Chain tools is now provided by
532 the WITHOUT_TOOLCHAIN knob.
535 The polarity of Pulse Per Second (PPS) capture events with the
536 uart(4) driver has been corrected. Prior to this change the PPS
537 "assert" event corresponded to the trailing edge of a positive PPS
538 pulse and the "clear" event was the leading edge of the next pulse.
540 As the width of a PPS pulse in a typical GPS receiver is on the
541 order of 1 millisecond, most users will not notice any significant
542 difference with this change.
544 Anyone who has compensated for the historical polarity reversal by
545 configuring a negative offset equal to the pulse width will need to
546 remove that workaround.
549 The default group assigned to /dev/dri entries has been changed
550 from 'wheel' to 'video' with the id of '44'. If you want to have
551 access to the dri devices please add yourself to the video group
554 # pw groupmod video -m $USER
557 The menu.rc and loader.rc files will now be replaced during
558 upgrades. Please migrate local changes to menu.rc.local and
559 loader.rc.local instead.
562 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
563 strings and strip have been removed. The src.conf(5) knob
564 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
567 As ZFS requires more kernel stack pages than is the default on some
568 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
569 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
571 Please consider using 'options KSTACK_PAGES=X' where X is greater
572 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
575 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
576 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
577 default, i.e., they will not contain "::". For example, instead
578 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
579 to have a more specific match, such as different map entries for
580 IPv6:0:0 vs IPv6:0. This change requires that configuration
581 data (including maps, files, classes, custom ruleset, etc.) must
582 use the same format, so make certain such configuration data is
583 upgrading. As a very simple check search for patterns like
584 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
585 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
586 the cf option UseCompressedIPv6Addresses.
589 The default kernel entropy-processing algorithm is now
590 Fortuna, replacing Yarrow.
592 Assuming you have 'device random' in your kernel config
593 file, the configurations allow a kernel option to override
594 this default. You may choose *ONE* of:
596 options RANDOM_YARROW # Legacy /dev/random algorithm.
597 options RANDOM_DUMMY # Blocking-only driver.
599 If you have neither, you get Fortuna. For most people,
600 read no further, Fortuna will give a /dev/random that works
601 like it always used to, and the difference will be irrelevant.
603 If you remove 'device random', you get *NO* kernel-processed
604 entropy at all. This may be acceptable to folks building
605 embedded systems, but has complications. Carry on reading,
606 and it is assumed you know what you need.
608 *PLEASE* read random(4) and random(9) if you are in the
609 habit of tweaking kernel configs, and/or if you are a member
610 of the embedded community, wanting specific and not-usual
611 behaviour from your security subsystems.
613 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
614 random', you will NOT have a functioning /dev/random, and
615 many cryptographic features will not work, including SSH.
616 You may also find strange behaviour from the random(3) set
617 of library functions, in particular sranddev(3), srandomdev(3)
618 and arc4random(3). The reason for this is that the KERN_ARND
619 sysctl only returns entropy if it thinks it has some to
620 share, and with RANDOM_DUMMY or no 'device random' this
624 An additional fix for the issue described in the 20150614 sendmail
625 entry below has been been committed in revision 284717.
628 FreeBSD's old make (fmake) has been removed from the system. It is
629 available as the devel/fmake port or via pkg install fmake.
632 The fix for the issue described in the 20150614 sendmail entry
633 below has been been committed in revision 284436. The work
634 around described in that entry is no longer needed unless the
635 default setting is overridden by a confDH_PARAMETERS configuration
636 setting of '5' or pointing to a 512 bit DH parameter file.
639 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
640 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
641 and devel/kyua to version 0.20+ and adjust any calling code to work
642 with Kyuafile and kyua.
645 The import of openssl to address the FreeBSD-SA-15:10.openssl
646 security advisory includes a change which rejects handshakes
647 with DH parameters below 768 bits. sendmail releases prior
648 to 8.15.2 (not yet released), defaulted to a 512 bit
649 DH parameter setting for client connections. To work around
650 this interoperability, sendmail can be configured to use a
651 2048 bit DH parameter by:
653 1. Edit /etc/mail/`hostname`.mc
654 2. If a setting for confDH_PARAMETERS does not exist or
655 exists and is set to a string beginning with '5',
657 3. If a setting for confDH_PARAMETERS exists and is set to
658 a file path, create a new file with:
659 openssl dhparam -out /path/to/file 2048
660 4. Rebuild the .cf file:
661 cd /etc/mail/; make; make install
663 cd /etc/mail/; make restart
665 A sendmail patch is coming, at which time this file will be
669 Generation of legacy formatted entries have been disabled by default
670 in pwd_mkdb(8), as all base system consumers of the legacy formatted
671 entries were converted to use the new format by default when the new,
672 machine independent format have been added and supported since FreeBSD
675 Please see the pwd_mkdb(8) manual page for further details.
678 Clang and llvm have been upgraded to 3.6.1 release. Please see the
679 20141231 entry below for information about prerequisites and upgrading,
680 if you are not already using 3.5.0 or higher.
683 TI platform code switched to using vendor DTS files and this update
684 may break existing systems running on Beaglebone, Beaglebone Black,
687 - dtb files should be regenerated/reinstalled. Filenames are the
688 same but content is different now
689 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
690 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
691 addressing scheme is now pin 25 on /dev/gpioc3.
692 - Pandaboard: /etc/ttys should be updated, serial console device is
693 now /dev/ttyu2, not /dev/ttyu0
696 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
697 If you need the GNU extension from groff soelim(1), install groff
698 from package: pkg install groff, or via ports: textproc/groff.
701 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
702 defined in symlink(7); previously symlinks were silently ignored.
705 The const qualifier has been removed from iconv(3) to comply with
706 POSIX. The ports tree is aware of this from r384038 onwards.
709 Libraries specified by LIBADD in Makefiles must have a corresponding
710 DPADD_<lib> variable to ensure correct dependencies. This is now
711 enforced in src.libnames.mk.
714 From legacy ata(4) driver was removed support for SATA controllers
715 supported by more functional drivers ahci(4), siis(4) and mvs(4).
716 Kernel modules ataahci and ataadaptec were removed completely,
717 replaced by ahci and mvs modules respectively.
720 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
721 the 20141231 entry below for information about prerequisites and
722 upgrading, if you are not already using 3.5.0 or higher.
725 The 32-bit PowerPC kernel has been changed to a position-independent
726 executable. This can only be booted with a version of loader(8)
727 newer than January 31, 2015, so make sure to update both world and
728 kernel before rebooting.
731 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
732 but before r278950, the RNG was not seeded properly. Immediately
733 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
734 ssh keys or openssl keys) that were generated w/ a kernel from that
735 range. This does not affect programs that directly used /dev/random
736 or /dev/urandom. All userland uses of arc4random(3) are affected.
739 The autofs(4) ABI was changed in order to restore binary compatibility
740 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
744 The powerpc64 kernel has been changed to a position-independent
745 executable. This can only be booted with a new version of loader(8),
746 so make sure to update both world and kernel before rebooting.
749 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
750 only release, no new features have been added. Please see the 20141231
751 entry below for information about prerequisites and upgrading, if you
752 are not already using 3.5.0.
755 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
756 taken from the ELF Tool Chain project rather than GNU binutils. They
757 should be drop-in replacements, with the addition of arm64 support.
758 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
759 binutils tools, if necessary. See 20150805 for updated information.
762 The default Unbound configuration now enables remote control
763 using a local socket. Users who have already enabled the
764 local_unbound service should regenerate their configuration
765 by running "service local_unbound setup" as root.
768 The GNU texinfo and GNU info pages have been removed.
769 To be able to view GNU info pages please install texinfo from ports.
772 Clang, llvm and lldb have been upgraded to 3.5.0 release.
774 As of this release, a prerequisite for building clang, llvm and lldb is
775 a C++11 capable compiler and C++11 standard library. This means that to
776 be able to successfully build the cross-tools stage of buildworld, with
777 clang as the bootstrap compiler, your system compiler or cross compiler
778 should either be clang 3.3 or later, or gcc 4.8 or later, and your
779 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
782 On any standard FreeBSD 10.x or 11.x installation, where clang and
783 libc++ are on by default (that is, on x86 or arm), this should work out
786 On 9.x installations where clang is enabled by default, e.g. on x86 and
787 powerpc, libc++ will not be enabled by default, so libc++ should be
788 built (with clang) and installed first. If both clang and libc++ are
789 missing, build clang first, then use it to build libc++.
791 On 8.x and earlier installations, upgrade to 9.x first, and then follow
792 the instructions for 9.x above.
794 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
795 default, and do not build clang.
797 Many embedded systems are resource constrained, and will not be able to
798 build clang in a reasonable time, or in some cases at all. In those
799 cases, cross building bootable systems on amd64 is a workaround.
801 This new version of clang introduces a number of new warnings, of which
802 the following are most likely to appear:
806 This warns in two cases, for both C and C++:
807 * When the code is trying to take the absolute value of an unsigned
808 quantity, which is effectively a no-op, and almost never what was
809 intended. The code should be fixed, if at all possible. If you are
810 sure that the unsigned quantity can be safely cast to signed, without
811 loss of information or undefined behavior, you can add an explicit
812 cast, or disable the warning.
814 * When the code is trying to take an absolute value, but the called
815 abs() variant is for the wrong type, which can lead to truncation.
816 If you want to disable the warning instead of fixing the code, please
817 make sure that truncation will not occur, or it might lead to unwanted
820 -Wtautological-undefined-compare and
821 -Wundefined-bool-conversion
823 These warn when C++ code is trying to compare 'this' against NULL, while
824 'this' should never be NULL in well-defined C++ code. However, there is
825 some legacy (pre C++11) code out there, which actively abuses this
826 feature, which was less strictly defined in previous C++ versions.
828 Squid and openjdk do this, for example. The warning can be turned off
829 for C++98 and earlier, but compiling the code in C++11 mode might result
830 in unexpected behavior; for example, the parts of the program that are
831 unreachable could be optimized away.
834 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
835 kernel sources have been removed. The .h files remain, since some
836 utilities include them. This will need to be fixed later.
837 If "mount -t oldnfs ..." is attempted, it will fail.
838 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
839 the utilities will report errors.
842 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
843 directories to top level SUBDIR variable when their parent
844 directory is included in LOCAL_DIRS. Users with build systems with
845 such hierarchies and without SUBDIR entries in the parent
846 directory Makefiles should add them or add the directories to
850 faith(4) and faithd(8) have been removed from the base system. Faith
851 has been obsolete for a very long time.
854 vt(4), the new console driver, is enabled by default. It brings
855 support for Unicode and double-width characters, as well as
856 support for UEFI and integration with the KMS kernel video
859 You may need to update your console settings in /etc/rc.conf,
860 most probably the keymap. During boot, /etc/rc.d/syscons will
861 indicate what you need to do.
863 vt(4) still has issues and lacks some features compared to
864 syscons(4). See the wiki for up-to-date information:
865 https://wiki.freebsd.org/Newcons
867 If you want to keep using syscons(4), you can do so by adding
868 the following line to /boot/loader.conf:
872 pjdfstest has been integrated into kyua as an opt-in test suite.
873 Please see share/doc/pjdfstest/README for more details on how to
877 gperf has been removed from the base system for architectures
878 that use clang. Ports that require gperf will obtain it from the
882 pjdfstest has been moved from tools/regression/pjdfstest to
886 At svn r271982, The default linux compat kernel ABI has been adjusted
887 to 2.6.18 in support of the linux-c6 compat ports infrastructure
888 update. If you wish to continue using the linux-f10 compat ports,
889 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
890 encouraged to update their linux-compat packages to linux-c6 during
891 their next update cycle.
894 The ofwfb driver, used to provide a graphics console on PowerPC when
895 using vt(4), no longer allows mmap() of all physical memory. This
896 will prevent Xorg on PowerPC with some ATI graphics cards from
897 initializing properly unless x11-servers/xorg-server is updated to
901 The xdev targets have been converted to using TARGET and
902 TARGET_ARCH instead of XDEV and XDEV_ARCH.
905 The default unbound configuration has been modified to address
906 issues with reverse lookups on networks that use private
907 address ranges. If you use the local_unbound service, run
908 "service local_unbound setup" as root to regenerate your
909 configuration, then "service local_unbound reload" to load the
913 The GNU texinfo and GNU info pages are not built and installed
914 anymore, WITH_INFO knob has been added to allow to built and install
916 UPDATE: see 20150102 entry on texinfo's removal
919 The GNU readline library is now an INTERNALLIB - that is, it is
920 statically linked into consumers (GDB and variants) in the base
921 system, and the shared library is no longer installed. The
922 devel/readline port is available for third party software that
926 The Itanium architecture (ia64) has been removed from the list of
927 known architectures. This is the first step in the removal of the
931 Commit r268115 has added NFSv4.1 server support, merged from
932 projects/nfsv4.1-server. Since this includes changes to the
933 internal interfaces between the NFS related modules, a full
934 build of the kernel and modules will be necessary.
935 __FreeBSD_version has been bumped.
938 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
939 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
940 which differs from the behaviour controlled by this knob.)
943 Maximal length of the serial number in CTL was increased from 16 to
944 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
945 and ctld, need to be rebuilt to work with a new kernel.
948 The libatf-c and libatf-c++ major versions were downgraded to 0 and
949 1 respectively to match the upstream numbers. They were out of
950 sync because, when they were originally added to FreeBSD, the
951 upstream versions were not respected. These libraries are private
952 and not yet built by default, so renumbering them should be a
953 non-issue. However, unclean source trees will yield broken test
954 programs once the operator executes "make delete-old-libs" after a
957 Additionally, the atf-sh binary was made private by moving it into
958 /usr/libexec/. Already-built shell test programs will keep the
959 path to the old binary so they will break after "make delete-old"
962 If you are using WITH_TESTS=yes (not the default), wipe the object
963 tree and rebuild from scratch to prevent spurious test failures.
964 This is only needed once: the misnumbered libraries and misplaced
965 binaries have been added to OptionalObsoleteFiles.inc so they will
966 be removed during a clean upgrade.
969 Clang and llvm have been upgraded to 3.4.1 release.
972 We bogusly installed src.opts.mk in /usr/share/mk. This file should
973 be removed to avoid issues in the future (and has been added to
977 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
978 past, it affected all builds that used the bsd.*.mk files. The old
979 behavior was a bug, but people may have relied upon it. To get this
980 behavior back, you can .include /etc/src.conf from /etc/make.conf
981 (which is still global and isn't changed). This also changes the
982 behavior of incremental builds inside the tree of individual
983 directories. Set MAKESYSPATH to ".../share/mk" to do that.
984 Although this has survived make universe and some upgrade scenarios,
985 other upgrade scenarios may have broken. At least one form of
986 temporary breakage was fixed with MAKESYSPATH settings for buildworld
987 as well... In cases where MAKESYSPATH isn't working with this
988 setting, you'll need to set it to the full path to your tree.
990 One side effect of all this cleaning up is that bsd.compiler.mk
991 is no longer implicitly included by bsd.own.mk. If you wish to
992 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
996 The lindev device has been removed since /dev/full has been made a
997 standard device. __FreeBSD_version has been bumped.
1000 The knob WITHOUT_VI was added to the base system, which controls
1001 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1002 in order to reorder files share/termcap and didn't build ex(1) as a
1003 build tool, so building/installing with WITH_VI is highly advised for
1004 build hosts for older releases.
1006 This issue has been fixed in stable/9 and stable/10 in r277022 and
1007 r276991, respectively.
1010 The YES_HESIOD knob has been removed. It has been obsolete for
1011 a decade. Please move to using WITH_HESIOD instead or your builds
1012 will silently lack HESIOD.
1015 The uart(4) driver has been changed with respect to its handling
1016 of the low-level console. Previously the uart(4) driver prevented
1017 any process from changing the baudrate or the CLOCAL and HUPCL
1018 control flags. By removing the restrictions, operators can make
1019 changes to the serial console port without having to reboot.
1020 However, when getty(8) is started on the serial device that is
1021 associated with the low-level console, a misconfigured terminal
1022 line in /etc/ttys will now have a real impact.
1023 Before upgrading the kernel, make sure that /etc/ttys has the
1024 serial console device configured as 3wire without baudrate to
1025 preserve the previous behaviour. E.g:
1026 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1029 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1030 to improve performance. To re-enable it, if needed, run rpcbind
1031 with command line option -W.
1034 Switched back to the GPL dtc compiler due to updates in the upstream
1035 dts files not being supported by the BSDL dtc compiler. You will need
1036 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1037 may result while building dtb files during a kernel build if you fail
1038 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1041 Clang and llvm have been upgraded to 3.4 release.
1044 The nve(4) driver has been removed. Please use the nfe(4) driver
1045 for NVIDIA nForce MCP Ethernet adapters instead.
1048 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1049 This could cause certain C++ applications using shared libraries built
1050 against the previous version of libc++ to crash. The incompatibility
1051 has now been fixed, but any C++ applications or shared libraries built
1052 between r261283 and r261801 should be recompiled.
1055 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1056 capability mode support. Please note that enabling the feature in
1057 kernel is still highly recommended.
1060 OpenSSH is now built with sandbox support, and will use sandbox as
1061 the default privilege separation method. This requires Capsicum
1062 capability mode support in kernel.
1065 The libelf and libdwarf libraries have been updated to newer
1066 versions from upstream. Shared library version numbers for
1067 these two libraries were bumped. Any ports or binaries
1068 requiring these two libraries should be recompiled.
1069 __FreeBSD_version is bumped to 1100006.
1072 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1073 instead of providing an explicit one, this would prevent such
1074 Makefile from providing its own Kyuafile in the future during
1075 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1076 intervention is needed to clean an objdir if you use NO_CLEAN:
1077 # find /usr/obj -name Kyuafile | xargs rm -f
1080 The behavior of gss_pseudo_random() for the krb5 mechanism
1081 has changed, for applications requesting a longer random string
1082 than produced by the underlying enctype's pseudo-random() function.
1083 In particular, the random string produced from a session key of
1084 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1085 be different at the 17th octet and later, after this change.
1086 The counter used in the PRF+ construction is now encoded as a
1087 big-endian integer in accordance with RFC 4402.
1088 __FreeBSD_version is bumped to 1100004.
1091 The WITHOUT_ATF build knob has been removed and its functionality
1092 has been subsumed into the more generic WITHOUT_TESTS. If you were
1093 using the former to disable the build of the ATF libraries, you
1094 should change your settings to use the latter.
1097 The default version of mtree is nmtree which is obtained from
1098 NetBSD. The output is generally the same, but may vary
1099 slightly. If you found you need identical output adding
1100 "-F freebsd9" to the command line should do the trick. For the
1101 time being, the old mtree is available as fmtree.
1104 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1105 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1106 1.1.4_8 and verify bsdyml not linked in, before running "make
1108 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1110 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1113 The stable/10 branch has been created in subversion from head
1117 The rc.d/jail script has been updated to support jail(8)
1118 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1119 for per-jail configuration are automatically converted to
1120 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1121 This is transparently backward compatible. See below about some
1122 incompatibilities and rc.conf(5) manual page for more details.
1124 These variables are now deprecated in favor of jail(8) configuration
1125 file. One can use "rc.d/jail config <jname>" command to generate
1126 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1127 running the jail(8) utility. The default pathname of the
1128 configuration file is /etc/jail.conf and can be specified by
1129 using $jail_conf or $jail_<jname>_conf variables.
1131 Please note that jail_devfs_ruleset accepts an integer at
1132 this moment. Please consider to rewrite the ruleset name
1136 BIND has been removed from the base system. If all you need
1137 is a local resolver, simply enable and start the local_unbound
1138 service instead. Otherwise, several versions of BIND are
1139 available in the ports tree. The dns/bind99 port is one example.
1141 With this change, nslookup(1) and dig(1) are no longer in the base
1142 system. Users should instead use host(1) and drill(1) which are
1143 in the base system. Alternatively, nslookup and dig can
1144 be obtained by installing the dns/bind-tools port.
1147 With the addition of unbound(8), a new unbound user is now
1148 required during installworld. "mergemaster -p" can be used to
1149 add the user prior to installworld, as documented in the handbook.
1152 OpenSSH is now built with DNSSEC support, and will by default
1153 silently trust signed SSHFP records. This can be controlled with
1154 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1155 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1158 The GNU Compiler Collection and C++ standard library (libstdc++)
1159 are no longer built by default on platforms where clang is the system
1160 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1161 options in src.conf.
1164 The PROCDESC kernel option is now part of the GENERIC kernel
1165 configuration and is required for the rwhod(8) to work.
1166 If you are using custom kernel configuration, you should include
1170 The API and ABI related to the Capsicum framework was modified
1171 in backward incompatible way. The userland libraries and programs
1172 have to be recompiled to work with the new kernel. This includes the
1173 following libraries and programs, but the whole buildworld is
1174 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1175 kdump, procstat, rwho, rwhod, uniq.
1178 AES-NI intrinsic support has been added to gcc. The AES-NI module
1179 has been updated to use this support. A new gcc is required to build
1180 the aesni module on both i386 and amd64.
1183 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1184 Thus "device padlock_rng" and "device rdrand_rng" should be
1185 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1188 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1189 enables just the iconv* functionality and is now on by default.
1190 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1191 compatibility. Set WITHOUT_ICONV to build the old way.
1192 If you have been using WITH_ICONV before, you will very likely
1193 need to turn on WITH_LIBICONV_COMPAT.
1196 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1197 Illumos origin, including ZFS. If you have INVARIANTS in your
1198 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1200 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1201 locks if WITNESS option was set. Because that generated a lot of
1202 witness(9) reports and all of them were believed to be false
1203 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1204 can be used to achieve the previous behavior.
1207 Timer values in IPv6 data structures now use time_uptime instead
1208 of time_second. Although this is not a user-visible functional
1209 change, userland utilities which directly use them---ndp(8),
1210 rtadvd(8), and rtsold(8) in the base system---need to be updated
1211 to r253970 or later.
1214 find -delete can now delete the pathnames given as arguments,
1215 instead of only files found below them or if the pathname did
1216 not contain any slashes. Formerly, the following error message
1219 find: -delete: <path>: relative path potentially not safe
1221 Deleting the pathnames given as arguments can be prevented
1222 without error messages using -mindepth 1 or by changing
1223 directory and passing "." as argument to find. This works in the
1224 old as well as the new version of find.
1227 Behavior of devfs rules path matching has been changed.
1228 Pattern is now always matched against fully qualified devfs
1229 path and slash characters must be explicitly matched by
1230 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1231 subdirectories must be reviewed.
1234 The default ARM ABI has changed to the ARM EABI. The old ABI is
1235 incompatible with the ARM EABI and all programs and modules will
1236 need to be rebuilt to work with a new kernel.
1238 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1240 NOTE: Support for the old ABI will be removed in the future and
1241 users are advised to upgrade.
1244 pkg_install has been disconnected from the build if you really need it
1245 you should add WITH_PKGTOOLS in your src.conf(5).
1248 Most of network statistics structures were changed to be able
1249 keep 64-bits counters. Thus all tools, that work with networking
1250 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1253 Fix a bug that allowed a tracing process (e.g. gdb) to write
1254 to a memory-mapped file in the traced process's address space
1255 even if neither the traced process nor the tracing process had
1256 write access to that file.
1259 CVS has been removed from the base system. An exact copy
1260 of the code is available from the devel/cvs port.
1263 Some people report the following error after the switch to bmake:
1265 make: illegal option -- J
1266 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1268 *** [buildworld] Error code 2
1270 this likely due to an old instance of make in
1271 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1272 which src/Makefile will use that blindly, if it exists, so if
1273 you see the above error:
1275 rm -rf `make -V MAKEPATH`
1280 Use bmake by default.
1281 Whereas before one could choose to build with bmake via
1282 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1283 make. The goal is to remove these knobs for 10-RELEASE.
1285 It is worth noting that bmake (like gmake) treats the command
1286 line as the unit of failure, rather than statements within the
1287 command line. Thus '(cd some/where && dosomething)' is safer
1288 than 'cd some/where; dosomething'. The '()' allows consistent
1289 behavior in parallel build.
1292 Fix a bug that allows NFS clients to issue READDIR on files.
1295 The WITHOUT_IDEA option has been removed because
1296 the IDEA patent expired.
1299 The sysctl which controls TRIM support under ZFS has been renamed
1300 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1304 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1305 rather than creating it's own in the temporary directory in
1306 order allow access to bootstrapped versions of tools such as
1307 install and mtree. When upgrading from version of FreeBSD where
1308 the install command does not support -l, you will need to
1309 install a new mergemaster command if mergemaster -p is required.
1310 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1314 Legacy ATA stack, disabled and replaced by new CAM-based one since
1315 FreeBSD 9.0, completely removed from the sources. Kernel modules
1316 atadisk and atapi*, user-level tools atacontrol and burncd are
1317 removed. Kernel option `options ATA_CAM` is now permanently enabled
1321 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1322 and socketpair(2). Software, in particular Kerberos, may
1323 automatically detect and use these during building. The resulting
1324 binaries will not work on older kernels.
1327 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1328 information, see the respective 20130304 entry).
1331 Recent commits to callout(9) changed the size of struct callout,
1332 so the KBI is probably heavily disturbed. Also, some functions
1333 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1334 by macros. Every kernel module using it won't load, so rebuild
1337 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1338 but does not initialize by default (because of the new CTL_DISABLE
1339 option) to save memory. To re-enable it, remove the CTL_DISABLE
1340 option from the kernel config file or set kern.cam.ctl.disable=0
1341 in /boot/loader.conf.
1344 The ctl device has been disabled in GENERIC for i386 and amd64.
1345 This was done due to the extra memory being allocated at system
1346 initialisation time by the ctl driver which was only used if
1347 a CAM target device was created. This makes a FreeBSD system
1348 unusable on 128MB or less of RAM.
1351 A new compression method (lz4) has been merged to -HEAD. Please
1352 refer to zpool-features(7) for more information.
1354 Please refer to the "ZFS notes" section of this file for information
1355 on upgrading boot ZFS pools.
1358 A BSD-licensed patch(1) variant has been added and is installed
1359 as bsdpatch, being the GNU version the default patch.
1360 To inverse the logic and use the BSD-licensed one as default,
1361 while having the GNU version installed as gnupatch, rebuild
1362 and install world with the WITH_BSD_PATCH knob set.
1365 Due to the use of the new -l option to install(1) during build
1366 and install, you must take care not to directly set the INSTALL
1367 make variable in your /etc/make.conf, /etc/src.conf, or on the
1368 command line. If you wish to use the -C flag for all installs
1369 you may be able to add INSTALL+=-C to /etc/make.conf or
1373 The install(1) option -M has changed meaning and now takes an
1374 argument that is a file or path to append logs to. In the
1375 unlikely event that -M was the last option on the command line
1376 and the command line contained at least two files and a target
1377 directory the first file will have logs appended to it. The -M
1378 option served little practical purpose in the last decade so its
1379 use is expected to be extremely rare.
1382 After switching to Clang as the default compiler some users of ZFS
1383 on i386 systems started to experience stack overflow kernel panics.
1384 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1387 GEOM_LABEL now mangles label names read from file system metadata.
1388 Mangling affect labels containing spaces, non-printable characters,
1389 '%' or '"'. Device names in /etc/fstab and other places may need to
1393 By default, only the 10 most recent kernel dumps will be saved. To
1394 restore the previous behaviour (no limit on the number of kernel dumps
1395 stored in the dump directory) add the following line to /etc/rc.conf:
1400 With the addition of auditdistd(8), a new auditdistd user is now
1401 required during installworld. "mergemaster -p" can be used to
1402 add the user prior to installworld, as documented in the handbook.
1405 The sin6_scope_id member variable in struct sockaddr_in6 is now
1406 filled by the kernel before passing the structure to the userland via
1407 sysctl or routing socket. This means the KAME-specific embedded scope
1408 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1409 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1410 __FreeBSD_version is bumped to 1000025.
1413 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1414 This means that the world and kernel will be compiled with clang
1415 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1416 and /usr/bin/cpp. To disable this behavior and revert to building
1417 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1418 of current may need to bootstrap WITHOUT_CLANG first if the clang
1419 build fails (its compatibility window doesn't extend to the 9 stable
1423 The IPFIREWALL_FORWARD kernel option has been removed. Its
1424 functionality now turned on by default.
1427 The ZERO_COPY_SOCKET kernel option has been removed and
1428 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1429 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1430 mechanism which is not safe and may result in kernel crashes.
1431 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1432 driver supports disposeable external page sized mbuf storage.
1433 Proper replacements for both zero-copy mechanisms are under
1434 consideration and will eventually lead to complete removal
1435 of the two kernel options.
1438 The IPv4 network stack has been converted to network byte
1439 order. The following modules need to be recompiled together
1440 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1441 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1444 Support for non-MPSAFE filesystems was removed from VFS. The
1445 VFS_VERSION was bumped, all filesystem modules shall be
1449 All the non-MPSAFE filesystems have been disconnected from
1450 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1451 portalfs, smbfs, xfs.
1454 The interface cloning API and ABI has changed. The following
1455 modules need to be recompiled together with kernel:
1456 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1457 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1458 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1461 The sdhci driver was split in two parts: sdhci (generic SD Host
1462 Controller logic) and sdhci_pci (actual hardware driver).
1463 No kernel config modifications are required, but if you
1464 load sdhc as a module you must switch to sdhci_pci instead.
1467 Import the FUSE kernel and userland support into base system.
1470 The GNU sort(1) program has been removed since the BSD-licensed
1471 sort(1) has been the default for quite some time and no serious
1472 problems have been reported. The corresponding WITH_GNU_SORT
1476 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1477 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1481 The net80211(4) ABI has been changed to allow for improved driver
1482 PS-POLL and power-save support. All wireless drivers need to be
1483 recompiled to work with the new kernel.
1486 The random(4) support for the VIA hardware random number
1487 generator (`PADLOCK') is no longer enabled unconditionally.
1488 Add the padlock_rng device in the custom kernel config if
1489 needed. The GENERIC kernels on i386 and amd64 do include the
1490 device, so the change only affects the custom kernel
1494 The pf(4) packet filter ABI has been changed. pfctl(8) and
1495 snmp_pf module need to be recompiled to work with new kernel.
1498 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1499 to -HEAD. Pools that have empty_bpobj in active state can not be
1500 imported read-write with ZFS implementations that do not support
1501 this feature. For more information read the zpool-features(5)
1505 The sparc64 ZFS loader has been changed to no longer try to auto-
1506 detect ZFS providers based on diskN aliases but now requires these
1507 to be explicitly listed in the OFW boot-device environment variable.
1510 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1511 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1512 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1515 The following sysctls and tunables have been renamed for consistency
1516 with other variables:
1517 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1518 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1521 The sort utility has been replaced with BSD sort. For now, GNU sort
1522 is also available as "gnusort" or the default can be set back to
1523 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1524 installed as "bsdsort".
1527 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1528 Starting with this version the old system of ZFS pool versioning
1529 is superseded by "feature flags". This concept enables forward
1530 compatibility against certain future changes in functionality of ZFS
1531 pools. The first read-only compatible "feature flag" for ZFS pools
1532 is named "com.delphix:async_destroy". For more information
1533 read the new zpool-features(5) manual page.
1534 Please refer to the "ZFS notes" section of this file for information
1535 on upgrading boot ZFS pools.
1538 The malloc(3) implementation embedded in libc now uses sources imported
1539 as contrib/jemalloc. The most disruptive API change is to
1540 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1541 delete it prior to installworld, and optionally re-create it using the
1542 new format after rebooting. See malloc.conf(5) for details
1543 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1547 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1548 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1549 now spelled mips. This is to aid compatibility with third-party
1550 software that expects this naming scheme in uname(3). Little-endian
1551 settings are unchanged. If you are updating a big-endian mips64 machine
1552 from before this change, you may need to set MACHINE_ARCH=mips64 in
1553 your environment before the new build system will recognize your machine.
1556 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1560 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1561 nullfs(5) did not pass through all behaviours to the underlying layer,
1562 as a result if we bound to a socket on the lower layer we could connect
1563 only to the lower path; if we bound to the upper layer we could connect
1564 only to the upper path. The new behavior is one can connect to both the
1565 lower and the upper paths regardless what layer path one binds to.
1568 The getifaddrs upgrade path broken with 20111215 has been restored.
1569 If you have upgraded in between 20111215 and 20120209 you need to
1570 recompile libc again with your kernel. You still need to recompile
1571 world to be able to configure CARP but this restriction already
1572 comes from 20111215.
1575 The set_rcvar() function has been removed from /etc/rc.subr. All
1576 base and ports rc.d scripts have been updated, so if you have a
1577 port installed with a script in /usr/local/etc/rc.d you can either
1578 hand-edit the rcvar= line, or reinstall the port.
1580 An easy way to handle the mass-update of /etc/rc.d:
1581 rm /etc/rc.d/* && mergemaster -i
1584 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1585 on the current CPU and prevents other threads from running.
1586 This behavior can be reverted using the kern.stop_scheduler_on_panic
1588 The new behavior can be incompatible with kern.sync_on_panic.
1591 The carp(4) facility has been changed significantly. Configuration
1592 of the CARP protocol via ifconfig(8) has changed, as well as format
1593 of CARP events submitted to devd(8) has changed. See manual pages
1594 for more information. The arpbalance feature of carp(4) is currently
1595 not supported anymore.
1597 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1598 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1599 need to be recompiled.
1602 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1606 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1607 explicitely support non-MPSAFE filesystems.
1608 It is on by default for all supported platform at this present
1612 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1613 i386 and pc98 GENERIC kernel configuration files.
1616 sysinstall has been removed
1619 The stable/9 branch created in subversion. This corresponds to the
1620 RELENG_9 branch in CVS.
1626 Avoid using make -j when upgrading. While generally safe, there are
1627 sometimes problems using -j to upgrade. If your upgrade fails with
1628 -j, please try again without -j. From time to time in the past there
1629 have been problems using -j with buildworld and/or installworld. This
1630 is especially true when upgrading between "distant" versions (eg one
1631 that cross a major release boundary or several minor releases, or when
1632 several months have passed on the -current branch).
1634 Sometimes, obscure build problems are the result of environment
1635 poisoning. This can happen because the make utility reads its
1636 environment when searching for values for global variables. To run
1637 your build attempts in an "environmental clean room", prefix all make
1638 commands with 'env -i '. See the env(1) manual page for more details.
1640 When upgrading from one major version to another it is generally best
1641 to upgrade to the latest code in the currently installed branch first,
1642 then do an upgrade to the new branch. This is the best-tested upgrade
1643 path, and has the highest probability of being successful. Please try
1644 this approach before reporting problems with a major version upgrade.
1646 When upgrading a live system, having a root shell around before
1647 installing anything can help undo problems. Not having a root shell
1648 around can lead to problems if pam has changed too much from your
1649 starting point to allow continued authentication after the upgrade.
1651 This file should be read as a log of events. When a later event changes
1652 information of a prior event, the prior event should not be deleted.
1653 Instead, a pointer to the entry with the new information should be
1654 placed in the old entry. Readers of this file should also sanity check
1655 older entries before relying on them blindly. Authors of new entries
1656 should write them with this in mind.
1660 When upgrading the boot ZFS pool to a new version, always follow
1663 1.) recompile and reinstall the ZFS boot loader and boot block
1664 (this is part of "make buildworld" and "make installworld")
1666 2.) update the ZFS boot block on your boot drive
1668 The following example updates the ZFS boot block on the first
1669 partition (freebsd-boot) of a GPT partitioned drive ada0:
1670 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1672 Non-boot pools do not need these updates.
1676 If you are updating from a prior version of FreeBSD (even one just
1677 a few days old), you should follow this procedure. It is the most
1678 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1680 make kernel-toolchain
1681 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1682 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1684 To test a kernel once
1685 ---------------------
1686 If you just want to boot a kernel once (because you are not sure
1687 if it works, or if you want to boot a known bad kernel to provide
1688 debugging information) run
1689 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1690 nextboot -k testkernel
1692 To just build a kernel when you know that it won't mess you up
1693 --------------------------------------------------------------
1694 This assumes you are already running a CURRENT system. Replace
1695 ${arch} with the architecture of your machine (e.g. "i386",
1696 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1698 cd src/sys/${arch}/conf
1699 config KERNEL_NAME_HERE
1700 cd ../compile/KERNEL_NAME_HERE
1705 If this fails, go to the "To build a kernel" section.
1707 To rebuild everything and install it on the current system.
1708 -----------------------------------------------------------
1709 # Note: sometimes if you are running current you gotta do more than
1710 # is listed here if you are upgrading from a really old current.
1712 <make sure you have good level 0 dumps>
1714 make kernel KERNCONF=YOUR_KERNEL_HERE
1716 <reboot in single user> [3]
1723 To cross-install current onto a separate partition
1724 --------------------------------------------------
1725 # In this approach we use a separate partition to hold
1726 # current's root, 'usr', and 'var' directories. A partition
1727 # holding "/", "/usr" and "/var" should be about 2GB in
1730 <make sure you have good level 0 dumps>
1733 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1734 <maybe newfs current's root partition>
1735 <mount current's root partition on directory ${CURRENT_ROOT}>
1736 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1737 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1738 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1739 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1740 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1741 <reboot into current>
1742 <do a "native" rebuild/install as described in the previous section>
1743 <maybe install compatibility libraries from ports/misc/compat*>
1747 To upgrade in-place from stable to current
1748 ----------------------------------------------
1749 <make sure you have good level 0 dumps>
1751 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1753 <reboot in single user> [3]
1760 Make sure that you've read the UPDATING file to understand the
1761 tweaks to various things you need. At this point in the life
1762 cycle of current, things change often and you are on your own
1763 to cope. The defaults can also change, so please read ALL of
1764 the UPDATING entries.
1766 Also, if you are tracking -current, you must be subscribed to
1767 freebsd-current@freebsd.org. Make sure that before you update
1768 your sources that you have read and understood all the recent
1769 messages there. If in doubt, please track -stable which has
1770 much fewer pitfalls.
1772 [1] If you have third party modules, such as vmware, you
1773 should disable them at this point so they don't crash your
1776 [3] From the bootblocks, boot -s, and then do
1781 adjkerntz -i # if CMOS is wall time
1782 Also, when doing a major release upgrade, it is required that
1783 you boot into single user mode to do the installworld.
1785 [4] Note: This step is non-optional. Failure to do this step
1786 can result in a significant reduction in the functionality of the
1787 system. Attempting to do it by hand is not recommended and those
1788 that pursue this avenue should read this file carefully, as well
1789 as the archives of freebsd-current and freebsd-hackers mailing lists
1790 for potential gotchas. The -U option is also useful to consider.
1791 See mergemaster(8) for more information.
1793 [5] Usually this step is a noop. However, from time to time
1794 you may need to do this if you get unknown user in the following
1795 step. It never hurts to do it all the time. You may need to
1796 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1797 install) after the buildworld before this step if you last updated
1798 from current before 20130425 or from -stable before 20130430.
1800 [6] This only deletes old files and directories. Old libraries
1801 can be deleted by "make delete-old-libs", but you have to make
1802 sure that no program is using those libraries anymore.
1804 [8] The new kernel must be able to run existing binaries used by
1805 an installworld. When upgrading across major versions, the new
1806 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1807 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1808 binaries). Failure to do so may leave you with a system that is
1809 hard to boot to recover. A GENERIC kernel will include suitable
1810 compatibility options to run binaries from older branches.
1812 Make sure that you merge any new devices from GENERIC since the
1813 last time you updated your kernel config file.
1815 [9] When checking out sources, you must include the -P flag to have
1816 cvs prune empty directories.
1818 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1819 "?=" instead of the "=" assignment operator, so that buildworld can
1820 override the CPUTYPE if it needs to.
1822 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1823 not on the command line, or in /etc/make.conf. buildworld will
1824 warn if it is improperly defined.
1827 This file contains a list, in reverse chronological order, of major
1828 breakages in tracking -current. It is not guaranteed to be a complete
1829 list of such breakages, and only contains entries since September 23, 2011.
1830 If you need to see UPDATING entries from before that date, you will need
1831 to fetch an UPDATING file from an older FreeBSD release.
1833 Copyright information:
1835 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1837 Redistribution, publication, translation and use, with or without
1838 modification, in full or in part, in any form or format of this
1839 document are permitted without further permission from the author.
1841 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1842 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1843 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1844 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1845 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1846 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1847 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1848 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1849 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1850 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1851 POSSIBILITY OF SUCH DAMAGE.
1853 Contact Warner Losh if you have any questions about your use of