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 20190724 p12 FreeBSD-EN-19:13.mds
20 FreeBSD-SA-19:12.telnet
22 FreeBSD-SA-19:14.freebsd32
23 FreeBSD-SA-19:15.mqueuefs
24 FreeBSD-SA-19:16.bhyve
27 Fix panic from Intel CPU vulnerability mitigation. [EN-19:13.mds]
29 Fix multiple telnet client vulnerabilities. [SA-19:12.telnet]
31 Fix pts write-after-free. [SA-19:13.pts]
33 Fix kernel memory disclosure in freebsd32_ioctl. [SA-19:14.freebsd32]
35 Fix reference count overflow in mqueuefs. [SA-19:15.mqueuefs]
37 Fix byhve out-of-bounds read in XHCI device. [SA-19:16.bhyve]
39 Fix file descriptor reference count leak. [SA-19:17.fd]
41 20190702 p11 FreeBSD-EN-19:12.tzdata
42 FreeBSD-SA-19:09.iconv
44 FreeBSD-SA-19:11.cd_ioctl
46 Import tzdata 2019b. [EN-19:12.tzdata]
48 Fix iconv buffer overflow. [SA-19:09.iconv]
50 Fix kernel stack disclosure in UFS/FFS. [SA-19:10.ufs]
52 Fix privilege escalation in cd(4) driver. [SA-19:11.cd_ioctl]
54 20190514 p10 FreeBSD-EN-19:08.tzdata
55 FreeBSD-EN-19:09.xinstall
62 Import tzdata 2019a. [EN-19:08.tzdata]
64 Fix install with partially matching relative paths. [EN-19:09.xinstall]
66 Fix multiple vulnerabilities in hostapd/wpa_supplicant. [SA-19:03.wpa]
68 Fix authenticated denial of service in ntpd. [SA-19:04.ntp]
70 Fix IPv6 fragment reassembly in pf. [SA-19:05.pf]
72 Fix ICMP/ICMP6 packet filter bypass in pf. [SA-19:06.pf]
74 Add mitigations for Microarchitectural Data Sampling. [SA-19:07.mds]
77 20190205 p9 FreeBSD-SA-19:01.syscall
79 amd64: clear callee-preserved registers on syscall exit
82 20190109 p8 FreeBSD-EN-19:03.sqlite
83 FreeBSD-EN-19:04.tzdata
84 FreeBSD-EN-19:05.kqueue
86 Update sqlite3-3.20.0 --> sqlite3-3.26.0 (3260000) [EN-19:03.sqlite]
88 Import tzdata 2018h, 2018i [EN-19:04.tzdata]
90 Avoid unsynchronized updates to kn_status. [EN-19:05.kqueue]
93 20181219 p7 FreeBSD-SA-18:15.bootpd
94 FreeBSD-EN-18:16.ptrace
98 bootpd: validate hardware type [SA-18:15.bootpd]
100 Only clear a pending thread event if one is pending. [EN-18:16.ptrace]
102 Update the free page count when blacklisting pages. [EN-18:17.vm]
104 Resolve a hang in ZFS during vnode reclamation [EN-18:18.zfs]
107 20181204 p6 FreeBSD-SA-18:14.bhyve
109 Fix insufficient bounds checking in bhyve(8) device model.
112 20181127 p5 FreeBSD-SA-18:13.nfs
113 FreeBSD-EN-18:13.icmp
114 FreeBSD-EN-18:14.tzdata
115 FreeBSD-EN-18:15.loader
117 Fix multiple vulnerabilities in NFS server code. [SA-18:13.nfs]
119 Fix ICMP buffer underwrite. [EN-18:13.icmp]
121 Timezone database information update. [EN-18:14.tzdata]
123 Fix deferred kernel loading breaks loader password. [EN-18:15.loader]
125 20180927 p4 FreeBSD-EN-18:09.ip
126 FreeBSD-EN-18:10.syscall
127 FreeBSD-EN-18:11.listen
130 Fix regression in IPv6 fragment reassembly. [EN-18:09.ip]
132 Fix NULL pointer dereference in freebsd4_getfsstat. [EN-18:10.syscall]
134 Fix DoS in listen syscall over IPv6 socket. [EN-18:11.listen]
136 Fix small kernel memory disclosures. [EN-18:12.mem]
138 20180912 p3 FreeBSD-SA-18:12.elf
139 FreeBSD-EN-18:08.lazyfpu
141 Fix improper elf header parsing. [SA-18:12.elf]
143 Fix regression in Lazy FPU remediation. [EN-18:08.lazyfpu]
145 20180814 p2 FreeBSD-SA-18:08.tcp [revised]
146 FreeBSD-SA-18:09.l1tf
148 FreeBSD-SA-18:11.hostapd
150 Revise manual pages. [SA-18:08.tcp]
152 Fix L1 Terminal Fault (L1TF) kernel information disclosure.
155 Fix resource exhaustion in IP fragment reassembly. [SA-18:10.ip]
157 Fix unauthenticated EAPOL-Key decryption vulnerability.
160 20180806 p1 FreeBSD-SA-18:08.tcp
162 Fix resource exhaustion in TCP reassembly.
168 The tz database (tzdb) has been updated to 2018e. This version more
169 correctly models time stamps in time zones with negative DST such as
170 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
171 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
172 time zone abbreviations and the tm_isdst flag.
175 The use of RSS hash from the network card aka flowid has been
176 disabled by default for lagg(4) as it's currently incompatible with
177 the lacp and loadbalance protocols.
179 This can be re-enabled by setting the following in loader.conf:
180 net.link.lagg.default_use_flowid="1"
183 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
184 6.0.0. Please see the 20141231 entry below for information about
185 prerequisites and upgrading, if you are not already using clang 3.5.0
189 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
190 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
191 to WITH/OUT_LOADER_GELI.
194 The geli password typed at boot is now hidden. To restore the previous
195 behavior, see geli(8) for configuration options.
197 The SW_WATCHDOG option is no longer necessary to enable the
198 hardclock-based software watchdog if no hardware watchdog is
199 configured. As before, SW_WATCHDOG will cause the software
200 watchdog to be enabled even if a hardware watchdog is configured.
203 lint(1) binaries and library are no longer built by default. To
204 enable building them, define WITH_LINT in src.conf. If you are using
205 a FreeBSD 12 or later system to build 11-stable, you may need to
206 install a lint(1) binary to use WITH_LINT.
209 When building multiple kernels using KERNCONF, non-existent KERNCONF
210 files will produce an error and buildkernel will fail. Previously
211 missing KERNCONF files silently failed giving no indication as to
212 why, only to subsequently discover during installkernel that the
213 desired kernel was never built in the first place.
216 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.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 Since the switch to GPT disk labels, fsck for UFS/FFS has been
222 unable to automatically find alternate superblocks. As of r322806,
223 the information needed to find alternate superblocks has been
224 moved to the end of the area reserved for the boot block.
225 Filesystems created with a newfs of this vintage or later
226 will create the recovery information. If you have a filesystem
227 created prior to this change and wish to have a recovery block
228 created for your filesystem, you can do so by running fsck in
229 forground mode (i.e., do not use the -p or -y options). As it
230 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
231 to which you should answer yes.
234 arm64 builds now use the base system LLD 4.0.0 linker by default,
235 instead of requiring that the aarch64-binutils port or package be
236 installed. To continue using aarch64-binutils, set
237 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
240 The ctl.ko module no longer implements the iSCSI target frontend:
241 cfiscsi.ko does instead.
243 If building cfiscsi.ko as a kernel module, the module can be loaded
244 via one of the following methods:
245 - `cfiscsi_load="YES"` in loader.conf(5).
246 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
247 - ctladm(8)/ctld(8), when compiled with iSCSI support
248 (`WITH_ISCSI=yes` in src.conf(5))
250 Please see cfiscsi(4) for more details.
253 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
254 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
255 same source (previously, the dependency of mmcsd.ko on mmc.ko was
256 missing, but mmcsd.ko now will refuse to load if it is incompatible
260 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
261 use any explicitly assigned loopback address available in the jail
262 instead of using the first assigned address of the jail.
265 As of r316810 for ipfilter, keep frags is no longer assumed when
266 keep state is specified in a rule. r316810 aligns ipfilter with
267 documentation in man pages separating keep frags from keep state.
268 This allows keep state to specified without forcing keep frags
269 and allows keep frags to be specified independently of keep state.
270 To maintain previous behaviour, also specify keep frags with
271 keep state (as documented in ipf.conf.5).
274 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
275 Please see the 20141231 entry below for information about prerequisites
276 and upgrading, if you are not already using clang 3.5.0 or higher.
279 The code that provides support for ZFS .zfs/ directory functionality
280 has been reimplemented. It's not possible now to create a snapshot
281 by mkdir under .zfs/snapshot/. That should be the only user visible
285 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
286 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
287 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
288 and now NAT-T is supported by default. Security associations now use
289 the single namespace for SPI allocation, so if you use several manually
290 configured security associations with the same SPI, this configuration
294 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
295 Please see the 20141231 entry below for information about prerequisites
296 and upgrading, if you are not already using clang 3.5.0 or higher.
299 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
300 Please see the 20141231 entry below for information about prerequisites
301 and upgrading, if you are not already using clang 3.5.0 or higher.
304 The layout of the pmap structure has changed for powerpc to put the pmap
305 statistics at the front for all CPU variations. libkvm(3) and all tools
306 that link against it need to be recompiled.
309 isl(4) and cyapa(4) drivers now require a new driver,
310 chromebook_platform(4), to work properly on Chromebook-class hardware.
311 On other types of hardware the drivers may need to be configured using
312 device hints. Please see the corresponding manual pages for details.
315 Relocatable object files with the extension of .So have been renamed
316 to use an extension of .pico instead. The purpose of this change is
317 to avoid a name clash with shared libraries on case-insensitive file
318 systems. On those file systems, foo.So is the same file as foo.so.
321 The libc stub for the pipe(2) system call has been replaced with
322 a wrapper that calls the pipe2(2) system call and the pipe(2)
323 system call is now only implemented by the kernels that include
324 "options COMPAT_FREEBSD10" in their config file (this is the
325 default). Users should ensure that this option is enabled in
326 their kernel or upgrade userspace to r302092 before upgrading their
330 CAM will now strip leading spaces from SCSI disks' serial numbers.
331 This will effect users who create UFS filesystems on SCSI disks using
332 those disk's diskid device nodes. For example, if /etc/fstab
333 previously contained a line like
334 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
335 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
336 transforms like gmirror may also be affected. ZFS users should
340 The bitstring(3) API has been updated with new functionality and
341 improved performance. But it is binary-incompatible with the old API.
342 Objects built with the new headers may not be linked against objects
343 built with the old headers.
346 The brk and sbrk functions have been removed from libc on arm64.
347 Binutils from ports has been updated to not link to these
348 functions and should be updated to the latest version before
349 installing a new libc.
352 The armv6 port now defaults to hard float ABI. Limited support
353 for running both hardfloat and soft float on the same system
354 is available using the libraries installed with -DWITH_LIBSOFT.
355 This has only been tested as an upgrade path for installworld
356 and packages may fail or need manual intervention to run. New
357 packages will be needed.
359 To update an existing self-hosted armv6hf system, you must add
360 TARGET_ARCH=armv6 on the make command line for both the build
361 and the install steps.
364 Kernel modules compiled outside of a kernel build now default to
365 installing to /boot/modules instead of /boot/kernel. Many kernel
366 modules built this way (such as those in ports) already overrode
367 KMODDIR explicitly to install into /boot/modules. However,
368 manually building and installing a module from /sys/modules will
369 now install to /boot/modules instead of /boot/kernel.
372 The CAM I/O scheduler has been committed to the kernel. There should be
373 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
374 list of known rogues that claim support for this but actually corrupt
375 data is believed to be complete, be on the lookout for data
376 corruption. The known rogue list is believed to be complete:
378 o Crucial MX100, M550 drives with MU01 firmware.
379 o Micron M510 and M550 drives with MU01 firmware.
380 o Micron M500 prior to MU07 firmware
381 o Samsung 830, 840, and 850 all firmwares
382 o FCCT M500 all firmwares
384 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
385 with working NCQ TRIM. For Micron branded drives, see your sales rep for
386 updated firmware. Black listed drives will work correctly because these
387 drives work correctly so long as no NCQ TRIMs are sent to them. Given
388 this list is the same as found in Linux, it's believed there are no
389 other rogues in the market place. All other models from the above
392 To be safe, if you are at all concerned, you can quirk each of your
393 drives to prevent NCQ from being sent by setting:
394 kern.cam.ada.X.quirks="0x2"
395 in loader.conf. If the drive requires the 4k sector quirk, set the
399 The FAST_DEPEND build option has been removed and its functionality is
400 now the one true way. The old mkdep(1) style of 'make depend' has
401 been removed. See 20160311 for further details.
404 Resource range types have grown from unsigned long to uintmax_t. All
405 drivers, and anything using libdevinfo, need to be recompiled.
408 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
409 builds. It no longer runs mkdep(1) during 'make depend', and the
410 'make depend' stage can safely be skipped now as it is auto ran
411 when building 'make all' and will generate all SRCS and DPSRCS before
412 building anything else. Dependencies are gathered at compile time with
413 -MF flags kept in separate .depend files per object file. Users should
414 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
418 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
419 kernel modules. Therefore, if you load any kernel modules at boot time,
420 please install the boot loaders after you install the kernel, but before
424 make kernel KERNCONF=YOUR_KERNEL_HERE
425 make -C sys/boot install
426 <reboot in single user>
428 Then follow the usual steps, described in the General Notes section,
432 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
433 see the 20141231 entry below for information about prerequisites and
434 upgrading, if you are not already using clang 3.5.0 or higher.
437 The AIO subsystem is now a standard part of the kernel. The
438 VFS_AIO kernel option and aio.ko kernel module have been removed.
439 Due to stability concerns, asynchronous I/O requests are only
440 permitted on sockets and raw disks by default. To enable
441 asynchronous I/O requests on all file types, set the
442 vfs.aio.enable_unsafe sysctl to a non-zero value.
445 The ELF object manipulation tool objcopy is now provided by the
446 ELF Tool Chain project rather than by GNU binutils. It should be a
447 drop-in replacement, with the addition of arm64 support. The
448 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
449 to obtain the GNU version if necessary.
452 Building ZFS pools on top of zvols is prohibited by default. That
453 feature has never worked safely; it's always been prone to deadlocks.
454 Using a zvol as the backing store for a VM guest's virtual disk will
455 still work, even if the guest is using ZFS. Legacy behavior can be
456 restored by setting vfs.zfs.vol.recursive=1.
459 The NONE and HPN patches has been removed from OpenSSH. They are
460 still available in the security/openssh-portable port.
463 With the addition of ypldap(8), a new _ypldap user is now required
464 during installworld. "mergemaster -p" can be used to add the user
465 prior to installworld, as documented in the handbook.
468 The tftp loader (pxeboot) now uses the option root-path directive. As a
469 consequence it no longer looks for a pxeboot.4th file on the tftp
470 server. Instead it uses the regular /boot infrastructure as with the
474 The code to start recording plug and play data into the modules has
475 been committed. While the old tools will properly build a new kernel,
476 a number of warnings about "unknown metadata record 4" will be produced
477 for an older kldxref. To avoid such warnings, make sure to rebuild
478 the kernel toolchain (or world). Make sure that you have r292078 or
479 later when trying to build 292077 or later before rebuilding.
482 Debug data files are now built by default with 'make buildworld' and
483 installed with 'make installworld'. This facilitates debugging but
484 requires more disk space both during the build and for the installed
485 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
489 r291527 changed the internal interface between the nfsd.ko and
490 nfscommon.ko modules. As such, they must both be upgraded to-gether.
491 __FreeBSD_version has been bumped because of this.
494 Add support for unicode collation strings leads to a change of
495 order of files listed by ls(1) for example. To get back to the old
496 behaviour, set LC_COLLATE environment variable to "C".
498 Databases administrators will need to reindex their databases given
499 collation results will be different.
501 Due to a bug in install(1) it is recommended to remove the ancient
502 locales before running make installworld.
504 rm -rf /usr/share/locale/*
507 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
508 libcrypto.so.7 or libssl.so.7 must be recompiled.
511 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
512 Kernel modules isp_2400_multi and isp_2500_multi were removed and
513 should be replaced with isp_2400 and isp_2500 modules respectively.
516 The build previously allowed using 'make -n' to not recurse into
517 sub-directories while showing what commands would be executed, and
518 'make -n -n' to recursively show commands. Now 'make -n' will recurse
519 and 'make -N' will not.
522 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
523 and etcupdate will now use this file. A custom sendmail.cf is now
524 updated via this mechanism rather than via installworld. If you had
525 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
526 want to remove the exclusion or change it to "always install".
527 /etc/mail/sendmail.cf is now managed the same way regardless of
528 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
529 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
532 Compatibility shims for legacy ATA device names have been removed.
533 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
534 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
535 environment variables, /dev/ad* and /dev/ar* symbolic links.
538 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
539 Please see the 20141231 entry below for information about prerequisites
540 and upgrading, if you are not already using clang 3.5.0 or higher.
543 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
544 and renamed from .symbols to .debug. This reduces the size requirements
545 on the boot partition or file system and provides consistency with
546 userland debug files.
548 When using the supported kernel installation method the
549 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
550 as is done with /boot/kernel.
552 Developers wishing to maintain the historical behavior of installing
553 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
556 The wireless drivers had undergone changes that remove the 'parent
557 interface' from the ifconfig -l output. The rc.d network scripts
558 used to check presence of a parent interface in the list, so old
559 scripts would fail to start wireless networking. Thus, etcupdate(3)
560 or mergemaster(8) run is required after kernel update, to update your
561 rc.d scripts in /etc.
564 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
565 These configurations are now automatically interpreted as
566 'scrub fragment reassemble'.
569 Kernel-loadable modules for the random(4) device are back. To use
570 them, the kernel must have
573 options RANDOM_LOADABLE
575 kldload(8) can then be used to load random_fortuna.ko
576 or random_yarrow.ko. Please note that due to the indirect
577 function calls that the loadable modules need to provide,
578 the build-in variants will be slightly more efficient.
580 The random(4) kernel option RANDOM_DUMMY has been retired due to
581 unpopularity. It was not all that useful anyway.
584 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
585 Control over building the ELF Tool Chain tools is now provided by
586 the WITHOUT_TOOLCHAIN knob.
589 The polarity of Pulse Per Second (PPS) capture events with the
590 uart(4) driver has been corrected. Prior to this change the PPS
591 "assert" event corresponded to the trailing edge of a positive PPS
592 pulse and the "clear" event was the leading edge of the next pulse.
594 As the width of a PPS pulse in a typical GPS receiver is on the
595 order of 1 millisecond, most users will not notice any significant
596 difference with this change.
598 Anyone who has compensated for the historical polarity reversal by
599 configuring a negative offset equal to the pulse width will need to
600 remove that workaround.
603 The default group assigned to /dev/dri entries has been changed
604 from 'wheel' to 'video' with the id of '44'. If you want to have
605 access to the dri devices please add yourself to the video group
608 # pw groupmod video -m $USER
611 The menu.rc and loader.rc files will now be replaced during
612 upgrades. Please migrate local changes to menu.rc.local and
613 loader.rc.local instead.
616 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
617 strings and strip have been removed. The src.conf(5) knob
618 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
621 As ZFS requires more kernel stack pages than is the default on some
622 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
623 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
625 Please consider using 'options KSTACK_PAGES=X' where X is greater
626 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
629 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
630 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
631 default, i.e., they will not contain "::". For example, instead
632 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
633 to have a more specific match, such as different map entries for
634 IPv6:0:0 vs IPv6:0. This change requires that configuration
635 data (including maps, files, classes, custom ruleset, etc.) must
636 use the same format, so make certain such configuration data is
637 upgrading. As a very simple check search for patterns like
638 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
639 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
640 the cf option UseCompressedIPv6Addresses.
643 The default kernel entropy-processing algorithm is now
644 Fortuna, replacing Yarrow.
646 Assuming you have 'device random' in your kernel config
647 file, the configurations allow a kernel option to override
648 this default. You may choose *ONE* of:
650 options RANDOM_YARROW # Legacy /dev/random algorithm.
651 options RANDOM_DUMMY # Blocking-only driver.
653 If you have neither, you get Fortuna. For most people,
654 read no further, Fortuna will give a /dev/random that works
655 like it always used to, and the difference will be irrelevant.
657 If you remove 'device random', you get *NO* kernel-processed
658 entropy at all. This may be acceptable to folks building
659 embedded systems, but has complications. Carry on reading,
660 and it is assumed you know what you need.
662 *PLEASE* read random(4) and random(9) if you are in the
663 habit of tweaking kernel configs, and/or if you are a member
664 of the embedded community, wanting specific and not-usual
665 behaviour from your security subsystems.
667 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
668 random', you will NOT have a functioning /dev/random, and
669 many cryptographic features will not work, including SSH.
670 You may also find strange behaviour from the random(3) set
671 of library functions, in particular sranddev(3), srandomdev(3)
672 and arc4random(3). The reason for this is that the KERN_ARND
673 sysctl only returns entropy if it thinks it has some to
674 share, and with RANDOM_DUMMY or no 'device random' this
678 An additional fix for the issue described in the 20150614 sendmail
679 entry below has been been committed in revision 284717.
682 FreeBSD's old make (fmake) has been removed from the system. It is
683 available as the devel/fmake port or via pkg install fmake.
686 The fix for the issue described in the 20150614 sendmail entry
687 below has been been committed in revision 284436. The work
688 around described in that entry is no longer needed unless the
689 default setting is overridden by a confDH_PARAMETERS configuration
690 setting of '5' or pointing to a 512 bit DH parameter file.
693 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
694 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
695 and devel/kyua to version 0.20+ and adjust any calling code to work
696 with Kyuafile and kyua.
699 The import of openssl to address the FreeBSD-SA-15:10.openssl
700 security advisory includes a change which rejects handshakes
701 with DH parameters below 768 bits. sendmail releases prior
702 to 8.15.2 (not yet released), defaulted to a 512 bit
703 DH parameter setting for client connections. To work around
704 this interoperability, sendmail can be configured to use a
705 2048 bit DH parameter by:
707 1. Edit /etc/mail/`hostname`.mc
708 2. If a setting for confDH_PARAMETERS does not exist or
709 exists and is set to a string beginning with '5',
711 3. If a setting for confDH_PARAMETERS exists and is set to
712 a file path, create a new file with:
713 openssl dhparam -out /path/to/file 2048
714 4. Rebuild the .cf file:
715 cd /etc/mail/; make; make install
717 cd /etc/mail/; make restart
719 A sendmail patch is coming, at which time this file will be
723 Generation of legacy formatted entries have been disabled by default
724 in pwd_mkdb(8), as all base system consumers of the legacy formatted
725 entries were converted to use the new format by default when the new,
726 machine independent format have been added and supported since FreeBSD
729 Please see the pwd_mkdb(8) manual page for further details.
732 Clang and llvm have been upgraded to 3.6.1 release. Please see the
733 20141231 entry below for information about prerequisites and upgrading,
734 if you are not already using 3.5.0 or higher.
737 TI platform code switched to using vendor DTS files and this update
738 may break existing systems running on Beaglebone, Beaglebone Black,
741 - dtb files should be regenerated/reinstalled. Filenames are the
742 same but content is different now
743 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
744 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
745 addressing scheme is now pin 25 on /dev/gpioc3.
746 - Pandaboard: /etc/ttys should be updated, serial console device is
747 now /dev/ttyu2, not /dev/ttyu0
750 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
751 If you need the GNU extension from groff soelim(1), install groff
752 from package: pkg install groff, or via ports: textproc/groff.
755 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
756 defined in symlink(7); previously symlinks were silently ignored.
759 The const qualifier has been removed from iconv(3) to comply with
760 POSIX. The ports tree is aware of this from r384038 onwards.
763 Libraries specified by LIBADD in Makefiles must have a corresponding
764 DPADD_<lib> variable to ensure correct dependencies. This is now
765 enforced in src.libnames.mk.
768 From legacy ata(4) driver was removed support for SATA controllers
769 supported by more functional drivers ahci(4), siis(4) and mvs(4).
770 Kernel modules ataahci and ataadaptec were removed completely,
771 replaced by ahci and mvs modules respectively.
774 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
775 the 20141231 entry below for information about prerequisites and
776 upgrading, if you are not already using 3.5.0 or higher.
779 The 32-bit PowerPC kernel has been changed to a position-independent
780 executable. This can only be booted with a version of loader(8)
781 newer than January 31, 2015, so make sure to update both world and
782 kernel before rebooting.
785 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
786 but before r278950, the RNG was not seeded properly. Immediately
787 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
788 ssh keys or openssl keys) that were generated w/ a kernel from that
789 range. This does not affect programs that directly used /dev/random
790 or /dev/urandom. All userland uses of arc4random(3) are affected.
793 The autofs(4) ABI was changed in order to restore binary compatibility
794 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
798 The powerpc64 kernel has been changed to a position-independent
799 executable. This can only be booted with a new version of loader(8),
800 so make sure to update both world and kernel before rebooting.
803 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
804 only release, no new features have been added. Please see the 20141231
805 entry below for information about prerequisites and upgrading, if you
806 are not already using 3.5.0.
809 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
810 taken from the ELF Tool Chain project rather than GNU binutils. They
811 should be drop-in replacements, with the addition of arm64 support.
812 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
813 binutils tools, if necessary. See 20150805 for updated information.
816 The default Unbound configuration now enables remote control
817 using a local socket. Users who have already enabled the
818 local_unbound service should regenerate their configuration
819 by running "service local_unbound setup" as root.
822 The GNU texinfo and GNU info pages have been removed.
823 To be able to view GNU info pages please install texinfo from ports.
826 Clang, llvm and lldb have been upgraded to 3.5.0 release.
828 As of this release, a prerequisite for building clang, llvm and lldb is
829 a C++11 capable compiler and C++11 standard library. This means that to
830 be able to successfully build the cross-tools stage of buildworld, with
831 clang as the bootstrap compiler, your system compiler or cross compiler
832 should either be clang 3.3 or later, or gcc 4.8 or later, and your
833 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
836 On any standard FreeBSD 10.x or 11.x installation, where clang and
837 libc++ are on by default (that is, on x86 or arm), this should work out
840 On 9.x installations where clang is enabled by default, e.g. on x86 and
841 powerpc, libc++ will not be enabled by default, so libc++ should be
842 built (with clang) and installed first. If both clang and libc++ are
843 missing, build clang first, then use it to build libc++.
845 On 8.x and earlier installations, upgrade to 9.x first, and then follow
846 the instructions for 9.x above.
848 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
849 default, and do not build clang.
851 Many embedded systems are resource constrained, and will not be able to
852 build clang in a reasonable time, or in some cases at all. In those
853 cases, cross building bootable systems on amd64 is a workaround.
855 This new version of clang introduces a number of new warnings, of which
856 the following are most likely to appear:
860 This warns in two cases, for both C and C++:
861 * When the code is trying to take the absolute value of an unsigned
862 quantity, which is effectively a no-op, and almost never what was
863 intended. The code should be fixed, if at all possible. If you are
864 sure that the unsigned quantity can be safely cast to signed, without
865 loss of information or undefined behavior, you can add an explicit
866 cast, or disable the warning.
868 * When the code is trying to take an absolute value, but the called
869 abs() variant is for the wrong type, which can lead to truncation.
870 If you want to disable the warning instead of fixing the code, please
871 make sure that truncation will not occur, or it might lead to unwanted
874 -Wtautological-undefined-compare and
875 -Wundefined-bool-conversion
877 These warn when C++ code is trying to compare 'this' against NULL, while
878 'this' should never be NULL in well-defined C++ code. However, there is
879 some legacy (pre C++11) code out there, which actively abuses this
880 feature, which was less strictly defined in previous C++ versions.
882 Squid and openjdk do this, for example. The warning can be turned off
883 for C++98 and earlier, but compiling the code in C++11 mode might result
884 in unexpected behavior; for example, the parts of the program that are
885 unreachable could be optimized away.
888 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
889 kernel sources have been removed. The .h files remain, since some
890 utilities include them. This will need to be fixed later.
891 If "mount -t oldnfs ..." is attempted, it will fail.
892 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
893 the utilities will report errors.
896 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
897 directories to top level SUBDIR variable when their parent
898 directory is included in LOCAL_DIRS. Users with build systems with
899 such hierarchies and without SUBDIR entries in the parent
900 directory Makefiles should add them or add the directories to
904 faith(4) and faithd(8) have been removed from the base system. Faith
905 has been obsolete for a very long time.
908 vt(4), the new console driver, is enabled by default. It brings
909 support for Unicode and double-width characters, as well as
910 support for UEFI and integration with the KMS kernel video
913 You may need to update your console settings in /etc/rc.conf,
914 most probably the keymap. During boot, /etc/rc.d/syscons will
915 indicate what you need to do.
917 vt(4) still has issues and lacks some features compared to
918 syscons(4). See the wiki for up-to-date information:
919 https://wiki.freebsd.org/Newcons
921 If you want to keep using syscons(4), you can do so by adding
922 the following line to /boot/loader.conf:
926 pjdfstest has been integrated into kyua as an opt-in test suite.
927 Please see share/doc/pjdfstest/README for more details on how to
931 gperf has been removed from the base system for architectures
932 that use clang. Ports that require gperf will obtain it from the
936 pjdfstest has been moved from tools/regression/pjdfstest to
940 At svn r271982, The default linux compat kernel ABI has been adjusted
941 to 2.6.18 in support of the linux-c6 compat ports infrastructure
942 update. If you wish to continue using the linux-f10 compat ports,
943 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
944 encouraged to update their linux-compat packages to linux-c6 during
945 their next update cycle.
948 The ofwfb driver, used to provide a graphics console on PowerPC when
949 using vt(4), no longer allows mmap() of all physical memory. This
950 will prevent Xorg on PowerPC with some ATI graphics cards from
951 initializing properly unless x11-servers/xorg-server is updated to
955 The xdev targets have been converted to using TARGET and
956 TARGET_ARCH instead of XDEV and XDEV_ARCH.
959 The default unbound configuration has been modified to address
960 issues with reverse lookups on networks that use private
961 address ranges. If you use the local_unbound service, run
962 "service local_unbound setup" as root to regenerate your
963 configuration, then "service local_unbound reload" to load the
967 The GNU texinfo and GNU info pages are not built and installed
968 anymore, WITH_INFO knob has been added to allow to built and install
970 UPDATE: see 20150102 entry on texinfo's removal
973 The GNU readline library is now an INTERNALLIB - that is, it is
974 statically linked into consumers (GDB and variants) in the base
975 system, and the shared library is no longer installed. The
976 devel/readline port is available for third party software that
980 The Itanium architecture (ia64) has been removed from the list of
981 known architectures. This is the first step in the removal of the
985 Commit r268115 has added NFSv4.1 server support, merged from
986 projects/nfsv4.1-server. Since this includes changes to the
987 internal interfaces between the NFS related modules, a full
988 build of the kernel and modules will be necessary.
989 __FreeBSD_version has been bumped.
992 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
993 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
994 which differs from the behaviour controlled by this knob.)
997 Maximal length of the serial number in CTL was increased from 16 to
998 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
999 and ctld, need to be rebuilt to work with a new kernel.
1002 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1003 1 respectively to match the upstream numbers. They were out of
1004 sync because, when they were originally added to FreeBSD, the
1005 upstream versions were not respected. These libraries are private
1006 and not yet built by default, so renumbering them should be a
1007 non-issue. However, unclean source trees will yield broken test
1008 programs once the operator executes "make delete-old-libs" after a
1009 "make installworld".
1011 Additionally, the atf-sh binary was made private by moving it into
1012 /usr/libexec/. Already-built shell test programs will keep the
1013 path to the old binary so they will break after "make delete-old"
1016 If you are using WITH_TESTS=yes (not the default), wipe the object
1017 tree and rebuild from scratch to prevent spurious test failures.
1018 This is only needed once: the misnumbered libraries and misplaced
1019 binaries have been added to OptionalObsoleteFiles.inc so they will
1020 be removed during a clean upgrade.
1023 Clang and llvm have been upgraded to 3.4.1 release.
1026 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1027 be removed to avoid issues in the future (and has been added to
1031 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1032 past, it affected all builds that used the bsd.*.mk files. The old
1033 behavior was a bug, but people may have relied upon it. To get this
1034 behavior back, you can .include /etc/src.conf from /etc/make.conf
1035 (which is still global and isn't changed). This also changes the
1036 behavior of incremental builds inside the tree of individual
1037 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1038 Although this has survived make universe and some upgrade scenarios,
1039 other upgrade scenarios may have broken. At least one form of
1040 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1041 as well... In cases where MAKESYSPATH isn't working with this
1042 setting, you'll need to set it to the full path to your tree.
1044 One side effect of all this cleaning up is that bsd.compiler.mk
1045 is no longer implicitly included by bsd.own.mk. If you wish to
1046 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1050 The lindev device has been removed since /dev/full has been made a
1051 standard device. __FreeBSD_version has been bumped.
1054 The knob WITHOUT_VI was added to the base system, which controls
1055 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1056 in order to reorder files share/termcap and didn't build ex(1) as a
1057 build tool, so building/installing with WITH_VI is highly advised for
1058 build hosts for older releases.
1060 This issue has been fixed in stable/9 and stable/10 in r277022 and
1061 r276991, respectively.
1064 The YES_HESIOD knob has been removed. It has been obsolete for
1065 a decade. Please move to using WITH_HESIOD instead or your builds
1066 will silently lack HESIOD.
1069 The uart(4) driver has been changed with respect to its handling
1070 of the low-level console. Previously the uart(4) driver prevented
1071 any process from changing the baudrate or the CLOCAL and HUPCL
1072 control flags. By removing the restrictions, operators can make
1073 changes to the serial console port without having to reboot.
1074 However, when getty(8) is started on the serial device that is
1075 associated with the low-level console, a misconfigured terminal
1076 line in /etc/ttys will now have a real impact.
1077 Before upgrading the kernel, make sure that /etc/ttys has the
1078 serial console device configured as 3wire without baudrate to
1079 preserve the previous behaviour. E.g:
1080 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1083 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1084 to improve performance. To re-enable it, if needed, run rpcbind
1085 with command line option -W.
1088 Switched back to the GPL dtc compiler due to updates in the upstream
1089 dts files not being supported by the BSDL dtc compiler. You will need
1090 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1091 may result while building dtb files during a kernel build if you fail
1092 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1095 Clang and llvm have been upgraded to 3.4 release.
1098 The nve(4) driver has been removed. Please use the nfe(4) driver
1099 for NVIDIA nForce MCP Ethernet adapters instead.
1102 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1103 This could cause certain C++ applications using shared libraries built
1104 against the previous version of libc++ to crash. The incompatibility
1105 has now been fixed, but any C++ applications or shared libraries built
1106 between r261283 and r261801 should be recompiled.
1109 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1110 capability mode support. Please note that enabling the feature in
1111 kernel is still highly recommended.
1114 OpenSSH is now built with sandbox support, and will use sandbox as
1115 the default privilege separation method. This requires Capsicum
1116 capability mode support in kernel.
1119 The libelf and libdwarf libraries have been updated to newer
1120 versions from upstream. Shared library version numbers for
1121 these two libraries were bumped. Any ports or binaries
1122 requiring these two libraries should be recompiled.
1123 __FreeBSD_version is bumped to 1100006.
1126 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1127 instead of providing an explicit one, this would prevent such
1128 Makefile from providing its own Kyuafile in the future during
1129 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1130 intervention is needed to clean an objdir if you use NO_CLEAN:
1131 # find /usr/obj -name Kyuafile | xargs rm -f
1134 The behavior of gss_pseudo_random() for the krb5 mechanism
1135 has changed, for applications requesting a longer random string
1136 than produced by the underlying enctype's pseudo-random() function.
1137 In particular, the random string produced from a session key of
1138 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1139 be different at the 17th octet and later, after this change.
1140 The counter used in the PRF+ construction is now encoded as a
1141 big-endian integer in accordance with RFC 4402.
1142 __FreeBSD_version is bumped to 1100004.
1145 The WITHOUT_ATF build knob has been removed and its functionality
1146 has been subsumed into the more generic WITHOUT_TESTS. If you were
1147 using the former to disable the build of the ATF libraries, you
1148 should change your settings to use the latter.
1151 The default version of mtree is nmtree which is obtained from
1152 NetBSD. The output is generally the same, but may vary
1153 slightly. If you found you need identical output adding
1154 "-F freebsd9" to the command line should do the trick. For the
1155 time being, the old mtree is available as fmtree.
1158 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1159 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1160 1.1.4_8 and verify bsdyml not linked in, before running "make
1162 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1164 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1167 The stable/10 branch has been created in subversion from head
1171 The rc.d/jail script has been updated to support jail(8)
1172 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1173 for per-jail configuration are automatically converted to
1174 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1175 This is transparently backward compatible. See below about some
1176 incompatibilities and rc.conf(5) manual page for more details.
1178 These variables are now deprecated in favor of jail(8) configuration
1179 file. One can use "rc.d/jail config <jname>" command to generate
1180 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1181 running the jail(8) utility. The default pathname of the
1182 configuration file is /etc/jail.conf and can be specified by
1183 using $jail_conf or $jail_<jname>_conf variables.
1185 Please note that jail_devfs_ruleset accepts an integer at
1186 this moment. Please consider to rewrite the ruleset name
1190 BIND has been removed from the base system. If all you need
1191 is a local resolver, simply enable and start the local_unbound
1192 service instead. Otherwise, several versions of BIND are
1193 available in the ports tree. The dns/bind99 port is one example.
1195 With this change, nslookup(1) and dig(1) are no longer in the base
1196 system. Users should instead use host(1) and drill(1) which are
1197 in the base system. Alternatively, nslookup and dig can
1198 be obtained by installing the dns/bind-tools port.
1201 With the addition of unbound(8), a new unbound user is now
1202 required during installworld. "mergemaster -p" can be used to
1203 add the user prior to installworld, as documented in the handbook.
1206 OpenSSH is now built with DNSSEC support, and will by default
1207 silently trust signed SSHFP records. This can be controlled with
1208 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1209 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1212 The GNU Compiler Collection and C++ standard library (libstdc++)
1213 are no longer built by default on platforms where clang is the system
1214 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1215 options in src.conf.
1218 The PROCDESC kernel option is now part of the GENERIC kernel
1219 configuration and is required for the rwhod(8) to work.
1220 If you are using custom kernel configuration, you should include
1224 The API and ABI related to the Capsicum framework was modified
1225 in backward incompatible way. The userland libraries and programs
1226 have to be recompiled to work with the new kernel. This includes the
1227 following libraries and programs, but the whole buildworld is
1228 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1229 kdump, procstat, rwho, rwhod, uniq.
1232 AES-NI intrinsic support has been added to gcc. The AES-NI module
1233 has been updated to use this support. A new gcc is required to build
1234 the aesni module on both i386 and amd64.
1237 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1238 Thus "device padlock_rng" and "device rdrand_rng" should be
1239 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1242 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1243 enables just the iconv* functionality and is now on by default.
1244 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1245 compatibility. Set WITHOUT_ICONV to build the old way.
1246 If you have been using WITH_ICONV before, you will very likely
1247 need to turn on WITH_LIBICONV_COMPAT.
1250 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1251 Illumos origin, including ZFS. If you have INVARIANTS in your
1252 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1254 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1255 locks if WITNESS option was set. Because that generated a lot of
1256 witness(9) reports and all of them were believed to be false
1257 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1258 can be used to achieve the previous behavior.
1261 Timer values in IPv6 data structures now use time_uptime instead
1262 of time_second. Although this is not a user-visible functional
1263 change, userland utilities which directly use them---ndp(8),
1264 rtadvd(8), and rtsold(8) in the base system---need to be updated
1265 to r253970 or later.
1268 find -delete can now delete the pathnames given as arguments,
1269 instead of only files found below them or if the pathname did
1270 not contain any slashes. Formerly, the following error message
1273 find: -delete: <path>: relative path potentially not safe
1275 Deleting the pathnames given as arguments can be prevented
1276 without error messages using -mindepth 1 or by changing
1277 directory and passing "." as argument to find. This works in the
1278 old as well as the new version of find.
1281 Behavior of devfs rules path matching has been changed.
1282 Pattern is now always matched against fully qualified devfs
1283 path and slash characters must be explicitly matched by
1284 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1285 subdirectories must be reviewed.
1288 The default ARM ABI has changed to the ARM EABI. The old ABI is
1289 incompatible with the ARM EABI and all programs and modules will
1290 need to be rebuilt to work with a new kernel.
1292 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1294 NOTE: Support for the old ABI will be removed in the future and
1295 users are advised to upgrade.
1298 pkg_install has been disconnected from the build if you really need it
1299 you should add WITH_PKGTOOLS in your src.conf(5).
1302 Most of network statistics structures were changed to be able
1303 keep 64-bits counters. Thus all tools, that work with networking
1304 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1307 Fix a bug that allowed a tracing process (e.g. gdb) to write
1308 to a memory-mapped file in the traced process's address space
1309 even if neither the traced process nor the tracing process had
1310 write access to that file.
1313 CVS has been removed from the base system. An exact copy
1314 of the code is available from the devel/cvs port.
1317 Some people report the following error after the switch to bmake:
1319 make: illegal option -- J
1320 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1322 *** [buildworld] Error code 2
1324 this likely due to an old instance of make in
1325 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1326 which src/Makefile will use that blindly, if it exists, so if
1327 you see the above error:
1329 rm -rf `make -V MAKEPATH`
1334 Use bmake by default.
1335 Whereas before one could choose to build with bmake via
1336 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1337 make. The goal is to remove these knobs for 10-RELEASE.
1339 It is worth noting that bmake (like gmake) treats the command
1340 line as the unit of failure, rather than statements within the
1341 command line. Thus '(cd some/where && dosomething)' is safer
1342 than 'cd some/where; dosomething'. The '()' allows consistent
1343 behavior in parallel build.
1346 Fix a bug that allows NFS clients to issue READDIR on files.
1349 The WITHOUT_IDEA option has been removed because
1350 the IDEA patent expired.
1353 The sysctl which controls TRIM support under ZFS has been renamed
1354 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1358 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1359 rather than creating it's own in the temporary directory in
1360 order allow access to bootstrapped versions of tools such as
1361 install and mtree. When upgrading from version of FreeBSD where
1362 the install command does not support -l, you will need to
1363 install a new mergemaster command if mergemaster -p is required.
1364 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1368 Legacy ATA stack, disabled and replaced by new CAM-based one since
1369 FreeBSD 9.0, completely removed from the sources. Kernel modules
1370 atadisk and atapi*, user-level tools atacontrol and burncd are
1371 removed. Kernel option `options ATA_CAM` is now permanently enabled
1375 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1376 and socketpair(2). Software, in particular Kerberos, may
1377 automatically detect and use these during building. The resulting
1378 binaries will not work on older kernels.
1381 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1382 information, see the respective 20130304 entry).
1385 Recent commits to callout(9) changed the size of struct callout,
1386 so the KBI is probably heavily disturbed. Also, some functions
1387 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1388 by macros. Every kernel module using it won't load, so rebuild
1391 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1392 but does not initialize by default (because of the new CTL_DISABLE
1393 option) to save memory. To re-enable it, remove the CTL_DISABLE
1394 option from the kernel config file or set kern.cam.ctl.disable=0
1395 in /boot/loader.conf.
1398 The ctl device has been disabled in GENERIC for i386 and amd64.
1399 This was done due to the extra memory being allocated at system
1400 initialisation time by the ctl driver which was only used if
1401 a CAM target device was created. This makes a FreeBSD system
1402 unusable on 128MB or less of RAM.
1405 A new compression method (lz4) has been merged to -HEAD. Please
1406 refer to zpool-features(7) for more information.
1408 Please refer to the "ZFS notes" section of this file for information
1409 on upgrading boot ZFS pools.
1412 A BSD-licensed patch(1) variant has been added and is installed
1413 as bsdpatch, being the GNU version the default patch.
1414 To inverse the logic and use the BSD-licensed one as default,
1415 while having the GNU version installed as gnupatch, rebuild
1416 and install world with the WITH_BSD_PATCH knob set.
1419 Due to the use of the new -l option to install(1) during build
1420 and install, you must take care not to directly set the INSTALL
1421 make variable in your /etc/make.conf, /etc/src.conf, or on the
1422 command line. If you wish to use the -C flag for all installs
1423 you may be able to add INSTALL+=-C to /etc/make.conf or
1427 The install(1) option -M has changed meaning and now takes an
1428 argument that is a file or path to append logs to. In the
1429 unlikely event that -M was the last option on the command line
1430 and the command line contained at least two files and a target
1431 directory the first file will have logs appended to it. The -M
1432 option served little practical purpose in the last decade so its
1433 use is expected to be extremely rare.
1436 After switching to Clang as the default compiler some users of ZFS
1437 on i386 systems started to experience stack overflow kernel panics.
1438 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1441 GEOM_LABEL now mangles label names read from file system metadata.
1442 Mangling affect labels containing spaces, non-printable characters,
1443 '%' or '"'. Device names in /etc/fstab and other places may need to
1447 By default, only the 10 most recent kernel dumps will be saved. To
1448 restore the previous behaviour (no limit on the number of kernel dumps
1449 stored in the dump directory) add the following line to /etc/rc.conf:
1454 With the addition of auditdistd(8), a new auditdistd user is now
1455 required during installworld. "mergemaster -p" can be used to
1456 add the user prior to installworld, as documented in the handbook.
1459 The sin6_scope_id member variable in struct sockaddr_in6 is now
1460 filled by the kernel before passing the structure to the userland via
1461 sysctl or routing socket. This means the KAME-specific embedded scope
1462 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1463 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1464 __FreeBSD_version is bumped to 1000025.
1467 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1468 This means that the world and kernel will be compiled with clang
1469 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1470 and /usr/bin/cpp. To disable this behavior and revert to building
1471 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1472 of current may need to bootstrap WITHOUT_CLANG first if the clang
1473 build fails (its compatibility window doesn't extend to the 9 stable
1477 The IPFIREWALL_FORWARD kernel option has been removed. Its
1478 functionality now turned on by default.
1481 The ZERO_COPY_SOCKET kernel option has been removed and
1482 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1483 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1484 mechanism which is not safe and may result in kernel crashes.
1485 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1486 driver supports disposeable external page sized mbuf storage.
1487 Proper replacements for both zero-copy mechanisms are under
1488 consideration and will eventually lead to complete removal
1489 of the two kernel options.
1492 The IPv4 network stack has been converted to network byte
1493 order. The following modules need to be recompiled together
1494 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1495 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1498 Support for non-MPSAFE filesystems was removed from VFS. The
1499 VFS_VERSION was bumped, all filesystem modules shall be
1503 All the non-MPSAFE filesystems have been disconnected from
1504 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1505 portalfs, smbfs, xfs.
1508 The interface cloning API and ABI has changed. The following
1509 modules need to be recompiled together with kernel:
1510 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1511 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1512 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1515 The sdhci driver was split in two parts: sdhci (generic SD Host
1516 Controller logic) and sdhci_pci (actual hardware driver).
1517 No kernel config modifications are required, but if you
1518 load sdhc as a module you must switch to sdhci_pci instead.
1521 Import the FUSE kernel and userland support into base system.
1524 The GNU sort(1) program has been removed since the BSD-licensed
1525 sort(1) has been the default for quite some time and no serious
1526 problems have been reported. The corresponding WITH_GNU_SORT
1530 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1531 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1535 The net80211(4) ABI has been changed to allow for improved driver
1536 PS-POLL and power-save support. All wireless drivers need to be
1537 recompiled to work with the new kernel.
1540 The random(4) support for the VIA hardware random number
1541 generator (`PADLOCK') is no longer enabled unconditionally.
1542 Add the padlock_rng device in the custom kernel config if
1543 needed. The GENERIC kernels on i386 and amd64 do include the
1544 device, so the change only affects the custom kernel
1548 The pf(4) packet filter ABI has been changed. pfctl(8) and
1549 snmp_pf module need to be recompiled to work with new kernel.
1552 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1553 to -HEAD. Pools that have empty_bpobj in active state can not be
1554 imported read-write with ZFS implementations that do not support
1555 this feature. For more information read the zpool-features(5)
1559 The sparc64 ZFS loader has been changed to no longer try to auto-
1560 detect ZFS providers based on diskN aliases but now requires these
1561 to be explicitly listed in the OFW boot-device environment variable.
1564 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1565 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1566 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1569 The following sysctls and tunables have been renamed for consistency
1570 with other variables:
1571 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1572 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1575 The sort utility has been replaced with BSD sort. For now, GNU sort
1576 is also available as "gnusort" or the default can be set back to
1577 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1578 installed as "bsdsort".
1581 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1582 Starting with this version the old system of ZFS pool versioning
1583 is superseded by "feature flags". This concept enables forward
1584 compatibility against certain future changes in functionality of ZFS
1585 pools. The first read-only compatible "feature flag" for ZFS pools
1586 is named "com.delphix:async_destroy". For more information
1587 read the new zpool-features(5) manual page.
1588 Please refer to the "ZFS notes" section of this file for information
1589 on upgrading boot ZFS pools.
1592 The malloc(3) implementation embedded in libc now uses sources imported
1593 as contrib/jemalloc. The most disruptive API change is to
1594 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1595 delete it prior to installworld, and optionally re-create it using the
1596 new format after rebooting. See malloc.conf(5) for details
1597 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1601 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1602 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1603 now spelled mips. This is to aid compatibility with third-party
1604 software that expects this naming scheme in uname(3). Little-endian
1605 settings are unchanged. If you are updating a big-endian mips64 machine
1606 from before this change, you may need to set MACHINE_ARCH=mips64 in
1607 your environment before the new build system will recognize your machine.
1610 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1614 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1615 nullfs(5) did not pass through all behaviours to the underlying layer,
1616 as a result if we bound to a socket on the lower layer we could connect
1617 only to the lower path; if we bound to the upper layer we could connect
1618 only to the upper path. The new behavior is one can connect to both the
1619 lower and the upper paths regardless what layer path one binds to.
1622 The getifaddrs upgrade path broken with 20111215 has been restored.
1623 If you have upgraded in between 20111215 and 20120209 you need to
1624 recompile libc again with your kernel. You still need to recompile
1625 world to be able to configure CARP but this restriction already
1626 comes from 20111215.
1629 The set_rcvar() function has been removed from /etc/rc.subr. All
1630 base and ports rc.d scripts have been updated, so if you have a
1631 port installed with a script in /usr/local/etc/rc.d you can either
1632 hand-edit the rcvar= line, or reinstall the port.
1634 An easy way to handle the mass-update of /etc/rc.d:
1635 rm /etc/rc.d/* && mergemaster -i
1638 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1639 on the current CPU and prevents other threads from running.
1640 This behavior can be reverted using the kern.stop_scheduler_on_panic
1642 The new behavior can be incompatible with kern.sync_on_panic.
1645 The carp(4) facility has been changed significantly. Configuration
1646 of the CARP protocol via ifconfig(8) has changed, as well as format
1647 of CARP events submitted to devd(8) has changed. See manual pages
1648 for more information. The arpbalance feature of carp(4) is currently
1649 not supported anymore.
1651 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1652 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1653 need to be recompiled.
1656 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1660 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1661 explicitely support non-MPSAFE filesystems.
1662 It is on by default for all supported platform at this present
1666 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1667 i386 and pc98 GENERIC kernel configuration files.
1670 sysinstall has been removed
1673 The stable/9 branch created in subversion. This corresponds to the
1674 RELENG_9 branch in CVS.
1680 Avoid using make -j when upgrading. While generally safe, there are
1681 sometimes problems using -j to upgrade. If your upgrade fails with
1682 -j, please try again without -j. From time to time in the past there
1683 have been problems using -j with buildworld and/or installworld. This
1684 is especially true when upgrading between "distant" versions (eg one
1685 that cross a major release boundary or several minor releases, or when
1686 several months have passed on the -current branch).
1688 Sometimes, obscure build problems are the result of environment
1689 poisoning. This can happen because the make utility reads its
1690 environment when searching for values for global variables. To run
1691 your build attempts in an "environmental clean room", prefix all make
1692 commands with 'env -i '. See the env(1) manual page for more details.
1694 When upgrading from one major version to another it is generally best
1695 to upgrade to the latest code in the currently installed branch first,
1696 then do an upgrade to the new branch. This is the best-tested upgrade
1697 path, and has the highest probability of being successful. Please try
1698 this approach before reporting problems with a major version upgrade.
1700 When upgrading a live system, having a root shell around before
1701 installing anything can help undo problems. Not having a root shell
1702 around can lead to problems if pam has changed too much from your
1703 starting point to allow continued authentication after the upgrade.
1705 This file should be read as a log of events. When a later event changes
1706 information of a prior event, the prior event should not be deleted.
1707 Instead, a pointer to the entry with the new information should be
1708 placed in the old entry. Readers of this file should also sanity check
1709 older entries before relying on them blindly. Authors of new entries
1710 should write them with this in mind.
1714 When upgrading the boot ZFS pool to a new version, always follow
1717 1.) recompile and reinstall the ZFS boot loader and boot block
1718 (this is part of "make buildworld" and "make installworld")
1720 2.) update the ZFS boot block on your boot drive
1722 The following example updates the ZFS boot block on the first
1723 partition (freebsd-boot) of a GPT partitioned drive ada0:
1724 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1726 Non-boot pools do not need these updates.
1730 If you are updating from a prior version of FreeBSD (even one just
1731 a few days old), you should follow this procedure. It is the most
1732 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1734 make kernel-toolchain
1735 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1736 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1738 To test a kernel once
1739 ---------------------
1740 If you just want to boot a kernel once (because you are not sure
1741 if it works, or if you want to boot a known bad kernel to provide
1742 debugging information) run
1743 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1744 nextboot -k testkernel
1746 To just build a kernel when you know that it won't mess you up
1747 --------------------------------------------------------------
1748 This assumes you are already running a CURRENT system. Replace
1749 ${arch} with the architecture of your machine (e.g. "i386",
1750 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1752 cd src/sys/${arch}/conf
1753 config KERNEL_NAME_HERE
1754 cd ../compile/KERNEL_NAME_HERE
1759 If this fails, go to the "To build a kernel" section.
1761 To rebuild everything and install it on the current system.
1762 -----------------------------------------------------------
1763 # Note: sometimes if you are running current you gotta do more than
1764 # is listed here if you are upgrading from a really old current.
1766 <make sure you have good level 0 dumps>
1768 make kernel KERNCONF=YOUR_KERNEL_HERE
1770 <reboot in single user> [3]
1777 To cross-install current onto a separate partition
1778 --------------------------------------------------
1779 # In this approach we use a separate partition to hold
1780 # current's root, 'usr', and 'var' directories. A partition
1781 # holding "/", "/usr" and "/var" should be about 2GB in
1784 <make sure you have good level 0 dumps>
1787 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1788 <maybe newfs current's root partition>
1789 <mount current's root partition on directory ${CURRENT_ROOT}>
1790 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1791 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1792 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1793 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1794 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1795 <reboot into current>
1796 <do a "native" rebuild/install as described in the previous section>
1797 <maybe install compatibility libraries from ports/misc/compat*>
1801 To upgrade in-place from stable to current
1802 ----------------------------------------------
1803 <make sure you have good level 0 dumps>
1805 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1807 <reboot in single user> [3]
1814 Make sure that you've read the UPDATING file to understand the
1815 tweaks to various things you need. At this point in the life
1816 cycle of current, things change often and you are on your own
1817 to cope. The defaults can also change, so please read ALL of
1818 the UPDATING entries.
1820 Also, if you are tracking -current, you must be subscribed to
1821 freebsd-current@freebsd.org. Make sure that before you update
1822 your sources that you have read and understood all the recent
1823 messages there. If in doubt, please track -stable which has
1824 much fewer pitfalls.
1826 [1] If you have third party modules, such as vmware, you
1827 should disable them at this point so they don't crash your
1830 [3] From the bootblocks, boot -s, and then do
1835 adjkerntz -i # if CMOS is wall time
1836 Also, when doing a major release upgrade, it is required that
1837 you boot into single user mode to do the installworld.
1839 [4] Note: This step is non-optional. Failure to do this step
1840 can result in a significant reduction in the functionality of the
1841 system. Attempting to do it by hand is not recommended and those
1842 that pursue this avenue should read this file carefully, as well
1843 as the archives of freebsd-current and freebsd-hackers mailing lists
1844 for potential gotchas. The -U option is also useful to consider.
1845 See mergemaster(8) for more information.
1847 [5] Usually this step is a noop. However, from time to time
1848 you may need to do this if you get unknown user in the following
1849 step. It never hurts to do it all the time. You may need to
1850 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1851 install) after the buildworld before this step if you last updated
1852 from current before 20130425 or from -stable before 20130430.
1854 [6] This only deletes old files and directories. Old libraries
1855 can be deleted by "make delete-old-libs", but you have to make
1856 sure that no program is using those libraries anymore.
1858 [8] In order to have a kernel that can run the 4.x binaries needed to
1859 do an installworld, you must include the COMPAT_FREEBSD4 option in
1860 your kernel. Failure to do so may leave you with a system that is
1861 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1862 required to run the 5.x binaries on more recent kernels. And so on
1863 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1865 Make sure that you merge any new devices from GENERIC since the
1866 last time you updated your kernel config file.
1868 [9] When checking out sources, you must include the -P flag to have
1869 cvs prune empty directories.
1871 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1872 "?=" instead of the "=" assignment operator, so that buildworld can
1873 override the CPUTYPE if it needs to.
1875 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1876 not on the command line, or in /etc/make.conf. buildworld will
1877 warn if it is improperly defined.
1880 This file contains a list, in reverse chronological order, of major
1881 breakages in tracking -current. It is not guaranteed to be a complete
1882 list of such breakages, and only contains entries since September 23, 2011.
1883 If you need to see UPDATING entries from before that date, you will need
1884 to fetch an UPDATING file from an older FreeBSD release.
1886 Copyright information:
1888 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1890 Redistribution, publication, translation and use, with or without
1891 modification, in full or in part, in any form or format of this
1892 document are permitted without further permission from the author.
1894 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1895 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1896 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1897 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1898 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1899 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1900 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1901 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1902 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1903 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1904 POSSIBILITY OF SUCH DAMAGE.
1906 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob