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 code that provides support for ZFS .zfs/ directory functionality
56 has been reimplemented. It's not possible now to create a snapshot
57 by mkdir under .zfs/snapshot/. That should be the only user visible
61 EISA bus support has been removed. The WITH_EISA option is no longer
65 MCA bus support has been removed.
68 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
69 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
72 The EM_MULTIQUEUE kernel configuration option is deprecated now that
73 the em(4) driver conforms to iflib specifications.
76 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
77 IFLIB. If you have a custom kernel configuration that excludes em(4)
78 but you use igb(4), you need to re-add em(4) to your custom configuration.
81 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
82 Please see the 20141231 entry below for information about prerequisites
83 and upgrading, if you are not already using clang 3.5.0 or higher.
86 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
87 Please see the 20141231 entry below for information about prerequisites
88 and upgrading, if you are not already using clang 3.5.0 or higher.
91 The layout of the pmap structure has changed for powerpc to put the pmap
92 statistics at the front for all CPU variations. libkvm(3) and all tools
93 that link against it need to be recompiled.
96 isl(4) and cyapa(4) drivers now require a new driver,
97 chromebook_platform(4), to work properly on Chromebook-class hardware.
98 On other types of hardware the drivers may need to be configured using
99 device hints. Please see the corresponding manual pages for details.
102 The urtwn(4) driver was merged into rtwn(4) and now consists of
103 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
105 Also, firmware for RTL8188CE was renamed due to possible name
106 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
109 GNU rcs has been removed from base. It is available as packages:
110 - rcs: Latest GPLv3 GNU rcs version.
111 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
115 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
116 modules now requires that the kernel configuration contain the
117 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
120 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
121 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
124 Relocatable object files with the extension of .So have been renamed
125 to use an extension of .pico instead. The purpose of this change is
126 to avoid a name clash with shared libraries on case-insensitive file
127 systems. On those file systems, foo.So is the same file as foo.so.
130 GNU rcs has been turned off by default. It can (temporarily) be built
131 again by adding WITH_RCS knob in src.conf.
132 Otherwise, GNU rcs is available from packages:
133 - rcs: Latest GPLv3 GNU rcs version.
134 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
137 The backup_uses_rcs functionality has been removed from rc.subr.
140 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
141 two separate components, QUEUE_MACRO_DEBUG_TRACE and
142 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
143 QUEUE_MACRO_DEBUG behavior.
146 r304787 changed some ioctl interfaces between the iSCSI userspace
147 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
148 rebuilt to work with new kernels. __FreeBSD_version has been bumped
152 The UDP receive code has been updated to only treat incoming UDP
153 packets that were addressed to an L2 broadcast address as L3
154 broadcast packets. It is not expected that this will affect any
155 standards-conforming UDP application. The new behaviour can be
156 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
160 Remove the openbsd_poll system call.
161 __FreeBSD_version has been bumped because of this.
164 The libc stub for the pipe(2) system call has been replaced with
165 a wrapper that calls the pipe2(2) system call and the pipe(2)
166 system call is now only implemented by the kernels that include
167 "options COMPAT_FREEBSD10" in their config file (this is the
168 default). Users should ensure that this option is enabled in
169 their kernel or upgrade userspace to r302092 before upgrading their
173 CAM will now strip leading spaces from SCSI disks' serial numbers.
174 This will affect users who create UFS filesystems on SCSI disks using
175 those disk's diskid device nodes. For example, if /etc/fstab
176 previously contained a line like
177 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
178 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
179 transforms like gmirror may also be affected. ZFS users should
183 The bitstring(3) API has been updated with new functionality and
184 improved performance. But it is binary-incompatible with the old API.
185 Objects built with the new headers may not be linked against objects
186 built with the old headers.
189 The brk and sbrk functions have been removed from libc on arm64.
190 Binutils from ports has been updated to not link to these
191 functions and should be updated to the latest version before
192 installing a new libc.
195 The armv6 port now defaults to hard float ABI. Limited support
196 for running both hardfloat and soft float on the same system
197 is available using the libraries installed with -DWITH_LIBSOFT.
198 This has only been tested as an upgrade path for installworld
199 and packages may fail or need manual intervention to run. New
200 packages will be needed.
202 To update an existing self-hosted armv6hf system, you must add
203 TARGET_ARCH=armv6 on the make command line for both the build
204 and the install steps.
207 Kernel modules compiled outside of a kernel build now default to
208 installing to /boot/modules instead of /boot/kernel. Many kernel
209 modules built this way (such as those in ports) already overrode
210 KMODDIR explicitly to install into /boot/modules. However,
211 manually building and installing a module from /sys/modules will
212 now install to /boot/modules instead of /boot/kernel.
215 The CAM I/O scheduler has been committed to the kernel. There should be
216 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
217 list of known rogues that claim support for this but actually corrupt
218 data is believed to be complete, be on the lookout for data
219 corruption. The known rogue list is believed to be complete:
221 o Crucial MX100, M550 drives with MU01 firmware.
222 o Micron M510 and M550 drives with MU01 firmware.
223 o Micron M500 prior to MU07 firmware
224 o Samsung 830, 840, and 850 all firmwares
225 o FCCT M500 all firmwares
227 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
228 with working NCQ TRIM. For Micron branded drives, see your sales rep for
229 updated firmware. Black listed drives will work correctly because these
230 drives work correctly so long as no NCQ TRIMs are sent to them. Given
231 this list is the same as found in Linux, it's believed there are no
232 other rogues in the market place. All other models from the above
235 To be safe, if you are at all concerned, you can quirk each of your
236 drives to prevent NCQ from being sent by setting:
237 kern.cam.ada.X.quirks="0x2"
238 in loader.conf. If the drive requires the 4k sector quirk, set the
242 The FAST_DEPEND build option has been removed and its functionality is
243 now the one true way. The old mkdep(1) style of 'make depend' has
244 been removed. See 20160311 for further details.
247 Resource range types have grown from unsigned long to uintmax_t. All
248 drivers, and anything using libdevinfo, need to be recompiled.
251 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
252 builds. It no longer runs mkdep(1) during 'make depend', and the
253 'make depend' stage can safely be skipped now as it is auto ran
254 when building 'make all' and will generate all SRCS and DPSRCS before
255 building anything else. Dependencies are gathered at compile time with
256 -MF flags kept in separate .depend files per object file. Users should
257 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
261 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
262 kernel modules. Therefore, if you load any kernel modules at boot time,
263 please install the boot loaders after you install the kernel, but before
267 make kernel KERNCONF=YOUR_KERNEL_HERE
268 make -C sys/boot install
269 <reboot in single user>
271 Then follow the usual steps, described in the General Notes section,
275 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
276 see the 20141231 entry below for information about prerequisites and
277 upgrading, if you are not already using clang 3.5.0 or higher.
280 The AIO subsystem is now a standard part of the kernel. The
281 VFS_AIO kernel option and aio.ko kernel module have been removed.
282 Due to stability concerns, asynchronous I/O requests are only
283 permitted on sockets and raw disks by default. To enable
284 asynchronous I/O requests on all file types, set the
285 vfs.aio.enable_unsafe sysctl to a non-zero value.
288 The ELF object manipulation tool objcopy is now provided by the
289 ELF Tool Chain project rather than by GNU binutils. It should be a
290 drop-in replacement, with the addition of arm64 support. The
291 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
292 to obtain the GNU version if necessary.
295 Building ZFS pools on top of zvols is prohibited by default. That
296 feature has never worked safely; it's always been prone to deadlocks.
297 Using a zvol as the backing store for a VM guest's virtual disk will
298 still work, even if the guest is using ZFS. Legacy behavior can be
299 restored by setting vfs.zfs.vol.recursive=1.
302 The NONE and HPN patches has been removed from OpenSSH. They are
303 still available in the security/openssh-portable port.
306 With the addition of ypldap(8), a new _ypldap user is now required
307 during installworld. "mergemaster -p" can be used to add the user
308 prior to installworld, as documented in the handbook.
311 The tftp loader (pxeboot) now uses the option root-path directive. As a
312 consequence it no longer looks for a pxeboot.4th file on the tftp
313 server. Instead it uses the regular /boot infrastructure as with the
317 The code to start recording plug and play data into the modules has
318 been committed. While the old tools will properly build a new kernel,
319 a number of warnings about "unknown metadata record 4" will be produced
320 for an older kldxref. To avoid such warnings, make sure to rebuild
321 the kernel toolchain (or world). Make sure that you have r292078 or
322 later when trying to build 292077 or later before rebuilding.
325 Debug data files are now built by default with 'make buildworld' and
326 installed with 'make installworld'. This facilitates debugging but
327 requires more disk space both during the build and for the installed
328 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
332 r291527 changed the internal interface between the nfsd.ko and
333 nfscommon.ko modules. As such, they must both be upgraded to-gether.
334 __FreeBSD_version has been bumped because of this.
337 Add support for unicode collation strings leads to a change of
338 order of files listed by ls(1) for example. To get back to the old
339 behaviour, set LC_COLLATE environment variable to "C".
341 Databases administrators will need to reindex their databases given
342 collation results will be different.
344 Due to a bug in install(1) it is recommended to remove the ancient
345 locales before running make installworld.
347 rm -rf /usr/share/locale/*
350 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
351 libcrypto.so.7 or libssl.so.7 must be recompiled.
354 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
355 Kernel modules isp_2400_multi and isp_2500_multi were removed and
356 should be replaced with isp_2400 and isp_2500 modules respectively.
359 The build previously allowed using 'make -n' to not recurse into
360 sub-directories while showing what commands would be executed, and
361 'make -n -n' to recursively show commands. Now 'make -n' will recurse
362 and 'make -N' will not.
365 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
366 and etcupdate will now use this file. A custom sendmail.cf is now
367 updated via this mechanism rather than via installworld. If you had
368 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
369 want to remove the exclusion or change it to "always install".
370 /etc/mail/sendmail.cf is now managed the same way regardless of
371 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
372 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
375 Compatibility shims for legacy ATA device names have been removed.
376 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
377 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
378 environment variables, /dev/ad* and /dev/ar* symbolic links.
381 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
382 Please see the 20141231 entry below for information about prerequisites
383 and upgrading, if you are not already using clang 3.5.0 or higher.
386 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
387 and renamed from .symbols to .debug. This reduces the size requirements
388 on the boot partition or file system and provides consistency with
389 userland debug files.
391 When using the supported kernel installation method the
392 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
393 as is done with /boot/kernel.
395 Developers wishing to maintain the historical behavior of installing
396 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
399 The wireless drivers had undergone changes that remove the 'parent
400 interface' from the ifconfig -l output. The rc.d network scripts
401 used to check presence of a parent interface in the list, so old
402 scripts would fail to start wireless networking. Thus, etcupdate(3)
403 or mergemaster(8) run is required after kernel update, to update your
404 rc.d scripts in /etc.
407 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
408 These configurations are now automatically interpreted as
409 'scrub fragment reassemble'.
412 Kernel-loadable modules for the random(4) device are back. To use
413 them, the kernel must have
416 options RANDOM_LOADABLE
418 kldload(8) can then be used to load random_fortuna.ko
419 or random_yarrow.ko. Please note that due to the indirect
420 function calls that the loadable modules need to provide,
421 the build-in variants will be slightly more efficient.
423 The random(4) kernel option RANDOM_DUMMY has been retired due to
424 unpopularity. It was not all that useful anyway.
427 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
428 Control over building the ELF Tool Chain tools is now provided by
429 the WITHOUT_TOOLCHAIN knob.
432 The polarity of Pulse Per Second (PPS) capture events with the
433 uart(4) driver has been corrected. Prior to this change the PPS
434 "assert" event corresponded to the trailing edge of a positive PPS
435 pulse and the "clear" event was the leading edge of the next pulse.
437 As the width of a PPS pulse in a typical GPS receiver is on the
438 order of 1 millisecond, most users will not notice any significant
439 difference with this change.
441 Anyone who has compensated for the historical polarity reversal by
442 configuring a negative offset equal to the pulse width will need to
443 remove that workaround.
446 The default group assigned to /dev/dri entries has been changed
447 from 'wheel' to 'video' with the id of '44'. If you want to have
448 access to the dri devices please add yourself to the video group
451 # pw groupmod video -m $USER
454 The menu.rc and loader.rc files will now be replaced during
455 upgrades. Please migrate local changes to menu.rc.local and
456 loader.rc.local instead.
459 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
460 strings and strip have been removed. The src.conf(5) knob
461 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
464 As ZFS requires more kernel stack pages than is the default on some
465 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
466 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
468 Please consider using 'options KSTACK_PAGES=X' where X is greater
469 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
472 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
473 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
474 default, i.e., they will not contain "::". For example, instead
475 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
476 to have a more specific match, such as different map entries for
477 IPv6:0:0 vs IPv6:0. This change requires that configuration
478 data (including maps, files, classes, custom ruleset, etc.) must
479 use the same format, so make certain such configuration data is
480 upgrading. As a very simple check search for patterns like
481 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
482 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
483 the cf option UseCompressedIPv6Addresses.
486 The default kernel entropy-processing algorithm is now
487 Fortuna, replacing Yarrow.
489 Assuming you have 'device random' in your kernel config
490 file, the configurations allow a kernel option to override
491 this default. You may choose *ONE* of:
493 options RANDOM_YARROW # Legacy /dev/random algorithm.
494 options RANDOM_DUMMY # Blocking-only driver.
496 If you have neither, you get Fortuna. For most people,
497 read no further, Fortuna will give a /dev/random that works
498 like it always used to, and the difference will be irrelevant.
500 If you remove 'device random', you get *NO* kernel-processed
501 entropy at all. This may be acceptable to folks building
502 embedded systems, but has complications. Carry on reading,
503 and it is assumed you know what you need.
505 *PLEASE* read random(4) and random(9) if you are in the
506 habit of tweaking kernel configs, and/or if you are a member
507 of the embedded community, wanting specific and not-usual
508 behaviour from your security subsystems.
510 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
511 random', you will NOT have a functioning /dev/random, and
512 many cryptographic features will not work, including SSH.
513 You may also find strange behaviour from the random(3) set
514 of library functions, in particular sranddev(3), srandomdev(3)
515 and arc4random(3). The reason for this is that the KERN_ARND
516 sysctl only returns entropy if it thinks it has some to
517 share, and with RANDOM_DUMMY or no 'device random' this
521 An additional fix for the issue described in the 20150614 sendmail
522 entry below has been been committed in revision 284717.
525 FreeBSD's old make (fmake) has been removed from the system. It is
526 available as the devel/fmake port or via pkg install fmake.
529 The fix for the issue described in the 20150614 sendmail entry
530 below has been been committed in revision 284436. The work
531 around described in that entry is no longer needed unless the
532 default setting is overridden by a confDH_PARAMETERS configuration
533 setting of '5' or pointing to a 512 bit DH parameter file.
536 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
537 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
538 and devel/kyua to version 0.20+ and adjust any calling code to work
539 with Kyuafile and kyua.
542 The import of openssl to address the FreeBSD-SA-15:10.openssl
543 security advisory includes a change which rejects handshakes
544 with DH parameters below 768 bits. sendmail releases prior
545 to 8.15.2 (not yet released), defaulted to a 512 bit
546 DH parameter setting for client connections. To work around
547 this interoperability, sendmail can be configured to use a
548 2048 bit DH parameter by:
550 1. Edit /etc/mail/`hostname`.mc
551 2. If a setting for confDH_PARAMETERS does not exist or
552 exists and is set to a string beginning with '5',
554 3. If a setting for confDH_PARAMETERS exists and is set to
555 a file path, create a new file with:
556 openssl dhparam -out /path/to/file 2048
557 4. Rebuild the .cf file:
558 cd /etc/mail/; make; make install
560 cd /etc/mail/; make restart
562 A sendmail patch is coming, at which time this file will be
566 Generation of legacy formatted entries have been disabled by default
567 in pwd_mkdb(8), as all base system consumers of the legacy formatted
568 entries were converted to use the new format by default when the new,
569 machine independent format have been added and supported since FreeBSD
572 Please see the pwd_mkdb(8) manual page for further details.
575 Clang and llvm have been upgraded to 3.6.1 release. Please see the
576 20141231 entry below for information about prerequisites and upgrading,
577 if you are not already using 3.5.0 or higher.
580 TI platform code switched to using vendor DTS files and this update
581 may break existing systems running on Beaglebone, Beaglebone Black,
584 - dtb files should be regenerated/reinstalled. Filenames are the
585 same but content is different now
586 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
587 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
588 addressing scheme is now pin 25 on /dev/gpioc3.
589 - Pandaboard: /etc/ttys should be updated, serial console device is
590 now /dev/ttyu2, not /dev/ttyu0
593 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
594 If you need the GNU extension from groff soelim(1), install groff
595 from package: pkg install groff, or via ports: textproc/groff.
598 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
599 defined in symlink(7); previously symlinks were silently ignored.
602 The const qualifier has been removed from iconv(3) to comply with
603 POSIX. The ports tree is aware of this from r384038 onwards.
606 Libraries specified by LIBADD in Makefiles must have a corresponding
607 DPADD_<lib> variable to ensure correct dependencies. This is now
608 enforced in src.libnames.mk.
611 From legacy ata(4) driver was removed support for SATA controllers
612 supported by more functional drivers ahci(4), siis(4) and mvs(4).
613 Kernel modules ataahci and ataadaptec were removed completely,
614 replaced by ahci and mvs modules respectively.
617 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
618 the 20141231 entry below for information about prerequisites and
619 upgrading, if you are not already using 3.5.0 or higher.
622 The 32-bit PowerPC kernel has been changed to a position-independent
623 executable. This can only be booted with a version of loader(8)
624 newer than January 31, 2015, so make sure to update both world and
625 kernel before rebooting.
628 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
629 but before r278950, the RNG was not seeded properly. Immediately
630 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
631 ssh keys or openssl keys) that were generated w/ a kernel from that
632 range. This does not affect programs that directly used /dev/random
633 or /dev/urandom. All userland uses of arc4random(3) are affected.
636 The autofs(4) ABI was changed in order to restore binary compatibility
637 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
641 The powerpc64 kernel has been changed to a position-independent
642 executable. This can only be booted with a new version of loader(8),
643 so make sure to update both world and kernel before rebooting.
646 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
647 only release, no new features have been added. Please see the 20141231
648 entry below for information about prerequisites and upgrading, if you
649 are not already using 3.5.0.
652 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
653 taken from the ELF Tool Chain project rather than GNU binutils. They
654 should be drop-in replacements, with the addition of arm64 support.
655 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
656 binutils tools, if necessary. See 20150805 for updated information.
659 The default Unbound configuration now enables remote control
660 using a local socket. Users who have already enabled the
661 local_unbound service should regenerate their configuration
662 by running "service local_unbound setup" as root.
665 The GNU texinfo and GNU info pages have been removed.
666 To be able to view GNU info pages please install texinfo from ports.
669 Clang, llvm and lldb have been upgraded to 3.5.0 release.
671 As of this release, a prerequisite for building clang, llvm and lldb is
672 a C++11 capable compiler and C++11 standard library. This means that to
673 be able to successfully build the cross-tools stage of buildworld, with
674 clang as the bootstrap compiler, your system compiler or cross compiler
675 should either be clang 3.3 or later, or gcc 4.8 or later, and your
676 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
679 On any standard FreeBSD 10.x or 11.x installation, where clang and
680 libc++ are on by default (that is, on x86 or arm), this should work out
683 On 9.x installations where clang is enabled by default, e.g. on x86 and
684 powerpc, libc++ will not be enabled by default, so libc++ should be
685 built (with clang) and installed first. If both clang and libc++ are
686 missing, build clang first, then use it to build libc++.
688 On 8.x and earlier installations, upgrade to 9.x first, and then follow
689 the instructions for 9.x above.
691 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
692 default, and do not build clang.
694 Many embedded systems are resource constrained, and will not be able to
695 build clang in a reasonable time, or in some cases at all. In those
696 cases, cross building bootable systems on amd64 is a workaround.
698 This new version of clang introduces a number of new warnings, of which
699 the following are most likely to appear:
703 This warns in two cases, for both C and C++:
704 * When the code is trying to take the absolute value of an unsigned
705 quantity, which is effectively a no-op, and almost never what was
706 intended. The code should be fixed, if at all possible. If you are
707 sure that the unsigned quantity can be safely cast to signed, without
708 loss of information or undefined behavior, you can add an explicit
709 cast, or disable the warning.
711 * When the code is trying to take an absolute value, but the called
712 abs() variant is for the wrong type, which can lead to truncation.
713 If you want to disable the warning instead of fixing the code, please
714 make sure that truncation will not occur, or it might lead to unwanted
717 -Wtautological-undefined-compare and
718 -Wundefined-bool-conversion
720 These warn when C++ code is trying to compare 'this' against NULL, while
721 'this' should never be NULL in well-defined C++ code. However, there is
722 some legacy (pre C++11) code out there, which actively abuses this
723 feature, which was less strictly defined in previous C++ versions.
725 Squid and openjdk do this, for example. The warning can be turned off
726 for C++98 and earlier, but compiling the code in C++11 mode might result
727 in unexpected behavior; for example, the parts of the program that are
728 unreachable could be optimized away.
731 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
732 kernel sources have been removed. The .h files remain, since some
733 utilities include them. This will need to be fixed later.
734 If "mount -t oldnfs ..." is attempted, it will fail.
735 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
736 the utilities will report errors.
739 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
740 directories to top level SUBDIR variable when their parent
741 directory is included in LOCAL_DIRS. Users with build systems with
742 such hierarchies and without SUBDIR entries in the parent
743 directory Makefiles should add them or add the directories to
747 faith(4) and faithd(8) have been removed from the base system. Faith
748 has been obsolete for a very long time.
751 vt(4), the new console driver, is enabled by default. It brings
752 support for Unicode and double-width characters, as well as
753 support for UEFI and integration with the KMS kernel video
756 You may need to update your console settings in /etc/rc.conf,
757 most probably the keymap. During boot, /etc/rc.d/syscons will
758 indicate what you need to do.
760 vt(4) still has issues and lacks some features compared to
761 syscons(4). See the wiki for up-to-date information:
762 https://wiki.freebsd.org/Newcons
764 If you want to keep using syscons(4), you can do so by adding
765 the following line to /boot/loader.conf:
769 pjdfstest has been integrated into kyua as an opt-in test suite.
770 Please see share/doc/pjdfstest/README for more details on how to
774 gperf has been removed from the base system for architectures
775 that use clang. Ports that require gperf will obtain it from the
779 pjdfstest has been moved from tools/regression/pjdfstest to
783 At svn r271982, The default linux compat kernel ABI has been adjusted
784 to 2.6.18 in support of the linux-c6 compat ports infrastructure
785 update. If you wish to continue using the linux-f10 compat ports,
786 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
787 encouraged to update their linux-compat packages to linux-c6 during
788 their next update cycle.
791 The ofwfb driver, used to provide a graphics console on PowerPC when
792 using vt(4), no longer allows mmap() of all physical memory. This
793 will prevent Xorg on PowerPC with some ATI graphics cards from
794 initializing properly unless x11-servers/xorg-server is updated to
798 The xdev targets have been converted to using TARGET and
799 TARGET_ARCH instead of XDEV and XDEV_ARCH.
802 The default unbound configuration has been modified to address
803 issues with reverse lookups on networks that use private
804 address ranges. If you use the local_unbound service, run
805 "service local_unbound setup" as root to regenerate your
806 configuration, then "service local_unbound reload" to load the
810 The GNU texinfo and GNU info pages are not built and installed
811 anymore, WITH_INFO knob has been added to allow to built and install
813 UPDATE: see 20150102 entry on texinfo's removal
816 The GNU readline library is now an INTERNALLIB - that is, it is
817 statically linked into consumers (GDB and variants) in the base
818 system, and the shared library is no longer installed. The
819 devel/readline port is available for third party software that
823 The Itanium architecture (ia64) has been removed from the list of
824 known architectures. This is the first step in the removal of the
828 Commit r268115 has added NFSv4.1 server support, merged from
829 projects/nfsv4.1-server. Since this includes changes to the
830 internal interfaces between the NFS related modules, a full
831 build of the kernel and modules will be necessary.
832 __FreeBSD_version has been bumped.
835 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
836 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
837 which differs from the behaviour controlled by this knob.)
840 Maximal length of the serial number in CTL was increased from 16 to
841 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
842 and ctld, need to be rebuilt to work with a new kernel.
845 The libatf-c and libatf-c++ major versions were downgraded to 0 and
846 1 respectively to match the upstream numbers. They were out of
847 sync because, when they were originally added to FreeBSD, the
848 upstream versions were not respected. These libraries are private
849 and not yet built by default, so renumbering them should be a
850 non-issue. However, unclean source trees will yield broken test
851 programs once the operator executes "make delete-old-libs" after a
854 Additionally, the atf-sh binary was made private by moving it into
855 /usr/libexec/. Already-built shell test programs will keep the
856 path to the old binary so they will break after "make delete-old"
859 If you are using WITH_TESTS=yes (not the default), wipe the object
860 tree and rebuild from scratch to prevent spurious test failures.
861 This is only needed once: the misnumbered libraries and misplaced
862 binaries have been added to OptionalObsoleteFiles.inc so they will
863 be removed during a clean upgrade.
866 Clang and llvm have been upgraded to 3.4.1 release.
869 We bogusly installed src.opts.mk in /usr/share/mk. This file should
870 be removed to avoid issues in the future (and has been added to
874 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
875 past, it affected all builds that used the bsd.*.mk files. The old
876 behavior was a bug, but people may have relied upon it. To get this
877 behavior back, you can .include /etc/src.conf from /etc/make.conf
878 (which is still global and isn't changed). This also changes the
879 behavior of incremental builds inside the tree of individual
880 directories. Set MAKESYSPATH to ".../share/mk" to do that.
881 Although this has survived make universe and some upgrade scenarios,
882 other upgrade scenarios may have broken. At least one form of
883 temporary breakage was fixed with MAKESYSPATH settings for buildworld
884 as well... In cases where MAKESYSPATH isn't working with this
885 setting, you'll need to set it to the full path to your tree.
887 One side effect of all this cleaning up is that bsd.compiler.mk
888 is no longer implicitly included by bsd.own.mk. If you wish to
889 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
893 The lindev device has been removed since /dev/full has been made a
894 standard device. __FreeBSD_version has been bumped.
897 The knob WITHOUT_VI was added to the base system, which controls
898 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
899 in order to reorder files share/termcap and didn't build ex(1) as a
900 build tool, so building/installing with WITH_VI is highly advised for
901 build hosts for older releases.
903 This issue has been fixed in stable/9 and stable/10 in r277022 and
904 r276991, respectively.
907 The YES_HESIOD knob has been removed. It has been obsolete for
908 a decade. Please move to using WITH_HESIOD instead or your builds
909 will silently lack HESIOD.
912 The uart(4) driver has been changed with respect to its handling
913 of the low-level console. Previously the uart(4) driver prevented
914 any process from changing the baudrate or the CLOCAL and HUPCL
915 control flags. By removing the restrictions, operators can make
916 changes to the serial console port without having to reboot.
917 However, when getty(8) is started on the serial device that is
918 associated with the low-level console, a misconfigured terminal
919 line in /etc/ttys will now have a real impact.
920 Before upgrading the kernel, make sure that /etc/ttys has the
921 serial console device configured as 3wire without baudrate to
922 preserve the previous behaviour. E.g:
923 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
926 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
927 to improve performance. To re-enable it, if needed, run rpcbind
928 with command line option -W.
931 Switched back to the GPL dtc compiler due to updates in the upstream
932 dts files not being supported by the BSDL dtc compiler. You will need
933 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
934 may result while building dtb files during a kernel build if you fail
935 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
938 Clang and llvm have been upgraded to 3.4 release.
941 The nve(4) driver has been removed. Please use the nfe(4) driver
942 for NVIDIA nForce MCP Ethernet adapters instead.
945 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
946 This could cause certain C++ applications using shared libraries built
947 against the previous version of libc++ to crash. The incompatibility
948 has now been fixed, but any C++ applications or shared libraries built
949 between r261283 and r261801 should be recompiled.
952 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
953 capability mode support. Please note that enabling the feature in
954 kernel is still highly recommended.
957 OpenSSH is now built with sandbox support, and will use sandbox as
958 the default privilege separation method. This requires Capsicum
959 capability mode support in kernel.
962 The libelf and libdwarf libraries have been updated to newer
963 versions from upstream. Shared library version numbers for
964 these two libraries were bumped. Any ports or binaries
965 requiring these two libraries should be recompiled.
966 __FreeBSD_version is bumped to 1100006.
969 If a Makefile in a tests/ directory was auto-generating a Kyuafile
970 instead of providing an explicit one, this would prevent such
971 Makefile from providing its own Kyuafile in the future during
972 NO_CLEAN builds. This has been fixed in the Makefiles but manual
973 intervention is needed to clean an objdir if you use NO_CLEAN:
974 # find /usr/obj -name Kyuafile | xargs rm -f
977 The behavior of gss_pseudo_random() for the krb5 mechanism
978 has changed, for applications requesting a longer random string
979 than produced by the underlying enctype's pseudo-random() function.
980 In particular, the random string produced from a session key of
981 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
982 be different at the 17th octet and later, after this change.
983 The counter used in the PRF+ construction is now encoded as a
984 big-endian integer in accordance with RFC 4402.
985 __FreeBSD_version is bumped to 1100004.
988 The WITHOUT_ATF build knob has been removed and its functionality
989 has been subsumed into the more generic WITHOUT_TESTS. If you were
990 using the former to disable the build of the ATF libraries, you
991 should change your settings to use the latter.
994 The default version of mtree is nmtree which is obtained from
995 NetBSD. The output is generally the same, but may vary
996 slightly. If you found you need identical output adding
997 "-F freebsd9" to the command line should do the trick. For the
998 time being, the old mtree is available as fmtree.
1001 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1002 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1003 1.1.4_8 and verify bsdyml not linked in, before running "make
1005 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1007 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1010 The stable/10 branch has been created in subversion from head
1014 The rc.d/jail script has been updated to support jail(8)
1015 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1016 for per-jail configuration are automatically converted to
1017 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1018 This is transparently backward compatible. See below about some
1019 incompatibilities and rc.conf(5) manual page for more details.
1021 These variables are now deprecated in favor of jail(8) configuration
1022 file. One can use "rc.d/jail config <jname>" command to generate
1023 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1024 running the jail(8) utility. The default pathname of the
1025 configuration file is /etc/jail.conf and can be specified by
1026 using $jail_conf or $jail_<jname>_conf variables.
1028 Please note that jail_devfs_ruleset accepts an integer at
1029 this moment. Please consider to rewrite the ruleset name
1033 BIND has been removed from the base system. If all you need
1034 is a local resolver, simply enable and start the local_unbound
1035 service instead. Otherwise, several versions of BIND are
1036 available in the ports tree. The dns/bind99 port is one example.
1038 With this change, nslookup(1) and dig(1) are no longer in the base
1039 system. Users should instead use host(1) and drill(1) which are
1040 in the base system. Alternatively, nslookup and dig can
1041 be obtained by installing the dns/bind-tools port.
1044 With the addition of unbound(8), a new unbound user is now
1045 required during installworld. "mergemaster -p" can be used to
1046 add the user prior to installworld, as documented in the handbook.
1049 OpenSSH is now built with DNSSEC support, and will by default
1050 silently trust signed SSHFP records. This can be controlled with
1051 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1052 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1055 The GNU Compiler Collection and C++ standard library (libstdc++)
1056 are no longer built by default on platforms where clang is the system
1057 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1058 options in src.conf.
1061 The PROCDESC kernel option is now part of the GENERIC kernel
1062 configuration and is required for the rwhod(8) to work.
1063 If you are using custom kernel configuration, you should include
1067 The API and ABI related to the Capsicum framework was modified
1068 in backward incompatible way. The userland libraries and programs
1069 have to be recompiled to work with the new kernel. This includes the
1070 following libraries and programs, but the whole buildworld is
1071 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1072 kdump, procstat, rwho, rwhod, uniq.
1075 AES-NI intrinsic support has been added to gcc. The AES-NI module
1076 has been updated to use this support. A new gcc is required to build
1077 the aesni module on both i386 and amd64.
1080 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1081 Thus "device padlock_rng" and "device rdrand_rng" should be
1082 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1085 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1086 enables just the iconv* functionality and is now on by default.
1087 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1088 compatibility. Set WITHOUT_ICONV to build the old way.
1089 If you have been using WITH_ICONV before, you will very likely
1090 need to turn on WITH_LIBICONV_COMPAT.
1093 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1094 Illumos origin, including ZFS. If you have INVARIANTS in your
1095 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1097 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1098 locks if WITNESS option was set. Because that generated a lot of
1099 witness(9) reports and all of them were believed to be false
1100 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1101 can be used to achieve the previous behavior.
1104 Timer values in IPv6 data structures now use time_uptime instead
1105 of time_second. Although this is not a user-visible functional
1106 change, userland utilities which directly use them---ndp(8),
1107 rtadvd(8), and rtsold(8) in the base system---need to be updated
1108 to r253970 or later.
1111 find -delete can now delete the pathnames given as arguments,
1112 instead of only files found below them or if the pathname did
1113 not contain any slashes. Formerly, the following error message
1116 find: -delete: <path>: relative path potentially not safe
1118 Deleting the pathnames given as arguments can be prevented
1119 without error messages using -mindepth 1 or by changing
1120 directory and passing "." as argument to find. This works in the
1121 old as well as the new version of find.
1124 Behavior of devfs rules path matching has been changed.
1125 Pattern is now always matched against fully qualified devfs
1126 path and slash characters must be explicitly matched by
1127 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1128 subdirectories must be reviewed.
1131 The default ARM ABI has changed to the ARM EABI. The old ABI is
1132 incompatible with the ARM EABI and all programs and modules will
1133 need to be rebuilt to work with a new kernel.
1135 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1137 NOTE: Support for the old ABI will be removed in the future and
1138 users are advised to upgrade.
1141 pkg_install has been disconnected from the build if you really need it
1142 you should add WITH_PKGTOOLS in your src.conf(5).
1145 Most of network statistics structures were changed to be able
1146 keep 64-bits counters. Thus all tools, that work with networking
1147 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1150 Fix a bug that allowed a tracing process (e.g. gdb) to write
1151 to a memory-mapped file in the traced process's address space
1152 even if neither the traced process nor the tracing process had
1153 write access to that file.
1156 CVS has been removed from the base system. An exact copy
1157 of the code is available from the devel/cvs port.
1160 Some people report the following error after the switch to bmake:
1162 make: illegal option -- J
1163 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1165 *** [buildworld] Error code 2
1167 this likely due to an old instance of make in
1168 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1169 which src/Makefile will use that blindly, if it exists, so if
1170 you see the above error:
1172 rm -rf `make -V MAKEPATH`
1177 Use bmake by default.
1178 Whereas before one could choose to build with bmake via
1179 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1180 make. The goal is to remove these knobs for 10-RELEASE.
1182 It is worth noting that bmake (like gmake) treats the command
1183 line as the unit of failure, rather than statements within the
1184 command line. Thus '(cd some/where && dosomething)' is safer
1185 than 'cd some/where; dosomething'. The '()' allows consistent
1186 behavior in parallel build.
1189 Fix a bug that allows NFS clients to issue READDIR on files.
1192 The WITHOUT_IDEA option has been removed because
1193 the IDEA patent expired.
1196 The sysctl which controls TRIM support under ZFS has been renamed
1197 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1201 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1202 rather than creating it's own in the temporary directory in
1203 order allow access to bootstrapped versions of tools such as
1204 install and mtree. When upgrading from version of FreeBSD where
1205 the install command does not support -l, you will need to
1206 install a new mergemaster command if mergemaster -p is required.
1207 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1211 Legacy ATA stack, disabled and replaced by new CAM-based one since
1212 FreeBSD 9.0, completely removed from the sources. Kernel modules
1213 atadisk and atapi*, user-level tools atacontrol and burncd are
1214 removed. Kernel option `options ATA_CAM` is now permanently enabled
1218 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1219 and socketpair(2). Software, in particular Kerberos, may
1220 automatically detect and use these during building. The resulting
1221 binaries will not work on older kernels.
1224 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1225 information, see the respective 20130304 entry).
1228 Recent commits to callout(9) changed the size of struct callout,
1229 so the KBI is probably heavily disturbed. Also, some functions
1230 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1231 by macros. Every kernel module using it won't load, so rebuild
1234 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1235 but does not initialize by default (because of the new CTL_DISABLE
1236 option) to save memory. To re-enable it, remove the CTL_DISABLE
1237 option from the kernel config file or set kern.cam.ctl.disable=0
1238 in /boot/loader.conf.
1241 The ctl device has been disabled in GENERIC for i386 and amd64.
1242 This was done due to the extra memory being allocated at system
1243 initialisation time by the ctl driver which was only used if
1244 a CAM target device was created. This makes a FreeBSD system
1245 unusable on 128MB or less of RAM.
1248 A new compression method (lz4) has been merged to -HEAD. Please
1249 refer to zpool-features(7) for more information.
1251 Please refer to the "ZFS notes" section of this file for information
1252 on upgrading boot ZFS pools.
1255 A BSD-licensed patch(1) variant has been added and is installed
1256 as bsdpatch, being the GNU version the default patch.
1257 To inverse the logic and use the BSD-licensed one as default,
1258 while having the GNU version installed as gnupatch, rebuild
1259 and install world with the WITH_BSD_PATCH knob set.
1262 Due to the use of the new -l option to install(1) during build
1263 and install, you must take care not to directly set the INSTALL
1264 make variable in your /etc/make.conf, /etc/src.conf, or on the
1265 command line. If you wish to use the -C flag for all installs
1266 you may be able to add INSTALL+=-C to /etc/make.conf or
1270 The install(1) option -M has changed meaning and now takes an
1271 argument that is a file or path to append logs to. In the
1272 unlikely event that -M was the last option on the command line
1273 and the command line contained at least two files and a target
1274 directory the first file will have logs appended to it. The -M
1275 option served little practical purpose in the last decade so its
1276 use is expected to be extremely rare.
1279 After switching to Clang as the default compiler some users of ZFS
1280 on i386 systems started to experience stack overflow kernel panics.
1281 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1284 GEOM_LABEL now mangles label names read from file system metadata.
1285 Mangling affect labels containing spaces, non-printable characters,
1286 '%' or '"'. Device names in /etc/fstab and other places may need to
1290 By default, only the 10 most recent kernel dumps will be saved. To
1291 restore the previous behaviour (no limit on the number of kernel dumps
1292 stored in the dump directory) add the following line to /etc/rc.conf:
1297 With the addition of auditdistd(8), a new auditdistd user is now
1298 required during installworld. "mergemaster -p" can be used to
1299 add the user prior to installworld, as documented in the handbook.
1302 The sin6_scope_id member variable in struct sockaddr_in6 is now
1303 filled by the kernel before passing the structure to the userland via
1304 sysctl or routing socket. This means the KAME-specific embedded scope
1305 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1306 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1307 __FreeBSD_version is bumped to 1000025.
1310 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1311 This means that the world and kernel will be compiled with clang
1312 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1313 and /usr/bin/cpp. To disable this behavior and revert to building
1314 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1315 of current may need to bootstrap WITHOUT_CLANG first if the clang
1316 build fails (its compatibility window doesn't extend to the 9 stable
1320 The IPFIREWALL_FORWARD kernel option has been removed. Its
1321 functionality now turned on by default.
1324 The ZERO_COPY_SOCKET kernel option has been removed and
1325 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1326 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1327 mechanism which is not safe and may result in kernel crashes.
1328 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1329 driver supports disposeable external page sized mbuf storage.
1330 Proper replacements for both zero-copy mechanisms are under
1331 consideration and will eventually lead to complete removal
1332 of the two kernel options.
1335 The IPv4 network stack has been converted to network byte
1336 order. The following modules need to be recompiled together
1337 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1338 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1341 Support for non-MPSAFE filesystems was removed from VFS. The
1342 VFS_VERSION was bumped, all filesystem modules shall be
1346 All the non-MPSAFE filesystems have been disconnected from
1347 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1348 portalfs, smbfs, xfs.
1351 The interface cloning API and ABI has changed. The following
1352 modules need to be recompiled together with kernel:
1353 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1354 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1355 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1358 The sdhci driver was split in two parts: sdhci (generic SD Host
1359 Controller logic) and sdhci_pci (actual hardware driver).
1360 No kernel config modifications are required, but if you
1361 load sdhc as a module you must switch to sdhci_pci instead.
1364 Import the FUSE kernel and userland support into base system.
1367 The GNU sort(1) program has been removed since the BSD-licensed
1368 sort(1) has been the default for quite some time and no serious
1369 problems have been reported. The corresponding WITH_GNU_SORT
1373 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1374 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1378 The net80211(4) ABI has been changed to allow for improved driver
1379 PS-POLL and power-save support. All wireless drivers need to be
1380 recompiled to work with the new kernel.
1383 The random(4) support for the VIA hardware random number
1384 generator (`PADLOCK') is no longer enabled unconditionally.
1385 Add the padlock_rng device in the custom kernel config if
1386 needed. The GENERIC kernels on i386 and amd64 do include the
1387 device, so the change only affects the custom kernel
1391 The pf(4) packet filter ABI has been changed. pfctl(8) and
1392 snmp_pf module need to be recompiled to work with new kernel.
1395 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1396 to -HEAD. Pools that have empty_bpobj in active state can not be
1397 imported read-write with ZFS implementations that do not support
1398 this feature. For more information read the zpool-features(5)
1402 The sparc64 ZFS loader has been changed to no longer try to auto-
1403 detect ZFS providers based on diskN aliases but now requires these
1404 to be explicitly listed in the OFW boot-device environment variable.
1407 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1408 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1409 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1412 The following sysctls and tunables have been renamed for consistency
1413 with other variables:
1414 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1415 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1418 The sort utility has been replaced with BSD sort. For now, GNU sort
1419 is also available as "gnusort" or the default can be set back to
1420 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1421 installed as "bsdsort".
1424 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1425 Starting with this version the old system of ZFS pool versioning
1426 is superseded by "feature flags". This concept enables forward
1427 compatibility against certain future changes in functionality of ZFS
1428 pools. The first read-only compatible "feature flag" for ZFS pools
1429 is named "com.delphix:async_destroy". For more information
1430 read the new zpool-features(5) manual page.
1431 Please refer to the "ZFS notes" section of this file for information
1432 on upgrading boot ZFS pools.
1435 The malloc(3) implementation embedded in libc now uses sources imported
1436 as contrib/jemalloc. The most disruptive API change is to
1437 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1438 delete it prior to installworld, and optionally re-create it using the
1439 new format after rebooting. See malloc.conf(5) for details
1440 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1444 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1445 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1446 now spelled mips. This is to aid compatibility with third-party
1447 software that expects this naming scheme in uname(3). Little-endian
1448 settings are unchanged. If you are updating a big-endian mips64 machine
1449 from before this change, you may need to set MACHINE_ARCH=mips64 in
1450 your environment before the new build system will recognize your machine.
1453 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1457 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1458 nullfs(5) did not pass through all behaviours to the underlying layer,
1459 as a result if we bound to a socket on the lower layer we could connect
1460 only to the lower path; if we bound to the upper layer we could connect
1461 only to the upper path. The new behavior is one can connect to both the
1462 lower and the upper paths regardless what layer path one binds to.
1465 The getifaddrs upgrade path broken with 20111215 has been restored.
1466 If you have upgraded in between 20111215 and 20120209 you need to
1467 recompile libc again with your kernel. You still need to recompile
1468 world to be able to configure CARP but this restriction already
1469 comes from 20111215.
1472 The set_rcvar() function has been removed from /etc/rc.subr. All
1473 base and ports rc.d scripts have been updated, so if you have a
1474 port installed with a script in /usr/local/etc/rc.d you can either
1475 hand-edit the rcvar= line, or reinstall the port.
1477 An easy way to handle the mass-update of /etc/rc.d:
1478 rm /etc/rc.d/* && mergemaster -i
1481 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1482 on the current CPU and prevents other threads from running.
1483 This behavior can be reverted using the kern.stop_scheduler_on_panic
1485 The new behavior can be incompatible with kern.sync_on_panic.
1488 The carp(4) facility has been changed significantly. Configuration
1489 of the CARP protocol via ifconfig(8) has changed, as well as format
1490 of CARP events submitted to devd(8) has changed. See manual pages
1491 for more information. The arpbalance feature of carp(4) is currently
1492 not supported anymore.
1494 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1495 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1496 need to be recompiled.
1499 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1503 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1504 explicitely support non-MPSAFE filesystems.
1505 It is on by default for all supported platform at this present
1509 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1510 i386 and pc98 GENERIC kernel configuration files.
1513 sysinstall has been removed
1516 The stable/9 branch created in subversion. This corresponds to the
1517 RELENG_9 branch in CVS.
1523 Avoid using make -j when upgrading. While generally safe, there are
1524 sometimes problems using -j to upgrade. If your upgrade fails with
1525 -j, please try again without -j. From time to time in the past there
1526 have been problems using -j with buildworld and/or installworld. This
1527 is especially true when upgrading between "distant" versions (eg one
1528 that cross a major release boundary or several minor releases, or when
1529 several months have passed on the -current branch).
1531 Sometimes, obscure build problems are the result of environment
1532 poisoning. This can happen because the make utility reads its
1533 environment when searching for values for global variables. To run
1534 your build attempts in an "environmental clean room", prefix all make
1535 commands with 'env -i '. See the env(1) manual page for more details.
1537 When upgrading from one major version to another it is generally best to
1538 upgrade to the latest code in the currently installed branch first, then
1539 do an upgrade to the new branch. This is the best-tested upgrade path,
1540 and has the highest probability of being successful. Please try this
1541 approach if you encounter problems with a major version upgrade. Since
1542 the stable 4.x branch point, one has generally been able to upgade from
1543 anywhere in the most recent stable branch to head / current (or even the
1544 last couple of stable branches). See the top of this file when there's
1547 When upgrading a live system, having a root shell around before
1548 installing anything can help undo problems. Not having a root shell
1549 around can lead to problems if pam has changed too much from your
1550 starting point to allow continued authentication after the upgrade.
1552 This file should be read as a log of events. When a later event changes
1553 information of a prior event, the prior event should not be deleted.
1554 Instead, a pointer to the entry with the new information should be
1555 placed in the old entry. Readers of this file should also sanity check
1556 older entries before relying on them blindly. Authors of new entries
1557 should write them with this in mind.
1561 When upgrading the boot ZFS pool to a new version, always follow
1564 1.) recompile and reinstall the ZFS boot loader and boot block
1565 (this is part of "make buildworld" and "make installworld")
1567 2.) update the ZFS boot block on your boot drive
1569 The following example updates the ZFS boot block on the first
1570 partition (freebsd-boot) of a GPT partitioned drive ada0:
1571 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1573 Non-boot pools do not need these updates.
1577 If you are updating from a prior version of FreeBSD (even one just
1578 a few days old), you should follow this procedure. It is the most
1579 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1581 make kernel-toolchain
1582 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1583 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1585 To test a kernel once
1586 ---------------------
1587 If you just want to boot a kernel once (because you are not sure
1588 if it works, or if you want to boot a known bad kernel to provide
1589 debugging information) run
1590 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1591 nextboot -k testkernel
1593 To just build a kernel when you know that it won't mess you up
1594 --------------------------------------------------------------
1595 This assumes you are already running a CURRENT system. Replace
1596 ${arch} with the architecture of your machine (e.g. "i386",
1597 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1599 cd src/sys/${arch}/conf
1600 config KERNEL_NAME_HERE
1601 cd ../compile/KERNEL_NAME_HERE
1606 If this fails, go to the "To build a kernel" section.
1608 To rebuild everything and install it on the current system.
1609 -----------------------------------------------------------
1610 # Note: sometimes if you are running current you gotta do more than
1611 # is listed here if you are upgrading from a really old current.
1613 <make sure you have good level 0 dumps>
1615 make kernel KERNCONF=YOUR_KERNEL_HERE
1617 <reboot in single user> [3]
1624 To cross-install current onto a separate partition
1625 --------------------------------------------------
1626 # In this approach we use a separate partition to hold
1627 # current's root, 'usr', and 'var' directories. A partition
1628 # holding "/", "/usr" and "/var" should be about 2GB in
1631 <make sure you have good level 0 dumps>
1634 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1635 <maybe newfs current's root partition>
1636 <mount current's root partition on directory ${CURRENT_ROOT}>
1637 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1638 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1639 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1640 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1641 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1642 <reboot into current>
1643 <do a "native" rebuild/install as described in the previous section>
1644 <maybe install compatibility libraries from ports/misc/compat*>
1648 To upgrade in-place from stable to current
1649 ----------------------------------------------
1650 <make sure you have good level 0 dumps>
1652 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1654 <reboot in single user> [3]
1661 Make sure that you've read the UPDATING file to understand the
1662 tweaks to various things you need. At this point in the life
1663 cycle of current, things change often and you are on your own
1664 to cope. The defaults can also change, so please read ALL of
1665 the UPDATING entries.
1667 Also, if you are tracking -current, you must be subscribed to
1668 freebsd-current@freebsd.org. Make sure that before you update
1669 your sources that you have read and understood all the recent
1670 messages there. If in doubt, please track -stable which has
1671 much fewer pitfalls.
1673 [1] If you have third party modules, such as vmware, you
1674 should disable them at this point so they don't crash your
1677 [3] From the bootblocks, boot -s, and then do
1682 adjkerntz -i # if CMOS is wall time
1683 Also, when doing a major release upgrade, it is required that
1684 you boot into single user mode to do the installworld.
1686 [4] Note: This step is non-optional. Failure to do this step
1687 can result in a significant reduction in the functionality of the
1688 system. Attempting to do it by hand is not recommended and those
1689 that pursue this avenue should read this file carefully, as well
1690 as the archives of freebsd-current and freebsd-hackers mailing lists
1691 for potential gotchas. The -U option is also useful to consider.
1692 See mergemaster(8) for more information.
1694 [5] Usually this step is a noop. However, from time to time
1695 you may need to do this if you get unknown user in the following
1696 step. It never hurts to do it all the time. You may need to
1697 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1698 install) after the buildworld before this step if you last updated
1699 from current before 20130425 or from -stable before 20130430.
1701 [6] This only deletes old files and directories. Old libraries
1702 can be deleted by "make delete-old-libs", but you have to make
1703 sure that no program is using those libraries anymore.
1705 [8] In order to have a kernel that can run the 4.x binaries needed to
1706 do an installworld, you must include the COMPAT_FREEBSD4 option in
1707 your kernel. Failure to do so may leave you with a system that is
1708 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1709 required to run the 5.x binaries on more recent kernels. And so on
1710 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1712 Make sure that you merge any new devices from GENERIC since the
1713 last time you updated your kernel config file.
1715 [9] When checking out sources, you must include the -P flag to have
1716 cvs prune empty directories.
1718 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1719 "?=" instead of the "=" assignment operator, so that buildworld can
1720 override the CPUTYPE if it needs to.
1722 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1723 not on the command line, or in /etc/make.conf. buildworld will
1724 warn if it is improperly defined.
1727 This file contains a list, in reverse chronological order, of major
1728 breakages in tracking -current. It is not guaranteed to be a complete
1729 list of such breakages, and only contains entries since September 23, 2011.
1730 If you need to see UPDATING entries from before that date, you will need
1731 to fetch an UPDATING file from an older FreeBSD release.
1733 Copyright information:
1735 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1737 Redistribution, publication, translation and use, with or without
1738 modification, in full or in part, in any form or format of this
1739 document are permitted without further permission from the author.
1741 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1742 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1743 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1744 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1745 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1746 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1747 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1748 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1749 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1750 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1751 POSSIBILITY OF SUCH DAMAGE.
1753 Contact Warner Losh if you have any questions about your use of