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 http://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.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
20 FreeBSD 12.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 ****************************** SPECIAL WARNING: ******************************
37 Due to a bug in some versions of clang that's very hard to workaround in
38 the upgrade process, to upgrade to -current you must first upgrade
39 either stable/9 after r286035 or stable/10 after r286033 (including
40 10.3-RELEASE) or current after r286007 (including stable/11 and
41 11.0-RELEASE). These revisions post-date the 10.2 and 9.3 releases, so
42 you'll need to take the unusual step of upgrading to the tip of the
43 stable branch before moving to 11 or -current via a source upgrade.
44 stable/11 and 11.0-RELEASE have working newer compiler. This differs
45 from the historical situation where one could upgrade from anywhere on
46 the last couple of stable branches, so be careful.
48 If you're running a hybrid system on 9.x or 10.x with an updated clang
49 compiler or are using an supported external toolchain, the build system
50 will allow the upgrade. Otherwise it will print a reminder.
52 ****************************** SPECIAL WARNING: ******************************
55 The NATM framework including the en(4), fatm(4), hatm(4), and
56 patm(4) devices has been removed. Consumers should plan a
57 migration before the end-of-life date for FreeBSD 11.
60 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
61 diff has not been implemented, if those are needed a newer version of
62 GNU diff is available via the diffutils package under the gdiff name.
65 As of r316810 for ipfilter, keep frags is no longer assumed when
66 keep state is specified in a rule. r316810 aligns ipfilter with
67 documentation in man pages separating keep frags from keep state.
68 This allows keep state to be specified without forcing keep frags
69 and allows keep frags to be specified independently of keep state.
70 To maintain previous behaviour, also specify keep frags with
71 keep state (as documented in ipf.conf.5).
74 arm64 builds now use the base system LLD 4.0.0 linker by default,
75 instead of requiring that the aarch64-binutils port or package be
76 installed. To continue using aarch64-binutils, set
77 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
80 The UDP optimization in entry 20160818 that added the sysctl
81 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
82 packets will no longer be treated as L3 broadcast packets.
85 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
86 use any explicitly assigned loopback address available in the jail
87 instead of using the first assigned address of the jail.
90 The ctl.ko module no longer implements the iSCSI target frontend:
91 cfiscsi.ko does instead.
93 If building cfiscsi.ko as a kernel module, the module can be loaded
94 via one of the following methods:
95 - `cfiscsi_load="YES"` in loader.conf(5).
96 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
97 - ctladm(8)/ctld(8), when compiled with iSCSI support
98 (`WITH_ISCSI=yes` in src.conf(5))
100 Please see cfiscsi(4) for more details.
103 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
104 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
105 same source (previously, the dependency of mmcsd.ko on mmc.ko was
106 missing, but mmcsd.ko now will refuse to load if it is incompatible
110 The syntax of ipfw(8) named states was changed to avoid ambiguity.
111 If you have used named states in the firewall rules, you need to modify
112 them after installworld and before rebooting. Now named states must
113 be prefixed with colon.
116 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
117 removed as the userland we provide cannot use them. The KMS version
118 (sys/dev/drm2) supports the same hardware.
121 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
122 Please see the 20141231 entry below for information about prerequisites
123 and upgrading, if you are not already using clang 3.5.0 or higher.
126 The code that provides support for ZFS .zfs/ directory functionality
127 has been reimplemented. It's not possible now to create a snapshot
128 by mkdir under .zfs/snapshot/. That should be the only user visible
132 EISA bus support has been removed. The WITH_EISA option is no longer
136 MCA bus support has been removed.
139 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
140 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
143 The EM_MULTIQUEUE kernel configuration option is deprecated now that
144 the em(4) driver conforms to iflib specifications.
147 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
148 IFLIB. If you have a custom kernel configuration that excludes em(4)
149 but you use igb(4), you need to re-add em(4) to your custom configuration.
152 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
153 Please see the 20141231 entry below for information about prerequisites
154 and upgrading, if you are not already using clang 3.5.0 or higher.
157 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
158 Please see the 20141231 entry below for information about prerequisites
159 and upgrading, if you are not already using clang 3.5.0 or higher.
162 The layout of the pmap structure has changed for powerpc to put the pmap
163 statistics at the front for all CPU variations. libkvm(3) and all tools
164 that link against it need to be recompiled.
167 isl(4) and cyapa(4) drivers now require a new driver,
168 chromebook_platform(4), to work properly on Chromebook-class hardware.
169 On other types of hardware the drivers may need to be configured using
170 device hints. Please see the corresponding manual pages for details.
173 The urtwn(4) driver was merged into rtwn(4) and now consists of
174 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
176 Also, firmware for RTL8188CE was renamed due to possible name
177 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
180 GNU rcs has been removed from base. It is available as packages:
181 - rcs: Latest GPLv3 GNU rcs version.
182 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
186 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
187 modules now requires that the kernel configuration contain the
188 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
191 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
192 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
195 Relocatable object files with the extension of .So have been renamed
196 to use an extension of .pico instead. The purpose of this change is
197 to avoid a name clash with shared libraries on case-insensitive file
198 systems. On those file systems, foo.So is the same file as foo.so.
201 GNU rcs has been turned off by default. It can (temporarily) be built
202 again by adding WITH_RCS knob in src.conf.
203 Otherwise, GNU rcs is available from packages:
204 - rcs: Latest GPLv3 GNU rcs version.
205 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
208 The backup_uses_rcs functionality has been removed from rc.subr.
211 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
212 two separate components, QUEUE_MACRO_DEBUG_TRACE and
213 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
214 QUEUE_MACRO_DEBUG behavior.
217 r304787 changed some ioctl interfaces between the iSCSI userspace
218 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
219 rebuilt to work with new kernels. __FreeBSD_version has been bumped
223 The UDP receive code has been updated to only treat incoming UDP
224 packets that were addressed to an L2 broadcast address as L3
225 broadcast packets. It is not expected that this will affect any
226 standards-conforming UDP application. The new behaviour can be
227 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
231 Remove the openbsd_poll system call.
232 __FreeBSD_version has been bumped because of this.
235 The libc stub for the pipe(2) system call has been replaced with
236 a wrapper that calls the pipe2(2) system call and the pipe(2)
237 system call is now only implemented by the kernels that include
238 "options COMPAT_FREEBSD10" in their config file (this is the
239 default). Users should ensure that this option is enabled in
240 their kernel or upgrade userspace to r302092 before upgrading their
244 CAM will now strip leading spaces from SCSI disks' serial numbers.
245 This will affect users who create UFS filesystems on SCSI disks using
246 those disk's diskid device nodes. For example, if /etc/fstab
247 previously contained a line like
248 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
249 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
250 transforms like gmirror may also be affected. ZFS users should
254 The bitstring(3) API has been updated with new functionality and
255 improved performance. But it is binary-incompatible with the old API.
256 Objects built with the new headers may not be linked against objects
257 built with the old headers.
260 The brk and sbrk functions have been removed from libc on arm64.
261 Binutils from ports has been updated to not link to these
262 functions and should be updated to the latest version before
263 installing a new libc.
266 The armv6 port now defaults to hard float ABI. Limited support
267 for running both hardfloat and soft float on the same system
268 is available using the libraries installed with -DWITH_LIBSOFT.
269 This has only been tested as an upgrade path for installworld
270 and packages may fail or need manual intervention to run. New
271 packages will be needed.
273 To update an existing self-hosted armv6hf system, you must add
274 TARGET_ARCH=armv6 on the make command line for both the build
275 and the install steps.
278 Kernel modules compiled outside of a kernel build now default to
279 installing to /boot/modules instead of /boot/kernel. Many kernel
280 modules built this way (such as those in ports) already overrode
281 KMODDIR explicitly to install into /boot/modules. However,
282 manually building and installing a module from /sys/modules will
283 now install to /boot/modules instead of /boot/kernel.
286 The CAM I/O scheduler has been committed to the kernel. There should be
287 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
288 list of known rogues that claim support for this but actually corrupt
289 data is believed to be complete, be on the lookout for data
290 corruption. The known rogue list is believed to be complete:
292 o Crucial MX100, M550 drives with MU01 firmware.
293 o Micron M510 and M550 drives with MU01 firmware.
294 o Micron M500 prior to MU07 firmware
295 o Samsung 830, 840, and 850 all firmwares
296 o FCCT M500 all firmwares
298 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
299 with working NCQ TRIM. For Micron branded drives, see your sales rep for
300 updated firmware. Black listed drives will work correctly because these
301 drives work correctly so long as no NCQ TRIMs are sent to them. Given
302 this list is the same as found in Linux, it's believed there are no
303 other rogues in the market place. All other models from the above
306 To be safe, if you are at all concerned, you can quirk each of your
307 drives to prevent NCQ from being sent by setting:
308 kern.cam.ada.X.quirks="0x2"
309 in loader.conf. If the drive requires the 4k sector quirk, set the
313 The FAST_DEPEND build option has been removed and its functionality is
314 now the one true way. The old mkdep(1) style of 'make depend' has
315 been removed. See 20160311 for further details.
318 Resource range types have grown from unsigned long to uintmax_t. All
319 drivers, and anything using libdevinfo, need to be recompiled.
322 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
323 builds. It no longer runs mkdep(1) during 'make depend', and the
324 'make depend' stage can safely be skipped now as it is auto ran
325 when building 'make all' and will generate all SRCS and DPSRCS before
326 building anything else. Dependencies are gathered at compile time with
327 -MF flags kept in separate .depend files per object file. Users should
328 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
332 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
333 kernel modules. Therefore, if you load any kernel modules at boot time,
334 please install the boot loaders after you install the kernel, but before
338 make kernel KERNCONF=YOUR_KERNEL_HERE
339 make -C sys/boot install
340 <reboot in single user>
342 Then follow the usual steps, described in the General Notes section,
346 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
347 see the 20141231 entry below for information about prerequisites and
348 upgrading, if you are not already using clang 3.5.0 or higher.
351 The AIO subsystem is now a standard part of the kernel. The
352 VFS_AIO kernel option and aio.ko kernel module have been removed.
353 Due to stability concerns, asynchronous I/O requests are only
354 permitted on sockets and raw disks by default. To enable
355 asynchronous I/O requests on all file types, set the
356 vfs.aio.enable_unsafe sysctl to a non-zero value.
359 The ELF object manipulation tool objcopy is now provided by the
360 ELF Tool Chain project rather than by GNU binutils. It should be a
361 drop-in replacement, with the addition of arm64 support. The
362 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
363 to obtain the GNU version if necessary.
366 Building ZFS pools on top of zvols is prohibited by default. That
367 feature has never worked safely; it's always been prone to deadlocks.
368 Using a zvol as the backing store for a VM guest's virtual disk will
369 still work, even if the guest is using ZFS. Legacy behavior can be
370 restored by setting vfs.zfs.vol.recursive=1.
373 The NONE and HPN patches has been removed from OpenSSH. They are
374 still available in the security/openssh-portable port.
377 With the addition of ypldap(8), a new _ypldap user is now required
378 during installworld. "mergemaster -p" can be used to add the user
379 prior to installworld, as documented in the handbook.
382 The tftp loader (pxeboot) now uses the option root-path directive. As a
383 consequence it no longer looks for a pxeboot.4th file on the tftp
384 server. Instead it uses the regular /boot infrastructure as with the
388 The code to start recording plug and play data into the modules has
389 been committed. While the old tools will properly build a new kernel,
390 a number of warnings about "unknown metadata record 4" will be produced
391 for an older kldxref. To avoid such warnings, make sure to rebuild
392 the kernel toolchain (or world). Make sure that you have r292078 or
393 later when trying to build 292077 or later before rebuilding.
396 Debug data files are now built by default with 'make buildworld' and
397 installed with 'make installworld'. This facilitates debugging but
398 requires more disk space both during the build and for the installed
399 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
403 r291527 changed the internal interface between the nfsd.ko and
404 nfscommon.ko modules. As such, they must both be upgraded to-gether.
405 __FreeBSD_version has been bumped because of this.
408 Add support for unicode collation strings leads to a change of
409 order of files listed by ls(1) for example. To get back to the old
410 behaviour, set LC_COLLATE environment variable to "C".
412 Databases administrators will need to reindex their databases given
413 collation results will be different.
415 Due to a bug in install(1) it is recommended to remove the ancient
416 locales before running make installworld.
418 rm -rf /usr/share/locale/*
421 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
422 libcrypto.so.7 or libssl.so.7 must be recompiled.
425 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
426 Kernel modules isp_2400_multi and isp_2500_multi were removed and
427 should be replaced with isp_2400 and isp_2500 modules respectively.
430 The build previously allowed using 'make -n' to not recurse into
431 sub-directories while showing what commands would be executed, and
432 'make -n -n' to recursively show commands. Now 'make -n' will recurse
433 and 'make -N' will not.
436 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
437 and etcupdate will now use this file. A custom sendmail.cf is now
438 updated via this mechanism rather than via installworld. If you had
439 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
440 want to remove the exclusion or change it to "always install".
441 /etc/mail/sendmail.cf is now managed the same way regardless of
442 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
443 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
446 Compatibility shims for legacy ATA device names have been removed.
447 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
448 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
449 environment variables, /dev/ad* and /dev/ar* symbolic links.
452 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
453 Please see the 20141231 entry below for information about prerequisites
454 and upgrading, if you are not already using clang 3.5.0 or higher.
457 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
458 and renamed from .symbols to .debug. This reduces the size requirements
459 on the boot partition or file system and provides consistency with
460 userland debug files.
462 When using the supported kernel installation method the
463 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
464 as is done with /boot/kernel.
466 Developers wishing to maintain the historical behavior of installing
467 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
470 The wireless drivers had undergone changes that remove the 'parent
471 interface' from the ifconfig -l output. The rc.d network scripts
472 used to check presence of a parent interface in the list, so old
473 scripts would fail to start wireless networking. Thus, etcupdate(3)
474 or mergemaster(8) run is required after kernel update, to update your
475 rc.d scripts in /etc.
478 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
479 These configurations are now automatically interpreted as
480 'scrub fragment reassemble'.
483 Kernel-loadable modules for the random(4) device are back. To use
484 them, the kernel must have
487 options RANDOM_LOADABLE
489 kldload(8) can then be used to load random_fortuna.ko
490 or random_yarrow.ko. Please note that due to the indirect
491 function calls that the loadable modules need to provide,
492 the build-in variants will be slightly more efficient.
494 The random(4) kernel option RANDOM_DUMMY has been retired due to
495 unpopularity. It was not all that useful anyway.
498 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
499 Control over building the ELF Tool Chain tools is now provided by
500 the WITHOUT_TOOLCHAIN knob.
503 The polarity of Pulse Per Second (PPS) capture events with the
504 uart(4) driver has been corrected. Prior to this change the PPS
505 "assert" event corresponded to the trailing edge of a positive PPS
506 pulse and the "clear" event was the leading edge of the next pulse.
508 As the width of a PPS pulse in a typical GPS receiver is on the
509 order of 1 millisecond, most users will not notice any significant
510 difference with this change.
512 Anyone who has compensated for the historical polarity reversal by
513 configuring a negative offset equal to the pulse width will need to
514 remove that workaround.
517 The default group assigned to /dev/dri entries has been changed
518 from 'wheel' to 'video' with the id of '44'. If you want to have
519 access to the dri devices please add yourself to the video group
522 # pw groupmod video -m $USER
525 The menu.rc and loader.rc files will now be replaced during
526 upgrades. Please migrate local changes to menu.rc.local and
527 loader.rc.local instead.
530 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
531 strings and strip have been removed. The src.conf(5) knob
532 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
535 As ZFS requires more kernel stack pages than is the default on some
536 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
537 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
539 Please consider using 'options KSTACK_PAGES=X' where X is greater
540 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
543 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
544 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
545 default, i.e., they will not contain "::". For example, instead
546 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
547 to have a more specific match, such as different map entries for
548 IPv6:0:0 vs IPv6:0. This change requires that configuration
549 data (including maps, files, classes, custom ruleset, etc.) must
550 use the same format, so make certain such configuration data is
551 upgrading. As a very simple check search for patterns like
552 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
553 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
554 the cf option UseCompressedIPv6Addresses.
557 The default kernel entropy-processing algorithm is now
558 Fortuna, replacing Yarrow.
560 Assuming you have 'device random' in your kernel config
561 file, the configurations allow a kernel option to override
562 this default. You may choose *ONE* of:
564 options RANDOM_YARROW # Legacy /dev/random algorithm.
565 options RANDOM_DUMMY # Blocking-only driver.
567 If you have neither, you get Fortuna. For most people,
568 read no further, Fortuna will give a /dev/random that works
569 like it always used to, and the difference will be irrelevant.
571 If you remove 'device random', you get *NO* kernel-processed
572 entropy at all. This may be acceptable to folks building
573 embedded systems, but has complications. Carry on reading,
574 and it is assumed you know what you need.
576 *PLEASE* read random(4) and random(9) if you are in the
577 habit of tweaking kernel configs, and/or if you are a member
578 of the embedded community, wanting specific and not-usual
579 behaviour from your security subsystems.
581 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
582 random', you will NOT have a functioning /dev/random, and
583 many cryptographic features will not work, including SSH.
584 You may also find strange behaviour from the random(3) set
585 of library functions, in particular sranddev(3), srandomdev(3)
586 and arc4random(3). The reason for this is that the KERN_ARND
587 sysctl only returns entropy if it thinks it has some to
588 share, and with RANDOM_DUMMY or no 'device random' this
592 An additional fix for the issue described in the 20150614 sendmail
593 entry below has been been committed in revision 284717.
596 FreeBSD's old make (fmake) has been removed from the system. It is
597 available as the devel/fmake port or via pkg install fmake.
600 The fix for the issue described in the 20150614 sendmail entry
601 below has been been committed in revision 284436. The work
602 around described in that entry is no longer needed unless the
603 default setting is overridden by a confDH_PARAMETERS configuration
604 setting of '5' or pointing to a 512 bit DH parameter file.
607 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
608 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
609 and devel/kyua to version 0.20+ and adjust any calling code to work
610 with Kyuafile and kyua.
613 The import of openssl to address the FreeBSD-SA-15:10.openssl
614 security advisory includes a change which rejects handshakes
615 with DH parameters below 768 bits. sendmail releases prior
616 to 8.15.2 (not yet released), defaulted to a 512 bit
617 DH parameter setting for client connections. To work around
618 this interoperability, sendmail can be configured to use a
619 2048 bit DH parameter by:
621 1. Edit /etc/mail/`hostname`.mc
622 2. If a setting for confDH_PARAMETERS does not exist or
623 exists and is set to a string beginning with '5',
625 3. If a setting for confDH_PARAMETERS exists and is set to
626 a file path, create a new file with:
627 openssl dhparam -out /path/to/file 2048
628 4. Rebuild the .cf file:
629 cd /etc/mail/; make; make install
631 cd /etc/mail/; make restart
633 A sendmail patch is coming, at which time this file will be
637 Generation of legacy formatted entries have been disabled by default
638 in pwd_mkdb(8), as all base system consumers of the legacy formatted
639 entries were converted to use the new format by default when the new,
640 machine independent format have been added and supported since FreeBSD
643 Please see the pwd_mkdb(8) manual page for further details.
646 Clang and llvm have been upgraded to 3.6.1 release. Please see the
647 20141231 entry below for information about prerequisites and upgrading,
648 if you are not already using 3.5.0 or higher.
651 TI platform code switched to using vendor DTS files and this update
652 may break existing systems running on Beaglebone, Beaglebone Black,
655 - dtb files should be regenerated/reinstalled. Filenames are the
656 same but content is different now
657 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
658 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
659 addressing scheme is now pin 25 on /dev/gpioc3.
660 - Pandaboard: /etc/ttys should be updated, serial console device is
661 now /dev/ttyu2, not /dev/ttyu0
664 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
665 If you need the GNU extension from groff soelim(1), install groff
666 from package: pkg install groff, or via ports: textproc/groff.
669 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
670 defined in symlink(7); previously symlinks were silently ignored.
673 The const qualifier has been removed from iconv(3) to comply with
674 POSIX. The ports tree is aware of this from r384038 onwards.
677 Libraries specified by LIBADD in Makefiles must have a corresponding
678 DPADD_<lib> variable to ensure correct dependencies. This is now
679 enforced in src.libnames.mk.
682 From legacy ata(4) driver was removed support for SATA controllers
683 supported by more functional drivers ahci(4), siis(4) and mvs(4).
684 Kernel modules ataahci and ataadaptec were removed completely,
685 replaced by ahci and mvs modules respectively.
688 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
689 the 20141231 entry below for information about prerequisites and
690 upgrading, if you are not already using 3.5.0 or higher.
693 The 32-bit PowerPC kernel has been changed to a position-independent
694 executable. This can only be booted with a version of loader(8)
695 newer than January 31, 2015, so make sure to update both world and
696 kernel before rebooting.
699 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
700 but before r278950, the RNG was not seeded properly. Immediately
701 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
702 ssh keys or openssl keys) that were generated w/ a kernel from that
703 range. This does not affect programs that directly used /dev/random
704 or /dev/urandom. All userland uses of arc4random(3) are affected.
707 The autofs(4) ABI was changed in order to restore binary compatibility
708 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
712 The powerpc64 kernel has been changed to a position-independent
713 executable. This can only be booted with a new version of loader(8),
714 so make sure to update both world and kernel before rebooting.
717 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
718 only release, no new features have been added. Please see the 20141231
719 entry below for information about prerequisites and upgrading, if you
720 are not already using 3.5.0.
723 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
724 taken from the ELF Tool Chain project rather than GNU binutils. They
725 should be drop-in replacements, with the addition of arm64 support.
726 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
727 binutils tools, if necessary. See 20150805 for updated information.
730 The default Unbound configuration now enables remote control
731 using a local socket. Users who have already enabled the
732 local_unbound service should regenerate their configuration
733 by running "service local_unbound setup" as root.
736 The GNU texinfo and GNU info pages have been removed.
737 To be able to view GNU info pages please install texinfo from ports.
740 Clang, llvm and lldb have been upgraded to 3.5.0 release.
742 As of this release, a prerequisite for building clang, llvm and lldb is
743 a C++11 capable compiler and C++11 standard library. This means that to
744 be able to successfully build the cross-tools stage of buildworld, with
745 clang as the bootstrap compiler, your system compiler or cross compiler
746 should either be clang 3.3 or later, or gcc 4.8 or later, and your
747 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
750 On any standard FreeBSD 10.x or 11.x installation, where clang and
751 libc++ are on by default (that is, on x86 or arm), this should work out
754 On 9.x installations where clang is enabled by default, e.g. on x86 and
755 powerpc, libc++ will not be enabled by default, so libc++ should be
756 built (with clang) and installed first. If both clang and libc++ are
757 missing, build clang first, then use it to build libc++.
759 On 8.x and earlier installations, upgrade to 9.x first, and then follow
760 the instructions for 9.x above.
762 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
763 default, and do not build clang.
765 Many embedded systems are resource constrained, and will not be able to
766 build clang in a reasonable time, or in some cases at all. In those
767 cases, cross building bootable systems on amd64 is a workaround.
769 This new version of clang introduces a number of new warnings, of which
770 the following are most likely to appear:
774 This warns in two cases, for both C and C++:
775 * When the code is trying to take the absolute value of an unsigned
776 quantity, which is effectively a no-op, and almost never what was
777 intended. The code should be fixed, if at all possible. If you are
778 sure that the unsigned quantity can be safely cast to signed, without
779 loss of information or undefined behavior, you can add an explicit
780 cast, or disable the warning.
782 * When the code is trying to take an absolute value, but the called
783 abs() variant is for the wrong type, which can lead to truncation.
784 If you want to disable the warning instead of fixing the code, please
785 make sure that truncation will not occur, or it might lead to unwanted
788 -Wtautological-undefined-compare and
789 -Wundefined-bool-conversion
791 These warn when C++ code is trying to compare 'this' against NULL, while
792 'this' should never be NULL in well-defined C++ code. However, there is
793 some legacy (pre C++11) code out there, which actively abuses this
794 feature, which was less strictly defined in previous C++ versions.
796 Squid and openjdk do this, for example. The warning can be turned off
797 for C++98 and earlier, but compiling the code in C++11 mode might result
798 in unexpected behavior; for example, the parts of the program that are
799 unreachable could be optimized away.
802 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
803 kernel sources have been removed. The .h files remain, since some
804 utilities include them. This will need to be fixed later.
805 If "mount -t oldnfs ..." is attempted, it will fail.
806 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
807 the utilities will report errors.
810 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
811 directories to top level SUBDIR variable when their parent
812 directory is included in LOCAL_DIRS. Users with build systems with
813 such hierarchies and without SUBDIR entries in the parent
814 directory Makefiles should add them or add the directories to
818 faith(4) and faithd(8) have been removed from the base system. Faith
819 has been obsolete for a very long time.
822 vt(4), the new console driver, is enabled by default. It brings
823 support for Unicode and double-width characters, as well as
824 support for UEFI and integration with the KMS kernel video
827 You may need to update your console settings in /etc/rc.conf,
828 most probably the keymap. During boot, /etc/rc.d/syscons will
829 indicate what you need to do.
831 vt(4) still has issues and lacks some features compared to
832 syscons(4). See the wiki for up-to-date information:
833 https://wiki.freebsd.org/Newcons
835 If you want to keep using syscons(4), you can do so by adding
836 the following line to /boot/loader.conf:
840 pjdfstest has been integrated into kyua as an opt-in test suite.
841 Please see share/doc/pjdfstest/README for more details on how to
845 gperf has been removed from the base system for architectures
846 that use clang. Ports that require gperf will obtain it from the
850 pjdfstest has been moved from tools/regression/pjdfstest to
854 At svn r271982, The default linux compat kernel ABI has been adjusted
855 to 2.6.18 in support of the linux-c6 compat ports infrastructure
856 update. If you wish to continue using the linux-f10 compat ports,
857 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
858 encouraged to update their linux-compat packages to linux-c6 during
859 their next update cycle.
862 The ofwfb driver, used to provide a graphics console on PowerPC when
863 using vt(4), no longer allows mmap() of all physical memory. This
864 will prevent Xorg on PowerPC with some ATI graphics cards from
865 initializing properly unless x11-servers/xorg-server is updated to
869 The xdev targets have been converted to using TARGET and
870 TARGET_ARCH instead of XDEV and XDEV_ARCH.
873 The default unbound configuration has been modified to address
874 issues with reverse lookups on networks that use private
875 address ranges. If you use the local_unbound service, run
876 "service local_unbound setup" as root to regenerate your
877 configuration, then "service local_unbound reload" to load the
881 The GNU texinfo and GNU info pages are not built and installed
882 anymore, WITH_INFO knob has been added to allow to built and install
884 UPDATE: see 20150102 entry on texinfo's removal
887 The GNU readline library is now an INTERNALLIB - that is, it is
888 statically linked into consumers (GDB and variants) in the base
889 system, and the shared library is no longer installed. The
890 devel/readline port is available for third party software that
894 The Itanium architecture (ia64) has been removed from the list of
895 known architectures. This is the first step in the removal of the
899 Commit r268115 has added NFSv4.1 server support, merged from
900 projects/nfsv4.1-server. Since this includes changes to the
901 internal interfaces between the NFS related modules, a full
902 build of the kernel and modules will be necessary.
903 __FreeBSD_version has been bumped.
906 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
907 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
908 which differs from the behaviour controlled by this knob.)
911 Maximal length of the serial number in CTL was increased from 16 to
912 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
913 and ctld, need to be rebuilt to work with a new kernel.
916 The libatf-c and libatf-c++ major versions were downgraded to 0 and
917 1 respectively to match the upstream numbers. They were out of
918 sync because, when they were originally added to FreeBSD, the
919 upstream versions were not respected. These libraries are private
920 and not yet built by default, so renumbering them should be a
921 non-issue. However, unclean source trees will yield broken test
922 programs once the operator executes "make delete-old-libs" after a
925 Additionally, the atf-sh binary was made private by moving it into
926 /usr/libexec/. Already-built shell test programs will keep the
927 path to the old binary so they will break after "make delete-old"
930 If you are using WITH_TESTS=yes (not the default), wipe the object
931 tree and rebuild from scratch to prevent spurious test failures.
932 This is only needed once: the misnumbered libraries and misplaced
933 binaries have been added to OptionalObsoleteFiles.inc so they will
934 be removed during a clean upgrade.
937 Clang and llvm have been upgraded to 3.4.1 release.
940 We bogusly installed src.opts.mk in /usr/share/mk. This file should
941 be removed to avoid issues in the future (and has been added to
945 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
946 past, it affected all builds that used the bsd.*.mk files. The old
947 behavior was a bug, but people may have relied upon it. To get this
948 behavior back, you can .include /etc/src.conf from /etc/make.conf
949 (which is still global and isn't changed). This also changes the
950 behavior of incremental builds inside the tree of individual
951 directories. Set MAKESYSPATH to ".../share/mk" to do that.
952 Although this has survived make universe and some upgrade scenarios,
953 other upgrade scenarios may have broken. At least one form of
954 temporary breakage was fixed with MAKESYSPATH settings for buildworld
955 as well... In cases where MAKESYSPATH isn't working with this
956 setting, you'll need to set it to the full path to your tree.
958 One side effect of all this cleaning up is that bsd.compiler.mk
959 is no longer implicitly included by bsd.own.mk. If you wish to
960 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
964 The lindev device has been removed since /dev/full has been made a
965 standard device. __FreeBSD_version has been bumped.
968 The knob WITHOUT_VI was added to the base system, which controls
969 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
970 in order to reorder files share/termcap and didn't build ex(1) as a
971 build tool, so building/installing with WITH_VI is highly advised for
972 build hosts for older releases.
974 This issue has been fixed in stable/9 and stable/10 in r277022 and
975 r276991, respectively.
978 The YES_HESIOD knob has been removed. It has been obsolete for
979 a decade. Please move to using WITH_HESIOD instead or your builds
980 will silently lack HESIOD.
983 The uart(4) driver has been changed with respect to its handling
984 of the low-level console. Previously the uart(4) driver prevented
985 any process from changing the baudrate or the CLOCAL and HUPCL
986 control flags. By removing the restrictions, operators can make
987 changes to the serial console port without having to reboot.
988 However, when getty(8) is started on the serial device that is
989 associated with the low-level console, a misconfigured terminal
990 line in /etc/ttys will now have a real impact.
991 Before upgrading the kernel, make sure that /etc/ttys has the
992 serial console device configured as 3wire without baudrate to
993 preserve the previous behaviour. E.g:
994 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
997 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
998 to improve performance. To re-enable it, if needed, run rpcbind
999 with command line option -W.
1002 Switched back to the GPL dtc compiler due to updates in the upstream
1003 dts files not being supported by the BSDL dtc compiler. You will need
1004 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1005 may result while building dtb files during a kernel build if you fail
1006 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1009 Clang and llvm have been upgraded to 3.4 release.
1012 The nve(4) driver has been removed. Please use the nfe(4) driver
1013 for NVIDIA nForce MCP Ethernet adapters instead.
1016 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1017 This could cause certain C++ applications using shared libraries built
1018 against the previous version of libc++ to crash. The incompatibility
1019 has now been fixed, but any C++ applications or shared libraries built
1020 between r261283 and r261801 should be recompiled.
1023 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1024 capability mode support. Please note that enabling the feature in
1025 kernel is still highly recommended.
1028 OpenSSH is now built with sandbox support, and will use sandbox as
1029 the default privilege separation method. This requires Capsicum
1030 capability mode support in kernel.
1033 The libelf and libdwarf libraries have been updated to newer
1034 versions from upstream. Shared library version numbers for
1035 these two libraries were bumped. Any ports or binaries
1036 requiring these two libraries should be recompiled.
1037 __FreeBSD_version is bumped to 1100006.
1040 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1041 instead of providing an explicit one, this would prevent such
1042 Makefile from providing its own Kyuafile in the future during
1043 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1044 intervention is needed to clean an objdir if you use NO_CLEAN:
1045 # find /usr/obj -name Kyuafile | xargs rm -f
1048 The behavior of gss_pseudo_random() for the krb5 mechanism
1049 has changed, for applications requesting a longer random string
1050 than produced by the underlying enctype's pseudo-random() function.
1051 In particular, the random string produced from a session key of
1052 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1053 be different at the 17th octet and later, after this change.
1054 The counter used in the PRF+ construction is now encoded as a
1055 big-endian integer in accordance with RFC 4402.
1056 __FreeBSD_version is bumped to 1100004.
1059 The WITHOUT_ATF build knob has been removed and its functionality
1060 has been subsumed into the more generic WITHOUT_TESTS. If you were
1061 using the former to disable the build of the ATF libraries, you
1062 should change your settings to use the latter.
1065 The default version of mtree is nmtree which is obtained from
1066 NetBSD. The output is generally the same, but may vary
1067 slightly. If you found you need identical output adding
1068 "-F freebsd9" to the command line should do the trick. For the
1069 time being, the old mtree is available as fmtree.
1072 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1073 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1074 1.1.4_8 and verify bsdyml not linked in, before running "make
1076 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1078 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1081 The stable/10 branch has been created in subversion from head
1085 The rc.d/jail script has been updated to support jail(8)
1086 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1087 for per-jail configuration are automatically converted to
1088 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1089 This is transparently backward compatible. See below about some
1090 incompatibilities and rc.conf(5) manual page for more details.
1092 These variables are now deprecated in favor of jail(8) configuration
1093 file. One can use "rc.d/jail config <jname>" command to generate
1094 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1095 running the jail(8) utility. The default pathname of the
1096 configuration file is /etc/jail.conf and can be specified by
1097 using $jail_conf or $jail_<jname>_conf variables.
1099 Please note that jail_devfs_ruleset accepts an integer at
1100 this moment. Please consider to rewrite the ruleset name
1104 BIND has been removed from the base system. If all you need
1105 is a local resolver, simply enable and start the local_unbound
1106 service instead. Otherwise, several versions of BIND are
1107 available in the ports tree. The dns/bind99 port is one example.
1109 With this change, nslookup(1) and dig(1) are no longer in the base
1110 system. Users should instead use host(1) and drill(1) which are
1111 in the base system. Alternatively, nslookup and dig can
1112 be obtained by installing the dns/bind-tools port.
1115 With the addition of unbound(8), a new unbound user is now
1116 required during installworld. "mergemaster -p" can be used to
1117 add the user prior to installworld, as documented in the handbook.
1120 OpenSSH is now built with DNSSEC support, and will by default
1121 silently trust signed SSHFP records. This can be controlled with
1122 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1123 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1126 The GNU Compiler Collection and C++ standard library (libstdc++)
1127 are no longer built by default on platforms where clang is the system
1128 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1129 options in src.conf.
1132 The PROCDESC kernel option is now part of the GENERIC kernel
1133 configuration and is required for the rwhod(8) to work.
1134 If you are using custom kernel configuration, you should include
1138 The API and ABI related to the Capsicum framework was modified
1139 in backward incompatible way. The userland libraries and programs
1140 have to be recompiled to work with the new kernel. This includes the
1141 following libraries and programs, but the whole buildworld is
1142 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1143 kdump, procstat, rwho, rwhod, uniq.
1146 AES-NI intrinsic support has been added to gcc. The AES-NI module
1147 has been updated to use this support. A new gcc is required to build
1148 the aesni module on both i386 and amd64.
1151 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1152 Thus "device padlock_rng" and "device rdrand_rng" should be
1153 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1156 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1157 enables just the iconv* functionality and is now on by default.
1158 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1159 compatibility. Set WITHOUT_ICONV to build the old way.
1160 If you have been using WITH_ICONV before, you will very likely
1161 need to turn on WITH_LIBICONV_COMPAT.
1164 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1165 Illumos origin, including ZFS. If you have INVARIANTS in your
1166 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1168 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1169 locks if WITNESS option was set. Because that generated a lot of
1170 witness(9) reports and all of them were believed to be false
1171 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1172 can be used to achieve the previous behavior.
1175 Timer values in IPv6 data structures now use time_uptime instead
1176 of time_second. Although this is not a user-visible functional
1177 change, userland utilities which directly use them---ndp(8),
1178 rtadvd(8), and rtsold(8) in the base system---need to be updated
1179 to r253970 or later.
1182 find -delete can now delete the pathnames given as arguments,
1183 instead of only files found below them or if the pathname did
1184 not contain any slashes. Formerly, the following error message
1187 find: -delete: <path>: relative path potentially not safe
1189 Deleting the pathnames given as arguments can be prevented
1190 without error messages using -mindepth 1 or by changing
1191 directory and passing "." as argument to find. This works in the
1192 old as well as the new version of find.
1195 Behavior of devfs rules path matching has been changed.
1196 Pattern is now always matched against fully qualified devfs
1197 path and slash characters must be explicitly matched by
1198 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1199 subdirectories must be reviewed.
1202 The default ARM ABI has changed to the ARM EABI. The old ABI is
1203 incompatible with the ARM EABI and all programs and modules will
1204 need to be rebuilt to work with a new kernel.
1206 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1208 NOTE: Support for the old ABI will be removed in the future and
1209 users are advised to upgrade.
1212 pkg_install has been disconnected from the build if you really need it
1213 you should add WITH_PKGTOOLS in your src.conf(5).
1216 Most of network statistics structures were changed to be able
1217 keep 64-bits counters. Thus all tools, that work with networking
1218 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1221 Fix a bug that allowed a tracing process (e.g. gdb) to write
1222 to a memory-mapped file in the traced process's address space
1223 even if neither the traced process nor the tracing process had
1224 write access to that file.
1227 CVS has been removed from the base system. An exact copy
1228 of the code is available from the devel/cvs port.
1231 Some people report the following error after the switch to bmake:
1233 make: illegal option -- J
1234 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1236 *** [buildworld] Error code 2
1238 this likely due to an old instance of make in
1239 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1240 which src/Makefile will use that blindly, if it exists, so if
1241 you see the above error:
1243 rm -rf `make -V MAKEPATH`
1248 Use bmake by default.
1249 Whereas before one could choose to build with bmake via
1250 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1251 make. The goal is to remove these knobs for 10-RELEASE.
1253 It is worth noting that bmake (like gmake) treats the command
1254 line as the unit of failure, rather than statements within the
1255 command line. Thus '(cd some/where && dosomething)' is safer
1256 than 'cd some/where; dosomething'. The '()' allows consistent
1257 behavior in parallel build.
1260 Fix a bug that allows NFS clients to issue READDIR on files.
1263 The WITHOUT_IDEA option has been removed because
1264 the IDEA patent expired.
1267 The sysctl which controls TRIM support under ZFS has been renamed
1268 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1272 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1273 rather than creating it's own in the temporary directory in
1274 order allow access to bootstrapped versions of tools such as
1275 install and mtree. When upgrading from version of FreeBSD where
1276 the install command does not support -l, you will need to
1277 install a new mergemaster command if mergemaster -p is required.
1278 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1282 Legacy ATA stack, disabled and replaced by new CAM-based one since
1283 FreeBSD 9.0, completely removed from the sources. Kernel modules
1284 atadisk and atapi*, user-level tools atacontrol and burncd are
1285 removed. Kernel option `options ATA_CAM` is now permanently enabled
1289 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1290 and socketpair(2). Software, in particular Kerberos, may
1291 automatically detect and use these during building. The resulting
1292 binaries will not work on older kernels.
1295 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1296 information, see the respective 20130304 entry).
1299 Recent commits to callout(9) changed the size of struct callout,
1300 so the KBI is probably heavily disturbed. Also, some functions
1301 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1302 by macros. Every kernel module using it won't load, so rebuild
1305 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1306 but does not initialize by default (because of the new CTL_DISABLE
1307 option) to save memory. To re-enable it, remove the CTL_DISABLE
1308 option from the kernel config file or set kern.cam.ctl.disable=0
1309 in /boot/loader.conf.
1312 The ctl device has been disabled in GENERIC for i386 and amd64.
1313 This was done due to the extra memory being allocated at system
1314 initialisation time by the ctl driver which was only used if
1315 a CAM target device was created. This makes a FreeBSD system
1316 unusable on 128MB or less of RAM.
1319 A new compression method (lz4) has been merged to -HEAD. Please
1320 refer to zpool-features(7) for more information.
1322 Please refer to the "ZFS notes" section of this file for information
1323 on upgrading boot ZFS pools.
1326 A BSD-licensed patch(1) variant has been added and is installed
1327 as bsdpatch, being the GNU version the default patch.
1328 To inverse the logic and use the BSD-licensed one as default,
1329 while having the GNU version installed as gnupatch, rebuild
1330 and install world with the WITH_BSD_PATCH knob set.
1333 Due to the use of the new -l option to install(1) during build
1334 and install, you must take care not to directly set the INSTALL
1335 make variable in your /etc/make.conf, /etc/src.conf, or on the
1336 command line. If you wish to use the -C flag for all installs
1337 you may be able to add INSTALL+=-C to /etc/make.conf or
1341 The install(1) option -M has changed meaning and now takes an
1342 argument that is a file or path to append logs to. In the
1343 unlikely event that -M was the last option on the command line
1344 and the command line contained at least two files and a target
1345 directory the first file will have logs appended to it. The -M
1346 option served little practical purpose in the last decade so its
1347 use is expected to be extremely rare.
1350 After switching to Clang as the default compiler some users of ZFS
1351 on i386 systems started to experience stack overflow kernel panics.
1352 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1355 GEOM_LABEL now mangles label names read from file system metadata.
1356 Mangling affect labels containing spaces, non-printable characters,
1357 '%' or '"'. Device names in /etc/fstab and other places may need to
1361 By default, only the 10 most recent kernel dumps will be saved. To
1362 restore the previous behaviour (no limit on the number of kernel dumps
1363 stored in the dump directory) add the following line to /etc/rc.conf:
1368 With the addition of auditdistd(8), a new auditdistd user is now
1369 required during installworld. "mergemaster -p" can be used to
1370 add the user prior to installworld, as documented in the handbook.
1373 The sin6_scope_id member variable in struct sockaddr_in6 is now
1374 filled by the kernel before passing the structure to the userland via
1375 sysctl or routing socket. This means the KAME-specific embedded scope
1376 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1377 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1378 __FreeBSD_version is bumped to 1000025.
1381 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1382 This means that the world and kernel will be compiled with clang
1383 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1384 and /usr/bin/cpp. To disable this behavior and revert to building
1385 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1386 of current may need to bootstrap WITHOUT_CLANG first if the clang
1387 build fails (its compatibility window doesn't extend to the 9 stable
1391 The IPFIREWALL_FORWARD kernel option has been removed. Its
1392 functionality now turned on by default.
1395 The ZERO_COPY_SOCKET kernel option has been removed and
1396 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1397 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1398 mechanism which is not safe and may result in kernel crashes.
1399 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1400 driver supports disposeable external page sized mbuf storage.
1401 Proper replacements for both zero-copy mechanisms are under
1402 consideration and will eventually lead to complete removal
1403 of the two kernel options.
1406 The IPv4 network stack has been converted to network byte
1407 order. The following modules need to be recompiled together
1408 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1409 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1412 Support for non-MPSAFE filesystems was removed from VFS. The
1413 VFS_VERSION was bumped, all filesystem modules shall be
1417 All the non-MPSAFE filesystems have been disconnected from
1418 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1419 portalfs, smbfs, xfs.
1422 The interface cloning API and ABI has changed. The following
1423 modules need to be recompiled together with kernel:
1424 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1425 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1426 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1429 The sdhci driver was split in two parts: sdhci (generic SD Host
1430 Controller logic) and sdhci_pci (actual hardware driver).
1431 No kernel config modifications are required, but if you
1432 load sdhc as a module you must switch to sdhci_pci instead.
1435 Import the FUSE kernel and userland support into base system.
1438 The GNU sort(1) program has been removed since the BSD-licensed
1439 sort(1) has been the default for quite some time and no serious
1440 problems have been reported. The corresponding WITH_GNU_SORT
1444 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1445 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1449 The net80211(4) ABI has been changed to allow for improved driver
1450 PS-POLL and power-save support. All wireless drivers need to be
1451 recompiled to work with the new kernel.
1454 The random(4) support for the VIA hardware random number
1455 generator (`PADLOCK') is no longer enabled unconditionally.
1456 Add the padlock_rng device in the custom kernel config if
1457 needed. The GENERIC kernels on i386 and amd64 do include the
1458 device, so the change only affects the custom kernel
1462 The pf(4) packet filter ABI has been changed. pfctl(8) and
1463 snmp_pf module need to be recompiled to work with new kernel.
1466 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1467 to -HEAD. Pools that have empty_bpobj in active state can not be
1468 imported read-write with ZFS implementations that do not support
1469 this feature. For more information read the zpool-features(5)
1473 The sparc64 ZFS loader has been changed to no longer try to auto-
1474 detect ZFS providers based on diskN aliases but now requires these
1475 to be explicitly listed in the OFW boot-device environment variable.
1478 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1479 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1480 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1483 The following sysctls and tunables have been renamed for consistency
1484 with other variables:
1485 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1486 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1489 The sort utility has been replaced with BSD sort. For now, GNU sort
1490 is also available as "gnusort" or the default can be set back to
1491 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1492 installed as "bsdsort".
1495 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1496 Starting with this version the old system of ZFS pool versioning
1497 is superseded by "feature flags". This concept enables forward
1498 compatibility against certain future changes in functionality of ZFS
1499 pools. The first read-only compatible "feature flag" for ZFS pools
1500 is named "com.delphix:async_destroy". For more information
1501 read the new zpool-features(5) manual page.
1502 Please refer to the "ZFS notes" section of this file for information
1503 on upgrading boot ZFS pools.
1506 The malloc(3) implementation embedded in libc now uses sources imported
1507 as contrib/jemalloc. The most disruptive API change is to
1508 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1509 delete it prior to installworld, and optionally re-create it using the
1510 new format after rebooting. See malloc.conf(5) for details
1511 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1515 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1516 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1517 now spelled mips. This is to aid compatibility with third-party
1518 software that expects this naming scheme in uname(3). Little-endian
1519 settings are unchanged. If you are updating a big-endian mips64 machine
1520 from before this change, you may need to set MACHINE_ARCH=mips64 in
1521 your environment before the new build system will recognize your machine.
1524 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1528 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1529 nullfs(5) did not pass through all behaviours to the underlying layer,
1530 as a result if we bound to a socket on the lower layer we could connect
1531 only to the lower path; if we bound to the upper layer we could connect
1532 only to the upper path. The new behavior is one can connect to both the
1533 lower and the upper paths regardless what layer path one binds to.
1536 The getifaddrs upgrade path broken with 20111215 has been restored.
1537 If you have upgraded in between 20111215 and 20120209 you need to
1538 recompile libc again with your kernel. You still need to recompile
1539 world to be able to configure CARP but this restriction already
1540 comes from 20111215.
1543 The set_rcvar() function has been removed from /etc/rc.subr. All
1544 base and ports rc.d scripts have been updated, so if you have a
1545 port installed with a script in /usr/local/etc/rc.d you can either
1546 hand-edit the rcvar= line, or reinstall the port.
1548 An easy way to handle the mass-update of /etc/rc.d:
1549 rm /etc/rc.d/* && mergemaster -i
1552 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1553 on the current CPU and prevents other threads from running.
1554 This behavior can be reverted using the kern.stop_scheduler_on_panic
1556 The new behavior can be incompatible with kern.sync_on_panic.
1559 The carp(4) facility has been changed significantly. Configuration
1560 of the CARP protocol via ifconfig(8) has changed, as well as format
1561 of CARP events submitted to devd(8) has changed. See manual pages
1562 for more information. The arpbalance feature of carp(4) is currently
1563 not supported anymore.
1565 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1566 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1567 need to be recompiled.
1570 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1574 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1575 explicitely support non-MPSAFE filesystems.
1576 It is on by default for all supported platform at this present
1580 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1581 i386 and pc98 GENERIC kernel configuration files.
1584 sysinstall has been removed
1587 The stable/9 branch created in subversion. This corresponds to the
1588 RELENG_9 branch in CVS.
1594 Avoid using make -j when upgrading. While generally safe, there are
1595 sometimes problems using -j to upgrade. If your upgrade fails with
1596 -j, please try again without -j. From time to time in the past there
1597 have been problems using -j with buildworld and/or installworld. This
1598 is especially true when upgrading between "distant" versions (eg one
1599 that cross a major release boundary or several minor releases, or when
1600 several months have passed on the -current branch).
1602 Sometimes, obscure build problems are the result of environment
1603 poisoning. This can happen because the make utility reads its
1604 environment when searching for values for global variables. To run
1605 your build attempts in an "environmental clean room", prefix all make
1606 commands with 'env -i '. See the env(1) manual page for more details.
1608 When upgrading from one major version to another it is generally best to
1609 upgrade to the latest code in the currently installed branch first, then
1610 do an upgrade to the new branch. This is the best-tested upgrade path,
1611 and has the highest probability of being successful. Please try this
1612 approach if you encounter problems with a major version upgrade. Since
1613 the stable 4.x branch point, one has generally been able to upgade from
1614 anywhere in the most recent stable branch to head / current (or even the
1615 last couple of stable branches). See the top of this file when there's
1618 When upgrading a live system, having a root shell around before
1619 installing anything can help undo problems. Not having a root shell
1620 around can lead to problems if pam has changed too much from your
1621 starting point to allow continued authentication after the upgrade.
1623 This file should be read as a log of events. When a later event changes
1624 information of a prior event, the prior event should not be deleted.
1625 Instead, a pointer to the entry with the new information should be
1626 placed in the old entry. Readers of this file should also sanity check
1627 older entries before relying on them blindly. Authors of new entries
1628 should write them with this in mind.
1632 When upgrading the boot ZFS pool to a new version, always follow
1635 1.) recompile and reinstall the ZFS boot loader and boot block
1636 (this is part of "make buildworld" and "make installworld")
1638 2.) update the ZFS boot block on your boot drive
1640 The following example updates the ZFS boot block on the first
1641 partition (freebsd-boot) of a GPT partitioned drive ada0:
1642 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1644 Non-boot pools do not need these updates.
1648 If you are updating from a prior version of FreeBSD (even one just
1649 a few days old), you should follow this procedure. It is the most
1650 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1652 make kernel-toolchain
1653 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1654 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1656 To test a kernel once
1657 ---------------------
1658 If you just want to boot a kernel once (because you are not sure
1659 if it works, or if you want to boot a known bad kernel to provide
1660 debugging information) run
1661 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1662 nextboot -k testkernel
1664 To just build a kernel when you know that it won't mess you up
1665 --------------------------------------------------------------
1666 This assumes you are already running a CURRENT system. Replace
1667 ${arch} with the architecture of your machine (e.g. "i386",
1668 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1670 cd src/sys/${arch}/conf
1671 config KERNEL_NAME_HERE
1672 cd ../compile/KERNEL_NAME_HERE
1677 If this fails, go to the "To build a kernel" section.
1679 To rebuild everything and install it on the current system.
1680 -----------------------------------------------------------
1681 # Note: sometimes if you are running current you gotta do more than
1682 # is listed here if you are upgrading from a really old current.
1684 <make sure you have good level 0 dumps>
1686 make kernel KERNCONF=YOUR_KERNEL_HERE
1688 <reboot in single user> [3]
1695 To cross-install current onto a separate partition
1696 --------------------------------------------------
1697 # In this approach we use a separate partition to hold
1698 # current's root, 'usr', and 'var' directories. A partition
1699 # holding "/", "/usr" and "/var" should be about 2GB in
1702 <make sure you have good level 0 dumps>
1705 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1706 <maybe newfs current's root partition>
1707 <mount current's root partition on directory ${CURRENT_ROOT}>
1708 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1709 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1710 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1711 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1712 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1713 <reboot into current>
1714 <do a "native" rebuild/install as described in the previous section>
1715 <maybe install compatibility libraries from ports/misc/compat*>
1719 To upgrade in-place from stable to current
1720 ----------------------------------------------
1721 <make sure you have good level 0 dumps>
1723 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1725 <reboot in single user> [3]
1732 Make sure that you've read the UPDATING file to understand the
1733 tweaks to various things you need. At this point in the life
1734 cycle of current, things change often and you are on your own
1735 to cope. The defaults can also change, so please read ALL of
1736 the UPDATING entries.
1738 Also, if you are tracking -current, you must be subscribed to
1739 freebsd-current@freebsd.org. Make sure that before you update
1740 your sources that you have read and understood all the recent
1741 messages there. If in doubt, please track -stable which has
1742 much fewer pitfalls.
1744 [1] If you have third party modules, such as vmware, you
1745 should disable them at this point so they don't crash your
1748 [3] From the bootblocks, boot -s, and then do
1753 adjkerntz -i # if CMOS is wall time
1754 Also, when doing a major release upgrade, it is required that
1755 you boot into single user mode to do the installworld.
1757 [4] Note: This step is non-optional. Failure to do this step
1758 can result in a significant reduction in the functionality of the
1759 system. Attempting to do it by hand is not recommended and those
1760 that pursue this avenue should read this file carefully, as well
1761 as the archives of freebsd-current and freebsd-hackers mailing lists
1762 for potential gotchas. The -U option is also useful to consider.
1763 See mergemaster(8) for more information.
1765 [5] Usually this step is a noop. However, from time to time
1766 you may need to do this if you get unknown user in the following
1767 step. It never hurts to do it all the time. You may need to
1768 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1769 install) after the buildworld before this step if you last updated
1770 from current before 20130425 or from -stable before 20130430.
1772 [6] This only deletes old files and directories. Old libraries
1773 can be deleted by "make delete-old-libs", but you have to make
1774 sure that no program is using those libraries anymore.
1776 [8] In order to have a kernel that can run the 4.x binaries needed to
1777 do an installworld, you must include the COMPAT_FREEBSD4 option in
1778 your kernel. Failure to do so may leave you with a system that is
1779 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1780 required to run the 5.x binaries on more recent kernels. And so on
1781 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1783 Make sure that you merge any new devices from GENERIC since the
1784 last time you updated your kernel config file.
1786 [9] When checking out sources, you must include the -P flag to have
1787 cvs prune empty directories.
1789 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1790 "?=" instead of the "=" assignment operator, so that buildworld can
1791 override the CPUTYPE if it needs to.
1793 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1794 not on the command line, or in /etc/make.conf. buildworld will
1795 warn if it is improperly defined.
1798 This file contains a list, in reverse chronological order, of major
1799 breakages in tracking -current. It is not guaranteed to be a complete
1800 list of such breakages, and only contains entries since September 23, 2011.
1801 If you need to see UPDATING entries from before that date, you will need
1802 to fetch an UPDATING file from an older FreeBSD release.
1804 Copyright information:
1806 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1808 Redistribution, publication, translation and use, with or without
1809 modification, in full or in part, in any form or format of this
1810 document are permitted without further permission from the author.
1812 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1813 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1814 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1815 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1816 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1817 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1818 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1819 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1820 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1821 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1822 POSSIBILITY OF SUCH DAMAGE.
1824 Contact Warner Losh if you have any questions about your use of