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 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-src.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.
20 The use of RSS hash from the network card aka flowid has been
21 disabled by default for lagg(4) as it's currently incompatible with
22 the lacp and loadbalance protocols.
24 This can be re-enabled by setting the following in loader.conf:
25 net.link.lagg.default_use_flowid="1"
28 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
29 6.0.0. Please see the 20141231 entry below for information about
30 prerequisites and upgrading, if you are not already using clang 3.5.0
34 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
35 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
36 to WITH/OUT_LOADER_GELI.
39 The geli password typed at boot is now hidden. To restore the previous
40 behavior, see geli(8) for configuration options.
42 The SW_WATCHDOG option is no longer necessary to enable the
43 hardclock-based software watchdog if no hardware watchdog is
44 configured. As before, SW_WATCHDOG will cause the software
45 watchdog to be enabled even if a hardware watchdog is configured.
48 lint(1) binaries and library are no longer built by default. To
49 enable building them, define WITH_LINT in src.conf. If you are using
50 a FreeBSD 12 or later system to build 11-stable, you may need to
51 install a lint(1) binary to use WITH_LINT.
54 When building multiple kernels using KERNCONF, non-existent KERNCONF
55 files will produce an error and buildkernel will fail. Previously
56 missing KERNCONF files silently failed giving no indication as to
57 why, only to subsequently discover during installkernel that the
58 desired kernel was never built in the first place.
61 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
62 Please see the 20141231 entry below for information about prerequisites
63 and upgrading, if you are not already using clang 3.5.0 or higher.
66 Since the switch to GPT disk labels, fsck for UFS/FFS has been
67 unable to automatically find alternate superblocks. As of r322806,
68 the information needed to find alternate superblocks has been
69 moved to the end of the area reserved for the boot block.
70 Filesystems created with a newfs of this vintage or later
71 will create the recovery information. If you have a filesystem
72 created prior to this change and wish to have a recovery block
73 created for your filesystem, you can do so by running fsck in
74 forground mode (i.e., do not use the -p or -y options). As it
75 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
76 to which you should answer yes.
79 arm64 builds now use the base system LLD 4.0.0 linker by default,
80 instead of requiring that the aarch64-binutils port or package be
81 installed. To continue using aarch64-binutils, set
82 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
85 The ctl.ko module no longer implements the iSCSI target frontend:
86 cfiscsi.ko does instead.
88 If building cfiscsi.ko as a kernel module, the module can be loaded
89 via one of the following methods:
90 - `cfiscsi_load="YES"` in loader.conf(5).
91 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
92 - ctladm(8)/ctld(8), when compiled with iSCSI support
93 (`WITH_ISCSI=yes` in src.conf(5))
95 Please see cfiscsi(4) for more details.
98 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
99 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
100 same source (previously, the dependency of mmcsd.ko on mmc.ko was
101 missing, but mmcsd.ko now will refuse to load if it is incompatible
105 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
106 use any explicitly assigned loopback address available in the jail
107 instead of using the first assigned address of the jail.
110 As of r316810 for ipfilter, keep frags is no longer assumed when
111 keep state is specified in a rule. r316810 aligns ipfilter with
112 documentation in man pages separating keep frags from keep state.
113 This allows keep state to specified without forcing keep frags
114 and allows keep frags to be specified independently of keep state.
115 To maintain previous behaviour, also specify keep frags with
116 keep state (as documented in ipf.conf.5).
119 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
120 Please see the 20141231 entry below for information about prerequisites
121 and upgrading, if you are not already using clang 3.5.0 or higher.
124 The code that provides support for ZFS .zfs/ directory functionality
125 has been reimplemented. It's not possible now to create a snapshot
126 by mkdir under .zfs/snapshot/. That should be the only user visible
130 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
131 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
132 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
133 and now NAT-T is supported by default. Security associations now use
134 the single namespace for SPI allocation, so if you use several manually
135 configured security associations with the same SPI, this configuration
139 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
140 Please see the 20141231 entry below for information about prerequisites
141 and upgrading, if you are not already using clang 3.5.0 or higher.
144 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
145 Please see the 20141231 entry below for information about prerequisites
146 and upgrading, if you are not already using clang 3.5.0 or higher.
149 The layout of the pmap structure has changed for powerpc to put the pmap
150 statistics at the front for all CPU variations. libkvm(3) and all tools
151 that link against it need to be recompiled.
154 isl(4) and cyapa(4) drivers now require a new driver,
155 chromebook_platform(4), to work properly on Chromebook-class hardware.
156 On other types of hardware the drivers may need to be configured using
157 device hints. Please see the corresponding manual pages for details.
160 Relocatable object files with the extension of .So have been renamed
161 to use an extension of .pico instead. The purpose of this change is
162 to avoid a name clash with shared libraries on case-insensitive file
163 systems. On those file systems, foo.So is the same file as foo.so.
166 The libc stub for the pipe(2) system call has been replaced with
167 a wrapper that calls the pipe2(2) system call and the pipe(2)
168 system call is now only implemented by the kernels that include
169 "options COMPAT_FREEBSD10" in their config file (this is the
170 default). Users should ensure that this option is enabled in
171 their kernel or upgrade userspace to r302092 before upgrading their
175 CAM will now strip leading spaces from SCSI disks' serial numbers.
176 This will effect users who create UFS filesystems on SCSI disks using
177 those disk's diskid device nodes. For example, if /etc/fstab
178 previously contained a line like
179 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
180 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
181 transforms like gmirror may also be affected. ZFS users should
185 The bitstring(3) API has been updated with new functionality and
186 improved performance. But it is binary-incompatible with the old API.
187 Objects built with the new headers may not be linked against objects
188 built with the old headers.
191 The brk and sbrk functions have been removed from libc on arm64.
192 Binutils from ports has been updated to not link to these
193 functions and should be updated to the latest version before
194 installing a new libc.
197 The armv6 port now defaults to hard float ABI. Limited support
198 for running both hardfloat and soft float on the same system
199 is available using the libraries installed with -DWITH_LIBSOFT.
200 This has only been tested as an upgrade path for installworld
201 and packages may fail or need manual intervention to run. New
202 packages will be needed.
204 To update an existing self-hosted armv6hf system, you must add
205 TARGET_ARCH=armv6 on the make command line for both the build
206 and the install steps.
209 Kernel modules compiled outside of a kernel build now default to
210 installing to /boot/modules instead of /boot/kernel. Many kernel
211 modules built this way (such as those in ports) already overrode
212 KMODDIR explicitly to install into /boot/modules. However,
213 manually building and installing a module from /sys/modules will
214 now install to /boot/modules instead of /boot/kernel.
217 The CAM I/O scheduler has been committed to the kernel. There should be
218 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
219 list of known rogues that claim support for this but actually corrupt
220 data is believed to be complete, be on the lookout for data
221 corruption. The known rogue list is believed to be complete:
223 o Crucial MX100, M550 drives with MU01 firmware.
224 o Micron M510 and M550 drives with MU01 firmware.
225 o Micron M500 prior to MU07 firmware
226 o Samsung 830, 840, and 850 all firmwares
227 o FCCT M500 all firmwares
229 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
230 with working NCQ TRIM. For Micron branded drives, see your sales rep for
231 updated firmware. Black listed drives will work correctly because these
232 drives work correctly so long as no NCQ TRIMs are sent to them. Given
233 this list is the same as found in Linux, it's believed there are no
234 other rogues in the market place. All other models from the above
237 To be safe, if you are at all concerned, you can quirk each of your
238 drives to prevent NCQ from being sent by setting:
239 kern.cam.ada.X.quirks="0x2"
240 in loader.conf. If the drive requires the 4k sector quirk, set the
244 The FAST_DEPEND build option has been removed and its functionality is
245 now the one true way. The old mkdep(1) style of 'make depend' has
246 been removed. See 20160311 for further details.
249 Resource range types have grown from unsigned long to uintmax_t. All
250 drivers, and anything using libdevinfo, need to be recompiled.
253 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
254 builds. It no longer runs mkdep(1) during 'make depend', and the
255 'make depend' stage can safely be skipped now as it is auto ran
256 when building 'make all' and will generate all SRCS and DPSRCS before
257 building anything else. Dependencies are gathered at compile time with
258 -MF flags kept in separate .depend files per object file. Users should
259 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
263 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
264 kernel modules. Therefore, if you load any kernel modules at boot time,
265 please install the boot loaders after you install the kernel, but before
269 make kernel KERNCONF=YOUR_KERNEL_HERE
270 make -C sys/boot install
271 <reboot in single user>
273 Then follow the usual steps, described in the General Notes section,
277 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
278 see the 20141231 entry below for information about prerequisites and
279 upgrading, if you are not already using clang 3.5.0 or higher.
282 The AIO subsystem is now a standard part of the kernel. The
283 VFS_AIO kernel option and aio.ko kernel module have been removed.
284 Due to stability concerns, asynchronous I/O requests are only
285 permitted on sockets and raw disks by default. To enable
286 asynchronous I/O requests on all file types, set the
287 vfs.aio.enable_unsafe sysctl to a non-zero value.
290 The ELF object manipulation tool objcopy is now provided by the
291 ELF Tool Chain project rather than by GNU binutils. It should be a
292 drop-in replacement, with the addition of arm64 support. The
293 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
294 to obtain the GNU version if necessary.
297 Building ZFS pools on top of zvols is prohibited by default. That
298 feature has never worked safely; it's always been prone to deadlocks.
299 Using a zvol as the backing store for a VM guest's virtual disk will
300 still work, even if the guest is using ZFS. Legacy behavior can be
301 restored by setting vfs.zfs.vol.recursive=1.
304 The NONE and HPN patches has been removed from OpenSSH. They are
305 still available in the security/openssh-portable port.
308 With the addition of ypldap(8), a new _ypldap user is now required
309 during installworld. "mergemaster -p" can be used to add the user
310 prior to installworld, as documented in the handbook.
313 The tftp loader (pxeboot) now uses the option root-path directive. As a
314 consequence it no longer looks for a pxeboot.4th file on the tftp
315 server. Instead it uses the regular /boot infrastructure as with the
319 The code to start recording plug and play data into the modules has
320 been committed. While the old tools will properly build a new kernel,
321 a number of warnings about "unknown metadata record 4" will be produced
322 for an older kldxref. To avoid such warnings, make sure to rebuild
323 the kernel toolchain (or world). Make sure that you have r292078 or
324 later when trying to build 292077 or later before rebuilding.
327 Debug data files are now built by default with 'make buildworld' and
328 installed with 'make installworld'. This facilitates debugging but
329 requires more disk space both during the build and for the installed
330 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
334 r291527 changed the internal interface between the nfsd.ko and
335 nfscommon.ko modules. As such, they must both be upgraded to-gether.
336 __FreeBSD_version has been bumped because of this.
339 Add support for unicode collation strings leads to a change of
340 order of files listed by ls(1) for example. To get back to the old
341 behaviour, set LC_COLLATE environment variable to "C".
343 Databases administrators will need to reindex their databases given
344 collation results will be different.
346 Due to a bug in install(1) it is recommended to remove the ancient
347 locales before running make installworld.
349 rm -rf /usr/share/locale/*
352 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
353 libcrypto.so.7 or libssl.so.7 must be recompiled.
356 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
357 Kernel modules isp_2400_multi and isp_2500_multi were removed and
358 should be replaced with isp_2400 and isp_2500 modules respectively.
361 The build previously allowed using 'make -n' to not recurse into
362 sub-directories while showing what commands would be executed, and
363 'make -n -n' to recursively show commands. Now 'make -n' will recurse
364 and 'make -N' will not.
367 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
368 and etcupdate will now use this file. A custom sendmail.cf is now
369 updated via this mechanism rather than via installworld. If you had
370 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
371 want to remove the exclusion or change it to "always install".
372 /etc/mail/sendmail.cf is now managed the same way regardless of
373 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
374 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
377 Compatibility shims for legacy ATA device names have been removed.
378 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
379 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
380 environment variables, /dev/ad* and /dev/ar* symbolic links.
383 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
384 Please see the 20141231 entry below for information about prerequisites
385 and upgrading, if you are not already using clang 3.5.0 or higher.
388 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
389 and renamed from .symbols to .debug. This reduces the size requirements
390 on the boot partition or file system and provides consistency with
391 userland debug files.
393 When using the supported kernel installation method the
394 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
395 as is done with /boot/kernel.
397 Developers wishing to maintain the historical behavior of installing
398 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
401 The wireless drivers had undergone changes that remove the 'parent
402 interface' from the ifconfig -l output. The rc.d network scripts
403 used to check presence of a parent interface in the list, so old
404 scripts would fail to start wireless networking. Thus, etcupdate(3)
405 or mergemaster(8) run is required after kernel update, to update your
406 rc.d scripts in /etc.
409 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
410 These configurations are now automatically interpreted as
411 'scrub fragment reassemble'.
414 Kernel-loadable modules for the random(4) device are back. To use
415 them, the kernel must have
418 options RANDOM_LOADABLE
420 kldload(8) can then be used to load random_fortuna.ko
421 or random_yarrow.ko. Please note that due to the indirect
422 function calls that the loadable modules need to provide,
423 the build-in variants will be slightly more efficient.
425 The random(4) kernel option RANDOM_DUMMY has been retired due to
426 unpopularity. It was not all that useful anyway.
429 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
430 Control over building the ELF Tool Chain tools is now provided by
431 the WITHOUT_TOOLCHAIN knob.
434 The polarity of Pulse Per Second (PPS) capture events with the
435 uart(4) driver has been corrected. Prior to this change the PPS
436 "assert" event corresponded to the trailing edge of a positive PPS
437 pulse and the "clear" event was the leading edge of the next pulse.
439 As the width of a PPS pulse in a typical GPS receiver is on the
440 order of 1 millisecond, most users will not notice any significant
441 difference with this change.
443 Anyone who has compensated for the historical polarity reversal by
444 configuring a negative offset equal to the pulse width will need to
445 remove that workaround.
448 The default group assigned to /dev/dri entries has been changed
449 from 'wheel' to 'video' with the id of '44'. If you want to have
450 access to the dri devices please add yourself to the video group
453 # pw groupmod video -m $USER
456 The menu.rc and loader.rc files will now be replaced during
457 upgrades. Please migrate local changes to menu.rc.local and
458 loader.rc.local instead.
461 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
462 strings and strip have been removed. The src.conf(5) knob
463 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
466 As ZFS requires more kernel stack pages than is the default on some
467 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
468 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
470 Please consider using 'options KSTACK_PAGES=X' where X is greater
471 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
474 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
475 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
476 default, i.e., they will not contain "::". For example, instead
477 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
478 to have a more specific match, such as different map entries for
479 IPv6:0:0 vs IPv6:0. This change requires that configuration
480 data (including maps, files, classes, custom ruleset, etc.) must
481 use the same format, so make certain such configuration data is
482 upgrading. As a very simple check search for patterns like
483 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
484 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
485 the cf option UseCompressedIPv6Addresses.
488 The default kernel entropy-processing algorithm is now
489 Fortuna, replacing Yarrow.
491 Assuming you have 'device random' in your kernel config
492 file, the configurations allow a kernel option to override
493 this default. You may choose *ONE* of:
495 options RANDOM_YARROW # Legacy /dev/random algorithm.
496 options RANDOM_DUMMY # Blocking-only driver.
498 If you have neither, you get Fortuna. For most people,
499 read no further, Fortuna will give a /dev/random that works
500 like it always used to, and the difference will be irrelevant.
502 If you remove 'device random', you get *NO* kernel-processed
503 entropy at all. This may be acceptable to folks building
504 embedded systems, but has complications. Carry on reading,
505 and it is assumed you know what you need.
507 *PLEASE* read random(4) and random(9) if you are in the
508 habit of tweaking kernel configs, and/or if you are a member
509 of the embedded community, wanting specific and not-usual
510 behaviour from your security subsystems.
512 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
513 random', you will NOT have a functioning /dev/random, and
514 many cryptographic features will not work, including SSH.
515 You may also find strange behaviour from the random(3) set
516 of library functions, in particular sranddev(3), srandomdev(3)
517 and arc4random(3). The reason for this is that the KERN_ARND
518 sysctl only returns entropy if it thinks it has some to
519 share, and with RANDOM_DUMMY or no 'device random' this
523 An additional fix for the issue described in the 20150614 sendmail
524 entry below has been been committed in revision 284717.
527 FreeBSD's old make (fmake) has been removed from the system. It is
528 available as the devel/fmake port or via pkg install fmake.
531 The fix for the issue described in the 20150614 sendmail entry
532 below has been been committed in revision 284436. The work
533 around described in that entry is no longer needed unless the
534 default setting is overridden by a confDH_PARAMETERS configuration
535 setting of '5' or pointing to a 512 bit DH parameter file.
538 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
539 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
540 and devel/kyua to version 0.20+ and adjust any calling code to work
541 with Kyuafile and kyua.
544 The import of openssl to address the FreeBSD-SA-15:10.openssl
545 security advisory includes a change which rejects handshakes
546 with DH parameters below 768 bits. sendmail releases prior
547 to 8.15.2 (not yet released), defaulted to a 512 bit
548 DH parameter setting for client connections. To work around
549 this interoperability, sendmail can be configured to use a
550 2048 bit DH parameter by:
552 1. Edit /etc/mail/`hostname`.mc
553 2. If a setting for confDH_PARAMETERS does not exist or
554 exists and is set to a string beginning with '5',
556 3. If a setting for confDH_PARAMETERS exists and is set to
557 a file path, create a new file with:
558 openssl dhparam -out /path/to/file 2048
559 4. Rebuild the .cf file:
560 cd /etc/mail/; make; make install
562 cd /etc/mail/; make restart
564 A sendmail patch is coming, at which time this file will be
568 Generation of legacy formatted entries have been disabled by default
569 in pwd_mkdb(8), as all base system consumers of the legacy formatted
570 entries were converted to use the new format by default when the new,
571 machine independent format have been added and supported since FreeBSD
574 Please see the pwd_mkdb(8) manual page for further details.
577 Clang and llvm have been upgraded to 3.6.1 release. Please see the
578 20141231 entry below for information about prerequisites and upgrading,
579 if you are not already using 3.5.0 or higher.
582 TI platform code switched to using vendor DTS files and this update
583 may break existing systems running on Beaglebone, Beaglebone Black,
586 - dtb files should be regenerated/reinstalled. Filenames are the
587 same but content is different now
588 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
589 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
590 addressing scheme is now pin 25 on /dev/gpioc3.
591 - Pandaboard: /etc/ttys should be updated, serial console device is
592 now /dev/ttyu2, not /dev/ttyu0
595 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
596 If you need the GNU extension from groff soelim(1), install groff
597 from package: pkg install groff, or via ports: textproc/groff.
600 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
601 defined in symlink(7); previously symlinks were silently ignored.
604 The const qualifier has been removed from iconv(3) to comply with
605 POSIX. The ports tree is aware of this from r384038 onwards.
608 Libraries specified by LIBADD in Makefiles must have a corresponding
609 DPADD_<lib> variable to ensure correct dependencies. This is now
610 enforced in src.libnames.mk.
613 From legacy ata(4) driver was removed support for SATA controllers
614 supported by more functional drivers ahci(4), siis(4) and mvs(4).
615 Kernel modules ataahci and ataadaptec were removed completely,
616 replaced by ahci and mvs modules respectively.
619 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
620 the 20141231 entry below for information about prerequisites and
621 upgrading, if you are not already using 3.5.0 or higher.
624 The 32-bit PowerPC kernel has been changed to a position-independent
625 executable. This can only be booted with a version of loader(8)
626 newer than January 31, 2015, so make sure to update both world and
627 kernel before rebooting.
630 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
631 but before r278950, the RNG was not seeded properly. Immediately
632 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
633 ssh keys or openssl keys) that were generated w/ a kernel from that
634 range. This does not affect programs that directly used /dev/random
635 or /dev/urandom. All userland uses of arc4random(3) are affected.
638 The autofs(4) ABI was changed in order to restore binary compatibility
639 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
643 The powerpc64 kernel has been changed to a position-independent
644 executable. This can only be booted with a new version of loader(8),
645 so make sure to update both world and kernel before rebooting.
648 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
649 only release, no new features have been added. Please see the 20141231
650 entry below for information about prerequisites and upgrading, if you
651 are not already using 3.5.0.
654 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
655 taken from the ELF Tool Chain project rather than GNU binutils. They
656 should be drop-in replacements, with the addition of arm64 support.
657 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
658 binutils tools, if necessary. See 20150805 for updated information.
661 The default Unbound configuration now enables remote control
662 using a local socket. Users who have already enabled the
663 local_unbound service should regenerate their configuration
664 by running "service local_unbound setup" as root.
667 The GNU texinfo and GNU info pages have been removed.
668 To be able to view GNU info pages please install texinfo from ports.
671 Clang, llvm and lldb have been upgraded to 3.5.0 release.
673 As of this release, a prerequisite for building clang, llvm and lldb is
674 a C++11 capable compiler and C++11 standard library. This means that to
675 be able to successfully build the cross-tools stage of buildworld, with
676 clang as the bootstrap compiler, your system compiler or cross compiler
677 should either be clang 3.3 or later, or gcc 4.8 or later, and your
678 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
681 On any standard FreeBSD 10.x or 11.x installation, where clang and
682 libc++ are on by default (that is, on x86 or arm), this should work out
685 On 9.x installations where clang is enabled by default, e.g. on x86 and
686 powerpc, libc++ will not be enabled by default, so libc++ should be
687 built (with clang) and installed first. If both clang and libc++ are
688 missing, build clang first, then use it to build libc++.
690 On 8.x and earlier installations, upgrade to 9.x first, and then follow
691 the instructions for 9.x above.
693 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
694 default, and do not build clang.
696 Many embedded systems are resource constrained, and will not be able to
697 build clang in a reasonable time, or in some cases at all. In those
698 cases, cross building bootable systems on amd64 is a workaround.
700 This new version of clang introduces a number of new warnings, of which
701 the following are most likely to appear:
705 This warns in two cases, for both C and C++:
706 * When the code is trying to take the absolute value of an unsigned
707 quantity, which is effectively a no-op, and almost never what was
708 intended. The code should be fixed, if at all possible. If you are
709 sure that the unsigned quantity can be safely cast to signed, without
710 loss of information or undefined behavior, you can add an explicit
711 cast, or disable the warning.
713 * When the code is trying to take an absolute value, but the called
714 abs() variant is for the wrong type, which can lead to truncation.
715 If you want to disable the warning instead of fixing the code, please
716 make sure that truncation will not occur, or it might lead to unwanted
719 -Wtautological-undefined-compare and
720 -Wundefined-bool-conversion
722 These warn when C++ code is trying to compare 'this' against NULL, while
723 'this' should never be NULL in well-defined C++ code. However, there is
724 some legacy (pre C++11) code out there, which actively abuses this
725 feature, which was less strictly defined in previous C++ versions.
727 Squid and openjdk do this, for example. The warning can be turned off
728 for C++98 and earlier, but compiling the code in C++11 mode might result
729 in unexpected behavior; for example, the parts of the program that are
730 unreachable could be optimized away.
733 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
734 kernel sources have been removed. The .h files remain, since some
735 utilities include them. This will need to be fixed later.
736 If "mount -t oldnfs ..." is attempted, it will fail.
737 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
738 the utilities will report errors.
741 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
742 directories to top level SUBDIR variable when their parent
743 directory is included in LOCAL_DIRS. Users with build systems with
744 such hierarchies and without SUBDIR entries in the parent
745 directory Makefiles should add them or add the directories to
749 faith(4) and faithd(8) have been removed from the base system. Faith
750 has been obsolete for a very long time.
753 vt(4), the new console driver, is enabled by default. It brings
754 support for Unicode and double-width characters, as well as
755 support for UEFI and integration with the KMS kernel video
758 You may need to update your console settings in /etc/rc.conf,
759 most probably the keymap. During boot, /etc/rc.d/syscons will
760 indicate what you need to do.
762 vt(4) still has issues and lacks some features compared to
763 syscons(4). See the wiki for up-to-date information:
764 https://wiki.freebsd.org/Newcons
766 If you want to keep using syscons(4), you can do so by adding
767 the following line to /boot/loader.conf:
771 pjdfstest has been integrated into kyua as an opt-in test suite.
772 Please see share/doc/pjdfstest/README for more details on how to
776 gperf has been removed from the base system for architectures
777 that use clang. Ports that require gperf will obtain it from the
781 pjdfstest has been moved from tools/regression/pjdfstest to
785 At svn r271982, The default linux compat kernel ABI has been adjusted
786 to 2.6.18 in support of the linux-c6 compat ports infrastructure
787 update. If you wish to continue using the linux-f10 compat ports,
788 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
789 encouraged to update their linux-compat packages to linux-c6 during
790 their next update cycle.
793 The ofwfb driver, used to provide a graphics console on PowerPC when
794 using vt(4), no longer allows mmap() of all physical memory. This
795 will prevent Xorg on PowerPC with some ATI graphics cards from
796 initializing properly unless x11-servers/xorg-server is updated to
800 The xdev targets have been converted to using TARGET and
801 TARGET_ARCH instead of XDEV and XDEV_ARCH.
804 The default unbound configuration has been modified to address
805 issues with reverse lookups on networks that use private
806 address ranges. If you use the local_unbound service, run
807 "service local_unbound setup" as root to regenerate your
808 configuration, then "service local_unbound reload" to load the
812 The GNU texinfo and GNU info pages are not built and installed
813 anymore, WITH_INFO knob has been added to allow to built and install
815 UPDATE: see 20150102 entry on texinfo's removal
818 The GNU readline library is now an INTERNALLIB - that is, it is
819 statically linked into consumers (GDB and variants) in the base
820 system, and the shared library is no longer installed. The
821 devel/readline port is available for third party software that
825 The Itanium architecture (ia64) has been removed from the list of
826 known architectures. This is the first step in the removal of the
830 Commit r268115 has added NFSv4.1 server support, merged from
831 projects/nfsv4.1-server. Since this includes changes to the
832 internal interfaces between the NFS related modules, a full
833 build of the kernel and modules will be necessary.
834 __FreeBSD_version has been bumped.
837 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
838 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
839 which differs from the behaviour controlled by this knob.)
842 Maximal length of the serial number in CTL was increased from 16 to
843 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
844 and ctld, need to be rebuilt to work with a new kernel.
847 The libatf-c and libatf-c++ major versions were downgraded to 0 and
848 1 respectively to match the upstream numbers. They were out of
849 sync because, when they were originally added to FreeBSD, the
850 upstream versions were not respected. These libraries are private
851 and not yet built by default, so renumbering them should be a
852 non-issue. However, unclean source trees will yield broken test
853 programs once the operator executes "make delete-old-libs" after a
856 Additionally, the atf-sh binary was made private by moving it into
857 /usr/libexec/. Already-built shell test programs will keep the
858 path to the old binary so they will break after "make delete-old"
861 If you are using WITH_TESTS=yes (not the default), wipe the object
862 tree and rebuild from scratch to prevent spurious test failures.
863 This is only needed once: the misnumbered libraries and misplaced
864 binaries have been added to OptionalObsoleteFiles.inc so they will
865 be removed during a clean upgrade.
868 Clang and llvm have been upgraded to 3.4.1 release.
871 We bogusly installed src.opts.mk in /usr/share/mk. This file should
872 be removed to avoid issues in the future (and has been added to
876 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
877 past, it affected all builds that used the bsd.*.mk files. The old
878 behavior was a bug, but people may have relied upon it. To get this
879 behavior back, you can .include /etc/src.conf from /etc/make.conf
880 (which is still global and isn't changed). This also changes the
881 behavior of incremental builds inside the tree of individual
882 directories. Set MAKESYSPATH to ".../share/mk" to do that.
883 Although this has survived make universe and some upgrade scenarios,
884 other upgrade scenarios may have broken. At least one form of
885 temporary breakage was fixed with MAKESYSPATH settings for buildworld
886 as well... In cases where MAKESYSPATH isn't working with this
887 setting, you'll need to set it to the full path to your tree.
889 One side effect of all this cleaning up is that bsd.compiler.mk
890 is no longer implicitly included by bsd.own.mk. If you wish to
891 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
895 The lindev device has been removed since /dev/full has been made a
896 standard device. __FreeBSD_version has been bumped.
899 The knob WITHOUT_VI was added to the base system, which controls
900 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
901 in order to reorder files share/termcap and didn't build ex(1) as a
902 build tool, so building/installing with WITH_VI is highly advised for
903 build hosts for older releases.
905 This issue has been fixed in stable/9 and stable/10 in r277022 and
906 r276991, respectively.
909 The YES_HESIOD knob has been removed. It has been obsolete for
910 a decade. Please move to using WITH_HESIOD instead or your builds
911 will silently lack HESIOD.
914 The uart(4) driver has been changed with respect to its handling
915 of the low-level console. Previously the uart(4) driver prevented
916 any process from changing the baudrate or the CLOCAL and HUPCL
917 control flags. By removing the restrictions, operators can make
918 changes to the serial console port without having to reboot.
919 However, when getty(8) is started on the serial device that is
920 associated with the low-level console, a misconfigured terminal
921 line in /etc/ttys will now have a real impact.
922 Before upgrading the kernel, make sure that /etc/ttys has the
923 serial console device configured as 3wire without baudrate to
924 preserve the previous behaviour. E.g:
925 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
928 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
929 to improve performance. To re-enable it, if needed, run rpcbind
930 with command line option -W.
933 Switched back to the GPL dtc compiler due to updates in the upstream
934 dts files not being supported by the BSDL dtc compiler. You will need
935 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
936 may result while building dtb files during a kernel build if you fail
937 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
940 Clang and llvm have been upgraded to 3.4 release.
943 The nve(4) driver has been removed. Please use the nfe(4) driver
944 for NVIDIA nForce MCP Ethernet adapters instead.
947 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
948 This could cause certain C++ applications using shared libraries built
949 against the previous version of libc++ to crash. The incompatibility
950 has now been fixed, but any C++ applications or shared libraries built
951 between r261283 and r261801 should be recompiled.
954 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
955 capability mode support. Please note that enabling the feature in
956 kernel is still highly recommended.
959 OpenSSH is now built with sandbox support, and will use sandbox as
960 the default privilege separation method. This requires Capsicum
961 capability mode support in kernel.
964 The libelf and libdwarf libraries have been updated to newer
965 versions from upstream. Shared library version numbers for
966 these two libraries were bumped. Any ports or binaries
967 requiring these two libraries should be recompiled.
968 __FreeBSD_version is bumped to 1100006.
971 If a Makefile in a tests/ directory was auto-generating a Kyuafile
972 instead of providing an explicit one, this would prevent such
973 Makefile from providing its own Kyuafile in the future during
974 NO_CLEAN builds. This has been fixed in the Makefiles but manual
975 intervention is needed to clean an objdir if you use NO_CLEAN:
976 # find /usr/obj -name Kyuafile | xargs rm -f
979 The behavior of gss_pseudo_random() for the krb5 mechanism
980 has changed, for applications requesting a longer random string
981 than produced by the underlying enctype's pseudo-random() function.
982 In particular, the random string produced from a session key of
983 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
984 be different at the 17th octet and later, after this change.
985 The counter used in the PRF+ construction is now encoded as a
986 big-endian integer in accordance with RFC 4402.
987 __FreeBSD_version is bumped to 1100004.
990 The WITHOUT_ATF build knob has been removed and its functionality
991 has been subsumed into the more generic WITHOUT_TESTS. If you were
992 using the former to disable the build of the ATF libraries, you
993 should change your settings to use the latter.
996 The default version of mtree is nmtree which is obtained from
997 NetBSD. The output is generally the same, but may vary
998 slightly. If you found you need identical output adding
999 "-F freebsd9" to the command line should do the trick. For the
1000 time being, the old mtree is available as fmtree.
1003 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1004 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1005 1.1.4_8 and verify bsdyml not linked in, before running "make
1007 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1009 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1012 The stable/10 branch has been created in subversion from head
1016 The rc.d/jail script has been updated to support jail(8)
1017 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1018 for per-jail configuration are automatically converted to
1019 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1020 This is transparently backward compatible. See below about some
1021 incompatibilities and rc.conf(5) manual page for more details.
1023 These variables are now deprecated in favor of jail(8) configuration
1024 file. One can use "rc.d/jail config <jname>" command to generate
1025 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1026 running the jail(8) utility. The default pathname of the
1027 configuration file is /etc/jail.conf and can be specified by
1028 using $jail_conf or $jail_<jname>_conf variables.
1030 Please note that jail_devfs_ruleset accepts an integer at
1031 this moment. Please consider to rewrite the ruleset name
1035 BIND has been removed from the base system. If all you need
1036 is a local resolver, simply enable and start the local_unbound
1037 service instead. Otherwise, several versions of BIND are
1038 available in the ports tree. The dns/bind99 port is one example.
1040 With this change, nslookup(1) and dig(1) are no longer in the base
1041 system. Users should instead use host(1) and drill(1) which are
1042 in the base system. Alternatively, nslookup and dig can
1043 be obtained by installing the dns/bind-tools port.
1046 With the addition of unbound(8), a new unbound user is now
1047 required during installworld. "mergemaster -p" can be used to
1048 add the user prior to installworld, as documented in the handbook.
1051 OpenSSH is now built with DNSSEC support, and will by default
1052 silently trust signed SSHFP records. This can be controlled with
1053 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1054 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1057 The GNU Compiler Collection and C++ standard library (libstdc++)
1058 are no longer built by default on platforms where clang is the system
1059 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1060 options in src.conf.
1063 The PROCDESC kernel option is now part of the GENERIC kernel
1064 configuration and is required for the rwhod(8) to work.
1065 If you are using custom kernel configuration, you should include
1069 The API and ABI related to the Capsicum framework was modified
1070 in backward incompatible way. The userland libraries and programs
1071 have to be recompiled to work with the new kernel. This includes the
1072 following libraries and programs, but the whole buildworld is
1073 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1074 kdump, procstat, rwho, rwhod, uniq.
1077 AES-NI intrinsic support has been added to gcc. The AES-NI module
1078 has been updated to use this support. A new gcc is required to build
1079 the aesni module on both i386 and amd64.
1082 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1083 Thus "device padlock_rng" and "device rdrand_rng" should be
1084 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1087 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1088 enables just the iconv* functionality and is now on by default.
1089 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1090 compatibility. Set WITHOUT_ICONV to build the old way.
1091 If you have been using WITH_ICONV before, you will very likely
1092 need to turn on WITH_LIBICONV_COMPAT.
1095 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1096 Illumos origin, including ZFS. If you have INVARIANTS in your
1097 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1099 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1100 locks if WITNESS option was set. Because that generated a lot of
1101 witness(9) reports and all of them were believed to be false
1102 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1103 can be used to achieve the previous behavior.
1106 Timer values in IPv6 data structures now use time_uptime instead
1107 of time_second. Although this is not a user-visible functional
1108 change, userland utilities which directly use them---ndp(8),
1109 rtadvd(8), and rtsold(8) in the base system---need to be updated
1110 to r253970 or later.
1113 find -delete can now delete the pathnames given as arguments,
1114 instead of only files found below them or if the pathname did
1115 not contain any slashes. Formerly, the following error message
1118 find: -delete: <path>: relative path potentially not safe
1120 Deleting the pathnames given as arguments can be prevented
1121 without error messages using -mindepth 1 or by changing
1122 directory and passing "." as argument to find. This works in the
1123 old as well as the new version of find.
1126 Behavior of devfs rules path matching has been changed.
1127 Pattern is now always matched against fully qualified devfs
1128 path and slash characters must be explicitly matched by
1129 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1130 subdirectories must be reviewed.
1133 The default ARM ABI has changed to the ARM EABI. The old ABI is
1134 incompatible with the ARM EABI and all programs and modules will
1135 need to be rebuilt to work with a new kernel.
1137 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1139 NOTE: Support for the old ABI will be removed in the future and
1140 users are advised to upgrade.
1143 pkg_install has been disconnected from the build if you really need it
1144 you should add WITH_PKGTOOLS in your src.conf(5).
1147 Most of network statistics structures were changed to be able
1148 keep 64-bits counters. Thus all tools, that work with networking
1149 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1152 Fix a bug that allowed a tracing process (e.g. gdb) to write
1153 to a memory-mapped file in the traced process's address space
1154 even if neither the traced process nor the tracing process had
1155 write access to that file.
1158 CVS has been removed from the base system. An exact copy
1159 of the code is available from the devel/cvs port.
1162 Some people report the following error after the switch to bmake:
1164 make: illegal option -- J
1165 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1167 *** [buildworld] Error code 2
1169 this likely due to an old instance of make in
1170 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1171 which src/Makefile will use that blindly, if it exists, so if
1172 you see the above error:
1174 rm -rf `make -V MAKEPATH`
1179 Use bmake by default.
1180 Whereas before one could choose to build with bmake via
1181 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1182 make. The goal is to remove these knobs for 10-RELEASE.
1184 It is worth noting that bmake (like gmake) treats the command
1185 line as the unit of failure, rather than statements within the
1186 command line. Thus '(cd some/where && dosomething)' is safer
1187 than 'cd some/where; dosomething'. The '()' allows consistent
1188 behavior in parallel build.
1191 Fix a bug that allows NFS clients to issue READDIR on files.
1194 The WITHOUT_IDEA option has been removed because
1195 the IDEA patent expired.
1198 The sysctl which controls TRIM support under ZFS has been renamed
1199 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1203 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1204 rather than creating it's own in the temporary directory in
1205 order allow access to bootstrapped versions of tools such as
1206 install and mtree. When upgrading from version of FreeBSD where
1207 the install command does not support -l, you will need to
1208 install a new mergemaster command if mergemaster -p is required.
1209 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1213 Legacy ATA stack, disabled and replaced by new CAM-based one since
1214 FreeBSD 9.0, completely removed from the sources. Kernel modules
1215 atadisk and atapi*, user-level tools atacontrol and burncd are
1216 removed. Kernel option `options ATA_CAM` is now permanently enabled
1220 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1221 and socketpair(2). Software, in particular Kerberos, may
1222 automatically detect and use these during building. The resulting
1223 binaries will not work on older kernels.
1226 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1227 information, see the respective 20130304 entry).
1230 Recent commits to callout(9) changed the size of struct callout,
1231 so the KBI is probably heavily disturbed. Also, some functions
1232 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1233 by macros. Every kernel module using it won't load, so rebuild
1236 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1237 but does not initialize by default (because of the new CTL_DISABLE
1238 option) to save memory. To re-enable it, remove the CTL_DISABLE
1239 option from the kernel config file or set kern.cam.ctl.disable=0
1240 in /boot/loader.conf.
1243 The ctl device has been disabled in GENERIC for i386 and amd64.
1244 This was done due to the extra memory being allocated at system
1245 initialisation time by the ctl driver which was only used if
1246 a CAM target device was created. This makes a FreeBSD system
1247 unusable on 128MB or less of RAM.
1250 A new compression method (lz4) has been merged to -HEAD. Please
1251 refer to zpool-features(7) for more information.
1253 Please refer to the "ZFS notes" section of this file for information
1254 on upgrading boot ZFS pools.
1257 A BSD-licensed patch(1) variant has been added and is installed
1258 as bsdpatch, being the GNU version the default patch.
1259 To inverse the logic and use the BSD-licensed one as default,
1260 while having the GNU version installed as gnupatch, rebuild
1261 and install world with the WITH_BSD_PATCH knob set.
1264 Due to the use of the new -l option to install(1) during build
1265 and install, you must take care not to directly set the INSTALL
1266 make variable in your /etc/make.conf, /etc/src.conf, or on the
1267 command line. If you wish to use the -C flag for all installs
1268 you may be able to add INSTALL+=-C to /etc/make.conf or
1272 The install(1) option -M has changed meaning and now takes an
1273 argument that is a file or path to append logs to. In the
1274 unlikely event that -M was the last option on the command line
1275 and the command line contained at least two files and a target
1276 directory the first file will have logs appended to it. The -M
1277 option served little practical purpose in the last decade so its
1278 use is expected to be extremely rare.
1281 After switching to Clang as the default compiler some users of ZFS
1282 on i386 systems started to experience stack overflow kernel panics.
1283 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1286 GEOM_LABEL now mangles label names read from file system metadata.
1287 Mangling affect labels containing spaces, non-printable characters,
1288 '%' or '"'. Device names in /etc/fstab and other places may need to
1292 By default, only the 10 most recent kernel dumps will be saved. To
1293 restore the previous behaviour (no limit on the number of kernel dumps
1294 stored in the dump directory) add the following line to /etc/rc.conf:
1299 With the addition of auditdistd(8), a new auditdistd user is now
1300 required during installworld. "mergemaster -p" can be used to
1301 add the user prior to installworld, as documented in the handbook.
1304 The sin6_scope_id member variable in struct sockaddr_in6 is now
1305 filled by the kernel before passing the structure to the userland via
1306 sysctl or routing socket. This means the KAME-specific embedded scope
1307 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1308 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1309 __FreeBSD_version is bumped to 1000025.
1312 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1313 This means that the world and kernel will be compiled with clang
1314 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1315 and /usr/bin/cpp. To disable this behavior and revert to building
1316 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1317 of current may need to bootstrap WITHOUT_CLANG first if the clang
1318 build fails (its compatibility window doesn't extend to the 9 stable
1322 The IPFIREWALL_FORWARD kernel option has been removed. Its
1323 functionality now turned on by default.
1326 The ZERO_COPY_SOCKET kernel option has been removed and
1327 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1328 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1329 mechanism which is not safe and may result in kernel crashes.
1330 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1331 driver supports disposeable external page sized mbuf storage.
1332 Proper replacements for both zero-copy mechanisms are under
1333 consideration and will eventually lead to complete removal
1334 of the two kernel options.
1337 The IPv4 network stack has been converted to network byte
1338 order. The following modules need to be recompiled together
1339 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1340 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1343 Support for non-MPSAFE filesystems was removed from VFS. The
1344 VFS_VERSION was bumped, all filesystem modules shall be
1348 All the non-MPSAFE filesystems have been disconnected from
1349 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1350 portalfs, smbfs, xfs.
1353 The interface cloning API and ABI has changed. The following
1354 modules need to be recompiled together with kernel:
1355 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1356 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1357 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1360 The sdhci driver was split in two parts: sdhci (generic SD Host
1361 Controller logic) and sdhci_pci (actual hardware driver).
1362 No kernel config modifications are required, but if you
1363 load sdhc as a module you must switch to sdhci_pci instead.
1366 Import the FUSE kernel and userland support into base system.
1369 The GNU sort(1) program has been removed since the BSD-licensed
1370 sort(1) has been the default for quite some time and no serious
1371 problems have been reported. The corresponding WITH_GNU_SORT
1375 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1376 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1380 The net80211(4) ABI has been changed to allow for improved driver
1381 PS-POLL and power-save support. All wireless drivers need to be
1382 recompiled to work with the new kernel.
1385 The random(4) support for the VIA hardware random number
1386 generator (`PADLOCK') is no longer enabled unconditionally.
1387 Add the padlock_rng device in the custom kernel config if
1388 needed. The GENERIC kernels on i386 and amd64 do include the
1389 device, so the change only affects the custom kernel
1393 The pf(4) packet filter ABI has been changed. pfctl(8) and
1394 snmp_pf module need to be recompiled to work with new kernel.
1397 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1398 to -HEAD. Pools that have empty_bpobj in active state can not be
1399 imported read-write with ZFS implementations that do not support
1400 this feature. For more information read the zpool-features(5)
1404 The sparc64 ZFS loader has been changed to no longer try to auto-
1405 detect ZFS providers based on diskN aliases but now requires these
1406 to be explicitly listed in the OFW boot-device environment variable.
1409 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1410 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1411 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1414 The following sysctls and tunables have been renamed for consistency
1415 with other variables:
1416 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1417 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1420 The sort utility has been replaced with BSD sort. For now, GNU sort
1421 is also available as "gnusort" or the default can be set back to
1422 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1423 installed as "bsdsort".
1426 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1427 Starting with this version the old system of ZFS pool versioning
1428 is superseded by "feature flags". This concept enables forward
1429 compatibility against certain future changes in functionality of ZFS
1430 pools. The first read-only compatible "feature flag" for ZFS pools
1431 is named "com.delphix:async_destroy". For more information
1432 read the new zpool-features(5) manual page.
1433 Please refer to the "ZFS notes" section of this file for information
1434 on upgrading boot ZFS pools.
1437 The malloc(3) implementation embedded in libc now uses sources imported
1438 as contrib/jemalloc. The most disruptive API change is to
1439 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1440 delete it prior to installworld, and optionally re-create it using the
1441 new format after rebooting. See malloc.conf(5) for details
1442 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1446 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1447 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1448 now spelled mips. This is to aid compatibility with third-party
1449 software that expects this naming scheme in uname(3). Little-endian
1450 settings are unchanged. If you are updating a big-endian mips64 machine
1451 from before this change, you may need to set MACHINE_ARCH=mips64 in
1452 your environment before the new build system will recognize your machine.
1455 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1459 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1460 nullfs(5) did not pass through all behaviours to the underlying layer,
1461 as a result if we bound to a socket on the lower layer we could connect
1462 only to the lower path; if we bound to the upper layer we could connect
1463 only to the upper path. The new behavior is one can connect to both the
1464 lower and the upper paths regardless what layer path one binds to.
1467 The getifaddrs upgrade path broken with 20111215 has been restored.
1468 If you have upgraded in between 20111215 and 20120209 you need to
1469 recompile libc again with your kernel. You still need to recompile
1470 world to be able to configure CARP but this restriction already
1471 comes from 20111215.
1474 The set_rcvar() function has been removed from /etc/rc.subr. All
1475 base and ports rc.d scripts have been updated, so if you have a
1476 port installed with a script in /usr/local/etc/rc.d you can either
1477 hand-edit the rcvar= line, or reinstall the port.
1479 An easy way to handle the mass-update of /etc/rc.d:
1480 rm /etc/rc.d/* && mergemaster -i
1483 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1484 on the current CPU and prevents other threads from running.
1485 This behavior can be reverted using the kern.stop_scheduler_on_panic
1487 The new behavior can be incompatible with kern.sync_on_panic.
1490 The carp(4) facility has been changed significantly. Configuration
1491 of the CARP protocol via ifconfig(8) has changed, as well as format
1492 of CARP events submitted to devd(8) has changed. See manual pages
1493 for more information. The arpbalance feature of carp(4) is currently
1494 not supported anymore.
1496 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1497 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1498 need to be recompiled.
1501 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1505 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1506 explicitely support non-MPSAFE filesystems.
1507 It is on by default for all supported platform at this present
1511 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1512 i386 and pc98 GENERIC kernel configuration files.
1515 sysinstall has been removed
1518 The stable/9 branch created in subversion. This corresponds to the
1519 RELENG_9 branch in CVS.
1525 Avoid using make -j when upgrading. While generally safe, there are
1526 sometimes problems using -j to upgrade. If your upgrade fails with
1527 -j, please try again without -j. From time to time in the past there
1528 have been problems using -j with buildworld and/or installworld. This
1529 is especially true when upgrading between "distant" versions (eg one
1530 that cross a major release boundary or several minor releases, or when
1531 several months have passed on the -current branch).
1533 Sometimes, obscure build problems are the result of environment
1534 poisoning. This can happen because the make utility reads its
1535 environment when searching for values for global variables. To run
1536 your build attempts in an "environmental clean room", prefix all make
1537 commands with 'env -i '. See the env(1) manual page for more details.
1539 When upgrading from one major version to another it is generally best
1540 to upgrade to the latest code in the currently installed branch first,
1541 then do an upgrade to the new branch. This is the best-tested upgrade
1542 path, and has the highest probability of being successful. Please try
1543 this approach before reporting problems with a major version upgrade.
1545 When upgrading a live system, having a root shell around before
1546 installing anything can help undo problems. Not having a root shell
1547 around can lead to problems if pam has changed too much from your
1548 starting point to allow continued authentication after the upgrade.
1550 This file should be read as a log of events. When a later event changes
1551 information of a prior event, the prior event should not be deleted.
1552 Instead, a pointer to the entry with the new information should be
1553 placed in the old entry. Readers of this file should also sanity check
1554 older entries before relying on them blindly. Authors of new entries
1555 should write them with this in mind.
1559 When upgrading the boot ZFS pool to a new version, always follow
1562 1.) recompile and reinstall the ZFS boot loader and boot block
1563 (this is part of "make buildworld" and "make installworld")
1565 2.) update the ZFS boot block on your boot drive
1567 The following example updates the ZFS boot block on the first
1568 partition (freebsd-boot) of a GPT partitioned drive ada0:
1569 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1571 Non-boot pools do not need these updates.
1575 If you are updating from a prior version of FreeBSD (even one just
1576 a few days old), you should follow this procedure. It is the most
1577 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1579 make kernel-toolchain
1580 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1581 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1583 To test a kernel once
1584 ---------------------
1585 If you just want to boot a kernel once (because you are not sure
1586 if it works, or if you want to boot a known bad kernel to provide
1587 debugging information) run
1588 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1589 nextboot -k testkernel
1591 To just build a kernel when you know that it won't mess you up
1592 --------------------------------------------------------------
1593 This assumes you are already running a CURRENT system. Replace
1594 ${arch} with the architecture of your machine (e.g. "i386",
1595 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1597 cd src/sys/${arch}/conf
1598 config KERNEL_NAME_HERE
1599 cd ../compile/KERNEL_NAME_HERE
1604 If this fails, go to the "To build a kernel" section.
1606 To rebuild everything and install it on the current system.
1607 -----------------------------------------------------------
1608 # Note: sometimes if you are running current you gotta do more than
1609 # is listed here if you are upgrading from a really old current.
1611 <make sure you have good level 0 dumps>
1613 make kernel KERNCONF=YOUR_KERNEL_HERE
1615 <reboot in single user> [3]
1622 To cross-install current onto a separate partition
1623 --------------------------------------------------
1624 # In this approach we use a separate partition to hold
1625 # current's root, 'usr', and 'var' directories. A partition
1626 # holding "/", "/usr" and "/var" should be about 2GB in
1629 <make sure you have good level 0 dumps>
1632 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1633 <maybe newfs current's root partition>
1634 <mount current's root partition on directory ${CURRENT_ROOT}>
1635 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1636 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1637 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1638 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1639 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1640 <reboot into current>
1641 <do a "native" rebuild/install as described in the previous section>
1642 <maybe install compatibility libraries from ports/misc/compat*>
1646 To upgrade in-place from stable to current
1647 ----------------------------------------------
1648 <make sure you have good level 0 dumps>
1650 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1652 <reboot in single user> [3]
1659 Make sure that you've read the UPDATING file to understand the
1660 tweaks to various things you need. At this point in the life
1661 cycle of current, things change often and you are on your own
1662 to cope. The defaults can also change, so please read ALL of
1663 the UPDATING entries.
1665 Also, if you are tracking -current, you must be subscribed to
1666 freebsd-current@freebsd.org. Make sure that before you update
1667 your sources that you have read and understood all the recent
1668 messages there. If in doubt, please track -stable which has
1669 much fewer pitfalls.
1671 [1] If you have third party modules, such as vmware, you
1672 should disable them at this point so they don't crash your
1675 [3] From the bootblocks, boot -s, and then do
1680 adjkerntz -i # if CMOS is wall time
1681 Also, when doing a major release upgrade, it is required that
1682 you boot into single user mode to do the installworld.
1684 [4] Note: This step is non-optional. Failure to do this step
1685 can result in a significant reduction in the functionality of the
1686 system. Attempting to do it by hand is not recommended and those
1687 that pursue this avenue should read this file carefully, as well
1688 as the archives of freebsd-current and freebsd-hackers mailing lists
1689 for potential gotchas. The -U option is also useful to consider.
1690 See mergemaster(8) for more information.
1692 [5] Usually this step is a noop. However, from time to time
1693 you may need to do this if you get unknown user in the following
1694 step. It never hurts to do it all the time. You may need to
1695 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1696 install) after the buildworld before this step if you last updated
1697 from current before 20130425 or from -stable before 20130430.
1699 [6] This only deletes old files and directories. Old libraries
1700 can be deleted by "make delete-old-libs", but you have to make
1701 sure that no program is using those libraries anymore.
1703 [8] In order to have a kernel that can run the 4.x binaries needed to
1704 do an installworld, you must include the COMPAT_FREEBSD4 option in
1705 your kernel. Failure to do so may leave you with a system that is
1706 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1707 required to run the 5.x binaries on more recent kernels. And so on
1708 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1710 Make sure that you merge any new devices from GENERIC since the
1711 last time you updated your kernel config file.
1713 [9] When checking out sources, you must include the -P flag to have
1714 cvs prune empty directories.
1716 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1717 "?=" instead of the "=" assignment operator, so that buildworld can
1718 override the CPUTYPE if it needs to.
1720 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1721 not on the command line, or in /etc/make.conf. buildworld will
1722 warn if it is improperly defined.
1725 This file contains a list, in reverse chronological order, of major
1726 breakages in tracking -current. It is not guaranteed to be a complete
1727 list of such breakages, and only contains entries since September 23, 2011.
1728 If you need to see UPDATING entries from before that date, you will need
1729 to fetch an UPDATING file from an older FreeBSD release.
1731 Copyright information:
1733 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1735 Redistribution, publication, translation and use, with or without
1736 modification, in full or in part, in any form or format of this
1737 document are permitted without further permission from the author.
1739 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1740 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1741 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1742 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1743 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1744 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1745 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1746 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1747 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1748 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1749 POSSIBILITY OF SUCH DAMAGE.
1751 Contact Warner Losh if you have any questions about your use of