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