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