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 zfsloader's functionality has now been folded into loader.
21 zfsloader is no longer necesasary once you've updated your
22 boot blocks. For a transition period, we will install a
23 hardlink for zfsloader to loader to allow a smooth transition
24 until the boot blocks can be updated (hard link because old
25 zfs boot blocks don't understand symlinks).
28 Lualoader has been merged to facilitate testing on this branch. It's
29 purely opt-in for now by building WITH_LOADER_LUA and WITHOUT_FORTH in
30 /etc/src.conf, but co-existance will come shortly. Booting is a complex
31 environment and test coverage for Lua-enabled loaders has been thin, so
32 it would be prudent to assume it might not work and make provisions for
36 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
37 7.0.1. Please see the 20141231 entry below for information about
38 prerequisites and upgrading, if you are not already using clang 3.5.0
42 r342562 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
43 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
44 servers that have vfs.nfsd.nfs_privport set will only allow mounts
45 from clients using a reserved port#. Since both the FreeBSD and Linux
46 NFSv4 clients use reserved port#s by default, this should not affect
50 The '%I' format in the kern.corefile sysctl limits the number of
51 core files that a process can generate to the number stored in the
52 debug.ncores sysctl. The '%I' format is replaced by the single digit
53 index. Previously, if all indexes were taken the kernel would overwrite
54 only a core file with the highest index in a filename.
55 Currently the system will create a new core file if there is a free
56 index or if all slots are taken it will overwrite the oldest one.
59 WITH_OFED option now only enables the build for the OFED libraries
60 and some fundamental client utilities. OpenSM and rest of the
61 debugging tools are enabled by WITH_OFED_EXTRA build switch.
62 WITH_OFED is turned on by default on amd64.
65 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
66 6.0.1. Please see the 20141231 entry below for information about
67 prerequisites and upgrading, if you are not already using clang 3.5.0
71 The releng/11.2 branch has been created from stable/11@r334458.
74 The tz database (tzdb) has been updated to 2018e. This version more
75 correctly models time stamps in time zones with negative DST such as
76 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
77 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
78 time zone abbreviations and the tm_isdst flag.
81 The use of RSS hash from the network card aka flowid has been
82 disabled by default for lagg(4) as it's currently incompatible with
83 the lacp and loadbalance protocols.
85 This can be re-enabled by setting the following in loader.conf:
86 net.link.lagg.default_use_flowid="1"
89 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
90 6.0.0. Please see the 20141231 entry below for information about
91 prerequisites and upgrading, if you are not already using clang 3.5.0
95 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
96 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
97 to WITH/OUT_LOADER_GELI.
100 The geli password typed at boot is now hidden. To restore the previous
101 behavior, see geli(8) for configuration options.
103 The SW_WATCHDOG option is no longer necessary to enable the
104 hardclock-based software watchdog if no hardware watchdog is
105 configured. As before, SW_WATCHDOG will cause the software
106 watchdog to be enabled even if a hardware watchdog is configured.
109 lint(1) binaries and library are no longer built by default. To
110 enable building them, define WITH_LINT in src.conf. If you are using
111 a FreeBSD 12 or later system to build 11-stable, you may need to
112 install a lint(1) binary to use WITH_LINT.
115 When building multiple kernels using KERNCONF, non-existent KERNCONF
116 files will produce an error and buildkernel will fail. Previously
117 missing KERNCONF files silently failed giving no indication as to
118 why, only to subsequently discover during installkernel that the
119 desired kernel was never built in the first place.
122 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
123 Please see the 20141231 entry below for information about prerequisites
124 and upgrading, if you are not already using clang 3.5.0 or higher.
127 Since the switch to GPT disk labels, fsck for UFS/FFS has been
128 unable to automatically find alternate superblocks. As of r322806,
129 the information needed to find alternate superblocks has been
130 moved to the end of the area reserved for the boot block.
131 Filesystems created with a newfs of this vintage or later
132 will create the recovery information. If you have a filesystem
133 created prior to this change and wish to have a recovery block
134 created for your filesystem, you can do so by running fsck in
135 forground mode (i.e., do not use the -p or -y options). As it
136 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
137 to which you should answer yes.
140 The releng/11.1 branch has been created from stable/11@r320475.
143 arm64 builds now use the base system LLD 4.0.0 linker by default,
144 instead of requiring that the aarch64-binutils port or package be
145 installed. To continue using aarch64-binutils, set
146 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
149 The ctl.ko module no longer implements the iSCSI target frontend:
150 cfiscsi.ko does instead.
152 If building cfiscsi.ko as a kernel module, the module can be loaded
153 via one of the following methods:
154 - `cfiscsi_load="YES"` in loader.conf(5).
155 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
156 - ctladm(8)/ctld(8), when compiled with iSCSI support
157 (`WITH_ISCSI=yes` in src.conf(5))
159 Please see cfiscsi(4) for more details.
162 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
163 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
164 same source (previously, the dependency of mmcsd.ko on mmc.ko was
165 missing, but mmcsd.ko now will refuse to load if it is incompatible
169 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
170 use any explicitly assigned loopback address available in the jail
171 instead of using the first assigned address of the jail.
174 As of r316810 for ipfilter, keep frags is no longer assumed when
175 keep state is specified in a rule. r316810 aligns ipfilter with
176 documentation in man pages separating keep frags from keep state.
177 This allows keep state to specified without forcing keep frags
178 and allows keep frags to be specified independently of keep state.
179 To maintain previous behaviour, also specify keep frags with
180 keep state (as documented in ipf.conf.5).
183 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
184 Please see the 20141231 entry below for information about prerequisites
185 and upgrading, if you are not already using clang 3.5.0 or higher.
188 The code that provides support for ZFS .zfs/ directory functionality
189 has been reimplemented. It's not possible now to create a snapshot
190 by mkdir under .zfs/snapshot/. That should be the only user visible
194 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
195 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
196 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
197 and now NAT-T is supported by default. Security associations now use
198 the single namespace for SPI allocation, so if you use several manually
199 configured security associations with the same SPI, this configuration
203 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
204 Please see the 20141231 entry below for information about prerequisites
205 and upgrading, if you are not already using clang 3.5.0 or higher.
208 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
209 Please see the 20141231 entry below for information about prerequisites
210 and upgrading, if you are not already using clang 3.5.0 or higher.
213 The layout of the pmap structure has changed for powerpc to put the pmap
214 statistics at the front for all CPU variations. libkvm(3) and all tools
215 that link against it need to be recompiled.
218 isl(4) and cyapa(4) drivers now require a new driver,
219 chromebook_platform(4), to work properly on Chromebook-class hardware.
220 On other types of hardware the drivers may need to be configured using
221 device hints. Please see the corresponding manual pages for details.
224 Relocatable object files with the extension of .So have been renamed
225 to use an extension of .pico instead. The purpose of this change is
226 to avoid a name clash with shared libraries on case-insensitive file
227 systems. On those file systems, foo.So is the same file as foo.so.
230 The releng/11.0 branch has been created from stable/11@r303970.
233 The stable/11 branch has been created from head@r302406.
236 The libc stub for the pipe(2) system call has been replaced with
237 a wrapper that calls the pipe2(2) system call and the pipe(2)
238 system call is now only implemented by the kernels that include
239 "options COMPAT_FREEBSD10" in their config file (this is the
240 default). Users should ensure that this option is enabled in
241 their kernel or upgrade userspace to r302092 before upgrading their
245 CAM will now strip leading spaces from SCSI disks' serial numbers.
246 This will effect users who create UFS filesystems on SCSI disks using
247 those disk's diskid device nodes. For example, if /etc/fstab
248 previously contained a line like
249 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
250 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
251 transforms like gmirror may also be affected. ZFS users should
255 The bitstring(3) API has been updated with new functionality and
256 improved performance. But it is binary-incompatible with the old API.
257 Objects built with the new headers may not be linked against objects
258 built with the old headers.
261 The brk and sbrk functions have been removed from libc on arm64.
262 Binutils from ports has been updated to not link to these
263 functions and should be updated to the latest version before
264 installing a new libc.
267 The armv6 port now defaults to hard float ABI. Limited support
268 for running both hardfloat and soft float on the same system
269 is available using the libraries installed with -DWITH_LIBSOFT.
270 This has only been tested as an upgrade path for installworld
271 and packages may fail or need manual intervention to run. New
272 packages will be needed.
274 To update an existing self-hosted armv6hf system, you must add
275 TARGET_ARCH=armv6 on the make command line for both the build
276 and the install steps.
279 Kernel modules compiled outside of a kernel build now default to
280 installing to /boot/modules instead of /boot/kernel. Many kernel
281 modules built this way (such as those in ports) already overrode
282 KMODDIR explicitly to install into /boot/modules. However,
283 manually building and installing a module from /sys/modules will
284 now install to /boot/modules instead of /boot/kernel.
287 The CAM I/O scheduler has been committed to the kernel. There should be
288 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
289 list of known rogues that claim support for this but actually corrupt
290 data is believed to be complete, be on the lookout for data
291 corruption. The known rogue list is believed to be complete:
293 o Crucial MX100, M550 drives with MU01 firmware.
294 o Micron M510 and M550 drives with MU01 firmware.
295 o Micron M500 prior to MU07 firmware
296 o Samsung 830, 840, and 850 all firmwares
297 o FCCT M500 all firmwares
299 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
300 with working NCQ TRIM. For Micron branded drives, see your sales rep for
301 updated firmware. Black listed drives will work correctly because these
302 drives work correctly so long as no NCQ TRIMs are sent to them. Given
303 this list is the same as found in Linux, it's believed there are no
304 other rogues in the market place. All other models from the above
307 To be safe, if you are at all concerned, you can quirk each of your
308 drives to prevent NCQ from being sent by setting:
309 kern.cam.ada.X.quirks="0x2"
310 in loader.conf. If the drive requires the 4k sector quirk, set the
314 The FAST_DEPEND build option has been removed and its functionality is
315 now the one true way. The old mkdep(1) style of 'make depend' has
316 been removed. See 20160311 for further details.
319 Resource range types have grown from unsigned long to uintmax_t. All
320 drivers, and anything using libdevinfo, need to be recompiled.
323 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
324 builds. It no longer runs mkdep(1) during 'make depend', and the
325 'make depend' stage can safely be skipped now as it is auto ran
326 when building 'make all' and will generate all SRCS and DPSRCS before
327 building anything else. Dependencies are gathered at compile time with
328 -MF flags kept in separate .depend files per object file. Users should
329 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
333 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
334 kernel modules. Therefore, if you load any kernel modules at boot time,
335 please install the boot loaders after you install the kernel, but before
339 make kernel KERNCONF=YOUR_KERNEL_HERE
340 make -C sys/boot install
341 <reboot in single user>
343 Then follow the usual steps, described in the General Notes section,
347 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
348 see the 20141231 entry below for information about prerequisites and
349 upgrading, if you are not already using clang 3.5.0 or higher.
352 The AIO subsystem is now a standard part of the kernel. The
353 VFS_AIO kernel option and aio.ko kernel module have been removed.
354 Due to stability concerns, asynchronous I/O requests are only
355 permitted on sockets and raw disks by default. To enable
356 asynchronous I/O requests on all file types, set the
357 vfs.aio.enable_unsafe sysctl to a non-zero value.
360 The ELF object manipulation tool objcopy is now provided by the
361 ELF Tool Chain project rather than by GNU binutils. It should be a
362 drop-in replacement, with the addition of arm64 support. The
363 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
364 to obtain the GNU version if necessary.
367 Building ZFS pools on top of zvols is prohibited by default. That
368 feature has never worked safely; it's always been prone to deadlocks.
369 Using a zvol as the backing store for a VM guest's virtual disk will
370 still work, even if the guest is using ZFS. Legacy behavior can be
371 restored by setting vfs.zfs.vol.recursive=1.
374 The NONE and HPN patches has been removed from OpenSSH. They are
375 still available in the security/openssh-portable port.
378 With the addition of ypldap(8), a new _ypldap user is now required
379 during installworld. "mergemaster -p" can be used to add the user
380 prior to installworld, as documented in the handbook.
383 The tftp loader (pxeboot) now uses the option root-path directive. As a
384 consequence it no longer looks for a pxeboot.4th file on the tftp
385 server. Instead it uses the regular /boot infrastructure as with the
389 The code to start recording plug and play data into the modules has
390 been committed. While the old tools will properly build a new kernel,
391 a number of warnings about "unknown metadata record 4" will be produced
392 for an older kldxref. To avoid such warnings, make sure to rebuild
393 the kernel toolchain (or world). Make sure that you have r292078 or
394 later when trying to build 292077 or later before rebuilding.
397 Debug data files are now built by default with 'make buildworld' and
398 installed with 'make installworld'. This facilitates debugging but
399 requires more disk space both during the build and for the installed
400 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
404 r291527 changed the internal interface between the nfsd.ko and
405 nfscommon.ko modules. As such, they must both be upgraded to-gether.
406 __FreeBSD_version has been bumped because of this.
409 Add support for unicode collation strings leads to a change of
410 order of files listed by ls(1) for example. To get back to the old
411 behaviour, set LC_COLLATE environment variable to "C".
413 Databases administrators will need to reindex their databases given
414 collation results will be different.
416 Due to a bug in install(1) it is recommended to remove the ancient
417 locales before running make installworld.
419 rm -rf /usr/share/locale/*
422 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
423 libcrypto.so.7 or libssl.so.7 must be recompiled.
426 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
427 Kernel modules isp_2400_multi and isp_2500_multi were removed and
428 should be replaced with isp_2400 and isp_2500 modules respectively.
431 The build previously allowed using 'make -n' to not recurse into
432 sub-directories while showing what commands would be executed, and
433 'make -n -n' to recursively show commands. Now 'make -n' will recurse
434 and 'make -N' will not.
437 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
438 and etcupdate will now use this file. A custom sendmail.cf is now
439 updated via this mechanism rather than via installworld. If you had
440 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
441 want to remove the exclusion or change it to "always install".
442 /etc/mail/sendmail.cf is now managed the same way regardless of
443 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
444 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
447 Compatibility shims for legacy ATA device names have been removed.
448 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
449 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
450 environment variables, /dev/ad* and /dev/ar* symbolic links.
453 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
454 Please see the 20141231 entry below for information about prerequisites
455 and upgrading, if you are not already using clang 3.5.0 or higher.
458 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
459 and renamed from .symbols to .debug. This reduces the size requirements
460 on the boot partition or file system and provides consistency with
461 userland debug files.
463 When using the supported kernel installation method the
464 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
465 as is done with /boot/kernel.
467 Developers wishing to maintain the historical behavior of installing
468 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
471 The wireless drivers had undergone changes that remove the 'parent
472 interface' from the ifconfig -l output. The rc.d network scripts
473 used to check presence of a parent interface in the list, so old
474 scripts would fail to start wireless networking. Thus, etcupdate(3)
475 or mergemaster(8) run is required after kernel update, to update your
476 rc.d scripts in /etc.
479 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
480 These configurations are now automatically interpreted as
481 'scrub fragment reassemble'.
484 Kernel-loadable modules for the random(4) device are back. To use
485 them, the kernel must have
488 options RANDOM_LOADABLE
490 kldload(8) can then be used to load random_fortuna.ko
491 or random_yarrow.ko. Please note that due to the indirect
492 function calls that the loadable modules need to provide,
493 the build-in variants will be slightly more efficient.
495 The random(4) kernel option RANDOM_DUMMY has been retired due to
496 unpopularity. It was not all that useful anyway.
499 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
500 Control over building the ELF Tool Chain tools is now provided by
501 the WITHOUT_TOOLCHAIN knob.
504 The polarity of Pulse Per Second (PPS) capture events with the
505 uart(4) driver has been corrected. Prior to this change the PPS
506 "assert" event corresponded to the trailing edge of a positive PPS
507 pulse and the "clear" event was the leading edge of the next pulse.
509 As the width of a PPS pulse in a typical GPS receiver is on the
510 order of 1 millisecond, most users will not notice any significant
511 difference with this change.
513 Anyone who has compensated for the historical polarity reversal by
514 configuring a negative offset equal to the pulse width will need to
515 remove that workaround.
518 The default group assigned to /dev/dri entries has been changed
519 from 'wheel' to 'video' with the id of '44'. If you want to have
520 access to the dri devices please add yourself to the video group
523 # pw groupmod video -m $USER
526 The menu.rc and loader.rc files will now be replaced during
527 upgrades. Please migrate local changes to menu.rc.local and
528 loader.rc.local instead.
531 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
532 strings and strip have been removed. The src.conf(5) knob
533 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
536 As ZFS requires more kernel stack pages than is the default on some
537 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
538 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
540 Please consider using 'options KSTACK_PAGES=X' where X is greater
541 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
544 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
545 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
546 default, i.e., they will not contain "::". For example, instead
547 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
548 to have a more specific match, such as different map entries for
549 IPv6:0:0 vs IPv6:0. This change requires that configuration
550 data (including maps, files, classes, custom ruleset, etc.) must
551 use the same format, so make certain such configuration data is
552 upgrading. As a very simple check search for patterns like
553 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
554 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
555 the cf option UseCompressedIPv6Addresses.
558 The default kernel entropy-processing algorithm is now
559 Fortuna, replacing Yarrow.
561 Assuming you have 'device random' in your kernel config
562 file, the configurations allow a kernel option to override
563 this default. You may choose *ONE* of:
565 options RANDOM_YARROW # Legacy /dev/random algorithm.
566 options RANDOM_DUMMY # Blocking-only driver.
568 If you have neither, you get Fortuna. For most people,
569 read no further, Fortuna will give a /dev/random that works
570 like it always used to, and the difference will be irrelevant.
572 If you remove 'device random', you get *NO* kernel-processed
573 entropy at all. This may be acceptable to folks building
574 embedded systems, but has complications. Carry on reading,
575 and it is assumed you know what you need.
577 *PLEASE* read random(4) and random(9) if you are in the
578 habit of tweaking kernel configs, and/or if you are a member
579 of the embedded community, wanting specific and not-usual
580 behaviour from your security subsystems.
582 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
583 random', you will NOT have a functioning /dev/random, and
584 many cryptographic features will not work, including SSH.
585 You may also find strange behaviour from the random(3) set
586 of library functions, in particular sranddev(3), srandomdev(3)
587 and arc4random(3). The reason for this is that the KERN_ARND
588 sysctl only returns entropy if it thinks it has some to
589 share, and with RANDOM_DUMMY or no 'device random' this
593 An additional fix for the issue described in the 20150614 sendmail
594 entry below has been been committed in revision 284717.
597 FreeBSD's old make (fmake) has been removed from the system. It is
598 available as the devel/fmake port or via pkg install fmake.
601 The fix for the issue described in the 20150614 sendmail entry
602 below has been been committed in revision 284436. The work
603 around described in that entry is no longer needed unless the
604 default setting is overridden by a confDH_PARAMETERS configuration
605 setting of '5' or pointing to a 512 bit DH parameter file.
608 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
609 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
610 and devel/kyua to version 0.20+ and adjust any calling code to work
611 with Kyuafile and kyua.
614 The import of openssl to address the FreeBSD-SA-15:10.openssl
615 security advisory includes a change which rejects handshakes
616 with DH parameters below 768 bits. sendmail releases prior
617 to 8.15.2 (not yet released), defaulted to a 512 bit
618 DH parameter setting for client connections. To work around
619 this interoperability, sendmail can be configured to use a
620 2048 bit DH parameter by:
622 1. Edit /etc/mail/`hostname`.mc
623 2. If a setting for confDH_PARAMETERS does not exist or
624 exists and is set to a string beginning with '5',
626 3. If a setting for confDH_PARAMETERS exists and is set to
627 a file path, create a new file with:
628 openssl dhparam -out /path/to/file 2048
629 4. Rebuild the .cf file:
630 cd /etc/mail/; make; make install
632 cd /etc/mail/; make restart
634 A sendmail patch is coming, at which time this file will be
638 Generation of legacy formatted entries have been disabled by default
639 in pwd_mkdb(8), as all base system consumers of the legacy formatted
640 entries were converted to use the new format by default when the new,
641 machine independent format have been added and supported since FreeBSD
644 Please see the pwd_mkdb(8) manual page for further details.
647 Clang and llvm have been upgraded to 3.6.1 release. Please see the
648 20141231 entry below for information about prerequisites and upgrading,
649 if you are not already using 3.5.0 or higher.
652 TI platform code switched to using vendor DTS files and this update
653 may break existing systems running on Beaglebone, Beaglebone Black,
656 - dtb files should be regenerated/reinstalled. Filenames are the
657 same but content is different now
658 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
659 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
660 addressing scheme is now pin 25 on /dev/gpioc3.
661 - Pandaboard: /etc/ttys should be updated, serial console device is
662 now /dev/ttyu2, not /dev/ttyu0
665 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
666 If you need the GNU extension from groff soelim(1), install groff
667 from package: pkg install groff, or via ports: textproc/groff.
670 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
671 defined in symlink(7); previously symlinks were silently ignored.
674 The const qualifier has been removed from iconv(3) to comply with
675 POSIX. The ports tree is aware of this from r384038 onwards.
678 Libraries specified by LIBADD in Makefiles must have a corresponding
679 DPADD_<lib> variable to ensure correct dependencies. This is now
680 enforced in src.libnames.mk.
683 From legacy ata(4) driver was removed support for SATA controllers
684 supported by more functional drivers ahci(4), siis(4) and mvs(4).
685 Kernel modules ataahci and ataadaptec were removed completely,
686 replaced by ahci and mvs modules respectively.
689 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
690 the 20141231 entry below for information about prerequisites and
691 upgrading, if you are not already using 3.5.0 or higher.
694 The 32-bit PowerPC kernel has been changed to a position-independent
695 executable. This can only be booted with a version of loader(8)
696 newer than January 31, 2015, so make sure to update both world and
697 kernel before rebooting.
700 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
701 but before r278950, the RNG was not seeded properly. Immediately
702 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
703 ssh keys or openssl keys) that were generated w/ a kernel from that
704 range. This does not affect programs that directly used /dev/random
705 or /dev/urandom. All userland uses of arc4random(3) are affected.
708 The autofs(4) ABI was changed in order to restore binary compatibility
709 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
713 The powerpc64 kernel has been changed to a position-independent
714 executable. This can only be booted with a new version of loader(8),
715 so make sure to update both world and kernel before rebooting.
718 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
719 only release, no new features have been added. Please see the 20141231
720 entry below for information about prerequisites and upgrading, if you
721 are not already using 3.5.0.
724 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
725 taken from the ELF Tool Chain project rather than GNU binutils. They
726 should be drop-in replacements, with the addition of arm64 support.
727 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
728 binutils tools, if necessary. See 20150805 for updated information.
731 The default Unbound configuration now enables remote control
732 using a local socket. Users who have already enabled the
733 local_unbound service should regenerate their configuration
734 by running "service local_unbound setup" as root.
737 The GNU texinfo and GNU info pages have been removed.
738 To be able to view GNU info pages please install texinfo from ports.
741 Clang, llvm and lldb have been upgraded to 3.5.0 release.
743 As of this release, a prerequisite for building clang, llvm and lldb is
744 a C++11 capable compiler and C++11 standard library. This means that to
745 be able to successfully build the cross-tools stage of buildworld, with
746 clang as the bootstrap compiler, your system compiler or cross compiler
747 should either be clang 3.3 or later, or gcc 4.8 or later, and your
748 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
751 On any standard FreeBSD 10.x or 11.x installation, where clang and
752 libc++ are on by default (that is, on x86 or arm), this should work out
755 On 9.x installations where clang is enabled by default, e.g. on x86 and
756 powerpc, libc++ will not be enabled by default, so libc++ should be
757 built (with clang) and installed first. If both clang and libc++ are
758 missing, build clang first, then use it to build libc++.
760 On 8.x and earlier installations, upgrade to 9.x first, and then follow
761 the instructions for 9.x above.
763 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
764 default, and do not build clang.
766 Many embedded systems are resource constrained, and will not be able to
767 build clang in a reasonable time, or in some cases at all. In those
768 cases, cross building bootable systems on amd64 is a workaround.
770 This new version of clang introduces a number of new warnings, of which
771 the following are most likely to appear:
775 This warns in two cases, for both C and C++:
776 * When the code is trying to take the absolute value of an unsigned
777 quantity, which is effectively a no-op, and almost never what was
778 intended. The code should be fixed, if at all possible. If you are
779 sure that the unsigned quantity can be safely cast to signed, without
780 loss of information or undefined behavior, you can add an explicit
781 cast, or disable the warning.
783 * When the code is trying to take an absolute value, but the called
784 abs() variant is for the wrong type, which can lead to truncation.
785 If you want to disable the warning instead of fixing the code, please
786 make sure that truncation will not occur, or it might lead to unwanted
789 -Wtautological-undefined-compare and
790 -Wundefined-bool-conversion
792 These warn when C++ code is trying to compare 'this' against NULL, while
793 'this' should never be NULL in well-defined C++ code. However, there is
794 some legacy (pre C++11) code out there, which actively abuses this
795 feature, which was less strictly defined in previous C++ versions.
797 Squid and openjdk do this, for example. The warning can be turned off
798 for C++98 and earlier, but compiling the code in C++11 mode might result
799 in unexpected behavior; for example, the parts of the program that are
800 unreachable could be optimized away.
803 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
804 kernel sources have been removed. The .h files remain, since some
805 utilities include them. This will need to be fixed later.
806 If "mount -t oldnfs ..." is attempted, it will fail.
807 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
808 the utilities will report errors.
811 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
812 directories to top level SUBDIR variable when their parent
813 directory is included in LOCAL_DIRS. Users with build systems with
814 such hierarchies and without SUBDIR entries in the parent
815 directory Makefiles should add them or add the directories to
819 faith(4) and faithd(8) have been removed from the base system. Faith
820 has been obsolete for a very long time.
823 vt(4), the new console driver, is enabled by default. It brings
824 support for Unicode and double-width characters, as well as
825 support for UEFI and integration with the KMS kernel video
828 You may need to update your console settings in /etc/rc.conf,
829 most probably the keymap. During boot, /etc/rc.d/syscons will
830 indicate what you need to do.
832 vt(4) still has issues and lacks some features compared to
833 syscons(4). See the wiki for up-to-date information:
834 https://wiki.freebsd.org/Newcons
836 If you want to keep using syscons(4), you can do so by adding
837 the following line to /boot/loader.conf:
841 pjdfstest has been integrated into kyua as an opt-in test suite.
842 Please see share/doc/pjdfstest/README for more details on how to
846 gperf has been removed from the base system for architectures
847 that use clang. Ports that require gperf will obtain it from the
851 pjdfstest has been moved from tools/regression/pjdfstest to
855 At svn r271982, The default linux compat kernel ABI has been adjusted
856 to 2.6.18 in support of the linux-c6 compat ports infrastructure
857 update. If you wish to continue using the linux-f10 compat ports,
858 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
859 encouraged to update their linux-compat packages to linux-c6 during
860 their next update cycle.
863 The ofwfb driver, used to provide a graphics console on PowerPC when
864 using vt(4), no longer allows mmap() of all physical memory. This
865 will prevent Xorg on PowerPC with some ATI graphics cards from
866 initializing properly unless x11-servers/xorg-server is updated to
870 The xdev targets have been converted to using TARGET and
871 TARGET_ARCH instead of XDEV and XDEV_ARCH.
874 The default unbound configuration has been modified to address
875 issues with reverse lookups on networks that use private
876 address ranges. If you use the local_unbound service, run
877 "service local_unbound setup" as root to regenerate your
878 configuration, then "service local_unbound reload" to load the
882 The GNU texinfo and GNU info pages are not built and installed
883 anymore, WITH_INFO knob has been added to allow to built and install
885 UPDATE: see 20150102 entry on texinfo's removal
888 The GNU readline library is now an INTERNALLIB - that is, it is
889 statically linked into consumers (GDB and variants) in the base
890 system, and the shared library is no longer installed. The
891 devel/readline port is available for third party software that
895 The Itanium architecture (ia64) has been removed from the list of
896 known architectures. This is the first step in the removal of the
900 Commit r268115 has added NFSv4.1 server support, merged from
901 projects/nfsv4.1-server. Since this includes changes to the
902 internal interfaces between the NFS related modules, a full
903 build of the kernel and modules will be necessary.
904 __FreeBSD_version has been bumped.
907 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
908 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
909 which differs from the behaviour controlled by this knob.)
912 Maximal length of the serial number in CTL was increased from 16 to
913 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
914 and ctld, need to be rebuilt to work with a new kernel.
917 The libatf-c and libatf-c++ major versions were downgraded to 0 and
918 1 respectively to match the upstream numbers. They were out of
919 sync because, when they were originally added to FreeBSD, the
920 upstream versions were not respected. These libraries are private
921 and not yet built by default, so renumbering them should be a
922 non-issue. However, unclean source trees will yield broken test
923 programs once the operator executes "make delete-old-libs" after a
926 Additionally, the atf-sh binary was made private by moving it into
927 /usr/libexec/. Already-built shell test programs will keep the
928 path to the old binary so they will break after "make delete-old"
931 If you are using WITH_TESTS=yes (not the default), wipe the object
932 tree and rebuild from scratch to prevent spurious test failures.
933 This is only needed once: the misnumbered libraries and misplaced
934 binaries have been added to OptionalObsoleteFiles.inc so they will
935 be removed during a clean upgrade.
938 Clang and llvm have been upgraded to 3.4.1 release.
941 We bogusly installed src.opts.mk in /usr/share/mk. This file should
942 be removed to avoid issues in the future (and has been added to
946 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
947 past, it affected all builds that used the bsd.*.mk files. The old
948 behavior was a bug, but people may have relied upon it. To get this
949 behavior back, you can .include /etc/src.conf from /etc/make.conf
950 (which is still global and isn't changed). This also changes the
951 behavior of incremental builds inside the tree of individual
952 directories. Set MAKESYSPATH to ".../share/mk" to do that.
953 Although this has survived make universe and some upgrade scenarios,
954 other upgrade scenarios may have broken. At least one form of
955 temporary breakage was fixed with MAKESYSPATH settings for buildworld
956 as well... In cases where MAKESYSPATH isn't working with this
957 setting, you'll need to set it to the full path to your tree.
959 One side effect of all this cleaning up is that bsd.compiler.mk
960 is no longer implicitly included by bsd.own.mk. If you wish to
961 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
965 The lindev device has been removed since /dev/full has been made a
966 standard device. __FreeBSD_version has been bumped.
969 The knob WITHOUT_VI was added to the base system, which controls
970 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
971 in order to reorder files share/termcap and didn't build ex(1) as a
972 build tool, so building/installing with WITH_VI is highly advised for
973 build hosts for older releases.
975 This issue has been fixed in stable/9 and stable/10 in r277022 and
976 r276991, respectively.
979 The YES_HESIOD knob has been removed. It has been obsolete for
980 a decade. Please move to using WITH_HESIOD instead or your builds
981 will silently lack HESIOD.
984 The uart(4) driver has been changed with respect to its handling
985 of the low-level console. Previously the uart(4) driver prevented
986 any process from changing the baudrate or the CLOCAL and HUPCL
987 control flags. By removing the restrictions, operators can make
988 changes to the serial console port without having to reboot.
989 However, when getty(8) is started on the serial device that is
990 associated with the low-level console, a misconfigured terminal
991 line in /etc/ttys will now have a real impact.
992 Before upgrading the kernel, make sure that /etc/ttys has the
993 serial console device configured as 3wire without baudrate to
994 preserve the previous behaviour. E.g:
995 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
998 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
999 to improve performance. To re-enable it, if needed, run rpcbind
1000 with command line option -W.
1003 Switched back to the GPL dtc compiler due to updates in the upstream
1004 dts files not being supported by the BSDL dtc compiler. You will need
1005 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1006 may result while building dtb files during a kernel build if you fail
1007 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1010 Clang and llvm have been upgraded to 3.4 release.
1013 The nve(4) driver has been removed. Please use the nfe(4) driver
1014 for NVIDIA nForce MCP Ethernet adapters instead.
1017 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1018 This could cause certain C++ applications using shared libraries built
1019 against the previous version of libc++ to crash. The incompatibility
1020 has now been fixed, but any C++ applications or shared libraries built
1021 between r261283 and r261801 should be recompiled.
1024 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1025 capability mode support. Please note that enabling the feature in
1026 kernel is still highly recommended.
1029 OpenSSH is now built with sandbox support, and will use sandbox as
1030 the default privilege separation method. This requires Capsicum
1031 capability mode support in kernel.
1034 The libelf and libdwarf libraries have been updated to newer
1035 versions from upstream. Shared library version numbers for
1036 these two libraries were bumped. Any ports or binaries
1037 requiring these two libraries should be recompiled.
1038 __FreeBSD_version is bumped to 1100006.
1041 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1042 instead of providing an explicit one, this would prevent such
1043 Makefile from providing its own Kyuafile in the future during
1044 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1045 intervention is needed to clean an objdir if you use NO_CLEAN:
1046 # find /usr/obj -name Kyuafile | xargs rm -f
1049 The behavior of gss_pseudo_random() for the krb5 mechanism
1050 has changed, for applications requesting a longer random string
1051 than produced by the underlying enctype's pseudo-random() function.
1052 In particular, the random string produced from a session key of
1053 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1054 be different at the 17th octet and later, after this change.
1055 The counter used in the PRF+ construction is now encoded as a
1056 big-endian integer in accordance with RFC 4402.
1057 __FreeBSD_version is bumped to 1100004.
1060 The WITHOUT_ATF build knob has been removed and its functionality
1061 has been subsumed into the more generic WITHOUT_TESTS. If you were
1062 using the former to disable the build of the ATF libraries, you
1063 should change your settings to use the latter.
1066 The default version of mtree is nmtree which is obtained from
1067 NetBSD. The output is generally the same, but may vary
1068 slightly. If you found you need identical output adding
1069 "-F freebsd9" to the command line should do the trick. For the
1070 time being, the old mtree is available as fmtree.
1073 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1074 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1075 1.1.4_8 and verify bsdyml not linked in, before running "make
1077 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1079 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1082 The stable/10 branch has been created in subversion from head
1086 The rc.d/jail script has been updated to support jail(8)
1087 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1088 for per-jail configuration are automatically converted to
1089 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1090 This is transparently backward compatible. See below about some
1091 incompatibilities and rc.conf(5) manual page for more details.
1093 These variables are now deprecated in favor of jail(8) configuration
1094 file. One can use "rc.d/jail config <jname>" command to generate
1095 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1096 running the jail(8) utility. The default pathname of the
1097 configuration file is /etc/jail.conf and can be specified by
1098 using $jail_conf or $jail_<jname>_conf variables.
1100 Please note that jail_devfs_ruleset accepts an integer at
1101 this moment. Please consider to rewrite the ruleset name
1105 BIND has been removed from the base system. If all you need
1106 is a local resolver, simply enable and start the local_unbound
1107 service instead. Otherwise, several versions of BIND are
1108 available in the ports tree. The dns/bind99 port is one example.
1110 With this change, nslookup(1) and dig(1) are no longer in the base
1111 system. Users should instead use host(1) and drill(1) which are
1112 in the base system. Alternatively, nslookup and dig can
1113 be obtained by installing the dns/bind-tools port.
1116 With the addition of unbound(8), a new unbound user is now
1117 required during installworld. "mergemaster -p" can be used to
1118 add the user prior to installworld, as documented in the handbook.
1121 OpenSSH is now built with DNSSEC support, and will by default
1122 silently trust signed SSHFP records. This can be controlled with
1123 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1124 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1127 The GNU Compiler Collection and C++ standard library (libstdc++)
1128 are no longer built by default on platforms where clang is the system
1129 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1130 options in src.conf.
1133 The PROCDESC kernel option is now part of the GENERIC kernel
1134 configuration and is required for the rwhod(8) to work.
1135 If you are using custom kernel configuration, you should include
1139 The API and ABI related to the Capsicum framework was modified
1140 in backward incompatible way. The userland libraries and programs
1141 have to be recompiled to work with the new kernel. This includes the
1142 following libraries and programs, but the whole buildworld is
1143 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1144 kdump, procstat, rwho, rwhod, uniq.
1147 AES-NI intrinsic support has been added to gcc. The AES-NI module
1148 has been updated to use this support. A new gcc is required to build
1149 the aesni module on both i386 and amd64.
1152 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1153 Thus "device padlock_rng" and "device rdrand_rng" should be
1154 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1157 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1158 enables just the iconv* functionality and is now on by default.
1159 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1160 compatibility. Set WITHOUT_ICONV to build the old way.
1161 If you have been using WITH_ICONV before, you will very likely
1162 need to turn on WITH_LIBICONV_COMPAT.
1165 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1166 Illumos origin, including ZFS. If you have INVARIANTS in your
1167 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1169 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1170 locks if WITNESS option was set. Because that generated a lot of
1171 witness(9) reports and all of them were believed to be false
1172 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1173 can be used to achieve the previous behavior.
1176 Timer values in IPv6 data structures now use time_uptime instead
1177 of time_second. Although this is not a user-visible functional
1178 change, userland utilities which directly use them---ndp(8),
1179 rtadvd(8), and rtsold(8) in the base system---need to be updated
1180 to r253970 or later.
1183 find -delete can now delete the pathnames given as arguments,
1184 instead of only files found below them or if the pathname did
1185 not contain any slashes. Formerly, the following error message
1188 find: -delete: <path>: relative path potentially not safe
1190 Deleting the pathnames given as arguments can be prevented
1191 without error messages using -mindepth 1 or by changing
1192 directory and passing "." as argument to find. This works in the
1193 old as well as the new version of find.
1196 Behavior of devfs rules path matching has been changed.
1197 Pattern is now always matched against fully qualified devfs
1198 path and slash characters must be explicitly matched by
1199 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1200 subdirectories must be reviewed.
1203 The default ARM ABI has changed to the ARM EABI. The old ABI is
1204 incompatible with the ARM EABI and all programs and modules will
1205 need to be rebuilt to work with a new kernel.
1207 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1209 NOTE: Support for the old ABI will be removed in the future and
1210 users are advised to upgrade.
1213 pkg_install has been disconnected from the build if you really need it
1214 you should add WITH_PKGTOOLS in your src.conf(5).
1217 Most of network statistics structures were changed to be able
1218 keep 64-bits counters. Thus all tools, that work with networking
1219 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1222 Fix a bug that allowed a tracing process (e.g. gdb) to write
1223 to a memory-mapped file in the traced process's address space
1224 even if neither the traced process nor the tracing process had
1225 write access to that file.
1228 CVS has been removed from the base system. An exact copy
1229 of the code is available from the devel/cvs port.
1232 Some people report the following error after the switch to bmake:
1234 make: illegal option -- J
1235 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1237 *** [buildworld] Error code 2
1239 this likely due to an old instance of make in
1240 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1241 which src/Makefile will use that blindly, if it exists, so if
1242 you see the above error:
1244 rm -rf `make -V MAKEPATH`
1249 Use bmake by default.
1250 Whereas before one could choose to build with bmake via
1251 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1252 make. The goal is to remove these knobs for 10-RELEASE.
1254 It is worth noting that bmake (like gmake) treats the command
1255 line as the unit of failure, rather than statements within the
1256 command line. Thus '(cd some/where && dosomething)' is safer
1257 than 'cd some/where; dosomething'. The '()' allows consistent
1258 behavior in parallel build.
1261 Fix a bug that allows NFS clients to issue READDIR on files.
1264 The WITHOUT_IDEA option has been removed because
1265 the IDEA patent expired.
1268 The sysctl which controls TRIM support under ZFS has been renamed
1269 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1273 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1274 rather than creating it's own in the temporary directory in
1275 order allow access to bootstrapped versions of tools such as
1276 install and mtree. When upgrading from version of FreeBSD where
1277 the install command does not support -l, you will need to
1278 install a new mergemaster command if mergemaster -p is required.
1279 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1283 Legacy ATA stack, disabled and replaced by new CAM-based one since
1284 FreeBSD 9.0, completely removed from the sources. Kernel modules
1285 atadisk and atapi*, user-level tools atacontrol and burncd are
1286 removed. Kernel option `options ATA_CAM` is now permanently enabled
1290 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1291 and socketpair(2). Software, in particular Kerberos, may
1292 automatically detect and use these during building. The resulting
1293 binaries will not work on older kernels.
1296 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1297 information, see the respective 20130304 entry).
1300 Recent commits to callout(9) changed the size of struct callout,
1301 so the KBI is probably heavily disturbed. Also, some functions
1302 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1303 by macros. Every kernel module using it won't load, so rebuild
1306 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1307 but does not initialize by default (because of the new CTL_DISABLE
1308 option) to save memory. To re-enable it, remove the CTL_DISABLE
1309 option from the kernel config file or set kern.cam.ctl.disable=0
1310 in /boot/loader.conf.
1313 The ctl device has been disabled in GENERIC for i386 and amd64.
1314 This was done due to the extra memory being allocated at system
1315 initialisation time by the ctl driver which was only used if
1316 a CAM target device was created. This makes a FreeBSD system
1317 unusable on 128MB or less of RAM.
1320 A new compression method (lz4) has been merged to -HEAD. Please
1321 refer to zpool-features(7) for more information.
1323 Please refer to the "ZFS notes" section of this file for information
1324 on upgrading boot ZFS pools.
1327 A BSD-licensed patch(1) variant has been added and is installed
1328 as bsdpatch, being the GNU version the default patch.
1329 To inverse the logic and use the BSD-licensed one as default,
1330 while having the GNU version installed as gnupatch, rebuild
1331 and install world with the WITH_BSD_PATCH knob set.
1334 Due to the use of the new -l option to install(1) during build
1335 and install, you must take care not to directly set the INSTALL
1336 make variable in your /etc/make.conf, /etc/src.conf, or on the
1337 command line. If you wish to use the -C flag for all installs
1338 you may be able to add INSTALL+=-C to /etc/make.conf or
1342 The install(1) option -M has changed meaning and now takes an
1343 argument that is a file or path to append logs to. In the
1344 unlikely event that -M was the last option on the command line
1345 and the command line contained at least two files and a target
1346 directory the first file will have logs appended to it. The -M
1347 option served little practical purpose in the last decade so its
1348 use is expected to be extremely rare.
1351 After switching to Clang as the default compiler some users of ZFS
1352 on i386 systems started to experience stack overflow kernel panics.
1353 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1356 GEOM_LABEL now mangles label names read from file system metadata.
1357 Mangling affect labels containing spaces, non-printable characters,
1358 '%' or '"'. Device names in /etc/fstab and other places may need to
1362 By default, only the 10 most recent kernel dumps will be saved. To
1363 restore the previous behaviour (no limit on the number of kernel dumps
1364 stored in the dump directory) add the following line to /etc/rc.conf:
1369 With the addition of auditdistd(8), a new auditdistd user is now
1370 required during installworld. "mergemaster -p" can be used to
1371 add the user prior to installworld, as documented in the handbook.
1374 The sin6_scope_id member variable in struct sockaddr_in6 is now
1375 filled by the kernel before passing the structure to the userland via
1376 sysctl or routing socket. This means the KAME-specific embedded scope
1377 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1378 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1379 __FreeBSD_version is bumped to 1000025.
1382 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1383 This means that the world and kernel will be compiled with clang
1384 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1385 and /usr/bin/cpp. To disable this behavior and revert to building
1386 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1387 of current may need to bootstrap WITHOUT_CLANG first if the clang
1388 build fails (its compatibility window doesn't extend to the 9 stable
1392 The IPFIREWALL_FORWARD kernel option has been removed. Its
1393 functionality now turned on by default.
1396 The ZERO_COPY_SOCKET kernel option has been removed and
1397 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1398 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1399 mechanism which is not safe and may result in kernel crashes.
1400 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1401 driver supports disposeable external page sized mbuf storage.
1402 Proper replacements for both zero-copy mechanisms are under
1403 consideration and will eventually lead to complete removal
1404 of the two kernel options.
1407 The IPv4 network stack has been converted to network byte
1408 order. The following modules need to be recompiled together
1409 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1410 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1413 Support for non-MPSAFE filesystems was removed from VFS. The
1414 VFS_VERSION was bumped, all filesystem modules shall be
1418 All the non-MPSAFE filesystems have been disconnected from
1419 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1420 portalfs, smbfs, xfs.
1423 The interface cloning API and ABI has changed. The following
1424 modules need to be recompiled together with kernel:
1425 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1426 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1427 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1430 The sdhci driver was split in two parts: sdhci (generic SD Host
1431 Controller logic) and sdhci_pci (actual hardware driver).
1432 No kernel config modifications are required, but if you
1433 load sdhc as a module you must switch to sdhci_pci instead.
1436 Import the FUSE kernel and userland support into base system.
1439 The GNU sort(1) program has been removed since the BSD-licensed
1440 sort(1) has been the default for quite some time and no serious
1441 problems have been reported. The corresponding WITH_GNU_SORT
1445 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1446 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1450 The net80211(4) ABI has been changed to allow for improved driver
1451 PS-POLL and power-save support. All wireless drivers need to be
1452 recompiled to work with the new kernel.
1455 The random(4) support for the VIA hardware random number
1456 generator (`PADLOCK') is no longer enabled unconditionally.
1457 Add the padlock_rng device in the custom kernel config if
1458 needed. The GENERIC kernels on i386 and amd64 do include the
1459 device, so the change only affects the custom kernel
1463 The pf(4) packet filter ABI has been changed. pfctl(8) and
1464 snmp_pf module need to be recompiled to work with new kernel.
1467 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1468 to -HEAD. Pools that have empty_bpobj in active state can not be
1469 imported read-write with ZFS implementations that do not support
1470 this feature. For more information read the zpool-features(5)
1474 The sparc64 ZFS loader has been changed to no longer try to auto-
1475 detect ZFS providers based on diskN aliases but now requires these
1476 to be explicitly listed in the OFW boot-device environment variable.
1479 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1480 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1481 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1484 The following sysctls and tunables have been renamed for consistency
1485 with other variables:
1486 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1487 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1490 The sort utility has been replaced with BSD sort. For now, GNU sort
1491 is also available as "gnusort" or the default can be set back to
1492 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1493 installed as "bsdsort".
1496 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1497 Starting with this version the old system of ZFS pool versioning
1498 is superseded by "feature flags". This concept enables forward
1499 compatibility against certain future changes in functionality of ZFS
1500 pools. The first read-only compatible "feature flag" for ZFS pools
1501 is named "com.delphix:async_destroy". For more information
1502 read the new zpool-features(5) manual page.
1503 Please refer to the "ZFS notes" section of this file for information
1504 on upgrading boot ZFS pools.
1507 The malloc(3) implementation embedded in libc now uses sources imported
1508 as contrib/jemalloc. The most disruptive API change is to
1509 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1510 delete it prior to installworld, and optionally re-create it using the
1511 new format after rebooting. See malloc.conf(5) for details
1512 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1516 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1517 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1518 now spelled mips. This is to aid compatibility with third-party
1519 software that expects this naming scheme in uname(3). Little-endian
1520 settings are unchanged. If you are updating a big-endian mips64 machine
1521 from before this change, you may need to set MACHINE_ARCH=mips64 in
1522 your environment before the new build system will recognize your machine.
1525 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1529 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1530 nullfs(5) did not pass through all behaviours to the underlying layer,
1531 as a result if we bound to a socket on the lower layer we could connect
1532 only to the lower path; if we bound to the upper layer we could connect
1533 only to the upper path. The new behavior is one can connect to both the
1534 lower and the upper paths regardless what layer path one binds to.
1537 The getifaddrs upgrade path broken with 20111215 has been restored.
1538 If you have upgraded in between 20111215 and 20120209 you need to
1539 recompile libc again with your kernel. You still need to recompile
1540 world to be able to configure CARP but this restriction already
1541 comes from 20111215.
1544 The set_rcvar() function has been removed from /etc/rc.subr. All
1545 base and ports rc.d scripts have been updated, so if you have a
1546 port installed with a script in /usr/local/etc/rc.d you can either
1547 hand-edit the rcvar= line, or reinstall the port.
1549 An easy way to handle the mass-update of /etc/rc.d:
1550 rm /etc/rc.d/* && mergemaster -i
1553 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1554 on the current CPU and prevents other threads from running.
1555 This behavior can be reverted using the kern.stop_scheduler_on_panic
1557 The new behavior can be incompatible with kern.sync_on_panic.
1560 The carp(4) facility has been changed significantly. Configuration
1561 of the CARP protocol via ifconfig(8) has changed, as well as format
1562 of CARP events submitted to devd(8) has changed. See manual pages
1563 for more information. The arpbalance feature of carp(4) is currently
1564 not supported anymore.
1566 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1567 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1568 need to be recompiled.
1571 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1575 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1576 explicitely support non-MPSAFE filesystems.
1577 It is on by default for all supported platform at this present
1581 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1582 i386 and pc98 GENERIC kernel configuration files.
1585 sysinstall has been removed
1588 The stable/9 branch created in subversion. This corresponds to the
1589 RELENG_9 branch in CVS.
1595 Avoid using make -j when upgrading. While generally safe, there are
1596 sometimes problems using -j to upgrade. If your upgrade fails with
1597 -j, please try again without -j. From time to time in the past there
1598 have been problems using -j with buildworld and/or installworld. This
1599 is especially true when upgrading between "distant" versions (eg one
1600 that cross a major release boundary or several minor releases, or when
1601 several months have passed on the -current branch).
1603 Sometimes, obscure build problems are the result of environment
1604 poisoning. This can happen because the make utility reads its
1605 environment when searching for values for global variables. To run
1606 your build attempts in an "environmental clean room", prefix all make
1607 commands with 'env -i '. See the env(1) manual page for more details.
1609 When upgrading from one major version to another it is generally best
1610 to upgrade to the latest code in the currently installed branch first,
1611 then do an upgrade to the new branch. This is the best-tested upgrade
1612 path, and has the highest probability of being successful. Please try
1613 this approach before reporting problems with a major version upgrade.
1615 When upgrading a live system, having a root shell around before
1616 installing anything can help undo problems. Not having a root shell
1617 around can lead to problems if pam has changed too much from your
1618 starting point to allow continued authentication after the upgrade.
1620 This file should be read as a log of events. When a later event changes
1621 information of a prior event, the prior event should not be deleted.
1622 Instead, a pointer to the entry with the new information should be
1623 placed in the old entry. Readers of this file should also sanity check
1624 older entries before relying on them blindly. Authors of new entries
1625 should write them with this in mind.
1629 When upgrading the boot ZFS pool to a new version, always follow
1632 1.) recompile and reinstall the ZFS boot loader and boot block
1633 (this is part of "make buildworld" and "make installworld")
1635 2.) update the ZFS boot block on your boot drive
1637 The following example updates the ZFS boot block on the first
1638 partition (freebsd-boot) of a GPT partitioned drive ada0:
1639 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1641 Non-boot pools do not need these updates.
1645 If you are updating from a prior version of FreeBSD (even one just
1646 a few days old), you should follow this procedure. It is the most
1647 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1649 make kernel-toolchain
1650 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1651 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1653 To test a kernel once
1654 ---------------------
1655 If you just want to boot a kernel once (because you are not sure
1656 if it works, or if you want to boot a known bad kernel to provide
1657 debugging information) run
1658 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1659 nextboot -k testkernel
1661 To just build a kernel when you know that it won't mess you up
1662 --------------------------------------------------------------
1663 This assumes you are already running a CURRENT system. Replace
1664 ${arch} with the architecture of your machine (e.g. "i386",
1665 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1667 cd src/sys/${arch}/conf
1668 config KERNEL_NAME_HERE
1669 cd ../compile/KERNEL_NAME_HERE
1674 If this fails, go to the "To build a kernel" section.
1676 To rebuild everything and install it on the current system.
1677 -----------------------------------------------------------
1678 # Note: sometimes if you are running current you gotta do more than
1679 # is listed here if you are upgrading from a really old current.
1681 <make sure you have good level 0 dumps>
1683 make kernel KERNCONF=YOUR_KERNEL_HERE
1685 <reboot in single user> [3]
1692 To cross-install current onto a separate partition
1693 --------------------------------------------------
1694 # In this approach we use a separate partition to hold
1695 # current's root, 'usr', and 'var' directories. A partition
1696 # holding "/", "/usr" and "/var" should be about 2GB in
1699 <make sure you have good level 0 dumps>
1702 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1703 <maybe newfs current's root partition>
1704 <mount current's root partition on directory ${CURRENT_ROOT}>
1705 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1706 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1707 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1708 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1709 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1710 <reboot into current>
1711 <do a "native" rebuild/install as described in the previous section>
1712 <maybe install compatibility libraries from ports/misc/compat*>
1716 To upgrade in-place from stable to current
1717 ----------------------------------------------
1718 <make sure you have good level 0 dumps>
1720 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1722 <reboot in single user> [3]
1729 Make sure that you've read the UPDATING file to understand the
1730 tweaks to various things you need. At this point in the life
1731 cycle of current, things change often and you are on your own
1732 to cope. The defaults can also change, so please read ALL of
1733 the UPDATING entries.
1735 Also, if you are tracking -current, you must be subscribed to
1736 freebsd-current@freebsd.org. Make sure that before you update
1737 your sources that you have read and understood all the recent
1738 messages there. If in doubt, please track -stable which has
1739 much fewer pitfalls.
1741 [1] If you have third party modules, such as vmware, you
1742 should disable them at this point so they don't crash your
1745 [3] From the bootblocks, boot -s, and then do
1750 adjkerntz -i # if CMOS is wall time
1751 Also, when doing a major release upgrade, it is required that
1752 you boot into single user mode to do the installworld.
1754 [4] Note: This step is non-optional. Failure to do this step
1755 can result in a significant reduction in the functionality of the
1756 system. Attempting to do it by hand is not recommended and those
1757 that pursue this avenue should read this file carefully, as well
1758 as the archives of freebsd-current and freebsd-hackers mailing lists
1759 for potential gotchas. The -U option is also useful to consider.
1760 See mergemaster(8) for more information.
1762 [5] Usually this step is a noop. However, from time to time
1763 you may need to do this if you get unknown user in the following
1764 step. It never hurts to do it all the time. You may need to
1765 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1766 install) after the buildworld before this step if you last updated
1767 from current before 20130425 or from -stable before 20130430.
1769 [6] This only deletes old files and directories. Old libraries
1770 can be deleted by "make delete-old-libs", but you have to make
1771 sure that no program is using those libraries anymore.
1773 [8] In order to have a kernel that can run the 4.x binaries needed to
1774 do an installworld, you must include the COMPAT_FREEBSD4 option in
1775 your kernel. Failure to do so may leave you with a system that is
1776 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1777 required to run the 5.x binaries on more recent kernels. And so on
1778 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1780 Make sure that you merge any new devices from GENERIC since the
1781 last time you updated your kernel config file.
1783 [9] When checking out sources, you must include the -P flag to have
1784 cvs prune empty directories.
1786 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1787 "?=" instead of the "=" assignment operator, so that buildworld can
1788 override the CPUTYPE if it needs to.
1790 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1791 not on the command line, or in /etc/make.conf. buildworld will
1792 warn if it is improperly defined.
1795 This file contains a list, in reverse chronological order, of major
1796 breakages in tracking -current. It is not guaranteed to be a complete
1797 list of such breakages, and only contains entries since September 23, 2011.
1798 If you need to see UPDATING entries from before that date, you will need
1799 to fetch an UPDATING file from an older FreeBSD release.
1801 Copyright information:
1803 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1805 Redistribution, publication, translation and use, with or without
1806 modification, in full or in part, in any form or format of this
1807 document are permitted without further permission from the author.
1809 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1810 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1811 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1812 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1813 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1814 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1815 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1816 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1817 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1818 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1819 POSSIBILITY OF SUCH DAMAGE.
1821 Contact Warner Losh if you have any questions about your use of