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 Commit r268115 has added NFSv4.1 server support, merged from
36 projects/nfsv4.1-server. Since this includes changes to the
37 internal interfaces between the NFS related modules, a full
38 build of the kernel and modules will be necessary.
39 __FreeBSD_version has been bumped.
42 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
43 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
44 which differs from the behaviour controlled by this knob.)
47 Maximal length of the serial number in CTL was increased from 16 to
48 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
49 and ctld, need to be rebuilt to work with a new kernel.
52 The libatf-c and libatf-c++ major versions were downgraded to 0 and
53 1 respectively to match the upstream numbers. They were out of
54 sync because, when they were originally added to FreeBSD, the
55 upstream versions were not respected. These libraries are private
56 and not yet built by default, so renumbering them should be a
57 non-issue. However, unclean source trees will yield broken test
58 programs once the operator executes "make delete-old-libs" after a
61 Additionally, the atf-sh binary was made private by moving it into
62 /usr/libexec/. Already-built shell test programs will keep the
63 path to the old binary so they will break after "make delete-old"
66 If you are using WITH_TESTS=yes (not the default), wipe the object
67 tree and rebuild from scratch to prevent spurious test failures.
68 This is only needed once: the misnumbered libraries and misplaced
69 binaries have been added to OptionalObsoleteFiles.inc so they will
70 be removed during a clean upgrade.
73 Clang and llvm have been upgraded to 3.4.1 release.
76 We bogusly installed src.opts.mk in /usr/share/mk. This file should
77 be removed to avoid issues in the future (and has been added to
81 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
82 past, it affected all builds that used the bsd.*.mk files. The old
83 behavior was a bug, but people may have relied upon it. To get this
84 behavior back, you can .include /etc/src.conf from /etc/make.conf
85 (which is still global and isn't changed). This also changes the
86 behavior of incremental builds inside the tree of individual
87 directories. Set MAKESYSPATH to ".../share/mk" to do that.
88 Although this has survived make universe and some upgrade scenarios,
89 other upgrade scenarios may have broken. At least one form of
90 temporary breakage was fixed with MAKESYSPATH settings for buildworld
91 as well... In cases where MAKESYSPATH isn't working with this
92 setting, you'll need to set it to the full path to your tree.
94 One side effect of all this cleaning up is that bsd.compiler.mk
95 is no longer implicitly included by bsd.own.mk. If you wish to
96 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
100 The lindev device has been removed since /dev/full has been made a
101 standard device. __FreeBSD_version has been bumped.
104 The YES_HESIOD knob has been removed. It has been obsolete for
105 a decade. Please move to using WITH_HESIOD instead or your builds
106 will silently lack HESIOD.
109 The uart(4) driver has been changed with respect to its handling
110 of the low-level console. Previously the uart(4) driver prevented
111 any process from changing the baudrate or the CLOCAL and HUPCL
112 control flags. By removing the restrictions, operators can make
113 changes to the serial console port without having to reboot.
114 However, when getty(8) is started on the serial device that is
115 associated with the low-level console, a misconfigured terminal
116 line in /etc/ttys will now have a real impact.
117 Before upgrading the kernel, make sure that /etc/ttys has the
118 serial console device configured as 3wire without baudrate to
119 preserve the previous behaviour. E.g:
120 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
123 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
124 to improve performance. To re-enable it, if needed, run rpcbind
125 with command line option -W.
128 Switched back to the GPL dtc compiler due to updates in the upstream
129 dts files not being supported by the BSDL dtc compiler. You will need
130 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
131 may result while building dtb files during a kernel build if you fail
132 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
135 Clang and llvm have been upgraded to 3.4 release.
138 The nve(4) driver has been removed. Please use the nfe(4) driver
139 for NVIDIA nForce MCP Ethernet adapters instead.
142 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
143 This could cause certain C++ applications using shared libraries built
144 against the previous version of libc++ to crash. The incompatibility
145 has now been fixed, but any C++ applications or shared libraries built
146 between r261283 and r261801 should be recompiled.
149 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
150 capability mode support. Please note that enabling the feature in
151 kernel is still highly recommended.
154 OpenSSH is now built with sandbox support, and will use sandbox as
155 the default privilege separation method. This requires Capsicum
156 capability mode support in kernel.
159 The libelf and libdwarf libraries have been updated to newer
160 versions from upstream. Shared library version numbers for
161 these two libraries were bumped. Any ports or binaries
162 requiring these two libraries should be recompiled.
163 __FreeBSD_version is bumped to 1100006.
166 If a Makefile in a tests/ directory was auto-generating a Kyuafile
167 instead of providing an explicit one, this would prevent such
168 Makefile from providing its own Kyuafile in the future during
169 NO_CLEAN builds. This has been fixed in the Makefiles but manual
170 intervention is needed to clean an objdir if you use NO_CLEAN:
171 # find /usr/obj -name Kyuafile | xargs rm -f
174 The behavior of gss_pseudo_random() for the krb5 mechanism
175 has changed, for applications requesting a longer random string
176 than produced by the underlying enctype's pseudo-random() function.
177 In particular, the random string produced from a session key of
178 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
179 be different at the 17th octet and later, after this change.
180 The counter used in the PRF+ construction is now encoded as a
181 big-endian integer in accordance with RFC 4402.
182 __FreeBSD_version is bumped to 1100004.
185 The WITHOUT_ATF build knob has been removed and its functionality
186 has been subsumed into the more generic WITHOUT_TESTS. If you were
187 using the former to disable the build of the ATF libraries, you
188 should change your settings to use the latter.
191 The default version of mtree is nmtree which is obtained from
192 NetBSD. The output is generally the same, but may vary
193 slightly. If you found you need identical output adding
194 "-F freebsd9" to the command line should do the trick. For the
195 time being, the old mtree is available as fmtree.
198 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
199 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
200 1.1.4_8 and verify bsdyml not linked in, before running "make
202 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
204 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
207 The rc.d/jail script has been updated to support jail(8)
208 configuration file. The "jail_<jname>_*" rc.conf(5) variables
209 for per-jail configuration are automatically converted to
210 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
211 This is transparently backward compatible. See below about some
212 incompatibilities and rc.conf(5) manual page for more details.
214 These variables are now deprecated in favor of jail(8) configuration
215 file. One can use "rc.d/jail config <jname>" command to generate
216 a jail(8) configuration file in /var/run/jail.<jname>.conf without
217 running the jail(8) utility. The default pathname of the
218 configuration file is /etc/jail.conf and can be specified by
219 using $jail_conf or $jail_<jname>_conf variables.
221 Please note that jail_devfs_ruleset accepts an integer at
222 this moment. Please consider to rewrite the ruleset name
226 BIND has been removed from the base system. If all you need
227 is a local resolver, simply enable and start the local_unbound
228 service instead. Otherwise, several versions of BIND are
229 available in the ports tree. The dns/bind99 port is one example.
231 With this change, nslookup(1) and dig(1) are no longer in the base
232 system. Users should instead use host(1) and drill(1) which are
233 in the base system. Alternatively, nslookup and dig can
234 be obtained by installing the dns/bind-tools port.
237 With the addition of unbound(8), a new unbound user is now
238 required during installworld. "mergemaster -p" can be used to
239 add the user prior to installworld, as documented in the handbook.
242 OpenSSH is now built with DNSSEC support, and will by default
243 silently trust signed SSHFP records. This can be controlled with
244 the VerifyHostKeyDNS client configuration setting. DNSSEC support
245 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
248 The GNU Compiler Collection and C++ standard library (libstdc++)
249 are no longer built by default on platforms where clang is the system
250 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
254 The PROCDESC kernel option is now part of the GENERIC kernel
255 configuration and is required for the rwhod(8) to work.
256 If you are using custom kernel configuration, you should include
260 The API and ABI related to the Capsicum framework was modified
261 in backward incompatible way. The userland libraries and programs
262 have to be recompiled to work with the new kernel. This includes the
263 following libraries and programs, but the whole buildworld is
264 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
265 kdump, procstat, rwho, rwhod, uniq.
268 AES-NI intrinsic support has been added to gcc. The AES-NI module
269 has been updated to use this support. A new gcc is required to build
270 the aesni module on both i386 and amd64.
273 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
274 Thus "device padlock_rng" and "device rdrand_rng" should be
275 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
278 WITH_ICONV has been split into two feature sets. WITH_ICONV now
279 enables just the iconv* functionality and is now on by default.
280 WITH_LIBICONV_COMPAT enables the libiconv api and link time
281 compatability. Set WITHOUT_ICONV to build the old way.
282 If you have been using WITH_ICONV before, you will very likely
283 need to turn on WITH_LIBICONV_COMPAT.
286 INVARIANTS option now enables DEBUG for code with OpenSolaris and
287 Illumos origin, including ZFS. If you have INVARIANTS in your
288 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
290 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
291 locks if WITNESS option was set. Because that generated a lot of
292 witness(9) reports and all of them were believed to be false
293 positives, this is no longer done. New option OPENSOLARIS_WITNESS
294 can be used to achieve the previous behavior.
297 Timer values in IPv6 data structures now use time_uptime instead
298 of time_second. Although this is not a user-visible functional
299 change, userland utilities which directly use them---ndp(8),
300 rtadvd(8), and rtsold(8) in the base system---need to be updated
304 find -delete can now delete the pathnames given as arguments,
305 instead of only files found below them or if the pathname did
306 not contain any slashes. Formerly, the following error message
309 find: -delete: <path>: relative path potentially not safe
311 Deleting the pathnames given as arguments can be prevented
312 without error messages using -mindepth 1 or by changing
313 directory and passing "." as argument to find. This works in the
314 old as well as the new version of find.
317 Behavior of devfs rules path matching has been changed.
318 Pattern is now always matched against fully qualified devfs
319 path and slash characters must be explicitly matched by
320 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
321 subdirectories must be reviewed.
324 The default ARM ABI has changed to the ARM EABI. The old ABI is
325 incompatible with the ARM EABI and all programs and modules will
326 need to be rebuilt to work with a new kernel.
328 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
330 NOTE: Support for the old ABI will be removed in the future and
331 users are advised to upgrade.
334 pkg_install has been disconnected from the build if you really need it
335 you should add WITH_PKGTOOLS in your src.conf(5).
338 Most of network statistics structures were changed to be able
339 keep 64-bits counters. Thus all tools, that work with networking
340 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
343 Fix targets that run multiple make's to use && rather than ;
344 so that subsequent steps depend on success of previous.
346 NOTE: if building 'universe' with -j* on stable/8 or stable/9
347 it would be better to start the build using bmake, to avoid
348 overloading the machine.
351 Fix a bug that allowed a tracing process (e.g. gdb) to write
352 to a memory-mapped file in the traced process's address space
353 even if neither the traced process nor the tracing process had
354 write access to that file.
357 CVS has been removed from the base system. An exact copy
358 of the code is available from the devel/cvs port.
361 Some people report the following error after the switch to bmake:
363 make: illegal option -- J
364 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
366 *** [buildworld] Error code 2
368 this likely due to an old instance of make in
369 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
370 which src/Makefile will use that blindly, if it exists, so if
371 you see the above error:
373 rm -rf `make -V MAKEPATH`
378 Use bmake by default.
379 Whereas before one could choose to build with bmake via
380 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
381 make. The goal is to remove these knobs for 10-RELEASE.
383 It is worth noting that bmake (like gmake) treats the command
384 line as the unit of failure, rather than statements within the
385 command line. Thus '(cd some/where && dosomething)' is safer
386 than 'cd some/where; dosomething'. The '()' allows consistent
387 behavior in parallel build.
390 Fix a bug that allows NFS clients to issue READDIR on files.
393 The WITHOUT_IDEA option has been removed because
394 the IDEA patent expired.
397 The sysctl which controls TRIM support under ZFS has been renamed
398 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
402 The mergemaster command now uses the default MAKEOBJDIRPREFIX
403 rather than creating it's own in the temporary directory in
404 order allow access to bootstrapped versions of tools such as
405 install and mtree. When upgrading from version of FreeBSD where
406 the install command does not support -l, you will need to
407 install a new mergemaster command if mergemaster -p is required.
408 This can be accomplished with the command (cd src/usr.sbin/mergemaster
412 Legacy ATA stack, disabled and replaced by new CAM-based one since
413 FreeBSD 9.0, completely removed from the sources. Kernel modules
414 atadisk and atapi*, user-level tools atacontrol and burncd are
415 removed. Kernel option `options ATA_CAM` is now permanently enabled
419 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
420 and socketpair(2). Software, in particular Kerberos, may
421 automatically detect and use these during building. The resulting
422 binaries will not work on older kernels.
425 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
426 information, see the respective 20130304 entry).
429 Recent commits to callout(9) changed the size of struct callout,
430 so the KBI is probably heavily disturbed. Also, some functions
431 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
432 by macros. Every kernel module using it won't load, so rebuild
435 The ctl device has been re-enabled in GENERIC for i386 and amd64,
436 but does not initialize by default (because of the new CTL_DISABLE
437 option) to save memory. To re-enable it, remove the CTL_DISABLE
438 option from the kernel config file or set kern.cam.ctl.disable=0
439 in /boot/loader.conf.
442 The ctl device has been disabled in GENERIC for i386 and amd64.
443 This was done due to the extra memory being allocated at system
444 initialisation time by the ctl driver which was only used if
445 a CAM target device was created. This makes a FreeBSD system
446 unusable on 128MB or less of RAM.
449 A new compression method (lz4) has been merged to -HEAD. Please
450 refer to zpool-features(7) for more information.
452 Please refer to the "ZFS notes" section of this file for information
453 on upgrading boot ZFS pools.
456 A BSD-licensed patch(1) variant has been added and is installed
457 as bsdpatch, being the GNU version the default patch.
458 To inverse the logic and use the BSD-licensed one as default,
459 while having the GNU version installed as gnupatch, rebuild
460 and install world with the WITH_BSD_PATCH knob set.
463 Due to the use of the new -l option to install(1) during build
464 and install, you must take care not to directly set the INSTALL
465 make variable in your /etc/make.conf, /etc/src.conf, or on the
466 command line. If you wish to use the -C flag for all installs
467 you may be able to add INSTALL+=-C to /etc/make.conf or
471 The install(1) option -M has changed meaning and now takes an
472 argument that is a file or path to append logs to. In the
473 unlikely event that -M was the last option on the command line
474 and the command line contained at least two files and a target
475 directory the first file will have logs appended to it. The -M
476 option served little practical purpose in the last decade so its
477 use is expected to be extremely rare.
480 After switching to Clang as the default compiler some users of ZFS
481 on i386 systems started to experience stack overflow kernel panics.
482 Please consider using 'options KSTACK_PAGES=4' in such configurations.
485 GEOM_LABEL now mangles label names read from file system metadata.
486 Mangling affect labels containing spaces, non-printable characters,
487 '%' or '"'. Device names in /etc/fstab and other places may need to
491 By default, only the 10 most recent kernel dumps will be saved. To
492 restore the previous behaviour (no limit on the number of kernel dumps
493 stored in the dump directory) add the following line to /etc/rc.conf:
498 With the addition of auditdistd(8), a new auditdistd user is now
499 required during installworld. "mergemaster -p" can be used to
500 add the user prior to installworld, as documented in the handbook.
503 The sin6_scope_id member variable in struct sockaddr_in6 is now
504 filled by the kernel before passing the structure to the userland via
505 sysctl or routing socket. This means the KAME-specific embedded scope
506 id in sin6_addr.s6_addr[2] is always cleared in userland application.
507 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
508 __FreeBSD_version is bumped to 1000025.
511 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
512 This means that the world and kernel will be compiled with clang
513 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
514 and /usr/bin/cpp. To disable this behavior and revert to building
515 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
516 of current may need to bootstrap WITHOUT_CLANG first if the clang
517 build fails (its compatibility window doesn't extend to the 9 stable
521 The IPFIREWALL_FORWARD kernel option has been removed. Its
522 functionality now turned on by default.
525 The ZERO_COPY_SOCKET kernel option has been removed and
526 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
527 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
528 mechanism which is not safe and may result in kernel crashes.
529 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
530 driver supports disposeable external page sized mbuf storage.
531 Proper replacements for both zero-copy mechanisms are under
532 consideration and will eventually lead to complete removal
533 of the two kernel options.
536 The IPv4 network stack has been converted to network byte
537 order. The following modules need to be recompiled together
538 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
539 pf(4), ipfw(4), ng_ipfw(4), stf(4).
542 Support for non-MPSAFE filesystems was removed from VFS. The
543 VFS_VERSION was bumped, all filesystem modules shall be
547 All the non-MPSAFE filesystems have been disconnected from
548 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
549 portalfs, smbfs, xfs.
552 The interface cloning API and ABI has changed. The following
553 modules need to be recompiled together with kernel:
554 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
555 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
556 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
559 The sdhci driver was split in two parts: sdhci (generic SD Host
560 Controller logic) and sdhci_pci (actual hardware driver).
561 No kernel config modifications are required, but if you
562 load sdhc as a module you must switch to sdhci_pci instead.
565 Import the FUSE kernel and userland support into base system.
568 The GNU sort(1) program has been removed since the BSD-licensed
569 sort(1) has been the default for quite some time and no serious
570 problems have been reported. The corresponding WITH_GNU_SORT
574 The pfil(9) API/ABI for AF_INET family has been changed. Packet
575 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
579 The net80211(4) ABI has been changed to allow for improved driver
580 PS-POLL and power-save support. All wireless drivers need to be
581 recompiled to work with the new kernel.
584 The random(4) support for the VIA hardware random number
585 generator (`PADLOCK') is no longer enabled unconditionally.
586 Add the padlock_rng device in the custom kernel config if
587 needed. The GENERIC kernels on i386 and amd64 do include the
588 device, so the change only affects the custom kernel
592 The pf(4) packet filter ABI has been changed. pfctl(8) and
593 snmp_pf module need to be recompiled to work with new kernel.
596 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
597 to -HEAD. Pools that have empty_bpobj in active state can not be
598 imported read-write with ZFS implementations that do not support
599 this feature. For more information read the zpool-features(5)
603 The sparc64 ZFS loader has been changed to no longer try to auto-
604 detect ZFS providers based on diskN aliases but now requires these
605 to be explicitly listed in the OFW boot-device environment variable.
608 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
609 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
610 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
613 The following sysctls and tunables have been renamed for consistency
614 with other variables:
615 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
616 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
619 The sort utility has been replaced with BSD sort. For now, GNU sort
620 is also available as "gnusort" or the default can be set back to
621 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
622 installed as "bsdsort".
625 A new version of ZFS (pool version 5000) has been merged to -HEAD.
626 Starting with this version the old system of ZFS pool versioning
627 is superseded by "feature flags". This concept enables forward
628 compatibility against certain future changes in functionality of ZFS
629 pools. The first read-only compatible "feature flag" for ZFS pools
630 is named "com.delphix:async_destroy". For more information
631 read the new zpool-features(5) manual page.
632 Please refer to the "ZFS notes" section of this file for information
633 on upgrading boot ZFS pools.
636 The malloc(3) implementation embedded in libc now uses sources imported
637 as contrib/jemalloc. The most disruptive API change is to
638 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
639 delete it prior to installworld, and optionally re-create it using the
640 new format after rebooting. See malloc.conf(5) for details
641 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
645 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
646 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
647 now spelled mips. This is to aid compatibility with third-party
648 software that expects this naming scheme in uname(3). Little-endian
649 settings are unchanged. If you are updating a big-endian mips64 machine
650 from before this change, you may need to set MACHINE_ARCH=mips64 in
651 your environment before the new build system will recognize your machine.
654 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
658 Now unix domain sockets behave "as expected" on nullfs(5). Previously
659 nullfs(5) did not pass through all behaviours to the underlying layer,
660 as a result if we bound to a socket on the lower layer we could connect
661 only to the lower path; if we bound to the upper layer we could connect
662 only to the upper path. The new behavior is one can connect to both the
663 lower and the upper paths regardless what layer path one binds to.
666 The getifaddrs upgrade path broken with 20111215 has been restored.
667 If you have upgraded in between 20111215 and 20120209 you need to
668 recompile libc again with your kernel. You still need to recompile
669 world to be able to configure CARP but this restriction already
673 The set_rcvar() function has been removed from /etc/rc.subr. All
674 base and ports rc.d scripts have been updated, so if you have a
675 port installed with a script in /usr/local/etc/rc.d you can either
676 hand-edit the rcvar= line, or reinstall the port.
678 An easy way to handle the mass-update of /etc/rc.d:
679 rm /etc/rc.d/* && mergemaster -i
682 panic(9) now stops other CPUs in the SMP systems, disables interrupts
683 on the current CPU and prevents other threads from running.
684 This behavior can be reverted using the kern.stop_scheduler_on_panic
686 The new behavior can be incompatible with kern.sync_on_panic.
689 The carp(4) facility has been changed significantly. Configuration
690 of the CARP protocol via ifconfig(8) has changed, as well as format
691 of CARP events submitted to devd(8) has changed. See manual pages
692 for more information. The arpbalance feature of carp(4) is currently
693 not supported anymore.
695 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
696 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
697 need to be recompiled.
700 The acpi_wmi(4) status device /dev/wmistat has been renamed to
704 The option VFS_ALLOW_NONMPSAFE option has been added in order to
705 explicitely support non-MPSAFE filesystems.
706 It is on by default for all supported platform at this present
710 The broken amd(4) driver has been replaced with esp(4) in the amd64,
711 i386 and pc98 GENERIC kernel configuration files.
714 sysinstall has been removed
717 The stable/9 branch created in subversion. This corresponds to the
718 RELENG_9 branch in CVS.
724 Avoid using make -j when upgrading. While generally safe, there are
725 sometimes problems using -j to upgrade. If your upgrade fails with
726 -j, please try again without -j. From time to time in the past there
727 have been problems using -j with buildworld and/or installworld. This
728 is especially true when upgrading between "distant" versions (eg one
729 that cross a major release boundary or several minor releases, or when
730 several months have passed on the -current branch).
732 Sometimes, obscure build problems are the result of environment
733 poisoning. This can happen because the make utility reads its
734 environment when searching for values for global variables. To run
735 your build attempts in an "environmental clean room", prefix all make
736 commands with 'env -i '. See the env(1) manual page for more details.
738 When upgrading from one major version to another it is generally best
739 to upgrade to the latest code in the currently installed branch first,
740 then do an upgrade to the new branch. This is the best-tested upgrade
741 path, and has the highest probability of being successful. Please try
742 this approach before reporting problems with a major version upgrade.
744 When upgrading a live system, having a root shell around before
745 installing anything can help undo problems. Not having a root shell
746 around can lead to problems if pam has changed too much from your
747 starting point to allow continued authentication after the upgrade.
751 When upgrading the boot ZFS pool to a new version, always follow
754 1.) recompile and reinstall the ZFS boot loader and boot block
755 (this is part of "make buildworld" and "make installworld")
757 2.) update the ZFS boot block on your boot drive
759 The following example updates the ZFS boot block on the first
760 partition (freebsd-boot) of a GPT partitioned drive ad0:
761 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
763 Non-boot pools do not need these updates.
767 If you are updating from a prior version of FreeBSD (even one just
768 a few days old), you should follow this procedure. It is the most
769 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
771 make kernel-toolchain
772 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
773 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
775 To test a kernel once
776 ---------------------
777 If you just want to boot a kernel once (because you are not sure
778 if it works, or if you want to boot a known bad kernel to provide
779 debugging information) run
780 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
781 nextboot -k testkernel
783 To just build a kernel when you know that it won't mess you up
784 --------------------------------------------------------------
785 This assumes you are already running a CURRENT system. Replace
786 ${arch} with the architecture of your machine (e.g. "i386",
787 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
789 cd src/sys/${arch}/conf
790 config KERNEL_NAME_HERE
791 cd ../compile/KERNEL_NAME_HERE
796 If this fails, go to the "To build a kernel" section.
798 To rebuild everything and install it on the current system.
799 -----------------------------------------------------------
800 # Note: sometimes if you are running current you gotta do more than
801 # is listed here if you are upgrading from a really old current.
803 <make sure you have good level 0 dumps>
805 make kernel KERNCONF=YOUR_KERNEL_HERE
807 <reboot in single user> [3]
814 To cross-install current onto a separate partition
815 --------------------------------------------------
816 # In this approach we use a separate partition to hold
817 # current's root, 'usr', and 'var' directories. A partition
818 # holding "/", "/usr" and "/var" should be about 2GB in
821 <make sure you have good level 0 dumps>
824 make buildkernel KERNCONF=YOUR_KERNEL_HERE
825 <maybe newfs current's root partition>
826 <mount current's root partition on directory ${CURRENT_ROOT}>
827 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
828 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
829 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
830 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
831 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
832 <reboot into current>
833 <do a "native" rebuild/install as described in the previous section>
834 <maybe install compatibility libraries from ports/misc/compat*>
838 To upgrade in-place from stable to current
839 ----------------------------------------------
840 <make sure you have good level 0 dumps>
842 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
844 <reboot in single user> [3]
851 Make sure that you've read the UPDATING file to understand the
852 tweaks to various things you need. At this point in the life
853 cycle of current, things change often and you are on your own
854 to cope. The defaults can also change, so please read ALL of
855 the UPDATING entries.
857 Also, if you are tracking -current, you must be subscribed to
858 freebsd-current@freebsd.org. Make sure that before you update
859 your sources that you have read and understood all the recent
860 messages there. If in doubt, please track -stable which has
863 [1] If you have third party modules, such as vmware, you
864 should disable them at this point so they don't crash your
867 [3] From the bootblocks, boot -s, and then do
872 adjkerntz -i # if CMOS is wall time
873 Also, when doing a major release upgrade, it is required that
874 you boot into single user mode to do the installworld.
876 [4] Note: This step is non-optional. Failure to do this step
877 can result in a significant reduction in the functionality of the
878 system. Attempting to do it by hand is not recommended and those
879 that pursue this avenue should read this file carefully, as well
880 as the archives of freebsd-current and freebsd-hackers mailing lists
881 for potential gotchas. The -U option is also useful to consider.
882 See mergemaster(8) for more information.
884 [5] Usually this step is a noop. However, from time to time
885 you may need to do this if you get unknown user in the following
886 step. It never hurts to do it all the time. You may need to
887 install a new mergemaster (cd src/usr.sbin/mergemaster && make
888 install) after the buildworld before this step if you last updated
889 from current before 20130425 or from -stable before 20130430.
891 [6] This only deletes old files and directories. Old libraries
892 can be deleted by "make delete-old-libs", but you have to make
893 sure that no program is using those libraries anymore.
895 [8] In order to have a kernel that can run the 4.x binaries needed to
896 do an installworld, you must include the COMPAT_FREEBSD4 option in
897 your kernel. Failure to do so may leave you with a system that is
898 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
899 required to run the 5.x binaries on more recent kernels. And so on
900 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
902 Make sure that you merge any new devices from GENERIC since the
903 last time you updated your kernel config file.
905 [9] When checking out sources, you must include the -P flag to have
906 cvs prune empty directories.
908 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
909 "?=" instead of the "=" assignment operator, so that buildworld can
910 override the CPUTYPE if it needs to.
912 MAKEOBJDIRPREFIX must be defined in an environment variable, and
913 not on the command line, or in /etc/make.conf. buildworld will
914 warn if it is improperly defined.
917 This file contains a list, in reverse chronological order, of major
918 breakages in tracking -current. It is not guaranteed to be a complete
919 list of such breakages, and only contains entries since October 10, 2007.
920 If you need to see UPDATING entries from before that date, you will need
921 to fetch an UPDATING file from an older FreeBSD release.
923 Copyright information:
925 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
927 Redistribution, publication, translation and use, with or without
928 modification, in full or in part, in any form or format of this
929 document are permitted without further permission from the author.
931 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
932 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
933 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
934 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
935 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
936 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
937 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
938 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
939 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
940 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
941 POSSIBILITY OF SUCH DAMAGE.
943 Contact Warner Losh if you have any questions about your use of