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