1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW:
20 FreeBSD 11.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 The default configuration of ssh(1) no longer allows to use ssh-dss
36 keys. To enable using them, add 'ssh-dss' to PubkeyAcceptedKeyTypes
37 option in the /etc/ssh/ssh_config. Refer to ssh_config(5) for more
39 The NONE and HPN patches has been removed from OpenSSH. They are
40 still available in the security/openssh-portable port.
43 With the addition of ypldap(8), a new _ypldap user is now required
44 during installworld. "mergemaster -p" can be used to add the user
45 prior to installworld, as documented in the handbook.
48 The tftp loader (pxeboot) now uses the option root-path directive. As a
49 consequence it no longer looks for a pxeboot.4th file on the tftp
50 server. Instead it uses the regular /boot infrastructure as with the
54 The code to start recording plug and play data into the modules has
55 been committed. While the old tools will properly build a new kernel,
56 a number of warnings about "unknown metadata record 4" will be produced
57 for an older kldxref. To avoid such warnings, make sure to rebuild
58 the kernel toolchain (or world). Make sure that you have r292078 or
59 later when trying to build 292077 or later before rebuilding.
62 Debug data files are now built by default with 'make buildworld' and
63 installed with 'make installworld'. This facilitates debugging but
64 requires more disk space both during the build and for the installed
65 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
69 r291527 changed the internal interface between the nfsd.ko and
70 nfscommon.ko modules. As such, they must both be upgraded to-gether.
71 __FreeBSD_version has been bumped because of this.
74 Add support for unicode collation strings leads to a change of
75 order of files listed by ls(1) for example. To get back to the old
76 behaviour, set LC_COLLATE environment variable to "C".
78 Databases administrators will need to reindex their databases given
79 collation results will be different.
81 Due to a bug in install(1) it is recommended to remove the ancient
82 locales before running make installworld.
84 rm -rf /usr/share/locale/*
87 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
88 libcrypto.so.7 or libssl.so.7 must be recompiled.
91 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
92 Kernel modules isp_2400_multi and isp_2500_multi were removed and
93 should be replaced with isp_2400 and isp_2500 modules respectively.
96 The build previously allowed using 'make -n' to not recurse into
97 sub-directories while showing what commands would be executed, and
98 'make -n -n' to recursively show commands. Now 'make -n' will recurse
99 and 'make -N' will not.
102 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
103 and etcupdate will now use this file. A custom sendmail.cf is now
104 updated via this mechanism rather than via installworld. If you had
105 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
106 want to remove the exclusion or change it to "always install".
107 /etc/mail/sendmail.cf is now managed the same way regardless of
108 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
109 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
112 Compatibility shims for legacy ATA device names have been removed.
113 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
114 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
115 environment variables, /dev/ad* and /dev/ar* symbolic links.
118 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
119 Please see the 20141231 entry below for information about prerequisites
120 and upgrading, if you are not already using clang 3.5.0 or higher.
123 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
124 and renamed from .symbols to .debug. This reduces the size requirements
125 on the boot partition or file system and provides consistency with
126 userland debug files.
128 When using the supported kernel installation method the
129 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
130 as is done with /boot/kernel.
132 Developers wishing to maintain the historical behavior of installing
133 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
136 The wireless drivers had undergone changes that remove the 'parent
137 interface' from the ifconfig -l output. The rc.d network scripts
138 used to check presence of a parent interface in the list, so old
139 scripts would fail to start wireless networking. Thus, etcupdate(3)
140 or mergemaster(8) run is required after kernel update, to update your
141 rc.d scripts in /etc.
144 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
145 These configurations are now automatically interpreted as
146 'scrub fragment reassemble'.
149 Kernel-loadable modules for the random(4) device are back. To use
150 them, the kernel must have
153 options RANDOM_LOADABLE
155 kldload(8) can then be used to load random_fortuna.ko
156 or random_yarrow.ko. Please note that due to the indirect
157 function calls that the loadable modules need to provide,
158 the build-in variants will be slightly more efficient.
160 The random(4) kernel option RANDOM_DUMMY has been retired due to
161 unpopularity. It was not all that useful anyway.
164 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
165 Control over building the ELF Tool Chain tools is now provided by
166 the WITHOUT_TOOLCHAIN knob.
169 The polarity of Pulse Per Second (PPS) capture events with the
170 uart(4) driver has been corrected. Prior to this change the PPS
171 "assert" event corresponded to the trailing edge of a positive PPS
172 pulse and the "clear" event was the leading edge of the next pulse.
174 As the width of a PPS pulse in a typical GPS receiver is on the
175 order of 1 millisecond, most users will not notice any significant
176 difference with this change.
178 Anyone who has compensated for the historical polarity reversal by
179 configuring a negative offset equal to the pulse width will need to
180 remove that workaround.
183 The default group assigned to /dev/dri entries has been changed
184 from 'wheel' to 'video' with the id of '44'. If you want to have
185 access to the dri devices please add yourself to the video group
188 # pw groupmod video -m $USER
191 The menu.rc and loader.rc files will now be replaced during
192 upgrades. Please migrate local changes to menu.rc.local and
193 loader.rc.local instead.
196 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
197 strings and strip have been removed. The src.conf(5) knob
198 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
201 As ZFS requires more kernel stack pages than is the default on some
202 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
203 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
205 Please consider using 'options KSTACK_PAGES=X' where X is greater
206 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
209 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
210 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
211 default, i.e., they will not contain "::". For example, instead
212 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
213 to have a more specific match, such as different map entries for
214 IPv6:0:0 vs IPv6:0. This change requires that configuration
215 data (including maps, files, classes, custom ruleset, etc.) must
216 use the same format, so make certain such configuration data is
217 upgrading. As a very simple check search for patterns like
218 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
219 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
220 the cf option UseCompressedIPv6Addresses.
223 The default kernel entropy-processing algorithm is now
224 Fortuna, replacing Yarrow.
226 Assuming you have 'device random' in your kernel config
227 file, the configurations allow a kernel option to override
228 this default. You may choose *ONE* of:
230 options RANDOM_YARROW # Legacy /dev/random algorithm.
231 options RANDOM_DUMMY # Blocking-only driver.
233 If you have neither, you get Fortuna. For most people,
234 read no further, Fortuna will give a /dev/random that works
235 like it always used to, and the difference will be irrelevant.
237 If you remove 'device random', you get *NO* kernel-processed
238 entropy at all. This may be acceptable to folks building
239 embedded systems, but has complications. Carry on reading,
240 and it is assumed you know what you need.
242 *PLEASE* read random(4) and random(9) if you are in the
243 habit of tweaking kernel configs, and/or if you are a member
244 of the embedded community, wanting specific and not-usual
245 behaviour from your security subsystems.
247 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
248 random', you will NOT have a functioning /dev/random, and
249 many cryptographic features will not work, including SSH.
250 You may also find strange behaviour from the random(3) set
251 of library functions, in particular sranddev(3), srandomdev(3)
252 and arc4random(3). The reason for this is that the KERN_ARND
253 sysctl only returns entropy if it thinks it has some to
254 share, and with RANDOM_DUMMY or no 'device random' this
258 An additional fix for the issue described in the 20150614 sendmail
259 entry below has been been committed in revision 284717.
262 FreeBSD's old make (fmake) has been removed from the system. It is
263 available as the devel/fmake port or via pkg install fmake.
266 The fix for the issue described in the 20150614 sendmail entry
267 below has been been committed in revision 284436. The work
268 around described in that entry is no longer needed unless the
269 default setting is overridden by a confDH_PARAMETERS configuration
270 setting of '5' or pointing to a 512 bit DH parameter file.
273 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
274 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
275 and devel/kyua to version 0.20+ and adjust any calling code to work
276 with Kyuafile and kyua.
279 The import of openssl to address the FreeBSD-SA-15:10.openssl
280 security advisory includes a change which rejects handshakes
281 with DH parameters below 768 bits. sendmail releases prior
282 to 8.15.2 (not yet released), defaulted to a 512 bit
283 DH parameter setting for client connections. To work around
284 this interoperability, sendmail can be configured to use a
285 2048 bit DH parameter by:
287 1. Edit /etc/mail/`hostname`.mc
288 2. If a setting for confDH_PARAMETERS does not exist or
289 exists and is set to a string beginning with '5',
291 3. If a setting for confDH_PARAMETERS exists and is set to
292 a file path, create a new file with:
293 openssl dhparam -out /path/to/file 2048
294 4. Rebuild the .cf file:
295 cd /etc/mail/; make; make install
297 cd /etc/mail/; make restart
299 A sendmail patch is coming, at which time this file will be
303 Generation of legacy formatted entries have been disabled by default
304 in pwd_mkdb(8), as all base system consumers of the legacy formatted
305 entries were converted to use the new format by default when the new,
306 machine independent format have been added and supported since FreeBSD
309 Please see the pwd_mkdb(8) manual page for further details.
312 Clang and llvm have been upgraded to 3.6.1 release. Please see the
313 20141231 entry below for information about prerequisites and upgrading,
314 if you are not already using 3.5.0 or higher.
317 TI platform code switched to using vendor DTS files and this update
318 may break existing systems running on Beaglebone, Beaglebone Black,
321 - dtb files should be regenerated/reinstalled. Filenames are the
322 same but content is different now
323 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
324 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
325 addressing scheme is now pin 25 on /dev/gpioc3.
326 - Pandaboard: /etc/ttys should be updated, serial console device is
327 now /dev/ttyu2, not /dev/ttyu0
330 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
331 If you need the GNU extension from groff soelim(1), install groff
332 from package: pkg install groff, or via ports: textproc/groff.
335 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
336 defined in symlink(7); previously symlinks were silently ignored.
339 The const qualifier has been removed from iconv(3) to comply with
340 POSIX. The ports tree is aware of this from r384038 onwards.
343 Libraries specified by LIBADD in Makefiles must have a corresponding
344 DPADD_<lib> variable to ensure correct dependencies. This is now
345 enforced in src.libnames.mk.
348 From legacy ata(4) driver was removed support for SATA controllers
349 supported by more functional drivers ahci(4), siis(4) and mvs(4).
350 Kernel modules ataahci and ataadaptec were removed completely,
351 replaced by ahci and mvs modules respectively.
354 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
355 the 20141231 entry below for information about prerequisites and
356 upgrading, if you are not already using 3.5.0 or higher.
359 The 32-bit PowerPC kernel has been changed to a position-independent
360 executable. This can only be booted with a version of loader(8)
361 newer than January 31, 2015, so make sure to update both world and
362 kernel before rebooting.
365 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
366 but before r278950, the RNG was not seeded properly. Immediately
367 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
368 ssh keys or openssl keys) that were generated w/ a kernel from that
369 range. This does not affect programs that directly used /dev/random
370 or /dev/urandom. All userland uses of arc4random(3) are affected.
373 The autofs(4) ABI was changed in order to restore binary compatibility
374 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
378 The powerpc64 kernel has been changed to a position-independent
379 executable. This can only be booted with a new version of loader(8),
380 so make sure to update both world and kernel before rebooting.
383 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
384 only release, no new features have been added. Please see the 20141231
385 entry below for information about prerequisites and upgrading, if you
386 are not already using 3.5.0.
389 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
390 taken from the ELF Tool Chain project rather than GNU binutils. They
391 should be drop-in replacements, with the addition of arm64 support.
392 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
393 binutils tools, if necessary. See 20150805 for updated information.
396 The default Unbound configuration now enables remote control
397 using a local socket. Users who have already enabled the
398 local_unbound service should regenerate their configuration
399 by running "service local_unbound setup" as root.
402 The GNU texinfo and GNU info pages have been removed.
403 To be able to view GNU info pages please install texinfo from ports.
406 Clang, llvm and lldb have been upgraded to 3.5.0 release.
408 As of this release, a prerequisite for building clang, llvm and lldb is
409 a C++11 capable compiler and C++11 standard library. This means that to
410 be able to successfully build the cross-tools stage of buildworld, with
411 clang as the bootstrap compiler, your system compiler or cross compiler
412 should either be clang 3.3 or later, or gcc 4.8 or later, and your
413 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
416 On any standard FreeBSD 10.x or 11.x installation, where clang and
417 libc++ are on by default (that is, on x86 or arm), this should work out
420 On 9.x installations where clang is enabled by default, e.g. on x86 and
421 powerpc, libc++ will not be enabled by default, so libc++ should be
422 built (with clang) and installed first. If both clang and libc++ are
423 missing, build clang first, then use it to build libc++.
425 On 8.x and earlier installations, upgrade to 9.x first, and then follow
426 the instructions for 9.x above.
428 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
429 default, and do not build clang.
431 Many embedded systems are resource constrained, and will not be able to
432 build clang in a reasonable time, or in some cases at all. In those
433 cases, cross building bootable systems on amd64 is a workaround.
435 This new version of clang introduces a number of new warnings, of which
436 the following are most likely to appear:
440 This warns in two cases, for both C and C++:
441 * When the code is trying to take the absolute value of an unsigned
442 quantity, which is effectively a no-op, and almost never what was
443 intended. The code should be fixed, if at all possible. If you are
444 sure that the unsigned quantity can be safely cast to signed, without
445 loss of information or undefined behavior, you can add an explicit
446 cast, or disable the warning.
448 * When the code is trying to take an absolute value, but the called
449 abs() variant is for the wrong type, which can lead to truncation.
450 If you want to disable the warning instead of fixing the code, please
451 make sure that truncation will not occur, or it might lead to unwanted
454 -Wtautological-undefined-compare and
455 -Wundefined-bool-conversion
457 These warn when C++ code is trying to compare 'this' against NULL, while
458 'this' should never be NULL in well-defined C++ code. However, there is
459 some legacy (pre C++11) code out there, which actively abuses this
460 feature, which was less strictly defined in previous C++ versions.
462 Squid and openjdk do this, for example. The warning can be turned off
463 for C++98 and earlier, but compiling the code in C++11 mode might result
464 in unexpected behavior; for example, the parts of the program that are
465 unreachable could be optimized away.
468 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
469 kernel sources have been removed. The .h files remain, since some
470 utilities include them. This will need to be fixed later.
471 If "mount -t oldnfs ..." is attempted, it will fail.
472 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
473 the utilities will report errors.
476 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
477 directories to top level SUBDIR variable when their parent
478 directory is included in LOCAL_DIRS. Users with build systems with
479 such hierarchies and without SUBDIR entries in the parent
480 directory Makefiles should add them or add the directories to
484 faith(4) and faithd(8) have been removed from the base system. Faith
485 has been obsolete for a very long time.
488 vt(4), the new console driver, is enabled by default. It brings
489 support for Unicode and double-width characters, as well as
490 support for UEFI and integration with the KMS kernel video
493 You may need to update your console settings in /etc/rc.conf,
494 most probably the keymap. During boot, /etc/rc.d/syscons will
495 indicate what you need to do.
497 vt(4) still has issues and lacks some features compared to
498 syscons(4). See the wiki for up-to-date information:
499 https://wiki.freebsd.org/Newcons
501 If you want to keep using syscons(4), you can do so by adding
502 the following line to /boot/loader.conf:
506 pjdfstest has been integrated into kyua as an opt-in test suite.
507 Please see share/doc/pjdfstest/README for more details on how to
511 gperf has been removed from the base system for architectures
512 that use clang. Ports that require gperf will obtain it from the
516 pjdfstest has been moved from tools/regression/pjdfstest to
520 At svn r271982, The default linux compat kernel ABI has been adjusted
521 to 2.6.18 in support of the linux-c6 compat ports infrastructure
522 update. If you wish to continue using the linux-f10 compat ports,
523 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
524 encouraged to update their linux-compat packages to linux-c6 during
525 their next update cycle.
528 The ofwfb driver, used to provide a graphics console on PowerPC when
529 using vt(4), no longer allows mmap() of all physical memory. This
530 will prevent Xorg on PowerPC with some ATI graphics cards from
531 initializing properly unless x11-servers/xorg-server is updated to
535 The xdev targets have been converted to using TARGET and
536 TARGET_ARCH instead of XDEV and XDEV_ARCH.
539 The default unbound configuration has been modified to address
540 issues with reverse lookups on networks that use private
541 address ranges. If you use the local_unbound service, run
542 "service local_unbound setup" as root to regenerate your
543 configuration, then "service local_unbound reload" to load the
547 The GNU texinfo and GNU info pages are not built and installed
548 anymore, WITH_INFO knob has been added to allow to built and install
550 UPDATE: see 20150102 entry on texinfo's removal
553 The GNU readline library is now an INTERNALLIB - that is, it is
554 statically linked into consumers (GDB and variants) in the base
555 system, and the shared library is no longer installed. The
556 devel/readline port is available for third party software that
560 The Itanium architecture (ia64) has been removed from the list of
561 known architectures. This is the first step in the removal of the
565 Commit r268115 has added NFSv4.1 server support, merged from
566 projects/nfsv4.1-server. Since this includes changes to the
567 internal interfaces between the NFS related modules, a full
568 build of the kernel and modules will be necessary.
569 __FreeBSD_version has been bumped.
572 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
573 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
574 which differs from the behaviour controlled by this knob.)
577 Maximal length of the serial number in CTL was increased from 16 to
578 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
579 and ctld, need to be rebuilt to work with a new kernel.
582 The libatf-c and libatf-c++ major versions were downgraded to 0 and
583 1 respectively to match the upstream numbers. They were out of
584 sync because, when they were originally added to FreeBSD, the
585 upstream versions were not respected. These libraries are private
586 and not yet built by default, so renumbering them should be a
587 non-issue. However, unclean source trees will yield broken test
588 programs once the operator executes "make delete-old-libs" after a
591 Additionally, the atf-sh binary was made private by moving it into
592 /usr/libexec/. Already-built shell test programs will keep the
593 path to the old binary so they will break after "make delete-old"
596 If you are using WITH_TESTS=yes (not the default), wipe the object
597 tree and rebuild from scratch to prevent spurious test failures.
598 This is only needed once: the misnumbered libraries and misplaced
599 binaries have been added to OptionalObsoleteFiles.inc so they will
600 be removed during a clean upgrade.
603 Clang and llvm have been upgraded to 3.4.1 release.
606 We bogusly installed src.opts.mk in /usr/share/mk. This file should
607 be removed to avoid issues in the future (and has been added to
611 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
612 past, it affected all builds that used the bsd.*.mk files. The old
613 behavior was a bug, but people may have relied upon it. To get this
614 behavior back, you can .include /etc/src.conf from /etc/make.conf
615 (which is still global and isn't changed). This also changes the
616 behavior of incremental builds inside the tree of individual
617 directories. Set MAKESYSPATH to ".../share/mk" to do that.
618 Although this has survived make universe and some upgrade scenarios,
619 other upgrade scenarios may have broken. At least one form of
620 temporary breakage was fixed with MAKESYSPATH settings for buildworld
621 as well... In cases where MAKESYSPATH isn't working with this
622 setting, you'll need to set it to the full path to your tree.
624 One side effect of all this cleaning up is that bsd.compiler.mk
625 is no longer implicitly included by bsd.own.mk. If you wish to
626 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
630 The lindev device has been removed since /dev/full has been made a
631 standard device. __FreeBSD_version has been bumped.
634 The knob WITHOUT_VI was added to the base system, which controls
635 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
636 in order to reorder files share/termcap and didn't build ex(1) as a
637 build tool, so building/installing with WITH_VI is highly advised for
638 build hosts for older releases.
640 This issue has been fixed in stable/9 and stable/10 in r277022 and
641 r276991, respectively.
644 The YES_HESIOD knob has been removed. It has been obsolete for
645 a decade. Please move to using WITH_HESIOD instead or your builds
646 will silently lack HESIOD.
649 The uart(4) driver has been changed with respect to its handling
650 of the low-level console. Previously the uart(4) driver prevented
651 any process from changing the baudrate or the CLOCAL and HUPCL
652 control flags. By removing the restrictions, operators can make
653 changes to the serial console port without having to reboot.
654 However, when getty(8) is started on the serial device that is
655 associated with the low-level console, a misconfigured terminal
656 line in /etc/ttys will now have a real impact.
657 Before upgrading the kernel, make sure that /etc/ttys has the
658 serial console device configured as 3wire without baudrate to
659 preserve the previous behaviour. E.g:
660 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
663 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
664 to improve performance. To re-enable it, if needed, run rpcbind
665 with command line option -W.
668 Switched back to the GPL dtc compiler due to updates in the upstream
669 dts files not being supported by the BSDL dtc compiler. You will need
670 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
671 may result while building dtb files during a kernel build if you fail
672 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
675 Clang and llvm have been upgraded to 3.4 release.
678 The nve(4) driver has been removed. Please use the nfe(4) driver
679 for NVIDIA nForce MCP Ethernet adapters instead.
682 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
683 This could cause certain C++ applications using shared libraries built
684 against the previous version of libc++ to crash. The incompatibility
685 has now been fixed, but any C++ applications or shared libraries built
686 between r261283 and r261801 should be recompiled.
689 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
690 capability mode support. Please note that enabling the feature in
691 kernel is still highly recommended.
694 OpenSSH is now built with sandbox support, and will use sandbox as
695 the default privilege separation method. This requires Capsicum
696 capability mode support in kernel.
699 The libelf and libdwarf libraries have been updated to newer
700 versions from upstream. Shared library version numbers for
701 these two libraries were bumped. Any ports or binaries
702 requiring these two libraries should be recompiled.
703 __FreeBSD_version is bumped to 1100006.
706 If a Makefile in a tests/ directory was auto-generating a Kyuafile
707 instead of providing an explicit one, this would prevent such
708 Makefile from providing its own Kyuafile in the future during
709 NO_CLEAN builds. This has been fixed in the Makefiles but manual
710 intervention is needed to clean an objdir if you use NO_CLEAN:
711 # find /usr/obj -name Kyuafile | xargs rm -f
714 The behavior of gss_pseudo_random() for the krb5 mechanism
715 has changed, for applications requesting a longer random string
716 than produced by the underlying enctype's pseudo-random() function.
717 In particular, the random string produced from a session key of
718 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
719 be different at the 17th octet and later, after this change.
720 The counter used in the PRF+ construction is now encoded as a
721 big-endian integer in accordance with RFC 4402.
722 __FreeBSD_version is bumped to 1100004.
725 The WITHOUT_ATF build knob has been removed and its functionality
726 has been subsumed into the more generic WITHOUT_TESTS. If you were
727 using the former to disable the build of the ATF libraries, you
728 should change your settings to use the latter.
731 The default version of mtree is nmtree which is obtained from
732 NetBSD. The output is generally the same, but may vary
733 slightly. If you found you need identical output adding
734 "-F freebsd9" to the command line should do the trick. For the
735 time being, the old mtree is available as fmtree.
738 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
739 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
740 1.1.4_8 and verify bsdyml not linked in, before running "make
742 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
744 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
747 The stable/10 branch has been created in subversion from head
751 The rc.d/jail script has been updated to support jail(8)
752 configuration file. The "jail_<jname>_*" rc.conf(5) variables
753 for per-jail configuration are automatically converted to
754 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
755 This is transparently backward compatible. See below about some
756 incompatibilities and rc.conf(5) manual page for more details.
758 These variables are now deprecated in favor of jail(8) configuration
759 file. One can use "rc.d/jail config <jname>" command to generate
760 a jail(8) configuration file in /var/run/jail.<jname>.conf without
761 running the jail(8) utility. The default pathname of the
762 configuration file is /etc/jail.conf and can be specified by
763 using $jail_conf or $jail_<jname>_conf variables.
765 Please note that jail_devfs_ruleset accepts an integer at
766 this moment. Please consider to rewrite the ruleset name
770 BIND has been removed from the base system. If all you need
771 is a local resolver, simply enable and start the local_unbound
772 service instead. Otherwise, several versions of BIND are
773 available in the ports tree. The dns/bind99 port is one example.
775 With this change, nslookup(1) and dig(1) are no longer in the base
776 system. Users should instead use host(1) and drill(1) which are
777 in the base system. Alternatively, nslookup and dig can
778 be obtained by installing the dns/bind-tools port.
781 With the addition of unbound(8), a new unbound user is now
782 required during installworld. "mergemaster -p" can be used to
783 add the user prior to installworld, as documented in the handbook.
786 OpenSSH is now built with DNSSEC support, and will by default
787 silently trust signed SSHFP records. This can be controlled with
788 the VerifyHostKeyDNS client configuration setting. DNSSEC support
789 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
792 The GNU Compiler Collection and C++ standard library (libstdc++)
793 are no longer built by default on platforms where clang is the system
794 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
798 The PROCDESC kernel option is now part of the GENERIC kernel
799 configuration and is required for the rwhod(8) to work.
800 If you are using custom kernel configuration, you should include
804 The API and ABI related to the Capsicum framework was modified
805 in backward incompatible way. The userland libraries and programs
806 have to be recompiled to work with the new kernel. This includes the
807 following libraries and programs, but the whole buildworld is
808 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
809 kdump, procstat, rwho, rwhod, uniq.
812 AES-NI intrinsic support has been added to gcc. The AES-NI module
813 has been updated to use this support. A new gcc is required to build
814 the aesni module on both i386 and amd64.
817 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
818 Thus "device padlock_rng" and "device rdrand_rng" should be
819 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
822 WITH_ICONV has been split into two feature sets. WITH_ICONV now
823 enables just the iconv* functionality and is now on by default.
824 WITH_LIBICONV_COMPAT enables the libiconv api and link time
825 compatability. Set WITHOUT_ICONV to build the old way.
826 If you have been using WITH_ICONV before, you will very likely
827 need to turn on WITH_LIBICONV_COMPAT.
830 INVARIANTS option now enables DEBUG for code with OpenSolaris and
831 Illumos origin, including ZFS. If you have INVARIANTS in your
832 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
834 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
835 locks if WITNESS option was set. Because that generated a lot of
836 witness(9) reports and all of them were believed to be false
837 positives, this is no longer done. New option OPENSOLARIS_WITNESS
838 can be used to achieve the previous behavior.
841 Timer values in IPv6 data structures now use time_uptime instead
842 of time_second. Although this is not a user-visible functional
843 change, userland utilities which directly use them---ndp(8),
844 rtadvd(8), and rtsold(8) in the base system---need to be updated
848 find -delete can now delete the pathnames given as arguments,
849 instead of only files found below them or if the pathname did
850 not contain any slashes. Formerly, the following error message
853 find: -delete: <path>: relative path potentially not safe
855 Deleting the pathnames given as arguments can be prevented
856 without error messages using -mindepth 1 or by changing
857 directory and passing "." as argument to find. This works in the
858 old as well as the new version of find.
861 Behavior of devfs rules path matching has been changed.
862 Pattern is now always matched against fully qualified devfs
863 path and slash characters must be explicitly matched by
864 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
865 subdirectories must be reviewed.
868 The default ARM ABI has changed to the ARM EABI. The old ABI is
869 incompatible with the ARM EABI and all programs and modules will
870 need to be rebuilt to work with a new kernel.
872 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
874 NOTE: Support for the old ABI will be removed in the future and
875 users are advised to upgrade.
878 pkg_install has been disconnected from the build if you really need it
879 you should add WITH_PKGTOOLS in your src.conf(5).
882 Most of network statistics structures were changed to be able
883 keep 64-bits counters. Thus all tools, that work with networking
884 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
887 Fix a bug that allowed a tracing process (e.g. gdb) to write
888 to a memory-mapped file in the traced process's address space
889 even if neither the traced process nor the tracing process had
890 write access to that file.
893 CVS has been removed from the base system. An exact copy
894 of the code is available from the devel/cvs port.
897 Some people report the following error after the switch to bmake:
899 make: illegal option -- J
900 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
902 *** [buildworld] Error code 2
904 this likely due to an old instance of make in
905 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
906 which src/Makefile will use that blindly, if it exists, so if
907 you see the above error:
909 rm -rf `make -V MAKEPATH`
914 Use bmake by default.
915 Whereas before one could choose to build with bmake via
916 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
917 make. The goal is to remove these knobs for 10-RELEASE.
919 It is worth noting that bmake (like gmake) treats the command
920 line as the unit of failure, rather than statements within the
921 command line. Thus '(cd some/where && dosomething)' is safer
922 than 'cd some/where; dosomething'. The '()' allows consistent
923 behavior in parallel build.
926 Fix a bug that allows NFS clients to issue READDIR on files.
929 The WITHOUT_IDEA option has been removed because
930 the IDEA patent expired.
933 The sysctl which controls TRIM support under ZFS has been renamed
934 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
938 The mergemaster command now uses the default MAKEOBJDIRPREFIX
939 rather than creating it's own in the temporary directory in
940 order allow access to bootstrapped versions of tools such as
941 install and mtree. When upgrading from version of FreeBSD where
942 the install command does not support -l, you will need to
943 install a new mergemaster command if mergemaster -p is required.
944 This can be accomplished with the command (cd src/usr.sbin/mergemaster
948 Legacy ATA stack, disabled and replaced by new CAM-based one since
949 FreeBSD 9.0, completely removed from the sources. Kernel modules
950 atadisk and atapi*, user-level tools atacontrol and burncd are
951 removed. Kernel option `options ATA_CAM` is now permanently enabled
955 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
956 and socketpair(2). Software, in particular Kerberos, may
957 automatically detect and use these during building. The resulting
958 binaries will not work on older kernels.
961 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
962 information, see the respective 20130304 entry).
965 Recent commits to callout(9) changed the size of struct callout,
966 so the KBI is probably heavily disturbed. Also, some functions
967 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
968 by macros. Every kernel module using it won't load, so rebuild
971 The ctl device has been re-enabled in GENERIC for i386 and amd64,
972 but does not initialize by default (because of the new CTL_DISABLE
973 option) to save memory. To re-enable it, remove the CTL_DISABLE
974 option from the kernel config file or set kern.cam.ctl.disable=0
975 in /boot/loader.conf.
978 The ctl device has been disabled in GENERIC for i386 and amd64.
979 This was done due to the extra memory being allocated at system
980 initialisation time by the ctl driver which was only used if
981 a CAM target device was created. This makes a FreeBSD system
982 unusable on 128MB or less of RAM.
985 A new compression method (lz4) has been merged to -HEAD. Please
986 refer to zpool-features(7) for more information.
988 Please refer to the "ZFS notes" section of this file for information
989 on upgrading boot ZFS pools.
992 A BSD-licensed patch(1) variant has been added and is installed
993 as bsdpatch, being the GNU version the default patch.
994 To inverse the logic and use the BSD-licensed one as default,
995 while having the GNU version installed as gnupatch, rebuild
996 and install world with the WITH_BSD_PATCH knob set.
999 Due to the use of the new -l option to install(1) during build
1000 and install, you must take care not to directly set the INSTALL
1001 make variable in your /etc/make.conf, /etc/src.conf, or on the
1002 command line. If you wish to use the -C flag for all installs
1003 you may be able to add INSTALL+=-C to /etc/make.conf or
1007 The install(1) option -M has changed meaning and now takes an
1008 argument that is a file or path to append logs to. In the
1009 unlikely event that -M was the last option on the command line
1010 and the command line contained at least two files and a target
1011 directory the first file will have logs appended to it. The -M
1012 option served little practical purpose in the last decade so its
1013 use is expected to be extremely rare.
1016 After switching to Clang as the default compiler some users of ZFS
1017 on i386 systems started to experience stack overflow kernel panics.
1018 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1021 GEOM_LABEL now mangles label names read from file system metadata.
1022 Mangling affect labels containing spaces, non-printable characters,
1023 '%' or '"'. Device names in /etc/fstab and other places may need to
1027 By default, only the 10 most recent kernel dumps will be saved. To
1028 restore the previous behaviour (no limit on the number of kernel dumps
1029 stored in the dump directory) add the following line to /etc/rc.conf:
1034 With the addition of auditdistd(8), a new auditdistd user is now
1035 required during installworld. "mergemaster -p" can be used to
1036 add the user prior to installworld, as documented in the handbook.
1039 The sin6_scope_id member variable in struct sockaddr_in6 is now
1040 filled by the kernel before passing the structure to the userland via
1041 sysctl or routing socket. This means the KAME-specific embedded scope
1042 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1043 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1044 __FreeBSD_version is bumped to 1000025.
1047 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1048 This means that the world and kernel will be compiled with clang
1049 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1050 and /usr/bin/cpp. To disable this behavior and revert to building
1051 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1052 of current may need to bootstrap WITHOUT_CLANG first if the clang
1053 build fails (its compatibility window doesn't extend to the 9 stable
1057 The IPFIREWALL_FORWARD kernel option has been removed. Its
1058 functionality now turned on by default.
1061 The ZERO_COPY_SOCKET kernel option has been removed and
1062 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1063 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1064 mechanism which is not safe and may result in kernel crashes.
1065 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1066 driver supports disposeable external page sized mbuf storage.
1067 Proper replacements for both zero-copy mechanisms are under
1068 consideration and will eventually lead to complete removal
1069 of the two kernel options.
1072 The IPv4 network stack has been converted to network byte
1073 order. The following modules need to be recompiled together
1074 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1075 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1078 Support for non-MPSAFE filesystems was removed from VFS. The
1079 VFS_VERSION was bumped, all filesystem modules shall be
1083 All the non-MPSAFE filesystems have been disconnected from
1084 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1085 portalfs, smbfs, xfs.
1088 The interface cloning API and ABI has changed. The following
1089 modules need to be recompiled together with kernel:
1090 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1091 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1092 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1095 The sdhci driver was split in two parts: sdhci (generic SD Host
1096 Controller logic) and sdhci_pci (actual hardware driver).
1097 No kernel config modifications are required, but if you
1098 load sdhc as a module you must switch to sdhci_pci instead.
1101 Import the FUSE kernel and userland support into base system.
1104 The GNU sort(1) program has been removed since the BSD-licensed
1105 sort(1) has been the default for quite some time and no serious
1106 problems have been reported. The corresponding WITH_GNU_SORT
1110 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1111 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1115 The net80211(4) ABI has been changed to allow for improved driver
1116 PS-POLL and power-save support. All wireless drivers need to be
1117 recompiled to work with the new kernel.
1120 The random(4) support for the VIA hardware random number
1121 generator (`PADLOCK') is no longer enabled unconditionally.
1122 Add the padlock_rng device in the custom kernel config if
1123 needed. The GENERIC kernels on i386 and amd64 do include the
1124 device, so the change only affects the custom kernel
1128 The pf(4) packet filter ABI has been changed. pfctl(8) and
1129 snmp_pf module need to be recompiled to work with new kernel.
1132 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1133 to -HEAD. Pools that have empty_bpobj in active state can not be
1134 imported read-write with ZFS implementations that do not support
1135 this feature. For more information read the zpool-features(5)
1139 The sparc64 ZFS loader has been changed to no longer try to auto-
1140 detect ZFS providers based on diskN aliases but now requires these
1141 to be explicitly listed in the OFW boot-device environment variable.
1144 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1145 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1146 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1149 The following sysctls and tunables have been renamed for consistency
1150 with other variables:
1151 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1152 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1155 The sort utility has been replaced with BSD sort. For now, GNU sort
1156 is also available as "gnusort" or the default can be set back to
1157 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1158 installed as "bsdsort".
1161 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1162 Starting with this version the old system of ZFS pool versioning
1163 is superseded by "feature flags". This concept enables forward
1164 compatibility against certain future changes in functionality of ZFS
1165 pools. The first read-only compatible "feature flag" for ZFS pools
1166 is named "com.delphix:async_destroy". For more information
1167 read the new zpool-features(5) manual page.
1168 Please refer to the "ZFS notes" section of this file for information
1169 on upgrading boot ZFS pools.
1172 The malloc(3) implementation embedded in libc now uses sources imported
1173 as contrib/jemalloc. The most disruptive API change is to
1174 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1175 delete it prior to installworld, and optionally re-create it using the
1176 new format after rebooting. See malloc.conf(5) for details
1177 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1181 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1182 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1183 now spelled mips. This is to aid compatibility with third-party
1184 software that expects this naming scheme in uname(3). Little-endian
1185 settings are unchanged. If you are updating a big-endian mips64 machine
1186 from before this change, you may need to set MACHINE_ARCH=mips64 in
1187 your environment before the new build system will recognize your machine.
1190 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1194 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1195 nullfs(5) did not pass through all behaviours to the underlying layer,
1196 as a result if we bound to a socket on the lower layer we could connect
1197 only to the lower path; if we bound to the upper layer we could connect
1198 only to the upper path. The new behavior is one can connect to both the
1199 lower and the upper paths regardless what layer path one binds to.
1202 The getifaddrs upgrade path broken with 20111215 has been restored.
1203 If you have upgraded in between 20111215 and 20120209 you need to
1204 recompile libc again with your kernel. You still need to recompile
1205 world to be able to configure CARP but this restriction already
1206 comes from 20111215.
1209 The set_rcvar() function has been removed from /etc/rc.subr. All
1210 base and ports rc.d scripts have been updated, so if you have a
1211 port installed with a script in /usr/local/etc/rc.d you can either
1212 hand-edit the rcvar= line, or reinstall the port.
1214 An easy way to handle the mass-update of /etc/rc.d:
1215 rm /etc/rc.d/* && mergemaster -i
1218 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1219 on the current CPU and prevents other threads from running.
1220 This behavior can be reverted using the kern.stop_scheduler_on_panic
1222 The new behavior can be incompatible with kern.sync_on_panic.
1225 The carp(4) facility has been changed significantly. Configuration
1226 of the CARP protocol via ifconfig(8) has changed, as well as format
1227 of CARP events submitted to devd(8) has changed. See manual pages
1228 for more information. The arpbalance feature of carp(4) is currently
1229 not supported anymore.
1231 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1232 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1233 need to be recompiled.
1236 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1240 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1241 explicitely support non-MPSAFE filesystems.
1242 It is on by default for all supported platform at this present
1246 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1247 i386 and pc98 GENERIC kernel configuration files.
1250 sysinstall has been removed
1253 The stable/9 branch created in subversion. This corresponds to the
1254 RELENG_9 branch in CVS.
1260 Avoid using make -j when upgrading. While generally safe, there are
1261 sometimes problems using -j to upgrade. If your upgrade fails with
1262 -j, please try again without -j. From time to time in the past there
1263 have been problems using -j with buildworld and/or installworld. This
1264 is especially true when upgrading between "distant" versions (eg one
1265 that cross a major release boundary or several minor releases, or when
1266 several months have passed on the -current branch).
1268 Sometimes, obscure build problems are the result of environment
1269 poisoning. This can happen because the make utility reads its
1270 environment when searching for values for global variables. To run
1271 your build attempts in an "environmental clean room", prefix all make
1272 commands with 'env -i '. See the env(1) manual page for more details.
1274 When upgrading from one major version to another it is generally best
1275 to upgrade to the latest code in the currently installed branch first,
1276 then do an upgrade to the new branch. This is the best-tested upgrade
1277 path, and has the highest probability of being successful. Please try
1278 this approach before reporting problems with a major version upgrade.
1280 When upgrading a live system, having a root shell around before
1281 installing anything can help undo problems. Not having a root shell
1282 around can lead to problems if pam has changed too much from your
1283 starting point to allow continued authentication after the upgrade.
1285 This file should be read as a log of events. When a later event changes
1286 information of a prior event, the prior event should not be deleted.
1287 Instead, a pointer to the entry with the new information should be
1288 placed in the old entry. Readers of this file should also sanity check
1289 older entries before relying on them blindly. Authors of new entries
1290 should write them with this in mind.
1294 When upgrading the boot ZFS pool to a new version, always follow
1297 1.) recompile and reinstall the ZFS boot loader and boot block
1298 (this is part of "make buildworld" and "make installworld")
1300 2.) update the ZFS boot block on your boot drive
1302 The following example updates the ZFS boot block on the first
1303 partition (freebsd-boot) of a GPT partitioned drive ada0:
1304 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1306 Non-boot pools do not need these updates.
1310 If you are updating from a prior version of FreeBSD (even one just
1311 a few days old), you should follow this procedure. It is the most
1312 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1314 make kernel-toolchain
1315 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1316 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1318 To test a kernel once
1319 ---------------------
1320 If you just want to boot a kernel once (because you are not sure
1321 if it works, or if you want to boot a known bad kernel to provide
1322 debugging information) run
1323 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1324 nextboot -k testkernel
1326 To just build a kernel when you know that it won't mess you up
1327 --------------------------------------------------------------
1328 This assumes you are already running a CURRENT system. Replace
1329 ${arch} with the architecture of your machine (e.g. "i386",
1330 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1332 cd src/sys/${arch}/conf
1333 config KERNEL_NAME_HERE
1334 cd ../compile/KERNEL_NAME_HERE
1339 If this fails, go to the "To build a kernel" section.
1341 To rebuild everything and install it on the current system.
1342 -----------------------------------------------------------
1343 # Note: sometimes if you are running current you gotta do more than
1344 # is listed here if you are upgrading from a really old current.
1346 <make sure you have good level 0 dumps>
1348 make kernel KERNCONF=YOUR_KERNEL_HERE
1350 <reboot in single user> [3]
1357 To cross-install current onto a separate partition
1358 --------------------------------------------------
1359 # In this approach we use a separate partition to hold
1360 # current's root, 'usr', and 'var' directories. A partition
1361 # holding "/", "/usr" and "/var" should be about 2GB in
1364 <make sure you have good level 0 dumps>
1367 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1368 <maybe newfs current's root partition>
1369 <mount current's root partition on directory ${CURRENT_ROOT}>
1370 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1371 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1372 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1373 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1374 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1375 <reboot into current>
1376 <do a "native" rebuild/install as described in the previous section>
1377 <maybe install compatibility libraries from ports/misc/compat*>
1381 To upgrade in-place from stable to current
1382 ----------------------------------------------
1383 <make sure you have good level 0 dumps>
1385 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1387 <reboot in single user> [3]
1394 Make sure that you've read the UPDATING file to understand the
1395 tweaks to various things you need. At this point in the life
1396 cycle of current, things change often and you are on your own
1397 to cope. The defaults can also change, so please read ALL of
1398 the UPDATING entries.
1400 Also, if you are tracking -current, you must be subscribed to
1401 freebsd-current@freebsd.org. Make sure that before you update
1402 your sources that you have read and understood all the recent
1403 messages there. If in doubt, please track -stable which has
1404 much fewer pitfalls.
1406 [1] If you have third party modules, such as vmware, you
1407 should disable them at this point so they don't crash your
1410 [3] From the bootblocks, boot -s, and then do
1415 adjkerntz -i # if CMOS is wall time
1416 Also, when doing a major release upgrade, it is required that
1417 you boot into single user mode to do the installworld.
1419 [4] Note: This step is non-optional. Failure to do this step
1420 can result in a significant reduction in the functionality of the
1421 system. Attempting to do it by hand is not recommended and those
1422 that pursue this avenue should read this file carefully, as well
1423 as the archives of freebsd-current and freebsd-hackers mailing lists
1424 for potential gotchas. The -U option is also useful to consider.
1425 See mergemaster(8) for more information.
1427 [5] Usually this step is a noop. However, from time to time
1428 you may need to do this if you get unknown user in the following
1429 step. It never hurts to do it all the time. You may need to
1430 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1431 install) after the buildworld before this step if you last updated
1432 from current before 20130425 or from -stable before 20130430.
1434 [6] This only deletes old files and directories. Old libraries
1435 can be deleted by "make delete-old-libs", but you have to make
1436 sure that no program is using those libraries anymore.
1438 [8] In order to have a kernel that can run the 4.x binaries needed to
1439 do an installworld, you must include the COMPAT_FREEBSD4 option in
1440 your kernel. Failure to do so may leave you with a system that is
1441 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1442 required to run the 5.x binaries on more recent kernels. And so on
1443 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1445 Make sure that you merge any new devices from GENERIC since the
1446 last time you updated your kernel config file.
1448 [9] When checking out sources, you must include the -P flag to have
1449 cvs prune empty directories.
1451 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1452 "?=" instead of the "=" assignment operator, so that buildworld can
1453 override the CPUTYPE if it needs to.
1455 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1456 not on the command line, or in /etc/make.conf. buildworld will
1457 warn if it is improperly defined.
1460 This file contains a list, in reverse chronological order, of major
1461 breakages in tracking -current. It is not guaranteed to be a complete
1462 list of such breakages, and only contains entries since September 23, 2011.
1463 If you need to see UPDATING entries from before that date, you will need
1464 to fetch an UPDATING file from an older FreeBSD release.
1466 Copyright information:
1468 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1470 Redistribution, publication, translation and use, with or without
1471 modification, in full or in part, in any form or format of this
1472 document are permitted without further permission from the author.
1474 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1475 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1476 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1477 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1478 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1479 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1480 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1481 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1482 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1483 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1484 POSSIBILITY OF SUCH DAMAGE.
1486 Contact Warner Losh if you have any questions about your use of