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