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.
20 The libc stub for the pipe(2) system call has been replaced with
21 a wrapper that calls the pipe2(2) system call and the pipe(2)
22 system call is now only implemented by the kernels that include
23 "options COMPAT_FREEBSD10" in their config file (this is the
24 default). Users should ensure that this option is enabled in
25 their kernel or upgrade userspace to r302092 before upgrading their
29 CAM will now strip leading spaces from SCSI disks' serial numbers.
30 This will effect users who create UFS filesystems on SCSI disks using
31 those disk's diskid device nodes. For example, if /etc/fstab
32 previously contained a line like
33 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
34 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
35 transforms like gmirror may also be affected. ZFS users should
39 The bitstring(3) API has been updated with new functionality and
40 improved performance. But it is binary-incompatible with the old API.
41 Objects built with the new headers may not be linked against objects
42 built with the old headers.
45 The brk and sbrk functions have been removed from libc on arm64.
46 Binutils from ports has been updated to not link to these
47 functions and should be updated to the latest version before
48 installing a new libc.
51 The armv6 port now defaults to hard float ABI. Limited support
52 for running both hardfloat and soft float on the same system
53 is available using the libraries installed with -DWITH_LIBSOFT.
54 This has only been tested as an upgrade path for installworld
55 and packages may fail or need manual intervention to run. New
56 packages will be needed.
58 To update an existing self-hosted armv6hf system, you must add
59 TARGET_ARCH=armv6 on the make command line for both the build
60 and the install steps.
63 Kernel modules compiled outside of a kernel build now default to
64 installing to /boot/modules instead of /boot/kernel. Many kernel
65 modules built this way (such as those in ports) already overrode
66 KMODDIR explicitly to install into /boot/modules. However,
67 manually building and installing a module from /sys/modules will
68 now install to /boot/modules instead of /boot/kernel.
71 The CAM I/O scheduler has been committed to the kernel. There should be
72 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
73 list of known rogues that claim support for this but actually corrupt
74 data is believed to be complete, be on the lookout for data
75 corruption. The known rogue list is believed to be complete:
77 o Crucial MX100, M550 drives with MU01 firmware.
78 o Micron M510 and M550 drives with MU01 firmware.
79 o Micron M500 prior to MU07 firmware
80 o Samsung 830, 840, and 850 all firmwares
81 o FCCT M500 all firmwares
83 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
84 with working NCQ TRIM. For Micron branded drives, see your sales rep for
85 updated firmware. Black listed drives will work correctly because these
86 drives work correctly so long as no NCQ TRIMs are sent to them. Given
87 this list is the same as found in Linux, it's believed there are no
88 other rogues in the market place. All other models from the above
91 To be safe, if you are at all concerned, you can quirk each of your
92 drives to prevent NCQ from being sent by setting:
93 kern.cam.ada.X.quirks="0x2"
94 in loader.conf. If the drive requires the 4k sector quirk, set the
98 The FAST_DEPEND build option has been removed and its functionality is
99 now the one true way. The old mkdep(1) style of 'make depend' has
100 been removed. See 20160311 for further details.
103 Resource range types have grown from unsigned long to uintmax_t. All
104 drivers, and anything using libdevinfo, need to be recompiled.
107 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
108 builds. It no longer runs mkdep(1) during 'make depend', and the
109 'make depend' stage can safely be skipped now as it is auto ran
110 when building 'make all' and will generate all SRCS and DPSRCS before
111 building anything else. Dependencies are gathered at compile time with
112 -MF flags kept in separate .depend files per object file. Users should
113 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
117 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
118 kernel modules. Therefore, if you load any kernel modules at boot time,
119 please install the boot loaders after you install the kernel, but before
123 make kernel KERNCONF=YOUR_KERNEL_HERE
124 make -C sys/boot install
125 <reboot in single user>
127 Then follow the usual steps, described in the General Notes section,
131 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
132 see the 20141231 entry below for information about prerequisites and
133 upgrading, if you are not already using clang 3.5.0 or higher.
136 The AIO subsystem is now a standard part of the kernel. The
137 VFS_AIO kernel option and aio.ko kernel module have been removed.
138 Due to stability concerns, asynchronous I/O requests are only
139 permitted on sockets and raw disks by default. To enable
140 asynchronous I/O requests on all file types, set the
141 vfs.aio.enable_unsafe sysctl to a non-zero value.
144 The ELF object manipulation tool objcopy is now provided by the
145 ELF Tool Chain project rather than by GNU binutils. It should be a
146 drop-in replacement, with the addition of arm64 support. The
147 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
148 to obtain the GNU version if necessary.
151 Building ZFS pools on top of zvols is prohibited by default. That
152 feature has never worked safely; it's always been prone to deadlocks.
153 Using a zvol as the backing store for a VM guest's virtual disk will
154 still work, even if the guest is using ZFS. Legacy behavior can be
155 restored by setting vfs.zfs.vol.recursive=1.
158 The NONE and HPN patches has been removed from OpenSSH. They are
159 still available in the security/openssh-portable port.
162 With the addition of ypldap(8), a new _ypldap user is now required
163 during installworld. "mergemaster -p" can be used to add the user
164 prior to installworld, as documented in the handbook.
167 The tftp loader (pxeboot) now uses the option root-path directive. As a
168 consequence it no longer looks for a pxeboot.4th file on the tftp
169 server. Instead it uses the regular /boot infrastructure as with the
173 The code to start recording plug and play data into the modules has
174 been committed. While the old tools will properly build a new kernel,
175 a number of warnings about "unknown metadata record 4" will be produced
176 for an older kldxref. To avoid such warnings, make sure to rebuild
177 the kernel toolchain (or world). Make sure that you have r292078 or
178 later when trying to build 292077 or later before rebuilding.
181 Debug data files are now built by default with 'make buildworld' and
182 installed with 'make installworld'. This facilitates debugging but
183 requires more disk space both during the build and for the installed
184 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
188 r291527 changed the internal interface between the nfsd.ko and
189 nfscommon.ko modules. As such, they must both be upgraded to-gether.
190 __FreeBSD_version has been bumped because of this.
193 Add support for unicode collation strings leads to a change of
194 order of files listed by ls(1) for example. To get back to the old
195 behaviour, set LC_COLLATE environment variable to "C".
197 Databases administrators will need to reindex their databases given
198 collation results will be different.
200 Due to a bug in install(1) it is recommended to remove the ancient
201 locales before running make installworld.
203 rm -rf /usr/share/locale/*
206 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
207 libcrypto.so.7 or libssl.so.7 must be recompiled.
210 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
211 Kernel modules isp_2400_multi and isp_2500_multi were removed and
212 should be replaced with isp_2400 and isp_2500 modules respectively.
215 The build previously allowed using 'make -n' to not recurse into
216 sub-directories while showing what commands would be executed, and
217 'make -n -n' to recursively show commands. Now 'make -n' will recurse
218 and 'make -N' will not.
221 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
222 and etcupdate will now use this file. A custom sendmail.cf is now
223 updated via this mechanism rather than via installworld. If you had
224 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
225 want to remove the exclusion or change it to "always install".
226 /etc/mail/sendmail.cf is now managed the same way regardless of
227 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
228 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
231 Compatibility shims for legacy ATA device names have been removed.
232 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
233 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
234 environment variables, /dev/ad* and /dev/ar* symbolic links.
237 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
238 Please see the 20141231 entry below for information about prerequisites
239 and upgrading, if you are not already using clang 3.5.0 or higher.
242 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
243 and renamed from .symbols to .debug. This reduces the size requirements
244 on the boot partition or file system and provides consistency with
245 userland debug files.
247 When using the supported kernel installation method the
248 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
249 as is done with /boot/kernel.
251 Developers wishing to maintain the historical behavior of installing
252 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
255 The wireless drivers had undergone changes that remove the 'parent
256 interface' from the ifconfig -l output. The rc.d network scripts
257 used to check presence of a parent interface in the list, so old
258 scripts would fail to start wireless networking. Thus, etcupdate(3)
259 or mergemaster(8) run is required after kernel update, to update your
260 rc.d scripts in /etc.
263 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
264 These configurations are now automatically interpreted as
265 'scrub fragment reassemble'.
268 Kernel-loadable modules for the random(4) device are back. To use
269 them, the kernel must have
272 options RANDOM_LOADABLE
274 kldload(8) can then be used to load random_fortuna.ko
275 or random_yarrow.ko. Please note that due to the indirect
276 function calls that the loadable modules need to provide,
277 the build-in variants will be slightly more efficient.
279 The random(4) kernel option RANDOM_DUMMY has been retired due to
280 unpopularity. It was not all that useful anyway.
283 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
284 Control over building the ELF Tool Chain tools is now provided by
285 the WITHOUT_TOOLCHAIN knob.
288 The polarity of Pulse Per Second (PPS) capture events with the
289 uart(4) driver has been corrected. Prior to this change the PPS
290 "assert" event corresponded to the trailing edge of a positive PPS
291 pulse and the "clear" event was the leading edge of the next pulse.
293 As the width of a PPS pulse in a typical GPS receiver is on the
294 order of 1 millisecond, most users will not notice any significant
295 difference with this change.
297 Anyone who has compensated for the historical polarity reversal by
298 configuring a negative offset equal to the pulse width will need to
299 remove that workaround.
302 The default group assigned to /dev/dri entries has been changed
303 from 'wheel' to 'video' with the id of '44'. If you want to have
304 access to the dri devices please add yourself to the video group
307 # pw groupmod video -m $USER
310 The menu.rc and loader.rc files will now be replaced during
311 upgrades. Please migrate local changes to menu.rc.local and
312 loader.rc.local instead.
315 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
316 strings and strip have been removed. The src.conf(5) knob
317 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
320 As ZFS requires more kernel stack pages than is the default on some
321 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
322 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
324 Please consider using 'options KSTACK_PAGES=X' where X is greater
325 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
328 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
329 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
330 default, i.e., they will not contain "::". For example, instead
331 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
332 to have a more specific match, such as different map entries for
333 IPv6:0:0 vs IPv6:0. This change requires that configuration
334 data (including maps, files, classes, custom ruleset, etc.) must
335 use the same format, so make certain such configuration data is
336 upgrading. As a very simple check search for patterns like
337 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
338 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
339 the cf option UseCompressedIPv6Addresses.
342 The default kernel entropy-processing algorithm is now
343 Fortuna, replacing Yarrow.
345 Assuming you have 'device random' in your kernel config
346 file, the configurations allow a kernel option to override
347 this default. You may choose *ONE* of:
349 options RANDOM_YARROW # Legacy /dev/random algorithm.
350 options RANDOM_DUMMY # Blocking-only driver.
352 If you have neither, you get Fortuna. For most people,
353 read no further, Fortuna will give a /dev/random that works
354 like it always used to, and the difference will be irrelevant.
356 If you remove 'device random', you get *NO* kernel-processed
357 entropy at all. This may be acceptable to folks building
358 embedded systems, but has complications. Carry on reading,
359 and it is assumed you know what you need.
361 *PLEASE* read random(4) and random(9) if you are in the
362 habit of tweaking kernel configs, and/or if you are a member
363 of the embedded community, wanting specific and not-usual
364 behaviour from your security subsystems.
366 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
367 random', you will NOT have a functioning /dev/random, and
368 many cryptographic features will not work, including SSH.
369 You may also find strange behaviour from the random(3) set
370 of library functions, in particular sranddev(3), srandomdev(3)
371 and arc4random(3). The reason for this is that the KERN_ARND
372 sysctl only returns entropy if it thinks it has some to
373 share, and with RANDOM_DUMMY or no 'device random' this
377 An additional fix for the issue described in the 20150614 sendmail
378 entry below has been been committed in revision 284717.
381 FreeBSD's old make (fmake) has been removed from the system. It is
382 available as the devel/fmake port or via pkg install fmake.
385 The fix for the issue described in the 20150614 sendmail entry
386 below has been been committed in revision 284436. The work
387 around described in that entry is no longer needed unless the
388 default setting is overridden by a confDH_PARAMETERS configuration
389 setting of '5' or pointing to a 512 bit DH parameter file.
392 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
393 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
394 and devel/kyua to version 0.20+ and adjust any calling code to work
395 with Kyuafile and kyua.
398 The import of openssl to address the FreeBSD-SA-15:10.openssl
399 security advisory includes a change which rejects handshakes
400 with DH parameters below 768 bits. sendmail releases prior
401 to 8.15.2 (not yet released), defaulted to a 512 bit
402 DH parameter setting for client connections. To work around
403 this interoperability, sendmail can be configured to use a
404 2048 bit DH parameter by:
406 1. Edit /etc/mail/`hostname`.mc
407 2. If a setting for confDH_PARAMETERS does not exist or
408 exists and is set to a string beginning with '5',
410 3. If a setting for confDH_PARAMETERS exists and is set to
411 a file path, create a new file with:
412 openssl dhparam -out /path/to/file 2048
413 4. Rebuild the .cf file:
414 cd /etc/mail/; make; make install
416 cd /etc/mail/; make restart
418 A sendmail patch is coming, at which time this file will be
422 Generation of legacy formatted entries have been disabled by default
423 in pwd_mkdb(8), as all base system consumers of the legacy formatted
424 entries were converted to use the new format by default when the new,
425 machine independent format have been added and supported since FreeBSD
428 Please see the pwd_mkdb(8) manual page for further details.
431 Clang and llvm have been upgraded to 3.6.1 release. Please see the
432 20141231 entry below for information about prerequisites and upgrading,
433 if you are not already using 3.5.0 or higher.
436 TI platform code switched to using vendor DTS files and this update
437 may break existing systems running on Beaglebone, Beaglebone Black,
440 - dtb files should be regenerated/reinstalled. Filenames are the
441 same but content is different now
442 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
443 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
444 addressing scheme is now pin 25 on /dev/gpioc3.
445 - Pandaboard: /etc/ttys should be updated, serial console device is
446 now /dev/ttyu2, not /dev/ttyu0
449 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
450 If you need the GNU extension from groff soelim(1), install groff
451 from package: pkg install groff, or via ports: textproc/groff.
454 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
455 defined in symlink(7); previously symlinks were silently ignored.
458 The const qualifier has been removed from iconv(3) to comply with
459 POSIX. The ports tree is aware of this from r384038 onwards.
462 Libraries specified by LIBADD in Makefiles must have a corresponding
463 DPADD_<lib> variable to ensure correct dependencies. This is now
464 enforced in src.libnames.mk.
467 From legacy ata(4) driver was removed support for SATA controllers
468 supported by more functional drivers ahci(4), siis(4) and mvs(4).
469 Kernel modules ataahci and ataadaptec were removed completely,
470 replaced by ahci and mvs modules respectively.
473 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
474 the 20141231 entry below for information about prerequisites and
475 upgrading, if you are not already using 3.5.0 or higher.
478 The 32-bit PowerPC kernel has been changed to a position-independent
479 executable. This can only be booted with a version of loader(8)
480 newer than January 31, 2015, so make sure to update both world and
481 kernel before rebooting.
484 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
485 but before r278950, the RNG was not seeded properly. Immediately
486 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
487 ssh keys or openssl keys) that were generated w/ a kernel from that
488 range. This does not affect programs that directly used /dev/random
489 or /dev/urandom. All userland uses of arc4random(3) are affected.
492 The autofs(4) ABI was changed in order to restore binary compatibility
493 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
497 The powerpc64 kernel has been changed to a position-independent
498 executable. This can only be booted with a new version of loader(8),
499 so make sure to update both world and kernel before rebooting.
502 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
503 only release, no new features have been added. Please see the 20141231
504 entry below for information about prerequisites and upgrading, if you
505 are not already using 3.5.0.
508 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
509 taken from the ELF Tool Chain project rather than GNU binutils. They
510 should be drop-in replacements, with the addition of arm64 support.
511 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
512 binutils tools, if necessary. See 20150805 for updated information.
515 The default Unbound configuration now enables remote control
516 using a local socket. Users who have already enabled the
517 local_unbound service should regenerate their configuration
518 by running "service local_unbound setup" as root.
521 The GNU texinfo and GNU info pages have been removed.
522 To be able to view GNU info pages please install texinfo from ports.
525 Clang, llvm and lldb have been upgraded to 3.5.0 release.
527 As of this release, a prerequisite for building clang, llvm and lldb is
528 a C++11 capable compiler and C++11 standard library. This means that to
529 be able to successfully build the cross-tools stage of buildworld, with
530 clang as the bootstrap compiler, your system compiler or cross compiler
531 should either be clang 3.3 or later, or gcc 4.8 or later, and your
532 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
535 On any standard FreeBSD 10.x or 11.x installation, where clang and
536 libc++ are on by default (that is, on x86 or arm), this should work out
539 On 9.x installations where clang is enabled by default, e.g. on x86 and
540 powerpc, libc++ will not be enabled by default, so libc++ should be
541 built (with clang) and installed first. If both clang and libc++ are
542 missing, build clang first, then use it to build libc++.
544 On 8.x and earlier installations, upgrade to 9.x first, and then follow
545 the instructions for 9.x above.
547 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
548 default, and do not build clang.
550 Many embedded systems are resource constrained, and will not be able to
551 build clang in a reasonable time, or in some cases at all. In those
552 cases, cross building bootable systems on amd64 is a workaround.
554 This new version of clang introduces a number of new warnings, of which
555 the following are most likely to appear:
559 This warns in two cases, for both C and C++:
560 * When the code is trying to take the absolute value of an unsigned
561 quantity, which is effectively a no-op, and almost never what was
562 intended. The code should be fixed, if at all possible. If you are
563 sure that the unsigned quantity can be safely cast to signed, without
564 loss of information or undefined behavior, you can add an explicit
565 cast, or disable the warning.
567 * When the code is trying to take an absolute value, but the called
568 abs() variant is for the wrong type, which can lead to truncation.
569 If you want to disable the warning instead of fixing the code, please
570 make sure that truncation will not occur, or it might lead to unwanted
573 -Wtautological-undefined-compare and
574 -Wundefined-bool-conversion
576 These warn when C++ code is trying to compare 'this' against NULL, while
577 'this' should never be NULL in well-defined C++ code. However, there is
578 some legacy (pre C++11) code out there, which actively abuses this
579 feature, which was less strictly defined in previous C++ versions.
581 Squid and openjdk do this, for example. The warning can be turned off
582 for C++98 and earlier, but compiling the code in C++11 mode might result
583 in unexpected behavior; for example, the parts of the program that are
584 unreachable could be optimized away.
587 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
588 kernel sources have been removed. The .h files remain, since some
589 utilities include them. This will need to be fixed later.
590 If "mount -t oldnfs ..." is attempted, it will fail.
591 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
592 the utilities will report errors.
595 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
596 directories to top level SUBDIR variable when their parent
597 directory is included in LOCAL_DIRS. Users with build systems with
598 such hierarchies and without SUBDIR entries in the parent
599 directory Makefiles should add them or add the directories to
603 faith(4) and faithd(8) have been removed from the base system. Faith
604 has been obsolete for a very long time.
607 vt(4), the new console driver, is enabled by default. It brings
608 support for Unicode and double-width characters, as well as
609 support for UEFI and integration with the KMS kernel video
612 You may need to update your console settings in /etc/rc.conf,
613 most probably the keymap. During boot, /etc/rc.d/syscons will
614 indicate what you need to do.
616 vt(4) still has issues and lacks some features compared to
617 syscons(4). See the wiki for up-to-date information:
618 https://wiki.freebsd.org/Newcons
620 If you want to keep using syscons(4), you can do so by adding
621 the following line to /boot/loader.conf:
625 pjdfstest has been integrated into kyua as an opt-in test suite.
626 Please see share/doc/pjdfstest/README for more details on how to
630 gperf has been removed from the base system for architectures
631 that use clang. Ports that require gperf will obtain it from the
635 pjdfstest has been moved from tools/regression/pjdfstest to
639 At svn r271982, The default linux compat kernel ABI has been adjusted
640 to 2.6.18 in support of the linux-c6 compat ports infrastructure
641 update. If you wish to continue using the linux-f10 compat ports,
642 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
643 encouraged to update their linux-compat packages to linux-c6 during
644 their next update cycle.
647 The ofwfb driver, used to provide a graphics console on PowerPC when
648 using vt(4), no longer allows mmap() of all physical memory. This
649 will prevent Xorg on PowerPC with some ATI graphics cards from
650 initializing properly unless x11-servers/xorg-server is updated to
654 The xdev targets have been converted to using TARGET and
655 TARGET_ARCH instead of XDEV and XDEV_ARCH.
658 The default unbound configuration has been modified to address
659 issues with reverse lookups on networks that use private
660 address ranges. If you use the local_unbound service, run
661 "service local_unbound setup" as root to regenerate your
662 configuration, then "service local_unbound reload" to load the
666 The GNU texinfo and GNU info pages are not built and installed
667 anymore, WITH_INFO knob has been added to allow to built and install
669 UPDATE: see 20150102 entry on texinfo's removal
672 The GNU readline library is now an INTERNALLIB - that is, it is
673 statically linked into consumers (GDB and variants) in the base
674 system, and the shared library is no longer installed. The
675 devel/readline port is available for third party software that
679 The Itanium architecture (ia64) has been removed from the list of
680 known architectures. This is the first step in the removal of the
684 Commit r268115 has added NFSv4.1 server support, merged from
685 projects/nfsv4.1-server. Since this includes changes to the
686 internal interfaces between the NFS related modules, a full
687 build of the kernel and modules will be necessary.
688 __FreeBSD_version has been bumped.
691 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
692 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
693 which differs from the behaviour controlled by this knob.)
696 Maximal length of the serial number in CTL was increased from 16 to
697 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
698 and ctld, need to be rebuilt to work with a new kernel.
701 The libatf-c and libatf-c++ major versions were downgraded to 0 and
702 1 respectively to match the upstream numbers. They were out of
703 sync because, when they were originally added to FreeBSD, the
704 upstream versions were not respected. These libraries are private
705 and not yet built by default, so renumbering them should be a
706 non-issue. However, unclean source trees will yield broken test
707 programs once the operator executes "make delete-old-libs" after a
710 Additionally, the atf-sh binary was made private by moving it into
711 /usr/libexec/. Already-built shell test programs will keep the
712 path to the old binary so they will break after "make delete-old"
715 If you are using WITH_TESTS=yes (not the default), wipe the object
716 tree and rebuild from scratch to prevent spurious test failures.
717 This is only needed once: the misnumbered libraries and misplaced
718 binaries have been added to OptionalObsoleteFiles.inc so they will
719 be removed during a clean upgrade.
722 Clang and llvm have been upgraded to 3.4.1 release.
725 We bogusly installed src.opts.mk in /usr/share/mk. This file should
726 be removed to avoid issues in the future (and has been added to
730 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
731 past, it affected all builds that used the bsd.*.mk files. The old
732 behavior was a bug, but people may have relied upon it. To get this
733 behavior back, you can .include /etc/src.conf from /etc/make.conf
734 (which is still global and isn't changed). This also changes the
735 behavior of incremental builds inside the tree of individual
736 directories. Set MAKESYSPATH to ".../share/mk" to do that.
737 Although this has survived make universe and some upgrade scenarios,
738 other upgrade scenarios may have broken. At least one form of
739 temporary breakage was fixed with MAKESYSPATH settings for buildworld
740 as well... In cases where MAKESYSPATH isn't working with this
741 setting, you'll need to set it to the full path to your tree.
743 One side effect of all this cleaning up is that bsd.compiler.mk
744 is no longer implicitly included by bsd.own.mk. If you wish to
745 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
749 The lindev device has been removed since /dev/full has been made a
750 standard device. __FreeBSD_version has been bumped.
753 The knob WITHOUT_VI was added to the base system, which controls
754 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
755 in order to reorder files share/termcap and didn't build ex(1) as a
756 build tool, so building/installing with WITH_VI is highly advised for
757 build hosts for older releases.
759 This issue has been fixed in stable/9 and stable/10 in r277022 and
760 r276991, respectively.
763 The YES_HESIOD knob has been removed. It has been obsolete for
764 a decade. Please move to using WITH_HESIOD instead or your builds
765 will silently lack HESIOD.
768 The uart(4) driver has been changed with respect to its handling
769 of the low-level console. Previously the uart(4) driver prevented
770 any process from changing the baudrate or the CLOCAL and HUPCL
771 control flags. By removing the restrictions, operators can make
772 changes to the serial console port without having to reboot.
773 However, when getty(8) is started on the serial device that is
774 associated with the low-level console, a misconfigured terminal
775 line in /etc/ttys will now have a real impact.
776 Before upgrading the kernel, make sure that /etc/ttys has the
777 serial console device configured as 3wire without baudrate to
778 preserve the previous behaviour. E.g:
779 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
782 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
783 to improve performance. To re-enable it, if needed, run rpcbind
784 with command line option -W.
787 Switched back to the GPL dtc compiler due to updates in the upstream
788 dts files not being supported by the BSDL dtc compiler. You will need
789 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
790 may result while building dtb files during a kernel build if you fail
791 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
794 Clang and llvm have been upgraded to 3.4 release.
797 The nve(4) driver has been removed. Please use the nfe(4) driver
798 for NVIDIA nForce MCP Ethernet adapters instead.
801 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
802 This could cause certain C++ applications using shared libraries built
803 against the previous version of libc++ to crash. The incompatibility
804 has now been fixed, but any C++ applications or shared libraries built
805 between r261283 and r261801 should be recompiled.
808 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
809 capability mode support. Please note that enabling the feature in
810 kernel is still highly recommended.
813 OpenSSH is now built with sandbox support, and will use sandbox as
814 the default privilege separation method. This requires Capsicum
815 capability mode support in kernel.
818 The libelf and libdwarf libraries have been updated to newer
819 versions from upstream. Shared library version numbers for
820 these two libraries were bumped. Any ports or binaries
821 requiring these two libraries should be recompiled.
822 __FreeBSD_version is bumped to 1100006.
825 If a Makefile in a tests/ directory was auto-generating a Kyuafile
826 instead of providing an explicit one, this would prevent such
827 Makefile from providing its own Kyuafile in the future during
828 NO_CLEAN builds. This has been fixed in the Makefiles but manual
829 intervention is needed to clean an objdir if you use NO_CLEAN:
830 # find /usr/obj -name Kyuafile | xargs rm -f
833 The behavior of gss_pseudo_random() for the krb5 mechanism
834 has changed, for applications requesting a longer random string
835 than produced by the underlying enctype's pseudo-random() function.
836 In particular, the random string produced from a session key of
837 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
838 be different at the 17th octet and later, after this change.
839 The counter used in the PRF+ construction is now encoded as a
840 big-endian integer in accordance with RFC 4402.
841 __FreeBSD_version is bumped to 1100004.
844 The WITHOUT_ATF build knob has been removed and its functionality
845 has been subsumed into the more generic WITHOUT_TESTS. If you were
846 using the former to disable the build of the ATF libraries, you
847 should change your settings to use the latter.
850 The default version of mtree is nmtree which is obtained from
851 NetBSD. The output is generally the same, but may vary
852 slightly. If you found you need identical output adding
853 "-F freebsd9" to the command line should do the trick. For the
854 time being, the old mtree is available as fmtree.
857 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
858 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
859 1.1.4_8 and verify bsdyml not linked in, before running "make
861 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
863 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
866 The stable/10 branch has been created in subversion from head
870 The rc.d/jail script has been updated to support jail(8)
871 configuration file. The "jail_<jname>_*" rc.conf(5) variables
872 for per-jail configuration are automatically converted to
873 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
874 This is transparently backward compatible. See below about some
875 incompatibilities and rc.conf(5) manual page for more details.
877 These variables are now deprecated in favor of jail(8) configuration
878 file. One can use "rc.d/jail config <jname>" command to generate
879 a jail(8) configuration file in /var/run/jail.<jname>.conf without
880 running the jail(8) utility. The default pathname of the
881 configuration file is /etc/jail.conf and can be specified by
882 using $jail_conf or $jail_<jname>_conf variables.
884 Please note that jail_devfs_ruleset accepts an integer at
885 this moment. Please consider to rewrite the ruleset name
889 BIND has been removed from the base system. If all you need
890 is a local resolver, simply enable and start the local_unbound
891 service instead. Otherwise, several versions of BIND are
892 available in the ports tree. The dns/bind99 port is one example.
894 With this change, nslookup(1) and dig(1) are no longer in the base
895 system. Users should instead use host(1) and drill(1) which are
896 in the base system. Alternatively, nslookup and dig can
897 be obtained by installing the dns/bind-tools port.
900 With the addition of unbound(8), a new unbound user is now
901 required during installworld. "mergemaster -p" can be used to
902 add the user prior to installworld, as documented in the handbook.
905 OpenSSH is now built with DNSSEC support, and will by default
906 silently trust signed SSHFP records. This can be controlled with
907 the VerifyHostKeyDNS client configuration setting. DNSSEC support
908 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
911 The GNU Compiler Collection and C++ standard library (libstdc++)
912 are no longer built by default on platforms where clang is the system
913 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
917 The PROCDESC kernel option is now part of the GENERIC kernel
918 configuration and is required for the rwhod(8) to work.
919 If you are using custom kernel configuration, you should include
923 The API and ABI related to the Capsicum framework was modified
924 in backward incompatible way. The userland libraries and programs
925 have to be recompiled to work with the new kernel. This includes the
926 following libraries and programs, but the whole buildworld is
927 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
928 kdump, procstat, rwho, rwhod, uniq.
931 AES-NI intrinsic support has been added to gcc. The AES-NI module
932 has been updated to use this support. A new gcc is required to build
933 the aesni module on both i386 and amd64.
936 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
937 Thus "device padlock_rng" and "device rdrand_rng" should be
938 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
941 WITH_ICONV has been split into two feature sets. WITH_ICONV now
942 enables just the iconv* functionality and is now on by default.
943 WITH_LIBICONV_COMPAT enables the libiconv api and link time
944 compatibility. Set WITHOUT_ICONV to build the old way.
945 If you have been using WITH_ICONV before, you will very likely
946 need to turn on WITH_LIBICONV_COMPAT.
949 INVARIANTS option now enables DEBUG for code with OpenSolaris and
950 Illumos origin, including ZFS. If you have INVARIANTS in your
951 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
953 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
954 locks if WITNESS option was set. Because that generated a lot of
955 witness(9) reports and all of them were believed to be false
956 positives, this is no longer done. New option OPENSOLARIS_WITNESS
957 can be used to achieve the previous behavior.
960 Timer values in IPv6 data structures now use time_uptime instead
961 of time_second. Although this is not a user-visible functional
962 change, userland utilities which directly use them---ndp(8),
963 rtadvd(8), and rtsold(8) in the base system---need to be updated
967 find -delete can now delete the pathnames given as arguments,
968 instead of only files found below them or if the pathname did
969 not contain any slashes. Formerly, the following error message
972 find: -delete: <path>: relative path potentially not safe
974 Deleting the pathnames given as arguments can be prevented
975 without error messages using -mindepth 1 or by changing
976 directory and passing "." as argument to find. This works in the
977 old as well as the new version of find.
980 Behavior of devfs rules path matching has been changed.
981 Pattern is now always matched against fully qualified devfs
982 path and slash characters must be explicitly matched by
983 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
984 subdirectories must be reviewed.
987 The default ARM ABI has changed to the ARM EABI. The old ABI is
988 incompatible with the ARM EABI and all programs and modules will
989 need to be rebuilt to work with a new kernel.
991 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
993 NOTE: Support for the old ABI will be removed in the future and
994 users are advised to upgrade.
997 pkg_install has been disconnected from the build if you really need it
998 you should add WITH_PKGTOOLS in your src.conf(5).
1001 Most of network statistics structures were changed to be able
1002 keep 64-bits counters. Thus all tools, that work with networking
1003 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1006 Fix a bug that allowed a tracing process (e.g. gdb) to write
1007 to a memory-mapped file in the traced process's address space
1008 even if neither the traced process nor the tracing process had
1009 write access to that file.
1012 CVS has been removed from the base system. An exact copy
1013 of the code is available from the devel/cvs port.
1016 Some people report the following error after the switch to bmake:
1018 make: illegal option -- J
1019 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1021 *** [buildworld] Error code 2
1023 this likely due to an old instance of make in
1024 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1025 which src/Makefile will use that blindly, if it exists, so if
1026 you see the above error:
1028 rm -rf `make -V MAKEPATH`
1033 Use bmake by default.
1034 Whereas before one could choose to build with bmake via
1035 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1036 make. The goal is to remove these knobs for 10-RELEASE.
1038 It is worth noting that bmake (like gmake) treats the command
1039 line as the unit of failure, rather than statements within the
1040 command line. Thus '(cd some/where && dosomething)' is safer
1041 than 'cd some/where; dosomething'. The '()' allows consistent
1042 behavior in parallel build.
1045 Fix a bug that allows NFS clients to issue READDIR on files.
1048 The WITHOUT_IDEA option has been removed because
1049 the IDEA patent expired.
1052 The sysctl which controls TRIM support under ZFS has been renamed
1053 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1057 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1058 rather than creating it's own in the temporary directory in
1059 order allow access to bootstrapped versions of tools such as
1060 install and mtree. When upgrading from version of FreeBSD where
1061 the install command does not support -l, you will need to
1062 install a new mergemaster command if mergemaster -p is required.
1063 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1067 Legacy ATA stack, disabled and replaced by new CAM-based one since
1068 FreeBSD 9.0, completely removed from the sources. Kernel modules
1069 atadisk and atapi*, user-level tools atacontrol and burncd are
1070 removed. Kernel option `options ATA_CAM` is now permanently enabled
1074 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1075 and socketpair(2). Software, in particular Kerberos, may
1076 automatically detect and use these during building. The resulting
1077 binaries will not work on older kernels.
1080 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1081 information, see the respective 20130304 entry).
1084 Recent commits to callout(9) changed the size of struct callout,
1085 so the KBI is probably heavily disturbed. Also, some functions
1086 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1087 by macros. Every kernel module using it won't load, so rebuild
1090 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1091 but does not initialize by default (because of the new CTL_DISABLE
1092 option) to save memory. To re-enable it, remove the CTL_DISABLE
1093 option from the kernel config file or set kern.cam.ctl.disable=0
1094 in /boot/loader.conf.
1097 The ctl device has been disabled in GENERIC for i386 and amd64.
1098 This was done due to the extra memory being allocated at system
1099 initialisation time by the ctl driver which was only used if
1100 a CAM target device was created. This makes a FreeBSD system
1101 unusable on 128MB or less of RAM.
1104 A new compression method (lz4) has been merged to -HEAD. Please
1105 refer to zpool-features(7) for more information.
1107 Please refer to the "ZFS notes" section of this file for information
1108 on upgrading boot ZFS pools.
1111 A BSD-licensed patch(1) variant has been added and is installed
1112 as bsdpatch, being the GNU version the default patch.
1113 To inverse the logic and use the BSD-licensed one as default,
1114 while having the GNU version installed as gnupatch, rebuild
1115 and install world with the WITH_BSD_PATCH knob set.
1118 Due to the use of the new -l option to install(1) during build
1119 and install, you must take care not to directly set the INSTALL
1120 make variable in your /etc/make.conf, /etc/src.conf, or on the
1121 command line. If you wish to use the -C flag for all installs
1122 you may be able to add INSTALL+=-C to /etc/make.conf or
1126 The install(1) option -M has changed meaning and now takes an
1127 argument that is a file or path to append logs to. In the
1128 unlikely event that -M was the last option on the command line
1129 and the command line contained at least two files and a target
1130 directory the first file will have logs appended to it. The -M
1131 option served little practical purpose in the last decade so its
1132 use is expected to be extremely rare.
1135 After switching to Clang as the default compiler some users of ZFS
1136 on i386 systems started to experience stack overflow kernel panics.
1137 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1140 GEOM_LABEL now mangles label names read from file system metadata.
1141 Mangling affect labels containing spaces, non-printable characters,
1142 '%' or '"'. Device names in /etc/fstab and other places may need to
1146 By default, only the 10 most recent kernel dumps will be saved. To
1147 restore the previous behaviour (no limit on the number of kernel dumps
1148 stored in the dump directory) add the following line to /etc/rc.conf:
1153 With the addition of auditdistd(8), a new auditdistd user is now
1154 required during installworld. "mergemaster -p" can be used to
1155 add the user prior to installworld, as documented in the handbook.
1158 The sin6_scope_id member variable in struct sockaddr_in6 is now
1159 filled by the kernel before passing the structure to the userland via
1160 sysctl or routing socket. This means the KAME-specific embedded scope
1161 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1162 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1163 __FreeBSD_version is bumped to 1000025.
1166 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1167 This means that the world and kernel will be compiled with clang
1168 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1169 and /usr/bin/cpp. To disable this behavior and revert to building
1170 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1171 of current may need to bootstrap WITHOUT_CLANG first if the clang
1172 build fails (its compatibility window doesn't extend to the 9 stable
1176 The IPFIREWALL_FORWARD kernel option has been removed. Its
1177 functionality now turned on by default.
1180 The ZERO_COPY_SOCKET kernel option has been removed and
1181 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1182 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1183 mechanism which is not safe and may result in kernel crashes.
1184 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1185 driver supports disposeable external page sized mbuf storage.
1186 Proper replacements for both zero-copy mechanisms are under
1187 consideration and will eventually lead to complete removal
1188 of the two kernel options.
1191 The IPv4 network stack has been converted to network byte
1192 order. The following modules need to be recompiled together
1193 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1194 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1197 Support for non-MPSAFE filesystems was removed from VFS. The
1198 VFS_VERSION was bumped, all filesystem modules shall be
1202 All the non-MPSAFE filesystems have been disconnected from
1203 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1204 portalfs, smbfs, xfs.
1207 The interface cloning API and ABI has changed. The following
1208 modules need to be recompiled together with kernel:
1209 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1210 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1211 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1214 The sdhci driver was split in two parts: sdhci (generic SD Host
1215 Controller logic) and sdhci_pci (actual hardware driver).
1216 No kernel config modifications are required, but if you
1217 load sdhc as a module you must switch to sdhci_pci instead.
1220 Import the FUSE kernel and userland support into base system.
1223 The GNU sort(1) program has been removed since the BSD-licensed
1224 sort(1) has been the default for quite some time and no serious
1225 problems have been reported. The corresponding WITH_GNU_SORT
1229 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1230 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1234 The net80211(4) ABI has been changed to allow for improved driver
1235 PS-POLL and power-save support. All wireless drivers need to be
1236 recompiled to work with the new kernel.
1239 The random(4) support for the VIA hardware random number
1240 generator (`PADLOCK') is no longer enabled unconditionally.
1241 Add the padlock_rng device in the custom kernel config if
1242 needed. The GENERIC kernels on i386 and amd64 do include the
1243 device, so the change only affects the custom kernel
1247 The pf(4) packet filter ABI has been changed. pfctl(8) and
1248 snmp_pf module need to be recompiled to work with new kernel.
1251 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1252 to -HEAD. Pools that have empty_bpobj in active state can not be
1253 imported read-write with ZFS implementations that do not support
1254 this feature. For more information read the zpool-features(5)
1258 The sparc64 ZFS loader has been changed to no longer try to auto-
1259 detect ZFS providers based on diskN aliases but now requires these
1260 to be explicitly listed in the OFW boot-device environment variable.
1263 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1264 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1265 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1268 The following sysctls and tunables have been renamed for consistency
1269 with other variables:
1270 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1271 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1274 The sort utility has been replaced with BSD sort. For now, GNU sort
1275 is also available as "gnusort" or the default can be set back to
1276 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1277 installed as "bsdsort".
1280 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1281 Starting with this version the old system of ZFS pool versioning
1282 is superseded by "feature flags". This concept enables forward
1283 compatibility against certain future changes in functionality of ZFS
1284 pools. The first read-only compatible "feature flag" for ZFS pools
1285 is named "com.delphix:async_destroy". For more information
1286 read the new zpool-features(5) manual page.
1287 Please refer to the "ZFS notes" section of this file for information
1288 on upgrading boot ZFS pools.
1291 The malloc(3) implementation embedded in libc now uses sources imported
1292 as contrib/jemalloc. The most disruptive API change is to
1293 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1294 delete it prior to installworld, and optionally re-create it using the
1295 new format after rebooting. See malloc.conf(5) for details
1296 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1300 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1301 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1302 now spelled mips. This is to aid compatibility with third-party
1303 software that expects this naming scheme in uname(3). Little-endian
1304 settings are unchanged. If you are updating a big-endian mips64 machine
1305 from before this change, you may need to set MACHINE_ARCH=mips64 in
1306 your environment before the new build system will recognize your machine.
1309 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1313 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1314 nullfs(5) did not pass through all behaviours to the underlying layer,
1315 as a result if we bound to a socket on the lower layer we could connect
1316 only to the lower path; if we bound to the upper layer we could connect
1317 only to the upper path. The new behavior is one can connect to both the
1318 lower and the upper paths regardless what layer path one binds to.
1321 The getifaddrs upgrade path broken with 20111215 has been restored.
1322 If you have upgraded in between 20111215 and 20120209 you need to
1323 recompile libc again with your kernel. You still need to recompile
1324 world to be able to configure CARP but this restriction already
1325 comes from 20111215.
1328 The set_rcvar() function has been removed from /etc/rc.subr. All
1329 base and ports rc.d scripts have been updated, so if you have a
1330 port installed with a script in /usr/local/etc/rc.d you can either
1331 hand-edit the rcvar= line, or reinstall the port.
1333 An easy way to handle the mass-update of /etc/rc.d:
1334 rm /etc/rc.d/* && mergemaster -i
1337 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1338 on the current CPU and prevents other threads from running.
1339 This behavior can be reverted using the kern.stop_scheduler_on_panic
1341 The new behavior can be incompatible with kern.sync_on_panic.
1344 The carp(4) facility has been changed significantly. Configuration
1345 of the CARP protocol via ifconfig(8) has changed, as well as format
1346 of CARP events submitted to devd(8) has changed. See manual pages
1347 for more information. The arpbalance feature of carp(4) is currently
1348 not supported anymore.
1350 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1351 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1352 need to be recompiled.
1355 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1359 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1360 explicitely support non-MPSAFE filesystems.
1361 It is on by default for all supported platform at this present
1365 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1366 i386 and pc98 GENERIC kernel configuration files.
1369 sysinstall has been removed
1372 The stable/9 branch created in subversion. This corresponds to the
1373 RELENG_9 branch in CVS.
1379 Avoid using make -j when upgrading. While generally safe, there are
1380 sometimes problems using -j to upgrade. If your upgrade fails with
1381 -j, please try again without -j. From time to time in the past there
1382 have been problems using -j with buildworld and/or installworld. This
1383 is especially true when upgrading between "distant" versions (eg one
1384 that cross a major release boundary or several minor releases, or when
1385 several months have passed on the -current branch).
1387 Sometimes, obscure build problems are the result of environment
1388 poisoning. This can happen because the make utility reads its
1389 environment when searching for values for global variables. To run
1390 your build attempts in an "environmental clean room", prefix all make
1391 commands with 'env -i '. See the env(1) manual page for more details.
1393 When upgrading from one major version to another it is generally best
1394 to upgrade to the latest code in the currently installed branch first,
1395 then do an upgrade to the new branch. This is the best-tested upgrade
1396 path, and has the highest probability of being successful. Please try
1397 this approach before reporting problems with a major version upgrade.
1399 When upgrading a live system, having a root shell around before
1400 installing anything can help undo problems. Not having a root shell
1401 around can lead to problems if pam has changed too much from your
1402 starting point to allow continued authentication after the upgrade.
1404 This file should be read as a log of events. When a later event changes
1405 information of a prior event, the prior event should not be deleted.
1406 Instead, a pointer to the entry with the new information should be
1407 placed in the old entry. Readers of this file should also sanity check
1408 older entries before relying on them blindly. Authors of new entries
1409 should write them with this in mind.
1413 When upgrading the boot ZFS pool to a new version, always follow
1416 1.) recompile and reinstall the ZFS boot loader and boot block
1417 (this is part of "make buildworld" and "make installworld")
1419 2.) update the ZFS boot block on your boot drive
1421 The following example updates the ZFS boot block on the first
1422 partition (freebsd-boot) of a GPT partitioned drive ada0:
1423 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1425 Non-boot pools do not need these updates.
1429 If you are updating from a prior version of FreeBSD (even one just
1430 a few days old), you should follow this procedure. It is the most
1431 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1433 make kernel-toolchain
1434 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1435 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1437 To test a kernel once
1438 ---------------------
1439 If you just want to boot a kernel once (because you are not sure
1440 if it works, or if you want to boot a known bad kernel to provide
1441 debugging information) run
1442 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1443 nextboot -k testkernel
1445 To just build a kernel when you know that it won't mess you up
1446 --------------------------------------------------------------
1447 This assumes you are already running a CURRENT system. Replace
1448 ${arch} with the architecture of your machine (e.g. "i386",
1449 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1451 cd src/sys/${arch}/conf
1452 config KERNEL_NAME_HERE
1453 cd ../compile/KERNEL_NAME_HERE
1458 If this fails, go to the "To build a kernel" section.
1460 To rebuild everything and install it on the current system.
1461 -----------------------------------------------------------
1462 # Note: sometimes if you are running current you gotta do more than
1463 # is listed here if you are upgrading from a really old current.
1465 <make sure you have good level 0 dumps>
1467 make kernel KERNCONF=YOUR_KERNEL_HERE
1469 <reboot in single user> [3]
1476 To cross-install current onto a separate partition
1477 --------------------------------------------------
1478 # In this approach we use a separate partition to hold
1479 # current's root, 'usr', and 'var' directories. A partition
1480 # holding "/", "/usr" and "/var" should be about 2GB in
1483 <make sure you have good level 0 dumps>
1486 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1487 <maybe newfs current's root partition>
1488 <mount current's root partition on directory ${CURRENT_ROOT}>
1489 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1490 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1491 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1492 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1493 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1494 <reboot into current>
1495 <do a "native" rebuild/install as described in the previous section>
1496 <maybe install compatibility libraries from ports/misc/compat*>
1500 To upgrade in-place from stable to current
1501 ----------------------------------------------
1502 <make sure you have good level 0 dumps>
1504 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1506 <reboot in single user> [3]
1513 Make sure that you've read the UPDATING file to understand the
1514 tweaks to various things you need. At this point in the life
1515 cycle of current, things change often and you are on your own
1516 to cope. The defaults can also change, so please read ALL of
1517 the UPDATING entries.
1519 Also, if you are tracking -current, you must be subscribed to
1520 freebsd-current@freebsd.org. Make sure that before you update
1521 your sources that you have read and understood all the recent
1522 messages there. If in doubt, please track -stable which has
1523 much fewer pitfalls.
1525 [1] If you have third party modules, such as vmware, you
1526 should disable them at this point so they don't crash your
1529 [3] From the bootblocks, boot -s, and then do
1534 adjkerntz -i # if CMOS is wall time
1535 Also, when doing a major release upgrade, it is required that
1536 you boot into single user mode to do the installworld.
1538 [4] Note: This step is non-optional. Failure to do this step
1539 can result in a significant reduction in the functionality of the
1540 system. Attempting to do it by hand is not recommended and those
1541 that pursue this avenue should read this file carefully, as well
1542 as the archives of freebsd-current and freebsd-hackers mailing lists
1543 for potential gotchas. The -U option is also useful to consider.
1544 See mergemaster(8) for more information.
1546 [5] Usually this step is a noop. However, from time to time
1547 you may need to do this if you get unknown user in the following
1548 step. It never hurts to do it all the time. You may need to
1549 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1550 install) after the buildworld before this step if you last updated
1551 from current before 20130425 or from -stable before 20130430.
1553 [6] This only deletes old files and directories. Old libraries
1554 can be deleted by "make delete-old-libs", but you have to make
1555 sure that no program is using those libraries anymore.
1557 [8] In order to have a kernel that can run the 4.x binaries needed to
1558 do an installworld, you must include the COMPAT_FREEBSD4 option in
1559 your kernel. Failure to do so may leave you with a system that is
1560 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1561 required to run the 5.x binaries on more recent kernels. And so on
1562 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1564 Make sure that you merge any new devices from GENERIC since the
1565 last time you updated your kernel config file.
1567 [9] When checking out sources, you must include the -P flag to have
1568 cvs prune empty directories.
1570 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1571 "?=" instead of the "=" assignment operator, so that buildworld can
1572 override the CPUTYPE if it needs to.
1574 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1575 not on the command line, or in /etc/make.conf. buildworld will
1576 warn if it is improperly defined.
1579 This file contains a list, in reverse chronological order, of major
1580 breakages in tracking -current. It is not guaranteed to be a complete
1581 list of such breakages, and only contains entries since September 23, 2011.
1582 If you need to see UPDATING entries from before that date, you will need
1583 to fetch an UPDATING file from an older FreeBSD release.
1585 Copyright information:
1587 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1589 Redistribution, publication, translation and use, with or without
1590 modification, in full or in part, in any form or format of this
1591 document are permitted without further permission from the author.
1593 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1594 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1595 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1596 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1597 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1598 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1599 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1600 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1601 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1602 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1603 POSSIBILITY OF SUCH DAMAGE.
1605 Contact Warner Losh if you have any questions about your use of