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 The const qualifier has been removed from iconv(3) to comply with
36 POSIX. The ports tree is aware of this from r384038 onwards.
39 From legacy ata(4) driver was removed support for SATA controllers
40 supported by more functional drivers ahci(4), siis(4) and mvs(4).
41 Kernel modules ataahci and ataadaptec were removed completely,
42 replaced by ahci and mvs modules respectively.
45 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
46 the 20141231 entry below for information about prerequisites and
47 upgrading, if you are not already using 3.5.0 or higher.
50 The 32-bit PowerPC kernel has been changed to a position-independent
51 executable. This can only be booted with a version of loader(8)
52 newer than January 31, 2015, so make sure to update both world and
53 kernel before rebooting.
56 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
57 but before r278950, the RNG was not seeded properly. Immediately
58 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
59 ssh keys or openssl keys) that were generated w/ a kernel from that
60 range. This does not affect programs that directly used /dev/random
61 or /dev/urandom. All userland uses of arc4random(3) are affected.
64 The autofs(4) ABI was changed in order to restore binary compatibility
65 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
69 The powerpc64 kernel has been changed to a position-independent
70 executable. This can only be booted with a new version of loader(8),
71 so make sure to update both world and kernel before rebooting.
74 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
75 only release, no new features have been added. Please see the 20141231
76 entry below for information about prerequisites and upgrading, if you
77 are not already using 3.5.0.
80 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
81 taken from the ELF Tool Chain project rather than GNU binutils. They
82 should be drop-in replacements, with the addition of arm64 support.
83 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
84 binutils tools, if necessary.
87 The default Unbound configuration now enables remote control
88 using a local socket. Users who have already enabled the
89 local_unbound service should regenerate their configuration
90 by running "service local_unbound setup" as root.
93 The GNU texinfo and GNU info pages have been removed.
94 To be able to view GNU info pages please install texinfo from ports.
97 Clang, llvm and lldb have been upgraded to 3.5.0 release.
99 As of this release, a prerequisite for building clang, llvm and lldb is
100 a C++11 capable compiler and C++11 standard library. This means that to
101 be able to successfully build the cross-tools stage of buildworld, with
102 clang as the bootstrap compiler, your system compiler or cross compiler
103 should either be clang 3.3 or later, or gcc 4.8 or later, and your
104 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
107 On any standard FreeBSD 10.x or 11.x installation, where clang and
108 libc++ are on by default (that is, on x86 or arm), this should work out
111 On 9.x installations where clang is enabled by default, e.g. on x86 and
112 powerpc, libc++ will not be enabled by default, so libc++ should be
113 built (with clang) and installed first. If both clang and libc++ are
114 missing, build clang first, then use it to build libc++.
116 On 8.x and earlier installations, upgrade to 9.x first, and then follow
117 the instructions for 9.x above.
119 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
120 default, and do not build clang.
122 Many embedded systems are resource constrained, and will not be able to
123 build clang in a reasonable time, or in some cases at all. In those
124 cases, cross building bootable systems on amd64 is a workaround.
126 This new version of clang introduces a number of new warnings, of which
127 the following are most likely to appear:
131 This warns in two cases, for both C and C++:
132 * When the code is trying to take the absolute value of an unsigned
133 quantity, which is effectively a no-op, and almost never what was
134 intended. The code should be fixed, if at all possible. If you are
135 sure that the unsigned quantity can be safely cast to signed, without
136 loss of information or undefined behavior, you can add an explicit
137 cast, or disable the warning.
139 * When the code is trying to take an absolute value, but the called
140 abs() variant is for the wrong type, which can lead to truncation.
141 If you want to disable the warning instead of fixing the code, please
142 make sure that truncation will not occur, or it might lead to unwanted
145 -Wtautological-undefined-compare and
146 -Wundefined-bool-conversion
148 These warn when C++ code is trying to compare 'this' against NULL, while
149 'this' should never be NULL in well-defined C++ code. However, there is
150 some legacy (pre C++11) code out there, which actively abuses this
151 feature, which was less strictly defined in previous C++ versions.
153 Squid and openjdk do this, for example. The warning can be turned off
154 for C++98 and earlier, but compiling the code in C++11 mode might result
155 in unexpected behavior; for example, the parts of the program that are
156 unreachable could be optimized away.
159 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
160 kernel sources have been removed. The .h files remain, since some
161 utilities include them. This will need to be fixed later.
162 If "mount -t oldnfs ..." is attempted, it will fail.
163 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
164 the utilities will report errors.
167 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
168 directories to top level SUBDIR variable when their parent
169 directory is included in LOCAL_DIRS. Users with build systems with
170 such hierarchies and without SUBDIR entries in the parent
171 directory Makefiles should add them or add the directories to
175 faith(4) and faithd(8) have been removed from the base system. Faith
176 has been obsolete for a very long time.
179 vt(4), the new console driver, is enabled by default. It brings
180 support for Unicode and double-width characters, as well as
181 support for UEFI and integration with the KMS kernel video
184 You may need to update your console settings in /etc/rc.conf,
185 most probably the keymap. During boot, /etc/rc.d/syscons will
186 indicate what you need to do.
188 vt(4) still has issues and lacks some features compared to
189 syscons(4). See the wiki for up-to-date information:
190 https://wiki.freebsd.org/Newcons
192 If you want to keep using syscons(4), you can do so by adding
193 the following line to /boot/loader.conf:
197 pjdfstest has been integrated into kyua as an opt-in test suite.
198 Please see share/doc/pjdfstest/README for more details on how to
202 gperf has been removed from the base system for architectures
203 that use clang. Ports that require gperf will obtain it from the
207 pjdfstest has been moved from tools/regression/pjdfstest to
211 At svn r271982, The default linux compat kernel ABI has been adjusted
212 to 2.6.18 in support of the linux-c6 compat ports infrastructure
213 update. If you wish to continue using the linux-f10 compat ports,
214 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
215 encouraged to update their linux-compat packages to linux-c6 during
216 their next update cycle.
219 The ofwfb driver, used to provide a graphics console on PowerPC when
220 using vt(4), no longer allows mmap() of all physical memory. This
221 will prevent Xorg on PowerPC with some ATI graphics cards from
222 initializing properly unless x11-servers/xorg-server is updated to
226 The xdev targets have been converted to using TARGET and
227 TARGET_ARCH instead of XDEV and XDEV_ARCH.
230 The default unbound configuration has been modified to address
231 issues with reverse lookups on networks that use private
232 address ranges. If you use the local_unbound service, run
233 "service local_unbound setup" as root to regenerate your
234 configuration, then "service local_unbound reload" to load the
238 The GNU texinfo and GNU info pages are not built and installed
239 anymore, WITH_INFO knob has been added to allow to built and install
241 UPDATE: see 20150102 entry on texinfo's removal
244 The GNU readline library is now an INTERNALLIB - that is, it is
245 statically linked into consumers (GDB and variants) in the base
246 system, and the shared library is no longer installed. The
247 devel/readline port is available for third party software that
251 The Itanium architecture (ia64) has been removed from the list of
252 known architectures. This is the first step in the removal of the
256 Commit r268115 has added NFSv4.1 server support, merged from
257 projects/nfsv4.1-server. Since this includes changes to the
258 internal interfaces between the NFS related modules, a full
259 build of the kernel and modules will be necessary.
260 __FreeBSD_version has been bumped.
263 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
264 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
265 which differs from the behaviour controlled by this knob.)
268 Maximal length of the serial number in CTL was increased from 16 to
269 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
270 and ctld, need to be rebuilt to work with a new kernel.
273 The libatf-c and libatf-c++ major versions were downgraded to 0 and
274 1 respectively to match the upstream numbers. They were out of
275 sync because, when they were originally added to FreeBSD, the
276 upstream versions were not respected. These libraries are private
277 and not yet built by default, so renumbering them should be a
278 non-issue. However, unclean source trees will yield broken test
279 programs once the operator executes "make delete-old-libs" after a
282 Additionally, the atf-sh binary was made private by moving it into
283 /usr/libexec/. Already-built shell test programs will keep the
284 path to the old binary so they will break after "make delete-old"
287 If you are using WITH_TESTS=yes (not the default), wipe the object
288 tree and rebuild from scratch to prevent spurious test failures.
289 This is only needed once: the misnumbered libraries and misplaced
290 binaries have been added to OptionalObsoleteFiles.inc so they will
291 be removed during a clean upgrade.
294 Clang and llvm have been upgraded to 3.4.1 release.
297 We bogusly installed src.opts.mk in /usr/share/mk. This file should
298 be removed to avoid issues in the future (and has been added to
302 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
303 past, it affected all builds that used the bsd.*.mk files. The old
304 behavior was a bug, but people may have relied upon it. To get this
305 behavior back, you can .include /etc/src.conf from /etc/make.conf
306 (which is still global and isn't changed). This also changes the
307 behavior of incremental builds inside the tree of individual
308 directories. Set MAKESYSPATH to ".../share/mk" to do that.
309 Although this has survived make universe and some upgrade scenarios,
310 other upgrade scenarios may have broken. At least one form of
311 temporary breakage was fixed with MAKESYSPATH settings for buildworld
312 as well... In cases where MAKESYSPATH isn't working with this
313 setting, you'll need to set it to the full path to your tree.
315 One side effect of all this cleaning up is that bsd.compiler.mk
316 is no longer implicitly included by bsd.own.mk. If you wish to
317 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
321 The lindev device has been removed since /dev/full has been made a
322 standard device. __FreeBSD_version has been bumped.
325 The knob WITHOUT_VI was added to the base system, which controls
326 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
327 in order to reorder files share/termcap and didn't build ex(1) as a
328 build tool, so building/installing with WITH_VI is highly advised for
329 build hosts for older releases.
331 This issue has been fixed in stable/9 and stable/10 in r277022 and
332 r276991, respectively.
335 The YES_HESIOD knob has been removed. It has been obsolete for
336 a decade. Please move to using WITH_HESIOD instead or your builds
337 will silently lack HESIOD.
340 The uart(4) driver has been changed with respect to its handling
341 of the low-level console. Previously the uart(4) driver prevented
342 any process from changing the baudrate or the CLOCAL and HUPCL
343 control flags. By removing the restrictions, operators can make
344 changes to the serial console port without having to reboot.
345 However, when getty(8) is started on the serial device that is
346 associated with the low-level console, a misconfigured terminal
347 line in /etc/ttys will now have a real impact.
348 Before upgrading the kernel, make sure that /etc/ttys has the
349 serial console device configured as 3wire without baudrate to
350 preserve the previous behaviour. E.g:
351 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
354 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
355 to improve performance. To re-enable it, if needed, run rpcbind
356 with command line option -W.
359 Switched back to the GPL dtc compiler due to updates in the upstream
360 dts files not being supported by the BSDL dtc compiler. You will need
361 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
362 may result while building dtb files during a kernel build if you fail
363 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
366 Clang and llvm have been upgraded to 3.4 release.
369 The nve(4) driver has been removed. Please use the nfe(4) driver
370 for NVIDIA nForce MCP Ethernet adapters instead.
373 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
374 This could cause certain C++ applications using shared libraries built
375 against the previous version of libc++ to crash. The incompatibility
376 has now been fixed, but any C++ applications or shared libraries built
377 between r261283 and r261801 should be recompiled.
380 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
381 capability mode support. Please note that enabling the feature in
382 kernel is still highly recommended.
385 OpenSSH is now built with sandbox support, and will use sandbox as
386 the default privilege separation method. This requires Capsicum
387 capability mode support in kernel.
390 The libelf and libdwarf libraries have been updated to newer
391 versions from upstream. Shared library version numbers for
392 these two libraries were bumped. Any ports or binaries
393 requiring these two libraries should be recompiled.
394 __FreeBSD_version is bumped to 1100006.
397 If a Makefile in a tests/ directory was auto-generating a Kyuafile
398 instead of providing an explicit one, this would prevent such
399 Makefile from providing its own Kyuafile in the future during
400 NO_CLEAN builds. This has been fixed in the Makefiles but manual
401 intervention is needed to clean an objdir if you use NO_CLEAN:
402 # find /usr/obj -name Kyuafile | xargs rm -f
405 The behavior of gss_pseudo_random() for the krb5 mechanism
406 has changed, for applications requesting a longer random string
407 than produced by the underlying enctype's pseudo-random() function.
408 In particular, the random string produced from a session key of
409 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
410 be different at the 17th octet and later, after this change.
411 The counter used in the PRF+ construction is now encoded as a
412 big-endian integer in accordance with RFC 4402.
413 __FreeBSD_version is bumped to 1100004.
416 The WITHOUT_ATF build knob has been removed and its functionality
417 has been subsumed into the more generic WITHOUT_TESTS. If you were
418 using the former to disable the build of the ATF libraries, you
419 should change your settings to use the latter.
422 The default version of mtree is nmtree which is obtained from
423 NetBSD. The output is generally the same, but may vary
424 slightly. If you found you need identical output adding
425 "-F freebsd9" to the command line should do the trick. For the
426 time being, the old mtree is available as fmtree.
429 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
430 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
431 1.1.4_8 and verify bsdyml not linked in, before running "make
433 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
435 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
438 The rc.d/jail script has been updated to support jail(8)
439 configuration file. The "jail_<jname>_*" rc.conf(5) variables
440 for per-jail configuration are automatically converted to
441 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
442 This is transparently backward compatible. See below about some
443 incompatibilities and rc.conf(5) manual page for more details.
445 These variables are now deprecated in favor of jail(8) configuration
446 file. One can use "rc.d/jail config <jname>" command to generate
447 a jail(8) configuration file in /var/run/jail.<jname>.conf without
448 running the jail(8) utility. The default pathname of the
449 configuration file is /etc/jail.conf and can be specified by
450 using $jail_conf or $jail_<jname>_conf variables.
452 Please note that jail_devfs_ruleset accepts an integer at
453 this moment. Please consider to rewrite the ruleset name
457 BIND has been removed from the base system. If all you need
458 is a local resolver, simply enable and start the local_unbound
459 service instead. Otherwise, several versions of BIND are
460 available in the ports tree. The dns/bind99 port is one example.
462 With this change, nslookup(1) and dig(1) are no longer in the base
463 system. Users should instead use host(1) and drill(1) which are
464 in the base system. Alternatively, nslookup and dig can
465 be obtained by installing the dns/bind-tools port.
468 With the addition of unbound(8), a new unbound user is now
469 required during installworld. "mergemaster -p" can be used to
470 add the user prior to installworld, as documented in the handbook.
473 OpenSSH is now built with DNSSEC support, and will by default
474 silently trust signed SSHFP records. This can be controlled with
475 the VerifyHostKeyDNS client configuration setting. DNSSEC support
476 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
479 The GNU Compiler Collection and C++ standard library (libstdc++)
480 are no longer built by default on platforms where clang is the system
481 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
485 The PROCDESC kernel option is now part of the GENERIC kernel
486 configuration and is required for the rwhod(8) to work.
487 If you are using custom kernel configuration, you should include
491 The API and ABI related to the Capsicum framework was modified
492 in backward incompatible way. The userland libraries and programs
493 have to be recompiled to work with the new kernel. This includes the
494 following libraries and programs, but the whole buildworld is
495 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
496 kdump, procstat, rwho, rwhod, uniq.
499 AES-NI intrinsic support has been added to gcc. The AES-NI module
500 has been updated to use this support. A new gcc is required to build
501 the aesni module on both i386 and amd64.
504 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
505 Thus "device padlock_rng" and "device rdrand_rng" should be
506 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
509 WITH_ICONV has been split into two feature sets. WITH_ICONV now
510 enables just the iconv* functionality and is now on by default.
511 WITH_LIBICONV_COMPAT enables the libiconv api and link time
512 compatability. Set WITHOUT_ICONV to build the old way.
513 If you have been using WITH_ICONV before, you will very likely
514 need to turn on WITH_LIBICONV_COMPAT.
517 INVARIANTS option now enables DEBUG for code with OpenSolaris and
518 Illumos origin, including ZFS. If you have INVARIANTS in your
519 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
521 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
522 locks if WITNESS option was set. Because that generated a lot of
523 witness(9) reports and all of them were believed to be false
524 positives, this is no longer done. New option OPENSOLARIS_WITNESS
525 can be used to achieve the previous behavior.
528 Timer values in IPv6 data structures now use time_uptime instead
529 of time_second. Although this is not a user-visible functional
530 change, userland utilities which directly use them---ndp(8),
531 rtadvd(8), and rtsold(8) in the base system---need to be updated
535 find -delete can now delete the pathnames given as arguments,
536 instead of only files found below them or if the pathname did
537 not contain any slashes. Formerly, the following error message
540 find: -delete: <path>: relative path potentially not safe
542 Deleting the pathnames given as arguments can be prevented
543 without error messages using -mindepth 1 or by changing
544 directory and passing "." as argument to find. This works in the
545 old as well as the new version of find.
548 Behavior of devfs rules path matching has been changed.
549 Pattern is now always matched against fully qualified devfs
550 path and slash characters must be explicitly matched by
551 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
552 subdirectories must be reviewed.
555 The default ARM ABI has changed to the ARM EABI. The old ABI is
556 incompatible with the ARM EABI and all programs and modules will
557 need to be rebuilt to work with a new kernel.
559 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
561 NOTE: Support for the old ABI will be removed in the future and
562 users are advised to upgrade.
565 pkg_install has been disconnected from the build if you really need it
566 you should add WITH_PKGTOOLS in your src.conf(5).
569 Most of network statistics structures were changed to be able
570 keep 64-bits counters. Thus all tools, that work with networking
571 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
574 Fix targets that run multiple make's to use && rather than ;
575 so that subsequent steps depend on success of previous.
577 NOTE: if building 'universe' with -j* on stable/8 or stable/9
578 it would be better to start the build using bmake, to avoid
579 overloading the machine.
582 Fix a bug that allowed a tracing process (e.g. gdb) to write
583 to a memory-mapped file in the traced process's address space
584 even if neither the traced process nor the tracing process had
585 write access to that file.
588 CVS has been removed from the base system. An exact copy
589 of the code is available from the devel/cvs port.
592 Some people report the following error after the switch to bmake:
594 make: illegal option -- J
595 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
597 *** [buildworld] Error code 2
599 this likely due to an old instance of make in
600 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
601 which src/Makefile will use that blindly, if it exists, so if
602 you see the above error:
604 rm -rf `make -V MAKEPATH`
609 Use bmake by default.
610 Whereas before one could choose to build with bmake via
611 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
612 make. The goal is to remove these knobs for 10-RELEASE.
614 It is worth noting that bmake (like gmake) treats the command
615 line as the unit of failure, rather than statements within the
616 command line. Thus '(cd some/where && dosomething)' is safer
617 than 'cd some/where; dosomething'. The '()' allows consistent
618 behavior in parallel build.
621 Fix a bug that allows NFS clients to issue READDIR on files.
624 The WITHOUT_IDEA option has been removed because
625 the IDEA patent expired.
628 The sysctl which controls TRIM support under ZFS has been renamed
629 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
633 The mergemaster command now uses the default MAKEOBJDIRPREFIX
634 rather than creating it's own in the temporary directory in
635 order allow access to bootstrapped versions of tools such as
636 install and mtree. When upgrading from version of FreeBSD where
637 the install command does not support -l, you will need to
638 install a new mergemaster command if mergemaster -p is required.
639 This can be accomplished with the command (cd src/usr.sbin/mergemaster
643 Legacy ATA stack, disabled and replaced by new CAM-based one since
644 FreeBSD 9.0, completely removed from the sources. Kernel modules
645 atadisk and atapi*, user-level tools atacontrol and burncd are
646 removed. Kernel option `options ATA_CAM` is now permanently enabled
650 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
651 and socketpair(2). Software, in particular Kerberos, may
652 automatically detect and use these during building. The resulting
653 binaries will not work on older kernels.
656 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
657 information, see the respective 20130304 entry).
660 Recent commits to callout(9) changed the size of struct callout,
661 so the KBI is probably heavily disturbed. Also, some functions
662 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
663 by macros. Every kernel module using it won't load, so rebuild
666 The ctl device has been re-enabled in GENERIC for i386 and amd64,
667 but does not initialize by default (because of the new CTL_DISABLE
668 option) to save memory. To re-enable it, remove the CTL_DISABLE
669 option from the kernel config file or set kern.cam.ctl.disable=0
670 in /boot/loader.conf.
673 The ctl device has been disabled in GENERIC for i386 and amd64.
674 This was done due to the extra memory being allocated at system
675 initialisation time by the ctl driver which was only used if
676 a CAM target device was created. This makes a FreeBSD system
677 unusable on 128MB or less of RAM.
680 A new compression method (lz4) has been merged to -HEAD. Please
681 refer to zpool-features(7) for more information.
683 Please refer to the "ZFS notes" section of this file for information
684 on upgrading boot ZFS pools.
687 A BSD-licensed patch(1) variant has been added and is installed
688 as bsdpatch, being the GNU version the default patch.
689 To inverse the logic and use the BSD-licensed one as default,
690 while having the GNU version installed as gnupatch, rebuild
691 and install world with the WITH_BSD_PATCH knob set.
694 Due to the use of the new -l option to install(1) during build
695 and install, you must take care not to directly set the INSTALL
696 make variable in your /etc/make.conf, /etc/src.conf, or on the
697 command line. If you wish to use the -C flag for all installs
698 you may be able to add INSTALL+=-C to /etc/make.conf or
702 The install(1) option -M has changed meaning and now takes an
703 argument that is a file or path to append logs to. In the
704 unlikely event that -M was the last option on the command line
705 and the command line contained at least two files and a target
706 directory the first file will have logs appended to it. The -M
707 option served little practical purpose in the last decade so its
708 use is expected to be extremely rare.
711 After switching to Clang as the default compiler some users of ZFS
712 on i386 systems started to experience stack overflow kernel panics.
713 Please consider using 'options KSTACK_PAGES=4' in such configurations.
716 GEOM_LABEL now mangles label names read from file system metadata.
717 Mangling affect labels containing spaces, non-printable characters,
718 '%' or '"'. Device names in /etc/fstab and other places may need to
722 By default, only the 10 most recent kernel dumps will be saved. To
723 restore the previous behaviour (no limit on the number of kernel dumps
724 stored in the dump directory) add the following line to /etc/rc.conf:
729 With the addition of auditdistd(8), a new auditdistd user is now
730 required during installworld. "mergemaster -p" can be used to
731 add the user prior to installworld, as documented in the handbook.
734 The sin6_scope_id member variable in struct sockaddr_in6 is now
735 filled by the kernel before passing the structure to the userland via
736 sysctl or routing socket. This means the KAME-specific embedded scope
737 id in sin6_addr.s6_addr[2] is always cleared in userland application.
738 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
739 __FreeBSD_version is bumped to 1000025.
742 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
743 This means that the world and kernel will be compiled with clang
744 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
745 and /usr/bin/cpp. To disable this behavior and revert to building
746 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
747 of current may need to bootstrap WITHOUT_CLANG first if the clang
748 build fails (its compatibility window doesn't extend to the 9 stable
752 The IPFIREWALL_FORWARD kernel option has been removed. Its
753 functionality now turned on by default.
756 The ZERO_COPY_SOCKET kernel option has been removed and
757 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
758 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
759 mechanism which is not safe and may result in kernel crashes.
760 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
761 driver supports disposeable external page sized mbuf storage.
762 Proper replacements for both zero-copy mechanisms are under
763 consideration and will eventually lead to complete removal
764 of the two kernel options.
767 The IPv4 network stack has been converted to network byte
768 order. The following modules need to be recompiled together
769 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
770 pf(4), ipfw(4), ng_ipfw(4), stf(4).
773 Support for non-MPSAFE filesystems was removed from VFS. The
774 VFS_VERSION was bumped, all filesystem modules shall be
778 All the non-MPSAFE filesystems have been disconnected from
779 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
780 portalfs, smbfs, xfs.
783 The interface cloning API and ABI has changed. The following
784 modules need to be recompiled together with kernel:
785 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
786 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
787 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
790 The sdhci driver was split in two parts: sdhci (generic SD Host
791 Controller logic) and sdhci_pci (actual hardware driver).
792 No kernel config modifications are required, but if you
793 load sdhc as a module you must switch to sdhci_pci instead.
796 Import the FUSE kernel and userland support into base system.
799 The GNU sort(1) program has been removed since the BSD-licensed
800 sort(1) has been the default for quite some time and no serious
801 problems have been reported. The corresponding WITH_GNU_SORT
805 The pfil(9) API/ABI for AF_INET family has been changed. Packet
806 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
810 The net80211(4) ABI has been changed to allow for improved driver
811 PS-POLL and power-save support. All wireless drivers need to be
812 recompiled to work with the new kernel.
815 The random(4) support for the VIA hardware random number
816 generator (`PADLOCK') is no longer enabled unconditionally.
817 Add the padlock_rng device in the custom kernel config if
818 needed. The GENERIC kernels on i386 and amd64 do include the
819 device, so the change only affects the custom kernel
823 The pf(4) packet filter ABI has been changed. pfctl(8) and
824 snmp_pf module need to be recompiled to work with new kernel.
827 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
828 to -HEAD. Pools that have empty_bpobj in active state can not be
829 imported read-write with ZFS implementations that do not support
830 this feature. For more information read the zpool-features(5)
834 The sparc64 ZFS loader has been changed to no longer try to auto-
835 detect ZFS providers based on diskN aliases but now requires these
836 to be explicitly listed in the OFW boot-device environment variable.
839 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
840 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
841 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
844 The following sysctls and tunables have been renamed for consistency
845 with other variables:
846 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
847 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
850 The sort utility has been replaced with BSD sort. For now, GNU sort
851 is also available as "gnusort" or the default can be set back to
852 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
853 installed as "bsdsort".
856 A new version of ZFS (pool version 5000) has been merged to -HEAD.
857 Starting with this version the old system of ZFS pool versioning
858 is superseded by "feature flags". This concept enables forward
859 compatibility against certain future changes in functionality of ZFS
860 pools. The first read-only compatible "feature flag" for ZFS pools
861 is named "com.delphix:async_destroy". For more information
862 read the new zpool-features(5) manual page.
863 Please refer to the "ZFS notes" section of this file for information
864 on upgrading boot ZFS pools.
867 The malloc(3) implementation embedded in libc now uses sources imported
868 as contrib/jemalloc. The most disruptive API change is to
869 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
870 delete it prior to installworld, and optionally re-create it using the
871 new format after rebooting. See malloc.conf(5) for details
872 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
876 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
877 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
878 now spelled mips. This is to aid compatibility with third-party
879 software that expects this naming scheme in uname(3). Little-endian
880 settings are unchanged. If you are updating a big-endian mips64 machine
881 from before this change, you may need to set MACHINE_ARCH=mips64 in
882 your environment before the new build system will recognize your machine.
885 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
889 Now unix domain sockets behave "as expected" on nullfs(5). Previously
890 nullfs(5) did not pass through all behaviours to the underlying layer,
891 as a result if we bound to a socket on the lower layer we could connect
892 only to the lower path; if we bound to the upper layer we could connect
893 only to the upper path. The new behavior is one can connect to both the
894 lower and the upper paths regardless what layer path one binds to.
897 The getifaddrs upgrade path broken with 20111215 has been restored.
898 If you have upgraded in between 20111215 and 20120209 you need to
899 recompile libc again with your kernel. You still need to recompile
900 world to be able to configure CARP but this restriction already
904 The set_rcvar() function has been removed from /etc/rc.subr. All
905 base and ports rc.d scripts have been updated, so if you have a
906 port installed with a script in /usr/local/etc/rc.d you can either
907 hand-edit the rcvar= line, or reinstall the port.
909 An easy way to handle the mass-update of /etc/rc.d:
910 rm /etc/rc.d/* && mergemaster -i
913 panic(9) now stops other CPUs in the SMP systems, disables interrupts
914 on the current CPU and prevents other threads from running.
915 This behavior can be reverted using the kern.stop_scheduler_on_panic
917 The new behavior can be incompatible with kern.sync_on_panic.
920 The carp(4) facility has been changed significantly. Configuration
921 of the CARP protocol via ifconfig(8) has changed, as well as format
922 of CARP events submitted to devd(8) has changed. See manual pages
923 for more information. The arpbalance feature of carp(4) is currently
924 not supported anymore.
926 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
927 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
928 need to be recompiled.
931 The acpi_wmi(4) status device /dev/wmistat has been renamed to
935 The option VFS_ALLOW_NONMPSAFE option has been added in order to
936 explicitely support non-MPSAFE filesystems.
937 It is on by default for all supported platform at this present
941 The broken amd(4) driver has been replaced with esp(4) in the amd64,
942 i386 and pc98 GENERIC kernel configuration files.
945 sysinstall has been removed
948 The stable/9 branch created in subversion. This corresponds to the
949 RELENG_9 branch in CVS.
955 Avoid using make -j when upgrading. While generally safe, there are
956 sometimes problems using -j to upgrade. If your upgrade fails with
957 -j, please try again without -j. From time to time in the past there
958 have been problems using -j with buildworld and/or installworld. This
959 is especially true when upgrading between "distant" versions (eg one
960 that cross a major release boundary or several minor releases, or when
961 several months have passed on the -current branch).
963 Sometimes, obscure build problems are the result of environment
964 poisoning. This can happen because the make utility reads its
965 environment when searching for values for global variables. To run
966 your build attempts in an "environmental clean room", prefix all make
967 commands with 'env -i '. See the env(1) manual page for more details.
969 When upgrading from one major version to another it is generally best
970 to upgrade to the latest code in the currently installed branch first,
971 then do an upgrade to the new branch. This is the best-tested upgrade
972 path, and has the highest probability of being successful. Please try
973 this approach before reporting problems with a major version upgrade.
975 When upgrading a live system, having a root shell around before
976 installing anything can help undo problems. Not having a root shell
977 around can lead to problems if pam has changed too much from your
978 starting point to allow continued authentication after the upgrade.
982 When upgrading the boot ZFS pool to a new version, always follow
985 1.) recompile and reinstall the ZFS boot loader and boot block
986 (this is part of "make buildworld" and "make installworld")
988 2.) update the ZFS boot block on your boot drive
990 The following example updates the ZFS boot block on the first
991 partition (freebsd-boot) of a GPT partitioned drive ada0:
992 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
994 Non-boot pools do not need these updates.
998 If you are updating from a prior version of FreeBSD (even one just
999 a few days old), you should follow this procedure. It is the most
1000 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1002 make kernel-toolchain
1003 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1004 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1006 To test a kernel once
1007 ---------------------
1008 If you just want to boot a kernel once (because you are not sure
1009 if it works, or if you want to boot a known bad kernel to provide
1010 debugging information) run
1011 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1012 nextboot -k testkernel
1014 To just build a kernel when you know that it won't mess you up
1015 --------------------------------------------------------------
1016 This assumes you are already running a CURRENT system. Replace
1017 ${arch} with the architecture of your machine (e.g. "i386",
1018 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1020 cd src/sys/${arch}/conf
1021 config KERNEL_NAME_HERE
1022 cd ../compile/KERNEL_NAME_HERE
1027 If this fails, go to the "To build a kernel" section.
1029 To rebuild everything and install it on the current system.
1030 -----------------------------------------------------------
1031 # Note: sometimes if you are running current you gotta do more than
1032 # is listed here if you are upgrading from a really old current.
1034 <make sure you have good level 0 dumps>
1036 make kernel KERNCONF=YOUR_KERNEL_HERE
1038 <reboot in single user> [3]
1045 To cross-install current onto a separate partition
1046 --------------------------------------------------
1047 # In this approach we use a separate partition to hold
1048 # current's root, 'usr', and 'var' directories. A partition
1049 # holding "/", "/usr" and "/var" should be about 2GB in
1052 <make sure you have good level 0 dumps>
1055 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1056 <maybe newfs current's root partition>
1057 <mount current's root partition on directory ${CURRENT_ROOT}>
1058 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1059 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1060 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1061 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1062 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1063 <reboot into current>
1064 <do a "native" rebuild/install as described in the previous section>
1065 <maybe install compatibility libraries from ports/misc/compat*>
1069 To upgrade in-place from stable to current
1070 ----------------------------------------------
1071 <make sure you have good level 0 dumps>
1073 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1075 <reboot in single user> [3]
1082 Make sure that you've read the UPDATING file to understand the
1083 tweaks to various things you need. At this point in the life
1084 cycle of current, things change often and you are on your own
1085 to cope. The defaults can also change, so please read ALL of
1086 the UPDATING entries.
1088 Also, if you are tracking -current, you must be subscribed to
1089 freebsd-current@freebsd.org. Make sure that before you update
1090 your sources that you have read and understood all the recent
1091 messages there. If in doubt, please track -stable which has
1092 much fewer pitfalls.
1094 [1] If you have third party modules, such as vmware, you
1095 should disable them at this point so they don't crash your
1098 [3] From the bootblocks, boot -s, and then do
1103 adjkerntz -i # if CMOS is wall time
1104 Also, when doing a major release upgrade, it is required that
1105 you boot into single user mode to do the installworld.
1107 [4] Note: This step is non-optional. Failure to do this step
1108 can result in a significant reduction in the functionality of the
1109 system. Attempting to do it by hand is not recommended and those
1110 that pursue this avenue should read this file carefully, as well
1111 as the archives of freebsd-current and freebsd-hackers mailing lists
1112 for potential gotchas. The -U option is also useful to consider.
1113 See mergemaster(8) for more information.
1115 [5] Usually this step is a noop. However, from time to time
1116 you may need to do this if you get unknown user in the following
1117 step. It never hurts to do it all the time. You may need to
1118 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1119 install) after the buildworld before this step if you last updated
1120 from current before 20130425 or from -stable before 20130430.
1122 [6] This only deletes old files and directories. Old libraries
1123 can be deleted by "make delete-old-libs", but you have to make
1124 sure that no program is using those libraries anymore.
1126 [8] In order to have a kernel that can run the 4.x binaries needed to
1127 do an installworld, you must include the COMPAT_FREEBSD4 option in
1128 your kernel. Failure to do so may leave you with a system that is
1129 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1130 required to run the 5.x binaries on more recent kernels. And so on
1131 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1133 Make sure that you merge any new devices from GENERIC since the
1134 last time you updated your kernel config file.
1136 [9] When checking out sources, you must include the -P flag to have
1137 cvs prune empty directories.
1139 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1140 "?=" instead of the "=" assignment operator, so that buildworld can
1141 override the CPUTYPE if it needs to.
1143 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1144 not on the command line, or in /etc/make.conf. buildworld will
1145 warn if it is improperly defined.
1148 This file contains a list, in reverse chronological order, of major
1149 breakages in tracking -current. It is not guaranteed to be a complete
1150 list of such breakages, and only contains entries since October 10, 2007.
1151 If you need to see UPDATING entries from before that date, you will need
1152 to fetch an UPDATING file from an older FreeBSD release.
1154 Copyright information:
1156 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1158 Redistribution, publication, translation and use, with or without
1159 modification, in full or in part, in any form or format of this
1160 document are permitted without further permission from the author.
1162 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1163 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1164 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1165 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1166 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1167 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1168 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1169 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1170 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1171 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1172 POSSIBILITY OF SUCH DAMAGE.
1174 Contact Warner Losh if you have any questions about your use of