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