1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 Items affecting the ports and packages system can be found in
10 /usr/ports/UPDATING. Please read that file before running portupgrade.
12 NOTE TO PEOPLE WHO THINK THAT FreeBSD 9.x IS SLOW:
13 FreeBSD 9.x has many debugging features turned on, in both the kernel
14 and userland. These features attempt to detect incorrect use of
15 system primitives, and encourage loud failure through extra sanity
16 checking and fail stop semantics. They also substantially impact
17 system performance. If you want to do performance measurement,
18 benchmarking, and optimization, you'll want to turn them off. This
19 includes various WITNESS- related kernel options, INVARIANTS, malloc
20 debugging flags in userland, and various verbose features in the
21 kernel. Many developers choose to disable these features on build
22 machines to maximize performance. (To disable malloc debugging, run
23 ln -s aj /etc/malloc.conf.)
26 The rc.d/network_ipv6, IPv6 configuration script has been integrated
27 into rc.d/netif. The changes are the following:
29 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
30 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
31 Note that both variables need the "inet6" keyword at the head.
33 Do not set $ipv6_network_interfaces manually if you do not
34 understand what you are doing. It is not needed in most cases.
36 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
39 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
40 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
42 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
43 all configured interfaces have "inet6 accept_rtadv" in the
44 $ifconfig_IF_ipv6. These are for backward compatibility.
46 3. A new variable $ipv6_prefer has been added. If NO, IPv6
47 functionality of interfaces with no corresponding
48 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
49 and the default address selection policy of ip6addrctl(8)
50 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
51 Note that if you want to configure IPv6 functionality on the
52 disabled interfaces after boot, first you need to clear the flag by
53 using ifconfig(8) like:
55 ifconfig em0 inet6 -ifdisabled
57 If YES, the default address selection policy is set as
60 The default value of $ipv6_prefer is NO.
62 4. If your system need to receive Router Advertisement messages,
63 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
64 scripts automatically invoke rtsol(8) when the interface becomes
65 UP. The Router Advertisement messages are used for SLAAC
66 (State-Less Address AutoConfiguration).
69 802.11s D3.03 support was committed. This is incompatible with the
70 previous code, which was based on D3.0.
73 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
74 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
75 control whether accepting Router Advertisement messages or not.
76 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
77 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
78 The ifconfig(8) utility now supports these flags.
81 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
82 mount(8) and -a option for df(1) to see them.
85 The old tunable hw.bus.devctl_disable has been superseded by
86 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
87 replaced by hw.bus.devctl_queue=0. The default for this new tunable
91 Remove the option STOP_NMI. The default action is now to use NMI only
92 for KDB via the newly introduced function stop_cpus_hard() and
93 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
96 The stable/8 branch created in subversion. This corresponds to the
97 RELENG_8 branch in CVS.
100 Bump the shared library version numbers for all libraries that do not
101 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
102 __FreeBSD_version to 800105.
105 Due to changes in the implementation of virtual network stack support,
106 all network-related kernel modules must be recompiled. As this change
107 breaks the ABI, bump __FreeBSD_version to 800104.
110 The TOE interface to the TCP syncache has been modified to remove
111 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
112 The cxgb driver is the only TOE consumer affected by this change, and
113 needs to be recompiled along with the kernel. As this change breaks
114 the ABI, bump __FreeBSD_version to 800103.
117 Padding has been added to struct tcpcb, sackhint and tcpstat in
118 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
119 maintainig the ABI. However, this change breaks the ABI, so bump
120 __FreeBSD_version to 800102. User space tools that rely on the size of
121 any of these structs (e.g. sockstat) need to be recompiled.
124 The NFS_LEGACYRPC option has been removed along with the old kernel
125 RPC implementation that this option selected. Kernel configurations
126 may need to be adjusted.
129 The network interface device nodes at /dev/net/<interface> have been
130 removed. All ioctl operations can be performed the normal way using
131 routing sockets. The kqueue functionality can generally be replaced
132 with routing sockets.
135 The documentation from the FreeBSD Documentation Project (Handbook,
136 FAQ, etc.) is now installed via packages by sysinstall(8) and under
137 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
140 The ABI of various structures related to the SYSV IPC API have been
141 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
142 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
146 Layout of struct vnet has changed as routing related variables were
147 moved to their own Vimage module. Modules need to be recompiled. Bump
148 __FreeBSD_version to 800099.
151 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
152 respectively. As long as no more than 16 groups per process are used,
153 no changes should be visible. When more than 16 groups are used, old
154 binaries may fail if they call getgroups() or getgrouplist() with
155 statically sized storage. Recompiling will work around this, but
156 applications should be modified to use dynamically allocated storage
157 for group arrays as POSIX.1-2008 does not cap an implementation's
158 number of supported groups at NGROUPS_MAX+1 as previous versions did.
160 NFS and portalfs mounts may also be affected as the list of groups is
161 truncated to 16. Users of NFS who use more than 16 groups, should
162 take care that negative group permissions are not used on the exported
163 file systems as they will not be reliable unless a GSSAPI based
164 authentication method is used.
167 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
168 option compiles in the support for adaptive spinning for lockmgrs
169 which want to enable it. The lockinit() function now accepts the flag
170 LK_ADAPTIVE in order to make the lock object subject to adaptive
171 spinning when both held in write and read mode.
174 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
175 changed. User applications that use this ioctl need to be rebuilt.
178 The layout of struct thread has changed. Kernel and modules need to
182 The layout of structs ifnet, domain, protosw and vnet_net has changed.
183 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
186 window(1) has been removed from the base system. It can now be
187 installed from ports. The port is called misc/window.
190 The way we are storing and accessing `routing table' entries has
191 changed. Programs reading the FIB, like netstat, need to be
195 A new netisr implementation has been added for FreeBSD 8. Network
196 file system modules, such as igmp, ipdivert, and others, should be
198 Bump __FreeBSD_version to 800096.
201 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
205 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
206 Bump __FreeBSD_version to 800094.
209 Add mnt_xflag field to 'struct mount'. File system modules need to be
211 Bump __FreeBSD_version to 800093.
214 The compiling option ADAPTIVE_SX has been retired while it has been
215 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
216 The KPI for sx_init_flags() changes as accepting flags:
217 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
218 been introduced in order to handle the reversed logic.
219 Bump __FreeBSD_version to 800092.
222 Add support for hierarchical jails. Remove global securelevel.
223 Bump __FreeBSD_version to 800091.
226 The layout of struct vnet_net has changed, therefore modules
228 Bump __FreeBSD_version to 800090.
231 The newly imported zic(8) produces a new format in the output. Please
232 run tzsetup(8) to install the newly created data to /etc/localtime.
235 The sysctl tree for the usb stack has renamed from hw.usb2.* to
236 hw.usb.* and is now consistent again with previous releases.
239 802.11 monitor mode support was revised and driver api's were changed.
240 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
241 of DLT_IEEE802_11. No user-visible data structures were changed but
242 applications that use DLT_IEEE802_11 may require changes.
243 Bump __FreeBSD_version to 800088.
246 The layout of the following structs has changed: sysctl_oid,
247 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
248 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
249 panics may be experienced. World rebuild is required for
250 correctly checking networking state from userland.
251 Bump __FreeBSD_version to 800085.
254 MLDv2 and Source-Specific Multicast (SSM) have been merged
255 to the IPv6 stack. VIMAGE hooks are in but not yet used.
256 The implementation of SSM within FreeBSD's IPv6 stack closely
257 follows the IPv4 implementation.
259 For kernel developers:
261 * The most important changes are that the ip6_output() and
262 ip6_input() paths no longer take the IN6_MULTI_LOCK,
263 and this lock has been downgraded to a non-recursive mutex.
265 * As with the changes to the IPv4 stack to support SSM, filtering
266 of inbound multicast traffic must now be performed by transport
267 protocols within the IPv6 stack. This does not apply to TCP and
268 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
270 * The KPIs used by IPv6 multicast are similar to those used by
271 the IPv4 stack, with the following differences:
272 * im6o_mc_filter() is analogous to imo_multicast_filter().
273 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
274 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
275 * IN6_LOOKUP_MULTI() has been deprecated and removed.
276 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
277 for MLDv1 have an additional 'timer' argument which is used to
278 jitter the initial membership report for the solicited-node
279 multicast membership on-link.
280 * This is not strictly needed for MLDv2, which already jitters
281 its report transmissions. However, the 'timer' argument is
282 preserved in case MLDv1 is active on the interface.
284 * The KAME linked-list based IPv6 membership implementation has
285 been refactored to use a vector similar to that used by the IPv4
287 Code which maintains a list of its own multicast memberships
288 internally, e.g. carp, has been updated to reflect the new
291 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
292 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
293 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
294 implementation constraint which needs to be addressed in HEAD.
296 For application developers:
298 * The changes are broadly similar to those made for the IPv4
301 * The use of IPv4 and IPv6 multicast socket options on the same
302 socket, using mapped addresses, HAS NOT been tested or supported.
304 * There are a number of issues with the implementation of various
305 IPv6 multicast APIs which need to be resolved in the API surface
306 before the implementation is fully compatible with KAME userland
307 use, and these are mostly to do with interface index treatment.
309 * The literature available discusses the use of either the delta / ASM
310 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
311 using setsourcefilter(3)/getsourcefilter(3). For more information
312 please refer to RFC 3768, 'Socket Interface Extensions for
313 Multicast Source Filters'.
315 * Applications which use the published RFC 3678 APIs should be fine.
317 For systems administrators:
319 * The mtest(8) utility has been refactored to support IPv6, in
320 addition to IPv4. Interface addresses are no longer accepted
321 as arguments, their names must be used instead. The utility
322 will map the interface name to its first IPv4 address as
323 returned by getifaddrs(3).
325 * The ifmcstat(8) utility has also been updated to print the MLDv2
326 endpoint state and source filter lists via sysctl(3).
328 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
329 loopback of IPv6 multicast datagrams by default; it defaults to 1
330 to preserve the existing behaviour. Disabling multicast loopback is
331 recommended for optimal system performance.
333 * The IPv6 MROUTING code has been changed to examine this sysctl
334 instead of attempting to perform a group lookup before looping
335 back forwarded datagrams.
337 Bump __FreeBSD_version to 800084.
340 Implement low-level Bluetooth HCI API.
341 Bump __FreeBSD_version to 800083.
344 The layout of struct malloc_type, used by modules to register new
345 memory allocation types, has changed. Most modules will need to
346 be rebuilt or panics may be experienced.
347 Bump __FreeBSD_version to 800081.
350 Anticipate overflowing inp_flags - add inp_flags2.
351 This changes most offsets in inpcb, so checking v4 connection
352 state will require a world rebuild.
353 Bump __FreeBSD_version to 800080.
356 Add an llentry to struct route and struct route_in6. Modules
357 embedding a struct route will need to be recompiled.
358 Bump __FreeBSD_version to 800079.
361 The size of rt_metrics_lite and by extension rtentry has changed.
362 Networking administration apps will need to be recompiled.
363 The route command now supports show as an alias for get, weighting
364 of routes, sticky and nostick flags to alter the behavior of stateful
366 Bump __FreeBSD_version to 800078.
369 Do not use Giant for kbdmux(4) locking. This is wrong and
370 apparently causing more problems than it solves. This will
371 re-open the issue where interrupt handlers may race with
372 kbdmux(4) in polling mode. Typical symptoms include (but
373 not limited to) duplicated and/or missing characters when
374 low level console functions (such as gets) are used while
375 interrupts are enabled (for example geli password prompt,
376 mountroot prompt etc.). Disabling kbdmux(4) may help.
379 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
380 kernel modules referencing any of the above need to be recompiled.
381 Bump __FreeBSD_version to 800075.
384 GEOM_PART has become the default partition slicer for storage devices,
385 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
386 introduces some changes:
388 MSDOS/EBR: the devices created from MSDOS extended partition entries
389 (EBR) can be named differently than with GEOM_MBR and are now symlinks
390 to devices with offset-based names. fstabs may need to be modified.
392 BSD: the "geometry does not match label" warning is harmless in most
393 cases but it points to problems in file system misalignment with
394 disk geometry. The "c" partition is now implicit, covers the whole
395 top-level drive and cannot be (mis)used by users.
397 General: Kernel dumps are now not allowed to be written to devices
398 whose partition types indicate they are meant to be used for file
399 systems (or, in case of MSDOS partitions, as something else than
402 Most of these changes date approximately from 200812.
405 The uscanner(4) driver has been removed from the kernel. This follows
406 Linux removing theirs in 2.6 and making libusb the default interface
410 The multicast forwarding code has been cleaned up. netstat(1)
411 only relies on KVM now for printing bandwidth upcall meters.
412 The IPv4 and IPv6 modules are split into ip_mroute_mod and
413 ip6_mroute_mod respectively. The config(5) options for statically
414 compiling this code remain the same, i.e. 'options MROUTING'.
417 Support for the IFF_NEEDSGIANT network interface flag has been
418 removed, which means that non-MPSAFE network device drivers are no
419 longer supported. In particular, if_ar, if_sr, and network device
420 drivers from the old (legacy) USB stack can no longer be built or
424 POSIX.1 Native Language Support (NLS) has been enabled in libc and
425 a bunch of new language catalog files have also been added.
426 This means that some common libc messages are now localized and
427 they depend on the LC_MESSAGES environmental variable.
430 The k8temp(4) driver has been renamed to amdtemp(4) since
431 support for K10 and K11 CPU families was added.
434 IGMPv3 and Source-Specific Multicast (SSM) have been merged
435 to the IPv4 stack. VIMAGE hooks are in but not yet used.
437 For kernel developers, the most important changes are that the
438 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
439 and this lock has been downgraded to a non-recursive mutex.
441 Transport protocols (UDP, Raw IP) are now responsible for filtering
442 inbound multicast traffic according to group membership and source
443 filters. The imo_multicast_filter() KPI exists for this purpose.
444 Transports which do not use multicast (SCTP, TCP) already reject
445 multicast by default. Forwarding and receive performance may improve
446 as a mutex acquisition is no longer needed in the ip_input()
447 low-level input path. in_addmulti() and in_delmulti() are shimmed
448 to new KPIs which exist to support SSM in-kernel.
450 For application developers, it is recommended that loopback of
451 multicast datagrams be disabled for best performance, as this
452 will still cause the lock to be taken for each looped-back
453 datagram transmission. The net.inet.ip.mcast.loop sysctl may
454 be tuned to 0 to disable loopback by default; it defaults to 1
455 to preserve the existing behaviour.
457 For systems administrators, to obtain best performance with
458 multicast reception and multiple groups, it is always recommended
459 that a card with a suitably precise hash filter is used. Hash
460 collisions will still result in the lock being taken within the
461 transport protocol input path to check group membership.
463 If deploying FreeBSD in an environment with IGMP snooping switches,
464 it is recommended that the net.inet.igmp.sendlocal sysctl remain
465 enabled; this forces 224.0.0.0/24 group membership to be announced
468 The size of 'struct igmpstat' has changed; netstat needs to be
469 recompiled to reflect this.
470 Bump __FreeBSD_version to 800070.
473 libusb20.so.1 is now installed as libusb.so.1 and the ports system
474 updated to use it. This requires a buildworld/installworld in order to
475 update the library and dependencies (usbconfig, etc). Its advisable to
476 rebuild all ports which uses libusb. More specific directions are given
477 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
478 libusb are no longer required and can be removed.
481 A workaround is committed to allow the creation of System V shared
482 memory segment of size > 2 GB on the 64-bit architectures.
483 Due to a limitation of the existing ABI, the shm_segsz member
484 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
485 wrong for large segments. Note that limits must be explicitly
486 raised to allow such segments to be created.
489 The layout of struct ifnet has changed, requiring a rebuild of all
490 network device driver modules.
493 The /dev handling for the new USB stack has changed, a
494 buildworld/installworld is required for libusb20.
497 The new USB2 stack has now been permanently moved in and all kernel and
498 module names reverted to their previous values (eg, usb, ehci, ohci,
499 ums, ...). The old usb stack can be compiled in by prefixing the name
500 with the letter 'o', the old usb modules have been removed.
501 Updating entry 20090216 for xorg and 20090215 for libmap may still
505 The rc.conf(5) option if_up_delay has been renamed to
506 defaultroute_delay to better reflect its purpose. If you have
507 customized this setting in /etc/rc.conf you need to update it to
511 xorg 7.4 wants to configure its input devices via hald which does not
512 yet work with USB2. If the keyboard/mouse does not work in xorg then
514 Option "AllowEmptyInput" "off"
515 to your ServerLayout section. This will cause X to use the configured
516 kbd and mouse sections from your xorg.conf.
519 The GENERIC kernels for all architectures now default to the new USB2
520 stack. No kernel config options or code have been removed so if a
521 problem arises please report it and optionally revert to the old USB
522 stack. If you are loading USB kernel modules or have a custom kernel
523 that includes GENERIC then ensure that usb names are also changed over,
524 eg uftdi -> usb2_serial_ftdi.
526 Older programs linked against the ports libusb 0.1 need to be
527 redirected to the new stack's libusb20. /etc/libmap.conf can
529 # Map old usb library to new one for usb2 stack
530 libusb-0.1.so.8 libusb20.so.1
533 The ichsmb(4) driver has been changed to require SMBus slave
534 addresses be left-justified (xxxxxxx0b) rather than right-justified.
535 All of the other SMBus controller drivers require left-justified
536 slave addresses, so this change makes all the drivers provide the
540 INET6 statistics (struct ip6stat) was updated.
541 netstat(1) needs to be recompiled.
544 NTFS has been removed from GENERIC kernel on amd64 to match
545 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
546 will load ntfs.ko module automatically when NTFS support is
547 actually needed, unless ntfs.ko is not installed or security
548 level prohibits loading kernel modules. If either is the case,
549 "options NTFS" has to be added into kernel config.
552 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
553 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
554 800061. User space tools that rely on the size of struct tcpcb in
555 tcp_var.h (e.g. sockstat) need to be recompiled.
558 ng_tty(4) module updated to match the new TTY subsystem.
559 Due to API change, user-level applications must be updated.
560 New API support added to mpd5 CVS and expected to be present
561 in next mpd5.3 release.
564 With __FreeBSD_version 800060 the makefs tool is part of
565 the base system (it was a port).
568 The afdata and ifnet locks have been changed from mutexes to
569 rwlocks, network modules will need to be re-compiled.
572 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
573 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
574 The new code reduced struct rtentry{} by 16 bytes on 32-bit
575 architecture and 40 bytes on 64-bit architecture. The userland
576 applications "arp" and "ndp" have been updated accordingly.
577 The output from "netstat -r" shows only routing entries and
578 none of the L2 information.
581 __FreeBSD_version 800057 marks the switchover from the
582 binary ath hal to source code. Users must add the line:
584 options AH_SUPPORT_AR5416
586 to their kernel config files when specifying:
590 The ath_hal module no longer exists; the code is now compiled
591 together with the driver in the ath module. It is now
592 possible to tailor chip support (i.e. reduce the set of chips
593 and thereby the code size); consult ath_hal(4) for details.
596 __FreeBSD_version 800054 adds memory barriers to
597 <machine/atomic.h>, new interfaces to ifnet to facilitate
598 multiple hardware transmit queues for cards that support
599 them, and a lock-less ring-buffer implementation to
600 enable drivers to more efficiently manage queueing of
604 A new version of ZFS (version 13) has been merged to -HEAD.
605 This version has zpool attribute "listsnapshots" off by
606 default, which means "zfs list" does not show snapshots,
607 and is the same as Solaris behavior.
610 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
613 The uhci, ohci, ehci and slhci USB Host controller drivers have
614 been put into separate modules. If you load the usb module
615 separately through loader.conf you will need to load the
616 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
617 controller add the following to loader.conf:
623 The ABI used by the PMC toolset has changed. Please keep
624 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
628 The TTY subsystem of the kernel has been replaced by a new
629 implementation, which provides better scalability and an
630 improved driver model. Most common drivers have been migrated to
631 the new TTY subsystem, while others have not. The following
632 drivers have not yet been ported to the new TTY layer:
635 cy, digi, rc, rp, sio
641 ng_h4, ng_tty, ppp, sl, snp
643 Adding these drivers to your kernel configuration file shall
644 cause compilation to fail.
647 ntpd has been upgraded to 4.2.4p5.
650 OpenSSH has been upgraded to 5.1p1.
652 For many years, FreeBSD's version of OpenSSH preferred DSA
653 over RSA for host and user authentication keys. With this
654 upgrade, we've switched to the vendor's default of RSA over
655 DSA. This may cause upgraded clients to warn about unknown
656 host keys even for previously known hosts. Users should
657 follow the usual procedure for verifying host keys before
658 accepting the RSA key.
660 This can be circumvented by setting the "HostKeyAlgorithms"
661 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
664 Please note that the sequence of keys offered for
665 authentication has been changed as well. You may want to
666 specify IdentityFile in a different order to revert this
670 The sio(4) driver has been removed from the i386 and amd64
671 kernel configuration files. This means uart(4) is now the
672 default serial port driver on those platforms as well.
674 To prevent collisions with the sio(4) driver, the uart(4) driver
675 uses different names for its device nodes. This means the
676 onboard serial port will now most likely be called "ttyu0"
677 instead of "ttyd0". You may need to reconfigure applications to
678 use the new device names.
680 When using the serial port as a boot console, be sure to update
681 /boot/device.hints and /etc/ttys before booting the new kernel.
682 If you forget to do so, you can still manually specify the hints
683 at the loader prompt:
685 set hint.uart.0.at="isa"
686 set hint.uart.0.port="0x3F8"
687 set hint.uart.0.flags="0x10"
688 set hint.uart.0.irq="4"
692 The gpt(8) utility has been removed. Use gpart(8) to partition
696 The version that Linuxulator emulates was changed from 2.4.2
697 to 2.6.16. If you experience any problems with Linux binaries
698 please try to set sysctl compat.linux.osrelease to 2.4.2 and
699 if it fixes the problem contact emulation mailing list.
702 ISDN4BSD (I4B) was removed from the src tree. You may need to
703 update a your kernel configuration and remove relevant entries.
706 I have checked in code to support multiple routing tables.
707 See the man pages setfib(1) and setfib(2).
708 This is a hopefully backwards compatible version,
709 but to make use of it you need to compile your kernel
710 with options ROUTETABLES=2 (or more up to 16).
713 The 802.11 wireless support was redone to enable multi-bss
714 operation on devices that are capable. The underlying device
715 is no longer used directly but instead wlanX devices are
716 cloned with ifconfig. This requires changes to rc.conf files.
718 ifconfig_ath0="WPA DHCP"
721 ifconfig_wlan0="WPA DHCP"
722 see rc.conf(5) for more details. In addition, mergemaster of
723 /etc/rc.d is highly recommended. Simultaneous update of userland
724 and kernel wouldn't hurt either.
726 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
727 modules were merged into the base wlan module. All references
728 to these modules (e.g. in kernel config files) must be removed.
731 psm(4) has gained write(2) support in native operation level.
732 Arbitrary commands can be written to /dev/psm%d and status can
733 be read back from it. Therefore, an application is responsible
734 for status validation and error recovery. It is a no-op in
735 other operation levels.
738 Support for KSE threading has been removed from the kernel. To
739 run legacy applications linked against KSE libmap.conf may
740 be used. The following libmap.conf may be used to ensure
741 compatibility with any prior release:
743 libpthread.so.1 libthr.so.1
744 libpthread.so.2 libthr.so.2
745 libkse.so.3 libthr.so.3
748 The layout of struct vmspace has changed. This affects libkvm
749 and any executables that link against libkvm and use the
750 kvm_getprocs() function. In particular, but not exclusively,
751 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
752 The effects are minimal, but it's advisable to upgrade world
756 The latest em driver no longer has support in it for the
757 82575 adapter, this is now moved to the igb driver. The
758 split was done to make new features that are incompatible
759 with older hardware easier to do.
762 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
763 likewise the kernel option is now GEOM_LINUX_LVM.
766 The default NFS mount mode has changed from UDP to TCP for
767 increased reliability. If you rely on (insecurely) NFS
768 mounting across a firewall you may need to update your
772 Belatedly note the addition of m_collapse for compacting
776 The fts(3) structures have been changed to use adequate
777 integer types for their members and so to be able to cope
778 with huge file trees. The old fts(3) ABI is preserved
779 through symbol versioning in libc, so third-party binaries
780 using fts(3) should still work, although they will not take
781 advantage of the extended types. At the same time, some
782 third-party software might fail to build after this change
783 due to unportable assumptions made in its source code about
784 fts(3) structure members. Such software should be fixed
785 by its vendor or, in the worst case, in the ports tree.
786 FreeBSD_version 800015 marks this change for the unlikely
787 case that a portable fix is impossible.
790 To upgrade to -current after this date, you must be running
791 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
792 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
795 The ADAPTIVE_GIANT kernel option has been retired because its
796 functionality is the default now.
799 The AT keyboard emulation of sunkbd(4) has been turned on
800 by default. In order to make the special symbols of the Sun
801 keyboards driven by sunkbd(4) work under X these now have
802 to be configured the same way as Sun USB keyboards driven
803 by ukbd(4) (which also does AT keyboard emulation), f.e.:
805 Option "XkbLayout" "us"
806 Option "XkbRules" "xorg"
807 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
810 It has been decided that it is desirable to provide ABI
811 backwards compatibility to the FreeBSD 4/5/6 versions of the
812 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
813 broken with the introduction of PCI domain support (see the
814 20070930 entry). Unfortunately, this required the ABI of
815 PCIOCGETCONF to be broken again in order to be able to
816 provide backwards compatibility to the old version of that
817 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
818 again. As for prominent ports this affects neither pciutils
819 nor xorg-server this time, the hal port needs to be rebuilt
823 The misnamed kthread_create() and friends have been renamed
824 to kproc_create() etc. Many of the callers already
826 I will return kthread_create() and friends in a while
827 with implementations that actually create threads, not procs.
828 Renaming corresponds with version 800002.
837 Avoid using make -j when upgrading. While generally safe, there are
838 sometimes problems using -j to upgrade. If your upgrade fails with
839 -j, please try again wtihout -j. From time to time in the past there
840 have been problems using -j with buildworld and/or installworld. This
841 is especially true when upgrading between "distant" versions (eg one
842 that cross a major release boundary or several minor releases, or when
843 several months have passed on the -current branch).
845 Sometimes, obscure build problems are the result of environment
846 poisoning. This can happen because the make utility reads its
847 environment when searching for values for global variables. To run
848 your build attempts in an "environmental clean room", prefix all make
849 commands with 'env -i '. See the env(1) manual page for more details.
851 When upgrading from one major version to another it is generally best
852 to upgrade to the latest code in the currently installed branch first,
853 then do an upgrade to the new branch. This is the best-tested upgrade
854 path, and has the highest probability of being successful. Please try
855 this approach before reporting problems with a major version upgrade.
859 If you are updating from a prior version of FreeBSD (even one just
860 a few days old), you should follow this procedure. It is the most
861 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
863 make kernel-toolchain
864 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
865 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
867 To test a kernel once
868 ---------------------
869 If you just want to boot a kernel once (because you are not sure
870 if it works, or if you want to boot a known bad kernel to provide
871 debugging information) run
872 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
873 nextboot -k testkernel
875 To just build a kernel when you know that it won't mess you up
876 --------------------------------------------------------------
877 This assumes you are already running a CURRENT system. Replace
878 ${arch} with the architecture of your machine (e.g. "i386",
879 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
881 cd src/sys/${arch}/conf
882 config KERNEL_NAME_HERE
883 cd ../compile/KERNEL_NAME_HERE
888 If this fails, go to the "To build a kernel" section.
890 To rebuild everything and install it on the current system.
891 -----------------------------------------------------------
892 # Note: sometimes if you are running current you gotta do more than
893 # is listed here if you are upgrading from a really old current.
895 <make sure you have good level 0 dumps>
897 make kernel KERNCONF=YOUR_KERNEL_HERE
899 <reboot in single user> [3]
907 To cross-install current onto a separate partition
908 --------------------------------------------------
909 # In this approach we use a separate partition to hold
910 # current's root, 'usr', and 'var' directories. A partition
911 # holding "/", "/usr" and "/var" should be about 2GB in
914 <make sure you have good level 0 dumps>
917 make buildkernel KERNCONF=YOUR_KERNEL_HERE
918 <maybe newfs current's root partition>
919 <mount current's root partition on directory ${CURRENT_ROOT}>
920 make installworld DESTDIR=${CURRENT_ROOT}
921 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
922 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
923 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
924 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
925 <reboot into current>
926 <do a "native" rebuild/install as described in the previous section>
927 <maybe install compatibility libraries from ports/misc/compat*>
931 To upgrade in-place from 8.x-stable to current
932 ----------------------------------------------
933 <make sure you have good level 0 dumps>
935 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
937 <reboot in single user> [3]
944 Make sure that you've read the UPDATING file to understand the
945 tweaks to various things you need. At this point in the life
946 cycle of current, things change often and you are on your own
947 to cope. The defaults can also change, so please read ALL of
948 the UPDATING entries.
950 Also, if you are tracking -current, you must be subscribed to
951 freebsd-current@freebsd.org. Make sure that before you update
952 your sources that you have read and understood all the recent
953 messages there. If in doubt, please track -stable which has
956 [1] If you have third party modules, such as vmware, you
957 should disable them at this point so they don't crash your
960 [3] From the bootblocks, boot -s, and then do
965 adjkerntz -i # if CMOS is wall time
966 Also, when doing a major release upgrade, it is required that
967 you boot into single user mode to do the installworld.
969 [4] Note: This step is non-optional. Failure to do this step
970 can result in a significant reduction in the functionality of the
971 system. Attempting to do it by hand is not recommended and those
972 that pursue this avenue should read this file carefully, as well
973 as the archives of freebsd-current and freebsd-hackers mailing lists
974 for potential gotchas.
976 [5] Usually this step is a noop. However, from time to time
977 you may need to do this if you get unknown user in the following
978 step. It never hurts to do it all the time. You may need to
979 install a new mergemaster (cd src/usr.sbin/mergemaster && make
980 install) after the buildworld before this step if you last updated
981 from current before 20020224 or from -stable before 20020408.
983 [8] In order to have a kernel that can run the 4.x binaries needed to
984 do an installworld, you must include the COMPAT_FREEBSD4 option in
985 your kernel. Failure to do so may leave you with a system that is
986 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
987 required to run the 5.x binaries on more recent kernels. And so on
988 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
990 Make sure that you merge any new devices from GENERIC since the
991 last time you updated your kernel config file.
993 [9] When checking out sources, you must include the -P flag to have
994 cvs prune empty directories.
996 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
997 "?=" instead of the "=" assignment operator, so that buildworld can
998 override the CPUTYPE if it needs to.
1000 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1001 not on the command line, or in /etc/make.conf. buildworld will
1002 warn if it is improperly defined.
1005 This file contains a list, in reverse chronological order, of major
1006 breakages in tracking -current. Not all things will be listed here,
1007 and it only starts on October 16, 2004. Updating files can found in
1008 previous releases if your system is older than this.
1010 Copyright information:
1012 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1014 Redistribution, publication, translation and use, with or without
1015 modification, in full or in part, in any form or format of this
1016 document are permitted without further permission from the author.
1018 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1019 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1020 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1021 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1022 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1023 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1024 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1025 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1026 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1027 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1028 POSSIBILITY OF SUCH DAMAGE.
1030 Contact Warner Losh if you have any questions about your use of