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