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.
25 The misnamed kthread_create() and friends have been renamed
26 to kproc_create() etc. Many of the callers already
28 I will return kthread_create() and friends in a while
29 with implementations that actually create threads, not procs.
30 Renaming corresponds with version 800002.
36 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
37 WITHOUT_LIBTHR are set.
40 The PCI code has been made aware of PCI domains. This means that
41 the location strings as used by pciconf(8) etc are now in the
42 following format: pci<domain>:<bus>:<device>[:<function>]. It
43 also means that consumers of <sys/pciio.h> potentially need to
44 be recompiled; this includes the hal and xorg-server ports.
47 The caching daemon (cached) was renamed to nscd. nscd.conf
48 configuration file should be used instead of cached.conf and
49 nscd_enable, nscd_pidfile and nscd_flags options should be used
50 instead of cached_enable, cached_pidfile and cached_flags in
54 The getfacl(1) utility now prints owning user and group name
55 instead of owning uid and gid in the three line comment header.
56 This is the same behavior as getfacl(1) on Solaris and Linux.
59 The new IPsec code is now compiled in using the IPSEC option. The
60 IPSEC option now requires "device crypto" be defined in your kernel
61 configuration. The FAST_IPSEC kernel option is now deprecated.
64 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
65 note the changed syntax - keep state is now on by default. Also
66 note the fact that ftp-proxy(8) has been changed from bottom up and
67 has been moved from libexec to usr/sbin. Changes in the ALTQ
68 handling also affect users of IPFW's ALTQ capabilities.
71 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
72 only IPsec supported by FreeBSD. The new IPsec stack
73 supports both IPv4 and IPv6. The kernel option will change
74 after the code changes have settled in. For now the kernel
75 option IPSEC is deprecated and FAST_IPSEC is the only option, that
76 will change after some settling time.
79 The wicontrol(8) utility has been removed from the base system. wi(4)
80 cards should be configured using ifconfig(8), see the man page for more
84 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
85 instead of the nve(4) driver. Please update your configuration
89 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
90 database if it is missing or older than the aliases file. If
91 desired, set the new rc.conf option sendmail_rebuild_aliases
92 to "YES" to restore that functionality.
95 The IPv4 multicast socket code has been considerably modified, and
96 moved to the file sys/netinet/in_mcast.c. Initial support for the
97 RFC 3678 Source-Specific Multicast Socket API has been added to
98 the IPv4 network stack.
100 Strict multicast and broadcast reception is now the default for
101 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
102 has now been removed.
104 The RFC 1724 hack for interface selection has been removed; the use
105 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
106 been added to replace it. Consumers such as routed will soon be
107 updated to reflect this.
109 These changes affect users who are running routed(8) or rdisc(8)
110 from the FreeBSD base system on point-to-point or unnumbered
114 The net80211 layer has changed significantly and all wireless
115 drivers that depend on it need to be recompiled. Further these
116 changes require that any program that interacts with the wireless
117 support in the kernel be recompiled; this includes: ifconfig,
118 wpa_supplicant, hostapd, and wlanstats. Users must also, for
119 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
120 if they use modules for wireless support. These modules implement
121 scanning support for station and ap modes, respectively. Failure
122 to load the appropriate module before marking a wireless interface
123 up will result in a message to the console and the device not
127 The pam_nologin(8) module ceases to provide an authentication
128 function and starts providing an account management function.
129 Consequent changes to /etc/pam.d should be brought in using
130 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
131 need manual editing as follows. Locate this line (or similar):
133 auth required pam_nologin.so no_warn
135 and change it according to this example:
137 account required pam_nologin.so no_warn
139 That is, the first word needs to be changed from "auth" to
140 "account". The new line can be moved to the account section
141 within the file for clarity. Not updating pam.conf(5) files
142 will result in nologin(5) ignored by the respective services.
145 The ether_ioctl() function has been synchronized with ioctl(2)
146 and ifnet.if_ioctl. Due to that, the size of one of its arguments
147 has changed on 64-bit architectures. All kernel modules using
148 ether_ioctl() need to be rebuilt on such architectures.
151 Improved INCLUDE_CONFIG_FILE support has been introduced to the
152 config(8) utility. In order to take advantage of this new
153 functionality, you are expected to recompile and install
154 src/usr.sbin/config. If you don't rebuild config(8), and your
155 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
156 build will be broken because of a missing "kernconfstring"
160 Symbol versioning is enabled by default. To disable it, use
161 option WITHOUT_SYMVER. It is not advisable to attempt to
162 disable symbol versioning once it is enabled; your installworld
163 will break because a symbol version-less libc will get installed
164 before the install tools. As a result, the old install tools,
165 which previously had symbol dependencies to FBSD_1.0, will fail
166 because the freshly installed libc will not have them.
168 The default threading library (providing "libpthread") has been
169 changed to libthr. If you wish to have libkse as your default,
170 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
173 The ABI breakage in sendmail(8)'s libmilter has been repaired
174 so it is no longer necessary to recompile mail filters (aka,
175 milters). If you recompiled mail filters after the 20070408
176 note, it is not necessary to recompile them again.
179 The new trunk(4) driver has been renamed to lagg(4) as it better
180 reflects its purpose. ifconfig will need to be recompiled.
183 sendmail(8) has been updated to version 8.14.1. Mail filters
184 (aka, milters) compiled against the libmilter included in the
185 base operating system should be recompiled.
188 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
189 In order to use them one must agree to the respective LICENSE in
190 share/doc/legal and define legal.intel_<name>.license_ack=1 via
191 loader.conf(5) or kenv(1). Make sure to deinstall the now
192 deprecated modules from the respective firmware ports.
195 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
196 were removed from FreeBSD's libc. These originally came from INRIA
197 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
198 deprecated in previous releases.
199 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
200 replace it as a more portable (and re-entrant) API.
203 To support interrupt filtering a modification to the newbus API
204 has occurred, ABI was broken and __FreeBSD_version was bumped
205 to 700031. Please make sure that your kernel and modules are in
207 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
210 The IPv6 multicast forwarding code may now be loaded into GENERIC
211 kernels by loading the ip_mroute.ko module. This is built into the
212 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
213 set; see src.conf(5) for more information.
216 The output of netstat -r has changed. Without -n, we now only
217 print a "network name" without the prefix length if the network
218 address and mask exactly match a Class A/B/C network, and an entry
219 exists in the nsswitch "networks" map.
220 With -n, we print the full unabbreviated CIDR network prefix in
221 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
222 This change is in preparation for changes such as equal-cost
223 multipath, and to more generally assist operational deployment
224 of FreeBSD as a modern IPv4 router.
227 PIM has been turned on by default in the IPv4 multicast
228 routing code. The kernel option 'PIM' has now been removed.
229 PIM is now built by default if option 'MROUTING' is specified.
230 It may now be loaded into GENERIC kernels by loading the
234 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
235 has been removed. Its functionality may be achieved by explicitly
236 configuring gif(4) interfaces and using the 'phyint' keyword in
238 XORP does not support source-routed IPv4 multicast tunnels nor the
239 integrated IPIP tunneling, therefore it is not affected by this
240 change. The __FreeBSD_version macro has been bumped to 700030.
243 Support for PCI Message Signalled Interrupts has been
244 re-enabled in the bge driver, only for those chips which are
245 believed to support it properly. If there are any problems,
246 MSI can be disabled completely by setting the
247 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
251 Support for PCI Message Signalled Interrupts has been
252 disabled again in the bge driver. Many revisions of the
253 hardware fail to support it properly. Support can be
254 re-enabled by removing the #define of BGE_DISABLE_MSI in
255 "src/sys/dev/bge/if_bge.c".
258 Support for PCI Message Signalled Interrupts has been added
259 to the bge driver. If there are any problems, MSI can be
260 disabled completely by setting the 'hw.pci.enable_msi' and
261 'hw.pci.enable_msix' tunables to 0 in the loader.
264 The removal of several facets of the experimental Threading
265 system from the kernel means that the proc and thread structures
266 have changed quite a bit. I suggest all kernel modules that might
267 reference these structures be recompiled.. Especially the
271 Sound infrastructure has been updated with various fixes and
272 improvements. Most of the changes are pretty much transparent,
273 with exceptions of followings:
274 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
275 moved to their own dev sysctl nodes, for example:
276 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
277 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
278 own chardev in the form of "dsp%d.<function>%d", where <function>
279 is p = playback, r = record and v = virtual, respectively. Users
280 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
281 This does not affect those who are using "/dev/dsp".
284 The following binaries have been disconnected from the build:
285 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
286 and mount_std. The functionality of these programs has been
287 moved into the mount program. For example, to mount a devfs
288 filesystem, instead of using mount_devfs, use: "mount -t devfs".
289 This does not affect entries in /etc/fstab, since entries in
290 /etc/fstab are always processed with "mount -t fstype".
293 Support for PCI Message Signalled Interrupts on i386 and amd64
294 has been added to the kernel and various drivers will soon be
295 updated to use MSI when it is available. If there are any problems,
296 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
297 and 'hw.pci.enable_msix' tunables to 0 in the loader.
300 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
301 The lockmgr object layout has been changed as a result of having
302 a lock_object embedded in it. As a consequence all file system
303 kernel modules must be re-compiled. The mutex profiling man page
304 has not yet been updated to reflect this change.
307 KSE in the kernel has now been made optional and turned on by
308 default. Use 'nooption KSE' in your kernel config to turn it
309 off. All kernel modules *must* be recompiled after this change.
310 There-after, modules from a KSE kernel should be compatible with
311 modules from a NOKSE kernel due to the temporary padding fields
312 added to 'struct proc'.
315 mrouted and its utilities have been removed from the base system.
318 Some ioctl(2) command codes have changed. Full backward ABI
319 compatibility is provided if the "options COMPAT_FREEBSD6" is
320 present in the kernel configuration file. Make sure to add
321 this option to your kernel config file, or recompile X.Org
322 and the rest of ports; otherwise they may refuse to work.
325 tcpslice has been removed from the base system.
328 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
329 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
330 systat needs to be rebuilt.
333 libpcap updated to v0.9.4 and tcpdump to v3.9.4
336 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
337 for IPFIREWALL_FORWARD is now as it was before when it was first
338 committed and for years after. The behaviour is now ON.
341 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
342 Now it can decrypt files created from different architectures.
343 Unfortunately, it is no longer able to decrypt a cipher text
344 generated with an older version on 64 bit architectures.
345 If you have such a file, you need old utility to decrypt it.
348 The interface version of the i4b kernel part has changed. So
349 after updating the kernel sources and compiling a new kernel,
350 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
351 be rebuilt, and vice versa.
354 The XBOX kernel now defaults to the nfe(4) driver instead of
355 the nve(4) driver. Please update your configuration
359 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
360 PCnet family of NICs has been removed. The new le(4) driver serves
361 as an equivalent but cross-platform replacement with the pcn(4)
362 driver still providing performance-optimized support for the subset
363 of AMD Am79C971 PCnet-FAST and greater chips as before.
366 The machdep.* sysctls and the adjkerntz utility have been
367 modified a bit. The new adjkerntz utility uses the new
368 sysctl names and sysctlbyname() calls, so it may be impossible
369 to run an old /sbin/adjkerntz utility in single-user mode
370 with a new kernel. Replace the `adjkerntz -i' step before
371 `make installworld' with:
373 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
375 and proceed as usual with the rest of the installworld-stage
376 steps. Otherwise, you risk installing binaries with their
377 timestamp set several hours in the future, especially if
378 you are running with local time set to GMT+X hours.
381 The ip6fw utility has been removed. The behavior provided by
382 ip6fw has been in ipfw2 for a good while and the rc.d scripts
383 have been updated to deal with it. There are some rules that
384 might not migrate cleanly. Use rc.firewall6 as a template to
388 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
389 attachments have been removed. Make sure to configure scc(4)
390 on sparc64. Note also that by default puc(4) will use uart(4)
391 and not sio(4) for serial ports because interrupt handling has
392 been optimized for multi-port serial cards and only uart(4)
393 implements the interface to support it.
396 The scc(4) driver replaces puc(4) for Serial Communications
397 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
398 Z8530. On sparc64, it is advised to add scc(4) to the kernel
399 configuration to make sure that the serial ports remain
403 Most world/kernel related NO_* build options changed names.
404 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
405 after FreeBSD ports) and should be set in /etc/src.conf
406 (the src.conf(5) manpage is provided). Full backwards
407 compatibility is maintained for the time being though it's
408 highly recommended to start moving old options out of the
409 system-wide /etc/make.conf file into the new /etc/src.conf
410 while also properly renaming them. More conversions will
411 likely follow. Posting to current@:
413 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
416 The NETSMBCRYPTO kernel option has been retired because its
417 functionality is always included in NETSMB and smbfs.ko now.
420 The TDFX_LINUX kernel option was retired and replaced by the
421 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
422 kernel module. Loading it alone should suffice to get 3dfx support
423 for Linux apps because it will pull in 3dfx.ko and linux.ko through
427 The 'audit' group was added to support the new auditing functionality
428 in the base system. Be sure to follow the directions for updating,
429 including the requirement to run mergemaster -p.
432 The kernel ABI to file system modules was changed on i386.
433 Please make sure that your kernel and modules are in sync.
436 This actually occured some time ago, but installing the kernel
437 now also installs a bunch of symbol files for the kernel modules.
438 This increases the size of /boot/kernel to about 67Mbytes. You
439 will need twice this if you will eventually back this up to kernel.old
440 on your next install.
441 If you have a shortage of room in your root partition, you should add
442 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
443 to your /etc/make.conf.
446 libc's malloc implementation has been replaced. This change has the
447 potential to uncover application bugs that previously went unnoticed.
448 See the malloc(3) manual page for more details.
451 The generic netgraph(4) cookie has been changed. If you upgrade
452 kernel passing this point, you also need to upgrade userland
453 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
456 si(4)'s device files now contain the unit number.
457 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
460 The kernel ABI was mostly destroyed due to a change in the size
461 of struct lock_object which is nested in other structures such
462 as mutexes which are nested in all sorts of other structures.
463 Make sure your kernel and modules are in sync.
466 The page coloring algorithm in the VM subsystem was converted
467 from tuning with kernel options to autotuning. Please remove
468 any PQ_* option except PQ_NOOPT from your kernel config.
471 The net80211-related tools in the tools/tools/ath directory
472 have been moved to tools/tools/net80211 and renamed with a
473 "wlan" prefix. Scripts that use them should be adjusted
477 Scripts in the local_startup directories (as defined in
478 /etc/defaults/rc.conf) that have the new rc.d semantics will
479 now be run as part of the base system rcorder. If there are
480 errors or problems with one of these local scripts, it could
481 cause boot problems. If you encounter such problems, boot in
482 single user mode, remove that script from the */rc.d directory.
483 Please report the problem to the port's maintainer, and the
484 freebsd-ports@freebsd.org mailing list.
487 The nodev mount option was deprecated in RELENG_6 (where it
488 was a no-op), and is now unsupported. If you have nodev or dev listed
489 in /etc/fstab, remove it, otherwise it will result in a mount error.
492 ABI between ipfw(4) and ipfw(8) has been changed. You need
493 to rebuild ipfw(8) when rebuilding kernel.
496 rp(4)'s device files now contain the unit number.
497 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
500 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
501 Its /etc/rc.conf.d configuration file has been `ppp' from
502 the beginning, and hence there is no need to touch it.
505 Now most modules get their build-time options from the kernel
506 configuration file. A few modules still have fixed options
507 due to their non-conformant implementation, but they will be
508 corrected eventually. You may need to review the options of
509 the modules in use, explicitly specify the non-default options
510 in the kernel configuration file, and rebuild the kernel and
514 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
515 to turn polling(4) on your interfaces.
518 The old bridge(4) implementation was retired. The new
519 if_bridge(4) serves as a full functional replacement.
522 The ai_addrlen of a struct addrinfo was changed to a socklen_t
523 to conform to POSIX-2001. This change broke an ABI
524 compatibility on 64 bit architecture. You have to recompile
525 userland programs that use getaddrinfo(3) on 64 bit
529 RELENG_6 branched here.
532 The pccard_ifconfig rc.conf variable has been removed and a new
533 variable, ifconfig_DEFAULT has been introduced. Unlike
534 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
535 do not have ifconfig_ifn entries rather than just those in
536 removable_interfaces.
539 Some previous versions of PAM have permitted the use of
540 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
541 to third party PAM modules in /usr/local/lib. A change has been
542 made to require the use of absolute paths in order to avoid
543 ambiguity and dependence on library path configuration, which may
544 affect existing configurations.
547 Major changes to network interface API. All drivers must be
548 recompiled. Drivers not in the base system will need to be
549 updated to the new APIs.
552 Changes were made to kinfo_proc in sys/user.h. Please recompile
553 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
554 will not behave correctly.
556 The API and ABI for hwpmc(4) have changed with the addition
557 of sampling support. Please recompile lib/libpmc(3) and
558 usr.sbin/{pmcstat,pmccontrol}.
561 The OpenBSD dhclient was imported in place of the ISC dhclient
562 and the network interface configuration scripts were updated
563 accordingly. If you use DHCP to configure your interfaces, you
564 must now run devd. Also, DNS updating was lost so you will need
565 to find a workaround if you use this feature.
567 The '_dhcp' user was added to support the OpenBSD dhclient. Be
568 sure to run mergemaster -p (like you are supposed to do every time
572 if_bridge was added to the tree. This has changed struct ifnet.
573 Please recompile userland and all network related modules.
576 The n_net of a struct netent was changed to an uint32_t, and
577 1st argument of getnetbyaddr() was changed to an uint32_t, to
578 conform to POSIX-2001. These changes broke an ABI
579 compatibility on 64 bit architecture. With these changes,
580 shlib major of libpcap was bumped. You have to recompile
581 userland programs that use getnetbyaddr(3), getnetbyname(3),
582 getnetent(3) and/or libpcap on 64 bit architecture.
585 Kernel parsing of extra options on '#!' first lines of shell
586 scripts has changed. Lines with multiple options likely will
587 fail after this date. For full details, please see
588 http://people.freebsd.org/~gad/Updating-20050528.txt
591 The packet filter (pf) code has been updated to OpenBSD 3.7
592 Please note the changed anchor syntax and the fact that
593 authpf(8) now needs a mounted fdescfs(5) to function.
596 The NO_MIXED_MODE kernel option has been removed from the i386
597 amd64 platforms as its use has been superceded by the new local
598 APIC timer code. Any kernel config files containing this option
602 The on-disk format of LC_CTYPE files was changed to be machine
603 independent. Please make sure NOT to use NO_CLEAN buildworld
604 when crossing this point. Crossing this point also requires
605 recompile or reinstall of all locale depended packages.
608 The ifi_epoch member of struct if_data has been changed to
609 contain the uptime at which the interface was created or the
610 statistics zeroed rather then the wall clock time because
611 wallclock time may go backwards. This should have no impact
612 unless an snmp implementation is using this value (I know of
616 The acpi_perf and acpi_throttle drivers are now part of the
617 acpi(4) main module. They are no longer built separately.
620 The layout of struct image_params has changed. You have to
621 recompile all compatibility modules (linux, svr4, etc) for use
625 The p4tcc driver has been merged into cpufreq(4). This makes
626 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
627 compile in "device cpufreq" to restore this functionality.
630 The responsibility of recomputing the file system summary of
631 a SoftUpdates-enabled dirty volume has been transferred to the
632 background fsck. A rebuild of fsck(8) utility is recommended
633 if you have updated the kernel.
635 To get the old behavior (recompute file system summary at mount
636 time), you can set vfs.ffs.compute_summary_at_mount=1 before
637 mounting the new volume.
640 The cpufreq import is complete. As part of this, the sysctls for
641 acpi(4) throttling have been removed. The power_profile script
642 has been updated, so you can use performance/economy_cpu_freq in
643 rc.conf(5) to set AC on/offline cpu frequencies.
646 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
647 requires recompiling libnetgraph and userland netgraph utilities.
650 Support for abbreviated forms of a number of ipfw options is
651 now deprecated. Warnings are printed to stderr indicating the
652 correct full form when a match occurs. Some abbreviations may
653 be supported at a later date based on user feedback. To be
654 considered for support, abbreviations must be in use prior to
655 this commit and unlikely to be confused with current key words.
658 By a popular demand, a lot of NOFOO options were renamed
659 to NO_FOO (see bsd.compat.mk for a full list). The old
660 spellings are still supported, but will cause annoying
661 warnings on stderr. Make sure you upgrade properly (see
662 the COMMON ITEMS: section later in this file).
665 Auto-loading of ancillary wlan modules such as wlan_wep has
666 been temporarily disabled; you need to statically configure
667 the modules you need into your kernel or explicitly load them
668 prior to use. Specifically, if you intend to use WEP encryption
669 with an 802.11 device load/configure wlan_wep; if you want to
670 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
671 and wlan_xauth as required.
674 The behaviour of ppp(8) has changed slightly. If lqr is enabled
675 (``enable lqr''), older versions would revert to LCP ECHO mode on
676 negotiation failure. Now, ``enable echo'' is required for this
677 behaviour. The ppp version number has been bumped to 3.4.2 to
681 The wlan support has been updated to split the crypto support
682 into separate modules. For static WEP you must configure the
683 wlan_wep module in your system or build and install the module
684 in place where it can be loaded (the kernel will auto-load
685 the module when a wep key is configured).
688 The ath driver has been updated to split the tx rate control
689 algorithm into a separate module. You need to include either
690 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
693 Support for systems with an 80386 CPU has been removed. Please
694 use FreeBSD 5.x or earlier on systems with an 80386.
697 We have had a hack which would mount the root filesystem
698 R/W if the device were named 'md*'. As part of the vnode
699 work I'm doing I have had to remove this hack. People
700 building systems which use preloaded MD root filesystems
701 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
702 their /etc/rc scripts.
705 FreeBSD 5.3 shipped here.
708 The size of struct tcpcb has changed again due to the removal
709 of RFC1644 T/TCP. You have to recompile userland programs that
710 read kmem for tcp sockets directly (netstat, sockstat, etc.)
713 The size of struct tcpcb has changed. You have to recompile
714 userland programs that read kmem for tcp sockets directly
715 (netstat, sockstat, etc.)
718 RELENG_5 branched here. For older entries, please see updating
719 in the RELENG_5 branch.
725 Avoid using make -j when upgrading. From time to time in the
726 past there have been problems using -j with buildworld and/or
727 installworld. This is especially true when upgrading between
728 "distant" versions (eg one that cross a major release boundary
729 or several minor releases, or when several months have passed
730 on the -current branch).
732 Sometimes, obscure build problems are the result of environment
733 poisoning. This can happen because the make utility reads its
734 environment when searching for values for global variables.
735 To run your build attempts in an "environmental clean room",
736 prefix all make commands with 'env -i '. See the env(1) manual
737 page for more details.
739 When upgrading from one major version to another it is generally
740 best to upgrade to the latest code in the currently installed branch
741 first, then do an upgrade to the new branch. This is the best-tested
742 upgrade path, and has the highest probability of being successful.
743 Please try this approach before reporting problems with a major
748 If you are updating from a prior version of FreeBSD (even one just
749 a few days old), you should follow this procedure. It is the most
750 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
752 make kernel-toolchain
753 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
754 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
756 To test a kernel once
757 ---------------------
758 If you just want to boot a kernel once (because you are not sure
759 if it works, or if you want to boot a known bad kernel to provide
760 debugging information) run
761 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
762 nextboot -k testkernel
764 To just build a kernel when you know that it won't mess you up
765 --------------------------------------------------------------
766 This assumes you are already running a 5.X system. Replace
767 ${arch} with the architecture of your machine (e.g. "i386",
768 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
770 cd src/sys/${arch}/conf
771 config KERNEL_NAME_HERE
772 cd ../compile/KERNEL_NAME_HERE
777 If this fails, go to the "To build a kernel" section.
779 To rebuild everything and install it on the current system.
780 -----------------------------------------------------------
781 # Note: sometimes if you are running current you gotta do more than
782 # is listed here if you are upgrading from a really old current.
784 <make sure you have good level 0 dumps>
786 make kernel KERNCONF=YOUR_KERNEL_HERE
788 <reboot in single user> [3]
796 To cross-install current onto a separate partition
797 --------------------------------------------------
798 # In this approach we use a separate partition to hold
799 # current's root, 'usr', and 'var' directories. A partition
800 # holding "/", "/usr" and "/var" should be about 2GB in
803 <make sure you have good level 0 dumps>
806 make buildkernel KERNCONF=YOUR_KERNEL_HERE
807 <maybe newfs current's root partition>
808 <mount current's root partition on directory ${CURRENT_ROOT}>
809 make installworld DESTDIR=${CURRENT_ROOT}
810 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
811 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
812 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
813 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
814 <reboot into current>
815 <do a "native" rebuild/install as described in the previous section>
816 <maybe install compatibility libraries from src/lib/compat>
820 To upgrade in-place from 5.x-stable to current
821 ----------------------------------------------
822 <make sure you have good level 0 dumps>
824 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
826 <reboot in single user> [3]
833 Make sure that you've read the UPDATING file to understand the
834 tweaks to various things you need. At this point in the life
835 cycle of current, things change often and you are on your own
836 to cope. The defaults can also change, so please read ALL of
837 the UPDATING entries.
839 Also, if you are tracking -current, you must be subscribed to
840 freebsd-current@freebsd.org. Make sure that before you update
841 your sources that you have read and understood all the recent
842 messages there. If in doubt, please track -stable which has
845 [1] If you have third party modules, such as vmware, you
846 should disable them at this point so they don't crash your
849 [3] From the bootblocks, boot -s, and then do
854 adjkerntz -i # if CMOS is wall time
855 Also, when doing a major release upgrade, it is required that
856 you boot into single user mode to do the installworld.
858 [4] Note: This step is non-optional. Failure to do this step
859 can result in a significant reduction in the functionality of the
860 system. Attempting to do it by hand is not recommended and those
861 that pursue this avenue should read this file carefully, as well
862 as the archives of freebsd-current and freebsd-hackers mailing lists
863 for potential gotchas.
865 [5] Usually this step is a noop. However, from time to time
866 you may need to do this if you get unknown user in the following
867 step. It never hurts to do it all the time. You may need to
868 install a new mergemaster (cd src/usr.sbin/mergemaster && make
869 install) after the buildworld before this step if you last updated
870 from current before 20020224 or from -stable before 20020408.
872 [8] In order to have a kernel that can run the 4.x binaries
873 needed to do an installworld, you must include the COMPAT_FREEBSD4
874 option in your kernel. Failure to do so may leave you with a system
875 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
876 is required to run the 5.x binaries on more recent kernels.
878 Make sure that you merge any new devices from GENERIC since the
879 last time you updated your kernel config file.
881 [9] When checking out sources, you must include the -P flag to have
882 cvs prune empty directories.
884 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
885 "?=" instead of the "=" assignment operator, so that buildworld can
886 override the CPUTYPE if it needs to.
888 MAKEOBJDIRPREFIX must be defined in an environment variable, and
889 not on the command line, or in /etc/make.conf. buildworld will
890 warn if it is improperly defined.
893 This file contains a list, in reverse chronological order, of major
894 breakages in tracking -current. Not all things will be listed here,
895 and it only starts on October 16, 2004. Updating files can found in
896 previous releases if your system is older than this.
898 Copyright information:
900 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
902 Redistribution, publication, translation and use, with or without
903 modification, in full or in part, in any form or format of this
904 document are permitted without further permission from the author.
906 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
907 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
908 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
909 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
910 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
911 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
912 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
913 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
914 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
915 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
916 POSSIBILITY OF SUCH DAMAGE.
918 If you find this document useful, and you want to, you may buy the
921 Contact Warner Losh if you have any questions about your use of