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