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 rc.firewall and rc.firewall6 were unified, and
20 rc.firewall6 and rc.d/ip6fw were removed.
21 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
22 variables are obsoleted. Instead, the following new rc
23 variables are added to rc.d/ipfw:
25 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
26 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
27 firewall_simple_onet_ipv6
29 The meanings correspond to the relevant IPv4 variables.
32 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
33 to allow 32-bit compatibility on non-x86 platforms. All kernel
34 configurations on amd64 and ia64 platforms using these options must
35 be modified accordingly.
38 Introduce the kernel thread "deadlock resolver" (which can be enabled
39 via the DEADLKRES option, see NOTES for more details) and the
40 sleepq_type() function for sleepqueues.
43 802.11s D3.03 support was committed. This is incompatible with
44 the previous code, which was based on D3.0.
47 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
48 mount(8) and -a option for df(1) to see them.
51 Remove the option STOP_NMI. The default action is now to use NMI
52 only for KDB via the newly introduced function stop_cpus_hard()
53 and maintain stop_cpus() to just use a normal IPI_STOP on ia32
60 Bump the shared library version numbers for all libraries that
61 do not use symbol versioning as part of the 8.0-RELEASE cycle.
62 Bump __FreeBSD_version to 800105.
65 Due to changes in the implementation of virtual network stack
66 support, all network-related kernel modules must be recompiled.
67 As this change breaks the ABI, bump __FreeBSD_version to 800104.
70 The TOE interface to the TCP syncache has been modified to remove struct
71 tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack. The
72 cxgb driver is the only TOE consumer affected by this change, and needs
73 to be recompiled along with the kernel. As this change breaks the ABI,
74 bump __FreeBSD_version to 800103.
77 Padding has been added to struct tcpcb, sackhint and tcpstat in
78 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
79 maintainig the ABI. However, this change breaks the ABI, so bump
80 __FreeBSD_version to 800102. User space tools that rely on the size of
81 any of these structs (e.g. sockstat) need to be recompiled.
84 The NFS_LEGACYRPC option has been removed along with the old
85 kernel RPC implementation that this option selected. Kernel
86 configurations may need to be adjusted.
89 The network interface device nodes at /dev/net/<interface> have
90 been removed. All ioctl operations can be performed the normal
91 way using routing sockets. The kqueue functionality can
92 generally be replaced with routing sockets.
95 The documentation from the FreeBSD Documentation Project
96 (Handbook, FAQ, etc.) is now installed via packages by
97 sysinstall(8) and under the /usr/local/share/doc/freebsd
98 directory instead of /usr/share/doc.
101 The ABI of various structures related to the SYSV IPC API have
102 been changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43
103 kernel options now all require COMPAT_FREEBSD7.
104 Bump __FreeBSD_version to 800100.
107 Layout of struct vnet has changed as routing related variables
108 were moved to their own Vimage module. Modules need to be
109 recompiled. Bump __FreeBSD_version to 800099.
112 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023
113 and 1024 respectively. As long as no more than 16 groups per
114 process are used, no changes should be visible. When more
115 than 16 groups are used, old binaries may fail if they call
116 getgroups() or getgrouplist() with statically sized storage.
117 Recompiling will work around this, but applications should be
118 modified to use dynamically allocated storage for group arrays
119 as POSIX.1-2008 does not cap an implementation's number of
120 supported groups at NGROUPS_MAX+1 as previous versions did.
122 NFS and portalfs mounts may also be affected as the list of
123 groups is truncated to 16. Users of NFS who use more than 16
124 groups, should take care that negative group permissions are not
125 used on the exported file systems as they will not be reliable
126 unless a GSSAPI based authentication method is used.
129 The compiling option ADAPTIVE_LOCKMGRS has been introduced.
130 This option compiles in the support for adaptive spinning for lockmgrs
131 which want to enable it. The lockinit() function now accepts the
132 flag LK_ADAPTIVE in order to make the lock object subject to
133 adaptive spinning when both held in write and read mode.
136 The layout of the structure returned by IEEE80211_IOC_STA_INFO
137 has changed. User applications that use this ioctl need to be
141 The layout of struct thread has changed. Kernel and modules
145 The layout of structs ifnet, domain, protosw and vnet_net has
146 changed. Kernel modules need to be rebuilt.
147 Bump __FreeBSD_version to 800097.
150 window(1) has been removed from the base system. It can now be
151 installed from ports. The port is called misc/window.
154 The way we are storing and accessing `routing table' entries
155 has changed. Programs reading the FIB, like netstat, need to
159 A new netisr implementation has been added for FreeBSD 8. Network
160 file system modules, such as igmp, ipdivert, and others, should be
162 Bump __FreeBSD_version to 800096.
165 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose
169 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
170 Bump __FreeBSD_version to 800094.
173 Add mnt_xflag field to 'struct mount'. File system modules
175 Bump __FreeBSD_version to 800093.
178 The compiling option ADAPTIVE_SX has been retired while it has been
179 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
180 The KPI for sx_init_flags() changes as accepting flags:
181 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag
182 has been introduced in order to handle the reversed logic.
183 Bump __FreeBSD_version to 800092.
186 Add support for hierarchical jails. Remove global securelevel.
187 Bump __FreeBSD_version to 800091.
190 The layout of struct vnet_net has changed, therefore modules
192 Bump __FreeBSD_version to 800090.
195 The newly imported zic(8) produces a new format in the
196 output. Please run tzsetup(8) to install the newly created
197 data to /etc/localtime.
200 The sysctl tree for the usb stack has renamed from hw.usb2.* to
201 hw.usb.* and is now consistent again with previous releases.
204 802.11 monitor mode support was revised and driver api's
205 were changed. Drivers dependent on net80211 now support
206 DLT_IEEE802_11_RADIO instead of DLT_IEEE802_11. No
207 user-visible data structures were changed but applications
208 that use DLT_IEEE802_11 may require changes.
209 Bump __FreeBSD_version to 800088.
212 The layout of the following structs has changed: sysctl_oid,
213 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
214 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
215 panics may be experienced. World rebuild is required for
216 correctly checking networking state from userland.
217 Bump __FreeBSD_version to 800085.
220 MLDv2 and Source-Specific Multicast (SSM) have been merged
221 to the IPv6 stack. VIMAGE hooks are in but not yet used.
222 The implementation of SSM within FreeBSD's IPv6 stack closely
223 follows the IPv4 implementation.
225 For kernel developers:
227 * The most important changes are that the ip6_output() and
228 ip6_input() paths no longer take the IN6_MULTI_LOCK,
229 and this lock has been downgraded to a non-recursive mutex.
231 * As with the changes to the IPv4 stack to support SSM, filtering
232 of inbound multicast traffic must now be performed by transport
233 protocols within the IPv6 stack. This does not apply to TCP and
234 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
236 * The KPIs used by IPv6 multicast are similar to those used by
237 the IPv4 stack, with the following differences:
238 * im6o_mc_filter() is analogous to imo_multicast_filter().
239 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
240 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
241 * IN6_LOOKUP_MULTI() has been deprecated and removed.
242 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
243 for MLDv1 have an additional 'timer' argument which is used to
244 jitter the initial membership report for the solicited-node
245 multicast membership on-link.
246 * This is not strictly needed for MLDv2, which already jitters
247 its report transmissions. However, the 'timer' argument is
248 preserved in case MLDv1 is active on the interface.
250 * The KAME linked-list based IPv6 membership implementation has
251 been refactored to use a vector similar to that used by the IPv4
253 Code which maintains a list of its own multicast memberships
254 internally, e.g. carp, has been updated to reflect the new
257 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
258 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
259 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
260 implementation constraint which needs to be addressed in HEAD.
262 For application developers:
264 * The changes are broadly similar to those made for the IPv4
267 * The use of IPv4 and IPv6 multicast socket options on the same
268 socket, using mapped addresses, HAS NOT been tested or supported.
270 * There are a number of issues with the implementation of various
271 IPv6 multicast APIs which need to be resolved in the API surface
272 before the implementation is fully compatible with KAME userland
273 use, and these are mostly to do with interface index treatment.
275 * The literature available discusses the use of either the delta / ASM
276 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
277 using setsourcefilter(3)/getsourcefilter(3). For more information
278 please refer to RFC 3768, 'Socket Interface Extensions for
279 Multicast Source Filters'.
281 * Applications which use the published RFC 3678 APIs should be fine.
283 For systems administrators:
285 * The mtest(8) utility has been refactored to support IPv6, in
286 addition to IPv4. Interface addresses are no longer accepted
287 as arguments, their names must be used instead. The utility
288 will map the interface name to its first IPv4 address as
289 returned by getifaddrs(3).
291 * The ifmcstat(8) utility has also been updated to print the MLDv2
292 endpoint state and source filter lists via sysctl(3).
294 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
295 loopback of IPv6 multicast datagrams by default; it defaults to 1
296 to preserve the existing behaviour. Disabling multicast loopback is
297 recommended for optimal system performance.
299 * The IPv6 MROUTING code has been changed to examine this sysctl
300 instead of attempting to perform a group lookup before looping
301 back forwarded datagrams.
303 Bump __FreeBSD_version to 800084.
306 Implement low-level Bluetooth HCI API.
307 Bump __FreeBSD_version to 800083.
310 The layout of struct malloc_type, used by modules to register new
311 memory allocation types, has changed. Most modules will need to
312 be rebuilt or panics may be experienced.
313 Bump __FreeBSD_version to 800081.
316 Anticipate overflowing inp_flags - add inp_flags2.
317 This changes most offsets in inpcb, so checking v4 connection
318 state will require a world rebuild.
319 Bump __FreeBSD_version to 800080.
322 Add an llentry to struct route and struct route_in6. Modules
323 embedding a struct route will need to be recompiled.
324 Bump __FreeBSD_version to 800079.
327 The size of rt_metrics_lite and by extension rtentry has changed.
328 Networking administration apps will need to be recompiled.
329 The route command now supports show as an alias for get, weighting
330 of routes, sticky and nostick flags to alter the behavior of stateful
332 Bump __FreeBSD_version to 800078.
335 Do not use Giant for kbdmux(4) locking. This is wrong and
336 apparently causing more problems than it solves. This will
337 re-open the issue where interrupt handlers may race with
338 kbdmux(4) in polling mode. Typical symptoms include (but
339 not limited to) duplicated and/or missing characters when
340 low level console functions (such as gets) are used while
341 interrupts are enabled (for example geli password prompt,
342 mountroot prompt etc.). Disabling kbdmux(4) may help.
345 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
346 kernel modules referencing any of the above need to be recompiled.
347 Bump __FreeBSD_version to 800075.
350 GEOM_PART has become the default partition slicer for storage devices,
351 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
352 introduces some changes:
354 MSDOS/EBR: the devices created from MSDOS extended partition entries
355 (EBR) can be named differently than with GEOM_MBR and are now symlinks
356 to devices with offset-based names. fstabs may need to be modified.
358 BSD: the "geometry does not match label" warning is harmless in most
359 cases but it points to problems in file system misalignment with
360 disk geometry. The "c" partition is now implicit, covers the whole
361 top-level drive and cannot be (mis)used by users.
363 General: Kernel dumps are now not allowed to be written to devices
364 whose partition types indicate they are meant to be used for file
365 systems (or, in case of MSDOS partitions, as something else than
368 Most of these changes date approximately from 200812.
371 The uscanner(4) driver has been removed from the kernel. This follows
372 Linux removing theirs in 2.6 and making libusb the default interface
376 The multicast forwarding code has been cleaned up. netstat(1)
377 only relies on KVM now for printing bandwidth upcall meters.
378 The IPv4 and IPv6 modules are split into ip_mroute_mod and
379 ip6_mroute_mod respectively. The config(5) options for statically
380 compiling this code remain the same, i.e. 'options MROUTING'.
383 Support for the IFF_NEEDSGIANT network interface flag has been
384 removed, which means that non-MPSAFE network device drivers are no
385 longer supported. In particular, if_ar, if_sr, and network device
386 drivers from the old (legacy) USB stack can no longer be built or
390 POSIX.1 Native Language Support (NLS) has been enabled in libc and
391 a bunch of new language catalog files have also been added.
392 This means that some common libc messages are now localized and
393 they depend on the LC_MESSAGES environmental variable.
396 The k8temp(4) driver has been renamed to amdtemp(4) since
397 support for K10 and K11 CPU families was added.
400 IGMPv3 and Source-Specific Multicast (SSM) have been merged
401 to the IPv4 stack. VIMAGE hooks are in but not yet used.
403 For kernel developers, the most important changes are that the
404 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
405 and this lock has been downgraded to a non-recursive mutex.
407 Transport protocols (UDP, Raw IP) are now responsible for filtering
408 inbound multicast traffic according to group membership and source
409 filters. The imo_multicast_filter() KPI exists for this purpose.
410 Transports which do not use multicast (SCTP, TCP) already reject
411 multicast by default. Forwarding and receive performance may improve
412 as a mutex acquisition is no longer needed in the ip_input()
413 low-level input path. in_addmulti() and in_delmulti() are shimmed
414 to new KPIs which exist to support SSM in-kernel.
416 For application developers, it is recommended that loopback of
417 multicast datagrams be disabled for best performance, as this
418 will still cause the lock to be taken for each looped-back
419 datagram transmission. The net.inet.ip.mcast.loop sysctl may
420 be tuned to 0 to disable loopback by default; it defaults to 1
421 to preserve the existing behaviour.
423 For systems administrators, to obtain best performance with
424 multicast reception and multiple groups, it is always recommended
425 that a card with a suitably precise hash filter is used. Hash
426 collisions will still result in the lock being taken within the
427 transport protocol input path to check group membership.
429 If deploying FreeBSD in an environment with IGMP snooping switches,
430 it is recommended that the net.inet.igmp.sendlocal sysctl remain
431 enabled; this forces 224.0.0.0/24 group membership to be announced
434 The size of 'struct igmpstat' has changed; netstat needs to be
435 recompiled to reflect this.
436 Bump __FreeBSD_version to 800070.
439 libusb20.so.1 is now installed as libusb.so.1 and the ports system
440 updated to use it. This requires a buildworld/installworld in order to
441 update the library and dependencies (usbconfig, etc). Its advisable to
442 rebuild all ports which uses libusb. More specific directions are given
443 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
444 libusb are no longer required and can be removed.
447 A workaround is committed to allow the creation of System V shared
448 memory segment of size > 2 GB on the 64-bit architectures.
449 Due to a limitation of the existing ABI, the shm_segsz member
450 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
451 wrong for large segments. Note that limits must be explicitly
452 raised to allow such segments to be created.
455 The layout of struct ifnet has changed, requiring a rebuild of all
456 network device driver modules.
459 The /dev handling for the new USB stack has changed, a
460 buildworld/installworld is required for libusb20.
463 The new USB2 stack has now been permanently moved in and all kernel and
464 module names reverted to their previous values (eg, usb, ehci, ohci,
465 ums, ...). The old usb stack can be compiled in by prefixing the name
466 with the letter 'o', the old usb modules have been removed.
467 Updating entry 20090216 for xorg and 20090215 for libmap may still
471 The rc.conf(5) option if_up_delay has been renamed to
472 defaultroute_delay to better reflect its purpose. If you have
473 customized this setting in /etc/rc.conf you need to update it to
477 xorg 7.4 wants to configure its input devices via hald which does not
478 yet work with USB2. If the keyboard/mouse does not work in xorg then
480 Option "AllowEmptyInput" "off"
481 to your ServerLayout section. This will cause X to use the configured
482 kbd and mouse sections from your xorg.conf.
485 The GENERIC kernels for all architectures now default to the new USB2
486 stack. No kernel config options or code have been removed so if a
487 problem arises please report it and optionally revert to the old USB
488 stack. If you are loading USB kernel modules or have a custom kernel
489 that includes GENERIC then ensure that usb names are also changed over,
490 eg uftdi -> usb2_serial_ftdi.
492 Older programs linked against the ports libusb 0.1 need to be
493 redirected to the new stack's libusb20. /etc/libmap.conf can
495 # Map old usb library to new one for usb2 stack
496 libusb-0.1.so.8 libusb20.so.1
499 All USB ethernet devices now attach as interfaces under the name ueN
500 (eg. ue0). This is to provide a predictable name as vendors often
501 change usb chipsets in a product without notice.
504 The ichsmb(4) driver has been changed to require SMBus slave
505 addresses be left-justified (xxxxxxx0b) rather than right-justified.
506 All of the other SMBus controller drivers require left-justified
507 slave addresses, so this change makes all the drivers provide the
511 INET6 statistics (struct ip6stat) was updated.
512 netstat(1) needs to be recompiled.
515 NTFS has been removed from GENERIC kernel on amd64 to match
516 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
517 will load ntfs.ko module automatically when NTFS support is
518 actually needed, unless ntfs.ko is not installed or security
519 level prohibits loading kernel modules. If either is the case,
520 "options NTFS" has to be added into kernel config.
523 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
524 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
525 800061. User space tools that rely on the size of struct tcpcb in
526 tcp_var.h (e.g. sockstat) need to be recompiled.
529 ng_tty(4) module updated to match the new TTY subsystem.
530 Due to API change, user-level applications must be updated.
531 New API support added to mpd5 CVS and expected to be present
532 in next mpd5.3 release.
535 With __FreeBSD_version 800060 the makefs tool is part of
536 the base system (it was a port).
539 The afdata and ifnet locks have been changed from mutexes to
540 rwlocks, network modules will need to be re-compiled.
543 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
544 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
545 The new code reduced struct rtentry{} by 16 bytes on 32-bit
546 architecture and 40 bytes on 64-bit architecture. The userland
547 applications "arp" and "ndp" have been updated accordingly.
548 The output from "netstat -r" shows only routing entries and
549 none of the L2 information.
552 __FreeBSD_version 800057 marks the switchover from the
553 binary ath hal to source code. Users must add the line:
555 options AH_SUPPORT_AR5416
557 to their kernel config files when specifying:
561 The ath_hal module no longer exists; the code is now compiled
562 together with the driver in the ath module. It is now
563 possible to tailor chip support (i.e. reduce the set of chips
564 and thereby the code size); consult ath_hal(4) for details.
567 __FreeBSD_version 800054 adds memory barriers to
568 <machine/atomic.h>, new interfaces to ifnet to facilitate
569 multiple hardware transmit queues for cards that support
570 them, and a lock-less ring-buffer implementation to
571 enable drivers to more efficiently manage queueing of
575 A new version of ZFS (version 13) has been merged to -HEAD.
576 This version has zpool attribute "listsnapshots" off by
577 default, which means "zfs list" does not show snapshots,
578 and is the same as Solaris behavior.
581 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
584 The uhci, ohci, ehci and slhci USB Host controller drivers have
585 been put into separate modules. If you load the usb module
586 separately through loader.conf you will need to load the
587 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
588 controller add the following to loader.conf:
594 The ABI used by the PMC toolset has changed. Please keep
595 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
599 atapci kernel module now includes only generic PCI ATA
600 driver. AHCI driver moved to ataahci kernel module.
601 All vendor-specific code moved into separate kernel modules:
602 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
603 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
604 atamarvell, atamicron, atanational, atanetcell, atanvidia,
605 atapromise, ataserverworks, atasiliconimage, atasis, atavia
608 The TTY subsystem of the kernel has been replaced by a new
609 implementation, which provides better scalability and an
610 improved driver model. Most common drivers have been migrated to
611 the new TTY subsystem, while others have not. The following
612 drivers have not yet been ported to the new TTY layer:
615 cy, digi, rc, rp, sio
621 ng_h4, ng_tty, ppp, sl, snp
623 Adding these drivers to your kernel configuration file shall
624 cause compilation to fail.
627 ntpd has been upgraded to 4.2.4p5.
630 OpenSSH has been upgraded to 5.1p1.
632 For many years, FreeBSD's version of OpenSSH preferred DSA
633 over RSA for host and user authentication keys. With this
634 upgrade, we've switched to the vendor's default of RSA over
635 DSA. This may cause upgraded clients to warn about unknown
636 host keys even for previously known hosts. Users should
637 follow the usual procedure for verifying host keys before
638 accepting the RSA key.
640 This can be circumvented by setting the "HostKeyAlgorithms"
641 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
644 Please note that the sequence of keys offered for
645 authentication has been changed as well. You may want to
646 specify IdentityFile in a different order to revert this
650 The sio(4) driver has been removed from the i386 and amd64
651 kernel configuration files. This means uart(4) is now the
652 default serial port driver on those platforms as well.
654 To prevent collisions with the sio(4) driver, the uart(4) driver
655 uses different names for its device nodes. This means the
656 onboard serial port will now most likely be called "ttyu0"
657 instead of "ttyd0". You may need to reconfigure applications to
658 use the new device names.
660 When using the serial port as a boot console, be sure to update
661 /boot/device.hints and /etc/ttys before booting the new kernel.
662 If you forget to do so, you can still manually specify the hints
663 at the loader prompt:
665 set hint.uart.0.at="isa"
666 set hint.uart.0.port="0x3F8"
667 set hint.uart.0.flags="0x10"
668 set hint.uart.0.irq="4"
672 The gpt(8) utility has been removed. Use gpart(8) to partition
676 The version that Linuxulator emulates was changed from 2.4.2
677 to 2.6.16. If you experience any problems with Linux binaries
678 please try to set sysctl compat.linux.osrelease to 2.4.2 and
679 if it fixes the problem contact emulation mailing list.
682 ISDN4BSD (I4B) was removed from the src tree. You may need to
683 update a your kernel configuration and remove relevant entries.
686 I have checked in code to support multiple routing tables.
687 See the man pages setfib(1) and setfib(2).
688 This is a hopefully backwards compatible version,
689 but to make use of it you need to compile your kernel
690 with options ROUTETABLES=2 (or more up to 16).
693 The 802.11 wireless support was redone to enable multi-bss
694 operation on devices that are capable. The underlying device
695 is no longer used directly but instead wlanX devices are
696 cloned with ifconfig. This requires changes to rc.conf files.
698 ifconfig_ath0="WPA DHCP"
701 ifconfig_wlan0="WPA DHCP"
702 see rc.conf(5) for more details. In addition, mergemaster of
703 /etc/rc.d is highly recommended. Simultaneous update of userland
704 and kernel wouldn't hurt either.
706 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
707 modules were merged into the base wlan module. All references
708 to these modules (e.g. in kernel config files) must be removed.
711 psm(4) has gained write(2) support in native operation level.
712 Arbitrary commands can be written to /dev/psm%d and status can
713 be read back from it. Therefore, an application is responsible
714 for status validation and error recovery. It is a no-op in
715 other operation levels.
718 Support for KSE threading has been removed from the kernel. To
719 run legacy applications linked against KSE libmap.conf may
720 be used. The following libmap.conf may be used to ensure
721 compatibility with any prior release:
723 libpthread.so.1 libthr.so.1
724 libpthread.so.2 libthr.so.2
725 libkse.so.3 libthr.so.3
728 The layout of struct vmspace has changed. This affects libkvm
729 and any executables that link against libkvm and use the
730 kvm_getprocs() function. In particular, but not exclusively,
731 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
732 The effects are minimal, but it's advisable to upgrade world
736 The latest em driver no longer has support in it for the
737 82575 adapter, this is now moved to the igb driver. The
738 split was done to make new features that are incompatible
739 with older hardware easier to do.
742 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
743 likewise the kernel option is now GEOM_LINUX_LVM.
746 The default NFS mount mode has changed from UDP to TCP for
747 increased reliability. If you rely on (insecurely) NFS
748 mounting across a firewall you may need to update your
752 Belatedly note the addition of m_collapse for compacting
756 The fts(3) structures have been changed to use adequate
757 integer types for their members and so to be able to cope
758 with huge file trees. The old fts(3) ABI is preserved
759 through symbol versioning in libc, so third-party binaries
760 using fts(3) should still work, although they will not take
761 advantage of the extended types. At the same time, some
762 third-party software might fail to build after this change
763 due to unportable assumptions made in its source code about
764 fts(3) structure members. Such software should be fixed
765 by its vendor or, in the worst case, in the ports tree.
766 FreeBSD_version 800015 marks this change for the unlikely
767 case that a portable fix is impossible.
770 To upgrade to -current after this date, you must be running
771 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
772 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
775 The ADAPTIVE_GIANT kernel option has been retired because its
776 functionality is the default now.
779 The AT keyboard emulation of sunkbd(4) has been turned on
780 by default. In order to make the special symbols of the Sun
781 keyboards driven by sunkbd(4) work under X these now have
782 to be configured the same way as Sun USB keyboards driven
783 by ukbd(4) (which also does AT keyboard emulation), f.e.:
785 Option "XkbLayout" "us"
786 Option "XkbRules" "xorg"
787 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
790 It has been decided that it is desirable to provide ABI
791 backwards compatibility to the FreeBSD 4/5/6 versions of the
792 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
793 broken with the introduction of PCI domain support (see the
794 20070930 entry). Unfortunately, this required the ABI of
795 PCIOCGETCONF to be broken again in order to be able to
796 provide backwards compatibility to the old version of that
797 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
798 again. As for prominent ports this affects neither pciutils
799 nor xorg-server this time, the hal port needs to be rebuilt
803 The misnamed kthread_create() and friends have been renamed
804 to kproc_create() etc. Many of the callers already
806 I will return kthread_create() and friends in a while
807 with implementations that actually create threads, not procs.
808 Renaming corresponds with version 800002.
814 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
815 WITHOUT_LIBTHR are set.
818 The PCI code has been made aware of PCI domains. This means that
819 the location strings as used by pciconf(8) etc are now in the
820 following format: pci<domain>:<bus>:<device>[:<function>]. It
821 also means that consumers of <sys/pciio.h> potentially need to
822 be recompiled; this includes the hal and xorg-server ports.
825 The caching daemon (cached) was renamed to nscd. nscd.conf
826 configuration file should be used instead of cached.conf and
827 nscd_enable, nscd_pidfile and nscd_flags options should be used
828 instead of cached_enable, cached_pidfile and cached_flags in
832 The getfacl(1) utility now prints owning user and group name
833 instead of owning uid and gid in the three line comment header.
834 This is the same behavior as getfacl(1) on Solaris and Linux.
837 The new IPsec code is now compiled in using the IPSEC option. The
838 IPSEC option now requires "device crypto" be defined in your kernel
839 configuration. The FAST_IPSEC kernel option is now deprecated.
842 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
843 note the changed syntax - keep state is now on by default. Also
844 note the fact that ftp-proxy(8) has been changed from bottom up and
845 has been moved from libexec to usr/sbin. Changes in the ALTQ
846 handling also affect users of IPFW's ALTQ capabilities.
849 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
850 only IPsec supported by FreeBSD. The new IPsec stack
851 supports both IPv4 and IPv6. The kernel option will change
852 after the code changes have settled in. For now the kernel
853 option IPSEC is deprecated and FAST_IPSEC is the only option, that
854 will change after some settling time.
857 The wicontrol(8) utility has been removed from the base system. wi(4)
858 cards should be configured using ifconfig(8), see the man page for more
862 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
863 instead of the nve(4) driver. Please update your configuration
867 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
868 database if it is missing or older than the aliases file. If
869 desired, set the new rc.conf option sendmail_rebuild_aliases
870 to "YES" to restore that functionality.
873 The IPv4 multicast socket code has been considerably modified, and
874 moved to the file sys/netinet/in_mcast.c. Initial support for the
875 RFC 3678 Source-Specific Multicast Socket API has been added to
876 the IPv4 network stack.
878 Strict multicast and broadcast reception is now the default for
879 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
880 has now been removed.
882 The RFC 1724 hack for interface selection has been removed; the use
883 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
884 been added to replace it. Consumers such as routed will soon be
885 updated to reflect this.
887 These changes affect users who are running routed(8) or rdisc(8)
888 from the FreeBSD base system on point-to-point or unnumbered
892 The net80211 layer has changed significantly and all wireless
893 drivers that depend on it need to be recompiled. Further these
894 changes require that any program that interacts with the wireless
895 support in the kernel be recompiled; this includes: ifconfig,
896 wpa_supplicant, hostapd, and wlanstats. Users must also, for
897 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
898 if they use modules for wireless support. These modules implement
899 scanning support for station and ap modes, respectively. Failure
900 to load the appropriate module before marking a wireless interface
901 up will result in a message to the console and the device not
905 The pam_nologin(8) module ceases to provide an authentication
906 function and starts providing an account management function.
907 Consequent changes to /etc/pam.d should be brought in using
908 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
909 need manual editing as follows. Locate this line (or similar):
911 auth required pam_nologin.so no_warn
913 and change it according to this example:
915 account required pam_nologin.so no_warn
917 That is, the first word needs to be changed from "auth" to
918 "account". The new line can be moved to the account section
919 within the file for clarity. Not updating pam.conf(5) files
920 will result in nologin(5) ignored by the respective services.
923 The ether_ioctl() function has been synchronized with ioctl(2)
924 and ifnet.if_ioctl. Due to that, the size of one of its arguments
925 has changed on 64-bit architectures. All kernel modules using
926 ether_ioctl() need to be rebuilt on such architectures.
929 Improved INCLUDE_CONFIG_FILE support has been introduced to the
930 config(8) utility. In order to take advantage of this new
931 functionality, you are expected to recompile and install
932 src/usr.sbin/config. If you don't rebuild config(8), and your
933 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
934 build will be broken because of a missing "kernconfstring"
938 Symbol versioning is enabled by default. To disable it, use
939 option WITHOUT_SYMVER. It is not advisable to attempt to
940 disable symbol versioning once it is enabled; your installworld
941 will break because a symbol version-less libc will get installed
942 before the install tools. As a result, the old install tools,
943 which previously had symbol dependencies to FBSD_1.0, will fail
944 because the freshly installed libc will not have them.
946 The default threading library (providing "libpthread") has been
947 changed to libthr. If you wish to have libkse as your default,
948 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
951 The ABI breakage in sendmail(8)'s libmilter has been repaired
952 so it is no longer necessary to recompile mail filters (aka,
953 milters). If you recompiled mail filters after the 20070408
954 note, it is not necessary to recompile them again.
957 The new trunk(4) driver has been renamed to lagg(4) as it better
958 reflects its purpose. ifconfig will need to be recompiled.
961 sendmail(8) has been updated to version 8.14.1. Mail filters
962 (aka, milters) compiled against the libmilter included in the
963 base operating system should be recompiled.
966 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
967 In order to use them one must agree to the respective LICENSE in
968 share/doc/legal and define legal.intel_<name>.license_ack=1 via
969 loader.conf(5) or kenv(1). Make sure to deinstall the now
970 deprecated modules from the respective firmware ports.
973 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
974 were removed from FreeBSD's libc. These originally came from INRIA
975 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
976 deprecated in previous releases.
977 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
978 replace it as a more portable (and re-entrant) API.
981 To support interrupt filtering a modification to the newbus API
982 has occurred, ABI was broken and __FreeBSD_version was bumped
983 to 700031. Please make sure that your kernel and modules are in
985 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
988 The IPv6 multicast forwarding code may now be loaded into GENERIC
989 kernels by loading the ip_mroute.ko module. This is built into the
990 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
991 set; see src.conf(5) for more information.
994 The output of netstat -r has changed. Without -n, we now only
995 print a "network name" without the prefix length if the network
996 address and mask exactly match a Class A/B/C network, and an entry
997 exists in the nsswitch "networks" map.
998 With -n, we print the full unabbreviated CIDR network prefix in
999 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
1000 This change is in preparation for changes such as equal-cost
1001 multipath, and to more generally assist operational deployment
1002 of FreeBSD as a modern IPv4 router.
1005 PIM has been turned on by default in the IPv4 multicast
1006 routing code. The kernel option 'PIM' has now been removed.
1007 PIM is now built by default if option 'MROUTING' is specified.
1008 It may now be loaded into GENERIC kernels by loading the
1009 ip_mroute.ko module.
1012 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
1013 has been removed. Its functionality may be achieved by explicitly
1014 configuring gif(4) interfaces and using the 'phyint' keyword in
1016 XORP does not support source-routed IPv4 multicast tunnels nor the
1017 integrated IPIP tunneling, therefore it is not affected by this
1018 change. The __FreeBSD_version macro has been bumped to 700030.
1021 Support for PCI Message Signalled Interrupts has been
1022 re-enabled in the bge driver, only for those chips which are
1023 believed to support it properly. If there are any problems,
1024 MSI can be disabled completely by setting the
1025 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
1029 Support for PCI Message Signalled Interrupts has been
1030 disabled again in the bge driver. Many revisions of the
1031 hardware fail to support it properly. Support can be
1032 re-enabled by removing the #define of BGE_DISABLE_MSI in
1033 "src/sys/dev/bge/if_bge.c".
1036 Support for PCI Message Signalled Interrupts has been added
1037 to the bge driver. If there are any problems, MSI can be
1038 disabled completely by setting the 'hw.pci.enable_msi' and
1039 'hw.pci.enable_msix' tunables to 0 in the loader.
1042 The removal of several facets of the experimental Threading
1043 system from the kernel means that the proc and thread structures
1044 have changed quite a bit. I suggest all kernel modules that might
1045 reference these structures be recompiled.. Especially the
1049 Sound infrastructure has been updated with various fixes and
1050 improvements. Most of the changes are pretty much transparent,
1051 with exceptions of followings:
1052 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
1053 moved to their own dev sysctl nodes, for example:
1054 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
1055 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
1056 own chardev in the form of "dsp%d.<function>%d", where <function>
1057 is p = playback, r = record and v = virtual, respectively. Users
1058 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
1059 This does not affect those who are using "/dev/dsp".
1062 geom(4)'s gmirror(8) class metadata structure has been
1063 rev'd from v3 to v4. If you update across this point and
1064 your metadata is converted for you, you will not be easily
1065 able to downgrade since the /boot/kernel.old/geom_mirror.ko
1066 kernel module will be unable to read the v4 metadata. You
1067 can resolve this by doing from the loader(8) prompt:
1069 set vfs.root.mountfrom="ufs:/dev/XXX"
1071 where XXX is the root slice of one of the disks that composed
1072 the mirror (i.e.: /dev/ad0s1a). You can then rebuild
1073 the array the same way you built it originally.
1076 The following binaries have been disconnected from the build:
1077 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
1078 and mount_std. The functionality of these programs has been
1079 moved into the mount program. For example, to mount a devfs
1080 filesystem, instead of using mount_devfs, use: "mount -t devfs".
1081 This does not affect entries in /etc/fstab, since entries in
1082 /etc/fstab are always processed with "mount -t fstype".
1085 Support for PCI Message Signalled Interrupts on i386 and amd64
1086 has been added to the kernel and various drivers will soon be
1087 updated to use MSI when it is available. If there are any problems,
1088 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
1089 and 'hw.pci.enable_msix' tunables to 0 in the loader.
1092 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
1093 The lockmgr object layout has been changed as a result of having
1094 a lock_object embedded in it. As a consequence all file system
1095 kernel modules must be re-compiled. The mutex profiling man page
1096 has not yet been updated to reflect this change.
1099 KSE in the kernel has now been made optional and turned on by
1100 default. Use 'nooption KSE' in your kernel config to turn it
1101 off. All kernel modules *must* be recompiled after this change.
1102 There-after, modules from a KSE kernel should be compatible with
1103 modules from a NOKSE kernel due to the temporary padding fields
1104 added to 'struct proc'.
1107 mrouted and its utilities have been removed from the base system.
1110 Some ioctl(2) command codes have changed. Full backward ABI
1111 compatibility is provided if the "options COMPAT_FREEBSD6" is
1112 present in the kernel configuration file. Make sure to add
1113 this option to your kernel config file, or recompile X.Org
1114 and the rest of ports; otherwise they may refuse to work.
1117 tcpslice has been removed from the base system.
1120 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
1121 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
1122 systat needs to be rebuilt.
1125 libpcap updated to v0.9.4 and tcpdump to v3.9.4
1128 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
1129 for IPFIREWALL_FORWARD is now as it was before when it was first
1130 committed and for years after. The behaviour is now ON.
1133 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
1134 Now it can decrypt files created from different architectures.
1135 Unfortunately, it is no longer able to decrypt a cipher text
1136 generated with an older version on 64 bit architectures.
1137 If you have such a file, you need old utility to decrypt it.
1140 The interface version of the i4b kernel part has changed. So
1141 after updating the kernel sources and compiling a new kernel,
1142 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
1143 be rebuilt, and vice versa.
1146 The XBOX kernel now defaults to the nfe(4) driver instead of
1147 the nve(4) driver. Please update your configuration
1151 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
1152 PCnet family of NICs has been removed. The new le(4) driver serves
1153 as an equivalent but cross-platform replacement with the pcn(4)
1154 driver still providing performance-optimized support for the subset
1155 of AMD Am79C971 PCnet-FAST and greater chips as before.
1158 The machdep.* sysctls and the adjkerntz utility have been
1159 modified a bit. The new adjkerntz utility uses the new
1160 sysctl names and sysctlbyname() calls, so it may be impossible
1161 to run an old /sbin/adjkerntz utility in single-user mode
1162 with a new kernel. Replace the `adjkerntz -i' step before
1163 `make installworld' with:
1165 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
1167 and proceed as usual with the rest of the installworld-stage
1168 steps. Otherwise, you risk installing binaries with their
1169 timestamp set several hours in the future, especially if
1170 you are running with local time set to GMT+X hours.
1173 The ip6fw utility has been removed. The behavior provided by
1174 ip6fw has been in ipfw2 for a good while and the rc.d scripts
1175 have been updated to deal with it. There are some rules that
1176 might not migrate cleanly. Use rc.firewall6 as a template to
1180 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
1181 attachments have been removed. Make sure to configure scc(4)
1182 on sparc64. Note also that by default puc(4) will use uart(4)
1183 and not sio(4) for serial ports because interrupt handling has
1184 been optimized for multi-port serial cards and only uart(4)
1185 implements the interface to support it.
1188 The scc(4) driver replaces puc(4) for Serial Communications
1189 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
1190 Z8530. On sparc64, it is advised to add scc(4) to the kernel
1191 configuration to make sure that the serial ports remain
1195 Most world/kernel related NO_* build options changed names.
1196 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
1197 after FreeBSD ports) and should be set in /etc/src.conf
1198 (the src.conf(5) manpage is provided). Full backwards
1199 compatibility is maintained for the time being though it's
1200 highly recommended to start moving old options out of the
1201 system-wide /etc/make.conf file into the new /etc/src.conf
1202 while also properly renaming them. More conversions will
1203 likely follow. Posting to current@:
1205 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
1208 The NETSMBCRYPTO kernel option has been retired because its
1209 functionality is always included in NETSMB and smbfs.ko now.
1212 The TDFX_LINUX kernel option was retired and replaced by the
1213 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
1214 kernel module. Loading it alone should suffice to get 3dfx support
1215 for Linux apps because it will pull in 3dfx.ko and linux.ko through
1219 The 'audit' group was added to support the new auditing functionality
1220 in the base system. Be sure to follow the directions for updating,
1221 including the requirement to run mergemaster -p.
1224 The kernel ABI to file system modules was changed on i386.
1225 Please make sure that your kernel and modules are in sync.
1228 This actually occured some time ago, but installing the kernel
1229 now also installs a bunch of symbol files for the kernel modules.
1230 This increases the size of /boot/kernel to about 67Mbytes. You
1231 will need twice this if you will eventually back this up to kernel.old
1232 on your next install.
1233 If you have a shortage of room in your root partition, you should add
1234 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
1235 to your /etc/make.conf.
1238 libc's malloc implementation has been replaced. This change has the
1239 potential to uncover application bugs that previously went unnoticed.
1240 See the malloc(3) manual page for more details.
1243 The generic netgraph(4) cookie has been changed. If you upgrade
1244 kernel passing this point, you also need to upgrade userland
1245 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
1248 si(4)'s device files now contain the unit number.
1249 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
1252 The kernel ABI was mostly destroyed due to a change in the size
1253 of struct lock_object which is nested in other structures such
1254 as mutexes which are nested in all sorts of other structures.
1255 Make sure your kernel and modules are in sync.
1258 The page coloring algorithm in the VM subsystem was converted
1259 from tuning with kernel options to autotuning. Please remove
1260 any PQ_* option except PQ_NOOPT from your kernel config.
1263 The net80211-related tools in the tools/tools/ath directory
1264 have been moved to tools/tools/net80211 and renamed with a
1265 "wlan" prefix. Scripts that use them should be adjusted
1269 Scripts in the local_startup directories (as defined in
1270 /etc/defaults/rc.conf) that have the new rc.d semantics will
1271 now be run as part of the base system rcorder. If there are
1272 errors or problems with one of these local scripts, it could
1273 cause boot problems. If you encounter such problems, boot in
1274 single user mode, remove that script from the */rc.d directory.
1275 Please report the problem to the port's maintainer, and the
1276 freebsd-ports@freebsd.org mailing list.
1279 The nodev mount option was deprecated in RELENG_6 (where it
1280 was a no-op), and is now unsupported. If you have nodev or dev listed
1281 in /etc/fstab, remove it, otherwise it will result in a mount error.
1284 ABI between ipfw(4) and ipfw(8) has been changed. You need
1285 to rebuild ipfw(8) when rebuilding kernel.
1288 rp(4)'s device files now contain the unit number.
1289 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
1292 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
1293 Its /etc/rc.conf.d configuration file has been `ppp' from
1294 the beginning, and hence there is no need to touch it.
1297 Now most modules get their build-time options from the kernel
1298 configuration file. A few modules still have fixed options
1299 due to their non-conformant implementation, but they will be
1300 corrected eventually. You may need to review the options of
1301 the modules in use, explicitly specify the non-default options
1302 in the kernel configuration file, and rebuild the kernel and
1306 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
1307 to turn polling(4) on your interfaces.
1310 The old bridge(4) implementation was retired. The new
1311 if_bridge(4) serves as a full functional replacement.
1314 The ai_addrlen of a struct addrinfo was changed to a socklen_t
1315 to conform to POSIX-2001. This change broke an ABI
1316 compatibility on 64 bit architecture. You have to recompile
1317 userland programs that use getaddrinfo(3) on 64 bit
1321 RELENG_6 branched here.
1324 The pccard_ifconfig rc.conf variable has been removed and a new
1325 variable, ifconfig_DEFAULT has been introduced. Unlike
1326 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
1327 do not have ifconfig_ifn entries rather than just those in
1328 removable_interfaces.
1331 Some previous versions of PAM have permitted the use of
1332 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
1333 to third party PAM modules in /usr/local/lib. A change has been
1334 made to require the use of absolute paths in order to avoid
1335 ambiguity and dependence on library path configuration, which may
1336 affect existing configurations.
1339 Major changes to network interface API. All drivers must be
1340 recompiled. Drivers not in the base system will need to be
1341 updated to the new APIs.
1344 Changes were made to kinfo_proc in sys/user.h. Please recompile
1345 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
1346 will not behave correctly.
1348 The API and ABI for hwpmc(4) have changed with the addition
1349 of sampling support. Please recompile lib/libpmc(3) and
1350 usr.sbin/{pmcstat,pmccontrol}.
1353 The OpenBSD dhclient was imported in place of the ISC dhclient
1354 and the network interface configuration scripts were updated
1355 accordingly. If you use DHCP to configure your interfaces, you
1356 must now run devd. Also, DNS updating was lost so you will need
1357 to find a workaround if you use this feature.
1359 The '_dhcp' user was added to support the OpenBSD dhclient. Be
1360 sure to run mergemaster -p (like you are supposed to do every time
1364 if_bridge was added to the tree. This has changed struct ifnet.
1365 Please recompile userland and all network related modules.
1368 The n_net of a struct netent was changed to an uint32_t, and
1369 1st argument of getnetbyaddr() was changed to an uint32_t, to
1370 conform to POSIX-2001. These changes broke an ABI
1371 compatibility on 64 bit architecture. With these changes,
1372 shlib major of libpcap was bumped. You have to recompile
1373 userland programs that use getnetbyaddr(3), getnetbyname(3),
1374 getnetent(3) and/or libpcap on 64 bit architecture.
1377 Kernel parsing of extra options on '#!' first lines of shell
1378 scripts has changed. Lines with multiple options likely will
1379 fail after this date. For full details, please see
1380 http://people.freebsd.org/~gad/Updating-20050528.txt
1383 The packet filter (pf) code has been updated to OpenBSD 3.7
1384 Please note the changed anchor syntax and the fact that
1385 authpf(8) now needs a mounted fdescfs(5) to function.
1388 The NO_MIXED_MODE kernel option has been removed from the i386
1389 amd64 platforms as its use has been superceded by the new local
1390 APIC timer code. Any kernel config files containing this option
1394 The on-disk format of LC_CTYPE files was changed to be machine
1395 independent. Please make sure NOT to use NO_CLEAN buildworld
1396 when crossing this point. Crossing this point also requires
1397 recompile or reinstall of all locale depended packages.
1400 The ifi_epoch member of struct if_data has been changed to
1401 contain the uptime at which the interface was created or the
1402 statistics zeroed rather then the wall clock time because
1403 wallclock time may go backwards. This should have no impact
1404 unless an snmp implementation is using this value (I know of
1405 none at this point.)
1408 The acpi_perf and acpi_throttle drivers are now part of the
1409 acpi(4) main module. They are no longer built separately.
1412 The layout of struct image_params has changed. You have to
1413 recompile all compatibility modules (linux, svr4, etc) for use
1414 with the new kernel.
1417 The p4tcc driver has been merged into cpufreq(4). This makes
1418 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
1419 compile in "device cpufreq" to restore this functionality.
1422 The responsibility of recomputing the file system summary of
1423 a SoftUpdates-enabled dirty volume has been transferred to the
1424 background fsck. A rebuild of fsck(8) utility is recommended
1425 if you have updated the kernel.
1427 To get the old behavior (recompute file system summary at mount
1428 time), you can set vfs.ffs.compute_summary_at_mount=1 before
1429 mounting the new volume.
1432 The cpufreq import is complete. As part of this, the sysctls for
1433 acpi(4) throttling have been removed. The power_profile script
1434 has been updated, so you can use performance/economy_cpu_freq in
1435 rc.conf(5) to set AC on/offline cpu frequencies.
1438 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
1439 requires recompiling libnetgraph and userland netgraph utilities.
1442 Support for abbreviated forms of a number of ipfw options is
1443 now deprecated. Warnings are printed to stderr indicating the
1444 correct full form when a match occurs. Some abbreviations may
1445 be supported at a later date based on user feedback. To be
1446 considered for support, abbreviations must be in use prior to
1447 this commit and unlikely to be confused with current key words.
1450 By a popular demand, a lot of NOFOO options were renamed
1451 to NO_FOO (see bsd.compat.mk for a full list). The old
1452 spellings are still supported, but will cause annoying
1453 warnings on stderr. Make sure you upgrade properly (see
1454 the COMMON ITEMS: section later in this file).
1457 Auto-loading of ancillary wlan modules such as wlan_wep has
1458 been temporarily disabled; you need to statically configure
1459 the modules you need into your kernel or explicitly load them
1460 prior to use. Specifically, if you intend to use WEP encryption
1461 with an 802.11 device load/configure wlan_wep; if you want to
1462 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
1463 and wlan_xauth as required.
1466 The behaviour of ppp(8) has changed slightly. If lqr is enabled
1467 (``enable lqr''), older versions would revert to LCP ECHO mode on
1468 negotiation failure. Now, ``enable echo'' is required for this
1469 behaviour. The ppp version number has been bumped to 3.4.2 to
1473 The wlan support has been updated to split the crypto support
1474 into separate modules. For static WEP you must configure the
1475 wlan_wep module in your system or build and install the module
1476 in place where it can be loaded (the kernel will auto-load
1477 the module when a wep key is configured).
1480 The ath driver has been updated to split the tx rate control
1481 algorithm into a separate module. You need to include either
1482 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
1485 Support for systems with an 80386 CPU has been removed. Please
1486 use FreeBSD 5.x or earlier on systems with an 80386.
1489 We have had a hack which would mount the root filesystem
1490 R/W if the device were named 'md*'. As part of the vnode
1491 work I'm doing I have had to remove this hack. People
1492 building systems which use preloaded MD root filesystems
1493 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
1494 their /etc/rc scripts.
1497 FreeBSD 5.3 shipped here.
1500 The size of struct tcpcb has changed again due to the removal
1501 of RFC1644 T/TCP. You have to recompile userland programs that
1502 read kmem for tcp sockets directly (netstat, sockstat, etc.)
1505 The size of struct tcpcb has changed. You have to recompile
1506 userland programs that read kmem for tcp sockets directly
1507 (netstat, sockstat, etc.)
1510 RELENG_5 branched here. For older entries, please see updating
1511 in the RELENG_5 branch.
1517 Avoid using make -j when upgrading. From time to time in the
1518 past there have been problems using -j with buildworld and/or
1519 installworld. This is especially true when upgrading between
1520 "distant" versions (eg one that cross a major release boundary
1521 or several minor releases, or when several months have passed
1522 on the -current branch).
1524 Sometimes, obscure build problems are the result of environment
1525 poisoning. This can happen because the make utility reads its
1526 environment when searching for values for global variables.
1527 To run your build attempts in an "environmental clean room",
1528 prefix all make commands with 'env -i '. See the env(1) manual
1529 page for more details.
1531 When upgrading from one major version to another it is generally
1532 best to upgrade to the latest code in the currently installed branch
1533 first, then do an upgrade to the new branch. This is the best-tested
1534 upgrade path, and has the highest probability of being successful.
1535 Please try this approach before reporting problems with a major
1540 If you are updating from a prior version of FreeBSD (even one just
1541 a few days old), you should follow this procedure. It is the most
1542 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1544 make kernel-toolchain
1545 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1546 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1548 To test a kernel once
1549 ---------------------
1550 If you just want to boot a kernel once (because you are not sure
1551 if it works, or if you want to boot a known bad kernel to provide
1552 debugging information) run
1553 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1554 nextboot -k testkernel
1556 To just build a kernel when you know that it won't mess you up
1557 --------------------------------------------------------------
1558 This assumes you are already running a 5.X system. Replace
1559 ${arch} with the architecture of your machine (e.g. "i386",
1560 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1562 cd src/sys/${arch}/conf
1563 config KERNEL_NAME_HERE
1564 cd ../compile/KERNEL_NAME_HERE
1569 If this fails, go to the "To build a kernel" section.
1571 To rebuild everything and install it on the current system.
1572 -----------------------------------------------------------
1573 # Note: sometimes if you are running current you gotta do more than
1574 # is listed here if you are upgrading from a really old current.
1576 <make sure you have good level 0 dumps>
1578 make kernel KERNCONF=YOUR_KERNEL_HERE
1580 <reboot in single user> [3]
1588 To cross-install current onto a separate partition
1589 --------------------------------------------------
1590 # In this approach we use a separate partition to hold
1591 # current's root, 'usr', and 'var' directories. A partition
1592 # holding "/", "/usr" and "/var" should be about 2GB in
1595 <make sure you have good level 0 dumps>
1598 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1599 <maybe newfs current's root partition>
1600 <mount current's root partition on directory ${CURRENT_ROOT}>
1601 make installworld DESTDIR=${CURRENT_ROOT}
1602 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1603 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1604 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1605 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1606 <reboot into current>
1607 <do a "native" rebuild/install as described in the previous section>
1608 <maybe install compatibility libraries from ports/misc/compat*>
1612 To upgrade in-place from 5.x-stable to current
1613 ----------------------------------------------
1614 <make sure you have good level 0 dumps>
1616 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1618 <reboot in single user> [3]
1625 Make sure that you've read the UPDATING file to understand the
1626 tweaks to various things you need. At this point in the life
1627 cycle of current, things change often and you are on your own
1628 to cope. The defaults can also change, so please read ALL of
1629 the UPDATING entries.
1631 Also, if you are tracking -current, you must be subscribed to
1632 freebsd-current@freebsd.org. Make sure that before you update
1633 your sources that you have read and understood all the recent
1634 messages there. If in doubt, please track -stable which has
1635 much fewer pitfalls.
1637 [1] If you have third party modules, such as vmware, you
1638 should disable them at this point so they don't crash your
1641 [3] From the bootblocks, boot -s, and then do
1646 adjkerntz -i # if CMOS is wall time
1647 Also, when doing a major release upgrade, it is required that
1648 you boot into single user mode to do the installworld.
1650 [4] Note: This step is non-optional. Failure to do this step
1651 can result in a significant reduction in the functionality of the
1652 system. Attempting to do it by hand is not recommended and those
1653 that pursue this avenue should read this file carefully, as well
1654 as the archives of freebsd-current and freebsd-hackers mailing lists
1655 for potential gotchas.
1657 [5] Usually this step is a noop. However, from time to time
1658 you may need to do this if you get unknown user in the following
1659 step. It never hurts to do it all the time. You may need to
1660 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1661 install) after the buildworld before this step if you last updated
1662 from current before 20020224 or from -stable before 20020408.
1664 [8] In order to have a kernel that can run the 4.x binaries
1665 needed to do an installworld, you must include the COMPAT_FREEBSD4
1666 option in your kernel. Failure to do so may leave you with a system
1667 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
1668 is required to run the 5.x binaries on more recent kernels.
1670 Make sure that you merge any new devices from GENERIC since the
1671 last time you updated your kernel config file.
1673 [9] When checking out sources, you must include the -P flag to have
1674 cvs prune empty directories.
1676 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1677 "?=" instead of the "=" assignment operator, so that buildworld can
1678 override the CPUTYPE if it needs to.
1680 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1681 not on the command line, or in /etc/make.conf. buildworld will
1682 warn if it is improperly defined.
1685 This file contains a list, in reverse chronological order, of major
1686 breakages in tracking -current. Not all things will be listed here,
1687 and it only starts on October 16, 2004. Updating files can found in
1688 previous releases if your system is older than this.
1690 Copyright information:
1692 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
1694 Redistribution, publication, translation and use, with or without
1695 modification, in full or in part, in any form or format of this
1696 document are permitted without further permission from the author.
1698 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1699 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1700 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1701 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1702 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1703 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1704 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1705 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1706 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1707 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1708 POSSIBILITY OF SUCH DAMAGE.
1710 If you find this document useful, and you want to, you may buy the
1713 Contact Warner Losh if you have any questions about your use of