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 CAM I/O scheduler has been committed to the kernel. There should
36 be no user visible impact. This does enable NCQ Trim on ada
37 SSDs. While the list of known rogues that claim support for
38 this but actually corrupt data is believed to be complete, be
39 on the lookout for data corruption.
42 The FAST_DEPEND build option has been removed and its functionality is
43 now the one true way. The old mkdep(1) style of 'make depend' has
44 been removed. See 20160311 for further details.
47 Resource range types have grown from unsigned long to uintmax_t. All
48 drivers, and anything using libdevinfo, need to be recompiled.
51 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
52 builds. It no longer runs mkdep(1) during 'make depend', and the
53 'make depend' stage can safely be skipped now as it is auto ran
54 when building 'make all' and will generate all SRCS and DPSRCS before
55 building anything else. Dependencies are gathered at compile time with
56 -MF flags kept in separate .depend files per object file. Users should
57 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
61 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
62 kernel modules. Therefore, if you load any kernel modules at boot time,
63 please install the boot loaders after you install the kernel, but before
67 make kernel KERNCONF=YOUR_KERNEL_HERE
68 make -C sys/boot install
69 <reboot in single user>
71 Then follow the usual steps, described in the General Notes section,
75 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
76 see the 20141231 entry below for information about prerequisites and
77 upgrading, if you are not already using clang 3.5.0 or higher.
80 The AIO subsystem is now a standard part of the kernel. The
81 VFS_AIO kernel option and aio.ko kernel module have been removed.
82 Due to stability concerns, asynchronous I/O requests are only
83 permitted on sockets and raw disks by default. To enable
84 asynchronous I/O requests on all file types, set the
85 vfs.aio.enable_unsafe sysctl to a non-zero value.
88 The ELF object manipulation tool objcopy is now provided by the
89 ELF Tool Chain project rather than by GNU binutils. It should be a
90 drop-in replacement, with the addition of arm64 support. The
91 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
92 to obtain the GNU version if necessary.
95 Building ZFS pools on top of zvols is prohibited by default. That
96 feature has never worked safely; it's always been prone to deadlocks.
97 Using a zvol as the backing store for a VM guest's virtual disk will
98 still work, even if the guest is using ZFS. Legacy behavior can be
99 restored by setting vfs.zfs.vol.recursive=1.
102 The NONE and HPN patches has been removed from OpenSSH. They are
103 still available in the security/openssh-portable port.
106 With the addition of ypldap(8), a new _ypldap user is now required
107 during installworld. "mergemaster -p" can be used to add the user
108 prior to installworld, as documented in the handbook.
111 The tftp loader (pxeboot) now uses the option root-path directive. As a
112 consequence it no longer looks for a pxeboot.4th file on the tftp
113 server. Instead it uses the regular /boot infrastructure as with the
117 The code to start recording plug and play data into the modules has
118 been committed. While the old tools will properly build a new kernel,
119 a number of warnings about "unknown metadata record 4" will be produced
120 for an older kldxref. To avoid such warnings, make sure to rebuild
121 the kernel toolchain (or world). Make sure that you have r292078 or
122 later when trying to build 292077 or later before rebuilding.
125 Debug data files are now built by default with 'make buildworld' and
126 installed with 'make installworld'. This facilitates debugging but
127 requires more disk space both during the build and for the installed
128 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
132 r291527 changed the internal interface between the nfsd.ko and
133 nfscommon.ko modules. As such, they must both be upgraded to-gether.
134 __FreeBSD_version has been bumped because of this.
137 Add support for unicode collation strings leads to a change of
138 order of files listed by ls(1) for example. To get back to the old
139 behaviour, set LC_COLLATE environment variable to "C".
141 Databases administrators will need to reindex their databases given
142 collation results will be different.
144 Due to a bug in install(1) it is recommended to remove the ancient
145 locales before running make installworld.
147 rm -rf /usr/share/locale/*
150 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
151 libcrypto.so.7 or libssl.so.7 must be recompiled.
154 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
155 Kernel modules isp_2400_multi and isp_2500_multi were removed and
156 should be replaced with isp_2400 and isp_2500 modules respectively.
159 The build previously allowed using 'make -n' to not recurse into
160 sub-directories while showing what commands would be executed, and
161 'make -n -n' to recursively show commands. Now 'make -n' will recurse
162 and 'make -N' will not.
165 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
166 and etcupdate will now use this file. A custom sendmail.cf is now
167 updated via this mechanism rather than via installworld. If you had
168 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
169 want to remove the exclusion or change it to "always install".
170 /etc/mail/sendmail.cf is now managed the same way regardless of
171 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
172 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
175 Compatibility shims for legacy ATA device names have been removed.
176 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
177 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
178 environment variables, /dev/ad* and /dev/ar* symbolic links.
181 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
182 Please see the 20141231 entry below for information about prerequisites
183 and upgrading, if you are not already using clang 3.5.0 or higher.
186 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
187 and renamed from .symbols to .debug. This reduces the size requirements
188 on the boot partition or file system and provides consistency with
189 userland debug files.
191 When using the supported kernel installation method the
192 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
193 as is done with /boot/kernel.
195 Developers wishing to maintain the historical behavior of installing
196 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
199 The wireless drivers had undergone changes that remove the 'parent
200 interface' from the ifconfig -l output. The rc.d network scripts
201 used to check presence of a parent interface in the list, so old
202 scripts would fail to start wireless networking. Thus, etcupdate(3)
203 or mergemaster(8) run is required after kernel update, to update your
204 rc.d scripts in /etc.
207 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
208 These configurations are now automatically interpreted as
209 'scrub fragment reassemble'.
212 Kernel-loadable modules for the random(4) device are back. To use
213 them, the kernel must have
216 options RANDOM_LOADABLE
218 kldload(8) can then be used to load random_fortuna.ko
219 or random_yarrow.ko. Please note that due to the indirect
220 function calls that the loadable modules need to provide,
221 the build-in variants will be slightly more efficient.
223 The random(4) kernel option RANDOM_DUMMY has been retired due to
224 unpopularity. It was not all that useful anyway.
227 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
228 Control over building the ELF Tool Chain tools is now provided by
229 the WITHOUT_TOOLCHAIN knob.
232 The polarity of Pulse Per Second (PPS) capture events with the
233 uart(4) driver has been corrected. Prior to this change the PPS
234 "assert" event corresponded to the trailing edge of a positive PPS
235 pulse and the "clear" event was the leading edge of the next pulse.
237 As the width of a PPS pulse in a typical GPS receiver is on the
238 order of 1 millisecond, most users will not notice any significant
239 difference with this change.
241 Anyone who has compensated for the historical polarity reversal by
242 configuring a negative offset equal to the pulse width will need to
243 remove that workaround.
246 The default group assigned to /dev/dri entries has been changed
247 from 'wheel' to 'video' with the id of '44'. If you want to have
248 access to the dri devices please add yourself to the video group
251 # pw groupmod video -m $USER
254 The menu.rc and loader.rc files will now be replaced during
255 upgrades. Please migrate local changes to menu.rc.local and
256 loader.rc.local instead.
259 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
260 strings and strip have been removed. The src.conf(5) knob
261 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
264 As ZFS requires more kernel stack pages than is the default on some
265 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
266 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
268 Please consider using 'options KSTACK_PAGES=X' where X is greater
269 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
272 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
273 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
274 default, i.e., they will not contain "::". For example, instead
275 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
276 to have a more specific match, such as different map entries for
277 IPv6:0:0 vs IPv6:0. This change requires that configuration
278 data (including maps, files, classes, custom ruleset, etc.) must
279 use the same format, so make certain such configuration data is
280 upgrading. As a very simple check search for patterns like
281 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
282 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
283 the cf option UseCompressedIPv6Addresses.
286 The default kernel entropy-processing algorithm is now
287 Fortuna, replacing Yarrow.
289 Assuming you have 'device random' in your kernel config
290 file, the configurations allow a kernel option to override
291 this default. You may choose *ONE* of:
293 options RANDOM_YARROW # Legacy /dev/random algorithm.
294 options RANDOM_DUMMY # Blocking-only driver.
296 If you have neither, you get Fortuna. For most people,
297 read no further, Fortuna will give a /dev/random that works
298 like it always used to, and the difference will be irrelevant.
300 If you remove 'device random', you get *NO* kernel-processed
301 entropy at all. This may be acceptable to folks building
302 embedded systems, but has complications. Carry on reading,
303 and it is assumed you know what you need.
305 *PLEASE* read random(4) and random(9) if you are in the
306 habit of tweaking kernel configs, and/or if you are a member
307 of the embedded community, wanting specific and not-usual
308 behaviour from your security subsystems.
310 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
311 random', you will NOT have a functioning /dev/random, and
312 many cryptographic features will not work, including SSH.
313 You may also find strange behaviour from the random(3) set
314 of library functions, in particular sranddev(3), srandomdev(3)
315 and arc4random(3). The reason for this is that the KERN_ARND
316 sysctl only returns entropy if it thinks it has some to
317 share, and with RANDOM_DUMMY or no 'device random' this
321 An additional fix for the issue described in the 20150614 sendmail
322 entry below has been been committed in revision 284717.
325 FreeBSD's old make (fmake) has been removed from the system. It is
326 available as the devel/fmake port or via pkg install fmake.
329 The fix for the issue described in the 20150614 sendmail entry
330 below has been been committed in revision 284436. The work
331 around described in that entry is no longer needed unless the
332 default setting is overridden by a confDH_PARAMETERS configuration
333 setting of '5' or pointing to a 512 bit DH parameter file.
336 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
337 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
338 and devel/kyua to version 0.20+ and adjust any calling code to work
339 with Kyuafile and kyua.
342 The import of openssl to address the FreeBSD-SA-15:10.openssl
343 security advisory includes a change which rejects handshakes
344 with DH parameters below 768 bits. sendmail releases prior
345 to 8.15.2 (not yet released), defaulted to a 512 bit
346 DH parameter setting for client connections. To work around
347 this interoperability, sendmail can be configured to use a
348 2048 bit DH parameter by:
350 1. Edit /etc/mail/`hostname`.mc
351 2. If a setting for confDH_PARAMETERS does not exist or
352 exists and is set to a string beginning with '5',
354 3. If a setting for confDH_PARAMETERS exists and is set to
355 a file path, create a new file with:
356 openssl dhparam -out /path/to/file 2048
357 4. Rebuild the .cf file:
358 cd /etc/mail/; make; make install
360 cd /etc/mail/; make restart
362 A sendmail patch is coming, at which time this file will be
366 Generation of legacy formatted entries have been disabled by default
367 in pwd_mkdb(8), as all base system consumers of the legacy formatted
368 entries were converted to use the new format by default when the new,
369 machine independent format have been added and supported since FreeBSD
372 Please see the pwd_mkdb(8) manual page for further details.
375 Clang and llvm have been upgraded to 3.6.1 release. Please see the
376 20141231 entry below for information about prerequisites and upgrading,
377 if you are not already using 3.5.0 or higher.
380 TI platform code switched to using vendor DTS files and this update
381 may break existing systems running on Beaglebone, Beaglebone Black,
384 - dtb files should be regenerated/reinstalled. Filenames are the
385 same but content is different now
386 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
387 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
388 addressing scheme is now pin 25 on /dev/gpioc3.
389 - Pandaboard: /etc/ttys should be updated, serial console device is
390 now /dev/ttyu2, not /dev/ttyu0
393 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
394 If you need the GNU extension from groff soelim(1), install groff
395 from package: pkg install groff, or via ports: textproc/groff.
398 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
399 defined in symlink(7); previously symlinks were silently ignored.
402 The const qualifier has been removed from iconv(3) to comply with
403 POSIX. The ports tree is aware of this from r384038 onwards.
406 Libraries specified by LIBADD in Makefiles must have a corresponding
407 DPADD_<lib> variable to ensure correct dependencies. This is now
408 enforced in src.libnames.mk.
411 From legacy ata(4) driver was removed support for SATA controllers
412 supported by more functional drivers ahci(4), siis(4) and mvs(4).
413 Kernel modules ataahci and ataadaptec were removed completely,
414 replaced by ahci and mvs modules respectively.
417 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
418 the 20141231 entry below for information about prerequisites and
419 upgrading, if you are not already using 3.5.0 or higher.
422 The 32-bit PowerPC kernel has been changed to a position-independent
423 executable. This can only be booted with a version of loader(8)
424 newer than January 31, 2015, so make sure to update both world and
425 kernel before rebooting.
428 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
429 but before r278950, the RNG was not seeded properly. Immediately
430 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
431 ssh keys or openssl keys) that were generated w/ a kernel from that
432 range. This does not affect programs that directly used /dev/random
433 or /dev/urandom. All userland uses of arc4random(3) are affected.
436 The autofs(4) ABI was changed in order to restore binary compatibility
437 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
441 The powerpc64 kernel has been changed to a position-independent
442 executable. This can only be booted with a new version of loader(8),
443 so make sure to update both world and kernel before rebooting.
446 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
447 only release, no new features have been added. Please see the 20141231
448 entry below for information about prerequisites and upgrading, if you
449 are not already using 3.5.0.
452 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
453 taken from the ELF Tool Chain project rather than GNU binutils. They
454 should be drop-in replacements, with the addition of arm64 support.
455 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
456 binutils tools, if necessary. See 20150805 for updated information.
459 The default Unbound configuration now enables remote control
460 using a local socket. Users who have already enabled the
461 local_unbound service should regenerate their configuration
462 by running "service local_unbound setup" as root.
465 The GNU texinfo and GNU info pages have been removed.
466 To be able to view GNU info pages please install texinfo from ports.
469 Clang, llvm and lldb have been upgraded to 3.5.0 release.
471 As of this release, a prerequisite for building clang, llvm and lldb is
472 a C++11 capable compiler and C++11 standard library. This means that to
473 be able to successfully build the cross-tools stage of buildworld, with
474 clang as the bootstrap compiler, your system compiler or cross compiler
475 should either be clang 3.3 or later, or gcc 4.8 or later, and your
476 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
479 On any standard FreeBSD 10.x or 11.x installation, where clang and
480 libc++ are on by default (that is, on x86 or arm), this should work out
483 On 9.x installations where clang is enabled by default, e.g. on x86 and
484 powerpc, libc++ will not be enabled by default, so libc++ should be
485 built (with clang) and installed first. If both clang and libc++ are
486 missing, build clang first, then use it to build libc++.
488 On 8.x and earlier installations, upgrade to 9.x first, and then follow
489 the instructions for 9.x above.
491 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
492 default, and do not build clang.
494 Many embedded systems are resource constrained, and will not be able to
495 build clang in a reasonable time, or in some cases at all. In those
496 cases, cross building bootable systems on amd64 is a workaround.
498 This new version of clang introduces a number of new warnings, of which
499 the following are most likely to appear:
503 This warns in two cases, for both C and C++:
504 * When the code is trying to take the absolute value of an unsigned
505 quantity, which is effectively a no-op, and almost never what was
506 intended. The code should be fixed, if at all possible. If you are
507 sure that the unsigned quantity can be safely cast to signed, without
508 loss of information or undefined behavior, you can add an explicit
509 cast, or disable the warning.
511 * When the code is trying to take an absolute value, but the called
512 abs() variant is for the wrong type, which can lead to truncation.
513 If you want to disable the warning instead of fixing the code, please
514 make sure that truncation will not occur, or it might lead to unwanted
517 -Wtautological-undefined-compare and
518 -Wundefined-bool-conversion
520 These warn when C++ code is trying to compare 'this' against NULL, while
521 'this' should never be NULL in well-defined C++ code. However, there is
522 some legacy (pre C++11) code out there, which actively abuses this
523 feature, which was less strictly defined in previous C++ versions.
525 Squid and openjdk do this, for example. The warning can be turned off
526 for C++98 and earlier, but compiling the code in C++11 mode might result
527 in unexpected behavior; for example, the parts of the program that are
528 unreachable could be optimized away.
531 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
532 kernel sources have been removed. The .h files remain, since some
533 utilities include them. This will need to be fixed later.
534 If "mount -t oldnfs ..." is attempted, it will fail.
535 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
536 the utilities will report errors.
539 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
540 directories to top level SUBDIR variable when their parent
541 directory is included in LOCAL_DIRS. Users with build systems with
542 such hierarchies and without SUBDIR entries in the parent
543 directory Makefiles should add them or add the directories to
547 faith(4) and faithd(8) have been removed from the base system. Faith
548 has been obsolete for a very long time.
551 vt(4), the new console driver, is enabled by default. It brings
552 support for Unicode and double-width characters, as well as
553 support for UEFI and integration with the KMS kernel video
556 You may need to update your console settings in /etc/rc.conf,
557 most probably the keymap. During boot, /etc/rc.d/syscons will
558 indicate what you need to do.
560 vt(4) still has issues and lacks some features compared to
561 syscons(4). See the wiki for up-to-date information:
562 https://wiki.freebsd.org/Newcons
564 If you want to keep using syscons(4), you can do so by adding
565 the following line to /boot/loader.conf:
569 pjdfstest has been integrated into kyua as an opt-in test suite.
570 Please see share/doc/pjdfstest/README for more details on how to
574 gperf has been removed from the base system for architectures
575 that use clang. Ports that require gperf will obtain it from the
579 pjdfstest has been moved from tools/regression/pjdfstest to
583 At svn r271982, The default linux compat kernel ABI has been adjusted
584 to 2.6.18 in support of the linux-c6 compat ports infrastructure
585 update. If you wish to continue using the linux-f10 compat ports,
586 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
587 encouraged to update their linux-compat packages to linux-c6 during
588 their next update cycle.
591 The ofwfb driver, used to provide a graphics console on PowerPC when
592 using vt(4), no longer allows mmap() of all physical memory. This
593 will prevent Xorg on PowerPC with some ATI graphics cards from
594 initializing properly unless x11-servers/xorg-server is updated to
598 The xdev targets have been converted to using TARGET and
599 TARGET_ARCH instead of XDEV and XDEV_ARCH.
602 The default unbound configuration has been modified to address
603 issues with reverse lookups on networks that use private
604 address ranges. If you use the local_unbound service, run
605 "service local_unbound setup" as root to regenerate your
606 configuration, then "service local_unbound reload" to load the
610 The GNU texinfo and GNU info pages are not built and installed
611 anymore, WITH_INFO knob has been added to allow to built and install
613 UPDATE: see 20150102 entry on texinfo's removal
616 The GNU readline library is now an INTERNALLIB - that is, it is
617 statically linked into consumers (GDB and variants) in the base
618 system, and the shared library is no longer installed. The
619 devel/readline port is available for third party software that
623 The Itanium architecture (ia64) has been removed from the list of
624 known architectures. This is the first step in the removal of the
628 Commit r268115 has added NFSv4.1 server support, merged from
629 projects/nfsv4.1-server. Since this includes changes to the
630 internal interfaces between the NFS related modules, a full
631 build of the kernel and modules will be necessary.
632 __FreeBSD_version has been bumped.
635 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
636 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
637 which differs from the behaviour controlled by this knob.)
640 Maximal length of the serial number in CTL was increased from 16 to
641 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
642 and ctld, need to be rebuilt to work with a new kernel.
645 The libatf-c and libatf-c++ major versions were downgraded to 0 and
646 1 respectively to match the upstream numbers. They were out of
647 sync because, when they were originally added to FreeBSD, the
648 upstream versions were not respected. These libraries are private
649 and not yet built by default, so renumbering them should be a
650 non-issue. However, unclean source trees will yield broken test
651 programs once the operator executes "make delete-old-libs" after a
654 Additionally, the atf-sh binary was made private by moving it into
655 /usr/libexec/. Already-built shell test programs will keep the
656 path to the old binary so they will break after "make delete-old"
659 If you are using WITH_TESTS=yes (not the default), wipe the object
660 tree and rebuild from scratch to prevent spurious test failures.
661 This is only needed once: the misnumbered libraries and misplaced
662 binaries have been added to OptionalObsoleteFiles.inc so they will
663 be removed during a clean upgrade.
666 Clang and llvm have been upgraded to 3.4.1 release.
669 We bogusly installed src.opts.mk in /usr/share/mk. This file should
670 be removed to avoid issues in the future (and has been added to
674 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
675 past, it affected all builds that used the bsd.*.mk files. The old
676 behavior was a bug, but people may have relied upon it. To get this
677 behavior back, you can .include /etc/src.conf from /etc/make.conf
678 (which is still global and isn't changed). This also changes the
679 behavior of incremental builds inside the tree of individual
680 directories. Set MAKESYSPATH to ".../share/mk" to do that.
681 Although this has survived make universe and some upgrade scenarios,
682 other upgrade scenarios may have broken. At least one form of
683 temporary breakage was fixed with MAKESYSPATH settings for buildworld
684 as well... In cases where MAKESYSPATH isn't working with this
685 setting, you'll need to set it to the full path to your tree.
687 One side effect of all this cleaning up is that bsd.compiler.mk
688 is no longer implicitly included by bsd.own.mk. If you wish to
689 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
693 The lindev device has been removed since /dev/full has been made a
694 standard device. __FreeBSD_version has been bumped.
697 The knob WITHOUT_VI was added to the base system, which controls
698 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
699 in order to reorder files share/termcap and didn't build ex(1) as a
700 build tool, so building/installing with WITH_VI is highly advised for
701 build hosts for older releases.
703 This issue has been fixed in stable/9 and stable/10 in r277022 and
704 r276991, respectively.
707 The YES_HESIOD knob has been removed. It has been obsolete for
708 a decade. Please move to using WITH_HESIOD instead or your builds
709 will silently lack HESIOD.
712 The uart(4) driver has been changed with respect to its handling
713 of the low-level console. Previously the uart(4) driver prevented
714 any process from changing the baudrate or the CLOCAL and HUPCL
715 control flags. By removing the restrictions, operators can make
716 changes to the serial console port without having to reboot.
717 However, when getty(8) is started on the serial device that is
718 associated with the low-level console, a misconfigured terminal
719 line in /etc/ttys will now have a real impact.
720 Before upgrading the kernel, make sure that /etc/ttys has the
721 serial console device configured as 3wire without baudrate to
722 preserve the previous behaviour. E.g:
723 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
726 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
727 to improve performance. To re-enable it, if needed, run rpcbind
728 with command line option -W.
731 Switched back to the GPL dtc compiler due to updates in the upstream
732 dts files not being supported by the BSDL dtc compiler. You will need
733 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
734 may result while building dtb files during a kernel build if you fail
735 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
738 Clang and llvm have been upgraded to 3.4 release.
741 The nve(4) driver has been removed. Please use the nfe(4) driver
742 for NVIDIA nForce MCP Ethernet adapters instead.
745 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
746 This could cause certain C++ applications using shared libraries built
747 against the previous version of libc++ to crash. The incompatibility
748 has now been fixed, but any C++ applications or shared libraries built
749 between r261283 and r261801 should be recompiled.
752 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
753 capability mode support. Please note that enabling the feature in
754 kernel is still highly recommended.
757 OpenSSH is now built with sandbox support, and will use sandbox as
758 the default privilege separation method. This requires Capsicum
759 capability mode support in kernel.
762 The libelf and libdwarf libraries have been updated to newer
763 versions from upstream. Shared library version numbers for
764 these two libraries were bumped. Any ports or binaries
765 requiring these two libraries should be recompiled.
766 __FreeBSD_version is bumped to 1100006.
769 If a Makefile in a tests/ directory was auto-generating a Kyuafile
770 instead of providing an explicit one, this would prevent such
771 Makefile from providing its own Kyuafile in the future during
772 NO_CLEAN builds. This has been fixed in the Makefiles but manual
773 intervention is needed to clean an objdir if you use NO_CLEAN:
774 # find /usr/obj -name Kyuafile | xargs rm -f
777 The behavior of gss_pseudo_random() for the krb5 mechanism
778 has changed, for applications requesting a longer random string
779 than produced by the underlying enctype's pseudo-random() function.
780 In particular, the random string produced from a session key of
781 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
782 be different at the 17th octet and later, after this change.
783 The counter used in the PRF+ construction is now encoded as a
784 big-endian integer in accordance with RFC 4402.
785 __FreeBSD_version is bumped to 1100004.
788 The WITHOUT_ATF build knob has been removed and its functionality
789 has been subsumed into the more generic WITHOUT_TESTS. If you were
790 using the former to disable the build of the ATF libraries, you
791 should change your settings to use the latter.
794 The default version of mtree is nmtree which is obtained from
795 NetBSD. The output is generally the same, but may vary
796 slightly. If you found you need identical output adding
797 "-F freebsd9" to the command line should do the trick. For the
798 time being, the old mtree is available as fmtree.
801 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
802 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
803 1.1.4_8 and verify bsdyml not linked in, before running "make
805 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
807 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
810 The stable/10 branch has been created in subversion from head
814 The rc.d/jail script has been updated to support jail(8)
815 configuration file. The "jail_<jname>_*" rc.conf(5) variables
816 for per-jail configuration are automatically converted to
817 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
818 This is transparently backward compatible. See below about some
819 incompatibilities and rc.conf(5) manual page for more details.
821 These variables are now deprecated in favor of jail(8) configuration
822 file. One can use "rc.d/jail config <jname>" command to generate
823 a jail(8) configuration file in /var/run/jail.<jname>.conf without
824 running the jail(8) utility. The default pathname of the
825 configuration file is /etc/jail.conf and can be specified by
826 using $jail_conf or $jail_<jname>_conf variables.
828 Please note that jail_devfs_ruleset accepts an integer at
829 this moment. Please consider to rewrite the ruleset name
833 BIND has been removed from the base system. If all you need
834 is a local resolver, simply enable and start the local_unbound
835 service instead. Otherwise, several versions of BIND are
836 available in the ports tree. The dns/bind99 port is one example.
838 With this change, nslookup(1) and dig(1) are no longer in the base
839 system. Users should instead use host(1) and drill(1) which are
840 in the base system. Alternatively, nslookup and dig can
841 be obtained by installing the dns/bind-tools port.
844 With the addition of unbound(8), a new unbound user is now
845 required during installworld. "mergemaster -p" can be used to
846 add the user prior to installworld, as documented in the handbook.
849 OpenSSH is now built with DNSSEC support, and will by default
850 silently trust signed SSHFP records. This can be controlled with
851 the VerifyHostKeyDNS client configuration setting. DNSSEC support
852 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
855 The GNU Compiler Collection and C++ standard library (libstdc++)
856 are no longer built by default on platforms where clang is the system
857 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
861 The PROCDESC kernel option is now part of the GENERIC kernel
862 configuration and is required for the rwhod(8) to work.
863 If you are using custom kernel configuration, you should include
867 The API and ABI related to the Capsicum framework was modified
868 in backward incompatible way. The userland libraries and programs
869 have to be recompiled to work with the new kernel. This includes the
870 following libraries and programs, but the whole buildworld is
871 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
872 kdump, procstat, rwho, rwhod, uniq.
875 AES-NI intrinsic support has been added to gcc. The AES-NI module
876 has been updated to use this support. A new gcc is required to build
877 the aesni module on both i386 and amd64.
880 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
881 Thus "device padlock_rng" and "device rdrand_rng" should be
882 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
885 WITH_ICONV has been split into two feature sets. WITH_ICONV now
886 enables just the iconv* functionality and is now on by default.
887 WITH_LIBICONV_COMPAT enables the libiconv api and link time
888 compatability. Set WITHOUT_ICONV to build the old way.
889 If you have been using WITH_ICONV before, you will very likely
890 need to turn on WITH_LIBICONV_COMPAT.
893 INVARIANTS option now enables DEBUG for code with OpenSolaris and
894 Illumos origin, including ZFS. If you have INVARIANTS in your
895 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
897 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
898 locks if WITNESS option was set. Because that generated a lot of
899 witness(9) reports and all of them were believed to be false
900 positives, this is no longer done. New option OPENSOLARIS_WITNESS
901 can be used to achieve the previous behavior.
904 Timer values in IPv6 data structures now use time_uptime instead
905 of time_second. Although this is not a user-visible functional
906 change, userland utilities which directly use them---ndp(8),
907 rtadvd(8), and rtsold(8) in the base system---need to be updated
911 find -delete can now delete the pathnames given as arguments,
912 instead of only files found below them or if the pathname did
913 not contain any slashes. Formerly, the following error message
916 find: -delete: <path>: relative path potentially not safe
918 Deleting the pathnames given as arguments can be prevented
919 without error messages using -mindepth 1 or by changing
920 directory and passing "." as argument to find. This works in the
921 old as well as the new version of find.
924 Behavior of devfs rules path matching has been changed.
925 Pattern is now always matched against fully qualified devfs
926 path and slash characters must be explicitly matched by
927 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
928 subdirectories must be reviewed.
931 The default ARM ABI has changed to the ARM EABI. The old ABI is
932 incompatible with the ARM EABI and all programs and modules will
933 need to be rebuilt to work with a new kernel.
935 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
937 NOTE: Support for the old ABI will be removed in the future and
938 users are advised to upgrade.
941 pkg_install has been disconnected from the build if you really need it
942 you should add WITH_PKGTOOLS in your src.conf(5).
945 Most of network statistics structures were changed to be able
946 keep 64-bits counters. Thus all tools, that work with networking
947 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
950 Fix a bug that allowed a tracing process (e.g. gdb) to write
951 to a memory-mapped file in the traced process's address space
952 even if neither the traced process nor the tracing process had
953 write access to that file.
956 CVS has been removed from the base system. An exact copy
957 of the code is available from the devel/cvs port.
960 Some people report the following error after the switch to bmake:
962 make: illegal option -- J
963 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
965 *** [buildworld] Error code 2
967 this likely due to an old instance of make in
968 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
969 which src/Makefile will use that blindly, if it exists, so if
970 you see the above error:
972 rm -rf `make -V MAKEPATH`
977 Use bmake by default.
978 Whereas before one could choose to build with bmake via
979 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
980 make. The goal is to remove these knobs for 10-RELEASE.
982 It is worth noting that bmake (like gmake) treats the command
983 line as the unit of failure, rather than statements within the
984 command line. Thus '(cd some/where && dosomething)' is safer
985 than 'cd some/where; dosomething'. The '()' allows consistent
986 behavior in parallel build.
989 Fix a bug that allows NFS clients to issue READDIR on files.
992 The WITHOUT_IDEA option has been removed because
993 the IDEA patent expired.
996 The sysctl which controls TRIM support under ZFS has been renamed
997 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1001 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1002 rather than creating it's own in the temporary directory in
1003 order allow access to bootstrapped versions of tools such as
1004 install and mtree. When upgrading from version of FreeBSD where
1005 the install command does not support -l, you will need to
1006 install a new mergemaster command if mergemaster -p is required.
1007 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1011 Legacy ATA stack, disabled and replaced by new CAM-based one since
1012 FreeBSD 9.0, completely removed from the sources. Kernel modules
1013 atadisk and atapi*, user-level tools atacontrol and burncd are
1014 removed. Kernel option `options ATA_CAM` is now permanently enabled
1018 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1019 and socketpair(2). Software, in particular Kerberos, may
1020 automatically detect and use these during building. The resulting
1021 binaries will not work on older kernels.
1024 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1025 information, see the respective 20130304 entry).
1028 Recent commits to callout(9) changed the size of struct callout,
1029 so the KBI is probably heavily disturbed. Also, some functions
1030 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1031 by macros. Every kernel module using it won't load, so rebuild
1034 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1035 but does not initialize by default (because of the new CTL_DISABLE
1036 option) to save memory. To re-enable it, remove the CTL_DISABLE
1037 option from the kernel config file or set kern.cam.ctl.disable=0
1038 in /boot/loader.conf.
1041 The ctl device has been disabled in GENERIC for i386 and amd64.
1042 This was done due to the extra memory being allocated at system
1043 initialisation time by the ctl driver which was only used if
1044 a CAM target device was created. This makes a FreeBSD system
1045 unusable on 128MB or less of RAM.
1048 A new compression method (lz4) has been merged to -HEAD. Please
1049 refer to zpool-features(7) for more information.
1051 Please refer to the "ZFS notes" section of this file for information
1052 on upgrading boot ZFS pools.
1055 A BSD-licensed patch(1) variant has been added and is installed
1056 as bsdpatch, being the GNU version the default patch.
1057 To inverse the logic and use the BSD-licensed one as default,
1058 while having the GNU version installed as gnupatch, rebuild
1059 and install world with the WITH_BSD_PATCH knob set.
1062 Due to the use of the new -l option to install(1) during build
1063 and install, you must take care not to directly set the INSTALL
1064 make variable in your /etc/make.conf, /etc/src.conf, or on the
1065 command line. If you wish to use the -C flag for all installs
1066 you may be able to add INSTALL+=-C to /etc/make.conf or
1070 The install(1) option -M has changed meaning and now takes an
1071 argument that is a file or path to append logs to. In the
1072 unlikely event that -M was the last option on the command line
1073 and the command line contained at least two files and a target
1074 directory the first file will have logs appended to it. The -M
1075 option served little practical purpose in the last decade so its
1076 use is expected to be extremely rare.
1079 After switching to Clang as the default compiler some users of ZFS
1080 on i386 systems started to experience stack overflow kernel panics.
1081 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1084 GEOM_LABEL now mangles label names read from file system metadata.
1085 Mangling affect labels containing spaces, non-printable characters,
1086 '%' or '"'. Device names in /etc/fstab and other places may need to
1090 By default, only the 10 most recent kernel dumps will be saved. To
1091 restore the previous behaviour (no limit on the number of kernel dumps
1092 stored in the dump directory) add the following line to /etc/rc.conf:
1097 With the addition of auditdistd(8), a new auditdistd user is now
1098 required during installworld. "mergemaster -p" can be used to
1099 add the user prior to installworld, as documented in the handbook.
1102 The sin6_scope_id member variable in struct sockaddr_in6 is now
1103 filled by the kernel before passing the structure to the userland via
1104 sysctl or routing socket. This means the KAME-specific embedded scope
1105 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1106 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1107 __FreeBSD_version is bumped to 1000025.
1110 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1111 This means that the world and kernel will be compiled with clang
1112 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1113 and /usr/bin/cpp. To disable this behavior and revert to building
1114 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1115 of current may need to bootstrap WITHOUT_CLANG first if the clang
1116 build fails (its compatibility window doesn't extend to the 9 stable
1120 The IPFIREWALL_FORWARD kernel option has been removed. Its
1121 functionality now turned on by default.
1124 The ZERO_COPY_SOCKET kernel option has been removed and
1125 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1126 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1127 mechanism which is not safe and may result in kernel crashes.
1128 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1129 driver supports disposeable external page sized mbuf storage.
1130 Proper replacements for both zero-copy mechanisms are under
1131 consideration and will eventually lead to complete removal
1132 of the two kernel options.
1135 The IPv4 network stack has been converted to network byte
1136 order. The following modules need to be recompiled together
1137 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1138 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1141 Support for non-MPSAFE filesystems was removed from VFS. The
1142 VFS_VERSION was bumped, all filesystem modules shall be
1146 All the non-MPSAFE filesystems have been disconnected from
1147 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1148 portalfs, smbfs, xfs.
1151 The interface cloning API and ABI has changed. The following
1152 modules need to be recompiled together with kernel:
1153 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1154 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1155 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1158 The sdhci driver was split in two parts: sdhci (generic SD Host
1159 Controller logic) and sdhci_pci (actual hardware driver).
1160 No kernel config modifications are required, but if you
1161 load sdhc as a module you must switch to sdhci_pci instead.
1164 Import the FUSE kernel and userland support into base system.
1167 The GNU sort(1) program has been removed since the BSD-licensed
1168 sort(1) has been the default for quite some time and no serious
1169 problems have been reported. The corresponding WITH_GNU_SORT
1173 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1174 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1178 The net80211(4) ABI has been changed to allow for improved driver
1179 PS-POLL and power-save support. All wireless drivers need to be
1180 recompiled to work with the new kernel.
1183 The random(4) support for the VIA hardware random number
1184 generator (`PADLOCK') is no longer enabled unconditionally.
1185 Add the padlock_rng device in the custom kernel config if
1186 needed. The GENERIC kernels on i386 and amd64 do include the
1187 device, so the change only affects the custom kernel
1191 The pf(4) packet filter ABI has been changed. pfctl(8) and
1192 snmp_pf module need to be recompiled to work with new kernel.
1195 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1196 to -HEAD. Pools that have empty_bpobj in active state can not be
1197 imported read-write with ZFS implementations that do not support
1198 this feature. For more information read the zpool-features(5)
1202 The sparc64 ZFS loader has been changed to no longer try to auto-
1203 detect ZFS providers based on diskN aliases but now requires these
1204 to be explicitly listed in the OFW boot-device environment variable.
1207 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1208 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1209 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1212 The following sysctls and tunables have been renamed for consistency
1213 with other variables:
1214 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1215 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1218 The sort utility has been replaced with BSD sort. For now, GNU sort
1219 is also available as "gnusort" or the default can be set back to
1220 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1221 installed as "bsdsort".
1224 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1225 Starting with this version the old system of ZFS pool versioning
1226 is superseded by "feature flags". This concept enables forward
1227 compatibility against certain future changes in functionality of ZFS
1228 pools. The first read-only compatible "feature flag" for ZFS pools
1229 is named "com.delphix:async_destroy". For more information
1230 read the new zpool-features(5) manual page.
1231 Please refer to the "ZFS notes" section of this file for information
1232 on upgrading boot ZFS pools.
1235 The malloc(3) implementation embedded in libc now uses sources imported
1236 as contrib/jemalloc. The most disruptive API change is to
1237 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1238 delete it prior to installworld, and optionally re-create it using the
1239 new format after rebooting. See malloc.conf(5) for details
1240 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1244 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1245 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1246 now spelled mips. This is to aid compatibility with third-party
1247 software that expects this naming scheme in uname(3). Little-endian
1248 settings are unchanged. If you are updating a big-endian mips64 machine
1249 from before this change, you may need to set MACHINE_ARCH=mips64 in
1250 your environment before the new build system will recognize your machine.
1253 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1257 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1258 nullfs(5) did not pass through all behaviours to the underlying layer,
1259 as a result if we bound to a socket on the lower layer we could connect
1260 only to the lower path; if we bound to the upper layer we could connect
1261 only to the upper path. The new behavior is one can connect to both the
1262 lower and the upper paths regardless what layer path one binds to.
1265 The getifaddrs upgrade path broken with 20111215 has been restored.
1266 If you have upgraded in between 20111215 and 20120209 you need to
1267 recompile libc again with your kernel. You still need to recompile
1268 world to be able to configure CARP but this restriction already
1269 comes from 20111215.
1272 The set_rcvar() function has been removed from /etc/rc.subr. All
1273 base and ports rc.d scripts have been updated, so if you have a
1274 port installed with a script in /usr/local/etc/rc.d you can either
1275 hand-edit the rcvar= line, or reinstall the port.
1277 An easy way to handle the mass-update of /etc/rc.d:
1278 rm /etc/rc.d/* && mergemaster -i
1281 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1282 on the current CPU and prevents other threads from running.
1283 This behavior can be reverted using the kern.stop_scheduler_on_panic
1285 The new behavior can be incompatible with kern.sync_on_panic.
1288 The carp(4) facility has been changed significantly. Configuration
1289 of the CARP protocol via ifconfig(8) has changed, as well as format
1290 of CARP events submitted to devd(8) has changed. See manual pages
1291 for more information. The arpbalance feature of carp(4) is currently
1292 not supported anymore.
1294 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1295 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1296 need to be recompiled.
1299 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1303 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1304 explicitely support non-MPSAFE filesystems.
1305 It is on by default for all supported platform at this present
1309 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1310 i386 and pc98 GENERIC kernel configuration files.
1313 sysinstall has been removed
1316 The stable/9 branch created in subversion. This corresponds to the
1317 RELENG_9 branch in CVS.
1323 Avoid using make -j when upgrading. While generally safe, there are
1324 sometimes problems using -j to upgrade. If your upgrade fails with
1325 -j, please try again without -j. From time to time in the past there
1326 have been problems using -j with buildworld and/or installworld. This
1327 is especially true when upgrading between "distant" versions (eg one
1328 that cross a major release boundary or several minor releases, or when
1329 several months have passed on the -current branch).
1331 Sometimes, obscure build problems are the result of environment
1332 poisoning. This can happen because the make utility reads its
1333 environment when searching for values for global variables. To run
1334 your build attempts in an "environmental clean room", prefix all make
1335 commands with 'env -i '. See the env(1) manual page for more details.
1337 When upgrading from one major version to another it is generally best
1338 to upgrade to the latest code in the currently installed branch first,
1339 then do an upgrade to the new branch. This is the best-tested upgrade
1340 path, and has the highest probability of being successful. Please try
1341 this approach before reporting problems with a major version upgrade.
1343 When upgrading a live system, having a root shell around before
1344 installing anything can help undo problems. Not having a root shell
1345 around can lead to problems if pam has changed too much from your
1346 starting point to allow continued authentication after the upgrade.
1348 This file should be read as a log of events. When a later event changes
1349 information of a prior event, the prior event should not be deleted.
1350 Instead, a pointer to the entry with the new information should be
1351 placed in the old entry. Readers of this file should also sanity check
1352 older entries before relying on them blindly. Authors of new entries
1353 should write them with this in mind.
1357 When upgrading the boot ZFS pool to a new version, always follow
1360 1.) recompile and reinstall the ZFS boot loader and boot block
1361 (this is part of "make buildworld" and "make installworld")
1363 2.) update the ZFS boot block on your boot drive
1365 The following example updates the ZFS boot block on the first
1366 partition (freebsd-boot) of a GPT partitioned drive ada0:
1367 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1369 Non-boot pools do not need these updates.
1373 If you are updating from a prior version of FreeBSD (even one just
1374 a few days old), you should follow this procedure. It is the most
1375 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1377 make kernel-toolchain
1378 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1379 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1381 To test a kernel once
1382 ---------------------
1383 If you just want to boot a kernel once (because you are not sure
1384 if it works, or if you want to boot a known bad kernel to provide
1385 debugging information) run
1386 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1387 nextboot -k testkernel
1389 To just build a kernel when you know that it won't mess you up
1390 --------------------------------------------------------------
1391 This assumes you are already running a CURRENT system. Replace
1392 ${arch} with the architecture of your machine (e.g. "i386",
1393 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1395 cd src/sys/${arch}/conf
1396 config KERNEL_NAME_HERE
1397 cd ../compile/KERNEL_NAME_HERE
1402 If this fails, go to the "To build a kernel" section.
1404 To rebuild everything and install it on the current system.
1405 -----------------------------------------------------------
1406 # Note: sometimes if you are running current you gotta do more than
1407 # is listed here if you are upgrading from a really old current.
1409 <make sure you have good level 0 dumps>
1411 make kernel KERNCONF=YOUR_KERNEL_HERE
1413 <reboot in single user> [3]
1420 To cross-install current onto a separate partition
1421 --------------------------------------------------
1422 # In this approach we use a separate partition to hold
1423 # current's root, 'usr', and 'var' directories. A partition
1424 # holding "/", "/usr" and "/var" should be about 2GB in
1427 <make sure you have good level 0 dumps>
1430 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1431 <maybe newfs current's root partition>
1432 <mount current's root partition on directory ${CURRENT_ROOT}>
1433 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1434 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1435 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1436 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1437 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1438 <reboot into current>
1439 <do a "native" rebuild/install as described in the previous section>
1440 <maybe install compatibility libraries from ports/misc/compat*>
1444 To upgrade in-place from stable to current
1445 ----------------------------------------------
1446 <make sure you have good level 0 dumps>
1448 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1450 <reboot in single user> [3]
1457 Make sure that you've read the UPDATING file to understand the
1458 tweaks to various things you need. At this point in the life
1459 cycle of current, things change often and you are on your own
1460 to cope. The defaults can also change, so please read ALL of
1461 the UPDATING entries.
1463 Also, if you are tracking -current, you must be subscribed to
1464 freebsd-current@freebsd.org. Make sure that before you update
1465 your sources that you have read and understood all the recent
1466 messages there. If in doubt, please track -stable which has
1467 much fewer pitfalls.
1469 [1] If you have third party modules, such as vmware, you
1470 should disable them at this point so they don't crash your
1473 [3] From the bootblocks, boot -s, and then do
1478 adjkerntz -i # if CMOS is wall time
1479 Also, when doing a major release upgrade, it is required that
1480 you boot into single user mode to do the installworld.
1482 [4] Note: This step is non-optional. Failure to do this step
1483 can result in a significant reduction in the functionality of the
1484 system. Attempting to do it by hand is not recommended and those
1485 that pursue this avenue should read this file carefully, as well
1486 as the archives of freebsd-current and freebsd-hackers mailing lists
1487 for potential gotchas. The -U option is also useful to consider.
1488 See mergemaster(8) for more information.
1490 [5] Usually this step is a noop. However, from time to time
1491 you may need to do this if you get unknown user in the following
1492 step. It never hurts to do it all the time. You may need to
1493 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1494 install) after the buildworld before this step if you last updated
1495 from current before 20130425 or from -stable before 20130430.
1497 [6] This only deletes old files and directories. Old libraries
1498 can be deleted by "make delete-old-libs", but you have to make
1499 sure that no program is using those libraries anymore.
1501 [8] In order to have a kernel that can run the 4.x binaries needed to
1502 do an installworld, you must include the COMPAT_FREEBSD4 option in
1503 your kernel. Failure to do so may leave you with a system that is
1504 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1505 required to run the 5.x binaries on more recent kernels. And so on
1506 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1508 Make sure that you merge any new devices from GENERIC since the
1509 last time you updated your kernel config file.
1511 [9] When checking out sources, you must include the -P flag to have
1512 cvs prune empty directories.
1514 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1515 "?=" instead of the "=" assignment operator, so that buildworld can
1516 override the CPUTYPE if it needs to.
1518 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1519 not on the command line, or in /etc/make.conf. buildworld will
1520 warn if it is improperly defined.
1523 This file contains a list, in reverse chronological order, of major
1524 breakages in tracking -current. It is not guaranteed to be a complete
1525 list of such breakages, and only contains entries since September 23, 2011.
1526 If you need to see UPDATING entries from before that date, you will need
1527 to fetch an UPDATING file from an older FreeBSD release.
1529 Copyright information:
1531 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1533 Redistribution, publication, translation and use, with or without
1534 modification, in full or in part, in any form or format of this
1535 document are permitted without further permission from the author.
1537 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1538 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1539 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1540 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1541 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1542 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1543 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1544 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1545 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1546 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1547 POSSIBILITY OF SUCH DAMAGE.
1549 Contact Warner Losh if you have any questions about your use of