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