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