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