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 The syntax of ipfw(8) named states was changed to avoid ambiguity.
56 If you have used named states in the firewall rules, you need to modify
57 them after installworld and before rebooting. Now named states must
58 be prefixed with colon.
61 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
62 removed as the userland we provide cannot use them. The KMS version
63 (sys/dev/drm2) support the same hardware.
66 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
67 diff has not been implemented, if those are needed a newer version of
68 GNU diff is available via the diffutils package under the gdiff name.
71 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
72 Please see the 20141231 entry below for information about prerequisites
73 and upgrading, if you are not already using clang 3.5.0 or higher.
76 The code that provides support for ZFS .zfs/ directory functionality
77 has been reimplemented. It's not possible now to create a snapshot
78 by mkdir under .zfs/snapshot/. That should be the only user visible
82 EISA bus support has been removed. The WITH_EISA option is no longer
86 MCA bus support has been removed.
89 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
90 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
93 The EM_MULTIQUEUE kernel configuration option is deprecated now that
94 the em(4) driver conforms to iflib specifications.
97 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
98 IFLIB. If you have a custom kernel configuration that excludes em(4)
99 but you use igb(4), you need to re-add em(4) to your custom configuration.
102 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
103 Please see the 20141231 entry below for information about prerequisites
104 and upgrading, if you are not already using clang 3.5.0 or higher.
107 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
108 Please see the 20141231 entry below for information about prerequisites
109 and upgrading, if you are not already using clang 3.5.0 or higher.
112 The layout of the pmap structure has changed for powerpc to put the pmap
113 statistics at the front for all CPU variations. libkvm(3) and all tools
114 that link against it need to be recompiled.
117 isl(4) and cyapa(4) drivers now require a new driver,
118 chromebook_platform(4), to work properly on Chromebook-class hardware.
119 On other types of hardware the drivers may need to be configured using
120 device hints. Please see the corresponding manual pages for details.
123 The urtwn(4) driver was merged into rtwn(4) and now consists of
124 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
126 Also, firmware for RTL8188CE was renamed due to possible name
127 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
130 GNU rcs has been removed from base. It is available as packages:
131 - rcs: Latest GPLv3 GNU rcs version.
132 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
136 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
137 modules now requires that the kernel configuration contain the
138 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
141 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
142 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
145 Relocatable object files with the extension of .So have been renamed
146 to use an extension of .pico instead. The purpose of this change is
147 to avoid a name clash with shared libraries on case-insensitive file
148 systems. On those file systems, foo.So is the same file as foo.so.
151 GNU rcs has been turned off by default. It can (temporarily) be built
152 again by adding WITH_RCS knob in src.conf.
153 Otherwise, GNU rcs is available from packages:
154 - rcs: Latest GPLv3 GNU rcs version.
155 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
158 The backup_uses_rcs functionality has been removed from rc.subr.
161 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
162 two separate components, QUEUE_MACRO_DEBUG_TRACE and
163 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
164 QUEUE_MACRO_DEBUG behavior.
167 r304787 changed some ioctl interfaces between the iSCSI userspace
168 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
169 rebuilt to work with new kernels. __FreeBSD_version has been bumped
173 The UDP receive code has been updated to only treat incoming UDP
174 packets that were addressed to an L2 broadcast address as L3
175 broadcast packets. It is not expected that this will affect any
176 standards-conforming UDP application. The new behaviour can be
177 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
181 Remove the openbsd_poll system call.
182 __FreeBSD_version has been bumped because of this.
185 The libc stub for the pipe(2) system call has been replaced with
186 a wrapper that calls the pipe2(2) system call and the pipe(2)
187 system call is now only implemented by the kernels that include
188 "options COMPAT_FREEBSD10" in their config file (this is the
189 default). Users should ensure that this option is enabled in
190 their kernel or upgrade userspace to r302092 before upgrading their
194 CAM will now strip leading spaces from SCSI disks' serial numbers.
195 This will affect users who create UFS filesystems on SCSI disks using
196 those disk's diskid device nodes. For example, if /etc/fstab
197 previously contained a line like
198 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
199 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
200 transforms like gmirror may also be affected. ZFS users should
204 The bitstring(3) API has been updated with new functionality and
205 improved performance. But it is binary-incompatible with the old API.
206 Objects built with the new headers may not be linked against objects
207 built with the old headers.
210 The brk and sbrk functions have been removed from libc on arm64.
211 Binutils from ports has been updated to not link to these
212 functions and should be updated to the latest version before
213 installing a new libc.
216 The armv6 port now defaults to hard float ABI. Limited support
217 for running both hardfloat and soft float on the same system
218 is available using the libraries installed with -DWITH_LIBSOFT.
219 This has only been tested as an upgrade path for installworld
220 and packages may fail or need manual intervention to run. New
221 packages will be needed.
223 To update an existing self-hosted armv6hf system, you must add
224 TARGET_ARCH=armv6 on the make command line for both the build
225 and the install steps.
228 Kernel modules compiled outside of a kernel build now default to
229 installing to /boot/modules instead of /boot/kernel. Many kernel
230 modules built this way (such as those in ports) already overrode
231 KMODDIR explicitly to install into /boot/modules. However,
232 manually building and installing a module from /sys/modules will
233 now install to /boot/modules instead of /boot/kernel.
236 The CAM I/O scheduler has been committed to the kernel. There should be
237 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
238 list of known rogues that claim support for this but actually corrupt
239 data is believed to be complete, be on the lookout for data
240 corruption. The known rogue list is believed to be complete:
242 o Crucial MX100, M550 drives with MU01 firmware.
243 o Micron M510 and M550 drives with MU01 firmware.
244 o Micron M500 prior to MU07 firmware
245 o Samsung 830, 840, and 850 all firmwares
246 o FCCT M500 all firmwares
248 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
249 with working NCQ TRIM. For Micron branded drives, see your sales rep for
250 updated firmware. Black listed drives will work correctly because these
251 drives work correctly so long as no NCQ TRIMs are sent to them. Given
252 this list is the same as found in Linux, it's believed there are no
253 other rogues in the market place. All other models from the above
256 To be safe, if you are at all concerned, you can quirk each of your
257 drives to prevent NCQ from being sent by setting:
258 kern.cam.ada.X.quirks="0x2"
259 in loader.conf. If the drive requires the 4k sector quirk, set the
263 The FAST_DEPEND build option has been removed and its functionality is
264 now the one true way. The old mkdep(1) style of 'make depend' has
265 been removed. See 20160311 for further details.
268 Resource range types have grown from unsigned long to uintmax_t. All
269 drivers, and anything using libdevinfo, need to be recompiled.
272 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
273 builds. It no longer runs mkdep(1) during 'make depend', and the
274 'make depend' stage can safely be skipped now as it is auto ran
275 when building 'make all' and will generate all SRCS and DPSRCS before
276 building anything else. Dependencies are gathered at compile time with
277 -MF flags kept in separate .depend files per object file. Users should
278 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
282 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
283 kernel modules. Therefore, if you load any kernel modules at boot time,
284 please install the boot loaders after you install the kernel, but before
288 make kernel KERNCONF=YOUR_KERNEL_HERE
289 make -C sys/boot install
290 <reboot in single user>
292 Then follow the usual steps, described in the General Notes section,
296 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
297 see the 20141231 entry below for information about prerequisites and
298 upgrading, if you are not already using clang 3.5.0 or higher.
301 The AIO subsystem is now a standard part of the kernel. The
302 VFS_AIO kernel option and aio.ko kernel module have been removed.
303 Due to stability concerns, asynchronous I/O requests are only
304 permitted on sockets and raw disks by default. To enable
305 asynchronous I/O requests on all file types, set the
306 vfs.aio.enable_unsafe sysctl to a non-zero value.
309 The ELF object manipulation tool objcopy is now provided by the
310 ELF Tool Chain project rather than by GNU binutils. It should be a
311 drop-in replacement, with the addition of arm64 support. The
312 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
313 to obtain the GNU version if necessary.
316 Building ZFS pools on top of zvols is prohibited by default. That
317 feature has never worked safely; it's always been prone to deadlocks.
318 Using a zvol as the backing store for a VM guest's virtual disk will
319 still work, even if the guest is using ZFS. Legacy behavior can be
320 restored by setting vfs.zfs.vol.recursive=1.
323 The NONE and HPN patches has been removed from OpenSSH. They are
324 still available in the security/openssh-portable port.
327 With the addition of ypldap(8), a new _ypldap user is now required
328 during installworld. "mergemaster -p" can be used to add the user
329 prior to installworld, as documented in the handbook.
332 The tftp loader (pxeboot) now uses the option root-path directive. As a
333 consequence it no longer looks for a pxeboot.4th file on the tftp
334 server. Instead it uses the regular /boot infrastructure as with the
338 The code to start recording plug and play data into the modules has
339 been committed. While the old tools will properly build a new kernel,
340 a number of warnings about "unknown metadata record 4" will be produced
341 for an older kldxref. To avoid such warnings, make sure to rebuild
342 the kernel toolchain (or world). Make sure that you have r292078 or
343 later when trying to build 292077 or later before rebuilding.
346 Debug data files are now built by default with 'make buildworld' and
347 installed with 'make installworld'. This facilitates debugging but
348 requires more disk space both during the build and for the installed
349 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
353 r291527 changed the internal interface between the nfsd.ko and
354 nfscommon.ko modules. As such, they must both be upgraded to-gether.
355 __FreeBSD_version has been bumped because of this.
358 Add support for unicode collation strings leads to a change of
359 order of files listed by ls(1) for example. To get back to the old
360 behaviour, set LC_COLLATE environment variable to "C".
362 Databases administrators will need to reindex their databases given
363 collation results will be different.
365 Due to a bug in install(1) it is recommended to remove the ancient
366 locales before running make installworld.
368 rm -rf /usr/share/locale/*
371 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
372 libcrypto.so.7 or libssl.so.7 must be recompiled.
375 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
376 Kernel modules isp_2400_multi and isp_2500_multi were removed and
377 should be replaced with isp_2400 and isp_2500 modules respectively.
380 The build previously allowed using 'make -n' to not recurse into
381 sub-directories while showing what commands would be executed, and
382 'make -n -n' to recursively show commands. Now 'make -n' will recurse
383 and 'make -N' will not.
386 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
387 and etcupdate will now use this file. A custom sendmail.cf is now
388 updated via this mechanism rather than via installworld. If you had
389 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
390 want to remove the exclusion or change it to "always install".
391 /etc/mail/sendmail.cf is now managed the same way regardless of
392 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
393 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
396 Compatibility shims for legacy ATA device names have been removed.
397 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
398 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
399 environment variables, /dev/ad* and /dev/ar* symbolic links.
402 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
403 Please see the 20141231 entry below for information about prerequisites
404 and upgrading, if you are not already using clang 3.5.0 or higher.
407 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
408 and renamed from .symbols to .debug. This reduces the size requirements
409 on the boot partition or file system and provides consistency with
410 userland debug files.
412 When using the supported kernel installation method the
413 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
414 as is done with /boot/kernel.
416 Developers wishing to maintain the historical behavior of installing
417 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
420 The wireless drivers had undergone changes that remove the 'parent
421 interface' from the ifconfig -l output. The rc.d network scripts
422 used to check presence of a parent interface in the list, so old
423 scripts would fail to start wireless networking. Thus, etcupdate(3)
424 or mergemaster(8) run is required after kernel update, to update your
425 rc.d scripts in /etc.
428 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
429 These configurations are now automatically interpreted as
430 'scrub fragment reassemble'.
433 Kernel-loadable modules for the random(4) device are back. To use
434 them, the kernel must have
437 options RANDOM_LOADABLE
439 kldload(8) can then be used to load random_fortuna.ko
440 or random_yarrow.ko. Please note that due to the indirect
441 function calls that the loadable modules need to provide,
442 the build-in variants will be slightly more efficient.
444 The random(4) kernel option RANDOM_DUMMY has been retired due to
445 unpopularity. It was not all that useful anyway.
448 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
449 Control over building the ELF Tool Chain tools is now provided by
450 the WITHOUT_TOOLCHAIN knob.
453 The polarity of Pulse Per Second (PPS) capture events with the
454 uart(4) driver has been corrected. Prior to this change the PPS
455 "assert" event corresponded to the trailing edge of a positive PPS
456 pulse and the "clear" event was the leading edge of the next pulse.
458 As the width of a PPS pulse in a typical GPS receiver is on the
459 order of 1 millisecond, most users will not notice any significant
460 difference with this change.
462 Anyone who has compensated for the historical polarity reversal by
463 configuring a negative offset equal to the pulse width will need to
464 remove that workaround.
467 The default group assigned to /dev/dri entries has been changed
468 from 'wheel' to 'video' with the id of '44'. If you want to have
469 access to the dri devices please add yourself to the video group
472 # pw groupmod video -m $USER
475 The menu.rc and loader.rc files will now be replaced during
476 upgrades. Please migrate local changes to menu.rc.local and
477 loader.rc.local instead.
480 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
481 strings and strip have been removed. The src.conf(5) knob
482 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
485 As ZFS requires more kernel stack pages than is the default on some
486 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
487 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
489 Please consider using 'options KSTACK_PAGES=X' where X is greater
490 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
493 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
494 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
495 default, i.e., they will not contain "::". For example, instead
496 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
497 to have a more specific match, such as different map entries for
498 IPv6:0:0 vs IPv6:0. This change requires that configuration
499 data (including maps, files, classes, custom ruleset, etc.) must
500 use the same format, so make certain such configuration data is
501 upgrading. As a very simple check search for patterns like
502 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
503 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
504 the cf option UseCompressedIPv6Addresses.
507 The default kernel entropy-processing algorithm is now
508 Fortuna, replacing Yarrow.
510 Assuming you have 'device random' in your kernel config
511 file, the configurations allow a kernel option to override
512 this default. You may choose *ONE* of:
514 options RANDOM_YARROW # Legacy /dev/random algorithm.
515 options RANDOM_DUMMY # Blocking-only driver.
517 If you have neither, you get Fortuna. For most people,
518 read no further, Fortuna will give a /dev/random that works
519 like it always used to, and the difference will be irrelevant.
521 If you remove 'device random', you get *NO* kernel-processed
522 entropy at all. This may be acceptable to folks building
523 embedded systems, but has complications. Carry on reading,
524 and it is assumed you know what you need.
526 *PLEASE* read random(4) and random(9) if you are in the
527 habit of tweaking kernel configs, and/or if you are a member
528 of the embedded community, wanting specific and not-usual
529 behaviour from your security subsystems.
531 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
532 random', you will NOT have a functioning /dev/random, and
533 many cryptographic features will not work, including SSH.
534 You may also find strange behaviour from the random(3) set
535 of library functions, in particular sranddev(3), srandomdev(3)
536 and arc4random(3). The reason for this is that the KERN_ARND
537 sysctl only returns entropy if it thinks it has some to
538 share, and with RANDOM_DUMMY or no 'device random' this
542 An additional fix for the issue described in the 20150614 sendmail
543 entry below has been been committed in revision 284717.
546 FreeBSD's old make (fmake) has been removed from the system. It is
547 available as the devel/fmake port or via pkg install fmake.
550 The fix for the issue described in the 20150614 sendmail entry
551 below has been been committed in revision 284436. The work
552 around described in that entry is no longer needed unless the
553 default setting is overridden by a confDH_PARAMETERS configuration
554 setting of '5' or pointing to a 512 bit DH parameter file.
557 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
558 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
559 and devel/kyua to version 0.20+ and adjust any calling code to work
560 with Kyuafile and kyua.
563 The import of openssl to address the FreeBSD-SA-15:10.openssl
564 security advisory includes a change which rejects handshakes
565 with DH parameters below 768 bits. sendmail releases prior
566 to 8.15.2 (not yet released), defaulted to a 512 bit
567 DH parameter setting for client connections. To work around
568 this interoperability, sendmail can be configured to use a
569 2048 bit DH parameter by:
571 1. Edit /etc/mail/`hostname`.mc
572 2. If a setting for confDH_PARAMETERS does not exist or
573 exists and is set to a string beginning with '5',
575 3. If a setting for confDH_PARAMETERS exists and is set to
576 a file path, create a new file with:
577 openssl dhparam -out /path/to/file 2048
578 4. Rebuild the .cf file:
579 cd /etc/mail/; make; make install
581 cd /etc/mail/; make restart
583 A sendmail patch is coming, at which time this file will be
587 Generation of legacy formatted entries have been disabled by default
588 in pwd_mkdb(8), as all base system consumers of the legacy formatted
589 entries were converted to use the new format by default when the new,
590 machine independent format have been added and supported since FreeBSD
593 Please see the pwd_mkdb(8) manual page for further details.
596 Clang and llvm have been upgraded to 3.6.1 release. Please see the
597 20141231 entry below for information about prerequisites and upgrading,
598 if you are not already using 3.5.0 or higher.
601 TI platform code switched to using vendor DTS files and this update
602 may break existing systems running on Beaglebone, Beaglebone Black,
605 - dtb files should be regenerated/reinstalled. Filenames are the
606 same but content is different now
607 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
608 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
609 addressing scheme is now pin 25 on /dev/gpioc3.
610 - Pandaboard: /etc/ttys should be updated, serial console device is
611 now /dev/ttyu2, not /dev/ttyu0
614 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
615 If you need the GNU extension from groff soelim(1), install groff
616 from package: pkg install groff, or via ports: textproc/groff.
619 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
620 defined in symlink(7); previously symlinks were silently ignored.
623 The const qualifier has been removed from iconv(3) to comply with
624 POSIX. The ports tree is aware of this from r384038 onwards.
627 Libraries specified by LIBADD in Makefiles must have a corresponding
628 DPADD_<lib> variable to ensure correct dependencies. This is now
629 enforced in src.libnames.mk.
632 From legacy ata(4) driver was removed support for SATA controllers
633 supported by more functional drivers ahci(4), siis(4) and mvs(4).
634 Kernel modules ataahci and ataadaptec were removed completely,
635 replaced by ahci and mvs modules respectively.
638 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
639 the 20141231 entry below for information about prerequisites and
640 upgrading, if you are not already using 3.5.0 or higher.
643 The 32-bit PowerPC kernel has been changed to a position-independent
644 executable. This can only be booted with a version of loader(8)
645 newer than January 31, 2015, so make sure to update both world and
646 kernel before rebooting.
649 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
650 but before r278950, the RNG was not seeded properly. Immediately
651 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
652 ssh keys or openssl keys) that were generated w/ a kernel from that
653 range. This does not affect programs that directly used /dev/random
654 or /dev/urandom. All userland uses of arc4random(3) are affected.
657 The autofs(4) ABI was changed in order to restore binary compatibility
658 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
662 The powerpc64 kernel has been changed to a position-independent
663 executable. This can only be booted with a new version of loader(8),
664 so make sure to update both world and kernel before rebooting.
667 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
668 only release, no new features have been added. Please see the 20141231
669 entry below for information about prerequisites and upgrading, if you
670 are not already using 3.5.0.
673 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
674 taken from the ELF Tool Chain project rather than GNU binutils. They
675 should be drop-in replacements, with the addition of arm64 support.
676 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
677 binutils tools, if necessary. See 20150805 for updated information.
680 The default Unbound configuration now enables remote control
681 using a local socket. Users who have already enabled the
682 local_unbound service should regenerate their configuration
683 by running "service local_unbound setup" as root.
686 The GNU texinfo and GNU info pages have been removed.
687 To be able to view GNU info pages please install texinfo from ports.
690 Clang, llvm and lldb have been upgraded to 3.5.0 release.
692 As of this release, a prerequisite for building clang, llvm and lldb is
693 a C++11 capable compiler and C++11 standard library. This means that to
694 be able to successfully build the cross-tools stage of buildworld, with
695 clang as the bootstrap compiler, your system compiler or cross compiler
696 should either be clang 3.3 or later, or gcc 4.8 or later, and your
697 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
700 On any standard FreeBSD 10.x or 11.x installation, where clang and
701 libc++ are on by default (that is, on x86 or arm), this should work out
704 On 9.x installations where clang is enabled by default, e.g. on x86 and
705 powerpc, libc++ will not be enabled by default, so libc++ should be
706 built (with clang) and installed first. If both clang and libc++ are
707 missing, build clang first, then use it to build libc++.
709 On 8.x and earlier installations, upgrade to 9.x first, and then follow
710 the instructions for 9.x above.
712 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
713 default, and do not build clang.
715 Many embedded systems are resource constrained, and will not be able to
716 build clang in a reasonable time, or in some cases at all. In those
717 cases, cross building bootable systems on amd64 is a workaround.
719 This new version of clang introduces a number of new warnings, of which
720 the following are most likely to appear:
724 This warns in two cases, for both C and C++:
725 * When the code is trying to take the absolute value of an unsigned
726 quantity, which is effectively a no-op, and almost never what was
727 intended. The code should be fixed, if at all possible. If you are
728 sure that the unsigned quantity can be safely cast to signed, without
729 loss of information or undefined behavior, you can add an explicit
730 cast, or disable the warning.
732 * When the code is trying to take an absolute value, but the called
733 abs() variant is for the wrong type, which can lead to truncation.
734 If you want to disable the warning instead of fixing the code, please
735 make sure that truncation will not occur, or it might lead to unwanted
738 -Wtautological-undefined-compare and
739 -Wundefined-bool-conversion
741 These warn when C++ code is trying to compare 'this' against NULL, while
742 'this' should never be NULL in well-defined C++ code. However, there is
743 some legacy (pre C++11) code out there, which actively abuses this
744 feature, which was less strictly defined in previous C++ versions.
746 Squid and openjdk do this, for example. The warning can be turned off
747 for C++98 and earlier, but compiling the code in C++11 mode might result
748 in unexpected behavior; for example, the parts of the program that are
749 unreachable could be optimized away.
752 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
753 kernel sources have been removed. The .h files remain, since some
754 utilities include them. This will need to be fixed later.
755 If "mount -t oldnfs ..." is attempted, it will fail.
756 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
757 the utilities will report errors.
760 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
761 directories to top level SUBDIR variable when their parent
762 directory is included in LOCAL_DIRS. Users with build systems with
763 such hierarchies and without SUBDIR entries in the parent
764 directory Makefiles should add them or add the directories to
768 faith(4) and faithd(8) have been removed from the base system. Faith
769 has been obsolete for a very long time.
772 vt(4), the new console driver, is enabled by default. It brings
773 support for Unicode and double-width characters, as well as
774 support for UEFI and integration with the KMS kernel video
777 You may need to update your console settings in /etc/rc.conf,
778 most probably the keymap. During boot, /etc/rc.d/syscons will
779 indicate what you need to do.
781 vt(4) still has issues and lacks some features compared to
782 syscons(4). See the wiki for up-to-date information:
783 https://wiki.freebsd.org/Newcons
785 If you want to keep using syscons(4), you can do so by adding
786 the following line to /boot/loader.conf:
790 pjdfstest has been integrated into kyua as an opt-in test suite.
791 Please see share/doc/pjdfstest/README for more details on how to
795 gperf has been removed from the base system for architectures
796 that use clang. Ports that require gperf will obtain it from the
800 pjdfstest has been moved from tools/regression/pjdfstest to
804 At svn r271982, The default linux compat kernel ABI has been adjusted
805 to 2.6.18 in support of the linux-c6 compat ports infrastructure
806 update. If you wish to continue using the linux-f10 compat ports,
807 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
808 encouraged to update their linux-compat packages to linux-c6 during
809 their next update cycle.
812 The ofwfb driver, used to provide a graphics console on PowerPC when
813 using vt(4), no longer allows mmap() of all physical memory. This
814 will prevent Xorg on PowerPC with some ATI graphics cards from
815 initializing properly unless x11-servers/xorg-server is updated to
819 The xdev targets have been converted to using TARGET and
820 TARGET_ARCH instead of XDEV and XDEV_ARCH.
823 The default unbound configuration has been modified to address
824 issues with reverse lookups on networks that use private
825 address ranges. If you use the local_unbound service, run
826 "service local_unbound setup" as root to regenerate your
827 configuration, then "service local_unbound reload" to load the
831 The GNU texinfo and GNU info pages are not built and installed
832 anymore, WITH_INFO knob has been added to allow to built and install
834 UPDATE: see 20150102 entry on texinfo's removal
837 The GNU readline library is now an INTERNALLIB - that is, it is
838 statically linked into consumers (GDB and variants) in the base
839 system, and the shared library is no longer installed. The
840 devel/readline port is available for third party software that
844 The Itanium architecture (ia64) has been removed from the list of
845 known architectures. This is the first step in the removal of the
849 Commit r268115 has added NFSv4.1 server support, merged from
850 projects/nfsv4.1-server. Since this includes changes to the
851 internal interfaces between the NFS related modules, a full
852 build of the kernel and modules will be necessary.
853 __FreeBSD_version has been bumped.
856 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
857 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
858 which differs from the behaviour controlled by this knob.)
861 Maximal length of the serial number in CTL was increased from 16 to
862 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
863 and ctld, need to be rebuilt to work with a new kernel.
866 The libatf-c and libatf-c++ major versions were downgraded to 0 and
867 1 respectively to match the upstream numbers. They were out of
868 sync because, when they were originally added to FreeBSD, the
869 upstream versions were not respected. These libraries are private
870 and not yet built by default, so renumbering them should be a
871 non-issue. However, unclean source trees will yield broken test
872 programs once the operator executes "make delete-old-libs" after a
875 Additionally, the atf-sh binary was made private by moving it into
876 /usr/libexec/. Already-built shell test programs will keep the
877 path to the old binary so they will break after "make delete-old"
880 If you are using WITH_TESTS=yes (not the default), wipe the object
881 tree and rebuild from scratch to prevent spurious test failures.
882 This is only needed once: the misnumbered libraries and misplaced
883 binaries have been added to OptionalObsoleteFiles.inc so they will
884 be removed during a clean upgrade.
887 Clang and llvm have been upgraded to 3.4.1 release.
890 We bogusly installed src.opts.mk in /usr/share/mk. This file should
891 be removed to avoid issues in the future (and has been added to
895 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
896 past, it affected all builds that used the bsd.*.mk files. The old
897 behavior was a bug, but people may have relied upon it. To get this
898 behavior back, you can .include /etc/src.conf from /etc/make.conf
899 (which is still global and isn't changed). This also changes the
900 behavior of incremental builds inside the tree of individual
901 directories. Set MAKESYSPATH to ".../share/mk" to do that.
902 Although this has survived make universe and some upgrade scenarios,
903 other upgrade scenarios may have broken. At least one form of
904 temporary breakage was fixed with MAKESYSPATH settings for buildworld
905 as well... In cases where MAKESYSPATH isn't working with this
906 setting, you'll need to set it to the full path to your tree.
908 One side effect of all this cleaning up is that bsd.compiler.mk
909 is no longer implicitly included by bsd.own.mk. If you wish to
910 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
914 The lindev device has been removed since /dev/full has been made a
915 standard device. __FreeBSD_version has been bumped.
918 The knob WITHOUT_VI was added to the base system, which controls
919 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
920 in order to reorder files share/termcap and didn't build ex(1) as a
921 build tool, so building/installing with WITH_VI is highly advised for
922 build hosts for older releases.
924 This issue has been fixed in stable/9 and stable/10 in r277022 and
925 r276991, respectively.
928 The YES_HESIOD knob has been removed. It has been obsolete for
929 a decade. Please move to using WITH_HESIOD instead or your builds
930 will silently lack HESIOD.
933 The uart(4) driver has been changed with respect to its handling
934 of the low-level console. Previously the uart(4) driver prevented
935 any process from changing the baudrate or the CLOCAL and HUPCL
936 control flags. By removing the restrictions, operators can make
937 changes to the serial console port without having to reboot.
938 However, when getty(8) is started on the serial device that is
939 associated with the low-level console, a misconfigured terminal
940 line in /etc/ttys will now have a real impact.
941 Before upgrading the kernel, make sure that /etc/ttys has the
942 serial console device configured as 3wire without baudrate to
943 preserve the previous behaviour. E.g:
944 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
947 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
948 to improve performance. To re-enable it, if needed, run rpcbind
949 with command line option -W.
952 Switched back to the GPL dtc compiler due to updates in the upstream
953 dts files not being supported by the BSDL dtc compiler. You will need
954 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
955 may result while building dtb files during a kernel build if you fail
956 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
959 Clang and llvm have been upgraded to 3.4 release.
962 The nve(4) driver has been removed. Please use the nfe(4) driver
963 for NVIDIA nForce MCP Ethernet adapters instead.
966 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
967 This could cause certain C++ applications using shared libraries built
968 against the previous version of libc++ to crash. The incompatibility
969 has now been fixed, but any C++ applications or shared libraries built
970 between r261283 and r261801 should be recompiled.
973 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
974 capability mode support. Please note that enabling the feature in
975 kernel is still highly recommended.
978 OpenSSH is now built with sandbox support, and will use sandbox as
979 the default privilege separation method. This requires Capsicum
980 capability mode support in kernel.
983 The libelf and libdwarf libraries have been updated to newer
984 versions from upstream. Shared library version numbers for
985 these two libraries were bumped. Any ports or binaries
986 requiring these two libraries should be recompiled.
987 __FreeBSD_version is bumped to 1100006.
990 If a Makefile in a tests/ directory was auto-generating a Kyuafile
991 instead of providing an explicit one, this would prevent such
992 Makefile from providing its own Kyuafile in the future during
993 NO_CLEAN builds. This has been fixed in the Makefiles but manual
994 intervention is needed to clean an objdir if you use NO_CLEAN:
995 # find /usr/obj -name Kyuafile | xargs rm -f
998 The behavior of gss_pseudo_random() for the krb5 mechanism
999 has changed, for applications requesting a longer random string
1000 than produced by the underlying enctype's pseudo-random() function.
1001 In particular, the random string produced from a session key of
1002 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1003 be different at the 17th octet and later, after this change.
1004 The counter used in the PRF+ construction is now encoded as a
1005 big-endian integer in accordance with RFC 4402.
1006 __FreeBSD_version is bumped to 1100004.
1009 The WITHOUT_ATF build knob has been removed and its functionality
1010 has been subsumed into the more generic WITHOUT_TESTS. If you were
1011 using the former to disable the build of the ATF libraries, you
1012 should change your settings to use the latter.
1015 The default version of mtree is nmtree which is obtained from
1016 NetBSD. The output is generally the same, but may vary
1017 slightly. If you found you need identical output adding
1018 "-F freebsd9" to the command line should do the trick. For the
1019 time being, the old mtree is available as fmtree.
1022 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1023 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1024 1.1.4_8 and verify bsdyml not linked in, before running "make
1026 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1028 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1031 The stable/10 branch has been created in subversion from head
1035 The rc.d/jail script has been updated to support jail(8)
1036 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1037 for per-jail configuration are automatically converted to
1038 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1039 This is transparently backward compatible. See below about some
1040 incompatibilities and rc.conf(5) manual page for more details.
1042 These variables are now deprecated in favor of jail(8) configuration
1043 file. One can use "rc.d/jail config <jname>" command to generate
1044 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1045 running the jail(8) utility. The default pathname of the
1046 configuration file is /etc/jail.conf and can be specified by
1047 using $jail_conf or $jail_<jname>_conf variables.
1049 Please note that jail_devfs_ruleset accepts an integer at
1050 this moment. Please consider to rewrite the ruleset name
1054 BIND has been removed from the base system. If all you need
1055 is a local resolver, simply enable and start the local_unbound
1056 service instead. Otherwise, several versions of BIND are
1057 available in the ports tree. The dns/bind99 port is one example.
1059 With this change, nslookup(1) and dig(1) are no longer in the base
1060 system. Users should instead use host(1) and drill(1) which are
1061 in the base system. Alternatively, nslookup and dig can
1062 be obtained by installing the dns/bind-tools port.
1065 With the addition of unbound(8), a new unbound user is now
1066 required during installworld. "mergemaster -p" can be used to
1067 add the user prior to installworld, as documented in the handbook.
1070 OpenSSH is now built with DNSSEC support, and will by default
1071 silently trust signed SSHFP records. This can be controlled with
1072 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1073 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1076 The GNU Compiler Collection and C++ standard library (libstdc++)
1077 are no longer built by default on platforms where clang is the system
1078 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1079 options in src.conf.
1082 The PROCDESC kernel option is now part of the GENERIC kernel
1083 configuration and is required for the rwhod(8) to work.
1084 If you are using custom kernel configuration, you should include
1088 The API and ABI related to the Capsicum framework was modified
1089 in backward incompatible way. The userland libraries and programs
1090 have to be recompiled to work with the new kernel. This includes the
1091 following libraries and programs, but the whole buildworld is
1092 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1093 kdump, procstat, rwho, rwhod, uniq.
1096 AES-NI intrinsic support has been added to gcc. The AES-NI module
1097 has been updated to use this support. A new gcc is required to build
1098 the aesni module on both i386 and amd64.
1101 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1102 Thus "device padlock_rng" and "device rdrand_rng" should be
1103 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1106 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1107 enables just the iconv* functionality and is now on by default.
1108 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1109 compatibility. Set WITHOUT_ICONV to build the old way.
1110 If you have been using WITH_ICONV before, you will very likely
1111 need to turn on WITH_LIBICONV_COMPAT.
1114 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1115 Illumos origin, including ZFS. If you have INVARIANTS in your
1116 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1118 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1119 locks if WITNESS option was set. Because that generated a lot of
1120 witness(9) reports and all of them were believed to be false
1121 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1122 can be used to achieve the previous behavior.
1125 Timer values in IPv6 data structures now use time_uptime instead
1126 of time_second. Although this is not a user-visible functional
1127 change, userland utilities which directly use them---ndp(8),
1128 rtadvd(8), and rtsold(8) in the base system---need to be updated
1129 to r253970 or later.
1132 find -delete can now delete the pathnames given as arguments,
1133 instead of only files found below them or if the pathname did
1134 not contain any slashes. Formerly, the following error message
1137 find: -delete: <path>: relative path potentially not safe
1139 Deleting the pathnames given as arguments can be prevented
1140 without error messages using -mindepth 1 or by changing
1141 directory and passing "." as argument to find. This works in the
1142 old as well as the new version of find.
1145 Behavior of devfs rules path matching has been changed.
1146 Pattern is now always matched against fully qualified devfs
1147 path and slash characters must be explicitly matched by
1148 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1149 subdirectories must be reviewed.
1152 The default ARM ABI has changed to the ARM EABI. The old ABI is
1153 incompatible with the ARM EABI and all programs and modules will
1154 need to be rebuilt to work with a new kernel.
1156 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1158 NOTE: Support for the old ABI will be removed in the future and
1159 users are advised to upgrade.
1162 pkg_install has been disconnected from the build if you really need it
1163 you should add WITH_PKGTOOLS in your src.conf(5).
1166 Most of network statistics structures were changed to be able
1167 keep 64-bits counters. Thus all tools, that work with networking
1168 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1171 Fix a bug that allowed a tracing process (e.g. gdb) to write
1172 to a memory-mapped file in the traced process's address space
1173 even if neither the traced process nor the tracing process had
1174 write access to that file.
1177 CVS has been removed from the base system. An exact copy
1178 of the code is available from the devel/cvs port.
1181 Some people report the following error after the switch to bmake:
1183 make: illegal option -- J
1184 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1186 *** [buildworld] Error code 2
1188 this likely due to an old instance of make in
1189 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1190 which src/Makefile will use that blindly, if it exists, so if
1191 you see the above error:
1193 rm -rf `make -V MAKEPATH`
1198 Use bmake by default.
1199 Whereas before one could choose to build with bmake via
1200 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1201 make. The goal is to remove these knobs for 10-RELEASE.
1203 It is worth noting that bmake (like gmake) treats the command
1204 line as the unit of failure, rather than statements within the
1205 command line. Thus '(cd some/where && dosomething)' is safer
1206 than 'cd some/where; dosomething'. The '()' allows consistent
1207 behavior in parallel build.
1210 Fix a bug that allows NFS clients to issue READDIR on files.
1213 The WITHOUT_IDEA option has been removed because
1214 the IDEA patent expired.
1217 The sysctl which controls TRIM support under ZFS has been renamed
1218 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1222 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1223 rather than creating it's own in the temporary directory in
1224 order allow access to bootstrapped versions of tools such as
1225 install and mtree. When upgrading from version of FreeBSD where
1226 the install command does not support -l, you will need to
1227 install a new mergemaster command if mergemaster -p is required.
1228 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1232 Legacy ATA stack, disabled and replaced by new CAM-based one since
1233 FreeBSD 9.0, completely removed from the sources. Kernel modules
1234 atadisk and atapi*, user-level tools atacontrol and burncd are
1235 removed. Kernel option `options ATA_CAM` is now permanently enabled
1239 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1240 and socketpair(2). Software, in particular Kerberos, may
1241 automatically detect and use these during building. The resulting
1242 binaries will not work on older kernels.
1245 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1246 information, see the respective 20130304 entry).
1249 Recent commits to callout(9) changed the size of struct callout,
1250 so the KBI is probably heavily disturbed. Also, some functions
1251 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1252 by macros. Every kernel module using it won't load, so rebuild
1255 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1256 but does not initialize by default (because of the new CTL_DISABLE
1257 option) to save memory. To re-enable it, remove the CTL_DISABLE
1258 option from the kernel config file or set kern.cam.ctl.disable=0
1259 in /boot/loader.conf.
1262 The ctl device has been disabled in GENERIC for i386 and amd64.
1263 This was done due to the extra memory being allocated at system
1264 initialisation time by the ctl driver which was only used if
1265 a CAM target device was created. This makes a FreeBSD system
1266 unusable on 128MB or less of RAM.
1269 A new compression method (lz4) has been merged to -HEAD. Please
1270 refer to zpool-features(7) for more information.
1272 Please refer to the "ZFS notes" section of this file for information
1273 on upgrading boot ZFS pools.
1276 A BSD-licensed patch(1) variant has been added and is installed
1277 as bsdpatch, being the GNU version the default patch.
1278 To inverse the logic and use the BSD-licensed one as default,
1279 while having the GNU version installed as gnupatch, rebuild
1280 and install world with the WITH_BSD_PATCH knob set.
1283 Due to the use of the new -l option to install(1) during build
1284 and install, you must take care not to directly set the INSTALL
1285 make variable in your /etc/make.conf, /etc/src.conf, or on the
1286 command line. If you wish to use the -C flag for all installs
1287 you may be able to add INSTALL+=-C to /etc/make.conf or
1291 The install(1) option -M has changed meaning and now takes an
1292 argument that is a file or path to append logs to. In the
1293 unlikely event that -M was the last option on the command line
1294 and the command line contained at least two files and a target
1295 directory the first file will have logs appended to it. The -M
1296 option served little practical purpose in the last decade so its
1297 use is expected to be extremely rare.
1300 After switching to Clang as the default compiler some users of ZFS
1301 on i386 systems started to experience stack overflow kernel panics.
1302 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1305 GEOM_LABEL now mangles label names read from file system metadata.
1306 Mangling affect labels containing spaces, non-printable characters,
1307 '%' or '"'. Device names in /etc/fstab and other places may need to
1311 By default, only the 10 most recent kernel dumps will be saved. To
1312 restore the previous behaviour (no limit on the number of kernel dumps
1313 stored in the dump directory) add the following line to /etc/rc.conf:
1318 With the addition of auditdistd(8), a new auditdistd user is now
1319 required during installworld. "mergemaster -p" can be used to
1320 add the user prior to installworld, as documented in the handbook.
1323 The sin6_scope_id member variable in struct sockaddr_in6 is now
1324 filled by the kernel before passing the structure to the userland via
1325 sysctl or routing socket. This means the KAME-specific embedded scope
1326 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1327 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1328 __FreeBSD_version is bumped to 1000025.
1331 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1332 This means that the world and kernel will be compiled with clang
1333 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1334 and /usr/bin/cpp. To disable this behavior and revert to building
1335 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1336 of current may need to bootstrap WITHOUT_CLANG first if the clang
1337 build fails (its compatibility window doesn't extend to the 9 stable
1341 The IPFIREWALL_FORWARD kernel option has been removed. Its
1342 functionality now turned on by default.
1345 The ZERO_COPY_SOCKET kernel option has been removed and
1346 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1347 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1348 mechanism which is not safe and may result in kernel crashes.
1349 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1350 driver supports disposeable external page sized mbuf storage.
1351 Proper replacements for both zero-copy mechanisms are under
1352 consideration and will eventually lead to complete removal
1353 of the two kernel options.
1356 The IPv4 network stack has been converted to network byte
1357 order. The following modules need to be recompiled together
1358 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1359 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1362 Support for non-MPSAFE filesystems was removed from VFS. The
1363 VFS_VERSION was bumped, all filesystem modules shall be
1367 All the non-MPSAFE filesystems have been disconnected from
1368 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1369 portalfs, smbfs, xfs.
1372 The interface cloning API and ABI has changed. The following
1373 modules need to be recompiled together with kernel:
1374 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1375 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1376 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1379 The sdhci driver was split in two parts: sdhci (generic SD Host
1380 Controller logic) and sdhci_pci (actual hardware driver).
1381 No kernel config modifications are required, but if you
1382 load sdhc as a module you must switch to sdhci_pci instead.
1385 Import the FUSE kernel and userland support into base system.
1388 The GNU sort(1) program has been removed since the BSD-licensed
1389 sort(1) has been the default for quite some time and no serious
1390 problems have been reported. The corresponding WITH_GNU_SORT
1394 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1395 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1399 The net80211(4) ABI has been changed to allow for improved driver
1400 PS-POLL and power-save support. All wireless drivers need to be
1401 recompiled to work with the new kernel.
1404 The random(4) support for the VIA hardware random number
1405 generator (`PADLOCK') is no longer enabled unconditionally.
1406 Add the padlock_rng device in the custom kernel config if
1407 needed. The GENERIC kernels on i386 and amd64 do include the
1408 device, so the change only affects the custom kernel
1412 The pf(4) packet filter ABI has been changed. pfctl(8) and
1413 snmp_pf module need to be recompiled to work with new kernel.
1416 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1417 to -HEAD. Pools that have empty_bpobj in active state can not be
1418 imported read-write with ZFS implementations that do not support
1419 this feature. For more information read the zpool-features(5)
1423 The sparc64 ZFS loader has been changed to no longer try to auto-
1424 detect ZFS providers based on diskN aliases but now requires these
1425 to be explicitly listed in the OFW boot-device environment variable.
1428 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1429 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1430 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1433 The following sysctls and tunables have been renamed for consistency
1434 with other variables:
1435 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1436 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1439 The sort utility has been replaced with BSD sort. For now, GNU sort
1440 is also available as "gnusort" or the default can be set back to
1441 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1442 installed as "bsdsort".
1445 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1446 Starting with this version the old system of ZFS pool versioning
1447 is superseded by "feature flags". This concept enables forward
1448 compatibility against certain future changes in functionality of ZFS
1449 pools. The first read-only compatible "feature flag" for ZFS pools
1450 is named "com.delphix:async_destroy". For more information
1451 read the new zpool-features(5) manual page.
1452 Please refer to the "ZFS notes" section of this file for information
1453 on upgrading boot ZFS pools.
1456 The malloc(3) implementation embedded in libc now uses sources imported
1457 as contrib/jemalloc. The most disruptive API change is to
1458 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1459 delete it prior to installworld, and optionally re-create it using the
1460 new format after rebooting. See malloc.conf(5) for details
1461 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1465 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1466 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1467 now spelled mips. This is to aid compatibility with third-party
1468 software that expects this naming scheme in uname(3). Little-endian
1469 settings are unchanged. If you are updating a big-endian mips64 machine
1470 from before this change, you may need to set MACHINE_ARCH=mips64 in
1471 your environment before the new build system will recognize your machine.
1474 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1478 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1479 nullfs(5) did not pass through all behaviours to the underlying layer,
1480 as a result if we bound to a socket on the lower layer we could connect
1481 only to the lower path; if we bound to the upper layer we could connect
1482 only to the upper path. The new behavior is one can connect to both the
1483 lower and the upper paths regardless what layer path one binds to.
1486 The getifaddrs upgrade path broken with 20111215 has been restored.
1487 If you have upgraded in between 20111215 and 20120209 you need to
1488 recompile libc again with your kernel. You still need to recompile
1489 world to be able to configure CARP but this restriction already
1490 comes from 20111215.
1493 The set_rcvar() function has been removed from /etc/rc.subr. All
1494 base and ports rc.d scripts have been updated, so if you have a
1495 port installed with a script in /usr/local/etc/rc.d you can either
1496 hand-edit the rcvar= line, or reinstall the port.
1498 An easy way to handle the mass-update of /etc/rc.d:
1499 rm /etc/rc.d/* && mergemaster -i
1502 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1503 on the current CPU and prevents other threads from running.
1504 This behavior can be reverted using the kern.stop_scheduler_on_panic
1506 The new behavior can be incompatible with kern.sync_on_panic.
1509 The carp(4) facility has been changed significantly. Configuration
1510 of the CARP protocol via ifconfig(8) has changed, as well as format
1511 of CARP events submitted to devd(8) has changed. See manual pages
1512 for more information. The arpbalance feature of carp(4) is currently
1513 not supported anymore.
1515 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1516 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1517 need to be recompiled.
1520 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1524 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1525 explicitely support non-MPSAFE filesystems.
1526 It is on by default for all supported platform at this present
1530 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1531 i386 and pc98 GENERIC kernel configuration files.
1534 sysinstall has been removed
1537 The stable/9 branch created in subversion. This corresponds to the
1538 RELENG_9 branch in CVS.
1544 Avoid using make -j when upgrading. While generally safe, there are
1545 sometimes problems using -j to upgrade. If your upgrade fails with
1546 -j, please try again without -j. From time to time in the past there
1547 have been problems using -j with buildworld and/or installworld. This
1548 is especially true when upgrading between "distant" versions (eg one
1549 that cross a major release boundary or several minor releases, or when
1550 several months have passed on the -current branch).
1552 Sometimes, obscure build problems are the result of environment
1553 poisoning. This can happen because the make utility reads its
1554 environment when searching for values for global variables. To run
1555 your build attempts in an "environmental clean room", prefix all make
1556 commands with 'env -i '. See the env(1) manual page for more details.
1558 When upgrading from one major version to another it is generally best to
1559 upgrade to the latest code in the currently installed branch first, then
1560 do an upgrade to the new branch. This is the best-tested upgrade path,
1561 and has the highest probability of being successful. Please try this
1562 approach if you encounter problems with a major version upgrade. Since
1563 the stable 4.x branch point, one has generally been able to upgade from
1564 anywhere in the most recent stable branch to head / current (or even the
1565 last couple of stable branches). See the top of this file when there's
1568 When upgrading a live system, having a root shell around before
1569 installing anything can help undo problems. Not having a root shell
1570 around can lead to problems if pam has changed too much from your
1571 starting point to allow continued authentication after the upgrade.
1573 This file should be read as a log of events. When a later event changes
1574 information of a prior event, the prior event should not be deleted.
1575 Instead, a pointer to the entry with the new information should be
1576 placed in the old entry. Readers of this file should also sanity check
1577 older entries before relying on them blindly. Authors of new entries
1578 should write them with this in mind.
1582 When upgrading the boot ZFS pool to a new version, always follow
1585 1.) recompile and reinstall the ZFS boot loader and boot block
1586 (this is part of "make buildworld" and "make installworld")
1588 2.) update the ZFS boot block on your boot drive
1590 The following example updates the ZFS boot block on the first
1591 partition (freebsd-boot) of a GPT partitioned drive ada0:
1592 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1594 Non-boot pools do not need these updates.
1598 If you are updating from a prior version of FreeBSD (even one just
1599 a few days old), you should follow this procedure. It is the most
1600 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1602 make kernel-toolchain
1603 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1604 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1606 To test a kernel once
1607 ---------------------
1608 If you just want to boot a kernel once (because you are not sure
1609 if it works, or if you want to boot a known bad kernel to provide
1610 debugging information) run
1611 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1612 nextboot -k testkernel
1614 To just build a kernel when you know that it won't mess you up
1615 --------------------------------------------------------------
1616 This assumes you are already running a CURRENT system. Replace
1617 ${arch} with the architecture of your machine (e.g. "i386",
1618 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1620 cd src/sys/${arch}/conf
1621 config KERNEL_NAME_HERE
1622 cd ../compile/KERNEL_NAME_HERE
1627 If this fails, go to the "To build a kernel" section.
1629 To rebuild everything and install it on the current system.
1630 -----------------------------------------------------------
1631 # Note: sometimes if you are running current you gotta do more than
1632 # is listed here if you are upgrading from a really old current.
1634 <make sure you have good level 0 dumps>
1636 make kernel KERNCONF=YOUR_KERNEL_HERE
1638 <reboot in single user> [3]
1645 To cross-install current onto a separate partition
1646 --------------------------------------------------
1647 # In this approach we use a separate partition to hold
1648 # current's root, 'usr', and 'var' directories. A partition
1649 # holding "/", "/usr" and "/var" should be about 2GB in
1652 <make sure you have good level 0 dumps>
1655 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1656 <maybe newfs current's root partition>
1657 <mount current's root partition on directory ${CURRENT_ROOT}>
1658 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1659 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1660 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1661 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1662 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1663 <reboot into current>
1664 <do a "native" rebuild/install as described in the previous section>
1665 <maybe install compatibility libraries from ports/misc/compat*>
1669 To upgrade in-place from stable to current
1670 ----------------------------------------------
1671 <make sure you have good level 0 dumps>
1673 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1675 <reboot in single user> [3]
1682 Make sure that you've read the UPDATING file to understand the
1683 tweaks to various things you need. At this point in the life
1684 cycle of current, things change often and you are on your own
1685 to cope. The defaults can also change, so please read ALL of
1686 the UPDATING entries.
1688 Also, if you are tracking -current, you must be subscribed to
1689 freebsd-current@freebsd.org. Make sure that before you update
1690 your sources that you have read and understood all the recent
1691 messages there. If in doubt, please track -stable which has
1692 much fewer pitfalls.
1694 [1] If you have third party modules, such as vmware, you
1695 should disable them at this point so they don't crash your
1698 [3] From the bootblocks, boot -s, and then do
1703 adjkerntz -i # if CMOS is wall time
1704 Also, when doing a major release upgrade, it is required that
1705 you boot into single user mode to do the installworld.
1707 [4] Note: This step is non-optional. Failure to do this step
1708 can result in a significant reduction in the functionality of the
1709 system. Attempting to do it by hand is not recommended and those
1710 that pursue this avenue should read this file carefully, as well
1711 as the archives of freebsd-current and freebsd-hackers mailing lists
1712 for potential gotchas. The -U option is also useful to consider.
1713 See mergemaster(8) for more information.
1715 [5] Usually this step is a noop. However, from time to time
1716 you may need to do this if you get unknown user in the following
1717 step. It never hurts to do it all the time. You may need to
1718 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1719 install) after the buildworld before this step if you last updated
1720 from current before 20130425 or from -stable before 20130430.
1722 [6] This only deletes old files and directories. Old libraries
1723 can be deleted by "make delete-old-libs", but you have to make
1724 sure that no program is using those libraries anymore.
1726 [8] In order to have a kernel that can run the 4.x binaries needed to
1727 do an installworld, you must include the COMPAT_FREEBSD4 option in
1728 your kernel. Failure to do so may leave you with a system that is
1729 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1730 required to run the 5.x binaries on more recent kernels. And so on
1731 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1733 Make sure that you merge any new devices from GENERIC since the
1734 last time you updated your kernel config file.
1736 [9] When checking out sources, you must include the -P flag to have
1737 cvs prune empty directories.
1739 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1740 "?=" instead of the "=" assignment operator, so that buildworld can
1741 override the CPUTYPE if it needs to.
1743 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1744 not on the command line, or in /etc/make.conf. buildworld will
1745 warn if it is improperly defined.
1748 This file contains a list, in reverse chronological order, of major
1749 breakages in tracking -current. It is not guaranteed to be a complete
1750 list of such breakages, and only contains entries since September 23, 2011.
1751 If you need to see UPDATING entries from before that date, you will need
1752 to fetch an UPDATING file from an older FreeBSD release.
1754 Copyright information:
1756 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1758 Redistribution, publication, translation and use, with or without
1759 modification, in full or in part, in any form or format of this
1760 document are permitted without further permission from the author.
1762 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1763 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1764 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1765 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1766 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1767 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1768 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1769 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1770 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1771 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1772 POSSIBILITY OF SUCH DAMAGE.
1774 Contact Warner Losh if you have any questions about your use of