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