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:
12 FreeBSD 8.x has many debugging features turned on, in
13 both the kernel and userland. These features attempt to detect
14 incorrect use of system primitives, and encourage loud failure
15 through extra sanity checking and fail stop semantics. They
16 also substantially impact system performance. If you want to
17 do performance measurement, benchmarking, and optimization,
18 you'll want to turn them off. This includes various WITNESS-
19 related kernel options, INVARIANTS, malloc debugging flags
20 in userland, and various verbose features in the kernel. Many
21 developers choose to disable these features on build machines
22 to maximize performance. (To disable malloc debugging, run
23 ln -s aj /etc/malloc.conf.)
26 The newly imported zic(8) produces a new format in the
27 output. Please run tzsetup(8) to install the newly created
28 data to /etc/localtime.
31 The sysctl tree for the usb stack has renamed from hw.usb2.* to
32 hw.usb.* and is now consistent again with previous releases.
35 802.11 monitor mode support was revised and driver api's
36 were changed. Drivers dependent on net80211 now support
37 DLT_IEEE802_11_RADIO instead of DLT_IEEE802_11. No
38 user-visible data structures were changed but applications
39 that use DLT_IEEE802_11 may require changes.
40 Bump __FreeBSD_version to 800088.
43 The layout of the following structs has changed: sysctl_oid,
44 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
45 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
46 panics may be experienced. World rebuild is required for
47 correctly checking networking state from userland.
48 Bump __FreeBSD_version to 800085.
51 MLDv2 and Source-Specific Multicast (SSM) have been merged
52 to the IPv6 stack. VIMAGE hooks are in but not yet used.
53 The implementation of SSM within FreeBSD's IPv6 stack closely
54 follows the IPv4 implementation.
56 For kernel developers:
58 * The most important changes are that the ip6_output() and
59 ip6_input() paths no longer take the IN6_MULTI_LOCK,
60 and this lock has been downgraded to a non-recursive mutex.
62 * As with the changes to the IPv4 stack to support SSM, filtering
63 of inbound multicast traffic must now be performed by transport
64 protocols within the IPv6 stack. This does not apply to TCP and
65 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
67 * The KPIs used by IPv6 multicast are similar to those used by
68 the IPv4 stack, with the following differences:
69 * im6o_mc_filter() is analogous to imo_multicast_filter().
70 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
71 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
72 * IN6_LOOKUP_MULTI() has been deprecated and removed.
73 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
74 for MLDv1 have an additional 'timer' argument which is used to
75 jitter the initial membership report for the solicited-node
76 multicast membership on-link.
77 * This is not strictly needed for MLDv2, which already jitters
78 its report transmissions. However, the 'timer' argument is
79 preserved in case MLDv1 is active on the interface.
81 * The KAME linked-list based IPv6 membership implementation has
82 been refactored to use a vector similar to that used by the IPv4
84 Code which maintains a list of its own multicast memberships
85 internally, e.g. carp, has been updated to reflect the new
88 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
89 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
90 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
91 implementation constraint which needs to be addressed in HEAD.
93 For application developers:
95 * The changes are broadly similar to those made for the IPv4
98 * The use of IPv4 and IPv6 multicast socket options on the same
99 socket, using mapped addresses, HAS NOT been tested or supported.
101 * There are a number of issues with the implementation of various
102 IPv6 multicast APIs which need to be resolved in the API surface
103 before the implementation is fully compatible with KAME userland
104 use, and these are mostly to do with interface index treatment.
106 * The literature available discusses the use of either the delta / ASM
107 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
108 using setsourcefilter(3)/getsourcefilter(3). For more information
109 please refer to RFC 3768, 'Socket Interface Extensions for
110 Multicast Source Filters'.
112 * Applications which use the published RFC 3678 APIs should be fine.
114 For systems administrators:
116 * The mtest(8) utility has been refactored to support IPv6, in
117 addition to IPv4. Interface addresses are no longer accepted
118 as arguments, their names must be used instead. The utility
119 will map the interface name to its first IPv4 address as
120 returned by getifaddrs(3).
122 * The ifmcstat(8) utility has also been updated to print the MLDv2
123 endpoint state and source filter lists via sysctl(3).
125 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
126 loopback of IPv6 multicast datagrams by default; it defaults to 1
127 to preserve the existing behaviour. Disabling multicast loopback is
128 recommended for optimal system performance.
130 * The IPv6 MROUTING code has been changed to examine this sysctl
131 instead of attempting to perform a group lookup before looping
132 back forwarded datagrams.
134 Bump __FreeBSD_version to 800084.
137 Implement low-level Bluetooth HCI API.
138 Bump __FreeBSD_version to 800083.
141 The layout of struct malloc_type, used by modules to register new
142 memory allocation types, has changed. Most modules will need to
143 be rebuilt or panics may be experienced.
144 Bump __FreeBSD_version to 800081.
147 Anticipate overflowing inp_flags - add inp_flags2.
148 This changes most offsets in inpcb, so checking v4 connection
149 state will require a world rebuild.
150 Bump __FreeBSD_version to 800080.
153 Add an llentry to struct route and struct route_in6. Modules
154 embedding a struct route will need to be recompiled.
155 Bump __FreeBSD_version to 800079.
158 The size of rt_metrics_lite and by extension rtentry has changed.
159 Networking administration apps will need to be recompiled.
160 The route command now supports show as an alias for get, weighting
161 of routes, sticky and nostick flags to alter the behavior of stateful
163 Bump __FreeBSD_version to 800078.
166 Do not use Giant for kbdmux(4) locking. This is wrong and
167 apparently causing more problems than it solves. This will
168 re-open the issue where interrupt handlers may race with
169 kbdmux(4) in polling mode. Typical symptoms include (but
170 not limited to) duplicated and/or missing characters when
171 low level console functions (such as gets) are used while
172 interrupts are enabled (for example geli password prompt,
173 mountroot prompt etc.). Disabling kbdmux(4) may help.
176 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
177 kernel modules referencing any of the above need to be recompiled.
178 Bump __FreeBSD_version to 800075.
181 GEOM_PART has become the default partition slicer for storage devices,
182 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
183 introduces some changes:
185 MSDOS/EBR: the devices created from MSDOS extended partition entries
186 (EBR) can be named differently than with GEOM_MBR and are now symlinks
187 to devices with offset-based names. fstabs may need to be modified.
189 BSD: the "geometry does not match label" warning is harmless in most
190 cases but it points to problems in file system misalignment with
191 disk geometry. The "c" partition is now implicit, covers the whole
192 top-level drive and cannot be (mis)used by users.
194 General: Kernel dumps are now not allowed to be written to devices
195 whose partition types indicate they are meant to be used for file
196 systems (or, in case of MSDOS partitions, as something else than
199 Most of these changes date approximately from 200812.
202 The uscanner(4) driver has been removed from the kernel. This follows
203 Linux removing theirs in 2.6 and making libusb the default interface
207 The multicast forwarding code has been cleaned up. netstat(1)
208 only relies on KVM now for printing bandwidth upcall meters.
209 The IPv4 and IPv6 modules are split into ip_mroute_mod and
210 ip6_mroute_mod respectively. The config(5) options for statically
211 compiling this code remain the same, i.e. 'options MROUTING'.
214 Support for the IFF_NEEDSGIANT network interface flag has been
215 removed, which means that non-MPSAFE network device drivers are no
216 longer supported. In particular, if_ar, if_sr, and network device
217 drivers from the old (legacy) USB stack can no longer be built or
221 POSIX.1 Native Language Support (NLS) has been enabled in libc and
222 a bunch of new language catalog files have also been added.
223 This means that some common libc messages are now localized and
224 they depend on the LC_MESSAGES environmental variable.
227 The k8temp(4) driver has been renamed to amdtemp(4) since
228 support for K10 and K11 CPU families was added.
231 IGMPv3 and Source-Specific Multicast (SSM) have been merged
232 to the IPv4 stack. VIMAGE hooks are in but not yet used.
234 For kernel developers, the most important changes are that the
235 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
236 and this lock has been downgraded to a non-recursive mutex.
238 Transport protocols (UDP, Raw IP) are now responsible for filtering
239 inbound multicast traffic according to group membership and source
240 filters. The imo_multicast_filter() KPI exists for this purpose.
241 Transports which do not use multicast (SCTP, TCP) already reject
242 multicast by default. Forwarding and receive performance may improve
243 as a mutex acquisition is no longer needed in the ip_input()
244 low-level input path. in_addmulti() and in_delmulti() are shimmed
245 to new KPIs which exist to support SSM in-kernel.
247 For application developers, it is recommended that loopback of
248 multicast datagrams be disabled for best performance, as this
249 will still cause the lock to be taken for each looped-back
250 datagram transmission. The net.inet.ip.mcast.loop sysctl may
251 be tuned to 0 to disable loopback by default; it defaults to 1
252 to preserve the existing behaviour.
254 For systems administrators, to obtain best performance with
255 multicast reception and multiple groups, it is always recommended
256 that a card with a suitably precise hash filter is used. Hash
257 collisions will still result in the lock being taken within the
258 transport protocol input path to check group membership.
260 If deploying FreeBSD in an environment with IGMP snooping switches,
261 it is recommended that the net.inet.igmp.sendlocal sysctl remain
262 enabled; this forces 224.0.0.0/24 group membership to be announced
265 The size of 'struct igmpstat' has changed; netstat needs to be
266 recompiled to reflect this.
267 Bump __FreeBSD_version to 800070.
270 libusb20.so.1 is now installed as libusb.so.1 and the ports system
271 updated to use it. This requires a buildworld/installworld in order to
272 update the library and dependencies (usbconfig, etc). Its advisable to
273 rebuild all ports which uses libusb. More specific directions are given
274 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
275 libusb are no longer required and can be removed.
278 A workaround is committed to allow the creation of System V shared
279 memory segment of size > 2 GB on the 64-bit architectures.
280 Due to a limitation of the existing ABI, the shm_segsz member
281 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
282 wrong for large segments. Note that limits must be explicitly
283 raised to allow such segments to be created.
286 The layout of struct ifnet has changed, requiring a rebuild of all
287 network device driver modules.
290 The /dev handling for the new USB stack has changed, a
291 buildworld/installworld is required for libusb20.
294 The new USB2 stack has now been permanently moved in and all kernel and
295 module names reverted to their previous values (eg, usb, ehci, ohci,
296 ums, ...). The old usb stack can be compiled in by prefixing the name
297 with the letter 'o', the old usb modules have been removed.
298 Updating entry 20090216 for xorg and 20090215 for libmap may still
302 The rc.conf(5) option if_up_delay has been renamed to
303 defaultroute_delay to better reflect its purpose. If you have
304 customized this setting in /etc/rc.conf you need to update it to
308 xorg 7.4 wants to configure its input devices via hald which does not
309 yet work with USB2. If the keyboard/mouse does not work in xorg then
311 Option "AllowEmptyInput" "off"
312 to your ServerLayout section. This will cause X to use the configured
313 kbd and mouse sections from your xorg.conf.
316 The GENERIC kernels for all architectures now default to the new USB2
317 stack. No kernel config options or code have been removed so if a
318 problem arises please report it and optionally revert to the old USB
319 stack. If you are loading USB kernel modules or have a custom kernel
320 that includes GENERIC then ensure that usb names are also changed over,
321 eg uftdi -> usb2_serial_ftdi.
323 Older programs linked against the ports libusb 0.1 need to be
324 redirected to the new stack's libusb20. /etc/libmap.conf can
326 # Map old usb library to new one for usb2 stack
327 libusb-0.1.so.8 libusb20.so.1
330 The ichsmb(4) driver has been changed to require SMBus slave
331 addresses be left-justified (xxxxxxx0b) rather than right-justified.
332 All of the other SMBus controller drivers require left-justified
333 slave addresses, so this change makes all the drivers provide the
337 INET6 statistics (struct ip6stat) was updated.
338 netstat(1) needs to be recompiled.
341 NTFS has been removed from GENERIC kernel on amd64 to match
342 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
343 will load ntfs.ko module automatically when NTFS support is
344 actually needed, unless ntfs.ko is not installed or security
345 level prohibits loading kernel modules. If either is the case,
346 "options NTFS" has to be added into kernel config.
349 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
350 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
351 800061. User space tools that rely on the size of struct tcpcb in
352 tcp_var.h (e.g. sockstat) need to be recompiled.
355 ng_tty(4) module updated to match the new TTY subsystem.
356 Due to API change, user-level applications must be updated.
357 New API support added to mpd5 CVS and expected to be present
358 in next mpd5.3 release.
361 With __FreeBSD_version 800060 the makefs tool is part of
362 the base system (it was a port).
365 The afdata and ifnet locks have been changed from mutexes to
366 rwlocks, network modules will need to be re-compiled.
369 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
370 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
371 The new code reduced struct rtentry{} by 16 bytes on 32-bit
372 architecture and 40 bytes on 64-bit architecture. The userland
373 applications "arp" and "ndp" have been updated accordingly.
374 The output from "netstat -r" shows only routing entries and
375 none of the L2 information.
378 __FreeBSD_version 800057 marks the switchover from the
379 binary ath hal to source code. Users must add the line:
381 options AH_SUPPORT_AR5416
383 to their kernel config files when specifying:
387 The ath_hal module no longer exists; the code is now compiled
388 together with the driver in the ath module. It is now
389 possible to tailor chip support (i.e. reduce the set of chips
390 and thereby the code size); consult ath_hal(4) for details.
393 __FreeBSD_version 800054 adds memory barriers to
394 <machine/atomic.h>, new interfaces to ifnet to facilitate
395 multiple hardware transmit queues for cards that support
396 them, and a lock-less ring-buffer implementation to
397 enable drivers to more efficiently manage queueing of
401 A new version of ZFS (version 13) has been merged to -HEAD.
402 This version has zpool attribute "listsnapshots" off by
403 default, which means "zfs list" does not show snapshots,
404 and is the same as Solaris behavior.
407 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
410 The uhci, ohci, ehci and slhci USB Host controller drivers have
411 been put into separate modules. If you load the usb module
412 separately through loader.conf you will need to load the
413 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
414 controller add the following to loader.conf:
420 The ABI used by the PMC toolset has changed. Please keep
421 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
425 The TTY subsystem of the kernel has been replaced by a new
426 implementation, which provides better scalability and an
427 improved driver model. Most common drivers have been migrated to
428 the new TTY subsystem, while others have not. The following
429 drivers have not yet been ported to the new TTY layer:
432 cy, digi, rc, rp, sio
438 ng_h4, ng_tty, ppp, sl, snp
440 Adding these drivers to your kernel configuration file shall
441 cause compilation to fail.
444 ntpd has been upgraded to 4.2.4p5.
447 OpenSSH has been upgraded to 5.1p1.
449 For many years, FreeBSD's version of OpenSSH preferred DSA
450 over RSA for host and user authentication keys. With this
451 upgrade, we've switched to the vendor's default of RSA over
452 DSA. This may cause upgraded clients to warn about unknown
453 host keys even for previously known hosts. Users should
454 follow the usual procedure for verifying host keys before
455 accepting the RSA key.
457 This can be circumvented by setting the "HostKeyAlgorithms"
458 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
461 Please note that the sequence of keys offered for
462 authentication has been changed as well. You may want to
463 specify IdentityFile in a different order to revert this
467 The sio(4) driver has been removed from the i386 and amd64
468 kernel configuration files. This means uart(4) is now the
469 default serial port driver on those platforms as well.
471 To prevent collisions with the sio(4) driver, the uart(4) driver
472 uses different names for its device nodes. This means the
473 onboard serial port will now most likely be called "ttyu0"
474 instead of "ttyd0". You may need to reconfigure applications to
475 use the new device names.
477 When using the serial port as a boot console, be sure to update
478 /boot/device.hints and /etc/ttys before booting the new kernel.
479 If you forget to do so, you can still manually specify the hints
480 at the loader prompt:
482 set hint.uart.0.at="isa"
483 set hint.uart.0.port="0x3F8"
484 set hint.uart.0.flags="0x10"
485 set hint.uart.0.irq="4"
489 The gpt(8) utility has been removed. Use gpart(8) to partition
493 The version that Linuxulator emulates was changed from 2.4.2
494 to 2.6.16. If you experience any problems with Linux binaries
495 please try to set sysctl compat.linux.osrelease to 2.4.2 and
496 if it fixes the problem contact emulation mailing list.
499 ISDN4BSD (I4B) was removed from the src tree. You may need to
500 update a your kernel configuration and remove relevant entries.
503 I have checked in code to support multiple routing tables.
504 See the man pages setfib(1) and setfib(2).
505 This is a hopefully backwards compatible version,
506 but to make use of it you need to compile your kernel
507 with options ROUTETABLES=2 (or more up to 16).
510 The 802.11 wireless support was redone to enable multi-bss
511 operation on devices that are capable. The underlying device
512 is no longer used directly but instead wlanX devices are
513 cloned with ifconfig. This requires changes to rc.conf files.
515 ifconfig_ath0="WPA DHCP"
518 ifconfig_wlan0="WPA DHCP"
519 see rc.conf(5) for more details. In addition, mergemaster of
520 /etc/rc.d is highly recommended. Simultaneous update of userland
521 and kernel wouldn't hurt either.
523 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
524 modules were merged into the base wlan module. All references
525 to these modules (e.g. in kernel config files) must be removed.
528 psm(4) has gained write(2) support in native operation level.
529 Arbitrary commands can be written to /dev/psm%d and status can
530 be read back from it. Therefore, an application is responsible
531 for status validation and error recovery. It is a no-op in
532 other operation levels.
535 Support for KSE threading has been removed from the kernel. To
536 run legacy applications linked against KSE libmap.conf may
537 be used. The following libmap.conf may be used to ensure
538 compatibility with any prior release:
540 libpthread.so.1 libthr.so.1
541 libpthread.so.2 libthr.so.2
542 libkse.so.3 libthr.so.3
545 The layout of struct vmspace has changed. This affects libkvm
546 and any executables that link against libkvm and use the
547 kvm_getprocs() function. In particular, but not exclusively,
548 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
549 The effects are minimal, but it's advisable to upgrade world
553 The latest em driver no longer has support in it for the
554 82575 adapter, this is now moved to the igb driver. The
555 split was done to make new features that are incompatible
556 with older hardware easier to do.
559 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
560 likewise the kernel option is now GEOM_LINUX_LVM.
563 The default NFS mount mode has changed from UDP to TCP for
564 increased reliability. If you rely on (insecurely) NFS
565 mounting across a firewall you may need to update your
569 Belatedly note the addition of m_collapse for compacting
573 The fts(3) structures have been changed to use adequate
574 integer types for their members and so to be able to cope
575 with huge file trees. The old fts(3) ABI is preserved
576 through symbol versioning in libc, so third-party binaries
577 using fts(3) should still work, although they will not take
578 advantage of the extended types. At the same time, some
579 third-party software might fail to build after this change
580 due to unportable assumptions made in its source code about
581 fts(3) structure members. Such software should be fixed
582 by its vendor or, in the worst case, in the ports tree.
583 FreeBSD_version 800015 marks this change for the unlikely
584 case that a portable fix is impossible.
587 To upgrade to -current after this date, you must be running
588 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
589 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
592 The ADAPTIVE_GIANT kernel option has been retired because its
593 functionality is the default now.
596 The AT keyboard emulation of sunkbd(4) has been turned on
597 by default. In order to make the special symbols of the Sun
598 keyboards driven by sunkbd(4) work under X these now have
599 to be configured the same way as Sun USB keyboards driven
600 by ukbd(4) (which also does AT keyboard emulation), f.e.:
602 Option "XkbLayout" "us"
603 Option "XkbRules" "xorg"
604 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
607 It has been decided that it is desirable to provide ABI
608 backwards compatibility to the FreeBSD 4/5/6 versions of the
609 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
610 broken with the introduction of PCI domain support (see the
611 20070930 entry). Unfortunately, this required the ABI of
612 PCIOCGETCONF to be broken again in order to be able to
613 provide backwards compatibility to the old version of that
614 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
615 again. As for prominent ports this affects neither pciutils
616 nor xorg-server this time, the hal port needs to be rebuilt
620 The misnamed kthread_create() and friends have been renamed
621 to kproc_create() etc. Many of the callers already
623 I will return kthread_create() and friends in a while
624 with implementations that actually create threads, not procs.
625 Renaming corresponds with version 800002.
631 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
632 WITHOUT_LIBTHR are set.
635 The PCI code has been made aware of PCI domains. This means that
636 the location strings as used by pciconf(8) etc are now in the
637 following format: pci<domain>:<bus>:<device>[:<function>]. It
638 also means that consumers of <sys/pciio.h> potentially need to
639 be recompiled; this includes the hal and xorg-server ports.
642 The caching daemon (cached) was renamed to nscd. nscd.conf
643 configuration file should be used instead of cached.conf and
644 nscd_enable, nscd_pidfile and nscd_flags options should be used
645 instead of cached_enable, cached_pidfile and cached_flags in
649 The getfacl(1) utility now prints owning user and group name
650 instead of owning uid and gid in the three line comment header.
651 This is the same behavior as getfacl(1) on Solaris and Linux.
654 The new IPsec code is now compiled in using the IPSEC option. The
655 IPSEC option now requires "device crypto" be defined in your kernel
656 configuration. The FAST_IPSEC kernel option is now deprecated.
659 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
660 note the changed syntax - keep state is now on by default. Also
661 note the fact that ftp-proxy(8) has been changed from bottom up and
662 has been moved from libexec to usr/sbin. Changes in the ALTQ
663 handling also affect users of IPFW's ALTQ capabilities.
666 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
667 only IPsec supported by FreeBSD. The new IPsec stack
668 supports both IPv4 and IPv6. The kernel option will change
669 after the code changes have settled in. For now the kernel
670 option IPSEC is deprecated and FAST_IPSEC is the only option, that
671 will change after some settling time.
674 The wicontrol(8) utility has been removed from the base system. wi(4)
675 cards should be configured using ifconfig(8), see the man page for more
679 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
680 instead of the nve(4) driver. Please update your configuration
684 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
685 database if it is missing or older than the aliases file. If
686 desired, set the new rc.conf option sendmail_rebuild_aliases
687 to "YES" to restore that functionality.
690 The IPv4 multicast socket code has been considerably modified, and
691 moved to the file sys/netinet/in_mcast.c. Initial support for the
692 RFC 3678 Source-Specific Multicast Socket API has been added to
693 the IPv4 network stack.
695 Strict multicast and broadcast reception is now the default for
696 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
697 has now been removed.
699 The RFC 1724 hack for interface selection has been removed; the use
700 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
701 been added to replace it. Consumers such as routed will soon be
702 updated to reflect this.
704 These changes affect users who are running routed(8) or rdisc(8)
705 from the FreeBSD base system on point-to-point or unnumbered
709 The net80211 layer has changed significantly and all wireless
710 drivers that depend on it need to be recompiled. Further these
711 changes require that any program that interacts with the wireless
712 support in the kernel be recompiled; this includes: ifconfig,
713 wpa_supplicant, hostapd, and wlanstats. Users must also, for
714 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
715 if they use modules for wireless support. These modules implement
716 scanning support for station and ap modes, respectively. Failure
717 to load the appropriate module before marking a wireless interface
718 up will result in a message to the console and the device not
722 The pam_nologin(8) module ceases to provide an authentication
723 function and starts providing an account management function.
724 Consequent changes to /etc/pam.d should be brought in using
725 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
726 need manual editing as follows. Locate this line (or similar):
728 auth required pam_nologin.so no_warn
730 and change it according to this example:
732 account required pam_nologin.so no_warn
734 That is, the first word needs to be changed from "auth" to
735 "account". The new line can be moved to the account section
736 within the file for clarity. Not updating pam.conf(5) files
737 will result in nologin(5) ignored by the respective services.
740 The ether_ioctl() function has been synchronized with ioctl(2)
741 and ifnet.if_ioctl. Due to that, the size of one of its arguments
742 has changed on 64-bit architectures. All kernel modules using
743 ether_ioctl() need to be rebuilt on such architectures.
746 Improved INCLUDE_CONFIG_FILE support has been introduced to the
747 config(8) utility. In order to take advantage of this new
748 functionality, you are expected to recompile and install
749 src/usr.sbin/config. If you don't rebuild config(8), and your
750 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
751 build will be broken because of a missing "kernconfstring"
755 Symbol versioning is enabled by default. To disable it, use
756 option WITHOUT_SYMVER. It is not advisable to attempt to
757 disable symbol versioning once it is enabled; your installworld
758 will break because a symbol version-less libc will get installed
759 before the install tools. As a result, the old install tools,
760 which previously had symbol dependencies to FBSD_1.0, will fail
761 because the freshly installed libc will not have them.
763 The default threading library (providing "libpthread") has been
764 changed to libthr. If you wish to have libkse as your default,
765 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
768 The ABI breakage in sendmail(8)'s libmilter has been repaired
769 so it is no longer necessary to recompile mail filters (aka,
770 milters). If you recompiled mail filters after the 20070408
771 note, it is not necessary to recompile them again.
774 The new trunk(4) driver has been renamed to lagg(4) as it better
775 reflects its purpose. ifconfig will need to be recompiled.
778 sendmail(8) has been updated to version 8.14.1. Mail filters
779 (aka, milters) compiled against the libmilter included in the
780 base operating system should be recompiled.
783 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
784 In order to use them one must agree to the respective LICENSE in
785 share/doc/legal and define legal.intel_<name>.license_ack=1 via
786 loader.conf(5) or kenv(1). Make sure to deinstall the now
787 deprecated modules from the respective firmware ports.
790 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
791 were removed from FreeBSD's libc. These originally came from INRIA
792 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
793 deprecated in previous releases.
794 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
795 replace it as a more portable (and re-entrant) API.
798 To support interrupt filtering a modification to the newbus API
799 has occurred, ABI was broken and __FreeBSD_version was bumped
800 to 700031. Please make sure that your kernel and modules are in
802 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
805 The IPv6 multicast forwarding code may now be loaded into GENERIC
806 kernels by loading the ip_mroute.ko module. This is built into the
807 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
808 set; see src.conf(5) for more information.
811 The output of netstat -r has changed. Without -n, we now only
812 print a "network name" without the prefix length if the network
813 address and mask exactly match a Class A/B/C network, and an entry
814 exists in the nsswitch "networks" map.
815 With -n, we print the full unabbreviated CIDR network prefix in
816 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
817 This change is in preparation for changes such as equal-cost
818 multipath, and to more generally assist operational deployment
819 of FreeBSD as a modern IPv4 router.
822 PIM has been turned on by default in the IPv4 multicast
823 routing code. The kernel option 'PIM' has now been removed.
824 PIM is now built by default if option 'MROUTING' is specified.
825 It may now be loaded into GENERIC kernels by loading the
829 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
830 has been removed. Its functionality may be achieved by explicitly
831 configuring gif(4) interfaces and using the 'phyint' keyword in
833 XORP does not support source-routed IPv4 multicast tunnels nor the
834 integrated IPIP tunneling, therefore it is not affected by this
835 change. The __FreeBSD_version macro has been bumped to 700030.
838 Support for PCI Message Signalled Interrupts has been
839 re-enabled in the bge driver, only for those chips which are
840 believed to support it properly. If there are any problems,
841 MSI can be disabled completely by setting the
842 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
846 Support for PCI Message Signalled Interrupts has been
847 disabled again in the bge driver. Many revisions of the
848 hardware fail to support it properly. Support can be
849 re-enabled by removing the #define of BGE_DISABLE_MSI in
850 "src/sys/dev/bge/if_bge.c".
853 Support for PCI Message Signalled Interrupts has been added
854 to the bge driver. If there are any problems, MSI can be
855 disabled completely by setting the 'hw.pci.enable_msi' and
856 'hw.pci.enable_msix' tunables to 0 in the loader.
859 The removal of several facets of the experimental Threading
860 system from the kernel means that the proc and thread structures
861 have changed quite a bit. I suggest all kernel modules that might
862 reference these structures be recompiled.. Especially the
866 Sound infrastructure has been updated with various fixes and
867 improvements. Most of the changes are pretty much transparent,
868 with exceptions of followings:
869 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
870 moved to their own dev sysctl nodes, for example:
871 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
872 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
873 own chardev in the form of "dsp%d.<function>%d", where <function>
874 is p = playback, r = record and v = virtual, respectively. Users
875 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
876 This does not affect those who are using "/dev/dsp".
879 geom(4)'s gmirror(8) class metadata structure has been
880 rev'd from v3 to v4. If you update across this point and
881 your metadata is converted for you, you will not be easily
882 able to downgrade since the /boot/kernel.old/geom_mirror.ko
883 kernel module will be unable to read the v4 metadata. You
884 can resolve this by doing from the loader(8) prompt:
886 set vfs.root.mountfrom="ufs:/dev/XXX"
888 where XXX is the root slice of one of the disks that composed
889 the mirror (i.e.: /dev/ad0s1a). You can then rebuild
890 the array the same way you built it originally.
893 The following binaries have been disconnected from the build:
894 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
895 and mount_std. The functionality of these programs has been
896 moved into the mount program. For example, to mount a devfs
897 filesystem, instead of using mount_devfs, use: "mount -t devfs".
898 This does not affect entries in /etc/fstab, since entries in
899 /etc/fstab are always processed with "mount -t fstype".
902 Support for PCI Message Signalled Interrupts on i386 and amd64
903 has been added to the kernel and various drivers will soon be
904 updated to use MSI when it is available. If there are any problems,
905 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
906 and 'hw.pci.enable_msix' tunables to 0 in the loader.
909 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
910 The lockmgr object layout has been changed as a result of having
911 a lock_object embedded in it. As a consequence all file system
912 kernel modules must be re-compiled. The mutex profiling man page
913 has not yet been updated to reflect this change.
916 KSE in the kernel has now been made optional and turned on by
917 default. Use 'nooption KSE' in your kernel config to turn it
918 off. All kernel modules *must* be recompiled after this change.
919 There-after, modules from a KSE kernel should be compatible with
920 modules from a NOKSE kernel due to the temporary padding fields
921 added to 'struct proc'.
924 mrouted and its utilities have been removed from the base system.
927 Some ioctl(2) command codes have changed. Full backward ABI
928 compatibility is provided if the "options COMPAT_FREEBSD6" is
929 present in the kernel configuration file. Make sure to add
930 this option to your kernel config file, or recompile X.Org
931 and the rest of ports; otherwise they may refuse to work.
934 tcpslice has been removed from the base system.
937 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
938 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
939 systat needs to be rebuilt.
942 libpcap updated to v0.9.4 and tcpdump to v3.9.4
945 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
946 for IPFIREWALL_FORWARD is now as it was before when it was first
947 committed and for years after. The behaviour is now ON.
950 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
951 Now it can decrypt files created from different architectures.
952 Unfortunately, it is no longer able to decrypt a cipher text
953 generated with an older version on 64 bit architectures.
954 If you have such a file, you need old utility to decrypt it.
957 The interface version of the i4b kernel part has changed. So
958 after updating the kernel sources and compiling a new kernel,
959 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
960 be rebuilt, and vice versa.
963 The XBOX kernel now defaults to the nfe(4) driver instead of
964 the nve(4) driver. Please update your configuration
968 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
969 PCnet family of NICs has been removed. The new le(4) driver serves
970 as an equivalent but cross-platform replacement with the pcn(4)
971 driver still providing performance-optimized support for the subset
972 of AMD Am79C971 PCnet-FAST and greater chips as before.
975 The machdep.* sysctls and the adjkerntz utility have been
976 modified a bit. The new adjkerntz utility uses the new
977 sysctl names and sysctlbyname() calls, so it may be impossible
978 to run an old /sbin/adjkerntz utility in single-user mode
979 with a new kernel. Replace the `adjkerntz -i' step before
980 `make installworld' with:
982 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
984 and proceed as usual with the rest of the installworld-stage
985 steps. Otherwise, you risk installing binaries with their
986 timestamp set several hours in the future, especially if
987 you are running with local time set to GMT+X hours.
990 The ip6fw utility has been removed. The behavior provided by
991 ip6fw has been in ipfw2 for a good while and the rc.d scripts
992 have been updated to deal with it. There are some rules that
993 might not migrate cleanly. Use rc.firewall6 as a template to
997 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
998 attachments have been removed. Make sure to configure scc(4)
999 on sparc64. Note also that by default puc(4) will use uart(4)
1000 and not sio(4) for serial ports because interrupt handling has
1001 been optimized for multi-port serial cards and only uart(4)
1002 implements the interface to support it.
1005 The scc(4) driver replaces puc(4) for Serial Communications
1006 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
1007 Z8530. On sparc64, it is advised to add scc(4) to the kernel
1008 configuration to make sure that the serial ports remain
1012 Most world/kernel related NO_* build options changed names.
1013 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
1014 after FreeBSD ports) and should be set in /etc/src.conf
1015 (the src.conf(5) manpage is provided). Full backwards
1016 compatibility is maintained for the time being though it's
1017 highly recommended to start moving old options out of the
1018 system-wide /etc/make.conf file into the new /etc/src.conf
1019 while also properly renaming them. More conversions will
1020 likely follow. Posting to current@:
1022 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
1025 The NETSMBCRYPTO kernel option has been retired because its
1026 functionality is always included in NETSMB and smbfs.ko now.
1029 The TDFX_LINUX kernel option was retired and replaced by the
1030 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
1031 kernel module. Loading it alone should suffice to get 3dfx support
1032 for Linux apps because it will pull in 3dfx.ko and linux.ko through
1036 The 'audit' group was added to support the new auditing functionality
1037 in the base system. Be sure to follow the directions for updating,
1038 including the requirement to run mergemaster -p.
1041 The kernel ABI to file system modules was changed on i386.
1042 Please make sure that your kernel and modules are in sync.
1045 This actually occured some time ago, but installing the kernel
1046 now also installs a bunch of symbol files for the kernel modules.
1047 This increases the size of /boot/kernel to about 67Mbytes. You
1048 will need twice this if you will eventually back this up to kernel.old
1049 on your next install.
1050 If you have a shortage of room in your root partition, you should add
1051 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
1052 to your /etc/make.conf.
1055 libc's malloc implementation has been replaced. This change has the
1056 potential to uncover application bugs that previously went unnoticed.
1057 See the malloc(3) manual page for more details.
1060 The generic netgraph(4) cookie has been changed. If you upgrade
1061 kernel passing this point, you also need to upgrade userland
1062 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
1065 si(4)'s device files now contain the unit number.
1066 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
1069 The kernel ABI was mostly destroyed due to a change in the size
1070 of struct lock_object which is nested in other structures such
1071 as mutexes which are nested in all sorts of other structures.
1072 Make sure your kernel and modules are in sync.
1075 The page coloring algorithm in the VM subsystem was converted
1076 from tuning with kernel options to autotuning. Please remove
1077 any PQ_* option except PQ_NOOPT from your kernel config.
1080 The net80211-related tools in the tools/tools/ath directory
1081 have been moved to tools/tools/net80211 and renamed with a
1082 "wlan" prefix. Scripts that use them should be adjusted
1086 Scripts in the local_startup directories (as defined in
1087 /etc/defaults/rc.conf) that have the new rc.d semantics will
1088 now be run as part of the base system rcorder. If there are
1089 errors or problems with one of these local scripts, it could
1090 cause boot problems. If you encounter such problems, boot in
1091 single user mode, remove that script from the */rc.d directory.
1092 Please report the problem to the port's maintainer, and the
1093 freebsd-ports@freebsd.org mailing list.
1096 The nodev mount option was deprecated in RELENG_6 (where it
1097 was a no-op), and is now unsupported. If you have nodev or dev listed
1098 in /etc/fstab, remove it, otherwise it will result in a mount error.
1101 ABI between ipfw(4) and ipfw(8) has been changed. You need
1102 to rebuild ipfw(8) when rebuilding kernel.
1105 rp(4)'s device files now contain the unit number.
1106 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
1109 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
1110 Its /etc/rc.conf.d configuration file has been `ppp' from
1111 the beginning, and hence there is no need to touch it.
1114 Now most modules get their build-time options from the kernel
1115 configuration file. A few modules still have fixed options
1116 due to their non-conformant implementation, but they will be
1117 corrected eventually. You may need to review the options of
1118 the modules in use, explicitly specify the non-default options
1119 in the kernel configuration file, and rebuild the kernel and
1123 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
1124 to turn polling(4) on your interfaces.
1127 The old bridge(4) implementation was retired. The new
1128 if_bridge(4) serves as a full functional replacement.
1131 The ai_addrlen of a struct addrinfo was changed to a socklen_t
1132 to conform to POSIX-2001. This change broke an ABI
1133 compatibility on 64 bit architecture. You have to recompile
1134 userland programs that use getaddrinfo(3) on 64 bit
1138 RELENG_6 branched here.
1141 The pccard_ifconfig rc.conf variable has been removed and a new
1142 variable, ifconfig_DEFAULT has been introduced. Unlike
1143 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
1144 do not have ifconfig_ifn entries rather than just those in
1145 removable_interfaces.
1148 Some previous versions of PAM have permitted the use of
1149 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
1150 to third party PAM modules in /usr/local/lib. A change has been
1151 made to require the use of absolute paths in order to avoid
1152 ambiguity and dependence on library path configuration, which may
1153 affect existing configurations.
1156 Major changes to network interface API. All drivers must be
1157 recompiled. Drivers not in the base system will need to be
1158 updated to the new APIs.
1161 Changes were made to kinfo_proc in sys/user.h. Please recompile
1162 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
1163 will not behave correctly.
1165 The API and ABI for hwpmc(4) have changed with the addition
1166 of sampling support. Please recompile lib/libpmc(3) and
1167 usr.sbin/{pmcstat,pmccontrol}.
1170 The OpenBSD dhclient was imported in place of the ISC dhclient
1171 and the network interface configuration scripts were updated
1172 accordingly. If you use DHCP to configure your interfaces, you
1173 must now run devd. Also, DNS updating was lost so you will need
1174 to find a workaround if you use this feature.
1176 The '_dhcp' user was added to support the OpenBSD dhclient. Be
1177 sure to run mergemaster -p (like you are supposed to do every time
1181 if_bridge was added to the tree. This has changed struct ifnet.
1182 Please recompile userland and all network related modules.
1185 The n_net of a struct netent was changed to an uint32_t, and
1186 1st argument of getnetbyaddr() was changed to an uint32_t, to
1187 conform to POSIX-2001. These changes broke an ABI
1188 compatibility on 64 bit architecture. With these changes,
1189 shlib major of libpcap was bumped. You have to recompile
1190 userland programs that use getnetbyaddr(3), getnetbyname(3),
1191 getnetent(3) and/or libpcap on 64 bit architecture.
1194 Kernel parsing of extra options on '#!' first lines of shell
1195 scripts has changed. Lines with multiple options likely will
1196 fail after this date. For full details, please see
1197 http://people.freebsd.org/~gad/Updating-20050528.txt
1200 The packet filter (pf) code has been updated to OpenBSD 3.7
1201 Please note the changed anchor syntax and the fact that
1202 authpf(8) now needs a mounted fdescfs(5) to function.
1205 The NO_MIXED_MODE kernel option has been removed from the i386
1206 amd64 platforms as its use has been superceded by the new local
1207 APIC timer code. Any kernel config files containing this option
1211 The on-disk format of LC_CTYPE files was changed to be machine
1212 independent. Please make sure NOT to use NO_CLEAN buildworld
1213 when crossing this point. Crossing this point also requires
1214 recompile or reinstall of all locale depended packages.
1217 The ifi_epoch member of struct if_data has been changed to
1218 contain the uptime at which the interface was created or the
1219 statistics zeroed rather then the wall clock time because
1220 wallclock time may go backwards. This should have no impact
1221 unless an snmp implementation is using this value (I know of
1222 none at this point.)
1225 The acpi_perf and acpi_throttle drivers are now part of the
1226 acpi(4) main module. They are no longer built separately.
1229 The layout of struct image_params has changed. You have to
1230 recompile all compatibility modules (linux, svr4, etc) for use
1231 with the new kernel.
1234 The p4tcc driver has been merged into cpufreq(4). This makes
1235 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
1236 compile in "device cpufreq" to restore this functionality.
1239 The responsibility of recomputing the file system summary of
1240 a SoftUpdates-enabled dirty volume has been transferred to the
1241 background fsck. A rebuild of fsck(8) utility is recommended
1242 if you have updated the kernel.
1244 To get the old behavior (recompute file system summary at mount
1245 time), you can set vfs.ffs.compute_summary_at_mount=1 before
1246 mounting the new volume.
1249 The cpufreq import is complete. As part of this, the sysctls for
1250 acpi(4) throttling have been removed. The power_profile script
1251 has been updated, so you can use performance/economy_cpu_freq in
1252 rc.conf(5) to set AC on/offline cpu frequencies.
1255 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
1256 requires recompiling libnetgraph and userland netgraph utilities.
1259 Support for abbreviated forms of a number of ipfw options is
1260 now deprecated. Warnings are printed to stderr indicating the
1261 correct full form when a match occurs. Some abbreviations may
1262 be supported at a later date based on user feedback. To be
1263 considered for support, abbreviations must be in use prior to
1264 this commit and unlikely to be confused with current key words.
1267 By a popular demand, a lot of NOFOO options were renamed
1268 to NO_FOO (see bsd.compat.mk for a full list). The old
1269 spellings are still supported, but will cause annoying
1270 warnings on stderr. Make sure you upgrade properly (see
1271 the COMMON ITEMS: section later in this file).
1274 Auto-loading of ancillary wlan modules such as wlan_wep has
1275 been temporarily disabled; you need to statically configure
1276 the modules you need into your kernel or explicitly load them
1277 prior to use. Specifically, if you intend to use WEP encryption
1278 with an 802.11 device load/configure wlan_wep; if you want to
1279 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
1280 and wlan_xauth as required.
1283 The behaviour of ppp(8) has changed slightly. If lqr is enabled
1284 (``enable lqr''), older versions would revert to LCP ECHO mode on
1285 negotiation failure. Now, ``enable echo'' is required for this
1286 behaviour. The ppp version number has been bumped to 3.4.2 to
1290 The wlan support has been updated to split the crypto support
1291 into separate modules. For static WEP you must configure the
1292 wlan_wep module in your system or build and install the module
1293 in place where it can be loaded (the kernel will auto-load
1294 the module when a wep key is configured).
1297 The ath driver has been updated to split the tx rate control
1298 algorithm into a separate module. You need to include either
1299 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
1302 Support for systems with an 80386 CPU has been removed. Please
1303 use FreeBSD 5.x or earlier on systems with an 80386.
1306 We have had a hack which would mount the root filesystem
1307 R/W if the device were named 'md*'. As part of the vnode
1308 work I'm doing I have had to remove this hack. People
1309 building systems which use preloaded MD root filesystems
1310 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
1311 their /etc/rc scripts.
1314 FreeBSD 5.3 shipped here.
1317 The size of struct tcpcb has changed again due to the removal
1318 of RFC1644 T/TCP. You have to recompile userland programs that
1319 read kmem for tcp sockets directly (netstat, sockstat, etc.)
1322 The size of struct tcpcb has changed. You have to recompile
1323 userland programs that read kmem for tcp sockets directly
1324 (netstat, sockstat, etc.)
1327 RELENG_5 branched here. For older entries, please see updating
1328 in the RELENG_5 branch.
1334 Avoid using make -j when upgrading. From time to time in the
1335 past there have been problems using -j with buildworld and/or
1336 installworld. This is especially true when upgrading between
1337 "distant" versions (eg one that cross a major release boundary
1338 or several minor releases, or when several months have passed
1339 on the -current branch).
1341 Sometimes, obscure build problems are the result of environment
1342 poisoning. This can happen because the make utility reads its
1343 environment when searching for values for global variables.
1344 To run your build attempts in an "environmental clean room",
1345 prefix all make commands with 'env -i '. See the env(1) manual
1346 page for more details.
1348 When upgrading from one major version to another it is generally
1349 best to upgrade to the latest code in the currently installed branch
1350 first, then do an upgrade to the new branch. This is the best-tested
1351 upgrade path, and has the highest probability of being successful.
1352 Please try this approach before reporting problems with a major
1357 If you are updating from a prior version of FreeBSD (even one just
1358 a few days old), you should follow this procedure. It is the most
1359 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1361 make kernel-toolchain
1362 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1363 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1365 To test a kernel once
1366 ---------------------
1367 If you just want to boot a kernel once (because you are not sure
1368 if it works, or if you want to boot a known bad kernel to provide
1369 debugging information) run
1370 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1371 nextboot -k testkernel
1373 To just build a kernel when you know that it won't mess you up
1374 --------------------------------------------------------------
1375 This assumes you are already running a 5.X system. Replace
1376 ${arch} with the architecture of your machine (e.g. "i386",
1377 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1379 cd src/sys/${arch}/conf
1380 config KERNEL_NAME_HERE
1381 cd ../compile/KERNEL_NAME_HERE
1386 If this fails, go to the "To build a kernel" section.
1388 To rebuild everything and install it on the current system.
1389 -----------------------------------------------------------
1390 # Note: sometimes if you are running current you gotta do more than
1391 # is listed here if you are upgrading from a really old current.
1393 <make sure you have good level 0 dumps>
1395 make kernel KERNCONF=YOUR_KERNEL_HERE
1397 <reboot in single user> [3]
1405 To cross-install current onto a separate partition
1406 --------------------------------------------------
1407 # In this approach we use a separate partition to hold
1408 # current's root, 'usr', and 'var' directories. A partition
1409 # holding "/", "/usr" and "/var" should be about 2GB in
1412 <make sure you have good level 0 dumps>
1415 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1416 <maybe newfs current's root partition>
1417 <mount current's root partition on directory ${CURRENT_ROOT}>
1418 make installworld DESTDIR=${CURRENT_ROOT}
1419 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1420 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1421 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1422 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1423 <reboot into current>
1424 <do a "native" rebuild/install as described in the previous section>
1425 <maybe install compatibility libraries from ports/misc/compat*>
1429 To upgrade in-place from 5.x-stable to current
1430 ----------------------------------------------
1431 <make sure you have good level 0 dumps>
1433 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1435 <reboot in single user> [3]
1442 Make sure that you've read the UPDATING file to understand the
1443 tweaks to various things you need. At this point in the life
1444 cycle of current, things change often and you are on your own
1445 to cope. The defaults can also change, so please read ALL of
1446 the UPDATING entries.
1448 Also, if you are tracking -current, you must be subscribed to
1449 freebsd-current@freebsd.org. Make sure that before you update
1450 your sources that you have read and understood all the recent
1451 messages there. If in doubt, please track -stable which has
1452 much fewer pitfalls.
1454 [1] If you have third party modules, such as vmware, you
1455 should disable them at this point so they don't crash your
1458 [3] From the bootblocks, boot -s, and then do
1463 adjkerntz -i # if CMOS is wall time
1464 Also, when doing a major release upgrade, it is required that
1465 you boot into single user mode to do the installworld.
1467 [4] Note: This step is non-optional. Failure to do this step
1468 can result in a significant reduction in the functionality of the
1469 system. Attempting to do it by hand is not recommended and those
1470 that pursue this avenue should read this file carefully, as well
1471 as the archives of freebsd-current and freebsd-hackers mailing lists
1472 for potential gotchas.
1474 [5] Usually this step is a noop. However, from time to time
1475 you may need to do this if you get unknown user in the following
1476 step. It never hurts to do it all the time. You may need to
1477 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1478 install) after the buildworld before this step if you last updated
1479 from current before 20020224 or from -stable before 20020408.
1481 [8] In order to have a kernel that can run the 4.x binaries
1482 needed to do an installworld, you must include the COMPAT_FREEBSD4
1483 option in your kernel. Failure to do so may leave you with a system
1484 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
1485 is required to run the 5.x binaries on more recent kernels.
1487 Make sure that you merge any new devices from GENERIC since the
1488 last time you updated your kernel config file.
1490 [9] When checking out sources, you must include the -P flag to have
1491 cvs prune empty directories.
1493 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1494 "?=" instead of the "=" assignment operator, so that buildworld can
1495 override the CPUTYPE if it needs to.
1497 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1498 not on the command line, or in /etc/make.conf. buildworld will
1499 warn if it is improperly defined.
1502 This file contains a list, in reverse chronological order, of major
1503 breakages in tracking -current. Not all things will be listed here,
1504 and it only starts on October 16, 2004. Updating files can found in
1505 previous releases if your system is older than this.
1507 Copyright information:
1509 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
1511 Redistribution, publication, translation and use, with or without
1512 modification, in full or in part, in any form or format of this
1513 document are permitted without further permission from the author.
1515 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1516 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1517 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1518 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1519 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1520 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1521 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1522 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1523 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1524 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1525 POSSIBILITY OF SUCH DAMAGE.
1527 If you find this document useful, and you want to, you may buy the
1530 Contact Warner Losh if you have any questions about your use of