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