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