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