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