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