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