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 An additional fix for the issue described in the 20150615 sendmail
20 entry below has been been committed in revision 284790.
23 The latest version of openssl rejects TLS handshakes with DH
24 parameters below 768 bits. sendmail releases prior to 8.15.2
25 (not yet released), defaulted to a 512 bit DH parameter setting
26 for client connections. To improve interoperability, the
27 sendmail default for client connections has been raised to
31 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
32 been deprecated and will not be part of FreeBSD 11.0 and later
33 releases. If you use this driver, please consider switching to
34 the nfe(4) driver instead.
37 The behavior of gss_pseudo_random() for the krb5 mechanism
38 has changed, for applications requesting a longer random string
39 than produced by the underlying enctype's pseudo-random() function.
40 In particular, the random string produced from a session key of
41 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
42 be different at the 17th octet and later, after this change.
43 The counter used in the PRF+ construction is now encoded as a
44 big-endian integer in accordance with RFC 4402.
45 __FreeBSD_version is bumped to 804501.
48 Behavior of devfs rules path matching has been changed.
49 Pattern is now always matched against fully qualified devfs
50 path and slash characters must be explicitly matched by
51 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
52 subdirectories must be reviewed.
55 hastctl(8)'s `status' command output changed to terse one-liner format.
56 Scripts using this should switch to `list' command or be rewritten.
59 Added ZFS TRIM support which is enabled by default. To disable
60 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
62 Creating new ZFS pools and adding new devices to existing pools
63 first performs a full device level TRIM, which can take a significant
64 amount of time. Set the sysctl vfs.zfs.vdev.trim_on_init to 0 to
65 disable this behaviour.
67 ZFS TRIM requires the underlying device support BIO_DELETE which
68 is currently provided by methods such as ATA TRIM and SCSI UNMAP
69 via CAM, which are typically supported by SSD's.
71 Stats for ZFS TRIM can be monitored by looking at the sysctl's
72 under kstat.zfs.misc.zio_trim.
78 `list' command has been added to hastctl(8). For now, it is full
79 equivalent of `status' command.
80 WARNING: in the near future the output of hastctl's status command
81 will change to more terse format. If you use `hastctl status'
82 for parsing in your scripts, switch to `hastctl list'.
85 Fix a bug that allows NFS clients to issue READDIR on files.
88 A new compression method (lz4) has been merged. Please refer to
89 zpool-features(7) for more information.
91 Please refer to the "ZFS notes" section of this file for information
92 on upgrading boot ZFS pools.
95 A new version of ZFS (pool version 5000) has been merged to 8-STABLE.
96 Starting with this version the old system of ZFS pool versioning
97 is superseded by "feature flags". This concept enables forward
98 compatibility against certain future changes in functionality of ZFS
99 pools. The first two read-only compatible "feature flags" for ZFS
100 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
101 For more information read the new zpool-features(7) manual page.
102 Please refer to the "ZFS notes" section of this file for information
103 on upgrading boot ZFS pools.
106 WITH_CTF can now be specified in src.conf (not recommended, there
107 are some problems with static executables), make.conf (would also
108 affect ports which do not use GNU make and do not override the
109 compile targets) or in the kernel config (via "makeoptions
111 When WITH_CTF was specified there before this was silently ignored,
112 so make sure that WITH_CTF is not used in places which could lead
113 to unwanted behavior.
116 The random(4) support for the VIA hardware random number
117 generator (`PADLOCK') is no longer enabled unconditionally.
118 Add the PADLOCK_RNG option in the custom kernel config if
119 needed. The GENERIC kernels on i386 and amd64 do include the
120 option, so the change only affects the custom kernel
124 The sparc64 ZFS loader has been changed to no longer try to auto-
125 detect ZFS providers based on diskN aliases but now requires these
126 to be explicitly listed in the OFW boot-device environment variable.
132 A new VOP_ADVISE() was added to support posix_fadvise(2). All
133 filesystem modules must be recompiled.
136 A new VOP_ALLOCATE() was added to support posix_fallocate(2). All
137 filesystem modules must be recompiled.
140 The broken amd(4) driver has been replaced with esp(4) in the amd64,
141 i386 and pc98 GENERIC kernel configuration files.
144 A new version of ZFS (version 28) has been merged.
145 This version does not depend on a python library and the
146 sysutils/py-zfs port is not used anymore.
147 For upgrading your boot pool, please read "ZFS notes"
148 in the COMMON ITEMS: section later in this file.
151 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
152 compliant, and will now use half of hash for authentication.
153 This will break interoperability with all stacks (including all
154 older FreeBSD versions) who implement
155 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
157 The only workaround with such peers is to use another HMAC
158 algorithm for IPsec ("phase 2") authentication.
164 New version of minidump format for amd64 architecture was
165 introduced in r215872. To analyze vmcore files produced by
166 kernels at or after this version you will need updated userland,
167 libkvm actually, that is able to handle the new version.
170 A workaround for a fixed ld bug has been removed in kernel code,
171 so make sure that your system ld is built from sources after
172 revision 211583 from 2010-08-21 (r210245 from 2010-07-19 if
173 building stable/8 kernel on head, r211584 from 2010-08-21 for
174 stable/7). A symptom of incorrect ld version is
175 different addresses for set_pcpu section and __start_set_pcpu
176 symbol in kernel and/or modules.
179 A new version of ZFS (version 15) has been merged.
180 This version uses a python library for the following subcommands:
181 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
182 For full functionality of these commands the following port must
183 be installed: sysutils/py-zfs
189 The config(8) command has been updated to maintain compatibility
190 with config files from 8.0-RELEASE. You will need a new version
191 of config to build kernels (this version can be used from 8.0-RELEASE
192 forward). The buildworld target will generate it, so following
193 the instructions in this file for updating will work glitch-free.
194 Merely doing a make buildkernel without first doing a make buildworld
195 (or kernel-toolchain), or attempting to build a kernel using
196 traidtional methods will generate a config version warning, indicating
200 The rc.firewall and rc.firewall6 were unified, and
201 rc.firewall6 and rc.d/ip6fw were removed.
202 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
203 variables are obsoleted. Instead, the following new rc
204 variables are added to rc.d/ipfw:
206 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
207 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
208 firewall_simple_onet_ipv6
210 The meanings correspond to the relevant IPv4 variables.
213 COMPAT_IA32 has been added as an alias for COMPAT_FREEBSD32. A new
214 version of config(8) is required. The error message when you hit this
215 condition is confusing (COMPAT_FREEBSD32 duplicate option), when it
216 should really say "your config is too old to compile this new kernel."
219 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
220 to allow 32-bit compatibility on non-x86 platforms. All kernel
221 configurations on amd64 and ia64 platforms using these options must
222 be modified accordingly.
225 Introduce the kernel thread "deadlock resolver" (which can be enabled
226 via the DEADLKRES option, see NOTES for more details) and the
227 sleepq_type() function for sleepqueues.
233 802.11s D3.03 support was committed. This is incompatible with
234 the previous code, which was based on D3.0.
237 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
238 mount(8) and -a option for df(1) to see them.
241 Remove the option STOP_NMI. The default action is now to use NMI
242 only for KDB via the newly introduced function stop_cpus_hard()
243 and maintain stop_cpus() to just use a normal IPI_STOP on ia32
250 Bump the shared library version numbers for all libraries that
251 do not use symbol versioning as part of the 8.0-RELEASE cycle.
252 Bump __FreeBSD_version to 800105.
255 Due to changes in the implementation of virtual network stack
256 support, all network-related kernel modules must be recompiled.
257 As this change breaks the ABI, bump __FreeBSD_version to 800104.
260 The TOE interface to the TCP syncache has been modified to remove struct
261 tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack. The
262 cxgb driver is the only TOE consumer affected by this change, and needs
263 to be recompiled along with the kernel. As this change breaks the ABI,
264 bump __FreeBSD_version to 800103.
267 Padding has been added to struct tcpcb, sackhint and tcpstat in
268 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
269 maintainig the ABI. However, this change breaks the ABI, so bump
270 __FreeBSD_version to 800102. User space tools that rely on the size of
271 any of these structs (e.g. sockstat) need to be recompiled.
274 The NFS_LEGACYRPC option has been removed along with the old
275 kernel RPC implementation that this option selected. Kernel
276 configurations may need to be adjusted.
279 The network interface device nodes at /dev/net/<interface> have
280 been removed. All ioctl operations can be performed the normal
281 way using routing sockets. The kqueue functionality can
282 generally be replaced with routing sockets.
285 The documentation from the FreeBSD Documentation Project
286 (Handbook, FAQ, etc.) is now installed via packages by
287 sysinstall(8) and under the /usr/local/share/doc/freebsd
288 directory instead of /usr/share/doc.
291 The ABI of various structures related to the SYSV IPC API have
292 been changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43
293 kernel options now all require COMPAT_FREEBSD7.
294 Bump __FreeBSD_version to 800100.
297 Layout of struct vnet has changed as routing related variables
298 were moved to their own Vimage module. Modules need to be
299 recompiled. Bump __FreeBSD_version to 800099.
302 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023
303 and 1024 respectively. As long as no more than 16 groups per
304 process are used, no changes should be visible. When more
305 than 16 groups are used, old binaries may fail if they call
306 getgroups() or getgrouplist() with statically sized storage.
307 Recompiling will work around this, but applications should be
308 modified to use dynamically allocated storage for group arrays
309 as POSIX.1-2008 does not cap an implementation's number of
310 supported groups at NGROUPS_MAX+1 as previous versions did.
312 NFS and portalfs mounts may also be affected as the list of
313 groups is truncated to 16. Users of NFS who use more than 16
314 groups, should take care that negative group permissions are not
315 used on the exported file systems as they will not be reliable
316 unless a GSSAPI based authentication method is used.
319 The compiling option ADAPTIVE_LOCKMGRS has been introduced.
320 This option compiles in the support for adaptive spinning for lockmgrs
321 which want to enable it. The lockinit() function now accepts the
322 flag LK_ADAPTIVE in order to make the lock object subject to
323 adaptive spinning when both held in write and read mode.
326 The layout of the structure returned by IEEE80211_IOC_STA_INFO
327 has changed. User applications that use this ioctl need to be
331 The layout of struct thread has changed. Kernel and modules
335 The layout of structs ifnet, domain, protosw and vnet_net has
336 changed. Kernel modules need to be rebuilt.
337 Bump __FreeBSD_version to 800097.
340 window(1) has been removed from the base system. It can now be
341 installed from ports. The port is called misc/window.
344 The way we are storing and accessing `routing table' entries
345 has changed. Programs reading the FIB, like netstat, need to
349 A new netisr implementation has been added for FreeBSD 8. Network
350 file system modules, such as igmp, ipdivert, and others, should be
352 Bump __FreeBSD_version to 800096.
355 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose
359 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
360 Bump __FreeBSD_version to 800094.
363 Add mnt_xflag field to 'struct mount'. File system modules
365 Bump __FreeBSD_version to 800093.
368 The compiling option ADAPTIVE_SX has been retired while it has been
369 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
370 The KPI for sx_init_flags() changes as accepting flags:
371 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag
372 has been introduced in order to handle the reversed logic.
373 Bump __FreeBSD_version to 800092.
376 Add support for hierarchical jails. Remove global securelevel.
377 Bump __FreeBSD_version to 800091.
380 The layout of struct vnet_net has changed, therefore modules
382 Bump __FreeBSD_version to 800090.
385 The newly imported zic(8) produces a new format in the
386 output. Please run tzsetup(8) to install the newly created
387 data to /etc/localtime.
390 The sysctl tree for the usb stack has renamed from hw.usb2.* to
391 hw.usb.* and is now consistent again with previous releases.
394 802.11 monitor mode support was revised and driver api's
395 were changed. Drivers dependent on net80211 now support
396 DLT_IEEE802_11_RADIO instead of DLT_IEEE802_11. No
397 user-visible data structures were changed but applications
398 that use DLT_IEEE802_11 may require changes.
399 Bump __FreeBSD_version to 800088.
402 The layout of the following structs has changed: sysctl_oid,
403 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
404 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
405 panics may be experienced. World rebuild is required for
406 correctly checking networking state from userland.
407 Bump __FreeBSD_version to 800085.
410 MLDv2 and Source-Specific Multicast (SSM) have been merged
411 to the IPv6 stack. VIMAGE hooks are in but not yet used.
412 The implementation of SSM within FreeBSD's IPv6 stack closely
413 follows the IPv4 implementation.
415 For kernel developers:
417 * The most important changes are that the ip6_output() and
418 ip6_input() paths no longer take the IN6_MULTI_LOCK,
419 and this lock has been downgraded to a non-recursive mutex.
421 * As with the changes to the IPv4 stack to support SSM, filtering
422 of inbound multicast traffic must now be performed by transport
423 protocols within the IPv6 stack. This does not apply to TCP and
424 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
426 * The KPIs used by IPv6 multicast are similar to those used by
427 the IPv4 stack, with the following differences:
428 * im6o_mc_filter() is analogous to imo_multicast_filter().
429 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
430 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
431 * IN6_LOOKUP_MULTI() has been deprecated and removed.
432 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
433 for MLDv1 have an additional 'timer' argument which is used to
434 jitter the initial membership report for the solicited-node
435 multicast membership on-link.
436 * This is not strictly needed for MLDv2, which already jitters
437 its report transmissions. However, the 'timer' argument is
438 preserved in case MLDv1 is active on the interface.
440 * The KAME linked-list based IPv6 membership implementation has
441 been refactored to use a vector similar to that used by the IPv4
443 Code which maintains a list of its own multicast memberships
444 internally, e.g. carp, has been updated to reflect the new
447 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
448 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
449 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
450 implementation constraint which needs to be addressed in HEAD.
452 For application developers:
454 * The changes are broadly similar to those made for the IPv4
457 * The use of IPv4 and IPv6 multicast socket options on the same
458 socket, using mapped addresses, HAS NOT been tested or supported.
460 * There are a number of issues with the implementation of various
461 IPv6 multicast APIs which need to be resolved in the API surface
462 before the implementation is fully compatible with KAME userland
463 use, and these are mostly to do with interface index treatment.
465 * The literature available discusses the use of either the delta / ASM
466 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
467 using setsourcefilter(3)/getsourcefilter(3). For more information
468 please refer to RFC 3768, 'Socket Interface Extensions for
469 Multicast Source Filters'.
471 * Applications which use the published RFC 3678 APIs should be fine.
473 For systems administrators:
475 * The mtest(8) utility has been refactored to support IPv6, in
476 addition to IPv4. Interface addresses are no longer accepted
477 as arguments, their names must be used instead. The utility
478 will map the interface name to its first IPv4 address as
479 returned by getifaddrs(3).
481 * The ifmcstat(8) utility has also been updated to print the MLDv2
482 endpoint state and source filter lists via sysctl(3).
484 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
485 loopback of IPv6 multicast datagrams by default; it defaults to 1
486 to preserve the existing behaviour. Disabling multicast loopback is
487 recommended for optimal system performance.
489 * The IPv6 MROUTING code has been changed to examine this sysctl
490 instead of attempting to perform a group lookup before looping
491 back forwarded datagrams.
493 Bump __FreeBSD_version to 800084.
496 Implement low-level Bluetooth HCI API.
497 Bump __FreeBSD_version to 800083.
500 The layout of struct malloc_type, used by modules to register new
501 memory allocation types, has changed. Most modules will need to
502 be rebuilt or panics may be experienced.
503 Bump __FreeBSD_version to 800081.
506 Anticipate overflowing inp_flags - add inp_flags2.
507 This changes most offsets in inpcb, so checking v4 connection
508 state will require a world rebuild.
509 Bump __FreeBSD_version to 800080.
512 Add an llentry to struct route and struct route_in6. Modules
513 embedding a struct route will need to be recompiled.
514 Bump __FreeBSD_version to 800079.
517 The size of rt_metrics_lite and by extension rtentry has changed.
518 Networking administration apps will need to be recompiled.
519 The route command now supports show as an alias for get, weighting
520 of routes, sticky and nostick flags to alter the behavior of stateful
522 Bump __FreeBSD_version to 800078.
525 Do not use Giant for kbdmux(4) locking. This is wrong and
526 apparently causing more problems than it solves. This will
527 re-open the issue where interrupt handlers may race with
528 kbdmux(4) in polling mode. Typical symptoms include (but
529 not limited to) duplicated and/or missing characters when
530 low level console functions (such as gets) are used while
531 interrupts are enabled (for example geli password prompt,
532 mountroot prompt etc.). Disabling kbdmux(4) may help.
535 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
536 kernel modules referencing any of the above need to be recompiled.
537 Bump __FreeBSD_version to 800075.
540 GEOM_PART has become the default partition slicer for storage devices,
541 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
542 introduces some changes:
544 MSDOS/EBR: the devices created from MSDOS extended partition entries
545 (EBR) can be named differently than with GEOM_MBR and are now symlinks
546 to devices with offset-based names. fstabs may need to be modified.
548 BSD: the "geometry does not match label" warning is harmless in most
549 cases but it points to problems in file system misalignment with
550 disk geometry. The "c" partition is now implicit, covers the whole
551 top-level drive and cannot be (mis)used by users.
553 General: Kernel dumps are now not allowed to be written to devices
554 whose partition types indicate they are meant to be used for file
555 systems (or, in case of MSDOS partitions, as something else than
558 Most of these changes date approximately from 200812.
561 The uscanner(4) driver has been removed from the kernel. This follows
562 Linux removing theirs in 2.6 and making libusb the default interface
566 The multicast forwarding code has been cleaned up. netstat(1)
567 only relies on KVM now for printing bandwidth upcall meters.
568 The IPv4 and IPv6 modules are split into ip_mroute_mod and
569 ip6_mroute_mod respectively. The config(5) options for statically
570 compiling this code remain the same, i.e. 'options MROUTING'.
573 Support for the IFF_NEEDSGIANT network interface flag has been
574 removed, which means that non-MPSAFE network device drivers are no
575 longer supported. In particular, if_ar, if_sr, and network device
576 drivers from the old (legacy) USB stack can no longer be built or
580 POSIX.1 Native Language Support (NLS) has been enabled in libc and
581 a bunch of new language catalog files have also been added.
582 This means that some common libc messages are now localized and
583 they depend on the LC_MESSAGES environmental variable.
586 The k8temp(4) driver has been renamed to amdtemp(4) since
587 support for K10 and K11 CPU families was added.
590 IGMPv3 and Source-Specific Multicast (SSM) have been merged
591 to the IPv4 stack. VIMAGE hooks are in but not yet used.
593 For kernel developers, the most important changes are that the
594 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
595 and this lock has been downgraded to a non-recursive mutex.
597 Transport protocols (UDP, Raw IP) are now responsible for filtering
598 inbound multicast traffic according to group membership and source
599 filters. The imo_multicast_filter() KPI exists for this purpose.
600 Transports which do not use multicast (SCTP, TCP) already reject
601 multicast by default. Forwarding and receive performance may improve
602 as a mutex acquisition is no longer needed in the ip_input()
603 low-level input path. in_addmulti() and in_delmulti() are shimmed
604 to new KPIs which exist to support SSM in-kernel.
606 For application developers, it is recommended that loopback of
607 multicast datagrams be disabled for best performance, as this
608 will still cause the lock to be taken for each looped-back
609 datagram transmission. The net.inet.ip.mcast.loop sysctl may
610 be tuned to 0 to disable loopback by default; it defaults to 1
611 to preserve the existing behaviour.
613 For systems administrators, to obtain best performance with
614 multicast reception and multiple groups, it is always recommended
615 that a card with a suitably precise hash filter is used. Hash
616 collisions will still result in the lock being taken within the
617 transport protocol input path to check group membership.
619 If deploying FreeBSD in an environment with IGMP snooping switches,
620 it is recommended that the net.inet.igmp.sendlocal sysctl remain
621 enabled; this forces 224.0.0.0/24 group membership to be announced
624 The size of 'struct igmpstat' has changed; netstat needs to be
625 recompiled to reflect this.
626 Bump __FreeBSD_version to 800070.
629 libusb20.so.1 is now installed as libusb.so.1 and the ports system
630 updated to use it. This requires a buildworld/installworld in order to
631 update the library and dependencies (usbconfig, etc). Its advisable to
632 rebuild all ports which uses libusb. More specific directions are given
633 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
634 libusb are no longer required and can be removed.
637 A workaround is committed to allow the creation of System V shared
638 memory segment of size > 2 GB on the 64-bit architectures.
639 Due to a limitation of the existing ABI, the shm_segsz member
640 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
641 wrong for large segments. Note that limits must be explicitly
642 raised to allow such segments to be created.
645 The layout of struct ifnet has changed, requiring a rebuild of all
646 network device driver modules.
649 The /dev handling for the new USB stack has changed, a
650 buildworld/installworld is required for libusb20.
653 The new USB2 stack has now been permanently moved in and all kernel and
654 module names reverted to their previous values (eg, usb, ehci, ohci,
655 ums, ...). The old usb stack can be compiled in by prefixing the name
656 with the letter 'o', the old usb modules have been removed.
657 Updating entry 20090216 for xorg and 20090215 for libmap may still
661 The rc.conf(5) option if_up_delay has been renamed to
662 defaultroute_delay to better reflect its purpose. If you have
663 customized this setting in /etc/rc.conf you need to update it to
667 xorg 7.4 wants to configure its input devices via hald which does not
668 yet work with USB2. If the keyboard/mouse does not work in xorg then
670 Option "AllowEmptyInput" "off"
671 to your ServerLayout section. This will cause X to use the configured
672 kbd and mouse sections from your xorg.conf.
675 The GENERIC kernels for all architectures now default to the new USB2
676 stack. No kernel config options or code have been removed so if a
677 problem arises please report it and optionally revert to the old USB
678 stack. If you are loading USB kernel modules or have a custom kernel
679 that includes GENERIC then ensure that usb names are also changed over,
680 eg uftdi -> usb2_serial_ftdi.
682 Older programs linked against the ports libusb 0.1 need to be
683 redirected to the new stack's libusb20. /etc/libmap.conf can
685 # Map old usb library to new one for usb2 stack
686 libusb-0.1.so.8 libusb20.so.1
689 All USB ethernet devices now attach as interfaces under the name ueN
690 (eg. ue0). This is to provide a predictable name as vendors often
691 change usb chipsets in a product without notice.
694 The ichsmb(4) driver has been changed to require SMBus slave
695 addresses be left-justified (xxxxxxx0b) rather than right-justified.
696 All of the other SMBus controller drivers require left-justified
697 slave addresses, so this change makes all the drivers provide the
701 INET6 statistics (struct ip6stat) was updated.
702 netstat(1) needs to be recompiled.
705 NTFS has been removed from GENERIC kernel on amd64 to match
706 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
707 will load ntfs.ko module automatically when NTFS support is
708 actually needed, unless ntfs.ko is not installed or security
709 level prohibits loading kernel modules. If either is the case,
710 "options NTFS" has to be added into kernel config.
713 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
714 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
715 800061. User space tools that rely on the size of struct tcpcb in
716 tcp_var.h (e.g. sockstat) need to be recompiled.
719 ng_tty(4) module updated to match the new TTY subsystem.
720 Due to API change, user-level applications must be updated.
721 New API support added to mpd5 CVS and expected to be present
722 in next mpd5.3 release.
725 With __FreeBSD_version 800060 the makefs tool is part of
726 the base system (it was a port).
729 The afdata and ifnet locks have been changed from mutexes to
730 rwlocks, network modules will need to be re-compiled.
733 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
734 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
735 The new code reduced struct rtentry{} by 16 bytes on 32-bit
736 architecture and 40 bytes on 64-bit architecture. The userland
737 applications "arp" and "ndp" have been updated accordingly.
738 The output from "netstat -r" shows only routing entries and
739 none of the L2 information.
742 __FreeBSD_version 800057 marks the switchover from the
743 binary ath hal to source code. Users must add the line:
745 options AH_SUPPORT_AR5416
747 to their kernel config files when specifying:
751 The ath_hal module no longer exists; the code is now compiled
752 together with the driver in the ath module. It is now
753 possible to tailor chip support (i.e. reduce the set of chips
754 and thereby the code size); consult ath_hal(4) for details.
757 __FreeBSD_version 800054 adds memory barriers to
758 <machine/atomic.h>, new interfaces to ifnet to facilitate
759 multiple hardware transmit queues for cards that support
760 them, and a lock-less ring-buffer implementation to
761 enable drivers to more efficiently manage queueing of
765 A new version of ZFS (version 13) has been merged to -HEAD.
766 This version has zpool attribute "listsnapshots" off by
767 default, which means "zfs list" does not show snapshots,
768 and is the same as Solaris behavior.
771 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
774 The uhci, ohci, ehci and slhci USB Host controller drivers have
775 been put into separate modules. If you load the usb module
776 separately through loader.conf you will need to load the
777 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
778 controller add the following to loader.conf:
784 The ABI used by the PMC toolset has changed. Please keep
785 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
789 atapci kernel module now includes only generic PCI ATA
790 driver. AHCI driver moved to ataahci kernel module.
791 All vendor-specific code moved into separate kernel modules:
792 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
793 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
794 atamarvell, atamicron, atanational, atanetcell, atanvidia,
795 atapromise, ataserverworks, atasiliconimage, atasis, atavia
798 The TTY subsystem of the kernel has been replaced by a new
799 implementation, which provides better scalability and an
800 improved driver model. Most common drivers have been migrated to
801 the new TTY subsystem, while others have not. The following
802 drivers have not yet been ported to the new TTY layer:
805 cy, digi, rc, rp, sio
811 ng_h4, ng_tty, ppp, sl, snp
813 Adding these drivers to your kernel configuration file shall
814 cause compilation to fail.
817 ntpd has been upgraded to 4.2.4p5.
820 OpenSSH has been upgraded to 5.1p1.
822 For many years, FreeBSD's version of OpenSSH preferred DSA
823 over RSA for host and user authentication keys. With this
824 upgrade, we've switched to the vendor's default of RSA over
825 DSA. This may cause upgraded clients to warn about unknown
826 host keys even for previously known hosts. Users should
827 follow the usual procedure for verifying host keys before
828 accepting the RSA key.
830 This can be circumvented by setting the "HostKeyAlgorithms"
831 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
834 Please note that the sequence of keys offered for
835 authentication has been changed as well. You may want to
836 specify IdentityFile in a different order to revert this
840 The sio(4) driver has been removed from the i386 and amd64
841 kernel configuration files. This means uart(4) is now the
842 default serial port driver on those platforms as well.
844 To prevent collisions with the sio(4) driver, the uart(4) driver
845 uses different names for its device nodes. This means the
846 onboard serial port will now most likely be called "ttyu0"
847 instead of "ttyd0". You may need to reconfigure applications to
848 use the new device names.
850 When using the serial port as a boot console, be sure to update
851 /boot/device.hints and /etc/ttys before booting the new kernel.
852 If you forget to do so, you can still manually specify the hints
853 at the loader prompt:
855 set hint.uart.0.at="isa"
856 set hint.uart.0.port="0x3F8"
857 set hint.uart.0.flags="0x10"
858 set hint.uart.0.irq="4"
862 The gpt(8) utility has been removed. Use gpart(8) to partition
866 The version that Linuxulator emulates was changed from 2.4.2
867 to 2.6.16. If you experience any problems with Linux binaries
868 please try to set sysctl compat.linux.osrelease to 2.4.2 and
869 if it fixes the problem contact emulation mailing list.
872 ISDN4BSD (I4B) was removed from the src tree. You may need to
873 update a your kernel configuration and remove relevant entries.
876 I have checked in code to support multiple routing tables.
877 See the man pages setfib(1) and setfib(2).
878 This is a hopefully backwards compatible version,
879 but to make use of it you need to compile your kernel
880 with options ROUTETABLES=2 (or more up to 16).
883 The 802.11 wireless support was redone to enable multi-bss
884 operation on devices that are capable. The underlying device
885 is no longer used directly but instead wlanX devices are
886 cloned with ifconfig. This requires changes to rc.conf files.
888 ifconfig_ath0="WPA DHCP"
891 ifconfig_wlan0="WPA DHCP"
892 see rc.conf(5) for more details. In addition, mergemaster of
893 /etc/rc.d is highly recommended. Simultaneous update of userland
894 and kernel wouldn't hurt either.
896 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
897 modules were merged into the base wlan module. All references
898 to these modules (e.g. in kernel config files) must be removed.
901 psm(4) has gained write(2) support in native operation level.
902 Arbitrary commands can be written to /dev/psm%d and status can
903 be read back from it. Therefore, an application is responsible
904 for status validation and error recovery. It is a no-op in
905 other operation levels.
908 Support for KSE threading has been removed from the kernel. To
909 run legacy applications linked against KSE libmap.conf may
910 be used. The following libmap.conf may be used to ensure
911 compatibility with any prior release:
913 libpthread.so.1 libthr.so.1
914 libpthread.so.2 libthr.so.2
915 libkse.so.3 libthr.so.3
918 The layout of struct vmspace has changed. This affects libkvm
919 and any executables that link against libkvm and use the
920 kvm_getprocs() function. In particular, but not exclusively,
921 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
922 The effects are minimal, but it's advisable to upgrade world
926 The latest em driver no longer has support in it for the
927 82575 adapter, this is now moved to the igb driver. The
928 split was done to make new features that are incompatible
929 with older hardware easier to do.
932 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
933 likewise the kernel option is now GEOM_LINUX_LVM.
936 The default NFS mount mode has changed from UDP to TCP for
937 increased reliability. If you rely on (insecurely) NFS
938 mounting across a firewall you may need to update your
942 Belatedly note the addition of m_collapse for compacting
946 The fts(3) structures have been changed to use adequate
947 integer types for their members and so to be able to cope
948 with huge file trees. The old fts(3) ABI is preserved
949 through symbol versioning in libc, so third-party binaries
950 using fts(3) should still work, although they will not take
951 advantage of the extended types. At the same time, some
952 third-party software might fail to build after this change
953 due to unportable assumptions made in its source code about
954 fts(3) structure members. Such software should be fixed
955 by its vendor or, in the worst case, in the ports tree.
956 FreeBSD_version 800015 marks this change for the unlikely
957 case that a portable fix is impossible.
960 To upgrade to -current after this date, you must be running
961 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
962 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
965 The ADAPTIVE_GIANT kernel option has been retired because its
966 functionality is the default now.
969 The AT keyboard emulation of sunkbd(4) has been turned on
970 by default. In order to make the special symbols of the Sun
971 keyboards driven by sunkbd(4) work under X these now have
972 to be configured the same way as Sun USB keyboards driven
973 by ukbd(4) (which also does AT keyboard emulation), f.e.:
975 Option "XkbLayout" "us"
976 Option "XkbRules" "xorg"
977 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
980 It has been decided that it is desirable to provide ABI
981 backwards compatibility to the FreeBSD 4/5/6 versions of the
982 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
983 broken with the introduction of PCI domain support (see the
984 20070930 entry). Unfortunately, this required the ABI of
985 PCIOCGETCONF to be broken again in order to be able to
986 provide backwards compatibility to the old version of that
987 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
988 again. As for prominent ports this affects neither pciutils
989 nor xorg-server this time, the hal port needs to be rebuilt
993 The misnamed kthread_create() and friends have been renamed
994 to kproc_create() etc. Many of the callers already
996 I will return kthread_create() and friends in a while
997 with implementations that actually create threads, not procs.
998 Renaming corresponds with version 800002.
1004 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
1005 WITHOUT_LIBTHR are set.
1008 The PCI code has been made aware of PCI domains. This means that
1009 the location strings as used by pciconf(8) etc are now in the
1010 following format: pci<domain>:<bus>:<device>[:<function>]. It
1011 also means that consumers of <sys/pciio.h> potentially need to
1012 be recompiled; this includes the hal and xorg-server ports.
1015 The caching daemon (cached) was renamed to nscd. nscd.conf
1016 configuration file should be used instead of cached.conf and
1017 nscd_enable, nscd_pidfile and nscd_flags options should be used
1018 instead of cached_enable, cached_pidfile and cached_flags in
1022 The getfacl(1) utility now prints owning user and group name
1023 instead of owning uid and gid in the three line comment header.
1024 This is the same behavior as getfacl(1) on Solaris and Linux.
1027 The new IPsec code is now compiled in using the IPSEC option. The
1028 IPSEC option now requires "device crypto" be defined in your kernel
1029 configuration. The FAST_IPSEC kernel option is now deprecated.
1032 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
1033 note the changed syntax - keep state is now on by default. Also
1034 note the fact that ftp-proxy(8) has been changed from bottom up and
1035 has been moved from libexec to usr/sbin. Changes in the ALTQ
1036 handling also affect users of IPFW's ALTQ capabilities.
1039 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
1040 only IPsec supported by FreeBSD. The new IPsec stack
1041 supports both IPv4 and IPv6. The kernel option will change
1042 after the code changes have settled in. For now the kernel
1043 option IPSEC is deprecated and FAST_IPSEC is the only option, that
1044 will change after some settling time.
1047 The wicontrol(8) utility has been removed from the base system. wi(4)
1048 cards should be configured using ifconfig(8), see the man page for more
1052 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
1053 instead of the nve(4) driver. Please update your configuration
1057 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
1058 database if it is missing or older than the aliases file. If
1059 desired, set the new rc.conf option sendmail_rebuild_aliases
1060 to "YES" to restore that functionality.
1063 The IPv4 multicast socket code has been considerably modified, and
1064 moved to the file sys/netinet/in_mcast.c. Initial support for the
1065 RFC 3678 Source-Specific Multicast Socket API has been added to
1066 the IPv4 network stack.
1068 Strict multicast and broadcast reception is now the default for
1069 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
1070 has now been removed.
1072 The RFC 1724 hack for interface selection has been removed; the use
1073 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
1074 been added to replace it. Consumers such as routed will soon be
1075 updated to reflect this.
1077 These changes affect users who are running routed(8) or rdisc(8)
1078 from the FreeBSD base system on point-to-point or unnumbered
1082 The net80211 layer has changed significantly and all wireless
1083 drivers that depend on it need to be recompiled. Further these
1084 changes require that any program that interacts with the wireless
1085 support in the kernel be recompiled; this includes: ifconfig,
1086 wpa_supplicant, hostapd, and wlanstats. Users must also, for
1087 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
1088 if they use modules for wireless support. These modules implement
1089 scanning support for station and ap modes, respectively. Failure
1090 to load the appropriate module before marking a wireless interface
1091 up will result in a message to the console and the device not
1095 The pam_nologin(8) module ceases to provide an authentication
1096 function and starts providing an account management function.
1097 Consequent changes to /etc/pam.d should be brought in using
1098 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
1099 need manual editing as follows. Locate this line (or similar):
1101 auth required pam_nologin.so no_warn
1103 and change it according to this example:
1105 account required pam_nologin.so no_warn
1107 That is, the first word needs to be changed from "auth" to
1108 "account". The new line can be moved to the account section
1109 within the file for clarity. Not updating pam.conf(5) files
1110 will result in nologin(5) ignored by the respective services.
1113 The ether_ioctl() function has been synchronized with ioctl(2)
1114 and ifnet.if_ioctl. Due to that, the size of one of its arguments
1115 has changed on 64-bit architectures. All kernel modules using
1116 ether_ioctl() need to be rebuilt on such architectures.
1119 Improved INCLUDE_CONFIG_FILE support has been introduced to the
1120 config(8) utility. In order to take advantage of this new
1121 functionality, you are expected to recompile and install
1122 src/usr.sbin/config. If you don't rebuild config(8), and your
1123 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
1124 build will be broken because of a missing "kernconfstring"
1128 Symbol versioning is enabled by default. To disable it, use
1129 option WITHOUT_SYMVER. It is not advisable to attempt to
1130 disable symbol versioning once it is enabled; your installworld
1131 will break because a symbol version-less libc will get installed
1132 before the install tools. As a result, the old install tools,
1133 which previously had symbol dependencies to FBSD_1.0, will fail
1134 because the freshly installed libc will not have them.
1136 The default threading library (providing "libpthread") has been
1137 changed to libthr. If you wish to have libkse as your default,
1138 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
1141 The ABI breakage in sendmail(8)'s libmilter has been repaired
1142 so it is no longer necessary to recompile mail filters (aka,
1143 milters). If you recompiled mail filters after the 20070408
1144 note, it is not necessary to recompile them again.
1147 The new trunk(4) driver has been renamed to lagg(4) as it better
1148 reflects its purpose. ifconfig will need to be recompiled.
1151 sendmail(8) has been updated to version 8.14.1. Mail filters
1152 (aka, milters) compiled against the libmilter included in the
1153 base operating system should be recompiled.
1156 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
1157 In order to use them one must agree to the respective LICENSE in
1158 share/doc/legal and define legal.intel_<name>.license_ack=1 via
1159 loader.conf(5) or kenv(1). Make sure to deinstall the now
1160 deprecated modules from the respective firmware ports.
1163 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
1164 were removed from FreeBSD's libc. These originally came from INRIA
1165 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
1166 deprecated in previous releases.
1167 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
1168 replace it as a more portable (and re-entrant) API.
1171 To support interrupt filtering a modification to the newbus API
1172 has occurred, ABI was broken and __FreeBSD_version was bumped
1173 to 700031. Please make sure that your kernel and modules are in
1174 sync. For more info:
1175 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
1178 The IPv6 multicast forwarding code may now be loaded into GENERIC
1179 kernels by loading the ip_mroute.ko module. This is built into the
1180 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
1181 set; see src.conf(5) for more information.
1184 The output of netstat -r has changed. Without -n, we now only
1185 print a "network name" without the prefix length if the network
1186 address and mask exactly match a Class A/B/C network, and an entry
1187 exists in the nsswitch "networks" map.
1188 With -n, we print the full unabbreviated CIDR network prefix in
1189 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
1190 This change is in preparation for changes such as equal-cost
1191 multipath, and to more generally assist operational deployment
1192 of FreeBSD as a modern IPv4 router.
1195 PIM has been turned on by default in the IPv4 multicast
1196 routing code. The kernel option 'PIM' has now been removed.
1197 PIM is now built by default if option 'MROUTING' is specified.
1198 It may now be loaded into GENERIC kernels by loading the
1199 ip_mroute.ko module.
1202 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
1203 has been removed. Its functionality may be achieved by explicitly
1204 configuring gif(4) interfaces and using the 'phyint' keyword in
1206 XORP does not support source-routed IPv4 multicast tunnels nor the
1207 integrated IPIP tunneling, therefore it is not affected by this
1208 change. The __FreeBSD_version macro has been bumped to 700030.
1211 Support for PCI Message Signalled Interrupts has been
1212 re-enabled in the bge driver, only for those chips which are
1213 believed to support it properly. If there are any problems,
1214 MSI can be disabled completely by setting the
1215 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
1219 Support for PCI Message Signalled Interrupts has been
1220 disabled again in the bge driver. Many revisions of the
1221 hardware fail to support it properly. Support can be
1222 re-enabled by removing the #define of BGE_DISABLE_MSI in
1223 "src/sys/dev/bge/if_bge.c".
1226 Support for PCI Message Signalled Interrupts has been added
1227 to the bge driver. If there are any problems, MSI can be
1228 disabled completely by setting the 'hw.pci.enable_msi' and
1229 'hw.pci.enable_msix' tunables to 0 in the loader.
1232 The removal of several facets of the experimental Threading
1233 system from the kernel means that the proc and thread structures
1234 have changed quite a bit. I suggest all kernel modules that might
1235 reference these structures be recompiled.. Especially the
1239 Sound infrastructure has been updated with various fixes and
1240 improvements. Most of the changes are pretty much transparent,
1241 with exceptions of followings:
1242 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
1243 moved to their own dev sysctl nodes, for example:
1244 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
1245 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
1246 own chardev in the form of "dsp%d.<function>%d", where <function>
1247 is p = playback, r = record and v = virtual, respectively. Users
1248 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
1249 This does not affect those who are using "/dev/dsp".
1252 geom(4)'s gmirror(8) class metadata structure has been
1253 rev'd from v3 to v4. If you update across this point and
1254 your metadata is converted for you, you will not be easily
1255 able to downgrade since the /boot/kernel.old/geom_mirror.ko
1256 kernel module will be unable to read the v4 metadata. You
1257 can resolve this by doing from the loader(8) prompt:
1259 set vfs.root.mountfrom="ufs:/dev/XXX"
1261 where XXX is the root slice of one of the disks that composed
1262 the mirror (i.e.: /dev/ad0s1a). You can then rebuild
1263 the array the same way you built it originally.
1266 The following binaries have been disconnected from the build:
1267 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
1268 and mount_std. The functionality of these programs has been
1269 moved into the mount program. For example, to mount a devfs
1270 filesystem, instead of using mount_devfs, use: "mount -t devfs".
1271 This does not affect entries in /etc/fstab, since entries in
1272 /etc/fstab are always processed with "mount -t fstype".
1275 Support for PCI Message Signalled Interrupts on i386 and amd64
1276 has been added to the kernel and various drivers will soon be
1277 updated to use MSI when it is available. If there are any problems,
1278 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
1279 and 'hw.pci.enable_msix' tunables to 0 in the loader.
1282 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
1283 The lockmgr object layout has been changed as a result of having
1284 a lock_object embedded in it. As a consequence all file system
1285 kernel modules must be re-compiled. The mutex profiling man page
1286 has not yet been updated to reflect this change.
1289 KSE in the kernel has now been made optional and turned on by
1290 default. Use 'nooption KSE' in your kernel config to turn it
1291 off. All kernel modules *must* be recompiled after this change.
1292 There-after, modules from a KSE kernel should be compatible with
1293 modules from a NOKSE kernel due to the temporary padding fields
1294 added to 'struct proc'.
1297 mrouted and its utilities have been removed from the base system.
1300 Some ioctl(2) command codes have changed. Full backward ABI
1301 compatibility is provided if the "options COMPAT_FREEBSD6" is
1302 present in the kernel configuration file. Make sure to add
1303 this option to your kernel config file, or recompile X.Org
1304 and the rest of ports; otherwise they may refuse to work.
1307 tcpslice has been removed from the base system.
1310 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
1311 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
1312 systat needs to be rebuilt.
1315 libpcap updated to v0.9.4 and tcpdump to v3.9.4
1318 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
1319 for IPFIREWALL_FORWARD is now as it was before when it was first
1320 committed and for years after. The behaviour is now ON.
1323 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
1324 Now it can decrypt files created from different architectures.
1325 Unfortunately, it is no longer able to decrypt a cipher text
1326 generated with an older version on 64 bit architectures.
1327 If you have such a file, you need old utility to decrypt it.
1330 The interface version of the i4b kernel part has changed. So
1331 after updating the kernel sources and compiling a new kernel,
1332 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
1333 be rebuilt, and vice versa.
1336 The XBOX kernel now defaults to the nfe(4) driver instead of
1337 the nve(4) driver. Please update your configuration
1341 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
1342 PCnet family of NICs has been removed. The new le(4) driver serves
1343 as an equivalent but cross-platform replacement with the pcn(4)
1344 driver still providing performance-optimized support for the subset
1345 of AMD Am79C971 PCnet-FAST and greater chips as before.
1348 The machdep.* sysctls and the adjkerntz utility have been
1349 modified a bit. The new adjkerntz utility uses the new
1350 sysctl names and sysctlbyname() calls, so it may be impossible
1351 to run an old /sbin/adjkerntz utility in single-user mode
1352 with a new kernel. Replace the `adjkerntz -i' step before
1353 `make installworld' with:
1355 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
1357 and proceed as usual with the rest of the installworld-stage
1358 steps. Otherwise, you risk installing binaries with their
1359 timestamp set several hours in the future, especially if
1360 you are running with local time set to GMT+X hours.
1363 The ip6fw utility has been removed. The behavior provided by
1364 ip6fw has been in ipfw2 for a good while and the rc.d scripts
1365 have been updated to deal with it. There are some rules that
1366 might not migrate cleanly. Use rc.firewall6 as a template to
1370 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
1371 attachments have been removed. Make sure to configure scc(4)
1372 on sparc64. Note also that by default puc(4) will use uart(4)
1373 and not sio(4) for serial ports because interrupt handling has
1374 been optimized for multi-port serial cards and only uart(4)
1375 implements the interface to support it.
1378 The scc(4) driver replaces puc(4) for Serial Communications
1379 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
1380 Z8530. On sparc64, it is advised to add scc(4) to the kernel
1381 configuration to make sure that the serial ports remain
1385 Most world/kernel related NO_* build options changed names.
1386 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
1387 after FreeBSD ports) and should be set in /etc/src.conf
1388 (the src.conf(5) manpage is provided). Full backwards
1389 compatibility is maintained for the time being though it's
1390 highly recommended to start moving old options out of the
1391 system-wide /etc/make.conf file into the new /etc/src.conf
1392 while also properly renaming them. More conversions will
1393 likely follow. Posting to current@:
1395 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
1398 The NETSMBCRYPTO kernel option has been retired because its
1399 functionality is always included in NETSMB and smbfs.ko now.
1402 The TDFX_LINUX kernel option was retired and replaced by the
1403 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
1404 kernel module. Loading it alone should suffice to get 3dfx support
1405 for Linux apps because it will pull in 3dfx.ko and linux.ko through
1409 The 'audit' group was added to support the new auditing functionality
1410 in the base system. Be sure to follow the directions for updating,
1411 including the requirement to run mergemaster -p.
1414 The kernel ABI to file system modules was changed on i386.
1415 Please make sure that your kernel and modules are in sync.
1418 This actually occured some time ago, but installing the kernel
1419 now also installs a bunch of symbol files for the kernel modules.
1420 This increases the size of /boot/kernel to about 67Mbytes. You
1421 will need twice this if you will eventually back this up to kernel.old
1422 on your next install.
1423 If you have a shortage of room in your root partition, you should add
1424 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
1425 to your /etc/make.conf.
1428 libc's malloc implementation has been replaced. This change has the
1429 potential to uncover application bugs that previously went unnoticed.
1430 See the malloc(3) manual page for more details.
1433 The generic netgraph(4) cookie has been changed. If you upgrade
1434 kernel passing this point, you also need to upgrade userland
1435 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
1438 si(4)'s device files now contain the unit number.
1439 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
1442 The kernel ABI was mostly destroyed due to a change in the size
1443 of struct lock_object which is nested in other structures such
1444 as mutexes which are nested in all sorts of other structures.
1445 Make sure your kernel and modules are in sync.
1448 The page coloring algorithm in the VM subsystem was converted
1449 from tuning with kernel options to autotuning. Please remove
1450 any PQ_* option except PQ_NOOPT from your kernel config.
1453 The net80211-related tools in the tools/tools/ath directory
1454 have been moved to tools/tools/net80211 and renamed with a
1455 "wlan" prefix. Scripts that use them should be adjusted
1459 Scripts in the local_startup directories (as defined in
1460 /etc/defaults/rc.conf) that have the new rc.d semantics will
1461 now be run as part of the base system rcorder. If there are
1462 errors or problems with one of these local scripts, it could
1463 cause boot problems. If you encounter such problems, boot in
1464 single user mode, remove that script from the */rc.d directory.
1465 Please report the problem to the port's maintainer, and the
1466 freebsd-ports@freebsd.org mailing list.
1469 The nodev mount option was deprecated in RELENG_6 (where it
1470 was a no-op), and is now unsupported. If you have nodev or dev listed
1471 in /etc/fstab, remove it, otherwise it will result in a mount error.
1474 ABI between ipfw(4) and ipfw(8) has been changed. You need
1475 to rebuild ipfw(8) when rebuilding kernel.
1478 rp(4)'s device files now contain the unit number.
1479 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
1482 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
1483 Its /etc/rc.conf.d configuration file has been `ppp' from
1484 the beginning, and hence there is no need to touch it.
1487 Now most modules get their build-time options from the kernel
1488 configuration file. A few modules still have fixed options
1489 due to their non-conformant implementation, but they will be
1490 corrected eventually. You may need to review the options of
1491 the modules in use, explicitly specify the non-default options
1492 in the kernel configuration file, and rebuild the kernel and
1496 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
1497 to turn polling(4) on your interfaces.
1500 The old bridge(4) implementation was retired. The new
1501 if_bridge(4) serves as a full functional replacement.
1504 The ai_addrlen of a struct addrinfo was changed to a socklen_t
1505 to conform to POSIX-2001. This change broke an ABI
1506 compatibility on 64 bit architecture. You have to recompile
1507 userland programs that use getaddrinfo(3) on 64 bit
1511 RELENG_6 branched here.
1514 The pccard_ifconfig rc.conf variable has been removed and a new
1515 variable, ifconfig_DEFAULT has been introduced. Unlike
1516 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
1517 do not have ifconfig_ifn entries rather than just those in
1518 removable_interfaces.
1521 Some previous versions of PAM have permitted the use of
1522 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
1523 to third party PAM modules in /usr/local/lib. A change has been
1524 made to require the use of absolute paths in order to avoid
1525 ambiguity and dependence on library path configuration, which may
1526 affect existing configurations.
1529 Major changes to network interface API. All drivers must be
1530 recompiled. Drivers not in the base system will need to be
1531 updated to the new APIs.
1534 Changes were made to kinfo_proc in sys/user.h. Please recompile
1535 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
1536 will not behave correctly.
1538 The API and ABI for hwpmc(4) have changed with the addition
1539 of sampling support. Please recompile lib/libpmc(3) and
1540 usr.sbin/{pmcstat,pmccontrol}.
1543 The OpenBSD dhclient was imported in place of the ISC dhclient
1544 and the network interface configuration scripts were updated
1545 accordingly. If you use DHCP to configure your interfaces, you
1546 must now run devd. Also, DNS updating was lost so you will need
1547 to find a workaround if you use this feature.
1549 The '_dhcp' user was added to support the OpenBSD dhclient. Be
1550 sure to run mergemaster -p (like you are supposed to do every time
1554 if_bridge was added to the tree. This has changed struct ifnet.
1555 Please recompile userland and all network related modules.
1558 The n_net of a struct netent was changed to an uint32_t, and
1559 1st argument of getnetbyaddr() was changed to an uint32_t, to
1560 conform to POSIX-2001. These changes broke an ABI
1561 compatibility on 64 bit architecture. With these changes,
1562 shlib major of libpcap was bumped. You have to recompile
1563 userland programs that use getnetbyaddr(3), getnetbyname(3),
1564 getnetent(3) and/or libpcap on 64 bit architecture.
1567 Kernel parsing of extra options on '#!' first lines of shell
1568 scripts has changed. Lines with multiple options likely will
1569 fail after this date. For full details, please see
1570 http://people.freebsd.org/~gad/Updating-20050528.txt
1573 The packet filter (pf) code has been updated to OpenBSD 3.7
1574 Please note the changed anchor syntax and the fact that
1575 authpf(8) now needs a mounted fdescfs(5) to function.
1578 The NO_MIXED_MODE kernel option has been removed from the i386
1579 amd64 platforms as its use has been superceded by the new local
1580 APIC timer code. Any kernel config files containing this option
1584 The on-disk format of LC_CTYPE files was changed to be machine
1585 independent. Please make sure NOT to use NO_CLEAN buildworld
1586 when crossing this point. Crossing this point also requires
1587 recompile or reinstall of all locale depended packages.
1590 The ifi_epoch member of struct if_data has been changed to
1591 contain the uptime at which the interface was created or the
1592 statistics zeroed rather then the wall clock time because
1593 wallclock time may go backwards. This should have no impact
1594 unless an snmp implementation is using this value (I know of
1595 none at this point.)
1598 The acpi_perf and acpi_throttle drivers are now part of the
1599 acpi(4) main module. They are no longer built separately.
1602 The layout of struct image_params has changed. You have to
1603 recompile all compatibility modules (linux, svr4, etc) for use
1604 with the new kernel.
1607 The p4tcc driver has been merged into cpufreq(4). This makes
1608 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
1609 compile in "device cpufreq" to restore this functionality.
1612 The responsibility of recomputing the file system summary of
1613 a SoftUpdates-enabled dirty volume has been transferred to the
1614 background fsck. A rebuild of fsck(8) utility is recommended
1615 if you have updated the kernel.
1617 To get the old behavior (recompute file system summary at mount
1618 time), you can set vfs.ffs.compute_summary_at_mount=1 before
1619 mounting the new volume.
1622 The cpufreq import is complete. As part of this, the sysctls for
1623 acpi(4) throttling have been removed. The power_profile script
1624 has been updated, so you can use performance/economy_cpu_freq in
1625 rc.conf(5) to set AC on/offline cpu frequencies.
1628 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
1629 requires recompiling libnetgraph and userland netgraph utilities.
1632 Support for abbreviated forms of a number of ipfw options is
1633 now deprecated. Warnings are printed to stderr indicating the
1634 correct full form when a match occurs. Some abbreviations may
1635 be supported at a later date based on user feedback. To be
1636 considered for support, abbreviations must be in use prior to
1637 this commit and unlikely to be confused with current key words.
1640 By a popular demand, a lot of NOFOO options were renamed
1641 to NO_FOO (see bsd.compat.mk for a full list). The old
1642 spellings are still supported, but will cause annoying
1643 warnings on stderr. Make sure you upgrade properly (see
1644 the COMMON ITEMS: section later in this file).
1647 Auto-loading of ancillary wlan modules such as wlan_wep has
1648 been temporarily disabled; you need to statically configure
1649 the modules you need into your kernel or explicitly load them
1650 prior to use. Specifically, if you intend to use WEP encryption
1651 with an 802.11 device load/configure wlan_wep; if you want to
1652 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
1653 and wlan_xauth as required.
1656 The behaviour of ppp(8) has changed slightly. If lqr is enabled
1657 (``enable lqr''), older versions would revert to LCP ECHO mode on
1658 negotiation failure. Now, ``enable echo'' is required for this
1659 behaviour. The ppp version number has been bumped to 3.4.2 to
1663 The wlan support has been updated to split the crypto support
1664 into separate modules. For static WEP you must configure the
1665 wlan_wep module in your system or build and install the module
1666 in place where it can be loaded (the kernel will auto-load
1667 the module when a wep key is configured).
1670 The ath driver has been updated to split the tx rate control
1671 algorithm into a separate module. You need to include either
1672 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
1675 Support for systems with an 80386 CPU has been removed. Please
1676 use FreeBSD 5.x or earlier on systems with an 80386.
1679 We have had a hack which would mount the root filesystem
1680 R/W if the device were named 'md*'. As part of the vnode
1681 work I'm doing I have had to remove this hack. People
1682 building systems which use preloaded MD root filesystems
1683 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
1684 their /etc/rc scripts.
1687 FreeBSD 5.3 shipped here.
1690 The size of struct tcpcb has changed again due to the removal
1691 of RFC1644 T/TCP. You have to recompile userland programs that
1692 read kmem for tcp sockets directly (netstat, sockstat, etc.)
1695 The size of struct tcpcb has changed. You have to recompile
1696 userland programs that read kmem for tcp sockets directly
1697 (netstat, sockstat, etc.)
1700 RELENG_5 branched here. For older entries, please see updating
1701 in the RELENG_5 branch.
1707 Avoid using make -j when upgrading. From time to time in the
1708 past there have been problems using -j with buildworld and/or
1709 installworld. This is especially true when upgrading between
1710 "distant" versions (eg one that cross a major release boundary
1711 or several minor releases, or when several months have passed
1712 on the -current branch).
1714 Sometimes, obscure build problems are the result of environment
1715 poisoning. This can happen because the make utility reads its
1716 environment when searching for values for global variables.
1717 To run your build attempts in an "environmental clean room",
1718 prefix all make commands with 'env -i '. See the env(1) manual
1719 page for more details.
1721 When upgrading from one major version to another it is generally
1722 best to upgrade to the latest code in the currently installed branch
1723 first, then do an upgrade to the new branch. This is the best-tested
1724 upgrade path, and has the highest probability of being successful.
1725 Please try this approach before reporting problems with a major
1730 When upgrading the boot ZFS pool to a new version, always follow
1733 1.) recompile and reinstall the ZFS boot loader and boot block
1734 (this is part of "make buildworld" and "make installworld")
1736 2.) update the ZFS boot block on your boot drive
1738 The following example updates the ZFS boot block on the first
1739 partition (freebsd-boot) of a GPT partitioned drive ad0:
1740 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1742 Non-boot pools do not need these updates.
1746 If you are updating from a prior version of FreeBSD (even one just
1747 a few days old), you should follow this procedure. It is the most
1748 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1750 make kernel-toolchain
1751 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1752 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1754 To test a kernel once
1755 ---------------------
1756 If you just want to boot a kernel once (because you are not sure
1757 if it works, or if you want to boot a known bad kernel to provide
1758 debugging information) run
1759 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1760 nextboot -k testkernel
1762 To just build a kernel when you know that it won't mess you up
1763 --------------------------------------------------------------
1764 This assumes you are already running a 5.X system. Replace
1765 ${arch} with the architecture of your machine (e.g. "i386",
1766 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1768 cd src/sys/${arch}/conf
1769 config KERNEL_NAME_HERE
1770 cd ../compile/KERNEL_NAME_HERE
1775 If this fails, go to the "To build a kernel" section.
1777 To rebuild everything and install it on the current system.
1778 -----------------------------------------------------------
1779 # Note: sometimes if you are running current you gotta do more than
1780 # is listed here if you are upgrading from a really old current.
1782 <make sure you have good level 0 dumps>
1784 make kernel KERNCONF=YOUR_KERNEL_HERE
1786 <reboot in single user> [3]
1794 To cross-install current onto a separate partition
1795 --------------------------------------------------
1796 # In this approach we use a separate partition to hold
1797 # current's root, 'usr', and 'var' directories. A partition
1798 # holding "/", "/usr" and "/var" should be about 2GB in
1801 <make sure you have good level 0 dumps>
1804 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1805 <maybe newfs current's root partition>
1806 <mount current's root partition on directory ${CURRENT_ROOT}>
1807 make installworld DESTDIR=${CURRENT_ROOT}
1808 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1809 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1810 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1811 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1812 <reboot into current>
1813 <do a "native" rebuild/install as described in the previous section>
1814 <maybe install compatibility libraries from ports/misc/compat*>
1818 To upgrade in-place from 5.x-stable to current
1819 ----------------------------------------------
1820 <make sure you have good level 0 dumps>
1822 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1824 <reboot in single user> [3]
1831 Make sure that you've read the UPDATING file to understand the
1832 tweaks to various things you need. At this point in the life
1833 cycle of current, things change often and you are on your own
1834 to cope. The defaults can also change, so please read ALL of
1835 the UPDATING entries.
1837 Also, if you are tracking -current, you must be subscribed to
1838 freebsd-current@freebsd.org. Make sure that before you update
1839 your sources that you have read and understood all the recent
1840 messages there. If in doubt, please track -stable which has
1841 much fewer pitfalls.
1843 [1] If you have third party modules, such as vmware, you
1844 should disable them at this point so they don't crash your
1847 [3] From the bootblocks, boot -s, and then do
1852 adjkerntz -i # if CMOS is wall time
1853 Also, when doing a major release upgrade, it is required that
1854 you boot into single user mode to do the installworld.
1856 [4] Note: This step is non-optional. Failure to do this step
1857 can result in a significant reduction in the functionality of the
1858 system. Attempting to do it by hand is not recommended and those
1859 that pursue this avenue should read this file carefully, as well
1860 as the archives of freebsd-current and freebsd-hackers mailing lists
1861 for potential gotchas.
1863 [5] Usually this step is a noop. However, from time to time
1864 you may need to do this if you get unknown user in the following
1865 step. It never hurts to do it all the time. You may need to
1866 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1867 install) after the buildworld before this step if you last updated
1868 from current before 20020224 or from -stable before 20020408.
1870 [6] This only deletes old files and directories. Old libraries
1871 can be deleted by "make delete-old-libs", but you have to make
1872 sure that no program is using those libraries anymore.
1874 [8] In order to have a kernel that can run the 4.x binaries
1875 needed to do an installworld, you must include the COMPAT_FREEBSD4
1876 option in your kernel. Failure to do so may leave you with a system
1877 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
1878 is required to run the 5.x binaries on more recent kernels.
1880 Make sure that you merge any new devices from GENERIC since the
1881 last time you updated your kernel config file.
1883 [9] When checking out sources, you must include the -P flag to have
1884 cvs prune empty directories.
1886 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1887 "?=" instead of the "=" assignment operator, so that buildworld can
1888 override the CPUTYPE if it needs to.
1890 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1891 not on the command line, or in /etc/make.conf. buildworld will
1892 warn if it is improperly defined.
1895 This file contains a list, in reverse chronological order, of major
1896 breakages in tracking -current. It is not guaranteed to be a complete
1897 list of such breakages, and only contains entries since October 16, 2004.
1898 If you need to see UPDATING entries from before that date, you will need
1899 to fetch an UPDATING file from an older FreeBSD release.
1901 Copyright information:
1903 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
1905 Redistribution, publication, translation and use, with or without
1906 modification, in full or in part, in any form or format of this
1907 document are permitted without further permission from the author.
1909 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1910 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1911 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1912 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1913 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1914 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1915 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1916 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1917 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1918 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1919 POSSIBILITY OF SUCH DAMAGE.
1921 If you find this document useful, and you want to, you may buy the
1924 Contact Warner Losh if you have any questions about your use of