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 20171129 p5 FreeBSD-SA-17:11.openssl
21 Fix multiple vulnerabilities of OpenSSL.
23 20171115 p4 FreeBSD-SA-17:08.ptrace
24 FreeBSD-SA-17:10.kldstat
26 Fix ptrace(2) vulnerability. [SA-17:08.ptrace]
28 Fix kldstat(2) vulnerability. [SA-17:10.kldstat]
30 20171102 p3 FreeBSD-EN-17:09.tzdata
32 Update timezone database information. [EN-17:09]
34 20171017 p2 FreeBSD-SA-17:07.wpa
36 Fix WPA2 protocol vulnerability. [SA-17:07]
38 20170810 p1 FreeBSD-SA-17:06.openssh
42 Fix OpenSSH Denial of Service vulnerability. [SA-17:06]
44 Fix VNET kernel panic with asynchronous I/O. [EN-17:07]
46 Fix pf(4) housekeeping thread causes kernel panic. [EN-17:08]
52 arm64 builds now use the base system LLD 4.0.0 linker by default,
53 instead of requiring that the aarch64-binutils port or package be
54 installed. To continue using aarch64-binutils, set
55 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
58 The ctl.ko module no longer implements the iSCSI target frontend:
59 cfiscsi.ko does instead.
61 If building cfiscsi.ko as a kernel module, the module can be loaded
62 via one of the following methods:
63 - `cfiscsi_load="YES"` in loader.conf(5).
64 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
65 - ctladm(8)/ctld(8), when compiled with iSCSI support
66 (`WITH_ISCSI=yes` in src.conf(5))
68 Please see cfiscsi(4) for more details.
71 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
72 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
73 same source (previously, the dependency of mmcsd.ko on mmc.ko was
74 missing, but mmcsd.ko now will refuse to load if it is incompatible
78 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
79 use any explicitly assigned loopback address available in the jail
80 instead of using the first assigned address of the jail.
83 As of r316810 for ipfilter, keep frags is no longer assumed when
84 keep state is specified in a rule. r316810 aligns ipfilter with
85 documentation in man pages separating keep frags from keep state.
86 This allows keep state to specified without forcing keep frags
87 and allows keep frags to be specified independently of keep state.
88 To maintain previous behaviour, also specify keep frags with
89 keep state (as documented in ipf.conf.5).
92 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
93 Please see the 20141231 entry below for information about prerequisites
94 and upgrading, if you are not already using clang 3.5.0 or higher.
97 The code that provides support for ZFS .zfs/ directory functionality
98 has been reimplemented. It's not possible now to create a snapshot
99 by mkdir under .zfs/snapshot/. That should be the only user visible
103 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
104 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
105 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
106 and now NAT-T is supported by default. Security associations now use
107 the single namespace for SPI allocation, so if you use several manually
108 configured security associations with the same SPI, this configuration
112 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
113 Please see the 20141231 entry below for information about prerequisites
114 and upgrading, if you are not already using clang 3.5.0 or higher.
117 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
118 Please see the 20141231 entry below for information about prerequisites
119 and upgrading, if you are not already using clang 3.5.0 or higher.
122 The layout of the pmap structure has changed for powerpc to put the pmap
123 statistics at the front for all CPU variations. libkvm(3) and all tools
124 that link against it need to be recompiled.
127 isl(4) and cyapa(4) drivers now require a new driver,
128 chromebook_platform(4), to work properly on Chromebook-class hardware.
129 On other types of hardware the drivers may need to be configured using
130 device hints. Please see the corresponding manual pages for details.
133 Relocatable object files with the extension of .So have been renamed
134 to use an extension of .pico instead. The purpose of this change is
135 to avoid a name clash with shared libraries on case-insensitive file
136 systems. On those file systems, foo.So is the same file as foo.so.
139 The libc stub for the pipe(2) system call has been replaced with
140 a wrapper that calls the pipe2(2) system call and the pipe(2)
141 system call is now only implemented by the kernels that include
142 "options COMPAT_FREEBSD10" in their config file (this is the
143 default). Users should ensure that this option is enabled in
144 their kernel or upgrade userspace to r302092 before upgrading their
148 CAM will now strip leading spaces from SCSI disks' serial numbers.
149 This will effect users who create UFS filesystems on SCSI disks using
150 those disk's diskid device nodes. For example, if /etc/fstab
151 previously contained a line like
152 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
153 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
154 transforms like gmirror may also be affected. ZFS users should
158 The bitstring(3) API has been updated with new functionality and
159 improved performance. But it is binary-incompatible with the old API.
160 Objects built with the new headers may not be linked against objects
161 built with the old headers.
164 The brk and sbrk functions have been removed from libc on arm64.
165 Binutils from ports has been updated to not link to these
166 functions and should be updated to the latest version before
167 installing a new libc.
170 The armv6 port now defaults to hard float ABI. Limited support
171 for running both hardfloat and soft float on the same system
172 is available using the libraries installed with -DWITH_LIBSOFT.
173 This has only been tested as an upgrade path for installworld
174 and packages may fail or need manual intervention to run. New
175 packages will be needed.
177 To update an existing self-hosted armv6hf system, you must add
178 TARGET_ARCH=armv6 on the make command line for both the build
179 and the install steps.
182 Kernel modules compiled outside of a kernel build now default to
183 installing to /boot/modules instead of /boot/kernel. Many kernel
184 modules built this way (such as those in ports) already overrode
185 KMODDIR explicitly to install into /boot/modules. However,
186 manually building and installing a module from /sys/modules will
187 now install to /boot/modules instead of /boot/kernel.
190 The CAM I/O scheduler has been committed to the kernel. There should be
191 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
192 list of known rogues that claim support for this but actually corrupt
193 data is believed to be complete, be on the lookout for data
194 corruption. The known rogue list is believed to be complete:
196 o Crucial MX100, M550 drives with MU01 firmware.
197 o Micron M510 and M550 drives with MU01 firmware.
198 o Micron M500 prior to MU07 firmware
199 o Samsung 830, 840, and 850 all firmwares
200 o FCCT M500 all firmwares
202 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
203 with working NCQ TRIM. For Micron branded drives, see your sales rep for
204 updated firmware. Black listed drives will work correctly because these
205 drives work correctly so long as no NCQ TRIMs are sent to them. Given
206 this list is the same as found in Linux, it's believed there are no
207 other rogues in the market place. All other models from the above
210 To be safe, if you are at all concerned, you can quirk each of your
211 drives to prevent NCQ from being sent by setting:
212 kern.cam.ada.X.quirks="0x2"
213 in loader.conf. If the drive requires the 4k sector quirk, set the
217 The FAST_DEPEND build option has been removed and its functionality is
218 now the one true way. The old mkdep(1) style of 'make depend' has
219 been removed. See 20160311 for further details.
222 Resource range types have grown from unsigned long to uintmax_t. All
223 drivers, and anything using libdevinfo, need to be recompiled.
226 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
227 builds. It no longer runs mkdep(1) during 'make depend', and the
228 'make depend' stage can safely be skipped now as it is auto ran
229 when building 'make all' and will generate all SRCS and DPSRCS before
230 building anything else. Dependencies are gathered at compile time with
231 -MF flags kept in separate .depend files per object file. Users should
232 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
236 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
237 kernel modules. Therefore, if you load any kernel modules at boot time,
238 please install the boot loaders after you install the kernel, but before
242 make kernel KERNCONF=YOUR_KERNEL_HERE
243 make -C sys/boot install
244 <reboot in single user>
246 Then follow the usual steps, described in the General Notes section,
250 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
251 see the 20141231 entry below for information about prerequisites and
252 upgrading, if you are not already using clang 3.5.0 or higher.
255 The AIO subsystem is now a standard part of the kernel. The
256 VFS_AIO kernel option and aio.ko kernel module have been removed.
257 Due to stability concerns, asynchronous I/O requests are only
258 permitted on sockets and raw disks by default. To enable
259 asynchronous I/O requests on all file types, set the
260 vfs.aio.enable_unsafe sysctl to a non-zero value.
263 The ELF object manipulation tool objcopy is now provided by the
264 ELF Tool Chain project rather than by GNU binutils. It should be a
265 drop-in replacement, with the addition of arm64 support. The
266 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
267 to obtain the GNU version if necessary.
270 Building ZFS pools on top of zvols is prohibited by default. That
271 feature has never worked safely; it's always been prone to deadlocks.
272 Using a zvol as the backing store for a VM guest's virtual disk will
273 still work, even if the guest is using ZFS. Legacy behavior can be
274 restored by setting vfs.zfs.vol.recursive=1.
277 The NONE and HPN patches has been removed from OpenSSH. They are
278 still available in the security/openssh-portable port.
281 With the addition of ypldap(8), a new _ypldap user is now required
282 during installworld. "mergemaster -p" can be used to add the user
283 prior to installworld, as documented in the handbook.
286 The tftp loader (pxeboot) now uses the option root-path directive. As a
287 consequence it no longer looks for a pxeboot.4th file on the tftp
288 server. Instead it uses the regular /boot infrastructure as with the
292 The code to start recording plug and play data into the modules has
293 been committed. While the old tools will properly build a new kernel,
294 a number of warnings about "unknown metadata record 4" will be produced
295 for an older kldxref. To avoid such warnings, make sure to rebuild
296 the kernel toolchain (or world). Make sure that you have r292078 or
297 later when trying to build 292077 or later before rebuilding.
300 Debug data files are now built by default with 'make buildworld' and
301 installed with 'make installworld'. This facilitates debugging but
302 requires more disk space both during the build and for the installed
303 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
307 r291527 changed the internal interface between the nfsd.ko and
308 nfscommon.ko modules. As such, they must both be upgraded to-gether.
309 __FreeBSD_version has been bumped because of this.
312 Add support for unicode collation strings leads to a change of
313 order of files listed by ls(1) for example. To get back to the old
314 behaviour, set LC_COLLATE environment variable to "C".
316 Databases administrators will need to reindex their databases given
317 collation results will be different.
319 Due to a bug in install(1) it is recommended to remove the ancient
320 locales before running make installworld.
322 rm -rf /usr/share/locale/*
325 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
326 libcrypto.so.7 or libssl.so.7 must be recompiled.
329 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
330 Kernel modules isp_2400_multi and isp_2500_multi were removed and
331 should be replaced with isp_2400 and isp_2500 modules respectively.
334 The build previously allowed using 'make -n' to not recurse into
335 sub-directories while showing what commands would be executed, and
336 'make -n -n' to recursively show commands. Now 'make -n' will recurse
337 and 'make -N' will not.
340 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
341 and etcupdate will now use this file. A custom sendmail.cf is now
342 updated via this mechanism rather than via installworld. If you had
343 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
344 want to remove the exclusion or change it to "always install".
345 /etc/mail/sendmail.cf is now managed the same way regardless of
346 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
347 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
350 Compatibility shims for legacy ATA device names have been removed.
351 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
352 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
353 environment variables, /dev/ad* and /dev/ar* symbolic links.
356 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
357 Please see the 20141231 entry below for information about prerequisites
358 and upgrading, if you are not already using clang 3.5.0 or higher.
361 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
362 and renamed from .symbols to .debug. This reduces the size requirements
363 on the boot partition or file system and provides consistency with
364 userland debug files.
366 When using the supported kernel installation method the
367 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
368 as is done with /boot/kernel.
370 Developers wishing to maintain the historical behavior of installing
371 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
374 The wireless drivers had undergone changes that remove the 'parent
375 interface' from the ifconfig -l output. The rc.d network scripts
376 used to check presence of a parent interface in the list, so old
377 scripts would fail to start wireless networking. Thus, etcupdate(3)
378 or mergemaster(8) run is required after kernel update, to update your
379 rc.d scripts in /etc.
382 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
383 These configurations are now automatically interpreted as
384 'scrub fragment reassemble'.
387 Kernel-loadable modules for the random(4) device are back. To use
388 them, the kernel must have
391 options RANDOM_LOADABLE
393 kldload(8) can then be used to load random_fortuna.ko
394 or random_yarrow.ko. Please note that due to the indirect
395 function calls that the loadable modules need to provide,
396 the build-in variants will be slightly more efficient.
398 The random(4) kernel option RANDOM_DUMMY has been retired due to
399 unpopularity. It was not all that useful anyway.
402 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
403 Control over building the ELF Tool Chain tools is now provided by
404 the WITHOUT_TOOLCHAIN knob.
407 The polarity of Pulse Per Second (PPS) capture events with the
408 uart(4) driver has been corrected. Prior to this change the PPS
409 "assert" event corresponded to the trailing edge of a positive PPS
410 pulse and the "clear" event was the leading edge of the next pulse.
412 As the width of a PPS pulse in a typical GPS receiver is on the
413 order of 1 millisecond, most users will not notice any significant
414 difference with this change.
416 Anyone who has compensated for the historical polarity reversal by
417 configuring a negative offset equal to the pulse width will need to
418 remove that workaround.
421 The default group assigned to /dev/dri entries has been changed
422 from 'wheel' to 'video' with the id of '44'. If you want to have
423 access to the dri devices please add yourself to the video group
426 # pw groupmod video -m $USER
429 The menu.rc and loader.rc files will now be replaced during
430 upgrades. Please migrate local changes to menu.rc.local and
431 loader.rc.local instead.
434 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
435 strings and strip have been removed. The src.conf(5) knob
436 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
439 As ZFS requires more kernel stack pages than is the default on some
440 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
441 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
443 Please consider using 'options KSTACK_PAGES=X' where X is greater
444 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
447 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
448 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
449 default, i.e., they will not contain "::". For example, instead
450 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
451 to have a more specific match, such as different map entries for
452 IPv6:0:0 vs IPv6:0. This change requires that configuration
453 data (including maps, files, classes, custom ruleset, etc.) must
454 use the same format, so make certain such configuration data is
455 upgrading. As a very simple check search for patterns like
456 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
457 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
458 the cf option UseCompressedIPv6Addresses.
461 The default kernel entropy-processing algorithm is now
462 Fortuna, replacing Yarrow.
464 Assuming you have 'device random' in your kernel config
465 file, the configurations allow a kernel option to override
466 this default. You may choose *ONE* of:
468 options RANDOM_YARROW # Legacy /dev/random algorithm.
469 options RANDOM_DUMMY # Blocking-only driver.
471 If you have neither, you get Fortuna. For most people,
472 read no further, Fortuna will give a /dev/random that works
473 like it always used to, and the difference will be irrelevant.
475 If you remove 'device random', you get *NO* kernel-processed
476 entropy at all. This may be acceptable to folks building
477 embedded systems, but has complications. Carry on reading,
478 and it is assumed you know what you need.
480 *PLEASE* read random(4) and random(9) if you are in the
481 habit of tweaking kernel configs, and/or if you are a member
482 of the embedded community, wanting specific and not-usual
483 behaviour from your security subsystems.
485 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
486 random', you will NOT have a functioning /dev/random, and
487 many cryptographic features will not work, including SSH.
488 You may also find strange behaviour from the random(3) set
489 of library functions, in particular sranddev(3), srandomdev(3)
490 and arc4random(3). The reason for this is that the KERN_ARND
491 sysctl only returns entropy if it thinks it has some to
492 share, and with RANDOM_DUMMY or no 'device random' this
496 An additional fix for the issue described in the 20150614 sendmail
497 entry below has been been committed in revision 284717.
500 FreeBSD's old make (fmake) has been removed from the system. It is
501 available as the devel/fmake port or via pkg install fmake.
504 The fix for the issue described in the 20150614 sendmail entry
505 below has been been committed in revision 284436. The work
506 around described in that entry is no longer needed unless the
507 default setting is overridden by a confDH_PARAMETERS configuration
508 setting of '5' or pointing to a 512 bit DH parameter file.
511 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
512 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
513 and devel/kyua to version 0.20+ and adjust any calling code to work
514 with Kyuafile and kyua.
517 The import of openssl to address the FreeBSD-SA-15:10.openssl
518 security advisory includes a change which rejects handshakes
519 with DH parameters below 768 bits. sendmail releases prior
520 to 8.15.2 (not yet released), defaulted to a 512 bit
521 DH parameter setting for client connections. To work around
522 this interoperability, sendmail can be configured to use a
523 2048 bit DH parameter by:
525 1. Edit /etc/mail/`hostname`.mc
526 2. If a setting for confDH_PARAMETERS does not exist or
527 exists and is set to a string beginning with '5',
529 3. If a setting for confDH_PARAMETERS exists and is set to
530 a file path, create a new file with:
531 openssl dhparam -out /path/to/file 2048
532 4. Rebuild the .cf file:
533 cd /etc/mail/; make; make install
535 cd /etc/mail/; make restart
537 A sendmail patch is coming, at which time this file will be
541 Generation of legacy formatted entries have been disabled by default
542 in pwd_mkdb(8), as all base system consumers of the legacy formatted
543 entries were converted to use the new format by default when the new,
544 machine independent format have been added and supported since FreeBSD
547 Please see the pwd_mkdb(8) manual page for further details.
550 Clang and llvm have been upgraded to 3.6.1 release. Please see the
551 20141231 entry below for information about prerequisites and upgrading,
552 if you are not already using 3.5.0 or higher.
555 TI platform code switched to using vendor DTS files and this update
556 may break existing systems running on Beaglebone, Beaglebone Black,
559 - dtb files should be regenerated/reinstalled. Filenames are the
560 same but content is different now
561 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
562 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
563 addressing scheme is now pin 25 on /dev/gpioc3.
564 - Pandaboard: /etc/ttys should be updated, serial console device is
565 now /dev/ttyu2, not /dev/ttyu0
568 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
569 If you need the GNU extension from groff soelim(1), install groff
570 from package: pkg install groff, or via ports: textproc/groff.
573 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
574 defined in symlink(7); previously symlinks were silently ignored.
577 The const qualifier has been removed from iconv(3) to comply with
578 POSIX. The ports tree is aware of this from r384038 onwards.
581 Libraries specified by LIBADD in Makefiles must have a corresponding
582 DPADD_<lib> variable to ensure correct dependencies. This is now
583 enforced in src.libnames.mk.
586 From legacy ata(4) driver was removed support for SATA controllers
587 supported by more functional drivers ahci(4), siis(4) and mvs(4).
588 Kernel modules ataahci and ataadaptec were removed completely,
589 replaced by ahci and mvs modules respectively.
592 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
593 the 20141231 entry below for information about prerequisites and
594 upgrading, if you are not already using 3.5.0 or higher.
597 The 32-bit PowerPC kernel has been changed to a position-independent
598 executable. This can only be booted with a version of loader(8)
599 newer than January 31, 2015, so make sure to update both world and
600 kernel before rebooting.
603 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
604 but before r278950, the RNG was not seeded properly. Immediately
605 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
606 ssh keys or openssl keys) that were generated w/ a kernel from that
607 range. This does not affect programs that directly used /dev/random
608 or /dev/urandom. All userland uses of arc4random(3) are affected.
611 The autofs(4) ABI was changed in order to restore binary compatibility
612 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
616 The powerpc64 kernel has been changed to a position-independent
617 executable. This can only be booted with a new version of loader(8),
618 so make sure to update both world and kernel before rebooting.
621 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
622 only release, no new features have been added. Please see the 20141231
623 entry below for information about prerequisites and upgrading, if you
624 are not already using 3.5.0.
627 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
628 taken from the ELF Tool Chain project rather than GNU binutils. They
629 should be drop-in replacements, with the addition of arm64 support.
630 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
631 binutils tools, if necessary. See 20150805 for updated information.
634 The default Unbound configuration now enables remote control
635 using a local socket. Users who have already enabled the
636 local_unbound service should regenerate their configuration
637 by running "service local_unbound setup" as root.
640 The GNU texinfo and GNU info pages have been removed.
641 To be able to view GNU info pages please install texinfo from ports.
644 Clang, llvm and lldb have been upgraded to 3.5.0 release.
646 As of this release, a prerequisite for building clang, llvm and lldb is
647 a C++11 capable compiler and C++11 standard library. This means that to
648 be able to successfully build the cross-tools stage of buildworld, with
649 clang as the bootstrap compiler, your system compiler or cross compiler
650 should either be clang 3.3 or later, or gcc 4.8 or later, and your
651 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
654 On any standard FreeBSD 10.x or 11.x installation, where clang and
655 libc++ are on by default (that is, on x86 or arm), this should work out
658 On 9.x installations where clang is enabled by default, e.g. on x86 and
659 powerpc, libc++ will not be enabled by default, so libc++ should be
660 built (with clang) and installed first. If both clang and libc++ are
661 missing, build clang first, then use it to build libc++.
663 On 8.x and earlier installations, upgrade to 9.x first, and then follow
664 the instructions for 9.x above.
666 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
667 default, and do not build clang.
669 Many embedded systems are resource constrained, and will not be able to
670 build clang in a reasonable time, or in some cases at all. In those
671 cases, cross building bootable systems on amd64 is a workaround.
673 This new version of clang introduces a number of new warnings, of which
674 the following are most likely to appear:
678 This warns in two cases, for both C and C++:
679 * When the code is trying to take the absolute value of an unsigned
680 quantity, which is effectively a no-op, and almost never what was
681 intended. The code should be fixed, if at all possible. If you are
682 sure that the unsigned quantity can be safely cast to signed, without
683 loss of information or undefined behavior, you can add an explicit
684 cast, or disable the warning.
686 * When the code is trying to take an absolute value, but the called
687 abs() variant is for the wrong type, which can lead to truncation.
688 If you want to disable the warning instead of fixing the code, please
689 make sure that truncation will not occur, or it might lead to unwanted
692 -Wtautological-undefined-compare and
693 -Wundefined-bool-conversion
695 These warn when C++ code is trying to compare 'this' against NULL, while
696 'this' should never be NULL in well-defined C++ code. However, there is
697 some legacy (pre C++11) code out there, which actively abuses this
698 feature, which was less strictly defined in previous C++ versions.
700 Squid and openjdk do this, for example. The warning can be turned off
701 for C++98 and earlier, but compiling the code in C++11 mode might result
702 in unexpected behavior; for example, the parts of the program that are
703 unreachable could be optimized away.
706 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
707 kernel sources have been removed. The .h files remain, since some
708 utilities include them. This will need to be fixed later.
709 If "mount -t oldnfs ..." is attempted, it will fail.
710 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
711 the utilities will report errors.
714 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
715 directories to top level SUBDIR variable when their parent
716 directory is included in LOCAL_DIRS. Users with build systems with
717 such hierarchies and without SUBDIR entries in the parent
718 directory Makefiles should add them or add the directories to
722 faith(4) and faithd(8) have been removed from the base system. Faith
723 has been obsolete for a very long time.
726 vt(4), the new console driver, is enabled by default. It brings
727 support for Unicode and double-width characters, as well as
728 support for UEFI and integration with the KMS kernel video
731 You may need to update your console settings in /etc/rc.conf,
732 most probably the keymap. During boot, /etc/rc.d/syscons will
733 indicate what you need to do.
735 vt(4) still has issues and lacks some features compared to
736 syscons(4). See the wiki for up-to-date information:
737 https://wiki.freebsd.org/Newcons
739 If you want to keep using syscons(4), you can do so by adding
740 the following line to /boot/loader.conf:
744 pjdfstest has been integrated into kyua as an opt-in test suite.
745 Please see share/doc/pjdfstest/README for more details on how to
749 gperf has been removed from the base system for architectures
750 that use clang. Ports that require gperf will obtain it from the
754 pjdfstest has been moved from tools/regression/pjdfstest to
758 At svn r271982, The default linux compat kernel ABI has been adjusted
759 to 2.6.18 in support of the linux-c6 compat ports infrastructure
760 update. If you wish to continue using the linux-f10 compat ports,
761 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
762 encouraged to update their linux-compat packages to linux-c6 during
763 their next update cycle.
766 The ofwfb driver, used to provide a graphics console on PowerPC when
767 using vt(4), no longer allows mmap() of all physical memory. This
768 will prevent Xorg on PowerPC with some ATI graphics cards from
769 initializing properly unless x11-servers/xorg-server is updated to
773 The xdev targets have been converted to using TARGET and
774 TARGET_ARCH instead of XDEV and XDEV_ARCH.
777 The default unbound configuration has been modified to address
778 issues with reverse lookups on networks that use private
779 address ranges. If you use the local_unbound service, run
780 "service local_unbound setup" as root to regenerate your
781 configuration, then "service local_unbound reload" to load the
785 The GNU texinfo and GNU info pages are not built and installed
786 anymore, WITH_INFO knob has been added to allow to built and install
788 UPDATE: see 20150102 entry on texinfo's removal
791 The GNU readline library is now an INTERNALLIB - that is, it is
792 statically linked into consumers (GDB and variants) in the base
793 system, and the shared library is no longer installed. The
794 devel/readline port is available for third party software that
798 The Itanium architecture (ia64) has been removed from the list of
799 known architectures. This is the first step in the removal of the
803 Commit r268115 has added NFSv4.1 server support, merged from
804 projects/nfsv4.1-server. Since this includes changes to the
805 internal interfaces between the NFS related modules, a full
806 build of the kernel and modules will be necessary.
807 __FreeBSD_version has been bumped.
810 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
811 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
812 which differs from the behaviour controlled by this knob.)
815 Maximal length of the serial number in CTL was increased from 16 to
816 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
817 and ctld, need to be rebuilt to work with a new kernel.
820 The libatf-c and libatf-c++ major versions were downgraded to 0 and
821 1 respectively to match the upstream numbers. They were out of
822 sync because, when they were originally added to FreeBSD, the
823 upstream versions were not respected. These libraries are private
824 and not yet built by default, so renumbering them should be a
825 non-issue. However, unclean source trees will yield broken test
826 programs once the operator executes "make delete-old-libs" after a
829 Additionally, the atf-sh binary was made private by moving it into
830 /usr/libexec/. Already-built shell test programs will keep the
831 path to the old binary so they will break after "make delete-old"
834 If you are using WITH_TESTS=yes (not the default), wipe the object
835 tree and rebuild from scratch to prevent spurious test failures.
836 This is only needed once: the misnumbered libraries and misplaced
837 binaries have been added to OptionalObsoleteFiles.inc so they will
838 be removed during a clean upgrade.
841 Clang and llvm have been upgraded to 3.4.1 release.
844 We bogusly installed src.opts.mk in /usr/share/mk. This file should
845 be removed to avoid issues in the future (and has been added to
849 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
850 past, it affected all builds that used the bsd.*.mk files. The old
851 behavior was a bug, but people may have relied upon it. To get this
852 behavior back, you can .include /etc/src.conf from /etc/make.conf
853 (which is still global and isn't changed). This also changes the
854 behavior of incremental builds inside the tree of individual
855 directories. Set MAKESYSPATH to ".../share/mk" to do that.
856 Although this has survived make universe and some upgrade scenarios,
857 other upgrade scenarios may have broken. At least one form of
858 temporary breakage was fixed with MAKESYSPATH settings for buildworld
859 as well... In cases where MAKESYSPATH isn't working with this
860 setting, you'll need to set it to the full path to your tree.
862 One side effect of all this cleaning up is that bsd.compiler.mk
863 is no longer implicitly included by bsd.own.mk. If you wish to
864 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
868 The lindev device has been removed since /dev/full has been made a
869 standard device. __FreeBSD_version has been bumped.
872 The knob WITHOUT_VI was added to the base system, which controls
873 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
874 in order to reorder files share/termcap and didn't build ex(1) as a
875 build tool, so building/installing with WITH_VI is highly advised for
876 build hosts for older releases.
878 This issue has been fixed in stable/9 and stable/10 in r277022 and
879 r276991, respectively.
882 The YES_HESIOD knob has been removed. It has been obsolete for
883 a decade. Please move to using WITH_HESIOD instead or your builds
884 will silently lack HESIOD.
887 The uart(4) driver has been changed with respect to its handling
888 of the low-level console. Previously the uart(4) driver prevented
889 any process from changing the baudrate or the CLOCAL and HUPCL
890 control flags. By removing the restrictions, operators can make
891 changes to the serial console port without having to reboot.
892 However, when getty(8) is started on the serial device that is
893 associated with the low-level console, a misconfigured terminal
894 line in /etc/ttys will now have a real impact.
895 Before upgrading the kernel, make sure that /etc/ttys has the
896 serial console device configured as 3wire without baudrate to
897 preserve the previous behaviour. E.g:
898 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
901 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
902 to improve performance. To re-enable it, if needed, run rpcbind
903 with command line option -W.
906 Switched back to the GPL dtc compiler due to updates in the upstream
907 dts files not being supported by the BSDL dtc compiler. You will need
908 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
909 may result while building dtb files during a kernel build if you fail
910 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
913 Clang and llvm have been upgraded to 3.4 release.
916 The nve(4) driver has been removed. Please use the nfe(4) driver
917 for NVIDIA nForce MCP Ethernet adapters instead.
920 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
921 This could cause certain C++ applications using shared libraries built
922 against the previous version of libc++ to crash. The incompatibility
923 has now been fixed, but any C++ applications or shared libraries built
924 between r261283 and r261801 should be recompiled.
927 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
928 capability mode support. Please note that enabling the feature in
929 kernel is still highly recommended.
932 OpenSSH is now built with sandbox support, and will use sandbox as
933 the default privilege separation method. This requires Capsicum
934 capability mode support in kernel.
937 The libelf and libdwarf libraries have been updated to newer
938 versions from upstream. Shared library version numbers for
939 these two libraries were bumped. Any ports or binaries
940 requiring these two libraries should be recompiled.
941 __FreeBSD_version is bumped to 1100006.
944 If a Makefile in a tests/ directory was auto-generating a Kyuafile
945 instead of providing an explicit one, this would prevent such
946 Makefile from providing its own Kyuafile in the future during
947 NO_CLEAN builds. This has been fixed in the Makefiles but manual
948 intervention is needed to clean an objdir if you use NO_CLEAN:
949 # find /usr/obj -name Kyuafile | xargs rm -f
952 The behavior of gss_pseudo_random() for the krb5 mechanism
953 has changed, for applications requesting a longer random string
954 than produced by the underlying enctype's pseudo-random() function.
955 In particular, the random string produced from a session key of
956 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
957 be different at the 17th octet and later, after this change.
958 The counter used in the PRF+ construction is now encoded as a
959 big-endian integer in accordance with RFC 4402.
960 __FreeBSD_version is bumped to 1100004.
963 The WITHOUT_ATF build knob has been removed and its functionality
964 has been subsumed into the more generic WITHOUT_TESTS. If you were
965 using the former to disable the build of the ATF libraries, you
966 should change your settings to use the latter.
969 The default version of mtree is nmtree which is obtained from
970 NetBSD. The output is generally the same, but may vary
971 slightly. If you found you need identical output adding
972 "-F freebsd9" to the command line should do the trick. For the
973 time being, the old mtree is available as fmtree.
976 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
977 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
978 1.1.4_8 and verify bsdyml not linked in, before running "make
980 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
982 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
985 The stable/10 branch has been created in subversion from head
989 The rc.d/jail script has been updated to support jail(8)
990 configuration file. The "jail_<jname>_*" rc.conf(5) variables
991 for per-jail configuration are automatically converted to
992 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
993 This is transparently backward compatible. See below about some
994 incompatibilities and rc.conf(5) manual page for more details.
996 These variables are now deprecated in favor of jail(8) configuration
997 file. One can use "rc.d/jail config <jname>" command to generate
998 a jail(8) configuration file in /var/run/jail.<jname>.conf without
999 running the jail(8) utility. The default pathname of the
1000 configuration file is /etc/jail.conf and can be specified by
1001 using $jail_conf or $jail_<jname>_conf variables.
1003 Please note that jail_devfs_ruleset accepts an integer at
1004 this moment. Please consider to rewrite the ruleset name
1008 BIND has been removed from the base system. If all you need
1009 is a local resolver, simply enable and start the local_unbound
1010 service instead. Otherwise, several versions of BIND are
1011 available in the ports tree. The dns/bind99 port is one example.
1013 With this change, nslookup(1) and dig(1) are no longer in the base
1014 system. Users should instead use host(1) and drill(1) which are
1015 in the base system. Alternatively, nslookup and dig can
1016 be obtained by installing the dns/bind-tools port.
1019 With the addition of unbound(8), a new unbound user is now
1020 required during installworld. "mergemaster -p" can be used to
1021 add the user prior to installworld, as documented in the handbook.
1024 OpenSSH is now built with DNSSEC support, and will by default
1025 silently trust signed SSHFP records. This can be controlled with
1026 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1027 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1030 The GNU Compiler Collection and C++ standard library (libstdc++)
1031 are no longer built by default on platforms where clang is the system
1032 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1033 options in src.conf.
1036 The PROCDESC kernel option is now part of the GENERIC kernel
1037 configuration and is required for the rwhod(8) to work.
1038 If you are using custom kernel configuration, you should include
1042 The API and ABI related to the Capsicum framework was modified
1043 in backward incompatible way. The userland libraries and programs
1044 have to be recompiled to work with the new kernel. This includes the
1045 following libraries and programs, but the whole buildworld is
1046 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1047 kdump, procstat, rwho, rwhod, uniq.
1050 AES-NI intrinsic support has been added to gcc. The AES-NI module
1051 has been updated to use this support. A new gcc is required to build
1052 the aesni module on both i386 and amd64.
1055 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1056 Thus "device padlock_rng" and "device rdrand_rng" should be
1057 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1060 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1061 enables just the iconv* functionality and is now on by default.
1062 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1063 compatibility. Set WITHOUT_ICONV to build the old way.
1064 If you have been using WITH_ICONV before, you will very likely
1065 need to turn on WITH_LIBICONV_COMPAT.
1068 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1069 Illumos origin, including ZFS. If you have INVARIANTS in your
1070 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1072 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1073 locks if WITNESS option was set. Because that generated a lot of
1074 witness(9) reports and all of them were believed to be false
1075 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1076 can be used to achieve the previous behavior.
1079 Timer values in IPv6 data structures now use time_uptime instead
1080 of time_second. Although this is not a user-visible functional
1081 change, userland utilities which directly use them---ndp(8),
1082 rtadvd(8), and rtsold(8) in the base system---need to be updated
1083 to r253970 or later.
1086 find -delete can now delete the pathnames given as arguments,
1087 instead of only files found below them or if the pathname did
1088 not contain any slashes. Formerly, the following error message
1091 find: -delete: <path>: relative path potentially not safe
1093 Deleting the pathnames given as arguments can be prevented
1094 without error messages using -mindepth 1 or by changing
1095 directory and passing "." as argument to find. This works in the
1096 old as well as the new version of find.
1099 Behavior of devfs rules path matching has been changed.
1100 Pattern is now always matched against fully qualified devfs
1101 path and slash characters must be explicitly matched by
1102 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1103 subdirectories must be reviewed.
1106 The default ARM ABI has changed to the ARM EABI. The old ABI is
1107 incompatible with the ARM EABI and all programs and modules will
1108 need to be rebuilt to work with a new kernel.
1110 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1112 NOTE: Support for the old ABI will be removed in the future and
1113 users are advised to upgrade.
1116 pkg_install has been disconnected from the build if you really need it
1117 you should add WITH_PKGTOOLS in your src.conf(5).
1120 Most of network statistics structures were changed to be able
1121 keep 64-bits counters. Thus all tools, that work with networking
1122 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1125 Fix a bug that allowed a tracing process (e.g. gdb) to write
1126 to a memory-mapped file in the traced process's address space
1127 even if neither the traced process nor the tracing process had
1128 write access to that file.
1131 CVS has been removed from the base system. An exact copy
1132 of the code is available from the devel/cvs port.
1135 Some people report the following error after the switch to bmake:
1137 make: illegal option -- J
1138 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1140 *** [buildworld] Error code 2
1142 this likely due to an old instance of make in
1143 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1144 which src/Makefile will use that blindly, if it exists, so if
1145 you see the above error:
1147 rm -rf `make -V MAKEPATH`
1152 Use bmake by default.
1153 Whereas before one could choose to build with bmake via
1154 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1155 make. The goal is to remove these knobs for 10-RELEASE.
1157 It is worth noting that bmake (like gmake) treats the command
1158 line as the unit of failure, rather than statements within the
1159 command line. Thus '(cd some/where && dosomething)' is safer
1160 than 'cd some/where; dosomething'. The '()' allows consistent
1161 behavior in parallel build.
1164 Fix a bug that allows NFS clients to issue READDIR on files.
1167 The WITHOUT_IDEA option has been removed because
1168 the IDEA patent expired.
1171 The sysctl which controls TRIM support under ZFS has been renamed
1172 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1176 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1177 rather than creating it's own in the temporary directory in
1178 order allow access to bootstrapped versions of tools such as
1179 install and mtree. When upgrading from version of FreeBSD where
1180 the install command does not support -l, you will need to
1181 install a new mergemaster command if mergemaster -p is required.
1182 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1186 Legacy ATA stack, disabled and replaced by new CAM-based one since
1187 FreeBSD 9.0, completely removed from the sources. Kernel modules
1188 atadisk and atapi*, user-level tools atacontrol and burncd are
1189 removed. Kernel option `options ATA_CAM` is now permanently enabled
1193 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1194 and socketpair(2). Software, in particular Kerberos, may
1195 automatically detect and use these during building. The resulting
1196 binaries will not work on older kernels.
1199 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1200 information, see the respective 20130304 entry).
1203 Recent commits to callout(9) changed the size of struct callout,
1204 so the KBI is probably heavily disturbed. Also, some functions
1205 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1206 by macros. Every kernel module using it won't load, so rebuild
1209 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1210 but does not initialize by default (because of the new CTL_DISABLE
1211 option) to save memory. To re-enable it, remove the CTL_DISABLE
1212 option from the kernel config file or set kern.cam.ctl.disable=0
1213 in /boot/loader.conf.
1216 The ctl device has been disabled in GENERIC for i386 and amd64.
1217 This was done due to the extra memory being allocated at system
1218 initialisation time by the ctl driver which was only used if
1219 a CAM target device was created. This makes a FreeBSD system
1220 unusable on 128MB or less of RAM.
1223 A new compression method (lz4) has been merged to -HEAD. Please
1224 refer to zpool-features(7) for more information.
1226 Please refer to the "ZFS notes" section of this file for information
1227 on upgrading boot ZFS pools.
1230 A BSD-licensed patch(1) variant has been added and is installed
1231 as bsdpatch, being the GNU version the default patch.
1232 To inverse the logic and use the BSD-licensed one as default,
1233 while having the GNU version installed as gnupatch, rebuild
1234 and install world with the WITH_BSD_PATCH knob set.
1237 Due to the use of the new -l option to install(1) during build
1238 and install, you must take care not to directly set the INSTALL
1239 make variable in your /etc/make.conf, /etc/src.conf, or on the
1240 command line. If you wish to use the -C flag for all installs
1241 you may be able to add INSTALL+=-C to /etc/make.conf or
1245 The install(1) option -M has changed meaning and now takes an
1246 argument that is a file or path to append logs to. In the
1247 unlikely event that -M was the last option on the command line
1248 and the command line contained at least two files and a target
1249 directory the first file will have logs appended to it. The -M
1250 option served little practical purpose in the last decade so its
1251 use is expected to be extremely rare.
1254 After switching to Clang as the default compiler some users of ZFS
1255 on i386 systems started to experience stack overflow kernel panics.
1256 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1259 GEOM_LABEL now mangles label names read from file system metadata.
1260 Mangling affect labels containing spaces, non-printable characters,
1261 '%' or '"'. Device names in /etc/fstab and other places may need to
1265 By default, only the 10 most recent kernel dumps will be saved. To
1266 restore the previous behaviour (no limit on the number of kernel dumps
1267 stored in the dump directory) add the following line to /etc/rc.conf:
1272 With the addition of auditdistd(8), a new auditdistd user is now
1273 required during installworld. "mergemaster -p" can be used to
1274 add the user prior to installworld, as documented in the handbook.
1277 The sin6_scope_id member variable in struct sockaddr_in6 is now
1278 filled by the kernel before passing the structure to the userland via
1279 sysctl or routing socket. This means the KAME-specific embedded scope
1280 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1281 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1282 __FreeBSD_version is bumped to 1000025.
1285 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1286 This means that the world and kernel will be compiled with clang
1287 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1288 and /usr/bin/cpp. To disable this behavior and revert to building
1289 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1290 of current may need to bootstrap WITHOUT_CLANG first if the clang
1291 build fails (its compatibility window doesn't extend to the 9 stable
1295 The IPFIREWALL_FORWARD kernel option has been removed. Its
1296 functionality now turned on by default.
1299 The ZERO_COPY_SOCKET kernel option has been removed and
1300 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1301 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1302 mechanism which is not safe and may result in kernel crashes.
1303 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1304 driver supports disposeable external page sized mbuf storage.
1305 Proper replacements for both zero-copy mechanisms are under
1306 consideration and will eventually lead to complete removal
1307 of the two kernel options.
1310 The IPv4 network stack has been converted to network byte
1311 order. The following modules need to be recompiled together
1312 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1313 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1316 Support for non-MPSAFE filesystems was removed from VFS. The
1317 VFS_VERSION was bumped, all filesystem modules shall be
1321 All the non-MPSAFE filesystems have been disconnected from
1322 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1323 portalfs, smbfs, xfs.
1326 The interface cloning API and ABI has changed. The following
1327 modules need to be recompiled together with kernel:
1328 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1329 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1330 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1333 The sdhci driver was split in two parts: sdhci (generic SD Host
1334 Controller logic) and sdhci_pci (actual hardware driver).
1335 No kernel config modifications are required, but if you
1336 load sdhc as a module you must switch to sdhci_pci instead.
1339 Import the FUSE kernel and userland support into base system.
1342 The GNU sort(1) program has been removed since the BSD-licensed
1343 sort(1) has been the default for quite some time and no serious
1344 problems have been reported. The corresponding WITH_GNU_SORT
1348 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1349 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1353 The net80211(4) ABI has been changed to allow for improved driver
1354 PS-POLL and power-save support. All wireless drivers need to be
1355 recompiled to work with the new kernel.
1358 The random(4) support for the VIA hardware random number
1359 generator (`PADLOCK') is no longer enabled unconditionally.
1360 Add the padlock_rng device in the custom kernel config if
1361 needed. The GENERIC kernels on i386 and amd64 do include the
1362 device, so the change only affects the custom kernel
1366 The pf(4) packet filter ABI has been changed. pfctl(8) and
1367 snmp_pf module need to be recompiled to work with new kernel.
1370 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1371 to -HEAD. Pools that have empty_bpobj in active state can not be
1372 imported read-write with ZFS implementations that do not support
1373 this feature. For more information read the zpool-features(5)
1377 The sparc64 ZFS loader has been changed to no longer try to auto-
1378 detect ZFS providers based on diskN aliases but now requires these
1379 to be explicitly listed in the OFW boot-device environment variable.
1382 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1383 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1384 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1387 The following sysctls and tunables have been renamed for consistency
1388 with other variables:
1389 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1390 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1393 The sort utility has been replaced with BSD sort. For now, GNU sort
1394 is also available as "gnusort" or the default can be set back to
1395 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1396 installed as "bsdsort".
1399 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1400 Starting with this version the old system of ZFS pool versioning
1401 is superseded by "feature flags". This concept enables forward
1402 compatibility against certain future changes in functionality of ZFS
1403 pools. The first read-only compatible "feature flag" for ZFS pools
1404 is named "com.delphix:async_destroy". For more information
1405 read the new zpool-features(5) manual page.
1406 Please refer to the "ZFS notes" section of this file for information
1407 on upgrading boot ZFS pools.
1410 The malloc(3) implementation embedded in libc now uses sources imported
1411 as contrib/jemalloc. The most disruptive API change is to
1412 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1413 delete it prior to installworld, and optionally re-create it using the
1414 new format after rebooting. See malloc.conf(5) for details
1415 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1419 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1420 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1421 now spelled mips. This is to aid compatibility with third-party
1422 software that expects this naming scheme in uname(3). Little-endian
1423 settings are unchanged. If you are updating a big-endian mips64 machine
1424 from before this change, you may need to set MACHINE_ARCH=mips64 in
1425 your environment before the new build system will recognize your machine.
1428 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1432 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1433 nullfs(5) did not pass through all behaviours to the underlying layer,
1434 as a result if we bound to a socket on the lower layer we could connect
1435 only to the lower path; if we bound to the upper layer we could connect
1436 only to the upper path. The new behavior is one can connect to both the
1437 lower and the upper paths regardless what layer path one binds to.
1440 The getifaddrs upgrade path broken with 20111215 has been restored.
1441 If you have upgraded in between 20111215 and 20120209 you need to
1442 recompile libc again with your kernel. You still need to recompile
1443 world to be able to configure CARP but this restriction already
1444 comes from 20111215.
1447 The set_rcvar() function has been removed from /etc/rc.subr. All
1448 base and ports rc.d scripts have been updated, so if you have a
1449 port installed with a script in /usr/local/etc/rc.d you can either
1450 hand-edit the rcvar= line, or reinstall the port.
1452 An easy way to handle the mass-update of /etc/rc.d:
1453 rm /etc/rc.d/* && mergemaster -i
1456 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1457 on the current CPU and prevents other threads from running.
1458 This behavior can be reverted using the kern.stop_scheduler_on_panic
1460 The new behavior can be incompatible with kern.sync_on_panic.
1463 The carp(4) facility has been changed significantly. Configuration
1464 of the CARP protocol via ifconfig(8) has changed, as well as format
1465 of CARP events submitted to devd(8) has changed. See manual pages
1466 for more information. The arpbalance feature of carp(4) is currently
1467 not supported anymore.
1469 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1470 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1471 need to be recompiled.
1474 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1478 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1479 explicitely support non-MPSAFE filesystems.
1480 It is on by default for all supported platform at this present
1484 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1485 i386 and pc98 GENERIC kernel configuration files.
1488 sysinstall has been removed
1491 The stable/9 branch created in subversion. This corresponds to the
1492 RELENG_9 branch in CVS.
1498 Avoid using make -j when upgrading. While generally safe, there are
1499 sometimes problems using -j to upgrade. If your upgrade fails with
1500 -j, please try again without -j. From time to time in the past there
1501 have been problems using -j with buildworld and/or installworld. This
1502 is especially true when upgrading between "distant" versions (eg one
1503 that cross a major release boundary or several minor releases, or when
1504 several months have passed on the -current branch).
1506 Sometimes, obscure build problems are the result of environment
1507 poisoning. This can happen because the make utility reads its
1508 environment when searching for values for global variables. To run
1509 your build attempts in an "environmental clean room", prefix all make
1510 commands with 'env -i '. See the env(1) manual page for more details.
1512 When upgrading from one major version to another it is generally best
1513 to upgrade to the latest code in the currently installed branch first,
1514 then do an upgrade to the new branch. This is the best-tested upgrade
1515 path, and has the highest probability of being successful. Please try
1516 this approach before reporting problems with a major version upgrade.
1518 When upgrading a live system, having a root shell around before
1519 installing anything can help undo problems. Not having a root shell
1520 around can lead to problems if pam has changed too much from your
1521 starting point to allow continued authentication after the upgrade.
1523 This file should be read as a log of events. When a later event changes
1524 information of a prior event, the prior event should not be deleted.
1525 Instead, a pointer to the entry with the new information should be
1526 placed in the old entry. Readers of this file should also sanity check
1527 older entries before relying on them blindly. Authors of new entries
1528 should write them with this in mind.
1532 When upgrading the boot ZFS pool to a new version, always follow
1535 1.) recompile and reinstall the ZFS boot loader and boot block
1536 (this is part of "make buildworld" and "make installworld")
1538 2.) update the ZFS boot block on your boot drive
1540 The following example updates the ZFS boot block on the first
1541 partition (freebsd-boot) of a GPT partitioned drive ada0:
1542 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1544 Non-boot pools do not need these updates.
1548 If you are updating from a prior version of FreeBSD (even one just
1549 a few days old), you should follow this procedure. It is the most
1550 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1552 make kernel-toolchain
1553 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1554 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1556 To test a kernel once
1557 ---------------------
1558 If you just want to boot a kernel once (because you are not sure
1559 if it works, or if you want to boot a known bad kernel to provide
1560 debugging information) run
1561 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1562 nextboot -k testkernel
1564 To just build a kernel when you know that it won't mess you up
1565 --------------------------------------------------------------
1566 This assumes you are already running a CURRENT system. Replace
1567 ${arch} with the architecture of your machine (e.g. "i386",
1568 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1570 cd src/sys/${arch}/conf
1571 config KERNEL_NAME_HERE
1572 cd ../compile/KERNEL_NAME_HERE
1577 If this fails, go to the "To build a kernel" section.
1579 To rebuild everything and install it on the current system.
1580 -----------------------------------------------------------
1581 # Note: sometimes if you are running current you gotta do more than
1582 # is listed here if you are upgrading from a really old current.
1584 <make sure you have good level 0 dumps>
1586 make kernel KERNCONF=YOUR_KERNEL_HERE
1588 <reboot in single user> [3]
1595 To cross-install current onto a separate partition
1596 --------------------------------------------------
1597 # In this approach we use a separate partition to hold
1598 # current's root, 'usr', and 'var' directories. A partition
1599 # holding "/", "/usr" and "/var" should be about 2GB in
1602 <make sure you have good level 0 dumps>
1605 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1606 <maybe newfs current's root partition>
1607 <mount current's root partition on directory ${CURRENT_ROOT}>
1608 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1609 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1610 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1611 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1612 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1613 <reboot into current>
1614 <do a "native" rebuild/install as described in the previous section>
1615 <maybe install compatibility libraries from ports/misc/compat*>
1619 To upgrade in-place from stable to current
1620 ----------------------------------------------
1621 <make sure you have good level 0 dumps>
1623 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1625 <reboot in single user> [3]
1632 Make sure that you've read the UPDATING file to understand the
1633 tweaks to various things you need. At this point in the life
1634 cycle of current, things change often and you are on your own
1635 to cope. The defaults can also change, so please read ALL of
1636 the UPDATING entries.
1638 Also, if you are tracking -current, you must be subscribed to
1639 freebsd-current@freebsd.org. Make sure that before you update
1640 your sources that you have read and understood all the recent
1641 messages there. If in doubt, please track -stable which has
1642 much fewer pitfalls.
1644 [1] If you have third party modules, such as vmware, you
1645 should disable them at this point so they don't crash your
1648 [3] From the bootblocks, boot -s, and then do
1653 adjkerntz -i # if CMOS is wall time
1654 Also, when doing a major release upgrade, it is required that
1655 you boot into single user mode to do the installworld.
1657 [4] Note: This step is non-optional. Failure to do this step
1658 can result in a significant reduction in the functionality of the
1659 system. Attempting to do it by hand is not recommended and those
1660 that pursue this avenue should read this file carefully, as well
1661 as the archives of freebsd-current and freebsd-hackers mailing lists
1662 for potential gotchas. The -U option is also useful to consider.
1663 See mergemaster(8) for more information.
1665 [5] Usually this step is a noop. However, from time to time
1666 you may need to do this if you get unknown user in the following
1667 step. It never hurts to do it all the time. You may need to
1668 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1669 install) after the buildworld before this step if you last updated
1670 from current before 20130425 or from -stable before 20130430.
1672 [6] This only deletes old files and directories. Old libraries
1673 can be deleted by "make delete-old-libs", but you have to make
1674 sure that no program is using those libraries anymore.
1676 [8] In order to have a kernel that can run the 4.x binaries needed to
1677 do an installworld, you must include the COMPAT_FREEBSD4 option in
1678 your kernel. Failure to do so may leave you with a system that is
1679 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1680 required to run the 5.x binaries on more recent kernels. And so on
1681 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1683 Make sure that you merge any new devices from GENERIC since the
1684 last time you updated your kernel config file.
1686 [9] When checking out sources, you must include the -P flag to have
1687 cvs prune empty directories.
1689 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1690 "?=" instead of the "=" assignment operator, so that buildworld can
1691 override the CPUTYPE if it needs to.
1693 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1694 not on the command line, or in /etc/make.conf. buildworld will
1695 warn if it is improperly defined.
1698 This file contains a list, in reverse chronological order, of major
1699 breakages in tracking -current. It is not guaranteed to be a complete
1700 list of such breakages, and only contains entries since September 23, 2011.
1701 If you need to see UPDATING entries from before that date, you will need
1702 to fetch an UPDATING file from an older FreeBSD release.
1704 Copyright information:
1706 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1708 Redistribution, publication, translation and use, with or without
1709 modification, in full or in part, in any form or format of this
1710 document are permitted without further permission from the author.
1712 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1713 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1714 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1715 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1716 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1717 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1718 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1719 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1720 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1721 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1722 POSSIBILITY OF SUCH DAMAGE.
1724 Contact Warner Losh if you have any questions about your use of