1 Updating Information for FreeBSD current users. 2 3This file is maintained and copyrighted by M. Warner Losh <[email protected]>. 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://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html 10 11Items affecting the ports and packages system can be found in 12/usr/ports/UPDATING. Please read that file before running portupgrade. 13 14NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping 15from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to 16the tip of head, and then rebuild without this option. The bootstrap process 17from older version of current across the gcc/clang cutover is a bit fragile. 18 1920190723: 20 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 21 been upgraded to 8.0.1. Please see the 20141231 entry below for 22 information about prerequisites and upgrading, if you are not already 23 using clang 3.5.0 or higher. 24 2520190413: 26 Now Clang 8 has been merged (see the 20190412 entry below), the ifunc 27 functionality needed for the RETPOLINE option should work properly 28 again. The RETPOLINE option has been removed from BROKEN_OPTIONS. 29 3020190412: 31 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 32 8.0.0. Please see the 20141231 entry below for information about 33 prerequisites and upgrading, if you are not already using clang 3.5.0 34 or higher. 35 3620190307: 37 The RETPOLINE option produces non-functional ifunc-using binaries 38 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS). 39 Once Clang 8 is merged it may be enabled again. 40 4120190216: 42 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 43 7.0.1. Please see the 20141231 entry below for information about 44 prerequisites and upgrading, if you are not already using clang 3.5.0 45 or higher. 46 4720190226: 48 geom_uzip(4) depends on the new module xz. If geom_uzip is statically 49 compiled into your custom kernel, add 'device xz' statement to the 50 kernel config. 51 5220190214: 53 Iflib is no longer unconditionally compiled into the kernel. Drivers 54 using iflib and statically compiled into the kernel, now require 55 the 'device iflib' config option. For the same drivers loaded as 56 modules on kernels not having 'device iflib', the iflib.ko module 57 is loaded automatically. 58 5920181228: 60 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport 61 in the same as it is applied to NFSv2 and 3. This implies that NFSv4 62 servers that have vfs.nfsd.nfs_privport set will only allow mounts 63 from clients using a reserved port#. Since both the FreeBSD and Linux 64 NFSv4 clients use reserved port#s by default, this should not affect 65 most NFSv4 mounts. 66 6720181129: 68 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld 69 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as 70 it produces broken binaries when ifuncs are in use. Users needing 71 GNU ld should install the binutils port or package. 72 7320181115: 74 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue) 75 has been converted to a port (misc/ctm) and will be removed from 76 FreeBSD-13. A depreciation warning will be printed to stderr by 77 the ctm command, but the functionality will remain in base for all 78 FreeBSD-12 releases. 79 8020181019: 81 The stable/12 branch has been created in subversion from head 82 revision r339432. 83 8420181015: 85 Ports for the DRM modules have been simplified. Now, amd64 users should 86 just install the drm-kmod port. All others should install 87 drm-legacy-kmod. 88 89 Graphics hardware that's newer than about 2010 usually works with 90 drm-kmod. For hardware older than 2013, however, some users will need 91 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older 92 than 2008 usually only works in drm-legacy-kmod. The graphics team can 93 only commit to hardware made since 2013 due to the complexity of the 94 market and difficulty to test all the older cards effectively. If you 95 have hardware supported by drm-kmod, you are strongly encouraged to use 96 that as you will get better support. 97 98 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined 99 elsewhere, the drm and drm2 modules will be eliminated from the src base 100 soon (with a limited exception for arm). Please update to the package asap 101 and report any issues to [email protected]. 102 103 Generally, anybody using the drm*-kmod packages should add 104 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty 105 cross-threading surprises, especially with automatic driver 106 loading from X11 startup. These will become the defaults in 13-current 107 shortly. 108 10920181012: 110 The ixlv(4) driver has been renamed to iavf(4). As a consequence, 111 custom kernel and module loading configuration files must be updated 112 accordingly. Moreover, interfaces previous presented as ixlvN to the 113 system are now exposed as iavfN and network configuration files must 114 be adjusted as necessary. 115 11620181009: 117 OpenSSL has been updated to version 1.1.1. This update included 118 additional various API changes througout the base system. It is 119 important to rebuild third-party software after upgrading. The value 120 of __FreeBSD_version has been bumped accordingly. 121 12220181006: 123 The legacy DRM modules and drivers have now been added to the loader's 124 module blacklist, in favor of loading them with kld_list in rc.conf(5). 125 The module blacklist may be overridden with the loader.conf(5) 126 'module_blacklist' variable, but loading them via rc.conf(5) is strongly 127 encouraged. 128 12920181002: 130 The cam(4) based nda(4) driver will be used over nvd(4) by default on 131 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or 132 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing 133 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the 134 nda device name. 135 13620180913: 137 Reproducible build mode is now on by default, in preparation for 138 FreeBSD 12.0. This eliminates build metadata such as the user, 139 host, and time from the kernel (and uname), unless the working tree 140 corresponds to a modified checkout from a version control system. 141 The previous behavior can be obtained by setting the /etc/src.conf 142 knob WITHOUT_REPRODUCIBLE_BUILD. 143 14420180826: 145 The Yarrow CSPRNG has been removed from the kernel as it has not been 146 supported by its designers since at least 2003. Fortuna has been the 147 default since FreeBSD-11. 148 14920180822: 150 devctl freeze/thaw have gone into the tree, the rc scripts have been 151 updated to use them and devmatch has been changed. You should update 152 kernel, userland and rc scripts all at the same time. 153 15420180818: 155 The default interpreter has been switched from 4th to Lua. 156 LOADER_DEFAULT_INTERP, documented in build(7), will override the default 157 interpreter. If you have custom FORTH code you will need to set 158 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in 159 src.conf for the build. This will create default hard links between 160 loader and loader_4th instead of loader and loader_lua, the new default. 161 If you are using UEFI it will create the proper hard link to loader.efi. 162 163 bhyve uses userboot.so. It remains 4th-only until some issues are solved 164 regarding coexisting with multiple versions of FreeBSD are resolved. 165 16620180815: 167 ls(1) now respects the COLORTERM environment variable used in other 168 systems and software to indicate that a colored terminal is both 169 supported and desired. If ls(1) is suddenly emitting colors, they may 170 be disabled again by either removing the unwanted COLORTERM from your 171 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR 172 may not be observed in a future release. 173 17420180808: 175 The default pager for most commands has been changed to "less". To 176 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in 177 your environment. 178 17920180731: 180 The jedec_ts(4) driver has been removed. A superset of its functionality 181 is available in the jedec_dimm(4) driver, and the manpage for that 182 driver includes migration instructions. If you have "device jedec_ts" 183 in your kernel configuration file, it must be removed. 184 18520180730: 186 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default. 187 This should have no effect if the kernel is booted via BIOS/legacy boot. 188 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system 189 has a buggy firmware that prevents a successful boot due to use of 190 runtime services. 191 19220180727: 193 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale 194 support has been removed from the tree. These ports were 195 obsolete and/or known to be broken for many years. 196 19720180723: 198 loader.efi has been augmented to participate more fully in the 199 UEFI boot manager protocol. loader.efi will now look at the 200 BootXXXX environment variable to determine if a specific kernel 201 or root partition was specified. XXXX is derived from BootCurrent. 202 efibootmgr(8) manages these standard UEFI variables. 203 20420180720: 205 zfsloader's functionality has now been folded into loader. 206 zfsloader is no longer necessary once you've updated your 207 boot blocks. For a transition period, we will install a 208 hardlink for zfsloader to loader to allow a smooth transition 209 until the boot blocks can be updated (hard link because old 210 zfs boot blocks don't understand symlinks). 211 21220180719: 213 ARM64 now have efifb support, if you want to have serial console 214 on your arm64 board when an screen is connected and the bootloader 215 setup a frambuffer for us to use, just add : 216 boot_serial=YES 217 boot_multicons=YES 218 in /boot/loader.conf 219 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have 220 an screen connected as the firmware will setup a framebuffer are that 221 u-boot will expose as an EFI framebuffer. 222 22320180719: 224 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster 225 or take steps to update /etc/passwd before doing installworld on 226 existing systems. Do not skip the "mergemaster -Fp" step before 227 installworld, as described in the update procedures near the bottom 228 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd 229 if the new mac_ntpd(4) policy is available, unless ntpd_flags or 230 the ntp config file contain options that change file/dir locations. 231 When such options (e.g., "statsdir" or "crypto") are used, ntpd can 232 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after 233 taking steps to ensure that all required files/dirs are accessible 234 by the ntpd user. 235 23620180717: 237 Big endian arm support has been removed. 238 23920180711: 240 The static environment setup in kernel configs is no longer mutually 241 exclusive with the loader(8) environment by default. In order to 242 restore the previous default behavior of disabling the loader(8) 243 environment if a static environment is present, you must specify 244 loader_env.disabled=1 in the static environment. 245 24620180705: 247 The ABI of syscalls used by management tools like sockstat and 248 netstat has been broken to allow 32-bit binaries to work on 249 64-bit kernels without modification. These programs will need 250 to match the kernel in order to function. External programs may 251 require minor modifications to accommodate a change of type in 252 structures from pointers to 64-bit virtual addresses. 253 25420180702: 255 On i386 and amd64 atomics are now inlined. Out of tree modules using 256 atomics will need to be rebuilt. 257 25820180701: 259 The '%I' format in the kern.corefile sysctl limits the number of 260 core files that a process can generate to the number stored in the 261 debug.ncores sysctl. The '%I' format is replaced by the single digit 262 index. Previously, if all indexes were taken the kernel would overwrite 263 only a core file with the highest index in a filename. 264 Currently the system will create a new core file if there is a free 265 index or if all slots are taken it will overwrite the oldest one. 266 26720180630: 268 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 269 6.0.1. Please see the 20141231 entry below for information about 270 prerequisites and upgrading, if you are not already using clang 3.5.0 271 or higher. 272 27320180628: 274 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf 275 needed to be changed to work with it. This change was made with r335763 276 and requires a mergemaster / etcupdate / etc to update the installed file. 277 27820180612: 279 r334930 changed the interface between the NFS modules, so they all 280 need to be rebuilt. r335018 did a __FreeBSD_version bump for this. 281 28220180530: 283 As of r334391 lld is the default amd64 system linker; it is installed 284 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no 285 longer necessary. 286 28720180530: 288 The kernel / userland interface for devinfo changed, so you'll 289 need a new kernel and userland as a pair for it to work (rebuilding 290 lib/libdevinfo is all that's required). devinfo and devmatch will 291 not work, but everything else will when there's a mismatch. 292 29320180523: 294 The on-disk format for hwpmc callchain records has changed to include 295 threadid corresponding to a given record. This changes the field offsets 296 and thus requires that libpmcstat be rebuilt before using a kernel 297 later than r334108. 298 29920180517: 300 The vxge(4) driver has been removed. This driver was introduced into 301 HEAD one week before the Exar left the Ethernet market and is not 302 known to be used. If you have device vxge in your kernel config file 303 it must be removed. 304 30520180510: 306 The amd64 kernel now requires a ld that supports ifunc to produce a 307 working kernel, either lld or a newer binutils. lld is built by default 308 on amd64, and the 'buildkernel' target uses it automatically. However, 309 it is not the default linker, so building the kernel the traditional 310 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for 311 binutils port/package). lld will soon be default, and this requirement 312 will go away. 313 314 NOTE: As of r334391 lld is the default system linker on amd64, and no 315 workaround is necessary. 316 31720180508: 318 The nxge(4) driver has been removed. This driver was for PCI-X 10g 319 cards made by s2io/Neterion. The company was aquired by Exar and 320 no longer sells or supports Ethernet products. If you have device 321 nxge in your kernel config file it must be removed. 322 32320180504: 324 The tz database (tzdb) has been updated to 2018e. This version more 325 correctly models time stamps in time zones with negative DST such as 326 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and 327 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only 328 time zone abbreviations and the tm_isdst flag. 329 33020180502: 331 The ixgb(4) driver has been removed. This driver was for an early and 332 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel 333 quickly shifted to the long lived ixgbe family. If you have device 334 ixgb in your kernel config file it must be removed. 335 33620180501: 337 The lmc(4) driver has been removed. This was a WAN interface 338 card that was already reportedly rare in 2003, and had an ambiguous 339 license. If you have device lmc in your kernel config file it must 340 be removed. 341 34220180413: 343 Support for Arcnet networks has been removed. If you have device 344 arcnet or device cm in your kernel config file they must be 345 removed. 346 34720180411: 348 Support for FDDI networks has been removed. If you have device 349 fddi or device fpa in your kernel config file they must be 350 removed. 351 35220180406: 353 In addition to supporting RFC 3164 formatted messages, the 354 syslogd(8) service is now capable of parsing RFC 5424 formatted 355 log messages. The main benefit of using RFC 5424 is that clients 356 may now send log messages with timestamps containing year numbers, 357 microseconds and time zone offsets. 358 359 Similarly, the syslog(3) C library function has been altered to 360 send RFC 5424 formatted messages to the local system logging 361 daemon. On systems using syslogd(8), this change should have no 362 negative impact, as long as syslogd(8) and the C library are 363 updated at the same time. On systems using a different system 364 logging daemon, it may be necessary to make configuration 365 adjustments, depending on the software used. 366 367 When using syslog-ng, add the 'syslog-protocol' flag to local 368 input sources to enable parsing of RFC 5424 formatted messages: 369 370 source src { 371 unix-dgram("/var/run/log" flags(syslog-protocol)); 372 } 373 374 When using rsyslog, disable the 'SysSock.UseSpecialParser' option 375 of the 'imuxsock' module to let messages be processed by the 376 regular RFC 3164/5424 parsing pipeline: 377 378 module(load="imuxsock" SysSock.UseSpecialParser="off") 379 380 Do note that these changes only affect communication between local 381 applications and syslogd(8). The format that syslogd(8) uses to 382 store messages on disk or forward messages to other systems 383 remains unchanged. syslogd(8) still uses RFC 3164 for these 384 purposes. Options to customize this behaviour will be added in the 385 future. Utilities that process log files stored in /var/log are 386 thus expected to continue to function as before. 387 388 __FreeBSD_version has been incremented to 1200061 to denote this 389 change. 390 39120180328: 392 Support for token ring networks has been removed. If you 393 have "device token" in your kernel config you should remove 394 it. No device drivers supported token ring. 395 39620180323: 397 makefs was modified to be able to tag ISO9660 El Torito boot catalog 398 entries as EFI instead of overloading the i386 tag as done previously. 399 The amd64 mkisoimages.sh script used to build amd64 ISO images for 400 release was updated to use this. This may mean that makefs must be 401 updated before "make cdrom" can be run in the release directory. This 402 should be as simple as: 403 404 $ cd $SRCDIR/usr.sbin/makefs 405 $ make depend all install 406 40720180212: 408 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for 409 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf. 410 Co-existance for the transition period will come shortly. Booting is a 411 complex environment and test coverage for Lua-enabled loaders has been 412 thin, so it would be prudent to assume it might not work and make 413 provisions for backup boot methods. 414 41520180211: 416 devmatch functionality has been turned on in devd. It will automatically 417 load drivers for unattached devices. This may cause unexpected drivers to 418 be loaded. Please report any problems to current@ and [email protected]. 419 42020180114: 421 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 422 6.0.0. Please see the 20141231 entry below for information about 423 prerequisites and upgrading, if you are not already using clang 3.5.0 424 or higher. 425 42620180110: 427 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker. 428 This means it is used to link the kernel and userland libraries and 429 executables, but is not yet installed as /usr/bin/ld by default. 430 431 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set 432 WITHOUT_LLD_BOOTSTRAP=yes 433 43420180110: 435 On i386, pmtimer has been removed. Its functionality has been folded 436 into apm. It was a no-op on ACPI in current for a while now (but was still 437 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it 438 from kernel config files. 439 44020180104: 441 The use of RSS hash from the network card aka flowid has been 442 disabled by default for lagg(4) as it's currently incompatible with 443 the lacp and loadbalance protocols. 444 445 This can be re-enabled by setting the following in loader.conf: 446 net.link.lagg.default_use_flowid="1" 447 44820180102: 449 The SW_WATCHDOG option is no longer necessary to enable the 450 hardclock-based software watchdog if no hardware watchdog is 451 configured. As before, SW_WATCHDOG will cause the software 452 watchdog to be enabled even if a hardware watchdog is configured. 453 45420171215: 455 r326887 fixes the issue described in the 20171214 UPDATING entry. 456 r326888 flips the switch back to building GELI support always. 457 45820171214: 459 r362593 broke ZFS + GELI support for reasons unknown. However, 460 it also broke ZFS support generally, so GELI has been turned off 461 by default as the lesser evil in r326857. If you boot off ZFS and/or 462 GELI, it might not be a good time to update. 463 46420171125: 465 PowerPC users must update loader(8) by rebuilding world before 466 installing a new kernel, as the protocol connecting them has 467 changed. Without the update, loader metadata will not be passed 468 successfully to the kernel and users will have to enter their 469 root partition at the kernel mountroot prompt to continue booting. 470 Newer versions of loader can boot old kernels without issue. 471 47220171110: 473 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to 474 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed 475 to WITH/OUT_LOADER_GELI. 476 47720171106: 478 The naive and non-compliant support of posix_fallocate(2) in ZFS 479 has been removed as of r325320. The system call now returns EINVAL 480 when used on a ZFS file. Although the new behavior complies with the 481 standard, some consumers are not prepared to cope with it. 482 One known victim is lld prior to r325420. 483 48420171102: 485 Building in a FreeBSD src checkout will automatically create object 486 directories now rather than store files in the current directory if 487 'make obj' was not ran. Calling 'make obj' is no longer necessary. 488 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in 489 /etc/src-env.conf (not /etc/src.conf), or passing the option in the 490 environment. 491 49220171101: 493 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native 494 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified 495 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old 496 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf, 497 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building. 498 The UNIFIED_OBJDIR option is a transitional feature that will be 499 removed for 12.0 release; please migrate to the new format for any 500 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather 501 than hardcoding paths. 502 50320171028: 504 The native-xtools target no longer installs the files by default to the 505 OBJDIR. Use the native-xtools-install target with a DESTDIR to install 506 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin. 507 50820171021: 509 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT 510 options are changing from controlling the build if defined / undefined 511 to controlling the build with explicit 'yes' or 'no' values. They will 512 shift to WITH/WITHOUT options to match other options in the system. 513 51420171010: 515 libstand has turned into a private library for sys/boot use only. 516 It is no longer supported as a public interface outside of sys/boot. 517 51820171005: 519 The arm port has split armv6 into armv6 and armv7. armv7 is now 520 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system 521 and are running a kernel from before r324363, you will need to add 522 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build. 523 52420171003: 525 When building multiple kernels using KERNCONF, non-existent KERNCONF 526 files will produce an error and buildkernel will fail. Previously 527 missing KERNCONF files silently failed giving no indication as to 528 why, only to subsequently discover during installkernel that the 529 desired kernel was never built in the first place. 530 53120170912: 532 The default serial number format for CTL LUNs has changed. This will 533 affect users who use /dev/diskid/* device nodes, or whose FibreChannel 534 or iSCSI clients care about their LUNs' serial numbers. Users who 535 require serial number stability should hardcode serial numbers in 536 /etc/ctl.conf . 537 53820170912: 539 For 32-bit arm compiled for hard-float support, soft-floating point 540 binaries now always get their shared libraries from 541 LD_SOFT_LIBRARY_PATH (in the past, this was only used if 542 /usr/libsoft also existed). Only users with a hard-float ld.so, but 543 soft-float everything else should be affected. 544 54520170826: 546 The geli password typed at boot is now hidden. To restore the previous 547 behavior, see geli(8) for configuration options. 548 54920170825: 550 Move PMTUD blackhole counters to TCPSTATS and remove them from bare 551 sysctl values. Minor nit, but requires a rebuild of both world/kernel 552 to complete. 553 55420170814: 555 "make check" behavior (made in ^/head@r295380) has been changed to 556 execute from a limited sandbox, as opposed to executing from 557 ${TESTSDIR}. 558 559 Behavioral changes: 560 - The "beforecheck" and "aftercheck" targets are now specified. 561 - ${CHECKDIR} (added in commit noted above) has been removed. 562 - Legacy behavior can be enabled by setting 563 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment. 564 565 If the limited sandbox mode is enabled, "make check" will execute 566 "make distribution", then install, execute the tests, and clean up the 567 sandbox if successful. 568 569 The "make distribution" and "make install" targets are typically run as 570 root to set appropriate permissions and ownership at installation time. 571 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the 572 environment if executing "make check" with limited sandbox mode using 573 an unprivileged user. 574 57520170808: 576 Since the switch to GPT disk labels, fsck for UFS/FFS has been 577 unable to automatically find alternate superblocks. As of r322297, 578 the information needed to find alternate superblocks has been 579 moved to the end of the area reserved for the boot block. 580 Filesystems created with a newfs of this vintage or later 581 will create the recovery information. If you have a filesystem 582 created prior to this change and wish to have a recovery block 583 created for your filesystem, you can do so by running fsck in 584 foreground mode (i.e., do not use the -p or -y options). As it 585 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS'' 586 to which you should answer yes. 587 58820170728: 589 As of r321665, an NFSv4 server configuration that services 590 Kerberos mounts or clients that do not support the uid/gid in 591 owner/owner_group string capability, must explicitly enable 592 the nfsuserd daemon by adding nfsuserd_enable="YES" to the 593 machine's /etc/rc.conf file. 594 59520170722: 596 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0. 597 Please see the 20141231 entry below for information about prerequisites 598 and upgrading, if you are not already using clang 3.5.0 or higher. 599 60020170701: 601 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the 602 r-commands (rlogin, rsh, etc.) to be built with the base system. 603 60420170625: 605 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is 606 a very major ABI incompatible change, so users of FreeBSD/powerpc must 607 be careful when performing source upgrades. It is best to run 608 'make installworld' from an alternate root system, either a live 609 CD/memory stick, or a temporary root partition. Additionally, all ports 610 must be recompiled. powerpc64 is largely unaffected, except in the case 611 of 32-bit compatibility. All 32-bit binaries will be affected. 612 61320170623: 614 Forward compatibility for the "ino64" project have been committed. This 615 will allow most new binaries to run on older kernels in a limited 616 fashion. This prevents many of the common foot-shooting actions in the 617 upgrade as well as the limited ability to roll back the kernel across 618 the ino64 upgrade. Complicated use cases may not work properly, though 619 enough simpler ones work to allow recovery in most situations. 620 62120170620: 622 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC 623 if you require the GPL compiler. 624 62520170618: 626 The internal ABI used for communication between the NFS kernel modules 627 was changed by r320085, so __FreeBSD_version was bumped to 628 ensure all the NFS related modules are updated together. 629 63020170617: 631 The ABI of struct event was changed by extending the data 632 member to 64bit and adding ext fields. For upgrade, same 633 precautions as for the entry 20170523 "ino64" must be 634 followed. 635 63620170531: 637 The GNU roff toolchain has been removed from base. To render manpages 638 which are not supported by mandoc(1), man(1) can fallback on GNU roff 639 from ports (and recommends to install it). 640 To render roff(7) documents, consider using GNU roff from ports or the 641 heirloom doctools roff toolchain from ports via pkg install groff or 642 via pkg install heirloom-doctools. 643 64420170524: 645 The ath(4) and ath_hal(4) modules now build piecemeal to allow for 646 smaller runtime footprint builds. This is useful for embedded systems 647 which only require one chipset support. 648 649 If you load it as a module, make sure this is in /boot/loader.conf: 650 651 if_ath_load="YES" 652 653 This will load the HAL, all chip/RF backends and if_ath_pci. 654 If you have if_ath_pci in /boot/loader.conf, ensure it is after 655 if_ath or it will not load any HAL chipset support. 656 657 If you want to selectively load things (eg on ye cheape ARM/MIPS 658 platforms where RAM is at a premium) you should: 659 660 * load ath_hal 661 * load the chip modules in question 662 * load ath_rate, ath_dfs 663 * load ath_main 664 * load if_ath_pci and/or if_ath_ahb depending upon your particular 665 bus bind type - this is where probe/attach is done. 666 667 For further comments/feedback, poke adrian@ . 668 66920170523: 670 The "ino64" 64-bit inode project has been committed, which extends 671 a number of types to 64 bits. Upgrading in place requires care and 672 adherence to the documented upgrade procedure. 673 674 If using a custom kernel configuration ensure that the 675 COMPAT_FREEBSD11 option is included (as during the upgrade the 676 system will be running the ino64 kernel with the existing world). 677 678 For the safest in-place upgrade begin by removing previous build 679 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the 680 full procedure documented below under the heading "To rebuild 681 everything and install it on the current system." Specifically, 682 a reboot is required after installing the new kernel before 683 installing world. 684 68520170424: 686 The NATM framework including the en(4), fatm(4), hatm(4), and 687 patm(4) devices has been removed. Consumers should plan a 688 migration before the end-of-life date for FreeBSD 11. 689 69020170420: 691 GNU diff has been replaced by a BSD licensed diff. Some features of GNU 692 diff has not been implemented, if those are needed a newer version of 693 GNU diff is available via the diffutils package under the gdiff name. 694 69520170413: 696 As of r316810 for ipfilter, keep frags is no longer assumed when 697 keep state is specified in a rule. r316810 aligns ipfilter with 698 documentation in man pages separating keep frags from keep state. 699 This allows keep state to be specified without forcing keep frags 700 and allows keep frags to be specified independently of keep state. 701 To maintain previous behaviour, also specify keep frags with 702 keep state (as documented in ipf.conf.5). 703 70420170407: 705 arm64 builds now use the base system LLD 4.0.0 linker by default, 706 instead of requiring that the aarch64-binutils port or package be 707 installed. To continue using aarch64-binutils, set 708 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin . 709 71020170405: 711 The UDP optimization in entry 20160818 that added the sysctl 712 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast 713 packets will no longer be treated as L3 broadcast packets. 714 71520170331: 716 Binds and sends to the loopback addresses, IPv6 and IPv4, will now 717 use any explicitly assigned loopback address available in the jail 718 instead of using the first assigned address of the jail. 719 72020170329: 721 The ctl.ko module no longer implements the iSCSI target frontend: 722 cfiscsi.ko does instead. 723 724 If building cfiscsi.ko as a kernel module, the module can be loaded 725 via one of the following methods: 726 - `cfiscsi_load="YES"` in loader.conf(5). 727 - Add `cfiscsi` to `$kld_list` in rc.conf(5). 728 - ctladm(8)/ctld(8), when compiled with iSCSI support 729 (`WITH_ISCSI=yes` in src.conf(5)) 730 731 Please see cfiscsi(4) for more details. 732 73320170316: 734 The mmcsd.ko module now additionally depends on geom_flashmap.ko. 735 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the 736 same source (previously, the dependency of mmcsd.ko on mmc.ko was 737 missing, but mmcsd.ko now will refuse to load if it is incompatible 738 with mmc.ko). 739 74020170315: 741 The syntax of ipfw(8) named states was changed to avoid ambiguity. 742 If you have used named states in the firewall rules, you need to modify 743 them after installworld and before rebooting. Now named states must 744 be prefixed with colon. 745 74620170311: 747 The old drm (sys/dev/drm/) drivers for i915 and radeon have been 748 removed as the userland we provide cannot use them. The KMS version 749 (sys/dev/drm2) supports the same hardware. 750 75120170302: 752 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0. 753 Please see the 20141231 entry below for information about prerequisites 754 and upgrading, if you are not already using clang 3.5.0 or higher. 755 75620170221: 757 The code that provides support for ZFS .zfs/ directory functionality 758 has been reimplemented. It's not possible now to create a snapshot 759 by mkdir under .zfs/snapshot/. That should be the only user visible 760 change. 761 76220170216: 763 EISA bus support has been removed. The WITH_EISA option is no longer 764 valid. 765 76620170215: 767 MCA bus support has been removed. 768 76920170127: 770 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed 771 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC. 772 77320170112: 774 The EM_MULTIQUEUE kernel configuration option is deprecated now that 775 the em(4) driver conforms to iflib specifications. 776 77720170109: 778 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via 779 IFLIB. If you have a custom kernel configuration that excludes em(4) 780 but you use igb(4), you need to re-add em(4) to your custom configuration. 781 78220161217: 783 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1. 784 Please see the 20141231 entry below for information about prerequisites 785 and upgrading, if you are not already using clang 3.5.0 or higher. 786 78720161124: 788 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0. 789 Please see the 20141231 entry below for information about prerequisites 790 and upgrading, if you are not already using clang 3.5.0 or higher. 791 79220161119: 793 The layout of the pmap structure has changed for powerpc to put the pmap 794 statistics at the front for all CPU variations. libkvm(3) and all tools 795 that link against it need to be recompiled. 796 79720161030: 798 isl(4) and cyapa(4) drivers now require a new driver, 799 chromebook_platform(4), to work properly on Chromebook-class hardware. 800 On other types of hardware the drivers may need to be configured using 801 device hints. Please see the corresponding manual pages for details. 802 80320161017: 804 The urtwn(4) driver was merged into rtwn(4) and now consists of 805 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific 806 parts. 807 Also, firmware for RTL8188CE was renamed due to possible name 808 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B)) 809 81020161015: 811 GNU rcs has been removed from base. It is available as packages: 812 - rcs: Latest GPLv3 GNU rcs version. 813 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was 814 removed from base. 815 81620161008: 817 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control 818 modules now requires that the kernel configuration contain the 819 TCP_HHOOK option. (This option is included in the GENERIC kernel.) 820 82120161003: 822 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired. 823 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy. 824 82520160924: 826 Relocatable object files with the extension of .So have been renamed 827 to use an extension of .pico instead. The purpose of this change is 828 to avoid a name clash with shared libraries on case-insensitive file 829 systems. On those file systems, foo.So is the same file as foo.so. 830 83120160918: 832 GNU rcs has been turned off by default. It can (temporarily) be built 833 again by adding WITH_RCS knob in src.conf. 834 Otherwise, GNU rcs is available from packages: 835 - rcs: Latest GPLv3 GNU rcs version. 836 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base. 837 83820160918: 839 The backup_uses_rcs functionality has been removed from rc.subr. 840 84120160908: 842 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into 843 two separate components, QUEUE_MACRO_DEBUG_TRACE and 844 QUEUE_MACRO_DEBUG_TRASH. Define both for the original 845 QUEUE_MACRO_DEBUG behavior. 846 84720160824: 848 r304787 changed some ioctl interfaces between the iSCSI userspace 849 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be 850 rebuilt to work with new kernels. __FreeBSD_version has been bumped 851 to 1200005. 852 85320160818: 854 The UDP receive code has been updated to only treat incoming UDP 855 packets that were addressed to an L2 broadcast address as L3 856 broadcast packets. It is not expected that this will affect any 857 standards-conforming UDP application. The new behaviour can be 858 disabled by setting the sysctl net.inet.udp.require_l2_bcast to 859 0. 860 86120160818: 862 Remove the openbsd_poll system call. 863 __FreeBSD_version has been bumped because of this. 864 86520160708: 866 The stable/11 branch has been created from head@r302406. 867 86820160622: 869 The libc stub for the pipe(2) system call has been replaced with 870 a wrapper that calls the pipe2(2) system call and the pipe(2) 871 system call is now only implemented by the kernels that include 872 "options COMPAT_FREEBSD10" in their config file (this is the 873 default). Users should ensure that this option is enabled in 874 their kernel or upgrade userspace to r302092 before upgrading their 875 kernel. 876 87720160527: 878 CAM will now strip leading spaces from SCSI disks' serial numbers. 879 This will affect users who create UFS filesystems on SCSI disks using 880 those disk's diskid device nodes. For example, if /etc/fstab 881 previously contained a line like 882 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should 883 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom 884 transforms like gmirror may also be affected. ZFS users should 885 generally be fine. 886 88720160523: 888 The bitstring(3) API has been updated with new functionality and 889 improved performance. But it is binary-incompatible with the old API. 890 Objects built with the new headers may not be linked against objects 891 built with the old headers. 892 89320160520: 894 The brk and sbrk functions have been removed from libc on arm64. 895 Binutils from ports has been updated to not link to these 896 functions and should be updated to the latest version before 897 installing a new libc. 898 89920160517: 900 The armv6 port now defaults to hard float ABI. Limited support 901 for running both hardfloat and soft float on the same system 902 is available using the libraries installed with -DWITH_LIBSOFT. 903 This has only been tested as an upgrade path for installworld 904 and packages may fail or need manual intervention to run. New 905 packages will be needed. 906 907 To update an existing self-hosted armv6hf system, you must add 908 TARGET_ARCH=armv6 on the make command line for both the build 909 and the install steps. 910 91120160510: 912 Kernel modules compiled outside of a kernel build now default to 913 installing to /boot/modules instead of /boot/kernel. Many kernel 914 modules built this way (such as those in ports) already overrode 915 KMODDIR explicitly to install into /boot/modules. However, 916 manually building and installing a module from /sys/modules will 917 now install to /boot/modules instead of /boot/kernel. 918 91920160414: 920 The CAM I/O scheduler has been committed to the kernel. There should be 921 no user visible impact. This does enable NCQ Trim on ada SSDs. While the 922 list of known rogues that claim support for this but actually corrupt 923 data is believed to be complete, be on the lookout for data 924 corruption. The known rogue list is believed to be complete: 925 926 o Crucial MX100, M550 drives with MU01 firmware. 927 o Micron M510 and M550 drives with MU01 firmware. 928 o Micron M500 prior to MU07 firmware 929 o Samsung 830, 840, and 850 all firmwares 930 o FCCT M500 all firmwares 931 932 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware 933 with working NCQ TRIM. For Micron branded drives, see your sales rep for 934 updated firmware. Black listed drives will work correctly because these 935 drives work correctly so long as no NCQ TRIMs are sent to them. Given 936 this list is the same as found in Linux, it's believed there are no 937 other rogues in the market place. All other models from the above 938 vendors work. 939 940 To be safe, if you are at all concerned, you can quirk each of your 941 drives to prevent NCQ from being sent by setting: 942 kern.cam.ada.X.quirks="0x2" 943 in loader.conf. If the drive requires the 4k sector quirk, set the 944 quirks entry to 0x3. 945 94620160330: 947 The FAST_DEPEND build option has been removed and its functionality is 948 now the one true way. The old mkdep(1) style of 'make depend' has 949 been removed. See 20160311 for further details. 950 95120160317: 952 Resource range types have grown from unsigned long to uintmax_t. All 953 drivers, and anything using libdevinfo, need to be recompiled. 954 95520160311: 956 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree 957 builds. It no longer runs mkdep(1) during 'make depend', and the 958 'make depend' stage can safely be skipped now as it is auto ran 959 when building 'make all' and will generate all SRCS and DPSRCS before 960 building anything else. Dependencies are gathered at compile time with 961 -MF flags kept in separate .depend files per object file. Users should 962 run 'make cleandepend' once if using -DNO_CLEAN to clean out older 963 stale .depend files. 964 96520160306: 966 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into 967 kernel modules. Therefore, if you load any kernel modules at boot time, 968 please install the boot loaders after you install the kernel, but before 969 rebooting, e.g.: 970 971 make buildworld 972 make buildkernel KERNCONF=YOUR_KERNEL_HERE 973 make installkernel KERNCONF=YOUR_KERNEL_HERE 974 make -C sys/boot install 975 <reboot in single user> 976 977 Then follow the usual steps, described in the General Notes section, 978 below. 979 98020160305: 981 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please 982 see the 20141231 entry below for information about prerequisites and 983 upgrading, if you are not already using clang 3.5.0 or higher. 984 98520160301: 986 The AIO subsystem is now a standard part of the kernel. The 987 VFS_AIO kernel option and aio.ko kernel module have been removed. 988 Due to stability concerns, asynchronous I/O requests are only 989 permitted on sockets and raw disks by default. To enable 990 asynchronous I/O requests on all file types, set the 991 vfs.aio.enable_unsafe sysctl to a non-zero value. 992 99320160226: 994 The ELF object manipulation tool objcopy is now provided by the 995 ELF Tool Chain project rather than by GNU binutils. It should be a 996 drop-in replacement, with the addition of arm64 support. The 997 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set 998 to obtain the GNU version if necessary. 999 100020160129: 1001 Building ZFS pools on top of zvols is prohibited by default. That 1002 feature has never worked safely; it's always been prone to deadlocks. 1003 Using a zvol as the backing store for a VM guest's virtual disk will 1004 still work, even if the guest is using ZFS. Legacy behavior can be 1005 restored by setting vfs.zfs.vol.recursive=1. 1006 100720160119: 1008 The NONE and HPN patches has been removed from OpenSSH. They are 1009 still available in the security/openssh-portable port. 1010 101120160113: 1012 With the addition of ypldap(8), a new _ypldap user is now required 1013 during installworld. "mergemaster -p" can be used to add the user 1014 prior to installworld, as documented in the handbook. 1015 101620151216: 1017 The tftp loader (pxeboot) now uses the option root-path directive. As a 1018 consequence it no longer looks for a pxeboot.4th file on the tftp 1019 server. Instead it uses the regular /boot infrastructure as with the 1020 other loaders. 1021 102220151211: 1023 The code to start recording plug and play data into the modules has 1024 been committed. While the old tools will properly build a new kernel, 1025 a number of warnings about "unknown metadata record 4" will be produced 1026 for an older kldxref. To avoid such warnings, make sure to rebuild 1027 the kernel toolchain (or world). Make sure that you have r292078 or 1028 later when trying to build 292077 or later before rebuilding. 1029 103020151207: 1031 Debug data files are now built by default with 'make buildworld' and 1032 installed with 'make installworld'. This facilitates debugging but 1033 requires more disk space both during the build and for the installed 1034 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes 1035 in src.conf(5). 1036 103720151130: 1038 r291527 changed the internal interface between the nfsd.ko and 1039 nfscommon.ko modules. As such, they must both be upgraded to-gether. 1040 __FreeBSD_version has been bumped because of this. 1041 104220151108: 1043 Add support for unicode collation strings leads to a change of 1044 order of files listed by ls(1) for example. To get back to the old 1045 behaviour, set LC_COLLATE environment variable to "C". 1046 1047 Databases administrators will need to reindex their databases given 1048 collation results will be different. 1049 1050 Due to a bug in install(1) it is recommended to remove the ancient 1051 locales before running make installworld. 1052 1053 rm -rf /usr/share/locale/* 1054 105520151030: 1056 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring 1057 libcrypto.so.7 or libssl.so.7 must be recompiled. 1058 105920151020: 1060 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0. 1061 Kernel modules isp_2400_multi and isp_2500_multi were removed and 1062 should be replaced with isp_2400 and isp_2500 modules respectively. 1063 106420151017: 1065 The build previously allowed using 'make -n' to not recurse into 1066 sub-directories while showing what commands would be executed, and 1067 'make -n -n' to recursively show commands. Now 'make -n' will recurse 1068 and 'make -N' will not. 1069 107020151012: 1071 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster 1072 and etcupdate will now use this file. A custom sendmail.cf is now 1073 updated via this mechanism rather than via installworld. If you had 1074 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may 1075 want to remove the exclusion or change it to "always install". 1076 /etc/mail/sendmail.cf is now managed the same way regardless of 1077 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using 1078 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior. 1079 108020151011: 1081 Compatibility shims for legacy ATA device names have been removed. 1082 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases 1083 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.* 1084 environment variables, /dev/ad* and /dev/ar* symbolic links. 1085 108620151006: 1087 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0. 1088 Please see the 20141231 entry below for information about prerequisites 1089 and upgrading, if you are not already using clang 3.5.0 or higher. 1090 109120150924: 1092 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/, 1093 and renamed from .symbols to .debug. This reduces the size requirements 1094 on the boot partition or file system and provides consistency with 1095 userland debug files. 1096 1097 When using the supported kernel installation method the 1098 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old) 1099 as is done with /boot/kernel. 1100 1101 Developers wishing to maintain the historical behavior of installing 1102 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5). 1103 110420150827: 1105 The wireless drivers had undergone changes that remove the 'parent 1106 interface' from the ifconfig -l output. The rc.d network scripts 1107 used to check presence of a parent interface in the list, so old 1108 scripts would fail to start wireless networking. Thus, etcupdate(3) 1109 or mergemaster(8) run is required after kernel update, to update your 1110 rc.d scripts in /etc. 1111 111220150827: 1113 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl' 1114 These configurations are now automatically interpreted as 1115 'scrub fragment reassemble'. 1116 111720150817: 1118 Kernel-loadable modules for the random(4) device are back. To use 1119 them, the kernel must have 1120 1121 device random 1122 options RANDOM_LOADABLE 1123 1124 kldload(8) can then be used to load random_fortuna.ko 1125 or random_yarrow.ko. Please note that due to the indirect 1126 function calls that the loadable modules need to provide, 1127 the build-in variants will be slightly more efficient. 1128 1129 The random(4) kernel option RANDOM_DUMMY has been retired due to 1130 unpopularity. It was not all that useful anyway. 1131 113220150813: 1133 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired. 1134 Control over building the ELF Tool Chain tools is now provided by 1135 the WITHOUT_TOOLCHAIN knob. 1136 113720150810: 1138 The polarity of Pulse Per Second (PPS) capture events with the 1139 uart(4) driver has been corrected. Prior to this change the PPS 1140 "assert" event corresponded to the trailing edge of a positive PPS 1141 pulse and the "clear" event was the leading edge of the next pulse. 1142 1143 As the width of a PPS pulse in a typical GPS receiver is on the 1144 order of 1 millisecond, most users will not notice any significant 1145 difference with this change. 1146 1147 Anyone who has compensated for the historical polarity reversal by 1148 configuring a negative offset equal to the pulse width will need to 1149 remove that workaround. 1150 115120150809: 1152 The default group assigned to /dev/dri entries has been changed 1153 from 'wheel' to 'video' with the id of '44'. If you want to have 1154 access to the dri devices please add yourself to the video group 1155 with: 1156 1157 # pw groupmod video -m $USER 1158 115920150806: 1160 The menu.rc and loader.rc files will now be replaced during 1161 upgrades. Please migrate local changes to menu.rc.local and 1162 loader.rc.local instead. 1163 116420150805: 1165 GNU Binutils versions of addr2line, c++filt, nm, readelf, size, 1166 strings and strip have been removed. The src.conf(5) knob 1167 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools. 1168 116920150728: 1170 As ZFS requires more kernel stack pages than is the default on some 1171 architectures e.g. i386, it now warns if KSTACK_PAGES is less than 1172 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing). 1173 1174 Please consider using 'options KSTACK_PAGES=X' where X is greater 1175 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations. 1176 117720150706: 1178 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0 1179 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by 1180 default, i.e., they will not contain "::". For example, instead 1181 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet 1182 to have a more specific match, such as different map entries for 1183 IPv6:0:0 vs IPv6:0. This change requires that configuration 1184 data (including maps, files, classes, custom ruleset, etc.) must 1185 use the same format, so make certain such configuration data is 1186 upgrading. As a very simple check search for patterns like 1187 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old 1188 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or 1189 the cf option UseCompressedIPv6Addresses. 1190 119120150630: 1192 The default kernel entropy-processing algorithm is now 1193 Fortuna, replacing Yarrow. 1194 1195 Assuming you have 'device random' in your kernel config 1196 file, the configurations allow a kernel option to override 1197 this default. You may choose *ONE* of: 1198 1199 options RANDOM_YARROW # Legacy /dev/random algorithm. 1200 options RANDOM_DUMMY # Blocking-only driver. 1201 1202 If you have neither, you get Fortuna. For most people, 1203 read no further, Fortuna will give a /dev/random that works 1204 like it always used to, and the difference will be irrelevant. 1205 1206 If you remove 'device random', you get *NO* kernel-processed 1207 entropy at all. This may be acceptable to folks building 1208 embedded systems, but has complications. Carry on reading, 1209 and it is assumed you know what you need. 1210 1211 *PLEASE* read random(4) and random(9) if you are in the 1212 habit of tweaking kernel configs, and/or if you are a member 1213 of the embedded community, wanting specific and not-usual 1214 behaviour from your security subsystems. 1215 1216 NOTE!! If you use RANDOM_DUMMY and/or have no 'device 1217 random', you will NOT have a functioning /dev/random, and 1218 many cryptographic features will not work, including SSH. 1219 You may also find strange behaviour from the random(3) set 1220 of library functions, in particular sranddev(3), srandomdev(3) 1221 and arc4random(3). The reason for this is that the KERN_ARND 1222 sysctl only returns entropy if it thinks it has some to 1223 share, and with RANDOM_DUMMY or no 'device random' this 1224 will never happen. 1225 122620150623: 1227 An additional fix for the issue described in the 20150614 sendmail 1228 entry below has been committed in revision 284717. 1229 123020150616: 1231 FreeBSD's old make (fmake) has been removed from the system. It is 1232 available as the devel/fmake port or via pkg install fmake. 1233 123420150615: 1235 The fix for the issue described in the 20150614 sendmail entry 1236 below has been committed in revision 284436. The work 1237 around described in that entry is no longer needed unless the 1238 default setting is overridden by a confDH_PARAMETERS configuration 1239 setting of '5' or pointing to a 512 bit DH parameter file. 1240 124120150614: 1242 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from 1243 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf 1244 and devel/kyua to version 0.20+ and adjust any calling code to work 1245 with Kyuafile and kyua. 1246 124720150614: 1248 The import of openssl to address the FreeBSD-SA-15:10.openssl 1249 security advisory includes a change which rejects handshakes 1250 with DH parameters below 768 bits. sendmail releases prior 1251 to 8.15.2 (not yet released), defaulted to a 512 bit 1252 DH parameter setting for client connections. To work around 1253 this interoperability, sendmail can be configured to use a 1254 2048 bit DH parameter by: 1255 1256 1. Edit /etc/mail/`hostname`.mc 1257 2. If a setting for confDH_PARAMETERS does not exist or 1258 exists and is set to a string beginning with '5', 1259 replace it with '2'. 1260 3. If a setting for confDH_PARAMETERS exists and is set to 1261 a file path, create a new file with: 1262 openssl dhparam -out /path/to/file 2048 1263 4. Rebuild the .cf file: 1264 cd /etc/mail/; make; make install 1265 5. Restart sendmail: 1266 cd /etc/mail/; make restart 1267 1268 A sendmail patch is coming, at which time this file will be 1269 updated. 1270 127120150604: 1272 Generation of legacy formatted entries have been disabled by default 1273 in pwd_mkdb(8), as all base system consumers of the legacy formatted 1274 entries were converted to use the new format by default when the new, 1275 machine independent format have been added and supported since FreeBSD 1276 5.x. 1277 1278 Please see the pwd_mkdb(8) manual page for further details. 1279 128020150525: 1281 Clang and llvm have been upgraded to 3.6.1 release. Please see the 1282 20141231 entry below for information about prerequisites and upgrading, 1283 if you are not already using 3.5.0 or higher. 1284 128520150521: 1286 TI platform code switched to using vendor DTS files and this update 1287 may break existing systems running on Beaglebone, Beaglebone Black, 1288 and Pandaboard: 1289 1290 - dtb files should be regenerated/reinstalled. Filenames are the 1291 same but content is different now 1292 - GPIO addressing was changed, now each GPIO bank (32 pins per bank) 1293 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old 1294 addressing scheme is now pin 25 on /dev/gpioc3. 1295 - Pandaboard: /etc/ttys should be updated, serial console device is 1296 now /dev/ttyu2, not /dev/ttyu0 1297 129820150501: 1299 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim. 1300 If you need the GNU extension from groff soelim(1), install groff 1301 from package: pkg install groff, or via ports: textproc/groff. 1302 130320150423: 1304 chmod, chflags, chown and chgrp now affect symlinks in -R mode as 1305 defined in symlink(7); previously symlinks were silently ignored. 1306 130720150415: 1308 The const qualifier has been removed from iconv(3) to comply with 1309 POSIX. The ports tree is aware of this from r384038 onwards. 1310 131120150416: 1312 Libraries specified by LIBADD in Makefiles must have a corresponding 1313 DPADD_<lib> variable to ensure correct dependencies. This is now 1314 enforced in src.libnames.mk. 1315 131620150324: 1317 From legacy ata(4) driver was removed support for SATA controllers 1318 supported by more functional drivers ahci(4), siis(4) and mvs(4). 1319 Kernel modules ataahci and ataadaptec were removed completely, 1320 replaced by ahci and mvs modules respectively. 1321 132220150315: 1323 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see 1324 the 20141231 entry below for information about prerequisites and 1325 upgrading, if you are not already using 3.5.0 or higher. 1326 132720150307: 1328 The 32-bit PowerPC kernel has been changed to a position-independent 1329 executable. This can only be booted with a version of loader(8) 1330 newer than January 31, 2015, so make sure to update both world and 1331 kernel before rebooting. 1332 133320150217: 1334 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014), 1335 but before r278950, the RNG was not seeded properly. Immediately 1336 upgrade the kernel to r278950 or later and regenerate any keys (e.g. 1337 ssh keys or openssl keys) that were generated w/ a kernel from that 1338 range. This does not affect programs that directly used /dev/random 1339 or /dev/urandom. All userland uses of arc4random(3) are affected. 1340 134120150210: 1342 The autofs(4) ABI was changed in order to restore binary compatibility 1343 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work 1344 with the new kernel. 1345 134620150131: 1347 The powerpc64 kernel has been changed to a position-independent 1348 executable. This can only be booted with a new version of loader(8), 1349 so make sure to update both world and kernel before rebooting. 1350 135120150118: 1352 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix 1353 only release, no new features have been added. Please see the 20141231 1354 entry below for information about prerequisites and upgrading, if you 1355 are not already using 3.5.0. 1356 135720150107: 1358 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now 1359 taken from the ELF Tool Chain project rather than GNU binutils. They 1360 should be drop-in replacements, with the addition of arm64 support. 1361 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the 1362 binutils tools, if necessary. See 20150805 for updated information. 1363 136420150105: 1365 The default Unbound configuration now enables remote control 1366 using a local socket. Users who have already enabled the 1367 local_unbound service should regenerate their configuration 1368 by running "service local_unbound setup" as root. 1369 137020150102: 1371 The GNU texinfo and GNU info pages have been removed. 1372 To be able to view GNU info pages please install texinfo from ports. 1373 137420141231: 1375 Clang, llvm and lldb have been upgraded to 3.5.0 release. 1376 1377 As of this release, a prerequisite for building clang, llvm and lldb is 1378 a C++11 capable compiler and C++11 standard library. This means that to 1379 be able to successfully build the cross-tools stage of buildworld, with 1380 clang as the bootstrap compiler, your system compiler or cross compiler 1381 should either be clang 3.3 or later, or gcc 4.8 or later, and your 1382 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or 1383 later. 1384 1385 On any standard FreeBSD 10.x or 11.x installation, where clang and 1386 libc++ are on by default (that is, on x86 or arm), this should work out 1387 of the box. 1388 1389 On 9.x installations where clang is enabled by default, e.g. on x86 and 1390 powerpc, libc++ will not be enabled by default, so libc++ should be 1391 built (with clang) and installed first. If both clang and libc++ are 1392 missing, build clang first, then use it to build libc++. 1393 1394 On 8.x and earlier installations, upgrade to 9.x first, and then follow 1395 the instructions for 9.x above. 1396 1397 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by 1398 default, and do not build clang. 1399 1400 Many embedded systems are resource constrained, and will not be able to 1401 build clang in a reasonable time, or in some cases at all. In those 1402 cases, cross building bootable systems on amd64 is a workaround. 1403 1404 This new version of clang introduces a number of new warnings, of which 1405 the following are most likely to appear: 1406 1407 -Wabsolute-value 1408 1409 This warns in two cases, for both C and C++: 1410 * When the code is trying to take the absolute value of an unsigned 1411 quantity, which is effectively a no-op, and almost never what was 1412 intended. The code should be fixed, if at all possible. If you are 1413 sure that the unsigned quantity can be safely cast to signed, without 1414 loss of information or undefined behavior, you can add an explicit 1415 cast, or disable the warning. 1416 1417 * When the code is trying to take an absolute value, but the called 1418 abs() variant is for the wrong type, which can lead to truncation. 1419 If you want to disable the warning instead of fixing the code, please 1420 make sure that truncation will not occur, or it might lead to unwanted 1421 side-effects. 1422 1423 -Wtautological-undefined-compare and 1424 -Wundefined-bool-conversion 1425 1426 These warn when C++ code is trying to compare 'this' against NULL, while 1427 'this' should never be NULL in well-defined C++ code. However, there is 1428 some legacy (pre C++11) code out there, which actively abuses this 1429 feature, which was less strictly defined in previous C++ versions. 1430 1431 Squid and openjdk do this, for example. The warning can be turned off 1432 for C++98 and earlier, but compiling the code in C++11 mode might result 1433 in unexpected behavior; for example, the parts of the program that are 1434 unreachable could be optimized away. 1435 143620141222: 1437 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER) 1438 kernel sources have been removed. The .h files remain, since some 1439 utilities include them. This will need to be fixed later. 1440 If "mount -t oldnfs ..." is attempted, it will fail. 1441 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used, 1442 the utilities will report errors. 1443 144420141121: 1445 The handling of LOCAL_LIB_DIRS has been altered to skip addition of 1446 directories to top level SUBDIR variable when their parent 1447 directory is included in LOCAL_DIRS. Users with build systems with 1448 such hierarchies and without SUBDIR entries in the parent 1449 directory Makefiles should add them or add the directories to 1450 LOCAL_DIRS. 1451 145220141109: 1453 faith(4) and faithd(8) have been removed from the base system. Faith 1454 has been obsolete for a very long time. 1455 145620141104: 1457 vt(4), the new console driver, is enabled by default. It brings 1458 support for Unicode and double-width characters, as well as 1459 support for UEFI and integration with the KMS kernel video 1460 drivers. 1461 1462 You may need to update your console settings in /etc/rc.conf, 1463 most probably the keymap. During boot, /etc/rc.d/syscons will 1464 indicate what you need to do. 1465 1466 vt(4) still has issues and lacks some features compared to 1467 syscons(4). See the wiki for up-to-date information: 1468 https://wiki.freebsd.org/Newcons 1469 1470 If you want to keep using syscons(4), you can do so by adding 1471 the following line to /boot/loader.conf: 1472 kern.vty=sc 1473 147420141102: 1475 pjdfstest has been integrated into kyua as an opt-in test suite. 1476 Please see share/doc/pjdfstest/README for more details on how to 1477 execute it. 1478 147920141009: 1480 gperf has been removed from the base system for architectures 1481 that use clang. Ports that require gperf will obtain it from the 1482 devel/gperf port. 1483 148420140923: 1485 pjdfstest has been moved from tools/regression/pjdfstest to 1486 contrib/pjdfstest . 1487 148820140922: 1489 At svn r271982, The default linux compat kernel ABI has been adjusted 1490 to 2.6.18 in support of the linux-c6 compat ports infrastructure 1491 update. If you wish to continue using the linux-f10 compat ports, 1492 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are 1493 encouraged to update their linux-compat packages to linux-c6 during 1494 their next update cycle. 1495 149620140729: 1497 The ofwfb driver, used to provide a graphics console on PowerPC when 1498 using vt(4), no longer allows mmap() of all physical memory. This 1499 will prevent Xorg on PowerPC with some ATI graphics cards from 1500 initializing properly unless x11-servers/xorg-server is updated to 1501 1.12.4_8 or newer. 1502 150320140723: 1504 The xdev targets have been converted to using TARGET and 1505 TARGET_ARCH instead of XDEV and XDEV_ARCH. 1506 150720140719: 1508 The default unbound configuration has been modified to address 1509 issues with reverse lookups on networks that use private 1510 address ranges. If you use the local_unbound service, run 1511 "service local_unbound setup" as root to regenerate your 1512 configuration, then "service local_unbound reload" to load the 1513 new configuration. 1514 151520140709: 1516 The GNU texinfo and GNU info pages are not built and installed 1517 anymore, WITH_INFO knob has been added to allow to built and install 1518 them again. 1519 UPDATE: see 20150102 entry on texinfo's removal 1520 152120140708: 1522 The GNU readline library is now an INTERNALLIB - that is, it is 1523 statically linked into consumers (GDB and variants) in the base 1524 system, and the shared library is no longer installed. The 1525 devel/readline port is available for third party software that 1526 requires readline. 1527 152820140702: 1529 The Itanium architecture (ia64) has been removed from the list of 1530 known architectures. This is the first step in the removal of the 1531 architecture. 1532 153320140701: 1534 Commit r268115 has added NFSv4.1 server support, merged from 1535 projects/nfsv4.1-server. Since this includes changes to the 1536 internal interfaces between the NFS related modules, a full 1537 build of the kernel and modules will be necessary. 1538 __FreeBSD_version has been bumped. 1539 154020140629: 1541 The WITHOUT_VT_SUPPORT kernel config knob has been renamed 1542 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning 1543 which differs from the behaviour controlled by this knob.) 1544 154520140619: 1546 Maximal length of the serial number in CTL was increased from 16 to 1547 64 chars, that breaks ABI. All CTL-related tools, such as ctladm 1548 and ctld, need to be rebuilt to work with a new kernel. 1549 155020140606: 1551 The libatf-c and libatf-c++ major versions were downgraded to 0 and 1552 1 respectively to match the upstream numbers. They were out of 1553 sync because, when they were originally added to FreeBSD, the 1554 upstream versions were not respected. These libraries are private 1555 and not yet built by default, so renumbering them should be a 1556 non-issue. However, unclean source trees will yield broken test 1557 programs once the operator executes "make delete-old-libs" after a 1558 "make installworld". 1559 1560 Additionally, the atf-sh binary was made private by moving it into 1561 /usr/libexec/. Already-built shell test programs will keep the 1562 path to the old binary so they will break after "make delete-old" 1563 is run. 1564 1565 If you are using WITH_TESTS=yes (not the default), wipe the object 1566 tree and rebuild from scratch to prevent spurious test failures. 1567 This is only needed once: the misnumbered libraries and misplaced 1568 binaries have been added to OptionalObsoleteFiles.inc so they will 1569 be removed during a clean upgrade. 1570 157120140512: 1572 Clang and llvm have been upgraded to 3.4.1 release. 1573 157420140508: 1575 We bogusly installed src.opts.mk in /usr/share/mk. This file should 1576 be removed to avoid issues in the future (and has been added to 1577 ObsoleteFiles.inc). 1578 157920140505: 1580 /etc/src.conf now affects only builds of the FreeBSD src tree. In the 1581 past, it affected all builds that used the bsd.*.mk files. The old 1582 behavior was a bug, but people may have relied upon it. To get this 1583 behavior back, you can .include /etc/src.conf from /etc/make.conf 1584 (which is still global and isn't changed). This also changes the 1585 behavior of incremental builds inside the tree of individual 1586 directories. Set MAKESYSPATH to ".../share/mk" to do that. 1587 Although this has survived make universe and some upgrade scenarios, 1588 other upgrade scenarios may have broken. At least one form of 1589 temporary breakage was fixed with MAKESYSPATH settings for buildworld 1590 as well... In cases where MAKESYSPATH isn't working with this 1591 setting, you'll need to set it to the full path to your tree. 1592 1593 One side effect of all this cleaning up is that bsd.compiler.mk 1594 is no longer implicitly included by bsd.own.mk. If you wish to 1595 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk 1596 as well. 1597 159820140430: 1599 The lindev device has been removed since /dev/full has been made a 1600 standard device. __FreeBSD_version has been bumped. 1601 160220140424: 1603 The knob WITHOUT_VI was added to the base system, which controls 1604 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1) 1605 in order to reorder files share/termcap and didn't build ex(1) as a 1606 build tool, so building/installing with WITH_VI is highly advised for 1607 build hosts for older releases. 1608 1609 This issue has been fixed in stable/9 and stable/10 in r277022 and 1610 r276991, respectively. 1611 161220140418: 1613 The YES_HESIOD knob has been removed. It has been obsolete for 1614 a decade. Please move to using WITH_HESIOD instead or your builds 1615 will silently lack HESIOD. 1616 161720140405: 1618 The uart(4) driver has been changed with respect to its handling 1619 of the low-level console. Previously the uart(4) driver prevented 1620 any process from changing the baudrate or the CLOCAL and HUPCL 1621 control flags. By removing the restrictions, operators can make 1622 changes to the serial console port without having to reboot. 1623 However, when getty(8) is started on the serial device that is 1624 associated with the low-level console, a misconfigured terminal 1625 line in /etc/ttys will now have a real impact. 1626 Before upgrading the kernel, make sure that /etc/ttys has the 1627 serial console device configured as 3wire without baudrate to 1628 preserve the previous behaviour. E.g: 1629 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure 1630 163120140306: 1632 Support for libwrap (TCP wrappers) in rpcbind was disabled by default 1633 to improve performance. To re-enable it, if needed, run rpcbind 1634 with command line option -W. 1635 163620140226: 1637 Switched back to the GPL dtc compiler due to updates in the upstream 1638 dts files not being supported by the BSDL dtc compiler. You will need 1639 to rebuild your kernel toolchain to pick up the new compiler. Core dumps 1640 may result while building dtb files during a kernel build if you fail 1641 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler. 1642 164320140216: 1644 Clang and llvm have been upgraded to 3.4 release. 1645 164620140216: 1647 The nve(4) driver has been removed. Please use the nfe(4) driver 1648 for NVIDIA nForce MCP Ethernet adapters instead. 1649 165020140212: 1651 An ABI incompatibility crept into the libc++ 3.4 import in r261283. 1652 This could cause certain C++ applications using shared libraries built 1653 against the previous version of libc++ to crash. The incompatibility 1654 has now been fixed, but any C++ applications or shared libraries built 1655 between r261283 and r261801 should be recompiled. 1656 165720140204: 1658 OpenSSH will now ignore errors caused by kernel lacking of Capsicum 1659 capability mode support. Please note that enabling the feature in 1660 kernel is still highly recommended. 1661 166220140131: 1663 OpenSSH is now built with sandbox support, and will use sandbox as 1664 the default privilege separation method. This requires Capsicum 1665 capability mode support in kernel. 1666 166720140128: 1668 The libelf and libdwarf libraries have been updated to newer 1669 versions from upstream. Shared library version numbers for 1670 these two libraries were bumped. Any ports or binaries 1671 requiring these two libraries should be recompiled. 1672 __FreeBSD_version is bumped to 1100006. 1673 167420140110: 1675 If a Makefile in a tests/ directory was auto-generating a Kyuafile 1676 instead of providing an explicit one, this would prevent such 1677 Makefile from providing its own Kyuafile in the future during 1678 NO_CLEAN builds. This has been fixed in the Makefiles but manual 1679 intervention is needed to clean an objdir if you use NO_CLEAN: 1680 # find /usr/obj -name Kyuafile | xargs rm -f 1681 168220131213: 1683 The behavior of gss_pseudo_random() for the krb5 mechanism 1684 has changed, for applications requesting a longer random string 1685 than produced by the underlying enctype's pseudo-random() function. 1686 In particular, the random string produced from a session key of 1687 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will 1688 be different at the 17th octet and later, after this change. 1689 The counter used in the PRF+ construction is now encoded as a 1690 big-endian integer in accordance with RFC 4402. 1691 __FreeBSD_version is bumped to 1100004. 1692 169320131108: 1694 The WITHOUT_ATF build knob has been removed and its functionality 1695 has been subsumed into the more generic WITHOUT_TESTS. If you were 1696 using the former to disable the build of the ATF libraries, you 1697 should change your settings to use the latter. 1698 169920131025: 1700 The default version of mtree is nmtree which is obtained from 1701 NetBSD. The output is generally the same, but may vary 1702 slightly. If you found you need identical output adding 1703 "-F freebsd9" to the command line should do the trick. For the 1704 time being, the old mtree is available as fmtree. 1705 170620131014: 1707 libbsdyml has been renamed to libyaml and moved to /usr/lib/private. 1708 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg 1709 1.1.4_8 and verify bsdyml not linked in, before running "make 1710 delete-old-libs": 1711 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean 1712 or 1713 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml 1714 171520131010: 1716 The stable/10 branch has been created in subversion from head 1717 revision r256279. 1718 1719COMMON ITEMS: 1720 1721 General Notes 1722 ------------- 1723 Avoid using make -j when upgrading. While generally safe, there are 1724 sometimes problems using -j to upgrade. If your upgrade fails with 1725 -j, please try again without -j. From time to time in the past there 1726 have been problems using -j with buildworld and/or installworld. This 1727 is especially true when upgrading between "distant" versions (eg one 1728 that cross a major release boundary or several minor releases, or when 1729 several months have passed on the -current branch). 1730 1731 Sometimes, obscure build problems are the result of environment 1732 poisoning. This can happen because the make utility reads its 1733 environment when searching for values for global variables. To run 1734 your build attempts in an "environmental clean room", prefix all make 1735 commands with 'env -i '. See the env(1) manual page for more details. 1736 1737 When upgrading from one major version to another it is generally best to 1738 upgrade to the latest code in the currently installed branch first, then 1739 do an upgrade to the new branch. This is the best-tested upgrade path, 1740 and has the highest probability of being successful. Please try this 1741 approach if you encounter problems with a major version upgrade. Since 1742 the stable 4.x branch point, one has generally been able to upgrade from 1743 anywhere in the most recent stable branch to head / current (or even the 1744 last couple of stable branches). See the top of this file when there's 1745 an exception. 1746 1747 When upgrading a live system, having a root shell around before 1748 installing anything can help undo problems. Not having a root shell 1749 around can lead to problems if pam has changed too much from your 1750 starting point to allow continued authentication after the upgrade. 1751 1752 This file should be read as a log of events. When a later event changes 1753 information of a prior event, the prior event should not be deleted. 1754 Instead, a pointer to the entry with the new information should be 1755 placed in the old entry. Readers of this file should also sanity check 1756 older entries before relying on them blindly. Authors of new entries 1757 should write them with this in mind. 1758 1759 ZFS notes 1760 --------- 1761 When upgrading the boot ZFS pool to a new version, always follow 1762 these two steps: 1763 1764 1.) recompile and reinstall the ZFS boot loader and boot block 1765 (this is part of "make buildworld" and "make installworld") 1766 1767 2.) update the ZFS boot block on your boot drive 1768 1769 The following example updates the ZFS boot block on the first 1770 partition (freebsd-boot) of a GPT partitioned drive ada0: 1771 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0" 1772 1773 Non-boot pools do not need these updates. 1774 1775 To build a kernel 1776 ----------------- 1777 If you are updating from a prior version of FreeBSD (even one just 1778 a few days old), you should follow this procedure. It is the most 1779 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 1780 1781 make kernel-toolchain 1782 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1783 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1784 1785 To test a kernel once 1786 --------------------- 1787 If you just want to boot a kernel once (because you are not sure 1788 if it works, or if you want to boot a known bad kernel to provide 1789 debugging information) run 1790 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 1791 nextboot -k testkernel 1792 1793 To rebuild everything and install it on the current system. 1794 ----------------------------------------------------------- 1795 # Note: sometimes if you are running current you gotta do more than 1796 # is listed here if you are upgrading from a really old current. 1797 1798 <make sure you have good level 0 dumps> 1799 make buildworld 1800 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1801 make installkernel KERNCONF=YOUR_KERNEL_HERE 1802 [1] 1803 <reboot in single user> [3] 1804 mergemaster -Fp [5] 1805 make installworld 1806 mergemaster -Fi [4] 1807 make delete-old [6] 1808 <reboot> 1809 1810 To cross-install current onto a separate partition 1811 -------------------------------------------------- 1812 # In this approach we use a separate partition to hold 1813 # current's root, 'usr', and 'var' directories. A partition 1814 # holding "/", "/usr" and "/var" should be about 2GB in 1815 # size. 1816 1817 <make sure you have good level 0 dumps> 1818 <boot into -stable> 1819 make buildworld 1820 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1821 <maybe newfs current's root partition> 1822 <mount current's root partition on directory ${CURRENT_ROOT}> 1823 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC 1824 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1825 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1826 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1827 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1828 <reboot into current> 1829 <do a "native" rebuild/install as described in the previous section> 1830 <maybe install compatibility libraries from ports/misc/compat*> 1831 <reboot> 1832 1833 1834 To upgrade in-place from stable to current 1835 ---------------------------------------------- 1836 <make sure you have good level 0 dumps> 1837 make buildworld [9] 1838 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1839 make installkernel KERNCONF=YOUR_KERNEL_HERE 1840 [1] 1841 <reboot in single user> [3] 1842 mergemaster -Fp [5] 1843 make installworld 1844 mergemaster -Fi [4] 1845 make delete-old [6] 1846 <reboot> 1847 1848 Make sure that you've read the UPDATING file to understand the 1849 tweaks to various things you need. At this point in the life 1850 cycle of current, things change often and you are on your own 1851 to cope. The defaults can also change, so please read ALL of 1852 the UPDATING entries. 1853 1854 Also, if you are tracking -current, you must be subscribed to 1855 [email protected]. Make sure that before you update 1856 your sources that you have read and understood all the recent 1857 messages there. If in doubt, please track -stable which has 1858 much fewer pitfalls. 1859 1860 [1] If you have third party modules, such as vmware, you 1861 should disable them at this point so they don't crash your 1862 system on reboot. 1863 1864 [3] From the bootblocks, boot -s, and then do 1865 fsck -p 1866 mount -u / 1867 mount -a 1868 cd src 1869 adjkerntz -i # if CMOS is wall time 1870 Also, when doing a major release upgrade, it is required that 1871 you boot into single user mode to do the installworld. 1872 1873 [4] Note: This step is non-optional. Failure to do this step 1874 can result in a significant reduction in the functionality of the 1875 system. Attempting to do it by hand is not recommended and those 1876 that pursue this avenue should read this file carefully, as well 1877 as the archives of freebsd-current and freebsd-hackers mailing lists 1878 for potential gotchas. The -U option is also useful to consider. 1879 See mergemaster(8) for more information. 1880 1881 [5] Usually this step is a no-op. However, from time to time 1882 you may need to do this if you get unknown user in the following 1883 step. It never hurts to do it all the time. You may need to 1884 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1885 install) after the buildworld before this step if you last updated 1886 from current before 20130425 or from -stable before 20130430. 1887 1888 [6] This only deletes old files and directories. Old libraries 1889 can be deleted by "make delete-old-libs", but you have to make 1890 sure that no program is using those libraries anymore. 1891 1892 [8] The new kernel must be able to run existing binaries used by 1893 an installworld. When upgrading across major versions, the new 1894 kernel's configuration must include the correct COMPAT_FREEBSD<n> 1895 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x 1896 binaries). Failure to do so may leave you with a system that is 1897 hard to boot to recover. A GENERIC kernel will include suitable 1898 compatibility options to run binaries from older branches. 1899 1900 Make sure that you merge any new devices from GENERIC since the 1901 last time you updated your kernel config file. 1902 1903 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1904 "?=" instead of the "=" assignment operator, so that buildworld can 1905 override the CPUTYPE if it needs to. 1906 1907 MAKEOBJDIRPREFIX must be defined in an environment variable, and 1908 not on the command line, or in /etc/make.conf. buildworld will 1909 warn if it is improperly defined. 1910FORMAT: 1911 1912This file contains a list, in reverse chronological order, of major 1913breakages in tracking -current. It is not guaranteed to be a complete 1914list of such breakages, and only contains entries since September 23, 2011. 1915If you need to see UPDATING entries from before that date, you will need 1916to fetch an UPDATING file from an older FreeBSD release. 1917 1918Copyright information: 1919 1920Copyright 1998-2009 M. Warner Losh. All Rights Reserved. 1921 1922Redistribution, publication, translation and use, with or without 1923modification, in full or in part, in any form or format of this 1924document are permitted without further permission from the author. 1925 1926THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1927IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1928WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1929DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1930INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1931(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1932SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1933HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1934STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1935IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1936POSSIBILITY OF SUCH DAMAGE. 1937 1938Contact Warner Losh if you have any questions about your use of 1939this document. 1940 1941$FreeBSD$ 1942