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