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.
19 20180508 p10 FreeBSD-SA-18:06.debugreg
21 FreeBSD-EN-18:06.tzdata
23 Fix mishandling of x86 debug exceptions. [SA-18:06.debugreg]
25 Fix multiple small kernel memory disclosures. [EN-18:05.mem]
27 Update timezone database information. [EN-18:06.tzdata]
29 20180404 p9 FreeBSD-SA-18:04.vt
30 FreeBSD-SA-18:05.ipsec
31 FreeBSD-EN-18:03.tzdata
34 Fix vt console memory disclosure. [SA-18:04.vt]
36 Fix ipsec crash or denial of service. [SA-18:05.ipsec]
38 Update timezone database information. [EN-18:03.tzdata]
40 Fix multiple small kernel memory disclosures. [EN-18:04.mem]
42 20180314 p8 FreeBSD-SA-18:03.speculative_execution
44 Add mitigations for two classes of speculative execution vulnerabilities
47 20180307 p7 FreeBSD-SA-18:01.ipsec
49 FreeBSD-EN-18:01.tzdata
52 Fix ipsec validation and use-after-free. [SA-18:01.ipsec]
54 Fix multiple vulnerabilities in ntp. [SA-18:02.ntp]
56 Update timezone database information. [EN-18:01.tzdata]
58 Update file(1) to new version with security update. [EN-18:02.file]
60 20171209 p6 FreeBSD-SA-17:12.openssl
62 Fix multiple vulnerabilities of OpenSSL.
64 20171129 p5 FreeBSD-SA-17:11.openssl
66 Fix multiple vulnerabilities of OpenSSL.
68 20171115 p4 FreeBSD-SA-17:08.ptrace
69 FreeBSD-SA-17:10.kldstat
71 Fix ptrace(2) vulnerability. [SA-17:08.ptrace]
73 Fix kldstat(2) vulnerability. [SA-17:10.kldstat]
75 20171102 p3 FreeBSD-EN-17:09.tzdata
77 Update timezone database information. [EN-17:09]
79 20171017 p2 FreeBSD-SA-17:07.wpa
81 Fix WPA2 protocol vulnerability. [SA-17:07]
83 20170810 p1 FreeBSD-SA-17:06.openssh
87 Fix OpenSSH Denial of Service vulnerability. [SA-17:06]
89 Fix VNET kernel panic with asynchronous I/O. [EN-17:07]
91 Fix pf(4) housekeeping thread causes kernel panic. [EN-17:08]
97 arm64 builds now use the base system LLD 4.0.0 linker by default,
98 instead of requiring that the aarch64-binutils port or package be
99 installed. To continue using aarch64-binutils, set
100 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
103 The ctl.ko module no longer implements the iSCSI target frontend:
104 cfiscsi.ko does instead.
106 If building cfiscsi.ko as a kernel module, the module can be loaded
107 via one of the following methods:
108 - `cfiscsi_load="YES"` in loader.conf(5).
109 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
110 - ctladm(8)/ctld(8), when compiled with iSCSI support
111 (`WITH_ISCSI=yes` in src.conf(5))
113 Please see cfiscsi(4) for more details.
116 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
117 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
118 same source (previously, the dependency of mmcsd.ko on mmc.ko was
119 missing, but mmcsd.ko now will refuse to load if it is incompatible
123 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
124 use any explicitly assigned loopback address available in the jail
125 instead of using the first assigned address of the jail.
128 As of r316810 for ipfilter, keep frags is no longer assumed when
129 keep state is specified in a rule. r316810 aligns ipfilter with
130 documentation in man pages separating keep frags from keep state.
131 This allows keep state to specified without forcing keep frags
132 and allows keep frags to be specified independently of keep state.
133 To maintain previous behaviour, also specify keep frags with
134 keep state (as documented in ipf.conf.5).
137 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
138 Please see the 20141231 entry below for information about prerequisites
139 and upgrading, if you are not already using clang 3.5.0 or higher.
142 The code that provides support for ZFS .zfs/ directory functionality
143 has been reimplemented. It's not possible now to create a snapshot
144 by mkdir under .zfs/snapshot/. That should be the only user visible
148 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
149 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
150 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
151 and now NAT-T is supported by default. Security associations now use
152 the single namespace for SPI allocation, so if you use several manually
153 configured security associations with the same SPI, this configuration
157 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
158 Please see the 20141231 entry below for information about prerequisites
159 and upgrading, if you are not already using clang 3.5.0 or higher.
162 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
163 Please see the 20141231 entry below for information about prerequisites
164 and upgrading, if you are not already using clang 3.5.0 or higher.
167 The layout of the pmap structure has changed for powerpc to put the pmap
168 statistics at the front for all CPU variations. libkvm(3) and all tools
169 that link against it need to be recompiled.
172 isl(4) and cyapa(4) drivers now require a new driver,
173 chromebook_platform(4), to work properly on Chromebook-class hardware.
174 On other types of hardware the drivers may need to be configured using
175 device hints. Please see the corresponding manual pages for details.
178 Relocatable object files with the extension of .So have been renamed
179 to use an extension of .pico instead. The purpose of this change is
180 to avoid a name clash with shared libraries on case-insensitive file
181 systems. On those file systems, foo.So is the same file as foo.so.
184 The libc stub for the pipe(2) system call has been replaced with
185 a wrapper that calls the pipe2(2) system call and the pipe(2)
186 system call is now only implemented by the kernels that include
187 "options COMPAT_FREEBSD10" in their config file (this is the
188 default). Users should ensure that this option is enabled in
189 their kernel or upgrade userspace to r302092 before upgrading their
193 CAM will now strip leading spaces from SCSI disks' serial numbers.
194 This will effect users who create UFS filesystems on SCSI disks using
195 those disk's diskid device nodes. For example, if /etc/fstab
196 previously contained a line like
197 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
198 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
199 transforms like gmirror may also be affected. ZFS users should
203 The bitstring(3) API has been updated with new functionality and
204 improved performance. But it is binary-incompatible with the old API.
205 Objects built with the new headers may not be linked against objects
206 built with the old headers.
209 The brk and sbrk functions have been removed from libc on arm64.
210 Binutils from ports has been updated to not link to these
211 functions and should be updated to the latest version before
212 installing a new libc.
215 The armv6 port now defaults to hard float ABI. Limited support
216 for running both hardfloat and soft float on the same system
217 is available using the libraries installed with -DWITH_LIBSOFT.
218 This has only been tested as an upgrade path for installworld
219 and packages may fail or need manual intervention to run. New
220 packages will be needed.
222 To update an existing self-hosted armv6hf system, you must add
223 TARGET_ARCH=armv6 on the make command line for both the build
224 and the install steps.
227 Kernel modules compiled outside of a kernel build now default to
228 installing to /boot/modules instead of /boot/kernel. Many kernel
229 modules built this way (such as those in ports) already overrode
230 KMODDIR explicitly to install into /boot/modules. However,
231 manually building and installing a module from /sys/modules will
232 now install to /boot/modules instead of /boot/kernel.
235 The CAM I/O scheduler has been committed to the kernel. There should be
236 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
237 list of known rogues that claim support for this but actually corrupt
238 data is believed to be complete, be on the lookout for data
239 corruption. The known rogue list is believed to be complete:
241 o Crucial MX100, M550 drives with MU01 firmware.
242 o Micron M510 and M550 drives with MU01 firmware.
243 o Micron M500 prior to MU07 firmware
244 o Samsung 830, 840, and 850 all firmwares
245 o FCCT M500 all firmwares
247 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
248 with working NCQ TRIM. For Micron branded drives, see your sales rep for
249 updated firmware. Black listed drives will work correctly because these
250 drives work correctly so long as no NCQ TRIMs are sent to them. Given
251 this list is the same as found in Linux, it's believed there are no
252 other rogues in the market place. All other models from the above
255 To be safe, if you are at all concerned, you can quirk each of your
256 drives to prevent NCQ from being sent by setting:
257 kern.cam.ada.X.quirks="0x2"
258 in loader.conf. If the drive requires the 4k sector quirk, set the
262 The FAST_DEPEND build option has been removed and its functionality is
263 now the one true way. The old mkdep(1) style of 'make depend' has
264 been removed. See 20160311 for further details.
267 Resource range types have grown from unsigned long to uintmax_t. All
268 drivers, and anything using libdevinfo, need to be recompiled.
271 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
272 builds. It no longer runs mkdep(1) during 'make depend', and the
273 'make depend' stage can safely be skipped now as it is auto ran
274 when building 'make all' and will generate all SRCS and DPSRCS before
275 building anything else. Dependencies are gathered at compile time with
276 -MF flags kept in separate .depend files per object file. Users should
277 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
281 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
282 kernel modules. Therefore, if you load any kernel modules at boot time,
283 please install the boot loaders after you install the kernel, but before
287 make kernel KERNCONF=YOUR_KERNEL_HERE
288 make -C sys/boot install
289 <reboot in single user>
291 Then follow the usual steps, described in the General Notes section,
295 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
296 see the 20141231 entry below for information about prerequisites and
297 upgrading, if you are not already using clang 3.5.0 or higher.
300 The AIO subsystem is now a standard part of the kernel. The
301 VFS_AIO kernel option and aio.ko kernel module have been removed.
302 Due to stability concerns, asynchronous I/O requests are only
303 permitted on sockets and raw disks by default. To enable
304 asynchronous I/O requests on all file types, set the
305 vfs.aio.enable_unsafe sysctl to a non-zero value.
308 The ELF object manipulation tool objcopy is now provided by the
309 ELF Tool Chain project rather than by GNU binutils. It should be a
310 drop-in replacement, with the addition of arm64 support. The
311 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
312 to obtain the GNU version if necessary.
315 Building ZFS pools on top of zvols is prohibited by default. That
316 feature has never worked safely; it's always been prone to deadlocks.
317 Using a zvol as the backing store for a VM guest's virtual disk will
318 still work, even if the guest is using ZFS. Legacy behavior can be
319 restored by setting vfs.zfs.vol.recursive=1.
322 The NONE and HPN patches has been removed from OpenSSH. They are
323 still available in the security/openssh-portable port.
326 With the addition of ypldap(8), a new _ypldap user is now required
327 during installworld. "mergemaster -p" can be used to add the user
328 prior to installworld, as documented in the handbook.
331 The tftp loader (pxeboot) now uses the option root-path directive. As a
332 consequence it no longer looks for a pxeboot.4th file on the tftp
333 server. Instead it uses the regular /boot infrastructure as with the
337 The code to start recording plug and play data into the modules has
338 been committed. While the old tools will properly build a new kernel,
339 a number of warnings about "unknown metadata record 4" will be produced
340 for an older kldxref. To avoid such warnings, make sure to rebuild
341 the kernel toolchain (or world). Make sure that you have r292078 or
342 later when trying to build 292077 or later before rebuilding.
345 Debug data files are now built by default with 'make buildworld' and
346 installed with 'make installworld'. This facilitates debugging but
347 requires more disk space both during the build and for the installed
348 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
352 r291527 changed the internal interface between the nfsd.ko and
353 nfscommon.ko modules. As such, they must both be upgraded to-gether.
354 __FreeBSD_version has been bumped because of this.
357 Add support for unicode collation strings leads to a change of
358 order of files listed by ls(1) for example. To get back to the old
359 behaviour, set LC_COLLATE environment variable to "C".
361 Databases administrators will need to reindex their databases given
362 collation results will be different.
364 Due to a bug in install(1) it is recommended to remove the ancient
365 locales before running make installworld.
367 rm -rf /usr/share/locale/*
370 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
371 libcrypto.so.7 or libssl.so.7 must be recompiled.
374 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
375 Kernel modules isp_2400_multi and isp_2500_multi were removed and
376 should be replaced with isp_2400 and isp_2500 modules respectively.
379 The build previously allowed using 'make -n' to not recurse into
380 sub-directories while showing what commands would be executed, and
381 'make -n -n' to recursively show commands. Now 'make -n' will recurse
382 and 'make -N' will not.
385 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
386 and etcupdate will now use this file. A custom sendmail.cf is now
387 updated via this mechanism rather than via installworld. If you had
388 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
389 want to remove the exclusion or change it to "always install".
390 /etc/mail/sendmail.cf is now managed the same way regardless of
391 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
392 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
395 Compatibility shims for legacy ATA device names have been removed.
396 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
397 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
398 environment variables, /dev/ad* and /dev/ar* symbolic links.
401 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
402 Please see the 20141231 entry below for information about prerequisites
403 and upgrading, if you are not already using clang 3.5.0 or higher.
406 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
407 and renamed from .symbols to .debug. This reduces the size requirements
408 on the boot partition or file system and provides consistency with
409 userland debug files.
411 When using the supported kernel installation method the
412 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
413 as is done with /boot/kernel.
415 Developers wishing to maintain the historical behavior of installing
416 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
419 The wireless drivers had undergone changes that remove the 'parent
420 interface' from the ifconfig -l output. The rc.d network scripts
421 used to check presence of a parent interface in the list, so old
422 scripts would fail to start wireless networking. Thus, etcupdate(3)
423 or mergemaster(8) run is required after kernel update, to update your
424 rc.d scripts in /etc.
427 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
428 These configurations are now automatically interpreted as
429 'scrub fragment reassemble'.
432 Kernel-loadable modules for the random(4) device are back. To use
433 them, the kernel must have
436 options RANDOM_LOADABLE
438 kldload(8) can then be used to load random_fortuna.ko
439 or random_yarrow.ko. Please note that due to the indirect
440 function calls that the loadable modules need to provide,
441 the build-in variants will be slightly more efficient.
443 The random(4) kernel option RANDOM_DUMMY has been retired due to
444 unpopularity. It was not all that useful anyway.
447 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
448 Control over building the ELF Tool Chain tools is now provided by
449 the WITHOUT_TOOLCHAIN knob.
452 The polarity of Pulse Per Second (PPS) capture events with the
453 uart(4) driver has been corrected. Prior to this change the PPS
454 "assert" event corresponded to the trailing edge of a positive PPS
455 pulse and the "clear" event was the leading edge of the next pulse.
457 As the width of a PPS pulse in a typical GPS receiver is on the
458 order of 1 millisecond, most users will not notice any significant
459 difference with this change.
461 Anyone who has compensated for the historical polarity reversal by
462 configuring a negative offset equal to the pulse width will need to
463 remove that workaround.
466 The default group assigned to /dev/dri entries has been changed
467 from 'wheel' to 'video' with the id of '44'. If you want to have
468 access to the dri devices please add yourself to the video group
471 # pw groupmod video -m $USER
474 The menu.rc and loader.rc files will now be replaced during
475 upgrades. Please migrate local changes to menu.rc.local and
476 loader.rc.local instead.
479 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
480 strings and strip have been removed. The src.conf(5) knob
481 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
484 As ZFS requires more kernel stack pages than is the default on some
485 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
486 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
488 Please consider using 'options KSTACK_PAGES=X' where X is greater
489 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
492 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
493 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
494 default, i.e., they will not contain "::". For example, instead
495 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
496 to have a more specific match, such as different map entries for
497 IPv6:0:0 vs IPv6:0. This change requires that configuration
498 data (including maps, files, classes, custom ruleset, etc.) must
499 use the same format, so make certain such configuration data is
500 upgrading. As a very simple check search for patterns like
501 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
502 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
503 the cf option UseCompressedIPv6Addresses.
506 The default kernel entropy-processing algorithm is now
507 Fortuna, replacing Yarrow.
509 Assuming you have 'device random' in your kernel config
510 file, the configurations allow a kernel option to override
511 this default. You may choose *ONE* of:
513 options RANDOM_YARROW # Legacy /dev/random algorithm.
514 options RANDOM_DUMMY # Blocking-only driver.
516 If you have neither, you get Fortuna. For most people,
517 read no further, Fortuna will give a /dev/random that works
518 like it always used to, and the difference will be irrelevant.
520 If you remove 'device random', you get *NO* kernel-processed
521 entropy at all. This may be acceptable to folks building
522 embedded systems, but has complications. Carry on reading,
523 and it is assumed you know what you need.
525 *PLEASE* read random(4) and random(9) if you are in the
526 habit of tweaking kernel configs, and/or if you are a member
527 of the embedded community, wanting specific and not-usual
528 behaviour from your security subsystems.
530 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
531 random', you will NOT have a functioning /dev/random, and
532 many cryptographic features will not work, including SSH.
533 You may also find strange behaviour from the random(3) set
534 of library functions, in particular sranddev(3), srandomdev(3)
535 and arc4random(3). The reason for this is that the KERN_ARND
536 sysctl only returns entropy if it thinks it has some to
537 share, and with RANDOM_DUMMY or no 'device random' this
541 An additional fix for the issue described in the 20150614 sendmail
542 entry below has been been committed in revision 284717.
545 FreeBSD's old make (fmake) has been removed from the system. It is
546 available as the devel/fmake port or via pkg install fmake.
549 The fix for the issue described in the 20150614 sendmail entry
550 below has been been committed in revision 284436. The work
551 around described in that entry is no longer needed unless the
552 default setting is overridden by a confDH_PARAMETERS configuration
553 setting of '5' or pointing to a 512 bit DH parameter file.
556 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
557 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
558 and devel/kyua to version 0.20+ and adjust any calling code to work
559 with Kyuafile and kyua.
562 The import of openssl to address the FreeBSD-SA-15:10.openssl
563 security advisory includes a change which rejects handshakes
564 with DH parameters below 768 bits. sendmail releases prior
565 to 8.15.2 (not yet released), defaulted to a 512 bit
566 DH parameter setting for client connections. To work around
567 this interoperability, sendmail can be configured to use a
568 2048 bit DH parameter by:
570 1. Edit /etc/mail/`hostname`.mc
571 2. If a setting for confDH_PARAMETERS does not exist or
572 exists and is set to a string beginning with '5',
574 3. If a setting for confDH_PARAMETERS exists and is set to
575 a file path, create a new file with:
576 openssl dhparam -out /path/to/file 2048
577 4. Rebuild the .cf file:
578 cd /etc/mail/; make; make install
580 cd /etc/mail/; make restart
582 A sendmail patch is coming, at which time this file will be
586 Generation of legacy formatted entries have been disabled by default
587 in pwd_mkdb(8), as all base system consumers of the legacy formatted
588 entries were converted to use the new format by default when the new,
589 machine independent format have been added and supported since FreeBSD
592 Please see the pwd_mkdb(8) manual page for further details.
595 Clang and llvm have been upgraded to 3.6.1 release. Please see the
596 20141231 entry below for information about prerequisites and upgrading,
597 if you are not already using 3.5.0 or higher.
600 TI platform code switched to using vendor DTS files and this update
601 may break existing systems running on Beaglebone, Beaglebone Black,
604 - dtb files should be regenerated/reinstalled. Filenames are the
605 same but content is different now
606 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
607 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
608 addressing scheme is now pin 25 on /dev/gpioc3.
609 - Pandaboard: /etc/ttys should be updated, serial console device is
610 now /dev/ttyu2, not /dev/ttyu0
613 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
614 If you need the GNU extension from groff soelim(1), install groff
615 from package: pkg install groff, or via ports: textproc/groff.
618 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
619 defined in symlink(7); previously symlinks were silently ignored.
622 The const qualifier has been removed from iconv(3) to comply with
623 POSIX. The ports tree is aware of this from r384038 onwards.
626 Libraries specified by LIBADD in Makefiles must have a corresponding
627 DPADD_<lib> variable to ensure correct dependencies. This is now
628 enforced in src.libnames.mk.
631 From legacy ata(4) driver was removed support for SATA controllers
632 supported by more functional drivers ahci(4), siis(4) and mvs(4).
633 Kernel modules ataahci and ataadaptec were removed completely,
634 replaced by ahci and mvs modules respectively.
637 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
638 the 20141231 entry below for information about prerequisites and
639 upgrading, if you are not already using 3.5.0 or higher.
642 The 32-bit PowerPC kernel has been changed to a position-independent
643 executable. This can only be booted with a version of loader(8)
644 newer than January 31, 2015, so make sure to update both world and
645 kernel before rebooting.
648 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
649 but before r278950, the RNG was not seeded properly. Immediately
650 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
651 ssh keys or openssl keys) that were generated w/ a kernel from that
652 range. This does not affect programs that directly used /dev/random
653 or /dev/urandom. All userland uses of arc4random(3) are affected.
656 The autofs(4) ABI was changed in order to restore binary compatibility
657 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
661 The powerpc64 kernel has been changed to a position-independent
662 executable. This can only be booted with a new version of loader(8),
663 so make sure to update both world and kernel before rebooting.
666 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
667 only release, no new features have been added. Please see the 20141231
668 entry below for information about prerequisites and upgrading, if you
669 are not already using 3.5.0.
672 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
673 taken from the ELF Tool Chain project rather than GNU binutils. They
674 should be drop-in replacements, with the addition of arm64 support.
675 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
676 binutils tools, if necessary. See 20150805 for updated information.
679 The default Unbound configuration now enables remote control
680 using a local socket. Users who have already enabled the
681 local_unbound service should regenerate their configuration
682 by running "service local_unbound setup" as root.
685 The GNU texinfo and GNU info pages have been removed.
686 To be able to view GNU info pages please install texinfo from ports.
689 Clang, llvm and lldb have been upgraded to 3.5.0 release.
691 As of this release, a prerequisite for building clang, llvm and lldb is
692 a C++11 capable compiler and C++11 standard library. This means that to
693 be able to successfully build the cross-tools stage of buildworld, with
694 clang as the bootstrap compiler, your system compiler or cross compiler
695 should either be clang 3.3 or later, or gcc 4.8 or later, and your
696 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
699 On any standard FreeBSD 10.x or 11.x installation, where clang and
700 libc++ are on by default (that is, on x86 or arm), this should work out
703 On 9.x installations where clang is enabled by default, e.g. on x86 and
704 powerpc, libc++ will not be enabled by default, so libc++ should be
705 built (with clang) and installed first. If both clang and libc++ are
706 missing, build clang first, then use it to build libc++.
708 On 8.x and earlier installations, upgrade to 9.x first, and then follow
709 the instructions for 9.x above.
711 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
712 default, and do not build clang.
714 Many embedded systems are resource constrained, and will not be able to
715 build clang in a reasonable time, or in some cases at all. In those
716 cases, cross building bootable systems on amd64 is a workaround.
718 This new version of clang introduces a number of new warnings, of which
719 the following are most likely to appear:
723 This warns in two cases, for both C and C++:
724 * When the code is trying to take the absolute value of an unsigned
725 quantity, which is effectively a no-op, and almost never what was
726 intended. The code should be fixed, if at all possible. If you are
727 sure that the unsigned quantity can be safely cast to signed, without
728 loss of information or undefined behavior, you can add an explicit
729 cast, or disable the warning.
731 * When the code is trying to take an absolute value, but the called
732 abs() variant is for the wrong type, which can lead to truncation.
733 If you want to disable the warning instead of fixing the code, please
734 make sure that truncation will not occur, or it might lead to unwanted
737 -Wtautological-undefined-compare and
738 -Wundefined-bool-conversion
740 These warn when C++ code is trying to compare 'this' against NULL, while
741 'this' should never be NULL in well-defined C++ code. However, there is
742 some legacy (pre C++11) code out there, which actively abuses this
743 feature, which was less strictly defined in previous C++ versions.
745 Squid and openjdk do this, for example. The warning can be turned off
746 for C++98 and earlier, but compiling the code in C++11 mode might result
747 in unexpected behavior; for example, the parts of the program that are
748 unreachable could be optimized away.
751 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
752 kernel sources have been removed. The .h files remain, since some
753 utilities include them. This will need to be fixed later.
754 If "mount -t oldnfs ..." is attempted, it will fail.
755 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
756 the utilities will report errors.
759 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
760 directories to top level SUBDIR variable when their parent
761 directory is included in LOCAL_DIRS. Users with build systems with
762 such hierarchies and without SUBDIR entries in the parent
763 directory Makefiles should add them or add the directories to
767 faith(4) and faithd(8) have been removed from the base system. Faith
768 has been obsolete for a very long time.
771 vt(4), the new console driver, is enabled by default. It brings
772 support for Unicode and double-width characters, as well as
773 support for UEFI and integration with the KMS kernel video
776 You may need to update your console settings in /etc/rc.conf,
777 most probably the keymap. During boot, /etc/rc.d/syscons will
778 indicate what you need to do.
780 vt(4) still has issues and lacks some features compared to
781 syscons(4). See the wiki for up-to-date information:
782 https://wiki.freebsd.org/Newcons
784 If you want to keep using syscons(4), you can do so by adding
785 the following line to /boot/loader.conf:
789 pjdfstest has been integrated into kyua as an opt-in test suite.
790 Please see share/doc/pjdfstest/README for more details on how to
794 gperf has been removed from the base system for architectures
795 that use clang. Ports that require gperf will obtain it from the
799 pjdfstest has been moved from tools/regression/pjdfstest to
803 At svn r271982, The default linux compat kernel ABI has been adjusted
804 to 2.6.18 in support of the linux-c6 compat ports infrastructure
805 update. If you wish to continue using the linux-f10 compat ports,
806 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
807 encouraged to update their linux-compat packages to linux-c6 during
808 their next update cycle.
811 The ofwfb driver, used to provide a graphics console on PowerPC when
812 using vt(4), no longer allows mmap() of all physical memory. This
813 will prevent Xorg on PowerPC with some ATI graphics cards from
814 initializing properly unless x11-servers/xorg-server is updated to
818 The xdev targets have been converted to using TARGET and
819 TARGET_ARCH instead of XDEV and XDEV_ARCH.
822 The default unbound configuration has been modified to address
823 issues with reverse lookups on networks that use private
824 address ranges. If you use the local_unbound service, run
825 "service local_unbound setup" as root to regenerate your
826 configuration, then "service local_unbound reload" to load the
830 The GNU texinfo and GNU info pages are not built and installed
831 anymore, WITH_INFO knob has been added to allow to built and install
833 UPDATE: see 20150102 entry on texinfo's removal
836 The GNU readline library is now an INTERNALLIB - that is, it is
837 statically linked into consumers (GDB and variants) in the base
838 system, and the shared library is no longer installed. The
839 devel/readline port is available for third party software that
843 The Itanium architecture (ia64) has been removed from the list of
844 known architectures. This is the first step in the removal of the
848 Commit r268115 has added NFSv4.1 server support, merged from
849 projects/nfsv4.1-server. Since this includes changes to the
850 internal interfaces between the NFS related modules, a full
851 build of the kernel and modules will be necessary.
852 __FreeBSD_version has been bumped.
855 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
856 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
857 which differs from the behaviour controlled by this knob.)
860 Maximal length of the serial number in CTL was increased from 16 to
861 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
862 and ctld, need to be rebuilt to work with a new kernel.
865 The libatf-c and libatf-c++ major versions were downgraded to 0 and
866 1 respectively to match the upstream numbers. They were out of
867 sync because, when they were originally added to FreeBSD, the
868 upstream versions were not respected. These libraries are private
869 and not yet built by default, so renumbering them should be a
870 non-issue. However, unclean source trees will yield broken test
871 programs once the operator executes "make delete-old-libs" after a
874 Additionally, the atf-sh binary was made private by moving it into
875 /usr/libexec/. Already-built shell test programs will keep the
876 path to the old binary so they will break after "make delete-old"
879 If you are using WITH_TESTS=yes (not the default), wipe the object
880 tree and rebuild from scratch to prevent spurious test failures.
881 This is only needed once: the misnumbered libraries and misplaced
882 binaries have been added to OptionalObsoleteFiles.inc so they will
883 be removed during a clean upgrade.
886 Clang and llvm have been upgraded to 3.4.1 release.
889 We bogusly installed src.opts.mk in /usr/share/mk. This file should
890 be removed to avoid issues in the future (and has been added to
894 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
895 past, it affected all builds that used the bsd.*.mk files. The old
896 behavior was a bug, but people may have relied upon it. To get this
897 behavior back, you can .include /etc/src.conf from /etc/make.conf
898 (which is still global and isn't changed). This also changes the
899 behavior of incremental builds inside the tree of individual
900 directories. Set MAKESYSPATH to ".../share/mk" to do that.
901 Although this has survived make universe and some upgrade scenarios,
902 other upgrade scenarios may have broken. At least one form of
903 temporary breakage was fixed with MAKESYSPATH settings for buildworld
904 as well... In cases where MAKESYSPATH isn't working with this
905 setting, you'll need to set it to the full path to your tree.
907 One side effect of all this cleaning up is that bsd.compiler.mk
908 is no longer implicitly included by bsd.own.mk. If you wish to
909 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
913 The lindev device has been removed since /dev/full has been made a
914 standard device. __FreeBSD_version has been bumped.
917 The knob WITHOUT_VI was added to the base system, which controls
918 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
919 in order to reorder files share/termcap and didn't build ex(1) as a
920 build tool, so building/installing with WITH_VI is highly advised for
921 build hosts for older releases.
923 This issue has been fixed in stable/9 and stable/10 in r277022 and
924 r276991, respectively.
927 The YES_HESIOD knob has been removed. It has been obsolete for
928 a decade. Please move to using WITH_HESIOD instead or your builds
929 will silently lack HESIOD.
932 The uart(4) driver has been changed with respect to its handling
933 of the low-level console. Previously the uart(4) driver prevented
934 any process from changing the baudrate or the CLOCAL and HUPCL
935 control flags. By removing the restrictions, operators can make
936 changes to the serial console port without having to reboot.
937 However, when getty(8) is started on the serial device that is
938 associated with the low-level console, a misconfigured terminal
939 line in /etc/ttys will now have a real impact.
940 Before upgrading the kernel, make sure that /etc/ttys has the
941 serial console device configured as 3wire without baudrate to
942 preserve the previous behaviour. E.g:
943 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
946 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
947 to improve performance. To re-enable it, if needed, run rpcbind
948 with command line option -W.
951 Switched back to the GPL dtc compiler due to updates in the upstream
952 dts files not being supported by the BSDL dtc compiler. You will need
953 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
954 may result while building dtb files during a kernel build if you fail
955 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
958 Clang and llvm have been upgraded to 3.4 release.
961 The nve(4) driver has been removed. Please use the nfe(4) driver
962 for NVIDIA nForce MCP Ethernet adapters instead.
965 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
966 This could cause certain C++ applications using shared libraries built
967 against the previous version of libc++ to crash. The incompatibility
968 has now been fixed, but any C++ applications or shared libraries built
969 between r261283 and r261801 should be recompiled.
972 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
973 capability mode support. Please note that enabling the feature in
974 kernel is still highly recommended.
977 OpenSSH is now built with sandbox support, and will use sandbox as
978 the default privilege separation method. This requires Capsicum
979 capability mode support in kernel.
982 The libelf and libdwarf libraries have been updated to newer
983 versions from upstream. Shared library version numbers for
984 these two libraries were bumped. Any ports or binaries
985 requiring these two libraries should be recompiled.
986 __FreeBSD_version is bumped to 1100006.
989 If a Makefile in a tests/ directory was auto-generating a Kyuafile
990 instead of providing an explicit one, this would prevent such
991 Makefile from providing its own Kyuafile in the future during
992 NO_CLEAN builds. This has been fixed in the Makefiles but manual
993 intervention is needed to clean an objdir if you use NO_CLEAN:
994 # find /usr/obj -name Kyuafile | xargs rm -f
997 The behavior of gss_pseudo_random() for the krb5 mechanism
998 has changed, for applications requesting a longer random string
999 than produced by the underlying enctype's pseudo-random() function.
1000 In particular, the random string produced from a session key of
1001 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1002 be different at the 17th octet and later, after this change.
1003 The counter used in the PRF+ construction is now encoded as a
1004 big-endian integer in accordance with RFC 4402.
1005 __FreeBSD_version is bumped to 1100004.
1008 The WITHOUT_ATF build knob has been removed and its functionality
1009 has been subsumed into the more generic WITHOUT_TESTS. If you were
1010 using the former to disable the build of the ATF libraries, you
1011 should change your settings to use the latter.
1014 The default version of mtree is nmtree which is obtained from
1015 NetBSD. The output is generally the same, but may vary
1016 slightly. If you found you need identical output adding
1017 "-F freebsd9" to the command line should do the trick. For the
1018 time being, the old mtree is available as fmtree.
1021 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1022 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1023 1.1.4_8 and verify bsdyml not linked in, before running "make
1025 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1027 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1030 The stable/10 branch has been created in subversion from head
1034 The rc.d/jail script has been updated to support jail(8)
1035 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1036 for per-jail configuration are automatically converted to
1037 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1038 This is transparently backward compatible. See below about some
1039 incompatibilities and rc.conf(5) manual page for more details.
1041 These variables are now deprecated in favor of jail(8) configuration
1042 file. One can use "rc.d/jail config <jname>" command to generate
1043 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1044 running the jail(8) utility. The default pathname of the
1045 configuration file is /etc/jail.conf and can be specified by
1046 using $jail_conf or $jail_<jname>_conf variables.
1048 Please note that jail_devfs_ruleset accepts an integer at
1049 this moment. Please consider to rewrite the ruleset name
1053 BIND has been removed from the base system. If all you need
1054 is a local resolver, simply enable and start the local_unbound
1055 service instead. Otherwise, several versions of BIND are
1056 available in the ports tree. The dns/bind99 port is one example.
1058 With this change, nslookup(1) and dig(1) are no longer in the base
1059 system. Users should instead use host(1) and drill(1) which are
1060 in the base system. Alternatively, nslookup and dig can
1061 be obtained by installing the dns/bind-tools port.
1064 With the addition of unbound(8), a new unbound user is now
1065 required during installworld. "mergemaster -p" can be used to
1066 add the user prior to installworld, as documented in the handbook.
1069 OpenSSH is now built with DNSSEC support, and will by default
1070 silently trust signed SSHFP records. This can be controlled with
1071 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1072 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1075 The GNU Compiler Collection and C++ standard library (libstdc++)
1076 are no longer built by default on platforms where clang is the system
1077 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1078 options in src.conf.
1081 The PROCDESC kernel option is now part of the GENERIC kernel
1082 configuration and is required for the rwhod(8) to work.
1083 If you are using custom kernel configuration, you should include
1087 The API and ABI related to the Capsicum framework was modified
1088 in backward incompatible way. The userland libraries and programs
1089 have to be recompiled to work with the new kernel. This includes the
1090 following libraries and programs, but the whole buildworld is
1091 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1092 kdump, procstat, rwho, rwhod, uniq.
1095 AES-NI intrinsic support has been added to gcc. The AES-NI module
1096 has been updated to use this support. A new gcc is required to build
1097 the aesni module on both i386 and amd64.
1100 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1101 Thus "device padlock_rng" and "device rdrand_rng" should be
1102 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1105 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1106 enables just the iconv* functionality and is now on by default.
1107 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1108 compatibility. Set WITHOUT_ICONV to build the old way.
1109 If you have been using WITH_ICONV before, you will very likely
1110 need to turn on WITH_LIBICONV_COMPAT.
1113 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1114 Illumos origin, including ZFS. If you have INVARIANTS in your
1115 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1117 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1118 locks if WITNESS option was set. Because that generated a lot of
1119 witness(9) reports and all of them were believed to be false
1120 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1121 can be used to achieve the previous behavior.
1124 Timer values in IPv6 data structures now use time_uptime instead
1125 of time_second. Although this is not a user-visible functional
1126 change, userland utilities which directly use them---ndp(8),
1127 rtadvd(8), and rtsold(8) in the base system---need to be updated
1128 to r253970 or later.
1131 find -delete can now delete the pathnames given as arguments,
1132 instead of only files found below them or if the pathname did
1133 not contain any slashes. Formerly, the following error message
1136 find: -delete: <path>: relative path potentially not safe
1138 Deleting the pathnames given as arguments can be prevented
1139 without error messages using -mindepth 1 or by changing
1140 directory and passing "." as argument to find. This works in the
1141 old as well as the new version of find.
1144 Behavior of devfs rules path matching has been changed.
1145 Pattern is now always matched against fully qualified devfs
1146 path and slash characters must be explicitly matched by
1147 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1148 subdirectories must be reviewed.
1151 The default ARM ABI has changed to the ARM EABI. The old ABI is
1152 incompatible with the ARM EABI and all programs and modules will
1153 need to be rebuilt to work with a new kernel.
1155 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1157 NOTE: Support for the old ABI will be removed in the future and
1158 users are advised to upgrade.
1161 pkg_install has been disconnected from the build if you really need it
1162 you should add WITH_PKGTOOLS in your src.conf(5).
1165 Most of network statistics structures were changed to be able
1166 keep 64-bits counters. Thus all tools, that work with networking
1167 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1170 Fix a bug that allowed a tracing process (e.g. gdb) to write
1171 to a memory-mapped file in the traced process's address space
1172 even if neither the traced process nor the tracing process had
1173 write access to that file.
1176 CVS has been removed from the base system. An exact copy
1177 of the code is available from the devel/cvs port.
1180 Some people report the following error after the switch to bmake:
1182 make: illegal option -- J
1183 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1185 *** [buildworld] Error code 2
1187 this likely due to an old instance of make in
1188 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1189 which src/Makefile will use that blindly, if it exists, so if
1190 you see the above error:
1192 rm -rf `make -V MAKEPATH`
1197 Use bmake by default.
1198 Whereas before one could choose to build with bmake via
1199 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1200 make. The goal is to remove these knobs for 10-RELEASE.
1202 It is worth noting that bmake (like gmake) treats the command
1203 line as the unit of failure, rather than statements within the
1204 command line. Thus '(cd some/where && dosomething)' is safer
1205 than 'cd some/where; dosomething'. The '()' allows consistent
1206 behavior in parallel build.
1209 Fix a bug that allows NFS clients to issue READDIR on files.
1212 The WITHOUT_IDEA option has been removed because
1213 the IDEA patent expired.
1216 The sysctl which controls TRIM support under ZFS has been renamed
1217 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1221 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1222 rather than creating it's own in the temporary directory in
1223 order allow access to bootstrapped versions of tools such as
1224 install and mtree. When upgrading from version of FreeBSD where
1225 the install command does not support -l, you will need to
1226 install a new mergemaster command if mergemaster -p is required.
1227 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1231 Legacy ATA stack, disabled and replaced by new CAM-based one since
1232 FreeBSD 9.0, completely removed from the sources. Kernel modules
1233 atadisk and atapi*, user-level tools atacontrol and burncd are
1234 removed. Kernel option `options ATA_CAM` is now permanently enabled
1238 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1239 and socketpair(2). Software, in particular Kerberos, may
1240 automatically detect and use these during building. The resulting
1241 binaries will not work on older kernels.
1244 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1245 information, see the respective 20130304 entry).
1248 Recent commits to callout(9) changed the size of struct callout,
1249 so the KBI is probably heavily disturbed. Also, some functions
1250 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1251 by macros. Every kernel module using it won't load, so rebuild
1254 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1255 but does not initialize by default (because of the new CTL_DISABLE
1256 option) to save memory. To re-enable it, remove the CTL_DISABLE
1257 option from the kernel config file or set kern.cam.ctl.disable=0
1258 in /boot/loader.conf.
1261 The ctl device has been disabled in GENERIC for i386 and amd64.
1262 This was done due to the extra memory being allocated at system
1263 initialisation time by the ctl driver which was only used if
1264 a CAM target device was created. This makes a FreeBSD system
1265 unusable on 128MB or less of RAM.
1268 A new compression method (lz4) has been merged to -HEAD. Please
1269 refer to zpool-features(7) for more information.
1271 Please refer to the "ZFS notes" section of this file for information
1272 on upgrading boot ZFS pools.
1275 A BSD-licensed patch(1) variant has been added and is installed
1276 as bsdpatch, being the GNU version the default patch.
1277 To inverse the logic and use the BSD-licensed one as default,
1278 while having the GNU version installed as gnupatch, rebuild
1279 and install world with the WITH_BSD_PATCH knob set.
1282 Due to the use of the new -l option to install(1) during build
1283 and install, you must take care not to directly set the INSTALL
1284 make variable in your /etc/make.conf, /etc/src.conf, or on the
1285 command line. If you wish to use the -C flag for all installs
1286 you may be able to add INSTALL+=-C to /etc/make.conf or
1290 The install(1) option -M has changed meaning and now takes an
1291 argument that is a file or path to append logs to. In the
1292 unlikely event that -M was the last option on the command line
1293 and the command line contained at least two files and a target
1294 directory the first file will have logs appended to it. The -M
1295 option served little practical purpose in the last decade so its
1296 use is expected to be extremely rare.
1299 After switching to Clang as the default compiler some users of ZFS
1300 on i386 systems started to experience stack overflow kernel panics.
1301 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1304 GEOM_LABEL now mangles label names read from file system metadata.
1305 Mangling affect labels containing spaces, non-printable characters,
1306 '%' or '"'. Device names in /etc/fstab and other places may need to
1310 By default, only the 10 most recent kernel dumps will be saved. To
1311 restore the previous behaviour (no limit on the number of kernel dumps
1312 stored in the dump directory) add the following line to /etc/rc.conf:
1317 With the addition of auditdistd(8), a new auditdistd user is now
1318 required during installworld. "mergemaster -p" can be used to
1319 add the user prior to installworld, as documented in the handbook.
1322 The sin6_scope_id member variable in struct sockaddr_in6 is now
1323 filled by the kernel before passing the structure to the userland via
1324 sysctl or routing socket. This means the KAME-specific embedded scope
1325 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1326 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1327 __FreeBSD_version is bumped to 1000025.
1330 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1331 This means that the world and kernel will be compiled with clang
1332 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1333 and /usr/bin/cpp. To disable this behavior and revert to building
1334 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1335 of current may need to bootstrap WITHOUT_CLANG first if the clang
1336 build fails (its compatibility window doesn't extend to the 9 stable
1340 The IPFIREWALL_FORWARD kernel option has been removed. Its
1341 functionality now turned on by default.
1344 The ZERO_COPY_SOCKET kernel option has been removed and
1345 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1346 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1347 mechanism which is not safe and may result in kernel crashes.
1348 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1349 driver supports disposeable external page sized mbuf storage.
1350 Proper replacements for both zero-copy mechanisms are under
1351 consideration and will eventually lead to complete removal
1352 of the two kernel options.
1355 The IPv4 network stack has been converted to network byte
1356 order. The following modules need to be recompiled together
1357 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1358 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1361 Support for non-MPSAFE filesystems was removed from VFS. The
1362 VFS_VERSION was bumped, all filesystem modules shall be
1366 All the non-MPSAFE filesystems have been disconnected from
1367 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1368 portalfs, smbfs, xfs.
1371 The interface cloning API and ABI has changed. The following
1372 modules need to be recompiled together with kernel:
1373 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1374 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1375 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1378 The sdhci driver was split in two parts: sdhci (generic SD Host
1379 Controller logic) and sdhci_pci (actual hardware driver).
1380 No kernel config modifications are required, but if you
1381 load sdhc as a module you must switch to sdhci_pci instead.
1384 Import the FUSE kernel and userland support into base system.
1387 The GNU sort(1) program has been removed since the BSD-licensed
1388 sort(1) has been the default for quite some time and no serious
1389 problems have been reported. The corresponding WITH_GNU_SORT
1393 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1394 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1398 The net80211(4) ABI has been changed to allow for improved driver
1399 PS-POLL and power-save support. All wireless drivers need to be
1400 recompiled to work with the new kernel.
1403 The random(4) support for the VIA hardware random number
1404 generator (`PADLOCK') is no longer enabled unconditionally.
1405 Add the padlock_rng device in the custom kernel config if
1406 needed. The GENERIC kernels on i386 and amd64 do include the
1407 device, so the change only affects the custom kernel
1411 The pf(4) packet filter ABI has been changed. pfctl(8) and
1412 snmp_pf module need to be recompiled to work with new kernel.
1415 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1416 to -HEAD. Pools that have empty_bpobj in active state can not be
1417 imported read-write with ZFS implementations that do not support
1418 this feature. For more information read the zpool-features(5)
1422 The sparc64 ZFS loader has been changed to no longer try to auto-
1423 detect ZFS providers based on diskN aliases but now requires these
1424 to be explicitly listed in the OFW boot-device environment variable.
1427 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1428 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1429 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1432 The following sysctls and tunables have been renamed for consistency
1433 with other variables:
1434 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1435 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1438 The sort utility has been replaced with BSD sort. For now, GNU sort
1439 is also available as "gnusort" or the default can be set back to
1440 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1441 installed as "bsdsort".
1444 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1445 Starting with this version the old system of ZFS pool versioning
1446 is superseded by "feature flags". This concept enables forward
1447 compatibility against certain future changes in functionality of ZFS
1448 pools. The first read-only compatible "feature flag" for ZFS pools
1449 is named "com.delphix:async_destroy". For more information
1450 read the new zpool-features(5) manual page.
1451 Please refer to the "ZFS notes" section of this file for information
1452 on upgrading boot ZFS pools.
1455 The malloc(3) implementation embedded in libc now uses sources imported
1456 as contrib/jemalloc. The most disruptive API change is to
1457 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1458 delete it prior to installworld, and optionally re-create it using the
1459 new format after rebooting. See malloc.conf(5) for details
1460 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1464 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1465 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1466 now spelled mips. This is to aid compatibility with third-party
1467 software that expects this naming scheme in uname(3). Little-endian
1468 settings are unchanged. If you are updating a big-endian mips64 machine
1469 from before this change, you may need to set MACHINE_ARCH=mips64 in
1470 your environment before the new build system will recognize your machine.
1473 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1477 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1478 nullfs(5) did not pass through all behaviours to the underlying layer,
1479 as a result if we bound to a socket on the lower layer we could connect
1480 only to the lower path; if we bound to the upper layer we could connect
1481 only to the upper path. The new behavior is one can connect to both the
1482 lower and the upper paths regardless what layer path one binds to.
1485 The getifaddrs upgrade path broken with 20111215 has been restored.
1486 If you have upgraded in between 20111215 and 20120209 you need to
1487 recompile libc again with your kernel. You still need to recompile
1488 world to be able to configure CARP but this restriction already
1489 comes from 20111215.
1492 The set_rcvar() function has been removed from /etc/rc.subr. All
1493 base and ports rc.d scripts have been updated, so if you have a
1494 port installed with a script in /usr/local/etc/rc.d you can either
1495 hand-edit the rcvar= line, or reinstall the port.
1497 An easy way to handle the mass-update of /etc/rc.d:
1498 rm /etc/rc.d/* && mergemaster -i
1501 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1502 on the current CPU and prevents other threads from running.
1503 This behavior can be reverted using the kern.stop_scheduler_on_panic
1505 The new behavior can be incompatible with kern.sync_on_panic.
1508 The carp(4) facility has been changed significantly. Configuration
1509 of the CARP protocol via ifconfig(8) has changed, as well as format
1510 of CARP events submitted to devd(8) has changed. See manual pages
1511 for more information. The arpbalance feature of carp(4) is currently
1512 not supported anymore.
1514 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1515 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1516 need to be recompiled.
1519 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1523 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1524 explicitely support non-MPSAFE filesystems.
1525 It is on by default for all supported platform at this present
1529 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1530 i386 and pc98 GENERIC kernel configuration files.
1533 sysinstall has been removed
1536 The stable/9 branch created in subversion. This corresponds to the
1537 RELENG_9 branch in CVS.
1543 Avoid using make -j when upgrading. While generally safe, there are
1544 sometimes problems using -j to upgrade. If your upgrade fails with
1545 -j, please try again without -j. From time to time in the past there
1546 have been problems using -j with buildworld and/or installworld. This
1547 is especially true when upgrading between "distant" versions (eg one
1548 that cross a major release boundary or several minor releases, or when
1549 several months have passed on the -current branch).
1551 Sometimes, obscure build problems are the result of environment
1552 poisoning. This can happen because the make utility reads its
1553 environment when searching for values for global variables. To run
1554 your build attempts in an "environmental clean room", prefix all make
1555 commands with 'env -i '. See the env(1) manual page for more details.
1557 When upgrading from one major version to another it is generally best
1558 to upgrade to the latest code in the currently installed branch first,
1559 then do an upgrade to the new branch. This is the best-tested upgrade
1560 path, and has the highest probability of being successful. Please try
1561 this approach before reporting problems with a major version upgrade.
1563 When upgrading a live system, having a root shell around before
1564 installing anything can help undo problems. Not having a root shell
1565 around can lead to problems if pam has changed too much from your
1566 starting point to allow continued authentication after the upgrade.
1568 This file should be read as a log of events. When a later event changes
1569 information of a prior event, the prior event should not be deleted.
1570 Instead, a pointer to the entry with the new information should be
1571 placed in the old entry. Readers of this file should also sanity check
1572 older entries before relying on them blindly. Authors of new entries
1573 should write them with this in mind.
1577 When upgrading the boot ZFS pool to a new version, always follow
1580 1.) recompile and reinstall the ZFS boot loader and boot block
1581 (this is part of "make buildworld" and "make installworld")
1583 2.) update the ZFS boot block on your boot drive
1585 The following example updates the ZFS boot block on the first
1586 partition (freebsd-boot) of a GPT partitioned drive ada0:
1587 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1589 Non-boot pools do not need these updates.
1593 If you are updating from a prior version of FreeBSD (even one just
1594 a few days old), you should follow this procedure. It is the most
1595 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1597 make kernel-toolchain
1598 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1599 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1601 To test a kernel once
1602 ---------------------
1603 If you just want to boot a kernel once (because you are not sure
1604 if it works, or if you want to boot a known bad kernel to provide
1605 debugging information) run
1606 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1607 nextboot -k testkernel
1609 To just build a kernel when you know that it won't mess you up
1610 --------------------------------------------------------------
1611 This assumes you are already running a CURRENT system. Replace
1612 ${arch} with the architecture of your machine (e.g. "i386",
1613 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1615 cd src/sys/${arch}/conf
1616 config KERNEL_NAME_HERE
1617 cd ../compile/KERNEL_NAME_HERE
1622 If this fails, go to the "To build a kernel" section.
1624 To rebuild everything and install it on the current system.
1625 -----------------------------------------------------------
1626 # Note: sometimes if you are running current you gotta do more than
1627 # is listed here if you are upgrading from a really old current.
1629 <make sure you have good level 0 dumps>
1631 make kernel KERNCONF=YOUR_KERNEL_HERE
1633 <reboot in single user> [3]
1640 To cross-install current onto a separate partition
1641 --------------------------------------------------
1642 # In this approach we use a separate partition to hold
1643 # current's root, 'usr', and 'var' directories. A partition
1644 # holding "/", "/usr" and "/var" should be about 2GB in
1647 <make sure you have good level 0 dumps>
1650 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1651 <maybe newfs current's root partition>
1652 <mount current's root partition on directory ${CURRENT_ROOT}>
1653 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1654 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1655 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1656 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1657 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1658 <reboot into current>
1659 <do a "native" rebuild/install as described in the previous section>
1660 <maybe install compatibility libraries from ports/misc/compat*>
1664 To upgrade in-place from stable to current
1665 ----------------------------------------------
1666 <make sure you have good level 0 dumps>
1668 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1670 <reboot in single user> [3]
1677 Make sure that you've read the UPDATING file to understand the
1678 tweaks to various things you need. At this point in the life
1679 cycle of current, things change often and you are on your own
1680 to cope. The defaults can also change, so please read ALL of
1681 the UPDATING entries.
1683 Also, if you are tracking -current, you must be subscribed to
1684 freebsd-current@freebsd.org. Make sure that before you update
1685 your sources that you have read and understood all the recent
1686 messages there. If in doubt, please track -stable which has
1687 much fewer pitfalls.
1689 [1] If you have third party modules, such as vmware, you
1690 should disable them at this point so they don't crash your
1693 [3] From the bootblocks, boot -s, and then do
1698 adjkerntz -i # if CMOS is wall time
1699 Also, when doing a major release upgrade, it is required that
1700 you boot into single user mode to do the installworld.
1702 [4] Note: This step is non-optional. Failure to do this step
1703 can result in a significant reduction in the functionality of the
1704 system. Attempting to do it by hand is not recommended and those
1705 that pursue this avenue should read this file carefully, as well
1706 as the archives of freebsd-current and freebsd-hackers mailing lists
1707 for potential gotchas. The -U option is also useful to consider.
1708 See mergemaster(8) for more information.
1710 [5] Usually this step is a noop. However, from time to time
1711 you may need to do this if you get unknown user in the following
1712 step. It never hurts to do it all the time. You may need to
1713 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1714 install) after the buildworld before this step if you last updated
1715 from current before 20130425 or from -stable before 20130430.
1717 [6] This only deletes old files and directories. Old libraries
1718 can be deleted by "make delete-old-libs", but you have to make
1719 sure that no program is using those libraries anymore.
1721 [8] In order to have a kernel that can run the 4.x binaries needed to
1722 do an installworld, you must include the COMPAT_FREEBSD4 option in
1723 your kernel. Failure to do so may leave you with a system that is
1724 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1725 required to run the 5.x binaries on more recent kernels. And so on
1726 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1728 Make sure that you merge any new devices from GENERIC since the
1729 last time you updated your kernel config file.
1731 [9] When checking out sources, you must include the -P flag to have
1732 cvs prune empty directories.
1734 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1735 "?=" instead of the "=" assignment operator, so that buildworld can
1736 override the CPUTYPE if it needs to.
1738 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1739 not on the command line, or in /etc/make.conf. buildworld will
1740 warn if it is improperly defined.
1743 This file contains a list, in reverse chronological order, of major
1744 breakages in tracking -current. It is not guaranteed to be a complete
1745 list of such breakages, and only contains entries since September 23, 2011.
1746 If you need to see UPDATING entries from before that date, you will need
1747 to fetch an UPDATING file from an older FreeBSD release.
1749 Copyright information:
1751 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1753 Redistribution, publication, translation and use, with or without
1754 modification, in full or in part, in any form or format of this
1755 document are permitted without further permission from the author.
1757 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1758 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1759 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1760 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1761 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1762 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1763 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1764 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1765 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1766 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1767 POSSIBILITY OF SUCH DAMAGE.
1769 Contact Warner Losh if you have any questions about your use of