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 https://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 20200902 p13 FreeBSD-EN-20:17.linuxthread
20 FreeBSD-EN-20:18.getfsstat
23 FreeBSD-SA-20:26.dhclient
25 Fix FreeBSD Linux ABI kernel panic. [EN-20:17.linuxthread]
27 Fix getfsstat compatibility system call panic. [EN-20:18.getfsstat]
29 Fix IPv6 Hop-by-Hop options use-after-free. [SA-20:24.ipv6]
31 Fix SCTP socket use-after-free. [SA-20:25.sctp]
33 Fix dhclient heap overflow. [SA-20:26.dhclient]
35 20200805 p12 FreeBSD-SA-20:21.usb_net
36 FreeBSD-SA-20:22.unbound
39 Fix memory corruption in USB network device drivers. [SA-20:21.usb_net]
41 Fix multiple vulnerabilities in sqlite3. [SA-20:22.sqlite]
43 Fix sendmsg(2) privilege escalation. [SA-20:23.sendmsg]
45 20200708 p11 FreeBSD-EN-20:14.linuxkpi
47 FreeBSD-SA-20:19.unbound
50 Fix kernel panic in LinuxKPI subsystem. [EN-20:14.linuxpki]
52 Fix kernel panic in mps(4) driver. [EN-20:15.mps]
54 Fix multiple vulnerabilities in unbound. [SA-20:19.unbound]
56 Fix IPv6 socket option race condition and use after free. [SA-20:20.ipv6]
58 20200609 p10 FreeBSD-SA-20:17.usb
60 Fix USB HID descriptor parsing error. [SA-20:17.usb]
62 20200512 p9 FreeBSD-EN-20:08.tzdata
63 FreeBSD-EN-20:10.build
64 FreeBSD-SA-20:12.libalias
65 FreeBSD-SA-20:13.libalias
67 FreeBSD-SA-20:15.cryptodev
69 Import tzdata 2020a. [EN-20:08.tzdata]
71 Fix incorrect build host Clang version detection [EN-20:10.build]
73 Fix insufficient packet length validation in libalias [SA-20:12.libalias]
75 Fix memory disclosure vulnerability in libalias [SA-20:13.libalias]
77 Fix improper checking in SCTP-AUTH shared key update [SA-20:14.sctp]
79 Fix use after free in cryptodev module [SA-20:15.cryptodev]
81 20200421 p8 FreeBSD-EN-20:07.quotad
84 Fix regression in rpc.rquotad with certain NFS servers [EN-20:07.quotad]
86 Fix ipfw invalid mbuf handling [SA-20:10.ipfw]
88 20200319 p7 FreeBSD-EN-20:04.pfctl
91 FreeBSD-SA-20:05.if_oce_ioctl
92 FreeBSD-SA-20:07.epair
96 Fix missing pfctl(8) tunable [EN-20:04.pfctl]
98 Fix incorrect checksum calculations with IPv6 extension headers [EN-20:06.ipv6]
100 Fix TCP IPv6 SYN cache kernel information disclosure [SA-20:04.tcp]
102 Fix insufficient oce(4) ioctl(2) privilege checking [SA-20:05.if_oce_ioctl]
104 Fix incorrect user-controlled pointer use in epair [SA-20:07.epair]
106 Fix kernel memory disclosure with nested jails [SA-20:08.jail]
108 Fix multiple denial of service in ntpd [SA-20:09.ntp]
110 20200128 p6 FreeBSD-EN-20:01.ssp
111 FreeBSD-EN-20:02.nmount
112 FreeBSD-SA-20:01.libfetch
113 FreeBSD-SA-20:03.thrmisc
115 Fix imprecise ordering of SSP canary initialization [EN-20:01.ssp]
117 Fix nmount invalid pointer dereference [EN-20:02.nmount]
119 Fix libfetch buffer overflow [SA-20:01.libfetch]
121 Fix kernel stack data disclosure [SA-20:03.thrmisc]
123 20191112 p5 FreeBSD-SA-19:25.mcepsc
125 Fix Machine Check Exception on Page Size Change [SA-19:25.mcepsc]
127 20191023 p4 FreeBSD-EN-19:18.tzdata
129 Import tzdata 2019c. [EN-19:18.tzdata]
131 20190820 p3 FreeBSD-EN-19:16.bhyve
132 FreeBSD-EN-19:17.ipfw
133 FreeBSD-SA-19:22.mbuf
134 FreeBSD-SA-19:23.midi
135 FreeBSD-SA-19:24.mqueuefs
137 Bhyve instruction emulation improvements (opcode 03H and F7H).
140 Fix ipfw(8) jail keyword prior to jail startup. [EN-19:17.ipfw]
142 Fix IPv6 remote denial of service. [SA-19:22.mbuf]
144 Fix kernel memory disclosure from /dev/midistat. [SA-19:23.midi]
146 Fix reference count overflow in mqueuefs. [SA-19:24.mqueuefs]
148 20190806 p2 FreeBSD-SA-19:18.bzip2
149 FreeBSD-SA-19:19.mldv2
150 FreeBSD-SA-19:20.bsnmp
151 FreeBSD-SA-19:21.bhyve
153 Fix multiple vulnerabilities in bzip2. [SA-19:18.bzip2]
155 Fix ICMPv6 / MLDv2 out-of-bounds memory access. [SA-19:19.mldv2]
157 Fix insufficient message length validation in bsnmp library.
160 Fix insufficient validation of guest-supplied data (e1000 device).
163 20190724 p1 FreeBSD-EN-19:13.mds
164 FreeBSD-SA-19:12.telnet
166 FreeBSD-SA-19:14.freebsd32
167 FreeBSD-SA-19:15.mqueuefs
168 FreeBSD-SA-19:16.bhyve
171 Fix panic from Intel CPU vulnerability mitigation. [EN-19:13.mds]
173 Fix multiple telnet client vulnerabilities. [SA-19:12.telnet]
175 Fix pts write-after-free. [SA-19:13.pts]
177 Fix kernel memory disclosure in freebsd32_ioctl. [SA-19:14.freebsd32]
179 Fix reference count overflow in mqueuefs. [SA-19:15.mqueuefs]
181 Fix byhve out-of-bounds read in XHCI device. [SA-19:16.bhyve]
183 Fix file descriptor reference count leak. [SA-19:17.fd]
188 20190702 FreeBSD-EN-19:12.tzdata
189 FreeBSD-SA-19:09.iconv
190 FreeBSD-SA-19:11.cd_ioctl
192 Import tzdata 2019b. [EN-19:12.tzdata]
194 Fix iconv buffer overflow. [SA-19:09.iconv]
196 Fix privilege escalation in cd(4) driver. [SA-19:11.cd_ioctl]
199 CARP now sets DSCP value CS7(Network Traffic) in the flowlabel field
200 of packets by default instead of only setting TOS_LOWDELAY in IPv4,
201 which was deprecated in 1998. Original behavior can be restored by
202 setting sysctl net.inet.carp.dscp=4.
205 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
206 8.0.0. Please see the 20141231 entry below for information about
207 prerequisites and upgrading, if you are not already using clang 3.5.0
211 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
212 compiled into your custom kernel, add 'device xz' statement to the
216 Co-existance for Forth and Lua interpreters in bootloaders has now been
217 merged to ease testing of lualoader. LOADER_DEFAULT_INTERP, documented
218 in build(7), may be used to control which interpreter flavor is used in
219 the default loader to be installed. For systems where Lua and Forth
220 coexist, this switch can also be made on a running system by creating a
221 link from /boot/loader{,.efi} to /boot/loader_${flavor}{,.efi} rather
222 than requiring a rebuild.
224 The default flavor in this branch will remain Forth. As indicated in
225 the 20190216 UPDATING entry, booting is a complex environment; it would
226 be prudent to assume that lualoader may not work for your setup and make
227 provisions for backup boot methods.
230 zfsloader's functionality has now been folded into loader.
231 zfsloader is no longer necesasary once you've updated your
232 boot blocks. For a transition period, we will install a
233 hardlink for zfsloader to loader to allow a smooth transition
234 until the boot blocks can be updated (hard link because old
235 zfs boot blocks don't understand symlinks).
238 Lualoader has been merged to facilitate testing on this branch. It's
239 purely opt-in for now by building WITH_LOADER_LUA and WITHOUT_FORTH in
240 /etc/src.conf, but co-existance will come shortly. Booting is a complex
241 environment and test coverage for Lua-enabled loaders has been thin, so
242 it would be prudent to assume it might not work and make provisions for
246 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
247 7.0.1. Please see the 20141231 entry below for information about
248 prerequisites and upgrading, if you are not already using clang 3.5.0
252 r342562 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
253 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
254 servers that have vfs.nfsd.nfs_privport set will only allow mounts
255 from clients using a reserved port#. Since both the FreeBSD and Linux
256 NFSv4 clients use reserved port#s by default, this should not affect
260 The '%I' format in the kern.corefile sysctl limits the number of
261 core files that a process can generate to the number stored in the
262 debug.ncores sysctl. The '%I' format is replaced by the single digit
263 index. Previously, if all indexes were taken the kernel would overwrite
264 only a core file with the highest index in a filename.
265 Currently the system will create a new core file if there is a free
266 index or if all slots are taken it will overwrite the oldest one.
269 WITH_OFED option now only enables the build for the OFED libraries
270 and some fundamental client utilities. OpenSM and rest of the
271 debugging tools are enabled by WITH_OFED_EXTRA build switch.
272 WITH_OFED is turned on by default on amd64.
275 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
276 6.0.1. Please see the 20141231 entry below for information about
277 prerequisites and upgrading, if you are not already using clang 3.5.0
281 The releng/11.2 branch has been created from stable/11@r334458.
284 The tz database (tzdb) has been updated to 2018e. This version more
285 correctly models time stamps in time zones with negative DST such as
286 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
287 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
288 time zone abbreviations and the tm_isdst flag.
291 The use of RSS hash from the network card aka flowid has been
292 disabled by default for lagg(4) as it's currently incompatible with
293 the lacp and loadbalance protocols.
295 This can be re-enabled by setting the following in loader.conf:
296 net.link.lagg.default_use_flowid="1"
299 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
300 6.0.0. Please see the 20141231 entry below for information about
301 prerequisites and upgrading, if you are not already using clang 3.5.0
305 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
306 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
307 to WITH/OUT_LOADER_GELI.
310 The geli password typed at boot is now hidden. To restore the previous
311 behavior, see geli(8) for configuration options.
313 The SW_WATCHDOG option is no longer necessary to enable the
314 hardclock-based software watchdog if no hardware watchdog is
315 configured. As before, SW_WATCHDOG will cause the software
316 watchdog to be enabled even if a hardware watchdog is configured.
319 lint(1) binaries and library are no longer built by default. To
320 enable building them, define WITH_LINT in src.conf. If you are using
321 a FreeBSD 12 or later system to build 11-stable, you may need to
322 install a lint(1) binary to use WITH_LINT.
325 When building multiple kernels using KERNCONF, non-existent KERNCONF
326 files will produce an error and buildkernel will fail. Previously
327 missing KERNCONF files silently failed giving no indication as to
328 why, only to subsequently discover during installkernel that the
329 desired kernel was never built in the first place.
332 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
333 Please see the 20141231 entry below for information about prerequisites
334 and upgrading, if you are not already using clang 3.5.0 or higher.
337 Since the switch to GPT disk labels, fsck for UFS/FFS has been
338 unable to automatically find alternate superblocks. As of r322806,
339 the information needed to find alternate superblocks has been
340 moved to the end of the area reserved for the boot block.
341 Filesystems created with a newfs of this vintage or later
342 will create the recovery information. If you have a filesystem
343 created prior to this change and wish to have a recovery block
344 created for your filesystem, you can do so by running fsck in
345 forground mode (i.e., do not use the -p or -y options). As it
346 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
347 to which you should answer yes.
350 The releng/11.1 branch has been created from stable/11@r320475.
353 arm64 builds now use the base system LLD 4.0.0 linker by default,
354 instead of requiring that the aarch64-binutils port or package be
355 installed. To continue using aarch64-binutils, set
356 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
359 The ctl.ko module no longer implements the iSCSI target frontend:
360 cfiscsi.ko does instead.
362 If building cfiscsi.ko as a kernel module, the module can be loaded
363 via one of the following methods:
364 - `cfiscsi_load="YES"` in loader.conf(5).
365 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
366 - ctladm(8)/ctld(8), when compiled with iSCSI support
367 (`WITH_ISCSI=yes` in src.conf(5))
369 Please see cfiscsi(4) for more details.
372 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
373 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
374 same source (previously, the dependency of mmcsd.ko on mmc.ko was
375 missing, but mmcsd.ko now will refuse to load if it is incompatible
379 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
380 use any explicitly assigned loopback address available in the jail
381 instead of using the first assigned address of the jail.
384 As of r316810 for ipfilter, keep frags is no longer assumed when
385 keep state is specified in a rule. r316810 aligns ipfilter with
386 documentation in man pages separating keep frags from keep state.
387 This allows keep state to specified without forcing keep frags
388 and allows keep frags to be specified independently of keep state.
389 To maintain previous behaviour, also specify keep frags with
390 keep state (as documented in ipf.conf.5).
393 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
394 Please see the 20141231 entry below for information about prerequisites
395 and upgrading, if you are not already using clang 3.5.0 or higher.
398 The code that provides support for ZFS .zfs/ directory functionality
399 has been reimplemented. It's not possible now to create a snapshot
400 by mkdir under .zfs/snapshot/. That should be the only user visible
404 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
405 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
406 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
407 and now NAT-T is supported by default. Security associations now use
408 the single namespace for SPI allocation, so if you use several manually
409 configured security associations with the same SPI, this configuration
413 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
414 Please see the 20141231 entry below for information about prerequisites
415 and upgrading, if you are not already using clang 3.5.0 or higher.
418 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
419 Please see the 20141231 entry below for information about prerequisites
420 and upgrading, if you are not already using clang 3.5.0 or higher.
423 The layout of the pmap structure has changed for powerpc to put the pmap
424 statistics at the front for all CPU variations. libkvm(3) and all tools
425 that link against it need to be recompiled.
428 isl(4) and cyapa(4) drivers now require a new driver,
429 chromebook_platform(4), to work properly on Chromebook-class hardware.
430 On other types of hardware the drivers may need to be configured using
431 device hints. Please see the corresponding manual pages for details.
434 Relocatable object files with the extension of .So have been renamed
435 to use an extension of .pico instead. The purpose of this change is
436 to avoid a name clash with shared libraries on case-insensitive file
437 systems. On those file systems, foo.So is the same file as foo.so.
440 The releng/11.0 branch has been created from stable/11@r303970.
443 The stable/11 branch has been created from head@r302406.
446 The libc stub for the pipe(2) system call has been replaced with
447 a wrapper that calls the pipe2(2) system call and the pipe(2)
448 system call is now only implemented by the kernels that include
449 "options COMPAT_FREEBSD10" in their config file (this is the
450 default). Users should ensure that this option is enabled in
451 their kernel or upgrade userspace to r302092 before upgrading their
455 CAM will now strip leading spaces from SCSI disks' serial numbers.
456 This will effect users who create UFS filesystems on SCSI disks using
457 those disk's diskid device nodes. For example, if /etc/fstab
458 previously contained a line like
459 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
460 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
461 transforms like gmirror may also be affected. ZFS users should
465 The bitstring(3) API has been updated with new functionality and
466 improved performance. But it is binary-incompatible with the old API.
467 Objects built with the new headers may not be linked against objects
468 built with the old headers.
471 The brk and sbrk functions have been removed from libc on arm64.
472 Binutils from ports has been updated to not link to these
473 functions and should be updated to the latest version before
474 installing a new libc.
477 The armv6 port now defaults to hard float ABI. Limited support
478 for running both hardfloat and soft float on the same system
479 is available using the libraries installed with -DWITH_LIBSOFT.
480 This has only been tested as an upgrade path for installworld
481 and packages may fail or need manual intervention to run. New
482 packages will be needed.
484 To update an existing self-hosted armv6hf system, you must add
485 TARGET_ARCH=armv6 on the make command line for both the build
486 and the install steps.
489 Kernel modules compiled outside of a kernel build now default to
490 installing to /boot/modules instead of /boot/kernel. Many kernel
491 modules built this way (such as those in ports) already overrode
492 KMODDIR explicitly to install into /boot/modules. However,
493 manually building and installing a module from /sys/modules will
494 now install to /boot/modules instead of /boot/kernel.
497 The CAM I/O scheduler has been committed to the kernel. There should be
498 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
499 list of known rogues that claim support for this but actually corrupt
500 data is believed to be complete, be on the lookout for data
501 corruption. The known rogue list is believed to be complete:
503 o Crucial MX100, M550 drives with MU01 firmware.
504 o Micron M510 and M550 drives with MU01 firmware.
505 o Micron M500 prior to MU07 firmware
506 o Samsung 830, 840, and 850 all firmwares
507 o FCCT M500 all firmwares
509 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
510 with working NCQ TRIM. For Micron branded drives, see your sales rep for
511 updated firmware. Black listed drives will work correctly because these
512 drives work correctly so long as no NCQ TRIMs are sent to them. Given
513 this list is the same as found in Linux, it's believed there are no
514 other rogues in the market place. All other models from the above
517 To be safe, if you are at all concerned, you can quirk each of your
518 drives to prevent NCQ from being sent by setting:
519 kern.cam.ada.X.quirks="0x2"
520 in loader.conf. If the drive requires the 4k sector quirk, set the
524 The FAST_DEPEND build option has been removed and its functionality is
525 now the one true way. The old mkdep(1) style of 'make depend' has
526 been removed. See 20160311 for further details.
529 Resource range types have grown from unsigned long to uintmax_t. All
530 drivers, and anything using libdevinfo, need to be recompiled.
533 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
534 builds. It no longer runs mkdep(1) during 'make depend', and the
535 'make depend' stage can safely be skipped now as it is auto ran
536 when building 'make all' and will generate all SRCS and DPSRCS before
537 building anything else. Dependencies are gathered at compile time with
538 -MF flags kept in separate .depend files per object file. Users should
539 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
543 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
544 kernel modules. Therefore, if you load any kernel modules at boot time,
545 please install the boot loaders after you install the kernel, but before
549 make kernel KERNCONF=YOUR_KERNEL_HERE
550 make -C sys/boot install
551 <reboot in single user>
553 Then follow the usual steps, described in the General Notes section,
557 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
558 see the 20141231 entry below for information about prerequisites and
559 upgrading, if you are not already using clang 3.5.0 or higher.
562 The AIO subsystem is now a standard part of the kernel. The
563 VFS_AIO kernel option and aio.ko kernel module have been removed.
564 Due to stability concerns, asynchronous I/O requests are only
565 permitted on sockets and raw disks by default. To enable
566 asynchronous I/O requests on all file types, set the
567 vfs.aio.enable_unsafe sysctl to a non-zero value.
570 The ELF object manipulation tool objcopy is now provided by the
571 ELF Tool Chain project rather than by GNU binutils. It should be a
572 drop-in replacement, with the addition of arm64 support. The
573 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
574 to obtain the GNU version if necessary.
577 Building ZFS pools on top of zvols is prohibited by default. That
578 feature has never worked safely; it's always been prone to deadlocks.
579 Using a zvol as the backing store for a VM guest's virtual disk will
580 still work, even if the guest is using ZFS. Legacy behavior can be
581 restored by setting vfs.zfs.vol.recursive=1.
584 The NONE and HPN patches has been removed from OpenSSH. They are
585 still available in the security/openssh-portable port.
588 With the addition of ypldap(8), a new _ypldap user is now required
589 during installworld. "mergemaster -p" can be used to add the user
590 prior to installworld, as documented in the handbook.
593 The tftp loader (pxeboot) now uses the option root-path directive. As a
594 consequence it no longer looks for a pxeboot.4th file on the tftp
595 server. Instead it uses the regular /boot infrastructure as with the
599 The code to start recording plug and play data into the modules has
600 been committed. While the old tools will properly build a new kernel,
601 a number of warnings about "unknown metadata record 4" will be produced
602 for an older kldxref. To avoid such warnings, make sure to rebuild
603 the kernel toolchain (or world). Make sure that you have r292078 or
604 later when trying to build 292077 or later before rebuilding.
607 Debug data files are now built by default with 'make buildworld' and
608 installed with 'make installworld'. This facilitates debugging but
609 requires more disk space both during the build and for the installed
610 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
614 r291527 changed the internal interface between the nfsd.ko and
615 nfscommon.ko modules. As such, they must both be upgraded to-gether.
616 __FreeBSD_version has been bumped because of this.
619 Add support for unicode collation strings leads to a change of
620 order of files listed by ls(1) for example. To get back to the old
621 behaviour, set LC_COLLATE environment variable to "C".
623 Databases administrators will need to reindex their databases given
624 collation results will be different.
626 Due to a bug in install(1) it is recommended to remove the ancient
627 locales before running make installworld.
629 rm -rf /usr/share/locale/*
632 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
633 libcrypto.so.7 or libssl.so.7 must be recompiled.
636 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
637 Kernel modules isp_2400_multi and isp_2500_multi were removed and
638 should be replaced with isp_2400 and isp_2500 modules respectively.
641 The build previously allowed using 'make -n' to not recurse into
642 sub-directories while showing what commands would be executed, and
643 'make -n -n' to recursively show commands. Now 'make -n' will recurse
644 and 'make -N' will not.
647 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
648 and etcupdate will now use this file. A custom sendmail.cf is now
649 updated via this mechanism rather than via installworld. If you had
650 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
651 want to remove the exclusion or change it to "always install".
652 /etc/mail/sendmail.cf is now managed the same way regardless of
653 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
654 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
657 Compatibility shims for legacy ATA device names have been removed.
658 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
659 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
660 environment variables, /dev/ad* and /dev/ar* symbolic links.
663 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
664 Please see the 20141231 entry below for information about prerequisites
665 and upgrading, if you are not already using clang 3.5.0 or higher.
668 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
669 and renamed from .symbols to .debug. This reduces the size requirements
670 on the boot partition or file system and provides consistency with
671 userland debug files.
673 When using the supported kernel installation method the
674 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
675 as is done with /boot/kernel.
677 Developers wishing to maintain the historical behavior of installing
678 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
681 The wireless drivers had undergone changes that remove the 'parent
682 interface' from the ifconfig -l output. The rc.d network scripts
683 used to check presence of a parent interface in the list, so old
684 scripts would fail to start wireless networking. Thus, etcupdate(3)
685 or mergemaster(8) run is required after kernel update, to update your
686 rc.d scripts in /etc.
689 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
690 These configurations are now automatically interpreted as
691 'scrub fragment reassemble'.
694 Kernel-loadable modules for the random(4) device are back. To use
695 them, the kernel must have
698 options RANDOM_LOADABLE
700 kldload(8) can then be used to load random_fortuna.ko
701 or random_yarrow.ko. Please note that due to the indirect
702 function calls that the loadable modules need to provide,
703 the build-in variants will be slightly more efficient.
705 The random(4) kernel option RANDOM_DUMMY has been retired due to
706 unpopularity. It was not all that useful anyway.
709 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
710 Control over building the ELF Tool Chain tools is now provided by
711 the WITHOUT_TOOLCHAIN knob.
714 The polarity of Pulse Per Second (PPS) capture events with the
715 uart(4) driver has been corrected. Prior to this change the PPS
716 "assert" event corresponded to the trailing edge of a positive PPS
717 pulse and the "clear" event was the leading edge of the next pulse.
719 As the width of a PPS pulse in a typical GPS receiver is on the
720 order of 1 millisecond, most users will not notice any significant
721 difference with this change.
723 Anyone who has compensated for the historical polarity reversal by
724 configuring a negative offset equal to the pulse width will need to
725 remove that workaround.
728 The default group assigned to /dev/dri entries has been changed
729 from 'wheel' to 'video' with the id of '44'. If you want to have
730 access to the dri devices please add yourself to the video group
733 # pw groupmod video -m $USER
736 The menu.rc and loader.rc files will now be replaced during
737 upgrades. Please migrate local changes to menu.rc.local and
738 loader.rc.local instead.
741 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
742 strings and strip have been removed. The src.conf(5) knob
743 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
746 As ZFS requires more kernel stack pages than is the default on some
747 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
748 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
750 Please consider using 'options KSTACK_PAGES=X' where X is greater
751 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
754 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
755 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
756 default, i.e., they will not contain "::". For example, instead
757 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
758 to have a more specific match, such as different map entries for
759 IPv6:0:0 vs IPv6:0. This change requires that configuration
760 data (including maps, files, classes, custom ruleset, etc.) must
761 use the same format, so make certain such configuration data is
762 upgrading. As a very simple check search for patterns like
763 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
764 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
765 the cf option UseCompressedIPv6Addresses.
768 The default kernel entropy-processing algorithm is now
769 Fortuna, replacing Yarrow.
771 Assuming you have 'device random' in your kernel config
772 file, the configurations allow a kernel option to override
773 this default. You may choose *ONE* of:
775 options RANDOM_YARROW # Legacy /dev/random algorithm.
776 options RANDOM_DUMMY # Blocking-only driver.
778 If you have neither, you get Fortuna. For most people,
779 read no further, Fortuna will give a /dev/random that works
780 like it always used to, and the difference will be irrelevant.
782 If you remove 'device random', you get *NO* kernel-processed
783 entropy at all. This may be acceptable to folks building
784 embedded systems, but has complications. Carry on reading,
785 and it is assumed you know what you need.
787 *PLEASE* read random(4) and random(9) if you are in the
788 habit of tweaking kernel configs, and/or if you are a member
789 of the embedded community, wanting specific and not-usual
790 behaviour from your security subsystems.
792 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
793 random', you will NOT have a functioning /dev/random, and
794 many cryptographic features will not work, including SSH.
795 You may also find strange behaviour from the random(3) set
796 of library functions, in particular sranddev(3), srandomdev(3)
797 and arc4random(3). The reason for this is that the KERN_ARND
798 sysctl only returns entropy if it thinks it has some to
799 share, and with RANDOM_DUMMY or no 'device random' this
803 An additional fix for the issue described in the 20150614 sendmail
804 entry below has been been committed in revision 284717.
807 FreeBSD's old make (fmake) has been removed from the system. It is
808 available as the devel/fmake port or via pkg install fmake.
811 The fix for the issue described in the 20150614 sendmail entry
812 below has been been committed in revision 284436. The work
813 around described in that entry is no longer needed unless the
814 default setting is overridden by a confDH_PARAMETERS configuration
815 setting of '5' or pointing to a 512 bit DH parameter file.
818 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
819 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
820 and devel/kyua to version 0.20+ and adjust any calling code to work
821 with Kyuafile and kyua.
824 The import of openssl to address the FreeBSD-SA-15:10.openssl
825 security advisory includes a change which rejects handshakes
826 with DH parameters below 768 bits. sendmail releases prior
827 to 8.15.2 (not yet released), defaulted to a 512 bit
828 DH parameter setting for client connections. To work around
829 this interoperability, sendmail can be configured to use a
830 2048 bit DH parameter by:
832 1. Edit /etc/mail/`hostname`.mc
833 2. If a setting for confDH_PARAMETERS does not exist or
834 exists and is set to a string beginning with '5',
836 3. If a setting for confDH_PARAMETERS exists and is set to
837 a file path, create a new file with:
838 openssl dhparam -out /path/to/file 2048
839 4. Rebuild the .cf file:
840 cd /etc/mail/; make; make install
842 cd /etc/mail/; make restart
844 A sendmail patch is coming, at which time this file will be
848 Generation of legacy formatted entries have been disabled by default
849 in pwd_mkdb(8), as all base system consumers of the legacy formatted
850 entries were converted to use the new format by default when the new,
851 machine independent format have been added and supported since FreeBSD
854 Please see the pwd_mkdb(8) manual page for further details.
857 Clang and llvm have been upgraded to 3.6.1 release. Please see the
858 20141231 entry below for information about prerequisites and upgrading,
859 if you are not already using 3.5.0 or higher.
862 TI platform code switched to using vendor DTS files and this update
863 may break existing systems running on Beaglebone, Beaglebone Black,
866 - dtb files should be regenerated/reinstalled. Filenames are the
867 same but content is different now
868 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
869 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
870 addressing scheme is now pin 25 on /dev/gpioc3.
871 - Pandaboard: /etc/ttys should be updated, serial console device is
872 now /dev/ttyu2, not /dev/ttyu0
875 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
876 If you need the GNU extension from groff soelim(1), install groff
877 from package: pkg install groff, or via ports: textproc/groff.
880 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
881 defined in symlink(7); previously symlinks were silently ignored.
884 The const qualifier has been removed from iconv(3) to comply with
885 POSIX. The ports tree is aware of this from r384038 onwards.
888 Libraries specified by LIBADD in Makefiles must have a corresponding
889 DPADD_<lib> variable to ensure correct dependencies. This is now
890 enforced in src.libnames.mk.
893 From legacy ata(4) driver was removed support for SATA controllers
894 supported by more functional drivers ahci(4), siis(4) and mvs(4).
895 Kernel modules ataahci and ataadaptec were removed completely,
896 replaced by ahci and mvs modules respectively.
899 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
900 the 20141231 entry below for information about prerequisites and
901 upgrading, if you are not already using 3.5.0 or higher.
904 The 32-bit PowerPC kernel has been changed to a position-independent
905 executable. This can only be booted with a version of loader(8)
906 newer than January 31, 2015, so make sure to update both world and
907 kernel before rebooting.
910 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
911 but before r278950, the RNG was not seeded properly. Immediately
912 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
913 ssh keys or openssl keys) that were generated w/ a kernel from that
914 range. This does not affect programs that directly used /dev/random
915 or /dev/urandom. All userland uses of arc4random(3) are affected.
918 The autofs(4) ABI was changed in order to restore binary compatibility
919 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
923 The powerpc64 kernel has been changed to a position-independent
924 executable. This can only be booted with a new version of loader(8),
925 so make sure to update both world and kernel before rebooting.
928 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
929 only release, no new features have been added. Please see the 20141231
930 entry below for information about prerequisites and upgrading, if you
931 are not already using 3.5.0.
934 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
935 taken from the ELF Tool Chain project rather than GNU binutils. They
936 should be drop-in replacements, with the addition of arm64 support.
937 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
938 binutils tools, if necessary. See 20150805 for updated information.
941 The default Unbound configuration now enables remote control
942 using a local socket. Users who have already enabled the
943 local_unbound service should regenerate their configuration
944 by running "service local_unbound setup" as root.
947 The GNU texinfo and GNU info pages have been removed.
948 To be able to view GNU info pages please install texinfo from ports.
951 Clang, llvm and lldb have been upgraded to 3.5.0 release.
953 As of this release, a prerequisite for building clang, llvm and lldb is
954 a C++11 capable compiler and C++11 standard library. This means that to
955 be able to successfully build the cross-tools stage of buildworld, with
956 clang as the bootstrap compiler, your system compiler or cross compiler
957 should either be clang 3.3 or later, or gcc 4.8 or later, and your
958 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
961 On any standard FreeBSD 10.x or 11.x installation, where clang and
962 libc++ are on by default (that is, on x86 or arm), this should work out
965 On 9.x installations where clang is enabled by default, e.g. on x86 and
966 powerpc, libc++ will not be enabled by default, so libc++ should be
967 built (with clang) and installed first. If both clang and libc++ are
968 missing, build clang first, then use it to build libc++.
970 On 8.x and earlier installations, upgrade to 9.x first, and then follow
971 the instructions for 9.x above.
973 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
974 default, and do not build clang.
976 Many embedded systems are resource constrained, and will not be able to
977 build clang in a reasonable time, or in some cases at all. In those
978 cases, cross building bootable systems on amd64 is a workaround.
980 This new version of clang introduces a number of new warnings, of which
981 the following are most likely to appear:
985 This warns in two cases, for both C and C++:
986 * When the code is trying to take the absolute value of an unsigned
987 quantity, which is effectively a no-op, and almost never what was
988 intended. The code should be fixed, if at all possible. If you are
989 sure that the unsigned quantity can be safely cast to signed, without
990 loss of information or undefined behavior, you can add an explicit
991 cast, or disable the warning.
993 * When the code is trying to take an absolute value, but the called
994 abs() variant is for the wrong type, which can lead to truncation.
995 If you want to disable the warning instead of fixing the code, please
996 make sure that truncation will not occur, or it might lead to unwanted
999 -Wtautological-undefined-compare and
1000 -Wundefined-bool-conversion
1002 These warn when C++ code is trying to compare 'this' against NULL, while
1003 'this' should never be NULL in well-defined C++ code. However, there is
1004 some legacy (pre C++11) code out there, which actively abuses this
1005 feature, which was less strictly defined in previous C++ versions.
1007 Squid and openjdk do this, for example. The warning can be turned off
1008 for C++98 and earlier, but compiling the code in C++11 mode might result
1009 in unexpected behavior; for example, the parts of the program that are
1010 unreachable could be optimized away.
1013 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1014 kernel sources have been removed. The .h files remain, since some
1015 utilities include them. This will need to be fixed later.
1016 If "mount -t oldnfs ..." is attempted, it will fail.
1017 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1018 the utilities will report errors.
1021 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1022 directories to top level SUBDIR variable when their parent
1023 directory is included in LOCAL_DIRS. Users with build systems with
1024 such hierarchies and without SUBDIR entries in the parent
1025 directory Makefiles should add them or add the directories to
1029 faith(4) and faithd(8) have been removed from the base system. Faith
1030 has been obsolete for a very long time.
1033 vt(4), the new console driver, is enabled by default. It brings
1034 support for Unicode and double-width characters, as well as
1035 support for UEFI and integration with the KMS kernel video
1038 You may need to update your console settings in /etc/rc.conf,
1039 most probably the keymap. During boot, /etc/rc.d/syscons will
1040 indicate what you need to do.
1042 vt(4) still has issues and lacks some features compared to
1043 syscons(4). See the wiki for up-to-date information:
1044 https://wiki.freebsd.org/Newcons
1046 If you want to keep using syscons(4), you can do so by adding
1047 the following line to /boot/loader.conf:
1051 pjdfstest has been integrated into kyua as an opt-in test suite.
1052 Please see share/doc/pjdfstest/README for more details on how to
1056 gperf has been removed from the base system for architectures
1057 that use clang. Ports that require gperf will obtain it from the
1061 pjdfstest has been moved from tools/regression/pjdfstest to
1065 At svn r271982, The default linux compat kernel ABI has been adjusted
1066 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1067 update. If you wish to continue using the linux-f10 compat ports,
1068 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1069 encouraged to update their linux-compat packages to linux-c6 during
1070 their next update cycle.
1073 The ofwfb driver, used to provide a graphics console on PowerPC when
1074 using vt(4), no longer allows mmap() of all physical memory. This
1075 will prevent Xorg on PowerPC with some ATI graphics cards from
1076 initializing properly unless x11-servers/xorg-server is updated to
1080 The xdev targets have been converted to using TARGET and
1081 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1084 The default unbound configuration has been modified to address
1085 issues with reverse lookups on networks that use private
1086 address ranges. If you use the local_unbound service, run
1087 "service local_unbound setup" as root to regenerate your
1088 configuration, then "service local_unbound reload" to load the
1092 The GNU texinfo and GNU info pages are not built and installed
1093 anymore, WITH_INFO knob has been added to allow to built and install
1095 UPDATE: see 20150102 entry on texinfo's removal
1098 The GNU readline library is now an INTERNALLIB - that is, it is
1099 statically linked into consumers (GDB and variants) in the base
1100 system, and the shared library is no longer installed. The
1101 devel/readline port is available for third party software that
1105 The Itanium architecture (ia64) has been removed from the list of
1106 known architectures. This is the first step in the removal of the
1110 Commit r268115 has added NFSv4.1 server support, merged from
1111 projects/nfsv4.1-server. Since this includes changes to the
1112 internal interfaces between the NFS related modules, a full
1113 build of the kernel and modules will be necessary.
1114 __FreeBSD_version has been bumped.
1117 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1118 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1119 which differs from the behaviour controlled by this knob.)
1122 Maximal length of the serial number in CTL was increased from 16 to
1123 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1124 and ctld, need to be rebuilt to work with a new kernel.
1127 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1128 1 respectively to match the upstream numbers. They were out of
1129 sync because, when they were originally added to FreeBSD, the
1130 upstream versions were not respected. These libraries are private
1131 and not yet built by default, so renumbering them should be a
1132 non-issue. However, unclean source trees will yield broken test
1133 programs once the operator executes "make delete-old-libs" after a
1134 "make installworld".
1136 Additionally, the atf-sh binary was made private by moving it into
1137 /usr/libexec/. Already-built shell test programs will keep the
1138 path to the old binary so they will break after "make delete-old"
1141 If you are using WITH_TESTS=yes (not the default), wipe the object
1142 tree and rebuild from scratch to prevent spurious test failures.
1143 This is only needed once: the misnumbered libraries and misplaced
1144 binaries have been added to OptionalObsoleteFiles.inc so they will
1145 be removed during a clean upgrade.
1148 Clang and llvm have been upgraded to 3.4.1 release.
1151 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1152 be removed to avoid issues in the future (and has been added to
1156 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1157 past, it affected all builds that used the bsd.*.mk files. The old
1158 behavior was a bug, but people may have relied upon it. To get this
1159 behavior back, you can .include /etc/src.conf from /etc/make.conf
1160 (which is still global and isn't changed). This also changes the
1161 behavior of incremental builds inside the tree of individual
1162 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1163 Although this has survived make universe and some upgrade scenarios,
1164 other upgrade scenarios may have broken. At least one form of
1165 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1166 as well... In cases where MAKESYSPATH isn't working with this
1167 setting, you'll need to set it to the full path to your tree.
1169 One side effect of all this cleaning up is that bsd.compiler.mk
1170 is no longer implicitly included by bsd.own.mk. If you wish to
1171 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1175 The lindev device has been removed since /dev/full has been made a
1176 standard device. __FreeBSD_version has been bumped.
1179 The knob WITHOUT_VI was added to the base system, which controls
1180 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1181 in order to reorder files share/termcap and didn't build ex(1) as a
1182 build tool, so building/installing with WITH_VI is highly advised for
1183 build hosts for older releases.
1185 This issue has been fixed in stable/9 and stable/10 in r277022 and
1186 r276991, respectively.
1189 The YES_HESIOD knob has been removed. It has been obsolete for
1190 a decade. Please move to using WITH_HESIOD instead or your builds
1191 will silently lack HESIOD.
1194 The uart(4) driver has been changed with respect to its handling
1195 of the low-level console. Previously the uart(4) driver prevented
1196 any process from changing the baudrate or the CLOCAL and HUPCL
1197 control flags. By removing the restrictions, operators can make
1198 changes to the serial console port without having to reboot.
1199 However, when getty(8) is started on the serial device that is
1200 associated with the low-level console, a misconfigured terminal
1201 line in /etc/ttys will now have a real impact.
1202 Before upgrading the kernel, make sure that /etc/ttys has the
1203 serial console device configured as 3wire without baudrate to
1204 preserve the previous behaviour. E.g:
1205 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1208 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1209 to improve performance. To re-enable it, if needed, run rpcbind
1210 with command line option -W.
1213 Switched back to the GPL dtc compiler due to updates in the upstream
1214 dts files not being supported by the BSDL dtc compiler. You will need
1215 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1216 may result while building dtb files during a kernel build if you fail
1217 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1220 Clang and llvm have been upgraded to 3.4 release.
1223 The nve(4) driver has been removed. Please use the nfe(4) driver
1224 for NVIDIA nForce MCP Ethernet adapters instead.
1227 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1228 This could cause certain C++ applications using shared libraries built
1229 against the previous version of libc++ to crash. The incompatibility
1230 has now been fixed, but any C++ applications or shared libraries built
1231 between r261283 and r261801 should be recompiled.
1234 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1235 capability mode support. Please note that enabling the feature in
1236 kernel is still highly recommended.
1239 OpenSSH is now built with sandbox support, and will use sandbox as
1240 the default privilege separation method. This requires Capsicum
1241 capability mode support in kernel.
1244 The libelf and libdwarf libraries have been updated to newer
1245 versions from upstream. Shared library version numbers for
1246 these two libraries were bumped. Any ports or binaries
1247 requiring these two libraries should be recompiled.
1248 __FreeBSD_version is bumped to 1100006.
1251 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1252 instead of providing an explicit one, this would prevent such
1253 Makefile from providing its own Kyuafile in the future during
1254 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1255 intervention is needed to clean an objdir if you use NO_CLEAN:
1256 # find /usr/obj -name Kyuafile | xargs rm -f
1259 The behavior of gss_pseudo_random() for the krb5 mechanism
1260 has changed, for applications requesting a longer random string
1261 than produced by the underlying enctype's pseudo-random() function.
1262 In particular, the random string produced from a session key of
1263 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1264 be different at the 17th octet and later, after this change.
1265 The counter used in the PRF+ construction is now encoded as a
1266 big-endian integer in accordance with RFC 4402.
1267 __FreeBSD_version is bumped to 1100004.
1270 The WITHOUT_ATF build knob has been removed and its functionality
1271 has been subsumed into the more generic WITHOUT_TESTS. If you were
1272 using the former to disable the build of the ATF libraries, you
1273 should change your settings to use the latter.
1276 The default version of mtree is nmtree which is obtained from
1277 NetBSD. The output is generally the same, but may vary
1278 slightly. If you found you need identical output adding
1279 "-F freebsd9" to the command line should do the trick. For the
1280 time being, the old mtree is available as fmtree.
1283 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1284 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1285 1.1.4_8 and verify bsdyml not linked in, before running "make
1287 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1289 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1292 The stable/10 branch has been created in subversion from head
1296 The rc.d/jail script has been updated to support jail(8)
1297 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1298 for per-jail configuration are automatically converted to
1299 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1300 This is transparently backward compatible. See below about some
1301 incompatibilities and rc.conf(5) manual page for more details.
1303 These variables are now deprecated in favor of jail(8) configuration
1304 file. One can use "rc.d/jail config <jname>" command to generate
1305 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1306 running the jail(8) utility. The default pathname of the
1307 configuration file is /etc/jail.conf and can be specified by
1308 using $jail_conf or $jail_<jname>_conf variables.
1310 Please note that jail_devfs_ruleset accepts an integer at
1311 this moment. Please consider to rewrite the ruleset name
1315 BIND has been removed from the base system. If all you need
1316 is a local resolver, simply enable and start the local_unbound
1317 service instead. Otherwise, several versions of BIND are
1318 available in the ports tree. The dns/bind99 port is one example.
1320 With this change, nslookup(1) and dig(1) are no longer in the base
1321 system. Users should instead use host(1) and drill(1) which are
1322 in the base system. Alternatively, nslookup and dig can
1323 be obtained by installing the dns/bind-tools port.
1326 With the addition of unbound(8), a new unbound user is now
1327 required during installworld. "mergemaster -p" can be used to
1328 add the user prior to installworld, as documented in the handbook.
1331 OpenSSH is now built with DNSSEC support, and will by default
1332 silently trust signed SSHFP records. This can be controlled with
1333 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1334 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1337 The GNU Compiler Collection and C++ standard library (libstdc++)
1338 are no longer built by default on platforms where clang is the system
1339 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1340 options in src.conf.
1343 The PROCDESC kernel option is now part of the GENERIC kernel
1344 configuration and is required for the rwhod(8) to work.
1345 If you are using custom kernel configuration, you should include
1349 The API and ABI related to the Capsicum framework was modified
1350 in backward incompatible way. The userland libraries and programs
1351 have to be recompiled to work with the new kernel. This includes the
1352 following libraries and programs, but the whole buildworld is
1353 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1354 kdump, procstat, rwho, rwhod, uniq.
1357 AES-NI intrinsic support has been added to gcc. The AES-NI module
1358 has been updated to use this support. A new gcc is required to build
1359 the aesni module on both i386 and amd64.
1362 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1363 Thus "device padlock_rng" and "device rdrand_rng" should be
1364 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1367 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1368 enables just the iconv* functionality and is now on by default.
1369 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1370 compatibility. Set WITHOUT_ICONV to build the old way.
1371 If you have been using WITH_ICONV before, you will very likely
1372 need to turn on WITH_LIBICONV_COMPAT.
1375 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1376 Illumos origin, including ZFS. If you have INVARIANTS in your
1377 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1379 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1380 locks if WITNESS option was set. Because that generated a lot of
1381 witness(9) reports and all of them were believed to be false
1382 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1383 can be used to achieve the previous behavior.
1386 Timer values in IPv6 data structures now use time_uptime instead
1387 of time_second. Although this is not a user-visible functional
1388 change, userland utilities which directly use them---ndp(8),
1389 rtadvd(8), and rtsold(8) in the base system---need to be updated
1390 to r253970 or later.
1393 find -delete can now delete the pathnames given as arguments,
1394 instead of only files found below them or if the pathname did
1395 not contain any slashes. Formerly, the following error message
1398 find: -delete: <path>: relative path potentially not safe
1400 Deleting the pathnames given as arguments can be prevented
1401 without error messages using -mindepth 1 or by changing
1402 directory and passing "." as argument to find. This works in the
1403 old as well as the new version of find.
1406 Behavior of devfs rules path matching has been changed.
1407 Pattern is now always matched against fully qualified devfs
1408 path and slash characters must be explicitly matched by
1409 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1410 subdirectories must be reviewed.
1413 The default ARM ABI has changed to the ARM EABI. The old ABI is
1414 incompatible with the ARM EABI and all programs and modules will
1415 need to be rebuilt to work with a new kernel.
1417 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1419 NOTE: Support for the old ABI will be removed in the future and
1420 users are advised to upgrade.
1423 pkg_install has been disconnected from the build if you really need it
1424 you should add WITH_PKGTOOLS in your src.conf(5).
1427 Most of network statistics structures were changed to be able
1428 keep 64-bits counters. Thus all tools, that work with networking
1429 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1432 Fix a bug that allowed a tracing process (e.g. gdb) to write
1433 to a memory-mapped file in the traced process's address space
1434 even if neither the traced process nor the tracing process had
1435 write access to that file.
1438 CVS has been removed from the base system. An exact copy
1439 of the code is available from the devel/cvs port.
1442 Some people report the following error after the switch to bmake:
1444 make: illegal option -- J
1445 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1447 *** [buildworld] Error code 2
1449 this likely due to an old instance of make in
1450 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1451 which src/Makefile will use that blindly, if it exists, so if
1452 you see the above error:
1454 rm -rf `make -V MAKEPATH`
1459 Use bmake by default.
1460 Whereas before one could choose to build with bmake via
1461 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1462 make. The goal is to remove these knobs for 10-RELEASE.
1464 It is worth noting that bmake (like gmake) treats the command
1465 line as the unit of failure, rather than statements within the
1466 command line. Thus '(cd some/where && dosomething)' is safer
1467 than 'cd some/where; dosomething'. The '()' allows consistent
1468 behavior in parallel build.
1471 Fix a bug that allows NFS clients to issue READDIR on files.
1474 The WITHOUT_IDEA option has been removed because
1475 the IDEA patent expired.
1478 The sysctl which controls TRIM support under ZFS has been renamed
1479 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1483 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1484 rather than creating it's own in the temporary directory in
1485 order allow access to bootstrapped versions of tools such as
1486 install and mtree. When upgrading from version of FreeBSD where
1487 the install command does not support -l, you will need to
1488 install a new mergemaster command if mergemaster -p is required.
1489 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1493 Legacy ATA stack, disabled and replaced by new CAM-based one since
1494 FreeBSD 9.0, completely removed from the sources. Kernel modules
1495 atadisk and atapi*, user-level tools atacontrol and burncd are
1496 removed. Kernel option `options ATA_CAM` is now permanently enabled
1500 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1501 and socketpair(2). Software, in particular Kerberos, may
1502 automatically detect and use these during building. The resulting
1503 binaries will not work on older kernels.
1506 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1507 information, see the respective 20130304 entry).
1510 Recent commits to callout(9) changed the size of struct callout,
1511 so the KBI is probably heavily disturbed. Also, some functions
1512 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1513 by macros. Every kernel module using it won't load, so rebuild
1516 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1517 but does not initialize by default (because of the new CTL_DISABLE
1518 option) to save memory. To re-enable it, remove the CTL_DISABLE
1519 option from the kernel config file or set kern.cam.ctl.disable=0
1520 in /boot/loader.conf.
1523 The ctl device has been disabled in GENERIC for i386 and amd64.
1524 This was done due to the extra memory being allocated at system
1525 initialisation time by the ctl driver which was only used if
1526 a CAM target device was created. This makes a FreeBSD system
1527 unusable on 128MB or less of RAM.
1530 A new compression method (lz4) has been merged to -HEAD. Please
1531 refer to zpool-features(7) for more information.
1533 Please refer to the "ZFS notes" section of this file for information
1534 on upgrading boot ZFS pools.
1537 A BSD-licensed patch(1) variant has been added and is installed
1538 as bsdpatch, being the GNU version the default patch.
1539 To inverse the logic and use the BSD-licensed one as default,
1540 while having the GNU version installed as gnupatch, rebuild
1541 and install world with the WITH_BSD_PATCH knob set.
1544 Due to the use of the new -l option to install(1) during build
1545 and install, you must take care not to directly set the INSTALL
1546 make variable in your /etc/make.conf, /etc/src.conf, or on the
1547 command line. If you wish to use the -C flag for all installs
1548 you may be able to add INSTALL+=-C to /etc/make.conf or
1552 The install(1) option -M has changed meaning and now takes an
1553 argument that is a file or path to append logs to. In the
1554 unlikely event that -M was the last option on the command line
1555 and the command line contained at least two files and a target
1556 directory the first file will have logs appended to it. The -M
1557 option served little practical purpose in the last decade so its
1558 use is expected to be extremely rare.
1561 After switching to Clang as the default compiler some users of ZFS
1562 on i386 systems started to experience stack overflow kernel panics.
1563 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1566 GEOM_LABEL now mangles label names read from file system metadata.
1567 Mangling affect labels containing spaces, non-printable characters,
1568 '%' or '"'. Device names in /etc/fstab and other places may need to
1572 By default, only the 10 most recent kernel dumps will be saved. To
1573 restore the previous behaviour (no limit on the number of kernel dumps
1574 stored in the dump directory) add the following line to /etc/rc.conf:
1579 With the addition of auditdistd(8), a new auditdistd user is now
1580 required during installworld. "mergemaster -p" can be used to
1581 add the user prior to installworld, as documented in the handbook.
1584 The sin6_scope_id member variable in struct sockaddr_in6 is now
1585 filled by the kernel before passing the structure to the userland via
1586 sysctl or routing socket. This means the KAME-specific embedded scope
1587 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1588 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1589 __FreeBSD_version is bumped to 1000025.
1592 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1593 This means that the world and kernel will be compiled with clang
1594 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1595 and /usr/bin/cpp. To disable this behavior and revert to building
1596 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1597 of current may need to bootstrap WITHOUT_CLANG first if the clang
1598 build fails (its compatibility window doesn't extend to the 9 stable
1602 The IPFIREWALL_FORWARD kernel option has been removed. Its
1603 functionality now turned on by default.
1606 The ZERO_COPY_SOCKET kernel option has been removed and
1607 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1608 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1609 mechanism which is not safe and may result in kernel crashes.
1610 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1611 driver supports disposeable external page sized mbuf storage.
1612 Proper replacements for both zero-copy mechanisms are under
1613 consideration and will eventually lead to complete removal
1614 of the two kernel options.
1617 The IPv4 network stack has been converted to network byte
1618 order. The following modules need to be recompiled together
1619 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1620 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1623 Support for non-MPSAFE filesystems was removed from VFS. The
1624 VFS_VERSION was bumped, all filesystem modules shall be
1628 All the non-MPSAFE filesystems have been disconnected from
1629 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1630 portalfs, smbfs, xfs.
1633 The interface cloning API and ABI has changed. The following
1634 modules need to be recompiled together with kernel:
1635 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1636 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1637 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1640 The sdhci driver was split in two parts: sdhci (generic SD Host
1641 Controller logic) and sdhci_pci (actual hardware driver).
1642 No kernel config modifications are required, but if you
1643 load sdhc as a module you must switch to sdhci_pci instead.
1646 Import the FUSE kernel and userland support into base system.
1649 The GNU sort(1) program has been removed since the BSD-licensed
1650 sort(1) has been the default for quite some time and no serious
1651 problems have been reported. The corresponding WITH_GNU_SORT
1655 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1656 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1660 The net80211(4) ABI has been changed to allow for improved driver
1661 PS-POLL and power-save support. All wireless drivers need to be
1662 recompiled to work with the new kernel.
1665 The random(4) support for the VIA hardware random number
1666 generator (`PADLOCK') is no longer enabled unconditionally.
1667 Add the padlock_rng device in the custom kernel config if
1668 needed. The GENERIC kernels on i386 and amd64 do include the
1669 device, so the change only affects the custom kernel
1673 The pf(4) packet filter ABI has been changed. pfctl(8) and
1674 snmp_pf module need to be recompiled to work with new kernel.
1677 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1678 to -HEAD. Pools that have empty_bpobj in active state can not be
1679 imported read-write with ZFS implementations that do not support
1680 this feature. For more information read the zpool-features(5)
1684 The sparc64 ZFS loader has been changed to no longer try to auto-
1685 detect ZFS providers based on diskN aliases but now requires these
1686 to be explicitly listed in the OFW boot-device environment variable.
1689 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1690 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1691 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1694 The following sysctls and tunables have been renamed for consistency
1695 with other variables:
1696 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1697 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1700 The sort utility has been replaced with BSD sort. For now, GNU sort
1701 is also available as "gnusort" or the default can be set back to
1702 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1703 installed as "bsdsort".
1706 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1707 Starting with this version the old system of ZFS pool versioning
1708 is superseded by "feature flags". This concept enables forward
1709 compatibility against certain future changes in functionality of ZFS
1710 pools. The first read-only compatible "feature flag" for ZFS pools
1711 is named "com.delphix:async_destroy". For more information
1712 read the new zpool-features(5) manual page.
1713 Please refer to the "ZFS notes" section of this file for information
1714 on upgrading boot ZFS pools.
1717 The malloc(3) implementation embedded in libc now uses sources imported
1718 as contrib/jemalloc. The most disruptive API change is to
1719 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1720 delete it prior to installworld, and optionally re-create it using the
1721 new format after rebooting. See malloc.conf(5) for details
1722 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1726 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1727 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1728 now spelled mips. This is to aid compatibility with third-party
1729 software that expects this naming scheme in uname(3). Little-endian
1730 settings are unchanged. If you are updating a big-endian mips64 machine
1731 from before this change, you may need to set MACHINE_ARCH=mips64 in
1732 your environment before the new build system will recognize your machine.
1735 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1739 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1740 nullfs(5) did not pass through all behaviours to the underlying layer,
1741 as a result if we bound to a socket on the lower layer we could connect
1742 only to the lower path; if we bound to the upper layer we could connect
1743 only to the upper path. The new behavior is one can connect to both the
1744 lower and the upper paths regardless what layer path one binds to.
1747 The getifaddrs upgrade path broken with 20111215 has been restored.
1748 If you have upgraded in between 20111215 and 20120209 you need to
1749 recompile libc again with your kernel. You still need to recompile
1750 world to be able to configure CARP but this restriction already
1751 comes from 20111215.
1754 The set_rcvar() function has been removed from /etc/rc.subr. All
1755 base and ports rc.d scripts have been updated, so if you have a
1756 port installed with a script in /usr/local/etc/rc.d you can either
1757 hand-edit the rcvar= line, or reinstall the port.
1759 An easy way to handle the mass-update of /etc/rc.d:
1760 rm /etc/rc.d/* && mergemaster -i
1763 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1764 on the current CPU and prevents other threads from running.
1765 This behavior can be reverted using the kern.stop_scheduler_on_panic
1767 The new behavior can be incompatible with kern.sync_on_panic.
1770 The carp(4) facility has been changed significantly. Configuration
1771 of the CARP protocol via ifconfig(8) has changed, as well as format
1772 of CARP events submitted to devd(8) has changed. See manual pages
1773 for more information. The arpbalance feature of carp(4) is currently
1774 not supported anymore.
1776 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1777 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1778 need to be recompiled.
1781 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1785 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1786 explicitely support non-MPSAFE filesystems.
1787 It is on by default for all supported platform at this present
1791 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1792 i386 and pc98 GENERIC kernel configuration files.
1795 sysinstall has been removed
1798 The stable/9 branch created in subversion. This corresponds to the
1799 RELENG_9 branch in CVS.
1805 Avoid using make -j when upgrading. While generally safe, there are
1806 sometimes problems using -j to upgrade. If your upgrade fails with
1807 -j, please try again without -j. From time to time in the past there
1808 have been problems using -j with buildworld and/or installworld. This
1809 is especially true when upgrading between "distant" versions (eg one
1810 that cross a major release boundary or several minor releases, or when
1811 several months have passed on the -current branch).
1813 Sometimes, obscure build problems are the result of environment
1814 poisoning. This can happen because the make utility reads its
1815 environment when searching for values for global variables. To run
1816 your build attempts in an "environmental clean room", prefix all make
1817 commands with 'env -i '. See the env(1) manual page for more details.
1819 When upgrading from one major version to another it is generally best
1820 to upgrade to the latest code in the currently installed branch first,
1821 then do an upgrade to the new branch. This is the best-tested upgrade
1822 path, and has the highest probability of being successful. Please try
1823 this approach before reporting problems with a major version upgrade.
1825 When upgrading a live system, having a root shell around before
1826 installing anything can help undo problems. Not having a root shell
1827 around can lead to problems if pam has changed too much from your
1828 starting point to allow continued authentication after the upgrade.
1830 This file should be read as a log of events. When a later event changes
1831 information of a prior event, the prior event should not be deleted.
1832 Instead, a pointer to the entry with the new information should be
1833 placed in the old entry. Readers of this file should also sanity check
1834 older entries before relying on them blindly. Authors of new entries
1835 should write them with this in mind.
1839 When upgrading the boot ZFS pool to a new version, always follow
1842 1.) recompile and reinstall the ZFS boot loader and boot block
1843 (this is part of "make buildworld" and "make installworld")
1845 2.) update the ZFS boot block on your boot drive
1847 The following example updates the ZFS boot block on the first
1848 partition (freebsd-boot) of a GPT partitioned drive ada0:
1849 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1851 Non-boot pools do not need these updates.
1855 If you are updating from a prior version of FreeBSD (even one just
1856 a few days old), you should follow this procedure. It is the most
1857 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1859 make kernel-toolchain
1860 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1861 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1863 To test a kernel once
1864 ---------------------
1865 If you just want to boot a kernel once (because you are not sure
1866 if it works, or if you want to boot a known bad kernel to provide
1867 debugging information) run
1868 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1869 nextboot -k testkernel
1871 To just build a kernel when you know that it won't mess you up
1872 --------------------------------------------------------------
1873 This assumes you are already running a CURRENT system. Replace
1874 ${arch} with the architecture of your machine (e.g. "i386",
1875 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1877 cd src/sys/${arch}/conf
1878 config KERNEL_NAME_HERE
1879 cd ../compile/KERNEL_NAME_HERE
1884 If this fails, go to the "To build a kernel" section.
1886 To rebuild everything and install it on the current system.
1887 -----------------------------------------------------------
1888 # Note: sometimes if you are running current you gotta do more than
1889 # is listed here if you are upgrading from a really old current.
1891 <make sure you have good level 0 dumps>
1893 make kernel KERNCONF=YOUR_KERNEL_HERE
1895 <reboot in single user> [3]
1902 To cross-install current onto a separate partition
1903 --------------------------------------------------
1904 # In this approach we use a separate partition to hold
1905 # current's root, 'usr', and 'var' directories. A partition
1906 # holding "/", "/usr" and "/var" should be about 2GB in
1909 <make sure you have good level 0 dumps>
1912 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1913 <maybe newfs current's root partition>
1914 <mount current's root partition on directory ${CURRENT_ROOT}>
1915 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1916 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1917 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1918 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1919 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1920 <reboot into current>
1921 <do a "native" rebuild/install as described in the previous section>
1922 <maybe install compatibility libraries from ports/misc/compat*>
1926 To upgrade in-place from stable to current
1927 ----------------------------------------------
1928 <make sure you have good level 0 dumps>
1930 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1932 <reboot in single user> [3]
1939 Make sure that you've read the UPDATING file to understand the
1940 tweaks to various things you need. At this point in the life
1941 cycle of current, things change often and you are on your own
1942 to cope. The defaults can also change, so please read ALL of
1943 the UPDATING entries.
1945 Also, if you are tracking -current, you must be subscribed to
1946 freebsd-current@freebsd.org. Make sure that before you update
1947 your sources that you have read and understood all the recent
1948 messages there. If in doubt, please track -stable which has
1949 much fewer pitfalls.
1951 [1] If you have third party modules, such as vmware, you
1952 should disable them at this point so they don't crash your
1955 [3] From the bootblocks, boot -s, and then do
1960 adjkerntz -i # if CMOS is wall time
1961 Also, when doing a major release upgrade, it is required that
1962 you boot into single user mode to do the installworld.
1964 [4] Note: This step is non-optional. Failure to do this step
1965 can result in a significant reduction in the functionality of the
1966 system. Attempting to do it by hand is not recommended and those
1967 that pursue this avenue should read this file carefully, as well
1968 as the archives of freebsd-current and freebsd-hackers mailing lists
1969 for potential gotchas. The -U option is also useful to consider.
1970 See mergemaster(8) for more information.
1972 [5] Usually this step is a noop. However, from time to time
1973 you may need to do this if you get unknown user in the following
1974 step. It never hurts to do it all the time. You may need to
1975 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1976 install) after the buildworld before this step if you last updated
1977 from current before 20130425 or from -stable before 20130430.
1979 [6] This only deletes old files and directories. Old libraries
1980 can be deleted by "make delete-old-libs", but you have to make
1981 sure that no program is using those libraries anymore.
1983 [8] The new kernel must be able to run existing binaries used by
1984 an installworld. When upgrading across major versions, the new
1985 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1986 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1987 binaries). Failure to do so may leave you with a system that is
1988 hard to boot to recover. A GENERIC kernel will include suitable
1989 compatibility options to run binaries from older branches.
1991 Make sure that you merge any new devices from GENERIC since the
1992 last time you updated your kernel config file.
1994 [9] When checking out sources, you must include the -P flag to have
1995 cvs prune empty directories.
1997 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1998 "?=" instead of the "=" assignment operator, so that buildworld can
1999 override the CPUTYPE if it needs to.
2001 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2002 not on the command line, or in /etc/make.conf. buildworld will
2003 warn if it is improperly defined.
2006 This file contains a list, in reverse chronological order, of major
2007 breakages in tracking -current. It is not guaranteed to be a complete
2008 list of such breakages, and only contains entries since September 23, 2011.
2009 If you need to see UPDATING entries from before that date, you will need
2010 to fetch an UPDATING file from an older FreeBSD release.
2012 Copyright information:
2014 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2016 Redistribution, publication, translation and use, with or without
2017 modification, in full or in part, in any form or format of this
2018 document are permitted without further permission from the author.
2020 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2021 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2022 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2023 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2024 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2025 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2026 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2027 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2028 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2029 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2030 POSSIBILITY OF SUCH DAMAGE.
2032 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob