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 LOADER_FIREWIRE_SUPPORT build variable as been renamed to
21 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
22 to WITH/OUT_LOADER_GELI.
25 The geli password typed at boot is now hidden. To restore the previous
26 behavior, see geli(8) for configuration options.
29 The SW_WATCHDOG option is no longer necessary to enable the
30 hardclock-based software watchdog if no hardware watchdog is
31 configured. As before, SW_WATCHDOG will cause the software
32 watchdog to be enabled even if a hardware watchdog is configured.
35 lint(1) binaries and library are no longer built by default. To
36 enable building them, define WITH_LINT in src.conf. If you are using
37 a FreeBSD 12 or later system to build 11-stable, you may need to
38 install a lint(1) binary to use WITH_LINT.
41 When building multiple kernels using KERNCONF, non-existent KERNCONF
42 files will produce an error and buildkernel will fail. Previously
43 missing KERNCONF files silently failed giving no indication as to
44 why, only to subsequently discover during installkernel that the
45 desired kernel was never built in the first place.
48 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
49 Please see the 20141231 entry below for information about prerequisites
50 and upgrading, if you are not already using clang 3.5.0 or higher.
53 Since the switch to GPT disk labels, fsck for UFS/FFS has been
54 unable to automatically find alternate superblocks. As of r322806,
55 the information needed to find alternate superblocks has been
56 moved to the end of the area reserved for the boot block.
57 Filesystems created with a newfs of this vintage or later
58 will create the recovery information. If you have a filesystem
59 created prior to this change and wish to have a recovery block
60 created for your filesystem, you can do so by running fsck in
61 forground mode (i.e., do not use the -p or -y options). As it
62 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
63 to which you should answer yes.
66 arm64 builds now use the base system LLD 4.0.0 linker by default,
67 instead of requiring that the aarch64-binutils port or package be
68 installed. To continue using aarch64-binutils, set
69 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
72 The ctl.ko module no longer implements the iSCSI target frontend:
73 cfiscsi.ko does instead.
75 If building cfiscsi.ko as a kernel module, the module can be loaded
76 via one of the following methods:
77 - `cfiscsi_load="YES"` in loader.conf(5).
78 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
79 - ctladm(8)/ctld(8), when compiled with iSCSI support
80 (`WITH_ISCSI=yes` in src.conf(5))
82 Please see cfiscsi(4) for more details.
85 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
86 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
87 same source (previously, the dependency of mmcsd.ko on mmc.ko was
88 missing, but mmcsd.ko now will refuse to load if it is incompatible
92 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
93 use any explicitly assigned loopback address available in the jail
94 instead of using the first assigned address of the jail.
97 As of r316810 for ipfilter, keep frags is no longer assumed when
98 keep state is specified in a rule. r316810 aligns ipfilter with
99 documentation in man pages separating keep frags from keep state.
100 This allows keep state to specified without forcing keep frags
101 and allows keep frags to be specified independently of keep state.
102 To maintain previous behaviour, also specify keep frags with
103 keep state (as documented in ipf.conf.5).
106 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
107 Please see the 20141231 entry below for information about prerequisites
108 and upgrading, if you are not already using clang 3.5.0 or higher.
111 The code that provides support for ZFS .zfs/ directory functionality
112 has been reimplemented. It's not possible now to create a snapshot
113 by mkdir under .zfs/snapshot/. That should be the only user visible
117 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
118 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
119 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
120 and now NAT-T is supported by default. Security associations now use
121 the single namespace for SPI allocation, so if you use several manually
122 configured security associations with the same SPI, this configuration
126 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
127 Please see the 20141231 entry below for information about prerequisites
128 and upgrading, if you are not already using clang 3.5.0 or higher.
131 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
132 Please see the 20141231 entry below for information about prerequisites
133 and upgrading, if you are not already using clang 3.5.0 or higher.
136 The layout of the pmap structure has changed for powerpc to put the pmap
137 statistics at the front for all CPU variations. libkvm(3) and all tools
138 that link against it need to be recompiled.
141 isl(4) and cyapa(4) drivers now require a new driver,
142 chromebook_platform(4), to work properly on Chromebook-class hardware.
143 On other types of hardware the drivers may need to be configured using
144 device hints. Please see the corresponding manual pages for details.
147 Relocatable object files with the extension of .So have been renamed
148 to use an extension of .pico instead. The purpose of this change is
149 to avoid a name clash with shared libraries on case-insensitive file
150 systems. On those file systems, foo.So is the same file as foo.so.
153 The libc stub for the pipe(2) system call has been replaced with
154 a wrapper that calls the pipe2(2) system call and the pipe(2)
155 system call is now only implemented by the kernels that include
156 "options COMPAT_FREEBSD10" in their config file (this is the
157 default). Users should ensure that this option is enabled in
158 their kernel or upgrade userspace to r302092 before upgrading their
162 CAM will now strip leading spaces from SCSI disks' serial numbers.
163 This will effect users who create UFS filesystems on SCSI disks using
164 those disk's diskid device nodes. For example, if /etc/fstab
165 previously contained a line like
166 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
167 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
168 transforms like gmirror may also be affected. ZFS users should
172 The bitstring(3) API has been updated with new functionality and
173 improved performance. But it is binary-incompatible with the old API.
174 Objects built with the new headers may not be linked against objects
175 built with the old headers.
178 The brk and sbrk functions have been removed from libc on arm64.
179 Binutils from ports has been updated to not link to these
180 functions and should be updated to the latest version before
181 installing a new libc.
184 The armv6 port now defaults to hard float ABI. Limited support
185 for running both hardfloat and soft float on the same system
186 is available using the libraries installed with -DWITH_LIBSOFT.
187 This has only been tested as an upgrade path for installworld
188 and packages may fail or need manual intervention to run. New
189 packages will be needed.
191 To update an existing self-hosted armv6hf system, you must add
192 TARGET_ARCH=armv6 on the make command line for both the build
193 and the install steps.
196 Kernel modules compiled outside of a kernel build now default to
197 installing to /boot/modules instead of /boot/kernel. Many kernel
198 modules built this way (such as those in ports) already overrode
199 KMODDIR explicitly to install into /boot/modules. However,
200 manually building and installing a module from /sys/modules will
201 now install to /boot/modules instead of /boot/kernel.
204 The CAM I/O scheduler has been committed to the kernel. There should be
205 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
206 list of known rogues that claim support for this but actually corrupt
207 data is believed to be complete, be on the lookout for data
208 corruption. The known rogue list is believed to be complete:
210 o Crucial MX100, M550 drives with MU01 firmware.
211 o Micron M510 and M550 drives with MU01 firmware.
212 o Micron M500 prior to MU07 firmware
213 o Samsung 830, 840, and 850 all firmwares
214 o FCCT M500 all firmwares
216 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
217 with working NCQ TRIM. For Micron branded drives, see your sales rep for
218 updated firmware. Black listed drives will work correctly because these
219 drives work correctly so long as no NCQ TRIMs are sent to them. Given
220 this list is the same as found in Linux, it's believed there are no
221 other rogues in the market place. All other models from the above
224 To be safe, if you are at all concerned, you can quirk each of your
225 drives to prevent NCQ from being sent by setting:
226 kern.cam.ada.X.quirks="0x2"
227 in loader.conf. If the drive requires the 4k sector quirk, set the
231 The FAST_DEPEND build option has been removed and its functionality is
232 now the one true way. The old mkdep(1) style of 'make depend' has
233 been removed. See 20160311 for further details.
236 Resource range types have grown from unsigned long to uintmax_t. All
237 drivers, and anything using libdevinfo, need to be recompiled.
240 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
241 builds. It no longer runs mkdep(1) during 'make depend', and the
242 'make depend' stage can safely be skipped now as it is auto ran
243 when building 'make all' and will generate all SRCS and DPSRCS before
244 building anything else. Dependencies are gathered at compile time with
245 -MF flags kept in separate .depend files per object file. Users should
246 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
250 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
251 kernel modules. Therefore, if you load any kernel modules at boot time,
252 please install the boot loaders after you install the kernel, but before
256 make kernel KERNCONF=YOUR_KERNEL_HERE
257 make -C sys/boot install
258 <reboot in single user>
260 Then follow the usual steps, described in the General Notes section,
264 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
265 see the 20141231 entry below for information about prerequisites and
266 upgrading, if you are not already using clang 3.5.0 or higher.
269 The AIO subsystem is now a standard part of the kernel. The
270 VFS_AIO kernel option and aio.ko kernel module have been removed.
271 Due to stability concerns, asynchronous I/O requests are only
272 permitted on sockets and raw disks by default. To enable
273 asynchronous I/O requests on all file types, set the
274 vfs.aio.enable_unsafe sysctl to a non-zero value.
277 The ELF object manipulation tool objcopy is now provided by the
278 ELF Tool Chain project rather than by GNU binutils. It should be a
279 drop-in replacement, with the addition of arm64 support. The
280 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
281 to obtain the GNU version if necessary.
284 Building ZFS pools on top of zvols is prohibited by default. That
285 feature has never worked safely; it's always been prone to deadlocks.
286 Using a zvol as the backing store for a VM guest's virtual disk will
287 still work, even if the guest is using ZFS. Legacy behavior can be
288 restored by setting vfs.zfs.vol.recursive=1.
291 The NONE and HPN patches has been removed from OpenSSH. They are
292 still available in the security/openssh-portable port.
295 With the addition of ypldap(8), a new _ypldap user is now required
296 during installworld. "mergemaster -p" can be used to add the user
297 prior to installworld, as documented in the handbook.
300 The tftp loader (pxeboot) now uses the option root-path directive. As a
301 consequence it no longer looks for a pxeboot.4th file on the tftp
302 server. Instead it uses the regular /boot infrastructure as with the
306 The code to start recording plug and play data into the modules has
307 been committed. While the old tools will properly build a new kernel,
308 a number of warnings about "unknown metadata record 4" will be produced
309 for an older kldxref. To avoid such warnings, make sure to rebuild
310 the kernel toolchain (or world). Make sure that you have r292078 or
311 later when trying to build 292077 or later before rebuilding.
314 Debug data files are now built by default with 'make buildworld' and
315 installed with 'make installworld'. This facilitates debugging but
316 requires more disk space both during the build and for the installed
317 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
321 r291527 changed the internal interface between the nfsd.ko and
322 nfscommon.ko modules. As such, they must both be upgraded to-gether.
323 __FreeBSD_version has been bumped because of this.
326 Add support for unicode collation strings leads to a change of
327 order of files listed by ls(1) for example. To get back to the old
328 behaviour, set LC_COLLATE environment variable to "C".
330 Databases administrators will need to reindex their databases given
331 collation results will be different.
333 Due to a bug in install(1) it is recommended to remove the ancient
334 locales before running make installworld.
336 rm -rf /usr/share/locale/*
339 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
340 libcrypto.so.7 or libssl.so.7 must be recompiled.
343 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
344 Kernel modules isp_2400_multi and isp_2500_multi were removed and
345 should be replaced with isp_2400 and isp_2500 modules respectively.
348 The build previously allowed using 'make -n' to not recurse into
349 sub-directories while showing what commands would be executed, and
350 'make -n -n' to recursively show commands. Now 'make -n' will recurse
351 and 'make -N' will not.
354 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
355 and etcupdate will now use this file. A custom sendmail.cf is now
356 updated via this mechanism rather than via installworld. If you had
357 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
358 want to remove the exclusion or change it to "always install".
359 /etc/mail/sendmail.cf is now managed the same way regardless of
360 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
361 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
364 Compatibility shims for legacy ATA device names have been removed.
365 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
366 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
367 environment variables, /dev/ad* and /dev/ar* symbolic links.
370 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
371 Please see the 20141231 entry below for information about prerequisites
372 and upgrading, if you are not already using clang 3.5.0 or higher.
375 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
376 and renamed from .symbols to .debug. This reduces the size requirements
377 on the boot partition or file system and provides consistency with
378 userland debug files.
380 When using the supported kernel installation method the
381 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
382 as is done with /boot/kernel.
384 Developers wishing to maintain the historical behavior of installing
385 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
388 The wireless drivers had undergone changes that remove the 'parent
389 interface' from the ifconfig -l output. The rc.d network scripts
390 used to check presence of a parent interface in the list, so old
391 scripts would fail to start wireless networking. Thus, etcupdate(3)
392 or mergemaster(8) run is required after kernel update, to update your
393 rc.d scripts in /etc.
396 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
397 These configurations are now automatically interpreted as
398 'scrub fragment reassemble'.
401 Kernel-loadable modules for the random(4) device are back. To use
402 them, the kernel must have
405 options RANDOM_LOADABLE
407 kldload(8) can then be used to load random_fortuna.ko
408 or random_yarrow.ko. Please note that due to the indirect
409 function calls that the loadable modules need to provide,
410 the build-in variants will be slightly more efficient.
412 The random(4) kernel option RANDOM_DUMMY has been retired due to
413 unpopularity. It was not all that useful anyway.
416 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
417 Control over building the ELF Tool Chain tools is now provided by
418 the WITHOUT_TOOLCHAIN knob.
421 The polarity of Pulse Per Second (PPS) capture events with the
422 uart(4) driver has been corrected. Prior to this change the PPS
423 "assert" event corresponded to the trailing edge of a positive PPS
424 pulse and the "clear" event was the leading edge of the next pulse.
426 As the width of a PPS pulse in a typical GPS receiver is on the
427 order of 1 millisecond, most users will not notice any significant
428 difference with this change.
430 Anyone who has compensated for the historical polarity reversal by
431 configuring a negative offset equal to the pulse width will need to
432 remove that workaround.
435 The default group assigned to /dev/dri entries has been changed
436 from 'wheel' to 'video' with the id of '44'. If you want to have
437 access to the dri devices please add yourself to the video group
440 # pw groupmod video -m $USER
443 The menu.rc and loader.rc files will now be replaced during
444 upgrades. Please migrate local changes to menu.rc.local and
445 loader.rc.local instead.
448 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
449 strings and strip have been removed. The src.conf(5) knob
450 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
453 As ZFS requires more kernel stack pages than is the default on some
454 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
455 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
457 Please consider using 'options KSTACK_PAGES=X' where X is greater
458 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
461 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
462 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
463 default, i.e., they will not contain "::". For example, instead
464 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
465 to have a more specific match, such as different map entries for
466 IPv6:0:0 vs IPv6:0. This change requires that configuration
467 data (including maps, files, classes, custom ruleset, etc.) must
468 use the same format, so make certain such configuration data is
469 upgrading. As a very simple check search for patterns like
470 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
471 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
472 the cf option UseCompressedIPv6Addresses.
475 The default kernel entropy-processing algorithm is now
476 Fortuna, replacing Yarrow.
478 Assuming you have 'device random' in your kernel config
479 file, the configurations allow a kernel option to override
480 this default. You may choose *ONE* of:
482 options RANDOM_YARROW # Legacy /dev/random algorithm.
483 options RANDOM_DUMMY # Blocking-only driver.
485 If you have neither, you get Fortuna. For most people,
486 read no further, Fortuna will give a /dev/random that works
487 like it always used to, and the difference will be irrelevant.
489 If you remove 'device random', you get *NO* kernel-processed
490 entropy at all. This may be acceptable to folks building
491 embedded systems, but has complications. Carry on reading,
492 and it is assumed you know what you need.
494 *PLEASE* read random(4) and random(9) if you are in the
495 habit of tweaking kernel configs, and/or if you are a member
496 of the embedded community, wanting specific and not-usual
497 behaviour from your security subsystems.
499 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
500 random', you will NOT have a functioning /dev/random, and
501 many cryptographic features will not work, including SSH.
502 You may also find strange behaviour from the random(3) set
503 of library functions, in particular sranddev(3), srandomdev(3)
504 and arc4random(3). The reason for this is that the KERN_ARND
505 sysctl only returns entropy if it thinks it has some to
506 share, and with RANDOM_DUMMY or no 'device random' this
510 An additional fix for the issue described in the 20150614 sendmail
511 entry below has been been committed in revision 284717.
514 FreeBSD's old make (fmake) has been removed from the system. It is
515 available as the devel/fmake port or via pkg install fmake.
518 The fix for the issue described in the 20150614 sendmail entry
519 below has been been committed in revision 284436. The work
520 around described in that entry is no longer needed unless the
521 default setting is overridden by a confDH_PARAMETERS configuration
522 setting of '5' or pointing to a 512 bit DH parameter file.
525 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
526 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
527 and devel/kyua to version 0.20+ and adjust any calling code to work
528 with Kyuafile and kyua.
531 The import of openssl to address the FreeBSD-SA-15:10.openssl
532 security advisory includes a change which rejects handshakes
533 with DH parameters below 768 bits. sendmail releases prior
534 to 8.15.2 (not yet released), defaulted to a 512 bit
535 DH parameter setting for client connections. To work around
536 this interoperability, sendmail can be configured to use a
537 2048 bit DH parameter by:
539 1. Edit /etc/mail/`hostname`.mc
540 2. If a setting for confDH_PARAMETERS does not exist or
541 exists and is set to a string beginning with '5',
543 3. If a setting for confDH_PARAMETERS exists and is set to
544 a file path, create a new file with:
545 openssl dhparam -out /path/to/file 2048
546 4. Rebuild the .cf file:
547 cd /etc/mail/; make; make install
549 cd /etc/mail/; make restart
551 A sendmail patch is coming, at which time this file will be
555 Generation of legacy formatted entries have been disabled by default
556 in pwd_mkdb(8), as all base system consumers of the legacy formatted
557 entries were converted to use the new format by default when the new,
558 machine independent format have been added and supported since FreeBSD
561 Please see the pwd_mkdb(8) manual page for further details.
564 Clang and llvm have been upgraded to 3.6.1 release. Please see the
565 20141231 entry below for information about prerequisites and upgrading,
566 if you are not already using 3.5.0 or higher.
569 TI platform code switched to using vendor DTS files and this update
570 may break existing systems running on Beaglebone, Beaglebone Black,
573 - dtb files should be regenerated/reinstalled. Filenames are the
574 same but content is different now
575 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
576 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
577 addressing scheme is now pin 25 on /dev/gpioc3.
578 - Pandaboard: /etc/ttys should be updated, serial console device is
579 now /dev/ttyu2, not /dev/ttyu0
582 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
583 If you need the GNU extension from groff soelim(1), install groff
584 from package: pkg install groff, or via ports: textproc/groff.
587 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
588 defined in symlink(7); previously symlinks were silently ignored.
591 The const qualifier has been removed from iconv(3) to comply with
592 POSIX. The ports tree is aware of this from r384038 onwards.
595 Libraries specified by LIBADD in Makefiles must have a corresponding
596 DPADD_<lib> variable to ensure correct dependencies. This is now
597 enforced in src.libnames.mk.
600 From legacy ata(4) driver was removed support for SATA controllers
601 supported by more functional drivers ahci(4), siis(4) and mvs(4).
602 Kernel modules ataahci and ataadaptec were removed completely,
603 replaced by ahci and mvs modules respectively.
606 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
607 the 20141231 entry below for information about prerequisites and
608 upgrading, if you are not already using 3.5.0 or higher.
611 The 32-bit PowerPC kernel has been changed to a position-independent
612 executable. This can only be booted with a version of loader(8)
613 newer than January 31, 2015, so make sure to update both world and
614 kernel before rebooting.
617 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
618 but before r278950, the RNG was not seeded properly. Immediately
619 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
620 ssh keys or openssl keys) that were generated w/ a kernel from that
621 range. This does not affect programs that directly used /dev/random
622 or /dev/urandom. All userland uses of arc4random(3) are affected.
625 The autofs(4) ABI was changed in order to restore binary compatibility
626 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
630 The powerpc64 kernel has been changed to a position-independent
631 executable. This can only be booted with a new version of loader(8),
632 so make sure to update both world and kernel before rebooting.
635 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
636 only release, no new features have been added. Please see the 20141231
637 entry below for information about prerequisites and upgrading, if you
638 are not already using 3.5.0.
641 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
642 taken from the ELF Tool Chain project rather than GNU binutils. They
643 should be drop-in replacements, with the addition of arm64 support.
644 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
645 binutils tools, if necessary. See 20150805 for updated information.
648 The default Unbound configuration now enables remote control
649 using a local socket. Users who have already enabled the
650 local_unbound service should regenerate their configuration
651 by running "service local_unbound setup" as root.
654 The GNU texinfo and GNU info pages have been removed.
655 To be able to view GNU info pages please install texinfo from ports.
658 Clang, llvm and lldb have been upgraded to 3.5.0 release.
660 As of this release, a prerequisite for building clang, llvm and lldb is
661 a C++11 capable compiler and C++11 standard library. This means that to
662 be able to successfully build the cross-tools stage of buildworld, with
663 clang as the bootstrap compiler, your system compiler or cross compiler
664 should either be clang 3.3 or later, or gcc 4.8 or later, and your
665 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
668 On any standard FreeBSD 10.x or 11.x installation, where clang and
669 libc++ are on by default (that is, on x86 or arm), this should work out
672 On 9.x installations where clang is enabled by default, e.g. on x86 and
673 powerpc, libc++ will not be enabled by default, so libc++ should be
674 built (with clang) and installed first. If both clang and libc++ are
675 missing, build clang first, then use it to build libc++.
677 On 8.x and earlier installations, upgrade to 9.x first, and then follow
678 the instructions for 9.x above.
680 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
681 default, and do not build clang.
683 Many embedded systems are resource constrained, and will not be able to
684 build clang in a reasonable time, or in some cases at all. In those
685 cases, cross building bootable systems on amd64 is a workaround.
687 This new version of clang introduces a number of new warnings, of which
688 the following are most likely to appear:
692 This warns in two cases, for both C and C++:
693 * When the code is trying to take the absolute value of an unsigned
694 quantity, which is effectively a no-op, and almost never what was
695 intended. The code should be fixed, if at all possible. If you are
696 sure that the unsigned quantity can be safely cast to signed, without
697 loss of information or undefined behavior, you can add an explicit
698 cast, or disable the warning.
700 * When the code is trying to take an absolute value, but the called
701 abs() variant is for the wrong type, which can lead to truncation.
702 If you want to disable the warning instead of fixing the code, please
703 make sure that truncation will not occur, or it might lead to unwanted
706 -Wtautological-undefined-compare and
707 -Wundefined-bool-conversion
709 These warn when C++ code is trying to compare 'this' against NULL, while
710 'this' should never be NULL in well-defined C++ code. However, there is
711 some legacy (pre C++11) code out there, which actively abuses this
712 feature, which was less strictly defined in previous C++ versions.
714 Squid and openjdk do this, for example. The warning can be turned off
715 for C++98 and earlier, but compiling the code in C++11 mode might result
716 in unexpected behavior; for example, the parts of the program that are
717 unreachable could be optimized away.
720 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
721 kernel sources have been removed. The .h files remain, since some
722 utilities include them. This will need to be fixed later.
723 If "mount -t oldnfs ..." is attempted, it will fail.
724 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
725 the utilities will report errors.
728 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
729 directories to top level SUBDIR variable when their parent
730 directory is included in LOCAL_DIRS. Users with build systems with
731 such hierarchies and without SUBDIR entries in the parent
732 directory Makefiles should add them or add the directories to
736 faith(4) and faithd(8) have been removed from the base system. Faith
737 has been obsolete for a very long time.
740 vt(4), the new console driver, is enabled by default. It brings
741 support for Unicode and double-width characters, as well as
742 support for UEFI and integration with the KMS kernel video
745 You may need to update your console settings in /etc/rc.conf,
746 most probably the keymap. During boot, /etc/rc.d/syscons will
747 indicate what you need to do.
749 vt(4) still has issues and lacks some features compared to
750 syscons(4). See the wiki for up-to-date information:
751 https://wiki.freebsd.org/Newcons
753 If you want to keep using syscons(4), you can do so by adding
754 the following line to /boot/loader.conf:
758 pjdfstest has been integrated into kyua as an opt-in test suite.
759 Please see share/doc/pjdfstest/README for more details on how to
763 gperf has been removed from the base system for architectures
764 that use clang. Ports that require gperf will obtain it from the
768 pjdfstest has been moved from tools/regression/pjdfstest to
772 At svn r271982, The default linux compat kernel ABI has been adjusted
773 to 2.6.18 in support of the linux-c6 compat ports infrastructure
774 update. If you wish to continue using the linux-f10 compat ports,
775 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
776 encouraged to update their linux-compat packages to linux-c6 during
777 their next update cycle.
780 The ofwfb driver, used to provide a graphics console on PowerPC when
781 using vt(4), no longer allows mmap() of all physical memory. This
782 will prevent Xorg on PowerPC with some ATI graphics cards from
783 initializing properly unless x11-servers/xorg-server is updated to
787 The xdev targets have been converted to using TARGET and
788 TARGET_ARCH instead of XDEV and XDEV_ARCH.
791 The default unbound configuration has been modified to address
792 issues with reverse lookups on networks that use private
793 address ranges. If you use the local_unbound service, run
794 "service local_unbound setup" as root to regenerate your
795 configuration, then "service local_unbound reload" to load the
799 The GNU texinfo and GNU info pages are not built and installed
800 anymore, WITH_INFO knob has been added to allow to built and install
802 UPDATE: see 20150102 entry on texinfo's removal
805 The GNU readline library is now an INTERNALLIB - that is, it is
806 statically linked into consumers (GDB and variants) in the base
807 system, and the shared library is no longer installed. The
808 devel/readline port is available for third party software that
812 The Itanium architecture (ia64) has been removed from the list of
813 known architectures. This is the first step in the removal of the
817 Commit r268115 has added NFSv4.1 server support, merged from
818 projects/nfsv4.1-server. Since this includes changes to the
819 internal interfaces between the NFS related modules, a full
820 build of the kernel and modules will be necessary.
821 __FreeBSD_version has been bumped.
824 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
825 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
826 which differs from the behaviour controlled by this knob.)
829 Maximal length of the serial number in CTL was increased from 16 to
830 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
831 and ctld, need to be rebuilt to work with a new kernel.
834 The libatf-c and libatf-c++ major versions were downgraded to 0 and
835 1 respectively to match the upstream numbers. They were out of
836 sync because, when they were originally added to FreeBSD, the
837 upstream versions were not respected. These libraries are private
838 and not yet built by default, so renumbering them should be a
839 non-issue. However, unclean source trees will yield broken test
840 programs once the operator executes "make delete-old-libs" after a
843 Additionally, the atf-sh binary was made private by moving it into
844 /usr/libexec/. Already-built shell test programs will keep the
845 path to the old binary so they will break after "make delete-old"
848 If you are using WITH_TESTS=yes (not the default), wipe the object
849 tree and rebuild from scratch to prevent spurious test failures.
850 This is only needed once: the misnumbered libraries and misplaced
851 binaries have been added to OptionalObsoleteFiles.inc so they will
852 be removed during a clean upgrade.
855 Clang and llvm have been upgraded to 3.4.1 release.
858 We bogusly installed src.opts.mk in /usr/share/mk. This file should
859 be removed to avoid issues in the future (and has been added to
863 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
864 past, it affected all builds that used the bsd.*.mk files. The old
865 behavior was a bug, but people may have relied upon it. To get this
866 behavior back, you can .include /etc/src.conf from /etc/make.conf
867 (which is still global and isn't changed). This also changes the
868 behavior of incremental builds inside the tree of individual
869 directories. Set MAKESYSPATH to ".../share/mk" to do that.
870 Although this has survived make universe and some upgrade scenarios,
871 other upgrade scenarios may have broken. At least one form of
872 temporary breakage was fixed with MAKESYSPATH settings for buildworld
873 as well... In cases where MAKESYSPATH isn't working with this
874 setting, you'll need to set it to the full path to your tree.
876 One side effect of all this cleaning up is that bsd.compiler.mk
877 is no longer implicitly included by bsd.own.mk. If you wish to
878 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
882 The lindev device has been removed since /dev/full has been made a
883 standard device. __FreeBSD_version has been bumped.
886 The knob WITHOUT_VI was added to the base system, which controls
887 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
888 in order to reorder files share/termcap and didn't build ex(1) as a
889 build tool, so building/installing with WITH_VI is highly advised for
890 build hosts for older releases.
892 This issue has been fixed in stable/9 and stable/10 in r277022 and
893 r276991, respectively.
896 The YES_HESIOD knob has been removed. It has been obsolete for
897 a decade. Please move to using WITH_HESIOD instead or your builds
898 will silently lack HESIOD.
901 The uart(4) driver has been changed with respect to its handling
902 of the low-level console. Previously the uart(4) driver prevented
903 any process from changing the baudrate or the CLOCAL and HUPCL
904 control flags. By removing the restrictions, operators can make
905 changes to the serial console port without having to reboot.
906 However, when getty(8) is started on the serial device that is
907 associated with the low-level console, a misconfigured terminal
908 line in /etc/ttys will now have a real impact.
909 Before upgrading the kernel, make sure that /etc/ttys has the
910 serial console device configured as 3wire without baudrate to
911 preserve the previous behaviour. E.g:
912 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
915 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
916 to improve performance. To re-enable it, if needed, run rpcbind
917 with command line option -W.
920 Switched back to the GPL dtc compiler due to updates in the upstream
921 dts files not being supported by the BSDL dtc compiler. You will need
922 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
923 may result while building dtb files during a kernel build if you fail
924 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
927 Clang and llvm have been upgraded to 3.4 release.
930 The nve(4) driver has been removed. Please use the nfe(4) driver
931 for NVIDIA nForce MCP Ethernet adapters instead.
934 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
935 This could cause certain C++ applications using shared libraries built
936 against the previous version of libc++ to crash. The incompatibility
937 has now been fixed, but any C++ applications or shared libraries built
938 between r261283 and r261801 should be recompiled.
941 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
942 capability mode support. Please note that enabling the feature in
943 kernel is still highly recommended.
946 OpenSSH is now built with sandbox support, and will use sandbox as
947 the default privilege separation method. This requires Capsicum
948 capability mode support in kernel.
951 The libelf and libdwarf libraries have been updated to newer
952 versions from upstream. Shared library version numbers for
953 these two libraries were bumped. Any ports or binaries
954 requiring these two libraries should be recompiled.
955 __FreeBSD_version is bumped to 1100006.
958 If a Makefile in a tests/ directory was auto-generating a Kyuafile
959 instead of providing an explicit one, this would prevent such
960 Makefile from providing its own Kyuafile in the future during
961 NO_CLEAN builds. This has been fixed in the Makefiles but manual
962 intervention is needed to clean an objdir if you use NO_CLEAN:
963 # find /usr/obj -name Kyuafile | xargs rm -f
966 The behavior of gss_pseudo_random() for the krb5 mechanism
967 has changed, for applications requesting a longer random string
968 than produced by the underlying enctype's pseudo-random() function.
969 In particular, the random string produced from a session key of
970 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
971 be different at the 17th octet and later, after this change.
972 The counter used in the PRF+ construction is now encoded as a
973 big-endian integer in accordance with RFC 4402.
974 __FreeBSD_version is bumped to 1100004.
977 The WITHOUT_ATF build knob has been removed and its functionality
978 has been subsumed into the more generic WITHOUT_TESTS. If you were
979 using the former to disable the build of the ATF libraries, you
980 should change your settings to use the latter.
983 The default version of mtree is nmtree which is obtained from
984 NetBSD. The output is generally the same, but may vary
985 slightly. If you found you need identical output adding
986 "-F freebsd9" to the command line should do the trick. For the
987 time being, the old mtree is available as fmtree.
990 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
991 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
992 1.1.4_8 and verify bsdyml not linked in, before running "make
994 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
996 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
999 The stable/10 branch has been created in subversion from head
1003 The rc.d/jail script has been updated to support jail(8)
1004 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1005 for per-jail configuration are automatically converted to
1006 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1007 This is transparently backward compatible. See below about some
1008 incompatibilities and rc.conf(5) manual page for more details.
1010 These variables are now deprecated in favor of jail(8) configuration
1011 file. One can use "rc.d/jail config <jname>" command to generate
1012 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1013 running the jail(8) utility. The default pathname of the
1014 configuration file is /etc/jail.conf and can be specified by
1015 using $jail_conf or $jail_<jname>_conf variables.
1017 Please note that jail_devfs_ruleset accepts an integer at
1018 this moment. Please consider to rewrite the ruleset name
1022 BIND has been removed from the base system. If all you need
1023 is a local resolver, simply enable and start the local_unbound
1024 service instead. Otherwise, several versions of BIND are
1025 available in the ports tree. The dns/bind99 port is one example.
1027 With this change, nslookup(1) and dig(1) are no longer in the base
1028 system. Users should instead use host(1) and drill(1) which are
1029 in the base system. Alternatively, nslookup and dig can
1030 be obtained by installing the dns/bind-tools port.
1033 With the addition of unbound(8), a new unbound user is now
1034 required during installworld. "mergemaster -p" can be used to
1035 add the user prior to installworld, as documented in the handbook.
1038 OpenSSH is now built with DNSSEC support, and will by default
1039 silently trust signed SSHFP records. This can be controlled with
1040 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1041 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1044 The GNU Compiler Collection and C++ standard library (libstdc++)
1045 are no longer built by default on platforms where clang is the system
1046 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1047 options in src.conf.
1050 The PROCDESC kernel option is now part of the GENERIC kernel
1051 configuration and is required for the rwhod(8) to work.
1052 If you are using custom kernel configuration, you should include
1056 The API and ABI related to the Capsicum framework was modified
1057 in backward incompatible way. The userland libraries and programs
1058 have to be recompiled to work with the new kernel. This includes the
1059 following libraries and programs, but the whole buildworld is
1060 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1061 kdump, procstat, rwho, rwhod, uniq.
1064 AES-NI intrinsic support has been added to gcc. The AES-NI module
1065 has been updated to use this support. A new gcc is required to build
1066 the aesni module on both i386 and amd64.
1069 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1070 Thus "device padlock_rng" and "device rdrand_rng" should be
1071 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1074 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1075 enables just the iconv* functionality and is now on by default.
1076 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1077 compatibility. Set WITHOUT_ICONV to build the old way.
1078 If you have been using WITH_ICONV before, you will very likely
1079 need to turn on WITH_LIBICONV_COMPAT.
1082 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1083 Illumos origin, including ZFS. If you have INVARIANTS in your
1084 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1086 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1087 locks if WITNESS option was set. Because that generated a lot of
1088 witness(9) reports and all of them were believed to be false
1089 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1090 can be used to achieve the previous behavior.
1093 Timer values in IPv6 data structures now use time_uptime instead
1094 of time_second. Although this is not a user-visible functional
1095 change, userland utilities which directly use them---ndp(8),
1096 rtadvd(8), and rtsold(8) in the base system---need to be updated
1097 to r253970 or later.
1100 find -delete can now delete the pathnames given as arguments,
1101 instead of only files found below them or if the pathname did
1102 not contain any slashes. Formerly, the following error message
1105 find: -delete: <path>: relative path potentially not safe
1107 Deleting the pathnames given as arguments can be prevented
1108 without error messages using -mindepth 1 or by changing
1109 directory and passing "." as argument to find. This works in the
1110 old as well as the new version of find.
1113 Behavior of devfs rules path matching has been changed.
1114 Pattern is now always matched against fully qualified devfs
1115 path and slash characters must be explicitly matched by
1116 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1117 subdirectories must be reviewed.
1120 The default ARM ABI has changed to the ARM EABI. The old ABI is
1121 incompatible with the ARM EABI and all programs and modules will
1122 need to be rebuilt to work with a new kernel.
1124 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1126 NOTE: Support for the old ABI will be removed in the future and
1127 users are advised to upgrade.
1130 pkg_install has been disconnected from the build if you really need it
1131 you should add WITH_PKGTOOLS in your src.conf(5).
1134 Most of network statistics structures were changed to be able
1135 keep 64-bits counters. Thus all tools, that work with networking
1136 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1139 Fix a bug that allowed a tracing process (e.g. gdb) to write
1140 to a memory-mapped file in the traced process's address space
1141 even if neither the traced process nor the tracing process had
1142 write access to that file.
1145 CVS has been removed from the base system. An exact copy
1146 of the code is available from the devel/cvs port.
1149 Some people report the following error after the switch to bmake:
1151 make: illegal option -- J
1152 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1154 *** [buildworld] Error code 2
1156 this likely due to an old instance of make in
1157 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1158 which src/Makefile will use that blindly, if it exists, so if
1159 you see the above error:
1161 rm -rf `make -V MAKEPATH`
1166 Use bmake by default.
1167 Whereas before one could choose to build with bmake via
1168 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1169 make. The goal is to remove these knobs for 10-RELEASE.
1171 It is worth noting that bmake (like gmake) treats the command
1172 line as the unit of failure, rather than statements within the
1173 command line. Thus '(cd some/where && dosomething)' is safer
1174 than 'cd some/where; dosomething'. The '()' allows consistent
1175 behavior in parallel build.
1178 Fix a bug that allows NFS clients to issue READDIR on files.
1181 The WITHOUT_IDEA option has been removed because
1182 the IDEA patent expired.
1185 The sysctl which controls TRIM support under ZFS has been renamed
1186 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1190 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1191 rather than creating it's own in the temporary directory in
1192 order allow access to bootstrapped versions of tools such as
1193 install and mtree. When upgrading from version of FreeBSD where
1194 the install command does not support -l, you will need to
1195 install a new mergemaster command if mergemaster -p is required.
1196 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1200 Legacy ATA stack, disabled and replaced by new CAM-based one since
1201 FreeBSD 9.0, completely removed from the sources. Kernel modules
1202 atadisk and atapi*, user-level tools atacontrol and burncd are
1203 removed. Kernel option `options ATA_CAM` is now permanently enabled
1207 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1208 and socketpair(2). Software, in particular Kerberos, may
1209 automatically detect and use these during building. The resulting
1210 binaries will not work on older kernels.
1213 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1214 information, see the respective 20130304 entry).
1217 Recent commits to callout(9) changed the size of struct callout,
1218 so the KBI is probably heavily disturbed. Also, some functions
1219 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1220 by macros. Every kernel module using it won't load, so rebuild
1223 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1224 but does not initialize by default (because of the new CTL_DISABLE
1225 option) to save memory. To re-enable it, remove the CTL_DISABLE
1226 option from the kernel config file or set kern.cam.ctl.disable=0
1227 in /boot/loader.conf.
1230 The ctl device has been disabled in GENERIC for i386 and amd64.
1231 This was done due to the extra memory being allocated at system
1232 initialisation time by the ctl driver which was only used if
1233 a CAM target device was created. This makes a FreeBSD system
1234 unusable on 128MB or less of RAM.
1237 A new compression method (lz4) has been merged to -HEAD. Please
1238 refer to zpool-features(7) for more information.
1240 Please refer to the "ZFS notes" section of this file for information
1241 on upgrading boot ZFS pools.
1244 A BSD-licensed patch(1) variant has been added and is installed
1245 as bsdpatch, being the GNU version the default patch.
1246 To inverse the logic and use the BSD-licensed one as default,
1247 while having the GNU version installed as gnupatch, rebuild
1248 and install world with the WITH_BSD_PATCH knob set.
1251 Due to the use of the new -l option to install(1) during build
1252 and install, you must take care not to directly set the INSTALL
1253 make variable in your /etc/make.conf, /etc/src.conf, or on the
1254 command line. If you wish to use the -C flag for all installs
1255 you may be able to add INSTALL+=-C to /etc/make.conf or
1259 The install(1) option -M has changed meaning and now takes an
1260 argument that is a file or path to append logs to. In the
1261 unlikely event that -M was the last option on the command line
1262 and the command line contained at least two files and a target
1263 directory the first file will have logs appended to it. The -M
1264 option served little practical purpose in the last decade so its
1265 use is expected to be extremely rare.
1268 After switching to Clang as the default compiler some users of ZFS
1269 on i386 systems started to experience stack overflow kernel panics.
1270 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1273 GEOM_LABEL now mangles label names read from file system metadata.
1274 Mangling affect labels containing spaces, non-printable characters,
1275 '%' or '"'. Device names in /etc/fstab and other places may need to
1279 By default, only the 10 most recent kernel dumps will be saved. To
1280 restore the previous behaviour (no limit on the number of kernel dumps
1281 stored in the dump directory) add the following line to /etc/rc.conf:
1286 With the addition of auditdistd(8), a new auditdistd user is now
1287 required during installworld. "mergemaster -p" can be used to
1288 add the user prior to installworld, as documented in the handbook.
1291 The sin6_scope_id member variable in struct sockaddr_in6 is now
1292 filled by the kernel before passing the structure to the userland via
1293 sysctl or routing socket. This means the KAME-specific embedded scope
1294 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1295 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1296 __FreeBSD_version is bumped to 1000025.
1299 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1300 This means that the world and kernel will be compiled with clang
1301 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1302 and /usr/bin/cpp. To disable this behavior and revert to building
1303 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1304 of current may need to bootstrap WITHOUT_CLANG first if the clang
1305 build fails (its compatibility window doesn't extend to the 9 stable
1309 The IPFIREWALL_FORWARD kernel option has been removed. Its
1310 functionality now turned on by default.
1313 The ZERO_COPY_SOCKET kernel option has been removed and
1314 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1315 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1316 mechanism which is not safe and may result in kernel crashes.
1317 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1318 driver supports disposeable external page sized mbuf storage.
1319 Proper replacements for both zero-copy mechanisms are under
1320 consideration and will eventually lead to complete removal
1321 of the two kernel options.
1324 The IPv4 network stack has been converted to network byte
1325 order. The following modules need to be recompiled together
1326 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1327 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1330 Support for non-MPSAFE filesystems was removed from VFS. The
1331 VFS_VERSION was bumped, all filesystem modules shall be
1335 All the non-MPSAFE filesystems have been disconnected from
1336 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1337 portalfs, smbfs, xfs.
1340 The interface cloning API and ABI has changed. The following
1341 modules need to be recompiled together with kernel:
1342 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1343 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1344 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1347 The sdhci driver was split in two parts: sdhci (generic SD Host
1348 Controller logic) and sdhci_pci (actual hardware driver).
1349 No kernel config modifications are required, but if you
1350 load sdhc as a module you must switch to sdhci_pci instead.
1353 Import the FUSE kernel and userland support into base system.
1356 The GNU sort(1) program has been removed since the BSD-licensed
1357 sort(1) has been the default for quite some time and no serious
1358 problems have been reported. The corresponding WITH_GNU_SORT
1362 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1363 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1367 The net80211(4) ABI has been changed to allow for improved driver
1368 PS-POLL and power-save support. All wireless drivers need to be
1369 recompiled to work with the new kernel.
1372 The random(4) support for the VIA hardware random number
1373 generator (`PADLOCK') is no longer enabled unconditionally.
1374 Add the padlock_rng device in the custom kernel config if
1375 needed. The GENERIC kernels on i386 and amd64 do include the
1376 device, so the change only affects the custom kernel
1380 The pf(4) packet filter ABI has been changed. pfctl(8) and
1381 snmp_pf module need to be recompiled to work with new kernel.
1384 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1385 to -HEAD. Pools that have empty_bpobj in active state can not be
1386 imported read-write with ZFS implementations that do not support
1387 this feature. For more information read the zpool-features(5)
1391 The sparc64 ZFS loader has been changed to no longer try to auto-
1392 detect ZFS providers based on diskN aliases but now requires these
1393 to be explicitly listed in the OFW boot-device environment variable.
1396 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1397 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1398 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1401 The following sysctls and tunables have been renamed for consistency
1402 with other variables:
1403 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1404 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1407 The sort utility has been replaced with BSD sort. For now, GNU sort
1408 is also available as "gnusort" or the default can be set back to
1409 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1410 installed as "bsdsort".
1413 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1414 Starting with this version the old system of ZFS pool versioning
1415 is superseded by "feature flags". This concept enables forward
1416 compatibility against certain future changes in functionality of ZFS
1417 pools. The first read-only compatible "feature flag" for ZFS pools
1418 is named "com.delphix:async_destroy". For more information
1419 read the new zpool-features(5) manual page.
1420 Please refer to the "ZFS notes" section of this file for information
1421 on upgrading boot ZFS pools.
1424 The malloc(3) implementation embedded in libc now uses sources imported
1425 as contrib/jemalloc. The most disruptive API change is to
1426 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1427 delete it prior to installworld, and optionally re-create it using the
1428 new format after rebooting. See malloc.conf(5) for details
1429 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1433 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1434 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1435 now spelled mips. This is to aid compatibility with third-party
1436 software that expects this naming scheme in uname(3). Little-endian
1437 settings are unchanged. If you are updating a big-endian mips64 machine
1438 from before this change, you may need to set MACHINE_ARCH=mips64 in
1439 your environment before the new build system will recognize your machine.
1442 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1446 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1447 nullfs(5) did not pass through all behaviours to the underlying layer,
1448 as a result if we bound to a socket on the lower layer we could connect
1449 only to the lower path; if we bound to the upper layer we could connect
1450 only to the upper path. The new behavior is one can connect to both the
1451 lower and the upper paths regardless what layer path one binds to.
1454 The getifaddrs upgrade path broken with 20111215 has been restored.
1455 If you have upgraded in between 20111215 and 20120209 you need to
1456 recompile libc again with your kernel. You still need to recompile
1457 world to be able to configure CARP but this restriction already
1458 comes from 20111215.
1461 The set_rcvar() function has been removed from /etc/rc.subr. All
1462 base and ports rc.d scripts have been updated, so if you have a
1463 port installed with a script in /usr/local/etc/rc.d you can either
1464 hand-edit the rcvar= line, or reinstall the port.
1466 An easy way to handle the mass-update of /etc/rc.d:
1467 rm /etc/rc.d/* && mergemaster -i
1470 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1471 on the current CPU and prevents other threads from running.
1472 This behavior can be reverted using the kern.stop_scheduler_on_panic
1474 The new behavior can be incompatible with kern.sync_on_panic.
1477 The carp(4) facility has been changed significantly. Configuration
1478 of the CARP protocol via ifconfig(8) has changed, as well as format
1479 of CARP events submitted to devd(8) has changed. See manual pages
1480 for more information. The arpbalance feature of carp(4) is currently
1481 not supported anymore.
1483 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1484 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1485 need to be recompiled.
1488 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1492 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1493 explicitely support non-MPSAFE filesystems.
1494 It is on by default for all supported platform at this present
1498 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1499 i386 and pc98 GENERIC kernel configuration files.
1502 sysinstall has been removed
1505 The stable/9 branch created in subversion. This corresponds to the
1506 RELENG_9 branch in CVS.
1512 Avoid using make -j when upgrading. While generally safe, there are
1513 sometimes problems using -j to upgrade. If your upgrade fails with
1514 -j, please try again without -j. From time to time in the past there
1515 have been problems using -j with buildworld and/or installworld. This
1516 is especially true when upgrading between "distant" versions (eg one
1517 that cross a major release boundary or several minor releases, or when
1518 several months have passed on the -current branch).
1520 Sometimes, obscure build problems are the result of environment
1521 poisoning. This can happen because the make utility reads its
1522 environment when searching for values for global variables. To run
1523 your build attempts in an "environmental clean room", prefix all make
1524 commands with 'env -i '. See the env(1) manual page for more details.
1526 When upgrading from one major version to another it is generally best
1527 to upgrade to the latest code in the currently installed branch first,
1528 then do an upgrade to the new branch. This is the best-tested upgrade
1529 path, and has the highest probability of being successful. Please try
1530 this approach before reporting problems with a major version upgrade.
1532 When upgrading a live system, having a root shell around before
1533 installing anything can help undo problems. Not having a root shell
1534 around can lead to problems if pam has changed too much from your
1535 starting point to allow continued authentication after the upgrade.
1537 This file should be read as a log of events. When a later event changes
1538 information of a prior event, the prior event should not be deleted.
1539 Instead, a pointer to the entry with the new information should be
1540 placed in the old entry. Readers of this file should also sanity check
1541 older entries before relying on them blindly. Authors of new entries
1542 should write them with this in mind.
1546 When upgrading the boot ZFS pool to a new version, always follow
1549 1.) recompile and reinstall the ZFS boot loader and boot block
1550 (this is part of "make buildworld" and "make installworld")
1552 2.) update the ZFS boot block on your boot drive
1554 The following example updates the ZFS boot block on the first
1555 partition (freebsd-boot) of a GPT partitioned drive ada0:
1556 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1558 Non-boot pools do not need these updates.
1562 If you are updating from a prior version of FreeBSD (even one just
1563 a few days old), you should follow this procedure. It is the most
1564 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1566 make kernel-toolchain
1567 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1568 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1570 To test a kernel once
1571 ---------------------
1572 If you just want to boot a kernel once (because you are not sure
1573 if it works, or if you want to boot a known bad kernel to provide
1574 debugging information) run
1575 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1576 nextboot -k testkernel
1578 To just build a kernel when you know that it won't mess you up
1579 --------------------------------------------------------------
1580 This assumes you are already running a CURRENT system. Replace
1581 ${arch} with the architecture of your machine (e.g. "i386",
1582 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1584 cd src/sys/${arch}/conf
1585 config KERNEL_NAME_HERE
1586 cd ../compile/KERNEL_NAME_HERE
1591 If this fails, go to the "To build a kernel" section.
1593 To rebuild everything and install it on the current system.
1594 -----------------------------------------------------------
1595 # Note: sometimes if you are running current you gotta do more than
1596 # is listed here if you are upgrading from a really old current.
1598 <make sure you have good level 0 dumps>
1600 make kernel KERNCONF=YOUR_KERNEL_HERE
1602 <reboot in single user> [3]
1609 To cross-install current onto a separate partition
1610 --------------------------------------------------
1611 # In this approach we use a separate partition to hold
1612 # current's root, 'usr', and 'var' directories. A partition
1613 # holding "/", "/usr" and "/var" should be about 2GB in
1616 <make sure you have good level 0 dumps>
1619 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1620 <maybe newfs current's root partition>
1621 <mount current's root partition on directory ${CURRENT_ROOT}>
1622 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1623 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1624 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1625 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1626 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1627 <reboot into current>
1628 <do a "native" rebuild/install as described in the previous section>
1629 <maybe install compatibility libraries from ports/misc/compat*>
1633 To upgrade in-place from stable to current
1634 ----------------------------------------------
1635 <make sure you have good level 0 dumps>
1637 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1639 <reboot in single user> [3]
1646 Make sure that you've read the UPDATING file to understand the
1647 tweaks to various things you need. At this point in the life
1648 cycle of current, things change often and you are on your own
1649 to cope. The defaults can also change, so please read ALL of
1650 the UPDATING entries.
1652 Also, if you are tracking -current, you must be subscribed to
1653 freebsd-current@freebsd.org. Make sure that before you update
1654 your sources that you have read and understood all the recent
1655 messages there. If in doubt, please track -stable which has
1656 much fewer pitfalls.
1658 [1] If you have third party modules, such as vmware, you
1659 should disable them at this point so they don't crash your
1662 [3] From the bootblocks, boot -s, and then do
1667 adjkerntz -i # if CMOS is wall time
1668 Also, when doing a major release upgrade, it is required that
1669 you boot into single user mode to do the installworld.
1671 [4] Note: This step is non-optional. Failure to do this step
1672 can result in a significant reduction in the functionality of the
1673 system. Attempting to do it by hand is not recommended and those
1674 that pursue this avenue should read this file carefully, as well
1675 as the archives of freebsd-current and freebsd-hackers mailing lists
1676 for potential gotchas. The -U option is also useful to consider.
1677 See mergemaster(8) for more information.
1679 [5] Usually this step is a noop. However, from time to time
1680 you may need to do this if you get unknown user in the following
1681 step. It never hurts to do it all the time. You may need to
1682 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1683 install) after the buildworld before this step if you last updated
1684 from current before 20130425 or from -stable before 20130430.
1686 [6] This only deletes old files and directories. Old libraries
1687 can be deleted by "make delete-old-libs", but you have to make
1688 sure that no program is using those libraries anymore.
1690 [8] In order to have a kernel that can run the 4.x binaries needed to
1691 do an installworld, you must include the COMPAT_FREEBSD4 option in
1692 your kernel. Failure to do so may leave you with a system that is
1693 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1694 required to run the 5.x binaries on more recent kernels. And so on
1695 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1697 Make sure that you merge any new devices from GENERIC since the
1698 last time you updated your kernel config file.
1700 [9] When checking out sources, you must include the -P flag to have
1701 cvs prune empty directories.
1703 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1704 "?=" instead of the "=" assignment operator, so that buildworld can
1705 override the CPUTYPE if it needs to.
1707 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1708 not on the command line, or in /etc/make.conf. buildworld will
1709 warn if it is improperly defined.
1712 This file contains a list, in reverse chronological order, of major
1713 breakages in tracking -current. It is not guaranteed to be a complete
1714 list of such breakages, and only contains entries since September 23, 2011.
1715 If you need to see UPDATING entries from before that date, you will need
1716 to fetch an UPDATING file from an older FreeBSD release.
1718 Copyright information:
1720 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1722 Redistribution, publication, translation and use, with or without
1723 modification, in full or in part, in any form or format of this
1724 document are permitted without further permission from the author.
1726 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1727 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1728 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1729 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1730 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1731 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1732 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1733 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1734 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1735 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1736 POSSIBILITY OF SUCH DAMAGE.
1738 Contact Warner Losh if you have any questions about your use of