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 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
27 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
28 800061. User space tools that rely on the size of struct tcpcb in
29 tcp_var.h (e.g. sockstat) need to be recompiled.
32 ng_tty(4) module updated to match the new TTY subsystem.
33 Due to API change, user-level applications must be updated.
34 New API support added to mpd5 CVS and expected to be present
35 in next mpd5.3 release.
38 With __FreeBSD_version 800060 the makefs tool is part of
39 the base system (it was a port).
42 The afdata and ifnet locks have been changed from mutexes to
43 rwlocks, network modules will need to be re-compiled.
46 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
47 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
48 The new code reduced struct rtentry{} by 16 bytes on 32-bit
49 architecture and 40 bytes on 64-bit architecture. The userland
50 applications "arp" and "ndp" have been updated accordingly.
51 The output from "netstat -r" shows only routing entries and
52 none of the L2 information.
55 __FreeBSD_version 800057 marks the switchover from the
56 binary ath hal to source code. Users must add the line:
58 options AH_SUPPORT_AR5416
60 to their kernel config files when specifying:
64 The ath_hal module no longer exists; the code is now compiled
65 together with the driver in the ath module. It is now
66 possible to tailor chip support (i.e. reduce the set of chips
67 and thereby the code size); consult ath_hal(4) for details.
70 __FreeBSD_version 800054 adds memory barriers to
71 <machine/atomic.h>, new interfaces to ifnet to facilitate
72 multiple hardware transmit queues for cards that support
73 them, and a lock-less ring-buffer implementation to
74 enable drivers to more efficiently manage queueing of
78 A new version of ZFS (version 13) has been merged to -HEAD.
79 This version has zpool attribute "listsnapshots" off by
80 default, which means "zfs list" does not show snapshots,
81 and is the same as Solaris behavior.
84 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
87 The uhci, ohci, ehci and slhci USB Host controller drivers have
88 been put into separate modules. If you load the usb module
89 separately through loader.conf you will need to load the
90 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
91 controller add the following to loader.conf:
97 The ABI used by the PMC toolset has changed. Please keep
98 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
102 The TTY subsystem of the kernel has been replaced by a new
103 implementation, which provides better scalability and an
104 improved driver model. Most common drivers have been migrated to
105 the new TTY subsystem, while others have not. The following
106 drivers have not yet been ported to the new TTY layer:
109 cy, digi, rc, rp, sio
115 ng_h4, ng_tty, ppp, sl, snp
117 Adding these drivers to your kernel configuration file shall
118 cause compilation to fail.
121 ntpd has been upgraded to 4.2.4p5.
124 OpenSSH has been upgraded to 5.1p1.
126 For many years, FreeBSD's version of OpenSSH preferred DSA
127 over RSA for host and user authentication keys. With this
128 upgrade, we've switched to the vendor's default of RSA over
129 DSA. This may cause upgraded clients to warn about unknown
130 host keys even for previously known hosts. Users should
131 follow the usual procedure for verifying host keys before
132 accepting the RSA key.
134 This can be circumvented by setting the "HostKeyAlgorithms"
135 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
138 Please note that the sequence of keys offered for
139 authentication has been changed as well. You may want to
140 specify IdentityFile in a different order to revert this
144 The sio(4) driver has been removed from the i386 and amd64
145 kernel configuration files. This means uart(4) is now the
146 default serial port driver on those platforms as well.
148 To prevent collisions with the sio(4) driver, the uart(4) driver
149 uses different names for its device nodes. This means the
150 onboard serial port will now most likely be called "ttyu0"
151 instead of "ttyd0". You may need to reconfigure applications to
152 use the new device names.
154 When using the serial port as a boot console, be sure to update
155 /boot/device.hints and /etc/ttys before booting the new kernel.
156 If you forget to do so, you can still manually specify the hints
157 at the loader prompt:
159 set hint.uart.0.at="isa"
160 set hint.uart.0.port="0x3F8"
161 set hint.uart.0.flags="0x10"
162 set hint.uart.0.irq="4"
166 The gpt(8) utility has been removed. Use gpart(8) to partition
170 The version that Linuxulator emulates was changed from 2.4.2
171 to 2.6.16. If you experience any problems with Linux binaries
172 please try to set sysctl compat.linux.osrelease to 2.4.2 and
173 if it fixes the problem contact emulation mailing list.
176 ISDN4BSD (I4B) was removed from the src tree. You may need to
177 update a your kernel configuration and remove relevant entries.
180 I have checked in code to support multiple routing tables.
181 See the man pages setfib(1) and setfib(2).
182 This is a hopefully backwards compatible version,
183 but to make use of it you need to compile your kernel
184 with options ROUTETABLES=2 (or more up to 16).
187 The 802.11 wireless support was redone to enable multi-bss
188 operation on devices that are capable. The underlying device
189 is no longer used directly but instead wlanX devices are
190 cloned with ifconfig. This requires changes to rc.conf files.
192 ifconfig_ath0="WPA DHCP"
195 ifconfig_wlan0="WPA DHCP"
196 see rc.conf(5) for more details. In addition, mergemaster of
197 /etc/rc.d is highly recommended. Simultaneous update of userland
198 and kernel wouldn't hurt either.
200 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
201 modules were merged into the base wlan module. All references
202 to these modules (e.g. in kernel config files) must be removed.
205 psm(4) has gained write(2) support in native operation level.
206 Arbitrary commands can be written to /dev/psm%d and status can
207 be read back from it. Therefore, an application is responsible
208 for status validation and error recovery. It is a no-op in
209 other operation levels.
212 Support for KSE threading has been removed from the kernel. To
213 run legacy applications linked against KSE libmap.conf may
214 be used. The following libmap.conf may be used to ensure
215 compatibility with any prior release:
217 libpthread.so.1 libthr.so.1
218 libpthread.so.2 libthr.so.2
219 libkse.so.3 libthr.so.3
222 The layout of struct vmspace has changed. This affects libkvm
223 and any executables that link against libkvm and use the
224 kvm_getprocs() function. In particular, but not exclusively,
225 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
226 The effects are minimal, but it's advisable to upgrade world
230 The latest em driver no longer has support in it for the
231 82575 adapter, this is now moved to the igb driver. The
232 split was done to make new features that are incompatible
233 with older hardware easier to do.
236 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
237 likewise the kernel option is now GEOM_LINUX_LVM.
240 The default NFS mount mode has changed from UDP to TCP for
241 increased reliability. If you rely on (insecurely) NFS
242 mounting across a firewall you may need to update your
246 Belatedly note the addition of m_collapse for compacting
250 The fts(3) structures have been changed to use adequate
251 integer types for their members and so to be able to cope
252 with huge file trees. The old fts(3) ABI is preserved
253 through symbol versioning in libc, so third-party binaries
254 using fts(3) should still work, although they will not take
255 advantage of the extended types. At the same time, some
256 third-party software might fail to build after this change
257 due to unportable assumptions made in its source code about
258 fts(3) structure members. Such software should be fixed
259 by its vendor or, in the worst case, in the ports tree.
260 FreeBSD_version 800015 marks this change for the unlikely
261 case that a portable fix is impossible.
264 To upgrade to -current after this date, you must be running
265 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
266 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
269 The ADAPTIVE_GIANT kernel option has been retired because its
270 functionality is the default now.
273 The AT keyboard emulation of sunkbd(4) has been turned on
274 by default. In order to make the special symbols of the Sun
275 keyboards driven by sunkbd(4) work under X these now have
276 to be configured the same way as Sun USB keyboards driven
277 by ukbd(4) (which also does AT keyboard emulation), f.e.:
279 Option "XkbLayout" "us"
280 Option "XkbRules" "xorg"
281 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
284 It has been decided that it is desirable to provide ABI
285 backwards compatibility to the FreeBSD 4/5/6 versions of the
286 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
287 broken with the introduction of PCI domain support (see the
288 20070930 entry). Unfortunately, this required the ABI of
289 PCIOCGETCONF to be broken again in order to be able to
290 provide backwards compatibility to the old version of that
291 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
292 again. As for prominent ports this affects neither pciutils
293 nor xorg-server this time, the hal port needs to be rebuilt
297 The misnamed kthread_create() and friends have been renamed
298 to kproc_create() etc. Many of the callers already
300 I will return kthread_create() and friends in a while
301 with implementations that actually create threads, not procs.
302 Renaming corresponds with version 800002.
308 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
309 WITHOUT_LIBTHR are set.
312 The PCI code has been made aware of PCI domains. This means that
313 the location strings as used by pciconf(8) etc are now in the
314 following format: pci<domain>:<bus>:<device>[:<function>]. It
315 also means that consumers of <sys/pciio.h> potentially need to
316 be recompiled; this includes the hal and xorg-server ports.
319 The caching daemon (cached) was renamed to nscd. nscd.conf
320 configuration file should be used instead of cached.conf and
321 nscd_enable, nscd_pidfile and nscd_flags options should be used
322 instead of cached_enable, cached_pidfile and cached_flags in
326 The getfacl(1) utility now prints owning user and group name
327 instead of owning uid and gid in the three line comment header.
328 This is the same behavior as getfacl(1) on Solaris and Linux.
331 The new IPsec code is now compiled in using the IPSEC option. The
332 IPSEC option now requires "device crypto" be defined in your kernel
333 configuration. The FAST_IPSEC kernel option is now deprecated.
336 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
337 note the changed syntax - keep state is now on by default. Also
338 note the fact that ftp-proxy(8) has been changed from bottom up and
339 has been moved from libexec to usr/sbin. Changes in the ALTQ
340 handling also affect users of IPFW's ALTQ capabilities.
343 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
344 only IPsec supported by FreeBSD. The new IPsec stack
345 supports both IPv4 and IPv6. The kernel option will change
346 after the code changes have settled in. For now the kernel
347 option IPSEC is deprecated and FAST_IPSEC is the only option, that
348 will change after some settling time.
351 The wicontrol(8) utility has been removed from the base system. wi(4)
352 cards should be configured using ifconfig(8), see the man page for more
356 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
357 instead of the nve(4) driver. Please update your configuration
361 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
362 database if it is missing or older than the aliases file. If
363 desired, set the new rc.conf option sendmail_rebuild_aliases
364 to "YES" to restore that functionality.
367 The IPv4 multicast socket code has been considerably modified, and
368 moved to the file sys/netinet/in_mcast.c. Initial support for the
369 RFC 3678 Source-Specific Multicast Socket API has been added to
370 the IPv4 network stack.
372 Strict multicast and broadcast reception is now the default for
373 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
374 has now been removed.
376 The RFC 1724 hack for interface selection has been removed; the use
377 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
378 been added to replace it. Consumers such as routed will soon be
379 updated to reflect this.
381 These changes affect users who are running routed(8) or rdisc(8)
382 from the FreeBSD base system on point-to-point or unnumbered
386 The net80211 layer has changed significantly and all wireless
387 drivers that depend on it need to be recompiled. Further these
388 changes require that any program that interacts with the wireless
389 support in the kernel be recompiled; this includes: ifconfig,
390 wpa_supplicant, hostapd, and wlanstats. Users must also, for
391 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
392 if they use modules for wireless support. These modules implement
393 scanning support for station and ap modes, respectively. Failure
394 to load the appropriate module before marking a wireless interface
395 up will result in a message to the console and the device not
399 The pam_nologin(8) module ceases to provide an authentication
400 function and starts providing an account management function.
401 Consequent changes to /etc/pam.d should be brought in using
402 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
403 need manual editing as follows. Locate this line (or similar):
405 auth required pam_nologin.so no_warn
407 and change it according to this example:
409 account required pam_nologin.so no_warn
411 That is, the first word needs to be changed from "auth" to
412 "account". The new line can be moved to the account section
413 within the file for clarity. Not updating pam.conf(5) files
414 will result in nologin(5) ignored by the respective services.
417 The ether_ioctl() function has been synchronized with ioctl(2)
418 and ifnet.if_ioctl. Due to that, the size of one of its arguments
419 has changed on 64-bit architectures. All kernel modules using
420 ether_ioctl() need to be rebuilt on such architectures.
423 Improved INCLUDE_CONFIG_FILE support has been introduced to the
424 config(8) utility. In order to take advantage of this new
425 functionality, you are expected to recompile and install
426 src/usr.sbin/config. If you don't rebuild config(8), and your
427 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
428 build will be broken because of a missing "kernconfstring"
432 Symbol versioning is enabled by default. To disable it, use
433 option WITHOUT_SYMVER. It is not advisable to attempt to
434 disable symbol versioning once it is enabled; your installworld
435 will break because a symbol version-less libc will get installed
436 before the install tools. As a result, the old install tools,
437 which previously had symbol dependencies to FBSD_1.0, will fail
438 because the freshly installed libc will not have them.
440 The default threading library (providing "libpthread") has been
441 changed to libthr. If you wish to have libkse as your default,
442 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
445 The ABI breakage in sendmail(8)'s libmilter has been repaired
446 so it is no longer necessary to recompile mail filters (aka,
447 milters). If you recompiled mail filters after the 20070408
448 note, it is not necessary to recompile them again.
451 The new trunk(4) driver has been renamed to lagg(4) as it better
452 reflects its purpose. ifconfig will need to be recompiled.
455 sendmail(8) has been updated to version 8.14.1. Mail filters
456 (aka, milters) compiled against the libmilter included in the
457 base operating system should be recompiled.
460 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
461 In order to use them one must agree to the respective LICENSE in
462 share/doc/legal and define legal.intel_<name>.license_ack=1 via
463 loader.conf(5) or kenv(1). Make sure to deinstall the now
464 deprecated modules from the respective firmware ports.
467 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
468 were removed from FreeBSD's libc. These originally came from INRIA
469 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
470 deprecated in previous releases.
471 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
472 replace it as a more portable (and re-entrant) API.
475 To support interrupt filtering a modification to the newbus API
476 has occurred, ABI was broken and __FreeBSD_version was bumped
477 to 700031. Please make sure that your kernel and modules are in
479 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
482 The IPv6 multicast forwarding code may now be loaded into GENERIC
483 kernels by loading the ip_mroute.ko module. This is built into the
484 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
485 set; see src.conf(5) for more information.
488 The output of netstat -r has changed. Without -n, we now only
489 print a "network name" without the prefix length if the network
490 address and mask exactly match a Class A/B/C network, and an entry
491 exists in the nsswitch "networks" map.
492 With -n, we print the full unabbreviated CIDR network prefix in
493 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
494 This change is in preparation for changes such as equal-cost
495 multipath, and to more generally assist operational deployment
496 of FreeBSD as a modern IPv4 router.
499 PIM has been turned on by default in the IPv4 multicast
500 routing code. The kernel option 'PIM' has now been removed.
501 PIM is now built by default if option 'MROUTING' is specified.
502 It may now be loaded into GENERIC kernels by loading the
506 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
507 has been removed. Its functionality may be achieved by explicitly
508 configuring gif(4) interfaces and using the 'phyint' keyword in
510 XORP does not support source-routed IPv4 multicast tunnels nor the
511 integrated IPIP tunneling, therefore it is not affected by this
512 change. The __FreeBSD_version macro has been bumped to 700030.
515 Support for PCI Message Signalled Interrupts has been
516 re-enabled in the bge driver, only for those chips which are
517 believed to support it properly. If there are any problems,
518 MSI can be disabled completely by setting the
519 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
523 Support for PCI Message Signalled Interrupts has been
524 disabled again in the bge driver. Many revisions of the
525 hardware fail to support it properly. Support can be
526 re-enabled by removing the #define of BGE_DISABLE_MSI in
527 "src/sys/dev/bge/if_bge.c".
530 Support for PCI Message Signalled Interrupts has been added
531 to the bge driver. If there are any problems, MSI can be
532 disabled completely by setting the 'hw.pci.enable_msi' and
533 'hw.pci.enable_msix' tunables to 0 in the loader.
536 The removal of several facets of the experimental Threading
537 system from the kernel means that the proc and thread structures
538 have changed quite a bit. I suggest all kernel modules that might
539 reference these structures be recompiled.. Especially the
543 Sound infrastructure has been updated with various fixes and
544 improvements. Most of the changes are pretty much transparent,
545 with exceptions of followings:
546 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
547 moved to their own dev sysctl nodes, for example:
548 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
549 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
550 own chardev in the form of "dsp%d.<function>%d", where <function>
551 is p = playback, r = record and v = virtual, respectively. Users
552 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
553 This does not affect those who are using "/dev/dsp".
556 geom(4)'s gmirror(8) class metadata structure has been
557 rev'd from v3 to v4. If you update across this point and
558 your metadata is converted for you, you will not be easily
559 able to downgrade since the /boot/kernel.old/geom_mirror.ko
560 kernel module will be unable to read the v4 metadata. You
561 can resolve this by doing from the loader(8) prompt:
563 set vfs.root.mountfrom="ufs:/dev/XXX"
565 where XXX is the root slice of one of the disks that composed
566 the mirror (i.e.: /dev/ad0s1a). You can then rebuild
567 the array the same way you built it originally.
570 The following binaries have been disconnected from the build:
571 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
572 and mount_std. The functionality of these programs has been
573 moved into the mount program. For example, to mount a devfs
574 filesystem, instead of using mount_devfs, use: "mount -t devfs".
575 This does not affect entries in /etc/fstab, since entries in
576 /etc/fstab are always processed with "mount -t fstype".
579 Support for PCI Message Signalled Interrupts on i386 and amd64
580 has been added to the kernel and various drivers will soon be
581 updated to use MSI when it is available. If there are any problems,
582 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
583 and 'hw.pci.enable_msix' tunables to 0 in the loader.
586 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
587 The lockmgr object layout has been changed as a result of having
588 a lock_object embedded in it. As a consequence all file system
589 kernel modules must be re-compiled. The mutex profiling man page
590 has not yet been updated to reflect this change.
593 KSE in the kernel has now been made optional and turned on by
594 default. Use 'nooption KSE' in your kernel config to turn it
595 off. All kernel modules *must* be recompiled after this change.
596 There-after, modules from a KSE kernel should be compatible with
597 modules from a NOKSE kernel due to the temporary padding fields
598 added to 'struct proc'.
601 mrouted and its utilities have been removed from the base system.
604 Some ioctl(2) command codes have changed. Full backward ABI
605 compatibility is provided if the "options COMPAT_FREEBSD6" is
606 present in the kernel configuration file. Make sure to add
607 this option to your kernel config file, or recompile X.Org
608 and the rest of ports; otherwise they may refuse to work.
611 tcpslice has been removed from the base system.
614 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
615 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
616 systat needs to be rebuilt.
619 libpcap updated to v0.9.4 and tcpdump to v3.9.4
622 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
623 for IPFIREWALL_FORWARD is now as it was before when it was first
624 committed and for years after. The behaviour is now ON.
627 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
628 Now it can decrypt files created from different architectures.
629 Unfortunately, it is no longer able to decrypt a cipher text
630 generated with an older version on 64 bit architectures.
631 If you have such a file, you need old utility to decrypt it.
634 The interface version of the i4b kernel part has changed. So
635 after updating the kernel sources and compiling a new kernel,
636 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
637 be rebuilt, and vice versa.
640 The XBOX kernel now defaults to the nfe(4) driver instead of
641 the nve(4) driver. Please update your configuration
645 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
646 PCnet family of NICs has been removed. The new le(4) driver serves
647 as an equivalent but cross-platform replacement with the pcn(4)
648 driver still providing performance-optimized support for the subset
649 of AMD Am79C971 PCnet-FAST and greater chips as before.
652 The machdep.* sysctls and the adjkerntz utility have been
653 modified a bit. The new adjkerntz utility uses the new
654 sysctl names and sysctlbyname() calls, so it may be impossible
655 to run an old /sbin/adjkerntz utility in single-user mode
656 with a new kernel. Replace the `adjkerntz -i' step before
657 `make installworld' with:
659 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
661 and proceed as usual with the rest of the installworld-stage
662 steps. Otherwise, you risk installing binaries with their
663 timestamp set several hours in the future, especially if
664 you are running with local time set to GMT+X hours.
667 The ip6fw utility has been removed. The behavior provided by
668 ip6fw has been in ipfw2 for a good while and the rc.d scripts
669 have been updated to deal with it. There are some rules that
670 might not migrate cleanly. Use rc.firewall6 as a template to
674 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
675 attachments have been removed. Make sure to configure scc(4)
676 on sparc64. Note also that by default puc(4) will use uart(4)
677 and not sio(4) for serial ports because interrupt handling has
678 been optimized for multi-port serial cards and only uart(4)
679 implements the interface to support it.
682 The scc(4) driver replaces puc(4) for Serial Communications
683 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
684 Z8530. On sparc64, it is advised to add scc(4) to the kernel
685 configuration to make sure that the serial ports remain
689 Most world/kernel related NO_* build options changed names.
690 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
691 after FreeBSD ports) and should be set in /etc/src.conf
692 (the src.conf(5) manpage is provided). Full backwards
693 compatibility is maintained for the time being though it's
694 highly recommended to start moving old options out of the
695 system-wide /etc/make.conf file into the new /etc/src.conf
696 while also properly renaming them. More conversions will
697 likely follow. Posting to current@:
699 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
702 The NETSMBCRYPTO kernel option has been retired because its
703 functionality is always included in NETSMB and smbfs.ko now.
706 The TDFX_LINUX kernel option was retired and replaced by the
707 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
708 kernel module. Loading it alone should suffice to get 3dfx support
709 for Linux apps because it will pull in 3dfx.ko and linux.ko through
713 The 'audit' group was added to support the new auditing functionality
714 in the base system. Be sure to follow the directions for updating,
715 including the requirement to run mergemaster -p.
718 The kernel ABI to file system modules was changed on i386.
719 Please make sure that your kernel and modules are in sync.
722 This actually occured some time ago, but installing the kernel
723 now also installs a bunch of symbol files for the kernel modules.
724 This increases the size of /boot/kernel to about 67Mbytes. You
725 will need twice this if you will eventually back this up to kernel.old
726 on your next install.
727 If you have a shortage of room in your root partition, you should add
728 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
729 to your /etc/make.conf.
732 libc's malloc implementation has been replaced. This change has the
733 potential to uncover application bugs that previously went unnoticed.
734 See the malloc(3) manual page for more details.
737 The generic netgraph(4) cookie has been changed. If you upgrade
738 kernel passing this point, you also need to upgrade userland
739 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
742 si(4)'s device files now contain the unit number.
743 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
746 The kernel ABI was mostly destroyed due to a change in the size
747 of struct lock_object which is nested in other structures such
748 as mutexes which are nested in all sorts of other structures.
749 Make sure your kernel and modules are in sync.
752 The page coloring algorithm in the VM subsystem was converted
753 from tuning with kernel options to autotuning. Please remove
754 any PQ_* option except PQ_NOOPT from your kernel config.
757 The net80211-related tools in the tools/tools/ath directory
758 have been moved to tools/tools/net80211 and renamed with a
759 "wlan" prefix. Scripts that use them should be adjusted
763 Scripts in the local_startup directories (as defined in
764 /etc/defaults/rc.conf) that have the new rc.d semantics will
765 now be run as part of the base system rcorder. If there are
766 errors or problems with one of these local scripts, it could
767 cause boot problems. If you encounter such problems, boot in
768 single user mode, remove that script from the */rc.d directory.
769 Please report the problem to the port's maintainer, and the
770 freebsd-ports@freebsd.org mailing list.
773 The nodev mount option was deprecated in RELENG_6 (where it
774 was a no-op), and is now unsupported. If you have nodev or dev listed
775 in /etc/fstab, remove it, otherwise it will result in a mount error.
778 ABI between ipfw(4) and ipfw(8) has been changed. You need
779 to rebuild ipfw(8) when rebuilding kernel.
782 rp(4)'s device files now contain the unit number.
783 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
786 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
787 Its /etc/rc.conf.d configuration file has been `ppp' from
788 the beginning, and hence there is no need to touch it.
791 Now most modules get their build-time options from the kernel
792 configuration file. A few modules still have fixed options
793 due to their non-conformant implementation, but they will be
794 corrected eventually. You may need to review the options of
795 the modules in use, explicitly specify the non-default options
796 in the kernel configuration file, and rebuild the kernel and
800 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
801 to turn polling(4) on your interfaces.
804 The old bridge(4) implementation was retired. The new
805 if_bridge(4) serves as a full functional replacement.
808 The ai_addrlen of a struct addrinfo was changed to a socklen_t
809 to conform to POSIX-2001. This change broke an ABI
810 compatibility on 64 bit architecture. You have to recompile
811 userland programs that use getaddrinfo(3) on 64 bit
815 RELENG_6 branched here.
818 The pccard_ifconfig rc.conf variable has been removed and a new
819 variable, ifconfig_DEFAULT has been introduced. Unlike
820 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
821 do not have ifconfig_ifn entries rather than just those in
822 removable_interfaces.
825 Some previous versions of PAM have permitted the use of
826 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
827 to third party PAM modules in /usr/local/lib. A change has been
828 made to require the use of absolute paths in order to avoid
829 ambiguity and dependence on library path configuration, which may
830 affect existing configurations.
833 Major changes to network interface API. All drivers must be
834 recompiled. Drivers not in the base system will need to be
835 updated to the new APIs.
838 Changes were made to kinfo_proc in sys/user.h. Please recompile
839 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
840 will not behave correctly.
842 The API and ABI for hwpmc(4) have changed with the addition
843 of sampling support. Please recompile lib/libpmc(3) and
844 usr.sbin/{pmcstat,pmccontrol}.
847 The OpenBSD dhclient was imported in place of the ISC dhclient
848 and the network interface configuration scripts were updated
849 accordingly. If you use DHCP to configure your interfaces, you
850 must now run devd. Also, DNS updating was lost so you will need
851 to find a workaround if you use this feature.
853 The '_dhcp' user was added to support the OpenBSD dhclient. Be
854 sure to run mergemaster -p (like you are supposed to do every time
858 if_bridge was added to the tree. This has changed struct ifnet.
859 Please recompile userland and all network related modules.
862 The n_net of a struct netent was changed to an uint32_t, and
863 1st argument of getnetbyaddr() was changed to an uint32_t, to
864 conform to POSIX-2001. These changes broke an ABI
865 compatibility on 64 bit architecture. With these changes,
866 shlib major of libpcap was bumped. You have to recompile
867 userland programs that use getnetbyaddr(3), getnetbyname(3),
868 getnetent(3) and/or libpcap on 64 bit architecture.
871 Kernel parsing of extra options on '#!' first lines of shell
872 scripts has changed. Lines with multiple options likely will
873 fail after this date. For full details, please see
874 http://people.freebsd.org/~gad/Updating-20050528.txt
877 The packet filter (pf) code has been updated to OpenBSD 3.7
878 Please note the changed anchor syntax and the fact that
879 authpf(8) now needs a mounted fdescfs(5) to function.
882 The NO_MIXED_MODE kernel option has been removed from the i386
883 amd64 platforms as its use has been superceded by the new local
884 APIC timer code. Any kernel config files containing this option
888 The on-disk format of LC_CTYPE files was changed to be machine
889 independent. Please make sure NOT to use NO_CLEAN buildworld
890 when crossing this point. Crossing this point also requires
891 recompile or reinstall of all locale depended packages.
894 The ifi_epoch member of struct if_data has been changed to
895 contain the uptime at which the interface was created or the
896 statistics zeroed rather then the wall clock time because
897 wallclock time may go backwards. This should have no impact
898 unless an snmp implementation is using this value (I know of
902 The acpi_perf and acpi_throttle drivers are now part of the
903 acpi(4) main module. They are no longer built separately.
906 The layout of struct image_params has changed. You have to
907 recompile all compatibility modules (linux, svr4, etc) for use
911 The p4tcc driver has been merged into cpufreq(4). This makes
912 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
913 compile in "device cpufreq" to restore this functionality.
916 The responsibility of recomputing the file system summary of
917 a SoftUpdates-enabled dirty volume has been transferred to the
918 background fsck. A rebuild of fsck(8) utility is recommended
919 if you have updated the kernel.
921 To get the old behavior (recompute file system summary at mount
922 time), you can set vfs.ffs.compute_summary_at_mount=1 before
923 mounting the new volume.
926 The cpufreq import is complete. As part of this, the sysctls for
927 acpi(4) throttling have been removed. The power_profile script
928 has been updated, so you can use performance/economy_cpu_freq in
929 rc.conf(5) to set AC on/offline cpu frequencies.
932 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
933 requires recompiling libnetgraph and userland netgraph utilities.
936 Support for abbreviated forms of a number of ipfw options is
937 now deprecated. Warnings are printed to stderr indicating the
938 correct full form when a match occurs. Some abbreviations may
939 be supported at a later date based on user feedback. To be
940 considered for support, abbreviations must be in use prior to
941 this commit and unlikely to be confused with current key words.
944 By a popular demand, a lot of NOFOO options were renamed
945 to NO_FOO (see bsd.compat.mk for a full list). The old
946 spellings are still supported, but will cause annoying
947 warnings on stderr. Make sure you upgrade properly (see
948 the COMMON ITEMS: section later in this file).
951 Auto-loading of ancillary wlan modules such as wlan_wep has
952 been temporarily disabled; you need to statically configure
953 the modules you need into your kernel or explicitly load them
954 prior to use. Specifically, if you intend to use WEP encryption
955 with an 802.11 device load/configure wlan_wep; if you want to
956 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
957 and wlan_xauth as required.
960 The behaviour of ppp(8) has changed slightly. If lqr is enabled
961 (``enable lqr''), older versions would revert to LCP ECHO mode on
962 negotiation failure. Now, ``enable echo'' is required for this
963 behaviour. The ppp version number has been bumped to 3.4.2 to
967 The wlan support has been updated to split the crypto support
968 into separate modules. For static WEP you must configure the
969 wlan_wep module in your system or build and install the module
970 in place where it can be loaded (the kernel will auto-load
971 the module when a wep key is configured).
974 The ath driver has been updated to split the tx rate control
975 algorithm into a separate module. You need to include either
976 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
979 Support for systems with an 80386 CPU has been removed. Please
980 use FreeBSD 5.x or earlier on systems with an 80386.
983 We have had a hack which would mount the root filesystem
984 R/W if the device were named 'md*'. As part of the vnode
985 work I'm doing I have had to remove this hack. People
986 building systems which use preloaded MD root filesystems
987 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
988 their /etc/rc scripts.
991 FreeBSD 5.3 shipped here.
994 The size of struct tcpcb has changed again due to the removal
995 of RFC1644 T/TCP. You have to recompile userland programs that
996 read kmem for tcp sockets directly (netstat, sockstat, etc.)
999 The size of struct tcpcb has changed. You have to recompile
1000 userland programs that read kmem for tcp sockets directly
1001 (netstat, sockstat, etc.)
1004 RELENG_5 branched here. For older entries, please see updating
1005 in the RELENG_5 branch.
1011 Avoid using make -j when upgrading. From time to time in the
1012 past there have been problems using -j with buildworld and/or
1013 installworld. This is especially true when upgrading between
1014 "distant" versions (eg one that cross a major release boundary
1015 or several minor releases, or when several months have passed
1016 on the -current branch).
1018 Sometimes, obscure build problems are the result of environment
1019 poisoning. This can happen because the make utility reads its
1020 environment when searching for values for global variables.
1021 To run your build attempts in an "environmental clean room",
1022 prefix all make commands with 'env -i '. See the env(1) manual
1023 page for more details.
1025 When upgrading from one major version to another it is generally
1026 best to upgrade to the latest code in the currently installed branch
1027 first, then do an upgrade to the new branch. This is the best-tested
1028 upgrade path, and has the highest probability of being successful.
1029 Please try this approach before reporting problems with a major
1034 If you are updating from a prior version of FreeBSD (even one just
1035 a few days old), you should follow this procedure. It is the most
1036 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1038 make kernel-toolchain
1039 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1040 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1042 To test a kernel once
1043 ---------------------
1044 If you just want to boot a kernel once (because you are not sure
1045 if it works, or if you want to boot a known bad kernel to provide
1046 debugging information) run
1047 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1048 nextboot -k testkernel
1050 To just build a kernel when you know that it won't mess you up
1051 --------------------------------------------------------------
1052 This assumes you are already running a 5.X system. Replace
1053 ${arch} with the architecture of your machine (e.g. "i386",
1054 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1056 cd src/sys/${arch}/conf
1057 config KERNEL_NAME_HERE
1058 cd ../compile/KERNEL_NAME_HERE
1063 If this fails, go to the "To build a kernel" section.
1065 To rebuild everything and install it on the current system.
1066 -----------------------------------------------------------
1067 # Note: sometimes if you are running current you gotta do more than
1068 # is listed here if you are upgrading from a really old current.
1070 <make sure you have good level 0 dumps>
1072 make kernel KERNCONF=YOUR_KERNEL_HERE
1074 <reboot in single user> [3]
1082 To cross-install current onto a separate partition
1083 --------------------------------------------------
1084 # In this approach we use a separate partition to hold
1085 # current's root, 'usr', and 'var' directories. A partition
1086 # holding "/", "/usr" and "/var" should be about 2GB in
1089 <make sure you have good level 0 dumps>
1092 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1093 <maybe newfs current's root partition>
1094 <mount current's root partition on directory ${CURRENT_ROOT}>
1095 make installworld DESTDIR=${CURRENT_ROOT}
1096 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1097 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1098 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1099 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1100 <reboot into current>
1101 <do a "native" rebuild/install as described in the previous section>
1102 <maybe install compatibility libraries from ports/misc/compat*>
1106 To upgrade in-place from 5.x-stable to current
1107 ----------------------------------------------
1108 <make sure you have good level 0 dumps>
1110 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1112 <reboot in single user> [3]
1119 Make sure that you've read the UPDATING file to understand the
1120 tweaks to various things you need. At this point in the life
1121 cycle of current, things change often and you are on your own
1122 to cope. The defaults can also change, so please read ALL of
1123 the UPDATING entries.
1125 Also, if you are tracking -current, you must be subscribed to
1126 freebsd-current@freebsd.org. Make sure that before you update
1127 your sources that you have read and understood all the recent
1128 messages there. If in doubt, please track -stable which has
1129 much fewer pitfalls.
1131 [1] If you have third party modules, such as vmware, you
1132 should disable them at this point so they don't crash your
1135 [3] From the bootblocks, boot -s, and then do
1140 adjkerntz -i # if CMOS is wall time
1141 Also, when doing a major release upgrade, it is required that
1142 you boot into single user mode to do the installworld.
1144 [4] Note: This step is non-optional. Failure to do this step
1145 can result in a significant reduction in the functionality of the
1146 system. Attempting to do it by hand is not recommended and those
1147 that pursue this avenue should read this file carefully, as well
1148 as the archives of freebsd-current and freebsd-hackers mailing lists
1149 for potential gotchas.
1151 [5] Usually this step is a noop. However, from time to time
1152 you may need to do this if you get unknown user in the following
1153 step. It never hurts to do it all the time. You may need to
1154 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1155 install) after the buildworld before this step if you last updated
1156 from current before 20020224 or from -stable before 20020408.
1158 [8] In order to have a kernel that can run the 4.x binaries
1159 needed to do an installworld, you must include the COMPAT_FREEBSD4
1160 option in your kernel. Failure to do so may leave you with a system
1161 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
1162 is required to run the 5.x binaries on more recent kernels.
1164 Make sure that you merge any new devices from GENERIC since the
1165 last time you updated your kernel config file.
1167 [9] When checking out sources, you must include the -P flag to have
1168 cvs prune empty directories.
1170 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1171 "?=" instead of the "=" assignment operator, so that buildworld can
1172 override the CPUTYPE if it needs to.
1174 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1175 not on the command line, or in /etc/make.conf. buildworld will
1176 warn if it is improperly defined.
1179 This file contains a list, in reverse chronological order, of major
1180 breakages in tracking -current. Not all things will be listed here,
1181 and it only starts on October 16, 2004. Updating files can found in
1182 previous releases if your system is older than this.
1184 Copyright information:
1186 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
1188 Redistribution, publication, translation and use, with or without
1189 modification, in full or in part, in any form or format of this
1190 document are permitted without further permission from the author.
1192 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1193 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1194 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1195 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1196 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1197 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1198 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1199 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1200 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1201 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1202 POSSIBILITY OF SUCH DAMAGE.
1204 If you find this document useful, and you want to, you may buy the
1207 Contact Warner Losh if you have any questions about your use of