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 The sparc64 ZFS loader has been changed to no longer try to auto-
20 detect ZFS providers based on diskN aliases but now requires these
21 to be explicitly listed in the OFW boot-device environment variable.
27 A new VOP_ADVISE() was added to support posix_fadvise(2). All
28 filesystem modules must be recompiled.
31 A new VOP_ALLOCATE() was added to support posix_fallocate(2). All
32 filesystem modules must be recompiled.
35 The broken amd(4) driver has been replaced with esp(4) in the amd64,
36 i386 and pc98 GENERIC kernel configuration files.
39 A new version of ZFS (version 28) has been merged.
40 This version does not depend on a python library and the
41 sysutils/py-zfs port is not used anymore.
42 For upgrading your boot pool, please read "ZFS notes"
43 in the COMMON ITEMS: section later in this file.
46 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
47 compliant, and will now use half of hash for authentication.
48 This will break interoperability with all stacks (including all
49 older FreeBSD versions) who implement
50 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
52 The only workaround with such peers is to use another HMAC
53 algorithm for IPsec ("phase 2") authentication.
59 New version of minidump format for amd64 architecture was
60 introduced in r215872. To analyze vmcore files produced by
61 kernels at or after this version you will need updated userland,
62 libkvm actually, that is able to handle the new version.
65 A workaround for a fixed ld bug has been removed in kernel code,
66 so make sure that your system ld is built from sources after
67 revision 211583 from 2010-08-21 (r210245 from 2010-07-19 if
68 building stable/8 kernel on head, r211584 from 2010-08-21 for
69 stable/7). A symptom of incorrect ld version is
70 different addresses for set_pcpu section and __start_set_pcpu
71 symbol in kernel and/or modules.
74 A new version of ZFS (version 15) has been merged.
75 This version uses a python library for the following subcommands:
76 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
77 For full functionality of these commands the following port must
78 be installed: sysutils/py-zfs
84 The config(8) command has been updated to maintain compatibility
85 with config files from 8.0-RELEASE. You will need a new version
86 of config to build kernels (this version can be used from 8.0-RELEASE
87 forward). The buildworld target will generate it, so following
88 the instructions in this file for updating will work glitch-free.
89 Merely doing a make buildkernel without first doing a make buildworld
90 (or kernel-toolchain), or attempting to build a kernel using
91 traidtional methods will generate a config version warning, indicating
95 The rc.firewall and rc.firewall6 were unified, and
96 rc.firewall6 and rc.d/ip6fw were removed.
97 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
98 variables are obsoleted. Instead, the following new rc
99 variables are added to rc.d/ipfw:
101 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
102 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
103 firewall_simple_onet_ipv6
105 The meanings correspond to the relevant IPv4 variables.
108 COMPAT_IA32 has been added as an alias for COMPAT_FREEBSD32. A new
109 version of config(8) is required. The error message when you hit this
110 condition is confusing (COMPAT_FREEBSD32 duplicate option), when it
111 should really say "your config is too old to compile this new kernel."
114 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
115 to allow 32-bit compatibility on non-x86 platforms. All kernel
116 configurations on amd64 and ia64 platforms using these options must
117 be modified accordingly.
120 Introduce the kernel thread "deadlock resolver" (which can be enabled
121 via the DEADLKRES option, see NOTES for more details) and the
122 sleepq_type() function for sleepqueues.
128 802.11s D3.03 support was committed. This is incompatible with
129 the previous code, which was based on D3.0.
132 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
133 mount(8) and -a option for df(1) to see them.
136 Remove the option STOP_NMI. The default action is now to use NMI
137 only for KDB via the newly introduced function stop_cpus_hard()
138 and maintain stop_cpus() to just use a normal IPI_STOP on ia32
145 Bump the shared library version numbers for all libraries that
146 do not use symbol versioning as part of the 8.0-RELEASE cycle.
147 Bump __FreeBSD_version to 800105.
150 Due to changes in the implementation of virtual network stack
151 support, all network-related kernel modules must be recompiled.
152 As this change breaks the ABI, bump __FreeBSD_version to 800104.
155 The TOE interface to the TCP syncache has been modified to remove struct
156 tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack. The
157 cxgb driver is the only TOE consumer affected by this change, and needs
158 to be recompiled along with the kernel. As this change breaks the ABI,
159 bump __FreeBSD_version to 800103.
162 Padding has been added to struct tcpcb, sackhint and tcpstat in
163 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
164 maintainig the ABI. However, this change breaks the ABI, so bump
165 __FreeBSD_version to 800102. User space tools that rely on the size of
166 any of these structs (e.g. sockstat) need to be recompiled.
169 The NFS_LEGACYRPC option has been removed along with the old
170 kernel RPC implementation that this option selected. Kernel
171 configurations may need to be adjusted.
174 The network interface device nodes at /dev/net/<interface> have
175 been removed. All ioctl operations can be performed the normal
176 way using routing sockets. The kqueue functionality can
177 generally be replaced with routing sockets.
180 The documentation from the FreeBSD Documentation Project
181 (Handbook, FAQ, etc.) is now installed via packages by
182 sysinstall(8) and under the /usr/local/share/doc/freebsd
183 directory instead of /usr/share/doc.
186 The ABI of various structures related to the SYSV IPC API have
187 been changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43
188 kernel options now all require COMPAT_FREEBSD7.
189 Bump __FreeBSD_version to 800100.
192 Layout of struct vnet has changed as routing related variables
193 were moved to their own Vimage module. Modules need to be
194 recompiled. Bump __FreeBSD_version to 800099.
197 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023
198 and 1024 respectively. As long as no more than 16 groups per
199 process are used, no changes should be visible. When more
200 than 16 groups are used, old binaries may fail if they call
201 getgroups() or getgrouplist() with statically sized storage.
202 Recompiling will work around this, but applications should be
203 modified to use dynamically allocated storage for group arrays
204 as POSIX.1-2008 does not cap an implementation's number of
205 supported groups at NGROUPS_MAX+1 as previous versions did.
207 NFS and portalfs mounts may also be affected as the list of
208 groups is truncated to 16. Users of NFS who use more than 16
209 groups, should take care that negative group permissions are not
210 used on the exported file systems as they will not be reliable
211 unless a GSSAPI based authentication method is used.
214 The compiling option ADAPTIVE_LOCKMGRS has been introduced.
215 This option compiles in the support for adaptive spinning for lockmgrs
216 which want to enable it. The lockinit() function now accepts the
217 flag LK_ADAPTIVE in order to make the lock object subject to
218 adaptive spinning when both held in write and read mode.
221 The layout of the structure returned by IEEE80211_IOC_STA_INFO
222 has changed. User applications that use this ioctl need to be
226 The layout of struct thread has changed. Kernel and modules
230 The layout of structs ifnet, domain, protosw and vnet_net has
231 changed. Kernel modules need to be rebuilt.
232 Bump __FreeBSD_version to 800097.
235 window(1) has been removed from the base system. It can now be
236 installed from ports. The port is called misc/window.
239 The way we are storing and accessing `routing table' entries
240 has changed. Programs reading the FIB, like netstat, need to
244 A new netisr implementation has been added for FreeBSD 8. Network
245 file system modules, such as igmp, ipdivert, and others, should be
247 Bump __FreeBSD_version to 800096.
250 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose
254 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
255 Bump __FreeBSD_version to 800094.
258 Add mnt_xflag field to 'struct mount'. File system modules
260 Bump __FreeBSD_version to 800093.
263 The compiling option ADAPTIVE_SX has been retired while it has been
264 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
265 The KPI for sx_init_flags() changes as accepting flags:
266 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag
267 has been introduced in order to handle the reversed logic.
268 Bump __FreeBSD_version to 800092.
271 Add support for hierarchical jails. Remove global securelevel.
272 Bump __FreeBSD_version to 800091.
275 The layout of struct vnet_net has changed, therefore modules
277 Bump __FreeBSD_version to 800090.
280 The newly imported zic(8) produces a new format in the
281 output. Please run tzsetup(8) to install the newly created
282 data to /etc/localtime.
285 The sysctl tree for the usb stack has renamed from hw.usb2.* to
286 hw.usb.* and is now consistent again with previous releases.
289 802.11 monitor mode support was revised and driver api's
290 were changed. Drivers dependent on net80211 now support
291 DLT_IEEE802_11_RADIO instead of DLT_IEEE802_11. No
292 user-visible data structures were changed but applications
293 that use DLT_IEEE802_11 may require changes.
294 Bump __FreeBSD_version to 800088.
297 The layout of the following structs has changed: sysctl_oid,
298 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
299 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
300 panics may be experienced. World rebuild is required for
301 correctly checking networking state from userland.
302 Bump __FreeBSD_version to 800085.
305 MLDv2 and Source-Specific Multicast (SSM) have been merged
306 to the IPv6 stack. VIMAGE hooks are in but not yet used.
307 The implementation of SSM within FreeBSD's IPv6 stack closely
308 follows the IPv4 implementation.
310 For kernel developers:
312 * The most important changes are that the ip6_output() and
313 ip6_input() paths no longer take the IN6_MULTI_LOCK,
314 and this lock has been downgraded to a non-recursive mutex.
316 * As with the changes to the IPv4 stack to support SSM, filtering
317 of inbound multicast traffic must now be performed by transport
318 protocols within the IPv6 stack. This does not apply to TCP and
319 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
321 * The KPIs used by IPv6 multicast are similar to those used by
322 the IPv4 stack, with the following differences:
323 * im6o_mc_filter() is analogous to imo_multicast_filter().
324 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
325 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
326 * IN6_LOOKUP_MULTI() has been deprecated and removed.
327 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
328 for MLDv1 have an additional 'timer' argument which is used to
329 jitter the initial membership report for the solicited-node
330 multicast membership on-link.
331 * This is not strictly needed for MLDv2, which already jitters
332 its report transmissions. However, the 'timer' argument is
333 preserved in case MLDv1 is active on the interface.
335 * The KAME linked-list based IPv6 membership implementation has
336 been refactored to use a vector similar to that used by the IPv4
338 Code which maintains a list of its own multicast memberships
339 internally, e.g. carp, has been updated to reflect the new
342 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
343 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
344 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
345 implementation constraint which needs to be addressed in HEAD.
347 For application developers:
349 * The changes are broadly similar to those made for the IPv4
352 * The use of IPv4 and IPv6 multicast socket options on the same
353 socket, using mapped addresses, HAS NOT been tested or supported.
355 * There are a number of issues with the implementation of various
356 IPv6 multicast APIs which need to be resolved in the API surface
357 before the implementation is fully compatible with KAME userland
358 use, and these are mostly to do with interface index treatment.
360 * The literature available discusses the use of either the delta / ASM
361 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
362 using setsourcefilter(3)/getsourcefilter(3). For more information
363 please refer to RFC 3768, 'Socket Interface Extensions for
364 Multicast Source Filters'.
366 * Applications which use the published RFC 3678 APIs should be fine.
368 For systems administrators:
370 * The mtest(8) utility has been refactored to support IPv6, in
371 addition to IPv4. Interface addresses are no longer accepted
372 as arguments, their names must be used instead. The utility
373 will map the interface name to its first IPv4 address as
374 returned by getifaddrs(3).
376 * The ifmcstat(8) utility has also been updated to print the MLDv2
377 endpoint state and source filter lists via sysctl(3).
379 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
380 loopback of IPv6 multicast datagrams by default; it defaults to 1
381 to preserve the existing behaviour. Disabling multicast loopback is
382 recommended for optimal system performance.
384 * The IPv6 MROUTING code has been changed to examine this sysctl
385 instead of attempting to perform a group lookup before looping
386 back forwarded datagrams.
388 Bump __FreeBSD_version to 800084.
391 Implement low-level Bluetooth HCI API.
392 Bump __FreeBSD_version to 800083.
395 The layout of struct malloc_type, used by modules to register new
396 memory allocation types, has changed. Most modules will need to
397 be rebuilt or panics may be experienced.
398 Bump __FreeBSD_version to 800081.
401 Anticipate overflowing inp_flags - add inp_flags2.
402 This changes most offsets in inpcb, so checking v4 connection
403 state will require a world rebuild.
404 Bump __FreeBSD_version to 800080.
407 Add an llentry to struct route and struct route_in6. Modules
408 embedding a struct route will need to be recompiled.
409 Bump __FreeBSD_version to 800079.
412 The size of rt_metrics_lite and by extension rtentry has changed.
413 Networking administration apps will need to be recompiled.
414 The route command now supports show as an alias for get, weighting
415 of routes, sticky and nostick flags to alter the behavior of stateful
417 Bump __FreeBSD_version to 800078.
420 Do not use Giant for kbdmux(4) locking. This is wrong and
421 apparently causing more problems than it solves. This will
422 re-open the issue where interrupt handlers may race with
423 kbdmux(4) in polling mode. Typical symptoms include (but
424 not limited to) duplicated and/or missing characters when
425 low level console functions (such as gets) are used while
426 interrupts are enabled (for example geli password prompt,
427 mountroot prompt etc.). Disabling kbdmux(4) may help.
430 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
431 kernel modules referencing any of the above need to be recompiled.
432 Bump __FreeBSD_version to 800075.
435 GEOM_PART has become the default partition slicer for storage devices,
436 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
437 introduces some changes:
439 MSDOS/EBR: the devices created from MSDOS extended partition entries
440 (EBR) can be named differently than with GEOM_MBR and are now symlinks
441 to devices with offset-based names. fstabs may need to be modified.
443 BSD: the "geometry does not match label" warning is harmless in most
444 cases but it points to problems in file system misalignment with
445 disk geometry. The "c" partition is now implicit, covers the whole
446 top-level drive and cannot be (mis)used by users.
448 General: Kernel dumps are now not allowed to be written to devices
449 whose partition types indicate they are meant to be used for file
450 systems (or, in case of MSDOS partitions, as something else than
453 Most of these changes date approximately from 200812.
456 The uscanner(4) driver has been removed from the kernel. This follows
457 Linux removing theirs in 2.6 and making libusb the default interface
461 The multicast forwarding code has been cleaned up. netstat(1)
462 only relies on KVM now for printing bandwidth upcall meters.
463 The IPv4 and IPv6 modules are split into ip_mroute_mod and
464 ip6_mroute_mod respectively. The config(5) options for statically
465 compiling this code remain the same, i.e. 'options MROUTING'.
468 Support for the IFF_NEEDSGIANT network interface flag has been
469 removed, which means that non-MPSAFE network device drivers are no
470 longer supported. In particular, if_ar, if_sr, and network device
471 drivers from the old (legacy) USB stack can no longer be built or
475 POSIX.1 Native Language Support (NLS) has been enabled in libc and
476 a bunch of new language catalog files have also been added.
477 This means that some common libc messages are now localized and
478 they depend on the LC_MESSAGES environmental variable.
481 The k8temp(4) driver has been renamed to amdtemp(4) since
482 support for K10 and K11 CPU families was added.
485 IGMPv3 and Source-Specific Multicast (SSM) have been merged
486 to the IPv4 stack. VIMAGE hooks are in but not yet used.
488 For kernel developers, the most important changes are that the
489 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
490 and this lock has been downgraded to a non-recursive mutex.
492 Transport protocols (UDP, Raw IP) are now responsible for filtering
493 inbound multicast traffic according to group membership and source
494 filters. The imo_multicast_filter() KPI exists for this purpose.
495 Transports which do not use multicast (SCTP, TCP) already reject
496 multicast by default. Forwarding and receive performance may improve
497 as a mutex acquisition is no longer needed in the ip_input()
498 low-level input path. in_addmulti() and in_delmulti() are shimmed
499 to new KPIs which exist to support SSM in-kernel.
501 For application developers, it is recommended that loopback of
502 multicast datagrams be disabled for best performance, as this
503 will still cause the lock to be taken for each looped-back
504 datagram transmission. The net.inet.ip.mcast.loop sysctl may
505 be tuned to 0 to disable loopback by default; it defaults to 1
506 to preserve the existing behaviour.
508 For systems administrators, to obtain best performance with
509 multicast reception and multiple groups, it is always recommended
510 that a card with a suitably precise hash filter is used. Hash
511 collisions will still result in the lock being taken within the
512 transport protocol input path to check group membership.
514 If deploying FreeBSD in an environment with IGMP snooping switches,
515 it is recommended that the net.inet.igmp.sendlocal sysctl remain
516 enabled; this forces 224.0.0.0/24 group membership to be announced
519 The size of 'struct igmpstat' has changed; netstat needs to be
520 recompiled to reflect this.
521 Bump __FreeBSD_version to 800070.
524 libusb20.so.1 is now installed as libusb.so.1 and the ports system
525 updated to use it. This requires a buildworld/installworld in order to
526 update the library and dependencies (usbconfig, etc). Its advisable to
527 rebuild all ports which uses libusb. More specific directions are given
528 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
529 libusb are no longer required and can be removed.
532 A workaround is committed to allow the creation of System V shared
533 memory segment of size > 2 GB on the 64-bit architectures.
534 Due to a limitation of the existing ABI, the shm_segsz member
535 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
536 wrong for large segments. Note that limits must be explicitly
537 raised to allow such segments to be created.
540 The layout of struct ifnet has changed, requiring a rebuild of all
541 network device driver modules.
544 The /dev handling for the new USB stack has changed, a
545 buildworld/installworld is required for libusb20.
548 The new USB2 stack has now been permanently moved in and all kernel and
549 module names reverted to their previous values (eg, usb, ehci, ohci,
550 ums, ...). The old usb stack can be compiled in by prefixing the name
551 with the letter 'o', the old usb modules have been removed.
552 Updating entry 20090216 for xorg and 20090215 for libmap may still
556 The rc.conf(5) option if_up_delay has been renamed to
557 defaultroute_delay to better reflect its purpose. If you have
558 customized this setting in /etc/rc.conf you need to update it to
562 xorg 7.4 wants to configure its input devices via hald which does not
563 yet work with USB2. If the keyboard/mouse does not work in xorg then
565 Option "AllowEmptyInput" "off"
566 to your ServerLayout section. This will cause X to use the configured
567 kbd and mouse sections from your xorg.conf.
570 The GENERIC kernels for all architectures now default to the new USB2
571 stack. No kernel config options or code have been removed so if a
572 problem arises please report it and optionally revert to the old USB
573 stack. If you are loading USB kernel modules or have a custom kernel
574 that includes GENERIC then ensure that usb names are also changed over,
575 eg uftdi -> usb2_serial_ftdi.
577 Older programs linked against the ports libusb 0.1 need to be
578 redirected to the new stack's libusb20. /etc/libmap.conf can
580 # Map old usb library to new one for usb2 stack
581 libusb-0.1.so.8 libusb20.so.1
584 All USB ethernet devices now attach as interfaces under the name ueN
585 (eg. ue0). This is to provide a predictable name as vendors often
586 change usb chipsets in a product without notice.
589 The ichsmb(4) driver has been changed to require SMBus slave
590 addresses be left-justified (xxxxxxx0b) rather than right-justified.
591 All of the other SMBus controller drivers require left-justified
592 slave addresses, so this change makes all the drivers provide the
596 INET6 statistics (struct ip6stat) was updated.
597 netstat(1) needs to be recompiled.
600 NTFS has been removed from GENERIC kernel on amd64 to match
601 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
602 will load ntfs.ko module automatically when NTFS support is
603 actually needed, unless ntfs.ko is not installed or security
604 level prohibits loading kernel modules. If either is the case,
605 "options NTFS" has to be added into kernel config.
608 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
609 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
610 800061. User space tools that rely on the size of struct tcpcb in
611 tcp_var.h (e.g. sockstat) need to be recompiled.
614 ng_tty(4) module updated to match the new TTY subsystem.
615 Due to API change, user-level applications must be updated.
616 New API support added to mpd5 CVS and expected to be present
617 in next mpd5.3 release.
620 With __FreeBSD_version 800060 the makefs tool is part of
621 the base system (it was a port).
624 The afdata and ifnet locks have been changed from mutexes to
625 rwlocks, network modules will need to be re-compiled.
628 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
629 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
630 The new code reduced struct rtentry{} by 16 bytes on 32-bit
631 architecture and 40 bytes on 64-bit architecture. The userland
632 applications "arp" and "ndp" have been updated accordingly.
633 The output from "netstat -r" shows only routing entries and
634 none of the L2 information.
637 __FreeBSD_version 800057 marks the switchover from the
638 binary ath hal to source code. Users must add the line:
640 options AH_SUPPORT_AR5416
642 to their kernel config files when specifying:
646 The ath_hal module no longer exists; the code is now compiled
647 together with the driver in the ath module. It is now
648 possible to tailor chip support (i.e. reduce the set of chips
649 and thereby the code size); consult ath_hal(4) for details.
652 __FreeBSD_version 800054 adds memory barriers to
653 <machine/atomic.h>, new interfaces to ifnet to facilitate
654 multiple hardware transmit queues for cards that support
655 them, and a lock-less ring-buffer implementation to
656 enable drivers to more efficiently manage queueing of
660 A new version of ZFS (version 13) has been merged to -HEAD.
661 This version has zpool attribute "listsnapshots" off by
662 default, which means "zfs list" does not show snapshots,
663 and is the same as Solaris behavior.
666 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
669 The uhci, ohci, ehci and slhci USB Host controller drivers have
670 been put into separate modules. If you load the usb module
671 separately through loader.conf you will need to load the
672 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
673 controller add the following to loader.conf:
679 The ABI used by the PMC toolset has changed. Please keep
680 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
684 atapci kernel module now includes only generic PCI ATA
685 driver. AHCI driver moved to ataahci kernel module.
686 All vendor-specific code moved into separate kernel modules:
687 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
688 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
689 atamarvell, atamicron, atanational, atanetcell, atanvidia,
690 atapromise, ataserverworks, atasiliconimage, atasis, atavia
693 The TTY subsystem of the kernel has been replaced by a new
694 implementation, which provides better scalability and an
695 improved driver model. Most common drivers have been migrated to
696 the new TTY subsystem, while others have not. The following
697 drivers have not yet been ported to the new TTY layer:
700 cy, digi, rc, rp, sio
706 ng_h4, ng_tty, ppp, sl, snp
708 Adding these drivers to your kernel configuration file shall
709 cause compilation to fail.
712 ntpd has been upgraded to 4.2.4p5.
715 OpenSSH has been upgraded to 5.1p1.
717 For many years, FreeBSD's version of OpenSSH preferred DSA
718 over RSA for host and user authentication keys. With this
719 upgrade, we've switched to the vendor's default of RSA over
720 DSA. This may cause upgraded clients to warn about unknown
721 host keys even for previously known hosts. Users should
722 follow the usual procedure for verifying host keys before
723 accepting the RSA key.
725 This can be circumvented by setting the "HostKeyAlgorithms"
726 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
729 Please note that the sequence of keys offered for
730 authentication has been changed as well. You may want to
731 specify IdentityFile in a different order to revert this
735 The sio(4) driver has been removed from the i386 and amd64
736 kernel configuration files. This means uart(4) is now the
737 default serial port driver on those platforms as well.
739 To prevent collisions with the sio(4) driver, the uart(4) driver
740 uses different names for its device nodes. This means the
741 onboard serial port will now most likely be called "ttyu0"
742 instead of "ttyd0". You may need to reconfigure applications to
743 use the new device names.
745 When using the serial port as a boot console, be sure to update
746 /boot/device.hints and /etc/ttys before booting the new kernel.
747 If you forget to do so, you can still manually specify the hints
748 at the loader prompt:
750 set hint.uart.0.at="isa"
751 set hint.uart.0.port="0x3F8"
752 set hint.uart.0.flags="0x10"
753 set hint.uart.0.irq="4"
757 The gpt(8) utility has been removed. Use gpart(8) to partition
761 The version that Linuxulator emulates was changed from 2.4.2
762 to 2.6.16. If you experience any problems with Linux binaries
763 please try to set sysctl compat.linux.osrelease to 2.4.2 and
764 if it fixes the problem contact emulation mailing list.
767 ISDN4BSD (I4B) was removed from the src tree. You may need to
768 update a your kernel configuration and remove relevant entries.
771 I have checked in code to support multiple routing tables.
772 See the man pages setfib(1) and setfib(2).
773 This is a hopefully backwards compatible version,
774 but to make use of it you need to compile your kernel
775 with options ROUTETABLES=2 (or more up to 16).
778 The 802.11 wireless support was redone to enable multi-bss
779 operation on devices that are capable. The underlying device
780 is no longer used directly but instead wlanX devices are
781 cloned with ifconfig. This requires changes to rc.conf files.
783 ifconfig_ath0="WPA DHCP"
786 ifconfig_wlan0="WPA DHCP"
787 see rc.conf(5) for more details. In addition, mergemaster of
788 /etc/rc.d is highly recommended. Simultaneous update of userland
789 and kernel wouldn't hurt either.
791 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
792 modules were merged into the base wlan module. All references
793 to these modules (e.g. in kernel config files) must be removed.
796 psm(4) has gained write(2) support in native operation level.
797 Arbitrary commands can be written to /dev/psm%d and status can
798 be read back from it. Therefore, an application is responsible
799 for status validation and error recovery. It is a no-op in
800 other operation levels.
803 Support for KSE threading has been removed from the kernel. To
804 run legacy applications linked against KSE libmap.conf may
805 be used. The following libmap.conf may be used to ensure
806 compatibility with any prior release:
808 libpthread.so.1 libthr.so.1
809 libpthread.so.2 libthr.so.2
810 libkse.so.3 libthr.so.3
813 The layout of struct vmspace has changed. This affects libkvm
814 and any executables that link against libkvm and use the
815 kvm_getprocs() function. In particular, but not exclusively,
816 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
817 The effects are minimal, but it's advisable to upgrade world
821 The latest em driver no longer has support in it for the
822 82575 adapter, this is now moved to the igb driver. The
823 split was done to make new features that are incompatible
824 with older hardware easier to do.
827 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
828 likewise the kernel option is now GEOM_LINUX_LVM.
831 The default NFS mount mode has changed from UDP to TCP for
832 increased reliability. If you rely on (insecurely) NFS
833 mounting across a firewall you may need to update your
837 Belatedly note the addition of m_collapse for compacting
841 The fts(3) structures have been changed to use adequate
842 integer types for their members and so to be able to cope
843 with huge file trees. The old fts(3) ABI is preserved
844 through symbol versioning in libc, so third-party binaries
845 using fts(3) should still work, although they will not take
846 advantage of the extended types. At the same time, some
847 third-party software might fail to build after this change
848 due to unportable assumptions made in its source code about
849 fts(3) structure members. Such software should be fixed
850 by its vendor or, in the worst case, in the ports tree.
851 FreeBSD_version 800015 marks this change for the unlikely
852 case that a portable fix is impossible.
855 To upgrade to -current after this date, you must be running
856 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
857 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
860 The ADAPTIVE_GIANT kernel option has been retired because its
861 functionality is the default now.
864 The AT keyboard emulation of sunkbd(4) has been turned on
865 by default. In order to make the special symbols of the Sun
866 keyboards driven by sunkbd(4) work under X these now have
867 to be configured the same way as Sun USB keyboards driven
868 by ukbd(4) (which also does AT keyboard emulation), f.e.:
870 Option "XkbLayout" "us"
871 Option "XkbRules" "xorg"
872 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
875 It has been decided that it is desirable to provide ABI
876 backwards compatibility to the FreeBSD 4/5/6 versions of the
877 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
878 broken with the introduction of PCI domain support (see the
879 20070930 entry). Unfortunately, this required the ABI of
880 PCIOCGETCONF to be broken again in order to be able to
881 provide backwards compatibility to the old version of that
882 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
883 again. As for prominent ports this affects neither pciutils
884 nor xorg-server this time, the hal port needs to be rebuilt
888 The misnamed kthread_create() and friends have been renamed
889 to kproc_create() etc. Many of the callers already
891 I will return kthread_create() and friends in a while
892 with implementations that actually create threads, not procs.
893 Renaming corresponds with version 800002.
899 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
900 WITHOUT_LIBTHR are set.
903 The PCI code has been made aware of PCI domains. This means that
904 the location strings as used by pciconf(8) etc are now in the
905 following format: pci<domain>:<bus>:<device>[:<function>]. It
906 also means that consumers of <sys/pciio.h> potentially need to
907 be recompiled; this includes the hal and xorg-server ports.
910 The caching daemon (cached) was renamed to nscd. nscd.conf
911 configuration file should be used instead of cached.conf and
912 nscd_enable, nscd_pidfile and nscd_flags options should be used
913 instead of cached_enable, cached_pidfile and cached_flags in
917 The getfacl(1) utility now prints owning user and group name
918 instead of owning uid and gid in the three line comment header.
919 This is the same behavior as getfacl(1) on Solaris and Linux.
922 The new IPsec code is now compiled in using the IPSEC option. The
923 IPSEC option now requires "device crypto" be defined in your kernel
924 configuration. The FAST_IPSEC kernel option is now deprecated.
927 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
928 note the changed syntax - keep state is now on by default. Also
929 note the fact that ftp-proxy(8) has been changed from bottom up and
930 has been moved from libexec to usr/sbin. Changes in the ALTQ
931 handling also affect users of IPFW's ALTQ capabilities.
934 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
935 only IPsec supported by FreeBSD. The new IPsec stack
936 supports both IPv4 and IPv6. The kernel option will change
937 after the code changes have settled in. For now the kernel
938 option IPSEC is deprecated and FAST_IPSEC is the only option, that
939 will change after some settling time.
942 The wicontrol(8) utility has been removed from the base system. wi(4)
943 cards should be configured using ifconfig(8), see the man page for more
947 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
948 instead of the nve(4) driver. Please update your configuration
952 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
953 database if it is missing or older than the aliases file. If
954 desired, set the new rc.conf option sendmail_rebuild_aliases
955 to "YES" to restore that functionality.
958 The IPv4 multicast socket code has been considerably modified, and
959 moved to the file sys/netinet/in_mcast.c. Initial support for the
960 RFC 3678 Source-Specific Multicast Socket API has been added to
961 the IPv4 network stack.
963 Strict multicast and broadcast reception is now the default for
964 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
965 has now been removed.
967 The RFC 1724 hack for interface selection has been removed; the use
968 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
969 been added to replace it. Consumers such as routed will soon be
970 updated to reflect this.
972 These changes affect users who are running routed(8) or rdisc(8)
973 from the FreeBSD base system on point-to-point or unnumbered
977 The net80211 layer has changed significantly and all wireless
978 drivers that depend on it need to be recompiled. Further these
979 changes require that any program that interacts with the wireless
980 support in the kernel be recompiled; this includes: ifconfig,
981 wpa_supplicant, hostapd, and wlanstats. Users must also, for
982 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
983 if they use modules for wireless support. These modules implement
984 scanning support for station and ap modes, respectively. Failure
985 to load the appropriate module before marking a wireless interface
986 up will result in a message to the console and the device not
990 The pam_nologin(8) module ceases to provide an authentication
991 function and starts providing an account management function.
992 Consequent changes to /etc/pam.d should be brought in using
993 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
994 need manual editing as follows. Locate this line (or similar):
996 auth required pam_nologin.so no_warn
998 and change it according to this example:
1000 account required pam_nologin.so no_warn
1002 That is, the first word needs to be changed from "auth" to
1003 "account". The new line can be moved to the account section
1004 within the file for clarity. Not updating pam.conf(5) files
1005 will result in nologin(5) ignored by the respective services.
1008 The ether_ioctl() function has been synchronized with ioctl(2)
1009 and ifnet.if_ioctl. Due to that, the size of one of its arguments
1010 has changed on 64-bit architectures. All kernel modules using
1011 ether_ioctl() need to be rebuilt on such architectures.
1014 Improved INCLUDE_CONFIG_FILE support has been introduced to the
1015 config(8) utility. In order to take advantage of this new
1016 functionality, you are expected to recompile and install
1017 src/usr.sbin/config. If you don't rebuild config(8), and your
1018 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
1019 build will be broken because of a missing "kernconfstring"
1023 Symbol versioning is enabled by default. To disable it, use
1024 option WITHOUT_SYMVER. It is not advisable to attempt to
1025 disable symbol versioning once it is enabled; your installworld
1026 will break because a symbol version-less libc will get installed
1027 before the install tools. As a result, the old install tools,
1028 which previously had symbol dependencies to FBSD_1.0, will fail
1029 because the freshly installed libc will not have them.
1031 The default threading library (providing "libpthread") has been
1032 changed to libthr. If you wish to have libkse as your default,
1033 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
1036 The ABI breakage in sendmail(8)'s libmilter has been repaired
1037 so it is no longer necessary to recompile mail filters (aka,
1038 milters). If you recompiled mail filters after the 20070408
1039 note, it is not necessary to recompile them again.
1042 The new trunk(4) driver has been renamed to lagg(4) as it better
1043 reflects its purpose. ifconfig will need to be recompiled.
1046 sendmail(8) has been updated to version 8.14.1. Mail filters
1047 (aka, milters) compiled against the libmilter included in the
1048 base operating system should be recompiled.
1051 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
1052 In order to use them one must agree to the respective LICENSE in
1053 share/doc/legal and define legal.intel_<name>.license_ack=1 via
1054 loader.conf(5) or kenv(1). Make sure to deinstall the now
1055 deprecated modules from the respective firmware ports.
1058 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
1059 were removed from FreeBSD's libc. These originally came from INRIA
1060 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
1061 deprecated in previous releases.
1062 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
1063 replace it as a more portable (and re-entrant) API.
1066 To support interrupt filtering a modification to the newbus API
1067 has occurred, ABI was broken and __FreeBSD_version was bumped
1068 to 700031. Please make sure that your kernel and modules are in
1069 sync. For more info:
1070 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
1073 The IPv6 multicast forwarding code may now be loaded into GENERIC
1074 kernels by loading the ip_mroute.ko module. This is built into the
1075 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
1076 set; see src.conf(5) for more information.
1079 The output of netstat -r has changed. Without -n, we now only
1080 print a "network name" without the prefix length if the network
1081 address and mask exactly match a Class A/B/C network, and an entry
1082 exists in the nsswitch "networks" map.
1083 With -n, we print the full unabbreviated CIDR network prefix in
1084 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
1085 This change is in preparation for changes such as equal-cost
1086 multipath, and to more generally assist operational deployment
1087 of FreeBSD as a modern IPv4 router.
1090 PIM has been turned on by default in the IPv4 multicast
1091 routing code. The kernel option 'PIM' has now been removed.
1092 PIM is now built by default if option 'MROUTING' is specified.
1093 It may now be loaded into GENERIC kernels by loading the
1094 ip_mroute.ko module.
1097 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
1098 has been removed. Its functionality may be achieved by explicitly
1099 configuring gif(4) interfaces and using the 'phyint' keyword in
1101 XORP does not support source-routed IPv4 multicast tunnels nor the
1102 integrated IPIP tunneling, therefore it is not affected by this
1103 change. The __FreeBSD_version macro has been bumped to 700030.
1106 Support for PCI Message Signalled Interrupts has been
1107 re-enabled in the bge driver, only for those chips which are
1108 believed to support it properly. If there are any problems,
1109 MSI can be disabled completely by setting the
1110 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
1114 Support for PCI Message Signalled Interrupts has been
1115 disabled again in the bge driver. Many revisions of the
1116 hardware fail to support it properly. Support can be
1117 re-enabled by removing the #define of BGE_DISABLE_MSI in
1118 "src/sys/dev/bge/if_bge.c".
1121 Support for PCI Message Signalled Interrupts has been added
1122 to the bge driver. If there are any problems, MSI can be
1123 disabled completely by setting the 'hw.pci.enable_msi' and
1124 'hw.pci.enable_msix' tunables to 0 in the loader.
1127 The removal of several facets of the experimental Threading
1128 system from the kernel means that the proc and thread structures
1129 have changed quite a bit. I suggest all kernel modules that might
1130 reference these structures be recompiled.. Especially the
1134 Sound infrastructure has been updated with various fixes and
1135 improvements. Most of the changes are pretty much transparent,
1136 with exceptions of followings:
1137 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
1138 moved to their own dev sysctl nodes, for example:
1139 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
1140 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
1141 own chardev in the form of "dsp%d.<function>%d", where <function>
1142 is p = playback, r = record and v = virtual, respectively. Users
1143 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
1144 This does not affect those who are using "/dev/dsp".
1147 geom(4)'s gmirror(8) class metadata structure has been
1148 rev'd from v3 to v4. If you update across this point and
1149 your metadata is converted for you, you will not be easily
1150 able to downgrade since the /boot/kernel.old/geom_mirror.ko
1151 kernel module will be unable to read the v4 metadata. You
1152 can resolve this by doing from the loader(8) prompt:
1154 set vfs.root.mountfrom="ufs:/dev/XXX"
1156 where XXX is the root slice of one of the disks that composed
1157 the mirror (i.e.: /dev/ad0s1a). You can then rebuild
1158 the array the same way you built it originally.
1161 The following binaries have been disconnected from the build:
1162 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
1163 and mount_std. The functionality of these programs has been
1164 moved into the mount program. For example, to mount a devfs
1165 filesystem, instead of using mount_devfs, use: "mount -t devfs".
1166 This does not affect entries in /etc/fstab, since entries in
1167 /etc/fstab are always processed with "mount -t fstype".
1170 Support for PCI Message Signalled Interrupts on i386 and amd64
1171 has been added to the kernel and various drivers will soon be
1172 updated to use MSI when it is available. If there are any problems,
1173 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
1174 and 'hw.pci.enable_msix' tunables to 0 in the loader.
1177 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
1178 The lockmgr object layout has been changed as a result of having
1179 a lock_object embedded in it. As a consequence all file system
1180 kernel modules must be re-compiled. The mutex profiling man page
1181 has not yet been updated to reflect this change.
1184 KSE in the kernel has now been made optional and turned on by
1185 default. Use 'nooption KSE' in your kernel config to turn it
1186 off. All kernel modules *must* be recompiled after this change.
1187 There-after, modules from a KSE kernel should be compatible with
1188 modules from a NOKSE kernel due to the temporary padding fields
1189 added to 'struct proc'.
1192 mrouted and its utilities have been removed from the base system.
1195 Some ioctl(2) command codes have changed. Full backward ABI
1196 compatibility is provided if the "options COMPAT_FREEBSD6" is
1197 present in the kernel configuration file. Make sure to add
1198 this option to your kernel config file, or recompile X.Org
1199 and the rest of ports; otherwise they may refuse to work.
1202 tcpslice has been removed from the base system.
1205 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
1206 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
1207 systat needs to be rebuilt.
1210 libpcap updated to v0.9.4 and tcpdump to v3.9.4
1213 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
1214 for IPFIREWALL_FORWARD is now as it was before when it was first
1215 committed and for years after. The behaviour is now ON.
1218 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
1219 Now it can decrypt files created from different architectures.
1220 Unfortunately, it is no longer able to decrypt a cipher text
1221 generated with an older version on 64 bit architectures.
1222 If you have such a file, you need old utility to decrypt it.
1225 The interface version of the i4b kernel part has changed. So
1226 after updating the kernel sources and compiling a new kernel,
1227 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
1228 be rebuilt, and vice versa.
1231 The XBOX kernel now defaults to the nfe(4) driver instead of
1232 the nve(4) driver. Please update your configuration
1236 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
1237 PCnet family of NICs has been removed. The new le(4) driver serves
1238 as an equivalent but cross-platform replacement with the pcn(4)
1239 driver still providing performance-optimized support for the subset
1240 of AMD Am79C971 PCnet-FAST and greater chips as before.
1243 The machdep.* sysctls and the adjkerntz utility have been
1244 modified a bit. The new adjkerntz utility uses the new
1245 sysctl names and sysctlbyname() calls, so it may be impossible
1246 to run an old /sbin/adjkerntz utility in single-user mode
1247 with a new kernel. Replace the `adjkerntz -i' step before
1248 `make installworld' with:
1250 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
1252 and proceed as usual with the rest of the installworld-stage
1253 steps. Otherwise, you risk installing binaries with their
1254 timestamp set several hours in the future, especially if
1255 you are running with local time set to GMT+X hours.
1258 The ip6fw utility has been removed. The behavior provided by
1259 ip6fw has been in ipfw2 for a good while and the rc.d scripts
1260 have been updated to deal with it. There are some rules that
1261 might not migrate cleanly. Use rc.firewall6 as a template to
1265 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
1266 attachments have been removed. Make sure to configure scc(4)
1267 on sparc64. Note also that by default puc(4) will use uart(4)
1268 and not sio(4) for serial ports because interrupt handling has
1269 been optimized for multi-port serial cards and only uart(4)
1270 implements the interface to support it.
1273 The scc(4) driver replaces puc(4) for Serial Communications
1274 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
1275 Z8530. On sparc64, it is advised to add scc(4) to the kernel
1276 configuration to make sure that the serial ports remain
1280 Most world/kernel related NO_* build options changed names.
1281 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
1282 after FreeBSD ports) and should be set in /etc/src.conf
1283 (the src.conf(5) manpage is provided). Full backwards
1284 compatibility is maintained for the time being though it's
1285 highly recommended to start moving old options out of the
1286 system-wide /etc/make.conf file into the new /etc/src.conf
1287 while also properly renaming them. More conversions will
1288 likely follow. Posting to current@:
1290 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
1293 The NETSMBCRYPTO kernel option has been retired because its
1294 functionality is always included in NETSMB and smbfs.ko now.
1297 The TDFX_LINUX kernel option was retired and replaced by the
1298 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
1299 kernel module. Loading it alone should suffice to get 3dfx support
1300 for Linux apps because it will pull in 3dfx.ko and linux.ko through
1304 The 'audit' group was added to support the new auditing functionality
1305 in the base system. Be sure to follow the directions for updating,
1306 including the requirement to run mergemaster -p.
1309 The kernel ABI to file system modules was changed on i386.
1310 Please make sure that your kernel and modules are in sync.
1313 This actually occured some time ago, but installing the kernel
1314 now also installs a bunch of symbol files for the kernel modules.
1315 This increases the size of /boot/kernel to about 67Mbytes. You
1316 will need twice this if you will eventually back this up to kernel.old
1317 on your next install.
1318 If you have a shortage of room in your root partition, you should add
1319 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
1320 to your /etc/make.conf.
1323 libc's malloc implementation has been replaced. This change has the
1324 potential to uncover application bugs that previously went unnoticed.
1325 See the malloc(3) manual page for more details.
1328 The generic netgraph(4) cookie has been changed. If you upgrade
1329 kernel passing this point, you also need to upgrade userland
1330 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
1333 si(4)'s device files now contain the unit number.
1334 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
1337 The kernel ABI was mostly destroyed due to a change in the size
1338 of struct lock_object which is nested in other structures such
1339 as mutexes which are nested in all sorts of other structures.
1340 Make sure your kernel and modules are in sync.
1343 The page coloring algorithm in the VM subsystem was converted
1344 from tuning with kernel options to autotuning. Please remove
1345 any PQ_* option except PQ_NOOPT from your kernel config.
1348 The net80211-related tools in the tools/tools/ath directory
1349 have been moved to tools/tools/net80211 and renamed with a
1350 "wlan" prefix. Scripts that use them should be adjusted
1354 Scripts in the local_startup directories (as defined in
1355 /etc/defaults/rc.conf) that have the new rc.d semantics will
1356 now be run as part of the base system rcorder. If there are
1357 errors or problems with one of these local scripts, it could
1358 cause boot problems. If you encounter such problems, boot in
1359 single user mode, remove that script from the */rc.d directory.
1360 Please report the problem to the port's maintainer, and the
1361 freebsd-ports@freebsd.org mailing list.
1364 The nodev mount option was deprecated in RELENG_6 (where it
1365 was a no-op), and is now unsupported. If you have nodev or dev listed
1366 in /etc/fstab, remove it, otherwise it will result in a mount error.
1369 ABI between ipfw(4) and ipfw(8) has been changed. You need
1370 to rebuild ipfw(8) when rebuilding kernel.
1373 rp(4)'s device files now contain the unit number.
1374 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
1377 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
1378 Its /etc/rc.conf.d configuration file has been `ppp' from
1379 the beginning, and hence there is no need to touch it.
1382 Now most modules get their build-time options from the kernel
1383 configuration file. A few modules still have fixed options
1384 due to their non-conformant implementation, but they will be
1385 corrected eventually. You may need to review the options of
1386 the modules in use, explicitly specify the non-default options
1387 in the kernel configuration file, and rebuild the kernel and
1391 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
1392 to turn polling(4) on your interfaces.
1395 The old bridge(4) implementation was retired. The new
1396 if_bridge(4) serves as a full functional replacement.
1399 The ai_addrlen of a struct addrinfo was changed to a socklen_t
1400 to conform to POSIX-2001. This change broke an ABI
1401 compatibility on 64 bit architecture. You have to recompile
1402 userland programs that use getaddrinfo(3) on 64 bit
1406 RELENG_6 branched here.
1409 The pccard_ifconfig rc.conf variable has been removed and a new
1410 variable, ifconfig_DEFAULT has been introduced. Unlike
1411 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
1412 do not have ifconfig_ifn entries rather than just those in
1413 removable_interfaces.
1416 Some previous versions of PAM have permitted the use of
1417 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
1418 to third party PAM modules in /usr/local/lib. A change has been
1419 made to require the use of absolute paths in order to avoid
1420 ambiguity and dependence on library path configuration, which may
1421 affect existing configurations.
1424 Major changes to network interface API. All drivers must be
1425 recompiled. Drivers not in the base system will need to be
1426 updated to the new APIs.
1429 Changes were made to kinfo_proc in sys/user.h. Please recompile
1430 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
1431 will not behave correctly.
1433 The API and ABI for hwpmc(4) have changed with the addition
1434 of sampling support. Please recompile lib/libpmc(3) and
1435 usr.sbin/{pmcstat,pmccontrol}.
1438 The OpenBSD dhclient was imported in place of the ISC dhclient
1439 and the network interface configuration scripts were updated
1440 accordingly. If you use DHCP to configure your interfaces, you
1441 must now run devd. Also, DNS updating was lost so you will need
1442 to find a workaround if you use this feature.
1444 The '_dhcp' user was added to support the OpenBSD dhclient. Be
1445 sure to run mergemaster -p (like you are supposed to do every time
1449 if_bridge was added to the tree. This has changed struct ifnet.
1450 Please recompile userland and all network related modules.
1453 The n_net of a struct netent was changed to an uint32_t, and
1454 1st argument of getnetbyaddr() was changed to an uint32_t, to
1455 conform to POSIX-2001. These changes broke an ABI
1456 compatibility on 64 bit architecture. With these changes,
1457 shlib major of libpcap was bumped. You have to recompile
1458 userland programs that use getnetbyaddr(3), getnetbyname(3),
1459 getnetent(3) and/or libpcap on 64 bit architecture.
1462 Kernel parsing of extra options on '#!' first lines of shell
1463 scripts has changed. Lines with multiple options likely will
1464 fail after this date. For full details, please see
1465 http://people.freebsd.org/~gad/Updating-20050528.txt
1468 The packet filter (pf) code has been updated to OpenBSD 3.7
1469 Please note the changed anchor syntax and the fact that
1470 authpf(8) now needs a mounted fdescfs(5) to function.
1473 The NO_MIXED_MODE kernel option has been removed from the i386
1474 amd64 platforms as its use has been superceded by the new local
1475 APIC timer code. Any kernel config files containing this option
1479 The on-disk format of LC_CTYPE files was changed to be machine
1480 independent. Please make sure NOT to use NO_CLEAN buildworld
1481 when crossing this point. Crossing this point also requires
1482 recompile or reinstall of all locale depended packages.
1485 The ifi_epoch member of struct if_data has been changed to
1486 contain the uptime at which the interface was created or the
1487 statistics zeroed rather then the wall clock time because
1488 wallclock time may go backwards. This should have no impact
1489 unless an snmp implementation is using this value (I know of
1490 none at this point.)
1493 The acpi_perf and acpi_throttle drivers are now part of the
1494 acpi(4) main module. They are no longer built separately.
1497 The layout of struct image_params has changed. You have to
1498 recompile all compatibility modules (linux, svr4, etc) for use
1499 with the new kernel.
1502 The p4tcc driver has been merged into cpufreq(4). This makes
1503 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
1504 compile in "device cpufreq" to restore this functionality.
1507 The responsibility of recomputing the file system summary of
1508 a SoftUpdates-enabled dirty volume has been transferred to the
1509 background fsck. A rebuild of fsck(8) utility is recommended
1510 if you have updated the kernel.
1512 To get the old behavior (recompute file system summary at mount
1513 time), you can set vfs.ffs.compute_summary_at_mount=1 before
1514 mounting the new volume.
1517 The cpufreq import is complete. As part of this, the sysctls for
1518 acpi(4) throttling have been removed. The power_profile script
1519 has been updated, so you can use performance/economy_cpu_freq in
1520 rc.conf(5) to set AC on/offline cpu frequencies.
1523 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
1524 requires recompiling libnetgraph and userland netgraph utilities.
1527 Support for abbreviated forms of a number of ipfw options is
1528 now deprecated. Warnings are printed to stderr indicating the
1529 correct full form when a match occurs. Some abbreviations may
1530 be supported at a later date based on user feedback. To be
1531 considered for support, abbreviations must be in use prior to
1532 this commit and unlikely to be confused with current key words.
1535 By a popular demand, a lot of NOFOO options were renamed
1536 to NO_FOO (see bsd.compat.mk for a full list). The old
1537 spellings are still supported, but will cause annoying
1538 warnings on stderr. Make sure you upgrade properly (see
1539 the COMMON ITEMS: section later in this file).
1542 Auto-loading of ancillary wlan modules such as wlan_wep has
1543 been temporarily disabled; you need to statically configure
1544 the modules you need into your kernel or explicitly load them
1545 prior to use. Specifically, if you intend to use WEP encryption
1546 with an 802.11 device load/configure wlan_wep; if you want to
1547 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
1548 and wlan_xauth as required.
1551 The behaviour of ppp(8) has changed slightly. If lqr is enabled
1552 (``enable lqr''), older versions would revert to LCP ECHO mode on
1553 negotiation failure. Now, ``enable echo'' is required for this
1554 behaviour. The ppp version number has been bumped to 3.4.2 to
1558 The wlan support has been updated to split the crypto support
1559 into separate modules. For static WEP you must configure the
1560 wlan_wep module in your system or build and install the module
1561 in place where it can be loaded (the kernel will auto-load
1562 the module when a wep key is configured).
1565 The ath driver has been updated to split the tx rate control
1566 algorithm into a separate module. You need to include either
1567 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
1570 Support for systems with an 80386 CPU has been removed. Please
1571 use FreeBSD 5.x or earlier on systems with an 80386.
1574 We have had a hack which would mount the root filesystem
1575 R/W if the device were named 'md*'. As part of the vnode
1576 work I'm doing I have had to remove this hack. People
1577 building systems which use preloaded MD root filesystems
1578 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
1579 their /etc/rc scripts.
1582 FreeBSD 5.3 shipped here.
1585 The size of struct tcpcb has changed again due to the removal
1586 of RFC1644 T/TCP. You have to recompile userland programs that
1587 read kmem for tcp sockets directly (netstat, sockstat, etc.)
1590 The size of struct tcpcb has changed. You have to recompile
1591 userland programs that read kmem for tcp sockets directly
1592 (netstat, sockstat, etc.)
1595 RELENG_5 branched here. For older entries, please see updating
1596 in the RELENG_5 branch.
1602 Avoid using make -j when upgrading. From time to time in the
1603 past there have been problems using -j with buildworld and/or
1604 installworld. This is especially true when upgrading between
1605 "distant" versions (eg one that cross a major release boundary
1606 or several minor releases, or when several months have passed
1607 on the -current branch).
1609 Sometimes, obscure build problems are the result of environment
1610 poisoning. This can happen because the make utility reads its
1611 environment when searching for values for global variables.
1612 To run your build attempts in an "environmental clean room",
1613 prefix all make commands with 'env -i '. See the env(1) manual
1614 page for more details.
1616 When upgrading from one major version to another it is generally
1617 best to upgrade to the latest code in the currently installed branch
1618 first, then do an upgrade to the new branch. This is the best-tested
1619 upgrade path, and has the highest probability of being successful.
1620 Please try this approach before reporting problems with a major
1625 When upgrading the boot ZFS pool to a new version, always follow
1628 1.) recompile and reinstall the ZFS boot loader and boot block
1629 (this is part of "make buildworld" and "make installworld")
1631 2.) update the ZFS boot block on your boot drive
1633 The following example updates the ZFS boot block on the first
1634 partition (freebsd-boot) of a GPT partitioned drive ad0:
1635 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1637 Non-boot pools do not need these updates.
1641 If you are updating from a prior version of FreeBSD (even one just
1642 a few days old), you should follow this procedure. It is the most
1643 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1645 make kernel-toolchain
1646 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1647 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1649 To test a kernel once
1650 ---------------------
1651 If you just want to boot a kernel once (because you are not sure
1652 if it works, or if you want to boot a known bad kernel to provide
1653 debugging information) run
1654 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1655 nextboot -k testkernel
1657 To just build a kernel when you know that it won't mess you up
1658 --------------------------------------------------------------
1659 This assumes you are already running a 5.X system. Replace
1660 ${arch} with the architecture of your machine (e.g. "i386",
1661 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1663 cd src/sys/${arch}/conf
1664 config KERNEL_NAME_HERE
1665 cd ../compile/KERNEL_NAME_HERE
1670 If this fails, go to the "To build a kernel" section.
1672 To rebuild everything and install it on the current system.
1673 -----------------------------------------------------------
1674 # Note: sometimes if you are running current you gotta do more than
1675 # is listed here if you are upgrading from a really old current.
1677 <make sure you have good level 0 dumps>
1679 make kernel KERNCONF=YOUR_KERNEL_HERE
1681 <reboot in single user> [3]
1689 To cross-install current onto a separate partition
1690 --------------------------------------------------
1691 # In this approach we use a separate partition to hold
1692 # current's root, 'usr', and 'var' directories. A partition
1693 # holding "/", "/usr" and "/var" should be about 2GB in
1696 <make sure you have good level 0 dumps>
1699 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1700 <maybe newfs current's root partition>
1701 <mount current's root partition on directory ${CURRENT_ROOT}>
1702 make installworld DESTDIR=${CURRENT_ROOT}
1703 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1704 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1705 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1706 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1707 <reboot into current>
1708 <do a "native" rebuild/install as described in the previous section>
1709 <maybe install compatibility libraries from ports/misc/compat*>
1713 To upgrade in-place from 5.x-stable to current
1714 ----------------------------------------------
1715 <make sure you have good level 0 dumps>
1717 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1719 <reboot in single user> [3]
1726 Make sure that you've read the UPDATING file to understand the
1727 tweaks to various things you need. At this point in the life
1728 cycle of current, things change often and you are on your own
1729 to cope. The defaults can also change, so please read ALL of
1730 the UPDATING entries.
1732 Also, if you are tracking -current, you must be subscribed to
1733 freebsd-current@freebsd.org. Make sure that before you update
1734 your sources that you have read and understood all the recent
1735 messages there. If in doubt, please track -stable which has
1736 much fewer pitfalls.
1738 [1] If you have third party modules, such as vmware, you
1739 should disable them at this point so they don't crash your
1742 [3] From the bootblocks, boot -s, and then do
1747 adjkerntz -i # if CMOS is wall time
1748 Also, when doing a major release upgrade, it is required that
1749 you boot into single user mode to do the installworld.
1751 [4] Note: This step is non-optional. Failure to do this step
1752 can result in a significant reduction in the functionality of the
1753 system. Attempting to do it by hand is not recommended and those
1754 that pursue this avenue should read this file carefully, as well
1755 as the archives of freebsd-current and freebsd-hackers mailing lists
1756 for potential gotchas.
1758 [5] Usually this step is a noop. However, from time to time
1759 you may need to do this if you get unknown user in the following
1760 step. It never hurts to do it all the time. You may need to
1761 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1762 install) after the buildworld before this step if you last updated
1763 from current before 20020224 or from -stable before 20020408.
1765 [6] This only deletes old files and directories. Old libraries
1766 can be deleted by "make delete-old-libs", but you have to make
1767 sure that no program is using those libraries anymore.
1769 [8] In order to have a kernel that can run the 4.x binaries
1770 needed to do an installworld, you must include the COMPAT_FREEBSD4
1771 option in your kernel. Failure to do so may leave you with a system
1772 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
1773 is required to run the 5.x binaries on more recent kernels.
1775 Make sure that you merge any new devices from GENERIC since the
1776 last time you updated your kernel config file.
1778 [9] When checking out sources, you must include the -P flag to have
1779 cvs prune empty directories.
1781 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1782 "?=" instead of the "=" assignment operator, so that buildworld can
1783 override the CPUTYPE if it needs to.
1785 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1786 not on the command line, or in /etc/make.conf. buildworld will
1787 warn if it is improperly defined.
1790 This file contains a list, in reverse chronological order, of major
1791 breakages in tracking -current. It is not guaranteed to be a complete
1792 list of such breakages, and only contains entries since October 16, 2004.
1793 If you need to see UPDATING entries from before that date, you will need
1794 to fetch an UPDATING file from an older FreeBSD release.
1796 Copyright information:
1798 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
1800 Redistribution, publication, translation and use, with or without
1801 modification, in full or in part, in any form or format of this
1802 document are permitted without further permission from the author.
1804 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1805 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1806 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1807 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1808 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1809 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1810 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1811 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1812 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1813 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1814 POSSIBILITY OF SUCH DAMAGE.
1816 If you find this document useful, and you want to, you may buy the
1819 Contact Warner Losh if you have any questions about your use of