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