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 As of r316810 for ipfilter, keep frags is no longer assumed when
56 keep state is specified in a rule. r316810 aligns ipfilter with
57 documentation in man pages separating keep frags from keep state.
58 This allows keep state to be specified without forcing keep frags
59 and allows keep frags to be specified independently of keep state.
60 To maintain previous behaviour, also specify keep frags with
61 keep state (as documented in ipf.conf.5).
64 arm64 builds now use the base system LLD 4.0.0 linker by default,
65 instead of requiring that the aarch64-binutils port or package be
66 installed. To continue using aarch64-binutils, set
67 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
70 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
71 use any explicitly assigned loopback address available in the jail
72 instead of using the first assigned address of the jail.
75 The ctl.ko module no longer implements the iSCSI target frontend:
76 cfiscsi.ko does instead.
78 If building cfiscsi.ko as a kernel module, the module can be loaded
79 via one of the following methods:
80 - `cfiscsi_load="YES"` in loader.conf(5).
81 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
82 - ctladm(8)/ctld(8), when compiled with iSCSI support
83 (`WITH_ISCSI=yes` in src.conf(5))
85 Please see cfiscsi(4) for more details.
88 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
89 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
90 same source (previously, the dependency of mmcsd.ko on mmc.ko was
91 missing, but mmcsd.ko now will refuse to load if it is incompatible
95 The syntax of ipfw(8) named states was changed to avoid ambiguity.
96 If you have used named states in the firewall rules, you need to modify
97 them after installworld and before rebooting. Now named states must
98 be prefixed with colon.
101 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
102 removed as the userland we provide cannot use them. The KMS version
103 (sys/dev/drm2) supports the same hardware.
106 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
107 Please see the 20141231 entry below for information about prerequisites
108 and upgrading, if you are not already using clang 3.5.0 or higher.
111 The code that provides support for ZFS .zfs/ directory functionality
112 has been reimplemented. It's not possible now to create a snapshot
113 by mkdir under .zfs/snapshot/. That should be the only user visible
117 EISA bus support has been removed. The WITH_EISA option is no longer
121 MCA bus support has been removed.
124 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
125 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
128 The EM_MULTIQUEUE kernel configuration option is deprecated now that
129 the em(4) driver conforms to iflib specifications.
132 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
133 IFLIB. If you have a custom kernel configuration that excludes em(4)
134 but you use igb(4), you need to re-add em(4) to your custom configuration.
137 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
138 Please see the 20141231 entry below for information about prerequisites
139 and upgrading, if you are not already using clang 3.5.0 or higher.
142 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
143 Please see the 20141231 entry below for information about prerequisites
144 and upgrading, if you are not already using clang 3.5.0 or higher.
147 The layout of the pmap structure has changed for powerpc to put the pmap
148 statistics at the front for all CPU variations. libkvm(3) and all tools
149 that link against it need to be recompiled.
152 isl(4) and cyapa(4) drivers now require a new driver,
153 chromebook_platform(4), to work properly on Chromebook-class hardware.
154 On other types of hardware the drivers may need to be configured using
155 device hints. Please see the corresponding manual pages for details.
158 The urtwn(4) driver was merged into rtwn(4) and now consists of
159 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
161 Also, firmware for RTL8188CE was renamed due to possible name
162 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
165 GNU rcs has been removed from base. It is available as packages:
166 - rcs: Latest GPLv3 GNU rcs version.
167 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
171 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
172 modules now requires that the kernel configuration contain the
173 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
176 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
177 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
180 Relocatable object files with the extension of .So have been renamed
181 to use an extension of .pico instead. The purpose of this change is
182 to avoid a name clash with shared libraries on case-insensitive file
183 systems. On those file systems, foo.So is the same file as foo.so.
186 GNU rcs has been turned off by default. It can (temporarily) be built
187 again by adding WITH_RCS knob in src.conf.
188 Otherwise, GNU rcs is available from packages:
189 - rcs: Latest GPLv3 GNU rcs version.
190 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
193 The backup_uses_rcs functionality has been removed from rc.subr.
196 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
197 two separate components, QUEUE_MACRO_DEBUG_TRACE and
198 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
199 QUEUE_MACRO_DEBUG behavior.
202 r304787 changed some ioctl interfaces between the iSCSI userspace
203 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
204 rebuilt to work with new kernels. __FreeBSD_version has been bumped
208 The UDP receive code has been updated to only treat incoming UDP
209 packets that were addressed to an L2 broadcast address as L3
210 broadcast packets. It is not expected that this will affect any
211 standards-conforming UDP application. The new behaviour can be
212 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
216 Remove the openbsd_poll system call.
217 __FreeBSD_version has been bumped because of this.
220 The libc stub for the pipe(2) system call has been replaced with
221 a wrapper that calls the pipe2(2) system call and the pipe(2)
222 system call is now only implemented by the kernels that include
223 "options COMPAT_FREEBSD10" in their config file (this is the
224 default). Users should ensure that this option is enabled in
225 their kernel or upgrade userspace to r302092 before upgrading their
229 CAM will now strip leading spaces from SCSI disks' serial numbers.
230 This will affect users who create UFS filesystems on SCSI disks using
231 those disk's diskid device nodes. For example, if /etc/fstab
232 previously contained a line like
233 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
234 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
235 transforms like gmirror may also be affected. ZFS users should
239 The bitstring(3) API has been updated with new functionality and
240 improved performance. But it is binary-incompatible with the old API.
241 Objects built with the new headers may not be linked against objects
242 built with the old headers.
245 The brk and sbrk functions have been removed from libc on arm64.
246 Binutils from ports has been updated to not link to these
247 functions and should be updated to the latest version before
248 installing a new libc.
251 The armv6 port now defaults to hard float ABI. Limited support
252 for running both hardfloat and soft float on the same system
253 is available using the libraries installed with -DWITH_LIBSOFT.
254 This has only been tested as an upgrade path for installworld
255 and packages may fail or need manual intervention to run. New
256 packages will be needed.
258 To update an existing self-hosted armv6hf system, you must add
259 TARGET_ARCH=armv6 on the make command line for both the build
260 and the install steps.
263 Kernel modules compiled outside of a kernel build now default to
264 installing to /boot/modules instead of /boot/kernel. Many kernel
265 modules built this way (such as those in ports) already overrode
266 KMODDIR explicitly to install into /boot/modules. However,
267 manually building and installing a module from /sys/modules will
268 now install to /boot/modules instead of /boot/kernel.
271 The CAM I/O scheduler has been committed to the kernel. There should be
272 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
273 list of known rogues that claim support for this but actually corrupt
274 data is believed to be complete, be on the lookout for data
275 corruption. The known rogue list is believed to be complete:
277 o Crucial MX100, M550 drives with MU01 firmware.
278 o Micron M510 and M550 drives with MU01 firmware.
279 o Micron M500 prior to MU07 firmware
280 o Samsung 830, 840, and 850 all firmwares
281 o FCCT M500 all firmwares
283 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
284 with working NCQ TRIM. For Micron branded drives, see your sales rep for
285 updated firmware. Black listed drives will work correctly because these
286 drives work correctly so long as no NCQ TRIMs are sent to them. Given
287 this list is the same as found in Linux, it's believed there are no
288 other rogues in the market place. All other models from the above
291 To be safe, if you are at all concerned, you can quirk each of your
292 drives to prevent NCQ from being sent by setting:
293 kern.cam.ada.X.quirks="0x2"
294 in loader.conf. If the drive requires the 4k sector quirk, set the
298 The FAST_DEPEND build option has been removed and its functionality is
299 now the one true way. The old mkdep(1) style of 'make depend' has
300 been removed. See 20160311 for further details.
303 Resource range types have grown from unsigned long to uintmax_t. All
304 drivers, and anything using libdevinfo, need to be recompiled.
307 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
308 builds. It no longer runs mkdep(1) during 'make depend', and the
309 'make depend' stage can safely be skipped now as it is auto ran
310 when building 'make all' and will generate all SRCS and DPSRCS before
311 building anything else. Dependencies are gathered at compile time with
312 -MF flags kept in separate .depend files per object file. Users should
313 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
317 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
318 kernel modules. Therefore, if you load any kernel modules at boot time,
319 please install the boot loaders after you install the kernel, but before
323 make kernel KERNCONF=YOUR_KERNEL_HERE
324 make -C sys/boot install
325 <reboot in single user>
327 Then follow the usual steps, described in the General Notes section,
331 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
332 see the 20141231 entry below for information about prerequisites and
333 upgrading, if you are not already using clang 3.5.0 or higher.
336 The AIO subsystem is now a standard part of the kernel. The
337 VFS_AIO kernel option and aio.ko kernel module have been removed.
338 Due to stability concerns, asynchronous I/O requests are only
339 permitted on sockets and raw disks by default. To enable
340 asynchronous I/O requests on all file types, set the
341 vfs.aio.enable_unsafe sysctl to a non-zero value.
344 The ELF object manipulation tool objcopy is now provided by the
345 ELF Tool Chain project rather than by GNU binutils. It should be a
346 drop-in replacement, with the addition of arm64 support. The
347 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
348 to obtain the GNU version if necessary.
351 Building ZFS pools on top of zvols is prohibited by default. That
352 feature has never worked safely; it's always been prone to deadlocks.
353 Using a zvol as the backing store for a VM guest's virtual disk will
354 still work, even if the guest is using ZFS. Legacy behavior can be
355 restored by setting vfs.zfs.vol.recursive=1.
358 The NONE and HPN patches has been removed from OpenSSH. They are
359 still available in the security/openssh-portable port.
362 With the addition of ypldap(8), a new _ypldap user is now required
363 during installworld. "mergemaster -p" can be used to add the user
364 prior to installworld, as documented in the handbook.
367 The tftp loader (pxeboot) now uses the option root-path directive. As a
368 consequence it no longer looks for a pxeboot.4th file on the tftp
369 server. Instead it uses the regular /boot infrastructure as with the
373 The code to start recording plug and play data into the modules has
374 been committed. While the old tools will properly build a new kernel,
375 a number of warnings about "unknown metadata record 4" will be produced
376 for an older kldxref. To avoid such warnings, make sure to rebuild
377 the kernel toolchain (or world). Make sure that you have r292078 or
378 later when trying to build 292077 or later before rebuilding.
381 Debug data files are now built by default with 'make buildworld' and
382 installed with 'make installworld'. This facilitates debugging but
383 requires more disk space both during the build and for the installed
384 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
388 r291527 changed the internal interface between the nfsd.ko and
389 nfscommon.ko modules. As such, they must both be upgraded to-gether.
390 __FreeBSD_version has been bumped because of this.
393 Add support for unicode collation strings leads to a change of
394 order of files listed by ls(1) for example. To get back to the old
395 behaviour, set LC_COLLATE environment variable to "C".
397 Databases administrators will need to reindex their databases given
398 collation results will be different.
400 Due to a bug in install(1) it is recommended to remove the ancient
401 locales before running make installworld.
403 rm -rf /usr/share/locale/*
406 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
407 libcrypto.so.7 or libssl.so.7 must be recompiled.
410 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
411 Kernel modules isp_2400_multi and isp_2500_multi were removed and
412 should be replaced with isp_2400 and isp_2500 modules respectively.
415 The build previously allowed using 'make -n' to not recurse into
416 sub-directories while showing what commands would be executed, and
417 'make -n -n' to recursively show commands. Now 'make -n' will recurse
418 and 'make -N' will not.
421 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
422 and etcupdate will now use this file. A custom sendmail.cf is now
423 updated via this mechanism rather than via installworld. If you had
424 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
425 want to remove the exclusion or change it to "always install".
426 /etc/mail/sendmail.cf is now managed the same way regardless of
427 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
428 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
431 Compatibility shims for legacy ATA device names have been removed.
432 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
433 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
434 environment variables, /dev/ad* and /dev/ar* symbolic links.
437 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
438 Please see the 20141231 entry below for information about prerequisites
439 and upgrading, if you are not already using clang 3.5.0 or higher.
442 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
443 and renamed from .symbols to .debug. This reduces the size requirements
444 on the boot partition or file system and provides consistency with
445 userland debug files.
447 When using the supported kernel installation method the
448 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
449 as is done with /boot/kernel.
451 Developers wishing to maintain the historical behavior of installing
452 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
455 The wireless drivers had undergone changes that remove the 'parent
456 interface' from the ifconfig -l output. The rc.d network scripts
457 used to check presence of a parent interface in the list, so old
458 scripts would fail to start wireless networking. Thus, etcupdate(3)
459 or mergemaster(8) run is required after kernel update, to update your
460 rc.d scripts in /etc.
463 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
464 These configurations are now automatically interpreted as
465 'scrub fragment reassemble'.
468 Kernel-loadable modules for the random(4) device are back. To use
469 them, the kernel must have
472 options RANDOM_LOADABLE
474 kldload(8) can then be used to load random_fortuna.ko
475 or random_yarrow.ko. Please note that due to the indirect
476 function calls that the loadable modules need to provide,
477 the build-in variants will be slightly more efficient.
479 The random(4) kernel option RANDOM_DUMMY has been retired due to
480 unpopularity. It was not all that useful anyway.
483 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
484 Control over building the ELF Tool Chain tools is now provided by
485 the WITHOUT_TOOLCHAIN knob.
488 The polarity of Pulse Per Second (PPS) capture events with the
489 uart(4) driver has been corrected. Prior to this change the PPS
490 "assert" event corresponded to the trailing edge of a positive PPS
491 pulse and the "clear" event was the leading edge of the next pulse.
493 As the width of a PPS pulse in a typical GPS receiver is on the
494 order of 1 millisecond, most users will not notice any significant
495 difference with this change.
497 Anyone who has compensated for the historical polarity reversal by
498 configuring a negative offset equal to the pulse width will need to
499 remove that workaround.
502 The default group assigned to /dev/dri entries has been changed
503 from 'wheel' to 'video' with the id of '44'. If you want to have
504 access to the dri devices please add yourself to the video group
507 # pw groupmod video -m $USER
510 The menu.rc and loader.rc files will now be replaced during
511 upgrades. Please migrate local changes to menu.rc.local and
512 loader.rc.local instead.
515 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
516 strings and strip have been removed. The src.conf(5) knob
517 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
520 As ZFS requires more kernel stack pages than is the default on some
521 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
522 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
524 Please consider using 'options KSTACK_PAGES=X' where X is greater
525 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
528 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
529 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
530 default, i.e., they will not contain "::". For example, instead
531 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
532 to have a more specific match, such as different map entries for
533 IPv6:0:0 vs IPv6:0. This change requires that configuration
534 data (including maps, files, classes, custom ruleset, etc.) must
535 use the same format, so make certain such configuration data is
536 upgrading. As a very simple check search for patterns like
537 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
538 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
539 the cf option UseCompressedIPv6Addresses.
542 The default kernel entropy-processing algorithm is now
543 Fortuna, replacing Yarrow.
545 Assuming you have 'device random' in your kernel config
546 file, the configurations allow a kernel option to override
547 this default. You may choose *ONE* of:
549 options RANDOM_YARROW # Legacy /dev/random algorithm.
550 options RANDOM_DUMMY # Blocking-only driver.
552 If you have neither, you get Fortuna. For most people,
553 read no further, Fortuna will give a /dev/random that works
554 like it always used to, and the difference will be irrelevant.
556 If you remove 'device random', you get *NO* kernel-processed
557 entropy at all. This may be acceptable to folks building
558 embedded systems, but has complications. Carry on reading,
559 and it is assumed you know what you need.
561 *PLEASE* read random(4) and random(9) if you are in the
562 habit of tweaking kernel configs, and/or if you are a member
563 of the embedded community, wanting specific and not-usual
564 behaviour from your security subsystems.
566 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
567 random', you will NOT have a functioning /dev/random, and
568 many cryptographic features will not work, including SSH.
569 You may also find strange behaviour from the random(3) set
570 of library functions, in particular sranddev(3), srandomdev(3)
571 and arc4random(3). The reason for this is that the KERN_ARND
572 sysctl only returns entropy if it thinks it has some to
573 share, and with RANDOM_DUMMY or no 'device random' this
577 An additional fix for the issue described in the 20150614 sendmail
578 entry below has been been committed in revision 284717.
581 FreeBSD's old make (fmake) has been removed from the system. It is
582 available as the devel/fmake port or via pkg install fmake.
585 The fix for the issue described in the 20150614 sendmail entry
586 below has been been committed in revision 284436. The work
587 around described in that entry is no longer needed unless the
588 default setting is overridden by a confDH_PARAMETERS configuration
589 setting of '5' or pointing to a 512 bit DH parameter file.
592 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
593 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
594 and devel/kyua to version 0.20+ and adjust any calling code to work
595 with Kyuafile and kyua.
598 The import of openssl to address the FreeBSD-SA-15:10.openssl
599 security advisory includes a change which rejects handshakes
600 with DH parameters below 768 bits. sendmail releases prior
601 to 8.15.2 (not yet released), defaulted to a 512 bit
602 DH parameter setting for client connections. To work around
603 this interoperability, sendmail can be configured to use a
604 2048 bit DH parameter by:
606 1. Edit /etc/mail/`hostname`.mc
607 2. If a setting for confDH_PARAMETERS does not exist or
608 exists and is set to a string beginning with '5',
610 3. If a setting for confDH_PARAMETERS exists and is set to
611 a file path, create a new file with:
612 openssl dhparam -out /path/to/file 2048
613 4. Rebuild the .cf file:
614 cd /etc/mail/; make; make install
616 cd /etc/mail/; make restart
618 A sendmail patch is coming, at which time this file will be
622 Generation of legacy formatted entries have been disabled by default
623 in pwd_mkdb(8), as all base system consumers of the legacy formatted
624 entries were converted to use the new format by default when the new,
625 machine independent format have been added and supported since FreeBSD
628 Please see the pwd_mkdb(8) manual page for further details.
631 Clang and llvm have been upgraded to 3.6.1 release. Please see the
632 20141231 entry below for information about prerequisites and upgrading,
633 if you are not already using 3.5.0 or higher.
636 TI platform code switched to using vendor DTS files and this update
637 may break existing systems running on Beaglebone, Beaglebone Black,
640 - dtb files should be regenerated/reinstalled. Filenames are the
641 same but content is different now
642 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
643 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
644 addressing scheme is now pin 25 on /dev/gpioc3.
645 - Pandaboard: /etc/ttys should be updated, serial console device is
646 now /dev/ttyu2, not /dev/ttyu0
649 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
650 If you need the GNU extension from groff soelim(1), install groff
651 from package: pkg install groff, or via ports: textproc/groff.
654 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
655 defined in symlink(7); previously symlinks were silently ignored.
658 The const qualifier has been removed from iconv(3) to comply with
659 POSIX. The ports tree is aware of this from r384038 onwards.
662 Libraries specified by LIBADD in Makefiles must have a corresponding
663 DPADD_<lib> variable to ensure correct dependencies. This is now
664 enforced in src.libnames.mk.
667 From legacy ata(4) driver was removed support for SATA controllers
668 supported by more functional drivers ahci(4), siis(4) and mvs(4).
669 Kernel modules ataahci and ataadaptec were removed completely,
670 replaced by ahci and mvs modules respectively.
673 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
674 the 20141231 entry below for information about prerequisites and
675 upgrading, if you are not already using 3.5.0 or higher.
678 The 32-bit PowerPC kernel has been changed to a position-independent
679 executable. This can only be booted with a version of loader(8)
680 newer than January 31, 2015, so make sure to update both world and
681 kernel before rebooting.
684 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
685 but before r278950, the RNG was not seeded properly. Immediately
686 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
687 ssh keys or openssl keys) that were generated w/ a kernel from that
688 range. This does not affect programs that directly used /dev/random
689 or /dev/urandom. All userland uses of arc4random(3) are affected.
692 The autofs(4) ABI was changed in order to restore binary compatibility
693 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
697 The powerpc64 kernel has been changed to a position-independent
698 executable. This can only be booted with a new version of loader(8),
699 so make sure to update both world and kernel before rebooting.
702 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
703 only release, no new features have been added. Please see the 20141231
704 entry below for information about prerequisites and upgrading, if you
705 are not already using 3.5.0.
708 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
709 taken from the ELF Tool Chain project rather than GNU binutils. They
710 should be drop-in replacements, with the addition of arm64 support.
711 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
712 binutils tools, if necessary. See 20150805 for updated information.
715 The default Unbound configuration now enables remote control
716 using a local socket. Users who have already enabled the
717 local_unbound service should regenerate their configuration
718 by running "service local_unbound setup" as root.
721 The GNU texinfo and GNU info pages have been removed.
722 To be able to view GNU info pages please install texinfo from ports.
725 Clang, llvm and lldb have been upgraded to 3.5.0 release.
727 As of this release, a prerequisite for building clang, llvm and lldb is
728 a C++11 capable compiler and C++11 standard library. This means that to
729 be able to successfully build the cross-tools stage of buildworld, with
730 clang as the bootstrap compiler, your system compiler or cross compiler
731 should either be clang 3.3 or later, or gcc 4.8 or later, and your
732 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
735 On any standard FreeBSD 10.x or 11.x installation, where clang and
736 libc++ are on by default (that is, on x86 or arm), this should work out
739 On 9.x installations where clang is enabled by default, e.g. on x86 and
740 powerpc, libc++ will not be enabled by default, so libc++ should be
741 built (with clang) and installed first. If both clang and libc++ are
742 missing, build clang first, then use it to build libc++.
744 On 8.x and earlier installations, upgrade to 9.x first, and then follow
745 the instructions for 9.x above.
747 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
748 default, and do not build clang.
750 Many embedded systems are resource constrained, and will not be able to
751 build clang in a reasonable time, or in some cases at all. In those
752 cases, cross building bootable systems on amd64 is a workaround.
754 This new version of clang introduces a number of new warnings, of which
755 the following are most likely to appear:
759 This warns in two cases, for both C and C++:
760 * When the code is trying to take the absolute value of an unsigned
761 quantity, which is effectively a no-op, and almost never what was
762 intended. The code should be fixed, if at all possible. If you are
763 sure that the unsigned quantity can be safely cast to signed, without
764 loss of information or undefined behavior, you can add an explicit
765 cast, or disable the warning.
767 * When the code is trying to take an absolute value, but the called
768 abs() variant is for the wrong type, which can lead to truncation.
769 If you want to disable the warning instead of fixing the code, please
770 make sure that truncation will not occur, or it might lead to unwanted
773 -Wtautological-undefined-compare and
774 -Wundefined-bool-conversion
776 These warn when C++ code is trying to compare 'this' against NULL, while
777 'this' should never be NULL in well-defined C++ code. However, there is
778 some legacy (pre C++11) code out there, which actively abuses this
779 feature, which was less strictly defined in previous C++ versions.
781 Squid and openjdk do this, for example. The warning can be turned off
782 for C++98 and earlier, but compiling the code in C++11 mode might result
783 in unexpected behavior; for example, the parts of the program that are
784 unreachable could be optimized away.
787 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
788 kernel sources have been removed. The .h files remain, since some
789 utilities include them. This will need to be fixed later.
790 If "mount -t oldnfs ..." is attempted, it will fail.
791 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
792 the utilities will report errors.
795 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
796 directories to top level SUBDIR variable when their parent
797 directory is included in LOCAL_DIRS. Users with build systems with
798 such hierarchies and without SUBDIR entries in the parent
799 directory Makefiles should add them or add the directories to
803 faith(4) and faithd(8) have been removed from the base system. Faith
804 has been obsolete for a very long time.
807 vt(4), the new console driver, is enabled by default. It brings
808 support for Unicode and double-width characters, as well as
809 support for UEFI and integration with the KMS kernel video
812 You may need to update your console settings in /etc/rc.conf,
813 most probably the keymap. During boot, /etc/rc.d/syscons will
814 indicate what you need to do.
816 vt(4) still has issues and lacks some features compared to
817 syscons(4). See the wiki for up-to-date information:
818 https://wiki.freebsd.org/Newcons
820 If you want to keep using syscons(4), you can do so by adding
821 the following line to /boot/loader.conf:
825 pjdfstest has been integrated into kyua as an opt-in test suite.
826 Please see share/doc/pjdfstest/README for more details on how to
830 gperf has been removed from the base system for architectures
831 that use clang. Ports that require gperf will obtain it from the
835 pjdfstest has been moved from tools/regression/pjdfstest to
839 At svn r271982, The default linux compat kernel ABI has been adjusted
840 to 2.6.18 in support of the linux-c6 compat ports infrastructure
841 update. If you wish to continue using the linux-f10 compat ports,
842 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
843 encouraged to update their linux-compat packages to linux-c6 during
844 their next update cycle.
847 The ofwfb driver, used to provide a graphics console on PowerPC when
848 using vt(4), no longer allows mmap() of all physical memory. This
849 will prevent Xorg on PowerPC with some ATI graphics cards from
850 initializing properly unless x11-servers/xorg-server is updated to
854 The xdev targets have been converted to using TARGET and
855 TARGET_ARCH instead of XDEV and XDEV_ARCH.
858 The default unbound configuration has been modified to address
859 issues with reverse lookups on networks that use private
860 address ranges. If you use the local_unbound service, run
861 "service local_unbound setup" as root to regenerate your
862 configuration, then "service local_unbound reload" to load the
866 The GNU texinfo and GNU info pages are not built and installed
867 anymore, WITH_INFO knob has been added to allow to built and install
869 UPDATE: see 20150102 entry on texinfo's removal
872 The GNU readline library is now an INTERNALLIB - that is, it is
873 statically linked into consumers (GDB and variants) in the base
874 system, and the shared library is no longer installed. The
875 devel/readline port is available for third party software that
879 The Itanium architecture (ia64) has been removed from the list of
880 known architectures. This is the first step in the removal of the
884 Commit r268115 has added NFSv4.1 server support, merged from
885 projects/nfsv4.1-server. Since this includes changes to the
886 internal interfaces between the NFS related modules, a full
887 build of the kernel and modules will be necessary.
888 __FreeBSD_version has been bumped.
891 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
892 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
893 which differs from the behaviour controlled by this knob.)
896 Maximal length of the serial number in CTL was increased from 16 to
897 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
898 and ctld, need to be rebuilt to work with a new kernel.
901 The libatf-c and libatf-c++ major versions were downgraded to 0 and
902 1 respectively to match the upstream numbers. They were out of
903 sync because, when they were originally added to FreeBSD, the
904 upstream versions were not respected. These libraries are private
905 and not yet built by default, so renumbering them should be a
906 non-issue. However, unclean source trees will yield broken test
907 programs once the operator executes "make delete-old-libs" after a
910 Additionally, the atf-sh binary was made private by moving it into
911 /usr/libexec/. Already-built shell test programs will keep the
912 path to the old binary so they will break after "make delete-old"
915 If you are using WITH_TESTS=yes (not the default), wipe the object
916 tree and rebuild from scratch to prevent spurious test failures.
917 This is only needed once: the misnumbered libraries and misplaced
918 binaries have been added to OptionalObsoleteFiles.inc so they will
919 be removed during a clean upgrade.
922 Clang and llvm have been upgraded to 3.4.1 release.
925 We bogusly installed src.opts.mk in /usr/share/mk. This file should
926 be removed to avoid issues in the future (and has been added to
930 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
931 past, it affected all builds that used the bsd.*.mk files. The old
932 behavior was a bug, but people may have relied upon it. To get this
933 behavior back, you can .include /etc/src.conf from /etc/make.conf
934 (which is still global and isn't changed). This also changes the
935 behavior of incremental builds inside the tree of individual
936 directories. Set MAKESYSPATH to ".../share/mk" to do that.
937 Although this has survived make universe and some upgrade scenarios,
938 other upgrade scenarios may have broken. At least one form of
939 temporary breakage was fixed with MAKESYSPATH settings for buildworld
940 as well... In cases where MAKESYSPATH isn't working with this
941 setting, you'll need to set it to the full path to your tree.
943 One side effect of all this cleaning up is that bsd.compiler.mk
944 is no longer implicitly included by bsd.own.mk. If you wish to
945 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
949 The lindev device has been removed since /dev/full has been made a
950 standard device. __FreeBSD_version has been bumped.
953 The knob WITHOUT_VI was added to the base system, which controls
954 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
955 in order to reorder files share/termcap and didn't build ex(1) as a
956 build tool, so building/installing with WITH_VI is highly advised for
957 build hosts for older releases.
959 This issue has been fixed in stable/9 and stable/10 in r277022 and
960 r276991, respectively.
963 The YES_HESIOD knob has been removed. It has been obsolete for
964 a decade. Please move to using WITH_HESIOD instead or your builds
965 will silently lack HESIOD.
968 The uart(4) driver has been changed with respect to its handling
969 of the low-level console. Previously the uart(4) driver prevented
970 any process from changing the baudrate or the CLOCAL and HUPCL
971 control flags. By removing the restrictions, operators can make
972 changes to the serial console port without having to reboot.
973 However, when getty(8) is started on the serial device that is
974 associated with the low-level console, a misconfigured terminal
975 line in /etc/ttys will now have a real impact.
976 Before upgrading the kernel, make sure that /etc/ttys has the
977 serial console device configured as 3wire without baudrate to
978 preserve the previous behaviour. E.g:
979 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
982 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
983 to improve performance. To re-enable it, if needed, run rpcbind
984 with command line option -W.
987 Switched back to the GPL dtc compiler due to updates in the upstream
988 dts files not being supported by the BSDL dtc compiler. You will need
989 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
990 may result while building dtb files during a kernel build if you fail
991 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
994 Clang and llvm have been upgraded to 3.4 release.
997 The nve(4) driver has been removed. Please use the nfe(4) driver
998 for NVIDIA nForce MCP Ethernet adapters instead.
1001 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1002 This could cause certain C++ applications using shared libraries built
1003 against the previous version of libc++ to crash. The incompatibility
1004 has now been fixed, but any C++ applications or shared libraries built
1005 between r261283 and r261801 should be recompiled.
1008 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1009 capability mode support. Please note that enabling the feature in
1010 kernel is still highly recommended.
1013 OpenSSH is now built with sandbox support, and will use sandbox as
1014 the default privilege separation method. This requires Capsicum
1015 capability mode support in kernel.
1018 The libelf and libdwarf libraries have been updated to newer
1019 versions from upstream. Shared library version numbers for
1020 these two libraries were bumped. Any ports or binaries
1021 requiring these two libraries should be recompiled.
1022 __FreeBSD_version is bumped to 1100006.
1025 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1026 instead of providing an explicit one, this would prevent such
1027 Makefile from providing its own Kyuafile in the future during
1028 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1029 intervention is needed to clean an objdir if you use NO_CLEAN:
1030 # find /usr/obj -name Kyuafile | xargs rm -f
1033 The behavior of gss_pseudo_random() for the krb5 mechanism
1034 has changed, for applications requesting a longer random string
1035 than produced by the underlying enctype's pseudo-random() function.
1036 In particular, the random string produced from a session key of
1037 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1038 be different at the 17th octet and later, after this change.
1039 The counter used in the PRF+ construction is now encoded as a
1040 big-endian integer in accordance with RFC 4402.
1041 __FreeBSD_version is bumped to 1100004.
1044 The WITHOUT_ATF build knob has been removed and its functionality
1045 has been subsumed into the more generic WITHOUT_TESTS. If you were
1046 using the former to disable the build of the ATF libraries, you
1047 should change your settings to use the latter.
1050 The default version of mtree is nmtree which is obtained from
1051 NetBSD. The output is generally the same, but may vary
1052 slightly. If you found you need identical output adding
1053 "-F freebsd9" to the command line should do the trick. For the
1054 time being, the old mtree is available as fmtree.
1057 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1058 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1059 1.1.4_8 and verify bsdyml not linked in, before running "make
1061 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1063 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1066 The stable/10 branch has been created in subversion from head
1070 The rc.d/jail script has been updated to support jail(8)
1071 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1072 for per-jail configuration are automatically converted to
1073 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1074 This is transparently backward compatible. See below about some
1075 incompatibilities and rc.conf(5) manual page for more details.
1077 These variables are now deprecated in favor of jail(8) configuration
1078 file. One can use "rc.d/jail config <jname>" command to generate
1079 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1080 running the jail(8) utility. The default pathname of the
1081 configuration file is /etc/jail.conf and can be specified by
1082 using $jail_conf or $jail_<jname>_conf variables.
1084 Please note that jail_devfs_ruleset accepts an integer at
1085 this moment. Please consider to rewrite the ruleset name
1089 BIND has been removed from the base system. If all you need
1090 is a local resolver, simply enable and start the local_unbound
1091 service instead. Otherwise, several versions of BIND are
1092 available in the ports tree. The dns/bind99 port is one example.
1094 With this change, nslookup(1) and dig(1) are no longer in the base
1095 system. Users should instead use host(1) and drill(1) which are
1096 in the base system. Alternatively, nslookup and dig can
1097 be obtained by installing the dns/bind-tools port.
1100 With the addition of unbound(8), a new unbound user is now
1101 required during installworld. "mergemaster -p" can be used to
1102 add the user prior to installworld, as documented in the handbook.
1105 OpenSSH is now built with DNSSEC support, and will by default
1106 silently trust signed SSHFP records. This can be controlled with
1107 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1108 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1111 The GNU Compiler Collection and C++ standard library (libstdc++)
1112 are no longer built by default on platforms where clang is the system
1113 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1114 options in src.conf.
1117 The PROCDESC kernel option is now part of the GENERIC kernel
1118 configuration and is required for the rwhod(8) to work.
1119 If you are using custom kernel configuration, you should include
1123 The API and ABI related to the Capsicum framework was modified
1124 in backward incompatible way. The userland libraries and programs
1125 have to be recompiled to work with the new kernel. This includes the
1126 following libraries and programs, but the whole buildworld is
1127 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1128 kdump, procstat, rwho, rwhod, uniq.
1131 AES-NI intrinsic support has been added to gcc. The AES-NI module
1132 has been updated to use this support. A new gcc is required to build
1133 the aesni module on both i386 and amd64.
1136 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1137 Thus "device padlock_rng" and "device rdrand_rng" should be
1138 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1141 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1142 enables just the iconv* functionality and is now on by default.
1143 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1144 compatibility. Set WITHOUT_ICONV to build the old way.
1145 If you have been using WITH_ICONV before, you will very likely
1146 need to turn on WITH_LIBICONV_COMPAT.
1149 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1150 Illumos origin, including ZFS. If you have INVARIANTS in your
1151 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1153 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1154 locks if WITNESS option was set. Because that generated a lot of
1155 witness(9) reports and all of them were believed to be false
1156 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1157 can be used to achieve the previous behavior.
1160 Timer values in IPv6 data structures now use time_uptime instead
1161 of time_second. Although this is not a user-visible functional
1162 change, userland utilities which directly use them---ndp(8),
1163 rtadvd(8), and rtsold(8) in the base system---need to be updated
1164 to r253970 or later.
1167 find -delete can now delete the pathnames given as arguments,
1168 instead of only files found below them or if the pathname did
1169 not contain any slashes. Formerly, the following error message
1172 find: -delete: <path>: relative path potentially not safe
1174 Deleting the pathnames given as arguments can be prevented
1175 without error messages using -mindepth 1 or by changing
1176 directory and passing "." as argument to find. This works in the
1177 old as well as the new version of find.
1180 Behavior of devfs rules path matching has been changed.
1181 Pattern is now always matched against fully qualified devfs
1182 path and slash characters must be explicitly matched by
1183 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1184 subdirectories must be reviewed.
1187 The default ARM ABI has changed to the ARM EABI. The old ABI is
1188 incompatible with the ARM EABI and all programs and modules will
1189 need to be rebuilt to work with a new kernel.
1191 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1193 NOTE: Support for the old ABI will be removed in the future and
1194 users are advised to upgrade.
1197 pkg_install has been disconnected from the build if you really need it
1198 you should add WITH_PKGTOOLS in your src.conf(5).
1201 Most of network statistics structures were changed to be able
1202 keep 64-bits counters. Thus all tools, that work with networking
1203 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1206 Fix a bug that allowed a tracing process (e.g. gdb) to write
1207 to a memory-mapped file in the traced process's address space
1208 even if neither the traced process nor the tracing process had
1209 write access to that file.
1212 CVS has been removed from the base system. An exact copy
1213 of the code is available from the devel/cvs port.
1216 Some people report the following error after the switch to bmake:
1218 make: illegal option -- J
1219 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1221 *** [buildworld] Error code 2
1223 this likely due to an old instance of make in
1224 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1225 which src/Makefile will use that blindly, if it exists, so if
1226 you see the above error:
1228 rm -rf `make -V MAKEPATH`
1233 Use bmake by default.
1234 Whereas before one could choose to build with bmake via
1235 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1236 make. The goal is to remove these knobs for 10-RELEASE.
1238 It is worth noting that bmake (like gmake) treats the command
1239 line as the unit of failure, rather than statements within the
1240 command line. Thus '(cd some/where && dosomething)' is safer
1241 than 'cd some/where; dosomething'. The '()' allows consistent
1242 behavior in parallel build.
1245 Fix a bug that allows NFS clients to issue READDIR on files.
1248 The WITHOUT_IDEA option has been removed because
1249 the IDEA patent expired.
1252 The sysctl which controls TRIM support under ZFS has been renamed
1253 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1257 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1258 rather than creating it's own in the temporary directory in
1259 order allow access to bootstrapped versions of tools such as
1260 install and mtree. When upgrading from version of FreeBSD where
1261 the install command does not support -l, you will need to
1262 install a new mergemaster command if mergemaster -p is required.
1263 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1267 Legacy ATA stack, disabled and replaced by new CAM-based one since
1268 FreeBSD 9.0, completely removed from the sources. Kernel modules
1269 atadisk and atapi*, user-level tools atacontrol and burncd are
1270 removed. Kernel option `options ATA_CAM` is now permanently enabled
1274 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1275 and socketpair(2). Software, in particular Kerberos, may
1276 automatically detect and use these during building. The resulting
1277 binaries will not work on older kernels.
1280 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1281 information, see the respective 20130304 entry).
1284 Recent commits to callout(9) changed the size of struct callout,
1285 so the KBI is probably heavily disturbed. Also, some functions
1286 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1287 by macros. Every kernel module using it won't load, so rebuild
1290 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1291 but does not initialize by default (because of the new CTL_DISABLE
1292 option) to save memory. To re-enable it, remove the CTL_DISABLE
1293 option from the kernel config file or set kern.cam.ctl.disable=0
1294 in /boot/loader.conf.
1297 The ctl device has been disabled in GENERIC for i386 and amd64.
1298 This was done due to the extra memory being allocated at system
1299 initialisation time by the ctl driver which was only used if
1300 a CAM target device was created. This makes a FreeBSD system
1301 unusable on 128MB or less of RAM.
1304 A new compression method (lz4) has been merged to -HEAD. Please
1305 refer to zpool-features(7) for more information.
1307 Please refer to the "ZFS notes" section of this file for information
1308 on upgrading boot ZFS pools.
1311 A BSD-licensed patch(1) variant has been added and is installed
1312 as bsdpatch, being the GNU version the default patch.
1313 To inverse the logic and use the BSD-licensed one as default,
1314 while having the GNU version installed as gnupatch, rebuild
1315 and install world with the WITH_BSD_PATCH knob set.
1318 Due to the use of the new -l option to install(1) during build
1319 and install, you must take care not to directly set the INSTALL
1320 make variable in your /etc/make.conf, /etc/src.conf, or on the
1321 command line. If you wish to use the -C flag for all installs
1322 you may be able to add INSTALL+=-C to /etc/make.conf or
1326 The install(1) option -M has changed meaning and now takes an
1327 argument that is a file or path to append logs to. In the
1328 unlikely event that -M was the last option on the command line
1329 and the command line contained at least two files and a target
1330 directory the first file will have logs appended to it. The -M
1331 option served little practical purpose in the last decade so its
1332 use is expected to be extremely rare.
1335 After switching to Clang as the default compiler some users of ZFS
1336 on i386 systems started to experience stack overflow kernel panics.
1337 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1340 GEOM_LABEL now mangles label names read from file system metadata.
1341 Mangling affect labels containing spaces, non-printable characters,
1342 '%' or '"'. Device names in /etc/fstab and other places may need to
1346 By default, only the 10 most recent kernel dumps will be saved. To
1347 restore the previous behaviour (no limit on the number of kernel dumps
1348 stored in the dump directory) add the following line to /etc/rc.conf:
1353 With the addition of auditdistd(8), a new auditdistd user is now
1354 required during installworld. "mergemaster -p" can be used to
1355 add the user prior to installworld, as documented in the handbook.
1358 The sin6_scope_id member variable in struct sockaddr_in6 is now
1359 filled by the kernel before passing the structure to the userland via
1360 sysctl or routing socket. This means the KAME-specific embedded scope
1361 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1362 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1363 __FreeBSD_version is bumped to 1000025.
1366 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1367 This means that the world and kernel will be compiled with clang
1368 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1369 and /usr/bin/cpp. To disable this behavior and revert to building
1370 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1371 of current may need to bootstrap WITHOUT_CLANG first if the clang
1372 build fails (its compatibility window doesn't extend to the 9 stable
1376 The IPFIREWALL_FORWARD kernel option has been removed. Its
1377 functionality now turned on by default.
1380 The ZERO_COPY_SOCKET kernel option has been removed and
1381 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1382 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1383 mechanism which is not safe and may result in kernel crashes.
1384 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1385 driver supports disposeable external page sized mbuf storage.
1386 Proper replacements for both zero-copy mechanisms are under
1387 consideration and will eventually lead to complete removal
1388 of the two kernel options.
1391 The IPv4 network stack has been converted to network byte
1392 order. The following modules need to be recompiled together
1393 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1394 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1397 Support for non-MPSAFE filesystems was removed from VFS. The
1398 VFS_VERSION was bumped, all filesystem modules shall be
1402 All the non-MPSAFE filesystems have been disconnected from
1403 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1404 portalfs, smbfs, xfs.
1407 The interface cloning API and ABI has changed. The following
1408 modules need to be recompiled together with kernel:
1409 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1410 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1411 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1414 The sdhci driver was split in two parts: sdhci (generic SD Host
1415 Controller logic) and sdhci_pci (actual hardware driver).
1416 No kernel config modifications are required, but if you
1417 load sdhc as a module you must switch to sdhci_pci instead.
1420 Import the FUSE kernel and userland support into base system.
1423 The GNU sort(1) program has been removed since the BSD-licensed
1424 sort(1) has been the default for quite some time and no serious
1425 problems have been reported. The corresponding WITH_GNU_SORT
1429 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1430 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1434 The net80211(4) ABI has been changed to allow for improved driver
1435 PS-POLL and power-save support. All wireless drivers need to be
1436 recompiled to work with the new kernel.
1439 The random(4) support for the VIA hardware random number
1440 generator (`PADLOCK') is no longer enabled unconditionally.
1441 Add the padlock_rng device in the custom kernel config if
1442 needed. The GENERIC kernels on i386 and amd64 do include the
1443 device, so the change only affects the custom kernel
1447 The pf(4) packet filter ABI has been changed. pfctl(8) and
1448 snmp_pf module need to be recompiled to work with new kernel.
1451 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1452 to -HEAD. Pools that have empty_bpobj in active state can not be
1453 imported read-write with ZFS implementations that do not support
1454 this feature. For more information read the zpool-features(5)
1458 The sparc64 ZFS loader has been changed to no longer try to auto-
1459 detect ZFS providers based on diskN aliases but now requires these
1460 to be explicitly listed in the OFW boot-device environment variable.
1463 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1464 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1465 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1468 The following sysctls and tunables have been renamed for consistency
1469 with other variables:
1470 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1471 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1474 The sort utility has been replaced with BSD sort. For now, GNU sort
1475 is also available as "gnusort" or the default can be set back to
1476 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1477 installed as "bsdsort".
1480 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1481 Starting with this version the old system of ZFS pool versioning
1482 is superseded by "feature flags". This concept enables forward
1483 compatibility against certain future changes in functionality of ZFS
1484 pools. The first read-only compatible "feature flag" for ZFS pools
1485 is named "com.delphix:async_destroy". For more information
1486 read the new zpool-features(5) manual page.
1487 Please refer to the "ZFS notes" section of this file for information
1488 on upgrading boot ZFS pools.
1491 The malloc(3) implementation embedded in libc now uses sources imported
1492 as contrib/jemalloc. The most disruptive API change is to
1493 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1494 delete it prior to installworld, and optionally re-create it using the
1495 new format after rebooting. See malloc.conf(5) for details
1496 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1500 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1501 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1502 now spelled mips. This is to aid compatibility with third-party
1503 software that expects this naming scheme in uname(3). Little-endian
1504 settings are unchanged. If you are updating a big-endian mips64 machine
1505 from before this change, you may need to set MACHINE_ARCH=mips64 in
1506 your environment before the new build system will recognize your machine.
1509 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1513 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1514 nullfs(5) did not pass through all behaviours to the underlying layer,
1515 as a result if we bound to a socket on the lower layer we could connect
1516 only to the lower path; if we bound to the upper layer we could connect
1517 only to the upper path. The new behavior is one can connect to both the
1518 lower and the upper paths regardless what layer path one binds to.
1521 The getifaddrs upgrade path broken with 20111215 has been restored.
1522 If you have upgraded in between 20111215 and 20120209 you need to
1523 recompile libc again with your kernel. You still need to recompile
1524 world to be able to configure CARP but this restriction already
1525 comes from 20111215.
1528 The set_rcvar() function has been removed from /etc/rc.subr. All
1529 base and ports rc.d scripts have been updated, so if you have a
1530 port installed with a script in /usr/local/etc/rc.d you can either
1531 hand-edit the rcvar= line, or reinstall the port.
1533 An easy way to handle the mass-update of /etc/rc.d:
1534 rm /etc/rc.d/* && mergemaster -i
1537 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1538 on the current CPU and prevents other threads from running.
1539 This behavior can be reverted using the kern.stop_scheduler_on_panic
1541 The new behavior can be incompatible with kern.sync_on_panic.
1544 The carp(4) facility has been changed significantly. Configuration
1545 of the CARP protocol via ifconfig(8) has changed, as well as format
1546 of CARP events submitted to devd(8) has changed. See manual pages
1547 for more information. The arpbalance feature of carp(4) is currently
1548 not supported anymore.
1550 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1551 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1552 need to be recompiled.
1555 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1559 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1560 explicitely support non-MPSAFE filesystems.
1561 It is on by default for all supported platform at this present
1565 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1566 i386 and pc98 GENERIC kernel configuration files.
1569 sysinstall has been removed
1572 The stable/9 branch created in subversion. This corresponds to the
1573 RELENG_9 branch in CVS.
1579 Avoid using make -j when upgrading. While generally safe, there are
1580 sometimes problems using -j to upgrade. If your upgrade fails with
1581 -j, please try again without -j. From time to time in the past there
1582 have been problems using -j with buildworld and/or installworld. This
1583 is especially true when upgrading between "distant" versions (eg one
1584 that cross a major release boundary or several minor releases, or when
1585 several months have passed on the -current branch).
1587 Sometimes, obscure build problems are the result of environment
1588 poisoning. This can happen because the make utility reads its
1589 environment when searching for values for global variables. To run
1590 your build attempts in an "environmental clean room", prefix all make
1591 commands with 'env -i '. See the env(1) manual page for more details.
1593 When upgrading from one major version to another it is generally best to
1594 upgrade to the latest code in the currently installed branch first, then
1595 do an upgrade to the new branch. This is the best-tested upgrade path,
1596 and has the highest probability of being successful. Please try this
1597 approach if you encounter problems with a major version upgrade. Since
1598 the stable 4.x branch point, one has generally been able to upgade from
1599 anywhere in the most recent stable branch to head / current (or even the
1600 last couple of stable branches). See the top of this file when there's
1603 When upgrading a live system, having a root shell around before
1604 installing anything can help undo problems. Not having a root shell
1605 around can lead to problems if pam has changed too much from your
1606 starting point to allow continued authentication after the upgrade.
1608 This file should be read as a log of events. When a later event changes
1609 information of a prior event, the prior event should not be deleted.
1610 Instead, a pointer to the entry with the new information should be
1611 placed in the old entry. Readers of this file should also sanity check
1612 older entries before relying on them blindly. Authors of new entries
1613 should write them with this in mind.
1617 When upgrading the boot ZFS pool to a new version, always follow
1620 1.) recompile and reinstall the ZFS boot loader and boot block
1621 (this is part of "make buildworld" and "make installworld")
1623 2.) update the ZFS boot block on your boot drive
1625 The following example updates the ZFS boot block on the first
1626 partition (freebsd-boot) of a GPT partitioned drive ada0:
1627 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1629 Non-boot pools do not need these updates.
1633 If you are updating from a prior version of FreeBSD (even one just
1634 a few days old), you should follow this procedure. It is the most
1635 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1637 make kernel-toolchain
1638 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1639 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1641 To test a kernel once
1642 ---------------------
1643 If you just want to boot a kernel once (because you are not sure
1644 if it works, or if you want to boot a known bad kernel to provide
1645 debugging information) run
1646 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1647 nextboot -k testkernel
1649 To just build a kernel when you know that it won't mess you up
1650 --------------------------------------------------------------
1651 This assumes you are already running a CURRENT system. Replace
1652 ${arch} with the architecture of your machine (e.g. "i386",
1653 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1655 cd src/sys/${arch}/conf
1656 config KERNEL_NAME_HERE
1657 cd ../compile/KERNEL_NAME_HERE
1662 If this fails, go to the "To build a kernel" section.
1664 To rebuild everything and install it on the current system.
1665 -----------------------------------------------------------
1666 # Note: sometimes if you are running current you gotta do more than
1667 # is listed here if you are upgrading from a really old current.
1669 <make sure you have good level 0 dumps>
1671 make kernel KERNCONF=YOUR_KERNEL_HERE
1673 <reboot in single user> [3]
1680 To cross-install current onto a separate partition
1681 --------------------------------------------------
1682 # In this approach we use a separate partition to hold
1683 # current's root, 'usr', and 'var' directories. A partition
1684 # holding "/", "/usr" and "/var" should be about 2GB in
1687 <make sure you have good level 0 dumps>
1690 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1691 <maybe newfs current's root partition>
1692 <mount current's root partition on directory ${CURRENT_ROOT}>
1693 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1694 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1695 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1696 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1697 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1698 <reboot into current>
1699 <do a "native" rebuild/install as described in the previous section>
1700 <maybe install compatibility libraries from ports/misc/compat*>
1704 To upgrade in-place from stable to current
1705 ----------------------------------------------
1706 <make sure you have good level 0 dumps>
1708 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1710 <reboot in single user> [3]
1717 Make sure that you've read the UPDATING file to understand the
1718 tweaks to various things you need. At this point in the life
1719 cycle of current, things change often and you are on your own
1720 to cope. The defaults can also change, so please read ALL of
1721 the UPDATING entries.
1723 Also, if you are tracking -current, you must be subscribed to
1724 freebsd-current@freebsd.org. Make sure that before you update
1725 your sources that you have read and understood all the recent
1726 messages there. If in doubt, please track -stable which has
1727 much fewer pitfalls.
1729 [1] If you have third party modules, such as vmware, you
1730 should disable them at this point so they don't crash your
1733 [3] From the bootblocks, boot -s, and then do
1738 adjkerntz -i # if CMOS is wall time
1739 Also, when doing a major release upgrade, it is required that
1740 you boot into single user mode to do the installworld.
1742 [4] Note: This step is non-optional. Failure to do this step
1743 can result in a significant reduction in the functionality of the
1744 system. Attempting to do it by hand is not recommended and those
1745 that pursue this avenue should read this file carefully, as well
1746 as the archives of freebsd-current and freebsd-hackers mailing lists
1747 for potential gotchas. The -U option is also useful to consider.
1748 See mergemaster(8) for more information.
1750 [5] Usually this step is a noop. However, from time to time
1751 you may need to do this if you get unknown user in the following
1752 step. It never hurts to do it all the time. You may need to
1753 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1754 install) after the buildworld before this step if you last updated
1755 from current before 20130425 or from -stable before 20130430.
1757 [6] This only deletes old files and directories. Old libraries
1758 can be deleted by "make delete-old-libs", but you have to make
1759 sure that no program is using those libraries anymore.
1761 [8] In order to have a kernel that can run the 4.x binaries needed to
1762 do an installworld, you must include the COMPAT_FREEBSD4 option in
1763 your kernel. Failure to do so may leave you with a system that is
1764 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1765 required to run the 5.x binaries on more recent kernels. And so on
1766 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1768 Make sure that you merge any new devices from GENERIC since the
1769 last time you updated your kernel config file.
1771 [9] When checking out sources, you must include the -P flag to have
1772 cvs prune empty directories.
1774 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1775 "?=" instead of the "=" assignment operator, so that buildworld can
1776 override the CPUTYPE if it needs to.
1778 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1779 not on the command line, or in /etc/make.conf. buildworld will
1780 warn if it is improperly defined.
1783 This file contains a list, in reverse chronological order, of major
1784 breakages in tracking -current. It is not guaranteed to be a complete
1785 list of such breakages, and only contains entries since September 23, 2011.
1786 If you need to see UPDATING entries from before that date, you will need
1787 to fetch an UPDATING file from an older FreeBSD release.
1789 Copyright information:
1791 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1793 Redistribution, publication, translation and use, with or without
1794 modification, in full or in part, in any form or format of this
1795 document are permitted without further permission from the author.
1797 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1798 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1799 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1800 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1801 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1802 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1803 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1804 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1805 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1806 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1807 POSSIBILITY OF SUCH DAMAGE.
1809 Contact Warner Losh if you have any questions about your use of