1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE TO PEOPLE WHO THINK THAT FreeBSD 10.x IS SLOW:
15 FreeBSD 10.x has many debugging features turned on, in both the kernel
16 and userland. These features attempt to detect incorrect use of
17 system primitives, and encourage loud failure through extra sanity
18 checking and fail stop semantics. They also substantially impact
19 system performance. If you want to do performance measurement,
20 benchmarking, and optimization, you'll want to turn them off. This
21 includes various WITNESS- related kernel options, INVARIANTS, malloc
22 debugging flags in userland, and various verbose features in the
23 kernel. Many developers choose to disable these features on build
24 machines to maximize performance. (To completely disable malloc
25 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
26 disable the most expensive debugging functionality run
27 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
30 A BSD-licensed patch(1) variant has been added and is installed
31 as bsdpatch, being the GNU version the default patch.
32 To inverse the logic and use the BSD-licensed one as default,
33 while having the GNU version installed as gnupatch, rebuild
34 and install world with the WITH_BSD_PATCH knob set.
37 The install(1) option -M has changed meaning and now takes an
38 argument that is a file or path to append logs to. In the
39 unlikely event that -M was the last option on the command line
40 and the command line contained at least two files and a target
41 directory the first file will have logs appended to it. The -M
42 option served little practical purpose in the last decade so it's
43 used expected to be extremely rare.
46 After switching to Clang as the default compiler some users of ZFS
47 on i386 systems started to experience stack overflow kernel panics.
48 Please consider using 'options KSTACK_PAGES=4' in such configurations.
51 GEOM_LABEL now mangles label names read from file system metadata.
52 Mangling affect labels containing spaces, non-printable characters,
53 '%' or '"'. Device names in /etc/fstab and other places may need to
57 By default, only the 10 most recent kernel dumps will be saved. To
58 restore the previous behaviour (no limit on the number of kernel dumps
59 stored in the dump directory) add the following line to /etc/rc.conf:
64 With the addition of auditdistd(8), a new auditdistd user is now
65 depended on during installworld. "mergemaster -p" can be used to add
66 the user prior to installworld, as documented in the handbook.
69 The sin6_scope_id member variable in struct sockaddr_in6 is now
70 filled by the kernel before passing the structure to the userland via
71 sysctl or routing socket. This means the KAME-specific embedded scope
72 id in sin6_addr.s6_addr[2] is always cleared in userland application.
73 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
74 __FreeBSD_version is bumped to 1000025.
77 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
78 This means that the world and kernel will be compiled with clang
79 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
80 and /usr/bin/cpp. To disable this behavior and revert to building
81 with gcc, compile with WITHOUT_CLANG_IS_CC.
84 The IPFIREWALL_FORWARD kernel option has been removed. Its
85 functionality now turned on by default.
88 The ZERO_COPY_SOCKET kernel option has been removed and
89 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
90 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
91 mechanism which is not safe and may result in kernel crashes.
92 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
93 driver supports disposeable external page sized mbuf storage.
94 Proper replacements for both zero-copy mechanisms are under
95 consideration and will eventually lead to complete removal
96 of the two kernel options.
99 The IPv4 network stack has been converted to network byte
100 order. The following modules need to be recompiled together
101 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
102 pf(4), ipfw(4), ng_ipfw(4), stf(4).
105 Support for non-MPSAFE filesystems was removed from VFS. The
106 VFS_VERSION was bumped, all filesystem modules shall be
110 All the non-MPSAFE filesystems have been disconnected from
111 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
112 portalfs, smbfs, xfs.
115 The interface cloning API and ABI has changed. The following
116 modules need to be recompiled together with kernel:
117 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
118 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
119 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
122 The sdhci driver was split in two parts: sdhci (generic SD Host
123 Controller logic) and sdhci_pci (actual hardware driver).
124 No kernel config modifications are required, but if you
125 load sdhc as a module you must switch to sdhci_pci instead.
128 Import the FUSE kernel and userland support into base system.
131 The GNU sort(1) program has been removed since the BSD-licensed
132 sort(1) has been the default for quite some time and no serious
133 problems have been reported. The corresponding WITH_GNU_SORT
137 The pfil(9) API/ABI for AF_INET family has been changed. Packet
138 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
142 The net80211(4) ABI has been changed to allow for improved driver
143 PS-POLL and power-save support. All wireless drivers need to be
144 recompiled to work with the new kernel.
147 The random(4) support for the VIA hardware random number
148 generator (`PADLOCK') is no longer enabled unconditionally.
149 Add the PADLOCK_RNG option in the custom kernel config if
150 needed. The GENERIC kernels on i386 and amd64 do include the
151 option, so the change only affects the custom kernel
155 The pf(4) packet filter ABI has been changed. pfctl(8) and
156 snmp_pf module need to be recompiled to work with new kernel.
159 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
160 to -HEAD. Pools that have empty_bpobj in active state can not be
161 imported read-write with ZFS implementations that do not support
162 this feature. For more information read the zpool-features(5)
166 The sparc64 ZFS loader has been changed to no longer try to auto-
167 detect ZFS providers based on diskN aliases but now requires these
168 to be explicitly listed in the OFW boot-device environment variable.
171 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
172 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
173 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
176 The following sysctls and tunables have been renamed for consistency
177 with other variables:
178 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
179 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
182 The sort utility has been replaced with BSD sort. For now, GNU sort
183 is also available as "gnusort" or the default can be set back to
184 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
185 installed as "bsdsort".
188 A new version of ZFS (pool version 5000) has been merged to -HEAD.
189 Starting with this version the old system of ZFS pool versioning
190 is superseded by "feature flags". This concept enables forward
191 compatibility against certain future changes in functionality of ZFS
192 pools. The first read-only compatible "feature flag" for ZFS pools
193 is named "com.delphix:async_destroy". For more information
194 read the new zpool-features(5) manual page.
195 Please refer to the "ZFS notes" section of this file for information
196 on upgrading boot ZFS pools.
199 The malloc(3) implementation embedded in libc now uses sources imported
200 as contrib/jemalloc. The most disruptive API change is to
201 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
202 delete it prior to installworld, and optionally re-create it using the
203 new format after rebooting. See malloc.conf(5) for details
204 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
208 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
209 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
210 now spelled mips. This is to aid compatibility with third-party
211 software that expects this naming scheme in uname(3). Little-endian
212 settings are unchanged.
215 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
219 Now unix domain sockets behave "as expected" on nullfs(5). Previously
220 nullfs(5) did not pass through all behaviours to the underlying layer,
221 as a result if we bound to a socket on the lower layer we could connect
222 only to the lower path; if we bound to the upper layer we could connect
223 only to the upper path. The new behavior is one can connect to both the
224 lower and the upper paths regardless what layer path one binds to.
227 The getifaddrs upgrade path broken with 20111215 has been restored.
228 If you have upgraded in between 20111215 and 20120209 you need to
229 recompile libc again with your kernel. You still need to recompile
230 world to be able to configure CARP but this restriction already
234 The set_rcvar() function has been removed from /etc/rc.subr. All
235 base and ports rc.d scripts have been updated, so if you have a
236 port installed with a script in /usr/local/etc/rc.d you can either
237 hand-edit the rcvar= line, or reinstall the port.
239 An easy way to handle the mass-update of /etc/rc.d:
240 rm /etc/rc.d/* && mergemaster -i
243 panic(9) now stops other CPUs in the SMP systems, disables interrupts
244 on the current CPU and prevents other threads from running.
245 This behavior can be reverted using the kern.stop_scheduler_on_panic
247 The new behavior can be incompatible with kern.sync_on_panic.
250 The carp(4) facility has been changed significantly. Configuration
251 of the CARP protocol via ifconfig(8) has changed, as well as format
252 of CARP events submitted to devd(8) has changed. See manual pages
253 for more information. The arpbalance feature of carp(4) is currently
254 not supported anymore.
256 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
257 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
258 need to be recompiled.
261 The acpi_wmi(4) status device /dev/wmistat has been renamed to
265 The option VFS_ALLOW_NONMPSAFE option has been added in order to
266 explicitely support non-MPSAFE filesystems.
267 It is on by default for all supported platform at this present
271 The broken amd(4) driver has been replaced with esp(4) in the amd64,
272 i386 and pc98 GENERIC kernel configuration files.
275 sysinstall has been removed
278 The stable/9 branch created in subversion. This corresponds to the
279 RELENG_9 branch in CVS.
282 This commit modifies vfs_register() so that it uses a hash
283 calculation to set vfc_typenum, which is enabled by default.
284 The first time a system is booted after this change, the
285 vfc_typenum values will change for all file systems. The
286 main effect of this is a change to the NFS server file handles
287 for file systems that use vfc_typenum in their fsid, such as ZFS.
288 It will, however, prevent vfc_typenum from changing when file
289 systems are loaded in a different order for subsequent reboots.
290 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
291 until you are ready to remount all NFS clients after a reboot.
294 Bump the shared library version numbers for libraries that
295 do not use symbol versioning, have changed the ABI compared
296 to stable/8 and which shared library version was not bumped.
297 Done as part of 9.0-RELEASE cycle.
300 During the merge of Capsicum features, the fget(9) KPI was modified.
301 This may require the rebuilding of out-of-tree device drivers --
302 issues have been reported specifically with the nVidia device driver.
303 __FreeBSD_version is bumped to 900041.
305 Also, there is a period between 20110811 and 20110814 where the
306 special devices /dev/{stdin,stdout,stderr} did not work correctly.
307 Building world from a kernel during that window may not work.
310 The packet filter (pf) code has been updated to OpenBSD 4.5.
311 You need to update userland tools to be in sync with kernel.
312 This update breaks backward compatibility with earlier pfsync(4)
313 versions. Care must be taken when updating redundant firewall setups.
316 The following sysctls and tunables are retired on x86 platforms:
318 machdep.hlt_logical_cpus
319 The following sysctl is retired:
320 machdep.hyperthreading_allowed
321 The sysctls were supposed to provide a way to dynamically offline and
322 online selected CPUs on x86 platforms, but the implementation has not
323 been reliable especially with SCHED_ULE scheduler.
324 machdep.hyperthreading_allowed tunable is still available to ignore
325 hyperthreading CPUs at OS level.
326 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
327 where X is an APIC ID of a CPU. Be advised, though, that disabling
328 CPUs in non-uniform fashion will result in non-uniform topology and
329 may lead to sub-optimal system performance with SCHED_ULE, which is
333 cpumask_t type is retired and cpuset_t is used in order to describe
337 Changes to ifconfig(8) for dynamic address family detection mandate
338 that you are running a kernel of 20110525 or later. Make sure to
339 follow the update procedure to boot a new kernel before installing
343 Support for sun4v architecture is officially dropped
346 Several KPI breaking changes have been committed to the mii(4) layer,
347 the PHY drivers and consequently some Ethernet drivers using mii(4).
348 This means that miibus.ko and the modules of the affected Ethernet
349 drivers need to be recompiled.
351 Note to kernel developers: Given that the OUI bit reversion problem
352 was fixed as part of these changes all mii(4) commits related to OUIs,
353 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
354 handling, no longer can be merged verbatim to stable/8 and previous
358 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
359 into their kernel configurations along with 'device pci'.
362 The default NFS client is now the new NFS client, so fstype "newnfs"
363 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
364 Although mounts via fstype "nfs" will usually work without userland
365 changes, it is recommended that the mount(8) and mount_nfs(8)
366 commands be rebuilt from sources and that a link to mount_nfs called
367 mount_oldnfs be created. The new client is compiled into the
368 kernel with "options NFSCL" and this is needed for diskless root
369 file systems. The GENERIC kernel configs have been changed to use
370 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
371 To use the regular/old client, you can "mount -t oldnfs ...". For
372 a diskless root file system, you must also include a line like:
374 vfs.root.mountfrom="oldnfs:"
376 in the boot/loader.conf on the root fs on the NFS server to make
377 a diskless root fs use the old client.
380 The GENERIC kernels for all architectures now default to the new
381 CAM-based ATA stack. It means that all legacy ATA drivers were
382 removed and replaced by respective CAM drivers. If you are using
383 ATA device names in /etc/fstab or other places, make sure to update
384 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
385 where 'Y's are the sequential numbers starting from zero for each type
386 in order of detection, unless configured otherwise with tunables,
387 see cam(4)). There will be symbolic links created in /dev/ to map
388 old adX devices to the respective adaY. They should provide basic
389 compatibility for file systems mounting in most cases, but they do
390 not support old user-level APIs and do not have respective providers
391 in GEOM. Consider using updated management tools with new device names.
393 It is possible to load devices ahci, ata, siis and mvs as modules,
394 but option ATA_CAM should remain in kernel configuration to make ata
395 module work as CAM driver supporting legacy ATA controllers. Device ata
396 still can be used in modular fashion (atacore + ...). Modules atadisk
397 and atapi* are not used and won't affect operation in ATA_CAM mode.
398 Note that to use CAM-based ATA kernel should include CAM devices
399 scbus, pass, da (or explicitly ada), cd and optionally others. All of
400 them are parts of the cam module.
402 ataraid(4) functionality is now supported by the RAID GEOM class.
403 To use it you can load geom_raid kernel module and use graid(8) tool
404 for management. Instead of /dev/arX device names, use /dev/raid/rX.
406 No kernel config options or code have been removed, so if a problem
407 arises, please report it and optionally revert to the old ATA stack.
408 In order to do it you can remove from the kernel config:
413 , and instead add back:
414 device atadisk # ATA disk drives
415 device ataraid # ATA RAID drives
416 device atapicd # ATAPI CDROM drives
417 device atapifd # ATAPI floppy drives
418 device atapist # ATAPI tape drives
421 The default NFS server has been changed to the new server, which
422 was referred to as the experimental server. If you need to switch
423 back to the old NFS server, you must now put the "-o" option on
424 both the mountd and nfsd commands. This can be done using the
425 mountd_flags and nfs_server_flags rc.conf variables until an
426 update to the rc scripts is committed, which is coming soon.
429 The GNU Objective-C runtime library (libobjc), and other Objective-C
430 related components have been removed from the base system. If you
431 require an Objective-C library, please use one of the available ports.
434 ath(4) has been split into bus- and device- modules. if_ath contains
435 the HAL, the TX rate control and the network device code. if_ath_pci
436 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
437 contains the AHB glue. Users need to load both if_ath_pci and if_ath
438 in order to use ath on everything else.
440 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
441 need to load if_ath and if_ath_pci for ath(4) operation.
444 As part of the replacement of sysinstall, the process of building
445 release media has changed significantly. For details, please re-read
446 release(7), which has been updated to reflect the new build process.
449 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
450 is the last available version under GPLv2. It brings a number of new
451 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
452 4.1 and SSE 4.2), better support for powerpc64, a number of new
453 directives, and lots of other small improvements. See the ChangeLog
454 file in contrib/binutils for the full details.
457 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
458 compliant, and will now use half of hash for authentication.
459 This will break interoperability with all stacks (including all
460 actual FreeBSD versions) who implement
461 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
463 The only workaround with such peers is to use another HMAC
464 algorithm for IPsec ("phase 2") authentication.
467 Remove the uio_yield prototype and symbol. This function has
468 been misnamed since it was introduced and should not be
469 globally exposed with this name. The equivalent functionality
470 is now available using kern_yield(curthread->td_user_pri).
471 The function remains undocumented.
474 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
475 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
476 for scalar sysctls is defined but disabled. Code that needs
477 UQUAD to pass the type checking that must compile on older
478 systems where the define is not present can check against
479 __FreeBSD_version >= 900030.
481 The system dialog(1) has been replaced with a new version previously
482 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
483 with the previous version, but the libdialog associated with it has
484 a largely incompatible API. As such, the original version of libdialog
485 will be kept temporarily as libodialog, until its base system consumers
486 are replaced or updated. Bump __FreeBSD_version to 900030.
489 If you are trying to run make universe on a -stable system, and you get
490 the following warning:
491 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
492 unknown. config(8) likely too old."
493 or something similar to it, then you must upgrade your -stable system
494 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
495 stable/8) or build the config from the latest stable/8 branch and
496 install it on your system.
498 Prior to this date, building a current universe on 8-stable system from
499 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
500 error in the first kernel build phase. A new config on those old
501 systems will fix that problem for older versions of -current.
504 The TCP stack has been modified to allow Khelp modules to interact with
505 it via helper hook points and store per-connection data in the TCP
506 control block. Bump __FreeBSD_version to 900029. User space tools that
507 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
511 Generic IEEE 802.3 annex 31B full duplex flow control support has been
512 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
513 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
514 to take advantage of it instead of using custom implementations. This
515 means that these drivers now no longer unconditionally advertise
516 support for flow control but only do so if flow control is a selected
517 media option. This was implemented in the generic support that way in
518 order to allow flow control to be switched on and off via ifconfig(8)
519 with the PHY specific default to typically off in order to protect
520 from unwanted effects. Consequently, if you used flow control with
521 one of the above mentioned drivers you now need to explicitly enable
523 ifconfig bge0 media auto mediaopt flowcontrol
525 Along with the above mentioned changes generic support for setting
526 1000baseT master mode also has been added and brgphy(4), ciphy(4),
527 e1000phy(4) as well as ip1000phy(4) have been converted to take
528 advantage of it. This means that these drivers now no longer take the
529 link0 parameter for selecting master mode but the master media option
530 has to be used instead, for example like in the following:
531 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
533 Selection of master mode now is also available with all other PHY
534 drivers supporting 1000baseT.
537 The TCP stack has received a significant update to add support for
538 modularised congestion control and generally improve the clarity of
539 congestion control decisions. Bump __FreeBSD_version to 900025. User
540 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
541 sockstat) need to be recompiled.
544 The man(1) utility has been replaced by a new version that no longer
545 uses /etc/manpath.config. Please consult man.conf(5) for how to
546 migrate local entries to the new format.
549 The copyright strings printed by login(1) and sshd(8) at the time of a
550 new connection have been removed to follow other operating systems and
554 A workaround for a fixed ld bug has been removed in kernel code,
555 so make sure that your system ld is built from sources after
556 revision 210245 from 2010-07-19 (r211583 if building head kernel
557 on stable/8, r211584 for stable/7; both from 2010-08-21).
558 A symptom of incorrect ld version is different addresses for
559 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
562 The $ipv6_prefer variable in rc.conf(5) has been split into
563 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
565 The $ip6addrctl_policy is a variable to choose a pre-defined
566 address selection policy set by ip6addrctl(8). A value
567 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
570 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
571 flag (see an entry of 20090926) is set on an interface with no
572 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
573 security reason. If you want IPv6 link-local address on all
574 interfaces by default, set this to "YES".
576 The old ipv6_prefer="YES" is equivalent to
577 ipv6_activate_all_interfaces="YES" and
578 ip6addrctl_policy="ipv6_prefer".
581 DTrace has grown support for userland tracing. Due to this, DTrace is
582 now i386 and amd64 only.
583 dtruss(1) is now installed by default on those systems and a new
584 kernel module is needed for userland tracing: fasttrap.
585 No changes to your kernel config file are necessary to enable
586 userland tracing, but you might consider adding 'STRIP=' and
587 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
588 to have informative userland stack traces in DTrace (ustack).
591 The acpi_aiboost(4) driver has been removed in favor of the new
592 aibs(4) driver. You should update your kernel configuration file.
595 BSD grep has been imported to the base system and it is built by
596 default. It is completely BSD licensed, highly GNU-compatible, uses
597 less memory than its GNU counterpart and has a small codebase.
598 However, it is slower than its GNU counterpart, which is mostly
599 noticeable for larger searches, for smaller ones it is measurable
600 but not significant. The reason is complex, the most important factor
601 is that we lack a modern and efficient regex library and GNU
602 overcomes this by optimizing the searches internally. Future work
603 on improving the regex performance is planned, for the meantime,
604 users that need better performance, can build GNU grep instead by
605 setting the WITH_GNU_GREP knob.
608 Due to the import of powerpc64 support, all existing powerpc kernel
609 configuration files must be updated with a machine directive like this:
610 machine powerpc powerpc
612 In addition, an updated config(8) is required to build powerpc kernels
616 A new version of ZFS (version 15) has been merged to -HEAD.
617 This version uses a python library for the following subcommands:
618 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
619 For full functionality of these commands the following port must
620 be installed: sysutils/py-zfs
623 'vm_page's are now hashed by physical address to an array of mutexes.
624 Currently this is only used to serialize access to hold_count. Over
625 time the page queue mutex will be peeled away. This changes the size
626 of pmap on every architecture. And requires all callers of vm_page_hold
627 and vm_page_unhold to be updated.
630 WITH_CTF can now be specified in src.conf (not recommended, there
631 are some problems with static executables), make.conf (would also
632 affect ports which do not use GNU make and do not override the
633 compile targets) or in the kernel config (via "makeoptions
635 When WITH_CTF was specified there before this was silently ignored,
636 so make sure that WITH_CTF is not used in places which could lead
637 to unwanted behavior.
640 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
641 to allow 32-bit compatibility on non-x86 platforms. All kernel
642 configurations on amd64 and ia64 platforms using these options must
643 be modified accordingly.
646 The utmp user accounting database has been replaced with utmpx,
647 the user accounting interface standardized by POSIX.
648 Unfortunately the semantics of utmp and utmpx don't match,
649 making it practically impossible to support both interfaces.
650 The user accounting database is used by tools like finger(1),
651 last(1), talk(1), w(1) and ac(8).
653 All applications in the base system use utmpx. This means only
654 local binaries (e.g. from the ports tree) may still use these
655 utmp database files. These applications must be rebuilt to make
658 After the system has been upgraded, it is safe to remove the old
659 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
660 assuming their contents is of no importance anymore. Old wtmp
661 databases can only be used by last(1) and ac(8) after they have
662 been converted to the new format using wtmpcvt(1).
665 Introduce the kernel thread "deadlock resolver" (which can be enabled
666 via the DEADLKRES option, see NOTES for more details) and the
667 sleepq_type() function for sleepqueues.
670 The rc.firewall and rc.firewall6 were unified, and
671 rc.firewall6 and rc.d/ip6fw were removed.
672 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
673 variables are obsoleted. Instead, the following new rc
674 variables are added to rc.d/ipfw:
676 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
677 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
678 firewall_simple_onet_ipv6, firewall_trusted_ipv6
680 The meanings correspond to the relevant IPv4 variables.
686 The default terminal emulation for syscons(4) has been changed
687 from cons25 to xterm on all platforms except pc98. This means
688 that the /etc/ttys file needs to be updated to ensure correct
689 operation of applications on the console.
691 The terminal emulation style can be toggled per window by using
692 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
693 options can be used to change the compile-time default back to
696 To prevent graphical artifacts, make sure the TERM environment
697 variable is set to match the terminal emulation that is being
698 performed by syscons(4).
701 The layout of the structure ieee80211req_scan_result has changed.
702 Applications that require wireless scan results (e.g. ifconfig(8))
703 from net80211 need to be recompiled.
705 Applications such as wpa_supplicant(8) may require a full world
706 build without using NO_CLEAN in order to get synchronized with the
710 The iwn(4) driver has been updated to support the 5000 and 5150 series.
711 There's one kernel module for each firmware. Adding "device iwnfw"
712 to the kernel configuration file means including all three firmware
713 images inside the kernel. If you want to include just the one for
714 your wireless card, use the devices iwn4965fw, iwn5000fw or
718 The rc.d/network_ipv6, IPv6 configuration script has been integrated
719 into rc.d/netif. The changes are the following:
721 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
722 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
723 Note that both variables need the "inet6" keyword at the head.
725 Do not set $ipv6_network_interfaces manually if you do not
726 understand what you are doing. It is not needed in most cases.
728 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
731 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
732 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
734 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
735 all configured interfaces have "inet6 accept_rtadv" in the
736 $ifconfig_IF_ipv6. These are for backward compatibility.
738 3. A new variable $ipv6_prefer has been added. If NO, IPv6
739 functionality of interfaces with no corresponding
740 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
741 and the default address selection policy of ip6addrctl(8)
742 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
743 Note that if you want to configure IPv6 functionality on the
744 disabled interfaces after boot, first you need to clear the flag by
745 using ifconfig(8) like:
747 ifconfig em0 inet6 -ifdisabled
749 If YES, the default address selection policy is set as
752 The default value of $ipv6_prefer is NO.
754 4. If your system need to receive Router Advertisement messages,
755 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
756 scripts automatically invoke rtsol(8) when the interface becomes
757 UP. The Router Advertisement messages are used for SLAAC
758 (State-Less Address AutoConfiguration).
761 802.11s D3.03 support was committed. This is incompatible with the
762 previous code, which was based on D3.0.
765 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
766 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
767 control whether accepting Router Advertisement messages or not.
768 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
769 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
770 The ifconfig(8) utility now supports these flags.
773 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
774 mount(8) and -a option for df(1) to see them.
777 The old tunable hw.bus.devctl_disable has been superseded by
778 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
779 replaced by hw.bus.devctl_queue=0. The default for this new tunable
783 Remove the option STOP_NMI. The default action is now to use NMI only
784 for KDB via the newly introduced function stop_cpus_hard() and
785 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
788 The stable/8 branch created in subversion. This corresponds to the
789 RELENG_8 branch in CVS.
792 Bump the shared library version numbers for all libraries that do not
793 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
794 __FreeBSD_version to 800105.
797 Due to changes in the implementation of virtual network stack support,
798 all network-related kernel modules must be recompiled. As this change
799 breaks the ABI, bump __FreeBSD_version to 800104.
802 The TOE interface to the TCP syncache has been modified to remove
803 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
804 The cxgb driver is the only TOE consumer affected by this change, and
805 needs to be recompiled along with the kernel. As this change breaks
806 the ABI, bump __FreeBSD_version to 800103.
809 Padding has been added to struct tcpcb, sackhint and tcpstat in
810 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
811 maintaining the ABI. However, this change breaks the ABI, so bump
812 __FreeBSD_version to 800102. User space tools that rely on the size of
813 any of these structs (e.g. sockstat) need to be recompiled.
816 The NFS_LEGACYRPC option has been removed along with the old kernel
817 RPC implementation that this option selected. Kernel configurations
818 may need to be adjusted.
821 The network interface device nodes at /dev/net/<interface> have been
822 removed. All ioctl operations can be performed the normal way using
823 routing sockets. The kqueue functionality can generally be replaced
824 with routing sockets.
827 The documentation from the FreeBSD Documentation Project (Handbook,
828 FAQ, etc.) is now installed via packages by sysinstall(8) and under
829 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
832 The ABI of various structures related to the SYSV IPC API have been
833 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
834 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
838 Layout of struct vnet has changed as routing related variables were
839 moved to their own Vimage module. Modules need to be recompiled. Bump
840 __FreeBSD_version to 800099.
843 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
844 respectively. As long as no more than 16 groups per process are used,
845 no changes should be visible. When more than 16 groups are used, old
846 binaries may fail if they call getgroups() or getgrouplist() with
847 statically sized storage. Recompiling will work around this, but
848 applications should be modified to use dynamically allocated storage
849 for group arrays as POSIX.1-2008 does not cap an implementation's
850 number of supported groups at NGROUPS_MAX+1 as previous versions did.
852 NFS and portalfs mounts may also be affected as the list of groups is
853 truncated to 16. Users of NFS who use more than 16 groups, should
854 take care that negative group permissions are not used on the exported
855 file systems as they will not be reliable unless a GSSAPI based
856 authentication method is used.
859 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
860 option compiles in the support for adaptive spinning for lockmgrs
861 which want to enable it. The lockinit() function now accepts the flag
862 LK_ADAPTIVE in order to make the lock object subject to adaptive
863 spinning when both held in write and read mode.
866 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
867 changed. User applications that use this ioctl need to be rebuilt.
870 The layout of struct thread has changed. Kernel and modules need to
874 The layout of structs ifnet, domain, protosw and vnet_net has changed.
875 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
878 window(1) has been removed from the base system. It can now be
879 installed from ports. The port is called misc/window.
882 The way we are storing and accessing `routing table' entries has
883 changed. Programs reading the FIB, like netstat, need to be
887 A new netisr implementation has been added for FreeBSD 8. Network
888 file system modules, such as igmp, ipdivert, and others, should be
890 Bump __FreeBSD_version to 800096.
893 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
897 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
898 Bump __FreeBSD_version to 800094.
901 Add mnt_xflag field to 'struct mount'. File system modules need to be
903 Bump __FreeBSD_version to 800093.
906 The compiling option ADAPTIVE_SX has been retired while it has been
907 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
908 The KPI for sx_init_flags() changes as accepting flags:
909 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
910 been introduced in order to handle the reversed logic.
911 Bump __FreeBSD_version to 800092.
914 Add support for hierarchical jails. Remove global securelevel.
915 Bump __FreeBSD_version to 800091.
918 The layout of struct vnet_net has changed, therefore modules
920 Bump __FreeBSD_version to 800090.
923 The newly imported zic(8) produces a new format in the output. Please
924 run tzsetup(8) to install the newly created data to /etc/localtime.
927 The sysctl tree for the usb stack has renamed from hw.usb2.* to
928 hw.usb.* and is now consistent again with previous releases.
931 802.11 monitor mode support was revised and driver api's were changed.
932 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
933 of DLT_IEEE802_11. No user-visible data structures were changed but
934 applications that use DLT_IEEE802_11 may require changes.
935 Bump __FreeBSD_version to 800088.
938 The layout of the following structs has changed: sysctl_oid,
939 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
940 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
941 panics may be experienced. World rebuild is required for
942 correctly checking networking state from userland.
943 Bump __FreeBSD_version to 800085.
946 MLDv2 and Source-Specific Multicast (SSM) have been merged
947 to the IPv6 stack. VIMAGE hooks are in but not yet used.
948 The implementation of SSM within FreeBSD's IPv6 stack closely
949 follows the IPv4 implementation.
951 For kernel developers:
953 * The most important changes are that the ip6_output() and
954 ip6_input() paths no longer take the IN6_MULTI_LOCK,
955 and this lock has been downgraded to a non-recursive mutex.
957 * As with the changes to the IPv4 stack to support SSM, filtering
958 of inbound multicast traffic must now be performed by transport
959 protocols within the IPv6 stack. This does not apply to TCP and
960 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
962 * The KPIs used by IPv6 multicast are similar to those used by
963 the IPv4 stack, with the following differences:
964 * im6o_mc_filter() is analogous to imo_multicast_filter().
965 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
966 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
967 * IN6_LOOKUP_MULTI() has been deprecated and removed.
968 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
969 for MLDv1 have an additional 'timer' argument which is used to
970 jitter the initial membership report for the solicited-node
971 multicast membership on-link.
972 * This is not strictly needed for MLDv2, which already jitters
973 its report transmissions. However, the 'timer' argument is
974 preserved in case MLDv1 is active on the interface.
976 * The KAME linked-list based IPv6 membership implementation has
977 been refactored to use a vector similar to that used by the IPv4
979 Code which maintains a list of its own multicast memberships
980 internally, e.g. carp, has been updated to reflect the new
983 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
984 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
985 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
986 implementation constraint which needs to be addressed in HEAD.
988 For application developers:
990 * The changes are broadly similar to those made for the IPv4
993 * The use of IPv4 and IPv6 multicast socket options on the same
994 socket, using mapped addresses, HAS NOT been tested or supported.
996 * There are a number of issues with the implementation of various
997 IPv6 multicast APIs which need to be resolved in the API surface
998 before the implementation is fully compatible with KAME userland
999 use, and these are mostly to do with interface index treatment.
1001 * The literature available discusses the use of either the delta / ASM
1002 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1003 using setsourcefilter(3)/getsourcefilter(3). For more information
1004 please refer to RFC 3768, 'Socket Interface Extensions for
1005 Multicast Source Filters'.
1007 * Applications which use the published RFC 3678 APIs should be fine.
1009 For systems administrators:
1011 * The mtest(8) utility has been refactored to support IPv6, in
1012 addition to IPv4. Interface addresses are no longer accepted
1013 as arguments, their names must be used instead. The utility
1014 will map the interface name to its first IPv4 address as
1015 returned by getifaddrs(3).
1017 * The ifmcstat(8) utility has also been updated to print the MLDv2
1018 endpoint state and source filter lists via sysctl(3).
1020 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1021 loopback of IPv6 multicast datagrams by default; it defaults to 1
1022 to preserve the existing behaviour. Disabling multicast loopback is
1023 recommended for optimal system performance.
1025 * The IPv6 MROUTING code has been changed to examine this sysctl
1026 instead of attempting to perform a group lookup before looping
1027 back forwarded datagrams.
1029 Bump __FreeBSD_version to 800084.
1032 Implement low-level Bluetooth HCI API.
1033 Bump __FreeBSD_version to 800083.
1036 The layout of struct malloc_type, used by modules to register new
1037 memory allocation types, has changed. Most modules will need to
1038 be rebuilt or panics may be experienced.
1039 Bump __FreeBSD_version to 800081.
1042 Anticipate overflowing inp_flags - add inp_flags2.
1043 This changes most offsets in inpcb, so checking v4 connection
1044 state will require a world rebuild.
1045 Bump __FreeBSD_version to 800080.
1048 Add an llentry to struct route and struct route_in6. Modules
1049 embedding a struct route will need to be recompiled.
1050 Bump __FreeBSD_version to 800079.
1053 The size of rt_metrics_lite and by extension rtentry has changed.
1054 Networking administration apps will need to be recompiled.
1055 The route command now supports show as an alias for get, weighting
1056 of routes, sticky and nostick flags to alter the behavior of stateful
1058 Bump __FreeBSD_version to 800078.
1061 Do not use Giant for kbdmux(4) locking. This is wrong and
1062 apparently causing more problems than it solves. This will
1063 re-open the issue where interrupt handlers may race with
1064 kbdmux(4) in polling mode. Typical symptoms include (but
1065 not limited to) duplicated and/or missing characters when
1066 low level console functions (such as gets) are used while
1067 interrupts are enabled (for example geli password prompt,
1068 mountroot prompt etc.). Disabling kbdmux(4) may help.
1071 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1072 kernel modules referencing any of the above need to be recompiled.
1073 Bump __FreeBSD_version to 800075.
1076 GEOM_PART has become the default partition slicer for storage devices,
1077 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1078 introduces some changes:
1080 MSDOS/EBR: the devices created from MSDOS extended partition entries
1081 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1082 to devices with offset-based names. fstabs may need to be modified.
1084 BSD: the "geometry does not match label" warning is harmless in most
1085 cases but it points to problems in file system misalignment with
1086 disk geometry. The "c" partition is now implicit, covers the whole
1087 top-level drive and cannot be (mis)used by users.
1089 General: Kernel dumps are now not allowed to be written to devices
1090 whose partition types indicate they are meant to be used for file
1091 systems (or, in case of MSDOS partitions, as something else than
1094 Most of these changes date approximately from 200812.
1097 The uscanner(4) driver has been removed from the kernel. This follows
1098 Linux removing theirs in 2.6 and making libusb the default interface
1099 (supported by sane).
1102 The multicast forwarding code has been cleaned up. netstat(1)
1103 only relies on KVM now for printing bandwidth upcall meters.
1104 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1105 ip6_mroute_mod respectively. The config(5) options for statically
1106 compiling this code remain the same, i.e. 'options MROUTING'.
1109 Support for the IFF_NEEDSGIANT network interface flag has been
1110 removed, which means that non-MPSAFE network device drivers are no
1111 longer supported. In particular, if_ar, if_sr, and network device
1112 drivers from the old (legacy) USB stack can no longer be built or
1116 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1117 a bunch of new language catalog files have also been added.
1118 This means that some common libc messages are now localized and
1119 they depend on the LC_MESSAGES environmental variable.
1122 The k8temp(4) driver has been renamed to amdtemp(4) since
1123 support for Family 10 and Family 11 CPU families was added.
1126 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1127 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1129 For kernel developers, the most important changes are that the
1130 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1131 and this lock has been downgraded to a non-recursive mutex.
1133 Transport protocols (UDP, Raw IP) are now responsible for filtering
1134 inbound multicast traffic according to group membership and source
1135 filters. The imo_multicast_filter() KPI exists for this purpose.
1136 Transports which do not use multicast (SCTP, TCP) already reject
1137 multicast by default. Forwarding and receive performance may improve
1138 as a mutex acquisition is no longer needed in the ip_input()
1139 low-level input path. in_addmulti() and in_delmulti() are shimmed
1140 to new KPIs which exist to support SSM in-kernel.
1142 For application developers, it is recommended that loopback of
1143 multicast datagrams be disabled for best performance, as this
1144 will still cause the lock to be taken for each looped-back
1145 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1146 be tuned to 0 to disable loopback by default; it defaults to 1
1147 to preserve the existing behaviour.
1149 For systems administrators, to obtain best performance with
1150 multicast reception and multiple groups, it is always recommended
1151 that a card with a suitably precise hash filter is used. Hash
1152 collisions will still result in the lock being taken within the
1153 transport protocol input path to check group membership.
1155 If deploying FreeBSD in an environment with IGMP snooping switches,
1156 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1157 enabled; this forces 224.0.0.0/24 group membership to be announced
1160 The size of 'struct igmpstat' has changed; netstat needs to be
1161 recompiled to reflect this.
1162 Bump __FreeBSD_version to 800070.
1165 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1166 updated to use it. This requires a buildworld/installworld in order to
1167 update the library and dependencies (usbconfig, etc). Its advisable to
1168 rebuild all ports which uses libusb. More specific directions are given
1169 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1170 libusb are no longer required and can be removed.
1173 A workaround is committed to allow the creation of System V shared
1174 memory segment of size > 2 GB on the 64-bit architectures.
1175 Due to a limitation of the existing ABI, the shm_segsz member
1176 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1177 wrong for large segments. Note that limits must be explicitly
1178 raised to allow such segments to be created.
1181 The layout of struct ifnet has changed, requiring a rebuild of all
1182 network device driver modules.
1185 The /dev handling for the new USB stack has changed, a
1186 buildworld/installworld is required for libusb20.
1189 The new USB2 stack has now been permanently moved in and all kernel and
1190 module names reverted to their previous values (eg, usb, ehci, ohci,
1191 ums, ...). The old usb stack can be compiled in by prefixing the name
1192 with the letter 'o', the old usb modules have been removed.
1193 Updating entry 20090216 for xorg and 20090215 for libmap may still
1197 The rc.conf(5) option if_up_delay has been renamed to
1198 defaultroute_delay to better reflect its purpose. If you have
1199 customized this setting in /etc/rc.conf you need to update it to
1203 xorg 7.4 wants to configure its input devices via hald which does not
1204 yet work with USB2. If the keyboard/mouse does not work in xorg then
1206 Option "AllowEmptyInput" "off"
1207 to your ServerLayout section. This will cause X to use the configured
1208 kbd and mouse sections from your xorg.conf.
1211 The GENERIC kernels for all architectures now default to the new USB2
1212 stack. No kernel config options or code have been removed so if a
1213 problem arises please report it and optionally revert to the old USB
1214 stack. If you are loading USB kernel modules or have a custom kernel
1215 that includes GENERIC then ensure that usb names are also changed over,
1216 eg uftdi -> usb2_serial_ftdi.
1218 Older programs linked against the ports libusb 0.1 need to be
1219 redirected to the new stack's libusb20. /etc/libmap.conf can
1221 # Map old usb library to new one for usb2 stack
1222 libusb-0.1.so.8 libusb20.so.1
1225 All USB ethernet devices now attach as interfaces under the name ueN
1226 (eg. ue0). This is to provide a predictable name as vendors often
1227 change usb chipsets in a product without notice.
1230 The ichsmb(4) driver has been changed to require SMBus slave
1231 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1232 All of the other SMBus controller drivers require left-justified
1233 slave addresses, so this change makes all the drivers provide the
1237 INET6 statistics (struct ip6stat) was updated.
1238 netstat(1) needs to be recompiled.
1241 NTFS has been removed from GENERIC kernel on amd64 to match
1242 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1243 will load ntfs.ko module automatically when NTFS support is
1244 actually needed, unless ntfs.ko is not installed or security
1245 level prohibits loading kernel modules. If either is the case,
1246 "options NTFS" has to be added into kernel config.
1249 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1250 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1251 800061. User space tools that rely on the size of struct tcpcb in
1252 tcp_var.h (e.g. sockstat) need to be recompiled.
1255 ng_tty(4) module updated to match the new TTY subsystem.
1256 Due to API change, user-level applications must be updated.
1257 New API support added to mpd5 CVS and expected to be present
1258 in next mpd5.3 release.
1261 With __FreeBSD_version 800060 the makefs tool is part of
1262 the base system (it was a port).
1265 The afdata and ifnet locks have been changed from mutexes to
1266 rwlocks, network modules will need to be re-compiled.
1269 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1270 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1271 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1272 architecture and 40 bytes on 64-bit architecture. The userland
1273 applications "arp" and "ndp" have been updated accordingly.
1274 The output from "netstat -r" shows only routing entries and
1275 none of the L2 information.
1278 __FreeBSD_version 800057 marks the switchover from the
1279 binary ath hal to source code. Users must add the line:
1281 options AH_SUPPORT_AR5416
1283 to their kernel config files when specifying:
1287 The ath_hal module no longer exists; the code is now compiled
1288 together with the driver in the ath module. It is now
1289 possible to tailor chip support (i.e. reduce the set of chips
1290 and thereby the code size); consult ath_hal(4) for details.
1293 __FreeBSD_version 800054 adds memory barriers to
1294 <machine/atomic.h>, new interfaces to ifnet to facilitate
1295 multiple hardware transmit queues for cards that support
1296 them, and a lock-less ring-buffer implementation to
1297 enable drivers to more efficiently manage queueing of
1301 A new version of ZFS (version 13) has been merged to -HEAD.
1302 This version has zpool attribute "listsnapshots" off by
1303 default, which means "zfs list" does not show snapshots,
1304 and is the same as Solaris behavior.
1307 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1310 The uhci, ohci, ehci and slhci USB Host controller drivers have
1311 been put into separate modules. If you load the usb module
1312 separately through loader.conf you will need to load the
1313 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1314 controller add the following to loader.conf:
1320 The ABI used by the PMC toolset has changed. Please keep
1321 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1325 atapci kernel module now includes only generic PCI ATA
1326 driver. AHCI driver moved to ataahci kernel module.
1327 All vendor-specific code moved into separate kernel modules:
1328 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1329 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1330 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1331 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1334 The TTY subsystem of the kernel has been replaced by a new
1335 implementation, which provides better scalability and an
1336 improved driver model. Most common drivers have been migrated to
1337 the new TTY subsystem, while others have not. The following
1338 drivers have not yet been ported to the new TTY layer:
1341 cy, digi, rc, rp, sio
1347 ng_h4, ng_tty, ppp, sl, snp
1349 Adding these drivers to your kernel configuration file shall
1350 cause compilation to fail.
1353 ntpd has been upgraded to 4.2.4p5.
1356 OpenSSH has been upgraded to 5.1p1.
1358 For many years, FreeBSD's version of OpenSSH preferred DSA
1359 over RSA for host and user authentication keys. With this
1360 upgrade, we've switched to the vendor's default of RSA over
1361 DSA. This may cause upgraded clients to warn about unknown
1362 host keys even for previously known hosts. Users should
1363 follow the usual procedure for verifying host keys before
1364 accepting the RSA key.
1366 This can be circumvented by setting the "HostKeyAlgorithms"
1367 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1370 Please note that the sequence of keys offered for
1371 authentication has been changed as well. You may want to
1372 specify IdentityFile in a different order to revert this
1376 The sio(4) driver has been removed from the i386 and amd64
1377 kernel configuration files. This means uart(4) is now the
1378 default serial port driver on those platforms as well.
1380 To prevent collisions with the sio(4) driver, the uart(4) driver
1381 uses different names for its device nodes. This means the
1382 onboard serial port will now most likely be called "ttyu0"
1383 instead of "ttyd0". You may need to reconfigure applications to
1384 use the new device names.
1386 When using the serial port as a boot console, be sure to update
1387 /boot/device.hints and /etc/ttys before booting the new kernel.
1388 If you forget to do so, you can still manually specify the hints
1389 at the loader prompt:
1391 set hint.uart.0.at="isa"
1392 set hint.uart.0.port="0x3F8"
1393 set hint.uart.0.flags="0x10"
1394 set hint.uart.0.irq="4"
1398 The gpt(8) utility has been removed. Use gpart(8) to partition
1402 The version that Linuxulator emulates was changed from 2.4.2
1403 to 2.6.16. If you experience any problems with Linux binaries
1404 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1405 if it fixes the problem contact emulation mailing list.
1408 ISDN4BSD (I4B) was removed from the src tree. You may need to
1409 update a your kernel configuration and remove relevant entries.
1412 I have checked in code to support multiple routing tables.
1413 See the man pages setfib(1) and setfib(2).
1414 This is a hopefully backwards compatible version,
1415 but to make use of it you need to compile your kernel
1416 with options ROUTETABLES=2 (or more up to 16).
1419 The 802.11 wireless support was redone to enable multi-bss
1420 operation on devices that are capable. The underlying device
1421 is no longer used directly but instead wlanX devices are
1422 cloned with ifconfig. This requires changes to rc.conf files.
1423 For example, change:
1424 ifconfig_ath0="WPA DHCP"
1427 ifconfig_wlan0="WPA DHCP"
1428 see rc.conf(5) for more details. In addition, mergemaster of
1429 /etc/rc.d is highly recommended. Simultaneous update of userland
1430 and kernel wouldn't hurt either.
1432 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1433 modules were merged into the base wlan module. All references
1434 to these modules (e.g. in kernel config files) must be removed.
1437 psm(4) has gained write(2) support in native operation level.
1438 Arbitrary commands can be written to /dev/psm%d and status can
1439 be read back from it. Therefore, an application is responsible
1440 for status validation and error recovery. It is a no-op in
1441 other operation levels.
1444 Support for KSE threading has been removed from the kernel. To
1445 run legacy applications linked against KSE libmap.conf may
1446 be used. The following libmap.conf may be used to ensure
1447 compatibility with any prior release:
1449 libpthread.so.1 libthr.so.1
1450 libpthread.so.2 libthr.so.2
1451 libkse.so.3 libthr.so.3
1454 The layout of struct vmspace has changed. This affects libkvm
1455 and any executables that link against libkvm and use the
1456 kvm_getprocs() function. In particular, but not exclusively,
1457 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1458 The effects are minimal, but it's advisable to upgrade world
1462 The latest em driver no longer has support in it for the
1463 82575 adapter, this is now moved to the igb driver. The
1464 split was done to make new features that are incompatible
1465 with older hardware easier to do.
1468 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1469 likewise the kernel option is now GEOM_LINUX_LVM.
1472 The default NFS mount mode has changed from UDP to TCP for
1473 increased reliability. If you rely on (insecurely) NFS
1474 mounting across a firewall you may need to update your
1478 Belatedly note the addition of m_collapse for compacting
1482 The fts(3) structures have been changed to use adequate
1483 integer types for their members and so to be able to cope
1484 with huge file trees. The old fts(3) ABI is preserved
1485 through symbol versioning in libc, so third-party binaries
1486 using fts(3) should still work, although they will not take
1487 advantage of the extended types. At the same time, some
1488 third-party software might fail to build after this change
1489 due to unportable assumptions made in its source code about
1490 fts(3) structure members. Such software should be fixed
1491 by its vendor or, in the worst case, in the ports tree.
1492 FreeBSD_version 800015 marks this change for the unlikely
1493 case that a portable fix is impossible.
1496 To upgrade to -current after this date, you must be running
1497 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1498 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1501 The ADAPTIVE_GIANT kernel option has been retired because its
1502 functionality is the default now.
1505 The AT keyboard emulation of sunkbd(4) has been turned on
1506 by default. In order to make the special symbols of the Sun
1507 keyboards driven by sunkbd(4) work under X these now have
1508 to be configured the same way as Sun USB keyboards driven
1509 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1511 Option "XkbLayout" "us"
1512 Option "XkbRules" "xorg"
1513 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1516 It has been decided that it is desirable to provide ABI
1517 backwards compatibility to the FreeBSD 4/5/6 versions of the
1518 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1519 broken with the introduction of PCI domain support (see the
1520 20070930 entry). Unfortunately, this required the ABI of
1521 PCIOCGETCONF to be broken again in order to be able to
1522 provide backwards compatibility to the old version of that
1523 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1524 again. As for prominent ports this affects neither pciutils
1525 nor xorg-server this time, the hal port needs to be rebuilt
1529 The misnamed kthread_create() and friends have been renamed
1530 to kproc_create() etc. Many of the callers already
1531 used kproc_start()..
1532 I will return kthread_create() and friends in a while
1533 with implementations that actually create threads, not procs.
1534 Renaming corresponds with version 800002.
1543 Avoid using make -j when upgrading. While generally safe, there are
1544 sometimes problems using -j to upgrade. If your upgrade fails with
1545 -j, please try again without -j. From time to time in the past there
1546 have been problems using -j with buildworld and/or installworld. This
1547 is especially true when upgrading between "distant" versions (eg one
1548 that cross a major release boundary or several minor releases, or when
1549 several months have passed on the -current branch).
1551 Sometimes, obscure build problems are the result of environment
1552 poisoning. This can happen because the make utility reads its
1553 environment when searching for values for global variables. To run
1554 your build attempts in an "environmental clean room", prefix all make
1555 commands with 'env -i '. See the env(1) manual page for more details.
1557 When upgrading from one major version to another it is generally best
1558 to upgrade to the latest code in the currently installed branch first,
1559 then do an upgrade to the new branch. This is the best-tested upgrade
1560 path, and has the highest probability of being successful. Please try
1561 this approach before reporting problems with a major version upgrade.
1565 When upgrading the boot ZFS pool to a new version, always follow
1568 1.) recompile and reinstall the ZFS boot loader and boot block
1569 (this is part of "make buildworld" and "make installworld")
1571 2.) update the ZFS boot block on your boot drive
1573 The following example updates the ZFS boot block on the first
1574 partition (freebsd-boot) of a GPT partitioned drive ad0:
1575 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1577 Non-boot pools do not need these updates.
1581 If you are updating from a prior version of FreeBSD (even one just
1582 a few days old), you should follow this procedure. It is the most
1583 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1585 make kernel-toolchain
1586 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1587 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1589 To test a kernel once
1590 ---------------------
1591 If you just want to boot a kernel once (because you are not sure
1592 if it works, or if you want to boot a known bad kernel to provide
1593 debugging information) run
1594 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1595 nextboot -k testkernel
1597 To just build a kernel when you know that it won't mess you up
1598 --------------------------------------------------------------
1599 This assumes you are already running a CURRENT system. Replace
1600 ${arch} with the architecture of your machine (e.g. "i386",
1601 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1603 cd src/sys/${arch}/conf
1604 config KERNEL_NAME_HERE
1605 cd ../compile/KERNEL_NAME_HERE
1610 If this fails, go to the "To build a kernel" section.
1612 To rebuild everything and install it on the current system.
1613 -----------------------------------------------------------
1614 # Note: sometimes if you are running current you gotta do more than
1615 # is listed here if you are upgrading from a really old current.
1617 <make sure you have good level 0 dumps>
1619 make kernel KERNCONF=YOUR_KERNEL_HERE
1621 <reboot in single user> [3]
1629 To cross-install current onto a separate partition
1630 --------------------------------------------------
1631 # In this approach we use a separate partition to hold
1632 # current's root, 'usr', and 'var' directories. A partition
1633 # holding "/", "/usr" and "/var" should be about 2GB in
1636 <make sure you have good level 0 dumps>
1639 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1640 <maybe newfs current's root partition>
1641 <mount current's root partition on directory ${CURRENT_ROOT}>
1642 make installworld DESTDIR=${CURRENT_ROOT}
1643 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1644 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1645 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1646 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1647 <reboot into current>
1648 <do a "native" rebuild/install as described in the previous section>
1649 <maybe install compatibility libraries from ports/misc/compat*>
1653 To upgrade in-place from stable to current
1654 ----------------------------------------------
1655 <make sure you have good level 0 dumps>
1657 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1659 <reboot in single user> [3]
1666 Make sure that you've read the UPDATING file to understand the
1667 tweaks to various things you need. At this point in the life
1668 cycle of current, things change often and you are on your own
1669 to cope. The defaults can also change, so please read ALL of
1670 the UPDATING entries.
1672 Also, if you are tracking -current, you must be subscribed to
1673 freebsd-current@freebsd.org. Make sure that before you update
1674 your sources that you have read and understood all the recent
1675 messages there. If in doubt, please track -stable which has
1676 much fewer pitfalls.
1678 [1] If you have third party modules, such as vmware, you
1679 should disable them at this point so they don't crash your
1682 [3] From the bootblocks, boot -s, and then do
1687 adjkerntz -i # if CMOS is wall time
1688 Also, when doing a major release upgrade, it is required that
1689 you boot into single user mode to do the installworld.
1691 [4] Note: This step is non-optional. Failure to do this step
1692 can result in a significant reduction in the functionality of the
1693 system. Attempting to do it by hand is not recommended and those
1694 that pursue this avenue should read this file carefully, as well
1695 as the archives of freebsd-current and freebsd-hackers mailing lists
1696 for potential gotchas. The -U option is also useful to consider.
1697 See mergemaster(8) for more information.
1699 [5] Usually this step is a noop. However, from time to time
1700 you may need to do this if you get unknown user in the following
1701 step. It never hurts to do it all the time. You may need to
1702 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1703 install) after the buildworld before this step if you last updated
1704 from current before 20020224 or from -stable before 20020408.
1706 [6] This only deletes old files and directories. Old libraries
1707 can be deleted by "make delete-old-libs", but you have to make
1708 sure that no program is using those libraries anymore.
1710 [8] In order to have a kernel that can run the 4.x binaries needed to
1711 do an installworld, you must include the COMPAT_FREEBSD4 option in
1712 your kernel. Failure to do so may leave you with a system that is
1713 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1714 required to run the 5.x binaries on more recent kernels. And so on
1715 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1717 Make sure that you merge any new devices from GENERIC since the
1718 last time you updated your kernel config file.
1720 [9] When checking out sources, you must include the -P flag to have
1721 cvs prune empty directories.
1723 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1724 "?=" instead of the "=" assignment operator, so that buildworld can
1725 override the CPUTYPE if it needs to.
1727 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1728 not on the command line, or in /etc/make.conf. buildworld will
1729 warn if it is improperly defined.
1732 This file contains a list, in reverse chronological order, of major
1733 breakages in tracking -current. It is not guaranteed to be a complete
1734 list of such breakages, and only contains entries since October 10, 2007.
1735 If you need to see UPDATING entries from before that date, you will need
1736 to fetch an UPDATING file from an older FreeBSD release.
1738 Copyright information:
1740 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1742 Redistribution, publication, translation and use, with or without
1743 modification, in full or in part, in any form or format of this
1744 document are permitted without further permission from the author.
1746 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1747 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1748 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1749 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1750 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1751 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1752 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1753 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1754 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1755 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1756 POSSIBILITY OF SUCH DAMAGE.
1758 Contact Warner Losh if you have any questions about your use of