1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process from
17 older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW:
20 FreeBSD 11.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
36 the 20141231 entry below for information about prerequisites and
37 upgrading, if you are not already using 3.5.0 or higher.
40 The 32-bit PowerPC kernel has been changed to a position-independent
41 executable. This can only be booted with a version of loader(8)
42 newer than January 31, 2015, so make sure to update both world and
43 kernel before rebooting.
46 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
47 but before r278950, the RNG was not seeded properly. Immediately
48 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
49 ssh keys or openssl keys) that were generated w/ a kernel from that
50 range. This does not affect programs that directly used /dev/random
51 or /dev/urandom. All userland uses of arc4random(3) are affected.
54 The autofs(4) ABI was changed in order to restore binary compatibility
55 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
59 The powerpc64 kernel has been changed to a position-independent
60 executable. This can only be booted with a new version of loader(8),
61 so make sure to update both world and kernel before rebooting.
64 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
65 only release, no new features have been added. Please see the 20141231
66 entry below for information about prerequisites and upgrading, if you
67 are not already using 3.5.0.
70 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
71 taken from the ELF Tool Chain project rather than GNU binutils. They
72 should be drop-in replacements, with the addition of arm64 support.
73 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
74 binutils tools, if necessary.
77 The default Unbound configuration now enables remote control
78 using a local socket. Users who have already enabled the
79 local_unbound service should regenerate their configuration
80 by running "service local_unbound setup" as root.
83 The GNU texinfo and GNU info pages have been removed.
84 To be able to view GNU info pages please install texinfo from ports.
87 Clang, llvm and lldb have been upgraded to 3.5.0 release.
89 As of this release, a prerequisite for building clang, llvm and lldb is
90 a C++11 capable compiler and C++11 standard library. This means that to
91 be able to successfully build the cross-tools stage of buildworld, with
92 clang as the bootstrap compiler, your system compiler or cross compiler
93 should either be clang 3.3 or later, or gcc 4.8 or later, and your
94 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
97 On any standard FreeBSD 10.x or 11.x installation, where clang and
98 libc++ are on by default (that is, on x86 or arm), this should work out
101 On 9.x installations where clang is enabled by default, e.g. on x86 and
102 powerpc, libc++ will not be enabled by default, so libc++ should be
103 built (with clang) and installed first. If both clang and libc++ are
104 missing, build clang first, then use it to build libc++.
106 On 8.x and earlier installations, upgrade to 9.x first, and then follow
107 the instructions for 9.x above.
109 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
110 default, and do not build clang.
112 Many embedded systems are resource constrained, and will not be able to
113 build clang in a reasonable time, or in some cases at all. In those
114 cases, cross building bootable systems on amd64 is a workaround.
116 This new version of clang introduces a number of new warnings, of which
117 the following are most likely to appear:
121 This warns in two cases, for both C and C++:
122 * When the code is trying to take the absolute value of an unsigned
123 quantity, which is effectively a no-op, and almost never what was
124 intended. The code should be fixed, if at all possible. If you are
125 sure that the unsigned quantity can be safely cast to signed, without
126 loss of information or undefined behavior, you can add an explicit
127 cast, or disable the warning.
129 * When the code is trying to take an absolute value, but the called
130 abs() variant is for the wrong type, which can lead to truncation.
131 If you want to disable the warning instead of fixing the code, please
132 make sure that truncation will not occur, or it might lead to unwanted
135 -Wtautological-undefined-compare and
136 -Wundefined-bool-conversion
138 These warn when C++ code is trying to compare 'this' against NULL, while
139 'this' should never be NULL in well-defined C++ code. However, there is
140 some legacy (pre C++11) code out there, which actively abuses this
141 feature, which was less strictly defined in previous C++ versions.
143 Squid and openjdk do this, for example. The warning can be turned off
144 for C++98 and earlier, but compiling the code in C++11 mode might result
145 in unexpected behavior; for example, the parts of the program that are
146 unreachable could be optimized away.
149 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
150 kernel sources have been removed. The .h files remain, since some
151 utilities include them. This will need to be fixed later.
152 If "mount -t oldnfs ..." is attempted, it will fail.
153 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
154 the utilities will report errors.
157 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
158 directories to top level SUBDIR variable when their parent
159 directory is included in LOCAL_DIRS. Users with build systems with
160 such hierarchies and without SUBDIR entries in the parent
161 directory Makefiles should add them or add the directories to
165 faith(4) and faithd(8) have been removed from the base system. Faith
166 has been obsolete for a very long time.
169 vt(4), the new console driver, is enabled by default. It brings
170 support for Unicode and double-width characters, as well as
171 support for UEFI and integration with the KMS kernel video
174 You may need to update your console settings in /etc/rc.conf,
175 most probably the keymap. During boot, /etc/rc.d/syscons will
176 indicate what you need to do.
178 vt(4) still has issues and lacks some features compared to
179 syscons(4). See the wiki for up-to-date information:
180 https://wiki.freebsd.org/Newcons
182 If you want to keep using syscons(4), you can do so by adding
183 the following line to /boot/loader.conf:
187 pjdfstest has been integrated into kyua as an opt-in test suite.
188 Please see share/doc/pjdfstest/README for more details on how to
192 gperf has been removed from the base system for architectures
193 that use clang. Ports that require gperf will obtain it from the
197 pjdfstest has been moved from tools/regression/pjdfstest to
201 At svn r271982, The default linux compat kernel ABI has been adjusted
202 to 2.6.18 in support of the linux-c6 compat ports infrastructure
203 update. If you wish to continue using the linux-f10 compat ports,
204 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
205 encouraged to update their linux-compat packages to linux-c6 during
206 their next update cycle.
209 The ofwfb driver, used to provide a graphics console on PowerPC when
210 using vt(4), no longer allows mmap() of all physical memory. This
211 will prevent Xorg on PowerPC with some ATI graphics cards from
212 initializing properly unless x11-servers/xorg-server is updated to
216 The xdev targets have been converted to using TARGET and
217 TARGET_ARCH instead of XDEV and XDEV_ARCH.
220 The default unbound configuration has been modified to address
221 issues with reverse lookups on networks that use private
222 address ranges. If you use the local_unbound service, run
223 "service local_unbound setup" as root to regenerate your
224 configuration, then "service local_unbound reload" to load the
228 The GNU texinfo and GNU info pages are not built and installed
229 anymore, WITH_INFO knob has been added to allow to built and install
231 UPDATE: see 20150102 entry on texinfo's removal
234 The GNU readline library is now an INTERNALLIB - that is, it is
235 statically linked into consumers (GDB and variants) in the base
236 system, and the shared library is no longer installed. The
237 devel/readline port is available for third party software that
241 The Itanium architecture (ia64) has been removed from the list of
242 known architectures. This is the first step in the removal of the
246 Commit r268115 has added NFSv4.1 server support, merged from
247 projects/nfsv4.1-server. Since this includes changes to the
248 internal interfaces between the NFS related modules, a full
249 build of the kernel and modules will be necessary.
250 __FreeBSD_version has been bumped.
253 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
254 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
255 which differs from the behaviour controlled by this knob.)
258 Maximal length of the serial number in CTL was increased from 16 to
259 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
260 and ctld, need to be rebuilt to work with a new kernel.
263 The libatf-c and libatf-c++ major versions were downgraded to 0 and
264 1 respectively to match the upstream numbers. They were out of
265 sync because, when they were originally added to FreeBSD, the
266 upstream versions were not respected. These libraries are private
267 and not yet built by default, so renumbering them should be a
268 non-issue. However, unclean source trees will yield broken test
269 programs once the operator executes "make delete-old-libs" after a
272 Additionally, the atf-sh binary was made private by moving it into
273 /usr/libexec/. Already-built shell test programs will keep the
274 path to the old binary so they will break after "make delete-old"
277 If you are using WITH_TESTS=yes (not the default), wipe the object
278 tree and rebuild from scratch to prevent spurious test failures.
279 This is only needed once: the misnumbered libraries and misplaced
280 binaries have been added to OptionalObsoleteFiles.inc so they will
281 be removed during a clean upgrade.
284 Clang and llvm have been upgraded to 3.4.1 release.
287 We bogusly installed src.opts.mk in /usr/share/mk. This file should
288 be removed to avoid issues in the future (and has been added to
292 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
293 past, it affected all builds that used the bsd.*.mk files. The old
294 behavior was a bug, but people may have relied upon it. To get this
295 behavior back, you can .include /etc/src.conf from /etc/make.conf
296 (which is still global and isn't changed). This also changes the
297 behavior of incremental builds inside the tree of individual
298 directories. Set MAKESYSPATH to ".../share/mk" to do that.
299 Although this has survived make universe and some upgrade scenarios,
300 other upgrade scenarios may have broken. At least one form of
301 temporary breakage was fixed with MAKESYSPATH settings for buildworld
302 as well... In cases where MAKESYSPATH isn't working with this
303 setting, you'll need to set it to the full path to your tree.
305 One side effect of all this cleaning up is that bsd.compiler.mk
306 is no longer implicitly included by bsd.own.mk. If you wish to
307 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
311 The lindev device has been removed since /dev/full has been made a
312 standard device. __FreeBSD_version has been bumped.
315 The knob WITHOUT_VI was added to the base system, which controls
316 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
317 in order to reorder files share/termcap and didn't build ex(1) as a
318 build tool, so building/installing with WITH_VI is highly advised for
319 build hosts for older releases.
321 This issue has been fixed in stable/9 and stable/10 in r277022 and
322 r276991, respectively.
325 The YES_HESIOD knob has been removed. It has been obsolete for
326 a decade. Please move to using WITH_HESIOD instead or your builds
327 will silently lack HESIOD.
330 The uart(4) driver has been changed with respect to its handling
331 of the low-level console. Previously the uart(4) driver prevented
332 any process from changing the baudrate or the CLOCAL and HUPCL
333 control flags. By removing the restrictions, operators can make
334 changes to the serial console port without having to reboot.
335 However, when getty(8) is started on the serial device that is
336 associated with the low-level console, a misconfigured terminal
337 line in /etc/ttys will now have a real impact.
338 Before upgrading the kernel, make sure that /etc/ttys has the
339 serial console device configured as 3wire without baudrate to
340 preserve the previous behaviour. E.g:
341 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
344 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
345 to improve performance. To re-enable it, if needed, run rpcbind
346 with command line option -W.
349 Switched back to the GPL dtc compiler due to updates in the upstream
350 dts files not being supported by the BSDL dtc compiler. You will need
351 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
352 may result while building dtb files during a kernel build if you fail
353 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
356 Clang and llvm have been upgraded to 3.4 release.
359 The nve(4) driver has been removed. Please use the nfe(4) driver
360 for NVIDIA nForce MCP Ethernet adapters instead.
363 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
364 This could cause certain C++ applications using shared libraries built
365 against the previous version of libc++ to crash. The incompatibility
366 has now been fixed, but any C++ applications or shared libraries built
367 between r261283 and r261801 should be recompiled.
370 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
371 capability mode support. Please note that enabling the feature in
372 kernel is still highly recommended.
375 OpenSSH is now built with sandbox support, and will use sandbox as
376 the default privilege separation method. This requires Capsicum
377 capability mode support in kernel.
380 The libelf and libdwarf libraries have been updated to newer
381 versions from upstream. Shared library version numbers for
382 these two libraries were bumped. Any ports or binaries
383 requiring these two libraries should be recompiled.
384 __FreeBSD_version is bumped to 1100006.
387 If a Makefile in a tests/ directory was auto-generating a Kyuafile
388 instead of providing an explicit one, this would prevent such
389 Makefile from providing its own Kyuafile in the future during
390 NO_CLEAN builds. This has been fixed in the Makefiles but manual
391 intervention is needed to clean an objdir if you use NO_CLEAN:
392 # find /usr/obj -name Kyuafile | xargs rm -f
395 The behavior of gss_pseudo_random() for the krb5 mechanism
396 has changed, for applications requesting a longer random string
397 than produced by the underlying enctype's pseudo-random() function.
398 In particular, the random string produced from a session key of
399 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
400 be different at the 17th octet and later, after this change.
401 The counter used in the PRF+ construction is now encoded as a
402 big-endian integer in accordance with RFC 4402.
403 __FreeBSD_version is bumped to 1100004.
406 The WITHOUT_ATF build knob has been removed and its functionality
407 has been subsumed into the more generic WITHOUT_TESTS. If you were
408 using the former to disable the build of the ATF libraries, you
409 should change your settings to use the latter.
412 The default version of mtree is nmtree which is obtained from
413 NetBSD. The output is generally the same, but may vary
414 slightly. If you found you need identical output adding
415 "-F freebsd9" to the command line should do the trick. For the
416 time being, the old mtree is available as fmtree.
419 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
420 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
421 1.1.4_8 and verify bsdyml not linked in, before running "make
423 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
425 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
428 The rc.d/jail script has been updated to support jail(8)
429 configuration file. The "jail_<jname>_*" rc.conf(5) variables
430 for per-jail configuration are automatically converted to
431 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
432 This is transparently backward compatible. See below about some
433 incompatibilities and rc.conf(5) manual page for more details.
435 These variables are now deprecated in favor of jail(8) configuration
436 file. One can use "rc.d/jail config <jname>" command to generate
437 a jail(8) configuration file in /var/run/jail.<jname>.conf without
438 running the jail(8) utility. The default pathname of the
439 configuration file is /etc/jail.conf and can be specified by
440 using $jail_conf or $jail_<jname>_conf variables.
442 Please note that jail_devfs_ruleset accepts an integer at
443 this moment. Please consider to rewrite the ruleset name
447 BIND has been removed from the base system. If all you need
448 is a local resolver, simply enable and start the local_unbound
449 service instead. Otherwise, several versions of BIND are
450 available in the ports tree. The dns/bind99 port is one example.
452 With this change, nslookup(1) and dig(1) are no longer in the base
453 system. Users should instead use host(1) and drill(1) which are
454 in the base system. Alternatively, nslookup and dig can
455 be obtained by installing the dns/bind-tools port.
458 With the addition of unbound(8), a new unbound user is now
459 required during installworld. "mergemaster -p" can be used to
460 add the user prior to installworld, as documented in the handbook.
463 OpenSSH is now built with DNSSEC support, and will by default
464 silently trust signed SSHFP records. This can be controlled with
465 the VerifyHostKeyDNS client configuration setting. DNSSEC support
466 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
469 The GNU Compiler Collection and C++ standard library (libstdc++)
470 are no longer built by default on platforms where clang is the system
471 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
475 The PROCDESC kernel option is now part of the GENERIC kernel
476 configuration and is required for the rwhod(8) to work.
477 If you are using custom kernel configuration, you should include
481 The API and ABI related to the Capsicum framework was modified
482 in backward incompatible way. The userland libraries and programs
483 have to be recompiled to work with the new kernel. This includes the
484 following libraries and programs, but the whole buildworld is
485 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
486 kdump, procstat, rwho, rwhod, uniq.
489 AES-NI intrinsic support has been added to gcc. The AES-NI module
490 has been updated to use this support. A new gcc is required to build
491 the aesni module on both i386 and amd64.
494 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
495 Thus "device padlock_rng" and "device rdrand_rng" should be
496 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
499 WITH_ICONV has been split into two feature sets. WITH_ICONV now
500 enables just the iconv* functionality and is now on by default.
501 WITH_LIBICONV_COMPAT enables the libiconv api and link time
502 compatability. Set WITHOUT_ICONV to build the old way.
503 If you have been using WITH_ICONV before, you will very likely
504 need to turn on WITH_LIBICONV_COMPAT.
507 INVARIANTS option now enables DEBUG for code with OpenSolaris and
508 Illumos origin, including ZFS. If you have INVARIANTS in your
509 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
511 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
512 locks if WITNESS option was set. Because that generated a lot of
513 witness(9) reports and all of them were believed to be false
514 positives, this is no longer done. New option OPENSOLARIS_WITNESS
515 can be used to achieve the previous behavior.
518 Timer values in IPv6 data structures now use time_uptime instead
519 of time_second. Although this is not a user-visible functional
520 change, userland utilities which directly use them---ndp(8),
521 rtadvd(8), and rtsold(8) in the base system---need to be updated
525 find -delete can now delete the pathnames given as arguments,
526 instead of only files found below them or if the pathname did
527 not contain any slashes. Formerly, the following error message
530 find: -delete: <path>: relative path potentially not safe
532 Deleting the pathnames given as arguments can be prevented
533 without error messages using -mindepth 1 or by changing
534 directory and passing "." as argument to find. This works in the
535 old as well as the new version of find.
538 Behavior of devfs rules path matching has been changed.
539 Pattern is now always matched against fully qualified devfs
540 path and slash characters must be explicitly matched by
541 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
542 subdirectories must be reviewed.
545 The default ARM ABI has changed to the ARM EABI. The old ABI is
546 incompatible with the ARM EABI and all programs and modules will
547 need to be rebuilt to work with a new kernel.
549 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
551 NOTE: Support for the old ABI will be removed in the future and
552 users are advised to upgrade.
555 pkg_install has been disconnected from the build if you really need it
556 you should add WITH_PKGTOOLS in your src.conf(5).
559 Most of network statistics structures were changed to be able
560 keep 64-bits counters. Thus all tools, that work with networking
561 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
564 Fix targets that run multiple make's to use && rather than ;
565 so that subsequent steps depend on success of previous.
567 NOTE: if building 'universe' with -j* on stable/8 or stable/9
568 it would be better to start the build using bmake, to avoid
569 overloading the machine.
572 Fix a bug that allowed a tracing process (e.g. gdb) to write
573 to a memory-mapped file in the traced process's address space
574 even if neither the traced process nor the tracing process had
575 write access to that file.
578 CVS has been removed from the base system. An exact copy
579 of the code is available from the devel/cvs port.
582 Some people report the following error after the switch to bmake:
584 make: illegal option -- J
585 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
587 *** [buildworld] Error code 2
589 this likely due to an old instance of make in
590 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
591 which src/Makefile will use that blindly, if it exists, so if
592 you see the above error:
594 rm -rf `make -V MAKEPATH`
599 Use bmake by default.
600 Whereas before one could choose to build with bmake via
601 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
602 make. The goal is to remove these knobs for 10-RELEASE.
604 It is worth noting that bmake (like gmake) treats the command
605 line as the unit of failure, rather than statements within the
606 command line. Thus '(cd some/where && dosomething)' is safer
607 than 'cd some/where; dosomething'. The '()' allows consistent
608 behavior in parallel build.
611 Fix a bug that allows NFS clients to issue READDIR on files.
614 The WITHOUT_IDEA option has been removed because
615 the IDEA patent expired.
618 The sysctl which controls TRIM support under ZFS has been renamed
619 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
623 The mergemaster command now uses the default MAKEOBJDIRPREFIX
624 rather than creating it's own in the temporary directory in
625 order allow access to bootstrapped versions of tools such as
626 install and mtree. When upgrading from version of FreeBSD where
627 the install command does not support -l, you will need to
628 install a new mergemaster command if mergemaster -p is required.
629 This can be accomplished with the command (cd src/usr.sbin/mergemaster
633 Legacy ATA stack, disabled and replaced by new CAM-based one since
634 FreeBSD 9.0, completely removed from the sources. Kernel modules
635 atadisk and atapi*, user-level tools atacontrol and burncd are
636 removed. Kernel option `options ATA_CAM` is now permanently enabled
640 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
641 and socketpair(2). Software, in particular Kerberos, may
642 automatically detect and use these during building. The resulting
643 binaries will not work on older kernels.
646 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
647 information, see the respective 20130304 entry).
650 Recent commits to callout(9) changed the size of struct callout,
651 so the KBI is probably heavily disturbed. Also, some functions
652 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
653 by macros. Every kernel module using it won't load, so rebuild
656 The ctl device has been re-enabled in GENERIC for i386 and amd64,
657 but does not initialize by default (because of the new CTL_DISABLE
658 option) to save memory. To re-enable it, remove the CTL_DISABLE
659 option from the kernel config file or set kern.cam.ctl.disable=0
660 in /boot/loader.conf.
663 The ctl device has been disabled in GENERIC for i386 and amd64.
664 This was done due to the extra memory being allocated at system
665 initialisation time by the ctl driver which was only used if
666 a CAM target device was created. This makes a FreeBSD system
667 unusable on 128MB or less of RAM.
670 A new compression method (lz4) has been merged to -HEAD. Please
671 refer to zpool-features(7) for more information.
673 Please refer to the "ZFS notes" section of this file for information
674 on upgrading boot ZFS pools.
677 A BSD-licensed patch(1) variant has been added and is installed
678 as bsdpatch, being the GNU version the default patch.
679 To inverse the logic and use the BSD-licensed one as default,
680 while having the GNU version installed as gnupatch, rebuild
681 and install world with the WITH_BSD_PATCH knob set.
684 Due to the use of the new -l option to install(1) during build
685 and install, you must take care not to directly set the INSTALL
686 make variable in your /etc/make.conf, /etc/src.conf, or on the
687 command line. If you wish to use the -C flag for all installs
688 you may be able to add INSTALL+=-C to /etc/make.conf or
692 The install(1) option -M has changed meaning and now takes an
693 argument that is a file or path to append logs to. In the
694 unlikely event that -M was the last option on the command line
695 and the command line contained at least two files and a target
696 directory the first file will have logs appended to it. The -M
697 option served little practical purpose in the last decade so its
698 use is expected to be extremely rare.
701 After switching to Clang as the default compiler some users of ZFS
702 on i386 systems started to experience stack overflow kernel panics.
703 Please consider using 'options KSTACK_PAGES=4' in such configurations.
706 GEOM_LABEL now mangles label names read from file system metadata.
707 Mangling affect labels containing spaces, non-printable characters,
708 '%' or '"'. Device names in /etc/fstab and other places may need to
712 By default, only the 10 most recent kernel dumps will be saved. To
713 restore the previous behaviour (no limit on the number of kernel dumps
714 stored in the dump directory) add the following line to /etc/rc.conf:
719 With the addition of auditdistd(8), a new auditdistd user is now
720 required during installworld. "mergemaster -p" can be used to
721 add the user prior to installworld, as documented in the handbook.
724 The sin6_scope_id member variable in struct sockaddr_in6 is now
725 filled by the kernel before passing the structure to the userland via
726 sysctl or routing socket. This means the KAME-specific embedded scope
727 id in sin6_addr.s6_addr[2] is always cleared in userland application.
728 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
729 __FreeBSD_version is bumped to 1000025.
732 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
733 This means that the world and kernel will be compiled with clang
734 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
735 and /usr/bin/cpp. To disable this behavior and revert to building
736 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
737 of current may need to bootstrap WITHOUT_CLANG first if the clang
738 build fails (its compatibility window doesn't extend to the 9 stable
742 The IPFIREWALL_FORWARD kernel option has been removed. Its
743 functionality now turned on by default.
746 The ZERO_COPY_SOCKET kernel option has been removed and
747 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
748 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
749 mechanism which is not safe and may result in kernel crashes.
750 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
751 driver supports disposeable external page sized mbuf storage.
752 Proper replacements for both zero-copy mechanisms are under
753 consideration and will eventually lead to complete removal
754 of the two kernel options.
757 The IPv4 network stack has been converted to network byte
758 order. The following modules need to be recompiled together
759 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
760 pf(4), ipfw(4), ng_ipfw(4), stf(4).
763 Support for non-MPSAFE filesystems was removed from VFS. The
764 VFS_VERSION was bumped, all filesystem modules shall be
768 All the non-MPSAFE filesystems have been disconnected from
769 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
770 portalfs, smbfs, xfs.
773 The interface cloning API and ABI has changed. The following
774 modules need to be recompiled together with kernel:
775 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
776 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
777 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
780 The sdhci driver was split in two parts: sdhci (generic SD Host
781 Controller logic) and sdhci_pci (actual hardware driver).
782 No kernel config modifications are required, but if you
783 load sdhc as a module you must switch to sdhci_pci instead.
786 Import the FUSE kernel and userland support into base system.
789 The GNU sort(1) program has been removed since the BSD-licensed
790 sort(1) has been the default for quite some time and no serious
791 problems have been reported. The corresponding WITH_GNU_SORT
795 The pfil(9) API/ABI for AF_INET family has been changed. Packet
796 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
800 The net80211(4) ABI has been changed to allow for improved driver
801 PS-POLL and power-save support. All wireless drivers need to be
802 recompiled to work with the new kernel.
805 The random(4) support for the VIA hardware random number
806 generator (`PADLOCK') is no longer enabled unconditionally.
807 Add the padlock_rng device in the custom kernel config if
808 needed. The GENERIC kernels on i386 and amd64 do include the
809 device, so the change only affects the custom kernel
813 The pf(4) packet filter ABI has been changed. pfctl(8) and
814 snmp_pf module need to be recompiled to work with new kernel.
817 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
818 to -HEAD. Pools that have empty_bpobj in active state can not be
819 imported read-write with ZFS implementations that do not support
820 this feature. For more information read the zpool-features(5)
824 The sparc64 ZFS loader has been changed to no longer try to auto-
825 detect ZFS providers based on diskN aliases but now requires these
826 to be explicitly listed in the OFW boot-device environment variable.
829 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
830 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
831 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
834 The following sysctls and tunables have been renamed for consistency
835 with other variables:
836 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
837 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
840 The sort utility has been replaced with BSD sort. For now, GNU sort
841 is also available as "gnusort" or the default can be set back to
842 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
843 installed as "bsdsort".
846 A new version of ZFS (pool version 5000) has been merged to -HEAD.
847 Starting with this version the old system of ZFS pool versioning
848 is superseded by "feature flags". This concept enables forward
849 compatibility against certain future changes in functionality of ZFS
850 pools. The first read-only compatible "feature flag" for ZFS pools
851 is named "com.delphix:async_destroy". For more information
852 read the new zpool-features(5) manual page.
853 Please refer to the "ZFS notes" section of this file for information
854 on upgrading boot ZFS pools.
857 The malloc(3) implementation embedded in libc now uses sources imported
858 as contrib/jemalloc. The most disruptive API change is to
859 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
860 delete it prior to installworld, and optionally re-create it using the
861 new format after rebooting. See malloc.conf(5) for details
862 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
866 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
867 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
868 now spelled mips. This is to aid compatibility with third-party
869 software that expects this naming scheme in uname(3). Little-endian
870 settings are unchanged. If you are updating a big-endian mips64 machine
871 from before this change, you may need to set MACHINE_ARCH=mips64 in
872 your environment before the new build system will recognize your machine.
875 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
879 Now unix domain sockets behave "as expected" on nullfs(5). Previously
880 nullfs(5) did not pass through all behaviours to the underlying layer,
881 as a result if we bound to a socket on the lower layer we could connect
882 only to the lower path; if we bound to the upper layer we could connect
883 only to the upper path. The new behavior is one can connect to both the
884 lower and the upper paths regardless what layer path one binds to.
887 The getifaddrs upgrade path broken with 20111215 has been restored.
888 If you have upgraded in between 20111215 and 20120209 you need to
889 recompile libc again with your kernel. You still need to recompile
890 world to be able to configure CARP but this restriction already
894 The set_rcvar() function has been removed from /etc/rc.subr. All
895 base and ports rc.d scripts have been updated, so if you have a
896 port installed with a script in /usr/local/etc/rc.d you can either
897 hand-edit the rcvar= line, or reinstall the port.
899 An easy way to handle the mass-update of /etc/rc.d:
900 rm /etc/rc.d/* && mergemaster -i
903 panic(9) now stops other CPUs in the SMP systems, disables interrupts
904 on the current CPU and prevents other threads from running.
905 This behavior can be reverted using the kern.stop_scheduler_on_panic
907 The new behavior can be incompatible with kern.sync_on_panic.
910 The carp(4) facility has been changed significantly. Configuration
911 of the CARP protocol via ifconfig(8) has changed, as well as format
912 of CARP events submitted to devd(8) has changed. See manual pages
913 for more information. The arpbalance feature of carp(4) is currently
914 not supported anymore.
916 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
917 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
918 need to be recompiled.
921 The acpi_wmi(4) status device /dev/wmistat has been renamed to
925 The option VFS_ALLOW_NONMPSAFE option has been added in order to
926 explicitely support non-MPSAFE filesystems.
927 It is on by default for all supported platform at this present
931 The broken amd(4) driver has been replaced with esp(4) in the amd64,
932 i386 and pc98 GENERIC kernel configuration files.
935 sysinstall has been removed
938 The stable/9 branch created in subversion. This corresponds to the
939 RELENG_9 branch in CVS.
945 Avoid using make -j when upgrading. While generally safe, there are
946 sometimes problems using -j to upgrade. If your upgrade fails with
947 -j, please try again without -j. From time to time in the past there
948 have been problems using -j with buildworld and/or installworld. This
949 is especially true when upgrading between "distant" versions (eg one
950 that cross a major release boundary or several minor releases, or when
951 several months have passed on the -current branch).
953 Sometimes, obscure build problems are the result of environment
954 poisoning. This can happen because the make utility reads its
955 environment when searching for values for global variables. To run
956 your build attempts in an "environmental clean room", prefix all make
957 commands with 'env -i '. See the env(1) manual page for more details.
959 When upgrading from one major version to another it is generally best
960 to upgrade to the latest code in the currently installed branch first,
961 then do an upgrade to the new branch. This is the best-tested upgrade
962 path, and has the highest probability of being successful. Please try
963 this approach before reporting problems with a major version upgrade.
965 When upgrading a live system, having a root shell around before
966 installing anything can help undo problems. Not having a root shell
967 around can lead to problems if pam has changed too much from your
968 starting point to allow continued authentication after the upgrade.
972 When upgrading the boot ZFS pool to a new version, always follow
975 1.) recompile and reinstall the ZFS boot loader and boot block
976 (this is part of "make buildworld" and "make installworld")
978 2.) update the ZFS boot block on your boot drive
980 The following example updates the ZFS boot block on the first
981 partition (freebsd-boot) of a GPT partitioned drive ada0:
982 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
984 Non-boot pools do not need these updates.
988 If you are updating from a prior version of FreeBSD (even one just
989 a few days old), you should follow this procedure. It is the most
990 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
992 make kernel-toolchain
993 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
994 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
996 To test a kernel once
997 ---------------------
998 If you just want to boot a kernel once (because you are not sure
999 if it works, or if you want to boot a known bad kernel to provide
1000 debugging information) run
1001 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1002 nextboot -k testkernel
1004 To just build a kernel when you know that it won't mess you up
1005 --------------------------------------------------------------
1006 This assumes you are already running a CURRENT system. Replace
1007 ${arch} with the architecture of your machine (e.g. "i386",
1008 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1010 cd src/sys/${arch}/conf
1011 config KERNEL_NAME_HERE
1012 cd ../compile/KERNEL_NAME_HERE
1017 If this fails, go to the "To build a kernel" section.
1019 To rebuild everything and install it on the current system.
1020 -----------------------------------------------------------
1021 # Note: sometimes if you are running current you gotta do more than
1022 # is listed here if you are upgrading from a really old current.
1024 <make sure you have good level 0 dumps>
1026 make kernel KERNCONF=YOUR_KERNEL_HERE
1028 <reboot in single user> [3]
1035 To cross-install current onto a separate partition
1036 --------------------------------------------------
1037 # In this approach we use a separate partition to hold
1038 # current's root, 'usr', and 'var' directories. A partition
1039 # holding "/", "/usr" and "/var" should be about 2GB in
1042 <make sure you have good level 0 dumps>
1045 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1046 <maybe newfs current's root partition>
1047 <mount current's root partition on directory ${CURRENT_ROOT}>
1048 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1049 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1050 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1051 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1052 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1053 <reboot into current>
1054 <do a "native" rebuild/install as described in the previous section>
1055 <maybe install compatibility libraries from ports/misc/compat*>
1059 To upgrade in-place from stable to current
1060 ----------------------------------------------
1061 <make sure you have good level 0 dumps>
1063 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1065 <reboot in single user> [3]
1072 Make sure that you've read the UPDATING file to understand the
1073 tweaks to various things you need. At this point in the life
1074 cycle of current, things change often and you are on your own
1075 to cope. The defaults can also change, so please read ALL of
1076 the UPDATING entries.
1078 Also, if you are tracking -current, you must be subscribed to
1079 freebsd-current@freebsd.org. Make sure that before you update
1080 your sources that you have read and understood all the recent
1081 messages there. If in doubt, please track -stable which has
1082 much fewer pitfalls.
1084 [1] If you have third party modules, such as vmware, you
1085 should disable them at this point so they don't crash your
1088 [3] From the bootblocks, boot -s, and then do
1093 adjkerntz -i # if CMOS is wall time
1094 Also, when doing a major release upgrade, it is required that
1095 you boot into single user mode to do the installworld.
1097 [4] Note: This step is non-optional. Failure to do this step
1098 can result in a significant reduction in the functionality of the
1099 system. Attempting to do it by hand is not recommended and those
1100 that pursue this avenue should read this file carefully, as well
1101 as the archives of freebsd-current and freebsd-hackers mailing lists
1102 for potential gotchas. The -U option is also useful to consider.
1103 See mergemaster(8) for more information.
1105 [5] Usually this step is a noop. However, from time to time
1106 you may need to do this if you get unknown user in the following
1107 step. It never hurts to do it all the time. You may need to
1108 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1109 install) after the buildworld before this step if you last updated
1110 from current before 20130425 or from -stable before 20130430.
1112 [6] This only deletes old files and directories. Old libraries
1113 can be deleted by "make delete-old-libs", but you have to make
1114 sure that no program is using those libraries anymore.
1116 [8] In order to have a kernel that can run the 4.x binaries needed to
1117 do an installworld, you must include the COMPAT_FREEBSD4 option in
1118 your kernel. Failure to do so may leave you with a system that is
1119 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1120 required to run the 5.x binaries on more recent kernels. And so on
1121 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1123 Make sure that you merge any new devices from GENERIC since the
1124 last time you updated your kernel config file.
1126 [9] When checking out sources, you must include the -P flag to have
1127 cvs prune empty directories.
1129 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1130 "?=" instead of the "=" assignment operator, so that buildworld can
1131 override the CPUTYPE if it needs to.
1133 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1134 not on the command line, or in /etc/make.conf. buildworld will
1135 warn if it is improperly defined.
1138 This file contains a list, in reverse chronological order, of major
1139 breakages in tracking -current. It is not guaranteed to be a complete
1140 list of such breakages, and only contains entries since October 10, 2007.
1141 If you need to see UPDATING entries from before that date, you will need
1142 to fetch an UPDATING file from an older FreeBSD release.
1144 Copyright information:
1146 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1148 Redistribution, publication, translation and use, with or without
1149 modification, in full or in part, in any form or format of this
1150 document are permitted without further permission from the author.
1152 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1153 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1154 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1155 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1156 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1157 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1158 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1159 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1160 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1161 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1162 POSSIBILITY OF SUCH DAMAGE.
1164 Contact Warner Losh if you have any questions about your use of