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