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