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