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