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 from
17 older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW:
20 FreeBSD 11.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 Clang and llvm have been upgraded to 3.7.0. Please see the
36 20141231 entry below for information about prerequisites and upgrading,
37 if you are not already using 3.5.0 or higher.
40 /etc/make.conf now included earlier.
41 sys.mk now includes /etc/make.conf and {local,src}.sys.mk earlier
43 This makes it simple to interpose external toolchains etc.
44 However it may cause problems for users who have things like::
48 in /etc/make.conf, since INSTALL is not yet defined.
49 A safe fix for that is to have::
54 which is equivalent to previous behavior.
57 FreeBSD's old make (fmake) has been removed from the system. It is
58 available as the devel/fmake port or via pkg install fmake.
61 The fix for the issue described in the 20150614 sendmail entry
62 below has been been committed in revision 284436. The work
63 around described in that entry is no longer needed unless the
64 default setting is overridden by a confDH_PARAMETERS configuration
65 setting of '5' or pointing to a 512 bit DH parameter file.
68 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
69 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
70 and devel/kyua to version 0.20+ and adjust any calling code to work
71 with Kyuafile and kyua.
74 The import of openssl to address the FreeBSD-SA-15:10.openssl
75 security advisory includes a change which rejects handshakes
76 with DH parameters below 768 bits. sendmail releases prior
77 to 8.15.2 (not yet released), defaulted to a 512 bit
78 DH parameter setting for client connections. To work around
79 this interoperability, sendmail can be configured to use a
80 2048 bit DH parameter by:
82 1. Edit /etc/mail/`hostname`.mc
83 2. If a setting for confDH_PARAMETERS does not exist or
84 exists and is set to a string beginning with '5',
86 3. If a setting for confDH_PARAMETERS exists and is set to
87 a file path, create a new file with:
88 openssl dhparam -out /path/to/file 2048
89 4. Rebuild the .cf file:
90 cd /etc/mail/; make; make install
92 cd /etc/mail/; make restart
94 A sendmail patch is coming, at which time this file will be
98 Generation of legacy formatted entries have been disabled by default
99 in pwd_mkdb(8), as all base system consumers of the legacy formatted
100 entries were converted to use the new format by default when the new,
101 machine independent format have been added and supported since FreeBSD
104 Please see the pwd_mkdb(8) manual page for further details.
107 Clang and llvm have been upgraded to 3.6.1 release. Please see the
108 20141231 entry below for information about prerequisites and upgrading,
109 if you are not already using 3.5.0 or higher.
112 TI platform code switched to using vendor DTS files and this update
113 may break existing systems running on Beaglebone, Beaglebone Black,
116 - dtb files should be regenerated/reinstalled. Filenames are the
117 same but content is different now
118 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
119 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
120 addressing scheme is now pin 25 on /dev/gpioc3.
121 - Pandaboard: /etc/ttys should be updated, serial console device is
122 now /dev/ttyu2, not /dev/ttyu0
125 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
126 If you need the GNU extension from groff soelim(1), install groff
127 from package: pkg install groff, or via ports: textproc/groff.
130 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
131 defined in symlink(7); previously symlinks were silently ignored.
134 The const qualifier has been removed from iconv(3) to comply with
135 POSIX. The ports tree is aware of this from r384038 onwards.
138 Libraries specified by LIBADD in Makefiles must have a corresponding
139 DPADD_<lib> variable to ensure correct dependencies. This is now
140 enforced in src.libnames.mk.
143 From legacy ata(4) driver was removed support for SATA controllers
144 supported by more functional drivers ahci(4), siis(4) and mvs(4).
145 Kernel modules ataahci and ataadaptec were removed completely,
146 replaced by ahci and mvs modules respectively.
149 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
150 the 20141231 entry below for information about prerequisites and
151 upgrading, if you are not already using 3.5.0 or higher.
154 The 32-bit PowerPC kernel has been changed to a position-independent
155 executable. This can only be booted with a version of loader(8)
156 newer than January 31, 2015, so make sure to update both world and
157 kernel before rebooting.
160 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
161 but before r278950, the RNG was not seeded properly. Immediately
162 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
163 ssh keys or openssl keys) that were generated w/ a kernel from that
164 range. This does not affect programs that directly used /dev/random
165 or /dev/urandom. All userland uses of arc4random(3) are affected.
168 The autofs(4) ABI was changed in order to restore binary compatibility
169 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
173 The powerpc64 kernel has been changed to a position-independent
174 executable. This can only be booted with a new version of loader(8),
175 so make sure to update both world and kernel before rebooting.
178 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
179 only release, no new features have been added. Please see the 20141231
180 entry below for information about prerequisites and upgrading, if you
181 are not already using 3.5.0.
184 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
185 taken from the ELF Tool Chain project rather than GNU binutils. They
186 should be drop-in replacements, with the addition of arm64 support.
187 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
188 binutils tools, if necessary.
191 The default Unbound configuration now enables remote control
192 using a local socket. Users who have already enabled the
193 local_unbound service should regenerate their configuration
194 by running "service local_unbound setup" as root.
197 The GNU texinfo and GNU info pages have been removed.
198 To be able to view GNU info pages please install texinfo from ports.
201 Clang, llvm and lldb have been upgraded to 3.5.0 release.
203 As of this release, a prerequisite for building clang, llvm and lldb is
204 a C++11 capable compiler and C++11 standard library. This means that to
205 be able to successfully build the cross-tools stage of buildworld, with
206 clang as the bootstrap compiler, your system compiler or cross compiler
207 should either be clang 3.3 or later, or gcc 4.8 or later, and your
208 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
211 On any standard FreeBSD 10.x or 11.x installation, where clang and
212 libc++ are on by default (that is, on x86 or arm), this should work out
215 On 9.x installations where clang is enabled by default, e.g. on x86 and
216 powerpc, libc++ will not be enabled by default, so libc++ should be
217 built (with clang) and installed first. If both clang and libc++ are
218 missing, build clang first, then use it to build libc++.
220 On 8.x and earlier installations, upgrade to 9.x first, and then follow
221 the instructions for 9.x above.
223 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
224 default, and do not build clang.
226 Many embedded systems are resource constrained, and will not be able to
227 build clang in a reasonable time, or in some cases at all. In those
228 cases, cross building bootable systems on amd64 is a workaround.
230 This new version of clang introduces a number of new warnings, of which
231 the following are most likely to appear:
235 This warns in two cases, for both C and C++:
236 * When the code is trying to take the absolute value of an unsigned
237 quantity, which is effectively a no-op, and almost never what was
238 intended. The code should be fixed, if at all possible. If you are
239 sure that the unsigned quantity can be safely cast to signed, without
240 loss of information or undefined behavior, you can add an explicit
241 cast, or disable the warning.
243 * When the code is trying to take an absolute value, but the called
244 abs() variant is for the wrong type, which can lead to truncation.
245 If you want to disable the warning instead of fixing the code, please
246 make sure that truncation will not occur, or it might lead to unwanted
249 -Wtautological-undefined-compare and
250 -Wundefined-bool-conversion
252 These warn when C++ code is trying to compare 'this' against NULL, while
253 'this' should never be NULL in well-defined C++ code. However, there is
254 some legacy (pre C++11) code out there, which actively abuses this
255 feature, which was less strictly defined in previous C++ versions.
257 Squid and openjdk do this, for example. The warning can be turned off
258 for C++98 and earlier, but compiling the code in C++11 mode might result
259 in unexpected behavior; for example, the parts of the program that are
260 unreachable could be optimized away.
263 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
264 kernel sources have been removed. The .h files remain, since some
265 utilities include them. This will need to be fixed later.
266 If "mount -t oldnfs ..." is attempted, it will fail.
267 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
268 the utilities will report errors.
271 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
272 directories to top level SUBDIR variable when their parent
273 directory is included in LOCAL_DIRS. Users with build systems with
274 such hierarchies and without SUBDIR entries in the parent
275 directory Makefiles should add them or add the directories to
279 faith(4) and faithd(8) have been removed from the base system. Faith
280 has been obsolete for a very long time.
283 vt(4), the new console driver, is enabled by default. It brings
284 support for Unicode and double-width characters, as well as
285 support for UEFI and integration with the KMS kernel video
288 You may need to update your console settings in /etc/rc.conf,
289 most probably the keymap. During boot, /etc/rc.d/syscons will
290 indicate what you need to do.
292 vt(4) still has issues and lacks some features compared to
293 syscons(4). See the wiki for up-to-date information:
294 https://wiki.freebsd.org/Newcons
296 If you want to keep using syscons(4), you can do so by adding
297 the following line to /boot/loader.conf:
301 pjdfstest has been integrated into kyua as an opt-in test suite.
302 Please see share/doc/pjdfstest/README for more details on how to
306 gperf has been removed from the base system for architectures
307 that use clang. Ports that require gperf will obtain it from the
311 pjdfstest has been moved from tools/regression/pjdfstest to
315 At svn r271982, The default linux compat kernel ABI has been adjusted
316 to 2.6.18 in support of the linux-c6 compat ports infrastructure
317 update. If you wish to continue using the linux-f10 compat ports,
318 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
319 encouraged to update their linux-compat packages to linux-c6 during
320 their next update cycle.
323 The ofwfb driver, used to provide a graphics console on PowerPC when
324 using vt(4), no longer allows mmap() of all physical memory. This
325 will prevent Xorg on PowerPC with some ATI graphics cards from
326 initializing properly unless x11-servers/xorg-server is updated to
330 The xdev targets have been converted to using TARGET and
331 TARGET_ARCH instead of XDEV and XDEV_ARCH.
334 The default unbound configuration has been modified to address
335 issues with reverse lookups on networks that use private
336 address ranges. If you use the local_unbound service, run
337 "service local_unbound setup" as root to regenerate your
338 configuration, then "service local_unbound reload" to load the
342 The GNU texinfo and GNU info pages are not built and installed
343 anymore, WITH_INFO knob has been added to allow to built and install
345 UPDATE: see 20150102 entry on texinfo's removal
348 The GNU readline library is now an INTERNALLIB - that is, it is
349 statically linked into consumers (GDB and variants) in the base
350 system, and the shared library is no longer installed. The
351 devel/readline port is available for third party software that
355 The Itanium architecture (ia64) has been removed from the list of
356 known architectures. This is the first step in the removal of the
360 Commit r268115 has added NFSv4.1 server support, merged from
361 projects/nfsv4.1-server. Since this includes changes to the
362 internal interfaces between the NFS related modules, a full
363 build of the kernel and modules will be necessary.
364 __FreeBSD_version has been bumped.
367 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
368 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
369 which differs from the behaviour controlled by this knob.)
372 Maximal length of the serial number in CTL was increased from 16 to
373 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
374 and ctld, need to be rebuilt to work with a new kernel.
377 The libatf-c and libatf-c++ major versions were downgraded to 0 and
378 1 respectively to match the upstream numbers. They were out of
379 sync because, when they were originally added to FreeBSD, the
380 upstream versions were not respected. These libraries are private
381 and not yet built by default, so renumbering them should be a
382 non-issue. However, unclean source trees will yield broken test
383 programs once the operator executes "make delete-old-libs" after a
386 Additionally, the atf-sh binary was made private by moving it into
387 /usr/libexec/. Already-built shell test programs will keep the
388 path to the old binary so they will break after "make delete-old"
391 If you are using WITH_TESTS=yes (not the default), wipe the object
392 tree and rebuild from scratch to prevent spurious test failures.
393 This is only needed once: the misnumbered libraries and misplaced
394 binaries have been added to OptionalObsoleteFiles.inc so they will
395 be removed during a clean upgrade.
398 Clang and llvm have been upgraded to 3.4.1 release.
401 We bogusly installed src.opts.mk in /usr/share/mk. This file should
402 be removed to avoid issues in the future (and has been added to
406 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
407 past, it affected all builds that used the bsd.*.mk files. The old
408 behavior was a bug, but people may have relied upon it. To get this
409 behavior back, you can .include /etc/src.conf from /etc/make.conf
410 (which is still global and isn't changed). This also changes the
411 behavior of incremental builds inside the tree of individual
412 directories. Set MAKESYSPATH to ".../share/mk" to do that.
413 Although this has survived make universe and some upgrade scenarios,
414 other upgrade scenarios may have broken. At least one form of
415 temporary breakage was fixed with MAKESYSPATH settings for buildworld
416 as well... In cases where MAKESYSPATH isn't working with this
417 setting, you'll need to set it to the full path to your tree.
419 One side effect of all this cleaning up is that bsd.compiler.mk
420 is no longer implicitly included by bsd.own.mk. If you wish to
421 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
425 The lindev device has been removed since /dev/full has been made a
426 standard device. __FreeBSD_version has been bumped.
429 The knob WITHOUT_VI was added to the base system, which controls
430 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
431 in order to reorder files share/termcap and didn't build ex(1) as a
432 build tool, so building/installing with WITH_VI is highly advised for
433 build hosts for older releases.
435 This issue has been fixed in stable/9 and stable/10 in r277022 and
436 r276991, respectively.
439 The YES_HESIOD knob has been removed. It has been obsolete for
440 a decade. Please move to using WITH_HESIOD instead or your builds
441 will silently lack HESIOD.
444 The uart(4) driver has been changed with respect to its handling
445 of the low-level console. Previously the uart(4) driver prevented
446 any process from changing the baudrate or the CLOCAL and HUPCL
447 control flags. By removing the restrictions, operators can make
448 changes to the serial console port without having to reboot.
449 However, when getty(8) is started on the serial device that is
450 associated with the low-level console, a misconfigured terminal
451 line in /etc/ttys will now have a real impact.
452 Before upgrading the kernel, make sure that /etc/ttys has the
453 serial console device configured as 3wire without baudrate to
454 preserve the previous behaviour. E.g:
455 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
458 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
459 to improve performance. To re-enable it, if needed, run rpcbind
460 with command line option -W.
463 Switched back to the GPL dtc compiler due to updates in the upstream
464 dts files not being supported by the BSDL dtc compiler. You will need
465 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
466 may result while building dtb files during a kernel build if you fail
467 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
470 Clang and llvm have been upgraded to 3.4 release.
473 The nve(4) driver has been removed. Please use the nfe(4) driver
474 for NVIDIA nForce MCP Ethernet adapters instead.
477 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
478 This could cause certain C++ applications using shared libraries built
479 against the previous version of libc++ to crash. The incompatibility
480 has now been fixed, but any C++ applications or shared libraries built
481 between r261283 and r261801 should be recompiled.
484 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
485 capability mode support. Please note that enabling the feature in
486 kernel is still highly recommended.
489 OpenSSH is now built with sandbox support, and will use sandbox as
490 the default privilege separation method. This requires Capsicum
491 capability mode support in kernel.
494 The libelf and libdwarf libraries have been updated to newer
495 versions from upstream. Shared library version numbers for
496 these two libraries were bumped. Any ports or binaries
497 requiring these two libraries should be recompiled.
498 __FreeBSD_version is bumped to 1100006.
501 If a Makefile in a tests/ directory was auto-generating a Kyuafile
502 instead of providing an explicit one, this would prevent such
503 Makefile from providing its own Kyuafile in the future during
504 NO_CLEAN builds. This has been fixed in the Makefiles but manual
505 intervention is needed to clean an objdir if you use NO_CLEAN:
506 # find /usr/obj -name Kyuafile | xargs rm -f
509 The behavior of gss_pseudo_random() for the krb5 mechanism
510 has changed, for applications requesting a longer random string
511 than produced by the underlying enctype's pseudo-random() function.
512 In particular, the random string produced from a session key of
513 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
514 be different at the 17th octet and later, after this change.
515 The counter used in the PRF+ construction is now encoded as a
516 big-endian integer in accordance with RFC 4402.
517 __FreeBSD_version is bumped to 1100004.
520 The WITHOUT_ATF build knob has been removed and its functionality
521 has been subsumed into the more generic WITHOUT_TESTS. If you were
522 using the former to disable the build of the ATF libraries, you
523 should change your settings to use the latter.
526 The default version of mtree is nmtree which is obtained from
527 NetBSD. The output is generally the same, but may vary
528 slightly. If you found you need identical output adding
529 "-F freebsd9" to the command line should do the trick. For the
530 time being, the old mtree is available as fmtree.
533 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
534 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
535 1.1.4_8 and verify bsdyml not linked in, before running "make
537 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
539 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
542 The rc.d/jail script has been updated to support jail(8)
543 configuration file. The "jail_<jname>_*" rc.conf(5) variables
544 for per-jail configuration are automatically converted to
545 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
546 This is transparently backward compatible. See below about some
547 incompatibilities and rc.conf(5) manual page for more details.
549 These variables are now deprecated in favor of jail(8) configuration
550 file. One can use "rc.d/jail config <jname>" command to generate
551 a jail(8) configuration file in /var/run/jail.<jname>.conf without
552 running the jail(8) utility. The default pathname of the
553 configuration file is /etc/jail.conf and can be specified by
554 using $jail_conf or $jail_<jname>_conf variables.
556 Please note that jail_devfs_ruleset accepts an integer at
557 this moment. Please consider to rewrite the ruleset name
561 BIND has been removed from the base system. If all you need
562 is a local resolver, simply enable and start the local_unbound
563 service instead. Otherwise, several versions of BIND are
564 available in the ports tree. The dns/bind99 port is one example.
566 With this change, nslookup(1) and dig(1) are no longer in the base
567 system. Users should instead use host(1) and drill(1) which are
568 in the base system. Alternatively, nslookup and dig can
569 be obtained by installing the dns/bind-tools port.
572 With the addition of unbound(8), a new unbound user is now
573 required during installworld. "mergemaster -p" can be used to
574 add the user prior to installworld, as documented in the handbook.
577 OpenSSH is now built with DNSSEC support, and will by default
578 silently trust signed SSHFP records. This can be controlled with
579 the VerifyHostKeyDNS client configuration setting. DNSSEC support
580 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
583 The GNU Compiler Collection and C++ standard library (libstdc++)
584 are no longer built by default on platforms where clang is the system
585 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
589 The PROCDESC kernel option is now part of the GENERIC kernel
590 configuration and is required for the rwhod(8) to work.
591 If you are using custom kernel configuration, you should include
595 The API and ABI related to the Capsicum framework was modified
596 in backward incompatible way. The userland libraries and programs
597 have to be recompiled to work with the new kernel. This includes the
598 following libraries and programs, but the whole buildworld is
599 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
600 kdump, procstat, rwho, rwhod, uniq.
603 AES-NI intrinsic support has been added to gcc. The AES-NI module
604 has been updated to use this support. A new gcc is required to build
605 the aesni module on both i386 and amd64.
608 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
609 Thus "device padlock_rng" and "device rdrand_rng" should be
610 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
613 WITH_ICONV has been split into two feature sets. WITH_ICONV now
614 enables just the iconv* functionality and is now on by default.
615 WITH_LIBICONV_COMPAT enables the libiconv api and link time
616 compatability. Set WITHOUT_ICONV to build the old way.
617 If you have been using WITH_ICONV before, you will very likely
618 need to turn on WITH_LIBICONV_COMPAT.
621 INVARIANTS option now enables DEBUG for code with OpenSolaris and
622 Illumos origin, including ZFS. If you have INVARIANTS in your
623 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
625 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
626 locks if WITNESS option was set. Because that generated a lot of
627 witness(9) reports and all of them were believed to be false
628 positives, this is no longer done. New option OPENSOLARIS_WITNESS
629 can be used to achieve the previous behavior.
632 Timer values in IPv6 data structures now use time_uptime instead
633 of time_second. Although this is not a user-visible functional
634 change, userland utilities which directly use them---ndp(8),
635 rtadvd(8), and rtsold(8) in the base system---need to be updated
639 find -delete can now delete the pathnames given as arguments,
640 instead of only files found below them or if the pathname did
641 not contain any slashes. Formerly, the following error message
644 find: -delete: <path>: relative path potentially not safe
646 Deleting the pathnames given as arguments can be prevented
647 without error messages using -mindepth 1 or by changing
648 directory and passing "." as argument to find. This works in the
649 old as well as the new version of find.
652 Behavior of devfs rules path matching has been changed.
653 Pattern is now always matched against fully qualified devfs
654 path and slash characters must be explicitly matched by
655 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
656 subdirectories must be reviewed.
659 The default ARM ABI has changed to the ARM EABI. The old ABI is
660 incompatible with the ARM EABI and all programs and modules will
661 need to be rebuilt to work with a new kernel.
663 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
665 NOTE: Support for the old ABI will be removed in the future and
666 users are advised to upgrade.
669 pkg_install has been disconnected from the build if you really need it
670 you should add WITH_PKGTOOLS in your src.conf(5).
673 Most of network statistics structures were changed to be able
674 keep 64-bits counters. Thus all tools, that work with networking
675 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
678 Fix targets that run multiple make's to use && rather than ;
679 so that subsequent steps depend on success of previous.
681 NOTE: if building 'universe' with -j* on stable/8 or stable/9
682 it would be better to start the build using bmake, to avoid
683 overloading the machine.
686 Fix a bug that allowed a tracing process (e.g. gdb) to write
687 to a memory-mapped file in the traced process's address space
688 even if neither the traced process nor the tracing process had
689 write access to that file.
692 CVS has been removed from the base system. An exact copy
693 of the code is available from the devel/cvs port.
696 Some people report the following error after the switch to bmake:
698 make: illegal option -- J
699 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
701 *** [buildworld] Error code 2
703 this likely due to an old instance of make in
704 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
705 which src/Makefile will use that blindly, if it exists, so if
706 you see the above error:
708 rm -rf `make -V MAKEPATH`
713 Use bmake by default.
714 Whereas before one could choose to build with bmake via
715 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
716 make. The goal is to remove these knobs for 10-RELEASE.
718 It is worth noting that bmake (like gmake) treats the command
719 line as the unit of failure, rather than statements within the
720 command line. Thus '(cd some/where && dosomething)' is safer
721 than 'cd some/where; dosomething'. The '()' allows consistent
722 behavior in parallel build.
725 Fix a bug that allows NFS clients to issue READDIR on files.
728 The WITHOUT_IDEA option has been removed because
729 the IDEA patent expired.
732 The sysctl which controls TRIM support under ZFS has been renamed
733 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
737 The mergemaster command now uses the default MAKEOBJDIRPREFIX
738 rather than creating it's own in the temporary directory in
739 order allow access to bootstrapped versions of tools such as
740 install and mtree. When upgrading from version of FreeBSD where
741 the install command does not support -l, you will need to
742 install a new mergemaster command if mergemaster -p is required.
743 This can be accomplished with the command (cd src/usr.sbin/mergemaster
747 Legacy ATA stack, disabled and replaced by new CAM-based one since
748 FreeBSD 9.0, completely removed from the sources. Kernel modules
749 atadisk and atapi*, user-level tools atacontrol and burncd are
750 removed. Kernel option `options ATA_CAM` is now permanently enabled
754 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
755 and socketpair(2). Software, in particular Kerberos, may
756 automatically detect and use these during building. The resulting
757 binaries will not work on older kernels.
760 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
761 information, see the respective 20130304 entry).
764 Recent commits to callout(9) changed the size of struct callout,
765 so the KBI is probably heavily disturbed. Also, some functions
766 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
767 by macros. Every kernel module using it won't load, so rebuild
770 The ctl device has been re-enabled in GENERIC for i386 and amd64,
771 but does not initialize by default (because of the new CTL_DISABLE
772 option) to save memory. To re-enable it, remove the CTL_DISABLE
773 option from the kernel config file or set kern.cam.ctl.disable=0
774 in /boot/loader.conf.
777 The ctl device has been disabled in GENERIC for i386 and amd64.
778 This was done due to the extra memory being allocated at system
779 initialisation time by the ctl driver which was only used if
780 a CAM target device was created. This makes a FreeBSD system
781 unusable on 128MB or less of RAM.
784 A new compression method (lz4) has been merged to -HEAD. Please
785 refer to zpool-features(7) for more information.
787 Please refer to the "ZFS notes" section of this file for information
788 on upgrading boot ZFS pools.
791 A BSD-licensed patch(1) variant has been added and is installed
792 as bsdpatch, being the GNU version the default patch.
793 To inverse the logic and use the BSD-licensed one as default,
794 while having the GNU version installed as gnupatch, rebuild
795 and install world with the WITH_BSD_PATCH knob set.
798 Due to the use of the new -l option to install(1) during build
799 and install, you must take care not to directly set the INSTALL
800 make variable in your /etc/make.conf, /etc/src.conf, or on the
801 command line. If you wish to use the -C flag for all installs
802 you may be able to add INSTALL+=-C to /etc/make.conf or
806 The install(1) option -M has changed meaning and now takes an
807 argument that is a file or path to append logs to. In the
808 unlikely event that -M was the last option on the command line
809 and the command line contained at least two files and a target
810 directory the first file will have logs appended to it. The -M
811 option served little practical purpose in the last decade so its
812 use is expected to be extremely rare.
815 After switching to Clang as the default compiler some users of ZFS
816 on i386 systems started to experience stack overflow kernel panics.
817 Please consider using 'options KSTACK_PAGES=4' in such configurations.
820 GEOM_LABEL now mangles label names read from file system metadata.
821 Mangling affect labels containing spaces, non-printable characters,
822 '%' or '"'. Device names in /etc/fstab and other places may need to
826 By default, only the 10 most recent kernel dumps will be saved. To
827 restore the previous behaviour (no limit on the number of kernel dumps
828 stored in the dump directory) add the following line to /etc/rc.conf:
833 With the addition of auditdistd(8), a new auditdistd user is now
834 required during installworld. "mergemaster -p" can be used to
835 add the user prior to installworld, as documented in the handbook.
838 The sin6_scope_id member variable in struct sockaddr_in6 is now
839 filled by the kernel before passing the structure to the userland via
840 sysctl or routing socket. This means the KAME-specific embedded scope
841 id in sin6_addr.s6_addr[2] is always cleared in userland application.
842 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
843 __FreeBSD_version is bumped to 1000025.
846 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
847 This means that the world and kernel will be compiled with clang
848 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
849 and /usr/bin/cpp. To disable this behavior and revert to building
850 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
851 of current may need to bootstrap WITHOUT_CLANG first if the clang
852 build fails (its compatibility window doesn't extend to the 9 stable
856 The IPFIREWALL_FORWARD kernel option has been removed. Its
857 functionality now turned on by default.
860 The ZERO_COPY_SOCKET kernel option has been removed and
861 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
862 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
863 mechanism which is not safe and may result in kernel crashes.
864 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
865 driver supports disposeable external page sized mbuf storage.
866 Proper replacements for both zero-copy mechanisms are under
867 consideration and will eventually lead to complete removal
868 of the two kernel options.
871 The IPv4 network stack has been converted to network byte
872 order. The following modules need to be recompiled together
873 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
874 pf(4), ipfw(4), ng_ipfw(4), stf(4).
877 Support for non-MPSAFE filesystems was removed from VFS. The
878 VFS_VERSION was bumped, all filesystem modules shall be
882 All the non-MPSAFE filesystems have been disconnected from
883 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
884 portalfs, smbfs, xfs.
887 The interface cloning API and ABI has changed. The following
888 modules need to be recompiled together with kernel:
889 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
890 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
891 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
894 The sdhci driver was split in two parts: sdhci (generic SD Host
895 Controller logic) and sdhci_pci (actual hardware driver).
896 No kernel config modifications are required, but if you
897 load sdhc as a module you must switch to sdhci_pci instead.
900 Import the FUSE kernel and userland support into base system.
903 The GNU sort(1) program has been removed since the BSD-licensed
904 sort(1) has been the default for quite some time and no serious
905 problems have been reported. The corresponding WITH_GNU_SORT
909 The pfil(9) API/ABI for AF_INET family has been changed. Packet
910 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
914 The net80211(4) ABI has been changed to allow for improved driver
915 PS-POLL and power-save support. All wireless drivers need to be
916 recompiled to work with the new kernel.
919 The random(4) support for the VIA hardware random number
920 generator (`PADLOCK') is no longer enabled unconditionally.
921 Add the padlock_rng device in the custom kernel config if
922 needed. The GENERIC kernels on i386 and amd64 do include the
923 device, so the change only affects the custom kernel
927 The pf(4) packet filter ABI has been changed. pfctl(8) and
928 snmp_pf module need to be recompiled to work with new kernel.
931 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
932 to -HEAD. Pools that have empty_bpobj in active state can not be
933 imported read-write with ZFS implementations that do not support
934 this feature. For more information read the zpool-features(5)
938 The sparc64 ZFS loader has been changed to no longer try to auto-
939 detect ZFS providers based on diskN aliases but now requires these
940 to be explicitly listed in the OFW boot-device environment variable.
943 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
944 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
945 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
948 The following sysctls and tunables have been renamed for consistency
949 with other variables:
950 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
951 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
954 The sort utility has been replaced with BSD sort. For now, GNU sort
955 is also available as "gnusort" or the default can be set back to
956 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
957 installed as "bsdsort".
960 A new version of ZFS (pool version 5000) has been merged to -HEAD.
961 Starting with this version the old system of ZFS pool versioning
962 is superseded by "feature flags". This concept enables forward
963 compatibility against certain future changes in functionality of ZFS
964 pools. The first read-only compatible "feature flag" for ZFS pools
965 is named "com.delphix:async_destroy". For more information
966 read the new zpool-features(5) manual page.
967 Please refer to the "ZFS notes" section of this file for information
968 on upgrading boot ZFS pools.
971 The malloc(3) implementation embedded in libc now uses sources imported
972 as contrib/jemalloc. The most disruptive API change is to
973 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
974 delete it prior to installworld, and optionally re-create it using the
975 new format after rebooting. See malloc.conf(5) for details
976 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
980 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
981 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
982 now spelled mips. This is to aid compatibility with third-party
983 software that expects this naming scheme in uname(3). Little-endian
984 settings are unchanged. If you are updating a big-endian mips64 machine
985 from before this change, you may need to set MACHINE_ARCH=mips64 in
986 your environment before the new build system will recognize your machine.
989 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
993 Now unix domain sockets behave "as expected" on nullfs(5). Previously
994 nullfs(5) did not pass through all behaviours to the underlying layer,
995 as a result if we bound to a socket on the lower layer we could connect
996 only to the lower path; if we bound to the upper layer we could connect
997 only to the upper path. The new behavior is one can connect to both the
998 lower and the upper paths regardless what layer path one binds to.
1001 The getifaddrs upgrade path broken with 20111215 has been restored.
1002 If you have upgraded in between 20111215 and 20120209 you need to
1003 recompile libc again with your kernel. You still need to recompile
1004 world to be able to configure CARP but this restriction already
1005 comes from 20111215.
1008 The set_rcvar() function has been removed from /etc/rc.subr. All
1009 base and ports rc.d scripts have been updated, so if you have a
1010 port installed with a script in /usr/local/etc/rc.d you can either
1011 hand-edit the rcvar= line, or reinstall the port.
1013 An easy way to handle the mass-update of /etc/rc.d:
1014 rm /etc/rc.d/* && mergemaster -i
1017 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1018 on the current CPU and prevents other threads from running.
1019 This behavior can be reverted using the kern.stop_scheduler_on_panic
1021 The new behavior can be incompatible with kern.sync_on_panic.
1024 The carp(4) facility has been changed significantly. Configuration
1025 of the CARP protocol via ifconfig(8) has changed, as well as format
1026 of CARP events submitted to devd(8) has changed. See manual pages
1027 for more information. The arpbalance feature of carp(4) is currently
1028 not supported anymore.
1030 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1031 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1032 need to be recompiled.
1035 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1039 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1040 explicitely support non-MPSAFE filesystems.
1041 It is on by default for all supported platform at this present
1045 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1046 i386 and pc98 GENERIC kernel configuration files.
1049 sysinstall has been removed
1052 The stable/9 branch created in subversion. This corresponds to the
1053 RELENG_9 branch in CVS.
1059 Avoid using make -j when upgrading. While generally safe, there are
1060 sometimes problems using -j to upgrade. If your upgrade fails with
1061 -j, please try again without -j. From time to time in the past there
1062 have been problems using -j with buildworld and/or installworld. This
1063 is especially true when upgrading between "distant" versions (eg one
1064 that cross a major release boundary or several minor releases, or when
1065 several months have passed on the -current branch).
1067 Sometimes, obscure build problems are the result of environment
1068 poisoning. This can happen because the make utility reads its
1069 environment when searching for values for global variables. To run
1070 your build attempts in an "environmental clean room", prefix all make
1071 commands with 'env -i '. See the env(1) manual page for more details.
1073 When upgrading from one major version to another it is generally best
1074 to upgrade to the latest code in the currently installed branch first,
1075 then do an upgrade to the new branch. This is the best-tested upgrade
1076 path, and has the highest probability of being successful. Please try
1077 this approach before reporting problems with a major version upgrade.
1079 When upgrading a live system, having a root shell around before
1080 installing anything can help undo problems. Not having a root shell
1081 around can lead to problems if pam has changed too much from your
1082 starting point to allow continued authentication after the upgrade.
1086 When upgrading the boot ZFS pool to a new version, always follow
1089 1.) recompile and reinstall the ZFS boot loader and boot block
1090 (this is part of "make buildworld" and "make installworld")
1092 2.) update the ZFS boot block on your boot drive
1094 The following example updates the ZFS boot block on the first
1095 partition (freebsd-boot) of a GPT partitioned drive ada0:
1096 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1098 Non-boot pools do not need these updates.
1102 If you are updating from a prior version of FreeBSD (even one just
1103 a few days old), you should follow this procedure. It is the most
1104 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1106 make kernel-toolchain
1107 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1108 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1110 To test a kernel once
1111 ---------------------
1112 If you just want to boot a kernel once (because you are not sure
1113 if it works, or if you want to boot a known bad kernel to provide
1114 debugging information) run
1115 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1116 nextboot -k testkernel
1118 To just build a kernel when you know that it won't mess you up
1119 --------------------------------------------------------------
1120 This assumes you are already running a CURRENT system. Replace
1121 ${arch} with the architecture of your machine (e.g. "i386",
1122 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1124 cd src/sys/${arch}/conf
1125 config KERNEL_NAME_HERE
1126 cd ../compile/KERNEL_NAME_HERE
1131 If this fails, go to the "To build a kernel" section.
1133 To rebuild everything and install it on the current system.
1134 -----------------------------------------------------------
1135 # Note: sometimes if you are running current you gotta do more than
1136 # is listed here if you are upgrading from a really old current.
1138 <make sure you have good level 0 dumps>
1140 make kernel KERNCONF=YOUR_KERNEL_HERE
1142 <reboot in single user> [3]
1149 To cross-install current onto a separate partition
1150 --------------------------------------------------
1151 # In this approach we use a separate partition to hold
1152 # current's root, 'usr', and 'var' directories. A partition
1153 # holding "/", "/usr" and "/var" should be about 2GB in
1156 <make sure you have good level 0 dumps>
1159 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1160 <maybe newfs current's root partition>
1161 <mount current's root partition on directory ${CURRENT_ROOT}>
1162 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1163 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1164 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1165 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1166 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1167 <reboot into current>
1168 <do a "native" rebuild/install as described in the previous section>
1169 <maybe install compatibility libraries from ports/misc/compat*>
1173 To upgrade in-place from stable to current
1174 ----------------------------------------------
1175 <make sure you have good level 0 dumps>
1177 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1179 <reboot in single user> [3]
1186 Make sure that you've read the UPDATING file to understand the
1187 tweaks to various things you need. At this point in the life
1188 cycle of current, things change often and you are on your own
1189 to cope. The defaults can also change, so please read ALL of
1190 the UPDATING entries.
1192 Also, if you are tracking -current, you must be subscribed to
1193 freebsd-current@freebsd.org. Make sure that before you update
1194 your sources that you have read and understood all the recent
1195 messages there. If in doubt, please track -stable which has
1196 much fewer pitfalls.
1198 [1] If you have third party modules, such as vmware, you
1199 should disable them at this point so they don't crash your
1202 [3] From the bootblocks, boot -s, and then do
1207 adjkerntz -i # if CMOS is wall time
1208 Also, when doing a major release upgrade, it is required that
1209 you boot into single user mode to do the installworld.
1211 [4] Note: This step is non-optional. Failure to do this step
1212 can result in a significant reduction in the functionality of the
1213 system. Attempting to do it by hand is not recommended and those
1214 that pursue this avenue should read this file carefully, as well
1215 as the archives of freebsd-current and freebsd-hackers mailing lists
1216 for potential gotchas. The -U option is also useful to consider.
1217 See mergemaster(8) for more information.
1219 [5] Usually this step is a noop. However, from time to time
1220 you may need to do this if you get unknown user in the following
1221 step. It never hurts to do it all the time. You may need to
1222 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1223 install) after the buildworld before this step if you last updated
1224 from current before 20130425 or from -stable before 20130430.
1226 [6] This only deletes old files and directories. Old libraries
1227 can be deleted by "make delete-old-libs", but you have to make
1228 sure that no program is using those libraries anymore.
1230 [8] In order to have a kernel that can run the 4.x binaries needed to
1231 do an installworld, you must include the COMPAT_FREEBSD4 option in
1232 your kernel. Failure to do so may leave you with a system that is
1233 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1234 required to run the 5.x binaries on more recent kernels. And so on
1235 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1237 Make sure that you merge any new devices from GENERIC since the
1238 last time you updated your kernel config file.
1240 [9] When checking out sources, you must include the -P flag to have
1241 cvs prune empty directories.
1243 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1244 "?=" instead of the "=" assignment operator, so that buildworld can
1245 override the CPUTYPE if it needs to.
1247 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1248 not on the command line, or in /etc/make.conf. buildworld will
1249 warn if it is improperly defined.
1252 This file contains a list, in reverse chronological order, of major
1253 breakages in tracking -current. It is not guaranteed to be a complete
1254 list of such breakages, and only contains entries since October 10, 2007.
1255 If you need to see UPDATING entries from before that date, you will need
1256 to fetch an UPDATING file from an older FreeBSD release.
1258 Copyright information:
1260 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1262 Redistribution, publication, translation and use, with or without
1263 modification, in full or in part, in any form or format of this
1264 document are permitted without further permission from the author.
1266 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1267 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1268 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1269 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1270 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1271 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1272 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1273 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1274 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1275 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1276 POSSIBILITY OF SUCH DAMAGE.
1278 Contact Warner Losh if you have any questions about your use of