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 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
56 diff has not been implemented, if those are needed a newer version of
57 GNU diff is available via the diffutils package under the gdiff name.
60 As of r316810 for ipfilter, keep frags is no longer assumed when
61 keep state is specified in a rule. r316810 aligns ipfilter with
62 documentation in man pages separating keep frags from keep state.
63 This allows keep state to be specified without forcing keep frags
64 and allows keep frags to be specified independently of keep state.
65 To maintain previous behaviour, also specify keep frags with
66 keep state (as documented in ipf.conf.5).
69 arm64 builds now use the base system LLD 4.0.0 linker by default,
70 instead of requiring that the aarch64-binutils port or package be
71 installed. To continue using aarch64-binutils, set
72 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
75 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
76 use any explicitly assigned loopback address available in the jail
77 instead of using the first assigned address of the jail.
80 The ctl.ko module no longer implements the iSCSI target frontend:
81 cfiscsi.ko does instead.
83 If building cfiscsi.ko as a kernel module, the module can be loaded
84 via one of the following methods:
85 - `cfiscsi_load="YES"` in loader.conf(5).
86 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
87 - ctladm(8)/ctld(8), when compiled with iSCSI support
88 (`WITH_ISCSI=yes` in src.conf(5))
90 Please see cfiscsi(4) for more details.
93 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
94 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
95 same source (previously, the dependency of mmcsd.ko on mmc.ko was
96 missing, but mmcsd.ko now will refuse to load if it is incompatible
100 The syntax of ipfw(8) named states was changed to avoid ambiguity.
101 If you have used named states in the firewall rules, you need to modify
102 them after installworld and before rebooting. Now named states must
103 be prefixed with colon.
106 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
107 removed as the userland we provide cannot use them. The KMS version
108 (sys/dev/drm2) supports the same hardware.
111 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
112 Please see the 20141231 entry below for information about prerequisites
113 and upgrading, if you are not already using clang 3.5.0 or higher.
116 The code that provides support for ZFS .zfs/ directory functionality
117 has been reimplemented. It's not possible now to create a snapshot
118 by mkdir under .zfs/snapshot/. That should be the only user visible
122 EISA bus support has been removed. The WITH_EISA option is no longer
126 MCA bus support has been removed.
129 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
130 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
133 The EM_MULTIQUEUE kernel configuration option is deprecated now that
134 the em(4) driver conforms to iflib specifications.
137 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
138 IFLIB. If you have a custom kernel configuration that excludes em(4)
139 but you use igb(4), you need to re-add em(4) to your custom configuration.
142 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
143 Please see the 20141231 entry below for information about prerequisites
144 and upgrading, if you are not already using clang 3.5.0 or higher.
147 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
148 Please see the 20141231 entry below for information about prerequisites
149 and upgrading, if you are not already using clang 3.5.0 or higher.
152 The layout of the pmap structure has changed for powerpc to put the pmap
153 statistics at the front for all CPU variations. libkvm(3) and all tools
154 that link against it need to be recompiled.
157 isl(4) and cyapa(4) drivers now require a new driver,
158 chromebook_platform(4), to work properly on Chromebook-class hardware.
159 On other types of hardware the drivers may need to be configured using
160 device hints. Please see the corresponding manual pages for details.
163 The urtwn(4) driver was merged into rtwn(4) and now consists of
164 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
166 Also, firmware for RTL8188CE was renamed due to possible name
167 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
170 GNU rcs has been removed from base. It is available as packages:
171 - rcs: Latest GPLv3 GNU rcs version.
172 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
176 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
177 modules now requires that the kernel configuration contain the
178 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
181 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
182 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
185 Relocatable object files with the extension of .So have been renamed
186 to use an extension of .pico instead. The purpose of this change is
187 to avoid a name clash with shared libraries on case-insensitive file
188 systems. On those file systems, foo.So is the same file as foo.so.
191 GNU rcs has been turned off by default. It can (temporarily) be built
192 again by adding WITH_RCS knob in src.conf.
193 Otherwise, GNU rcs is available from packages:
194 - rcs: Latest GPLv3 GNU rcs version.
195 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
198 The backup_uses_rcs functionality has been removed from rc.subr.
201 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
202 two separate components, QUEUE_MACRO_DEBUG_TRACE and
203 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
204 QUEUE_MACRO_DEBUG behavior.
207 r304787 changed some ioctl interfaces between the iSCSI userspace
208 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
209 rebuilt to work with new kernels. __FreeBSD_version has been bumped
213 The UDP receive code has been updated to only treat incoming UDP
214 packets that were addressed to an L2 broadcast address as L3
215 broadcast packets. It is not expected that this will affect any
216 standards-conforming UDP application. The new behaviour can be
217 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
221 Remove the openbsd_poll system call.
222 __FreeBSD_version has been bumped because of this.
225 The libc stub for the pipe(2) system call has been replaced with
226 a wrapper that calls the pipe2(2) system call and the pipe(2)
227 system call is now only implemented by the kernels that include
228 "options COMPAT_FREEBSD10" in their config file (this is the
229 default). Users should ensure that this option is enabled in
230 their kernel or upgrade userspace to r302092 before upgrading their
234 CAM will now strip leading spaces from SCSI disks' serial numbers.
235 This will affect users who create UFS filesystems on SCSI disks using
236 those disk's diskid device nodes. For example, if /etc/fstab
237 previously contained a line like
238 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
239 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
240 transforms like gmirror may also be affected. ZFS users should
244 The bitstring(3) API has been updated with new functionality and
245 improved performance. But it is binary-incompatible with the old API.
246 Objects built with the new headers may not be linked against objects
247 built with the old headers.
250 The brk and sbrk functions have been removed from libc on arm64.
251 Binutils from ports has been updated to not link to these
252 functions and should be updated to the latest version before
253 installing a new libc.
256 The armv6 port now defaults to hard float ABI. Limited support
257 for running both hardfloat and soft float on the same system
258 is available using the libraries installed with -DWITH_LIBSOFT.
259 This has only been tested as an upgrade path for installworld
260 and packages may fail or need manual intervention to run. New
261 packages will be needed.
263 To update an existing self-hosted armv6hf system, you must add
264 TARGET_ARCH=armv6 on the make command line for both the build
265 and the install steps.
268 Kernel modules compiled outside of a kernel build now default to
269 installing to /boot/modules instead of /boot/kernel. Many kernel
270 modules built this way (such as those in ports) already overrode
271 KMODDIR explicitly to install into /boot/modules. However,
272 manually building and installing a module from /sys/modules will
273 now install to /boot/modules instead of /boot/kernel.
276 The CAM I/O scheduler has been committed to the kernel. There should be
277 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
278 list of known rogues that claim support for this but actually corrupt
279 data is believed to be complete, be on the lookout for data
280 corruption. The known rogue list is believed to be complete:
282 o Crucial MX100, M550 drives with MU01 firmware.
283 o Micron M510 and M550 drives with MU01 firmware.
284 o Micron M500 prior to MU07 firmware
285 o Samsung 830, 840, and 850 all firmwares
286 o FCCT M500 all firmwares
288 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
289 with working NCQ TRIM. For Micron branded drives, see your sales rep for
290 updated firmware. Black listed drives will work correctly because these
291 drives work correctly so long as no NCQ TRIMs are sent to them. Given
292 this list is the same as found in Linux, it's believed there are no
293 other rogues in the market place. All other models from the above
296 To be safe, if you are at all concerned, you can quirk each of your
297 drives to prevent NCQ from being sent by setting:
298 kern.cam.ada.X.quirks="0x2"
299 in loader.conf. If the drive requires the 4k sector quirk, set the
303 The FAST_DEPEND build option has been removed and its functionality is
304 now the one true way. The old mkdep(1) style of 'make depend' has
305 been removed. See 20160311 for further details.
308 Resource range types have grown from unsigned long to uintmax_t. All
309 drivers, and anything using libdevinfo, need to be recompiled.
312 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
313 builds. It no longer runs mkdep(1) during 'make depend', and the
314 'make depend' stage can safely be skipped now as it is auto ran
315 when building 'make all' and will generate all SRCS and DPSRCS before
316 building anything else. Dependencies are gathered at compile time with
317 -MF flags kept in separate .depend files per object file. Users should
318 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
322 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
323 kernel modules. Therefore, if you load any kernel modules at boot time,
324 please install the boot loaders after you install the kernel, but before
328 make kernel KERNCONF=YOUR_KERNEL_HERE
329 make -C sys/boot install
330 <reboot in single user>
332 Then follow the usual steps, described in the General Notes section,
336 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
337 see the 20141231 entry below for information about prerequisites and
338 upgrading, if you are not already using clang 3.5.0 or higher.
341 The AIO subsystem is now a standard part of the kernel. The
342 VFS_AIO kernel option and aio.ko kernel module have been removed.
343 Due to stability concerns, asynchronous I/O requests are only
344 permitted on sockets and raw disks by default. To enable
345 asynchronous I/O requests on all file types, set the
346 vfs.aio.enable_unsafe sysctl to a non-zero value.
349 The ELF object manipulation tool objcopy is now provided by the
350 ELF Tool Chain project rather than by GNU binutils. It should be a
351 drop-in replacement, with the addition of arm64 support. The
352 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
353 to obtain the GNU version if necessary.
356 Building ZFS pools on top of zvols is prohibited by default. That
357 feature has never worked safely; it's always been prone to deadlocks.
358 Using a zvol as the backing store for a VM guest's virtual disk will
359 still work, even if the guest is using ZFS. Legacy behavior can be
360 restored by setting vfs.zfs.vol.recursive=1.
363 The NONE and HPN patches has been removed from OpenSSH. They are
364 still available in the security/openssh-portable port.
367 With the addition of ypldap(8), a new _ypldap user is now required
368 during installworld. "mergemaster -p" can be used to add the user
369 prior to installworld, as documented in the handbook.
372 The tftp loader (pxeboot) now uses the option root-path directive. As a
373 consequence it no longer looks for a pxeboot.4th file on the tftp
374 server. Instead it uses the regular /boot infrastructure as with the
378 The code to start recording plug and play data into the modules has
379 been committed. While the old tools will properly build a new kernel,
380 a number of warnings about "unknown metadata record 4" will be produced
381 for an older kldxref. To avoid such warnings, make sure to rebuild
382 the kernel toolchain (or world). Make sure that you have r292078 or
383 later when trying to build 292077 or later before rebuilding.
386 Debug data files are now built by default with 'make buildworld' and
387 installed with 'make installworld'. This facilitates debugging but
388 requires more disk space both during the build and for the installed
389 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
393 r291527 changed the internal interface between the nfsd.ko and
394 nfscommon.ko modules. As such, they must both be upgraded to-gether.
395 __FreeBSD_version has been bumped because of this.
398 Add support for unicode collation strings leads to a change of
399 order of files listed by ls(1) for example. To get back to the old
400 behaviour, set LC_COLLATE environment variable to "C".
402 Databases administrators will need to reindex their databases given
403 collation results will be different.
405 Due to a bug in install(1) it is recommended to remove the ancient
406 locales before running make installworld.
408 rm -rf /usr/share/locale/*
411 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
412 libcrypto.so.7 or libssl.so.7 must be recompiled.
415 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
416 Kernel modules isp_2400_multi and isp_2500_multi were removed and
417 should be replaced with isp_2400 and isp_2500 modules respectively.
420 The build previously allowed using 'make -n' to not recurse into
421 sub-directories while showing what commands would be executed, and
422 'make -n -n' to recursively show commands. Now 'make -n' will recurse
423 and 'make -N' will not.
426 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
427 and etcupdate will now use this file. A custom sendmail.cf is now
428 updated via this mechanism rather than via installworld. If you had
429 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
430 want to remove the exclusion or change it to "always install".
431 /etc/mail/sendmail.cf is now managed the same way regardless of
432 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
433 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
436 Compatibility shims for legacy ATA device names have been removed.
437 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
438 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
439 environment variables, /dev/ad* and /dev/ar* symbolic links.
442 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
443 Please see the 20141231 entry below for information about prerequisites
444 and upgrading, if you are not already using clang 3.5.0 or higher.
447 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
448 and renamed from .symbols to .debug. This reduces the size requirements
449 on the boot partition or file system and provides consistency with
450 userland debug files.
452 When using the supported kernel installation method the
453 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
454 as is done with /boot/kernel.
456 Developers wishing to maintain the historical behavior of installing
457 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
460 The wireless drivers had undergone changes that remove the 'parent
461 interface' from the ifconfig -l output. The rc.d network scripts
462 used to check presence of a parent interface in the list, so old
463 scripts would fail to start wireless networking. Thus, etcupdate(3)
464 or mergemaster(8) run is required after kernel update, to update your
465 rc.d scripts in /etc.
468 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
469 These configurations are now automatically interpreted as
470 'scrub fragment reassemble'.
473 Kernel-loadable modules for the random(4) device are back. To use
474 them, the kernel must have
477 options RANDOM_LOADABLE
479 kldload(8) can then be used to load random_fortuna.ko
480 or random_yarrow.ko. Please note that due to the indirect
481 function calls that the loadable modules need to provide,
482 the build-in variants will be slightly more efficient.
484 The random(4) kernel option RANDOM_DUMMY has been retired due to
485 unpopularity. It was not all that useful anyway.
488 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
489 Control over building the ELF Tool Chain tools is now provided by
490 the WITHOUT_TOOLCHAIN knob.
493 The polarity of Pulse Per Second (PPS) capture events with the
494 uart(4) driver has been corrected. Prior to this change the PPS
495 "assert" event corresponded to the trailing edge of a positive PPS
496 pulse and the "clear" event was the leading edge of the next pulse.
498 As the width of a PPS pulse in a typical GPS receiver is on the
499 order of 1 millisecond, most users will not notice any significant
500 difference with this change.
502 Anyone who has compensated for the historical polarity reversal by
503 configuring a negative offset equal to the pulse width will need to
504 remove that workaround.
507 The default group assigned to /dev/dri entries has been changed
508 from 'wheel' to 'video' with the id of '44'. If you want to have
509 access to the dri devices please add yourself to the video group
512 # pw groupmod video -m $USER
515 The menu.rc and loader.rc files will now be replaced during
516 upgrades. Please migrate local changes to menu.rc.local and
517 loader.rc.local instead.
520 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
521 strings and strip have been removed. The src.conf(5) knob
522 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
525 As ZFS requires more kernel stack pages than is the default on some
526 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
527 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
529 Please consider using 'options KSTACK_PAGES=X' where X is greater
530 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
533 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
534 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
535 default, i.e., they will not contain "::". For example, instead
536 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
537 to have a more specific match, such as different map entries for
538 IPv6:0:0 vs IPv6:0. This change requires that configuration
539 data (including maps, files, classes, custom ruleset, etc.) must
540 use the same format, so make certain such configuration data is
541 upgrading. As a very simple check search for patterns like
542 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
543 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
544 the cf option UseCompressedIPv6Addresses.
547 The default kernel entropy-processing algorithm is now
548 Fortuna, replacing Yarrow.
550 Assuming you have 'device random' in your kernel config
551 file, the configurations allow a kernel option to override
552 this default. You may choose *ONE* of:
554 options RANDOM_YARROW # Legacy /dev/random algorithm.
555 options RANDOM_DUMMY # Blocking-only driver.
557 If you have neither, you get Fortuna. For most people,
558 read no further, Fortuna will give a /dev/random that works
559 like it always used to, and the difference will be irrelevant.
561 If you remove 'device random', you get *NO* kernel-processed
562 entropy at all. This may be acceptable to folks building
563 embedded systems, but has complications. Carry on reading,
564 and it is assumed you know what you need.
566 *PLEASE* read random(4) and random(9) if you are in the
567 habit of tweaking kernel configs, and/or if you are a member
568 of the embedded community, wanting specific and not-usual
569 behaviour from your security subsystems.
571 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
572 random', you will NOT have a functioning /dev/random, and
573 many cryptographic features will not work, including SSH.
574 You may also find strange behaviour from the random(3) set
575 of library functions, in particular sranddev(3), srandomdev(3)
576 and arc4random(3). The reason for this is that the KERN_ARND
577 sysctl only returns entropy if it thinks it has some to
578 share, and with RANDOM_DUMMY or no 'device random' this
582 An additional fix for the issue described in the 20150614 sendmail
583 entry below has been been committed in revision 284717.
586 FreeBSD's old make (fmake) has been removed from the system. It is
587 available as the devel/fmake port or via pkg install fmake.
590 The fix for the issue described in the 20150614 sendmail entry
591 below has been been committed in revision 284436. The work
592 around described in that entry is no longer needed unless the
593 default setting is overridden by a confDH_PARAMETERS configuration
594 setting of '5' or pointing to a 512 bit DH parameter file.
597 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
598 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
599 and devel/kyua to version 0.20+ and adjust any calling code to work
600 with Kyuafile and kyua.
603 The import of openssl to address the FreeBSD-SA-15:10.openssl
604 security advisory includes a change which rejects handshakes
605 with DH parameters below 768 bits. sendmail releases prior
606 to 8.15.2 (not yet released), defaulted to a 512 bit
607 DH parameter setting for client connections. To work around
608 this interoperability, sendmail can be configured to use a
609 2048 bit DH parameter by:
611 1. Edit /etc/mail/`hostname`.mc
612 2. If a setting for confDH_PARAMETERS does not exist or
613 exists and is set to a string beginning with '5',
615 3. If a setting for confDH_PARAMETERS exists and is set to
616 a file path, create a new file with:
617 openssl dhparam -out /path/to/file 2048
618 4. Rebuild the .cf file:
619 cd /etc/mail/; make; make install
621 cd /etc/mail/; make restart
623 A sendmail patch is coming, at which time this file will be
627 Generation of legacy formatted entries have been disabled by default
628 in pwd_mkdb(8), as all base system consumers of the legacy formatted
629 entries were converted to use the new format by default when the new,
630 machine independent format have been added and supported since FreeBSD
633 Please see the pwd_mkdb(8) manual page for further details.
636 Clang and llvm have been upgraded to 3.6.1 release. Please see the
637 20141231 entry below for information about prerequisites and upgrading,
638 if you are not already using 3.5.0 or higher.
641 TI platform code switched to using vendor DTS files and this update
642 may break existing systems running on Beaglebone, Beaglebone Black,
645 - dtb files should be regenerated/reinstalled. Filenames are the
646 same but content is different now
647 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
648 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
649 addressing scheme is now pin 25 on /dev/gpioc3.
650 - Pandaboard: /etc/ttys should be updated, serial console device is
651 now /dev/ttyu2, not /dev/ttyu0
654 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
655 If you need the GNU extension from groff soelim(1), install groff
656 from package: pkg install groff, or via ports: textproc/groff.
659 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
660 defined in symlink(7); previously symlinks were silently ignored.
663 The const qualifier has been removed from iconv(3) to comply with
664 POSIX. The ports tree is aware of this from r384038 onwards.
667 Libraries specified by LIBADD in Makefiles must have a corresponding
668 DPADD_<lib> variable to ensure correct dependencies. This is now
669 enforced in src.libnames.mk.
672 From legacy ata(4) driver was removed support for SATA controllers
673 supported by more functional drivers ahci(4), siis(4) and mvs(4).
674 Kernel modules ataahci and ataadaptec were removed completely,
675 replaced by ahci and mvs modules respectively.
678 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
679 the 20141231 entry below for information about prerequisites and
680 upgrading, if you are not already using 3.5.0 or higher.
683 The 32-bit PowerPC kernel has been changed to a position-independent
684 executable. This can only be booted with a version of loader(8)
685 newer than January 31, 2015, so make sure to update both world and
686 kernel before rebooting.
689 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
690 but before r278950, the RNG was not seeded properly. Immediately
691 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
692 ssh keys or openssl keys) that were generated w/ a kernel from that
693 range. This does not affect programs that directly used /dev/random
694 or /dev/urandom. All userland uses of arc4random(3) are affected.
697 The autofs(4) ABI was changed in order to restore binary compatibility
698 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
702 The powerpc64 kernel has been changed to a position-independent
703 executable. This can only be booted with a new version of loader(8),
704 so make sure to update both world and kernel before rebooting.
707 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
708 only release, no new features have been added. Please see the 20141231
709 entry below for information about prerequisites and upgrading, if you
710 are not already using 3.5.0.
713 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
714 taken from the ELF Tool Chain project rather than GNU binutils. They
715 should be drop-in replacements, with the addition of arm64 support.
716 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
717 binutils tools, if necessary. See 20150805 for updated information.
720 The default Unbound configuration now enables remote control
721 using a local socket. Users who have already enabled the
722 local_unbound service should regenerate their configuration
723 by running "service local_unbound setup" as root.
726 The GNU texinfo and GNU info pages have been removed.
727 To be able to view GNU info pages please install texinfo from ports.
730 Clang, llvm and lldb have been upgraded to 3.5.0 release.
732 As of this release, a prerequisite for building clang, llvm and lldb is
733 a C++11 capable compiler and C++11 standard library. This means that to
734 be able to successfully build the cross-tools stage of buildworld, with
735 clang as the bootstrap compiler, your system compiler or cross compiler
736 should either be clang 3.3 or later, or gcc 4.8 or later, and your
737 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
740 On any standard FreeBSD 10.x or 11.x installation, where clang and
741 libc++ are on by default (that is, on x86 or arm), this should work out
744 On 9.x installations where clang is enabled by default, e.g. on x86 and
745 powerpc, libc++ will not be enabled by default, so libc++ should be
746 built (with clang) and installed first. If both clang and libc++ are
747 missing, build clang first, then use it to build libc++.
749 On 8.x and earlier installations, upgrade to 9.x first, and then follow
750 the instructions for 9.x above.
752 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
753 default, and do not build clang.
755 Many embedded systems are resource constrained, and will not be able to
756 build clang in a reasonable time, or in some cases at all. In those
757 cases, cross building bootable systems on amd64 is a workaround.
759 This new version of clang introduces a number of new warnings, of which
760 the following are most likely to appear:
764 This warns in two cases, for both C and C++:
765 * When the code is trying to take the absolute value of an unsigned
766 quantity, which is effectively a no-op, and almost never what was
767 intended. The code should be fixed, if at all possible. If you are
768 sure that the unsigned quantity can be safely cast to signed, without
769 loss of information or undefined behavior, you can add an explicit
770 cast, or disable the warning.
772 * When the code is trying to take an absolute value, but the called
773 abs() variant is for the wrong type, which can lead to truncation.
774 If you want to disable the warning instead of fixing the code, please
775 make sure that truncation will not occur, or it might lead to unwanted
778 -Wtautological-undefined-compare and
779 -Wundefined-bool-conversion
781 These warn when C++ code is trying to compare 'this' against NULL, while
782 'this' should never be NULL in well-defined C++ code. However, there is
783 some legacy (pre C++11) code out there, which actively abuses this
784 feature, which was less strictly defined in previous C++ versions.
786 Squid and openjdk do this, for example. The warning can be turned off
787 for C++98 and earlier, but compiling the code in C++11 mode might result
788 in unexpected behavior; for example, the parts of the program that are
789 unreachable could be optimized away.
792 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
793 kernel sources have been removed. The .h files remain, since some
794 utilities include them. This will need to be fixed later.
795 If "mount -t oldnfs ..." is attempted, it will fail.
796 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
797 the utilities will report errors.
800 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
801 directories to top level SUBDIR variable when their parent
802 directory is included in LOCAL_DIRS. Users with build systems with
803 such hierarchies and without SUBDIR entries in the parent
804 directory Makefiles should add them or add the directories to
808 faith(4) and faithd(8) have been removed from the base system. Faith
809 has been obsolete for a very long time.
812 vt(4), the new console driver, is enabled by default. It brings
813 support for Unicode and double-width characters, as well as
814 support for UEFI and integration with the KMS kernel video
817 You may need to update your console settings in /etc/rc.conf,
818 most probably the keymap. During boot, /etc/rc.d/syscons will
819 indicate what you need to do.
821 vt(4) still has issues and lacks some features compared to
822 syscons(4). See the wiki for up-to-date information:
823 https://wiki.freebsd.org/Newcons
825 If you want to keep using syscons(4), you can do so by adding
826 the following line to /boot/loader.conf:
830 pjdfstest has been integrated into kyua as an opt-in test suite.
831 Please see share/doc/pjdfstest/README for more details on how to
835 gperf has been removed from the base system for architectures
836 that use clang. Ports that require gperf will obtain it from the
840 pjdfstest has been moved from tools/regression/pjdfstest to
844 At svn r271982, The default linux compat kernel ABI has been adjusted
845 to 2.6.18 in support of the linux-c6 compat ports infrastructure
846 update. If you wish to continue using the linux-f10 compat ports,
847 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
848 encouraged to update their linux-compat packages to linux-c6 during
849 their next update cycle.
852 The ofwfb driver, used to provide a graphics console on PowerPC when
853 using vt(4), no longer allows mmap() of all physical memory. This
854 will prevent Xorg on PowerPC with some ATI graphics cards from
855 initializing properly unless x11-servers/xorg-server is updated to
859 The xdev targets have been converted to using TARGET and
860 TARGET_ARCH instead of XDEV and XDEV_ARCH.
863 The default unbound configuration has been modified to address
864 issues with reverse lookups on networks that use private
865 address ranges. If you use the local_unbound service, run
866 "service local_unbound setup" as root to regenerate your
867 configuration, then "service local_unbound reload" to load the
871 The GNU texinfo and GNU info pages are not built and installed
872 anymore, WITH_INFO knob has been added to allow to built and install
874 UPDATE: see 20150102 entry on texinfo's removal
877 The GNU readline library is now an INTERNALLIB - that is, it is
878 statically linked into consumers (GDB and variants) in the base
879 system, and the shared library is no longer installed. The
880 devel/readline port is available for third party software that
884 The Itanium architecture (ia64) has been removed from the list of
885 known architectures. This is the first step in the removal of the
889 Commit r268115 has added NFSv4.1 server support, merged from
890 projects/nfsv4.1-server. Since this includes changes to the
891 internal interfaces between the NFS related modules, a full
892 build of the kernel and modules will be necessary.
893 __FreeBSD_version has been bumped.
896 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
897 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
898 which differs from the behaviour controlled by this knob.)
901 Maximal length of the serial number in CTL was increased from 16 to
902 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
903 and ctld, need to be rebuilt to work with a new kernel.
906 The libatf-c and libatf-c++ major versions were downgraded to 0 and
907 1 respectively to match the upstream numbers. They were out of
908 sync because, when they were originally added to FreeBSD, the
909 upstream versions were not respected. These libraries are private
910 and not yet built by default, so renumbering them should be a
911 non-issue. However, unclean source trees will yield broken test
912 programs once the operator executes "make delete-old-libs" after a
915 Additionally, the atf-sh binary was made private by moving it into
916 /usr/libexec/. Already-built shell test programs will keep the
917 path to the old binary so they will break after "make delete-old"
920 If you are using WITH_TESTS=yes (not the default), wipe the object
921 tree and rebuild from scratch to prevent spurious test failures.
922 This is only needed once: the misnumbered libraries and misplaced
923 binaries have been added to OptionalObsoleteFiles.inc so they will
924 be removed during a clean upgrade.
927 Clang and llvm have been upgraded to 3.4.1 release.
930 We bogusly installed src.opts.mk in /usr/share/mk. This file should
931 be removed to avoid issues in the future (and has been added to
935 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
936 past, it affected all builds that used the bsd.*.mk files. The old
937 behavior was a bug, but people may have relied upon it. To get this
938 behavior back, you can .include /etc/src.conf from /etc/make.conf
939 (which is still global and isn't changed). This also changes the
940 behavior of incremental builds inside the tree of individual
941 directories. Set MAKESYSPATH to ".../share/mk" to do that.
942 Although this has survived make universe and some upgrade scenarios,
943 other upgrade scenarios may have broken. At least one form of
944 temporary breakage was fixed with MAKESYSPATH settings for buildworld
945 as well... In cases where MAKESYSPATH isn't working with this
946 setting, you'll need to set it to the full path to your tree.
948 One side effect of all this cleaning up is that bsd.compiler.mk
949 is no longer implicitly included by bsd.own.mk. If you wish to
950 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
954 The lindev device has been removed since /dev/full has been made a
955 standard device. __FreeBSD_version has been bumped.
958 The knob WITHOUT_VI was added to the base system, which controls
959 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
960 in order to reorder files share/termcap and didn't build ex(1) as a
961 build tool, so building/installing with WITH_VI is highly advised for
962 build hosts for older releases.
964 This issue has been fixed in stable/9 and stable/10 in r277022 and
965 r276991, respectively.
968 The YES_HESIOD knob has been removed. It has been obsolete for
969 a decade. Please move to using WITH_HESIOD instead or your builds
970 will silently lack HESIOD.
973 The uart(4) driver has been changed with respect to its handling
974 of the low-level console. Previously the uart(4) driver prevented
975 any process from changing the baudrate or the CLOCAL and HUPCL
976 control flags. By removing the restrictions, operators can make
977 changes to the serial console port without having to reboot.
978 However, when getty(8) is started on the serial device that is
979 associated with the low-level console, a misconfigured terminal
980 line in /etc/ttys will now have a real impact.
981 Before upgrading the kernel, make sure that /etc/ttys has the
982 serial console device configured as 3wire without baudrate to
983 preserve the previous behaviour. E.g:
984 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
987 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
988 to improve performance. To re-enable it, if needed, run rpcbind
989 with command line option -W.
992 Switched back to the GPL dtc compiler due to updates in the upstream
993 dts files not being supported by the BSDL dtc compiler. You will need
994 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
995 may result while building dtb files during a kernel build if you fail
996 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
999 Clang and llvm have been upgraded to 3.4 release.
1002 The nve(4) driver has been removed. Please use the nfe(4) driver
1003 for NVIDIA nForce MCP Ethernet adapters instead.
1006 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1007 This could cause certain C++ applications using shared libraries built
1008 against the previous version of libc++ to crash. The incompatibility
1009 has now been fixed, but any C++ applications or shared libraries built
1010 between r261283 and r261801 should be recompiled.
1013 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1014 capability mode support. Please note that enabling the feature in
1015 kernel is still highly recommended.
1018 OpenSSH is now built with sandbox support, and will use sandbox as
1019 the default privilege separation method. This requires Capsicum
1020 capability mode support in kernel.
1023 The libelf and libdwarf libraries have been updated to newer
1024 versions from upstream. Shared library version numbers for
1025 these two libraries were bumped. Any ports or binaries
1026 requiring these two libraries should be recompiled.
1027 __FreeBSD_version is bumped to 1100006.
1030 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1031 instead of providing an explicit one, this would prevent such
1032 Makefile from providing its own Kyuafile in the future during
1033 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1034 intervention is needed to clean an objdir if you use NO_CLEAN:
1035 # find /usr/obj -name Kyuafile | xargs rm -f
1038 The behavior of gss_pseudo_random() for the krb5 mechanism
1039 has changed, for applications requesting a longer random string
1040 than produced by the underlying enctype's pseudo-random() function.
1041 In particular, the random string produced from a session key of
1042 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1043 be different at the 17th octet and later, after this change.
1044 The counter used in the PRF+ construction is now encoded as a
1045 big-endian integer in accordance with RFC 4402.
1046 __FreeBSD_version is bumped to 1100004.
1049 The WITHOUT_ATF build knob has been removed and its functionality
1050 has been subsumed into the more generic WITHOUT_TESTS. If you were
1051 using the former to disable the build of the ATF libraries, you
1052 should change your settings to use the latter.
1055 The default version of mtree is nmtree which is obtained from
1056 NetBSD. The output is generally the same, but may vary
1057 slightly. If you found you need identical output adding
1058 "-F freebsd9" to the command line should do the trick. For the
1059 time being, the old mtree is available as fmtree.
1062 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1063 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1064 1.1.4_8 and verify bsdyml not linked in, before running "make
1066 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1068 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1071 The stable/10 branch has been created in subversion from head
1075 The rc.d/jail script has been updated to support jail(8)
1076 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1077 for per-jail configuration are automatically converted to
1078 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1079 This is transparently backward compatible. See below about some
1080 incompatibilities and rc.conf(5) manual page for more details.
1082 These variables are now deprecated in favor of jail(8) configuration
1083 file. One can use "rc.d/jail config <jname>" command to generate
1084 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1085 running the jail(8) utility. The default pathname of the
1086 configuration file is /etc/jail.conf and can be specified by
1087 using $jail_conf or $jail_<jname>_conf variables.
1089 Please note that jail_devfs_ruleset accepts an integer at
1090 this moment. Please consider to rewrite the ruleset name
1094 BIND has been removed from the base system. If all you need
1095 is a local resolver, simply enable and start the local_unbound
1096 service instead. Otherwise, several versions of BIND are
1097 available in the ports tree. The dns/bind99 port is one example.
1099 With this change, nslookup(1) and dig(1) are no longer in the base
1100 system. Users should instead use host(1) and drill(1) which are
1101 in the base system. Alternatively, nslookup and dig can
1102 be obtained by installing the dns/bind-tools port.
1105 With the addition of unbound(8), a new unbound user is now
1106 required during installworld. "mergemaster -p" can be used to
1107 add the user prior to installworld, as documented in the handbook.
1110 OpenSSH is now built with DNSSEC support, and will by default
1111 silently trust signed SSHFP records. This can be controlled with
1112 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1113 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1116 The GNU Compiler Collection and C++ standard library (libstdc++)
1117 are no longer built by default on platforms where clang is the system
1118 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1119 options in src.conf.
1122 The PROCDESC kernel option is now part of the GENERIC kernel
1123 configuration and is required for the rwhod(8) to work.
1124 If you are using custom kernel configuration, you should include
1128 The API and ABI related to the Capsicum framework was modified
1129 in backward incompatible way. The userland libraries and programs
1130 have to be recompiled to work with the new kernel. This includes the
1131 following libraries and programs, but the whole buildworld is
1132 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1133 kdump, procstat, rwho, rwhod, uniq.
1136 AES-NI intrinsic support has been added to gcc. The AES-NI module
1137 has been updated to use this support. A new gcc is required to build
1138 the aesni module on both i386 and amd64.
1141 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1142 Thus "device padlock_rng" and "device rdrand_rng" should be
1143 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1146 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1147 enables just the iconv* functionality and is now on by default.
1148 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1149 compatibility. Set WITHOUT_ICONV to build the old way.
1150 If you have been using WITH_ICONV before, you will very likely
1151 need to turn on WITH_LIBICONV_COMPAT.
1154 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1155 Illumos origin, including ZFS. If you have INVARIANTS in your
1156 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1158 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1159 locks if WITNESS option was set. Because that generated a lot of
1160 witness(9) reports and all of them were believed to be false
1161 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1162 can be used to achieve the previous behavior.
1165 Timer values in IPv6 data structures now use time_uptime instead
1166 of time_second. Although this is not a user-visible functional
1167 change, userland utilities which directly use them---ndp(8),
1168 rtadvd(8), and rtsold(8) in the base system---need to be updated
1169 to r253970 or later.
1172 find -delete can now delete the pathnames given as arguments,
1173 instead of only files found below them or if the pathname did
1174 not contain any slashes. Formerly, the following error message
1177 find: -delete: <path>: relative path potentially not safe
1179 Deleting the pathnames given as arguments can be prevented
1180 without error messages using -mindepth 1 or by changing
1181 directory and passing "." as argument to find. This works in the
1182 old as well as the new version of find.
1185 Behavior of devfs rules path matching has been changed.
1186 Pattern is now always matched against fully qualified devfs
1187 path and slash characters must be explicitly matched by
1188 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1189 subdirectories must be reviewed.
1192 The default ARM ABI has changed to the ARM EABI. The old ABI is
1193 incompatible with the ARM EABI and all programs and modules will
1194 need to be rebuilt to work with a new kernel.
1196 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1198 NOTE: Support for the old ABI will be removed in the future and
1199 users are advised to upgrade.
1202 pkg_install has been disconnected from the build if you really need it
1203 you should add WITH_PKGTOOLS in your src.conf(5).
1206 Most of network statistics structures were changed to be able
1207 keep 64-bits counters. Thus all tools, that work with networking
1208 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1211 Fix a bug that allowed a tracing process (e.g. gdb) to write
1212 to a memory-mapped file in the traced process's address space
1213 even if neither the traced process nor the tracing process had
1214 write access to that file.
1217 CVS has been removed from the base system. An exact copy
1218 of the code is available from the devel/cvs port.
1221 Some people report the following error after the switch to bmake:
1223 make: illegal option -- J
1224 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1226 *** [buildworld] Error code 2
1228 this likely due to an old instance of make in
1229 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1230 which src/Makefile will use that blindly, if it exists, so if
1231 you see the above error:
1233 rm -rf `make -V MAKEPATH`
1238 Use bmake by default.
1239 Whereas before one could choose to build with bmake via
1240 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1241 make. The goal is to remove these knobs for 10-RELEASE.
1243 It is worth noting that bmake (like gmake) treats the command
1244 line as the unit of failure, rather than statements within the
1245 command line. Thus '(cd some/where && dosomething)' is safer
1246 than 'cd some/where; dosomething'. The '()' allows consistent
1247 behavior in parallel build.
1250 Fix a bug that allows NFS clients to issue READDIR on files.
1253 The WITHOUT_IDEA option has been removed because
1254 the IDEA patent expired.
1257 The sysctl which controls TRIM support under ZFS has been renamed
1258 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1262 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1263 rather than creating it's own in the temporary directory in
1264 order allow access to bootstrapped versions of tools such as
1265 install and mtree. When upgrading from version of FreeBSD where
1266 the install command does not support -l, you will need to
1267 install a new mergemaster command if mergemaster -p is required.
1268 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1272 Legacy ATA stack, disabled and replaced by new CAM-based one since
1273 FreeBSD 9.0, completely removed from the sources. Kernel modules
1274 atadisk and atapi*, user-level tools atacontrol and burncd are
1275 removed. Kernel option `options ATA_CAM` is now permanently enabled
1279 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1280 and socketpair(2). Software, in particular Kerberos, may
1281 automatically detect and use these during building. The resulting
1282 binaries will not work on older kernels.
1285 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1286 information, see the respective 20130304 entry).
1289 Recent commits to callout(9) changed the size of struct callout,
1290 so the KBI is probably heavily disturbed. Also, some functions
1291 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1292 by macros. Every kernel module using it won't load, so rebuild
1295 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1296 but does not initialize by default (because of the new CTL_DISABLE
1297 option) to save memory. To re-enable it, remove the CTL_DISABLE
1298 option from the kernel config file or set kern.cam.ctl.disable=0
1299 in /boot/loader.conf.
1302 The ctl device has been disabled in GENERIC for i386 and amd64.
1303 This was done due to the extra memory being allocated at system
1304 initialisation time by the ctl driver which was only used if
1305 a CAM target device was created. This makes a FreeBSD system
1306 unusable on 128MB or less of RAM.
1309 A new compression method (lz4) has been merged to -HEAD. Please
1310 refer to zpool-features(7) for more information.
1312 Please refer to the "ZFS notes" section of this file for information
1313 on upgrading boot ZFS pools.
1316 A BSD-licensed patch(1) variant has been added and is installed
1317 as bsdpatch, being the GNU version the default patch.
1318 To inverse the logic and use the BSD-licensed one as default,
1319 while having the GNU version installed as gnupatch, rebuild
1320 and install world with the WITH_BSD_PATCH knob set.
1323 Due to the use of the new -l option to install(1) during build
1324 and install, you must take care not to directly set the INSTALL
1325 make variable in your /etc/make.conf, /etc/src.conf, or on the
1326 command line. If you wish to use the -C flag for all installs
1327 you may be able to add INSTALL+=-C to /etc/make.conf or
1331 The install(1) option -M has changed meaning and now takes an
1332 argument that is a file or path to append logs to. In the
1333 unlikely event that -M was the last option on the command line
1334 and the command line contained at least two files and a target
1335 directory the first file will have logs appended to it. The -M
1336 option served little practical purpose in the last decade so its
1337 use is expected to be extremely rare.
1340 After switching to Clang as the default compiler some users of ZFS
1341 on i386 systems started to experience stack overflow kernel panics.
1342 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1345 GEOM_LABEL now mangles label names read from file system metadata.
1346 Mangling affect labels containing spaces, non-printable characters,
1347 '%' or '"'. Device names in /etc/fstab and other places may need to
1351 By default, only the 10 most recent kernel dumps will be saved. To
1352 restore the previous behaviour (no limit on the number of kernel dumps
1353 stored in the dump directory) add the following line to /etc/rc.conf:
1358 With the addition of auditdistd(8), a new auditdistd user is now
1359 required during installworld. "mergemaster -p" can be used to
1360 add the user prior to installworld, as documented in the handbook.
1363 The sin6_scope_id member variable in struct sockaddr_in6 is now
1364 filled by the kernel before passing the structure to the userland via
1365 sysctl or routing socket. This means the KAME-specific embedded scope
1366 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1367 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1368 __FreeBSD_version is bumped to 1000025.
1371 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1372 This means that the world and kernel will be compiled with clang
1373 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1374 and /usr/bin/cpp. To disable this behavior and revert to building
1375 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1376 of current may need to bootstrap WITHOUT_CLANG first if the clang
1377 build fails (its compatibility window doesn't extend to the 9 stable
1381 The IPFIREWALL_FORWARD kernel option has been removed. Its
1382 functionality now turned on by default.
1385 The ZERO_COPY_SOCKET kernel option has been removed and
1386 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1387 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1388 mechanism which is not safe and may result in kernel crashes.
1389 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1390 driver supports disposeable external page sized mbuf storage.
1391 Proper replacements for both zero-copy mechanisms are under
1392 consideration and will eventually lead to complete removal
1393 of the two kernel options.
1396 The IPv4 network stack has been converted to network byte
1397 order. The following modules need to be recompiled together
1398 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1399 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1402 Support for non-MPSAFE filesystems was removed from VFS. The
1403 VFS_VERSION was bumped, all filesystem modules shall be
1407 All the non-MPSAFE filesystems have been disconnected from
1408 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1409 portalfs, smbfs, xfs.
1412 The interface cloning API and ABI has changed. The following
1413 modules need to be recompiled together with kernel:
1414 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1415 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1416 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1419 The sdhci driver was split in two parts: sdhci (generic SD Host
1420 Controller logic) and sdhci_pci (actual hardware driver).
1421 No kernel config modifications are required, but if you
1422 load sdhc as a module you must switch to sdhci_pci instead.
1425 Import the FUSE kernel and userland support into base system.
1428 The GNU sort(1) program has been removed since the BSD-licensed
1429 sort(1) has been the default for quite some time and no serious
1430 problems have been reported. The corresponding WITH_GNU_SORT
1434 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1435 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1439 The net80211(4) ABI has been changed to allow for improved driver
1440 PS-POLL and power-save support. All wireless drivers need to be
1441 recompiled to work with the new kernel.
1444 The random(4) support for the VIA hardware random number
1445 generator (`PADLOCK') is no longer enabled unconditionally.
1446 Add the padlock_rng device in the custom kernel config if
1447 needed. The GENERIC kernels on i386 and amd64 do include the
1448 device, so the change only affects the custom kernel
1452 The pf(4) packet filter ABI has been changed. pfctl(8) and
1453 snmp_pf module need to be recompiled to work with new kernel.
1456 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1457 to -HEAD. Pools that have empty_bpobj in active state can not be
1458 imported read-write with ZFS implementations that do not support
1459 this feature. For more information read the zpool-features(5)
1463 The sparc64 ZFS loader has been changed to no longer try to auto-
1464 detect ZFS providers based on diskN aliases but now requires these
1465 to be explicitly listed in the OFW boot-device environment variable.
1468 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1469 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1470 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1473 The following sysctls and tunables have been renamed for consistency
1474 with other variables:
1475 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1476 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1479 The sort utility has been replaced with BSD sort. For now, GNU sort
1480 is also available as "gnusort" or the default can be set back to
1481 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1482 installed as "bsdsort".
1485 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1486 Starting with this version the old system of ZFS pool versioning
1487 is superseded by "feature flags". This concept enables forward
1488 compatibility against certain future changes in functionality of ZFS
1489 pools. The first read-only compatible "feature flag" for ZFS pools
1490 is named "com.delphix:async_destroy". For more information
1491 read the new zpool-features(5) manual page.
1492 Please refer to the "ZFS notes" section of this file for information
1493 on upgrading boot ZFS pools.
1496 The malloc(3) implementation embedded in libc now uses sources imported
1497 as contrib/jemalloc. The most disruptive API change is to
1498 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1499 delete it prior to installworld, and optionally re-create it using the
1500 new format after rebooting. See malloc.conf(5) for details
1501 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1505 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1506 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1507 now spelled mips. This is to aid compatibility with third-party
1508 software that expects this naming scheme in uname(3). Little-endian
1509 settings are unchanged. If you are updating a big-endian mips64 machine
1510 from before this change, you may need to set MACHINE_ARCH=mips64 in
1511 your environment before the new build system will recognize your machine.
1514 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1518 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1519 nullfs(5) did not pass through all behaviours to the underlying layer,
1520 as a result if we bound to a socket on the lower layer we could connect
1521 only to the lower path; if we bound to the upper layer we could connect
1522 only to the upper path. The new behavior is one can connect to both the
1523 lower and the upper paths regardless what layer path one binds to.
1526 The getifaddrs upgrade path broken with 20111215 has been restored.
1527 If you have upgraded in between 20111215 and 20120209 you need to
1528 recompile libc again with your kernel. You still need to recompile
1529 world to be able to configure CARP but this restriction already
1530 comes from 20111215.
1533 The set_rcvar() function has been removed from /etc/rc.subr. All
1534 base and ports rc.d scripts have been updated, so if you have a
1535 port installed with a script in /usr/local/etc/rc.d you can either
1536 hand-edit the rcvar= line, or reinstall the port.
1538 An easy way to handle the mass-update of /etc/rc.d:
1539 rm /etc/rc.d/* && mergemaster -i
1542 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1543 on the current CPU and prevents other threads from running.
1544 This behavior can be reverted using the kern.stop_scheduler_on_panic
1546 The new behavior can be incompatible with kern.sync_on_panic.
1549 The carp(4) facility has been changed significantly. Configuration
1550 of the CARP protocol via ifconfig(8) has changed, as well as format
1551 of CARP events submitted to devd(8) has changed. See manual pages
1552 for more information. The arpbalance feature of carp(4) is currently
1553 not supported anymore.
1555 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1556 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1557 need to be recompiled.
1560 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1564 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1565 explicitely support non-MPSAFE filesystems.
1566 It is on by default for all supported platform at this present
1570 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1571 i386 and pc98 GENERIC kernel configuration files.
1574 sysinstall has been removed
1577 The stable/9 branch created in subversion. This corresponds to the
1578 RELENG_9 branch in CVS.
1584 Avoid using make -j when upgrading. While generally safe, there are
1585 sometimes problems using -j to upgrade. If your upgrade fails with
1586 -j, please try again without -j. From time to time in the past there
1587 have been problems using -j with buildworld and/or installworld. This
1588 is especially true when upgrading between "distant" versions (eg one
1589 that cross a major release boundary or several minor releases, or when
1590 several months have passed on the -current branch).
1592 Sometimes, obscure build problems are the result of environment
1593 poisoning. This can happen because the make utility reads its
1594 environment when searching for values for global variables. To run
1595 your build attempts in an "environmental clean room", prefix all make
1596 commands with 'env -i '. See the env(1) manual page for more details.
1598 When upgrading from one major version to another it is generally best to
1599 upgrade to the latest code in the currently installed branch first, then
1600 do an upgrade to the new branch. This is the best-tested upgrade path,
1601 and has the highest probability of being successful. Please try this
1602 approach if you encounter problems with a major version upgrade. Since
1603 the stable 4.x branch point, one has generally been able to upgade from
1604 anywhere in the most recent stable branch to head / current (or even the
1605 last couple of stable branches). See the top of this file when there's
1608 When upgrading a live system, having a root shell around before
1609 installing anything can help undo problems. Not having a root shell
1610 around can lead to problems if pam has changed too much from your
1611 starting point to allow continued authentication after the upgrade.
1613 This file should be read as a log of events. When a later event changes
1614 information of a prior event, the prior event should not be deleted.
1615 Instead, a pointer to the entry with the new information should be
1616 placed in the old entry. Readers of this file should also sanity check
1617 older entries before relying on them blindly. Authors of new entries
1618 should write them with this in mind.
1622 When upgrading the boot ZFS pool to a new version, always follow
1625 1.) recompile and reinstall the ZFS boot loader and boot block
1626 (this is part of "make buildworld" and "make installworld")
1628 2.) update the ZFS boot block on your boot drive
1630 The following example updates the ZFS boot block on the first
1631 partition (freebsd-boot) of a GPT partitioned drive ada0:
1632 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1634 Non-boot pools do not need these updates.
1638 If you are updating from a prior version of FreeBSD (even one just
1639 a few days old), you should follow this procedure. It is the most
1640 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1642 make kernel-toolchain
1643 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1644 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1646 To test a kernel once
1647 ---------------------
1648 If you just want to boot a kernel once (because you are not sure
1649 if it works, or if you want to boot a known bad kernel to provide
1650 debugging information) run
1651 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1652 nextboot -k testkernel
1654 To just build a kernel when you know that it won't mess you up
1655 --------------------------------------------------------------
1656 This assumes you are already running a CURRENT system. Replace
1657 ${arch} with the architecture of your machine (e.g. "i386",
1658 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1660 cd src/sys/${arch}/conf
1661 config KERNEL_NAME_HERE
1662 cd ../compile/KERNEL_NAME_HERE
1667 If this fails, go to the "To build a kernel" section.
1669 To rebuild everything and install it on the current system.
1670 -----------------------------------------------------------
1671 # Note: sometimes if you are running current you gotta do more than
1672 # is listed here if you are upgrading from a really old current.
1674 <make sure you have good level 0 dumps>
1676 make kernel KERNCONF=YOUR_KERNEL_HERE
1678 <reboot in single user> [3]
1685 To cross-install current onto a separate partition
1686 --------------------------------------------------
1687 # In this approach we use a separate partition to hold
1688 # current's root, 'usr', and 'var' directories. A partition
1689 # holding "/", "/usr" and "/var" should be about 2GB in
1692 <make sure you have good level 0 dumps>
1695 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1696 <maybe newfs current's root partition>
1697 <mount current's root partition on directory ${CURRENT_ROOT}>
1698 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1699 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1700 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1701 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1702 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1703 <reboot into current>
1704 <do a "native" rebuild/install as described in the previous section>
1705 <maybe install compatibility libraries from ports/misc/compat*>
1709 To upgrade in-place from stable to current
1710 ----------------------------------------------
1711 <make sure you have good level 0 dumps>
1713 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1715 <reboot in single user> [3]
1722 Make sure that you've read the UPDATING file to understand the
1723 tweaks to various things you need. At this point in the life
1724 cycle of current, things change often and you are on your own
1725 to cope. The defaults can also change, so please read ALL of
1726 the UPDATING entries.
1728 Also, if you are tracking -current, you must be subscribed to
1729 freebsd-current@freebsd.org. Make sure that before you update
1730 your sources that you have read and understood all the recent
1731 messages there. If in doubt, please track -stable which has
1732 much fewer pitfalls.
1734 [1] If you have third party modules, such as vmware, you
1735 should disable them at this point so they don't crash your
1738 [3] From the bootblocks, boot -s, and then do
1743 adjkerntz -i # if CMOS is wall time
1744 Also, when doing a major release upgrade, it is required that
1745 you boot into single user mode to do the installworld.
1747 [4] Note: This step is non-optional. Failure to do this step
1748 can result in a significant reduction in the functionality of the
1749 system. Attempting to do it by hand is not recommended and those
1750 that pursue this avenue should read this file carefully, as well
1751 as the archives of freebsd-current and freebsd-hackers mailing lists
1752 for potential gotchas. The -U option is also useful to consider.
1753 See mergemaster(8) for more information.
1755 [5] Usually this step is a noop. However, from time to time
1756 you may need to do this if you get unknown user in the following
1757 step. It never hurts to do it all the time. You may need to
1758 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1759 install) after the buildworld before this step if you last updated
1760 from current before 20130425 or from -stable before 20130430.
1762 [6] This only deletes old files and directories. Old libraries
1763 can be deleted by "make delete-old-libs", but you have to make
1764 sure that no program is using those libraries anymore.
1766 [8] In order to have a kernel that can run the 4.x binaries needed to
1767 do an installworld, you must include the COMPAT_FREEBSD4 option in
1768 your kernel. Failure to do so may leave you with a system that is
1769 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1770 required to run the 5.x binaries on more recent kernels. And so on
1771 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1773 Make sure that you merge any new devices from GENERIC since the
1774 last time you updated your kernel config file.
1776 [9] When checking out sources, you must include the -P flag to have
1777 cvs prune empty directories.
1779 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1780 "?=" instead of the "=" assignment operator, so that buildworld can
1781 override the CPUTYPE if it needs to.
1783 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1784 not on the command line, or in /etc/make.conf. buildworld will
1785 warn if it is improperly defined.
1788 This file contains a list, in reverse chronological order, of major
1789 breakages in tracking -current. It is not guaranteed to be a complete
1790 list of such breakages, and only contains entries since September 23, 2011.
1791 If you need to see UPDATING entries from before that date, you will need
1792 to fetch an UPDATING file from an older FreeBSD release.
1794 Copyright information:
1796 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1798 Redistribution, publication, translation and use, with or without
1799 modification, in full or in part, in any form or format of this
1800 document are permitted without further permission from the author.
1802 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1803 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1804 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1805 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1806 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1807 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1808 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1809 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1810 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1811 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1812 POSSIBILITY OF SUCH DAMAGE.
1814 Contact Warner Losh if you have any questions about your use of