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 20180814 p2 FreeBSD-SA-18:08.tcp [revised]
22 FreeBSD-SA-18:11.hostapd
24 Revise manual pages. [SA-18:08.tcp]
26 Fix L1 Terminal Fault (L1TF) kernel information disclosure.
29 Fix resource exhaustion in IP fragment reassembly. [SA-18:10.ip]
31 Fix unauthenticated EAPOL-Key decryption vulnerability.
34 20180806 p1 FreeBSD-SA-18:08.tcp
36 Fix resource exhaustion in TCP reassembly.
42 The tz database (tzdb) has been updated to 2018e. This version more
43 correctly models time stamps in time zones with negative DST such as
44 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
45 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
46 time zone abbreviations and the tm_isdst flag.
49 The use of RSS hash from the network card aka flowid has been
50 disabled by default for lagg(4) as it's currently incompatible with
51 the lacp and loadbalance protocols.
53 This can be re-enabled by setting the following in loader.conf:
54 net.link.lagg.default_use_flowid="1"
57 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
58 6.0.0. Please see the 20141231 entry below for information about
59 prerequisites and upgrading, if you are not already using clang 3.5.0
63 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
64 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
65 to WITH/OUT_LOADER_GELI.
68 The geli password typed at boot is now hidden. To restore the previous
69 behavior, see geli(8) for configuration options.
71 The SW_WATCHDOG option is no longer necessary to enable the
72 hardclock-based software watchdog if no hardware watchdog is
73 configured. As before, SW_WATCHDOG will cause the software
74 watchdog to be enabled even if a hardware watchdog is configured.
77 lint(1) binaries and library are no longer built by default. To
78 enable building them, define WITH_LINT in src.conf. If you are using
79 a FreeBSD 12 or later system to build 11-stable, you may need to
80 install a lint(1) binary to use WITH_LINT.
83 When building multiple kernels using KERNCONF, non-existent KERNCONF
84 files will produce an error and buildkernel will fail. Previously
85 missing KERNCONF files silently failed giving no indication as to
86 why, only to subsequently discover during installkernel that the
87 desired kernel was never built in the first place.
90 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
91 Please see the 20141231 entry below for information about prerequisites
92 and upgrading, if you are not already using clang 3.5.0 or higher.
95 Since the switch to GPT disk labels, fsck for UFS/FFS has been
96 unable to automatically find alternate superblocks. As of r322806,
97 the information needed to find alternate superblocks has been
98 moved to the end of the area reserved for the boot block.
99 Filesystems created with a newfs of this vintage or later
100 will create the recovery information. If you have a filesystem
101 created prior to this change and wish to have a recovery block
102 created for your filesystem, you can do so by running fsck in
103 forground mode (i.e., do not use the -p or -y options). As it
104 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
105 to which you should answer yes.
108 arm64 builds now use the base system LLD 4.0.0 linker by default,
109 instead of requiring that the aarch64-binutils port or package be
110 installed. To continue using aarch64-binutils, set
111 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
114 The ctl.ko module no longer implements the iSCSI target frontend:
115 cfiscsi.ko does instead.
117 If building cfiscsi.ko as a kernel module, the module can be loaded
118 via one of the following methods:
119 - `cfiscsi_load="YES"` in loader.conf(5).
120 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
121 - ctladm(8)/ctld(8), when compiled with iSCSI support
122 (`WITH_ISCSI=yes` in src.conf(5))
124 Please see cfiscsi(4) for more details.
127 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
128 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
129 same source (previously, the dependency of mmcsd.ko on mmc.ko was
130 missing, but mmcsd.ko now will refuse to load if it is incompatible
134 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
135 use any explicitly assigned loopback address available in the jail
136 instead of using the first assigned address of the jail.
139 As of r316810 for ipfilter, keep frags is no longer assumed when
140 keep state is specified in a rule. r316810 aligns ipfilter with
141 documentation in man pages separating keep frags from keep state.
142 This allows keep state to specified without forcing keep frags
143 and allows keep frags to be specified independently of keep state.
144 To maintain previous behaviour, also specify keep frags with
145 keep state (as documented in ipf.conf.5).
148 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
149 Please see the 20141231 entry below for information about prerequisites
150 and upgrading, if you are not already using clang 3.5.0 or higher.
153 The code that provides support for ZFS .zfs/ directory functionality
154 has been reimplemented. It's not possible now to create a snapshot
155 by mkdir under .zfs/snapshot/. That should be the only user visible
159 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
160 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
161 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
162 and now NAT-T is supported by default. Security associations now use
163 the single namespace for SPI allocation, so if you use several manually
164 configured security associations with the same SPI, this configuration
168 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
169 Please see the 20141231 entry below for information about prerequisites
170 and upgrading, if you are not already using clang 3.5.0 or higher.
173 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
174 Please see the 20141231 entry below for information about prerequisites
175 and upgrading, if you are not already using clang 3.5.0 or higher.
178 The layout of the pmap structure has changed for powerpc to put the pmap
179 statistics at the front for all CPU variations. libkvm(3) and all tools
180 that link against it need to be recompiled.
183 isl(4) and cyapa(4) drivers now require a new driver,
184 chromebook_platform(4), to work properly on Chromebook-class hardware.
185 On other types of hardware the drivers may need to be configured using
186 device hints. Please see the corresponding manual pages for details.
189 Relocatable object files with the extension of .So have been renamed
190 to use an extension of .pico instead. The purpose of this change is
191 to avoid a name clash with shared libraries on case-insensitive file
192 systems. On those file systems, foo.So is the same file as foo.so.
195 The libc stub for the pipe(2) system call has been replaced with
196 a wrapper that calls the pipe2(2) system call and the pipe(2)
197 system call is now only implemented by the kernels that include
198 "options COMPAT_FREEBSD10" in their config file (this is the
199 default). Users should ensure that this option is enabled in
200 their kernel or upgrade userspace to r302092 before upgrading their
204 CAM will now strip leading spaces from SCSI disks' serial numbers.
205 This will effect users who create UFS filesystems on SCSI disks using
206 those disk's diskid device nodes. For example, if /etc/fstab
207 previously contained a line like
208 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
209 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
210 transforms like gmirror may also be affected. ZFS users should
214 The bitstring(3) API has been updated with new functionality and
215 improved performance. But it is binary-incompatible with the old API.
216 Objects built with the new headers may not be linked against objects
217 built with the old headers.
220 The brk and sbrk functions have been removed from libc on arm64.
221 Binutils from ports has been updated to not link to these
222 functions and should be updated to the latest version before
223 installing a new libc.
226 The armv6 port now defaults to hard float ABI. Limited support
227 for running both hardfloat and soft float on the same system
228 is available using the libraries installed with -DWITH_LIBSOFT.
229 This has only been tested as an upgrade path for installworld
230 and packages may fail or need manual intervention to run. New
231 packages will be needed.
233 To update an existing self-hosted armv6hf system, you must add
234 TARGET_ARCH=armv6 on the make command line for both the build
235 and the install steps.
238 Kernel modules compiled outside of a kernel build now default to
239 installing to /boot/modules instead of /boot/kernel. Many kernel
240 modules built this way (such as those in ports) already overrode
241 KMODDIR explicitly to install into /boot/modules. However,
242 manually building and installing a module from /sys/modules will
243 now install to /boot/modules instead of /boot/kernel.
246 The CAM I/O scheduler has been committed to the kernel. There should be
247 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
248 list of known rogues that claim support for this but actually corrupt
249 data is believed to be complete, be on the lookout for data
250 corruption. The known rogue list is believed to be complete:
252 o Crucial MX100, M550 drives with MU01 firmware.
253 o Micron M510 and M550 drives with MU01 firmware.
254 o Micron M500 prior to MU07 firmware
255 o Samsung 830, 840, and 850 all firmwares
256 o FCCT M500 all firmwares
258 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
259 with working NCQ TRIM. For Micron branded drives, see your sales rep for
260 updated firmware. Black listed drives will work correctly because these
261 drives work correctly so long as no NCQ TRIMs are sent to them. Given
262 this list is the same as found in Linux, it's believed there are no
263 other rogues in the market place. All other models from the above
266 To be safe, if you are at all concerned, you can quirk each of your
267 drives to prevent NCQ from being sent by setting:
268 kern.cam.ada.X.quirks="0x2"
269 in loader.conf. If the drive requires the 4k sector quirk, set the
273 The FAST_DEPEND build option has been removed and its functionality is
274 now the one true way. The old mkdep(1) style of 'make depend' has
275 been removed. See 20160311 for further details.
278 Resource range types have grown from unsigned long to uintmax_t. All
279 drivers, and anything using libdevinfo, need to be recompiled.
282 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
283 builds. It no longer runs mkdep(1) during 'make depend', and the
284 'make depend' stage can safely be skipped now as it is auto ran
285 when building 'make all' and will generate all SRCS and DPSRCS before
286 building anything else. Dependencies are gathered at compile time with
287 -MF flags kept in separate .depend files per object file. Users should
288 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
292 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
293 kernel modules. Therefore, if you load any kernel modules at boot time,
294 please install the boot loaders after you install the kernel, but before
298 make kernel KERNCONF=YOUR_KERNEL_HERE
299 make -C sys/boot install
300 <reboot in single user>
302 Then follow the usual steps, described in the General Notes section,
306 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
307 see the 20141231 entry below for information about prerequisites and
308 upgrading, if you are not already using clang 3.5.0 or higher.
311 The AIO subsystem is now a standard part of the kernel. The
312 VFS_AIO kernel option and aio.ko kernel module have been removed.
313 Due to stability concerns, asynchronous I/O requests are only
314 permitted on sockets and raw disks by default. To enable
315 asynchronous I/O requests on all file types, set the
316 vfs.aio.enable_unsafe sysctl to a non-zero value.
319 The ELF object manipulation tool objcopy is now provided by the
320 ELF Tool Chain project rather than by GNU binutils. It should be a
321 drop-in replacement, with the addition of arm64 support. The
322 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
323 to obtain the GNU version if necessary.
326 Building ZFS pools on top of zvols is prohibited by default. That
327 feature has never worked safely; it's always been prone to deadlocks.
328 Using a zvol as the backing store for a VM guest's virtual disk will
329 still work, even if the guest is using ZFS. Legacy behavior can be
330 restored by setting vfs.zfs.vol.recursive=1.
333 The NONE and HPN patches has been removed from OpenSSH. They are
334 still available in the security/openssh-portable port.
337 With the addition of ypldap(8), a new _ypldap user is now required
338 during installworld. "mergemaster -p" can be used to add the user
339 prior to installworld, as documented in the handbook.
342 The tftp loader (pxeboot) now uses the option root-path directive. As a
343 consequence it no longer looks for a pxeboot.4th file on the tftp
344 server. Instead it uses the regular /boot infrastructure as with the
348 The code to start recording plug and play data into the modules has
349 been committed. While the old tools will properly build a new kernel,
350 a number of warnings about "unknown metadata record 4" will be produced
351 for an older kldxref. To avoid such warnings, make sure to rebuild
352 the kernel toolchain (or world). Make sure that you have r292078 or
353 later when trying to build 292077 or later before rebuilding.
356 Debug data files are now built by default with 'make buildworld' and
357 installed with 'make installworld'. This facilitates debugging but
358 requires more disk space both during the build and for the installed
359 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
363 r291527 changed the internal interface between the nfsd.ko and
364 nfscommon.ko modules. As such, they must both be upgraded to-gether.
365 __FreeBSD_version has been bumped because of this.
368 Add support for unicode collation strings leads to a change of
369 order of files listed by ls(1) for example. To get back to the old
370 behaviour, set LC_COLLATE environment variable to "C".
372 Databases administrators will need to reindex their databases given
373 collation results will be different.
375 Due to a bug in install(1) it is recommended to remove the ancient
376 locales before running make installworld.
378 rm -rf /usr/share/locale/*
381 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
382 libcrypto.so.7 or libssl.so.7 must be recompiled.
385 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
386 Kernel modules isp_2400_multi and isp_2500_multi were removed and
387 should be replaced with isp_2400 and isp_2500 modules respectively.
390 The build previously allowed using 'make -n' to not recurse into
391 sub-directories while showing what commands would be executed, and
392 'make -n -n' to recursively show commands. Now 'make -n' will recurse
393 and 'make -N' will not.
396 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
397 and etcupdate will now use this file. A custom sendmail.cf is now
398 updated via this mechanism rather than via installworld. If you had
399 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
400 want to remove the exclusion or change it to "always install".
401 /etc/mail/sendmail.cf is now managed the same way regardless of
402 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
403 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
406 Compatibility shims for legacy ATA device names have been removed.
407 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
408 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
409 environment variables, /dev/ad* and /dev/ar* symbolic links.
412 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
413 Please see the 20141231 entry below for information about prerequisites
414 and upgrading, if you are not already using clang 3.5.0 or higher.
417 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
418 and renamed from .symbols to .debug. This reduces the size requirements
419 on the boot partition or file system and provides consistency with
420 userland debug files.
422 When using the supported kernel installation method the
423 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
424 as is done with /boot/kernel.
426 Developers wishing to maintain the historical behavior of installing
427 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
430 The wireless drivers had undergone changes that remove the 'parent
431 interface' from the ifconfig -l output. The rc.d network scripts
432 used to check presence of a parent interface in the list, so old
433 scripts would fail to start wireless networking. Thus, etcupdate(3)
434 or mergemaster(8) run is required after kernel update, to update your
435 rc.d scripts in /etc.
438 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
439 These configurations are now automatically interpreted as
440 'scrub fragment reassemble'.
443 Kernel-loadable modules for the random(4) device are back. To use
444 them, the kernel must have
447 options RANDOM_LOADABLE
449 kldload(8) can then be used to load random_fortuna.ko
450 or random_yarrow.ko. Please note that due to the indirect
451 function calls that the loadable modules need to provide,
452 the build-in variants will be slightly more efficient.
454 The random(4) kernel option RANDOM_DUMMY has been retired due to
455 unpopularity. It was not all that useful anyway.
458 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
459 Control over building the ELF Tool Chain tools is now provided by
460 the WITHOUT_TOOLCHAIN knob.
463 The polarity of Pulse Per Second (PPS) capture events with the
464 uart(4) driver has been corrected. Prior to this change the PPS
465 "assert" event corresponded to the trailing edge of a positive PPS
466 pulse and the "clear" event was the leading edge of the next pulse.
468 As the width of a PPS pulse in a typical GPS receiver is on the
469 order of 1 millisecond, most users will not notice any significant
470 difference with this change.
472 Anyone who has compensated for the historical polarity reversal by
473 configuring a negative offset equal to the pulse width will need to
474 remove that workaround.
477 The default group assigned to /dev/dri entries has been changed
478 from 'wheel' to 'video' with the id of '44'. If you want to have
479 access to the dri devices please add yourself to the video group
482 # pw groupmod video -m $USER
485 The menu.rc and loader.rc files will now be replaced during
486 upgrades. Please migrate local changes to menu.rc.local and
487 loader.rc.local instead.
490 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
491 strings and strip have been removed. The src.conf(5) knob
492 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
495 As ZFS requires more kernel stack pages than is the default on some
496 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
497 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
499 Please consider using 'options KSTACK_PAGES=X' where X is greater
500 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
503 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
504 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
505 default, i.e., they will not contain "::". For example, instead
506 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
507 to have a more specific match, such as different map entries for
508 IPv6:0:0 vs IPv6:0. This change requires that configuration
509 data (including maps, files, classes, custom ruleset, etc.) must
510 use the same format, so make certain such configuration data is
511 upgrading. As a very simple check search for patterns like
512 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
513 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
514 the cf option UseCompressedIPv6Addresses.
517 The default kernel entropy-processing algorithm is now
518 Fortuna, replacing Yarrow.
520 Assuming you have 'device random' in your kernel config
521 file, the configurations allow a kernel option to override
522 this default. You may choose *ONE* of:
524 options RANDOM_YARROW # Legacy /dev/random algorithm.
525 options RANDOM_DUMMY # Blocking-only driver.
527 If you have neither, you get Fortuna. For most people,
528 read no further, Fortuna will give a /dev/random that works
529 like it always used to, and the difference will be irrelevant.
531 If you remove 'device random', you get *NO* kernel-processed
532 entropy at all. This may be acceptable to folks building
533 embedded systems, but has complications. Carry on reading,
534 and it is assumed you know what you need.
536 *PLEASE* read random(4) and random(9) if you are in the
537 habit of tweaking kernel configs, and/or if you are a member
538 of the embedded community, wanting specific and not-usual
539 behaviour from your security subsystems.
541 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
542 random', you will NOT have a functioning /dev/random, and
543 many cryptographic features will not work, including SSH.
544 You may also find strange behaviour from the random(3) set
545 of library functions, in particular sranddev(3), srandomdev(3)
546 and arc4random(3). The reason for this is that the KERN_ARND
547 sysctl only returns entropy if it thinks it has some to
548 share, and with RANDOM_DUMMY or no 'device random' this
552 An additional fix for the issue described in the 20150614 sendmail
553 entry below has been been committed in revision 284717.
556 FreeBSD's old make (fmake) has been removed from the system. It is
557 available as the devel/fmake port or via pkg install fmake.
560 The fix for the issue described in the 20150614 sendmail entry
561 below has been been committed in revision 284436. The work
562 around described in that entry is no longer needed unless the
563 default setting is overridden by a confDH_PARAMETERS configuration
564 setting of '5' or pointing to a 512 bit DH parameter file.
567 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
568 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
569 and devel/kyua to version 0.20+ and adjust any calling code to work
570 with Kyuafile and kyua.
573 The import of openssl to address the FreeBSD-SA-15:10.openssl
574 security advisory includes a change which rejects handshakes
575 with DH parameters below 768 bits. sendmail releases prior
576 to 8.15.2 (not yet released), defaulted to a 512 bit
577 DH parameter setting for client connections. To work around
578 this interoperability, sendmail can be configured to use a
579 2048 bit DH parameter by:
581 1. Edit /etc/mail/`hostname`.mc
582 2. If a setting for confDH_PARAMETERS does not exist or
583 exists and is set to a string beginning with '5',
585 3. If a setting for confDH_PARAMETERS exists and is set to
586 a file path, create a new file with:
587 openssl dhparam -out /path/to/file 2048
588 4. Rebuild the .cf file:
589 cd /etc/mail/; make; make install
591 cd /etc/mail/; make restart
593 A sendmail patch is coming, at which time this file will be
597 Generation of legacy formatted entries have been disabled by default
598 in pwd_mkdb(8), as all base system consumers of the legacy formatted
599 entries were converted to use the new format by default when the new,
600 machine independent format have been added and supported since FreeBSD
603 Please see the pwd_mkdb(8) manual page for further details.
606 Clang and llvm have been upgraded to 3.6.1 release. Please see the
607 20141231 entry below for information about prerequisites and upgrading,
608 if you are not already using 3.5.0 or higher.
611 TI platform code switched to using vendor DTS files and this update
612 may break existing systems running on Beaglebone, Beaglebone Black,
615 - dtb files should be regenerated/reinstalled. Filenames are the
616 same but content is different now
617 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
618 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
619 addressing scheme is now pin 25 on /dev/gpioc3.
620 - Pandaboard: /etc/ttys should be updated, serial console device is
621 now /dev/ttyu2, not /dev/ttyu0
624 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
625 If you need the GNU extension from groff soelim(1), install groff
626 from package: pkg install groff, or via ports: textproc/groff.
629 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
630 defined in symlink(7); previously symlinks were silently ignored.
633 The const qualifier has been removed from iconv(3) to comply with
634 POSIX. The ports tree is aware of this from r384038 onwards.
637 Libraries specified by LIBADD in Makefiles must have a corresponding
638 DPADD_<lib> variable to ensure correct dependencies. This is now
639 enforced in src.libnames.mk.
642 From legacy ata(4) driver was removed support for SATA controllers
643 supported by more functional drivers ahci(4), siis(4) and mvs(4).
644 Kernel modules ataahci and ataadaptec were removed completely,
645 replaced by ahci and mvs modules respectively.
648 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
649 the 20141231 entry below for information about prerequisites and
650 upgrading, if you are not already using 3.5.0 or higher.
653 The 32-bit PowerPC kernel has been changed to a position-independent
654 executable. This can only be booted with a version of loader(8)
655 newer than January 31, 2015, so make sure to update both world and
656 kernel before rebooting.
659 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
660 but before r278950, the RNG was not seeded properly. Immediately
661 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
662 ssh keys or openssl keys) that were generated w/ a kernel from that
663 range. This does not affect programs that directly used /dev/random
664 or /dev/urandom. All userland uses of arc4random(3) are affected.
667 The autofs(4) ABI was changed in order to restore binary compatibility
668 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
672 The powerpc64 kernel has been changed to a position-independent
673 executable. This can only be booted with a new version of loader(8),
674 so make sure to update both world and kernel before rebooting.
677 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
678 only release, no new features have been added. Please see the 20141231
679 entry below for information about prerequisites and upgrading, if you
680 are not already using 3.5.0.
683 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
684 taken from the ELF Tool Chain project rather than GNU binutils. They
685 should be drop-in replacements, with the addition of arm64 support.
686 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
687 binutils tools, if necessary. See 20150805 for updated information.
690 The default Unbound configuration now enables remote control
691 using a local socket. Users who have already enabled the
692 local_unbound service should regenerate their configuration
693 by running "service local_unbound setup" as root.
696 The GNU texinfo and GNU info pages have been removed.
697 To be able to view GNU info pages please install texinfo from ports.
700 Clang, llvm and lldb have been upgraded to 3.5.0 release.
702 As of this release, a prerequisite for building clang, llvm and lldb is
703 a C++11 capable compiler and C++11 standard library. This means that to
704 be able to successfully build the cross-tools stage of buildworld, with
705 clang as the bootstrap compiler, your system compiler or cross compiler
706 should either be clang 3.3 or later, or gcc 4.8 or later, and your
707 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
710 On any standard FreeBSD 10.x or 11.x installation, where clang and
711 libc++ are on by default (that is, on x86 or arm), this should work out
714 On 9.x installations where clang is enabled by default, e.g. on x86 and
715 powerpc, libc++ will not be enabled by default, so libc++ should be
716 built (with clang) and installed first. If both clang and libc++ are
717 missing, build clang first, then use it to build libc++.
719 On 8.x and earlier installations, upgrade to 9.x first, and then follow
720 the instructions for 9.x above.
722 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
723 default, and do not build clang.
725 Many embedded systems are resource constrained, and will not be able to
726 build clang in a reasonable time, or in some cases at all. In those
727 cases, cross building bootable systems on amd64 is a workaround.
729 This new version of clang introduces a number of new warnings, of which
730 the following are most likely to appear:
734 This warns in two cases, for both C and C++:
735 * When the code is trying to take the absolute value of an unsigned
736 quantity, which is effectively a no-op, and almost never what was
737 intended. The code should be fixed, if at all possible. If you are
738 sure that the unsigned quantity can be safely cast to signed, without
739 loss of information or undefined behavior, you can add an explicit
740 cast, or disable the warning.
742 * When the code is trying to take an absolute value, but the called
743 abs() variant is for the wrong type, which can lead to truncation.
744 If you want to disable the warning instead of fixing the code, please
745 make sure that truncation will not occur, or it might lead to unwanted
748 -Wtautological-undefined-compare and
749 -Wundefined-bool-conversion
751 These warn when C++ code is trying to compare 'this' against NULL, while
752 'this' should never be NULL in well-defined C++ code. However, there is
753 some legacy (pre C++11) code out there, which actively abuses this
754 feature, which was less strictly defined in previous C++ versions.
756 Squid and openjdk do this, for example. The warning can be turned off
757 for C++98 and earlier, but compiling the code in C++11 mode might result
758 in unexpected behavior; for example, the parts of the program that are
759 unreachable could be optimized away.
762 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
763 kernel sources have been removed. The .h files remain, since some
764 utilities include them. This will need to be fixed later.
765 If "mount -t oldnfs ..." is attempted, it will fail.
766 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
767 the utilities will report errors.
770 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
771 directories to top level SUBDIR variable when their parent
772 directory is included in LOCAL_DIRS. Users with build systems with
773 such hierarchies and without SUBDIR entries in the parent
774 directory Makefiles should add them or add the directories to
778 faith(4) and faithd(8) have been removed from the base system. Faith
779 has been obsolete for a very long time.
782 vt(4), the new console driver, is enabled by default. It brings
783 support for Unicode and double-width characters, as well as
784 support for UEFI and integration with the KMS kernel video
787 You may need to update your console settings in /etc/rc.conf,
788 most probably the keymap. During boot, /etc/rc.d/syscons will
789 indicate what you need to do.
791 vt(4) still has issues and lacks some features compared to
792 syscons(4). See the wiki for up-to-date information:
793 https://wiki.freebsd.org/Newcons
795 If you want to keep using syscons(4), you can do so by adding
796 the following line to /boot/loader.conf:
800 pjdfstest has been integrated into kyua as an opt-in test suite.
801 Please see share/doc/pjdfstest/README for more details on how to
805 gperf has been removed from the base system for architectures
806 that use clang. Ports that require gperf will obtain it from the
810 pjdfstest has been moved from tools/regression/pjdfstest to
814 At svn r271982, The default linux compat kernel ABI has been adjusted
815 to 2.6.18 in support of the linux-c6 compat ports infrastructure
816 update. If you wish to continue using the linux-f10 compat ports,
817 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
818 encouraged to update their linux-compat packages to linux-c6 during
819 their next update cycle.
822 The ofwfb driver, used to provide a graphics console on PowerPC when
823 using vt(4), no longer allows mmap() of all physical memory. This
824 will prevent Xorg on PowerPC with some ATI graphics cards from
825 initializing properly unless x11-servers/xorg-server is updated to
829 The xdev targets have been converted to using TARGET and
830 TARGET_ARCH instead of XDEV and XDEV_ARCH.
833 The default unbound configuration has been modified to address
834 issues with reverse lookups on networks that use private
835 address ranges. If you use the local_unbound service, run
836 "service local_unbound setup" as root to regenerate your
837 configuration, then "service local_unbound reload" to load the
841 The GNU texinfo and GNU info pages are not built and installed
842 anymore, WITH_INFO knob has been added to allow to built and install
844 UPDATE: see 20150102 entry on texinfo's removal
847 The GNU readline library is now an INTERNALLIB - that is, it is
848 statically linked into consumers (GDB and variants) in the base
849 system, and the shared library is no longer installed. The
850 devel/readline port is available for third party software that
854 The Itanium architecture (ia64) has been removed from the list of
855 known architectures. This is the first step in the removal of the
859 Commit r268115 has added NFSv4.1 server support, merged from
860 projects/nfsv4.1-server. Since this includes changes to the
861 internal interfaces between the NFS related modules, a full
862 build of the kernel and modules will be necessary.
863 __FreeBSD_version has been bumped.
866 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
867 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
868 which differs from the behaviour controlled by this knob.)
871 Maximal length of the serial number in CTL was increased from 16 to
872 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
873 and ctld, need to be rebuilt to work with a new kernel.
876 The libatf-c and libatf-c++ major versions were downgraded to 0 and
877 1 respectively to match the upstream numbers. They were out of
878 sync because, when they were originally added to FreeBSD, the
879 upstream versions were not respected. These libraries are private
880 and not yet built by default, so renumbering them should be a
881 non-issue. However, unclean source trees will yield broken test
882 programs once the operator executes "make delete-old-libs" after a
885 Additionally, the atf-sh binary was made private by moving it into
886 /usr/libexec/. Already-built shell test programs will keep the
887 path to the old binary so they will break after "make delete-old"
890 If you are using WITH_TESTS=yes (not the default), wipe the object
891 tree and rebuild from scratch to prevent spurious test failures.
892 This is only needed once: the misnumbered libraries and misplaced
893 binaries have been added to OptionalObsoleteFiles.inc so they will
894 be removed during a clean upgrade.
897 Clang and llvm have been upgraded to 3.4.1 release.
900 We bogusly installed src.opts.mk in /usr/share/mk. This file should
901 be removed to avoid issues in the future (and has been added to
905 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
906 past, it affected all builds that used the bsd.*.mk files. The old
907 behavior was a bug, but people may have relied upon it. To get this
908 behavior back, you can .include /etc/src.conf from /etc/make.conf
909 (which is still global and isn't changed). This also changes the
910 behavior of incremental builds inside the tree of individual
911 directories. Set MAKESYSPATH to ".../share/mk" to do that.
912 Although this has survived make universe and some upgrade scenarios,
913 other upgrade scenarios may have broken. At least one form of
914 temporary breakage was fixed with MAKESYSPATH settings for buildworld
915 as well... In cases where MAKESYSPATH isn't working with this
916 setting, you'll need to set it to the full path to your tree.
918 One side effect of all this cleaning up is that bsd.compiler.mk
919 is no longer implicitly included by bsd.own.mk. If you wish to
920 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
924 The lindev device has been removed since /dev/full has been made a
925 standard device. __FreeBSD_version has been bumped.
928 The knob WITHOUT_VI was added to the base system, which controls
929 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
930 in order to reorder files share/termcap and didn't build ex(1) as a
931 build tool, so building/installing with WITH_VI is highly advised for
932 build hosts for older releases.
934 This issue has been fixed in stable/9 and stable/10 in r277022 and
935 r276991, respectively.
938 The YES_HESIOD knob has been removed. It has been obsolete for
939 a decade. Please move to using WITH_HESIOD instead or your builds
940 will silently lack HESIOD.
943 The uart(4) driver has been changed with respect to its handling
944 of the low-level console. Previously the uart(4) driver prevented
945 any process from changing the baudrate or the CLOCAL and HUPCL
946 control flags. By removing the restrictions, operators can make
947 changes to the serial console port without having to reboot.
948 However, when getty(8) is started on the serial device that is
949 associated with the low-level console, a misconfigured terminal
950 line in /etc/ttys will now have a real impact.
951 Before upgrading the kernel, make sure that /etc/ttys has the
952 serial console device configured as 3wire without baudrate to
953 preserve the previous behaviour. E.g:
954 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
957 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
958 to improve performance. To re-enable it, if needed, run rpcbind
959 with command line option -W.
962 Switched back to the GPL dtc compiler due to updates in the upstream
963 dts files not being supported by the BSDL dtc compiler. You will need
964 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
965 may result while building dtb files during a kernel build if you fail
966 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
969 Clang and llvm have been upgraded to 3.4 release.
972 The nve(4) driver has been removed. Please use the nfe(4) driver
973 for NVIDIA nForce MCP Ethernet adapters instead.
976 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
977 This could cause certain C++ applications using shared libraries built
978 against the previous version of libc++ to crash. The incompatibility
979 has now been fixed, but any C++ applications or shared libraries built
980 between r261283 and r261801 should be recompiled.
983 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
984 capability mode support. Please note that enabling the feature in
985 kernel is still highly recommended.
988 OpenSSH is now built with sandbox support, and will use sandbox as
989 the default privilege separation method. This requires Capsicum
990 capability mode support in kernel.
993 The libelf and libdwarf libraries have been updated to newer
994 versions from upstream. Shared library version numbers for
995 these two libraries were bumped. Any ports or binaries
996 requiring these two libraries should be recompiled.
997 __FreeBSD_version is bumped to 1100006.
1000 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1001 instead of providing an explicit one, this would prevent such
1002 Makefile from providing its own Kyuafile in the future during
1003 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1004 intervention is needed to clean an objdir if you use NO_CLEAN:
1005 # find /usr/obj -name Kyuafile | xargs rm -f
1008 The behavior of gss_pseudo_random() for the krb5 mechanism
1009 has changed, for applications requesting a longer random string
1010 than produced by the underlying enctype's pseudo-random() function.
1011 In particular, the random string produced from a session key of
1012 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1013 be different at the 17th octet and later, after this change.
1014 The counter used in the PRF+ construction is now encoded as a
1015 big-endian integer in accordance with RFC 4402.
1016 __FreeBSD_version is bumped to 1100004.
1019 The WITHOUT_ATF build knob has been removed and its functionality
1020 has been subsumed into the more generic WITHOUT_TESTS. If you were
1021 using the former to disable the build of the ATF libraries, you
1022 should change your settings to use the latter.
1025 The default version of mtree is nmtree which is obtained from
1026 NetBSD. The output is generally the same, but may vary
1027 slightly. If you found you need identical output adding
1028 "-F freebsd9" to the command line should do the trick. For the
1029 time being, the old mtree is available as fmtree.
1032 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1033 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1034 1.1.4_8 and verify bsdyml not linked in, before running "make
1036 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1038 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1041 The stable/10 branch has been created in subversion from head
1045 The rc.d/jail script has been updated to support jail(8)
1046 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1047 for per-jail configuration are automatically converted to
1048 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1049 This is transparently backward compatible. See below about some
1050 incompatibilities and rc.conf(5) manual page for more details.
1052 These variables are now deprecated in favor of jail(8) configuration
1053 file. One can use "rc.d/jail config <jname>" command to generate
1054 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1055 running the jail(8) utility. The default pathname of the
1056 configuration file is /etc/jail.conf and can be specified by
1057 using $jail_conf or $jail_<jname>_conf variables.
1059 Please note that jail_devfs_ruleset accepts an integer at
1060 this moment. Please consider to rewrite the ruleset name
1064 BIND has been removed from the base system. If all you need
1065 is a local resolver, simply enable and start the local_unbound
1066 service instead. Otherwise, several versions of BIND are
1067 available in the ports tree. The dns/bind99 port is one example.
1069 With this change, nslookup(1) and dig(1) are no longer in the base
1070 system. Users should instead use host(1) and drill(1) which are
1071 in the base system. Alternatively, nslookup and dig can
1072 be obtained by installing the dns/bind-tools port.
1075 With the addition of unbound(8), a new unbound user is now
1076 required during installworld. "mergemaster -p" can be used to
1077 add the user prior to installworld, as documented in the handbook.
1080 OpenSSH is now built with DNSSEC support, and will by default
1081 silently trust signed SSHFP records. This can be controlled with
1082 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1083 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1086 The GNU Compiler Collection and C++ standard library (libstdc++)
1087 are no longer built by default on platforms where clang is the system
1088 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1089 options in src.conf.
1092 The PROCDESC kernel option is now part of the GENERIC kernel
1093 configuration and is required for the rwhod(8) to work.
1094 If you are using custom kernel configuration, you should include
1098 The API and ABI related to the Capsicum framework was modified
1099 in backward incompatible way. The userland libraries and programs
1100 have to be recompiled to work with the new kernel. This includes the
1101 following libraries and programs, but the whole buildworld is
1102 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1103 kdump, procstat, rwho, rwhod, uniq.
1106 AES-NI intrinsic support has been added to gcc. The AES-NI module
1107 has been updated to use this support. A new gcc is required to build
1108 the aesni module on both i386 and amd64.
1111 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1112 Thus "device padlock_rng" and "device rdrand_rng" should be
1113 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1116 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1117 enables just the iconv* functionality and is now on by default.
1118 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1119 compatibility. Set WITHOUT_ICONV to build the old way.
1120 If you have been using WITH_ICONV before, you will very likely
1121 need to turn on WITH_LIBICONV_COMPAT.
1124 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1125 Illumos origin, including ZFS. If you have INVARIANTS in your
1126 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1128 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1129 locks if WITNESS option was set. Because that generated a lot of
1130 witness(9) reports and all of them were believed to be false
1131 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1132 can be used to achieve the previous behavior.
1135 Timer values in IPv6 data structures now use time_uptime instead
1136 of time_second. Although this is not a user-visible functional
1137 change, userland utilities which directly use them---ndp(8),
1138 rtadvd(8), and rtsold(8) in the base system---need to be updated
1139 to r253970 or later.
1142 find -delete can now delete the pathnames given as arguments,
1143 instead of only files found below them or if the pathname did
1144 not contain any slashes. Formerly, the following error message
1147 find: -delete: <path>: relative path potentially not safe
1149 Deleting the pathnames given as arguments can be prevented
1150 without error messages using -mindepth 1 or by changing
1151 directory and passing "." as argument to find. This works in the
1152 old as well as the new version of find.
1155 Behavior of devfs rules path matching has been changed.
1156 Pattern is now always matched against fully qualified devfs
1157 path and slash characters must be explicitly matched by
1158 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1159 subdirectories must be reviewed.
1162 The default ARM ABI has changed to the ARM EABI. The old ABI is
1163 incompatible with the ARM EABI and all programs and modules will
1164 need to be rebuilt to work with a new kernel.
1166 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1168 NOTE: Support for the old ABI will be removed in the future and
1169 users are advised to upgrade.
1172 pkg_install has been disconnected from the build if you really need it
1173 you should add WITH_PKGTOOLS in your src.conf(5).
1176 Most of network statistics structures were changed to be able
1177 keep 64-bits counters. Thus all tools, that work with networking
1178 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1181 Fix a bug that allowed a tracing process (e.g. gdb) to write
1182 to a memory-mapped file in the traced process's address space
1183 even if neither the traced process nor the tracing process had
1184 write access to that file.
1187 CVS has been removed from the base system. An exact copy
1188 of the code is available from the devel/cvs port.
1191 Some people report the following error after the switch to bmake:
1193 make: illegal option -- J
1194 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1196 *** [buildworld] Error code 2
1198 this likely due to an old instance of make in
1199 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1200 which src/Makefile will use that blindly, if it exists, so if
1201 you see the above error:
1203 rm -rf `make -V MAKEPATH`
1208 Use bmake by default.
1209 Whereas before one could choose to build with bmake via
1210 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1211 make. The goal is to remove these knobs for 10-RELEASE.
1213 It is worth noting that bmake (like gmake) treats the command
1214 line as the unit of failure, rather than statements within the
1215 command line. Thus '(cd some/where && dosomething)' is safer
1216 than 'cd some/where; dosomething'. The '()' allows consistent
1217 behavior in parallel build.
1220 Fix a bug that allows NFS clients to issue READDIR on files.
1223 The WITHOUT_IDEA option has been removed because
1224 the IDEA patent expired.
1227 The sysctl which controls TRIM support under ZFS has been renamed
1228 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1232 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1233 rather than creating it's own in the temporary directory in
1234 order allow access to bootstrapped versions of tools such as
1235 install and mtree. When upgrading from version of FreeBSD where
1236 the install command does not support -l, you will need to
1237 install a new mergemaster command if mergemaster -p is required.
1238 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1242 Legacy ATA stack, disabled and replaced by new CAM-based one since
1243 FreeBSD 9.0, completely removed from the sources. Kernel modules
1244 atadisk and atapi*, user-level tools atacontrol and burncd are
1245 removed. Kernel option `options ATA_CAM` is now permanently enabled
1249 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1250 and socketpair(2). Software, in particular Kerberos, may
1251 automatically detect and use these during building. The resulting
1252 binaries will not work on older kernels.
1255 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1256 information, see the respective 20130304 entry).
1259 Recent commits to callout(9) changed the size of struct callout,
1260 so the KBI is probably heavily disturbed. Also, some functions
1261 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1262 by macros. Every kernel module using it won't load, so rebuild
1265 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1266 but does not initialize by default (because of the new CTL_DISABLE
1267 option) to save memory. To re-enable it, remove the CTL_DISABLE
1268 option from the kernel config file or set kern.cam.ctl.disable=0
1269 in /boot/loader.conf.
1272 The ctl device has been disabled in GENERIC for i386 and amd64.
1273 This was done due to the extra memory being allocated at system
1274 initialisation time by the ctl driver which was only used if
1275 a CAM target device was created. This makes a FreeBSD system
1276 unusable on 128MB or less of RAM.
1279 A new compression method (lz4) has been merged to -HEAD. Please
1280 refer to zpool-features(7) for more information.
1282 Please refer to the "ZFS notes" section of this file for information
1283 on upgrading boot ZFS pools.
1286 A BSD-licensed patch(1) variant has been added and is installed
1287 as bsdpatch, being the GNU version the default patch.
1288 To inverse the logic and use the BSD-licensed one as default,
1289 while having the GNU version installed as gnupatch, rebuild
1290 and install world with the WITH_BSD_PATCH knob set.
1293 Due to the use of the new -l option to install(1) during build
1294 and install, you must take care not to directly set the INSTALL
1295 make variable in your /etc/make.conf, /etc/src.conf, or on the
1296 command line. If you wish to use the -C flag for all installs
1297 you may be able to add INSTALL+=-C to /etc/make.conf or
1301 The install(1) option -M has changed meaning and now takes an
1302 argument that is a file or path to append logs to. In the
1303 unlikely event that -M was the last option on the command line
1304 and the command line contained at least two files and a target
1305 directory the first file will have logs appended to it. The -M
1306 option served little practical purpose in the last decade so its
1307 use is expected to be extremely rare.
1310 After switching to Clang as the default compiler some users of ZFS
1311 on i386 systems started to experience stack overflow kernel panics.
1312 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1315 GEOM_LABEL now mangles label names read from file system metadata.
1316 Mangling affect labels containing spaces, non-printable characters,
1317 '%' or '"'. Device names in /etc/fstab and other places may need to
1321 By default, only the 10 most recent kernel dumps will be saved. To
1322 restore the previous behaviour (no limit on the number of kernel dumps
1323 stored in the dump directory) add the following line to /etc/rc.conf:
1328 With the addition of auditdistd(8), a new auditdistd user is now
1329 required during installworld. "mergemaster -p" can be used to
1330 add the user prior to installworld, as documented in the handbook.
1333 The sin6_scope_id member variable in struct sockaddr_in6 is now
1334 filled by the kernel before passing the structure to the userland via
1335 sysctl or routing socket. This means the KAME-specific embedded scope
1336 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1337 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1338 __FreeBSD_version is bumped to 1000025.
1341 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1342 This means that the world and kernel will be compiled with clang
1343 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1344 and /usr/bin/cpp. To disable this behavior and revert to building
1345 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1346 of current may need to bootstrap WITHOUT_CLANG first if the clang
1347 build fails (its compatibility window doesn't extend to the 9 stable
1351 The IPFIREWALL_FORWARD kernel option has been removed. Its
1352 functionality now turned on by default.
1355 The ZERO_COPY_SOCKET kernel option has been removed and
1356 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1357 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1358 mechanism which is not safe and may result in kernel crashes.
1359 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1360 driver supports disposeable external page sized mbuf storage.
1361 Proper replacements for both zero-copy mechanisms are under
1362 consideration and will eventually lead to complete removal
1363 of the two kernel options.
1366 The IPv4 network stack has been converted to network byte
1367 order. The following modules need to be recompiled together
1368 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1369 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1372 Support for non-MPSAFE filesystems was removed from VFS. The
1373 VFS_VERSION was bumped, all filesystem modules shall be
1377 All the non-MPSAFE filesystems have been disconnected from
1378 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1379 portalfs, smbfs, xfs.
1382 The interface cloning API and ABI has changed. The following
1383 modules need to be recompiled together with kernel:
1384 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1385 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1386 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1389 The sdhci driver was split in two parts: sdhci (generic SD Host
1390 Controller logic) and sdhci_pci (actual hardware driver).
1391 No kernel config modifications are required, but if you
1392 load sdhc as a module you must switch to sdhci_pci instead.
1395 Import the FUSE kernel and userland support into base system.
1398 The GNU sort(1) program has been removed since the BSD-licensed
1399 sort(1) has been the default for quite some time and no serious
1400 problems have been reported. The corresponding WITH_GNU_SORT
1404 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1405 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1409 The net80211(4) ABI has been changed to allow for improved driver
1410 PS-POLL and power-save support. All wireless drivers need to be
1411 recompiled to work with the new kernel.
1414 The random(4) support for the VIA hardware random number
1415 generator (`PADLOCK') is no longer enabled unconditionally.
1416 Add the padlock_rng device in the custom kernel config if
1417 needed. The GENERIC kernels on i386 and amd64 do include the
1418 device, so the change only affects the custom kernel
1422 The pf(4) packet filter ABI has been changed. pfctl(8) and
1423 snmp_pf module need to be recompiled to work with new kernel.
1426 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1427 to -HEAD. Pools that have empty_bpobj in active state can not be
1428 imported read-write with ZFS implementations that do not support
1429 this feature. For more information read the zpool-features(5)
1433 The sparc64 ZFS loader has been changed to no longer try to auto-
1434 detect ZFS providers based on diskN aliases but now requires these
1435 to be explicitly listed in the OFW boot-device environment variable.
1438 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1439 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1440 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1443 The following sysctls and tunables have been renamed for consistency
1444 with other variables:
1445 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1446 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1449 The sort utility has been replaced with BSD sort. For now, GNU sort
1450 is also available as "gnusort" or the default can be set back to
1451 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1452 installed as "bsdsort".
1455 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1456 Starting with this version the old system of ZFS pool versioning
1457 is superseded by "feature flags". This concept enables forward
1458 compatibility against certain future changes in functionality of ZFS
1459 pools. The first read-only compatible "feature flag" for ZFS pools
1460 is named "com.delphix:async_destroy". For more information
1461 read the new zpool-features(5) manual page.
1462 Please refer to the "ZFS notes" section of this file for information
1463 on upgrading boot ZFS pools.
1466 The malloc(3) implementation embedded in libc now uses sources imported
1467 as contrib/jemalloc. The most disruptive API change is to
1468 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1469 delete it prior to installworld, and optionally re-create it using the
1470 new format after rebooting. See malloc.conf(5) for details
1471 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1475 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1476 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1477 now spelled mips. This is to aid compatibility with third-party
1478 software that expects this naming scheme in uname(3). Little-endian
1479 settings are unchanged. If you are updating a big-endian mips64 machine
1480 from before this change, you may need to set MACHINE_ARCH=mips64 in
1481 your environment before the new build system will recognize your machine.
1484 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1488 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1489 nullfs(5) did not pass through all behaviours to the underlying layer,
1490 as a result if we bound to a socket on the lower layer we could connect
1491 only to the lower path; if we bound to the upper layer we could connect
1492 only to the upper path. The new behavior is one can connect to both the
1493 lower and the upper paths regardless what layer path one binds to.
1496 The getifaddrs upgrade path broken with 20111215 has been restored.
1497 If you have upgraded in between 20111215 and 20120209 you need to
1498 recompile libc again with your kernel. You still need to recompile
1499 world to be able to configure CARP but this restriction already
1500 comes from 20111215.
1503 The set_rcvar() function has been removed from /etc/rc.subr. All
1504 base and ports rc.d scripts have been updated, so if you have a
1505 port installed with a script in /usr/local/etc/rc.d you can either
1506 hand-edit the rcvar= line, or reinstall the port.
1508 An easy way to handle the mass-update of /etc/rc.d:
1509 rm /etc/rc.d/* && mergemaster -i
1512 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1513 on the current CPU and prevents other threads from running.
1514 This behavior can be reverted using the kern.stop_scheduler_on_panic
1516 The new behavior can be incompatible with kern.sync_on_panic.
1519 The carp(4) facility has been changed significantly. Configuration
1520 of the CARP protocol via ifconfig(8) has changed, as well as format
1521 of CARP events submitted to devd(8) has changed. See manual pages
1522 for more information. The arpbalance feature of carp(4) is currently
1523 not supported anymore.
1525 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1526 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1527 need to be recompiled.
1530 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1534 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1535 explicitely support non-MPSAFE filesystems.
1536 It is on by default for all supported platform at this present
1540 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1541 i386 and pc98 GENERIC kernel configuration files.
1544 sysinstall has been removed
1547 The stable/9 branch created in subversion. This corresponds to the
1548 RELENG_9 branch in CVS.
1554 Avoid using make -j when upgrading. While generally safe, there are
1555 sometimes problems using -j to upgrade. If your upgrade fails with
1556 -j, please try again without -j. From time to time in the past there
1557 have been problems using -j with buildworld and/or installworld. This
1558 is especially true when upgrading between "distant" versions (eg one
1559 that cross a major release boundary or several minor releases, or when
1560 several months have passed on the -current branch).
1562 Sometimes, obscure build problems are the result of environment
1563 poisoning. This can happen because the make utility reads its
1564 environment when searching for values for global variables. To run
1565 your build attempts in an "environmental clean room", prefix all make
1566 commands with 'env -i '. See the env(1) manual page for more details.
1568 When upgrading from one major version to another it is generally best
1569 to upgrade to the latest code in the currently installed branch first,
1570 then do an upgrade to the new branch. This is the best-tested upgrade
1571 path, and has the highest probability of being successful. Please try
1572 this approach before reporting problems with a major version upgrade.
1574 When upgrading a live system, having a root shell around before
1575 installing anything can help undo problems. Not having a root shell
1576 around can lead to problems if pam has changed too much from your
1577 starting point to allow continued authentication after the upgrade.
1579 This file should be read as a log of events. When a later event changes
1580 information of a prior event, the prior event should not be deleted.
1581 Instead, a pointer to the entry with the new information should be
1582 placed in the old entry. Readers of this file should also sanity check
1583 older entries before relying on them blindly. Authors of new entries
1584 should write them with this in mind.
1588 When upgrading the boot ZFS pool to a new version, always follow
1591 1.) recompile and reinstall the ZFS boot loader and boot block
1592 (this is part of "make buildworld" and "make installworld")
1594 2.) update the ZFS boot block on your boot drive
1596 The following example updates the ZFS boot block on the first
1597 partition (freebsd-boot) of a GPT partitioned drive ada0:
1598 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1600 Non-boot pools do not need these updates.
1604 If you are updating from a prior version of FreeBSD (even one just
1605 a few days old), you should follow this procedure. It is the most
1606 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1608 make kernel-toolchain
1609 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1610 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1612 To test a kernel once
1613 ---------------------
1614 If you just want to boot a kernel once (because you are not sure
1615 if it works, or if you want to boot a known bad kernel to provide
1616 debugging information) run
1617 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1618 nextboot -k testkernel
1620 To just build a kernel when you know that it won't mess you up
1621 --------------------------------------------------------------
1622 This assumes you are already running a CURRENT system. Replace
1623 ${arch} with the architecture of your machine (e.g. "i386",
1624 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1626 cd src/sys/${arch}/conf
1627 config KERNEL_NAME_HERE
1628 cd ../compile/KERNEL_NAME_HERE
1633 If this fails, go to the "To build a kernel" section.
1635 To rebuild everything and install it on the current system.
1636 -----------------------------------------------------------
1637 # Note: sometimes if you are running current you gotta do more than
1638 # is listed here if you are upgrading from a really old current.
1640 <make sure you have good level 0 dumps>
1642 make kernel KERNCONF=YOUR_KERNEL_HERE
1644 <reboot in single user> [3]
1651 To cross-install current onto a separate partition
1652 --------------------------------------------------
1653 # In this approach we use a separate partition to hold
1654 # current's root, 'usr', and 'var' directories. A partition
1655 # holding "/", "/usr" and "/var" should be about 2GB in
1658 <make sure you have good level 0 dumps>
1661 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1662 <maybe newfs current's root partition>
1663 <mount current's root partition on directory ${CURRENT_ROOT}>
1664 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1665 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1666 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1667 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1668 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1669 <reboot into current>
1670 <do a "native" rebuild/install as described in the previous section>
1671 <maybe install compatibility libraries from ports/misc/compat*>
1675 To upgrade in-place from stable to current
1676 ----------------------------------------------
1677 <make sure you have good level 0 dumps>
1679 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1681 <reboot in single user> [3]
1688 Make sure that you've read the UPDATING file to understand the
1689 tweaks to various things you need. At this point in the life
1690 cycle of current, things change often and you are on your own
1691 to cope. The defaults can also change, so please read ALL of
1692 the UPDATING entries.
1694 Also, if you are tracking -current, you must be subscribed to
1695 freebsd-current@freebsd.org. Make sure that before you update
1696 your sources that you have read and understood all the recent
1697 messages there. If in doubt, please track -stable which has
1698 much fewer pitfalls.
1700 [1] If you have third party modules, such as vmware, you
1701 should disable them at this point so they don't crash your
1704 [3] From the bootblocks, boot -s, and then do
1709 adjkerntz -i # if CMOS is wall time
1710 Also, when doing a major release upgrade, it is required that
1711 you boot into single user mode to do the installworld.
1713 [4] Note: This step is non-optional. Failure to do this step
1714 can result in a significant reduction in the functionality of the
1715 system. Attempting to do it by hand is not recommended and those
1716 that pursue this avenue should read this file carefully, as well
1717 as the archives of freebsd-current and freebsd-hackers mailing lists
1718 for potential gotchas. The -U option is also useful to consider.
1719 See mergemaster(8) for more information.
1721 [5] Usually this step is a noop. However, from time to time
1722 you may need to do this if you get unknown user in the following
1723 step. It never hurts to do it all the time. You may need to
1724 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1725 install) after the buildworld before this step if you last updated
1726 from current before 20130425 or from -stable before 20130430.
1728 [6] This only deletes old files and directories. Old libraries
1729 can be deleted by "make delete-old-libs", but you have to make
1730 sure that no program is using those libraries anymore.
1732 [8] In order to have a kernel that can run the 4.x binaries needed to
1733 do an installworld, you must include the COMPAT_FREEBSD4 option in
1734 your kernel. Failure to do so may leave you with a system that is
1735 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1736 required to run the 5.x binaries on more recent kernels. And so on
1737 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1739 Make sure that you merge any new devices from GENERIC since the
1740 last time you updated your kernel config file.
1742 [9] When checking out sources, you must include the -P flag to have
1743 cvs prune empty directories.
1745 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1746 "?=" instead of the "=" assignment operator, so that buildworld can
1747 override the CPUTYPE if it needs to.
1749 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1750 not on the command line, or in /etc/make.conf. buildworld will
1751 warn if it is improperly defined.
1754 This file contains a list, in reverse chronological order, of major
1755 breakages in tracking -current. It is not guaranteed to be a complete
1756 list of such breakages, and only contains entries since September 23, 2011.
1757 If you need to see UPDATING entries from before that date, you will need
1758 to fetch an UPDATING file from an older FreeBSD release.
1760 Copyright information:
1762 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1764 Redistribution, publication, translation and use, with or without
1765 modification, in full or in part, in any form or format of this
1766 document are permitted without further permission from the author.
1768 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1769 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1770 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1771 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1772 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1773 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1774 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1775 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1776 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1777 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1778 POSSIBILITY OF SUCH DAMAGE.
1780 Contact Warner Losh if you have any questions about your use of