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 20100713: p4 FreeBSD-SA-10:07.mbuf
19 Correctly copy the M_RDONLY flag when duplicating a reference
20 to an mbuf external buffer.
22 20100526: p3 FreeBSD-SA-10:04.jail, FreeBSD-SA-10:05.opie,
23 FreeBSD-SA-10:06.nfsclient
24 Change the current working directory to be inside the jail created by
25 the jail(8) command. [10:04]
27 Fix a one-NUL-byte buffer overflow in libopie. [10:05]
29 Correctly sanity-check a buffer length in nfs mount. [10:06]
31 20100106: p2 FreeBSD-SA-10:01.bind, FreeBSD-SA-10:02.ntpd,
32 FreeBSD-SA-10:03.zfs, FreeBSD-EN-10:01.freebsd
33 Fix BIND named(8) cache poisoning with DNSSEC validation.
36 Fix ntpd mode 7 denial of service. [SA-10:02]
38 Fix ZFS ZIL playback with insecure permissions. [SA-10:03]
40 Various FreeBSD 8.0-RELEASE improvements. [EN-10:01]
42 20091203: p1 FreeBSD-SA-09:15.ssl, FreeBSD-SA-09:16.rtld,
43 FreeBSD-SA-09:17.freebsd-update
44 Disable SSL renegotiation in order to protect against a serious
45 protocol flaw. [09:15]
47 Correctly handle failures from unsetenv resulting from a corrupt
48 environment in rtld-elf. [09:16]
50 Fix permissions in freebsd-update in order to prevent leakage of
51 sensitive files. [09:17]
57 802.11s D3.03 support was committed. This is incompatible with
58 the previous code, which was based on D3.0.
61 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
62 mount(8) and -a option for df(1) to see them.
65 Remove the option STOP_NMI. The default action is now to use NMI
66 only for KDB via the newly introduced function stop_cpus_hard()
67 and maintain stop_cpus() to just use a normal IPI_STOP on ia32
74 Bump the shared library version numbers for all libraries that
75 do not use symbol versioning as part of the 8.0-RELEASE cycle.
76 Bump __FreeBSD_version to 800105.
79 Due to changes in the implementation of virtual network stack
80 support, all network-related kernel modules must be recompiled.
81 As this change breaks the ABI, bump __FreeBSD_version to 800104.
84 The TOE interface to the TCP syncache has been modified to remove struct
85 tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack. The
86 cxgb driver is the only TOE consumer affected by this change, and needs
87 to be recompiled along with the kernel. As this change breaks the ABI,
88 bump __FreeBSD_version to 800103.
91 Padding has been added to struct tcpcb, sackhint and tcpstat in
92 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
93 maintainig the ABI. However, this change breaks the ABI, so bump
94 __FreeBSD_version to 800102. User space tools that rely on the size of
95 any of these structs (e.g. sockstat) need to be recompiled.
98 The NFS_LEGACYRPC option has been removed along with the old
99 kernel RPC implementation that this option selected. Kernel
100 configurations may need to be adjusted.
103 The network interface device nodes at /dev/net/<interface> have
104 been removed. All ioctl operations can be performed the normal
105 way using routing sockets. The kqueue functionality can
106 generally be replaced with routing sockets.
109 The documentation from the FreeBSD Documentation Project
110 (Handbook, FAQ, etc.) is now installed via packages by
111 sysinstall(8) and under the /usr/local/share/doc/freebsd
112 directory instead of /usr/share/doc.
115 The ABI of various structures related to the SYSV IPC API have
116 been changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43
117 kernel options now all require COMPAT_FREEBSD7.
118 Bump __FreeBSD_version to 800100.
121 Layout of struct vnet has changed as routing related variables
122 were moved to their own Vimage module. Modules need to be
123 recompiled. Bump __FreeBSD_version to 800099.
126 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023
127 and 1024 respectively. As long as no more than 16 groups per
128 process are used, no changes should be visible. When more
129 than 16 groups are used, old binaries may fail if they call
130 getgroups() or getgrouplist() with statically sized storage.
131 Recompiling will work around this, but applications should be
132 modified to use dynamically allocated storage for group arrays
133 as POSIX.1-2008 does not cap an implementation's number of
134 supported groups at NGROUPS_MAX+1 as previous versions did.
136 NFS and portalfs mounts may also be affected as the list of
137 groups is truncated to 16. Users of NFS who use more than 16
138 groups, should take care that negative group permissions are not
139 used on the exported file systems as they will not be reliable
140 unless a GSSAPI based authentication method is used.
143 The compiling option ADAPTIVE_LOCKMGRS has been introduced.
144 This option compiles in the support for adaptive spinning for lockmgrs
145 which want to enable it. The lockinit() function now accepts the
146 flag LK_ADAPTIVE in order to make the lock object subject to
147 adaptive spinning when both held in write and read mode.
150 The layout of the structure returned by IEEE80211_IOC_STA_INFO
151 has changed. User applications that use this ioctl need to be
155 The layout of struct thread has changed. Kernel and modules
159 The layout of structs ifnet, domain, protosw and vnet_net has
160 changed. Kernel modules need to be rebuilt.
161 Bump __FreeBSD_version to 800097.
164 window(1) has been removed from the base system. It can now be
165 installed from ports. The port is called misc/window.
168 The way we are storing and accessing `routing table' entries
169 has changed. Programs reading the FIB, like netstat, need to
173 A new netisr implementation has been added for FreeBSD 8. Network
174 file system modules, such as igmp, ipdivert, and others, should be
176 Bump __FreeBSD_version to 800096.
179 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose
183 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
184 Bump __FreeBSD_version to 800094.
187 Add mnt_xflag field to 'struct mount'. File system modules
189 Bump __FreeBSD_version to 800093.
192 The compiling option ADAPTIVE_SX has been retired while it has been
193 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
194 The KPI for sx_init_flags() changes as accepting flags:
195 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag
196 has been introduced in order to handle the reversed logic.
197 Bump __FreeBSD_version to 800092.
200 Add support for hierarchical jails. Remove global securelevel.
201 Bump __FreeBSD_version to 800091.
204 The layout of struct vnet_net has changed, therefore modules
206 Bump __FreeBSD_version to 800090.
209 The newly imported zic(8) produces a new format in the
210 output. Please run tzsetup(8) to install the newly created
211 data to /etc/localtime.
214 The sysctl tree for the usb stack has renamed from hw.usb2.* to
215 hw.usb.* and is now consistent again with previous releases.
218 802.11 monitor mode support was revised and driver api's
219 were changed. Drivers dependent on net80211 now support
220 DLT_IEEE802_11_RADIO instead of DLT_IEEE802_11. No
221 user-visible data structures were changed but applications
222 that use DLT_IEEE802_11 may require changes.
223 Bump __FreeBSD_version to 800088.
226 The layout of the following structs has changed: sysctl_oid,
227 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
228 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
229 panics may be experienced. World rebuild is required for
230 correctly checking networking state from userland.
231 Bump __FreeBSD_version to 800085.
234 MLDv2 and Source-Specific Multicast (SSM) have been merged
235 to the IPv6 stack. VIMAGE hooks are in but not yet used.
236 The implementation of SSM within FreeBSD's IPv6 stack closely
237 follows the IPv4 implementation.
239 For kernel developers:
241 * The most important changes are that the ip6_output() and
242 ip6_input() paths no longer take the IN6_MULTI_LOCK,
243 and this lock has been downgraded to a non-recursive mutex.
245 * As with the changes to the IPv4 stack to support SSM, filtering
246 of inbound multicast traffic must now be performed by transport
247 protocols within the IPv6 stack. This does not apply to TCP and
248 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
250 * The KPIs used by IPv6 multicast are similar to those used by
251 the IPv4 stack, with the following differences:
252 * im6o_mc_filter() is analogous to imo_multicast_filter().
253 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
254 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
255 * IN6_LOOKUP_MULTI() has been deprecated and removed.
256 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
257 for MLDv1 have an additional 'timer' argument which is used to
258 jitter the initial membership report for the solicited-node
259 multicast membership on-link.
260 * This is not strictly needed for MLDv2, which already jitters
261 its report transmissions. However, the 'timer' argument is
262 preserved in case MLDv1 is active on the interface.
264 * The KAME linked-list based IPv6 membership implementation has
265 been refactored to use a vector similar to that used by the IPv4
267 Code which maintains a list of its own multicast memberships
268 internally, e.g. carp, has been updated to reflect the new
271 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
272 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
273 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
274 implementation constraint which needs to be addressed in HEAD.
276 For application developers:
278 * The changes are broadly similar to those made for the IPv4
281 * The use of IPv4 and IPv6 multicast socket options on the same
282 socket, using mapped addresses, HAS NOT been tested or supported.
284 * There are a number of issues with the implementation of various
285 IPv6 multicast APIs which need to be resolved in the API surface
286 before the implementation is fully compatible with KAME userland
287 use, and these are mostly to do with interface index treatment.
289 * The literature available discusses the use of either the delta / ASM
290 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
291 using setsourcefilter(3)/getsourcefilter(3). For more information
292 please refer to RFC 3768, 'Socket Interface Extensions for
293 Multicast Source Filters'.
295 * Applications which use the published RFC 3678 APIs should be fine.
297 For systems administrators:
299 * The mtest(8) utility has been refactored to support IPv6, in
300 addition to IPv4. Interface addresses are no longer accepted
301 as arguments, their names must be used instead. The utility
302 will map the interface name to its first IPv4 address as
303 returned by getifaddrs(3).
305 * The ifmcstat(8) utility has also been updated to print the MLDv2
306 endpoint state and source filter lists via sysctl(3).
308 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
309 loopback of IPv6 multicast datagrams by default; it defaults to 1
310 to preserve the existing behaviour. Disabling multicast loopback is
311 recommended for optimal system performance.
313 * The IPv6 MROUTING code has been changed to examine this sysctl
314 instead of attempting to perform a group lookup before looping
315 back forwarded datagrams.
317 Bump __FreeBSD_version to 800084.
320 Implement low-level Bluetooth HCI API.
321 Bump __FreeBSD_version to 800083.
324 The layout of struct malloc_type, used by modules to register new
325 memory allocation types, has changed. Most modules will need to
326 be rebuilt or panics may be experienced.
327 Bump __FreeBSD_version to 800081.
330 Anticipate overflowing inp_flags - add inp_flags2.
331 This changes most offsets in inpcb, so checking v4 connection
332 state will require a world rebuild.
333 Bump __FreeBSD_version to 800080.
336 Add an llentry to struct route and struct route_in6. Modules
337 embedding a struct route will need to be recompiled.
338 Bump __FreeBSD_version to 800079.
341 The size of rt_metrics_lite and by extension rtentry has changed.
342 Networking administration apps will need to be recompiled.
343 The route command now supports show as an alias for get, weighting
344 of routes, sticky and nostick flags to alter the behavior of stateful
346 Bump __FreeBSD_version to 800078.
349 Do not use Giant for kbdmux(4) locking. This is wrong and
350 apparently causing more problems than it solves. This will
351 re-open the issue where interrupt handlers may race with
352 kbdmux(4) in polling mode. Typical symptoms include (but
353 not limited to) duplicated and/or missing characters when
354 low level console functions (such as gets) are used while
355 interrupts are enabled (for example geli password prompt,
356 mountroot prompt etc.). Disabling kbdmux(4) may help.
359 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
360 kernel modules referencing any of the above need to be recompiled.
361 Bump __FreeBSD_version to 800075.
364 GEOM_PART has become the default partition slicer for storage devices,
365 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
366 introduces some changes:
368 MSDOS/EBR: the devices created from MSDOS extended partition entries
369 (EBR) can be named differently than with GEOM_MBR and are now symlinks
370 to devices with offset-based names. fstabs may need to be modified.
372 BSD: the "geometry does not match label" warning is harmless in most
373 cases but it points to problems in file system misalignment with
374 disk geometry. The "c" partition is now implicit, covers the whole
375 top-level drive and cannot be (mis)used by users.
377 General: Kernel dumps are now not allowed to be written to devices
378 whose partition types indicate they are meant to be used for file
379 systems (or, in case of MSDOS partitions, as something else than
382 Most of these changes date approximately from 200812.
385 The uscanner(4) driver has been removed from the kernel. This follows
386 Linux removing theirs in 2.6 and making libusb the default interface
390 The multicast forwarding code has been cleaned up. netstat(1)
391 only relies on KVM now for printing bandwidth upcall meters.
392 The IPv4 and IPv6 modules are split into ip_mroute_mod and
393 ip6_mroute_mod respectively. The config(5) options for statically
394 compiling this code remain the same, i.e. 'options MROUTING'.
397 Support for the IFF_NEEDSGIANT network interface flag has been
398 removed, which means that non-MPSAFE network device drivers are no
399 longer supported. In particular, if_ar, if_sr, and network device
400 drivers from the old (legacy) USB stack can no longer be built or
404 POSIX.1 Native Language Support (NLS) has been enabled in libc and
405 a bunch of new language catalog files have also been added.
406 This means that some common libc messages are now localized and
407 they depend on the LC_MESSAGES environmental variable.
410 The k8temp(4) driver has been renamed to amdtemp(4) since
411 support for K10 and K11 CPU families was added.
414 IGMPv3 and Source-Specific Multicast (SSM) have been merged
415 to the IPv4 stack. VIMAGE hooks are in but not yet used.
417 For kernel developers, the most important changes are that the
418 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
419 and this lock has been downgraded to a non-recursive mutex.
421 Transport protocols (UDP, Raw IP) are now responsible for filtering
422 inbound multicast traffic according to group membership and source
423 filters. The imo_multicast_filter() KPI exists for this purpose.
424 Transports which do not use multicast (SCTP, TCP) already reject
425 multicast by default. Forwarding and receive performance may improve
426 as a mutex acquisition is no longer needed in the ip_input()
427 low-level input path. in_addmulti() and in_delmulti() are shimmed
428 to new KPIs which exist to support SSM in-kernel.
430 For application developers, it is recommended that loopback of
431 multicast datagrams be disabled for best performance, as this
432 will still cause the lock to be taken for each looped-back
433 datagram transmission. The net.inet.ip.mcast.loop sysctl may
434 be tuned to 0 to disable loopback by default; it defaults to 1
435 to preserve the existing behaviour.
437 For systems administrators, to obtain best performance with
438 multicast reception and multiple groups, it is always recommended
439 that a card with a suitably precise hash filter is used. Hash
440 collisions will still result in the lock being taken within the
441 transport protocol input path to check group membership.
443 If deploying FreeBSD in an environment with IGMP snooping switches,
444 it is recommended that the net.inet.igmp.sendlocal sysctl remain
445 enabled; this forces 224.0.0.0/24 group membership to be announced
448 The size of 'struct igmpstat' has changed; netstat needs to be
449 recompiled to reflect this.
450 Bump __FreeBSD_version to 800070.
453 libusb20.so.1 is now installed as libusb.so.1 and the ports system
454 updated to use it. This requires a buildworld/installworld in order to
455 update the library and dependencies (usbconfig, etc). Its advisable to
456 rebuild all ports which uses libusb. More specific directions are given
457 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
458 libusb are no longer required and can be removed.
461 A workaround is committed to allow the creation of System V shared
462 memory segment of size > 2 GB on the 64-bit architectures.
463 Due to a limitation of the existing ABI, the shm_segsz member
464 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
465 wrong for large segments. Note that limits must be explicitly
466 raised to allow such segments to be created.
469 The layout of struct ifnet has changed, requiring a rebuild of all
470 network device driver modules.
473 The /dev handling for the new USB stack has changed, a
474 buildworld/installworld is required for libusb20.
477 The new USB2 stack has now been permanently moved in and all kernel and
478 module names reverted to their previous values (eg, usb, ehci, ohci,
479 ums, ...). The old usb stack can be compiled in by prefixing the name
480 with the letter 'o', the old usb modules have been removed.
481 Updating entry 20090216 for xorg and 20090215 for libmap may still
485 The rc.conf(5) option if_up_delay has been renamed to
486 defaultroute_delay to better reflect its purpose. If you have
487 customized this setting in /etc/rc.conf you need to update it to
491 xorg 7.4 wants to configure its input devices via hald which does not
492 yet work with USB2. If the keyboard/mouse does not work in xorg then
494 Option "AllowEmptyInput" "off"
495 to your ServerLayout section. This will cause X to use the configured
496 kbd and mouse sections from your xorg.conf.
499 The GENERIC kernels for all architectures now default to the new USB2
500 stack. No kernel config options or code have been removed so if a
501 problem arises please report it and optionally revert to the old USB
502 stack. If you are loading USB kernel modules or have a custom kernel
503 that includes GENERIC then ensure that usb names are also changed over,
504 eg uftdi -> usb2_serial_ftdi.
506 Older programs linked against the ports libusb 0.1 need to be
507 redirected to the new stack's libusb20. /etc/libmap.conf can
509 # Map old usb library to new one for usb2 stack
510 libusb-0.1.so.8 libusb20.so.1
513 The ichsmb(4) driver has been changed to require SMBus slave
514 addresses be left-justified (xxxxxxx0b) rather than right-justified.
515 All of the other SMBus controller drivers require left-justified
516 slave addresses, so this change makes all the drivers provide the
520 INET6 statistics (struct ip6stat) was updated.
521 netstat(1) needs to be recompiled.
524 NTFS has been removed from GENERIC kernel on amd64 to match
525 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
526 will load ntfs.ko module automatically when NTFS support is
527 actually needed, unless ntfs.ko is not installed or security
528 level prohibits loading kernel modules. If either is the case,
529 "options NTFS" has to be added into kernel config.
532 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
533 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
534 800061. User space tools that rely on the size of struct tcpcb in
535 tcp_var.h (e.g. sockstat) need to be recompiled.
538 ng_tty(4) module updated to match the new TTY subsystem.
539 Due to API change, user-level applications must be updated.
540 New API support added to mpd5 CVS and expected to be present
541 in next mpd5.3 release.
544 With __FreeBSD_version 800060 the makefs tool is part of
545 the base system (it was a port).
548 The afdata and ifnet locks have been changed from mutexes to
549 rwlocks, network modules will need to be re-compiled.
552 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
553 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
554 The new code reduced struct rtentry{} by 16 bytes on 32-bit
555 architecture and 40 bytes on 64-bit architecture. The userland
556 applications "arp" and "ndp" have been updated accordingly.
557 The output from "netstat -r" shows only routing entries and
558 none of the L2 information.
561 __FreeBSD_version 800057 marks the switchover from the
562 binary ath hal to source code. Users must add the line:
564 options AH_SUPPORT_AR5416
566 to their kernel config files when specifying:
570 The ath_hal module no longer exists; the code is now compiled
571 together with the driver in the ath module. It is now
572 possible to tailor chip support (i.e. reduce the set of chips
573 and thereby the code size); consult ath_hal(4) for details.
576 __FreeBSD_version 800054 adds memory barriers to
577 <machine/atomic.h>, new interfaces to ifnet to facilitate
578 multiple hardware transmit queues for cards that support
579 them, and a lock-less ring-buffer implementation to
580 enable drivers to more efficiently manage queueing of
584 A new version of ZFS (version 13) has been merged to -HEAD.
585 This version has zpool attribute "listsnapshots" off by
586 default, which means "zfs list" does not show snapshots,
587 and is the same as Solaris behavior.
590 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
593 The uhci, ohci, ehci and slhci USB Host controller drivers have
594 been put into separate modules. If you load the usb module
595 separately through loader.conf you will need to load the
596 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
597 controller add the following to loader.conf:
603 The ABI used by the PMC toolset has changed. Please keep
604 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
608 atapci kernel module now includes only generic PCI ATA
609 driver. AHCI driver moved to ataahci kernel module.
610 All vendor-specific code moved into separate kernel modules:
611 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
612 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
613 atamarvell, atamicron, atanational, atanetcell, atanvidia,
614 atapromise, ataserverworks, atasiliconimage, atasis, atavia
617 The TTY subsystem of the kernel has been replaced by a new
618 implementation, which provides better scalability and an
619 improved driver model. Most common drivers have been migrated to
620 the new TTY subsystem, while others have not. The following
621 drivers have not yet been ported to the new TTY layer:
624 cy, digi, rc, rp, sio
630 ng_h4, ng_tty, ppp, sl, snp
632 Adding these drivers to your kernel configuration file shall
633 cause compilation to fail.
636 ntpd has been upgraded to 4.2.4p5.
639 OpenSSH has been upgraded to 5.1p1.
641 For many years, FreeBSD's version of OpenSSH preferred DSA
642 over RSA for host and user authentication keys. With this
643 upgrade, we've switched to the vendor's default of RSA over
644 DSA. This may cause upgraded clients to warn about unknown
645 host keys even for previously known hosts. Users should
646 follow the usual procedure for verifying host keys before
647 accepting the RSA key.
649 This can be circumvented by setting the "HostKeyAlgorithms"
650 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
653 Please note that the sequence of keys offered for
654 authentication has been changed as well. You may want to
655 specify IdentityFile in a different order to revert this
659 The sio(4) driver has been removed from the i386 and amd64
660 kernel configuration files. This means uart(4) is now the
661 default serial port driver on those platforms as well.
663 To prevent collisions with the sio(4) driver, the uart(4) driver
664 uses different names for its device nodes. This means the
665 onboard serial port will now most likely be called "ttyu0"
666 instead of "ttyd0". You may need to reconfigure applications to
667 use the new device names.
669 When using the serial port as a boot console, be sure to update
670 /boot/device.hints and /etc/ttys before booting the new kernel.
671 If you forget to do so, you can still manually specify the hints
672 at the loader prompt:
674 set hint.uart.0.at="isa"
675 set hint.uart.0.port="0x3F8"
676 set hint.uart.0.flags="0x10"
677 set hint.uart.0.irq="4"
681 The gpt(8) utility has been removed. Use gpart(8) to partition
685 The version that Linuxulator emulates was changed from 2.4.2
686 to 2.6.16. If you experience any problems with Linux binaries
687 please try to set sysctl compat.linux.osrelease to 2.4.2 and
688 if it fixes the problem contact emulation mailing list.
691 ISDN4BSD (I4B) was removed from the src tree. You may need to
692 update a your kernel configuration and remove relevant entries.
695 I have checked in code to support multiple routing tables.
696 See the man pages setfib(1) and setfib(2).
697 This is a hopefully backwards compatible version,
698 but to make use of it you need to compile your kernel
699 with options ROUTETABLES=2 (or more up to 16).
702 The 802.11 wireless support was redone to enable multi-bss
703 operation on devices that are capable. The underlying device
704 is no longer used directly but instead wlanX devices are
705 cloned with ifconfig. This requires changes to rc.conf files.
707 ifconfig_ath0="WPA DHCP"
710 ifconfig_wlan0="WPA DHCP"
711 see rc.conf(5) for more details. In addition, mergemaster of
712 /etc/rc.d is highly recommended. Simultaneous update of userland
713 and kernel wouldn't hurt either.
715 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
716 modules were merged into the base wlan module. All references
717 to these modules (e.g. in kernel config files) must be removed.
720 psm(4) has gained write(2) support in native operation level.
721 Arbitrary commands can be written to /dev/psm%d and status can
722 be read back from it. Therefore, an application is responsible
723 for status validation and error recovery. It is a no-op in
724 other operation levels.
727 Support for KSE threading has been removed from the kernel. To
728 run legacy applications linked against KSE libmap.conf may
729 be used. The following libmap.conf may be used to ensure
730 compatibility with any prior release:
732 libpthread.so.1 libthr.so.1
733 libpthread.so.2 libthr.so.2
734 libkse.so.3 libthr.so.3
737 The layout of struct vmspace has changed. This affects libkvm
738 and any executables that link against libkvm and use the
739 kvm_getprocs() function. In particular, but not exclusively,
740 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
741 The effects are minimal, but it's advisable to upgrade world
745 The latest em driver no longer has support in it for the
746 82575 adapter, this is now moved to the igb driver. The
747 split was done to make new features that are incompatible
748 with older hardware easier to do.
751 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
752 likewise the kernel option is now GEOM_LINUX_LVM.
755 The default NFS mount mode has changed from UDP to TCP for
756 increased reliability. If you rely on (insecurely) NFS
757 mounting across a firewall you may need to update your
761 Belatedly note the addition of m_collapse for compacting
765 The fts(3) structures have been changed to use adequate
766 integer types for their members and so to be able to cope
767 with huge file trees. The old fts(3) ABI is preserved
768 through symbol versioning in libc, so third-party binaries
769 using fts(3) should still work, although they will not take
770 advantage of the extended types. At the same time, some
771 third-party software might fail to build after this change
772 due to unportable assumptions made in its source code about
773 fts(3) structure members. Such software should be fixed
774 by its vendor or, in the worst case, in the ports tree.
775 FreeBSD_version 800015 marks this change for the unlikely
776 case that a portable fix is impossible.
779 To upgrade to -current after this date, you must be running
780 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
781 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
784 The ADAPTIVE_GIANT kernel option has been retired because its
785 functionality is the default now.
788 The AT keyboard emulation of sunkbd(4) has been turned on
789 by default. In order to make the special symbols of the Sun
790 keyboards driven by sunkbd(4) work under X these now have
791 to be configured the same way as Sun USB keyboards driven
792 by ukbd(4) (which also does AT keyboard emulation), f.e.:
794 Option "XkbLayout" "us"
795 Option "XkbRules" "xorg"
796 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
799 It has been decided that it is desirable to provide ABI
800 backwards compatibility to the FreeBSD 4/5/6 versions of the
801 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
802 broken with the introduction of PCI domain support (see the
803 20070930 entry). Unfortunately, this required the ABI of
804 PCIOCGETCONF to be broken again in order to be able to
805 provide backwards compatibility to the old version of that
806 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
807 again. As for prominent ports this affects neither pciutils
808 nor xorg-server this time, the hal port needs to be rebuilt
812 The misnamed kthread_create() and friends have been renamed
813 to kproc_create() etc. Many of the callers already
815 I will return kthread_create() and friends in a while
816 with implementations that actually create threads, not procs.
817 Renaming corresponds with version 800002.
823 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
824 WITHOUT_LIBTHR are set.
827 The PCI code has been made aware of PCI domains. This means that
828 the location strings as used by pciconf(8) etc are now in the
829 following format: pci<domain>:<bus>:<device>[:<function>]. It
830 also means that consumers of <sys/pciio.h> potentially need to
831 be recompiled; this includes the hal and xorg-server ports.
834 The caching daemon (cached) was renamed to nscd. nscd.conf
835 configuration file should be used instead of cached.conf and
836 nscd_enable, nscd_pidfile and nscd_flags options should be used
837 instead of cached_enable, cached_pidfile and cached_flags in
841 The getfacl(1) utility now prints owning user and group name
842 instead of owning uid and gid in the three line comment header.
843 This is the same behavior as getfacl(1) on Solaris and Linux.
846 The new IPsec code is now compiled in using the IPSEC option. The
847 IPSEC option now requires "device crypto" be defined in your kernel
848 configuration. The FAST_IPSEC kernel option is now deprecated.
851 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
852 note the changed syntax - keep state is now on by default. Also
853 note the fact that ftp-proxy(8) has been changed from bottom up and
854 has been moved from libexec to usr/sbin. Changes in the ALTQ
855 handling also affect users of IPFW's ALTQ capabilities.
858 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
859 only IPsec supported by FreeBSD. The new IPsec stack
860 supports both IPv4 and IPv6. The kernel option will change
861 after the code changes have settled in. For now the kernel
862 option IPSEC is deprecated and FAST_IPSEC is the only option, that
863 will change after some settling time.
866 The wicontrol(8) utility has been removed from the base system. wi(4)
867 cards should be configured using ifconfig(8), see the man page for more
871 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
872 instead of the nve(4) driver. Please update your configuration
876 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
877 database if it is missing or older than the aliases file. If
878 desired, set the new rc.conf option sendmail_rebuild_aliases
879 to "YES" to restore that functionality.
882 The IPv4 multicast socket code has been considerably modified, and
883 moved to the file sys/netinet/in_mcast.c. Initial support for the
884 RFC 3678 Source-Specific Multicast Socket API has been added to
885 the IPv4 network stack.
887 Strict multicast and broadcast reception is now the default for
888 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
889 has now been removed.
891 The RFC 1724 hack for interface selection has been removed; the use
892 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
893 been added to replace it. Consumers such as routed will soon be
894 updated to reflect this.
896 These changes affect users who are running routed(8) or rdisc(8)
897 from the FreeBSD base system on point-to-point or unnumbered
901 The net80211 layer has changed significantly and all wireless
902 drivers that depend on it need to be recompiled. Further these
903 changes require that any program that interacts with the wireless
904 support in the kernel be recompiled; this includes: ifconfig,
905 wpa_supplicant, hostapd, and wlanstats. Users must also, for
906 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
907 if they use modules for wireless support. These modules implement
908 scanning support for station and ap modes, respectively. Failure
909 to load the appropriate module before marking a wireless interface
910 up will result in a message to the console and the device not
914 The pam_nologin(8) module ceases to provide an authentication
915 function and starts providing an account management function.
916 Consequent changes to /etc/pam.d should be brought in using
917 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
918 need manual editing as follows. Locate this line (or similar):
920 auth required pam_nologin.so no_warn
922 and change it according to this example:
924 account required pam_nologin.so no_warn
926 That is, the first word needs to be changed from "auth" to
927 "account". The new line can be moved to the account section
928 within the file for clarity. Not updating pam.conf(5) files
929 will result in nologin(5) ignored by the respective services.
932 The ether_ioctl() function has been synchronized with ioctl(2)
933 and ifnet.if_ioctl. Due to that, the size of one of its arguments
934 has changed on 64-bit architectures. All kernel modules using
935 ether_ioctl() need to be rebuilt on such architectures.
938 Improved INCLUDE_CONFIG_FILE support has been introduced to the
939 config(8) utility. In order to take advantage of this new
940 functionality, you are expected to recompile and install
941 src/usr.sbin/config. If you don't rebuild config(8), and your
942 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
943 build will be broken because of a missing "kernconfstring"
947 Symbol versioning is enabled by default. To disable it, use
948 option WITHOUT_SYMVER. It is not advisable to attempt to
949 disable symbol versioning once it is enabled; your installworld
950 will break because a symbol version-less libc will get installed
951 before the install tools. As a result, the old install tools,
952 which previously had symbol dependencies to FBSD_1.0, will fail
953 because the freshly installed libc will not have them.
955 The default threading library (providing "libpthread") has been
956 changed to libthr. If you wish to have libkse as your default,
957 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
960 The ABI breakage in sendmail(8)'s libmilter has been repaired
961 so it is no longer necessary to recompile mail filters (aka,
962 milters). If you recompiled mail filters after the 20070408
963 note, it is not necessary to recompile them again.
966 The new trunk(4) driver has been renamed to lagg(4) as it better
967 reflects its purpose. ifconfig will need to be recompiled.
970 sendmail(8) has been updated to version 8.14.1. Mail filters
971 (aka, milters) compiled against the libmilter included in the
972 base operating system should be recompiled.
975 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
976 In order to use them one must agree to the respective LICENSE in
977 share/doc/legal and define legal.intel_<name>.license_ack=1 via
978 loader.conf(5) or kenv(1). Make sure to deinstall the now
979 deprecated modules from the respective firmware ports.
982 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
983 were removed from FreeBSD's libc. These originally came from INRIA
984 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
985 deprecated in previous releases.
986 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
987 replace it as a more portable (and re-entrant) API.
990 To support interrupt filtering a modification to the newbus API
991 has occurred, ABI was broken and __FreeBSD_version was bumped
992 to 700031. Please make sure that your kernel and modules are in
994 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
997 The IPv6 multicast forwarding code may now be loaded into GENERIC
998 kernels by loading the ip_mroute.ko module. This is built into the
999 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
1000 set; see src.conf(5) for more information.
1003 The output of netstat -r has changed. Without -n, we now only
1004 print a "network name" without the prefix length if the network
1005 address and mask exactly match a Class A/B/C network, and an entry
1006 exists in the nsswitch "networks" map.
1007 With -n, we print the full unabbreviated CIDR network prefix in
1008 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
1009 This change is in preparation for changes such as equal-cost
1010 multipath, and to more generally assist operational deployment
1011 of FreeBSD as a modern IPv4 router.
1014 PIM has been turned on by default in the IPv4 multicast
1015 routing code. The kernel option 'PIM' has now been removed.
1016 PIM is now built by default if option 'MROUTING' is specified.
1017 It may now be loaded into GENERIC kernels by loading the
1018 ip_mroute.ko module.
1021 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
1022 has been removed. Its functionality may be achieved by explicitly
1023 configuring gif(4) interfaces and using the 'phyint' keyword in
1025 XORP does not support source-routed IPv4 multicast tunnels nor the
1026 integrated IPIP tunneling, therefore it is not affected by this
1027 change. The __FreeBSD_version macro has been bumped to 700030.
1030 Support for PCI Message Signalled Interrupts has been
1031 re-enabled in the bge driver, only for those chips which are
1032 believed to support it properly. If there are any problems,
1033 MSI can be disabled completely by setting the
1034 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
1038 Support for PCI Message Signalled Interrupts has been
1039 disabled again in the bge driver. Many revisions of the
1040 hardware fail to support it properly. Support can be
1041 re-enabled by removing the #define of BGE_DISABLE_MSI in
1042 "src/sys/dev/bge/if_bge.c".
1045 Support for PCI Message Signalled Interrupts has been added
1046 to the bge driver. If there are any problems, MSI can be
1047 disabled completely by setting the 'hw.pci.enable_msi' and
1048 'hw.pci.enable_msix' tunables to 0 in the loader.
1051 The removal of several facets of the experimental Threading
1052 system from the kernel means that the proc and thread structures
1053 have changed quite a bit. I suggest all kernel modules that might
1054 reference these structures be recompiled.. Especially the
1058 Sound infrastructure has been updated with various fixes and
1059 improvements. Most of the changes are pretty much transparent,
1060 with exceptions of followings:
1061 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
1062 moved to their own dev sysctl nodes, for example:
1063 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
1064 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
1065 own chardev in the form of "dsp%d.<function>%d", where <function>
1066 is p = playback, r = record and v = virtual, respectively. Users
1067 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
1068 This does not affect those who are using "/dev/dsp".
1071 geom(4)'s gmirror(8) class metadata structure has been
1072 rev'd from v3 to v4. If you update across this point and
1073 your metadata is converted for you, you will not be easily
1074 able to downgrade since the /boot/kernel.old/geom_mirror.ko
1075 kernel module will be unable to read the v4 metadata. You
1076 can resolve this by doing from the loader(8) prompt:
1078 set vfs.root.mountfrom="ufs:/dev/XXX"
1080 where XXX is the root slice of one of the disks that composed
1081 the mirror (i.e.: /dev/ad0s1a). You can then rebuild
1082 the array the same way you built it originally.
1085 The following binaries have been disconnected from the build:
1086 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
1087 and mount_std. The functionality of these programs has been
1088 moved into the mount program. For example, to mount a devfs
1089 filesystem, instead of using mount_devfs, use: "mount -t devfs".
1090 This does not affect entries in /etc/fstab, since entries in
1091 /etc/fstab are always processed with "mount -t fstype".
1094 Support for PCI Message Signalled Interrupts on i386 and amd64
1095 has been added to the kernel and various drivers will soon be
1096 updated to use MSI when it is available. If there are any problems,
1097 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
1098 and 'hw.pci.enable_msix' tunables to 0 in the loader.
1101 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
1102 The lockmgr object layout has been changed as a result of having
1103 a lock_object embedded in it. As a consequence all file system
1104 kernel modules must be re-compiled. The mutex profiling man page
1105 has not yet been updated to reflect this change.
1108 KSE in the kernel has now been made optional and turned on by
1109 default. Use 'nooption KSE' in your kernel config to turn it
1110 off. All kernel modules *must* be recompiled after this change.
1111 There-after, modules from a KSE kernel should be compatible with
1112 modules from a NOKSE kernel due to the temporary padding fields
1113 added to 'struct proc'.
1116 mrouted and its utilities have been removed from the base system.
1119 Some ioctl(2) command codes have changed. Full backward ABI
1120 compatibility is provided if the "options COMPAT_FREEBSD6" is
1121 present in the kernel configuration file. Make sure to add
1122 this option to your kernel config file, or recompile X.Org
1123 and the rest of ports; otherwise they may refuse to work.
1126 tcpslice has been removed from the base system.
1129 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
1130 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
1131 systat needs to be rebuilt.
1134 libpcap updated to v0.9.4 and tcpdump to v3.9.4
1137 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
1138 for IPFIREWALL_FORWARD is now as it was before when it was first
1139 committed and for years after. The behaviour is now ON.
1142 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
1143 Now it can decrypt files created from different architectures.
1144 Unfortunately, it is no longer able to decrypt a cipher text
1145 generated with an older version on 64 bit architectures.
1146 If you have such a file, you need old utility to decrypt it.
1149 The interface version of the i4b kernel part has changed. So
1150 after updating the kernel sources and compiling a new kernel,
1151 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
1152 be rebuilt, and vice versa.
1155 The XBOX kernel now defaults to the nfe(4) driver instead of
1156 the nve(4) driver. Please update your configuration
1160 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
1161 PCnet family of NICs has been removed. The new le(4) driver serves
1162 as an equivalent but cross-platform replacement with the pcn(4)
1163 driver still providing performance-optimized support for the subset
1164 of AMD Am79C971 PCnet-FAST and greater chips as before.
1167 The machdep.* sysctls and the adjkerntz utility have been
1168 modified a bit. The new adjkerntz utility uses the new
1169 sysctl names and sysctlbyname() calls, so it may be impossible
1170 to run an old /sbin/adjkerntz utility in single-user mode
1171 with a new kernel. Replace the `adjkerntz -i' step before
1172 `make installworld' with:
1174 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
1176 and proceed as usual with the rest of the installworld-stage
1177 steps. Otherwise, you risk installing binaries with their
1178 timestamp set several hours in the future, especially if
1179 you are running with local time set to GMT+X hours.
1182 The ip6fw utility has been removed. The behavior provided by
1183 ip6fw has been in ipfw2 for a good while and the rc.d scripts
1184 have been updated to deal with it. There are some rules that
1185 might not migrate cleanly. Use rc.firewall6 as a template to
1189 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
1190 attachments have been removed. Make sure to configure scc(4)
1191 on sparc64. Note also that by default puc(4) will use uart(4)
1192 and not sio(4) for serial ports because interrupt handling has
1193 been optimized for multi-port serial cards and only uart(4)
1194 implements the interface to support it.
1197 The scc(4) driver replaces puc(4) for Serial Communications
1198 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
1199 Z8530. On sparc64, it is advised to add scc(4) to the kernel
1200 configuration to make sure that the serial ports remain
1204 Most world/kernel related NO_* build options changed names.
1205 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
1206 after FreeBSD ports) and should be set in /etc/src.conf
1207 (the src.conf(5) manpage is provided). Full backwards
1208 compatibility is maintained for the time being though it's
1209 highly recommended to start moving old options out of the
1210 system-wide /etc/make.conf file into the new /etc/src.conf
1211 while also properly renaming them. More conversions will
1212 likely follow. Posting to current@:
1214 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
1217 The NETSMBCRYPTO kernel option has been retired because its
1218 functionality is always included in NETSMB and smbfs.ko now.
1221 The TDFX_LINUX kernel option was retired and replaced by the
1222 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
1223 kernel module. Loading it alone should suffice to get 3dfx support
1224 for Linux apps because it will pull in 3dfx.ko and linux.ko through
1228 The 'audit' group was added to support the new auditing functionality
1229 in the base system. Be sure to follow the directions for updating,
1230 including the requirement to run mergemaster -p.
1233 The kernel ABI to file system modules was changed on i386.
1234 Please make sure that your kernel and modules are in sync.
1237 This actually occured some time ago, but installing the kernel
1238 now also installs a bunch of symbol files for the kernel modules.
1239 This increases the size of /boot/kernel to about 67Mbytes. You
1240 will need twice this if you will eventually back this up to kernel.old
1241 on your next install.
1242 If you have a shortage of room in your root partition, you should add
1243 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
1244 to your /etc/make.conf.
1247 libc's malloc implementation has been replaced. This change has the
1248 potential to uncover application bugs that previously went unnoticed.
1249 See the malloc(3) manual page for more details.
1252 The generic netgraph(4) cookie has been changed. If you upgrade
1253 kernel passing this point, you also need to upgrade userland
1254 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
1257 si(4)'s device files now contain the unit number.
1258 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
1261 The kernel ABI was mostly destroyed due to a change in the size
1262 of struct lock_object which is nested in other structures such
1263 as mutexes which are nested in all sorts of other structures.
1264 Make sure your kernel and modules are in sync.
1267 The page coloring algorithm in the VM subsystem was converted
1268 from tuning with kernel options to autotuning. Please remove
1269 any PQ_* option except PQ_NOOPT from your kernel config.
1272 The net80211-related tools in the tools/tools/ath directory
1273 have been moved to tools/tools/net80211 and renamed with a
1274 "wlan" prefix. Scripts that use them should be adjusted
1278 Scripts in the local_startup directories (as defined in
1279 /etc/defaults/rc.conf) that have the new rc.d semantics will
1280 now be run as part of the base system rcorder. If there are
1281 errors or problems with one of these local scripts, it could
1282 cause boot problems. If you encounter such problems, boot in
1283 single user mode, remove that script from the */rc.d directory.
1284 Please report the problem to the port's maintainer, and the
1285 freebsd-ports@freebsd.org mailing list.
1288 The nodev mount option was deprecated in RELENG_6 (where it
1289 was a no-op), and is now unsupported. If you have nodev or dev listed
1290 in /etc/fstab, remove it, otherwise it will result in a mount error.
1293 ABI between ipfw(4) and ipfw(8) has been changed. You need
1294 to rebuild ipfw(8) when rebuilding kernel.
1297 rp(4)'s device files now contain the unit number.
1298 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
1301 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
1302 Its /etc/rc.conf.d configuration file has been `ppp' from
1303 the beginning, and hence there is no need to touch it.
1306 Now most modules get their build-time options from the kernel
1307 configuration file. A few modules still have fixed options
1308 due to their non-conformant implementation, but they will be
1309 corrected eventually. You may need to review the options of
1310 the modules in use, explicitly specify the non-default options
1311 in the kernel configuration file, and rebuild the kernel and
1315 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
1316 to turn polling(4) on your interfaces.
1319 The old bridge(4) implementation was retired. The new
1320 if_bridge(4) serves as a full functional replacement.
1323 The ai_addrlen of a struct addrinfo was changed to a socklen_t
1324 to conform to POSIX-2001. This change broke an ABI
1325 compatibility on 64 bit architecture. You have to recompile
1326 userland programs that use getaddrinfo(3) on 64 bit
1330 RELENG_6 branched here.
1333 The pccard_ifconfig rc.conf variable has been removed and a new
1334 variable, ifconfig_DEFAULT has been introduced. Unlike
1335 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
1336 do not have ifconfig_ifn entries rather than just those in
1337 removable_interfaces.
1340 Some previous versions of PAM have permitted the use of
1341 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
1342 to third party PAM modules in /usr/local/lib. A change has been
1343 made to require the use of absolute paths in order to avoid
1344 ambiguity and dependence on library path configuration, which may
1345 affect existing configurations.
1348 Major changes to network interface API. All drivers must be
1349 recompiled. Drivers not in the base system will need to be
1350 updated to the new APIs.
1353 Changes were made to kinfo_proc in sys/user.h. Please recompile
1354 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
1355 will not behave correctly.
1357 The API and ABI for hwpmc(4) have changed with the addition
1358 of sampling support. Please recompile lib/libpmc(3) and
1359 usr.sbin/{pmcstat,pmccontrol}.
1362 The OpenBSD dhclient was imported in place of the ISC dhclient
1363 and the network interface configuration scripts were updated
1364 accordingly. If you use DHCP to configure your interfaces, you
1365 must now run devd. Also, DNS updating was lost so you will need
1366 to find a workaround if you use this feature.
1368 The '_dhcp' user was added to support the OpenBSD dhclient. Be
1369 sure to run mergemaster -p (like you are supposed to do every time
1373 if_bridge was added to the tree. This has changed struct ifnet.
1374 Please recompile userland and all network related modules.
1377 The n_net of a struct netent was changed to an uint32_t, and
1378 1st argument of getnetbyaddr() was changed to an uint32_t, to
1379 conform to POSIX-2001. These changes broke an ABI
1380 compatibility on 64 bit architecture. With these changes,
1381 shlib major of libpcap was bumped. You have to recompile
1382 userland programs that use getnetbyaddr(3), getnetbyname(3),
1383 getnetent(3) and/or libpcap on 64 bit architecture.
1386 Kernel parsing of extra options on '#!' first lines of shell
1387 scripts has changed. Lines with multiple options likely will
1388 fail after this date. For full details, please see
1389 http://people.freebsd.org/~gad/Updating-20050528.txt
1392 The packet filter (pf) code has been updated to OpenBSD 3.7
1393 Please note the changed anchor syntax and the fact that
1394 authpf(8) now needs a mounted fdescfs(5) to function.
1397 The NO_MIXED_MODE kernel option has been removed from the i386
1398 amd64 platforms as its use has been superceded by the new local
1399 APIC timer code. Any kernel config files containing this option
1403 The on-disk format of LC_CTYPE files was changed to be machine
1404 independent. Please make sure NOT to use NO_CLEAN buildworld
1405 when crossing this point. Crossing this point also requires
1406 recompile or reinstall of all locale depended packages.
1409 The ifi_epoch member of struct if_data has been changed to
1410 contain the uptime at which the interface was created or the
1411 statistics zeroed rather then the wall clock time because
1412 wallclock time may go backwards. This should have no impact
1413 unless an snmp implementation is using this value (I know of
1414 none at this point.)
1417 The acpi_perf and acpi_throttle drivers are now part of the
1418 acpi(4) main module. They are no longer built separately.
1421 The layout of struct image_params has changed. You have to
1422 recompile all compatibility modules (linux, svr4, etc) for use
1423 with the new kernel.
1426 The p4tcc driver has been merged into cpufreq(4). This makes
1427 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
1428 compile in "device cpufreq" to restore this functionality.
1431 The responsibility of recomputing the file system summary of
1432 a SoftUpdates-enabled dirty volume has been transferred to the
1433 background fsck. A rebuild of fsck(8) utility is recommended
1434 if you have updated the kernel.
1436 To get the old behavior (recompute file system summary at mount
1437 time), you can set vfs.ffs.compute_summary_at_mount=1 before
1438 mounting the new volume.
1441 The cpufreq import is complete. As part of this, the sysctls for
1442 acpi(4) throttling have been removed. The power_profile script
1443 has been updated, so you can use performance/economy_cpu_freq in
1444 rc.conf(5) to set AC on/offline cpu frequencies.
1447 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
1448 requires recompiling libnetgraph and userland netgraph utilities.
1451 Support for abbreviated forms of a number of ipfw options is
1452 now deprecated. Warnings are printed to stderr indicating the
1453 correct full form when a match occurs. Some abbreviations may
1454 be supported at a later date based on user feedback. To be
1455 considered for support, abbreviations must be in use prior to
1456 this commit and unlikely to be confused with current key words.
1459 By a popular demand, a lot of NOFOO options were renamed
1460 to NO_FOO (see bsd.compat.mk for a full list). The old
1461 spellings are still supported, but will cause annoying
1462 warnings on stderr. Make sure you upgrade properly (see
1463 the COMMON ITEMS: section later in this file).
1466 Auto-loading of ancillary wlan modules such as wlan_wep has
1467 been temporarily disabled; you need to statically configure
1468 the modules you need into your kernel or explicitly load them
1469 prior to use. Specifically, if you intend to use WEP encryption
1470 with an 802.11 device load/configure wlan_wep; if you want to
1471 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
1472 and wlan_xauth as required.
1475 The behaviour of ppp(8) has changed slightly. If lqr is enabled
1476 (``enable lqr''), older versions would revert to LCP ECHO mode on
1477 negotiation failure. Now, ``enable echo'' is required for this
1478 behaviour. The ppp version number has been bumped to 3.4.2 to
1482 The wlan support has been updated to split the crypto support
1483 into separate modules. For static WEP you must configure the
1484 wlan_wep module in your system or build and install the module
1485 in place where it can be loaded (the kernel will auto-load
1486 the module when a wep key is configured).
1489 The ath driver has been updated to split the tx rate control
1490 algorithm into a separate module. You need to include either
1491 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
1494 Support for systems with an 80386 CPU has been removed. Please
1495 use FreeBSD 5.x or earlier on systems with an 80386.
1498 We have had a hack which would mount the root filesystem
1499 R/W if the device were named 'md*'. As part of the vnode
1500 work I'm doing I have had to remove this hack. People
1501 building systems which use preloaded MD root filesystems
1502 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
1503 their /etc/rc scripts.
1506 FreeBSD 5.3 shipped here.
1509 The size of struct tcpcb has changed again due to the removal
1510 of RFC1644 T/TCP. You have to recompile userland programs that
1511 read kmem for tcp sockets directly (netstat, sockstat, etc.)
1514 The size of struct tcpcb has changed. You have to recompile
1515 userland programs that read kmem for tcp sockets directly
1516 (netstat, sockstat, etc.)
1519 RELENG_5 branched here. For older entries, please see updating
1520 in the RELENG_5 branch.
1526 Avoid using make -j when upgrading. From time to time in the
1527 past there have been problems using -j with buildworld and/or
1528 installworld. This is especially true when upgrading between
1529 "distant" versions (eg one that cross a major release boundary
1530 or several minor releases, or when several months have passed
1531 on the -current branch).
1533 Sometimes, obscure build problems are the result of environment
1534 poisoning. This can happen because the make utility reads its
1535 environment when searching for values for global variables.
1536 To run your build attempts in an "environmental clean room",
1537 prefix all make commands with 'env -i '. See the env(1) manual
1538 page for more details.
1540 When upgrading from one major version to another it is generally
1541 best to upgrade to the latest code in the currently installed branch
1542 first, then do an upgrade to the new branch. This is the best-tested
1543 upgrade path, and has the highest probability of being successful.
1544 Please try this approach before reporting problems with a major
1549 If you are updating from a prior version of FreeBSD (even one just
1550 a few days old), you should follow this procedure. It is the most
1551 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1553 make kernel-toolchain
1554 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1555 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1557 To test a kernel once
1558 ---------------------
1559 If you just want to boot a kernel once (because you are not sure
1560 if it works, or if you want to boot a known bad kernel to provide
1561 debugging information) run
1562 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1563 nextboot -k testkernel
1565 To just build a kernel when you know that it won't mess you up
1566 --------------------------------------------------------------
1567 This assumes you are already running a 5.X system. Replace
1568 ${arch} with the architecture of your machine (e.g. "i386",
1569 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1571 cd src/sys/${arch}/conf
1572 config KERNEL_NAME_HERE
1573 cd ../compile/KERNEL_NAME_HERE
1578 If this fails, go to the "To build a kernel" section.
1580 To rebuild everything and install it on the current system.
1581 -----------------------------------------------------------
1582 # Note: sometimes if you are running current you gotta do more than
1583 # is listed here if you are upgrading from a really old current.
1585 <make sure you have good level 0 dumps>
1587 make kernel KERNCONF=YOUR_KERNEL_HERE
1589 <reboot in single user> [3]
1597 To cross-install current onto a separate partition
1598 --------------------------------------------------
1599 # In this approach we use a separate partition to hold
1600 # current's root, 'usr', and 'var' directories. A partition
1601 # holding "/", "/usr" and "/var" should be about 2GB in
1604 <make sure you have good level 0 dumps>
1607 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1608 <maybe newfs current's root partition>
1609 <mount current's root partition on directory ${CURRENT_ROOT}>
1610 make installworld DESTDIR=${CURRENT_ROOT}
1611 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1612 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1613 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1614 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1615 <reboot into current>
1616 <do a "native" rebuild/install as described in the previous section>
1617 <maybe install compatibility libraries from ports/misc/compat*>
1621 To upgrade in-place from 5.x-stable to current
1622 ----------------------------------------------
1623 <make sure you have good level 0 dumps>
1625 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1627 <reboot in single user> [3]
1634 Make sure that you've read the UPDATING file to understand the
1635 tweaks to various things you need. At this point in the life
1636 cycle of current, things change often and you are on your own
1637 to cope. The defaults can also change, so please read ALL of
1638 the UPDATING entries.
1640 Also, if you are tracking -current, you must be subscribed to
1641 freebsd-current@freebsd.org. Make sure that before you update
1642 your sources that you have read and understood all the recent
1643 messages there. If in doubt, please track -stable which has
1644 much fewer pitfalls.
1646 [1] If you have third party modules, such as vmware, you
1647 should disable them at this point so they don't crash your
1650 [3] From the bootblocks, boot -s, and then do
1655 adjkerntz -i # if CMOS is wall time
1656 Also, when doing a major release upgrade, it is required that
1657 you boot into single user mode to do the installworld.
1659 [4] Note: This step is non-optional. Failure to do this step
1660 can result in a significant reduction in the functionality of the
1661 system. Attempting to do it by hand is not recommended and those
1662 that pursue this avenue should read this file carefully, as well
1663 as the archives of freebsd-current and freebsd-hackers mailing lists
1664 for potential gotchas.
1666 [5] Usually this step is a noop. However, from time to time
1667 you may need to do this if you get unknown user in the following
1668 step. It never hurts to do it all the time. You may need to
1669 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1670 install) after the buildworld before this step if you last updated
1671 from current before 20020224 or from -stable before 20020408.
1673 [8] In order to have a kernel that can run the 4.x binaries
1674 needed to do an installworld, you must include the COMPAT_FREEBSD4
1675 option in your kernel. Failure to do so may leave you with a system
1676 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
1677 is required to run the 5.x binaries on more recent kernels.
1679 Make sure that you merge any new devices from GENERIC since the
1680 last time you updated your kernel config file.
1682 [9] When checking out sources, you must include the -P flag to have
1683 cvs prune empty directories.
1685 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1686 "?=" instead of the "=" assignment operator, so that buildworld can
1687 override the CPUTYPE if it needs to.
1689 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1690 not on the command line, or in /etc/make.conf. buildworld will
1691 warn if it is improperly defined.
1694 This file contains a list, in reverse chronological order, of major
1695 breakages in tracking -current. Not all things will be listed here,
1696 and it only starts on October 16, 2004. Updating files can found in
1697 previous releases if your system is older than this.
1699 Copyright information:
1701 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
1703 Redistribution, publication, translation and use, with or without
1704 modification, in full or in part, in any form or format of this
1705 document are permitted without further permission from the author.
1707 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1708 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1709 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1710 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1711 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1712 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1713 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1714 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1715 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1716 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1717 POSSIBILITY OF SUCH DAMAGE.
1719 If you find this document useful, and you want to, you may buy the
1722 Contact Warner Losh if you have any questions about your use of