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