1Updating Information for users of FreeBSD-CURRENT. 2 3This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>. 4See end of file for further details. For commonly done items, please see the 5COMMON ITEMS: section later in the file. These instructions assume that you 6basically know what you are doing. If not, then please consult the FreeBSD 7handbook: 8 9 https://docs.freebsd.org/en/books/handbook/cutting-edge/#makeworld 10 11Items affecting the ports and packages system can be found in 12/usr/ports/UPDATING. Please read that file before updating system packages 13and/or ports. 14 15NOTE 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".) 29 3020230817: 31 Serial communication (in boot loaders, kernel, and userland) has 32 been changed to default to 115200 bps, in line with common industry 33 practice and typcial firmware serial console redirection 34 configuration. 35 36 Note that the early x86 BIOS bootloader (i.e., boot0sio) does not 37 support rates above 9600 bps and is not changed. boot0sio users may 38 set BOOT_COMCONSOLE_SPEED=9600 to use 9600 for all of the boot 39 components, or use the standard boot0 and have the boot2 stage start 40 with the serial port at 115200. 41 4220230807: 43 Following the general removal of MIPS support, the ath(4) AHB bus- 44 frontend has been removed, too, and building of the PCI support is 45 integrated with the ath(4) main module again. As a result, there's 46 no longer a need for if_ath_pci_load="YES" in /boot/loader.conf or 47 "device ath_pci" in the kernel configuration. 48 4920230803: 50 MAXCPU has been increased to 1024 in the amd64 GENERIC kernel config. 51 Out-of-tree kernel modules will need to be rebuilt. 52 5320230724: 54 CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g 55 to move to the standard uintXX_t types from the old, traditional 56 BSD u_intXX_t types. This should be a NOP, but may cause problems 57 for out of tree changes. The SIMs were not updated since most of 58 the old u_intXX_t uses weren't due to CAM interfaces. 59 6020230629: 61 The heuristic for detecting old chromebooks with an EC bug that requires 62 atkbdc driver workarounds has changed. There should be no functional 63 change, but if your old chromebook's keyboard stops working, please 64 file a PR and assign it to imp. 65 6620230623: 67 OpenSSL has been updated to version 3.0, including changes throughout 68 the base system. It is important to rebuild third-party software 69 after upgrading. 70 7120230619: 72 To enable pf rdr rules for connections initiated from the host, pf 73 filter rules can be optionally enabled for packets delivered 74 locally. This can change the behavior of rules which match packets 75 delivered to lo0. To enable this feature: 76 77 sysctl net.pf.filter_local=1 78 service pf restart 79 80 When enabled, its best to ensure that packets delivered locally are not 81 filtered, e.g. by adding a 'skip on lo' rule. 82 8320230613: 84 Improvements to libtacplus(8) mean that tacplus.conf(5) now 85 follows POSIX shell syntax rules. This may cause TACACS+ 86 authentication to fail if the shared secret contains a single 87 quote, double quote, or backslash character which isn't 88 already properly quoted or escaped. 89 9020230612: 91 Belatedly switch the default nvme block device on x86 from nvd to nda. 92 nda created nvd compatibility links by default, so this should be a 93 nop. If this causes problems for your application, set hw.nvme.use_nvd=1 94 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel 95 config. To disable the nvd compatibility aliases, add 96 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on 97 all non-x86 platforms for some time now. If you need to fall back, 98 please email imp@freebsd.org about why. 99 100 Encrypted swap partitions need to be changed from nvd to nda if you 101 migrate, or you need to use the above to switch back to nvd. 102 10320230422: 104 Remove portsnap(8). Users are encouraged to obtain the ports tree 105 using git instead. 106 10720230420: 108 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging 109 eg. 110 make buildworld-jobs 111 runs 112 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1 113 114 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env. 115 11620230316: 117 Video related devices for some arm devices have been renamed. 118 If you have a custom kernel config and want to use hdmi output on 119 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and 120 "device imx6_ipu" to it. 121 If you have a custom kernel config and want to use hdmi output on 122 TI AM335X board you need to add "device tda19988" to it. 123 If you add "device hdmi" in it you need to remove it as it doesn't 124 exist anymore. 125 12620230221: 127 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4) 128 for details. 129 13020230206: 131 sshd now defaults to having X11Forwarding disabled, following upstream. 132 Administrators who wish to enable X11Forwarding should add 133 `X11Forwarding yes` to /etc/ssh/sshd_config. 134 13520230204: 136 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default 137 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4). 138 13920230130: 140 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added 141 to the linux_common(4) module. Users relying on linux_common may need 142 to complile netlink(4) module if it is not present in their kernel. 143 14420230126: 145 The WITHOUT_CXX option has been removed. C++ components in the base 146 system are now built unconditionally. 147 14820230113: 149 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled. 150 Bump _FreeBSD_version to 1400078 to be able to detect this change. 151 15220221212: 153 llvm-objump is now always installed as objdump. Previously there was 154 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used. 155 156 Some LLVM objdump options have a different output format compared to 157 GNU objdump; readelf is available for inspecting ELF files, and GNU 158 objdump is available from the devel/binutils port or package. 159 16020221205: 161 dma(8) has replaced sendmail(8) as the default mta. For people willing 162 to reenable sendmail(8): 163 164 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf 165 166 and add sendmail_enable="YES" to rc.conf. 167 16820221204: 169 hw.bus.disable_failed_devices has changed from 'false' to 'true' by 170 default. Now if newbus succeeds in probing a device, but fails to attach 171 the device, we'll disable the device. In the past, we'd keep retrying 172 the device on each new driver loaded. To get that behavior now, one 173 needs to use devctl to re-enable the device, and reprobe it (or set 174 the sysctl/tunable hw.bus.disable_failed_devices=false). 175 176 NOTE: This was reverted 20221205 due to unexpected compatibility issues 177 17820221122: 179 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'. 180 These configurations are no longer automatically reinterpreted as 181 'scrub fragment reassemble'. 182 18320221121: 184 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled 185 it is always installed as /usr/bin/cc (and c++, cpp). 186 18720221026: 188 Some programs have been moved into separate packages. It is recommended 189 for pkgbase users to do: 190 191 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \ 192 FreeBSD-devd FreeBSD-devmatch 193 194 after upgrading to restore all the component that were previously 195 installed. 196 19720220610: 198 LinuxKPI pm.h changes require an update to the latest drm-kmod version 199 before re-compiling to avoid errors. 200 20120211230: 202 The macros provided for the manipulation of CPU sets (e.g. CPU_AND) 203 have been modified to take 2 source arguments instead of only 1. 204 Externally maintained sources that use these macros will have to 205 be adapted. The FreeBSD version has been bumped to 1400046 to 206 reflect this change. 207 20820211214: 209 A number of the kernel include files are able to be included by 210 themselves. A test has been added to buildworld to enforce this. 211 21220211209: 213 Remove mips as a recognized target. This starts the decommissioning of 214 mips support in FreeBSD. mips related items will be removed wholesale in 215 the coming days and weeks. 216 217 This broke the NO_CLEAN build for some people. Either do a clean build 218 or touch 219 lib/clang/include/llvm/Config/Targets.def 220 lib/clang/include/llvm/Config/AsmParsers.def 221 lib/clang/include/llvm/Config/Disassemblers.def 222 lib/clang/include/llvm/Config/AsmPrinters.def 223 before the build to force everything to rebuild that needs to. 224 22520211202: 226 Unbound support for RFC8375: The special-use domain 'home.arpa' is 227 by default blocked. To unblock it use a local-zone nodefault 228 statement in unbound.conf: 229 local-zone: "home.arpa." nodefault 230 231 Or use another type of local-zone to override with your choice. 232 233 The reason for this is discussed in Section 6.1 of RFC8375: 234 Because 'home.arpa.' is not globally scoped and cannot be secured 235 using DNSSEC based on the root domain's trust anchor, there is no way 236 to tell, using a standard DNS query, in which homenet scope an answer 237 belongs. Consequently, users may experience surprising results with 238 such names when roaming to different homenets. 239 24020211110: 241 Commit b8d60729deef changed the TCP congestion control framework so 242 that any of the included congestion control modules could be 243 the single module built into the kernel. Previously newreno 244 was automatically built in through direct reference. As of 245 this commit you are required to declare at least one congestion 246 control module (e.g. 'options CC_NEWRENO') and to also declare a 247 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\"). 248 The GENERIC configuration includes CC_NEWRENO and defines newreno 249 as the default. If no congestion control option is built into the 250 kernel and you are including networking, the kernel compile will 251 fail. Also if no default is declared the kernel compile will fail. 252 25320211118: 254 Mips has been removed from universe builds. It will be removed from the 255 tree shortly. 256 25720211106: 258 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE. 259 The NFS modules must be rebuilt from sources and any out 260 of tree file systems that implement their own VOP_ALLOCATE 261 may need to be modified. 262 26320211022: 264 The synchronous PPP kernel driver sppp(4) has been removed. 265 The cp(4) and ce(4) drivers are now always compiled with netgraph(4) 266 support, formerly enabled by NETGRAPH_CRONYX option. 267 26820211020: 269 sh(1) is now the default shell for the root user. To force root to use 270 the csh shell, please run the following command as root: 271 272 # chsh -s csh 273 27420211004: 275 Ncurses distribution has been split between libtinfow and libncurses 276 with libncurses.so becoming a linker (ld) script to seamlessly link 277 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect 278 this change. 279 28020210923: 281 As of commit 8160a0f62be6, the dummynet module no longer depends on the 282 ipfw module. Dummynet can now be used by pf as well as ipfw. As such 283 users who relied on this dependency may need to include ipfw in the 284 list of modules to load on their systems. 285 28620210922: 287 As of commit 903873ce1560, the mixer(8) utility has got a slightly 288 new syntax. Please refer to the mixer(8) manual page for more 289 information. The old mixer utility can be installed from ports: 290 audio/freebsd-13-mixer 291 29220210911: 293 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has 294 been deleted from the nfscommon.ko. As such, nfsd.ko must be built 295 from up to date sources to avoid an undefined reference when 296 being loaded. 297 29820210817: 299 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS 300 by default. Users can enable kernel TLS via the "KTLS" SSL 301 option. This can be enabled globally by using a custom 302 OpenSSL config file via OPENSSL_CONF or via an 303 application-specific configuration option for applications 304 which permit setting SSL options via SSL_CONF_cmd(3). 305 30620210811: 307 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS 308 modules. Therefore, all need to be rebuilt from sources. 309 31020210730: 311 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl. 312 As of be70c7a50d32 it is no longer used by userspace, but it does mean 313 users may not be able to enumerate pf states if they update the kernel 314 past b69019c14cd8 without first updating userspace past be70c7a50d32. 315 31620210729: 317 As of commit 01ad0c007964 if_bridge member interfaces can no longer 318 change their MTU. Changing the MTU of the bridge itself will change the 319 MTU on all member interfaces instead. 320 32120210716: 322 Commit ee29e6f31111 changed the internal KAPI between the nfscommon 323 and nfsd modules. Therefore, both need to be rebuilt from sources. 324 Bump __FreeBSD_version to 1400026 for this KAPI change. 325 32620210715: 327 The 20210707 awk update brought in a change in behavior. This has 328 been corrected as of d4d252c49976. Between these dates, if you 329 installed a new awk binary, you may not be able to build a new 330 kernel because the change in behavior affected the genoffset 331 script used to build the kernel. If you did update, the fix is 332 to update your sources past the above hash and do 333 % cd usr.bin/awk 334 % make clean all 335 % sudo -E make install 336 to enable building kernels again. 337 33820210708: 339 Commit 1e0a518d6548 changed the internal KAPI between the NFS 340 modules. They all need to be rebuilt from sources. I did not 341 bump __FreeBSD_version, since it was bumped recently. 342 34320210707: 344 awk has been updated to the latest one-true-awk version 20210215. 345 This contains a number of minor bug fixes. 346 34720210624: 348 The NFSv4 client now uses the highest minor version of NFSv4 349 supported by the NFSv4 server by default instead of minor version 0, 350 for NFSv4 mounts. 351 The "minorversion" mount option may be used to override this default. 352 35320210618: 354 Bump __FreeBSD_version to 1400024 for LinuxKPI changes. 355 Most notably netdev.h can change now as the (last) dependencies 356 (mlx4/ofed) are now using struct ifnet directly, but also for PCI 357 additions and others. 358 35920210618: 360 The directory "blacklisted" under /usr/share/certs/ has been 361 renamed to "untrusted". 362 36320210611: 364 svnlite has been removed from base. Should you need svn for any reason 365 please install the svn package or port. 366 36720210611: 368 Commit e1a907a25cfa changed the internal KAPI between the krpc 369 and nfsserver. As such, both modules must be rebuilt from 370 sources. Bump __FreeBSD_version to 1400022. 371 37220210610: 373 The an(4) driver has been removed from FreeBSD. 374 37520210608: 376 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to 377 start tracking OpenZFS upstream more closely. Please see 378https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html 379 for details on how to correct any errors that might result. The 380 short version is that you need to remove the old branch locally: 381 git update-ref -d refs/remotes/freebsd/vendor/openzfs 382 (assuming your upstream origin is named 'freebsd'). 383 38420210525: 385 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI 386 which break drm-kmod. In addition various other additions where 387 committed. Bump __FreeBSD_version to 1400015 to be able to 388 detect this. 389 39020210513: 391 Commit ca179c4d74f2 changed the package in which the OpenSSL 392 libraries and utilities are packaged. 393 It is recommended for pkgbase user to do: 394 pkg install -f FreeBSD-openssl 395 before pkg upgrade otherwise some dependencies might not be met 396 and pkg will stop working as libssl will not be present anymore 397 on the system. 398 39920210426: 400 Commit 875977314881 changed the internal KAPI between 401 the nfsd and nfscommon modules. As such these modules 402 need to be rebuilt from sources. 403 Without this patch in your NFSv4.1/4.2 server, enabling 404 delegations by setting vfs.nfsd.issue_delegations non-zero 405 is not recommended. 406 40720210411: 408 Commit 7763814fc9c2 changed the internal KAPI between 409 the krpc and NFS. As such, the krpc, nfscommon and 410 nfscl modules must all be rebuilt from sources. 411 Without this patch, NFSv4.1/4.2 mounts should not 412 be done with the nfscbd(8) daemon running, to avoid 413 needing a working back channel for server->client RPCs. 414 41520210330: 416 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it 417 handles binding of the back channel as required by RFC5661. 418 Until this patch is in your server, avoid use of the "nconnects" 419 mount option for Linux NFSv4.1/4.2 mounts. 420 42120210225: 422 For 64-bit architectures the base system is now built with Position 423 Independent Executable (PIE) support enabled by default. It may be 424 disabled using the WITHOUT_PIE knob. A clean build is required. 425 42620210128: 427 Various LinuxKPI functionality was added which conflicts with DRM. 428 Please update your drm-kmod port to after the __FreeBSD_version 1400003 429 update. 430 43120210108: 432 PC Card attachments for all devices have been removed. In the case of 433 wi and cmx, the entire drivers were removed because they were only 434 PC Card devices. FreeBSD_version 1300134 should be used for this 435 since it was bumped so recently. 436 43720210107: 438 Transport-independent parts of HID support have been split off the USB 439 code in to separate subsystem. Kernel configs which include one of 440 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should 441 be updated with adding of "device hid" line. 442 44320210105: 444 ncurses installation has been modified to only keep the widechar 445 enabled version. Incremental build is broken for that change, so it 446 requires a clean build. 447 44820201223: 449 The FreeBSD project has migrated from Subversion to Git. Temporary 450 instructions can be found at 451 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md 452 and other documents in that repo. 453 45420201216: 455 The services database has been updated to cover more of the basic 456 services expected in a modern system. The database is big enough 457 that it will cause issues in mergemaster in Releases previous to 458 12.2 and 11.3, or in very old current systems from before r358154. 459 46020201215: 461 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb) 462 may be installed from ports or packages. 463 46420201124: 465 ping6 has been merged into ping. It can now be called as "ping -6". 466 See ping(8) for details. 467 46820201108: 469 Default value of net.add_addr_allfibs has been changed to 0. 470 If you have multi-fib configuration and rely on existence of all 471 interface routes in every fib, you need to set the above sysctl to 1. 472 47320201030: 474 The internal pre-processor in the calendar(1) program has been 475 extended to support more C pre-processor commands (e.g. #ifdef, #else, 476 and #undef) and to detect unbalanced conditional statements. 477 Error messages have been extended to include the filename and line 478 number if processing stops to help fixing malformed data files. 479 48020201026: 481 All the data files for the calendar(1) program, except calendar.freebsd, 482 have been moved to the deskutils/calendar-data port, much like the 483 jewish calendar entries were moved to deskutils/hebcal years ago. After 484 make delete-old-files, you need to install it to retain full 485 functionality. calendar(1) will issue a reminder for files it can't 486 find. 487 48820200923: 489 LINT files are no longer generated. We now include the relevant NOTES 490 files. Note: This may cause conflicts with updating in some cases. 491 find sys -name LINT\* -delete 492 is suggested across this commit to remove the generated LINT files. 493 494 If you have tried to update with generated files there, the svn 495 command you want to un-auger the tree is 496 cd sys/amd64/conf 497 svn revert -R . 498 and then do the above find from the top level. Substitute 'amd64' 499 above with where the error message indicates a conflict. 500 50120200824: 502 OpenZFS support has been integrated. Do not upgrade root pools until 503 the loader is updated to support zstd. Furthermore, we caution against 504 'zpool upgrade' for the next few weeks. The change should be transparent 505 unless you want to use new features. 506 507 Not all "NO_CLEAN" build scenarios work across these changes. Many 508 scenarios have been tested and fixed, but rebuilding kernels without 509 rebuilding world may fail. 510 511 The ZFS cache file has moved from /boot to /etc to match the OpenZFS 512 upstream default. A fallback to /boot has been added for mountroot. 513 514 Pool auto import behavior at boot has been moved from the kernel module 515 to an explicit "zpool import -a" in one of the rc scripts enabled by 516 zfs_enable=YES. This means your non-root zpools won't auto import until 517 you upgrade your /etc/rc.d files. 518 51920200824: 520 The resume code now notifies devd with the 'kernel' system 521 rather than the old 'kern' subsystem to be consistent with 522 other use. The old notification will be created as well, but 523 will be removed prior to FreeBSD 14.0. 524 52520200821: 526 r362275 changed the internal API between the kernel RPC and the 527 NFS modules. As such, all the modules must be recompiled from 528 sources. 529 53020200817: 531 r364330 modified the internal API used between the NFS modules. 532 As such, all the NFS modules must be re-compiled from sources. 533 53420200816: 535 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 536 been upgraded to 11.0.0. Please see the 20141231 entry below for 537 information about prerequisites and upgrading, if you are not already 538 using clang 3.5.0 or higher. 539 54020200810: 541 r364092 modified the internal ABI used between the kernel NFS 542 modules. As such, all of these modules need to be rebuilt 543 from sources, so a version bump was done. 544 54520200807: 546 Makefile.inc has been updated to work around the issue documented in 547 20200729. It was a case where the optimization of using symbolic links 548 to point to binaries created a situation where we'd run new binaries 549 with old libraries starting midway through the installworld process. 550 55120200729: 552 r363679 has redefined some undefined behavior in regcomp(3); notably, 553 extraneous escapes of most ordinary characters will no longer be 554 accepted. An exp-run has identified all of the problems with this in 555 ports, but other non-ports software may need extra escapes removed to 556 continue to function. 557 558 Because of this change, installworld may encounter the following error 559 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that 560 you do not halt installworld. Instead, let it run to completion (whether 561 successful or not) and run installworld once more. 562 56320200627: 564 A new implementation of bc and dc has been imported in r362681. This 565 implementation corrects non-conformant behavior of the previous bc 566 and adds GNU bc compatible options. It offers a number of extensions, 567 is much faster on large values, and has support for message catalogs 568 (a number of languages are already supported, contributions of further 569 languages welcome). The option WITHOUT_GH_BC can be used to build the 570 world with the previous versions of bc and dc. 571 57220200625: 573 r362639 changed the internal API used between the NFS kernel modules. 574 As such, they all need to be rebuilt from sources. 575 57620200613: 577 r362158 changed the arguments for VFS_CHECKEXP(). As such, any 578 out of tree file systems need to be modified and rebuilt. 579 Also, any file systems that are modules must be rebuilt. 580 58120200604: 582 read(2) of a directory fd is now rejected by default. root may 583 re-enable it for system root only on non-ZFS filesystems with the 584 security.bsd.allow_read_dir sysctl(8) MIB if 585 security.bsd.suser_enabled=1. 586 587 It may be advised to setup aliases for grep to default to `-d skip` if 588 commonly non-recursively grepping a list that includes directories and 589 the potential for the resulting stderr output is not tolerable. Example 590 aliases are now installed, commented out, in /root/.cshrc and 591 /root/.shrc. 592 59320200523: 594 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 595 been upgraded to 10.0.1. Please see the 20141231 entry below for 596 information about prerequisites and upgrading, if you are not already 597 using clang 3.5.0 or higher. 598 59920200512: 600 Support for obsolete compilers has been removed from the build system. 601 Clang 6 and GCC 6.4 are the minimum supported versions. 602 60320200424: 604 closefrom(2) has been moved under COMPAT12, and replaced in libc with a 605 stub that calls close_range(2). If using a custom kernel configuration, 606 you may want to ensure that the COMPAT_FREEBSD12 option is included, as 607 a slightly older -CURRENT userland and older FreeBSD userlands may not 608 be functional without closefrom(2). 609 61020200414: 611 Upstream DTS from Linux 5.6 was merged and they now have the SID 612 and THS (Secure ID controller and THermal Sensor) node present. 613 The DTB overlays have now been removed from the tree for the H3/H5 and 614 A64 SoCs and the aw_sid and aw_thermal driver have been updated to 615 deal with upstream DTS. If you are using those overlays you need to 616 remove them from loader.conf and update the DTBs on the FAT partition. 617 61820200310: 619 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 620 been upgraded to 10.0.0. Please see the 20141231 entry below for 621 information about prerequisites and upgrading, if you are not already 622 using clang 3.5.0 or higher. 623 62420200309: 625 The amd(8) automount daemon has been removed from the source tree. 626 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting. 627 amd is still available in the sysutils/am-utils port. 628 62920200301: 630 Removed brooktree driver (bktr.4) from the tree. 631 63220200229: 633 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree 634 compiler in usr.bin/dtc is used on all architectures which use dtc, and 635 the GPL dtc is available (if needed) from the sysutils/dtc port. 636 63720200229: 638 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind 639 is used by all supported CPU architectures. 640 64120200229: 642 GCC 4.2.1 has been removed from the tree. The WITH_GCC, 643 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available. 644 Users who wish to build FreeBSD with GCC must use the external toolchain 645 ports or packages. 646 64720200220: 648 ncurses has been updated to a newer version (6.2-20200215). Given the ABI 649 has changed, users will have to rebuild all the ports that are linked to 650 ncurses. 651 65220200217: 653 The size of struct vnet and the magic cookie have changed. 654 Users need to recompile libkvm and all modules using VIMAGE 655 together with their new kernel. 656 65720200212: 658 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB, 659 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update 660 your Makefiles and scripts to define MK_<var>=no instead as required. 661 662 One exception to this is that program or library Makefiles should 663 define MAN to empty rather than setting MK_MAN=no. 664 66520200108: 666 Clang/LLVM is now the default compiler and LLD the default 667 linker for riscv64. 668 66920200107: 670 make universe no longer uses GCC 4.2.1 on any architectures. 671 Architectures not supported by in-tree Clang/LLVM require an 672 external toolchain package. 673 67420200104: 675 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1 676 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX 677 options default to off for all supported CPU architectures. As a 678 short-term transition aid they may be enabled via WITH_* options. 679 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31. 680 68120200102: 682 Support for armv5 has been disconnected and is being removed. The 683 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid. 684 You must now use a MACHINE_ARCH of armv6 or armv7. The default 685 MACHINE_ARCH for MACHINE=arm is now armv7. 686 68720191226: 688 Clang/LLVM is now the default compiler for all powerpc architectures. 689 LLD is now the default linker for powerpc64. The change for powerpc64 690 also includes a change to the ELFv2 ABI, incompatible with the existing 691 ABI. 692 69320191226: 694 Kernel-loadable random(4) modules are no longer unloadable. 695 69620191222: 697 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 698 been upgraded to 9.0.1. Please see the 20141231 entry below for 699 information about prerequisites and upgrading, if you are not already 700 using clang 3.5.0 or higher. 701 70220191212: 703 r355677 has modified the internal interface used between the 704 NFS modules in the kernel. As such, they must all be upgraded 705 simultaneously. I will do a version bump for this. 706 70720191205: 708 The root certificates of the Mozilla CA Certificate Store have been 709 imported into the base system and can be managed with the certctl(8) 710 utility. If you have installed the security/ca_root_nss port or package 711 with the ETCSYMLINK option (the default), be advised that there may be 712 differences between those included in the port and those included in 713 base due to differences in nss branch used as well as general update 714 frequency. Note also that certctl(8) cannot manage certs in the 715 format used by the security/ca_root_nss port. 716 71720191120: 718 The amd(8) automount daemon has been disabled by default, and will be 719 removed in the future. As of FreeBSD 10.1 the autofs(5) is available 720 for automounting. 721 72220191107: 723 The nctgpio and wbwd drivers have been moved to the superio bus. 724 If you have one of these drivers in a kernel configuration, then 725 you should add device superio to it. If you use one of these drivers 726 as a module and you compile a custom set of modules, then you should 727 add superio to the set. 728 72920191021: 730 KPIs for network drivers to access interface addresses have changed. 731 Users need to recompile NIC driver modules together with kernel. 732 73320191021: 734 The net.link.tap.user_open sysctl no longer prevents user opening of 735 already created /dev/tapNN devices. Access is still controlled by 736 node permissions, just like tun devices. The net.link.tap.user_open 737 sysctl is now used only to allow users to perform devfs cloning of 738 tap devices, and the subsequent open may not succeed if the user is not 739 in the appropriate group. This sysctl may be deprecated/removed 740 completely in the future. 741 74220191009: 743 mips, powerpc, and sparc64 are no longer built as part of 744 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If 745 not defined, mips, powerpc, and sparc64 builds will look for 746 the xtoolchain binaries and if installed use them for universe 747 builds. As llvm 9.0 becomes vetted for these architectures, they 748 will be removed from the list. 749 75020191009: 751 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 752 been upgraded to 9.0.0. Please see the 20141231 entry below for 753 information about prerequisites and upgrading, if you are not already 754 using clang 3.5.0 or higher. 755 75620191003: 757 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from 758 GENERIC. They are available as modules and can be loaded by adding 759 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES", 760 hptnr_load="YES", or hptrr_load="YES", respectively. 761 76220190913: 763 ntpd no longer by default locks its pages in memory, allowing them 764 to be paged out by the kernel. Use rlimit memlock to restore 765 historic BSD behaviour. For example, add "rlimit memlock 32" 766 to ntp.conf to lock up to 32 MB of ntpd address space in memory. 767 76820190823: 769 Several of ping6's options have been renamed for better consistency 770 with ping. If you use any of -ARWXaghmrtwx, you must update your 771 scripts. See ping6(8) for details. 772 77320190727: 774 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls 775 and the "-o sync_unmount" and "-o init_backgrounded" mount options have 776 been removed from mount_fusefs(8). You can safely remove them from 777 your scripts, because they had no effect. 778 779 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize, 780 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable, 781 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate 782 sysctls have been removed. If you felt the need to set any of them to 783 a non-default value, please tell asomers@FreeBSD.org why. 784 78520190713: 786 Default permissions on the /var/account/acct file (and copies of it 787 rotated by periodic daily scripts) are changed from 0644 to 0640 788 because the file contains sensitive information that should not be 789 world-readable. If the /var/account directory must be created by 790 rc.d/accounting, the mode used is now 0750. Admins who use the 791 accounting feature are encouraged to change the mode of an existing 792 /var/account directory to 0750 or 0700. 793 79420190620: 795 Entropy collection and the /dev/random device are no longer optional 796 components. The "device random" option has been removed. 797 Implementations of distilling algorithms can still be made loadable 798 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko). 799 80020190612: 801 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 802 been upgraded to 8.0.1. Please see the 20141231 entry below for 803 information about prerequisites and upgrading, if you are not already 804 using clang 3.5.0 or higher. 805 80620190608: 807 A fix was applied to i386 kernel modules to avoid panics with 808 dpcpu or vnet. Users need to recompile i386 kernel modules 809 having pcpu or vnet sections or they will refuse to load. 810 81120190513: 812 User-wired pages now have their own counter, 813 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed 814 to vm.max_user_wired and changed from an unsigned int to an unsigned 815 long. bhyve VMs wired with the -S are now subject to the user 816 wiring limit; the vm.max_user_wired sysctl may need to be tuned to 817 avoid running into the limit. 818 81920190507: 820 The IPSEC option has been removed from GENERIC. Users requiring 821 ipsec(4) must now load the ipsec(4) kernel module. 822 82320190507: 824 The tap(4) driver has been folded into tun(4), and the module has been 825 renamed to tuntap. You should update any kld_list="if_tap" or 826 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or 827 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap 828 module instead, and "device tap" or "device tun" entries in kernel 829 config files to select the tuntap device instead. 830 83120190418: 832 The following knobs have been added related to tradeoffs between 833 safe use of the random device and availability in the absence of 834 entropy: 835 836 kern.random.initial_seeding.bypass_before_seeding: tunable; set 837 non-zero to bypass the random device prior to seeding, or zero to 838 block random requests until the random device is initially seeded. 839 For now, set to 1 (unsafe) by default to restore pre-r346250 boot 840 availability properties. 841 842 kern.random.initial_seeding.read_random_bypassed_before_seeding: 843 read-only diagnostic sysctl that is set when bypass is enabled and 844 read_random(9) is bypassed, to enable programmatic handling of this 845 initial condition, if desired. 846 847 kern.random.initial_seeding.arc4random_bypassed_before_seeding: 848 Similar to the above, but for arc4random(9) initial seeding. 849 850 kern.random.initial_seeding.disable_bypass_warnings: tunable; set 851 non-zero to disable warnings in dmesg when the same conditions are 852 met as for the diagnostic sysctls above. Defaults to zero, i.e., 853 produce warnings in dmesg when the conditions are met. 854 85520190416: 856 The loadable random module KPI has changed; the random_infra_init() 857 routine now requires a 3rd function pointer for a bool (*)(void) 858 method that returns true if the random device is seeded (and 859 therefore unblocked). 860 86120190404: 862 r345895 reverts r320698. This implies that an nfsuserd(8) daemon 863 built from head sources between r320757 (July 6, 2017) and 864 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock" 865 is added to the command line. 866 nfsuserd daemons built from head sources that are post-r338192 are 867 not affected and should continue to work. 868 86920190320: 870 The fuse(4) module has been renamed to fusefs(4) for consistency with 871 other filesystems. You should update any kld_load="fuse" entries in 872 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and 873 "options FUSE" entries in kernel config files. 874 87520190304: 876 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 877 8.0.0. Please see the 20141231 entry below for information about 878 prerequisites and upgrading, if you are not already using clang 3.5.0 879 or higher. 880 88120190226: 882 geom_uzip(4) depends on the new module xz. If geom_uzip is statically 883 compiled into your custom kernel, add 'device xz' statement to the 884 kernel config. 885 88620190219: 887 drm and drm2 have been removed from the tree. Please see 888 https://wiki.freebsd.org/Graphics for the latest information on 889 migrating to the drm ports. 890 89120190131: 892 Iflib is no longer unconditionally compiled into the kernel. Drivers 893 using iflib and statically compiled into the kernel, now require 894 the 'device iflib' config option. For the same drivers loaded as 895 modules on kernels not having 'device iflib', the iflib.ko module 896 is loaded automatically. 897 89820190125: 899 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration 900 options no longer exist since r343219 and r343427 respectively; 901 nothing uses them, so they should be just removed from custom 902 kernel config files. 903 90420181230: 905 r342635 changes the way efibootmgr(8) works by requiring users to add 906 the -b (bootnum) parameter for commands where the bootnum was previously 907 specified with each option. For example 'efibootmgr -B 0001' is now 908 'efibootmgr -B -b 0001'. 909 91020181220: 911 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport 912 in the same as it is applied to NFSv2 and 3. This implies that NFSv4 913 servers that have vfs.nfsd.nfs_privport set will only allow mounts 914 from clients using a reserved port. Since both the FreeBSD and Linux 915 NFSv4 clients use reserved ports by default, this should not affect 916 most NFSv4 mounts. 917 91820181219: 919 The XLP config has been removed. We can't support 64-bit atomics in this 920 kernel because it is running in 32-bit mode. XLP users must transition 921 to running a 64-bit kernel (XLP64 or XLPN32). 922 923 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is 924 the preferred emulator today and we don't need two different ones. 925 926 The old sibyte / swarm / Broadcom BCM1250 support has been 927 removed from the mips port. 928 92920181211: 930 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 931 7.0.1. Please see the 20141231 entry below for information about 932 prerequisites and upgrading, if you are not already using clang 3.5.0 933 or higher. 934 93520181211: 936 Remove the timed and netdate programs from the base tree. Setting 937 the time with these daemons has been obsolete for over a decade. 938 93920181126: 940 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld 941 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as 942 it produces broken binaries when ifuncs are in use. Users needing 943 GNU ld should install the binutils port or package. 944 94520181123: 946 The BSD crtbegin and crtend code has been enabled by default. It has 947 had extensive testing on amd64, arm64, and i386. It can be disabled 948 by building a world with -DWITHOUT_BSD_CRTBEGIN. 949 95020181115: 951 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue) 952 has been converted to a port (misc/ctm) and will be removed from 953 FreeBSD-13. It is available as a package (ctm) for all supported 954 FreeBSD versions. 955 95620181110: 957 The default newsyslog.conf(5) file has been changed to only include 958 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if 959 the filenames end in '.conf' and do not begin with a '.'. 960 961 You should check the configuration files in these two directories match 962 this naming convention. You can verify which configuration files are 963 being included using the command: 964 $ newsyslog -Nrv 965 96620181015: 967 Ports for the DRM modules have been simplified. Now, amd64 users should 968 just install the drm-kmod port. All others should install 969 drm-legacy-kmod. 970 971 Graphics hardware that's newer than about 2010 usually works with 972 drm-kmod. For hardware older than 2013, however, some users will need 973 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older 974 than 2008 usually only works in drm-legacy-kmod. The graphics team can 975 only commit to hardware made since 2013 due to the complexity of the 976 market and difficulty to test all the older cards effectively. If you 977 have hardware supported by drm-kmod, you are strongly encouraged to use 978 that as you will get better support. 979 980 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined 981 elsewhere, the drm and drm2 modules will be eliminated from the src base 982 soon (with a limited exception for arm). Please update to the package 983 asap and report any issues to x11@freebsd.org. 984 985 Generally, anybody using the drm*-kmod packages should add 986 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty 987 cross-threading surprises, especially with automatic driver 988 loading from X11 startup. These will become the defaults in 13-current 989 shortly. 990 99120181012: 992 The ixlv(4) driver has been renamed to iavf(4). As a consequence, 993 custom kernel and module loading configuration files must be updated 994 accordingly. Moreover, interfaces previous presented as ixlvN to the 995 system are now exposed as iavfN and network configuration files must 996 be adjusted as necessary. 997 99820181009: 999 OpenSSL has been updated to version 1.1.1. This update included 1000 additional various API changes throughout the base system. It is 1001 important to rebuild third-party software after upgrading. The value 1002 of __FreeBSD_version has been bumped accordingly. 1003 100420181006: 1005 The legacy DRM modules and drivers have now been added to the loader's 1006 module blacklist, in favor of loading them with kld_list in rc.conf(5). 1007 The module blacklist may be overridden with the loader.conf(5) 1008 'module_blacklist' variable, but loading them via rc.conf(5) is strongly 1009 encouraged. 1010 101120181002: 1012 The cam(4) based nda(4) driver will be used over nvd(4) by default on 1013 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or 1014 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing 1015 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the 1016 nda device name. 1017 101820180913: 1019 Reproducible build mode is now on by default, in preparation for 1020 FreeBSD 12.0. This eliminates build metadata such as the user, 1021 host, and time from the kernel (and uname), unless the working tree 1022 corresponds to a modified checkout from a version control system. 1023 The previous behavior can be obtained by setting the /etc/src.conf 1024 knob WITHOUT_REPRODUCIBLE_BUILD. 1025 102620180826: 1027 The Yarrow CSPRNG has been removed from the kernel as it has not been 1028 supported by its designers since at least 2003. Fortuna has been the 1029 default since FreeBSD-11. 1030 103120180822: 1032 devctl freeze/thaw have gone into the tree, the rc scripts have been 1033 updated to use them and devmatch has been changed. You should update 1034 kernel, userland and rc scripts all at the same time. 1035 103620180818: 1037 The default interpreter has been switched from 4th to Lua. 1038 LOADER_DEFAULT_INTERP, documented in build(7), will override the default 1039 interpreter. If you have custom FORTH code you will need to set 1040 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in 1041 src.conf for the build. This will create default hard links between 1042 loader and loader_4th instead of loader and loader_lua, the new default. 1043 If you are using UEFI it will create the proper hard link to loader.efi. 1044 1045 bhyve uses userboot.so. It remains 4th-only until some issues are solved 1046 regarding coexisting with multiple versions of FreeBSD are resolved. 1047 104820180815: 1049 ls(1) now respects the COLORTERM environment variable used in other 1050 systems and software to indicate that a colored terminal is both 1051 supported and desired. If ls(1) is suddenly emitting colors, they may 1052 be disabled again by either removing the unwanted COLORTERM from your 1053 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR 1054 may not be observed in a future release. 1055 105620180808: 1057 The default pager for most commands has been changed to "less". To 1058 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in 1059 your environment. 1060 106120180731: 1062 The jedec_ts(4) driver has been removed. A superset of its functionality 1063 is available in the jedec_dimm(4) driver, and the manpage for that 1064 driver includes migration instructions. If you have "device jedec_ts" 1065 in your kernel configuration file, it must be removed. 1066 106720180730: 1068 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default. 1069 This should have no effect if the kernel is booted via BIOS/legacy boot. 1070 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system 1071 has a buggy firmware that prevents a successful boot due to use of 1072 runtime services. 1073 107420180727: 1075 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale 1076 support has been removed from the tree. These ports were 1077 obsolete and/or known to be broken for many years. 1078 107920180723: 1080 loader.efi has been augmented to participate more fully in the 1081 UEFI boot manager protocol. loader.efi will now look at the 1082 BootXXXX environment variable to determine if a specific kernel 1083 or root partition was specified. XXXX is derived from BootCurrent. 1084 efibootmgr(8) manages these standard UEFI variables. 1085 108620180720: 1087 zfsloader's functionality has now been folded into loader. 1088 zfsloader is no longer necessary once you've updated your 1089 boot blocks. For a transition period, we will install a 1090 hardlink for zfsloader to loader to allow a smooth transition 1091 until the boot blocks can be updated (hard link because old 1092 zfs boot blocks don't understand symlinks). 1093 109420180719: 1095 ARM64 now have efifb support, if you want to have serial console 1096 on your arm64 board when an screen is connected and the bootloader 1097 setup a frame buffer for us to use, just add : 1098 boot_serial=YES 1099 boot_multicons=YES 1100 in /boot/loader.conf 1101 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have 1102 an screen connected as the firmware will setup a frame buffer are that 1103 u-boot will expose as an EFI frame buffer. 1104 110520180719: 1106 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster 1107 or take steps to update /etc/passwd before doing installworld on 1108 existing systems. Do not skip the "mergemaster -Fp" step before 1109 installworld, as described in the update procedures near the bottom 1110 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd 1111 if the new mac_ntpd(4) policy is available, unless ntpd_flags or 1112 the ntp config file contain options that change file/dir locations. 1113 When such options (e.g., "statsdir" or "crypto") are used, ntpd can 1114 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after 1115 taking steps to ensure that all required files/dirs are accessible 1116 by the ntpd user. 1117 111820180717: 1119 Big endian arm support has been removed. 1120 112120180711: 1122 The static environment setup in kernel configs is no longer mutually 1123 exclusive with the loader(8) environment by default. In order to 1124 restore the previous default behavior of disabling the loader(8) 1125 environment if a static environment is present, you must specify 1126 loader_env.disabled=1 in the static environment. 1127 112820180705: 1129 The ABI of syscalls used by management tools like sockstat and 1130 netstat has been broken to allow 32-bit binaries to work on 1131 64-bit kernels without modification. These programs will need 1132 to match the kernel in order to function. External programs may 1133 require minor modifications to accommodate a change of type in 1134 structures from pointers to 64-bit virtual addresses. 1135 113620180702: 1137 On i386 and amd64 atomics are now inlined. Out of tree modules using 1138 atomics will need to be rebuilt. 1139 114020180701: 1141 The '%I' format in the kern.corefile sysctl limits the number of 1142 core files that a process can generate to the number stored in the 1143 debug.ncores sysctl. The '%I' format is replaced by the single digit 1144 index. Previously, if all indexes were taken the kernel would overwrite 1145 only a core file with the highest index in a filename. 1146 Currently the system will create a new core file if there is a free 1147 index or if all slots are taken it will overwrite the oldest one. 1148 114920180630: 1150 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 1151 6.0.1. Please see the 20141231 entry below for information about 1152 prerequisites and upgrading, if you are not already using clang 3.5.0 1153 or higher. 1154 115520180628: 1156 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf 1157 needed to be changed to work with it. This change was made with r335763 1158 and requires a mergemaster / etcupdate / etc to update the installed 1159 file. 1160 116120180612: 1162 r334930 changed the interface between the NFS modules, so they all 1163 need to be rebuilt. r335018 did a __FreeBSD_version bump for this. 1164 116520180530: 1166 As of r334391 lld is the default amd64 system linker; it is installed 1167 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no 1168 longer necessary. 1169 117020180530: 1171 The kernel / userland interface for devinfo changed, so you'll 1172 need a new kernel and userland as a pair for it to work (rebuilding 1173 lib/libdevinfo is all that's required). devinfo and devmatch will 1174 not work, but everything else will when there's a mismatch. 1175 117620180523: 1177 The on-disk format for hwpmc callchain records has changed to include 1178 threadid corresponding to a given record. This changes the field offsets 1179 and thus requires that libpmcstat be rebuilt before using a kernel 1180 later than r334108. 1181 118220180517: 1183 The vxge(4) driver has been removed. This driver was introduced into 1184 HEAD one week before the Exar left the Ethernet market and is not 1185 known to be used. If you have device vxge in your kernel config file 1186 it must be removed. 1187 118820180510: 1189 The amd64 kernel now requires a ld that supports ifunc to produce a 1190 working kernel, either lld or a newer binutils. lld is built by default 1191 on amd64, and the 'buildkernel' target uses it automatically. However, 1192 it is not the default linker, so building the kernel the traditional 1193 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for 1194 binutils port/package). lld will soon be default, and this requirement 1195 will go away. 1196 1197 NOTE: As of r334391 lld is the default system linker on amd64, and no 1198 workaround is necessary. 1199 120020180508: 1201 The nxge(4) driver has been removed. This driver was for PCI-X 10g 1202 cards made by s2io/Neterion. The company was acquired by Exar and 1203 no longer sells or supports Ethernet products. If you have device 1204 nxge in your kernel config file it must be removed. 1205 120620180504: 1207 The tz database (tzdb) has been updated to 2018e. This version more 1208 correctly models time stamps in time zones with negative DST such as 1209 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and 1210 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only 1211 time zone abbreviations and the tm_isdst flag. 1212 121320180502: 1214 The ixgb(4) driver has been removed. This driver was for an early and 1215 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel 1216 quickly shifted to the long lived ixgbe family. If you have device 1217 ixgb in your kernel config file it must be removed. 1218 121920180501: 1220 The lmc(4) driver has been removed. This was a WAN interface 1221 card that was already reportedly rare in 2003, and had an ambiguous 1222 license. If you have device lmc in your kernel config file it must 1223 be removed. 1224 122520180413: 1226 Support for Arcnet networks has been removed. If you have device 1227 arcnet or device cm in your kernel config file they must be 1228 removed. 1229 123020180411: 1231 Support for FDDI networks has been removed. If you have device 1232 fddi or device fpa in your kernel config file they must be 1233 removed. 1234 123520180406: 1236 In addition to supporting RFC 3164 formatted messages, the 1237 syslogd(8) service is now capable of parsing RFC 5424 formatted 1238 log messages. The main benefit of using RFC 5424 is that clients 1239 may now send log messages with timestamps containing year numbers, 1240 microseconds and time zone offsets. 1241 1242 Similarly, the syslog(3) C library function has been altered to 1243 send RFC 5424 formatted messages to the local system logging 1244 daemon. On systems using syslogd(8), this change should have no 1245 negative impact, as long as syslogd(8) and the C library are 1246 updated at the same time. On systems using a different system 1247 logging daemon, it may be necessary to make configuration 1248 adjustments, depending on the software used. 1249 1250 When using syslog-ng, add the 'syslog-protocol' flag to local 1251 input sources to enable parsing of RFC 5424 formatted messages: 1252 1253 source src { 1254 unix-dgram("/var/run/log" flags(syslog-protocol)); 1255 } 1256 1257 When using rsyslog, disable the 'SysSock.UseSpecialParser' option 1258 of the 'imuxsock' module to let messages be processed by the 1259 regular RFC 3164/5424 parsing pipeline: 1260 1261 module(load="imuxsock" SysSock.UseSpecialParser="off") 1262 1263 Do note that these changes only affect communication between local 1264 applications and syslogd(8). The format that syslogd(8) uses to 1265 store messages on disk or forward messages to other systems 1266 remains unchanged. syslogd(8) still uses RFC 3164 for these 1267 purposes. Options to customize this behaviour will be added in the 1268 future. Utilities that process log files stored in /var/log are 1269 thus expected to continue to function as before. 1270 1271 __FreeBSD_version has been incremented to 1200061 to denote this 1272 change. 1273 127420180328: 1275 Support for token ring networks has been removed. If you 1276 have "device token" in your kernel config you should remove 1277 it. No device drivers supported token ring. 1278 127920180323: 1280 makefs was modified to be able to tag ISO9660 El Torito boot catalog 1281 entries as EFI instead of overloading the i386 tag as done previously. 1282 The amd64 mkisoimages.sh script used to build amd64 ISO images for 1283 release was updated to use this. This may mean that makefs must be 1284 updated before "make cdrom" can be run in the release directory. This 1285 should be as simple as: 1286 1287 $ cd $SRCDIR/usr.sbin/makefs 1288 $ make depend all install 1289 129020180212: 1291 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for 1292 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf. 1293 Co-existence for the transition period will come shortly. Booting is a 1294 complex environment and test coverage for Lua-enabled loaders has been 1295 thin, so it would be prudent to assume it might not work and make 1296 provisions for backup boot methods. 1297 129820180211: 1299 devmatch functionality has been turned on in devd. It will automatically 1300 load drivers for unattached devices. This may cause unexpected drivers 1301 to be loaded. Please report any problems to current@ and 1302 imp@freebsd.org. 1303 130420180114: 1305 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 1306 6.0.0. Please see the 20141231 entry below for information about 1307 prerequisites and upgrading, if you are not already using clang 3.5.0 1308 or higher. 1309 131020180110: 1311 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker. 1312 This means it is used to link the kernel and userland libraries and 1313 executables, but is not yet installed as /usr/bin/ld by default. 1314 1315 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set 1316 WITHOUT_LLD_BOOTSTRAP=yes 1317 131820180110: 1319 On i386, pmtimer has been removed. Its functionality has been folded 1320 into apm. It was a no-op on ACPI in current for a while now (but was 1321 still needed on i386 in FreeBSD 11 and earlier). Users may need to 1322 remove it from kernel config files. 1323 132420180104: 1325 The use of RSS hash from the network card aka flowid has been 1326 disabled by default for lagg(4) as it's currently incompatible with 1327 the lacp and loadbalance protocols. 1328 1329 This can be re-enabled by setting the following in loader.conf: 1330 net.link.lagg.default_use_flowid="1" 1331 133220180102: 1333 The SW_WATCHDOG option is no longer necessary to enable the 1334 hardclock-based software watchdog if no hardware watchdog is 1335 configured. As before, SW_WATCHDOG will cause the software 1336 watchdog to be enabled even if a hardware watchdog is configured. 1337 133820171215: 1339 r326887 fixes the issue described in the 20171214 UPDATING entry. 1340 r326888 flips the switch back to building GELI support always. 1341 134220171214: 1343 r362593 broke ZFS + GELI support for reasons unknown. However, 1344 it also broke ZFS support generally, so GELI has been turned off 1345 by default as the lesser evil in r326857. If you boot off ZFS and/or 1346 GELI, it might not be a good time to update. 1347 134820171125: 1349 PowerPC users must update loader(8) by rebuilding world before 1350 installing a new kernel, as the protocol connecting them has 1351 changed. Without the update, loader metadata will not be passed 1352 successfully to the kernel and users will have to enter their 1353 root partition at the kernel mountroot prompt to continue booting. 1354 Newer versions of loader can boot old kernels without issue. 1355 135620171110: 1357 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to 1358 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed 1359 to WITH/OUT_LOADER_GELI. 1360 136120171106: 1362 The naive and non-compliant support of posix_fallocate(2) in ZFS 1363 has been removed as of r325320. The system call now returns EINVAL 1364 when used on a ZFS file. Although the new behavior complies with the 1365 standard, some consumers are not prepared to cope with it. 1366 One known victim is lld prior to r325420. 1367 136820171102: 1369 Building in a FreeBSD src checkout will automatically create object 1370 directories now rather than store files in the current directory if 1371 'make obj' was not ran. Calling 'make obj' is no longer necessary. 1372 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in 1373 /etc/src-env.conf (not /etc/src.conf), or passing the option in the 1374 environment. 1375 137620171101: 1377 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native 1378 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified 1379 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old 1380 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf, 1381 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building. 1382 The UNIFIED_OBJDIR option is a transitional feature that will be 1383 removed for 12.0 release; please migrate to the new format for any 1384 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather 1385 than hardcoding paths. 1386 138720171028: 1388 The native-xtools target no longer installs the files by default to the 1389 OBJDIR. Use the native-xtools-install target with a DESTDIR to install 1390 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin. 1391 139220171021: 1393 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT 1394 options are changing from controlling the build if defined / undefined 1395 to controlling the build with explicit 'yes' or 'no' values. They will 1396 shift to WITH/WITHOUT options to match other options in the system. 1397 139820171010: 1399 libstand has turned into a private library for sys/boot use only. 1400 It is no longer supported as a public interface outside of sys/boot. 1401 140220171005: 1403 The arm port has split armv6 into armv6 and armv7. armv7 is now 1404 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system 1405 and are running a kernel from before r324363, you will need to add 1406 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build. 1407 140820171003: 1409 When building multiple kernels using KERNCONF, non-existent KERNCONF 1410 files will produce an error and buildkernel will fail. Previously 1411 missing KERNCONF files silently failed giving no indication as to 1412 why, only to subsequently discover during installkernel that the 1413 desired kernel was never built in the first place. 1414 141520170912: 1416 The default serial number format for CTL LUNs has changed. This will 1417 affect users who use /dev/diskid/* device nodes, or whose FibreChannel 1418 or iSCSI clients care about their LUNs' serial numbers. Users who 1419 require serial number stability should hardcode serial numbers in 1420 /etc/ctl.conf . 1421 142220170912: 1423 For 32-bit arm compiled for hard-float support, soft-floating point 1424 binaries now always get their shared libraries from 1425 LD_SOFT_LIBRARY_PATH (in the past, this was only used if 1426 /usr/libsoft also existed). Only users with a hard-float ld.so, but 1427 soft-float everything else should be affected. 1428 142920170826: 1430 The geli password typed at boot is now hidden. To restore the previous 1431 behavior, see geli(8) for configuration options. 1432 143320170825: 1434 Move PMTUD blackhole counters to TCPSTATS and remove them from bare 1435 sysctl values. Minor nit, but requires a rebuild of both world/kernel 1436 to complete. 1437 143820170814: 1439 "make check" behavior (made in ^/head@r295380) has been changed to 1440 execute from a limited sandbox, as opposed to executing from 1441 ${TESTSDIR}. 1442 1443 Behavioral changes: 1444 - The "beforecheck" and "aftercheck" targets are now specified. 1445 - ${CHECKDIR} (added in commit noted above) has been removed. 1446 - Legacy behavior can be enabled by setting 1447 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment. 1448 1449 If the limited sandbox mode is enabled, "make check" will execute 1450 "make distribution", then install, execute the tests, and clean up the 1451 sandbox if successful. 1452 1453 The "make distribution" and "make install" targets are typically run as 1454 root to set appropriate permissions and ownership at installation time. 1455 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the 1456 environment if executing "make check" with limited sandbox mode using 1457 an unprivileged user. 1458 145920170808: 1460 Since the switch to GPT disk labels, fsck for UFS/FFS has been 1461 unable to automatically find alternate superblocks. As of r322297, 1462 the information needed to find alternate superblocks has been 1463 moved to the end of the area reserved for the boot block. 1464 Filesystems created with a newfs of this vintage or later 1465 will create the recovery information. If you have a filesystem 1466 created prior to this change and wish to have a recovery block 1467 created for your filesystem, you can do so by running fsck in 1468 foreground mode (i.e., do not use the -p or -y options). As it 1469 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS'' 1470 to which you should answer yes. 1471 147220170728: 1473 As of r321665, an NFSv4 server configuration that services 1474 Kerberos mounts or clients that do not support the uid/gid in 1475 owner/owner_group string capability, must explicitly enable 1476 the nfsuserd daemon by adding nfsuserd_enable="YES" to the 1477 machine's /etc/rc.conf file. 1478 147920170722: 1480 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0. 1481 Please see the 20141231 entry below for information about prerequisites 1482 and upgrading, if you are not already using clang 3.5.0 or higher. 1483 148420170701: 1485 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the 1486 r-commands (rlogin, rsh, etc.) to be built with the base system. 1487 148820170625: 1489 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is 1490 a very major ABI incompatible change, so users of FreeBSD/powerpc must 1491 be careful when performing source upgrades. It is best to run 1492 'make installworld' from an alternate root system, either a live 1493 CD/memory stick, or a temporary root partition. Additionally, all ports 1494 must be recompiled. powerpc64 is largely unaffected, except in the case 1495 of 32-bit compatibility. All 32-bit binaries will be affected. 1496 149720170623: 1498 Forward compatibility for the "ino64" project have been committed. This 1499 will allow most new binaries to run on older kernels in a limited 1500 fashion. This prevents many of the common foot-shooting actions in the 1501 upgrade as well as the limited ability to roll back the kernel across 1502 the ino64 upgrade. Complicated use cases may not work properly, though 1503 enough simpler ones work to allow recovery in most situations. 1504 150520170620: 1506 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC 1507 if you require the GPL compiler. 1508 150920170618: 1510 The internal ABI used for communication between the NFS kernel modules 1511 was changed by r320085, so __FreeBSD_version was bumped to 1512 ensure all the NFS related modules are updated together. 1513 151420170617: 1515 The ABI of struct event was changed by extending the data 1516 member to 64bit and adding ext fields. For upgrade, same 1517 precautions as for the entry 20170523 "ino64" must be 1518 followed. 1519 152020170531: 1521 The GNU roff toolchain has been removed from base. To render manpages 1522 which are not supported by mandoc(1), man(1) can fallback on GNU roff 1523 from ports (and recommends to install it). 1524 To render roff(7) documents, consider using GNU roff from ports or the 1525 heirloom doctools roff toolchain from ports via pkg install groff or 1526 via pkg install heirloom-doctools. 1527 152820170524: 1529 The ath(4) and ath_hal(4) modules now build piecemeal to allow for 1530 smaller runtime footprint builds. This is useful for embedded systems 1531 which only require one chipset support. 1532 1533 If you load it as a module, make sure this is in /boot/loader.conf: 1534 1535 if_ath_load="YES" 1536 1537 This will load the HAL, all chip/RF backends and if_ath_pci. 1538 If you have if_ath_pci in /boot/loader.conf, ensure it is after 1539 if_ath or it will not load any HAL chipset support. 1540 1541 If you want to selectively load things (eg on cheaper ARM/MIPS 1542 platforms where RAM is at a premium) you should: 1543 1544 * load ath_hal 1545 * load the chip modules in question 1546 * load ath_rate, ath_dfs 1547 * load ath_main 1548 * load if_ath_pci and/or if_ath_ahb depending upon your particular 1549 bus bind type - this is where probe/attach is done. 1550 1551 For further comments/feedback, poke adrian@ . 1552 155320170523: 1554 The "ino64" 64-bit inode project has been committed, which extends 1555 a number of types to 64 bits. Upgrading in place requires care and 1556 adherence to the documented upgrade procedure. 1557 1558 If using a custom kernel configuration ensure that the 1559 COMPAT_FREEBSD11 option is included (as during the upgrade the 1560 system will be running the ino64 kernel with the existing world). 1561 1562 For the safest in-place upgrade begin by removing previous build 1563 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full 1564 procedure documented below under the heading "To rebuild everything and 1565 install it on the current system." Specifically, a reboot is required 1566 after installing the new kernel before installing world. While an 1567 installworld normally works by accident from multiuser after rebooting 1568 the proper kernel, there are many cases where this will fail across this 1569 upgrade and installworld from single user is required. 1570 157120170424: 1572 The NATM framework including the en(4), fatm(4), hatm(4), and 1573 patm(4) devices has been removed. Consumers should plan a 1574 migration before the end-of-life date for FreeBSD 11. 1575 157620170420: 1577 GNU diff has been replaced by a BSD licensed diff. Some features of GNU 1578 diff has not been implemented, if those are needed a newer version of 1579 GNU diff is available via the diffutils package under the gdiff name. 1580 158120170413: 1582 As of r316810 for ipfilter, keep frags is no longer assumed when 1583 keep state is specified in a rule. r316810 aligns ipfilter with 1584 documentation in man pages separating keep frags from keep state. 1585 This allows keep state to be specified without forcing keep frags 1586 and allows keep frags to be specified independently of keep state. 1587 To maintain previous behaviour, also specify keep frags with 1588 keep state (as documented in ipf.conf.5). 1589 159020170407: 1591 arm64 builds now use the base system LLD 4.0.0 linker by default, 1592 instead of requiring that the aarch64-binutils port or package be 1593 installed. To continue using aarch64-binutils, set 1594 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin . 1595 159620170405: 1597 The UDP optimization in entry 20160818 that added the sysctl 1598 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast 1599 packets will no longer be treated as L3 broadcast packets. 1600 160120170331: 1602 Binds and sends to the loopback addresses, IPv6 and IPv4, will now 1603 use any explicitly assigned loopback address available in the jail 1604 instead of using the first assigned address of the jail. 1605 160620170329: 1607 The ctl.ko module no longer implements the iSCSI target frontend: 1608 cfiscsi.ko does instead. 1609 1610 If building cfiscsi.ko as a kernel module, the module can be loaded 1611 via one of the following methods: 1612 - `cfiscsi_load="YES"` in loader.conf(5). 1613 - Add `cfiscsi` to `$kld_list` in rc.conf(5). 1614 - ctladm(8)/ctld(8), when compiled with iSCSI support 1615 (`WITH_ISCSI=yes` in src.conf(5)) 1616 1617 Please see cfiscsi(4) for more details. 1618 161920170316: 1620 The mmcsd.ko module now additionally depends on geom_flashmap.ko. 1621 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the 1622 same source (previously, the dependency of mmcsd.ko on mmc.ko was 1623 missing, but mmcsd.ko now will refuse to load if it is incompatible 1624 with mmc.ko). 1625 162620170315: 1627 The syntax of ipfw(8) named states was changed to avoid ambiguity. 1628 If you have used named states in the firewall rules, you need to modify 1629 them after installworld and before rebooting. Now named states must 1630 be prefixed with colon. 1631 163220170311: 1633 The old drm (sys/dev/drm/) drivers for i915 and radeon have been 1634 removed as the userland we provide cannot use them. The KMS version 1635 (sys/dev/drm2) supports the same hardware. 1636 163720170302: 1638 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0. 1639 Please see the 20141231 entry below for information about prerequisites 1640 and upgrading, if you are not already using clang 3.5.0 or higher. 1641 164220170221: 1643 The code that provides support for ZFS .zfs/ directory functionality 1644 has been reimplemented. It's not possible now to create a snapshot 1645 by mkdir under .zfs/snapshot/. That should be the only user visible 1646 change. 1647 164820170216: 1649 EISA bus support has been removed. The WITH_EISA option is no longer 1650 valid. 1651 165220170215: 1653 MCA bus support has been removed. 1654 165520170127: 1656 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed 1657 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC. 1658 165920170112: 1660 The EM_MULTIQUEUE kernel configuration option is deprecated now that 1661 the em(4) driver conforms to iflib specifications. 1662 166320170109: 1664 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via 1665 IFLIB. If you have a custom kernel configuration that excludes em(4) 1666 but you use igb(4), you need to re-add em(4) to your custom 1667 configuration. 1668 166920161217: 1670 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1. 1671 Please see the 20141231 entry below for information about prerequisites 1672 and upgrading, if you are not already using clang 3.5.0 or higher. 1673 167420161124: 1675 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0. 1676 Please see the 20141231 entry below for information about prerequisites 1677 and upgrading, if you are not already using clang 3.5.0 or higher. 1678 167920161119: 1680 The layout of the pmap structure has changed for powerpc to put the pmap 1681 statistics at the front for all CPU variations. libkvm(3) and all tools 1682 that link against it need to be recompiled. 1683 168420161030: 1685 isl(4) and cyapa(4) drivers now require a new driver, 1686 chromebook_platform(4), to work properly on Chromebook-class hardware. 1687 On other types of hardware the drivers may need to be configured using 1688 device hints. Please see the corresponding manual pages for details. 1689 169020161017: 1691 The urtwn(4) driver was merged into rtwn(4) and now consists of 1692 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific 1693 parts. 1694 Also, firmware for RTL8188CE was renamed due to possible name 1695 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B)) 1696 169720161015: 1698 GNU rcs has been removed from base. It is available as packages: 1699 - rcs: Latest GPLv3 GNU rcs version. 1700 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was 1701 removed from base. 1702 170320161008: 1704 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control 1705 modules now requires that the kernel configuration contain the 1706 TCP_HHOOK option. (This option is included in the GENERIC kernel.) 1707 170820161003: 1709 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired. 1710 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy. 1711 171220160924: 1713 Relocatable object files with the extension of .So have been renamed 1714 to use an extension of .pico instead. The purpose of this change is 1715 to avoid a name clash with shared libraries on case-insensitive file 1716 systems. On those file systems, foo.So is the same file as foo.so. 1717 171820160918: 1719 GNU rcs has been turned off by default. It can (temporarily) be built 1720 again by adding WITH_RCS knob in src.conf. 1721 Otherwise, GNU rcs is available from packages: 1722 - rcs: Latest GPLv3 GNU rcs version. 1723 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base. 1724 172520160918: 1726 The backup_uses_rcs functionality has been removed from rc.subr. 1727 172820160908: 1729 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into 1730 two separate components, QUEUE_MACRO_DEBUG_TRACE and 1731 QUEUE_MACRO_DEBUG_TRASH. Define both for the original 1732 QUEUE_MACRO_DEBUG behavior. 1733 173420160824: 1735 r304787 changed some ioctl interfaces between the iSCSI userspace 1736 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be 1737 rebuilt to work with new kernels. __FreeBSD_version has been bumped 1738 to 1200005. 1739 174020160818: 1741 The UDP receive code has been updated to only treat incoming UDP 1742 packets that were addressed to an L2 broadcast address as L3 1743 broadcast packets. It is not expected that this will affect any 1744 standards-conforming UDP application. The new behaviour can be 1745 disabled by setting the sysctl net.inet.udp.require_l2_bcast to 1746 0. 1747 174820160818: 1749 Remove the openbsd_poll system call. 1750 __FreeBSD_version has been bumped because of this. 1751 175220160708: 1753 The stable/11 branch has been created from head@r302406. 1754 1755After branch N is created, entries older than the N-2 branch point are removed 1756from this file. After stable/14 is branched and current becomes FreeBSD 15, 1757entries older than stable/12 branch point will be removed from current's 1758UPDATING file. 1759 1760COMMON ITEMS: 1761 1762 General Notes 1763 ------------- 1764 Sometimes, obscure build problems are the result of environment 1765 poisoning. This can happen because the make utility reads its 1766 environment when searching for values for global variables. To run 1767 your build attempts in an "environmental clean room", prefix all make 1768 commands with 'env -i '. See the env(1) manual page for more details. 1769 Occasionally a build failure will occur with "make -j" due to a race 1770 condition. If this happens try building again without -j, and please 1771 report a bug if it happens consistently. 1772 1773 When upgrading from one major version to another it is generally best to 1774 upgrade to the latest code in the currently installed branch first, then 1775 do an upgrade to the new branch. This is the best-tested upgrade path, 1776 and has the highest probability of being successful. Please try this 1777 approach if you encounter problems with a major version upgrade. Since 1778 the stable 4.x branch point, one has generally been able to upgrade from 1779 anywhere in the most recent stable branch to head / current (or even the 1780 last couple of stable branches). See the top of this file when there's 1781 an exception. 1782 1783 The update process will emit an error on an attempt to perform a build 1784 or install from a FreeBSD version below the earliest supported version. 1785 When updating from an older version the update should be performed one 1786 major release at a time, including running `make delete-old` at each 1787 step. 1788 1789 When upgrading a live system, having a root shell around before 1790 installing anything can help undo problems. Not having a root shell 1791 around can lead to problems if pam has changed too much from your 1792 starting point to allow continued authentication after the upgrade. 1793 1794 This file should be read as a log of events. When a later event changes 1795 information of a prior event, the prior event should not be deleted. 1796 Instead, a pointer to the entry with the new information should be 1797 placed in the old entry. Readers of this file should also sanity check 1798 older entries before relying on them blindly. Authors of new entries 1799 should write them with this in mind. 1800 1801 ZFS notes 1802 --------- 1803 When upgrading the boot ZFS pool to a new version (via zpool upgrade), 1804 always follow these three steps: 1805 1806 1) recompile and reinstall the ZFS boot loader and boot block 1807 (this is part of "make buildworld" and "make installworld") 1808 1809 2) update the ZFS boot block on your boot drive (only required when 1810 doing a zpool upgrade): 1811 1812 When booting on x86 via BIOS, use the following to update the ZFS boot 1813 block on the freebsd-boot partition of a GPT partitioned drive ada0: 1814 gpart bootcode -p /boot/gptzfsboot -i $N ada0 1815 The value $N will typically be 1. For EFI booting, see EFI notes. 1816 1817 3) zpool upgrade the root pool. New bootblocks will work with old 1818 pools, but not vice versa, so they need to be updated before any 1819 zpool upgrade. 1820 1821 Non-boot pools do not need these updates. 1822 1823 EFI notes 1824 --------- 1825 1826 There are two locations the boot loader can be installed into. The 1827 current location (and the default) is \efi\freebsd\loader.efi and using 1828 efibootmgr(8) to configure it. The old location, that must be used on 1829 deficient systems that don't honor efibootmgr(8) protocols, is the 1830 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy 1831 /boot/loader.efi to this location, but on systems installed a long time 1832 ago the ESP may be too small and /boot/boot1.efi may be needed unless 1833 the ESP has been expanded in the meantime. 1834 1835 Recent systems will have the ESP mounted on /boot/efi, but older ones 1836 may not have it mounted at all, or mounted in a different 1837 location. Older arm SD images with MBR used /boot/msdos as the 1838 mountpoint. The ESP is a MSDOS filesystem. 1839 1840 The EFI boot loader rarely needs to be updated. For ZFS booting, 1841 however, you must update loader.efi before you do 'zpool upgrade' the 1842 root zpool, otherwise the old loader.efi may reject the upgraded zpool 1843 since it does not automatically understand some new features. 1844 1845 See loader.efi(8) and uefi(8) for more details. 1846 1847 To build a kernel 1848 ----------------- 1849 If you are updating from a prior version of FreeBSD (even one just 1850 a few days old), you should follow this procedure. It is the most 1851 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 1852 1853 make kernel-toolchain 1854 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1855 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1856 1857 To test a kernel once 1858 --------------------- 1859 If you just want to boot a kernel once (because you are not sure 1860 if it works, or if you want to boot a known bad kernel to provide 1861 debugging information) run 1862 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 1863 nextboot -k testkernel 1864 1865 To rebuild everything and install it on the current system. 1866 ----------------------------------------------------------- 1867 # Note: sometimes if you are running current you gotta do more than 1868 # is listed here if you are upgrading from a really old current. 1869 1870 <make sure you have good level 0 dumps> 1871 make buildworld 1872 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1873 make installkernel KERNCONF=YOUR_KERNEL_HERE 1874 [1] 1875 <reboot in single user> [3] 1876 etcupdate -p [5] 1877 make installworld 1878 etcupdate -B [4] 1879 make delete-old [6] 1880 <reboot> 1881 1882 To cross-install current onto a separate partition 1883 -------------------------------------------------- 1884 # In this approach we use a separate partition to hold 1885 # current's root, 'usr', and 'var' directories. A partition 1886 # holding "/", "/usr" and "/var" should be about 2GB in 1887 # size. 1888 1889 <make sure you have good level 0 dumps> 1890 <boot into -stable> 1891 make buildworld 1892 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1893 <maybe newfs current's root partition> 1894 <mount current's root partition on directory ${CURRENT_ROOT}> 1895 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC 1896 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1897 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1898 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1899 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1900 <reboot into current> 1901 <do a "native" rebuild/install as described in the previous section> 1902 <maybe install compatibility libraries from ports/misc/compat*> 1903 <reboot> 1904 1905 1906 To upgrade in-place from stable to current 1907 ---------------------------------------------- 1908 <make sure you have good level 0 dumps> 1909 make buildworld [9] 1910 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1911 make installkernel KERNCONF=YOUR_KERNEL_HERE 1912 [1] 1913 <reboot in single user> [3] 1914 etcupdate -p [5] 1915 make installworld 1916 etcupdate -B [4] 1917 make delete-old [6] 1918 <reboot> 1919 1920 Make sure that you've read the UPDATING file to understand the 1921 tweaks to various things you need. At this point in the life 1922 cycle of current, things change often and you are on your own 1923 to cope. The defaults can also change, so please read ALL of 1924 the UPDATING entries. 1925 1926 Also, if you are tracking -current, you must be subscribed to 1927 freebsd-current@freebsd.org. Make sure that before you update 1928 your sources that you have read and understood all the recent 1929 messages there. If in doubt, please track -stable which has 1930 much fewer pitfalls. 1931 1932 [1] If you have third party modules, such as vmware, you should disable 1933 them at this point so they don't crash your system on 1934 reboot. Alternatively, you should rebuild all the modules you have in 1935 your system and install them as well. If you are running -current, you 1936 should seriously consider placing all sources to all the modules for 1937 your system (or symlinks to them) in /usr/local/sys/modules so this 1938 happens automatically. If all your modules come from ports, then adding 1939 the port origin directories to PORTS_MODULES instead is also automatic 1940 and effective, eg: 1941 PORTS_MODULES+=x11/nvidia-driver 1942 1943 [3] From the bootblocks, boot -s, and then do 1944 fsck -p 1945 mount -u / 1946 mount -a 1947 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed 1948 cd src # full path to source 1949 adjkerntz -i # if CMOS is wall time 1950 Also, when doing a major release upgrade, it is required that you boot 1951 into single user mode to do the installworld. 1952 1953 [4] Note: This step is non-optional. Failure to do this step 1954 can result in a significant reduction in the functionality of the 1955 system. Attempting to do it by hand is not recommended and those 1956 that pursue this avenue should read this file carefully, as well 1957 as the archives of freebsd-current and freebsd-hackers mailing lists 1958 for potential gotchas. See etcupdate(8) for more information. 1959 1960 [5] Usually this step is a no-op. However, from time to time 1961 you may need to do this if you get unknown user in the following 1962 step. 1963 1964 [6] This only deletes old files and directories. Old libraries 1965 can be deleted by "make delete-old-libs", but you have to make 1966 sure that no program is using those libraries anymore. 1967 1968 [8] The new kernel must be able to run existing binaries used by an 1969 installworld. When upgrading across major versions, the new kernel's 1970 configuration must include the correct COMPAT_FREEBSD<n> option for 1971 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure 1972 to do so may leave you with a system that is hard to boot to recover. A 1973 GENERIC kernel will include suitable compatibility options to run 1974 binaries from older branches. Note that the ability to run binaries 1975 from unsupported branches is not guaranteed. 1976 1977 Make sure that you merge any new devices from GENERIC since the 1978 last time you updated your kernel config file. Options also 1979 change over time, so you may need to adjust your custom kernels 1980 for these as well. 1981 1982 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1983 "?=" instead of the "=" assignment operator, so that buildworld can 1984 override the CPUTYPE if it needs to. 1985 1986 MAKEOBJDIRPREFIX must be defined in an environment variable, and 1987 not on the command line, or in /etc/make.conf. buildworld will 1988 warn if it is improperly defined. 1989FORMAT: 1990 1991This file contains a list, in reverse chronological order, of major 1992breakages in tracking -current. It is not guaranteed to be a complete 1993list of such breakages, and only contains entries since September 23, 2011. 1994If you need to see UPDATING entries from before that date, you will need 1995to fetch an UPDATING file from an older FreeBSD release. 1996 1997Copyright information: 1998 1999Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org> 2000 2001Redistribution, publication, translation and use, with or without 2002modification, in full or in part, in any form or format of this 2003document are permitted without further permission from the author. 2004 2005THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 2006IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 2007WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 2008DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 2009INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 2010(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 2011SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 2012HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 2013STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 2014IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 2015POSSIBILITY OF SUCH DAMAGE. 2016 2017Contact Warner Losh if you have any questions about your use of 2018this document. 2019