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 Items affecting the ports and packages system can be found in
10 /usr/ports/UPDATING. Please read that file before running portupgrade.
12 NOTE TO PEOPLE WHO THINK THAT FreeBSD 10.x IS SLOW:
13 FreeBSD 10.x has many debugging features turned on, in both the kernel
14 and userland. These features attempt to detect incorrect use of
15 system primitives, and encourage loud failure through extra sanity
16 checking and fail stop semantics. They also substantially impact
17 system performance. If you want to do performance measurement,
18 benchmarking, and optimization, you'll want to turn them off. This
19 includes various WITNESS- related kernel options, INVARIANTS, malloc
20 debugging flags in userland, and various verbose features in the
21 kernel. Many developers choose to disable these features on build
22 machines to maximize performance. (To completely disable malloc
23 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
24 disable the most expensive debugging functionality run
25 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
28 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
29 This means that the world and kernel will be compiled with clang
30 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
31 and /usr/bin/cpp. To disable this behavior and revert to building
32 with gcc, compile with WITHOUT_CLANG_IS_CC.
35 The IPFIREWALL_FORWARD kernel option has been removed. Its
36 functionality now turned on by default.
39 The ZERO_COPY_SOCKET kernel option has been removed and
40 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
41 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
42 mechanism which is not safe and may result in kernel crashes.
43 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
44 driver supports disposeable external page sized mbuf storage.
45 Proper replacements for both zero-copy mechanisms are under
46 consideration and will eventually lead to complete removal
47 of the two kernel options.
50 The IPv4 network stack has been converted to network byte
51 order. The following modules need to be recompiled together
52 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
53 pf(4), ipfw(4), ng_ipfw(4), stf(4).
56 Support for non-MPSAFE filesystems was removed from VFS. The
57 VFS_VERSION was bumped, all filesystem modules shall be
61 All the non-MPSAFE filesystems have been disconnected from
62 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
66 The interface cloning API and ABI has changed. The following
67 modules need to be recompiled together with kernel:
68 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
69 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
70 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
73 The sdhci driver was split in two parts: sdhci (generic SD Host
74 Controller logic) and sdhci_pci (actual hardware driver).
75 No kernel config modifications are required, but if you
76 load sdhc as a module you must switch to sdhci_pci instead.
79 Import the FUSE kernel and userland support into base system.
82 The GNU sort(1) program has been removed since the BSD-licensed
83 sort(1) has been the default for quite some time and no serious
84 problems have been reported. The corresponding WITH_GNU_SORT
88 The pfil(9) API/ABI for AF_INET family has been changed. Packet
89 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
93 The net80211(4) ABI has been changed to allow for improved driver
94 PS-POLL and power-save support. All wireless drivers need to be
95 recompiled to work with the new kernel.
98 The random(4) support for the VIA hardware random number
99 generator (`PADLOCK') is no longer enabled unconditionally.
100 Add the PADLOCK_RNG option in the custom kernel config if
101 needed. The GENERIC kernels on i386 and amd64 do include the
102 option, so the change only affects the custom kernel
106 The pf(4) packet filter ABI has been changed. pfctl(8) and
107 snmp_pf module need to be recompiled to work with new kernel.
110 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
111 to -HEAD. Pools that have empty_bpobj in active state can not be
112 imported read-write with ZFS implementations that do not support
113 this feature. For more information read the zpool-features(5)
117 The sparc64 ZFS loader has been changed to no longer try to auto-
118 detect ZFS providers based on diskN aliases but now requires these
119 to be explicitly listed in the OFW boot-device environment variable.
122 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
123 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
124 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
127 The following sysctls and tunables have been renamed for consistency
128 with other variables:
129 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
130 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
133 The sort utility has been replaced with BSD sort. For now, GNU sort
134 is also available as "gnusort" or the default can be set back to
135 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
136 installed as "bsdsort".
139 A new version of ZFS (pool version 5000) has been merged to -HEAD.
140 Starting with this version the old system of ZFS pool versioning
141 is superseded by "feature flags". This concept enables forward
142 compatibility against certain future changes in functionality of ZFS
143 pools. The first read-only compatible "feature flag" for ZFS pools
144 is named "com.delphix:async_destroy". For more information
145 read the new zpool-features(5) manual page.
146 Please refer to the "ZFS notes" section of this file for information
147 on upgrading boot ZFS pools.
150 The malloc(3) implementation embedded in libc now uses sources imported
151 as contrib/jemalloc. The most disruptive API change is to
152 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
153 delete it prior to installworld, and optionally re-create it using the
154 new format after rebooting. See malloc.conf(5) for details
155 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
159 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
160 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
161 now spelled mips. This is to aid compatibility with third-party
162 software that expects this naming scheme in uname(3). Little-endian
163 settings are unchanged.
166 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
170 Now unix domain sockets behave "as expected" on nullfs(5). Previously
171 nullfs(5) did not pass through all behaviours to the underlying layer,
172 as a result if we bound to a socket on the lower layer we could connect
173 only to the lower path; if we bound to the upper layer we could connect
174 only to the upper path. The new behavior is one can connect to both the
175 lower and the upper paths regardless what layer path one binds to.
178 The getifaddrs upgrade path broken with 20111215 has been restored.
179 If you have upgraded in between 20111215 and 20120209 you need to
180 recompile libc again with your kernel. You still need to recompile
181 world to be able to configure CARP but this restriction already
185 The set_rcvar() function has been removed from /etc/rc.subr. All
186 base and ports rc.d scripts have been updated, so if you have a
187 port installed with a script in /usr/local/etc/rc.d you can either
188 hand-edit the rcvar= line, or reinstall the port.
190 An easy way to handle the mass-update of /etc/rc.d:
191 rm /etc/rc.d/* && mergemaster -i
194 panic(9) now stops other CPUs in the SMP systems, disables interrupts
195 on the current CPU and prevents other threads from running.
196 This behavior can be reverted using the kern.stop_scheduler_on_panic
198 The new behavior can be incompatible with kern.sync_on_panic.
201 The carp(4) facility has been changed significantly. Configuration
202 of the CARP protocol via ifconfig(8) has changed, as well as format
203 of CARP events submitted to devd(8) has changed. See manual pages
204 for more information. The arpbalance feature of carp(4) is currently
205 not supported anymore.
207 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
208 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
209 need to be recompiled.
212 The acpi_wmi(4) status device /dev/wmistat has been renamed to
216 The option VFS_ALLOW_NONMPSAFE option has been added in order to
217 explicitely support non-MPSAFE filesystems.
218 It is on by default for all supported platform at this present
222 The broken amd(4) driver has been replaced with esp(4) in the amd64,
223 i386 and pc98 GENERIC kernel configuration files.
226 sysinstall has been removed
229 The stable/9 branch created in subversion. This corresponds to the
230 RELENG_9 branch in CVS.
233 This commit modifies vfs_register() so that it uses a hash
234 calculation to set vfc_typenum, which is enabled by default.
235 The first time a system is booted after this change, the
236 vfc_typenum values will change for all file systems. The
237 main effect of this is a change to the NFS server file handles
238 for file systems that use vfc_typenum in their fsid, such as ZFS.
239 It will, however, prevent vfc_typenum from changing when file
240 systems are loaded in a different order for subsequent reboots.
241 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
242 until you are ready to remount all NFS clients after a reboot.
245 Bump the shared library version numbers for libraries that
246 do not use symbol versioning, have changed the ABI compared
247 to stable/8 and which shared library version was not bumped.
248 Done as part of 9.0-RELEASE cycle.
251 During the merge of Capsicum features, the fget(9) KPI was modified.
252 This may require the rebuilding of out-of-tree device drivers --
253 issues have been reported specifically with the nVidia device driver.
254 __FreeBSD_version is bumped to 900041.
256 Also, there is a period between 20110811 and 20110814 where the
257 special devices /dev/{stdin,stdout,stderr} did not work correctly.
258 Building world from a kernel during that window may not work.
261 The packet filter (pf) code has been updated to OpenBSD 4.5.
262 You need to update userland tools to be in sync with kernel.
263 This update breaks backward compatibility with earlier pfsync(4)
264 versions. Care must be taken when updating redundant firewall setups.
267 The following sysctls and tunables are retired on x86 platforms:
269 machdep.hlt_logical_cpus
270 The following sysctl is retired:
271 machdep.hyperthreading_allowed
272 The sysctls were supposed to provide a way to dynamically offline and
273 online selected CPUs on x86 platforms, but the implementation has not
274 been reliable especially with SCHED_ULE scheduler.
275 machdep.hyperthreading_allowed tunable is still available to ignore
276 hyperthreading CPUs at OS level.
277 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
278 where X is an APIC ID of a CPU. Be advised, though, that disabling
279 CPUs in non-uniform fashion will result in non-uniform topology and
280 may lead to sub-optimal system performance with SCHED_ULE, which is
284 cpumask_t type is retired and cpuset_t is used in order to describe
288 Changes to ifconfig(8) for dynamic address family detection mandate
289 that you are running a kernel of 20110525 or later. Make sure to
290 follow the update procedure to boot a new kernel before installing
294 Support for sun4v architecture is officially dropped
297 Several KPI breaking changes have been committed to the mii(4) layer,
298 the PHY drivers and consequently some Ethernet drivers using mii(4).
299 This means that miibus.ko and the modules of the affected Ethernet
300 drivers need to be recompiled.
302 Note to kernel developers: Given that the OUI bit reversion problem
303 was fixed as part of these changes all mii(4) commits related to OUIs,
304 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
305 handling, no longer can be merged verbatim to stable/8 and previous
309 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
310 into their kernel configurations along with 'device pci'.
313 The default NFS client is now the new NFS client, so fstype "newnfs"
314 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
315 Although mounts via fstype "nfs" will usually work without userland
316 changes, it is recommended that the mount(8) and mount_nfs(8)
317 commands be rebuilt from sources and that a link to mount_nfs called
318 mount_oldnfs be created. The new client is compiled into the
319 kernel with "options NFSCL" and this is needed for diskless root
320 file systems. The GENERIC kernel configs have been changed to use
321 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
322 To use the regular/old client, you can "mount -t oldnfs ...". For
323 a diskless root file system, you must also include a line like:
325 vfs.root.mountfrom="oldnfs:"
327 in the boot/loader.conf on the root fs on the NFS server to make
328 a diskless root fs use the old client.
331 The GENERIC kernels for all architectures now default to the new
332 CAM-based ATA stack. It means that all legacy ATA drivers were
333 removed and replaced by respective CAM drivers. If you are using
334 ATA device names in /etc/fstab or other places, make sure to update
335 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
336 where 'Y's are the sequential numbers starting from zero for each type
337 in order of detection, unless configured otherwise with tunables,
338 see cam(4)). There will be symbolic links created in /dev/ to map
339 old adX devices to the respective adaY. They should provide basic
340 compatibility for file systems mounting in most cases, but they do
341 not support old user-level APIs and do not have respective providers
342 in GEOM. Consider using updated management tools with new device names.
344 It is possible to load devices ahci, ata, siis and mvs as modules,
345 but option ATA_CAM should remain in kernel configuration to make ata
346 module work as CAM driver supporting legacy ATA controllers. Device ata
347 still can be used in modular fashion (atacore + ...). Modules atadisk
348 and atapi* are not used and won't affect operation in ATA_CAM mode.
349 Note that to use CAM-based ATA kernel should include CAM devices
350 scbus, pass, da (or explicitly ada), cd and optionally others. All of
351 them are parts of the cam module.
353 ataraid(4) functionality is now supported by the RAID GEOM class.
354 To use it you can load geom_raid kernel module and use graid(8) tool
355 for management. Instead of /dev/arX device names, use /dev/raid/rX.
357 No kernel config options or code have been removed, so if a problem
358 arises, please report it and optionally revert to the old ATA stack.
359 In order to do it you can remove from the kernel config:
364 , and instead add back:
365 device atadisk # ATA disk drives
366 device ataraid # ATA RAID drives
367 device atapicd # ATAPI CDROM drives
368 device atapifd # ATAPI floppy drives
369 device atapist # ATAPI tape drives
372 The default NFS server has been changed to the new server, which
373 was referred to as the experimental server. If you need to switch
374 back to the old NFS server, you must now put the "-o" option on
375 both the mountd and nfsd commands. This can be done using the
376 mountd_flags and nfs_server_flags rc.conf variables until an
377 update to the rc scripts is committed, which is coming soon.
380 The GNU Objective-C runtime library (libobjc), and other Objective-C
381 related components have been removed from the base system. If you
382 require an Objective-C library, please use one of the available ports.
385 ath(4) has been split into bus- and device- modules. if_ath contains
386 the HAL, the TX rate control and the network device code. if_ath_pci
387 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
388 contains the AHB glue. Users need to load both if_ath_pci and if_ath
389 in order to use ath on everything else.
391 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
392 need to load if_ath and if_ath_pci for ath(4) operation.
395 As part of the replacement of sysinstall, the process of building
396 release media has changed significantly. For details, please re-read
397 release(7), which has been updated to reflect the new build process.
400 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
401 is the last available version under GPLv2. It brings a number of new
402 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
403 4.1 and SSE 4.2), better support for powerpc64, a number of new
404 directives, and lots of other small improvements. See the ChangeLog
405 file in contrib/binutils for the full details.
408 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
409 compliant, and will now use half of hash for authentication.
410 This will break interoperability with all stacks (including all
411 actual FreeBSD versions) who implement
412 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
414 The only workaround with such peers is to use another HMAC
415 algorithm for IPsec ("phase 2") authentication.
418 Remove the uio_yield prototype and symbol. This function has
419 been misnamed since it was introduced and should not be
420 globally exposed with this name. The equivalent functionality
421 is now available using kern_yield(curthread->td_user_pri).
422 The function remains undocumented.
425 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
426 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
427 for scalar sysctls is defined but disabled. Code that needs
428 UQUAD to pass the type checking that must compile on older
429 systems where the define is not present can check against
430 __FreeBSD_version >= 900030.
432 The system dialog(1) has been replaced with a new version previously
433 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
434 with the previous version, but the libdialog associated with it has
435 a largely incompatible API. As such, the original version of libdialog
436 will be kept temporarily as libodialog, until its base system consumers
437 are replaced or updated. Bump __FreeBSD_version to 900030.
440 If you are trying to run make universe on a -stable system, and you get
441 the following warning:
442 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
443 unknown. config(8) likely too old."
444 or something similar to it, then you must upgrade your -stable system
445 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
446 stable/8) or build the config from the latest stable/8 branch and
447 install it on your system.
449 Prior to this date, building a current universe on 8-stable system from
450 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
451 error in the first kernel build phase. A new config on those old
452 systems will fix that problem for older versions of -current.
455 The TCP stack has been modified to allow Khelp modules to interact with
456 it via helper hook points and store per-connection data in the TCP
457 control block. Bump __FreeBSD_version to 900029. User space tools that
458 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
462 Generic IEEE 802.3 annex 31B full duplex flow control support has been
463 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
464 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
465 to take advantage of it instead of using custom implementations. This
466 means that these drivers now no longer unconditionally advertise
467 support for flow control but only do so if flow control is a selected
468 media option. This was implemented in the generic support that way in
469 order to allow flow control to be switched on and off via ifconfig(8)
470 with the PHY specific default to typically off in order to protect
471 from unwanted effects. Consequently, if you used flow control with
472 one of the above mentioned drivers you now need to explicitly enable
474 ifconfig bge0 media auto mediaopt flowcontrol
476 Along with the above mentioned changes generic support for setting
477 1000baseT master mode also has been added and brgphy(4), ciphy(4),
478 e1000phy(4) as well as ip1000phy(4) have been converted to take
479 advantage of it. This means that these drivers now no longer take the
480 link0 parameter for selecting master mode but the master media option
481 has to be used instead, for example like in the following:
482 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
484 Selection of master mode now is also available with all other PHY
485 drivers supporting 1000baseT.
488 The TCP stack has received a significant update to add support for
489 modularised congestion control and generally improve the clarity of
490 congestion control decisions. Bump __FreeBSD_version to 900025. User
491 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
492 sockstat) need to be recompiled.
495 The man(1) utility has been replaced by a new version that no longer
496 uses /etc/manpath.config. Please consult man.conf(5) for how to
497 migrate local entries to the new format.
500 The copyright strings printed by login(1) and sshd(8) at the time of a
501 new connection have been removed to follow other operating systems and
505 A workaround for a fixed ld bug has been removed in kernel code,
506 so make sure that your system ld is built from sources after
507 revision 210245 from 2010-07-19 (r211583 if building head kernel
508 on stable/8, r211584 for stable/7; both from 2010-08-21).
509 A symptom of incorrect ld version is different addresses for
510 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
513 The $ipv6_prefer variable in rc.conf(5) has been split into
514 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
516 The $ip6addrctl_policy is a variable to choose a pre-defined
517 address selection policy set by ip6addrctl(8). A value
518 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
521 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
522 flag (see an entry of 20090926) is set on an interface with no
523 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
524 security reason. If you want IPv6 link-local address on all
525 interfaces by default, set this to "YES".
527 The old ipv6_prefer="YES" is equivalent to
528 ipv6_activate_all_interfaces="YES" and
529 ip6addrctl_policy="ipv6_prefer".
532 DTrace has grown support for userland tracing. Due to this, DTrace is
533 now i386 and amd64 only.
534 dtruss(1) is now installed by default on those systems and a new
535 kernel module is needed for userland tracing: fasttrap.
536 No changes to your kernel config file are necessary to enable
537 userland tracing, but you might consider adding 'STRIP=' and
538 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
539 to have informative userland stack traces in DTrace (ustack).
542 The acpi_aiboost(4) driver has been removed in favor of the new
543 aibs(4) driver. You should update your kernel configuration file.
546 BSD grep has been imported to the base system and it is built by
547 default. It is completely BSD licensed, highly GNU-compatible, uses
548 less memory than its GNU counterpart and has a small codebase.
549 However, it is slower than its GNU counterpart, which is mostly
550 noticeable for larger searches, for smaller ones it is measurable
551 but not significant. The reason is complex, the most important factor
552 is that we lack a modern and efficient regex library and GNU
553 overcomes this by optimizing the searches internally. Future work
554 on improving the regex performance is planned, for the meantime,
555 users that need better performance, can build GNU grep instead by
556 setting the WITH_GNU_GREP knob.
559 Due to the import of powerpc64 support, all existing powerpc kernel
560 configuration files must be updated with a machine directive like this:
561 machine powerpc powerpc
563 In addition, an updated config(8) is required to build powerpc kernels
567 A new version of ZFS (version 15) has been merged to -HEAD.
568 This version uses a python library for the following subcommands:
569 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
570 For full functionality of these commands the following port must
571 be installed: sysutils/py-zfs
574 'vm_page's are now hashed by physical address to an array of mutexes.
575 Currently this is only used to serialize access to hold_count. Over
576 time the page queue mutex will be peeled away. This changes the size
577 of pmap on every architecture. And requires all callers of vm_page_hold
578 and vm_page_unhold to be updated.
581 WITH_CTF can now be specified in src.conf (not recommended, there
582 are some problems with static executables), make.conf (would also
583 affect ports which do not use GNU make and do not override the
584 compile targets) or in the kernel config (via "makeoptions
586 When WITH_CTF was specified there before this was silently ignored,
587 so make sure that WITH_CTF is not used in places which could lead
588 to unwanted behavior.
591 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
592 to allow 32-bit compatibility on non-x86 platforms. All kernel
593 configurations on amd64 and ia64 platforms using these options must
594 be modified accordingly.
597 The utmp user accounting database has been replaced with utmpx,
598 the user accounting interface standardized by POSIX.
599 Unfortunately the semantics of utmp and utmpx don't match,
600 making it practically impossible to support both interfaces.
601 The user accounting database is used by tools like finger(1),
602 last(1), talk(1), w(1) and ac(8).
604 All applications in the base system use utmpx. This means only
605 local binaries (e.g. from the ports tree) may still use these
606 utmp database files. These applications must be rebuilt to make
609 After the system has been upgraded, it is safe to remove the old
610 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
611 assuming their contents is of no importance anymore. Old wtmp
612 databases can only be used by last(1) and ac(8) after they have
613 been converted to the new format using wtmpcvt(1).
616 Introduce the kernel thread "deadlock resolver" (which can be enabled
617 via the DEADLKRES option, see NOTES for more details) and the
618 sleepq_type() function for sleepqueues.
621 The rc.firewall and rc.firewall6 were unified, and
622 rc.firewall6 and rc.d/ip6fw were removed.
623 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
624 variables are obsoleted. Instead, the following new rc
625 variables are added to rc.d/ipfw:
627 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
628 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
629 firewall_simple_onet_ipv6, firewall_trusted_ipv6
631 The meanings correspond to the relevant IPv4 variables.
637 The default terminal emulation for syscons(4) has been changed
638 from cons25 to xterm on all platforms except pc98. This means
639 that the /etc/ttys file needs to be updated to ensure correct
640 operation of applications on the console.
642 The terminal emulation style can be toggled per window by using
643 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
644 options can be used to change the compile-time default back to
647 To prevent graphical artifacts, make sure the TERM environment
648 variable is set to match the terminal emulation that is being
649 performed by syscons(4).
652 The layout of the structure ieee80211req_scan_result has changed.
653 Applications that require wireless scan results (e.g. ifconfig(8))
654 from net80211 need to be recompiled.
656 Applications such as wpa_supplicant(8) may require a full world
657 build without using NO_CLEAN in order to get synchronized with the
661 The iwn(4) driver has been updated to support the 5000 and 5150 series.
662 There's one kernel module for each firmware. Adding "device iwnfw"
663 to the kernel configuration file means including all three firmware
664 images inside the kernel. If you want to include just the one for
665 your wireless card, use the devices iwn4965fw, iwn5000fw or
669 The rc.d/network_ipv6, IPv6 configuration script has been integrated
670 into rc.d/netif. The changes are the following:
672 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
673 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
674 Note that both variables need the "inet6" keyword at the head.
676 Do not set $ipv6_network_interfaces manually if you do not
677 understand what you are doing. It is not needed in most cases.
679 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
682 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
683 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
685 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
686 all configured interfaces have "inet6 accept_rtadv" in the
687 $ifconfig_IF_ipv6. These are for backward compatibility.
689 3. A new variable $ipv6_prefer has been added. If NO, IPv6
690 functionality of interfaces with no corresponding
691 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
692 and the default address selection policy of ip6addrctl(8)
693 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
694 Note that if you want to configure IPv6 functionality on the
695 disabled interfaces after boot, first you need to clear the flag by
696 using ifconfig(8) like:
698 ifconfig em0 inet6 -ifdisabled
700 If YES, the default address selection policy is set as
703 The default value of $ipv6_prefer is NO.
705 4. If your system need to receive Router Advertisement messages,
706 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
707 scripts automatically invoke rtsol(8) when the interface becomes
708 UP. The Router Advertisement messages are used for SLAAC
709 (State-Less Address AutoConfiguration).
712 802.11s D3.03 support was committed. This is incompatible with the
713 previous code, which was based on D3.0.
716 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
717 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
718 control whether accepting Router Advertisement messages or not.
719 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
720 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
721 The ifconfig(8) utility now supports these flags.
724 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
725 mount(8) and -a option for df(1) to see them.
728 The old tunable hw.bus.devctl_disable has been superseded by
729 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
730 replaced by hw.bus.devctl_queue=0. The default for this new tunable
734 Remove the option STOP_NMI. The default action is now to use NMI only
735 for KDB via the newly introduced function stop_cpus_hard() and
736 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
739 The stable/8 branch created in subversion. This corresponds to the
740 RELENG_8 branch in CVS.
743 Bump the shared library version numbers for all libraries that do not
744 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
745 __FreeBSD_version to 800105.
748 Due to changes in the implementation of virtual network stack support,
749 all network-related kernel modules must be recompiled. As this change
750 breaks the ABI, bump __FreeBSD_version to 800104.
753 The TOE interface to the TCP syncache has been modified to remove
754 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
755 The cxgb driver is the only TOE consumer affected by this change, and
756 needs to be recompiled along with the kernel. As this change breaks
757 the ABI, bump __FreeBSD_version to 800103.
760 Padding has been added to struct tcpcb, sackhint and tcpstat in
761 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
762 maintaining the ABI. However, this change breaks the ABI, so bump
763 __FreeBSD_version to 800102. User space tools that rely on the size of
764 any of these structs (e.g. sockstat) need to be recompiled.
767 The NFS_LEGACYRPC option has been removed along with the old kernel
768 RPC implementation that this option selected. Kernel configurations
769 may need to be adjusted.
772 The network interface device nodes at /dev/net/<interface> have been
773 removed. All ioctl operations can be performed the normal way using
774 routing sockets. The kqueue functionality can generally be replaced
775 with routing sockets.
778 The documentation from the FreeBSD Documentation Project (Handbook,
779 FAQ, etc.) is now installed via packages by sysinstall(8) and under
780 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
783 The ABI of various structures related to the SYSV IPC API have been
784 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
785 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
789 Layout of struct vnet has changed as routing related variables were
790 moved to their own Vimage module. Modules need to be recompiled. Bump
791 __FreeBSD_version to 800099.
794 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
795 respectively. As long as no more than 16 groups per process are used,
796 no changes should be visible. When more than 16 groups are used, old
797 binaries may fail if they call getgroups() or getgrouplist() with
798 statically sized storage. Recompiling will work around this, but
799 applications should be modified to use dynamically allocated storage
800 for group arrays as POSIX.1-2008 does not cap an implementation's
801 number of supported groups at NGROUPS_MAX+1 as previous versions did.
803 NFS and portalfs mounts may also be affected as the list of groups is
804 truncated to 16. Users of NFS who use more than 16 groups, should
805 take care that negative group permissions are not used on the exported
806 file systems as they will not be reliable unless a GSSAPI based
807 authentication method is used.
810 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
811 option compiles in the support for adaptive spinning for lockmgrs
812 which want to enable it. The lockinit() function now accepts the flag
813 LK_ADAPTIVE in order to make the lock object subject to adaptive
814 spinning when both held in write and read mode.
817 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
818 changed. User applications that use this ioctl need to be rebuilt.
821 The layout of struct thread has changed. Kernel and modules need to
825 The layout of structs ifnet, domain, protosw and vnet_net has changed.
826 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
829 window(1) has been removed from the base system. It can now be
830 installed from ports. The port is called misc/window.
833 The way we are storing and accessing `routing table' entries has
834 changed. Programs reading the FIB, like netstat, need to be
838 A new netisr implementation has been added for FreeBSD 8. Network
839 file system modules, such as igmp, ipdivert, and others, should be
841 Bump __FreeBSD_version to 800096.
844 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
848 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
849 Bump __FreeBSD_version to 800094.
852 Add mnt_xflag field to 'struct mount'. File system modules need to be
854 Bump __FreeBSD_version to 800093.
857 The compiling option ADAPTIVE_SX has been retired while it has been
858 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
859 The KPI for sx_init_flags() changes as accepting flags:
860 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
861 been introduced in order to handle the reversed logic.
862 Bump __FreeBSD_version to 800092.
865 Add support for hierarchical jails. Remove global securelevel.
866 Bump __FreeBSD_version to 800091.
869 The layout of struct vnet_net has changed, therefore modules
871 Bump __FreeBSD_version to 800090.
874 The newly imported zic(8) produces a new format in the output. Please
875 run tzsetup(8) to install the newly created data to /etc/localtime.
878 The sysctl tree for the usb stack has renamed from hw.usb2.* to
879 hw.usb.* and is now consistent again with previous releases.
882 802.11 monitor mode support was revised and driver api's were changed.
883 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
884 of DLT_IEEE802_11. No user-visible data structures were changed but
885 applications that use DLT_IEEE802_11 may require changes.
886 Bump __FreeBSD_version to 800088.
889 The layout of the following structs has changed: sysctl_oid,
890 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
891 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
892 panics may be experienced. World rebuild is required for
893 correctly checking networking state from userland.
894 Bump __FreeBSD_version to 800085.
897 MLDv2 and Source-Specific Multicast (SSM) have been merged
898 to the IPv6 stack. VIMAGE hooks are in but not yet used.
899 The implementation of SSM within FreeBSD's IPv6 stack closely
900 follows the IPv4 implementation.
902 For kernel developers:
904 * The most important changes are that the ip6_output() and
905 ip6_input() paths no longer take the IN6_MULTI_LOCK,
906 and this lock has been downgraded to a non-recursive mutex.
908 * As with the changes to the IPv4 stack to support SSM, filtering
909 of inbound multicast traffic must now be performed by transport
910 protocols within the IPv6 stack. This does not apply to TCP and
911 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
913 * The KPIs used by IPv6 multicast are similar to those used by
914 the IPv4 stack, with the following differences:
915 * im6o_mc_filter() is analogous to imo_multicast_filter().
916 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
917 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
918 * IN6_LOOKUP_MULTI() has been deprecated and removed.
919 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
920 for MLDv1 have an additional 'timer' argument which is used to
921 jitter the initial membership report for the solicited-node
922 multicast membership on-link.
923 * This is not strictly needed for MLDv2, which already jitters
924 its report transmissions. However, the 'timer' argument is
925 preserved in case MLDv1 is active on the interface.
927 * The KAME linked-list based IPv6 membership implementation has
928 been refactored to use a vector similar to that used by the IPv4
930 Code which maintains a list of its own multicast memberships
931 internally, e.g. carp, has been updated to reflect the new
934 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
935 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
936 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
937 implementation constraint which needs to be addressed in HEAD.
939 For application developers:
941 * The changes are broadly similar to those made for the IPv4
944 * The use of IPv4 and IPv6 multicast socket options on the same
945 socket, using mapped addresses, HAS NOT been tested or supported.
947 * There are a number of issues with the implementation of various
948 IPv6 multicast APIs which need to be resolved in the API surface
949 before the implementation is fully compatible with KAME userland
950 use, and these are mostly to do with interface index treatment.
952 * The literature available discusses the use of either the delta / ASM
953 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
954 using setsourcefilter(3)/getsourcefilter(3). For more information
955 please refer to RFC 3768, 'Socket Interface Extensions for
956 Multicast Source Filters'.
958 * Applications which use the published RFC 3678 APIs should be fine.
960 For systems administrators:
962 * The mtest(8) utility has been refactored to support IPv6, in
963 addition to IPv4. Interface addresses are no longer accepted
964 as arguments, their names must be used instead. The utility
965 will map the interface name to its first IPv4 address as
966 returned by getifaddrs(3).
968 * The ifmcstat(8) utility has also been updated to print the MLDv2
969 endpoint state and source filter lists via sysctl(3).
971 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
972 loopback of IPv6 multicast datagrams by default; it defaults to 1
973 to preserve the existing behaviour. Disabling multicast loopback is
974 recommended for optimal system performance.
976 * The IPv6 MROUTING code has been changed to examine this sysctl
977 instead of attempting to perform a group lookup before looping
978 back forwarded datagrams.
980 Bump __FreeBSD_version to 800084.
983 Implement low-level Bluetooth HCI API.
984 Bump __FreeBSD_version to 800083.
987 The layout of struct malloc_type, used by modules to register new
988 memory allocation types, has changed. Most modules will need to
989 be rebuilt or panics may be experienced.
990 Bump __FreeBSD_version to 800081.
993 Anticipate overflowing inp_flags - add inp_flags2.
994 This changes most offsets in inpcb, so checking v4 connection
995 state will require a world rebuild.
996 Bump __FreeBSD_version to 800080.
999 Add an llentry to struct route and struct route_in6. Modules
1000 embedding a struct route will need to be recompiled.
1001 Bump __FreeBSD_version to 800079.
1004 The size of rt_metrics_lite and by extension rtentry has changed.
1005 Networking administration apps will need to be recompiled.
1006 The route command now supports show as an alias for get, weighting
1007 of routes, sticky and nostick flags to alter the behavior of stateful
1009 Bump __FreeBSD_version to 800078.
1012 Do not use Giant for kbdmux(4) locking. This is wrong and
1013 apparently causing more problems than it solves. This will
1014 re-open the issue where interrupt handlers may race with
1015 kbdmux(4) in polling mode. Typical symptoms include (but
1016 not limited to) duplicated and/or missing characters when
1017 low level console functions (such as gets) are used while
1018 interrupts are enabled (for example geli password prompt,
1019 mountroot prompt etc.). Disabling kbdmux(4) may help.
1022 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1023 kernel modules referencing any of the above need to be recompiled.
1024 Bump __FreeBSD_version to 800075.
1027 GEOM_PART has become the default partition slicer for storage devices,
1028 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1029 introduces some changes:
1031 MSDOS/EBR: the devices created from MSDOS extended partition entries
1032 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1033 to devices with offset-based names. fstabs may need to be modified.
1035 BSD: the "geometry does not match label" warning is harmless in most
1036 cases but it points to problems in file system misalignment with
1037 disk geometry. The "c" partition is now implicit, covers the whole
1038 top-level drive and cannot be (mis)used by users.
1040 General: Kernel dumps are now not allowed to be written to devices
1041 whose partition types indicate they are meant to be used for file
1042 systems (or, in case of MSDOS partitions, as something else than
1045 Most of these changes date approximately from 200812.
1048 The uscanner(4) driver has been removed from the kernel. This follows
1049 Linux removing theirs in 2.6 and making libusb the default interface
1050 (supported by sane).
1053 The multicast forwarding code has been cleaned up. netstat(1)
1054 only relies on KVM now for printing bandwidth upcall meters.
1055 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1056 ip6_mroute_mod respectively. The config(5) options for statically
1057 compiling this code remain the same, i.e. 'options MROUTING'.
1060 Support for the IFF_NEEDSGIANT network interface flag has been
1061 removed, which means that non-MPSAFE network device drivers are no
1062 longer supported. In particular, if_ar, if_sr, and network device
1063 drivers from the old (legacy) USB stack can no longer be built or
1067 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1068 a bunch of new language catalog files have also been added.
1069 This means that some common libc messages are now localized and
1070 they depend on the LC_MESSAGES environmental variable.
1073 The k8temp(4) driver has been renamed to amdtemp(4) since
1074 support for Family 10 and Family 11 CPU families was added.
1077 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1078 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1080 For kernel developers, the most important changes are that the
1081 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1082 and this lock has been downgraded to a non-recursive mutex.
1084 Transport protocols (UDP, Raw IP) are now responsible for filtering
1085 inbound multicast traffic according to group membership and source
1086 filters. The imo_multicast_filter() KPI exists for this purpose.
1087 Transports which do not use multicast (SCTP, TCP) already reject
1088 multicast by default. Forwarding and receive performance may improve
1089 as a mutex acquisition is no longer needed in the ip_input()
1090 low-level input path. in_addmulti() and in_delmulti() are shimmed
1091 to new KPIs which exist to support SSM in-kernel.
1093 For application developers, it is recommended that loopback of
1094 multicast datagrams be disabled for best performance, as this
1095 will still cause the lock to be taken for each looped-back
1096 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1097 be tuned to 0 to disable loopback by default; it defaults to 1
1098 to preserve the existing behaviour.
1100 For systems administrators, to obtain best performance with
1101 multicast reception and multiple groups, it is always recommended
1102 that a card with a suitably precise hash filter is used. Hash
1103 collisions will still result in the lock being taken within the
1104 transport protocol input path to check group membership.
1106 If deploying FreeBSD in an environment with IGMP snooping switches,
1107 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1108 enabled; this forces 224.0.0.0/24 group membership to be announced
1111 The size of 'struct igmpstat' has changed; netstat needs to be
1112 recompiled to reflect this.
1113 Bump __FreeBSD_version to 800070.
1116 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1117 updated to use it. This requires a buildworld/installworld in order to
1118 update the library and dependencies (usbconfig, etc). Its advisable to
1119 rebuild all ports which uses libusb. More specific directions are given
1120 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1121 libusb are no longer required and can be removed.
1124 A workaround is committed to allow the creation of System V shared
1125 memory segment of size > 2 GB on the 64-bit architectures.
1126 Due to a limitation of the existing ABI, the shm_segsz member
1127 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1128 wrong for large segments. Note that limits must be explicitly
1129 raised to allow such segments to be created.
1132 The layout of struct ifnet has changed, requiring a rebuild of all
1133 network device driver modules.
1136 The /dev handling for the new USB stack has changed, a
1137 buildworld/installworld is required for libusb20.
1140 The new USB2 stack has now been permanently moved in and all kernel and
1141 module names reverted to their previous values (eg, usb, ehci, ohci,
1142 ums, ...). The old usb stack can be compiled in by prefixing the name
1143 with the letter 'o', the old usb modules have been removed.
1144 Updating entry 20090216 for xorg and 20090215 for libmap may still
1148 The rc.conf(5) option if_up_delay has been renamed to
1149 defaultroute_delay to better reflect its purpose. If you have
1150 customized this setting in /etc/rc.conf you need to update it to
1154 xorg 7.4 wants to configure its input devices via hald which does not
1155 yet work with USB2. If the keyboard/mouse does not work in xorg then
1157 Option "AllowEmptyInput" "off"
1158 to your ServerLayout section. This will cause X to use the configured
1159 kbd and mouse sections from your xorg.conf.
1162 The GENERIC kernels for all architectures now default to the new USB2
1163 stack. No kernel config options or code have been removed so if a
1164 problem arises please report it and optionally revert to the old USB
1165 stack. If you are loading USB kernel modules or have a custom kernel
1166 that includes GENERIC then ensure that usb names are also changed over,
1167 eg uftdi -> usb2_serial_ftdi.
1169 Older programs linked against the ports libusb 0.1 need to be
1170 redirected to the new stack's libusb20. /etc/libmap.conf can
1172 # Map old usb library to new one for usb2 stack
1173 libusb-0.1.so.8 libusb20.so.1
1176 All USB ethernet devices now attach as interfaces under the name ueN
1177 (eg. ue0). This is to provide a predictable name as vendors often
1178 change usb chipsets in a product without notice.
1181 The ichsmb(4) driver has been changed to require SMBus slave
1182 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1183 All of the other SMBus controller drivers require left-justified
1184 slave addresses, so this change makes all the drivers provide the
1188 INET6 statistics (struct ip6stat) was updated.
1189 netstat(1) needs to be recompiled.
1192 NTFS has been removed from GENERIC kernel on amd64 to match
1193 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1194 will load ntfs.ko module automatically when NTFS support is
1195 actually needed, unless ntfs.ko is not installed or security
1196 level prohibits loading kernel modules. If either is the case,
1197 "options NTFS" has to be added into kernel config.
1200 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1201 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1202 800061. User space tools that rely on the size of struct tcpcb in
1203 tcp_var.h (e.g. sockstat) need to be recompiled.
1206 ng_tty(4) module updated to match the new TTY subsystem.
1207 Due to API change, user-level applications must be updated.
1208 New API support added to mpd5 CVS and expected to be present
1209 in next mpd5.3 release.
1212 With __FreeBSD_version 800060 the makefs tool is part of
1213 the base system (it was a port).
1216 The afdata and ifnet locks have been changed from mutexes to
1217 rwlocks, network modules will need to be re-compiled.
1220 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1221 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1222 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1223 architecture and 40 bytes on 64-bit architecture. The userland
1224 applications "arp" and "ndp" have been updated accordingly.
1225 The output from "netstat -r" shows only routing entries and
1226 none of the L2 information.
1229 __FreeBSD_version 800057 marks the switchover from the
1230 binary ath hal to source code. Users must add the line:
1232 options AH_SUPPORT_AR5416
1234 to their kernel config files when specifying:
1238 The ath_hal module no longer exists; the code is now compiled
1239 together with the driver in the ath module. It is now
1240 possible to tailor chip support (i.e. reduce the set of chips
1241 and thereby the code size); consult ath_hal(4) for details.
1244 __FreeBSD_version 800054 adds memory barriers to
1245 <machine/atomic.h>, new interfaces to ifnet to facilitate
1246 multiple hardware transmit queues for cards that support
1247 them, and a lock-less ring-buffer implementation to
1248 enable drivers to more efficiently manage queueing of
1252 A new version of ZFS (version 13) has been merged to -HEAD.
1253 This version has zpool attribute "listsnapshots" off by
1254 default, which means "zfs list" does not show snapshots,
1255 and is the same as Solaris behavior.
1258 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1261 The uhci, ohci, ehci and slhci USB Host controller drivers have
1262 been put into separate modules. If you load the usb module
1263 separately through loader.conf you will need to load the
1264 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1265 controller add the following to loader.conf:
1271 The ABI used by the PMC toolset has changed. Please keep
1272 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1276 atapci kernel module now includes only generic PCI ATA
1277 driver. AHCI driver moved to ataahci kernel module.
1278 All vendor-specific code moved into separate kernel modules:
1279 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1280 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1281 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1282 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1285 The TTY subsystem of the kernel has been replaced by a new
1286 implementation, which provides better scalability and an
1287 improved driver model. Most common drivers have been migrated to
1288 the new TTY subsystem, while others have not. The following
1289 drivers have not yet been ported to the new TTY layer:
1292 cy, digi, rc, rp, sio
1298 ng_h4, ng_tty, ppp, sl, snp
1300 Adding these drivers to your kernel configuration file shall
1301 cause compilation to fail.
1304 ntpd has been upgraded to 4.2.4p5.
1307 OpenSSH has been upgraded to 5.1p1.
1309 For many years, FreeBSD's version of OpenSSH preferred DSA
1310 over RSA for host and user authentication keys. With this
1311 upgrade, we've switched to the vendor's default of RSA over
1312 DSA. This may cause upgraded clients to warn about unknown
1313 host keys even for previously known hosts. Users should
1314 follow the usual procedure for verifying host keys before
1315 accepting the RSA key.
1317 This can be circumvented by setting the "HostKeyAlgorithms"
1318 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1321 Please note that the sequence of keys offered for
1322 authentication has been changed as well. You may want to
1323 specify IdentityFile in a different order to revert this
1327 The sio(4) driver has been removed from the i386 and amd64
1328 kernel configuration files. This means uart(4) is now the
1329 default serial port driver on those platforms as well.
1331 To prevent collisions with the sio(4) driver, the uart(4) driver
1332 uses different names for its device nodes. This means the
1333 onboard serial port will now most likely be called "ttyu0"
1334 instead of "ttyd0". You may need to reconfigure applications to
1335 use the new device names.
1337 When using the serial port as a boot console, be sure to update
1338 /boot/device.hints and /etc/ttys before booting the new kernel.
1339 If you forget to do so, you can still manually specify the hints
1340 at the loader prompt:
1342 set hint.uart.0.at="isa"
1343 set hint.uart.0.port="0x3F8"
1344 set hint.uart.0.flags="0x10"
1345 set hint.uart.0.irq="4"
1349 The gpt(8) utility has been removed. Use gpart(8) to partition
1353 The version that Linuxulator emulates was changed from 2.4.2
1354 to 2.6.16. If you experience any problems with Linux binaries
1355 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1356 if it fixes the problem contact emulation mailing list.
1359 ISDN4BSD (I4B) was removed from the src tree. You may need to
1360 update a your kernel configuration and remove relevant entries.
1363 I have checked in code to support multiple routing tables.
1364 See the man pages setfib(1) and setfib(2).
1365 This is a hopefully backwards compatible version,
1366 but to make use of it you need to compile your kernel
1367 with options ROUTETABLES=2 (or more up to 16).
1370 The 802.11 wireless support was redone to enable multi-bss
1371 operation on devices that are capable. The underlying device
1372 is no longer used directly but instead wlanX devices are
1373 cloned with ifconfig. This requires changes to rc.conf files.
1374 For example, change:
1375 ifconfig_ath0="WPA DHCP"
1378 ifconfig_wlan0="WPA DHCP"
1379 see rc.conf(5) for more details. In addition, mergemaster of
1380 /etc/rc.d is highly recommended. Simultaneous update of userland
1381 and kernel wouldn't hurt either.
1383 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1384 modules were merged into the base wlan module. All references
1385 to these modules (e.g. in kernel config files) must be removed.
1388 psm(4) has gained write(2) support in native operation level.
1389 Arbitrary commands can be written to /dev/psm%d and status can
1390 be read back from it. Therefore, an application is responsible
1391 for status validation and error recovery. It is a no-op in
1392 other operation levels.
1395 Support for KSE threading has been removed from the kernel. To
1396 run legacy applications linked against KSE libmap.conf may
1397 be used. The following libmap.conf may be used to ensure
1398 compatibility with any prior release:
1400 libpthread.so.1 libthr.so.1
1401 libpthread.so.2 libthr.so.2
1402 libkse.so.3 libthr.so.3
1405 The layout of struct vmspace has changed. This affects libkvm
1406 and any executables that link against libkvm and use the
1407 kvm_getprocs() function. In particular, but not exclusively,
1408 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1409 The effects are minimal, but it's advisable to upgrade world
1413 The latest em driver no longer has support in it for the
1414 82575 adapter, this is now moved to the igb driver. The
1415 split was done to make new features that are incompatible
1416 with older hardware easier to do.
1419 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1420 likewise the kernel option is now GEOM_LINUX_LVM.
1423 The default NFS mount mode has changed from UDP to TCP for
1424 increased reliability. If you rely on (insecurely) NFS
1425 mounting across a firewall you may need to update your
1429 Belatedly note the addition of m_collapse for compacting
1433 The fts(3) structures have been changed to use adequate
1434 integer types for their members and so to be able to cope
1435 with huge file trees. The old fts(3) ABI is preserved
1436 through symbol versioning in libc, so third-party binaries
1437 using fts(3) should still work, although they will not take
1438 advantage of the extended types. At the same time, some
1439 third-party software might fail to build after this change
1440 due to unportable assumptions made in its source code about
1441 fts(3) structure members. Such software should be fixed
1442 by its vendor or, in the worst case, in the ports tree.
1443 FreeBSD_version 800015 marks this change for the unlikely
1444 case that a portable fix is impossible.
1447 To upgrade to -current after this date, you must be running
1448 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1449 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1452 The ADAPTIVE_GIANT kernel option has been retired because its
1453 functionality is the default now.
1456 The AT keyboard emulation of sunkbd(4) has been turned on
1457 by default. In order to make the special symbols of the Sun
1458 keyboards driven by sunkbd(4) work under X these now have
1459 to be configured the same way as Sun USB keyboards driven
1460 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1462 Option "XkbLayout" "us"
1463 Option "XkbRules" "xorg"
1464 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1467 It has been decided that it is desirable to provide ABI
1468 backwards compatibility to the FreeBSD 4/5/6 versions of the
1469 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1470 broken with the introduction of PCI domain support (see the
1471 20070930 entry). Unfortunately, this required the ABI of
1472 PCIOCGETCONF to be broken again in order to be able to
1473 provide backwards compatibility to the old version of that
1474 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1475 again. As for prominent ports this affects neither pciutils
1476 nor xorg-server this time, the hal port needs to be rebuilt
1480 The misnamed kthread_create() and friends have been renamed
1481 to kproc_create() etc. Many of the callers already
1482 used kproc_start()..
1483 I will return kthread_create() and friends in a while
1484 with implementations that actually create threads, not procs.
1485 Renaming corresponds with version 800002.
1494 Avoid using make -j when upgrading. While generally safe, there are
1495 sometimes problems using -j to upgrade. If your upgrade fails with
1496 -j, please try again without -j. From time to time in the past there
1497 have been problems using -j with buildworld and/or installworld. This
1498 is especially true when upgrading between "distant" versions (eg one
1499 that cross a major release boundary or several minor releases, or when
1500 several months have passed on the -current branch).
1502 Sometimes, obscure build problems are the result of environment
1503 poisoning. This can happen because the make utility reads its
1504 environment when searching for values for global variables. To run
1505 your build attempts in an "environmental clean room", prefix all make
1506 commands with 'env -i '. See the env(1) manual page for more details.
1508 When upgrading from one major version to another it is generally best
1509 to upgrade to the latest code in the currently installed branch first,
1510 then do an upgrade to the new branch. This is the best-tested upgrade
1511 path, and has the highest probability of being successful. Please try
1512 this approach before reporting problems with a major version upgrade.
1516 When upgrading the boot ZFS pool to a new version, always follow
1519 1.) recompile and reinstall the ZFS boot loader and boot block
1520 (this is part of "make buildworld" and "make installworld")
1522 2.) update the ZFS boot block on your boot drive
1524 The following example updates the ZFS boot block on the first
1525 partition (freebsd-boot) of a GPT partitioned drive ad0:
1526 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1528 Non-boot pools do not need these updates.
1532 If you are updating from a prior version of FreeBSD (even one just
1533 a few days old), you should follow this procedure. It is the most
1534 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1536 make kernel-toolchain
1537 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1538 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1540 To test a kernel once
1541 ---------------------
1542 If you just want to boot a kernel once (because you are not sure
1543 if it works, or if you want to boot a known bad kernel to provide
1544 debugging information) run
1545 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1546 nextboot -k testkernel
1548 To just build a kernel when you know that it won't mess you up
1549 --------------------------------------------------------------
1550 This assumes you are already running a CURRENT system. Replace
1551 ${arch} with the architecture of your machine (e.g. "i386",
1552 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1554 cd src/sys/${arch}/conf
1555 config KERNEL_NAME_HERE
1556 cd ../compile/KERNEL_NAME_HERE
1561 If this fails, go to the "To build a kernel" section.
1563 To rebuild everything and install it on the current system.
1564 -----------------------------------------------------------
1565 # Note: sometimes if you are running current you gotta do more than
1566 # is listed here if you are upgrading from a really old current.
1568 <make sure you have good level 0 dumps>
1570 make kernel KERNCONF=YOUR_KERNEL_HERE
1572 <reboot in single user> [3]
1580 To cross-install current onto a separate partition
1581 --------------------------------------------------
1582 # In this approach we use a separate partition to hold
1583 # current's root, 'usr', and 'var' directories. A partition
1584 # holding "/", "/usr" and "/var" should be about 2GB in
1587 <make sure you have good level 0 dumps>
1590 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1591 <maybe newfs current's root partition>
1592 <mount current's root partition on directory ${CURRENT_ROOT}>
1593 make installworld DESTDIR=${CURRENT_ROOT}
1594 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1595 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1596 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1597 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1598 <reboot into current>
1599 <do a "native" rebuild/install as described in the previous section>
1600 <maybe install compatibility libraries from ports/misc/compat*>
1604 To upgrade in-place from stable to current
1605 ----------------------------------------------
1606 <make sure you have good level 0 dumps>
1608 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1610 <reboot in single user> [3]
1617 Make sure that you've read the UPDATING file to understand the
1618 tweaks to various things you need. At this point in the life
1619 cycle of current, things change often and you are on your own
1620 to cope. The defaults can also change, so please read ALL of
1621 the UPDATING entries.
1623 Also, if you are tracking -current, you must be subscribed to
1624 freebsd-current@freebsd.org. Make sure that before you update
1625 your sources that you have read and understood all the recent
1626 messages there. If in doubt, please track -stable which has
1627 much fewer pitfalls.
1629 [1] If you have third party modules, such as vmware, you
1630 should disable them at this point so they don't crash your
1633 [3] From the bootblocks, boot -s, and then do
1638 adjkerntz -i # if CMOS is wall time
1639 Also, when doing a major release upgrade, it is required that
1640 you boot into single user mode to do the installworld.
1642 [4] Note: This step is non-optional. Failure to do this step
1643 can result in a significant reduction in the functionality of the
1644 system. Attempting to do it by hand is not recommended and those
1645 that pursue this avenue should read this file carefully, as well
1646 as the archives of freebsd-current and freebsd-hackers mailing lists
1647 for potential gotchas. The -U option is also useful to consider.
1648 See mergemaster(8) for more information.
1650 [5] Usually this step is a noop. However, from time to time
1651 you may need to do this if you get unknown user in the following
1652 step. It never hurts to do it all the time. You may need to
1653 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1654 install) after the buildworld before this step if you last updated
1655 from current before 20020224 or from -stable before 20020408.
1657 [6] This only deletes old files and directories. Old libraries
1658 can be deleted by "make delete-old-libs", but you have to make
1659 sure that no program is using those libraries anymore.
1661 [8] In order to have a kernel that can run the 4.x binaries needed to
1662 do an installworld, you must include the COMPAT_FREEBSD4 option in
1663 your kernel. Failure to do so may leave you with a system that is
1664 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1665 required to run the 5.x binaries on more recent kernels. And so on
1666 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1668 Make sure that you merge any new devices from GENERIC since the
1669 last time you updated your kernel config file.
1671 [9] When checking out sources, you must include the -P flag to have
1672 cvs prune empty directories.
1674 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1675 "?=" instead of the "=" assignment operator, so that buildworld can
1676 override the CPUTYPE if it needs to.
1678 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1679 not on the command line, or in /etc/make.conf. buildworld will
1680 warn if it is improperly defined.
1683 This file contains a list, in reverse chronological order, of major
1684 breakages in tracking -current. It is not guaranteed to be a complete
1685 list of such breakages, and only contains entries since October 10, 2007.
1686 If you need to see UPDATING entries from before that date, you will need
1687 to fetch an UPDATING file from an older FreeBSD release.
1689 Copyright information:
1691 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1693 Redistribution, publication, translation and use, with or without
1694 modification, in full or in part, in any form or format of this
1695 document are permitted without further permission from the author.
1697 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1698 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1699 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1700 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1701 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1702 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1703 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1704 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1705 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1706 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1707 POSSIBILITY OF SUCH DAMAGE.
1709 Contact Warner Losh if you have any questions about your use of