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