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.
18 20110528: p2 FreeBSD-SA-11:02.bind
19 Fix BIND remote DoS with large RRSIG RRsets and negative
22 20110420: p1 FreeBSD-SA-11:01.mountd
23 Fix CIDR parsing bug in mountd ACLs.
29 New version of minidump format for amd64 architecture was
30 introduced in r215872. To analyze vmcore files produced by
31 kernels at or after this version you will need updated userland,
32 libkvm actually, that is able to handle the new version.
35 A workaround for a fixed ld bug has been removed in kernel code,
36 so make sure that your system ld is built from sources after
37 revision 211583 from 2010-08-21 (r210245 from 2010-07-19 if
38 building stable/8 kernel on head, r211584 from 2010-08-21 for
39 stable/7). A symptom of incorrect ld version is
40 different addresses for set_pcpu section and __start_set_pcpu
41 symbol in kernel and/or modules.
44 A new version of ZFS (version 15) has been merged.
45 This version uses a python library for the following subcommands:
46 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
47 For full functionality of these commands the following port must
48 be installed: sysutils/py-zfs
54 The config(8) command has been updated to maintain compatibility
55 with config files from 8.0-RELEASE. You will need a new version
56 of config to build kernels (this version can be used from 8.0-RELEASE
57 forward). The buildworld target will generate it, so following
58 the instructions in this file for updating will work glitch-free.
59 Merely doing a make buildkernel without first doing a make buildworld
60 (or kernel-toolchain), or attempting to build a kernel using
61 traidtional methods will generate a config version warning, indicating
65 The rc.firewall and rc.firewall6 were unified, and
66 rc.firewall6 and rc.d/ip6fw were removed.
67 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
68 variables are obsoleted. Instead, the following new rc
69 variables are added to rc.d/ipfw:
71 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
72 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
73 firewall_simple_onet_ipv6
75 The meanings correspond to the relevant IPv4 variables.
78 COMPAT_IA32 has been added as an alias for COMPAT_FREEBSD32. A new
79 version of config(8) is required. The error message when you hit this
80 condition is confusing (COMPAT_FREEBSD32 duplicate option), when it
81 should really say "your config is too old to compile this new kernel."
84 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
85 to allow 32-bit compatibility on non-x86 platforms. All kernel
86 configurations on amd64 and ia64 platforms using these options must
87 be modified accordingly.
90 Introduce the kernel thread "deadlock resolver" (which can be enabled
91 via the DEADLKRES option, see NOTES for more details) and the
92 sleepq_type() function for sleepqueues.
98 802.11s D3.03 support was committed. This is incompatible with
99 the previous code, which was based on D3.0.
102 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
103 mount(8) and -a option for df(1) to see them.
106 Remove the option STOP_NMI. The default action is now to use NMI
107 only for KDB via the newly introduced function stop_cpus_hard()
108 and maintain stop_cpus() to just use a normal IPI_STOP on ia32
115 Bump the shared library version numbers for all libraries that
116 do not use symbol versioning as part of the 8.0-RELEASE cycle.
117 Bump __FreeBSD_version to 800105.
120 Due to changes in the implementation of virtual network stack
121 support, all network-related kernel modules must be recompiled.
122 As this change breaks the ABI, bump __FreeBSD_version to 800104.
125 The TOE interface to the TCP syncache has been modified to remove struct
126 tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack. The
127 cxgb driver is the only TOE consumer affected by this change, and needs
128 to be recompiled along with the kernel. As this change breaks the ABI,
129 bump __FreeBSD_version to 800103.
132 Padding has been added to struct tcpcb, sackhint and tcpstat in
133 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
134 maintainig the ABI. However, this change breaks the ABI, so bump
135 __FreeBSD_version to 800102. User space tools that rely on the size of
136 any of these structs (e.g. sockstat) need to be recompiled.
139 The NFS_LEGACYRPC option has been removed along with the old
140 kernel RPC implementation that this option selected. Kernel
141 configurations may need to be adjusted.
144 The network interface device nodes at /dev/net/<interface> have
145 been removed. All ioctl operations can be performed the normal
146 way using routing sockets. The kqueue functionality can
147 generally be replaced with routing sockets.
150 The documentation from the FreeBSD Documentation Project
151 (Handbook, FAQ, etc.) is now installed via packages by
152 sysinstall(8) and under the /usr/local/share/doc/freebsd
153 directory instead of /usr/share/doc.
156 The ABI of various structures related to the SYSV IPC API have
157 been changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43
158 kernel options now all require COMPAT_FREEBSD7.
159 Bump __FreeBSD_version to 800100.
162 Layout of struct vnet has changed as routing related variables
163 were moved to their own Vimage module. Modules need to be
164 recompiled. Bump __FreeBSD_version to 800099.
167 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023
168 and 1024 respectively. As long as no more than 16 groups per
169 process are used, no changes should be visible. When more
170 than 16 groups are used, old binaries may fail if they call
171 getgroups() or getgrouplist() with statically sized storage.
172 Recompiling will work around this, but applications should be
173 modified to use dynamically allocated storage for group arrays
174 as POSIX.1-2008 does not cap an implementation's number of
175 supported groups at NGROUPS_MAX+1 as previous versions did.
177 NFS and portalfs mounts may also be affected as the list of
178 groups is truncated to 16. Users of NFS who use more than 16
179 groups, should take care that negative group permissions are not
180 used on the exported file systems as they will not be reliable
181 unless a GSSAPI based authentication method is used.
184 The compiling option ADAPTIVE_LOCKMGRS has been introduced.
185 This option compiles in the support for adaptive spinning for lockmgrs
186 which want to enable it. The lockinit() function now accepts the
187 flag LK_ADAPTIVE in order to make the lock object subject to
188 adaptive spinning when both held in write and read mode.
191 The layout of the structure returned by IEEE80211_IOC_STA_INFO
192 has changed. User applications that use this ioctl need to be
196 The layout of struct thread has changed. Kernel and modules
200 The layout of structs ifnet, domain, protosw and vnet_net has
201 changed. Kernel modules need to be rebuilt.
202 Bump __FreeBSD_version to 800097.
205 window(1) has been removed from the base system. It can now be
206 installed from ports. The port is called misc/window.
209 The way we are storing and accessing `routing table' entries
210 has changed. Programs reading the FIB, like netstat, need to
214 A new netisr implementation has been added for FreeBSD 8. Network
215 file system modules, such as igmp, ipdivert, and others, should be
217 Bump __FreeBSD_version to 800096.
220 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose
224 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
225 Bump __FreeBSD_version to 800094.
228 Add mnt_xflag field to 'struct mount'. File system modules
230 Bump __FreeBSD_version to 800093.
233 The compiling option ADAPTIVE_SX has been retired while it has been
234 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
235 The KPI for sx_init_flags() changes as accepting flags:
236 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag
237 has been introduced in order to handle the reversed logic.
238 Bump __FreeBSD_version to 800092.
241 Add support for hierarchical jails. Remove global securelevel.
242 Bump __FreeBSD_version to 800091.
245 The layout of struct vnet_net has changed, therefore modules
247 Bump __FreeBSD_version to 800090.
250 The newly imported zic(8) produces a new format in the
251 output. Please run tzsetup(8) to install the newly created
252 data to /etc/localtime.
255 The sysctl tree for the usb stack has renamed from hw.usb2.* to
256 hw.usb.* and is now consistent again with previous releases.
259 802.11 monitor mode support was revised and driver api's
260 were changed. Drivers dependent on net80211 now support
261 DLT_IEEE802_11_RADIO instead of DLT_IEEE802_11. No
262 user-visible data structures were changed but applications
263 that use DLT_IEEE802_11 may require changes.
264 Bump __FreeBSD_version to 800088.
267 The layout of the following structs has changed: sysctl_oid,
268 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
269 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
270 panics may be experienced. World rebuild is required for
271 correctly checking networking state from userland.
272 Bump __FreeBSD_version to 800085.
275 MLDv2 and Source-Specific Multicast (SSM) have been merged
276 to the IPv6 stack. VIMAGE hooks are in but not yet used.
277 The implementation of SSM within FreeBSD's IPv6 stack closely
278 follows the IPv4 implementation.
280 For kernel developers:
282 * The most important changes are that the ip6_output() and
283 ip6_input() paths no longer take the IN6_MULTI_LOCK,
284 and this lock has been downgraded to a non-recursive mutex.
286 * As with the changes to the IPv4 stack to support SSM, filtering
287 of inbound multicast traffic must now be performed by transport
288 protocols within the IPv6 stack. This does not apply to TCP and
289 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
291 * The KPIs used by IPv6 multicast are similar to those used by
292 the IPv4 stack, with the following differences:
293 * im6o_mc_filter() is analogous to imo_multicast_filter().
294 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
295 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
296 * IN6_LOOKUP_MULTI() has been deprecated and removed.
297 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
298 for MLDv1 have an additional 'timer' argument which is used to
299 jitter the initial membership report for the solicited-node
300 multicast membership on-link.
301 * This is not strictly needed for MLDv2, which already jitters
302 its report transmissions. However, the 'timer' argument is
303 preserved in case MLDv1 is active on the interface.
305 * The KAME linked-list based IPv6 membership implementation has
306 been refactored to use a vector similar to that used by the IPv4
308 Code which maintains a list of its own multicast memberships
309 internally, e.g. carp, has been updated to reflect the new
312 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
313 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
314 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
315 implementation constraint which needs to be addressed in HEAD.
317 For application developers:
319 * The changes are broadly similar to those made for the IPv4
322 * The use of IPv4 and IPv6 multicast socket options on the same
323 socket, using mapped addresses, HAS NOT been tested or supported.
325 * There are a number of issues with the implementation of various
326 IPv6 multicast APIs which need to be resolved in the API surface
327 before the implementation is fully compatible with KAME userland
328 use, and these are mostly to do with interface index treatment.
330 * The literature available discusses the use of either the delta / ASM
331 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
332 using setsourcefilter(3)/getsourcefilter(3). For more information
333 please refer to RFC 3768, 'Socket Interface Extensions for
334 Multicast Source Filters'.
336 * Applications which use the published RFC 3678 APIs should be fine.
338 For systems administrators:
340 * The mtest(8) utility has been refactored to support IPv6, in
341 addition to IPv4. Interface addresses are no longer accepted
342 as arguments, their names must be used instead. The utility
343 will map the interface name to its first IPv4 address as
344 returned by getifaddrs(3).
346 * The ifmcstat(8) utility has also been updated to print the MLDv2
347 endpoint state and source filter lists via sysctl(3).
349 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
350 loopback of IPv6 multicast datagrams by default; it defaults to 1
351 to preserve the existing behaviour. Disabling multicast loopback is
352 recommended for optimal system performance.
354 * The IPv6 MROUTING code has been changed to examine this sysctl
355 instead of attempting to perform a group lookup before looping
356 back forwarded datagrams.
358 Bump __FreeBSD_version to 800084.
361 Implement low-level Bluetooth HCI API.
362 Bump __FreeBSD_version to 800083.
365 The layout of struct malloc_type, used by modules to register new
366 memory allocation types, has changed. Most modules will need to
367 be rebuilt or panics may be experienced.
368 Bump __FreeBSD_version to 800081.
371 Anticipate overflowing inp_flags - add inp_flags2.
372 This changes most offsets in inpcb, so checking v4 connection
373 state will require a world rebuild.
374 Bump __FreeBSD_version to 800080.
377 Add an llentry to struct route and struct route_in6. Modules
378 embedding a struct route will need to be recompiled.
379 Bump __FreeBSD_version to 800079.
382 The size of rt_metrics_lite and by extension rtentry has changed.
383 Networking administration apps will need to be recompiled.
384 The route command now supports show as an alias for get, weighting
385 of routes, sticky and nostick flags to alter the behavior of stateful
387 Bump __FreeBSD_version to 800078.
390 Do not use Giant for kbdmux(4) locking. This is wrong and
391 apparently causing more problems than it solves. This will
392 re-open the issue where interrupt handlers may race with
393 kbdmux(4) in polling mode. Typical symptoms include (but
394 not limited to) duplicated and/or missing characters when
395 low level console functions (such as gets) are used while
396 interrupts are enabled (for example geli password prompt,
397 mountroot prompt etc.). Disabling kbdmux(4) may help.
400 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
401 kernel modules referencing any of the above need to be recompiled.
402 Bump __FreeBSD_version to 800075.
405 GEOM_PART has become the default partition slicer for storage devices,
406 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
407 introduces some changes:
409 MSDOS/EBR: the devices created from MSDOS extended partition entries
410 (EBR) can be named differently than with GEOM_MBR and are now symlinks
411 to devices with offset-based names. fstabs may need to be modified.
413 BSD: the "geometry does not match label" warning is harmless in most
414 cases but it points to problems in file system misalignment with
415 disk geometry. The "c" partition is now implicit, covers the whole
416 top-level drive and cannot be (mis)used by users.
418 General: Kernel dumps are now not allowed to be written to devices
419 whose partition types indicate they are meant to be used for file
420 systems (or, in case of MSDOS partitions, as something else than
423 Most of these changes date approximately from 200812.
426 The uscanner(4) driver has been removed from the kernel. This follows
427 Linux removing theirs in 2.6 and making libusb the default interface
431 The multicast forwarding code has been cleaned up. netstat(1)
432 only relies on KVM now for printing bandwidth upcall meters.
433 The IPv4 and IPv6 modules are split into ip_mroute_mod and
434 ip6_mroute_mod respectively. The config(5) options for statically
435 compiling this code remain the same, i.e. 'options MROUTING'.
438 Support for the IFF_NEEDSGIANT network interface flag has been
439 removed, which means that non-MPSAFE network device drivers are no
440 longer supported. In particular, if_ar, if_sr, and network device
441 drivers from the old (legacy) USB stack can no longer be built or
445 POSIX.1 Native Language Support (NLS) has been enabled in libc and
446 a bunch of new language catalog files have also been added.
447 This means that some common libc messages are now localized and
448 they depend on the LC_MESSAGES environmental variable.
451 The k8temp(4) driver has been renamed to amdtemp(4) since
452 support for K10 and K11 CPU families was added.
455 IGMPv3 and Source-Specific Multicast (SSM) have been merged
456 to the IPv4 stack. VIMAGE hooks are in but not yet used.
458 For kernel developers, the most important changes are that the
459 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
460 and this lock has been downgraded to a non-recursive mutex.
462 Transport protocols (UDP, Raw IP) are now responsible for filtering
463 inbound multicast traffic according to group membership and source
464 filters. The imo_multicast_filter() KPI exists for this purpose.
465 Transports which do not use multicast (SCTP, TCP) already reject
466 multicast by default. Forwarding and receive performance may improve
467 as a mutex acquisition is no longer needed in the ip_input()
468 low-level input path. in_addmulti() and in_delmulti() are shimmed
469 to new KPIs which exist to support SSM in-kernel.
471 For application developers, it is recommended that loopback of
472 multicast datagrams be disabled for best performance, as this
473 will still cause the lock to be taken for each looped-back
474 datagram transmission. The net.inet.ip.mcast.loop sysctl may
475 be tuned to 0 to disable loopback by default; it defaults to 1
476 to preserve the existing behaviour.
478 For systems administrators, to obtain best performance with
479 multicast reception and multiple groups, it is always recommended
480 that a card with a suitably precise hash filter is used. Hash
481 collisions will still result in the lock being taken within the
482 transport protocol input path to check group membership.
484 If deploying FreeBSD in an environment with IGMP snooping switches,
485 it is recommended that the net.inet.igmp.sendlocal sysctl remain
486 enabled; this forces 224.0.0.0/24 group membership to be announced
489 The size of 'struct igmpstat' has changed; netstat needs to be
490 recompiled to reflect this.
491 Bump __FreeBSD_version to 800070.
494 libusb20.so.1 is now installed as libusb.so.1 and the ports system
495 updated to use it. This requires a buildworld/installworld in order to
496 update the library and dependencies (usbconfig, etc). Its advisable to
497 rebuild all ports which uses libusb. More specific directions are given
498 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
499 libusb are no longer required and can be removed.
502 A workaround is committed to allow the creation of System V shared
503 memory segment of size > 2 GB on the 64-bit architectures.
504 Due to a limitation of the existing ABI, the shm_segsz member
505 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
506 wrong for large segments. Note that limits must be explicitly
507 raised to allow such segments to be created.
510 The layout of struct ifnet has changed, requiring a rebuild of all
511 network device driver modules.
514 The /dev handling for the new USB stack has changed, a
515 buildworld/installworld is required for libusb20.
518 The new USB2 stack has now been permanently moved in and all kernel and
519 module names reverted to their previous values (eg, usb, ehci, ohci,
520 ums, ...). The old usb stack can be compiled in by prefixing the name
521 with the letter 'o', the old usb modules have been removed.
522 Updating entry 20090216 for xorg and 20090215 for libmap may still
526 The rc.conf(5) option if_up_delay has been renamed to
527 defaultroute_delay to better reflect its purpose. If you have
528 customized this setting in /etc/rc.conf you need to update it to
532 xorg 7.4 wants to configure its input devices via hald which does not
533 yet work with USB2. If the keyboard/mouse does not work in xorg then
535 Option "AllowEmptyInput" "off"
536 to your ServerLayout section. This will cause X to use the configured
537 kbd and mouse sections from your xorg.conf.
540 The GENERIC kernels for all architectures now default to the new USB2
541 stack. No kernel config options or code have been removed so if a
542 problem arises please report it and optionally revert to the old USB
543 stack. If you are loading USB kernel modules or have a custom kernel
544 that includes GENERIC then ensure that usb names are also changed over,
545 eg uftdi -> usb2_serial_ftdi.
547 Older programs linked against the ports libusb 0.1 need to be
548 redirected to the new stack's libusb20. /etc/libmap.conf can
550 # Map old usb library to new one for usb2 stack
551 libusb-0.1.so.8 libusb20.so.1
554 All USB ethernet devices now attach as interfaces under the name ueN
555 (eg. ue0). This is to provide a predictable name as vendors often
556 change usb chipsets in a product without notice.
559 The ichsmb(4) driver has been changed to require SMBus slave
560 addresses be left-justified (xxxxxxx0b) rather than right-justified.
561 All of the other SMBus controller drivers require left-justified
562 slave addresses, so this change makes all the drivers provide the
566 INET6 statistics (struct ip6stat) was updated.
567 netstat(1) needs to be recompiled.
570 NTFS has been removed from GENERIC kernel on amd64 to match
571 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
572 will load ntfs.ko module automatically when NTFS support is
573 actually needed, unless ntfs.ko is not installed or security
574 level prohibits loading kernel modules. If either is the case,
575 "options NTFS" has to be added into kernel config.
578 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
579 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
580 800061. User space tools that rely on the size of struct tcpcb in
581 tcp_var.h (e.g. sockstat) need to be recompiled.
584 ng_tty(4) module updated to match the new TTY subsystem.
585 Due to API change, user-level applications must be updated.
586 New API support added to mpd5 CVS and expected to be present
587 in next mpd5.3 release.
590 With __FreeBSD_version 800060 the makefs tool is part of
591 the base system (it was a port).
594 The afdata and ifnet locks have been changed from mutexes to
595 rwlocks, network modules will need to be re-compiled.
598 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
599 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
600 The new code reduced struct rtentry{} by 16 bytes on 32-bit
601 architecture and 40 bytes on 64-bit architecture. The userland
602 applications "arp" and "ndp" have been updated accordingly.
603 The output from "netstat -r" shows only routing entries and
604 none of the L2 information.
607 __FreeBSD_version 800057 marks the switchover from the
608 binary ath hal to source code. Users must add the line:
610 options AH_SUPPORT_AR5416
612 to their kernel config files when specifying:
616 The ath_hal module no longer exists; the code is now compiled
617 together with the driver in the ath module. It is now
618 possible to tailor chip support (i.e. reduce the set of chips
619 and thereby the code size); consult ath_hal(4) for details.
622 __FreeBSD_version 800054 adds memory barriers to
623 <machine/atomic.h>, new interfaces to ifnet to facilitate
624 multiple hardware transmit queues for cards that support
625 them, and a lock-less ring-buffer implementation to
626 enable drivers to more efficiently manage queueing of
630 A new version of ZFS (version 13) has been merged to -HEAD.
631 This version has zpool attribute "listsnapshots" off by
632 default, which means "zfs list" does not show snapshots,
633 and is the same as Solaris behavior.
636 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
639 The uhci, ohci, ehci and slhci USB Host controller drivers have
640 been put into separate modules. If you load the usb module
641 separately through loader.conf you will need to load the
642 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
643 controller add the following to loader.conf:
649 The ABI used by the PMC toolset has changed. Please keep
650 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
654 atapci kernel module now includes only generic PCI ATA
655 driver. AHCI driver moved to ataahci kernel module.
656 All vendor-specific code moved into separate kernel modules:
657 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
658 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
659 atamarvell, atamicron, atanational, atanetcell, atanvidia,
660 atapromise, ataserverworks, atasiliconimage, atasis, atavia
663 The TTY subsystem of the kernel has been replaced by a new
664 implementation, which provides better scalability and an
665 improved driver model. Most common drivers have been migrated to
666 the new TTY subsystem, while others have not. The following
667 drivers have not yet been ported to the new TTY layer:
670 cy, digi, rc, rp, sio
676 ng_h4, ng_tty, ppp, sl, snp
678 Adding these drivers to your kernel configuration file shall
679 cause compilation to fail.
682 ntpd has been upgraded to 4.2.4p5.
685 OpenSSH has been upgraded to 5.1p1.
687 For many years, FreeBSD's version of OpenSSH preferred DSA
688 over RSA for host and user authentication keys. With this
689 upgrade, we've switched to the vendor's default of RSA over
690 DSA. This may cause upgraded clients to warn about unknown
691 host keys even for previously known hosts. Users should
692 follow the usual procedure for verifying host keys before
693 accepting the RSA key.
695 This can be circumvented by setting the "HostKeyAlgorithms"
696 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
699 Please note that the sequence of keys offered for
700 authentication has been changed as well. You may want to
701 specify IdentityFile in a different order to revert this
705 The sio(4) driver has been removed from the i386 and amd64
706 kernel configuration files. This means uart(4) is now the
707 default serial port driver on those platforms as well.
709 To prevent collisions with the sio(4) driver, the uart(4) driver
710 uses different names for its device nodes. This means the
711 onboard serial port will now most likely be called "ttyu0"
712 instead of "ttyd0". You may need to reconfigure applications to
713 use the new device names.
715 When using the serial port as a boot console, be sure to update
716 /boot/device.hints and /etc/ttys before booting the new kernel.
717 If you forget to do so, you can still manually specify the hints
718 at the loader prompt:
720 set hint.uart.0.at="isa"
721 set hint.uart.0.port="0x3F8"
722 set hint.uart.0.flags="0x10"
723 set hint.uart.0.irq="4"
727 The gpt(8) utility has been removed. Use gpart(8) to partition
731 The version that Linuxulator emulates was changed from 2.4.2
732 to 2.6.16. If you experience any problems with Linux binaries
733 please try to set sysctl compat.linux.osrelease to 2.4.2 and
734 if it fixes the problem contact emulation mailing list.
737 ISDN4BSD (I4B) was removed from the src tree. You may need to
738 update a your kernel configuration and remove relevant entries.
741 I have checked in code to support multiple routing tables.
742 See the man pages setfib(1) and setfib(2).
743 This is a hopefully backwards compatible version,
744 but to make use of it you need to compile your kernel
745 with options ROUTETABLES=2 (or more up to 16).
748 The 802.11 wireless support was redone to enable multi-bss
749 operation on devices that are capable. The underlying device
750 is no longer used directly but instead wlanX devices are
751 cloned with ifconfig. This requires changes to rc.conf files.
753 ifconfig_ath0="WPA DHCP"
756 ifconfig_wlan0="WPA DHCP"
757 see rc.conf(5) for more details. In addition, mergemaster of
758 /etc/rc.d is highly recommended. Simultaneous update of userland
759 and kernel wouldn't hurt either.
761 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
762 modules were merged into the base wlan module. All references
763 to these modules (e.g. in kernel config files) must be removed.
766 psm(4) has gained write(2) support in native operation level.
767 Arbitrary commands can be written to /dev/psm%d and status can
768 be read back from it. Therefore, an application is responsible
769 for status validation and error recovery. It is a no-op in
770 other operation levels.
773 Support for KSE threading has been removed from the kernel. To
774 run legacy applications linked against KSE libmap.conf may
775 be used. The following libmap.conf may be used to ensure
776 compatibility with any prior release:
778 libpthread.so.1 libthr.so.1
779 libpthread.so.2 libthr.so.2
780 libkse.so.3 libthr.so.3
783 The layout of struct vmspace has changed. This affects libkvm
784 and any executables that link against libkvm and use the
785 kvm_getprocs() function. In particular, but not exclusively,
786 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
787 The effects are minimal, but it's advisable to upgrade world
791 The latest em driver no longer has support in it for the
792 82575 adapter, this is now moved to the igb driver. The
793 split was done to make new features that are incompatible
794 with older hardware easier to do.
797 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
798 likewise the kernel option is now GEOM_LINUX_LVM.
801 The default NFS mount mode has changed from UDP to TCP for
802 increased reliability. If you rely on (insecurely) NFS
803 mounting across a firewall you may need to update your
807 Belatedly note the addition of m_collapse for compacting
811 The fts(3) structures have been changed to use adequate
812 integer types for their members and so to be able to cope
813 with huge file trees. The old fts(3) ABI is preserved
814 through symbol versioning in libc, so third-party binaries
815 using fts(3) should still work, although they will not take
816 advantage of the extended types. At the same time, some
817 third-party software might fail to build after this change
818 due to unportable assumptions made in its source code about
819 fts(3) structure members. Such software should be fixed
820 by its vendor or, in the worst case, in the ports tree.
821 FreeBSD_version 800015 marks this change for the unlikely
822 case that a portable fix is impossible.
825 To upgrade to -current after this date, you must be running
826 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
827 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
830 The ADAPTIVE_GIANT kernel option has been retired because its
831 functionality is the default now.
834 The AT keyboard emulation of sunkbd(4) has been turned on
835 by default. In order to make the special symbols of the Sun
836 keyboards driven by sunkbd(4) work under X these now have
837 to be configured the same way as Sun USB keyboards driven
838 by ukbd(4) (which also does AT keyboard emulation), f.e.:
840 Option "XkbLayout" "us"
841 Option "XkbRules" "xorg"
842 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
845 It has been decided that it is desirable to provide ABI
846 backwards compatibility to the FreeBSD 4/5/6 versions of the
847 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
848 broken with the introduction of PCI domain support (see the
849 20070930 entry). Unfortunately, this required the ABI of
850 PCIOCGETCONF to be broken again in order to be able to
851 provide backwards compatibility to the old version of that
852 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
853 again. As for prominent ports this affects neither pciutils
854 nor xorg-server this time, the hal port needs to be rebuilt
858 The misnamed kthread_create() and friends have been renamed
859 to kproc_create() etc. Many of the callers already
861 I will return kthread_create() and friends in a while
862 with implementations that actually create threads, not procs.
863 Renaming corresponds with version 800002.
869 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
870 WITHOUT_LIBTHR are set.
873 The PCI code has been made aware of PCI domains. This means that
874 the location strings as used by pciconf(8) etc are now in the
875 following format: pci<domain>:<bus>:<device>[:<function>]. It
876 also means that consumers of <sys/pciio.h> potentially need to
877 be recompiled; this includes the hal and xorg-server ports.
880 The caching daemon (cached) was renamed to nscd. nscd.conf
881 configuration file should be used instead of cached.conf and
882 nscd_enable, nscd_pidfile and nscd_flags options should be used
883 instead of cached_enable, cached_pidfile and cached_flags in
887 The getfacl(1) utility now prints owning user and group name
888 instead of owning uid and gid in the three line comment header.
889 This is the same behavior as getfacl(1) on Solaris and Linux.
892 The new IPsec code is now compiled in using the IPSEC option. The
893 IPSEC option now requires "device crypto" be defined in your kernel
894 configuration. The FAST_IPSEC kernel option is now deprecated.
897 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
898 note the changed syntax - keep state is now on by default. Also
899 note the fact that ftp-proxy(8) has been changed from bottom up and
900 has been moved from libexec to usr/sbin. Changes in the ALTQ
901 handling also affect users of IPFW's ALTQ capabilities.
904 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
905 only IPsec supported by FreeBSD. The new IPsec stack
906 supports both IPv4 and IPv6. The kernel option will change
907 after the code changes have settled in. For now the kernel
908 option IPSEC is deprecated and FAST_IPSEC is the only option, that
909 will change after some settling time.
912 The wicontrol(8) utility has been removed from the base system. wi(4)
913 cards should be configured using ifconfig(8), see the man page for more
917 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
918 instead of the nve(4) driver. Please update your configuration
922 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
923 database if it is missing or older than the aliases file. If
924 desired, set the new rc.conf option sendmail_rebuild_aliases
925 to "YES" to restore that functionality.
928 The IPv4 multicast socket code has been considerably modified, and
929 moved to the file sys/netinet/in_mcast.c. Initial support for the
930 RFC 3678 Source-Specific Multicast Socket API has been added to
931 the IPv4 network stack.
933 Strict multicast and broadcast reception is now the default for
934 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
935 has now been removed.
937 The RFC 1724 hack for interface selection has been removed; the use
938 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
939 been added to replace it. Consumers such as routed will soon be
940 updated to reflect this.
942 These changes affect users who are running routed(8) or rdisc(8)
943 from the FreeBSD base system on point-to-point or unnumbered
947 The net80211 layer has changed significantly and all wireless
948 drivers that depend on it need to be recompiled. Further these
949 changes require that any program that interacts with the wireless
950 support in the kernel be recompiled; this includes: ifconfig,
951 wpa_supplicant, hostapd, and wlanstats. Users must also, for
952 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
953 if they use modules for wireless support. These modules implement
954 scanning support for station and ap modes, respectively. Failure
955 to load the appropriate module before marking a wireless interface
956 up will result in a message to the console and the device not
960 The pam_nologin(8) module ceases to provide an authentication
961 function and starts providing an account management function.
962 Consequent changes to /etc/pam.d should be brought in using
963 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
964 need manual editing as follows. Locate this line (or similar):
966 auth required pam_nologin.so no_warn
968 and change it according to this example:
970 account required pam_nologin.so no_warn
972 That is, the first word needs to be changed from "auth" to
973 "account". The new line can be moved to the account section
974 within the file for clarity. Not updating pam.conf(5) files
975 will result in nologin(5) ignored by the respective services.
978 The ether_ioctl() function has been synchronized with ioctl(2)
979 and ifnet.if_ioctl. Due to that, the size of one of its arguments
980 has changed on 64-bit architectures. All kernel modules using
981 ether_ioctl() need to be rebuilt on such architectures.
984 Improved INCLUDE_CONFIG_FILE support has been introduced to the
985 config(8) utility. In order to take advantage of this new
986 functionality, you are expected to recompile and install
987 src/usr.sbin/config. If you don't rebuild config(8), and your
988 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
989 build will be broken because of a missing "kernconfstring"
993 Symbol versioning is enabled by default. To disable it, use
994 option WITHOUT_SYMVER. It is not advisable to attempt to
995 disable symbol versioning once it is enabled; your installworld
996 will break because a symbol version-less libc will get installed
997 before the install tools. As a result, the old install tools,
998 which previously had symbol dependencies to FBSD_1.0, will fail
999 because the freshly installed libc will not have them.
1001 The default threading library (providing "libpthread") has been
1002 changed to libthr. If you wish to have libkse as your default,
1003 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
1006 The ABI breakage in sendmail(8)'s libmilter has been repaired
1007 so it is no longer necessary to recompile mail filters (aka,
1008 milters). If you recompiled mail filters after the 20070408
1009 note, it is not necessary to recompile them again.
1012 The new trunk(4) driver has been renamed to lagg(4) as it better
1013 reflects its purpose. ifconfig will need to be recompiled.
1016 sendmail(8) has been updated to version 8.14.1. Mail filters
1017 (aka, milters) compiled against the libmilter included in the
1018 base operating system should be recompiled.
1021 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
1022 In order to use them one must agree to the respective LICENSE in
1023 share/doc/legal and define legal.intel_<name>.license_ack=1 via
1024 loader.conf(5) or kenv(1). Make sure to deinstall the now
1025 deprecated modules from the respective firmware ports.
1028 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
1029 were removed from FreeBSD's libc. These originally came from INRIA
1030 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
1031 deprecated in previous releases.
1032 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
1033 replace it as a more portable (and re-entrant) API.
1036 To support interrupt filtering a modification to the newbus API
1037 has occurred, ABI was broken and __FreeBSD_version was bumped
1038 to 700031. Please make sure that your kernel and modules are in
1039 sync. For more info:
1040 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
1043 The IPv6 multicast forwarding code may now be loaded into GENERIC
1044 kernels by loading the ip_mroute.ko module. This is built into the
1045 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
1046 set; see src.conf(5) for more information.
1049 The output of netstat -r has changed. Without -n, we now only
1050 print a "network name" without the prefix length if the network
1051 address and mask exactly match a Class A/B/C network, and an entry
1052 exists in the nsswitch "networks" map.
1053 With -n, we print the full unabbreviated CIDR network prefix in
1054 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
1055 This change is in preparation for changes such as equal-cost
1056 multipath, and to more generally assist operational deployment
1057 of FreeBSD as a modern IPv4 router.
1060 PIM has been turned on by default in the IPv4 multicast
1061 routing code. The kernel option 'PIM' has now been removed.
1062 PIM is now built by default if option 'MROUTING' is specified.
1063 It may now be loaded into GENERIC kernels by loading the
1064 ip_mroute.ko module.
1067 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
1068 has been removed. Its functionality may be achieved by explicitly
1069 configuring gif(4) interfaces and using the 'phyint' keyword in
1071 XORP does not support source-routed IPv4 multicast tunnels nor the
1072 integrated IPIP tunneling, therefore it is not affected by this
1073 change. The __FreeBSD_version macro has been bumped to 700030.
1076 Support for PCI Message Signalled Interrupts has been
1077 re-enabled in the bge driver, only for those chips which are
1078 believed to support it properly. If there are any problems,
1079 MSI can be disabled completely by setting the
1080 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
1084 Support for PCI Message Signalled Interrupts has been
1085 disabled again in the bge driver. Many revisions of the
1086 hardware fail to support it properly. Support can be
1087 re-enabled by removing the #define of BGE_DISABLE_MSI in
1088 "src/sys/dev/bge/if_bge.c".
1091 Support for PCI Message Signalled Interrupts has been added
1092 to the bge driver. If there are any problems, MSI can be
1093 disabled completely by setting the 'hw.pci.enable_msi' and
1094 'hw.pci.enable_msix' tunables to 0 in the loader.
1097 The removal of several facets of the experimental Threading
1098 system from the kernel means that the proc and thread structures
1099 have changed quite a bit. I suggest all kernel modules that might
1100 reference these structures be recompiled.. Especially the
1104 Sound infrastructure has been updated with various fixes and
1105 improvements. Most of the changes are pretty much transparent,
1106 with exceptions of followings:
1107 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
1108 moved to their own dev sysctl nodes, for example:
1109 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
1110 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
1111 own chardev in the form of "dsp%d.<function>%d", where <function>
1112 is p = playback, r = record and v = virtual, respectively. Users
1113 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
1114 This does not affect those who are using "/dev/dsp".
1117 geom(4)'s gmirror(8) class metadata structure has been
1118 rev'd from v3 to v4. If you update across this point and
1119 your metadata is converted for you, you will not be easily
1120 able to downgrade since the /boot/kernel.old/geom_mirror.ko
1121 kernel module will be unable to read the v4 metadata. You
1122 can resolve this by doing from the loader(8) prompt:
1124 set vfs.root.mountfrom="ufs:/dev/XXX"
1126 where XXX is the root slice of one of the disks that composed
1127 the mirror (i.e.: /dev/ad0s1a). You can then rebuild
1128 the array the same way you built it originally.
1131 The following binaries have been disconnected from the build:
1132 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
1133 and mount_std. The functionality of these programs has been
1134 moved into the mount program. For example, to mount a devfs
1135 filesystem, instead of using mount_devfs, use: "mount -t devfs".
1136 This does not affect entries in /etc/fstab, since entries in
1137 /etc/fstab are always processed with "mount -t fstype".
1140 Support for PCI Message Signalled Interrupts on i386 and amd64
1141 has been added to the kernel and various drivers will soon be
1142 updated to use MSI when it is available. If there are any problems,
1143 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
1144 and 'hw.pci.enable_msix' tunables to 0 in the loader.
1147 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
1148 The lockmgr object layout has been changed as a result of having
1149 a lock_object embedded in it. As a consequence all file system
1150 kernel modules must be re-compiled. The mutex profiling man page
1151 has not yet been updated to reflect this change.
1154 KSE in the kernel has now been made optional and turned on by
1155 default. Use 'nooption KSE' in your kernel config to turn it
1156 off. All kernel modules *must* be recompiled after this change.
1157 There-after, modules from a KSE kernel should be compatible with
1158 modules from a NOKSE kernel due to the temporary padding fields
1159 added to 'struct proc'.
1162 mrouted and its utilities have been removed from the base system.
1165 Some ioctl(2) command codes have changed. Full backward ABI
1166 compatibility is provided if the "options COMPAT_FREEBSD6" is
1167 present in the kernel configuration file. Make sure to add
1168 this option to your kernel config file, or recompile X.Org
1169 and the rest of ports; otherwise they may refuse to work.
1172 tcpslice has been removed from the base system.
1175 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
1176 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
1177 systat needs to be rebuilt.
1180 libpcap updated to v0.9.4 and tcpdump to v3.9.4
1183 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
1184 for IPFIREWALL_FORWARD is now as it was before when it was first
1185 committed and for years after. The behaviour is now ON.
1188 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
1189 Now it can decrypt files created from different architectures.
1190 Unfortunately, it is no longer able to decrypt a cipher text
1191 generated with an older version on 64 bit architectures.
1192 If you have such a file, you need old utility to decrypt it.
1195 The interface version of the i4b kernel part has changed. So
1196 after updating the kernel sources and compiling a new kernel,
1197 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
1198 be rebuilt, and vice versa.
1201 The XBOX kernel now defaults to the nfe(4) driver instead of
1202 the nve(4) driver. Please update your configuration
1206 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
1207 PCnet family of NICs has been removed. The new le(4) driver serves
1208 as an equivalent but cross-platform replacement with the pcn(4)
1209 driver still providing performance-optimized support for the subset
1210 of AMD Am79C971 PCnet-FAST and greater chips as before.
1213 The machdep.* sysctls and the adjkerntz utility have been
1214 modified a bit. The new adjkerntz utility uses the new
1215 sysctl names and sysctlbyname() calls, so it may be impossible
1216 to run an old /sbin/adjkerntz utility in single-user mode
1217 with a new kernel. Replace the `adjkerntz -i' step before
1218 `make installworld' with:
1220 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
1222 and proceed as usual with the rest of the installworld-stage
1223 steps. Otherwise, you risk installing binaries with their
1224 timestamp set several hours in the future, especially if
1225 you are running with local time set to GMT+X hours.
1228 The ip6fw utility has been removed. The behavior provided by
1229 ip6fw has been in ipfw2 for a good while and the rc.d scripts
1230 have been updated to deal with it. There are some rules that
1231 might not migrate cleanly. Use rc.firewall6 as a template to
1235 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
1236 attachments have been removed. Make sure to configure scc(4)
1237 on sparc64. Note also that by default puc(4) will use uart(4)
1238 and not sio(4) for serial ports because interrupt handling has
1239 been optimized for multi-port serial cards and only uart(4)
1240 implements the interface to support it.
1243 The scc(4) driver replaces puc(4) for Serial Communications
1244 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
1245 Z8530. On sparc64, it is advised to add scc(4) to the kernel
1246 configuration to make sure that the serial ports remain
1250 Most world/kernel related NO_* build options changed names.
1251 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
1252 after FreeBSD ports) and should be set in /etc/src.conf
1253 (the src.conf(5) manpage is provided). Full backwards
1254 compatibility is maintained for the time being though it's
1255 highly recommended to start moving old options out of the
1256 system-wide /etc/make.conf file into the new /etc/src.conf
1257 while also properly renaming them. More conversions will
1258 likely follow. Posting to current@:
1260 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
1263 The NETSMBCRYPTO kernel option has been retired because its
1264 functionality is always included in NETSMB and smbfs.ko now.
1267 The TDFX_LINUX kernel option was retired and replaced by the
1268 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
1269 kernel module. Loading it alone should suffice to get 3dfx support
1270 for Linux apps because it will pull in 3dfx.ko and linux.ko through
1274 The 'audit' group was added to support the new auditing functionality
1275 in the base system. Be sure to follow the directions for updating,
1276 including the requirement to run mergemaster -p.
1279 The kernel ABI to file system modules was changed on i386.
1280 Please make sure that your kernel and modules are in sync.
1283 This actually occured some time ago, but installing the kernel
1284 now also installs a bunch of symbol files for the kernel modules.
1285 This increases the size of /boot/kernel to about 67Mbytes. You
1286 will need twice this if you will eventually back this up to kernel.old
1287 on your next install.
1288 If you have a shortage of room in your root partition, you should add
1289 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
1290 to your /etc/make.conf.
1293 libc's malloc implementation has been replaced. This change has the
1294 potential to uncover application bugs that previously went unnoticed.
1295 See the malloc(3) manual page for more details.
1298 The generic netgraph(4) cookie has been changed. If you upgrade
1299 kernel passing this point, you also need to upgrade userland
1300 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
1303 si(4)'s device files now contain the unit number.
1304 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
1307 The kernel ABI was mostly destroyed due to a change in the size
1308 of struct lock_object which is nested in other structures such
1309 as mutexes which are nested in all sorts of other structures.
1310 Make sure your kernel and modules are in sync.
1313 The page coloring algorithm in the VM subsystem was converted
1314 from tuning with kernel options to autotuning. Please remove
1315 any PQ_* option except PQ_NOOPT from your kernel config.
1318 The net80211-related tools in the tools/tools/ath directory
1319 have been moved to tools/tools/net80211 and renamed with a
1320 "wlan" prefix. Scripts that use them should be adjusted
1324 Scripts in the local_startup directories (as defined in
1325 /etc/defaults/rc.conf) that have the new rc.d semantics will
1326 now be run as part of the base system rcorder. If there are
1327 errors or problems with one of these local scripts, it could
1328 cause boot problems. If you encounter such problems, boot in
1329 single user mode, remove that script from the */rc.d directory.
1330 Please report the problem to the port's maintainer, and the
1331 freebsd-ports@freebsd.org mailing list.
1334 The nodev mount option was deprecated in RELENG_6 (where it
1335 was a no-op), and is now unsupported. If you have nodev or dev listed
1336 in /etc/fstab, remove it, otherwise it will result in a mount error.
1339 ABI between ipfw(4) and ipfw(8) has been changed. You need
1340 to rebuild ipfw(8) when rebuilding kernel.
1343 rp(4)'s device files now contain the unit number.
1344 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
1347 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
1348 Its /etc/rc.conf.d configuration file has been `ppp' from
1349 the beginning, and hence there is no need to touch it.
1352 Now most modules get their build-time options from the kernel
1353 configuration file. A few modules still have fixed options
1354 due to their non-conformant implementation, but they will be
1355 corrected eventually. You may need to review the options of
1356 the modules in use, explicitly specify the non-default options
1357 in the kernel configuration file, and rebuild the kernel and
1361 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
1362 to turn polling(4) on your interfaces.
1365 The old bridge(4) implementation was retired. The new
1366 if_bridge(4) serves as a full functional replacement.
1369 The ai_addrlen of a struct addrinfo was changed to a socklen_t
1370 to conform to POSIX-2001. This change broke an ABI
1371 compatibility on 64 bit architecture. You have to recompile
1372 userland programs that use getaddrinfo(3) on 64 bit
1376 RELENG_6 branched here.
1379 The pccard_ifconfig rc.conf variable has been removed and a new
1380 variable, ifconfig_DEFAULT has been introduced. Unlike
1381 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
1382 do not have ifconfig_ifn entries rather than just those in
1383 removable_interfaces.
1386 Some previous versions of PAM have permitted the use of
1387 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
1388 to third party PAM modules in /usr/local/lib. A change has been
1389 made to require the use of absolute paths in order to avoid
1390 ambiguity and dependence on library path configuration, which may
1391 affect existing configurations.
1394 Major changes to network interface API. All drivers must be
1395 recompiled. Drivers not in the base system will need to be
1396 updated to the new APIs.
1399 Changes were made to kinfo_proc in sys/user.h. Please recompile
1400 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
1401 will not behave correctly.
1403 The API and ABI for hwpmc(4) have changed with the addition
1404 of sampling support. Please recompile lib/libpmc(3) and
1405 usr.sbin/{pmcstat,pmccontrol}.
1408 The OpenBSD dhclient was imported in place of the ISC dhclient
1409 and the network interface configuration scripts were updated
1410 accordingly. If you use DHCP to configure your interfaces, you
1411 must now run devd. Also, DNS updating was lost so you will need
1412 to find a workaround if you use this feature.
1414 The '_dhcp' user was added to support the OpenBSD dhclient. Be
1415 sure to run mergemaster -p (like you are supposed to do every time
1419 if_bridge was added to the tree. This has changed struct ifnet.
1420 Please recompile userland and all network related modules.
1423 The n_net of a struct netent was changed to an uint32_t, and
1424 1st argument of getnetbyaddr() was changed to an uint32_t, to
1425 conform to POSIX-2001. These changes broke an ABI
1426 compatibility on 64 bit architecture. With these changes,
1427 shlib major of libpcap was bumped. You have to recompile
1428 userland programs that use getnetbyaddr(3), getnetbyname(3),
1429 getnetent(3) and/or libpcap on 64 bit architecture.
1432 Kernel parsing of extra options on '#!' first lines of shell
1433 scripts has changed. Lines with multiple options likely will
1434 fail after this date. For full details, please see
1435 http://people.freebsd.org/~gad/Updating-20050528.txt
1438 The packet filter (pf) code has been updated to OpenBSD 3.7
1439 Please note the changed anchor syntax and the fact that
1440 authpf(8) now needs a mounted fdescfs(5) to function.
1443 The NO_MIXED_MODE kernel option has been removed from the i386
1444 amd64 platforms as its use has been superceded by the new local
1445 APIC timer code. Any kernel config files containing this option
1449 The on-disk format of LC_CTYPE files was changed to be machine
1450 independent. Please make sure NOT to use NO_CLEAN buildworld
1451 when crossing this point. Crossing this point also requires
1452 recompile or reinstall of all locale depended packages.
1455 The ifi_epoch member of struct if_data has been changed to
1456 contain the uptime at which the interface was created or the
1457 statistics zeroed rather then the wall clock time because
1458 wallclock time may go backwards. This should have no impact
1459 unless an snmp implementation is using this value (I know of
1460 none at this point.)
1463 The acpi_perf and acpi_throttle drivers are now part of the
1464 acpi(4) main module. They are no longer built separately.
1467 The layout of struct image_params has changed. You have to
1468 recompile all compatibility modules (linux, svr4, etc) for use
1469 with the new kernel.
1472 The p4tcc driver has been merged into cpufreq(4). This makes
1473 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
1474 compile in "device cpufreq" to restore this functionality.
1477 The responsibility of recomputing the file system summary of
1478 a SoftUpdates-enabled dirty volume has been transferred to the
1479 background fsck. A rebuild of fsck(8) utility is recommended
1480 if you have updated the kernel.
1482 To get the old behavior (recompute file system summary at mount
1483 time), you can set vfs.ffs.compute_summary_at_mount=1 before
1484 mounting the new volume.
1487 The cpufreq import is complete. As part of this, the sysctls for
1488 acpi(4) throttling have been removed. The power_profile script
1489 has been updated, so you can use performance/economy_cpu_freq in
1490 rc.conf(5) to set AC on/offline cpu frequencies.
1493 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
1494 requires recompiling libnetgraph and userland netgraph utilities.
1497 Support for abbreviated forms of a number of ipfw options is
1498 now deprecated. Warnings are printed to stderr indicating the
1499 correct full form when a match occurs. Some abbreviations may
1500 be supported at a later date based on user feedback. To be
1501 considered for support, abbreviations must be in use prior to
1502 this commit and unlikely to be confused with current key words.
1505 By a popular demand, a lot of NOFOO options were renamed
1506 to NO_FOO (see bsd.compat.mk for a full list). The old
1507 spellings are still supported, but will cause annoying
1508 warnings on stderr. Make sure you upgrade properly (see
1509 the COMMON ITEMS: section later in this file).
1512 Auto-loading of ancillary wlan modules such as wlan_wep has
1513 been temporarily disabled; you need to statically configure
1514 the modules you need into your kernel or explicitly load them
1515 prior to use. Specifically, if you intend to use WEP encryption
1516 with an 802.11 device load/configure wlan_wep; if you want to
1517 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
1518 and wlan_xauth as required.
1521 The behaviour of ppp(8) has changed slightly. If lqr is enabled
1522 (``enable lqr''), older versions would revert to LCP ECHO mode on
1523 negotiation failure. Now, ``enable echo'' is required for this
1524 behaviour. The ppp version number has been bumped to 3.4.2 to
1528 The wlan support has been updated to split the crypto support
1529 into separate modules. For static WEP you must configure the
1530 wlan_wep module in your system or build and install the module
1531 in place where it can be loaded (the kernel will auto-load
1532 the module when a wep key is configured).
1535 The ath driver has been updated to split the tx rate control
1536 algorithm into a separate module. You need to include either
1537 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
1540 Support for systems with an 80386 CPU has been removed. Please
1541 use FreeBSD 5.x or earlier on systems with an 80386.
1544 We have had a hack which would mount the root filesystem
1545 R/W if the device were named 'md*'. As part of the vnode
1546 work I'm doing I have had to remove this hack. People
1547 building systems which use preloaded MD root filesystems
1548 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
1549 their /etc/rc scripts.
1552 FreeBSD 5.3 shipped here.
1555 The size of struct tcpcb has changed again due to the removal
1556 of RFC1644 T/TCP. You have to recompile userland programs that
1557 read kmem for tcp sockets directly (netstat, sockstat, etc.)
1560 The size of struct tcpcb has changed. You have to recompile
1561 userland programs that read kmem for tcp sockets directly
1562 (netstat, sockstat, etc.)
1565 RELENG_5 branched here. For older entries, please see updating
1566 in the RELENG_5 branch.
1572 Avoid using make -j when upgrading. From time to time in the
1573 past there have been problems using -j with buildworld and/or
1574 installworld. This is especially true when upgrading between
1575 "distant" versions (eg one that cross a major release boundary
1576 or several minor releases, or when several months have passed
1577 on the -current branch).
1579 Sometimes, obscure build problems are the result of environment
1580 poisoning. This can happen because the make utility reads its
1581 environment when searching for values for global variables.
1582 To run your build attempts in an "environmental clean room",
1583 prefix all make commands with 'env -i '. See the env(1) manual
1584 page for more details.
1586 When upgrading from one major version to another it is generally
1587 best to upgrade to the latest code in the currently installed branch
1588 first, then do an upgrade to the new branch. This is the best-tested
1589 upgrade path, and has the highest probability of being successful.
1590 Please try this approach before reporting problems with a major
1595 When upgrading the boot ZFS pool to a new version, always follow
1598 1.) recompile and reinstall the ZFS boot loader and boot block
1599 (this is part of "make buildworld" and "make installworld")
1601 2.) update the ZFS boot block on your boot drive
1603 The following example updates the ZFS boot block on the first
1604 partition (freebsd-boot) of a GPT partitioned drive ad0:
1605 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1607 Non-boot pools do not need these updates.
1611 If you are updating from a prior version of FreeBSD (even one just
1612 a few days old), you should follow this procedure. It is the most
1613 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1615 make kernel-toolchain
1616 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1617 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1619 To test a kernel once
1620 ---------------------
1621 If you just want to boot a kernel once (because you are not sure
1622 if it works, or if you want to boot a known bad kernel to provide
1623 debugging information) run
1624 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1625 nextboot -k testkernel
1627 To just build a kernel when you know that it won't mess you up
1628 --------------------------------------------------------------
1629 This assumes you are already running a 5.X system. Replace
1630 ${arch} with the architecture of your machine (e.g. "i386",
1631 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1633 cd src/sys/${arch}/conf
1634 config KERNEL_NAME_HERE
1635 cd ../compile/KERNEL_NAME_HERE
1640 If this fails, go to the "To build a kernel" section.
1642 To rebuild everything and install it on the current system.
1643 -----------------------------------------------------------
1644 # Note: sometimes if you are running current you gotta do more than
1645 # is listed here if you are upgrading from a really old current.
1647 <make sure you have good level 0 dumps>
1649 make kernel KERNCONF=YOUR_KERNEL_HERE
1651 <reboot in single user> [3]
1659 To cross-install current onto a separate partition
1660 --------------------------------------------------
1661 # In this approach we use a separate partition to hold
1662 # current's root, 'usr', and 'var' directories. A partition
1663 # holding "/", "/usr" and "/var" should be about 2GB in
1666 <make sure you have good level 0 dumps>
1669 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1670 <maybe newfs current's root partition>
1671 <mount current's root partition on directory ${CURRENT_ROOT}>
1672 make installworld DESTDIR=${CURRENT_ROOT}
1673 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1674 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1675 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1676 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1677 <reboot into current>
1678 <do a "native" rebuild/install as described in the previous section>
1679 <maybe install compatibility libraries from ports/misc/compat*>
1683 To upgrade in-place from 5.x-stable to current
1684 ----------------------------------------------
1685 <make sure you have good level 0 dumps>
1687 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1689 <reboot in single user> [3]
1696 Make sure that you've read the UPDATING file to understand the
1697 tweaks to various things you need. At this point in the life
1698 cycle of current, things change often and you are on your own
1699 to cope. The defaults can also change, so please read ALL of
1700 the UPDATING entries.
1702 Also, if you are tracking -current, you must be subscribed to
1703 freebsd-current@freebsd.org. Make sure that before you update
1704 your sources that you have read and understood all the recent
1705 messages there. If in doubt, please track -stable which has
1706 much fewer pitfalls.
1708 [1] If you have third party modules, such as vmware, you
1709 should disable them at this point so they don't crash your
1712 [3] From the bootblocks, boot -s, and then do
1717 adjkerntz -i # if CMOS is wall time
1718 Also, when doing a major release upgrade, it is required that
1719 you boot into single user mode to do the installworld.
1721 [4] Note: This step is non-optional. Failure to do this step
1722 can result in a significant reduction in the functionality of the
1723 system. Attempting to do it by hand is not recommended and those
1724 that pursue this avenue should read this file carefully, as well
1725 as the archives of freebsd-current and freebsd-hackers mailing lists
1726 for potential gotchas.
1728 [5] Usually this step is a noop. However, from time to time
1729 you may need to do this if you get unknown user in the following
1730 step. It never hurts to do it all the time. You may need to
1731 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1732 install) after the buildworld before this step if you last updated
1733 from current before 20020224 or from -stable before 20020408.
1735 [8] In order to have a kernel that can run the 4.x binaries
1736 needed to do an installworld, you must include the COMPAT_FREEBSD4
1737 option in your kernel. Failure to do so may leave you with a system
1738 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
1739 is required to run the 5.x binaries on more recent kernels.
1741 Make sure that you merge any new devices from GENERIC since the
1742 last time you updated your kernel config file.
1744 [9] When checking out sources, you must include the -P flag to have
1745 cvs prune empty directories.
1747 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1748 "?=" instead of the "=" assignment operator, so that buildworld can
1749 override the CPUTYPE if it needs to.
1751 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1752 not on the command line, or in /etc/make.conf. buildworld will
1753 warn if it is improperly defined.
1756 This file contains a list, in reverse chronological order, of major
1757 breakages in tracking -current. Not all things will be listed here,
1758 and it only starts on October 16, 2004. Updating files can found in
1759 previous releases if your system is older than this.
1761 Copyright information:
1763 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
1765 Redistribution, publication, translation and use, with or without
1766 modification, in full or in part, in any form or format of this
1767 document are permitted without further permission from the author.
1769 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1770 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1771 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1772 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1773 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1774 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1775 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1776 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1777 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1778 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1779 POSSIBILITY OF SUCH DAMAGE.
1781 If you find this document useful, and you want to, you may buy the
1784 Contact Warner Losh if you have any questions about your use of