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