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