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/updating-src.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 NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
20 FreeBSD 12.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 ****************************** SPECIAL WARNING: ******************************
37 Due to a bug in some versions of clang that's very hard to workaround in
38 the upgrade process, to upgrade to -current you must first upgrade
39 either stable/9 after r286035 or stable/10 after r286033 (including
40 10.3-RELEASE) or current after r286007 (including stable/11 and
41 11.0-RELEASE). These revisions post-date the 10.2 and 9.3 releases, so
42 you'll need to take the unusual step of upgrading to the tip of the
43 stable branch before moving to 11 or -current via a source upgrade.
44 stable/11 and 11.0-RELEASE have working newer compiler. This differs
45 from the historical situation where one could upgrade from anywhere on
46 the last couple of stable branches, so be careful.
48 If you're running a hybrid system on 9.x or 10.x with an updated clang
49 compiler or are using an supported external toolchain, the build system
50 will allow the upgrade. Otherwise it will print a reminder.
52 ****************************** SPECIAL WARNING: ******************************
55 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
56 Please see the 20141231 entry below for information about prerequisites
57 and upgrading, if you are not already using clang 3.5.0 or higher.
60 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
61 smaller runtime footprint builds. This is useful for embedded systems
62 which only require one chipset support.
64 If you load it as a module, make sure this is in /boot/loader.conf:
68 This will load the HAL, all chip/RF backends and if_ath_pci.
69 If you have if_ath_pci in /boot/loader.conf, ensure it is after
70 if_ath or it will not load any HAL chipset support.
72 If you want to selectively load things (eg on ye cheape ARM/MIPS
73 platforms where RAM is at a premium) you should:
76 * load the chip modules in question
77 * load ath_rate, ath_dfs
79 * load if_ath_pci and/or if_ath_ahb depending upon your particular
80 bus bind type - this is where probe/attach is done.
82 For further comments/feedback, poke adrian@ .
85 The "ino64" 64-bit inode project has been committed, which extends
86 a number of types to 64 bits. Upgrading in place requires care and
87 adherence to the documented upgrade procedure.
89 If using a custom kernel configuration ensure that the
90 COMPAT_FREEBSD11 option is included (as during the upgrade the
91 system will be running the ino64 kernel with the existing world).
93 For the safest in-place upgrade begin by removing previous build
94 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
95 full procedure documented below under the heading "To rebuild
96 everything and install it on the current system." Specifically,
97 a reboot is required after installing the new kernel before
101 The NATM framework including the en(4), fatm(4), hatm(4), and
102 patm(4) devices has been removed. Consumers should plan a
103 migration before the end-of-life date for FreeBSD 11.
106 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
107 diff has not been implemented, if those are needed a newer version of
108 GNU diff is available via the diffutils package under the gdiff name.
111 As of r316810 for ipfilter, keep frags is no longer assumed when
112 keep state is specified in a rule. r316810 aligns ipfilter with
113 documentation in man pages separating keep frags from keep state.
114 This allows keep state to be specified without forcing keep frags
115 and allows keep frags to be specified independently of keep state.
116 To maintain previous behaviour, also specify keep frags with
117 keep state (as documented in ipf.conf.5).
120 arm64 builds now use the base system LLD 4.0.0 linker by default,
121 instead of requiring that the aarch64-binutils port or package be
122 installed. To continue using aarch64-binutils, set
123 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
126 The UDP optimization in entry 20160818 that added the sysctl
127 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
128 packets will no longer be treated as L3 broadcast packets.
131 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
132 use any explicitly assigned loopback address available in the jail
133 instead of using the first assigned address of the jail.
136 The ctl.ko module no longer implements the iSCSI target frontend:
137 cfiscsi.ko does instead.
139 If building cfiscsi.ko as a kernel module, the module can be loaded
140 via one of the following methods:
141 - `cfiscsi_load="YES"` in loader.conf(5).
142 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
143 - ctladm(8)/ctld(8), when compiled with iSCSI support
144 (`WITH_ISCSI=yes` in src.conf(5))
146 Please see cfiscsi(4) for more details.
149 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
150 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
151 same source (previously, the dependency of mmcsd.ko on mmc.ko was
152 missing, but mmcsd.ko now will refuse to load if it is incompatible
156 The syntax of ipfw(8) named states was changed to avoid ambiguity.
157 If you have used named states in the firewall rules, you need to modify
158 them after installworld and before rebooting. Now named states must
159 be prefixed with colon.
162 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
163 removed as the userland we provide cannot use them. The KMS version
164 (sys/dev/drm2) supports the same hardware.
167 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
168 Please see the 20141231 entry below for information about prerequisites
169 and upgrading, if you are not already using clang 3.5.0 or higher.
172 The code that provides support for ZFS .zfs/ directory functionality
173 has been reimplemented. It's not possible now to create a snapshot
174 by mkdir under .zfs/snapshot/. That should be the only user visible
178 EISA bus support has been removed. The WITH_EISA option is no longer
182 MCA bus support has been removed.
185 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
186 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
189 The EM_MULTIQUEUE kernel configuration option is deprecated now that
190 the em(4) driver conforms to iflib specifications.
193 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
194 IFLIB. If you have a custom kernel configuration that excludes em(4)
195 but you use igb(4), you need to re-add em(4) to your custom configuration.
198 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
199 Please see the 20141231 entry below for information about prerequisites
200 and upgrading, if you are not already using clang 3.5.0 or higher.
203 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
204 Please see the 20141231 entry below for information about prerequisites
205 and upgrading, if you are not already using clang 3.5.0 or higher.
208 The layout of the pmap structure has changed for powerpc to put the pmap
209 statistics at the front for all CPU variations. libkvm(3) and all tools
210 that link against it need to be recompiled.
213 isl(4) and cyapa(4) drivers now require a new driver,
214 chromebook_platform(4), to work properly on Chromebook-class hardware.
215 On other types of hardware the drivers may need to be configured using
216 device hints. Please see the corresponding manual pages for details.
219 The urtwn(4) driver was merged into rtwn(4) and now consists of
220 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
222 Also, firmware for RTL8188CE was renamed due to possible name
223 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
226 GNU rcs has been removed from base. It is available as packages:
227 - rcs: Latest GPLv3 GNU rcs version.
228 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
232 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
233 modules now requires that the kernel configuration contain the
234 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
237 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
238 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
241 Relocatable object files with the extension of .So have been renamed
242 to use an extension of .pico instead. The purpose of this change is
243 to avoid a name clash with shared libraries on case-insensitive file
244 systems. On those file systems, foo.So is the same file as foo.so.
247 GNU rcs has been turned off by default. It can (temporarily) be built
248 again by adding WITH_RCS knob in src.conf.
249 Otherwise, GNU rcs is available from packages:
250 - rcs: Latest GPLv3 GNU rcs version.
251 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
254 The backup_uses_rcs functionality has been removed from rc.subr.
257 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
258 two separate components, QUEUE_MACRO_DEBUG_TRACE and
259 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
260 QUEUE_MACRO_DEBUG behavior.
263 r304787 changed some ioctl interfaces between the iSCSI userspace
264 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
265 rebuilt to work with new kernels. __FreeBSD_version has been bumped
269 The UDP receive code has been updated to only treat incoming UDP
270 packets that were addressed to an L2 broadcast address as L3
271 broadcast packets. It is not expected that this will affect any
272 standards-conforming UDP application. The new behaviour can be
273 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
277 Remove the openbsd_poll system call.
278 __FreeBSD_version has been bumped because of this.
281 The libc stub for the pipe(2) system call has been replaced with
282 a wrapper that calls the pipe2(2) system call and the pipe(2)
283 system call is now only implemented by the kernels that include
284 "options COMPAT_FREEBSD10" in their config file (this is the
285 default). Users should ensure that this option is enabled in
286 their kernel or upgrade userspace to r302092 before upgrading their
290 CAM will now strip leading spaces from SCSI disks' serial numbers.
291 This will affect users who create UFS filesystems on SCSI disks using
292 those disk's diskid device nodes. For example, if /etc/fstab
293 previously contained a line like
294 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
295 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
296 transforms like gmirror may also be affected. ZFS users should
300 The bitstring(3) API has been updated with new functionality and
301 improved performance. But it is binary-incompatible with the old API.
302 Objects built with the new headers may not be linked against objects
303 built with the old headers.
306 The brk and sbrk functions have been removed from libc on arm64.
307 Binutils from ports has been updated to not link to these
308 functions and should be updated to the latest version before
309 installing a new libc.
312 The armv6 port now defaults to hard float ABI. Limited support
313 for running both hardfloat and soft float on the same system
314 is available using the libraries installed with -DWITH_LIBSOFT.
315 This has only been tested as an upgrade path for installworld
316 and packages may fail or need manual intervention to run. New
317 packages will be needed.
319 To update an existing self-hosted armv6hf system, you must add
320 TARGET_ARCH=armv6 on the make command line for both the build
321 and the install steps.
324 Kernel modules compiled outside of a kernel build now default to
325 installing to /boot/modules instead of /boot/kernel. Many kernel
326 modules built this way (such as those in ports) already overrode
327 KMODDIR explicitly to install into /boot/modules. However,
328 manually building and installing a module from /sys/modules will
329 now install to /boot/modules instead of /boot/kernel.
332 The CAM I/O scheduler has been committed to the kernel. There should be
333 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
334 list of known rogues that claim support for this but actually corrupt
335 data is believed to be complete, be on the lookout for data
336 corruption. The known rogue list is believed to be complete:
338 o Crucial MX100, M550 drives with MU01 firmware.
339 o Micron M510 and M550 drives with MU01 firmware.
340 o Micron M500 prior to MU07 firmware
341 o Samsung 830, 840, and 850 all firmwares
342 o FCCT M500 all firmwares
344 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
345 with working NCQ TRIM. For Micron branded drives, see your sales rep for
346 updated firmware. Black listed drives will work correctly because these
347 drives work correctly so long as no NCQ TRIMs are sent to them. Given
348 this list is the same as found in Linux, it's believed there are no
349 other rogues in the market place. All other models from the above
352 To be safe, if you are at all concerned, you can quirk each of your
353 drives to prevent NCQ from being sent by setting:
354 kern.cam.ada.X.quirks="0x2"
355 in loader.conf. If the drive requires the 4k sector quirk, set the
359 The FAST_DEPEND build option has been removed and its functionality is
360 now the one true way. The old mkdep(1) style of 'make depend' has
361 been removed. See 20160311 for further details.
364 Resource range types have grown from unsigned long to uintmax_t. All
365 drivers, and anything using libdevinfo, need to be recompiled.
368 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
369 builds. It no longer runs mkdep(1) during 'make depend', and the
370 'make depend' stage can safely be skipped now as it is auto ran
371 when building 'make all' and will generate all SRCS and DPSRCS before
372 building anything else. Dependencies are gathered at compile time with
373 -MF flags kept in separate .depend files per object file. Users should
374 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
378 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
379 kernel modules. Therefore, if you load any kernel modules at boot time,
380 please install the boot loaders after you install the kernel, but before
384 make kernel KERNCONF=YOUR_KERNEL_HERE
385 make -C sys/boot install
386 <reboot in single user>
388 Then follow the usual steps, described in the General Notes section,
392 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
393 see the 20141231 entry below for information about prerequisites and
394 upgrading, if you are not already using clang 3.5.0 or higher.
397 The AIO subsystem is now a standard part of the kernel. The
398 VFS_AIO kernel option and aio.ko kernel module have been removed.
399 Due to stability concerns, asynchronous I/O requests are only
400 permitted on sockets and raw disks by default. To enable
401 asynchronous I/O requests on all file types, set the
402 vfs.aio.enable_unsafe sysctl to a non-zero value.
405 The ELF object manipulation tool objcopy is now provided by the
406 ELF Tool Chain project rather than by GNU binutils. It should be a
407 drop-in replacement, with the addition of arm64 support. The
408 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
409 to obtain the GNU version if necessary.
412 Building ZFS pools on top of zvols is prohibited by default. That
413 feature has never worked safely; it's always been prone to deadlocks.
414 Using a zvol as the backing store for a VM guest's virtual disk will
415 still work, even if the guest is using ZFS. Legacy behavior can be
416 restored by setting vfs.zfs.vol.recursive=1.
419 The NONE and HPN patches has been removed from OpenSSH. They are
420 still available in the security/openssh-portable port.
423 With the addition of ypldap(8), a new _ypldap user is now required
424 during installworld. "mergemaster -p" can be used to add the user
425 prior to installworld, as documented in the handbook.
428 The tftp loader (pxeboot) now uses the option root-path directive. As a
429 consequence it no longer looks for a pxeboot.4th file on the tftp
430 server. Instead it uses the regular /boot infrastructure as with the
434 The code to start recording plug and play data into the modules has
435 been committed. While the old tools will properly build a new kernel,
436 a number of warnings about "unknown metadata record 4" will be produced
437 for an older kldxref. To avoid such warnings, make sure to rebuild
438 the kernel toolchain (or world). Make sure that you have r292078 or
439 later when trying to build 292077 or later before rebuilding.
442 Debug data files are now built by default with 'make buildworld' and
443 installed with 'make installworld'. This facilitates debugging but
444 requires more disk space both during the build and for the installed
445 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
449 r291527 changed the internal interface between the nfsd.ko and
450 nfscommon.ko modules. As such, they must both be upgraded to-gether.
451 __FreeBSD_version has been bumped because of this.
454 Add support for unicode collation strings leads to a change of
455 order of files listed by ls(1) for example. To get back to the old
456 behaviour, set LC_COLLATE environment variable to "C".
458 Databases administrators will need to reindex their databases given
459 collation results will be different.
461 Due to a bug in install(1) it is recommended to remove the ancient
462 locales before running make installworld.
464 rm -rf /usr/share/locale/*
467 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
468 libcrypto.so.7 or libssl.so.7 must be recompiled.
471 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
472 Kernel modules isp_2400_multi and isp_2500_multi were removed and
473 should be replaced with isp_2400 and isp_2500 modules respectively.
476 The build previously allowed using 'make -n' to not recurse into
477 sub-directories while showing what commands would be executed, and
478 'make -n -n' to recursively show commands. Now 'make -n' will recurse
479 and 'make -N' will not.
482 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
483 and etcupdate will now use this file. A custom sendmail.cf is now
484 updated via this mechanism rather than via installworld. If you had
485 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
486 want to remove the exclusion or change it to "always install".
487 /etc/mail/sendmail.cf is now managed the same way regardless of
488 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
489 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
492 Compatibility shims for legacy ATA device names have been removed.
493 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
494 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
495 environment variables, /dev/ad* and /dev/ar* symbolic links.
498 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
499 Please see the 20141231 entry below for information about prerequisites
500 and upgrading, if you are not already using clang 3.5.0 or higher.
503 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
504 and renamed from .symbols to .debug. This reduces the size requirements
505 on the boot partition or file system and provides consistency with
506 userland debug files.
508 When using the supported kernel installation method the
509 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
510 as is done with /boot/kernel.
512 Developers wishing to maintain the historical behavior of installing
513 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
516 The wireless drivers had undergone changes that remove the 'parent
517 interface' from the ifconfig -l output. The rc.d network scripts
518 used to check presence of a parent interface in the list, so old
519 scripts would fail to start wireless networking. Thus, etcupdate(3)
520 or mergemaster(8) run is required after kernel update, to update your
521 rc.d scripts in /etc.
524 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
525 These configurations are now automatically interpreted as
526 'scrub fragment reassemble'.
529 Kernel-loadable modules for the random(4) device are back. To use
530 them, the kernel must have
533 options RANDOM_LOADABLE
535 kldload(8) can then be used to load random_fortuna.ko
536 or random_yarrow.ko. Please note that due to the indirect
537 function calls that the loadable modules need to provide,
538 the build-in variants will be slightly more efficient.
540 The random(4) kernel option RANDOM_DUMMY has been retired due to
541 unpopularity. It was not all that useful anyway.
544 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
545 Control over building the ELF Tool Chain tools is now provided by
546 the WITHOUT_TOOLCHAIN knob.
549 The polarity of Pulse Per Second (PPS) capture events with the
550 uart(4) driver has been corrected. Prior to this change the PPS
551 "assert" event corresponded to the trailing edge of a positive PPS
552 pulse and the "clear" event was the leading edge of the next pulse.
554 As the width of a PPS pulse in a typical GPS receiver is on the
555 order of 1 millisecond, most users will not notice any significant
556 difference with this change.
558 Anyone who has compensated for the historical polarity reversal by
559 configuring a negative offset equal to the pulse width will need to
560 remove that workaround.
563 The default group assigned to /dev/dri entries has been changed
564 from 'wheel' to 'video' with the id of '44'. If you want to have
565 access to the dri devices please add yourself to the video group
568 # pw groupmod video -m $USER
571 The menu.rc and loader.rc files will now be replaced during
572 upgrades. Please migrate local changes to menu.rc.local and
573 loader.rc.local instead.
576 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
577 strings and strip have been removed. The src.conf(5) knob
578 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
581 As ZFS requires more kernel stack pages than is the default on some
582 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
583 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
585 Please consider using 'options KSTACK_PAGES=X' where X is greater
586 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
589 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
590 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
591 default, i.e., they will not contain "::". For example, instead
592 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
593 to have a more specific match, such as different map entries for
594 IPv6:0:0 vs IPv6:0. This change requires that configuration
595 data (including maps, files, classes, custom ruleset, etc.) must
596 use the same format, so make certain such configuration data is
597 upgrading. As a very simple check search for patterns like
598 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
599 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
600 the cf option UseCompressedIPv6Addresses.
603 The default kernel entropy-processing algorithm is now
604 Fortuna, replacing Yarrow.
606 Assuming you have 'device random' in your kernel config
607 file, the configurations allow a kernel option to override
608 this default. You may choose *ONE* of:
610 options RANDOM_YARROW # Legacy /dev/random algorithm.
611 options RANDOM_DUMMY # Blocking-only driver.
613 If you have neither, you get Fortuna. For most people,
614 read no further, Fortuna will give a /dev/random that works
615 like it always used to, and the difference will be irrelevant.
617 If you remove 'device random', you get *NO* kernel-processed
618 entropy at all. This may be acceptable to folks building
619 embedded systems, but has complications. Carry on reading,
620 and it is assumed you know what you need.
622 *PLEASE* read random(4) and random(9) if you are in the
623 habit of tweaking kernel configs, and/or if you are a member
624 of the embedded community, wanting specific and not-usual
625 behaviour from your security subsystems.
627 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
628 random', you will NOT have a functioning /dev/random, and
629 many cryptographic features will not work, including SSH.
630 You may also find strange behaviour from the random(3) set
631 of library functions, in particular sranddev(3), srandomdev(3)
632 and arc4random(3). The reason for this is that the KERN_ARND
633 sysctl only returns entropy if it thinks it has some to
634 share, and with RANDOM_DUMMY or no 'device random' this
638 An additional fix for the issue described in the 20150614 sendmail
639 entry below has been been committed in revision 284717.
642 FreeBSD's old make (fmake) has been removed from the system. It is
643 available as the devel/fmake port or via pkg install fmake.
646 The fix for the issue described in the 20150614 sendmail entry
647 below has been been committed in revision 284436. The work
648 around described in that entry is no longer needed unless the
649 default setting is overridden by a confDH_PARAMETERS configuration
650 setting of '5' or pointing to a 512 bit DH parameter file.
653 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
654 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
655 and devel/kyua to version 0.20+ and adjust any calling code to work
656 with Kyuafile and kyua.
659 The import of openssl to address the FreeBSD-SA-15:10.openssl
660 security advisory includes a change which rejects handshakes
661 with DH parameters below 768 bits. sendmail releases prior
662 to 8.15.2 (not yet released), defaulted to a 512 bit
663 DH parameter setting for client connections. To work around
664 this interoperability, sendmail can be configured to use a
665 2048 bit DH parameter by:
667 1. Edit /etc/mail/`hostname`.mc
668 2. If a setting for confDH_PARAMETERS does not exist or
669 exists and is set to a string beginning with '5',
671 3. If a setting for confDH_PARAMETERS exists and is set to
672 a file path, create a new file with:
673 openssl dhparam -out /path/to/file 2048
674 4. Rebuild the .cf file:
675 cd /etc/mail/; make; make install
677 cd /etc/mail/; make restart
679 A sendmail patch is coming, at which time this file will be
683 Generation of legacy formatted entries have been disabled by default
684 in pwd_mkdb(8), as all base system consumers of the legacy formatted
685 entries were converted to use the new format by default when the new,
686 machine independent format have been added and supported since FreeBSD
689 Please see the pwd_mkdb(8) manual page for further details.
692 Clang and llvm have been upgraded to 3.6.1 release. Please see the
693 20141231 entry below for information about prerequisites and upgrading,
694 if you are not already using 3.5.0 or higher.
697 TI platform code switched to using vendor DTS files and this update
698 may break existing systems running on Beaglebone, Beaglebone Black,
701 - dtb files should be regenerated/reinstalled. Filenames are the
702 same but content is different now
703 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
704 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
705 addressing scheme is now pin 25 on /dev/gpioc3.
706 - Pandaboard: /etc/ttys should be updated, serial console device is
707 now /dev/ttyu2, not /dev/ttyu0
710 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
711 If you need the GNU extension from groff soelim(1), install groff
712 from package: pkg install groff, or via ports: textproc/groff.
715 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
716 defined in symlink(7); previously symlinks were silently ignored.
719 The const qualifier has been removed from iconv(3) to comply with
720 POSIX. The ports tree is aware of this from r384038 onwards.
723 Libraries specified by LIBADD in Makefiles must have a corresponding
724 DPADD_<lib> variable to ensure correct dependencies. This is now
725 enforced in src.libnames.mk.
728 From legacy ata(4) driver was removed support for SATA controllers
729 supported by more functional drivers ahci(4), siis(4) and mvs(4).
730 Kernel modules ataahci and ataadaptec were removed completely,
731 replaced by ahci and mvs modules respectively.
734 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
735 the 20141231 entry below for information about prerequisites and
736 upgrading, if you are not already using 3.5.0 or higher.
739 The 32-bit PowerPC kernel has been changed to a position-independent
740 executable. This can only be booted with a version of loader(8)
741 newer than January 31, 2015, so make sure to update both world and
742 kernel before rebooting.
745 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
746 but before r278950, the RNG was not seeded properly. Immediately
747 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
748 ssh keys or openssl keys) that were generated w/ a kernel from that
749 range. This does not affect programs that directly used /dev/random
750 or /dev/urandom. All userland uses of arc4random(3) are affected.
753 The autofs(4) ABI was changed in order to restore binary compatibility
754 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
758 The powerpc64 kernel has been changed to a position-independent
759 executable. This can only be booted with a new version of loader(8),
760 so make sure to update both world and kernel before rebooting.
763 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
764 only release, no new features have been added. Please see the 20141231
765 entry below for information about prerequisites and upgrading, if you
766 are not already using 3.5.0.
769 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
770 taken from the ELF Tool Chain project rather than GNU binutils. They
771 should be drop-in replacements, with the addition of arm64 support.
772 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
773 binutils tools, if necessary. See 20150805 for updated information.
776 The default Unbound configuration now enables remote control
777 using a local socket. Users who have already enabled the
778 local_unbound service should regenerate their configuration
779 by running "service local_unbound setup" as root.
782 The GNU texinfo and GNU info pages have been removed.
783 To be able to view GNU info pages please install texinfo from ports.
786 Clang, llvm and lldb have been upgraded to 3.5.0 release.
788 As of this release, a prerequisite for building clang, llvm and lldb is
789 a C++11 capable compiler and C++11 standard library. This means that to
790 be able to successfully build the cross-tools stage of buildworld, with
791 clang as the bootstrap compiler, your system compiler or cross compiler
792 should either be clang 3.3 or later, or gcc 4.8 or later, and your
793 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
796 On any standard FreeBSD 10.x or 11.x installation, where clang and
797 libc++ are on by default (that is, on x86 or arm), this should work out
800 On 9.x installations where clang is enabled by default, e.g. on x86 and
801 powerpc, libc++ will not be enabled by default, so libc++ should be
802 built (with clang) and installed first. If both clang and libc++ are
803 missing, build clang first, then use it to build libc++.
805 On 8.x and earlier installations, upgrade to 9.x first, and then follow
806 the instructions for 9.x above.
808 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
809 default, and do not build clang.
811 Many embedded systems are resource constrained, and will not be able to
812 build clang in a reasonable time, or in some cases at all. In those
813 cases, cross building bootable systems on amd64 is a workaround.
815 This new version of clang introduces a number of new warnings, of which
816 the following are most likely to appear:
820 This warns in two cases, for both C and C++:
821 * When the code is trying to take the absolute value of an unsigned
822 quantity, which is effectively a no-op, and almost never what was
823 intended. The code should be fixed, if at all possible. If you are
824 sure that the unsigned quantity can be safely cast to signed, without
825 loss of information or undefined behavior, you can add an explicit
826 cast, or disable the warning.
828 * When the code is trying to take an absolute value, but the called
829 abs() variant is for the wrong type, which can lead to truncation.
830 If you want to disable the warning instead of fixing the code, please
831 make sure that truncation will not occur, or it might lead to unwanted
834 -Wtautological-undefined-compare and
835 -Wundefined-bool-conversion
837 These warn when C++ code is trying to compare 'this' against NULL, while
838 'this' should never be NULL in well-defined C++ code. However, there is
839 some legacy (pre C++11) code out there, which actively abuses this
840 feature, which was less strictly defined in previous C++ versions.
842 Squid and openjdk do this, for example. The warning can be turned off
843 for C++98 and earlier, but compiling the code in C++11 mode might result
844 in unexpected behavior; for example, the parts of the program that are
845 unreachable could be optimized away.
848 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
849 kernel sources have been removed. The .h files remain, since some
850 utilities include them. This will need to be fixed later.
851 If "mount -t oldnfs ..." is attempted, it will fail.
852 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
853 the utilities will report errors.
856 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
857 directories to top level SUBDIR variable when their parent
858 directory is included in LOCAL_DIRS. Users with build systems with
859 such hierarchies and without SUBDIR entries in the parent
860 directory Makefiles should add them or add the directories to
864 faith(4) and faithd(8) have been removed from the base system. Faith
865 has been obsolete for a very long time.
868 vt(4), the new console driver, is enabled by default. It brings
869 support for Unicode and double-width characters, as well as
870 support for UEFI and integration with the KMS kernel video
873 You may need to update your console settings in /etc/rc.conf,
874 most probably the keymap. During boot, /etc/rc.d/syscons will
875 indicate what you need to do.
877 vt(4) still has issues and lacks some features compared to
878 syscons(4). See the wiki for up-to-date information:
879 https://wiki.freebsd.org/Newcons
881 If you want to keep using syscons(4), you can do so by adding
882 the following line to /boot/loader.conf:
886 pjdfstest has been integrated into kyua as an opt-in test suite.
887 Please see share/doc/pjdfstest/README for more details on how to
891 gperf has been removed from the base system for architectures
892 that use clang. Ports that require gperf will obtain it from the
896 pjdfstest has been moved from tools/regression/pjdfstest to
900 At svn r271982, The default linux compat kernel ABI has been adjusted
901 to 2.6.18 in support of the linux-c6 compat ports infrastructure
902 update. If you wish to continue using the linux-f10 compat ports,
903 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
904 encouraged to update their linux-compat packages to linux-c6 during
905 their next update cycle.
908 The ofwfb driver, used to provide a graphics console on PowerPC when
909 using vt(4), no longer allows mmap() of all physical memory. This
910 will prevent Xorg on PowerPC with some ATI graphics cards from
911 initializing properly unless x11-servers/xorg-server is updated to
915 The xdev targets have been converted to using TARGET and
916 TARGET_ARCH instead of XDEV and XDEV_ARCH.
919 The default unbound configuration has been modified to address
920 issues with reverse lookups on networks that use private
921 address ranges. If you use the local_unbound service, run
922 "service local_unbound setup" as root to regenerate your
923 configuration, then "service local_unbound reload" to load the
927 The GNU texinfo and GNU info pages are not built and installed
928 anymore, WITH_INFO knob has been added to allow to built and install
930 UPDATE: see 20150102 entry on texinfo's removal
933 The GNU readline library is now an INTERNALLIB - that is, it is
934 statically linked into consumers (GDB and variants) in the base
935 system, and the shared library is no longer installed. The
936 devel/readline port is available for third party software that
940 The Itanium architecture (ia64) has been removed from the list of
941 known architectures. This is the first step in the removal of the
945 Commit r268115 has added NFSv4.1 server support, merged from
946 projects/nfsv4.1-server. Since this includes changes to the
947 internal interfaces between the NFS related modules, a full
948 build of the kernel and modules will be necessary.
949 __FreeBSD_version has been bumped.
952 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
953 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
954 which differs from the behaviour controlled by this knob.)
957 Maximal length of the serial number in CTL was increased from 16 to
958 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
959 and ctld, need to be rebuilt to work with a new kernel.
962 The libatf-c and libatf-c++ major versions were downgraded to 0 and
963 1 respectively to match the upstream numbers. They were out of
964 sync because, when they were originally added to FreeBSD, the
965 upstream versions were not respected. These libraries are private
966 and not yet built by default, so renumbering them should be a
967 non-issue. However, unclean source trees will yield broken test
968 programs once the operator executes "make delete-old-libs" after a
971 Additionally, the atf-sh binary was made private by moving it into
972 /usr/libexec/. Already-built shell test programs will keep the
973 path to the old binary so they will break after "make delete-old"
976 If you are using WITH_TESTS=yes (not the default), wipe the object
977 tree and rebuild from scratch to prevent spurious test failures.
978 This is only needed once: the misnumbered libraries and misplaced
979 binaries have been added to OptionalObsoleteFiles.inc so they will
980 be removed during a clean upgrade.
983 Clang and llvm have been upgraded to 3.4.1 release.
986 We bogusly installed src.opts.mk in /usr/share/mk. This file should
987 be removed to avoid issues in the future (and has been added to
991 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
992 past, it affected all builds that used the bsd.*.mk files. The old
993 behavior was a bug, but people may have relied upon it. To get this
994 behavior back, you can .include /etc/src.conf from /etc/make.conf
995 (which is still global and isn't changed). This also changes the
996 behavior of incremental builds inside the tree of individual
997 directories. Set MAKESYSPATH to ".../share/mk" to do that.
998 Although this has survived make universe and some upgrade scenarios,
999 other upgrade scenarios may have broken. At least one form of
1000 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1001 as well... In cases where MAKESYSPATH isn't working with this
1002 setting, you'll need to set it to the full path to your tree.
1004 One side effect of all this cleaning up is that bsd.compiler.mk
1005 is no longer implicitly included by bsd.own.mk. If you wish to
1006 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1010 The lindev device has been removed since /dev/full has been made a
1011 standard device. __FreeBSD_version has been bumped.
1014 The knob WITHOUT_VI was added to the base system, which controls
1015 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1016 in order to reorder files share/termcap and didn't build ex(1) as a
1017 build tool, so building/installing with WITH_VI is highly advised for
1018 build hosts for older releases.
1020 This issue has been fixed in stable/9 and stable/10 in r277022 and
1021 r276991, respectively.
1024 The YES_HESIOD knob has been removed. It has been obsolete for
1025 a decade. Please move to using WITH_HESIOD instead or your builds
1026 will silently lack HESIOD.
1029 The uart(4) driver has been changed with respect to its handling
1030 of the low-level console. Previously the uart(4) driver prevented
1031 any process from changing the baudrate or the CLOCAL and HUPCL
1032 control flags. By removing the restrictions, operators can make
1033 changes to the serial console port without having to reboot.
1034 However, when getty(8) is started on the serial device that is
1035 associated with the low-level console, a misconfigured terminal
1036 line in /etc/ttys will now have a real impact.
1037 Before upgrading the kernel, make sure that /etc/ttys has the
1038 serial console device configured as 3wire without baudrate to
1039 preserve the previous behaviour. E.g:
1040 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1043 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1044 to improve performance. To re-enable it, if needed, run rpcbind
1045 with command line option -W.
1048 Switched back to the GPL dtc compiler due to updates in the upstream
1049 dts files not being supported by the BSDL dtc compiler. You will need
1050 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1051 may result while building dtb files during a kernel build if you fail
1052 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1055 Clang and llvm have been upgraded to 3.4 release.
1058 The nve(4) driver has been removed. Please use the nfe(4) driver
1059 for NVIDIA nForce MCP Ethernet adapters instead.
1062 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1063 This could cause certain C++ applications using shared libraries built
1064 against the previous version of libc++ to crash. The incompatibility
1065 has now been fixed, but any C++ applications or shared libraries built
1066 between r261283 and r261801 should be recompiled.
1069 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1070 capability mode support. Please note that enabling the feature in
1071 kernel is still highly recommended.
1074 OpenSSH is now built with sandbox support, and will use sandbox as
1075 the default privilege separation method. This requires Capsicum
1076 capability mode support in kernel.
1079 The libelf and libdwarf libraries have been updated to newer
1080 versions from upstream. Shared library version numbers for
1081 these two libraries were bumped. Any ports or binaries
1082 requiring these two libraries should be recompiled.
1083 __FreeBSD_version is bumped to 1100006.
1086 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1087 instead of providing an explicit one, this would prevent such
1088 Makefile from providing its own Kyuafile in the future during
1089 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1090 intervention is needed to clean an objdir if you use NO_CLEAN:
1091 # find /usr/obj -name Kyuafile | xargs rm -f
1094 The behavior of gss_pseudo_random() for the krb5 mechanism
1095 has changed, for applications requesting a longer random string
1096 than produced by the underlying enctype's pseudo-random() function.
1097 In particular, the random string produced from a session key of
1098 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1099 be different at the 17th octet and later, after this change.
1100 The counter used in the PRF+ construction is now encoded as a
1101 big-endian integer in accordance with RFC 4402.
1102 __FreeBSD_version is bumped to 1100004.
1105 The WITHOUT_ATF build knob has been removed and its functionality
1106 has been subsumed into the more generic WITHOUT_TESTS. If you were
1107 using the former to disable the build of the ATF libraries, you
1108 should change your settings to use the latter.
1111 The default version of mtree is nmtree which is obtained from
1112 NetBSD. The output is generally the same, but may vary
1113 slightly. If you found you need identical output adding
1114 "-F freebsd9" to the command line should do the trick. For the
1115 time being, the old mtree is available as fmtree.
1118 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1119 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1120 1.1.4_8 and verify bsdyml not linked in, before running "make
1122 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1124 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1127 The stable/10 branch has been created in subversion from head
1131 The rc.d/jail script has been updated to support jail(8)
1132 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1133 for per-jail configuration are automatically converted to
1134 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1135 This is transparently backward compatible. See below about some
1136 incompatibilities and rc.conf(5) manual page for more details.
1138 These variables are now deprecated in favor of jail(8) configuration
1139 file. One can use "rc.d/jail config <jname>" command to generate
1140 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1141 running the jail(8) utility. The default pathname of the
1142 configuration file is /etc/jail.conf and can be specified by
1143 using $jail_conf or $jail_<jname>_conf variables.
1145 Please note that jail_devfs_ruleset accepts an integer at
1146 this moment. Please consider to rewrite the ruleset name
1150 BIND has been removed from the base system. If all you need
1151 is a local resolver, simply enable and start the local_unbound
1152 service instead. Otherwise, several versions of BIND are
1153 available in the ports tree. The dns/bind99 port is one example.
1155 With this change, nslookup(1) and dig(1) are no longer in the base
1156 system. Users should instead use host(1) and drill(1) which are
1157 in the base system. Alternatively, nslookup and dig can
1158 be obtained by installing the dns/bind-tools port.
1161 With the addition of unbound(8), a new unbound user is now
1162 required during installworld. "mergemaster -p" can be used to
1163 add the user prior to installworld, as documented in the handbook.
1166 OpenSSH is now built with DNSSEC support, and will by default
1167 silently trust signed SSHFP records. This can be controlled with
1168 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1169 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1172 The GNU Compiler Collection and C++ standard library (libstdc++)
1173 are no longer built by default on platforms where clang is the system
1174 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1175 options in src.conf.
1178 The PROCDESC kernel option is now part of the GENERIC kernel
1179 configuration and is required for the rwhod(8) to work.
1180 If you are using custom kernel configuration, you should include
1184 The API and ABI related to the Capsicum framework was modified
1185 in backward incompatible way. The userland libraries and programs
1186 have to be recompiled to work with the new kernel. This includes the
1187 following libraries and programs, but the whole buildworld is
1188 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1189 kdump, procstat, rwho, rwhod, uniq.
1192 AES-NI intrinsic support has been added to gcc. The AES-NI module
1193 has been updated to use this support. A new gcc is required to build
1194 the aesni module on both i386 and amd64.
1197 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1198 Thus "device padlock_rng" and "device rdrand_rng" should be
1199 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1202 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1203 enables just the iconv* functionality and is now on by default.
1204 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1205 compatibility. Set WITHOUT_ICONV to build the old way.
1206 If you have been using WITH_ICONV before, you will very likely
1207 need to turn on WITH_LIBICONV_COMPAT.
1210 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1211 Illumos origin, including ZFS. If you have INVARIANTS in your
1212 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1214 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1215 locks if WITNESS option was set. Because that generated a lot of
1216 witness(9) reports and all of them were believed to be false
1217 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1218 can be used to achieve the previous behavior.
1221 Timer values in IPv6 data structures now use time_uptime instead
1222 of time_second. Although this is not a user-visible functional
1223 change, userland utilities which directly use them---ndp(8),
1224 rtadvd(8), and rtsold(8) in the base system---need to be updated
1225 to r253970 or later.
1228 find -delete can now delete the pathnames given as arguments,
1229 instead of only files found below them or if the pathname did
1230 not contain any slashes. Formerly, the following error message
1233 find: -delete: <path>: relative path potentially not safe
1235 Deleting the pathnames given as arguments can be prevented
1236 without error messages using -mindepth 1 or by changing
1237 directory and passing "." as argument to find. This works in the
1238 old as well as the new version of find.
1241 Behavior of devfs rules path matching has been changed.
1242 Pattern is now always matched against fully qualified devfs
1243 path and slash characters must be explicitly matched by
1244 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1245 subdirectories must be reviewed.
1248 The default ARM ABI has changed to the ARM EABI. The old ABI is
1249 incompatible with the ARM EABI and all programs and modules will
1250 need to be rebuilt to work with a new kernel.
1252 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1254 NOTE: Support for the old ABI will be removed in the future and
1255 users are advised to upgrade.
1258 pkg_install has been disconnected from the build if you really need it
1259 you should add WITH_PKGTOOLS in your src.conf(5).
1262 Most of network statistics structures were changed to be able
1263 keep 64-bits counters. Thus all tools, that work with networking
1264 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1267 Fix a bug that allowed a tracing process (e.g. gdb) to write
1268 to a memory-mapped file in the traced process's address space
1269 even if neither the traced process nor the tracing process had
1270 write access to that file.
1273 CVS has been removed from the base system. An exact copy
1274 of the code is available from the devel/cvs port.
1277 Some people report the following error after the switch to bmake:
1279 make: illegal option -- J
1280 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1282 *** [buildworld] Error code 2
1284 this likely due to an old instance of make in
1285 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1286 which src/Makefile will use that blindly, if it exists, so if
1287 you see the above error:
1289 rm -rf `make -V MAKEPATH`
1294 Use bmake by default.
1295 Whereas before one could choose to build with bmake via
1296 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1297 make. The goal is to remove these knobs for 10-RELEASE.
1299 It is worth noting that bmake (like gmake) treats the command
1300 line as the unit of failure, rather than statements within the
1301 command line. Thus '(cd some/where && dosomething)' is safer
1302 than 'cd some/where; dosomething'. The '()' allows consistent
1303 behavior in parallel build.
1306 Fix a bug that allows NFS clients to issue READDIR on files.
1309 The WITHOUT_IDEA option has been removed because
1310 the IDEA patent expired.
1313 The sysctl which controls TRIM support under ZFS has been renamed
1314 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1318 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1319 rather than creating it's own in the temporary directory in
1320 order allow access to bootstrapped versions of tools such as
1321 install and mtree. When upgrading from version of FreeBSD where
1322 the install command does not support -l, you will need to
1323 install a new mergemaster command if mergemaster -p is required.
1324 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1328 Legacy ATA stack, disabled and replaced by new CAM-based one since
1329 FreeBSD 9.0, completely removed from the sources. Kernel modules
1330 atadisk and atapi*, user-level tools atacontrol and burncd are
1331 removed. Kernel option `options ATA_CAM` is now permanently enabled
1335 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1336 and socketpair(2). Software, in particular Kerberos, may
1337 automatically detect and use these during building. The resulting
1338 binaries will not work on older kernels.
1341 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1342 information, see the respective 20130304 entry).
1345 Recent commits to callout(9) changed the size of struct callout,
1346 so the KBI is probably heavily disturbed. Also, some functions
1347 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1348 by macros. Every kernel module using it won't load, so rebuild
1351 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1352 but does not initialize by default (because of the new CTL_DISABLE
1353 option) to save memory. To re-enable it, remove the CTL_DISABLE
1354 option from the kernel config file or set kern.cam.ctl.disable=0
1355 in /boot/loader.conf.
1358 The ctl device has been disabled in GENERIC for i386 and amd64.
1359 This was done due to the extra memory being allocated at system
1360 initialisation time by the ctl driver which was only used if
1361 a CAM target device was created. This makes a FreeBSD system
1362 unusable on 128MB or less of RAM.
1365 A new compression method (lz4) has been merged to -HEAD. Please
1366 refer to zpool-features(7) for more information.
1368 Please refer to the "ZFS notes" section of this file for information
1369 on upgrading boot ZFS pools.
1372 A BSD-licensed patch(1) variant has been added and is installed
1373 as bsdpatch, being the GNU version the default patch.
1374 To inverse the logic and use the BSD-licensed one as default,
1375 while having the GNU version installed as gnupatch, rebuild
1376 and install world with the WITH_BSD_PATCH knob set.
1379 Due to the use of the new -l option to install(1) during build
1380 and install, you must take care not to directly set the INSTALL
1381 make variable in your /etc/make.conf, /etc/src.conf, or on the
1382 command line. If you wish to use the -C flag for all installs
1383 you may be able to add INSTALL+=-C to /etc/make.conf or
1387 The install(1) option -M has changed meaning and now takes an
1388 argument that is a file or path to append logs to. In the
1389 unlikely event that -M was the last option on the command line
1390 and the command line contained at least two files and a target
1391 directory the first file will have logs appended to it. The -M
1392 option served little practical purpose in the last decade so its
1393 use is expected to be extremely rare.
1396 After switching to Clang as the default compiler some users of ZFS
1397 on i386 systems started to experience stack overflow kernel panics.
1398 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1401 GEOM_LABEL now mangles label names read from file system metadata.
1402 Mangling affect labels containing spaces, non-printable characters,
1403 '%' or '"'. Device names in /etc/fstab and other places may need to
1407 By default, only the 10 most recent kernel dumps will be saved. To
1408 restore the previous behaviour (no limit on the number of kernel dumps
1409 stored in the dump directory) add the following line to /etc/rc.conf:
1414 With the addition of auditdistd(8), a new auditdistd user is now
1415 required during installworld. "mergemaster -p" can be used to
1416 add the user prior to installworld, as documented in the handbook.
1419 The sin6_scope_id member variable in struct sockaddr_in6 is now
1420 filled by the kernel before passing the structure to the userland via
1421 sysctl or routing socket. This means the KAME-specific embedded scope
1422 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1423 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1424 __FreeBSD_version is bumped to 1000025.
1427 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1428 This means that the world and kernel will be compiled with clang
1429 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1430 and /usr/bin/cpp. To disable this behavior and revert to building
1431 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1432 of current may need to bootstrap WITHOUT_CLANG first if the clang
1433 build fails (its compatibility window doesn't extend to the 9 stable
1437 The IPFIREWALL_FORWARD kernel option has been removed. Its
1438 functionality now turned on by default.
1441 The ZERO_COPY_SOCKET kernel option has been removed and
1442 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1443 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1444 mechanism which is not safe and may result in kernel crashes.
1445 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1446 driver supports disposeable external page sized mbuf storage.
1447 Proper replacements for both zero-copy mechanisms are under
1448 consideration and will eventually lead to complete removal
1449 of the two kernel options.
1452 The IPv4 network stack has been converted to network byte
1453 order. The following modules need to be recompiled together
1454 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1455 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1458 Support for non-MPSAFE filesystems was removed from VFS. The
1459 VFS_VERSION was bumped, all filesystem modules shall be
1463 All the non-MPSAFE filesystems have been disconnected from
1464 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1465 portalfs, smbfs, xfs.
1468 The interface cloning API and ABI has changed. The following
1469 modules need to be recompiled together with kernel:
1470 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1471 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1472 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1475 The sdhci driver was split in two parts: sdhci (generic SD Host
1476 Controller logic) and sdhci_pci (actual hardware driver).
1477 No kernel config modifications are required, but if you
1478 load sdhc as a module you must switch to sdhci_pci instead.
1481 Import the FUSE kernel and userland support into base system.
1484 The GNU sort(1) program has been removed since the BSD-licensed
1485 sort(1) has been the default for quite some time and no serious
1486 problems have been reported. The corresponding WITH_GNU_SORT
1490 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1491 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1495 The net80211(4) ABI has been changed to allow for improved driver
1496 PS-POLL and power-save support. All wireless drivers need to be
1497 recompiled to work with the new kernel.
1500 The random(4) support for the VIA hardware random number
1501 generator (`PADLOCK') is no longer enabled unconditionally.
1502 Add the padlock_rng device in the custom kernel config if
1503 needed. The GENERIC kernels on i386 and amd64 do include the
1504 device, so the change only affects the custom kernel
1508 The pf(4) packet filter ABI has been changed. pfctl(8) and
1509 snmp_pf module need to be recompiled to work with new kernel.
1512 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1513 to -HEAD. Pools that have empty_bpobj in active state can not be
1514 imported read-write with ZFS implementations that do not support
1515 this feature. For more information read the zpool-features(5)
1519 The sparc64 ZFS loader has been changed to no longer try to auto-
1520 detect ZFS providers based on diskN aliases but now requires these
1521 to be explicitly listed in the OFW boot-device environment variable.
1524 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1525 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1526 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1529 The following sysctls and tunables have been renamed for consistency
1530 with other variables:
1531 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1532 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1535 The sort utility has been replaced with BSD sort. For now, GNU sort
1536 is also available as "gnusort" or the default can be set back to
1537 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1538 installed as "bsdsort".
1541 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1542 Starting with this version the old system of ZFS pool versioning
1543 is superseded by "feature flags". This concept enables forward
1544 compatibility against certain future changes in functionality of ZFS
1545 pools. The first read-only compatible "feature flag" for ZFS pools
1546 is named "com.delphix:async_destroy". For more information
1547 read the new zpool-features(5) manual page.
1548 Please refer to the "ZFS notes" section of this file for information
1549 on upgrading boot ZFS pools.
1552 The malloc(3) implementation embedded in libc now uses sources imported
1553 as contrib/jemalloc. The most disruptive API change is to
1554 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1555 delete it prior to installworld, and optionally re-create it using the
1556 new format after rebooting. See malloc.conf(5) for details
1557 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1561 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1562 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1563 now spelled mips. This is to aid compatibility with third-party
1564 software that expects this naming scheme in uname(3). Little-endian
1565 settings are unchanged. If you are updating a big-endian mips64 machine
1566 from before this change, you may need to set MACHINE_ARCH=mips64 in
1567 your environment before the new build system will recognize your machine.
1570 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1574 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1575 nullfs(5) did not pass through all behaviours to the underlying layer,
1576 as a result if we bound to a socket on the lower layer we could connect
1577 only to the lower path; if we bound to the upper layer we could connect
1578 only to the upper path. The new behavior is one can connect to both the
1579 lower and the upper paths regardless what layer path one binds to.
1582 The getifaddrs upgrade path broken with 20111215 has been restored.
1583 If you have upgraded in between 20111215 and 20120209 you need to
1584 recompile libc again with your kernel. You still need to recompile
1585 world to be able to configure CARP but this restriction already
1586 comes from 20111215.
1589 The set_rcvar() function has been removed from /etc/rc.subr. All
1590 base and ports rc.d scripts have been updated, so if you have a
1591 port installed with a script in /usr/local/etc/rc.d you can either
1592 hand-edit the rcvar= line, or reinstall the port.
1594 An easy way to handle the mass-update of /etc/rc.d:
1595 rm /etc/rc.d/* && mergemaster -i
1598 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1599 on the current CPU and prevents other threads from running.
1600 This behavior can be reverted using the kern.stop_scheduler_on_panic
1602 The new behavior can be incompatible with kern.sync_on_panic.
1605 The carp(4) facility has been changed significantly. Configuration
1606 of the CARP protocol via ifconfig(8) has changed, as well as format
1607 of CARP events submitted to devd(8) has changed. See manual pages
1608 for more information. The arpbalance feature of carp(4) is currently
1609 not supported anymore.
1611 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1612 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1613 need to be recompiled.
1616 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1620 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1621 explicitely support non-MPSAFE filesystems.
1622 It is on by default for all supported platform at this present
1626 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1627 i386 and pc98 GENERIC kernel configuration files.
1630 sysinstall has been removed
1633 The stable/9 branch created in subversion. This corresponds to the
1634 RELENG_9 branch in CVS.
1640 Avoid using make -j when upgrading. While generally safe, there are
1641 sometimes problems using -j to upgrade. If your upgrade fails with
1642 -j, please try again without -j. From time to time in the past there
1643 have been problems using -j with buildworld and/or installworld. This
1644 is especially true when upgrading between "distant" versions (eg one
1645 that cross a major release boundary or several minor releases, or when
1646 several months have passed on the -current branch).
1648 Sometimes, obscure build problems are the result of environment
1649 poisoning. This can happen because the make utility reads its
1650 environment when searching for values for global variables. To run
1651 your build attempts in an "environmental clean room", prefix all make
1652 commands with 'env -i '. See the env(1) manual page for more details.
1654 When upgrading from one major version to another it is generally best to
1655 upgrade to the latest code in the currently installed branch first, then
1656 do an upgrade to the new branch. This is the best-tested upgrade path,
1657 and has the highest probability of being successful. Please try this
1658 approach if you encounter problems with a major version upgrade. Since
1659 the stable 4.x branch point, one has generally been able to upgade from
1660 anywhere in the most recent stable branch to head / current (or even the
1661 last couple of stable branches). See the top of this file when there's
1664 When upgrading a live system, having a root shell around before
1665 installing anything can help undo problems. Not having a root shell
1666 around can lead to problems if pam has changed too much from your
1667 starting point to allow continued authentication after the upgrade.
1669 This file should be read as a log of events. When a later event changes
1670 information of a prior event, the prior event should not be deleted.
1671 Instead, a pointer to the entry with the new information should be
1672 placed in the old entry. Readers of this file should also sanity check
1673 older entries before relying on them blindly. Authors of new entries
1674 should write them with this in mind.
1678 When upgrading the boot ZFS pool to a new version, always follow
1681 1.) recompile and reinstall the ZFS boot loader and boot block
1682 (this is part of "make buildworld" and "make installworld")
1684 2.) update the ZFS boot block on your boot drive
1686 The following example updates the ZFS boot block on the first
1687 partition (freebsd-boot) of a GPT partitioned drive ada0:
1688 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1690 Non-boot pools do not need these updates.
1694 If you are updating from a prior version of FreeBSD (even one just
1695 a few days old), you should follow this procedure. It is the most
1696 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1698 make kernel-toolchain
1699 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1700 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1702 To test a kernel once
1703 ---------------------
1704 If you just want to boot a kernel once (because you are not sure
1705 if it works, or if you want to boot a known bad kernel to provide
1706 debugging information) run
1707 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1708 nextboot -k testkernel
1710 To just build a kernel when you know that it won't mess you up
1711 --------------------------------------------------------------
1712 This assumes you are already running a CURRENT system. Replace
1713 ${arch} with the architecture of your machine (e.g. "i386",
1714 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1716 cd src/sys/${arch}/conf
1717 config KERNEL_NAME_HERE
1718 cd ../compile/KERNEL_NAME_HERE
1723 If this fails, go to the "To build a kernel" section.
1725 To rebuild everything and install it on the current system.
1726 -----------------------------------------------------------
1727 # Note: sometimes if you are running current you gotta do more than
1728 # is listed here if you are upgrading from a really old current.
1730 <make sure you have good level 0 dumps>
1732 make kernel KERNCONF=YOUR_KERNEL_HERE
1734 <reboot in single user> [3]
1741 To cross-install current onto a separate partition
1742 --------------------------------------------------
1743 # In this approach we use a separate partition to hold
1744 # current's root, 'usr', and 'var' directories. A partition
1745 # holding "/", "/usr" and "/var" should be about 2GB in
1748 <make sure you have good level 0 dumps>
1751 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1752 <maybe newfs current's root partition>
1753 <mount current's root partition on directory ${CURRENT_ROOT}>
1754 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1755 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1756 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1757 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1758 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1759 <reboot into current>
1760 <do a "native" rebuild/install as described in the previous section>
1761 <maybe install compatibility libraries from ports/misc/compat*>
1765 To upgrade in-place from stable to current
1766 ----------------------------------------------
1767 <make sure you have good level 0 dumps>
1769 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1771 <reboot in single user> [3]
1778 Make sure that you've read the UPDATING file to understand the
1779 tweaks to various things you need. At this point in the life
1780 cycle of current, things change often and you are on your own
1781 to cope. The defaults can also change, so please read ALL of
1782 the UPDATING entries.
1784 Also, if you are tracking -current, you must be subscribed to
1785 freebsd-current@freebsd.org. Make sure that before you update
1786 your sources that you have read and understood all the recent
1787 messages there. If in doubt, please track -stable which has
1788 much fewer pitfalls.
1790 [1] If you have third party modules, such as vmware, you
1791 should disable them at this point so they don't crash your
1794 [3] From the bootblocks, boot -s, and then do
1799 adjkerntz -i # if CMOS is wall time
1800 Also, when doing a major release upgrade, it is required that
1801 you boot into single user mode to do the installworld.
1803 [4] Note: This step is non-optional. Failure to do this step
1804 can result in a significant reduction in the functionality of the
1805 system. Attempting to do it by hand is not recommended and those
1806 that pursue this avenue should read this file carefully, as well
1807 as the archives of freebsd-current and freebsd-hackers mailing lists
1808 for potential gotchas. The -U option is also useful to consider.
1809 See mergemaster(8) for more information.
1811 [5] Usually this step is a noop. However, from time to time
1812 you may need to do this if you get unknown user in the following
1813 step. It never hurts to do it all the time. You may need to
1814 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1815 install) after the buildworld before this step if you last updated
1816 from current before 20130425 or from -stable before 20130430.
1818 [6] This only deletes old files and directories. Old libraries
1819 can be deleted by "make delete-old-libs", but you have to make
1820 sure that no program is using those libraries anymore.
1822 [8] In order to have a kernel that can run the 4.x binaries needed to
1823 do an installworld, you must include the COMPAT_FREEBSD4 option in
1824 your kernel. Failure to do so may leave you with a system that is
1825 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1826 required to run the 5.x binaries on more recent kernels. And so on
1827 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1829 Make sure that you merge any new devices from GENERIC since the
1830 last time you updated your kernel config file.
1832 [9] When checking out sources, you must include the -P flag to have
1833 cvs prune empty directories.
1835 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1836 "?=" instead of the "=" assignment operator, so that buildworld can
1837 override the CPUTYPE if it needs to.
1839 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1840 not on the command line, or in /etc/make.conf. buildworld will
1841 warn if it is improperly defined.
1844 This file contains a list, in reverse chronological order, of major
1845 breakages in tracking -current. It is not guaranteed to be a complete
1846 list of such breakages, and only contains entries since September 23, 2011.
1847 If you need to see UPDATING entries from before that date, you will need
1848 to fetch an UPDATING file from an older FreeBSD release.
1850 Copyright information:
1852 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1854 Redistribution, publication, translation and use, with or without
1855 modification, in full or in part, in any form or format of this
1856 document are permitted without further permission from the author.
1858 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1859 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1860 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1861 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1862 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1863 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1864 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1865 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1866 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1867 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1868 POSSIBILITY OF SUCH DAMAGE.
1870 Contact Warner Losh if you have any questions about your use of