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