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 Building ZFS pools on top of zvols is prohibited by default. That
36 feature has never worked safely; it's always been prone to deadlocks.
37 Using a zvol as the backing store for a VM guest's virtual disk will
38 still work, even if the guest is using ZFS. Legacy behavior can be
39 restored by setting vfs.zfs.vol.recursive=1.
42 The NONE and HPN patches has been removed from OpenSSH. They are
43 still available in the security/openssh-portable port.
46 With the addition of ypldap(8), a new _ypldap user is now required
47 during installworld. "mergemaster -p" can be used to add the user
48 prior to installworld, as documented in the handbook.
51 The tftp loader (pxeboot) now uses the option root-path directive. As a
52 consequence it no longer looks for a pxeboot.4th file on the tftp
53 server. Instead it uses the regular /boot infrastructure as with the
57 The code to start recording plug and play data into the modules has
58 been committed. While the old tools will properly build a new kernel,
59 a number of warnings about "unknown metadata record 4" will be produced
60 for an older kldxref. To avoid such warnings, make sure to rebuild
61 the kernel toolchain (or world). Make sure that you have r292078 or
62 later when trying to build 292077 or later before rebuilding.
65 Debug data files are now built by default with 'make buildworld' and
66 installed with 'make installworld'. This facilitates debugging but
67 requires more disk space both during the build and for the installed
68 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
72 r291527 changed the internal interface between the nfsd.ko and
73 nfscommon.ko modules. As such, they must both be upgraded to-gether.
74 __FreeBSD_version has been bumped because of this.
77 Add support for unicode collation strings leads to a change of
78 order of files listed by ls(1) for example. To get back to the old
79 behaviour, set LC_COLLATE environment variable to "C".
81 Databases administrators will need to reindex their databases given
82 collation results will be different.
84 Due to a bug in install(1) it is recommended to remove the ancient
85 locales before running make installworld.
87 rm -rf /usr/share/locale/*
90 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
91 libcrypto.so.7 or libssl.so.7 must be recompiled.
94 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
95 Kernel modules isp_2400_multi and isp_2500_multi were removed and
96 should be replaced with isp_2400 and isp_2500 modules respectively.
99 The build previously allowed using 'make -n' to not recurse into
100 sub-directories while showing what commands would be executed, and
101 'make -n -n' to recursively show commands. Now 'make -n' will recurse
102 and 'make -N' will not.
105 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
106 and etcupdate will now use this file. A custom sendmail.cf is now
107 updated via this mechanism rather than via installworld. If you had
108 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
109 want to remove the exclusion or change it to "always install".
110 /etc/mail/sendmail.cf is now managed the same way regardless of
111 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
112 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
115 Compatibility shims for legacy ATA device names have been removed.
116 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
117 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
118 environment variables, /dev/ad* and /dev/ar* symbolic links.
121 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
122 Please see the 20141231 entry below for information about prerequisites
123 and upgrading, if you are not already using clang 3.5.0 or higher.
126 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
127 and renamed from .symbols to .debug. This reduces the size requirements
128 on the boot partition or file system and provides consistency with
129 userland debug files.
131 When using the supported kernel installation method the
132 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
133 as is done with /boot/kernel.
135 Developers wishing to maintain the historical behavior of installing
136 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
139 The wireless drivers had undergone changes that remove the 'parent
140 interface' from the ifconfig -l output. The rc.d network scripts
141 used to check presence of a parent interface in the list, so old
142 scripts would fail to start wireless networking. Thus, etcupdate(3)
143 or mergemaster(8) run is required after kernel update, to update your
144 rc.d scripts in /etc.
147 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
148 These configurations are now automatically interpreted as
149 'scrub fragment reassemble'.
152 Kernel-loadable modules for the random(4) device are back. To use
153 them, the kernel must have
156 options RANDOM_LOADABLE
158 kldload(8) can then be used to load random_fortuna.ko
159 or random_yarrow.ko. Please note that due to the indirect
160 function calls that the loadable modules need to provide,
161 the build-in variants will be slightly more efficient.
163 The random(4) kernel option RANDOM_DUMMY has been retired due to
164 unpopularity. It was not all that useful anyway.
167 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
168 Control over building the ELF Tool Chain tools is now provided by
169 the WITHOUT_TOOLCHAIN knob.
172 The polarity of Pulse Per Second (PPS) capture events with the
173 uart(4) driver has been corrected. Prior to this change the PPS
174 "assert" event corresponded to the trailing edge of a positive PPS
175 pulse and the "clear" event was the leading edge of the next pulse.
177 As the width of a PPS pulse in a typical GPS receiver is on the
178 order of 1 millisecond, most users will not notice any significant
179 difference with this change.
181 Anyone who has compensated for the historical polarity reversal by
182 configuring a negative offset equal to the pulse width will need to
183 remove that workaround.
186 The default group assigned to /dev/dri entries has been changed
187 from 'wheel' to 'video' with the id of '44'. If you want to have
188 access to the dri devices please add yourself to the video group
191 # pw groupmod video -m $USER
194 The menu.rc and loader.rc files will now be replaced during
195 upgrades. Please migrate local changes to menu.rc.local and
196 loader.rc.local instead.
199 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
200 strings and strip have been removed. The src.conf(5) knob
201 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
204 As ZFS requires more kernel stack pages than is the default on some
205 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
206 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
208 Please consider using 'options KSTACK_PAGES=X' where X is greater
209 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
212 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
213 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
214 default, i.e., they will not contain "::". For example, instead
215 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
216 to have a more specific match, such as different map entries for
217 IPv6:0:0 vs IPv6:0. This change requires that configuration
218 data (including maps, files, classes, custom ruleset, etc.) must
219 use the same format, so make certain such configuration data is
220 upgrading. As a very simple check search for patterns like
221 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
222 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
223 the cf option UseCompressedIPv6Addresses.
226 The default kernel entropy-processing algorithm is now
227 Fortuna, replacing Yarrow.
229 Assuming you have 'device random' in your kernel config
230 file, the configurations allow a kernel option to override
231 this default. You may choose *ONE* of:
233 options RANDOM_YARROW # Legacy /dev/random algorithm.
234 options RANDOM_DUMMY # Blocking-only driver.
236 If you have neither, you get Fortuna. For most people,
237 read no further, Fortuna will give a /dev/random that works
238 like it always used to, and the difference will be irrelevant.
240 If you remove 'device random', you get *NO* kernel-processed
241 entropy at all. This may be acceptable to folks building
242 embedded systems, but has complications. Carry on reading,
243 and it is assumed you know what you need.
245 *PLEASE* read random(4) and random(9) if you are in the
246 habit of tweaking kernel configs, and/or if you are a member
247 of the embedded community, wanting specific and not-usual
248 behaviour from your security subsystems.
250 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
251 random', you will NOT have a functioning /dev/random, and
252 many cryptographic features will not work, including SSH.
253 You may also find strange behaviour from the random(3) set
254 of library functions, in particular sranddev(3), srandomdev(3)
255 and arc4random(3). The reason for this is that the KERN_ARND
256 sysctl only returns entropy if it thinks it has some to
257 share, and with RANDOM_DUMMY or no 'device random' this
261 An additional fix for the issue described in the 20150614 sendmail
262 entry below has been been committed in revision 284717.
265 FreeBSD's old make (fmake) has been removed from the system. It is
266 available as the devel/fmake port or via pkg install fmake.
269 The fix for the issue described in the 20150614 sendmail entry
270 below has been been committed in revision 284436. The work
271 around described in that entry is no longer needed unless the
272 default setting is overridden by a confDH_PARAMETERS configuration
273 setting of '5' or pointing to a 512 bit DH parameter file.
276 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
277 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
278 and devel/kyua to version 0.20+ and adjust any calling code to work
279 with Kyuafile and kyua.
282 The import of openssl to address the FreeBSD-SA-15:10.openssl
283 security advisory includes a change which rejects handshakes
284 with DH parameters below 768 bits. sendmail releases prior
285 to 8.15.2 (not yet released), defaulted to a 512 bit
286 DH parameter setting for client connections. To work around
287 this interoperability, sendmail can be configured to use a
288 2048 bit DH parameter by:
290 1. Edit /etc/mail/`hostname`.mc
291 2. If a setting for confDH_PARAMETERS does not exist or
292 exists and is set to a string beginning with '5',
294 3. If a setting for confDH_PARAMETERS exists and is set to
295 a file path, create a new file with:
296 openssl dhparam -out /path/to/file 2048
297 4. Rebuild the .cf file:
298 cd /etc/mail/; make; make install
300 cd /etc/mail/; make restart
302 A sendmail patch is coming, at which time this file will be
306 Generation of legacy formatted entries have been disabled by default
307 in pwd_mkdb(8), as all base system consumers of the legacy formatted
308 entries were converted to use the new format by default when the new,
309 machine independent format have been added and supported since FreeBSD
312 Please see the pwd_mkdb(8) manual page for further details.
315 Clang and llvm have been upgraded to 3.6.1 release. Please see the
316 20141231 entry below for information about prerequisites and upgrading,
317 if you are not already using 3.5.0 or higher.
320 TI platform code switched to using vendor DTS files and this update
321 may break existing systems running on Beaglebone, Beaglebone Black,
324 - dtb files should be regenerated/reinstalled. Filenames are the
325 same but content is different now
326 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
327 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
328 addressing scheme is now pin 25 on /dev/gpioc3.
329 - Pandaboard: /etc/ttys should be updated, serial console device is
330 now /dev/ttyu2, not /dev/ttyu0
333 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
334 If you need the GNU extension from groff soelim(1), install groff
335 from package: pkg install groff, or via ports: textproc/groff.
338 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
339 defined in symlink(7); previously symlinks were silently ignored.
342 The const qualifier has been removed from iconv(3) to comply with
343 POSIX. The ports tree is aware of this from r384038 onwards.
346 Libraries specified by LIBADD in Makefiles must have a corresponding
347 DPADD_<lib> variable to ensure correct dependencies. This is now
348 enforced in src.libnames.mk.
351 From legacy ata(4) driver was removed support for SATA controllers
352 supported by more functional drivers ahci(4), siis(4) and mvs(4).
353 Kernel modules ataahci and ataadaptec were removed completely,
354 replaced by ahci and mvs modules respectively.
357 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
358 the 20141231 entry below for information about prerequisites and
359 upgrading, if you are not already using 3.5.0 or higher.
362 The 32-bit PowerPC kernel has been changed to a position-independent
363 executable. This can only be booted with a version of loader(8)
364 newer than January 31, 2015, so make sure to update both world and
365 kernel before rebooting.
368 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
369 but before r278950, the RNG was not seeded properly. Immediately
370 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
371 ssh keys or openssl keys) that were generated w/ a kernel from that
372 range. This does not affect programs that directly used /dev/random
373 or /dev/urandom. All userland uses of arc4random(3) are affected.
376 The autofs(4) ABI was changed in order to restore binary compatibility
377 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
381 The powerpc64 kernel has been changed to a position-independent
382 executable. This can only be booted with a new version of loader(8),
383 so make sure to update both world and kernel before rebooting.
386 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
387 only release, no new features have been added. Please see the 20141231
388 entry below for information about prerequisites and upgrading, if you
389 are not already using 3.5.0.
392 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
393 taken from the ELF Tool Chain project rather than GNU binutils. They
394 should be drop-in replacements, with the addition of arm64 support.
395 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
396 binutils tools, if necessary. See 20150805 for updated information.
399 The default Unbound configuration now enables remote control
400 using a local socket. Users who have already enabled the
401 local_unbound service should regenerate their configuration
402 by running "service local_unbound setup" as root.
405 The GNU texinfo and GNU info pages have been removed.
406 To be able to view GNU info pages please install texinfo from ports.
409 Clang, llvm and lldb have been upgraded to 3.5.0 release.
411 As of this release, a prerequisite for building clang, llvm and lldb is
412 a C++11 capable compiler and C++11 standard library. This means that to
413 be able to successfully build the cross-tools stage of buildworld, with
414 clang as the bootstrap compiler, your system compiler or cross compiler
415 should either be clang 3.3 or later, or gcc 4.8 or later, and your
416 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
419 On any standard FreeBSD 10.x or 11.x installation, where clang and
420 libc++ are on by default (that is, on x86 or arm), this should work out
423 On 9.x installations where clang is enabled by default, e.g. on x86 and
424 powerpc, libc++ will not be enabled by default, so libc++ should be
425 built (with clang) and installed first. If both clang and libc++ are
426 missing, build clang first, then use it to build libc++.
428 On 8.x and earlier installations, upgrade to 9.x first, and then follow
429 the instructions for 9.x above.
431 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
432 default, and do not build clang.
434 Many embedded systems are resource constrained, and will not be able to
435 build clang in a reasonable time, or in some cases at all. In those
436 cases, cross building bootable systems on amd64 is a workaround.
438 This new version of clang introduces a number of new warnings, of which
439 the following are most likely to appear:
443 This warns in two cases, for both C and C++:
444 * When the code is trying to take the absolute value of an unsigned
445 quantity, which is effectively a no-op, and almost never what was
446 intended. The code should be fixed, if at all possible. If you are
447 sure that the unsigned quantity can be safely cast to signed, without
448 loss of information or undefined behavior, you can add an explicit
449 cast, or disable the warning.
451 * When the code is trying to take an absolute value, but the called
452 abs() variant is for the wrong type, which can lead to truncation.
453 If you want to disable the warning instead of fixing the code, please
454 make sure that truncation will not occur, or it might lead to unwanted
457 -Wtautological-undefined-compare and
458 -Wundefined-bool-conversion
460 These warn when C++ code is trying to compare 'this' against NULL, while
461 'this' should never be NULL in well-defined C++ code. However, there is
462 some legacy (pre C++11) code out there, which actively abuses this
463 feature, which was less strictly defined in previous C++ versions.
465 Squid and openjdk do this, for example. The warning can be turned off
466 for C++98 and earlier, but compiling the code in C++11 mode might result
467 in unexpected behavior; for example, the parts of the program that are
468 unreachable could be optimized away.
471 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
472 kernel sources have been removed. The .h files remain, since some
473 utilities include them. This will need to be fixed later.
474 If "mount -t oldnfs ..." is attempted, it will fail.
475 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
476 the utilities will report errors.
479 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
480 directories to top level SUBDIR variable when their parent
481 directory is included in LOCAL_DIRS. Users with build systems with
482 such hierarchies and without SUBDIR entries in the parent
483 directory Makefiles should add them or add the directories to
487 faith(4) and faithd(8) have been removed from the base system. Faith
488 has been obsolete for a very long time.
491 vt(4), the new console driver, is enabled by default. It brings
492 support for Unicode and double-width characters, as well as
493 support for UEFI and integration with the KMS kernel video
496 You may need to update your console settings in /etc/rc.conf,
497 most probably the keymap. During boot, /etc/rc.d/syscons will
498 indicate what you need to do.
500 vt(4) still has issues and lacks some features compared to
501 syscons(4). See the wiki for up-to-date information:
502 https://wiki.freebsd.org/Newcons
504 If you want to keep using syscons(4), you can do so by adding
505 the following line to /boot/loader.conf:
509 pjdfstest has been integrated into kyua as an opt-in test suite.
510 Please see share/doc/pjdfstest/README for more details on how to
514 gperf has been removed from the base system for architectures
515 that use clang. Ports that require gperf will obtain it from the
519 pjdfstest has been moved from tools/regression/pjdfstest to
523 At svn r271982, The default linux compat kernel ABI has been adjusted
524 to 2.6.18 in support of the linux-c6 compat ports infrastructure
525 update. If you wish to continue using the linux-f10 compat ports,
526 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
527 encouraged to update their linux-compat packages to linux-c6 during
528 their next update cycle.
531 The ofwfb driver, used to provide a graphics console on PowerPC when
532 using vt(4), no longer allows mmap() of all physical memory. This
533 will prevent Xorg on PowerPC with some ATI graphics cards from
534 initializing properly unless x11-servers/xorg-server is updated to
538 The xdev targets have been converted to using TARGET and
539 TARGET_ARCH instead of XDEV and XDEV_ARCH.
542 The default unbound configuration has been modified to address
543 issues with reverse lookups on networks that use private
544 address ranges. If you use the local_unbound service, run
545 "service local_unbound setup" as root to regenerate your
546 configuration, then "service local_unbound reload" to load the
550 The GNU texinfo and GNU info pages are not built and installed
551 anymore, WITH_INFO knob has been added to allow to built and install
553 UPDATE: see 20150102 entry on texinfo's removal
556 The GNU readline library is now an INTERNALLIB - that is, it is
557 statically linked into consumers (GDB and variants) in the base
558 system, and the shared library is no longer installed. The
559 devel/readline port is available for third party software that
563 The Itanium architecture (ia64) has been removed from the list of
564 known architectures. This is the first step in the removal of the
568 Commit r268115 has added NFSv4.1 server support, merged from
569 projects/nfsv4.1-server. Since this includes changes to the
570 internal interfaces between the NFS related modules, a full
571 build of the kernel and modules will be necessary.
572 __FreeBSD_version has been bumped.
575 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
576 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
577 which differs from the behaviour controlled by this knob.)
580 Maximal length of the serial number in CTL was increased from 16 to
581 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
582 and ctld, need to be rebuilt to work with a new kernel.
585 The libatf-c and libatf-c++ major versions were downgraded to 0 and
586 1 respectively to match the upstream numbers. They were out of
587 sync because, when they were originally added to FreeBSD, the
588 upstream versions were not respected. These libraries are private
589 and not yet built by default, so renumbering them should be a
590 non-issue. However, unclean source trees will yield broken test
591 programs once the operator executes "make delete-old-libs" after a
594 Additionally, the atf-sh binary was made private by moving it into
595 /usr/libexec/. Already-built shell test programs will keep the
596 path to the old binary so they will break after "make delete-old"
599 If you are using WITH_TESTS=yes (not the default), wipe the object
600 tree and rebuild from scratch to prevent spurious test failures.
601 This is only needed once: the misnumbered libraries and misplaced
602 binaries have been added to OptionalObsoleteFiles.inc so they will
603 be removed during a clean upgrade.
606 Clang and llvm have been upgraded to 3.4.1 release.
609 We bogusly installed src.opts.mk in /usr/share/mk. This file should
610 be removed to avoid issues in the future (and has been added to
614 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
615 past, it affected all builds that used the bsd.*.mk files. The old
616 behavior was a bug, but people may have relied upon it. To get this
617 behavior back, you can .include /etc/src.conf from /etc/make.conf
618 (which is still global and isn't changed). This also changes the
619 behavior of incremental builds inside the tree of individual
620 directories. Set MAKESYSPATH to ".../share/mk" to do that.
621 Although this has survived make universe and some upgrade scenarios,
622 other upgrade scenarios may have broken. At least one form of
623 temporary breakage was fixed with MAKESYSPATH settings for buildworld
624 as well... In cases where MAKESYSPATH isn't working with this
625 setting, you'll need to set it to the full path to your tree.
627 One side effect of all this cleaning up is that bsd.compiler.mk
628 is no longer implicitly included by bsd.own.mk. If you wish to
629 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
633 The lindev device has been removed since /dev/full has been made a
634 standard device. __FreeBSD_version has been bumped.
637 The knob WITHOUT_VI was added to the base system, which controls
638 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
639 in order to reorder files share/termcap and didn't build ex(1) as a
640 build tool, so building/installing with WITH_VI is highly advised for
641 build hosts for older releases.
643 This issue has been fixed in stable/9 and stable/10 in r277022 and
644 r276991, respectively.
647 The YES_HESIOD knob has been removed. It has been obsolete for
648 a decade. Please move to using WITH_HESIOD instead or your builds
649 will silently lack HESIOD.
652 The uart(4) driver has been changed with respect to its handling
653 of the low-level console. Previously the uart(4) driver prevented
654 any process from changing the baudrate or the CLOCAL and HUPCL
655 control flags. By removing the restrictions, operators can make
656 changes to the serial console port without having to reboot.
657 However, when getty(8) is started on the serial device that is
658 associated with the low-level console, a misconfigured terminal
659 line in /etc/ttys will now have a real impact.
660 Before upgrading the kernel, make sure that /etc/ttys has the
661 serial console device configured as 3wire without baudrate to
662 preserve the previous behaviour. E.g:
663 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
666 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
667 to improve performance. To re-enable it, if needed, run rpcbind
668 with command line option -W.
671 Switched back to the GPL dtc compiler due to updates in the upstream
672 dts files not being supported by the BSDL dtc compiler. You will need
673 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
674 may result while building dtb files during a kernel build if you fail
675 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
678 Clang and llvm have been upgraded to 3.4 release.
681 The nve(4) driver has been removed. Please use the nfe(4) driver
682 for NVIDIA nForce MCP Ethernet adapters instead.
685 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
686 This could cause certain C++ applications using shared libraries built
687 against the previous version of libc++ to crash. The incompatibility
688 has now been fixed, but any C++ applications or shared libraries built
689 between r261283 and r261801 should be recompiled.
692 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
693 capability mode support. Please note that enabling the feature in
694 kernel is still highly recommended.
697 OpenSSH is now built with sandbox support, and will use sandbox as
698 the default privilege separation method. This requires Capsicum
699 capability mode support in kernel.
702 The libelf and libdwarf libraries have been updated to newer
703 versions from upstream. Shared library version numbers for
704 these two libraries were bumped. Any ports or binaries
705 requiring these two libraries should be recompiled.
706 __FreeBSD_version is bumped to 1100006.
709 If a Makefile in a tests/ directory was auto-generating a Kyuafile
710 instead of providing an explicit one, this would prevent such
711 Makefile from providing its own Kyuafile in the future during
712 NO_CLEAN builds. This has been fixed in the Makefiles but manual
713 intervention is needed to clean an objdir if you use NO_CLEAN:
714 # find /usr/obj -name Kyuafile | xargs rm -f
717 The behavior of gss_pseudo_random() for the krb5 mechanism
718 has changed, for applications requesting a longer random string
719 than produced by the underlying enctype's pseudo-random() function.
720 In particular, the random string produced from a session key of
721 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
722 be different at the 17th octet and later, after this change.
723 The counter used in the PRF+ construction is now encoded as a
724 big-endian integer in accordance with RFC 4402.
725 __FreeBSD_version is bumped to 1100004.
728 The WITHOUT_ATF build knob has been removed and its functionality
729 has been subsumed into the more generic WITHOUT_TESTS. If you were
730 using the former to disable the build of the ATF libraries, you
731 should change your settings to use the latter.
734 The default version of mtree is nmtree which is obtained from
735 NetBSD. The output is generally the same, but may vary
736 slightly. If you found you need identical output adding
737 "-F freebsd9" to the command line should do the trick. For the
738 time being, the old mtree is available as fmtree.
741 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
742 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
743 1.1.4_8 and verify bsdyml not linked in, before running "make
745 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
747 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
750 The stable/10 branch has been created in subversion from head
754 The rc.d/jail script has been updated to support jail(8)
755 configuration file. The "jail_<jname>_*" rc.conf(5) variables
756 for per-jail configuration are automatically converted to
757 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
758 This is transparently backward compatible. See below about some
759 incompatibilities and rc.conf(5) manual page for more details.
761 These variables are now deprecated in favor of jail(8) configuration
762 file. One can use "rc.d/jail config <jname>" command to generate
763 a jail(8) configuration file in /var/run/jail.<jname>.conf without
764 running the jail(8) utility. The default pathname of the
765 configuration file is /etc/jail.conf and can be specified by
766 using $jail_conf or $jail_<jname>_conf variables.
768 Please note that jail_devfs_ruleset accepts an integer at
769 this moment. Please consider to rewrite the ruleset name
773 BIND has been removed from the base system. If all you need
774 is a local resolver, simply enable and start the local_unbound
775 service instead. Otherwise, several versions of BIND are
776 available in the ports tree. The dns/bind99 port is one example.
778 With this change, nslookup(1) and dig(1) are no longer in the base
779 system. Users should instead use host(1) and drill(1) which are
780 in the base system. Alternatively, nslookup and dig can
781 be obtained by installing the dns/bind-tools port.
784 With the addition of unbound(8), a new unbound user is now
785 required during installworld. "mergemaster -p" can be used to
786 add the user prior to installworld, as documented in the handbook.
789 OpenSSH is now built with DNSSEC support, and will by default
790 silently trust signed SSHFP records. This can be controlled with
791 the VerifyHostKeyDNS client configuration setting. DNSSEC support
792 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
795 The GNU Compiler Collection and C++ standard library (libstdc++)
796 are no longer built by default on platforms where clang is the system
797 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
801 The PROCDESC kernel option is now part of the GENERIC kernel
802 configuration and is required for the rwhod(8) to work.
803 If you are using custom kernel configuration, you should include
807 The API and ABI related to the Capsicum framework was modified
808 in backward incompatible way. The userland libraries and programs
809 have to be recompiled to work with the new kernel. This includes the
810 following libraries and programs, but the whole buildworld is
811 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
812 kdump, procstat, rwho, rwhod, uniq.
815 AES-NI intrinsic support has been added to gcc. The AES-NI module
816 has been updated to use this support. A new gcc is required to build
817 the aesni module on both i386 and amd64.
820 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
821 Thus "device padlock_rng" and "device rdrand_rng" should be
822 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
825 WITH_ICONV has been split into two feature sets. WITH_ICONV now
826 enables just the iconv* functionality and is now on by default.
827 WITH_LIBICONV_COMPAT enables the libiconv api and link time
828 compatability. Set WITHOUT_ICONV to build the old way.
829 If you have been using WITH_ICONV before, you will very likely
830 need to turn on WITH_LIBICONV_COMPAT.
833 INVARIANTS option now enables DEBUG for code with OpenSolaris and
834 Illumos origin, including ZFS. If you have INVARIANTS in your
835 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
837 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
838 locks if WITNESS option was set. Because that generated a lot of
839 witness(9) reports and all of them were believed to be false
840 positives, this is no longer done. New option OPENSOLARIS_WITNESS
841 can be used to achieve the previous behavior.
844 Timer values in IPv6 data structures now use time_uptime instead
845 of time_second. Although this is not a user-visible functional
846 change, userland utilities which directly use them---ndp(8),
847 rtadvd(8), and rtsold(8) in the base system---need to be updated
851 find -delete can now delete the pathnames given as arguments,
852 instead of only files found below them or if the pathname did
853 not contain any slashes. Formerly, the following error message
856 find: -delete: <path>: relative path potentially not safe
858 Deleting the pathnames given as arguments can be prevented
859 without error messages using -mindepth 1 or by changing
860 directory and passing "." as argument to find. This works in the
861 old as well as the new version of find.
864 Behavior of devfs rules path matching has been changed.
865 Pattern is now always matched against fully qualified devfs
866 path and slash characters must be explicitly matched by
867 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
868 subdirectories must be reviewed.
871 The default ARM ABI has changed to the ARM EABI. The old ABI is
872 incompatible with the ARM EABI and all programs and modules will
873 need to be rebuilt to work with a new kernel.
875 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
877 NOTE: Support for the old ABI will be removed in the future and
878 users are advised to upgrade.
881 pkg_install has been disconnected from the build if you really need it
882 you should add WITH_PKGTOOLS in your src.conf(5).
885 Most of network statistics structures were changed to be able
886 keep 64-bits counters. Thus all tools, that work with networking
887 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
890 Fix a bug that allowed a tracing process (e.g. gdb) to write
891 to a memory-mapped file in the traced process's address space
892 even if neither the traced process nor the tracing process had
893 write access to that file.
896 CVS has been removed from the base system. An exact copy
897 of the code is available from the devel/cvs port.
900 Some people report the following error after the switch to bmake:
902 make: illegal option -- J
903 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
905 *** [buildworld] Error code 2
907 this likely due to an old instance of make in
908 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
909 which src/Makefile will use that blindly, if it exists, so if
910 you see the above error:
912 rm -rf `make -V MAKEPATH`
917 Use bmake by default.
918 Whereas before one could choose to build with bmake via
919 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
920 make. The goal is to remove these knobs for 10-RELEASE.
922 It is worth noting that bmake (like gmake) treats the command
923 line as the unit of failure, rather than statements within the
924 command line. Thus '(cd some/where && dosomething)' is safer
925 than 'cd some/where; dosomething'. The '()' allows consistent
926 behavior in parallel build.
929 Fix a bug that allows NFS clients to issue READDIR on files.
932 The WITHOUT_IDEA option has been removed because
933 the IDEA patent expired.
936 The sysctl which controls TRIM support under ZFS has been renamed
937 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
941 The mergemaster command now uses the default MAKEOBJDIRPREFIX
942 rather than creating it's own in the temporary directory in
943 order allow access to bootstrapped versions of tools such as
944 install and mtree. When upgrading from version of FreeBSD where
945 the install command does not support -l, you will need to
946 install a new mergemaster command if mergemaster -p is required.
947 This can be accomplished with the command (cd src/usr.sbin/mergemaster
951 Legacy ATA stack, disabled and replaced by new CAM-based one since
952 FreeBSD 9.0, completely removed from the sources. Kernel modules
953 atadisk and atapi*, user-level tools atacontrol and burncd are
954 removed. Kernel option `options ATA_CAM` is now permanently enabled
958 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
959 and socketpair(2). Software, in particular Kerberos, may
960 automatically detect and use these during building. The resulting
961 binaries will not work on older kernels.
964 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
965 information, see the respective 20130304 entry).
968 Recent commits to callout(9) changed the size of struct callout,
969 so the KBI is probably heavily disturbed. Also, some functions
970 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
971 by macros. Every kernel module using it won't load, so rebuild
974 The ctl device has been re-enabled in GENERIC for i386 and amd64,
975 but does not initialize by default (because of the new CTL_DISABLE
976 option) to save memory. To re-enable it, remove the CTL_DISABLE
977 option from the kernel config file or set kern.cam.ctl.disable=0
978 in /boot/loader.conf.
981 The ctl device has been disabled in GENERIC for i386 and amd64.
982 This was done due to the extra memory being allocated at system
983 initialisation time by the ctl driver which was only used if
984 a CAM target device was created. This makes a FreeBSD system
985 unusable on 128MB or less of RAM.
988 A new compression method (lz4) has been merged to -HEAD. Please
989 refer to zpool-features(7) for more information.
991 Please refer to the "ZFS notes" section of this file for information
992 on upgrading boot ZFS pools.
995 A BSD-licensed patch(1) variant has been added and is installed
996 as bsdpatch, being the GNU version the default patch.
997 To inverse the logic and use the BSD-licensed one as default,
998 while having the GNU version installed as gnupatch, rebuild
999 and install world with the WITH_BSD_PATCH knob set.
1002 Due to the use of the new -l option to install(1) during build
1003 and install, you must take care not to directly set the INSTALL
1004 make variable in your /etc/make.conf, /etc/src.conf, or on the
1005 command line. If you wish to use the -C flag for all installs
1006 you may be able to add INSTALL+=-C to /etc/make.conf or
1010 The install(1) option -M has changed meaning and now takes an
1011 argument that is a file or path to append logs to. In the
1012 unlikely event that -M was the last option on the command line
1013 and the command line contained at least two files and a target
1014 directory the first file will have logs appended to it. The -M
1015 option served little practical purpose in the last decade so its
1016 use is expected to be extremely rare.
1019 After switching to Clang as the default compiler some users of ZFS
1020 on i386 systems started to experience stack overflow kernel panics.
1021 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1024 GEOM_LABEL now mangles label names read from file system metadata.
1025 Mangling affect labels containing spaces, non-printable characters,
1026 '%' or '"'. Device names in /etc/fstab and other places may need to
1030 By default, only the 10 most recent kernel dumps will be saved. To
1031 restore the previous behaviour (no limit on the number of kernel dumps
1032 stored in the dump directory) add the following line to /etc/rc.conf:
1037 With the addition of auditdistd(8), a new auditdistd user is now
1038 required during installworld. "mergemaster -p" can be used to
1039 add the user prior to installworld, as documented in the handbook.
1042 The sin6_scope_id member variable in struct sockaddr_in6 is now
1043 filled by the kernel before passing the structure to the userland via
1044 sysctl or routing socket. This means the KAME-specific embedded scope
1045 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1046 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1047 __FreeBSD_version is bumped to 1000025.
1050 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1051 This means that the world and kernel will be compiled with clang
1052 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1053 and /usr/bin/cpp. To disable this behavior and revert to building
1054 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1055 of current may need to bootstrap WITHOUT_CLANG first if the clang
1056 build fails (its compatibility window doesn't extend to the 9 stable
1060 The IPFIREWALL_FORWARD kernel option has been removed. Its
1061 functionality now turned on by default.
1064 The ZERO_COPY_SOCKET kernel option has been removed and
1065 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1066 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1067 mechanism which is not safe and may result in kernel crashes.
1068 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1069 driver supports disposeable external page sized mbuf storage.
1070 Proper replacements for both zero-copy mechanisms are under
1071 consideration and will eventually lead to complete removal
1072 of the two kernel options.
1075 The IPv4 network stack has been converted to network byte
1076 order. The following modules need to be recompiled together
1077 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1078 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1081 Support for non-MPSAFE filesystems was removed from VFS. The
1082 VFS_VERSION was bumped, all filesystem modules shall be
1086 All the non-MPSAFE filesystems have been disconnected from
1087 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1088 portalfs, smbfs, xfs.
1091 The interface cloning API and ABI has changed. The following
1092 modules need to be recompiled together with kernel:
1093 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1094 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1095 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1098 The sdhci driver was split in two parts: sdhci (generic SD Host
1099 Controller logic) and sdhci_pci (actual hardware driver).
1100 No kernel config modifications are required, but if you
1101 load sdhc as a module you must switch to sdhci_pci instead.
1104 Import the FUSE kernel and userland support into base system.
1107 The GNU sort(1) program has been removed since the BSD-licensed
1108 sort(1) has been the default for quite some time and no serious
1109 problems have been reported. The corresponding WITH_GNU_SORT
1113 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1114 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1118 The net80211(4) ABI has been changed to allow for improved driver
1119 PS-POLL and power-save support. All wireless drivers need to be
1120 recompiled to work with the new kernel.
1123 The random(4) support for the VIA hardware random number
1124 generator (`PADLOCK') is no longer enabled unconditionally.
1125 Add the padlock_rng device in the custom kernel config if
1126 needed. The GENERIC kernels on i386 and amd64 do include the
1127 device, so the change only affects the custom kernel
1131 The pf(4) packet filter ABI has been changed. pfctl(8) and
1132 snmp_pf module need to be recompiled to work with new kernel.
1135 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1136 to -HEAD. Pools that have empty_bpobj in active state can not be
1137 imported read-write with ZFS implementations that do not support
1138 this feature. For more information read the zpool-features(5)
1142 The sparc64 ZFS loader has been changed to no longer try to auto-
1143 detect ZFS providers based on diskN aliases but now requires these
1144 to be explicitly listed in the OFW boot-device environment variable.
1147 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1148 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1149 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1152 The following sysctls and tunables have been renamed for consistency
1153 with other variables:
1154 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1155 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1158 The sort utility has been replaced with BSD sort. For now, GNU sort
1159 is also available as "gnusort" or the default can be set back to
1160 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1161 installed as "bsdsort".
1164 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1165 Starting with this version the old system of ZFS pool versioning
1166 is superseded by "feature flags". This concept enables forward
1167 compatibility against certain future changes in functionality of ZFS
1168 pools. The first read-only compatible "feature flag" for ZFS pools
1169 is named "com.delphix:async_destroy". For more information
1170 read the new zpool-features(5) manual page.
1171 Please refer to the "ZFS notes" section of this file for information
1172 on upgrading boot ZFS pools.
1175 The malloc(3) implementation embedded in libc now uses sources imported
1176 as contrib/jemalloc. The most disruptive API change is to
1177 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1178 delete it prior to installworld, and optionally re-create it using the
1179 new format after rebooting. See malloc.conf(5) for details
1180 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1184 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1185 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1186 now spelled mips. This is to aid compatibility with third-party
1187 software that expects this naming scheme in uname(3). Little-endian
1188 settings are unchanged. If you are updating a big-endian mips64 machine
1189 from before this change, you may need to set MACHINE_ARCH=mips64 in
1190 your environment before the new build system will recognize your machine.
1193 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1197 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1198 nullfs(5) did not pass through all behaviours to the underlying layer,
1199 as a result if we bound to a socket on the lower layer we could connect
1200 only to the lower path; if we bound to the upper layer we could connect
1201 only to the upper path. The new behavior is one can connect to both the
1202 lower and the upper paths regardless what layer path one binds to.
1205 The getifaddrs upgrade path broken with 20111215 has been restored.
1206 If you have upgraded in between 20111215 and 20120209 you need to
1207 recompile libc again with your kernel. You still need to recompile
1208 world to be able to configure CARP but this restriction already
1209 comes from 20111215.
1212 The set_rcvar() function has been removed from /etc/rc.subr. All
1213 base and ports rc.d scripts have been updated, so if you have a
1214 port installed with a script in /usr/local/etc/rc.d you can either
1215 hand-edit the rcvar= line, or reinstall the port.
1217 An easy way to handle the mass-update of /etc/rc.d:
1218 rm /etc/rc.d/* && mergemaster -i
1221 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1222 on the current CPU and prevents other threads from running.
1223 This behavior can be reverted using the kern.stop_scheduler_on_panic
1225 The new behavior can be incompatible with kern.sync_on_panic.
1228 The carp(4) facility has been changed significantly. Configuration
1229 of the CARP protocol via ifconfig(8) has changed, as well as format
1230 of CARP events submitted to devd(8) has changed. See manual pages
1231 for more information. The arpbalance feature of carp(4) is currently
1232 not supported anymore.
1234 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1235 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1236 need to be recompiled.
1239 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1243 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1244 explicitely support non-MPSAFE filesystems.
1245 It is on by default for all supported platform at this present
1249 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1250 i386 and pc98 GENERIC kernel configuration files.
1253 sysinstall has been removed
1256 The stable/9 branch created in subversion. This corresponds to the
1257 RELENG_9 branch in CVS.
1263 Avoid using make -j when upgrading. While generally safe, there are
1264 sometimes problems using -j to upgrade. If your upgrade fails with
1265 -j, please try again without -j. From time to time in the past there
1266 have been problems using -j with buildworld and/or installworld. This
1267 is especially true when upgrading between "distant" versions (eg one
1268 that cross a major release boundary or several minor releases, or when
1269 several months have passed on the -current branch).
1271 Sometimes, obscure build problems are the result of environment
1272 poisoning. This can happen because the make utility reads its
1273 environment when searching for values for global variables. To run
1274 your build attempts in an "environmental clean room", prefix all make
1275 commands with 'env -i '. See the env(1) manual page for more details.
1277 When upgrading from one major version to another it is generally best
1278 to upgrade to the latest code in the currently installed branch first,
1279 then do an upgrade to the new branch. This is the best-tested upgrade
1280 path, and has the highest probability of being successful. Please try
1281 this approach before reporting problems with a major version upgrade.
1283 When upgrading a live system, having a root shell around before
1284 installing anything can help undo problems. Not having a root shell
1285 around can lead to problems if pam has changed too much from your
1286 starting point to allow continued authentication after the upgrade.
1288 This file should be read as a log of events. When a later event changes
1289 information of a prior event, the prior event should not be deleted.
1290 Instead, a pointer to the entry with the new information should be
1291 placed in the old entry. Readers of this file should also sanity check
1292 older entries before relying on them blindly. Authors of new entries
1293 should write them with this in mind.
1297 When upgrading the boot ZFS pool to a new version, always follow
1300 1.) recompile and reinstall the ZFS boot loader and boot block
1301 (this is part of "make buildworld" and "make installworld")
1303 2.) update the ZFS boot block on your boot drive
1305 The following example updates the ZFS boot block on the first
1306 partition (freebsd-boot) of a GPT partitioned drive ada0:
1307 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1309 Non-boot pools do not need these updates.
1313 If you are updating from a prior version of FreeBSD (even one just
1314 a few days old), you should follow this procedure. It is the most
1315 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1317 make kernel-toolchain
1318 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1319 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1321 To test a kernel once
1322 ---------------------
1323 If you just want to boot a kernel once (because you are not sure
1324 if it works, or if you want to boot a known bad kernel to provide
1325 debugging information) run
1326 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1327 nextboot -k testkernel
1329 To just build a kernel when you know that it won't mess you up
1330 --------------------------------------------------------------
1331 This assumes you are already running a CURRENT system. Replace
1332 ${arch} with the architecture of your machine (e.g. "i386",
1333 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1335 cd src/sys/${arch}/conf
1336 config KERNEL_NAME_HERE
1337 cd ../compile/KERNEL_NAME_HERE
1342 If this fails, go to the "To build a kernel" section.
1344 To rebuild everything and install it on the current system.
1345 -----------------------------------------------------------
1346 # Note: sometimes if you are running current you gotta do more than
1347 # is listed here if you are upgrading from a really old current.
1349 <make sure you have good level 0 dumps>
1351 make kernel KERNCONF=YOUR_KERNEL_HERE
1353 <reboot in single user> [3]
1360 To cross-install current onto a separate partition
1361 --------------------------------------------------
1362 # In this approach we use a separate partition to hold
1363 # current's root, 'usr', and 'var' directories. A partition
1364 # holding "/", "/usr" and "/var" should be about 2GB in
1367 <make sure you have good level 0 dumps>
1370 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1371 <maybe newfs current's root partition>
1372 <mount current's root partition on directory ${CURRENT_ROOT}>
1373 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1374 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1375 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1376 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1377 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1378 <reboot into current>
1379 <do a "native" rebuild/install as described in the previous section>
1380 <maybe install compatibility libraries from ports/misc/compat*>
1384 To upgrade in-place from stable to current
1385 ----------------------------------------------
1386 <make sure you have good level 0 dumps>
1388 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1390 <reboot in single user> [3]
1397 Make sure that you've read the UPDATING file to understand the
1398 tweaks to various things you need. At this point in the life
1399 cycle of current, things change often and you are on your own
1400 to cope. The defaults can also change, so please read ALL of
1401 the UPDATING entries.
1403 Also, if you are tracking -current, you must be subscribed to
1404 freebsd-current@freebsd.org. Make sure that before you update
1405 your sources that you have read and understood all the recent
1406 messages there. If in doubt, please track -stable which has
1407 much fewer pitfalls.
1409 [1] If you have third party modules, such as vmware, you
1410 should disable them at this point so they don't crash your
1413 [3] From the bootblocks, boot -s, and then do
1418 adjkerntz -i # if CMOS is wall time
1419 Also, when doing a major release upgrade, it is required that
1420 you boot into single user mode to do the installworld.
1422 [4] Note: This step is non-optional. Failure to do this step
1423 can result in a significant reduction in the functionality of the
1424 system. Attempting to do it by hand is not recommended and those
1425 that pursue this avenue should read this file carefully, as well
1426 as the archives of freebsd-current and freebsd-hackers mailing lists
1427 for potential gotchas. The -U option is also useful to consider.
1428 See mergemaster(8) for more information.
1430 [5] Usually this step is a noop. However, from time to time
1431 you may need to do this if you get unknown user in the following
1432 step. It never hurts to do it all the time. You may need to
1433 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1434 install) after the buildworld before this step if you last updated
1435 from current before 20130425 or from -stable before 20130430.
1437 [6] This only deletes old files and directories. Old libraries
1438 can be deleted by "make delete-old-libs", but you have to make
1439 sure that no program is using those libraries anymore.
1441 [8] In order to have a kernel that can run the 4.x binaries needed to
1442 do an installworld, you must include the COMPAT_FREEBSD4 option in
1443 your kernel. Failure to do so may leave you with a system that is
1444 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1445 required to run the 5.x binaries on more recent kernels. And so on
1446 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1448 Make sure that you merge any new devices from GENERIC since the
1449 last time you updated your kernel config file.
1451 [9] When checking out sources, you must include the -P flag to have
1452 cvs prune empty directories.
1454 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1455 "?=" instead of the "=" assignment operator, so that buildworld can
1456 override the CPUTYPE if it needs to.
1458 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1459 not on the command line, or in /etc/make.conf. buildworld will
1460 warn if it is improperly defined.
1463 This file contains a list, in reverse chronological order, of major
1464 breakages in tracking -current. It is not guaranteed to be a complete
1465 list of such breakages, and only contains entries since September 23, 2011.
1466 If you need to see UPDATING entries from before that date, you will need
1467 to fetch an UPDATING file from an older FreeBSD release.
1469 Copyright information:
1471 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1473 Redistribution, publication, translation and use, with or without
1474 modification, in full or in part, in any form or format of this
1475 document are permitted without further permission from the author.
1477 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1478 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1479 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1480 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1481 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1482 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1483 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1484 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1485 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1486 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1487 POSSIBILITY OF SUCH DAMAGE.
1489 Contact Warner Losh if you have any questions about your use of