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 20190109 p8 FreeBSD-EN-19:03.sqlite
20 FreeBSD-EN-19:04.tzdata
21 FreeBSD-EN-19:05.kqueue
23 Update sqlite3-3.20.0 --> sqlite3-3.26.0 (3260000) [EN-19:03.sqlite]
25 Import tzdata 2018h, 2018i [EN-19:04.tzdata]
27 Avoid unsynchronized updates to kn_status. [EN-19:05.kqueue]
30 20181219 p7 FreeBSD-SA-18:15.bootpd
31 FreeBSD-EN-18:16.ptrace
35 bootpd: validate hardware type [SA-18:15.bootpd]
37 Only clear a pending thread event if one is pending. [EN-18:16.ptrace]
39 Update the free page count when blacklisting pages. [EN-18:17.vm]
41 Resolve a hang in ZFS during vnode reclamation [EN-18:18.zfs]
44 20181204 p6 FreeBSD-SA-18:14.bhyve
46 Fix insufficient bounds checking in bhyve(8) device model.
49 20181127 p5 FreeBSD-SA-18:13.nfs
51 FreeBSD-EN-18:14.tzdata
52 FreeBSD-EN-18:15.loader
54 Fix multiple vulnerabilities in NFS server code. [SA-18:13.nfs]
56 Fix ICMP buffer underwrite. [EN-18:13.icmp]
58 Timezone database information update. [EN-18:14.tzdata]
60 Fix deferred kernel loading breaks loader password. [EN-18:15.loader]
62 20180927 p4 FreeBSD-EN-18:09.ip
63 FreeBSD-EN-18:10.syscall
64 FreeBSD-EN-18:11.listen
67 Fix regression in IPv6 fragment reassembly. [EN-18:09.ip]
69 Fix NULL pointer dereference in freebsd4_getfsstat. [EN-18:10.syscall]
71 Fix DoS in listen syscall over IPv6 socket. [EN-18:11.listen]
73 Fix small kernel memory disclosures. [EN-18:12.mem]
75 20180912 p3 FreeBSD-SA-18:12.elf
76 FreeBSD-EN-18:08.lazyfpu
78 Fix improper elf header parsing. [SA-18:12.elf]
80 Fix regression in Lazy FPU remediation. [EN-18:08.lazyfpu]
82 20180814 p2 FreeBSD-SA-18:08.tcp [revised]
85 FreeBSD-SA-18:11.hostapd
87 Revise manual pages. [SA-18:08.tcp]
89 Fix L1 Terminal Fault (L1TF) kernel information disclosure.
92 Fix resource exhaustion in IP fragment reassembly. [SA-18:10.ip]
94 Fix unauthenticated EAPOL-Key decryption vulnerability.
97 20180806 p1 FreeBSD-SA-18:08.tcp
99 Fix resource exhaustion in TCP reassembly.
105 The tz database (tzdb) has been updated to 2018e. This version more
106 correctly models time stamps in time zones with negative DST such as
107 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
108 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
109 time zone abbreviations and the tm_isdst flag.
112 The use of RSS hash from the network card aka flowid has been
113 disabled by default for lagg(4) as it's currently incompatible with
114 the lacp and loadbalance protocols.
116 This can be re-enabled by setting the following in loader.conf:
117 net.link.lagg.default_use_flowid="1"
120 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
121 6.0.0. Please see the 20141231 entry below for information about
122 prerequisites and upgrading, if you are not already using clang 3.5.0
126 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
127 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
128 to WITH/OUT_LOADER_GELI.
131 The geli password typed at boot is now hidden. To restore the previous
132 behavior, see geli(8) for configuration options.
134 The SW_WATCHDOG option is no longer necessary to enable the
135 hardclock-based software watchdog if no hardware watchdog is
136 configured. As before, SW_WATCHDOG will cause the software
137 watchdog to be enabled even if a hardware watchdog is configured.
140 lint(1) binaries and library are no longer built by default. To
141 enable building them, define WITH_LINT in src.conf. If you are using
142 a FreeBSD 12 or later system to build 11-stable, you may need to
143 install a lint(1) binary to use WITH_LINT.
146 When building multiple kernels using KERNCONF, non-existent KERNCONF
147 files will produce an error and buildkernel will fail. Previously
148 missing KERNCONF files silently failed giving no indication as to
149 why, only to subsequently discover during installkernel that the
150 desired kernel was never built in the first place.
153 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.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 Since the switch to GPT disk labels, fsck for UFS/FFS has been
159 unable to automatically find alternate superblocks. As of r322806,
160 the information needed to find alternate superblocks has been
161 moved to the end of the area reserved for the boot block.
162 Filesystems created with a newfs of this vintage or later
163 will create the recovery information. If you have a filesystem
164 created prior to this change and wish to have a recovery block
165 created for your filesystem, you can do so by running fsck in
166 forground mode (i.e., do not use the -p or -y options). As it
167 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
168 to which you should answer yes.
171 arm64 builds now use the base system LLD 4.0.0 linker by default,
172 instead of requiring that the aarch64-binutils port or package be
173 installed. To continue using aarch64-binutils, set
174 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
177 The ctl.ko module no longer implements the iSCSI target frontend:
178 cfiscsi.ko does instead.
180 If building cfiscsi.ko as a kernel module, the module can be loaded
181 via one of the following methods:
182 - `cfiscsi_load="YES"` in loader.conf(5).
183 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
184 - ctladm(8)/ctld(8), when compiled with iSCSI support
185 (`WITH_ISCSI=yes` in src.conf(5))
187 Please see cfiscsi(4) for more details.
190 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
191 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
192 same source (previously, the dependency of mmcsd.ko on mmc.ko was
193 missing, but mmcsd.ko now will refuse to load if it is incompatible
197 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
198 use any explicitly assigned loopback address available in the jail
199 instead of using the first assigned address of the jail.
202 As of r316810 for ipfilter, keep frags is no longer assumed when
203 keep state is specified in a rule. r316810 aligns ipfilter with
204 documentation in man pages separating keep frags from keep state.
205 This allows keep state to specified without forcing keep frags
206 and allows keep frags to be specified independently of keep state.
207 To maintain previous behaviour, also specify keep frags with
208 keep state (as documented in ipf.conf.5).
211 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
212 Please see the 20141231 entry below for information about prerequisites
213 and upgrading, if you are not already using clang 3.5.0 or higher.
216 The code that provides support for ZFS .zfs/ directory functionality
217 has been reimplemented. It's not possible now to create a snapshot
218 by mkdir under .zfs/snapshot/. That should be the only user visible
222 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
223 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
224 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
225 and now NAT-T is supported by default. Security associations now use
226 the single namespace for SPI allocation, so if you use several manually
227 configured security associations with the same SPI, this configuration
231 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
232 Please see the 20141231 entry below for information about prerequisites
233 and upgrading, if you are not already using clang 3.5.0 or higher.
236 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
237 Please see the 20141231 entry below for information about prerequisites
238 and upgrading, if you are not already using clang 3.5.0 or higher.
241 The layout of the pmap structure has changed for powerpc to put the pmap
242 statistics at the front for all CPU variations. libkvm(3) and all tools
243 that link against it need to be recompiled.
246 isl(4) and cyapa(4) drivers now require a new driver,
247 chromebook_platform(4), to work properly on Chromebook-class hardware.
248 On other types of hardware the drivers may need to be configured using
249 device hints. Please see the corresponding manual pages for details.
252 Relocatable object files with the extension of .So have been renamed
253 to use an extension of .pico instead. The purpose of this change is
254 to avoid a name clash with shared libraries on case-insensitive file
255 systems. On those file systems, foo.So is the same file as foo.so.
258 The libc stub for the pipe(2) system call has been replaced with
259 a wrapper that calls the pipe2(2) system call and the pipe(2)
260 system call is now only implemented by the kernels that include
261 "options COMPAT_FREEBSD10" in their config file (this is the
262 default). Users should ensure that this option is enabled in
263 their kernel or upgrade userspace to r302092 before upgrading their
267 CAM will now strip leading spaces from SCSI disks' serial numbers.
268 This will effect users who create UFS filesystems on SCSI disks using
269 those disk's diskid device nodes. For example, if /etc/fstab
270 previously contained a line like
271 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
272 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
273 transforms like gmirror may also be affected. ZFS users should
277 The bitstring(3) API has been updated with new functionality and
278 improved performance. But it is binary-incompatible with the old API.
279 Objects built with the new headers may not be linked against objects
280 built with the old headers.
283 The brk and sbrk functions have been removed from libc on arm64.
284 Binutils from ports has been updated to not link to these
285 functions and should be updated to the latest version before
286 installing a new libc.
289 The armv6 port now defaults to hard float ABI. Limited support
290 for running both hardfloat and soft float on the same system
291 is available using the libraries installed with -DWITH_LIBSOFT.
292 This has only been tested as an upgrade path for installworld
293 and packages may fail or need manual intervention to run. New
294 packages will be needed.
296 To update an existing self-hosted armv6hf system, you must add
297 TARGET_ARCH=armv6 on the make command line for both the build
298 and the install steps.
301 Kernel modules compiled outside of a kernel build now default to
302 installing to /boot/modules instead of /boot/kernel. Many kernel
303 modules built this way (such as those in ports) already overrode
304 KMODDIR explicitly to install into /boot/modules. However,
305 manually building and installing a module from /sys/modules will
306 now install to /boot/modules instead of /boot/kernel.
309 The CAM I/O scheduler has been committed to the kernel. There should be
310 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
311 list of known rogues that claim support for this but actually corrupt
312 data is believed to be complete, be on the lookout for data
313 corruption. The known rogue list is believed to be complete:
315 o Crucial MX100, M550 drives with MU01 firmware.
316 o Micron M510 and M550 drives with MU01 firmware.
317 o Micron M500 prior to MU07 firmware
318 o Samsung 830, 840, and 850 all firmwares
319 o FCCT M500 all firmwares
321 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
322 with working NCQ TRIM. For Micron branded drives, see your sales rep for
323 updated firmware. Black listed drives will work correctly because these
324 drives work correctly so long as no NCQ TRIMs are sent to them. Given
325 this list is the same as found in Linux, it's believed there are no
326 other rogues in the market place. All other models from the above
329 To be safe, if you are at all concerned, you can quirk each of your
330 drives to prevent NCQ from being sent by setting:
331 kern.cam.ada.X.quirks="0x2"
332 in loader.conf. If the drive requires the 4k sector quirk, set the
336 The FAST_DEPEND build option has been removed and its functionality is
337 now the one true way. The old mkdep(1) style of 'make depend' has
338 been removed. See 20160311 for further details.
341 Resource range types have grown from unsigned long to uintmax_t. All
342 drivers, and anything using libdevinfo, need to be recompiled.
345 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
346 builds. It no longer runs mkdep(1) during 'make depend', and the
347 'make depend' stage can safely be skipped now as it is auto ran
348 when building 'make all' and will generate all SRCS and DPSRCS before
349 building anything else. Dependencies are gathered at compile time with
350 -MF flags kept in separate .depend files per object file. Users should
351 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
355 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
356 kernel modules. Therefore, if you load any kernel modules at boot time,
357 please install the boot loaders after you install the kernel, but before
361 make kernel KERNCONF=YOUR_KERNEL_HERE
362 make -C sys/boot install
363 <reboot in single user>
365 Then follow the usual steps, described in the General Notes section,
369 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
370 see the 20141231 entry below for information about prerequisites and
371 upgrading, if you are not already using clang 3.5.0 or higher.
374 The AIO subsystem is now a standard part of the kernel. The
375 VFS_AIO kernel option and aio.ko kernel module have been removed.
376 Due to stability concerns, asynchronous I/O requests are only
377 permitted on sockets and raw disks by default. To enable
378 asynchronous I/O requests on all file types, set the
379 vfs.aio.enable_unsafe sysctl to a non-zero value.
382 The ELF object manipulation tool objcopy is now provided by the
383 ELF Tool Chain project rather than by GNU binutils. It should be a
384 drop-in replacement, with the addition of arm64 support. The
385 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
386 to obtain the GNU version if necessary.
389 Building ZFS pools on top of zvols is prohibited by default. That
390 feature has never worked safely; it's always been prone to deadlocks.
391 Using a zvol as the backing store for a VM guest's virtual disk will
392 still work, even if the guest is using ZFS. Legacy behavior can be
393 restored by setting vfs.zfs.vol.recursive=1.
396 The NONE and HPN patches has been removed from OpenSSH. They are
397 still available in the security/openssh-portable port.
400 With the addition of ypldap(8), a new _ypldap user is now required
401 during installworld. "mergemaster -p" can be used to add the user
402 prior to installworld, as documented in the handbook.
405 The tftp loader (pxeboot) now uses the option root-path directive. As a
406 consequence it no longer looks for a pxeboot.4th file on the tftp
407 server. Instead it uses the regular /boot infrastructure as with the
411 The code to start recording plug and play data into the modules has
412 been committed. While the old tools will properly build a new kernel,
413 a number of warnings about "unknown metadata record 4" will be produced
414 for an older kldxref. To avoid such warnings, make sure to rebuild
415 the kernel toolchain (or world). Make sure that you have r292078 or
416 later when trying to build 292077 or later before rebuilding.
419 Debug data files are now built by default with 'make buildworld' and
420 installed with 'make installworld'. This facilitates debugging but
421 requires more disk space both during the build and for the installed
422 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
426 r291527 changed the internal interface between the nfsd.ko and
427 nfscommon.ko modules. As such, they must both be upgraded to-gether.
428 __FreeBSD_version has been bumped because of this.
431 Add support for unicode collation strings leads to a change of
432 order of files listed by ls(1) for example. To get back to the old
433 behaviour, set LC_COLLATE environment variable to "C".
435 Databases administrators will need to reindex their databases given
436 collation results will be different.
438 Due to a bug in install(1) it is recommended to remove the ancient
439 locales before running make installworld.
441 rm -rf /usr/share/locale/*
444 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
445 libcrypto.so.7 or libssl.so.7 must be recompiled.
448 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
449 Kernel modules isp_2400_multi and isp_2500_multi were removed and
450 should be replaced with isp_2400 and isp_2500 modules respectively.
453 The build previously allowed using 'make -n' to not recurse into
454 sub-directories while showing what commands would be executed, and
455 'make -n -n' to recursively show commands. Now 'make -n' will recurse
456 and 'make -N' will not.
459 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
460 and etcupdate will now use this file. A custom sendmail.cf is now
461 updated via this mechanism rather than via installworld. If you had
462 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
463 want to remove the exclusion or change it to "always install".
464 /etc/mail/sendmail.cf is now managed the same way regardless of
465 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
466 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
469 Compatibility shims for legacy ATA device names have been removed.
470 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
471 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
472 environment variables, /dev/ad* and /dev/ar* symbolic links.
475 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
476 Please see the 20141231 entry below for information about prerequisites
477 and upgrading, if you are not already using clang 3.5.0 or higher.
480 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
481 and renamed from .symbols to .debug. This reduces the size requirements
482 on the boot partition or file system and provides consistency with
483 userland debug files.
485 When using the supported kernel installation method the
486 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
487 as is done with /boot/kernel.
489 Developers wishing to maintain the historical behavior of installing
490 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
493 The wireless drivers had undergone changes that remove the 'parent
494 interface' from the ifconfig -l output. The rc.d network scripts
495 used to check presence of a parent interface in the list, so old
496 scripts would fail to start wireless networking. Thus, etcupdate(3)
497 or mergemaster(8) run is required after kernel update, to update your
498 rc.d scripts in /etc.
501 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
502 These configurations are now automatically interpreted as
503 'scrub fragment reassemble'.
506 Kernel-loadable modules for the random(4) device are back. To use
507 them, the kernel must have
510 options RANDOM_LOADABLE
512 kldload(8) can then be used to load random_fortuna.ko
513 or random_yarrow.ko. Please note that due to the indirect
514 function calls that the loadable modules need to provide,
515 the build-in variants will be slightly more efficient.
517 The random(4) kernel option RANDOM_DUMMY has been retired due to
518 unpopularity. It was not all that useful anyway.
521 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
522 Control over building the ELF Tool Chain tools is now provided by
523 the WITHOUT_TOOLCHAIN knob.
526 The polarity of Pulse Per Second (PPS) capture events with the
527 uart(4) driver has been corrected. Prior to this change the PPS
528 "assert" event corresponded to the trailing edge of a positive PPS
529 pulse and the "clear" event was the leading edge of the next pulse.
531 As the width of a PPS pulse in a typical GPS receiver is on the
532 order of 1 millisecond, most users will not notice any significant
533 difference with this change.
535 Anyone who has compensated for the historical polarity reversal by
536 configuring a negative offset equal to the pulse width will need to
537 remove that workaround.
540 The default group assigned to /dev/dri entries has been changed
541 from 'wheel' to 'video' with the id of '44'. If you want to have
542 access to the dri devices please add yourself to the video group
545 # pw groupmod video -m $USER
548 The menu.rc and loader.rc files will now be replaced during
549 upgrades. Please migrate local changes to menu.rc.local and
550 loader.rc.local instead.
553 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
554 strings and strip have been removed. The src.conf(5) knob
555 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
558 As ZFS requires more kernel stack pages than is the default on some
559 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
560 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
562 Please consider using 'options KSTACK_PAGES=X' where X is greater
563 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
566 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
567 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
568 default, i.e., they will not contain "::". For example, instead
569 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
570 to have a more specific match, such as different map entries for
571 IPv6:0:0 vs IPv6:0. This change requires that configuration
572 data (including maps, files, classes, custom ruleset, etc.) must
573 use the same format, so make certain such configuration data is
574 upgrading. As a very simple check search for patterns like
575 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
576 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
577 the cf option UseCompressedIPv6Addresses.
580 The default kernel entropy-processing algorithm is now
581 Fortuna, replacing Yarrow.
583 Assuming you have 'device random' in your kernel config
584 file, the configurations allow a kernel option to override
585 this default. You may choose *ONE* of:
587 options RANDOM_YARROW # Legacy /dev/random algorithm.
588 options RANDOM_DUMMY # Blocking-only driver.
590 If you have neither, you get Fortuna. For most people,
591 read no further, Fortuna will give a /dev/random that works
592 like it always used to, and the difference will be irrelevant.
594 If you remove 'device random', you get *NO* kernel-processed
595 entropy at all. This may be acceptable to folks building
596 embedded systems, but has complications. Carry on reading,
597 and it is assumed you know what you need.
599 *PLEASE* read random(4) and random(9) if you are in the
600 habit of tweaking kernel configs, and/or if you are a member
601 of the embedded community, wanting specific and not-usual
602 behaviour from your security subsystems.
604 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
605 random', you will NOT have a functioning /dev/random, and
606 many cryptographic features will not work, including SSH.
607 You may also find strange behaviour from the random(3) set
608 of library functions, in particular sranddev(3), srandomdev(3)
609 and arc4random(3). The reason for this is that the KERN_ARND
610 sysctl only returns entropy if it thinks it has some to
611 share, and with RANDOM_DUMMY or no 'device random' this
615 An additional fix for the issue described in the 20150614 sendmail
616 entry below has been been committed in revision 284717.
619 FreeBSD's old make (fmake) has been removed from the system. It is
620 available as the devel/fmake port or via pkg install fmake.
623 The fix for the issue described in the 20150614 sendmail entry
624 below has been been committed in revision 284436. The work
625 around described in that entry is no longer needed unless the
626 default setting is overridden by a confDH_PARAMETERS configuration
627 setting of '5' or pointing to a 512 bit DH parameter file.
630 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
631 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
632 and devel/kyua to version 0.20+ and adjust any calling code to work
633 with Kyuafile and kyua.
636 The import of openssl to address the FreeBSD-SA-15:10.openssl
637 security advisory includes a change which rejects handshakes
638 with DH parameters below 768 bits. sendmail releases prior
639 to 8.15.2 (not yet released), defaulted to a 512 bit
640 DH parameter setting for client connections. To work around
641 this interoperability, sendmail can be configured to use a
642 2048 bit DH parameter by:
644 1. Edit /etc/mail/`hostname`.mc
645 2. If a setting for confDH_PARAMETERS does not exist or
646 exists and is set to a string beginning with '5',
648 3. If a setting for confDH_PARAMETERS exists and is set to
649 a file path, create a new file with:
650 openssl dhparam -out /path/to/file 2048
651 4. Rebuild the .cf file:
652 cd /etc/mail/; make; make install
654 cd /etc/mail/; make restart
656 A sendmail patch is coming, at which time this file will be
660 Generation of legacy formatted entries have been disabled by default
661 in pwd_mkdb(8), as all base system consumers of the legacy formatted
662 entries were converted to use the new format by default when the new,
663 machine independent format have been added and supported since FreeBSD
666 Please see the pwd_mkdb(8) manual page for further details.
669 Clang and llvm have been upgraded to 3.6.1 release. Please see the
670 20141231 entry below for information about prerequisites and upgrading,
671 if you are not already using 3.5.0 or higher.
674 TI platform code switched to using vendor DTS files and this update
675 may break existing systems running on Beaglebone, Beaglebone Black,
678 - dtb files should be regenerated/reinstalled. Filenames are the
679 same but content is different now
680 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
681 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
682 addressing scheme is now pin 25 on /dev/gpioc3.
683 - Pandaboard: /etc/ttys should be updated, serial console device is
684 now /dev/ttyu2, not /dev/ttyu0
687 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
688 If you need the GNU extension from groff soelim(1), install groff
689 from package: pkg install groff, or via ports: textproc/groff.
692 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
693 defined in symlink(7); previously symlinks were silently ignored.
696 The const qualifier has been removed from iconv(3) to comply with
697 POSIX. The ports tree is aware of this from r384038 onwards.
700 Libraries specified by LIBADD in Makefiles must have a corresponding
701 DPADD_<lib> variable to ensure correct dependencies. This is now
702 enforced in src.libnames.mk.
705 From legacy ata(4) driver was removed support for SATA controllers
706 supported by more functional drivers ahci(4), siis(4) and mvs(4).
707 Kernel modules ataahci and ataadaptec were removed completely,
708 replaced by ahci and mvs modules respectively.
711 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
712 the 20141231 entry below for information about prerequisites and
713 upgrading, if you are not already using 3.5.0 or higher.
716 The 32-bit PowerPC kernel has been changed to a position-independent
717 executable. This can only be booted with a version of loader(8)
718 newer than January 31, 2015, so make sure to update both world and
719 kernel before rebooting.
722 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
723 but before r278950, the RNG was not seeded properly. Immediately
724 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
725 ssh keys or openssl keys) that were generated w/ a kernel from that
726 range. This does not affect programs that directly used /dev/random
727 or /dev/urandom. All userland uses of arc4random(3) are affected.
730 The autofs(4) ABI was changed in order to restore binary compatibility
731 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
735 The powerpc64 kernel has been changed to a position-independent
736 executable. This can only be booted with a new version of loader(8),
737 so make sure to update both world and kernel before rebooting.
740 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
741 only release, no new features have been added. Please see the 20141231
742 entry below for information about prerequisites and upgrading, if you
743 are not already using 3.5.0.
746 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
747 taken from the ELF Tool Chain project rather than GNU binutils. They
748 should be drop-in replacements, with the addition of arm64 support.
749 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
750 binutils tools, if necessary. See 20150805 for updated information.
753 The default Unbound configuration now enables remote control
754 using a local socket. Users who have already enabled the
755 local_unbound service should regenerate their configuration
756 by running "service local_unbound setup" as root.
759 The GNU texinfo and GNU info pages have been removed.
760 To be able to view GNU info pages please install texinfo from ports.
763 Clang, llvm and lldb have been upgraded to 3.5.0 release.
765 As of this release, a prerequisite for building clang, llvm and lldb is
766 a C++11 capable compiler and C++11 standard library. This means that to
767 be able to successfully build the cross-tools stage of buildworld, with
768 clang as the bootstrap compiler, your system compiler or cross compiler
769 should either be clang 3.3 or later, or gcc 4.8 or later, and your
770 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
773 On any standard FreeBSD 10.x or 11.x installation, where clang and
774 libc++ are on by default (that is, on x86 or arm), this should work out
777 On 9.x installations where clang is enabled by default, e.g. on x86 and
778 powerpc, libc++ will not be enabled by default, so libc++ should be
779 built (with clang) and installed first. If both clang and libc++ are
780 missing, build clang first, then use it to build libc++.
782 On 8.x and earlier installations, upgrade to 9.x first, and then follow
783 the instructions for 9.x above.
785 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
786 default, and do not build clang.
788 Many embedded systems are resource constrained, and will not be able to
789 build clang in a reasonable time, or in some cases at all. In those
790 cases, cross building bootable systems on amd64 is a workaround.
792 This new version of clang introduces a number of new warnings, of which
793 the following are most likely to appear:
797 This warns in two cases, for both C and C++:
798 * When the code is trying to take the absolute value of an unsigned
799 quantity, which is effectively a no-op, and almost never what was
800 intended. The code should be fixed, if at all possible. If you are
801 sure that the unsigned quantity can be safely cast to signed, without
802 loss of information or undefined behavior, you can add an explicit
803 cast, or disable the warning.
805 * When the code is trying to take an absolute value, but the called
806 abs() variant is for the wrong type, which can lead to truncation.
807 If you want to disable the warning instead of fixing the code, please
808 make sure that truncation will not occur, or it might lead to unwanted
811 -Wtautological-undefined-compare and
812 -Wundefined-bool-conversion
814 These warn when C++ code is trying to compare 'this' against NULL, while
815 'this' should never be NULL in well-defined C++ code. However, there is
816 some legacy (pre C++11) code out there, which actively abuses this
817 feature, which was less strictly defined in previous C++ versions.
819 Squid and openjdk do this, for example. The warning can be turned off
820 for C++98 and earlier, but compiling the code in C++11 mode might result
821 in unexpected behavior; for example, the parts of the program that are
822 unreachable could be optimized away.
825 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
826 kernel sources have been removed. The .h files remain, since some
827 utilities include them. This will need to be fixed later.
828 If "mount -t oldnfs ..." is attempted, it will fail.
829 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
830 the utilities will report errors.
833 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
834 directories to top level SUBDIR variable when their parent
835 directory is included in LOCAL_DIRS. Users with build systems with
836 such hierarchies and without SUBDIR entries in the parent
837 directory Makefiles should add them or add the directories to
841 faith(4) and faithd(8) have been removed from the base system. Faith
842 has been obsolete for a very long time.
845 vt(4), the new console driver, is enabled by default. It brings
846 support for Unicode and double-width characters, as well as
847 support for UEFI and integration with the KMS kernel video
850 You may need to update your console settings in /etc/rc.conf,
851 most probably the keymap. During boot, /etc/rc.d/syscons will
852 indicate what you need to do.
854 vt(4) still has issues and lacks some features compared to
855 syscons(4). See the wiki for up-to-date information:
856 https://wiki.freebsd.org/Newcons
858 If you want to keep using syscons(4), you can do so by adding
859 the following line to /boot/loader.conf:
863 pjdfstest has been integrated into kyua as an opt-in test suite.
864 Please see share/doc/pjdfstest/README for more details on how to
868 gperf has been removed from the base system for architectures
869 that use clang. Ports that require gperf will obtain it from the
873 pjdfstest has been moved from tools/regression/pjdfstest to
877 At svn r271982, The default linux compat kernel ABI has been adjusted
878 to 2.6.18 in support of the linux-c6 compat ports infrastructure
879 update. If you wish to continue using the linux-f10 compat ports,
880 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
881 encouraged to update their linux-compat packages to linux-c6 during
882 their next update cycle.
885 The ofwfb driver, used to provide a graphics console on PowerPC when
886 using vt(4), no longer allows mmap() of all physical memory. This
887 will prevent Xorg on PowerPC with some ATI graphics cards from
888 initializing properly unless x11-servers/xorg-server is updated to
892 The xdev targets have been converted to using TARGET and
893 TARGET_ARCH instead of XDEV and XDEV_ARCH.
896 The default unbound configuration has been modified to address
897 issues with reverse lookups on networks that use private
898 address ranges. If you use the local_unbound service, run
899 "service local_unbound setup" as root to regenerate your
900 configuration, then "service local_unbound reload" to load the
904 The GNU texinfo and GNU info pages are not built and installed
905 anymore, WITH_INFO knob has been added to allow to built and install
907 UPDATE: see 20150102 entry on texinfo's removal
910 The GNU readline library is now an INTERNALLIB - that is, it is
911 statically linked into consumers (GDB and variants) in the base
912 system, and the shared library is no longer installed. The
913 devel/readline port is available for third party software that
917 The Itanium architecture (ia64) has been removed from the list of
918 known architectures. This is the first step in the removal of the
922 Commit r268115 has added NFSv4.1 server support, merged from
923 projects/nfsv4.1-server. Since this includes changes to the
924 internal interfaces between the NFS related modules, a full
925 build of the kernel and modules will be necessary.
926 __FreeBSD_version has been bumped.
929 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
930 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
931 which differs from the behaviour controlled by this knob.)
934 Maximal length of the serial number in CTL was increased from 16 to
935 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
936 and ctld, need to be rebuilt to work with a new kernel.
939 The libatf-c and libatf-c++ major versions were downgraded to 0 and
940 1 respectively to match the upstream numbers. They were out of
941 sync because, when they were originally added to FreeBSD, the
942 upstream versions were not respected. These libraries are private
943 and not yet built by default, so renumbering them should be a
944 non-issue. However, unclean source trees will yield broken test
945 programs once the operator executes "make delete-old-libs" after a
948 Additionally, the atf-sh binary was made private by moving it into
949 /usr/libexec/. Already-built shell test programs will keep the
950 path to the old binary so they will break after "make delete-old"
953 If you are using WITH_TESTS=yes (not the default), wipe the object
954 tree and rebuild from scratch to prevent spurious test failures.
955 This is only needed once: the misnumbered libraries and misplaced
956 binaries have been added to OptionalObsoleteFiles.inc so they will
957 be removed during a clean upgrade.
960 Clang and llvm have been upgraded to 3.4.1 release.
963 We bogusly installed src.opts.mk in /usr/share/mk. This file should
964 be removed to avoid issues in the future (and has been added to
968 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
969 past, it affected all builds that used the bsd.*.mk files. The old
970 behavior was a bug, but people may have relied upon it. To get this
971 behavior back, you can .include /etc/src.conf from /etc/make.conf
972 (which is still global and isn't changed). This also changes the
973 behavior of incremental builds inside the tree of individual
974 directories. Set MAKESYSPATH to ".../share/mk" to do that.
975 Although this has survived make universe and some upgrade scenarios,
976 other upgrade scenarios may have broken. At least one form of
977 temporary breakage was fixed with MAKESYSPATH settings for buildworld
978 as well... In cases where MAKESYSPATH isn't working with this
979 setting, you'll need to set it to the full path to your tree.
981 One side effect of all this cleaning up is that bsd.compiler.mk
982 is no longer implicitly included by bsd.own.mk. If you wish to
983 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
987 The lindev device has been removed since /dev/full has been made a
988 standard device. __FreeBSD_version has been bumped.
991 The knob WITHOUT_VI was added to the base system, which controls
992 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
993 in order to reorder files share/termcap and didn't build ex(1) as a
994 build tool, so building/installing with WITH_VI is highly advised for
995 build hosts for older releases.
997 This issue has been fixed in stable/9 and stable/10 in r277022 and
998 r276991, respectively.
1001 The YES_HESIOD knob has been removed. It has been obsolete for
1002 a decade. Please move to using WITH_HESIOD instead or your builds
1003 will silently lack HESIOD.
1006 The uart(4) driver has been changed with respect to its handling
1007 of the low-level console. Previously the uart(4) driver prevented
1008 any process from changing the baudrate or the CLOCAL and HUPCL
1009 control flags. By removing the restrictions, operators can make
1010 changes to the serial console port without having to reboot.
1011 However, when getty(8) is started on the serial device that is
1012 associated with the low-level console, a misconfigured terminal
1013 line in /etc/ttys will now have a real impact.
1014 Before upgrading the kernel, make sure that /etc/ttys has the
1015 serial console device configured as 3wire without baudrate to
1016 preserve the previous behaviour. E.g:
1017 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1020 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1021 to improve performance. To re-enable it, if needed, run rpcbind
1022 with command line option -W.
1025 Switched back to the GPL dtc compiler due to updates in the upstream
1026 dts files not being supported by the BSDL dtc compiler. You will need
1027 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1028 may result while building dtb files during a kernel build if you fail
1029 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1032 Clang and llvm have been upgraded to 3.4 release.
1035 The nve(4) driver has been removed. Please use the nfe(4) driver
1036 for NVIDIA nForce MCP Ethernet adapters instead.
1039 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1040 This could cause certain C++ applications using shared libraries built
1041 against the previous version of libc++ to crash. The incompatibility
1042 has now been fixed, but any C++ applications or shared libraries built
1043 between r261283 and r261801 should be recompiled.
1046 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1047 capability mode support. Please note that enabling the feature in
1048 kernel is still highly recommended.
1051 OpenSSH is now built with sandbox support, and will use sandbox as
1052 the default privilege separation method. This requires Capsicum
1053 capability mode support in kernel.
1056 The libelf and libdwarf libraries have been updated to newer
1057 versions from upstream. Shared library version numbers for
1058 these two libraries were bumped. Any ports or binaries
1059 requiring these two libraries should be recompiled.
1060 __FreeBSD_version is bumped to 1100006.
1063 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1064 instead of providing an explicit one, this would prevent such
1065 Makefile from providing its own Kyuafile in the future during
1066 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1067 intervention is needed to clean an objdir if you use NO_CLEAN:
1068 # find /usr/obj -name Kyuafile | xargs rm -f
1071 The behavior of gss_pseudo_random() for the krb5 mechanism
1072 has changed, for applications requesting a longer random string
1073 than produced by the underlying enctype's pseudo-random() function.
1074 In particular, the random string produced from a session key of
1075 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1076 be different at the 17th octet and later, after this change.
1077 The counter used in the PRF+ construction is now encoded as a
1078 big-endian integer in accordance with RFC 4402.
1079 __FreeBSD_version is bumped to 1100004.
1082 The WITHOUT_ATF build knob has been removed and its functionality
1083 has been subsumed into the more generic WITHOUT_TESTS. If you were
1084 using the former to disable the build of the ATF libraries, you
1085 should change your settings to use the latter.
1088 The default version of mtree is nmtree which is obtained from
1089 NetBSD. The output is generally the same, but may vary
1090 slightly. If you found you need identical output adding
1091 "-F freebsd9" to the command line should do the trick. For the
1092 time being, the old mtree is available as fmtree.
1095 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1096 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1097 1.1.4_8 and verify bsdyml not linked in, before running "make
1099 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1101 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1104 The stable/10 branch has been created in subversion from head
1108 The rc.d/jail script has been updated to support jail(8)
1109 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1110 for per-jail configuration are automatically converted to
1111 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1112 This is transparently backward compatible. See below about some
1113 incompatibilities and rc.conf(5) manual page for more details.
1115 These variables are now deprecated in favor of jail(8) configuration
1116 file. One can use "rc.d/jail config <jname>" command to generate
1117 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1118 running the jail(8) utility. The default pathname of the
1119 configuration file is /etc/jail.conf and can be specified by
1120 using $jail_conf or $jail_<jname>_conf variables.
1122 Please note that jail_devfs_ruleset accepts an integer at
1123 this moment. Please consider to rewrite the ruleset name
1127 BIND has been removed from the base system. If all you need
1128 is a local resolver, simply enable and start the local_unbound
1129 service instead. Otherwise, several versions of BIND are
1130 available in the ports tree. The dns/bind99 port is one example.
1132 With this change, nslookup(1) and dig(1) are no longer in the base
1133 system. Users should instead use host(1) and drill(1) which are
1134 in the base system. Alternatively, nslookup and dig can
1135 be obtained by installing the dns/bind-tools port.
1138 With the addition of unbound(8), a new unbound user is now
1139 required during installworld. "mergemaster -p" can be used to
1140 add the user prior to installworld, as documented in the handbook.
1143 OpenSSH is now built with DNSSEC support, and will by default
1144 silently trust signed SSHFP records. This can be controlled with
1145 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1146 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1149 The GNU Compiler Collection and C++ standard library (libstdc++)
1150 are no longer built by default on platforms where clang is the system
1151 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1152 options in src.conf.
1155 The PROCDESC kernel option is now part of the GENERIC kernel
1156 configuration and is required for the rwhod(8) to work.
1157 If you are using custom kernel configuration, you should include
1161 The API and ABI related to the Capsicum framework was modified
1162 in backward incompatible way. The userland libraries and programs
1163 have to be recompiled to work with the new kernel. This includes the
1164 following libraries and programs, but the whole buildworld is
1165 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1166 kdump, procstat, rwho, rwhod, uniq.
1169 AES-NI intrinsic support has been added to gcc. The AES-NI module
1170 has been updated to use this support. A new gcc is required to build
1171 the aesni module on both i386 and amd64.
1174 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1175 Thus "device padlock_rng" and "device rdrand_rng" should be
1176 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1179 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1180 enables just the iconv* functionality and is now on by default.
1181 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1182 compatibility. Set WITHOUT_ICONV to build the old way.
1183 If you have been using WITH_ICONV before, you will very likely
1184 need to turn on WITH_LIBICONV_COMPAT.
1187 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1188 Illumos origin, including ZFS. If you have INVARIANTS in your
1189 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1191 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1192 locks if WITNESS option was set. Because that generated a lot of
1193 witness(9) reports and all of them were believed to be false
1194 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1195 can be used to achieve the previous behavior.
1198 Timer values in IPv6 data structures now use time_uptime instead
1199 of time_second. Although this is not a user-visible functional
1200 change, userland utilities which directly use them---ndp(8),
1201 rtadvd(8), and rtsold(8) in the base system---need to be updated
1202 to r253970 or later.
1205 find -delete can now delete the pathnames given as arguments,
1206 instead of only files found below them or if the pathname did
1207 not contain any slashes. Formerly, the following error message
1210 find: -delete: <path>: relative path potentially not safe
1212 Deleting the pathnames given as arguments can be prevented
1213 without error messages using -mindepth 1 or by changing
1214 directory and passing "." as argument to find. This works in the
1215 old as well as the new version of find.
1218 Behavior of devfs rules path matching has been changed.
1219 Pattern is now always matched against fully qualified devfs
1220 path and slash characters must be explicitly matched by
1221 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1222 subdirectories must be reviewed.
1225 The default ARM ABI has changed to the ARM EABI. The old ABI is
1226 incompatible with the ARM EABI and all programs and modules will
1227 need to be rebuilt to work with a new kernel.
1229 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1231 NOTE: Support for the old ABI will be removed in the future and
1232 users are advised to upgrade.
1235 pkg_install has been disconnected from the build if you really need it
1236 you should add WITH_PKGTOOLS in your src.conf(5).
1239 Most of network statistics structures were changed to be able
1240 keep 64-bits counters. Thus all tools, that work with networking
1241 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1244 Fix a bug that allowed a tracing process (e.g. gdb) to write
1245 to a memory-mapped file in the traced process's address space
1246 even if neither the traced process nor the tracing process had
1247 write access to that file.
1250 CVS has been removed from the base system. An exact copy
1251 of the code is available from the devel/cvs port.
1254 Some people report the following error after the switch to bmake:
1256 make: illegal option -- J
1257 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1259 *** [buildworld] Error code 2
1261 this likely due to an old instance of make in
1262 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1263 which src/Makefile will use that blindly, if it exists, so if
1264 you see the above error:
1266 rm -rf `make -V MAKEPATH`
1271 Use bmake by default.
1272 Whereas before one could choose to build with bmake via
1273 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1274 make. The goal is to remove these knobs for 10-RELEASE.
1276 It is worth noting that bmake (like gmake) treats the command
1277 line as the unit of failure, rather than statements within the
1278 command line. Thus '(cd some/where && dosomething)' is safer
1279 than 'cd some/where; dosomething'. The '()' allows consistent
1280 behavior in parallel build.
1283 Fix a bug that allows NFS clients to issue READDIR on files.
1286 The WITHOUT_IDEA option has been removed because
1287 the IDEA patent expired.
1290 The sysctl which controls TRIM support under ZFS has been renamed
1291 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1295 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1296 rather than creating it's own in the temporary directory in
1297 order allow access to bootstrapped versions of tools such as
1298 install and mtree. When upgrading from version of FreeBSD where
1299 the install command does not support -l, you will need to
1300 install a new mergemaster command if mergemaster -p is required.
1301 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1305 Legacy ATA stack, disabled and replaced by new CAM-based one since
1306 FreeBSD 9.0, completely removed from the sources. Kernel modules
1307 atadisk and atapi*, user-level tools atacontrol and burncd are
1308 removed. Kernel option `options ATA_CAM` is now permanently enabled
1312 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1313 and socketpair(2). Software, in particular Kerberos, may
1314 automatically detect and use these during building. The resulting
1315 binaries will not work on older kernels.
1318 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1319 information, see the respective 20130304 entry).
1322 Recent commits to callout(9) changed the size of struct callout,
1323 so the KBI is probably heavily disturbed. Also, some functions
1324 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1325 by macros. Every kernel module using it won't load, so rebuild
1328 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1329 but does not initialize by default (because of the new CTL_DISABLE
1330 option) to save memory. To re-enable it, remove the CTL_DISABLE
1331 option from the kernel config file or set kern.cam.ctl.disable=0
1332 in /boot/loader.conf.
1335 The ctl device has been disabled in GENERIC for i386 and amd64.
1336 This was done due to the extra memory being allocated at system
1337 initialisation time by the ctl driver which was only used if
1338 a CAM target device was created. This makes a FreeBSD system
1339 unusable on 128MB or less of RAM.
1342 A new compression method (lz4) has been merged to -HEAD. Please
1343 refer to zpool-features(7) for more information.
1345 Please refer to the "ZFS notes" section of this file for information
1346 on upgrading boot ZFS pools.
1349 A BSD-licensed patch(1) variant has been added and is installed
1350 as bsdpatch, being the GNU version the default patch.
1351 To inverse the logic and use the BSD-licensed one as default,
1352 while having the GNU version installed as gnupatch, rebuild
1353 and install world with the WITH_BSD_PATCH knob set.
1356 Due to the use of the new -l option to install(1) during build
1357 and install, you must take care not to directly set the INSTALL
1358 make variable in your /etc/make.conf, /etc/src.conf, or on the
1359 command line. If you wish to use the -C flag for all installs
1360 you may be able to add INSTALL+=-C to /etc/make.conf or
1364 The install(1) option -M has changed meaning and now takes an
1365 argument that is a file or path to append logs to. In the
1366 unlikely event that -M was the last option on the command line
1367 and the command line contained at least two files and a target
1368 directory the first file will have logs appended to it. The -M
1369 option served little practical purpose in the last decade so its
1370 use is expected to be extremely rare.
1373 After switching to Clang as the default compiler some users of ZFS
1374 on i386 systems started to experience stack overflow kernel panics.
1375 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1378 GEOM_LABEL now mangles label names read from file system metadata.
1379 Mangling affect labels containing spaces, non-printable characters,
1380 '%' or '"'. Device names in /etc/fstab and other places may need to
1384 By default, only the 10 most recent kernel dumps will be saved. To
1385 restore the previous behaviour (no limit on the number of kernel dumps
1386 stored in the dump directory) add the following line to /etc/rc.conf:
1391 With the addition of auditdistd(8), a new auditdistd user is now
1392 required during installworld. "mergemaster -p" can be used to
1393 add the user prior to installworld, as documented in the handbook.
1396 The sin6_scope_id member variable in struct sockaddr_in6 is now
1397 filled by the kernel before passing the structure to the userland via
1398 sysctl or routing socket. This means the KAME-specific embedded scope
1399 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1400 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1401 __FreeBSD_version is bumped to 1000025.
1404 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1405 This means that the world and kernel will be compiled with clang
1406 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1407 and /usr/bin/cpp. To disable this behavior and revert to building
1408 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1409 of current may need to bootstrap WITHOUT_CLANG first if the clang
1410 build fails (its compatibility window doesn't extend to the 9 stable
1414 The IPFIREWALL_FORWARD kernel option has been removed. Its
1415 functionality now turned on by default.
1418 The ZERO_COPY_SOCKET kernel option has been removed and
1419 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1420 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1421 mechanism which is not safe and may result in kernel crashes.
1422 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1423 driver supports disposeable external page sized mbuf storage.
1424 Proper replacements for both zero-copy mechanisms are under
1425 consideration and will eventually lead to complete removal
1426 of the two kernel options.
1429 The IPv4 network stack has been converted to network byte
1430 order. The following modules need to be recompiled together
1431 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1432 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1435 Support for non-MPSAFE filesystems was removed from VFS. The
1436 VFS_VERSION was bumped, all filesystem modules shall be
1440 All the non-MPSAFE filesystems have been disconnected from
1441 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1442 portalfs, smbfs, xfs.
1445 The interface cloning API and ABI has changed. The following
1446 modules need to be recompiled together with kernel:
1447 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1448 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1449 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1452 The sdhci driver was split in two parts: sdhci (generic SD Host
1453 Controller logic) and sdhci_pci (actual hardware driver).
1454 No kernel config modifications are required, but if you
1455 load sdhc as a module you must switch to sdhci_pci instead.
1458 Import the FUSE kernel and userland support into base system.
1461 The GNU sort(1) program has been removed since the BSD-licensed
1462 sort(1) has been the default for quite some time and no serious
1463 problems have been reported. The corresponding WITH_GNU_SORT
1467 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1468 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1472 The net80211(4) ABI has been changed to allow for improved driver
1473 PS-POLL and power-save support. All wireless drivers need to be
1474 recompiled to work with the new kernel.
1477 The random(4) support for the VIA hardware random number
1478 generator (`PADLOCK') is no longer enabled unconditionally.
1479 Add the padlock_rng device in the custom kernel config if
1480 needed. The GENERIC kernels on i386 and amd64 do include the
1481 device, so the change only affects the custom kernel
1485 The pf(4) packet filter ABI has been changed. pfctl(8) and
1486 snmp_pf module need to be recompiled to work with new kernel.
1489 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1490 to -HEAD. Pools that have empty_bpobj in active state can not be
1491 imported read-write with ZFS implementations that do not support
1492 this feature. For more information read the zpool-features(5)
1496 The sparc64 ZFS loader has been changed to no longer try to auto-
1497 detect ZFS providers based on diskN aliases but now requires these
1498 to be explicitly listed in the OFW boot-device environment variable.
1501 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1502 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1503 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1506 The following sysctls and tunables have been renamed for consistency
1507 with other variables:
1508 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1509 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1512 The sort utility has been replaced with BSD sort. For now, GNU sort
1513 is also available as "gnusort" or the default can be set back to
1514 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1515 installed as "bsdsort".
1518 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1519 Starting with this version the old system of ZFS pool versioning
1520 is superseded by "feature flags". This concept enables forward
1521 compatibility against certain future changes in functionality of ZFS
1522 pools. The first read-only compatible "feature flag" for ZFS pools
1523 is named "com.delphix:async_destroy". For more information
1524 read the new zpool-features(5) manual page.
1525 Please refer to the "ZFS notes" section of this file for information
1526 on upgrading boot ZFS pools.
1529 The malloc(3) implementation embedded in libc now uses sources imported
1530 as contrib/jemalloc. The most disruptive API change is to
1531 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1532 delete it prior to installworld, and optionally re-create it using the
1533 new format after rebooting. See malloc.conf(5) for details
1534 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1538 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1539 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1540 now spelled mips. This is to aid compatibility with third-party
1541 software that expects this naming scheme in uname(3). Little-endian
1542 settings are unchanged. If you are updating a big-endian mips64 machine
1543 from before this change, you may need to set MACHINE_ARCH=mips64 in
1544 your environment before the new build system will recognize your machine.
1547 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1551 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1552 nullfs(5) did not pass through all behaviours to the underlying layer,
1553 as a result if we bound to a socket on the lower layer we could connect
1554 only to the lower path; if we bound to the upper layer we could connect
1555 only to the upper path. The new behavior is one can connect to both the
1556 lower and the upper paths regardless what layer path one binds to.
1559 The getifaddrs upgrade path broken with 20111215 has been restored.
1560 If you have upgraded in between 20111215 and 20120209 you need to
1561 recompile libc again with your kernel. You still need to recompile
1562 world to be able to configure CARP but this restriction already
1563 comes from 20111215.
1566 The set_rcvar() function has been removed from /etc/rc.subr. All
1567 base and ports rc.d scripts have been updated, so if you have a
1568 port installed with a script in /usr/local/etc/rc.d you can either
1569 hand-edit the rcvar= line, or reinstall the port.
1571 An easy way to handle the mass-update of /etc/rc.d:
1572 rm /etc/rc.d/* && mergemaster -i
1575 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1576 on the current CPU and prevents other threads from running.
1577 This behavior can be reverted using the kern.stop_scheduler_on_panic
1579 The new behavior can be incompatible with kern.sync_on_panic.
1582 The carp(4) facility has been changed significantly. Configuration
1583 of the CARP protocol via ifconfig(8) has changed, as well as format
1584 of CARP events submitted to devd(8) has changed. See manual pages
1585 for more information. The arpbalance feature of carp(4) is currently
1586 not supported anymore.
1588 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1589 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1590 need to be recompiled.
1593 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1597 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1598 explicitely support non-MPSAFE filesystems.
1599 It is on by default for all supported platform at this present
1603 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1604 i386 and pc98 GENERIC kernel configuration files.
1607 sysinstall has been removed
1610 The stable/9 branch created in subversion. This corresponds to the
1611 RELENG_9 branch in CVS.
1617 Avoid using make -j when upgrading. While generally safe, there are
1618 sometimes problems using -j to upgrade. If your upgrade fails with
1619 -j, please try again without -j. From time to time in the past there
1620 have been problems using -j with buildworld and/or installworld. This
1621 is especially true when upgrading between "distant" versions (eg one
1622 that cross a major release boundary or several minor releases, or when
1623 several months have passed on the -current branch).
1625 Sometimes, obscure build problems are the result of environment
1626 poisoning. This can happen because the make utility reads its
1627 environment when searching for values for global variables. To run
1628 your build attempts in an "environmental clean room", prefix all make
1629 commands with 'env -i '. See the env(1) manual page for more details.
1631 When upgrading from one major version to another it is generally best
1632 to upgrade to the latest code in the currently installed branch first,
1633 then do an upgrade to the new branch. This is the best-tested upgrade
1634 path, and has the highest probability of being successful. Please try
1635 this approach before reporting problems with a major version upgrade.
1637 When upgrading a live system, having a root shell around before
1638 installing anything can help undo problems. Not having a root shell
1639 around can lead to problems if pam has changed too much from your
1640 starting point to allow continued authentication after the upgrade.
1642 This file should be read as a log of events. When a later event changes
1643 information of a prior event, the prior event should not be deleted.
1644 Instead, a pointer to the entry with the new information should be
1645 placed in the old entry. Readers of this file should also sanity check
1646 older entries before relying on them blindly. Authors of new entries
1647 should write them with this in mind.
1651 When upgrading the boot ZFS pool to a new version, always follow
1654 1.) recompile and reinstall the ZFS boot loader and boot block
1655 (this is part of "make buildworld" and "make installworld")
1657 2.) update the ZFS boot block on your boot drive
1659 The following example updates the ZFS boot block on the first
1660 partition (freebsd-boot) of a GPT partitioned drive ada0:
1661 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1663 Non-boot pools do not need these updates.
1667 If you are updating from a prior version of FreeBSD (even one just
1668 a few days old), you should follow this procedure. It is the most
1669 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1671 make kernel-toolchain
1672 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1673 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1675 To test a kernel once
1676 ---------------------
1677 If you just want to boot a kernel once (because you are not sure
1678 if it works, or if you want to boot a known bad kernel to provide
1679 debugging information) run
1680 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1681 nextboot -k testkernel
1683 To just build a kernel when you know that it won't mess you up
1684 --------------------------------------------------------------
1685 This assumes you are already running a CURRENT system. Replace
1686 ${arch} with the architecture of your machine (e.g. "i386",
1687 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1689 cd src/sys/${arch}/conf
1690 config KERNEL_NAME_HERE
1691 cd ../compile/KERNEL_NAME_HERE
1696 If this fails, go to the "To build a kernel" section.
1698 To rebuild everything and install it on the current system.
1699 -----------------------------------------------------------
1700 # Note: sometimes if you are running current you gotta do more than
1701 # is listed here if you are upgrading from a really old current.
1703 <make sure you have good level 0 dumps>
1705 make kernel KERNCONF=YOUR_KERNEL_HERE
1707 <reboot in single user> [3]
1714 To cross-install current onto a separate partition
1715 --------------------------------------------------
1716 # In this approach we use a separate partition to hold
1717 # current's root, 'usr', and 'var' directories. A partition
1718 # holding "/", "/usr" and "/var" should be about 2GB in
1721 <make sure you have good level 0 dumps>
1724 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1725 <maybe newfs current's root partition>
1726 <mount current's root partition on directory ${CURRENT_ROOT}>
1727 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1728 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1729 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1730 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1731 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1732 <reboot into current>
1733 <do a "native" rebuild/install as described in the previous section>
1734 <maybe install compatibility libraries from ports/misc/compat*>
1738 To upgrade in-place from stable to current
1739 ----------------------------------------------
1740 <make sure you have good level 0 dumps>
1742 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1744 <reboot in single user> [3]
1751 Make sure that you've read the UPDATING file to understand the
1752 tweaks to various things you need. At this point in the life
1753 cycle of current, things change often and you are on your own
1754 to cope. The defaults can also change, so please read ALL of
1755 the UPDATING entries.
1757 Also, if you are tracking -current, you must be subscribed to
1758 freebsd-current@freebsd.org. Make sure that before you update
1759 your sources that you have read and understood all the recent
1760 messages there. If in doubt, please track -stable which has
1761 much fewer pitfalls.
1763 [1] If you have third party modules, such as vmware, you
1764 should disable them at this point so they don't crash your
1767 [3] From the bootblocks, boot -s, and then do
1772 adjkerntz -i # if CMOS is wall time
1773 Also, when doing a major release upgrade, it is required that
1774 you boot into single user mode to do the installworld.
1776 [4] Note: This step is non-optional. Failure to do this step
1777 can result in a significant reduction in the functionality of the
1778 system. Attempting to do it by hand is not recommended and those
1779 that pursue this avenue should read this file carefully, as well
1780 as the archives of freebsd-current and freebsd-hackers mailing lists
1781 for potential gotchas. The -U option is also useful to consider.
1782 See mergemaster(8) for more information.
1784 [5] Usually this step is a noop. However, from time to time
1785 you may need to do this if you get unknown user in the following
1786 step. It never hurts to do it all the time. You may need to
1787 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1788 install) after the buildworld before this step if you last updated
1789 from current before 20130425 or from -stable before 20130430.
1791 [6] This only deletes old files and directories. Old libraries
1792 can be deleted by "make delete-old-libs", but you have to make
1793 sure that no program is using those libraries anymore.
1795 [8] In order to have a kernel that can run the 4.x binaries needed to
1796 do an installworld, you must include the COMPAT_FREEBSD4 option in
1797 your kernel. Failure to do so may leave you with a system that is
1798 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1799 required to run the 5.x binaries on more recent kernels. And so on
1800 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1802 Make sure that you merge any new devices from GENERIC since the
1803 last time you updated your kernel config file.
1805 [9] When checking out sources, you must include the -P flag to have
1806 cvs prune empty directories.
1808 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1809 "?=" instead of the "=" assignment operator, so that buildworld can
1810 override the CPUTYPE if it needs to.
1812 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1813 not on the command line, or in /etc/make.conf. buildworld will
1814 warn if it is improperly defined.
1817 This file contains a list, in reverse chronological order, of major
1818 breakages in tracking -current. It is not guaranteed to be a complete
1819 list of such breakages, and only contains entries since September 23, 2011.
1820 If you need to see UPDATING entries from before that date, you will need
1821 to fetch an UPDATING file from an older FreeBSD release.
1823 Copyright information:
1825 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1827 Redistribution, publication, translation and use, with or without
1828 modification, in full or in part, in any form or format of this
1829 document are permitted without further permission from the author.
1831 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1832 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1833 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1834 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1835 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1836 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1837 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1838 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1839 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1840 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1841 POSSIBILITY OF SUCH DAMAGE.
1843 Contact Warner Losh if you have any questions about your use of