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