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