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