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