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