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