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