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 9.x IS SLOW:
13 FreeBSD 9.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 disable malloc debugging, run
23 ln -s aj /etc/malloc.conf.)
26 The acpi_aiboost(4) driver has been removed in favor of the new
27 aibs(4) driver. You should update your kernel configuration file.
30 BSD grep has been imported to the base system and it is built by
31 default. It is completely BSD licensed, highly GNU-compatible, uses
32 less memory than its GNU counterpart and has a small codebase.
33 However, it is slower than its GNU counterpart, which is mostly
34 noticeable for larger searches, for smaller ones it is measurable
35 but not significant. The reason is complex, the most important factor
36 is that we lack a modern and efficient regex library and GNU
37 overcomes this by optimizing the searches internally. Future work
38 on improving the regex performance is planned, for the meantime,
39 users that need better performance, can build GNU grep instead by
40 setting the WITH_GNU_GREP knob.
43 Due to the import of powerpc64 support, all existing powerpc kernel
44 configuration files must be updated with a machine directive like this:
45 machine powerpc powerpc
47 In addition, an updated config(8) is required to build powerpc kernels
51 A new version of ZFS (version 15) has been merged to -HEAD.
52 This version uses a python library for the following subcommands:
53 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
54 For full functionality of these commands the following port must
55 be installed: sysutils/py-zfs
58 'vm_page's are now hashed by physical address to an array of mutexes.
59 Currently this is only used to serialize access to hold_count. Over
60 time the page queue mutex will be peeled away. This changes the size
61 of pmap on every architecture. And requires all callers of vm_page_hold
62 and vm_page_unhold to be updated.
65 WITH_CTF can now be specified in src.conf (not recommended, there
66 are some problems with static executables), make.conf (would also
67 affect ports which do not use GNU make and do not override the
68 compile targets) or in the kernel config (via "makeoptions
70 When WITH_CTF was specified there before this was silently ignored,
71 so make sure that WITH_CTF is not used in places which could lead
75 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
76 to allow 32-bit compatibility on non-x86 platforms. All kernel
77 configurations on amd64 and ia64 platforms using these options must
78 be modified accordingly.
81 The utmp user accounting database has been replaced with utmpx,
82 the user accounting interface standardized by POSIX.
83 Unfortunately the semantics of utmp and utmpx don't match,
84 making it practically impossible to support both interfaces.
85 The user accounting database is used by tools like finger(1),
86 last(1), talk(1), w(1) and ac(8).
88 All applications in the base system use utmpx. This means only
89 local binaries (e.g. from the ports tree) may still use these
90 utmp database files. These applications must be rebuilt to make
93 After the system has been upgraded, it is safe to remove the old
94 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
95 assuming their contents is of no importance anymore. Old wtmp
96 databases can only be used by last(1) and ac(8) after they have
97 been converted to the new format using wtmpcvt(1).
100 Introduce the kernel thread "deadlock resolver" (which can be enabled
101 via the DEADLKRES option, see NOTES for more details) and the
102 sleepq_type() function for sleepqueues.
105 The rc.firewall and rc.firewall6 were unified, and
106 rc.firewall6 and rc.d/ip6fw were removed.
107 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
108 variables are obsoleted. Instead, the following new rc
109 variables are added to rc.d/ipfw:
111 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
112 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
113 firewall_simple_onet_ipv6, firewall_trusted_ipv6
115 The meanings correspond to the relevant IPv4 variables.
121 The default terminal emulation for syscons(4) has been changed
122 from cons25 to xterm on all platforms except pc98. This means
123 that the /etc/ttys file needs to be updated to ensure correct
124 operation of applications on the console.
126 The terminal emulation style can be toggled per window by using
127 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
128 options can be used to change the compile-time default back to
131 To prevent graphical artifacts, make sure the TERM environment
132 variable is set to match the terminal emulation that is being
133 performed by syscons(4).
136 The layout of the structure ieee80211req_scan_result has changed.
137 Applications that require wireless scan results (e.g. ifconfig(8))
138 from net80211 need to be recompiled.
140 Applications such as wpa_supplicant(8) may require a full world
141 build without using NO_CLEAN in order to get synchronized with the
145 The iwn(4) driver has been updated to support the 5000 and 5150 series.
146 There's one kernel module for each firmware. Adding "device iwnfw"
147 to the kernel configuration file means including all three firmware
148 images inside the kernel. If you want to include just the one for
149 your wireless card, use the the devices iwn4965fw, iwn5000fw or
153 The rc.d/network_ipv6, IPv6 configuration script has been integrated
154 into rc.d/netif. The changes are the following:
156 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
157 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
158 Note that both variables need the "inet6" keyword at the head.
160 Do not set $ipv6_network_interfaces manually if you do not
161 understand what you are doing. It is not needed in most cases.
163 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
166 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
167 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
169 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
170 all configured interfaces have "inet6 accept_rtadv" in the
171 $ifconfig_IF_ipv6. These are for backward compatibility.
173 3. A new variable $ipv6_prefer has been added. If NO, IPv6
174 functionality of interfaces with no corresponding
175 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
176 and the default address selection policy of ip6addrctl(8)
177 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
178 Note that if you want to configure IPv6 functionality on the
179 disabled interfaces after boot, first you need to clear the flag by
180 using ifconfig(8) like:
182 ifconfig em0 inet6 -ifdisabled
184 If YES, the default address selection policy is set as
187 The default value of $ipv6_prefer is NO.
189 4. If your system need to receive Router Advertisement messages,
190 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
191 scripts automatically invoke rtsol(8) when the interface becomes
192 UP. The Router Advertisement messages are used for SLAAC
193 (State-Less Address AutoConfiguration).
196 802.11s D3.03 support was committed. This is incompatible with the
197 previous code, which was based on D3.0.
200 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
201 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
202 control whether accepting Router Advertisement messages or not.
203 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
204 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
205 The ifconfig(8) utility now supports these flags.
208 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
209 mount(8) and -a option for df(1) to see them.
212 The old tunable hw.bus.devctl_disable has been superseded by
213 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
214 replaced by hw.bus.devctl_queue=0. The default for this new tunable
218 Remove the option STOP_NMI. The default action is now to use NMI only
219 for KDB via the newly introduced function stop_cpus_hard() and
220 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
223 The stable/8 branch created in subversion. This corresponds to the
224 RELENG_8 branch in CVS.
227 Bump the shared library version numbers for all libraries that do not
228 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
229 __FreeBSD_version to 800105.
232 Due to changes in the implementation of virtual network stack support,
233 all network-related kernel modules must be recompiled. As this change
234 breaks the ABI, bump __FreeBSD_version to 800104.
237 The TOE interface to the TCP syncache has been modified to remove
238 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
239 The cxgb driver is the only TOE consumer affected by this change, and
240 needs to be recompiled along with the kernel. As this change breaks
241 the ABI, bump __FreeBSD_version to 800103.
244 Padding has been added to struct tcpcb, sackhint and tcpstat in
245 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
246 maintaining the ABI. However, this change breaks the ABI, so bump
247 __FreeBSD_version to 800102. User space tools that rely on the size of
248 any of these structs (e.g. sockstat) need to be recompiled.
251 The NFS_LEGACYRPC option has been removed along with the old kernel
252 RPC implementation that this option selected. Kernel configurations
253 may need to be adjusted.
256 The network interface device nodes at /dev/net/<interface> have been
257 removed. All ioctl operations can be performed the normal way using
258 routing sockets. The kqueue functionality can generally be replaced
259 with routing sockets.
262 The documentation from the FreeBSD Documentation Project (Handbook,
263 FAQ, etc.) is now installed via packages by sysinstall(8) and under
264 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
267 The ABI of various structures related to the SYSV IPC API have been
268 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
269 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
273 Layout of struct vnet has changed as routing related variables were
274 moved to their own Vimage module. Modules need to be recompiled. Bump
275 __FreeBSD_version to 800099.
278 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
279 respectively. As long as no more than 16 groups per process are used,
280 no changes should be visible. When more than 16 groups are used, old
281 binaries may fail if they call getgroups() or getgrouplist() with
282 statically sized storage. Recompiling will work around this, but
283 applications should be modified to use dynamically allocated storage
284 for group arrays as POSIX.1-2008 does not cap an implementation's
285 number of supported groups at NGROUPS_MAX+1 as previous versions did.
287 NFS and portalfs mounts may also be affected as the list of groups is
288 truncated to 16. Users of NFS who use more than 16 groups, should
289 take care that negative group permissions are not used on the exported
290 file systems as they will not be reliable unless a GSSAPI based
291 authentication method is used.
294 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
295 option compiles in the support for adaptive spinning for lockmgrs
296 which want to enable it. The lockinit() function now accepts the flag
297 LK_ADAPTIVE in order to make the lock object subject to adaptive
298 spinning when both held in write and read mode.
301 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
302 changed. User applications that use this ioctl need to be rebuilt.
305 The layout of struct thread has changed. Kernel and modules need to
309 The layout of structs ifnet, domain, protosw and vnet_net has changed.
310 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
313 window(1) has been removed from the base system. It can now be
314 installed from ports. The port is called misc/window.
317 The way we are storing and accessing `routing table' entries has
318 changed. Programs reading the FIB, like netstat, need to be
322 A new netisr implementation has been added for FreeBSD 8. Network
323 file system modules, such as igmp, ipdivert, and others, should be
325 Bump __FreeBSD_version to 800096.
328 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
332 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
333 Bump __FreeBSD_version to 800094.
336 Add mnt_xflag field to 'struct mount'. File system modules need to be
338 Bump __FreeBSD_version to 800093.
341 The compiling option ADAPTIVE_SX has been retired while it has been
342 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
343 The KPI for sx_init_flags() changes as accepting flags:
344 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
345 been introduced in order to handle the reversed logic.
346 Bump __FreeBSD_version to 800092.
349 Add support for hierarchical jails. Remove global securelevel.
350 Bump __FreeBSD_version to 800091.
353 The layout of struct vnet_net has changed, therefore modules
355 Bump __FreeBSD_version to 800090.
358 The newly imported zic(8) produces a new format in the output. Please
359 run tzsetup(8) to install the newly created data to /etc/localtime.
362 The sysctl tree for the usb stack has renamed from hw.usb2.* to
363 hw.usb.* and is now consistent again with previous releases.
366 802.11 monitor mode support was revised and driver api's were changed.
367 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
368 of DLT_IEEE802_11. No user-visible data structures were changed but
369 applications that use DLT_IEEE802_11 may require changes.
370 Bump __FreeBSD_version to 800088.
373 The layout of the following structs has changed: sysctl_oid,
374 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
375 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
376 panics may be experienced. World rebuild is required for
377 correctly checking networking state from userland.
378 Bump __FreeBSD_version to 800085.
381 MLDv2 and Source-Specific Multicast (SSM) have been merged
382 to the IPv6 stack. VIMAGE hooks are in but not yet used.
383 The implementation of SSM within FreeBSD's IPv6 stack closely
384 follows the IPv4 implementation.
386 For kernel developers:
388 * The most important changes are that the ip6_output() and
389 ip6_input() paths no longer take the IN6_MULTI_LOCK,
390 and this lock has been downgraded to a non-recursive mutex.
392 * As with the changes to the IPv4 stack to support SSM, filtering
393 of inbound multicast traffic must now be performed by transport
394 protocols within the IPv6 stack. This does not apply to TCP and
395 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
397 * The KPIs used by IPv6 multicast are similar to those used by
398 the IPv4 stack, with the following differences:
399 * im6o_mc_filter() is analogous to imo_multicast_filter().
400 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
401 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
402 * IN6_LOOKUP_MULTI() has been deprecated and removed.
403 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
404 for MLDv1 have an additional 'timer' argument which is used to
405 jitter the initial membership report for the solicited-node
406 multicast membership on-link.
407 * This is not strictly needed for MLDv2, which already jitters
408 its report transmissions. However, the 'timer' argument is
409 preserved in case MLDv1 is active on the interface.
411 * The KAME linked-list based IPv6 membership implementation has
412 been refactored to use a vector similar to that used by the IPv4
414 Code which maintains a list of its own multicast memberships
415 internally, e.g. carp, has been updated to reflect the new
418 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
419 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
420 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
421 implementation constraint which needs to be addressed in HEAD.
423 For application developers:
425 * The changes are broadly similar to those made for the IPv4
428 * The use of IPv4 and IPv6 multicast socket options on the same
429 socket, using mapped addresses, HAS NOT been tested or supported.
431 * There are a number of issues with the implementation of various
432 IPv6 multicast APIs which need to be resolved in the API surface
433 before the implementation is fully compatible with KAME userland
434 use, and these are mostly to do with interface index treatment.
436 * The literature available discusses the use of either the delta / ASM
437 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
438 using setsourcefilter(3)/getsourcefilter(3). For more information
439 please refer to RFC 3768, 'Socket Interface Extensions for
440 Multicast Source Filters'.
442 * Applications which use the published RFC 3678 APIs should be fine.
444 For systems administrators:
446 * The mtest(8) utility has been refactored to support IPv6, in
447 addition to IPv4. Interface addresses are no longer accepted
448 as arguments, their names must be used instead. The utility
449 will map the interface name to its first IPv4 address as
450 returned by getifaddrs(3).
452 * The ifmcstat(8) utility has also been updated to print the MLDv2
453 endpoint state and source filter lists via sysctl(3).
455 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
456 loopback of IPv6 multicast datagrams by default; it defaults to 1
457 to preserve the existing behaviour. Disabling multicast loopback is
458 recommended for optimal system performance.
460 * The IPv6 MROUTING code has been changed to examine this sysctl
461 instead of attempting to perform a group lookup before looping
462 back forwarded datagrams.
464 Bump __FreeBSD_version to 800084.
467 Implement low-level Bluetooth HCI API.
468 Bump __FreeBSD_version to 800083.
471 The layout of struct malloc_type, used by modules to register new
472 memory allocation types, has changed. Most modules will need to
473 be rebuilt or panics may be experienced.
474 Bump __FreeBSD_version to 800081.
477 Anticipate overflowing inp_flags - add inp_flags2.
478 This changes most offsets in inpcb, so checking v4 connection
479 state will require a world rebuild.
480 Bump __FreeBSD_version to 800080.
483 Add an llentry to struct route and struct route_in6. Modules
484 embedding a struct route will need to be recompiled.
485 Bump __FreeBSD_version to 800079.
488 The size of rt_metrics_lite and by extension rtentry has changed.
489 Networking administration apps will need to be recompiled.
490 The route command now supports show as an alias for get, weighting
491 of routes, sticky and nostick flags to alter the behavior of stateful
493 Bump __FreeBSD_version to 800078.
496 Do not use Giant for kbdmux(4) locking. This is wrong and
497 apparently causing more problems than it solves. This will
498 re-open the issue where interrupt handlers may race with
499 kbdmux(4) in polling mode. Typical symptoms include (but
500 not limited to) duplicated and/or missing characters when
501 low level console functions (such as gets) are used while
502 interrupts are enabled (for example geli password prompt,
503 mountroot prompt etc.). Disabling kbdmux(4) may help.
506 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
507 kernel modules referencing any of the above need to be recompiled.
508 Bump __FreeBSD_version to 800075.
511 GEOM_PART has become the default partition slicer for storage devices,
512 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
513 introduces some changes:
515 MSDOS/EBR: the devices created from MSDOS extended partition entries
516 (EBR) can be named differently than with GEOM_MBR and are now symlinks
517 to devices with offset-based names. fstabs may need to be modified.
519 BSD: the "geometry does not match label" warning is harmless in most
520 cases but it points to problems in file system misalignment with
521 disk geometry. The "c" partition is now implicit, covers the whole
522 top-level drive and cannot be (mis)used by users.
524 General: Kernel dumps are now not allowed to be written to devices
525 whose partition types indicate they are meant to be used for file
526 systems (or, in case of MSDOS partitions, as something else than
529 Most of these changes date approximately from 200812.
532 The uscanner(4) driver has been removed from the kernel. This follows
533 Linux removing theirs in 2.6 and making libusb the default interface
537 The multicast forwarding code has been cleaned up. netstat(1)
538 only relies on KVM now for printing bandwidth upcall meters.
539 The IPv4 and IPv6 modules are split into ip_mroute_mod and
540 ip6_mroute_mod respectively. The config(5) options for statically
541 compiling this code remain the same, i.e. 'options MROUTING'.
544 Support for the IFF_NEEDSGIANT network interface flag has been
545 removed, which means that non-MPSAFE network device drivers are no
546 longer supported. In particular, if_ar, if_sr, and network device
547 drivers from the old (legacy) USB stack can no longer be built or
551 POSIX.1 Native Language Support (NLS) has been enabled in libc and
552 a bunch of new language catalog files have also been added.
553 This means that some common libc messages are now localized and
554 they depend on the LC_MESSAGES environmental variable.
557 The k8temp(4) driver has been renamed to amdtemp(4) since
558 support for Family 10 and Family 11 CPU families was added.
561 IGMPv3 and Source-Specific Multicast (SSM) have been merged
562 to the IPv4 stack. VIMAGE hooks are in but not yet used.
564 For kernel developers, the most important changes are that the
565 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
566 and this lock has been downgraded to a non-recursive mutex.
568 Transport protocols (UDP, Raw IP) are now responsible for filtering
569 inbound multicast traffic according to group membership and source
570 filters. The imo_multicast_filter() KPI exists for this purpose.
571 Transports which do not use multicast (SCTP, TCP) already reject
572 multicast by default. Forwarding and receive performance may improve
573 as a mutex acquisition is no longer needed in the ip_input()
574 low-level input path. in_addmulti() and in_delmulti() are shimmed
575 to new KPIs which exist to support SSM in-kernel.
577 For application developers, it is recommended that loopback of
578 multicast datagrams be disabled for best performance, as this
579 will still cause the lock to be taken for each looped-back
580 datagram transmission. The net.inet.ip.mcast.loop sysctl may
581 be tuned to 0 to disable loopback by default; it defaults to 1
582 to preserve the existing behaviour.
584 For systems administrators, to obtain best performance with
585 multicast reception and multiple groups, it is always recommended
586 that a card with a suitably precise hash filter is used. Hash
587 collisions will still result in the lock being taken within the
588 transport protocol input path to check group membership.
590 If deploying FreeBSD in an environment with IGMP snooping switches,
591 it is recommended that the net.inet.igmp.sendlocal sysctl remain
592 enabled; this forces 224.0.0.0/24 group membership to be announced
595 The size of 'struct igmpstat' has changed; netstat needs to be
596 recompiled to reflect this.
597 Bump __FreeBSD_version to 800070.
600 libusb20.so.1 is now installed as libusb.so.1 and the ports system
601 updated to use it. This requires a buildworld/installworld in order to
602 update the library and dependencies (usbconfig, etc). Its advisable to
603 rebuild all ports which uses libusb. More specific directions are given
604 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
605 libusb are no longer required and can be removed.
608 A workaround is committed to allow the creation of System V shared
609 memory segment of size > 2 GB on the 64-bit architectures.
610 Due to a limitation of the existing ABI, the shm_segsz member
611 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
612 wrong for large segments. Note that limits must be explicitly
613 raised to allow such segments to be created.
616 The layout of struct ifnet has changed, requiring a rebuild of all
617 network device driver modules.
620 The /dev handling for the new USB stack has changed, a
621 buildworld/installworld is required for libusb20.
624 The new USB2 stack has now been permanently moved in and all kernel and
625 module names reverted to their previous values (eg, usb, ehci, ohci,
626 ums, ...). The old usb stack can be compiled in by prefixing the name
627 with the letter 'o', the old usb modules have been removed.
628 Updating entry 20090216 for xorg and 20090215 for libmap may still
632 The rc.conf(5) option if_up_delay has been renamed to
633 defaultroute_delay to better reflect its purpose. If you have
634 customized this setting in /etc/rc.conf you need to update it to
638 xorg 7.4 wants to configure its input devices via hald which does not
639 yet work with USB2. If the keyboard/mouse does not work in xorg then
641 Option "AllowEmptyInput" "off"
642 to your ServerLayout section. This will cause X to use the configured
643 kbd and mouse sections from your xorg.conf.
646 The GENERIC kernels for all architectures now default to the new USB2
647 stack. No kernel config options or code have been removed so if a
648 problem arises please report it and optionally revert to the old USB
649 stack. If you are loading USB kernel modules or have a custom kernel
650 that includes GENERIC then ensure that usb names are also changed over,
651 eg uftdi -> usb2_serial_ftdi.
653 Older programs linked against the ports libusb 0.1 need to be
654 redirected to the new stack's libusb20. /etc/libmap.conf can
656 # Map old usb library to new one for usb2 stack
657 libusb-0.1.so.8 libusb20.so.1
660 All USB ethernet devices now attach as interfaces under the name ueN
661 (eg. ue0). This is to provide a predictable name as vendors often
662 change usb chipsets in a product without notice.
665 The ichsmb(4) driver has been changed to require SMBus slave
666 addresses be left-justified (xxxxxxx0b) rather than right-justified.
667 All of the other SMBus controller drivers require left-justified
668 slave addresses, so this change makes all the drivers provide the
672 INET6 statistics (struct ip6stat) was updated.
673 netstat(1) needs to be recompiled.
676 NTFS has been removed from GENERIC kernel on amd64 to match
677 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
678 will load ntfs.ko module automatically when NTFS support is
679 actually needed, unless ntfs.ko is not installed or security
680 level prohibits loading kernel modules. If either is the case,
681 "options NTFS" has to be added into kernel config.
684 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
685 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
686 800061. User space tools that rely on the size of struct tcpcb in
687 tcp_var.h (e.g. sockstat) need to be recompiled.
690 ng_tty(4) module updated to match the new TTY subsystem.
691 Due to API change, user-level applications must be updated.
692 New API support added to mpd5 CVS and expected to be present
693 in next mpd5.3 release.
696 With __FreeBSD_version 800060 the makefs tool is part of
697 the base system (it was a port).
700 The afdata and ifnet locks have been changed from mutexes to
701 rwlocks, network modules will need to be re-compiled.
704 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
705 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
706 The new code reduced struct rtentry{} by 16 bytes on 32-bit
707 architecture and 40 bytes on 64-bit architecture. The userland
708 applications "arp" and "ndp" have been updated accordingly.
709 The output from "netstat -r" shows only routing entries and
710 none of the L2 information.
713 __FreeBSD_version 800057 marks the switchover from the
714 binary ath hal to source code. Users must add the line:
716 options AH_SUPPORT_AR5416
718 to their kernel config files when specifying:
722 The ath_hal module no longer exists; the code is now compiled
723 together with the driver in the ath module. It is now
724 possible to tailor chip support (i.e. reduce the set of chips
725 and thereby the code size); consult ath_hal(4) for details.
728 __FreeBSD_version 800054 adds memory barriers to
729 <machine/atomic.h>, new interfaces to ifnet to facilitate
730 multiple hardware transmit queues for cards that support
731 them, and a lock-less ring-buffer implementation to
732 enable drivers to more efficiently manage queueing of
736 A new version of ZFS (version 13) has been merged to -HEAD.
737 This version has zpool attribute "listsnapshots" off by
738 default, which means "zfs list" does not show snapshots,
739 and is the same as Solaris behavior.
742 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
745 The uhci, ohci, ehci and slhci USB Host controller drivers have
746 been put into separate modules. If you load the usb module
747 separately through loader.conf you will need to load the
748 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
749 controller add the following to loader.conf:
755 The ABI used by the PMC toolset has changed. Please keep
756 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
760 atapci kernel module now includes only generic PCI ATA
761 driver. AHCI driver moved to ataahci kernel module.
762 All vendor-specific code moved into separate kernel modules:
763 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
764 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
765 atamarvell, atamicron, atanational, atanetcell, atanvidia,
766 atapromise, ataserverworks, atasiliconimage, atasis, atavia
769 The TTY subsystem of the kernel has been replaced by a new
770 implementation, which provides better scalability and an
771 improved driver model. Most common drivers have been migrated to
772 the new TTY subsystem, while others have not. The following
773 drivers have not yet been ported to the new TTY layer:
776 cy, digi, rc, rp, sio
782 ng_h4, ng_tty, ppp, sl, snp
784 Adding these drivers to your kernel configuration file shall
785 cause compilation to fail.
788 ntpd has been upgraded to 4.2.4p5.
791 OpenSSH has been upgraded to 5.1p1.
793 For many years, FreeBSD's version of OpenSSH preferred DSA
794 over RSA for host and user authentication keys. With this
795 upgrade, we've switched to the vendor's default of RSA over
796 DSA. This may cause upgraded clients to warn about unknown
797 host keys even for previously known hosts. Users should
798 follow the usual procedure for verifying host keys before
799 accepting the RSA key.
801 This can be circumvented by setting the "HostKeyAlgorithms"
802 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
805 Please note that the sequence of keys offered for
806 authentication has been changed as well. You may want to
807 specify IdentityFile in a different order to revert this
811 The sio(4) driver has been removed from the i386 and amd64
812 kernel configuration files. This means uart(4) is now the
813 default serial port driver on those platforms as well.
815 To prevent collisions with the sio(4) driver, the uart(4) driver
816 uses different names for its device nodes. This means the
817 onboard serial port will now most likely be called "ttyu0"
818 instead of "ttyd0". You may need to reconfigure applications to
819 use the new device names.
821 When using the serial port as a boot console, be sure to update
822 /boot/device.hints and /etc/ttys before booting the new kernel.
823 If you forget to do so, you can still manually specify the hints
824 at the loader prompt:
826 set hint.uart.0.at="isa"
827 set hint.uart.0.port="0x3F8"
828 set hint.uart.0.flags="0x10"
829 set hint.uart.0.irq="4"
833 The gpt(8) utility has been removed. Use gpart(8) to partition
837 The version that Linuxulator emulates was changed from 2.4.2
838 to 2.6.16. If you experience any problems with Linux binaries
839 please try to set sysctl compat.linux.osrelease to 2.4.2 and
840 if it fixes the problem contact emulation mailing list.
843 ISDN4BSD (I4B) was removed from the src tree. You may need to
844 update a your kernel configuration and remove relevant entries.
847 I have checked in code to support multiple routing tables.
848 See the man pages setfib(1) and setfib(2).
849 This is a hopefully backwards compatible version,
850 but to make use of it you need to compile your kernel
851 with options ROUTETABLES=2 (or more up to 16).
854 The 802.11 wireless support was redone to enable multi-bss
855 operation on devices that are capable. The underlying device
856 is no longer used directly but instead wlanX devices are
857 cloned with ifconfig. This requires changes to rc.conf files.
859 ifconfig_ath0="WPA DHCP"
862 ifconfig_wlan0="WPA DHCP"
863 see rc.conf(5) for more details. In addition, mergemaster of
864 /etc/rc.d is highly recommended. Simultaneous update of userland
865 and kernel wouldn't hurt either.
867 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
868 modules were merged into the base wlan module. All references
869 to these modules (e.g. in kernel config files) must be removed.
872 psm(4) has gained write(2) support in native operation level.
873 Arbitrary commands can be written to /dev/psm%d and status can
874 be read back from it. Therefore, an application is responsible
875 for status validation and error recovery. It is a no-op in
876 other operation levels.
879 Support for KSE threading has been removed from the kernel. To
880 run legacy applications linked against KSE libmap.conf may
881 be used. The following libmap.conf may be used to ensure
882 compatibility with any prior release:
884 libpthread.so.1 libthr.so.1
885 libpthread.so.2 libthr.so.2
886 libkse.so.3 libthr.so.3
889 The layout of struct vmspace has changed. This affects libkvm
890 and any executables that link against libkvm and use the
891 kvm_getprocs() function. In particular, but not exclusively,
892 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
893 The effects are minimal, but it's advisable to upgrade world
897 The latest em driver no longer has support in it for the
898 82575 adapter, this is now moved to the igb driver. The
899 split was done to make new features that are incompatible
900 with older hardware easier to do.
903 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
904 likewise the kernel option is now GEOM_LINUX_LVM.
907 The default NFS mount mode has changed from UDP to TCP for
908 increased reliability. If you rely on (insecurely) NFS
909 mounting across a firewall you may need to update your
913 Belatedly note the addition of m_collapse for compacting
917 The fts(3) structures have been changed to use adequate
918 integer types for their members and so to be able to cope
919 with huge file trees. The old fts(3) ABI is preserved
920 through symbol versioning in libc, so third-party binaries
921 using fts(3) should still work, although they will not take
922 advantage of the extended types. At the same time, some
923 third-party software might fail to build after this change
924 due to unportable assumptions made in its source code about
925 fts(3) structure members. Such software should be fixed
926 by its vendor or, in the worst case, in the ports tree.
927 FreeBSD_version 800015 marks this change for the unlikely
928 case that a portable fix is impossible.
931 To upgrade to -current after this date, you must be running
932 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
933 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
936 The ADAPTIVE_GIANT kernel option has been retired because its
937 functionality is the default now.
940 The AT keyboard emulation of sunkbd(4) has been turned on
941 by default. In order to make the special symbols of the Sun
942 keyboards driven by sunkbd(4) work under X these now have
943 to be configured the same way as Sun USB keyboards driven
944 by ukbd(4) (which also does AT keyboard emulation), f.e.:
946 Option "XkbLayout" "us"
947 Option "XkbRules" "xorg"
948 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
951 It has been decided that it is desirable to provide ABI
952 backwards compatibility to the FreeBSD 4/5/6 versions of the
953 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
954 broken with the introduction of PCI domain support (see the
955 20070930 entry). Unfortunately, this required the ABI of
956 PCIOCGETCONF to be broken again in order to be able to
957 provide backwards compatibility to the old version of that
958 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
959 again. As for prominent ports this affects neither pciutils
960 nor xorg-server this time, the hal port needs to be rebuilt
964 The misnamed kthread_create() and friends have been renamed
965 to kproc_create() etc. Many of the callers already
967 I will return kthread_create() and friends in a while
968 with implementations that actually create threads, not procs.
969 Renaming corresponds with version 800002.
978 Avoid using make -j when upgrading. While generally safe, there are
979 sometimes problems using -j to upgrade. If your upgrade fails with
980 -j, please try again without -j. From time to time in the past there
981 have been problems using -j with buildworld and/or installworld. This
982 is especially true when upgrading between "distant" versions (eg one
983 that cross a major release boundary or several minor releases, or when
984 several months have passed on the -current branch).
986 Sometimes, obscure build problems are the result of environment
987 poisoning. This can happen because the make utility reads its
988 environment when searching for values for global variables. To run
989 your build attempts in an "environmental clean room", prefix all make
990 commands with 'env -i '. See the env(1) manual page for more details.
992 When upgrading from one major version to another it is generally best
993 to upgrade to the latest code in the currently installed branch first,
994 then do an upgrade to the new branch. This is the best-tested upgrade
995 path, and has the highest probability of being successful. Please try
996 this approach before reporting problems with a major version upgrade.
1000 When upgrading the boot ZFS pool to a new version, always follow
1003 1.) recompile and reinstall the ZFS boot loader and boot block
1004 (this is part of "make buildworld" and "make installworld")
1006 2.) update the ZFS boot block on your boot drive
1008 The following example updates the ZFS boot block on the first
1009 partition (freebsd-boot) of a GPT partitioned drive ad0:
1010 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1012 Non-boot pools do not need these updates.
1016 If you are updating from a prior version of FreeBSD (even one just
1017 a few days old), you should follow this procedure. It is the most
1018 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1020 make kernel-toolchain
1021 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1022 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1024 To test a kernel once
1025 ---------------------
1026 If you just want to boot a kernel once (because you are not sure
1027 if it works, or if you want to boot a known bad kernel to provide
1028 debugging information) run
1029 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1030 nextboot -k testkernel
1032 To just build a kernel when you know that it won't mess you up
1033 --------------------------------------------------------------
1034 This assumes you are already running a CURRENT system. Replace
1035 ${arch} with the architecture of your machine (e.g. "i386",
1036 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1038 cd src/sys/${arch}/conf
1039 config KERNEL_NAME_HERE
1040 cd ../compile/KERNEL_NAME_HERE
1045 If this fails, go to the "To build a kernel" section.
1047 To rebuild everything and install it on the current system.
1048 -----------------------------------------------------------
1049 # Note: sometimes if you are running current you gotta do more than
1050 # is listed here if you are upgrading from a really old current.
1052 <make sure you have good level 0 dumps>
1054 make kernel KERNCONF=YOUR_KERNEL_HERE
1056 <reboot in single user> [3]
1064 To cross-install current onto a separate partition
1065 --------------------------------------------------
1066 # In this approach we use a separate partition to hold
1067 # current's root, 'usr', and 'var' directories. A partition
1068 # holding "/", "/usr" and "/var" should be about 2GB in
1071 <make sure you have good level 0 dumps>
1074 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1075 <maybe newfs current's root partition>
1076 <mount current's root partition on directory ${CURRENT_ROOT}>
1077 make installworld DESTDIR=${CURRENT_ROOT}
1078 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1079 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1080 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1081 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1082 <reboot into current>
1083 <do a "native" rebuild/install as described in the previous section>
1084 <maybe install compatibility libraries from ports/misc/compat*>
1088 To upgrade in-place from 8.x-stable to current
1089 ----------------------------------------------
1090 <make sure you have good level 0 dumps>
1092 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1094 <reboot in single user> [3]
1101 Make sure that you've read the UPDATING file to understand the
1102 tweaks to various things you need. At this point in the life
1103 cycle of current, things change often and you are on your own
1104 to cope. The defaults can also change, so please read ALL of
1105 the UPDATING entries.
1107 Also, if you are tracking -current, you must be subscribed to
1108 freebsd-current@freebsd.org. Make sure that before you update
1109 your sources that you have read and understood all the recent
1110 messages there. If in doubt, please track -stable which has
1111 much fewer pitfalls.
1113 [1] If you have third party modules, such as vmware, you
1114 should disable them at this point so they don't crash your
1117 [3] From the bootblocks, boot -s, and then do
1122 adjkerntz -i # if CMOS is wall time
1123 Also, when doing a major release upgrade, it is required that
1124 you boot into single user mode to do the installworld.
1126 [4] Note: This step is non-optional. Failure to do this step
1127 can result in a significant reduction in the functionality of the
1128 system. Attempting to do it by hand is not recommended and those
1129 that pursue this avenue should read this file carefully, as well
1130 as the archives of freebsd-current and freebsd-hackers mailing lists
1131 for potential gotchas. The -U option is also useful to consider.
1132 See mergemaster(8) for more information.
1134 [5] Usually this step is a noop. However, from time to time
1135 you may need to do this if you get unknown user in the following
1136 step. It never hurts to do it all the time. You may need to
1137 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1138 install) after the buildworld before this step if you last updated
1139 from current before 20020224 or from -stable before 20020408.
1141 [8] In order to have a kernel that can run the 4.x binaries needed to
1142 do an installworld, you must include the COMPAT_FREEBSD4 option in
1143 your kernel. Failure to do so may leave you with a system that is
1144 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1145 required to run the 5.x binaries on more recent kernels. And so on
1146 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1148 Make sure that you merge any new devices from GENERIC since the
1149 last time you updated your kernel config file.
1151 [9] When checking out sources, you must include the -P flag to have
1152 cvs prune empty directories.
1154 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1155 "?=" instead of the "=" assignment operator, so that buildworld can
1156 override the CPUTYPE if it needs to.
1158 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1159 not on the command line, or in /etc/make.conf. buildworld will
1160 warn if it is improperly defined.
1163 This file contains a list, in reverse chronological order, of major
1164 breakages in tracking -current. Not all things will be listed here,
1165 and it only starts on October 16, 2004. Updating files can found in
1166 previous releases if your system is older than this.
1168 Copyright information:
1170 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1172 Redistribution, publication, translation and use, with or without
1173 modification, in full or in part, in any form or format of this
1174 document are permitted without further permission from the author.
1176 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1177 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1178 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1179 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1180 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1181 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1182 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1183 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1184 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1185 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1186 POSSIBILITY OF SUCH DAMAGE.
1188 Contact Warner Losh if you have any questions about your use of