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