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