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 isl(4) and cyapa(4) drivers now require a new driver,
56 chromebook_platform(4), to work properly on Chromebook-class hardware.
57 On other types of hardware the drivers may need to be configured using
58 device hints. Please see the corresponding manual pages for details.
61 The urtwn(4) driver was merged into rtwn(4) and now consists of
62 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
64 Also, firmware for RTL8188CE was renamed due to possible name
65 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
68 GNU rcs has been removed from base. It is available as packages:
69 - rcs: Latest GPLv3 GNU rcs version.
70 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
74 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
75 modules now requires that the kernel configuration contain the
76 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
79 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
80 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
83 Relocatable object files with the extension of .So have been renamed
84 to use an extension of .pico instead. The purpose of this change is
85 to avoid a name clash with shared libraries on case-insensitive file
86 systems. On those file systems, foo.So is the same file as foo.so.
89 GNU rcs has been turned off by default. It can (temporarily) be built
90 again by adding WITH_RCS knob in src.conf.
91 Otherwise, GNU rcs is available from packages:
92 - rcs: Latest GPLv3 GNU rcs version.
93 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
96 The backup_uses_rcs functionality has been removed from rc.subr.
99 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
100 two separate components, QUEUE_MACRO_DEBUG_TRACE and
101 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
102 QUEUE_MACRO_DEBUG behavior.
105 r304787 changed some ioctl interfaces between the iSCSI userspace
106 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
107 rebuilt to work with new kernels. __FreeBSD_version has been bumped
111 The UDP receive code has been updated to only treat incoming UDP
112 packets that were addressed to an L2 broadcast address as L3
113 broadcast packets. It is not expected that this will affect any
114 standards-conforming UDP application. The new behaviour can be
115 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
119 Remove the openbsd_poll system call.
120 __FreeBSD_version has been bumped because of this.
123 The libc stub for the pipe(2) system call has been replaced with
124 a wrapper that calls the pipe2(2) system call and the pipe(2)
125 system call is now only implemented by the kernels that include
126 "options COMPAT_FREEBSD10" in their config file (this is the
127 default). Users should ensure that this option is enabled in
128 their kernel or upgrade userspace to r302092 before upgrading their
132 CAM will now strip leading spaces from SCSI disks' serial numbers.
133 This will affect users who create UFS filesystems on SCSI disks using
134 those disk's diskid device nodes. For example, if /etc/fstab
135 previously contained a line like
136 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
137 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
138 transforms like gmirror may also be affected. ZFS users should
142 The bitstring(3) API has been updated with new functionality and
143 improved performance. But it is binary-incompatible with the old API.
144 Objects built with the new headers may not be linked against objects
145 built with the old headers.
148 The brk and sbrk functions have been removed from libc on arm64.
149 Binutils from ports has been updated to not link to these
150 functions and should be updated to the latest version before
151 installing a new libc.
154 The armv6 port now defaults to hard float ABI. Limited support
155 for running both hardfloat and soft float on the same system
156 is available using the libraries installed with -DWITH_LIBSOFT.
157 This has only been tested as an upgrade path for installworld
158 and packages may fail or need manual intervention to run. New
159 packages will be needed.
161 To update an existing self-hosted armv6hf system, you must add
162 TARGET_ARCH=armv6 on the make command line for both the build
163 and the install steps.
166 Kernel modules compiled outside of a kernel build now default to
167 installing to /boot/modules instead of /boot/kernel. Many kernel
168 modules built this way (such as those in ports) already overrode
169 KMODDIR explicitly to install into /boot/modules. However,
170 manually building and installing a module from /sys/modules will
171 now install to /boot/modules instead of /boot/kernel.
174 The CAM I/O scheduler has been committed to the kernel. There should be
175 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
176 list of known rogues that claim support for this but actually corrupt
177 data is believed to be complete, be on the lookout for data
178 corruption. The known rogue list is believed to be complete:
180 o Crucial MX100, M550 drives with MU01 firmware.
181 o Micron M510 and M550 drives with MU01 firmware.
182 o Micron M500 prior to MU07 firmware
183 o Samsung 830, 840, and 850 all firmwares
184 o FCCT M500 all firmwares
186 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
187 with working NCQ TRIM. For Micron branded drives, see your sales rep for
188 updated firmware. Black listed drives will work correctly because these
189 drives work correctly so long as no NCQ TRIMs are sent to them. Given
190 this list is the same as found in Linux, it's believed there are no
191 other rogues in the market place. All other models from the above
194 To be safe, if you are at all concerned, you can quirk each of your
195 drives to prevent NCQ from being sent by setting:
196 kern.cam.ada.X.quirks="0x2"
197 in loader.conf. If the drive requires the 4k sector quirk, set the
201 The FAST_DEPEND build option has been removed and its functionality is
202 now the one true way. The old mkdep(1) style of 'make depend' has
203 been removed. See 20160311 for further details.
206 Resource range types have grown from unsigned long to uintmax_t. All
207 drivers, and anything using libdevinfo, need to be recompiled.
210 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
211 builds. It no longer runs mkdep(1) during 'make depend', and the
212 'make depend' stage can safely be skipped now as it is auto ran
213 when building 'make all' and will generate all SRCS and DPSRCS before
214 building anything else. Dependencies are gathered at compile time with
215 -MF flags kept in separate .depend files per object file. Users should
216 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
220 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
221 kernel modules. Therefore, if you load any kernel modules at boot time,
222 please install the boot loaders after you install the kernel, but before
226 make kernel KERNCONF=YOUR_KERNEL_HERE
227 make -C sys/boot install
228 <reboot in single user>
230 Then follow the usual steps, described in the General Notes section,
234 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
235 see the 20141231 entry below for information about prerequisites and
236 upgrading, if you are not already using clang 3.5.0 or higher.
239 The AIO subsystem is now a standard part of the kernel. The
240 VFS_AIO kernel option and aio.ko kernel module have been removed.
241 Due to stability concerns, asynchronous I/O requests are only
242 permitted on sockets and raw disks by default. To enable
243 asynchronous I/O requests on all file types, set the
244 vfs.aio.enable_unsafe sysctl to a non-zero value.
247 The ELF object manipulation tool objcopy is now provided by the
248 ELF Tool Chain project rather than by GNU binutils. It should be a
249 drop-in replacement, with the addition of arm64 support. The
250 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
251 to obtain the GNU version if necessary.
254 Building ZFS pools on top of zvols is prohibited by default. That
255 feature has never worked safely; it's always been prone to deadlocks.
256 Using a zvol as the backing store for a VM guest's virtual disk will
257 still work, even if the guest is using ZFS. Legacy behavior can be
258 restored by setting vfs.zfs.vol.recursive=1.
261 The NONE and HPN patches has been removed from OpenSSH. They are
262 still available in the security/openssh-portable port.
265 With the addition of ypldap(8), a new _ypldap user is now required
266 during installworld. "mergemaster -p" can be used to add the user
267 prior to installworld, as documented in the handbook.
270 The tftp loader (pxeboot) now uses the option root-path directive. As a
271 consequence it no longer looks for a pxeboot.4th file on the tftp
272 server. Instead it uses the regular /boot infrastructure as with the
276 The code to start recording plug and play data into the modules has
277 been committed. While the old tools will properly build a new kernel,
278 a number of warnings about "unknown metadata record 4" will be produced
279 for an older kldxref. To avoid such warnings, make sure to rebuild
280 the kernel toolchain (or world). Make sure that you have r292078 or
281 later when trying to build 292077 or later before rebuilding.
284 Debug data files are now built by default with 'make buildworld' and
285 installed with 'make installworld'. This facilitates debugging but
286 requires more disk space both during the build and for the installed
287 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
291 r291527 changed the internal interface between the nfsd.ko and
292 nfscommon.ko modules. As such, they must both be upgraded to-gether.
293 __FreeBSD_version has been bumped because of this.
296 Add support for unicode collation strings leads to a change of
297 order of files listed by ls(1) for example. To get back to the old
298 behaviour, set LC_COLLATE environment variable to "C".
300 Databases administrators will need to reindex their databases given
301 collation results will be different.
303 Due to a bug in install(1) it is recommended to remove the ancient
304 locales before running make installworld.
306 rm -rf /usr/share/locale/*
309 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
310 libcrypto.so.7 or libssl.so.7 must be recompiled.
313 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
314 Kernel modules isp_2400_multi and isp_2500_multi were removed and
315 should be replaced with isp_2400 and isp_2500 modules respectively.
318 The build previously allowed using 'make -n' to not recurse into
319 sub-directories while showing what commands would be executed, and
320 'make -n -n' to recursively show commands. Now 'make -n' will recurse
321 and 'make -N' will not.
324 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
325 and etcupdate will now use this file. A custom sendmail.cf is now
326 updated via this mechanism rather than via installworld. If you had
327 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
328 want to remove the exclusion or change it to "always install".
329 /etc/mail/sendmail.cf is now managed the same way regardless of
330 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
331 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
334 Compatibility shims for legacy ATA device names have been removed.
335 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
336 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
337 environment variables, /dev/ad* and /dev/ar* symbolic links.
340 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
341 Please see the 20141231 entry below for information about prerequisites
342 and upgrading, if you are not already using clang 3.5.0 or higher.
345 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
346 and renamed from .symbols to .debug. This reduces the size requirements
347 on the boot partition or file system and provides consistency with
348 userland debug files.
350 When using the supported kernel installation method the
351 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
352 as is done with /boot/kernel.
354 Developers wishing to maintain the historical behavior of installing
355 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
358 The wireless drivers had undergone changes that remove the 'parent
359 interface' from the ifconfig -l output. The rc.d network scripts
360 used to check presence of a parent interface in the list, so old
361 scripts would fail to start wireless networking. Thus, etcupdate(3)
362 or mergemaster(8) run is required after kernel update, to update your
363 rc.d scripts in /etc.
366 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
367 These configurations are now automatically interpreted as
368 'scrub fragment reassemble'.
371 Kernel-loadable modules for the random(4) device are back. To use
372 them, the kernel must have
375 options RANDOM_LOADABLE
377 kldload(8) can then be used to load random_fortuna.ko
378 or random_yarrow.ko. Please note that due to the indirect
379 function calls that the loadable modules need to provide,
380 the build-in variants will be slightly more efficient.
382 The random(4) kernel option RANDOM_DUMMY has been retired due to
383 unpopularity. It was not all that useful anyway.
386 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
387 Control over building the ELF Tool Chain tools is now provided by
388 the WITHOUT_TOOLCHAIN knob.
391 The polarity of Pulse Per Second (PPS) capture events with the
392 uart(4) driver has been corrected. Prior to this change the PPS
393 "assert" event corresponded to the trailing edge of a positive PPS
394 pulse and the "clear" event was the leading edge of the next pulse.
396 As the width of a PPS pulse in a typical GPS receiver is on the
397 order of 1 millisecond, most users will not notice any significant
398 difference with this change.
400 Anyone who has compensated for the historical polarity reversal by
401 configuring a negative offset equal to the pulse width will need to
402 remove that workaround.
405 The default group assigned to /dev/dri entries has been changed
406 from 'wheel' to 'video' with the id of '44'. If you want to have
407 access to the dri devices please add yourself to the video group
410 # pw groupmod video -m $USER
413 The menu.rc and loader.rc files will now be replaced during
414 upgrades. Please migrate local changes to menu.rc.local and
415 loader.rc.local instead.
418 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
419 strings and strip have been removed. The src.conf(5) knob
420 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
423 As ZFS requires more kernel stack pages than is the default on some
424 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
425 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
427 Please consider using 'options KSTACK_PAGES=X' where X is greater
428 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
431 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
432 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
433 default, i.e., they will not contain "::". For example, instead
434 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
435 to have a more specific match, such as different map entries for
436 IPv6:0:0 vs IPv6:0. This change requires that configuration
437 data (including maps, files, classes, custom ruleset, etc.) must
438 use the same format, so make certain such configuration data is
439 upgrading. As a very simple check search for patterns like
440 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
441 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
442 the cf option UseCompressedIPv6Addresses.
445 The default kernel entropy-processing algorithm is now
446 Fortuna, replacing Yarrow.
448 Assuming you have 'device random' in your kernel config
449 file, the configurations allow a kernel option to override
450 this default. You may choose *ONE* of:
452 options RANDOM_YARROW # Legacy /dev/random algorithm.
453 options RANDOM_DUMMY # Blocking-only driver.
455 If you have neither, you get Fortuna. For most people,
456 read no further, Fortuna will give a /dev/random that works
457 like it always used to, and the difference will be irrelevant.
459 If you remove 'device random', you get *NO* kernel-processed
460 entropy at all. This may be acceptable to folks building
461 embedded systems, but has complications. Carry on reading,
462 and it is assumed you know what you need.
464 *PLEASE* read random(4) and random(9) if you are in the
465 habit of tweaking kernel configs, and/or if you are a member
466 of the embedded community, wanting specific and not-usual
467 behaviour from your security subsystems.
469 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
470 random', you will NOT have a functioning /dev/random, and
471 many cryptographic features will not work, including SSH.
472 You may also find strange behaviour from the random(3) set
473 of library functions, in particular sranddev(3), srandomdev(3)
474 and arc4random(3). The reason for this is that the KERN_ARND
475 sysctl only returns entropy if it thinks it has some to
476 share, and with RANDOM_DUMMY or no 'device random' this
480 An additional fix for the issue described in the 20150614 sendmail
481 entry below has been been committed in revision 284717.
484 FreeBSD's old make (fmake) has been removed from the system. It is
485 available as the devel/fmake port or via pkg install fmake.
488 The fix for the issue described in the 20150614 sendmail entry
489 below has been been committed in revision 284436. The work
490 around described in that entry is no longer needed unless the
491 default setting is overridden by a confDH_PARAMETERS configuration
492 setting of '5' or pointing to a 512 bit DH parameter file.
495 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
496 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
497 and devel/kyua to version 0.20+ and adjust any calling code to work
498 with Kyuafile and kyua.
501 The import of openssl to address the FreeBSD-SA-15:10.openssl
502 security advisory includes a change which rejects handshakes
503 with DH parameters below 768 bits. sendmail releases prior
504 to 8.15.2 (not yet released), defaulted to a 512 bit
505 DH parameter setting for client connections. To work around
506 this interoperability, sendmail can be configured to use a
507 2048 bit DH parameter by:
509 1. Edit /etc/mail/`hostname`.mc
510 2. If a setting for confDH_PARAMETERS does not exist or
511 exists and is set to a string beginning with '5',
513 3. If a setting for confDH_PARAMETERS exists and is set to
514 a file path, create a new file with:
515 openssl dhparam -out /path/to/file 2048
516 4. Rebuild the .cf file:
517 cd /etc/mail/; make; make install
519 cd /etc/mail/; make restart
521 A sendmail patch is coming, at which time this file will be
525 Generation of legacy formatted entries have been disabled by default
526 in pwd_mkdb(8), as all base system consumers of the legacy formatted
527 entries were converted to use the new format by default when the new,
528 machine independent format have been added and supported since FreeBSD
531 Please see the pwd_mkdb(8) manual page for further details.
534 Clang and llvm have been upgraded to 3.6.1 release. Please see the
535 20141231 entry below for information about prerequisites and upgrading,
536 if you are not already using 3.5.0 or higher.
539 TI platform code switched to using vendor DTS files and this update
540 may break existing systems running on Beaglebone, Beaglebone Black,
543 - dtb files should be regenerated/reinstalled. Filenames are the
544 same but content is different now
545 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
546 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
547 addressing scheme is now pin 25 on /dev/gpioc3.
548 - Pandaboard: /etc/ttys should be updated, serial console device is
549 now /dev/ttyu2, not /dev/ttyu0
552 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
553 If you need the GNU extension from groff soelim(1), install groff
554 from package: pkg install groff, or via ports: textproc/groff.
557 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
558 defined in symlink(7); previously symlinks were silently ignored.
561 The const qualifier has been removed from iconv(3) to comply with
562 POSIX. The ports tree is aware of this from r384038 onwards.
565 Libraries specified by LIBADD in Makefiles must have a corresponding
566 DPADD_<lib> variable to ensure correct dependencies. This is now
567 enforced in src.libnames.mk.
570 From legacy ata(4) driver was removed support for SATA controllers
571 supported by more functional drivers ahci(4), siis(4) and mvs(4).
572 Kernel modules ataahci and ataadaptec were removed completely,
573 replaced by ahci and mvs modules respectively.
576 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
577 the 20141231 entry below for information about prerequisites and
578 upgrading, if you are not already using 3.5.0 or higher.
581 The 32-bit PowerPC kernel has been changed to a position-independent
582 executable. This can only be booted with a version of loader(8)
583 newer than January 31, 2015, so make sure to update both world and
584 kernel before rebooting.
587 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
588 but before r278950, the RNG was not seeded properly. Immediately
589 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
590 ssh keys or openssl keys) that were generated w/ a kernel from that
591 range. This does not affect programs that directly used /dev/random
592 or /dev/urandom. All userland uses of arc4random(3) are affected.
595 The autofs(4) ABI was changed in order to restore binary compatibility
596 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
600 The powerpc64 kernel has been changed to a position-independent
601 executable. This can only be booted with a new version of loader(8),
602 so make sure to update both world and kernel before rebooting.
605 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
606 only release, no new features have been added. Please see the 20141231
607 entry below for information about prerequisites and upgrading, if you
608 are not already using 3.5.0.
611 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
612 taken from the ELF Tool Chain project rather than GNU binutils. They
613 should be drop-in replacements, with the addition of arm64 support.
614 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
615 binutils tools, if necessary. See 20150805 for updated information.
618 The default Unbound configuration now enables remote control
619 using a local socket. Users who have already enabled the
620 local_unbound service should regenerate their configuration
621 by running "service local_unbound setup" as root.
624 The GNU texinfo and GNU info pages have been removed.
625 To be able to view GNU info pages please install texinfo from ports.
628 Clang, llvm and lldb have been upgraded to 3.5.0 release.
630 As of this release, a prerequisite for building clang, llvm and lldb is
631 a C++11 capable compiler and C++11 standard library. This means that to
632 be able to successfully build the cross-tools stage of buildworld, with
633 clang as the bootstrap compiler, your system compiler or cross compiler
634 should either be clang 3.3 or later, or gcc 4.8 or later, and your
635 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
638 On any standard FreeBSD 10.x or 11.x installation, where clang and
639 libc++ are on by default (that is, on x86 or arm), this should work out
642 On 9.x installations where clang is enabled by default, e.g. on x86 and
643 powerpc, libc++ will not be enabled by default, so libc++ should be
644 built (with clang) and installed first. If both clang and libc++ are
645 missing, build clang first, then use it to build libc++.
647 On 8.x and earlier installations, upgrade to 9.x first, and then follow
648 the instructions for 9.x above.
650 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
651 default, and do not build clang.
653 Many embedded systems are resource constrained, and will not be able to
654 build clang in a reasonable time, or in some cases at all. In those
655 cases, cross building bootable systems on amd64 is a workaround.
657 This new version of clang introduces a number of new warnings, of which
658 the following are most likely to appear:
662 This warns in two cases, for both C and C++:
663 * When the code is trying to take the absolute value of an unsigned
664 quantity, which is effectively a no-op, and almost never what was
665 intended. The code should be fixed, if at all possible. If you are
666 sure that the unsigned quantity can be safely cast to signed, without
667 loss of information or undefined behavior, you can add an explicit
668 cast, or disable the warning.
670 * When the code is trying to take an absolute value, but the called
671 abs() variant is for the wrong type, which can lead to truncation.
672 If you want to disable the warning instead of fixing the code, please
673 make sure that truncation will not occur, or it might lead to unwanted
676 -Wtautological-undefined-compare and
677 -Wundefined-bool-conversion
679 These warn when C++ code is trying to compare 'this' against NULL, while
680 'this' should never be NULL in well-defined C++ code. However, there is
681 some legacy (pre C++11) code out there, which actively abuses this
682 feature, which was less strictly defined in previous C++ versions.
684 Squid and openjdk do this, for example. The warning can be turned off
685 for C++98 and earlier, but compiling the code in C++11 mode might result
686 in unexpected behavior; for example, the parts of the program that are
687 unreachable could be optimized away.
690 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
691 kernel sources have been removed. The .h files remain, since some
692 utilities include them. This will need to be fixed later.
693 If "mount -t oldnfs ..." is attempted, it will fail.
694 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
695 the utilities will report errors.
698 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
699 directories to top level SUBDIR variable when their parent
700 directory is included in LOCAL_DIRS. Users with build systems with
701 such hierarchies and without SUBDIR entries in the parent
702 directory Makefiles should add them or add the directories to
706 faith(4) and faithd(8) have been removed from the base system. Faith
707 has been obsolete for a very long time.
710 vt(4), the new console driver, is enabled by default. It brings
711 support for Unicode and double-width characters, as well as
712 support for UEFI and integration with the KMS kernel video
715 You may need to update your console settings in /etc/rc.conf,
716 most probably the keymap. During boot, /etc/rc.d/syscons will
717 indicate what you need to do.
719 vt(4) still has issues and lacks some features compared to
720 syscons(4). See the wiki for up-to-date information:
721 https://wiki.freebsd.org/Newcons
723 If you want to keep using syscons(4), you can do so by adding
724 the following line to /boot/loader.conf:
728 pjdfstest has been integrated into kyua as an opt-in test suite.
729 Please see share/doc/pjdfstest/README for more details on how to
733 gperf has been removed from the base system for architectures
734 that use clang. Ports that require gperf will obtain it from the
738 pjdfstest has been moved from tools/regression/pjdfstest to
742 At svn r271982, The default linux compat kernel ABI has been adjusted
743 to 2.6.18 in support of the linux-c6 compat ports infrastructure
744 update. If you wish to continue using the linux-f10 compat ports,
745 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
746 encouraged to update their linux-compat packages to linux-c6 during
747 their next update cycle.
750 The ofwfb driver, used to provide a graphics console on PowerPC when
751 using vt(4), no longer allows mmap() of all physical memory. This
752 will prevent Xorg on PowerPC with some ATI graphics cards from
753 initializing properly unless x11-servers/xorg-server is updated to
757 The xdev targets have been converted to using TARGET and
758 TARGET_ARCH instead of XDEV and XDEV_ARCH.
761 The default unbound configuration has been modified to address
762 issues with reverse lookups on networks that use private
763 address ranges. If you use the local_unbound service, run
764 "service local_unbound setup" as root to regenerate your
765 configuration, then "service local_unbound reload" to load the
769 The GNU texinfo and GNU info pages are not built and installed
770 anymore, WITH_INFO knob has been added to allow to built and install
772 UPDATE: see 20150102 entry on texinfo's removal
775 The GNU readline library is now an INTERNALLIB - that is, it is
776 statically linked into consumers (GDB and variants) in the base
777 system, and the shared library is no longer installed. The
778 devel/readline port is available for third party software that
782 The Itanium architecture (ia64) has been removed from the list of
783 known architectures. This is the first step in the removal of the
787 Commit r268115 has added NFSv4.1 server support, merged from
788 projects/nfsv4.1-server. Since this includes changes to the
789 internal interfaces between the NFS related modules, a full
790 build of the kernel and modules will be necessary.
791 __FreeBSD_version has been bumped.
794 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
795 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
796 which differs from the behaviour controlled by this knob.)
799 Maximal length of the serial number in CTL was increased from 16 to
800 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
801 and ctld, need to be rebuilt to work with a new kernel.
804 The libatf-c and libatf-c++ major versions were downgraded to 0 and
805 1 respectively to match the upstream numbers. They were out of
806 sync because, when they were originally added to FreeBSD, the
807 upstream versions were not respected. These libraries are private
808 and not yet built by default, so renumbering them should be a
809 non-issue. However, unclean source trees will yield broken test
810 programs once the operator executes "make delete-old-libs" after a
813 Additionally, the atf-sh binary was made private by moving it into
814 /usr/libexec/. Already-built shell test programs will keep the
815 path to the old binary so they will break after "make delete-old"
818 If you are using WITH_TESTS=yes (not the default), wipe the object
819 tree and rebuild from scratch to prevent spurious test failures.
820 This is only needed once: the misnumbered libraries and misplaced
821 binaries have been added to OptionalObsoleteFiles.inc so they will
822 be removed during a clean upgrade.
825 Clang and llvm have been upgraded to 3.4.1 release.
828 We bogusly installed src.opts.mk in /usr/share/mk. This file should
829 be removed to avoid issues in the future (and has been added to
833 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
834 past, it affected all builds that used the bsd.*.mk files. The old
835 behavior was a bug, but people may have relied upon it. To get this
836 behavior back, you can .include /etc/src.conf from /etc/make.conf
837 (which is still global and isn't changed). This also changes the
838 behavior of incremental builds inside the tree of individual
839 directories. Set MAKESYSPATH to ".../share/mk" to do that.
840 Although this has survived make universe and some upgrade scenarios,
841 other upgrade scenarios may have broken. At least one form of
842 temporary breakage was fixed with MAKESYSPATH settings for buildworld
843 as well... In cases where MAKESYSPATH isn't working with this
844 setting, you'll need to set it to the full path to your tree.
846 One side effect of all this cleaning up is that bsd.compiler.mk
847 is no longer implicitly included by bsd.own.mk. If you wish to
848 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
852 The lindev device has been removed since /dev/full has been made a
853 standard device. __FreeBSD_version has been bumped.
856 The knob WITHOUT_VI was added to the base system, which controls
857 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
858 in order to reorder files share/termcap and didn't build ex(1) as a
859 build tool, so building/installing with WITH_VI is highly advised for
860 build hosts for older releases.
862 This issue has been fixed in stable/9 and stable/10 in r277022 and
863 r276991, respectively.
866 The YES_HESIOD knob has been removed. It has been obsolete for
867 a decade. Please move to using WITH_HESIOD instead or your builds
868 will silently lack HESIOD.
871 The uart(4) driver has been changed with respect to its handling
872 of the low-level console. Previously the uart(4) driver prevented
873 any process from changing the baudrate or the CLOCAL and HUPCL
874 control flags. By removing the restrictions, operators can make
875 changes to the serial console port without having to reboot.
876 However, when getty(8) is started on the serial device that is
877 associated with the low-level console, a misconfigured terminal
878 line in /etc/ttys will now have a real impact.
879 Before upgrading the kernel, make sure that /etc/ttys has the
880 serial console device configured as 3wire without baudrate to
881 preserve the previous behaviour. E.g:
882 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
885 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
886 to improve performance. To re-enable it, if needed, run rpcbind
887 with command line option -W.
890 Switched back to the GPL dtc compiler due to updates in the upstream
891 dts files not being supported by the BSDL dtc compiler. You will need
892 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
893 may result while building dtb files during a kernel build if you fail
894 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
897 Clang and llvm have been upgraded to 3.4 release.
900 The nve(4) driver has been removed. Please use the nfe(4) driver
901 for NVIDIA nForce MCP Ethernet adapters instead.
904 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
905 This could cause certain C++ applications using shared libraries built
906 against the previous version of libc++ to crash. The incompatibility
907 has now been fixed, but any C++ applications or shared libraries built
908 between r261283 and r261801 should be recompiled.
911 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
912 capability mode support. Please note that enabling the feature in
913 kernel is still highly recommended.
916 OpenSSH is now built with sandbox support, and will use sandbox as
917 the default privilege separation method. This requires Capsicum
918 capability mode support in kernel.
921 The libelf and libdwarf libraries have been updated to newer
922 versions from upstream. Shared library version numbers for
923 these two libraries were bumped. Any ports or binaries
924 requiring these two libraries should be recompiled.
925 __FreeBSD_version is bumped to 1100006.
928 If a Makefile in a tests/ directory was auto-generating a Kyuafile
929 instead of providing an explicit one, this would prevent such
930 Makefile from providing its own Kyuafile in the future during
931 NO_CLEAN builds. This has been fixed in the Makefiles but manual
932 intervention is needed to clean an objdir if you use NO_CLEAN:
933 # find /usr/obj -name Kyuafile | xargs rm -f
936 The behavior of gss_pseudo_random() for the krb5 mechanism
937 has changed, for applications requesting a longer random string
938 than produced by the underlying enctype's pseudo-random() function.
939 In particular, the random string produced from a session key of
940 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
941 be different at the 17th octet and later, after this change.
942 The counter used in the PRF+ construction is now encoded as a
943 big-endian integer in accordance with RFC 4402.
944 __FreeBSD_version is bumped to 1100004.
947 The WITHOUT_ATF build knob has been removed and its functionality
948 has been subsumed into the more generic WITHOUT_TESTS. If you were
949 using the former to disable the build of the ATF libraries, you
950 should change your settings to use the latter.
953 The default version of mtree is nmtree which is obtained from
954 NetBSD. The output is generally the same, but may vary
955 slightly. If you found you need identical output adding
956 "-F freebsd9" to the command line should do the trick. For the
957 time being, the old mtree is available as fmtree.
960 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
961 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
962 1.1.4_8 and verify bsdyml not linked in, before running "make
964 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
966 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
969 The stable/10 branch has been created in subversion from head
973 The rc.d/jail script has been updated to support jail(8)
974 configuration file. The "jail_<jname>_*" rc.conf(5) variables
975 for per-jail configuration are automatically converted to
976 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
977 This is transparently backward compatible. See below about some
978 incompatibilities and rc.conf(5) manual page for more details.
980 These variables are now deprecated in favor of jail(8) configuration
981 file. One can use "rc.d/jail config <jname>" command to generate
982 a jail(8) configuration file in /var/run/jail.<jname>.conf without
983 running the jail(8) utility. The default pathname of the
984 configuration file is /etc/jail.conf and can be specified by
985 using $jail_conf or $jail_<jname>_conf variables.
987 Please note that jail_devfs_ruleset accepts an integer at
988 this moment. Please consider to rewrite the ruleset name
992 BIND has been removed from the base system. If all you need
993 is a local resolver, simply enable and start the local_unbound
994 service instead. Otherwise, several versions of BIND are
995 available in the ports tree. The dns/bind99 port is one example.
997 With this change, nslookup(1) and dig(1) are no longer in the base
998 system. Users should instead use host(1) and drill(1) which are
999 in the base system. Alternatively, nslookup and dig can
1000 be obtained by installing the dns/bind-tools port.
1003 With the addition of unbound(8), a new unbound user is now
1004 required during installworld. "mergemaster -p" can be used to
1005 add the user prior to installworld, as documented in the handbook.
1008 OpenSSH is now built with DNSSEC support, and will by default
1009 silently trust signed SSHFP records. This can be controlled with
1010 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1011 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1014 The GNU Compiler Collection and C++ standard library (libstdc++)
1015 are no longer built by default on platforms where clang is the system
1016 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1017 options in src.conf.
1020 The PROCDESC kernel option is now part of the GENERIC kernel
1021 configuration and is required for the rwhod(8) to work.
1022 If you are using custom kernel configuration, you should include
1026 The API and ABI related to the Capsicum framework was modified
1027 in backward incompatible way. The userland libraries and programs
1028 have to be recompiled to work with the new kernel. This includes the
1029 following libraries and programs, but the whole buildworld is
1030 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1031 kdump, procstat, rwho, rwhod, uniq.
1034 AES-NI intrinsic support has been added to gcc. The AES-NI module
1035 has been updated to use this support. A new gcc is required to build
1036 the aesni module on both i386 and amd64.
1039 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1040 Thus "device padlock_rng" and "device rdrand_rng" should be
1041 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1044 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1045 enables just the iconv* functionality and is now on by default.
1046 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1047 compatibility. Set WITHOUT_ICONV to build the old way.
1048 If you have been using WITH_ICONV before, you will very likely
1049 need to turn on WITH_LIBICONV_COMPAT.
1052 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1053 Illumos origin, including ZFS. If you have INVARIANTS in your
1054 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1056 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1057 locks if WITNESS option was set. Because that generated a lot of
1058 witness(9) reports and all of them were believed to be false
1059 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1060 can be used to achieve the previous behavior.
1063 Timer values in IPv6 data structures now use time_uptime instead
1064 of time_second. Although this is not a user-visible functional
1065 change, userland utilities which directly use them---ndp(8),
1066 rtadvd(8), and rtsold(8) in the base system---need to be updated
1067 to r253970 or later.
1070 find -delete can now delete the pathnames given as arguments,
1071 instead of only files found below them or if the pathname did
1072 not contain any slashes. Formerly, the following error message
1075 find: -delete: <path>: relative path potentially not safe
1077 Deleting the pathnames given as arguments can be prevented
1078 without error messages using -mindepth 1 or by changing
1079 directory and passing "." as argument to find. This works in the
1080 old as well as the new version of find.
1083 Behavior of devfs rules path matching has been changed.
1084 Pattern is now always matched against fully qualified devfs
1085 path and slash characters must be explicitly matched by
1086 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1087 subdirectories must be reviewed.
1090 The default ARM ABI has changed to the ARM EABI. The old ABI is
1091 incompatible with the ARM EABI and all programs and modules will
1092 need to be rebuilt to work with a new kernel.
1094 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1096 NOTE: Support for the old ABI will be removed in the future and
1097 users are advised to upgrade.
1100 pkg_install has been disconnected from the build if you really need it
1101 you should add WITH_PKGTOOLS in your src.conf(5).
1104 Most of network statistics structures were changed to be able
1105 keep 64-bits counters. Thus all tools, that work with networking
1106 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1109 Fix a bug that allowed a tracing process (e.g. gdb) to write
1110 to a memory-mapped file in the traced process's address space
1111 even if neither the traced process nor the tracing process had
1112 write access to that file.
1115 CVS has been removed from the base system. An exact copy
1116 of the code is available from the devel/cvs port.
1119 Some people report the following error after the switch to bmake:
1121 make: illegal option -- J
1122 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1124 *** [buildworld] Error code 2
1126 this likely due to an old instance of make in
1127 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1128 which src/Makefile will use that blindly, if it exists, so if
1129 you see the above error:
1131 rm -rf `make -V MAKEPATH`
1136 Use bmake by default.
1137 Whereas before one could choose to build with bmake via
1138 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1139 make. The goal is to remove these knobs for 10-RELEASE.
1141 It is worth noting that bmake (like gmake) treats the command
1142 line as the unit of failure, rather than statements within the
1143 command line. Thus '(cd some/where && dosomething)' is safer
1144 than 'cd some/where; dosomething'. The '()' allows consistent
1145 behavior in parallel build.
1148 Fix a bug that allows NFS clients to issue READDIR on files.
1151 The WITHOUT_IDEA option has been removed because
1152 the IDEA patent expired.
1155 The sysctl which controls TRIM support under ZFS has been renamed
1156 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1160 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1161 rather than creating it's own in the temporary directory in
1162 order allow access to bootstrapped versions of tools such as
1163 install and mtree. When upgrading from version of FreeBSD where
1164 the install command does not support -l, you will need to
1165 install a new mergemaster command if mergemaster -p is required.
1166 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1170 Legacy ATA stack, disabled and replaced by new CAM-based one since
1171 FreeBSD 9.0, completely removed from the sources. Kernel modules
1172 atadisk and atapi*, user-level tools atacontrol and burncd are
1173 removed. Kernel option `options ATA_CAM` is now permanently enabled
1177 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1178 and socketpair(2). Software, in particular Kerberos, may
1179 automatically detect and use these during building. The resulting
1180 binaries will not work on older kernels.
1183 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1184 information, see the respective 20130304 entry).
1187 Recent commits to callout(9) changed the size of struct callout,
1188 so the KBI is probably heavily disturbed. Also, some functions
1189 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1190 by macros. Every kernel module using it won't load, so rebuild
1193 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1194 but does not initialize by default (because of the new CTL_DISABLE
1195 option) to save memory. To re-enable it, remove the CTL_DISABLE
1196 option from the kernel config file or set kern.cam.ctl.disable=0
1197 in /boot/loader.conf.
1200 The ctl device has been disabled in GENERIC for i386 and amd64.
1201 This was done due to the extra memory being allocated at system
1202 initialisation time by the ctl driver which was only used if
1203 a CAM target device was created. This makes a FreeBSD system
1204 unusable on 128MB or less of RAM.
1207 A new compression method (lz4) has been merged to -HEAD. Please
1208 refer to zpool-features(7) for more information.
1210 Please refer to the "ZFS notes" section of this file for information
1211 on upgrading boot ZFS pools.
1214 A BSD-licensed patch(1) variant has been added and is installed
1215 as bsdpatch, being the GNU version the default patch.
1216 To inverse the logic and use the BSD-licensed one as default,
1217 while having the GNU version installed as gnupatch, rebuild
1218 and install world with the WITH_BSD_PATCH knob set.
1221 Due to the use of the new -l option to install(1) during build
1222 and install, you must take care not to directly set the INSTALL
1223 make variable in your /etc/make.conf, /etc/src.conf, or on the
1224 command line. If you wish to use the -C flag for all installs
1225 you may be able to add INSTALL+=-C to /etc/make.conf or
1229 The install(1) option -M has changed meaning and now takes an
1230 argument that is a file or path to append logs to. In the
1231 unlikely event that -M was the last option on the command line
1232 and the command line contained at least two files and a target
1233 directory the first file will have logs appended to it. The -M
1234 option served little practical purpose in the last decade so its
1235 use is expected to be extremely rare.
1238 After switching to Clang as the default compiler some users of ZFS
1239 on i386 systems started to experience stack overflow kernel panics.
1240 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1243 GEOM_LABEL now mangles label names read from file system metadata.
1244 Mangling affect labels containing spaces, non-printable characters,
1245 '%' or '"'. Device names in /etc/fstab and other places may need to
1249 By default, only the 10 most recent kernel dumps will be saved. To
1250 restore the previous behaviour (no limit on the number of kernel dumps
1251 stored in the dump directory) add the following line to /etc/rc.conf:
1256 With the addition of auditdistd(8), a new auditdistd user is now
1257 required during installworld. "mergemaster -p" can be used to
1258 add the user prior to installworld, as documented in the handbook.
1261 The sin6_scope_id member variable in struct sockaddr_in6 is now
1262 filled by the kernel before passing the structure to the userland via
1263 sysctl or routing socket. This means the KAME-specific embedded scope
1264 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1265 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1266 __FreeBSD_version is bumped to 1000025.
1269 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1270 This means that the world and kernel will be compiled with clang
1271 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1272 and /usr/bin/cpp. To disable this behavior and revert to building
1273 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1274 of current may need to bootstrap WITHOUT_CLANG first if the clang
1275 build fails (its compatibility window doesn't extend to the 9 stable
1279 The IPFIREWALL_FORWARD kernel option has been removed. Its
1280 functionality now turned on by default.
1283 The ZERO_COPY_SOCKET kernel option has been removed and
1284 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1285 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1286 mechanism which is not safe and may result in kernel crashes.
1287 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1288 driver supports disposeable external page sized mbuf storage.
1289 Proper replacements for both zero-copy mechanisms are under
1290 consideration and will eventually lead to complete removal
1291 of the two kernel options.
1294 The IPv4 network stack has been converted to network byte
1295 order. The following modules need to be recompiled together
1296 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1297 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1300 Support for non-MPSAFE filesystems was removed from VFS. The
1301 VFS_VERSION was bumped, all filesystem modules shall be
1305 All the non-MPSAFE filesystems have been disconnected from
1306 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1307 portalfs, smbfs, xfs.
1310 The interface cloning API and ABI has changed. The following
1311 modules need to be recompiled together with kernel:
1312 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1313 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1314 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1317 The sdhci driver was split in two parts: sdhci (generic SD Host
1318 Controller logic) and sdhci_pci (actual hardware driver).
1319 No kernel config modifications are required, but if you
1320 load sdhc as a module you must switch to sdhci_pci instead.
1323 Import the FUSE kernel and userland support into base system.
1326 The GNU sort(1) program has been removed since the BSD-licensed
1327 sort(1) has been the default for quite some time and no serious
1328 problems have been reported. The corresponding WITH_GNU_SORT
1332 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1333 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1337 The net80211(4) ABI has been changed to allow for improved driver
1338 PS-POLL and power-save support. All wireless drivers need to be
1339 recompiled to work with the new kernel.
1342 The random(4) support for the VIA hardware random number
1343 generator (`PADLOCK') is no longer enabled unconditionally.
1344 Add the padlock_rng device in the custom kernel config if
1345 needed. The GENERIC kernels on i386 and amd64 do include the
1346 device, so the change only affects the custom kernel
1350 The pf(4) packet filter ABI has been changed. pfctl(8) and
1351 snmp_pf module need to be recompiled to work with new kernel.
1354 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1355 to -HEAD. Pools that have empty_bpobj in active state can not be
1356 imported read-write with ZFS implementations that do not support
1357 this feature. For more information read the zpool-features(5)
1361 The sparc64 ZFS loader has been changed to no longer try to auto-
1362 detect ZFS providers based on diskN aliases but now requires these
1363 to be explicitly listed in the OFW boot-device environment variable.
1366 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1367 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1368 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1371 The following sysctls and tunables have been renamed for consistency
1372 with other variables:
1373 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1374 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1377 The sort utility has been replaced with BSD sort. For now, GNU sort
1378 is also available as "gnusort" or the default can be set back to
1379 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1380 installed as "bsdsort".
1383 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1384 Starting with this version the old system of ZFS pool versioning
1385 is superseded by "feature flags". This concept enables forward
1386 compatibility against certain future changes in functionality of ZFS
1387 pools. The first read-only compatible "feature flag" for ZFS pools
1388 is named "com.delphix:async_destroy". For more information
1389 read the new zpool-features(5) manual page.
1390 Please refer to the "ZFS notes" section of this file for information
1391 on upgrading boot ZFS pools.
1394 The malloc(3) implementation embedded in libc now uses sources imported
1395 as contrib/jemalloc. The most disruptive API change is to
1396 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1397 delete it prior to installworld, and optionally re-create it using the
1398 new format after rebooting. See malloc.conf(5) for details
1399 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1403 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1404 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1405 now spelled mips. This is to aid compatibility with third-party
1406 software that expects this naming scheme in uname(3). Little-endian
1407 settings are unchanged. If you are updating a big-endian mips64 machine
1408 from before this change, you may need to set MACHINE_ARCH=mips64 in
1409 your environment before the new build system will recognize your machine.
1412 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1416 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1417 nullfs(5) did not pass through all behaviours to the underlying layer,
1418 as a result if we bound to a socket on the lower layer we could connect
1419 only to the lower path; if we bound to the upper layer we could connect
1420 only to the upper path. The new behavior is one can connect to both the
1421 lower and the upper paths regardless what layer path one binds to.
1424 The getifaddrs upgrade path broken with 20111215 has been restored.
1425 If you have upgraded in between 20111215 and 20120209 you need to
1426 recompile libc again with your kernel. You still need to recompile
1427 world to be able to configure CARP but this restriction already
1428 comes from 20111215.
1431 The set_rcvar() function has been removed from /etc/rc.subr. All
1432 base and ports rc.d scripts have been updated, so if you have a
1433 port installed with a script in /usr/local/etc/rc.d you can either
1434 hand-edit the rcvar= line, or reinstall the port.
1436 An easy way to handle the mass-update of /etc/rc.d:
1437 rm /etc/rc.d/* && mergemaster -i
1440 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1441 on the current CPU and prevents other threads from running.
1442 This behavior can be reverted using the kern.stop_scheduler_on_panic
1444 The new behavior can be incompatible with kern.sync_on_panic.
1447 The carp(4) facility has been changed significantly. Configuration
1448 of the CARP protocol via ifconfig(8) has changed, as well as format
1449 of CARP events submitted to devd(8) has changed. See manual pages
1450 for more information. The arpbalance feature of carp(4) is currently
1451 not supported anymore.
1453 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1454 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1455 need to be recompiled.
1458 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1462 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1463 explicitely support non-MPSAFE filesystems.
1464 It is on by default for all supported platform at this present
1468 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1469 i386 and pc98 GENERIC kernel configuration files.
1472 sysinstall has been removed
1475 The stable/9 branch created in subversion. This corresponds to the
1476 RELENG_9 branch in CVS.
1482 Avoid using make -j when upgrading. While generally safe, there are
1483 sometimes problems using -j to upgrade. If your upgrade fails with
1484 -j, please try again without -j. From time to time in the past there
1485 have been problems using -j with buildworld and/or installworld. This
1486 is especially true when upgrading between "distant" versions (eg one
1487 that cross a major release boundary or several minor releases, or when
1488 several months have passed on the -current branch).
1490 Sometimes, obscure build problems are the result of environment
1491 poisoning. This can happen because the make utility reads its
1492 environment when searching for values for global variables. To run
1493 your build attempts in an "environmental clean room", prefix all make
1494 commands with 'env -i '. See the env(1) manual page for more details.
1496 When upgrading from one major version to another it is generally best to
1497 upgrade to the latest code in the currently installed branch first, then
1498 do an upgrade to the new branch. This is the best-tested upgrade path,
1499 and has the highest probability of being successful. Please try this
1500 approach if you encounter problems with a major version upgrade. Since
1501 the stable 4.x branch point, one has generally been able to upgade from
1502 anywhere in the most recent stable branch to head / current (or even the
1503 last couple of stable branches). See the top of this file when there's
1506 When upgrading a live system, having a root shell around before
1507 installing anything can help undo problems. Not having a root shell
1508 around can lead to problems if pam has changed too much from your
1509 starting point to allow continued authentication after the upgrade.
1511 This file should be read as a log of events. When a later event changes
1512 information of a prior event, the prior event should not be deleted.
1513 Instead, a pointer to the entry with the new information should be
1514 placed in the old entry. Readers of this file should also sanity check
1515 older entries before relying on them blindly. Authors of new entries
1516 should write them with this in mind.
1520 When upgrading the boot ZFS pool to a new version, always follow
1523 1.) recompile and reinstall the ZFS boot loader and boot block
1524 (this is part of "make buildworld" and "make installworld")
1526 2.) update the ZFS boot block on your boot drive
1528 The following example updates the ZFS boot block on the first
1529 partition (freebsd-boot) of a GPT partitioned drive ada0:
1530 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1532 Non-boot pools do not need these updates.
1536 If you are updating from a prior version of FreeBSD (even one just
1537 a few days old), you should follow this procedure. It is the most
1538 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1540 make kernel-toolchain
1541 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1542 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1544 To test a kernel once
1545 ---------------------
1546 If you just want to boot a kernel once (because you are not sure
1547 if it works, or if you want to boot a known bad kernel to provide
1548 debugging information) run
1549 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1550 nextboot -k testkernel
1552 To just build a kernel when you know that it won't mess you up
1553 --------------------------------------------------------------
1554 This assumes you are already running a CURRENT system. Replace
1555 ${arch} with the architecture of your machine (e.g. "i386",
1556 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1558 cd src/sys/${arch}/conf
1559 config KERNEL_NAME_HERE
1560 cd ../compile/KERNEL_NAME_HERE
1565 If this fails, go to the "To build a kernel" section.
1567 To rebuild everything and install it on the current system.
1568 -----------------------------------------------------------
1569 # Note: sometimes if you are running current you gotta do more than
1570 # is listed here if you are upgrading from a really old current.
1572 <make sure you have good level 0 dumps>
1574 make kernel KERNCONF=YOUR_KERNEL_HERE
1576 <reboot in single user> [3]
1583 To cross-install current onto a separate partition
1584 --------------------------------------------------
1585 # In this approach we use a separate partition to hold
1586 # current's root, 'usr', and 'var' directories. A partition
1587 # holding "/", "/usr" and "/var" should be about 2GB in
1590 <make sure you have good level 0 dumps>
1593 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1594 <maybe newfs current's root partition>
1595 <mount current's root partition on directory ${CURRENT_ROOT}>
1596 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1597 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1598 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1599 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1600 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1601 <reboot into current>
1602 <do a "native" rebuild/install as described in the previous section>
1603 <maybe install compatibility libraries from ports/misc/compat*>
1607 To upgrade in-place from stable to current
1608 ----------------------------------------------
1609 <make sure you have good level 0 dumps>
1611 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1613 <reboot in single user> [3]
1620 Make sure that you've read the UPDATING file to understand the
1621 tweaks to various things you need. At this point in the life
1622 cycle of current, things change often and you are on your own
1623 to cope. The defaults can also change, so please read ALL of
1624 the UPDATING entries.
1626 Also, if you are tracking -current, you must be subscribed to
1627 freebsd-current@freebsd.org. Make sure that before you update
1628 your sources that you have read and understood all the recent
1629 messages there. If in doubt, please track -stable which has
1630 much fewer pitfalls.
1632 [1] If you have third party modules, such as vmware, you
1633 should disable them at this point so they don't crash your
1636 [3] From the bootblocks, boot -s, and then do
1641 adjkerntz -i # if CMOS is wall time
1642 Also, when doing a major release upgrade, it is required that
1643 you boot into single user mode to do the installworld.
1645 [4] Note: This step is non-optional. Failure to do this step
1646 can result in a significant reduction in the functionality of the
1647 system. Attempting to do it by hand is not recommended and those
1648 that pursue this avenue should read this file carefully, as well
1649 as the archives of freebsd-current and freebsd-hackers mailing lists
1650 for potential gotchas. The -U option is also useful to consider.
1651 See mergemaster(8) for more information.
1653 [5] Usually this step is a noop. However, from time to time
1654 you may need to do this if you get unknown user in the following
1655 step. It never hurts to do it all the time. You may need to
1656 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1657 install) after the buildworld before this step if you last updated
1658 from current before 20130425 or from -stable before 20130430.
1660 [6] This only deletes old files and directories. Old libraries
1661 can be deleted by "make delete-old-libs", but you have to make
1662 sure that no program is using those libraries anymore.
1664 [8] In order to have a kernel that can run the 4.x binaries needed to
1665 do an installworld, you must include the COMPAT_FREEBSD4 option in
1666 your kernel. Failure to do so may leave you with a system that is
1667 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1668 required to run the 5.x binaries on more recent kernels. And so on
1669 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1671 Make sure that you merge any new devices from GENERIC since the
1672 last time you updated your kernel config file.
1674 [9] When checking out sources, you must include the -P flag to have
1675 cvs prune empty directories.
1677 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1678 "?=" instead of the "=" assignment operator, so that buildworld can
1679 override the CPUTYPE if it needs to.
1681 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1682 not on the command line, or in /etc/make.conf. buildworld will
1683 warn if it is improperly defined.
1686 This file contains a list, in reverse chronological order, of major
1687 breakages in tracking -current. It is not guaranteed to be a complete
1688 list of such breakages, and only contains entries since September 23, 2011.
1689 If you need to see UPDATING entries from before that date, you will need
1690 to fetch an UPDATING file from an older FreeBSD release.
1692 Copyright information:
1694 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1696 Redistribution, publication, translation and use, with or without
1697 modification, in full or in part, in any form or format of this
1698 document are permitted without further permission from the author.
1700 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1701 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1702 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1703 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1704 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1705 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1706 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1707 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1708 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1709 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1710 POSSIBILITY OF SUCH DAMAGE.
1712 Contact Warner Losh if you have any questions about your use of