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