1Updating 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 http://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 from 17older version of current across the gcc/clang cutover is a bit fragile. 18 19NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW: 20 FreeBSD 11.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 3420140512: 35 Clang and llvm have been upgraded to 3.4.1 release. 36 3720140508: 38 We bogusly installed src.opts.mk in /usr/share/mk. This file should 39 be removed to avoid issues in the future (and has been added to 40 ObsoleteFiles.inc). 41 4220140505: 43 /etc/src.conf now affects only builds of the FreeBSD src tree. In the 44 past, it affected all builds that used the bsd.*.mk files. The old 45 behavior was a bug, but people may have relied upon it. To get this 46 behavior back, you can .include /etc/src.conf from /etc/make.conf 47 (which is still global and isn't changed). This also changes the 48 behavior of incremental builds inside the tree of individual 49 directories. Set MAKESYSPATH to ".../share/mk" to do that. 50 Although this has survived make universe and some upgrade scenarios, 51 other upgrade scenarios may have broken. At least one form of 52 temporary breakage was fixed with MAKESYSPATH settings for buildworld 53 as well... 54 55 One side effect of all this cleaning up is that bsd.compiler.mk 56 is no longer implicitly included by bsd.own.mk. If you wish to 57 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk 58 as well. 59 6020140430: 61 The lindev device has been removed since /dev/full has been made a 62 standard device. __FreeBSD_version has been bumped. 63 6420140418: 65 The YES_HESIOD knob has been removed. It has been obsolete for 66 a decade. Please move to using WITH_HESIOD instead or your builds 67 will silently lack HESIOD. 68 6920140405: 70 The uart(4) driver has been changed with respect to its handling 71 of the low-level console. Previously the uart(4) driver prevented 72 any process from changing the baudrate or the CLOCAL and HUPCL 73 control flags. By removing the restrictions, operators can make 74 changes to the serial console port without having to reboot. 75 However, when getty(8) is started on the serial device that is 76 associated with the low-level console, a misconfigured terminal 77 line in /etc/ttys will now have a real impact. 78 Before upgrading the kernel, make sure that /etc/ttys has the 79 serial console device configured as 3wire without baudrate to 80 preserve the previous behaviour. E.g: 81 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure 82 8320140306: 84 Support for libwrap (TCP wrappers) in rpcbind was disabled by default 85 to improve performance. To re-enable it, if needed, run rpcbind 86 with command line option -W. 87 8820140226: 89 Switched back to the GPL dtc compiler due to updates in the upstream 90 dts files not being supported by the BSDL dtc compiler. You will need 91 to rebuild your kernel toolchain to pick up the new compiler. Core dumps 92 may result while building dtb files during a kernel build if you fail 93 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler. 94 9520140216: 96 Clang and llvm have been upgraded to 3.4 release. 97 9820140216: 99 The nve(4) driver has been removed. Please use the nfe(4) driver 100 for NVIDIA nForce MCP Ethernet adapters instead. 101 10220140212: 103 An ABI incompatibility crept into the libc++ 3.4 import in r261283. 104 This could cause certain C++ applications using shared libraries built 105 against the previous version of libc++ to crash. The incompatibility 106 has now been fixed, but any C++ applications or shared libraries built 107 between r261283 and r261801 should be recompiled. 108 10920140204: 110 OpenSSH will now ignore errors caused by kernel lacking of Capsicum 111 capability mode support. Please note that enabling the feature in 112 kernel is still highly recommended. 113 11420140131: 115 OpenSSH is now built with sandbox support, and will use sandbox as 116 the default privilege separation method. This requires Capsicum 117 capability mode support in kernel. 118 11920140128: 120 The libelf and libdwarf libraries have been updated to newer 121 versions from upstream. Shared library version numbers for 122 these two libraries were bumped. Any ports or binaries 123 requiring these two libraries should be recompiled. 124 __FreeBSD_version is bumped to 1100006. 125 12620140110: 127 If a Makefile in a tests/ directory was auto-generating a Kyuafile 128 instead of providing an explicit one, this would prevent such 129 Makefile from providing its own Kyuafile in the future during 130 NO_CLEAN builds. This has been fixed in the Makefiles but manual 131 intervention is needed to clean an objdir if you use NO_CLEAN: 132 # find /usr/obj -name Kyuafile | xargs rm -f 133 13420131213: 135 The behavior of gss_pseudo_random() for the krb5 mechanism 136 has changed, for applications requesting a longer random string 137 than produced by the underlying enctype's pseudo-random() function. 138 In particular, the random string produced from a session key of 139 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will 140 be different at the 17th octet and later, after this change. 141 The counter used in the PRF+ construction is now encoded as a 142 big-endian integer in accordance with RFC 4402. 143 __FreeBSD_version is bumped to 1100004. 144 14520131108: 146 The WITHOUT_ATF build knob has been removed and its functionality 147 has been subsumed into the more generic WITHOUT_TESTS. If you were 148 using the former to disable the build of the ATF libraries, you 149 should change your settings to use the latter. 150 15120131025: 152 The default version of mtree is nmtree which is obtained from 153 NetBSD. The output is generally the same, but may vary 154 slightly. If you found you need identical output adding 155 "-F freebsd9" to the command line should do the trick. For the 156 time being, the old mtree is available as fmtree. 157 15820131014: 159 libbsdyml has been renamed to libyaml and moved to /usr/lib/private. 160 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg 161 1.1.4_8 and verify bsdyml not linked in, before running "make 162 delete-old-libs": 163 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean 164 or 165 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml 166 16720131010: 168 The rc.d/jail script has been updated to support jail(8) 169 configuration file. The "jail_<jname>_*" rc.conf(5) variables 170 for per-jail configuration are automatically converted to 171 /var/run/jail.<jname>.conf before the jail(8) utility is invoked. 172 This is transparently backward compatible. See below about some 173 incompatibilities and rc.conf(5) manual page for more details. 174 175 These variables are now deprecated in favor of jail(8) configuration 176 file. One can use "rc.d/jail config <jname>" command to generate 177 a jail(8) configuration file in /var/run/jail.<jname>.conf without 178 running the jail(8) utility. The default pathname of the 179 configuration file is /etc/jail.conf and can be specified by 180 using $jail_conf or $jail_<jname>_conf variables. 181 182 Please note that jail_devfs_ruleset accepts an integer at 183 this moment. Please consider to rewrite the ruleset name 184 with an integer. 185 18620130930: 187 BIND has been removed from the base system. If all you need 188 is a local resolver, simply enable and start the local_unbound 189 service instead. Otherwise, several versions of BIND are 190 available in the ports tree. The dns/bind99 port is one example. 191 192 With this change, nslookup(1) and dig(1) are no longer in the base 193 system. Users should instead use host(1) and drill(1) which are 194 in the base system. Alternatively, nslookup and dig can 195 be obtained by installing the dns/bind-tools port. 196 19720130916: 198 With the addition of unbound(8), a new unbound user is now 199 required during installworld. "mergemaster -p" can be used to 200 add the user prior to installworld, as documented in the handbook. 201 20220130911: 203 OpenSSH is now built with DNSSEC support, and will by default 204 silently trust signed SSHFP records. This can be controlled with 205 the VerifyHostKeyDNS client configuration setting. DNSSEC support 206 can be disabled entirely with the WITHOUT_LDNS option in src.conf. 207 20820130906: 209 The GNU Compiler Collection and C++ standard library (libstdc++) 210 are no longer built by default on platforms where clang is the system 211 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX 212 options in src.conf. 213 21420130905: 215 The PROCDESC kernel option is now part of the GENERIC kernel 216 configuration and is required for the rwhod(8) to work. 217 If you are using custom kernel configuration, you should include 218 'options PROCDESC'. 219 22020130905: 221 The API and ABI related to the Capsicum framework was modified 222 in backward incompatible way. The userland libraries and programs 223 have to be recompiled to work with the new kernel. This includes the 224 following libraries and programs, but the whole buildworld is 225 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl, 226 kdump, procstat, rwho, rwhod, uniq. 227 22820130903: 229 AES-NI intrinsic support has been added to gcc. The AES-NI module 230 has been updated to use this support. A new gcc is required to build 231 the aesni module on both i386 and amd64. 232 23320130821: 234 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices. 235 Thus "device padlock_rng" and "device rdrand_rng" should be 236 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG". 237 23820130813: 239 WITH_ICONV has been split into two feature sets. WITH_ICONV now 240 enables just the iconv* functionality and is now on by default. 241 WITH_LIBICONV_COMPAT enables the libiconv api and link time 242 compatability. Set WITHOUT_ICONV to build the old way. 243 If you have been using WITH_ICONV before, you will very likely 244 need to turn on WITH_LIBICONV_COMPAT. 245 24620130806: 247 INVARIANTS option now enables DEBUG for code with OpenSolaris and 248 Illumos origin, including ZFS. If you have INVARIANTS in your 249 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG 250 explicitly. 251 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS) 252 locks if WITNESS option was set. Because that generated a lot of 253 witness(9) reports and all of them were believed to be false 254 positives, this is no longer done. New option OPENSOLARIS_WITNESS 255 can be used to achieve the previous behavior. 256 25720130806: 258 Timer values in IPv6 data structures now use time_uptime instead 259 of time_second. Although this is not a user-visible functional 260 change, userland utilities which directly use them---ndp(8), 261 rtadvd(8), and rtsold(8) in the base system---need to be updated 262 to r253970 or later. 263 26420130802: 265 find -delete can now delete the pathnames given as arguments, 266 instead of only files found below them or if the pathname did 267 not contain any slashes. Formerly, the following error message 268 would result: 269 270 find: -delete: <path>: relative path potentially not safe 271 272 Deleting the pathnames given as arguments can be prevented 273 without error messages using -mindepth 1 or by changing 274 directory and passing "." as argument to find. This works in the 275 old as well as the new version of find. 276 27720130726: 278 Behavior of devfs rules path matching has been changed. 279 Pattern is now always matched against fully qualified devfs 280 path and slash characters must be explicitly matched by 281 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs 282 subdirectories must be reviewed. 283 28420130716: 285 The default ARM ABI has changed to the ARM EABI. The old ABI is 286 incompatible with the ARM EABI and all programs and modules will 287 need to be rebuilt to work with a new kernel. 288 289 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set. 290 291 NOTE: Support for the old ABI will be removed in the future and 292 users are advised to upgrade. 293 29420130709: 295 pkg_install has been disconnected from the build if you really need it 296 you should add WITH_PKGTOOLS in your src.conf(5). 297 29820130709: 299 Most of network statistics structures were changed to be able 300 keep 64-bits counters. Thus all tools, that work with networking 301 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.) 302 30320130629: 304 Fix targets that run multiple make's to use && rather than ; 305 so that subsequent steps depend on success of previous. 306 307 NOTE: if building 'universe' with -j* on stable/8 or stable/9 308 it would be better to start the build using bmake, to avoid 309 overloading the machine. 310 31120130618: 312 Fix a bug that allowed a tracing process (e.g. gdb) to write 313 to a memory-mapped file in the traced process's address space 314 even if neither the traced process nor the tracing process had 315 write access to that file. 316 31720130615: 318 CVS has been removed from the base system. An exact copy 319 of the code is available from the devel/cvs port. 320 32120130613: 322 Some people report the following error after the switch to bmake: 323 324 make: illegal option -- J 325 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] 326 ... 327 *** [buildworld] Error code 2 328 329 this likely due to an old instance of make in 330 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE}) 331 which src/Makefile will use that blindly, if it exists, so if 332 you see the above error: 333 334 rm -rf `make -V MAKEPATH` 335 336 should resolve it. 337 33820130516: 339 Use bmake by default. 340 Whereas before one could choose to build with bmake via 341 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old 342 make. The goal is to remove these knobs for 10-RELEASE. 343 344 It is worth noting that bmake (like gmake) treats the command 345 line as the unit of failure, rather than statements within the 346 command line. Thus '(cd some/where && dosomething)' is safer 347 than 'cd some/where; dosomething'. The '()' allows consistent 348 behavior in parallel build. 349 35020130429: 351 Fix a bug that allows NFS clients to issue READDIR on files. 352 35320130426: 354 The WITHOUT_IDEA option has been removed because 355 the IDEA patent expired. 356 35720130426: 358 The sysctl which controls TRIM support under ZFS has been renamed 359 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been 360 enabled by default. 361 36220130425: 363 The mergemaster command now uses the default MAKEOBJDIRPREFIX 364 rather than creating it's own in the temporary directory in 365 order allow access to bootstrapped versions of tools such as 366 install and mtree. When upgrading from version of FreeBSD where 367 the install command does not support -l, you will need to 368 install a new mergemaster command if mergemaster -p is required. 369 This can be accomplished with the command (cd src/usr.sbin/mergemaster 370 && make install). 371 37220130404: 373 Legacy ATA stack, disabled and replaced by new CAM-based one since 374 FreeBSD 9.0, completely removed from the sources. Kernel modules 375 atadisk and atapi*, user-level tools atacontrol and burncd are 376 removed. Kernel option `options ATA_CAM` is now permanently enabled 377 and removed. 378 37920130319: 380 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2) 381 and socketpair(2). Software, in particular Kerberos, may 382 automatically detect and use these during building. The resulting 383 binaries will not work on older kernels. 384 38520130308: 386 CTL_DISABLE has also been added to the sparc64 GENERIC (for further 387 information, see the respective 20130304 entry). 388 38920130304: 390 Recent commits to callout(9) changed the size of struct callout, 391 so the KBI is probably heavily disturbed. Also, some functions 392 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced 393 by macros. Every kernel module using it won't load, so rebuild 394 is requested. 395 396 The ctl device has been re-enabled in GENERIC for i386 and amd64, 397 but does not initialize by default (because of the new CTL_DISABLE 398 option) to save memory. To re-enable it, remove the CTL_DISABLE 399 option from the kernel config file or set kern.cam.ctl.disable=0 400 in /boot/loader.conf. 401 40220130301: 403 The ctl device has been disabled in GENERIC for i386 and amd64. 404 This was done due to the extra memory being allocated at system 405 initialisation time by the ctl driver which was only used if 406 a CAM target device was created. This makes a FreeBSD system 407 unusable on 128MB or less of RAM. 408 40920130208: 410 A new compression method (lz4) has been merged to -HEAD. Please 411 refer to zpool-features(7) for more information. 412 413 Please refer to the "ZFS notes" section of this file for information 414 on upgrading boot ZFS pools. 415 41620130129: 417 A BSD-licensed patch(1) variant has been added and is installed 418 as bsdpatch, being the GNU version the default patch. 419 To inverse the logic and use the BSD-licensed one as default, 420 while having the GNU version installed as gnupatch, rebuild 421 and install world with the WITH_BSD_PATCH knob set. 422 42320130121: 424 Due to the use of the new -l option to install(1) during build 425 and install, you must take care not to directly set the INSTALL 426 make variable in your /etc/make.conf, /etc/src.conf, or on the 427 command line. If you wish to use the -C flag for all installs 428 you may be able to add INSTALL+=-C to /etc/make.conf or 429 /etc/src.conf. 430 43120130118: 432 The install(1) option -M has changed meaning and now takes an 433 argument that is a file or path to append logs to. In the 434 unlikely event that -M was the last option on the command line 435 and the command line contained at least two files and a target 436 directory the first file will have logs appended to it. The -M 437 option served little practical purpose in the last decade so its 438 use is expected to be extremely rare. 439 44020121223: 441 After switching to Clang as the default compiler some users of ZFS 442 on i386 systems started to experience stack overflow kernel panics. 443 Please consider using 'options KSTACK_PAGES=4' in such configurations. 444 44520121222: 446 GEOM_LABEL now mangles label names read from file system metadata. 447 Mangling affect labels containing spaces, non-printable characters, 448 '%' or '"'. Device names in /etc/fstab and other places may need to 449 be updated. 450 45120121217: 452 By default, only the 10 most recent kernel dumps will be saved. To 453 restore the previous behaviour (no limit on the number of kernel dumps 454 stored in the dump directory) add the following line to /etc/rc.conf: 455 456 savecore_flags="" 457 45820121201: 459 With the addition of auditdistd(8), a new auditdistd user is now 460 required during installworld. "mergemaster -p" can be used to 461 add the user prior to installworld, as documented in the handbook. 462 46320121117: 464 The sin6_scope_id member variable in struct sockaddr_in6 is now 465 filled by the kernel before passing the structure to the userland via 466 sysctl or routing socket. This means the KAME-specific embedded scope 467 id in sin6_addr.s6_addr[2] is always cleared in userland application. 468 This behavior can be controlled by net.inet6.ip6.deembed_scopeid. 469 __FreeBSD_version is bumped to 1000025. 470 47120121105: 472 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default. 473 This means that the world and kernel will be compiled with clang 474 and that clang will be installed as /usr/bin/cc, /usr/bin/c++, 475 and /usr/bin/cpp. To disable this behavior and revert to building 476 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions 477 of current may need to bootstrap WITHOUT_CLANG first if the clang 478 build fails (its compatibility window doesn't extend to the 9 stable 479 branch point). 480 48120121102: 482 The IPFIREWALL_FORWARD kernel option has been removed. Its 483 functionality now turned on by default. 484 48520121023: 486 The ZERO_COPY_SOCKET kernel option has been removed and 487 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP. 488 NB: SOCKET_SEND_COW uses the VM page based copy-on-write 489 mechanism which is not safe and may result in kernel crashes. 490 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current 491 driver supports disposeable external page sized mbuf storage. 492 Proper replacements for both zero-copy mechanisms are under 493 consideration and will eventually lead to complete removal 494 of the two kernel options. 495 49620121023: 497 The IPv4 network stack has been converted to network byte 498 order. The following modules need to be recompiled together 499 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4), 500 pf(4), ipfw(4), ng_ipfw(4), stf(4). 501 50220121022: 503 Support for non-MPSAFE filesystems was removed from VFS. The 504 VFS_VERSION was bumped, all filesystem modules shall be 505 recompiled. 506 50720121018: 508 All the non-MPSAFE filesystems have been disconnected from 509 the build. The full list includes: codafs, hpfs, ntfs, nwfs, 510 portalfs, smbfs, xfs. 511 51220121016: 513 The interface cloning API and ABI has changed. The following 514 modules need to be recompiled together with kernel: 515 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4), 516 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4), 517 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4). 518 51920121015: 520 The sdhci driver was split in two parts: sdhci (generic SD Host 521 Controller logic) and sdhci_pci (actual hardware driver). 522 No kernel config modifications are required, but if you 523 load sdhc as a module you must switch to sdhci_pci instead. 524 52520121014: 526 Import the FUSE kernel and userland support into base system. 527 52820121013: 529 The GNU sort(1) program has been removed since the BSD-licensed 530 sort(1) has been the default for quite some time and no serious 531 problems have been reported. The corresponding WITH_GNU_SORT 532 knob has also gone. 533 53420121006: 535 The pfil(9) API/ABI for AF_INET family has been changed. Packet 536 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled 537 with new kernel. 538 53920121001: 540 The net80211(4) ABI has been changed to allow for improved driver 541 PS-POLL and power-save support. All wireless drivers need to be 542 recompiled to work with the new kernel. 543 54420120913: 545 The random(4) support for the VIA hardware random number 546 generator (`PADLOCK') is no longer enabled unconditionally. 547 Add the padlock_rng device in the custom kernel config if 548 needed. The GENERIC kernels on i386 and amd64 do include the 549 device, so the change only affects the custom kernel 550 configurations. 551 55220120908: 553 The pf(4) packet filter ABI has been changed. pfctl(8) and 554 snmp_pf module need to be recompiled to work with new kernel. 555 55620120828: 557 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged 558 to -HEAD. Pools that have empty_bpobj in active state can not be 559 imported read-write with ZFS implementations that do not support 560 this feature. For more information read the zpool-features(5) 561 manual page. 562 56320120727: 564 The sparc64 ZFS loader has been changed to no longer try to auto- 565 detect ZFS providers based on diskN aliases but now requires these 566 to be explicitly listed in the OFW boot-device environment variable. 567 56820120712: 569 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring 570 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are 571 configuration changes. Make sure to merge /etc/ssl/openssl.cnf. 572 57320120712: 574 The following sysctls and tunables have been renamed for consistency 575 with other variables: 576 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered 577 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered 578 57920120628: 580 The sort utility has been replaced with BSD sort. For now, GNU sort 581 is also available as "gnusort" or the default can be set back to 582 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be 583 installed as "bsdsort". 584 58520120611: 586 A new version of ZFS (pool version 5000) has been merged to -HEAD. 587 Starting with this version the old system of ZFS pool versioning 588 is superseded by "feature flags". This concept enables forward 589 compatibility against certain future changes in functionality of ZFS 590 pools. The first read-only compatible "feature flag" for ZFS pools 591 is named "com.delphix:async_destroy". For more information 592 read the new zpool-features(5) manual page. 593 Please refer to the "ZFS notes" section of this file for information 594 on upgrading boot ZFS pools. 595 59620120417: 597 The malloc(3) implementation embedded in libc now uses sources imported 598 as contrib/jemalloc. The most disruptive API change is to 599 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf, 600 delete it prior to installworld, and optionally re-create it using the 601 new format after rebooting. See malloc.conf(5) for details 602 (specifically the TUNING section and the "opt.*" entries in the MALLCTL 603 NAMESPACE section). 604 60520120328: 606 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb 607 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is 608 now spelled mips. This is to aid compatibility with third-party 609 software that expects this naming scheme in uname(3). Little-endian 610 settings are unchanged. If you are updating a big-endian mips64 machine 611 from before this change, you may need to set MACHINE_ARCH=mips64 in 612 your environment before the new build system will recognize your machine. 613 61420120306: 615 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported 616 platforms. 617 61820120229: 619 Now unix domain sockets behave "as expected" on nullfs(5). Previously 620 nullfs(5) did not pass through all behaviours to the underlying layer, 621 as a result if we bound to a socket on the lower layer we could connect 622 only to the lower path; if we bound to the upper layer we could connect 623 only to the upper path. The new behavior is one can connect to both the 624 lower and the upper paths regardless what layer path one binds to. 625 62620120211: 627 The getifaddrs upgrade path broken with 20111215 has been restored. 628 If you have upgraded in between 20111215 and 20120209 you need to 629 recompile libc again with your kernel. You still need to recompile 630 world to be able to configure CARP but this restriction already 631 comes from 20111215. 632 63320120114: 634 The set_rcvar() function has been removed from /etc/rc.subr. All 635 base and ports rc.d scripts have been updated, so if you have a 636 port installed with a script in /usr/local/etc/rc.d you can either 637 hand-edit the rcvar= line, or reinstall the port. 638 639 An easy way to handle the mass-update of /etc/rc.d: 640 rm /etc/rc.d/* && mergemaster -i 641 64220120109: 643 panic(9) now stops other CPUs in the SMP systems, disables interrupts 644 on the current CPU and prevents other threads from running. 645 This behavior can be reverted using the kern.stop_scheduler_on_panic 646 tunable/sysctl. 647 The new behavior can be incompatible with kern.sync_on_panic. 648 64920111215: 650 The carp(4) facility has been changed significantly. Configuration 651 of the CARP protocol via ifconfig(8) has changed, as well as format 652 of CARP events submitted to devd(8) has changed. See manual pages 653 for more information. The arpbalance feature of carp(4) is currently 654 not supported anymore. 655 656 Size of struct in_aliasreq, struct in6_aliasreq has changed. User 657 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8), 658 need to be recompiled. 659 66020111122: 661 The acpi_wmi(4) status device /dev/wmistat has been renamed to 662 /dev/wmistat0. 663 66420111108: 665 The option VFS_ALLOW_NONMPSAFE option has been added in order to 666 explicitely support non-MPSAFE filesystems. 667 It is on by default for all supported platform at this present 668 time. 669 67020111101: 671 The broken amd(4) driver has been replaced with esp(4) in the amd64, 672 i386 and pc98 GENERIC kernel configuration files. 673 67420110930: 675 sysinstall has been removed 676 67720110923: 678 The stable/9 branch created in subversion. This corresponds to the 679 RELENG_9 branch in CVS. 680 681COMMON ITEMS: 682 683 General Notes 684 ------------- 685 Avoid using make -j when upgrading. While generally safe, there are 686 sometimes problems using -j to upgrade. If your upgrade fails with 687 -j, please try again without -j. From time to time in the past there 688 have been problems using -j with buildworld and/or installworld. This 689 is especially true when upgrading between "distant" versions (eg one 690 that cross a major release boundary or several minor releases, or when 691 several months have passed on the -current branch). 692 693 Sometimes, obscure build problems are the result of environment 694 poisoning. This can happen because the make utility reads its 695 environment when searching for values for global variables. To run 696 your build attempts in an "environmental clean room", prefix all make 697 commands with 'env -i '. See the env(1) manual page for more details. 698 699 When upgrading from one major version to another it is generally best 700 to upgrade to the latest code in the currently installed branch first, 701 then do an upgrade to the new branch. This is the best-tested upgrade 702 path, and has the highest probability of being successful. Please try 703 this approach before reporting problems with a major version upgrade. 704 705 When upgrading a live system, having a root shell around before 706 installing anything can help undo problems. Not having a root shell 707 around can lead to problems if pam has changed too much from your 708 starting point to allow continued authentication after the upgrade. 709 710 ZFS notes 711 --------- 712 When upgrading the boot ZFS pool to a new version, always follow 713 these two steps: 714 715 1.) recompile and reinstall the ZFS boot loader and boot block 716 (this is part of "make buildworld" and "make installworld") 717 718 2.) update the ZFS boot block on your boot drive 719 720 The following example updates the ZFS boot block on the first 721 partition (freebsd-boot) of a GPT partitioned drive ad0: 722 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0" 723 724 Non-boot pools do not need these updates. 725 726 To build a kernel 727 ----------------- 728 If you are updating from a prior version of FreeBSD (even one just 729 a few days old), you should follow this procedure. It is the most 730 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 731 732 make kernel-toolchain 733 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 734 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 735 736 To test a kernel once 737 --------------------- 738 If you just want to boot a kernel once (because you are not sure 739 if it works, or if you want to boot a known bad kernel to provide 740 debugging information) run 741 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 742 nextboot -k testkernel 743 744 To just build a kernel when you know that it won't mess you up 745 -------------------------------------------------------------- 746 This assumes you are already running a CURRENT system. Replace 747 ${arch} with the architecture of your machine (e.g. "i386", 748 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc). 749 750 cd src/sys/${arch}/conf 751 config KERNEL_NAME_HERE 752 cd ../compile/KERNEL_NAME_HERE 753 make depend 754 make 755 make install 756 757 If this fails, go to the "To build a kernel" section. 758 759 To rebuild everything and install it on the current system. 760 ----------------------------------------------------------- 761 # Note: sometimes if you are running current you gotta do more than 762 # is listed here if you are upgrading from a really old current. 763 764 <make sure you have good level 0 dumps> 765 make buildworld 766 make kernel KERNCONF=YOUR_KERNEL_HERE 767 [1] 768 <reboot in single user> [3] 769 mergemaster -Fp [5] 770 make installworld 771 mergemaster -Fi [4] 772 make delete-old [6] 773 <reboot> 774 775 To cross-install current onto a separate partition 776 -------------------------------------------------- 777 # In this approach we use a separate partition to hold 778 # current's root, 'usr', and 'var' directories. A partition 779 # holding "/", "/usr" and "/var" should be about 2GB in 780 # size. 781 782 <make sure you have good level 0 dumps> 783 <boot into -stable> 784 make buildworld 785 make buildkernel KERNCONF=YOUR_KERNEL_HERE 786 <maybe newfs current's root partition> 787 <mount current's root partition on directory ${CURRENT_ROOT}> 788 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC 789 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 790 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 791 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 792 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 793 <reboot into current> 794 <do a "native" rebuild/install as described in the previous section> 795 <maybe install compatibility libraries from ports/misc/compat*> 796 <reboot> 797 798 799 To upgrade in-place from stable to current 800 ---------------------------------------------- 801 <make sure you have good level 0 dumps> 802 make buildworld [9] 803 make kernel KERNCONF=YOUR_KERNEL_HERE [8] 804 [1] 805 <reboot in single user> [3] 806 mergemaster -Fp [5] 807 make installworld 808 mergemaster -Fi [4] 809 make delete-old [6] 810 <reboot> 811 812 Make sure that you've read the UPDATING file to understand the 813 tweaks to various things you need. At this point in the life 814 cycle of current, things change often and you are on your own 815 to cope. The defaults can also change, so please read ALL of 816 the UPDATING entries. 817 818 Also, if you are tracking -current, you must be subscribed to 819 freebsd-current@freebsd.org. Make sure that before you update 820 your sources that you have read and understood all the recent 821 messages there. If in doubt, please track -stable which has 822 much fewer pitfalls. 823 824 [1] If you have third party modules, such as vmware, you 825 should disable them at this point so they don't crash your 826 system on reboot. 827 828 [3] From the bootblocks, boot -s, and then do 829 fsck -p 830 mount -u / 831 mount -a 832 cd src 833 adjkerntz -i # if CMOS is wall time 834 Also, when doing a major release upgrade, it is required that 835 you boot into single user mode to do the installworld. 836 837 [4] Note: This step is non-optional. Failure to do this step 838 can result in a significant reduction in the functionality of the 839 system. Attempting to do it by hand is not recommended and those 840 that pursue this avenue should read this file carefully, as well 841 as the archives of freebsd-current and freebsd-hackers mailing lists 842 for potential gotchas. The -U option is also useful to consider. 843 See mergemaster(8) for more information. 844 845 [5] Usually this step is a noop. However, from time to time 846 you may need to do this if you get unknown user in the following 847 step. It never hurts to do it all the time. You may need to 848 install a new mergemaster (cd src/usr.sbin/mergemaster && make 849 install) after the buildworld before this step if you last updated 850 from current before 20130425 or from -stable before 20130430. 851 852 [6] This only deletes old files and directories. Old libraries 853 can be deleted by "make delete-old-libs", but you have to make 854 sure that no program is using those libraries anymore. 855 856 [8] In order to have a kernel that can run the 4.x binaries needed to 857 do an installworld, you must include the COMPAT_FREEBSD4 option in 858 your kernel. Failure to do so may leave you with a system that is 859 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is 860 required to run the 5.x binaries on more recent kernels. And so on 861 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7. 862 863 Make sure that you merge any new devices from GENERIC since the 864 last time you updated your kernel config file. 865 866 [9] When checking out sources, you must include the -P flag to have 867 cvs prune empty directories. 868 869 If CPUTYPE is defined in your /etc/make.conf, make sure to use the 870 "?=" instead of the "=" assignment operator, so that buildworld can 871 override the CPUTYPE if it needs to. 872 873 MAKEOBJDIRPREFIX must be defined in an environment variable, and 874 not on the command line, or in /etc/make.conf. buildworld will 875 warn if it is improperly defined. 876FORMAT: 877 878This file contains a list, in reverse chronological order, of major 879breakages in tracking -current. It is not guaranteed to be a complete 880list of such breakages, and only contains entries since October 10, 2007. 881If you need to see UPDATING entries from before that date, you will need 882to fetch an UPDATING file from an older FreeBSD release. 883 884Copyright information: 885 886Copyright 1998-2009 M. Warner Losh. All Rights Reserved. 887 888Redistribution, publication, translation and use, with or without 889modification, in full or in part, in any form or format of this 890document are permitted without further permission from the author. 891 892THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 893IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 894WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 895DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 896INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 897(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 898SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 899HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 900STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 901IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 902POSSIBILITY OF SUCH DAMAGE. 903 904Contact Warner Losh if you have any questions about your use of 905this document. 906 907$FreeBSD$ 908