1 Updating Information for users of FreeBSD-CURRENT.
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://docs.freebsd.org/en/books/handbook/cutting-edge/#makeworld
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before updating system packages
15 NOTE TO PEOPLE WHO THINK THAT FreeBSD 15.x IS SLOW:
16 FreeBSD 15.x has many debugging features turned on, in both the kernel
17 and userland. These features attempt to detect incorrect use of
18 system primitives, and encourage loud failure through extra sanity
19 checking and fail stop semantics. They also substantially impact
20 system performance. If you want to do performance measurement,
21 benchmarking, and optimization, you'll want to turn them off. This
22 includes various WITNESS- related kernel options, INVARIANTS, malloc
23 debugging flags in userland, and various verbose features in the
24 kernel. Many developers choose to disable these features on build
25 machines to maximize performance. (To completely disable malloc
26 debugging, define WITH_MALLOC_PRODUCTION in /etc/src.conf and rebuild
27 world, or to merely disable the most expensive debugging functionality
28 at runtime, run "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
31 The support for the rc_fast_and_loose variable has been removed from
32 rc.subr(8). Users setting rc_fast_and_loose on their systems are
33 advised to make sure their customizations to rc service scripts
34 do not depend on having a single shell environment shared across
35 all the rc service scripts during booting and shutdown.
38 The ciss driver was updated to cope better with hotplug events that
39 caused it to panic before, and to support more than 48 drives attached
40 to the card. These changes were made w/o benefit of hardware for testing
41 and ciss(4) users should be on the lookout for regressions.
44 The build now defaults to WITHOUT_CLEAN - i.e., no automatic clean
45 is performed at the beginning of buildworld or buildkernel. The
46 WITH_CLEAN src.conf(5) knob can be used to restore the previous
49 If you encounter incremental build issues, please report them to the
50 freebsd-current mailing list so that a special-case dependency can be
54 We now lean more heavily on ACPI enumeration for some traditional
55 devices. uart has moved from isa to acpi so the hints act as wiring
56 instead of device enumeration. Hints for parallel port, floppy, etc
57 have been removed. Before upgrading, grep your dmesg for lines like:
58 uart1: non-PNP ISA device will be removed from GENERIC in FreeBSD 15.
59 to see if you need to start including hints for the device on isa
60 in your loader.conf or device.hints file. APU1 (but not APU2) boards
61 are known to be affected, but there may be others.
64 Support for armv6 has been disconnected and is being removed.
67 ifconfig now treats IPv4 addresses without a width or mask as an error.
68 Specify the desired mask or width along with the IP address on the
69 ifconfig command line and in rc.conf.
72 OpenBSM auditing runtime (auditd, etc.) has been moved into the new
73 package FreeBSD-audit. If you use OpenBSM auditing and pkgbase, you
74 should install FreeBSD-audit.
77 cron, lpr, and ntpd have been moved from FreeBSD-utilities into their
78 own packages. If you use pkgbase, you should install the relevant
79 packages: FreeBSD-cron, FreeBSD-lp, or FreeBSD-ntp.
82 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
83 been upgraded to 18.1.6. It is important that you run `make delete-old`
84 as described in the COMMON ITEMS section, otherwise several libc++
85 headers that are obsolete and need to be removed can cause compilation
86 errors in C++ programs.
89 For dynamically linked programs, system calls are now made from
90 libsys rather than libc. No change in linkage is required as
91 libsys is an auxiliary filter for libc. People building custom
92 images must ensure that libsys.so.7 is included.
95 Loader now also read configuration files listed in local_loader_conf_files.
96 Files listed here are the last ones read. And /boot/loader.conf.local was
97 moved from loader_conf_files to local_loader_conf_files leaving only
98 loader.conf and device.hints in loader_conf_files by default.
100 The following sequencing is applied:
103 /boot/defaults/loader.conf
105 2. Read loader_conf_files files:
109 3. Read loader_conf_dirs files:
110 /boot/loader.conf.d/*.conf
112 4. And finally, rread local_loader_conf_files files:
113 /boot/loader.conf.local
116 sendmail 8.18.1 has been imported and merged. This version enforces
117 stricter RFC compliance by default, especially with respect to line
118 endings. This may cause issues with receiving messages from
119 non-compliant MTAs; please see the first 8.18.1 release note in
120 contrib/sendmail/RELEASE_NOTES for mitigations.
123 Commit cc760de2183f changed the internal interface between
124 the nfscommon and nfscl modules. As such, both need to be
125 rebuilt from sources. Therefore, __FreeBSD_version was
129 If you have an arm64 system that uses ACPI, you will need to update your
130 loader.efi in the ESP when you update past this point. Detection of ACPI
131 was moved earlier in the binary so the scripts could use it, but old
132 binaries don't have this, so we default to 'no ACPI' in this case. You can
133 undisable ACPI by doing
134 OK unset hint.acpi.0.disabled
135 This can also be used to recover any other system that was updated in the
136 small window where amd64 was also broken.
139 The WITHOUT_LLD_IS_LD option has been removed. When LLD is enabled
140 it is always installed as /usr/bin/ld.
143 Forward compatibility (running the new code on old kernels) for the
144 "ino64" project have been removed. The need for it has passed long ago.
147 Commit 57ce37f9dcd0 changed the internal KAPI between the
148 nfscommon and nfscl modules. Both must be rebuilt from sources.
151 dialog(1) has been replaced in base by bsddialog(1), while most of the
152 time replacing a dialog(1) call by a bsddialog(1) call works out of the
153 box, bsddialog(1) is not considered as a drop-in replacement for
156 If you do depend on dialog(1) functionality, please install cdialog
162 The EARLY_AP_STARTUP kernel option is mandatory on x86. The option
163 has been added to DEFAULTS, so it should automatically be included in
164 custom kernel configurations without any additional change.
167 A new loader tunable net.pf.default_to_drop allows pf(4)’s default
168 behaviour to be changed from pass to drop. Previously this required
169 recompiling the kernel with the option PF_DEFAULT_TO_DROP.
172 Enable splitting out pkgbase manpages into separate packages by
173 default. To disable this, set WITHOUT_MANSPLITPKG=yes in src.conf.
176 Move standard include files to the clibs-dev package and move clang
177 internal libraries and headers to clang and clang-dev. Upgrading systems
178 installed using pkgbase past this change involves extra steps to allow
179 for these file moves:
181 pkg upgrade -y FreeBSD-utilities
182 pkg upgrade -y FreeBSD-utilities-dev
186 Enable vnet sysctl variables to be loader tunable. SYSCTLs which
187 belongs to VNETs can be initialized during early boot or module
188 loading if they are marked with CTLFLAG_TUN and there are
189 corresponding kernel environment variables.
192 The WITH_INIT_ALL_PATTERN and WITH_INIT_ALL_ZERO build options have
193 been replaced by INIT_ALL=pattern and INIT_ALL=zero respectively.
196 FreeBSD 15.0-CURRENT.
199 Serial communication (in boot loaders, kernel, and userland) has
200 been changed to default to 115200 bps, in line with common industry
201 practice and typcial firmware serial console redirection
204 Note that the early x86 BIOS bootloader (i.e., boot0sio) does not
205 support rates above 9600 bps and is not changed. boot0sio users may
206 set BOOT_COMCONSOLE_SPEED=9600 to use 9600 for all of the boot
207 components, or use the standard boot0 and have the boot2 stage start
208 with the serial port at 115200.
211 Following the general removal of MIPS support, the ath(4) AHB bus-
212 frontend has been removed, too, and building of the PCI support is
213 integrated with the ath(4) main module again. As a result, there's
214 no longer a need for if_ath_pci_load="YES" in /boot/loader.conf or
215 "device ath_pci" in the kernel configuration.
218 MAXCPU has been increased to 1024 in the amd64 GENERIC kernel config.
219 Out-of-tree kernel modules will need to be rebuilt.
222 CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g
223 to move to the standard uintXX_t types from the old, traditional
224 BSD u_intXX_t types. This should be a NOP, but may cause problems
225 for out of tree changes. The SIMs were not updated since most of
226 the old u_intXX_t uses weren't due to CAM interfaces.
229 stable/14 branch created.
232 The heuristic for detecting old chromebooks with an EC bug that requires
233 atkbdc driver workarounds has changed. There should be no functional
234 change, but if your old chromebook's keyboard stops working, please
235 file a PR and assign it to imp.
238 OpenSSL has been updated to version 3.0, including changes throughout
239 the base system. It is important to rebuild third-party software
243 To enable pf rdr rules for connections initiated from the host, pf
244 filter rules can be optionally enabled for packets delivered
245 locally. This can change the behavior of rules which match packets
246 delivered to lo0. To enable this feature:
248 sysctl net.pf.filter_local=1
251 When enabled, its best to ensure that packets delivered locally are not
252 filtered, e.g. by adding a 'skip on lo' rule.
255 Improvements to libtacplus(8) mean that tacplus.conf(5) now
256 follows POSIX shell syntax rules. This may cause TACACS+
257 authentication to fail if the shared secret contains a single
258 quote, double quote, or backslash character which isn't
259 already properly quoted or escaped.
262 Belatedly switch the default nvme block device on x86 from nvd to nda.
263 nda created nvd compatibility links by default, so this should be a
264 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
265 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
266 config. To disable the nvd compatibility aliases, add
267 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
268 all non-x86 platforms for some time now. If you need to fall back,
269 please email imp@freebsd.org about why.
271 Encrypted swap partitions need to be changed from nvd to nda if you
272 migrate, or you need to use the above to switch back to nvd.
275 Remove portsnap(8). Users are encouraged to obtain the ports tree
279 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
283 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
285 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
288 Video related devices for some arm devices have been renamed.
289 If you have a custom kernel config and want to use hdmi output on
290 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
291 "device imx6_ipu" to it.
292 If you have a custom kernel config and want to use hdmi output on
293 TI AM335X board you need to add "device tda19988" to it.
294 If you add "device hdmi" in it you need to remove it as it doesn't
298 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
302 sshd now defaults to having X11Forwarding disabled, following upstream.
303 Administrators who wish to enable X11Forwarding should add
304 `X11Forwarding yes` to /etc/ssh/sshd_config.
307 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
308 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
311 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
312 to the linux_common(4) module. Users relying on linux_common may need
313 to complile netlink(4) module if it is not present in their kernel.
316 The WITHOUT_CXX option has been removed. C++ components in the base
317 system are now built unconditionally.
320 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
321 Bump _FreeBSD_version to 1400078 to be able to detect this change.
324 llvm-objump is now always installed as objdump. Previously there was
325 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
327 Some LLVM objdump options have a different output format compared to
328 GNU objdump; readelf is available for inspecting ELF files, and GNU
329 objdump is available from the devel/binutils port or package.
332 dma(8) has replaced sendmail(8) as the default mta. For people willing
333 to reenable sendmail(8):
335 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
337 and add sendmail_enable="YES" to rc.conf.
340 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
341 default. Now if newbus succeeds in probing a device, but fails to attach
342 the device, we'll disable the device. In the past, we'd keep retrying
343 the device on each new driver loaded. To get that behavior now, one
344 needs to use devctl to re-enable the device, and reprobe it (or set
345 the sysctl/tunable hw.bus.disable_failed_devices=false).
347 NOTE: This was reverted 20221205 due to unexpected compatibility issues
350 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
351 These configurations are no longer automatically reinterpreted as
352 'scrub fragment reassemble'.
355 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
356 it is always installed as /usr/bin/cc (and c++, cpp).
359 Some programs have been moved into separate packages. It is recommended
360 for pkgbase users to do:
362 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
363 FreeBSD-devd FreeBSD-devmatch
365 after upgrading to restore all the component that were previously
369 OPIE has been removed from the base system. If needed, it can
370 be installed from ports (security/opie) or packages (opie).
371 Otherwise, make sure that your PAM policies do not reference
372 pam_opie or pam_opieaccess.
375 LinuxKPI pm.h changes require an update to the latest drm-kmod version
376 before re-compiling to avoid errors.
379 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
380 have been modified to take 2 source arguments instead of only 1.
381 Externally maintained sources that use these macros will have to
382 be adapted. The FreeBSD version has been bumped to 1400046 to
386 A number of the kernel include files are able to be included by
387 themselves. A test has been added to buildworld to enforce this.
390 Remove mips as a recognized target. This starts the decommissioning of
391 mips support in FreeBSD. mips related items will be removed wholesale in
392 the coming days and weeks.
394 This broke the NO_CLEAN build for some people. Either do a clean build
396 lib/clang/include/llvm/Config/Targets.def
397 lib/clang/include/llvm/Config/AsmParsers.def
398 lib/clang/include/llvm/Config/Disassemblers.def
399 lib/clang/include/llvm/Config/AsmPrinters.def
400 before the build to force everything to rebuild that needs to.
403 Unbound support for RFC8375: The special-use domain 'home.arpa' is
404 by default blocked. To unblock it use a local-zone nodefault
405 statement in unbound.conf:
406 local-zone: "home.arpa." nodefault
408 Or use another type of local-zone to override with your choice.
410 The reason for this is discussed in Section 6.1 of RFC8375:
411 Because 'home.arpa.' is not globally scoped and cannot be secured
412 using DNSSEC based on the root domain's trust anchor, there is no way
413 to tell, using a standard DNS query, in which homenet scope an answer
414 belongs. Consequently, users may experience surprising results with
415 such names when roaming to different homenets.
418 Commit b8d60729deef changed the TCP congestion control framework so
419 that any of the included congestion control modules could be
420 the single module built into the kernel. Previously newreno
421 was automatically built in through direct reference. As of
422 this commit you are required to declare at least one congestion
423 control module (e.g. 'options CC_NEWRENO') and to also declare a
424 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
425 The GENERIC configuration includes CC_NEWRENO and defines newreno
426 as the default. If no congestion control option is built into the
427 kernel and you are including networking, the kernel compile will
428 fail. Also if no default is declared the kernel compile will fail.
431 Mips has been removed from universe builds. It will be removed from the
435 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
436 The NFS modules must be rebuilt from sources and any out
437 of tree file systems that implement their own VOP_ALLOCATE
438 may need to be modified.
441 The synchronous PPP kernel driver sppp(4) has been removed.
442 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
443 support, formerly enabled by NETGRAPH_CRONYX option.
446 sh(1) is now the default shell for the root user. To force root to use
447 the csh shell, please run the following command as root:
452 Ncurses distribution has been split between libtinfow and libncurses
453 with libncurses.so becoming a linker (ld) script to seamlessly link
454 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
458 As of commit 8160a0f62be6, the dummynet module no longer depends on the
459 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
460 users who relied on this dependency may need to include ipfw in the
461 list of modules to load on their systems.
464 As of commit 903873ce1560, the mixer(8) utility has got a slightly
465 new syntax. Please refer to the mixer(8) manual page for more
466 information. The old mixer utility can be installed from ports:
467 audio/freebsd-13-mixer
470 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
471 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
472 from up to date sources to avoid an undefined reference when
476 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
477 by default. Users can enable kernel TLS via the "KTLS" SSL
478 option. This can be enabled globally by using a custom
479 OpenSSL config file via OPENSSL_CONF or via an
480 application-specific configuration option for applications
481 which permit setting SSL options via SSL_CONF_cmd(3).
484 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
485 modules. Therefore, all need to be rebuilt from sources.
488 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
489 As of be70c7a50d32 it is no longer used by userspace, but it does mean
490 users may not be able to enumerate pf states if they update the kernel
491 past b69019c14cd8 without first updating userspace past be70c7a50d32.
494 As of commit 01ad0c007964 if_bridge member interfaces can no longer
495 change their MTU. Changing the MTU of the bridge itself will change the
496 MTU on all member interfaces instead.
499 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
500 and nfsd modules. Therefore, both need to be rebuilt from sources.
501 Bump __FreeBSD_version to 1400026 for this KAPI change.
504 The 20210707 awk update brought in a change in behavior. This has
505 been corrected as of d4d252c49976. Between these dates, if you
506 installed a new awk binary, you may not be able to build a new
507 kernel because the change in behavior affected the genoffset
508 script used to build the kernel. If you did update, the fix is
509 to update your sources past the above hash and do
512 % sudo -E make install
513 to enable building kernels again.
516 Commit 1e0a518d6548 changed the internal KAPI between the NFS
517 modules. They all need to be rebuilt from sources. I did not
518 bump __FreeBSD_version, since it was bumped recently.
521 awk has been updated to the latest one-true-awk version 20210215.
522 This contains a number of minor bug fixes.
525 The NFSv4 client now uses the highest minor version of NFSv4
526 supported by the NFSv4 server by default instead of minor version 0,
528 The "minorversion" mount option may be used to override this default.
531 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
532 Most notably netdev.h can change now as the (last) dependencies
533 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
534 additions and others.
537 The directory "blacklisted" under /usr/share/certs/ has been
538 renamed to "untrusted".
541 svnlite has been removed from base. Should you need svn for any reason
542 please install the svn package or port.
545 Commit e1a907a25cfa changed the internal KAPI between the krpc
546 and nfsserver. As such, both modules must be rebuilt from
547 sources. Bump __FreeBSD_version to 1400022.
550 The an(4) driver has been removed from FreeBSD.
553 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
554 start tracking OpenZFS upstream more closely. Please see
555 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
556 for details on how to correct any errors that might result. The
557 short version is that you need to remove the old branch locally:
558 git update-ref -d refs/remotes/freebsd/vendor/openzfs
559 (assuming your upstream origin is named 'freebsd').
562 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
563 which break drm-kmod. In addition various other additions where
564 committed. Bump __FreeBSD_version to 1400015 to be able to
568 Commit ca179c4d74f2 changed the package in which the OpenSSL
569 libraries and utilities are packaged.
570 It is recommended for pkgbase user to do:
571 pkg install -f FreeBSD-openssl
572 before pkg upgrade otherwise some dependencies might not be met
573 and pkg will stop working as libssl will not be present anymore
577 Commit 875977314881 changed the internal KAPI between
578 the nfsd and nfscommon modules. As such these modules
579 need to be rebuilt from sources.
580 Without this patch in your NFSv4.1/4.2 server, enabling
581 delegations by setting vfs.nfsd.issue_delegations non-zero
585 Commit 7763814fc9c2 changed the internal KAPI between
586 the krpc and NFS. As such, the krpc, nfscommon and
587 nfscl modules must all be rebuilt from sources.
588 Without this patch, NFSv4.1/4.2 mounts should not
589 be done with the nfscbd(8) daemon running, to avoid
590 needing a working back channel for server->client RPCs.
593 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
594 handles binding of the back channel as required by RFC5661.
595 Until this patch is in your server, avoid use of the "nconnects"
596 mount option for Linux NFSv4.1/4.2 mounts.
599 For 64-bit architectures the base system is now built with Position
600 Independent Executable (PIE) support enabled by default. It may be
601 disabled using the WITHOUT_PIE knob. A clean build is required.
604 Various LinuxKPI functionality was added which conflicts with DRM.
605 Please update your drm-kmod port to after the __FreeBSD_version 1400003
609 stable/13 branch created.
612 PC Card attachments for all devices have been removed. In the case of
613 wi and cmx, the entire drivers were removed because they were only
614 PC Card devices. FreeBSD_version 1300134 should be used for this
615 since it was bumped so recently.
618 Transport-independent parts of HID support have been split off the USB
619 code in to separate subsystem. Kernel configs which include one of
620 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
621 be updated with adding of "device hid" line.
624 ncurses installation has been modified to only keep the widechar
625 enabled version. Incremental build is broken for that change, so it
626 requires a clean build.
629 The FreeBSD project has migrated from Subversion to Git. Temporary
630 instructions can be found at
631 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
632 and other documents in that repo.
635 The services database has been updated to cover more of the basic
636 services expected in a modern system. The database is big enough
637 that it will cause issues in mergemaster in Releases previous to
638 12.2 and 11.3, or in very old current systems from before r358154.
641 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
642 may be installed from ports or packages.
645 ping6 has been merged into ping. It can now be called as "ping -6".
646 See ping(8) for details.
649 Default value of net.add_addr_allfibs has been changed to 0.
650 If you have multi-fib configuration and rely on existence of all
651 interface routes in every fib, you need to set the above sysctl to 1.
654 The internal pre-processor in the calendar(1) program has been
655 extended to support more C pre-processor commands (e.g. #ifdef, #else,
656 and #undef) and to detect unbalanced conditional statements.
657 Error messages have been extended to include the filename and line
658 number if processing stops to help fixing malformed data files.
661 All the data files for the calendar(1) program, except calendar.freebsd,
662 have been moved to the deskutils/calendar-data port, much like the
663 jewish calendar entries were moved to deskutils/hebcal years ago. After
664 make delete-old-files, you need to install it to retain full
665 functionality. calendar(1) will issue a reminder for files it can't
669 LINT files are no longer generated. We now include the relevant NOTES
670 files. Note: This may cause conflicts with updating in some cases.
671 find sys -name LINT\* -delete
672 is suggested across this commit to remove the generated LINT files.
674 If you have tried to update with generated files there, the svn
675 command you want to un-auger the tree is
678 and then do the above find from the top level. Substitute 'amd64'
679 above with where the error message indicates a conflict.
682 OpenZFS support has been integrated. Do not upgrade root pools until
683 the loader is updated to support zstd. Furthermore, we caution against
684 'zpool upgrade' for the next few weeks. The change should be transparent
685 unless you want to use new features.
687 Not all "NO_CLEAN" build scenarios work across these changes. Many
688 scenarios have been tested and fixed, but rebuilding kernels without
689 rebuilding world may fail.
691 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
692 upstream default. A fallback to /boot has been added for mountroot.
694 Pool auto import behavior at boot has been moved from the kernel module
695 to an explicit "zpool import -a" in one of the rc scripts enabled by
696 zfs_enable=YES. This means your non-root zpools won't auto import until
697 you upgrade your /etc/rc.d files.
700 The resume code now notifies devd with the 'kernel' system
701 rather than the old 'kern' subsystem to be consistent with
702 other use. The old notification will be created as well, but
703 will be removed prior to FreeBSD 14.0.
706 r362275 changed the internal API between the kernel RPC and the
707 NFS modules. As such, all the modules must be recompiled from
711 r364330 modified the internal API used between the NFS modules.
712 As such, all the NFS modules must be re-compiled from sources.
715 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
716 been upgraded to 11.0.0. Please see the 20141231 entry below for
717 information about prerequisites and upgrading, if you are not already
718 using clang 3.5.0 or higher.
721 r364092 modified the internal ABI used between the kernel NFS
722 modules. As such, all of these modules need to be rebuilt
723 from sources, so a version bump was done.
726 Makefile.inc has been updated to work around the issue documented in
727 20200729. It was a case where the optimization of using symbolic links
728 to point to binaries created a situation where we'd run new binaries
729 with old libraries starting midway through the installworld process.
732 r363679 has redefined some undefined behavior in regcomp(3); notably,
733 extraneous escapes of most ordinary characters will no longer be
734 accepted. An exp-run has identified all of the problems with this in
735 ports, but other non-ports software may need extra escapes removed to
736 continue to function.
738 Because of this change, installworld may encounter the following error
739 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
740 you do not halt installworld. Instead, let it run to completion (whether
741 successful or not) and run installworld once more.
744 A new implementation of bc and dc has been imported in r362681. This
745 implementation corrects non-conformant behavior of the previous bc
746 and adds GNU bc compatible options. It offers a number of extensions,
747 is much faster on large values, and has support for message catalogs
748 (a number of languages are already supported, contributions of further
749 languages welcome). The option WITHOUT_GH_BC can be used to build the
750 world with the previous versions of bc and dc.
753 r362639 changed the internal API used between the NFS kernel modules.
754 As such, they all need to be rebuilt from sources.
757 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
758 out of tree file systems need to be modified and rebuilt.
759 Also, any file systems that are modules must be rebuilt.
762 read(2) of a directory fd is now rejected by default. root may
763 re-enable it for system root only on non-ZFS filesystems with the
764 security.bsd.allow_read_dir sysctl(8) MIB if
765 security.bsd.suser_enabled=1.
767 It may be advised to setup aliases for grep to default to `-d skip` if
768 commonly non-recursively grepping a list that includes directories and
769 the potential for the resulting stderr output is not tolerable. Example
770 aliases are now installed, commented out, in /root/.cshrc and
774 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
775 been upgraded to 10.0.1. Please see the 20141231 entry below for
776 information about prerequisites and upgrading, if you are not already
777 using clang 3.5.0 or higher.
780 Support for obsolete compilers has been removed from the build system.
781 Clang 6 and GCC 6.4 are the minimum supported versions.
784 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
785 stub that calls close_range(2). If using a custom kernel configuration,
786 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
787 a slightly older -CURRENT userland and older FreeBSD userlands may not
788 be functional without closefrom(2).
791 Upstream DTS from Linux 5.6 was merged and they now have the SID
792 and THS (Secure ID controller and THermal Sensor) node present.
793 The DTB overlays have now been removed from the tree for the H3/H5 and
794 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
795 deal with upstream DTS. If you are using those overlays you need to
796 remove them from loader.conf and update the DTBs on the FAT partition.
799 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
800 been upgraded to 10.0.0. Please see the 20141231 entry below for
801 information about prerequisites and upgrading, if you are not already
802 using clang 3.5.0 or higher.
805 The amd(8) automount daemon has been removed from the source tree.
806 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
807 amd is still available in the sysutils/am-utils port.
810 Removed brooktree driver (bktr.4) from the tree.
813 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
814 compiler in usr.bin/dtc is used on all architectures which use dtc, and
815 the GPL dtc is available (if needed) from the sysutils/dtc port.
818 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
819 is used by all supported CPU architectures.
822 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
823 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
824 Users who wish to build FreeBSD with GCC must use the external toolchain
828 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
829 has changed, users will have to rebuild all the ports that are linked to
833 The size of struct vnet and the magic cookie have changed.
834 Users need to recompile libkvm and all modules using VIMAGE
835 together with their new kernel.
838 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
839 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
840 your Makefiles and scripts to define MK_<var>=no instead as required.
842 One exception to this is that program or library Makefiles should
843 define MAN to empty rather than setting MK_MAN=no.
846 Clang/LLVM is now the default compiler and LLD the default
850 make universe no longer uses GCC 4.2.1 on any architectures.
851 Architectures not supported by in-tree Clang/LLVM require an
852 external toolchain package.
855 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
856 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
857 options default to off for all supported CPU architectures. As a
858 short-term transition aid they may be enabled via WITH_* options.
859 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
862 Support for armv5 has been disconnected and is being removed. The
863 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
864 You must now use a MACHINE_ARCH of armv6 or armv7. The default
865 MACHINE_ARCH for MACHINE=arm is now armv7.
868 Clang/LLVM is now the default compiler for all powerpc architectures.
869 LLD is now the default linker for powerpc64. The change for powerpc64
870 also includes a change to the ELFv2 ABI, incompatible with the existing
874 Kernel-loadable random(4) modules are no longer unloadable.
877 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
878 been upgraded to 9.0.1. Please see the 20141231 entry below for
879 information about prerequisites and upgrading, if you are not already
880 using clang 3.5.0 or higher.
883 r355677 has modified the internal interface used between the
884 NFS modules in the kernel. As such, they must all be upgraded
885 simultaneously. I will do a version bump for this.
888 The root certificates of the Mozilla CA Certificate Store have been
889 imported into the base system and can be managed with the certctl(8)
890 utility. If you have installed the security/ca_root_nss port or package
891 with the ETCSYMLINK option (the default), be advised that there may be
892 differences between those included in the port and those included in
893 base due to differences in nss branch used as well as general update
894 frequency. Note also that certctl(8) cannot manage certs in the
895 format used by the security/ca_root_nss port.
898 The amd(8) automount daemon has been disabled by default, and will be
899 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
903 The nctgpio and wbwd drivers have been moved to the superio bus.
904 If you have one of these drivers in a kernel configuration, then
905 you should add device superio to it. If you use one of these drivers
906 as a module and you compile a custom set of modules, then you should
907 add superio to the set.
910 KPIs for network drivers to access interface addresses have changed.
911 Users need to recompile NIC driver modules together with kernel.
914 The net.link.tap.user_open sysctl no longer prevents user opening of
915 already created /dev/tapNN devices. Access is still controlled by
916 node permissions, just like tun devices. The net.link.tap.user_open
917 sysctl is now used only to allow users to perform devfs cloning of
918 tap devices, and the subsequent open may not succeed if the user is not
919 in the appropriate group. This sysctl may be deprecated/removed
920 completely in the future.
923 mips, powerpc, and sparc64 are no longer built as part of
924 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
925 not defined, mips, powerpc, and sparc64 builds will look for
926 the xtoolchain binaries and if installed use them for universe
927 builds. As llvm 9.0 becomes vetted for these architectures, they
928 will be removed from the list.
931 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
932 been upgraded to 9.0.0. Please see the 20141231 entry below for
933 information about prerequisites and upgrading, if you are not already
934 using clang 3.5.0 or higher.
937 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
938 GENERIC. They are available as modules and can be loaded by adding
939 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
940 hptnr_load="YES", or hptrr_load="YES", respectively.
943 ntpd no longer by default locks its pages in memory, allowing them
944 to be paged out by the kernel. Use rlimit memlock to restore
945 historic BSD behaviour. For example, add "rlimit memlock 32"
946 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
949 Several of ping6's options have been renamed for better consistency
950 with ping. If you use any of -ARWXaghmrtwx, you must update your
951 scripts. See ping6(8) for details.
954 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
955 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
956 been removed from mount_fusefs(8). You can safely remove them from
957 your scripts, because they had no effect.
959 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
960 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
961 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
962 sysctls have been removed. If you felt the need to set any of them to
963 a non-default value, please tell asomers@FreeBSD.org why.
966 Default permissions on the /var/account/acct file (and copies of it
967 rotated by periodic daily scripts) are changed from 0644 to 0640
968 because the file contains sensitive information that should not be
969 world-readable. If the /var/account directory must be created by
970 rc.d/accounting, the mode used is now 0750. Admins who use the
971 accounting feature are encouraged to change the mode of an existing
972 /var/account directory to 0750 or 0700.
975 Entropy collection and the /dev/random device are no longer optional
976 components. The "device random" option has been removed.
977 Implementations of distilling algorithms can still be made loadable
978 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
981 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
982 been upgraded to 8.0.1. Please see the 20141231 entry below for
983 information about prerequisites and upgrading, if you are not already
984 using clang 3.5.0 or higher.
987 A fix was applied to i386 kernel modules to avoid panics with
988 dpcpu or vnet. Users need to recompile i386 kernel modules
989 having pcpu or vnet sections or they will refuse to load.
992 User-wired pages now have their own counter,
993 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
994 to vm.max_user_wired and changed from an unsigned int to an unsigned
995 long. bhyve VMs wired with the -S are now subject to the user
996 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
997 avoid running into the limit.
1000 The IPSEC option has been removed from GENERIC. Users requiring
1001 ipsec(4) must now load the ipsec(4) kernel module.
1004 The tap(4) driver has been folded into tun(4), and the module has been
1005 renamed to tuntap. You should update any kld_list="if_tap" or
1006 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
1007 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
1008 module instead, and "device tap" or "device tun" entries in kernel
1009 config files to select the tuntap device instead.
1012 The following knobs have been added related to tradeoffs between
1013 safe use of the random device and availability in the absence of
1016 kern.random.initial_seeding.bypass_before_seeding: tunable; set
1017 non-zero to bypass the random device prior to seeding, or zero to
1018 block random requests until the random device is initially seeded.
1019 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
1020 availability properties.
1022 kern.random.initial_seeding.read_random_bypassed_before_seeding:
1023 read-only diagnostic sysctl that is set when bypass is enabled and
1024 read_random(9) is bypassed, to enable programmatic handling of this
1025 initial condition, if desired.
1027 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
1028 Similar to the above, but for arc4random(9) initial seeding.
1030 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
1031 non-zero to disable warnings in dmesg when the same conditions are
1032 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
1033 produce warnings in dmesg when the conditions are met.
1036 The loadable random module KPI has changed; the random_infra_init()
1037 routine now requires a 3rd function pointer for a bool (*)(void)
1038 method that returns true if the random device is seeded (and
1039 therefore unblocked).
1042 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
1043 built from head sources between r320757 (July 6, 2017) and
1044 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
1045 is added to the command line.
1046 nfsuserd daemons built from head sources that are post-r338192 are
1047 not affected and should continue to work.
1050 The fuse(4) module has been renamed to fusefs(4) for consistency with
1051 other filesystems. You should update any kld_load="fuse" entries in
1052 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
1053 "options FUSE" entries in kernel config files.
1056 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1057 8.0.0. Please see the 20141231 entry below for information about
1058 prerequisites and upgrading, if you are not already using clang 3.5.0
1062 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
1063 compiled into your custom kernel, add 'device xz' statement to the
1067 drm and drm2 have been removed from the tree. Please see
1068 https://wiki.freebsd.org/Graphics for the latest information on
1069 migrating to the drm ports.
1072 Iflib is no longer unconditionally compiled into the kernel. Drivers
1073 using iflib and statically compiled into the kernel, now require
1074 the 'device iflib' config option. For the same drivers loaded as
1075 modules on kernels not having 'device iflib', the iflib.ko module
1076 is loaded automatically.
1079 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
1080 options no longer exist since r343219 and r343427 respectively;
1081 nothing uses them, so they should be just removed from custom
1082 kernel config files.
1085 r342635 changes the way efibootmgr(8) works by requiring users to add
1086 the -b (bootnum) parameter for commands where the bootnum was previously
1087 specified with each option. For example 'efibootmgr -B 0001' is now
1088 'efibootmgr -B -b 0001'.
1091 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
1092 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
1093 servers that have vfs.nfsd.nfs_privport set will only allow mounts
1094 from clients using a reserved port. Since both the FreeBSD and Linux
1095 NFSv4 clients use reserved ports by default, this should not affect
1099 The XLP config has been removed. We can't support 64-bit atomics in this
1100 kernel because it is running in 32-bit mode. XLP users must transition
1101 to running a 64-bit kernel (XLP64 or XLPN32).
1103 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
1104 the preferred emulator today and we don't need two different ones.
1106 The old sibyte / swarm / Broadcom BCM1250 support has been
1107 removed from the mips port.
1110 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1111 7.0.1. Please see the 20141231 entry below for information about
1112 prerequisites and upgrading, if you are not already using clang 3.5.0
1116 Remove the timed and netdate programs from the base tree. Setting
1117 the time with these daemons has been obsolete for over a decade.
1120 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
1121 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
1122 it produces broken binaries when ifuncs are in use. Users needing
1123 GNU ld should install the binutils port or package.
1126 The BSD crtbegin and crtend code has been enabled by default. It has
1127 had extensive testing on amd64, arm64, and i386. It can be disabled
1128 by building a world with -DWITHOUT_BSD_CRTBEGIN.
1131 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
1132 has been converted to a port (misc/ctm) and will be removed from
1133 FreeBSD-13. It is available as a package (ctm) for all supported
1137 The default newsyslog.conf(5) file has been changed to only include
1138 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
1139 the filenames end in '.conf' and do not begin with a '.'.
1141 You should check the configuration files in these two directories match
1142 this naming convention. You can verify which configuration files are
1143 being included using the command:
1147 Stable/12 was branched created.
1150 Ports for the DRM modules have been simplified. Now, amd64 users should
1151 just install the drm-kmod port. All others should install
1154 Graphics hardware that's newer than about 2010 usually works with
1155 drm-kmod. For hardware older than 2013, however, some users will need
1156 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
1157 than 2008 usually only works in drm-legacy-kmod. The graphics team can
1158 only commit to hardware made since 2013 due to the complexity of the
1159 market and difficulty to test all the older cards effectively. If you
1160 have hardware supported by drm-kmod, you are strongly encouraged to use
1161 that as you will get better support.
1163 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
1164 elsewhere, the drm and drm2 modules will be eliminated from the src base
1165 soon (with a limited exception for arm). Please update to the package
1166 asap and report any issues to x11@freebsd.org.
1168 Generally, anybody using the drm*-kmod packages should add
1169 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
1170 cross-threading surprises, especially with automatic driver
1171 loading from X11 startup. These will become the defaults in 13-current
1175 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
1176 custom kernel and module loading configuration files must be updated
1177 accordingly. Moreover, interfaces previous presented as ixlvN to the
1178 system are now exposed as iavfN and network configuration files must
1179 be adjusted as necessary.
1182 OpenSSL has been updated to version 1.1.1. This update included
1183 additional various API changes throughout the base system. It is
1184 important to rebuild third-party software after upgrading. The value
1185 of __FreeBSD_version has been bumped accordingly.
1188 The legacy DRM modules and drivers have now been added to the loader's
1189 module blacklist, in favor of loading them with kld_list in rc.conf(5).
1190 The module blacklist may be overridden with the loader.conf(5)
1191 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
1195 The cam(4) based nda(4) driver will be used over nvd(4) by default on
1196 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
1197 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
1198 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
1202 Reproducible build mode is now on by default, in preparation for
1203 FreeBSD 12.0. This eliminates build metadata such as the user,
1204 host, and time from the kernel (and uname), unless the working tree
1205 corresponds to a modified checkout from a version control system.
1206 The previous behavior can be obtained by setting the /etc/src.conf
1207 knob WITHOUT_REPRODUCIBLE_BUILD.
1210 The Yarrow CSPRNG has been removed from the kernel as it has not been
1211 supported by its designers since at least 2003. Fortuna has been the
1212 default since FreeBSD-11.
1215 devctl freeze/thaw have gone into the tree, the rc scripts have been
1216 updated to use them and devmatch has been changed. You should update
1217 kernel, userland and rc scripts all at the same time.
1220 The default interpreter has been switched from 4th to Lua.
1221 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1222 interpreter. If you have custom FORTH code you will need to set
1223 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1224 src.conf for the build. This will create default hard links between
1225 loader and loader_4th instead of loader and loader_lua, the new default.
1226 If you are using UEFI it will create the proper hard link to loader.efi.
1228 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1229 regarding coexisting with multiple versions of FreeBSD are resolved.
1232 ls(1) now respects the COLORTERM environment variable used in other
1233 systems and software to indicate that a colored terminal is both
1234 supported and desired. If ls(1) is suddenly emitting colors, they may
1235 be disabled again by either removing the unwanted COLORTERM from your
1236 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1237 may not be observed in a future release.
1240 The default pager for most commands has been changed to "less". To
1241 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1245 The jedec_ts(4) driver has been removed. A superset of its functionality
1246 is available in the jedec_dimm(4) driver, and the manpage for that
1247 driver includes migration instructions. If you have "device jedec_ts"
1248 in your kernel configuration file, it must be removed.
1251 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1252 This should have no effect if the kernel is booted via BIOS/legacy boot.
1253 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1254 has a buggy firmware that prevents a successful boot due to use of
1258 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1259 support has been removed from the tree. These ports were
1260 obsolete and/or known to be broken for many years.
1263 loader.efi has been augmented to participate more fully in the
1264 UEFI boot manager protocol. loader.efi will now look at the
1265 BootXXXX environment variable to determine if a specific kernel
1266 or root partition was specified. XXXX is derived from BootCurrent.
1267 efibootmgr(8) manages these standard UEFI variables.
1270 zfsloader's functionality has now been folded into loader.
1271 zfsloader is no longer necessary once you've updated your
1272 boot blocks. For a transition period, we will install a
1273 hardlink for zfsloader to loader to allow a smooth transition
1274 until the boot blocks can be updated (hard link because old
1275 zfs boot blocks don't understand symlinks).
1278 ARM64 now have efifb support, if you want to have serial console
1279 on your arm64 board when an screen is connected and the bootloader
1280 setup a frame buffer for us to use, just add :
1283 in /boot/loader.conf
1284 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1285 an screen connected as the firmware will setup a frame buffer are that
1286 u-boot will expose as an EFI frame buffer.
1289 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1290 or take steps to update /etc/passwd before doing installworld on
1291 existing systems. Do not skip the "mergemaster -Fp" step before
1292 installworld, as described in the update procedures near the bottom
1293 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1294 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1295 the ntp config file contain options that change file/dir locations.
1296 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1297 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1298 taking steps to ensure that all required files/dirs are accessible
1302 Big endian arm support has been removed.
1305 The static environment setup in kernel configs is no longer mutually
1306 exclusive with the loader(8) environment by default. In order to
1307 restore the previous default behavior of disabling the loader(8)
1308 environment if a static environment is present, you must specify
1309 loader_env.disabled=1 in the static environment.
1312 The ABI of syscalls used by management tools like sockstat and
1313 netstat has been broken to allow 32-bit binaries to work on
1314 64-bit kernels without modification. These programs will need
1315 to match the kernel in order to function. External programs may
1316 require minor modifications to accommodate a change of type in
1317 structures from pointers to 64-bit virtual addresses.
1320 On i386 and amd64 atomics are now inlined. Out of tree modules using
1321 atomics will need to be rebuilt.
1324 The '%I' format in the kern.corefile sysctl limits the number of
1325 core files that a process can generate to the number stored in the
1326 debug.ncores sysctl. The '%I' format is replaced by the single digit
1327 index. Previously, if all indexes were taken the kernel would overwrite
1328 only a core file with the highest index in a filename.
1329 Currently the system will create a new core file if there is a free
1330 index or if all slots are taken it will overwrite the oldest one.
1333 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1334 6.0.1. Please see the 20141231 entry below for information about
1335 prerequisites and upgrading, if you are not already using clang 3.5.0
1339 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1340 needed to be changed to work with it. This change was made with r335763
1341 and requires a mergemaster / etcupdate / etc to update the installed
1345 r334930 changed the interface between the NFS modules, so they all
1346 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1349 As of r334391 lld is the default amd64 system linker; it is installed
1350 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1354 The kernel / userland interface for devinfo changed, so you'll
1355 need a new kernel and userland as a pair for it to work (rebuilding
1356 lib/libdevinfo is all that's required). devinfo and devmatch will
1357 not work, but everything else will when there's a mismatch.
1360 The on-disk format for hwpmc callchain records has changed to include
1361 threadid corresponding to a given record. This changes the field offsets
1362 and thus requires that libpmcstat be rebuilt before using a kernel
1366 The vxge(4) driver has been removed. This driver was introduced into
1367 HEAD one week before the Exar left the Ethernet market and is not
1368 known to be used. If you have device vxge in your kernel config file
1372 The amd64 kernel now requires a ld that supports ifunc to produce a
1373 working kernel, either lld or a newer binutils. lld is built by default
1374 on amd64, and the 'buildkernel' target uses it automatically. However,
1375 it is not the default linker, so building the kernel the traditional
1376 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1377 binutils port/package). lld will soon be default, and this requirement
1380 NOTE: As of r334391 lld is the default system linker on amd64, and no
1381 workaround is necessary.
1384 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1385 cards made by s2io/Neterion. The company was acquired by Exar and
1386 no longer sells or supports Ethernet products. If you have device
1387 nxge in your kernel config file it must be removed.
1390 The tz database (tzdb) has been updated to 2018e. This version more
1391 correctly models time stamps in time zones with negative DST such as
1392 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1393 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1394 time zone abbreviations and the tm_isdst flag.
1397 The ixgb(4) driver has been removed. This driver was for an early and
1398 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1399 quickly shifted to the long lived ixgbe family. If you have device
1400 ixgb in your kernel config file it must be removed.
1403 The lmc(4) driver has been removed. This was a WAN interface
1404 card that was already reportedly rare in 2003, and had an ambiguous
1405 license. If you have device lmc in your kernel config file it must
1409 Support for Arcnet networks has been removed. If you have device
1410 arcnet or device cm in your kernel config file they must be
1414 Support for FDDI networks has been removed. If you have device
1415 fddi or device fpa in your kernel config file they must be
1419 In addition to supporting RFC 3164 formatted messages, the
1420 syslogd(8) service is now capable of parsing RFC 5424 formatted
1421 log messages. The main benefit of using RFC 5424 is that clients
1422 may now send log messages with timestamps containing year numbers,
1423 microseconds and time zone offsets.
1425 Similarly, the syslog(3) C library function has been altered to
1426 send RFC 5424 formatted messages to the local system logging
1427 daemon. On systems using syslogd(8), this change should have no
1428 negative impact, as long as syslogd(8) and the C library are
1429 updated at the same time. On systems using a different system
1430 logging daemon, it may be necessary to make configuration
1431 adjustments, depending on the software used.
1433 When using syslog-ng, add the 'syslog-protocol' flag to local
1434 input sources to enable parsing of RFC 5424 formatted messages:
1437 unix-dgram("/var/run/log" flags(syslog-protocol));
1440 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1441 of the 'imuxsock' module to let messages be processed by the
1442 regular RFC 3164/5424 parsing pipeline:
1444 module(load="imuxsock" SysSock.UseSpecialParser="off")
1446 Do note that these changes only affect communication between local
1447 applications and syslogd(8). The format that syslogd(8) uses to
1448 store messages on disk or forward messages to other systems
1449 remains unchanged. syslogd(8) still uses RFC 3164 for these
1450 purposes. Options to customize this behaviour will be added in the
1451 future. Utilities that process log files stored in /var/log are
1452 thus expected to continue to function as before.
1454 __FreeBSD_version has been incremented to 1200061 to denote this
1458 Support for token ring networks has been removed. If you
1459 have "device token" in your kernel config you should remove
1460 it. No device drivers supported token ring.
1463 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1464 entries as EFI instead of overloading the i386 tag as done previously.
1465 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1466 release was updated to use this. This may mean that makefs must be
1467 updated before "make cdrom" can be run in the release directory. This
1468 should be as simple as:
1470 $ cd $SRCDIR/usr.sbin/makefs
1471 $ make depend all install
1474 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1475 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1476 Co-existence for the transition period will come shortly. Booting is a
1477 complex environment and test coverage for Lua-enabled loaders has been
1478 thin, so it would be prudent to assume it might not work and make
1479 provisions for backup boot methods.
1482 devmatch functionality has been turned on in devd. It will automatically
1483 load drivers for unattached devices. This may cause unexpected drivers
1484 to be loaded. Please report any problems to current@ and
1488 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1489 6.0.0. Please see the 20141231 entry below for information about
1490 prerequisites and upgrading, if you are not already using clang 3.5.0
1494 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1495 This means it is used to link the kernel and userland libraries and
1496 executables, but is not yet installed as /usr/bin/ld by default.
1498 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1499 WITHOUT_LLD_BOOTSTRAP=yes
1502 On i386, pmtimer has been removed. Its functionality has been folded
1503 into apm. It was a no-op on ACPI in current for a while now (but was
1504 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1505 remove it from kernel config files.
1508 The use of RSS hash from the network card aka flowid has been
1509 disabled by default for lagg(4) as it's currently incompatible with
1510 the lacp and loadbalance protocols.
1512 This can be re-enabled by setting the following in loader.conf:
1513 net.link.lagg.default_use_flowid="1"
1516 The SW_WATCHDOG option is no longer necessary to enable the
1517 hardclock-based software watchdog if no hardware watchdog is
1518 configured. As before, SW_WATCHDOG will cause the software
1519 watchdog to be enabled even if a hardware watchdog is configured.
1522 r326887 fixes the issue described in the 20171214 UPDATING entry.
1523 r326888 flips the switch back to building GELI support always.
1526 r362593 broke ZFS + GELI support for reasons unknown. However,
1527 it also broke ZFS support generally, so GELI has been turned off
1528 by default as the lesser evil in r326857. If you boot off ZFS and/or
1529 GELI, it might not be a good time to update.
1532 PowerPC users must update loader(8) by rebuilding world before
1533 installing a new kernel, as the protocol connecting them has
1534 changed. Without the update, loader metadata will not be passed
1535 successfully to the kernel and users will have to enter their
1536 root partition at the kernel mountroot prompt to continue booting.
1537 Newer versions of loader can boot old kernels without issue.
1540 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1541 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1542 to WITH/OUT_LOADER_GELI.
1545 The naive and non-compliant support of posix_fallocate(2) in ZFS
1546 has been removed as of r325320. The system call now returns EINVAL
1547 when used on a ZFS file. Although the new behavior complies with the
1548 standard, some consumers are not prepared to cope with it.
1549 One known victim is lld prior to r325420.
1552 Building in a FreeBSD src checkout will automatically create object
1553 directories now rather than store files in the current directory if
1554 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1555 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1556 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1560 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1561 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1562 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1563 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1564 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1565 The UNIFIED_OBJDIR option is a transitional feature that will be
1566 removed for 12.0 release; please migrate to the new format for any
1567 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1568 than hardcoding paths.
1571 The native-xtools target no longer installs the files by default to the
1572 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1573 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1576 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1577 options are changing from controlling the build if defined / undefined
1578 to controlling the build with explicit 'yes' or 'no' values. They will
1579 shift to WITH/WITHOUT options to match other options in the system.
1582 libstand has turned into a private library for sys/boot use only.
1583 It is no longer supported as a public interface outside of sys/boot.
1586 The arm port has split armv6 into armv6 and armv7. armv7 is now
1587 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1588 and are running a kernel from before r324363, you will need to add
1589 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1592 When building multiple kernels using KERNCONF, non-existent KERNCONF
1593 files will produce an error and buildkernel will fail. Previously
1594 missing KERNCONF files silently failed giving no indication as to
1595 why, only to subsequently discover during installkernel that the
1596 desired kernel was never built in the first place.
1599 The default serial number format for CTL LUNs has changed. This will
1600 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1601 or iSCSI clients care about their LUNs' serial numbers. Users who
1602 require serial number stability should hardcode serial numbers in
1606 For 32-bit arm compiled for hard-float support, soft-floating point
1607 binaries now always get their shared libraries from
1608 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1609 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1610 soft-float everything else should be affected.
1613 The geli password typed at boot is now hidden. To restore the previous
1614 behavior, see geli(8) for configuration options.
1617 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1618 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1622 "make check" behavior (made in ^/head@r295380) has been changed to
1623 execute from a limited sandbox, as opposed to executing from
1627 - The "beforecheck" and "aftercheck" targets are now specified.
1628 - ${CHECKDIR} (added in commit noted above) has been removed.
1629 - Legacy behavior can be enabled by setting
1630 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1632 If the limited sandbox mode is enabled, "make check" will execute
1633 "make distribution", then install, execute the tests, and clean up the
1634 sandbox if successful.
1636 The "make distribution" and "make install" targets are typically run as
1637 root to set appropriate permissions and ownership at installation time.
1638 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1639 environment if executing "make check" with limited sandbox mode using
1640 an unprivileged user.
1643 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1644 unable to automatically find alternate superblocks. As of r322297,
1645 the information needed to find alternate superblocks has been
1646 moved to the end of the area reserved for the boot block.
1647 Filesystems created with a newfs of this vintage or later
1648 will create the recovery information. If you have a filesystem
1649 created prior to this change and wish to have a recovery block
1650 created for your filesystem, you can do so by running fsck in
1651 foreground mode (i.e., do not use the -p or -y options). As it
1652 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1653 to which you should answer yes.
1656 As of r321665, an NFSv4 server configuration that services
1657 Kerberos mounts or clients that do not support the uid/gid in
1658 owner/owner_group string capability, must explicitly enable
1659 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1660 machine's /etc/rc.conf file.
1663 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1664 Please see the 20141231 entry below for information about prerequisites
1665 and upgrading, if you are not already using clang 3.5.0 or higher.
1668 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1669 r-commands (rlogin, rsh, etc.) to be built with the base system.
1672 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1673 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1674 be careful when performing source upgrades. It is best to run
1675 'make installworld' from an alternate root system, either a live
1676 CD/memory stick, or a temporary root partition. Additionally, all ports
1677 must be recompiled. powerpc64 is largely unaffected, except in the case
1678 of 32-bit compatibility. All 32-bit binaries will be affected.
1681 Forward compatibility for the "ino64" project have been committed. This
1682 will allow most new binaries to run on older kernels in a limited
1683 fashion. This prevents many of the common foot-shooting actions in the
1684 upgrade as well as the limited ability to roll back the kernel across
1685 the ino64 upgrade. Complicated use cases may not work properly, though
1686 enough simpler ones work to allow recovery in most situations.
1689 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1690 if you require the GPL compiler.
1693 Forward compatibility for the "ino64" project have been committed. This
1694 will allow most new binaries to run on older kernels in a limited
1695 fashion. This prevents many of the common foot-shooting actions in the
1696 upgrade as well as the limited ability to roll back the kernel across
1697 the ino64 upgrade. Complicated use cases may not work properly, though
1698 enough simpler ones work to allow recovery in most situations.
1701 The internal ABI used for communication between the NFS kernel modules
1702 was changed by r320085, so __FreeBSD_version was bumped to
1703 ensure all the NFS related modules are updated together.
1706 The ABI of struct event was changed by extending the data
1707 member to 64bit and adding ext fields. For upgrade, same
1708 precautions as for the entry 20170523 "ino64" must be
1712 The GNU roff toolchain has been removed from base. To render manpages
1713 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1714 from ports (and recommends to install it).
1715 To render roff(7) documents, consider using GNU roff from ports or the
1716 heirloom doctools roff toolchain from ports via pkg install groff or
1717 via pkg install heirloom-doctools.
1720 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1721 smaller runtime footprint builds. This is useful for embedded systems
1722 which only require one chipset support.
1724 If you load it as a module, make sure this is in /boot/loader.conf:
1728 This will load the HAL, all chip/RF backends and if_ath_pci.
1729 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1730 if_ath or it will not load any HAL chipset support.
1732 If you want to selectively load things (eg on cheaper ARM/MIPS
1733 platforms where RAM is at a premium) you should:
1736 * load the chip modules in question
1737 * load ath_rate, ath_dfs
1739 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1740 bus bind type - this is where probe/attach is done.
1742 For further comments/feedback, poke adrian@ .
1745 The "ino64" 64-bit inode project has been committed, which extends
1746 a number of types to 64 bits. Upgrading in place requires care and
1747 adherence to the documented upgrade procedure.
1749 If using a custom kernel configuration ensure that the
1750 COMPAT_FREEBSD11 option is included (as during the upgrade the
1751 system will be running the ino64 kernel with the existing world).
1753 For the safest in-place upgrade begin by removing previous build
1754 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1755 procedure documented below under the heading "To rebuild everything and
1756 install it on the current system." Specifically, a reboot is required
1757 after installing the new kernel before installing world. While an
1758 installworld normally works by accident from multiuser after rebooting
1759 the proper kernel, there are many cases where this will fail across this
1760 upgrade and installworld from single user is required.
1763 The NATM framework including the en(4), fatm(4), hatm(4), and
1764 patm(4) devices has been removed. Consumers should plan a
1765 migration before the end-of-life date for FreeBSD 11.
1768 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1769 diff has not been implemented, if those are needed a newer version of
1770 GNU diff is available via the diffutils package under the gdiff name.
1773 As of r316810 for ipfilter, keep frags is no longer assumed when
1774 keep state is specified in a rule. r316810 aligns ipfilter with
1775 documentation in man pages separating keep frags from keep state.
1776 This allows keep state to be specified without forcing keep frags
1777 and allows keep frags to be specified independently of keep state.
1778 To maintain previous behaviour, also specify keep frags with
1779 keep state (as documented in ipf.conf.5).
1782 arm64 builds now use the base system LLD 4.0.0 linker by default,
1783 instead of requiring that the aarch64-binutils port or package be
1784 installed. To continue using aarch64-binutils, set
1785 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1788 The UDP optimization in entry 20160818 that added the sysctl
1789 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1790 packets will no longer be treated as L3 broadcast packets.
1793 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1794 use any explicitly assigned loopback address available in the jail
1795 instead of using the first assigned address of the jail.
1798 The ctl.ko module no longer implements the iSCSI target frontend:
1799 cfiscsi.ko does instead.
1801 If building cfiscsi.ko as a kernel module, the module can be loaded
1802 via one of the following methods:
1803 - `cfiscsi_load="YES"` in loader.conf(5).
1804 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1805 - ctladm(8)/ctld(8), when compiled with iSCSI support
1806 (`WITH_ISCSI=yes` in src.conf(5))
1808 Please see cfiscsi(4) for more details.
1811 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1812 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1813 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1814 missing, but mmcsd.ko now will refuse to load if it is incompatible
1818 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1819 If you have used named states in the firewall rules, you need to modify
1820 them after installworld and before rebooting. Now named states must
1821 be prefixed with colon.
1824 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1825 removed as the userland we provide cannot use them. The KMS version
1826 (sys/dev/drm2) supports the same hardware.
1829 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1830 Please see the 20141231 entry below for information about prerequisites
1831 and upgrading, if you are not already using clang 3.5.0 or higher.
1834 The code that provides support for ZFS .zfs/ directory functionality
1835 has been reimplemented. It's not possible now to create a snapshot
1836 by mkdir under .zfs/snapshot/. That should be the only user visible
1840 EISA bus support has been removed. The WITH_EISA option is no longer
1844 MCA bus support has been removed.
1847 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1848 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1851 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1852 the em(4) driver conforms to iflib specifications.
1855 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1856 IFLIB. If you have a custom kernel configuration that excludes em(4)
1857 but you use igb(4), you need to re-add em(4) to your custom
1861 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1862 Please see the 20141231 entry below for information about prerequisites
1863 and upgrading, if you are not already using clang 3.5.0 or higher.
1866 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1867 Please see the 20141231 entry below for information about prerequisites
1868 and upgrading, if you are not already using clang 3.5.0 or higher.
1871 The layout of the pmap structure has changed for powerpc to put the pmap
1872 statistics at the front for all CPU variations. libkvm(3) and all tools
1873 that link against it need to be recompiled.
1876 isl(4) and cyapa(4) drivers now require a new driver,
1877 chromebook_platform(4), to work properly on Chromebook-class hardware.
1878 On other types of hardware the drivers may need to be configured using
1879 device hints. Please see the corresponding manual pages for details.
1882 The urtwn(4) driver was merged into rtwn(4) and now consists of
1883 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1885 Also, firmware for RTL8188CE was renamed due to possible name
1886 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1889 GNU rcs has been removed from base. It is available as packages:
1890 - rcs: Latest GPLv3 GNU rcs version.
1891 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1895 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1896 modules now requires that the kernel configuration contain the
1897 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1900 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1901 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1904 Relocatable object files with the extension of .So have been renamed
1905 to use an extension of .pico instead. The purpose of this change is
1906 to avoid a name clash with shared libraries on case-insensitive file
1907 systems. On those file systems, foo.So is the same file as foo.so.
1910 GNU rcs has been turned off by default. It can (temporarily) be built
1911 again by adding WITH_RCS knob in src.conf.
1912 Otherwise, GNU rcs is available from packages:
1913 - rcs: Latest GPLv3 GNU rcs version.
1914 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1917 The backup_uses_rcs functionality has been removed from rc.subr.
1920 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1921 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1922 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1923 QUEUE_MACRO_DEBUG behavior.
1926 r304787 changed some ioctl interfaces between the iSCSI userspace
1927 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1928 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1932 The UDP receive code has been updated to only treat incoming UDP
1933 packets that were addressed to an L2 broadcast address as L3
1934 broadcast packets. It is not expected that this will affect any
1935 standards-conforming UDP application. The new behaviour can be
1936 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1940 Remove the openbsd_poll system call.
1941 __FreeBSD_version has been bumped because of this.
1944 The stable/11 branch has been created from head@r302406.
1946 After branch N is created, entries older than the N-2 branch point are removed
1947 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1948 entries older than stable/12 branch point will be removed from current's
1955 Sometimes, obscure build problems are the result of environment
1956 poisoning. This can happen because the make utility reads its
1957 environment when searching for values for global variables. To run
1958 your build attempts in an "environmental clean room", prefix all make
1959 commands with 'env -i '. See the env(1) manual page for more details.
1960 Occasionally a build failure will occur with "make -j" due to a race
1961 condition. If this happens try building again without -j, and please
1962 report a bug if it happens consistently.
1964 When upgrading from one major version to another it is generally best to
1965 upgrade to the latest code in the currently installed branch first, then
1966 do an upgrade to the new branch. This is the best-tested upgrade path,
1967 and has the highest probability of being successful. Please try this
1968 approach if you encounter problems with a major version upgrade. Since
1969 the stable 4.x branch point, one has generally been able to upgrade from
1970 anywhere in the most recent stable branch to head / current (or even the
1971 last couple of stable branches). See the top of this file when there's
1974 The update process will emit an error on an attempt to perform a build
1975 or install from a FreeBSD version below the earliest supported version.
1976 When updating from an older version the update should be performed one
1977 major release at a time, including running `make delete-old` at each
1980 When upgrading a live system, having a root shell around before
1981 installing anything can help undo problems. Not having a root shell
1982 around can lead to problems if pam has changed too much from your
1983 starting point to allow continued authentication after the upgrade.
1985 This file should be read as a log of events. When a later event changes
1986 information of a prior event, the prior event should not be deleted.
1987 Instead, a pointer to the entry with the new information should be
1988 placed in the old entry. Readers of this file should also sanity check
1989 older entries before relying on them blindly. Authors of new entries
1990 should write them with this in mind.
1994 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1995 always follow these three steps:
1997 1) recompile and reinstall the ZFS boot loader and boot block
1998 (this is part of "make buildworld" and "make installworld")
2000 2) update the ZFS boot block on your boot drive (only required when
2001 doing a zpool upgrade):
2003 When booting on x86 via BIOS, use the following to update the ZFS boot
2004 block on the freebsd-boot partition of a GPT partitioned drive ada0:
2005 gpart bootcode -p /boot/gptzfsboot -i $N ada0
2006 The value $N will typically be 1. For EFI booting, see EFI notes.
2008 3) zpool upgrade the root pool. New bootblocks will work with old
2009 pools, but not vice versa, so they need to be updated before any
2012 Non-boot pools do not need these updates.
2017 There are two locations the boot loader can be installed into. The
2018 current location (and the default) is \efi\freebsd\loader.efi and using
2019 efibootmgr(8) to configure it. The old location, that must be used on
2020 deficient systems that don't honor efibootmgr(8) protocols, is the
2021 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
2022 /boot/loader.efi to this location, but on systems installed a long time
2023 ago the ESP may be too small and /boot/boot1.efi may be needed unless
2024 the ESP has been expanded in the meantime.
2026 Recent systems will have the ESP mounted on /boot/efi, but older ones
2027 may not have it mounted at all, or mounted in a different
2028 location. Older arm SD images with MBR used /boot/msdos as the
2029 mountpoint. The ESP is a MSDOS filesystem.
2031 The EFI boot loader rarely needs to be updated. For ZFS booting,
2032 however, you must update loader.efi before you do 'zpool upgrade' the
2033 root zpool, otherwise the old loader.efi may reject the upgraded zpool
2034 since it does not automatically understand some new features.
2036 See loader.efi(8) and uefi(8) for more details.
2040 If you are updating from a prior version of FreeBSD (even one just
2041 a few days old), you should follow this procedure. It is the most
2042 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2044 make kernel-toolchain
2045 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2046 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2048 If you are running kernel modules from ports, see FOOTNOTE [1].
2050 To test a kernel once
2051 ---------------------
2052 If you just want to boot a kernel once (because you are not sure
2053 if it works, or if you want to boot a known bad kernel to provide
2054 debugging information) run
2055 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2056 nextboot -k testkernel
2058 To rebuild everything and install it on the current system.
2059 -----------------------------------------------------------
2060 # Note: sometimes if you are running current you gotta do more than
2061 # is listed here if you are upgrading from a really old current.
2063 <make sure you have good level 0 dumps>
2065 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2066 make installkernel KERNCONF=YOUR_KERNEL_HERE [1]
2067 <reboot in single user> [3]
2074 To cross-install current onto a separate partition
2075 --------------------------------------------------
2076 # In this approach we use a separate partition to hold
2077 # current's root, 'usr', and 'var' directories. A partition
2078 # holding "/", "/usr" and "/var" should be about 2GB in
2081 <make sure you have good level 0 dumps>
2084 make buildkernel KERNCONF=YOUR_KERNEL_HERE [1]
2085 <maybe newfs current's root partition>
2086 <mount current's root partition on directory ${CURRENT_ROOT}>
2087 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2088 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2089 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2090 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2091 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2092 <reboot into current>
2093 <do a "native" rebuild/install as described in the previous section>
2094 <maybe install compatibility libraries from ports/misc/compat*>
2098 To upgrade in-place from stable to current
2099 ----------------------------------------------
2100 <make sure you have good level 0 dumps>
2102 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2103 make installkernel KERNCONF=YOUR_KERNEL_HERE [1]
2104 <reboot in single user> [3]
2111 Make sure that you've read the UPDATING file to understand the
2112 tweaks to various things you need. At this point in the life
2113 cycle of current, things change often and you are on your own
2114 to cope. The defaults can also change, so please read ALL of
2115 the UPDATING entries.
2117 Also, if you are tracking -current, you must be subscribed to
2118 freebsd-current@freebsd.org. Make sure that before you update
2119 your sources that you have read and understood all the recent
2120 messages there. If in doubt, please track -stable which has
2121 much fewer pitfalls.
2125 [1] If you have third party modules, such as drm-kmod or vmware, you
2126 should disable them at this point so they don't crash your system on
2127 reboot. Alternatively, you should rebuild all the modules you have in
2128 your system and install them as well. If you are running -current, you
2129 should seriously consider placing all sources to all the modules for
2130 your system (or symlinks to them) in /usr/local/sys/modules so this
2131 happens automatically. If all your modules come from ports, then adding
2132 the port origin directories to PORTS_MODULES instead is also automatic
2134 PORTS_MODULES+=x11/nvidia-driver
2136 [3] From the bootblocks, boot -s, and then do
2140 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2141 cd src # full path to source
2142 adjkerntz -i # if CMOS is wall time
2143 Also, when doing a major release upgrade, it is required that you boot
2144 into single user mode to do the installworld.
2146 [4] Note: This step is non-optional. Failure to do this step
2147 can result in a significant reduction in the functionality of the
2148 system. Attempting to do it by hand is not recommended and those
2149 that pursue this avenue should read this file carefully, as well
2150 as the archives of freebsd-current and freebsd-hackers mailing lists
2151 for potential gotchas. See etcupdate(8) for more information.
2153 [5] Usually this step is a no-op. However, from time to time
2154 you may need to do this if you get unknown user in the following
2157 [6] This only deletes old files and directories. Old libraries
2158 can be deleted by "make delete-old-libs", but you have to make
2159 sure that no program is using those libraries anymore.
2161 [8] The new kernel must be able to run existing binaries used by an
2162 installworld. When upgrading across major versions, the new kernel's
2163 configuration must include the correct COMPAT_FREEBSD<n> option for
2164 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2165 to do so may leave you with a system that is hard to boot to recover. A
2166 GENERIC kernel will include suitable compatibility options to run
2167 binaries from older branches. Note that the ability to run binaries
2168 from unsupported branches is not guaranteed.
2170 Make sure that you merge any new devices from GENERIC since the
2171 last time you updated your kernel config file. Options also
2172 change over time, so you may need to adjust your custom kernels
2175 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2176 "?=" instead of the "=" assignment operator, so that buildworld can
2177 override the CPUTYPE if it needs to.
2179 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2180 not on the command line, or in /etc/make.conf. buildworld will
2181 warn if it is improperly defined.
2184 This file contains a list, in reverse chronological order, of major
2185 breakages in tracking -current. It is not guaranteed to be a complete
2186 list of such breakages, and only contains entries since September 23, 2011.
2187 If you need to see UPDATING entries from before that date, you will need
2188 to fetch an UPDATING file from an older FreeBSD release.
2190 Copyright information:
2192 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2194 Redistribution, publication, translation and use, with or without
2195 modification, in full or in part, in any form or format of this
2196 document are permitted without further permission from the author.
2198 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2199 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2200 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2201 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2202 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2203 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2204 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2205 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2206 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2207 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2208 POSSIBILITY OF SUCH DAMAGE.
2210 Contact Warner Losh if you have any questions about your use of