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