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 20180912 p14 FreeBSD-SA-18:12.elf
20 FreeBSD-EN-18:08.lazyfpu
22 Fix improper elf header parsing. [SA-18:12.elf]
24 Fix regression in Lazy FPU remediation. [EN-18:08.lazyfpu]
26 20180814 p13 FreeBSD-SA-18:08.tcp [revised]
29 FreeBSD-SA-18:11.hostapd
31 Revise manual pages. [SA-18:08.tcp]
33 Fix L1 Terminal Fault (L1TF) kernel information disclosure.
36 Fix resource exhaustion in IP fragment reassembly. [SA-18:10.ip]
38 Fix unauthenticated EAPOL-Key decryption vulnerability.
41 20180806 p12 FreeBSD-SA-18:08.tcp
43 Fix resource exhaustion in TCP reassembly.
45 20180621 p11 FreeBSD-SA-18:07.lazyfpu
48 Fix Lazy FPU information disclosure. [SA-18:07.lazyfpu]
50 Fix TLB shootdown for Xen based guests. [EN-18:07.pmap]
52 20180508 p10 FreeBSD-SA-18:06.debugreg
54 FreeBSD-EN-18:06.tzdata
56 Fix mishandling of x86 debug exceptions. [SA-18:06.debugreg]
58 Fix multiple small kernel memory disclosures. [EN-18:05.mem]
60 Update timezone database information. [EN-18:06.tzdata]
62 20180404 p9 FreeBSD-SA-18:04.vt
63 FreeBSD-SA-18:05.ipsec
64 FreeBSD-EN-18:03.tzdata
67 Fix vt console memory disclosure. [SA-18:04.vt]
69 Fix ipsec crash or denial of service. [SA-18:05.ipsec]
71 Update timezone database information. [EN-18:03.tzdata]
73 Fix multiple small kernel memory disclosures. [EN-18:04.mem]
75 20180314 p8 FreeBSD-SA-18:03.speculative_execution
77 Add mitigations for two classes of speculative execution vulnerabilities
80 20180307 p7 FreeBSD-SA-18:01.ipsec
82 FreeBSD-EN-18:01.tzdata
85 Fix ipsec validation and use-after-free. [SA-18:01.ipsec]
87 Fix multiple vulnerabilities in ntp. [SA-18:02.ntp]
89 Update timezone database information. [EN-18:01.tzdata]
91 Update file(1) to new version with security update. [EN-18:02.file]
93 20171209 p6 FreeBSD-SA-17:12.openssl
95 Fix multiple vulnerabilities of OpenSSL.
97 20171129 p5 FreeBSD-SA-17:11.openssl
99 Fix multiple vulnerabilities of OpenSSL.
101 20171115 p4 FreeBSD-SA-17:08.ptrace
102 FreeBSD-SA-17:10.kldstat
104 Fix ptrace(2) vulnerability. [SA-17:08.ptrace]
106 Fix kldstat(2) vulnerability. [SA-17:10.kldstat]
108 20171102 p3 FreeBSD-EN-17:09.tzdata
110 Update timezone database information. [EN-17:09]
112 20171017 p2 FreeBSD-SA-17:07.wpa
114 Fix WPA2 protocol vulnerability. [SA-17:07]
116 20170810 p1 FreeBSD-SA-17:06.openssh
117 FreeBSD-EN-17:07.vnet
120 Fix OpenSSH Denial of Service vulnerability. [SA-17:06]
122 Fix VNET kernel panic with asynchronous I/O. [EN-17:07]
124 Fix pf(4) housekeeping thread causes kernel panic. [EN-17:08]
130 arm64 builds now use the base system LLD 4.0.0 linker by default,
131 instead of requiring that the aarch64-binutils port or package be
132 installed. To continue using aarch64-binutils, set
133 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
136 The ctl.ko module no longer implements the iSCSI target frontend:
137 cfiscsi.ko does instead.
139 If building cfiscsi.ko as a kernel module, the module can be loaded
140 via one of the following methods:
141 - `cfiscsi_load="YES"` in loader.conf(5).
142 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
143 - ctladm(8)/ctld(8), when compiled with iSCSI support
144 (`WITH_ISCSI=yes` in src.conf(5))
146 Please see cfiscsi(4) for more details.
149 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
150 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
151 same source (previously, the dependency of mmcsd.ko on mmc.ko was
152 missing, but mmcsd.ko now will refuse to load if it is incompatible
156 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
157 use any explicitly assigned loopback address available in the jail
158 instead of using the first assigned address of the jail.
161 As of r316810 for ipfilter, keep frags is no longer assumed when
162 keep state is specified in a rule. r316810 aligns ipfilter with
163 documentation in man pages separating keep frags from keep state.
164 This allows keep state to specified without forcing keep frags
165 and allows keep frags to be specified independently of keep state.
166 To maintain previous behaviour, also specify keep frags with
167 keep state (as documented in ipf.conf.5).
170 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
171 Please see the 20141231 entry below for information about prerequisites
172 and upgrading, if you are not already using clang 3.5.0 or higher.
175 The code that provides support for ZFS .zfs/ directory functionality
176 has been reimplemented. It's not possible now to create a snapshot
177 by mkdir under .zfs/snapshot/. That should be the only user visible
181 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
182 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
183 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
184 and now NAT-T is supported by default. Security associations now use
185 the single namespace for SPI allocation, so if you use several manually
186 configured security associations with the same SPI, this configuration
190 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
191 Please see the 20141231 entry below for information about prerequisites
192 and upgrading, if you are not already using clang 3.5.0 or higher.
195 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
196 Please see the 20141231 entry below for information about prerequisites
197 and upgrading, if you are not already using clang 3.5.0 or higher.
200 The layout of the pmap structure has changed for powerpc to put the pmap
201 statistics at the front for all CPU variations. libkvm(3) and all tools
202 that link against it need to be recompiled.
205 isl(4) and cyapa(4) drivers now require a new driver,
206 chromebook_platform(4), to work properly on Chromebook-class hardware.
207 On other types of hardware the drivers may need to be configured using
208 device hints. Please see the corresponding manual pages for details.
211 Relocatable object files with the extension of .So have been renamed
212 to use an extension of .pico instead. The purpose of this change is
213 to avoid a name clash with shared libraries on case-insensitive file
214 systems. On those file systems, foo.So is the same file as foo.so.
217 The libc stub for the pipe(2) system call has been replaced with
218 a wrapper that calls the pipe2(2) system call and the pipe(2)
219 system call is now only implemented by the kernels that include
220 "options COMPAT_FREEBSD10" in their config file (this is the
221 default). Users should ensure that this option is enabled in
222 their kernel or upgrade userspace to r302092 before upgrading their
226 CAM will now strip leading spaces from SCSI disks' serial numbers.
227 This will effect users who create UFS filesystems on SCSI disks using
228 those disk's diskid device nodes. For example, if /etc/fstab
229 previously contained a line like
230 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
231 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
232 transforms like gmirror may also be affected. ZFS users should
236 The bitstring(3) API has been updated with new functionality and
237 improved performance. But it is binary-incompatible with the old API.
238 Objects built with the new headers may not be linked against objects
239 built with the old headers.
242 The brk and sbrk functions have been removed from libc on arm64.
243 Binutils from ports has been updated to not link to these
244 functions and should be updated to the latest version before
245 installing a new libc.
248 The armv6 port now defaults to hard float ABI. Limited support
249 for running both hardfloat and soft float on the same system
250 is available using the libraries installed with -DWITH_LIBSOFT.
251 This has only been tested as an upgrade path for installworld
252 and packages may fail or need manual intervention to run. New
253 packages will be needed.
255 To update an existing self-hosted armv6hf system, you must add
256 TARGET_ARCH=armv6 on the make command line for both the build
257 and the install steps.
260 Kernel modules compiled outside of a kernel build now default to
261 installing to /boot/modules instead of /boot/kernel. Many kernel
262 modules built this way (such as those in ports) already overrode
263 KMODDIR explicitly to install into /boot/modules. However,
264 manually building and installing a module from /sys/modules will
265 now install to /boot/modules instead of /boot/kernel.
268 The CAM I/O scheduler has been committed to the kernel. There should be
269 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
270 list of known rogues that claim support for this but actually corrupt
271 data is believed to be complete, be on the lookout for data
272 corruption. The known rogue list is believed to be complete:
274 o Crucial MX100, M550 drives with MU01 firmware.
275 o Micron M510 and M550 drives with MU01 firmware.
276 o Micron M500 prior to MU07 firmware
277 o Samsung 830, 840, and 850 all firmwares
278 o FCCT M500 all firmwares
280 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
281 with working NCQ TRIM. For Micron branded drives, see your sales rep for
282 updated firmware. Black listed drives will work correctly because these
283 drives work correctly so long as no NCQ TRIMs are sent to them. Given
284 this list is the same as found in Linux, it's believed there are no
285 other rogues in the market place. All other models from the above
288 To be safe, if you are at all concerned, you can quirk each of your
289 drives to prevent NCQ from being sent by setting:
290 kern.cam.ada.X.quirks="0x2"
291 in loader.conf. If the drive requires the 4k sector quirk, set the
295 The FAST_DEPEND build option has been removed and its functionality is
296 now the one true way. The old mkdep(1) style of 'make depend' has
297 been removed. See 20160311 for further details.
300 Resource range types have grown from unsigned long to uintmax_t. All
301 drivers, and anything using libdevinfo, need to be recompiled.
304 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
305 builds. It no longer runs mkdep(1) during 'make depend', and the
306 'make depend' stage can safely be skipped now as it is auto ran
307 when building 'make all' and will generate all SRCS and DPSRCS before
308 building anything else. Dependencies are gathered at compile time with
309 -MF flags kept in separate .depend files per object file. Users should
310 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
314 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
315 kernel modules. Therefore, if you load any kernel modules at boot time,
316 please install the boot loaders after you install the kernel, but before
320 make kernel KERNCONF=YOUR_KERNEL_HERE
321 make -C sys/boot install
322 <reboot in single user>
324 Then follow the usual steps, described in the General Notes section,
328 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
329 see the 20141231 entry below for information about prerequisites and
330 upgrading, if you are not already using clang 3.5.0 or higher.
333 The AIO subsystem is now a standard part of the kernel. The
334 VFS_AIO kernel option and aio.ko kernel module have been removed.
335 Due to stability concerns, asynchronous I/O requests are only
336 permitted on sockets and raw disks by default. To enable
337 asynchronous I/O requests on all file types, set the
338 vfs.aio.enable_unsafe sysctl to a non-zero value.
341 The ELF object manipulation tool objcopy is now provided by the
342 ELF Tool Chain project rather than by GNU binutils. It should be a
343 drop-in replacement, with the addition of arm64 support. The
344 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
345 to obtain the GNU version if necessary.
348 Building ZFS pools on top of zvols is prohibited by default. That
349 feature has never worked safely; it's always been prone to deadlocks.
350 Using a zvol as the backing store for a VM guest's virtual disk will
351 still work, even if the guest is using ZFS. Legacy behavior can be
352 restored by setting vfs.zfs.vol.recursive=1.
355 The NONE and HPN patches has been removed from OpenSSH. They are
356 still available in the security/openssh-portable port.
359 With the addition of ypldap(8), a new _ypldap user is now required
360 during installworld. "mergemaster -p" can be used to add the user
361 prior to installworld, as documented in the handbook.
364 The tftp loader (pxeboot) now uses the option root-path directive. As a
365 consequence it no longer looks for a pxeboot.4th file on the tftp
366 server. Instead it uses the regular /boot infrastructure as with the
370 The code to start recording plug and play data into the modules has
371 been committed. While the old tools will properly build a new kernel,
372 a number of warnings about "unknown metadata record 4" will be produced
373 for an older kldxref. To avoid such warnings, make sure to rebuild
374 the kernel toolchain (or world). Make sure that you have r292078 or
375 later when trying to build 292077 or later before rebuilding.
378 Debug data files are now built by default with 'make buildworld' and
379 installed with 'make installworld'. This facilitates debugging but
380 requires more disk space both during the build and for the installed
381 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
385 r291527 changed the internal interface between the nfsd.ko and
386 nfscommon.ko modules. As such, they must both be upgraded to-gether.
387 __FreeBSD_version has been bumped because of this.
390 Add support for unicode collation strings leads to a change of
391 order of files listed by ls(1) for example. To get back to the old
392 behaviour, set LC_COLLATE environment variable to "C".
394 Databases administrators will need to reindex their databases given
395 collation results will be different.
397 Due to a bug in install(1) it is recommended to remove the ancient
398 locales before running make installworld.
400 rm -rf /usr/share/locale/*
403 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
404 libcrypto.so.7 or libssl.so.7 must be recompiled.
407 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
408 Kernel modules isp_2400_multi and isp_2500_multi were removed and
409 should be replaced with isp_2400 and isp_2500 modules respectively.
412 The build previously allowed using 'make -n' to not recurse into
413 sub-directories while showing what commands would be executed, and
414 'make -n -n' to recursively show commands. Now 'make -n' will recurse
415 and 'make -N' will not.
418 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
419 and etcupdate will now use this file. A custom sendmail.cf is now
420 updated via this mechanism rather than via installworld. If you had
421 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
422 want to remove the exclusion or change it to "always install".
423 /etc/mail/sendmail.cf is now managed the same way regardless of
424 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
425 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
428 Compatibility shims for legacy ATA device names have been removed.
429 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
430 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
431 environment variables, /dev/ad* and /dev/ar* symbolic links.
434 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
435 Please see the 20141231 entry below for information about prerequisites
436 and upgrading, if you are not already using clang 3.5.0 or higher.
439 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
440 and renamed from .symbols to .debug. This reduces the size requirements
441 on the boot partition or file system and provides consistency with
442 userland debug files.
444 When using the supported kernel installation method the
445 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
446 as is done with /boot/kernel.
448 Developers wishing to maintain the historical behavior of installing
449 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
452 The wireless drivers had undergone changes that remove the 'parent
453 interface' from the ifconfig -l output. The rc.d network scripts
454 used to check presence of a parent interface in the list, so old
455 scripts would fail to start wireless networking. Thus, etcupdate(3)
456 or mergemaster(8) run is required after kernel update, to update your
457 rc.d scripts in /etc.
460 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
461 These configurations are now automatically interpreted as
462 'scrub fragment reassemble'.
465 Kernel-loadable modules for the random(4) device are back. To use
466 them, the kernel must have
469 options RANDOM_LOADABLE
471 kldload(8) can then be used to load random_fortuna.ko
472 or random_yarrow.ko. Please note that due to the indirect
473 function calls that the loadable modules need to provide,
474 the build-in variants will be slightly more efficient.
476 The random(4) kernel option RANDOM_DUMMY has been retired due to
477 unpopularity. It was not all that useful anyway.
480 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
481 Control over building the ELF Tool Chain tools is now provided by
482 the WITHOUT_TOOLCHAIN knob.
485 The polarity of Pulse Per Second (PPS) capture events with the
486 uart(4) driver has been corrected. Prior to this change the PPS
487 "assert" event corresponded to the trailing edge of a positive PPS
488 pulse and the "clear" event was the leading edge of the next pulse.
490 As the width of a PPS pulse in a typical GPS receiver is on the
491 order of 1 millisecond, most users will not notice any significant
492 difference with this change.
494 Anyone who has compensated for the historical polarity reversal by
495 configuring a negative offset equal to the pulse width will need to
496 remove that workaround.
499 The default group assigned to /dev/dri entries has been changed
500 from 'wheel' to 'video' with the id of '44'. If you want to have
501 access to the dri devices please add yourself to the video group
504 # pw groupmod video -m $USER
507 The menu.rc and loader.rc files will now be replaced during
508 upgrades. Please migrate local changes to menu.rc.local and
509 loader.rc.local instead.
512 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
513 strings and strip have been removed. The src.conf(5) knob
514 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
517 As ZFS requires more kernel stack pages than is the default on some
518 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
519 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
521 Please consider using 'options KSTACK_PAGES=X' where X is greater
522 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
525 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
526 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
527 default, i.e., they will not contain "::". For example, instead
528 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
529 to have a more specific match, such as different map entries for
530 IPv6:0:0 vs IPv6:0. This change requires that configuration
531 data (including maps, files, classes, custom ruleset, etc.) must
532 use the same format, so make certain such configuration data is
533 upgrading. As a very simple check search for patterns like
534 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
535 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
536 the cf option UseCompressedIPv6Addresses.
539 The default kernel entropy-processing algorithm is now
540 Fortuna, replacing Yarrow.
542 Assuming you have 'device random' in your kernel config
543 file, the configurations allow a kernel option to override
544 this default. You may choose *ONE* of:
546 options RANDOM_YARROW # Legacy /dev/random algorithm.
547 options RANDOM_DUMMY # Blocking-only driver.
549 If you have neither, you get Fortuna. For most people,
550 read no further, Fortuna will give a /dev/random that works
551 like it always used to, and the difference will be irrelevant.
553 If you remove 'device random', you get *NO* kernel-processed
554 entropy at all. This may be acceptable to folks building
555 embedded systems, but has complications. Carry on reading,
556 and it is assumed you know what you need.
558 *PLEASE* read random(4) and random(9) if you are in the
559 habit of tweaking kernel configs, and/or if you are a member
560 of the embedded community, wanting specific and not-usual
561 behaviour from your security subsystems.
563 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
564 random', you will NOT have a functioning /dev/random, and
565 many cryptographic features will not work, including SSH.
566 You may also find strange behaviour from the random(3) set
567 of library functions, in particular sranddev(3), srandomdev(3)
568 and arc4random(3). The reason for this is that the KERN_ARND
569 sysctl only returns entropy if it thinks it has some to
570 share, and with RANDOM_DUMMY or no 'device random' this
574 An additional fix for the issue described in the 20150614 sendmail
575 entry below has been been committed in revision 284717.
578 FreeBSD's old make (fmake) has been removed from the system. It is
579 available as the devel/fmake port or via pkg install fmake.
582 The fix for the issue described in the 20150614 sendmail entry
583 below has been been committed in revision 284436. The work
584 around described in that entry is no longer needed unless the
585 default setting is overridden by a confDH_PARAMETERS configuration
586 setting of '5' or pointing to a 512 bit DH parameter file.
589 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
590 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
591 and devel/kyua to version 0.20+ and adjust any calling code to work
592 with Kyuafile and kyua.
595 The import of openssl to address the FreeBSD-SA-15:10.openssl
596 security advisory includes a change which rejects handshakes
597 with DH parameters below 768 bits. sendmail releases prior
598 to 8.15.2 (not yet released), defaulted to a 512 bit
599 DH parameter setting for client connections. To work around
600 this interoperability, sendmail can be configured to use a
601 2048 bit DH parameter by:
603 1. Edit /etc/mail/`hostname`.mc
604 2. If a setting for confDH_PARAMETERS does not exist or
605 exists and is set to a string beginning with '5',
607 3. If a setting for confDH_PARAMETERS exists and is set to
608 a file path, create a new file with:
609 openssl dhparam -out /path/to/file 2048
610 4. Rebuild the .cf file:
611 cd /etc/mail/; make; make install
613 cd /etc/mail/; make restart
615 A sendmail patch is coming, at which time this file will be
619 Generation of legacy formatted entries have been disabled by default
620 in pwd_mkdb(8), as all base system consumers of the legacy formatted
621 entries were converted to use the new format by default when the new,
622 machine independent format have been added and supported since FreeBSD
625 Please see the pwd_mkdb(8) manual page for further details.
628 Clang and llvm have been upgraded to 3.6.1 release. Please see the
629 20141231 entry below for information about prerequisites and upgrading,
630 if you are not already using 3.5.0 or higher.
633 TI platform code switched to using vendor DTS files and this update
634 may break existing systems running on Beaglebone, Beaglebone Black,
637 - dtb files should be regenerated/reinstalled. Filenames are the
638 same but content is different now
639 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
640 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
641 addressing scheme is now pin 25 on /dev/gpioc3.
642 - Pandaboard: /etc/ttys should be updated, serial console device is
643 now /dev/ttyu2, not /dev/ttyu0
646 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
647 If you need the GNU extension from groff soelim(1), install groff
648 from package: pkg install groff, or via ports: textproc/groff.
651 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
652 defined in symlink(7); previously symlinks were silently ignored.
655 The const qualifier has been removed from iconv(3) to comply with
656 POSIX. The ports tree is aware of this from r384038 onwards.
659 Libraries specified by LIBADD in Makefiles must have a corresponding
660 DPADD_<lib> variable to ensure correct dependencies. This is now
661 enforced in src.libnames.mk.
664 From legacy ata(4) driver was removed support for SATA controllers
665 supported by more functional drivers ahci(4), siis(4) and mvs(4).
666 Kernel modules ataahci and ataadaptec were removed completely,
667 replaced by ahci and mvs modules respectively.
670 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
671 the 20141231 entry below for information about prerequisites and
672 upgrading, if you are not already using 3.5.0 or higher.
675 The 32-bit PowerPC kernel has been changed to a position-independent
676 executable. This can only be booted with a version of loader(8)
677 newer than January 31, 2015, so make sure to update both world and
678 kernel before rebooting.
681 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
682 but before r278950, the RNG was not seeded properly. Immediately
683 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
684 ssh keys or openssl keys) that were generated w/ a kernel from that
685 range. This does not affect programs that directly used /dev/random
686 or /dev/urandom. All userland uses of arc4random(3) are affected.
689 The autofs(4) ABI was changed in order to restore binary compatibility
690 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
694 The powerpc64 kernel has been changed to a position-independent
695 executable. This can only be booted with a new version of loader(8),
696 so make sure to update both world and kernel before rebooting.
699 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
700 only release, no new features have been added. Please see the 20141231
701 entry below for information about prerequisites and upgrading, if you
702 are not already using 3.5.0.
705 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
706 taken from the ELF Tool Chain project rather than GNU binutils. They
707 should be drop-in replacements, with the addition of arm64 support.
708 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
709 binutils tools, if necessary. See 20150805 for updated information.
712 The default Unbound configuration now enables remote control
713 using a local socket. Users who have already enabled the
714 local_unbound service should regenerate their configuration
715 by running "service local_unbound setup" as root.
718 The GNU texinfo and GNU info pages have been removed.
719 To be able to view GNU info pages please install texinfo from ports.
722 Clang, llvm and lldb have been upgraded to 3.5.0 release.
724 As of this release, a prerequisite for building clang, llvm and lldb is
725 a C++11 capable compiler and C++11 standard library. This means that to
726 be able to successfully build the cross-tools stage of buildworld, with
727 clang as the bootstrap compiler, your system compiler or cross compiler
728 should either be clang 3.3 or later, or gcc 4.8 or later, and your
729 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
732 On any standard FreeBSD 10.x or 11.x installation, where clang and
733 libc++ are on by default (that is, on x86 or arm), this should work out
736 On 9.x installations where clang is enabled by default, e.g. on x86 and
737 powerpc, libc++ will not be enabled by default, so libc++ should be
738 built (with clang) and installed first. If both clang and libc++ are
739 missing, build clang first, then use it to build libc++.
741 On 8.x and earlier installations, upgrade to 9.x first, and then follow
742 the instructions for 9.x above.
744 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
745 default, and do not build clang.
747 Many embedded systems are resource constrained, and will not be able to
748 build clang in a reasonable time, or in some cases at all. In those
749 cases, cross building bootable systems on amd64 is a workaround.
751 This new version of clang introduces a number of new warnings, of which
752 the following are most likely to appear:
756 This warns in two cases, for both C and C++:
757 * When the code is trying to take the absolute value of an unsigned
758 quantity, which is effectively a no-op, and almost never what was
759 intended. The code should be fixed, if at all possible. If you are
760 sure that the unsigned quantity can be safely cast to signed, without
761 loss of information or undefined behavior, you can add an explicit
762 cast, or disable the warning.
764 * When the code is trying to take an absolute value, but the called
765 abs() variant is for the wrong type, which can lead to truncation.
766 If you want to disable the warning instead of fixing the code, please
767 make sure that truncation will not occur, or it might lead to unwanted
770 -Wtautological-undefined-compare and
771 -Wundefined-bool-conversion
773 These warn when C++ code is trying to compare 'this' against NULL, while
774 'this' should never be NULL in well-defined C++ code. However, there is
775 some legacy (pre C++11) code out there, which actively abuses this
776 feature, which was less strictly defined in previous C++ versions.
778 Squid and openjdk do this, for example. The warning can be turned off
779 for C++98 and earlier, but compiling the code in C++11 mode might result
780 in unexpected behavior; for example, the parts of the program that are
781 unreachable could be optimized away.
784 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
785 kernel sources have been removed. The .h files remain, since some
786 utilities include them. This will need to be fixed later.
787 If "mount -t oldnfs ..." is attempted, it will fail.
788 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
789 the utilities will report errors.
792 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
793 directories to top level SUBDIR variable when their parent
794 directory is included in LOCAL_DIRS. Users with build systems with
795 such hierarchies and without SUBDIR entries in the parent
796 directory Makefiles should add them or add the directories to
800 faith(4) and faithd(8) have been removed from the base system. Faith
801 has been obsolete for a very long time.
804 vt(4), the new console driver, is enabled by default. It brings
805 support for Unicode and double-width characters, as well as
806 support for UEFI and integration with the KMS kernel video
809 You may need to update your console settings in /etc/rc.conf,
810 most probably the keymap. During boot, /etc/rc.d/syscons will
811 indicate what you need to do.
813 vt(4) still has issues and lacks some features compared to
814 syscons(4). See the wiki for up-to-date information:
815 https://wiki.freebsd.org/Newcons
817 If you want to keep using syscons(4), you can do so by adding
818 the following line to /boot/loader.conf:
822 pjdfstest has been integrated into kyua as an opt-in test suite.
823 Please see share/doc/pjdfstest/README for more details on how to
827 gperf has been removed from the base system for architectures
828 that use clang. Ports that require gperf will obtain it from the
832 pjdfstest has been moved from tools/regression/pjdfstest to
836 At svn r271982, The default linux compat kernel ABI has been adjusted
837 to 2.6.18 in support of the linux-c6 compat ports infrastructure
838 update. If you wish to continue using the linux-f10 compat ports,
839 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
840 encouraged to update their linux-compat packages to linux-c6 during
841 their next update cycle.
844 The ofwfb driver, used to provide a graphics console on PowerPC when
845 using vt(4), no longer allows mmap() of all physical memory. This
846 will prevent Xorg on PowerPC with some ATI graphics cards from
847 initializing properly unless x11-servers/xorg-server is updated to
851 The xdev targets have been converted to using TARGET and
852 TARGET_ARCH instead of XDEV and XDEV_ARCH.
855 The default unbound configuration has been modified to address
856 issues with reverse lookups on networks that use private
857 address ranges. If you use the local_unbound service, run
858 "service local_unbound setup" as root to regenerate your
859 configuration, then "service local_unbound reload" to load the
863 The GNU texinfo and GNU info pages are not built and installed
864 anymore, WITH_INFO knob has been added to allow to built and install
866 UPDATE: see 20150102 entry on texinfo's removal
869 The GNU readline library is now an INTERNALLIB - that is, it is
870 statically linked into consumers (GDB and variants) in the base
871 system, and the shared library is no longer installed. The
872 devel/readline port is available for third party software that
876 The Itanium architecture (ia64) has been removed from the list of
877 known architectures. This is the first step in the removal of the
881 Commit r268115 has added NFSv4.1 server support, merged from
882 projects/nfsv4.1-server. Since this includes changes to the
883 internal interfaces between the NFS related modules, a full
884 build of the kernel and modules will be necessary.
885 __FreeBSD_version has been bumped.
888 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
889 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
890 which differs from the behaviour controlled by this knob.)
893 Maximal length of the serial number in CTL was increased from 16 to
894 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
895 and ctld, need to be rebuilt to work with a new kernel.
898 The libatf-c and libatf-c++ major versions were downgraded to 0 and
899 1 respectively to match the upstream numbers. They were out of
900 sync because, when they were originally added to FreeBSD, the
901 upstream versions were not respected. These libraries are private
902 and not yet built by default, so renumbering them should be a
903 non-issue. However, unclean source trees will yield broken test
904 programs once the operator executes "make delete-old-libs" after a
907 Additionally, the atf-sh binary was made private by moving it into
908 /usr/libexec/. Already-built shell test programs will keep the
909 path to the old binary so they will break after "make delete-old"
912 If you are using WITH_TESTS=yes (not the default), wipe the object
913 tree and rebuild from scratch to prevent spurious test failures.
914 This is only needed once: the misnumbered libraries and misplaced
915 binaries have been added to OptionalObsoleteFiles.inc so they will
916 be removed during a clean upgrade.
919 Clang and llvm have been upgraded to 3.4.1 release.
922 We bogusly installed src.opts.mk in /usr/share/mk. This file should
923 be removed to avoid issues in the future (and has been added to
927 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
928 past, it affected all builds that used the bsd.*.mk files. The old
929 behavior was a bug, but people may have relied upon it. To get this
930 behavior back, you can .include /etc/src.conf from /etc/make.conf
931 (which is still global and isn't changed). This also changes the
932 behavior of incremental builds inside the tree of individual
933 directories. Set MAKESYSPATH to ".../share/mk" to do that.
934 Although this has survived make universe and some upgrade scenarios,
935 other upgrade scenarios may have broken. At least one form of
936 temporary breakage was fixed with MAKESYSPATH settings for buildworld
937 as well... In cases where MAKESYSPATH isn't working with this
938 setting, you'll need to set it to the full path to your tree.
940 One side effect of all this cleaning up is that bsd.compiler.mk
941 is no longer implicitly included by bsd.own.mk. If you wish to
942 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
946 The lindev device has been removed since /dev/full has been made a
947 standard device. __FreeBSD_version has been bumped.
950 The knob WITHOUT_VI was added to the base system, which controls
951 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
952 in order to reorder files share/termcap and didn't build ex(1) as a
953 build tool, so building/installing with WITH_VI is highly advised for
954 build hosts for older releases.
956 This issue has been fixed in stable/9 and stable/10 in r277022 and
957 r276991, respectively.
960 The YES_HESIOD knob has been removed. It has been obsolete for
961 a decade. Please move to using WITH_HESIOD instead or your builds
962 will silently lack HESIOD.
965 The uart(4) driver has been changed with respect to its handling
966 of the low-level console. Previously the uart(4) driver prevented
967 any process from changing the baudrate or the CLOCAL and HUPCL
968 control flags. By removing the restrictions, operators can make
969 changes to the serial console port without having to reboot.
970 However, when getty(8) is started on the serial device that is
971 associated with the low-level console, a misconfigured terminal
972 line in /etc/ttys will now have a real impact.
973 Before upgrading the kernel, make sure that /etc/ttys has the
974 serial console device configured as 3wire without baudrate to
975 preserve the previous behaviour. E.g:
976 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
979 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
980 to improve performance. To re-enable it, if needed, run rpcbind
981 with command line option -W.
984 Switched back to the GPL dtc compiler due to updates in the upstream
985 dts files not being supported by the BSDL dtc compiler. You will need
986 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
987 may result while building dtb files during a kernel build if you fail
988 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
991 Clang and llvm have been upgraded to 3.4 release.
994 The nve(4) driver has been removed. Please use the nfe(4) driver
995 for NVIDIA nForce MCP Ethernet adapters instead.
998 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
999 This could cause certain C++ applications using shared libraries built
1000 against the previous version of libc++ to crash. The incompatibility
1001 has now been fixed, but any C++ applications or shared libraries built
1002 between r261283 and r261801 should be recompiled.
1005 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1006 capability mode support. Please note that enabling the feature in
1007 kernel is still highly recommended.
1010 OpenSSH is now built with sandbox support, and will use sandbox as
1011 the default privilege separation method. This requires Capsicum
1012 capability mode support in kernel.
1015 The libelf and libdwarf libraries have been updated to newer
1016 versions from upstream. Shared library version numbers for
1017 these two libraries were bumped. Any ports or binaries
1018 requiring these two libraries should be recompiled.
1019 __FreeBSD_version is bumped to 1100006.
1022 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1023 instead of providing an explicit one, this would prevent such
1024 Makefile from providing its own Kyuafile in the future during
1025 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1026 intervention is needed to clean an objdir if you use NO_CLEAN:
1027 # find /usr/obj -name Kyuafile | xargs rm -f
1030 The behavior of gss_pseudo_random() for the krb5 mechanism
1031 has changed, for applications requesting a longer random string
1032 than produced by the underlying enctype's pseudo-random() function.
1033 In particular, the random string produced from a session key of
1034 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1035 be different at the 17th octet and later, after this change.
1036 The counter used in the PRF+ construction is now encoded as a
1037 big-endian integer in accordance with RFC 4402.
1038 __FreeBSD_version is bumped to 1100004.
1041 The WITHOUT_ATF build knob has been removed and its functionality
1042 has been subsumed into the more generic WITHOUT_TESTS. If you were
1043 using the former to disable the build of the ATF libraries, you
1044 should change your settings to use the latter.
1047 The default version of mtree is nmtree which is obtained from
1048 NetBSD. The output is generally the same, but may vary
1049 slightly. If you found you need identical output adding
1050 "-F freebsd9" to the command line should do the trick. For the
1051 time being, the old mtree is available as fmtree.
1054 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1055 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1056 1.1.4_8 and verify bsdyml not linked in, before running "make
1058 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1060 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1063 The stable/10 branch has been created in subversion from head
1067 The rc.d/jail script has been updated to support jail(8)
1068 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1069 for per-jail configuration are automatically converted to
1070 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1071 This is transparently backward compatible. See below about some
1072 incompatibilities and rc.conf(5) manual page for more details.
1074 These variables are now deprecated in favor of jail(8) configuration
1075 file. One can use "rc.d/jail config <jname>" command to generate
1076 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1077 running the jail(8) utility. The default pathname of the
1078 configuration file is /etc/jail.conf and can be specified by
1079 using $jail_conf or $jail_<jname>_conf variables.
1081 Please note that jail_devfs_ruleset accepts an integer at
1082 this moment. Please consider to rewrite the ruleset name
1086 BIND has been removed from the base system. If all you need
1087 is a local resolver, simply enable and start the local_unbound
1088 service instead. Otherwise, several versions of BIND are
1089 available in the ports tree. The dns/bind99 port is one example.
1091 With this change, nslookup(1) and dig(1) are no longer in the base
1092 system. Users should instead use host(1) and drill(1) which are
1093 in the base system. Alternatively, nslookup and dig can
1094 be obtained by installing the dns/bind-tools port.
1097 With the addition of unbound(8), a new unbound user is now
1098 required during installworld. "mergemaster -p" can be used to
1099 add the user prior to installworld, as documented in the handbook.
1102 OpenSSH is now built with DNSSEC support, and will by default
1103 silently trust signed SSHFP records. This can be controlled with
1104 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1105 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1108 The GNU Compiler Collection and C++ standard library (libstdc++)
1109 are no longer built by default on platforms where clang is the system
1110 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1111 options in src.conf.
1114 The PROCDESC kernel option is now part of the GENERIC kernel
1115 configuration and is required for the rwhod(8) to work.
1116 If you are using custom kernel configuration, you should include
1120 The API and ABI related to the Capsicum framework was modified
1121 in backward incompatible way. The userland libraries and programs
1122 have to be recompiled to work with the new kernel. This includes the
1123 following libraries and programs, but the whole buildworld is
1124 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1125 kdump, procstat, rwho, rwhod, uniq.
1128 AES-NI intrinsic support has been added to gcc. The AES-NI module
1129 has been updated to use this support. A new gcc is required to build
1130 the aesni module on both i386 and amd64.
1133 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1134 Thus "device padlock_rng" and "device rdrand_rng" should be
1135 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1138 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1139 enables just the iconv* functionality and is now on by default.
1140 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1141 compatibility. Set WITHOUT_ICONV to build the old way.
1142 If you have been using WITH_ICONV before, you will very likely
1143 need to turn on WITH_LIBICONV_COMPAT.
1146 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1147 Illumos origin, including ZFS. If you have INVARIANTS in your
1148 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1150 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1151 locks if WITNESS option was set. Because that generated a lot of
1152 witness(9) reports and all of them were believed to be false
1153 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1154 can be used to achieve the previous behavior.
1157 Timer values in IPv6 data structures now use time_uptime instead
1158 of time_second. Although this is not a user-visible functional
1159 change, userland utilities which directly use them---ndp(8),
1160 rtadvd(8), and rtsold(8) in the base system---need to be updated
1161 to r253970 or later.
1164 find -delete can now delete the pathnames given as arguments,
1165 instead of only files found below them or if the pathname did
1166 not contain any slashes. Formerly, the following error message
1169 find: -delete: <path>: relative path potentially not safe
1171 Deleting the pathnames given as arguments can be prevented
1172 without error messages using -mindepth 1 or by changing
1173 directory and passing "." as argument to find. This works in the
1174 old as well as the new version of find.
1177 Behavior of devfs rules path matching has been changed.
1178 Pattern is now always matched against fully qualified devfs
1179 path and slash characters must be explicitly matched by
1180 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1181 subdirectories must be reviewed.
1184 The default ARM ABI has changed to the ARM EABI. The old ABI is
1185 incompatible with the ARM EABI and all programs and modules will
1186 need to be rebuilt to work with a new kernel.
1188 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1190 NOTE: Support for the old ABI will be removed in the future and
1191 users are advised to upgrade.
1194 pkg_install has been disconnected from the build if you really need it
1195 you should add WITH_PKGTOOLS in your src.conf(5).
1198 Most of network statistics structures were changed to be able
1199 keep 64-bits counters. Thus all tools, that work with networking
1200 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1203 Fix a bug that allowed a tracing process (e.g. gdb) to write
1204 to a memory-mapped file in the traced process's address space
1205 even if neither the traced process nor the tracing process had
1206 write access to that file.
1209 CVS has been removed from the base system. An exact copy
1210 of the code is available from the devel/cvs port.
1213 Some people report the following error after the switch to bmake:
1215 make: illegal option -- J
1216 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1218 *** [buildworld] Error code 2
1220 this likely due to an old instance of make in
1221 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1222 which src/Makefile will use that blindly, if it exists, so if
1223 you see the above error:
1225 rm -rf `make -V MAKEPATH`
1230 Use bmake by default.
1231 Whereas before one could choose to build with bmake via
1232 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1233 make. The goal is to remove these knobs for 10-RELEASE.
1235 It is worth noting that bmake (like gmake) treats the command
1236 line as the unit of failure, rather than statements within the
1237 command line. Thus '(cd some/where && dosomething)' is safer
1238 than 'cd some/where; dosomething'. The '()' allows consistent
1239 behavior in parallel build.
1242 Fix a bug that allows NFS clients to issue READDIR on files.
1245 The WITHOUT_IDEA option has been removed because
1246 the IDEA patent expired.
1249 The sysctl which controls TRIM support under ZFS has been renamed
1250 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1254 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1255 rather than creating it's own in the temporary directory in
1256 order allow access to bootstrapped versions of tools such as
1257 install and mtree. When upgrading from version of FreeBSD where
1258 the install command does not support -l, you will need to
1259 install a new mergemaster command if mergemaster -p is required.
1260 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1264 Legacy ATA stack, disabled and replaced by new CAM-based one since
1265 FreeBSD 9.0, completely removed from the sources. Kernel modules
1266 atadisk and atapi*, user-level tools atacontrol and burncd are
1267 removed. Kernel option `options ATA_CAM` is now permanently enabled
1271 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1272 and socketpair(2). Software, in particular Kerberos, may
1273 automatically detect and use these during building. The resulting
1274 binaries will not work on older kernels.
1277 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1278 information, see the respective 20130304 entry).
1281 Recent commits to callout(9) changed the size of struct callout,
1282 so the KBI is probably heavily disturbed. Also, some functions
1283 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1284 by macros. Every kernel module using it won't load, so rebuild
1287 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1288 but does not initialize by default (because of the new CTL_DISABLE
1289 option) to save memory. To re-enable it, remove the CTL_DISABLE
1290 option from the kernel config file or set kern.cam.ctl.disable=0
1291 in /boot/loader.conf.
1294 The ctl device has been disabled in GENERIC for i386 and amd64.
1295 This was done due to the extra memory being allocated at system
1296 initialisation time by the ctl driver which was only used if
1297 a CAM target device was created. This makes a FreeBSD system
1298 unusable on 128MB or less of RAM.
1301 A new compression method (lz4) has been merged to -HEAD. Please
1302 refer to zpool-features(7) for more information.
1304 Please refer to the "ZFS notes" section of this file for information
1305 on upgrading boot ZFS pools.
1308 A BSD-licensed patch(1) variant has been added and is installed
1309 as bsdpatch, being the GNU version the default patch.
1310 To inverse the logic and use the BSD-licensed one as default,
1311 while having the GNU version installed as gnupatch, rebuild
1312 and install world with the WITH_BSD_PATCH knob set.
1315 Due to the use of the new -l option to install(1) during build
1316 and install, you must take care not to directly set the INSTALL
1317 make variable in your /etc/make.conf, /etc/src.conf, or on the
1318 command line. If you wish to use the -C flag for all installs
1319 you may be able to add INSTALL+=-C to /etc/make.conf or
1323 The install(1) option -M has changed meaning and now takes an
1324 argument that is a file or path to append logs to. In the
1325 unlikely event that -M was the last option on the command line
1326 and the command line contained at least two files and a target
1327 directory the first file will have logs appended to it. The -M
1328 option served little practical purpose in the last decade so its
1329 use is expected to be extremely rare.
1332 After switching to Clang as the default compiler some users of ZFS
1333 on i386 systems started to experience stack overflow kernel panics.
1334 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1337 GEOM_LABEL now mangles label names read from file system metadata.
1338 Mangling affect labels containing spaces, non-printable characters,
1339 '%' or '"'. Device names in /etc/fstab and other places may need to
1343 By default, only the 10 most recent kernel dumps will be saved. To
1344 restore the previous behaviour (no limit on the number of kernel dumps
1345 stored in the dump directory) add the following line to /etc/rc.conf:
1350 With the addition of auditdistd(8), a new auditdistd user is now
1351 required during installworld. "mergemaster -p" can be used to
1352 add the user prior to installworld, as documented in the handbook.
1355 The sin6_scope_id member variable in struct sockaddr_in6 is now
1356 filled by the kernel before passing the structure to the userland via
1357 sysctl or routing socket. This means the KAME-specific embedded scope
1358 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1359 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1360 __FreeBSD_version is bumped to 1000025.
1363 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1364 This means that the world and kernel will be compiled with clang
1365 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1366 and /usr/bin/cpp. To disable this behavior and revert to building
1367 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1368 of current may need to bootstrap WITHOUT_CLANG first if the clang
1369 build fails (its compatibility window doesn't extend to the 9 stable
1373 The IPFIREWALL_FORWARD kernel option has been removed. Its
1374 functionality now turned on by default.
1377 The ZERO_COPY_SOCKET kernel option has been removed and
1378 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1379 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1380 mechanism which is not safe and may result in kernel crashes.
1381 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1382 driver supports disposeable external page sized mbuf storage.
1383 Proper replacements for both zero-copy mechanisms are under
1384 consideration and will eventually lead to complete removal
1385 of the two kernel options.
1388 The IPv4 network stack has been converted to network byte
1389 order. The following modules need to be recompiled together
1390 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1391 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1394 Support for non-MPSAFE filesystems was removed from VFS. The
1395 VFS_VERSION was bumped, all filesystem modules shall be
1399 All the non-MPSAFE filesystems have been disconnected from
1400 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1401 portalfs, smbfs, xfs.
1404 The interface cloning API and ABI has changed. The following
1405 modules need to be recompiled together with kernel:
1406 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1407 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1408 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1411 The sdhci driver was split in two parts: sdhci (generic SD Host
1412 Controller logic) and sdhci_pci (actual hardware driver).
1413 No kernel config modifications are required, but if you
1414 load sdhc as a module you must switch to sdhci_pci instead.
1417 Import the FUSE kernel and userland support into base system.
1420 The GNU sort(1) program has been removed since the BSD-licensed
1421 sort(1) has been the default for quite some time and no serious
1422 problems have been reported. The corresponding WITH_GNU_SORT
1426 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1427 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1431 The net80211(4) ABI has been changed to allow for improved driver
1432 PS-POLL and power-save support. All wireless drivers need to be
1433 recompiled to work with the new kernel.
1436 The random(4) support for the VIA hardware random number
1437 generator (`PADLOCK') is no longer enabled unconditionally.
1438 Add the padlock_rng device in the custom kernel config if
1439 needed. The GENERIC kernels on i386 and amd64 do include the
1440 device, so the change only affects the custom kernel
1444 The pf(4) packet filter ABI has been changed. pfctl(8) and
1445 snmp_pf module need to be recompiled to work with new kernel.
1448 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1449 to -HEAD. Pools that have empty_bpobj in active state can not be
1450 imported read-write with ZFS implementations that do not support
1451 this feature. For more information read the zpool-features(5)
1455 The sparc64 ZFS loader has been changed to no longer try to auto-
1456 detect ZFS providers based on diskN aliases but now requires these
1457 to be explicitly listed in the OFW boot-device environment variable.
1460 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1461 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1462 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1465 The following sysctls and tunables have been renamed for consistency
1466 with other variables:
1467 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1468 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1471 The sort utility has been replaced with BSD sort. For now, GNU sort
1472 is also available as "gnusort" or the default can be set back to
1473 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1474 installed as "bsdsort".
1477 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1478 Starting with this version the old system of ZFS pool versioning
1479 is superseded by "feature flags". This concept enables forward
1480 compatibility against certain future changes in functionality of ZFS
1481 pools. The first read-only compatible "feature flag" for ZFS pools
1482 is named "com.delphix:async_destroy". For more information
1483 read the new zpool-features(5) manual page.
1484 Please refer to the "ZFS notes" section of this file for information
1485 on upgrading boot ZFS pools.
1488 The malloc(3) implementation embedded in libc now uses sources imported
1489 as contrib/jemalloc. The most disruptive API change is to
1490 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1491 delete it prior to installworld, and optionally re-create it using the
1492 new format after rebooting. See malloc.conf(5) for details
1493 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1497 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1498 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1499 now spelled mips. This is to aid compatibility with third-party
1500 software that expects this naming scheme in uname(3). Little-endian
1501 settings are unchanged. If you are updating a big-endian mips64 machine
1502 from before this change, you may need to set MACHINE_ARCH=mips64 in
1503 your environment before the new build system will recognize your machine.
1506 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1510 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1511 nullfs(5) did not pass through all behaviours to the underlying layer,
1512 as a result if we bound to a socket on the lower layer we could connect
1513 only to the lower path; if we bound to the upper layer we could connect
1514 only to the upper path. The new behavior is one can connect to both the
1515 lower and the upper paths regardless what layer path one binds to.
1518 The getifaddrs upgrade path broken with 20111215 has been restored.
1519 If you have upgraded in between 20111215 and 20120209 you need to
1520 recompile libc again with your kernel. You still need to recompile
1521 world to be able to configure CARP but this restriction already
1522 comes from 20111215.
1525 The set_rcvar() function has been removed from /etc/rc.subr. All
1526 base and ports rc.d scripts have been updated, so if you have a
1527 port installed with a script in /usr/local/etc/rc.d you can either
1528 hand-edit the rcvar= line, or reinstall the port.
1530 An easy way to handle the mass-update of /etc/rc.d:
1531 rm /etc/rc.d/* && mergemaster -i
1534 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1535 on the current CPU and prevents other threads from running.
1536 This behavior can be reverted using the kern.stop_scheduler_on_panic
1538 The new behavior can be incompatible with kern.sync_on_panic.
1541 The carp(4) facility has been changed significantly. Configuration
1542 of the CARP protocol via ifconfig(8) has changed, as well as format
1543 of CARP events submitted to devd(8) has changed. See manual pages
1544 for more information. The arpbalance feature of carp(4) is currently
1545 not supported anymore.
1547 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1548 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1549 need to be recompiled.
1552 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1556 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1557 explicitely support non-MPSAFE filesystems.
1558 It is on by default for all supported platform at this present
1562 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1563 i386 and pc98 GENERIC kernel configuration files.
1566 sysinstall has been removed
1569 The stable/9 branch created in subversion. This corresponds to the
1570 RELENG_9 branch in CVS.
1576 Avoid using make -j when upgrading. While generally safe, there are
1577 sometimes problems using -j to upgrade. If your upgrade fails with
1578 -j, please try again without -j. From time to time in the past there
1579 have been problems using -j with buildworld and/or installworld. This
1580 is especially true when upgrading between "distant" versions (eg one
1581 that cross a major release boundary or several minor releases, or when
1582 several months have passed on the -current branch).
1584 Sometimes, obscure build problems are the result of environment
1585 poisoning. This can happen because the make utility reads its
1586 environment when searching for values for global variables. To run
1587 your build attempts in an "environmental clean room", prefix all make
1588 commands with 'env -i '. See the env(1) manual page for more details.
1590 When upgrading from one major version to another it is generally best
1591 to upgrade to the latest code in the currently installed branch first,
1592 then do an upgrade to the new branch. This is the best-tested upgrade
1593 path, and has the highest probability of being successful. Please try
1594 this approach before reporting problems with a major version upgrade.
1596 When upgrading a live system, having a root shell around before
1597 installing anything can help undo problems. Not having a root shell
1598 around can lead to problems if pam has changed too much from your
1599 starting point to allow continued authentication after the upgrade.
1601 This file should be read as a log of events. When a later event changes
1602 information of a prior event, the prior event should not be deleted.
1603 Instead, a pointer to the entry with the new information should be
1604 placed in the old entry. Readers of this file should also sanity check
1605 older entries before relying on them blindly. Authors of new entries
1606 should write them with this in mind.
1610 When upgrading the boot ZFS pool to a new version, always follow
1613 1.) recompile and reinstall the ZFS boot loader and boot block
1614 (this is part of "make buildworld" and "make installworld")
1616 2.) update the ZFS boot block on your boot drive
1618 The following example updates the ZFS boot block on the first
1619 partition (freebsd-boot) of a GPT partitioned drive ada0:
1620 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1622 Non-boot pools do not need these updates.
1626 If you are updating from a prior version of FreeBSD (even one just
1627 a few days old), you should follow this procedure. It is the most
1628 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1630 make kernel-toolchain
1631 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1632 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1634 To test a kernel once
1635 ---------------------
1636 If you just want to boot a kernel once (because you are not sure
1637 if it works, or if you want to boot a known bad kernel to provide
1638 debugging information) run
1639 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1640 nextboot -k testkernel
1642 To just build a kernel when you know that it won't mess you up
1643 --------------------------------------------------------------
1644 This assumes you are already running a CURRENT system. Replace
1645 ${arch} with the architecture of your machine (e.g. "i386",
1646 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1648 cd src/sys/${arch}/conf
1649 config KERNEL_NAME_HERE
1650 cd ../compile/KERNEL_NAME_HERE
1655 If this fails, go to the "To build a kernel" section.
1657 To rebuild everything and install it on the current system.
1658 -----------------------------------------------------------
1659 # Note: sometimes if you are running current you gotta do more than
1660 # is listed here if you are upgrading from a really old current.
1662 <make sure you have good level 0 dumps>
1664 make kernel KERNCONF=YOUR_KERNEL_HERE
1666 <reboot in single user> [3]
1673 To cross-install current onto a separate partition
1674 --------------------------------------------------
1675 # In this approach we use a separate partition to hold
1676 # current's root, 'usr', and 'var' directories. A partition
1677 # holding "/", "/usr" and "/var" should be about 2GB in
1680 <make sure you have good level 0 dumps>
1683 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1684 <maybe newfs current's root partition>
1685 <mount current's root partition on directory ${CURRENT_ROOT}>
1686 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1687 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1688 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1689 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1690 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1691 <reboot into current>
1692 <do a "native" rebuild/install as described in the previous section>
1693 <maybe install compatibility libraries from ports/misc/compat*>
1697 To upgrade in-place from stable to current
1698 ----------------------------------------------
1699 <make sure you have good level 0 dumps>
1701 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1703 <reboot in single user> [3]
1710 Make sure that you've read the UPDATING file to understand the
1711 tweaks to various things you need. At this point in the life
1712 cycle of current, things change often and you are on your own
1713 to cope. The defaults can also change, so please read ALL of
1714 the UPDATING entries.
1716 Also, if you are tracking -current, you must be subscribed to
1717 freebsd-current@freebsd.org. Make sure that before you update
1718 your sources that you have read and understood all the recent
1719 messages there. If in doubt, please track -stable which has
1720 much fewer pitfalls.
1722 [1] If you have third party modules, such as vmware, you
1723 should disable them at this point so they don't crash your
1726 [3] From the bootblocks, boot -s, and then do
1731 adjkerntz -i # if CMOS is wall time
1732 Also, when doing a major release upgrade, it is required that
1733 you boot into single user mode to do the installworld.
1735 [4] Note: This step is non-optional. Failure to do this step
1736 can result in a significant reduction in the functionality of the
1737 system. Attempting to do it by hand is not recommended and those
1738 that pursue this avenue should read this file carefully, as well
1739 as the archives of freebsd-current and freebsd-hackers mailing lists
1740 for potential gotchas. The -U option is also useful to consider.
1741 See mergemaster(8) for more information.
1743 [5] Usually this step is a noop. However, from time to time
1744 you may need to do this if you get unknown user in the following
1745 step. It never hurts to do it all the time. You may need to
1746 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1747 install) after the buildworld before this step if you last updated
1748 from current before 20130425 or from -stable before 20130430.
1750 [6] This only deletes old files and directories. Old libraries
1751 can be deleted by "make delete-old-libs", but you have to make
1752 sure that no program is using those libraries anymore.
1754 [8] In order to have a kernel that can run the 4.x binaries needed to
1755 do an installworld, you must include the COMPAT_FREEBSD4 option in
1756 your kernel. Failure to do so may leave you with a system that is
1757 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1758 required to run the 5.x binaries on more recent kernels. And so on
1759 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1761 Make sure that you merge any new devices from GENERIC since the
1762 last time you updated your kernel config file.
1764 [9] When checking out sources, you must include the -P flag to have
1765 cvs prune empty directories.
1767 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1768 "?=" instead of the "=" assignment operator, so that buildworld can
1769 override the CPUTYPE if it needs to.
1771 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1772 not on the command line, or in /etc/make.conf. buildworld will
1773 warn if it is improperly defined.
1776 This file contains a list, in reverse chronological order, of major
1777 breakages in tracking -current. It is not guaranteed to be a complete
1778 list of such breakages, and only contains entries since September 23, 2011.
1779 If you need to see UPDATING entries from before that date, you will need
1780 to fetch an UPDATING file from an older FreeBSD release.
1782 Copyright information:
1784 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1786 Redistribution, publication, translation and use, with or without
1787 modification, in full or in part, in any form or format of this
1788 document are permitted without further permission from the author.
1790 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1791 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1792 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1793 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1794 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1795 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1796 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1797 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1798 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1799 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1800 POSSIBILITY OF SUCH DAMAGE.
1802 Contact Warner Losh if you have any questions about your use of