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