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 __FreeBSD_version 800054 adds memory barriers to
27 <machine/atomic.h>, new interfaces to ifnet to facilitate
28 multiple hardware transmit queues for cards that support
29 them, and a lock-less ring-buffer implementation to
30 enable drivers to more efficiently manage queueing of
34 A new version of ZFS (version 13) has been merged to -HEAD.
35 This version has zpool attribute "listsnapshots" off by
36 default, which means "zfs list" does not show snapshots,
37 and is the same as Solaris behavior.
40 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
43 The uhci, ohci, ehci and slhci USB Host controller drivers have
44 been put into separate modules. If you load the usb module
45 separately through loader.conf you will need to load the
46 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
47 controller add the following to loader.conf:
53 The ABI used by the PMC toolset has changed. Please keep
54 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
58 The TTY subsystem of the kernel has been replaced by a new
59 implementation, which provides better scalability and an
60 improved driver model. Most common drivers have been migrated to
61 the new TTY subsystem, while others have not. The following
62 drivers have not yet been ported to the new TTY layer:
71 ng_h4, ng_tty, ppp, sl, snp
73 Adding these drivers to your kernel configuration file shall
74 cause compilation to fail.
77 ntpd has been upgraded to 4.2.4p5.
80 OpenSSH has been upgraded to 5.1p1.
82 For many years, FreeBSD's version of OpenSSH preferred DSA
83 over RSA for host and user authentication keys. With this
84 upgrade, we've switched to the vendor's default of RSA over
85 DSA. This may cause upgraded clients to warn about unknown
86 host keys even for previously known hosts. Users should
87 follow the usual procedure for verifying host keys before
88 accepting the RSA key.
90 This can be circumvented by setting the "HostKeyAlgorithms"
91 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
94 Please note that the sequence of keys offered for
95 authentication has been changed as well. You may want to
96 specify IdentityFile in a different order to revert this
100 The sio(4) driver has been removed from the i386 and amd64
101 kernel configuration files. This means uart(4) is now the
102 default serial port driver on those platforms as well.
104 To prevent collisions with the sio(4) driver, the uart(4) driver
105 uses different names for its device nodes. This means the
106 onboard serial port will now most likely be called "ttyu0"
107 instead of "ttyd0". You may need to reconfigure applications to
108 use the new device names.
110 When using the serial port as a boot console, be sure to update
111 /boot/device.hints and /etc/ttys before booting the new kernel.
112 If you forget to do so, you can still manually specify the hints
113 at the loader prompt:
115 set hint.uart.0.at="isa"
116 set hint.uart.0.port="0x3F8"
117 set hint.uart.0.flags="0x10"
118 set hint.uart.0.irq="4"
122 The gpt(8) utility has been removed. Use gpart(8) to partition
126 The version that Linuxulator emulates was changed from 2.4.2
127 to 2.6.16. If you experience any problems with Linux binaries
128 please try to set sysctl compat.linux.osrelease to 2.4.2 and
129 if it fixes the problem contact emulation mailing list.
132 ISDN4BSD (I4B) was removed from the src tree. You may need to
133 update a your kernel configuration and remove relevant entries.
136 I have checked in code to support multiple routing tables.
137 See the man pages setfib(1) and setfib(2).
138 This is a hopefully backwards compatible version,
139 but to make use of it you need to compile your kernel
140 with options ROUTETABLES=2 (or more up to 16).
143 The 802.11 wireless support was redone to enable multi-bss
144 operation on devices that are capable. The underlying device
145 is no longer used directly but instead wlanX devices are
146 cloned with ifconfig. This requires changes to rc.conf files.
148 ifconfig_ath0="WPA DHCP"
151 ifconfig_wlan0="WPA DHCP"
152 see rc.conf(5) for more details. In addition, mergemaster of
153 /etc/rc.d is highly recommended. Simultaneous update of userland
154 and kernel wouldn't hurt either.
156 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
157 modules were merged into the base wlan module. All references
158 to these modules (e.g. in kernel config files) must be removed.
161 psm(4) has gained write(2) support in native operation level.
162 Arbitrary commands can be written to /dev/psm%d and status can
163 be read back from it. Therefore, an application is responsible
164 for status validation and error recovery. It is a no-op in
165 other operation levels.
168 Support for KSE threading has been removed from the kernel. To
169 run legacy applications linked against KSE libmap.conf may
170 be used. The following libmap.conf may be used to ensure
171 compatibility with any prior release:
173 libpthread.so.1 libthr.so.1
174 libpthread.so.2 libthr.so.2
175 libkse.so.3 libthr.so.3
178 The layout of struct vmspace has changed. This affects libkvm
179 and any executables that link against libkvm and use the
180 kvm_getprocs() function. In particular, but not exclusively,
181 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
182 The effects are minimal, but it's advisable to upgrade world
186 The latest em driver no longer has support in it for the
187 82575 adapter, this is now moved to the igb driver. The
188 split was done to make new features that are incompatible
189 with older hardware easier to do.
192 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
193 likewise the kernel option is now GEOM_LINUX_LVM.
196 The default NFS mount mode has changed from UDP to TCP for
197 increased reliability. If you rely on (insecurely) NFS
198 mounting across a firewall you may need to update your
202 Belatedly note the addition of m_collapse for compacting
206 The fts(3) structures have been changed to use adequate
207 integer types for their members and so to be able to cope
208 with huge file trees. The old fts(3) ABI is preserved
209 through symbol versioning in libc, so third-party binaries
210 using fts(3) should still work, although they will not take
211 advantage of the extended types. At the same time, some
212 third-party software might fail to build after this change
213 due to unportable assumptions made in its source code about
214 fts(3) structure members. Such software should be fixed
215 by its vendor or, in the worst case, in the ports tree.
216 FreeBSD_version 800015 marks this change for the unlikely
217 case that a portable fix is impossible.
220 To upgrade to -current after this date, you must be running
221 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
222 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
225 The ADAPTIVE_GIANT kernel option has been retired because its
226 functionality is the default now.
229 The AT keyboard emulation of sunkbd(4) has been turned on
230 by default. In order to make the special symbols of the Sun
231 keyboards driven by sunkbd(4) work under X these now have
232 to be configured the same way as Sun USB keyboards driven
233 by ukbd(4) (which also does AT keyboard emulation), f.e.:
235 Option "XkbLayout" "us"
236 Option "XkbRules" "xorg"
237 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
240 It has been decided that it is desirable to provide ABI
241 backwards compatibility to the FreeBSD 4/5/6 versions of the
242 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
243 broken with the introduction of PCI domain support (see the
244 20070930 entry). Unfortunately, this required the ABI of
245 PCIOCGETCONF to be broken again in order to be able to
246 provide backwards compatibility to the old version of that
247 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
248 again. As for prominent ports this affects neither pciutils
249 nor xorg-server this time, the hal port needs to be rebuilt
253 The misnamed kthread_create() and friends have been renamed
254 to kproc_create() etc. Many of the callers already
256 I will return kthread_create() and friends in a while
257 with implementations that actually create threads, not procs.
258 Renaming corresponds with version 800002.
264 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
265 WITHOUT_LIBTHR are set.
268 The PCI code has been made aware of PCI domains. This means that
269 the location strings as used by pciconf(8) etc are now in the
270 following format: pci<domain>:<bus>:<device>[:<function>]. It
271 also means that consumers of <sys/pciio.h> potentially need to
272 be recompiled; this includes the hal and xorg-server ports.
275 The caching daemon (cached) was renamed to nscd. nscd.conf
276 configuration file should be used instead of cached.conf and
277 nscd_enable, nscd_pidfile and nscd_flags options should be used
278 instead of cached_enable, cached_pidfile and cached_flags in
282 The getfacl(1) utility now prints owning user and group name
283 instead of owning uid and gid in the three line comment header.
284 This is the same behavior as getfacl(1) on Solaris and Linux.
287 The new IPsec code is now compiled in using the IPSEC option. The
288 IPSEC option now requires "device crypto" be defined in your kernel
289 configuration. The FAST_IPSEC kernel option is now deprecated.
292 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
293 note the changed syntax - keep state is now on by default. Also
294 note the fact that ftp-proxy(8) has been changed from bottom up and
295 has been moved from libexec to usr/sbin. Changes in the ALTQ
296 handling also affect users of IPFW's ALTQ capabilities.
299 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
300 only IPsec supported by FreeBSD. The new IPsec stack
301 supports both IPv4 and IPv6. The kernel option will change
302 after the code changes have settled in. For now the kernel
303 option IPSEC is deprecated and FAST_IPSEC is the only option, that
304 will change after some settling time.
307 The wicontrol(8) utility has been removed from the base system. wi(4)
308 cards should be configured using ifconfig(8), see the man page for more
312 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
313 instead of the nve(4) driver. Please update your configuration
317 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
318 database if it is missing or older than the aliases file. If
319 desired, set the new rc.conf option sendmail_rebuild_aliases
320 to "YES" to restore that functionality.
323 The IPv4 multicast socket code has been considerably modified, and
324 moved to the file sys/netinet/in_mcast.c. Initial support for the
325 RFC 3678 Source-Specific Multicast Socket API has been added to
326 the IPv4 network stack.
328 Strict multicast and broadcast reception is now the default for
329 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
330 has now been removed.
332 The RFC 1724 hack for interface selection has been removed; the use
333 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
334 been added to replace it. Consumers such as routed will soon be
335 updated to reflect this.
337 These changes affect users who are running routed(8) or rdisc(8)
338 from the FreeBSD base system on point-to-point or unnumbered
342 The net80211 layer has changed significantly and all wireless
343 drivers that depend on it need to be recompiled. Further these
344 changes require that any program that interacts with the wireless
345 support in the kernel be recompiled; this includes: ifconfig,
346 wpa_supplicant, hostapd, and wlanstats. Users must also, for
347 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
348 if they use modules for wireless support. These modules implement
349 scanning support for station and ap modes, respectively. Failure
350 to load the appropriate module before marking a wireless interface
351 up will result in a message to the console and the device not
355 The pam_nologin(8) module ceases to provide an authentication
356 function and starts providing an account management function.
357 Consequent changes to /etc/pam.d should be brought in using
358 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
359 need manual editing as follows. Locate this line (or similar):
361 auth required pam_nologin.so no_warn
363 and change it according to this example:
365 account required pam_nologin.so no_warn
367 That is, the first word needs to be changed from "auth" to
368 "account". The new line can be moved to the account section
369 within the file for clarity. Not updating pam.conf(5) files
370 will result in nologin(5) ignored by the respective services.
373 The ether_ioctl() function has been synchronized with ioctl(2)
374 and ifnet.if_ioctl. Due to that, the size of one of its arguments
375 has changed on 64-bit architectures. All kernel modules using
376 ether_ioctl() need to be rebuilt on such architectures.
379 Improved INCLUDE_CONFIG_FILE support has been introduced to the
380 config(8) utility. In order to take advantage of this new
381 functionality, you are expected to recompile and install
382 src/usr.sbin/config. If you don't rebuild config(8), and your
383 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
384 build will be broken because of a missing "kernconfstring"
388 Symbol versioning is enabled by default. To disable it, use
389 option WITHOUT_SYMVER. It is not advisable to attempt to
390 disable symbol versioning once it is enabled; your installworld
391 will break because a symbol version-less libc will get installed
392 before the install tools. As a result, the old install tools,
393 which previously had symbol dependencies to FBSD_1.0, will fail
394 because the freshly installed libc will not have them.
396 The default threading library (providing "libpthread") has been
397 changed to libthr. If you wish to have libkse as your default,
398 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
401 The ABI breakage in sendmail(8)'s libmilter has been repaired
402 so it is no longer necessary to recompile mail filters (aka,
403 milters). If you recompiled mail filters after the 20070408
404 note, it is not necessary to recompile them again.
407 The new trunk(4) driver has been renamed to lagg(4) as it better
408 reflects its purpose. ifconfig will need to be recompiled.
411 sendmail(8) has been updated to version 8.14.1. Mail filters
412 (aka, milters) compiled against the libmilter included in the
413 base operating system should be recompiled.
416 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
417 In order to use them one must agree to the respective LICENSE in
418 share/doc/legal and define legal.intel_<name>.license_ack=1 via
419 loader.conf(5) or kenv(1). Make sure to deinstall the now
420 deprecated modules from the respective firmware ports.
423 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
424 were removed from FreeBSD's libc. These originally came from INRIA
425 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
426 deprecated in previous releases.
427 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
428 replace it as a more portable (and re-entrant) API.
431 To support interrupt filtering a modification to the newbus API
432 has occurred, ABI was broken and __FreeBSD_version was bumped
433 to 700031. Please make sure that your kernel and modules are in
435 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
438 The IPv6 multicast forwarding code may now be loaded into GENERIC
439 kernels by loading the ip_mroute.ko module. This is built into the
440 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
441 set; see src.conf(5) for more information.
444 The output of netstat -r has changed. Without -n, we now only
445 print a "network name" without the prefix length if the network
446 address and mask exactly match a Class A/B/C network, and an entry
447 exists in the nsswitch "networks" map.
448 With -n, we print the full unabbreviated CIDR network prefix in
449 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
450 This change is in preparation for changes such as equal-cost
451 multipath, and to more generally assist operational deployment
452 of FreeBSD as a modern IPv4 router.
455 PIM has been turned on by default in the IPv4 multicast
456 routing code. The kernel option 'PIM' has now been removed.
457 PIM is now built by default if option 'MROUTING' is specified.
458 It may now be loaded into GENERIC kernels by loading the
462 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
463 has been removed. Its functionality may be achieved by explicitly
464 configuring gif(4) interfaces and using the 'phyint' keyword in
466 XORP does not support source-routed IPv4 multicast tunnels nor the
467 integrated IPIP tunneling, therefore it is not affected by this
468 change. The __FreeBSD_version macro has been bumped to 700030.
471 Support for PCI Message Signalled Interrupts has been
472 re-enabled in the bge driver, only for those chips which are
473 believed to support it properly. If there are any problems,
474 MSI can be disabled completely by setting the
475 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
479 Support for PCI Message Signalled Interrupts has been
480 disabled again in the bge driver. Many revisions of the
481 hardware fail to support it properly. Support can be
482 re-enabled by removing the #define of BGE_DISABLE_MSI in
483 "src/sys/dev/bge/if_bge.c".
486 Support for PCI Message Signalled Interrupts has been added
487 to the bge driver. If there are any problems, MSI can be
488 disabled completely by setting the 'hw.pci.enable_msi' and
489 'hw.pci.enable_msix' tunables to 0 in the loader.
492 The removal of several facets of the experimental Threading
493 system from the kernel means that the proc and thread structures
494 have changed quite a bit. I suggest all kernel modules that might
495 reference these structures be recompiled.. Especially the
499 Sound infrastructure has been updated with various fixes and
500 improvements. Most of the changes are pretty much transparent,
501 with exceptions of followings:
502 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
503 moved to their own dev sysctl nodes, for example:
504 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
505 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
506 own chardev in the form of "dsp%d.<function>%d", where <function>
507 is p = playback, r = record and v = virtual, respectively. Users
508 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
509 This does not affect those who are using "/dev/dsp".
512 geom(4)'s gmirror(8) class metadata structure has been
513 rev'd from v3 to v4. If you update across this point and
514 your metadata is converted for you, you will not be easily
515 able to downgrade since the /boot/kernel.old/geom_mirror.ko
516 kernel module will be unable to read the v4 metadata. You
517 can resolve this by doing from the loader(8) prompt:
519 set vfs.root.mountfrom="ufs:/dev/XXX"
521 where XXX is the root slice of one of the disks that composed
522 the mirror (i.e.: /dev/ad0s1a). You can then rebuild
523 the array the same way you built it originally.
526 The following binaries have been disconnected from the build:
527 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
528 and mount_std. The functionality of these programs has been
529 moved into the mount program. For example, to mount a devfs
530 filesystem, instead of using mount_devfs, use: "mount -t devfs".
531 This does not affect entries in /etc/fstab, since entries in
532 /etc/fstab are always processed with "mount -t fstype".
535 Support for PCI Message Signalled Interrupts on i386 and amd64
536 has been added to the kernel and various drivers will soon be
537 updated to use MSI when it is available. If there are any problems,
538 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
539 and 'hw.pci.enable_msix' tunables to 0 in the loader.
542 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
543 The lockmgr object layout has been changed as a result of having
544 a lock_object embedded in it. As a consequence all file system
545 kernel modules must be re-compiled. The mutex profiling man page
546 has not yet been updated to reflect this change.
549 KSE in the kernel has now been made optional and turned on by
550 default. Use 'nooption KSE' in your kernel config to turn it
551 off. All kernel modules *must* be recompiled after this change.
552 There-after, modules from a KSE kernel should be compatible with
553 modules from a NOKSE kernel due to the temporary padding fields
554 added to 'struct proc'.
557 mrouted and its utilities have been removed from the base system.
560 Some ioctl(2) command codes have changed. Full backward ABI
561 compatibility is provided if the "options COMPAT_FREEBSD6" is
562 present in the kernel configuration file. Make sure to add
563 this option to your kernel config file, or recompile X.Org
564 and the rest of ports; otherwise they may refuse to work.
567 tcpslice has been removed from the base system.
570 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
571 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
572 systat needs to be rebuilt.
575 libpcap updated to v0.9.4 and tcpdump to v3.9.4
578 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
579 for IPFIREWALL_FORWARD is now as it was before when it was first
580 committed and for years after. The behaviour is now ON.
583 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
584 Now it can decrypt files created from different architectures.
585 Unfortunately, it is no longer able to decrypt a cipher text
586 generated with an older version on 64 bit architectures.
587 If you have such a file, you need old utility to decrypt it.
590 The interface version of the i4b kernel part has changed. So
591 after updating the kernel sources and compiling a new kernel,
592 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
593 be rebuilt, and vice versa.
596 The XBOX kernel now defaults to the nfe(4) driver instead of
597 the nve(4) driver. Please update your configuration
601 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
602 PCnet family of NICs has been removed. The new le(4) driver serves
603 as an equivalent but cross-platform replacement with the pcn(4)
604 driver still providing performance-optimized support for the subset
605 of AMD Am79C971 PCnet-FAST and greater chips as before.
608 The machdep.* sysctls and the adjkerntz utility have been
609 modified a bit. The new adjkerntz utility uses the new
610 sysctl names and sysctlbyname() calls, so it may be impossible
611 to run an old /sbin/adjkerntz utility in single-user mode
612 with a new kernel. Replace the `adjkerntz -i' step before
613 `make installworld' with:
615 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
617 and proceed as usual with the rest of the installworld-stage
618 steps. Otherwise, you risk installing binaries with their
619 timestamp set several hours in the future, especially if
620 you are running with local time set to GMT+X hours.
623 The ip6fw utility has been removed. The behavior provided by
624 ip6fw has been in ipfw2 for a good while and the rc.d scripts
625 have been updated to deal with it. There are some rules that
626 might not migrate cleanly. Use rc.firewall6 as a template to
630 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
631 attachments have been removed. Make sure to configure scc(4)
632 on sparc64. Note also that by default puc(4) will use uart(4)
633 and not sio(4) for serial ports because interrupt handling has
634 been optimized for multi-port serial cards and only uart(4)
635 implements the interface to support it.
638 The scc(4) driver replaces puc(4) for Serial Communications
639 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
640 Z8530. On sparc64, it is advised to add scc(4) to the kernel
641 configuration to make sure that the serial ports remain
645 Most world/kernel related NO_* build options changed names.
646 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
647 after FreeBSD ports) and should be set in /etc/src.conf
648 (the src.conf(5) manpage is provided). Full backwards
649 compatibility is maintained for the time being though it's
650 highly recommended to start moving old options out of the
651 system-wide /etc/make.conf file into the new /etc/src.conf
652 while also properly renaming them. More conversions will
653 likely follow. Posting to current@:
655 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
658 The NETSMBCRYPTO kernel option has been retired because its
659 functionality is always included in NETSMB and smbfs.ko now.
662 The TDFX_LINUX kernel option was retired and replaced by the
663 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
664 kernel module. Loading it alone should suffice to get 3dfx support
665 for Linux apps because it will pull in 3dfx.ko and linux.ko through
669 The 'audit' group was added to support the new auditing functionality
670 in the base system. Be sure to follow the directions for updating,
671 including the requirement to run mergemaster -p.
674 The kernel ABI to file system modules was changed on i386.
675 Please make sure that your kernel and modules are in sync.
678 This actually occured some time ago, but installing the kernel
679 now also installs a bunch of symbol files for the kernel modules.
680 This increases the size of /boot/kernel to about 67Mbytes. You
681 will need twice this if you will eventually back this up to kernel.old
682 on your next install.
683 If you have a shortage of room in your root partition, you should add
684 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
685 to your /etc/make.conf.
688 libc's malloc implementation has been replaced. This change has the
689 potential to uncover application bugs that previously went unnoticed.
690 See the malloc(3) manual page for more details.
693 The generic netgraph(4) cookie has been changed. If you upgrade
694 kernel passing this point, you also need to upgrade userland
695 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
698 si(4)'s device files now contain the unit number.
699 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
702 The kernel ABI was mostly destroyed due to a change in the size
703 of struct lock_object which is nested in other structures such
704 as mutexes which are nested in all sorts of other structures.
705 Make sure your kernel and modules are in sync.
708 The page coloring algorithm in the VM subsystem was converted
709 from tuning with kernel options to autotuning. Please remove
710 any PQ_* option except PQ_NOOPT from your kernel config.
713 The net80211-related tools in the tools/tools/ath directory
714 have been moved to tools/tools/net80211 and renamed with a
715 "wlan" prefix. Scripts that use them should be adjusted
719 Scripts in the local_startup directories (as defined in
720 /etc/defaults/rc.conf) that have the new rc.d semantics will
721 now be run as part of the base system rcorder. If there are
722 errors or problems with one of these local scripts, it could
723 cause boot problems. If you encounter such problems, boot in
724 single user mode, remove that script from the */rc.d directory.
725 Please report the problem to the port's maintainer, and the
726 freebsd-ports@freebsd.org mailing list.
729 The nodev mount option was deprecated in RELENG_6 (where it
730 was a no-op), and is now unsupported. If you have nodev or dev listed
731 in /etc/fstab, remove it, otherwise it will result in a mount error.
734 ABI between ipfw(4) and ipfw(8) has been changed. You need
735 to rebuild ipfw(8) when rebuilding kernel.
738 rp(4)'s device files now contain the unit number.
739 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
742 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
743 Its /etc/rc.conf.d configuration file has been `ppp' from
744 the beginning, and hence there is no need to touch it.
747 Now most modules get their build-time options from the kernel
748 configuration file. A few modules still have fixed options
749 due to their non-conformant implementation, but they will be
750 corrected eventually. You may need to review the options of
751 the modules in use, explicitly specify the non-default options
752 in the kernel configuration file, and rebuild the kernel and
756 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
757 to turn polling(4) on your interfaces.
760 The old bridge(4) implementation was retired. The new
761 if_bridge(4) serves as a full functional replacement.
764 The ai_addrlen of a struct addrinfo was changed to a socklen_t
765 to conform to POSIX-2001. This change broke an ABI
766 compatibility on 64 bit architecture. You have to recompile
767 userland programs that use getaddrinfo(3) on 64 bit
771 RELENG_6 branched here.
774 The pccard_ifconfig rc.conf variable has been removed and a new
775 variable, ifconfig_DEFAULT has been introduced. Unlike
776 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
777 do not have ifconfig_ifn entries rather than just those in
778 removable_interfaces.
781 Some previous versions of PAM have permitted the use of
782 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
783 to third party PAM modules in /usr/local/lib. A change has been
784 made to require the use of absolute paths in order to avoid
785 ambiguity and dependence on library path configuration, which may
786 affect existing configurations.
789 Major changes to network interface API. All drivers must be
790 recompiled. Drivers not in the base system will need to be
791 updated to the new APIs.
794 Changes were made to kinfo_proc in sys/user.h. Please recompile
795 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
796 will not behave correctly.
798 The API and ABI for hwpmc(4) have changed with the addition
799 of sampling support. Please recompile lib/libpmc(3) and
800 usr.sbin/{pmcstat,pmccontrol}.
803 The OpenBSD dhclient was imported in place of the ISC dhclient
804 and the network interface configuration scripts were updated
805 accordingly. If you use DHCP to configure your interfaces, you
806 must now run devd. Also, DNS updating was lost so you will need
807 to find a workaround if you use this feature.
809 The '_dhcp' user was added to support the OpenBSD dhclient. Be
810 sure to run mergemaster -p (like you are supposed to do every time
814 if_bridge was added to the tree. This has changed struct ifnet.
815 Please recompile userland and all network related modules.
818 The n_net of a struct netent was changed to an uint32_t, and
819 1st argument of getnetbyaddr() was changed to an uint32_t, to
820 conform to POSIX-2001. These changes broke an ABI
821 compatibility on 64 bit architecture. With these changes,
822 shlib major of libpcap was bumped. You have to recompile
823 userland programs that use getnetbyaddr(3), getnetbyname(3),
824 getnetent(3) and/or libpcap on 64 bit architecture.
827 Kernel parsing of extra options on '#!' first lines of shell
828 scripts has changed. Lines with multiple options likely will
829 fail after this date. For full details, please see
830 http://people.freebsd.org/~gad/Updating-20050528.txt
833 The packet filter (pf) code has been updated to OpenBSD 3.7
834 Please note the changed anchor syntax and the fact that
835 authpf(8) now needs a mounted fdescfs(5) to function.
838 The NO_MIXED_MODE kernel option has been removed from the i386
839 amd64 platforms as its use has been superceded by the new local
840 APIC timer code. Any kernel config files containing this option
844 The on-disk format of LC_CTYPE files was changed to be machine
845 independent. Please make sure NOT to use NO_CLEAN buildworld
846 when crossing this point. Crossing this point also requires
847 recompile or reinstall of all locale depended packages.
850 The ifi_epoch member of struct if_data has been changed to
851 contain the uptime at which the interface was created or the
852 statistics zeroed rather then the wall clock time because
853 wallclock time may go backwards. This should have no impact
854 unless an snmp implementation is using this value (I know of
858 The acpi_perf and acpi_throttle drivers are now part of the
859 acpi(4) main module. They are no longer built separately.
862 The layout of struct image_params has changed. You have to
863 recompile all compatibility modules (linux, svr4, etc) for use
867 The p4tcc driver has been merged into cpufreq(4). This makes
868 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
869 compile in "device cpufreq" to restore this functionality.
872 The responsibility of recomputing the file system summary of
873 a SoftUpdates-enabled dirty volume has been transferred to the
874 background fsck. A rebuild of fsck(8) utility is recommended
875 if you have updated the kernel.
877 To get the old behavior (recompute file system summary at mount
878 time), you can set vfs.ffs.compute_summary_at_mount=1 before
879 mounting the new volume.
882 The cpufreq import is complete. As part of this, the sysctls for
883 acpi(4) throttling have been removed. The power_profile script
884 has been updated, so you can use performance/economy_cpu_freq in
885 rc.conf(5) to set AC on/offline cpu frequencies.
888 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
889 requires recompiling libnetgraph and userland netgraph utilities.
892 Support for abbreviated forms of a number of ipfw options is
893 now deprecated. Warnings are printed to stderr indicating the
894 correct full form when a match occurs. Some abbreviations may
895 be supported at a later date based on user feedback. To be
896 considered for support, abbreviations must be in use prior to
897 this commit and unlikely to be confused with current key words.
900 By a popular demand, a lot of NOFOO options were renamed
901 to NO_FOO (see bsd.compat.mk for a full list). The old
902 spellings are still supported, but will cause annoying
903 warnings on stderr. Make sure you upgrade properly (see
904 the COMMON ITEMS: section later in this file).
907 Auto-loading of ancillary wlan modules such as wlan_wep has
908 been temporarily disabled; you need to statically configure
909 the modules you need into your kernel or explicitly load them
910 prior to use. Specifically, if you intend to use WEP encryption
911 with an 802.11 device load/configure wlan_wep; if you want to
912 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
913 and wlan_xauth as required.
916 The behaviour of ppp(8) has changed slightly. If lqr is enabled
917 (``enable lqr''), older versions would revert to LCP ECHO mode on
918 negotiation failure. Now, ``enable echo'' is required for this
919 behaviour. The ppp version number has been bumped to 3.4.2 to
923 The wlan support has been updated to split the crypto support
924 into separate modules. For static WEP you must configure the
925 wlan_wep module in your system or build and install the module
926 in place where it can be loaded (the kernel will auto-load
927 the module when a wep key is configured).
930 The ath driver has been updated to split the tx rate control
931 algorithm into a separate module. You need to include either
932 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
935 Support for systems with an 80386 CPU has been removed. Please
936 use FreeBSD 5.x or earlier on systems with an 80386.
939 We have had a hack which would mount the root filesystem
940 R/W if the device were named 'md*'. As part of the vnode
941 work I'm doing I have had to remove this hack. People
942 building systems which use preloaded MD root filesystems
943 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
944 their /etc/rc scripts.
947 FreeBSD 5.3 shipped here.
950 The size of struct tcpcb has changed again due to the removal
951 of RFC1644 T/TCP. You have to recompile userland programs that
952 read kmem for tcp sockets directly (netstat, sockstat, etc.)
955 The size of struct tcpcb has changed. You have to recompile
956 userland programs that read kmem for tcp sockets directly
957 (netstat, sockstat, etc.)
960 RELENG_5 branched here. For older entries, please see updating
961 in the RELENG_5 branch.
967 Avoid using make -j when upgrading. From time to time in the
968 past there have been problems using -j with buildworld and/or
969 installworld. This is especially true when upgrading between
970 "distant" versions (eg one that cross a major release boundary
971 or several minor releases, or when several months have passed
972 on the -current branch).
974 Sometimes, obscure build problems are the result of environment
975 poisoning. This can happen because the make utility reads its
976 environment when searching for values for global variables.
977 To run your build attempts in an "environmental clean room",
978 prefix all make commands with 'env -i '. See the env(1) manual
979 page for more details.
981 When upgrading from one major version to another it is generally
982 best to upgrade to the latest code in the currently installed branch
983 first, then do an upgrade to the new branch. This is the best-tested
984 upgrade path, and has the highest probability of being successful.
985 Please try this approach before reporting problems with a major
990 If you are updating from a prior version of FreeBSD (even one just
991 a few days old), you should follow this procedure. It is the most
992 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
994 make kernel-toolchain
995 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
996 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
998 To test a kernel once
999 ---------------------
1000 If you just want to boot a kernel once (because you are not sure
1001 if it works, or if you want to boot a known bad kernel to provide
1002 debugging information) run
1003 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1004 nextboot -k testkernel
1006 To just build a kernel when you know that it won't mess you up
1007 --------------------------------------------------------------
1008 This assumes you are already running a 5.X system. Replace
1009 ${arch} with the architecture of your machine (e.g. "i386",
1010 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1012 cd src/sys/${arch}/conf
1013 config KERNEL_NAME_HERE
1014 cd ../compile/KERNEL_NAME_HERE
1019 If this fails, go to the "To build a kernel" section.
1021 To rebuild everything and install it on the current system.
1022 -----------------------------------------------------------
1023 # Note: sometimes if you are running current you gotta do more than
1024 # is listed here if you are upgrading from a really old current.
1026 <make sure you have good level 0 dumps>
1028 make kernel KERNCONF=YOUR_KERNEL_HERE
1030 <reboot in single user> [3]
1038 To cross-install current onto a separate partition
1039 --------------------------------------------------
1040 # In this approach we use a separate partition to hold
1041 # current's root, 'usr', and 'var' directories. A partition
1042 # holding "/", "/usr" and "/var" should be about 2GB in
1045 <make sure you have good level 0 dumps>
1048 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1049 <maybe newfs current's root partition>
1050 <mount current's root partition on directory ${CURRENT_ROOT}>
1051 make installworld DESTDIR=${CURRENT_ROOT}
1052 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1053 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1054 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1055 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1056 <reboot into current>
1057 <do a "native" rebuild/install as described in the previous section>
1058 <maybe install compatibility libraries from ports/misc/compat*>
1062 To upgrade in-place from 5.x-stable to current
1063 ----------------------------------------------
1064 <make sure you have good level 0 dumps>
1066 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1068 <reboot in single user> [3]
1075 Make sure that you've read the UPDATING file to understand the
1076 tweaks to various things you need. At this point in the life
1077 cycle of current, things change often and you are on your own
1078 to cope. The defaults can also change, so please read ALL of
1079 the UPDATING entries.
1081 Also, if you are tracking -current, you must be subscribed to
1082 freebsd-current@freebsd.org. Make sure that before you update
1083 your sources that you have read and understood all the recent
1084 messages there. If in doubt, please track -stable which has
1085 much fewer pitfalls.
1087 [1] If you have third party modules, such as vmware, you
1088 should disable them at this point so they don't crash your
1091 [3] From the bootblocks, boot -s, and then do
1096 adjkerntz -i # if CMOS is wall time
1097 Also, when doing a major release upgrade, it is required that
1098 you boot into single user mode to do the installworld.
1100 [4] Note: This step is non-optional. Failure to do this step
1101 can result in a significant reduction in the functionality of the
1102 system. Attempting to do it by hand is not recommended and those
1103 that pursue this avenue should read this file carefully, as well
1104 as the archives of freebsd-current and freebsd-hackers mailing lists
1105 for potential gotchas.
1107 [5] Usually this step is a noop. However, from time to time
1108 you may need to do this if you get unknown user in the following
1109 step. It never hurts to do it all the time. You may need to
1110 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1111 install) after the buildworld before this step if you last updated
1112 from current before 20020224 or from -stable before 20020408.
1114 [8] In order to have a kernel that can run the 4.x binaries
1115 needed to do an installworld, you must include the COMPAT_FREEBSD4
1116 option in your kernel. Failure to do so may leave you with a system
1117 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
1118 is required to run the 5.x binaries on more recent kernels.
1120 Make sure that you merge any new devices from GENERIC since the
1121 last time you updated your kernel config file.
1123 [9] When checking out sources, you must include the -P flag to have
1124 cvs prune empty directories.
1126 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1127 "?=" instead of the "=" assignment operator, so that buildworld can
1128 override the CPUTYPE if it needs to.
1130 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1131 not on the command line, or in /etc/make.conf. buildworld will
1132 warn if it is improperly defined.
1135 This file contains a list, in reverse chronological order, of major
1136 breakages in tracking -current. Not all things will be listed here,
1137 and it only starts on October 16, 2004. Updating files can found in
1138 previous releases if your system is older than this.
1140 Copyright information:
1142 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
1144 Redistribution, publication, translation and use, with or without
1145 modification, in full or in part, in any form or format of this
1146 document are permitted without further permission from the author.
1148 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1149 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1150 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1151 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1152 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1153 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1154 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1155 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1156 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1157 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1158 POSSIBILITY OF SUCH DAMAGE.
1160 If you find this document useful, and you want to, you may buy the
1163 Contact Warner Losh if you have any questions about your use of