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/makeworld.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 '%I' format in the kern.corefile sysctl limits the number of
21 core files that a process can generate to the number stored in the
22 debug.ncores sysctl. The '%I' format is replaced by the single digit
23 index. Previously, if all indexes were taken the kernel would overwrite
24 only a core file with the highest index in a filename.
25 Currently the system will create a new core file if there is a free
26 index or if all slots are taken it will overwrite the oldest one.
29 WITH_OFED option now only enables the build for the OFED libraries
30 and some fundamental client utilities. OpenSM and rest of the
31 debugging tools are enabled by WITH_OFED_EXTRA build switch.
32 WITH_OFED is turned on by default on amd64.
35 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
36 6.0.1. Please see the 20141231 entry below for information about
37 prerequisites and upgrading, if you are not already using clang 3.5.0
41 The releng/11.2 branch has been created from stable/11@r334458.
44 The tz database (tzdb) has been updated to 2018e. This version more
45 correctly models time stamps in time zones with negative DST such as
46 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
47 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
48 time zone abbreviations and the tm_isdst flag.
51 The use of RSS hash from the network card aka flowid has been
52 disabled by default for lagg(4) as it's currently incompatible with
53 the lacp and loadbalance protocols.
55 This can be re-enabled by setting the following in loader.conf:
56 net.link.lagg.default_use_flowid="1"
59 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
60 6.0.0. Please see the 20141231 entry below for information about
61 prerequisites and upgrading, if you are not already using clang 3.5.0
65 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
66 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
67 to WITH/OUT_LOADER_GELI.
70 The geli password typed at boot is now hidden. To restore the previous
71 behavior, see geli(8) for configuration options.
73 The SW_WATCHDOG option is no longer necessary to enable the
74 hardclock-based software watchdog if no hardware watchdog is
75 configured. As before, SW_WATCHDOG will cause the software
76 watchdog to be enabled even if a hardware watchdog is configured.
79 lint(1) binaries and library are no longer built by default. To
80 enable building them, define WITH_LINT in src.conf. If you are using
81 a FreeBSD 12 or later system to build 11-stable, you may need to
82 install a lint(1) binary to use WITH_LINT.
85 When building multiple kernels using KERNCONF, non-existent KERNCONF
86 files will produce an error and buildkernel will fail. Previously
87 missing KERNCONF files silently failed giving no indication as to
88 why, only to subsequently discover during installkernel that the
89 desired kernel was never built in the first place.
92 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
93 Please see the 20141231 entry below for information about prerequisites
94 and upgrading, if you are not already using clang 3.5.0 or higher.
97 Since the switch to GPT disk labels, fsck for UFS/FFS has been
98 unable to automatically find alternate superblocks. As of r322806,
99 the information needed to find alternate superblocks has been
100 moved to the end of the area reserved for the boot block.
101 Filesystems created with a newfs of this vintage or later
102 will create the recovery information. If you have a filesystem
103 created prior to this change and wish to have a recovery block
104 created for your filesystem, you can do so by running fsck in
105 forground mode (i.e., do not use the -p or -y options). As it
106 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
107 to which you should answer yes.
110 The releng/11.1 branch has been created from stable/11@r320475.
113 arm64 builds now use the base system LLD 4.0.0 linker by default,
114 instead of requiring that the aarch64-binutils port or package be
115 installed. To continue using aarch64-binutils, set
116 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
119 The ctl.ko module no longer implements the iSCSI target frontend:
120 cfiscsi.ko does instead.
122 If building cfiscsi.ko as a kernel module, the module can be loaded
123 via one of the following methods:
124 - `cfiscsi_load="YES"` in loader.conf(5).
125 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
126 - ctladm(8)/ctld(8), when compiled with iSCSI support
127 (`WITH_ISCSI=yes` in src.conf(5))
129 Please see cfiscsi(4) for more details.
132 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
133 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
134 same source (previously, the dependency of mmcsd.ko on mmc.ko was
135 missing, but mmcsd.ko now will refuse to load if it is incompatible
139 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
140 use any explicitly assigned loopback address available in the jail
141 instead of using the first assigned address of the jail.
144 As of r316810 for ipfilter, keep frags is no longer assumed when
145 keep state is specified in a rule. r316810 aligns ipfilter with
146 documentation in man pages separating keep frags from keep state.
147 This allows keep state to specified without forcing keep frags
148 and allows keep frags to be specified independently of keep state.
149 To maintain previous behaviour, also specify keep frags with
150 keep state (as documented in ipf.conf.5).
153 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
154 Please see the 20141231 entry below for information about prerequisites
155 and upgrading, if you are not already using clang 3.5.0 or higher.
158 The code that provides support for ZFS .zfs/ directory functionality
159 has been reimplemented. It's not possible now to create a snapshot
160 by mkdir under .zfs/snapshot/. That should be the only user visible
164 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
165 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
166 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
167 and now NAT-T is supported by default. Security associations now use
168 the single namespace for SPI allocation, so if you use several manually
169 configured security associations with the same SPI, this configuration
173 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
174 Please see the 20141231 entry below for information about prerequisites
175 and upgrading, if you are not already using clang 3.5.0 or higher.
178 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
179 Please see the 20141231 entry below for information about prerequisites
180 and upgrading, if you are not already using clang 3.5.0 or higher.
183 The layout of the pmap structure has changed for powerpc to put the pmap
184 statistics at the front for all CPU variations. libkvm(3) and all tools
185 that link against it need to be recompiled.
188 isl(4) and cyapa(4) drivers now require a new driver,
189 chromebook_platform(4), to work properly on Chromebook-class hardware.
190 On other types of hardware the drivers may need to be configured using
191 device hints. Please see the corresponding manual pages for details.
194 Relocatable object files with the extension of .So have been renamed
195 to use an extension of .pico instead. The purpose of this change is
196 to avoid a name clash with shared libraries on case-insensitive file
197 systems. On those file systems, foo.So is the same file as foo.so.
200 The releng/11.0 branch has been created from stable/11@r303970.
203 The stable/11 branch has been created from head@r302406.
206 The libc stub for the pipe(2) system call has been replaced with
207 a wrapper that calls the pipe2(2) system call and the pipe(2)
208 system call is now only implemented by the kernels that include
209 "options COMPAT_FREEBSD10" in their config file (this is the
210 default). Users should ensure that this option is enabled in
211 their kernel or upgrade userspace to r302092 before upgrading their
215 CAM will now strip leading spaces from SCSI disks' serial numbers.
216 This will effect users who create UFS filesystems on SCSI disks using
217 those disk's diskid device nodes. For example, if /etc/fstab
218 previously contained a line like
219 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
220 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
221 transforms like gmirror may also be affected. ZFS users should
225 The bitstring(3) API has been updated with new functionality and
226 improved performance. But it is binary-incompatible with the old API.
227 Objects built with the new headers may not be linked against objects
228 built with the old headers.
231 The brk and sbrk functions have been removed from libc on arm64.
232 Binutils from ports has been updated to not link to these
233 functions and should be updated to the latest version before
234 installing a new libc.
237 The armv6 port now defaults to hard float ABI. Limited support
238 for running both hardfloat and soft float on the same system
239 is available using the libraries installed with -DWITH_LIBSOFT.
240 This has only been tested as an upgrade path for installworld
241 and packages may fail or need manual intervention to run. New
242 packages will be needed.
244 To update an existing self-hosted armv6hf system, you must add
245 TARGET_ARCH=armv6 on the make command line for both the build
246 and the install steps.
249 Kernel modules compiled outside of a kernel build now default to
250 installing to /boot/modules instead of /boot/kernel. Many kernel
251 modules built this way (such as those in ports) already overrode
252 KMODDIR explicitly to install into /boot/modules. However,
253 manually building and installing a module from /sys/modules will
254 now install to /boot/modules instead of /boot/kernel.
257 The CAM I/O scheduler has been committed to the kernel. There should be
258 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
259 list of known rogues that claim support for this but actually corrupt
260 data is believed to be complete, be on the lookout for data
261 corruption. The known rogue list is believed to be complete:
263 o Crucial MX100, M550 drives with MU01 firmware.
264 o Micron M510 and M550 drives with MU01 firmware.
265 o Micron M500 prior to MU07 firmware
266 o Samsung 830, 840, and 850 all firmwares
267 o FCCT M500 all firmwares
269 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
270 with working NCQ TRIM. For Micron branded drives, see your sales rep for
271 updated firmware. Black listed drives will work correctly because these
272 drives work correctly so long as no NCQ TRIMs are sent to them. Given
273 this list is the same as found in Linux, it's believed there are no
274 other rogues in the market place. All other models from the above
277 To be safe, if you are at all concerned, you can quirk each of your
278 drives to prevent NCQ from being sent by setting:
279 kern.cam.ada.X.quirks="0x2"
280 in loader.conf. If the drive requires the 4k sector quirk, set the
284 The FAST_DEPEND build option has been removed and its functionality is
285 now the one true way. The old mkdep(1) style of 'make depend' has
286 been removed. See 20160311 for further details.
289 Resource range types have grown from unsigned long to uintmax_t. All
290 drivers, and anything using libdevinfo, need to be recompiled.
293 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
294 builds. It no longer runs mkdep(1) during 'make depend', and the
295 'make depend' stage can safely be skipped now as it is auto ran
296 when building 'make all' and will generate all SRCS and DPSRCS before
297 building anything else. Dependencies are gathered at compile time with
298 -MF flags kept in separate .depend files per object file. Users should
299 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
303 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
304 kernel modules. Therefore, if you load any kernel modules at boot time,
305 please install the boot loaders after you install the kernel, but before
309 make kernel KERNCONF=YOUR_KERNEL_HERE
310 make -C sys/boot install
311 <reboot in single user>
313 Then follow the usual steps, described in the General Notes section,
317 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
318 see the 20141231 entry below for information about prerequisites and
319 upgrading, if you are not already using clang 3.5.0 or higher.
322 The AIO subsystem is now a standard part of the kernel. The
323 VFS_AIO kernel option and aio.ko kernel module have been removed.
324 Due to stability concerns, asynchronous I/O requests are only
325 permitted on sockets and raw disks by default. To enable
326 asynchronous I/O requests on all file types, set the
327 vfs.aio.enable_unsafe sysctl to a non-zero value.
330 The ELF object manipulation tool objcopy is now provided by the
331 ELF Tool Chain project rather than by GNU binutils. It should be a
332 drop-in replacement, with the addition of arm64 support. The
333 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
334 to obtain the GNU version if necessary.
337 Building ZFS pools on top of zvols is prohibited by default. That
338 feature has never worked safely; it's always been prone to deadlocks.
339 Using a zvol as the backing store for a VM guest's virtual disk will
340 still work, even if the guest is using ZFS. Legacy behavior can be
341 restored by setting vfs.zfs.vol.recursive=1.
344 The NONE and HPN patches has been removed from OpenSSH. They are
345 still available in the security/openssh-portable port.
348 With the addition of ypldap(8), a new _ypldap user is now required
349 during installworld. "mergemaster -p" can be used to add the user
350 prior to installworld, as documented in the handbook.
353 The tftp loader (pxeboot) now uses the option root-path directive. As a
354 consequence it no longer looks for a pxeboot.4th file on the tftp
355 server. Instead it uses the regular /boot infrastructure as with the
359 The code to start recording plug and play data into the modules has
360 been committed. While the old tools will properly build a new kernel,
361 a number of warnings about "unknown metadata record 4" will be produced
362 for an older kldxref. To avoid such warnings, make sure to rebuild
363 the kernel toolchain (or world). Make sure that you have r292078 or
364 later when trying to build 292077 or later before rebuilding.
367 Debug data files are now built by default with 'make buildworld' and
368 installed with 'make installworld'. This facilitates debugging but
369 requires more disk space both during the build and for the installed
370 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
374 r291527 changed the internal interface between the nfsd.ko and
375 nfscommon.ko modules. As such, they must both be upgraded to-gether.
376 __FreeBSD_version has been bumped because of this.
379 Add support for unicode collation strings leads to a change of
380 order of files listed by ls(1) for example. To get back to the old
381 behaviour, set LC_COLLATE environment variable to "C".
383 Databases administrators will need to reindex their databases given
384 collation results will be different.
386 Due to a bug in install(1) it is recommended to remove the ancient
387 locales before running make installworld.
389 rm -rf /usr/share/locale/*
392 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
393 libcrypto.so.7 or libssl.so.7 must be recompiled.
396 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
397 Kernel modules isp_2400_multi and isp_2500_multi were removed and
398 should be replaced with isp_2400 and isp_2500 modules respectively.
401 The build previously allowed using 'make -n' to not recurse into
402 sub-directories while showing what commands would be executed, and
403 'make -n -n' to recursively show commands. Now 'make -n' will recurse
404 and 'make -N' will not.
407 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
408 and etcupdate will now use this file. A custom sendmail.cf is now
409 updated via this mechanism rather than via installworld. If you had
410 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
411 want to remove the exclusion or change it to "always install".
412 /etc/mail/sendmail.cf is now managed the same way regardless of
413 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
414 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
417 Compatibility shims for legacy ATA device names have been removed.
418 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
419 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
420 environment variables, /dev/ad* and /dev/ar* symbolic links.
423 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
424 Please see the 20141231 entry below for information about prerequisites
425 and upgrading, if you are not already using clang 3.5.0 or higher.
428 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
429 and renamed from .symbols to .debug. This reduces the size requirements
430 on the boot partition or file system and provides consistency with
431 userland debug files.
433 When using the supported kernel installation method the
434 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
435 as is done with /boot/kernel.
437 Developers wishing to maintain the historical behavior of installing
438 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
441 The wireless drivers had undergone changes that remove the 'parent
442 interface' from the ifconfig -l output. The rc.d network scripts
443 used to check presence of a parent interface in the list, so old
444 scripts would fail to start wireless networking. Thus, etcupdate(3)
445 or mergemaster(8) run is required after kernel update, to update your
446 rc.d scripts in /etc.
449 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
450 These configurations are now automatically interpreted as
451 'scrub fragment reassemble'.
454 Kernel-loadable modules for the random(4) device are back. To use
455 them, the kernel must have
458 options RANDOM_LOADABLE
460 kldload(8) can then be used to load random_fortuna.ko
461 or random_yarrow.ko. Please note that due to the indirect
462 function calls that the loadable modules need to provide,
463 the build-in variants will be slightly more efficient.
465 The random(4) kernel option RANDOM_DUMMY has been retired due to
466 unpopularity. It was not all that useful anyway.
469 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
470 Control over building the ELF Tool Chain tools is now provided by
471 the WITHOUT_TOOLCHAIN knob.
474 The polarity of Pulse Per Second (PPS) capture events with the
475 uart(4) driver has been corrected. Prior to this change the PPS
476 "assert" event corresponded to the trailing edge of a positive PPS
477 pulse and the "clear" event was the leading edge of the next pulse.
479 As the width of a PPS pulse in a typical GPS receiver is on the
480 order of 1 millisecond, most users will not notice any significant
481 difference with this change.
483 Anyone who has compensated for the historical polarity reversal by
484 configuring a negative offset equal to the pulse width will need to
485 remove that workaround.
488 The default group assigned to /dev/dri entries has been changed
489 from 'wheel' to 'video' with the id of '44'. If you want to have
490 access to the dri devices please add yourself to the video group
493 # pw groupmod video -m $USER
496 The menu.rc and loader.rc files will now be replaced during
497 upgrades. Please migrate local changes to menu.rc.local and
498 loader.rc.local instead.
501 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
502 strings and strip have been removed. The src.conf(5) knob
503 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
506 As ZFS requires more kernel stack pages than is the default on some
507 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
508 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
510 Please consider using 'options KSTACK_PAGES=X' where X is greater
511 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
514 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
515 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
516 default, i.e., they will not contain "::". For example, instead
517 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
518 to have a more specific match, such as different map entries for
519 IPv6:0:0 vs IPv6:0. This change requires that configuration
520 data (including maps, files, classes, custom ruleset, etc.) must
521 use the same format, so make certain such configuration data is
522 upgrading. As a very simple check search for patterns like
523 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
524 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
525 the cf option UseCompressedIPv6Addresses.
528 The default kernel entropy-processing algorithm is now
529 Fortuna, replacing Yarrow.
531 Assuming you have 'device random' in your kernel config
532 file, the configurations allow a kernel option to override
533 this default. You may choose *ONE* of:
535 options RANDOM_YARROW # Legacy /dev/random algorithm.
536 options RANDOM_DUMMY # Blocking-only driver.
538 If you have neither, you get Fortuna. For most people,
539 read no further, Fortuna will give a /dev/random that works
540 like it always used to, and the difference will be irrelevant.
542 If you remove 'device random', you get *NO* kernel-processed
543 entropy at all. This may be acceptable to folks building
544 embedded systems, but has complications. Carry on reading,
545 and it is assumed you know what you need.
547 *PLEASE* read random(4) and random(9) if you are in the
548 habit of tweaking kernel configs, and/or if you are a member
549 of the embedded community, wanting specific and not-usual
550 behaviour from your security subsystems.
552 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
553 random', you will NOT have a functioning /dev/random, and
554 many cryptographic features will not work, including SSH.
555 You may also find strange behaviour from the random(3) set
556 of library functions, in particular sranddev(3), srandomdev(3)
557 and arc4random(3). The reason for this is that the KERN_ARND
558 sysctl only returns entropy if it thinks it has some to
559 share, and with RANDOM_DUMMY or no 'device random' this
563 An additional fix for the issue described in the 20150614 sendmail
564 entry below has been been committed in revision 284717.
567 FreeBSD's old make (fmake) has been removed from the system. It is
568 available as the devel/fmake port or via pkg install fmake.
571 The fix for the issue described in the 20150614 sendmail entry
572 below has been been committed in revision 284436. The work
573 around described in that entry is no longer needed unless the
574 default setting is overridden by a confDH_PARAMETERS configuration
575 setting of '5' or pointing to a 512 bit DH parameter file.
578 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
579 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
580 and devel/kyua to version 0.20+ and adjust any calling code to work
581 with Kyuafile and kyua.
584 The import of openssl to address the FreeBSD-SA-15:10.openssl
585 security advisory includes a change which rejects handshakes
586 with DH parameters below 768 bits. sendmail releases prior
587 to 8.15.2 (not yet released), defaulted to a 512 bit
588 DH parameter setting for client connections. To work around
589 this interoperability, sendmail can be configured to use a
590 2048 bit DH parameter by:
592 1. Edit /etc/mail/`hostname`.mc
593 2. If a setting for confDH_PARAMETERS does not exist or
594 exists and is set to a string beginning with '5',
596 3. If a setting for confDH_PARAMETERS exists and is set to
597 a file path, create a new file with:
598 openssl dhparam -out /path/to/file 2048
599 4. Rebuild the .cf file:
600 cd /etc/mail/; make; make install
602 cd /etc/mail/; make restart
604 A sendmail patch is coming, at which time this file will be
608 Generation of legacy formatted entries have been disabled by default
609 in pwd_mkdb(8), as all base system consumers of the legacy formatted
610 entries were converted to use the new format by default when the new,
611 machine independent format have been added and supported since FreeBSD
614 Please see the pwd_mkdb(8) manual page for further details.
617 Clang and llvm have been upgraded to 3.6.1 release. Please see the
618 20141231 entry below for information about prerequisites and upgrading,
619 if you are not already using 3.5.0 or higher.
622 TI platform code switched to using vendor DTS files and this update
623 may break existing systems running on Beaglebone, Beaglebone Black,
626 - dtb files should be regenerated/reinstalled. Filenames are the
627 same but content is different now
628 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
629 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
630 addressing scheme is now pin 25 on /dev/gpioc3.
631 - Pandaboard: /etc/ttys should be updated, serial console device is
632 now /dev/ttyu2, not /dev/ttyu0
635 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
636 If you need the GNU extension from groff soelim(1), install groff
637 from package: pkg install groff, or via ports: textproc/groff.
640 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
641 defined in symlink(7); previously symlinks were silently ignored.
644 The const qualifier has been removed from iconv(3) to comply with
645 POSIX. The ports tree is aware of this from r384038 onwards.
648 Libraries specified by LIBADD in Makefiles must have a corresponding
649 DPADD_<lib> variable to ensure correct dependencies. This is now
650 enforced in src.libnames.mk.
653 From legacy ata(4) driver was removed support for SATA controllers
654 supported by more functional drivers ahci(4), siis(4) and mvs(4).
655 Kernel modules ataahci and ataadaptec were removed completely,
656 replaced by ahci and mvs modules respectively.
659 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
660 the 20141231 entry below for information about prerequisites and
661 upgrading, if you are not already using 3.5.0 or higher.
664 The 32-bit PowerPC kernel has been changed to a position-independent
665 executable. This can only be booted with a version of loader(8)
666 newer than January 31, 2015, so make sure to update both world and
667 kernel before rebooting.
670 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
671 but before r278950, the RNG was not seeded properly. Immediately
672 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
673 ssh keys or openssl keys) that were generated w/ a kernel from that
674 range. This does not affect programs that directly used /dev/random
675 or /dev/urandom. All userland uses of arc4random(3) are affected.
678 The autofs(4) ABI was changed in order to restore binary compatibility
679 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
683 The powerpc64 kernel has been changed to a position-independent
684 executable. This can only be booted with a new version of loader(8),
685 so make sure to update both world and kernel before rebooting.
688 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
689 only release, no new features have been added. Please see the 20141231
690 entry below for information about prerequisites and upgrading, if you
691 are not already using 3.5.0.
694 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
695 taken from the ELF Tool Chain project rather than GNU binutils. They
696 should be drop-in replacements, with the addition of arm64 support.
697 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
698 binutils tools, if necessary. See 20150805 for updated information.
701 The default Unbound configuration now enables remote control
702 using a local socket. Users who have already enabled the
703 local_unbound service should regenerate their configuration
704 by running "service local_unbound setup" as root.
707 The GNU texinfo and GNU info pages have been removed.
708 To be able to view GNU info pages please install texinfo from ports.
711 Clang, llvm and lldb have been upgraded to 3.5.0 release.
713 As of this release, a prerequisite for building clang, llvm and lldb is
714 a C++11 capable compiler and C++11 standard library. This means that to
715 be able to successfully build the cross-tools stage of buildworld, with
716 clang as the bootstrap compiler, your system compiler or cross compiler
717 should either be clang 3.3 or later, or gcc 4.8 or later, and your
718 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
721 On any standard FreeBSD 10.x or 11.x installation, where clang and
722 libc++ are on by default (that is, on x86 or arm), this should work out
725 On 9.x installations where clang is enabled by default, e.g. on x86 and
726 powerpc, libc++ will not be enabled by default, so libc++ should be
727 built (with clang) and installed first. If both clang and libc++ are
728 missing, build clang first, then use it to build libc++.
730 On 8.x and earlier installations, upgrade to 9.x first, and then follow
731 the instructions for 9.x above.
733 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
734 default, and do not build clang.
736 Many embedded systems are resource constrained, and will not be able to
737 build clang in a reasonable time, or in some cases at all. In those
738 cases, cross building bootable systems on amd64 is a workaround.
740 This new version of clang introduces a number of new warnings, of which
741 the following are most likely to appear:
745 This warns in two cases, for both C and C++:
746 * When the code is trying to take the absolute value of an unsigned
747 quantity, which is effectively a no-op, and almost never what was
748 intended. The code should be fixed, if at all possible. If you are
749 sure that the unsigned quantity can be safely cast to signed, without
750 loss of information or undefined behavior, you can add an explicit
751 cast, or disable the warning.
753 * When the code is trying to take an absolute value, but the called
754 abs() variant is for the wrong type, which can lead to truncation.
755 If you want to disable the warning instead of fixing the code, please
756 make sure that truncation will not occur, or it might lead to unwanted
759 -Wtautological-undefined-compare and
760 -Wundefined-bool-conversion
762 These warn when C++ code is trying to compare 'this' against NULL, while
763 'this' should never be NULL in well-defined C++ code. However, there is
764 some legacy (pre C++11) code out there, which actively abuses this
765 feature, which was less strictly defined in previous C++ versions.
767 Squid and openjdk do this, for example. The warning can be turned off
768 for C++98 and earlier, but compiling the code in C++11 mode might result
769 in unexpected behavior; for example, the parts of the program that are
770 unreachable could be optimized away.
773 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
774 kernel sources have been removed. The .h files remain, since some
775 utilities include them. This will need to be fixed later.
776 If "mount -t oldnfs ..." is attempted, it will fail.
777 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
778 the utilities will report errors.
781 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
782 directories to top level SUBDIR variable when their parent
783 directory is included in LOCAL_DIRS. Users with build systems with
784 such hierarchies and without SUBDIR entries in the parent
785 directory Makefiles should add them or add the directories to
789 faith(4) and faithd(8) have been removed from the base system. Faith
790 has been obsolete for a very long time.
793 vt(4), the new console driver, is enabled by default. It brings
794 support for Unicode and double-width characters, as well as
795 support for UEFI and integration with the KMS kernel video
798 You may need to update your console settings in /etc/rc.conf,
799 most probably the keymap. During boot, /etc/rc.d/syscons will
800 indicate what you need to do.
802 vt(4) still has issues and lacks some features compared to
803 syscons(4). See the wiki for up-to-date information:
804 https://wiki.freebsd.org/Newcons
806 If you want to keep using syscons(4), you can do so by adding
807 the following line to /boot/loader.conf:
811 pjdfstest has been integrated into kyua as an opt-in test suite.
812 Please see share/doc/pjdfstest/README for more details on how to
816 gperf has been removed from the base system for architectures
817 that use clang. Ports that require gperf will obtain it from the
821 pjdfstest has been moved from tools/regression/pjdfstest to
825 At svn r271982, The default linux compat kernel ABI has been adjusted
826 to 2.6.18 in support of the linux-c6 compat ports infrastructure
827 update. If you wish to continue using the linux-f10 compat ports,
828 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
829 encouraged to update their linux-compat packages to linux-c6 during
830 their next update cycle.
833 The ofwfb driver, used to provide a graphics console on PowerPC when
834 using vt(4), no longer allows mmap() of all physical memory. This
835 will prevent Xorg on PowerPC with some ATI graphics cards from
836 initializing properly unless x11-servers/xorg-server is updated to
840 The xdev targets have been converted to using TARGET and
841 TARGET_ARCH instead of XDEV and XDEV_ARCH.
844 The default unbound configuration has been modified to address
845 issues with reverse lookups on networks that use private
846 address ranges. If you use the local_unbound service, run
847 "service local_unbound setup" as root to regenerate your
848 configuration, then "service local_unbound reload" to load the
852 The GNU texinfo and GNU info pages are not built and installed
853 anymore, WITH_INFO knob has been added to allow to built and install
855 UPDATE: see 20150102 entry on texinfo's removal
858 The GNU readline library is now an INTERNALLIB - that is, it is
859 statically linked into consumers (GDB and variants) in the base
860 system, and the shared library is no longer installed. The
861 devel/readline port is available for third party software that
865 The Itanium architecture (ia64) has been removed from the list of
866 known architectures. This is the first step in the removal of the
870 Commit r268115 has added NFSv4.1 server support, merged from
871 projects/nfsv4.1-server. Since this includes changes to the
872 internal interfaces between the NFS related modules, a full
873 build of the kernel and modules will be necessary.
874 __FreeBSD_version has been bumped.
877 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
878 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
879 which differs from the behaviour controlled by this knob.)
882 Maximal length of the serial number in CTL was increased from 16 to
883 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
884 and ctld, need to be rebuilt to work with a new kernel.
887 The libatf-c and libatf-c++ major versions were downgraded to 0 and
888 1 respectively to match the upstream numbers. They were out of
889 sync because, when they were originally added to FreeBSD, the
890 upstream versions were not respected. These libraries are private
891 and not yet built by default, so renumbering them should be a
892 non-issue. However, unclean source trees will yield broken test
893 programs once the operator executes "make delete-old-libs" after a
896 Additionally, the atf-sh binary was made private by moving it into
897 /usr/libexec/. Already-built shell test programs will keep the
898 path to the old binary so they will break after "make delete-old"
901 If you are using WITH_TESTS=yes (not the default), wipe the object
902 tree and rebuild from scratch to prevent spurious test failures.
903 This is only needed once: the misnumbered libraries and misplaced
904 binaries have been added to OptionalObsoleteFiles.inc so they will
905 be removed during a clean upgrade.
908 Clang and llvm have been upgraded to 3.4.1 release.
911 We bogusly installed src.opts.mk in /usr/share/mk. This file should
912 be removed to avoid issues in the future (and has been added to
916 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
917 past, it affected all builds that used the bsd.*.mk files. The old
918 behavior was a bug, but people may have relied upon it. To get this
919 behavior back, you can .include /etc/src.conf from /etc/make.conf
920 (which is still global and isn't changed). This also changes the
921 behavior of incremental builds inside the tree of individual
922 directories. Set MAKESYSPATH to ".../share/mk" to do that.
923 Although this has survived make universe and some upgrade scenarios,
924 other upgrade scenarios may have broken. At least one form of
925 temporary breakage was fixed with MAKESYSPATH settings for buildworld
926 as well... In cases where MAKESYSPATH isn't working with this
927 setting, you'll need to set it to the full path to your tree.
929 One side effect of all this cleaning up is that bsd.compiler.mk
930 is no longer implicitly included by bsd.own.mk. If you wish to
931 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
935 The lindev device has been removed since /dev/full has been made a
936 standard device. __FreeBSD_version has been bumped.
939 The knob WITHOUT_VI was added to the base system, which controls
940 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
941 in order to reorder files share/termcap and didn't build ex(1) as a
942 build tool, so building/installing with WITH_VI is highly advised for
943 build hosts for older releases.
945 This issue has been fixed in stable/9 and stable/10 in r277022 and
946 r276991, respectively.
949 The YES_HESIOD knob has been removed. It has been obsolete for
950 a decade. Please move to using WITH_HESIOD instead or your builds
951 will silently lack HESIOD.
954 The uart(4) driver has been changed with respect to its handling
955 of the low-level console. Previously the uart(4) driver prevented
956 any process from changing the baudrate or the CLOCAL and HUPCL
957 control flags. By removing the restrictions, operators can make
958 changes to the serial console port without having to reboot.
959 However, when getty(8) is started on the serial device that is
960 associated with the low-level console, a misconfigured terminal
961 line in /etc/ttys will now have a real impact.
962 Before upgrading the kernel, make sure that /etc/ttys has the
963 serial console device configured as 3wire without baudrate to
964 preserve the previous behaviour. E.g:
965 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
968 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
969 to improve performance. To re-enable it, if needed, run rpcbind
970 with command line option -W.
973 Switched back to the GPL dtc compiler due to updates in the upstream
974 dts files not being supported by the BSDL dtc compiler. You will need
975 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
976 may result while building dtb files during a kernel build if you fail
977 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
980 Clang and llvm have been upgraded to 3.4 release.
983 The nve(4) driver has been removed. Please use the nfe(4) driver
984 for NVIDIA nForce MCP Ethernet adapters instead.
987 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
988 This could cause certain C++ applications using shared libraries built
989 against the previous version of libc++ to crash. The incompatibility
990 has now been fixed, but any C++ applications or shared libraries built
991 between r261283 and r261801 should be recompiled.
994 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
995 capability mode support. Please note that enabling the feature in
996 kernel is still highly recommended.
999 OpenSSH is now built with sandbox support, and will use sandbox as
1000 the default privilege separation method. This requires Capsicum
1001 capability mode support in kernel.
1004 The libelf and libdwarf libraries have been updated to newer
1005 versions from upstream. Shared library version numbers for
1006 these two libraries were bumped. Any ports or binaries
1007 requiring these two libraries should be recompiled.
1008 __FreeBSD_version is bumped to 1100006.
1011 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1012 instead of providing an explicit one, this would prevent such
1013 Makefile from providing its own Kyuafile in the future during
1014 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1015 intervention is needed to clean an objdir if you use NO_CLEAN:
1016 # find /usr/obj -name Kyuafile | xargs rm -f
1019 The behavior of gss_pseudo_random() for the krb5 mechanism
1020 has changed, for applications requesting a longer random string
1021 than produced by the underlying enctype's pseudo-random() function.
1022 In particular, the random string produced from a session key of
1023 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1024 be different at the 17th octet and later, after this change.
1025 The counter used in the PRF+ construction is now encoded as a
1026 big-endian integer in accordance with RFC 4402.
1027 __FreeBSD_version is bumped to 1100004.
1030 The WITHOUT_ATF build knob has been removed and its functionality
1031 has been subsumed into the more generic WITHOUT_TESTS. If you were
1032 using the former to disable the build of the ATF libraries, you
1033 should change your settings to use the latter.
1036 The default version of mtree is nmtree which is obtained from
1037 NetBSD. The output is generally the same, but may vary
1038 slightly. If you found you need identical output adding
1039 "-F freebsd9" to the command line should do the trick. For the
1040 time being, the old mtree is available as fmtree.
1043 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1044 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1045 1.1.4_8 and verify bsdyml not linked in, before running "make
1047 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1049 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1052 The stable/10 branch has been created in subversion from head
1056 The rc.d/jail script has been updated to support jail(8)
1057 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1058 for per-jail configuration are automatically converted to
1059 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1060 This is transparently backward compatible. See below about some
1061 incompatibilities and rc.conf(5) manual page for more details.
1063 These variables are now deprecated in favor of jail(8) configuration
1064 file. One can use "rc.d/jail config <jname>" command to generate
1065 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1066 running the jail(8) utility. The default pathname of the
1067 configuration file is /etc/jail.conf and can be specified by
1068 using $jail_conf or $jail_<jname>_conf variables.
1070 Please note that jail_devfs_ruleset accepts an integer at
1071 this moment. Please consider to rewrite the ruleset name
1075 BIND has been removed from the base system. If all you need
1076 is a local resolver, simply enable and start the local_unbound
1077 service instead. Otherwise, several versions of BIND are
1078 available in the ports tree. The dns/bind99 port is one example.
1080 With this change, nslookup(1) and dig(1) are no longer in the base
1081 system. Users should instead use host(1) and drill(1) which are
1082 in the base system. Alternatively, nslookup and dig can
1083 be obtained by installing the dns/bind-tools port.
1086 With the addition of unbound(8), a new unbound user is now
1087 required during installworld. "mergemaster -p" can be used to
1088 add the user prior to installworld, as documented in the handbook.
1091 OpenSSH is now built with DNSSEC support, and will by default
1092 silently trust signed SSHFP records. This can be controlled with
1093 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1094 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1097 The GNU Compiler Collection and C++ standard library (libstdc++)
1098 are no longer built by default on platforms where clang is the system
1099 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1100 options in src.conf.
1103 The PROCDESC kernel option is now part of the GENERIC kernel
1104 configuration and is required for the rwhod(8) to work.
1105 If you are using custom kernel configuration, you should include
1109 The API and ABI related to the Capsicum framework was modified
1110 in backward incompatible way. The userland libraries and programs
1111 have to be recompiled to work with the new kernel. This includes the
1112 following libraries and programs, but the whole buildworld is
1113 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1114 kdump, procstat, rwho, rwhod, uniq.
1117 AES-NI intrinsic support has been added to gcc. The AES-NI module
1118 has been updated to use this support. A new gcc is required to build
1119 the aesni module on both i386 and amd64.
1122 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1123 Thus "device padlock_rng" and "device rdrand_rng" should be
1124 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1127 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1128 enables just the iconv* functionality and is now on by default.
1129 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1130 compatibility. Set WITHOUT_ICONV to build the old way.
1131 If you have been using WITH_ICONV before, you will very likely
1132 need to turn on WITH_LIBICONV_COMPAT.
1135 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1136 Illumos origin, including ZFS. If you have INVARIANTS in your
1137 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1139 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1140 locks if WITNESS option was set. Because that generated a lot of
1141 witness(9) reports and all of them were believed to be false
1142 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1143 can be used to achieve the previous behavior.
1146 Timer values in IPv6 data structures now use time_uptime instead
1147 of time_second. Although this is not a user-visible functional
1148 change, userland utilities which directly use them---ndp(8),
1149 rtadvd(8), and rtsold(8) in the base system---need to be updated
1150 to r253970 or later.
1153 find -delete can now delete the pathnames given as arguments,
1154 instead of only files found below them or if the pathname did
1155 not contain any slashes. Formerly, the following error message
1158 find: -delete: <path>: relative path potentially not safe
1160 Deleting the pathnames given as arguments can be prevented
1161 without error messages using -mindepth 1 or by changing
1162 directory and passing "." as argument to find. This works in the
1163 old as well as the new version of find.
1166 Behavior of devfs rules path matching has been changed.
1167 Pattern is now always matched against fully qualified devfs
1168 path and slash characters must be explicitly matched by
1169 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1170 subdirectories must be reviewed.
1173 The default ARM ABI has changed to the ARM EABI. The old ABI is
1174 incompatible with the ARM EABI and all programs and modules will
1175 need to be rebuilt to work with a new kernel.
1177 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1179 NOTE: Support for the old ABI will be removed in the future and
1180 users are advised to upgrade.
1183 pkg_install has been disconnected from the build if you really need it
1184 you should add WITH_PKGTOOLS in your src.conf(5).
1187 Most of network statistics structures were changed to be able
1188 keep 64-bits counters. Thus all tools, that work with networking
1189 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1192 Fix a bug that allowed a tracing process (e.g. gdb) to write
1193 to a memory-mapped file in the traced process's address space
1194 even if neither the traced process nor the tracing process had
1195 write access to that file.
1198 CVS has been removed from the base system. An exact copy
1199 of the code is available from the devel/cvs port.
1202 Some people report the following error after the switch to bmake:
1204 make: illegal option -- J
1205 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1207 *** [buildworld] Error code 2
1209 this likely due to an old instance of make in
1210 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1211 which src/Makefile will use that blindly, if it exists, so if
1212 you see the above error:
1214 rm -rf `make -V MAKEPATH`
1219 Use bmake by default.
1220 Whereas before one could choose to build with bmake via
1221 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1222 make. The goal is to remove these knobs for 10-RELEASE.
1224 It is worth noting that bmake (like gmake) treats the command
1225 line as the unit of failure, rather than statements within the
1226 command line. Thus '(cd some/where && dosomething)' is safer
1227 than 'cd some/where; dosomething'. The '()' allows consistent
1228 behavior in parallel build.
1231 Fix a bug that allows NFS clients to issue READDIR on files.
1234 The WITHOUT_IDEA option has been removed because
1235 the IDEA patent expired.
1238 The sysctl which controls TRIM support under ZFS has been renamed
1239 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1243 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1244 rather than creating it's own in the temporary directory in
1245 order allow access to bootstrapped versions of tools such as
1246 install and mtree. When upgrading from version of FreeBSD where
1247 the install command does not support -l, you will need to
1248 install a new mergemaster command if mergemaster -p is required.
1249 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1253 Legacy ATA stack, disabled and replaced by new CAM-based one since
1254 FreeBSD 9.0, completely removed from the sources. Kernel modules
1255 atadisk and atapi*, user-level tools atacontrol and burncd are
1256 removed. Kernel option `options ATA_CAM` is now permanently enabled
1260 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1261 and socketpair(2). Software, in particular Kerberos, may
1262 automatically detect and use these during building. The resulting
1263 binaries will not work on older kernels.
1266 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1267 information, see the respective 20130304 entry).
1270 Recent commits to callout(9) changed the size of struct callout,
1271 so the KBI is probably heavily disturbed. Also, some functions
1272 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1273 by macros. Every kernel module using it won't load, so rebuild
1276 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1277 but does not initialize by default (because of the new CTL_DISABLE
1278 option) to save memory. To re-enable it, remove the CTL_DISABLE
1279 option from the kernel config file or set kern.cam.ctl.disable=0
1280 in /boot/loader.conf.
1283 The ctl device has been disabled in GENERIC for i386 and amd64.
1284 This was done due to the extra memory being allocated at system
1285 initialisation time by the ctl driver which was only used if
1286 a CAM target device was created. This makes a FreeBSD system
1287 unusable on 128MB or less of RAM.
1290 A new compression method (lz4) has been merged to -HEAD. Please
1291 refer to zpool-features(7) for more information.
1293 Please refer to the "ZFS notes" section of this file for information
1294 on upgrading boot ZFS pools.
1297 A BSD-licensed patch(1) variant has been added and is installed
1298 as bsdpatch, being the GNU version the default patch.
1299 To inverse the logic and use the BSD-licensed one as default,
1300 while having the GNU version installed as gnupatch, rebuild
1301 and install world with the WITH_BSD_PATCH knob set.
1304 Due to the use of the new -l option to install(1) during build
1305 and install, you must take care not to directly set the INSTALL
1306 make variable in your /etc/make.conf, /etc/src.conf, or on the
1307 command line. If you wish to use the -C flag for all installs
1308 you may be able to add INSTALL+=-C to /etc/make.conf or
1312 The install(1) option -M has changed meaning and now takes an
1313 argument that is a file or path to append logs to. In the
1314 unlikely event that -M was the last option on the command line
1315 and the command line contained at least two files and a target
1316 directory the first file will have logs appended to it. The -M
1317 option served little practical purpose in the last decade so its
1318 use is expected to be extremely rare.
1321 After switching to Clang as the default compiler some users of ZFS
1322 on i386 systems started to experience stack overflow kernel panics.
1323 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1326 GEOM_LABEL now mangles label names read from file system metadata.
1327 Mangling affect labels containing spaces, non-printable characters,
1328 '%' or '"'. Device names in /etc/fstab and other places may need to
1332 By default, only the 10 most recent kernel dumps will be saved. To
1333 restore the previous behaviour (no limit on the number of kernel dumps
1334 stored in the dump directory) add the following line to /etc/rc.conf:
1339 With the addition of auditdistd(8), a new auditdistd user is now
1340 required during installworld. "mergemaster -p" can be used to
1341 add the user prior to installworld, as documented in the handbook.
1344 The sin6_scope_id member variable in struct sockaddr_in6 is now
1345 filled by the kernel before passing the structure to the userland via
1346 sysctl or routing socket. This means the KAME-specific embedded scope
1347 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1348 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1349 __FreeBSD_version is bumped to 1000025.
1352 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1353 This means that the world and kernel will be compiled with clang
1354 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1355 and /usr/bin/cpp. To disable this behavior and revert to building
1356 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1357 of current may need to bootstrap WITHOUT_CLANG first if the clang
1358 build fails (its compatibility window doesn't extend to the 9 stable
1362 The IPFIREWALL_FORWARD kernel option has been removed. Its
1363 functionality now turned on by default.
1366 The ZERO_COPY_SOCKET kernel option has been removed and
1367 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1368 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1369 mechanism which is not safe and may result in kernel crashes.
1370 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1371 driver supports disposeable external page sized mbuf storage.
1372 Proper replacements for both zero-copy mechanisms are under
1373 consideration and will eventually lead to complete removal
1374 of the two kernel options.
1377 The IPv4 network stack has been converted to network byte
1378 order. The following modules need to be recompiled together
1379 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1380 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1383 Support for non-MPSAFE filesystems was removed from VFS. The
1384 VFS_VERSION was bumped, all filesystem modules shall be
1388 All the non-MPSAFE filesystems have been disconnected from
1389 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1390 portalfs, smbfs, xfs.
1393 The interface cloning API and ABI has changed. The following
1394 modules need to be recompiled together with kernel:
1395 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1396 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1397 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1400 The sdhci driver was split in two parts: sdhci (generic SD Host
1401 Controller logic) and sdhci_pci (actual hardware driver).
1402 No kernel config modifications are required, but if you
1403 load sdhc as a module you must switch to sdhci_pci instead.
1406 Import the FUSE kernel and userland support into base system.
1409 The GNU sort(1) program has been removed since the BSD-licensed
1410 sort(1) has been the default for quite some time and no serious
1411 problems have been reported. The corresponding WITH_GNU_SORT
1415 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1416 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1420 The net80211(4) ABI has been changed to allow for improved driver
1421 PS-POLL and power-save support. All wireless drivers need to be
1422 recompiled to work with the new kernel.
1425 The random(4) support for the VIA hardware random number
1426 generator (`PADLOCK') is no longer enabled unconditionally.
1427 Add the padlock_rng device in the custom kernel config if
1428 needed. The GENERIC kernels on i386 and amd64 do include the
1429 device, so the change only affects the custom kernel
1433 The pf(4) packet filter ABI has been changed. pfctl(8) and
1434 snmp_pf module need to be recompiled to work with new kernel.
1437 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1438 to -HEAD. Pools that have empty_bpobj in active state can not be
1439 imported read-write with ZFS implementations that do not support
1440 this feature. For more information read the zpool-features(5)
1444 The sparc64 ZFS loader has been changed to no longer try to auto-
1445 detect ZFS providers based on diskN aliases but now requires these
1446 to be explicitly listed in the OFW boot-device environment variable.
1449 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1450 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1451 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1454 The following sysctls and tunables have been renamed for consistency
1455 with other variables:
1456 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1457 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1460 The sort utility has been replaced with BSD sort. For now, GNU sort
1461 is also available as "gnusort" or the default can be set back to
1462 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1463 installed as "bsdsort".
1466 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1467 Starting with this version the old system of ZFS pool versioning
1468 is superseded by "feature flags". This concept enables forward
1469 compatibility against certain future changes in functionality of ZFS
1470 pools. The first read-only compatible "feature flag" for ZFS pools
1471 is named "com.delphix:async_destroy". For more information
1472 read the new zpool-features(5) manual page.
1473 Please refer to the "ZFS notes" section of this file for information
1474 on upgrading boot ZFS pools.
1477 The malloc(3) implementation embedded in libc now uses sources imported
1478 as contrib/jemalloc. The most disruptive API change is to
1479 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1480 delete it prior to installworld, and optionally re-create it using the
1481 new format after rebooting. See malloc.conf(5) for details
1482 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1486 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1487 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1488 now spelled mips. This is to aid compatibility with third-party
1489 software that expects this naming scheme in uname(3). Little-endian
1490 settings are unchanged. If you are updating a big-endian mips64 machine
1491 from before this change, you may need to set MACHINE_ARCH=mips64 in
1492 your environment before the new build system will recognize your machine.
1495 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1499 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1500 nullfs(5) did not pass through all behaviours to the underlying layer,
1501 as a result if we bound to a socket on the lower layer we could connect
1502 only to the lower path; if we bound to the upper layer we could connect
1503 only to the upper path. The new behavior is one can connect to both the
1504 lower and the upper paths regardless what layer path one binds to.
1507 The getifaddrs upgrade path broken with 20111215 has been restored.
1508 If you have upgraded in between 20111215 and 20120209 you need to
1509 recompile libc again with your kernel. You still need to recompile
1510 world to be able to configure CARP but this restriction already
1511 comes from 20111215.
1514 The set_rcvar() function has been removed from /etc/rc.subr. All
1515 base and ports rc.d scripts have been updated, so if you have a
1516 port installed with a script in /usr/local/etc/rc.d you can either
1517 hand-edit the rcvar= line, or reinstall the port.
1519 An easy way to handle the mass-update of /etc/rc.d:
1520 rm /etc/rc.d/* && mergemaster -i
1523 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1524 on the current CPU and prevents other threads from running.
1525 This behavior can be reverted using the kern.stop_scheduler_on_panic
1527 The new behavior can be incompatible with kern.sync_on_panic.
1530 The carp(4) facility has been changed significantly. Configuration
1531 of the CARP protocol via ifconfig(8) has changed, as well as format
1532 of CARP events submitted to devd(8) has changed. See manual pages
1533 for more information. The arpbalance feature of carp(4) is currently
1534 not supported anymore.
1536 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1537 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1538 need to be recompiled.
1541 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1545 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1546 explicitely support non-MPSAFE filesystems.
1547 It is on by default for all supported platform at this present
1551 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1552 i386 and pc98 GENERIC kernel configuration files.
1555 sysinstall has been removed
1558 The stable/9 branch created in subversion. This corresponds to the
1559 RELENG_9 branch in CVS.
1565 Avoid using make -j when upgrading. While generally safe, there are
1566 sometimes problems using -j to upgrade. If your upgrade fails with
1567 -j, please try again without -j. From time to time in the past there
1568 have been problems using -j with buildworld and/or installworld. This
1569 is especially true when upgrading between "distant" versions (eg one
1570 that cross a major release boundary or several minor releases, or when
1571 several months have passed on the -current branch).
1573 Sometimes, obscure build problems are the result of environment
1574 poisoning. This can happen because the make utility reads its
1575 environment when searching for values for global variables. To run
1576 your build attempts in an "environmental clean room", prefix all make
1577 commands with 'env -i '. See the env(1) manual page for more details.
1579 When upgrading from one major version to another it is generally best
1580 to upgrade to the latest code in the currently installed branch first,
1581 then do an upgrade to the new branch. This is the best-tested upgrade
1582 path, and has the highest probability of being successful. Please try
1583 this approach before reporting problems with a major version upgrade.
1585 When upgrading a live system, having a root shell around before
1586 installing anything can help undo problems. Not having a root shell
1587 around can lead to problems if pam has changed too much from your
1588 starting point to allow continued authentication after the upgrade.
1590 This file should be read as a log of events. When a later event changes
1591 information of a prior event, the prior event should not be deleted.
1592 Instead, a pointer to the entry with the new information should be
1593 placed in the old entry. Readers of this file should also sanity check
1594 older entries before relying on them blindly. Authors of new entries
1595 should write them with this in mind.
1599 When upgrading the boot ZFS pool to a new version, always follow
1602 1.) recompile and reinstall the ZFS boot loader and boot block
1603 (this is part of "make buildworld" and "make installworld")
1605 2.) update the ZFS boot block on your boot drive
1607 The following example updates the ZFS boot block on the first
1608 partition (freebsd-boot) of a GPT partitioned drive ada0:
1609 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1611 Non-boot pools do not need these updates.
1615 If you are updating from a prior version of FreeBSD (even one just
1616 a few days old), you should follow this procedure. It is the most
1617 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1619 make kernel-toolchain
1620 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1621 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1623 To test a kernel once
1624 ---------------------
1625 If you just want to boot a kernel once (because you are not sure
1626 if it works, or if you want to boot a known bad kernel to provide
1627 debugging information) run
1628 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1629 nextboot -k testkernel
1631 To just build a kernel when you know that it won't mess you up
1632 --------------------------------------------------------------
1633 This assumes you are already running a CURRENT system. Replace
1634 ${arch} with the architecture of your machine (e.g. "i386",
1635 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1637 cd src/sys/${arch}/conf
1638 config KERNEL_NAME_HERE
1639 cd ../compile/KERNEL_NAME_HERE
1644 If this fails, go to the "To build a kernel" section.
1646 To rebuild everything and install it on the current system.
1647 -----------------------------------------------------------
1648 # Note: sometimes if you are running current you gotta do more than
1649 # is listed here if you are upgrading from a really old current.
1651 <make sure you have good level 0 dumps>
1653 make kernel KERNCONF=YOUR_KERNEL_HERE
1655 <reboot in single user> [3]
1662 To cross-install current onto a separate partition
1663 --------------------------------------------------
1664 # In this approach we use a separate partition to hold
1665 # current's root, 'usr', and 'var' directories. A partition
1666 # holding "/", "/usr" and "/var" should be about 2GB in
1669 <make sure you have good level 0 dumps>
1672 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1673 <maybe newfs current's root partition>
1674 <mount current's root partition on directory ${CURRENT_ROOT}>
1675 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1676 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1677 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1678 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1679 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1680 <reboot into current>
1681 <do a "native" rebuild/install as described in the previous section>
1682 <maybe install compatibility libraries from ports/misc/compat*>
1686 To upgrade in-place from stable to current
1687 ----------------------------------------------
1688 <make sure you have good level 0 dumps>
1690 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1692 <reboot in single user> [3]
1699 Make sure that you've read the UPDATING file to understand the
1700 tweaks to various things you need. At this point in the life
1701 cycle of current, things change often and you are on your own
1702 to cope. The defaults can also change, so please read ALL of
1703 the UPDATING entries.
1705 Also, if you are tracking -current, you must be subscribed to
1706 freebsd-current@freebsd.org. Make sure that before you update
1707 your sources that you have read and understood all the recent
1708 messages there. If in doubt, please track -stable which has
1709 much fewer pitfalls.
1711 [1] If you have third party modules, such as vmware, you
1712 should disable them at this point so they don't crash your
1715 [3] From the bootblocks, boot -s, and then do
1720 adjkerntz -i # if CMOS is wall time
1721 Also, when doing a major release upgrade, it is required that
1722 you boot into single user mode to do the installworld.
1724 [4] Note: This step is non-optional. Failure to do this step
1725 can result in a significant reduction in the functionality of the
1726 system. Attempting to do it by hand is not recommended and those
1727 that pursue this avenue should read this file carefully, as well
1728 as the archives of freebsd-current and freebsd-hackers mailing lists
1729 for potential gotchas. The -U option is also useful to consider.
1730 See mergemaster(8) for more information.
1732 [5] Usually this step is a noop. However, from time to time
1733 you may need to do this if you get unknown user in the following
1734 step. It never hurts to do it all the time. You may need to
1735 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1736 install) after the buildworld before this step if you last updated
1737 from current before 20130425 or from -stable before 20130430.
1739 [6] This only deletes old files and directories. Old libraries
1740 can be deleted by "make delete-old-libs", but you have to make
1741 sure that no program is using those libraries anymore.
1743 [8] In order to have a kernel that can run the 4.x binaries needed to
1744 do an installworld, you must include the COMPAT_FREEBSD4 option in
1745 your kernel. Failure to do so may leave you with a system that is
1746 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1747 required to run the 5.x binaries on more recent kernels. And so on
1748 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1750 Make sure that you merge any new devices from GENERIC since the
1751 last time you updated your kernel config file.
1753 [9] When checking out sources, you must include the -P flag to have
1754 cvs prune empty directories.
1756 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1757 "?=" instead of the "=" assignment operator, so that buildworld can
1758 override the CPUTYPE if it needs to.
1760 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1761 not on the command line, or in /etc/make.conf. buildworld will
1762 warn if it is improperly defined.
1765 This file contains a list, in reverse chronological order, of major
1766 breakages in tracking -current. It is not guaranteed to be a complete
1767 list of such breakages, and only contains entries since September 23, 2011.
1768 If you need to see UPDATING entries from before that date, you will need
1769 to fetch an UPDATING file from an older FreeBSD release.
1771 Copyright information:
1773 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1775 Redistribution, publication, translation and use, with or without
1776 modification, in full or in part, in any form or format of this
1777 document are permitted without further permission from the author.
1779 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1780 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1781 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1782 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1783 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1784 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1785 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1786 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1787 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1788 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1789 POSSIBILITY OF SUCH DAMAGE.
1791 Contact Warner Losh if you have any questions about your use of