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