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 Introduce the kernel thread "deadlock resolver" (which can be enabled
27 via the DEADLKRES option, see NOTES for more details) and the
28 sleepq_type() function for sleepqueues.
31 The rc.firewall and rc.firewall6 were unified, and
32 rc.firewall6 and rc.d/ip6fw were removed.
33 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
34 variables are obsoleted. Instead, the following new rc
35 variables are added to rc.d/ipfw:
37 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
38 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
39 firewall_simple_onet_ipv6, firewall_trusted_ipv6
41 The meanings correspond to the relevant IPv4 variables.
44 The default terminal emulation for syscons(4) has been changed
45 from cons25 to xterm on all platforms except pc98. This means
46 that the /etc/ttys file needs to be updated to ensure correct
47 operation of applications on the console.
49 The terminal emulation style can be toggled per window by using
50 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
51 options can be used to change the compile-time default back to
54 To prevent graphical artifacts, make sure the TERM environment
55 variable is set to match the terminal emulation that is being
56 performed by syscons(4).
59 The layout of the structure ieee80211req_scan_result has changed.
60 Applications that require wireless scan results (e.g. ifconfig(8))
61 from net80211 need to be recompiled.
63 Applications such as wpa_supplicant(8) may require a full world
64 build without using NO_CLEAN in order to get synchronized with the
68 The iwn(4) driver has been updated to support the 5000 and 5150 series.
69 There's one kernel module for each firmware. Adding "device iwnfw"
70 to the kernel configuration file means including all three firmware
71 images inside the kernel. If you want to include just the one for
72 your wireless card, use the the devices iwn4965fw, iwn5000fw or
76 The rc.d/network_ipv6, IPv6 configuration script has been integrated
77 into rc.d/netif. The changes are the following:
79 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
80 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
81 Note that both variables need the "inet6" keyword at the head.
83 Do not set $ipv6_network_interfaces manually if you do not
84 understand what you are doing. It is not needed in most cases.
86 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
89 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
90 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
92 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
93 all configured interfaces have "inet6 accept_rtadv" in the
94 $ifconfig_IF_ipv6. These are for backward compatibility.
96 3. A new variable $ipv6_prefer has been added. If NO, IPv6
97 functionality of interfaces with no corresponding
98 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
99 and the default address selection policy of ip6addrctl(8)
100 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
101 Note that if you want to configure IPv6 functionality on the
102 disabled interfaces after boot, first you need to clear the flag by
103 using ifconfig(8) like:
105 ifconfig em0 inet6 -ifdisabled
107 If YES, the default address selection policy is set as
110 The default value of $ipv6_prefer is NO.
112 4. If your system need to receive Router Advertisement messages,
113 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
114 scripts automatically invoke rtsol(8) when the interface becomes
115 UP. The Router Advertisement messages are used for SLAAC
116 (State-Less Address AutoConfiguration).
119 802.11s D3.03 support was committed. This is incompatible with the
120 previous code, which was based on D3.0.
123 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
124 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
125 control whether accepting Router Advertisement messages or not.
126 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
127 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
128 The ifconfig(8) utility now supports these flags.
131 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
132 mount(8) and -a option for df(1) to see them.
135 The old tunable hw.bus.devctl_disable has been superseded by
136 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
137 replaced by hw.bus.devctl_queue=0. The default for this new tunable
141 Remove the option STOP_NMI. The default action is now to use NMI only
142 for KDB via the newly introduced function stop_cpus_hard() and
143 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
146 The stable/8 branch created in subversion. This corresponds to the
147 RELENG_8 branch in CVS.
150 Bump the shared library version numbers for all libraries that do not
151 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
152 __FreeBSD_version to 800105.
155 Due to changes in the implementation of virtual network stack support,
156 all network-related kernel modules must be recompiled. As this change
157 breaks the ABI, bump __FreeBSD_version to 800104.
160 The TOE interface to the TCP syncache has been modified to remove
161 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
162 The cxgb driver is the only TOE consumer affected by this change, and
163 needs to be recompiled along with the kernel. As this change breaks
164 the ABI, bump __FreeBSD_version to 800103.
167 Padding has been added to struct tcpcb, sackhint and tcpstat in
168 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
169 maintaining the ABI. However, this change breaks the ABI, so bump
170 __FreeBSD_version to 800102. User space tools that rely on the size of
171 any of these structs (e.g. sockstat) need to be recompiled.
174 The NFS_LEGACYRPC option has been removed along with the old kernel
175 RPC implementation that this option selected. Kernel configurations
176 may need to be adjusted.
179 The network interface device nodes at /dev/net/<interface> have been
180 removed. All ioctl operations can be performed the normal way using
181 routing sockets. The kqueue functionality can generally be replaced
182 with routing sockets.
185 The documentation from the FreeBSD Documentation Project (Handbook,
186 FAQ, etc.) is now installed via packages by sysinstall(8) and under
187 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
190 The ABI of various structures related to the SYSV IPC API have been
191 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
192 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
196 Layout of struct vnet has changed as routing related variables were
197 moved to their own Vimage module. Modules need to be recompiled. Bump
198 __FreeBSD_version to 800099.
201 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
202 respectively. As long as no more than 16 groups per process are used,
203 no changes should be visible. When more than 16 groups are used, old
204 binaries may fail if they call getgroups() or getgrouplist() with
205 statically sized storage. Recompiling will work around this, but
206 applications should be modified to use dynamically allocated storage
207 for group arrays as POSIX.1-2008 does not cap an implementation's
208 number of supported groups at NGROUPS_MAX+1 as previous versions did.
210 NFS and portalfs mounts may also be affected as the list of groups is
211 truncated to 16. Users of NFS who use more than 16 groups, should
212 take care that negative group permissions are not used on the exported
213 file systems as they will not be reliable unless a GSSAPI based
214 authentication method is used.
217 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
218 option compiles in the support for adaptive spinning for lockmgrs
219 which want to enable it. The lockinit() function now accepts the flag
220 LK_ADAPTIVE in order to make the lock object subject to adaptive
221 spinning when both held in write and read mode.
224 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
225 changed. User applications that use this ioctl need to be rebuilt.
228 The layout of struct thread has changed. Kernel and modules need to
232 The layout of structs ifnet, domain, protosw and vnet_net has changed.
233 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
236 window(1) has been removed from the base system. It can now be
237 installed from ports. The port is called misc/window.
240 The way we are storing and accessing `routing table' entries has
241 changed. Programs reading the FIB, like netstat, need to be
245 A new netisr implementation has been added for FreeBSD 8. Network
246 file system modules, such as igmp, ipdivert, and others, should be
248 Bump __FreeBSD_version to 800096.
251 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
255 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
256 Bump __FreeBSD_version to 800094.
259 Add mnt_xflag field to 'struct mount'. File system modules need to be
261 Bump __FreeBSD_version to 800093.
264 The compiling option ADAPTIVE_SX has been retired while it has been
265 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
266 The KPI for sx_init_flags() changes as accepting flags:
267 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
268 been introduced in order to handle the reversed logic.
269 Bump __FreeBSD_version to 800092.
272 Add support for hierarchical jails. Remove global securelevel.
273 Bump __FreeBSD_version to 800091.
276 The layout of struct vnet_net has changed, therefore modules
278 Bump __FreeBSD_version to 800090.
281 The newly imported zic(8) produces a new format in the output. Please
282 run tzsetup(8) to install the newly created data to /etc/localtime.
285 The sysctl tree for the usb stack has renamed from hw.usb2.* to
286 hw.usb.* and is now consistent again with previous releases.
289 802.11 monitor mode support was revised and driver api's were changed.
290 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
291 of DLT_IEEE802_11. No user-visible data structures were changed but
292 applications that use DLT_IEEE802_11 may require changes.
293 Bump __FreeBSD_version to 800088.
296 The layout of the following structs has changed: sysctl_oid,
297 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
298 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
299 panics may be experienced. World rebuild is required for
300 correctly checking networking state from userland.
301 Bump __FreeBSD_version to 800085.
304 MLDv2 and Source-Specific Multicast (SSM) have been merged
305 to the IPv6 stack. VIMAGE hooks are in but not yet used.
306 The implementation of SSM within FreeBSD's IPv6 stack closely
307 follows the IPv4 implementation.
309 For kernel developers:
311 * The most important changes are that the ip6_output() and
312 ip6_input() paths no longer take the IN6_MULTI_LOCK,
313 and this lock has been downgraded to a non-recursive mutex.
315 * As with the changes to the IPv4 stack to support SSM, filtering
316 of inbound multicast traffic must now be performed by transport
317 protocols within the IPv6 stack. This does not apply to TCP and
318 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
320 * The KPIs used by IPv6 multicast are similar to those used by
321 the IPv4 stack, with the following differences:
322 * im6o_mc_filter() is analogous to imo_multicast_filter().
323 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
324 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
325 * IN6_LOOKUP_MULTI() has been deprecated and removed.
326 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
327 for MLDv1 have an additional 'timer' argument which is used to
328 jitter the initial membership report for the solicited-node
329 multicast membership on-link.
330 * This is not strictly needed for MLDv2, which already jitters
331 its report transmissions. However, the 'timer' argument is
332 preserved in case MLDv1 is active on the interface.
334 * The KAME linked-list based IPv6 membership implementation has
335 been refactored to use a vector similar to that used by the IPv4
337 Code which maintains a list of its own multicast memberships
338 internally, e.g. carp, has been updated to reflect the new
341 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
342 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
343 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
344 implementation constraint which needs to be addressed in HEAD.
346 For application developers:
348 * The changes are broadly similar to those made for the IPv4
351 * The use of IPv4 and IPv6 multicast socket options on the same
352 socket, using mapped addresses, HAS NOT been tested or supported.
354 * There are a number of issues with the implementation of various
355 IPv6 multicast APIs which need to be resolved in the API surface
356 before the implementation is fully compatible with KAME userland
357 use, and these are mostly to do with interface index treatment.
359 * The literature available discusses the use of either the delta / ASM
360 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
361 using setsourcefilter(3)/getsourcefilter(3). For more information
362 please refer to RFC 3768, 'Socket Interface Extensions for
363 Multicast Source Filters'.
365 * Applications which use the published RFC 3678 APIs should be fine.
367 For systems administrators:
369 * The mtest(8) utility has been refactored to support IPv6, in
370 addition to IPv4. Interface addresses are no longer accepted
371 as arguments, their names must be used instead. The utility
372 will map the interface name to its first IPv4 address as
373 returned by getifaddrs(3).
375 * The ifmcstat(8) utility has also been updated to print the MLDv2
376 endpoint state and source filter lists via sysctl(3).
378 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
379 loopback of IPv6 multicast datagrams by default; it defaults to 1
380 to preserve the existing behaviour. Disabling multicast loopback is
381 recommended for optimal system performance.
383 * The IPv6 MROUTING code has been changed to examine this sysctl
384 instead of attempting to perform a group lookup before looping
385 back forwarded datagrams.
387 Bump __FreeBSD_version to 800084.
390 Implement low-level Bluetooth HCI API.
391 Bump __FreeBSD_version to 800083.
394 The layout of struct malloc_type, used by modules to register new
395 memory allocation types, has changed. Most modules will need to
396 be rebuilt or panics may be experienced.
397 Bump __FreeBSD_version to 800081.
400 Anticipate overflowing inp_flags - add inp_flags2.
401 This changes most offsets in inpcb, so checking v4 connection
402 state will require a world rebuild.
403 Bump __FreeBSD_version to 800080.
406 Add an llentry to struct route and struct route_in6. Modules
407 embedding a struct route will need to be recompiled.
408 Bump __FreeBSD_version to 800079.
411 The size of rt_metrics_lite and by extension rtentry has changed.
412 Networking administration apps will need to be recompiled.
413 The route command now supports show as an alias for get, weighting
414 of routes, sticky and nostick flags to alter the behavior of stateful
416 Bump __FreeBSD_version to 800078.
419 Do not use Giant for kbdmux(4) locking. This is wrong and
420 apparently causing more problems than it solves. This will
421 re-open the issue where interrupt handlers may race with
422 kbdmux(4) in polling mode. Typical symptoms include (but
423 not limited to) duplicated and/or missing characters when
424 low level console functions (such as gets) are used while
425 interrupts are enabled (for example geli password prompt,
426 mountroot prompt etc.). Disabling kbdmux(4) may help.
429 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
430 kernel modules referencing any of the above need to be recompiled.
431 Bump __FreeBSD_version to 800075.
434 GEOM_PART has become the default partition slicer for storage devices,
435 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
436 introduces some changes:
438 MSDOS/EBR: the devices created from MSDOS extended partition entries
439 (EBR) can be named differently than with GEOM_MBR and are now symlinks
440 to devices with offset-based names. fstabs may need to be modified.
442 BSD: the "geometry does not match label" warning is harmless in most
443 cases but it points to problems in file system misalignment with
444 disk geometry. The "c" partition is now implicit, covers the whole
445 top-level drive and cannot be (mis)used by users.
447 General: Kernel dumps are now not allowed to be written to devices
448 whose partition types indicate they are meant to be used for file
449 systems (or, in case of MSDOS partitions, as something else than
452 Most of these changes date approximately from 200812.
455 The uscanner(4) driver has been removed from the kernel. This follows
456 Linux removing theirs in 2.6 and making libusb the default interface
460 The multicast forwarding code has been cleaned up. netstat(1)
461 only relies on KVM now for printing bandwidth upcall meters.
462 The IPv4 and IPv6 modules are split into ip_mroute_mod and
463 ip6_mroute_mod respectively. The config(5) options for statically
464 compiling this code remain the same, i.e. 'options MROUTING'.
467 Support for the IFF_NEEDSGIANT network interface flag has been
468 removed, which means that non-MPSAFE network device drivers are no
469 longer supported. In particular, if_ar, if_sr, and network device
470 drivers from the old (legacy) USB stack can no longer be built or
474 POSIX.1 Native Language Support (NLS) has been enabled in libc and
475 a bunch of new language catalog files have also been added.
476 This means that some common libc messages are now localized and
477 they depend on the LC_MESSAGES environmental variable.
480 The k8temp(4) driver has been renamed to amdtemp(4) since
481 support for K10 and K11 CPU families was added.
484 IGMPv3 and Source-Specific Multicast (SSM) have been merged
485 to the IPv4 stack. VIMAGE hooks are in but not yet used.
487 For kernel developers, the most important changes are that the
488 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
489 and this lock has been downgraded to a non-recursive mutex.
491 Transport protocols (UDP, Raw IP) are now responsible for filtering
492 inbound multicast traffic according to group membership and source
493 filters. The imo_multicast_filter() KPI exists for this purpose.
494 Transports which do not use multicast (SCTP, TCP) already reject
495 multicast by default. Forwarding and receive performance may improve
496 as a mutex acquisition is no longer needed in the ip_input()
497 low-level input path. in_addmulti() and in_delmulti() are shimmed
498 to new KPIs which exist to support SSM in-kernel.
500 For application developers, it is recommended that loopback of
501 multicast datagrams be disabled for best performance, as this
502 will still cause the lock to be taken for each looped-back
503 datagram transmission. The net.inet.ip.mcast.loop sysctl may
504 be tuned to 0 to disable loopback by default; it defaults to 1
505 to preserve the existing behaviour.
507 For systems administrators, to obtain best performance with
508 multicast reception and multiple groups, it is always recommended
509 that a card with a suitably precise hash filter is used. Hash
510 collisions will still result in the lock being taken within the
511 transport protocol input path to check group membership.
513 If deploying FreeBSD in an environment with IGMP snooping switches,
514 it is recommended that the net.inet.igmp.sendlocal sysctl remain
515 enabled; this forces 224.0.0.0/24 group membership to be announced
518 The size of 'struct igmpstat' has changed; netstat needs to be
519 recompiled to reflect this.
520 Bump __FreeBSD_version to 800070.
523 libusb20.so.1 is now installed as libusb.so.1 and the ports system
524 updated to use it. This requires a buildworld/installworld in order to
525 update the library and dependencies (usbconfig, etc). Its advisable to
526 rebuild all ports which uses libusb. More specific directions are given
527 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
528 libusb are no longer required and can be removed.
531 A workaround is committed to allow the creation of System V shared
532 memory segment of size > 2 GB on the 64-bit architectures.
533 Due to a limitation of the existing ABI, the shm_segsz member
534 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
535 wrong for large segments. Note that limits must be explicitly
536 raised to allow such segments to be created.
539 The layout of struct ifnet has changed, requiring a rebuild of all
540 network device driver modules.
543 The /dev handling for the new USB stack has changed, a
544 buildworld/installworld is required for libusb20.
547 The new USB2 stack has now been permanently moved in and all kernel and
548 module names reverted to their previous values (eg, usb, ehci, ohci,
549 ums, ...). The old usb stack can be compiled in by prefixing the name
550 with the letter 'o', the old usb modules have been removed.
551 Updating entry 20090216 for xorg and 20090215 for libmap may still
555 The rc.conf(5) option if_up_delay has been renamed to
556 defaultroute_delay to better reflect its purpose. If you have
557 customized this setting in /etc/rc.conf you need to update it to
561 xorg 7.4 wants to configure its input devices via hald which does not
562 yet work with USB2. If the keyboard/mouse does not work in xorg then
564 Option "AllowEmptyInput" "off"
565 to your ServerLayout section. This will cause X to use the configured
566 kbd and mouse sections from your xorg.conf.
569 The GENERIC kernels for all architectures now default to the new USB2
570 stack. No kernel config options or code have been removed so if a
571 problem arises please report it and optionally revert to the old USB
572 stack. If you are loading USB kernel modules or have a custom kernel
573 that includes GENERIC then ensure that usb names are also changed over,
574 eg uftdi -> usb2_serial_ftdi.
576 Older programs linked against the ports libusb 0.1 need to be
577 redirected to the new stack's libusb20. /etc/libmap.conf can
579 # Map old usb library to new one for usb2 stack
580 libusb-0.1.so.8 libusb20.so.1
583 All USB ethernet devices now attach as interfaces under the name ueN
584 (eg. ue0). This is to provide a predictable name as vendors often
585 change usb chipsets in a product without notice.
588 The ichsmb(4) driver has been changed to require SMBus slave
589 addresses be left-justified (xxxxxxx0b) rather than right-justified.
590 All of the other SMBus controller drivers require left-justified
591 slave addresses, so this change makes all the drivers provide the
595 INET6 statistics (struct ip6stat) was updated.
596 netstat(1) needs to be recompiled.
599 NTFS has been removed from GENERIC kernel on amd64 to match
600 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
601 will load ntfs.ko module automatically when NTFS support is
602 actually needed, unless ntfs.ko is not installed or security
603 level prohibits loading kernel modules. If either is the case,
604 "options NTFS" has to be added into kernel config.
607 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
608 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
609 800061. User space tools that rely on the size of struct tcpcb in
610 tcp_var.h (e.g. sockstat) need to be recompiled.
613 ng_tty(4) module updated to match the new TTY subsystem.
614 Due to API change, user-level applications must be updated.
615 New API support added to mpd5 CVS and expected to be present
616 in next mpd5.3 release.
619 With __FreeBSD_version 800060 the makefs tool is part of
620 the base system (it was a port).
623 The afdata and ifnet locks have been changed from mutexes to
624 rwlocks, network modules will need to be re-compiled.
627 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
628 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
629 The new code reduced struct rtentry{} by 16 bytes on 32-bit
630 architecture and 40 bytes on 64-bit architecture. The userland
631 applications "arp" and "ndp" have been updated accordingly.
632 The output from "netstat -r" shows only routing entries and
633 none of the L2 information.
636 __FreeBSD_version 800057 marks the switchover from the
637 binary ath hal to source code. Users must add the line:
639 options AH_SUPPORT_AR5416
641 to their kernel config files when specifying:
645 The ath_hal module no longer exists; the code is now compiled
646 together with the driver in the ath module. It is now
647 possible to tailor chip support (i.e. reduce the set of chips
648 and thereby the code size); consult ath_hal(4) for details.
651 __FreeBSD_version 800054 adds memory barriers to
652 <machine/atomic.h>, new interfaces to ifnet to facilitate
653 multiple hardware transmit queues for cards that support
654 them, and a lock-less ring-buffer implementation to
655 enable drivers to more efficiently manage queueing of
659 A new version of ZFS (version 13) has been merged to -HEAD.
660 This version has zpool attribute "listsnapshots" off by
661 default, which means "zfs list" does not show snapshots,
662 and is the same as Solaris behavior.
665 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
668 The uhci, ohci, ehci and slhci USB Host controller drivers have
669 been put into separate modules. If you load the usb module
670 separately through loader.conf you will need to load the
671 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
672 controller add the following to loader.conf:
678 The ABI used by the PMC toolset has changed. Please keep
679 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
683 atapci kernel module now includes only generic PCI ATA
684 driver. AHCI driver moved to ataahci kernel module.
685 All vendor-specific code moved into separate kernel modules:
686 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
687 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
688 atamarvell, atamicron, atanational, atanetcell, atanvidia,
689 atapromise, ataserverworks, atasiliconimage, atasis, atavia
692 The TTY subsystem of the kernel has been replaced by a new
693 implementation, which provides better scalability and an
694 improved driver model. Most common drivers have been migrated to
695 the new TTY subsystem, while others have not. The following
696 drivers have not yet been ported to the new TTY layer:
699 cy, digi, rc, rp, sio
705 ng_h4, ng_tty, ppp, sl, snp
707 Adding these drivers to your kernel configuration file shall
708 cause compilation to fail.
711 ntpd has been upgraded to 4.2.4p5.
714 OpenSSH has been upgraded to 5.1p1.
716 For many years, FreeBSD's version of OpenSSH preferred DSA
717 over RSA for host and user authentication keys. With this
718 upgrade, we've switched to the vendor's default of RSA over
719 DSA. This may cause upgraded clients to warn about unknown
720 host keys even for previously known hosts. Users should
721 follow the usual procedure for verifying host keys before
722 accepting the RSA key.
724 This can be circumvented by setting the "HostKeyAlgorithms"
725 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
728 Please note that the sequence of keys offered for
729 authentication has been changed as well. You may want to
730 specify IdentityFile in a different order to revert this
734 The sio(4) driver has been removed from the i386 and amd64
735 kernel configuration files. This means uart(4) is now the
736 default serial port driver on those platforms as well.
738 To prevent collisions with the sio(4) driver, the uart(4) driver
739 uses different names for its device nodes. This means the
740 onboard serial port will now most likely be called "ttyu0"
741 instead of "ttyd0". You may need to reconfigure applications to
742 use the new device names.
744 When using the serial port as a boot console, be sure to update
745 /boot/device.hints and /etc/ttys before booting the new kernel.
746 If you forget to do so, you can still manually specify the hints
747 at the loader prompt:
749 set hint.uart.0.at="isa"
750 set hint.uart.0.port="0x3F8"
751 set hint.uart.0.flags="0x10"
752 set hint.uart.0.irq="4"
756 The gpt(8) utility has been removed. Use gpart(8) to partition
760 The version that Linuxulator emulates was changed from 2.4.2
761 to 2.6.16. If you experience any problems with Linux binaries
762 please try to set sysctl compat.linux.osrelease to 2.4.2 and
763 if it fixes the problem contact emulation mailing list.
766 ISDN4BSD (I4B) was removed from the src tree. You may need to
767 update a your kernel configuration and remove relevant entries.
770 I have checked in code to support multiple routing tables.
771 See the man pages setfib(1) and setfib(2).
772 This is a hopefully backwards compatible version,
773 but to make use of it you need to compile your kernel
774 with options ROUTETABLES=2 (or more up to 16).
777 The 802.11 wireless support was redone to enable multi-bss
778 operation on devices that are capable. The underlying device
779 is no longer used directly but instead wlanX devices are
780 cloned with ifconfig. This requires changes to rc.conf files.
782 ifconfig_ath0="WPA DHCP"
785 ifconfig_wlan0="WPA DHCP"
786 see rc.conf(5) for more details. In addition, mergemaster of
787 /etc/rc.d is highly recommended. Simultaneous update of userland
788 and kernel wouldn't hurt either.
790 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
791 modules were merged into the base wlan module. All references
792 to these modules (e.g. in kernel config files) must be removed.
795 psm(4) has gained write(2) support in native operation level.
796 Arbitrary commands can be written to /dev/psm%d and status can
797 be read back from it. Therefore, an application is responsible
798 for status validation and error recovery. It is a no-op in
799 other operation levels.
802 Support for KSE threading has been removed from the kernel. To
803 run legacy applications linked against KSE libmap.conf may
804 be used. The following libmap.conf may be used to ensure
805 compatibility with any prior release:
807 libpthread.so.1 libthr.so.1
808 libpthread.so.2 libthr.so.2
809 libkse.so.3 libthr.so.3
812 The layout of struct vmspace has changed. This affects libkvm
813 and any executables that link against libkvm and use the
814 kvm_getprocs() function. In particular, but not exclusively,
815 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
816 The effects are minimal, but it's advisable to upgrade world
820 The latest em driver no longer has support in it for the
821 82575 adapter, this is now moved to the igb driver. The
822 split was done to make new features that are incompatible
823 with older hardware easier to do.
826 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
827 likewise the kernel option is now GEOM_LINUX_LVM.
830 The default NFS mount mode has changed from UDP to TCP for
831 increased reliability. If you rely on (insecurely) NFS
832 mounting across a firewall you may need to update your
836 Belatedly note the addition of m_collapse for compacting
840 The fts(3) structures have been changed to use adequate
841 integer types for their members and so to be able to cope
842 with huge file trees. The old fts(3) ABI is preserved
843 through symbol versioning in libc, so third-party binaries
844 using fts(3) should still work, although they will not take
845 advantage of the extended types. At the same time, some
846 third-party software might fail to build after this change
847 due to unportable assumptions made in its source code about
848 fts(3) structure members. Such software should be fixed
849 by its vendor or, in the worst case, in the ports tree.
850 FreeBSD_version 800015 marks this change for the unlikely
851 case that a portable fix is impossible.
854 To upgrade to -current after this date, you must be running
855 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
856 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
859 The ADAPTIVE_GIANT kernel option has been retired because its
860 functionality is the default now.
863 The AT keyboard emulation of sunkbd(4) has been turned on
864 by default. In order to make the special symbols of the Sun
865 keyboards driven by sunkbd(4) work under X these now have
866 to be configured the same way as Sun USB keyboards driven
867 by ukbd(4) (which also does AT keyboard emulation), f.e.:
869 Option "XkbLayout" "us"
870 Option "XkbRules" "xorg"
871 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
874 It has been decided that it is desirable to provide ABI
875 backwards compatibility to the FreeBSD 4/5/6 versions of the
876 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
877 broken with the introduction of PCI domain support (see the
878 20070930 entry). Unfortunately, this required the ABI of
879 PCIOCGETCONF to be broken again in order to be able to
880 provide backwards compatibility to the old version of that
881 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
882 again. As for prominent ports this affects neither pciutils
883 nor xorg-server this time, the hal port needs to be rebuilt
887 The misnamed kthread_create() and friends have been renamed
888 to kproc_create() etc. Many of the callers already
890 I will return kthread_create() and friends in a while
891 with implementations that actually create threads, not procs.
892 Renaming corresponds with version 800002.
901 Avoid using make -j when upgrading. While generally safe, there are
902 sometimes problems using -j to upgrade. If your upgrade fails with
903 -j, please try again without -j. From time to time in the past there
904 have been problems using -j with buildworld and/or installworld. This
905 is especially true when upgrading between "distant" versions (eg one
906 that cross a major release boundary or several minor releases, or when
907 several months have passed on the -current branch).
909 Sometimes, obscure build problems are the result of environment
910 poisoning. This can happen because the make utility reads its
911 environment when searching for values for global variables. To run
912 your build attempts in an "environmental clean room", prefix all make
913 commands with 'env -i '. See the env(1) manual page for more details.
915 When upgrading from one major version to another it is generally best
916 to upgrade to the latest code in the currently installed branch first,
917 then do an upgrade to the new branch. This is the best-tested upgrade
918 path, and has the highest probability of being successful. Please try
919 this approach before reporting problems with a major version upgrade.
923 If you are updating from a prior version of FreeBSD (even one just
924 a few days old), you should follow this procedure. It is the most
925 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
927 make kernel-toolchain
928 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
929 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
931 To test a kernel once
932 ---------------------
933 If you just want to boot a kernel once (because you are not sure
934 if it works, or if you want to boot a known bad kernel to provide
935 debugging information) run
936 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
937 nextboot -k testkernel
939 To just build a kernel when you know that it won't mess you up
940 --------------------------------------------------------------
941 This assumes you are already running a CURRENT system. Replace
942 ${arch} with the architecture of your machine (e.g. "i386",
943 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
945 cd src/sys/${arch}/conf
946 config KERNEL_NAME_HERE
947 cd ../compile/KERNEL_NAME_HERE
952 If this fails, go to the "To build a kernel" section.
954 To rebuild everything and install it on the current system.
955 -----------------------------------------------------------
956 # Note: sometimes if you are running current you gotta do more than
957 # is listed here if you are upgrading from a really old current.
959 <make sure you have good level 0 dumps>
961 make kernel KERNCONF=YOUR_KERNEL_HERE
963 <reboot in single user> [3]
971 To cross-install current onto a separate partition
972 --------------------------------------------------
973 # In this approach we use a separate partition to hold
974 # current's root, 'usr', and 'var' directories. A partition
975 # holding "/", "/usr" and "/var" should be about 2GB in
978 <make sure you have good level 0 dumps>
981 make buildkernel KERNCONF=YOUR_KERNEL_HERE
982 <maybe newfs current's root partition>
983 <mount current's root partition on directory ${CURRENT_ROOT}>
984 make installworld DESTDIR=${CURRENT_ROOT}
985 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
986 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
987 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
988 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
989 <reboot into current>
990 <do a "native" rebuild/install as described in the previous section>
991 <maybe install compatibility libraries from ports/misc/compat*>
995 To upgrade in-place from 8.x-stable to current
996 ----------------------------------------------
997 <make sure you have good level 0 dumps>
999 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1001 <reboot in single user> [3]
1008 Make sure that you've read the UPDATING file to understand the
1009 tweaks to various things you need. At this point in the life
1010 cycle of current, things change often and you are on your own
1011 to cope. The defaults can also change, so please read ALL of
1012 the UPDATING entries.
1014 Also, if you are tracking -current, you must be subscribed to
1015 freebsd-current@freebsd.org. Make sure that before you update
1016 your sources that you have read and understood all the recent
1017 messages there. If in doubt, please track -stable which has
1018 much fewer pitfalls.
1020 [1] If you have third party modules, such as vmware, you
1021 should disable them at this point so they don't crash your
1024 [3] From the bootblocks, boot -s, and then do
1029 adjkerntz -i # if CMOS is wall time
1030 Also, when doing a major release upgrade, it is required that
1031 you boot into single user mode to do the installworld.
1033 [4] Note: This step is non-optional. Failure to do this step
1034 can result in a significant reduction in the functionality of the
1035 system. Attempting to do it by hand is not recommended and those
1036 that pursue this avenue should read this file carefully, as well
1037 as the archives of freebsd-current and freebsd-hackers mailing lists
1038 for potential gotchas.
1040 [5] Usually this step is a noop. However, from time to time
1041 you may need to do this if you get unknown user in the following
1042 step. It never hurts to do it all the time. You may need to
1043 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1044 install) after the buildworld before this step if you last updated
1045 from current before 20020224 or from -stable before 20020408.
1047 [8] In order to have a kernel that can run the 4.x binaries needed to
1048 do an installworld, you must include the COMPAT_FREEBSD4 option in
1049 your kernel. Failure to do so may leave you with a system that is
1050 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1051 required to run the 5.x binaries on more recent kernels. And so on
1052 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1054 Make sure that you merge any new devices from GENERIC since the
1055 last time you updated your kernel config file.
1057 [9] When checking out sources, you must include the -P flag to have
1058 cvs prune empty directories.
1060 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1061 "?=" instead of the "=" assignment operator, so that buildworld can
1062 override the CPUTYPE if it needs to.
1064 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1065 not on the command line, or in /etc/make.conf. buildworld will
1066 warn if it is improperly defined.
1069 This file contains a list, in reverse chronological order, of major
1070 breakages in tracking -current. Not all things will be listed here,
1071 and it only starts on October 16, 2004. Updating files can found in
1072 previous releases if your system is older than this.
1074 Copyright information:
1076 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1078 Redistribution, publication, translation and use, with or without
1079 modification, in full or in part, in any form or format of this
1080 document are permitted without further permission from the author.
1082 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1083 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1084 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1085 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1086 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1087 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1088 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1089 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1090 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1091 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1092 POSSIBILITY OF SUCH DAMAGE.
1094 Contact Warner Losh if you have any questions about your use of