1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 20190702 p1 FreeBSD-EN-19:12.tzdata
20 FreeBSD-SA-19:09.iconv
21 FreeBSD-SA-19:11.cd_ioctl
23 Import tzdata 2019b. [EN-19:12.tzdata]
25 Fix iconv buffer overflow. [SA-19:09.iconv]
27 Fix privilege escalation in cd(4) driver. [SA-19:11.cd_ioctl]
30 CARP now sets DSCP value CS7(Network Traffic) in the flowlabel field
31 of packets by default instead of only setting TOS_LOWDELAY in IPv4,
32 which was deprecated in 1998. Original behavior can be restored by
33 setting sysctl net.inet.carp.dscp=4.
36 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
37 8.0.0. Please see the 20141231 entry below for information about
38 prerequisites and upgrading, if you are not already using clang 3.5.0
42 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
43 compiled into your custom kernel, add 'device xz' statement to the
47 Co-existance for Forth and Lua interpreters in bootloaders has now been
48 merged to ease testing of lualoader. LOADER_DEFAULT_INTERP, documented
49 in build(7), may be used to control which interpreter flavor is used in
50 the default loader to be installed. For systems where Lua and Forth
51 coexist, this switch can also be made on a running system by creating a
52 link from /boot/loader{,.efi} to /boot/loader_${flavor}{,.efi} rather
53 than requiring a rebuild.
55 The default flavor in this branch will remain Forth. As indicated in
56 the 20190216 UPDATING entry, booting is a complex environment; it would
57 be prudent to assume that lualoader may not work for your setup and make
58 provisions for backup boot methods.
61 zfsloader's functionality has now been folded into loader.
62 zfsloader is no longer necesasary once you've updated your
63 boot blocks. For a transition period, we will install a
64 hardlink for zfsloader to loader to allow a smooth transition
65 until the boot blocks can be updated (hard link because old
66 zfs boot blocks don't understand symlinks).
69 Lualoader has been merged to facilitate testing on this branch. It's
70 purely opt-in for now by building WITH_LOADER_LUA and WITHOUT_FORTH in
71 /etc/src.conf, but co-existance will come shortly. Booting is a complex
72 environment and test coverage for Lua-enabled loaders has been thin, so
73 it would be prudent to assume it might not work and make provisions for
77 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
78 7.0.1. Please see the 20141231 entry below for information about
79 prerequisites and upgrading, if you are not already using clang 3.5.0
83 r342562 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
84 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
85 servers that have vfs.nfsd.nfs_privport set will only allow mounts
86 from clients using a reserved port#. Since both the FreeBSD and Linux
87 NFSv4 clients use reserved port#s by default, this should not affect
91 The '%I' format in the kern.corefile sysctl limits the number of
92 core files that a process can generate to the number stored in the
93 debug.ncores sysctl. The '%I' format is replaced by the single digit
94 index. Previously, if all indexes were taken the kernel would overwrite
95 only a core file with the highest index in a filename.
96 Currently the system will create a new core file if there is a free
97 index or if all slots are taken it will overwrite the oldest one.
100 WITH_OFED option now only enables the build for the OFED libraries
101 and some fundamental client utilities. OpenSM and rest of the
102 debugging tools are enabled by WITH_OFED_EXTRA build switch.
103 WITH_OFED is turned on by default on amd64.
106 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
107 6.0.1. Please see the 20141231 entry below for information about
108 prerequisites and upgrading, if you are not already using clang 3.5.0
112 The releng/11.2 branch has been created from stable/11@r334458.
115 The tz database (tzdb) has been updated to 2018e. This version more
116 correctly models time stamps in time zones with negative DST such as
117 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
118 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
119 time zone abbreviations and the tm_isdst flag.
122 The use of RSS hash from the network card aka flowid has been
123 disabled by default for lagg(4) as it's currently incompatible with
124 the lacp and loadbalance protocols.
126 This can be re-enabled by setting the following in loader.conf:
127 net.link.lagg.default_use_flowid="1"
130 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
131 6.0.0. Please see the 20141231 entry below for information about
132 prerequisites and upgrading, if you are not already using clang 3.5.0
136 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
137 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
138 to WITH/OUT_LOADER_GELI.
141 The geli password typed at boot is now hidden. To restore the previous
142 behavior, see geli(8) for configuration options.
144 The SW_WATCHDOG option is no longer necessary to enable the
145 hardclock-based software watchdog if no hardware watchdog is
146 configured. As before, SW_WATCHDOG will cause the software
147 watchdog to be enabled even if a hardware watchdog is configured.
150 lint(1) binaries and library are no longer built by default. To
151 enable building them, define WITH_LINT in src.conf. If you are using
152 a FreeBSD 12 or later system to build 11-stable, you may need to
153 install a lint(1) binary to use WITH_LINT.
156 When building multiple kernels using KERNCONF, non-existent KERNCONF
157 files will produce an error and buildkernel will fail. Previously
158 missing KERNCONF files silently failed giving no indication as to
159 why, only to subsequently discover during installkernel that the
160 desired kernel was never built in the first place.
163 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
164 Please see the 20141231 entry below for information about prerequisites
165 and upgrading, if you are not already using clang 3.5.0 or higher.
168 Since the switch to GPT disk labels, fsck for UFS/FFS has been
169 unable to automatically find alternate superblocks. As of r322806,
170 the information needed to find alternate superblocks has been
171 moved to the end of the area reserved for the boot block.
172 Filesystems created with a newfs of this vintage or later
173 will create the recovery information. If you have a filesystem
174 created prior to this change and wish to have a recovery block
175 created for your filesystem, you can do so by running fsck in
176 forground mode (i.e., do not use the -p or -y options). As it
177 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
178 to which you should answer yes.
181 The releng/11.1 branch has been created from stable/11@r320475.
184 arm64 builds now use the base system LLD 4.0.0 linker by default,
185 instead of requiring that the aarch64-binutils port or package be
186 installed. To continue using aarch64-binutils, set
187 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
190 The ctl.ko module no longer implements the iSCSI target frontend:
191 cfiscsi.ko does instead.
193 If building cfiscsi.ko as a kernel module, the module can be loaded
194 via one of the following methods:
195 - `cfiscsi_load="YES"` in loader.conf(5).
196 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
197 - ctladm(8)/ctld(8), when compiled with iSCSI support
198 (`WITH_ISCSI=yes` in src.conf(5))
200 Please see cfiscsi(4) for more details.
203 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
204 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
205 same source (previously, the dependency of mmcsd.ko on mmc.ko was
206 missing, but mmcsd.ko now will refuse to load if it is incompatible
210 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
211 use any explicitly assigned loopback address available in the jail
212 instead of using the first assigned address of the jail.
215 As of r316810 for ipfilter, keep frags is no longer assumed when
216 keep state is specified in a rule. r316810 aligns ipfilter with
217 documentation in man pages separating keep frags from keep state.
218 This allows keep state to specified without forcing keep frags
219 and allows keep frags to be specified independently of keep state.
220 To maintain previous behaviour, also specify keep frags with
221 keep state (as documented in ipf.conf.5).
224 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
225 Please see the 20141231 entry below for information about prerequisites
226 and upgrading, if you are not already using clang 3.5.0 or higher.
229 The code that provides support for ZFS .zfs/ directory functionality
230 has been reimplemented. It's not possible now to create a snapshot
231 by mkdir under .zfs/snapshot/. That should be the only user visible
235 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
236 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
237 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
238 and now NAT-T is supported by default. Security associations now use
239 the single namespace for SPI allocation, so if you use several manually
240 configured security associations with the same SPI, this configuration
244 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
245 Please see the 20141231 entry below for information about prerequisites
246 and upgrading, if you are not already using clang 3.5.0 or higher.
249 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
250 Please see the 20141231 entry below for information about prerequisites
251 and upgrading, if you are not already using clang 3.5.0 or higher.
254 The layout of the pmap structure has changed for powerpc to put the pmap
255 statistics at the front for all CPU variations. libkvm(3) and all tools
256 that link against it need to be recompiled.
259 isl(4) and cyapa(4) drivers now require a new driver,
260 chromebook_platform(4), to work properly on Chromebook-class hardware.
261 On other types of hardware the drivers may need to be configured using
262 device hints. Please see the corresponding manual pages for details.
265 Relocatable object files with the extension of .So have been renamed
266 to use an extension of .pico instead. The purpose of this change is
267 to avoid a name clash with shared libraries on case-insensitive file
268 systems. On those file systems, foo.So is the same file as foo.so.
271 The releng/11.0 branch has been created from stable/11@r303970.
274 The stable/11 branch has been created from head@r302406.
277 The libc stub for the pipe(2) system call has been replaced with
278 a wrapper that calls the pipe2(2) system call and the pipe(2)
279 system call is now only implemented by the kernels that include
280 "options COMPAT_FREEBSD10" in their config file (this is the
281 default). Users should ensure that this option is enabled in
282 their kernel or upgrade userspace to r302092 before upgrading their
286 CAM will now strip leading spaces from SCSI disks' serial numbers.
287 This will effect users who create UFS filesystems on SCSI disks using
288 those disk's diskid device nodes. For example, if /etc/fstab
289 previously contained a line like
290 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
291 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
292 transforms like gmirror may also be affected. ZFS users should
296 The bitstring(3) API has been updated with new functionality and
297 improved performance. But it is binary-incompatible with the old API.
298 Objects built with the new headers may not be linked against objects
299 built with the old headers.
302 The brk and sbrk functions have been removed from libc on arm64.
303 Binutils from ports has been updated to not link to these
304 functions and should be updated to the latest version before
305 installing a new libc.
308 The armv6 port now defaults to hard float ABI. Limited support
309 for running both hardfloat and soft float on the same system
310 is available using the libraries installed with -DWITH_LIBSOFT.
311 This has only been tested as an upgrade path for installworld
312 and packages may fail or need manual intervention to run. New
313 packages will be needed.
315 To update an existing self-hosted armv6hf system, you must add
316 TARGET_ARCH=armv6 on the make command line for both the build
317 and the install steps.
320 Kernel modules compiled outside of a kernel build now default to
321 installing to /boot/modules instead of /boot/kernel. Many kernel
322 modules built this way (such as those in ports) already overrode
323 KMODDIR explicitly to install into /boot/modules. However,
324 manually building and installing a module from /sys/modules will
325 now install to /boot/modules instead of /boot/kernel.
328 The CAM I/O scheduler has been committed to the kernel. There should be
329 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
330 list of known rogues that claim support for this but actually corrupt
331 data is believed to be complete, be on the lookout for data
332 corruption. The known rogue list is believed to be complete:
334 o Crucial MX100, M550 drives with MU01 firmware.
335 o Micron M510 and M550 drives with MU01 firmware.
336 o Micron M500 prior to MU07 firmware
337 o Samsung 830, 840, and 850 all firmwares
338 o FCCT M500 all firmwares
340 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
341 with working NCQ TRIM. For Micron branded drives, see your sales rep for
342 updated firmware. Black listed drives will work correctly because these
343 drives work correctly so long as no NCQ TRIMs are sent to them. Given
344 this list is the same as found in Linux, it's believed there are no
345 other rogues in the market place. All other models from the above
348 To be safe, if you are at all concerned, you can quirk each of your
349 drives to prevent NCQ from being sent by setting:
350 kern.cam.ada.X.quirks="0x2"
351 in loader.conf. If the drive requires the 4k sector quirk, set the
355 The FAST_DEPEND build option has been removed and its functionality is
356 now the one true way. The old mkdep(1) style of 'make depend' has
357 been removed. See 20160311 for further details.
360 Resource range types have grown from unsigned long to uintmax_t. All
361 drivers, and anything using libdevinfo, need to be recompiled.
364 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
365 builds. It no longer runs mkdep(1) during 'make depend', and the
366 'make depend' stage can safely be skipped now as it is auto ran
367 when building 'make all' and will generate all SRCS and DPSRCS before
368 building anything else. Dependencies are gathered at compile time with
369 -MF flags kept in separate .depend files per object file. Users should
370 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
374 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
375 kernel modules. Therefore, if you load any kernel modules at boot time,
376 please install the boot loaders after you install the kernel, but before
380 make kernel KERNCONF=YOUR_KERNEL_HERE
381 make -C sys/boot install
382 <reboot in single user>
384 Then follow the usual steps, described in the General Notes section,
388 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
389 see the 20141231 entry below for information about prerequisites and
390 upgrading, if you are not already using clang 3.5.0 or higher.
393 The AIO subsystem is now a standard part of the kernel. The
394 VFS_AIO kernel option and aio.ko kernel module have been removed.
395 Due to stability concerns, asynchronous I/O requests are only
396 permitted on sockets and raw disks by default. To enable
397 asynchronous I/O requests on all file types, set the
398 vfs.aio.enable_unsafe sysctl to a non-zero value.
401 The ELF object manipulation tool objcopy is now provided by the
402 ELF Tool Chain project rather than by GNU binutils. It should be a
403 drop-in replacement, with the addition of arm64 support. The
404 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
405 to obtain the GNU version if necessary.
408 Building ZFS pools on top of zvols is prohibited by default. That
409 feature has never worked safely; it's always been prone to deadlocks.
410 Using a zvol as the backing store for a VM guest's virtual disk will
411 still work, even if the guest is using ZFS. Legacy behavior can be
412 restored by setting vfs.zfs.vol.recursive=1.
415 The NONE and HPN patches has been removed from OpenSSH. They are
416 still available in the security/openssh-portable port.
419 With the addition of ypldap(8), a new _ypldap user is now required
420 during installworld. "mergemaster -p" can be used to add the user
421 prior to installworld, as documented in the handbook.
424 The tftp loader (pxeboot) now uses the option root-path directive. As a
425 consequence it no longer looks for a pxeboot.4th file on the tftp
426 server. Instead it uses the regular /boot infrastructure as with the
430 The code to start recording plug and play data into the modules has
431 been committed. While the old tools will properly build a new kernel,
432 a number of warnings about "unknown metadata record 4" will be produced
433 for an older kldxref. To avoid such warnings, make sure to rebuild
434 the kernel toolchain (or world). Make sure that you have r292078 or
435 later when trying to build 292077 or later before rebuilding.
438 Debug data files are now built by default with 'make buildworld' and
439 installed with 'make installworld'. This facilitates debugging but
440 requires more disk space both during the build and for the installed
441 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
445 r291527 changed the internal interface between the nfsd.ko and
446 nfscommon.ko modules. As such, they must both be upgraded to-gether.
447 __FreeBSD_version has been bumped because of this.
450 Add support for unicode collation strings leads to a change of
451 order of files listed by ls(1) for example. To get back to the old
452 behaviour, set LC_COLLATE environment variable to "C".
454 Databases administrators will need to reindex their databases given
455 collation results will be different.
457 Due to a bug in install(1) it is recommended to remove the ancient
458 locales before running make installworld.
460 rm -rf /usr/share/locale/*
463 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
464 libcrypto.so.7 or libssl.so.7 must be recompiled.
467 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
468 Kernel modules isp_2400_multi and isp_2500_multi were removed and
469 should be replaced with isp_2400 and isp_2500 modules respectively.
472 The build previously allowed using 'make -n' to not recurse into
473 sub-directories while showing what commands would be executed, and
474 'make -n -n' to recursively show commands. Now 'make -n' will recurse
475 and 'make -N' will not.
478 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
479 and etcupdate will now use this file. A custom sendmail.cf is now
480 updated via this mechanism rather than via installworld. If you had
481 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
482 want to remove the exclusion or change it to "always install".
483 /etc/mail/sendmail.cf is now managed the same way regardless of
484 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
485 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
488 Compatibility shims for legacy ATA device names have been removed.
489 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
490 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
491 environment variables, /dev/ad* and /dev/ar* symbolic links.
494 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
495 Please see the 20141231 entry below for information about prerequisites
496 and upgrading, if you are not already using clang 3.5.0 or higher.
499 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
500 and renamed from .symbols to .debug. This reduces the size requirements
501 on the boot partition or file system and provides consistency with
502 userland debug files.
504 When using the supported kernel installation method the
505 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
506 as is done with /boot/kernel.
508 Developers wishing to maintain the historical behavior of installing
509 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
512 The wireless drivers had undergone changes that remove the 'parent
513 interface' from the ifconfig -l output. The rc.d network scripts
514 used to check presence of a parent interface in the list, so old
515 scripts would fail to start wireless networking. Thus, etcupdate(3)
516 or mergemaster(8) run is required after kernel update, to update your
517 rc.d scripts in /etc.
520 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
521 These configurations are now automatically interpreted as
522 'scrub fragment reassemble'.
525 Kernel-loadable modules for the random(4) device are back. To use
526 them, the kernel must have
529 options RANDOM_LOADABLE
531 kldload(8) can then be used to load random_fortuna.ko
532 or random_yarrow.ko. Please note that due to the indirect
533 function calls that the loadable modules need to provide,
534 the build-in variants will be slightly more efficient.
536 The random(4) kernel option RANDOM_DUMMY has been retired due to
537 unpopularity. It was not all that useful anyway.
540 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
541 Control over building the ELF Tool Chain tools is now provided by
542 the WITHOUT_TOOLCHAIN knob.
545 The polarity of Pulse Per Second (PPS) capture events with the
546 uart(4) driver has been corrected. Prior to this change the PPS
547 "assert" event corresponded to the trailing edge of a positive PPS
548 pulse and the "clear" event was the leading edge of the next pulse.
550 As the width of a PPS pulse in a typical GPS receiver is on the
551 order of 1 millisecond, most users will not notice any significant
552 difference with this change.
554 Anyone who has compensated for the historical polarity reversal by
555 configuring a negative offset equal to the pulse width will need to
556 remove that workaround.
559 The default group assigned to /dev/dri entries has been changed
560 from 'wheel' to 'video' with the id of '44'. If you want to have
561 access to the dri devices please add yourself to the video group
564 # pw groupmod video -m $USER
567 The menu.rc and loader.rc files will now be replaced during
568 upgrades. Please migrate local changes to menu.rc.local and
569 loader.rc.local instead.
572 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
573 strings and strip have been removed. The src.conf(5) knob
574 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
577 As ZFS requires more kernel stack pages than is the default on some
578 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
579 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
581 Please consider using 'options KSTACK_PAGES=X' where X is greater
582 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
585 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
586 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
587 default, i.e., they will not contain "::". For example, instead
588 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
589 to have a more specific match, such as different map entries for
590 IPv6:0:0 vs IPv6:0. This change requires that configuration
591 data (including maps, files, classes, custom ruleset, etc.) must
592 use the same format, so make certain such configuration data is
593 upgrading. As a very simple check search for patterns like
594 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
595 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
596 the cf option UseCompressedIPv6Addresses.
599 The default kernel entropy-processing algorithm is now
600 Fortuna, replacing Yarrow.
602 Assuming you have 'device random' in your kernel config
603 file, the configurations allow a kernel option to override
604 this default. You may choose *ONE* of:
606 options RANDOM_YARROW # Legacy /dev/random algorithm.
607 options RANDOM_DUMMY # Blocking-only driver.
609 If you have neither, you get Fortuna. For most people,
610 read no further, Fortuna will give a /dev/random that works
611 like it always used to, and the difference will be irrelevant.
613 If you remove 'device random', you get *NO* kernel-processed
614 entropy at all. This may be acceptable to folks building
615 embedded systems, but has complications. Carry on reading,
616 and it is assumed you know what you need.
618 *PLEASE* read random(4) and random(9) if you are in the
619 habit of tweaking kernel configs, and/or if you are a member
620 of the embedded community, wanting specific and not-usual
621 behaviour from your security subsystems.
623 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
624 random', you will NOT have a functioning /dev/random, and
625 many cryptographic features will not work, including SSH.
626 You may also find strange behaviour from the random(3) set
627 of library functions, in particular sranddev(3), srandomdev(3)
628 and arc4random(3). The reason for this is that the KERN_ARND
629 sysctl only returns entropy if it thinks it has some to
630 share, and with RANDOM_DUMMY or no 'device random' this
634 An additional fix for the issue described in the 20150614 sendmail
635 entry below has been been committed in revision 284717.
638 FreeBSD's old make (fmake) has been removed from the system. It is
639 available as the devel/fmake port or via pkg install fmake.
642 The fix for the issue described in the 20150614 sendmail entry
643 below has been been committed in revision 284436. The work
644 around described in that entry is no longer needed unless the
645 default setting is overridden by a confDH_PARAMETERS configuration
646 setting of '5' or pointing to a 512 bit DH parameter file.
649 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
650 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
651 and devel/kyua to version 0.20+ and adjust any calling code to work
652 with Kyuafile and kyua.
655 The import of openssl to address the FreeBSD-SA-15:10.openssl
656 security advisory includes a change which rejects handshakes
657 with DH parameters below 768 bits. sendmail releases prior
658 to 8.15.2 (not yet released), defaulted to a 512 bit
659 DH parameter setting for client connections. To work around
660 this interoperability, sendmail can be configured to use a
661 2048 bit DH parameter by:
663 1. Edit /etc/mail/`hostname`.mc
664 2. If a setting for confDH_PARAMETERS does not exist or
665 exists and is set to a string beginning with '5',
667 3. If a setting for confDH_PARAMETERS exists and is set to
668 a file path, create a new file with:
669 openssl dhparam -out /path/to/file 2048
670 4. Rebuild the .cf file:
671 cd /etc/mail/; make; make install
673 cd /etc/mail/; make restart
675 A sendmail patch is coming, at which time this file will be
679 Generation of legacy formatted entries have been disabled by default
680 in pwd_mkdb(8), as all base system consumers of the legacy formatted
681 entries were converted to use the new format by default when the new,
682 machine independent format have been added and supported since FreeBSD
685 Please see the pwd_mkdb(8) manual page for further details.
688 Clang and llvm have been upgraded to 3.6.1 release. Please see the
689 20141231 entry below for information about prerequisites and upgrading,
690 if you are not already using 3.5.0 or higher.
693 TI platform code switched to using vendor DTS files and this update
694 may break existing systems running on Beaglebone, Beaglebone Black,
697 - dtb files should be regenerated/reinstalled. Filenames are the
698 same but content is different now
699 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
700 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
701 addressing scheme is now pin 25 on /dev/gpioc3.
702 - Pandaboard: /etc/ttys should be updated, serial console device is
703 now /dev/ttyu2, not /dev/ttyu0
706 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
707 If you need the GNU extension from groff soelim(1), install groff
708 from package: pkg install groff, or via ports: textproc/groff.
711 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
712 defined in symlink(7); previously symlinks were silently ignored.
715 The const qualifier has been removed from iconv(3) to comply with
716 POSIX. The ports tree is aware of this from r384038 onwards.
719 Libraries specified by LIBADD in Makefiles must have a corresponding
720 DPADD_<lib> variable to ensure correct dependencies. This is now
721 enforced in src.libnames.mk.
724 From legacy ata(4) driver was removed support for SATA controllers
725 supported by more functional drivers ahci(4), siis(4) and mvs(4).
726 Kernel modules ataahci and ataadaptec were removed completely,
727 replaced by ahci and mvs modules respectively.
730 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
731 the 20141231 entry below for information about prerequisites and
732 upgrading, if you are not already using 3.5.0 or higher.
735 The 32-bit PowerPC kernel has been changed to a position-independent
736 executable. This can only be booted with a version of loader(8)
737 newer than January 31, 2015, so make sure to update both world and
738 kernel before rebooting.
741 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
742 but before r278950, the RNG was not seeded properly. Immediately
743 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
744 ssh keys or openssl keys) that were generated w/ a kernel from that
745 range. This does not affect programs that directly used /dev/random
746 or /dev/urandom. All userland uses of arc4random(3) are affected.
749 The autofs(4) ABI was changed in order to restore binary compatibility
750 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
754 The powerpc64 kernel has been changed to a position-independent
755 executable. This can only be booted with a new version of loader(8),
756 so make sure to update both world and kernel before rebooting.
759 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
760 only release, no new features have been added. Please see the 20141231
761 entry below for information about prerequisites and upgrading, if you
762 are not already using 3.5.0.
765 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
766 taken from the ELF Tool Chain project rather than GNU binutils. They
767 should be drop-in replacements, with the addition of arm64 support.
768 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
769 binutils tools, if necessary. See 20150805 for updated information.
772 The default Unbound configuration now enables remote control
773 using a local socket. Users who have already enabled the
774 local_unbound service should regenerate their configuration
775 by running "service local_unbound setup" as root.
778 The GNU texinfo and GNU info pages have been removed.
779 To be able to view GNU info pages please install texinfo from ports.
782 Clang, llvm and lldb have been upgraded to 3.5.0 release.
784 As of this release, a prerequisite for building clang, llvm and lldb is
785 a C++11 capable compiler and C++11 standard library. This means that to
786 be able to successfully build the cross-tools stage of buildworld, with
787 clang as the bootstrap compiler, your system compiler or cross compiler
788 should either be clang 3.3 or later, or gcc 4.8 or later, and your
789 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
792 On any standard FreeBSD 10.x or 11.x installation, where clang and
793 libc++ are on by default (that is, on x86 or arm), this should work out
796 On 9.x installations where clang is enabled by default, e.g. on x86 and
797 powerpc, libc++ will not be enabled by default, so libc++ should be
798 built (with clang) and installed first. If both clang and libc++ are
799 missing, build clang first, then use it to build libc++.
801 On 8.x and earlier installations, upgrade to 9.x first, and then follow
802 the instructions for 9.x above.
804 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
805 default, and do not build clang.
807 Many embedded systems are resource constrained, and will not be able to
808 build clang in a reasonable time, or in some cases at all. In those
809 cases, cross building bootable systems on amd64 is a workaround.
811 This new version of clang introduces a number of new warnings, of which
812 the following are most likely to appear:
816 This warns in two cases, for both C and C++:
817 * When the code is trying to take the absolute value of an unsigned
818 quantity, which is effectively a no-op, and almost never what was
819 intended. The code should be fixed, if at all possible. If you are
820 sure that the unsigned quantity can be safely cast to signed, without
821 loss of information or undefined behavior, you can add an explicit
822 cast, or disable the warning.
824 * When the code is trying to take an absolute value, but the called
825 abs() variant is for the wrong type, which can lead to truncation.
826 If you want to disable the warning instead of fixing the code, please
827 make sure that truncation will not occur, or it might lead to unwanted
830 -Wtautological-undefined-compare and
831 -Wundefined-bool-conversion
833 These warn when C++ code is trying to compare 'this' against NULL, while
834 'this' should never be NULL in well-defined C++ code. However, there is
835 some legacy (pre C++11) code out there, which actively abuses this
836 feature, which was less strictly defined in previous C++ versions.
838 Squid and openjdk do this, for example. The warning can be turned off
839 for C++98 and earlier, but compiling the code in C++11 mode might result
840 in unexpected behavior; for example, the parts of the program that are
841 unreachable could be optimized away.
844 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
845 kernel sources have been removed. The .h files remain, since some
846 utilities include them. This will need to be fixed later.
847 If "mount -t oldnfs ..." is attempted, it will fail.
848 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
849 the utilities will report errors.
852 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
853 directories to top level SUBDIR variable when their parent
854 directory is included in LOCAL_DIRS. Users with build systems with
855 such hierarchies and without SUBDIR entries in the parent
856 directory Makefiles should add them or add the directories to
860 faith(4) and faithd(8) have been removed from the base system. Faith
861 has been obsolete for a very long time.
864 vt(4), the new console driver, is enabled by default. It brings
865 support for Unicode and double-width characters, as well as
866 support for UEFI and integration with the KMS kernel video
869 You may need to update your console settings in /etc/rc.conf,
870 most probably the keymap. During boot, /etc/rc.d/syscons will
871 indicate what you need to do.
873 vt(4) still has issues and lacks some features compared to
874 syscons(4). See the wiki for up-to-date information:
875 https://wiki.freebsd.org/Newcons
877 If you want to keep using syscons(4), you can do so by adding
878 the following line to /boot/loader.conf:
882 pjdfstest has been integrated into kyua as an opt-in test suite.
883 Please see share/doc/pjdfstest/README for more details on how to
887 gperf has been removed from the base system for architectures
888 that use clang. Ports that require gperf will obtain it from the
892 pjdfstest has been moved from tools/regression/pjdfstest to
896 At svn r271982, The default linux compat kernel ABI has been adjusted
897 to 2.6.18 in support of the linux-c6 compat ports infrastructure
898 update. If you wish to continue using the linux-f10 compat ports,
899 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
900 encouraged to update their linux-compat packages to linux-c6 during
901 their next update cycle.
904 The ofwfb driver, used to provide a graphics console on PowerPC when
905 using vt(4), no longer allows mmap() of all physical memory. This
906 will prevent Xorg on PowerPC with some ATI graphics cards from
907 initializing properly unless x11-servers/xorg-server is updated to
911 The xdev targets have been converted to using TARGET and
912 TARGET_ARCH instead of XDEV and XDEV_ARCH.
915 The default unbound configuration has been modified to address
916 issues with reverse lookups on networks that use private
917 address ranges. If you use the local_unbound service, run
918 "service local_unbound setup" as root to regenerate your
919 configuration, then "service local_unbound reload" to load the
923 The GNU texinfo and GNU info pages are not built and installed
924 anymore, WITH_INFO knob has been added to allow to built and install
926 UPDATE: see 20150102 entry on texinfo's removal
929 The GNU readline library is now an INTERNALLIB - that is, it is
930 statically linked into consumers (GDB and variants) in the base
931 system, and the shared library is no longer installed. The
932 devel/readline port is available for third party software that
936 The Itanium architecture (ia64) has been removed from the list of
937 known architectures. This is the first step in the removal of the
941 Commit r268115 has added NFSv4.1 server support, merged from
942 projects/nfsv4.1-server. Since this includes changes to the
943 internal interfaces between the NFS related modules, a full
944 build of the kernel and modules will be necessary.
945 __FreeBSD_version has been bumped.
948 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
949 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
950 which differs from the behaviour controlled by this knob.)
953 Maximal length of the serial number in CTL was increased from 16 to
954 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
955 and ctld, need to be rebuilt to work with a new kernel.
958 The libatf-c and libatf-c++ major versions were downgraded to 0 and
959 1 respectively to match the upstream numbers. They were out of
960 sync because, when they were originally added to FreeBSD, the
961 upstream versions were not respected. These libraries are private
962 and not yet built by default, so renumbering them should be a
963 non-issue. However, unclean source trees will yield broken test
964 programs once the operator executes "make delete-old-libs" after a
967 Additionally, the atf-sh binary was made private by moving it into
968 /usr/libexec/. Already-built shell test programs will keep the
969 path to the old binary so they will break after "make delete-old"
972 If you are using WITH_TESTS=yes (not the default), wipe the object
973 tree and rebuild from scratch to prevent spurious test failures.
974 This is only needed once: the misnumbered libraries and misplaced
975 binaries have been added to OptionalObsoleteFiles.inc so they will
976 be removed during a clean upgrade.
979 Clang and llvm have been upgraded to 3.4.1 release.
982 We bogusly installed src.opts.mk in /usr/share/mk. This file should
983 be removed to avoid issues in the future (and has been added to
987 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
988 past, it affected all builds that used the bsd.*.mk files. The old
989 behavior was a bug, but people may have relied upon it. To get this
990 behavior back, you can .include /etc/src.conf from /etc/make.conf
991 (which is still global and isn't changed). This also changes the
992 behavior of incremental builds inside the tree of individual
993 directories. Set MAKESYSPATH to ".../share/mk" to do that.
994 Although this has survived make universe and some upgrade scenarios,
995 other upgrade scenarios may have broken. At least one form of
996 temporary breakage was fixed with MAKESYSPATH settings for buildworld
997 as well... In cases where MAKESYSPATH isn't working with this
998 setting, you'll need to set it to the full path to your tree.
1000 One side effect of all this cleaning up is that bsd.compiler.mk
1001 is no longer implicitly included by bsd.own.mk. If you wish to
1002 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1006 The lindev device has been removed since /dev/full has been made a
1007 standard device. __FreeBSD_version has been bumped.
1010 The knob WITHOUT_VI was added to the base system, which controls
1011 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1012 in order to reorder files share/termcap and didn't build ex(1) as a
1013 build tool, so building/installing with WITH_VI is highly advised for
1014 build hosts for older releases.
1016 This issue has been fixed in stable/9 and stable/10 in r277022 and
1017 r276991, respectively.
1020 The YES_HESIOD knob has been removed. It has been obsolete for
1021 a decade. Please move to using WITH_HESIOD instead or your builds
1022 will silently lack HESIOD.
1025 The uart(4) driver has been changed with respect to its handling
1026 of the low-level console. Previously the uart(4) driver prevented
1027 any process from changing the baudrate or the CLOCAL and HUPCL
1028 control flags. By removing the restrictions, operators can make
1029 changes to the serial console port without having to reboot.
1030 However, when getty(8) is started on the serial device that is
1031 associated with the low-level console, a misconfigured terminal
1032 line in /etc/ttys will now have a real impact.
1033 Before upgrading the kernel, make sure that /etc/ttys has the
1034 serial console device configured as 3wire without baudrate to
1035 preserve the previous behaviour. E.g:
1036 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1039 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1040 to improve performance. To re-enable it, if needed, run rpcbind
1041 with command line option -W.
1044 Switched back to the GPL dtc compiler due to updates in the upstream
1045 dts files not being supported by the BSDL dtc compiler. You will need
1046 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1047 may result while building dtb files during a kernel build if you fail
1048 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1051 Clang and llvm have been upgraded to 3.4 release.
1054 The nve(4) driver has been removed. Please use the nfe(4) driver
1055 for NVIDIA nForce MCP Ethernet adapters instead.
1058 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1059 This could cause certain C++ applications using shared libraries built
1060 against the previous version of libc++ to crash. The incompatibility
1061 has now been fixed, but any C++ applications or shared libraries built
1062 between r261283 and r261801 should be recompiled.
1065 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1066 capability mode support. Please note that enabling the feature in
1067 kernel is still highly recommended.
1070 OpenSSH is now built with sandbox support, and will use sandbox as
1071 the default privilege separation method. This requires Capsicum
1072 capability mode support in kernel.
1075 The libelf and libdwarf libraries have been updated to newer
1076 versions from upstream. Shared library version numbers for
1077 these two libraries were bumped. Any ports or binaries
1078 requiring these two libraries should be recompiled.
1079 __FreeBSD_version is bumped to 1100006.
1082 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1083 instead of providing an explicit one, this would prevent such
1084 Makefile from providing its own Kyuafile in the future during
1085 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1086 intervention is needed to clean an objdir if you use NO_CLEAN:
1087 # find /usr/obj -name Kyuafile | xargs rm -f
1090 The behavior of gss_pseudo_random() for the krb5 mechanism
1091 has changed, for applications requesting a longer random string
1092 than produced by the underlying enctype's pseudo-random() function.
1093 In particular, the random string produced from a session key of
1094 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1095 be different at the 17th octet and later, after this change.
1096 The counter used in the PRF+ construction is now encoded as a
1097 big-endian integer in accordance with RFC 4402.
1098 __FreeBSD_version is bumped to 1100004.
1101 The WITHOUT_ATF build knob has been removed and its functionality
1102 has been subsumed into the more generic WITHOUT_TESTS. If you were
1103 using the former to disable the build of the ATF libraries, you
1104 should change your settings to use the latter.
1107 The default version of mtree is nmtree which is obtained from
1108 NetBSD. The output is generally the same, but may vary
1109 slightly. If you found you need identical output adding
1110 "-F freebsd9" to the command line should do the trick. For the
1111 time being, the old mtree is available as fmtree.
1114 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1115 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1116 1.1.4_8 and verify bsdyml not linked in, before running "make
1118 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1120 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1123 The stable/10 branch has been created in subversion from head
1127 The rc.d/jail script has been updated to support jail(8)
1128 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1129 for per-jail configuration are automatically converted to
1130 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1131 This is transparently backward compatible. See below about some
1132 incompatibilities and rc.conf(5) manual page for more details.
1134 These variables are now deprecated in favor of jail(8) configuration
1135 file. One can use "rc.d/jail config <jname>" command to generate
1136 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1137 running the jail(8) utility. The default pathname of the
1138 configuration file is /etc/jail.conf and can be specified by
1139 using $jail_conf or $jail_<jname>_conf variables.
1141 Please note that jail_devfs_ruleset accepts an integer at
1142 this moment. Please consider to rewrite the ruleset name
1146 BIND has been removed from the base system. If all you need
1147 is a local resolver, simply enable and start the local_unbound
1148 service instead. Otherwise, several versions of BIND are
1149 available in the ports tree. The dns/bind99 port is one example.
1151 With this change, nslookup(1) and dig(1) are no longer in the base
1152 system. Users should instead use host(1) and drill(1) which are
1153 in the base system. Alternatively, nslookup and dig can
1154 be obtained by installing the dns/bind-tools port.
1157 With the addition of unbound(8), a new unbound user is now
1158 required during installworld. "mergemaster -p" can be used to
1159 add the user prior to installworld, as documented in the handbook.
1162 OpenSSH is now built with DNSSEC support, and will by default
1163 silently trust signed SSHFP records. This can be controlled with
1164 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1165 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1168 The GNU Compiler Collection and C++ standard library (libstdc++)
1169 are no longer built by default on platforms where clang is the system
1170 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1171 options in src.conf.
1174 The PROCDESC kernel option is now part of the GENERIC kernel
1175 configuration and is required for the rwhod(8) to work.
1176 If you are using custom kernel configuration, you should include
1180 The API and ABI related to the Capsicum framework was modified
1181 in backward incompatible way. The userland libraries and programs
1182 have to be recompiled to work with the new kernel. This includes the
1183 following libraries and programs, but the whole buildworld is
1184 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1185 kdump, procstat, rwho, rwhod, uniq.
1188 AES-NI intrinsic support has been added to gcc. The AES-NI module
1189 has been updated to use this support. A new gcc is required to build
1190 the aesni module on both i386 and amd64.
1193 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1194 Thus "device padlock_rng" and "device rdrand_rng" should be
1195 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1198 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1199 enables just the iconv* functionality and is now on by default.
1200 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1201 compatibility. Set WITHOUT_ICONV to build the old way.
1202 If you have been using WITH_ICONV before, you will very likely
1203 need to turn on WITH_LIBICONV_COMPAT.
1206 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1207 Illumos origin, including ZFS. If you have INVARIANTS in your
1208 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1210 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1211 locks if WITNESS option was set. Because that generated a lot of
1212 witness(9) reports and all of them were believed to be false
1213 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1214 can be used to achieve the previous behavior.
1217 Timer values in IPv6 data structures now use time_uptime instead
1218 of time_second. Although this is not a user-visible functional
1219 change, userland utilities which directly use them---ndp(8),
1220 rtadvd(8), and rtsold(8) in the base system---need to be updated
1221 to r253970 or later.
1224 find -delete can now delete the pathnames given as arguments,
1225 instead of only files found below them or if the pathname did
1226 not contain any slashes. Formerly, the following error message
1229 find: -delete: <path>: relative path potentially not safe
1231 Deleting the pathnames given as arguments can be prevented
1232 without error messages using -mindepth 1 or by changing
1233 directory and passing "." as argument to find. This works in the
1234 old as well as the new version of find.
1237 Behavior of devfs rules path matching has been changed.
1238 Pattern is now always matched against fully qualified devfs
1239 path and slash characters must be explicitly matched by
1240 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1241 subdirectories must be reviewed.
1244 The default ARM ABI has changed to the ARM EABI. The old ABI is
1245 incompatible with the ARM EABI and all programs and modules will
1246 need to be rebuilt to work with a new kernel.
1248 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1250 NOTE: Support for the old ABI will be removed in the future and
1251 users are advised to upgrade.
1254 pkg_install has been disconnected from the build if you really need it
1255 you should add WITH_PKGTOOLS in your src.conf(5).
1258 Most of network statistics structures were changed to be able
1259 keep 64-bits counters. Thus all tools, that work with networking
1260 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1263 Fix a bug that allowed a tracing process (e.g. gdb) to write
1264 to a memory-mapped file in the traced process's address space
1265 even if neither the traced process nor the tracing process had
1266 write access to that file.
1269 CVS has been removed from the base system. An exact copy
1270 of the code is available from the devel/cvs port.
1273 Some people report the following error after the switch to bmake:
1275 make: illegal option -- J
1276 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1278 *** [buildworld] Error code 2
1280 this likely due to an old instance of make in
1281 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1282 which src/Makefile will use that blindly, if it exists, so if
1283 you see the above error:
1285 rm -rf `make -V MAKEPATH`
1290 Use bmake by default.
1291 Whereas before one could choose to build with bmake via
1292 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1293 make. The goal is to remove these knobs for 10-RELEASE.
1295 It is worth noting that bmake (like gmake) treats the command
1296 line as the unit of failure, rather than statements within the
1297 command line. Thus '(cd some/where && dosomething)' is safer
1298 than 'cd some/where; dosomething'. The '()' allows consistent
1299 behavior in parallel build.
1302 Fix a bug that allows NFS clients to issue READDIR on files.
1305 The WITHOUT_IDEA option has been removed because
1306 the IDEA patent expired.
1309 The sysctl which controls TRIM support under ZFS has been renamed
1310 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1314 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1315 rather than creating it's own in the temporary directory in
1316 order allow access to bootstrapped versions of tools such as
1317 install and mtree. When upgrading from version of FreeBSD where
1318 the install command does not support -l, you will need to
1319 install a new mergemaster command if mergemaster -p is required.
1320 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1324 Legacy ATA stack, disabled and replaced by new CAM-based one since
1325 FreeBSD 9.0, completely removed from the sources. Kernel modules
1326 atadisk and atapi*, user-level tools atacontrol and burncd are
1327 removed. Kernel option `options ATA_CAM` is now permanently enabled
1331 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1332 and socketpair(2). Software, in particular Kerberos, may
1333 automatically detect and use these during building. The resulting
1334 binaries will not work on older kernels.
1337 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1338 information, see the respective 20130304 entry).
1341 Recent commits to callout(9) changed the size of struct callout,
1342 so the KBI is probably heavily disturbed. Also, some functions
1343 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1344 by macros. Every kernel module using it won't load, so rebuild
1347 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1348 but does not initialize by default (because of the new CTL_DISABLE
1349 option) to save memory. To re-enable it, remove the CTL_DISABLE
1350 option from the kernel config file or set kern.cam.ctl.disable=0
1351 in /boot/loader.conf.
1354 The ctl device has been disabled in GENERIC for i386 and amd64.
1355 This was done due to the extra memory being allocated at system
1356 initialisation time by the ctl driver which was only used if
1357 a CAM target device was created. This makes a FreeBSD system
1358 unusable on 128MB or less of RAM.
1361 A new compression method (lz4) has been merged to -HEAD. Please
1362 refer to zpool-features(7) for more information.
1364 Please refer to the "ZFS notes" section of this file for information
1365 on upgrading boot ZFS pools.
1368 A BSD-licensed patch(1) variant has been added and is installed
1369 as bsdpatch, being the GNU version the default patch.
1370 To inverse the logic and use the BSD-licensed one as default,
1371 while having the GNU version installed as gnupatch, rebuild
1372 and install world with the WITH_BSD_PATCH knob set.
1375 Due to the use of the new -l option to install(1) during build
1376 and install, you must take care not to directly set the INSTALL
1377 make variable in your /etc/make.conf, /etc/src.conf, or on the
1378 command line. If you wish to use the -C flag for all installs
1379 you may be able to add INSTALL+=-C to /etc/make.conf or
1383 The install(1) option -M has changed meaning and now takes an
1384 argument that is a file or path to append logs to. In the
1385 unlikely event that -M was the last option on the command line
1386 and the command line contained at least two files and a target
1387 directory the first file will have logs appended to it. The -M
1388 option served little practical purpose in the last decade so its
1389 use is expected to be extremely rare.
1392 After switching to Clang as the default compiler some users of ZFS
1393 on i386 systems started to experience stack overflow kernel panics.
1394 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1397 GEOM_LABEL now mangles label names read from file system metadata.
1398 Mangling affect labels containing spaces, non-printable characters,
1399 '%' or '"'. Device names in /etc/fstab and other places may need to
1403 By default, only the 10 most recent kernel dumps will be saved. To
1404 restore the previous behaviour (no limit on the number of kernel dumps
1405 stored in the dump directory) add the following line to /etc/rc.conf:
1410 With the addition of auditdistd(8), a new auditdistd user is now
1411 required during installworld. "mergemaster -p" can be used to
1412 add the user prior to installworld, as documented in the handbook.
1415 The sin6_scope_id member variable in struct sockaddr_in6 is now
1416 filled by the kernel before passing the structure to the userland via
1417 sysctl or routing socket. This means the KAME-specific embedded scope
1418 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1419 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1420 __FreeBSD_version is bumped to 1000025.
1423 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1424 This means that the world and kernel will be compiled with clang
1425 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1426 and /usr/bin/cpp. To disable this behavior and revert to building
1427 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1428 of current may need to bootstrap WITHOUT_CLANG first if the clang
1429 build fails (its compatibility window doesn't extend to the 9 stable
1433 The IPFIREWALL_FORWARD kernel option has been removed. Its
1434 functionality now turned on by default.
1437 The ZERO_COPY_SOCKET kernel option has been removed and
1438 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1439 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1440 mechanism which is not safe and may result in kernel crashes.
1441 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1442 driver supports disposeable external page sized mbuf storage.
1443 Proper replacements for both zero-copy mechanisms are under
1444 consideration and will eventually lead to complete removal
1445 of the two kernel options.
1448 The IPv4 network stack has been converted to network byte
1449 order. The following modules need to be recompiled together
1450 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1451 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1454 Support for non-MPSAFE filesystems was removed from VFS. The
1455 VFS_VERSION was bumped, all filesystem modules shall be
1459 All the non-MPSAFE filesystems have been disconnected from
1460 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1461 portalfs, smbfs, xfs.
1464 The interface cloning API and ABI has changed. The following
1465 modules need to be recompiled together with kernel:
1466 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1467 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1468 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1471 The sdhci driver was split in two parts: sdhci (generic SD Host
1472 Controller logic) and sdhci_pci (actual hardware driver).
1473 No kernel config modifications are required, but if you
1474 load sdhc as a module you must switch to sdhci_pci instead.
1477 Import the FUSE kernel and userland support into base system.
1480 The GNU sort(1) program has been removed since the BSD-licensed
1481 sort(1) has been the default for quite some time and no serious
1482 problems have been reported. The corresponding WITH_GNU_SORT
1486 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1487 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1491 The net80211(4) ABI has been changed to allow for improved driver
1492 PS-POLL and power-save support. All wireless drivers need to be
1493 recompiled to work with the new kernel.
1496 The random(4) support for the VIA hardware random number
1497 generator (`PADLOCK') is no longer enabled unconditionally.
1498 Add the padlock_rng device in the custom kernel config if
1499 needed. The GENERIC kernels on i386 and amd64 do include the
1500 device, so the change only affects the custom kernel
1504 The pf(4) packet filter ABI has been changed. pfctl(8) and
1505 snmp_pf module need to be recompiled to work with new kernel.
1508 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1509 to -HEAD. Pools that have empty_bpobj in active state can not be
1510 imported read-write with ZFS implementations that do not support
1511 this feature. For more information read the zpool-features(5)
1515 The sparc64 ZFS loader has been changed to no longer try to auto-
1516 detect ZFS providers based on diskN aliases but now requires these
1517 to be explicitly listed in the OFW boot-device environment variable.
1520 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1521 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1522 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1525 The following sysctls and tunables have been renamed for consistency
1526 with other variables:
1527 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1528 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1531 The sort utility has been replaced with BSD sort. For now, GNU sort
1532 is also available as "gnusort" or the default can be set back to
1533 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1534 installed as "bsdsort".
1537 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1538 Starting with this version the old system of ZFS pool versioning
1539 is superseded by "feature flags". This concept enables forward
1540 compatibility against certain future changes in functionality of ZFS
1541 pools. The first read-only compatible "feature flag" for ZFS pools
1542 is named "com.delphix:async_destroy". For more information
1543 read the new zpool-features(5) manual page.
1544 Please refer to the "ZFS notes" section of this file for information
1545 on upgrading boot ZFS pools.
1548 The malloc(3) implementation embedded in libc now uses sources imported
1549 as contrib/jemalloc. The most disruptive API change is to
1550 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1551 delete it prior to installworld, and optionally re-create it using the
1552 new format after rebooting. See malloc.conf(5) for details
1553 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1557 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1558 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1559 now spelled mips. This is to aid compatibility with third-party
1560 software that expects this naming scheme in uname(3). Little-endian
1561 settings are unchanged. If you are updating a big-endian mips64 machine
1562 from before this change, you may need to set MACHINE_ARCH=mips64 in
1563 your environment before the new build system will recognize your machine.
1566 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1570 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1571 nullfs(5) did not pass through all behaviours to the underlying layer,
1572 as a result if we bound to a socket on the lower layer we could connect
1573 only to the lower path; if we bound to the upper layer we could connect
1574 only to the upper path. The new behavior is one can connect to both the
1575 lower and the upper paths regardless what layer path one binds to.
1578 The getifaddrs upgrade path broken with 20111215 has been restored.
1579 If you have upgraded in between 20111215 and 20120209 you need to
1580 recompile libc again with your kernel. You still need to recompile
1581 world to be able to configure CARP but this restriction already
1582 comes from 20111215.
1585 The set_rcvar() function has been removed from /etc/rc.subr. All
1586 base and ports rc.d scripts have been updated, so if you have a
1587 port installed with a script in /usr/local/etc/rc.d you can either
1588 hand-edit the rcvar= line, or reinstall the port.
1590 An easy way to handle the mass-update of /etc/rc.d:
1591 rm /etc/rc.d/* && mergemaster -i
1594 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1595 on the current CPU and prevents other threads from running.
1596 This behavior can be reverted using the kern.stop_scheduler_on_panic
1598 The new behavior can be incompatible with kern.sync_on_panic.
1601 The carp(4) facility has been changed significantly. Configuration
1602 of the CARP protocol via ifconfig(8) has changed, as well as format
1603 of CARP events submitted to devd(8) has changed. See manual pages
1604 for more information. The arpbalance feature of carp(4) is currently
1605 not supported anymore.
1607 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1608 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1609 need to be recompiled.
1612 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1616 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1617 explicitely support non-MPSAFE filesystems.
1618 It is on by default for all supported platform at this present
1622 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1623 i386 and pc98 GENERIC kernel configuration files.
1626 sysinstall has been removed
1629 The stable/9 branch created in subversion. This corresponds to the
1630 RELENG_9 branch in CVS.
1636 Avoid using make -j when upgrading. While generally safe, there are
1637 sometimes problems using -j to upgrade. If your upgrade fails with
1638 -j, please try again without -j. From time to time in the past there
1639 have been problems using -j with buildworld and/or installworld. This
1640 is especially true when upgrading between "distant" versions (eg one
1641 that cross a major release boundary or several minor releases, or when
1642 several months have passed on the -current branch).
1644 Sometimes, obscure build problems are the result of environment
1645 poisoning. This can happen because the make utility reads its
1646 environment when searching for values for global variables. To run
1647 your build attempts in an "environmental clean room", prefix all make
1648 commands with 'env -i '. See the env(1) manual page for more details.
1650 When upgrading from one major version to another it is generally best
1651 to upgrade to the latest code in the currently installed branch first,
1652 then do an upgrade to the new branch. This is the best-tested upgrade
1653 path, and has the highest probability of being successful. Please try
1654 this approach before reporting problems with a major version upgrade.
1656 When upgrading a live system, having a root shell around before
1657 installing anything can help undo problems. Not having a root shell
1658 around can lead to problems if pam has changed too much from your
1659 starting point to allow continued authentication after the upgrade.
1661 This file should be read as a log of events. When a later event changes
1662 information of a prior event, the prior event should not be deleted.
1663 Instead, a pointer to the entry with the new information should be
1664 placed in the old entry. Readers of this file should also sanity check
1665 older entries before relying on them blindly. Authors of new entries
1666 should write them with this in mind.
1670 When upgrading the boot ZFS pool to a new version, always follow
1673 1.) recompile and reinstall the ZFS boot loader and boot block
1674 (this is part of "make buildworld" and "make installworld")
1676 2.) update the ZFS boot block on your boot drive
1678 The following example updates the ZFS boot block on the first
1679 partition (freebsd-boot) of a GPT partitioned drive ada0:
1680 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1682 Non-boot pools do not need these updates.
1686 If you are updating from a prior version of FreeBSD (even one just
1687 a few days old), you should follow this procedure. It is the most
1688 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1690 make kernel-toolchain
1691 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1692 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1694 To test a kernel once
1695 ---------------------
1696 If you just want to boot a kernel once (because you are not sure
1697 if it works, or if you want to boot a known bad kernel to provide
1698 debugging information) run
1699 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1700 nextboot -k testkernel
1702 To just build a kernel when you know that it won't mess you up
1703 --------------------------------------------------------------
1704 This assumes you are already running a CURRENT system. Replace
1705 ${arch} with the architecture of your machine (e.g. "i386",
1706 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1708 cd src/sys/${arch}/conf
1709 config KERNEL_NAME_HERE
1710 cd ../compile/KERNEL_NAME_HERE
1715 If this fails, go to the "To build a kernel" section.
1717 To rebuild everything and install it on the current system.
1718 -----------------------------------------------------------
1719 # Note: sometimes if you are running current you gotta do more than
1720 # is listed here if you are upgrading from a really old current.
1722 <make sure you have good level 0 dumps>
1724 make kernel KERNCONF=YOUR_KERNEL_HERE
1726 <reboot in single user> [3]
1733 To cross-install current onto a separate partition
1734 --------------------------------------------------
1735 # In this approach we use a separate partition to hold
1736 # current's root, 'usr', and 'var' directories. A partition
1737 # holding "/", "/usr" and "/var" should be about 2GB in
1740 <make sure you have good level 0 dumps>
1743 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1744 <maybe newfs current's root partition>
1745 <mount current's root partition on directory ${CURRENT_ROOT}>
1746 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1747 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1748 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1749 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1750 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1751 <reboot into current>
1752 <do a "native" rebuild/install as described in the previous section>
1753 <maybe install compatibility libraries from ports/misc/compat*>
1757 To upgrade in-place from stable to current
1758 ----------------------------------------------
1759 <make sure you have good level 0 dumps>
1761 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1763 <reboot in single user> [3]
1770 Make sure that you've read the UPDATING file to understand the
1771 tweaks to various things you need. At this point in the life
1772 cycle of current, things change often and you are on your own
1773 to cope. The defaults can also change, so please read ALL of
1774 the UPDATING entries.
1776 Also, if you are tracking -current, you must be subscribed to
1777 freebsd-current@freebsd.org. Make sure that before you update
1778 your sources that you have read and understood all the recent
1779 messages there. If in doubt, please track -stable which has
1780 much fewer pitfalls.
1782 [1] If you have third party modules, such as vmware, you
1783 should disable them at this point so they don't crash your
1786 [3] From the bootblocks, boot -s, and then do
1791 adjkerntz -i # if CMOS is wall time
1792 Also, when doing a major release upgrade, it is required that
1793 you boot into single user mode to do the installworld.
1795 [4] Note: This step is non-optional. Failure to do this step
1796 can result in a significant reduction in the functionality of the
1797 system. Attempting to do it by hand is not recommended and those
1798 that pursue this avenue should read this file carefully, as well
1799 as the archives of freebsd-current and freebsd-hackers mailing lists
1800 for potential gotchas. The -U option is also useful to consider.
1801 See mergemaster(8) for more information.
1803 [5] Usually this step is a noop. However, from time to time
1804 you may need to do this if you get unknown user in the following
1805 step. It never hurts to do it all the time. You may need to
1806 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1807 install) after the buildworld before this step if you last updated
1808 from current before 20130425 or from -stable before 20130430.
1810 [6] This only deletes old files and directories. Old libraries
1811 can be deleted by "make delete-old-libs", but you have to make
1812 sure that no program is using those libraries anymore.
1814 [8] The new kernel must be able to run existing binaries used by
1815 an installworld. When upgrading across major versions, the new
1816 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1817 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1818 binaries). Failure to do so may leave you with a system that is
1819 hard to boot to recover. A GENERIC kernel will include suitable
1820 compatibility options to run binaries from older branches.
1822 Make sure that you merge any new devices from GENERIC since the
1823 last time you updated your kernel config file.
1825 [9] When checking out sources, you must include the -P flag to have
1826 cvs prune empty directories.
1828 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1829 "?=" instead of the "=" assignment operator, so that buildworld can
1830 override the CPUTYPE if it needs to.
1832 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1833 not on the command line, or in /etc/make.conf. buildworld will
1834 warn if it is improperly defined.
1837 This file contains a list, in reverse chronological order, of major
1838 breakages in tracking -current. It is not guaranteed to be a complete
1839 list of such breakages, and only contains entries since September 23, 2011.
1840 If you need to see UPDATING entries from before that date, you will need
1841 to fetch an UPDATING file from an older FreeBSD release.
1843 Copyright information:
1845 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1847 Redistribution, publication, translation and use, with or without
1848 modification, in full or in part, in any form or format of this
1849 document are permitted without further permission from the author.
1851 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1852 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1853 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1854 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1855 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1856 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1857 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1858 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1859 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1860 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1861 POSSIBILITY OF SUCH DAMAGE.
1863 Contact Warner Losh if you have any questions about your use of