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 arm64 builds now use the base system LLD 4.0.0 linker by default,
56 instead of requiring that the aarch64-binutils port or package be
57 installed. To continue using aarch64-binutils, set
58 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
61 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
62 use any explicitly assigned loopback address available in the jail
63 instead of using the first assigned address of the jail.
66 The ctl.ko module no longer implements the iSCSI target frontend:
67 cfiscsi.ko does instead.
69 If building cfiscsi.ko as a kernel module, the module can be loaded
70 via one of the following methods:
71 - `cfiscsi_load="YES"` in loader.conf(5).
72 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
73 - ctladm(8)/ctld(8), when compiled with iSCSI support
74 (`WITH_ISCSI=yes` in src.conf(5))
76 Please see cfiscsi(4) for more details.
79 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
80 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
81 same source (previously, the dependency of mmcsd.ko on mmc.ko was
82 missing, but mmcsd.ko now will refuse to load if it is incompatible
86 The syntax of ipfw(8) named states was changed to avoid ambiguity.
87 If you have used named states in the firewall rules, you need to modify
88 them after installworld and before rebooting. Now named states must
89 be prefixed with colon.
92 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
93 removed as the userland we provide cannot use them. The KMS version
94 (sys/dev/drm2) support the same hardware.
97 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
98 Please see the 20141231 entry below for information about prerequisites
99 and upgrading, if you are not already using clang 3.5.0 or higher.
102 The code that provides support for ZFS .zfs/ directory functionality
103 has been reimplemented. It's not possible now to create a snapshot
104 by mkdir under .zfs/snapshot/. That should be the only user visible
108 EISA bus support has been removed. The WITH_EISA option is no longer
112 MCA bus support has been removed.
115 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
116 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
119 The EM_MULTIQUEUE kernel configuration option is deprecated now that
120 the em(4) driver conforms to iflib specifications.
123 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
124 IFLIB. If you have a custom kernel configuration that excludes em(4)
125 but you use igb(4), you need to re-add em(4) to your custom configuration.
128 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
129 Please see the 20141231 entry below for information about prerequisites
130 and upgrading, if you are not already using clang 3.5.0 or higher.
133 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
134 Please see the 20141231 entry below for information about prerequisites
135 and upgrading, if you are not already using clang 3.5.0 or higher.
138 The layout of the pmap structure has changed for powerpc to put the pmap
139 statistics at the front for all CPU variations. libkvm(3) and all tools
140 that link against it need to be recompiled.
143 isl(4) and cyapa(4) drivers now require a new driver,
144 chromebook_platform(4), to work properly on Chromebook-class hardware.
145 On other types of hardware the drivers may need to be configured using
146 device hints. Please see the corresponding manual pages for details.
149 The urtwn(4) driver was merged into rtwn(4) and now consists of
150 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
152 Also, firmware for RTL8188CE was renamed due to possible name
153 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
156 GNU rcs has been removed from base. It is available as packages:
157 - rcs: Latest GPLv3 GNU rcs version.
158 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
162 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
163 modules now requires that the kernel configuration contain the
164 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
167 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
168 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
171 Relocatable object files with the extension of .So have been renamed
172 to use an extension of .pico instead. The purpose of this change is
173 to avoid a name clash with shared libraries on case-insensitive file
174 systems. On those file systems, foo.So is the same file as foo.so.
177 GNU rcs has been turned off by default. It can (temporarily) be built
178 again by adding WITH_RCS knob in src.conf.
179 Otherwise, GNU rcs is available from packages:
180 - rcs: Latest GPLv3 GNU rcs version.
181 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
184 The backup_uses_rcs functionality has been removed from rc.subr.
187 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
188 two separate components, QUEUE_MACRO_DEBUG_TRACE and
189 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
190 QUEUE_MACRO_DEBUG behavior.
193 r304787 changed some ioctl interfaces between the iSCSI userspace
194 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
195 rebuilt to work with new kernels. __FreeBSD_version has been bumped
199 The UDP receive code has been updated to only treat incoming UDP
200 packets that were addressed to an L2 broadcast address as L3
201 broadcast packets. It is not expected that this will affect any
202 standards-conforming UDP application. The new behaviour can be
203 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
207 Remove the openbsd_poll system call.
208 __FreeBSD_version has been bumped because of this.
211 The libc stub for the pipe(2) system call has been replaced with
212 a wrapper that calls the pipe2(2) system call and the pipe(2)
213 system call is now only implemented by the kernels that include
214 "options COMPAT_FREEBSD10" in their config file (this is the
215 default). Users should ensure that this option is enabled in
216 their kernel or upgrade userspace to r302092 before upgrading their
220 CAM will now strip leading spaces from SCSI disks' serial numbers.
221 This will affect users who create UFS filesystems on SCSI disks using
222 those disk's diskid device nodes. For example, if /etc/fstab
223 previously contained a line like
224 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
225 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
226 transforms like gmirror may also be affected. ZFS users should
230 The bitstring(3) API has been updated with new functionality and
231 improved performance. But it is binary-incompatible with the old API.
232 Objects built with the new headers may not be linked against objects
233 built with the old headers.
236 The brk and sbrk functions have been removed from libc on arm64.
237 Binutils from ports has been updated to not link to these
238 functions and should be updated to the latest version before
239 installing a new libc.
242 The armv6 port now defaults to hard float ABI. Limited support
243 for running both hardfloat and soft float on the same system
244 is available using the libraries installed with -DWITH_LIBSOFT.
245 This has only been tested as an upgrade path for installworld
246 and packages may fail or need manual intervention to run. New
247 packages will be needed.
249 To update an existing self-hosted armv6hf system, you must add
250 TARGET_ARCH=armv6 on the make command line for both the build
251 and the install steps.
254 Kernel modules compiled outside of a kernel build now default to
255 installing to /boot/modules instead of /boot/kernel. Many kernel
256 modules built this way (such as those in ports) already overrode
257 KMODDIR explicitly to install into /boot/modules. However,
258 manually building and installing a module from /sys/modules will
259 now install to /boot/modules instead of /boot/kernel.
262 The CAM I/O scheduler has been committed to the kernel. There should be
263 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
264 list of known rogues that claim support for this but actually corrupt
265 data is believed to be complete, be on the lookout for data
266 corruption. The known rogue list is believed to be complete:
268 o Crucial MX100, M550 drives with MU01 firmware.
269 o Micron M510 and M550 drives with MU01 firmware.
270 o Micron M500 prior to MU07 firmware
271 o Samsung 830, 840, and 850 all firmwares
272 o FCCT M500 all firmwares
274 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
275 with working NCQ TRIM. For Micron branded drives, see your sales rep for
276 updated firmware. Black listed drives will work correctly because these
277 drives work correctly so long as no NCQ TRIMs are sent to them. Given
278 this list is the same as found in Linux, it's believed there are no
279 other rogues in the market place. All other models from the above
282 To be safe, if you are at all concerned, you can quirk each of your
283 drives to prevent NCQ from being sent by setting:
284 kern.cam.ada.X.quirks="0x2"
285 in loader.conf. If the drive requires the 4k sector quirk, set the
289 The FAST_DEPEND build option has been removed and its functionality is
290 now the one true way. The old mkdep(1) style of 'make depend' has
291 been removed. See 20160311 for further details.
294 Resource range types have grown from unsigned long to uintmax_t. All
295 drivers, and anything using libdevinfo, need to be recompiled.
298 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
299 builds. It no longer runs mkdep(1) during 'make depend', and the
300 'make depend' stage can safely be skipped now as it is auto ran
301 when building 'make all' and will generate all SRCS and DPSRCS before
302 building anything else. Dependencies are gathered at compile time with
303 -MF flags kept in separate .depend files per object file. Users should
304 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
308 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
309 kernel modules. Therefore, if you load any kernel modules at boot time,
310 please install the boot loaders after you install the kernel, but before
314 make kernel KERNCONF=YOUR_KERNEL_HERE
315 make -C sys/boot install
316 <reboot in single user>
318 Then follow the usual steps, described in the General Notes section,
322 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
323 see the 20141231 entry below for information about prerequisites and
324 upgrading, if you are not already using clang 3.5.0 or higher.
327 The AIO subsystem is now a standard part of the kernel. The
328 VFS_AIO kernel option and aio.ko kernel module have been removed.
329 Due to stability concerns, asynchronous I/O requests are only
330 permitted on sockets and raw disks by default. To enable
331 asynchronous I/O requests on all file types, set the
332 vfs.aio.enable_unsafe sysctl to a non-zero value.
335 The ELF object manipulation tool objcopy is now provided by the
336 ELF Tool Chain project rather than by GNU binutils. It should be a
337 drop-in replacement, with the addition of arm64 support. The
338 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
339 to obtain the GNU version if necessary.
342 Building ZFS pools on top of zvols is prohibited by default. That
343 feature has never worked safely; it's always been prone to deadlocks.
344 Using a zvol as the backing store for a VM guest's virtual disk will
345 still work, even if the guest is using ZFS. Legacy behavior can be
346 restored by setting vfs.zfs.vol.recursive=1.
349 The NONE and HPN patches has been removed from OpenSSH. They are
350 still available in the security/openssh-portable port.
353 With the addition of ypldap(8), a new _ypldap user is now required
354 during installworld. "mergemaster -p" can be used to add the user
355 prior to installworld, as documented in the handbook.
358 The tftp loader (pxeboot) now uses the option root-path directive. As a
359 consequence it no longer looks for a pxeboot.4th file on the tftp
360 server. Instead it uses the regular /boot infrastructure as with the
364 The code to start recording plug and play data into the modules has
365 been committed. While the old tools will properly build a new kernel,
366 a number of warnings about "unknown metadata record 4" will be produced
367 for an older kldxref. To avoid such warnings, make sure to rebuild
368 the kernel toolchain (or world). Make sure that you have r292078 or
369 later when trying to build 292077 or later before rebuilding.
372 Debug data files are now built by default with 'make buildworld' and
373 installed with 'make installworld'. This facilitates debugging but
374 requires more disk space both during the build and for the installed
375 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
379 r291527 changed the internal interface between the nfsd.ko and
380 nfscommon.ko modules. As such, they must both be upgraded to-gether.
381 __FreeBSD_version has been bumped because of this.
384 Add support for unicode collation strings leads to a change of
385 order of files listed by ls(1) for example. To get back to the old
386 behaviour, set LC_COLLATE environment variable to "C".
388 Databases administrators will need to reindex their databases given
389 collation results will be different.
391 Due to a bug in install(1) it is recommended to remove the ancient
392 locales before running make installworld.
394 rm -rf /usr/share/locale/*
397 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
398 libcrypto.so.7 or libssl.so.7 must be recompiled.
401 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
402 Kernel modules isp_2400_multi and isp_2500_multi were removed and
403 should be replaced with isp_2400 and isp_2500 modules respectively.
406 The build previously allowed using 'make -n' to not recurse into
407 sub-directories while showing what commands would be executed, and
408 'make -n -n' to recursively show commands. Now 'make -n' will recurse
409 and 'make -N' will not.
412 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
413 and etcupdate will now use this file. A custom sendmail.cf is now
414 updated via this mechanism rather than via installworld. If you had
415 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
416 want to remove the exclusion or change it to "always install".
417 /etc/mail/sendmail.cf is now managed the same way regardless of
418 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
419 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
422 Compatibility shims for legacy ATA device names have been removed.
423 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
424 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
425 environment variables, /dev/ad* and /dev/ar* symbolic links.
428 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
429 Please see the 20141231 entry below for information about prerequisites
430 and upgrading, if you are not already using clang 3.5.0 or higher.
433 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
434 and renamed from .symbols to .debug. This reduces the size requirements
435 on the boot partition or file system and provides consistency with
436 userland debug files.
438 When using the supported kernel installation method the
439 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
440 as is done with /boot/kernel.
442 Developers wishing to maintain the historical behavior of installing
443 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
446 The wireless drivers had undergone changes that remove the 'parent
447 interface' from the ifconfig -l output. The rc.d network scripts
448 used to check presence of a parent interface in the list, so old
449 scripts would fail to start wireless networking. Thus, etcupdate(3)
450 or mergemaster(8) run is required after kernel update, to update your
451 rc.d scripts in /etc.
454 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
455 These configurations are now automatically interpreted as
456 'scrub fragment reassemble'.
459 Kernel-loadable modules for the random(4) device are back. To use
460 them, the kernel must have
463 options RANDOM_LOADABLE
465 kldload(8) can then be used to load random_fortuna.ko
466 or random_yarrow.ko. Please note that due to the indirect
467 function calls that the loadable modules need to provide,
468 the build-in variants will be slightly more efficient.
470 The random(4) kernel option RANDOM_DUMMY has been retired due to
471 unpopularity. It was not all that useful anyway.
474 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
475 Control over building the ELF Tool Chain tools is now provided by
476 the WITHOUT_TOOLCHAIN knob.
479 The polarity of Pulse Per Second (PPS) capture events with the
480 uart(4) driver has been corrected. Prior to this change the PPS
481 "assert" event corresponded to the trailing edge of a positive PPS
482 pulse and the "clear" event was the leading edge of the next pulse.
484 As the width of a PPS pulse in a typical GPS receiver is on the
485 order of 1 millisecond, most users will not notice any significant
486 difference with this change.
488 Anyone who has compensated for the historical polarity reversal by
489 configuring a negative offset equal to the pulse width will need to
490 remove that workaround.
493 The default group assigned to /dev/dri entries has been changed
494 from 'wheel' to 'video' with the id of '44'. If you want to have
495 access to the dri devices please add yourself to the video group
498 # pw groupmod video -m $USER
501 The menu.rc and loader.rc files will now be replaced during
502 upgrades. Please migrate local changes to menu.rc.local and
503 loader.rc.local instead.
506 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
507 strings and strip have been removed. The src.conf(5) knob
508 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
511 As ZFS requires more kernel stack pages than is the default on some
512 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
513 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
515 Please consider using 'options KSTACK_PAGES=X' where X is greater
516 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
519 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
520 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
521 default, i.e., they will not contain "::". For example, instead
522 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
523 to have a more specific match, such as different map entries for
524 IPv6:0:0 vs IPv6:0. This change requires that configuration
525 data (including maps, files, classes, custom ruleset, etc.) must
526 use the same format, so make certain such configuration data is
527 upgrading. As a very simple check search for patterns like
528 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
529 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
530 the cf option UseCompressedIPv6Addresses.
533 The default kernel entropy-processing algorithm is now
534 Fortuna, replacing Yarrow.
536 Assuming you have 'device random' in your kernel config
537 file, the configurations allow a kernel option to override
538 this default. You may choose *ONE* of:
540 options RANDOM_YARROW # Legacy /dev/random algorithm.
541 options RANDOM_DUMMY # Blocking-only driver.
543 If you have neither, you get Fortuna. For most people,
544 read no further, Fortuna will give a /dev/random that works
545 like it always used to, and the difference will be irrelevant.
547 If you remove 'device random', you get *NO* kernel-processed
548 entropy at all. This may be acceptable to folks building
549 embedded systems, but has complications. Carry on reading,
550 and it is assumed you know what you need.
552 *PLEASE* read random(4) and random(9) if you are in the
553 habit of tweaking kernel configs, and/or if you are a member
554 of the embedded community, wanting specific and not-usual
555 behaviour from your security subsystems.
557 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
558 random', you will NOT have a functioning /dev/random, and
559 many cryptographic features will not work, including SSH.
560 You may also find strange behaviour from the random(3) set
561 of library functions, in particular sranddev(3), srandomdev(3)
562 and arc4random(3). The reason for this is that the KERN_ARND
563 sysctl only returns entropy if it thinks it has some to
564 share, and with RANDOM_DUMMY or no 'device random' this
568 An additional fix for the issue described in the 20150614 sendmail
569 entry below has been been committed in revision 284717.
572 FreeBSD's old make (fmake) has been removed from the system. It is
573 available as the devel/fmake port or via pkg install fmake.
576 The fix for the issue described in the 20150614 sendmail entry
577 below has been been committed in revision 284436. The work
578 around described in that entry is no longer needed unless the
579 default setting is overridden by a confDH_PARAMETERS configuration
580 setting of '5' or pointing to a 512 bit DH parameter file.
583 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
584 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
585 and devel/kyua to version 0.20+ and adjust any calling code to work
586 with Kyuafile and kyua.
589 The import of openssl to address the FreeBSD-SA-15:10.openssl
590 security advisory includes a change which rejects handshakes
591 with DH parameters below 768 bits. sendmail releases prior
592 to 8.15.2 (not yet released), defaulted to a 512 bit
593 DH parameter setting for client connections. To work around
594 this interoperability, sendmail can be configured to use a
595 2048 bit DH parameter by:
597 1. Edit /etc/mail/`hostname`.mc
598 2. If a setting for confDH_PARAMETERS does not exist or
599 exists and is set to a string beginning with '5',
601 3. If a setting for confDH_PARAMETERS exists and is set to
602 a file path, create a new file with:
603 openssl dhparam -out /path/to/file 2048
604 4. Rebuild the .cf file:
605 cd /etc/mail/; make; make install
607 cd /etc/mail/; make restart
609 A sendmail patch is coming, at which time this file will be
613 Generation of legacy formatted entries have been disabled by default
614 in pwd_mkdb(8), as all base system consumers of the legacy formatted
615 entries were converted to use the new format by default when the new,
616 machine independent format have been added and supported since FreeBSD
619 Please see the pwd_mkdb(8) manual page for further details.
622 Clang and llvm have been upgraded to 3.6.1 release. Please see the
623 20141231 entry below for information about prerequisites and upgrading,
624 if you are not already using 3.5.0 or higher.
627 TI platform code switched to using vendor DTS files and this update
628 may break existing systems running on Beaglebone, Beaglebone Black,
631 - dtb files should be regenerated/reinstalled. Filenames are the
632 same but content is different now
633 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
634 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
635 addressing scheme is now pin 25 on /dev/gpioc3.
636 - Pandaboard: /etc/ttys should be updated, serial console device is
637 now /dev/ttyu2, not /dev/ttyu0
640 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
641 If you need the GNU extension from groff soelim(1), install groff
642 from package: pkg install groff, or via ports: textproc/groff.
645 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
646 defined in symlink(7); previously symlinks were silently ignored.
649 The const qualifier has been removed from iconv(3) to comply with
650 POSIX. The ports tree is aware of this from r384038 onwards.
653 Libraries specified by LIBADD in Makefiles must have a corresponding
654 DPADD_<lib> variable to ensure correct dependencies. This is now
655 enforced in src.libnames.mk.
658 From legacy ata(4) driver was removed support for SATA controllers
659 supported by more functional drivers ahci(4), siis(4) and mvs(4).
660 Kernel modules ataahci and ataadaptec were removed completely,
661 replaced by ahci and mvs modules respectively.
664 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
665 the 20141231 entry below for information about prerequisites and
666 upgrading, if you are not already using 3.5.0 or higher.
669 The 32-bit PowerPC kernel has been changed to a position-independent
670 executable. This can only be booted with a version of loader(8)
671 newer than January 31, 2015, so make sure to update both world and
672 kernel before rebooting.
675 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
676 but before r278950, the RNG was not seeded properly. Immediately
677 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
678 ssh keys or openssl keys) that were generated w/ a kernel from that
679 range. This does not affect programs that directly used /dev/random
680 or /dev/urandom. All userland uses of arc4random(3) are affected.
683 The autofs(4) ABI was changed in order to restore binary compatibility
684 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
688 The powerpc64 kernel has been changed to a position-independent
689 executable. This can only be booted with a new version of loader(8),
690 so make sure to update both world and kernel before rebooting.
693 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
694 only release, no new features have been added. Please see the 20141231
695 entry below for information about prerequisites and upgrading, if you
696 are not already using 3.5.0.
699 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
700 taken from the ELF Tool Chain project rather than GNU binutils. They
701 should be drop-in replacements, with the addition of arm64 support.
702 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
703 binutils tools, if necessary. See 20150805 for updated information.
706 The default Unbound configuration now enables remote control
707 using a local socket. Users who have already enabled the
708 local_unbound service should regenerate their configuration
709 by running "service local_unbound setup" as root.
712 The GNU texinfo and GNU info pages have been removed.
713 To be able to view GNU info pages please install texinfo from ports.
716 Clang, llvm and lldb have been upgraded to 3.5.0 release.
718 As of this release, a prerequisite for building clang, llvm and lldb is
719 a C++11 capable compiler and C++11 standard library. This means that to
720 be able to successfully build the cross-tools stage of buildworld, with
721 clang as the bootstrap compiler, your system compiler or cross compiler
722 should either be clang 3.3 or later, or gcc 4.8 or later, and your
723 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
726 On any standard FreeBSD 10.x or 11.x installation, where clang and
727 libc++ are on by default (that is, on x86 or arm), this should work out
730 On 9.x installations where clang is enabled by default, e.g. on x86 and
731 powerpc, libc++ will not be enabled by default, so libc++ should be
732 built (with clang) and installed first. If both clang and libc++ are
733 missing, build clang first, then use it to build libc++.
735 On 8.x and earlier installations, upgrade to 9.x first, and then follow
736 the instructions for 9.x above.
738 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
739 default, and do not build clang.
741 Many embedded systems are resource constrained, and will not be able to
742 build clang in a reasonable time, or in some cases at all. In those
743 cases, cross building bootable systems on amd64 is a workaround.
745 This new version of clang introduces a number of new warnings, of which
746 the following are most likely to appear:
750 This warns in two cases, for both C and C++:
751 * When the code is trying to take the absolute value of an unsigned
752 quantity, which is effectively a no-op, and almost never what was
753 intended. The code should be fixed, if at all possible. If you are
754 sure that the unsigned quantity can be safely cast to signed, without
755 loss of information or undefined behavior, you can add an explicit
756 cast, or disable the warning.
758 * When the code is trying to take an absolute value, but the called
759 abs() variant is for the wrong type, which can lead to truncation.
760 If you want to disable the warning instead of fixing the code, please
761 make sure that truncation will not occur, or it might lead to unwanted
764 -Wtautological-undefined-compare and
765 -Wundefined-bool-conversion
767 These warn when C++ code is trying to compare 'this' against NULL, while
768 'this' should never be NULL in well-defined C++ code. However, there is
769 some legacy (pre C++11) code out there, which actively abuses this
770 feature, which was less strictly defined in previous C++ versions.
772 Squid and openjdk do this, for example. The warning can be turned off
773 for C++98 and earlier, but compiling the code in C++11 mode might result
774 in unexpected behavior; for example, the parts of the program that are
775 unreachable could be optimized away.
778 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
779 kernel sources have been removed. The .h files remain, since some
780 utilities include them. This will need to be fixed later.
781 If "mount -t oldnfs ..." is attempted, it will fail.
782 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
783 the utilities will report errors.
786 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
787 directories to top level SUBDIR variable when their parent
788 directory is included in LOCAL_DIRS. Users with build systems with
789 such hierarchies and without SUBDIR entries in the parent
790 directory Makefiles should add them or add the directories to
794 faith(4) and faithd(8) have been removed from the base system. Faith
795 has been obsolete for a very long time.
798 vt(4), the new console driver, is enabled by default. It brings
799 support for Unicode and double-width characters, as well as
800 support for UEFI and integration with the KMS kernel video
803 You may need to update your console settings in /etc/rc.conf,
804 most probably the keymap. During boot, /etc/rc.d/syscons will
805 indicate what you need to do.
807 vt(4) still has issues and lacks some features compared to
808 syscons(4). See the wiki for up-to-date information:
809 https://wiki.freebsd.org/Newcons
811 If you want to keep using syscons(4), you can do so by adding
812 the following line to /boot/loader.conf:
816 pjdfstest has been integrated into kyua as an opt-in test suite.
817 Please see share/doc/pjdfstest/README for more details on how to
821 gperf has been removed from the base system for architectures
822 that use clang. Ports that require gperf will obtain it from the
826 pjdfstest has been moved from tools/regression/pjdfstest to
830 At svn r271982, The default linux compat kernel ABI has been adjusted
831 to 2.6.18 in support of the linux-c6 compat ports infrastructure
832 update. If you wish to continue using the linux-f10 compat ports,
833 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
834 encouraged to update their linux-compat packages to linux-c6 during
835 their next update cycle.
838 The ofwfb driver, used to provide a graphics console on PowerPC when
839 using vt(4), no longer allows mmap() of all physical memory. This
840 will prevent Xorg on PowerPC with some ATI graphics cards from
841 initializing properly unless x11-servers/xorg-server is updated to
845 The xdev targets have been converted to using TARGET and
846 TARGET_ARCH instead of XDEV and XDEV_ARCH.
849 The default unbound configuration has been modified to address
850 issues with reverse lookups on networks that use private
851 address ranges. If you use the local_unbound service, run
852 "service local_unbound setup" as root to regenerate your
853 configuration, then "service local_unbound reload" to load the
857 The GNU texinfo and GNU info pages are not built and installed
858 anymore, WITH_INFO knob has been added to allow to built and install
860 UPDATE: see 20150102 entry on texinfo's removal
863 The GNU readline library is now an INTERNALLIB - that is, it is
864 statically linked into consumers (GDB and variants) in the base
865 system, and the shared library is no longer installed. The
866 devel/readline port is available for third party software that
870 The Itanium architecture (ia64) has been removed from the list of
871 known architectures. This is the first step in the removal of the
875 Commit r268115 has added NFSv4.1 server support, merged from
876 projects/nfsv4.1-server. Since this includes changes to the
877 internal interfaces between the NFS related modules, a full
878 build of the kernel and modules will be necessary.
879 __FreeBSD_version has been bumped.
882 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
883 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
884 which differs from the behaviour controlled by this knob.)
887 Maximal length of the serial number in CTL was increased from 16 to
888 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
889 and ctld, need to be rebuilt to work with a new kernel.
892 The libatf-c and libatf-c++ major versions were downgraded to 0 and
893 1 respectively to match the upstream numbers. They were out of
894 sync because, when they were originally added to FreeBSD, the
895 upstream versions were not respected. These libraries are private
896 and not yet built by default, so renumbering them should be a
897 non-issue. However, unclean source trees will yield broken test
898 programs once the operator executes "make delete-old-libs" after a
901 Additionally, the atf-sh binary was made private by moving it into
902 /usr/libexec/. Already-built shell test programs will keep the
903 path to the old binary so they will break after "make delete-old"
906 If you are using WITH_TESTS=yes (not the default), wipe the object
907 tree and rebuild from scratch to prevent spurious test failures.
908 This is only needed once: the misnumbered libraries and misplaced
909 binaries have been added to OptionalObsoleteFiles.inc so they will
910 be removed during a clean upgrade.
913 Clang and llvm have been upgraded to 3.4.1 release.
916 We bogusly installed src.opts.mk in /usr/share/mk. This file should
917 be removed to avoid issues in the future (and has been added to
921 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
922 past, it affected all builds that used the bsd.*.mk files. The old
923 behavior was a bug, but people may have relied upon it. To get this
924 behavior back, you can .include /etc/src.conf from /etc/make.conf
925 (which is still global and isn't changed). This also changes the
926 behavior of incremental builds inside the tree of individual
927 directories. Set MAKESYSPATH to ".../share/mk" to do that.
928 Although this has survived make universe and some upgrade scenarios,
929 other upgrade scenarios may have broken. At least one form of
930 temporary breakage was fixed with MAKESYSPATH settings for buildworld
931 as well... In cases where MAKESYSPATH isn't working with this
932 setting, you'll need to set it to the full path to your tree.
934 One side effect of all this cleaning up is that bsd.compiler.mk
935 is no longer implicitly included by bsd.own.mk. If you wish to
936 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
940 The lindev device has been removed since /dev/full has been made a
941 standard device. __FreeBSD_version has been bumped.
944 The knob WITHOUT_VI was added to the base system, which controls
945 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
946 in order to reorder files share/termcap and didn't build ex(1) as a
947 build tool, so building/installing with WITH_VI is highly advised for
948 build hosts for older releases.
950 This issue has been fixed in stable/9 and stable/10 in r277022 and
951 r276991, respectively.
954 The YES_HESIOD knob has been removed. It has been obsolete for
955 a decade. Please move to using WITH_HESIOD instead or your builds
956 will silently lack HESIOD.
959 The uart(4) driver has been changed with respect to its handling
960 of the low-level console. Previously the uart(4) driver prevented
961 any process from changing the baudrate or the CLOCAL and HUPCL
962 control flags. By removing the restrictions, operators can make
963 changes to the serial console port without having to reboot.
964 However, when getty(8) is started on the serial device that is
965 associated with the low-level console, a misconfigured terminal
966 line in /etc/ttys will now have a real impact.
967 Before upgrading the kernel, make sure that /etc/ttys has the
968 serial console device configured as 3wire without baudrate to
969 preserve the previous behaviour. E.g:
970 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
973 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
974 to improve performance. To re-enable it, if needed, run rpcbind
975 with command line option -W.
978 Switched back to the GPL dtc compiler due to updates in the upstream
979 dts files not being supported by the BSDL dtc compiler. You will need
980 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
981 may result while building dtb files during a kernel build if you fail
982 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
985 Clang and llvm have been upgraded to 3.4 release.
988 The nve(4) driver has been removed. Please use the nfe(4) driver
989 for NVIDIA nForce MCP Ethernet adapters instead.
992 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
993 This could cause certain C++ applications using shared libraries built
994 against the previous version of libc++ to crash. The incompatibility
995 has now been fixed, but any C++ applications or shared libraries built
996 between r261283 and r261801 should be recompiled.
999 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1000 capability mode support. Please note that enabling the feature in
1001 kernel is still highly recommended.
1004 OpenSSH is now built with sandbox support, and will use sandbox as
1005 the default privilege separation method. This requires Capsicum
1006 capability mode support in kernel.
1009 The libelf and libdwarf libraries have been updated to newer
1010 versions from upstream. Shared library version numbers for
1011 these two libraries were bumped. Any ports or binaries
1012 requiring these two libraries should be recompiled.
1013 __FreeBSD_version is bumped to 1100006.
1016 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1017 instead of providing an explicit one, this would prevent such
1018 Makefile from providing its own Kyuafile in the future during
1019 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1020 intervention is needed to clean an objdir if you use NO_CLEAN:
1021 # find /usr/obj -name Kyuafile | xargs rm -f
1024 The behavior of gss_pseudo_random() for the krb5 mechanism
1025 has changed, for applications requesting a longer random string
1026 than produced by the underlying enctype's pseudo-random() function.
1027 In particular, the random string produced from a session key of
1028 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1029 be different at the 17th octet and later, after this change.
1030 The counter used in the PRF+ construction is now encoded as a
1031 big-endian integer in accordance with RFC 4402.
1032 __FreeBSD_version is bumped to 1100004.
1035 The WITHOUT_ATF build knob has been removed and its functionality
1036 has been subsumed into the more generic WITHOUT_TESTS. If you were
1037 using the former to disable the build of the ATF libraries, you
1038 should change your settings to use the latter.
1041 The default version of mtree is nmtree which is obtained from
1042 NetBSD. The output is generally the same, but may vary
1043 slightly. If you found you need identical output adding
1044 "-F freebsd9" to the command line should do the trick. For the
1045 time being, the old mtree is available as fmtree.
1048 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1049 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1050 1.1.4_8 and verify bsdyml not linked in, before running "make
1052 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1054 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1057 The stable/10 branch has been created in subversion from head
1061 The rc.d/jail script has been updated to support jail(8)
1062 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1063 for per-jail configuration are automatically converted to
1064 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1065 This is transparently backward compatible. See below about some
1066 incompatibilities and rc.conf(5) manual page for more details.
1068 These variables are now deprecated in favor of jail(8) configuration
1069 file. One can use "rc.d/jail config <jname>" command to generate
1070 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1071 running the jail(8) utility. The default pathname of the
1072 configuration file is /etc/jail.conf and can be specified by
1073 using $jail_conf or $jail_<jname>_conf variables.
1075 Please note that jail_devfs_ruleset accepts an integer at
1076 this moment. Please consider to rewrite the ruleset name
1080 BIND has been removed from the base system. If all you need
1081 is a local resolver, simply enable and start the local_unbound
1082 service instead. Otherwise, several versions of BIND are
1083 available in the ports tree. The dns/bind99 port is one example.
1085 With this change, nslookup(1) and dig(1) are no longer in the base
1086 system. Users should instead use host(1) and drill(1) which are
1087 in the base system. Alternatively, nslookup and dig can
1088 be obtained by installing the dns/bind-tools port.
1091 With the addition of unbound(8), a new unbound user is now
1092 required during installworld. "mergemaster -p" can be used to
1093 add the user prior to installworld, as documented in the handbook.
1096 OpenSSH is now built with DNSSEC support, and will by default
1097 silently trust signed SSHFP records. This can be controlled with
1098 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1099 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1102 The GNU Compiler Collection and C++ standard library (libstdc++)
1103 are no longer built by default on platforms where clang is the system
1104 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1105 options in src.conf.
1108 The PROCDESC kernel option is now part of the GENERIC kernel
1109 configuration and is required for the rwhod(8) to work.
1110 If you are using custom kernel configuration, you should include
1114 The API and ABI related to the Capsicum framework was modified
1115 in backward incompatible way. The userland libraries and programs
1116 have to be recompiled to work with the new kernel. This includes the
1117 following libraries and programs, but the whole buildworld is
1118 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1119 kdump, procstat, rwho, rwhod, uniq.
1122 AES-NI intrinsic support has been added to gcc. The AES-NI module
1123 has been updated to use this support. A new gcc is required to build
1124 the aesni module on both i386 and amd64.
1127 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1128 Thus "device padlock_rng" and "device rdrand_rng" should be
1129 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1132 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1133 enables just the iconv* functionality and is now on by default.
1134 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1135 compatibility. Set WITHOUT_ICONV to build the old way.
1136 If you have been using WITH_ICONV before, you will very likely
1137 need to turn on WITH_LIBICONV_COMPAT.
1140 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1141 Illumos origin, including ZFS. If you have INVARIANTS in your
1142 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1144 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1145 locks if WITNESS option was set. Because that generated a lot of
1146 witness(9) reports and all of them were believed to be false
1147 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1148 can be used to achieve the previous behavior.
1151 Timer values in IPv6 data structures now use time_uptime instead
1152 of time_second. Although this is not a user-visible functional
1153 change, userland utilities which directly use them---ndp(8),
1154 rtadvd(8), and rtsold(8) in the base system---need to be updated
1155 to r253970 or later.
1158 find -delete can now delete the pathnames given as arguments,
1159 instead of only files found below them or if the pathname did
1160 not contain any slashes. Formerly, the following error message
1163 find: -delete: <path>: relative path potentially not safe
1165 Deleting the pathnames given as arguments can be prevented
1166 without error messages using -mindepth 1 or by changing
1167 directory and passing "." as argument to find. This works in the
1168 old as well as the new version of find.
1171 Behavior of devfs rules path matching has been changed.
1172 Pattern is now always matched against fully qualified devfs
1173 path and slash characters must be explicitly matched by
1174 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1175 subdirectories must be reviewed.
1178 The default ARM ABI has changed to the ARM EABI. The old ABI is
1179 incompatible with the ARM EABI and all programs and modules will
1180 need to be rebuilt to work with a new kernel.
1182 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1184 NOTE: Support for the old ABI will be removed in the future and
1185 users are advised to upgrade.
1188 pkg_install has been disconnected from the build if you really need it
1189 you should add WITH_PKGTOOLS in your src.conf(5).
1192 Most of network statistics structures were changed to be able
1193 keep 64-bits counters. Thus all tools, that work with networking
1194 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1197 Fix a bug that allowed a tracing process (e.g. gdb) to write
1198 to a memory-mapped file in the traced process's address space
1199 even if neither the traced process nor the tracing process had
1200 write access to that file.
1203 CVS has been removed from the base system. An exact copy
1204 of the code is available from the devel/cvs port.
1207 Some people report the following error after the switch to bmake:
1209 make: illegal option -- J
1210 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1212 *** [buildworld] Error code 2
1214 this likely due to an old instance of make in
1215 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1216 which src/Makefile will use that blindly, if it exists, so if
1217 you see the above error:
1219 rm -rf `make -V MAKEPATH`
1224 Use bmake by default.
1225 Whereas before one could choose to build with bmake via
1226 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1227 make. The goal is to remove these knobs for 10-RELEASE.
1229 It is worth noting that bmake (like gmake) treats the command
1230 line as the unit of failure, rather than statements within the
1231 command line. Thus '(cd some/where && dosomething)' is safer
1232 than 'cd some/where; dosomething'. The '()' allows consistent
1233 behavior in parallel build.
1236 Fix a bug that allows NFS clients to issue READDIR on files.
1239 The WITHOUT_IDEA option has been removed because
1240 the IDEA patent expired.
1243 The sysctl which controls TRIM support under ZFS has been renamed
1244 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1248 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1249 rather than creating it's own in the temporary directory in
1250 order allow access to bootstrapped versions of tools such as
1251 install and mtree. When upgrading from version of FreeBSD where
1252 the install command does not support -l, you will need to
1253 install a new mergemaster command if mergemaster -p is required.
1254 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1258 Legacy ATA stack, disabled and replaced by new CAM-based one since
1259 FreeBSD 9.0, completely removed from the sources. Kernel modules
1260 atadisk and atapi*, user-level tools atacontrol and burncd are
1261 removed. Kernel option `options ATA_CAM` is now permanently enabled
1265 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1266 and socketpair(2). Software, in particular Kerberos, may
1267 automatically detect and use these during building. The resulting
1268 binaries will not work on older kernels.
1271 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1272 information, see the respective 20130304 entry).
1275 Recent commits to callout(9) changed the size of struct callout,
1276 so the KBI is probably heavily disturbed. Also, some functions
1277 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1278 by macros. Every kernel module using it won't load, so rebuild
1281 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1282 but does not initialize by default (because of the new CTL_DISABLE
1283 option) to save memory. To re-enable it, remove the CTL_DISABLE
1284 option from the kernel config file or set kern.cam.ctl.disable=0
1285 in /boot/loader.conf.
1288 The ctl device has been disabled in GENERIC for i386 and amd64.
1289 This was done due to the extra memory being allocated at system
1290 initialisation time by the ctl driver which was only used if
1291 a CAM target device was created. This makes a FreeBSD system
1292 unusable on 128MB or less of RAM.
1295 A new compression method (lz4) has been merged to -HEAD. Please
1296 refer to zpool-features(7) for more information.
1298 Please refer to the "ZFS notes" section of this file for information
1299 on upgrading boot ZFS pools.
1302 A BSD-licensed patch(1) variant has been added and is installed
1303 as bsdpatch, being the GNU version the default patch.
1304 To inverse the logic and use the BSD-licensed one as default,
1305 while having the GNU version installed as gnupatch, rebuild
1306 and install world with the WITH_BSD_PATCH knob set.
1309 Due to the use of the new -l option to install(1) during build
1310 and install, you must take care not to directly set the INSTALL
1311 make variable in your /etc/make.conf, /etc/src.conf, or on the
1312 command line. If you wish to use the -C flag for all installs
1313 you may be able to add INSTALL+=-C to /etc/make.conf or
1317 The install(1) option -M has changed meaning and now takes an
1318 argument that is a file or path to append logs to. In the
1319 unlikely event that -M was the last option on the command line
1320 and the command line contained at least two files and a target
1321 directory the first file will have logs appended to it. The -M
1322 option served little practical purpose in the last decade so its
1323 use is expected to be extremely rare.
1326 After switching to Clang as the default compiler some users of ZFS
1327 on i386 systems started to experience stack overflow kernel panics.
1328 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1331 GEOM_LABEL now mangles label names read from file system metadata.
1332 Mangling affect labels containing spaces, non-printable characters,
1333 '%' or '"'. Device names in /etc/fstab and other places may need to
1337 By default, only the 10 most recent kernel dumps will be saved. To
1338 restore the previous behaviour (no limit on the number of kernel dumps
1339 stored in the dump directory) add the following line to /etc/rc.conf:
1344 With the addition of auditdistd(8), a new auditdistd user is now
1345 required during installworld. "mergemaster -p" can be used to
1346 add the user prior to installworld, as documented in the handbook.
1349 The sin6_scope_id member variable in struct sockaddr_in6 is now
1350 filled by the kernel before passing the structure to the userland via
1351 sysctl or routing socket. This means the KAME-specific embedded scope
1352 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1353 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1354 __FreeBSD_version is bumped to 1000025.
1357 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1358 This means that the world and kernel will be compiled with clang
1359 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1360 and /usr/bin/cpp. To disable this behavior and revert to building
1361 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1362 of current may need to bootstrap WITHOUT_CLANG first if the clang
1363 build fails (its compatibility window doesn't extend to the 9 stable
1367 The IPFIREWALL_FORWARD kernel option has been removed. Its
1368 functionality now turned on by default.
1371 The ZERO_COPY_SOCKET kernel option has been removed and
1372 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1373 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1374 mechanism which is not safe and may result in kernel crashes.
1375 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1376 driver supports disposeable external page sized mbuf storage.
1377 Proper replacements for both zero-copy mechanisms are under
1378 consideration and will eventually lead to complete removal
1379 of the two kernel options.
1382 The IPv4 network stack has been converted to network byte
1383 order. The following modules need to be recompiled together
1384 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1385 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1388 Support for non-MPSAFE filesystems was removed from VFS. The
1389 VFS_VERSION was bumped, all filesystem modules shall be
1393 All the non-MPSAFE filesystems have been disconnected from
1394 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1395 portalfs, smbfs, xfs.
1398 The interface cloning API and ABI has changed. The following
1399 modules need to be recompiled together with kernel:
1400 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1401 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1402 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1405 The sdhci driver was split in two parts: sdhci (generic SD Host
1406 Controller logic) and sdhci_pci (actual hardware driver).
1407 No kernel config modifications are required, but if you
1408 load sdhc as a module you must switch to sdhci_pci instead.
1411 Import the FUSE kernel and userland support into base system.
1414 The GNU sort(1) program has been removed since the BSD-licensed
1415 sort(1) has been the default for quite some time and no serious
1416 problems have been reported. The corresponding WITH_GNU_SORT
1420 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1421 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1425 The net80211(4) ABI has been changed to allow for improved driver
1426 PS-POLL and power-save support. All wireless drivers need to be
1427 recompiled to work with the new kernel.
1430 The random(4) support for the VIA hardware random number
1431 generator (`PADLOCK') is no longer enabled unconditionally.
1432 Add the padlock_rng device in the custom kernel config if
1433 needed. The GENERIC kernels on i386 and amd64 do include the
1434 device, so the change only affects the custom kernel
1438 The pf(4) packet filter ABI has been changed. pfctl(8) and
1439 snmp_pf module need to be recompiled to work with new kernel.
1442 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1443 to -HEAD. Pools that have empty_bpobj in active state can not be
1444 imported read-write with ZFS implementations that do not support
1445 this feature. For more information read the zpool-features(5)
1449 The sparc64 ZFS loader has been changed to no longer try to auto-
1450 detect ZFS providers based on diskN aliases but now requires these
1451 to be explicitly listed in the OFW boot-device environment variable.
1454 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1455 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1456 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1459 The following sysctls and tunables have been renamed for consistency
1460 with other variables:
1461 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1462 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1465 The sort utility has been replaced with BSD sort. For now, GNU sort
1466 is also available as "gnusort" or the default can be set back to
1467 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1468 installed as "bsdsort".
1471 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1472 Starting with this version the old system of ZFS pool versioning
1473 is superseded by "feature flags". This concept enables forward
1474 compatibility against certain future changes in functionality of ZFS
1475 pools. The first read-only compatible "feature flag" for ZFS pools
1476 is named "com.delphix:async_destroy". For more information
1477 read the new zpool-features(5) manual page.
1478 Please refer to the "ZFS notes" section of this file for information
1479 on upgrading boot ZFS pools.
1482 The malloc(3) implementation embedded in libc now uses sources imported
1483 as contrib/jemalloc. The most disruptive API change is to
1484 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1485 delete it prior to installworld, and optionally re-create it using the
1486 new format after rebooting. See malloc.conf(5) for details
1487 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1491 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1492 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1493 now spelled mips. This is to aid compatibility with third-party
1494 software that expects this naming scheme in uname(3). Little-endian
1495 settings are unchanged. If you are updating a big-endian mips64 machine
1496 from before this change, you may need to set MACHINE_ARCH=mips64 in
1497 your environment before the new build system will recognize your machine.
1500 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1504 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1505 nullfs(5) did not pass through all behaviours to the underlying layer,
1506 as a result if we bound to a socket on the lower layer we could connect
1507 only to the lower path; if we bound to the upper layer we could connect
1508 only to the upper path. The new behavior is one can connect to both the
1509 lower and the upper paths regardless what layer path one binds to.
1512 The getifaddrs upgrade path broken with 20111215 has been restored.
1513 If you have upgraded in between 20111215 and 20120209 you need to
1514 recompile libc again with your kernel. You still need to recompile
1515 world to be able to configure CARP but this restriction already
1516 comes from 20111215.
1519 The set_rcvar() function has been removed from /etc/rc.subr. All
1520 base and ports rc.d scripts have been updated, so if you have a
1521 port installed with a script in /usr/local/etc/rc.d you can either
1522 hand-edit the rcvar= line, or reinstall the port.
1524 An easy way to handle the mass-update of /etc/rc.d:
1525 rm /etc/rc.d/* && mergemaster -i
1528 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1529 on the current CPU and prevents other threads from running.
1530 This behavior can be reverted using the kern.stop_scheduler_on_panic
1532 The new behavior can be incompatible with kern.sync_on_panic.
1535 The carp(4) facility has been changed significantly. Configuration
1536 of the CARP protocol via ifconfig(8) has changed, as well as format
1537 of CARP events submitted to devd(8) has changed. See manual pages
1538 for more information. The arpbalance feature of carp(4) is currently
1539 not supported anymore.
1541 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1542 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1543 need to be recompiled.
1546 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1550 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1551 explicitely support non-MPSAFE filesystems.
1552 It is on by default for all supported platform at this present
1556 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1557 i386 and pc98 GENERIC kernel configuration files.
1560 sysinstall has been removed
1563 The stable/9 branch created in subversion. This corresponds to the
1564 RELENG_9 branch in CVS.
1570 Avoid using make -j when upgrading. While generally safe, there are
1571 sometimes problems using -j to upgrade. If your upgrade fails with
1572 -j, please try again without -j. From time to time in the past there
1573 have been problems using -j with buildworld and/or installworld. This
1574 is especially true when upgrading between "distant" versions (eg one
1575 that cross a major release boundary or several minor releases, or when
1576 several months have passed on the -current branch).
1578 Sometimes, obscure build problems are the result of environment
1579 poisoning. This can happen because the make utility reads its
1580 environment when searching for values for global variables. To run
1581 your build attempts in an "environmental clean room", prefix all make
1582 commands with 'env -i '. See the env(1) manual page for more details.
1584 When upgrading from one major version to another it is generally best to
1585 upgrade to the latest code in the currently installed branch first, then
1586 do an upgrade to the new branch. This is the best-tested upgrade path,
1587 and has the highest probability of being successful. Please try this
1588 approach if you encounter problems with a major version upgrade. Since
1589 the stable 4.x branch point, one has generally been able to upgade from
1590 anywhere in the most recent stable branch to head / current (or even the
1591 last couple of stable branches). See the top of this file when there's
1594 When upgrading a live system, having a root shell around before
1595 installing anything can help undo problems. Not having a root shell
1596 around can lead to problems if pam has changed too much from your
1597 starting point to allow continued authentication after the upgrade.
1599 This file should be read as a log of events. When a later event changes
1600 information of a prior event, the prior event should not be deleted.
1601 Instead, a pointer to the entry with the new information should be
1602 placed in the old entry. Readers of this file should also sanity check
1603 older entries before relying on them blindly. Authors of new entries
1604 should write them with this in mind.
1608 When upgrading the boot ZFS pool to a new version, always follow
1611 1.) recompile and reinstall the ZFS boot loader and boot block
1612 (this is part of "make buildworld" and "make installworld")
1614 2.) update the ZFS boot block on your boot drive
1616 The following example updates the ZFS boot block on the first
1617 partition (freebsd-boot) of a GPT partitioned drive ada0:
1618 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1620 Non-boot pools do not need these updates.
1624 If you are updating from a prior version of FreeBSD (even one just
1625 a few days old), you should follow this procedure. It is the most
1626 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1628 make kernel-toolchain
1629 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1630 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1632 To test a kernel once
1633 ---------------------
1634 If you just want to boot a kernel once (because you are not sure
1635 if it works, or if you want to boot a known bad kernel to provide
1636 debugging information) run
1637 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1638 nextboot -k testkernel
1640 To just build a kernel when you know that it won't mess you up
1641 --------------------------------------------------------------
1642 This assumes you are already running a CURRENT system. Replace
1643 ${arch} with the architecture of your machine (e.g. "i386",
1644 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1646 cd src/sys/${arch}/conf
1647 config KERNEL_NAME_HERE
1648 cd ../compile/KERNEL_NAME_HERE
1653 If this fails, go to the "To build a kernel" section.
1655 To rebuild everything and install it on the current system.
1656 -----------------------------------------------------------
1657 # Note: sometimes if you are running current you gotta do more than
1658 # is listed here if you are upgrading from a really old current.
1660 <make sure you have good level 0 dumps>
1662 make kernel KERNCONF=YOUR_KERNEL_HERE
1664 <reboot in single user> [3]
1671 To cross-install current onto a separate partition
1672 --------------------------------------------------
1673 # In this approach we use a separate partition to hold
1674 # current's root, 'usr', and 'var' directories. A partition
1675 # holding "/", "/usr" and "/var" should be about 2GB in
1678 <make sure you have good level 0 dumps>
1681 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1682 <maybe newfs current's root partition>
1683 <mount current's root partition on directory ${CURRENT_ROOT}>
1684 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1685 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1686 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1687 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1688 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1689 <reboot into current>
1690 <do a "native" rebuild/install as described in the previous section>
1691 <maybe install compatibility libraries from ports/misc/compat*>
1695 To upgrade in-place from stable to current
1696 ----------------------------------------------
1697 <make sure you have good level 0 dumps>
1699 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1701 <reboot in single user> [3]
1708 Make sure that you've read the UPDATING file to understand the
1709 tweaks to various things you need. At this point in the life
1710 cycle of current, things change often and you are on your own
1711 to cope. The defaults can also change, so please read ALL of
1712 the UPDATING entries.
1714 Also, if you are tracking -current, you must be subscribed to
1715 freebsd-current@freebsd.org. Make sure that before you update
1716 your sources that you have read and understood all the recent
1717 messages there. If in doubt, please track -stable which has
1718 much fewer pitfalls.
1720 [1] If you have third party modules, such as vmware, you
1721 should disable them at this point so they don't crash your
1724 [3] From the bootblocks, boot -s, and then do
1729 adjkerntz -i # if CMOS is wall time
1730 Also, when doing a major release upgrade, it is required that
1731 you boot into single user mode to do the installworld.
1733 [4] Note: This step is non-optional. Failure to do this step
1734 can result in a significant reduction in the functionality of the
1735 system. Attempting to do it by hand is not recommended and those
1736 that pursue this avenue should read this file carefully, as well
1737 as the archives of freebsd-current and freebsd-hackers mailing lists
1738 for potential gotchas. The -U option is also useful to consider.
1739 See mergemaster(8) for more information.
1741 [5] Usually this step is a noop. However, from time to time
1742 you may need to do this if you get unknown user in the following
1743 step. It never hurts to do it all the time. You may need to
1744 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1745 install) after the buildworld before this step if you last updated
1746 from current before 20130425 or from -stable before 20130430.
1748 [6] This only deletes old files and directories. Old libraries
1749 can be deleted by "make delete-old-libs", but you have to make
1750 sure that no program is using those libraries anymore.
1752 [8] In order to have a kernel that can run the 4.x binaries needed to
1753 do an installworld, you must include the COMPAT_FREEBSD4 option in
1754 your kernel. Failure to do so may leave you with a system that is
1755 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1756 required to run the 5.x binaries on more recent kernels. And so on
1757 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1759 Make sure that you merge any new devices from GENERIC since the
1760 last time you updated your kernel config file.
1762 [9] When checking out sources, you must include the -P flag to have
1763 cvs prune empty directories.
1765 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1766 "?=" instead of the "=" assignment operator, so that buildworld can
1767 override the CPUTYPE if it needs to.
1769 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1770 not on the command line, or in /etc/make.conf. buildworld will
1771 warn if it is improperly defined.
1774 This file contains a list, in reverse chronological order, of major
1775 breakages in tracking -current. It is not guaranteed to be a complete
1776 list of such breakages, and only contains entries since September 23, 2011.
1777 If you need to see UPDATING entries from before that date, you will need
1778 to fetch an UPDATING file from an older FreeBSD release.
1780 Copyright information:
1782 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1784 Redistribution, publication, translation and use, with or without
1785 modification, in full or in part, in any form or format of this
1786 document are permitted without further permission from the author.
1788 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1789 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1790 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1791 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1792 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1793 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1794 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1795 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1796 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1797 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1798 POSSIBILITY OF SUCH DAMAGE.
1800 Contact Warner Losh if you have any questions about your use of