1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-src.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 20180912 p3 FreeBSD-SA-18:12.elf
20 FreeBSD-EN-18:08.lazyfpu
22 Fix improper elf header parsing. [SA-18:12.elf]
24 Fix regression in Lazy FPU remediation. [EN-18:08.lazyfpu]
26 20180814 p2 FreeBSD-SA-18:08.tcp [revised]
29 FreeBSD-SA-18:11.hostapd
31 Revise manual pages. [SA-18:08.tcp]
33 Fix L1 Terminal Fault (L1TF) kernel information disclosure.
36 Fix resource exhaustion in IP fragment reassembly. [SA-18:10.ip]
38 Fix unauthenticated EAPOL-Key decryption vulnerability.
41 20180806 p1 FreeBSD-SA-18:08.tcp
43 Fix resource exhaustion in TCP reassembly.
49 The tz database (tzdb) has been updated to 2018e. This version more
50 correctly models time stamps in time zones with negative DST such as
51 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
52 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
53 time zone abbreviations and the tm_isdst flag.
56 The use of RSS hash from the network card aka flowid has been
57 disabled by default for lagg(4) as it's currently incompatible with
58 the lacp and loadbalance protocols.
60 This can be re-enabled by setting the following in loader.conf:
61 net.link.lagg.default_use_flowid="1"
64 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
65 6.0.0. Please see the 20141231 entry below for information about
66 prerequisites and upgrading, if you are not already using clang 3.5.0
70 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
71 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
72 to WITH/OUT_LOADER_GELI.
75 The geli password typed at boot is now hidden. To restore the previous
76 behavior, see geli(8) for configuration options.
78 The SW_WATCHDOG option is no longer necessary to enable the
79 hardclock-based software watchdog if no hardware watchdog is
80 configured. As before, SW_WATCHDOG will cause the software
81 watchdog to be enabled even if a hardware watchdog is configured.
84 lint(1) binaries and library are no longer built by default. To
85 enable building them, define WITH_LINT in src.conf. If you are using
86 a FreeBSD 12 or later system to build 11-stable, you may need to
87 install a lint(1) binary to use WITH_LINT.
90 When building multiple kernels using KERNCONF, non-existent KERNCONF
91 files will produce an error and buildkernel will fail. Previously
92 missing KERNCONF files silently failed giving no indication as to
93 why, only to subsequently discover during installkernel that the
94 desired kernel was never built in the first place.
97 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
98 Please see the 20141231 entry below for information about prerequisites
99 and upgrading, if you are not already using clang 3.5.0 or higher.
102 Since the switch to GPT disk labels, fsck for UFS/FFS has been
103 unable to automatically find alternate superblocks. As of r322806,
104 the information needed to find alternate superblocks has been
105 moved to the end of the area reserved for the boot block.
106 Filesystems created with a newfs of this vintage or later
107 will create the recovery information. If you have a filesystem
108 created prior to this change and wish to have a recovery block
109 created for your filesystem, you can do so by running fsck in
110 forground mode (i.e., do not use the -p or -y options). As it
111 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
112 to which you should answer yes.
115 arm64 builds now use the base system LLD 4.0.0 linker by default,
116 instead of requiring that the aarch64-binutils port or package be
117 installed. To continue using aarch64-binutils, set
118 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
121 The ctl.ko module no longer implements the iSCSI target frontend:
122 cfiscsi.ko does instead.
124 If building cfiscsi.ko as a kernel module, the module can be loaded
125 via one of the following methods:
126 - `cfiscsi_load="YES"` in loader.conf(5).
127 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
128 - ctladm(8)/ctld(8), when compiled with iSCSI support
129 (`WITH_ISCSI=yes` in src.conf(5))
131 Please see cfiscsi(4) for more details.
134 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
135 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
136 same source (previously, the dependency of mmcsd.ko on mmc.ko was
137 missing, but mmcsd.ko now will refuse to load if it is incompatible
141 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
142 use any explicitly assigned loopback address available in the jail
143 instead of using the first assigned address of the jail.
146 As of r316810 for ipfilter, keep frags is no longer assumed when
147 keep state is specified in a rule. r316810 aligns ipfilter with
148 documentation in man pages separating keep frags from keep state.
149 This allows keep state to specified without forcing keep frags
150 and allows keep frags to be specified independently of keep state.
151 To maintain previous behaviour, also specify keep frags with
152 keep state (as documented in ipf.conf.5).
155 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
156 Please see the 20141231 entry below for information about prerequisites
157 and upgrading, if you are not already using clang 3.5.0 or higher.
160 The code that provides support for ZFS .zfs/ directory functionality
161 has been reimplemented. It's not possible now to create a snapshot
162 by mkdir under .zfs/snapshot/. That should be the only user visible
166 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
167 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
168 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
169 and now NAT-T is supported by default. Security associations now use
170 the single namespace for SPI allocation, so if you use several manually
171 configured security associations with the same SPI, this configuration
175 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
176 Please see the 20141231 entry below for information about prerequisites
177 and upgrading, if you are not already using clang 3.5.0 or higher.
180 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
181 Please see the 20141231 entry below for information about prerequisites
182 and upgrading, if you are not already using clang 3.5.0 or higher.
185 The layout of the pmap structure has changed for powerpc to put the pmap
186 statistics at the front for all CPU variations. libkvm(3) and all tools
187 that link against it need to be recompiled.
190 isl(4) and cyapa(4) drivers now require a new driver,
191 chromebook_platform(4), to work properly on Chromebook-class hardware.
192 On other types of hardware the drivers may need to be configured using
193 device hints. Please see the corresponding manual pages for details.
196 Relocatable object files with the extension of .So have been renamed
197 to use an extension of .pico instead. The purpose of this change is
198 to avoid a name clash with shared libraries on case-insensitive file
199 systems. On those file systems, foo.So is the same file as foo.so.
202 The libc stub for the pipe(2) system call has been replaced with
203 a wrapper that calls the pipe2(2) system call and the pipe(2)
204 system call is now only implemented by the kernels that include
205 "options COMPAT_FREEBSD10" in their config file (this is the
206 default). Users should ensure that this option is enabled in
207 their kernel or upgrade userspace to r302092 before upgrading their
211 CAM will now strip leading spaces from SCSI disks' serial numbers.
212 This will effect users who create UFS filesystems on SCSI disks using
213 those disk's diskid device nodes. For example, if /etc/fstab
214 previously contained a line like
215 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
216 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
217 transforms like gmirror may also be affected. ZFS users should
221 The bitstring(3) API has been updated with new functionality and
222 improved performance. But it is binary-incompatible with the old API.
223 Objects built with the new headers may not be linked against objects
224 built with the old headers.
227 The brk and sbrk functions have been removed from libc on arm64.
228 Binutils from ports has been updated to not link to these
229 functions and should be updated to the latest version before
230 installing a new libc.
233 The armv6 port now defaults to hard float ABI. Limited support
234 for running both hardfloat and soft float on the same system
235 is available using the libraries installed with -DWITH_LIBSOFT.
236 This has only been tested as an upgrade path for installworld
237 and packages may fail or need manual intervention to run. New
238 packages will be needed.
240 To update an existing self-hosted armv6hf system, you must add
241 TARGET_ARCH=armv6 on the make command line for both the build
242 and the install steps.
245 Kernel modules compiled outside of a kernel build now default to
246 installing to /boot/modules instead of /boot/kernel. Many kernel
247 modules built this way (such as those in ports) already overrode
248 KMODDIR explicitly to install into /boot/modules. However,
249 manually building and installing a module from /sys/modules will
250 now install to /boot/modules instead of /boot/kernel.
253 The CAM I/O scheduler has been committed to the kernel. There should be
254 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
255 list of known rogues that claim support for this but actually corrupt
256 data is believed to be complete, be on the lookout for data
257 corruption. The known rogue list is believed to be complete:
259 o Crucial MX100, M550 drives with MU01 firmware.
260 o Micron M510 and M550 drives with MU01 firmware.
261 o Micron M500 prior to MU07 firmware
262 o Samsung 830, 840, and 850 all firmwares
263 o FCCT M500 all firmwares
265 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
266 with working NCQ TRIM. For Micron branded drives, see your sales rep for
267 updated firmware. Black listed drives will work correctly because these
268 drives work correctly so long as no NCQ TRIMs are sent to them. Given
269 this list is the same as found in Linux, it's believed there are no
270 other rogues in the market place. All other models from the above
273 To be safe, if you are at all concerned, you can quirk each of your
274 drives to prevent NCQ from being sent by setting:
275 kern.cam.ada.X.quirks="0x2"
276 in loader.conf. If the drive requires the 4k sector quirk, set the
280 The FAST_DEPEND build option has been removed and its functionality is
281 now the one true way. The old mkdep(1) style of 'make depend' has
282 been removed. See 20160311 for further details.
285 Resource range types have grown from unsigned long to uintmax_t. All
286 drivers, and anything using libdevinfo, need to be recompiled.
289 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
290 builds. It no longer runs mkdep(1) during 'make depend', and the
291 'make depend' stage can safely be skipped now as it is auto ran
292 when building 'make all' and will generate all SRCS and DPSRCS before
293 building anything else. Dependencies are gathered at compile time with
294 -MF flags kept in separate .depend files per object file. Users should
295 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
299 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
300 kernel modules. Therefore, if you load any kernel modules at boot time,
301 please install the boot loaders after you install the kernel, but before
305 make kernel KERNCONF=YOUR_KERNEL_HERE
306 make -C sys/boot install
307 <reboot in single user>
309 Then follow the usual steps, described in the General Notes section,
313 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
314 see the 20141231 entry below for information about prerequisites and
315 upgrading, if you are not already using clang 3.5.0 or higher.
318 The AIO subsystem is now a standard part of the kernel. The
319 VFS_AIO kernel option and aio.ko kernel module have been removed.
320 Due to stability concerns, asynchronous I/O requests are only
321 permitted on sockets and raw disks by default. To enable
322 asynchronous I/O requests on all file types, set the
323 vfs.aio.enable_unsafe sysctl to a non-zero value.
326 The ELF object manipulation tool objcopy is now provided by the
327 ELF Tool Chain project rather than by GNU binutils. It should be a
328 drop-in replacement, with the addition of arm64 support. The
329 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
330 to obtain the GNU version if necessary.
333 Building ZFS pools on top of zvols is prohibited by default. That
334 feature has never worked safely; it's always been prone to deadlocks.
335 Using a zvol as the backing store for a VM guest's virtual disk will
336 still work, even if the guest is using ZFS. Legacy behavior can be
337 restored by setting vfs.zfs.vol.recursive=1.
340 The NONE and HPN patches has been removed from OpenSSH. They are
341 still available in the security/openssh-portable port.
344 With the addition of ypldap(8), a new _ypldap user is now required
345 during installworld. "mergemaster -p" can be used to add the user
346 prior to installworld, as documented in the handbook.
349 The tftp loader (pxeboot) now uses the option root-path directive. As a
350 consequence it no longer looks for a pxeboot.4th file on the tftp
351 server. Instead it uses the regular /boot infrastructure as with the
355 The code to start recording plug and play data into the modules has
356 been committed. While the old tools will properly build a new kernel,
357 a number of warnings about "unknown metadata record 4" will be produced
358 for an older kldxref. To avoid such warnings, make sure to rebuild
359 the kernel toolchain (or world). Make sure that you have r292078 or
360 later when trying to build 292077 or later before rebuilding.
363 Debug data files are now built by default with 'make buildworld' and
364 installed with 'make installworld'. This facilitates debugging but
365 requires more disk space both during the build and for the installed
366 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
370 r291527 changed the internal interface between the nfsd.ko and
371 nfscommon.ko modules. As such, they must both be upgraded to-gether.
372 __FreeBSD_version has been bumped because of this.
375 Add support for unicode collation strings leads to a change of
376 order of files listed by ls(1) for example. To get back to the old
377 behaviour, set LC_COLLATE environment variable to "C".
379 Databases administrators will need to reindex their databases given
380 collation results will be different.
382 Due to a bug in install(1) it is recommended to remove the ancient
383 locales before running make installworld.
385 rm -rf /usr/share/locale/*
388 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
389 libcrypto.so.7 or libssl.so.7 must be recompiled.
392 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
393 Kernel modules isp_2400_multi and isp_2500_multi were removed and
394 should be replaced with isp_2400 and isp_2500 modules respectively.
397 The build previously allowed using 'make -n' to not recurse into
398 sub-directories while showing what commands would be executed, and
399 'make -n -n' to recursively show commands. Now 'make -n' will recurse
400 and 'make -N' will not.
403 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
404 and etcupdate will now use this file. A custom sendmail.cf is now
405 updated via this mechanism rather than via installworld. If you had
406 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
407 want to remove the exclusion or change it to "always install".
408 /etc/mail/sendmail.cf is now managed the same way regardless of
409 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
410 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
413 Compatibility shims for legacy ATA device names have been removed.
414 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
415 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
416 environment variables, /dev/ad* and /dev/ar* symbolic links.
419 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
420 Please see the 20141231 entry below for information about prerequisites
421 and upgrading, if you are not already using clang 3.5.0 or higher.
424 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
425 and renamed from .symbols to .debug. This reduces the size requirements
426 on the boot partition or file system and provides consistency with
427 userland debug files.
429 When using the supported kernel installation method the
430 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
431 as is done with /boot/kernel.
433 Developers wishing to maintain the historical behavior of installing
434 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
437 The wireless drivers had undergone changes that remove the 'parent
438 interface' from the ifconfig -l output. The rc.d network scripts
439 used to check presence of a parent interface in the list, so old
440 scripts would fail to start wireless networking. Thus, etcupdate(3)
441 or mergemaster(8) run is required after kernel update, to update your
442 rc.d scripts in /etc.
445 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
446 These configurations are now automatically interpreted as
447 'scrub fragment reassemble'.
450 Kernel-loadable modules for the random(4) device are back. To use
451 them, the kernel must have
454 options RANDOM_LOADABLE
456 kldload(8) can then be used to load random_fortuna.ko
457 or random_yarrow.ko. Please note that due to the indirect
458 function calls that the loadable modules need to provide,
459 the build-in variants will be slightly more efficient.
461 The random(4) kernel option RANDOM_DUMMY has been retired due to
462 unpopularity. It was not all that useful anyway.
465 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
466 Control over building the ELF Tool Chain tools is now provided by
467 the WITHOUT_TOOLCHAIN knob.
470 The polarity of Pulse Per Second (PPS) capture events with the
471 uart(4) driver has been corrected. Prior to this change the PPS
472 "assert" event corresponded to the trailing edge of a positive PPS
473 pulse and the "clear" event was the leading edge of the next pulse.
475 As the width of a PPS pulse in a typical GPS receiver is on the
476 order of 1 millisecond, most users will not notice any significant
477 difference with this change.
479 Anyone who has compensated for the historical polarity reversal by
480 configuring a negative offset equal to the pulse width will need to
481 remove that workaround.
484 The default group assigned to /dev/dri entries has been changed
485 from 'wheel' to 'video' with the id of '44'. If you want to have
486 access to the dri devices please add yourself to the video group
489 # pw groupmod video -m $USER
492 The menu.rc and loader.rc files will now be replaced during
493 upgrades. Please migrate local changes to menu.rc.local and
494 loader.rc.local instead.
497 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
498 strings and strip have been removed. The src.conf(5) knob
499 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
502 As ZFS requires more kernel stack pages than is the default on some
503 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
504 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
506 Please consider using 'options KSTACK_PAGES=X' where X is greater
507 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
510 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
511 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
512 default, i.e., they will not contain "::". For example, instead
513 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
514 to have a more specific match, such as different map entries for
515 IPv6:0:0 vs IPv6:0. This change requires that configuration
516 data (including maps, files, classes, custom ruleset, etc.) must
517 use the same format, so make certain such configuration data is
518 upgrading. As a very simple check search for patterns like
519 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
520 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
521 the cf option UseCompressedIPv6Addresses.
524 The default kernel entropy-processing algorithm is now
525 Fortuna, replacing Yarrow.
527 Assuming you have 'device random' in your kernel config
528 file, the configurations allow a kernel option to override
529 this default. You may choose *ONE* of:
531 options RANDOM_YARROW # Legacy /dev/random algorithm.
532 options RANDOM_DUMMY # Blocking-only driver.
534 If you have neither, you get Fortuna. For most people,
535 read no further, Fortuna will give a /dev/random that works
536 like it always used to, and the difference will be irrelevant.
538 If you remove 'device random', you get *NO* kernel-processed
539 entropy at all. This may be acceptable to folks building
540 embedded systems, but has complications. Carry on reading,
541 and it is assumed you know what you need.
543 *PLEASE* read random(4) and random(9) if you are in the
544 habit of tweaking kernel configs, and/or if you are a member
545 of the embedded community, wanting specific and not-usual
546 behaviour from your security subsystems.
548 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
549 random', you will NOT have a functioning /dev/random, and
550 many cryptographic features will not work, including SSH.
551 You may also find strange behaviour from the random(3) set
552 of library functions, in particular sranddev(3), srandomdev(3)
553 and arc4random(3). The reason for this is that the KERN_ARND
554 sysctl only returns entropy if it thinks it has some to
555 share, and with RANDOM_DUMMY or no 'device random' this
559 An additional fix for the issue described in the 20150614 sendmail
560 entry below has been been committed in revision 284717.
563 FreeBSD's old make (fmake) has been removed from the system. It is
564 available as the devel/fmake port or via pkg install fmake.
567 The fix for the issue described in the 20150614 sendmail entry
568 below has been been committed in revision 284436. The work
569 around described in that entry is no longer needed unless the
570 default setting is overridden by a confDH_PARAMETERS configuration
571 setting of '5' or pointing to a 512 bit DH parameter file.
574 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
575 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
576 and devel/kyua to version 0.20+ and adjust any calling code to work
577 with Kyuafile and kyua.
580 The import of openssl to address the FreeBSD-SA-15:10.openssl
581 security advisory includes a change which rejects handshakes
582 with DH parameters below 768 bits. sendmail releases prior
583 to 8.15.2 (not yet released), defaulted to a 512 bit
584 DH parameter setting for client connections. To work around
585 this interoperability, sendmail can be configured to use a
586 2048 bit DH parameter by:
588 1. Edit /etc/mail/`hostname`.mc
589 2. If a setting for confDH_PARAMETERS does not exist or
590 exists and is set to a string beginning with '5',
592 3. If a setting for confDH_PARAMETERS exists and is set to
593 a file path, create a new file with:
594 openssl dhparam -out /path/to/file 2048
595 4. Rebuild the .cf file:
596 cd /etc/mail/; make; make install
598 cd /etc/mail/; make restart
600 A sendmail patch is coming, at which time this file will be
604 Generation of legacy formatted entries have been disabled by default
605 in pwd_mkdb(8), as all base system consumers of the legacy formatted
606 entries were converted to use the new format by default when the new,
607 machine independent format have been added and supported since FreeBSD
610 Please see the pwd_mkdb(8) manual page for further details.
613 Clang and llvm have been upgraded to 3.6.1 release. Please see the
614 20141231 entry below for information about prerequisites and upgrading,
615 if you are not already using 3.5.0 or higher.
618 TI platform code switched to using vendor DTS files and this update
619 may break existing systems running on Beaglebone, Beaglebone Black,
622 - dtb files should be regenerated/reinstalled. Filenames are the
623 same but content is different now
624 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
625 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
626 addressing scheme is now pin 25 on /dev/gpioc3.
627 - Pandaboard: /etc/ttys should be updated, serial console device is
628 now /dev/ttyu2, not /dev/ttyu0
631 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
632 If you need the GNU extension from groff soelim(1), install groff
633 from package: pkg install groff, or via ports: textproc/groff.
636 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
637 defined in symlink(7); previously symlinks were silently ignored.
640 The const qualifier has been removed from iconv(3) to comply with
641 POSIX. The ports tree is aware of this from r384038 onwards.
644 Libraries specified by LIBADD in Makefiles must have a corresponding
645 DPADD_<lib> variable to ensure correct dependencies. This is now
646 enforced in src.libnames.mk.
649 From legacy ata(4) driver was removed support for SATA controllers
650 supported by more functional drivers ahci(4), siis(4) and mvs(4).
651 Kernel modules ataahci and ataadaptec were removed completely,
652 replaced by ahci and mvs modules respectively.
655 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
656 the 20141231 entry below for information about prerequisites and
657 upgrading, if you are not already using 3.5.0 or higher.
660 The 32-bit PowerPC kernel has been changed to a position-independent
661 executable. This can only be booted with a version of loader(8)
662 newer than January 31, 2015, so make sure to update both world and
663 kernel before rebooting.
666 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
667 but before r278950, the RNG was not seeded properly. Immediately
668 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
669 ssh keys or openssl keys) that were generated w/ a kernel from that
670 range. This does not affect programs that directly used /dev/random
671 or /dev/urandom. All userland uses of arc4random(3) are affected.
674 The autofs(4) ABI was changed in order to restore binary compatibility
675 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
679 The powerpc64 kernel has been changed to a position-independent
680 executable. This can only be booted with a new version of loader(8),
681 so make sure to update both world and kernel before rebooting.
684 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
685 only release, no new features have been added. Please see the 20141231
686 entry below for information about prerequisites and upgrading, if you
687 are not already using 3.5.0.
690 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
691 taken from the ELF Tool Chain project rather than GNU binutils. They
692 should be drop-in replacements, with the addition of arm64 support.
693 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
694 binutils tools, if necessary. See 20150805 for updated information.
697 The default Unbound configuration now enables remote control
698 using a local socket. Users who have already enabled the
699 local_unbound service should regenerate their configuration
700 by running "service local_unbound setup" as root.
703 The GNU texinfo and GNU info pages have been removed.
704 To be able to view GNU info pages please install texinfo from ports.
707 Clang, llvm and lldb have been upgraded to 3.5.0 release.
709 As of this release, a prerequisite for building clang, llvm and lldb is
710 a C++11 capable compiler and C++11 standard library. This means that to
711 be able to successfully build the cross-tools stage of buildworld, with
712 clang as the bootstrap compiler, your system compiler or cross compiler
713 should either be clang 3.3 or later, or gcc 4.8 or later, and your
714 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
717 On any standard FreeBSD 10.x or 11.x installation, where clang and
718 libc++ are on by default (that is, on x86 or arm), this should work out
721 On 9.x installations where clang is enabled by default, e.g. on x86 and
722 powerpc, libc++ will not be enabled by default, so libc++ should be
723 built (with clang) and installed first. If both clang and libc++ are
724 missing, build clang first, then use it to build libc++.
726 On 8.x and earlier installations, upgrade to 9.x first, and then follow
727 the instructions for 9.x above.
729 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
730 default, and do not build clang.
732 Many embedded systems are resource constrained, and will not be able to
733 build clang in a reasonable time, or in some cases at all. In those
734 cases, cross building bootable systems on amd64 is a workaround.
736 This new version of clang introduces a number of new warnings, of which
737 the following are most likely to appear:
741 This warns in two cases, for both C and C++:
742 * When the code is trying to take the absolute value of an unsigned
743 quantity, which is effectively a no-op, and almost never what was
744 intended. The code should be fixed, if at all possible. If you are
745 sure that the unsigned quantity can be safely cast to signed, without
746 loss of information or undefined behavior, you can add an explicit
747 cast, or disable the warning.
749 * When the code is trying to take an absolute value, but the called
750 abs() variant is for the wrong type, which can lead to truncation.
751 If you want to disable the warning instead of fixing the code, please
752 make sure that truncation will not occur, or it might lead to unwanted
755 -Wtautological-undefined-compare and
756 -Wundefined-bool-conversion
758 These warn when C++ code is trying to compare 'this' against NULL, while
759 'this' should never be NULL in well-defined C++ code. However, there is
760 some legacy (pre C++11) code out there, which actively abuses this
761 feature, which was less strictly defined in previous C++ versions.
763 Squid and openjdk do this, for example. The warning can be turned off
764 for C++98 and earlier, but compiling the code in C++11 mode might result
765 in unexpected behavior; for example, the parts of the program that are
766 unreachable could be optimized away.
769 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
770 kernel sources have been removed. The .h files remain, since some
771 utilities include them. This will need to be fixed later.
772 If "mount -t oldnfs ..." is attempted, it will fail.
773 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
774 the utilities will report errors.
777 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
778 directories to top level SUBDIR variable when their parent
779 directory is included in LOCAL_DIRS. Users with build systems with
780 such hierarchies and without SUBDIR entries in the parent
781 directory Makefiles should add them or add the directories to
785 faith(4) and faithd(8) have been removed from the base system. Faith
786 has been obsolete for a very long time.
789 vt(4), the new console driver, is enabled by default. It brings
790 support for Unicode and double-width characters, as well as
791 support for UEFI and integration with the KMS kernel video
794 You may need to update your console settings in /etc/rc.conf,
795 most probably the keymap. During boot, /etc/rc.d/syscons will
796 indicate what you need to do.
798 vt(4) still has issues and lacks some features compared to
799 syscons(4). See the wiki for up-to-date information:
800 https://wiki.freebsd.org/Newcons
802 If you want to keep using syscons(4), you can do so by adding
803 the following line to /boot/loader.conf:
807 pjdfstest has been integrated into kyua as an opt-in test suite.
808 Please see share/doc/pjdfstest/README for more details on how to
812 gperf has been removed from the base system for architectures
813 that use clang. Ports that require gperf will obtain it from the
817 pjdfstest has been moved from tools/regression/pjdfstest to
821 At svn r271982, The default linux compat kernel ABI has been adjusted
822 to 2.6.18 in support of the linux-c6 compat ports infrastructure
823 update. If you wish to continue using the linux-f10 compat ports,
824 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
825 encouraged to update their linux-compat packages to linux-c6 during
826 their next update cycle.
829 The ofwfb driver, used to provide a graphics console on PowerPC when
830 using vt(4), no longer allows mmap() of all physical memory. This
831 will prevent Xorg on PowerPC with some ATI graphics cards from
832 initializing properly unless x11-servers/xorg-server is updated to
836 The xdev targets have been converted to using TARGET and
837 TARGET_ARCH instead of XDEV and XDEV_ARCH.
840 The default unbound configuration has been modified to address
841 issues with reverse lookups on networks that use private
842 address ranges. If you use the local_unbound service, run
843 "service local_unbound setup" as root to regenerate your
844 configuration, then "service local_unbound reload" to load the
848 The GNU texinfo and GNU info pages are not built and installed
849 anymore, WITH_INFO knob has been added to allow to built and install
851 UPDATE: see 20150102 entry on texinfo's removal
854 The GNU readline library is now an INTERNALLIB - that is, it is
855 statically linked into consumers (GDB and variants) in the base
856 system, and the shared library is no longer installed. The
857 devel/readline port is available for third party software that
861 The Itanium architecture (ia64) has been removed from the list of
862 known architectures. This is the first step in the removal of the
866 Commit r268115 has added NFSv4.1 server support, merged from
867 projects/nfsv4.1-server. Since this includes changes to the
868 internal interfaces between the NFS related modules, a full
869 build of the kernel and modules will be necessary.
870 __FreeBSD_version has been bumped.
873 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
874 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
875 which differs from the behaviour controlled by this knob.)
878 Maximal length of the serial number in CTL was increased from 16 to
879 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
880 and ctld, need to be rebuilt to work with a new kernel.
883 The libatf-c and libatf-c++ major versions were downgraded to 0 and
884 1 respectively to match the upstream numbers. They were out of
885 sync because, when they were originally added to FreeBSD, the
886 upstream versions were not respected. These libraries are private
887 and not yet built by default, so renumbering them should be a
888 non-issue. However, unclean source trees will yield broken test
889 programs once the operator executes "make delete-old-libs" after a
892 Additionally, the atf-sh binary was made private by moving it into
893 /usr/libexec/. Already-built shell test programs will keep the
894 path to the old binary so they will break after "make delete-old"
897 If you are using WITH_TESTS=yes (not the default), wipe the object
898 tree and rebuild from scratch to prevent spurious test failures.
899 This is only needed once: the misnumbered libraries and misplaced
900 binaries have been added to OptionalObsoleteFiles.inc so they will
901 be removed during a clean upgrade.
904 Clang and llvm have been upgraded to 3.4.1 release.
907 We bogusly installed src.opts.mk in /usr/share/mk. This file should
908 be removed to avoid issues in the future (and has been added to
912 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
913 past, it affected all builds that used the bsd.*.mk files. The old
914 behavior was a bug, but people may have relied upon it. To get this
915 behavior back, you can .include /etc/src.conf from /etc/make.conf
916 (which is still global and isn't changed). This also changes the
917 behavior of incremental builds inside the tree of individual
918 directories. Set MAKESYSPATH to ".../share/mk" to do that.
919 Although this has survived make universe and some upgrade scenarios,
920 other upgrade scenarios may have broken. At least one form of
921 temporary breakage was fixed with MAKESYSPATH settings for buildworld
922 as well... In cases where MAKESYSPATH isn't working with this
923 setting, you'll need to set it to the full path to your tree.
925 One side effect of all this cleaning up is that bsd.compiler.mk
926 is no longer implicitly included by bsd.own.mk. If you wish to
927 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
931 The lindev device has been removed since /dev/full has been made a
932 standard device. __FreeBSD_version has been bumped.
935 The knob WITHOUT_VI was added to the base system, which controls
936 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
937 in order to reorder files share/termcap and didn't build ex(1) as a
938 build tool, so building/installing with WITH_VI is highly advised for
939 build hosts for older releases.
941 This issue has been fixed in stable/9 and stable/10 in r277022 and
942 r276991, respectively.
945 The YES_HESIOD knob has been removed. It has been obsolete for
946 a decade. Please move to using WITH_HESIOD instead or your builds
947 will silently lack HESIOD.
950 The uart(4) driver has been changed with respect to its handling
951 of the low-level console. Previously the uart(4) driver prevented
952 any process from changing the baudrate or the CLOCAL and HUPCL
953 control flags. By removing the restrictions, operators can make
954 changes to the serial console port without having to reboot.
955 However, when getty(8) is started on the serial device that is
956 associated with the low-level console, a misconfigured terminal
957 line in /etc/ttys will now have a real impact.
958 Before upgrading the kernel, make sure that /etc/ttys has the
959 serial console device configured as 3wire without baudrate to
960 preserve the previous behaviour. E.g:
961 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
964 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
965 to improve performance. To re-enable it, if needed, run rpcbind
966 with command line option -W.
969 Switched back to the GPL dtc compiler due to updates in the upstream
970 dts files not being supported by the BSDL dtc compiler. You will need
971 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
972 may result while building dtb files during a kernel build if you fail
973 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
976 Clang and llvm have been upgraded to 3.4 release.
979 The nve(4) driver has been removed. Please use the nfe(4) driver
980 for NVIDIA nForce MCP Ethernet adapters instead.
983 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
984 This could cause certain C++ applications using shared libraries built
985 against the previous version of libc++ to crash. The incompatibility
986 has now been fixed, but any C++ applications or shared libraries built
987 between r261283 and r261801 should be recompiled.
990 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
991 capability mode support. Please note that enabling the feature in
992 kernel is still highly recommended.
995 OpenSSH is now built with sandbox support, and will use sandbox as
996 the default privilege separation method. This requires Capsicum
997 capability mode support in kernel.
1000 The libelf and libdwarf libraries have been updated to newer
1001 versions from upstream. Shared library version numbers for
1002 these two libraries were bumped. Any ports or binaries
1003 requiring these two libraries should be recompiled.
1004 __FreeBSD_version is bumped to 1100006.
1007 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1008 instead of providing an explicit one, this would prevent such
1009 Makefile from providing its own Kyuafile in the future during
1010 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1011 intervention is needed to clean an objdir if you use NO_CLEAN:
1012 # find /usr/obj -name Kyuafile | xargs rm -f
1015 The behavior of gss_pseudo_random() for the krb5 mechanism
1016 has changed, for applications requesting a longer random string
1017 than produced by the underlying enctype's pseudo-random() function.
1018 In particular, the random string produced from a session key of
1019 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1020 be different at the 17th octet and later, after this change.
1021 The counter used in the PRF+ construction is now encoded as a
1022 big-endian integer in accordance with RFC 4402.
1023 __FreeBSD_version is bumped to 1100004.
1026 The WITHOUT_ATF build knob has been removed and its functionality
1027 has been subsumed into the more generic WITHOUT_TESTS. If you were
1028 using the former to disable the build of the ATF libraries, you
1029 should change your settings to use the latter.
1032 The default version of mtree is nmtree which is obtained from
1033 NetBSD. The output is generally the same, but may vary
1034 slightly. If you found you need identical output adding
1035 "-F freebsd9" to the command line should do the trick. For the
1036 time being, the old mtree is available as fmtree.
1039 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1040 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1041 1.1.4_8 and verify bsdyml not linked in, before running "make
1043 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1045 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1048 The stable/10 branch has been created in subversion from head
1052 The rc.d/jail script has been updated to support jail(8)
1053 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1054 for per-jail configuration are automatically converted to
1055 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1056 This is transparently backward compatible. See below about some
1057 incompatibilities and rc.conf(5) manual page for more details.
1059 These variables are now deprecated in favor of jail(8) configuration
1060 file. One can use "rc.d/jail config <jname>" command to generate
1061 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1062 running the jail(8) utility. The default pathname of the
1063 configuration file is /etc/jail.conf and can be specified by
1064 using $jail_conf or $jail_<jname>_conf variables.
1066 Please note that jail_devfs_ruleset accepts an integer at
1067 this moment. Please consider to rewrite the ruleset name
1071 BIND has been removed from the base system. If all you need
1072 is a local resolver, simply enable and start the local_unbound
1073 service instead. Otherwise, several versions of BIND are
1074 available in the ports tree. The dns/bind99 port is one example.
1076 With this change, nslookup(1) and dig(1) are no longer in the base
1077 system. Users should instead use host(1) and drill(1) which are
1078 in the base system. Alternatively, nslookup and dig can
1079 be obtained by installing the dns/bind-tools port.
1082 With the addition of unbound(8), a new unbound user is now
1083 required during installworld. "mergemaster -p" can be used to
1084 add the user prior to installworld, as documented in the handbook.
1087 OpenSSH is now built with DNSSEC support, and will by default
1088 silently trust signed SSHFP records. This can be controlled with
1089 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1090 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1093 The GNU Compiler Collection and C++ standard library (libstdc++)
1094 are no longer built by default on platforms where clang is the system
1095 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1096 options in src.conf.
1099 The PROCDESC kernel option is now part of the GENERIC kernel
1100 configuration and is required for the rwhod(8) to work.
1101 If you are using custom kernel configuration, you should include
1105 The API and ABI related to the Capsicum framework was modified
1106 in backward incompatible way. The userland libraries and programs
1107 have to be recompiled to work with the new kernel. This includes the
1108 following libraries and programs, but the whole buildworld is
1109 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1110 kdump, procstat, rwho, rwhod, uniq.
1113 AES-NI intrinsic support has been added to gcc. The AES-NI module
1114 has been updated to use this support. A new gcc is required to build
1115 the aesni module on both i386 and amd64.
1118 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1119 Thus "device padlock_rng" and "device rdrand_rng" should be
1120 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1123 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1124 enables just the iconv* functionality and is now on by default.
1125 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1126 compatibility. Set WITHOUT_ICONV to build the old way.
1127 If you have been using WITH_ICONV before, you will very likely
1128 need to turn on WITH_LIBICONV_COMPAT.
1131 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1132 Illumos origin, including ZFS. If you have INVARIANTS in your
1133 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1135 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1136 locks if WITNESS option was set. Because that generated a lot of
1137 witness(9) reports and all of them were believed to be false
1138 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1139 can be used to achieve the previous behavior.
1142 Timer values in IPv6 data structures now use time_uptime instead
1143 of time_second. Although this is not a user-visible functional
1144 change, userland utilities which directly use them---ndp(8),
1145 rtadvd(8), and rtsold(8) in the base system---need to be updated
1146 to r253970 or later.
1149 find -delete can now delete the pathnames given as arguments,
1150 instead of only files found below them or if the pathname did
1151 not contain any slashes. Formerly, the following error message
1154 find: -delete: <path>: relative path potentially not safe
1156 Deleting the pathnames given as arguments can be prevented
1157 without error messages using -mindepth 1 or by changing
1158 directory and passing "." as argument to find. This works in the
1159 old as well as the new version of find.
1162 Behavior of devfs rules path matching has been changed.
1163 Pattern is now always matched against fully qualified devfs
1164 path and slash characters must be explicitly matched by
1165 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1166 subdirectories must be reviewed.
1169 The default ARM ABI has changed to the ARM EABI. The old ABI is
1170 incompatible with the ARM EABI and all programs and modules will
1171 need to be rebuilt to work with a new kernel.
1173 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1175 NOTE: Support for the old ABI will be removed in the future and
1176 users are advised to upgrade.
1179 pkg_install has been disconnected from the build if you really need it
1180 you should add WITH_PKGTOOLS in your src.conf(5).
1183 Most of network statistics structures were changed to be able
1184 keep 64-bits counters. Thus all tools, that work with networking
1185 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1188 Fix a bug that allowed a tracing process (e.g. gdb) to write
1189 to a memory-mapped file in the traced process's address space
1190 even if neither the traced process nor the tracing process had
1191 write access to that file.
1194 CVS has been removed from the base system. An exact copy
1195 of the code is available from the devel/cvs port.
1198 Some people report the following error after the switch to bmake:
1200 make: illegal option -- J
1201 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1203 *** [buildworld] Error code 2
1205 this likely due to an old instance of make in
1206 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1207 which src/Makefile will use that blindly, if it exists, so if
1208 you see the above error:
1210 rm -rf `make -V MAKEPATH`
1215 Use bmake by default.
1216 Whereas before one could choose to build with bmake via
1217 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1218 make. The goal is to remove these knobs for 10-RELEASE.
1220 It is worth noting that bmake (like gmake) treats the command
1221 line as the unit of failure, rather than statements within the
1222 command line. Thus '(cd some/where && dosomething)' is safer
1223 than 'cd some/where; dosomething'. The '()' allows consistent
1224 behavior in parallel build.
1227 Fix a bug that allows NFS clients to issue READDIR on files.
1230 The WITHOUT_IDEA option has been removed because
1231 the IDEA patent expired.
1234 The sysctl which controls TRIM support under ZFS has been renamed
1235 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1239 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1240 rather than creating it's own in the temporary directory in
1241 order allow access to bootstrapped versions of tools such as
1242 install and mtree. When upgrading from version of FreeBSD where
1243 the install command does not support -l, you will need to
1244 install a new mergemaster command if mergemaster -p is required.
1245 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1249 Legacy ATA stack, disabled and replaced by new CAM-based one since
1250 FreeBSD 9.0, completely removed from the sources. Kernel modules
1251 atadisk and atapi*, user-level tools atacontrol and burncd are
1252 removed. Kernel option `options ATA_CAM` is now permanently enabled
1256 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1257 and socketpair(2). Software, in particular Kerberos, may
1258 automatically detect and use these during building. The resulting
1259 binaries will not work on older kernels.
1262 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1263 information, see the respective 20130304 entry).
1266 Recent commits to callout(9) changed the size of struct callout,
1267 so the KBI is probably heavily disturbed. Also, some functions
1268 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1269 by macros. Every kernel module using it won't load, so rebuild
1272 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1273 but does not initialize by default (because of the new CTL_DISABLE
1274 option) to save memory. To re-enable it, remove the CTL_DISABLE
1275 option from the kernel config file or set kern.cam.ctl.disable=0
1276 in /boot/loader.conf.
1279 The ctl device has been disabled in GENERIC for i386 and amd64.
1280 This was done due to the extra memory being allocated at system
1281 initialisation time by the ctl driver which was only used if
1282 a CAM target device was created. This makes a FreeBSD system
1283 unusable on 128MB or less of RAM.
1286 A new compression method (lz4) has been merged to -HEAD. Please
1287 refer to zpool-features(7) for more information.
1289 Please refer to the "ZFS notes" section of this file for information
1290 on upgrading boot ZFS pools.
1293 A BSD-licensed patch(1) variant has been added and is installed
1294 as bsdpatch, being the GNU version the default patch.
1295 To inverse the logic and use the BSD-licensed one as default,
1296 while having the GNU version installed as gnupatch, rebuild
1297 and install world with the WITH_BSD_PATCH knob set.
1300 Due to the use of the new -l option to install(1) during build
1301 and install, you must take care not to directly set the INSTALL
1302 make variable in your /etc/make.conf, /etc/src.conf, or on the
1303 command line. If you wish to use the -C flag for all installs
1304 you may be able to add INSTALL+=-C to /etc/make.conf or
1308 The install(1) option -M has changed meaning and now takes an
1309 argument that is a file or path to append logs to. In the
1310 unlikely event that -M was the last option on the command line
1311 and the command line contained at least two files and a target
1312 directory the first file will have logs appended to it. The -M
1313 option served little practical purpose in the last decade so its
1314 use is expected to be extremely rare.
1317 After switching to Clang as the default compiler some users of ZFS
1318 on i386 systems started to experience stack overflow kernel panics.
1319 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1322 GEOM_LABEL now mangles label names read from file system metadata.
1323 Mangling affect labels containing spaces, non-printable characters,
1324 '%' or '"'. Device names in /etc/fstab and other places may need to
1328 By default, only the 10 most recent kernel dumps will be saved. To
1329 restore the previous behaviour (no limit on the number of kernel dumps
1330 stored in the dump directory) add the following line to /etc/rc.conf:
1335 With the addition of auditdistd(8), a new auditdistd user is now
1336 required during installworld. "mergemaster -p" can be used to
1337 add the user prior to installworld, as documented in the handbook.
1340 The sin6_scope_id member variable in struct sockaddr_in6 is now
1341 filled by the kernel before passing the structure to the userland via
1342 sysctl or routing socket. This means the KAME-specific embedded scope
1343 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1344 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1345 __FreeBSD_version is bumped to 1000025.
1348 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1349 This means that the world and kernel will be compiled with clang
1350 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1351 and /usr/bin/cpp. To disable this behavior and revert to building
1352 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1353 of current may need to bootstrap WITHOUT_CLANG first if the clang
1354 build fails (its compatibility window doesn't extend to the 9 stable
1358 The IPFIREWALL_FORWARD kernel option has been removed. Its
1359 functionality now turned on by default.
1362 The ZERO_COPY_SOCKET kernel option has been removed and
1363 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1364 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1365 mechanism which is not safe and may result in kernel crashes.
1366 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1367 driver supports disposeable external page sized mbuf storage.
1368 Proper replacements for both zero-copy mechanisms are under
1369 consideration and will eventually lead to complete removal
1370 of the two kernel options.
1373 The IPv4 network stack has been converted to network byte
1374 order. The following modules need to be recompiled together
1375 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1376 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1379 Support for non-MPSAFE filesystems was removed from VFS. The
1380 VFS_VERSION was bumped, all filesystem modules shall be
1384 All the non-MPSAFE filesystems have been disconnected from
1385 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1386 portalfs, smbfs, xfs.
1389 The interface cloning API and ABI has changed. The following
1390 modules need to be recompiled together with kernel:
1391 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1392 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1393 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1396 The sdhci driver was split in two parts: sdhci (generic SD Host
1397 Controller logic) and sdhci_pci (actual hardware driver).
1398 No kernel config modifications are required, but if you
1399 load sdhc as a module you must switch to sdhci_pci instead.
1402 Import the FUSE kernel and userland support into base system.
1405 The GNU sort(1) program has been removed since the BSD-licensed
1406 sort(1) has been the default for quite some time and no serious
1407 problems have been reported. The corresponding WITH_GNU_SORT
1411 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1412 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1416 The net80211(4) ABI has been changed to allow for improved driver
1417 PS-POLL and power-save support. All wireless drivers need to be
1418 recompiled to work with the new kernel.
1421 The random(4) support for the VIA hardware random number
1422 generator (`PADLOCK') is no longer enabled unconditionally.
1423 Add the padlock_rng device in the custom kernel config if
1424 needed. The GENERIC kernels on i386 and amd64 do include the
1425 device, so the change only affects the custom kernel
1429 The pf(4) packet filter ABI has been changed. pfctl(8) and
1430 snmp_pf module need to be recompiled to work with new kernel.
1433 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1434 to -HEAD. Pools that have empty_bpobj in active state can not be
1435 imported read-write with ZFS implementations that do not support
1436 this feature. For more information read the zpool-features(5)
1440 The sparc64 ZFS loader has been changed to no longer try to auto-
1441 detect ZFS providers based on diskN aliases but now requires these
1442 to be explicitly listed in the OFW boot-device environment variable.
1445 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1446 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1447 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1450 The following sysctls and tunables have been renamed for consistency
1451 with other variables:
1452 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1453 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1456 The sort utility has been replaced with BSD sort. For now, GNU sort
1457 is also available as "gnusort" or the default can be set back to
1458 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1459 installed as "bsdsort".
1462 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1463 Starting with this version the old system of ZFS pool versioning
1464 is superseded by "feature flags". This concept enables forward
1465 compatibility against certain future changes in functionality of ZFS
1466 pools. The first read-only compatible "feature flag" for ZFS pools
1467 is named "com.delphix:async_destroy". For more information
1468 read the new zpool-features(5) manual page.
1469 Please refer to the "ZFS notes" section of this file for information
1470 on upgrading boot ZFS pools.
1473 The malloc(3) implementation embedded in libc now uses sources imported
1474 as contrib/jemalloc. The most disruptive API change is to
1475 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1476 delete it prior to installworld, and optionally re-create it using the
1477 new format after rebooting. See malloc.conf(5) for details
1478 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1482 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1483 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1484 now spelled mips. This is to aid compatibility with third-party
1485 software that expects this naming scheme in uname(3). Little-endian
1486 settings are unchanged. If you are updating a big-endian mips64 machine
1487 from before this change, you may need to set MACHINE_ARCH=mips64 in
1488 your environment before the new build system will recognize your machine.
1491 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1495 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1496 nullfs(5) did not pass through all behaviours to the underlying layer,
1497 as a result if we bound to a socket on the lower layer we could connect
1498 only to the lower path; if we bound to the upper layer we could connect
1499 only to the upper path. The new behavior is one can connect to both the
1500 lower and the upper paths regardless what layer path one binds to.
1503 The getifaddrs upgrade path broken with 20111215 has been restored.
1504 If you have upgraded in between 20111215 and 20120209 you need to
1505 recompile libc again with your kernel. You still need to recompile
1506 world to be able to configure CARP but this restriction already
1507 comes from 20111215.
1510 The set_rcvar() function has been removed from /etc/rc.subr. All
1511 base and ports rc.d scripts have been updated, so if you have a
1512 port installed with a script in /usr/local/etc/rc.d you can either
1513 hand-edit the rcvar= line, or reinstall the port.
1515 An easy way to handle the mass-update of /etc/rc.d:
1516 rm /etc/rc.d/* && mergemaster -i
1519 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1520 on the current CPU and prevents other threads from running.
1521 This behavior can be reverted using the kern.stop_scheduler_on_panic
1523 The new behavior can be incompatible with kern.sync_on_panic.
1526 The carp(4) facility has been changed significantly. Configuration
1527 of the CARP protocol via ifconfig(8) has changed, as well as format
1528 of CARP events submitted to devd(8) has changed. See manual pages
1529 for more information. The arpbalance feature of carp(4) is currently
1530 not supported anymore.
1532 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1533 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1534 need to be recompiled.
1537 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1541 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1542 explicitely support non-MPSAFE filesystems.
1543 It is on by default for all supported platform at this present
1547 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1548 i386 and pc98 GENERIC kernel configuration files.
1551 sysinstall has been removed
1554 The stable/9 branch created in subversion. This corresponds to the
1555 RELENG_9 branch in CVS.
1561 Avoid using make -j when upgrading. While generally safe, there are
1562 sometimes problems using -j to upgrade. If your upgrade fails with
1563 -j, please try again without -j. From time to time in the past there
1564 have been problems using -j with buildworld and/or installworld. This
1565 is especially true when upgrading between "distant" versions (eg one
1566 that cross a major release boundary or several minor releases, or when
1567 several months have passed on the -current branch).
1569 Sometimes, obscure build problems are the result of environment
1570 poisoning. This can happen because the make utility reads its
1571 environment when searching for values for global variables. To run
1572 your build attempts in an "environmental clean room", prefix all make
1573 commands with 'env -i '. See the env(1) manual page for more details.
1575 When upgrading from one major version to another it is generally best
1576 to upgrade to the latest code in the currently installed branch first,
1577 then do an upgrade to the new branch. This is the best-tested upgrade
1578 path, and has the highest probability of being successful. Please try
1579 this approach before reporting problems with a major version upgrade.
1581 When upgrading a live system, having a root shell around before
1582 installing anything can help undo problems. Not having a root shell
1583 around can lead to problems if pam has changed too much from your
1584 starting point to allow continued authentication after the upgrade.
1586 This file should be read as a log of events. When a later event changes
1587 information of a prior event, the prior event should not be deleted.
1588 Instead, a pointer to the entry with the new information should be
1589 placed in the old entry. Readers of this file should also sanity check
1590 older entries before relying on them blindly. Authors of new entries
1591 should write them with this in mind.
1595 When upgrading the boot ZFS pool to a new version, always follow
1598 1.) recompile and reinstall the ZFS boot loader and boot block
1599 (this is part of "make buildworld" and "make installworld")
1601 2.) update the ZFS boot block on your boot drive
1603 The following example updates the ZFS boot block on the first
1604 partition (freebsd-boot) of a GPT partitioned drive ada0:
1605 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1607 Non-boot pools do not need these updates.
1611 If you are updating from a prior version of FreeBSD (even one just
1612 a few days old), you should follow this procedure. It is the most
1613 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1615 make kernel-toolchain
1616 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1617 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1619 To test a kernel once
1620 ---------------------
1621 If you just want to boot a kernel once (because you are not sure
1622 if it works, or if you want to boot a known bad kernel to provide
1623 debugging information) run
1624 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1625 nextboot -k testkernel
1627 To just build a kernel when you know that it won't mess you up
1628 --------------------------------------------------------------
1629 This assumes you are already running a CURRENT system. Replace
1630 ${arch} with the architecture of your machine (e.g. "i386",
1631 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1633 cd src/sys/${arch}/conf
1634 config KERNEL_NAME_HERE
1635 cd ../compile/KERNEL_NAME_HERE
1640 If this fails, go to the "To build a kernel" section.
1642 To rebuild everything and install it on the current system.
1643 -----------------------------------------------------------
1644 # Note: sometimes if you are running current you gotta do more than
1645 # is listed here if you are upgrading from a really old current.
1647 <make sure you have good level 0 dumps>
1649 make kernel KERNCONF=YOUR_KERNEL_HERE
1651 <reboot in single user> [3]
1658 To cross-install current onto a separate partition
1659 --------------------------------------------------
1660 # In this approach we use a separate partition to hold
1661 # current's root, 'usr', and 'var' directories. A partition
1662 # holding "/", "/usr" and "/var" should be about 2GB in
1665 <make sure you have good level 0 dumps>
1668 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1669 <maybe newfs current's root partition>
1670 <mount current's root partition on directory ${CURRENT_ROOT}>
1671 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1672 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1673 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1674 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1675 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1676 <reboot into current>
1677 <do a "native" rebuild/install as described in the previous section>
1678 <maybe install compatibility libraries from ports/misc/compat*>
1682 To upgrade in-place from stable to current
1683 ----------------------------------------------
1684 <make sure you have good level 0 dumps>
1686 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1688 <reboot in single user> [3]
1695 Make sure that you've read the UPDATING file to understand the
1696 tweaks to various things you need. At this point in the life
1697 cycle of current, things change often and you are on your own
1698 to cope. The defaults can also change, so please read ALL of
1699 the UPDATING entries.
1701 Also, if you are tracking -current, you must be subscribed to
1702 freebsd-current@freebsd.org. Make sure that before you update
1703 your sources that you have read and understood all the recent
1704 messages there. If in doubt, please track -stable which has
1705 much fewer pitfalls.
1707 [1] If you have third party modules, such as vmware, you
1708 should disable them at this point so they don't crash your
1711 [3] From the bootblocks, boot -s, and then do
1716 adjkerntz -i # if CMOS is wall time
1717 Also, when doing a major release upgrade, it is required that
1718 you boot into single user mode to do the installworld.
1720 [4] Note: This step is non-optional. Failure to do this step
1721 can result in a significant reduction in the functionality of the
1722 system. Attempting to do it by hand is not recommended and those
1723 that pursue this avenue should read this file carefully, as well
1724 as the archives of freebsd-current and freebsd-hackers mailing lists
1725 for potential gotchas. The -U option is also useful to consider.
1726 See mergemaster(8) for more information.
1728 [5] Usually this step is a noop. However, from time to time
1729 you may need to do this if you get unknown user in the following
1730 step. It never hurts to do it all the time. You may need to
1731 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1732 install) after the buildworld before this step if you last updated
1733 from current before 20130425 or from -stable before 20130430.
1735 [6] This only deletes old files and directories. Old libraries
1736 can be deleted by "make delete-old-libs", but you have to make
1737 sure that no program is using those libraries anymore.
1739 [8] In order to have a kernel that can run the 4.x binaries needed to
1740 do an installworld, you must include the COMPAT_FREEBSD4 option in
1741 your kernel. Failure to do so may leave you with a system that is
1742 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1743 required to run the 5.x binaries on more recent kernels. And so on
1744 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1746 Make sure that you merge any new devices from GENERIC since the
1747 last time you updated your kernel config file.
1749 [9] When checking out sources, you must include the -P flag to have
1750 cvs prune empty directories.
1752 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1753 "?=" instead of the "=" assignment operator, so that buildworld can
1754 override the CPUTYPE if it needs to.
1756 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1757 not on the command line, or in /etc/make.conf. buildworld will
1758 warn if it is improperly defined.
1761 This file contains a list, in reverse chronological order, of major
1762 breakages in tracking -current. It is not guaranteed to be a complete
1763 list of such breakages, and only contains entries since September 23, 2011.
1764 If you need to see UPDATING entries from before that date, you will need
1765 to fetch an UPDATING file from an older FreeBSD release.
1767 Copyright information:
1769 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1771 Redistribution, publication, translation and use, with or without
1772 modification, in full or in part, in any form or format of this
1773 document are permitted without further permission from the author.
1775 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1776 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1777 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1778 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1779 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1780 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1781 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1782 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1783 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1784 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1785 POSSIBILITY OF SUCH DAMAGE.
1787 Contact Warner Losh if you have any questions about your use of