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