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 20181219 p7 FreeBSD-SA-18:15.bootpd
20 FreeBSD-EN-18:16.ptrace
24 bootpd: validate hardware type [SA-18:15.bootpd]
26 Only clear a pending thread event if one is pending. [EN-18:16.ptrace]
28 Update the free page count when blacklisting pages. [EN-18:17.vm]
30 Resolve a hang in ZFS during vnode reclamation [EN-18:18.zfs]
33 20181204 p6 FreeBSD-SA-18:14.bhyve
35 Fix insufficient bounds checking in bhyve(8) device model.
38 20181127 p5 FreeBSD-SA-18:13.nfs
40 FreeBSD-EN-18:14.tzdata
41 FreeBSD-EN-18:15.loader
43 Fix multiple vulnerabilities in NFS server code. [SA-18:13.nfs]
45 Fix ICMP buffer underwrite. [EN-18:13.icmp]
47 Timezone database information update. [EN-18:14.tzdata]
49 Fix deferred kernel loading breaks loader password. [EN-18:15.loader]
51 20180927 p4 FreeBSD-EN-18:09.ip
52 FreeBSD-EN-18:10.syscall
53 FreeBSD-EN-18:11.listen
56 Fix regression in IPv6 fragment reassembly. [EN-18:09.ip]
58 Fix NULL pointer dereference in freebsd4_getfsstat. [EN-18:10.syscall]
60 Fix DoS in listen syscall over IPv6 socket. [EN-18:11.listen]
62 Fix small kernel memory disclosures. [EN-18:12.mem]
64 20180912 p3 FreeBSD-SA-18:12.elf
65 FreeBSD-EN-18:08.lazyfpu
67 Fix improper elf header parsing. [SA-18:12.elf]
69 Fix regression in Lazy FPU remediation. [EN-18:08.lazyfpu]
71 20180814 p2 FreeBSD-SA-18:08.tcp [revised]
74 FreeBSD-SA-18:11.hostapd
76 Revise manual pages. [SA-18:08.tcp]
78 Fix L1 Terminal Fault (L1TF) kernel information disclosure.
81 Fix resource exhaustion in IP fragment reassembly. [SA-18:10.ip]
83 Fix unauthenticated EAPOL-Key decryption vulnerability.
86 20180806 p1 FreeBSD-SA-18:08.tcp
88 Fix resource exhaustion in TCP reassembly.
94 The tz database (tzdb) has been updated to 2018e. This version more
95 correctly models time stamps in time zones with negative DST such as
96 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
97 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
98 time zone abbreviations and the tm_isdst flag.
101 The use of RSS hash from the network card aka flowid has been
102 disabled by default for lagg(4) as it's currently incompatible with
103 the lacp and loadbalance protocols.
105 This can be re-enabled by setting the following in loader.conf:
106 net.link.lagg.default_use_flowid="1"
109 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
110 6.0.0. Please see the 20141231 entry below for information about
111 prerequisites and upgrading, if you are not already using clang 3.5.0
115 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
116 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
117 to WITH/OUT_LOADER_GELI.
120 The geli password typed at boot is now hidden. To restore the previous
121 behavior, see geli(8) for configuration options.
123 The SW_WATCHDOG option is no longer necessary to enable the
124 hardclock-based software watchdog if no hardware watchdog is
125 configured. As before, SW_WATCHDOG will cause the software
126 watchdog to be enabled even if a hardware watchdog is configured.
129 lint(1) binaries and library are no longer built by default. To
130 enable building them, define WITH_LINT in src.conf. If you are using
131 a FreeBSD 12 or later system to build 11-stable, you may need to
132 install a lint(1) binary to use WITH_LINT.
135 When building multiple kernels using KERNCONF, non-existent KERNCONF
136 files will produce an error and buildkernel will fail. Previously
137 missing KERNCONF files silently failed giving no indication as to
138 why, only to subsequently discover during installkernel that the
139 desired kernel was never built in the first place.
142 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
143 Please see the 20141231 entry below for information about prerequisites
144 and upgrading, if you are not already using clang 3.5.0 or higher.
147 Since the switch to GPT disk labels, fsck for UFS/FFS has been
148 unable to automatically find alternate superblocks. As of r322806,
149 the information needed to find alternate superblocks has been
150 moved to the end of the area reserved for the boot block.
151 Filesystems created with a newfs of this vintage or later
152 will create the recovery information. If you have a filesystem
153 created prior to this change and wish to have a recovery block
154 created for your filesystem, you can do so by running fsck in
155 forground mode (i.e., do not use the -p or -y options). As it
156 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
157 to which you should answer yes.
160 arm64 builds now use the base system LLD 4.0.0 linker by default,
161 instead of requiring that the aarch64-binutils port or package be
162 installed. To continue using aarch64-binutils, set
163 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
166 The ctl.ko module no longer implements the iSCSI target frontend:
167 cfiscsi.ko does instead.
169 If building cfiscsi.ko as a kernel module, the module can be loaded
170 via one of the following methods:
171 - `cfiscsi_load="YES"` in loader.conf(5).
172 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
173 - ctladm(8)/ctld(8), when compiled with iSCSI support
174 (`WITH_ISCSI=yes` in src.conf(5))
176 Please see cfiscsi(4) for more details.
179 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
180 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
181 same source (previously, the dependency of mmcsd.ko on mmc.ko was
182 missing, but mmcsd.ko now will refuse to load if it is incompatible
186 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
187 use any explicitly assigned loopback address available in the jail
188 instead of using the first assigned address of the jail.
191 As of r316810 for ipfilter, keep frags is no longer assumed when
192 keep state is specified in a rule. r316810 aligns ipfilter with
193 documentation in man pages separating keep frags from keep state.
194 This allows keep state to specified without forcing keep frags
195 and allows keep frags to be specified independently of keep state.
196 To maintain previous behaviour, also specify keep frags with
197 keep state (as documented in ipf.conf.5).
200 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
201 Please see the 20141231 entry below for information about prerequisites
202 and upgrading, if you are not already using clang 3.5.0 or higher.
205 The code that provides support for ZFS .zfs/ directory functionality
206 has been reimplemented. It's not possible now to create a snapshot
207 by mkdir under .zfs/snapshot/. That should be the only user visible
211 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
212 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
213 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
214 and now NAT-T is supported by default. Security associations now use
215 the single namespace for SPI allocation, so if you use several manually
216 configured security associations with the same SPI, this configuration
220 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
221 Please see the 20141231 entry below for information about prerequisites
222 and upgrading, if you are not already using clang 3.5.0 or higher.
225 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
226 Please see the 20141231 entry below for information about prerequisites
227 and upgrading, if you are not already using clang 3.5.0 or higher.
230 The layout of the pmap structure has changed for powerpc to put the pmap
231 statistics at the front for all CPU variations. libkvm(3) and all tools
232 that link against it need to be recompiled.
235 isl(4) and cyapa(4) drivers now require a new driver,
236 chromebook_platform(4), to work properly on Chromebook-class hardware.
237 On other types of hardware the drivers may need to be configured using
238 device hints. Please see the corresponding manual pages for details.
241 Relocatable object files with the extension of .So have been renamed
242 to use an extension of .pico instead. The purpose of this change is
243 to avoid a name clash with shared libraries on case-insensitive file
244 systems. On those file systems, foo.So is the same file as foo.so.
247 The libc stub for the pipe(2) system call has been replaced with
248 a wrapper that calls the pipe2(2) system call and the pipe(2)
249 system call is now only implemented by the kernels that include
250 "options COMPAT_FREEBSD10" in their config file (this is the
251 default). Users should ensure that this option is enabled in
252 their kernel or upgrade userspace to r302092 before upgrading their
256 CAM will now strip leading spaces from SCSI disks' serial numbers.
257 This will effect users who create UFS filesystems on SCSI disks using
258 those disk's diskid device nodes. For example, if /etc/fstab
259 previously contained a line like
260 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
261 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
262 transforms like gmirror may also be affected. ZFS users should
266 The bitstring(3) API has been updated with new functionality and
267 improved performance. But it is binary-incompatible with the old API.
268 Objects built with the new headers may not be linked against objects
269 built with the old headers.
272 The brk and sbrk functions have been removed from libc on arm64.
273 Binutils from ports has been updated to not link to these
274 functions and should be updated to the latest version before
275 installing a new libc.
278 The armv6 port now defaults to hard float ABI. Limited support
279 for running both hardfloat and soft float on the same system
280 is available using the libraries installed with -DWITH_LIBSOFT.
281 This has only been tested as an upgrade path for installworld
282 and packages may fail or need manual intervention to run. New
283 packages will be needed.
285 To update an existing self-hosted armv6hf system, you must add
286 TARGET_ARCH=armv6 on the make command line for both the build
287 and the install steps.
290 Kernel modules compiled outside of a kernel build now default to
291 installing to /boot/modules instead of /boot/kernel. Many kernel
292 modules built this way (such as those in ports) already overrode
293 KMODDIR explicitly to install into /boot/modules. However,
294 manually building and installing a module from /sys/modules will
295 now install to /boot/modules instead of /boot/kernel.
298 The CAM I/O scheduler has been committed to the kernel. There should be
299 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
300 list of known rogues that claim support for this but actually corrupt
301 data is believed to be complete, be on the lookout for data
302 corruption. The known rogue list is believed to be complete:
304 o Crucial MX100, M550 drives with MU01 firmware.
305 o Micron M510 and M550 drives with MU01 firmware.
306 o Micron M500 prior to MU07 firmware
307 o Samsung 830, 840, and 850 all firmwares
308 o FCCT M500 all firmwares
310 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
311 with working NCQ TRIM. For Micron branded drives, see your sales rep for
312 updated firmware. Black listed drives will work correctly because these
313 drives work correctly so long as no NCQ TRIMs are sent to them. Given
314 this list is the same as found in Linux, it's believed there are no
315 other rogues in the market place. All other models from the above
318 To be safe, if you are at all concerned, you can quirk each of your
319 drives to prevent NCQ from being sent by setting:
320 kern.cam.ada.X.quirks="0x2"
321 in loader.conf. If the drive requires the 4k sector quirk, set the
325 The FAST_DEPEND build option has been removed and its functionality is
326 now the one true way. The old mkdep(1) style of 'make depend' has
327 been removed. See 20160311 for further details.
330 Resource range types have grown from unsigned long to uintmax_t. All
331 drivers, and anything using libdevinfo, need to be recompiled.
334 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
335 builds. It no longer runs mkdep(1) during 'make depend', and the
336 'make depend' stage can safely be skipped now as it is auto ran
337 when building 'make all' and will generate all SRCS and DPSRCS before
338 building anything else. Dependencies are gathered at compile time with
339 -MF flags kept in separate .depend files per object file. Users should
340 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
344 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
345 kernel modules. Therefore, if you load any kernel modules at boot time,
346 please install the boot loaders after you install the kernel, but before
350 make kernel KERNCONF=YOUR_KERNEL_HERE
351 make -C sys/boot install
352 <reboot in single user>
354 Then follow the usual steps, described in the General Notes section,
358 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
359 see the 20141231 entry below for information about prerequisites and
360 upgrading, if you are not already using clang 3.5.0 or higher.
363 The AIO subsystem is now a standard part of the kernel. The
364 VFS_AIO kernel option and aio.ko kernel module have been removed.
365 Due to stability concerns, asynchronous I/O requests are only
366 permitted on sockets and raw disks by default. To enable
367 asynchronous I/O requests on all file types, set the
368 vfs.aio.enable_unsafe sysctl to a non-zero value.
371 The ELF object manipulation tool objcopy is now provided by the
372 ELF Tool Chain project rather than by GNU binutils. It should be a
373 drop-in replacement, with the addition of arm64 support. The
374 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
375 to obtain the GNU version if necessary.
378 Building ZFS pools on top of zvols is prohibited by default. That
379 feature has never worked safely; it's always been prone to deadlocks.
380 Using a zvol as the backing store for a VM guest's virtual disk will
381 still work, even if the guest is using ZFS. Legacy behavior can be
382 restored by setting vfs.zfs.vol.recursive=1.
385 The NONE and HPN patches has been removed from OpenSSH. They are
386 still available in the security/openssh-portable port.
389 With the addition of ypldap(8), a new _ypldap user is now required
390 during installworld. "mergemaster -p" can be used to add the user
391 prior to installworld, as documented in the handbook.
394 The tftp loader (pxeboot) now uses the option root-path directive. As a
395 consequence it no longer looks for a pxeboot.4th file on the tftp
396 server. Instead it uses the regular /boot infrastructure as with the
400 The code to start recording plug and play data into the modules has
401 been committed. While the old tools will properly build a new kernel,
402 a number of warnings about "unknown metadata record 4" will be produced
403 for an older kldxref. To avoid such warnings, make sure to rebuild
404 the kernel toolchain (or world). Make sure that you have r292078 or
405 later when trying to build 292077 or later before rebuilding.
408 Debug data files are now built by default with 'make buildworld' and
409 installed with 'make installworld'. This facilitates debugging but
410 requires more disk space both during the build and for the installed
411 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
415 r291527 changed the internal interface between the nfsd.ko and
416 nfscommon.ko modules. As such, they must both be upgraded to-gether.
417 __FreeBSD_version has been bumped because of this.
420 Add support for unicode collation strings leads to a change of
421 order of files listed by ls(1) for example. To get back to the old
422 behaviour, set LC_COLLATE environment variable to "C".
424 Databases administrators will need to reindex their databases given
425 collation results will be different.
427 Due to a bug in install(1) it is recommended to remove the ancient
428 locales before running make installworld.
430 rm -rf /usr/share/locale/*
433 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
434 libcrypto.so.7 or libssl.so.7 must be recompiled.
437 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
438 Kernel modules isp_2400_multi and isp_2500_multi were removed and
439 should be replaced with isp_2400 and isp_2500 modules respectively.
442 The build previously allowed using 'make -n' to not recurse into
443 sub-directories while showing what commands would be executed, and
444 'make -n -n' to recursively show commands. Now 'make -n' will recurse
445 and 'make -N' will not.
448 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
449 and etcupdate will now use this file. A custom sendmail.cf is now
450 updated via this mechanism rather than via installworld. If you had
451 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
452 want to remove the exclusion or change it to "always install".
453 /etc/mail/sendmail.cf is now managed the same way regardless of
454 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
455 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
458 Compatibility shims for legacy ATA device names have been removed.
459 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
460 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
461 environment variables, /dev/ad* and /dev/ar* symbolic links.
464 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
465 Please see the 20141231 entry below for information about prerequisites
466 and upgrading, if you are not already using clang 3.5.0 or higher.
469 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
470 and renamed from .symbols to .debug. This reduces the size requirements
471 on the boot partition or file system and provides consistency with
472 userland debug files.
474 When using the supported kernel installation method the
475 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
476 as is done with /boot/kernel.
478 Developers wishing to maintain the historical behavior of installing
479 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
482 The wireless drivers had undergone changes that remove the 'parent
483 interface' from the ifconfig -l output. The rc.d network scripts
484 used to check presence of a parent interface in the list, so old
485 scripts would fail to start wireless networking. Thus, etcupdate(3)
486 or mergemaster(8) run is required after kernel update, to update your
487 rc.d scripts in /etc.
490 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
491 These configurations are now automatically interpreted as
492 'scrub fragment reassemble'.
495 Kernel-loadable modules for the random(4) device are back. To use
496 them, the kernel must have
499 options RANDOM_LOADABLE
501 kldload(8) can then be used to load random_fortuna.ko
502 or random_yarrow.ko. Please note that due to the indirect
503 function calls that the loadable modules need to provide,
504 the build-in variants will be slightly more efficient.
506 The random(4) kernel option RANDOM_DUMMY has been retired due to
507 unpopularity. It was not all that useful anyway.
510 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
511 Control over building the ELF Tool Chain tools is now provided by
512 the WITHOUT_TOOLCHAIN knob.
515 The polarity of Pulse Per Second (PPS) capture events with the
516 uart(4) driver has been corrected. Prior to this change the PPS
517 "assert" event corresponded to the trailing edge of a positive PPS
518 pulse and the "clear" event was the leading edge of the next pulse.
520 As the width of a PPS pulse in a typical GPS receiver is on the
521 order of 1 millisecond, most users will not notice any significant
522 difference with this change.
524 Anyone who has compensated for the historical polarity reversal by
525 configuring a negative offset equal to the pulse width will need to
526 remove that workaround.
529 The default group assigned to /dev/dri entries has been changed
530 from 'wheel' to 'video' with the id of '44'. If you want to have
531 access to the dri devices please add yourself to the video group
534 # pw groupmod video -m $USER
537 The menu.rc and loader.rc files will now be replaced during
538 upgrades. Please migrate local changes to menu.rc.local and
539 loader.rc.local instead.
542 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
543 strings and strip have been removed. The src.conf(5) knob
544 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
547 As ZFS requires more kernel stack pages than is the default on some
548 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
549 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
551 Please consider using 'options KSTACK_PAGES=X' where X is greater
552 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
555 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
556 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
557 default, i.e., they will not contain "::". For example, instead
558 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
559 to have a more specific match, such as different map entries for
560 IPv6:0:0 vs IPv6:0. This change requires that configuration
561 data (including maps, files, classes, custom ruleset, etc.) must
562 use the same format, so make certain such configuration data is
563 upgrading. As a very simple check search for patterns like
564 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
565 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
566 the cf option UseCompressedIPv6Addresses.
569 The default kernel entropy-processing algorithm is now
570 Fortuna, replacing Yarrow.
572 Assuming you have 'device random' in your kernel config
573 file, the configurations allow a kernel option to override
574 this default. You may choose *ONE* of:
576 options RANDOM_YARROW # Legacy /dev/random algorithm.
577 options RANDOM_DUMMY # Blocking-only driver.
579 If you have neither, you get Fortuna. For most people,
580 read no further, Fortuna will give a /dev/random that works
581 like it always used to, and the difference will be irrelevant.
583 If you remove 'device random', you get *NO* kernel-processed
584 entropy at all. This may be acceptable to folks building
585 embedded systems, but has complications. Carry on reading,
586 and it is assumed you know what you need.
588 *PLEASE* read random(4) and random(9) if you are in the
589 habit of tweaking kernel configs, and/or if you are a member
590 of the embedded community, wanting specific and not-usual
591 behaviour from your security subsystems.
593 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
594 random', you will NOT have a functioning /dev/random, and
595 many cryptographic features will not work, including SSH.
596 You may also find strange behaviour from the random(3) set
597 of library functions, in particular sranddev(3), srandomdev(3)
598 and arc4random(3). The reason for this is that the KERN_ARND
599 sysctl only returns entropy if it thinks it has some to
600 share, and with RANDOM_DUMMY or no 'device random' this
604 An additional fix for the issue described in the 20150614 sendmail
605 entry below has been been committed in revision 284717.
608 FreeBSD's old make (fmake) has been removed from the system. It is
609 available as the devel/fmake port or via pkg install fmake.
612 The fix for the issue described in the 20150614 sendmail entry
613 below has been been committed in revision 284436. The work
614 around described in that entry is no longer needed unless the
615 default setting is overridden by a confDH_PARAMETERS configuration
616 setting of '5' or pointing to a 512 bit DH parameter file.
619 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
620 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
621 and devel/kyua to version 0.20+ and adjust any calling code to work
622 with Kyuafile and kyua.
625 The import of openssl to address the FreeBSD-SA-15:10.openssl
626 security advisory includes a change which rejects handshakes
627 with DH parameters below 768 bits. sendmail releases prior
628 to 8.15.2 (not yet released), defaulted to a 512 bit
629 DH parameter setting for client connections. To work around
630 this interoperability, sendmail can be configured to use a
631 2048 bit DH parameter by:
633 1. Edit /etc/mail/`hostname`.mc
634 2. If a setting for confDH_PARAMETERS does not exist or
635 exists and is set to a string beginning with '5',
637 3. If a setting for confDH_PARAMETERS exists and is set to
638 a file path, create a new file with:
639 openssl dhparam -out /path/to/file 2048
640 4. Rebuild the .cf file:
641 cd /etc/mail/; make; make install
643 cd /etc/mail/; make restart
645 A sendmail patch is coming, at which time this file will be
649 Generation of legacy formatted entries have been disabled by default
650 in pwd_mkdb(8), as all base system consumers of the legacy formatted
651 entries were converted to use the new format by default when the new,
652 machine independent format have been added and supported since FreeBSD
655 Please see the pwd_mkdb(8) manual page for further details.
658 Clang and llvm have been upgraded to 3.6.1 release. Please see the
659 20141231 entry below for information about prerequisites and upgrading,
660 if you are not already using 3.5.0 or higher.
663 TI platform code switched to using vendor DTS files and this update
664 may break existing systems running on Beaglebone, Beaglebone Black,
667 - dtb files should be regenerated/reinstalled. Filenames are the
668 same but content is different now
669 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
670 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
671 addressing scheme is now pin 25 on /dev/gpioc3.
672 - Pandaboard: /etc/ttys should be updated, serial console device is
673 now /dev/ttyu2, not /dev/ttyu0
676 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
677 If you need the GNU extension from groff soelim(1), install groff
678 from package: pkg install groff, or via ports: textproc/groff.
681 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
682 defined in symlink(7); previously symlinks were silently ignored.
685 The const qualifier has been removed from iconv(3) to comply with
686 POSIX. The ports tree is aware of this from r384038 onwards.
689 Libraries specified by LIBADD in Makefiles must have a corresponding
690 DPADD_<lib> variable to ensure correct dependencies. This is now
691 enforced in src.libnames.mk.
694 From legacy ata(4) driver was removed support for SATA controllers
695 supported by more functional drivers ahci(4), siis(4) and mvs(4).
696 Kernel modules ataahci and ataadaptec were removed completely,
697 replaced by ahci and mvs modules respectively.
700 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
701 the 20141231 entry below for information about prerequisites and
702 upgrading, if you are not already using 3.5.0 or higher.
705 The 32-bit PowerPC kernel has been changed to a position-independent
706 executable. This can only be booted with a version of loader(8)
707 newer than January 31, 2015, so make sure to update both world and
708 kernel before rebooting.
711 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
712 but before r278950, the RNG was not seeded properly. Immediately
713 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
714 ssh keys or openssl keys) that were generated w/ a kernel from that
715 range. This does not affect programs that directly used /dev/random
716 or /dev/urandom. All userland uses of arc4random(3) are affected.
719 The autofs(4) ABI was changed in order to restore binary compatibility
720 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
724 The powerpc64 kernel has been changed to a position-independent
725 executable. This can only be booted with a new version of loader(8),
726 so make sure to update both world and kernel before rebooting.
729 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
730 only release, no new features have been added. Please see the 20141231
731 entry below for information about prerequisites and upgrading, if you
732 are not already using 3.5.0.
735 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
736 taken from the ELF Tool Chain project rather than GNU binutils. They
737 should be drop-in replacements, with the addition of arm64 support.
738 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
739 binutils tools, if necessary. See 20150805 for updated information.
742 The default Unbound configuration now enables remote control
743 using a local socket. Users who have already enabled the
744 local_unbound service should regenerate their configuration
745 by running "service local_unbound setup" as root.
748 The GNU texinfo and GNU info pages have been removed.
749 To be able to view GNU info pages please install texinfo from ports.
752 Clang, llvm and lldb have been upgraded to 3.5.0 release.
754 As of this release, a prerequisite for building clang, llvm and lldb is
755 a C++11 capable compiler and C++11 standard library. This means that to
756 be able to successfully build the cross-tools stage of buildworld, with
757 clang as the bootstrap compiler, your system compiler or cross compiler
758 should either be clang 3.3 or later, or gcc 4.8 or later, and your
759 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
762 On any standard FreeBSD 10.x or 11.x installation, where clang and
763 libc++ are on by default (that is, on x86 or arm), this should work out
766 On 9.x installations where clang is enabled by default, e.g. on x86 and
767 powerpc, libc++ will not be enabled by default, so libc++ should be
768 built (with clang) and installed first. If both clang and libc++ are
769 missing, build clang first, then use it to build libc++.
771 On 8.x and earlier installations, upgrade to 9.x first, and then follow
772 the instructions for 9.x above.
774 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
775 default, and do not build clang.
777 Many embedded systems are resource constrained, and will not be able to
778 build clang in a reasonable time, or in some cases at all. In those
779 cases, cross building bootable systems on amd64 is a workaround.
781 This new version of clang introduces a number of new warnings, of which
782 the following are most likely to appear:
786 This warns in two cases, for both C and C++:
787 * When the code is trying to take the absolute value of an unsigned
788 quantity, which is effectively a no-op, and almost never what was
789 intended. The code should be fixed, if at all possible. If you are
790 sure that the unsigned quantity can be safely cast to signed, without
791 loss of information or undefined behavior, you can add an explicit
792 cast, or disable the warning.
794 * When the code is trying to take an absolute value, but the called
795 abs() variant is for the wrong type, which can lead to truncation.
796 If you want to disable the warning instead of fixing the code, please
797 make sure that truncation will not occur, or it might lead to unwanted
800 -Wtautological-undefined-compare and
801 -Wundefined-bool-conversion
803 These warn when C++ code is trying to compare 'this' against NULL, while
804 'this' should never be NULL in well-defined C++ code. However, there is
805 some legacy (pre C++11) code out there, which actively abuses this
806 feature, which was less strictly defined in previous C++ versions.
808 Squid and openjdk do this, for example. The warning can be turned off
809 for C++98 and earlier, but compiling the code in C++11 mode might result
810 in unexpected behavior; for example, the parts of the program that are
811 unreachable could be optimized away.
814 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
815 kernel sources have been removed. The .h files remain, since some
816 utilities include them. This will need to be fixed later.
817 If "mount -t oldnfs ..." is attempted, it will fail.
818 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
819 the utilities will report errors.
822 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
823 directories to top level SUBDIR variable when their parent
824 directory is included in LOCAL_DIRS. Users with build systems with
825 such hierarchies and without SUBDIR entries in the parent
826 directory Makefiles should add them or add the directories to
830 faith(4) and faithd(8) have been removed from the base system. Faith
831 has been obsolete for a very long time.
834 vt(4), the new console driver, is enabled by default. It brings
835 support for Unicode and double-width characters, as well as
836 support for UEFI and integration with the KMS kernel video
839 You may need to update your console settings in /etc/rc.conf,
840 most probably the keymap. During boot, /etc/rc.d/syscons will
841 indicate what you need to do.
843 vt(4) still has issues and lacks some features compared to
844 syscons(4). See the wiki for up-to-date information:
845 https://wiki.freebsd.org/Newcons
847 If you want to keep using syscons(4), you can do so by adding
848 the following line to /boot/loader.conf:
852 pjdfstest has been integrated into kyua as an opt-in test suite.
853 Please see share/doc/pjdfstest/README for more details on how to
857 gperf has been removed from the base system for architectures
858 that use clang. Ports that require gperf will obtain it from the
862 pjdfstest has been moved from tools/regression/pjdfstest to
866 At svn r271982, The default linux compat kernel ABI has been adjusted
867 to 2.6.18 in support of the linux-c6 compat ports infrastructure
868 update. If you wish to continue using the linux-f10 compat ports,
869 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
870 encouraged to update their linux-compat packages to linux-c6 during
871 their next update cycle.
874 The ofwfb driver, used to provide a graphics console on PowerPC when
875 using vt(4), no longer allows mmap() of all physical memory. This
876 will prevent Xorg on PowerPC with some ATI graphics cards from
877 initializing properly unless x11-servers/xorg-server is updated to
881 The xdev targets have been converted to using TARGET and
882 TARGET_ARCH instead of XDEV and XDEV_ARCH.
885 The default unbound configuration has been modified to address
886 issues with reverse lookups on networks that use private
887 address ranges. If you use the local_unbound service, run
888 "service local_unbound setup" as root to regenerate your
889 configuration, then "service local_unbound reload" to load the
893 The GNU texinfo and GNU info pages are not built and installed
894 anymore, WITH_INFO knob has been added to allow to built and install
896 UPDATE: see 20150102 entry on texinfo's removal
899 The GNU readline library is now an INTERNALLIB - that is, it is
900 statically linked into consumers (GDB and variants) in the base
901 system, and the shared library is no longer installed. The
902 devel/readline port is available for third party software that
906 The Itanium architecture (ia64) has been removed from the list of
907 known architectures. This is the first step in the removal of the
911 Commit r268115 has added NFSv4.1 server support, merged from
912 projects/nfsv4.1-server. Since this includes changes to the
913 internal interfaces between the NFS related modules, a full
914 build of the kernel and modules will be necessary.
915 __FreeBSD_version has been bumped.
918 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
919 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
920 which differs from the behaviour controlled by this knob.)
923 Maximal length of the serial number in CTL was increased from 16 to
924 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
925 and ctld, need to be rebuilt to work with a new kernel.
928 The libatf-c and libatf-c++ major versions were downgraded to 0 and
929 1 respectively to match the upstream numbers. They were out of
930 sync because, when they were originally added to FreeBSD, the
931 upstream versions were not respected. These libraries are private
932 and not yet built by default, so renumbering them should be a
933 non-issue. However, unclean source trees will yield broken test
934 programs once the operator executes "make delete-old-libs" after a
937 Additionally, the atf-sh binary was made private by moving it into
938 /usr/libexec/. Already-built shell test programs will keep the
939 path to the old binary so they will break after "make delete-old"
942 If you are using WITH_TESTS=yes (not the default), wipe the object
943 tree and rebuild from scratch to prevent spurious test failures.
944 This is only needed once: the misnumbered libraries and misplaced
945 binaries have been added to OptionalObsoleteFiles.inc so they will
946 be removed during a clean upgrade.
949 Clang and llvm have been upgraded to 3.4.1 release.
952 We bogusly installed src.opts.mk in /usr/share/mk. This file should
953 be removed to avoid issues in the future (and has been added to
957 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
958 past, it affected all builds that used the bsd.*.mk files. The old
959 behavior was a bug, but people may have relied upon it. To get this
960 behavior back, you can .include /etc/src.conf from /etc/make.conf
961 (which is still global and isn't changed). This also changes the
962 behavior of incremental builds inside the tree of individual
963 directories. Set MAKESYSPATH to ".../share/mk" to do that.
964 Although this has survived make universe and some upgrade scenarios,
965 other upgrade scenarios may have broken. At least one form of
966 temporary breakage was fixed with MAKESYSPATH settings for buildworld
967 as well... In cases where MAKESYSPATH isn't working with this
968 setting, you'll need to set it to the full path to your tree.
970 One side effect of all this cleaning up is that bsd.compiler.mk
971 is no longer implicitly included by bsd.own.mk. If you wish to
972 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
976 The lindev device has been removed since /dev/full has been made a
977 standard device. __FreeBSD_version has been bumped.
980 The knob WITHOUT_VI was added to the base system, which controls
981 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
982 in order to reorder files share/termcap and didn't build ex(1) as a
983 build tool, so building/installing with WITH_VI is highly advised for
984 build hosts for older releases.
986 This issue has been fixed in stable/9 and stable/10 in r277022 and
987 r276991, respectively.
990 The YES_HESIOD knob has been removed. It has been obsolete for
991 a decade. Please move to using WITH_HESIOD instead or your builds
992 will silently lack HESIOD.
995 The uart(4) driver has been changed with respect to its handling
996 of the low-level console. Previously the uart(4) driver prevented
997 any process from changing the baudrate or the CLOCAL and HUPCL
998 control flags. By removing the restrictions, operators can make
999 changes to the serial console port without having to reboot.
1000 However, when getty(8) is started on the serial device that is
1001 associated with the low-level console, a misconfigured terminal
1002 line in /etc/ttys will now have a real impact.
1003 Before upgrading the kernel, make sure that /etc/ttys has the
1004 serial console device configured as 3wire without baudrate to
1005 preserve the previous behaviour. E.g:
1006 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1009 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1010 to improve performance. To re-enable it, if needed, run rpcbind
1011 with command line option -W.
1014 Switched back to the GPL dtc compiler due to updates in the upstream
1015 dts files not being supported by the BSDL dtc compiler. You will need
1016 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1017 may result while building dtb files during a kernel build if you fail
1018 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1021 Clang and llvm have been upgraded to 3.4 release.
1024 The nve(4) driver has been removed. Please use the nfe(4) driver
1025 for NVIDIA nForce MCP Ethernet adapters instead.
1028 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1029 This could cause certain C++ applications using shared libraries built
1030 against the previous version of libc++ to crash. The incompatibility
1031 has now been fixed, but any C++ applications or shared libraries built
1032 between r261283 and r261801 should be recompiled.
1035 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1036 capability mode support. Please note that enabling the feature in
1037 kernel is still highly recommended.
1040 OpenSSH is now built with sandbox support, and will use sandbox as
1041 the default privilege separation method. This requires Capsicum
1042 capability mode support in kernel.
1045 The libelf and libdwarf libraries have been updated to newer
1046 versions from upstream. Shared library version numbers for
1047 these two libraries were bumped. Any ports or binaries
1048 requiring these two libraries should be recompiled.
1049 __FreeBSD_version is bumped to 1100006.
1052 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1053 instead of providing an explicit one, this would prevent such
1054 Makefile from providing its own Kyuafile in the future during
1055 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1056 intervention is needed to clean an objdir if you use NO_CLEAN:
1057 # find /usr/obj -name Kyuafile | xargs rm -f
1060 The behavior of gss_pseudo_random() for the krb5 mechanism
1061 has changed, for applications requesting a longer random string
1062 than produced by the underlying enctype's pseudo-random() function.
1063 In particular, the random string produced from a session key of
1064 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1065 be different at the 17th octet and later, after this change.
1066 The counter used in the PRF+ construction is now encoded as a
1067 big-endian integer in accordance with RFC 4402.
1068 __FreeBSD_version is bumped to 1100004.
1071 The WITHOUT_ATF build knob has been removed and its functionality
1072 has been subsumed into the more generic WITHOUT_TESTS. If you were
1073 using the former to disable the build of the ATF libraries, you
1074 should change your settings to use the latter.
1077 The default version of mtree is nmtree which is obtained from
1078 NetBSD. The output is generally the same, but may vary
1079 slightly. If you found you need identical output adding
1080 "-F freebsd9" to the command line should do the trick. For the
1081 time being, the old mtree is available as fmtree.
1084 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1085 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1086 1.1.4_8 and verify bsdyml not linked in, before running "make
1088 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1090 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1093 The stable/10 branch has been created in subversion from head
1097 The rc.d/jail script has been updated to support jail(8)
1098 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1099 for per-jail configuration are automatically converted to
1100 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1101 This is transparently backward compatible. See below about some
1102 incompatibilities and rc.conf(5) manual page for more details.
1104 These variables are now deprecated in favor of jail(8) configuration
1105 file. One can use "rc.d/jail config <jname>" command to generate
1106 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1107 running the jail(8) utility. The default pathname of the
1108 configuration file is /etc/jail.conf and can be specified by
1109 using $jail_conf or $jail_<jname>_conf variables.
1111 Please note that jail_devfs_ruleset accepts an integer at
1112 this moment. Please consider to rewrite the ruleset name
1116 BIND has been removed from the base system. If all you need
1117 is a local resolver, simply enable and start the local_unbound
1118 service instead. Otherwise, several versions of BIND are
1119 available in the ports tree. The dns/bind99 port is one example.
1121 With this change, nslookup(1) and dig(1) are no longer in the base
1122 system. Users should instead use host(1) and drill(1) which are
1123 in the base system. Alternatively, nslookup and dig can
1124 be obtained by installing the dns/bind-tools port.
1127 With the addition of unbound(8), a new unbound user is now
1128 required during installworld. "mergemaster -p" can be used to
1129 add the user prior to installworld, as documented in the handbook.
1132 OpenSSH is now built with DNSSEC support, and will by default
1133 silently trust signed SSHFP records. This can be controlled with
1134 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1135 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1138 The GNU Compiler Collection and C++ standard library (libstdc++)
1139 are no longer built by default on platforms where clang is the system
1140 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1141 options in src.conf.
1144 The PROCDESC kernel option is now part of the GENERIC kernel
1145 configuration and is required for the rwhod(8) to work.
1146 If you are using custom kernel configuration, you should include
1150 The API and ABI related to the Capsicum framework was modified
1151 in backward incompatible way. The userland libraries and programs
1152 have to be recompiled to work with the new kernel. This includes the
1153 following libraries and programs, but the whole buildworld is
1154 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1155 kdump, procstat, rwho, rwhod, uniq.
1158 AES-NI intrinsic support has been added to gcc. The AES-NI module
1159 has been updated to use this support. A new gcc is required to build
1160 the aesni module on both i386 and amd64.
1163 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1164 Thus "device padlock_rng" and "device rdrand_rng" should be
1165 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1168 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1169 enables just the iconv* functionality and is now on by default.
1170 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1171 compatibility. Set WITHOUT_ICONV to build the old way.
1172 If you have been using WITH_ICONV before, you will very likely
1173 need to turn on WITH_LIBICONV_COMPAT.
1176 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1177 Illumos origin, including ZFS. If you have INVARIANTS in your
1178 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1180 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1181 locks if WITNESS option was set. Because that generated a lot of
1182 witness(9) reports and all of them were believed to be false
1183 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1184 can be used to achieve the previous behavior.
1187 Timer values in IPv6 data structures now use time_uptime instead
1188 of time_second. Although this is not a user-visible functional
1189 change, userland utilities which directly use them---ndp(8),
1190 rtadvd(8), and rtsold(8) in the base system---need to be updated
1191 to r253970 or later.
1194 find -delete can now delete the pathnames given as arguments,
1195 instead of only files found below them or if the pathname did
1196 not contain any slashes. Formerly, the following error message
1199 find: -delete: <path>: relative path potentially not safe
1201 Deleting the pathnames given as arguments can be prevented
1202 without error messages using -mindepth 1 or by changing
1203 directory and passing "." as argument to find. This works in the
1204 old as well as the new version of find.
1207 Behavior of devfs rules path matching has been changed.
1208 Pattern is now always matched against fully qualified devfs
1209 path and slash characters must be explicitly matched by
1210 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1211 subdirectories must be reviewed.
1214 The default ARM ABI has changed to the ARM EABI. The old ABI is
1215 incompatible with the ARM EABI and all programs and modules will
1216 need to be rebuilt to work with a new kernel.
1218 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1220 NOTE: Support for the old ABI will be removed in the future and
1221 users are advised to upgrade.
1224 pkg_install has been disconnected from the build if you really need it
1225 you should add WITH_PKGTOOLS in your src.conf(5).
1228 Most of network statistics structures were changed to be able
1229 keep 64-bits counters. Thus all tools, that work with networking
1230 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1233 Fix a bug that allowed a tracing process (e.g. gdb) to write
1234 to a memory-mapped file in the traced process's address space
1235 even if neither the traced process nor the tracing process had
1236 write access to that file.
1239 CVS has been removed from the base system. An exact copy
1240 of the code is available from the devel/cvs port.
1243 Some people report the following error after the switch to bmake:
1245 make: illegal option -- J
1246 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1248 *** [buildworld] Error code 2
1250 this likely due to an old instance of make in
1251 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1252 which src/Makefile will use that blindly, if it exists, so if
1253 you see the above error:
1255 rm -rf `make -V MAKEPATH`
1260 Use bmake by default.
1261 Whereas before one could choose to build with bmake via
1262 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1263 make. The goal is to remove these knobs for 10-RELEASE.
1265 It is worth noting that bmake (like gmake) treats the command
1266 line as the unit of failure, rather than statements within the
1267 command line. Thus '(cd some/where && dosomething)' is safer
1268 than 'cd some/where; dosomething'. The '()' allows consistent
1269 behavior in parallel build.
1272 Fix a bug that allows NFS clients to issue READDIR on files.
1275 The WITHOUT_IDEA option has been removed because
1276 the IDEA patent expired.
1279 The sysctl which controls TRIM support under ZFS has been renamed
1280 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1284 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1285 rather than creating it's own in the temporary directory in
1286 order allow access to bootstrapped versions of tools such as
1287 install and mtree. When upgrading from version of FreeBSD where
1288 the install command does not support -l, you will need to
1289 install a new mergemaster command if mergemaster -p is required.
1290 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1294 Legacy ATA stack, disabled and replaced by new CAM-based one since
1295 FreeBSD 9.0, completely removed from the sources. Kernel modules
1296 atadisk and atapi*, user-level tools atacontrol and burncd are
1297 removed. Kernel option `options ATA_CAM` is now permanently enabled
1301 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1302 and socketpair(2). Software, in particular Kerberos, may
1303 automatically detect and use these during building. The resulting
1304 binaries will not work on older kernels.
1307 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1308 information, see the respective 20130304 entry).
1311 Recent commits to callout(9) changed the size of struct callout,
1312 so the KBI is probably heavily disturbed. Also, some functions
1313 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1314 by macros. Every kernel module using it won't load, so rebuild
1317 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1318 but does not initialize by default (because of the new CTL_DISABLE
1319 option) to save memory. To re-enable it, remove the CTL_DISABLE
1320 option from the kernel config file or set kern.cam.ctl.disable=0
1321 in /boot/loader.conf.
1324 The ctl device has been disabled in GENERIC for i386 and amd64.
1325 This was done due to the extra memory being allocated at system
1326 initialisation time by the ctl driver which was only used if
1327 a CAM target device was created. This makes a FreeBSD system
1328 unusable on 128MB or less of RAM.
1331 A new compression method (lz4) has been merged to -HEAD. Please
1332 refer to zpool-features(7) for more information.
1334 Please refer to the "ZFS notes" section of this file for information
1335 on upgrading boot ZFS pools.
1338 A BSD-licensed patch(1) variant has been added and is installed
1339 as bsdpatch, being the GNU version the default patch.
1340 To inverse the logic and use the BSD-licensed one as default,
1341 while having the GNU version installed as gnupatch, rebuild
1342 and install world with the WITH_BSD_PATCH knob set.
1345 Due to the use of the new -l option to install(1) during build
1346 and install, you must take care not to directly set the INSTALL
1347 make variable in your /etc/make.conf, /etc/src.conf, or on the
1348 command line. If you wish to use the -C flag for all installs
1349 you may be able to add INSTALL+=-C to /etc/make.conf or
1353 The install(1) option -M has changed meaning and now takes an
1354 argument that is a file or path to append logs to. In the
1355 unlikely event that -M was the last option on the command line
1356 and the command line contained at least two files and a target
1357 directory the first file will have logs appended to it. The -M
1358 option served little practical purpose in the last decade so its
1359 use is expected to be extremely rare.
1362 After switching to Clang as the default compiler some users of ZFS
1363 on i386 systems started to experience stack overflow kernel panics.
1364 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1367 GEOM_LABEL now mangles label names read from file system metadata.
1368 Mangling affect labels containing spaces, non-printable characters,
1369 '%' or '"'. Device names in /etc/fstab and other places may need to
1373 By default, only the 10 most recent kernel dumps will be saved. To
1374 restore the previous behaviour (no limit on the number of kernel dumps
1375 stored in the dump directory) add the following line to /etc/rc.conf:
1380 With the addition of auditdistd(8), a new auditdistd user is now
1381 required during installworld. "mergemaster -p" can be used to
1382 add the user prior to installworld, as documented in the handbook.
1385 The sin6_scope_id member variable in struct sockaddr_in6 is now
1386 filled by the kernel before passing the structure to the userland via
1387 sysctl or routing socket. This means the KAME-specific embedded scope
1388 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1389 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1390 __FreeBSD_version is bumped to 1000025.
1393 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1394 This means that the world and kernel will be compiled with clang
1395 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1396 and /usr/bin/cpp. To disable this behavior and revert to building
1397 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1398 of current may need to bootstrap WITHOUT_CLANG first if the clang
1399 build fails (its compatibility window doesn't extend to the 9 stable
1403 The IPFIREWALL_FORWARD kernel option has been removed. Its
1404 functionality now turned on by default.
1407 The ZERO_COPY_SOCKET kernel option has been removed and
1408 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1409 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1410 mechanism which is not safe and may result in kernel crashes.
1411 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1412 driver supports disposeable external page sized mbuf storage.
1413 Proper replacements for both zero-copy mechanisms are under
1414 consideration and will eventually lead to complete removal
1415 of the two kernel options.
1418 The IPv4 network stack has been converted to network byte
1419 order. The following modules need to be recompiled together
1420 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1421 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1424 Support for non-MPSAFE filesystems was removed from VFS. The
1425 VFS_VERSION was bumped, all filesystem modules shall be
1429 All the non-MPSAFE filesystems have been disconnected from
1430 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1431 portalfs, smbfs, xfs.
1434 The interface cloning API and ABI has changed. The following
1435 modules need to be recompiled together with kernel:
1436 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1437 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1438 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1441 The sdhci driver was split in two parts: sdhci (generic SD Host
1442 Controller logic) and sdhci_pci (actual hardware driver).
1443 No kernel config modifications are required, but if you
1444 load sdhc as a module you must switch to sdhci_pci instead.
1447 Import the FUSE kernel and userland support into base system.
1450 The GNU sort(1) program has been removed since the BSD-licensed
1451 sort(1) has been the default for quite some time and no serious
1452 problems have been reported. The corresponding WITH_GNU_SORT
1456 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1457 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1461 The net80211(4) ABI has been changed to allow for improved driver
1462 PS-POLL and power-save support. All wireless drivers need to be
1463 recompiled to work with the new kernel.
1466 The random(4) support for the VIA hardware random number
1467 generator (`PADLOCK') is no longer enabled unconditionally.
1468 Add the padlock_rng device in the custom kernel config if
1469 needed. The GENERIC kernels on i386 and amd64 do include the
1470 device, so the change only affects the custom kernel
1474 The pf(4) packet filter ABI has been changed. pfctl(8) and
1475 snmp_pf module need to be recompiled to work with new kernel.
1478 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1479 to -HEAD. Pools that have empty_bpobj in active state can not be
1480 imported read-write with ZFS implementations that do not support
1481 this feature. For more information read the zpool-features(5)
1485 The sparc64 ZFS loader has been changed to no longer try to auto-
1486 detect ZFS providers based on diskN aliases but now requires these
1487 to be explicitly listed in the OFW boot-device environment variable.
1490 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1491 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1492 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1495 The following sysctls and tunables have been renamed for consistency
1496 with other variables:
1497 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1498 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1501 The sort utility has been replaced with BSD sort. For now, GNU sort
1502 is also available as "gnusort" or the default can be set back to
1503 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1504 installed as "bsdsort".
1507 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1508 Starting with this version the old system of ZFS pool versioning
1509 is superseded by "feature flags". This concept enables forward
1510 compatibility against certain future changes in functionality of ZFS
1511 pools. The first read-only compatible "feature flag" for ZFS pools
1512 is named "com.delphix:async_destroy". For more information
1513 read the new zpool-features(5) manual page.
1514 Please refer to the "ZFS notes" section of this file for information
1515 on upgrading boot ZFS pools.
1518 The malloc(3) implementation embedded in libc now uses sources imported
1519 as contrib/jemalloc. The most disruptive API change is to
1520 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1521 delete it prior to installworld, and optionally re-create it using the
1522 new format after rebooting. See malloc.conf(5) for details
1523 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1527 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1528 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1529 now spelled mips. This is to aid compatibility with third-party
1530 software that expects this naming scheme in uname(3). Little-endian
1531 settings are unchanged. If you are updating a big-endian mips64 machine
1532 from before this change, you may need to set MACHINE_ARCH=mips64 in
1533 your environment before the new build system will recognize your machine.
1536 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1540 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1541 nullfs(5) did not pass through all behaviours to the underlying layer,
1542 as a result if we bound to a socket on the lower layer we could connect
1543 only to the lower path; if we bound to the upper layer we could connect
1544 only to the upper path. The new behavior is one can connect to both the
1545 lower and the upper paths regardless what layer path one binds to.
1548 The getifaddrs upgrade path broken with 20111215 has been restored.
1549 If you have upgraded in between 20111215 and 20120209 you need to
1550 recompile libc again with your kernel. You still need to recompile
1551 world to be able to configure CARP but this restriction already
1552 comes from 20111215.
1555 The set_rcvar() function has been removed from /etc/rc.subr. All
1556 base and ports rc.d scripts have been updated, so if you have a
1557 port installed with a script in /usr/local/etc/rc.d you can either
1558 hand-edit the rcvar= line, or reinstall the port.
1560 An easy way to handle the mass-update of /etc/rc.d:
1561 rm /etc/rc.d/* && mergemaster -i
1564 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1565 on the current CPU and prevents other threads from running.
1566 This behavior can be reverted using the kern.stop_scheduler_on_panic
1568 The new behavior can be incompatible with kern.sync_on_panic.
1571 The carp(4) facility has been changed significantly. Configuration
1572 of the CARP protocol via ifconfig(8) has changed, as well as format
1573 of CARP events submitted to devd(8) has changed. See manual pages
1574 for more information. The arpbalance feature of carp(4) is currently
1575 not supported anymore.
1577 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1578 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1579 need to be recompiled.
1582 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1586 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1587 explicitely support non-MPSAFE filesystems.
1588 It is on by default for all supported platform at this present
1592 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1593 i386 and pc98 GENERIC kernel configuration files.
1596 sysinstall has been removed
1599 The stable/9 branch created in subversion. This corresponds to the
1600 RELENG_9 branch in CVS.
1606 Avoid using make -j when upgrading. While generally safe, there are
1607 sometimes problems using -j to upgrade. If your upgrade fails with
1608 -j, please try again without -j. From time to time in the past there
1609 have been problems using -j with buildworld and/or installworld. This
1610 is especially true when upgrading between "distant" versions (eg one
1611 that cross a major release boundary or several minor releases, or when
1612 several months have passed on the -current branch).
1614 Sometimes, obscure build problems are the result of environment
1615 poisoning. This can happen because the make utility reads its
1616 environment when searching for values for global variables. To run
1617 your build attempts in an "environmental clean room", prefix all make
1618 commands with 'env -i '. See the env(1) manual page for more details.
1620 When upgrading from one major version to another it is generally best
1621 to upgrade to the latest code in the currently installed branch first,
1622 then do an upgrade to the new branch. This is the best-tested upgrade
1623 path, and has the highest probability of being successful. Please try
1624 this approach before reporting problems with a major version upgrade.
1626 When upgrading a live system, having a root shell around before
1627 installing anything can help undo problems. Not having a root shell
1628 around can lead to problems if pam has changed too much from your
1629 starting point to allow continued authentication after the upgrade.
1631 This file should be read as a log of events. When a later event changes
1632 information of a prior event, the prior event should not be deleted.
1633 Instead, a pointer to the entry with the new information should be
1634 placed in the old entry. Readers of this file should also sanity check
1635 older entries before relying on them blindly. Authors of new entries
1636 should write them with this in mind.
1640 When upgrading the boot ZFS pool to a new version, always follow
1643 1.) recompile and reinstall the ZFS boot loader and boot block
1644 (this is part of "make buildworld" and "make installworld")
1646 2.) update the ZFS boot block on your boot drive
1648 The following example updates the ZFS boot block on the first
1649 partition (freebsd-boot) of a GPT partitioned drive ada0:
1650 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1652 Non-boot pools do not need these updates.
1656 If you are updating from a prior version of FreeBSD (even one just
1657 a few days old), you should follow this procedure. It is the most
1658 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1660 make kernel-toolchain
1661 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1662 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1664 To test a kernel once
1665 ---------------------
1666 If you just want to boot a kernel once (because you are not sure
1667 if it works, or if you want to boot a known bad kernel to provide
1668 debugging information) run
1669 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1670 nextboot -k testkernel
1672 To just build a kernel when you know that it won't mess you up
1673 --------------------------------------------------------------
1674 This assumes you are already running a CURRENT system. Replace
1675 ${arch} with the architecture of your machine (e.g. "i386",
1676 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1678 cd src/sys/${arch}/conf
1679 config KERNEL_NAME_HERE
1680 cd ../compile/KERNEL_NAME_HERE
1685 If this fails, go to the "To build a kernel" section.
1687 To rebuild everything and install it on the current system.
1688 -----------------------------------------------------------
1689 # Note: sometimes if you are running current you gotta do more than
1690 # is listed here if you are upgrading from a really old current.
1692 <make sure you have good level 0 dumps>
1694 make kernel KERNCONF=YOUR_KERNEL_HERE
1696 <reboot in single user> [3]
1703 To cross-install current onto a separate partition
1704 --------------------------------------------------
1705 # In this approach we use a separate partition to hold
1706 # current's root, 'usr', and 'var' directories. A partition
1707 # holding "/", "/usr" and "/var" should be about 2GB in
1710 <make sure you have good level 0 dumps>
1713 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1714 <maybe newfs current's root partition>
1715 <mount current's root partition on directory ${CURRENT_ROOT}>
1716 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1717 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1718 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1719 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1720 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1721 <reboot into current>
1722 <do a "native" rebuild/install as described in the previous section>
1723 <maybe install compatibility libraries from ports/misc/compat*>
1727 To upgrade in-place from stable to current
1728 ----------------------------------------------
1729 <make sure you have good level 0 dumps>
1731 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1733 <reboot in single user> [3]
1740 Make sure that you've read the UPDATING file to understand the
1741 tweaks to various things you need. At this point in the life
1742 cycle of current, things change often and you are on your own
1743 to cope. The defaults can also change, so please read ALL of
1744 the UPDATING entries.
1746 Also, if you are tracking -current, you must be subscribed to
1747 freebsd-current@freebsd.org. Make sure that before you update
1748 your sources that you have read and understood all the recent
1749 messages there. If in doubt, please track -stable which has
1750 much fewer pitfalls.
1752 [1] If you have third party modules, such as vmware, you
1753 should disable them at this point so they don't crash your
1756 [3] From the bootblocks, boot -s, and then do
1761 adjkerntz -i # if CMOS is wall time
1762 Also, when doing a major release upgrade, it is required that
1763 you boot into single user mode to do the installworld.
1765 [4] Note: This step is non-optional. Failure to do this step
1766 can result in a significant reduction in the functionality of the
1767 system. Attempting to do it by hand is not recommended and those
1768 that pursue this avenue should read this file carefully, as well
1769 as the archives of freebsd-current and freebsd-hackers mailing lists
1770 for potential gotchas. The -U option is also useful to consider.
1771 See mergemaster(8) for more information.
1773 [5] Usually this step is a noop. However, from time to time
1774 you may need to do this if you get unknown user in the following
1775 step. It never hurts to do it all the time. You may need to
1776 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1777 install) after the buildworld before this step if you last updated
1778 from current before 20130425 or from -stable before 20130430.
1780 [6] This only deletes old files and directories. Old libraries
1781 can be deleted by "make delete-old-libs", but you have to make
1782 sure that no program is using those libraries anymore.
1784 [8] In order to have a kernel that can run the 4.x binaries needed to
1785 do an installworld, you must include the COMPAT_FREEBSD4 option in
1786 your kernel. Failure to do so may leave you with a system that is
1787 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1788 required to run the 5.x binaries on more recent kernels. And so on
1789 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1791 Make sure that you merge any new devices from GENERIC since the
1792 last time you updated your kernel config file.
1794 [9] When checking out sources, you must include the -P flag to have
1795 cvs prune empty directories.
1797 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1798 "?=" instead of the "=" assignment operator, so that buildworld can
1799 override the CPUTYPE if it needs to.
1801 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1802 not on the command line, or in /etc/make.conf. buildworld will
1803 warn if it is improperly defined.
1806 This file contains a list, in reverse chronological order, of major
1807 breakages in tracking -current. It is not guaranteed to be a complete
1808 list of such breakages, and only contains entries since September 23, 2011.
1809 If you need to see UPDATING entries from before that date, you will need
1810 to fetch an UPDATING file from an older FreeBSD release.
1812 Copyright information:
1814 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1816 Redistribution, publication, translation and use, with or without
1817 modification, in full or in part, in any form or format of this
1818 document are permitted without further permission from the author.
1820 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1821 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1822 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1823 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1824 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1825 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1826 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1827 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1828 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1829 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1830 POSSIBILITY OF SUCH DAMAGE.
1832 Contact Warner Losh if you have any questions about your use of