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 armv6 port now defaults to hard float ABI. Limited support
36 for running both hardfloat and soft float on the same system
37 is available using the libraries installed with -DWITH_LIBSOFT.
38 This has only been tested as an upgrade path for installworld
39 and packages may fail or need manual intervention to run. New
40 packages will be needed.
43 Kernel modules compiled outside of a kernel build now default to
44 installing to /boot/modules instead of /boot/kernel. Many kernel
45 modules built this way (such as those in ports) already overrode
46 KMODDIR explicitly to install into /boot/modules. However,
47 manually building and installing a module from /sys/modules will
48 now install to /boot/modules instead of /boot/kernel.
51 The CAM I/O scheduler has been committed to the kernel. There should be
52 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
53 list of known rogues that claim support for this but actually corrupt
54 data is believed to be complete, be on the lookout for data
55 corruption. The known rogue list is believed to be complete:
57 o Crucial MX100, M550 drives with MU01 firmware.
58 o Micron M510 and M550 drives with MU01 firmware.
59 o Micron M500 prior to MU07 firmware
60 o Samsung 830, 840, and 850 all firmwares
61 o FCCT M500 all firmwares
63 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
64 with working NCQ TRIM. For Micron branded drives, see your sales rep for
65 updated firmware. Black listed drives will work correctly because these
66 drives work correctly so long as no NCQ TRIMs are sent to them. Given
67 this list is the same as found in Linux, it's believed there are no
68 other rogues in the market place. All other models from the above
71 To be safe, if you are at all concerned, you can quirk each of your
72 drives to prevent NCQ from being sent by setting:
73 kern.cam.ada.X.quirks="0x2"
74 in loader.conf. If the drive requires the 4k sector quirk, set the
78 The FAST_DEPEND build option has been removed and its functionality is
79 now the one true way. The old mkdep(1) style of 'make depend' has
80 been removed. See 20160311 for further details.
83 Resource range types have grown from unsigned long to uintmax_t. All
84 drivers, and anything using libdevinfo, need to be recompiled.
87 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
88 builds. It no longer runs mkdep(1) during 'make depend', and the
89 'make depend' stage can safely be skipped now as it is auto ran
90 when building 'make all' and will generate all SRCS and DPSRCS before
91 building anything else. Dependencies are gathered at compile time with
92 -MF flags kept in separate .depend files per object file. Users should
93 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
97 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
98 kernel modules. Therefore, if you load any kernel modules at boot time,
99 please install the boot loaders after you install the kernel, but before
103 make kernel KERNCONF=YOUR_KERNEL_HERE
104 make -C sys/boot install
105 <reboot in single user>
107 Then follow the usual steps, described in the General Notes section,
111 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
112 see the 20141231 entry below for information about prerequisites and
113 upgrading, if you are not already using clang 3.5.0 or higher.
116 The AIO subsystem is now a standard part of the kernel. The
117 VFS_AIO kernel option and aio.ko kernel module have been removed.
118 Due to stability concerns, asynchronous I/O requests are only
119 permitted on sockets and raw disks by default. To enable
120 asynchronous I/O requests on all file types, set the
121 vfs.aio.enable_unsafe sysctl to a non-zero value.
124 The ELF object manipulation tool objcopy is now provided by the
125 ELF Tool Chain project rather than by GNU binutils. It should be a
126 drop-in replacement, with the addition of arm64 support. The
127 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
128 to obtain the GNU version if necessary.
131 Building ZFS pools on top of zvols is prohibited by default. That
132 feature has never worked safely; it's always been prone to deadlocks.
133 Using a zvol as the backing store for a VM guest's virtual disk will
134 still work, even if the guest is using ZFS. Legacy behavior can be
135 restored by setting vfs.zfs.vol.recursive=1.
138 The NONE and HPN patches has been removed from OpenSSH. They are
139 still available in the security/openssh-portable port.
142 With the addition of ypldap(8), a new _ypldap user is now required
143 during installworld. "mergemaster -p" can be used to add the user
144 prior to installworld, as documented in the handbook.
147 The tftp loader (pxeboot) now uses the option root-path directive. As a
148 consequence it no longer looks for a pxeboot.4th file on the tftp
149 server. Instead it uses the regular /boot infrastructure as with the
153 The code to start recording plug and play data into the modules has
154 been committed. While the old tools will properly build a new kernel,
155 a number of warnings about "unknown metadata record 4" will be produced
156 for an older kldxref. To avoid such warnings, make sure to rebuild
157 the kernel toolchain (or world). Make sure that you have r292078 or
158 later when trying to build 292077 or later before rebuilding.
161 Debug data files are now built by default with 'make buildworld' and
162 installed with 'make installworld'. This facilitates debugging but
163 requires more disk space both during the build and for the installed
164 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
168 r291527 changed the internal interface between the nfsd.ko and
169 nfscommon.ko modules. As such, they must both be upgraded to-gether.
170 __FreeBSD_version has been bumped because of this.
173 Add support for unicode collation strings leads to a change of
174 order of files listed by ls(1) for example. To get back to the old
175 behaviour, set LC_COLLATE environment variable to "C".
177 Databases administrators will need to reindex their databases given
178 collation results will be different.
180 Due to a bug in install(1) it is recommended to remove the ancient
181 locales before running make installworld.
183 rm -rf /usr/share/locale/*
186 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
187 libcrypto.so.7 or libssl.so.7 must be recompiled.
190 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
191 Kernel modules isp_2400_multi and isp_2500_multi were removed and
192 should be replaced with isp_2400 and isp_2500 modules respectively.
195 The build previously allowed using 'make -n' to not recurse into
196 sub-directories while showing what commands would be executed, and
197 'make -n -n' to recursively show commands. Now 'make -n' will recurse
198 and 'make -N' will not.
201 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
202 and etcupdate will now use this file. A custom sendmail.cf is now
203 updated via this mechanism rather than via installworld. If you had
204 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
205 want to remove the exclusion or change it to "always install".
206 /etc/mail/sendmail.cf is now managed the same way regardless of
207 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
208 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
211 Compatibility shims for legacy ATA device names have been removed.
212 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
213 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
214 environment variables, /dev/ad* and /dev/ar* symbolic links.
217 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
218 Please see the 20141231 entry below for information about prerequisites
219 and upgrading, if you are not already using clang 3.5.0 or higher.
222 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
223 and renamed from .symbols to .debug. This reduces the size requirements
224 on the boot partition or file system and provides consistency with
225 userland debug files.
227 When using the supported kernel installation method the
228 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
229 as is done with /boot/kernel.
231 Developers wishing to maintain the historical behavior of installing
232 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
235 The wireless drivers had undergone changes that remove the 'parent
236 interface' from the ifconfig -l output. The rc.d network scripts
237 used to check presence of a parent interface in the list, so old
238 scripts would fail to start wireless networking. Thus, etcupdate(3)
239 or mergemaster(8) run is required after kernel update, to update your
240 rc.d scripts in /etc.
243 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
244 These configurations are now automatically interpreted as
245 'scrub fragment reassemble'.
248 Kernel-loadable modules for the random(4) device are back. To use
249 them, the kernel must have
252 options RANDOM_LOADABLE
254 kldload(8) can then be used to load random_fortuna.ko
255 or random_yarrow.ko. Please note that due to the indirect
256 function calls that the loadable modules need to provide,
257 the build-in variants will be slightly more efficient.
259 The random(4) kernel option RANDOM_DUMMY has been retired due to
260 unpopularity. It was not all that useful anyway.
263 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
264 Control over building the ELF Tool Chain tools is now provided by
265 the WITHOUT_TOOLCHAIN knob.
268 The polarity of Pulse Per Second (PPS) capture events with the
269 uart(4) driver has been corrected. Prior to this change the PPS
270 "assert" event corresponded to the trailing edge of a positive PPS
271 pulse and the "clear" event was the leading edge of the next pulse.
273 As the width of a PPS pulse in a typical GPS receiver is on the
274 order of 1 millisecond, most users will not notice any significant
275 difference with this change.
277 Anyone who has compensated for the historical polarity reversal by
278 configuring a negative offset equal to the pulse width will need to
279 remove that workaround.
282 The default group assigned to /dev/dri entries has been changed
283 from 'wheel' to 'video' with the id of '44'. If you want to have
284 access to the dri devices please add yourself to the video group
287 # pw groupmod video -m $USER
290 The menu.rc and loader.rc files will now be replaced during
291 upgrades. Please migrate local changes to menu.rc.local and
292 loader.rc.local instead.
295 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
296 strings and strip have been removed. The src.conf(5) knob
297 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
300 As ZFS requires more kernel stack pages than is the default on some
301 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
302 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
304 Please consider using 'options KSTACK_PAGES=X' where X is greater
305 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
308 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
309 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
310 default, i.e., they will not contain "::". For example, instead
311 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
312 to have a more specific match, such as different map entries for
313 IPv6:0:0 vs IPv6:0. This change requires that configuration
314 data (including maps, files, classes, custom ruleset, etc.) must
315 use the same format, so make certain such configuration data is
316 upgrading. As a very simple check search for patterns like
317 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
318 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
319 the cf option UseCompressedIPv6Addresses.
322 The default kernel entropy-processing algorithm is now
323 Fortuna, replacing Yarrow.
325 Assuming you have 'device random' in your kernel config
326 file, the configurations allow a kernel option to override
327 this default. You may choose *ONE* of:
329 options RANDOM_YARROW # Legacy /dev/random algorithm.
330 options RANDOM_DUMMY # Blocking-only driver.
332 If you have neither, you get Fortuna. For most people,
333 read no further, Fortuna will give a /dev/random that works
334 like it always used to, and the difference will be irrelevant.
336 If you remove 'device random', you get *NO* kernel-processed
337 entropy at all. This may be acceptable to folks building
338 embedded systems, but has complications. Carry on reading,
339 and it is assumed you know what you need.
341 *PLEASE* read random(4) and random(9) if you are in the
342 habit of tweaking kernel configs, and/or if you are a member
343 of the embedded community, wanting specific and not-usual
344 behaviour from your security subsystems.
346 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
347 random', you will NOT have a functioning /dev/random, and
348 many cryptographic features will not work, including SSH.
349 You may also find strange behaviour from the random(3) set
350 of library functions, in particular sranddev(3), srandomdev(3)
351 and arc4random(3). The reason for this is that the KERN_ARND
352 sysctl only returns entropy if it thinks it has some to
353 share, and with RANDOM_DUMMY or no 'device random' this
357 An additional fix for the issue described in the 20150614 sendmail
358 entry below has been been committed in revision 284717.
361 FreeBSD's old make (fmake) has been removed from the system. It is
362 available as the devel/fmake port or via pkg install fmake.
365 The fix for the issue described in the 20150614 sendmail entry
366 below has been been committed in revision 284436. The work
367 around described in that entry is no longer needed unless the
368 default setting is overridden by a confDH_PARAMETERS configuration
369 setting of '5' or pointing to a 512 bit DH parameter file.
372 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
373 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
374 and devel/kyua to version 0.20+ and adjust any calling code to work
375 with Kyuafile and kyua.
378 The import of openssl to address the FreeBSD-SA-15:10.openssl
379 security advisory includes a change which rejects handshakes
380 with DH parameters below 768 bits. sendmail releases prior
381 to 8.15.2 (not yet released), defaulted to a 512 bit
382 DH parameter setting for client connections. To work around
383 this interoperability, sendmail can be configured to use a
384 2048 bit DH parameter by:
386 1. Edit /etc/mail/`hostname`.mc
387 2. If a setting for confDH_PARAMETERS does not exist or
388 exists and is set to a string beginning with '5',
390 3. If a setting for confDH_PARAMETERS exists and is set to
391 a file path, create a new file with:
392 openssl dhparam -out /path/to/file 2048
393 4. Rebuild the .cf file:
394 cd /etc/mail/; make; make install
396 cd /etc/mail/; make restart
398 A sendmail patch is coming, at which time this file will be
402 Generation of legacy formatted entries have been disabled by default
403 in pwd_mkdb(8), as all base system consumers of the legacy formatted
404 entries were converted to use the new format by default when the new,
405 machine independent format have been added and supported since FreeBSD
408 Please see the pwd_mkdb(8) manual page for further details.
411 Clang and llvm have been upgraded to 3.6.1 release. Please see the
412 20141231 entry below for information about prerequisites and upgrading,
413 if you are not already using 3.5.0 or higher.
416 TI platform code switched to using vendor DTS files and this update
417 may break existing systems running on Beaglebone, Beaglebone Black,
420 - dtb files should be regenerated/reinstalled. Filenames are the
421 same but content is different now
422 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
423 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
424 addressing scheme is now pin 25 on /dev/gpioc3.
425 - Pandaboard: /etc/ttys should be updated, serial console device is
426 now /dev/ttyu2, not /dev/ttyu0
429 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
430 If you need the GNU extension from groff soelim(1), install groff
431 from package: pkg install groff, or via ports: textproc/groff.
434 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
435 defined in symlink(7); previously symlinks were silently ignored.
438 The const qualifier has been removed from iconv(3) to comply with
439 POSIX. The ports tree is aware of this from r384038 onwards.
442 Libraries specified by LIBADD in Makefiles must have a corresponding
443 DPADD_<lib> variable to ensure correct dependencies. This is now
444 enforced in src.libnames.mk.
447 From legacy ata(4) driver was removed support for SATA controllers
448 supported by more functional drivers ahci(4), siis(4) and mvs(4).
449 Kernel modules ataahci and ataadaptec were removed completely,
450 replaced by ahci and mvs modules respectively.
453 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
454 the 20141231 entry below for information about prerequisites and
455 upgrading, if you are not already using 3.5.0 or higher.
458 The 32-bit PowerPC kernel has been changed to a position-independent
459 executable. This can only be booted with a version of loader(8)
460 newer than January 31, 2015, so make sure to update both world and
461 kernel before rebooting.
464 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
465 but before r278950, the RNG was not seeded properly. Immediately
466 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
467 ssh keys or openssl keys) that were generated w/ a kernel from that
468 range. This does not affect programs that directly used /dev/random
469 or /dev/urandom. All userland uses of arc4random(3) are affected.
472 The autofs(4) ABI was changed in order to restore binary compatibility
473 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
477 The powerpc64 kernel has been changed to a position-independent
478 executable. This can only be booted with a new version of loader(8),
479 so make sure to update both world and kernel before rebooting.
482 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
483 only release, no new features have been added. Please see the 20141231
484 entry below for information about prerequisites and upgrading, if you
485 are not already using 3.5.0.
488 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
489 taken from the ELF Tool Chain project rather than GNU binutils. They
490 should be drop-in replacements, with the addition of arm64 support.
491 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
492 binutils tools, if necessary. See 20150805 for updated information.
495 The default Unbound configuration now enables remote control
496 using a local socket. Users who have already enabled the
497 local_unbound service should regenerate their configuration
498 by running "service local_unbound setup" as root.
501 The GNU texinfo and GNU info pages have been removed.
502 To be able to view GNU info pages please install texinfo from ports.
505 Clang, llvm and lldb have been upgraded to 3.5.0 release.
507 As of this release, a prerequisite for building clang, llvm and lldb is
508 a C++11 capable compiler and C++11 standard library. This means that to
509 be able to successfully build the cross-tools stage of buildworld, with
510 clang as the bootstrap compiler, your system compiler or cross compiler
511 should either be clang 3.3 or later, or gcc 4.8 or later, and your
512 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
515 On any standard FreeBSD 10.x or 11.x installation, where clang and
516 libc++ are on by default (that is, on x86 or arm), this should work out
519 On 9.x installations where clang is enabled by default, e.g. on x86 and
520 powerpc, libc++ will not be enabled by default, so libc++ should be
521 built (with clang) and installed first. If both clang and libc++ are
522 missing, build clang first, then use it to build libc++.
524 On 8.x and earlier installations, upgrade to 9.x first, and then follow
525 the instructions for 9.x above.
527 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
528 default, and do not build clang.
530 Many embedded systems are resource constrained, and will not be able to
531 build clang in a reasonable time, or in some cases at all. In those
532 cases, cross building bootable systems on amd64 is a workaround.
534 This new version of clang introduces a number of new warnings, of which
535 the following are most likely to appear:
539 This warns in two cases, for both C and C++:
540 * When the code is trying to take the absolute value of an unsigned
541 quantity, which is effectively a no-op, and almost never what was
542 intended. The code should be fixed, if at all possible. If you are
543 sure that the unsigned quantity can be safely cast to signed, without
544 loss of information or undefined behavior, you can add an explicit
545 cast, or disable the warning.
547 * When the code is trying to take an absolute value, but the called
548 abs() variant is for the wrong type, which can lead to truncation.
549 If you want to disable the warning instead of fixing the code, please
550 make sure that truncation will not occur, or it might lead to unwanted
553 -Wtautological-undefined-compare and
554 -Wundefined-bool-conversion
556 These warn when C++ code is trying to compare 'this' against NULL, while
557 'this' should never be NULL in well-defined C++ code. However, there is
558 some legacy (pre C++11) code out there, which actively abuses this
559 feature, which was less strictly defined in previous C++ versions.
561 Squid and openjdk do this, for example. The warning can be turned off
562 for C++98 and earlier, but compiling the code in C++11 mode might result
563 in unexpected behavior; for example, the parts of the program that are
564 unreachable could be optimized away.
567 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
568 kernel sources have been removed. The .h files remain, since some
569 utilities include them. This will need to be fixed later.
570 If "mount -t oldnfs ..." is attempted, it will fail.
571 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
572 the utilities will report errors.
575 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
576 directories to top level SUBDIR variable when their parent
577 directory is included in LOCAL_DIRS. Users with build systems with
578 such hierarchies and without SUBDIR entries in the parent
579 directory Makefiles should add them or add the directories to
583 faith(4) and faithd(8) have been removed from the base system. Faith
584 has been obsolete for a very long time.
587 vt(4), the new console driver, is enabled by default. It brings
588 support for Unicode and double-width characters, as well as
589 support for UEFI and integration with the KMS kernel video
592 You may need to update your console settings in /etc/rc.conf,
593 most probably the keymap. During boot, /etc/rc.d/syscons will
594 indicate what you need to do.
596 vt(4) still has issues and lacks some features compared to
597 syscons(4). See the wiki for up-to-date information:
598 https://wiki.freebsd.org/Newcons
600 If you want to keep using syscons(4), you can do so by adding
601 the following line to /boot/loader.conf:
605 pjdfstest has been integrated into kyua as an opt-in test suite.
606 Please see share/doc/pjdfstest/README for more details on how to
610 gperf has been removed from the base system for architectures
611 that use clang. Ports that require gperf will obtain it from the
615 pjdfstest has been moved from tools/regression/pjdfstest to
619 At svn r271982, The default linux compat kernel ABI has been adjusted
620 to 2.6.18 in support of the linux-c6 compat ports infrastructure
621 update. If you wish to continue using the linux-f10 compat ports,
622 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
623 encouraged to update their linux-compat packages to linux-c6 during
624 their next update cycle.
627 The ofwfb driver, used to provide a graphics console on PowerPC when
628 using vt(4), no longer allows mmap() of all physical memory. This
629 will prevent Xorg on PowerPC with some ATI graphics cards from
630 initializing properly unless x11-servers/xorg-server is updated to
634 The xdev targets have been converted to using TARGET and
635 TARGET_ARCH instead of XDEV and XDEV_ARCH.
638 The default unbound configuration has been modified to address
639 issues with reverse lookups on networks that use private
640 address ranges. If you use the local_unbound service, run
641 "service local_unbound setup" as root to regenerate your
642 configuration, then "service local_unbound reload" to load the
646 The GNU texinfo and GNU info pages are not built and installed
647 anymore, WITH_INFO knob has been added to allow to built and install
649 UPDATE: see 20150102 entry on texinfo's removal
652 The GNU readline library is now an INTERNALLIB - that is, it is
653 statically linked into consumers (GDB and variants) in the base
654 system, and the shared library is no longer installed. The
655 devel/readline port is available for third party software that
659 The Itanium architecture (ia64) has been removed from the list of
660 known architectures. This is the first step in the removal of the
664 Commit r268115 has added NFSv4.1 server support, merged from
665 projects/nfsv4.1-server. Since this includes changes to the
666 internal interfaces between the NFS related modules, a full
667 build of the kernel and modules will be necessary.
668 __FreeBSD_version has been bumped.
671 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
672 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
673 which differs from the behaviour controlled by this knob.)
676 Maximal length of the serial number in CTL was increased from 16 to
677 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
678 and ctld, need to be rebuilt to work with a new kernel.
681 The libatf-c and libatf-c++ major versions were downgraded to 0 and
682 1 respectively to match the upstream numbers. They were out of
683 sync because, when they were originally added to FreeBSD, the
684 upstream versions were not respected. These libraries are private
685 and not yet built by default, so renumbering them should be a
686 non-issue. However, unclean source trees will yield broken test
687 programs once the operator executes "make delete-old-libs" after a
690 Additionally, the atf-sh binary was made private by moving it into
691 /usr/libexec/. Already-built shell test programs will keep the
692 path to the old binary so they will break after "make delete-old"
695 If you are using WITH_TESTS=yes (not the default), wipe the object
696 tree and rebuild from scratch to prevent spurious test failures.
697 This is only needed once: the misnumbered libraries and misplaced
698 binaries have been added to OptionalObsoleteFiles.inc so they will
699 be removed during a clean upgrade.
702 Clang and llvm have been upgraded to 3.4.1 release.
705 We bogusly installed src.opts.mk in /usr/share/mk. This file should
706 be removed to avoid issues in the future (and has been added to
710 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
711 past, it affected all builds that used the bsd.*.mk files. The old
712 behavior was a bug, but people may have relied upon it. To get this
713 behavior back, you can .include /etc/src.conf from /etc/make.conf
714 (which is still global and isn't changed). This also changes the
715 behavior of incremental builds inside the tree of individual
716 directories. Set MAKESYSPATH to ".../share/mk" to do that.
717 Although this has survived make universe and some upgrade scenarios,
718 other upgrade scenarios may have broken. At least one form of
719 temporary breakage was fixed with MAKESYSPATH settings for buildworld
720 as well... In cases where MAKESYSPATH isn't working with this
721 setting, you'll need to set it to the full path to your tree.
723 One side effect of all this cleaning up is that bsd.compiler.mk
724 is no longer implicitly included by bsd.own.mk. If you wish to
725 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
729 The lindev device has been removed since /dev/full has been made a
730 standard device. __FreeBSD_version has been bumped.
733 The knob WITHOUT_VI was added to the base system, which controls
734 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
735 in order to reorder files share/termcap and didn't build ex(1) as a
736 build tool, so building/installing with WITH_VI is highly advised for
737 build hosts for older releases.
739 This issue has been fixed in stable/9 and stable/10 in r277022 and
740 r276991, respectively.
743 The YES_HESIOD knob has been removed. It has been obsolete for
744 a decade. Please move to using WITH_HESIOD instead or your builds
745 will silently lack HESIOD.
748 The uart(4) driver has been changed with respect to its handling
749 of the low-level console. Previously the uart(4) driver prevented
750 any process from changing the baudrate or the CLOCAL and HUPCL
751 control flags. By removing the restrictions, operators can make
752 changes to the serial console port without having to reboot.
753 However, when getty(8) is started on the serial device that is
754 associated with the low-level console, a misconfigured terminal
755 line in /etc/ttys will now have a real impact.
756 Before upgrading the kernel, make sure that /etc/ttys has the
757 serial console device configured as 3wire without baudrate to
758 preserve the previous behaviour. E.g:
759 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
762 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
763 to improve performance. To re-enable it, if needed, run rpcbind
764 with command line option -W.
767 Switched back to the GPL dtc compiler due to updates in the upstream
768 dts files not being supported by the BSDL dtc compiler. You will need
769 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
770 may result while building dtb files during a kernel build if you fail
771 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
774 Clang and llvm have been upgraded to 3.4 release.
777 The nve(4) driver has been removed. Please use the nfe(4) driver
778 for NVIDIA nForce MCP Ethernet adapters instead.
781 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
782 This could cause certain C++ applications using shared libraries built
783 against the previous version of libc++ to crash. The incompatibility
784 has now been fixed, but any C++ applications or shared libraries built
785 between r261283 and r261801 should be recompiled.
788 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
789 capability mode support. Please note that enabling the feature in
790 kernel is still highly recommended.
793 OpenSSH is now built with sandbox support, and will use sandbox as
794 the default privilege separation method. This requires Capsicum
795 capability mode support in kernel.
798 The libelf and libdwarf libraries have been updated to newer
799 versions from upstream. Shared library version numbers for
800 these two libraries were bumped. Any ports or binaries
801 requiring these two libraries should be recompiled.
802 __FreeBSD_version is bumped to 1100006.
805 If a Makefile in a tests/ directory was auto-generating a Kyuafile
806 instead of providing an explicit one, this would prevent such
807 Makefile from providing its own Kyuafile in the future during
808 NO_CLEAN builds. This has been fixed in the Makefiles but manual
809 intervention is needed to clean an objdir if you use NO_CLEAN:
810 # find /usr/obj -name Kyuafile | xargs rm -f
813 The behavior of gss_pseudo_random() for the krb5 mechanism
814 has changed, for applications requesting a longer random string
815 than produced by the underlying enctype's pseudo-random() function.
816 In particular, the random string produced from a session key of
817 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
818 be different at the 17th octet and later, after this change.
819 The counter used in the PRF+ construction is now encoded as a
820 big-endian integer in accordance with RFC 4402.
821 __FreeBSD_version is bumped to 1100004.
824 The WITHOUT_ATF build knob has been removed and its functionality
825 has been subsumed into the more generic WITHOUT_TESTS. If you were
826 using the former to disable the build of the ATF libraries, you
827 should change your settings to use the latter.
830 The default version of mtree is nmtree which is obtained from
831 NetBSD. The output is generally the same, but may vary
832 slightly. If you found you need identical output adding
833 "-F freebsd9" to the command line should do the trick. For the
834 time being, the old mtree is available as fmtree.
837 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
838 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
839 1.1.4_8 and verify bsdyml not linked in, before running "make
841 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
843 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
846 The stable/10 branch has been created in subversion from head
850 The rc.d/jail script has been updated to support jail(8)
851 configuration file. The "jail_<jname>_*" rc.conf(5) variables
852 for per-jail configuration are automatically converted to
853 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
854 This is transparently backward compatible. See below about some
855 incompatibilities and rc.conf(5) manual page for more details.
857 These variables are now deprecated in favor of jail(8) configuration
858 file. One can use "rc.d/jail config <jname>" command to generate
859 a jail(8) configuration file in /var/run/jail.<jname>.conf without
860 running the jail(8) utility. The default pathname of the
861 configuration file is /etc/jail.conf and can be specified by
862 using $jail_conf or $jail_<jname>_conf variables.
864 Please note that jail_devfs_ruleset accepts an integer at
865 this moment. Please consider to rewrite the ruleset name
869 BIND has been removed from the base system. If all you need
870 is a local resolver, simply enable and start the local_unbound
871 service instead. Otherwise, several versions of BIND are
872 available in the ports tree. The dns/bind99 port is one example.
874 With this change, nslookup(1) and dig(1) are no longer in the base
875 system. Users should instead use host(1) and drill(1) which are
876 in the base system. Alternatively, nslookup and dig can
877 be obtained by installing the dns/bind-tools port.
880 With the addition of unbound(8), a new unbound user is now
881 required during installworld. "mergemaster -p" can be used to
882 add the user prior to installworld, as documented in the handbook.
885 OpenSSH is now built with DNSSEC support, and will by default
886 silently trust signed SSHFP records. This can be controlled with
887 the VerifyHostKeyDNS client configuration setting. DNSSEC support
888 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
891 The GNU Compiler Collection and C++ standard library (libstdc++)
892 are no longer built by default on platforms where clang is the system
893 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
897 The PROCDESC kernel option is now part of the GENERIC kernel
898 configuration and is required for the rwhod(8) to work.
899 If you are using custom kernel configuration, you should include
903 The API and ABI related to the Capsicum framework was modified
904 in backward incompatible way. The userland libraries and programs
905 have to be recompiled to work with the new kernel. This includes the
906 following libraries and programs, but the whole buildworld is
907 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
908 kdump, procstat, rwho, rwhod, uniq.
911 AES-NI intrinsic support has been added to gcc. The AES-NI module
912 has been updated to use this support. A new gcc is required to build
913 the aesni module on both i386 and amd64.
916 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
917 Thus "device padlock_rng" and "device rdrand_rng" should be
918 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
921 WITH_ICONV has been split into two feature sets. WITH_ICONV now
922 enables just the iconv* functionality and is now on by default.
923 WITH_LIBICONV_COMPAT enables the libiconv api and link time
924 compatibility. Set WITHOUT_ICONV to build the old way.
925 If you have been using WITH_ICONV before, you will very likely
926 need to turn on WITH_LIBICONV_COMPAT.
929 INVARIANTS option now enables DEBUG for code with OpenSolaris and
930 Illumos origin, including ZFS. If you have INVARIANTS in your
931 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
933 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
934 locks if WITNESS option was set. Because that generated a lot of
935 witness(9) reports and all of them were believed to be false
936 positives, this is no longer done. New option OPENSOLARIS_WITNESS
937 can be used to achieve the previous behavior.
940 Timer values in IPv6 data structures now use time_uptime instead
941 of time_second. Although this is not a user-visible functional
942 change, userland utilities which directly use them---ndp(8),
943 rtadvd(8), and rtsold(8) in the base system---need to be updated
947 find -delete can now delete the pathnames given as arguments,
948 instead of only files found below them or if the pathname did
949 not contain any slashes. Formerly, the following error message
952 find: -delete: <path>: relative path potentially not safe
954 Deleting the pathnames given as arguments can be prevented
955 without error messages using -mindepth 1 or by changing
956 directory and passing "." as argument to find. This works in the
957 old as well as the new version of find.
960 Behavior of devfs rules path matching has been changed.
961 Pattern is now always matched against fully qualified devfs
962 path and slash characters must be explicitly matched by
963 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
964 subdirectories must be reviewed.
967 The default ARM ABI has changed to the ARM EABI. The old ABI is
968 incompatible with the ARM EABI and all programs and modules will
969 need to be rebuilt to work with a new kernel.
971 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
973 NOTE: Support for the old ABI will be removed in the future and
974 users are advised to upgrade.
977 pkg_install has been disconnected from the build if you really need it
978 you should add WITH_PKGTOOLS in your src.conf(5).
981 Most of network statistics structures were changed to be able
982 keep 64-bits counters. Thus all tools, that work with networking
983 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
986 Fix a bug that allowed a tracing process (e.g. gdb) to write
987 to a memory-mapped file in the traced process's address space
988 even if neither the traced process nor the tracing process had
989 write access to that file.
992 CVS has been removed from the base system. An exact copy
993 of the code is available from the devel/cvs port.
996 Some people report the following error after the switch to bmake:
998 make: illegal option -- J
999 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1001 *** [buildworld] Error code 2
1003 this likely due to an old instance of make in
1004 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1005 which src/Makefile will use that blindly, if it exists, so if
1006 you see the above error:
1008 rm -rf `make -V MAKEPATH`
1013 Use bmake by default.
1014 Whereas before one could choose to build with bmake via
1015 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1016 make. The goal is to remove these knobs for 10-RELEASE.
1018 It is worth noting that bmake (like gmake) treats the command
1019 line as the unit of failure, rather than statements within the
1020 command line. Thus '(cd some/where && dosomething)' is safer
1021 than 'cd some/where; dosomething'. The '()' allows consistent
1022 behavior in parallel build.
1025 Fix a bug that allows NFS clients to issue READDIR on files.
1028 The WITHOUT_IDEA option has been removed because
1029 the IDEA patent expired.
1032 The sysctl which controls TRIM support under ZFS has been renamed
1033 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1037 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1038 rather than creating it's own in the temporary directory in
1039 order allow access to bootstrapped versions of tools such as
1040 install and mtree. When upgrading from version of FreeBSD where
1041 the install command does not support -l, you will need to
1042 install a new mergemaster command if mergemaster -p is required.
1043 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1047 Legacy ATA stack, disabled and replaced by new CAM-based one since
1048 FreeBSD 9.0, completely removed from the sources. Kernel modules
1049 atadisk and atapi*, user-level tools atacontrol and burncd are
1050 removed. Kernel option `options ATA_CAM` is now permanently enabled
1054 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1055 and socketpair(2). Software, in particular Kerberos, may
1056 automatically detect and use these during building. The resulting
1057 binaries will not work on older kernels.
1060 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1061 information, see the respective 20130304 entry).
1064 Recent commits to callout(9) changed the size of struct callout,
1065 so the KBI is probably heavily disturbed. Also, some functions
1066 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1067 by macros. Every kernel module using it won't load, so rebuild
1070 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1071 but does not initialize by default (because of the new CTL_DISABLE
1072 option) to save memory. To re-enable it, remove the CTL_DISABLE
1073 option from the kernel config file or set kern.cam.ctl.disable=0
1074 in /boot/loader.conf.
1077 The ctl device has been disabled in GENERIC for i386 and amd64.
1078 This was done due to the extra memory being allocated at system
1079 initialisation time by the ctl driver which was only used if
1080 a CAM target device was created. This makes a FreeBSD system
1081 unusable on 128MB or less of RAM.
1084 A new compression method (lz4) has been merged to -HEAD. Please
1085 refer to zpool-features(7) for more information.
1087 Please refer to the "ZFS notes" section of this file for information
1088 on upgrading boot ZFS pools.
1091 A BSD-licensed patch(1) variant has been added and is installed
1092 as bsdpatch, being the GNU version the default patch.
1093 To inverse the logic and use the BSD-licensed one as default,
1094 while having the GNU version installed as gnupatch, rebuild
1095 and install world with the WITH_BSD_PATCH knob set.
1098 Due to the use of the new -l option to install(1) during build
1099 and install, you must take care not to directly set the INSTALL
1100 make variable in your /etc/make.conf, /etc/src.conf, or on the
1101 command line. If you wish to use the -C flag for all installs
1102 you may be able to add INSTALL+=-C to /etc/make.conf or
1106 The install(1) option -M has changed meaning and now takes an
1107 argument that is a file or path to append logs to. In the
1108 unlikely event that -M was the last option on the command line
1109 and the command line contained at least two files and a target
1110 directory the first file will have logs appended to it. The -M
1111 option served little practical purpose in the last decade so its
1112 use is expected to be extremely rare.
1115 After switching to Clang as the default compiler some users of ZFS
1116 on i386 systems started to experience stack overflow kernel panics.
1117 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1120 GEOM_LABEL now mangles label names read from file system metadata.
1121 Mangling affect labels containing spaces, non-printable characters,
1122 '%' or '"'. Device names in /etc/fstab and other places may need to
1126 By default, only the 10 most recent kernel dumps will be saved. To
1127 restore the previous behaviour (no limit on the number of kernel dumps
1128 stored in the dump directory) add the following line to /etc/rc.conf:
1133 With the addition of auditdistd(8), a new auditdistd user is now
1134 required during installworld. "mergemaster -p" can be used to
1135 add the user prior to installworld, as documented in the handbook.
1138 The sin6_scope_id member variable in struct sockaddr_in6 is now
1139 filled by the kernel before passing the structure to the userland via
1140 sysctl or routing socket. This means the KAME-specific embedded scope
1141 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1142 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1143 __FreeBSD_version is bumped to 1000025.
1146 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1147 This means that the world and kernel will be compiled with clang
1148 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1149 and /usr/bin/cpp. To disable this behavior and revert to building
1150 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1151 of current may need to bootstrap WITHOUT_CLANG first if the clang
1152 build fails (its compatibility window doesn't extend to the 9 stable
1156 The IPFIREWALL_FORWARD kernel option has been removed. Its
1157 functionality now turned on by default.
1160 The ZERO_COPY_SOCKET kernel option has been removed and
1161 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1162 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1163 mechanism which is not safe and may result in kernel crashes.
1164 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1165 driver supports disposeable external page sized mbuf storage.
1166 Proper replacements for both zero-copy mechanisms are under
1167 consideration and will eventually lead to complete removal
1168 of the two kernel options.
1171 The IPv4 network stack has been converted to network byte
1172 order. The following modules need to be recompiled together
1173 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1174 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1177 Support for non-MPSAFE filesystems was removed from VFS. The
1178 VFS_VERSION was bumped, all filesystem modules shall be
1182 All the non-MPSAFE filesystems have been disconnected from
1183 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1184 portalfs, smbfs, xfs.
1187 The interface cloning API and ABI has changed. The following
1188 modules need to be recompiled together with kernel:
1189 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1190 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1191 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1194 The sdhci driver was split in two parts: sdhci (generic SD Host
1195 Controller logic) and sdhci_pci (actual hardware driver).
1196 No kernel config modifications are required, but if you
1197 load sdhc as a module you must switch to sdhci_pci instead.
1200 Import the FUSE kernel and userland support into base system.
1203 The GNU sort(1) program has been removed since the BSD-licensed
1204 sort(1) has been the default for quite some time and no serious
1205 problems have been reported. The corresponding WITH_GNU_SORT
1209 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1210 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1214 The net80211(4) ABI has been changed to allow for improved driver
1215 PS-POLL and power-save support. All wireless drivers need to be
1216 recompiled to work with the new kernel.
1219 The random(4) support for the VIA hardware random number
1220 generator (`PADLOCK') is no longer enabled unconditionally.
1221 Add the padlock_rng device in the custom kernel config if
1222 needed. The GENERIC kernels on i386 and amd64 do include the
1223 device, so the change only affects the custom kernel
1227 The pf(4) packet filter ABI has been changed. pfctl(8) and
1228 snmp_pf module need to be recompiled to work with new kernel.
1231 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1232 to -HEAD. Pools that have empty_bpobj in active state can not be
1233 imported read-write with ZFS implementations that do not support
1234 this feature. For more information read the zpool-features(5)
1238 The sparc64 ZFS loader has been changed to no longer try to auto-
1239 detect ZFS providers based on diskN aliases but now requires these
1240 to be explicitly listed in the OFW boot-device environment variable.
1243 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1244 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1245 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1248 The following sysctls and tunables have been renamed for consistency
1249 with other variables:
1250 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1251 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1254 The sort utility has been replaced with BSD sort. For now, GNU sort
1255 is also available as "gnusort" or the default can be set back to
1256 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1257 installed as "bsdsort".
1260 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1261 Starting with this version the old system of ZFS pool versioning
1262 is superseded by "feature flags". This concept enables forward
1263 compatibility against certain future changes in functionality of ZFS
1264 pools. The first read-only compatible "feature flag" for ZFS pools
1265 is named "com.delphix:async_destroy". For more information
1266 read the new zpool-features(5) manual page.
1267 Please refer to the "ZFS notes" section of this file for information
1268 on upgrading boot ZFS pools.
1271 The malloc(3) implementation embedded in libc now uses sources imported
1272 as contrib/jemalloc. The most disruptive API change is to
1273 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1274 delete it prior to installworld, and optionally re-create it using the
1275 new format after rebooting. See malloc.conf(5) for details
1276 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1280 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1281 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1282 now spelled mips. This is to aid compatibility with third-party
1283 software that expects this naming scheme in uname(3). Little-endian
1284 settings are unchanged. If you are updating a big-endian mips64 machine
1285 from before this change, you may need to set MACHINE_ARCH=mips64 in
1286 your environment before the new build system will recognize your machine.
1289 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1293 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1294 nullfs(5) did not pass through all behaviours to the underlying layer,
1295 as a result if we bound to a socket on the lower layer we could connect
1296 only to the lower path; if we bound to the upper layer we could connect
1297 only to the upper path. The new behavior is one can connect to both the
1298 lower and the upper paths regardless what layer path one binds to.
1301 The getifaddrs upgrade path broken with 20111215 has been restored.
1302 If you have upgraded in between 20111215 and 20120209 you need to
1303 recompile libc again with your kernel. You still need to recompile
1304 world to be able to configure CARP but this restriction already
1305 comes from 20111215.
1308 The set_rcvar() function has been removed from /etc/rc.subr. All
1309 base and ports rc.d scripts have been updated, so if you have a
1310 port installed with a script in /usr/local/etc/rc.d you can either
1311 hand-edit the rcvar= line, or reinstall the port.
1313 An easy way to handle the mass-update of /etc/rc.d:
1314 rm /etc/rc.d/* && mergemaster -i
1317 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1318 on the current CPU and prevents other threads from running.
1319 This behavior can be reverted using the kern.stop_scheduler_on_panic
1321 The new behavior can be incompatible with kern.sync_on_panic.
1324 The carp(4) facility has been changed significantly. Configuration
1325 of the CARP protocol via ifconfig(8) has changed, as well as format
1326 of CARP events submitted to devd(8) has changed. See manual pages
1327 for more information. The arpbalance feature of carp(4) is currently
1328 not supported anymore.
1330 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1331 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1332 need to be recompiled.
1335 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1339 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1340 explicitely support non-MPSAFE filesystems.
1341 It is on by default for all supported platform at this present
1345 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1346 i386 and pc98 GENERIC kernel configuration files.
1349 sysinstall has been removed
1352 The stable/9 branch created in subversion. This corresponds to the
1353 RELENG_9 branch in CVS.
1359 Avoid using make -j when upgrading. While generally safe, there are
1360 sometimes problems using -j to upgrade. If your upgrade fails with
1361 -j, please try again without -j. From time to time in the past there
1362 have been problems using -j with buildworld and/or installworld. This
1363 is especially true when upgrading between "distant" versions (eg one
1364 that cross a major release boundary or several minor releases, or when
1365 several months have passed on the -current branch).
1367 Sometimes, obscure build problems are the result of environment
1368 poisoning. This can happen because the make utility reads its
1369 environment when searching for values for global variables. To run
1370 your build attempts in an "environmental clean room", prefix all make
1371 commands with 'env -i '. See the env(1) manual page for more details.
1373 When upgrading from one major version to another it is generally best
1374 to upgrade to the latest code in the currently installed branch first,
1375 then do an upgrade to the new branch. This is the best-tested upgrade
1376 path, and has the highest probability of being successful. Please try
1377 this approach before reporting problems with a major version upgrade.
1379 When upgrading a live system, having a root shell around before
1380 installing anything can help undo problems. Not having a root shell
1381 around can lead to problems if pam has changed too much from your
1382 starting point to allow continued authentication after the upgrade.
1384 This file should be read as a log of events. When a later event changes
1385 information of a prior event, the prior event should not be deleted.
1386 Instead, a pointer to the entry with the new information should be
1387 placed in the old entry. Readers of this file should also sanity check
1388 older entries before relying on them blindly. Authors of new entries
1389 should write them with this in mind.
1393 When upgrading the boot ZFS pool to a new version, always follow
1396 1.) recompile and reinstall the ZFS boot loader and boot block
1397 (this is part of "make buildworld" and "make installworld")
1399 2.) update the ZFS boot block on your boot drive
1401 The following example updates the ZFS boot block on the first
1402 partition (freebsd-boot) of a GPT partitioned drive ada0:
1403 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1405 Non-boot pools do not need these updates.
1409 If you are updating from a prior version of FreeBSD (even one just
1410 a few days old), you should follow this procedure. It is the most
1411 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1413 make kernel-toolchain
1414 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1415 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1417 To test a kernel once
1418 ---------------------
1419 If you just want to boot a kernel once (because you are not sure
1420 if it works, or if you want to boot a known bad kernel to provide
1421 debugging information) run
1422 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1423 nextboot -k testkernel
1425 To just build a kernel when you know that it won't mess you up
1426 --------------------------------------------------------------
1427 This assumes you are already running a CURRENT system. Replace
1428 ${arch} with the architecture of your machine (e.g. "i386",
1429 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1431 cd src/sys/${arch}/conf
1432 config KERNEL_NAME_HERE
1433 cd ../compile/KERNEL_NAME_HERE
1438 If this fails, go to the "To build a kernel" section.
1440 To rebuild everything and install it on the current system.
1441 -----------------------------------------------------------
1442 # Note: sometimes if you are running current you gotta do more than
1443 # is listed here if you are upgrading from a really old current.
1445 <make sure you have good level 0 dumps>
1447 make kernel KERNCONF=YOUR_KERNEL_HERE
1449 <reboot in single user> [3]
1456 To cross-install current onto a separate partition
1457 --------------------------------------------------
1458 # In this approach we use a separate partition to hold
1459 # current's root, 'usr', and 'var' directories. A partition
1460 # holding "/", "/usr" and "/var" should be about 2GB in
1463 <make sure you have good level 0 dumps>
1466 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1467 <maybe newfs current's root partition>
1468 <mount current's root partition on directory ${CURRENT_ROOT}>
1469 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1470 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1471 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1472 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1473 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1474 <reboot into current>
1475 <do a "native" rebuild/install as described in the previous section>
1476 <maybe install compatibility libraries from ports/misc/compat*>
1480 To upgrade in-place from stable to current
1481 ----------------------------------------------
1482 <make sure you have good level 0 dumps>
1484 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1486 <reboot in single user> [3]
1493 Make sure that you've read the UPDATING file to understand the
1494 tweaks to various things you need. At this point in the life
1495 cycle of current, things change often and you are on your own
1496 to cope. The defaults can also change, so please read ALL of
1497 the UPDATING entries.
1499 Also, if you are tracking -current, you must be subscribed to
1500 freebsd-current@freebsd.org. Make sure that before you update
1501 your sources that you have read and understood all the recent
1502 messages there. If in doubt, please track -stable which has
1503 much fewer pitfalls.
1505 [1] If you have third party modules, such as vmware, you
1506 should disable them at this point so they don't crash your
1509 [3] From the bootblocks, boot -s, and then do
1514 adjkerntz -i # if CMOS is wall time
1515 Also, when doing a major release upgrade, it is required that
1516 you boot into single user mode to do the installworld.
1518 [4] Note: This step is non-optional. Failure to do this step
1519 can result in a significant reduction in the functionality of the
1520 system. Attempting to do it by hand is not recommended and those
1521 that pursue this avenue should read this file carefully, as well
1522 as the archives of freebsd-current and freebsd-hackers mailing lists
1523 for potential gotchas. The -U option is also useful to consider.
1524 See mergemaster(8) for more information.
1526 [5] Usually this step is a noop. However, from time to time
1527 you may need to do this if you get unknown user in the following
1528 step. It never hurts to do it all the time. You may need to
1529 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1530 install) after the buildworld before this step if you last updated
1531 from current before 20130425 or from -stable before 20130430.
1533 [6] This only deletes old files and directories. Old libraries
1534 can be deleted by "make delete-old-libs", but you have to make
1535 sure that no program is using those libraries anymore.
1537 [8] In order to have a kernel that can run the 4.x binaries needed to
1538 do an installworld, you must include the COMPAT_FREEBSD4 option in
1539 your kernel. Failure to do so may leave you with a system that is
1540 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1541 required to run the 5.x binaries on more recent kernels. And so on
1542 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1544 Make sure that you merge any new devices from GENERIC since the
1545 last time you updated your kernel config file.
1547 [9] When checking out sources, you must include the -P flag to have
1548 cvs prune empty directories.
1550 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1551 "?=" instead of the "=" assignment operator, so that buildworld can
1552 override the CPUTYPE if it needs to.
1554 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1555 not on the command line, or in /etc/make.conf. buildworld will
1556 warn if it is improperly defined.
1559 This file contains a list, in reverse chronological order, of major
1560 breakages in tracking -current. It is not guaranteed to be a complete
1561 list of such breakages, and only contains entries since September 23, 2011.
1562 If you need to see UPDATING entries from before that date, you will need
1563 to fetch an UPDATING file from an older FreeBSD release.
1565 Copyright information:
1567 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1569 Redistribution, publication, translation and use, with or without
1570 modification, in full or in part, in any form or format of this
1571 document are permitted without further permission from the author.
1573 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1574 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1575 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1576 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1577 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1578 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1579 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1580 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1581 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1582 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1583 POSSIBILITY OF SUCH DAMAGE.
1585 Contact Warner Losh if you have any questions about your use of