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 p13 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 p12 FreeBSD-SA-18:08.tcp
36 Fix resource exhaustion in TCP reassembly.
38 20180621 p11 FreeBSD-SA-18:07.lazyfpu
41 Fix Lazy FPU information disclosure. [SA-18:07.lazyfpu]
43 Fix TLB shootdown for Xen based guests. [EN-18:07.pmap]
45 20180508 p10 FreeBSD-SA-18:06.debugreg
47 FreeBSD-EN-18:06.tzdata
49 Fix mishandling of x86 debug exceptions. [SA-18:06.debugreg]
51 Fix multiple small kernel memory disclosures. [EN-18:05.mem]
53 Update timezone database information. [EN-18:06.tzdata]
55 20180404 p9 FreeBSD-SA-18:04.vt
56 FreeBSD-SA-18:05.ipsec
57 FreeBSD-EN-18:03.tzdata
60 Fix vt console memory disclosure. [SA-18:04.vt]
62 Fix ipsec crash or denial of service. [SA-18:05.ipsec]
64 Update timezone database information. [EN-18:03.tzdata]
66 Fix multiple small kernel memory disclosures. [EN-18:04.mem]
68 20180314 p8 FreeBSD-SA-18:03.speculative_execution
70 Add mitigations for two classes of speculative execution vulnerabilities
73 20180307 p7 FreeBSD-SA-18:01.ipsec
75 FreeBSD-EN-18:01.tzdata
78 Fix ipsec validation and use-after-free. [SA-18:01.ipsec]
80 Fix multiple vulnerabilities in ntp. [SA-18:02.ntp]
82 Update timezone database information. [EN-18:01.tzdata]
84 Update file(1) to new version with security update. [EN-18:02.file]
86 20171209 p6 FreeBSD-SA-17:12.openssl
88 Fix multiple vulnerabilities of OpenSSL.
90 20171129 p5 FreeBSD-SA-17:11.openssl
92 Fix multiple vulnerabilities of OpenSSL.
94 20171115 p4 FreeBSD-SA-17:08.ptrace
95 FreeBSD-SA-17:10.kldstat
97 Fix ptrace(2) vulnerability. [SA-17:08.ptrace]
99 Fix kldstat(2) vulnerability. [SA-17:10.kldstat]
101 20171102 p3 FreeBSD-EN-17:09.tzdata
103 Update timezone database information. [EN-17:09]
105 20171017 p2 FreeBSD-SA-17:07.wpa
107 Fix WPA2 protocol vulnerability. [SA-17:07]
109 20170810 p1 FreeBSD-SA-17:06.openssh
110 FreeBSD-EN-17:07.vnet
113 Fix OpenSSH Denial of Service vulnerability. [SA-17:06]
115 Fix VNET kernel panic with asynchronous I/O. [EN-17:07]
117 Fix pf(4) housekeeping thread causes kernel panic. [EN-17:08]
123 arm64 builds now use the base system LLD 4.0.0 linker by default,
124 instead of requiring that the aarch64-binutils port or package be
125 installed. To continue using aarch64-binutils, set
126 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
129 The ctl.ko module no longer implements the iSCSI target frontend:
130 cfiscsi.ko does instead.
132 If building cfiscsi.ko as a kernel module, the module can be loaded
133 via one of the following methods:
134 - `cfiscsi_load="YES"` in loader.conf(5).
135 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
136 - ctladm(8)/ctld(8), when compiled with iSCSI support
137 (`WITH_ISCSI=yes` in src.conf(5))
139 Please see cfiscsi(4) for more details.
142 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
143 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
144 same source (previously, the dependency of mmcsd.ko on mmc.ko was
145 missing, but mmcsd.ko now will refuse to load if it is incompatible
149 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
150 use any explicitly assigned loopback address available in the jail
151 instead of using the first assigned address of the jail.
154 As of r316810 for ipfilter, keep frags is no longer assumed when
155 keep state is specified in a rule. r316810 aligns ipfilter with
156 documentation in man pages separating keep frags from keep state.
157 This allows keep state to specified without forcing keep frags
158 and allows keep frags to be specified independently of keep state.
159 To maintain previous behaviour, also specify keep frags with
160 keep state (as documented in ipf.conf.5).
163 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
164 Please see the 20141231 entry below for information about prerequisites
165 and upgrading, if you are not already using clang 3.5.0 or higher.
168 The code that provides support for ZFS .zfs/ directory functionality
169 has been reimplemented. It's not possible now to create a snapshot
170 by mkdir under .zfs/snapshot/. That should be the only user visible
174 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
175 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
176 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
177 and now NAT-T is supported by default. Security associations now use
178 the single namespace for SPI allocation, so if you use several manually
179 configured security associations with the same SPI, this configuration
183 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
184 Please see the 20141231 entry below for information about prerequisites
185 and upgrading, if you are not already using clang 3.5.0 or higher.
188 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
189 Please see the 20141231 entry below for information about prerequisites
190 and upgrading, if you are not already using clang 3.5.0 or higher.
193 The layout of the pmap structure has changed for powerpc to put the pmap
194 statistics at the front for all CPU variations. libkvm(3) and all tools
195 that link against it need to be recompiled.
198 isl(4) and cyapa(4) drivers now require a new driver,
199 chromebook_platform(4), to work properly on Chromebook-class hardware.
200 On other types of hardware the drivers may need to be configured using
201 device hints. Please see the corresponding manual pages for details.
204 Relocatable object files with the extension of .So have been renamed
205 to use an extension of .pico instead. The purpose of this change is
206 to avoid a name clash with shared libraries on case-insensitive file
207 systems. On those file systems, foo.So is the same file as foo.so.
210 The libc stub for the pipe(2) system call has been replaced with
211 a wrapper that calls the pipe2(2) system call and the pipe(2)
212 system call is now only implemented by the kernels that include
213 "options COMPAT_FREEBSD10" in their config file (this is the
214 default). Users should ensure that this option is enabled in
215 their kernel or upgrade userspace to r302092 before upgrading their
219 CAM will now strip leading spaces from SCSI disks' serial numbers.
220 This will effect users who create UFS filesystems on SCSI disks using
221 those disk's diskid device nodes. For example, if /etc/fstab
222 previously contained a line like
223 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
224 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
225 transforms like gmirror may also be affected. ZFS users should
229 The bitstring(3) API has been updated with new functionality and
230 improved performance. But it is binary-incompatible with the old API.
231 Objects built with the new headers may not be linked against objects
232 built with the old headers.
235 The brk and sbrk functions have been removed from libc on arm64.
236 Binutils from ports has been updated to not link to these
237 functions and should be updated to the latest version before
238 installing a new libc.
241 The armv6 port now defaults to hard float ABI. Limited support
242 for running both hardfloat and soft float on the same system
243 is available using the libraries installed with -DWITH_LIBSOFT.
244 This has only been tested as an upgrade path for installworld
245 and packages may fail or need manual intervention to run. New
246 packages will be needed.
248 To update an existing self-hosted armv6hf system, you must add
249 TARGET_ARCH=armv6 on the make command line for both the build
250 and the install steps.
253 Kernel modules compiled outside of a kernel build now default to
254 installing to /boot/modules instead of /boot/kernel. Many kernel
255 modules built this way (such as those in ports) already overrode
256 KMODDIR explicitly to install into /boot/modules. However,
257 manually building and installing a module from /sys/modules will
258 now install to /boot/modules instead of /boot/kernel.
261 The CAM I/O scheduler has been committed to the kernel. There should be
262 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
263 list of known rogues that claim support for this but actually corrupt
264 data is believed to be complete, be on the lookout for data
265 corruption. The known rogue list is believed to be complete:
267 o Crucial MX100, M550 drives with MU01 firmware.
268 o Micron M510 and M550 drives with MU01 firmware.
269 o Micron M500 prior to MU07 firmware
270 o Samsung 830, 840, and 850 all firmwares
271 o FCCT M500 all firmwares
273 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
274 with working NCQ TRIM. For Micron branded drives, see your sales rep for
275 updated firmware. Black listed drives will work correctly because these
276 drives work correctly so long as no NCQ TRIMs are sent to them. Given
277 this list is the same as found in Linux, it's believed there are no
278 other rogues in the market place. All other models from the above
281 To be safe, if you are at all concerned, you can quirk each of your
282 drives to prevent NCQ from being sent by setting:
283 kern.cam.ada.X.quirks="0x2"
284 in loader.conf. If the drive requires the 4k sector quirk, set the
288 The FAST_DEPEND build option has been removed and its functionality is
289 now the one true way. The old mkdep(1) style of 'make depend' has
290 been removed. See 20160311 for further details.
293 Resource range types have grown from unsigned long to uintmax_t. All
294 drivers, and anything using libdevinfo, need to be recompiled.
297 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
298 builds. It no longer runs mkdep(1) during 'make depend', and the
299 'make depend' stage can safely be skipped now as it is auto ran
300 when building 'make all' and will generate all SRCS and DPSRCS before
301 building anything else. Dependencies are gathered at compile time with
302 -MF flags kept in separate .depend files per object file. Users should
303 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
307 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
308 kernel modules. Therefore, if you load any kernel modules at boot time,
309 please install the boot loaders after you install the kernel, but before
313 make kernel KERNCONF=YOUR_KERNEL_HERE
314 make -C sys/boot install
315 <reboot in single user>
317 Then follow the usual steps, described in the General Notes section,
321 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
322 see the 20141231 entry below for information about prerequisites and
323 upgrading, if you are not already using clang 3.5.0 or higher.
326 The AIO subsystem is now a standard part of the kernel. The
327 VFS_AIO kernel option and aio.ko kernel module have been removed.
328 Due to stability concerns, asynchronous I/O requests are only
329 permitted on sockets and raw disks by default. To enable
330 asynchronous I/O requests on all file types, set the
331 vfs.aio.enable_unsafe sysctl to a non-zero value.
334 The ELF object manipulation tool objcopy is now provided by the
335 ELF Tool Chain project rather than by GNU binutils. It should be a
336 drop-in replacement, with the addition of arm64 support. The
337 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
338 to obtain the GNU version if necessary.
341 Building ZFS pools on top of zvols is prohibited by default. That
342 feature has never worked safely; it's always been prone to deadlocks.
343 Using a zvol as the backing store for a VM guest's virtual disk will
344 still work, even if the guest is using ZFS. Legacy behavior can be
345 restored by setting vfs.zfs.vol.recursive=1.
348 The NONE and HPN patches has been removed from OpenSSH. They are
349 still available in the security/openssh-portable port.
352 With the addition of ypldap(8), a new _ypldap user is now required
353 during installworld. "mergemaster -p" can be used to add the user
354 prior to installworld, as documented in the handbook.
357 The tftp loader (pxeboot) now uses the option root-path directive. As a
358 consequence it no longer looks for a pxeboot.4th file on the tftp
359 server. Instead it uses the regular /boot infrastructure as with the
363 The code to start recording plug and play data into the modules has
364 been committed. While the old tools will properly build a new kernel,
365 a number of warnings about "unknown metadata record 4" will be produced
366 for an older kldxref. To avoid such warnings, make sure to rebuild
367 the kernel toolchain (or world). Make sure that you have r292078 or
368 later when trying to build 292077 or later before rebuilding.
371 Debug data files are now built by default with 'make buildworld' and
372 installed with 'make installworld'. This facilitates debugging but
373 requires more disk space both during the build and for the installed
374 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
378 r291527 changed the internal interface between the nfsd.ko and
379 nfscommon.ko modules. As such, they must both be upgraded to-gether.
380 __FreeBSD_version has been bumped because of this.
383 Add support for unicode collation strings leads to a change of
384 order of files listed by ls(1) for example. To get back to the old
385 behaviour, set LC_COLLATE environment variable to "C".
387 Databases administrators will need to reindex their databases given
388 collation results will be different.
390 Due to a bug in install(1) it is recommended to remove the ancient
391 locales before running make installworld.
393 rm -rf /usr/share/locale/*
396 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
397 libcrypto.so.7 or libssl.so.7 must be recompiled.
400 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
401 Kernel modules isp_2400_multi and isp_2500_multi were removed and
402 should be replaced with isp_2400 and isp_2500 modules respectively.
405 The build previously allowed using 'make -n' to not recurse into
406 sub-directories while showing what commands would be executed, and
407 'make -n -n' to recursively show commands. Now 'make -n' will recurse
408 and 'make -N' will not.
411 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
412 and etcupdate will now use this file. A custom sendmail.cf is now
413 updated via this mechanism rather than via installworld. If you had
414 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
415 want to remove the exclusion or change it to "always install".
416 /etc/mail/sendmail.cf is now managed the same way regardless of
417 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
418 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
421 Compatibility shims for legacy ATA device names have been removed.
422 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
423 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
424 environment variables, /dev/ad* and /dev/ar* symbolic links.
427 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
428 Please see the 20141231 entry below for information about prerequisites
429 and upgrading, if you are not already using clang 3.5.0 or higher.
432 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
433 and renamed from .symbols to .debug. This reduces the size requirements
434 on the boot partition or file system and provides consistency with
435 userland debug files.
437 When using the supported kernel installation method the
438 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
439 as is done with /boot/kernel.
441 Developers wishing to maintain the historical behavior of installing
442 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
445 The wireless drivers had undergone changes that remove the 'parent
446 interface' from the ifconfig -l output. The rc.d network scripts
447 used to check presence of a parent interface in the list, so old
448 scripts would fail to start wireless networking. Thus, etcupdate(3)
449 or mergemaster(8) run is required after kernel update, to update your
450 rc.d scripts in /etc.
453 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
454 These configurations are now automatically interpreted as
455 'scrub fragment reassemble'.
458 Kernel-loadable modules for the random(4) device are back. To use
459 them, the kernel must have
462 options RANDOM_LOADABLE
464 kldload(8) can then be used to load random_fortuna.ko
465 or random_yarrow.ko. Please note that due to the indirect
466 function calls that the loadable modules need to provide,
467 the build-in variants will be slightly more efficient.
469 The random(4) kernel option RANDOM_DUMMY has been retired due to
470 unpopularity. It was not all that useful anyway.
473 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
474 Control over building the ELF Tool Chain tools is now provided by
475 the WITHOUT_TOOLCHAIN knob.
478 The polarity of Pulse Per Second (PPS) capture events with the
479 uart(4) driver has been corrected. Prior to this change the PPS
480 "assert" event corresponded to the trailing edge of a positive PPS
481 pulse and the "clear" event was the leading edge of the next pulse.
483 As the width of a PPS pulse in a typical GPS receiver is on the
484 order of 1 millisecond, most users will not notice any significant
485 difference with this change.
487 Anyone who has compensated for the historical polarity reversal by
488 configuring a negative offset equal to the pulse width will need to
489 remove that workaround.
492 The default group assigned to /dev/dri entries has been changed
493 from 'wheel' to 'video' with the id of '44'. If you want to have
494 access to the dri devices please add yourself to the video group
497 # pw groupmod video -m $USER
500 The menu.rc and loader.rc files will now be replaced during
501 upgrades. Please migrate local changes to menu.rc.local and
502 loader.rc.local instead.
505 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
506 strings and strip have been removed. The src.conf(5) knob
507 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
510 As ZFS requires more kernel stack pages than is the default on some
511 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
512 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
514 Please consider using 'options KSTACK_PAGES=X' where X is greater
515 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
518 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
519 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
520 default, i.e., they will not contain "::". For example, instead
521 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
522 to have a more specific match, such as different map entries for
523 IPv6:0:0 vs IPv6:0. This change requires that configuration
524 data (including maps, files, classes, custom ruleset, etc.) must
525 use the same format, so make certain such configuration data is
526 upgrading. As a very simple check search for patterns like
527 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
528 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
529 the cf option UseCompressedIPv6Addresses.
532 The default kernel entropy-processing algorithm is now
533 Fortuna, replacing Yarrow.
535 Assuming you have 'device random' in your kernel config
536 file, the configurations allow a kernel option to override
537 this default. You may choose *ONE* of:
539 options RANDOM_YARROW # Legacy /dev/random algorithm.
540 options RANDOM_DUMMY # Blocking-only driver.
542 If you have neither, you get Fortuna. For most people,
543 read no further, Fortuna will give a /dev/random that works
544 like it always used to, and the difference will be irrelevant.
546 If you remove 'device random', you get *NO* kernel-processed
547 entropy at all. This may be acceptable to folks building
548 embedded systems, but has complications. Carry on reading,
549 and it is assumed you know what you need.
551 *PLEASE* read random(4) and random(9) if you are in the
552 habit of tweaking kernel configs, and/or if you are a member
553 of the embedded community, wanting specific and not-usual
554 behaviour from your security subsystems.
556 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
557 random', you will NOT have a functioning /dev/random, and
558 many cryptographic features will not work, including SSH.
559 You may also find strange behaviour from the random(3) set
560 of library functions, in particular sranddev(3), srandomdev(3)
561 and arc4random(3). The reason for this is that the KERN_ARND
562 sysctl only returns entropy if it thinks it has some to
563 share, and with RANDOM_DUMMY or no 'device random' this
567 An additional fix for the issue described in the 20150614 sendmail
568 entry below has been been committed in revision 284717.
571 FreeBSD's old make (fmake) has been removed from the system. It is
572 available as the devel/fmake port or via pkg install fmake.
575 The fix for the issue described in the 20150614 sendmail entry
576 below has been been committed in revision 284436. The work
577 around described in that entry is no longer needed unless the
578 default setting is overridden by a confDH_PARAMETERS configuration
579 setting of '5' or pointing to a 512 bit DH parameter file.
582 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
583 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
584 and devel/kyua to version 0.20+ and adjust any calling code to work
585 with Kyuafile and kyua.
588 The import of openssl to address the FreeBSD-SA-15:10.openssl
589 security advisory includes a change which rejects handshakes
590 with DH parameters below 768 bits. sendmail releases prior
591 to 8.15.2 (not yet released), defaulted to a 512 bit
592 DH parameter setting for client connections. To work around
593 this interoperability, sendmail can be configured to use a
594 2048 bit DH parameter by:
596 1. Edit /etc/mail/`hostname`.mc
597 2. If a setting for confDH_PARAMETERS does not exist or
598 exists and is set to a string beginning with '5',
600 3. If a setting for confDH_PARAMETERS exists and is set to
601 a file path, create a new file with:
602 openssl dhparam -out /path/to/file 2048
603 4. Rebuild the .cf file:
604 cd /etc/mail/; make; make install
606 cd /etc/mail/; make restart
608 A sendmail patch is coming, at which time this file will be
612 Generation of legacy formatted entries have been disabled by default
613 in pwd_mkdb(8), as all base system consumers of the legacy formatted
614 entries were converted to use the new format by default when the new,
615 machine independent format have been added and supported since FreeBSD
618 Please see the pwd_mkdb(8) manual page for further details.
621 Clang and llvm have been upgraded to 3.6.1 release. Please see the
622 20141231 entry below for information about prerequisites and upgrading,
623 if you are not already using 3.5.0 or higher.
626 TI platform code switched to using vendor DTS files and this update
627 may break existing systems running on Beaglebone, Beaglebone Black,
630 - dtb files should be regenerated/reinstalled. Filenames are the
631 same but content is different now
632 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
633 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
634 addressing scheme is now pin 25 on /dev/gpioc3.
635 - Pandaboard: /etc/ttys should be updated, serial console device is
636 now /dev/ttyu2, not /dev/ttyu0
639 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
640 If you need the GNU extension from groff soelim(1), install groff
641 from package: pkg install groff, or via ports: textproc/groff.
644 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
645 defined in symlink(7); previously symlinks were silently ignored.
648 The const qualifier has been removed from iconv(3) to comply with
649 POSIX. The ports tree is aware of this from r384038 onwards.
652 Libraries specified by LIBADD in Makefiles must have a corresponding
653 DPADD_<lib> variable to ensure correct dependencies. This is now
654 enforced in src.libnames.mk.
657 From legacy ata(4) driver was removed support for SATA controllers
658 supported by more functional drivers ahci(4), siis(4) and mvs(4).
659 Kernel modules ataahci and ataadaptec were removed completely,
660 replaced by ahci and mvs modules respectively.
663 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
664 the 20141231 entry below for information about prerequisites and
665 upgrading, if you are not already using 3.5.0 or higher.
668 The 32-bit PowerPC kernel has been changed to a position-independent
669 executable. This can only be booted with a version of loader(8)
670 newer than January 31, 2015, so make sure to update both world and
671 kernel before rebooting.
674 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
675 but before r278950, the RNG was not seeded properly. Immediately
676 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
677 ssh keys or openssl keys) that were generated w/ a kernel from that
678 range. This does not affect programs that directly used /dev/random
679 or /dev/urandom. All userland uses of arc4random(3) are affected.
682 The autofs(4) ABI was changed in order to restore binary compatibility
683 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
687 The powerpc64 kernel has been changed to a position-independent
688 executable. This can only be booted with a new version of loader(8),
689 so make sure to update both world and kernel before rebooting.
692 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
693 only release, no new features have been added. Please see the 20141231
694 entry below for information about prerequisites and upgrading, if you
695 are not already using 3.5.0.
698 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
699 taken from the ELF Tool Chain project rather than GNU binutils. They
700 should be drop-in replacements, with the addition of arm64 support.
701 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
702 binutils tools, if necessary. See 20150805 for updated information.
705 The default Unbound configuration now enables remote control
706 using a local socket. Users who have already enabled the
707 local_unbound service should regenerate their configuration
708 by running "service local_unbound setup" as root.
711 The GNU texinfo and GNU info pages have been removed.
712 To be able to view GNU info pages please install texinfo from ports.
715 Clang, llvm and lldb have been upgraded to 3.5.0 release.
717 As of this release, a prerequisite for building clang, llvm and lldb is
718 a C++11 capable compiler and C++11 standard library. This means that to
719 be able to successfully build the cross-tools stage of buildworld, with
720 clang as the bootstrap compiler, your system compiler or cross compiler
721 should either be clang 3.3 or later, or gcc 4.8 or later, and your
722 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
725 On any standard FreeBSD 10.x or 11.x installation, where clang and
726 libc++ are on by default (that is, on x86 or arm), this should work out
729 On 9.x installations where clang is enabled by default, e.g. on x86 and
730 powerpc, libc++ will not be enabled by default, so libc++ should be
731 built (with clang) and installed first. If both clang and libc++ are
732 missing, build clang first, then use it to build libc++.
734 On 8.x and earlier installations, upgrade to 9.x first, and then follow
735 the instructions for 9.x above.
737 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
738 default, and do not build clang.
740 Many embedded systems are resource constrained, and will not be able to
741 build clang in a reasonable time, or in some cases at all. In those
742 cases, cross building bootable systems on amd64 is a workaround.
744 This new version of clang introduces a number of new warnings, of which
745 the following are most likely to appear:
749 This warns in two cases, for both C and C++:
750 * When the code is trying to take the absolute value of an unsigned
751 quantity, which is effectively a no-op, and almost never what was
752 intended. The code should be fixed, if at all possible. If you are
753 sure that the unsigned quantity can be safely cast to signed, without
754 loss of information or undefined behavior, you can add an explicit
755 cast, or disable the warning.
757 * When the code is trying to take an absolute value, but the called
758 abs() variant is for the wrong type, which can lead to truncation.
759 If you want to disable the warning instead of fixing the code, please
760 make sure that truncation will not occur, or it might lead to unwanted
763 -Wtautological-undefined-compare and
764 -Wundefined-bool-conversion
766 These warn when C++ code is trying to compare 'this' against NULL, while
767 'this' should never be NULL in well-defined C++ code. However, there is
768 some legacy (pre C++11) code out there, which actively abuses this
769 feature, which was less strictly defined in previous C++ versions.
771 Squid and openjdk do this, for example. The warning can be turned off
772 for C++98 and earlier, but compiling the code in C++11 mode might result
773 in unexpected behavior; for example, the parts of the program that are
774 unreachable could be optimized away.
777 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
778 kernel sources have been removed. The .h files remain, since some
779 utilities include them. This will need to be fixed later.
780 If "mount -t oldnfs ..." is attempted, it will fail.
781 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
782 the utilities will report errors.
785 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
786 directories to top level SUBDIR variable when their parent
787 directory is included in LOCAL_DIRS. Users with build systems with
788 such hierarchies and without SUBDIR entries in the parent
789 directory Makefiles should add them or add the directories to
793 faith(4) and faithd(8) have been removed from the base system. Faith
794 has been obsolete for a very long time.
797 vt(4), the new console driver, is enabled by default. It brings
798 support for Unicode and double-width characters, as well as
799 support for UEFI and integration with the KMS kernel video
802 You may need to update your console settings in /etc/rc.conf,
803 most probably the keymap. During boot, /etc/rc.d/syscons will
804 indicate what you need to do.
806 vt(4) still has issues and lacks some features compared to
807 syscons(4). See the wiki for up-to-date information:
808 https://wiki.freebsd.org/Newcons
810 If you want to keep using syscons(4), you can do so by adding
811 the following line to /boot/loader.conf:
815 pjdfstest has been integrated into kyua as an opt-in test suite.
816 Please see share/doc/pjdfstest/README for more details on how to
820 gperf has been removed from the base system for architectures
821 that use clang. Ports that require gperf will obtain it from the
825 pjdfstest has been moved from tools/regression/pjdfstest to
829 At svn r271982, The default linux compat kernel ABI has been adjusted
830 to 2.6.18 in support of the linux-c6 compat ports infrastructure
831 update. If you wish to continue using the linux-f10 compat ports,
832 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
833 encouraged to update their linux-compat packages to linux-c6 during
834 their next update cycle.
837 The ofwfb driver, used to provide a graphics console on PowerPC when
838 using vt(4), no longer allows mmap() of all physical memory. This
839 will prevent Xorg on PowerPC with some ATI graphics cards from
840 initializing properly unless x11-servers/xorg-server is updated to
844 The xdev targets have been converted to using TARGET and
845 TARGET_ARCH instead of XDEV and XDEV_ARCH.
848 The default unbound configuration has been modified to address
849 issues with reverse lookups on networks that use private
850 address ranges. If you use the local_unbound service, run
851 "service local_unbound setup" as root to regenerate your
852 configuration, then "service local_unbound reload" to load the
856 The GNU texinfo and GNU info pages are not built and installed
857 anymore, WITH_INFO knob has been added to allow to built and install
859 UPDATE: see 20150102 entry on texinfo's removal
862 The GNU readline library is now an INTERNALLIB - that is, it is
863 statically linked into consumers (GDB and variants) in the base
864 system, and the shared library is no longer installed. The
865 devel/readline port is available for third party software that
869 The Itanium architecture (ia64) has been removed from the list of
870 known architectures. This is the first step in the removal of the
874 Commit r268115 has added NFSv4.1 server support, merged from
875 projects/nfsv4.1-server. Since this includes changes to the
876 internal interfaces between the NFS related modules, a full
877 build of the kernel and modules will be necessary.
878 __FreeBSD_version has been bumped.
881 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
882 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
883 which differs from the behaviour controlled by this knob.)
886 Maximal length of the serial number in CTL was increased from 16 to
887 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
888 and ctld, need to be rebuilt to work with a new kernel.
891 The libatf-c and libatf-c++ major versions were downgraded to 0 and
892 1 respectively to match the upstream numbers. They were out of
893 sync because, when they were originally added to FreeBSD, the
894 upstream versions were not respected. These libraries are private
895 and not yet built by default, so renumbering them should be a
896 non-issue. However, unclean source trees will yield broken test
897 programs once the operator executes "make delete-old-libs" after a
900 Additionally, the atf-sh binary was made private by moving it into
901 /usr/libexec/. Already-built shell test programs will keep the
902 path to the old binary so they will break after "make delete-old"
905 If you are using WITH_TESTS=yes (not the default), wipe the object
906 tree and rebuild from scratch to prevent spurious test failures.
907 This is only needed once: the misnumbered libraries and misplaced
908 binaries have been added to OptionalObsoleteFiles.inc so they will
909 be removed during a clean upgrade.
912 Clang and llvm have been upgraded to 3.4.1 release.
915 We bogusly installed src.opts.mk in /usr/share/mk. This file should
916 be removed to avoid issues in the future (and has been added to
920 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
921 past, it affected all builds that used the bsd.*.mk files. The old
922 behavior was a bug, but people may have relied upon it. To get this
923 behavior back, you can .include /etc/src.conf from /etc/make.conf
924 (which is still global and isn't changed). This also changes the
925 behavior of incremental builds inside the tree of individual
926 directories. Set MAKESYSPATH to ".../share/mk" to do that.
927 Although this has survived make universe and some upgrade scenarios,
928 other upgrade scenarios may have broken. At least one form of
929 temporary breakage was fixed with MAKESYSPATH settings for buildworld
930 as well... In cases where MAKESYSPATH isn't working with this
931 setting, you'll need to set it to the full path to your tree.
933 One side effect of all this cleaning up is that bsd.compiler.mk
934 is no longer implicitly included by bsd.own.mk. If you wish to
935 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
939 The lindev device has been removed since /dev/full has been made a
940 standard device. __FreeBSD_version has been bumped.
943 The knob WITHOUT_VI was added to the base system, which controls
944 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
945 in order to reorder files share/termcap and didn't build ex(1) as a
946 build tool, so building/installing with WITH_VI is highly advised for
947 build hosts for older releases.
949 This issue has been fixed in stable/9 and stable/10 in r277022 and
950 r276991, respectively.
953 The YES_HESIOD knob has been removed. It has been obsolete for
954 a decade. Please move to using WITH_HESIOD instead or your builds
955 will silently lack HESIOD.
958 The uart(4) driver has been changed with respect to its handling
959 of the low-level console. Previously the uart(4) driver prevented
960 any process from changing the baudrate or the CLOCAL and HUPCL
961 control flags. By removing the restrictions, operators can make
962 changes to the serial console port without having to reboot.
963 However, when getty(8) is started on the serial device that is
964 associated with the low-level console, a misconfigured terminal
965 line in /etc/ttys will now have a real impact.
966 Before upgrading the kernel, make sure that /etc/ttys has the
967 serial console device configured as 3wire without baudrate to
968 preserve the previous behaviour. E.g:
969 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
972 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
973 to improve performance. To re-enable it, if needed, run rpcbind
974 with command line option -W.
977 Switched back to the GPL dtc compiler due to updates in the upstream
978 dts files not being supported by the BSDL dtc compiler. You will need
979 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
980 may result while building dtb files during a kernel build if you fail
981 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
984 Clang and llvm have been upgraded to 3.4 release.
987 The nve(4) driver has been removed. Please use the nfe(4) driver
988 for NVIDIA nForce MCP Ethernet adapters instead.
991 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
992 This could cause certain C++ applications using shared libraries built
993 against the previous version of libc++ to crash. The incompatibility
994 has now been fixed, but any C++ applications or shared libraries built
995 between r261283 and r261801 should be recompiled.
998 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
999 capability mode support. Please note that enabling the feature in
1000 kernel is still highly recommended.
1003 OpenSSH is now built with sandbox support, and will use sandbox as
1004 the default privilege separation method. This requires Capsicum
1005 capability mode support in kernel.
1008 The libelf and libdwarf libraries have been updated to newer
1009 versions from upstream. Shared library version numbers for
1010 these two libraries were bumped. Any ports or binaries
1011 requiring these two libraries should be recompiled.
1012 __FreeBSD_version is bumped to 1100006.
1015 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1016 instead of providing an explicit one, this would prevent such
1017 Makefile from providing its own Kyuafile in the future during
1018 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1019 intervention is needed to clean an objdir if you use NO_CLEAN:
1020 # find /usr/obj -name Kyuafile | xargs rm -f
1023 The behavior of gss_pseudo_random() for the krb5 mechanism
1024 has changed, for applications requesting a longer random string
1025 than produced by the underlying enctype's pseudo-random() function.
1026 In particular, the random string produced from a session key of
1027 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1028 be different at the 17th octet and later, after this change.
1029 The counter used in the PRF+ construction is now encoded as a
1030 big-endian integer in accordance with RFC 4402.
1031 __FreeBSD_version is bumped to 1100004.
1034 The WITHOUT_ATF build knob has been removed and its functionality
1035 has been subsumed into the more generic WITHOUT_TESTS. If you were
1036 using the former to disable the build of the ATF libraries, you
1037 should change your settings to use the latter.
1040 The default version of mtree is nmtree which is obtained from
1041 NetBSD. The output is generally the same, but may vary
1042 slightly. If you found you need identical output adding
1043 "-F freebsd9" to the command line should do the trick. For the
1044 time being, the old mtree is available as fmtree.
1047 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1048 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1049 1.1.4_8 and verify bsdyml not linked in, before running "make
1051 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1053 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1056 The stable/10 branch has been created in subversion from head
1060 The rc.d/jail script has been updated to support jail(8)
1061 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1062 for per-jail configuration are automatically converted to
1063 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1064 This is transparently backward compatible. See below about some
1065 incompatibilities and rc.conf(5) manual page for more details.
1067 These variables are now deprecated in favor of jail(8) configuration
1068 file. One can use "rc.d/jail config <jname>" command to generate
1069 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1070 running the jail(8) utility. The default pathname of the
1071 configuration file is /etc/jail.conf and can be specified by
1072 using $jail_conf or $jail_<jname>_conf variables.
1074 Please note that jail_devfs_ruleset accepts an integer at
1075 this moment. Please consider to rewrite the ruleset name
1079 BIND has been removed from the base system. If all you need
1080 is a local resolver, simply enable and start the local_unbound
1081 service instead. Otherwise, several versions of BIND are
1082 available in the ports tree. The dns/bind99 port is one example.
1084 With this change, nslookup(1) and dig(1) are no longer in the base
1085 system. Users should instead use host(1) and drill(1) which are
1086 in the base system. Alternatively, nslookup and dig can
1087 be obtained by installing the dns/bind-tools port.
1090 With the addition of unbound(8), a new unbound user is now
1091 required during installworld. "mergemaster -p" can be used to
1092 add the user prior to installworld, as documented in the handbook.
1095 OpenSSH is now built with DNSSEC support, and will by default
1096 silently trust signed SSHFP records. This can be controlled with
1097 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1098 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1101 The GNU Compiler Collection and C++ standard library (libstdc++)
1102 are no longer built by default on platforms where clang is the system
1103 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1104 options in src.conf.
1107 The PROCDESC kernel option is now part of the GENERIC kernel
1108 configuration and is required for the rwhod(8) to work.
1109 If you are using custom kernel configuration, you should include
1113 The API and ABI related to the Capsicum framework was modified
1114 in backward incompatible way. The userland libraries and programs
1115 have to be recompiled to work with the new kernel. This includes the
1116 following libraries and programs, but the whole buildworld is
1117 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1118 kdump, procstat, rwho, rwhod, uniq.
1121 AES-NI intrinsic support has been added to gcc. The AES-NI module
1122 has been updated to use this support. A new gcc is required to build
1123 the aesni module on both i386 and amd64.
1126 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1127 Thus "device padlock_rng" and "device rdrand_rng" should be
1128 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1131 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1132 enables just the iconv* functionality and is now on by default.
1133 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1134 compatibility. Set WITHOUT_ICONV to build the old way.
1135 If you have been using WITH_ICONV before, you will very likely
1136 need to turn on WITH_LIBICONV_COMPAT.
1139 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1140 Illumos origin, including ZFS. If you have INVARIANTS in your
1141 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1143 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1144 locks if WITNESS option was set. Because that generated a lot of
1145 witness(9) reports and all of them were believed to be false
1146 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1147 can be used to achieve the previous behavior.
1150 Timer values in IPv6 data structures now use time_uptime instead
1151 of time_second. Although this is not a user-visible functional
1152 change, userland utilities which directly use them---ndp(8),
1153 rtadvd(8), and rtsold(8) in the base system---need to be updated
1154 to r253970 or later.
1157 find -delete can now delete the pathnames given as arguments,
1158 instead of only files found below them or if the pathname did
1159 not contain any slashes. Formerly, the following error message
1162 find: -delete: <path>: relative path potentially not safe
1164 Deleting the pathnames given as arguments can be prevented
1165 without error messages using -mindepth 1 or by changing
1166 directory and passing "." as argument to find. This works in the
1167 old as well as the new version of find.
1170 Behavior of devfs rules path matching has been changed.
1171 Pattern is now always matched against fully qualified devfs
1172 path and slash characters must be explicitly matched by
1173 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1174 subdirectories must be reviewed.
1177 The default ARM ABI has changed to the ARM EABI. The old ABI is
1178 incompatible with the ARM EABI and all programs and modules will
1179 need to be rebuilt to work with a new kernel.
1181 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1183 NOTE: Support for the old ABI will be removed in the future and
1184 users are advised to upgrade.
1187 pkg_install has been disconnected from the build if you really need it
1188 you should add WITH_PKGTOOLS in your src.conf(5).
1191 Most of network statistics structures were changed to be able
1192 keep 64-bits counters. Thus all tools, that work with networking
1193 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1196 Fix a bug that allowed a tracing process (e.g. gdb) to write
1197 to a memory-mapped file in the traced process's address space
1198 even if neither the traced process nor the tracing process had
1199 write access to that file.
1202 CVS has been removed from the base system. An exact copy
1203 of the code is available from the devel/cvs port.
1206 Some people report the following error after the switch to bmake:
1208 make: illegal option -- J
1209 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1211 *** [buildworld] Error code 2
1213 this likely due to an old instance of make in
1214 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1215 which src/Makefile will use that blindly, if it exists, so if
1216 you see the above error:
1218 rm -rf `make -V MAKEPATH`
1223 Use bmake by default.
1224 Whereas before one could choose to build with bmake via
1225 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1226 make. The goal is to remove these knobs for 10-RELEASE.
1228 It is worth noting that bmake (like gmake) treats the command
1229 line as the unit of failure, rather than statements within the
1230 command line. Thus '(cd some/where && dosomething)' is safer
1231 than 'cd some/where; dosomething'. The '()' allows consistent
1232 behavior in parallel build.
1235 Fix a bug that allows NFS clients to issue READDIR on files.
1238 The WITHOUT_IDEA option has been removed because
1239 the IDEA patent expired.
1242 The sysctl which controls TRIM support under ZFS has been renamed
1243 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1247 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1248 rather than creating it's own in the temporary directory in
1249 order allow access to bootstrapped versions of tools such as
1250 install and mtree. When upgrading from version of FreeBSD where
1251 the install command does not support -l, you will need to
1252 install a new mergemaster command if mergemaster -p is required.
1253 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1257 Legacy ATA stack, disabled and replaced by new CAM-based one since
1258 FreeBSD 9.0, completely removed from the sources. Kernel modules
1259 atadisk and atapi*, user-level tools atacontrol and burncd are
1260 removed. Kernel option `options ATA_CAM` is now permanently enabled
1264 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1265 and socketpair(2). Software, in particular Kerberos, may
1266 automatically detect and use these during building. The resulting
1267 binaries will not work on older kernels.
1270 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1271 information, see the respective 20130304 entry).
1274 Recent commits to callout(9) changed the size of struct callout,
1275 so the KBI is probably heavily disturbed. Also, some functions
1276 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1277 by macros. Every kernel module using it won't load, so rebuild
1280 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1281 but does not initialize by default (because of the new CTL_DISABLE
1282 option) to save memory. To re-enable it, remove the CTL_DISABLE
1283 option from the kernel config file or set kern.cam.ctl.disable=0
1284 in /boot/loader.conf.
1287 The ctl device has been disabled in GENERIC for i386 and amd64.
1288 This was done due to the extra memory being allocated at system
1289 initialisation time by the ctl driver which was only used if
1290 a CAM target device was created. This makes a FreeBSD system
1291 unusable on 128MB or less of RAM.
1294 A new compression method (lz4) has been merged to -HEAD. Please
1295 refer to zpool-features(7) for more information.
1297 Please refer to the "ZFS notes" section of this file for information
1298 on upgrading boot ZFS pools.
1301 A BSD-licensed patch(1) variant has been added and is installed
1302 as bsdpatch, being the GNU version the default patch.
1303 To inverse the logic and use the BSD-licensed one as default,
1304 while having the GNU version installed as gnupatch, rebuild
1305 and install world with the WITH_BSD_PATCH knob set.
1308 Due to the use of the new -l option to install(1) during build
1309 and install, you must take care not to directly set the INSTALL
1310 make variable in your /etc/make.conf, /etc/src.conf, or on the
1311 command line. If you wish to use the -C flag for all installs
1312 you may be able to add INSTALL+=-C to /etc/make.conf or
1316 The install(1) option -M has changed meaning and now takes an
1317 argument that is a file or path to append logs to. In the
1318 unlikely event that -M was the last option on the command line
1319 and the command line contained at least two files and a target
1320 directory the first file will have logs appended to it. The -M
1321 option served little practical purpose in the last decade so its
1322 use is expected to be extremely rare.
1325 After switching to Clang as the default compiler some users of ZFS
1326 on i386 systems started to experience stack overflow kernel panics.
1327 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1330 GEOM_LABEL now mangles label names read from file system metadata.
1331 Mangling affect labels containing spaces, non-printable characters,
1332 '%' or '"'. Device names in /etc/fstab and other places may need to
1336 By default, only the 10 most recent kernel dumps will be saved. To
1337 restore the previous behaviour (no limit on the number of kernel dumps
1338 stored in the dump directory) add the following line to /etc/rc.conf:
1343 With the addition of auditdistd(8), a new auditdistd user is now
1344 required during installworld. "mergemaster -p" can be used to
1345 add the user prior to installworld, as documented in the handbook.
1348 The sin6_scope_id member variable in struct sockaddr_in6 is now
1349 filled by the kernel before passing the structure to the userland via
1350 sysctl or routing socket. This means the KAME-specific embedded scope
1351 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1352 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1353 __FreeBSD_version is bumped to 1000025.
1356 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1357 This means that the world and kernel will be compiled with clang
1358 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1359 and /usr/bin/cpp. To disable this behavior and revert to building
1360 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1361 of current may need to bootstrap WITHOUT_CLANG first if the clang
1362 build fails (its compatibility window doesn't extend to the 9 stable
1366 The IPFIREWALL_FORWARD kernel option has been removed. Its
1367 functionality now turned on by default.
1370 The ZERO_COPY_SOCKET kernel option has been removed and
1371 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1372 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1373 mechanism which is not safe and may result in kernel crashes.
1374 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1375 driver supports disposeable external page sized mbuf storage.
1376 Proper replacements for both zero-copy mechanisms are under
1377 consideration and will eventually lead to complete removal
1378 of the two kernel options.
1381 The IPv4 network stack has been converted to network byte
1382 order. The following modules need to be recompiled together
1383 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1384 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1387 Support for non-MPSAFE filesystems was removed from VFS. The
1388 VFS_VERSION was bumped, all filesystem modules shall be
1392 All the non-MPSAFE filesystems have been disconnected from
1393 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1394 portalfs, smbfs, xfs.
1397 The interface cloning API and ABI has changed. The following
1398 modules need to be recompiled together with kernel:
1399 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1400 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1401 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1404 The sdhci driver was split in two parts: sdhci (generic SD Host
1405 Controller logic) and sdhci_pci (actual hardware driver).
1406 No kernel config modifications are required, but if you
1407 load sdhc as a module you must switch to sdhci_pci instead.
1410 Import the FUSE kernel and userland support into base system.
1413 The GNU sort(1) program has been removed since the BSD-licensed
1414 sort(1) has been the default for quite some time and no serious
1415 problems have been reported. The corresponding WITH_GNU_SORT
1419 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1420 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1424 The net80211(4) ABI has been changed to allow for improved driver
1425 PS-POLL and power-save support. All wireless drivers need to be
1426 recompiled to work with the new kernel.
1429 The random(4) support for the VIA hardware random number
1430 generator (`PADLOCK') is no longer enabled unconditionally.
1431 Add the padlock_rng device in the custom kernel config if
1432 needed. The GENERIC kernels on i386 and amd64 do include the
1433 device, so the change only affects the custom kernel
1437 The pf(4) packet filter ABI has been changed. pfctl(8) and
1438 snmp_pf module need to be recompiled to work with new kernel.
1441 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1442 to -HEAD. Pools that have empty_bpobj in active state can not be
1443 imported read-write with ZFS implementations that do not support
1444 this feature. For more information read the zpool-features(5)
1448 The sparc64 ZFS loader has been changed to no longer try to auto-
1449 detect ZFS providers based on diskN aliases but now requires these
1450 to be explicitly listed in the OFW boot-device environment variable.
1453 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1454 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1455 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1458 The following sysctls and tunables have been renamed for consistency
1459 with other variables:
1460 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1461 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1464 The sort utility has been replaced with BSD sort. For now, GNU sort
1465 is also available as "gnusort" or the default can be set back to
1466 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1467 installed as "bsdsort".
1470 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1471 Starting with this version the old system of ZFS pool versioning
1472 is superseded by "feature flags". This concept enables forward
1473 compatibility against certain future changes in functionality of ZFS
1474 pools. The first read-only compatible "feature flag" for ZFS pools
1475 is named "com.delphix:async_destroy". For more information
1476 read the new zpool-features(5) manual page.
1477 Please refer to the "ZFS notes" section of this file for information
1478 on upgrading boot ZFS pools.
1481 The malloc(3) implementation embedded in libc now uses sources imported
1482 as contrib/jemalloc. The most disruptive API change is to
1483 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1484 delete it prior to installworld, and optionally re-create it using the
1485 new format after rebooting. See malloc.conf(5) for details
1486 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1490 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1491 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1492 now spelled mips. This is to aid compatibility with third-party
1493 software that expects this naming scheme in uname(3). Little-endian
1494 settings are unchanged. If you are updating a big-endian mips64 machine
1495 from before this change, you may need to set MACHINE_ARCH=mips64 in
1496 your environment before the new build system will recognize your machine.
1499 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1503 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1504 nullfs(5) did not pass through all behaviours to the underlying layer,
1505 as a result if we bound to a socket on the lower layer we could connect
1506 only to the lower path; if we bound to the upper layer we could connect
1507 only to the upper path. The new behavior is one can connect to both the
1508 lower and the upper paths regardless what layer path one binds to.
1511 The getifaddrs upgrade path broken with 20111215 has been restored.
1512 If you have upgraded in between 20111215 and 20120209 you need to
1513 recompile libc again with your kernel. You still need to recompile
1514 world to be able to configure CARP but this restriction already
1515 comes from 20111215.
1518 The set_rcvar() function has been removed from /etc/rc.subr. All
1519 base and ports rc.d scripts have been updated, so if you have a
1520 port installed with a script in /usr/local/etc/rc.d you can either
1521 hand-edit the rcvar= line, or reinstall the port.
1523 An easy way to handle the mass-update of /etc/rc.d:
1524 rm /etc/rc.d/* && mergemaster -i
1527 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1528 on the current CPU and prevents other threads from running.
1529 This behavior can be reverted using the kern.stop_scheduler_on_panic
1531 The new behavior can be incompatible with kern.sync_on_panic.
1534 The carp(4) facility has been changed significantly. Configuration
1535 of the CARP protocol via ifconfig(8) has changed, as well as format
1536 of CARP events submitted to devd(8) has changed. See manual pages
1537 for more information. The arpbalance feature of carp(4) is currently
1538 not supported anymore.
1540 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1541 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1542 need to be recompiled.
1545 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1549 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1550 explicitely support non-MPSAFE filesystems.
1551 It is on by default for all supported platform at this present
1555 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1556 i386 and pc98 GENERIC kernel configuration files.
1559 sysinstall has been removed
1562 The stable/9 branch created in subversion. This corresponds to the
1563 RELENG_9 branch in CVS.
1569 Avoid using make -j when upgrading. While generally safe, there are
1570 sometimes problems using -j to upgrade. If your upgrade fails with
1571 -j, please try again without -j. From time to time in the past there
1572 have been problems using -j with buildworld and/or installworld. This
1573 is especially true when upgrading between "distant" versions (eg one
1574 that cross a major release boundary or several minor releases, or when
1575 several months have passed on the -current branch).
1577 Sometimes, obscure build problems are the result of environment
1578 poisoning. This can happen because the make utility reads its
1579 environment when searching for values for global variables. To run
1580 your build attempts in an "environmental clean room", prefix all make
1581 commands with 'env -i '. See the env(1) manual page for more details.
1583 When upgrading from one major version to another it is generally best
1584 to upgrade to the latest code in the currently installed branch first,
1585 then do an upgrade to the new branch. This is the best-tested upgrade
1586 path, and has the highest probability of being successful. Please try
1587 this approach before reporting problems with a major version upgrade.
1589 When upgrading a live system, having a root shell around before
1590 installing anything can help undo problems. Not having a root shell
1591 around can lead to problems if pam has changed too much from your
1592 starting point to allow continued authentication after the upgrade.
1594 This file should be read as a log of events. When a later event changes
1595 information of a prior event, the prior event should not be deleted.
1596 Instead, a pointer to the entry with the new information should be
1597 placed in the old entry. Readers of this file should also sanity check
1598 older entries before relying on them blindly. Authors of new entries
1599 should write them with this in mind.
1603 When upgrading the boot ZFS pool to a new version, always follow
1606 1.) recompile and reinstall the ZFS boot loader and boot block
1607 (this is part of "make buildworld" and "make installworld")
1609 2.) update the ZFS boot block on your boot drive
1611 The following example updates the ZFS boot block on the first
1612 partition (freebsd-boot) of a GPT partitioned drive ada0:
1613 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1615 Non-boot pools do not need these updates.
1619 If you are updating from a prior version of FreeBSD (even one just
1620 a few days old), you should follow this procedure. It is the most
1621 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1623 make kernel-toolchain
1624 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1625 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1627 To test a kernel once
1628 ---------------------
1629 If you just want to boot a kernel once (because you are not sure
1630 if it works, or if you want to boot a known bad kernel to provide
1631 debugging information) run
1632 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1633 nextboot -k testkernel
1635 To just build a kernel when you know that it won't mess you up
1636 --------------------------------------------------------------
1637 This assumes you are already running a CURRENT system. Replace
1638 ${arch} with the architecture of your machine (e.g. "i386",
1639 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1641 cd src/sys/${arch}/conf
1642 config KERNEL_NAME_HERE
1643 cd ../compile/KERNEL_NAME_HERE
1648 If this fails, go to the "To build a kernel" section.
1650 To rebuild everything and install it on the current system.
1651 -----------------------------------------------------------
1652 # Note: sometimes if you are running current you gotta do more than
1653 # is listed here if you are upgrading from a really old current.
1655 <make sure you have good level 0 dumps>
1657 make kernel KERNCONF=YOUR_KERNEL_HERE
1659 <reboot in single user> [3]
1666 To cross-install current onto a separate partition
1667 --------------------------------------------------
1668 # In this approach we use a separate partition to hold
1669 # current's root, 'usr', and 'var' directories. A partition
1670 # holding "/", "/usr" and "/var" should be about 2GB in
1673 <make sure you have good level 0 dumps>
1676 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1677 <maybe newfs current's root partition>
1678 <mount current's root partition on directory ${CURRENT_ROOT}>
1679 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1680 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1681 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1682 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1683 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1684 <reboot into current>
1685 <do a "native" rebuild/install as described in the previous section>
1686 <maybe install compatibility libraries from ports/misc/compat*>
1690 To upgrade in-place from stable to current
1691 ----------------------------------------------
1692 <make sure you have good level 0 dumps>
1694 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1696 <reboot in single user> [3]
1703 Make sure that you've read the UPDATING file to understand the
1704 tweaks to various things you need. At this point in the life
1705 cycle of current, things change often and you are on your own
1706 to cope. The defaults can also change, so please read ALL of
1707 the UPDATING entries.
1709 Also, if you are tracking -current, you must be subscribed to
1710 freebsd-current@freebsd.org. Make sure that before you update
1711 your sources that you have read and understood all the recent
1712 messages there. If in doubt, please track -stable which has
1713 much fewer pitfalls.
1715 [1] If you have third party modules, such as vmware, you
1716 should disable them at this point so they don't crash your
1719 [3] From the bootblocks, boot -s, and then do
1724 adjkerntz -i # if CMOS is wall time
1725 Also, when doing a major release upgrade, it is required that
1726 you boot into single user mode to do the installworld.
1728 [4] Note: This step is non-optional. Failure to do this step
1729 can result in a significant reduction in the functionality of the
1730 system. Attempting to do it by hand is not recommended and those
1731 that pursue this avenue should read this file carefully, as well
1732 as the archives of freebsd-current and freebsd-hackers mailing lists
1733 for potential gotchas. The -U option is also useful to consider.
1734 See mergemaster(8) for more information.
1736 [5] Usually this step is a noop. However, from time to time
1737 you may need to do this if you get unknown user in the following
1738 step. It never hurts to do it all the time. You may need to
1739 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1740 install) after the buildworld before this step if you last updated
1741 from current before 20130425 or from -stable before 20130430.
1743 [6] This only deletes old files and directories. Old libraries
1744 can be deleted by "make delete-old-libs", but you have to make
1745 sure that no program is using those libraries anymore.
1747 [8] In order to have a kernel that can run the 4.x binaries needed to
1748 do an installworld, you must include the COMPAT_FREEBSD4 option in
1749 your kernel. Failure to do so may leave you with a system that is
1750 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1751 required to run the 5.x binaries on more recent kernels. And so on
1752 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1754 Make sure that you merge any new devices from GENERIC since the
1755 last time you updated your kernel config file.
1757 [9] When checking out sources, you must include the -P flag to have
1758 cvs prune empty directories.
1760 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1761 "?=" instead of the "=" assignment operator, so that buildworld can
1762 override the CPUTYPE if it needs to.
1764 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1765 not on the command line, or in /etc/make.conf. buildworld will
1766 warn if it is improperly defined.
1769 This file contains a list, in reverse chronological order, of major
1770 breakages in tracking -current. It is not guaranteed to be a complete
1771 list of such breakages, and only contains entries since September 23, 2011.
1772 If you need to see UPDATING entries from before that date, you will need
1773 to fetch an UPDATING file from an older FreeBSD release.
1775 Copyright information:
1777 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1779 Redistribution, publication, translation and use, with or without
1780 modification, in full or in part, in any form or format of this
1781 document are permitted without further permission from the author.
1783 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1784 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1785 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1786 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1787 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1788 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1789 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1790 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1791 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1792 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1793 POSSIBILITY OF SUCH DAMAGE.
1795 Contact Warner Losh if you have any questions about your use of