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/makeworld.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.
20 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
21 6.0.1. Please see the 20141231 entry below for information about
22 prerequisites and upgrading, if you are not already using clang 3.5.0
26 The releng/11.2 branch has been created from stable/11@r334458.
29 The tz database (tzdb) has been updated to 2018e. This version more
30 correctly models time stamps in time zones with negative DST such as
31 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
32 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
33 time zone abbreviations and the tm_isdst flag.
36 The use of RSS hash from the network card aka flowid has been
37 disabled by default for lagg(4) as it's currently incompatible with
38 the lacp and loadbalance protocols.
40 This can be re-enabled by setting the following in loader.conf:
41 net.link.lagg.default_use_flowid="1"
44 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
45 6.0.0. Please see the 20141231 entry below for information about
46 prerequisites and upgrading, if you are not already using clang 3.5.0
50 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
51 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
52 to WITH/OUT_LOADER_GELI.
55 The geli password typed at boot is now hidden. To restore the previous
56 behavior, see geli(8) for configuration options.
58 The SW_WATCHDOG option is no longer necessary to enable the
59 hardclock-based software watchdog if no hardware watchdog is
60 configured. As before, SW_WATCHDOG will cause the software
61 watchdog to be enabled even if a hardware watchdog is configured.
64 lint(1) binaries and library are no longer built by default. To
65 enable building them, define WITH_LINT in src.conf. If you are using
66 a FreeBSD 12 or later system to build 11-stable, you may need to
67 install a lint(1) binary to use WITH_LINT.
70 When building multiple kernels using KERNCONF, non-existent KERNCONF
71 files will produce an error and buildkernel will fail. Previously
72 missing KERNCONF files silently failed giving no indication as to
73 why, only to subsequently discover during installkernel that the
74 desired kernel was never built in the first place.
77 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
78 Please see the 20141231 entry below for information about prerequisites
79 and upgrading, if you are not already using clang 3.5.0 or higher.
82 Since the switch to GPT disk labels, fsck for UFS/FFS has been
83 unable to automatically find alternate superblocks. As of r322806,
84 the information needed to find alternate superblocks has been
85 moved to the end of the area reserved for the boot block.
86 Filesystems created with a newfs of this vintage or later
87 will create the recovery information. If you have a filesystem
88 created prior to this change and wish to have a recovery block
89 created for your filesystem, you can do so by running fsck in
90 forground mode (i.e., do not use the -p or -y options). As it
91 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
92 to which you should answer yes.
95 The releng/11.1 branch has been created from stable/11@r320475.
98 arm64 builds now use the base system LLD 4.0.0 linker by default,
99 instead of requiring that the aarch64-binutils port or package be
100 installed. To continue using aarch64-binutils, set
101 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
104 The ctl.ko module no longer implements the iSCSI target frontend:
105 cfiscsi.ko does instead.
107 If building cfiscsi.ko as a kernel module, the module can be loaded
108 via one of the following methods:
109 - `cfiscsi_load="YES"` in loader.conf(5).
110 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
111 - ctladm(8)/ctld(8), when compiled with iSCSI support
112 (`WITH_ISCSI=yes` in src.conf(5))
114 Please see cfiscsi(4) for more details.
117 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
118 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
119 same source (previously, the dependency of mmcsd.ko on mmc.ko was
120 missing, but mmcsd.ko now will refuse to load if it is incompatible
124 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
125 use any explicitly assigned loopback address available in the jail
126 instead of using the first assigned address of the jail.
129 As of r316810 for ipfilter, keep frags is no longer assumed when
130 keep state is specified in a rule. r316810 aligns ipfilter with
131 documentation in man pages separating keep frags from keep state.
132 This allows keep state to specified without forcing keep frags
133 and allows keep frags to be specified independently of keep state.
134 To maintain previous behaviour, also specify keep frags with
135 keep state (as documented in ipf.conf.5).
138 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
139 Please see the 20141231 entry below for information about prerequisites
140 and upgrading, if you are not already using clang 3.5.0 or higher.
143 The code that provides support for ZFS .zfs/ directory functionality
144 has been reimplemented. It's not possible now to create a snapshot
145 by mkdir under .zfs/snapshot/. That should be the only user visible
149 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
150 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
151 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
152 and now NAT-T is supported by default. Security associations now use
153 the single namespace for SPI allocation, so if you use several manually
154 configured security associations with the same SPI, this configuration
158 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
159 Please see the 20141231 entry below for information about prerequisites
160 and upgrading, if you are not already using clang 3.5.0 or higher.
163 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.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 layout of the pmap structure has changed for powerpc to put the pmap
169 statistics at the front for all CPU variations. libkvm(3) and all tools
170 that link against it need to be recompiled.
173 isl(4) and cyapa(4) drivers now require a new driver,
174 chromebook_platform(4), to work properly on Chromebook-class hardware.
175 On other types of hardware the drivers may need to be configured using
176 device hints. Please see the corresponding manual pages for details.
179 Relocatable object files with the extension of .So have been renamed
180 to use an extension of .pico instead. The purpose of this change is
181 to avoid a name clash with shared libraries on case-insensitive file
182 systems. On those file systems, foo.So is the same file as foo.so.
185 The releng/11.0 branch has been created from stable/11@r303970.
188 The stable/11 branch has been created from head@r302406.
191 The libc stub for the pipe(2) system call has been replaced with
192 a wrapper that calls the pipe2(2) system call and the pipe(2)
193 system call is now only implemented by the kernels that include
194 "options COMPAT_FREEBSD10" in their config file (this is the
195 default). Users should ensure that this option is enabled in
196 their kernel or upgrade userspace to r302092 before upgrading their
200 CAM will now strip leading spaces from SCSI disks' serial numbers.
201 This will effect users who create UFS filesystems on SCSI disks using
202 those disk's diskid device nodes. For example, if /etc/fstab
203 previously contained a line like
204 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
205 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
206 transforms like gmirror may also be affected. ZFS users should
210 The bitstring(3) API has been updated with new functionality and
211 improved performance. But it is binary-incompatible with the old API.
212 Objects built with the new headers may not be linked against objects
213 built with the old headers.
216 The brk and sbrk functions have been removed from libc on arm64.
217 Binutils from ports has been updated to not link to these
218 functions and should be updated to the latest version before
219 installing a new libc.
222 The armv6 port now defaults to hard float ABI. Limited support
223 for running both hardfloat and soft float on the same system
224 is available using the libraries installed with -DWITH_LIBSOFT.
225 This has only been tested as an upgrade path for installworld
226 and packages may fail or need manual intervention to run. New
227 packages will be needed.
229 To update an existing self-hosted armv6hf system, you must add
230 TARGET_ARCH=armv6 on the make command line for both the build
231 and the install steps.
234 Kernel modules compiled outside of a kernel build now default to
235 installing to /boot/modules instead of /boot/kernel. Many kernel
236 modules built this way (such as those in ports) already overrode
237 KMODDIR explicitly to install into /boot/modules. However,
238 manually building and installing a module from /sys/modules will
239 now install to /boot/modules instead of /boot/kernel.
242 The CAM I/O scheduler has been committed to the kernel. There should be
243 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
244 list of known rogues that claim support for this but actually corrupt
245 data is believed to be complete, be on the lookout for data
246 corruption. The known rogue list is believed to be complete:
248 o Crucial MX100, M550 drives with MU01 firmware.
249 o Micron M510 and M550 drives with MU01 firmware.
250 o Micron M500 prior to MU07 firmware
251 o Samsung 830, 840, and 850 all firmwares
252 o FCCT M500 all firmwares
254 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
255 with working NCQ TRIM. For Micron branded drives, see your sales rep for
256 updated firmware. Black listed drives will work correctly because these
257 drives work correctly so long as no NCQ TRIMs are sent to them. Given
258 this list is the same as found in Linux, it's believed there are no
259 other rogues in the market place. All other models from the above
262 To be safe, if you are at all concerned, you can quirk each of your
263 drives to prevent NCQ from being sent by setting:
264 kern.cam.ada.X.quirks="0x2"
265 in loader.conf. If the drive requires the 4k sector quirk, set the
269 The FAST_DEPEND build option has been removed and its functionality is
270 now the one true way. The old mkdep(1) style of 'make depend' has
271 been removed. See 20160311 for further details.
274 Resource range types have grown from unsigned long to uintmax_t. All
275 drivers, and anything using libdevinfo, need to be recompiled.
278 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
279 builds. It no longer runs mkdep(1) during 'make depend', and the
280 'make depend' stage can safely be skipped now as it is auto ran
281 when building 'make all' and will generate all SRCS and DPSRCS before
282 building anything else. Dependencies are gathered at compile time with
283 -MF flags kept in separate .depend files per object file. Users should
284 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
288 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
289 kernel modules. Therefore, if you load any kernel modules at boot time,
290 please install the boot loaders after you install the kernel, but before
294 make kernel KERNCONF=YOUR_KERNEL_HERE
295 make -C sys/boot install
296 <reboot in single user>
298 Then follow the usual steps, described in the General Notes section,
302 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
303 see the 20141231 entry below for information about prerequisites and
304 upgrading, if you are not already using clang 3.5.0 or higher.
307 The AIO subsystem is now a standard part of the kernel. The
308 VFS_AIO kernel option and aio.ko kernel module have been removed.
309 Due to stability concerns, asynchronous I/O requests are only
310 permitted on sockets and raw disks by default. To enable
311 asynchronous I/O requests on all file types, set the
312 vfs.aio.enable_unsafe sysctl to a non-zero value.
315 The ELF object manipulation tool objcopy is now provided by the
316 ELF Tool Chain project rather than by GNU binutils. It should be a
317 drop-in replacement, with the addition of arm64 support. The
318 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
319 to obtain the GNU version if necessary.
322 Building ZFS pools on top of zvols is prohibited by default. That
323 feature has never worked safely; it's always been prone to deadlocks.
324 Using a zvol as the backing store for a VM guest's virtual disk will
325 still work, even if the guest is using ZFS. Legacy behavior can be
326 restored by setting vfs.zfs.vol.recursive=1.
329 The NONE and HPN patches has been removed from OpenSSH. They are
330 still available in the security/openssh-portable port.
333 With the addition of ypldap(8), a new _ypldap user is now required
334 during installworld. "mergemaster -p" can be used to add the user
335 prior to installworld, as documented in the handbook.
338 The tftp loader (pxeboot) now uses the option root-path directive. As a
339 consequence it no longer looks for a pxeboot.4th file on the tftp
340 server. Instead it uses the regular /boot infrastructure as with the
344 The code to start recording plug and play data into the modules has
345 been committed. While the old tools will properly build a new kernel,
346 a number of warnings about "unknown metadata record 4" will be produced
347 for an older kldxref. To avoid such warnings, make sure to rebuild
348 the kernel toolchain (or world). Make sure that you have r292078 or
349 later when trying to build 292077 or later before rebuilding.
352 Debug data files are now built by default with 'make buildworld' and
353 installed with 'make installworld'. This facilitates debugging but
354 requires more disk space both during the build and for the installed
355 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
359 r291527 changed the internal interface between the nfsd.ko and
360 nfscommon.ko modules. As such, they must both be upgraded to-gether.
361 __FreeBSD_version has been bumped because of this.
364 Add support for unicode collation strings leads to a change of
365 order of files listed by ls(1) for example. To get back to the old
366 behaviour, set LC_COLLATE environment variable to "C".
368 Databases administrators will need to reindex their databases given
369 collation results will be different.
371 Due to a bug in install(1) it is recommended to remove the ancient
372 locales before running make installworld.
374 rm -rf /usr/share/locale/*
377 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
378 libcrypto.so.7 or libssl.so.7 must be recompiled.
381 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
382 Kernel modules isp_2400_multi and isp_2500_multi were removed and
383 should be replaced with isp_2400 and isp_2500 modules respectively.
386 The build previously allowed using 'make -n' to not recurse into
387 sub-directories while showing what commands would be executed, and
388 'make -n -n' to recursively show commands. Now 'make -n' will recurse
389 and 'make -N' will not.
392 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
393 and etcupdate will now use this file. A custom sendmail.cf is now
394 updated via this mechanism rather than via installworld. If you had
395 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
396 want to remove the exclusion or change it to "always install".
397 /etc/mail/sendmail.cf is now managed the same way regardless of
398 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
399 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
402 Compatibility shims for legacy ATA device names have been removed.
403 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
404 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
405 environment variables, /dev/ad* and /dev/ar* symbolic links.
408 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
409 Please see the 20141231 entry below for information about prerequisites
410 and upgrading, if you are not already using clang 3.5.0 or higher.
413 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
414 and renamed from .symbols to .debug. This reduces the size requirements
415 on the boot partition or file system and provides consistency with
416 userland debug files.
418 When using the supported kernel installation method the
419 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
420 as is done with /boot/kernel.
422 Developers wishing to maintain the historical behavior of installing
423 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
426 The wireless drivers had undergone changes that remove the 'parent
427 interface' from the ifconfig -l output. The rc.d network scripts
428 used to check presence of a parent interface in the list, so old
429 scripts would fail to start wireless networking. Thus, etcupdate(3)
430 or mergemaster(8) run is required after kernel update, to update your
431 rc.d scripts in /etc.
434 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
435 These configurations are now automatically interpreted as
436 'scrub fragment reassemble'.
439 Kernel-loadable modules for the random(4) device are back. To use
440 them, the kernel must have
443 options RANDOM_LOADABLE
445 kldload(8) can then be used to load random_fortuna.ko
446 or random_yarrow.ko. Please note that due to the indirect
447 function calls that the loadable modules need to provide,
448 the build-in variants will be slightly more efficient.
450 The random(4) kernel option RANDOM_DUMMY has been retired due to
451 unpopularity. It was not all that useful anyway.
454 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
455 Control over building the ELF Tool Chain tools is now provided by
456 the WITHOUT_TOOLCHAIN knob.
459 The polarity of Pulse Per Second (PPS) capture events with the
460 uart(4) driver has been corrected. Prior to this change the PPS
461 "assert" event corresponded to the trailing edge of a positive PPS
462 pulse and the "clear" event was the leading edge of the next pulse.
464 As the width of a PPS pulse in a typical GPS receiver is on the
465 order of 1 millisecond, most users will not notice any significant
466 difference with this change.
468 Anyone who has compensated for the historical polarity reversal by
469 configuring a negative offset equal to the pulse width will need to
470 remove that workaround.
473 The default group assigned to /dev/dri entries has been changed
474 from 'wheel' to 'video' with the id of '44'. If you want to have
475 access to the dri devices please add yourself to the video group
478 # pw groupmod video -m $USER
481 The menu.rc and loader.rc files will now be replaced during
482 upgrades. Please migrate local changes to menu.rc.local and
483 loader.rc.local instead.
486 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
487 strings and strip have been removed. The src.conf(5) knob
488 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
491 As ZFS requires more kernel stack pages than is the default on some
492 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
493 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
495 Please consider using 'options KSTACK_PAGES=X' where X is greater
496 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
499 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
500 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
501 default, i.e., they will not contain "::". For example, instead
502 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
503 to have a more specific match, such as different map entries for
504 IPv6:0:0 vs IPv6:0. This change requires that configuration
505 data (including maps, files, classes, custom ruleset, etc.) must
506 use the same format, so make certain such configuration data is
507 upgrading. As a very simple check search for patterns like
508 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
509 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
510 the cf option UseCompressedIPv6Addresses.
513 The default kernel entropy-processing algorithm is now
514 Fortuna, replacing Yarrow.
516 Assuming you have 'device random' in your kernel config
517 file, the configurations allow a kernel option to override
518 this default. You may choose *ONE* of:
520 options RANDOM_YARROW # Legacy /dev/random algorithm.
521 options RANDOM_DUMMY # Blocking-only driver.
523 If you have neither, you get Fortuna. For most people,
524 read no further, Fortuna will give a /dev/random that works
525 like it always used to, and the difference will be irrelevant.
527 If you remove 'device random', you get *NO* kernel-processed
528 entropy at all. This may be acceptable to folks building
529 embedded systems, but has complications. Carry on reading,
530 and it is assumed you know what you need.
532 *PLEASE* read random(4) and random(9) if you are in the
533 habit of tweaking kernel configs, and/or if you are a member
534 of the embedded community, wanting specific and not-usual
535 behaviour from your security subsystems.
537 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
538 random', you will NOT have a functioning /dev/random, and
539 many cryptographic features will not work, including SSH.
540 You may also find strange behaviour from the random(3) set
541 of library functions, in particular sranddev(3), srandomdev(3)
542 and arc4random(3). The reason for this is that the KERN_ARND
543 sysctl only returns entropy if it thinks it has some to
544 share, and with RANDOM_DUMMY or no 'device random' this
548 An additional fix for the issue described in the 20150614 sendmail
549 entry below has been been committed in revision 284717.
552 FreeBSD's old make (fmake) has been removed from the system. It is
553 available as the devel/fmake port or via pkg install fmake.
556 The fix for the issue described in the 20150614 sendmail entry
557 below has been been committed in revision 284436. The work
558 around described in that entry is no longer needed unless the
559 default setting is overridden by a confDH_PARAMETERS configuration
560 setting of '5' or pointing to a 512 bit DH parameter file.
563 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
564 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
565 and devel/kyua to version 0.20+ and adjust any calling code to work
566 with Kyuafile and kyua.
569 The import of openssl to address the FreeBSD-SA-15:10.openssl
570 security advisory includes a change which rejects handshakes
571 with DH parameters below 768 bits. sendmail releases prior
572 to 8.15.2 (not yet released), defaulted to a 512 bit
573 DH parameter setting for client connections. To work around
574 this interoperability, sendmail can be configured to use a
575 2048 bit DH parameter by:
577 1. Edit /etc/mail/`hostname`.mc
578 2. If a setting for confDH_PARAMETERS does not exist or
579 exists and is set to a string beginning with '5',
581 3. If a setting for confDH_PARAMETERS exists and is set to
582 a file path, create a new file with:
583 openssl dhparam -out /path/to/file 2048
584 4. Rebuild the .cf file:
585 cd /etc/mail/; make; make install
587 cd /etc/mail/; make restart
589 A sendmail patch is coming, at which time this file will be
593 Generation of legacy formatted entries have been disabled by default
594 in pwd_mkdb(8), as all base system consumers of the legacy formatted
595 entries were converted to use the new format by default when the new,
596 machine independent format have been added and supported since FreeBSD
599 Please see the pwd_mkdb(8) manual page for further details.
602 Clang and llvm have been upgraded to 3.6.1 release. Please see the
603 20141231 entry below for information about prerequisites and upgrading,
604 if you are not already using 3.5.0 or higher.
607 TI platform code switched to using vendor DTS files and this update
608 may break existing systems running on Beaglebone, Beaglebone Black,
611 - dtb files should be regenerated/reinstalled. Filenames are the
612 same but content is different now
613 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
614 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
615 addressing scheme is now pin 25 on /dev/gpioc3.
616 - Pandaboard: /etc/ttys should be updated, serial console device is
617 now /dev/ttyu2, not /dev/ttyu0
620 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
621 If you need the GNU extension from groff soelim(1), install groff
622 from package: pkg install groff, or via ports: textproc/groff.
625 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
626 defined in symlink(7); previously symlinks were silently ignored.
629 The const qualifier has been removed from iconv(3) to comply with
630 POSIX. The ports tree is aware of this from r384038 onwards.
633 Libraries specified by LIBADD in Makefiles must have a corresponding
634 DPADD_<lib> variable to ensure correct dependencies. This is now
635 enforced in src.libnames.mk.
638 From legacy ata(4) driver was removed support for SATA controllers
639 supported by more functional drivers ahci(4), siis(4) and mvs(4).
640 Kernel modules ataahci and ataadaptec were removed completely,
641 replaced by ahci and mvs modules respectively.
644 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
645 the 20141231 entry below for information about prerequisites and
646 upgrading, if you are not already using 3.5.0 or higher.
649 The 32-bit PowerPC kernel has been changed to a position-independent
650 executable. This can only be booted with a version of loader(8)
651 newer than January 31, 2015, so make sure to update both world and
652 kernel before rebooting.
655 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
656 but before r278950, the RNG was not seeded properly. Immediately
657 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
658 ssh keys or openssl keys) that were generated w/ a kernel from that
659 range. This does not affect programs that directly used /dev/random
660 or /dev/urandom. All userland uses of arc4random(3) are affected.
663 The autofs(4) ABI was changed in order to restore binary compatibility
664 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
668 The powerpc64 kernel has been changed to a position-independent
669 executable. This can only be booted with a new version of loader(8),
670 so make sure to update both world and kernel before rebooting.
673 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
674 only release, no new features have been added. Please see the 20141231
675 entry below for information about prerequisites and upgrading, if you
676 are not already using 3.5.0.
679 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
680 taken from the ELF Tool Chain project rather than GNU binutils. They
681 should be drop-in replacements, with the addition of arm64 support.
682 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
683 binutils tools, if necessary. See 20150805 for updated information.
686 The default Unbound configuration now enables remote control
687 using a local socket. Users who have already enabled the
688 local_unbound service should regenerate their configuration
689 by running "service local_unbound setup" as root.
692 The GNU texinfo and GNU info pages have been removed.
693 To be able to view GNU info pages please install texinfo from ports.
696 Clang, llvm and lldb have been upgraded to 3.5.0 release.
698 As of this release, a prerequisite for building clang, llvm and lldb is
699 a C++11 capable compiler and C++11 standard library. This means that to
700 be able to successfully build the cross-tools stage of buildworld, with
701 clang as the bootstrap compiler, your system compiler or cross compiler
702 should either be clang 3.3 or later, or gcc 4.8 or later, and your
703 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
706 On any standard FreeBSD 10.x or 11.x installation, where clang and
707 libc++ are on by default (that is, on x86 or arm), this should work out
710 On 9.x installations where clang is enabled by default, e.g. on x86 and
711 powerpc, libc++ will not be enabled by default, so libc++ should be
712 built (with clang) and installed first. If both clang and libc++ are
713 missing, build clang first, then use it to build libc++.
715 On 8.x and earlier installations, upgrade to 9.x first, and then follow
716 the instructions for 9.x above.
718 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
719 default, and do not build clang.
721 Many embedded systems are resource constrained, and will not be able to
722 build clang in a reasonable time, or in some cases at all. In those
723 cases, cross building bootable systems on amd64 is a workaround.
725 This new version of clang introduces a number of new warnings, of which
726 the following are most likely to appear:
730 This warns in two cases, for both C and C++:
731 * When the code is trying to take the absolute value of an unsigned
732 quantity, which is effectively a no-op, and almost never what was
733 intended. The code should be fixed, if at all possible. If you are
734 sure that the unsigned quantity can be safely cast to signed, without
735 loss of information or undefined behavior, you can add an explicit
736 cast, or disable the warning.
738 * When the code is trying to take an absolute value, but the called
739 abs() variant is for the wrong type, which can lead to truncation.
740 If you want to disable the warning instead of fixing the code, please
741 make sure that truncation will not occur, or it might lead to unwanted
744 -Wtautological-undefined-compare and
745 -Wundefined-bool-conversion
747 These warn when C++ code is trying to compare 'this' against NULL, while
748 'this' should never be NULL in well-defined C++ code. However, there is
749 some legacy (pre C++11) code out there, which actively abuses this
750 feature, which was less strictly defined in previous C++ versions.
752 Squid and openjdk do this, for example. The warning can be turned off
753 for C++98 and earlier, but compiling the code in C++11 mode might result
754 in unexpected behavior; for example, the parts of the program that are
755 unreachable could be optimized away.
758 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
759 kernel sources have been removed. The .h files remain, since some
760 utilities include them. This will need to be fixed later.
761 If "mount -t oldnfs ..." is attempted, it will fail.
762 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
763 the utilities will report errors.
766 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
767 directories to top level SUBDIR variable when their parent
768 directory is included in LOCAL_DIRS. Users with build systems with
769 such hierarchies and without SUBDIR entries in the parent
770 directory Makefiles should add them or add the directories to
774 faith(4) and faithd(8) have been removed from the base system. Faith
775 has been obsolete for a very long time.
778 vt(4), the new console driver, is enabled by default. It brings
779 support for Unicode and double-width characters, as well as
780 support for UEFI and integration with the KMS kernel video
783 You may need to update your console settings in /etc/rc.conf,
784 most probably the keymap. During boot, /etc/rc.d/syscons will
785 indicate what you need to do.
787 vt(4) still has issues and lacks some features compared to
788 syscons(4). See the wiki for up-to-date information:
789 https://wiki.freebsd.org/Newcons
791 If you want to keep using syscons(4), you can do so by adding
792 the following line to /boot/loader.conf:
796 pjdfstest has been integrated into kyua as an opt-in test suite.
797 Please see share/doc/pjdfstest/README for more details on how to
801 gperf has been removed from the base system for architectures
802 that use clang. Ports that require gperf will obtain it from the
806 pjdfstest has been moved from tools/regression/pjdfstest to
810 At svn r271982, The default linux compat kernel ABI has been adjusted
811 to 2.6.18 in support of the linux-c6 compat ports infrastructure
812 update. If you wish to continue using the linux-f10 compat ports,
813 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
814 encouraged to update their linux-compat packages to linux-c6 during
815 their next update cycle.
818 The ofwfb driver, used to provide a graphics console on PowerPC when
819 using vt(4), no longer allows mmap() of all physical memory. This
820 will prevent Xorg on PowerPC with some ATI graphics cards from
821 initializing properly unless x11-servers/xorg-server is updated to
825 The xdev targets have been converted to using TARGET and
826 TARGET_ARCH instead of XDEV and XDEV_ARCH.
829 The default unbound configuration has been modified to address
830 issues with reverse lookups on networks that use private
831 address ranges. If you use the local_unbound service, run
832 "service local_unbound setup" as root to regenerate your
833 configuration, then "service local_unbound reload" to load the
837 The GNU texinfo and GNU info pages are not built and installed
838 anymore, WITH_INFO knob has been added to allow to built and install
840 UPDATE: see 20150102 entry on texinfo's removal
843 The GNU readline library is now an INTERNALLIB - that is, it is
844 statically linked into consumers (GDB and variants) in the base
845 system, and the shared library is no longer installed. The
846 devel/readline port is available for third party software that
850 The Itanium architecture (ia64) has been removed from the list of
851 known architectures. This is the first step in the removal of the
855 Commit r268115 has added NFSv4.1 server support, merged from
856 projects/nfsv4.1-server. Since this includes changes to the
857 internal interfaces between the NFS related modules, a full
858 build of the kernel and modules will be necessary.
859 __FreeBSD_version has been bumped.
862 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
863 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
864 which differs from the behaviour controlled by this knob.)
867 Maximal length of the serial number in CTL was increased from 16 to
868 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
869 and ctld, need to be rebuilt to work with a new kernel.
872 The libatf-c and libatf-c++ major versions were downgraded to 0 and
873 1 respectively to match the upstream numbers. They were out of
874 sync because, when they were originally added to FreeBSD, the
875 upstream versions were not respected. These libraries are private
876 and not yet built by default, so renumbering them should be a
877 non-issue. However, unclean source trees will yield broken test
878 programs once the operator executes "make delete-old-libs" after a
881 Additionally, the atf-sh binary was made private by moving it into
882 /usr/libexec/. Already-built shell test programs will keep the
883 path to the old binary so they will break after "make delete-old"
886 If you are using WITH_TESTS=yes (not the default), wipe the object
887 tree and rebuild from scratch to prevent spurious test failures.
888 This is only needed once: the misnumbered libraries and misplaced
889 binaries have been added to OptionalObsoleteFiles.inc so they will
890 be removed during a clean upgrade.
893 Clang and llvm have been upgraded to 3.4.1 release.
896 We bogusly installed src.opts.mk in /usr/share/mk. This file should
897 be removed to avoid issues in the future (and has been added to
901 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
902 past, it affected all builds that used the bsd.*.mk files. The old
903 behavior was a bug, but people may have relied upon it. To get this
904 behavior back, you can .include /etc/src.conf from /etc/make.conf
905 (which is still global and isn't changed). This also changes the
906 behavior of incremental builds inside the tree of individual
907 directories. Set MAKESYSPATH to ".../share/mk" to do that.
908 Although this has survived make universe and some upgrade scenarios,
909 other upgrade scenarios may have broken. At least one form of
910 temporary breakage was fixed with MAKESYSPATH settings for buildworld
911 as well... In cases where MAKESYSPATH isn't working with this
912 setting, you'll need to set it to the full path to your tree.
914 One side effect of all this cleaning up is that bsd.compiler.mk
915 is no longer implicitly included by bsd.own.mk. If you wish to
916 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
920 The lindev device has been removed since /dev/full has been made a
921 standard device. __FreeBSD_version has been bumped.
924 The knob WITHOUT_VI was added to the base system, which controls
925 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
926 in order to reorder files share/termcap and didn't build ex(1) as a
927 build tool, so building/installing with WITH_VI is highly advised for
928 build hosts for older releases.
930 This issue has been fixed in stable/9 and stable/10 in r277022 and
931 r276991, respectively.
934 The YES_HESIOD knob has been removed. It has been obsolete for
935 a decade. Please move to using WITH_HESIOD instead or your builds
936 will silently lack HESIOD.
939 The uart(4) driver has been changed with respect to its handling
940 of the low-level console. Previously the uart(4) driver prevented
941 any process from changing the baudrate or the CLOCAL and HUPCL
942 control flags. By removing the restrictions, operators can make
943 changes to the serial console port without having to reboot.
944 However, when getty(8) is started on the serial device that is
945 associated with the low-level console, a misconfigured terminal
946 line in /etc/ttys will now have a real impact.
947 Before upgrading the kernel, make sure that /etc/ttys has the
948 serial console device configured as 3wire without baudrate to
949 preserve the previous behaviour. E.g:
950 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
953 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
954 to improve performance. To re-enable it, if needed, run rpcbind
955 with command line option -W.
958 Switched back to the GPL dtc compiler due to updates in the upstream
959 dts files not being supported by the BSDL dtc compiler. You will need
960 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
961 may result while building dtb files during a kernel build if you fail
962 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
965 Clang and llvm have been upgraded to 3.4 release.
968 The nve(4) driver has been removed. Please use the nfe(4) driver
969 for NVIDIA nForce MCP Ethernet adapters instead.
972 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
973 This could cause certain C++ applications using shared libraries built
974 against the previous version of libc++ to crash. The incompatibility
975 has now been fixed, but any C++ applications or shared libraries built
976 between r261283 and r261801 should be recompiled.
979 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
980 capability mode support. Please note that enabling the feature in
981 kernel is still highly recommended.
984 OpenSSH is now built with sandbox support, and will use sandbox as
985 the default privilege separation method. This requires Capsicum
986 capability mode support in kernel.
989 The libelf and libdwarf libraries have been updated to newer
990 versions from upstream. Shared library version numbers for
991 these two libraries were bumped. Any ports or binaries
992 requiring these two libraries should be recompiled.
993 __FreeBSD_version is bumped to 1100006.
996 If a Makefile in a tests/ directory was auto-generating a Kyuafile
997 instead of providing an explicit one, this would prevent such
998 Makefile from providing its own Kyuafile in the future during
999 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1000 intervention is needed to clean an objdir if you use NO_CLEAN:
1001 # find /usr/obj -name Kyuafile | xargs rm -f
1004 The behavior of gss_pseudo_random() for the krb5 mechanism
1005 has changed, for applications requesting a longer random string
1006 than produced by the underlying enctype's pseudo-random() function.
1007 In particular, the random string produced from a session key of
1008 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1009 be different at the 17th octet and later, after this change.
1010 The counter used in the PRF+ construction is now encoded as a
1011 big-endian integer in accordance with RFC 4402.
1012 __FreeBSD_version is bumped to 1100004.
1015 The WITHOUT_ATF build knob has been removed and its functionality
1016 has been subsumed into the more generic WITHOUT_TESTS. If you were
1017 using the former to disable the build of the ATF libraries, you
1018 should change your settings to use the latter.
1021 The default version of mtree is nmtree which is obtained from
1022 NetBSD. The output is generally the same, but may vary
1023 slightly. If you found you need identical output adding
1024 "-F freebsd9" to the command line should do the trick. For the
1025 time being, the old mtree is available as fmtree.
1028 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1029 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1030 1.1.4_8 and verify bsdyml not linked in, before running "make
1032 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1034 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1037 The stable/10 branch has been created in subversion from head
1041 The rc.d/jail script has been updated to support jail(8)
1042 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1043 for per-jail configuration are automatically converted to
1044 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1045 This is transparently backward compatible. See below about some
1046 incompatibilities and rc.conf(5) manual page for more details.
1048 These variables are now deprecated in favor of jail(8) configuration
1049 file. One can use "rc.d/jail config <jname>" command to generate
1050 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1051 running the jail(8) utility. The default pathname of the
1052 configuration file is /etc/jail.conf and can be specified by
1053 using $jail_conf or $jail_<jname>_conf variables.
1055 Please note that jail_devfs_ruleset accepts an integer at
1056 this moment. Please consider to rewrite the ruleset name
1060 BIND has been removed from the base system. If all you need
1061 is a local resolver, simply enable and start the local_unbound
1062 service instead. Otherwise, several versions of BIND are
1063 available in the ports tree. The dns/bind99 port is one example.
1065 With this change, nslookup(1) and dig(1) are no longer in the base
1066 system. Users should instead use host(1) and drill(1) which are
1067 in the base system. Alternatively, nslookup and dig can
1068 be obtained by installing the dns/bind-tools port.
1071 With the addition of unbound(8), a new unbound user is now
1072 required during installworld. "mergemaster -p" can be used to
1073 add the user prior to installworld, as documented in the handbook.
1076 OpenSSH is now built with DNSSEC support, and will by default
1077 silently trust signed SSHFP records. This can be controlled with
1078 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1079 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1082 The GNU Compiler Collection and C++ standard library (libstdc++)
1083 are no longer built by default on platforms where clang is the system
1084 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1085 options in src.conf.
1088 The PROCDESC kernel option is now part of the GENERIC kernel
1089 configuration and is required for the rwhod(8) to work.
1090 If you are using custom kernel configuration, you should include
1094 The API and ABI related to the Capsicum framework was modified
1095 in backward incompatible way. The userland libraries and programs
1096 have to be recompiled to work with the new kernel. This includes the
1097 following libraries and programs, but the whole buildworld is
1098 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1099 kdump, procstat, rwho, rwhod, uniq.
1102 AES-NI intrinsic support has been added to gcc. The AES-NI module
1103 has been updated to use this support. A new gcc is required to build
1104 the aesni module on both i386 and amd64.
1107 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1108 Thus "device padlock_rng" and "device rdrand_rng" should be
1109 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1112 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1113 enables just the iconv* functionality and is now on by default.
1114 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1115 compatibility. Set WITHOUT_ICONV to build the old way.
1116 If you have been using WITH_ICONV before, you will very likely
1117 need to turn on WITH_LIBICONV_COMPAT.
1120 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1121 Illumos origin, including ZFS. If you have INVARIANTS in your
1122 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1124 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1125 locks if WITNESS option was set. Because that generated a lot of
1126 witness(9) reports and all of them were believed to be false
1127 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1128 can be used to achieve the previous behavior.
1131 Timer values in IPv6 data structures now use time_uptime instead
1132 of time_second. Although this is not a user-visible functional
1133 change, userland utilities which directly use them---ndp(8),
1134 rtadvd(8), and rtsold(8) in the base system---need to be updated
1135 to r253970 or later.
1138 find -delete can now delete the pathnames given as arguments,
1139 instead of only files found below them or if the pathname did
1140 not contain any slashes. Formerly, the following error message
1143 find: -delete: <path>: relative path potentially not safe
1145 Deleting the pathnames given as arguments can be prevented
1146 without error messages using -mindepth 1 or by changing
1147 directory and passing "." as argument to find. This works in the
1148 old as well as the new version of find.
1151 Behavior of devfs rules path matching has been changed.
1152 Pattern is now always matched against fully qualified devfs
1153 path and slash characters must be explicitly matched by
1154 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1155 subdirectories must be reviewed.
1158 The default ARM ABI has changed to the ARM EABI. The old ABI is
1159 incompatible with the ARM EABI and all programs and modules will
1160 need to be rebuilt to work with a new kernel.
1162 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1164 NOTE: Support for the old ABI will be removed in the future and
1165 users are advised to upgrade.
1168 pkg_install has been disconnected from the build if you really need it
1169 you should add WITH_PKGTOOLS in your src.conf(5).
1172 Most of network statistics structures were changed to be able
1173 keep 64-bits counters. Thus all tools, that work with networking
1174 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1177 Fix a bug that allowed a tracing process (e.g. gdb) to write
1178 to a memory-mapped file in the traced process's address space
1179 even if neither the traced process nor the tracing process had
1180 write access to that file.
1183 CVS has been removed from the base system. An exact copy
1184 of the code is available from the devel/cvs port.
1187 Some people report the following error after the switch to bmake:
1189 make: illegal option -- J
1190 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1192 *** [buildworld] Error code 2
1194 this likely due to an old instance of make in
1195 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1196 which src/Makefile will use that blindly, if it exists, so if
1197 you see the above error:
1199 rm -rf `make -V MAKEPATH`
1204 Use bmake by default.
1205 Whereas before one could choose to build with bmake via
1206 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1207 make. The goal is to remove these knobs for 10-RELEASE.
1209 It is worth noting that bmake (like gmake) treats the command
1210 line as the unit of failure, rather than statements within the
1211 command line. Thus '(cd some/where && dosomething)' is safer
1212 than 'cd some/where; dosomething'. The '()' allows consistent
1213 behavior in parallel build.
1216 Fix a bug that allows NFS clients to issue READDIR on files.
1219 The WITHOUT_IDEA option has been removed because
1220 the IDEA patent expired.
1223 The sysctl which controls TRIM support under ZFS has been renamed
1224 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1228 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1229 rather than creating it's own in the temporary directory in
1230 order allow access to bootstrapped versions of tools such as
1231 install and mtree. When upgrading from version of FreeBSD where
1232 the install command does not support -l, you will need to
1233 install a new mergemaster command if mergemaster -p is required.
1234 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1238 Legacy ATA stack, disabled and replaced by new CAM-based one since
1239 FreeBSD 9.0, completely removed from the sources. Kernel modules
1240 atadisk and atapi*, user-level tools atacontrol and burncd are
1241 removed. Kernel option `options ATA_CAM` is now permanently enabled
1245 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1246 and socketpair(2). Software, in particular Kerberos, may
1247 automatically detect and use these during building. The resulting
1248 binaries will not work on older kernels.
1251 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1252 information, see the respective 20130304 entry).
1255 Recent commits to callout(9) changed the size of struct callout,
1256 so the KBI is probably heavily disturbed. Also, some functions
1257 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1258 by macros. Every kernel module using it won't load, so rebuild
1261 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1262 but does not initialize by default (because of the new CTL_DISABLE
1263 option) to save memory. To re-enable it, remove the CTL_DISABLE
1264 option from the kernel config file or set kern.cam.ctl.disable=0
1265 in /boot/loader.conf.
1268 The ctl device has been disabled in GENERIC for i386 and amd64.
1269 This was done due to the extra memory being allocated at system
1270 initialisation time by the ctl driver which was only used if
1271 a CAM target device was created. This makes a FreeBSD system
1272 unusable on 128MB or less of RAM.
1275 A new compression method (lz4) has been merged to -HEAD. Please
1276 refer to zpool-features(7) for more information.
1278 Please refer to the "ZFS notes" section of this file for information
1279 on upgrading boot ZFS pools.
1282 A BSD-licensed patch(1) variant has been added and is installed
1283 as bsdpatch, being the GNU version the default patch.
1284 To inverse the logic and use the BSD-licensed one as default,
1285 while having the GNU version installed as gnupatch, rebuild
1286 and install world with the WITH_BSD_PATCH knob set.
1289 Due to the use of the new -l option to install(1) during build
1290 and install, you must take care not to directly set the INSTALL
1291 make variable in your /etc/make.conf, /etc/src.conf, or on the
1292 command line. If you wish to use the -C flag for all installs
1293 you may be able to add INSTALL+=-C to /etc/make.conf or
1297 The install(1) option -M has changed meaning and now takes an
1298 argument that is a file or path to append logs to. In the
1299 unlikely event that -M was the last option on the command line
1300 and the command line contained at least two files and a target
1301 directory the first file will have logs appended to it. The -M
1302 option served little practical purpose in the last decade so its
1303 use is expected to be extremely rare.
1306 After switching to Clang as the default compiler some users of ZFS
1307 on i386 systems started to experience stack overflow kernel panics.
1308 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1311 GEOM_LABEL now mangles label names read from file system metadata.
1312 Mangling affect labels containing spaces, non-printable characters,
1313 '%' or '"'. Device names in /etc/fstab and other places may need to
1317 By default, only the 10 most recent kernel dumps will be saved. To
1318 restore the previous behaviour (no limit on the number of kernel dumps
1319 stored in the dump directory) add the following line to /etc/rc.conf:
1324 With the addition of auditdistd(8), a new auditdistd user is now
1325 required during installworld. "mergemaster -p" can be used to
1326 add the user prior to installworld, as documented in the handbook.
1329 The sin6_scope_id member variable in struct sockaddr_in6 is now
1330 filled by the kernel before passing the structure to the userland via
1331 sysctl or routing socket. This means the KAME-specific embedded scope
1332 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1333 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1334 __FreeBSD_version is bumped to 1000025.
1337 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1338 This means that the world and kernel will be compiled with clang
1339 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1340 and /usr/bin/cpp. To disable this behavior and revert to building
1341 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1342 of current may need to bootstrap WITHOUT_CLANG first if the clang
1343 build fails (its compatibility window doesn't extend to the 9 stable
1347 The IPFIREWALL_FORWARD kernel option has been removed. Its
1348 functionality now turned on by default.
1351 The ZERO_COPY_SOCKET kernel option has been removed and
1352 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1353 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1354 mechanism which is not safe and may result in kernel crashes.
1355 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1356 driver supports disposeable external page sized mbuf storage.
1357 Proper replacements for both zero-copy mechanisms are under
1358 consideration and will eventually lead to complete removal
1359 of the two kernel options.
1362 The IPv4 network stack has been converted to network byte
1363 order. The following modules need to be recompiled together
1364 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1365 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1368 Support for non-MPSAFE filesystems was removed from VFS. The
1369 VFS_VERSION was bumped, all filesystem modules shall be
1373 All the non-MPSAFE filesystems have been disconnected from
1374 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1375 portalfs, smbfs, xfs.
1378 The interface cloning API and ABI has changed. The following
1379 modules need to be recompiled together with kernel:
1380 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1381 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1382 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1385 The sdhci driver was split in two parts: sdhci (generic SD Host
1386 Controller logic) and sdhci_pci (actual hardware driver).
1387 No kernel config modifications are required, but if you
1388 load sdhc as a module you must switch to sdhci_pci instead.
1391 Import the FUSE kernel and userland support into base system.
1394 The GNU sort(1) program has been removed since the BSD-licensed
1395 sort(1) has been the default for quite some time and no serious
1396 problems have been reported. The corresponding WITH_GNU_SORT
1400 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1401 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1405 The net80211(4) ABI has been changed to allow for improved driver
1406 PS-POLL and power-save support. All wireless drivers need to be
1407 recompiled to work with the new kernel.
1410 The random(4) support for the VIA hardware random number
1411 generator (`PADLOCK') is no longer enabled unconditionally.
1412 Add the padlock_rng device in the custom kernel config if
1413 needed. The GENERIC kernels on i386 and amd64 do include the
1414 device, so the change only affects the custom kernel
1418 The pf(4) packet filter ABI has been changed. pfctl(8) and
1419 snmp_pf module need to be recompiled to work with new kernel.
1422 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1423 to -HEAD. Pools that have empty_bpobj in active state can not be
1424 imported read-write with ZFS implementations that do not support
1425 this feature. For more information read the zpool-features(5)
1429 The sparc64 ZFS loader has been changed to no longer try to auto-
1430 detect ZFS providers based on diskN aliases but now requires these
1431 to be explicitly listed in the OFW boot-device environment variable.
1434 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1435 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1436 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1439 The following sysctls and tunables have been renamed for consistency
1440 with other variables:
1441 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1442 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1445 The sort utility has been replaced with BSD sort. For now, GNU sort
1446 is also available as "gnusort" or the default can be set back to
1447 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1448 installed as "bsdsort".
1451 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1452 Starting with this version the old system of ZFS pool versioning
1453 is superseded by "feature flags". This concept enables forward
1454 compatibility against certain future changes in functionality of ZFS
1455 pools. The first read-only compatible "feature flag" for ZFS pools
1456 is named "com.delphix:async_destroy". For more information
1457 read the new zpool-features(5) manual page.
1458 Please refer to the "ZFS notes" section of this file for information
1459 on upgrading boot ZFS pools.
1462 The malloc(3) implementation embedded in libc now uses sources imported
1463 as contrib/jemalloc. The most disruptive API change is to
1464 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1465 delete it prior to installworld, and optionally re-create it using the
1466 new format after rebooting. See malloc.conf(5) for details
1467 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1471 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1472 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1473 now spelled mips. This is to aid compatibility with third-party
1474 software that expects this naming scheme in uname(3). Little-endian
1475 settings are unchanged. If you are updating a big-endian mips64 machine
1476 from before this change, you may need to set MACHINE_ARCH=mips64 in
1477 your environment before the new build system will recognize your machine.
1480 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1484 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1485 nullfs(5) did not pass through all behaviours to the underlying layer,
1486 as a result if we bound to a socket on the lower layer we could connect
1487 only to the lower path; if we bound to the upper layer we could connect
1488 only to the upper path. The new behavior is one can connect to both the
1489 lower and the upper paths regardless what layer path one binds to.
1492 The getifaddrs upgrade path broken with 20111215 has been restored.
1493 If you have upgraded in between 20111215 and 20120209 you need to
1494 recompile libc again with your kernel. You still need to recompile
1495 world to be able to configure CARP but this restriction already
1496 comes from 20111215.
1499 The set_rcvar() function has been removed from /etc/rc.subr. All
1500 base and ports rc.d scripts have been updated, so if you have a
1501 port installed with a script in /usr/local/etc/rc.d you can either
1502 hand-edit the rcvar= line, or reinstall the port.
1504 An easy way to handle the mass-update of /etc/rc.d:
1505 rm /etc/rc.d/* && mergemaster -i
1508 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1509 on the current CPU and prevents other threads from running.
1510 This behavior can be reverted using the kern.stop_scheduler_on_panic
1512 The new behavior can be incompatible with kern.sync_on_panic.
1515 The carp(4) facility has been changed significantly. Configuration
1516 of the CARP protocol via ifconfig(8) has changed, as well as format
1517 of CARP events submitted to devd(8) has changed. See manual pages
1518 for more information. The arpbalance feature of carp(4) is currently
1519 not supported anymore.
1521 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1522 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1523 need to be recompiled.
1526 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1530 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1531 explicitely support non-MPSAFE filesystems.
1532 It is on by default for all supported platform at this present
1536 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1537 i386 and pc98 GENERIC kernel configuration files.
1540 sysinstall has been removed
1543 The stable/9 branch created in subversion. This corresponds to the
1544 RELENG_9 branch in CVS.
1550 Avoid using make -j when upgrading. While generally safe, there are
1551 sometimes problems using -j to upgrade. If your upgrade fails with
1552 -j, please try again without -j. From time to time in the past there
1553 have been problems using -j with buildworld and/or installworld. This
1554 is especially true when upgrading between "distant" versions (eg one
1555 that cross a major release boundary or several minor releases, or when
1556 several months have passed on the -current branch).
1558 Sometimes, obscure build problems are the result of environment
1559 poisoning. This can happen because the make utility reads its
1560 environment when searching for values for global variables. To run
1561 your build attempts in an "environmental clean room", prefix all make
1562 commands with 'env -i '. See the env(1) manual page for more details.
1564 When upgrading from one major version to another it is generally best
1565 to upgrade to the latest code in the currently installed branch first,
1566 then do an upgrade to the new branch. This is the best-tested upgrade
1567 path, and has the highest probability of being successful. Please try
1568 this approach before reporting problems with a major version upgrade.
1570 When upgrading a live system, having a root shell around before
1571 installing anything can help undo problems. Not having a root shell
1572 around can lead to problems if pam has changed too much from your
1573 starting point to allow continued authentication after the upgrade.
1575 This file should be read as a log of events. When a later event changes
1576 information of a prior event, the prior event should not be deleted.
1577 Instead, a pointer to the entry with the new information should be
1578 placed in the old entry. Readers of this file should also sanity check
1579 older entries before relying on them blindly. Authors of new entries
1580 should write them with this in mind.
1584 When upgrading the boot ZFS pool to a new version, always follow
1587 1.) recompile and reinstall the ZFS boot loader and boot block
1588 (this is part of "make buildworld" and "make installworld")
1590 2.) update the ZFS boot block on your boot drive
1592 The following example updates the ZFS boot block on the first
1593 partition (freebsd-boot) of a GPT partitioned drive ada0:
1594 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1596 Non-boot pools do not need these updates.
1600 If you are updating from a prior version of FreeBSD (even one just
1601 a few days old), you should follow this procedure. It is the most
1602 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1604 make kernel-toolchain
1605 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1606 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1608 To test a kernel once
1609 ---------------------
1610 If you just want to boot a kernel once (because you are not sure
1611 if it works, or if you want to boot a known bad kernel to provide
1612 debugging information) run
1613 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1614 nextboot -k testkernel
1616 To just build a kernel when you know that it won't mess you up
1617 --------------------------------------------------------------
1618 This assumes you are already running a CURRENT system. Replace
1619 ${arch} with the architecture of your machine (e.g. "i386",
1620 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1622 cd src/sys/${arch}/conf
1623 config KERNEL_NAME_HERE
1624 cd ../compile/KERNEL_NAME_HERE
1629 If this fails, go to the "To build a kernel" section.
1631 To rebuild everything and install it on the current system.
1632 -----------------------------------------------------------
1633 # Note: sometimes if you are running current you gotta do more than
1634 # is listed here if you are upgrading from a really old current.
1636 <make sure you have good level 0 dumps>
1638 make kernel KERNCONF=YOUR_KERNEL_HERE
1640 <reboot in single user> [3]
1647 To cross-install current onto a separate partition
1648 --------------------------------------------------
1649 # In this approach we use a separate partition to hold
1650 # current's root, 'usr', and 'var' directories. A partition
1651 # holding "/", "/usr" and "/var" should be about 2GB in
1654 <make sure you have good level 0 dumps>
1657 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1658 <maybe newfs current's root partition>
1659 <mount current's root partition on directory ${CURRENT_ROOT}>
1660 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1661 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1662 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1663 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1664 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1665 <reboot into current>
1666 <do a "native" rebuild/install as described in the previous section>
1667 <maybe install compatibility libraries from ports/misc/compat*>
1671 To upgrade in-place from stable to current
1672 ----------------------------------------------
1673 <make sure you have good level 0 dumps>
1675 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1677 <reboot in single user> [3]
1684 Make sure that you've read the UPDATING file to understand the
1685 tweaks to various things you need. At this point in the life
1686 cycle of current, things change often and you are on your own
1687 to cope. The defaults can also change, so please read ALL of
1688 the UPDATING entries.
1690 Also, if you are tracking -current, you must be subscribed to
1691 freebsd-current@freebsd.org. Make sure that before you update
1692 your sources that you have read and understood all the recent
1693 messages there. If in doubt, please track -stable which has
1694 much fewer pitfalls.
1696 [1] If you have third party modules, such as vmware, you
1697 should disable them at this point so they don't crash your
1700 [3] From the bootblocks, boot -s, and then do
1705 adjkerntz -i # if CMOS is wall time
1706 Also, when doing a major release upgrade, it is required that
1707 you boot into single user mode to do the installworld.
1709 [4] Note: This step is non-optional. Failure to do this step
1710 can result in a significant reduction in the functionality of the
1711 system. Attempting to do it by hand is not recommended and those
1712 that pursue this avenue should read this file carefully, as well
1713 as the archives of freebsd-current and freebsd-hackers mailing lists
1714 for potential gotchas. The -U option is also useful to consider.
1715 See mergemaster(8) for more information.
1717 [5] Usually this step is a noop. However, from time to time
1718 you may need to do this if you get unknown user in the following
1719 step. It never hurts to do it all the time. You may need to
1720 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1721 install) after the buildworld before this step if you last updated
1722 from current before 20130425 or from -stable before 20130430.
1724 [6] This only deletes old files and directories. Old libraries
1725 can be deleted by "make delete-old-libs", but you have to make
1726 sure that no program is using those libraries anymore.
1728 [8] In order to have a kernel that can run the 4.x binaries needed to
1729 do an installworld, you must include the COMPAT_FREEBSD4 option in
1730 your kernel. Failure to do so may leave you with a system that is
1731 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1732 required to run the 5.x binaries on more recent kernels. And so on
1733 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1735 Make sure that you merge any new devices from GENERIC since the
1736 last time you updated your kernel config file.
1738 [9] When checking out sources, you must include the -P flag to have
1739 cvs prune empty directories.
1741 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1742 "?=" instead of the "=" assignment operator, so that buildworld can
1743 override the CPUTYPE if it needs to.
1745 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1746 not on the command line, or in /etc/make.conf. buildworld will
1747 warn if it is improperly defined.
1750 This file contains a list, in reverse chronological order, of major
1751 breakages in tracking -current. It is not guaranteed to be a complete
1752 list of such breakages, and only contains entries since September 23, 2011.
1753 If you need to see UPDATING entries from before that date, you will need
1754 to fetch an UPDATING file from an older FreeBSD release.
1756 Copyright information:
1758 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1760 Redistribution, publication, translation and use, with or without
1761 modification, in full or in part, in any form or format of this
1762 document are permitted without further permission from the author.
1764 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1765 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1766 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1767 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1768 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1769 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1770 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1771 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1772 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1773 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1774 POSSIBILITY OF SUCH DAMAGE.
1776 Contact Warner Losh if you have any questions about your use of