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