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