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