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 3420150614: 35 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from 36 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf 37 and devel/kyua to version 0.20+ and adjust any calling code to work 38 with Kyuafile and kyua. 39 4020150614: 41 The import of openssl to address the FreeBSD-SA-15:10.openssl 42 security advisory includes a change which rejects handshakes 43 with DH parameters below 768 bits. sendmail releases prior 44 to 8.15.2 (not yet released), defaulted to a 512 bit 45 DH parameter setting for client connections. To work around 46 this interoperability, sendmail can be configured to use a 47 2048 bit DH parameter by: 48 49 1. Edit /etc/mail/`hostname`.mc 50 2. If a setting for confDH_PARAMETERS does not exist or 51 exists and is set to a string beginning with '5', 52 replace it with '2'. 53 3. If a setting for confDH_PARAMETERS exists and is set to 54 a file path, create a new file with: 55 openssl dhparam -out /path/to/file 2048 56 4. Rebuild the .cf file: 57 cd /etc/mail/; make; make install 58 5. Restart sendmail: 59 cd /etc/mail/; make restart 60 61 A sendmail patch is coming, at which time this file will be 62 updated. 63 6420150604: 65 Generation of legacy formatted entries have been disabled by default 66 in pwd_mkdb(8), as all base system consumers of the legacy formatted 67 entries were converted to use the new format by default when the new, 68 machine independent format have been added and supported since FreeBSD 69 5.x. 70 71 Please see the pwd_mkdb(8) manual page for further details. 72 7320150525: 74 Clang and llvm have been upgraded to 3.6.1 release. Please see the 75 20141231 entry below for information about prerequisites and upgrading, 76 if you are not already using 3.5.0 or higher. 77 7820150521: 79 TI platform code switched to using vendor DTS files and this update 80 may break existing systems running on Beaglebone, Beaglebone Black, 81 and Pandaboard: 82 83 - dtb files should be regenerated/reinstalled. Filenames are the 84 same but content is different now 85 - GPIO addressing was changed, now each GPIO bank (32 pins per bank) 86 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old 87 addressing scheme is now pin 25 on /dev/gpioc3. 88 - Pandaboard: /etc/ttys should be updated, serial console device is 89 now /dev/ttyu2, not /dev/ttyu0 90 9120150501: 92 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim. 93 If you need the GNU extension from groff soelim(1), install groff 94 from package: pkg install groff, or via ports: textproc/groff. 95 9620150423: 97 chmod, chflags, chown and chgrp now affect symlinks in -R mode as 98 defined in symlink(7); previously symlinks were silently ignored. 99 10020150415: 101 The const qualifier has been removed from iconv(3) to comply with 102 POSIX. The ports tree is aware of this from r384038 onwards. 103 10420150416: 105 Libraries specified by LIBADD in Makefiles must have a corresponding 106 DPADD_<lib> variable to ensure correct dependencies. This is now 107 enforced in src.libnames.mk. 108 10920150324: 110 From legacy ata(4) driver was removed support for SATA controllers 111 supported by more functional drivers ahci(4), siis(4) and mvs(4). 112 Kernel modules ataahci and ataadaptec were removed completely, 113 replaced by ahci and mvs modules respectively. 114 11520150315: 116 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see 117 the 20141231 entry below for information about prerequisites and 118 upgrading, if you are not already using 3.5.0 or higher. 119 12020150307: 121 The 32-bit PowerPC kernel has been changed to a position-independent 122 executable. This can only be booted with a version of loader(8) 123 newer than January 31, 2015, so make sure to update both world and 124 kernel before rebooting. 125 12620150217: 127 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014), 128 but before r278950, the RNG was not seeded properly. Immediately 129 upgrade the kernel to r278950 or later and regenerate any keys (e.g. 130 ssh keys or openssl keys) that were generated w/ a kernel from that 131 range. This does not affect programs that directly used /dev/random 132 or /dev/urandom. All userland uses of arc4random(3) are affected. 133 13420150210: 135 The autofs(4) ABI was changed in order to restore binary compatibility 136 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work 137 with the new kernel. 138 13920150131: 140 The powerpc64 kernel has been changed to a position-independent 141 executable. This can only be booted with a new version of loader(8), 142 so make sure to update both world and kernel before rebooting. 143 14420150118: 145 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix 146 only release, no new features have been added. Please see the 20141231 147 entry below for information about prerequisites and upgrading, if you 148 are not already using 3.5.0. 149 15020150107: 151 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now 152 taken from the ELF Tool Chain project rather than GNU binutils. They 153 should be drop-in replacements, with the addition of arm64 support. 154 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the 155 binutils tools, if necessary. 156 15720150105: 158 The default Unbound configuration now enables remote control 159 using a local socket. Users who have already enabled the 160 local_unbound service should regenerate their configuration 161 by running "service local_unbound setup" as root. 162 16320150102: 164 The GNU texinfo and GNU info pages have been removed. 165 To be able to view GNU info pages please install texinfo from ports. 166 16720141231: 168 Clang, llvm and lldb have been upgraded to 3.5.0 release. 169 170 As of this release, a prerequisite for building clang, llvm and lldb is 171 a C++11 capable compiler and C++11 standard library. This means that to 172 be able to successfully build the cross-tools stage of buildworld, with 173 clang as the bootstrap compiler, your system compiler or cross compiler 174 should either be clang 3.3 or later, or gcc 4.8 or later, and your 175 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or 176 later. 177 178 On any standard FreeBSD 10.x or 11.x installation, where clang and 179 libc++ are on by default (that is, on x86 or arm), this should work out 180 of the box. 181 182 On 9.x installations where clang is enabled by default, e.g. on x86 and 183 powerpc, libc++ will not be enabled by default, so libc++ should be 184 built (with clang) and installed first. If both clang and libc++ are 185 missing, build clang first, then use it to build libc++. 186 187 On 8.x and earlier installations, upgrade to 9.x first, and then follow 188 the instructions for 9.x above. 189 190 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by 191 default, and do not build clang. 192 193 Many embedded systems are resource constrained, and will not be able to 194 build clang in a reasonable time, or in some cases at all. In those 195 cases, cross building bootable systems on amd64 is a workaround. 196 197 This new version of clang introduces a number of new warnings, of which 198 the following are most likely to appear: 199 200 -Wabsolute-value 201 202 This warns in two cases, for both C and C++: 203 * When the code is trying to take the absolute value of an unsigned 204 quantity, which is effectively a no-op, and almost never what was 205 intended. The code should be fixed, if at all possible. If you are 206 sure that the unsigned quantity can be safely cast to signed, without 207 loss of information or undefined behavior, you can add an explicit 208 cast, or disable the warning. 209 210 * When the code is trying to take an absolute value, but the called 211 abs() variant is for the wrong type, which can lead to truncation. 212 If you want to disable the warning instead of fixing the code, please 213 make sure that truncation will not occur, or it might lead to unwanted 214 side-effects. 215 216 -Wtautological-undefined-compare and 217 -Wundefined-bool-conversion 218 219 These warn when C++ code is trying to compare 'this' against NULL, while 220 'this' should never be NULL in well-defined C++ code. However, there is 221 some legacy (pre C++11) code out there, which actively abuses this 222 feature, which was less strictly defined in previous C++ versions. 223 224 Squid and openjdk do this, for example. The warning can be turned off 225 for C++98 and earlier, but compiling the code in C++11 mode might result 226 in unexpected behavior; for example, the parts of the program that are 227 unreachable could be optimized away. 228 22920141222: 230 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER) 231 kernel sources have been removed. The .h files remain, since some 232 utilities include them. This will need to be fixed later. 233 If "mount -t oldnfs ..." is attempted, it will fail. 234 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used, 235 the utilities will report errors. 236 23720141121: 238 The handling of LOCAL_LIB_DIRS has been altered to skip addition of 239 directories to top level SUBDIR variable when their parent 240 directory is included in LOCAL_DIRS. Users with build systems with 241 such hierarchies and without SUBDIR entries in the parent 242 directory Makefiles should add them or add the directories to 243 LOCAL_DIRS. 244 24520141109: 246 faith(4) and faithd(8) have been removed from the base system. Faith 247 has been obsolete for a very long time. 248 24920141104: 250 vt(4), the new console driver, is enabled by default. It brings 251 support for Unicode and double-width characters, as well as 252 support for UEFI and integration with the KMS kernel video 253 drivers. 254 255 You may need to update your console settings in /etc/rc.conf, 256 most probably the keymap. During boot, /etc/rc.d/syscons will 257 indicate what you need to do. 258 259 vt(4) still has issues and lacks some features compared to 260 syscons(4). See the wiki for up-to-date information: 261 https://wiki.freebsd.org/Newcons 262 263 If you want to keep using syscons(4), you can do so by adding 264 the following line to /boot/loader.conf: 265 kern.vty=sc 266 26720141102: 268 pjdfstest has been integrated into kyua as an opt-in test suite. 269 Please see share/doc/pjdfstest/README for more details on how to 270 execute it. 271 27220141009: 273 gperf has been removed from the base system for architectures 274 that use clang. Ports that require gperf will obtain it from the 275 devel/gperf port. 276 27720140923: 278 pjdfstest has been moved from tools/regression/pjdfstest to 279 contrib/pjdfstest . 280 28120140922: 282 At svn r271982, The default linux compat kernel ABI has been adjusted 283 to 2.6.18 in support of the linux-c6 compat ports infrastructure 284 update. If you wish to continue using the linux-f10 compat ports, 285 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are 286 encouraged to update their linux-compat packages to linux-c6 during 287 their next update cycle. 288 28920140729: 290 The ofwfb driver, used to provide a graphics console on PowerPC when 291 using vt(4), no longer allows mmap() of all physical memory. This 292 will prevent Xorg on PowerPC with some ATI graphics cards from 293 initializing properly unless x11-servers/xorg-server is updated to 294 1.12.4_8 or newer. 295 29620140723: 297 The xdev targets have been converted to using TARGET and 298 TARGET_ARCH instead of XDEV and XDEV_ARCH. 299 30020140719: 301 The default unbound configuration has been modified to address 302 issues with reverse lookups on networks that use private 303 address ranges. If you use the local_unbound service, run 304 "service local_unbound setup" as root to regenerate your 305 configuration, then "service local_unbound reload" to load the 306 new configuration. 307 30820140709: 309 The GNU texinfo and GNU info pages are not built and installed 310 anymore, WITH_INFO knob has been added to allow to built and install 311 them again. 312 UPDATE: see 20150102 entry on texinfo's removal 313 31420140708: 315 The GNU readline library is now an INTERNALLIB - that is, it is 316 statically linked into consumers (GDB and variants) in the base 317 system, and the shared library is no longer installed. The 318 devel/readline port is available for third party software that 319 requires readline. 320 32120140702: 322 The Itanium architecture (ia64) has been removed from the list of 323 known architectures. This is the first step in the removal of the 324 architecture. 325 32620140701: 327 Commit r268115 has added NFSv4.1 server support, merged from 328 projects/nfsv4.1-server. Since this includes changes to the 329 internal interfaces between the NFS related modules, a full 330 build of the kernel and modules will be necessary. 331 __FreeBSD_version has been bumped. 332 33320140629: 334 The WITHOUT_VT_SUPPORT kernel config knob has been renamed 335 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning 336 which differs from the behaviour controlled by this knob.) 337 33820140619: 339 Maximal length of the serial number in CTL was increased from 16 to 340 64 chars, that breaks ABI. All CTL-related tools, such as ctladm 341 and ctld, need to be rebuilt to work with a new kernel. 342 34320140606: 344 The libatf-c and libatf-c++ major versions were downgraded to 0 and 345 1 respectively to match the upstream numbers. They were out of 346 sync because, when they were originally added to FreeBSD, the 347 upstream versions were not respected. These libraries are private 348 and not yet built by default, so renumbering them should be a 349 non-issue. However, unclean source trees will yield broken test 350 programs once the operator executes "make delete-old-libs" after a 351 "make installworld". 352 353 Additionally, the atf-sh binary was made private by moving it into 354 /usr/libexec/. Already-built shell test programs will keep the 355 path to the old binary so they will break after "make delete-old" 356 is run. 357 358 If you are using WITH_TESTS=yes (not the default), wipe the object 359 tree and rebuild from scratch to prevent spurious test failures. 360 This is only needed once: the misnumbered libraries and misplaced 361 binaries have been added to OptionalObsoleteFiles.inc so they will 362 be removed during a clean upgrade. 363 36420140512: 365 Clang and llvm have been upgraded to 3.4.1 release. 366 36720140508: 368 We bogusly installed src.opts.mk in /usr/share/mk. This file should 369 be removed to avoid issues in the future (and has been added to 370 ObsoleteFiles.inc). 371 37220140505: 373 /etc/src.conf now affects only builds of the FreeBSD src tree. In the 374 past, it affected all builds that used the bsd.*.mk files. The old 375 behavior was a bug, but people may have relied upon it. To get this 376 behavior back, you can .include /etc/src.conf from /etc/make.conf 377 (which is still global and isn't changed). This also changes the 378 behavior of incremental builds inside the tree of individual 379 directories. Set MAKESYSPATH to ".../share/mk" to do that. 380 Although this has survived make universe and some upgrade scenarios, 381 other upgrade scenarios may have broken. At least one form of 382 temporary breakage was fixed with MAKESYSPATH settings for buildworld 383 as well... In cases where MAKESYSPATH isn't working with this 384 setting, you'll need to set it to the full path to your tree. 385 386 One side effect of all this cleaning up is that bsd.compiler.mk 387 is no longer implicitly included by bsd.own.mk. If you wish to 388 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk 389 as well. 390 39120140430: 392 The lindev device has been removed since /dev/full has been made a 393 standard device. __FreeBSD_version has been bumped. 394 39520140424: 396 The knob WITHOUT_VI was added to the base system, which controls 397 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1) 398 in order to reorder files share/termcap and didn't build ex(1) as a 399 build tool, so building/installing with WITH_VI is highly advised for 400 build hosts for older releases. 401 402 This issue has been fixed in stable/9 and stable/10 in r277022 and 403 r276991, respectively. 404 40520140418: 406 The YES_HESIOD knob has been removed. It has been obsolete for 407 a decade. Please move to using WITH_HESIOD instead or your builds 408 will silently lack HESIOD. 409 41020140405: 411 The uart(4) driver has been changed with respect to its handling 412 of the low-level console. Previously the uart(4) driver prevented 413 any process from changing the baudrate or the CLOCAL and HUPCL 414 control flags. By removing the restrictions, operators can make 415 changes to the serial console port without having to reboot. 416 However, when getty(8) is started on the serial device that is 417 associated with the low-level console, a misconfigured terminal 418 line in /etc/ttys will now have a real impact. 419 Before upgrading the kernel, make sure that /etc/ttys has the 420 serial console device configured as 3wire without baudrate to 421 preserve the previous behaviour. E.g: 422 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure 423 42420140306: 425 Support for libwrap (TCP wrappers) in rpcbind was disabled by default 426 to improve performance. To re-enable it, if needed, run rpcbind 427 with command line option -W. 428 42920140226: 430 Switched back to the GPL dtc compiler due to updates in the upstream 431 dts files not being supported by the BSDL dtc compiler. You will need 432 to rebuild your kernel toolchain to pick up the new compiler. Core dumps 433 may result while building dtb files during a kernel build if you fail 434 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler. 435 43620140216: 437 Clang and llvm have been upgraded to 3.4 release. 438 43920140216: 440 The nve(4) driver has been removed. Please use the nfe(4) driver 441 for NVIDIA nForce MCP Ethernet adapters instead. 442 44320140212: 444 An ABI incompatibility crept into the libc++ 3.4 import in r261283. 445 This could cause certain C++ applications using shared libraries built 446 against the previous version of libc++ to crash. The incompatibility 447 has now been fixed, but any C++ applications or shared libraries built 448 between r261283 and r261801 should be recompiled. 449 45020140204: 451 OpenSSH will now ignore errors caused by kernel lacking of Capsicum 452 capability mode support. Please note that enabling the feature in 453 kernel is still highly recommended. 454 45520140131: 456 OpenSSH is now built with sandbox support, and will use sandbox as 457 the default privilege separation method. This requires Capsicum 458 capability mode support in kernel. 459 46020140128: 461 The libelf and libdwarf libraries have been updated to newer 462 versions from upstream. Shared library version numbers for 463 these two libraries were bumped. Any ports or binaries 464 requiring these two libraries should be recompiled. 465 __FreeBSD_version is bumped to 1100006. 466 46720140110: 468 If a Makefile in a tests/ directory was auto-generating a Kyuafile 469 instead of providing an explicit one, this would prevent such 470 Makefile from providing its own Kyuafile in the future during 471 NO_CLEAN builds. This has been fixed in the Makefiles but manual 472 intervention is needed to clean an objdir if you use NO_CLEAN: 473 # find /usr/obj -name Kyuafile | xargs rm -f 474 47520131213: 476 The behavior of gss_pseudo_random() for the krb5 mechanism 477 has changed, for applications requesting a longer random string 478 than produced by the underlying enctype's pseudo-random() function. 479 In particular, the random string produced from a session key of 480 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will 481 be different at the 17th octet and later, after this change. 482 The counter used in the PRF+ construction is now encoded as a 483 big-endian integer in accordance with RFC 4402. 484 __FreeBSD_version is bumped to 1100004. 485 48620131108: 487 The WITHOUT_ATF build knob has been removed and its functionality 488 has been subsumed into the more generic WITHOUT_TESTS. If you were 489 using the former to disable the build of the ATF libraries, you 490 should change your settings to use the latter. 491 49220131025: 493 The default version of mtree is nmtree which is obtained from 494 NetBSD. The output is generally the same, but may vary 495 slightly. If you found you need identical output adding 496 "-F freebsd9" to the command line should do the trick. For the 497 time being, the old mtree is available as fmtree. 498 49920131014: 500 libbsdyml has been renamed to libyaml and moved to /usr/lib/private. 501 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg 502 1.1.4_8 and verify bsdyml not linked in, before running "make 503 delete-old-libs": 504 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean 505 or 506 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml 507 50820131010: 509 The rc.d/jail script has been updated to support jail(8) 510 configuration file. The "jail_<jname>_*" rc.conf(5) variables 511 for per-jail configuration are automatically converted to 512 /var/run/jail.<jname>.conf before the jail(8) utility is invoked. 513 This is transparently backward compatible. See below about some 514 incompatibilities and rc.conf(5) manual page for more details. 515 516 These variables are now deprecated in favor of jail(8) configuration 517 file. One can use "rc.d/jail config <jname>" command to generate 518 a jail(8) configuration file in /var/run/jail.<jname>.conf without 519 running the jail(8) utility. The default pathname of the 520 configuration file is /etc/jail.conf and can be specified by 521 using $jail_conf or $jail_<jname>_conf variables. 522 523 Please note that jail_devfs_ruleset accepts an integer at 524 this moment. Please consider to rewrite the ruleset name 525 with an integer. 526 52720130930: 528 BIND has been removed from the base system. If all you need 529 is a local resolver, simply enable and start the local_unbound 530 service instead. Otherwise, several versions of BIND are 531 available in the ports tree. The dns/bind99 port is one example. 532 533 With this change, nslookup(1) and dig(1) are no longer in the base 534 system. Users should instead use host(1) and drill(1) which are 535 in the base system. Alternatively, nslookup and dig can 536 be obtained by installing the dns/bind-tools port. 537 53820130916: 539 With the addition of unbound(8), a new unbound user is now 540 required during installworld. "mergemaster -p" can be used to 541 add the user prior to installworld, as documented in the handbook. 542 54320130911: 544 OpenSSH is now built with DNSSEC support, and will by default 545 silently trust signed SSHFP records. This can be controlled with 546 the VerifyHostKeyDNS client configuration setting. DNSSEC support 547 can be disabled entirely with the WITHOUT_LDNS option in src.conf. 548 54920130906: 550 The GNU Compiler Collection and C++ standard library (libstdc++) 551 are no longer built by default on platforms where clang is the system 552 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX 553 options in src.conf. 554 55520130905: 556 The PROCDESC kernel option is now part of the GENERIC kernel 557 configuration and is required for the rwhod(8) to work. 558 If you are using custom kernel configuration, you should include 559 'options PROCDESC'. 560 56120130905: 562 The API and ABI related to the Capsicum framework was modified 563 in backward incompatible way. The userland libraries and programs 564 have to be recompiled to work with the new kernel. This includes the 565 following libraries and programs, but the whole buildworld is 566 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl, 567 kdump, procstat, rwho, rwhod, uniq. 568 56920130903: 570 AES-NI intrinsic support has been added to gcc. The AES-NI module 571 has been updated to use this support. A new gcc is required to build 572 the aesni module on both i386 and amd64. 573 57420130821: 575 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices. 576 Thus "device padlock_rng" and "device rdrand_rng" should be 577 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG". 578 57920130813: 580 WITH_ICONV has been split into two feature sets. WITH_ICONV now 581 enables just the iconv* functionality and is now on by default. 582 WITH_LIBICONV_COMPAT enables the libiconv api and link time 583 compatability. Set WITHOUT_ICONV to build the old way. 584 If you have been using WITH_ICONV before, you will very likely 585 need to turn on WITH_LIBICONV_COMPAT. 586 58720130806: 588 INVARIANTS option now enables DEBUG for code with OpenSolaris and 589 Illumos origin, including ZFS. If you have INVARIANTS in your 590 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG 591 explicitly. 592 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS) 593 locks if WITNESS option was set. Because that generated a lot of 594 witness(9) reports and all of them were believed to be false 595 positives, this is no longer done. New option OPENSOLARIS_WITNESS 596 can be used to achieve the previous behavior. 597 59820130806: 599 Timer values in IPv6 data structures now use time_uptime instead 600 of time_second. Although this is not a user-visible functional 601 change, userland utilities which directly use them---ndp(8), 602 rtadvd(8), and rtsold(8) in the base system---need to be updated 603 to r253970 or later. 604 60520130802: 606 find -delete can now delete the pathnames given as arguments, 607 instead of only files found below them or if the pathname did 608 not contain any slashes. Formerly, the following error message 609 would result: 610 611 find: -delete: <path>: relative path potentially not safe 612 613 Deleting the pathnames given as arguments can be prevented 614 without error messages using -mindepth 1 or by changing 615 directory and passing "." as argument to find. This works in the 616 old as well as the new version of find. 617 61820130726: 619 Behavior of devfs rules path matching has been changed. 620 Pattern is now always matched against fully qualified devfs 621 path and slash characters must be explicitly matched by 622 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs 623 subdirectories must be reviewed. 624 62520130716: 626 The default ARM ABI has changed to the ARM EABI. The old ABI is 627 incompatible with the ARM EABI and all programs and modules will 628 need to be rebuilt to work with a new kernel. 629 630 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set. 631 632 NOTE: Support for the old ABI will be removed in the future and 633 users are advised to upgrade. 634 63520130709: 636 pkg_install has been disconnected from the build if you really need it 637 you should add WITH_PKGTOOLS in your src.conf(5). 638 63920130709: 640 Most of network statistics structures were changed to be able 641 keep 64-bits counters. Thus all tools, that work with networking 642 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.) 643 64420130629: 645 Fix targets that run multiple make's to use && rather than ; 646 so that subsequent steps depend on success of previous. 647 648 NOTE: if building 'universe' with -j* on stable/8 or stable/9 649 it would be better to start the build using bmake, to avoid 650 overloading the machine. 651 65220130618: 653 Fix a bug that allowed a tracing process (e.g. gdb) to write 654 to a memory-mapped file in the traced process's address space 655 even if neither the traced process nor the tracing process had 656 write access to that file. 657 65820130615: 659 CVS has been removed from the base system. An exact copy 660 of the code is available from the devel/cvs port. 661 66220130613: 663 Some people report the following error after the switch to bmake: 664 665 make: illegal option -- J 666 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] 667 ... 668 *** [buildworld] Error code 2 669 670 this likely due to an old instance of make in 671 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE}) 672 which src/Makefile will use that blindly, if it exists, so if 673 you see the above error: 674 675 rm -rf `make -V MAKEPATH` 676 677 should resolve it. 678 67920130516: 680 Use bmake by default. 681 Whereas before one could choose to build with bmake via 682 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old 683 make. The goal is to remove these knobs for 10-RELEASE. 684 685 It is worth noting that bmake (like gmake) treats the command 686 line as the unit of failure, rather than statements within the 687 command line. Thus '(cd some/where && dosomething)' is safer 688 than 'cd some/where; dosomething'. The '()' allows consistent 689 behavior in parallel build. 690 69120130429: 692 Fix a bug that allows NFS clients to issue READDIR on files. 693 69420130426: 695 The WITHOUT_IDEA option has been removed because 696 the IDEA patent expired. 697 69820130426: 699 The sysctl which controls TRIM support under ZFS has been renamed 700 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been 701 enabled by default. 702 70320130425: 704 The mergemaster command now uses the default MAKEOBJDIRPREFIX 705 rather than creating it's own in the temporary directory in 706 order allow access to bootstrapped versions of tools such as 707 install and mtree. When upgrading from version of FreeBSD where 708 the install command does not support -l, you will need to 709 install a new mergemaster command if mergemaster -p is required. 710 This can be accomplished with the command (cd src/usr.sbin/mergemaster 711 && make install). 712 71320130404: 714 Legacy ATA stack, disabled and replaced by new CAM-based one since 715 FreeBSD 9.0, completely removed from the sources. Kernel modules 716 atadisk and atapi*, user-level tools atacontrol and burncd are 717 removed. Kernel option `options ATA_CAM` is now permanently enabled 718 and removed. 719 72020130319: 721 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2) 722 and socketpair(2). Software, in particular Kerberos, may 723 automatically detect and use these during building. The resulting 724 binaries will not work on older kernels. 725 72620130308: 727 CTL_DISABLE has also been added to the sparc64 GENERIC (for further 728 information, see the respective 20130304 entry). 729 73020130304: 731 Recent commits to callout(9) changed the size of struct callout, 732 so the KBI is probably heavily disturbed. Also, some functions 733 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced 734 by macros. Every kernel module using it won't load, so rebuild 735 is requested. 736 737 The ctl device has been re-enabled in GENERIC for i386 and amd64, 738 but does not initialize by default (because of the new CTL_DISABLE 739 option) to save memory. To re-enable it, remove the CTL_DISABLE 740 option from the kernel config file or set kern.cam.ctl.disable=0 741 in /boot/loader.conf. 742 74320130301: 744 The ctl device has been disabled in GENERIC for i386 and amd64. 745 This was done due to the extra memory being allocated at system 746 initialisation time by the ctl driver which was only used if 747 a CAM target device was created. This makes a FreeBSD system 748 unusable on 128MB or less of RAM. 749 75020130208: 751 A new compression method (lz4) has been merged to -HEAD. Please 752 refer to zpool-features(7) for more information. 753 754 Please refer to the "ZFS notes" section of this file for information 755 on upgrading boot ZFS pools. 756 75720130129: 758 A BSD-licensed patch(1) variant has been added and is installed 759 as bsdpatch, being the GNU version the default patch. 760 To inverse the logic and use the BSD-licensed one as default, 761 while having the GNU version installed as gnupatch, rebuild 762 and install world with the WITH_BSD_PATCH knob set. 763 76420130121: 765 Due to the use of the new -l option to install(1) during build 766 and install, you must take care not to directly set the INSTALL 767 make variable in your /etc/make.conf, /etc/src.conf, or on the 768 command line. If you wish to use the -C flag for all installs 769 you may be able to add INSTALL+=-C to /etc/make.conf or 770 /etc/src.conf. 771 77220130118: 773 The install(1) option -M has changed meaning and now takes an 774 argument that is a file or path to append logs to. In the 775 unlikely event that -M was the last option on the command line 776 and the command line contained at least two files and a target 777 directory the first file will have logs appended to it. The -M 778 option served little practical purpose in the last decade so its 779 use is expected to be extremely rare. 780 78120121223: 782 After switching to Clang as the default compiler some users of ZFS 783 on i386 systems started to experience stack overflow kernel panics. 784 Please consider using 'options KSTACK_PAGES=4' in such configurations. 785 78620121222: 787 GEOM_LABEL now mangles label names read from file system metadata. 788 Mangling affect labels containing spaces, non-printable characters, 789 '%' or '"'. Device names in /etc/fstab and other places may need to 790 be updated. 791 79220121217: 793 By default, only the 10 most recent kernel dumps will be saved. To 794 restore the previous behaviour (no limit on the number of kernel dumps 795 stored in the dump directory) add the following line to /etc/rc.conf: 796 797 savecore_flags="" 798 79920121201: 800 With the addition of auditdistd(8), a new auditdistd user is now 801 required during installworld. "mergemaster -p" can be used to 802 add the user prior to installworld, as documented in the handbook. 803 80420121117: 805 The sin6_scope_id member variable in struct sockaddr_in6 is now 806 filled by the kernel before passing the structure to the userland via 807 sysctl or routing socket. This means the KAME-specific embedded scope 808 id in sin6_addr.s6_addr[2] is always cleared in userland application. 809 This behavior can be controlled by net.inet6.ip6.deembed_scopeid. 810 __FreeBSD_version is bumped to 1000025. 811 81220121105: 813 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default. 814 This means that the world and kernel will be compiled with clang 815 and that clang will be installed as /usr/bin/cc, /usr/bin/c++, 816 and /usr/bin/cpp. To disable this behavior and revert to building 817 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions 818 of current may need to bootstrap WITHOUT_CLANG first if the clang 819 build fails (its compatibility window doesn't extend to the 9 stable 820 branch point). 821 82220121102: 823 The IPFIREWALL_FORWARD kernel option has been removed. Its 824 functionality now turned on by default. 825 82620121023: 827 The ZERO_COPY_SOCKET kernel option has been removed and 828 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP. 829 NB: SOCKET_SEND_COW uses the VM page based copy-on-write 830 mechanism which is not safe and may result in kernel crashes. 831 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current 832 driver supports disposeable external page sized mbuf storage. 833 Proper replacements for both zero-copy mechanisms are under 834 consideration and will eventually lead to complete removal 835 of the two kernel options. 836 83720121023: 838 The IPv4 network stack has been converted to network byte 839 order. The following modules need to be recompiled together 840 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4), 841 pf(4), ipfw(4), ng_ipfw(4), stf(4). 842 84320121022: 844 Support for non-MPSAFE filesystems was removed from VFS. The 845 VFS_VERSION was bumped, all filesystem modules shall be 846 recompiled. 847 84820121018: 849 All the non-MPSAFE filesystems have been disconnected from 850 the build. The full list includes: codafs, hpfs, ntfs, nwfs, 851 portalfs, smbfs, xfs. 852 85320121016: 854 The interface cloning API and ABI has changed. The following 855 modules need to be recompiled together with kernel: 856 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4), 857 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4), 858 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4). 859 86020121015: 861 The sdhci driver was split in two parts: sdhci (generic SD Host 862 Controller logic) and sdhci_pci (actual hardware driver). 863 No kernel config modifications are required, but if you 864 load sdhc as a module you must switch to sdhci_pci instead. 865 86620121014: 867 Import the FUSE kernel and userland support into base system. 868 86920121013: 870 The GNU sort(1) program has been removed since the BSD-licensed 871 sort(1) has been the default for quite some time and no serious 872 problems have been reported. The corresponding WITH_GNU_SORT 873 knob has also gone. 874 87520121006: 876 The pfil(9) API/ABI for AF_INET family has been changed. Packet 877 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled 878 with new kernel. 879 88020121001: 881 The net80211(4) ABI has been changed to allow for improved driver 882 PS-POLL and power-save support. All wireless drivers need to be 883 recompiled to work with the new kernel. 884 88520120913: 886 The random(4) support for the VIA hardware random number 887 generator (`PADLOCK') is no longer enabled unconditionally. 888 Add the padlock_rng device in the custom kernel config if 889 needed. The GENERIC kernels on i386 and amd64 do include the 890 device, so the change only affects the custom kernel 891 configurations. 892 89320120908: 894 The pf(4) packet filter ABI has been changed. pfctl(8) and 895 snmp_pf module need to be recompiled to work with new kernel. 896 89720120828: 898 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged 899 to -HEAD. Pools that have empty_bpobj in active state can not be 900 imported read-write with ZFS implementations that do not support 901 this feature. For more information read the zpool-features(5) 902 manual page. 903 90420120727: 905 The sparc64 ZFS loader has been changed to no longer try to auto- 906 detect ZFS providers based on diskN aliases but now requires these 907 to be explicitly listed in the OFW boot-device environment variable. 908 90920120712: 910 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring 911 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are 912 configuration changes. Make sure to merge /etc/ssl/openssl.cnf. 913 91420120712: 915 The following sysctls and tunables have been renamed for consistency 916 with other variables: 917 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered 918 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered 919 92020120628: 921 The sort utility has been replaced with BSD sort. For now, GNU sort 922 is also available as "gnusort" or the default can be set back to 923 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be 924 installed as "bsdsort". 925 92620120611: 927 A new version of ZFS (pool version 5000) has been merged to -HEAD. 928 Starting with this version the old system of ZFS pool versioning 929 is superseded by "feature flags". This concept enables forward 930 compatibility against certain future changes in functionality of ZFS 931 pools. The first read-only compatible "feature flag" for ZFS pools 932 is named "com.delphix:async_destroy". For more information 933 read the new zpool-features(5) manual page. 934 Please refer to the "ZFS notes" section of this file for information 935 on upgrading boot ZFS pools. 936 93720120417: 938 The malloc(3) implementation embedded in libc now uses sources imported 939 as contrib/jemalloc. The most disruptive API change is to 940 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf, 941 delete it prior to installworld, and optionally re-create it using the 942 new format after rebooting. See malloc.conf(5) for details 943 (specifically the TUNING section and the "opt.*" entries in the MALLCTL 944 NAMESPACE section). 945 94620120328: 947 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb 948 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is 949 now spelled mips. This is to aid compatibility with third-party 950 software that expects this naming scheme in uname(3). Little-endian 951 settings are unchanged. If you are updating a big-endian mips64 machine 952 from before this change, you may need to set MACHINE_ARCH=mips64 in 953 your environment before the new build system will recognize your machine. 954 95520120306: 956 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported 957 platforms. 958 95920120229: 960 Now unix domain sockets behave "as expected" on nullfs(5). Previously 961 nullfs(5) did not pass through all behaviours to the underlying layer, 962 as a result if we bound to a socket on the lower layer we could connect 963 only to the lower path; if we bound to the upper layer we could connect 964 only to the upper path. The new behavior is one can connect to both the 965 lower and the upper paths regardless what layer path one binds to. 966 96720120211: 968 The getifaddrs upgrade path broken with 20111215 has been restored. 969 If you have upgraded in between 20111215 and 20120209 you need to 970 recompile libc again with your kernel. You still need to recompile 971 world to be able to configure CARP but this restriction already 972 comes from 20111215. 973 97420120114: 975 The set_rcvar() function has been removed from /etc/rc.subr. All 976 base and ports rc.d scripts have been updated, so if you have a 977 port installed with a script in /usr/local/etc/rc.d you can either 978 hand-edit the rcvar= line, or reinstall the port. 979 980 An easy way to handle the mass-update of /etc/rc.d: 981 rm /etc/rc.d/* && mergemaster -i 982 98320120109: 984 panic(9) now stops other CPUs in the SMP systems, disables interrupts 985 on the current CPU and prevents other threads from running. 986 This behavior can be reverted using the kern.stop_scheduler_on_panic 987 tunable/sysctl. 988 The new behavior can be incompatible with kern.sync_on_panic. 989 99020111215: 991 The carp(4) facility has been changed significantly. Configuration 992 of the CARP protocol via ifconfig(8) has changed, as well as format 993 of CARP events submitted to devd(8) has changed. See manual pages 994 for more information. The arpbalance feature of carp(4) is currently 995 not supported anymore. 996 997 Size of struct in_aliasreq, struct in6_aliasreq has changed. User 998 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8), 999 need to be recompiled. 1000 100120111122: 1002 The acpi_wmi(4) status device /dev/wmistat has been renamed to 1003 /dev/wmistat0. 1004 100520111108: 1006 The option VFS_ALLOW_NONMPSAFE option has been added in order to 1007 explicitely support non-MPSAFE filesystems. 1008 It is on by default for all supported platform at this present 1009 time. 1010 101120111101: 1012 The broken amd(4) driver has been replaced with esp(4) in the amd64, 1013 i386 and pc98 GENERIC kernel configuration files. 1014 101520110930: 1016 sysinstall has been removed 1017 101820110923: 1019 The stable/9 branch created in subversion. This corresponds to the 1020 RELENG_9 branch in CVS. 1021 1022COMMON ITEMS: 1023 1024 General Notes 1025 ------------- 1026 Avoid using make -j when upgrading. While generally safe, there are 1027 sometimes problems using -j to upgrade. If your upgrade fails with 1028 -j, please try again without -j. From time to time in the past there 1029 have been problems using -j with buildworld and/or installworld. This 1030 is especially true when upgrading between "distant" versions (eg one 1031 that cross a major release boundary or several minor releases, or when 1032 several months have passed on the -current branch). 1033 1034 Sometimes, obscure build problems are the result of environment 1035 poisoning. This can happen because the make utility reads its 1036 environment when searching for values for global variables. To run 1037 your build attempts in an "environmental clean room", prefix all make 1038 commands with 'env -i '. See the env(1) manual page for more details. 1039 1040 When upgrading from one major version to another it is generally best 1041 to upgrade to the latest code in the currently installed branch first, 1042 then do an upgrade to the new branch. This is the best-tested upgrade 1043 path, and has the highest probability of being successful. Please try 1044 this approach before reporting problems with a major version upgrade. 1045 1046 When upgrading a live system, having a root shell around before 1047 installing anything can help undo problems. Not having a root shell 1048 around can lead to problems if pam has changed too much from your 1049 starting point to allow continued authentication after the upgrade. 1050 1051 ZFS notes 1052 --------- 1053 When upgrading the boot ZFS pool to a new version, always follow 1054 these two steps: 1055 1056 1.) recompile and reinstall the ZFS boot loader and boot block 1057 (this is part of "make buildworld" and "make installworld") 1058 1059 2.) update the ZFS boot block on your boot drive 1060 1061 The following example updates the ZFS boot block on the first 1062 partition (freebsd-boot) of a GPT partitioned drive ada0: 1063 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0" 1064 1065 Non-boot pools do not need these updates. 1066 1067 To build a kernel 1068 ----------------- 1069 If you are updating from a prior version of FreeBSD (even one just 1070 a few days old), you should follow this procedure. It is the most 1071 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 1072 1073 make kernel-toolchain 1074 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1075 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1076 1077 To test a kernel once 1078 --------------------- 1079 If you just want to boot a kernel once (because you are not sure 1080 if it works, or if you want to boot a known bad kernel to provide 1081 debugging information) run 1082 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 1083 nextboot -k testkernel 1084 1085 To just build a kernel when you know that it won't mess you up 1086 -------------------------------------------------------------- 1087 This assumes you are already running a CURRENT system. Replace 1088 ${arch} with the architecture of your machine (e.g. "i386", 1089 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc). 1090 1091 cd src/sys/${arch}/conf 1092 config KERNEL_NAME_HERE 1093 cd ../compile/KERNEL_NAME_HERE 1094 make depend 1095 make 1096 make install 1097 1098 If this fails, go to the "To build a kernel" section. 1099 1100 To rebuild everything and install it on the current system. 1101 ----------------------------------------------------------- 1102 # Note: sometimes if you are running current you gotta do more than 1103 # is listed here if you are upgrading from a really old current. 1104 1105 <make sure you have good level 0 dumps> 1106 make buildworld 1107 make kernel KERNCONF=YOUR_KERNEL_HERE 1108 [1] 1109 <reboot in single user> [3] 1110 mergemaster -Fp [5] 1111 make installworld 1112 mergemaster -Fi [4] 1113 make delete-old [6] 1114 <reboot> 1115 1116 To cross-install current onto a separate partition 1117 -------------------------------------------------- 1118 # In this approach we use a separate partition to hold 1119 # current's root, 'usr', and 'var' directories. A partition 1120 # holding "/", "/usr" and "/var" should be about 2GB in 1121 # size. 1122 1123 <make sure you have good level 0 dumps> 1124 <boot into -stable> 1125 make buildworld 1126 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1127 <maybe newfs current's root partition> 1128 <mount current's root partition on directory ${CURRENT_ROOT}> 1129 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC 1130 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1131 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1132 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1133 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1134 <reboot into current> 1135 <do a "native" rebuild/install as described in the previous section> 1136 <maybe install compatibility libraries from ports/misc/compat*> 1137 <reboot> 1138 1139 1140 To upgrade in-place from stable to current 1141 ---------------------------------------------- 1142 <make sure you have good level 0 dumps> 1143 make buildworld [9] 1144 make kernel KERNCONF=YOUR_KERNEL_HERE [8] 1145 [1] 1146 <reboot in single user> [3] 1147 mergemaster -Fp [5] 1148 make installworld 1149 mergemaster -Fi [4] 1150 make delete-old [6] 1151 <reboot> 1152 1153 Make sure that you've read the UPDATING file to understand the 1154 tweaks to various things you need. At this point in the life 1155 cycle of current, things change often and you are on your own 1156 to cope. The defaults can also change, so please read ALL of 1157 the UPDATING entries. 1158 1159 Also, if you are tracking -current, you must be subscribed to 1160 freebsd-current@freebsd.org. Make sure that before you update 1161 your sources that you have read and understood all the recent 1162 messages there. If in doubt, please track -stable which has 1163 much fewer pitfalls. 1164 1165 [1] If you have third party modules, such as vmware, you 1166 should disable them at this point so they don't crash your 1167 system on reboot. 1168 1169 [3] From the bootblocks, boot -s, and then do 1170 fsck -p 1171 mount -u / 1172 mount -a 1173 cd src 1174 adjkerntz -i # if CMOS is wall time 1175 Also, when doing a major release upgrade, it is required that 1176 you boot into single user mode to do the installworld. 1177 1178 [4] Note: This step is non-optional. Failure to do this step 1179 can result in a significant reduction in the functionality of the 1180 system. Attempting to do it by hand is not recommended and those 1181 that pursue this avenue should read this file carefully, as well 1182 as the archives of freebsd-current and freebsd-hackers mailing lists 1183 for potential gotchas. The -U option is also useful to consider. 1184 See mergemaster(8) for more information. 1185 1186 [5] Usually this step is a noop. However, from time to time 1187 you may need to do this if you get unknown user in the following 1188 step. It never hurts to do it all the time. You may need to 1189 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1190 install) after the buildworld before this step if you last updated 1191 from current before 20130425 or from -stable before 20130430. 1192 1193 [6] This only deletes old files and directories. Old libraries 1194 can be deleted by "make delete-old-libs", but you have to make 1195 sure that no program is using those libraries anymore. 1196 1197 [8] In order to have a kernel that can run the 4.x binaries needed to 1198 do an installworld, you must include the COMPAT_FREEBSD4 option in 1199 your kernel. Failure to do so may leave you with a system that is 1200 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is 1201 required to run the 5.x binaries on more recent kernels. And so on 1202 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7. 1203 1204 Make sure that you merge any new devices from GENERIC since the 1205 last time you updated your kernel config file. 1206 1207 [9] When checking out sources, you must include the -P flag to have 1208 cvs prune empty directories. 1209 1210 If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1211 "?=" instead of the "=" assignment operator, so that buildworld can 1212 override the CPUTYPE if it needs to. 1213 1214 MAKEOBJDIRPREFIX must be defined in an environment variable, and 1215 not on the command line, or in /etc/make.conf. buildworld will 1216 warn if it is improperly defined. 1217FORMAT: 1218 1219This file contains a list, in reverse chronological order, of major 1220breakages in tracking -current. It is not guaranteed to be a complete 1221list of such breakages, and only contains entries since October 10, 2007. 1222If you need to see UPDATING entries from before that date, you will need 1223to fetch an UPDATING file from an older FreeBSD release. 1224 1225Copyright information: 1226 1227Copyright 1998-2009 M. Warner Losh. All Rights Reserved. 1228 1229Redistribution, publication, translation and use, with or without 1230modification, in full or in part, in any form or format of this 1231document are permitted without further permission from the author. 1232 1233THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1234IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1235WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1236DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1237INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1238(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1239SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1240HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1241STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1242IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1243POSSIBILITY OF SUCH DAMAGE. 1244 1245Contact Warner Losh if you have any questions about your use of 1246this document. 1247 1248$FreeBSD$ 1249