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