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