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 old tunable hw.bus.devctl_disable has been superseded by
27 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
28 replaced by hw.bus.devctl_queue=0. The default for this new tunable
32 Remove the option STOP_NMI. The default action is now to use NMI only
33 for KDB via the newly introduced function stop_cpus_hard() and
34 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
37 The stable/8 branch created in subversion. This corresponds to the
38 RELENG_8 branch in CVS.
41 Bump the shared library version numbers for all libraries that do not
42 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
43 __FreeBSD_version to 800105.
46 Due to changes in the implementation of virtual network stack support,
47 all network-related kernel modules must be recompiled. As this change
48 breaks the ABI, bump __FreeBSD_version to 800104.
51 The TOE interface to the TCP syncache has been modified to remove
52 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
53 The cxgb driver is the only TOE consumer affected by this change, and
54 needs to be recompiled along with the kernel. As this change breaks
55 the ABI, bump __FreeBSD_version to 800103.
58 Padding has been added to struct tcpcb, sackhint and tcpstat in
59 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
60 maintainig the ABI. However, this change breaks the ABI, so bump
61 __FreeBSD_version to 800102. User space tools that rely on the size of
62 any of these structs (e.g. sockstat) need to be recompiled.
65 The NFS_LEGACYRPC option has been removed along with the old kernel
66 RPC implementation that this option selected. Kernel configurations
67 may need to be adjusted.
70 The network interface device nodes at /dev/net/<interface> have been
71 removed. All ioctl operations can be performed the normal way using
72 routing sockets. The kqueue functionality can generally be replaced
76 The documentation from the FreeBSD Documentation Project (Handbook,
77 FAQ, etc.) is now installed via packages by sysinstall(8) and under
78 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
81 The ABI of various structures related to the SYSV IPC API have been
82 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
83 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
87 Layout of struct vnet has changed as routing related variables were
88 moved to their own Vimage module. Modules need to be recompiled. Bump
89 __FreeBSD_version to 800099.
92 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
93 respectively. As long as no more than 16 groups per process are used,
94 no changes should be visible. When more than 16 groups are used, old
95 binaries may fail if they call getgroups() or getgrouplist() with
96 statically sized storage. Recompiling will work around this, but
97 applications should be modified to use dynamically allocated storage
98 for group arrays as POSIX.1-2008 does not cap an implementation's
99 number of supported groups at NGROUPS_MAX+1 as previous versions did.
101 NFS and portalfs mounts may also be affected as the list of groups is
102 truncated to 16. Users of NFS who use more than 16 groups, should
103 take care that negative group permissions are not used on the exported
104 file systems as they will not be reliable unless a GSSAPI based
105 authentication method is used.
108 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
109 option compiles in the support for adaptive spinning for lockmgrs
110 which want to enable it. The lockinit() function now accepts the flag
111 LK_ADAPTIVE in order to make the lock object subject to adaptive
112 spinning when both held in write and read mode.
115 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
116 changed. User applications that use this ioctl need to be rebuilt.
119 The layout of struct thread has changed. Kernel and modules need to
123 The layout of structs ifnet, domain, protosw and vnet_net has changed.
124 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
127 window(1) has been removed from the base system. It can now be
128 installed from ports. The port is called misc/window.
131 The way we are storing and accessing `routing table' entries has
132 changed. Programs reading the FIB, like netstat, need to be
136 A new netisr implementation has been added for FreeBSD 8. Network
137 file system modules, such as igmp, ipdivert, and others, should be
139 Bump __FreeBSD_version to 800096.
142 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
146 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
147 Bump __FreeBSD_version to 800094.
150 Add mnt_xflag field to 'struct mount'. File system modules need to be
152 Bump __FreeBSD_version to 800093.
155 The compiling option ADAPTIVE_SX has been retired while it has been
156 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
157 The KPI for sx_init_flags() changes as accepting flags:
158 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
159 been introduced in order to handle the reversed logic.
160 Bump __FreeBSD_version to 800092.
163 Add support for hierarchical jails. Remove global securelevel.
164 Bump __FreeBSD_version to 800091.
167 The layout of struct vnet_net has changed, therefore modules
169 Bump __FreeBSD_version to 800090.
172 The newly imported zic(8) produces a new format in the output. Please
173 run tzsetup(8) to install the newly created data to /etc/localtime.
176 The sysctl tree for the usb stack has renamed from hw.usb2.* to
177 hw.usb.* and is now consistent again with previous releases.
180 802.11 monitor mode support was revised and driver api's were changed.
181 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
182 of DLT_IEEE802_11. No user-visible data structures were changed but
183 applications that use DLT_IEEE802_11 may require changes.
184 Bump __FreeBSD_version to 800088.
187 The layout of the following structs has changed: sysctl_oid,
188 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
189 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
190 panics may be experienced. World rebuild is required for
191 correctly checking networking state from userland.
192 Bump __FreeBSD_version to 800085.
195 MLDv2 and Source-Specific Multicast (SSM) have been merged
196 to the IPv6 stack. VIMAGE hooks are in but not yet used.
197 The implementation of SSM within FreeBSD's IPv6 stack closely
198 follows the IPv4 implementation.
200 For kernel developers:
202 * The most important changes are that the ip6_output() and
203 ip6_input() paths no longer take the IN6_MULTI_LOCK,
204 and this lock has been downgraded to a non-recursive mutex.
206 * As with the changes to the IPv4 stack to support SSM, filtering
207 of inbound multicast traffic must now be performed by transport
208 protocols within the IPv6 stack. This does not apply to TCP and
209 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
211 * The KPIs used by IPv6 multicast are similar to those used by
212 the IPv4 stack, with the following differences:
213 * im6o_mc_filter() is analogous to imo_multicast_filter().
214 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
215 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
216 * IN6_LOOKUP_MULTI() has been deprecated and removed.
217 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
218 for MLDv1 have an additional 'timer' argument which is used to
219 jitter the initial membership report for the solicited-node
220 multicast membership on-link.
221 * This is not strictly needed for MLDv2, which already jitters
222 its report transmissions. However, the 'timer' argument is
223 preserved in case MLDv1 is active on the interface.
225 * The KAME linked-list based IPv6 membership implementation has
226 been refactored to use a vector similar to that used by the IPv4
228 Code which maintains a list of its own multicast memberships
229 internally, e.g. carp, has been updated to reflect the new
232 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
233 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
234 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
235 implementation constraint which needs to be addressed in HEAD.
237 For application developers:
239 * The changes are broadly similar to those made for the IPv4
242 * The use of IPv4 and IPv6 multicast socket options on the same
243 socket, using mapped addresses, HAS NOT been tested or supported.
245 * There are a number of issues with the implementation of various
246 IPv6 multicast APIs which need to be resolved in the API surface
247 before the implementation is fully compatible with KAME userland
248 use, and these are mostly to do with interface index treatment.
250 * The literature available discusses the use of either the delta / ASM
251 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
252 using setsourcefilter(3)/getsourcefilter(3). For more information
253 please refer to RFC 3768, 'Socket Interface Extensions for
254 Multicast Source Filters'.
256 * Applications which use the published RFC 3678 APIs should be fine.
258 For systems administrators:
260 * The mtest(8) utility has been refactored to support IPv6, in
261 addition to IPv4. Interface addresses are no longer accepted
262 as arguments, their names must be used instead. The utility
263 will map the interface name to its first IPv4 address as
264 returned by getifaddrs(3).
266 * The ifmcstat(8) utility has also been updated to print the MLDv2
267 endpoint state and source filter lists via sysctl(3).
269 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
270 loopback of IPv6 multicast datagrams by default; it defaults to 1
271 to preserve the existing behaviour. Disabling multicast loopback is
272 recommended for optimal system performance.
274 * The IPv6 MROUTING code has been changed to examine this sysctl
275 instead of attempting to perform a group lookup before looping
276 back forwarded datagrams.
278 Bump __FreeBSD_version to 800084.
281 Implement low-level Bluetooth HCI API.
282 Bump __FreeBSD_version to 800083.
285 The layout of struct malloc_type, used by modules to register new
286 memory allocation types, has changed. Most modules will need to
287 be rebuilt or panics may be experienced.
288 Bump __FreeBSD_version to 800081.
291 Anticipate overflowing inp_flags - add inp_flags2.
292 This changes most offsets in inpcb, so checking v4 connection
293 state will require a world rebuild.
294 Bump __FreeBSD_version to 800080.
297 Add an llentry to struct route and struct route_in6. Modules
298 embedding a struct route will need to be recompiled.
299 Bump __FreeBSD_version to 800079.
302 The size of rt_metrics_lite and by extension rtentry has changed.
303 Networking administration apps will need to be recompiled.
304 The route command now supports show as an alias for get, weighting
305 of routes, sticky and nostick flags to alter the behavior of stateful
307 Bump __FreeBSD_version to 800078.
310 Do not use Giant for kbdmux(4) locking. This is wrong and
311 apparently causing more problems than it solves. This will
312 re-open the issue where interrupt handlers may race with
313 kbdmux(4) in polling mode. Typical symptoms include (but
314 not limited to) duplicated and/or missing characters when
315 low level console functions (such as gets) are used while
316 interrupts are enabled (for example geli password prompt,
317 mountroot prompt etc.). Disabling kbdmux(4) may help.
320 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
321 kernel modules referencing any of the above need to be recompiled.
322 Bump __FreeBSD_version to 800075.
325 GEOM_PART has become the default partition slicer for storage devices,
326 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
327 introduces some changes:
329 MSDOS/EBR: the devices created from MSDOS extended partition entries
330 (EBR) can be named differently than with GEOM_MBR and are now symlinks
331 to devices with offset-based names. fstabs may need to be modified.
333 BSD: the "geometry does not match label" warning is harmless in most
334 cases but it points to problems in file system misalignment with
335 disk geometry. The "c" partition is now implicit, covers the whole
336 top-level drive and cannot be (mis)used by users.
338 General: Kernel dumps are now not allowed to be written to devices
339 whose partition types indicate they are meant to be used for file
340 systems (or, in case of MSDOS partitions, as something else than
343 Most of these changes date approximately from 200812.
346 The uscanner(4) driver has been removed from the kernel. This follows
347 Linux removing theirs in 2.6 and making libusb the default interface
351 The multicast forwarding code has been cleaned up. netstat(1)
352 only relies on KVM now for printing bandwidth upcall meters.
353 The IPv4 and IPv6 modules are split into ip_mroute_mod and
354 ip6_mroute_mod respectively. The config(5) options for statically
355 compiling this code remain the same, i.e. 'options MROUTING'.
358 Support for the IFF_NEEDSGIANT network interface flag has been
359 removed, which means that non-MPSAFE network device drivers are no
360 longer supported. In particular, if_ar, if_sr, and network device
361 drivers from the old (legacy) USB stack can no longer be built or
365 POSIX.1 Native Language Support (NLS) has been enabled in libc and
366 a bunch of new language catalog files have also been added.
367 This means that some common libc messages are now localized and
368 they depend on the LC_MESSAGES environmental variable.
371 The k8temp(4) driver has been renamed to amdtemp(4) since
372 support for K10 and K11 CPU families was added.
375 IGMPv3 and Source-Specific Multicast (SSM) have been merged
376 to the IPv4 stack. VIMAGE hooks are in but not yet used.
378 For kernel developers, the most important changes are that the
379 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
380 and this lock has been downgraded to a non-recursive mutex.
382 Transport protocols (UDP, Raw IP) are now responsible for filtering
383 inbound multicast traffic according to group membership and source
384 filters. The imo_multicast_filter() KPI exists for this purpose.
385 Transports which do not use multicast (SCTP, TCP) already reject
386 multicast by default. Forwarding and receive performance may improve
387 as a mutex acquisition is no longer needed in the ip_input()
388 low-level input path. in_addmulti() and in_delmulti() are shimmed
389 to new KPIs which exist to support SSM in-kernel.
391 For application developers, it is recommended that loopback of
392 multicast datagrams be disabled for best performance, as this
393 will still cause the lock to be taken for each looped-back
394 datagram transmission. The net.inet.ip.mcast.loop sysctl may
395 be tuned to 0 to disable loopback by default; it defaults to 1
396 to preserve the existing behaviour.
398 For systems administrators, to obtain best performance with
399 multicast reception and multiple groups, it is always recommended
400 that a card with a suitably precise hash filter is used. Hash
401 collisions will still result in the lock being taken within the
402 transport protocol input path to check group membership.
404 If deploying FreeBSD in an environment with IGMP snooping switches,
405 it is recommended that the net.inet.igmp.sendlocal sysctl remain
406 enabled; this forces 224.0.0.0/24 group membership to be announced
409 The size of 'struct igmpstat' has changed; netstat needs to be
410 recompiled to reflect this.
411 Bump __FreeBSD_version to 800070.
414 libusb20.so.1 is now installed as libusb.so.1 and the ports system
415 updated to use it. This requires a buildworld/installworld in order to
416 update the library and dependencies (usbconfig, etc). Its advisable to
417 rebuild all ports which uses libusb. More specific directions are given
418 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
419 libusb are no longer required and can be removed.
422 A workaround is committed to allow the creation of System V shared
423 memory segment of size > 2 GB on the 64-bit architectures.
424 Due to a limitation of the existing ABI, the shm_segsz member
425 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
426 wrong for large segments. Note that limits must be explicitly
427 raised to allow such segments to be created.
430 The layout of struct ifnet has changed, requiring a rebuild of all
431 network device driver modules.
434 The /dev handling for the new USB stack has changed, a
435 buildworld/installworld is required for libusb20.
438 The new USB2 stack has now been permanently moved in and all kernel and
439 module names reverted to their previous values (eg, usb, ehci, ohci,
440 ums, ...). The old usb stack can be compiled in by prefixing the name
441 with the letter 'o', the old usb modules have been removed.
442 Updating entry 20090216 for xorg and 20090215 for libmap may still
446 The rc.conf(5) option if_up_delay has been renamed to
447 defaultroute_delay to better reflect its purpose. If you have
448 customized this setting in /etc/rc.conf you need to update it to
452 xorg 7.4 wants to configure its input devices via hald which does not
453 yet work with USB2. If the keyboard/mouse does not work in xorg then
455 Option "AllowEmptyInput" "off"
456 to your ServerLayout section. This will cause X to use the configured
457 kbd and mouse sections from your xorg.conf.
460 The GENERIC kernels for all architectures now default to the new USB2
461 stack. No kernel config options or code have been removed so if a
462 problem arises please report it and optionally revert to the old USB
463 stack. If you are loading USB kernel modules or have a custom kernel
464 that includes GENERIC then ensure that usb names are also changed over,
465 eg uftdi -> usb2_serial_ftdi.
467 Older programs linked against the ports libusb 0.1 need to be
468 redirected to the new stack's libusb20. /etc/libmap.conf can
470 # Map old usb library to new one for usb2 stack
471 libusb-0.1.so.8 libusb20.so.1
474 The ichsmb(4) driver has been changed to require SMBus slave
475 addresses be left-justified (xxxxxxx0b) rather than right-justified.
476 All of the other SMBus controller drivers require left-justified
477 slave addresses, so this change makes all the drivers provide the
481 INET6 statistics (struct ip6stat) was updated.
482 netstat(1) needs to be recompiled.
485 NTFS has been removed from GENERIC kernel on amd64 to match
486 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
487 will load ntfs.ko module automatically when NTFS support is
488 actually needed, unless ntfs.ko is not installed or security
489 level prohibits loading kernel modules. If either is the case,
490 "options NTFS" has to be added into kernel config.
493 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
494 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
495 800061. User space tools that rely on the size of struct tcpcb in
496 tcp_var.h (e.g. sockstat) need to be recompiled.
499 ng_tty(4) module updated to match the new TTY subsystem.
500 Due to API change, user-level applications must be updated.
501 New API support added to mpd5 CVS and expected to be present
502 in next mpd5.3 release.
505 With __FreeBSD_version 800060 the makefs tool is part of
506 the base system (it was a port).
509 The afdata and ifnet locks have been changed from mutexes to
510 rwlocks, network modules will need to be re-compiled.
513 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
514 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
515 The new code reduced struct rtentry{} by 16 bytes on 32-bit
516 architecture and 40 bytes on 64-bit architecture. The userland
517 applications "arp" and "ndp" have been updated accordingly.
518 The output from "netstat -r" shows only routing entries and
519 none of the L2 information.
522 __FreeBSD_version 800057 marks the switchover from the
523 binary ath hal to source code. Users must add the line:
525 options AH_SUPPORT_AR5416
527 to their kernel config files when specifying:
531 The ath_hal module no longer exists; the code is now compiled
532 together with the driver in the ath module. It is now
533 possible to tailor chip support (i.e. reduce the set of chips
534 and thereby the code size); consult ath_hal(4) for details.
537 __FreeBSD_version 800054 adds memory barriers to
538 <machine/atomic.h>, new interfaces to ifnet to facilitate
539 multiple hardware transmit queues for cards that support
540 them, and a lock-less ring-buffer implementation to
541 enable drivers to more efficiently manage queueing of
545 A new version of ZFS (version 13) has been merged to -HEAD.
546 This version has zpool attribute "listsnapshots" off by
547 default, which means "zfs list" does not show snapshots,
548 and is the same as Solaris behavior.
551 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
554 The uhci, ohci, ehci and slhci USB Host controller drivers have
555 been put into separate modules. If you load the usb module
556 separately through loader.conf you will need to load the
557 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
558 controller add the following to loader.conf:
564 The ABI used by the PMC toolset has changed. Please keep
565 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
569 The TTY subsystem of the kernel has been replaced by a new
570 implementation, which provides better scalability and an
571 improved driver model. Most common drivers have been migrated to
572 the new TTY subsystem, while others have not. The following
573 drivers have not yet been ported to the new TTY layer:
576 cy, digi, rc, rp, sio
582 ng_h4, ng_tty, ppp, sl, snp
584 Adding these drivers to your kernel configuration file shall
585 cause compilation to fail.
588 ntpd has been upgraded to 4.2.4p5.
591 OpenSSH has been upgraded to 5.1p1.
593 For many years, FreeBSD's version of OpenSSH preferred DSA
594 over RSA for host and user authentication keys. With this
595 upgrade, we've switched to the vendor's default of RSA over
596 DSA. This may cause upgraded clients to warn about unknown
597 host keys even for previously known hosts. Users should
598 follow the usual procedure for verifying host keys before
599 accepting the RSA key.
601 This can be circumvented by setting the "HostKeyAlgorithms"
602 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
605 Please note that the sequence of keys offered for
606 authentication has been changed as well. You may want to
607 specify IdentityFile in a different order to revert this
611 The sio(4) driver has been removed from the i386 and amd64
612 kernel configuration files. This means uart(4) is now the
613 default serial port driver on those platforms as well.
615 To prevent collisions with the sio(4) driver, the uart(4) driver
616 uses different names for its device nodes. This means the
617 onboard serial port will now most likely be called "ttyu0"
618 instead of "ttyd0". You may need to reconfigure applications to
619 use the new device names.
621 When using the serial port as a boot console, be sure to update
622 /boot/device.hints and /etc/ttys before booting the new kernel.
623 If you forget to do so, you can still manually specify the hints
624 at the loader prompt:
626 set hint.uart.0.at="isa"
627 set hint.uart.0.port="0x3F8"
628 set hint.uart.0.flags="0x10"
629 set hint.uart.0.irq="4"
633 The gpt(8) utility has been removed. Use gpart(8) to partition
637 The version that Linuxulator emulates was changed from 2.4.2
638 to 2.6.16. If you experience any problems with Linux binaries
639 please try to set sysctl compat.linux.osrelease to 2.4.2 and
640 if it fixes the problem contact emulation mailing list.
643 ISDN4BSD (I4B) was removed from the src tree. You may need to
644 update a your kernel configuration and remove relevant entries.
647 I have checked in code to support multiple routing tables.
648 See the man pages setfib(1) and setfib(2).
649 This is a hopefully backwards compatible version,
650 but to make use of it you need to compile your kernel
651 with options ROUTETABLES=2 (or more up to 16).
654 The 802.11 wireless support was redone to enable multi-bss
655 operation on devices that are capable. The underlying device
656 is no longer used directly but instead wlanX devices are
657 cloned with ifconfig. This requires changes to rc.conf files.
659 ifconfig_ath0="WPA DHCP"
662 ifconfig_wlan0="WPA DHCP"
663 see rc.conf(5) for more details. In addition, mergemaster of
664 /etc/rc.d is highly recommended. Simultaneous update of userland
665 and kernel wouldn't hurt either.
667 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
668 modules were merged into the base wlan module. All references
669 to these modules (e.g. in kernel config files) must be removed.
672 psm(4) has gained write(2) support in native operation level.
673 Arbitrary commands can be written to /dev/psm%d and status can
674 be read back from it. Therefore, an application is responsible
675 for status validation and error recovery. It is a no-op in
676 other operation levels.
679 Support for KSE threading has been removed from the kernel. To
680 run legacy applications linked against KSE libmap.conf may
681 be used. The following libmap.conf may be used to ensure
682 compatibility with any prior release:
684 libpthread.so.1 libthr.so.1
685 libpthread.so.2 libthr.so.2
686 libkse.so.3 libthr.so.3
689 The layout of struct vmspace has changed. This affects libkvm
690 and any executables that link against libkvm and use the
691 kvm_getprocs() function. In particular, but not exclusively,
692 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
693 The effects are minimal, but it's advisable to upgrade world
697 The latest em driver no longer has support in it for the
698 82575 adapter, this is now moved to the igb driver. The
699 split was done to make new features that are incompatible
700 with older hardware easier to do.
703 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
704 likewise the kernel option is now GEOM_LINUX_LVM.
707 The default NFS mount mode has changed from UDP to TCP for
708 increased reliability. If you rely on (insecurely) NFS
709 mounting across a firewall you may need to update your
713 Belatedly note the addition of m_collapse for compacting
717 The fts(3) structures have been changed to use adequate
718 integer types for their members and so to be able to cope
719 with huge file trees. The old fts(3) ABI is preserved
720 through symbol versioning in libc, so third-party binaries
721 using fts(3) should still work, although they will not take
722 advantage of the extended types. At the same time, some
723 third-party software might fail to build after this change
724 due to unportable assumptions made in its source code about
725 fts(3) structure members. Such software should be fixed
726 by its vendor or, in the worst case, in the ports tree.
727 FreeBSD_version 800015 marks this change for the unlikely
728 case that a portable fix is impossible.
731 To upgrade to -current after this date, you must be running
732 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
733 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
736 The ADAPTIVE_GIANT kernel option has been retired because its
737 functionality is the default now.
740 The AT keyboard emulation of sunkbd(4) has been turned on
741 by default. In order to make the special symbols of the Sun
742 keyboards driven by sunkbd(4) work under X these now have
743 to be configured the same way as Sun USB keyboards driven
744 by ukbd(4) (which also does AT keyboard emulation), f.e.:
746 Option "XkbLayout" "us"
747 Option "XkbRules" "xorg"
748 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
751 It has been decided that it is desirable to provide ABI
752 backwards compatibility to the FreeBSD 4/5/6 versions of the
753 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
754 broken with the introduction of PCI domain support (see the
755 20070930 entry). Unfortunately, this required the ABI of
756 PCIOCGETCONF to be broken again in order to be able to
757 provide backwards compatibility to the old version of that
758 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
759 again. As for prominent ports this affects neither pciutils
760 nor xorg-server this time, the hal port needs to be rebuilt
764 The misnamed kthread_create() and friends have been renamed
765 to kproc_create() etc. Many of the callers already
767 I will return kthread_create() and friends in a while
768 with implementations that actually create threads, not procs.
769 Renaming corresponds with version 800002.
778 Avoid using make -j when upgrading. While generally safe, there are
779 sometimes problems using -j to upgrade. If your upgrade fails with
780 -j, please try again wtihout -j. From time to time in the past there
781 have been problems using -j with buildworld and/or installworld. This
782 is especially true when upgrading between "distant" versions (eg one
783 that cross a major release boundary or several minor releases, or when
784 several months have passed on the -current branch).
786 Sometimes, obscure build problems are the result of environment
787 poisoning. This can happen because the make utility reads its
788 environment when searching for values for global variables. To run
789 your build attempts in an "environmental clean room", prefix all make
790 commands with 'env -i '. See the env(1) manual page for more details.
792 When upgrading from one major version to another it is generally best
793 to upgrade to the latest code in the currently installed branch first,
794 then do an upgrade to the new branch. This is the best-tested upgrade
795 path, and has the highest probability of being successful. Please try
796 this approach before reporting problems with a major version upgrade.
800 If you are updating from a prior version of FreeBSD (even one just
801 a few days old), you should follow this procedure. It is the most
802 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
804 make kernel-toolchain
805 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
806 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
808 To test a kernel once
809 ---------------------
810 If you just want to boot a kernel once (because you are not sure
811 if it works, or if you want to boot a known bad kernel to provide
812 debugging information) run
813 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
814 nextboot -k testkernel
816 To just build a kernel when you know that it won't mess you up
817 --------------------------------------------------------------
818 This assumes you are already running a CURRENT system. Replace
819 ${arch} with the architecture of your machine (e.g. "i386",
820 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
822 cd src/sys/${arch}/conf
823 config KERNEL_NAME_HERE
824 cd ../compile/KERNEL_NAME_HERE
829 If this fails, go to the "To build a kernel" section.
831 To rebuild everything and install it on the current system.
832 -----------------------------------------------------------
833 # Note: sometimes if you are running current you gotta do more than
834 # is listed here if you are upgrading from a really old current.
836 <make sure you have good level 0 dumps>
838 make kernel KERNCONF=YOUR_KERNEL_HERE
840 <reboot in single user> [3]
848 To cross-install current onto a separate partition
849 --------------------------------------------------
850 # In this approach we use a separate partition to hold
851 # current's root, 'usr', and 'var' directories. A partition
852 # holding "/", "/usr" and "/var" should be about 2GB in
855 <make sure you have good level 0 dumps>
858 make buildkernel KERNCONF=YOUR_KERNEL_HERE
859 <maybe newfs current's root partition>
860 <mount current's root partition on directory ${CURRENT_ROOT}>
861 make installworld DESTDIR=${CURRENT_ROOT}
862 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
863 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
864 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
865 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
866 <reboot into current>
867 <do a "native" rebuild/install as described in the previous section>
868 <maybe install compatibility libraries from ports/misc/compat*>
872 To upgrade in-place from 8.x-stable to current
873 ----------------------------------------------
874 <make sure you have good level 0 dumps>
876 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
878 <reboot in single user> [3]
885 Make sure that you've read the UPDATING file to understand the
886 tweaks to various things you need. At this point in the life
887 cycle of current, things change often and you are on your own
888 to cope. The defaults can also change, so please read ALL of
889 the UPDATING entries.
891 Also, if you are tracking -current, you must be subscribed to
892 freebsd-current@freebsd.org. Make sure that before you update
893 your sources that you have read and understood all the recent
894 messages there. If in doubt, please track -stable which has
897 [1] If you have third party modules, such as vmware, you
898 should disable them at this point so they don't crash your
901 [3] From the bootblocks, boot -s, and then do
906 adjkerntz -i # if CMOS is wall time
907 Also, when doing a major release upgrade, it is required that
908 you boot into single user mode to do the installworld.
910 [4] Note: This step is non-optional. Failure to do this step
911 can result in a significant reduction in the functionality of the
912 system. Attempting to do it by hand is not recommended and those
913 that pursue this avenue should read this file carefully, as well
914 as the archives of freebsd-current and freebsd-hackers mailing lists
915 for potential gotchas.
917 [5] Usually this step is a noop. However, from time to time
918 you may need to do this if you get unknown user in the following
919 step. It never hurts to do it all the time. You may need to
920 install a new mergemaster (cd src/usr.sbin/mergemaster && make
921 install) after the buildworld before this step if you last updated
922 from current before 20020224 or from -stable before 20020408.
924 [8] In order to have a kernel that can run the 4.x binaries needed to
925 do an installworld, you must include the COMPAT_FREEBSD4 option in
926 your kernel. Failure to do so may leave you with a system that is
927 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
928 required to run the 5.x binaries on more recent kernels. And so on
929 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
931 Make sure that you merge any new devices from GENERIC since the
932 last time you updated your kernel config file.
934 [9] When checking out sources, you must include the -P flag to have
935 cvs prune empty directories.
937 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
938 "?=" instead of the "=" assignment operator, so that buildworld can
939 override the CPUTYPE if it needs to.
941 MAKEOBJDIRPREFIX must be defined in an environment variable, and
942 not on the command line, or in /etc/make.conf. buildworld will
943 warn if it is improperly defined.
946 This file contains a list, in reverse chronological order, of major
947 breakages in tracking -current. Not all things will be listed here,
948 and it only starts on October 16, 2004. Updating files can found in
949 previous releases if your system is older than this.
951 Copyright information:
953 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
955 Redistribution, publication, translation and use, with or without
956 modification, in full or in part, in any form or format of this
957 document are permitted without further permission from the author.
959 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
960 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
961 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
962 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
963 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
964 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
965 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
966 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
967 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
968 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
969 POSSIBILITY OF SUCH DAMAGE.
971 Contact Warner Losh if you have any questions about your use of