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 psm(4) has gained write(2) support in native operation level.
27 Arbitrary commands can be written to /dev/psm%d and status can
28 be read back from it. Therefore, an application is responsible
29 for status validation and error recovery. It is a no-op in
30 other operation levels.
33 Support for KSE threading has been removed from the kernel. To
34 run legacy applications linked against KSE libmap.conf may
35 be used. The following libmap.conf may be used to ensure
36 compatibility with any prior release:
38 libpthread.so.1 libthr.so.1
39 libpthread.so.2 libthr.so.2
40 libkse.so.3 libthr.so.3
43 The layout of struct vmspace has changed. This affects libkvm
44 and any executables that link against libkvm and use the
45 kvm_getprocs() function. In particular, but not exclusively,
46 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
47 The effects are minimal, but it's advisable to upgrade world
51 The latest em driver no longer has support in it for the
52 82575 adapter, this is now moved to the igb driver. The
53 split was done to make new features that are incompatible
54 with older hardware easier to do.
57 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
58 likewise the kernel option is now GEOM_LINUX_LVM.
61 The default NFS mount mode has changed from UDP to TCP for
62 increased reliability. If you rely on (insecurely) NFS
63 mounting across a firewall you may need to update your
67 Belatedly note the addition of m_collapse for compacting
71 The fts(3) structures have been changed to use adequate
72 integer types for their members and so to be able to cope
73 with huge file trees. The old fts(3) ABI is preserved
74 through symbol versioning in libc, so third-party binaries
75 using fts(3) should still work, although they will not take
76 advantage of the extended types. At the same time, some
77 third-party software might fail to build after this change
78 due to unportable assumptions made in its source code about
79 fts(3) structure members. Such software should be fixed
80 by its vendor or, in the worst case, in the ports tree.
81 FreeBSD_version 800015 marks this change for the unlikely
82 case that a portable fix is impossible.
85 To upgrade to -current after this date, you must be running
86 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
87 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
90 The ADAPTIVE_GIANT kernel option has been retired because its
91 functionality is the default now.
94 The AT keyboard emulation of sunkbd(4) has been turned on
95 by default. In order to make the special symbols of the Sun
96 keyboards driven by sunkbd(4) work under X these now have
97 to be configured the same way as Sun USB keyboards driven
98 by ukbd(4) (which also does AT keyboard emulation), f.e.:
100 Option "XkbLayout" "us"
101 Option "XkbRules" "xorg"
102 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
105 It has been decided that it is desirable to provide ABI
106 backwards compatibility to the FreeBSD 4/5/6 versions of the
107 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
108 broken with the introduction of PCI domain support (see the
109 20070930 entry). Unfortunately, this required the ABI of
110 PCIOCGETCONF to be broken again in order to be able to
111 provide backwards compatibility to the old version of that
112 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
113 again. As for prominent ports this affects neither pciutils
114 nor xorg-server this time, the hal port needs to be rebuilt
118 The misnamed kthread_create() and friends have been renamed
119 to kproc_create() etc. Many of the callers already
121 I will return kthread_create() and friends in a while
122 with implementations that actually create threads, not procs.
123 Renaming corresponds with version 800002.
129 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
130 WITHOUT_LIBTHR are set.
133 The PCI code has been made aware of PCI domains. This means that
134 the location strings as used by pciconf(8) etc are now in the
135 following format: pci<domain>:<bus>:<device>[:<function>]. It
136 also means that consumers of <sys/pciio.h> potentially need to
137 be recompiled; this includes the hal and xorg-server ports.
140 The caching daemon (cached) was renamed to nscd. nscd.conf
141 configuration file should be used instead of cached.conf and
142 nscd_enable, nscd_pidfile and nscd_flags options should be used
143 instead of cached_enable, cached_pidfile and cached_flags in
147 The getfacl(1) utility now prints owning user and group name
148 instead of owning uid and gid in the three line comment header.
149 This is the same behavior as getfacl(1) on Solaris and Linux.
152 The new IPsec code is now compiled in using the IPSEC option. The
153 IPSEC option now requires "device crypto" be defined in your kernel
154 configuration. The FAST_IPSEC kernel option is now deprecated.
157 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
158 note the changed syntax - keep state is now on by default. Also
159 note the fact that ftp-proxy(8) has been changed from bottom up and
160 has been moved from libexec to usr/sbin. Changes in the ALTQ
161 handling also affect users of IPFW's ALTQ capabilities.
164 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
165 only IPsec supported by FreeBSD. The new IPsec stack
166 supports both IPv4 and IPv6. The kernel option will change
167 after the code changes have settled in. For now the kernel
168 option IPSEC is deprecated and FAST_IPSEC is the only option, that
169 will change after some settling time.
172 The wicontrol(8) utility has been removed from the base system. wi(4)
173 cards should be configured using ifconfig(8), see the man page for more
177 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
178 instead of the nve(4) driver. Please update your configuration
182 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
183 database if it is missing or older than the aliases file. If
184 desired, set the new rc.conf option sendmail_rebuild_aliases
185 to "YES" to restore that functionality.
188 The IPv4 multicast socket code has been considerably modified, and
189 moved to the file sys/netinet/in_mcast.c. Initial support for the
190 RFC 3678 Source-Specific Multicast Socket API has been added to
191 the IPv4 network stack.
193 Strict multicast and broadcast reception is now the default for
194 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
195 has now been removed.
197 The RFC 1724 hack for interface selection has been removed; the use
198 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
199 been added to replace it. Consumers such as routed will soon be
200 updated to reflect this.
202 These changes affect users who are running routed(8) or rdisc(8)
203 from the FreeBSD base system on point-to-point or unnumbered
207 The net80211 layer has changed significantly and all wireless
208 drivers that depend on it need to be recompiled. Further these
209 changes require that any program that interacts with the wireless
210 support in the kernel be recompiled; this includes: ifconfig,
211 wpa_supplicant, hostapd, and wlanstats. Users must also, for
212 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
213 if they use modules for wireless support. These modules implement
214 scanning support for station and ap modes, respectively. Failure
215 to load the appropriate module before marking a wireless interface
216 up will result in a message to the console and the device not
220 The pam_nologin(8) module ceases to provide an authentication
221 function and starts providing an account management function.
222 Consequent changes to /etc/pam.d should be brought in using
223 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
224 need manual editing as follows. Locate this line (or similar):
226 auth required pam_nologin.so no_warn
228 and change it according to this example:
230 account required pam_nologin.so no_warn
232 That is, the first word needs to be changed from "auth" to
233 "account". The new line can be moved to the account section
234 within the file for clarity. Not updating pam.conf(5) files
235 will result in nologin(5) ignored by the respective services.
238 The ether_ioctl() function has been synchronized with ioctl(2)
239 and ifnet.if_ioctl. Due to that, the size of one of its arguments
240 has changed on 64-bit architectures. All kernel modules using
241 ether_ioctl() need to be rebuilt on such architectures.
244 Improved INCLUDE_CONFIG_FILE support has been introduced to the
245 config(8) utility. In order to take advantage of this new
246 functionality, you are expected to recompile and install
247 src/usr.sbin/config. If you don't rebuild config(8), and your
248 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
249 build will be broken because of a missing "kernconfstring"
253 Symbol versioning is enabled by default. To disable it, use
254 option WITHOUT_SYMVER. It is not advisable to attempt to
255 disable symbol versioning once it is enabled; your installworld
256 will break because a symbol version-less libc will get installed
257 before the install tools. As a result, the old install tools,
258 which previously had symbol dependencies to FBSD_1.0, will fail
259 because the freshly installed libc will not have them.
261 The default threading library (providing "libpthread") has been
262 changed to libthr. If you wish to have libkse as your default,
263 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
266 The ABI breakage in sendmail(8)'s libmilter has been repaired
267 so it is no longer necessary to recompile mail filters (aka,
268 milters). If you recompiled mail filters after the 20070408
269 note, it is not necessary to recompile them again.
272 The new trunk(4) driver has been renamed to lagg(4) as it better
273 reflects its purpose. ifconfig will need to be recompiled.
276 sendmail(8) has been updated to version 8.14.1. Mail filters
277 (aka, milters) compiled against the libmilter included in the
278 base operating system should be recompiled.
281 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
282 In order to use them one must agree to the respective LICENSE in
283 share/doc/legal and define legal.intel_<name>.license_ack=1 via
284 loader.conf(5) or kenv(1). Make sure to deinstall the now
285 deprecated modules from the respective firmware ports.
288 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
289 were removed from FreeBSD's libc. These originally came from INRIA
290 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
291 deprecated in previous releases.
292 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
293 replace it as a more portable (and re-entrant) API.
296 To support interrupt filtering a modification to the newbus API
297 has occurred, ABI was broken and __FreeBSD_version was bumped
298 to 700031. Please make sure that your kernel and modules are in
300 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
303 The IPv6 multicast forwarding code may now be loaded into GENERIC
304 kernels by loading the ip_mroute.ko module. This is built into the
305 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
306 set; see src.conf(5) for more information.
309 The output of netstat -r has changed. Without -n, we now only
310 print a "network name" without the prefix length if the network
311 address and mask exactly match a Class A/B/C network, and an entry
312 exists in the nsswitch "networks" map.
313 With -n, we print the full unabbreviated CIDR network prefix in
314 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
315 This change is in preparation for changes such as equal-cost
316 multipath, and to more generally assist operational deployment
317 of FreeBSD as a modern IPv4 router.
320 PIM has been turned on by default in the IPv4 multicast
321 routing code. The kernel option 'PIM' has now been removed.
322 PIM is now built by default if option 'MROUTING' is specified.
323 It may now be loaded into GENERIC kernels by loading the
327 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
328 has been removed. Its functionality may be achieved by explicitly
329 configuring gif(4) interfaces and using the 'phyint' keyword in
331 XORP does not support source-routed IPv4 multicast tunnels nor the
332 integrated IPIP tunneling, therefore it is not affected by this
333 change. The __FreeBSD_version macro has been bumped to 700030.
336 Support for PCI Message Signalled Interrupts has been
337 re-enabled in the bge driver, only for those chips which are
338 believed to support it properly. If there are any problems,
339 MSI can be disabled completely by setting the
340 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
344 Support for PCI Message Signalled Interrupts has been
345 disabled again in the bge driver. Many revisions of the
346 hardware fail to support it properly. Support can be
347 re-enabled by removing the #define of BGE_DISABLE_MSI in
348 "src/sys/dev/bge/if_bge.c".
351 Support for PCI Message Signalled Interrupts has been added
352 to the bge driver. If there are any problems, MSI can be
353 disabled completely by setting the 'hw.pci.enable_msi' and
354 'hw.pci.enable_msix' tunables to 0 in the loader.
357 The removal of several facets of the experimental Threading
358 system from the kernel means that the proc and thread structures
359 have changed quite a bit. I suggest all kernel modules that might
360 reference these structures be recompiled.. Especially the
364 Sound infrastructure has been updated with various fixes and
365 improvements. Most of the changes are pretty much transparent,
366 with exceptions of followings:
367 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
368 moved to their own dev sysctl nodes, for example:
369 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
370 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
371 own chardev in the form of "dsp%d.<function>%d", where <function>
372 is p = playback, r = record and v = virtual, respectively. Users
373 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
374 This does not affect those who are using "/dev/dsp".
377 The following binaries have been disconnected from the build:
378 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
379 and mount_std. The functionality of these programs has been
380 moved into the mount program. For example, to mount a devfs
381 filesystem, instead of using mount_devfs, use: "mount -t devfs".
382 This does not affect entries in /etc/fstab, since entries in
383 /etc/fstab are always processed with "mount -t fstype".
386 Support for PCI Message Signalled Interrupts on i386 and amd64
387 has been added to the kernel and various drivers will soon be
388 updated to use MSI when it is available. If there are any problems,
389 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
390 and 'hw.pci.enable_msix' tunables to 0 in the loader.
393 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
394 The lockmgr object layout has been changed as a result of having
395 a lock_object embedded in it. As a consequence all file system
396 kernel modules must be re-compiled. The mutex profiling man page
397 has not yet been updated to reflect this change.
400 KSE in the kernel has now been made optional and turned on by
401 default. Use 'nooption KSE' in your kernel config to turn it
402 off. All kernel modules *must* be recompiled after this change.
403 There-after, modules from a KSE kernel should be compatible with
404 modules from a NOKSE kernel due to the temporary padding fields
405 added to 'struct proc'.
408 mrouted and its utilities have been removed from the base system.
411 Some ioctl(2) command codes have changed. Full backward ABI
412 compatibility is provided if the "options COMPAT_FREEBSD6" is
413 present in the kernel configuration file. Make sure to add
414 this option to your kernel config file, or recompile X.Org
415 and the rest of ports; otherwise they may refuse to work.
418 tcpslice has been removed from the base system.
421 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
422 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
423 systat needs to be rebuilt.
426 libpcap updated to v0.9.4 and tcpdump to v3.9.4
429 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
430 for IPFIREWALL_FORWARD is now as it was before when it was first
431 committed and for years after. The behaviour is now ON.
434 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
435 Now it can decrypt files created from different architectures.
436 Unfortunately, it is no longer able to decrypt a cipher text
437 generated with an older version on 64 bit architectures.
438 If you have such a file, you need old utility to decrypt it.
441 The interface version of the i4b kernel part has changed. So
442 after updating the kernel sources and compiling a new kernel,
443 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
444 be rebuilt, and vice versa.
447 The XBOX kernel now defaults to the nfe(4) driver instead of
448 the nve(4) driver. Please update your configuration
452 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
453 PCnet family of NICs has been removed. The new le(4) driver serves
454 as an equivalent but cross-platform replacement with the pcn(4)
455 driver still providing performance-optimized support for the subset
456 of AMD Am79C971 PCnet-FAST and greater chips as before.
459 The machdep.* sysctls and the adjkerntz utility have been
460 modified a bit. The new adjkerntz utility uses the new
461 sysctl names and sysctlbyname() calls, so it may be impossible
462 to run an old /sbin/adjkerntz utility in single-user mode
463 with a new kernel. Replace the `adjkerntz -i' step before
464 `make installworld' with:
466 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
468 and proceed as usual with the rest of the installworld-stage
469 steps. Otherwise, you risk installing binaries with their
470 timestamp set several hours in the future, especially if
471 you are running with local time set to GMT+X hours.
474 The ip6fw utility has been removed. The behavior provided by
475 ip6fw has been in ipfw2 for a good while and the rc.d scripts
476 have been updated to deal with it. There are some rules that
477 might not migrate cleanly. Use rc.firewall6 as a template to
481 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
482 attachments have been removed. Make sure to configure scc(4)
483 on sparc64. Note also that by default puc(4) will use uart(4)
484 and not sio(4) for serial ports because interrupt handling has
485 been optimized for multi-port serial cards and only uart(4)
486 implements the interface to support it.
489 The scc(4) driver replaces puc(4) for Serial Communications
490 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
491 Z8530. On sparc64, it is advised to add scc(4) to the kernel
492 configuration to make sure that the serial ports remain
496 Most world/kernel related NO_* build options changed names.
497 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
498 after FreeBSD ports) and should be set in /etc/src.conf
499 (the src.conf(5) manpage is provided). Full backwards
500 compatibility is maintained for the time being though it's
501 highly recommended to start moving old options out of the
502 system-wide /etc/make.conf file into the new /etc/src.conf
503 while also properly renaming them. More conversions will
504 likely follow. Posting to current@:
506 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
509 The NETSMBCRYPTO kernel option has been retired because its
510 functionality is always included in NETSMB and smbfs.ko now.
513 The TDFX_LINUX kernel option was retired and replaced by the
514 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
515 kernel module. Loading it alone should suffice to get 3dfx support
516 for Linux apps because it will pull in 3dfx.ko and linux.ko through
520 The 'audit' group was added to support the new auditing functionality
521 in the base system. Be sure to follow the directions for updating,
522 including the requirement to run mergemaster -p.
525 The kernel ABI to file system modules was changed on i386.
526 Please make sure that your kernel and modules are in sync.
529 This actually occured some time ago, but installing the kernel
530 now also installs a bunch of symbol files for the kernel modules.
531 This increases the size of /boot/kernel to about 67Mbytes. You
532 will need twice this if you will eventually back this up to kernel.old
533 on your next install.
534 If you have a shortage of room in your root partition, you should add
535 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
536 to your /etc/make.conf.
539 libc's malloc implementation has been replaced. This change has the
540 potential to uncover application bugs that previously went unnoticed.
541 See the malloc(3) manual page for more details.
544 The generic netgraph(4) cookie has been changed. If you upgrade
545 kernel passing this point, you also need to upgrade userland
546 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
549 si(4)'s device files now contain the unit number.
550 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
553 The kernel ABI was mostly destroyed due to a change in the size
554 of struct lock_object which is nested in other structures such
555 as mutexes which are nested in all sorts of other structures.
556 Make sure your kernel and modules are in sync.
559 The page coloring algorithm in the VM subsystem was converted
560 from tuning with kernel options to autotuning. Please remove
561 any PQ_* option except PQ_NOOPT from your kernel config.
564 The net80211-related tools in the tools/tools/ath directory
565 have been moved to tools/tools/net80211 and renamed with a
566 "wlan" prefix. Scripts that use them should be adjusted
570 Scripts in the local_startup directories (as defined in
571 /etc/defaults/rc.conf) that have the new rc.d semantics will
572 now be run as part of the base system rcorder. If there are
573 errors or problems with one of these local scripts, it could
574 cause boot problems. If you encounter such problems, boot in
575 single user mode, remove that script from the */rc.d directory.
576 Please report the problem to the port's maintainer, and the
577 freebsd-ports@freebsd.org mailing list.
580 The nodev mount option was deprecated in RELENG_6 (where it
581 was a no-op), and is now unsupported. If you have nodev or dev listed
582 in /etc/fstab, remove it, otherwise it will result in a mount error.
585 ABI between ipfw(4) and ipfw(8) has been changed. You need
586 to rebuild ipfw(8) when rebuilding kernel.
589 rp(4)'s device files now contain the unit number.
590 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
593 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
594 Its /etc/rc.conf.d configuration file has been `ppp' from
595 the beginning, and hence there is no need to touch it.
598 Now most modules get their build-time options from the kernel
599 configuration file. A few modules still have fixed options
600 due to their non-conformant implementation, but they will be
601 corrected eventually. You may need to review the options of
602 the modules in use, explicitly specify the non-default options
603 in the kernel configuration file, and rebuild the kernel and
607 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
608 to turn polling(4) on your interfaces.
611 The old bridge(4) implementation was retired. The new
612 if_bridge(4) serves as a full functional replacement.
615 The ai_addrlen of a struct addrinfo was changed to a socklen_t
616 to conform to POSIX-2001. This change broke an ABI
617 compatibility on 64 bit architecture. You have to recompile
618 userland programs that use getaddrinfo(3) on 64 bit
622 RELENG_6 branched here.
625 The pccard_ifconfig rc.conf variable has been removed and a new
626 variable, ifconfig_DEFAULT has been introduced. Unlike
627 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
628 do not have ifconfig_ifn entries rather than just those in
629 removable_interfaces.
632 Some previous versions of PAM have permitted the use of
633 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
634 to third party PAM modules in /usr/local/lib. A change has been
635 made to require the use of absolute paths in order to avoid
636 ambiguity and dependence on library path configuration, which may
637 affect existing configurations.
640 Major changes to network interface API. All drivers must be
641 recompiled. Drivers not in the base system will need to be
642 updated to the new APIs.
645 Changes were made to kinfo_proc in sys/user.h. Please recompile
646 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
647 will not behave correctly.
649 The API and ABI for hwpmc(4) have changed with the addition
650 of sampling support. Please recompile lib/libpmc(3) and
651 usr.sbin/{pmcstat,pmccontrol}.
654 The OpenBSD dhclient was imported in place of the ISC dhclient
655 and the network interface configuration scripts were updated
656 accordingly. If you use DHCP to configure your interfaces, you
657 must now run devd. Also, DNS updating was lost so you will need
658 to find a workaround if you use this feature.
660 The '_dhcp' user was added to support the OpenBSD dhclient. Be
661 sure to run mergemaster -p (like you are supposed to do every time
665 if_bridge was added to the tree. This has changed struct ifnet.
666 Please recompile userland and all network related modules.
669 The n_net of a struct netent was changed to an uint32_t, and
670 1st argument of getnetbyaddr() was changed to an uint32_t, to
671 conform to POSIX-2001. These changes broke an ABI
672 compatibility on 64 bit architecture. With these changes,
673 shlib major of libpcap was bumped. You have to recompile
674 userland programs that use getnetbyaddr(3), getnetbyname(3),
675 getnetent(3) and/or libpcap on 64 bit architecture.
678 Kernel parsing of extra options on '#!' first lines of shell
679 scripts has changed. Lines with multiple options likely will
680 fail after this date. For full details, please see
681 http://people.freebsd.org/~gad/Updating-20050528.txt
684 The packet filter (pf) code has been updated to OpenBSD 3.7
685 Please note the changed anchor syntax and the fact that
686 authpf(8) now needs a mounted fdescfs(5) to function.
689 The NO_MIXED_MODE kernel option has been removed from the i386
690 amd64 platforms as its use has been superceded by the new local
691 APIC timer code. Any kernel config files containing this option
695 The on-disk format of LC_CTYPE files was changed to be machine
696 independent. Please make sure NOT to use NO_CLEAN buildworld
697 when crossing this point. Crossing this point also requires
698 recompile or reinstall of all locale depended packages.
701 The ifi_epoch member of struct if_data has been changed to
702 contain the uptime at which the interface was created or the
703 statistics zeroed rather then the wall clock time because
704 wallclock time may go backwards. This should have no impact
705 unless an snmp implementation is using this value (I know of
709 The acpi_perf and acpi_throttle drivers are now part of the
710 acpi(4) main module. They are no longer built separately.
713 The layout of struct image_params has changed. You have to
714 recompile all compatibility modules (linux, svr4, etc) for use
718 The p4tcc driver has been merged into cpufreq(4). This makes
719 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
720 compile in "device cpufreq" to restore this functionality.
723 The responsibility of recomputing the file system summary of
724 a SoftUpdates-enabled dirty volume has been transferred to the
725 background fsck. A rebuild of fsck(8) utility is recommended
726 if you have updated the kernel.
728 To get the old behavior (recompute file system summary at mount
729 time), you can set vfs.ffs.compute_summary_at_mount=1 before
730 mounting the new volume.
733 The cpufreq import is complete. As part of this, the sysctls for
734 acpi(4) throttling have been removed. The power_profile script
735 has been updated, so you can use performance/economy_cpu_freq in
736 rc.conf(5) to set AC on/offline cpu frequencies.
739 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
740 requires recompiling libnetgraph and userland netgraph utilities.
743 Support for abbreviated forms of a number of ipfw options is
744 now deprecated. Warnings are printed to stderr indicating the
745 correct full form when a match occurs. Some abbreviations may
746 be supported at a later date based on user feedback. To be
747 considered for support, abbreviations must be in use prior to
748 this commit and unlikely to be confused with current key words.
751 By a popular demand, a lot of NOFOO options were renamed
752 to NO_FOO (see bsd.compat.mk for a full list). The old
753 spellings are still supported, but will cause annoying
754 warnings on stderr. Make sure you upgrade properly (see
755 the COMMON ITEMS: section later in this file).
758 Auto-loading of ancillary wlan modules such as wlan_wep has
759 been temporarily disabled; you need to statically configure
760 the modules you need into your kernel or explicitly load them
761 prior to use. Specifically, if you intend to use WEP encryption
762 with an 802.11 device load/configure wlan_wep; if you want to
763 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
764 and wlan_xauth as required.
767 The behaviour of ppp(8) has changed slightly. If lqr is enabled
768 (``enable lqr''), older versions would revert to LCP ECHO mode on
769 negotiation failure. Now, ``enable echo'' is required for this
770 behaviour. The ppp version number has been bumped to 3.4.2 to
774 The wlan support has been updated to split the crypto support
775 into separate modules. For static WEP you must configure the
776 wlan_wep module in your system or build and install the module
777 in place where it can be loaded (the kernel will auto-load
778 the module when a wep key is configured).
781 The ath driver has been updated to split the tx rate control
782 algorithm into a separate module. You need to include either
783 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
786 Support for systems with an 80386 CPU has been removed. Please
787 use FreeBSD 5.x or earlier on systems with an 80386.
790 We have had a hack which would mount the root filesystem
791 R/W if the device were named 'md*'. As part of the vnode
792 work I'm doing I have had to remove this hack. People
793 building systems which use preloaded MD root filesystems
794 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
795 their /etc/rc scripts.
798 FreeBSD 5.3 shipped here.
801 The size of struct tcpcb has changed again due to the removal
802 of RFC1644 T/TCP. You have to recompile userland programs that
803 read kmem for tcp sockets directly (netstat, sockstat, etc.)
806 The size of struct tcpcb has changed. You have to recompile
807 userland programs that read kmem for tcp sockets directly
808 (netstat, sockstat, etc.)
811 RELENG_5 branched here. For older entries, please see updating
812 in the RELENG_5 branch.
818 Avoid using make -j when upgrading. From time to time in the
819 past there have been problems using -j with buildworld and/or
820 installworld. This is especially true when upgrading between
821 "distant" versions (eg one that cross a major release boundary
822 or several minor releases, or when several months have passed
823 on the -current branch).
825 Sometimes, obscure build problems are the result of environment
826 poisoning. This can happen because the make utility reads its
827 environment when searching for values for global variables.
828 To run your build attempts in an "environmental clean room",
829 prefix all make commands with 'env -i '. See the env(1) manual
830 page for more details.
832 When upgrading from one major version to another it is generally
833 best to upgrade to the latest code in the currently installed branch
834 first, then do an upgrade to the new branch. This is the best-tested
835 upgrade path, and has the highest probability of being successful.
836 Please try this approach before reporting problems with a major
841 If you are updating from a prior version of FreeBSD (even one just
842 a few days old), you should follow this procedure. It is the most
843 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
845 make kernel-toolchain
846 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
847 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
849 To test a kernel once
850 ---------------------
851 If you just want to boot a kernel once (because you are not sure
852 if it works, or if you want to boot a known bad kernel to provide
853 debugging information) run
854 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
855 nextboot -k testkernel
857 To just build a kernel when you know that it won't mess you up
858 --------------------------------------------------------------
859 This assumes you are already running a 5.X system. Replace
860 ${arch} with the architecture of your machine (e.g. "i386",
861 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
863 cd src/sys/${arch}/conf
864 config KERNEL_NAME_HERE
865 cd ../compile/KERNEL_NAME_HERE
870 If this fails, go to the "To build a kernel" section.
872 To rebuild everything and install it on the current system.
873 -----------------------------------------------------------
874 # Note: sometimes if you are running current you gotta do more than
875 # is listed here if you are upgrading from a really old current.
877 <make sure you have good level 0 dumps>
879 make kernel KERNCONF=YOUR_KERNEL_HERE
881 <reboot in single user> [3]
889 To cross-install current onto a separate partition
890 --------------------------------------------------
891 # In this approach we use a separate partition to hold
892 # current's root, 'usr', and 'var' directories. A partition
893 # holding "/", "/usr" and "/var" should be about 2GB in
896 <make sure you have good level 0 dumps>
899 make buildkernel KERNCONF=YOUR_KERNEL_HERE
900 <maybe newfs current's root partition>
901 <mount current's root partition on directory ${CURRENT_ROOT}>
902 make installworld DESTDIR=${CURRENT_ROOT}
903 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
904 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
905 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
906 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
907 <reboot into current>
908 <do a "native" rebuild/install as described in the previous section>
909 <maybe install compatibility libraries from src/lib/compat>
913 To upgrade in-place from 5.x-stable to current
914 ----------------------------------------------
915 <make sure you have good level 0 dumps>
917 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
919 <reboot in single user> [3]
926 Make sure that you've read the UPDATING file to understand the
927 tweaks to various things you need. At this point in the life
928 cycle of current, things change often and you are on your own
929 to cope. The defaults can also change, so please read ALL of
930 the UPDATING entries.
932 Also, if you are tracking -current, you must be subscribed to
933 freebsd-current@freebsd.org. Make sure that before you update
934 your sources that you have read and understood all the recent
935 messages there. If in doubt, please track -stable which has
938 [1] If you have third party modules, such as vmware, you
939 should disable them at this point so they don't crash your
942 [3] From the bootblocks, boot -s, and then do
947 adjkerntz -i # if CMOS is wall time
948 Also, when doing a major release upgrade, it is required that
949 you boot into single user mode to do the installworld.
951 [4] Note: This step is non-optional. Failure to do this step
952 can result in a significant reduction in the functionality of the
953 system. Attempting to do it by hand is not recommended and those
954 that pursue this avenue should read this file carefully, as well
955 as the archives of freebsd-current and freebsd-hackers mailing lists
956 for potential gotchas.
958 [5] Usually this step is a noop. However, from time to time
959 you may need to do this if you get unknown user in the following
960 step. It never hurts to do it all the time. You may need to
961 install a new mergemaster (cd src/usr.sbin/mergemaster && make
962 install) after the buildworld before this step if you last updated
963 from current before 20020224 or from -stable before 20020408.
965 [8] In order to have a kernel that can run the 4.x binaries
966 needed to do an installworld, you must include the COMPAT_FREEBSD4
967 option in your kernel. Failure to do so may leave you with a system
968 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
969 is required to run the 5.x binaries on more recent kernels.
971 Make sure that you merge any new devices from GENERIC since the
972 last time you updated your kernel config file.
974 [9] When checking out sources, you must include the -P flag to have
975 cvs prune empty directories.
977 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
978 "?=" instead of the "=" assignment operator, so that buildworld can
979 override the CPUTYPE if it needs to.
981 MAKEOBJDIRPREFIX must be defined in an environment variable, and
982 not on the command line, or in /etc/make.conf. buildworld will
983 warn if it is improperly defined.
986 This file contains a list, in reverse chronological order, of major
987 breakages in tracking -current. Not all things will be listed here,
988 and it only starts on October 16, 2004. Updating files can found in
989 previous releases if your system is older than this.
991 Copyright information:
993 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
995 Redistribution, publication, translation and use, with or without
996 modification, in full or in part, in any form or format of this
997 document are permitted without further permission from the author.
999 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1000 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1001 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1002 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1003 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1004 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1005 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1006 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1007 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1008 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1009 POSSIBILITY OF SUCH DAMAGE.
1011 If you find this document useful, and you want to, you may buy the
1014 Contact Warner Losh if you have any questions about your use of