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