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