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