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