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