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
17 from 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 Add support for unicode collation strings leads to a change of
36 order of files listed by ls(1) for example. To get back to the old
37 behaviour, set LC_COLLATE environment variable to "C".
39 Databases administrators will need to reindex their databases given
40 collation results will be different.
43 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
44 libcrypto.so.7 or libssl.so.7 must be recompiled.
47 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
48 Kernel modules isp_2400_multi and isp_2500_multi were removed and
49 should be replaced with isp_2400 and isp_2500 modules respectively.
52 The build previously allowed using 'make -n' to not recurse into
53 sub-directories while showing what commands would be executed, and
54 'make -n -n' to recursively show commands. Now 'make -n' will recurse
55 and 'make -N' will not.
58 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
59 and etcupdate will now use this file. A custom sendmail.cf is now
60 updated via this mechanism rather than via installworld. If you had
61 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
62 want to remove the exclusion or change it to "always install".
63 /etc/mail/sendmail.cf is now managed the same way regardless of
64 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
65 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
68 Compatibility shims for legacy ATA device names have been removed.
69 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
70 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
71 environment variables, /dev/ad* and /dev/ar* symbolic links.
74 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
75 Please see the 20141231 entry below for information about prerequisites
76 and upgrading, if you are not already using clang 3.5.0 or higher.
79 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
80 and renamed from .symbols to .debug. This reduces the size requirements
81 on the boot partition or file system and provides consistency with
84 When using the supported kernel installation method the
85 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
86 as is done with /boot/kernel.
88 Developers wishing to maintain the historical behavior of installing
89 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
92 The wireless drivers had undergone changes that remove the 'parent
93 interface' from the ifconfig -l output. The rc.d network scripts
94 used to check presence of a parent interface in the list, so old
95 scripts would fail to start wireless networking. Thus, etcupdate(3)
96 or mergemaster(8) run is required after kernel update, to update your
100 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
101 These configurations are now automatically interpreted as
102 'scrub fragment reassemble'.
105 Kernel-loadable modules for the random(4) device are back. To use
106 them, the kernel must have
109 options RANDOM_LOADABLE
111 kldload(8) can then be used to load random_fortuna.ko
112 or random_yarrow.ko. Please note that due to the indirect
113 function calls that the loadable modules need to provide,
114 the build-in variants will be slightly more efficient.
116 The random(4) kernel option RANDOM_DUMMY has been retired due to
117 unpopularity. It was not all that useful anyway.
120 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
121 Control over building the ELF Tool Chain tools is now provided by
122 the WITHOUT_TOOLCHAIN knob.
125 The polarity of Pulse Per Second (PPS) capture events with the
126 uart(4) driver has been corrected. Prior to this change the PPS
127 "assert" event corresponded to the trailing edge of a positive PPS
128 pulse and the "clear" event was the leading edge of the next pulse.
130 As the width of a PPS pulse in a typical GPS receiver is on the
131 order of 1 millisecond, most users will not notice any significant
132 difference with this change.
134 Anyone who has compensated for the historical polarity reversal by
135 configuring a negative offset equal to the pulse width will need to
136 remove that workaround.
139 The default group assigned to /dev/dri entries has been changed
140 from 'wheel' to 'video' with the id of '44'. If you want to have
141 access to the dri devices please add yourself to the video group
144 # pw groupmod video -m $USER
147 The menu.rc and loader.rc files will now be replaced during
148 upgrades. Please migrate local changes to menu.rc.local and
149 loader.rc.local instead.
152 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
153 strings and strip have been removed. The src.conf(5) knob
154 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
157 As ZFS requires more kernel stack pages than is the default on some
158 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
159 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
161 Please consider using 'options KSTACK_PAGES=X' where X is greater
162 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
165 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
166 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
167 default, i.e., they will not contain "::". For example, instead
168 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
169 to have a more specific match, such as different map entries for
170 IPv6:0:0 vs IPv6:0. This change requires that configuration
171 data (including maps, files, classes, custom ruleset, etc.) must
172 use the same format, so make certain such configuration data is
173 upgrading. As a very simple check search for patterns like
174 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
175 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
176 the cf option UseCompressedIPv6Addresses.
179 The default kernel entropy-processing algorithm is now
180 Fortuna, replacing Yarrow.
182 Assuming you have 'device random' in your kernel config
183 file, the configurations allow a kernel option to override
184 this default. You may choose *ONE* of:
186 options RANDOM_YARROW # Legacy /dev/random algorithm.
187 options RANDOM_DUMMY # Blocking-only driver.
189 If you have neither, you get Fortuna. For most people,
190 read no further, Fortuna will give a /dev/random that works
191 like it always used to, and the difference will be irrelevant.
193 If you remove 'device random', you get *NO* kernel-processed
194 entopy at all. This may be acceptable to folks building
195 embedded systems, but has complications. Carry on reading,
196 and it is assumed you know what you need.
198 *PLEASE* read random(4) and random(9) if you are in the
199 habit of tweeking kernel configs, and/or if you are a member
200 of the embedded community, wanting specific and not-usual
201 behaviour from your security subsystems.
203 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
204 random', you will NOT have a functioning /dev/random, and
205 many cryptographic features will not work, including SSH.
206 You may also find strange behaviour from the random(3) set
207 of library functions, in particular sranddev(3), srandomdev(3)
208 and arc4random(3). The reason for this is that the KERN_ARND
209 sysctl only returns entropy if it thinks it has some to
210 share, and with RANDOM_DUMMY or no 'device random' this
214 An additional fix for the issue described in the 20150614 sendmail
215 entry below has been been committed in revision 284717.
218 FreeBSD's old make (fmake) has been removed from the system. It is
219 available as the devel/fmake port or via pkg install fmake.
222 The fix for the issue described in the 20150614 sendmail entry
223 below has been been committed in revision 284436. The work
224 around described in that entry is no longer needed unless the
225 default setting is overridden by a confDH_PARAMETERS configuration
226 setting of '5' or pointing to a 512 bit DH parameter file.
229 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
230 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
231 and devel/kyua to version 0.20+ and adjust any calling code to work
232 with Kyuafile and kyua.
235 The import of openssl to address the FreeBSD-SA-15:10.openssl
236 security advisory includes a change which rejects handshakes
237 with DH parameters below 768 bits. sendmail releases prior
238 to 8.15.2 (not yet released), defaulted to a 512 bit
239 DH parameter setting for client connections. To work around
240 this interoperability, sendmail can be configured to use a
241 2048 bit DH parameter by:
243 1. Edit /etc/mail/`hostname`.mc
244 2. If a setting for confDH_PARAMETERS does not exist or
245 exists and is set to a string beginning with '5',
247 3. If a setting for confDH_PARAMETERS exists and is set to
248 a file path, create a new file with:
249 openssl dhparam -out /path/to/file 2048
250 4. Rebuild the .cf file:
251 cd /etc/mail/; make; make install
253 cd /etc/mail/; make restart
255 A sendmail patch is coming, at which time this file will be
259 Generation of legacy formatted entries have been disabled by default
260 in pwd_mkdb(8), as all base system consumers of the legacy formatted
261 entries were converted to use the new format by default when the new,
262 machine independent format have been added and supported since FreeBSD
265 Please see the pwd_mkdb(8) manual page for further details.
268 Clang and llvm have been upgraded to 3.6.1 release. Please see the
269 20141231 entry below for information about prerequisites and upgrading,
270 if you are not already using 3.5.0 or higher.
273 TI platform code switched to using vendor DTS files and this update
274 may break existing systems running on Beaglebone, Beaglebone Black,
277 - dtb files should be regenerated/reinstalled. Filenames are the
278 same but content is different now
279 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
280 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
281 addressing scheme is now pin 25 on /dev/gpioc3.
282 - Pandaboard: /etc/ttys should be updated, serial console device is
283 now /dev/ttyu2, not /dev/ttyu0
286 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
287 If you need the GNU extension from groff soelim(1), install groff
288 from package: pkg install groff, or via ports: textproc/groff.
291 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
292 defined in symlink(7); previously symlinks were silently ignored.
295 The const qualifier has been removed from iconv(3) to comply with
296 POSIX. The ports tree is aware of this from r384038 onwards.
299 Libraries specified by LIBADD in Makefiles must have a corresponding
300 DPADD_<lib> variable to ensure correct dependencies. This is now
301 enforced in src.libnames.mk.
304 From legacy ata(4) driver was removed support for SATA controllers
305 supported by more functional drivers ahci(4), siis(4) and mvs(4).
306 Kernel modules ataahci and ataadaptec were removed completely,
307 replaced by ahci and mvs modules respectively.
310 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
311 the 20141231 entry below for information about prerequisites and
312 upgrading, if you are not already using 3.5.0 or higher.
315 The 32-bit PowerPC kernel has been changed to a position-independent
316 executable. This can only be booted with a version of loader(8)
317 newer than January 31, 2015, so make sure to update both world and
318 kernel before rebooting.
321 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
322 but before r278950, the RNG was not seeded properly. Immediately
323 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
324 ssh keys or openssl keys) that were generated w/ a kernel from that
325 range. This does not affect programs that directly used /dev/random
326 or /dev/urandom. All userland uses of arc4random(3) are affected.
329 The autofs(4) ABI was changed in order to restore binary compatibility
330 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
334 The powerpc64 kernel has been changed to a position-independent
335 executable. This can only be booted with a new version of loader(8),
336 so make sure to update both world and kernel before rebooting.
339 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
340 only release, no new features have been added. Please see the 20141231
341 entry below for information about prerequisites and upgrading, if you
342 are not already using 3.5.0.
345 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
346 taken from the ELF Tool Chain project rather than GNU binutils. They
347 should be drop-in replacements, with the addition of arm64 support.
348 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
349 binutils tools, if necessary. See 20150805 for updated information.
352 The default Unbound configuration now enables remote control
353 using a local socket. Users who have already enabled the
354 local_unbound service should regenerate their configuration
355 by running "service local_unbound setup" as root.
358 The GNU texinfo and GNU info pages have been removed.
359 To be able to view GNU info pages please install texinfo from ports.
362 Clang, llvm and lldb have been upgraded to 3.5.0 release.
364 As of this release, a prerequisite for building clang, llvm and lldb is
365 a C++11 capable compiler and C++11 standard library. This means that to
366 be able to successfully build the cross-tools stage of buildworld, with
367 clang as the bootstrap compiler, your system compiler or cross compiler
368 should either be clang 3.3 or later, or gcc 4.8 or later, and your
369 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
372 On any standard FreeBSD 10.x or 11.x installation, where clang and
373 libc++ are on by default (that is, on x86 or arm), this should work out
376 On 9.x installations where clang is enabled by default, e.g. on x86 and
377 powerpc, libc++ will not be enabled by default, so libc++ should be
378 built (with clang) and installed first. If both clang and libc++ are
379 missing, build clang first, then use it to build libc++.
381 On 8.x and earlier installations, upgrade to 9.x first, and then follow
382 the instructions for 9.x above.
384 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
385 default, and do not build clang.
387 Many embedded systems are resource constrained, and will not be able to
388 build clang in a reasonable time, or in some cases at all. In those
389 cases, cross building bootable systems on amd64 is a workaround.
391 This new version of clang introduces a number of new warnings, of which
392 the following are most likely to appear:
396 This warns in two cases, for both C and C++:
397 * When the code is trying to take the absolute value of an unsigned
398 quantity, which is effectively a no-op, and almost never what was
399 intended. The code should be fixed, if at all possible. If you are
400 sure that the unsigned quantity can be safely cast to signed, without
401 loss of information or undefined behavior, you can add an explicit
402 cast, or disable the warning.
404 * When the code is trying to take an absolute value, but the called
405 abs() variant is for the wrong type, which can lead to truncation.
406 If you want to disable the warning instead of fixing the code, please
407 make sure that truncation will not occur, or it might lead to unwanted
410 -Wtautological-undefined-compare and
411 -Wundefined-bool-conversion
413 These warn when C++ code is trying to compare 'this' against NULL, while
414 'this' should never be NULL in well-defined C++ code. However, there is
415 some legacy (pre C++11) code out there, which actively abuses this
416 feature, which was less strictly defined in previous C++ versions.
418 Squid and openjdk do this, for example. The warning can be turned off
419 for C++98 and earlier, but compiling the code in C++11 mode might result
420 in unexpected behavior; for example, the parts of the program that are
421 unreachable could be optimized away.
424 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
425 kernel sources have been removed. The .h files remain, since some
426 utilities include them. This will need to be fixed later.
427 If "mount -t oldnfs ..." is attempted, it will fail.
428 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
429 the utilities will report errors.
432 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
433 directories to top level SUBDIR variable when their parent
434 directory is included in LOCAL_DIRS. Users with build systems with
435 such hierarchies and without SUBDIR entries in the parent
436 directory Makefiles should add them or add the directories to
440 faith(4) and faithd(8) have been removed from the base system. Faith
441 has been obsolete for a very long time.
444 vt(4), the new console driver, is enabled by default. It brings
445 support for Unicode and double-width characters, as well as
446 support for UEFI and integration with the KMS kernel video
449 You may need to update your console settings in /etc/rc.conf,
450 most probably the keymap. During boot, /etc/rc.d/syscons will
451 indicate what you need to do.
453 vt(4) still has issues and lacks some features compared to
454 syscons(4). See the wiki for up-to-date information:
455 https://wiki.freebsd.org/Newcons
457 If you want to keep using syscons(4), you can do so by adding
458 the following line to /boot/loader.conf:
462 pjdfstest has been integrated into kyua as an opt-in test suite.
463 Please see share/doc/pjdfstest/README for more details on how to
467 gperf has been removed from the base system for architectures
468 that use clang. Ports that require gperf will obtain it from the
472 pjdfstest has been moved from tools/regression/pjdfstest to
476 At svn r271982, The default linux compat kernel ABI has been adjusted
477 to 2.6.18 in support of the linux-c6 compat ports infrastructure
478 update. If you wish to continue using the linux-f10 compat ports,
479 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
480 encouraged to update their linux-compat packages to linux-c6 during
481 their next update cycle.
484 The ofwfb driver, used to provide a graphics console on PowerPC when
485 using vt(4), no longer allows mmap() of all physical memory. This
486 will prevent Xorg on PowerPC with some ATI graphics cards from
487 initializing properly unless x11-servers/xorg-server is updated to
491 The xdev targets have been converted to using TARGET and
492 TARGET_ARCH instead of XDEV and XDEV_ARCH.
495 The default unbound configuration has been modified to address
496 issues with reverse lookups on networks that use private
497 address ranges. If you use the local_unbound service, run
498 "service local_unbound setup" as root to regenerate your
499 configuration, then "service local_unbound reload" to load the
503 The GNU texinfo and GNU info pages are not built and installed
504 anymore, WITH_INFO knob has been added to allow to built and install
506 UPDATE: see 20150102 entry on texinfo's removal
509 The GNU readline library is now an INTERNALLIB - that is, it is
510 statically linked into consumers (GDB and variants) in the base
511 system, and the shared library is no longer installed. The
512 devel/readline port is available for third party software that
516 The Itanium architecture (ia64) has been removed from the list of
517 known architectures. This is the first step in the removal of the
521 Commit r268115 has added NFSv4.1 server support, merged from
522 projects/nfsv4.1-server. Since this includes changes to the
523 internal interfaces between the NFS related modules, a full
524 build of the kernel and modules will be necessary.
525 __FreeBSD_version has been bumped.
528 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
529 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
530 which differs from the behaviour controlled by this knob.)
533 Maximal length of the serial number in CTL was increased from 16 to
534 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
535 and ctld, need to be rebuilt to work with a new kernel.
538 The libatf-c and libatf-c++ major versions were downgraded to 0 and
539 1 respectively to match the upstream numbers. They were out of
540 sync because, when they were originally added to FreeBSD, the
541 upstream versions were not respected. These libraries are private
542 and not yet built by default, so renumbering them should be a
543 non-issue. However, unclean source trees will yield broken test
544 programs once the operator executes "make delete-old-libs" after a
547 Additionally, the atf-sh binary was made private by moving it into
548 /usr/libexec/. Already-built shell test programs will keep the
549 path to the old binary so they will break after "make delete-old"
552 If you are using WITH_TESTS=yes (not the default), wipe the object
553 tree and rebuild from scratch to prevent spurious test failures.
554 This is only needed once: the misnumbered libraries and misplaced
555 binaries have been added to OptionalObsoleteFiles.inc so they will
556 be removed during a clean upgrade.
559 Clang and llvm have been upgraded to 3.4.1 release.
562 We bogusly installed src.opts.mk in /usr/share/mk. This file should
563 be removed to avoid issues in the future (and has been added to
567 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
568 past, it affected all builds that used the bsd.*.mk files. The old
569 behavior was a bug, but people may have relied upon it. To get this
570 behavior back, you can .include /etc/src.conf from /etc/make.conf
571 (which is still global and isn't changed). This also changes the
572 behavior of incremental builds inside the tree of individual
573 directories. Set MAKESYSPATH to ".../share/mk" to do that.
574 Although this has survived make universe and some upgrade scenarios,
575 other upgrade scenarios may have broken. At least one form of
576 temporary breakage was fixed with MAKESYSPATH settings for buildworld
577 as well... In cases where MAKESYSPATH isn't working with this
578 setting, you'll need to set it to the full path to your tree.
580 One side effect of all this cleaning up is that bsd.compiler.mk
581 is no longer implicitly included by bsd.own.mk. If you wish to
582 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
586 The lindev device has been removed since /dev/full has been made a
587 standard device. __FreeBSD_version has been bumped.
590 The knob WITHOUT_VI was added to the base system, which controls
591 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
592 in order to reorder files share/termcap and didn't build ex(1) as a
593 build tool, so building/installing with WITH_VI is highly advised for
594 build hosts for older releases.
596 This issue has been fixed in stable/9 and stable/10 in r277022 and
597 r276991, respectively.
600 The YES_HESIOD knob has been removed. It has been obsolete for
601 a decade. Please move to using WITH_HESIOD instead or your builds
602 will silently lack HESIOD.
605 The uart(4) driver has been changed with respect to its handling
606 of the low-level console. Previously the uart(4) driver prevented
607 any process from changing the baudrate or the CLOCAL and HUPCL
608 control flags. By removing the restrictions, operators can make
609 changes to the serial console port without having to reboot.
610 However, when getty(8) is started on the serial device that is
611 associated with the low-level console, a misconfigured terminal
612 line in /etc/ttys will now have a real impact.
613 Before upgrading the kernel, make sure that /etc/ttys has the
614 serial console device configured as 3wire without baudrate to
615 preserve the previous behaviour. E.g:
616 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
619 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
620 to improve performance. To re-enable it, if needed, run rpcbind
621 with command line option -W.
624 Switched back to the GPL dtc compiler due to updates in the upstream
625 dts files not being supported by the BSDL dtc compiler. You will need
626 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
627 may result while building dtb files during a kernel build if you fail
628 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
631 Clang and llvm have been upgraded to 3.4 release.
634 The nve(4) driver has been removed. Please use the nfe(4) driver
635 for NVIDIA nForce MCP Ethernet adapters instead.
638 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
639 This could cause certain C++ applications using shared libraries built
640 against the previous version of libc++ to crash. The incompatibility
641 has now been fixed, but any C++ applications or shared libraries built
642 between r261283 and r261801 should be recompiled.
645 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
646 capability mode support. Please note that enabling the feature in
647 kernel is still highly recommended.
650 OpenSSH is now built with sandbox support, and will use sandbox as
651 the default privilege separation method. This requires Capsicum
652 capability mode support in kernel.
655 The libelf and libdwarf libraries have been updated to newer
656 versions from upstream. Shared library version numbers for
657 these two libraries were bumped. Any ports or binaries
658 requiring these two libraries should be recompiled.
659 __FreeBSD_version is bumped to 1100006.
662 If a Makefile in a tests/ directory was auto-generating a Kyuafile
663 instead of providing an explicit one, this would prevent such
664 Makefile from providing its own Kyuafile in the future during
665 NO_CLEAN builds. This has been fixed in the Makefiles but manual
666 intervention is needed to clean an objdir if you use NO_CLEAN:
667 # find /usr/obj -name Kyuafile | xargs rm -f
670 The behavior of gss_pseudo_random() for the krb5 mechanism
671 has changed, for applications requesting a longer random string
672 than produced by the underlying enctype's pseudo-random() function.
673 In particular, the random string produced from a session key of
674 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
675 be different at the 17th octet and later, after this change.
676 The counter used in the PRF+ construction is now encoded as a
677 big-endian integer in accordance with RFC 4402.
678 __FreeBSD_version is bumped to 1100004.
681 The WITHOUT_ATF build knob has been removed and its functionality
682 has been subsumed into the more generic WITHOUT_TESTS. If you were
683 using the former to disable the build of the ATF libraries, you
684 should change your settings to use the latter.
687 The default version of mtree is nmtree which is obtained from
688 NetBSD. The output is generally the same, but may vary
689 slightly. If you found you need identical output adding
690 "-F freebsd9" to the command line should do the trick. For the
691 time being, the old mtree is available as fmtree.
694 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
695 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
696 1.1.4_8 and verify bsdyml not linked in, before running "make
698 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
700 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
703 The stable/10 branch has been created in subversion from head
707 The rc.d/jail script has been updated to support jail(8)
708 configuration file. The "jail_<jname>_*" rc.conf(5) variables
709 for per-jail configuration are automatically converted to
710 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
711 This is transparently backward compatible. See below about some
712 incompatibilities and rc.conf(5) manual page for more details.
714 These variables are now deprecated in favor of jail(8) configuration
715 file. One can use "rc.d/jail config <jname>" command to generate
716 a jail(8) configuration file in /var/run/jail.<jname>.conf without
717 running the jail(8) utility. The default pathname of the
718 configuration file is /etc/jail.conf and can be specified by
719 using $jail_conf or $jail_<jname>_conf variables.
721 Please note that jail_devfs_ruleset accepts an integer at
722 this moment. Please consider to rewrite the ruleset name
726 BIND has been removed from the base system. If all you need
727 is a local resolver, simply enable and start the local_unbound
728 service instead. Otherwise, several versions of BIND are
729 available in the ports tree. The dns/bind99 port is one example.
731 With this change, nslookup(1) and dig(1) are no longer in the base
732 system. Users should instead use host(1) and drill(1) which are
733 in the base system. Alternatively, nslookup and dig can
734 be obtained by installing the dns/bind-tools port.
737 With the addition of unbound(8), a new unbound user is now
738 required during installworld. "mergemaster -p" can be used to
739 add the user prior to installworld, as documented in the handbook.
742 OpenSSH is now built with DNSSEC support, and will by default
743 silently trust signed SSHFP records. This can be controlled with
744 the VerifyHostKeyDNS client configuration setting. DNSSEC support
745 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
748 The GNU Compiler Collection and C++ standard library (libstdc++)
749 are no longer built by default on platforms where clang is the system
750 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
754 The PROCDESC kernel option is now part of the GENERIC kernel
755 configuration and is required for the rwhod(8) to work.
756 If you are using custom kernel configuration, you should include
760 The API and ABI related to the Capsicum framework was modified
761 in backward incompatible way. The userland libraries and programs
762 have to be recompiled to work with the new kernel. This includes the
763 following libraries and programs, but the whole buildworld is
764 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
765 kdump, procstat, rwho, rwhod, uniq.
768 AES-NI intrinsic support has been added to gcc. The AES-NI module
769 has been updated to use this support. A new gcc is required to build
770 the aesni module on both i386 and amd64.
773 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
774 Thus "device padlock_rng" and "device rdrand_rng" should be
775 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
778 WITH_ICONV has been split into two feature sets. WITH_ICONV now
779 enables just the iconv* functionality and is now on by default.
780 WITH_LIBICONV_COMPAT enables the libiconv api and link time
781 compatability. Set WITHOUT_ICONV to build the old way.
782 If you have been using WITH_ICONV before, you will very likely
783 need to turn on WITH_LIBICONV_COMPAT.
786 INVARIANTS option now enables DEBUG for code with OpenSolaris and
787 Illumos origin, including ZFS. If you have INVARIANTS in your
788 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
790 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
791 locks if WITNESS option was set. Because that generated a lot of
792 witness(9) reports and all of them were believed to be false
793 positives, this is no longer done. New option OPENSOLARIS_WITNESS
794 can be used to achieve the previous behavior.
797 Timer values in IPv6 data structures now use time_uptime instead
798 of time_second. Although this is not a user-visible functional
799 change, userland utilities which directly use them---ndp(8),
800 rtadvd(8), and rtsold(8) in the base system---need to be updated
804 find -delete can now delete the pathnames given as arguments,
805 instead of only files found below them or if the pathname did
806 not contain any slashes. Formerly, the following error message
809 find: -delete: <path>: relative path potentially not safe
811 Deleting the pathnames given as arguments can be prevented
812 without error messages using -mindepth 1 or by changing
813 directory and passing "." as argument to find. This works in the
814 old as well as the new version of find.
817 Behavior of devfs rules path matching has been changed.
818 Pattern is now always matched against fully qualified devfs
819 path and slash characters must be explicitly matched by
820 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
821 subdirectories must be reviewed.
824 The default ARM ABI has changed to the ARM EABI. The old ABI is
825 incompatible with the ARM EABI and all programs and modules will
826 need to be rebuilt to work with a new kernel.
828 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
830 NOTE: Support for the old ABI will be removed in the future and
831 users are advised to upgrade.
834 pkg_install has been disconnected from the build if you really need it
835 you should add WITH_PKGTOOLS in your src.conf(5).
838 Most of network statistics structures were changed to be able
839 keep 64-bits counters. Thus all tools, that work with networking
840 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
843 Fix targets that run multiple make's to use && rather than ;
844 so that subsequent steps depend on success of previous.
846 NOTE: if building 'universe' with -j* on stable/8 or stable/9
847 it would be better to start the build using bmake, to avoid
848 overloading the machine.
851 Fix a bug that allowed a tracing process (e.g. gdb) to write
852 to a memory-mapped file in the traced process's address space
853 even if neither the traced process nor the tracing process had
854 write access to that file.
857 CVS has been removed from the base system. An exact copy
858 of the code is available from the devel/cvs port.
861 Some people report the following error after the switch to bmake:
863 make: illegal option -- J
864 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
866 *** [buildworld] Error code 2
868 this likely due to an old instance of make in
869 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
870 which src/Makefile will use that blindly, if it exists, so if
871 you see the above error:
873 rm -rf `make -V MAKEPATH`
878 Use bmake by default.
879 Whereas before one could choose to build with bmake via
880 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
881 make. The goal is to remove these knobs for 10-RELEASE.
883 It is worth noting that bmake (like gmake) treats the command
884 line as the unit of failure, rather than statements within the
885 command line. Thus '(cd some/where && dosomething)' is safer
886 than 'cd some/where; dosomething'. The '()' allows consistent
887 behavior in parallel build.
890 Fix a bug that allows NFS clients to issue READDIR on files.
893 The WITHOUT_IDEA option has been removed because
894 the IDEA patent expired.
897 The sysctl which controls TRIM support under ZFS has been renamed
898 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
902 The mergemaster command now uses the default MAKEOBJDIRPREFIX
903 rather than creating it's own in the temporary directory in
904 order allow access to bootstrapped versions of tools such as
905 install and mtree. When upgrading from version of FreeBSD where
906 the install command does not support -l, you will need to
907 install a new mergemaster command if mergemaster -p is required.
908 This can be accomplished with the command (cd src/usr.sbin/mergemaster
912 Legacy ATA stack, disabled and replaced by new CAM-based one since
913 FreeBSD 9.0, completely removed from the sources. Kernel modules
914 atadisk and atapi*, user-level tools atacontrol and burncd are
915 removed. Kernel option `options ATA_CAM` is now permanently enabled
919 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
920 and socketpair(2). Software, in particular Kerberos, may
921 automatically detect and use these during building. The resulting
922 binaries will not work on older kernels.
925 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
926 information, see the respective 20130304 entry).
929 Recent commits to callout(9) changed the size of struct callout,
930 so the KBI is probably heavily disturbed. Also, some functions
931 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
932 by macros. Every kernel module using it won't load, so rebuild
935 The ctl device has been re-enabled in GENERIC for i386 and amd64,
936 but does not initialize by default (because of the new CTL_DISABLE
937 option) to save memory. To re-enable it, remove the CTL_DISABLE
938 option from the kernel config file or set kern.cam.ctl.disable=0
939 in /boot/loader.conf.
942 The ctl device has been disabled in GENERIC for i386 and amd64.
943 This was done due to the extra memory being allocated at system
944 initialisation time by the ctl driver which was only used if
945 a CAM target device was created. This makes a FreeBSD system
946 unusable on 128MB or less of RAM.
949 A new compression method (lz4) has been merged to -HEAD. Please
950 refer to zpool-features(7) for more information.
952 Please refer to the "ZFS notes" section of this file for information
953 on upgrading boot ZFS pools.
956 A BSD-licensed patch(1) variant has been added and is installed
957 as bsdpatch, being the GNU version the default patch.
958 To inverse the logic and use the BSD-licensed one as default,
959 while having the GNU version installed as gnupatch, rebuild
960 and install world with the WITH_BSD_PATCH knob set.
963 Due to the use of the new -l option to install(1) during build
964 and install, you must take care not to directly set the INSTALL
965 make variable in your /etc/make.conf, /etc/src.conf, or on the
966 command line. If you wish to use the -C flag for all installs
967 you may be able to add INSTALL+=-C to /etc/make.conf or
971 The install(1) option -M has changed meaning and now takes an
972 argument that is a file or path to append logs to. In the
973 unlikely event that -M was the last option on the command line
974 and the command line contained at least two files and a target
975 directory the first file will have logs appended to it. The -M
976 option served little practical purpose in the last decade so its
977 use is expected to be extremely rare.
980 After switching to Clang as the default compiler some users of ZFS
981 on i386 systems started to experience stack overflow kernel panics.
982 Please consider using 'options KSTACK_PAGES=4' in such configurations.
985 GEOM_LABEL now mangles label names read from file system metadata.
986 Mangling affect labels containing spaces, non-printable characters,
987 '%' or '"'. Device names in /etc/fstab and other places may need to
991 By default, only the 10 most recent kernel dumps will be saved. To
992 restore the previous behaviour (no limit on the number of kernel dumps
993 stored in the dump directory) add the following line to /etc/rc.conf:
998 With the addition of auditdistd(8), a new auditdistd user is now
999 required during installworld. "mergemaster -p" can be used to
1000 add the user prior to installworld, as documented in the handbook.
1003 The sin6_scope_id member variable in struct sockaddr_in6 is now
1004 filled by the kernel before passing the structure to the userland via
1005 sysctl or routing socket. This means the KAME-specific embedded scope
1006 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1007 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1008 __FreeBSD_version is bumped to 1000025.
1011 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1012 This means that the world and kernel will be compiled with clang
1013 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1014 and /usr/bin/cpp. To disable this behavior and revert to building
1015 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1016 of current may need to bootstrap WITHOUT_CLANG first if the clang
1017 build fails (its compatibility window doesn't extend to the 9 stable
1021 The IPFIREWALL_FORWARD kernel option has been removed. Its
1022 functionality now turned on by default.
1025 The ZERO_COPY_SOCKET kernel option has been removed and
1026 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1027 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1028 mechanism which is not safe and may result in kernel crashes.
1029 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1030 driver supports disposeable external page sized mbuf storage.
1031 Proper replacements for both zero-copy mechanisms are under
1032 consideration and will eventually lead to complete removal
1033 of the two kernel options.
1036 The IPv4 network stack has been converted to network byte
1037 order. The following modules need to be recompiled together
1038 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1039 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1042 Support for non-MPSAFE filesystems was removed from VFS. The
1043 VFS_VERSION was bumped, all filesystem modules shall be
1047 All the non-MPSAFE filesystems have been disconnected from
1048 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1049 portalfs, smbfs, xfs.
1052 The interface cloning API and ABI has changed. The following
1053 modules need to be recompiled together with kernel:
1054 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1055 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1056 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1059 The sdhci driver was split in two parts: sdhci (generic SD Host
1060 Controller logic) and sdhci_pci (actual hardware driver).
1061 No kernel config modifications are required, but if you
1062 load sdhc as a module you must switch to sdhci_pci instead.
1065 Import the FUSE kernel and userland support into base system.
1068 The GNU sort(1) program has been removed since the BSD-licensed
1069 sort(1) has been the default for quite some time and no serious
1070 problems have been reported. The corresponding WITH_GNU_SORT
1074 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1075 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1079 The net80211(4) ABI has been changed to allow for improved driver
1080 PS-POLL and power-save support. All wireless drivers need to be
1081 recompiled to work with the new kernel.
1084 The random(4) support for the VIA hardware random number
1085 generator (`PADLOCK') is no longer enabled unconditionally.
1086 Add the padlock_rng device in the custom kernel config if
1087 needed. The GENERIC kernels on i386 and amd64 do include the
1088 device, so the change only affects the custom kernel
1092 The pf(4) packet filter ABI has been changed. pfctl(8) and
1093 snmp_pf module need to be recompiled to work with new kernel.
1096 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1097 to -HEAD. Pools that have empty_bpobj in active state can not be
1098 imported read-write with ZFS implementations that do not support
1099 this feature. For more information read the zpool-features(5)
1103 The sparc64 ZFS loader has been changed to no longer try to auto-
1104 detect ZFS providers based on diskN aliases but now requires these
1105 to be explicitly listed in the OFW boot-device environment variable.
1108 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1109 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1110 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1113 The following sysctls and tunables have been renamed for consistency
1114 with other variables:
1115 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1116 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1119 The sort utility has been replaced with BSD sort. For now, GNU sort
1120 is also available as "gnusort" or the default can be set back to
1121 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1122 installed as "bsdsort".
1125 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1126 Starting with this version the old system of ZFS pool versioning
1127 is superseded by "feature flags". This concept enables forward
1128 compatibility against certain future changes in functionality of ZFS
1129 pools. The first read-only compatible "feature flag" for ZFS pools
1130 is named "com.delphix:async_destroy". For more information
1131 read the new zpool-features(5) manual page.
1132 Please refer to the "ZFS notes" section of this file for information
1133 on upgrading boot ZFS pools.
1136 The malloc(3) implementation embedded in libc now uses sources imported
1137 as contrib/jemalloc. The most disruptive API change is to
1138 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1139 delete it prior to installworld, and optionally re-create it using the
1140 new format after rebooting. See malloc.conf(5) for details
1141 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1145 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1146 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1147 now spelled mips. This is to aid compatibility with third-party
1148 software that expects this naming scheme in uname(3). Little-endian
1149 settings are unchanged. If you are updating a big-endian mips64 machine
1150 from before this change, you may need to set MACHINE_ARCH=mips64 in
1151 your environment before the new build system will recognize your machine.
1154 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1158 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1159 nullfs(5) did not pass through all behaviours to the underlying layer,
1160 as a result if we bound to a socket on the lower layer we could connect
1161 only to the lower path; if we bound to the upper layer we could connect
1162 only to the upper path. The new behavior is one can connect to both the
1163 lower and the upper paths regardless what layer path one binds to.
1166 The getifaddrs upgrade path broken with 20111215 has been restored.
1167 If you have upgraded in between 20111215 and 20120209 you need to
1168 recompile libc again with your kernel. You still need to recompile
1169 world to be able to configure CARP but this restriction already
1170 comes from 20111215.
1173 The set_rcvar() function has been removed from /etc/rc.subr. All
1174 base and ports rc.d scripts have been updated, so if you have a
1175 port installed with a script in /usr/local/etc/rc.d you can either
1176 hand-edit the rcvar= line, or reinstall the port.
1178 An easy way to handle the mass-update of /etc/rc.d:
1179 rm /etc/rc.d/* && mergemaster -i
1182 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1183 on the current CPU and prevents other threads from running.
1184 This behavior can be reverted using the kern.stop_scheduler_on_panic
1186 The new behavior can be incompatible with kern.sync_on_panic.
1189 The carp(4) facility has been changed significantly. Configuration
1190 of the CARP protocol via ifconfig(8) has changed, as well as format
1191 of CARP events submitted to devd(8) has changed. See manual pages
1192 for more information. The arpbalance feature of carp(4) is currently
1193 not supported anymore.
1195 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1196 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1197 need to be recompiled.
1200 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1204 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1205 explicitely support non-MPSAFE filesystems.
1206 It is on by default for all supported platform at this present
1210 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1211 i386 and pc98 GENERIC kernel configuration files.
1214 sysinstall has been removed
1217 The stable/9 branch created in subversion. This corresponds to the
1218 RELENG_9 branch in CVS.
1224 Avoid using make -j when upgrading. While generally safe, there are
1225 sometimes problems using -j to upgrade. If your upgrade fails with
1226 -j, please try again without -j. From time to time in the past there
1227 have been problems using -j with buildworld and/or installworld. This
1228 is especially true when upgrading between "distant" versions (eg one
1229 that cross a major release boundary or several minor releases, or when
1230 several months have passed on the -current branch).
1232 Sometimes, obscure build problems are the result of environment
1233 poisoning. This can happen because the make utility reads its
1234 environment when searching for values for global variables. To run
1235 your build attempts in an "environmental clean room", prefix all make
1236 commands with 'env -i '. See the env(1) manual page for more details.
1238 When upgrading from one major version to another it is generally best
1239 to upgrade to the latest code in the currently installed branch first,
1240 then do an upgrade to the new branch. This is the best-tested upgrade
1241 path, and has the highest probability of being successful. Please try
1242 this approach before reporting problems with a major version upgrade.
1244 When upgrading a live system, having a root shell around before
1245 installing anything can help undo problems. Not having a root shell
1246 around can lead to problems if pam has changed too much from your
1247 starting point to allow continued authentication after the upgrade.
1249 This file should be read as a log of events. When a later event changes
1250 information of a prior event, the prior event should not be deleted.
1251 Instead, a pointer to the entry with the new information should be
1252 placed in the old entry. Readers of this file should also sanity check
1253 older entries before relying on them blindly. Authors of new entries
1254 should write them with this in mind.
1258 When upgrading the boot ZFS pool to a new version, always follow
1261 1.) recompile and reinstall the ZFS boot loader and boot block
1262 (this is part of "make buildworld" and "make installworld")
1264 2.) update the ZFS boot block on your boot drive
1266 The following example updates the ZFS boot block on the first
1267 partition (freebsd-boot) of a GPT partitioned drive ada0:
1268 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1270 Non-boot pools do not need these updates.
1274 If you are updating from a prior version of FreeBSD (even one just
1275 a few days old), you should follow this procedure. It is the most
1276 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1278 make kernel-toolchain
1279 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1280 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1282 To test a kernel once
1283 ---------------------
1284 If you just want to boot a kernel once (because you are not sure
1285 if it works, or if you want to boot a known bad kernel to provide
1286 debugging information) run
1287 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1288 nextboot -k testkernel
1290 To just build a kernel when you know that it won't mess you up
1291 --------------------------------------------------------------
1292 This assumes you are already running a CURRENT system. Replace
1293 ${arch} with the architecture of your machine (e.g. "i386",
1294 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1296 cd src/sys/${arch}/conf
1297 config KERNEL_NAME_HERE
1298 cd ../compile/KERNEL_NAME_HERE
1303 If this fails, go to the "To build a kernel" section.
1305 To rebuild everything and install it on the current system.
1306 -----------------------------------------------------------
1307 # Note: sometimes if you are running current you gotta do more than
1308 # is listed here if you are upgrading from a really old current.
1310 <make sure you have good level 0 dumps>
1312 make kernel KERNCONF=YOUR_KERNEL_HERE
1314 <reboot in single user> [3]
1321 To cross-install current onto a separate partition
1322 --------------------------------------------------
1323 # In this approach we use a separate partition to hold
1324 # current's root, 'usr', and 'var' directories. A partition
1325 # holding "/", "/usr" and "/var" should be about 2GB in
1328 <make sure you have good level 0 dumps>
1331 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1332 <maybe newfs current's root partition>
1333 <mount current's root partition on directory ${CURRENT_ROOT}>
1334 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1335 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1336 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1337 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1338 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1339 <reboot into current>
1340 <do a "native" rebuild/install as described in the previous section>
1341 <maybe install compatibility libraries from ports/misc/compat*>
1345 To upgrade in-place from stable to current
1346 ----------------------------------------------
1347 <make sure you have good level 0 dumps>
1349 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1351 <reboot in single user> [3]
1358 Make sure that you've read the UPDATING file to understand the
1359 tweaks to various things you need. At this point in the life
1360 cycle of current, things change often and you are on your own
1361 to cope. The defaults can also change, so please read ALL of
1362 the UPDATING entries.
1364 Also, if you are tracking -current, you must be subscribed to
1365 freebsd-current@freebsd.org. Make sure that before you update
1366 your sources that you have read and understood all the recent
1367 messages there. If in doubt, please track -stable which has
1368 much fewer pitfalls.
1370 [1] If you have third party modules, such as vmware, you
1371 should disable them at this point so they don't crash your
1374 [3] From the bootblocks, boot -s, and then do
1379 adjkerntz -i # if CMOS is wall time
1380 Also, when doing a major release upgrade, it is required that
1381 you boot into single user mode to do the installworld.
1383 [4] Note: This step is non-optional. Failure to do this step
1384 can result in a significant reduction in the functionality of the
1385 system. Attempting to do it by hand is not recommended and those
1386 that pursue this avenue should read this file carefully, as well
1387 as the archives of freebsd-current and freebsd-hackers mailing lists
1388 for potential gotchas. The -U option is also useful to consider.
1389 See mergemaster(8) for more information.
1391 [5] Usually this step is a noop. However, from time to time
1392 you may need to do this if you get unknown user in the following
1393 step. It never hurts to do it all the time. You may need to
1394 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1395 install) after the buildworld before this step if you last updated
1396 from current before 20130425 or from -stable before 20130430.
1398 [6] This only deletes old files and directories. Old libraries
1399 can be deleted by "make delete-old-libs", but you have to make
1400 sure that no program is using those libraries anymore.
1402 [8] In order to have a kernel that can run the 4.x binaries needed to
1403 do an installworld, you must include the COMPAT_FREEBSD4 option in
1404 your kernel. Failure to do so may leave you with a system that is
1405 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1406 required to run the 5.x binaries on more recent kernels. And so on
1407 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1409 Make sure that you merge any new devices from GENERIC since the
1410 last time you updated your kernel config file.
1412 [9] When checking out sources, you must include the -P flag to have
1413 cvs prune empty directories.
1415 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1416 "?=" instead of the "=" assignment operator, so that buildworld can
1417 override the CPUTYPE if it needs to.
1419 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1420 not on the command line, or in /etc/make.conf. buildworld will
1421 warn if it is improperly defined.
1424 This file contains a list, in reverse chronological order, of major
1425 breakages in tracking -current. It is not guaranteed to be a complete
1426 list of such breakages, and only contains entries since September 23, 2011.
1427 If you need to see UPDATING entries from before that date, you will need
1428 to fetch an UPDATING file from an older FreeBSD release.
1430 Copyright information:
1432 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1434 Redistribution, publication, translation and use, with or without
1435 modification, in full or in part, in any form or format of this
1436 document are permitted without further permission from the author.
1438 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1439 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1440 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1441 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1442 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1443 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1444 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1445 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1446 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1447 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1448 POSSIBILITY OF SUCH DAMAGE.
1450 Contact Warner Losh if you have any questions about your use of