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 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
56 Please see the 20141231 entry below for information about prerequisites
57 and upgrading, if you are not already using clang 3.5.0 or higher.
60 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
61 IFLIB. If you have a custom kernel configuration that excludes em(4)
62 but you use igb(4), you need to re-add em(4) to your custom configuration.
65 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
66 Please see the 20141231 entry below for information about prerequisites
67 and upgrading, if you are not already using clang 3.5.0 or higher.
70 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
71 Please see the 20141231 entry below for information about prerequisites
72 and upgrading, if you are not already using clang 3.5.0 or higher.
75 The layout of the pmap structure has changed for powerpc to put the pmap
76 statistics at the front for all CPU variations. libkvm(3) and all tools
77 that link against it need to be recompiled.
80 isl(4) and cyapa(4) drivers now require a new driver,
81 chromebook_platform(4), to work properly on Chromebook-class hardware.
82 On other types of hardware the drivers may need to be configured using
83 device hints. Please see the corresponding manual pages for details.
86 The urtwn(4) driver was merged into rtwn(4) and now consists of
87 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
89 Also, firmware for RTL8188CE was renamed due to possible name
90 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
93 GNU rcs has been removed from base. It is available as packages:
94 - rcs: Latest GPLv3 GNU rcs version.
95 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
99 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
100 modules now requires that the kernel configuration contain the
101 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
104 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
105 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
108 Relocatable object files with the extension of .So have been renamed
109 to use an extension of .pico instead. The purpose of this change is
110 to avoid a name clash with shared libraries on case-insensitive file
111 systems. On those file systems, foo.So is the same file as foo.so.
114 GNU rcs has been turned off by default. It can (temporarily) be built
115 again by adding WITH_RCS knob in src.conf.
116 Otherwise, GNU rcs is available from packages:
117 - rcs: Latest GPLv3 GNU rcs version.
118 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
121 The backup_uses_rcs functionality has been removed from rc.subr.
124 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
125 two separate components, QUEUE_MACRO_DEBUG_TRACE and
126 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
127 QUEUE_MACRO_DEBUG behavior.
130 r304787 changed some ioctl interfaces between the iSCSI userspace
131 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
132 rebuilt to work with new kernels. __FreeBSD_version has been bumped
136 The UDP receive code has been updated to only treat incoming UDP
137 packets that were addressed to an L2 broadcast address as L3
138 broadcast packets. It is not expected that this will affect any
139 standards-conforming UDP application. The new behaviour can be
140 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
144 Remove the openbsd_poll system call.
145 __FreeBSD_version has been bumped because of this.
148 The libc stub for the pipe(2) system call has been replaced with
149 a wrapper that calls the pipe2(2) system call and the pipe(2)
150 system call is now only implemented by the kernels that include
151 "options COMPAT_FREEBSD10" in their config file (this is the
152 default). Users should ensure that this option is enabled in
153 their kernel or upgrade userspace to r302092 before upgrading their
157 CAM will now strip leading spaces from SCSI disks' serial numbers.
158 This will affect users who create UFS filesystems on SCSI disks using
159 those disk's diskid device nodes. For example, if /etc/fstab
160 previously contained a line like
161 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
162 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
163 transforms like gmirror may also be affected. ZFS users should
167 The bitstring(3) API has been updated with new functionality and
168 improved performance. But it is binary-incompatible with the old API.
169 Objects built with the new headers may not be linked against objects
170 built with the old headers.
173 The brk and sbrk functions have been removed from libc on arm64.
174 Binutils from ports has been updated to not link to these
175 functions and should be updated to the latest version before
176 installing a new libc.
179 The armv6 port now defaults to hard float ABI. Limited support
180 for running both hardfloat and soft float on the same system
181 is available using the libraries installed with -DWITH_LIBSOFT.
182 This has only been tested as an upgrade path for installworld
183 and packages may fail or need manual intervention to run. New
184 packages will be needed.
186 To update an existing self-hosted armv6hf system, you must add
187 TARGET_ARCH=armv6 on the make command line for both the build
188 and the install steps.
191 Kernel modules compiled outside of a kernel build now default to
192 installing to /boot/modules instead of /boot/kernel. Many kernel
193 modules built this way (such as those in ports) already overrode
194 KMODDIR explicitly to install into /boot/modules. However,
195 manually building and installing a module from /sys/modules will
196 now install to /boot/modules instead of /boot/kernel.
199 The CAM I/O scheduler has been committed to the kernel. There should be
200 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
201 list of known rogues that claim support for this but actually corrupt
202 data is believed to be complete, be on the lookout for data
203 corruption. The known rogue list is believed to be complete:
205 o Crucial MX100, M550 drives with MU01 firmware.
206 o Micron M510 and M550 drives with MU01 firmware.
207 o Micron M500 prior to MU07 firmware
208 o Samsung 830, 840, and 850 all firmwares
209 o FCCT M500 all firmwares
211 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
212 with working NCQ TRIM. For Micron branded drives, see your sales rep for
213 updated firmware. Black listed drives will work correctly because these
214 drives work correctly so long as no NCQ TRIMs are sent to them. Given
215 this list is the same as found in Linux, it's believed there are no
216 other rogues in the market place. All other models from the above
219 To be safe, if you are at all concerned, you can quirk each of your
220 drives to prevent NCQ from being sent by setting:
221 kern.cam.ada.X.quirks="0x2"
222 in loader.conf. If the drive requires the 4k sector quirk, set the
226 The FAST_DEPEND build option has been removed and its functionality is
227 now the one true way. The old mkdep(1) style of 'make depend' has
228 been removed. See 20160311 for further details.
231 Resource range types have grown from unsigned long to uintmax_t. All
232 drivers, and anything using libdevinfo, need to be recompiled.
235 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
236 builds. It no longer runs mkdep(1) during 'make depend', and the
237 'make depend' stage can safely be skipped now as it is auto ran
238 when building 'make all' and will generate all SRCS and DPSRCS before
239 building anything else. Dependencies are gathered at compile time with
240 -MF flags kept in separate .depend files per object file. Users should
241 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
245 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
246 kernel modules. Therefore, if you load any kernel modules at boot time,
247 please install the boot loaders after you install the kernel, but before
251 make kernel KERNCONF=YOUR_KERNEL_HERE
252 make -C sys/boot install
253 <reboot in single user>
255 Then follow the usual steps, described in the General Notes section,
259 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
260 see the 20141231 entry below for information about prerequisites and
261 upgrading, if you are not already using clang 3.5.0 or higher.
264 The AIO subsystem is now a standard part of the kernel. The
265 VFS_AIO kernel option and aio.ko kernel module have been removed.
266 Due to stability concerns, asynchronous I/O requests are only
267 permitted on sockets and raw disks by default. To enable
268 asynchronous I/O requests on all file types, set the
269 vfs.aio.enable_unsafe sysctl to a non-zero value.
272 The ELF object manipulation tool objcopy is now provided by the
273 ELF Tool Chain project rather than by GNU binutils. It should be a
274 drop-in replacement, with the addition of arm64 support. The
275 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
276 to obtain the GNU version if necessary.
279 Building ZFS pools on top of zvols is prohibited by default. That
280 feature has never worked safely; it's always been prone to deadlocks.
281 Using a zvol as the backing store for a VM guest's virtual disk will
282 still work, even if the guest is using ZFS. Legacy behavior can be
283 restored by setting vfs.zfs.vol.recursive=1.
286 The NONE and HPN patches has been removed from OpenSSH. They are
287 still available in the security/openssh-portable port.
290 With the addition of ypldap(8), a new _ypldap user is now required
291 during installworld. "mergemaster -p" can be used to add the user
292 prior to installworld, as documented in the handbook.
295 The tftp loader (pxeboot) now uses the option root-path directive. As a
296 consequence it no longer looks for a pxeboot.4th file on the tftp
297 server. Instead it uses the regular /boot infrastructure as with the
301 The code to start recording plug and play data into the modules has
302 been committed. While the old tools will properly build a new kernel,
303 a number of warnings about "unknown metadata record 4" will be produced
304 for an older kldxref. To avoid such warnings, make sure to rebuild
305 the kernel toolchain (or world). Make sure that you have r292078 or
306 later when trying to build 292077 or later before rebuilding.
309 Debug data files are now built by default with 'make buildworld' and
310 installed with 'make installworld'. This facilitates debugging but
311 requires more disk space both during the build and for the installed
312 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
316 r291527 changed the internal interface between the nfsd.ko and
317 nfscommon.ko modules. As such, they must both be upgraded to-gether.
318 __FreeBSD_version has been bumped because of this.
321 Add support for unicode collation strings leads to a change of
322 order of files listed by ls(1) for example. To get back to the old
323 behaviour, set LC_COLLATE environment variable to "C".
325 Databases administrators will need to reindex their databases given
326 collation results will be different.
328 Due to a bug in install(1) it is recommended to remove the ancient
329 locales before running make installworld.
331 rm -rf /usr/share/locale/*
334 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
335 libcrypto.so.7 or libssl.so.7 must be recompiled.
338 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
339 Kernel modules isp_2400_multi and isp_2500_multi were removed and
340 should be replaced with isp_2400 and isp_2500 modules respectively.
343 The build previously allowed using 'make -n' to not recurse into
344 sub-directories while showing what commands would be executed, and
345 'make -n -n' to recursively show commands. Now 'make -n' will recurse
346 and 'make -N' will not.
349 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
350 and etcupdate will now use this file. A custom sendmail.cf is now
351 updated via this mechanism rather than via installworld. If you had
352 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
353 want to remove the exclusion or change it to "always install".
354 /etc/mail/sendmail.cf is now managed the same way regardless of
355 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
356 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
359 Compatibility shims for legacy ATA device names have been removed.
360 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
361 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
362 environment variables, /dev/ad* and /dev/ar* symbolic links.
365 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
366 Please see the 20141231 entry below for information about prerequisites
367 and upgrading, if you are not already using clang 3.5.0 or higher.
370 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
371 and renamed from .symbols to .debug. This reduces the size requirements
372 on the boot partition or file system and provides consistency with
373 userland debug files.
375 When using the supported kernel installation method the
376 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
377 as is done with /boot/kernel.
379 Developers wishing to maintain the historical behavior of installing
380 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
383 The wireless drivers had undergone changes that remove the 'parent
384 interface' from the ifconfig -l output. The rc.d network scripts
385 used to check presence of a parent interface in the list, so old
386 scripts would fail to start wireless networking. Thus, etcupdate(3)
387 or mergemaster(8) run is required after kernel update, to update your
388 rc.d scripts in /etc.
391 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
392 These configurations are now automatically interpreted as
393 'scrub fragment reassemble'.
396 Kernel-loadable modules for the random(4) device are back. To use
397 them, the kernel must have
400 options RANDOM_LOADABLE
402 kldload(8) can then be used to load random_fortuna.ko
403 or random_yarrow.ko. Please note that due to the indirect
404 function calls that the loadable modules need to provide,
405 the build-in variants will be slightly more efficient.
407 The random(4) kernel option RANDOM_DUMMY has been retired due to
408 unpopularity. It was not all that useful anyway.
411 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
412 Control over building the ELF Tool Chain tools is now provided by
413 the WITHOUT_TOOLCHAIN knob.
416 The polarity of Pulse Per Second (PPS) capture events with the
417 uart(4) driver has been corrected. Prior to this change the PPS
418 "assert" event corresponded to the trailing edge of a positive PPS
419 pulse and the "clear" event was the leading edge of the next pulse.
421 As the width of a PPS pulse in a typical GPS receiver is on the
422 order of 1 millisecond, most users will not notice any significant
423 difference with this change.
425 Anyone who has compensated for the historical polarity reversal by
426 configuring a negative offset equal to the pulse width will need to
427 remove that workaround.
430 The default group assigned to /dev/dri entries has been changed
431 from 'wheel' to 'video' with the id of '44'. If you want to have
432 access to the dri devices please add yourself to the video group
435 # pw groupmod video -m $USER
438 The menu.rc and loader.rc files will now be replaced during
439 upgrades. Please migrate local changes to menu.rc.local and
440 loader.rc.local instead.
443 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
444 strings and strip have been removed. The src.conf(5) knob
445 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
448 As ZFS requires more kernel stack pages than is the default on some
449 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
450 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
452 Please consider using 'options KSTACK_PAGES=X' where X is greater
453 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
456 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
457 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
458 default, i.e., they will not contain "::". For example, instead
459 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
460 to have a more specific match, such as different map entries for
461 IPv6:0:0 vs IPv6:0. This change requires that configuration
462 data (including maps, files, classes, custom ruleset, etc.) must
463 use the same format, so make certain such configuration data is
464 upgrading. As a very simple check search for patterns like
465 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
466 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
467 the cf option UseCompressedIPv6Addresses.
470 The default kernel entropy-processing algorithm is now
471 Fortuna, replacing Yarrow.
473 Assuming you have 'device random' in your kernel config
474 file, the configurations allow a kernel option to override
475 this default. You may choose *ONE* of:
477 options RANDOM_YARROW # Legacy /dev/random algorithm.
478 options RANDOM_DUMMY # Blocking-only driver.
480 If you have neither, you get Fortuna. For most people,
481 read no further, Fortuna will give a /dev/random that works
482 like it always used to, and the difference will be irrelevant.
484 If you remove 'device random', you get *NO* kernel-processed
485 entropy at all. This may be acceptable to folks building
486 embedded systems, but has complications. Carry on reading,
487 and it is assumed you know what you need.
489 *PLEASE* read random(4) and random(9) if you are in the
490 habit of tweaking kernel configs, and/or if you are a member
491 of the embedded community, wanting specific and not-usual
492 behaviour from your security subsystems.
494 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
495 random', you will NOT have a functioning /dev/random, and
496 many cryptographic features will not work, including SSH.
497 You may also find strange behaviour from the random(3) set
498 of library functions, in particular sranddev(3), srandomdev(3)
499 and arc4random(3). The reason for this is that the KERN_ARND
500 sysctl only returns entropy if it thinks it has some to
501 share, and with RANDOM_DUMMY or no 'device random' this
505 An additional fix for the issue described in the 20150614 sendmail
506 entry below has been been committed in revision 284717.
509 FreeBSD's old make (fmake) has been removed from the system. It is
510 available as the devel/fmake port or via pkg install fmake.
513 The fix for the issue described in the 20150614 sendmail entry
514 below has been been committed in revision 284436. The work
515 around described in that entry is no longer needed unless the
516 default setting is overridden by a confDH_PARAMETERS configuration
517 setting of '5' or pointing to a 512 bit DH parameter file.
520 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
521 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
522 and devel/kyua to version 0.20+ and adjust any calling code to work
523 with Kyuafile and kyua.
526 The import of openssl to address the FreeBSD-SA-15:10.openssl
527 security advisory includes a change which rejects handshakes
528 with DH parameters below 768 bits. sendmail releases prior
529 to 8.15.2 (not yet released), defaulted to a 512 bit
530 DH parameter setting for client connections. To work around
531 this interoperability, sendmail can be configured to use a
532 2048 bit DH parameter by:
534 1. Edit /etc/mail/`hostname`.mc
535 2. If a setting for confDH_PARAMETERS does not exist or
536 exists and is set to a string beginning with '5',
538 3. If a setting for confDH_PARAMETERS exists and is set to
539 a file path, create a new file with:
540 openssl dhparam -out /path/to/file 2048
541 4. Rebuild the .cf file:
542 cd /etc/mail/; make; make install
544 cd /etc/mail/; make restart
546 A sendmail patch is coming, at which time this file will be
550 Generation of legacy formatted entries have been disabled by default
551 in pwd_mkdb(8), as all base system consumers of the legacy formatted
552 entries were converted to use the new format by default when the new,
553 machine independent format have been added and supported since FreeBSD
556 Please see the pwd_mkdb(8) manual page for further details.
559 Clang and llvm have been upgraded to 3.6.1 release. Please see the
560 20141231 entry below for information about prerequisites and upgrading,
561 if you are not already using 3.5.0 or higher.
564 TI platform code switched to using vendor DTS files and this update
565 may break existing systems running on Beaglebone, Beaglebone Black,
568 - dtb files should be regenerated/reinstalled. Filenames are the
569 same but content is different now
570 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
571 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
572 addressing scheme is now pin 25 on /dev/gpioc3.
573 - Pandaboard: /etc/ttys should be updated, serial console device is
574 now /dev/ttyu2, not /dev/ttyu0
577 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
578 If you need the GNU extension from groff soelim(1), install groff
579 from package: pkg install groff, or via ports: textproc/groff.
582 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
583 defined in symlink(7); previously symlinks were silently ignored.
586 The const qualifier has been removed from iconv(3) to comply with
587 POSIX. The ports tree is aware of this from r384038 onwards.
590 Libraries specified by LIBADD in Makefiles must have a corresponding
591 DPADD_<lib> variable to ensure correct dependencies. This is now
592 enforced in src.libnames.mk.
595 From legacy ata(4) driver was removed support for SATA controllers
596 supported by more functional drivers ahci(4), siis(4) and mvs(4).
597 Kernel modules ataahci and ataadaptec were removed completely,
598 replaced by ahci and mvs modules respectively.
601 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
602 the 20141231 entry below for information about prerequisites and
603 upgrading, if you are not already using 3.5.0 or higher.
606 The 32-bit PowerPC kernel has been changed to a position-independent
607 executable. This can only be booted with a version of loader(8)
608 newer than January 31, 2015, so make sure to update both world and
609 kernel before rebooting.
612 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
613 but before r278950, the RNG was not seeded properly. Immediately
614 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
615 ssh keys or openssl keys) that were generated w/ a kernel from that
616 range. This does not affect programs that directly used /dev/random
617 or /dev/urandom. All userland uses of arc4random(3) are affected.
620 The autofs(4) ABI was changed in order to restore binary compatibility
621 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
625 The powerpc64 kernel has been changed to a position-independent
626 executable. This can only be booted with a new version of loader(8),
627 so make sure to update both world and kernel before rebooting.
630 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
631 only release, no new features have been added. Please see the 20141231
632 entry below for information about prerequisites and upgrading, if you
633 are not already using 3.5.0.
636 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
637 taken from the ELF Tool Chain project rather than GNU binutils. They
638 should be drop-in replacements, with the addition of arm64 support.
639 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
640 binutils tools, if necessary. See 20150805 for updated information.
643 The default Unbound configuration now enables remote control
644 using a local socket. Users who have already enabled the
645 local_unbound service should regenerate their configuration
646 by running "service local_unbound setup" as root.
649 The GNU texinfo and GNU info pages have been removed.
650 To be able to view GNU info pages please install texinfo from ports.
653 Clang, llvm and lldb have been upgraded to 3.5.0 release.
655 As of this release, a prerequisite for building clang, llvm and lldb is
656 a C++11 capable compiler and C++11 standard library. This means that to
657 be able to successfully build the cross-tools stage of buildworld, with
658 clang as the bootstrap compiler, your system compiler or cross compiler
659 should either be clang 3.3 or later, or gcc 4.8 or later, and your
660 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
663 On any standard FreeBSD 10.x or 11.x installation, where clang and
664 libc++ are on by default (that is, on x86 or arm), this should work out
667 On 9.x installations where clang is enabled by default, e.g. on x86 and
668 powerpc, libc++ will not be enabled by default, so libc++ should be
669 built (with clang) and installed first. If both clang and libc++ are
670 missing, build clang first, then use it to build libc++.
672 On 8.x and earlier installations, upgrade to 9.x first, and then follow
673 the instructions for 9.x above.
675 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
676 default, and do not build clang.
678 Many embedded systems are resource constrained, and will not be able to
679 build clang in a reasonable time, or in some cases at all. In those
680 cases, cross building bootable systems on amd64 is a workaround.
682 This new version of clang introduces a number of new warnings, of which
683 the following are most likely to appear:
687 This warns in two cases, for both C and C++:
688 * When the code is trying to take the absolute value of an unsigned
689 quantity, which is effectively a no-op, and almost never what was
690 intended. The code should be fixed, if at all possible. If you are
691 sure that the unsigned quantity can be safely cast to signed, without
692 loss of information or undefined behavior, you can add an explicit
693 cast, or disable the warning.
695 * When the code is trying to take an absolute value, but the called
696 abs() variant is for the wrong type, which can lead to truncation.
697 If you want to disable the warning instead of fixing the code, please
698 make sure that truncation will not occur, or it might lead to unwanted
701 -Wtautological-undefined-compare and
702 -Wundefined-bool-conversion
704 These warn when C++ code is trying to compare 'this' against NULL, while
705 'this' should never be NULL in well-defined C++ code. However, there is
706 some legacy (pre C++11) code out there, which actively abuses this
707 feature, which was less strictly defined in previous C++ versions.
709 Squid and openjdk do this, for example. The warning can be turned off
710 for C++98 and earlier, but compiling the code in C++11 mode might result
711 in unexpected behavior; for example, the parts of the program that are
712 unreachable could be optimized away.
715 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
716 kernel sources have been removed. The .h files remain, since some
717 utilities include them. This will need to be fixed later.
718 If "mount -t oldnfs ..." is attempted, it will fail.
719 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
720 the utilities will report errors.
723 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
724 directories to top level SUBDIR variable when their parent
725 directory is included in LOCAL_DIRS. Users with build systems with
726 such hierarchies and without SUBDIR entries in the parent
727 directory Makefiles should add them or add the directories to
731 faith(4) and faithd(8) have been removed from the base system. Faith
732 has been obsolete for a very long time.
735 vt(4), the new console driver, is enabled by default. It brings
736 support for Unicode and double-width characters, as well as
737 support for UEFI and integration with the KMS kernel video
740 You may need to update your console settings in /etc/rc.conf,
741 most probably the keymap. During boot, /etc/rc.d/syscons will
742 indicate what you need to do.
744 vt(4) still has issues and lacks some features compared to
745 syscons(4). See the wiki for up-to-date information:
746 https://wiki.freebsd.org/Newcons
748 If you want to keep using syscons(4), you can do so by adding
749 the following line to /boot/loader.conf:
753 pjdfstest has been integrated into kyua as an opt-in test suite.
754 Please see share/doc/pjdfstest/README for more details on how to
758 gperf has been removed from the base system for architectures
759 that use clang. Ports that require gperf will obtain it from the
763 pjdfstest has been moved from tools/regression/pjdfstest to
767 At svn r271982, The default linux compat kernel ABI has been adjusted
768 to 2.6.18 in support of the linux-c6 compat ports infrastructure
769 update. If you wish to continue using the linux-f10 compat ports,
770 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
771 encouraged to update their linux-compat packages to linux-c6 during
772 their next update cycle.
775 The ofwfb driver, used to provide a graphics console on PowerPC when
776 using vt(4), no longer allows mmap() of all physical memory. This
777 will prevent Xorg on PowerPC with some ATI graphics cards from
778 initializing properly unless x11-servers/xorg-server is updated to
782 The xdev targets have been converted to using TARGET and
783 TARGET_ARCH instead of XDEV and XDEV_ARCH.
786 The default unbound configuration has been modified to address
787 issues with reverse lookups on networks that use private
788 address ranges. If you use the local_unbound service, run
789 "service local_unbound setup" as root to regenerate your
790 configuration, then "service local_unbound reload" to load the
794 The GNU texinfo and GNU info pages are not built and installed
795 anymore, WITH_INFO knob has been added to allow to built and install
797 UPDATE: see 20150102 entry on texinfo's removal
800 The GNU readline library is now an INTERNALLIB - that is, it is
801 statically linked into consumers (GDB and variants) in the base
802 system, and the shared library is no longer installed. The
803 devel/readline port is available for third party software that
807 The Itanium architecture (ia64) has been removed from the list of
808 known architectures. This is the first step in the removal of the
812 Commit r268115 has added NFSv4.1 server support, merged from
813 projects/nfsv4.1-server. Since this includes changes to the
814 internal interfaces between the NFS related modules, a full
815 build of the kernel and modules will be necessary.
816 __FreeBSD_version has been bumped.
819 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
820 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
821 which differs from the behaviour controlled by this knob.)
824 Maximal length of the serial number in CTL was increased from 16 to
825 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
826 and ctld, need to be rebuilt to work with a new kernel.
829 The libatf-c and libatf-c++ major versions were downgraded to 0 and
830 1 respectively to match the upstream numbers. They were out of
831 sync because, when they were originally added to FreeBSD, the
832 upstream versions were not respected. These libraries are private
833 and not yet built by default, so renumbering them should be a
834 non-issue. However, unclean source trees will yield broken test
835 programs once the operator executes "make delete-old-libs" after a
838 Additionally, the atf-sh binary was made private by moving it into
839 /usr/libexec/. Already-built shell test programs will keep the
840 path to the old binary so they will break after "make delete-old"
843 If you are using WITH_TESTS=yes (not the default), wipe the object
844 tree and rebuild from scratch to prevent spurious test failures.
845 This is only needed once: the misnumbered libraries and misplaced
846 binaries have been added to OptionalObsoleteFiles.inc so they will
847 be removed during a clean upgrade.
850 Clang and llvm have been upgraded to 3.4.1 release.
853 We bogusly installed src.opts.mk in /usr/share/mk. This file should
854 be removed to avoid issues in the future (and has been added to
858 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
859 past, it affected all builds that used the bsd.*.mk files. The old
860 behavior was a bug, but people may have relied upon it. To get this
861 behavior back, you can .include /etc/src.conf from /etc/make.conf
862 (which is still global and isn't changed). This also changes the
863 behavior of incremental builds inside the tree of individual
864 directories. Set MAKESYSPATH to ".../share/mk" to do that.
865 Although this has survived make universe and some upgrade scenarios,
866 other upgrade scenarios may have broken. At least one form of
867 temporary breakage was fixed with MAKESYSPATH settings for buildworld
868 as well... In cases where MAKESYSPATH isn't working with this
869 setting, you'll need to set it to the full path to your tree.
871 One side effect of all this cleaning up is that bsd.compiler.mk
872 is no longer implicitly included by bsd.own.mk. If you wish to
873 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
877 The lindev device has been removed since /dev/full has been made a
878 standard device. __FreeBSD_version has been bumped.
881 The knob WITHOUT_VI was added to the base system, which controls
882 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
883 in order to reorder files share/termcap and didn't build ex(1) as a
884 build tool, so building/installing with WITH_VI is highly advised for
885 build hosts for older releases.
887 This issue has been fixed in stable/9 and stable/10 in r277022 and
888 r276991, respectively.
891 The YES_HESIOD knob has been removed. It has been obsolete for
892 a decade. Please move to using WITH_HESIOD instead or your builds
893 will silently lack HESIOD.
896 The uart(4) driver has been changed with respect to its handling
897 of the low-level console. Previously the uart(4) driver prevented
898 any process from changing the baudrate or the CLOCAL and HUPCL
899 control flags. By removing the restrictions, operators can make
900 changes to the serial console port without having to reboot.
901 However, when getty(8) is started on the serial device that is
902 associated with the low-level console, a misconfigured terminal
903 line in /etc/ttys will now have a real impact.
904 Before upgrading the kernel, make sure that /etc/ttys has the
905 serial console device configured as 3wire without baudrate to
906 preserve the previous behaviour. E.g:
907 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
910 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
911 to improve performance. To re-enable it, if needed, run rpcbind
912 with command line option -W.
915 Switched back to the GPL dtc compiler due to updates in the upstream
916 dts files not being supported by the BSDL dtc compiler. You will need
917 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
918 may result while building dtb files during a kernel build if you fail
919 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
922 Clang and llvm have been upgraded to 3.4 release.
925 The nve(4) driver has been removed. Please use the nfe(4) driver
926 for NVIDIA nForce MCP Ethernet adapters instead.
929 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
930 This could cause certain C++ applications using shared libraries built
931 against the previous version of libc++ to crash. The incompatibility
932 has now been fixed, but any C++ applications or shared libraries built
933 between r261283 and r261801 should be recompiled.
936 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
937 capability mode support. Please note that enabling the feature in
938 kernel is still highly recommended.
941 OpenSSH is now built with sandbox support, and will use sandbox as
942 the default privilege separation method. This requires Capsicum
943 capability mode support in kernel.
946 The libelf and libdwarf libraries have been updated to newer
947 versions from upstream. Shared library version numbers for
948 these two libraries were bumped. Any ports or binaries
949 requiring these two libraries should be recompiled.
950 __FreeBSD_version is bumped to 1100006.
953 If a Makefile in a tests/ directory was auto-generating a Kyuafile
954 instead of providing an explicit one, this would prevent such
955 Makefile from providing its own Kyuafile in the future during
956 NO_CLEAN builds. This has been fixed in the Makefiles but manual
957 intervention is needed to clean an objdir if you use NO_CLEAN:
958 # find /usr/obj -name Kyuafile | xargs rm -f
961 The behavior of gss_pseudo_random() for the krb5 mechanism
962 has changed, for applications requesting a longer random string
963 than produced by the underlying enctype's pseudo-random() function.
964 In particular, the random string produced from a session key of
965 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
966 be different at the 17th octet and later, after this change.
967 The counter used in the PRF+ construction is now encoded as a
968 big-endian integer in accordance with RFC 4402.
969 __FreeBSD_version is bumped to 1100004.
972 The WITHOUT_ATF build knob has been removed and its functionality
973 has been subsumed into the more generic WITHOUT_TESTS. If you were
974 using the former to disable the build of the ATF libraries, you
975 should change your settings to use the latter.
978 The default version of mtree is nmtree which is obtained from
979 NetBSD. The output is generally the same, but may vary
980 slightly. If you found you need identical output adding
981 "-F freebsd9" to the command line should do the trick. For the
982 time being, the old mtree is available as fmtree.
985 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
986 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
987 1.1.4_8 and verify bsdyml not linked in, before running "make
989 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
991 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
994 The stable/10 branch has been created in subversion from head
998 The rc.d/jail script has been updated to support jail(8)
999 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1000 for per-jail configuration are automatically converted to
1001 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1002 This is transparently backward compatible. See below about some
1003 incompatibilities and rc.conf(5) manual page for more details.
1005 These variables are now deprecated in favor of jail(8) configuration
1006 file. One can use "rc.d/jail config <jname>" command to generate
1007 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1008 running the jail(8) utility. The default pathname of the
1009 configuration file is /etc/jail.conf and can be specified by
1010 using $jail_conf or $jail_<jname>_conf variables.
1012 Please note that jail_devfs_ruleset accepts an integer at
1013 this moment. Please consider to rewrite the ruleset name
1017 BIND has been removed from the base system. If all you need
1018 is a local resolver, simply enable and start the local_unbound
1019 service instead. Otherwise, several versions of BIND are
1020 available in the ports tree. The dns/bind99 port is one example.
1022 With this change, nslookup(1) and dig(1) are no longer in the base
1023 system. Users should instead use host(1) and drill(1) which are
1024 in the base system. Alternatively, nslookup and dig can
1025 be obtained by installing the dns/bind-tools port.
1028 With the addition of unbound(8), a new unbound user is now
1029 required during installworld. "mergemaster -p" can be used to
1030 add the user prior to installworld, as documented in the handbook.
1033 OpenSSH is now built with DNSSEC support, and will by default
1034 silently trust signed SSHFP records. This can be controlled with
1035 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1036 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1039 The GNU Compiler Collection and C++ standard library (libstdc++)
1040 are no longer built by default on platforms where clang is the system
1041 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1042 options in src.conf.
1045 The PROCDESC kernel option is now part of the GENERIC kernel
1046 configuration and is required for the rwhod(8) to work.
1047 If you are using custom kernel configuration, you should include
1051 The API and ABI related to the Capsicum framework was modified
1052 in backward incompatible way. The userland libraries and programs
1053 have to be recompiled to work with the new kernel. This includes the
1054 following libraries and programs, but the whole buildworld is
1055 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1056 kdump, procstat, rwho, rwhod, uniq.
1059 AES-NI intrinsic support has been added to gcc. The AES-NI module
1060 has been updated to use this support. A new gcc is required to build
1061 the aesni module on both i386 and amd64.
1064 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1065 Thus "device padlock_rng" and "device rdrand_rng" should be
1066 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1069 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1070 enables just the iconv* functionality and is now on by default.
1071 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1072 compatibility. Set WITHOUT_ICONV to build the old way.
1073 If you have been using WITH_ICONV before, you will very likely
1074 need to turn on WITH_LIBICONV_COMPAT.
1077 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1078 Illumos origin, including ZFS. If you have INVARIANTS in your
1079 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1081 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1082 locks if WITNESS option was set. Because that generated a lot of
1083 witness(9) reports and all of them were believed to be false
1084 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1085 can be used to achieve the previous behavior.
1088 Timer values in IPv6 data structures now use time_uptime instead
1089 of time_second. Although this is not a user-visible functional
1090 change, userland utilities which directly use them---ndp(8),
1091 rtadvd(8), and rtsold(8) in the base system---need to be updated
1092 to r253970 or later.
1095 find -delete can now delete the pathnames given as arguments,
1096 instead of only files found below them or if the pathname did
1097 not contain any slashes. Formerly, the following error message
1100 find: -delete: <path>: relative path potentially not safe
1102 Deleting the pathnames given as arguments can be prevented
1103 without error messages using -mindepth 1 or by changing
1104 directory and passing "." as argument to find. This works in the
1105 old as well as the new version of find.
1108 Behavior of devfs rules path matching has been changed.
1109 Pattern is now always matched against fully qualified devfs
1110 path and slash characters must be explicitly matched by
1111 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1112 subdirectories must be reviewed.
1115 The default ARM ABI has changed to the ARM EABI. The old ABI is
1116 incompatible with the ARM EABI and all programs and modules will
1117 need to be rebuilt to work with a new kernel.
1119 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1121 NOTE: Support for the old ABI will be removed in the future and
1122 users are advised to upgrade.
1125 pkg_install has been disconnected from the build if you really need it
1126 you should add WITH_PKGTOOLS in your src.conf(5).
1129 Most of network statistics structures were changed to be able
1130 keep 64-bits counters. Thus all tools, that work with networking
1131 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1134 Fix a bug that allowed a tracing process (e.g. gdb) to write
1135 to a memory-mapped file in the traced process's address space
1136 even if neither the traced process nor the tracing process had
1137 write access to that file.
1140 CVS has been removed from the base system. An exact copy
1141 of the code is available from the devel/cvs port.
1144 Some people report the following error after the switch to bmake:
1146 make: illegal option -- J
1147 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1149 *** [buildworld] Error code 2
1151 this likely due to an old instance of make in
1152 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1153 which src/Makefile will use that blindly, if it exists, so if
1154 you see the above error:
1156 rm -rf `make -V MAKEPATH`
1161 Use bmake by default.
1162 Whereas before one could choose to build with bmake via
1163 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1164 make. The goal is to remove these knobs for 10-RELEASE.
1166 It is worth noting that bmake (like gmake) treats the command
1167 line as the unit of failure, rather than statements within the
1168 command line. Thus '(cd some/where && dosomething)' is safer
1169 than 'cd some/where; dosomething'. The '()' allows consistent
1170 behavior in parallel build.
1173 Fix a bug that allows NFS clients to issue READDIR on files.
1176 The WITHOUT_IDEA option has been removed because
1177 the IDEA patent expired.
1180 The sysctl which controls TRIM support under ZFS has been renamed
1181 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1185 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1186 rather than creating it's own in the temporary directory in
1187 order allow access to bootstrapped versions of tools such as
1188 install and mtree. When upgrading from version of FreeBSD where
1189 the install command does not support -l, you will need to
1190 install a new mergemaster command if mergemaster -p is required.
1191 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1195 Legacy ATA stack, disabled and replaced by new CAM-based one since
1196 FreeBSD 9.0, completely removed from the sources. Kernel modules
1197 atadisk and atapi*, user-level tools atacontrol and burncd are
1198 removed. Kernel option `options ATA_CAM` is now permanently enabled
1202 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1203 and socketpair(2). Software, in particular Kerberos, may
1204 automatically detect and use these during building. The resulting
1205 binaries will not work on older kernels.
1208 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1209 information, see the respective 20130304 entry).
1212 Recent commits to callout(9) changed the size of struct callout,
1213 so the KBI is probably heavily disturbed. Also, some functions
1214 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1215 by macros. Every kernel module using it won't load, so rebuild
1218 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1219 but does not initialize by default (because of the new CTL_DISABLE
1220 option) to save memory. To re-enable it, remove the CTL_DISABLE
1221 option from the kernel config file or set kern.cam.ctl.disable=0
1222 in /boot/loader.conf.
1225 The ctl device has been disabled in GENERIC for i386 and amd64.
1226 This was done due to the extra memory being allocated at system
1227 initialisation time by the ctl driver which was only used if
1228 a CAM target device was created. This makes a FreeBSD system
1229 unusable on 128MB or less of RAM.
1232 A new compression method (lz4) has been merged to -HEAD. Please
1233 refer to zpool-features(7) for more information.
1235 Please refer to the "ZFS notes" section of this file for information
1236 on upgrading boot ZFS pools.
1239 A BSD-licensed patch(1) variant has been added and is installed
1240 as bsdpatch, being the GNU version the default patch.
1241 To inverse the logic and use the BSD-licensed one as default,
1242 while having the GNU version installed as gnupatch, rebuild
1243 and install world with the WITH_BSD_PATCH knob set.
1246 Due to the use of the new -l option to install(1) during build
1247 and install, you must take care not to directly set the INSTALL
1248 make variable in your /etc/make.conf, /etc/src.conf, or on the
1249 command line. If you wish to use the -C flag for all installs
1250 you may be able to add INSTALL+=-C to /etc/make.conf or
1254 The install(1) option -M has changed meaning and now takes an
1255 argument that is a file or path to append logs to. In the
1256 unlikely event that -M was the last option on the command line
1257 and the command line contained at least two files and a target
1258 directory the first file will have logs appended to it. The -M
1259 option served little practical purpose in the last decade so its
1260 use is expected to be extremely rare.
1263 After switching to Clang as the default compiler some users of ZFS
1264 on i386 systems started to experience stack overflow kernel panics.
1265 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1268 GEOM_LABEL now mangles label names read from file system metadata.
1269 Mangling affect labels containing spaces, non-printable characters,
1270 '%' or '"'. Device names in /etc/fstab and other places may need to
1274 By default, only the 10 most recent kernel dumps will be saved. To
1275 restore the previous behaviour (no limit on the number of kernel dumps
1276 stored in the dump directory) add the following line to /etc/rc.conf:
1281 With the addition of auditdistd(8), a new auditdistd user is now
1282 required during installworld. "mergemaster -p" can be used to
1283 add the user prior to installworld, as documented in the handbook.
1286 The sin6_scope_id member variable in struct sockaddr_in6 is now
1287 filled by the kernel before passing the structure to the userland via
1288 sysctl or routing socket. This means the KAME-specific embedded scope
1289 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1290 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1291 __FreeBSD_version is bumped to 1000025.
1294 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1295 This means that the world and kernel will be compiled with clang
1296 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1297 and /usr/bin/cpp. To disable this behavior and revert to building
1298 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1299 of current may need to bootstrap WITHOUT_CLANG first if the clang
1300 build fails (its compatibility window doesn't extend to the 9 stable
1304 The IPFIREWALL_FORWARD kernel option has been removed. Its
1305 functionality now turned on by default.
1308 The ZERO_COPY_SOCKET kernel option has been removed and
1309 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1310 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1311 mechanism which is not safe and may result in kernel crashes.
1312 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1313 driver supports disposeable external page sized mbuf storage.
1314 Proper replacements for both zero-copy mechanisms are under
1315 consideration and will eventually lead to complete removal
1316 of the two kernel options.
1319 The IPv4 network stack has been converted to network byte
1320 order. The following modules need to be recompiled together
1321 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1322 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1325 Support for non-MPSAFE filesystems was removed from VFS. The
1326 VFS_VERSION was bumped, all filesystem modules shall be
1330 All the non-MPSAFE filesystems have been disconnected from
1331 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1332 portalfs, smbfs, xfs.
1335 The interface cloning API and ABI has changed. The following
1336 modules need to be recompiled together with kernel:
1337 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1338 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1339 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1342 The sdhci driver was split in two parts: sdhci (generic SD Host
1343 Controller logic) and sdhci_pci (actual hardware driver).
1344 No kernel config modifications are required, but if you
1345 load sdhc as a module you must switch to sdhci_pci instead.
1348 Import the FUSE kernel and userland support into base system.
1351 The GNU sort(1) program has been removed since the BSD-licensed
1352 sort(1) has been the default for quite some time and no serious
1353 problems have been reported. The corresponding WITH_GNU_SORT
1357 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1358 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1362 The net80211(4) ABI has been changed to allow for improved driver
1363 PS-POLL and power-save support. All wireless drivers need to be
1364 recompiled to work with the new kernel.
1367 The random(4) support for the VIA hardware random number
1368 generator (`PADLOCK') is no longer enabled unconditionally.
1369 Add the padlock_rng device in the custom kernel config if
1370 needed. The GENERIC kernels on i386 and amd64 do include the
1371 device, so the change only affects the custom kernel
1375 The pf(4) packet filter ABI has been changed. pfctl(8) and
1376 snmp_pf module need to be recompiled to work with new kernel.
1379 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1380 to -HEAD. Pools that have empty_bpobj in active state can not be
1381 imported read-write with ZFS implementations that do not support
1382 this feature. For more information read the zpool-features(5)
1386 The sparc64 ZFS loader has been changed to no longer try to auto-
1387 detect ZFS providers based on diskN aliases but now requires these
1388 to be explicitly listed in the OFW boot-device environment variable.
1391 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1392 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1393 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1396 The following sysctls and tunables have been renamed for consistency
1397 with other variables:
1398 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1399 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1402 The sort utility has been replaced with BSD sort. For now, GNU sort
1403 is also available as "gnusort" or the default can be set back to
1404 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1405 installed as "bsdsort".
1408 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1409 Starting with this version the old system of ZFS pool versioning
1410 is superseded by "feature flags". This concept enables forward
1411 compatibility against certain future changes in functionality of ZFS
1412 pools. The first read-only compatible "feature flag" for ZFS pools
1413 is named "com.delphix:async_destroy". For more information
1414 read the new zpool-features(5) manual page.
1415 Please refer to the "ZFS notes" section of this file for information
1416 on upgrading boot ZFS pools.
1419 The malloc(3) implementation embedded in libc now uses sources imported
1420 as contrib/jemalloc. The most disruptive API change is to
1421 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1422 delete it prior to installworld, and optionally re-create it using the
1423 new format after rebooting. See malloc.conf(5) for details
1424 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1428 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1429 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1430 now spelled mips. This is to aid compatibility with third-party
1431 software that expects this naming scheme in uname(3). Little-endian
1432 settings are unchanged. If you are updating a big-endian mips64 machine
1433 from before this change, you may need to set MACHINE_ARCH=mips64 in
1434 your environment before the new build system will recognize your machine.
1437 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1441 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1442 nullfs(5) did not pass through all behaviours to the underlying layer,
1443 as a result if we bound to a socket on the lower layer we could connect
1444 only to the lower path; if we bound to the upper layer we could connect
1445 only to the upper path. The new behavior is one can connect to both the
1446 lower and the upper paths regardless what layer path one binds to.
1449 The getifaddrs upgrade path broken with 20111215 has been restored.
1450 If you have upgraded in between 20111215 and 20120209 you need to
1451 recompile libc again with your kernel. You still need to recompile
1452 world to be able to configure CARP but this restriction already
1453 comes from 20111215.
1456 The set_rcvar() function has been removed from /etc/rc.subr. All
1457 base and ports rc.d scripts have been updated, so if you have a
1458 port installed with a script in /usr/local/etc/rc.d you can either
1459 hand-edit the rcvar= line, or reinstall the port.
1461 An easy way to handle the mass-update of /etc/rc.d:
1462 rm /etc/rc.d/* && mergemaster -i
1465 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1466 on the current CPU and prevents other threads from running.
1467 This behavior can be reverted using the kern.stop_scheduler_on_panic
1469 The new behavior can be incompatible with kern.sync_on_panic.
1472 The carp(4) facility has been changed significantly. Configuration
1473 of the CARP protocol via ifconfig(8) has changed, as well as format
1474 of CARP events submitted to devd(8) has changed. See manual pages
1475 for more information. The arpbalance feature of carp(4) is currently
1476 not supported anymore.
1478 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1479 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1480 need to be recompiled.
1483 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1487 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1488 explicitely support non-MPSAFE filesystems.
1489 It is on by default for all supported platform at this present
1493 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1494 i386 and pc98 GENERIC kernel configuration files.
1497 sysinstall has been removed
1500 The stable/9 branch created in subversion. This corresponds to the
1501 RELENG_9 branch in CVS.
1507 Avoid using make -j when upgrading. While generally safe, there are
1508 sometimes problems using -j to upgrade. If your upgrade fails with
1509 -j, please try again without -j. From time to time in the past there
1510 have been problems using -j with buildworld and/or installworld. This
1511 is especially true when upgrading between "distant" versions (eg one
1512 that cross a major release boundary or several minor releases, or when
1513 several months have passed on the -current branch).
1515 Sometimes, obscure build problems are the result of environment
1516 poisoning. This can happen because the make utility reads its
1517 environment when searching for values for global variables. To run
1518 your build attempts in an "environmental clean room", prefix all make
1519 commands with 'env -i '. See the env(1) manual page for more details.
1521 When upgrading from one major version to another it is generally best to
1522 upgrade to the latest code in the currently installed branch first, then
1523 do an upgrade to the new branch. This is the best-tested upgrade path,
1524 and has the highest probability of being successful. Please try this
1525 approach if you encounter problems with a major version upgrade. Since
1526 the stable 4.x branch point, one has generally been able to upgade from
1527 anywhere in the most recent stable branch to head / current (or even the
1528 last couple of stable branches). See the top of this file when there's
1531 When upgrading a live system, having a root shell around before
1532 installing anything can help undo problems. Not having a root shell
1533 around can lead to problems if pam has changed too much from your
1534 starting point to allow continued authentication after the upgrade.
1536 This file should be read as a log of events. When a later event changes
1537 information of a prior event, the prior event should not be deleted.
1538 Instead, a pointer to the entry with the new information should be
1539 placed in the old entry. Readers of this file should also sanity check
1540 older entries before relying on them blindly. Authors of new entries
1541 should write them with this in mind.
1545 When upgrading the boot ZFS pool to a new version, always follow
1548 1.) recompile and reinstall the ZFS boot loader and boot block
1549 (this is part of "make buildworld" and "make installworld")
1551 2.) update the ZFS boot block on your boot drive
1553 The following example updates the ZFS boot block on the first
1554 partition (freebsd-boot) of a GPT partitioned drive ada0:
1555 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1557 Non-boot pools do not need these updates.
1561 If you are updating from a prior version of FreeBSD (even one just
1562 a few days old), you should follow this procedure. It is the most
1563 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1565 make kernel-toolchain
1566 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1567 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1569 To test a kernel once
1570 ---------------------
1571 If you just want to boot a kernel once (because you are not sure
1572 if it works, or if you want to boot a known bad kernel to provide
1573 debugging information) run
1574 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1575 nextboot -k testkernel
1577 To just build a kernel when you know that it won't mess you up
1578 --------------------------------------------------------------
1579 This assumes you are already running a CURRENT system. Replace
1580 ${arch} with the architecture of your machine (e.g. "i386",
1581 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1583 cd src/sys/${arch}/conf
1584 config KERNEL_NAME_HERE
1585 cd ../compile/KERNEL_NAME_HERE
1590 If this fails, go to the "To build a kernel" section.
1592 To rebuild everything and install it on the current system.
1593 -----------------------------------------------------------
1594 # Note: sometimes if you are running current you gotta do more than
1595 # is listed here if you are upgrading from a really old current.
1597 <make sure you have good level 0 dumps>
1599 make kernel KERNCONF=YOUR_KERNEL_HERE
1601 <reboot in single user> [3]
1608 To cross-install current onto a separate partition
1609 --------------------------------------------------
1610 # In this approach we use a separate partition to hold
1611 # current's root, 'usr', and 'var' directories. A partition
1612 # holding "/", "/usr" and "/var" should be about 2GB in
1615 <make sure you have good level 0 dumps>
1618 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1619 <maybe newfs current's root partition>
1620 <mount current's root partition on directory ${CURRENT_ROOT}>
1621 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1622 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1623 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1624 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1625 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1626 <reboot into current>
1627 <do a "native" rebuild/install as described in the previous section>
1628 <maybe install compatibility libraries from ports/misc/compat*>
1632 To upgrade in-place from stable to current
1633 ----------------------------------------------
1634 <make sure you have good level 0 dumps>
1636 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1638 <reboot in single user> [3]
1645 Make sure that you've read the UPDATING file to understand the
1646 tweaks to various things you need. At this point in the life
1647 cycle of current, things change often and you are on your own
1648 to cope. The defaults can also change, so please read ALL of
1649 the UPDATING entries.
1651 Also, if you are tracking -current, you must be subscribed to
1652 freebsd-current@freebsd.org. Make sure that before you update
1653 your sources that you have read and understood all the recent
1654 messages there. If in doubt, please track -stable which has
1655 much fewer pitfalls.
1657 [1] If you have third party modules, such as vmware, you
1658 should disable them at this point so they don't crash your
1661 [3] From the bootblocks, boot -s, and then do
1666 adjkerntz -i # if CMOS is wall time
1667 Also, when doing a major release upgrade, it is required that
1668 you boot into single user mode to do the installworld.
1670 [4] Note: This step is non-optional. Failure to do this step
1671 can result in a significant reduction in the functionality of the
1672 system. Attempting to do it by hand is not recommended and those
1673 that pursue this avenue should read this file carefully, as well
1674 as the archives of freebsd-current and freebsd-hackers mailing lists
1675 for potential gotchas. The -U option is also useful to consider.
1676 See mergemaster(8) for more information.
1678 [5] Usually this step is a noop. However, from time to time
1679 you may need to do this if you get unknown user in the following
1680 step. It never hurts to do it all the time. You may need to
1681 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1682 install) after the buildworld before this step if you last updated
1683 from current before 20130425 or from -stable before 20130430.
1685 [6] This only deletes old files and directories. Old libraries
1686 can be deleted by "make delete-old-libs", but you have to make
1687 sure that no program is using those libraries anymore.
1689 [8] In order to have a kernel that can run the 4.x binaries needed to
1690 do an installworld, you must include the COMPAT_FREEBSD4 option in
1691 your kernel. Failure to do so may leave you with a system that is
1692 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1693 required to run the 5.x binaries on more recent kernels. And so on
1694 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1696 Make sure that you merge any new devices from GENERIC since the
1697 last time you updated your kernel config file.
1699 [9] When checking out sources, you must include the -P flag to have
1700 cvs prune empty directories.
1702 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1703 "?=" instead of the "=" assignment operator, so that buildworld can
1704 override the CPUTYPE if it needs to.
1706 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1707 not on the command line, or in /etc/make.conf. buildworld will
1708 warn if it is improperly defined.
1711 This file contains a list, in reverse chronological order, of major
1712 breakages in tracking -current. It is not guaranteed to be a complete
1713 list of such breakages, and only contains entries since September 23, 2011.
1714 If you need to see UPDATING entries from before that date, you will need
1715 to fetch an UPDATING file from an older FreeBSD release.
1717 Copyright information:
1719 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1721 Redistribution, publication, translation and use, with or without
1722 modification, in full or in part, in any form or format of this
1723 document are permitted without further permission from the author.
1725 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1726 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1727 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1728 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1729 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1730 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1731 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1732 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1733 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1734 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1735 POSSIBILITY OF SUCH DAMAGE.
1737 Contact Warner Losh if you have any questions about your use of