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