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 20180314 p8 FreeBSD-SA-18:03.speculative_execution
21 Add mitigations for two classes of speculative execution vulnerabilities
24 20180307 p7 FreeBSD-SA-18:01.ipsec
26 FreeBSD-EN-18:01.tzdata
29 Fix ipsec validation and use-after-free. [SA-18:01.ipsec]
31 Fix multiple vulnerabilities in ntp. [SA-18:02.ntp]
33 Update timezone database information. [EN-18:01.tzdata]
35 Update file(1) to new version with security update. [EN-18:02.file]
37 20171209 p6 FreeBSD-SA-17:12.openssl
39 Fix multiple vulnerabilities of OpenSSL.
41 20171129 p5 FreeBSD-SA-17:11.openssl
43 Fix multiple vulnerabilities of OpenSSL.
45 20171115 p4 FreeBSD-SA-17:08.ptrace
46 FreeBSD-SA-17:10.kldstat
48 Fix ptrace(2) vulnerability. [SA-17:08.ptrace]
50 Fix kldstat(2) vulnerability. [SA-17:10.kldstat]
52 20171102 p3 FreeBSD-EN-17:09.tzdata
54 Update timezone database information. [EN-17:09]
56 20171017 p2 FreeBSD-SA-17:07.wpa
58 Fix WPA2 protocol vulnerability. [SA-17:07]
60 20170810 p1 FreeBSD-SA-17:06.openssh
64 Fix OpenSSH Denial of Service vulnerability. [SA-17:06]
66 Fix VNET kernel panic with asynchronous I/O. [EN-17:07]
68 Fix pf(4) housekeeping thread causes kernel panic. [EN-17:08]
74 arm64 builds now use the base system LLD 4.0.0 linker by default,
75 instead of requiring that the aarch64-binutils port or package be
76 installed. To continue using aarch64-binutils, set
77 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
80 The ctl.ko module no longer implements the iSCSI target frontend:
81 cfiscsi.ko does instead.
83 If building cfiscsi.ko as a kernel module, the module can be loaded
84 via one of the following methods:
85 - `cfiscsi_load="YES"` in loader.conf(5).
86 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
87 - ctladm(8)/ctld(8), when compiled with iSCSI support
88 (`WITH_ISCSI=yes` in src.conf(5))
90 Please see cfiscsi(4) for more details.
93 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
94 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
95 same source (previously, the dependency of mmcsd.ko on mmc.ko was
96 missing, but mmcsd.ko now will refuse to load if it is incompatible
100 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
101 use any explicitly assigned loopback address available in the jail
102 instead of using the first assigned address of the jail.
105 As of r316810 for ipfilter, keep frags is no longer assumed when
106 keep state is specified in a rule. r316810 aligns ipfilter with
107 documentation in man pages separating keep frags from keep state.
108 This allows keep state to specified without forcing keep frags
109 and allows keep frags to be specified independently of keep state.
110 To maintain previous behaviour, also specify keep frags with
111 keep state (as documented in ipf.conf.5).
114 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
115 Please see the 20141231 entry below for information about prerequisites
116 and upgrading, if you are not already using clang 3.5.0 or higher.
119 The code that provides support for ZFS .zfs/ directory functionality
120 has been reimplemented. It's not possible now to create a snapshot
121 by mkdir under .zfs/snapshot/. That should be the only user visible
125 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
126 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
127 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
128 and now NAT-T is supported by default. Security associations now use
129 the single namespace for SPI allocation, so if you use several manually
130 configured security associations with the same SPI, this configuration
134 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
135 Please see the 20141231 entry below for information about prerequisites
136 and upgrading, if you are not already using clang 3.5.0 or higher.
139 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
140 Please see the 20141231 entry below for information about prerequisites
141 and upgrading, if you are not already using clang 3.5.0 or higher.
144 The layout of the pmap structure has changed for powerpc to put the pmap
145 statistics at the front for all CPU variations. libkvm(3) and all tools
146 that link against it need to be recompiled.
149 isl(4) and cyapa(4) drivers now require a new driver,
150 chromebook_platform(4), to work properly on Chromebook-class hardware.
151 On other types of hardware the drivers may need to be configured using
152 device hints. Please see the corresponding manual pages for details.
155 Relocatable object files with the extension of .So have been renamed
156 to use an extension of .pico instead. The purpose of this change is
157 to avoid a name clash with shared libraries on case-insensitive file
158 systems. On those file systems, foo.So is the same file as foo.so.
161 The libc stub for the pipe(2) system call has been replaced with
162 a wrapper that calls the pipe2(2) system call and the pipe(2)
163 system call is now only implemented by the kernels that include
164 "options COMPAT_FREEBSD10" in their config file (this is the
165 default). Users should ensure that this option is enabled in
166 their kernel or upgrade userspace to r302092 before upgrading their
170 CAM will now strip leading spaces from SCSI disks' serial numbers.
171 This will effect users who create UFS filesystems on SCSI disks using
172 those disk's diskid device nodes. For example, if /etc/fstab
173 previously contained a line like
174 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
175 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
176 transforms like gmirror may also be affected. ZFS users should
180 The bitstring(3) API has been updated with new functionality and
181 improved performance. But it is binary-incompatible with the old API.
182 Objects built with the new headers may not be linked against objects
183 built with the old headers.
186 The brk and sbrk functions have been removed from libc on arm64.
187 Binutils from ports has been updated to not link to these
188 functions and should be updated to the latest version before
189 installing a new libc.
192 The armv6 port now defaults to hard float ABI. Limited support
193 for running both hardfloat and soft float on the same system
194 is available using the libraries installed with -DWITH_LIBSOFT.
195 This has only been tested as an upgrade path for installworld
196 and packages may fail or need manual intervention to run. New
197 packages will be needed.
199 To update an existing self-hosted armv6hf system, you must add
200 TARGET_ARCH=armv6 on the make command line for both the build
201 and the install steps.
204 Kernel modules compiled outside of a kernel build now default to
205 installing to /boot/modules instead of /boot/kernel. Many kernel
206 modules built this way (such as those in ports) already overrode
207 KMODDIR explicitly to install into /boot/modules. However,
208 manually building and installing a module from /sys/modules will
209 now install to /boot/modules instead of /boot/kernel.
212 The CAM I/O scheduler has been committed to the kernel. There should be
213 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
214 list of known rogues that claim support for this but actually corrupt
215 data is believed to be complete, be on the lookout for data
216 corruption. The known rogue list is believed to be complete:
218 o Crucial MX100, M550 drives with MU01 firmware.
219 o Micron M510 and M550 drives with MU01 firmware.
220 o Micron M500 prior to MU07 firmware
221 o Samsung 830, 840, and 850 all firmwares
222 o FCCT M500 all firmwares
224 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
225 with working NCQ TRIM. For Micron branded drives, see your sales rep for
226 updated firmware. Black listed drives will work correctly because these
227 drives work correctly so long as no NCQ TRIMs are sent to them. Given
228 this list is the same as found in Linux, it's believed there are no
229 other rogues in the market place. All other models from the above
232 To be safe, if you are at all concerned, you can quirk each of your
233 drives to prevent NCQ from being sent by setting:
234 kern.cam.ada.X.quirks="0x2"
235 in loader.conf. If the drive requires the 4k sector quirk, set the
239 The FAST_DEPEND build option has been removed and its functionality is
240 now the one true way. The old mkdep(1) style of 'make depend' has
241 been removed. See 20160311 for further details.
244 Resource range types have grown from unsigned long to uintmax_t. All
245 drivers, and anything using libdevinfo, need to be recompiled.
248 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
249 builds. It no longer runs mkdep(1) during 'make depend', and the
250 'make depend' stage can safely be skipped now as it is auto ran
251 when building 'make all' and will generate all SRCS and DPSRCS before
252 building anything else. Dependencies are gathered at compile time with
253 -MF flags kept in separate .depend files per object file. Users should
254 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
258 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
259 kernel modules. Therefore, if you load any kernel modules at boot time,
260 please install the boot loaders after you install the kernel, but before
264 make kernel KERNCONF=YOUR_KERNEL_HERE
265 make -C sys/boot install
266 <reboot in single user>
268 Then follow the usual steps, described in the General Notes section,
272 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
273 see the 20141231 entry below for information about prerequisites and
274 upgrading, if you are not already using clang 3.5.0 or higher.
277 The AIO subsystem is now a standard part of the kernel. The
278 VFS_AIO kernel option and aio.ko kernel module have been removed.
279 Due to stability concerns, asynchronous I/O requests are only
280 permitted on sockets and raw disks by default. To enable
281 asynchronous I/O requests on all file types, set the
282 vfs.aio.enable_unsafe sysctl to a non-zero value.
285 The ELF object manipulation tool objcopy is now provided by the
286 ELF Tool Chain project rather than by GNU binutils. It should be a
287 drop-in replacement, with the addition of arm64 support. The
288 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
289 to obtain the GNU version if necessary.
292 Building ZFS pools on top of zvols is prohibited by default. That
293 feature has never worked safely; it's always been prone to deadlocks.
294 Using a zvol as the backing store for a VM guest's virtual disk will
295 still work, even if the guest is using ZFS. Legacy behavior can be
296 restored by setting vfs.zfs.vol.recursive=1.
299 The NONE and HPN patches has been removed from OpenSSH. They are
300 still available in the security/openssh-portable port.
303 With the addition of ypldap(8), a new _ypldap user is now required
304 during installworld. "mergemaster -p" can be used to add the user
305 prior to installworld, as documented in the handbook.
308 The tftp loader (pxeboot) now uses the option root-path directive. As a
309 consequence it no longer looks for a pxeboot.4th file on the tftp
310 server. Instead it uses the regular /boot infrastructure as with the
314 The code to start recording plug and play data into the modules has
315 been committed. While the old tools will properly build a new kernel,
316 a number of warnings about "unknown metadata record 4" will be produced
317 for an older kldxref. To avoid such warnings, make sure to rebuild
318 the kernel toolchain (or world). Make sure that you have r292078 or
319 later when trying to build 292077 or later before rebuilding.
322 Debug data files are now built by default with 'make buildworld' and
323 installed with 'make installworld'. This facilitates debugging but
324 requires more disk space both during the build and for the installed
325 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
329 r291527 changed the internal interface between the nfsd.ko and
330 nfscommon.ko modules. As such, they must both be upgraded to-gether.
331 __FreeBSD_version has been bumped because of this.
334 Add support for unicode collation strings leads to a change of
335 order of files listed by ls(1) for example. To get back to the old
336 behaviour, set LC_COLLATE environment variable to "C".
338 Databases administrators will need to reindex their databases given
339 collation results will be different.
341 Due to a bug in install(1) it is recommended to remove the ancient
342 locales before running make installworld.
344 rm -rf /usr/share/locale/*
347 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
348 libcrypto.so.7 or libssl.so.7 must be recompiled.
351 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
352 Kernel modules isp_2400_multi and isp_2500_multi were removed and
353 should be replaced with isp_2400 and isp_2500 modules respectively.
356 The build previously allowed using 'make -n' to not recurse into
357 sub-directories while showing what commands would be executed, and
358 'make -n -n' to recursively show commands. Now 'make -n' will recurse
359 and 'make -N' will not.
362 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
363 and etcupdate will now use this file. A custom sendmail.cf is now
364 updated via this mechanism rather than via installworld. If you had
365 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
366 want to remove the exclusion or change it to "always install".
367 /etc/mail/sendmail.cf is now managed the same way regardless of
368 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
369 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
372 Compatibility shims for legacy ATA device names have been removed.
373 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
374 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
375 environment variables, /dev/ad* and /dev/ar* symbolic links.
378 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
379 Please see the 20141231 entry below for information about prerequisites
380 and upgrading, if you are not already using clang 3.5.0 or higher.
383 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
384 and renamed from .symbols to .debug. This reduces the size requirements
385 on the boot partition or file system and provides consistency with
386 userland debug files.
388 When using the supported kernel installation method the
389 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
390 as is done with /boot/kernel.
392 Developers wishing to maintain the historical behavior of installing
393 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
396 The wireless drivers had undergone changes that remove the 'parent
397 interface' from the ifconfig -l output. The rc.d network scripts
398 used to check presence of a parent interface in the list, so old
399 scripts would fail to start wireless networking. Thus, etcupdate(3)
400 or mergemaster(8) run is required after kernel update, to update your
401 rc.d scripts in /etc.
404 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
405 These configurations are now automatically interpreted as
406 'scrub fragment reassemble'.
409 Kernel-loadable modules for the random(4) device are back. To use
410 them, the kernel must have
413 options RANDOM_LOADABLE
415 kldload(8) can then be used to load random_fortuna.ko
416 or random_yarrow.ko. Please note that due to the indirect
417 function calls that the loadable modules need to provide,
418 the build-in variants will be slightly more efficient.
420 The random(4) kernel option RANDOM_DUMMY has been retired due to
421 unpopularity. It was not all that useful anyway.
424 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
425 Control over building the ELF Tool Chain tools is now provided by
426 the WITHOUT_TOOLCHAIN knob.
429 The polarity of Pulse Per Second (PPS) capture events with the
430 uart(4) driver has been corrected. Prior to this change the PPS
431 "assert" event corresponded to the trailing edge of a positive PPS
432 pulse and the "clear" event was the leading edge of the next pulse.
434 As the width of a PPS pulse in a typical GPS receiver is on the
435 order of 1 millisecond, most users will not notice any significant
436 difference with this change.
438 Anyone who has compensated for the historical polarity reversal by
439 configuring a negative offset equal to the pulse width will need to
440 remove that workaround.
443 The default group assigned to /dev/dri entries has been changed
444 from 'wheel' to 'video' with the id of '44'. If you want to have
445 access to the dri devices please add yourself to the video group
448 # pw groupmod video -m $USER
451 The menu.rc and loader.rc files will now be replaced during
452 upgrades. Please migrate local changes to menu.rc.local and
453 loader.rc.local instead.
456 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
457 strings and strip have been removed. The src.conf(5) knob
458 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
461 As ZFS requires more kernel stack pages than is the default on some
462 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
463 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
465 Please consider using 'options KSTACK_PAGES=X' where X is greater
466 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
469 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
470 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
471 default, i.e., they will not contain "::". For example, instead
472 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
473 to have a more specific match, such as different map entries for
474 IPv6:0:0 vs IPv6:0. This change requires that configuration
475 data (including maps, files, classes, custom ruleset, etc.) must
476 use the same format, so make certain such configuration data is
477 upgrading. As a very simple check search for patterns like
478 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
479 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
480 the cf option UseCompressedIPv6Addresses.
483 The default kernel entropy-processing algorithm is now
484 Fortuna, replacing Yarrow.
486 Assuming you have 'device random' in your kernel config
487 file, the configurations allow a kernel option to override
488 this default. You may choose *ONE* of:
490 options RANDOM_YARROW # Legacy /dev/random algorithm.
491 options RANDOM_DUMMY # Blocking-only driver.
493 If you have neither, you get Fortuna. For most people,
494 read no further, Fortuna will give a /dev/random that works
495 like it always used to, and the difference will be irrelevant.
497 If you remove 'device random', you get *NO* kernel-processed
498 entropy at all. This may be acceptable to folks building
499 embedded systems, but has complications. Carry on reading,
500 and it is assumed you know what you need.
502 *PLEASE* read random(4) and random(9) if you are in the
503 habit of tweaking kernel configs, and/or if you are a member
504 of the embedded community, wanting specific and not-usual
505 behaviour from your security subsystems.
507 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
508 random', you will NOT have a functioning /dev/random, and
509 many cryptographic features will not work, including SSH.
510 You may also find strange behaviour from the random(3) set
511 of library functions, in particular sranddev(3), srandomdev(3)
512 and arc4random(3). The reason for this is that the KERN_ARND
513 sysctl only returns entropy if it thinks it has some to
514 share, and with RANDOM_DUMMY or no 'device random' this
518 An additional fix for the issue described in the 20150614 sendmail
519 entry below has been been committed in revision 284717.
522 FreeBSD's old make (fmake) has been removed from the system. It is
523 available as the devel/fmake port or via pkg install fmake.
526 The fix for the issue described in the 20150614 sendmail entry
527 below has been been committed in revision 284436. The work
528 around described in that entry is no longer needed unless the
529 default setting is overridden by a confDH_PARAMETERS configuration
530 setting of '5' or pointing to a 512 bit DH parameter file.
533 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
534 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
535 and devel/kyua to version 0.20+ and adjust any calling code to work
536 with Kyuafile and kyua.
539 The import of openssl to address the FreeBSD-SA-15:10.openssl
540 security advisory includes a change which rejects handshakes
541 with DH parameters below 768 bits. sendmail releases prior
542 to 8.15.2 (not yet released), defaulted to a 512 bit
543 DH parameter setting for client connections. To work around
544 this interoperability, sendmail can be configured to use a
545 2048 bit DH parameter by:
547 1. Edit /etc/mail/`hostname`.mc
548 2. If a setting for confDH_PARAMETERS does not exist or
549 exists and is set to a string beginning with '5',
551 3. If a setting for confDH_PARAMETERS exists and is set to
552 a file path, create a new file with:
553 openssl dhparam -out /path/to/file 2048
554 4. Rebuild the .cf file:
555 cd /etc/mail/; make; make install
557 cd /etc/mail/; make restart
559 A sendmail patch is coming, at which time this file will be
563 Generation of legacy formatted entries have been disabled by default
564 in pwd_mkdb(8), as all base system consumers of the legacy formatted
565 entries were converted to use the new format by default when the new,
566 machine independent format have been added and supported since FreeBSD
569 Please see the pwd_mkdb(8) manual page for further details.
572 Clang and llvm have been upgraded to 3.6.1 release. Please see the
573 20141231 entry below for information about prerequisites and upgrading,
574 if you are not already using 3.5.0 or higher.
577 TI platform code switched to using vendor DTS files and this update
578 may break existing systems running on Beaglebone, Beaglebone Black,
581 - dtb files should be regenerated/reinstalled. Filenames are the
582 same but content is different now
583 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
584 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
585 addressing scheme is now pin 25 on /dev/gpioc3.
586 - Pandaboard: /etc/ttys should be updated, serial console device is
587 now /dev/ttyu2, not /dev/ttyu0
590 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
591 If you need the GNU extension from groff soelim(1), install groff
592 from package: pkg install groff, or via ports: textproc/groff.
595 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
596 defined in symlink(7); previously symlinks were silently ignored.
599 The const qualifier has been removed from iconv(3) to comply with
600 POSIX. The ports tree is aware of this from r384038 onwards.
603 Libraries specified by LIBADD in Makefiles must have a corresponding
604 DPADD_<lib> variable to ensure correct dependencies. This is now
605 enforced in src.libnames.mk.
608 From legacy ata(4) driver was removed support for SATA controllers
609 supported by more functional drivers ahci(4), siis(4) and mvs(4).
610 Kernel modules ataahci and ataadaptec were removed completely,
611 replaced by ahci and mvs modules respectively.
614 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
615 the 20141231 entry below for information about prerequisites and
616 upgrading, if you are not already using 3.5.0 or higher.
619 The 32-bit PowerPC kernel has been changed to a position-independent
620 executable. This can only be booted with a version of loader(8)
621 newer than January 31, 2015, so make sure to update both world and
622 kernel before rebooting.
625 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
626 but before r278950, the RNG was not seeded properly. Immediately
627 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
628 ssh keys or openssl keys) that were generated w/ a kernel from that
629 range. This does not affect programs that directly used /dev/random
630 or /dev/urandom. All userland uses of arc4random(3) are affected.
633 The autofs(4) ABI was changed in order to restore binary compatibility
634 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
638 The powerpc64 kernel has been changed to a position-independent
639 executable. This can only be booted with a new version of loader(8),
640 so make sure to update both world and kernel before rebooting.
643 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
644 only release, no new features have been added. Please see the 20141231
645 entry below for information about prerequisites and upgrading, if you
646 are not already using 3.5.0.
649 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
650 taken from the ELF Tool Chain project rather than GNU binutils. They
651 should be drop-in replacements, with the addition of arm64 support.
652 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
653 binutils tools, if necessary. See 20150805 for updated information.
656 The default Unbound configuration now enables remote control
657 using a local socket. Users who have already enabled the
658 local_unbound service should regenerate their configuration
659 by running "service local_unbound setup" as root.
662 The GNU texinfo and GNU info pages have been removed.
663 To be able to view GNU info pages please install texinfo from ports.
666 Clang, llvm and lldb have been upgraded to 3.5.0 release.
668 As of this release, a prerequisite for building clang, llvm and lldb is
669 a C++11 capable compiler and C++11 standard library. This means that to
670 be able to successfully build the cross-tools stage of buildworld, with
671 clang as the bootstrap compiler, your system compiler or cross compiler
672 should either be clang 3.3 or later, or gcc 4.8 or later, and your
673 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
676 On any standard FreeBSD 10.x or 11.x installation, where clang and
677 libc++ are on by default (that is, on x86 or arm), this should work out
680 On 9.x installations where clang is enabled by default, e.g. on x86 and
681 powerpc, libc++ will not be enabled by default, so libc++ should be
682 built (with clang) and installed first. If both clang and libc++ are
683 missing, build clang first, then use it to build libc++.
685 On 8.x and earlier installations, upgrade to 9.x first, and then follow
686 the instructions for 9.x above.
688 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
689 default, and do not build clang.
691 Many embedded systems are resource constrained, and will not be able to
692 build clang in a reasonable time, or in some cases at all. In those
693 cases, cross building bootable systems on amd64 is a workaround.
695 This new version of clang introduces a number of new warnings, of which
696 the following are most likely to appear:
700 This warns in two cases, for both C and C++:
701 * When the code is trying to take the absolute value of an unsigned
702 quantity, which is effectively a no-op, and almost never what was
703 intended. The code should be fixed, if at all possible. If you are
704 sure that the unsigned quantity can be safely cast to signed, without
705 loss of information or undefined behavior, you can add an explicit
706 cast, or disable the warning.
708 * When the code is trying to take an absolute value, but the called
709 abs() variant is for the wrong type, which can lead to truncation.
710 If you want to disable the warning instead of fixing the code, please
711 make sure that truncation will not occur, or it might lead to unwanted
714 -Wtautological-undefined-compare and
715 -Wundefined-bool-conversion
717 These warn when C++ code is trying to compare 'this' against NULL, while
718 'this' should never be NULL in well-defined C++ code. However, there is
719 some legacy (pre C++11) code out there, which actively abuses this
720 feature, which was less strictly defined in previous C++ versions.
722 Squid and openjdk do this, for example. The warning can be turned off
723 for C++98 and earlier, but compiling the code in C++11 mode might result
724 in unexpected behavior; for example, the parts of the program that are
725 unreachable could be optimized away.
728 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
729 kernel sources have been removed. The .h files remain, since some
730 utilities include them. This will need to be fixed later.
731 If "mount -t oldnfs ..." is attempted, it will fail.
732 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
733 the utilities will report errors.
736 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
737 directories to top level SUBDIR variable when their parent
738 directory is included in LOCAL_DIRS. Users with build systems with
739 such hierarchies and without SUBDIR entries in the parent
740 directory Makefiles should add them or add the directories to
744 faith(4) and faithd(8) have been removed from the base system. Faith
745 has been obsolete for a very long time.
748 vt(4), the new console driver, is enabled by default. It brings
749 support for Unicode and double-width characters, as well as
750 support for UEFI and integration with the KMS kernel video
753 You may need to update your console settings in /etc/rc.conf,
754 most probably the keymap. During boot, /etc/rc.d/syscons will
755 indicate what you need to do.
757 vt(4) still has issues and lacks some features compared to
758 syscons(4). See the wiki for up-to-date information:
759 https://wiki.freebsd.org/Newcons
761 If you want to keep using syscons(4), you can do so by adding
762 the following line to /boot/loader.conf:
766 pjdfstest has been integrated into kyua as an opt-in test suite.
767 Please see share/doc/pjdfstest/README for more details on how to
771 gperf has been removed from the base system for architectures
772 that use clang. Ports that require gperf will obtain it from the
776 pjdfstest has been moved from tools/regression/pjdfstest to
780 At svn r271982, The default linux compat kernel ABI has been adjusted
781 to 2.6.18 in support of the linux-c6 compat ports infrastructure
782 update. If you wish to continue using the linux-f10 compat ports,
783 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
784 encouraged to update their linux-compat packages to linux-c6 during
785 their next update cycle.
788 The ofwfb driver, used to provide a graphics console on PowerPC when
789 using vt(4), no longer allows mmap() of all physical memory. This
790 will prevent Xorg on PowerPC with some ATI graphics cards from
791 initializing properly unless x11-servers/xorg-server is updated to
795 The xdev targets have been converted to using TARGET and
796 TARGET_ARCH instead of XDEV and XDEV_ARCH.
799 The default unbound configuration has been modified to address
800 issues with reverse lookups on networks that use private
801 address ranges. If you use the local_unbound service, run
802 "service local_unbound setup" as root to regenerate your
803 configuration, then "service local_unbound reload" to load the
807 The GNU texinfo and GNU info pages are not built and installed
808 anymore, WITH_INFO knob has been added to allow to built and install
810 UPDATE: see 20150102 entry on texinfo's removal
813 The GNU readline library is now an INTERNALLIB - that is, it is
814 statically linked into consumers (GDB and variants) in the base
815 system, and the shared library is no longer installed. The
816 devel/readline port is available for third party software that
820 The Itanium architecture (ia64) has been removed from the list of
821 known architectures. This is the first step in the removal of the
825 Commit r268115 has added NFSv4.1 server support, merged from
826 projects/nfsv4.1-server. Since this includes changes to the
827 internal interfaces between the NFS related modules, a full
828 build of the kernel and modules will be necessary.
829 __FreeBSD_version has been bumped.
832 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
833 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
834 which differs from the behaviour controlled by this knob.)
837 Maximal length of the serial number in CTL was increased from 16 to
838 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
839 and ctld, need to be rebuilt to work with a new kernel.
842 The libatf-c and libatf-c++ major versions were downgraded to 0 and
843 1 respectively to match the upstream numbers. They were out of
844 sync because, when they were originally added to FreeBSD, the
845 upstream versions were not respected. These libraries are private
846 and not yet built by default, so renumbering them should be a
847 non-issue. However, unclean source trees will yield broken test
848 programs once the operator executes "make delete-old-libs" after a
851 Additionally, the atf-sh binary was made private by moving it into
852 /usr/libexec/. Already-built shell test programs will keep the
853 path to the old binary so they will break after "make delete-old"
856 If you are using WITH_TESTS=yes (not the default), wipe the object
857 tree and rebuild from scratch to prevent spurious test failures.
858 This is only needed once: the misnumbered libraries and misplaced
859 binaries have been added to OptionalObsoleteFiles.inc so they will
860 be removed during a clean upgrade.
863 Clang and llvm have been upgraded to 3.4.1 release.
866 We bogusly installed src.opts.mk in /usr/share/mk. This file should
867 be removed to avoid issues in the future (and has been added to
871 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
872 past, it affected all builds that used the bsd.*.mk files. The old
873 behavior was a bug, but people may have relied upon it. To get this
874 behavior back, you can .include /etc/src.conf from /etc/make.conf
875 (which is still global and isn't changed). This also changes the
876 behavior of incremental builds inside the tree of individual
877 directories. Set MAKESYSPATH to ".../share/mk" to do that.
878 Although this has survived make universe and some upgrade scenarios,
879 other upgrade scenarios may have broken. At least one form of
880 temporary breakage was fixed with MAKESYSPATH settings for buildworld
881 as well... In cases where MAKESYSPATH isn't working with this
882 setting, you'll need to set it to the full path to your tree.
884 One side effect of all this cleaning up is that bsd.compiler.mk
885 is no longer implicitly included by bsd.own.mk. If you wish to
886 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
890 The lindev device has been removed since /dev/full has been made a
891 standard device. __FreeBSD_version has been bumped.
894 The knob WITHOUT_VI was added to the base system, which controls
895 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
896 in order to reorder files share/termcap and didn't build ex(1) as a
897 build tool, so building/installing with WITH_VI is highly advised for
898 build hosts for older releases.
900 This issue has been fixed in stable/9 and stable/10 in r277022 and
901 r276991, respectively.
904 The YES_HESIOD knob has been removed. It has been obsolete for
905 a decade. Please move to using WITH_HESIOD instead or your builds
906 will silently lack HESIOD.
909 The uart(4) driver has been changed with respect to its handling
910 of the low-level console. Previously the uart(4) driver prevented
911 any process from changing the baudrate or the CLOCAL and HUPCL
912 control flags. By removing the restrictions, operators can make
913 changes to the serial console port without having to reboot.
914 However, when getty(8) is started on the serial device that is
915 associated with the low-level console, a misconfigured terminal
916 line in /etc/ttys will now have a real impact.
917 Before upgrading the kernel, make sure that /etc/ttys has the
918 serial console device configured as 3wire without baudrate to
919 preserve the previous behaviour. E.g:
920 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
923 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
924 to improve performance. To re-enable it, if needed, run rpcbind
925 with command line option -W.
928 Switched back to the GPL dtc compiler due to updates in the upstream
929 dts files not being supported by the BSDL dtc compiler. You will need
930 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
931 may result while building dtb files during a kernel build if you fail
932 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
935 Clang and llvm have been upgraded to 3.4 release.
938 The nve(4) driver has been removed. Please use the nfe(4) driver
939 for NVIDIA nForce MCP Ethernet adapters instead.
942 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
943 This could cause certain C++ applications using shared libraries built
944 against the previous version of libc++ to crash. The incompatibility
945 has now been fixed, but any C++ applications or shared libraries built
946 between r261283 and r261801 should be recompiled.
949 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
950 capability mode support. Please note that enabling the feature in
951 kernel is still highly recommended.
954 OpenSSH is now built with sandbox support, and will use sandbox as
955 the default privilege separation method. This requires Capsicum
956 capability mode support in kernel.
959 The libelf and libdwarf libraries have been updated to newer
960 versions from upstream. Shared library version numbers for
961 these two libraries were bumped. Any ports or binaries
962 requiring these two libraries should be recompiled.
963 __FreeBSD_version is bumped to 1100006.
966 If a Makefile in a tests/ directory was auto-generating a Kyuafile
967 instead of providing an explicit one, this would prevent such
968 Makefile from providing its own Kyuafile in the future during
969 NO_CLEAN builds. This has been fixed in the Makefiles but manual
970 intervention is needed to clean an objdir if you use NO_CLEAN:
971 # find /usr/obj -name Kyuafile | xargs rm -f
974 The behavior of gss_pseudo_random() for the krb5 mechanism
975 has changed, for applications requesting a longer random string
976 than produced by the underlying enctype's pseudo-random() function.
977 In particular, the random string produced from a session key of
978 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
979 be different at the 17th octet and later, after this change.
980 The counter used in the PRF+ construction is now encoded as a
981 big-endian integer in accordance with RFC 4402.
982 __FreeBSD_version is bumped to 1100004.
985 The WITHOUT_ATF build knob has been removed and its functionality
986 has been subsumed into the more generic WITHOUT_TESTS. If you were
987 using the former to disable the build of the ATF libraries, you
988 should change your settings to use the latter.
991 The default version of mtree is nmtree which is obtained from
992 NetBSD. The output is generally the same, but may vary
993 slightly. If you found you need identical output adding
994 "-F freebsd9" to the command line should do the trick. For the
995 time being, the old mtree is available as fmtree.
998 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
999 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1000 1.1.4_8 and verify bsdyml not linked in, before running "make
1002 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1004 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1007 The stable/10 branch has been created in subversion from head
1011 The rc.d/jail script has been updated to support jail(8)
1012 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1013 for per-jail configuration are automatically converted to
1014 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1015 This is transparently backward compatible. See below about some
1016 incompatibilities and rc.conf(5) manual page for more details.
1018 These variables are now deprecated in favor of jail(8) configuration
1019 file. One can use "rc.d/jail config <jname>" command to generate
1020 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1021 running the jail(8) utility. The default pathname of the
1022 configuration file is /etc/jail.conf and can be specified by
1023 using $jail_conf or $jail_<jname>_conf variables.
1025 Please note that jail_devfs_ruleset accepts an integer at
1026 this moment. Please consider to rewrite the ruleset name
1030 BIND has been removed from the base system. If all you need
1031 is a local resolver, simply enable and start the local_unbound
1032 service instead. Otherwise, several versions of BIND are
1033 available in the ports tree. The dns/bind99 port is one example.
1035 With this change, nslookup(1) and dig(1) are no longer in the base
1036 system. Users should instead use host(1) and drill(1) which are
1037 in the base system. Alternatively, nslookup and dig can
1038 be obtained by installing the dns/bind-tools port.
1041 With the addition of unbound(8), a new unbound user is now
1042 required during installworld. "mergemaster -p" can be used to
1043 add the user prior to installworld, as documented in the handbook.
1046 OpenSSH is now built with DNSSEC support, and will by default
1047 silently trust signed SSHFP records. This can be controlled with
1048 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1049 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1052 The GNU Compiler Collection and C++ standard library (libstdc++)
1053 are no longer built by default on platforms where clang is the system
1054 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1055 options in src.conf.
1058 The PROCDESC kernel option is now part of the GENERIC kernel
1059 configuration and is required for the rwhod(8) to work.
1060 If you are using custom kernel configuration, you should include
1064 The API and ABI related to the Capsicum framework was modified
1065 in backward incompatible way. The userland libraries and programs
1066 have to be recompiled to work with the new kernel. This includes the
1067 following libraries and programs, but the whole buildworld is
1068 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1069 kdump, procstat, rwho, rwhod, uniq.
1072 AES-NI intrinsic support has been added to gcc. The AES-NI module
1073 has been updated to use this support. A new gcc is required to build
1074 the aesni module on both i386 and amd64.
1077 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1078 Thus "device padlock_rng" and "device rdrand_rng" should be
1079 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1082 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1083 enables just the iconv* functionality and is now on by default.
1084 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1085 compatibility. Set WITHOUT_ICONV to build the old way.
1086 If you have been using WITH_ICONV before, you will very likely
1087 need to turn on WITH_LIBICONV_COMPAT.
1090 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1091 Illumos origin, including ZFS. If you have INVARIANTS in your
1092 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1094 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1095 locks if WITNESS option was set. Because that generated a lot of
1096 witness(9) reports and all of them were believed to be false
1097 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1098 can be used to achieve the previous behavior.
1101 Timer values in IPv6 data structures now use time_uptime instead
1102 of time_second. Although this is not a user-visible functional
1103 change, userland utilities which directly use them---ndp(8),
1104 rtadvd(8), and rtsold(8) in the base system---need to be updated
1105 to r253970 or later.
1108 find -delete can now delete the pathnames given as arguments,
1109 instead of only files found below them or if the pathname did
1110 not contain any slashes. Formerly, the following error message
1113 find: -delete: <path>: relative path potentially not safe
1115 Deleting the pathnames given as arguments can be prevented
1116 without error messages using -mindepth 1 or by changing
1117 directory and passing "." as argument to find. This works in the
1118 old as well as the new version of find.
1121 Behavior of devfs rules path matching has been changed.
1122 Pattern is now always matched against fully qualified devfs
1123 path and slash characters must be explicitly matched by
1124 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1125 subdirectories must be reviewed.
1128 The default ARM ABI has changed to the ARM EABI. The old ABI is
1129 incompatible with the ARM EABI and all programs and modules will
1130 need to be rebuilt to work with a new kernel.
1132 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1134 NOTE: Support for the old ABI will be removed in the future and
1135 users are advised to upgrade.
1138 pkg_install has been disconnected from the build if you really need it
1139 you should add WITH_PKGTOOLS in your src.conf(5).
1142 Most of network statistics structures were changed to be able
1143 keep 64-bits counters. Thus all tools, that work with networking
1144 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1147 Fix a bug that allowed a tracing process (e.g. gdb) to write
1148 to a memory-mapped file in the traced process's address space
1149 even if neither the traced process nor the tracing process had
1150 write access to that file.
1153 CVS has been removed from the base system. An exact copy
1154 of the code is available from the devel/cvs port.
1157 Some people report the following error after the switch to bmake:
1159 make: illegal option -- J
1160 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1162 *** [buildworld] Error code 2
1164 this likely due to an old instance of make in
1165 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1166 which src/Makefile will use that blindly, if it exists, so if
1167 you see the above error:
1169 rm -rf `make -V MAKEPATH`
1174 Use bmake by default.
1175 Whereas before one could choose to build with bmake via
1176 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1177 make. The goal is to remove these knobs for 10-RELEASE.
1179 It is worth noting that bmake (like gmake) treats the command
1180 line as the unit of failure, rather than statements within the
1181 command line. Thus '(cd some/where && dosomething)' is safer
1182 than 'cd some/where; dosomething'. The '()' allows consistent
1183 behavior in parallel build.
1186 Fix a bug that allows NFS clients to issue READDIR on files.
1189 The WITHOUT_IDEA option has been removed because
1190 the IDEA patent expired.
1193 The sysctl which controls TRIM support under ZFS has been renamed
1194 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1198 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1199 rather than creating it's own in the temporary directory in
1200 order allow access to bootstrapped versions of tools such as
1201 install and mtree. When upgrading from version of FreeBSD where
1202 the install command does not support -l, you will need to
1203 install a new mergemaster command if mergemaster -p is required.
1204 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1208 Legacy ATA stack, disabled and replaced by new CAM-based one since
1209 FreeBSD 9.0, completely removed from the sources. Kernel modules
1210 atadisk and atapi*, user-level tools atacontrol and burncd are
1211 removed. Kernel option `options ATA_CAM` is now permanently enabled
1215 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1216 and socketpair(2). Software, in particular Kerberos, may
1217 automatically detect and use these during building. The resulting
1218 binaries will not work on older kernels.
1221 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1222 information, see the respective 20130304 entry).
1225 Recent commits to callout(9) changed the size of struct callout,
1226 so the KBI is probably heavily disturbed. Also, some functions
1227 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1228 by macros. Every kernel module using it won't load, so rebuild
1231 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1232 but does not initialize by default (because of the new CTL_DISABLE
1233 option) to save memory. To re-enable it, remove the CTL_DISABLE
1234 option from the kernel config file or set kern.cam.ctl.disable=0
1235 in /boot/loader.conf.
1238 The ctl device has been disabled in GENERIC for i386 and amd64.
1239 This was done due to the extra memory being allocated at system
1240 initialisation time by the ctl driver which was only used if
1241 a CAM target device was created. This makes a FreeBSD system
1242 unusable on 128MB or less of RAM.
1245 A new compression method (lz4) has been merged to -HEAD. Please
1246 refer to zpool-features(7) for more information.
1248 Please refer to the "ZFS notes" section of this file for information
1249 on upgrading boot ZFS pools.
1252 A BSD-licensed patch(1) variant has been added and is installed
1253 as bsdpatch, being the GNU version the default patch.
1254 To inverse the logic and use the BSD-licensed one as default,
1255 while having the GNU version installed as gnupatch, rebuild
1256 and install world with the WITH_BSD_PATCH knob set.
1259 Due to the use of the new -l option to install(1) during build
1260 and install, you must take care not to directly set the INSTALL
1261 make variable in your /etc/make.conf, /etc/src.conf, or on the
1262 command line. If you wish to use the -C flag for all installs
1263 you may be able to add INSTALL+=-C to /etc/make.conf or
1267 The install(1) option -M has changed meaning and now takes an
1268 argument that is a file or path to append logs to. In the
1269 unlikely event that -M was the last option on the command line
1270 and the command line contained at least two files and a target
1271 directory the first file will have logs appended to it. The -M
1272 option served little practical purpose in the last decade so its
1273 use is expected to be extremely rare.
1276 After switching to Clang as the default compiler some users of ZFS
1277 on i386 systems started to experience stack overflow kernel panics.
1278 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1281 GEOM_LABEL now mangles label names read from file system metadata.
1282 Mangling affect labels containing spaces, non-printable characters,
1283 '%' or '"'. Device names in /etc/fstab and other places may need to
1287 By default, only the 10 most recent kernel dumps will be saved. To
1288 restore the previous behaviour (no limit on the number of kernel dumps
1289 stored in the dump directory) add the following line to /etc/rc.conf:
1294 With the addition of auditdistd(8), a new auditdistd user is now
1295 required during installworld. "mergemaster -p" can be used to
1296 add the user prior to installworld, as documented in the handbook.
1299 The sin6_scope_id member variable in struct sockaddr_in6 is now
1300 filled by the kernel before passing the structure to the userland via
1301 sysctl or routing socket. This means the KAME-specific embedded scope
1302 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1303 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1304 __FreeBSD_version is bumped to 1000025.
1307 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1308 This means that the world and kernel will be compiled with clang
1309 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1310 and /usr/bin/cpp. To disable this behavior and revert to building
1311 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1312 of current may need to bootstrap WITHOUT_CLANG first if the clang
1313 build fails (its compatibility window doesn't extend to the 9 stable
1317 The IPFIREWALL_FORWARD kernel option has been removed. Its
1318 functionality now turned on by default.
1321 The ZERO_COPY_SOCKET kernel option has been removed and
1322 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1323 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1324 mechanism which is not safe and may result in kernel crashes.
1325 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1326 driver supports disposeable external page sized mbuf storage.
1327 Proper replacements for both zero-copy mechanisms are under
1328 consideration and will eventually lead to complete removal
1329 of the two kernel options.
1332 The IPv4 network stack has been converted to network byte
1333 order. The following modules need to be recompiled together
1334 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1335 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1338 Support for non-MPSAFE filesystems was removed from VFS. The
1339 VFS_VERSION was bumped, all filesystem modules shall be
1343 All the non-MPSAFE filesystems have been disconnected from
1344 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1345 portalfs, smbfs, xfs.
1348 The interface cloning API and ABI has changed. The following
1349 modules need to be recompiled together with kernel:
1350 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1351 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1352 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1355 The sdhci driver was split in two parts: sdhci (generic SD Host
1356 Controller logic) and sdhci_pci (actual hardware driver).
1357 No kernel config modifications are required, but if you
1358 load sdhc as a module you must switch to sdhci_pci instead.
1361 Import the FUSE kernel and userland support into base system.
1364 The GNU sort(1) program has been removed since the BSD-licensed
1365 sort(1) has been the default for quite some time and no serious
1366 problems have been reported. The corresponding WITH_GNU_SORT
1370 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1371 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1375 The net80211(4) ABI has been changed to allow for improved driver
1376 PS-POLL and power-save support. All wireless drivers need to be
1377 recompiled to work with the new kernel.
1380 The random(4) support for the VIA hardware random number
1381 generator (`PADLOCK') is no longer enabled unconditionally.
1382 Add the padlock_rng device in the custom kernel config if
1383 needed. The GENERIC kernels on i386 and amd64 do include the
1384 device, so the change only affects the custom kernel
1388 The pf(4) packet filter ABI has been changed. pfctl(8) and
1389 snmp_pf module need to be recompiled to work with new kernel.
1392 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1393 to -HEAD. Pools that have empty_bpobj in active state can not be
1394 imported read-write with ZFS implementations that do not support
1395 this feature. For more information read the zpool-features(5)
1399 The sparc64 ZFS loader has been changed to no longer try to auto-
1400 detect ZFS providers based on diskN aliases but now requires these
1401 to be explicitly listed in the OFW boot-device environment variable.
1404 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1405 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1406 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1409 The following sysctls and tunables have been renamed for consistency
1410 with other variables:
1411 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1412 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1415 The sort utility has been replaced with BSD sort. For now, GNU sort
1416 is also available as "gnusort" or the default can be set back to
1417 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1418 installed as "bsdsort".
1421 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1422 Starting with this version the old system of ZFS pool versioning
1423 is superseded by "feature flags". This concept enables forward
1424 compatibility against certain future changes in functionality of ZFS
1425 pools. The first read-only compatible "feature flag" for ZFS pools
1426 is named "com.delphix:async_destroy". For more information
1427 read the new zpool-features(5) manual page.
1428 Please refer to the "ZFS notes" section of this file for information
1429 on upgrading boot ZFS pools.
1432 The malloc(3) implementation embedded in libc now uses sources imported
1433 as contrib/jemalloc. The most disruptive API change is to
1434 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1435 delete it prior to installworld, and optionally re-create it using the
1436 new format after rebooting. See malloc.conf(5) for details
1437 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1441 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1442 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1443 now spelled mips. This is to aid compatibility with third-party
1444 software that expects this naming scheme in uname(3). Little-endian
1445 settings are unchanged. If you are updating a big-endian mips64 machine
1446 from before this change, you may need to set MACHINE_ARCH=mips64 in
1447 your environment before the new build system will recognize your machine.
1450 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1454 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1455 nullfs(5) did not pass through all behaviours to the underlying layer,
1456 as a result if we bound to a socket on the lower layer we could connect
1457 only to the lower path; if we bound to the upper layer we could connect
1458 only to the upper path. The new behavior is one can connect to both the
1459 lower and the upper paths regardless what layer path one binds to.
1462 The getifaddrs upgrade path broken with 20111215 has been restored.
1463 If you have upgraded in between 20111215 and 20120209 you need to
1464 recompile libc again with your kernel. You still need to recompile
1465 world to be able to configure CARP but this restriction already
1466 comes from 20111215.
1469 The set_rcvar() function has been removed from /etc/rc.subr. All
1470 base and ports rc.d scripts have been updated, so if you have a
1471 port installed with a script in /usr/local/etc/rc.d you can either
1472 hand-edit the rcvar= line, or reinstall the port.
1474 An easy way to handle the mass-update of /etc/rc.d:
1475 rm /etc/rc.d/* && mergemaster -i
1478 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1479 on the current CPU and prevents other threads from running.
1480 This behavior can be reverted using the kern.stop_scheduler_on_panic
1482 The new behavior can be incompatible with kern.sync_on_panic.
1485 The carp(4) facility has been changed significantly. Configuration
1486 of the CARP protocol via ifconfig(8) has changed, as well as format
1487 of CARP events submitted to devd(8) has changed. See manual pages
1488 for more information. The arpbalance feature of carp(4) is currently
1489 not supported anymore.
1491 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1492 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1493 need to be recompiled.
1496 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1500 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1501 explicitely support non-MPSAFE filesystems.
1502 It is on by default for all supported platform at this present
1506 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1507 i386 and pc98 GENERIC kernel configuration files.
1510 sysinstall has been removed
1513 The stable/9 branch created in subversion. This corresponds to the
1514 RELENG_9 branch in CVS.
1520 Avoid using make -j when upgrading. While generally safe, there are
1521 sometimes problems using -j to upgrade. If your upgrade fails with
1522 -j, please try again without -j. From time to time in the past there
1523 have been problems using -j with buildworld and/or installworld. This
1524 is especially true when upgrading between "distant" versions (eg one
1525 that cross a major release boundary or several minor releases, or when
1526 several months have passed on the -current branch).
1528 Sometimes, obscure build problems are the result of environment
1529 poisoning. This can happen because the make utility reads its
1530 environment when searching for values for global variables. To run
1531 your build attempts in an "environmental clean room", prefix all make
1532 commands with 'env -i '. See the env(1) manual page for more details.
1534 When upgrading from one major version to another it is generally best
1535 to upgrade to the latest code in the currently installed branch first,
1536 then do an upgrade to the new branch. This is the best-tested upgrade
1537 path, and has the highest probability of being successful. Please try
1538 this approach before reporting problems with a major version upgrade.
1540 When upgrading a live system, having a root shell around before
1541 installing anything can help undo problems. Not having a root shell
1542 around can lead to problems if pam has changed too much from your
1543 starting point to allow continued authentication after the upgrade.
1545 This file should be read as a log of events. When a later event changes
1546 information of a prior event, the prior event should not be deleted.
1547 Instead, a pointer to the entry with the new information should be
1548 placed in the old entry. Readers of this file should also sanity check
1549 older entries before relying on them blindly. Authors of new entries
1550 should write them with this in mind.
1554 When upgrading the boot ZFS pool to a new version, always follow
1557 1.) recompile and reinstall the ZFS boot loader and boot block
1558 (this is part of "make buildworld" and "make installworld")
1560 2.) update the ZFS boot block on your boot drive
1562 The following example updates the ZFS boot block on the first
1563 partition (freebsd-boot) of a GPT partitioned drive ada0:
1564 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1566 Non-boot pools do not need these updates.
1570 If you are updating from a prior version of FreeBSD (even one just
1571 a few days old), you should follow this procedure. It is the most
1572 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1574 make kernel-toolchain
1575 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1576 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1578 To test a kernel once
1579 ---------------------
1580 If you just want to boot a kernel once (because you are not sure
1581 if it works, or if you want to boot a known bad kernel to provide
1582 debugging information) run
1583 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1584 nextboot -k testkernel
1586 To just build a kernel when you know that it won't mess you up
1587 --------------------------------------------------------------
1588 This assumes you are already running a CURRENT system. Replace
1589 ${arch} with the architecture of your machine (e.g. "i386",
1590 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1592 cd src/sys/${arch}/conf
1593 config KERNEL_NAME_HERE
1594 cd ../compile/KERNEL_NAME_HERE
1599 If this fails, go to the "To build a kernel" section.
1601 To rebuild everything and install it on the current system.
1602 -----------------------------------------------------------
1603 # Note: sometimes if you are running current you gotta do more than
1604 # is listed here if you are upgrading from a really old current.
1606 <make sure you have good level 0 dumps>
1608 make kernel KERNCONF=YOUR_KERNEL_HERE
1610 <reboot in single user> [3]
1617 To cross-install current onto a separate partition
1618 --------------------------------------------------
1619 # In this approach we use a separate partition to hold
1620 # current's root, 'usr', and 'var' directories. A partition
1621 # holding "/", "/usr" and "/var" should be about 2GB in
1624 <make sure you have good level 0 dumps>
1627 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1628 <maybe newfs current's root partition>
1629 <mount current's root partition on directory ${CURRENT_ROOT}>
1630 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1631 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1632 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1633 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1634 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1635 <reboot into current>
1636 <do a "native" rebuild/install as described in the previous section>
1637 <maybe install compatibility libraries from ports/misc/compat*>
1641 To upgrade in-place from stable to current
1642 ----------------------------------------------
1643 <make sure you have good level 0 dumps>
1645 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1647 <reboot in single user> [3]
1654 Make sure that you've read the UPDATING file to understand the
1655 tweaks to various things you need. At this point in the life
1656 cycle of current, things change often and you are on your own
1657 to cope. The defaults can also change, so please read ALL of
1658 the UPDATING entries.
1660 Also, if you are tracking -current, you must be subscribed to
1661 freebsd-current@freebsd.org. Make sure that before you update
1662 your sources that you have read and understood all the recent
1663 messages there. If in doubt, please track -stable which has
1664 much fewer pitfalls.
1666 [1] If you have third party modules, such as vmware, you
1667 should disable them at this point so they don't crash your
1670 [3] From the bootblocks, boot -s, and then do
1675 adjkerntz -i # if CMOS is wall time
1676 Also, when doing a major release upgrade, it is required that
1677 you boot into single user mode to do the installworld.
1679 [4] Note: This step is non-optional. Failure to do this step
1680 can result in a significant reduction in the functionality of the
1681 system. Attempting to do it by hand is not recommended and those
1682 that pursue this avenue should read this file carefully, as well
1683 as the archives of freebsd-current and freebsd-hackers mailing lists
1684 for potential gotchas. The -U option is also useful to consider.
1685 See mergemaster(8) for more information.
1687 [5] Usually this step is a noop. However, from time to time
1688 you may need to do this if you get unknown user in the following
1689 step. It never hurts to do it all the time. You may need to
1690 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1691 install) after the buildworld before this step if you last updated
1692 from current before 20130425 or from -stable before 20130430.
1694 [6] This only deletes old files and directories. Old libraries
1695 can be deleted by "make delete-old-libs", but you have to make
1696 sure that no program is using those libraries anymore.
1698 [8] In order to have a kernel that can run the 4.x binaries needed to
1699 do an installworld, you must include the COMPAT_FREEBSD4 option in
1700 your kernel. Failure to do so may leave you with a system that is
1701 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1702 required to run the 5.x binaries on more recent kernels. And so on
1703 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1705 Make sure that you merge any new devices from GENERIC since the
1706 last time you updated your kernel config file.
1708 [9] When checking out sources, you must include the -P flag to have
1709 cvs prune empty directories.
1711 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1712 "?=" instead of the "=" assignment operator, so that buildworld can
1713 override the CPUTYPE if it needs to.
1715 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1716 not on the command line, or in /etc/make.conf. buildworld will
1717 warn if it is improperly defined.
1720 This file contains a list, in reverse chronological order, of major
1721 breakages in tracking -current. It is not guaranteed to be a complete
1722 list of such breakages, and only contains entries since September 23, 2011.
1723 If you need to see UPDATING entries from before that date, you will need
1724 to fetch an UPDATING file from an older FreeBSD release.
1726 Copyright information:
1728 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1730 Redistribution, publication, translation and use, with or without
1731 modification, in full or in part, in any form or format of this
1732 document are permitted without further permission from the author.
1734 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1735 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1736 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1737 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1738 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1739 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1740 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1741 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1742 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1743 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1744 POSSIBILITY OF SUCH DAMAGE.
1746 Contact Warner Losh if you have any questions about your use of