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