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