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 20190514 p10 FreeBSD-EN-19:08.tzdata
20 FreeBSD-EN-19:09.xinstall
27 Import tzdata 2019a. [EN-19:08.tzdata]
29 Fix install with partially matching relative paths. [EN-19:09.xinstall]
31 Fix multiple vulnerabilities in hostapd/wpa_supplicant. [SA-19:03.wpa]
33 Fix authenticated denial of service in ntpd. [SA-19:04.ntp]
35 Fix IPv6 fragment reassembly in pf. [SA-19:05.pf]
37 Fix ICMP/ICMP6 packet filter bypass in pf. [SA-19:06.pf]
39 Add mitigations for Microarchitectural Data Sampling. [SA-19:07.mds]
42 20190205 p9 FreeBSD-SA-19:01.syscall
44 amd64: clear callee-preserved registers on syscall exit
47 20190109 p8 FreeBSD-EN-19:03.sqlite
48 FreeBSD-EN-19:04.tzdata
49 FreeBSD-EN-19:05.kqueue
51 Update sqlite3-3.20.0 --> sqlite3-3.26.0 (3260000) [EN-19:03.sqlite]
53 Import tzdata 2018h, 2018i [EN-19:04.tzdata]
55 Avoid unsynchronized updates to kn_status. [EN-19:05.kqueue]
58 20181219 p7 FreeBSD-SA-18:15.bootpd
59 FreeBSD-EN-18:16.ptrace
63 bootpd: validate hardware type [SA-18:15.bootpd]
65 Only clear a pending thread event if one is pending. [EN-18:16.ptrace]
67 Update the free page count when blacklisting pages. [EN-18:17.vm]
69 Resolve a hang in ZFS during vnode reclamation [EN-18:18.zfs]
72 20181204 p6 FreeBSD-SA-18:14.bhyve
74 Fix insufficient bounds checking in bhyve(8) device model.
77 20181127 p5 FreeBSD-SA-18:13.nfs
79 FreeBSD-EN-18:14.tzdata
80 FreeBSD-EN-18:15.loader
82 Fix multiple vulnerabilities in NFS server code. [SA-18:13.nfs]
84 Fix ICMP buffer underwrite. [EN-18:13.icmp]
86 Timezone database information update. [EN-18:14.tzdata]
88 Fix deferred kernel loading breaks loader password. [EN-18:15.loader]
90 20180927 p4 FreeBSD-EN-18:09.ip
91 FreeBSD-EN-18:10.syscall
92 FreeBSD-EN-18:11.listen
95 Fix regression in IPv6 fragment reassembly. [EN-18:09.ip]
97 Fix NULL pointer dereference in freebsd4_getfsstat. [EN-18:10.syscall]
99 Fix DoS in listen syscall over IPv6 socket. [EN-18:11.listen]
101 Fix small kernel memory disclosures. [EN-18:12.mem]
103 20180912 p3 FreeBSD-SA-18:12.elf
104 FreeBSD-EN-18:08.lazyfpu
106 Fix improper elf header parsing. [SA-18:12.elf]
108 Fix regression in Lazy FPU remediation. [EN-18:08.lazyfpu]
110 20180814 p2 FreeBSD-SA-18:08.tcp [revised]
111 FreeBSD-SA-18:09.l1tf
113 FreeBSD-SA-18:11.hostapd
115 Revise manual pages. [SA-18:08.tcp]
117 Fix L1 Terminal Fault (L1TF) kernel information disclosure.
120 Fix resource exhaustion in IP fragment reassembly. [SA-18:10.ip]
122 Fix unauthenticated EAPOL-Key decryption vulnerability.
125 20180806 p1 FreeBSD-SA-18:08.tcp
127 Fix resource exhaustion in TCP reassembly.
133 The tz database (tzdb) has been updated to 2018e. This version more
134 correctly models time stamps in time zones with negative DST such as
135 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
136 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
137 time zone abbreviations and the tm_isdst flag.
140 The use of RSS hash from the network card aka flowid has been
141 disabled by default for lagg(4) as it's currently incompatible with
142 the lacp and loadbalance protocols.
144 This can be re-enabled by setting the following in loader.conf:
145 net.link.lagg.default_use_flowid="1"
148 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
149 6.0.0. Please see the 20141231 entry below for information about
150 prerequisites and upgrading, if you are not already using clang 3.5.0
154 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
155 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
156 to WITH/OUT_LOADER_GELI.
159 The geli password typed at boot is now hidden. To restore the previous
160 behavior, see geli(8) for configuration options.
162 The SW_WATCHDOG option is no longer necessary to enable the
163 hardclock-based software watchdog if no hardware watchdog is
164 configured. As before, SW_WATCHDOG will cause the software
165 watchdog to be enabled even if a hardware watchdog is configured.
168 lint(1) binaries and library are no longer built by default. To
169 enable building them, define WITH_LINT in src.conf. If you are using
170 a FreeBSD 12 or later system to build 11-stable, you may need to
171 install a lint(1) binary to use WITH_LINT.
174 When building multiple kernels using KERNCONF, non-existent KERNCONF
175 files will produce an error and buildkernel will fail. Previously
176 missing KERNCONF files silently failed giving no indication as to
177 why, only to subsequently discover during installkernel that the
178 desired kernel was never built in the first place.
181 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
182 Please see the 20141231 entry below for information about prerequisites
183 and upgrading, if you are not already using clang 3.5.0 or higher.
186 Since the switch to GPT disk labels, fsck for UFS/FFS has been
187 unable to automatically find alternate superblocks. As of r322806,
188 the information needed to find alternate superblocks has been
189 moved to the end of the area reserved for the boot block.
190 Filesystems created with a newfs of this vintage or later
191 will create the recovery information. If you have a filesystem
192 created prior to this change and wish to have a recovery block
193 created for your filesystem, you can do so by running fsck in
194 forground mode (i.e., do not use the -p or -y options). As it
195 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
196 to which you should answer yes.
199 arm64 builds now use the base system LLD 4.0.0 linker by default,
200 instead of requiring that the aarch64-binutils port or package be
201 installed. To continue using aarch64-binutils, set
202 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
205 The ctl.ko module no longer implements the iSCSI target frontend:
206 cfiscsi.ko does instead.
208 If building cfiscsi.ko as a kernel module, the module can be loaded
209 via one of the following methods:
210 - `cfiscsi_load="YES"` in loader.conf(5).
211 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
212 - ctladm(8)/ctld(8), when compiled with iSCSI support
213 (`WITH_ISCSI=yes` in src.conf(5))
215 Please see cfiscsi(4) for more details.
218 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
219 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
220 same source (previously, the dependency of mmcsd.ko on mmc.ko was
221 missing, but mmcsd.ko now will refuse to load if it is incompatible
225 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
226 use any explicitly assigned loopback address available in the jail
227 instead of using the first assigned address of the jail.
230 As of r316810 for ipfilter, keep frags is no longer assumed when
231 keep state is specified in a rule. r316810 aligns ipfilter with
232 documentation in man pages separating keep frags from keep state.
233 This allows keep state to specified without forcing keep frags
234 and allows keep frags to be specified independently of keep state.
235 To maintain previous behaviour, also specify keep frags with
236 keep state (as documented in ipf.conf.5).
239 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
240 Please see the 20141231 entry below for information about prerequisites
241 and upgrading, if you are not already using clang 3.5.0 or higher.
244 The code that provides support for ZFS .zfs/ directory functionality
245 has been reimplemented. It's not possible now to create a snapshot
246 by mkdir under .zfs/snapshot/. That should be the only user visible
250 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
251 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
252 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
253 and now NAT-T is supported by default. Security associations now use
254 the single namespace for SPI allocation, so if you use several manually
255 configured security associations with the same SPI, this configuration
259 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
260 Please see the 20141231 entry below for information about prerequisites
261 and upgrading, if you are not already using clang 3.5.0 or higher.
264 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
265 Please see the 20141231 entry below for information about prerequisites
266 and upgrading, if you are not already using clang 3.5.0 or higher.
269 The layout of the pmap structure has changed for powerpc to put the pmap
270 statistics at the front for all CPU variations. libkvm(3) and all tools
271 that link against it need to be recompiled.
274 isl(4) and cyapa(4) drivers now require a new driver,
275 chromebook_platform(4), to work properly on Chromebook-class hardware.
276 On other types of hardware the drivers may need to be configured using
277 device hints. Please see the corresponding manual pages for details.
280 Relocatable object files with the extension of .So have been renamed
281 to use an extension of .pico instead. The purpose of this change is
282 to avoid a name clash with shared libraries on case-insensitive file
283 systems. On those file systems, foo.So is the same file as foo.so.
286 The libc stub for the pipe(2) system call has been replaced with
287 a wrapper that calls the pipe2(2) system call and the pipe(2)
288 system call is now only implemented by the kernels that include
289 "options COMPAT_FREEBSD10" in their config file (this is the
290 default). Users should ensure that this option is enabled in
291 their kernel or upgrade userspace to r302092 before upgrading their
295 CAM will now strip leading spaces from SCSI disks' serial numbers.
296 This will effect users who create UFS filesystems on SCSI disks using
297 those disk's diskid device nodes. For example, if /etc/fstab
298 previously contained a line like
299 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
300 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
301 transforms like gmirror may also be affected. ZFS users should
305 The bitstring(3) API has been updated with new functionality and
306 improved performance. But it is binary-incompatible with the old API.
307 Objects built with the new headers may not be linked against objects
308 built with the old headers.
311 The brk and sbrk functions have been removed from libc on arm64.
312 Binutils from ports has been updated to not link to these
313 functions and should be updated to the latest version before
314 installing a new libc.
317 The armv6 port now defaults to hard float ABI. Limited support
318 for running both hardfloat and soft float on the same system
319 is available using the libraries installed with -DWITH_LIBSOFT.
320 This has only been tested as an upgrade path for installworld
321 and packages may fail or need manual intervention to run. New
322 packages will be needed.
324 To update an existing self-hosted armv6hf system, you must add
325 TARGET_ARCH=armv6 on the make command line for both the build
326 and the install steps.
329 Kernel modules compiled outside of a kernel build now default to
330 installing to /boot/modules instead of /boot/kernel. Many kernel
331 modules built this way (such as those in ports) already overrode
332 KMODDIR explicitly to install into /boot/modules. However,
333 manually building and installing a module from /sys/modules will
334 now install to /boot/modules instead of /boot/kernel.
337 The CAM I/O scheduler has been committed to the kernel. There should be
338 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
339 list of known rogues that claim support for this but actually corrupt
340 data is believed to be complete, be on the lookout for data
341 corruption. The known rogue list is believed to be complete:
343 o Crucial MX100, M550 drives with MU01 firmware.
344 o Micron M510 and M550 drives with MU01 firmware.
345 o Micron M500 prior to MU07 firmware
346 o Samsung 830, 840, and 850 all firmwares
347 o FCCT M500 all firmwares
349 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
350 with working NCQ TRIM. For Micron branded drives, see your sales rep for
351 updated firmware. Black listed drives will work correctly because these
352 drives work correctly so long as no NCQ TRIMs are sent to them. Given
353 this list is the same as found in Linux, it's believed there are no
354 other rogues in the market place. All other models from the above
357 To be safe, if you are at all concerned, you can quirk each of your
358 drives to prevent NCQ from being sent by setting:
359 kern.cam.ada.X.quirks="0x2"
360 in loader.conf. If the drive requires the 4k sector quirk, set the
364 The FAST_DEPEND build option has been removed and its functionality is
365 now the one true way. The old mkdep(1) style of 'make depend' has
366 been removed. See 20160311 for further details.
369 Resource range types have grown from unsigned long to uintmax_t. All
370 drivers, and anything using libdevinfo, need to be recompiled.
373 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
374 builds. It no longer runs mkdep(1) during 'make depend', and the
375 'make depend' stage can safely be skipped now as it is auto ran
376 when building 'make all' and will generate all SRCS and DPSRCS before
377 building anything else. Dependencies are gathered at compile time with
378 -MF flags kept in separate .depend files per object file. Users should
379 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
383 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
384 kernel modules. Therefore, if you load any kernel modules at boot time,
385 please install the boot loaders after you install the kernel, but before
389 make kernel KERNCONF=YOUR_KERNEL_HERE
390 make -C sys/boot install
391 <reboot in single user>
393 Then follow the usual steps, described in the General Notes section,
397 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
398 see the 20141231 entry below for information about prerequisites and
399 upgrading, if you are not already using clang 3.5.0 or higher.
402 The AIO subsystem is now a standard part of the kernel. The
403 VFS_AIO kernel option and aio.ko kernel module have been removed.
404 Due to stability concerns, asynchronous I/O requests are only
405 permitted on sockets and raw disks by default. To enable
406 asynchronous I/O requests on all file types, set the
407 vfs.aio.enable_unsafe sysctl to a non-zero value.
410 The ELF object manipulation tool objcopy is now provided by the
411 ELF Tool Chain project rather than by GNU binutils. It should be a
412 drop-in replacement, with the addition of arm64 support. The
413 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
414 to obtain the GNU version if necessary.
417 Building ZFS pools on top of zvols is prohibited by default. That
418 feature has never worked safely; it's always been prone to deadlocks.
419 Using a zvol as the backing store for a VM guest's virtual disk will
420 still work, even if the guest is using ZFS. Legacy behavior can be
421 restored by setting vfs.zfs.vol.recursive=1.
424 The NONE and HPN patches has been removed from OpenSSH. They are
425 still available in the security/openssh-portable port.
428 With the addition of ypldap(8), a new _ypldap user is now required
429 during installworld. "mergemaster -p" can be used to add the user
430 prior to installworld, as documented in the handbook.
433 The tftp loader (pxeboot) now uses the option root-path directive. As a
434 consequence it no longer looks for a pxeboot.4th file on the tftp
435 server. Instead it uses the regular /boot infrastructure as with the
439 The code to start recording plug and play data into the modules has
440 been committed. While the old tools will properly build a new kernel,
441 a number of warnings about "unknown metadata record 4" will be produced
442 for an older kldxref. To avoid such warnings, make sure to rebuild
443 the kernel toolchain (or world). Make sure that you have r292078 or
444 later when trying to build 292077 or later before rebuilding.
447 Debug data files are now built by default with 'make buildworld' and
448 installed with 'make installworld'. This facilitates debugging but
449 requires more disk space both during the build and for the installed
450 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
454 r291527 changed the internal interface between the nfsd.ko and
455 nfscommon.ko modules. As such, they must both be upgraded to-gether.
456 __FreeBSD_version has been bumped because of this.
459 Add support for unicode collation strings leads to a change of
460 order of files listed by ls(1) for example. To get back to the old
461 behaviour, set LC_COLLATE environment variable to "C".
463 Databases administrators will need to reindex their databases given
464 collation results will be different.
466 Due to a bug in install(1) it is recommended to remove the ancient
467 locales before running make installworld.
469 rm -rf /usr/share/locale/*
472 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
473 libcrypto.so.7 or libssl.so.7 must be recompiled.
476 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
477 Kernel modules isp_2400_multi and isp_2500_multi were removed and
478 should be replaced with isp_2400 and isp_2500 modules respectively.
481 The build previously allowed using 'make -n' to not recurse into
482 sub-directories while showing what commands would be executed, and
483 'make -n -n' to recursively show commands. Now 'make -n' will recurse
484 and 'make -N' will not.
487 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
488 and etcupdate will now use this file. A custom sendmail.cf is now
489 updated via this mechanism rather than via installworld. If you had
490 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
491 want to remove the exclusion or change it to "always install".
492 /etc/mail/sendmail.cf is now managed the same way regardless of
493 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
494 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
497 Compatibility shims for legacy ATA device names have been removed.
498 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
499 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
500 environment variables, /dev/ad* and /dev/ar* symbolic links.
503 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
504 Please see the 20141231 entry below for information about prerequisites
505 and upgrading, if you are not already using clang 3.5.0 or higher.
508 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
509 and renamed from .symbols to .debug. This reduces the size requirements
510 on the boot partition or file system and provides consistency with
511 userland debug files.
513 When using the supported kernel installation method the
514 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
515 as is done with /boot/kernel.
517 Developers wishing to maintain the historical behavior of installing
518 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
521 The wireless drivers had undergone changes that remove the 'parent
522 interface' from the ifconfig -l output. The rc.d network scripts
523 used to check presence of a parent interface in the list, so old
524 scripts would fail to start wireless networking. Thus, etcupdate(3)
525 or mergemaster(8) run is required after kernel update, to update your
526 rc.d scripts in /etc.
529 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
530 These configurations are now automatically interpreted as
531 'scrub fragment reassemble'.
534 Kernel-loadable modules for the random(4) device are back. To use
535 them, the kernel must have
538 options RANDOM_LOADABLE
540 kldload(8) can then be used to load random_fortuna.ko
541 or random_yarrow.ko. Please note that due to the indirect
542 function calls that the loadable modules need to provide,
543 the build-in variants will be slightly more efficient.
545 The random(4) kernel option RANDOM_DUMMY has been retired due to
546 unpopularity. It was not all that useful anyway.
549 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
550 Control over building the ELF Tool Chain tools is now provided by
551 the WITHOUT_TOOLCHAIN knob.
554 The polarity of Pulse Per Second (PPS) capture events with the
555 uart(4) driver has been corrected. Prior to this change the PPS
556 "assert" event corresponded to the trailing edge of a positive PPS
557 pulse and the "clear" event was the leading edge of the next pulse.
559 As the width of a PPS pulse in a typical GPS receiver is on the
560 order of 1 millisecond, most users will not notice any significant
561 difference with this change.
563 Anyone who has compensated for the historical polarity reversal by
564 configuring a negative offset equal to the pulse width will need to
565 remove that workaround.
568 The default group assigned to /dev/dri entries has been changed
569 from 'wheel' to 'video' with the id of '44'. If you want to have
570 access to the dri devices please add yourself to the video group
573 # pw groupmod video -m $USER
576 The menu.rc and loader.rc files will now be replaced during
577 upgrades. Please migrate local changes to menu.rc.local and
578 loader.rc.local instead.
581 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
582 strings and strip have been removed. The src.conf(5) knob
583 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
586 As ZFS requires more kernel stack pages than is the default on some
587 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
588 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
590 Please consider using 'options KSTACK_PAGES=X' where X is greater
591 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
594 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
595 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
596 default, i.e., they will not contain "::". For example, instead
597 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
598 to have a more specific match, such as different map entries for
599 IPv6:0:0 vs IPv6:0. This change requires that configuration
600 data (including maps, files, classes, custom ruleset, etc.) must
601 use the same format, so make certain such configuration data is
602 upgrading. As a very simple check search for patterns like
603 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
604 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
605 the cf option UseCompressedIPv6Addresses.
608 The default kernel entropy-processing algorithm is now
609 Fortuna, replacing Yarrow.
611 Assuming you have 'device random' in your kernel config
612 file, the configurations allow a kernel option to override
613 this default. You may choose *ONE* of:
615 options RANDOM_YARROW # Legacy /dev/random algorithm.
616 options RANDOM_DUMMY # Blocking-only driver.
618 If you have neither, you get Fortuna. For most people,
619 read no further, Fortuna will give a /dev/random that works
620 like it always used to, and the difference will be irrelevant.
622 If you remove 'device random', you get *NO* kernel-processed
623 entropy at all. This may be acceptable to folks building
624 embedded systems, but has complications. Carry on reading,
625 and it is assumed you know what you need.
627 *PLEASE* read random(4) and random(9) if you are in the
628 habit of tweaking kernel configs, and/or if you are a member
629 of the embedded community, wanting specific and not-usual
630 behaviour from your security subsystems.
632 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
633 random', you will NOT have a functioning /dev/random, and
634 many cryptographic features will not work, including SSH.
635 You may also find strange behaviour from the random(3) set
636 of library functions, in particular sranddev(3), srandomdev(3)
637 and arc4random(3). The reason for this is that the KERN_ARND
638 sysctl only returns entropy if it thinks it has some to
639 share, and with RANDOM_DUMMY or no 'device random' this
643 An additional fix for the issue described in the 20150614 sendmail
644 entry below has been been committed in revision 284717.
647 FreeBSD's old make (fmake) has been removed from the system. It is
648 available as the devel/fmake port or via pkg install fmake.
651 The fix for the issue described in the 20150614 sendmail entry
652 below has been been committed in revision 284436. The work
653 around described in that entry is no longer needed unless the
654 default setting is overridden by a confDH_PARAMETERS configuration
655 setting of '5' or pointing to a 512 bit DH parameter file.
658 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
659 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
660 and devel/kyua to version 0.20+ and adjust any calling code to work
661 with Kyuafile and kyua.
664 The import of openssl to address the FreeBSD-SA-15:10.openssl
665 security advisory includes a change which rejects handshakes
666 with DH parameters below 768 bits. sendmail releases prior
667 to 8.15.2 (not yet released), defaulted to a 512 bit
668 DH parameter setting for client connections. To work around
669 this interoperability, sendmail can be configured to use a
670 2048 bit DH parameter by:
672 1. Edit /etc/mail/`hostname`.mc
673 2. If a setting for confDH_PARAMETERS does not exist or
674 exists and is set to a string beginning with '5',
676 3. If a setting for confDH_PARAMETERS exists and is set to
677 a file path, create a new file with:
678 openssl dhparam -out /path/to/file 2048
679 4. Rebuild the .cf file:
680 cd /etc/mail/; make; make install
682 cd /etc/mail/; make restart
684 A sendmail patch is coming, at which time this file will be
688 Generation of legacy formatted entries have been disabled by default
689 in pwd_mkdb(8), as all base system consumers of the legacy formatted
690 entries were converted to use the new format by default when the new,
691 machine independent format have been added and supported since FreeBSD
694 Please see the pwd_mkdb(8) manual page for further details.
697 Clang and llvm have been upgraded to 3.6.1 release. Please see the
698 20141231 entry below for information about prerequisites and upgrading,
699 if you are not already using 3.5.0 or higher.
702 TI platform code switched to using vendor DTS files and this update
703 may break existing systems running on Beaglebone, Beaglebone Black,
706 - dtb files should be regenerated/reinstalled. Filenames are the
707 same but content is different now
708 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
709 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
710 addressing scheme is now pin 25 on /dev/gpioc3.
711 - Pandaboard: /etc/ttys should be updated, serial console device is
712 now /dev/ttyu2, not /dev/ttyu0
715 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
716 If you need the GNU extension from groff soelim(1), install groff
717 from package: pkg install groff, or via ports: textproc/groff.
720 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
721 defined in symlink(7); previously symlinks were silently ignored.
724 The const qualifier has been removed from iconv(3) to comply with
725 POSIX. The ports tree is aware of this from r384038 onwards.
728 Libraries specified by LIBADD in Makefiles must have a corresponding
729 DPADD_<lib> variable to ensure correct dependencies. This is now
730 enforced in src.libnames.mk.
733 From legacy ata(4) driver was removed support for SATA controllers
734 supported by more functional drivers ahci(4), siis(4) and mvs(4).
735 Kernel modules ataahci and ataadaptec were removed completely,
736 replaced by ahci and mvs modules respectively.
739 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
740 the 20141231 entry below for information about prerequisites and
741 upgrading, if you are not already using 3.5.0 or higher.
744 The 32-bit PowerPC kernel has been changed to a position-independent
745 executable. This can only be booted with a version of loader(8)
746 newer than January 31, 2015, so make sure to update both world and
747 kernel before rebooting.
750 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
751 but before r278950, the RNG was not seeded properly. Immediately
752 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
753 ssh keys or openssl keys) that were generated w/ a kernel from that
754 range. This does not affect programs that directly used /dev/random
755 or /dev/urandom. All userland uses of arc4random(3) are affected.
758 The autofs(4) ABI was changed in order to restore binary compatibility
759 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
763 The powerpc64 kernel has been changed to a position-independent
764 executable. This can only be booted with a new version of loader(8),
765 so make sure to update both world and kernel before rebooting.
768 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
769 only release, no new features have been added. Please see the 20141231
770 entry below for information about prerequisites and upgrading, if you
771 are not already using 3.5.0.
774 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
775 taken from the ELF Tool Chain project rather than GNU binutils. They
776 should be drop-in replacements, with the addition of arm64 support.
777 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
778 binutils tools, if necessary. See 20150805 for updated information.
781 The default Unbound configuration now enables remote control
782 using a local socket. Users who have already enabled the
783 local_unbound service should regenerate their configuration
784 by running "service local_unbound setup" as root.
787 The GNU texinfo and GNU info pages have been removed.
788 To be able to view GNU info pages please install texinfo from ports.
791 Clang, llvm and lldb have been upgraded to 3.5.0 release.
793 As of this release, a prerequisite for building clang, llvm and lldb is
794 a C++11 capable compiler and C++11 standard library. This means that to
795 be able to successfully build the cross-tools stage of buildworld, with
796 clang as the bootstrap compiler, your system compiler or cross compiler
797 should either be clang 3.3 or later, or gcc 4.8 or later, and your
798 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
801 On any standard FreeBSD 10.x or 11.x installation, where clang and
802 libc++ are on by default (that is, on x86 or arm), this should work out
805 On 9.x installations where clang is enabled by default, e.g. on x86 and
806 powerpc, libc++ will not be enabled by default, so libc++ should be
807 built (with clang) and installed first. If both clang and libc++ are
808 missing, build clang first, then use it to build libc++.
810 On 8.x and earlier installations, upgrade to 9.x first, and then follow
811 the instructions for 9.x above.
813 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
814 default, and do not build clang.
816 Many embedded systems are resource constrained, and will not be able to
817 build clang in a reasonable time, or in some cases at all. In those
818 cases, cross building bootable systems on amd64 is a workaround.
820 This new version of clang introduces a number of new warnings, of which
821 the following are most likely to appear:
825 This warns in two cases, for both C and C++:
826 * When the code is trying to take the absolute value of an unsigned
827 quantity, which is effectively a no-op, and almost never what was
828 intended. The code should be fixed, if at all possible. If you are
829 sure that the unsigned quantity can be safely cast to signed, without
830 loss of information or undefined behavior, you can add an explicit
831 cast, or disable the warning.
833 * When the code is trying to take an absolute value, but the called
834 abs() variant is for the wrong type, which can lead to truncation.
835 If you want to disable the warning instead of fixing the code, please
836 make sure that truncation will not occur, or it might lead to unwanted
839 -Wtautological-undefined-compare and
840 -Wundefined-bool-conversion
842 These warn when C++ code is trying to compare 'this' against NULL, while
843 'this' should never be NULL in well-defined C++ code. However, there is
844 some legacy (pre C++11) code out there, which actively abuses this
845 feature, which was less strictly defined in previous C++ versions.
847 Squid and openjdk do this, for example. The warning can be turned off
848 for C++98 and earlier, but compiling the code in C++11 mode might result
849 in unexpected behavior; for example, the parts of the program that are
850 unreachable could be optimized away.
853 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
854 kernel sources have been removed. The .h files remain, since some
855 utilities include them. This will need to be fixed later.
856 If "mount -t oldnfs ..." is attempted, it will fail.
857 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
858 the utilities will report errors.
861 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
862 directories to top level SUBDIR variable when their parent
863 directory is included in LOCAL_DIRS. Users with build systems with
864 such hierarchies and without SUBDIR entries in the parent
865 directory Makefiles should add them or add the directories to
869 faith(4) and faithd(8) have been removed from the base system. Faith
870 has been obsolete for a very long time.
873 vt(4), the new console driver, is enabled by default. It brings
874 support for Unicode and double-width characters, as well as
875 support for UEFI and integration with the KMS kernel video
878 You may need to update your console settings in /etc/rc.conf,
879 most probably the keymap. During boot, /etc/rc.d/syscons will
880 indicate what you need to do.
882 vt(4) still has issues and lacks some features compared to
883 syscons(4). See the wiki for up-to-date information:
884 https://wiki.freebsd.org/Newcons
886 If you want to keep using syscons(4), you can do so by adding
887 the following line to /boot/loader.conf:
891 pjdfstest has been integrated into kyua as an opt-in test suite.
892 Please see share/doc/pjdfstest/README for more details on how to
896 gperf has been removed from the base system for architectures
897 that use clang. Ports that require gperf will obtain it from the
901 pjdfstest has been moved from tools/regression/pjdfstest to
905 At svn r271982, The default linux compat kernel ABI has been adjusted
906 to 2.6.18 in support of the linux-c6 compat ports infrastructure
907 update. If you wish to continue using the linux-f10 compat ports,
908 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
909 encouraged to update their linux-compat packages to linux-c6 during
910 their next update cycle.
913 The ofwfb driver, used to provide a graphics console on PowerPC when
914 using vt(4), no longer allows mmap() of all physical memory. This
915 will prevent Xorg on PowerPC with some ATI graphics cards from
916 initializing properly unless x11-servers/xorg-server is updated to
920 The xdev targets have been converted to using TARGET and
921 TARGET_ARCH instead of XDEV and XDEV_ARCH.
924 The default unbound configuration has been modified to address
925 issues with reverse lookups on networks that use private
926 address ranges. If you use the local_unbound service, run
927 "service local_unbound setup" as root to regenerate your
928 configuration, then "service local_unbound reload" to load the
932 The GNU texinfo and GNU info pages are not built and installed
933 anymore, WITH_INFO knob has been added to allow to built and install
935 UPDATE: see 20150102 entry on texinfo's removal
938 The GNU readline library is now an INTERNALLIB - that is, it is
939 statically linked into consumers (GDB and variants) in the base
940 system, and the shared library is no longer installed. The
941 devel/readline port is available for third party software that
945 The Itanium architecture (ia64) has been removed from the list of
946 known architectures. This is the first step in the removal of the
950 Commit r268115 has added NFSv4.1 server support, merged from
951 projects/nfsv4.1-server. Since this includes changes to the
952 internal interfaces between the NFS related modules, a full
953 build of the kernel and modules will be necessary.
954 __FreeBSD_version has been bumped.
957 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
958 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
959 which differs from the behaviour controlled by this knob.)
962 Maximal length of the serial number in CTL was increased from 16 to
963 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
964 and ctld, need to be rebuilt to work with a new kernel.
967 The libatf-c and libatf-c++ major versions were downgraded to 0 and
968 1 respectively to match the upstream numbers. They were out of
969 sync because, when they were originally added to FreeBSD, the
970 upstream versions were not respected. These libraries are private
971 and not yet built by default, so renumbering them should be a
972 non-issue. However, unclean source trees will yield broken test
973 programs once the operator executes "make delete-old-libs" after a
976 Additionally, the atf-sh binary was made private by moving it into
977 /usr/libexec/. Already-built shell test programs will keep the
978 path to the old binary so they will break after "make delete-old"
981 If you are using WITH_TESTS=yes (not the default), wipe the object
982 tree and rebuild from scratch to prevent spurious test failures.
983 This is only needed once: the misnumbered libraries and misplaced
984 binaries have been added to OptionalObsoleteFiles.inc so they will
985 be removed during a clean upgrade.
988 Clang and llvm have been upgraded to 3.4.1 release.
991 We bogusly installed src.opts.mk in /usr/share/mk. This file should
992 be removed to avoid issues in the future (and has been added to
996 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
997 past, it affected all builds that used the bsd.*.mk files. The old
998 behavior was a bug, but people may have relied upon it. To get this
999 behavior back, you can .include /etc/src.conf from /etc/make.conf
1000 (which is still global and isn't changed). This also changes the
1001 behavior of incremental builds inside the tree of individual
1002 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1003 Although this has survived make universe and some upgrade scenarios,
1004 other upgrade scenarios may have broken. At least one form of
1005 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1006 as well... In cases where MAKESYSPATH isn't working with this
1007 setting, you'll need to set it to the full path to your tree.
1009 One side effect of all this cleaning up is that bsd.compiler.mk
1010 is no longer implicitly included by bsd.own.mk. If you wish to
1011 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1015 The lindev device has been removed since /dev/full has been made a
1016 standard device. __FreeBSD_version has been bumped.
1019 The knob WITHOUT_VI was added to the base system, which controls
1020 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1021 in order to reorder files share/termcap and didn't build ex(1) as a
1022 build tool, so building/installing with WITH_VI is highly advised for
1023 build hosts for older releases.
1025 This issue has been fixed in stable/9 and stable/10 in r277022 and
1026 r276991, respectively.
1029 The YES_HESIOD knob has been removed. It has been obsolete for
1030 a decade. Please move to using WITH_HESIOD instead or your builds
1031 will silently lack HESIOD.
1034 The uart(4) driver has been changed with respect to its handling
1035 of the low-level console. Previously the uart(4) driver prevented
1036 any process from changing the baudrate or the CLOCAL and HUPCL
1037 control flags. By removing the restrictions, operators can make
1038 changes to the serial console port without having to reboot.
1039 However, when getty(8) is started on the serial device that is
1040 associated with the low-level console, a misconfigured terminal
1041 line in /etc/ttys will now have a real impact.
1042 Before upgrading the kernel, make sure that /etc/ttys has the
1043 serial console device configured as 3wire without baudrate to
1044 preserve the previous behaviour. E.g:
1045 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1048 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1049 to improve performance. To re-enable it, if needed, run rpcbind
1050 with command line option -W.
1053 Switched back to the GPL dtc compiler due to updates in the upstream
1054 dts files not being supported by the BSDL dtc compiler. You will need
1055 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1056 may result while building dtb files during a kernel build if you fail
1057 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1060 Clang and llvm have been upgraded to 3.4 release.
1063 The nve(4) driver has been removed. Please use the nfe(4) driver
1064 for NVIDIA nForce MCP Ethernet adapters instead.
1067 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1068 This could cause certain C++ applications using shared libraries built
1069 against the previous version of libc++ to crash. The incompatibility
1070 has now been fixed, but any C++ applications or shared libraries built
1071 between r261283 and r261801 should be recompiled.
1074 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1075 capability mode support. Please note that enabling the feature in
1076 kernel is still highly recommended.
1079 OpenSSH is now built with sandbox support, and will use sandbox as
1080 the default privilege separation method. This requires Capsicum
1081 capability mode support in kernel.
1084 The libelf and libdwarf libraries have been updated to newer
1085 versions from upstream. Shared library version numbers for
1086 these two libraries were bumped. Any ports or binaries
1087 requiring these two libraries should be recompiled.
1088 __FreeBSD_version is bumped to 1100006.
1091 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1092 instead of providing an explicit one, this would prevent such
1093 Makefile from providing its own Kyuafile in the future during
1094 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1095 intervention is needed to clean an objdir if you use NO_CLEAN:
1096 # find /usr/obj -name Kyuafile | xargs rm -f
1099 The behavior of gss_pseudo_random() for the krb5 mechanism
1100 has changed, for applications requesting a longer random string
1101 than produced by the underlying enctype's pseudo-random() function.
1102 In particular, the random string produced from a session key of
1103 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1104 be different at the 17th octet and later, after this change.
1105 The counter used in the PRF+ construction is now encoded as a
1106 big-endian integer in accordance with RFC 4402.
1107 __FreeBSD_version is bumped to 1100004.
1110 The WITHOUT_ATF build knob has been removed and its functionality
1111 has been subsumed into the more generic WITHOUT_TESTS. If you were
1112 using the former to disable the build of the ATF libraries, you
1113 should change your settings to use the latter.
1116 The default version of mtree is nmtree which is obtained from
1117 NetBSD. The output is generally the same, but may vary
1118 slightly. If you found you need identical output adding
1119 "-F freebsd9" to the command line should do the trick. For the
1120 time being, the old mtree is available as fmtree.
1123 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1124 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1125 1.1.4_8 and verify bsdyml not linked in, before running "make
1127 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1129 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1132 The stable/10 branch has been created in subversion from head
1136 The rc.d/jail script has been updated to support jail(8)
1137 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1138 for per-jail configuration are automatically converted to
1139 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1140 This is transparently backward compatible. See below about some
1141 incompatibilities and rc.conf(5) manual page for more details.
1143 These variables are now deprecated in favor of jail(8) configuration
1144 file. One can use "rc.d/jail config <jname>" command to generate
1145 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1146 running the jail(8) utility. The default pathname of the
1147 configuration file is /etc/jail.conf and can be specified by
1148 using $jail_conf or $jail_<jname>_conf variables.
1150 Please note that jail_devfs_ruleset accepts an integer at
1151 this moment. Please consider to rewrite the ruleset name
1155 BIND has been removed from the base system. If all you need
1156 is a local resolver, simply enable and start the local_unbound
1157 service instead. Otherwise, several versions of BIND are
1158 available in the ports tree. The dns/bind99 port is one example.
1160 With this change, nslookup(1) and dig(1) are no longer in the base
1161 system. Users should instead use host(1) and drill(1) which are
1162 in the base system. Alternatively, nslookup and dig can
1163 be obtained by installing the dns/bind-tools port.
1166 With the addition of unbound(8), a new unbound user is now
1167 required during installworld. "mergemaster -p" can be used to
1168 add the user prior to installworld, as documented in the handbook.
1171 OpenSSH is now built with DNSSEC support, and will by default
1172 silently trust signed SSHFP records. This can be controlled with
1173 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1174 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1177 The GNU Compiler Collection and C++ standard library (libstdc++)
1178 are no longer built by default on platforms where clang is the system
1179 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1180 options in src.conf.
1183 The PROCDESC kernel option is now part of the GENERIC kernel
1184 configuration and is required for the rwhod(8) to work.
1185 If you are using custom kernel configuration, you should include
1189 The API and ABI related to the Capsicum framework was modified
1190 in backward incompatible way. The userland libraries and programs
1191 have to be recompiled to work with the new kernel. This includes the
1192 following libraries and programs, but the whole buildworld is
1193 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1194 kdump, procstat, rwho, rwhod, uniq.
1197 AES-NI intrinsic support has been added to gcc. The AES-NI module
1198 has been updated to use this support. A new gcc is required to build
1199 the aesni module on both i386 and amd64.
1202 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1203 Thus "device padlock_rng" and "device rdrand_rng" should be
1204 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1207 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1208 enables just the iconv* functionality and is now on by default.
1209 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1210 compatibility. Set WITHOUT_ICONV to build the old way.
1211 If you have been using WITH_ICONV before, you will very likely
1212 need to turn on WITH_LIBICONV_COMPAT.
1215 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1216 Illumos origin, including ZFS. If you have INVARIANTS in your
1217 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1219 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1220 locks if WITNESS option was set. Because that generated a lot of
1221 witness(9) reports and all of them were believed to be false
1222 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1223 can be used to achieve the previous behavior.
1226 Timer values in IPv6 data structures now use time_uptime instead
1227 of time_second. Although this is not a user-visible functional
1228 change, userland utilities which directly use them---ndp(8),
1229 rtadvd(8), and rtsold(8) in the base system---need to be updated
1230 to r253970 or later.
1233 find -delete can now delete the pathnames given as arguments,
1234 instead of only files found below them or if the pathname did
1235 not contain any slashes. Formerly, the following error message
1238 find: -delete: <path>: relative path potentially not safe
1240 Deleting the pathnames given as arguments can be prevented
1241 without error messages using -mindepth 1 or by changing
1242 directory and passing "." as argument to find. This works in the
1243 old as well as the new version of find.
1246 Behavior of devfs rules path matching has been changed.
1247 Pattern is now always matched against fully qualified devfs
1248 path and slash characters must be explicitly matched by
1249 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1250 subdirectories must be reviewed.
1253 The default ARM ABI has changed to the ARM EABI. The old ABI is
1254 incompatible with the ARM EABI and all programs and modules will
1255 need to be rebuilt to work with a new kernel.
1257 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1259 NOTE: Support for the old ABI will be removed in the future and
1260 users are advised to upgrade.
1263 pkg_install has been disconnected from the build if you really need it
1264 you should add WITH_PKGTOOLS in your src.conf(5).
1267 Most of network statistics structures were changed to be able
1268 keep 64-bits counters. Thus all tools, that work with networking
1269 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1272 Fix a bug that allowed a tracing process (e.g. gdb) to write
1273 to a memory-mapped file in the traced process's address space
1274 even if neither the traced process nor the tracing process had
1275 write access to that file.
1278 CVS has been removed from the base system. An exact copy
1279 of the code is available from the devel/cvs port.
1282 Some people report the following error after the switch to bmake:
1284 make: illegal option -- J
1285 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1287 *** [buildworld] Error code 2
1289 this likely due to an old instance of make in
1290 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1291 which src/Makefile will use that blindly, if it exists, so if
1292 you see the above error:
1294 rm -rf `make -V MAKEPATH`
1299 Use bmake by default.
1300 Whereas before one could choose to build with bmake via
1301 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1302 make. The goal is to remove these knobs for 10-RELEASE.
1304 It is worth noting that bmake (like gmake) treats the command
1305 line as the unit of failure, rather than statements within the
1306 command line. Thus '(cd some/where && dosomething)' is safer
1307 than 'cd some/where; dosomething'. The '()' allows consistent
1308 behavior in parallel build.
1311 Fix a bug that allows NFS clients to issue READDIR on files.
1314 The WITHOUT_IDEA option has been removed because
1315 the IDEA patent expired.
1318 The sysctl which controls TRIM support under ZFS has been renamed
1319 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1323 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1324 rather than creating it's own in the temporary directory in
1325 order allow access to bootstrapped versions of tools such as
1326 install and mtree. When upgrading from version of FreeBSD where
1327 the install command does not support -l, you will need to
1328 install a new mergemaster command if mergemaster -p is required.
1329 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1333 Legacy ATA stack, disabled and replaced by new CAM-based one since
1334 FreeBSD 9.0, completely removed from the sources. Kernel modules
1335 atadisk and atapi*, user-level tools atacontrol and burncd are
1336 removed. Kernel option `options ATA_CAM` is now permanently enabled
1340 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1341 and socketpair(2). Software, in particular Kerberos, may
1342 automatically detect and use these during building. The resulting
1343 binaries will not work on older kernels.
1346 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1347 information, see the respective 20130304 entry).
1350 Recent commits to callout(9) changed the size of struct callout,
1351 so the KBI is probably heavily disturbed. Also, some functions
1352 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1353 by macros. Every kernel module using it won't load, so rebuild
1356 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1357 but does not initialize by default (because of the new CTL_DISABLE
1358 option) to save memory. To re-enable it, remove the CTL_DISABLE
1359 option from the kernel config file or set kern.cam.ctl.disable=0
1360 in /boot/loader.conf.
1363 The ctl device has been disabled in GENERIC for i386 and amd64.
1364 This was done due to the extra memory being allocated at system
1365 initialisation time by the ctl driver which was only used if
1366 a CAM target device was created. This makes a FreeBSD system
1367 unusable on 128MB or less of RAM.
1370 A new compression method (lz4) has been merged to -HEAD. Please
1371 refer to zpool-features(7) for more information.
1373 Please refer to the "ZFS notes" section of this file for information
1374 on upgrading boot ZFS pools.
1377 A BSD-licensed patch(1) variant has been added and is installed
1378 as bsdpatch, being the GNU version the default patch.
1379 To inverse the logic and use the BSD-licensed one as default,
1380 while having the GNU version installed as gnupatch, rebuild
1381 and install world with the WITH_BSD_PATCH knob set.
1384 Due to the use of the new -l option to install(1) during build
1385 and install, you must take care not to directly set the INSTALL
1386 make variable in your /etc/make.conf, /etc/src.conf, or on the
1387 command line. If you wish to use the -C flag for all installs
1388 you may be able to add INSTALL+=-C to /etc/make.conf or
1392 The install(1) option -M has changed meaning and now takes an
1393 argument that is a file or path to append logs to. In the
1394 unlikely event that -M was the last option on the command line
1395 and the command line contained at least two files and a target
1396 directory the first file will have logs appended to it. The -M
1397 option served little practical purpose in the last decade so its
1398 use is expected to be extremely rare.
1401 After switching to Clang as the default compiler some users of ZFS
1402 on i386 systems started to experience stack overflow kernel panics.
1403 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1406 GEOM_LABEL now mangles label names read from file system metadata.
1407 Mangling affect labels containing spaces, non-printable characters,
1408 '%' or '"'. Device names in /etc/fstab and other places may need to
1412 By default, only the 10 most recent kernel dumps will be saved. To
1413 restore the previous behaviour (no limit on the number of kernel dumps
1414 stored in the dump directory) add the following line to /etc/rc.conf:
1419 With the addition of auditdistd(8), a new auditdistd user is now
1420 required during installworld. "mergemaster -p" can be used to
1421 add the user prior to installworld, as documented in the handbook.
1424 The sin6_scope_id member variable in struct sockaddr_in6 is now
1425 filled by the kernel before passing the structure to the userland via
1426 sysctl or routing socket. This means the KAME-specific embedded scope
1427 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1428 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1429 __FreeBSD_version is bumped to 1000025.
1432 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1433 This means that the world and kernel will be compiled with clang
1434 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1435 and /usr/bin/cpp. To disable this behavior and revert to building
1436 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1437 of current may need to bootstrap WITHOUT_CLANG first if the clang
1438 build fails (its compatibility window doesn't extend to the 9 stable
1442 The IPFIREWALL_FORWARD kernel option has been removed. Its
1443 functionality now turned on by default.
1446 The ZERO_COPY_SOCKET kernel option has been removed and
1447 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1448 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1449 mechanism which is not safe and may result in kernel crashes.
1450 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1451 driver supports disposeable external page sized mbuf storage.
1452 Proper replacements for both zero-copy mechanisms are under
1453 consideration and will eventually lead to complete removal
1454 of the two kernel options.
1457 The IPv4 network stack has been converted to network byte
1458 order. The following modules need to be recompiled together
1459 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1460 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1463 Support for non-MPSAFE filesystems was removed from VFS. The
1464 VFS_VERSION was bumped, all filesystem modules shall be
1468 All the non-MPSAFE filesystems have been disconnected from
1469 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1470 portalfs, smbfs, xfs.
1473 The interface cloning API and ABI has changed. The following
1474 modules need to be recompiled together with kernel:
1475 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1476 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1477 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1480 The sdhci driver was split in two parts: sdhci (generic SD Host
1481 Controller logic) and sdhci_pci (actual hardware driver).
1482 No kernel config modifications are required, but if you
1483 load sdhc as a module you must switch to sdhci_pci instead.
1486 Import the FUSE kernel and userland support into base system.
1489 The GNU sort(1) program has been removed since the BSD-licensed
1490 sort(1) has been the default for quite some time and no serious
1491 problems have been reported. The corresponding WITH_GNU_SORT
1495 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1496 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1500 The net80211(4) ABI has been changed to allow for improved driver
1501 PS-POLL and power-save support. All wireless drivers need to be
1502 recompiled to work with the new kernel.
1505 The random(4) support for the VIA hardware random number
1506 generator (`PADLOCK') is no longer enabled unconditionally.
1507 Add the padlock_rng device in the custom kernel config if
1508 needed. The GENERIC kernels on i386 and amd64 do include the
1509 device, so the change only affects the custom kernel
1513 The pf(4) packet filter ABI has been changed. pfctl(8) and
1514 snmp_pf module need to be recompiled to work with new kernel.
1517 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1518 to -HEAD. Pools that have empty_bpobj in active state can not be
1519 imported read-write with ZFS implementations that do not support
1520 this feature. For more information read the zpool-features(5)
1524 The sparc64 ZFS loader has been changed to no longer try to auto-
1525 detect ZFS providers based on diskN aliases but now requires these
1526 to be explicitly listed in the OFW boot-device environment variable.
1529 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1530 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1531 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1534 The following sysctls and tunables have been renamed for consistency
1535 with other variables:
1536 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1537 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1540 The sort utility has been replaced with BSD sort. For now, GNU sort
1541 is also available as "gnusort" or the default can be set back to
1542 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1543 installed as "bsdsort".
1546 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1547 Starting with this version the old system of ZFS pool versioning
1548 is superseded by "feature flags". This concept enables forward
1549 compatibility against certain future changes in functionality of ZFS
1550 pools. The first read-only compatible "feature flag" for ZFS pools
1551 is named "com.delphix:async_destroy". For more information
1552 read the new zpool-features(5) manual page.
1553 Please refer to the "ZFS notes" section of this file for information
1554 on upgrading boot ZFS pools.
1557 The malloc(3) implementation embedded in libc now uses sources imported
1558 as contrib/jemalloc. The most disruptive API change is to
1559 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1560 delete it prior to installworld, and optionally re-create it using the
1561 new format after rebooting. See malloc.conf(5) for details
1562 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1566 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1567 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1568 now spelled mips. This is to aid compatibility with third-party
1569 software that expects this naming scheme in uname(3). Little-endian
1570 settings are unchanged. If you are updating a big-endian mips64 machine
1571 from before this change, you may need to set MACHINE_ARCH=mips64 in
1572 your environment before the new build system will recognize your machine.
1575 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1579 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1580 nullfs(5) did not pass through all behaviours to the underlying layer,
1581 as a result if we bound to a socket on the lower layer we could connect
1582 only to the lower path; if we bound to the upper layer we could connect
1583 only to the upper path. The new behavior is one can connect to both the
1584 lower and the upper paths regardless what layer path one binds to.
1587 The getifaddrs upgrade path broken with 20111215 has been restored.
1588 If you have upgraded in between 20111215 and 20120209 you need to
1589 recompile libc again with your kernel. You still need to recompile
1590 world to be able to configure CARP but this restriction already
1591 comes from 20111215.
1594 The set_rcvar() function has been removed from /etc/rc.subr. All
1595 base and ports rc.d scripts have been updated, so if you have a
1596 port installed with a script in /usr/local/etc/rc.d you can either
1597 hand-edit the rcvar= line, or reinstall the port.
1599 An easy way to handle the mass-update of /etc/rc.d:
1600 rm /etc/rc.d/* && mergemaster -i
1603 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1604 on the current CPU and prevents other threads from running.
1605 This behavior can be reverted using the kern.stop_scheduler_on_panic
1607 The new behavior can be incompatible with kern.sync_on_panic.
1610 The carp(4) facility has been changed significantly. Configuration
1611 of the CARP protocol via ifconfig(8) has changed, as well as format
1612 of CARP events submitted to devd(8) has changed. See manual pages
1613 for more information. The arpbalance feature of carp(4) is currently
1614 not supported anymore.
1616 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1617 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1618 need to be recompiled.
1621 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1625 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1626 explicitely support non-MPSAFE filesystems.
1627 It is on by default for all supported platform at this present
1631 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1632 i386 and pc98 GENERIC kernel configuration files.
1635 sysinstall has been removed
1638 The stable/9 branch created in subversion. This corresponds to the
1639 RELENG_9 branch in CVS.
1645 Avoid using make -j when upgrading. While generally safe, there are
1646 sometimes problems using -j to upgrade. If your upgrade fails with
1647 -j, please try again without -j. From time to time in the past there
1648 have been problems using -j with buildworld and/or installworld. This
1649 is especially true when upgrading between "distant" versions (eg one
1650 that cross a major release boundary or several minor releases, or when
1651 several months have passed on the -current branch).
1653 Sometimes, obscure build problems are the result of environment
1654 poisoning. This can happen because the make utility reads its
1655 environment when searching for values for global variables. To run
1656 your build attempts in an "environmental clean room", prefix all make
1657 commands with 'env -i '. See the env(1) manual page for more details.
1659 When upgrading from one major version to another it is generally best
1660 to upgrade to the latest code in the currently installed branch first,
1661 then do an upgrade to the new branch. This is the best-tested upgrade
1662 path, and has the highest probability of being successful. Please try
1663 this approach before reporting problems with a major version upgrade.
1665 When upgrading a live system, having a root shell around before
1666 installing anything can help undo problems. Not having a root shell
1667 around can lead to problems if pam has changed too much from your
1668 starting point to allow continued authentication after the upgrade.
1670 This file should be read as a log of events. When a later event changes
1671 information of a prior event, the prior event should not be deleted.
1672 Instead, a pointer to the entry with the new information should be
1673 placed in the old entry. Readers of this file should also sanity check
1674 older entries before relying on them blindly. Authors of new entries
1675 should write them with this in mind.
1679 When upgrading the boot ZFS pool to a new version, always follow
1682 1.) recompile and reinstall the ZFS boot loader and boot block
1683 (this is part of "make buildworld" and "make installworld")
1685 2.) update the ZFS boot block on your boot drive
1687 The following example updates the ZFS boot block on the first
1688 partition (freebsd-boot) of a GPT partitioned drive ada0:
1689 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1691 Non-boot pools do not need these updates.
1695 If you are updating from a prior version of FreeBSD (even one just
1696 a few days old), you should follow this procedure. It is the most
1697 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1699 make kernel-toolchain
1700 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1701 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1703 To test a kernel once
1704 ---------------------
1705 If you just want to boot a kernel once (because you are not sure
1706 if it works, or if you want to boot a known bad kernel to provide
1707 debugging information) run
1708 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1709 nextboot -k testkernel
1711 To just build a kernel when you know that it won't mess you up
1712 --------------------------------------------------------------
1713 This assumes you are already running a CURRENT system. Replace
1714 ${arch} with the architecture of your machine (e.g. "i386",
1715 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1717 cd src/sys/${arch}/conf
1718 config KERNEL_NAME_HERE
1719 cd ../compile/KERNEL_NAME_HERE
1724 If this fails, go to the "To build a kernel" section.
1726 To rebuild everything and install it on the current system.
1727 -----------------------------------------------------------
1728 # Note: sometimes if you are running current you gotta do more than
1729 # is listed here if you are upgrading from a really old current.
1731 <make sure you have good level 0 dumps>
1733 make kernel KERNCONF=YOUR_KERNEL_HERE
1735 <reboot in single user> [3]
1742 To cross-install current onto a separate partition
1743 --------------------------------------------------
1744 # In this approach we use a separate partition to hold
1745 # current's root, 'usr', and 'var' directories. A partition
1746 # holding "/", "/usr" and "/var" should be about 2GB in
1749 <make sure you have good level 0 dumps>
1752 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1753 <maybe newfs current's root partition>
1754 <mount current's root partition on directory ${CURRENT_ROOT}>
1755 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1756 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1757 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1758 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1759 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1760 <reboot into current>
1761 <do a "native" rebuild/install as described in the previous section>
1762 <maybe install compatibility libraries from ports/misc/compat*>
1766 To upgrade in-place from stable to current
1767 ----------------------------------------------
1768 <make sure you have good level 0 dumps>
1770 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1772 <reboot in single user> [3]
1779 Make sure that you've read the UPDATING file to understand the
1780 tweaks to various things you need. At this point in the life
1781 cycle of current, things change often and you are on your own
1782 to cope. The defaults can also change, so please read ALL of
1783 the UPDATING entries.
1785 Also, if you are tracking -current, you must be subscribed to
1786 freebsd-current@freebsd.org. Make sure that before you update
1787 your sources that you have read and understood all the recent
1788 messages there. If in doubt, please track -stable which has
1789 much fewer pitfalls.
1791 [1] If you have third party modules, such as vmware, you
1792 should disable them at this point so they don't crash your
1795 [3] From the bootblocks, boot -s, and then do
1800 adjkerntz -i # if CMOS is wall time
1801 Also, when doing a major release upgrade, it is required that
1802 you boot into single user mode to do the installworld.
1804 [4] Note: This step is non-optional. Failure to do this step
1805 can result in a significant reduction in the functionality of the
1806 system. Attempting to do it by hand is not recommended and those
1807 that pursue this avenue should read this file carefully, as well
1808 as the archives of freebsd-current and freebsd-hackers mailing lists
1809 for potential gotchas. The -U option is also useful to consider.
1810 See mergemaster(8) for more information.
1812 [5] Usually this step is a noop. However, from time to time
1813 you may need to do this if you get unknown user in the following
1814 step. It never hurts to do it all the time. You may need to
1815 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1816 install) after the buildworld before this step if you last updated
1817 from current before 20130425 or from -stable before 20130430.
1819 [6] This only deletes old files and directories. Old libraries
1820 can be deleted by "make delete-old-libs", but you have to make
1821 sure that no program is using those libraries anymore.
1823 [8] In order to have a kernel that can run the 4.x binaries needed to
1824 do an installworld, you must include the COMPAT_FREEBSD4 option in
1825 your kernel. Failure to do so may leave you with a system that is
1826 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1827 required to run the 5.x binaries on more recent kernels. And so on
1828 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1830 Make sure that you merge any new devices from GENERIC since the
1831 last time you updated your kernel config file.
1833 [9] When checking out sources, you must include the -P flag to have
1834 cvs prune empty directories.
1836 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1837 "?=" instead of the "=" assignment operator, so that buildworld can
1838 override the CPUTYPE if it needs to.
1840 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1841 not on the command line, or in /etc/make.conf. buildworld will
1842 warn if it is improperly defined.
1845 This file contains a list, in reverse chronological order, of major
1846 breakages in tracking -current. It is not guaranteed to be a complete
1847 list of such breakages, and only contains entries since September 23, 2011.
1848 If you need to see UPDATING entries from before that date, you will need
1849 to fetch an UPDATING file from an older FreeBSD release.
1851 Copyright information:
1853 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1855 Redistribution, publication, translation and use, with or without
1856 modification, in full or in part, in any form or format of this
1857 document are permitted without further permission from the author.
1859 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1860 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1861 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1862 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1863 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1864 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1865 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1866 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1867 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1868 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1869 POSSIBILITY OF SUCH DAMAGE.
1871 Contact Warner Losh if you have any questions about your use of