1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh
4 <imp@village.org>. See end of file for further details. For commonly
5 done items, please see the COMMON ITEMS: section later in the file.
7 Items affecting the ports and packages system can be found in
8 /usr/ports/UPDATING. Please read that file before running
11 NOTE TO PEOPLE WHO THINK THAT FreeBSD 8.x IS SLOW ON IA64 OR SUN4V:
12 For ia64 the INVARIANTS and INVARIANT_SUPPORT kernel options
13 were left in the GENERIC kernel because the kernel does not
14 work properly without them. For sun4v all of the normal kernel
15 debugging tools present in HEAD were left in place because
16 sun4v support still needs work to become production ready.
19 hastctl(8)'s `status' command output changed to terse one-liner format.
20 Scripts using this should switch to `list' command or be rewritten.
23 Added ZFS TRIM support which is enabled by default. To disable
24 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
26 Creating new ZFS pools and adding new devices to existing pools
27 first performs a full device level TRIM, which can take a significant
28 amount of time. Set the sysctl vfs.zfs.vdev.trim_on_init to 0 to
29 disable this behaviour.
31 ZFS TRIM requires the underlying device support BIO_DELETE which
32 is currently provided by methods such as ATA TRIM and SCSI UNMAP
33 via CAM, which are typically supported by SSD's.
35 Stats for ZFS TRIM can be monitored by looking at the sysctl's
36 under kstat.zfs.misc.zio_trim.
42 `list' command has been added to hastctl(8). For now, it is full
43 equivalent of `status' command.
44 WARNING: in the near future the output of hastctl's status command
45 will change to more terse format. If you use `hastctl status'
46 for parsing in your scripts, switch to `hastctl list'.
49 Fix a bug that allows NFS clients to issue READDIR on files.
52 A new compression method (lz4) has been merged. Please refer to
53 zpool-features(7) for more information.
55 Please refer to the "ZFS notes" section of this file for information
56 on upgrading boot ZFS pools.
59 A new version of ZFS (pool version 5000) has been merged to 8-STABLE.
60 Starting with this version the old system of ZFS pool versioning
61 is superseded by "feature flags". This concept enables forward
62 compatibility against certain future changes in functionality of ZFS
63 pools. The first two read-only compatible "feature flags" for ZFS
64 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
65 For more information read the new zpool-features(7) manual page.
66 Please refer to the "ZFS notes" section of this file for information
67 on upgrading boot ZFS pools.
70 WITH_CTF can now be specified in src.conf (not recommended, there
71 are some problems with static executables), make.conf (would also
72 affect ports which do not use GNU make and do not override the
73 compile targets) or in the kernel config (via "makeoptions
75 When WITH_CTF was specified there before this was silently ignored,
76 so make sure that WITH_CTF is not used in places which could lead
80 The random(4) support for the VIA hardware random number
81 generator (`PADLOCK') is no longer enabled unconditionally.
82 Add the PADLOCK_RNG option in the custom kernel config if
83 needed. The GENERIC kernels on i386 and amd64 do include the
84 option, so the change only affects the custom kernel
88 The sparc64 ZFS loader has been changed to no longer try to auto-
89 detect ZFS providers based on diskN aliases but now requires these
90 to be explicitly listed in the OFW boot-device environment variable.
96 A new VOP_ADVISE() was added to support posix_fadvise(2). All
97 filesystem modules must be recompiled.
100 A new VOP_ALLOCATE() was added to support posix_fallocate(2). All
101 filesystem modules must be recompiled.
104 The broken amd(4) driver has been replaced with esp(4) in the amd64,
105 i386 and pc98 GENERIC kernel configuration files.
108 A new version of ZFS (version 28) has been merged.
109 This version does not depend on a python library and the
110 sysutils/py-zfs port is not used anymore.
111 For upgrading your boot pool, please read "ZFS notes"
112 in the COMMON ITEMS: section later in this file.
115 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
116 compliant, and will now use half of hash for authentication.
117 This will break interoperability with all stacks (including all
118 older FreeBSD versions) who implement
119 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
121 The only workaround with such peers is to use another HMAC
122 algorithm for IPsec ("phase 2") authentication.
128 New version of minidump format for amd64 architecture was
129 introduced in r215872. To analyze vmcore files produced by
130 kernels at or after this version you will need updated userland,
131 libkvm actually, that is able to handle the new version.
134 A workaround for a fixed ld bug has been removed in kernel code,
135 so make sure that your system ld is built from sources after
136 revision 211583 from 2010-08-21 (r210245 from 2010-07-19 if
137 building stable/8 kernel on head, r211584 from 2010-08-21 for
138 stable/7). A symptom of incorrect ld version is
139 different addresses for set_pcpu section and __start_set_pcpu
140 symbol in kernel and/or modules.
143 A new version of ZFS (version 15) has been merged.
144 This version uses a python library for the following subcommands:
145 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
146 For full functionality of these commands the following port must
147 be installed: sysutils/py-zfs
153 The config(8) command has been updated to maintain compatibility
154 with config files from 8.0-RELEASE. You will need a new version
155 of config to build kernels (this version can be used from 8.0-RELEASE
156 forward). The buildworld target will generate it, so following
157 the instructions in this file for updating will work glitch-free.
158 Merely doing a make buildkernel without first doing a make buildworld
159 (or kernel-toolchain), or attempting to build a kernel using
160 traidtional methods will generate a config version warning, indicating
164 The rc.firewall and rc.firewall6 were unified, and
165 rc.firewall6 and rc.d/ip6fw were removed.
166 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
167 variables are obsoleted. Instead, the following new rc
168 variables are added to rc.d/ipfw:
170 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
171 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
172 firewall_simple_onet_ipv6
174 The meanings correspond to the relevant IPv4 variables.
177 COMPAT_IA32 has been added as an alias for COMPAT_FREEBSD32. A new
178 version of config(8) is required. The error message when you hit this
179 condition is confusing (COMPAT_FREEBSD32 duplicate option), when it
180 should really say "your config is too old to compile this new kernel."
183 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
184 to allow 32-bit compatibility on non-x86 platforms. All kernel
185 configurations on amd64 and ia64 platforms using these options must
186 be modified accordingly.
189 Introduce the kernel thread "deadlock resolver" (which can be enabled
190 via the DEADLKRES option, see NOTES for more details) and the
191 sleepq_type() function for sleepqueues.
197 802.11s D3.03 support was committed. This is incompatible with
198 the previous code, which was based on D3.0.
201 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
202 mount(8) and -a option for df(1) to see them.
205 Remove the option STOP_NMI. The default action is now to use NMI
206 only for KDB via the newly introduced function stop_cpus_hard()
207 and maintain stop_cpus() to just use a normal IPI_STOP on ia32
214 Bump the shared library version numbers for all libraries that
215 do not use symbol versioning as part of the 8.0-RELEASE cycle.
216 Bump __FreeBSD_version to 800105.
219 Due to changes in the implementation of virtual network stack
220 support, all network-related kernel modules must be recompiled.
221 As this change breaks the ABI, bump __FreeBSD_version to 800104.
224 The TOE interface to the TCP syncache has been modified to remove struct
225 tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack. The
226 cxgb driver is the only TOE consumer affected by this change, and needs
227 to be recompiled along with the kernel. As this change breaks the ABI,
228 bump __FreeBSD_version to 800103.
231 Padding has been added to struct tcpcb, sackhint and tcpstat in
232 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
233 maintainig the ABI. However, this change breaks the ABI, so bump
234 __FreeBSD_version to 800102. User space tools that rely on the size of
235 any of these structs (e.g. sockstat) need to be recompiled.
238 The NFS_LEGACYRPC option has been removed along with the old
239 kernel RPC implementation that this option selected. Kernel
240 configurations may need to be adjusted.
243 The network interface device nodes at /dev/net/<interface> have
244 been removed. All ioctl operations can be performed the normal
245 way using routing sockets. The kqueue functionality can
246 generally be replaced with routing sockets.
249 The documentation from the FreeBSD Documentation Project
250 (Handbook, FAQ, etc.) is now installed via packages by
251 sysinstall(8) and under the /usr/local/share/doc/freebsd
252 directory instead of /usr/share/doc.
255 The ABI of various structures related to the SYSV IPC API have
256 been changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43
257 kernel options now all require COMPAT_FREEBSD7.
258 Bump __FreeBSD_version to 800100.
261 Layout of struct vnet has changed as routing related variables
262 were moved to their own Vimage module. Modules need to be
263 recompiled. Bump __FreeBSD_version to 800099.
266 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023
267 and 1024 respectively. As long as no more than 16 groups per
268 process are used, no changes should be visible. When more
269 than 16 groups are used, old binaries may fail if they call
270 getgroups() or getgrouplist() with statically sized storage.
271 Recompiling will work around this, but applications should be
272 modified to use dynamically allocated storage for group arrays
273 as POSIX.1-2008 does not cap an implementation's number of
274 supported groups at NGROUPS_MAX+1 as previous versions did.
276 NFS and portalfs mounts may also be affected as the list of
277 groups is truncated to 16. Users of NFS who use more than 16
278 groups, should take care that negative group permissions are not
279 used on the exported file systems as they will not be reliable
280 unless a GSSAPI based authentication method is used.
283 The compiling option ADAPTIVE_LOCKMGRS has been introduced.
284 This option compiles in the support for adaptive spinning for lockmgrs
285 which want to enable it. The lockinit() function now accepts the
286 flag LK_ADAPTIVE in order to make the lock object subject to
287 adaptive spinning when both held in write and read mode.
290 The layout of the structure returned by IEEE80211_IOC_STA_INFO
291 has changed. User applications that use this ioctl need to be
295 The layout of struct thread has changed. Kernel and modules
299 The layout of structs ifnet, domain, protosw and vnet_net has
300 changed. Kernel modules need to be rebuilt.
301 Bump __FreeBSD_version to 800097.
304 window(1) has been removed from the base system. It can now be
305 installed from ports. The port is called misc/window.
308 The way we are storing and accessing `routing table' entries
309 has changed. Programs reading the FIB, like netstat, need to
313 A new netisr implementation has been added for FreeBSD 8. Network
314 file system modules, such as igmp, ipdivert, and others, should be
316 Bump __FreeBSD_version to 800096.
319 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose
323 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
324 Bump __FreeBSD_version to 800094.
327 Add mnt_xflag field to 'struct mount'. File system modules
329 Bump __FreeBSD_version to 800093.
332 The compiling option ADAPTIVE_SX has been retired while it has been
333 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
334 The KPI for sx_init_flags() changes as accepting flags:
335 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag
336 has been introduced in order to handle the reversed logic.
337 Bump __FreeBSD_version to 800092.
340 Add support for hierarchical jails. Remove global securelevel.
341 Bump __FreeBSD_version to 800091.
344 The layout of struct vnet_net has changed, therefore modules
346 Bump __FreeBSD_version to 800090.
349 The newly imported zic(8) produces a new format in the
350 output. Please run tzsetup(8) to install the newly created
351 data to /etc/localtime.
354 The sysctl tree for the usb stack has renamed from hw.usb2.* to
355 hw.usb.* and is now consistent again with previous releases.
358 802.11 monitor mode support was revised and driver api's
359 were changed. Drivers dependent on net80211 now support
360 DLT_IEEE802_11_RADIO instead of DLT_IEEE802_11. No
361 user-visible data structures were changed but applications
362 that use DLT_IEEE802_11 may require changes.
363 Bump __FreeBSD_version to 800088.
366 The layout of the following structs has changed: sysctl_oid,
367 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
368 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
369 panics may be experienced. World rebuild is required for
370 correctly checking networking state from userland.
371 Bump __FreeBSD_version to 800085.
374 MLDv2 and Source-Specific Multicast (SSM) have been merged
375 to the IPv6 stack. VIMAGE hooks are in but not yet used.
376 The implementation of SSM within FreeBSD's IPv6 stack closely
377 follows the IPv4 implementation.
379 For kernel developers:
381 * The most important changes are that the ip6_output() and
382 ip6_input() paths no longer take the IN6_MULTI_LOCK,
383 and this lock has been downgraded to a non-recursive mutex.
385 * As with the changes to the IPv4 stack to support SSM, filtering
386 of inbound multicast traffic must now be performed by transport
387 protocols within the IPv6 stack. This does not apply to TCP and
388 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
390 * The KPIs used by IPv6 multicast are similar to those used by
391 the IPv4 stack, with the following differences:
392 * im6o_mc_filter() is analogous to imo_multicast_filter().
393 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
394 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
395 * IN6_LOOKUP_MULTI() has been deprecated and removed.
396 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
397 for MLDv1 have an additional 'timer' argument which is used to
398 jitter the initial membership report for the solicited-node
399 multicast membership on-link.
400 * This is not strictly needed for MLDv2, which already jitters
401 its report transmissions. However, the 'timer' argument is
402 preserved in case MLDv1 is active on the interface.
404 * The KAME linked-list based IPv6 membership implementation has
405 been refactored to use a vector similar to that used by the IPv4
407 Code which maintains a list of its own multicast memberships
408 internally, e.g. carp, has been updated to reflect the new
411 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
412 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
413 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
414 implementation constraint which needs to be addressed in HEAD.
416 For application developers:
418 * The changes are broadly similar to those made for the IPv4
421 * The use of IPv4 and IPv6 multicast socket options on the same
422 socket, using mapped addresses, HAS NOT been tested or supported.
424 * There are a number of issues with the implementation of various
425 IPv6 multicast APIs which need to be resolved in the API surface
426 before the implementation is fully compatible with KAME userland
427 use, and these are mostly to do with interface index treatment.
429 * The literature available discusses the use of either the delta / ASM
430 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
431 using setsourcefilter(3)/getsourcefilter(3). For more information
432 please refer to RFC 3768, 'Socket Interface Extensions for
433 Multicast Source Filters'.
435 * Applications which use the published RFC 3678 APIs should be fine.
437 For systems administrators:
439 * The mtest(8) utility has been refactored to support IPv6, in
440 addition to IPv4. Interface addresses are no longer accepted
441 as arguments, their names must be used instead. The utility
442 will map the interface name to its first IPv4 address as
443 returned by getifaddrs(3).
445 * The ifmcstat(8) utility has also been updated to print the MLDv2
446 endpoint state and source filter lists via sysctl(3).
448 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
449 loopback of IPv6 multicast datagrams by default; it defaults to 1
450 to preserve the existing behaviour. Disabling multicast loopback is
451 recommended for optimal system performance.
453 * The IPv6 MROUTING code has been changed to examine this sysctl
454 instead of attempting to perform a group lookup before looping
455 back forwarded datagrams.
457 Bump __FreeBSD_version to 800084.
460 Implement low-level Bluetooth HCI API.
461 Bump __FreeBSD_version to 800083.
464 The layout of struct malloc_type, used by modules to register new
465 memory allocation types, has changed. Most modules will need to
466 be rebuilt or panics may be experienced.
467 Bump __FreeBSD_version to 800081.
470 Anticipate overflowing inp_flags - add inp_flags2.
471 This changes most offsets in inpcb, so checking v4 connection
472 state will require a world rebuild.
473 Bump __FreeBSD_version to 800080.
476 Add an llentry to struct route and struct route_in6. Modules
477 embedding a struct route will need to be recompiled.
478 Bump __FreeBSD_version to 800079.
481 The size of rt_metrics_lite and by extension rtentry has changed.
482 Networking administration apps will need to be recompiled.
483 The route command now supports show as an alias for get, weighting
484 of routes, sticky and nostick flags to alter the behavior of stateful
486 Bump __FreeBSD_version to 800078.
489 Do not use Giant for kbdmux(4) locking. This is wrong and
490 apparently causing more problems than it solves. This will
491 re-open the issue where interrupt handlers may race with
492 kbdmux(4) in polling mode. Typical symptoms include (but
493 not limited to) duplicated and/or missing characters when
494 low level console functions (such as gets) are used while
495 interrupts are enabled (for example geli password prompt,
496 mountroot prompt etc.). Disabling kbdmux(4) may help.
499 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
500 kernel modules referencing any of the above need to be recompiled.
501 Bump __FreeBSD_version to 800075.
504 GEOM_PART has become the default partition slicer for storage devices,
505 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
506 introduces some changes:
508 MSDOS/EBR: the devices created from MSDOS extended partition entries
509 (EBR) can be named differently than with GEOM_MBR and are now symlinks
510 to devices with offset-based names. fstabs may need to be modified.
512 BSD: the "geometry does not match label" warning is harmless in most
513 cases but it points to problems in file system misalignment with
514 disk geometry. The "c" partition is now implicit, covers the whole
515 top-level drive and cannot be (mis)used by users.
517 General: Kernel dumps are now not allowed to be written to devices
518 whose partition types indicate they are meant to be used for file
519 systems (or, in case of MSDOS partitions, as something else than
522 Most of these changes date approximately from 200812.
525 The uscanner(4) driver has been removed from the kernel. This follows
526 Linux removing theirs in 2.6 and making libusb the default interface
530 The multicast forwarding code has been cleaned up. netstat(1)
531 only relies on KVM now for printing bandwidth upcall meters.
532 The IPv4 and IPv6 modules are split into ip_mroute_mod and
533 ip6_mroute_mod respectively. The config(5) options for statically
534 compiling this code remain the same, i.e. 'options MROUTING'.
537 Support for the IFF_NEEDSGIANT network interface flag has been
538 removed, which means that non-MPSAFE network device drivers are no
539 longer supported. In particular, if_ar, if_sr, and network device
540 drivers from the old (legacy) USB stack can no longer be built or
544 POSIX.1 Native Language Support (NLS) has been enabled in libc and
545 a bunch of new language catalog files have also been added.
546 This means that some common libc messages are now localized and
547 they depend on the LC_MESSAGES environmental variable.
550 The k8temp(4) driver has been renamed to amdtemp(4) since
551 support for K10 and K11 CPU families was added.
554 IGMPv3 and Source-Specific Multicast (SSM) have been merged
555 to the IPv4 stack. VIMAGE hooks are in but not yet used.
557 For kernel developers, the most important changes are that the
558 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
559 and this lock has been downgraded to a non-recursive mutex.
561 Transport protocols (UDP, Raw IP) are now responsible for filtering
562 inbound multicast traffic according to group membership and source
563 filters. The imo_multicast_filter() KPI exists for this purpose.
564 Transports which do not use multicast (SCTP, TCP) already reject
565 multicast by default. Forwarding and receive performance may improve
566 as a mutex acquisition is no longer needed in the ip_input()
567 low-level input path. in_addmulti() and in_delmulti() are shimmed
568 to new KPIs which exist to support SSM in-kernel.
570 For application developers, it is recommended that loopback of
571 multicast datagrams be disabled for best performance, as this
572 will still cause the lock to be taken for each looped-back
573 datagram transmission. The net.inet.ip.mcast.loop sysctl may
574 be tuned to 0 to disable loopback by default; it defaults to 1
575 to preserve the existing behaviour.
577 For systems administrators, to obtain best performance with
578 multicast reception and multiple groups, it is always recommended
579 that a card with a suitably precise hash filter is used. Hash
580 collisions will still result in the lock being taken within the
581 transport protocol input path to check group membership.
583 If deploying FreeBSD in an environment with IGMP snooping switches,
584 it is recommended that the net.inet.igmp.sendlocal sysctl remain
585 enabled; this forces 224.0.0.0/24 group membership to be announced
588 The size of 'struct igmpstat' has changed; netstat needs to be
589 recompiled to reflect this.
590 Bump __FreeBSD_version to 800070.
593 libusb20.so.1 is now installed as libusb.so.1 and the ports system
594 updated to use it. This requires a buildworld/installworld in order to
595 update the library and dependencies (usbconfig, etc). Its advisable to
596 rebuild all ports which uses libusb. More specific directions are given
597 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
598 libusb are no longer required and can be removed.
601 A workaround is committed to allow the creation of System V shared
602 memory segment of size > 2 GB on the 64-bit architectures.
603 Due to a limitation of the existing ABI, the shm_segsz member
604 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
605 wrong for large segments. Note that limits must be explicitly
606 raised to allow such segments to be created.
609 The layout of struct ifnet has changed, requiring a rebuild of all
610 network device driver modules.
613 The /dev handling for the new USB stack has changed, a
614 buildworld/installworld is required for libusb20.
617 The new USB2 stack has now been permanently moved in and all kernel and
618 module names reverted to their previous values (eg, usb, ehci, ohci,
619 ums, ...). The old usb stack can be compiled in by prefixing the name
620 with the letter 'o', the old usb modules have been removed.
621 Updating entry 20090216 for xorg and 20090215 for libmap may still
625 The rc.conf(5) option if_up_delay has been renamed to
626 defaultroute_delay to better reflect its purpose. If you have
627 customized this setting in /etc/rc.conf you need to update it to
631 xorg 7.4 wants to configure its input devices via hald which does not
632 yet work with USB2. If the keyboard/mouse does not work in xorg then
634 Option "AllowEmptyInput" "off"
635 to your ServerLayout section. This will cause X to use the configured
636 kbd and mouse sections from your xorg.conf.
639 The GENERIC kernels for all architectures now default to the new USB2
640 stack. No kernel config options or code have been removed so if a
641 problem arises please report it and optionally revert to the old USB
642 stack. If you are loading USB kernel modules or have a custom kernel
643 that includes GENERIC then ensure that usb names are also changed over,
644 eg uftdi -> usb2_serial_ftdi.
646 Older programs linked against the ports libusb 0.1 need to be
647 redirected to the new stack's libusb20. /etc/libmap.conf can
649 # Map old usb library to new one for usb2 stack
650 libusb-0.1.so.8 libusb20.so.1
653 All USB ethernet devices now attach as interfaces under the name ueN
654 (eg. ue0). This is to provide a predictable name as vendors often
655 change usb chipsets in a product without notice.
658 The ichsmb(4) driver has been changed to require SMBus slave
659 addresses be left-justified (xxxxxxx0b) rather than right-justified.
660 All of the other SMBus controller drivers require left-justified
661 slave addresses, so this change makes all the drivers provide the
665 INET6 statistics (struct ip6stat) was updated.
666 netstat(1) needs to be recompiled.
669 NTFS has been removed from GENERIC kernel on amd64 to match
670 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
671 will load ntfs.ko module automatically when NTFS support is
672 actually needed, unless ntfs.ko is not installed or security
673 level prohibits loading kernel modules. If either is the case,
674 "options NTFS" has to be added into kernel config.
677 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
678 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
679 800061. User space tools that rely on the size of struct tcpcb in
680 tcp_var.h (e.g. sockstat) need to be recompiled.
683 ng_tty(4) module updated to match the new TTY subsystem.
684 Due to API change, user-level applications must be updated.
685 New API support added to mpd5 CVS and expected to be present
686 in next mpd5.3 release.
689 With __FreeBSD_version 800060 the makefs tool is part of
690 the base system (it was a port).
693 The afdata and ifnet locks have been changed from mutexes to
694 rwlocks, network modules will need to be re-compiled.
697 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
698 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
699 The new code reduced struct rtentry{} by 16 bytes on 32-bit
700 architecture and 40 bytes on 64-bit architecture. The userland
701 applications "arp" and "ndp" have been updated accordingly.
702 The output from "netstat -r" shows only routing entries and
703 none of the L2 information.
706 __FreeBSD_version 800057 marks the switchover from the
707 binary ath hal to source code. Users must add the line:
709 options AH_SUPPORT_AR5416
711 to their kernel config files when specifying:
715 The ath_hal module no longer exists; the code is now compiled
716 together with the driver in the ath module. It is now
717 possible to tailor chip support (i.e. reduce the set of chips
718 and thereby the code size); consult ath_hal(4) for details.
721 __FreeBSD_version 800054 adds memory barriers to
722 <machine/atomic.h>, new interfaces to ifnet to facilitate
723 multiple hardware transmit queues for cards that support
724 them, and a lock-less ring-buffer implementation to
725 enable drivers to more efficiently manage queueing of
729 A new version of ZFS (version 13) has been merged to -HEAD.
730 This version has zpool attribute "listsnapshots" off by
731 default, which means "zfs list" does not show snapshots,
732 and is the same as Solaris behavior.
735 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
738 The uhci, ohci, ehci and slhci USB Host controller drivers have
739 been put into separate modules. If you load the usb module
740 separately through loader.conf you will need to load the
741 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
742 controller add the following to loader.conf:
748 The ABI used by the PMC toolset has changed. Please keep
749 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
753 atapci kernel module now includes only generic PCI ATA
754 driver. AHCI driver moved to ataahci kernel module.
755 All vendor-specific code moved into separate kernel modules:
756 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
757 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
758 atamarvell, atamicron, atanational, atanetcell, atanvidia,
759 atapromise, ataserverworks, atasiliconimage, atasis, atavia
762 The TTY subsystem of the kernel has been replaced by a new
763 implementation, which provides better scalability and an
764 improved driver model. Most common drivers have been migrated to
765 the new TTY subsystem, while others have not. The following
766 drivers have not yet been ported to the new TTY layer:
769 cy, digi, rc, rp, sio
775 ng_h4, ng_tty, ppp, sl, snp
777 Adding these drivers to your kernel configuration file shall
778 cause compilation to fail.
781 ntpd has been upgraded to 4.2.4p5.
784 OpenSSH has been upgraded to 5.1p1.
786 For many years, FreeBSD's version of OpenSSH preferred DSA
787 over RSA for host and user authentication keys. With this
788 upgrade, we've switched to the vendor's default of RSA over
789 DSA. This may cause upgraded clients to warn about unknown
790 host keys even for previously known hosts. Users should
791 follow the usual procedure for verifying host keys before
792 accepting the RSA key.
794 This can be circumvented by setting the "HostKeyAlgorithms"
795 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
798 Please note that the sequence of keys offered for
799 authentication has been changed as well. You may want to
800 specify IdentityFile in a different order to revert this
804 The sio(4) driver has been removed from the i386 and amd64
805 kernel configuration files. This means uart(4) is now the
806 default serial port driver on those platforms as well.
808 To prevent collisions with the sio(4) driver, the uart(4) driver
809 uses different names for its device nodes. This means the
810 onboard serial port will now most likely be called "ttyu0"
811 instead of "ttyd0". You may need to reconfigure applications to
812 use the new device names.
814 When using the serial port as a boot console, be sure to update
815 /boot/device.hints and /etc/ttys before booting the new kernel.
816 If you forget to do so, you can still manually specify the hints
817 at the loader prompt:
819 set hint.uart.0.at="isa"
820 set hint.uart.0.port="0x3F8"
821 set hint.uart.0.flags="0x10"
822 set hint.uart.0.irq="4"
826 The gpt(8) utility has been removed. Use gpart(8) to partition
830 The version that Linuxulator emulates was changed from 2.4.2
831 to 2.6.16. If you experience any problems with Linux binaries
832 please try to set sysctl compat.linux.osrelease to 2.4.2 and
833 if it fixes the problem contact emulation mailing list.
836 ISDN4BSD (I4B) was removed from the src tree. You may need to
837 update a your kernel configuration and remove relevant entries.
840 I have checked in code to support multiple routing tables.
841 See the man pages setfib(1) and setfib(2).
842 This is a hopefully backwards compatible version,
843 but to make use of it you need to compile your kernel
844 with options ROUTETABLES=2 (or more up to 16).
847 The 802.11 wireless support was redone to enable multi-bss
848 operation on devices that are capable. The underlying device
849 is no longer used directly but instead wlanX devices are
850 cloned with ifconfig. This requires changes to rc.conf files.
852 ifconfig_ath0="WPA DHCP"
855 ifconfig_wlan0="WPA DHCP"
856 see rc.conf(5) for more details. In addition, mergemaster of
857 /etc/rc.d is highly recommended. Simultaneous update of userland
858 and kernel wouldn't hurt either.
860 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
861 modules were merged into the base wlan module. All references
862 to these modules (e.g. in kernel config files) must be removed.
865 psm(4) has gained write(2) support in native operation level.
866 Arbitrary commands can be written to /dev/psm%d and status can
867 be read back from it. Therefore, an application is responsible
868 for status validation and error recovery. It is a no-op in
869 other operation levels.
872 Support for KSE threading has been removed from the kernel. To
873 run legacy applications linked against KSE libmap.conf may
874 be used. The following libmap.conf may be used to ensure
875 compatibility with any prior release:
877 libpthread.so.1 libthr.so.1
878 libpthread.so.2 libthr.so.2
879 libkse.so.3 libthr.so.3
882 The layout of struct vmspace has changed. This affects libkvm
883 and any executables that link against libkvm and use the
884 kvm_getprocs() function. In particular, but not exclusively,
885 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
886 The effects are minimal, but it's advisable to upgrade world
890 The latest em driver no longer has support in it for the
891 82575 adapter, this is now moved to the igb driver. The
892 split was done to make new features that are incompatible
893 with older hardware easier to do.
896 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
897 likewise the kernel option is now GEOM_LINUX_LVM.
900 The default NFS mount mode has changed from UDP to TCP for
901 increased reliability. If you rely on (insecurely) NFS
902 mounting across a firewall you may need to update your
906 Belatedly note the addition of m_collapse for compacting
910 The fts(3) structures have been changed to use adequate
911 integer types for their members and so to be able to cope
912 with huge file trees. The old fts(3) ABI is preserved
913 through symbol versioning in libc, so third-party binaries
914 using fts(3) should still work, although they will not take
915 advantage of the extended types. At the same time, some
916 third-party software might fail to build after this change
917 due to unportable assumptions made in its source code about
918 fts(3) structure members. Such software should be fixed
919 by its vendor or, in the worst case, in the ports tree.
920 FreeBSD_version 800015 marks this change for the unlikely
921 case that a portable fix is impossible.
924 To upgrade to -current after this date, you must be running
925 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
926 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
929 The ADAPTIVE_GIANT kernel option has been retired because its
930 functionality is the default now.
933 The AT keyboard emulation of sunkbd(4) has been turned on
934 by default. In order to make the special symbols of the Sun
935 keyboards driven by sunkbd(4) work under X these now have
936 to be configured the same way as Sun USB keyboards driven
937 by ukbd(4) (which also does AT keyboard emulation), f.e.:
939 Option "XkbLayout" "us"
940 Option "XkbRules" "xorg"
941 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
944 It has been decided that it is desirable to provide ABI
945 backwards compatibility to the FreeBSD 4/5/6 versions of the
946 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
947 broken with the introduction of PCI domain support (see the
948 20070930 entry). Unfortunately, this required the ABI of
949 PCIOCGETCONF to be broken again in order to be able to
950 provide backwards compatibility to the old version of that
951 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
952 again. As for prominent ports this affects neither pciutils
953 nor xorg-server this time, the hal port needs to be rebuilt
957 The misnamed kthread_create() and friends have been renamed
958 to kproc_create() etc. Many of the callers already
960 I will return kthread_create() and friends in a while
961 with implementations that actually create threads, not procs.
962 Renaming corresponds with version 800002.
968 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
969 WITHOUT_LIBTHR are set.
972 The PCI code has been made aware of PCI domains. This means that
973 the location strings as used by pciconf(8) etc are now in the
974 following format: pci<domain>:<bus>:<device>[:<function>]. It
975 also means that consumers of <sys/pciio.h> potentially need to
976 be recompiled; this includes the hal and xorg-server ports.
979 The caching daemon (cached) was renamed to nscd. nscd.conf
980 configuration file should be used instead of cached.conf and
981 nscd_enable, nscd_pidfile and nscd_flags options should be used
982 instead of cached_enable, cached_pidfile and cached_flags in
986 The getfacl(1) utility now prints owning user and group name
987 instead of owning uid and gid in the three line comment header.
988 This is the same behavior as getfacl(1) on Solaris and Linux.
991 The new IPsec code is now compiled in using the IPSEC option. The
992 IPSEC option now requires "device crypto" be defined in your kernel
993 configuration. The FAST_IPSEC kernel option is now deprecated.
996 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
997 note the changed syntax - keep state is now on by default. Also
998 note the fact that ftp-proxy(8) has been changed from bottom up and
999 has been moved from libexec to usr/sbin. Changes in the ALTQ
1000 handling also affect users of IPFW's ALTQ capabilities.
1003 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
1004 only IPsec supported by FreeBSD. The new IPsec stack
1005 supports both IPv4 and IPv6. The kernel option will change
1006 after the code changes have settled in. For now the kernel
1007 option IPSEC is deprecated and FAST_IPSEC is the only option, that
1008 will change after some settling time.
1011 The wicontrol(8) utility has been removed from the base system. wi(4)
1012 cards should be configured using ifconfig(8), see the man page for more
1016 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
1017 instead of the nve(4) driver. Please update your configuration
1021 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
1022 database if it is missing or older than the aliases file. If
1023 desired, set the new rc.conf option sendmail_rebuild_aliases
1024 to "YES" to restore that functionality.
1027 The IPv4 multicast socket code has been considerably modified, and
1028 moved to the file sys/netinet/in_mcast.c. Initial support for the
1029 RFC 3678 Source-Specific Multicast Socket API has been added to
1030 the IPv4 network stack.
1032 Strict multicast and broadcast reception is now the default for
1033 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
1034 has now been removed.
1036 The RFC 1724 hack for interface selection has been removed; the use
1037 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
1038 been added to replace it. Consumers such as routed will soon be
1039 updated to reflect this.
1041 These changes affect users who are running routed(8) or rdisc(8)
1042 from the FreeBSD base system on point-to-point or unnumbered
1046 The net80211 layer has changed significantly and all wireless
1047 drivers that depend on it need to be recompiled. Further these
1048 changes require that any program that interacts with the wireless
1049 support in the kernel be recompiled; this includes: ifconfig,
1050 wpa_supplicant, hostapd, and wlanstats. Users must also, for
1051 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
1052 if they use modules for wireless support. These modules implement
1053 scanning support for station and ap modes, respectively. Failure
1054 to load the appropriate module before marking a wireless interface
1055 up will result in a message to the console and the device not
1059 The pam_nologin(8) module ceases to provide an authentication
1060 function and starts providing an account management function.
1061 Consequent changes to /etc/pam.d should be brought in using
1062 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
1063 need manual editing as follows. Locate this line (or similar):
1065 auth required pam_nologin.so no_warn
1067 and change it according to this example:
1069 account required pam_nologin.so no_warn
1071 That is, the first word needs to be changed from "auth" to
1072 "account". The new line can be moved to the account section
1073 within the file for clarity. Not updating pam.conf(5) files
1074 will result in nologin(5) ignored by the respective services.
1077 The ether_ioctl() function has been synchronized with ioctl(2)
1078 and ifnet.if_ioctl. Due to that, the size of one of its arguments
1079 has changed on 64-bit architectures. All kernel modules using
1080 ether_ioctl() need to be rebuilt on such architectures.
1083 Improved INCLUDE_CONFIG_FILE support has been introduced to the
1084 config(8) utility. In order to take advantage of this new
1085 functionality, you are expected to recompile and install
1086 src/usr.sbin/config. If you don't rebuild config(8), and your
1087 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
1088 build will be broken because of a missing "kernconfstring"
1092 Symbol versioning is enabled by default. To disable it, use
1093 option WITHOUT_SYMVER. It is not advisable to attempt to
1094 disable symbol versioning once it is enabled; your installworld
1095 will break because a symbol version-less libc will get installed
1096 before the install tools. As a result, the old install tools,
1097 which previously had symbol dependencies to FBSD_1.0, will fail
1098 because the freshly installed libc will not have them.
1100 The default threading library (providing "libpthread") has been
1101 changed to libthr. If you wish to have libkse as your default,
1102 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
1105 The ABI breakage in sendmail(8)'s libmilter has been repaired
1106 so it is no longer necessary to recompile mail filters (aka,
1107 milters). If you recompiled mail filters after the 20070408
1108 note, it is not necessary to recompile them again.
1111 The new trunk(4) driver has been renamed to lagg(4) as it better
1112 reflects its purpose. ifconfig will need to be recompiled.
1115 sendmail(8) has been updated to version 8.14.1. Mail filters
1116 (aka, milters) compiled against the libmilter included in the
1117 base operating system should be recompiled.
1120 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
1121 In order to use them one must agree to the respective LICENSE in
1122 share/doc/legal and define legal.intel_<name>.license_ack=1 via
1123 loader.conf(5) or kenv(1). Make sure to deinstall the now
1124 deprecated modules from the respective firmware ports.
1127 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
1128 were removed from FreeBSD's libc. These originally came from INRIA
1129 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
1130 deprecated in previous releases.
1131 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
1132 replace it as a more portable (and re-entrant) API.
1135 To support interrupt filtering a modification to the newbus API
1136 has occurred, ABI was broken and __FreeBSD_version was bumped
1137 to 700031. Please make sure that your kernel and modules are in
1138 sync. For more info:
1139 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
1142 The IPv6 multicast forwarding code may now be loaded into GENERIC
1143 kernels by loading the ip_mroute.ko module. This is built into the
1144 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
1145 set; see src.conf(5) for more information.
1148 The output of netstat -r has changed. Without -n, we now only
1149 print a "network name" without the prefix length if the network
1150 address and mask exactly match a Class A/B/C network, and an entry
1151 exists in the nsswitch "networks" map.
1152 With -n, we print the full unabbreviated CIDR network prefix in
1153 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
1154 This change is in preparation for changes such as equal-cost
1155 multipath, and to more generally assist operational deployment
1156 of FreeBSD as a modern IPv4 router.
1159 PIM has been turned on by default in the IPv4 multicast
1160 routing code. The kernel option 'PIM' has now been removed.
1161 PIM is now built by default if option 'MROUTING' is specified.
1162 It may now be loaded into GENERIC kernels by loading the
1163 ip_mroute.ko module.
1166 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
1167 has been removed. Its functionality may be achieved by explicitly
1168 configuring gif(4) interfaces and using the 'phyint' keyword in
1170 XORP does not support source-routed IPv4 multicast tunnels nor the
1171 integrated IPIP tunneling, therefore it is not affected by this
1172 change. The __FreeBSD_version macro has been bumped to 700030.
1175 Support for PCI Message Signalled Interrupts has been
1176 re-enabled in the bge driver, only for those chips which are
1177 believed to support it properly. If there are any problems,
1178 MSI can be disabled completely by setting the
1179 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
1183 Support for PCI Message Signalled Interrupts has been
1184 disabled again in the bge driver. Many revisions of the
1185 hardware fail to support it properly. Support can be
1186 re-enabled by removing the #define of BGE_DISABLE_MSI in
1187 "src/sys/dev/bge/if_bge.c".
1190 Support for PCI Message Signalled Interrupts has been added
1191 to the bge driver. If there are any problems, MSI can be
1192 disabled completely by setting the 'hw.pci.enable_msi' and
1193 'hw.pci.enable_msix' tunables to 0 in the loader.
1196 The removal of several facets of the experimental Threading
1197 system from the kernel means that the proc and thread structures
1198 have changed quite a bit. I suggest all kernel modules that might
1199 reference these structures be recompiled.. Especially the
1203 Sound infrastructure has been updated with various fixes and
1204 improvements. Most of the changes are pretty much transparent,
1205 with exceptions of followings:
1206 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
1207 moved to their own dev sysctl nodes, for example:
1208 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
1209 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
1210 own chardev in the form of "dsp%d.<function>%d", where <function>
1211 is p = playback, r = record and v = virtual, respectively. Users
1212 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
1213 This does not affect those who are using "/dev/dsp".
1216 geom(4)'s gmirror(8) class metadata structure has been
1217 rev'd from v3 to v4. If you update across this point and
1218 your metadata is converted for you, you will not be easily
1219 able to downgrade since the /boot/kernel.old/geom_mirror.ko
1220 kernel module will be unable to read the v4 metadata. You
1221 can resolve this by doing from the loader(8) prompt:
1223 set vfs.root.mountfrom="ufs:/dev/XXX"
1225 where XXX is the root slice of one of the disks that composed
1226 the mirror (i.e.: /dev/ad0s1a). You can then rebuild
1227 the array the same way you built it originally.
1230 The following binaries have been disconnected from the build:
1231 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
1232 and mount_std. The functionality of these programs has been
1233 moved into the mount program. For example, to mount a devfs
1234 filesystem, instead of using mount_devfs, use: "mount -t devfs".
1235 This does not affect entries in /etc/fstab, since entries in
1236 /etc/fstab are always processed with "mount -t fstype".
1239 Support for PCI Message Signalled Interrupts on i386 and amd64
1240 has been added to the kernel and various drivers will soon be
1241 updated to use MSI when it is available. If there are any problems,
1242 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
1243 and 'hw.pci.enable_msix' tunables to 0 in the loader.
1246 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
1247 The lockmgr object layout has been changed as a result of having
1248 a lock_object embedded in it. As a consequence all file system
1249 kernel modules must be re-compiled. The mutex profiling man page
1250 has not yet been updated to reflect this change.
1253 KSE in the kernel has now been made optional and turned on by
1254 default. Use 'nooption KSE' in your kernel config to turn it
1255 off. All kernel modules *must* be recompiled after this change.
1256 There-after, modules from a KSE kernel should be compatible with
1257 modules from a NOKSE kernel due to the temporary padding fields
1258 added to 'struct proc'.
1261 mrouted and its utilities have been removed from the base system.
1264 Some ioctl(2) command codes have changed. Full backward ABI
1265 compatibility is provided if the "options COMPAT_FREEBSD6" is
1266 present in the kernel configuration file. Make sure to add
1267 this option to your kernel config file, or recompile X.Org
1268 and the rest of ports; otherwise they may refuse to work.
1271 tcpslice has been removed from the base system.
1274 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
1275 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
1276 systat needs to be rebuilt.
1279 libpcap updated to v0.9.4 and tcpdump to v3.9.4
1282 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
1283 for IPFIREWALL_FORWARD is now as it was before when it was first
1284 committed and for years after. The behaviour is now ON.
1287 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
1288 Now it can decrypt files created from different architectures.
1289 Unfortunately, it is no longer able to decrypt a cipher text
1290 generated with an older version on 64 bit architectures.
1291 If you have such a file, you need old utility to decrypt it.
1294 The interface version of the i4b kernel part has changed. So
1295 after updating the kernel sources and compiling a new kernel,
1296 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
1297 be rebuilt, and vice versa.
1300 The XBOX kernel now defaults to the nfe(4) driver instead of
1301 the nve(4) driver. Please update your configuration
1305 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
1306 PCnet family of NICs has been removed. The new le(4) driver serves
1307 as an equivalent but cross-platform replacement with the pcn(4)
1308 driver still providing performance-optimized support for the subset
1309 of AMD Am79C971 PCnet-FAST and greater chips as before.
1312 The machdep.* sysctls and the adjkerntz utility have been
1313 modified a bit. The new adjkerntz utility uses the new
1314 sysctl names and sysctlbyname() calls, so it may be impossible
1315 to run an old /sbin/adjkerntz utility in single-user mode
1316 with a new kernel. Replace the `adjkerntz -i' step before
1317 `make installworld' with:
1319 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
1321 and proceed as usual with the rest of the installworld-stage
1322 steps. Otherwise, you risk installing binaries with their
1323 timestamp set several hours in the future, especially if
1324 you are running with local time set to GMT+X hours.
1327 The ip6fw utility has been removed. The behavior provided by
1328 ip6fw has been in ipfw2 for a good while and the rc.d scripts
1329 have been updated to deal with it. There are some rules that
1330 might not migrate cleanly. Use rc.firewall6 as a template to
1334 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
1335 attachments have been removed. Make sure to configure scc(4)
1336 on sparc64. Note also that by default puc(4) will use uart(4)
1337 and not sio(4) for serial ports because interrupt handling has
1338 been optimized for multi-port serial cards and only uart(4)
1339 implements the interface to support it.
1342 The scc(4) driver replaces puc(4) for Serial Communications
1343 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
1344 Z8530. On sparc64, it is advised to add scc(4) to the kernel
1345 configuration to make sure that the serial ports remain
1349 Most world/kernel related NO_* build options changed names.
1350 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
1351 after FreeBSD ports) and should be set in /etc/src.conf
1352 (the src.conf(5) manpage is provided). Full backwards
1353 compatibility is maintained for the time being though it's
1354 highly recommended to start moving old options out of the
1355 system-wide /etc/make.conf file into the new /etc/src.conf
1356 while also properly renaming them. More conversions will
1357 likely follow. Posting to current@:
1359 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
1362 The NETSMBCRYPTO kernel option has been retired because its
1363 functionality is always included in NETSMB and smbfs.ko now.
1366 The TDFX_LINUX kernel option was retired and replaced by the
1367 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
1368 kernel module. Loading it alone should suffice to get 3dfx support
1369 for Linux apps because it will pull in 3dfx.ko and linux.ko through
1373 The 'audit' group was added to support the new auditing functionality
1374 in the base system. Be sure to follow the directions for updating,
1375 including the requirement to run mergemaster -p.
1378 The kernel ABI to file system modules was changed on i386.
1379 Please make sure that your kernel and modules are in sync.
1382 This actually occured some time ago, but installing the kernel
1383 now also installs a bunch of symbol files for the kernel modules.
1384 This increases the size of /boot/kernel to about 67Mbytes. You
1385 will need twice this if you will eventually back this up to kernel.old
1386 on your next install.
1387 If you have a shortage of room in your root partition, you should add
1388 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
1389 to your /etc/make.conf.
1392 libc's malloc implementation has been replaced. This change has the
1393 potential to uncover application bugs that previously went unnoticed.
1394 See the malloc(3) manual page for more details.
1397 The generic netgraph(4) cookie has been changed. If you upgrade
1398 kernel passing this point, you also need to upgrade userland
1399 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
1402 si(4)'s device files now contain the unit number.
1403 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
1406 The kernel ABI was mostly destroyed due to a change in the size
1407 of struct lock_object which is nested in other structures such
1408 as mutexes which are nested in all sorts of other structures.
1409 Make sure your kernel and modules are in sync.
1412 The page coloring algorithm in the VM subsystem was converted
1413 from tuning with kernel options to autotuning. Please remove
1414 any PQ_* option except PQ_NOOPT from your kernel config.
1417 The net80211-related tools in the tools/tools/ath directory
1418 have been moved to tools/tools/net80211 and renamed with a
1419 "wlan" prefix. Scripts that use them should be adjusted
1423 Scripts in the local_startup directories (as defined in
1424 /etc/defaults/rc.conf) that have the new rc.d semantics will
1425 now be run as part of the base system rcorder. If there are
1426 errors or problems with one of these local scripts, it could
1427 cause boot problems. If you encounter such problems, boot in
1428 single user mode, remove that script from the */rc.d directory.
1429 Please report the problem to the port's maintainer, and the
1430 freebsd-ports@freebsd.org mailing list.
1433 The nodev mount option was deprecated in RELENG_6 (where it
1434 was a no-op), and is now unsupported. If you have nodev or dev listed
1435 in /etc/fstab, remove it, otherwise it will result in a mount error.
1438 ABI between ipfw(4) and ipfw(8) has been changed. You need
1439 to rebuild ipfw(8) when rebuilding kernel.
1442 rp(4)'s device files now contain the unit number.
1443 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
1446 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
1447 Its /etc/rc.conf.d configuration file has been `ppp' from
1448 the beginning, and hence there is no need to touch it.
1451 Now most modules get their build-time options from the kernel
1452 configuration file. A few modules still have fixed options
1453 due to their non-conformant implementation, but they will be
1454 corrected eventually. You may need to review the options of
1455 the modules in use, explicitly specify the non-default options
1456 in the kernel configuration file, and rebuild the kernel and
1460 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
1461 to turn polling(4) on your interfaces.
1464 The old bridge(4) implementation was retired. The new
1465 if_bridge(4) serves as a full functional replacement.
1468 The ai_addrlen of a struct addrinfo was changed to a socklen_t
1469 to conform to POSIX-2001. This change broke an ABI
1470 compatibility on 64 bit architecture. You have to recompile
1471 userland programs that use getaddrinfo(3) on 64 bit
1475 RELENG_6 branched here.
1478 The pccard_ifconfig rc.conf variable has been removed and a new
1479 variable, ifconfig_DEFAULT has been introduced. Unlike
1480 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
1481 do not have ifconfig_ifn entries rather than just those in
1482 removable_interfaces.
1485 Some previous versions of PAM have permitted the use of
1486 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
1487 to third party PAM modules in /usr/local/lib. A change has been
1488 made to require the use of absolute paths in order to avoid
1489 ambiguity and dependence on library path configuration, which may
1490 affect existing configurations.
1493 Major changes to network interface API. All drivers must be
1494 recompiled. Drivers not in the base system will need to be
1495 updated to the new APIs.
1498 Changes were made to kinfo_proc in sys/user.h. Please recompile
1499 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
1500 will not behave correctly.
1502 The API and ABI for hwpmc(4) have changed with the addition
1503 of sampling support. Please recompile lib/libpmc(3) and
1504 usr.sbin/{pmcstat,pmccontrol}.
1507 The OpenBSD dhclient was imported in place of the ISC dhclient
1508 and the network interface configuration scripts were updated
1509 accordingly. If you use DHCP to configure your interfaces, you
1510 must now run devd. Also, DNS updating was lost so you will need
1511 to find a workaround if you use this feature.
1513 The '_dhcp' user was added to support the OpenBSD dhclient. Be
1514 sure to run mergemaster -p (like you are supposed to do every time
1518 if_bridge was added to the tree. This has changed struct ifnet.
1519 Please recompile userland and all network related modules.
1522 The n_net of a struct netent was changed to an uint32_t, and
1523 1st argument of getnetbyaddr() was changed to an uint32_t, to
1524 conform to POSIX-2001. These changes broke an ABI
1525 compatibility on 64 bit architecture. With these changes,
1526 shlib major of libpcap was bumped. You have to recompile
1527 userland programs that use getnetbyaddr(3), getnetbyname(3),
1528 getnetent(3) and/or libpcap on 64 bit architecture.
1531 Kernel parsing of extra options on '#!' first lines of shell
1532 scripts has changed. Lines with multiple options likely will
1533 fail after this date. For full details, please see
1534 http://people.freebsd.org/~gad/Updating-20050528.txt
1537 The packet filter (pf) code has been updated to OpenBSD 3.7
1538 Please note the changed anchor syntax and the fact that
1539 authpf(8) now needs a mounted fdescfs(5) to function.
1542 The NO_MIXED_MODE kernel option has been removed from the i386
1543 amd64 platforms as its use has been superceded by the new local
1544 APIC timer code. Any kernel config files containing this option
1548 The on-disk format of LC_CTYPE files was changed to be machine
1549 independent. Please make sure NOT to use NO_CLEAN buildworld
1550 when crossing this point. Crossing this point also requires
1551 recompile or reinstall of all locale depended packages.
1554 The ifi_epoch member of struct if_data has been changed to
1555 contain the uptime at which the interface was created or the
1556 statistics zeroed rather then the wall clock time because
1557 wallclock time may go backwards. This should have no impact
1558 unless an snmp implementation is using this value (I know of
1559 none at this point.)
1562 The acpi_perf and acpi_throttle drivers are now part of the
1563 acpi(4) main module. They are no longer built separately.
1566 The layout of struct image_params has changed. You have to
1567 recompile all compatibility modules (linux, svr4, etc) for use
1568 with the new kernel.
1571 The p4tcc driver has been merged into cpufreq(4). This makes
1572 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
1573 compile in "device cpufreq" to restore this functionality.
1576 The responsibility of recomputing the file system summary of
1577 a SoftUpdates-enabled dirty volume has been transferred to the
1578 background fsck. A rebuild of fsck(8) utility is recommended
1579 if you have updated the kernel.
1581 To get the old behavior (recompute file system summary at mount
1582 time), you can set vfs.ffs.compute_summary_at_mount=1 before
1583 mounting the new volume.
1586 The cpufreq import is complete. As part of this, the sysctls for
1587 acpi(4) throttling have been removed. The power_profile script
1588 has been updated, so you can use performance/economy_cpu_freq in
1589 rc.conf(5) to set AC on/offline cpu frequencies.
1592 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
1593 requires recompiling libnetgraph and userland netgraph utilities.
1596 Support for abbreviated forms of a number of ipfw options is
1597 now deprecated. Warnings are printed to stderr indicating the
1598 correct full form when a match occurs. Some abbreviations may
1599 be supported at a later date based on user feedback. To be
1600 considered for support, abbreviations must be in use prior to
1601 this commit and unlikely to be confused with current key words.
1604 By a popular demand, a lot of NOFOO options were renamed
1605 to NO_FOO (see bsd.compat.mk for a full list). The old
1606 spellings are still supported, but will cause annoying
1607 warnings on stderr. Make sure you upgrade properly (see
1608 the COMMON ITEMS: section later in this file).
1611 Auto-loading of ancillary wlan modules such as wlan_wep has
1612 been temporarily disabled; you need to statically configure
1613 the modules you need into your kernel or explicitly load them
1614 prior to use. Specifically, if you intend to use WEP encryption
1615 with an 802.11 device load/configure wlan_wep; if you want to
1616 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
1617 and wlan_xauth as required.
1620 The behaviour of ppp(8) has changed slightly. If lqr is enabled
1621 (``enable lqr''), older versions would revert to LCP ECHO mode on
1622 negotiation failure. Now, ``enable echo'' is required for this
1623 behaviour. The ppp version number has been bumped to 3.4.2 to
1627 The wlan support has been updated to split the crypto support
1628 into separate modules. For static WEP you must configure the
1629 wlan_wep module in your system or build and install the module
1630 in place where it can be loaded (the kernel will auto-load
1631 the module when a wep key is configured).
1634 The ath driver has been updated to split the tx rate control
1635 algorithm into a separate module. You need to include either
1636 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
1639 Support for systems with an 80386 CPU has been removed. Please
1640 use FreeBSD 5.x or earlier on systems with an 80386.
1643 We have had a hack which would mount the root filesystem
1644 R/W if the device were named 'md*'. As part of the vnode
1645 work I'm doing I have had to remove this hack. People
1646 building systems which use preloaded MD root filesystems
1647 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
1648 their /etc/rc scripts.
1651 FreeBSD 5.3 shipped here.
1654 The size of struct tcpcb has changed again due to the removal
1655 of RFC1644 T/TCP. You have to recompile userland programs that
1656 read kmem for tcp sockets directly (netstat, sockstat, etc.)
1659 The size of struct tcpcb has changed. You have to recompile
1660 userland programs that read kmem for tcp sockets directly
1661 (netstat, sockstat, etc.)
1664 RELENG_5 branched here. For older entries, please see updating
1665 in the RELENG_5 branch.
1671 Avoid using make -j when upgrading. From time to time in the
1672 past there have been problems using -j with buildworld and/or
1673 installworld. This is especially true when upgrading between
1674 "distant" versions (eg one that cross a major release boundary
1675 or several minor releases, or when several months have passed
1676 on the -current branch).
1678 Sometimes, obscure build problems are the result of environment
1679 poisoning. This can happen because the make utility reads its
1680 environment when searching for values for global variables.
1681 To run your build attempts in an "environmental clean room",
1682 prefix all make commands with 'env -i '. See the env(1) manual
1683 page for more details.
1685 When upgrading from one major version to another it is generally
1686 best to upgrade to the latest code in the currently installed branch
1687 first, then do an upgrade to the new branch. This is the best-tested
1688 upgrade path, and has the highest probability of being successful.
1689 Please try this approach before reporting problems with a major
1694 When upgrading the boot ZFS pool to a new version, always follow
1697 1.) recompile and reinstall the ZFS boot loader and boot block
1698 (this is part of "make buildworld" and "make installworld")
1700 2.) update the ZFS boot block on your boot drive
1702 The following example updates the ZFS boot block on the first
1703 partition (freebsd-boot) of a GPT partitioned drive ad0:
1704 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1706 Non-boot pools do not need these updates.
1710 If you are updating from a prior version of FreeBSD (even one just
1711 a few days old), you should follow this procedure. It is the most
1712 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1714 make kernel-toolchain
1715 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1716 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1718 To test a kernel once
1719 ---------------------
1720 If you just want to boot a kernel once (because you are not sure
1721 if it works, or if you want to boot a known bad kernel to provide
1722 debugging information) run
1723 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1724 nextboot -k testkernel
1726 To just build a kernel when you know that it won't mess you up
1727 --------------------------------------------------------------
1728 This assumes you are already running a 5.X system. Replace
1729 ${arch} with the architecture of your machine (e.g. "i386",
1730 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1732 cd src/sys/${arch}/conf
1733 config KERNEL_NAME_HERE
1734 cd ../compile/KERNEL_NAME_HERE
1739 If this fails, go to the "To build a kernel" section.
1741 To rebuild everything and install it on the current system.
1742 -----------------------------------------------------------
1743 # Note: sometimes if you are running current you gotta do more than
1744 # is listed here if you are upgrading from a really old current.
1746 <make sure you have good level 0 dumps>
1748 make kernel KERNCONF=YOUR_KERNEL_HERE
1750 <reboot in single user> [3]
1758 To cross-install current onto a separate partition
1759 --------------------------------------------------
1760 # In this approach we use a separate partition to hold
1761 # current's root, 'usr', and 'var' directories. A partition
1762 # holding "/", "/usr" and "/var" should be about 2GB in
1765 <make sure you have good level 0 dumps>
1768 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1769 <maybe newfs current's root partition>
1770 <mount current's root partition on directory ${CURRENT_ROOT}>
1771 make installworld DESTDIR=${CURRENT_ROOT}
1772 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1773 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1774 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1775 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1776 <reboot into current>
1777 <do a "native" rebuild/install as described in the previous section>
1778 <maybe install compatibility libraries from ports/misc/compat*>
1782 To upgrade in-place from 5.x-stable to current
1783 ----------------------------------------------
1784 <make sure you have good level 0 dumps>
1786 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1788 <reboot in single user> [3]
1795 Make sure that you've read the UPDATING file to understand the
1796 tweaks to various things you need. At this point in the life
1797 cycle of current, things change often and you are on your own
1798 to cope. The defaults can also change, so please read ALL of
1799 the UPDATING entries.
1801 Also, if you are tracking -current, you must be subscribed to
1802 freebsd-current@freebsd.org. Make sure that before you update
1803 your sources that you have read and understood all the recent
1804 messages there. If in doubt, please track -stable which has
1805 much fewer pitfalls.
1807 [1] If you have third party modules, such as vmware, you
1808 should disable them at this point so they don't crash your
1811 [3] From the bootblocks, boot -s, and then do
1816 adjkerntz -i # if CMOS is wall time
1817 Also, when doing a major release upgrade, it is required that
1818 you boot into single user mode to do the installworld.
1820 [4] Note: This step is non-optional. Failure to do this step
1821 can result in a significant reduction in the functionality of the
1822 system. Attempting to do it by hand is not recommended and those
1823 that pursue this avenue should read this file carefully, as well
1824 as the archives of freebsd-current and freebsd-hackers mailing lists
1825 for potential gotchas.
1827 [5] Usually this step is a noop. However, from time to time
1828 you may need to do this if you get unknown user in the following
1829 step. It never hurts to do it all the time. You may need to
1830 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1831 install) after the buildworld before this step if you last updated
1832 from current before 20020224 or from -stable before 20020408.
1834 [6] This only deletes old files and directories. Old libraries
1835 can be deleted by "make delete-old-libs", but you have to make
1836 sure that no program is using those libraries anymore.
1838 [8] In order to have a kernel that can run the 4.x binaries
1839 needed to do an installworld, you must include the COMPAT_FREEBSD4
1840 option in your kernel. Failure to do so may leave you with a system
1841 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
1842 is required to run the 5.x binaries on more recent kernels.
1844 Make sure that you merge any new devices from GENERIC since the
1845 last time you updated your kernel config file.
1847 [9] When checking out sources, you must include the -P flag to have
1848 cvs prune empty directories.
1850 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1851 "?=" instead of the "=" assignment operator, so that buildworld can
1852 override the CPUTYPE if it needs to.
1854 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1855 not on the command line, or in /etc/make.conf. buildworld will
1856 warn if it is improperly defined.
1859 This file contains a list, in reverse chronological order, of major
1860 breakages in tracking -current. It is not guaranteed to be a complete
1861 list of such breakages, and only contains entries since October 16, 2004.
1862 If you need to see UPDATING entries from before that date, you will need
1863 to fetch an UPDATING file from an older FreeBSD release.
1865 Copyright information:
1867 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
1869 Redistribution, publication, translation and use, with or without
1870 modification, in full or in part, in any form or format of this
1871 document are permitted without further permission from the author.
1873 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1874 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1875 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1876 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1877 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1878 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1879 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1880 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1881 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1882 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1883 POSSIBILITY OF SUCH DAMAGE.
1885 If you find this document useful, and you want to, you may buy the
1888 Contact Warner Losh if you have any questions about your use of