1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh
4 <imp@village.org>. See end of file for further details. For commonly
5 done items, please see the COMMON ITEMS: section later in the file.
7 Items affecting the ports and packages system can be found in
8 /usr/ports/UPDATING. Please read that file before running
11 NOTE TO PEOPLE WHO THINK THAT FreeBSD 8.x IS SLOW:
12 FreeBSD 8.x has many debugging features turned on, in
13 both the kernel and userland. These features attempt to detect
14 incorrect use of system primitives, and encourage loud failure
15 through extra sanity checking and fail stop semantics. They
16 also substantially impact system performance. If you want to
17 do performance measurement, benchmarking, and optimization,
18 you'll want to turn them off. This includes various WITNESS-
19 related kernel options, INVARIANTS, malloc debugging flags
20 in userland, and various verbose features in the kernel. Many
21 developers choose to disable these features on build machines
22 to maximize performance. (To disable malloc debugging, run
23 ln -s aj /etc/malloc.conf.)
26 The default NFS mount mode has changed from UDP to TCP for
27 increased reliability. If you rely on (insecurely) NFS
28 mounting across a firewall you may need to update your
32 Belatedly note the addition of m_collapse for compacting
36 The fts(3) structures have been changed to use adequate
37 integer types for their members and so to be able to cope
38 with huge file trees. The old fts(3) ABI is preserved
39 through symbol versioning in libc, so third-party binaries
40 using fts(3) should still work, although they will not take
41 advantage of the extended types. At the same time, some
42 third-party software might fail to build after this change
43 due to unportable assumptions made in its source code about
44 fts(3) structure members. Such software should be fixed
45 by its vendor or, in the worst case, in the ports tree.
46 FreeBSD_version 800015 marks this change for the unlikely
47 case that a portable fix is impossible.
50 To upgrade to -current after this date, you must be running
51 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
52 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
55 The ADAPTIVE_GIANT kernel option has been retired because its
56 functionality is the default now.
59 The AT keyboard emulation of sunkbd(4) has been turned on
60 by default. In order to make the special symbols of the Sun
61 keyboards driven by sunkbd(4) work under X these now have
62 to be configured the same way as Sun USB keyboards driven
63 by ukbd(4) (which also does AT keyboard emulation), f.e.:
65 Option "XkbLayout" "us"
66 Option "XkbRules" "xorg"
67 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
70 It has been decided that it is desirable to provide ABI
71 backwards compatibility to the FreeBSD 4/5/6 versions of the
72 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
73 broken with the introduction of PCI domain support (see the
74 20070930 entry). Unfortunately, this required the ABI of
75 PCIOCGETCONF to be broken again in order to be able to
76 provide backwards compatibility to the old version of that
77 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
78 again. As for prominent ports this affects neither pciutils
79 nor xorg-server this time, the hal port needs to be rebuilt
83 The misnamed kthread_create() and friends have been renamed
84 to kproc_create() etc. Many of the callers already
86 I will return kthread_create() and friends in a while
87 with implementations that actually create threads, not procs.
88 Renaming corresponds with version 800002.
94 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
95 WITHOUT_LIBTHR are set.
98 The PCI code has been made aware of PCI domains. This means that
99 the location strings as used by pciconf(8) etc are now in the
100 following format: pci<domain>:<bus>:<device>[:<function>]. It
101 also means that consumers of <sys/pciio.h> potentially need to
102 be recompiled; this includes the hal and xorg-server ports.
105 The caching daemon (cached) was renamed to nscd. nscd.conf
106 configuration file should be used instead of cached.conf and
107 nscd_enable, nscd_pidfile and nscd_flags options should be used
108 instead of cached_enable, cached_pidfile and cached_flags in
112 The getfacl(1) utility now prints owning user and group name
113 instead of owning uid and gid in the three line comment header.
114 This is the same behavior as getfacl(1) on Solaris and Linux.
117 The new IPsec code is now compiled in using the IPSEC option. The
118 IPSEC option now requires "device crypto" be defined in your kernel
119 configuration. The FAST_IPSEC kernel option is now deprecated.
122 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
123 note the changed syntax - keep state is now on by default. Also
124 note the fact that ftp-proxy(8) has been changed from bottom up and
125 has been moved from libexec to usr/sbin. Changes in the ALTQ
126 handling also affect users of IPFW's ALTQ capabilities.
129 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
130 only IPsec supported by FreeBSD. The new IPsec stack
131 supports both IPv4 and IPv6. The kernel option will change
132 after the code changes have settled in. For now the kernel
133 option IPSEC is deprecated and FAST_IPSEC is the only option, that
134 will change after some settling time.
137 The wicontrol(8) utility has been removed from the base system. wi(4)
138 cards should be configured using ifconfig(8), see the man page for more
142 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
143 instead of the nve(4) driver. Please update your configuration
147 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
148 database if it is missing or older than the aliases file. If
149 desired, set the new rc.conf option sendmail_rebuild_aliases
150 to "YES" to restore that functionality.
153 The IPv4 multicast socket code has been considerably modified, and
154 moved to the file sys/netinet/in_mcast.c. Initial support for the
155 RFC 3678 Source-Specific Multicast Socket API has been added to
156 the IPv4 network stack.
158 Strict multicast and broadcast reception is now the default for
159 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
160 has now been removed.
162 The RFC 1724 hack for interface selection has been removed; the use
163 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
164 been added to replace it. Consumers such as routed will soon be
165 updated to reflect this.
167 These changes affect users who are running routed(8) or rdisc(8)
168 from the FreeBSD base system on point-to-point or unnumbered
172 The net80211 layer has changed significantly and all wireless
173 drivers that depend on it need to be recompiled. Further these
174 changes require that any program that interacts with the wireless
175 support in the kernel be recompiled; this includes: ifconfig,
176 wpa_supplicant, hostapd, and wlanstats. Users must also, for
177 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
178 if they use modules for wireless support. These modules implement
179 scanning support for station and ap modes, respectively. Failure
180 to load the appropriate module before marking a wireless interface
181 up will result in a message to the console and the device not
185 The pam_nologin(8) module ceases to provide an authentication
186 function and starts providing an account management function.
187 Consequent changes to /etc/pam.d should be brought in using
188 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
189 need manual editing as follows. Locate this line (or similar):
191 auth required pam_nologin.so no_warn
193 and change it according to this example:
195 account required pam_nologin.so no_warn
197 That is, the first word needs to be changed from "auth" to
198 "account". The new line can be moved to the account section
199 within the file for clarity. Not updating pam.conf(5) files
200 will result in nologin(5) ignored by the respective services.
203 The ether_ioctl() function has been synchronized with ioctl(2)
204 and ifnet.if_ioctl. Due to that, the size of one of its arguments
205 has changed on 64-bit architectures. All kernel modules using
206 ether_ioctl() need to be rebuilt on such architectures.
209 Improved INCLUDE_CONFIG_FILE support has been introduced to the
210 config(8) utility. In order to take advantage of this new
211 functionality, you are expected to recompile and install
212 src/usr.sbin/config. If you don't rebuild config(8), and your
213 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
214 build will be broken because of a missing "kernconfstring"
218 Symbol versioning is enabled by default. To disable it, use
219 option WITHOUT_SYMVER. It is not advisable to attempt to
220 disable symbol versioning once it is enabled; your installworld
221 will break because a symbol version-less libc will get installed
222 before the install tools. As a result, the old install tools,
223 which previously had symbol dependencies to FBSD_1.0, will fail
224 because the freshly installed libc will not have them.
226 The default threading library (providing "libpthread") has been
227 changed to libthr. If you wish to have libkse as your default,
228 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
231 The ABI breakage in sendmail(8)'s libmilter has been repaired
232 so it is no longer necessary to recompile mail filters (aka,
233 milters). If you recompiled mail filters after the 20070408
234 note, it is not necessary to recompile them again.
237 The new trunk(4) driver has been renamed to lagg(4) as it better
238 reflects its purpose. ifconfig will need to be recompiled.
241 sendmail(8) has been updated to version 8.14.1. Mail filters
242 (aka, milters) compiled against the libmilter included in the
243 base operating system should be recompiled.
246 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
247 In order to use them one must agree to the respective LICENSE in
248 share/doc/legal and define legal.intel_<name>.license_ack=1 via
249 loader.conf(5) or kenv(1). Make sure to deinstall the now
250 deprecated modules from the respective firmware ports.
253 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
254 were removed from FreeBSD's libc. These originally came from INRIA
255 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
256 deprecated in previous releases.
257 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
258 replace it as a more portable (and re-entrant) API.
261 To support interrupt filtering a modification to the newbus API
262 has occurred, ABI was broken and __FreeBSD_version was bumped
263 to 700031. Please make sure that your kernel and modules are in
265 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
268 The IPv6 multicast forwarding code may now be loaded into GENERIC
269 kernels by loading the ip_mroute.ko module. This is built into the
270 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
271 set; see src.conf(5) for more information.
274 The output of netstat -r has changed. Without -n, we now only
275 print a "network name" without the prefix length if the network
276 address and mask exactly match a Class A/B/C network, and an entry
277 exists in the nsswitch "networks" map.
278 With -n, we print the full unabbreviated CIDR network prefix in
279 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
280 This change is in preparation for changes such as equal-cost
281 multipath, and to more generally assist operational deployment
282 of FreeBSD as a modern IPv4 router.
285 PIM has been turned on by default in the IPv4 multicast
286 routing code. The kernel option 'PIM' has now been removed.
287 PIM is now built by default if option 'MROUTING' is specified.
288 It may now be loaded into GENERIC kernels by loading the
292 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
293 has been removed. Its functionality may be achieved by explicitly
294 configuring gif(4) interfaces and using the 'phyint' keyword in
296 XORP does not support source-routed IPv4 multicast tunnels nor the
297 integrated IPIP tunneling, therefore it is not affected by this
298 change. The __FreeBSD_version macro has been bumped to 700030.
301 Support for PCI Message Signalled Interrupts has been
302 re-enabled in the bge driver, only for those chips which are
303 believed to support it properly. If there are any problems,
304 MSI can be disabled completely by setting the
305 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
309 Support for PCI Message Signalled Interrupts has been
310 disabled again in the bge driver. Many revisions of the
311 hardware fail to support it properly. Support can be
312 re-enabled by removing the #define of BGE_DISABLE_MSI in
313 "src/sys/dev/bge/if_bge.c".
316 Support for PCI Message Signalled Interrupts has been added
317 to the bge driver. If there are any problems, MSI can be
318 disabled completely by setting the 'hw.pci.enable_msi' and
319 'hw.pci.enable_msix' tunables to 0 in the loader.
322 The removal of several facets of the experimental Threading
323 system from the kernel means that the proc and thread structures
324 have changed quite a bit. I suggest all kernel modules that might
325 reference these structures be recompiled.. Especially the
329 Sound infrastructure has been updated with various fixes and
330 improvements. Most of the changes are pretty much transparent,
331 with exceptions of followings:
332 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
333 moved to their own dev sysctl nodes, for example:
334 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
335 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
336 own chardev in the form of "dsp%d.<function>%d", where <function>
337 is p = playback, r = record and v = virtual, respectively. Users
338 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
339 This does not affect those who are using "/dev/dsp".
342 The following binaries have been disconnected from the build:
343 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
344 and mount_std. The functionality of these programs has been
345 moved into the mount program. For example, to mount a devfs
346 filesystem, instead of using mount_devfs, use: "mount -t devfs".
347 This does not affect entries in /etc/fstab, since entries in
348 /etc/fstab are always processed with "mount -t fstype".
351 Support for PCI Message Signalled Interrupts on i386 and amd64
352 has been added to the kernel and various drivers will soon be
353 updated to use MSI when it is available. If there are any problems,
354 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
355 and 'hw.pci.enable_msix' tunables to 0 in the loader.
358 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
359 The lockmgr object layout has been changed as a result of having
360 a lock_object embedded in it. As a consequence all file system
361 kernel modules must be re-compiled. The mutex profiling man page
362 has not yet been updated to reflect this change.
365 KSE in the kernel has now been made optional and turned on by
366 default. Use 'nooption KSE' in your kernel config to turn it
367 off. All kernel modules *must* be recompiled after this change.
368 There-after, modules from a KSE kernel should be compatible with
369 modules from a NOKSE kernel due to the temporary padding fields
370 added to 'struct proc'.
373 mrouted and its utilities have been removed from the base system.
376 Some ioctl(2) command codes have changed. Full backward ABI
377 compatibility is provided if the "options COMPAT_FREEBSD6" is
378 present in the kernel configuration file. Make sure to add
379 this option to your kernel config file, or recompile X.Org
380 and the rest of ports; otherwise they may refuse to work.
383 tcpslice has been removed from the base system.
386 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
387 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
388 systat needs to be rebuilt.
391 libpcap updated to v0.9.4 and tcpdump to v3.9.4
394 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
395 for IPFIREWALL_FORWARD is now as it was before when it was first
396 committed and for years after. The behaviour is now ON.
399 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
400 Now it can decrypt files created from different architectures.
401 Unfortunately, it is no longer able to decrypt a cipher text
402 generated with an older version on 64 bit architectures.
403 If you have such a file, you need old utility to decrypt it.
406 The interface version of the i4b kernel part has changed. So
407 after updating the kernel sources and compiling a new kernel,
408 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
409 be rebuilt, and vice versa.
412 The XBOX kernel now defaults to the nfe(4) driver instead of
413 the nve(4) driver. Please update your configuration
417 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
418 PCnet family of NICs has been removed. The new le(4) driver serves
419 as an equivalent but cross-platform replacement with the pcn(4)
420 driver still providing performance-optimized support for the subset
421 of AMD Am79C971 PCnet-FAST and greater chips as before.
424 The machdep.* sysctls and the adjkerntz utility have been
425 modified a bit. The new adjkerntz utility uses the new
426 sysctl names and sysctlbyname() calls, so it may be impossible
427 to run an old /sbin/adjkerntz utility in single-user mode
428 with a new kernel. Replace the `adjkerntz -i' step before
429 `make installworld' with:
431 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
433 and proceed as usual with the rest of the installworld-stage
434 steps. Otherwise, you risk installing binaries with their
435 timestamp set several hours in the future, especially if
436 you are running with local time set to GMT+X hours.
439 The ip6fw utility has been removed. The behavior provided by
440 ip6fw has been in ipfw2 for a good while and the rc.d scripts
441 have been updated to deal with it. There are some rules that
442 might not migrate cleanly. Use rc.firewall6 as a template to
446 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
447 attachments have been removed. Make sure to configure scc(4)
448 on sparc64. Note also that by default puc(4) will use uart(4)
449 and not sio(4) for serial ports because interrupt handling has
450 been optimized for multi-port serial cards and only uart(4)
451 implements the interface to support it.
454 The scc(4) driver replaces puc(4) for Serial Communications
455 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
456 Z8530. On sparc64, it is advised to add scc(4) to the kernel
457 configuration to make sure that the serial ports remain
461 Most world/kernel related NO_* build options changed names.
462 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
463 after FreeBSD ports) and should be set in /etc/src.conf
464 (the src.conf(5) manpage is provided). Full backwards
465 compatibility is maintained for the time being though it's
466 highly recommended to start moving old options out of the
467 system-wide /etc/make.conf file into the new /etc/src.conf
468 while also properly renaming them. More conversions will
469 likely follow. Posting to current@:
471 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
474 The NETSMBCRYPTO kernel option has been retired because its
475 functionality is always included in NETSMB and smbfs.ko now.
478 The TDFX_LINUX kernel option was retired and replaced by the
479 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
480 kernel module. Loading it alone should suffice to get 3dfx support
481 for Linux apps because it will pull in 3dfx.ko and linux.ko through
485 The 'audit' group was added to support the new auditing functionality
486 in the base system. Be sure to follow the directions for updating,
487 including the requirement to run mergemaster -p.
490 The kernel ABI to file system modules was changed on i386.
491 Please make sure that your kernel and modules are in sync.
494 This actually occured some time ago, but installing the kernel
495 now also installs a bunch of symbol files for the kernel modules.
496 This increases the size of /boot/kernel to about 67Mbytes. You
497 will need twice this if you will eventually back this up to kernel.old
498 on your next install.
499 If you have a shortage of room in your root partition, you should add
500 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
501 to your /etc/make.conf.
504 libc's malloc implementation has been replaced. This change has the
505 potential to uncover application bugs that previously went unnoticed.
506 See the malloc(3) manual page for more details.
509 The generic netgraph(4) cookie has been changed. If you upgrade
510 kernel passing this point, you also need to upgrade userland
511 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
514 si(4)'s device files now contain the unit number.
515 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
518 The kernel ABI was mostly destroyed due to a change in the size
519 of struct lock_object which is nested in other structures such
520 as mutexes which are nested in all sorts of other structures.
521 Make sure your kernel and modules are in sync.
524 The page coloring algorithm in the VM subsystem was converted
525 from tuning with kernel options to autotuning. Please remove
526 any PQ_* option except PQ_NOOPT from your kernel config.
529 The net80211-related tools in the tools/tools/ath directory
530 have been moved to tools/tools/net80211 and renamed with a
531 "wlan" prefix. Scripts that use them should be adjusted
535 Scripts in the local_startup directories (as defined in
536 /etc/defaults/rc.conf) that have the new rc.d semantics will
537 now be run as part of the base system rcorder. If there are
538 errors or problems with one of these local scripts, it could
539 cause boot problems. If you encounter such problems, boot in
540 single user mode, remove that script from the */rc.d directory.
541 Please report the problem to the port's maintainer, and the
542 freebsd-ports@freebsd.org mailing list.
545 The nodev mount option was deprecated in RELENG_6 (where it
546 was a no-op), and is now unsupported. If you have nodev or dev listed
547 in /etc/fstab, remove it, otherwise it will result in a mount error.
550 ABI between ipfw(4) and ipfw(8) has been changed. You need
551 to rebuild ipfw(8) when rebuilding kernel.
554 rp(4)'s device files now contain the unit number.
555 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
558 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
559 Its /etc/rc.conf.d configuration file has been `ppp' from
560 the beginning, and hence there is no need to touch it.
563 Now most modules get their build-time options from the kernel
564 configuration file. A few modules still have fixed options
565 due to their non-conformant implementation, but they will be
566 corrected eventually. You may need to review the options of
567 the modules in use, explicitly specify the non-default options
568 in the kernel configuration file, and rebuild the kernel and
572 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
573 to turn polling(4) on your interfaces.
576 The old bridge(4) implementation was retired. The new
577 if_bridge(4) serves as a full functional replacement.
580 The ai_addrlen of a struct addrinfo was changed to a socklen_t
581 to conform to POSIX-2001. This change broke an ABI
582 compatibility on 64 bit architecture. You have to recompile
583 userland programs that use getaddrinfo(3) on 64 bit
587 RELENG_6 branched here.
590 The pccard_ifconfig rc.conf variable has been removed and a new
591 variable, ifconfig_DEFAULT has been introduced. Unlike
592 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
593 do not have ifconfig_ifn entries rather than just those in
594 removable_interfaces.
597 Some previous versions of PAM have permitted the use of
598 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
599 to third party PAM modules in /usr/local/lib. A change has been
600 made to require the use of absolute paths in order to avoid
601 ambiguity and dependence on library path configuration, which may
602 affect existing configurations.
605 Major changes to network interface API. All drivers must be
606 recompiled. Drivers not in the base system will need to be
607 updated to the new APIs.
610 Changes were made to kinfo_proc in sys/user.h. Please recompile
611 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
612 will not behave correctly.
614 The API and ABI for hwpmc(4) have changed with the addition
615 of sampling support. Please recompile lib/libpmc(3) and
616 usr.sbin/{pmcstat,pmccontrol}.
619 The OpenBSD dhclient was imported in place of the ISC dhclient
620 and the network interface configuration scripts were updated
621 accordingly. If you use DHCP to configure your interfaces, you
622 must now run devd. Also, DNS updating was lost so you will need
623 to find a workaround if you use this feature.
625 The '_dhcp' user was added to support the OpenBSD dhclient. Be
626 sure to run mergemaster -p (like you are supposed to do every time
630 if_bridge was added to the tree. This has changed struct ifnet.
631 Please recompile userland and all network related modules.
634 The n_net of a struct netent was changed to an uint32_t, and
635 1st argument of getnetbyaddr() was changed to an uint32_t, to
636 conform to POSIX-2001. These changes broke an ABI
637 compatibility on 64 bit architecture. With these changes,
638 shlib major of libpcap was bumped. You have to recompile
639 userland programs that use getnetbyaddr(3), getnetbyname(3),
640 getnetent(3) and/or libpcap on 64 bit architecture.
643 Kernel parsing of extra options on '#!' first lines of shell
644 scripts has changed. Lines with multiple options likely will
645 fail after this date. For full details, please see
646 http://people.freebsd.org/~gad/Updating-20050528.txt
649 The packet filter (pf) code has been updated to OpenBSD 3.7
650 Please note the changed anchor syntax and the fact that
651 authpf(8) now needs a mounted fdescfs(5) to function.
654 The NO_MIXED_MODE kernel option has been removed from the i386
655 amd64 platforms as its use has been superceded by the new local
656 APIC timer code. Any kernel config files containing this option
660 The on-disk format of LC_CTYPE files was changed to be machine
661 independent. Please make sure NOT to use NO_CLEAN buildworld
662 when crossing this point. Crossing this point also requires
663 recompile or reinstall of all locale depended packages.
666 The ifi_epoch member of struct if_data has been changed to
667 contain the uptime at which the interface was created or the
668 statistics zeroed rather then the wall clock time because
669 wallclock time may go backwards. This should have no impact
670 unless an snmp implementation is using this value (I know of
674 The acpi_perf and acpi_throttle drivers are now part of the
675 acpi(4) main module. They are no longer built separately.
678 The layout of struct image_params has changed. You have to
679 recompile all compatibility modules (linux, svr4, etc) for use
683 The p4tcc driver has been merged into cpufreq(4). This makes
684 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
685 compile in "device cpufreq" to restore this functionality.
688 The responsibility of recomputing the file system summary of
689 a SoftUpdates-enabled dirty volume has been transferred to the
690 background fsck. A rebuild of fsck(8) utility is recommended
691 if you have updated the kernel.
693 To get the old behavior (recompute file system summary at mount
694 time), you can set vfs.ffs.compute_summary_at_mount=1 before
695 mounting the new volume.
698 The cpufreq import is complete. As part of this, the sysctls for
699 acpi(4) throttling have been removed. The power_profile script
700 has been updated, so you can use performance/economy_cpu_freq in
701 rc.conf(5) to set AC on/offline cpu frequencies.
704 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
705 requires recompiling libnetgraph and userland netgraph utilities.
708 Support for abbreviated forms of a number of ipfw options is
709 now deprecated. Warnings are printed to stderr indicating the
710 correct full form when a match occurs. Some abbreviations may
711 be supported at a later date based on user feedback. To be
712 considered for support, abbreviations must be in use prior to
713 this commit and unlikely to be confused with current key words.
716 By a popular demand, a lot of NOFOO options were renamed
717 to NO_FOO (see bsd.compat.mk for a full list). The old
718 spellings are still supported, but will cause annoying
719 warnings on stderr. Make sure you upgrade properly (see
720 the COMMON ITEMS: section later in this file).
723 Auto-loading of ancillary wlan modules such as wlan_wep has
724 been temporarily disabled; you need to statically configure
725 the modules you need into your kernel or explicitly load them
726 prior to use. Specifically, if you intend to use WEP encryption
727 with an 802.11 device load/configure wlan_wep; if you want to
728 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
729 and wlan_xauth as required.
732 The behaviour of ppp(8) has changed slightly. If lqr is enabled
733 (``enable lqr''), older versions would revert to LCP ECHO mode on
734 negotiation failure. Now, ``enable echo'' is required for this
735 behaviour. The ppp version number has been bumped to 3.4.2 to
739 The wlan support has been updated to split the crypto support
740 into separate modules. For static WEP you must configure the
741 wlan_wep module in your system or build and install the module
742 in place where it can be loaded (the kernel will auto-load
743 the module when a wep key is configured).
746 The ath driver has been updated to split the tx rate control
747 algorithm into a separate module. You need to include either
748 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
751 Support for systems with an 80386 CPU has been removed. Please
752 use FreeBSD 5.x or earlier on systems with an 80386.
755 We have had a hack which would mount the root filesystem
756 R/W if the device were named 'md*'. As part of the vnode
757 work I'm doing I have had to remove this hack. People
758 building systems which use preloaded MD root filesystems
759 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
760 their /etc/rc scripts.
763 FreeBSD 5.3 shipped here.
766 The size of struct tcpcb has changed again due to the removal
767 of RFC1644 T/TCP. You have to recompile userland programs that
768 read kmem for tcp sockets directly (netstat, sockstat, etc.)
771 The size of struct tcpcb has changed. You have to recompile
772 userland programs that read kmem for tcp sockets directly
773 (netstat, sockstat, etc.)
776 RELENG_5 branched here. For older entries, please see updating
777 in the RELENG_5 branch.
783 Avoid using make -j when upgrading. From time to time in the
784 past there have been problems using -j with buildworld and/or
785 installworld. This is especially true when upgrading between
786 "distant" versions (eg one that cross a major release boundary
787 or several minor releases, or when several months have passed
788 on the -current branch).
790 Sometimes, obscure build problems are the result of environment
791 poisoning. This can happen because the make utility reads its
792 environment when searching for values for global variables.
793 To run your build attempts in an "environmental clean room",
794 prefix all make commands with 'env -i '. See the env(1) manual
795 page for more details.
797 When upgrading from one major version to another it is generally
798 best to upgrade to the latest code in the currently installed branch
799 first, then do an upgrade to the new branch. This is the best-tested
800 upgrade path, and has the highest probability of being successful.
801 Please try this approach before reporting problems with a major
806 If you are updating from a prior version of FreeBSD (even one just
807 a few days old), you should follow this procedure. It is the most
808 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
810 make kernel-toolchain
811 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
812 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
814 To test a kernel once
815 ---------------------
816 If you just want to boot a kernel once (because you are not sure
817 if it works, or if you want to boot a known bad kernel to provide
818 debugging information) run
819 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
820 nextboot -k testkernel
822 To just build a kernel when you know that it won't mess you up
823 --------------------------------------------------------------
824 This assumes you are already running a 5.X system. Replace
825 ${arch} with the architecture of your machine (e.g. "i386",
826 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
828 cd src/sys/${arch}/conf
829 config KERNEL_NAME_HERE
830 cd ../compile/KERNEL_NAME_HERE
835 If this fails, go to the "To build a kernel" section.
837 To rebuild everything and install it on the current system.
838 -----------------------------------------------------------
839 # Note: sometimes if you are running current you gotta do more than
840 # is listed here if you are upgrading from a really old current.
842 <make sure you have good level 0 dumps>
844 make kernel KERNCONF=YOUR_KERNEL_HERE
846 <reboot in single user> [3]
854 To cross-install current onto a separate partition
855 --------------------------------------------------
856 # In this approach we use a separate partition to hold
857 # current's root, 'usr', and 'var' directories. A partition
858 # holding "/", "/usr" and "/var" should be about 2GB in
861 <make sure you have good level 0 dumps>
864 make buildkernel KERNCONF=YOUR_KERNEL_HERE
865 <maybe newfs current's root partition>
866 <mount current's root partition on directory ${CURRENT_ROOT}>
867 make installworld DESTDIR=${CURRENT_ROOT}
868 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
869 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
870 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
871 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
872 <reboot into current>
873 <do a "native" rebuild/install as described in the previous section>
874 <maybe install compatibility libraries from src/lib/compat>
878 To upgrade in-place from 5.x-stable to current
879 ----------------------------------------------
880 <make sure you have good level 0 dumps>
882 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
884 <reboot in single user> [3]
891 Make sure that you've read the UPDATING file to understand the
892 tweaks to various things you need. At this point in the life
893 cycle of current, things change often and you are on your own
894 to cope. The defaults can also change, so please read ALL of
895 the UPDATING entries.
897 Also, if you are tracking -current, you must be subscribed to
898 freebsd-current@freebsd.org. Make sure that before you update
899 your sources that you have read and understood all the recent
900 messages there. If in doubt, please track -stable which has
903 [1] If you have third party modules, such as vmware, you
904 should disable them at this point so they don't crash your
907 [3] From the bootblocks, boot -s, and then do
912 adjkerntz -i # if CMOS is wall time
913 Also, when doing a major release upgrade, it is required that
914 you boot into single user mode to do the installworld.
916 [4] Note: This step is non-optional. Failure to do this step
917 can result in a significant reduction in the functionality of the
918 system. Attempting to do it by hand is not recommended and those
919 that pursue this avenue should read this file carefully, as well
920 as the archives of freebsd-current and freebsd-hackers mailing lists
921 for potential gotchas.
923 [5] Usually this step is a noop. However, from time to time
924 you may need to do this if you get unknown user in the following
925 step. It never hurts to do it all the time. You may need to
926 install a new mergemaster (cd src/usr.sbin/mergemaster && make
927 install) after the buildworld before this step if you last updated
928 from current before 20020224 or from -stable before 20020408.
930 [8] In order to have a kernel that can run the 4.x binaries
931 needed to do an installworld, you must include the COMPAT_FREEBSD4
932 option in your kernel. Failure to do so may leave you with a system
933 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
934 is required to run the 5.x binaries on more recent kernels.
936 Make sure that you merge any new devices from GENERIC since the
937 last time you updated your kernel config file.
939 [9] When checking out sources, you must include the -P flag to have
940 cvs prune empty directories.
942 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
943 "?=" instead of the "=" assignment operator, so that buildworld can
944 override the CPUTYPE if it needs to.
946 MAKEOBJDIRPREFIX must be defined in an environment variable, and
947 not on the command line, or in /etc/make.conf. buildworld will
948 warn if it is improperly defined.
951 This file contains a list, in reverse chronological order, of major
952 breakages in tracking -current. Not all things will be listed here,
953 and it only starts on October 16, 2004. Updating files can found in
954 previous releases if your system is older than this.
956 Copyright information:
958 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
960 Redistribution, publication, translation and use, with or without
961 modification, in full or in part, in any form or format of this
962 document are permitted without further permission from the author.
964 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
965 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
966 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
967 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
968 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
969 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
970 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
971 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
972 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
973 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
974 POSSIBILITY OF SUCH DAMAGE.
976 If you find this document useful, and you want to, you may buy the
979 Contact Warner Losh if you have any questions about your use of