UPDATING revision 270403
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 to bootstrap to the tip of 16stable/10, and then rebuild without this option. The bootstrap process from 17older version of current is a bit fragile. 18 1920140814: 20 The ixgbe tunables now match their sysctl counterparts, for example: 21 hw.ixgbe.enable_aim => hw.ix.enable_aim 22 Anyone using ixgbe tunables should ensure they update /boot/loader.conf. 23 2420140801: 25 The NFSv4.1 server committed by r269398 changes the internal 26 function call interfaces used between the NFS and krpc modules. 27 As such, __FreeBSD_version was bumped. 28 2920140729: 30 The default unbound configuration has been modified to address 31 issues with reverse lookups on networks that use private 32 address ranges. If you use the local_unbound service, run 33 "service local_unbound setup" as root to regenerate your 34 configuration, then "service local_unbound reload" to load the 35 new configuration. 36 3720140717: 38 It is no longer necessary to include the dwarf version in your DEBUG 39 options in your kernel config file. The bug that required it to be 40 placed in the config file has bene fixed. DEBUG should now just 41 contain -g. The build system will automatically update things 42 to do the right thing. 43 4420140715: 45 Several ABI breaking changes were merged to CTL and new iSCSI code. 46 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and 47 iscsictl need to be rebuilt to work with a new kernel. 48 4920140708: 50 The WITHOUT_VT_SUPPORT kernel config knob has been renamed 51 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning 52 which differs from the behaviour controlled by this knob.) 53 5420140608: 55 On i386 and amd64 systems, the onifconsole flag is now set by default 56 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled 57 as a login TTY if it is set in the bootloader as an active kernel 58 console. No changes in behavior should result otherwise. To revert to 59 the previous behavior, set ttyu0 to "off" in /etc/ttys. 60 6120140512: 62 Clang and llvm have been upgraded to 3.4.1 release. 63 6420140321: 65 Clang and llvm have been upgraded to 3.4 release. 66 6720140306: 68 If a Makefile in a tests/ directory was auto-generating a Kyuafile 69 instead of providing an explicit one, this would prevent such 70 Makefile from providing its own Kyuafile in the future during 71 NO_CLEAN builds. This has been fixed in the Makefiles but manual 72 intervention is needed to clean an objdir if you use NO_CLEAN: 73 # find /usr/obj -name Kyuafile | xargs rm -f 74 7520140303: 76 OpenSSH will now ignore errors caused by kernel lacking of Capsicum 77 capability mode support. Please note that enabling the feature in 78 kernel is still highly recommended. 79 8020140227: 81 OpenSSH is now built with sandbox support, and will use sandbox as 82 the default privilege separation method. This requires Capsicum 83 capability mode support in kernel. 84 8520140216: 86 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has 87 been deprecated and will not be part of FreeBSD 11.0 and later 88 releases. If you use this driver, please consider switching to 89 the nfe(4) driver instead. 90 9120140120: 92 10.0-RELEASE. 93 9420131216: 95 The behavior of gss_pseudo_random() for the krb5 mechanism 96 has changed, for applications requesting a longer random string 97 than produced by the underlying enctype's pseudo-random() function. 98 In particular, the random string produced from a session key of 99 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will 100 be different at the 17th octet and later, after this change. 101 The counter used in the PRF+ construction is now encoded as a 102 big-endian integer in accordance with RFC 4402. 103 __FreeBSD_version is bumped to 1000701. 104 10520131108: 106 The WITHOUT_ATF build knob has been removed and its functionality 107 has been subsumed into the more generic WITHOUT_TESTS. If you were 108 using the former to disable the build of the ATF libraries, you 109 should change your settings to use the latter. 110 11120131031: 112 The default version of mtree is nmtree which is obtained from 113 NetBSD. The output is generally the same, but may vary 114 slightly. If you found you need identical output adding 115 "-F freebsd9" to the command line should do the trick. For the 116 time being, the old mtree is available as fmtree. 117 11820131014: 119 libbsdyml has been renamed to libyaml and moved to /usr/lib/private. 120 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg 121 1.1.4_8 and verify bsdyml not linked in, before running "make 122 delete-old-libs": 123 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean 124 or 125 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml 126 12720131010: 128 The rc.d/jail script has been updated to support jail(8) 129 configuration file. The "jail_<jname>_*" rc.conf(5) variables 130 for per-jail configuration are automatically converted to 131 /var/run/jail.<jname>.conf before the jail(8) utility is invoked. 132 This is transparently backward compatible. See below about some 133 incompatibilities and rc.conf(5) manual page for more details. 134 135 These variables are now deprecated in favor of jail(8) configuration 136 file. One can use "rc.d/jail config <jname>" command to generate 137 a jail(8) configuration file in /var/run/jail.<jname>.conf without 138 running the jail(8) utility. The default pathname of the 139 configuration file is /etc/jail.conf and can be specified by 140 using $jail_conf or $jail_<jname>_conf variables. 141 142 Please note that jail_devfs_ruleset accepts an integer at 143 this moment. Please consider to rewrite the ruleset name 144 with an integer. 145 14620130930: 147 BIND has been removed from the base system. If all you need 148 is a local resolver, simply enable and start the local_unbound 149 service instead. Otherwise, several versions of BIND are 150 available in the ports tree. The dns/bind99 port is one example. 151 152 With this change, nslookup(1) and dig(1) are no longer in the base 153 system. Users should instead use host(1) and drill(1) which are 154 in the base system. Alternatively, nslookup and dig can 155 be obtained by installing the dns/bind-tools port. 156 15720130916: 158 With the addition of unbound(8), a new unbound user is now 159 required during installworld. "mergemaster -p" can be used to 160 add the user prior to installworld, as documented in the handbook. 161 16220130911: 163 OpenSSH is now built with DNSSEC support, and will by default 164 silently trust signed SSHFP records. This can be controlled with 165 the VerifyHostKeyDNS client configuration setting. DNSSEC support 166 can be disabled entirely with the WITHOUT_LDNS option in src.conf. 167 16820130906: 169 The GNU Compiler Collection and C++ standard library (libstdc++) 170 are no longer built by default on platforms where clang is the system 171 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX 172 options in src.conf. 173 17420130905: 175 The PROCDESC kernel option is now part of the GENERIC kernel 176 configuration and is required for the rwhod(8) to work. 177 If you are using custom kernel configuration, you should include 178 'options PROCDESC'. 179 18020130905: 181 The API and ABI related to the Capsicum framework was modified 182 in backward incompatible way. The userland libraries and programs 183 have to be recompiled to work with the new kernel. This includes the 184 following libraries and programs, but the whole buildworld is 185 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl, 186 kdump, procstat, rwho, rwhod, uniq. 187 18820130903: 189 AES-NI intrinsic support has been added to gcc. The AES-NI module 190 has been updated to use this support. A new gcc is required to build 191 the aesni module on both i386 and amd64. 192 19320130821: 194 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices. 195 Thus "device padlock_rng" and "device rdrand_rng" should be 196 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG". 197 19820130813: 199 WITH_ICONV has been split into two feature sets. WITH_ICONV now 200 enables just the iconv* functionality and is now on by default. 201 WITH_LIBICONV_COMPAT enables the libiconv api and link time 202 compatability. Set WITHOUT_ICONV to build the old way. 203 If you have been using WITH_ICONV before, you will very likely 204 need to turn on WITH_LIBICONV_COMPAT. 205 20620130806: 207 INVARIANTS option now enables DEBUG for code with OpenSolaris and 208 Illumos origin, including ZFS. If you have INVARIANTS in your 209 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG 210 explicitly. 211 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS) 212 locks if WITNESS option was set. Because that generated a lot of 213 witness(9) reports and all of them were believed to be false 214 positives, this is no longer done. New option OPENSOLARIS_WITNESS 215 can be used to achieve the previous behavior. 216 21720130806: 218 Timer values in IPv6 data structures now use time_uptime instead 219 of time_second. Although this is not a user-visible functional 220 change, userland utilities which directly use them---ndp(8), 221 rtadvd(8), and rtsold(8) in the base system---need to be updated 222 to r253970 or later. 223 22420130802: 225 find -delete can now delete the pathnames given as arguments, 226 instead of only files found below them or if the pathname did 227 not contain any slashes. Formerly, the following error message 228 would result: 229 230 find: -delete: <path>: relative path potentially not safe 231 232 Deleting the pathnames given as arguments can be prevented 233 without error messages using -mindepth 1 or by changing 234 directory and passing "." as argument to find. This works in the 235 old as well as the new version of find. 236 23720130726: 238 Behavior of devfs rules path matching has been changed. 239 Pattern is now always matched against fully qualified devfs 240 path and slash characters must be explicitly matched by 241 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs 242 subdirectories must be reviewed. 243 24420130716: 245 The default ARM ABI has changed to the ARM EABI. The old ABI is 246 incompatible with the ARM EABI and all programs and modules will 247 need to be rebuilt to work with a new kernel. 248 249 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set. 250 251 NOTE: Support for the old ABI will be removed in the future and 252 users are advised to upgrade. 253 25420130709: 255 pkg_install has been disconnected from the build if you really need it 256 you should add WITH_PKGTOOLS in your src.conf(5). 257 25820130709: 259 Most of network statistics structures were changed to be able 260 keep 64-bits counters. Thus all tools, that work with networking 261 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.) 262 26320130629: 264 Fix targets that run multiple make's to use && rather than ; 265 so that subsequent steps depend on success of previous. 266 267 NOTE: if building 'universe' with -j* on stable/8 or stable/9 268 it would be better to start the build using bmake, to avoid 269 overloading the machine. 270 27120130618: 272 Fix a bug that allowed a tracing process (e.g. gdb) to write 273 to a memory-mapped file in the traced process's address space 274 even if neither the traced process nor the tracing process had 275 write access to that file. 276 27720130615: 278 CVS has been removed from the base system. An exact copy 279 of the code is available from the devel/cvs port. 280 28120130613: 282 Some people report the following error after the switch to bmake: 283 284 make: illegal option -- J 285 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] 286 ... 287 *** [buildworld] Error code 2 288 289 this likely due to an old instance of make in 290 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE}) 291 which src/Makefile will use that blindly, if it exists, so if 292 you see the above error: 293 294 rm -rf `make -V MAKEPATH` 295 296 should resolve it. 297 29820130516: 299 Use bmake by default. 300 Whereas before one could choose to build with bmake via 301 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old 302 make. The goal is to remove these knobs for 10-RELEASE. 303 304 It is worth noting that bmake (like gmake) treats the command 305 line as the unit of failure, rather than statements within the 306 command line. Thus '(cd some/where && dosomething)' is safer 307 than 'cd some/where; dosomething'. The '()' allows consistent 308 behavior in parallel build. 309 31020130429: 311 Fix a bug that allows NFS clients to issue READDIR on files. 312 31320130426: 314 The WITHOUT_IDEA option has been removed because 315 the IDEA patent expired. 316 31720130426: 318 The sysctl which controls TRIM support under ZFS has been renamed 319 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been 320 enabled by default. 321 32220130425: 323 The mergemaster command now uses the default MAKEOBJDIRPREFIX 324 rather than creating it's own in the temporary directory in 325 order allow access to bootstrapped versions of tools such as 326 install and mtree. When upgrading from version of FreeBSD where 327 the install command does not support -l, you will need to 328 install a new mergemaster command if mergemaster -p is required. 329 This can be accomplished with the command (cd src/usr.sbin/mergemaster 330 && make install). 331 33220130404: 333 Legacy ATA stack, disabled and replaced by new CAM-based one since 334 FreeBSD 9.0, completely removed from the sources. Kernel modules 335 atadisk and atapi*, user-level tools atacontrol and burncd are 336 removed. Kernel option `options ATA_CAM` is now permanently enabled 337 and removed. 338 33920130319: 340 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2) 341 and socketpair(2). Software, in particular Kerberos, may 342 automatically detect and use these during building. The resulting 343 binaries will not work on older kernels. 344 34520130308: 346 CTL_DISABLE has also been added to the sparc64 GENERIC (for further 347 information, see the respective 20130304 entry). 348 34920130304: 350 Recent commits to callout(9) changed the size of struct callout, 351 so the KBI is probably heavily disturbed. Also, some functions 352 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced 353 by macros. Every kernel module using it won't load, so rebuild 354 is requested. 355 356 The ctl device has been re-enabled in GENERIC for i386 and amd64, 357 but does not initialize by default (because of the new CTL_DISABLE 358 option) to save memory. To re-enable it, remove the CTL_DISABLE 359 option from the kernel config file or set kern.cam.ctl.disable=0 360 in /boot/loader.conf. 361 36220130301: 363 The ctl device has been disabled in GENERIC for i386 and amd64. 364 This was done due to the extra memory being allocated at system 365 initialisation time by the ctl driver which was only used if 366 a CAM target device was created. This makes a FreeBSD system 367 unusable on 128MB or less of RAM. 368 36920130208: 370 A new compression method (lz4) has been merged to -HEAD. Please 371 refer to zpool-features(7) for more information. 372 373 Please refer to the "ZFS notes" section of this file for information 374 on upgrading boot ZFS pools. 375 37620130129: 377 A BSD-licensed patch(1) variant has been added and is installed 378 as bsdpatch, being the GNU version the default patch. 379 To inverse the logic and use the BSD-licensed one as default, 380 while having the GNU version installed as gnupatch, rebuild 381 and install world with the WITH_BSD_PATCH knob set. 382 38320130121: 384 Due to the use of the new -l option to install(1) during build 385 and install, you must take care not to directly set the INSTALL 386 make variable in your /etc/make.conf, /etc/src.conf, or on the 387 command line. If you wish to use the -C flag for all installs 388 you may be able to add INSTALL+=-C to /etc/make.conf or 389 /etc/src.conf. 390 39120130118: 392 The install(1) option -M has changed meaning and now takes an 393 argument that is a file or path to append logs to. In the 394 unlikely event that -M was the last option on the command line 395 and the command line contained at least two files and a target 396 directory the first file will have logs appended to it. The -M 397 option served little practical purpose in the last decade so its 398 use is expected to be extremely rare. 399 40020121223: 401 After switching to Clang as the default compiler some users of ZFS 402 on i386 systems started to experience stack overflow kernel panics. 403 Please consider using 'options KSTACK_PAGES=4' in such configurations. 404 40520121222: 406 GEOM_LABEL now mangles label names read from file system metadata. 407 Mangling affect labels containing spaces, non-printable characters, 408 '%' or '"'. Device names in /etc/fstab and other places may need to 409 be updated. 410 41120121217: 412 By default, only the 10 most recent kernel dumps will be saved. To 413 restore the previous behaviour (no limit on the number of kernel dumps 414 stored in the dump directory) add the following line to /etc/rc.conf: 415 416 savecore_flags="" 417 41820121201: 419 With the addition of auditdistd(8), a new auditdistd user is now 420 required during installworld. "mergemaster -p" can be used to 421 add the user prior to installworld, as documented in the handbook. 422 42320121117: 424 The sin6_scope_id member variable in struct sockaddr_in6 is now 425 filled by the kernel before passing the structure to the userland via 426 sysctl or routing socket. This means the KAME-specific embedded scope 427 id in sin6_addr.s6_addr[2] is always cleared in userland application. 428 This behavior can be controlled by net.inet6.ip6.deembed_scopeid. 429 __FreeBSD_version is bumped to 1000025. 430 43120121105: 432 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default. 433 This means that the world and kernel will be compiled with clang 434 and that clang will be installed as /usr/bin/cc, /usr/bin/c++, 435 and /usr/bin/cpp. To disable this behavior and revert to building 436 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions 437 of current may need to bootstrap WITHOUT_CLANG first if the clang 438 build fails (its compatibility window doesn't extend to the 9 stable 439 branch point). 440 44120121102: 442 The IPFIREWALL_FORWARD kernel option has been removed. Its 443 functionality now turned on by default. 444 44520121023: 446 The ZERO_COPY_SOCKET kernel option has been removed and 447 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP. 448 NB: SOCKET_SEND_COW uses the VM page based copy-on-write 449 mechanism which is not safe and may result in kernel crashes. 450 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current 451 driver supports disposeable external page sized mbuf storage. 452 Proper replacements for both zero-copy mechanisms are under 453 consideration and will eventually lead to complete removal 454 of the two kernel options. 455 45620121023: 457 The IPv4 network stack has been converted to network byte 458 order. The following modules need to be recompiled together 459 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4), 460 pf(4), ipfw(4), ng_ipfw(4), stf(4). 461 46220121022: 463 Support for non-MPSAFE filesystems was removed from VFS. The 464 VFS_VERSION was bumped, all filesystem modules shall be 465 recompiled. 466 46720121018: 468 All the non-MPSAFE filesystems have been disconnected from 469 the build. The full list includes: codafs, hpfs, ntfs, nwfs, 470 portalfs, smbfs, xfs. 471 47220121016: 473 The interface cloning API and ABI has changed. The following 474 modules need to be recompiled together with kernel: 475 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4), 476 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4), 477 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4). 478 47920121015: 480 The sdhci driver was split in two parts: sdhci (generic SD Host 481 Controller logic) and sdhci_pci (actual hardware driver). 482 No kernel config modifications are required, but if you 483 load sdhc as a module you must switch to sdhci_pci instead. 484 48520121014: 486 Import the FUSE kernel and userland support into base system. 487 48820121013: 489 The GNU sort(1) program has been removed since the BSD-licensed 490 sort(1) has been the default for quite some time and no serious 491 problems have been reported. The corresponding WITH_GNU_SORT 492 knob has also gone. 493 49420121006: 495 The pfil(9) API/ABI for AF_INET family has been changed. Packet 496 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled 497 with new kernel. 498 49920121001: 500 The net80211(4) ABI has been changed to allow for improved driver 501 PS-POLL and power-save support. All wireless drivers need to be 502 recompiled to work with the new kernel. 503 50420120913: 505 The random(4) support for the VIA hardware random number 506 generator (`PADLOCK') is no longer enabled unconditionally. 507 Add the padlock_rng device in the custom kernel config if 508 needed. The GENERIC kernels on i386 and amd64 do include the 509 device, so the change only affects the custom kernel 510 configurations. 511 51220120908: 513 The pf(4) packet filter ABI has been changed. pfctl(8) and 514 snmp_pf module need to be recompiled to work with new kernel. 515 51620120828: 517 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged 518 to -HEAD. Pools that have empty_bpobj in active state can not be 519 imported read-write with ZFS implementations that do not support 520 this feature. For more information read the zpool-features(5) 521 manual page. 522 52320120727: 524 The sparc64 ZFS loader has been changed to no longer try to auto- 525 detect ZFS providers based on diskN aliases but now requires these 526 to be explicitly listed in the OFW boot-device environment variable. 527 52820120712: 529 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring 530 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are 531 configuration changes. Make sure to merge /etc/ssl/openssl.cnf. 532 53320120712: 534 The following sysctls and tunables have been renamed for consistency 535 with other variables: 536 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered 537 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered 538 53920120628: 540 The sort utility has been replaced with BSD sort. For now, GNU sort 541 is also available as "gnusort" or the default can be set back to 542 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be 543 installed as "bsdsort". 544 54520120611: 546 A new version of ZFS (pool version 5000) has been merged to -HEAD. 547 Starting with this version the old system of ZFS pool versioning 548 is superseded by "feature flags". This concept enables forward 549 compatibility against certain future changes in functionality of ZFS 550 pools. The first read-only compatible "feature flag" for ZFS pools 551 is named "com.delphix:async_destroy". For more information 552 read the new zpool-features(5) manual page. 553 Please refer to the "ZFS notes" section of this file for information 554 on upgrading boot ZFS pools. 555 55620120417: 557 The malloc(3) implementation embedded in libc now uses sources imported 558 as contrib/jemalloc. The most disruptive API change is to 559 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf, 560 delete it prior to installworld, and optionally re-create it using the 561 new format after rebooting. See malloc.conf(5) for details 562 (specifically the TUNING section and the "opt.*" entries in the MALLCTL 563 NAMESPACE section). 564 56520120328: 566 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb 567 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is 568 now spelled mips. This is to aid compatibility with third-party 569 software that expects this naming scheme in uname(3). Little-endian 570 settings are unchanged. If you are updating a big-endian mips64 machine 571 from before this change, you may need to set MACHINE_ARCH=mips64 in 572 your environment before the new build system will recognize your machine. 573 57420120306: 575 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported 576 platforms. 577 57820120229: 579 Now unix domain sockets behave "as expected" on nullfs(5). Previously 580 nullfs(5) did not pass through all behaviours to the underlying layer, 581 as a result if we bound to a socket on the lower layer we could connect 582 only to the lower path; if we bound to the upper layer we could connect 583 only to the upper path. The new behavior is one can connect to both the 584 lower and the upper paths regardless what layer path one binds to. 585 58620120211: 587 The getifaddrs upgrade path broken with 20111215 has been restored. 588 If you have upgraded in between 20111215 and 20120209 you need to 589 recompile libc again with your kernel. You still need to recompile 590 world to be able to configure CARP but this restriction already 591 comes from 20111215. 592 59320120114: 594 The set_rcvar() function has been removed from /etc/rc.subr. All 595 base and ports rc.d scripts have been updated, so if you have a 596 port installed with a script in /usr/local/etc/rc.d you can either 597 hand-edit the rcvar= line, or reinstall the port. 598 599 An easy way to handle the mass-update of /etc/rc.d: 600 rm /etc/rc.d/* && mergemaster -i 601 60220120109: 603 panic(9) now stops other CPUs in the SMP systems, disables interrupts 604 on the current CPU and prevents other threads from running. 605 This behavior can be reverted using the kern.stop_scheduler_on_panic 606 tunable/sysctl. 607 The new behavior can be incompatible with kern.sync_on_panic. 608 60920111215: 610 The carp(4) facility has been changed significantly. Configuration 611 of the CARP protocol via ifconfig(8) has changed, as well as format 612 of CARP events submitted to devd(8) has changed. See manual pages 613 for more information. The arpbalance feature of carp(4) is currently 614 not supported anymore. 615 616 Size of struct in_aliasreq, struct in6_aliasreq has changed. User 617 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8), 618 need to be recompiled. 619 62020111122: 621 The acpi_wmi(4) status device /dev/wmistat has been renamed to 622 /dev/wmistat0. 623 62420111108: 625 The option VFS_ALLOW_NONMPSAFE option has been added in order to 626 explicitely support non-MPSAFE filesystems. 627 It is on by default for all supported platform at this present 628 time. 629 63020111101: 631 The broken amd(4) driver has been replaced with esp(4) in the amd64, 632 i386 and pc98 GENERIC kernel configuration files. 633 63420110930: 635 sysinstall has been removed 636 63720110923: 638 The stable/9 branch created in subversion. This corresponds to the 639 RELENG_9 branch in CVS. 640 64120110913: 642 This commit modifies vfs_register() so that it uses a hash 643 calculation to set vfc_typenum, which is enabled by default. 644 The first time a system is booted after this change, the 645 vfc_typenum values will change for all file systems. The 646 main effect of this is a change to the NFS server file handles 647 for file systems that use vfc_typenum in their fsid, such as ZFS. 648 It will, however, prevent vfc_typenum from changing when file 649 systems are loaded in a different order for subsequent reboots. 650 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf 651 until you are ready to remount all NFS clients after a reboot. 652 65320110828: 654 Bump the shared library version numbers for libraries that 655 do not use symbol versioning, have changed the ABI compared 656 to stable/8 and which shared library version was not bumped. 657 Done as part of 9.0-RELEASE cycle. 658 65920110815: 660 During the merge of Capsicum features, the fget(9) KPI was modified. 661 This may require the rebuilding of out-of-tree device drivers -- 662 issues have been reported specifically with the nVidia device driver. 663 __FreeBSD_version is bumped to 900041. 664 665 Also, there is a period between 20110811 and 20110814 where the 666 special devices /dev/{stdin,stdout,stderr} did not work correctly. 667 Building world from a kernel during that window may not work. 668 66920110628: 670 The packet filter (pf) code has been updated to OpenBSD 4.5. 671 You need to update userland tools to be in sync with kernel. 672 This update breaks backward compatibility with earlier pfsync(4) 673 versions. Care must be taken when updating redundant firewall setups. 674 67520110608: 676 The following sysctls and tunables are retired on x86 platforms: 677 machdep.hlt_cpus 678 machdep.hlt_logical_cpus 679 The following sysctl is retired: 680 machdep.hyperthreading_allowed 681 The sysctls were supposed to provide a way to dynamically offline and 682 online selected CPUs on x86 platforms, but the implementation has not 683 been reliable especially with SCHED_ULE scheduler. 684 machdep.hyperthreading_allowed tunable is still available to ignore 685 hyperthreading CPUs at OS level. 686 Individual CPUs can be disabled using hint.lapic.X.disabled tunable, 687 where X is an APIC ID of a CPU. Be advised, though, that disabling 688 CPUs in non-uniform fashion will result in non-uniform topology and 689 may lead to sub-optimal system performance with SCHED_ULE, which is 690 a default scheduler. 691 69220110607: 693 cpumask_t type is retired and cpuset_t is used in order to describe 694 a mask of CPUs. 695 69620110531: 697 Changes to ifconfig(8) for dynamic address family detection mandate 698 that you are running a kernel of 20110525 or later. Make sure to 699 follow the update procedure to boot a new kernel before installing 700 world. 701 70220110513: 703 Support for sun4v architecture is officially dropped 704 70520110503: 706 Several KPI breaking changes have been committed to the mii(4) layer, 707 the PHY drivers and consequently some Ethernet drivers using mii(4). 708 This means that miibus.ko and the modules of the affected Ethernet 709 drivers need to be recompiled. 710 711 Note to kernel developers: Given that the OUI bit reversion problem 712 was fixed as part of these changes all mii(4) commits related to OUIs, 713 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific 714 handling, no longer can be merged verbatim to stable/8 and previous 715 branches. 716 71720110430: 718 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci' 719 into their kernel configurations along with 'device pci'. 720 72120110427: 722 The default NFS client is now the new NFS client, so fstype "newnfs" 723 is now "nfs" and the regular/old NFS client is now fstype "oldnfs". 724 Although mounts via fstype "nfs" will usually work without userland 725 changes, it is recommended that the mount(8) and mount_nfs(8) 726 commands be rebuilt from sources and that a link to mount_nfs called 727 mount_oldnfs be created. The new client is compiled into the 728 kernel with "options NFSCL" and this is needed for diskless root 729 file systems. The GENERIC kernel configs have been changed to use 730 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER. 731 To use the regular/old client, you can "mount -t oldnfs ...". For 732 a diskless root file system, you must also include a line like: 733 734 vfs.root.mountfrom="oldnfs:" 735 736 in the boot/loader.conf on the root fs on the NFS server to make 737 a diskless root fs use the old client. 738 73920110424: 740 The GENERIC kernels for all architectures now default to the new 741 CAM-based ATA stack. It means that all legacy ATA drivers were 742 removed and replaced by respective CAM drivers. If you are using 743 ATA device names in /etc/fstab or other places, make sure to update 744 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY, 745 where 'Y's are the sequential numbers starting from zero for each type 746 in order of detection, unless configured otherwise with tunables, 747 see cam(4)). There will be symbolic links created in /dev/ to map 748 old adX devices to the respective adaY. They should provide basic 749 compatibility for file systems mounting in most cases, but they do 750 not support old user-level APIs and do not have respective providers 751 in GEOM. Consider using updated management tools with new device names. 752 753 It is possible to load devices ahci, ata, siis and mvs as modules, 754 but option ATA_CAM should remain in kernel configuration to make ata 755 module work as CAM driver supporting legacy ATA controllers. Device ata 756 still can be used in modular fashion (atacore + ...). Modules atadisk 757 and atapi* are not used and won't affect operation in ATA_CAM mode. 758 Note that to use CAM-based ATA kernel should include CAM devices 759 scbus, pass, da (or explicitly ada), cd and optionally others. All of 760 them are parts of the cam module. 761 762 ataraid(4) functionality is now supported by the RAID GEOM class. 763 To use it you can load geom_raid kernel module and use graid(8) tool 764 for management. Instead of /dev/arX device names, use /dev/raid/rX. 765 766 No kernel config options or code have been removed, so if a problem 767 arises, please report it and optionally revert to the old ATA stack. 768 In order to do it you can remove from the kernel config: 769 options ATA_CAM 770 device ahci 771 device mvs 772 device siis 773 , and instead add back: 774 device atadisk # ATA disk drives 775 device ataraid # ATA RAID drives 776 device atapicd # ATAPI CDROM drives 777 device atapifd # ATAPI floppy drives 778 device atapist # ATAPI tape drives 779 78020110423: 781 The default NFS server has been changed to the new server, which 782 was referred to as the experimental server. If you need to switch 783 back to the old NFS server, you must now put the "-o" option on 784 both the mountd and nfsd commands. This can be done using the 785 mountd_flags and nfs_server_flags rc.conf variables until an 786 update to the rc scripts is committed, which is coming soon. 787 78820110418: 789 The GNU Objective-C runtime library (libobjc), and other Objective-C 790 related components have been removed from the base system. If you 791 require an Objective-C library, please use one of the available ports. 792 79320110331: 794 ath(4) has been split into bus- and device- modules. if_ath contains 795 the HAL, the TX rate control and the network device code. if_ath_pci 796 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb 797 contains the AHB glue. Users need to load both if_ath_pci and if_ath 798 in order to use ath on everything else. 799 800 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only 801 need to load if_ath and if_ath_pci for ath(4) operation. 802 80320110314: 804 As part of the replacement of sysinstall, the process of building 805 release media has changed significantly. For details, please re-read 806 release(7), which has been updated to reflect the new build process. 807 80820110218: 809 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This 810 is the last available version under GPLv2. It brings a number of new 811 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE 812 4.1 and SSE 4.2), better support for powerpc64, a number of new 813 directives, and lots of other small improvements. See the ChangeLog 814 file in contrib/binutils for the full details. 815 81620110218: 817 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868 818 compliant, and will now use half of hash for authentication. 819 This will break interoperability with all stacks (including all 820 actual FreeBSD versions) who implement 821 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for 822 authentication). 823 The only workaround with such peers is to use another HMAC 824 algorithm for IPsec ("phase 2") authentication. 825 82620110207: 827 Remove the uio_yield prototype and symbol. This function has 828 been misnamed since it was introduced and should not be 829 globally exposed with this name. The equivalent functionality 830 is now available using kern_yield(curthread->td_user_pri). 831 The function remains undocumented. 832 83320110112: 834 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers, 835 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking 836 for scalar sysctls is defined but disabled. Code that needs 837 UQUAD to pass the type checking that must compile on older 838 systems where the define is not present can check against 839 __FreeBSD_version >= 900030. 840 841 The system dialog(1) has been replaced with a new version previously 842 in ports as devel/cdialog. dialog(1) is mostly command-line compatible 843 with the previous version, but the libdialog associated with it has 844 a largely incompatible API. As such, the original version of libdialog 845 will be kept temporarily as libodialog, until its base system consumers 846 are replaced or updated. Bump __FreeBSD_version to 900030. 847 84820110103: 849 If you are trying to run make universe on a -stable system, and you get 850 the following warning: 851 "Makefile", line 356: "Target architecture for i386/conf/GENERIC 852 unknown. config(8) likely too old." 853 or something similar to it, then you must upgrade your -stable system 854 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in 855 stable/8) or build the config from the latest stable/8 branch and 856 install it on your system. 857 858 Prior to this date, building a current universe on 8-stable system from 859 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing 860 error in the first kernel build phase. A new config on those old 861 systems will fix that problem for older versions of -current. 862 86320101228: 864 The TCP stack has been modified to allow Khelp modules to interact with 865 it via helper hook points and store per-connection data in the TCP 866 control block. Bump __FreeBSD_version to 900029. User space tools that 867 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to 868 be recompiled. 869 87020101114: 871 Generic IEEE 802.3 annex 31B full duplex flow control support has been 872 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along 873 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted 874 to take advantage of it instead of using custom implementations. This 875 means that these drivers now no longer unconditionally advertise 876 support for flow control but only do so if flow control is a selected 877 media option. This was implemented in the generic support that way in 878 order to allow flow control to be switched on and off via ifconfig(8) 879 with the PHY specific default to typically off in order to protect 880 from unwanted effects. Consequently, if you used flow control with 881 one of the above mentioned drivers you now need to explicitly enable 882 it, for example via: 883 ifconfig bge0 media auto mediaopt flowcontrol 884 885 Along with the above mentioned changes generic support for setting 886 1000baseT master mode also has been added and brgphy(4), ciphy(4), 887 e1000phy(4) as well as ip1000phy(4) have been converted to take 888 advantage of it. This means that these drivers now no longer take the 889 link0 parameter for selecting master mode but the master media option 890 has to be used instead, for example like in the following: 891 ifconfig bge0 media 1000baseT mediaopt full-duplex,master 892 893 Selection of master mode now is also available with all other PHY 894 drivers supporting 1000baseT. 895 89620101111: 897 The TCP stack has received a significant update to add support for 898 modularised congestion control and generally improve the clarity of 899 congestion control decisions. Bump __FreeBSD_version to 900025. User 900 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g. 901 sockstat) need to be recompiled. 902 90320101002: 904 The man(1) utility has been replaced by a new version that no longer 905 uses /etc/manpath.config. Please consult man.conf(5) for how to 906 migrate local entries to the new format. 907 90820100928: 909 The copyright strings printed by login(1) and sshd(8) at the time of a 910 new connection have been removed to follow other operating systems and 911 upstream sshd. 912 91320100915: 914 A workaround for a fixed ld bug has been removed in kernel code, 915 so make sure that your system ld is built from sources after 916 revision 210245 from 2010-07-19 (r211583 if building head kernel 917 on stable/8, r211584 for stable/7; both from 2010-08-21). 918 A symptom of incorrect ld version is different addresses for 919 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules. 920 92120100913: 922 The $ipv6_prefer variable in rc.conf(5) has been split into 923 $ip6addrctl_policy and $ipv6_activate_all_interfaces. 924 925 The $ip6addrctl_policy is a variable to choose a pre-defined 926 address selection policy set by ip6addrctl(8). A value 927 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The 928 default is "AUTO". 929 930 The $ipv6_activate_all_interfaces specifies whether IFDISABLED 931 flag (see an entry of 20090926) is set on an interface with no 932 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for 933 security reason. If you want IPv6 link-local address on all 934 interfaces by default, set this to "YES". 935 936 The old ipv6_prefer="YES" is equivalent to 937 ipv6_activate_all_interfaces="YES" and 938 ip6addrctl_policy="ipv6_prefer". 939 94020100913: 941 DTrace has grown support for userland tracing. Due to this, DTrace is 942 now i386 and amd64 only. 943 dtruss(1) is now installed by default on those systems and a new 944 kernel module is needed for userland tracing: fasttrap. 945 No changes to your kernel config file are necessary to enable 946 userland tracing, but you might consider adding 'STRIP=' and 947 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want 948 to have informative userland stack traces in DTrace (ustack). 949 95020100725: 951 The acpi_aiboost(4) driver has been removed in favor of the new 952 aibs(4) driver. You should update your kernel configuration file. 953 95420100722: 955 BSD grep has been imported to the base system and it is built by 956 default. It is completely BSD licensed, highly GNU-compatible, uses 957 less memory than its GNU counterpart and has a small codebase. 958 However, it is slower than its GNU counterpart, which is mostly 959 noticeable for larger searches, for smaller ones it is measurable 960 but not significant. The reason is complex, the most important factor 961 is that we lack a modern and efficient regex library and GNU 962 overcomes this by optimizing the searches internally. Future work 963 on improving the regex performance is planned, for the meantime, 964 users that need better performance, can build GNU grep instead by 965 setting the WITH_GNU_GREP knob. 966 96720100713: 968 Due to the import of powerpc64 support, all existing powerpc kernel 969 configuration files must be updated with a machine directive like this: 970 machine powerpc powerpc 971 972 In addition, an updated config(8) is required to build powerpc kernels 973 after this change. 974 97520100713: 976 A new version of ZFS (version 15) has been merged to -HEAD. 977 This version uses a python library for the following subcommands: 978 zfs allow, zfs unallow, zfs groupspace, zfs userspace. 979 For full functionality of these commands the following port must 980 be installed: sysutils/py-zfs 981 98220100429: 983 'vm_page's are now hashed by physical address to an array of mutexes. 984 Currently this is only used to serialize access to hold_count. Over 985 time the page queue mutex will be peeled away. This changes the size 986 of pmap on every architecture. And requires all callers of vm_page_hold 987 and vm_page_unhold to be updated. 988 98920100402: 990 WITH_CTF can now be specified in src.conf (not recommended, there 991 are some problems with static executables), make.conf (would also 992 affect ports which do not use GNU make and do not override the 993 compile targets) or in the kernel config (via "makeoptions 994 WITH_CTF=yes"). 995 When WITH_CTF was specified there before this was silently ignored, 996 so make sure that WITH_CTF is not used in places which could lead 997 to unwanted behavior. 998 99920100311: 1000 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32 1001 to allow 32-bit compatibility on non-x86 platforms. All kernel 1002 configurations on amd64 and ia64 platforms using these options must 1003 be modified accordingly. 1004 100520100113: 1006 The utmp user accounting database has been replaced with utmpx, 1007 the user accounting interface standardized by POSIX. 1008 Unfortunately the semantics of utmp and utmpx don't match, 1009 making it practically impossible to support both interfaces. 1010 The user accounting database is used by tools like finger(1), 1011 last(1), talk(1), w(1) and ac(8). 1012 1013 All applications in the base system use utmpx. This means only 1014 local binaries (e.g. from the ports tree) may still use these 1015 utmp database files. These applications must be rebuilt to make 1016 use of utmpx. 1017 1018 After the system has been upgraded, it is safe to remove the old 1019 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*), 1020 assuming their contents is of no importance anymore. Old wtmp 1021 databases can only be used by last(1) and ac(8) after they have 1022 been converted to the new format using wtmpcvt(1). 1023 102420100108: 1025 Introduce the kernel thread "deadlock resolver" (which can be enabled 1026 via the DEADLKRES option, see NOTES for more details) and the 1027 sleepq_type() function for sleepqueues. 1028 102920091202: 1030 The rc.firewall and rc.firewall6 were unified, and 1031 rc.firewall6 and rc.d/ip6fw were removed. 1032 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc 1033 variables are obsoleted. Instead, the following new rc 1034 variables are added to rc.d/ipfw: 1035 1036 firewall_client_net_ipv6, firewall_simple_iif_ipv6, 1037 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6, 1038 firewall_simple_onet_ipv6, firewall_trusted_ipv6 1039 1040 The meanings correspond to the relevant IPv4 variables. 1041 104220091125: 1043 8.0-RELEASE. 1044 104520091113: 1046 The default terminal emulation for syscons(4) has been changed 1047 from cons25 to xterm on all platforms except pc98. This means 1048 that the /etc/ttys file needs to be updated to ensure correct 1049 operation of applications on the console. 1050 1051 The terminal emulation style can be toggled per window by using 1052 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration 1053 options can be used to change the compile-time default back to 1054 cons25. 1055 1056 To prevent graphical artifacts, make sure the TERM environment 1057 variable is set to match the terminal emulation that is being 1058 performed by syscons(4). 1059 106020091109: 1061 The layout of the structure ieee80211req_scan_result has changed. 1062 Applications that require wireless scan results (e.g. ifconfig(8)) 1063 from net80211 need to be recompiled. 1064 1065 Applications such as wpa_supplicant(8) may require a full world 1066 build without using NO_CLEAN in order to get synchronized with the 1067 new structure. 1068 106920091025: 1070 The iwn(4) driver has been updated to support the 5000 and 5150 series. 1071 There's one kernel module for each firmware. Adding "device iwnfw" 1072 to the kernel configuration file means including all three firmware 1073 images inside the kernel. If you want to include just the one for 1074 your wireless card, use the devices iwn4965fw, iwn5000fw or 1075 iwn5150fw. 1076 107720090926: 1078 The rc.d/network_ipv6, IPv6 configuration script has been integrated 1079 into rc.d/netif. The changes are the following: 1080 1081 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF 1082 for IPv4. For aliases, $ifconfig_IF_aliasN should be used. 1083 Note that both variables need the "inet6" keyword at the head. 1084 1085 Do not set $ipv6_network_interfaces manually if you do not 1086 understand what you are doing. It is not needed in most cases. 1087 1088 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but 1089 they are obsolete. 1090 1091 2. $ipv6_enable is obsolete. Use $ipv6_prefer and 1092 "inet6 accept_rtadv" keyword in ifconfig(8) instead. 1093 1094 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and 1095 all configured interfaces have "inet6 accept_rtadv" in the 1096 $ifconfig_IF_ipv6. These are for backward compatibility. 1097 1098 3. A new variable $ipv6_prefer has been added. If NO, IPv6 1099 functionality of interfaces with no corresponding 1100 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag, 1101 and the default address selection policy of ip6addrctl(8) 1102 is the IPv4-preferred one (see rc.d/ip6addrctl for more details). 1103 Note that if you want to configure IPv6 functionality on the 1104 disabled interfaces after boot, first you need to clear the flag by 1105 using ifconfig(8) like: 1106 1107 ifconfig em0 inet6 -ifdisabled 1108 1109 If YES, the default address selection policy is set as 1110 IPv6-preferred. 1111 1112 The default value of $ipv6_prefer is NO. 1113 1114 4. If your system need to receive Router Advertisement messages, 1115 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8) 1116 scripts automatically invoke rtsol(8) when the interface becomes 1117 UP. The Router Advertisement messages are used for SLAAC 1118 (State-Less Address AutoConfiguration). 1119 112020090922: 1121 802.11s D3.03 support was committed. This is incompatible with the 1122 previous code, which was based on D3.0. 1123 112420090912: 1125 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value 1126 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to 1127 control whether accepting Router Advertisement messages or not. 1128 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and 1129 a sysctl variable net.inet6.ip6.auto_linklocal is its default value. 1130 The ifconfig(8) utility now supports these flags. 1131 113220090910: 1133 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for 1134 mount(8) and -a option for df(1) to see them. 1135 113620090825: 1137 The old tunable hw.bus.devctl_disable has been superseded by 1138 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be 1139 replaced by hw.bus.devctl_queue=0. The default for this new tunable 1140 is 1000. 1141 114220090813: 1143 Remove the option STOP_NMI. The default action is now to use NMI only 1144 for KDB via the newly introduced function stop_cpus_hard() and 1145 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64. 1146 114720090803: 1148 The stable/8 branch created in subversion. This corresponds to the 1149 RELENG_8 branch in CVS. 1150 115120090719: 1152 Bump the shared library version numbers for all libraries that do not 1153 use symbol versioning as part of the 8.0-RELEASE cycle. Bump 1154 __FreeBSD_version to 800105. 1155 115620090714: 1157 Due to changes in the implementation of virtual network stack support, 1158 all network-related kernel modules must be recompiled. As this change 1159 breaks the ABI, bump __FreeBSD_version to 800104. 1160 116120090713: 1162 The TOE interface to the TCP syncache has been modified to remove 1163 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack. 1164 The cxgb driver is the only TOE consumer affected by this change, and 1165 needs to be recompiled along with the kernel. As this change breaks 1166 the ABI, bump __FreeBSD_version to 800103. 1167 116820090712: 1169 Padding has been added to struct tcpcb, sackhint and tcpstat in 1170 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst 1171 maintaining the ABI. However, this change breaks the ABI, so bump 1172 __FreeBSD_version to 800102. User space tools that rely on the size of 1173 any of these structs (e.g. sockstat) need to be recompiled. 1174 117520090630: 1176 The NFS_LEGACYRPC option has been removed along with the old kernel 1177 RPC implementation that this option selected. Kernel configurations 1178 may need to be adjusted. 1179 118020090629: 1181 The network interface device nodes at /dev/net/<interface> have been 1182 removed. All ioctl operations can be performed the normal way using 1183 routing sockets. The kqueue functionality can generally be replaced 1184 with routing sockets. 1185 118620090628: 1187 The documentation from the FreeBSD Documentation Project (Handbook, 1188 FAQ, etc.) is now installed via packages by sysinstall(8) and under 1189 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc. 1190 119120090624: 1192 The ABI of various structures related to the SYSV IPC API have been 1193 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel 1194 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to 1195 800100. 1196 119720090622: 1198 Layout of struct vnet has changed as routing related variables were 1199 moved to their own Vimage module. Modules need to be recompiled. Bump 1200 __FreeBSD_version to 800099. 1201 120220090619: 1203 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024 1204 respectively. As long as no more than 16 groups per process are used, 1205 no changes should be visible. When more than 16 groups are used, old 1206 binaries may fail if they call getgroups() or getgrouplist() with 1207 statically sized storage. Recompiling will work around this, but 1208 applications should be modified to use dynamically allocated storage 1209 for group arrays as POSIX.1-2008 does not cap an implementation's 1210 number of supported groups at NGROUPS_MAX+1 as previous versions did. 1211 1212 NFS and portalfs mounts may also be affected as the list of groups is 1213 truncated to 16. Users of NFS who use more than 16 groups, should 1214 take care that negative group permissions are not used on the exported 1215 file systems as they will not be reliable unless a GSSAPI based 1216 authentication method is used. 1217 121820090616: 1219 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This 1220 option compiles in the support for adaptive spinning for lockmgrs 1221 which want to enable it. The lockinit() function now accepts the flag 1222 LK_ADAPTIVE in order to make the lock object subject to adaptive 1223 spinning when both held in write and read mode. 1224 122520090613: 1226 The layout of the structure returned by IEEE80211_IOC_STA_INFO has 1227 changed. User applications that use this ioctl need to be rebuilt. 1228 122920090611: 1230 The layout of struct thread has changed. Kernel and modules need to 1231 be rebuilt. 1232 123320090608: 1234 The layout of structs ifnet, domain, protosw and vnet_net has changed. 1235 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097. 1236 123720090602: 1238 window(1) has been removed from the base system. It can now be 1239 installed from ports. The port is called misc/window. 1240 124120090601: 1242 The way we are storing and accessing `routing table' entries has 1243 changed. Programs reading the FIB, like netstat, need to be 1244 re-compiled. 1245 124620090601: 1247 A new netisr implementation has been added for FreeBSD 8. Network 1248 file system modules, such as igmp, ipdivert, and others, should be 1249 rebuilt. 1250 Bump __FreeBSD_version to 800096. 1251 125220090530: 1253 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no 1254 more valid. 1255 125620090530: 1257 Add VOP_ACCESSX(9). File system modules need to be rebuilt. 1258 Bump __FreeBSD_version to 800094. 1259 126020090529: 1261 Add mnt_xflag field to 'struct mount'. File system modules need to be 1262 rebuilt. 1263 Bump __FreeBSD_version to 800093. 1264 126520090528: 1266 The compiling option ADAPTIVE_SX has been retired while it has been 1267 introduced the option NO_ADAPTIVE_SX which handles the reversed logic. 1268 The KPI for sx_init_flags() changes as accepting flags: 1269 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has 1270 been introduced in order to handle the reversed logic. 1271 Bump __FreeBSD_version to 800092. 1272 127320090527: 1274 Add support for hierarchical jails. Remove global securelevel. 1275 Bump __FreeBSD_version to 800091. 1276 127720090523: 1278 The layout of struct vnet_net has changed, therefore modules 1279 need to be rebuilt. 1280 Bump __FreeBSD_version to 800090. 1281 128220090523: 1283 The newly imported zic(8) produces a new format in the output. Please 1284 run tzsetup(8) to install the newly created data to /etc/localtime. 1285 128620090520: 1287 The sysctl tree for the usb stack has renamed from hw.usb2.* to 1288 hw.usb.* and is now consistent again with previous releases. 1289 129020090520: 1291 802.11 monitor mode support was revised and driver api's were changed. 1292 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead 1293 of DLT_IEEE802_11. No user-visible data structures were changed but 1294 applications that use DLT_IEEE802_11 may require changes. 1295 Bump __FreeBSD_version to 800088. 1296 129720090430: 1298 The layout of the following structs has changed: sysctl_oid, 1299 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet, 1300 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or 1301 panics may be experienced. World rebuild is required for 1302 correctly checking networking state from userland. 1303 Bump __FreeBSD_version to 800085. 1304 130520090429: 1306 MLDv2 and Source-Specific Multicast (SSM) have been merged 1307 to the IPv6 stack. VIMAGE hooks are in but not yet used. 1308 The implementation of SSM within FreeBSD's IPv6 stack closely 1309 follows the IPv4 implementation. 1310 1311 For kernel developers: 1312 1313 * The most important changes are that the ip6_output() and 1314 ip6_input() paths no longer take the IN6_MULTI_LOCK, 1315 and this lock has been downgraded to a non-recursive mutex. 1316 1317 * As with the changes to the IPv4 stack to support SSM, filtering 1318 of inbound multicast traffic must now be performed by transport 1319 protocols within the IPv6 stack. This does not apply to TCP and 1320 SCTP, however, it does apply to UDP in IPv6 and raw IPv6. 1321 1322 * The KPIs used by IPv6 multicast are similar to those used by 1323 the IPv4 stack, with the following differences: 1324 * im6o_mc_filter() is analogous to imo_multicast_filter(). 1325 * The legacy KAME entry points in6_joingroup and in6_leavegroup() 1326 are shimmed to in6_mc_join() and in6_mc_leave() respectively. 1327 * IN6_LOOKUP_MULTI() has been deprecated and removed. 1328 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs 1329 for MLDv1 have an additional 'timer' argument which is used to 1330 jitter the initial membership report for the solicited-node 1331 multicast membership on-link. 1332 * This is not strictly needed for MLDv2, which already jitters 1333 its report transmissions. However, the 'timer' argument is 1334 preserved in case MLDv1 is active on the interface. 1335 1336 * The KAME linked-list based IPv6 membership implementation has 1337 been refactored to use a vector similar to that used by the IPv4 1338 stack. 1339 Code which maintains a list of its own multicast memberships 1340 internally, e.g. carp, has been updated to reflect the new 1341 semantics. 1342 1343 * There is a known Lock Order Reversal (LOR) due to in6_setscope() 1344 acquiring the IF_AFDATA_LOCK and being called within ip6_output(). 1345 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an 1346 implementation constraint which needs to be addressed in HEAD. 1347 1348 For application developers: 1349 1350 * The changes are broadly similar to those made for the IPv4 1351 stack. 1352 1353 * The use of IPv4 and IPv6 multicast socket options on the same 1354 socket, using mapped addresses, HAS NOT been tested or supported. 1355 1356 * There are a number of issues with the implementation of various 1357 IPv6 multicast APIs which need to be resolved in the API surface 1358 before the implementation is fully compatible with KAME userland 1359 use, and these are mostly to do with interface index treatment. 1360 1361 * The literature available discusses the use of either the delta / ASM 1362 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API 1363 using setsourcefilter(3)/getsourcefilter(3). For more information 1364 please refer to RFC 3768, 'Socket Interface Extensions for 1365 Multicast Source Filters'. 1366 1367 * Applications which use the published RFC 3678 APIs should be fine. 1368 1369 For systems administrators: 1370 1371 * The mtest(8) utility has been refactored to support IPv6, in 1372 addition to IPv4. Interface addresses are no longer accepted 1373 as arguments, their names must be used instead. The utility 1374 will map the interface name to its first IPv4 address as 1375 returned by getifaddrs(3). 1376 1377 * The ifmcstat(8) utility has also been updated to print the MLDv2 1378 endpoint state and source filter lists via sysctl(3). 1379 1380 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable 1381 loopback of IPv6 multicast datagrams by default; it defaults to 1 1382 to preserve the existing behaviour. Disabling multicast loopback is 1383 recommended for optimal system performance. 1384 1385 * The IPv6 MROUTING code has been changed to examine this sysctl 1386 instead of attempting to perform a group lookup before looping 1387 back forwarded datagrams. 1388 1389 Bump __FreeBSD_version to 800084. 1390 139120090422: 1392 Implement low-level Bluetooth HCI API. 1393 Bump __FreeBSD_version to 800083. 1394 139520090419: 1396 The layout of struct malloc_type, used by modules to register new 1397 memory allocation types, has changed. Most modules will need to 1398 be rebuilt or panics may be experienced. 1399 Bump __FreeBSD_version to 800081. 1400 140120090415: 1402 Anticipate overflowing inp_flags - add inp_flags2. 1403 This changes most offsets in inpcb, so checking v4 connection 1404 state will require a world rebuild. 1405 Bump __FreeBSD_version to 800080. 1406 140720090415: 1408 Add an llentry to struct route and struct route_in6. Modules 1409 embedding a struct route will need to be recompiled. 1410 Bump __FreeBSD_version to 800079. 1411 141220090414: 1413 The size of rt_metrics_lite and by extension rtentry has changed. 1414 Networking administration apps will need to be recompiled. 1415 The route command now supports show as an alias for get, weighting 1416 of routes, sticky and nostick flags to alter the behavior of stateful 1417 load balancing. 1418 Bump __FreeBSD_version to 800078. 1419 142020090408: 1421 Do not use Giant for kbdmux(4) locking. This is wrong and 1422 apparently causing more problems than it solves. This will 1423 re-open the issue where interrupt handlers may race with 1424 kbdmux(4) in polling mode. Typical symptoms include (but 1425 not limited to) duplicated and/or missing characters when 1426 low level console functions (such as gets) are used while 1427 interrupts are enabled (for example geli password prompt, 1428 mountroot prompt etc.). Disabling kbdmux(4) may help. 1429 143020090407: 1431 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed; 1432 kernel modules referencing any of the above need to be recompiled. 1433 Bump __FreeBSD_version to 800075. 1434 143520090320: 1436 GEOM_PART has become the default partition slicer for storage devices, 1437 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It 1438 introduces some changes: 1439 1440 MSDOS/EBR: the devices created from MSDOS extended partition entries 1441 (EBR) can be named differently than with GEOM_MBR and are now symlinks 1442 to devices with offset-based names. fstabs may need to be modified. 1443 1444 BSD: the "geometry does not match label" warning is harmless in most 1445 cases but it points to problems in file system misalignment with 1446 disk geometry. The "c" partition is now implicit, covers the whole 1447 top-level drive and cannot be (mis)used by users. 1448 1449 General: Kernel dumps are now not allowed to be written to devices 1450 whose partition types indicate they are meant to be used for file 1451 systems (or, in case of MSDOS partitions, as something else than 1452 the "386BSD" type). 1453 1454 Most of these changes date approximately from 200812. 1455 145620090319: 1457 The uscanner(4) driver has been removed from the kernel. This follows 1458 Linux removing theirs in 2.6 and making libusb the default interface 1459 (supported by sane). 1460 146120090319: 1462 The multicast forwarding code has been cleaned up. netstat(1) 1463 only relies on KVM now for printing bandwidth upcall meters. 1464 The IPv4 and IPv6 modules are split into ip_mroute_mod and 1465 ip6_mroute_mod respectively. The config(5) options for statically 1466 compiling this code remain the same, i.e. 'options MROUTING'. 1467 146820090315: 1469 Support for the IFF_NEEDSGIANT network interface flag has been 1470 removed, which means that non-MPSAFE network device drivers are no 1471 longer supported. In particular, if_ar, if_sr, and network device 1472 drivers from the old (legacy) USB stack can no longer be built or 1473 used. 1474 147520090313: 1476 POSIX.1 Native Language Support (NLS) has been enabled in libc and 1477 a bunch of new language catalog files have also been added. 1478 This means that some common libc messages are now localized and 1479 they depend on the LC_MESSAGES environmental variable. 1480 148120090313: 1482 The k8temp(4) driver has been renamed to amdtemp(4) since 1483 support for Family 10 and Family 11 CPU families was added. 1484 148520090309: 1486 IGMPv3 and Source-Specific Multicast (SSM) have been merged 1487 to the IPv4 stack. VIMAGE hooks are in but not yet used. 1488 1489 For kernel developers, the most important changes are that the 1490 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(), 1491 and this lock has been downgraded to a non-recursive mutex. 1492 1493 Transport protocols (UDP, Raw IP) are now responsible for filtering 1494 inbound multicast traffic according to group membership and source 1495 filters. The imo_multicast_filter() KPI exists for this purpose. 1496 Transports which do not use multicast (SCTP, TCP) already reject 1497 multicast by default. Forwarding and receive performance may improve 1498 as a mutex acquisition is no longer needed in the ip_input() 1499 low-level input path. in_addmulti() and in_delmulti() are shimmed 1500 to new KPIs which exist to support SSM in-kernel. 1501 1502 For application developers, it is recommended that loopback of 1503 multicast datagrams be disabled for best performance, as this 1504 will still cause the lock to be taken for each looped-back 1505 datagram transmission. The net.inet.ip.mcast.loop sysctl may 1506 be tuned to 0 to disable loopback by default; it defaults to 1 1507 to preserve the existing behaviour. 1508 1509 For systems administrators, to obtain best performance with 1510 multicast reception and multiple groups, it is always recommended 1511 that a card with a suitably precise hash filter is used. Hash 1512 collisions will still result in the lock being taken within the 1513 transport protocol input path to check group membership. 1514 1515 If deploying FreeBSD in an environment with IGMP snooping switches, 1516 it is recommended that the net.inet.igmp.sendlocal sysctl remain 1517 enabled; this forces 224.0.0.0/24 group membership to be announced 1518 via IGMP. 1519 1520 The size of 'struct igmpstat' has changed; netstat needs to be 1521 recompiled to reflect this. 1522 Bump __FreeBSD_version to 800070. 1523 152420090309: 1525 libusb20.so.1 is now installed as libusb.so.1 and the ports system 1526 updated to use it. This requires a buildworld/installworld in order to 1527 update the library and dependencies (usbconfig, etc). Its advisable to 1528 rebuild all ports which uses libusb. More specific directions are given 1529 in the ports collection UPDATING file. Any /etc/libmap.conf entries for 1530 libusb are no longer required and can be removed. 1531 153220090302: 1533 A workaround is committed to allow the creation of System V shared 1534 memory segment of size > 2 GB on the 64-bit architectures. 1535 Due to a limitation of the existing ABI, the shm_segsz member 1536 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is 1537 wrong for large segments. Note that limits must be explicitly 1538 raised to allow such segments to be created. 1539 154020090301: 1541 The layout of struct ifnet has changed, requiring a rebuild of all 1542 network device driver modules. 1543 154420090227: 1545 The /dev handling for the new USB stack has changed, a 1546 buildworld/installworld is required for libusb20. 1547 154820090223: 1549 The new USB2 stack has now been permanently moved in and all kernel and 1550 module names reverted to their previous values (eg, usb, ehci, ohci, 1551 ums, ...). The old usb stack can be compiled in by prefixing the name 1552 with the letter 'o', the old usb modules have been removed. 1553 Updating entry 20090216 for xorg and 20090215 for libmap may still 1554 apply. 1555 155620090217: 1557 The rc.conf(5) option if_up_delay has been renamed to 1558 defaultroute_delay to better reflect its purpose. If you have 1559 customized this setting in /etc/rc.conf you need to update it to 1560 use the new name. 1561 156220090216: 1563 xorg 7.4 wants to configure its input devices via hald which does not 1564 yet work with USB2. If the keyboard/mouse does not work in xorg then 1565 add 1566 Option "AllowEmptyInput" "off" 1567 to your ServerLayout section. This will cause X to use the configured 1568 kbd and mouse sections from your xorg.conf. 1569 157020090215: 1571 The GENERIC kernels for all architectures now default to the new USB2 1572 stack. No kernel config options or code have been removed so if a 1573 problem arises please report it and optionally revert to the old USB 1574 stack. If you are loading USB kernel modules or have a custom kernel 1575 that includes GENERIC then ensure that usb names are also changed over, 1576 eg uftdi -> usb2_serial_ftdi. 1577 1578 Older programs linked against the ports libusb 0.1 need to be 1579 redirected to the new stack's libusb20. /etc/libmap.conf can 1580 be used for this: 1581 # Map old usb library to new one for usb2 stack 1582 libusb-0.1.so.8 libusb20.so.1 1583 158420090209: 1585 All USB ethernet devices now attach as interfaces under the name ueN 1586 (eg. ue0). This is to provide a predictable name as vendors often 1587 change usb chipsets in a product without notice. 1588 158920090203: 1590 The ichsmb(4) driver has been changed to require SMBus slave 1591 addresses be left-justified (xxxxxxx0b) rather than right-justified. 1592 All of the other SMBus controller drivers require left-justified 1593 slave addresses, so this change makes all the drivers provide the 1594 same interface. 1595 159620090201: 1597 INET6 statistics (struct ip6stat) was updated. 1598 netstat(1) needs to be recompiled. 1599 160020090119: 1601 NTFS has been removed from GENERIC kernel on amd64 to match 1602 GENERIC on i386. Should not cause any issues since mount_ntfs(8) 1603 will load ntfs.ko module automatically when NTFS support is 1604 actually needed, unless ntfs.ko is not installed or security 1605 level prohibits loading kernel modules. If either is the case, 1606 "options NTFS" has to be added into kernel config. 1607 160820090115: 1609 TCP Appropriate Byte Counting (RFC 3465) support added to kernel. 1610 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to 1611 800061. User space tools that rely on the size of struct tcpcb in 1612 tcp_var.h (e.g. sockstat) need to be recompiled. 1613 161420081225: 1615 ng_tty(4) module updated to match the new TTY subsystem. 1616 Due to API change, user-level applications must be updated. 1617 New API support added to mpd5 CVS and expected to be present 1618 in next mpd5.3 release. 1619 162020081219: 1621 With __FreeBSD_version 800060 the makefs tool is part of 1622 the base system (it was a port). 1623 162420081216: 1625 The afdata and ifnet locks have been changed from mutexes to 1626 rwlocks, network modules will need to be re-compiled. 1627 162820081214: 1629 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite. 1630 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated. 1631 The new code reduced struct rtentry{} by 16 bytes on 32-bit 1632 architecture and 40 bytes on 64-bit architecture. The userland 1633 applications "arp" and "ndp" have been updated accordingly. 1634 The output from "netstat -r" shows only routing entries and 1635 none of the L2 information. 1636 163720081130: 1638 __FreeBSD_version 800057 marks the switchover from the 1639 binary ath hal to source code. Users must add the line: 1640 1641 options AH_SUPPORT_AR5416 1642 1643 to their kernel config files when specifying: 1644 1645 device ath_hal 1646 1647 The ath_hal module no longer exists; the code is now compiled 1648 together with the driver in the ath module. It is now 1649 possible to tailor chip support (i.e. reduce the set of chips 1650 and thereby the code size); consult ath_hal(4) for details. 1651 165220081121: 1653 __FreeBSD_version 800054 adds memory barriers to 1654 <machine/atomic.h>, new interfaces to ifnet to facilitate 1655 multiple hardware transmit queues for cards that support 1656 them, and a lock-less ring-buffer implementation to 1657 enable drivers to more efficiently manage queueing of 1658 packets. 1659 166020081117: 1661 A new version of ZFS (version 13) has been merged to -HEAD. 1662 This version has zpool attribute "listsnapshots" off by 1663 default, which means "zfs list" does not show snapshots, 1664 and is the same as Solaris behavior. 1665 166620081028: 1667 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled. 1668 166920081009: 1670 The uhci, ohci, ehci and slhci USB Host controller drivers have 1671 been put into separate modules. If you load the usb module 1672 separately through loader.conf you will need to load the 1673 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0 1674 controller add the following to loader.conf: 1675 1676 uhci_load="YES" 1677 ehci_load="YES" 1678 167920081009: 1680 The ABI used by the PMC toolset has changed. Please keep 1681 userland (libpmc(3)) and the kernel module (hwpmc(4)) in 1682 sync. 1683 168420081009: 1685 atapci kernel module now includes only generic PCI ATA 1686 driver. AHCI driver moved to ataahci kernel module. 1687 All vendor-specific code moved into separate kernel modules: 1688 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek, 1689 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron, 1690 atamarvell, atamicron, atanational, atanetcell, atanvidia, 1691 atapromise, ataserverworks, atasiliconimage, atasis, atavia 1692 169320080820: 1694 The TTY subsystem of the kernel has been replaced by a new 1695 implementation, which provides better scalability and an 1696 improved driver model. Most common drivers have been migrated to 1697 the new TTY subsystem, while others have not. The following 1698 drivers have not yet been ported to the new TTY layer: 1699 1700 PCI/ISA: 1701 cy, digi, rc, rp, sio 1702 1703 USB: 1704 ubser, ucycom 1705 1706 Line disciplines: 1707 ng_h4, ng_tty, ppp, sl, snp 1708 1709 Adding these drivers to your kernel configuration file shall 1710 cause compilation to fail. 1711 171220080818: 1713 ntpd has been upgraded to 4.2.4p5. 1714 171520080801: 1716 OpenSSH has been upgraded to 5.1p1. 1717 1718 For many years, FreeBSD's version of OpenSSH preferred DSA 1719 over RSA for host and user authentication keys. With this 1720 upgrade, we've switched to the vendor's default of RSA over 1721 DSA. This may cause upgraded clients to warn about unknown 1722 host keys even for previously known hosts. Users should 1723 follow the usual procedure for verifying host keys before 1724 accepting the RSA key. 1725 1726 This can be circumvented by setting the "HostKeyAlgorithms" 1727 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh 1728 command line. 1729 1730 Please note that the sequence of keys offered for 1731 authentication has been changed as well. You may want to 1732 specify IdentityFile in a different order to revert this 1733 behavior. 1734 173520080713: 1736 The sio(4) driver has been removed from the i386 and amd64 1737 kernel configuration files. This means uart(4) is now the 1738 default serial port driver on those platforms as well. 1739 1740 To prevent collisions with the sio(4) driver, the uart(4) driver 1741 uses different names for its device nodes. This means the 1742 onboard serial port will now most likely be called "ttyu0" 1743 instead of "ttyd0". You may need to reconfigure applications to 1744 use the new device names. 1745 1746 When using the serial port as a boot console, be sure to update 1747 /boot/device.hints and /etc/ttys before booting the new kernel. 1748 If you forget to do so, you can still manually specify the hints 1749 at the loader prompt: 1750 1751 set hint.uart.0.at="isa" 1752 set hint.uart.0.port="0x3F8" 1753 set hint.uart.0.flags="0x10" 1754 set hint.uart.0.irq="4" 1755 boot -s 1756 175720080609: 1758 The gpt(8) utility has been removed. Use gpart(8) to partition 1759 disks instead. 1760 176120080603: 1762 The version that Linuxulator emulates was changed from 2.4.2 1763 to 2.6.16. If you experience any problems with Linux binaries 1764 please try to set sysctl compat.linux.osrelease to 2.4.2 and 1765 if it fixes the problem contact emulation mailing list. 1766 176720080525: 1768 ISDN4BSD (I4B) was removed from the src tree. You may need to 1769 update a your kernel configuration and remove relevant entries. 1770 177120080509: 1772 I have checked in code to support multiple routing tables. 1773 See the man pages setfib(1) and setfib(2). 1774 This is a hopefully backwards compatible version, 1775 but to make use of it you need to compile your kernel 1776 with options ROUTETABLES=2 (or more up to 16). 1777 177820080420: 1779 The 802.11 wireless support was redone to enable multi-bss 1780 operation on devices that are capable. The underlying device 1781 is no longer used directly but instead wlanX devices are 1782 cloned with ifconfig. This requires changes to rc.conf files. 1783 For example, change: 1784 ifconfig_ath0="WPA DHCP" 1785 to 1786 wlans_ath0=wlan0 1787 ifconfig_wlan0="WPA DHCP" 1788 see rc.conf(5) for more details. In addition, mergemaster of 1789 /etc/rc.d is highly recommended. Simultaneous update of userland 1790 and kernel wouldn't hurt either. 1791 1792 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta 1793 modules were merged into the base wlan module. All references 1794 to these modules (e.g. in kernel config files) must be removed. 1795 179620080408: 1797 psm(4) has gained write(2) support in native operation level. 1798 Arbitrary commands can be written to /dev/psm%d and status can 1799 be read back from it. Therefore, an application is responsible 1800 for status validation and error recovery. It is a no-op in 1801 other operation levels. 1802 180320080312: 1804 Support for KSE threading has been removed from the kernel. To 1805 run legacy applications linked against KSE libmap.conf may 1806 be used. The following libmap.conf may be used to ensure 1807 compatibility with any prior release: 1808 1809 libpthread.so.1 libthr.so.1 1810 libpthread.so.2 libthr.so.2 1811 libkse.so.3 libthr.so.3 1812 181320080301: 1814 The layout of struct vmspace has changed. This affects libkvm 1815 and any executables that link against libkvm and use the 1816 kvm_getprocs() function. In particular, but not exclusively, 1817 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1). 1818 The effects are minimal, but it's advisable to upgrade world 1819 nonetheless. 1820 182120080229: 1822 The latest em driver no longer has support in it for the 1823 82575 adapter, this is now moved to the igb driver. The 1824 split was done to make new features that are incompatible 1825 with older hardware easier to do. 1826 182720080220: 1828 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4), 1829 likewise the kernel option is now GEOM_LINUX_LVM. 1830 183120080211: 1832 The default NFS mount mode has changed from UDP to TCP for 1833 increased reliability. If you rely on (insecurely) NFS 1834 mounting across a firewall you may need to update your 1835 firewall rules. 1836 183720080208: 1838 Belatedly note the addition of m_collapse for compacting 1839 mbuf chains. 1840 184120080126: 1842 The fts(3) structures have been changed to use adequate 1843 integer types for their members and so to be able to cope 1844 with huge file trees. The old fts(3) ABI is preserved 1845 through symbol versioning in libc, so third-party binaries 1846 using fts(3) should still work, although they will not take 1847 advantage of the extended types. At the same time, some 1848 third-party software might fail to build after this change 1849 due to unportable assumptions made in its source code about 1850 fts(3) structure members. Such software should be fixed 1851 by its vendor or, in the worst case, in the ports tree. 1852 FreeBSD_version 800015 marks this change for the unlikely 1853 case that a portable fix is impossible. 1854 185520080123: 1856 To upgrade to -current after this date, you must be running 1857 FreeBSD not older than 6.0-RELEASE. Upgrading to -current 1858 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems. 1859 186020071128: 1861 The ADAPTIVE_GIANT kernel option has been retired because its 1862 functionality is the default now. 1863 186420071118: 1865 The AT keyboard emulation of sunkbd(4) has been turned on 1866 by default. In order to make the special symbols of the Sun 1867 keyboards driven by sunkbd(4) work under X these now have 1868 to be configured the same way as Sun USB keyboards driven 1869 by ukbd(4) (which also does AT keyboard emulation), f.e.: 1870 1871 Option "XkbLayout" "us" 1872 Option "XkbRules" "xorg" 1873 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us" 1874 187520071024: 1876 It has been decided that it is desirable to provide ABI 1877 backwards compatibility to the FreeBSD 4/5/6 versions of the 1878 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was 1879 broken with the introduction of PCI domain support (see the 1880 20070930 entry). Unfortunately, this required the ABI of 1881 PCIOCGETCONF to be broken again in order to be able to 1882 provide backwards compatibility to the old version of that 1883 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled 1884 again. As for prominent ports this affects neither pciutils 1885 nor xorg-server this time, the hal port needs to be rebuilt 1886 however. 1887 188820071020: 1889 The misnamed kthread_create() and friends have been renamed 1890 to kproc_create() etc. Many of the callers already 1891 used kproc_start().. 1892 I will return kthread_create() and friends in a while 1893 with implementations that actually create threads, not procs. 1894 Renaming corresponds with version 800002. 1895 189620071010: 1897 RELENG_7 branched. 1898 1899COMMON ITEMS: 1900 1901 General Notes 1902 ------------- 1903 Avoid using make -j when upgrading. While generally safe, there are 1904 sometimes problems using -j to upgrade. If your upgrade fails with 1905 -j, please try again without -j. From time to time in the past there 1906 have been problems using -j with buildworld and/or installworld. This 1907 is especially true when upgrading between "distant" versions (eg one 1908 that cross a major release boundary or several minor releases, or when 1909 several months have passed on the -current branch). 1910 1911 Sometimes, obscure build problems are the result of environment 1912 poisoning. This can happen because the make utility reads its 1913 environment when searching for values for global variables. To run 1914 your build attempts in an "environmental clean room", prefix all make 1915 commands with 'env -i '. See the env(1) manual page for more details. 1916 1917 When upgrading from one major version to another it is generally best 1918 to upgrade to the latest code in the currently installed branch first, 1919 then do an upgrade to the new branch. This is the best-tested upgrade 1920 path, and has the highest probability of being successful. Please try 1921 this approach before reporting problems with a major version upgrade. 1922 1923 When upgrading a live system, having a root shell around before 1924 installing anything can help undo problems. Not having a root shell 1925 around can lead to problems if pam has changed too much from your 1926 starting point to allow continued authentication after the upgrade. 1927 1928 ZFS notes 1929 --------- 1930 When upgrading the boot ZFS pool to a new version, always follow 1931 these two steps: 1932 1933 1.) recompile and reinstall the ZFS boot loader and boot block 1934 (this is part of "make buildworld" and "make installworld") 1935 1936 2.) update the ZFS boot block on your boot drive 1937 1938 The following example updates the ZFS boot block on the first 1939 partition (freebsd-boot) of a GPT partitioned drive ad0: 1940 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0" 1941 1942 Non-boot pools do not need these updates. 1943 1944 To build a kernel 1945 ----------------- 1946 If you are updating from a prior version of FreeBSD (even one just 1947 a few days old), you should follow this procedure. It is the most 1948 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 1949 1950 make kernel-toolchain 1951 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1952 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1953 1954 To test a kernel once 1955 --------------------- 1956 If you just want to boot a kernel once (because you are not sure 1957 if it works, or if you want to boot a known bad kernel to provide 1958 debugging information) run 1959 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 1960 nextboot -k testkernel 1961 1962 To just build a kernel when you know that it won't mess you up 1963 -------------------------------------------------------------- 1964 This assumes you are already running a CURRENT system. Replace 1965 ${arch} with the architecture of your machine (e.g. "i386", 1966 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc). 1967 1968 cd src/sys/${arch}/conf 1969 config KERNEL_NAME_HERE 1970 cd ../compile/KERNEL_NAME_HERE 1971 make depend 1972 make 1973 make install 1974 1975 If this fails, go to the "To build a kernel" section. 1976 1977 To rebuild everything and install it on the current system. 1978 ----------------------------------------------------------- 1979 # Note: sometimes if you are running current you gotta do more than 1980 # is listed here if you are upgrading from a really old current. 1981 1982 <make sure you have good level 0 dumps> 1983 make buildworld 1984 make kernel KERNCONF=YOUR_KERNEL_HERE 1985 [1] 1986 <reboot in single user> [3] 1987 mergemaster -p [5] 1988 make installworld 1989 mergemaster -i [4] 1990 make delete-old [6] 1991 <reboot> 1992 1993 To cross-install current onto a separate partition 1994 -------------------------------------------------- 1995 # In this approach we use a separate partition to hold 1996 # current's root, 'usr', and 'var' directories. A partition 1997 # holding "/", "/usr" and "/var" should be about 2GB in 1998 # size. 1999 2000 <make sure you have good level 0 dumps> 2001 <boot into -stable> 2002 make buildworld 2003 make buildkernel KERNCONF=YOUR_KERNEL_HERE 2004 <maybe newfs current's root partition> 2005 <mount current's root partition on directory ${CURRENT_ROOT}> 2006 make installworld DESTDIR=${CURRENT_ROOT} 2007 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 2008 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 2009 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 2010 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 2011 <reboot into current> 2012 <do a "native" rebuild/install as described in the previous section> 2013 <maybe install compatibility libraries from ports/misc/compat*> 2014 <reboot> 2015 2016 2017 To upgrade in-place from stable to current 2018 ---------------------------------------------- 2019 <make sure you have good level 0 dumps> 2020 make buildworld [9] 2021 make kernel KERNCONF=YOUR_KERNEL_HERE [8] 2022 [1] 2023 <reboot in single user> [3] 2024 mergemaster -p [5] 2025 make installworld 2026 mergemaster -i [4] 2027 make delete-old [6] 2028 <reboot> 2029 2030 Make sure that you've read the UPDATING file to understand the 2031 tweaks to various things you need. At this point in the life 2032 cycle of current, things change often and you are on your own 2033 to cope. The defaults can also change, so please read ALL of 2034 the UPDATING entries. 2035 2036 Also, if you are tracking -current, you must be subscribed to 2037 freebsd-current@freebsd.org. Make sure that before you update 2038 your sources that you have read and understood all the recent 2039 messages there. If in doubt, please track -stable which has 2040 much fewer pitfalls. 2041 2042 [1] If you have third party modules, such as vmware, you 2043 should disable them at this point so they don't crash your 2044 system on reboot. 2045 2046 [3] From the bootblocks, boot -s, and then do 2047 fsck -p 2048 mount -u / 2049 mount -a 2050 cd src 2051 adjkerntz -i # if CMOS is wall time 2052 Also, when doing a major release upgrade, it is required that 2053 you boot into single user mode to do the installworld. 2054 2055 [4] Note: This step is non-optional. Failure to do this step 2056 can result in a significant reduction in the functionality of the 2057 system. Attempting to do it by hand is not recommended and those 2058 that pursue this avenue should read this file carefully, as well 2059 as the archives of freebsd-current and freebsd-hackers mailing lists 2060 for potential gotchas. The -U option is also useful to consider. 2061 See mergemaster(8) for more information. 2062 2063 [5] Usually this step is a noop. However, from time to time 2064 you may need to do this if you get unknown user in the following 2065 step. It never hurts to do it all the time. You may need to 2066 install a new mergemaster (cd src/usr.sbin/mergemaster && make 2067 install) after the buildworld before this step if you last updated 2068 from current before 20130425 or from -stable before 20130430. 2069 2070 [6] This only deletes old files and directories. Old libraries 2071 can be deleted by "make delete-old-libs", but you have to make 2072 sure that no program is using those libraries anymore. 2073 2074 [8] In order to have a kernel that can run the 4.x binaries needed to 2075 do an installworld, you must include the COMPAT_FREEBSD4 option in 2076 your kernel. Failure to do so may leave you with a system that is 2077 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is 2078 required to run the 5.x binaries on more recent kernels. And so on 2079 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7. 2080 2081 Make sure that you merge any new devices from GENERIC since the 2082 last time you updated your kernel config file. 2083 2084 [9] When checking out sources, you must include the -P flag to have 2085 cvs prune empty directories. 2086 2087 If CPUTYPE is defined in your /etc/make.conf, make sure to use the 2088 "?=" instead of the "=" assignment operator, so that buildworld can 2089 override the CPUTYPE if it needs to. 2090 2091 MAKEOBJDIRPREFIX must be defined in an environment variable, and 2092 not on the command line, or in /etc/make.conf. buildworld will 2093 warn if it is improperly defined. 2094FORMAT: 2095 2096This file contains a list, in reverse chronological order, of major 2097breakages in tracking -current. It is not guaranteed to be a complete 2098list of such breakages, and only contains entries since October 10, 2007. 2099If you need to see UPDATING entries from before that date, you will need 2100to fetch an UPDATING file from an older FreeBSD release. 2101 2102Copyright information: 2103 2104Copyright 1998-2009 M. Warner Losh. All Rights Reserved. 2105 2106Redistribution, publication, translation and use, with or without 2107modification, in full or in part, in any form or format of this 2108document are permitted without further permission from the author. 2109 2110THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 2111IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 2112WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 2113DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 2114INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 2115(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 2116SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 2117HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 2118STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 2119IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 2120POSSIBILITY OF SUCH DAMAGE. 2121 2122Contact Warner Losh if you have any questions about your use of 2123this document. 2124 2125$FreeBSD: stable/10/UPDATING 270403 2014-08-23 11:46:26Z des $ 2126