1 Updating Information for FreeBSD STABLE 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 20090610: p1 FreeBSD-SA-09:09.pipe, FreeBSD-SA-09:10.ipv6,
13 Prevent integer overflow in direct pipe write code from circumventing
14 virtual-to-physical page lookups. [09:09]
16 Add missing permissions check for SIOCSIFINFO_IN6 ioctl. [09:10]
18 Fix buffer overflow in "autokey" negotiation in ntpd(8). [09:11]
23 20090422: FreeBSD-SA-09:07.libc, FreeBSD-SA-09:08.openssl
24 Don't leak information via uninitialized space in db(3) records.
27 Sanity-check string lengths in order to stop OpenSSL crashing
28 when printing corrupt BMPString or UniversalString objects. [09:08]
31 Following bug-fixes to TCP connection state flags, netstat, systat,
32 and sockstat will need to be rebuilt in order to properly print
33 connections in the TIMEWAIT state.
36 Change IPv6 ephemeral port allocation from sequential to
37 random allocation, like IPv4 has done for more than four years.
38 The implementation shares infrastructure with IPv4. This
39 means that there is only one set of sysctls to control both
40 IPv4 and IPv6. See ip(4) man page for details.
43 A workaround is committed to allow the creation of System V shared
44 memory segment of size > 2 GB on the 64-bit architectures.
45 Due to a limitation of the existing ABI, the shm_segsz member
46 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
47 wrong for large segments. Note that limits must be explicitely
48 raised to allow such segments to be created.
50 The management interface that is used by ipcs(1) has to be changed
51 in incompatible way. Rebuild the ipcs(1) utility with the new
52 headers after the update. Buildworld/installworld takes care
53 of this issue automatically.
56 The open-source Atheros HAL has been merged from HEAD
58 The kernel compile-time option AH_SUPPORT_AR5416 has been
59 added to support certain newer Atheros parts, particularly
61 The following modules are no longer available, and should be
62 removed from MODULES_OVERRIDE and/or loader.conf:-
63 ath_hal ath_rate_amrr ath_rate_onoe ath_rate_sample
66 ZFS users on amd64 machines with 4GB or more of RAM should
67 reevaluate their need for setting vm.kmem_size_max and
68 vm.kmem_size manually. In fact, after recent changes to the
69 kernel, the default value of vm.kmem_size is larger than the
70 suggested manual setting in most ZFS/FreeBSD tuning guides.
73 Multi-IPv4/v6/no-IP jail support was merged to STABLE.
74 You need to rebuild jls(8) and to use the new features
75 jail(8), jexec(8) and cpuset(1) with a new kernel.
76 __FreeBSD_version was bumped to 701103.
79 NTFS has been removed from GENERIC kernel on amd64 to match
80 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
81 will load ntfs.ko module automatically when NTFS support is
82 actually needed, unless ntfs.ko is not installed or security
83 level prohibits loading kernel modules. If either is the case,
84 "options NTFS" has to be added into kernel config.
87 powerd(8) was updated to get better SMP support.
88 Meanings of the -i and -r command line options were changed.
91 snd_hda(4) driver was updated to version 20081226_0122.
93 Due to added HDMI audio and logical audio devices support, updated
94 driver often provides several PCM devices. In some cases it can make
95 system default audio device no longer correspond to the users's
96 habbitual audio connectors. In such cases wanted device can be
97 specified in audio application setup or defined globally via
98 hw.snd.default_unit sysctl according to sound(4) and snd_hda(4)
105 ntpd has been upgraded to 4.2.4p5.
108 OpenSSH has been upgraded to 5.1p1.
111 DTrace support was merged to STABLE today. In the best
112 tradition of "the dog ate my homework", subversion decided
113 that the commit message was too large and opted not to send
114 it. It was a stealth commit!
116 A 'make buildkernel' will now default to build the kernel
117 and modules with both DTrace kernel hooks and CTF data ready
120 After you have installed both world and the kernel, and
121 rebooted, you can 'kldload dtraceall' to load all the DTrace
122 kernel modules and then you're set to run the 'dtrace'
125 For DTrace documentation, refer to:
126 <http://wikis.sun.com/display/DTrace/Documentation>
128 We are limited to kernel tracing at the moment, so the pid
129 provider is not available.
131 For the syscall provider, note that the arguments to the
132 return probes are the same as for the entry probes.
135 Today STABLE got a reorganization of the Intel E1000
136 driver code. In order to better support our new adapters
137 there is a new driver, igb, that is now to be used for
138 either the 82575 or 82576 adapters. The source however,
139 is all now in sys/dev/e1000, both em and igb drivers are
140 built from that common directory if you configure them
141 in the kernel. Making loadable drivers still happens in
142 the same place: sys/modules/[em, igb].
144 The important thing to note is that the 82575 adapters
145 were supported in the em driver in 7.0, but now needed
146 to be moved into igb, so if you have the effected cards
147 be sure and make any script changes to follow the name
150 There are only 3 PCI ID's effected in this change:
151 0x10A7, 0x10A9, and 0x10D6
152 So you can know ahead of time if they will be effected,
153 these will now be supported in the igb driver. That
154 driver will also support the new 82576 followon.
156 The driver reorg in STABLE is inconvenient but it really
157 was necessary for Intel to do this, and I figured it was
158 better to have this small admin type issue than not to
159 have support for this new hardware for a whole release
163 I have MFC'd in code to support multiple routing tables.
164 see the man pages setfib(1) and setfib(2).
165 This is a backwards compatible version,
166 but to make use of it you need to compile your kernel
167 with options ROUTETABLES=2 (or more up to 16).
173 Note the addition of m_collapse for compacting mbuf chains.
176 The AT keyboard emulation of sunkbd(4) has been turned on
177 by default. In order to make the special symbols of the Sun
178 keyboards driven by sunkbd(4) work under X these now have
179 to be configured the same way as Sun USB keyboards driven
180 by ukbd(4) (which also does AT keyboard emulation), f.e.:
182 Option "XkbLayout" "us"
183 Option "XkbRules" "xorg"
184 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
187 It has been decided that it is desirable to provide ABI
188 backwards compatibility to the FreeBSD 4/5/6 versions of the
189 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
190 broken with the introduction of PCI domain support (see the
191 20070930 entry). Unfortunately, this required the ABI of
192 PCIOCGETCONF to be broken again in order to be able to
193 provide backwards compatibility to the old version of that
194 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
195 again. As for prominent ports this affects neither pciutils
196 nor xorg-server this time, the hal port needs to be rebuilt
203 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
204 WITHOUT_LIBTHR are set.
207 The PCI code has been made aware of PCI domains. This means that
208 the location strings as used by pciconf(8) etc are now in the
209 following format: pci<domain>:<bus>:<device>[:<function>]. It
210 also means that consumers of <sys/pciio.h> potentially need to
211 be recompiled; this includes the hal and xorg-server ports.
214 The caching daemon (cached) was renamed to nscd. nscd.conf
215 configuration file should be used instead of cached.conf and
216 nscd_enable, nscd_pidfile and nscd_flags options should be used
217 instead of cached_enable, cached_pidfile and cached_flags in
221 The new IPsec code is now compiled in using the IPSEC option. The
222 IPSEC option now requires "device crypto" be defined in your kernel
223 configuration. The FAST_IPSEC kernel option is now deprecated.
226 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
227 note the changed syntax - keep state is now on by default. Also
228 note the fact that ftp-proxy(8) has been changed from bottom up and
229 has been moved from libexec to usr/sbin. Changes in the ALTQ
230 handling also affect users of IPFW's ALTQ capabilities.
233 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
234 only IPsec supported by FreeBSD. The new IPsec stack
235 supports both IPv4 and IPv6. The kernel option will change
236 after the code changes have settled in. For now the kernel
237 option IPSEC is deprecated and FAST_IPSEC is the only option, that
238 will change after some settling time.
241 The wicontrol(8) utility has been removed from the base system. wi(4)
242 cards should be configured using ifconfig(8), see the man page for more
246 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
247 instead of the nve(4) driver. Please update your configuration
251 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
252 database if it is missing or older than the aliases file. If
253 desired, set the new rc.conf option sendmail_rebuild_aliases
254 to "YES" to restore that functionality.
257 The IPv4 multicast socket code has been considerably modified, and
258 moved to the file sys/netinet/in_mcast.c. Initial support for the
259 RFC 3678 Source-Specific Multicast Socket API has been added to
260 the IPv4 network stack.
262 Strict multicast and broadcast reception is now the default for
263 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
264 has now been removed.
266 The RFC 1724 hack for interface selection has been removed; the use
267 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
268 been added to replace it. Consumers such as routed will soon be
269 updated to reflect this.
271 These changes affect users who are running routed(8) or rdisc(8)
272 from the FreeBSD base system on point-to-point or unnumbered
276 The net80211 layer has changed significantly and all wireless
277 drivers that depend on it need to be recompiled. Further these
278 changes require that any program that interacts with the wireless
279 support in the kernel be recompiled; this includes: ifconfig,
280 wpa_supplicant, hostapd, and wlanstats. Users must also, for
281 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
282 if they use modules for wireless support. These modules implement
283 scanning support for station and ap modes, respectively. Failure
284 to load the appropriate module before marking a wireless interface
285 up will result in a message to the console and the device not
289 The pam_nologin(8) module ceases to provide an authentication
290 function and starts providing an account management function.
291 Consequent changes to /etc/pam.d should be brought in using
292 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
293 need manual editing as follows. Locate this line (or similar):
295 auth required pam_nologin.so no_warn
297 and change it according to this example:
299 account required pam_nologin.so no_warn
301 That is, the first word needs to be changed from "auth" to
302 "account". The new line can be moved to the account section
303 within the file for clarity. Not updating pam.conf(5) files
304 will result in nologin(5) ignored by the respective services.
307 The ether_ioctl() function has been synchronized with ioctl(2)
308 and ifnet.if_ioctl. Due to that, the size of one of its arguments
309 has changed on 64-bit architectures. All kernel modules using
310 ether_ioctl() need to be rebuilt on such architectures.
313 Improved INCLUDE_CONFIG_FILE support has been introduced to the
314 config(8) utility. In order to take advantage of this new
315 functionality, you are expected to recompile and install
316 src/usr.sbin/config. If you don't rebuild config(8), and your
317 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
318 build will be broken because of a missing "kernconfstring"
322 Symbol versioning is enabled by default. To disable it, use
323 option WITHOUT_SYMVER. It is not advisable to attempt to
324 disable symbol versioning once it is enabled; your installworld
325 will break because a symbol version-less libc will get installed
326 before the install tools. As a result, the old install tools,
327 which previously had symbol dependencies to FBSD_1.0, will fail
328 because the freshly installed libc will not have them.
330 The default threading library (providing "libpthread") has been
331 changed to libthr. If you wish to have libkse as your default,
332 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
335 The ABI breakage in sendmail(8)'s libmilter has been repaired
336 so it is no longer necessary to recompile mail filters (aka,
337 milters). If you recompiled mail filters after the 20070408
338 note, it is not necessary to recompile them again.
341 The new trunk(4) driver has been renamed to lagg(4) as it better
342 reflects its purpose. ifconfig will need to be recompiled.
345 sendmail(8) has been updated to version 8.14.1. Mail filters
346 (aka, milters) compiled against the libmilter included in the
347 base operating system should be recompiled.
350 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
351 In order to use them one must agree to the respective LICENSE in
352 share/doc/legal and define legal.intel_<name>.license_ack=1 via
353 loader.conf(5) or kenv(1). Make sure to deinstall the now
354 deprecated modules from the respective firmware ports.
357 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
358 were removed from FreeBSD's libc. These originally came from INRIA
359 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
360 deprecated in previous releases.
361 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
362 replace it as a more portable (and re-entrant) API.
365 To support interrupt filtering a modification to the newbus API
366 has occurred, ABI was broken and __FreeBSD_version was bumped
367 to 700031. Please make sure that your kernel and modules are in
369 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
372 The IPv6 multicast forwarding code may now be loaded into GENERIC
373 kernels by loading the ip_mroute.ko module. This is built into the
374 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
375 set; see src.conf(5) for more information.
378 The output of netstat -r has changed. Without -n, we now only
379 print a "network name" without the prefix length if the network
380 address and mask exactly match a Class A/B/C network, and an entry
381 exists in the nsswitch "networks" map.
382 With -n, we print the full unabbreviated CIDR network prefix in
383 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
384 This change is in preparation for changes such as equal-cost
385 multipath, and to more generally assist operational deployment
386 of FreeBSD as a modern IPv4 router.
389 PIM has been turned on by default in the IPv4 multicast
390 routing code. The kernel option 'PIM' has now been removed.
391 PIM is now built by default if option 'MROUTING' is specified.
392 It may now be loaded into GENERIC kernels by loading the
396 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
397 has been removed. Its functionality may be achieved by explicitly
398 configuring gif(4) interfaces and using the 'phyint' keyword in
400 XORP does not support source-routed IPv4 multicast tunnels nor the
401 integrated IPIP tunneling, therefore it is not affected by this
402 change. The __FreeBSD_version macro has been bumped to 700030.
405 Support for PCI Message Signalled Interrupts has been
406 re-enabled in the bge driver, only for those chips which are
407 believed to support it properly. If there are any problems,
408 MSI can be disabled completely by setting the
409 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
413 Support for PCI Message Signalled Interrupts has been
414 disabled again in the bge driver. Many revisions of the
415 hardware fail to support it properly. Support can be
416 re-enabled by removing the #define of BGE_DISABLE_MSI in
417 "src/sys/dev/bge/if_bge.c".
420 Support for PCI Message Signalled Interrupts has been added
421 to the bge driver. If there are any problems, MSI can be
422 disabled completely by setting the 'hw.pci.enable_msi' and
423 'hw.pci.enable_msix' tunables to 0 in the loader.
426 The removal of several facets of the experimental Threading
427 system from the kernel means that the proc and thread structures
428 have changed quite a bit. I suggest all kernel modules that might
429 reference these structures be recompiled.. Especially the
433 Sound infrastructure has been updated with various fixes and
434 improvements. Most of the changes are pretty much transparent,
435 with exceptions of followings:
436 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
437 moved to their own dev sysctl nodes, for example:
438 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
439 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
440 own chardev in the form of "dsp%d.<function>%d", where <function>
441 is p = playback, r = record and v = virtual, respectively. Users
442 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
443 This does not affect those who are using "/dev/dsp".
446 geom(4)'s gmirror(8) class metadata structure has been
447 rev'd from v3 to v4. If you update across this point and
448 your metadata is converted for you, you will not be easily
449 able to downgrade since the /boot/kernel.old/geom_mirror.ko
450 kernel module will be unable to read the v4 metadata. You
451 can resolve this by doing from the loader(8) prompt:
453 set vfs.root.mountfrom="ufs:/dev/XXX"
455 where XXX is the root slice of one of the disks that composed
456 the mirror (i.e.: /dev/ad0s1a). You can then rebuild
457 the array the same way you built it originally.
460 The following binaries have been disconnected from the build:
461 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
462 and mount_std. The functionality of these programs has been
463 moved into the mount program. For example, to mount a devfs
464 filesystem, instead of using mount_devfs, use: "mount -t devfs".
465 This does not affect entries in /etc/fstab, since entries in
466 /etc/fstab are always processed with "mount -t fstype".
469 Support for PCI Message Signalled Interrupts on i386 and amd64
470 has been added to the kernel and various drivers will soon be
471 updated to use MSI when it is available. If there are any problems,
472 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
473 and 'hw.pci.enable_msix' tunables to 0 in the loader.
476 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
477 The lockmgr object layout has been changed as a result of having
478 a lock_object embedded in it. As a consequence all file system
479 kernel modules must be re-compiled. The mutex profiling man page
480 has not yet been updated to reflect this change.
483 KSE in the kernel has now been made optional and turned on by
484 default. Use 'nooption KSE' in your kernel config to turn it
485 off. All kernel modules *must* be recompiled after this change.
486 There-after, modules from a KSE kernel should be compatible with
487 modules from a NOKSE kernel due to the temporary padding fields
488 added to 'struct proc'.
491 mrouted and its utilities have been removed from the base system.
494 Some ioctl(2) command codes have changed. Full backward ABI
495 compatibility is provided if the "options COMPAT_FREEBSD6" is
496 present in the kernel configuration file. Make sure to add
497 this option to your kernel config file, or recompile X.Org
498 and the rest of ports; otherwise they may refuse to work.
501 tcpslice has been removed from the base system.
504 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
505 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
506 systat needs to be rebuilt.
509 libpcap updated to v0.9.4 and tcpdump to v3.9.4
512 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
513 for IPFIREWALL_FORWARD is now as it was before when it was first
514 committed and for years after. The behaviour is now ON.
517 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
518 Now it can decrypt files created from different architectures.
519 Unfortunately, it is no longer able to decrypt a cipher text
520 generated with an older version on 64 bit architectures.
521 If you have such a file, you need old utility to decrypt it.
524 The interface version of the i4b kernel part has changed. So
525 after updating the kernel sources and compiling a new kernel,
526 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
527 be rebuilt, and vice versa.
530 The XBOX kernel now defaults to the nfe(4) driver instead of
531 the nve(4) driver. Please update your configuration
535 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
536 PCnet family of NICs has been removed. The new le(4) driver serves
537 as an equivalent but cross-platform replacement with the pcn(4)
538 driver still providing performance-optimized support for the subset
539 of AMD Am79C971 PCnet-FAST and greater chips as before.
542 The machdep.* sysctls and the adjkerntz utility have been
543 modified a bit. The new adjkerntz utility uses the new
544 sysctl names and sysctlbyname() calls, so it may be impossible
545 to run an old /sbin/adjkerntz utility in single-user mode
546 with a new kernel. Replace the `adjkerntz -i' step before
547 `make installworld' with:
549 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
551 and proceed as usual with the rest of the installworld-stage
552 steps. Otherwise, you risk installing binaries with their
553 timestamp set several hours in the future, especially if
554 you are running with local time set to GMT+X hours.
557 The ip6fw utility has been removed. The behavior provided by
558 ip6fw has been in ipfw2 for a good while and the rc.d scripts
559 have been updated to deal with it. There are some rules that
560 might not migrate cleanly. Use rc.firewall6 as a template to
564 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
565 attachments have been removed. Make sure to configure scc(4)
566 on sparc64. Note also that by default puc(4) will use uart(4)
567 and not sio(4) for serial ports because interrupt handling has
568 been optimized for multi-port serial cards and only uart(4)
569 implements the interface to support it.
572 The scc(4) driver replaces puc(4) for Serial Communications
573 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
574 Z8530. On sparc64, it is advised to add scc(4) to the kernel
575 configuration to make sure that the serial ports remain
579 Most world/kernel related NO_* build options changed names.
580 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
581 after FreeBSD ports) and should be set in /etc/src.conf
582 (the src.conf(5) manpage is provided). Full backwards
583 compatibility is maintained for the time being though it's
584 highly recommended to start moving old options out of the
585 system-wide /etc/make.conf file into the new /etc/src.conf
586 while also properly renaming them. More conversions will
587 likely follow. Posting to current@:
589 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
592 The NETSMBCRYPTO kernel option has been retired because its
593 functionality is always included in NETSMB and smbfs.ko now.
596 The TDFX_LINUX kernel option was retired and replaced by the
597 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
598 kernel module. Loading it alone should suffice to get 3dfx support
599 for Linux apps because it will pull in 3dfx.ko and linux.ko through
603 The 'audit' group was added to support the new auditing functionality
604 in the base system. Be sure to follow the directions for updating,
605 including the requirement to run mergemaster -p.
608 The kernel ABI to file system modules was changed on i386.
609 Please make sure that your kernel and modules are in sync.
612 This actually occured some time ago, but installing the kernel
613 now also installs a bunch of symbol files for the kernel modules.
614 This increases the size of /boot/kernel to about 67Mbytes. You
615 will need twice this if you will eventually back this up to kernel.old
616 on your next install.
617 If you have a shortage of room in your root partition, you should add
618 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
619 to your /etc/make.conf.
622 libc's malloc implementation has been replaced. This change has the
623 potential to uncover application bugs that previously went unnoticed.
624 See the malloc(3) manual page for more details.
627 The generic netgraph(4) cookie has been changed. If you upgrade
628 kernel passing this point, you also need to upgrade userland
629 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
632 si(4)'s device files now contain the unit number.
633 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
636 The kernel ABI was mostly destroyed due to a change in the size
637 of struct lock_object which is nested in other structures such
638 as mutexes which are nested in all sorts of other structures.
639 Make sure your kernel and modules are in sync.
642 The page coloring algorithm in the VM subsystem was converted
643 from tuning with kernel options to autotuning. Please remove
644 any PQ_* option except PQ_NOOPT from your kernel config.
647 The net80211-related tools in the tools/tools/ath directory
648 have been moved to tools/tools/net80211 and renamed with a
649 "wlan" prefix. Scripts that use them should be adjusted
653 Scripts in the local_startup directories (as defined in
654 /etc/defaults/rc.conf) that have the new rc.d semantics will
655 now be run as part of the base system rcorder. If there are
656 errors or problems with one of these local scripts, it could
657 cause boot problems. If you encounter such problems, boot in
658 single user mode, remove that script from the */rc.d directory.
659 Please report the problem to the port's maintainer, and the
660 freebsd-ports@freebsd.org mailing list.
663 The nodev mount option was deprecated in RELENG_6 (where it
664 was a no-op), and is now unsupported. If you have nodev or dev listed
665 in /etc/fstab, remove it, otherwise it will result in a mount error.
668 ABI between ipfw(4) and ipfw(8) has been changed. You need
669 to rebuild ipfw(8) when rebuilding kernel.
672 rp(4)'s device files now contain the unit number.
673 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
676 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
677 Its /etc/rc.conf.d configuration file has been `ppp' from
678 the beginning, and hence there is no need to touch it.
681 Now most modules get their build-time options from the kernel
682 configuration file. A few modules still have fixed options
683 due to their non-conformant implementation, but they will be
684 corrected eventually. You may need to review the options of
685 the modules in use, explicitly specify the non-default options
686 in the kernel configuration file, and rebuild the kernel and
690 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
691 to turn polling(4) on your interfaces.
694 The old bridge(4) implementation was retired. The new
695 if_bridge(4) serves as a full functional replacement.
698 The ai_addrlen of a struct addrinfo was changed to a socklen_t
699 to conform to POSIX-2001. This change broke an ABI
700 compatibility on 64 bit architecture. You have to recompile
701 userland programs that use getaddrinfo(3) on 64 bit
705 RELENG_6 branched here.
708 The pccard_ifconfig rc.conf variable has been removed and a new
709 variable, ifconfig_DEFAULT has been introduced. Unlike
710 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
711 do not have ifconfig_ifn entries rather than just those in
712 removable_interfaces.
715 Some previous versions of PAM have permitted the use of
716 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
717 to third party PAM modules in /usr/local/lib. A change has been
718 made to require the use of absolute paths in order to avoid
719 ambiguity and dependence on library path configuration, which may
720 affect existing configurations.
723 Major changes to network interface API. All drivers must be
724 recompiled. Drivers not in the base system will need to be
725 updated to the new APIs.
728 Changes were made to kinfo_proc in sys/user.h. Please recompile
729 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
730 will not behave correctly.
732 The API and ABI for hwpmc(4) have changed with the addition
733 of sampling support. Please recompile lib/libpmc(3) and
734 usr.sbin/{pmcstat,pmccontrol}.
737 The OpenBSD dhclient was imported in place of the ISC dhclient
738 and the network interface configuration scripts were updated
739 accordingly. If you use DHCP to configure your interfaces, you
740 must now run devd. Also, DNS updating was lost so you will need
741 to find a workaround if you use this feature.
743 The '_dhcp' user was added to support the OpenBSD dhclient. Be
744 sure to run mergemaster -p (like you are supposed to do every time
748 if_bridge was added to the tree. This has changed struct ifnet.
749 Please recompile userland and all network related modules.
752 The n_net of a struct netent was changed to an uint32_t, and
753 1st argument of getnetbyaddr() was changed to an uint32_t, to
754 conform to POSIX-2001. These changes broke an ABI
755 compatibility on 64 bit architecture. With these changes,
756 shlib major of libpcap was bumped. You have to recompile
757 userland programs that use getnetbyaddr(3), getnetbyname(3),
758 getnetent(3) and/or libpcap on 64 bit architecture.
761 Kernel parsing of extra options on '#!' first lines of shell
762 scripts has changed. Lines with multiple options likely will
763 fail after this date. For full details, please see
764 http://people.freebsd.org/~gad/Updating-20050528.txt
767 The packet filter (pf) code has been updated to OpenBSD 3.7
768 Please note the changed anchor syntax and the fact that
769 authpf(8) now needs a mounted fdescfs(5) to function.
772 The NO_MIXED_MODE kernel option has been removed from the i386
773 amd64 platforms as its use has been superceded by the new local
774 APIC timer code. Any kernel config files containing this option
778 The on-disk format of LC_CTYPE files was changed to be machine
779 independent. Please make sure NOT to use NO_CLEAN buildworld
780 when crossing this point. Crossing this point also requires
781 recompile or reinstall of all locale depended packages.
784 The ifi_epoch member of struct if_data has been changed to
785 contain the uptime at which the interface was created or the
786 statistics zeroed rather then the wall clock time because
787 wallclock time may go backwards. This should have no impact
788 unless an snmp implementation is using this value (I know of
792 The acpi_perf and acpi_throttle drivers are now part of the
793 acpi(4) main module. They are no longer built separately.
796 The layout of struct image_params has changed. You have to
797 recompile all compatibility modules (linux, svr4, etc) for use
801 The p4tcc driver has been merged into cpufreq(4). This makes
802 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
803 compile in "device cpufreq" to restore this functionality.
806 The responsibility of recomputing the file system summary of
807 a SoftUpdates-enabled dirty volume has been transferred to the
808 background fsck. A rebuild of fsck(8) utility is recommended
809 if you have updated the kernel.
811 To get the old behavior (recompute file system summary at mount
812 time), you can set vfs.ffs.compute_summary_at_mount=1 before
813 mounting the new volume.
816 The cpufreq import is complete. As part of this, the sysctls for
817 acpi(4) throttling have been removed. The power_profile script
818 has been updated, so you can use performance/economy_cpu_freq in
819 rc.conf(5) to set AC on/offline cpu frequencies.
822 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
823 requires recompiling libnetgraph and userland netgraph utilities.
826 Support for abbreviated forms of a number of ipfw options is
827 now deprecated. Warnings are printed to stderr indicating the
828 correct full form when a match occurs. Some abbreviations may
829 be supported at a later date based on user feedback. To be
830 considered for support, abbreviations must be in use prior to
831 this commit and unlikely to be confused with current key words.
834 By a popular demand, a lot of NOFOO options were renamed
835 to NO_FOO (see bsd.compat.mk for a full list). The old
836 spellings are still supported, but will cause annoying
837 warnings on stderr. Make sure you upgrade properly (see
838 the COMMON ITEMS: section later in this file).
841 Auto-loading of ancillary wlan modules such as wlan_wep has
842 been temporarily disabled; you need to statically configure
843 the modules you need into your kernel or explicitly load them
844 prior to use. Specifically, if you intend to use WEP encryption
845 with an 802.11 device load/configure wlan_wep; if you want to
846 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
847 and wlan_xauth as required.
850 The behaviour of ppp(8) has changed slightly. If lqr is enabled
851 (``enable lqr''), older versions would revert to LCP ECHO mode on
852 negotiation failure. Now, ``enable echo'' is required for this
853 behaviour. The ppp version number has been bumped to 3.4.2 to
857 The wlan support has been updated to split the crypto support
858 into separate modules. For static WEP you must configure the
859 wlan_wep module in your system or build and install the module
860 in place where it can be loaded (the kernel will auto-load
861 the module when a wep key is configured).
864 The ath driver has been updated to split the tx rate control
865 algorithm into a separate module. You need to include either
866 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
869 Support for systems with an 80386 CPU has been removed. Please
870 use FreeBSD 5.x or earlier on systems with an 80386.
873 We have had a hack which would mount the root filesystem
874 R/W if the device were named 'md*'. As part of the vnode
875 work I'm doing I have had to remove this hack. People
876 building systems which use preloaded MD root filesystems
877 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
878 their /etc/rc scripts.
881 FreeBSD 5.3 shipped here.
884 The size of struct tcpcb has changed again due to the removal
885 of RFC1644 T/TCP. You have to recompile userland programs that
886 read kmem for tcp sockets directly (netstat, sockstat, etc.)
889 The size of struct tcpcb has changed. You have to recompile
890 userland programs that read kmem for tcp sockets directly
891 (netstat, sockstat, etc.)
894 RELENG_5 branched here. For older entries, please see updating
895 in the RELENG_5 branch.
901 Avoid using make -j when upgrading. From time to time in the
902 past there have been problems using -j with buildworld and/or
903 installworld. This is especially true when upgrading between
904 "distant" versions (eg one that cross a major release boundary
905 or several minor releases, or when several months have passed
906 on the -current branch).
908 Sometimes, obscure build problems are the result of environment
909 poisoning. This can happen because the make utility reads its
910 environment when searching for values for global variables.
911 To run your build attempts in an "environmental clean room",
912 prefix all make commands with 'env -i '. See the env(1) manual
913 page for more details.
915 When upgrading from one major version to another it is generally
916 best to upgrade to the latest code in the currently installed branch
917 first, then do an upgrade to the new branch. This is the best-tested
918 upgrade path, and has the highest probability of being successful.
919 Please try this approach before reporting problems with a major
924 If you are updating from a prior version of FreeBSD (even one just
925 a few days old), you should follow this procedure. It is the most
926 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
928 make kernel-toolchain
929 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
930 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
932 To test a kernel once
933 ---------------------
934 If you just want to boot a kernel once (because you are not sure
935 if it works, or if you want to boot a known bad kernel to provide
936 debugging information) run
937 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
938 nextboot -k testkernel
940 To just build a kernel when you know that it won't mess you up
941 --------------------------------------------------------------
942 This assumes you are already running a 5.X system. Replace
943 ${arch} with the architecture of your machine (e.g. "i386",
944 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
946 cd src/sys/${arch}/conf
947 config KERNEL_NAME_HERE
948 cd ../compile/KERNEL_NAME_HERE
953 If this fails, go to the "To build a kernel" section.
955 To rebuild everything and install it on the current system.
956 -----------------------------------------------------------
957 # Note: sometimes if you are running current you gotta do more than
958 # is listed here if you are upgrading from a really old current.
960 <make sure you have good level 0 dumps>
962 make kernel KERNCONF=YOUR_KERNEL_HERE
964 <reboot in single user> [3]
972 To cross-install current onto a separate partition
973 --------------------------------------------------
974 # In this approach we use a separate partition to hold
975 # current's root, 'usr', and 'var' directories. A partition
976 # holding "/", "/usr" and "/var" should be about 2GB in
979 <make sure you have good level 0 dumps>
982 make buildkernel KERNCONF=YOUR_KERNEL_HERE
983 <maybe newfs current's root partition>
984 <mount current's root partition on directory ${CURRENT_ROOT}>
985 make installworld DESTDIR=${CURRENT_ROOT}
986 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
987 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
988 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
989 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
990 <reboot into current>
991 <do a "native" rebuild/install as described in the previous section>
992 <maybe install compatibility libraries from src/lib/compat>
996 To upgrade in-place from 5.x-stable to current
997 ----------------------------------------------
998 <make sure you have good level 0 dumps>
1000 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1002 <reboot in single user> [3]
1009 Make sure that you've read the UPDATING file to understand the
1010 tweaks to various things you need. At this point in the life
1011 cycle of current, things change often and you are on your own
1012 to cope. The defaults can also change, so please read ALL of
1013 the UPDATING entries.
1015 Also, if you are tracking -current, you must be subscribed to
1016 freebsd-current@freebsd.org. Make sure that before you update
1017 your sources that you have read and understood all the recent
1018 messages there. If in doubt, please track -stable which has
1019 much fewer pitfalls.
1021 [1] If you have third party modules, such as vmware, you
1022 should disable them at this point so they don't crash your
1025 [3] From the bootblocks, boot -s, and then do
1030 adjkerntz -i # if CMOS is wall time
1031 Also, when doing a major release upgrade, it is required that
1032 you boot into single user mode to do the installworld.
1034 [4] Note: This step is non-optional. Failure to do this step
1035 can result in a significant reduction in the functionality of the
1036 system. Attempting to do it by hand is not recommended and those
1037 that pursue this avenue should read this file carefully, as well
1038 as the archives of freebsd-current and freebsd-hackers mailing lists
1039 for potential gotchas.
1041 [5] Usually this step is a noop. However, from time to time
1042 you may need to do this if you get unknown user in the following
1043 step. It never hurts to do it all the time. You may need to
1044 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1045 install) after the buildworld before this step if you last updated
1046 from current before 20020224 or from -stable before 20020408.
1048 [8] In order to have a kernel that can run the 4.x binaries
1049 needed to do an installworld, you must include the COMPAT_FREEBSD4
1050 option in your kernel. Failure to do so may leave you with a system
1051 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
1052 is required to run the 5.x binaries on more recent kernels.
1054 Make sure that you merge any new devices from GENERIC since the
1055 last time you updated your kernel config file.
1057 [9] When checking out sources, you must include the -P flag to have
1058 cvs prune empty directories.
1060 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1061 "?=" instead of the "=" assignment operator, so that buildworld can
1062 override the CPUTYPE if it needs to.
1064 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1065 not on the command line, or in /etc/make.conf. buildworld will
1066 warn if it is improperly defined.
1069 This file contains a list, in reverse chronological order, of major
1070 breakages in tracking -current. Not all things will be listed here,
1071 and it only starts on October 16, 2004. Updating files can found in
1072 previous releases if your system is older than this.
1074 Copyright information:
1076 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
1078 Redistribution, publication, translation and use, with or without
1079 modification, in full or in part, in any form or format of this
1080 document are permitted without further permission from the author.
1082 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1083 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1084 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1085 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1086 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1087 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1088 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1089 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1090 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1091 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1092 POSSIBILITY OF SUCH DAMAGE.
1094 If you find this document useful, and you want to, you may buy the
1097 Contact Warner Losh if you have any questions about your use of