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