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 http://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 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 The "ino64" 64-bit inode project has been committed, which extends
56 a number of types to 64 bits. Upgrading in place requires care and
57 adherence to the documented upgrade procedure.
59 If using a custom kernel configuration ensure that the
60 COMPAT_FREEBSD11 option is included (as during the upgrade the
61 system will be running the ino64 kernel with the existing world).
63 For the safest in-place upgrade begin by removing previous build
64 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
65 full procedure documented below under the heading "To rebuild
66 everything and install it on the current system." Specifically,
67 a reboot is required after installing the new kernel before
71 The NATM framework including the en(4), fatm(4), hatm(4), and
72 patm(4) devices has been removed. Consumers should plan a
73 migration before the end-of-life date for FreeBSD 11.
76 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
77 diff has not been implemented, if those are needed a newer version of
78 GNU diff is available via the diffutils package under the gdiff name.
81 As of r316810 for ipfilter, keep frags is no longer assumed when
82 keep state is specified in a rule. r316810 aligns ipfilter with
83 documentation in man pages separating keep frags from keep state.
84 This allows keep state to be specified without forcing keep frags
85 and allows keep frags to be specified independently of keep state.
86 To maintain previous behaviour, also specify keep frags with
87 keep state (as documented in ipf.conf.5).
90 arm64 builds now use the base system LLD 4.0.0 linker by default,
91 instead of requiring that the aarch64-binutils port or package be
92 installed. To continue using aarch64-binutils, set
93 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
96 The UDP optimization in entry 20160818 that added the sysctl
97 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
98 packets will no longer be treated as L3 broadcast packets.
101 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
102 use any explicitly assigned loopback address available in the jail
103 instead of using the first assigned address of the jail.
106 The ctl.ko module no longer implements the iSCSI target frontend:
107 cfiscsi.ko does instead.
109 If building cfiscsi.ko as a kernel module, the module can be loaded
110 via one of the following methods:
111 - `cfiscsi_load="YES"` in loader.conf(5).
112 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
113 - ctladm(8)/ctld(8), when compiled with iSCSI support
114 (`WITH_ISCSI=yes` in src.conf(5))
116 Please see cfiscsi(4) for more details.
119 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
120 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
121 same source (previously, the dependency of mmcsd.ko on mmc.ko was
122 missing, but mmcsd.ko now will refuse to load if it is incompatible
126 The syntax of ipfw(8) named states was changed to avoid ambiguity.
127 If you have used named states in the firewall rules, you need to modify
128 them after installworld and before rebooting. Now named states must
129 be prefixed with colon.
132 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
133 removed as the userland we provide cannot use them. The KMS version
134 (sys/dev/drm2) supports the same hardware.
137 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
138 Please see the 20141231 entry below for information about prerequisites
139 and upgrading, if you are not already using clang 3.5.0 or higher.
142 The code that provides support for ZFS .zfs/ directory functionality
143 has been reimplemented. It's not possible now to create a snapshot
144 by mkdir under .zfs/snapshot/. That should be the only user visible
148 EISA bus support has been removed. The WITH_EISA option is no longer
152 MCA bus support has been removed.
155 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
156 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
159 The EM_MULTIQUEUE kernel configuration option is deprecated now that
160 the em(4) driver conforms to iflib specifications.
163 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
164 IFLIB. If you have a custom kernel configuration that excludes em(4)
165 but you use igb(4), you need to re-add em(4) to your custom configuration.
168 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
169 Please see the 20141231 entry below for information about prerequisites
170 and upgrading, if you are not already using clang 3.5.0 or higher.
173 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
174 Please see the 20141231 entry below for information about prerequisites
175 and upgrading, if you are not already using clang 3.5.0 or higher.
178 The layout of the pmap structure has changed for powerpc to put the pmap
179 statistics at the front for all CPU variations. libkvm(3) and all tools
180 that link against it need to be recompiled.
183 isl(4) and cyapa(4) drivers now require a new driver,
184 chromebook_platform(4), to work properly on Chromebook-class hardware.
185 On other types of hardware the drivers may need to be configured using
186 device hints. Please see the corresponding manual pages for details.
189 The urtwn(4) driver was merged into rtwn(4) and now consists of
190 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
192 Also, firmware for RTL8188CE was renamed due to possible name
193 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
196 GNU rcs has been removed from base. It is available as packages:
197 - rcs: Latest GPLv3 GNU rcs version.
198 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
202 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
203 modules now requires that the kernel configuration contain the
204 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
207 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
208 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
211 Relocatable object files with the extension of .So have been renamed
212 to use an extension of .pico instead. The purpose of this change is
213 to avoid a name clash with shared libraries on case-insensitive file
214 systems. On those file systems, foo.So is the same file as foo.so.
217 GNU rcs has been turned off by default. It can (temporarily) be built
218 again by adding WITH_RCS knob in src.conf.
219 Otherwise, GNU rcs is available from packages:
220 - rcs: Latest GPLv3 GNU rcs version.
221 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
224 The backup_uses_rcs functionality has been removed from rc.subr.
227 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
228 two separate components, QUEUE_MACRO_DEBUG_TRACE and
229 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
230 QUEUE_MACRO_DEBUG behavior.
233 r304787 changed some ioctl interfaces between the iSCSI userspace
234 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
235 rebuilt to work with new kernels. __FreeBSD_version has been bumped
239 The UDP receive code has been updated to only treat incoming UDP
240 packets that were addressed to an L2 broadcast address as L3
241 broadcast packets. It is not expected that this will affect any
242 standards-conforming UDP application. The new behaviour can be
243 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
247 Remove the openbsd_poll system call.
248 __FreeBSD_version has been bumped because of this.
251 The libc stub for the pipe(2) system call has been replaced with
252 a wrapper that calls the pipe2(2) system call and the pipe(2)
253 system call is now only implemented by the kernels that include
254 "options COMPAT_FREEBSD10" in their config file (this is the
255 default). Users should ensure that this option is enabled in
256 their kernel or upgrade userspace to r302092 before upgrading their
260 CAM will now strip leading spaces from SCSI disks' serial numbers.
261 This will affect users who create UFS filesystems on SCSI disks using
262 those disk's diskid device nodes. For example, if /etc/fstab
263 previously contained a line like
264 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
265 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
266 transforms like gmirror may also be affected. ZFS users should
270 The bitstring(3) API has been updated with new functionality and
271 improved performance. But it is binary-incompatible with the old API.
272 Objects built with the new headers may not be linked against objects
273 built with the old headers.
276 The brk and sbrk functions have been removed from libc on arm64.
277 Binutils from ports has been updated to not link to these
278 functions and should be updated to the latest version before
279 installing a new libc.
282 The armv6 port now defaults to hard float ABI. Limited support
283 for running both hardfloat and soft float on the same system
284 is available using the libraries installed with -DWITH_LIBSOFT.
285 This has only been tested as an upgrade path for installworld
286 and packages may fail or need manual intervention to run. New
287 packages will be needed.
289 To update an existing self-hosted armv6hf system, you must add
290 TARGET_ARCH=armv6 on the make command line for both the build
291 and the install steps.
294 Kernel modules compiled outside of a kernel build now default to
295 installing to /boot/modules instead of /boot/kernel. Many kernel
296 modules built this way (such as those in ports) already overrode
297 KMODDIR explicitly to install into /boot/modules. However,
298 manually building and installing a module from /sys/modules will
299 now install to /boot/modules instead of /boot/kernel.
302 The CAM I/O scheduler has been committed to the kernel. There should be
303 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
304 list of known rogues that claim support for this but actually corrupt
305 data is believed to be complete, be on the lookout for data
306 corruption. The known rogue list is believed to be complete:
308 o Crucial MX100, M550 drives with MU01 firmware.
309 o Micron M510 and M550 drives with MU01 firmware.
310 o Micron M500 prior to MU07 firmware
311 o Samsung 830, 840, and 850 all firmwares
312 o FCCT M500 all firmwares
314 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
315 with working NCQ TRIM. For Micron branded drives, see your sales rep for
316 updated firmware. Black listed drives will work correctly because these
317 drives work correctly so long as no NCQ TRIMs are sent to them. Given
318 this list is the same as found in Linux, it's believed there are no
319 other rogues in the market place. All other models from the above
322 To be safe, if you are at all concerned, you can quirk each of your
323 drives to prevent NCQ from being sent by setting:
324 kern.cam.ada.X.quirks="0x2"
325 in loader.conf. If the drive requires the 4k sector quirk, set the
329 The FAST_DEPEND build option has been removed and its functionality is
330 now the one true way. The old mkdep(1) style of 'make depend' has
331 been removed. See 20160311 for further details.
334 Resource range types have grown from unsigned long to uintmax_t. All
335 drivers, and anything using libdevinfo, need to be recompiled.
338 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
339 builds. It no longer runs mkdep(1) during 'make depend', and the
340 'make depend' stage can safely be skipped now as it is auto ran
341 when building 'make all' and will generate all SRCS and DPSRCS before
342 building anything else. Dependencies are gathered at compile time with
343 -MF flags kept in separate .depend files per object file. Users should
344 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
348 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
349 kernel modules. Therefore, if you load any kernel modules at boot time,
350 please install the boot loaders after you install the kernel, but before
354 make kernel KERNCONF=YOUR_KERNEL_HERE
355 make -C sys/boot install
356 <reboot in single user>
358 Then follow the usual steps, described in the General Notes section,
362 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
363 see the 20141231 entry below for information about prerequisites and
364 upgrading, if you are not already using clang 3.5.0 or higher.
367 The AIO subsystem is now a standard part of the kernel. The
368 VFS_AIO kernel option and aio.ko kernel module have been removed.
369 Due to stability concerns, asynchronous I/O requests are only
370 permitted on sockets and raw disks by default. To enable
371 asynchronous I/O requests on all file types, set the
372 vfs.aio.enable_unsafe sysctl to a non-zero value.
375 The ELF object manipulation tool objcopy is now provided by the
376 ELF Tool Chain project rather than by GNU binutils. It should be a
377 drop-in replacement, with the addition of arm64 support. The
378 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
379 to obtain the GNU version if necessary.
382 Building ZFS pools on top of zvols is prohibited by default. That
383 feature has never worked safely; it's always been prone to deadlocks.
384 Using a zvol as the backing store for a VM guest's virtual disk will
385 still work, even if the guest is using ZFS. Legacy behavior can be
386 restored by setting vfs.zfs.vol.recursive=1.
389 The NONE and HPN patches has been removed from OpenSSH. They are
390 still available in the security/openssh-portable port.
393 With the addition of ypldap(8), a new _ypldap user is now required
394 during installworld. "mergemaster -p" can be used to add the user
395 prior to installworld, as documented in the handbook.
398 The tftp loader (pxeboot) now uses the option root-path directive. As a
399 consequence it no longer looks for a pxeboot.4th file on the tftp
400 server. Instead it uses the regular /boot infrastructure as with the
404 The code to start recording plug and play data into the modules has
405 been committed. While the old tools will properly build a new kernel,
406 a number of warnings about "unknown metadata record 4" will be produced
407 for an older kldxref. To avoid such warnings, make sure to rebuild
408 the kernel toolchain (or world). Make sure that you have r292078 or
409 later when trying to build 292077 or later before rebuilding.
412 Debug data files are now built by default with 'make buildworld' and
413 installed with 'make installworld'. This facilitates debugging but
414 requires more disk space both during the build and for the installed
415 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
419 r291527 changed the internal interface between the nfsd.ko and
420 nfscommon.ko modules. As such, they must both be upgraded to-gether.
421 __FreeBSD_version has been bumped because of this.
424 Add support for unicode collation strings leads to a change of
425 order of files listed by ls(1) for example. To get back to the old
426 behaviour, set LC_COLLATE environment variable to "C".
428 Databases administrators will need to reindex their databases given
429 collation results will be different.
431 Due to a bug in install(1) it is recommended to remove the ancient
432 locales before running make installworld.
434 rm -rf /usr/share/locale/*
437 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
438 libcrypto.so.7 or libssl.so.7 must be recompiled.
441 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
442 Kernel modules isp_2400_multi and isp_2500_multi were removed and
443 should be replaced with isp_2400 and isp_2500 modules respectively.
446 The build previously allowed using 'make -n' to not recurse into
447 sub-directories while showing what commands would be executed, and
448 'make -n -n' to recursively show commands. Now 'make -n' will recurse
449 and 'make -N' will not.
452 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
453 and etcupdate will now use this file. A custom sendmail.cf is now
454 updated via this mechanism rather than via installworld. If you had
455 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
456 want to remove the exclusion or change it to "always install".
457 /etc/mail/sendmail.cf is now managed the same way regardless of
458 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
459 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
462 Compatibility shims for legacy ATA device names have been removed.
463 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
464 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
465 environment variables, /dev/ad* and /dev/ar* symbolic links.
468 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
469 Please see the 20141231 entry below for information about prerequisites
470 and upgrading, if you are not already using clang 3.5.0 or higher.
473 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
474 and renamed from .symbols to .debug. This reduces the size requirements
475 on the boot partition or file system and provides consistency with
476 userland debug files.
478 When using the supported kernel installation method the
479 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
480 as is done with /boot/kernel.
482 Developers wishing to maintain the historical behavior of installing
483 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
486 The wireless drivers had undergone changes that remove the 'parent
487 interface' from the ifconfig -l output. The rc.d network scripts
488 used to check presence of a parent interface in the list, so old
489 scripts would fail to start wireless networking. Thus, etcupdate(3)
490 or mergemaster(8) run is required after kernel update, to update your
491 rc.d scripts in /etc.
494 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
495 These configurations are now automatically interpreted as
496 'scrub fragment reassemble'.
499 Kernel-loadable modules for the random(4) device are back. To use
500 them, the kernel must have
503 options RANDOM_LOADABLE
505 kldload(8) can then be used to load random_fortuna.ko
506 or random_yarrow.ko. Please note that due to the indirect
507 function calls that the loadable modules need to provide,
508 the build-in variants will be slightly more efficient.
510 The random(4) kernel option RANDOM_DUMMY has been retired due to
511 unpopularity. It was not all that useful anyway.
514 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
515 Control over building the ELF Tool Chain tools is now provided by
516 the WITHOUT_TOOLCHAIN knob.
519 The polarity of Pulse Per Second (PPS) capture events with the
520 uart(4) driver has been corrected. Prior to this change the PPS
521 "assert" event corresponded to the trailing edge of a positive PPS
522 pulse and the "clear" event was the leading edge of the next pulse.
524 As the width of a PPS pulse in a typical GPS receiver is on the
525 order of 1 millisecond, most users will not notice any significant
526 difference with this change.
528 Anyone who has compensated for the historical polarity reversal by
529 configuring a negative offset equal to the pulse width will need to
530 remove that workaround.
533 The default group assigned to /dev/dri entries has been changed
534 from 'wheel' to 'video' with the id of '44'. If you want to have
535 access to the dri devices please add yourself to the video group
538 # pw groupmod video -m $USER
541 The menu.rc and loader.rc files will now be replaced during
542 upgrades. Please migrate local changes to menu.rc.local and
543 loader.rc.local instead.
546 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
547 strings and strip have been removed. The src.conf(5) knob
548 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
551 As ZFS requires more kernel stack pages than is the default on some
552 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
553 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
555 Please consider using 'options KSTACK_PAGES=X' where X is greater
556 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
559 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
560 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
561 default, i.e., they will not contain "::". For example, instead
562 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
563 to have a more specific match, such as different map entries for
564 IPv6:0:0 vs IPv6:0. This change requires that configuration
565 data (including maps, files, classes, custom ruleset, etc.) must
566 use the same format, so make certain such configuration data is
567 upgrading. As a very simple check search for patterns like
568 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
569 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
570 the cf option UseCompressedIPv6Addresses.
573 The default kernel entropy-processing algorithm is now
574 Fortuna, replacing Yarrow.
576 Assuming you have 'device random' in your kernel config
577 file, the configurations allow a kernel option to override
578 this default. You may choose *ONE* of:
580 options RANDOM_YARROW # Legacy /dev/random algorithm.
581 options RANDOM_DUMMY # Blocking-only driver.
583 If you have neither, you get Fortuna. For most people,
584 read no further, Fortuna will give a /dev/random that works
585 like it always used to, and the difference will be irrelevant.
587 If you remove 'device random', you get *NO* kernel-processed
588 entropy at all. This may be acceptable to folks building
589 embedded systems, but has complications. Carry on reading,
590 and it is assumed you know what you need.
592 *PLEASE* read random(4) and random(9) if you are in the
593 habit of tweaking kernel configs, and/or if you are a member
594 of the embedded community, wanting specific and not-usual
595 behaviour from your security subsystems.
597 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
598 random', you will NOT have a functioning /dev/random, and
599 many cryptographic features will not work, including SSH.
600 You may also find strange behaviour from the random(3) set
601 of library functions, in particular sranddev(3), srandomdev(3)
602 and arc4random(3). The reason for this is that the KERN_ARND
603 sysctl only returns entropy if it thinks it has some to
604 share, and with RANDOM_DUMMY or no 'device random' this
608 An additional fix for the issue described in the 20150614 sendmail
609 entry below has been been committed in revision 284717.
612 FreeBSD's old make (fmake) has been removed from the system. It is
613 available as the devel/fmake port or via pkg install fmake.
616 The fix for the issue described in the 20150614 sendmail entry
617 below has been been committed in revision 284436. The work
618 around described in that entry is no longer needed unless the
619 default setting is overridden by a confDH_PARAMETERS configuration
620 setting of '5' or pointing to a 512 bit DH parameter file.
623 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
624 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
625 and devel/kyua to version 0.20+ and adjust any calling code to work
626 with Kyuafile and kyua.
629 The import of openssl to address the FreeBSD-SA-15:10.openssl
630 security advisory includes a change which rejects handshakes
631 with DH parameters below 768 bits. sendmail releases prior
632 to 8.15.2 (not yet released), defaulted to a 512 bit
633 DH parameter setting for client connections. To work around
634 this interoperability, sendmail can be configured to use a
635 2048 bit DH parameter by:
637 1. Edit /etc/mail/`hostname`.mc
638 2. If a setting for confDH_PARAMETERS does not exist or
639 exists and is set to a string beginning with '5',
641 3. If a setting for confDH_PARAMETERS exists and is set to
642 a file path, create a new file with:
643 openssl dhparam -out /path/to/file 2048
644 4. Rebuild the .cf file:
645 cd /etc/mail/; make; make install
647 cd /etc/mail/; make restart
649 A sendmail patch is coming, at which time this file will be
653 Generation of legacy formatted entries have been disabled by default
654 in pwd_mkdb(8), as all base system consumers of the legacy formatted
655 entries were converted to use the new format by default when the new,
656 machine independent format have been added and supported since FreeBSD
659 Please see the pwd_mkdb(8) manual page for further details.
662 Clang and llvm have been upgraded to 3.6.1 release. Please see the
663 20141231 entry below for information about prerequisites and upgrading,
664 if you are not already using 3.5.0 or higher.
667 TI platform code switched to using vendor DTS files and this update
668 may break existing systems running on Beaglebone, Beaglebone Black,
671 - dtb files should be regenerated/reinstalled. Filenames are the
672 same but content is different now
673 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
674 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
675 addressing scheme is now pin 25 on /dev/gpioc3.
676 - Pandaboard: /etc/ttys should be updated, serial console device is
677 now /dev/ttyu2, not /dev/ttyu0
680 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
681 If you need the GNU extension from groff soelim(1), install groff
682 from package: pkg install groff, or via ports: textproc/groff.
685 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
686 defined in symlink(7); previously symlinks were silently ignored.
689 The const qualifier has been removed from iconv(3) to comply with
690 POSIX. The ports tree is aware of this from r384038 onwards.
693 Libraries specified by LIBADD in Makefiles must have a corresponding
694 DPADD_<lib> variable to ensure correct dependencies. This is now
695 enforced in src.libnames.mk.
698 From legacy ata(4) driver was removed support for SATA controllers
699 supported by more functional drivers ahci(4), siis(4) and mvs(4).
700 Kernel modules ataahci and ataadaptec were removed completely,
701 replaced by ahci and mvs modules respectively.
704 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
705 the 20141231 entry below for information about prerequisites and
706 upgrading, if you are not already using 3.5.0 or higher.
709 The 32-bit PowerPC kernel has been changed to a position-independent
710 executable. This can only be booted with a version of loader(8)
711 newer than January 31, 2015, so make sure to update both world and
712 kernel before rebooting.
715 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
716 but before r278950, the RNG was not seeded properly. Immediately
717 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
718 ssh keys or openssl keys) that were generated w/ a kernel from that
719 range. This does not affect programs that directly used /dev/random
720 or /dev/urandom. All userland uses of arc4random(3) are affected.
723 The autofs(4) ABI was changed in order to restore binary compatibility
724 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
728 The powerpc64 kernel has been changed to a position-independent
729 executable. This can only be booted with a new version of loader(8),
730 so make sure to update both world and kernel before rebooting.
733 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
734 only release, no new features have been added. Please see the 20141231
735 entry below for information about prerequisites and upgrading, if you
736 are not already using 3.5.0.
739 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
740 taken from the ELF Tool Chain project rather than GNU binutils. They
741 should be drop-in replacements, with the addition of arm64 support.
742 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
743 binutils tools, if necessary. See 20150805 for updated information.
746 The default Unbound configuration now enables remote control
747 using a local socket. Users who have already enabled the
748 local_unbound service should regenerate their configuration
749 by running "service local_unbound setup" as root.
752 The GNU texinfo and GNU info pages have been removed.
753 To be able to view GNU info pages please install texinfo from ports.
756 Clang, llvm and lldb have been upgraded to 3.5.0 release.
758 As of this release, a prerequisite for building clang, llvm and lldb is
759 a C++11 capable compiler and C++11 standard library. This means that to
760 be able to successfully build the cross-tools stage of buildworld, with
761 clang as the bootstrap compiler, your system compiler or cross compiler
762 should either be clang 3.3 or later, or gcc 4.8 or later, and your
763 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
766 On any standard FreeBSD 10.x or 11.x installation, where clang and
767 libc++ are on by default (that is, on x86 or arm), this should work out
770 On 9.x installations where clang is enabled by default, e.g. on x86 and
771 powerpc, libc++ will not be enabled by default, so libc++ should be
772 built (with clang) and installed first. If both clang and libc++ are
773 missing, build clang first, then use it to build libc++.
775 On 8.x and earlier installations, upgrade to 9.x first, and then follow
776 the instructions for 9.x above.
778 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
779 default, and do not build clang.
781 Many embedded systems are resource constrained, and will not be able to
782 build clang in a reasonable time, or in some cases at all. In those
783 cases, cross building bootable systems on amd64 is a workaround.
785 This new version of clang introduces a number of new warnings, of which
786 the following are most likely to appear:
790 This warns in two cases, for both C and C++:
791 * When the code is trying to take the absolute value of an unsigned
792 quantity, which is effectively a no-op, and almost never what was
793 intended. The code should be fixed, if at all possible. If you are
794 sure that the unsigned quantity can be safely cast to signed, without
795 loss of information or undefined behavior, you can add an explicit
796 cast, or disable the warning.
798 * When the code is trying to take an absolute value, but the called
799 abs() variant is for the wrong type, which can lead to truncation.
800 If you want to disable the warning instead of fixing the code, please
801 make sure that truncation will not occur, or it might lead to unwanted
804 -Wtautological-undefined-compare and
805 -Wundefined-bool-conversion
807 These warn when C++ code is trying to compare 'this' against NULL, while
808 'this' should never be NULL in well-defined C++ code. However, there is
809 some legacy (pre C++11) code out there, which actively abuses this
810 feature, which was less strictly defined in previous C++ versions.
812 Squid and openjdk do this, for example. The warning can be turned off
813 for C++98 and earlier, but compiling the code in C++11 mode might result
814 in unexpected behavior; for example, the parts of the program that are
815 unreachable could be optimized away.
818 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
819 kernel sources have been removed. The .h files remain, since some
820 utilities include them. This will need to be fixed later.
821 If "mount -t oldnfs ..." is attempted, it will fail.
822 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
823 the utilities will report errors.
826 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
827 directories to top level SUBDIR variable when their parent
828 directory is included in LOCAL_DIRS. Users with build systems with
829 such hierarchies and without SUBDIR entries in the parent
830 directory Makefiles should add them or add the directories to
834 faith(4) and faithd(8) have been removed from the base system. Faith
835 has been obsolete for a very long time.
838 vt(4), the new console driver, is enabled by default. It brings
839 support for Unicode and double-width characters, as well as
840 support for UEFI and integration with the KMS kernel video
843 You may need to update your console settings in /etc/rc.conf,
844 most probably the keymap. During boot, /etc/rc.d/syscons will
845 indicate what you need to do.
847 vt(4) still has issues and lacks some features compared to
848 syscons(4). See the wiki for up-to-date information:
849 https://wiki.freebsd.org/Newcons
851 If you want to keep using syscons(4), you can do so by adding
852 the following line to /boot/loader.conf:
856 pjdfstest has been integrated into kyua as an opt-in test suite.
857 Please see share/doc/pjdfstest/README for more details on how to
861 gperf has been removed from the base system for architectures
862 that use clang. Ports that require gperf will obtain it from the
866 pjdfstest has been moved from tools/regression/pjdfstest to
870 At svn r271982, The default linux compat kernel ABI has been adjusted
871 to 2.6.18 in support of the linux-c6 compat ports infrastructure
872 update. If you wish to continue using the linux-f10 compat ports,
873 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
874 encouraged to update their linux-compat packages to linux-c6 during
875 their next update cycle.
878 The ofwfb driver, used to provide a graphics console on PowerPC when
879 using vt(4), no longer allows mmap() of all physical memory. This
880 will prevent Xorg on PowerPC with some ATI graphics cards from
881 initializing properly unless x11-servers/xorg-server is updated to
885 The xdev targets have been converted to using TARGET and
886 TARGET_ARCH instead of XDEV and XDEV_ARCH.
889 The default unbound configuration has been modified to address
890 issues with reverse lookups on networks that use private
891 address ranges. If you use the local_unbound service, run
892 "service local_unbound setup" as root to regenerate your
893 configuration, then "service local_unbound reload" to load the
897 The GNU texinfo and GNU info pages are not built and installed
898 anymore, WITH_INFO knob has been added to allow to built and install
900 UPDATE: see 20150102 entry on texinfo's removal
903 The GNU readline library is now an INTERNALLIB - that is, it is
904 statically linked into consumers (GDB and variants) in the base
905 system, and the shared library is no longer installed. The
906 devel/readline port is available for third party software that
910 The Itanium architecture (ia64) has been removed from the list of
911 known architectures. This is the first step in the removal of the
915 Commit r268115 has added NFSv4.1 server support, merged from
916 projects/nfsv4.1-server. Since this includes changes to the
917 internal interfaces between the NFS related modules, a full
918 build of the kernel and modules will be necessary.
919 __FreeBSD_version has been bumped.
922 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
923 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
924 which differs from the behaviour controlled by this knob.)
927 Maximal length of the serial number in CTL was increased from 16 to
928 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
929 and ctld, need to be rebuilt to work with a new kernel.
932 The libatf-c and libatf-c++ major versions were downgraded to 0 and
933 1 respectively to match the upstream numbers. They were out of
934 sync because, when they were originally added to FreeBSD, the
935 upstream versions were not respected. These libraries are private
936 and not yet built by default, so renumbering them should be a
937 non-issue. However, unclean source trees will yield broken test
938 programs once the operator executes "make delete-old-libs" after a
941 Additionally, the atf-sh binary was made private by moving it into
942 /usr/libexec/. Already-built shell test programs will keep the
943 path to the old binary so they will break after "make delete-old"
946 If you are using WITH_TESTS=yes (not the default), wipe the object
947 tree and rebuild from scratch to prevent spurious test failures.
948 This is only needed once: the misnumbered libraries and misplaced
949 binaries have been added to OptionalObsoleteFiles.inc so they will
950 be removed during a clean upgrade.
953 Clang and llvm have been upgraded to 3.4.1 release.
956 We bogusly installed src.opts.mk in /usr/share/mk. This file should
957 be removed to avoid issues in the future (and has been added to
961 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
962 past, it affected all builds that used the bsd.*.mk files. The old
963 behavior was a bug, but people may have relied upon it. To get this
964 behavior back, you can .include /etc/src.conf from /etc/make.conf
965 (which is still global and isn't changed). This also changes the
966 behavior of incremental builds inside the tree of individual
967 directories. Set MAKESYSPATH to ".../share/mk" to do that.
968 Although this has survived make universe and some upgrade scenarios,
969 other upgrade scenarios may have broken. At least one form of
970 temporary breakage was fixed with MAKESYSPATH settings for buildworld
971 as well... In cases where MAKESYSPATH isn't working with this
972 setting, you'll need to set it to the full path to your tree.
974 One side effect of all this cleaning up is that bsd.compiler.mk
975 is no longer implicitly included by bsd.own.mk. If you wish to
976 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
980 The lindev device has been removed since /dev/full has been made a
981 standard device. __FreeBSD_version has been bumped.
984 The knob WITHOUT_VI was added to the base system, which controls
985 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
986 in order to reorder files share/termcap and didn't build ex(1) as a
987 build tool, so building/installing with WITH_VI is highly advised for
988 build hosts for older releases.
990 This issue has been fixed in stable/9 and stable/10 in r277022 and
991 r276991, respectively.
994 The YES_HESIOD knob has been removed. It has been obsolete for
995 a decade. Please move to using WITH_HESIOD instead or your builds
996 will silently lack HESIOD.
999 The uart(4) driver has been changed with respect to its handling
1000 of the low-level console. Previously the uart(4) driver prevented
1001 any process from changing the baudrate or the CLOCAL and HUPCL
1002 control flags. By removing the restrictions, operators can make
1003 changes to the serial console port without having to reboot.
1004 However, when getty(8) is started on the serial device that is
1005 associated with the low-level console, a misconfigured terminal
1006 line in /etc/ttys will now have a real impact.
1007 Before upgrading the kernel, make sure that /etc/ttys has the
1008 serial console device configured as 3wire without baudrate to
1009 preserve the previous behaviour. E.g:
1010 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1013 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1014 to improve performance. To re-enable it, if needed, run rpcbind
1015 with command line option -W.
1018 Switched back to the GPL dtc compiler due to updates in the upstream
1019 dts files not being supported by the BSDL dtc compiler. You will need
1020 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1021 may result while building dtb files during a kernel build if you fail
1022 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1025 Clang and llvm have been upgraded to 3.4 release.
1028 The nve(4) driver has been removed. Please use the nfe(4) driver
1029 for NVIDIA nForce MCP Ethernet adapters instead.
1032 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1033 This could cause certain C++ applications using shared libraries built
1034 against the previous version of libc++ to crash. The incompatibility
1035 has now been fixed, but any C++ applications or shared libraries built
1036 between r261283 and r261801 should be recompiled.
1039 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1040 capability mode support. Please note that enabling the feature in
1041 kernel is still highly recommended.
1044 OpenSSH is now built with sandbox support, and will use sandbox as
1045 the default privilege separation method. This requires Capsicum
1046 capability mode support in kernel.
1049 The libelf and libdwarf libraries have been updated to newer
1050 versions from upstream. Shared library version numbers for
1051 these two libraries were bumped. Any ports or binaries
1052 requiring these two libraries should be recompiled.
1053 __FreeBSD_version is bumped to 1100006.
1056 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1057 instead of providing an explicit one, this would prevent such
1058 Makefile from providing its own Kyuafile in the future during
1059 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1060 intervention is needed to clean an objdir if you use NO_CLEAN:
1061 # find /usr/obj -name Kyuafile | xargs rm -f
1064 The behavior of gss_pseudo_random() for the krb5 mechanism
1065 has changed, for applications requesting a longer random string
1066 than produced by the underlying enctype's pseudo-random() function.
1067 In particular, the random string produced from a session key of
1068 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1069 be different at the 17th octet and later, after this change.
1070 The counter used in the PRF+ construction is now encoded as a
1071 big-endian integer in accordance with RFC 4402.
1072 __FreeBSD_version is bumped to 1100004.
1075 The WITHOUT_ATF build knob has been removed and its functionality
1076 has been subsumed into the more generic WITHOUT_TESTS. If you were
1077 using the former to disable the build of the ATF libraries, you
1078 should change your settings to use the latter.
1081 The default version of mtree is nmtree which is obtained from
1082 NetBSD. The output is generally the same, but may vary
1083 slightly. If you found you need identical output adding
1084 "-F freebsd9" to the command line should do the trick. For the
1085 time being, the old mtree is available as fmtree.
1088 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1089 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1090 1.1.4_8 and verify bsdyml not linked in, before running "make
1092 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1094 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1097 The stable/10 branch has been created in subversion from head
1101 The rc.d/jail script has been updated to support jail(8)
1102 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1103 for per-jail configuration are automatically converted to
1104 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1105 This is transparently backward compatible. See below about some
1106 incompatibilities and rc.conf(5) manual page for more details.
1108 These variables are now deprecated in favor of jail(8) configuration
1109 file. One can use "rc.d/jail config <jname>" command to generate
1110 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1111 running the jail(8) utility. The default pathname of the
1112 configuration file is /etc/jail.conf and can be specified by
1113 using $jail_conf or $jail_<jname>_conf variables.
1115 Please note that jail_devfs_ruleset accepts an integer at
1116 this moment. Please consider to rewrite the ruleset name
1120 BIND has been removed from the base system. If all you need
1121 is a local resolver, simply enable and start the local_unbound
1122 service instead. Otherwise, several versions of BIND are
1123 available in the ports tree. The dns/bind99 port is one example.
1125 With this change, nslookup(1) and dig(1) are no longer in the base
1126 system. Users should instead use host(1) and drill(1) which are
1127 in the base system. Alternatively, nslookup and dig can
1128 be obtained by installing the dns/bind-tools port.
1131 With the addition of unbound(8), a new unbound user is now
1132 required during installworld. "mergemaster -p" can be used to
1133 add the user prior to installworld, as documented in the handbook.
1136 OpenSSH is now built with DNSSEC support, and will by default
1137 silently trust signed SSHFP records. This can be controlled with
1138 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1139 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1142 The GNU Compiler Collection and C++ standard library (libstdc++)
1143 are no longer built by default on platforms where clang is the system
1144 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1145 options in src.conf.
1148 The PROCDESC kernel option is now part of the GENERIC kernel
1149 configuration and is required for the rwhod(8) to work.
1150 If you are using custom kernel configuration, you should include
1154 The API and ABI related to the Capsicum framework was modified
1155 in backward incompatible way. The userland libraries and programs
1156 have to be recompiled to work with the new kernel. This includes the
1157 following libraries and programs, but the whole buildworld is
1158 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1159 kdump, procstat, rwho, rwhod, uniq.
1162 AES-NI intrinsic support has been added to gcc. The AES-NI module
1163 has been updated to use this support. A new gcc is required to build
1164 the aesni module on both i386 and amd64.
1167 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1168 Thus "device padlock_rng" and "device rdrand_rng" should be
1169 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1172 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1173 enables just the iconv* functionality and is now on by default.
1174 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1175 compatibility. Set WITHOUT_ICONV to build the old way.
1176 If you have been using WITH_ICONV before, you will very likely
1177 need to turn on WITH_LIBICONV_COMPAT.
1180 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1181 Illumos origin, including ZFS. If you have INVARIANTS in your
1182 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1184 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1185 locks if WITNESS option was set. Because that generated a lot of
1186 witness(9) reports and all of them were believed to be false
1187 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1188 can be used to achieve the previous behavior.
1191 Timer values in IPv6 data structures now use time_uptime instead
1192 of time_second. Although this is not a user-visible functional
1193 change, userland utilities which directly use them---ndp(8),
1194 rtadvd(8), and rtsold(8) in the base system---need to be updated
1195 to r253970 or later.
1198 find -delete can now delete the pathnames given as arguments,
1199 instead of only files found below them or if the pathname did
1200 not contain any slashes. Formerly, the following error message
1203 find: -delete: <path>: relative path potentially not safe
1205 Deleting the pathnames given as arguments can be prevented
1206 without error messages using -mindepth 1 or by changing
1207 directory and passing "." as argument to find. This works in the
1208 old as well as the new version of find.
1211 Behavior of devfs rules path matching has been changed.
1212 Pattern is now always matched against fully qualified devfs
1213 path and slash characters must be explicitly matched by
1214 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1215 subdirectories must be reviewed.
1218 The default ARM ABI has changed to the ARM EABI. The old ABI is
1219 incompatible with the ARM EABI and all programs and modules will
1220 need to be rebuilt to work with a new kernel.
1222 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1224 NOTE: Support for the old ABI will be removed in the future and
1225 users are advised to upgrade.
1228 pkg_install has been disconnected from the build if you really need it
1229 you should add WITH_PKGTOOLS in your src.conf(5).
1232 Most of network statistics structures were changed to be able
1233 keep 64-bits counters. Thus all tools, that work with networking
1234 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1237 Fix a bug that allowed a tracing process (e.g. gdb) to write
1238 to a memory-mapped file in the traced process's address space
1239 even if neither the traced process nor the tracing process had
1240 write access to that file.
1243 CVS has been removed from the base system. An exact copy
1244 of the code is available from the devel/cvs port.
1247 Some people report the following error after the switch to bmake:
1249 make: illegal option -- J
1250 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1252 *** [buildworld] Error code 2
1254 this likely due to an old instance of make in
1255 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1256 which src/Makefile will use that blindly, if it exists, so if
1257 you see the above error:
1259 rm -rf `make -V MAKEPATH`
1264 Use bmake by default.
1265 Whereas before one could choose to build with bmake via
1266 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1267 make. The goal is to remove these knobs for 10-RELEASE.
1269 It is worth noting that bmake (like gmake) treats the command
1270 line as the unit of failure, rather than statements within the
1271 command line. Thus '(cd some/where && dosomething)' is safer
1272 than 'cd some/where; dosomething'. The '()' allows consistent
1273 behavior in parallel build.
1276 Fix a bug that allows NFS clients to issue READDIR on files.
1279 The WITHOUT_IDEA option has been removed because
1280 the IDEA patent expired.
1283 The sysctl which controls TRIM support under ZFS has been renamed
1284 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1288 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1289 rather than creating it's own in the temporary directory in
1290 order allow access to bootstrapped versions of tools such as
1291 install and mtree. When upgrading from version of FreeBSD where
1292 the install command does not support -l, you will need to
1293 install a new mergemaster command if mergemaster -p is required.
1294 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1298 Legacy ATA stack, disabled and replaced by new CAM-based one since
1299 FreeBSD 9.0, completely removed from the sources. Kernel modules
1300 atadisk and atapi*, user-level tools atacontrol and burncd are
1301 removed. Kernel option `options ATA_CAM` is now permanently enabled
1305 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1306 and socketpair(2). Software, in particular Kerberos, may
1307 automatically detect and use these during building. The resulting
1308 binaries will not work on older kernels.
1311 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1312 information, see the respective 20130304 entry).
1315 Recent commits to callout(9) changed the size of struct callout,
1316 so the KBI is probably heavily disturbed. Also, some functions
1317 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1318 by macros. Every kernel module using it won't load, so rebuild
1321 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1322 but does not initialize by default (because of the new CTL_DISABLE
1323 option) to save memory. To re-enable it, remove the CTL_DISABLE
1324 option from the kernel config file or set kern.cam.ctl.disable=0
1325 in /boot/loader.conf.
1328 The ctl device has been disabled in GENERIC for i386 and amd64.
1329 This was done due to the extra memory being allocated at system
1330 initialisation time by the ctl driver which was only used if
1331 a CAM target device was created. This makes a FreeBSD system
1332 unusable on 128MB or less of RAM.
1335 A new compression method (lz4) has been merged to -HEAD. Please
1336 refer to zpool-features(7) for more information.
1338 Please refer to the "ZFS notes" section of this file for information
1339 on upgrading boot ZFS pools.
1342 A BSD-licensed patch(1) variant has been added and is installed
1343 as bsdpatch, being the GNU version the default patch.
1344 To inverse the logic and use the BSD-licensed one as default,
1345 while having the GNU version installed as gnupatch, rebuild
1346 and install world with the WITH_BSD_PATCH knob set.
1349 Due to the use of the new -l option to install(1) during build
1350 and install, you must take care not to directly set the INSTALL
1351 make variable in your /etc/make.conf, /etc/src.conf, or on the
1352 command line. If you wish to use the -C flag for all installs
1353 you may be able to add INSTALL+=-C to /etc/make.conf or
1357 The install(1) option -M has changed meaning and now takes an
1358 argument that is a file or path to append logs to. In the
1359 unlikely event that -M was the last option on the command line
1360 and the command line contained at least two files and a target
1361 directory the first file will have logs appended to it. The -M
1362 option served little practical purpose in the last decade so its
1363 use is expected to be extremely rare.
1366 After switching to Clang as the default compiler some users of ZFS
1367 on i386 systems started to experience stack overflow kernel panics.
1368 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1371 GEOM_LABEL now mangles label names read from file system metadata.
1372 Mangling affect labels containing spaces, non-printable characters,
1373 '%' or '"'. Device names in /etc/fstab and other places may need to
1377 By default, only the 10 most recent kernel dumps will be saved. To
1378 restore the previous behaviour (no limit on the number of kernel dumps
1379 stored in the dump directory) add the following line to /etc/rc.conf:
1384 With the addition of auditdistd(8), a new auditdistd user is now
1385 required during installworld. "mergemaster -p" can be used to
1386 add the user prior to installworld, as documented in the handbook.
1389 The sin6_scope_id member variable in struct sockaddr_in6 is now
1390 filled by the kernel before passing the structure to the userland via
1391 sysctl or routing socket. This means the KAME-specific embedded scope
1392 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1393 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1394 __FreeBSD_version is bumped to 1000025.
1397 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1398 This means that the world and kernel will be compiled with clang
1399 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1400 and /usr/bin/cpp. To disable this behavior and revert to building
1401 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1402 of current may need to bootstrap WITHOUT_CLANG first if the clang
1403 build fails (its compatibility window doesn't extend to the 9 stable
1407 The IPFIREWALL_FORWARD kernel option has been removed. Its
1408 functionality now turned on by default.
1411 The ZERO_COPY_SOCKET kernel option has been removed and
1412 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1413 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1414 mechanism which is not safe and may result in kernel crashes.
1415 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1416 driver supports disposeable external page sized mbuf storage.
1417 Proper replacements for both zero-copy mechanisms are under
1418 consideration and will eventually lead to complete removal
1419 of the two kernel options.
1422 The IPv4 network stack has been converted to network byte
1423 order. The following modules need to be recompiled together
1424 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1425 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1428 Support for non-MPSAFE filesystems was removed from VFS. The
1429 VFS_VERSION was bumped, all filesystem modules shall be
1433 All the non-MPSAFE filesystems have been disconnected from
1434 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1435 portalfs, smbfs, xfs.
1438 The interface cloning API and ABI has changed. The following
1439 modules need to be recompiled together with kernel:
1440 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1441 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1442 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1445 The sdhci driver was split in two parts: sdhci (generic SD Host
1446 Controller logic) and sdhci_pci (actual hardware driver).
1447 No kernel config modifications are required, but if you
1448 load sdhc as a module you must switch to sdhci_pci instead.
1451 Import the FUSE kernel and userland support into base system.
1454 The GNU sort(1) program has been removed since the BSD-licensed
1455 sort(1) has been the default for quite some time and no serious
1456 problems have been reported. The corresponding WITH_GNU_SORT
1460 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1461 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1465 The net80211(4) ABI has been changed to allow for improved driver
1466 PS-POLL and power-save support. All wireless drivers need to be
1467 recompiled to work with the new kernel.
1470 The random(4) support for the VIA hardware random number
1471 generator (`PADLOCK') is no longer enabled unconditionally.
1472 Add the padlock_rng device in the custom kernel config if
1473 needed. The GENERIC kernels on i386 and amd64 do include the
1474 device, so the change only affects the custom kernel
1478 The pf(4) packet filter ABI has been changed. pfctl(8) and
1479 snmp_pf module need to be recompiled to work with new kernel.
1482 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1483 to -HEAD. Pools that have empty_bpobj in active state can not be
1484 imported read-write with ZFS implementations that do not support
1485 this feature. For more information read the zpool-features(5)
1489 The sparc64 ZFS loader has been changed to no longer try to auto-
1490 detect ZFS providers based on diskN aliases but now requires these
1491 to be explicitly listed in the OFW boot-device environment variable.
1494 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1495 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1496 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1499 The following sysctls and tunables have been renamed for consistency
1500 with other variables:
1501 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1502 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1505 The sort utility has been replaced with BSD sort. For now, GNU sort
1506 is also available as "gnusort" or the default can be set back to
1507 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1508 installed as "bsdsort".
1511 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1512 Starting with this version the old system of ZFS pool versioning
1513 is superseded by "feature flags". This concept enables forward
1514 compatibility against certain future changes in functionality of ZFS
1515 pools. The first read-only compatible "feature flag" for ZFS pools
1516 is named "com.delphix:async_destroy". For more information
1517 read the new zpool-features(5) manual page.
1518 Please refer to the "ZFS notes" section of this file for information
1519 on upgrading boot ZFS pools.
1522 The malloc(3) implementation embedded in libc now uses sources imported
1523 as contrib/jemalloc. The most disruptive API change is to
1524 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1525 delete it prior to installworld, and optionally re-create it using the
1526 new format after rebooting. See malloc.conf(5) for details
1527 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1531 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1532 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1533 now spelled mips. This is to aid compatibility with third-party
1534 software that expects this naming scheme in uname(3). Little-endian
1535 settings are unchanged. If you are updating a big-endian mips64 machine
1536 from before this change, you may need to set MACHINE_ARCH=mips64 in
1537 your environment before the new build system will recognize your machine.
1540 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1544 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1545 nullfs(5) did not pass through all behaviours to the underlying layer,
1546 as a result if we bound to a socket on the lower layer we could connect
1547 only to the lower path; if we bound to the upper layer we could connect
1548 only to the upper path. The new behavior is one can connect to both the
1549 lower and the upper paths regardless what layer path one binds to.
1552 The getifaddrs upgrade path broken with 20111215 has been restored.
1553 If you have upgraded in between 20111215 and 20120209 you need to
1554 recompile libc again with your kernel. You still need to recompile
1555 world to be able to configure CARP but this restriction already
1556 comes from 20111215.
1559 The set_rcvar() function has been removed from /etc/rc.subr. All
1560 base and ports rc.d scripts have been updated, so if you have a
1561 port installed with a script in /usr/local/etc/rc.d you can either
1562 hand-edit the rcvar= line, or reinstall the port.
1564 An easy way to handle the mass-update of /etc/rc.d:
1565 rm /etc/rc.d/* && mergemaster -i
1568 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1569 on the current CPU and prevents other threads from running.
1570 This behavior can be reverted using the kern.stop_scheduler_on_panic
1572 The new behavior can be incompatible with kern.sync_on_panic.
1575 The carp(4) facility has been changed significantly. Configuration
1576 of the CARP protocol via ifconfig(8) has changed, as well as format
1577 of CARP events submitted to devd(8) has changed. See manual pages
1578 for more information. The arpbalance feature of carp(4) is currently
1579 not supported anymore.
1581 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1582 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1583 need to be recompiled.
1586 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1590 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1591 explicitely support non-MPSAFE filesystems.
1592 It is on by default for all supported platform at this present
1596 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1597 i386 and pc98 GENERIC kernel configuration files.
1600 sysinstall has been removed
1603 The stable/9 branch created in subversion. This corresponds to the
1604 RELENG_9 branch in CVS.
1610 Avoid using make -j when upgrading. While generally safe, there are
1611 sometimes problems using -j to upgrade. If your upgrade fails with
1612 -j, please try again without -j. From time to time in the past there
1613 have been problems using -j with buildworld and/or installworld. This
1614 is especially true when upgrading between "distant" versions (eg one
1615 that cross a major release boundary or several minor releases, or when
1616 several months have passed on the -current branch).
1618 Sometimes, obscure build problems are the result of environment
1619 poisoning. This can happen because the make utility reads its
1620 environment when searching for values for global variables. To run
1621 your build attempts in an "environmental clean room", prefix all make
1622 commands with 'env -i '. See the env(1) manual page for more details.
1624 When upgrading from one major version to another it is generally best to
1625 upgrade to the latest code in the currently installed branch first, then
1626 do an upgrade to the new branch. This is the best-tested upgrade path,
1627 and has the highest probability of being successful. Please try this
1628 approach if you encounter problems with a major version upgrade. Since
1629 the stable 4.x branch point, one has generally been able to upgade from
1630 anywhere in the most recent stable branch to head / current (or even the
1631 last couple of stable branches). See the top of this file when there's
1634 When upgrading a live system, having a root shell around before
1635 installing anything can help undo problems. Not having a root shell
1636 around can lead to problems if pam has changed too much from your
1637 starting point to allow continued authentication after the upgrade.
1639 This file should be read as a log of events. When a later event changes
1640 information of a prior event, the prior event should not be deleted.
1641 Instead, a pointer to the entry with the new information should be
1642 placed in the old entry. Readers of this file should also sanity check
1643 older entries before relying on them blindly. Authors of new entries
1644 should write them with this in mind.
1648 When upgrading the boot ZFS pool to a new version, always follow
1651 1.) recompile and reinstall the ZFS boot loader and boot block
1652 (this is part of "make buildworld" and "make installworld")
1654 2.) update the ZFS boot block on your boot drive
1656 The following example updates the ZFS boot block on the first
1657 partition (freebsd-boot) of a GPT partitioned drive ada0:
1658 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1660 Non-boot pools do not need these updates.
1664 If you are updating from a prior version of FreeBSD (even one just
1665 a few days old), you should follow this procedure. It is the most
1666 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1668 make kernel-toolchain
1669 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1670 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1672 To test a kernel once
1673 ---------------------
1674 If you just want to boot a kernel once (because you are not sure
1675 if it works, or if you want to boot a known bad kernel to provide
1676 debugging information) run
1677 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1678 nextboot -k testkernel
1680 To just build a kernel when you know that it won't mess you up
1681 --------------------------------------------------------------
1682 This assumes you are already running a CURRENT system. Replace
1683 ${arch} with the architecture of your machine (e.g. "i386",
1684 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1686 cd src/sys/${arch}/conf
1687 config KERNEL_NAME_HERE
1688 cd ../compile/KERNEL_NAME_HERE
1693 If this fails, go to the "To build a kernel" section.
1695 To rebuild everything and install it on the current system.
1696 -----------------------------------------------------------
1697 # Note: sometimes if you are running current you gotta do more than
1698 # is listed here if you are upgrading from a really old current.
1700 <make sure you have good level 0 dumps>
1702 make kernel KERNCONF=YOUR_KERNEL_HERE
1704 <reboot in single user> [3]
1711 To cross-install current onto a separate partition
1712 --------------------------------------------------
1713 # In this approach we use a separate partition to hold
1714 # current's root, 'usr', and 'var' directories. A partition
1715 # holding "/", "/usr" and "/var" should be about 2GB in
1718 <make sure you have good level 0 dumps>
1721 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1722 <maybe newfs current's root partition>
1723 <mount current's root partition on directory ${CURRENT_ROOT}>
1724 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1725 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1726 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1727 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1728 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1729 <reboot into current>
1730 <do a "native" rebuild/install as described in the previous section>
1731 <maybe install compatibility libraries from ports/misc/compat*>
1735 To upgrade in-place from stable to current
1736 ----------------------------------------------
1737 <make sure you have good level 0 dumps>
1739 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1741 <reboot in single user> [3]
1748 Make sure that you've read the UPDATING file to understand the
1749 tweaks to various things you need. At this point in the life
1750 cycle of current, things change often and you are on your own
1751 to cope. The defaults can also change, so please read ALL of
1752 the UPDATING entries.
1754 Also, if you are tracking -current, you must be subscribed to
1755 freebsd-current@freebsd.org. Make sure that before you update
1756 your sources that you have read and understood all the recent
1757 messages there. If in doubt, please track -stable which has
1758 much fewer pitfalls.
1760 [1] If you have third party modules, such as vmware, you
1761 should disable them at this point so they don't crash your
1764 [3] From the bootblocks, boot -s, and then do
1769 adjkerntz -i # if CMOS is wall time
1770 Also, when doing a major release upgrade, it is required that
1771 you boot into single user mode to do the installworld.
1773 [4] Note: This step is non-optional. Failure to do this step
1774 can result in a significant reduction in the functionality of the
1775 system. Attempting to do it by hand is not recommended and those
1776 that pursue this avenue should read this file carefully, as well
1777 as the archives of freebsd-current and freebsd-hackers mailing lists
1778 for potential gotchas. The -U option is also useful to consider.
1779 See mergemaster(8) for more information.
1781 [5] Usually this step is a noop. However, from time to time
1782 you may need to do this if you get unknown user in the following
1783 step. It never hurts to do it all the time. You may need to
1784 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1785 install) after the buildworld before this step if you last updated
1786 from current before 20130425 or from -stable before 20130430.
1788 [6] This only deletes old files and directories. Old libraries
1789 can be deleted by "make delete-old-libs", but you have to make
1790 sure that no program is using those libraries anymore.
1792 [8] In order to have a kernel that can run the 4.x binaries needed to
1793 do an installworld, you must include the COMPAT_FREEBSD4 option in
1794 your kernel. Failure to do so may leave you with a system that is
1795 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1796 required to run the 5.x binaries on more recent kernels. And so on
1797 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1799 Make sure that you merge any new devices from GENERIC since the
1800 last time you updated your kernel config file.
1802 [9] When checking out sources, you must include the -P flag to have
1803 cvs prune empty directories.
1805 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1806 "?=" instead of the "=" assignment operator, so that buildworld can
1807 override the CPUTYPE if it needs to.
1809 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1810 not on the command line, or in /etc/make.conf. buildworld will
1811 warn if it is improperly defined.
1814 This file contains a list, in reverse chronological order, of major
1815 breakages in tracking -current. It is not guaranteed to be a complete
1816 list of such breakages, and only contains entries since September 23, 2011.
1817 If you need to see UPDATING entries from before that date, you will need
1818 to fetch an UPDATING file from an older FreeBSD release.
1820 Copyright information:
1822 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1824 Redistribution, publication, translation and use, with or without
1825 modification, in full or in part, in any form or format of this
1826 document are permitted without further permission from the author.
1828 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1829 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1830 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1831 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1832 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1833 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1834 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1835 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1836 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1837 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1838 POSSIBILITY OF SUCH DAMAGE.
1840 Contact Warner Losh if you have any questions about your use of