1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 Items affecting the ports and packages system can be found in
10 /usr/ports/UPDATING. Please read that file before running portupgrade.
12 NOTE TO PEOPLE WHO THINK THAT FreeBSD 9.x IS SLOW:
13 FreeBSD 9.x has many debugging features turned on, in both the kernel
14 and userland. These features attempt to detect incorrect use of
15 system primitives, and encourage loud failure through extra sanity
16 checking and fail stop semantics. They also substantially impact
17 system performance. If you want to do performance measurement,
18 benchmarking, and optimization, you'll want to turn them off. This
19 includes various WITNESS- related kernel options, INVARIANTS, malloc
20 debugging flags in userland, and various verbose features in the
21 kernel. Many developers choose to disable these features on build
22 machines to maximize performance. (To disable malloc debugging, run
23 ln -s aj /etc/malloc.conf.)
26 This commit modifies vfs_register() so that it uses a hash
27 calculation to set vfc_typenum, which is enabled by default.
28 The first time a system is booted after this change, the
29 vfc_typenum values will change for all file systems. The
30 main effect of this is a change to the NFS server file handles
31 for file systems that use vfc_typenum in their fsid, such as ZFS.
32 It will, however, prevent vfc_typenum from changing when file
33 systems are loaded in a different order for subsequent reboots.
34 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
35 until you are ready to remount all NFS clients after a reboot.
38 Bump the shared library version numbers for libraries that
39 do not use symbol versioning, have changed the ABI compared
40 to stable/8 and which shared library version was not bumped.
41 Done as part of 9.0-RELEASE cycle.
44 During the merge of Capsicum features, the fget(9) KPI was modified.
45 This may require the rebuilding of out-of-tree device drivers --
46 issues have been reported specifically with the nVidia device driver.
47 __FreeBSD_version is bumped to 900041.
49 Also, there is a period between 20110811 and 20110814 where the
50 special devices /dev/{stdin,stdout,stderr} did not work correctly.
51 Building world from a kernel during that window may not work.
54 The packet filter (pf) code has been updated to OpenBSD 4.5.
55 You need to update userland tools to be in sync with kernel.
56 This update breaks backward compatibility with earlier pfsync(4)
57 versions. Care must be taken when updating redundant firewall setups.
60 The following sysctls and tunables are retired on x86 platforms:
62 machdep.hlt_logical_cpus
63 The following sysctl is retired:
64 machdep.hyperthreading_allowed
65 The sysctls were supposed to provide a way to dynamically offline and
66 online selected CPUs on x86 platforms, but the implementation has not
67 been reliable especially with SCHED_ULE scheduler.
68 machdep.hyperthreading_allowed tunable is still available to ignore
69 hyperthreading CPUs at OS level.
70 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
71 where X is an APIC ID of a CPU. Be advised, though, that disabling
72 CPUs in non-uniform fashion will result in non-uniform topology and
73 may lead to sub-optimal system performance with SCHED_ULE, which is
77 cpumask_t type is retired and cpuset_t is used in order to describe
81 Changes to ifconfig(8) for dynamic address family detection mandate
82 that you are running a kernel of 20110525 or later. Make sure to
83 follow the update procedure to boot a new kernel before installing
87 Support for sun4v architecture is officially dropped
90 Several KPI breaking changes have been committed to the mii(4) layer,
91 the PHY drivers and consequently some Ethernet drivers using mii(4).
92 This means that miibus.ko and the modules of the affected Ethernet
93 drivers need to be recompiled.
95 Note to kernel developers: Given that the OUI bit reversion problem
96 was fixed as part of these changes all mii(4) commits related to OUIs,
97 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
98 handling, no longer can be merged verbatim to stable/8 and previous
102 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
103 into their kernel configurations along with 'device pci'.
106 The default NFS client is now the new NFS client, so fstype "newnfs"
107 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
108 Although mounts via fstype "nfs" will usually work without userland
109 changes, it is recommended that the mount(8) and mount_nfs(8)
110 commands be rebuilt from sources and that a link to mount_nfs called
111 mount_oldnfs be created. The new client is compiled into the
112 kernel with "options NFSCL" and this is needed for diskless root
113 file systems. The GENERIC kernel configs have been changed to use
114 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
115 To use the regular/old client, you can "mount -t oldnfs ...". For
116 a diskless root file system, you must also include a line like:
118 vfs.root.mountfrom="oldnfs:"
120 in the boot/loader.conf on the root fs on the NFS server to make
121 a diskless root fs use the old client.
124 The GENERIC kernels for all architectures now default to the new
125 CAM-based ATA stack. It means that all legacy ATA drivers were
126 removed and replaced by respective CAM drivers. If you are using
127 ATA device names in /etc/fstab or other places, make sure to update
128 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
129 where 'Y's are the sequential numbers starting from zero for each type
130 in order of detection, unless configured otherwise with tunables,
131 see cam(4)). There will be symbolic links created in /dev/ to map
132 old adX devices to the respective adaY. They should provide basic
133 compatibility for file systems mounting in most cases, but they do
134 not support old user-level APIs and do not have respective providers
135 in GEOM. Consider using updated management tools with new device names.
137 It is possible to load devices ahci, ata, siis and mvs as modules,
138 but option ATA_CAM should remain in kernel configuration to make ata
139 module work as CAM driver supporting legacy ATA controllers. Device ata
140 still can be used in modular fashion (atacore + ...). Modules atadisk
141 and atapi* are not used and won't affect operation in ATA_CAM mode.
142 Note that to use CAM-based ATA kernel should include CAM devices
143 scbus, pass, da (or explicitly ada), cd and optionally others. All of
144 them are parts of the cam module.
146 ataraid(4) functionality is now supported by the RAID GEOM class.
147 To use it you can load geom_raid kernel module and use graid(8) tool
148 for management. Instead of /dev/arX device names, use /dev/raid/rX.
150 No kernel config options or code have been removed, so if a problem
151 arises, please report it and optionally revert to the old ATA stack.
152 In order to do it you can remove from the kernel config:
157 , and instead add back:
158 device atadisk # ATA disk drives
159 device ataraid # ATA RAID drives
160 device atapicd # ATAPI CDROM drives
161 device atapifd # ATAPI floppy drives
162 device atapist # ATAPI tape drives
165 The default NFS server has been changed to the new server, which
166 was referred to as the experimental server. If you need to switch
167 back to the old NFS server, you must now put the "-o" option on
168 both the mountd and nfsd commands. This can be done using the
169 mountd_flags and nfs_server_flags rc.conf variables until an
170 update to the rc scripts is committed, which is coming soon.
173 The GNU Objective-C runtime library (libobjc), and other Objective-C
174 related components have been removed from the base system. If you
175 require an Objective-C library, please use one of the available ports.
178 ath(4) has been split into bus- and device- modules. if_ath contains
179 the HAL, the TX rate control and the network device code. if_ath_pci
180 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
181 contains the AHB glue. Users need to load both if_ath_pci and if_ath
182 in order to use ath on everything else.
184 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
185 need to load if_ath and if_ath_pci for ath(4) operation.
188 As part of the replacement of sysinstall, the process of building
189 release media has changed significantly. For details, please re-read
190 release(7), which has been updated to reflect the new build process.
193 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
194 is the last available version under GPLv2. It brings a number of new
195 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
196 4.1 and SSE 4.2), better support for powerpc64, a number of new
197 directives, and lots of other small improvements. See the ChangeLog
198 file in contrib/binutils for the full details.
201 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
202 compliant, and will now use half of hash for authentication.
203 This will break interoperability with all stacks (including all
204 actual FreeBSD versions) who implement
205 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
207 The only workaround with such peers is to use another HMAC
208 algorithm for IPsec ("phase 2") authentication.
211 Remove the uio_yield prototype and symbol. This function has
212 been misnamed since it was introduced and should not be
213 globally exposed with this name. The equivalent functionality
214 is now available using kern_yield(curthread->td_user_pri).
215 The function remains undocumented.
218 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
219 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
220 for scalar sysctls is defined but disabled. Code that needs
221 UQUAD to pass the type checking that must compile on older
222 systems where the define is not present can check against
223 __FreeBSD_version >= 900030.
225 The system dialog(1) has been replaced with a new version previously
226 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
227 with the previous version, but the libdialog associated with it has
228 a largely incompatible API. As such, the original version of libdialog
229 will be kept temporarily as libodialog, until its base system consumers
230 are replaced or updated. Bump __FreeBSD_version to 900030.
233 If you are trying to run make universe on a -stable system, and you get
234 the following warning:
235 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
236 unknown. config(8) likely too old."
237 or something similar to it, then you must upgrade your -stable system
238 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
239 stable/8) or build the config from the latest stable/8 branch and
240 install it on your system.
242 Prior to this date, building a current universe on 8-stable system from
243 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
244 error in the first kernel build phase. A new config on those old
245 systems will fix that problem for older versions of -current.
248 The TCP stack has been modified to allow Khelp modules to interact with
249 it via helper hook points and store per-connection data in the TCP
250 control block. Bump __FreeBSD_version to 900029. User space tools that
251 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
255 Generic IEEE 802.3 annex 31B full duplex flow control support has been
256 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
257 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
258 to take advantage of it instead of using custom implementations. This
259 means that these drivers now no longer unconditionally advertise
260 support for flow control but only do so if flow control is a selected
261 media option. This was implemented in the generic support that way in
262 order to allow flow control to be switched on and off via ifconfig(8)
263 with the PHY specific default to typically off in order to protect
264 from unwanted effects. Consequently, if you used flow control with
265 one of the above mentioned drivers you now need to explicitly enable
267 ifconfig bge0 media auto mediaopt flowcontrol
269 Along with the above mentioned changes generic support for setting
270 1000baseT master mode also has been added and brgphy(4), ciphy(4),
271 e1000phy(4) as well as ip1000phy(4) have been converted to take
272 advantage of it. This means that these drivers now no longer take the
273 link0 parameter for selecting master mode but the master media option
274 has to be used instead, for example like in the following:
275 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
277 Selection of master mode now is also available with all other PHY
278 drivers supporting 1000baseT.
281 The TCP stack has received a significant update to add support for
282 modularised congestion control and generally improve the clarity of
283 congestion control decisions. Bump __FreeBSD_version to 900025. User
284 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
285 sockstat) need to be recompiled.
288 The man(1) utility has been replaced by a new version that no longer
289 uses /etc/manpath.config. Please consult man.conf(5) for how to
290 migrate local entries to the new format.
293 The copyright strings printed by login(1) and sshd(8) at the time of a
294 new connection have been removed to follow other operating systems and
298 A workaround for a fixed ld bug has been removed in kernel code,
299 so make sure that your system ld is built from sources after
300 revision 210245 from 2010-07-19 (r211583 if building head kernel
301 on stable/8, r211584 for stable/7; both from 2010-08-21).
302 A symptom of incorrect ld version is different addresses for
303 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
306 The $ipv6_prefer variable in rc.conf(5) has been split into
307 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
309 The $ip6addrctl_policy is a variable to choose a pre-defined
310 address selection policy set by ip6addrctl(8). A value
311 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
314 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
315 flag (see an entry of 20090926) is set on an interface with no
316 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
317 security reason. If you want IPv6 link-local address on all
318 interfaces by default, set this to "YES".
320 The old ipv6_prefer="YES" is equivalent to
321 ipv6_activate_all_interfaces="YES" and
322 ip6addrctl_policy="ipv6_prefer".
325 DTrace has grown support for userland tracing. Due to this, DTrace is
326 now i386 and amd64 only.
327 dtruss(1) is now installed by default on those systems and a new
328 kernel module is needed for userland tracing: fasttrap.
329 No changes to your kernel config file are necessary to enable
330 userland tracing, but you might consider adding 'STRIP=' and
331 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
332 to have informative userland stack traces in DTrace (ustack).
335 The acpi_aiboost(4) driver has been removed in favor of the new
336 aibs(4) driver. You should update your kernel configuration file.
339 BSD grep has been imported to the base system and it is built by
340 default. It is completely BSD licensed, highly GNU-compatible, uses
341 less memory than its GNU counterpart and has a small codebase.
342 However, it is slower than its GNU counterpart, which is mostly
343 noticeable for larger searches, for smaller ones it is measurable
344 but not significant. The reason is complex, the most important factor
345 is that we lack a modern and efficient regex library and GNU
346 overcomes this by optimizing the searches internally. Future work
347 on improving the regex performance is planned, for the meantime,
348 users that need better performance, can build GNU grep instead by
349 setting the WITH_GNU_GREP knob.
352 Due to the import of powerpc64 support, all existing powerpc kernel
353 configuration files must be updated with a machine directive like this:
354 machine powerpc powerpc
356 In addition, an updated config(8) is required to build powerpc kernels
360 A new version of ZFS (version 15) has been merged to -HEAD.
361 This version uses a python library for the following subcommands:
362 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
363 For full functionality of these commands the following port must
364 be installed: sysutils/py-zfs
367 'vm_page's are now hashed by physical address to an array of mutexes.
368 Currently this is only used to serialize access to hold_count. Over
369 time the page queue mutex will be peeled away. This changes the size
370 of pmap on every architecture. And requires all callers of vm_page_hold
371 and vm_page_unhold to be updated.
374 WITH_CTF can now be specified in src.conf (not recommended, there
375 are some problems with static executables), make.conf (would also
376 affect ports which do not use GNU make and do not override the
377 compile targets) or in the kernel config (via "makeoptions
379 When WITH_CTF was specified there before this was silently ignored,
380 so make sure that WITH_CTF is not used in places which could lead
381 to unwanted behavior.
384 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
385 to allow 32-bit compatibility on non-x86 platforms. All kernel
386 configurations on amd64 and ia64 platforms using these options must
387 be modified accordingly.
390 The utmp user accounting database has been replaced with utmpx,
391 the user accounting interface standardized by POSIX.
392 Unfortunately the semantics of utmp and utmpx don't match,
393 making it practically impossible to support both interfaces.
394 The user accounting database is used by tools like finger(1),
395 last(1), talk(1), w(1) and ac(8).
397 All applications in the base system use utmpx. This means only
398 local binaries (e.g. from the ports tree) may still use these
399 utmp database files. These applications must be rebuilt to make
402 After the system has been upgraded, it is safe to remove the old
403 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
404 assuming their contents is of no importance anymore. Old wtmp
405 databases can only be used by last(1) and ac(8) after they have
406 been converted to the new format using wtmpcvt(1).
409 Introduce the kernel thread "deadlock resolver" (which can be enabled
410 via the DEADLKRES option, see NOTES for more details) and the
411 sleepq_type() function for sleepqueues.
414 The rc.firewall and rc.firewall6 were unified, and
415 rc.firewall6 and rc.d/ip6fw were removed.
416 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
417 variables are obsoleted. Instead, the following new rc
418 variables are added to rc.d/ipfw:
420 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
421 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
422 firewall_simple_onet_ipv6, firewall_trusted_ipv6
424 The meanings correspond to the relevant IPv4 variables.
430 The default terminal emulation for syscons(4) has been changed
431 from cons25 to xterm on all platforms except pc98. This means
432 that the /etc/ttys file needs to be updated to ensure correct
433 operation of applications on the console.
435 The terminal emulation style can be toggled per window by using
436 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
437 options can be used to change the compile-time default back to
440 To prevent graphical artifacts, make sure the TERM environment
441 variable is set to match the terminal emulation that is being
442 performed by syscons(4).
445 The layout of the structure ieee80211req_scan_result has changed.
446 Applications that require wireless scan results (e.g. ifconfig(8))
447 from net80211 need to be recompiled.
449 Applications such as wpa_supplicant(8) may require a full world
450 build without using NO_CLEAN in order to get synchronized with the
454 The iwn(4) driver has been updated to support the 5000 and 5150 series.
455 There's one kernel module for each firmware. Adding "device iwnfw"
456 to the kernel configuration file means including all three firmware
457 images inside the kernel. If you want to include just the one for
458 your wireless card, use the the devices iwn4965fw, iwn5000fw or
462 The rc.d/network_ipv6, IPv6 configuration script has been integrated
463 into rc.d/netif. The changes are the following:
465 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
466 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
467 Note that both variables need the "inet6" keyword at the head.
469 Do not set $ipv6_network_interfaces manually if you do not
470 understand what you are doing. It is not needed in most cases.
472 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
475 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
476 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
478 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
479 all configured interfaces have "inet6 accept_rtadv" in the
480 $ifconfig_IF_ipv6. These are for backward compatibility.
482 3. A new variable $ipv6_prefer has been added. If NO, IPv6
483 functionality of interfaces with no corresponding
484 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
485 and the default address selection policy of ip6addrctl(8)
486 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
487 Note that if you want to configure IPv6 functionality on the
488 disabled interfaces after boot, first you need to clear the flag by
489 using ifconfig(8) like:
491 ifconfig em0 inet6 -ifdisabled
493 If YES, the default address selection policy is set as
496 The default value of $ipv6_prefer is NO.
498 4. If your system need to receive Router Advertisement messages,
499 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
500 scripts automatically invoke rtsol(8) when the interface becomes
501 UP. The Router Advertisement messages are used for SLAAC
502 (State-Less Address AutoConfiguration).
505 802.11s D3.03 support was committed. This is incompatible with the
506 previous code, which was based on D3.0.
509 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
510 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
511 control whether accepting Router Advertisement messages or not.
512 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
513 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
514 The ifconfig(8) utility now supports these flags.
517 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
518 mount(8) and -a option for df(1) to see them.
521 The old tunable hw.bus.devctl_disable has been superseded by
522 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
523 replaced by hw.bus.devctl_queue=0. The default for this new tunable
527 Remove the option STOP_NMI. The default action is now to use NMI only
528 for KDB via the newly introduced function stop_cpus_hard() and
529 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
532 The stable/8 branch created in subversion. This corresponds to the
533 RELENG_8 branch in CVS.
536 Bump the shared library version numbers for all libraries that do not
537 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
538 __FreeBSD_version to 800105.
541 Due to changes in the implementation of virtual network stack support,
542 all network-related kernel modules must be recompiled. As this change
543 breaks the ABI, bump __FreeBSD_version to 800104.
546 The TOE interface to the TCP syncache has been modified to remove
547 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
548 The cxgb driver is the only TOE consumer affected by this change, and
549 needs to be recompiled along with the kernel. As this change breaks
550 the ABI, bump __FreeBSD_version to 800103.
553 Padding has been added to struct tcpcb, sackhint and tcpstat in
554 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
555 maintaining the ABI. However, this change breaks the ABI, so bump
556 __FreeBSD_version to 800102. User space tools that rely on the size of
557 any of these structs (e.g. sockstat) need to be recompiled.
560 The NFS_LEGACYRPC option has been removed along with the old kernel
561 RPC implementation that this option selected. Kernel configurations
562 may need to be adjusted.
565 The network interface device nodes at /dev/net/<interface> have been
566 removed. All ioctl operations can be performed the normal way using
567 routing sockets. The kqueue functionality can generally be replaced
568 with routing sockets.
571 The documentation from the FreeBSD Documentation Project (Handbook,
572 FAQ, etc.) is now installed via packages by sysinstall(8) and under
573 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
576 The ABI of various structures related to the SYSV IPC API have been
577 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
578 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
582 Layout of struct vnet has changed as routing related variables were
583 moved to their own Vimage module. Modules need to be recompiled. Bump
584 __FreeBSD_version to 800099.
587 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
588 respectively. As long as no more than 16 groups per process are used,
589 no changes should be visible. When more than 16 groups are used, old
590 binaries may fail if they call getgroups() or getgrouplist() with
591 statically sized storage. Recompiling will work around this, but
592 applications should be modified to use dynamically allocated storage
593 for group arrays as POSIX.1-2008 does not cap an implementation's
594 number of supported groups at NGROUPS_MAX+1 as previous versions did.
596 NFS and portalfs mounts may also be affected as the list of groups is
597 truncated to 16. Users of NFS who use more than 16 groups, should
598 take care that negative group permissions are not used on the exported
599 file systems as they will not be reliable unless a GSSAPI based
600 authentication method is used.
603 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
604 option compiles in the support for adaptive spinning for lockmgrs
605 which want to enable it. The lockinit() function now accepts the flag
606 LK_ADAPTIVE in order to make the lock object subject to adaptive
607 spinning when both held in write and read mode.
610 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
611 changed. User applications that use this ioctl need to be rebuilt.
614 The layout of struct thread has changed. Kernel and modules need to
618 The layout of structs ifnet, domain, protosw and vnet_net has changed.
619 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
622 window(1) has been removed from the base system. It can now be
623 installed from ports. The port is called misc/window.
626 The way we are storing and accessing `routing table' entries has
627 changed. Programs reading the FIB, like netstat, need to be
631 A new netisr implementation has been added for FreeBSD 8. Network
632 file system modules, such as igmp, ipdivert, and others, should be
634 Bump __FreeBSD_version to 800096.
637 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
641 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
642 Bump __FreeBSD_version to 800094.
645 Add mnt_xflag field to 'struct mount'. File system modules need to be
647 Bump __FreeBSD_version to 800093.
650 The compiling option ADAPTIVE_SX has been retired while it has been
651 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
652 The KPI for sx_init_flags() changes as accepting flags:
653 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
654 been introduced in order to handle the reversed logic.
655 Bump __FreeBSD_version to 800092.
658 Add support for hierarchical jails. Remove global securelevel.
659 Bump __FreeBSD_version to 800091.
662 The layout of struct vnet_net has changed, therefore modules
664 Bump __FreeBSD_version to 800090.
667 The newly imported zic(8) produces a new format in the output. Please
668 run tzsetup(8) to install the newly created data to /etc/localtime.
671 The sysctl tree for the usb stack has renamed from hw.usb2.* to
672 hw.usb.* and is now consistent again with previous releases.
675 802.11 monitor mode support was revised and driver api's were changed.
676 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
677 of DLT_IEEE802_11. No user-visible data structures were changed but
678 applications that use DLT_IEEE802_11 may require changes.
679 Bump __FreeBSD_version to 800088.
682 The layout of the following structs has changed: sysctl_oid,
683 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
684 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
685 panics may be experienced. World rebuild is required for
686 correctly checking networking state from userland.
687 Bump __FreeBSD_version to 800085.
690 MLDv2 and Source-Specific Multicast (SSM) have been merged
691 to the IPv6 stack. VIMAGE hooks are in but not yet used.
692 The implementation of SSM within FreeBSD's IPv6 stack closely
693 follows the IPv4 implementation.
695 For kernel developers:
697 * The most important changes are that the ip6_output() and
698 ip6_input() paths no longer take the IN6_MULTI_LOCK,
699 and this lock has been downgraded to a non-recursive mutex.
701 * As with the changes to the IPv4 stack to support SSM, filtering
702 of inbound multicast traffic must now be performed by transport
703 protocols within the IPv6 stack. This does not apply to TCP and
704 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
706 * The KPIs used by IPv6 multicast are similar to those used by
707 the IPv4 stack, with the following differences:
708 * im6o_mc_filter() is analogous to imo_multicast_filter().
709 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
710 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
711 * IN6_LOOKUP_MULTI() has been deprecated and removed.
712 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
713 for MLDv1 have an additional 'timer' argument which is used to
714 jitter the initial membership report for the solicited-node
715 multicast membership on-link.
716 * This is not strictly needed for MLDv2, which already jitters
717 its report transmissions. However, the 'timer' argument is
718 preserved in case MLDv1 is active on the interface.
720 * The KAME linked-list based IPv6 membership implementation has
721 been refactored to use a vector similar to that used by the IPv4
723 Code which maintains a list of its own multicast memberships
724 internally, e.g. carp, has been updated to reflect the new
727 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
728 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
729 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
730 implementation constraint which needs to be addressed in HEAD.
732 For application developers:
734 * The changes are broadly similar to those made for the IPv4
737 * The use of IPv4 and IPv6 multicast socket options on the same
738 socket, using mapped addresses, HAS NOT been tested or supported.
740 * There are a number of issues with the implementation of various
741 IPv6 multicast APIs which need to be resolved in the API surface
742 before the implementation is fully compatible with KAME userland
743 use, and these are mostly to do with interface index treatment.
745 * The literature available discusses the use of either the delta / ASM
746 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
747 using setsourcefilter(3)/getsourcefilter(3). For more information
748 please refer to RFC 3768, 'Socket Interface Extensions for
749 Multicast Source Filters'.
751 * Applications which use the published RFC 3678 APIs should be fine.
753 For systems administrators:
755 * The mtest(8) utility has been refactored to support IPv6, in
756 addition to IPv4. Interface addresses are no longer accepted
757 as arguments, their names must be used instead. The utility
758 will map the interface name to its first IPv4 address as
759 returned by getifaddrs(3).
761 * The ifmcstat(8) utility has also been updated to print the MLDv2
762 endpoint state and source filter lists via sysctl(3).
764 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
765 loopback of IPv6 multicast datagrams by default; it defaults to 1
766 to preserve the existing behaviour. Disabling multicast loopback is
767 recommended for optimal system performance.
769 * The IPv6 MROUTING code has been changed to examine this sysctl
770 instead of attempting to perform a group lookup before looping
771 back forwarded datagrams.
773 Bump __FreeBSD_version to 800084.
776 Implement low-level Bluetooth HCI API.
777 Bump __FreeBSD_version to 800083.
780 The layout of struct malloc_type, used by modules to register new
781 memory allocation types, has changed. Most modules will need to
782 be rebuilt or panics may be experienced.
783 Bump __FreeBSD_version to 800081.
786 Anticipate overflowing inp_flags - add inp_flags2.
787 This changes most offsets in inpcb, so checking v4 connection
788 state will require a world rebuild.
789 Bump __FreeBSD_version to 800080.
792 Add an llentry to struct route and struct route_in6. Modules
793 embedding a struct route will need to be recompiled.
794 Bump __FreeBSD_version to 800079.
797 The size of rt_metrics_lite and by extension rtentry has changed.
798 Networking administration apps will need to be recompiled.
799 The route command now supports show as an alias for get, weighting
800 of routes, sticky and nostick flags to alter the behavior of stateful
802 Bump __FreeBSD_version to 800078.
805 Do not use Giant for kbdmux(4) locking. This is wrong and
806 apparently causing more problems than it solves. This will
807 re-open the issue where interrupt handlers may race with
808 kbdmux(4) in polling mode. Typical symptoms include (but
809 not limited to) duplicated and/or missing characters when
810 low level console functions (such as gets) are used while
811 interrupts are enabled (for example geli password prompt,
812 mountroot prompt etc.). Disabling kbdmux(4) may help.
815 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
816 kernel modules referencing any of the above need to be recompiled.
817 Bump __FreeBSD_version to 800075.
820 GEOM_PART has become the default partition slicer for storage devices,
821 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
822 introduces some changes:
824 MSDOS/EBR: the devices created from MSDOS extended partition entries
825 (EBR) can be named differently than with GEOM_MBR and are now symlinks
826 to devices with offset-based names. fstabs may need to be modified.
828 BSD: the "geometry does not match label" warning is harmless in most
829 cases but it points to problems in file system misalignment with
830 disk geometry. The "c" partition is now implicit, covers the whole
831 top-level drive and cannot be (mis)used by users.
833 General: Kernel dumps are now not allowed to be written to devices
834 whose partition types indicate they are meant to be used for file
835 systems (or, in case of MSDOS partitions, as something else than
838 Most of these changes date approximately from 200812.
841 The uscanner(4) driver has been removed from the kernel. This follows
842 Linux removing theirs in 2.6 and making libusb the default interface
846 The multicast forwarding code has been cleaned up. netstat(1)
847 only relies on KVM now for printing bandwidth upcall meters.
848 The IPv4 and IPv6 modules are split into ip_mroute_mod and
849 ip6_mroute_mod respectively. The config(5) options for statically
850 compiling this code remain the same, i.e. 'options MROUTING'.
853 Support for the IFF_NEEDSGIANT network interface flag has been
854 removed, which means that non-MPSAFE network device drivers are no
855 longer supported. In particular, if_ar, if_sr, and network device
856 drivers from the old (legacy) USB stack can no longer be built or
860 POSIX.1 Native Language Support (NLS) has been enabled in libc and
861 a bunch of new language catalog files have also been added.
862 This means that some common libc messages are now localized and
863 they depend on the LC_MESSAGES environmental variable.
866 The k8temp(4) driver has been renamed to amdtemp(4) since
867 support for Family 10 and Family 11 CPU families was added.
870 IGMPv3 and Source-Specific Multicast (SSM) have been merged
871 to the IPv4 stack. VIMAGE hooks are in but not yet used.
873 For kernel developers, the most important changes are that the
874 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
875 and this lock has been downgraded to a non-recursive mutex.
877 Transport protocols (UDP, Raw IP) are now responsible for filtering
878 inbound multicast traffic according to group membership and source
879 filters. The imo_multicast_filter() KPI exists for this purpose.
880 Transports which do not use multicast (SCTP, TCP) already reject
881 multicast by default. Forwarding and receive performance may improve
882 as a mutex acquisition is no longer needed in the ip_input()
883 low-level input path. in_addmulti() and in_delmulti() are shimmed
884 to new KPIs which exist to support SSM in-kernel.
886 For application developers, it is recommended that loopback of
887 multicast datagrams be disabled for best performance, as this
888 will still cause the lock to be taken for each looped-back
889 datagram transmission. The net.inet.ip.mcast.loop sysctl may
890 be tuned to 0 to disable loopback by default; it defaults to 1
891 to preserve the existing behaviour.
893 For systems administrators, to obtain best performance with
894 multicast reception and multiple groups, it is always recommended
895 that a card with a suitably precise hash filter is used. Hash
896 collisions will still result in the lock being taken within the
897 transport protocol input path to check group membership.
899 If deploying FreeBSD in an environment with IGMP snooping switches,
900 it is recommended that the net.inet.igmp.sendlocal sysctl remain
901 enabled; this forces 224.0.0.0/24 group membership to be announced
904 The size of 'struct igmpstat' has changed; netstat needs to be
905 recompiled to reflect this.
906 Bump __FreeBSD_version to 800070.
909 libusb20.so.1 is now installed as libusb.so.1 and the ports system
910 updated to use it. This requires a buildworld/installworld in order to
911 update the library and dependencies (usbconfig, etc). Its advisable to
912 rebuild all ports which uses libusb. More specific directions are given
913 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
914 libusb are no longer required and can be removed.
917 A workaround is committed to allow the creation of System V shared
918 memory segment of size > 2 GB on the 64-bit architectures.
919 Due to a limitation of the existing ABI, the shm_segsz member
920 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
921 wrong for large segments. Note that limits must be explicitly
922 raised to allow such segments to be created.
925 The layout of struct ifnet has changed, requiring a rebuild of all
926 network device driver modules.
929 The /dev handling for the new USB stack has changed, a
930 buildworld/installworld is required for libusb20.
933 The new USB2 stack has now been permanently moved in and all kernel and
934 module names reverted to their previous values (eg, usb, ehci, ohci,
935 ums, ...). The old usb stack can be compiled in by prefixing the name
936 with the letter 'o', the old usb modules have been removed.
937 Updating entry 20090216 for xorg and 20090215 for libmap may still
941 The rc.conf(5) option if_up_delay has been renamed to
942 defaultroute_delay to better reflect its purpose. If you have
943 customized this setting in /etc/rc.conf you need to update it to
947 xorg 7.4 wants to configure its input devices via hald which does not
948 yet work with USB2. If the keyboard/mouse does not work in xorg then
950 Option "AllowEmptyInput" "off"
951 to your ServerLayout section. This will cause X to use the configured
952 kbd and mouse sections from your xorg.conf.
955 The GENERIC kernels for all architectures now default to the new USB2
956 stack. No kernel config options or code have been removed so if a
957 problem arises please report it and optionally revert to the old USB
958 stack. If you are loading USB kernel modules or have a custom kernel
959 that includes GENERIC then ensure that usb names are also changed over,
960 eg uftdi -> usb2_serial_ftdi.
962 Older programs linked against the ports libusb 0.1 need to be
963 redirected to the new stack's libusb20. /etc/libmap.conf can
965 # Map old usb library to new one for usb2 stack
966 libusb-0.1.so.8 libusb20.so.1
969 All USB ethernet devices now attach as interfaces under the name ueN
970 (eg. ue0). This is to provide a predictable name as vendors often
971 change usb chipsets in a product without notice.
974 The ichsmb(4) driver has been changed to require SMBus slave
975 addresses be left-justified (xxxxxxx0b) rather than right-justified.
976 All of the other SMBus controller drivers require left-justified
977 slave addresses, so this change makes all the drivers provide the
981 INET6 statistics (struct ip6stat) was updated.
982 netstat(1) needs to be recompiled.
985 NTFS has been removed from GENERIC kernel on amd64 to match
986 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
987 will load ntfs.ko module automatically when NTFS support is
988 actually needed, unless ntfs.ko is not installed or security
989 level prohibits loading kernel modules. If either is the case,
990 "options NTFS" has to be added into kernel config.
993 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
994 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
995 800061. User space tools that rely on the size of struct tcpcb in
996 tcp_var.h (e.g. sockstat) need to be recompiled.
999 ng_tty(4) module updated to match the new TTY subsystem.
1000 Due to API change, user-level applications must be updated.
1001 New API support added to mpd5 CVS and expected to be present
1002 in next mpd5.3 release.
1005 With __FreeBSD_version 800060 the makefs tool is part of
1006 the base system (it was a port).
1009 The afdata and ifnet locks have been changed from mutexes to
1010 rwlocks, network modules will need to be re-compiled.
1013 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1014 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1015 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1016 architecture and 40 bytes on 64-bit architecture. The userland
1017 applications "arp" and "ndp" have been updated accordingly.
1018 The output from "netstat -r" shows only routing entries and
1019 none of the L2 information.
1022 __FreeBSD_version 800057 marks the switchover from the
1023 binary ath hal to source code. Users must add the line:
1025 options AH_SUPPORT_AR5416
1027 to their kernel config files when specifying:
1031 The ath_hal module no longer exists; the code is now compiled
1032 together with the driver in the ath module. It is now
1033 possible to tailor chip support (i.e. reduce the set of chips
1034 and thereby the code size); consult ath_hal(4) for details.
1037 __FreeBSD_version 800054 adds memory barriers to
1038 <machine/atomic.h>, new interfaces to ifnet to facilitate
1039 multiple hardware transmit queues for cards that support
1040 them, and a lock-less ring-buffer implementation to
1041 enable drivers to more efficiently manage queueing of
1045 A new version of ZFS (version 13) has been merged to -HEAD.
1046 This version has zpool attribute "listsnapshots" off by
1047 default, which means "zfs list" does not show snapshots,
1048 and is the same as Solaris behavior.
1051 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1054 The uhci, ohci, ehci and slhci USB Host controller drivers have
1055 been put into separate modules. If you load the usb module
1056 separately through loader.conf you will need to load the
1057 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1058 controller add the following to loader.conf:
1064 The ABI used by the PMC toolset has changed. Please keep
1065 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1069 atapci kernel module now includes only generic PCI ATA
1070 driver. AHCI driver moved to ataahci kernel module.
1071 All vendor-specific code moved into separate kernel modules:
1072 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1073 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1074 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1075 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1078 The TTY subsystem of the kernel has been replaced by a new
1079 implementation, which provides better scalability and an
1080 improved driver model. Most common drivers have been migrated to
1081 the new TTY subsystem, while others have not. The following
1082 drivers have not yet been ported to the new TTY layer:
1085 cy, digi, rc, rp, sio
1091 ng_h4, ng_tty, ppp, sl, snp
1093 Adding these drivers to your kernel configuration file shall
1094 cause compilation to fail.
1097 ntpd has been upgraded to 4.2.4p5.
1100 OpenSSH has been upgraded to 5.1p1.
1102 For many years, FreeBSD's version of OpenSSH preferred DSA
1103 over RSA for host and user authentication keys. With this
1104 upgrade, we've switched to the vendor's default of RSA over
1105 DSA. This may cause upgraded clients to warn about unknown
1106 host keys even for previously known hosts. Users should
1107 follow the usual procedure for verifying host keys before
1108 accepting the RSA key.
1110 This can be circumvented by setting the "HostKeyAlgorithms"
1111 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1114 Please note that the sequence of keys offered for
1115 authentication has been changed as well. You may want to
1116 specify IdentityFile in a different order to revert this
1120 The sio(4) driver has been removed from the i386 and amd64
1121 kernel configuration files. This means uart(4) is now the
1122 default serial port driver on those platforms as well.
1124 To prevent collisions with the sio(4) driver, the uart(4) driver
1125 uses different names for its device nodes. This means the
1126 onboard serial port will now most likely be called "ttyu0"
1127 instead of "ttyd0". You may need to reconfigure applications to
1128 use the new device names.
1130 When using the serial port as a boot console, be sure to update
1131 /boot/device.hints and /etc/ttys before booting the new kernel.
1132 If you forget to do so, you can still manually specify the hints
1133 at the loader prompt:
1135 set hint.uart.0.at="isa"
1136 set hint.uart.0.port="0x3F8"
1137 set hint.uart.0.flags="0x10"
1138 set hint.uart.0.irq="4"
1142 The gpt(8) utility has been removed. Use gpart(8) to partition
1146 The version that Linuxulator emulates was changed from 2.4.2
1147 to 2.6.16. If you experience any problems with Linux binaries
1148 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1149 if it fixes the problem contact emulation mailing list.
1152 ISDN4BSD (I4B) was removed from the src tree. You may need to
1153 update a your kernel configuration and remove relevant entries.
1156 I have checked in code to support multiple routing tables.
1157 See the man pages setfib(1) and setfib(2).
1158 This is a hopefully backwards compatible version,
1159 but to make use of it you need to compile your kernel
1160 with options ROUTETABLES=2 (or more up to 16).
1163 The 802.11 wireless support was redone to enable multi-bss
1164 operation on devices that are capable. The underlying device
1165 is no longer used directly but instead wlanX devices are
1166 cloned with ifconfig. This requires changes to rc.conf files.
1167 For example, change:
1168 ifconfig_ath0="WPA DHCP"
1171 ifconfig_wlan0="WPA DHCP"
1172 see rc.conf(5) for more details. In addition, mergemaster of
1173 /etc/rc.d is highly recommended. Simultaneous update of userland
1174 and kernel wouldn't hurt either.
1176 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1177 modules were merged into the base wlan module. All references
1178 to these modules (e.g. in kernel config files) must be removed.
1181 psm(4) has gained write(2) support in native operation level.
1182 Arbitrary commands can be written to /dev/psm%d and status can
1183 be read back from it. Therefore, an application is responsible
1184 for status validation and error recovery. It is a no-op in
1185 other operation levels.
1188 Support for KSE threading has been removed from the kernel. To
1189 run legacy applications linked against KSE libmap.conf may
1190 be used. The following libmap.conf may be used to ensure
1191 compatibility with any prior release:
1193 libpthread.so.1 libthr.so.1
1194 libpthread.so.2 libthr.so.2
1195 libkse.so.3 libthr.so.3
1198 The layout of struct vmspace has changed. This affects libkvm
1199 and any executables that link against libkvm and use the
1200 kvm_getprocs() function. In particular, but not exclusively,
1201 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1202 The effects are minimal, but it's advisable to upgrade world
1206 The latest em driver no longer has support in it for the
1207 82575 adapter, this is now moved to the igb driver. The
1208 split was done to make new features that are incompatible
1209 with older hardware easier to do.
1212 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1213 likewise the kernel option is now GEOM_LINUX_LVM.
1216 The default NFS mount mode has changed from UDP to TCP for
1217 increased reliability. If you rely on (insecurely) NFS
1218 mounting across a firewall you may need to update your
1222 Belatedly note the addition of m_collapse for compacting
1226 The fts(3) structures have been changed to use adequate
1227 integer types for their members and so to be able to cope
1228 with huge file trees. The old fts(3) ABI is preserved
1229 through symbol versioning in libc, so third-party binaries
1230 using fts(3) should still work, although they will not take
1231 advantage of the extended types. At the same time, some
1232 third-party software might fail to build after this change
1233 due to unportable assumptions made in its source code about
1234 fts(3) structure members. Such software should be fixed
1235 by its vendor or, in the worst case, in the ports tree.
1236 FreeBSD_version 800015 marks this change for the unlikely
1237 case that a portable fix is impossible.
1240 To upgrade to -current after this date, you must be running
1241 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1242 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1245 The ADAPTIVE_GIANT kernel option has been retired because its
1246 functionality is the default now.
1249 The AT keyboard emulation of sunkbd(4) has been turned on
1250 by default. In order to make the special symbols of the Sun
1251 keyboards driven by sunkbd(4) work under X these now have
1252 to be configured the same way as Sun USB keyboards driven
1253 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1255 Option "XkbLayout" "us"
1256 Option "XkbRules" "xorg"
1257 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1260 It has been decided that it is desirable to provide ABI
1261 backwards compatibility to the FreeBSD 4/5/6 versions of the
1262 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1263 broken with the introduction of PCI domain support (see the
1264 20070930 entry). Unfortunately, this required the ABI of
1265 PCIOCGETCONF to be broken again in order to be able to
1266 provide backwards compatibility to the old version of that
1267 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1268 again. As for prominent ports this affects neither pciutils
1269 nor xorg-server this time, the hal port needs to be rebuilt
1273 The misnamed kthread_create() and friends have been renamed
1274 to kproc_create() etc. Many of the callers already
1275 used kproc_start()..
1276 I will return kthread_create() and friends in a while
1277 with implementations that actually create threads, not procs.
1278 Renaming corresponds with version 800002.
1287 Avoid using make -j when upgrading. While generally safe, there are
1288 sometimes problems using -j to upgrade. If your upgrade fails with
1289 -j, please try again without -j. From time to time in the past there
1290 have been problems using -j with buildworld and/or installworld. This
1291 is especially true when upgrading between "distant" versions (eg one
1292 that cross a major release boundary or several minor releases, or when
1293 several months have passed on the -current branch).
1295 Sometimes, obscure build problems are the result of environment
1296 poisoning. This can happen because the make utility reads its
1297 environment when searching for values for global variables. To run
1298 your build attempts in an "environmental clean room", prefix all make
1299 commands with 'env -i '. See the env(1) manual page for more details.
1301 When upgrading from one major version to another it is generally best
1302 to upgrade to the latest code in the currently installed branch first,
1303 then do an upgrade to the new branch. This is the best-tested upgrade
1304 path, and has the highest probability of being successful. Please try
1305 this approach before reporting problems with a major version upgrade.
1309 When upgrading the boot ZFS pool to a new version, always follow
1312 1.) recompile and reinstall the ZFS boot loader and boot block
1313 (this is part of "make buildworld" and "make installworld")
1315 2.) update the ZFS boot block on your boot drive
1317 The following example updates the ZFS boot block on the first
1318 partition (freebsd-boot) of a GPT partitioned drive ad0:
1319 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1321 Non-boot pools do not need these updates.
1325 If you are updating from a prior version of FreeBSD (even one just
1326 a few days old), you should follow this procedure. It is the most
1327 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1329 make kernel-toolchain
1330 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1331 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1333 To test a kernel once
1334 ---------------------
1335 If you just want to boot a kernel once (because you are not sure
1336 if it works, or if you want to boot a known bad kernel to provide
1337 debugging information) run
1338 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1339 nextboot -k testkernel
1341 To just build a kernel when you know that it won't mess you up
1342 --------------------------------------------------------------
1343 This assumes you are already running a CURRENT system. Replace
1344 ${arch} with the architecture of your machine (e.g. "i386",
1345 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1347 cd src/sys/${arch}/conf
1348 config KERNEL_NAME_HERE
1349 cd ../compile/KERNEL_NAME_HERE
1354 If this fails, go to the "To build a kernel" section.
1356 To rebuild everything and install it on the current system.
1357 -----------------------------------------------------------
1358 # Note: sometimes if you are running current you gotta do more than
1359 # is listed here if you are upgrading from a really old current.
1361 <make sure you have good level 0 dumps>
1363 make kernel KERNCONF=YOUR_KERNEL_HERE
1365 <reboot in single user> [3]
1373 To cross-install current onto a separate partition
1374 --------------------------------------------------
1375 # In this approach we use a separate partition to hold
1376 # current's root, 'usr', and 'var' directories. A partition
1377 # holding "/", "/usr" and "/var" should be about 2GB in
1380 <make sure you have good level 0 dumps>
1383 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1384 <maybe newfs current's root partition>
1385 <mount current's root partition on directory ${CURRENT_ROOT}>
1386 make installworld DESTDIR=${CURRENT_ROOT}
1387 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1388 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1389 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1390 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1391 <reboot into current>
1392 <do a "native" rebuild/install as described in the previous section>
1393 <maybe install compatibility libraries from ports/misc/compat*>
1397 To upgrade in-place from 8.x-stable to current
1398 ----------------------------------------------
1399 <make sure you have good level 0 dumps>
1401 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1403 <reboot in single user> [3]
1410 Make sure that you've read the UPDATING file to understand the
1411 tweaks to various things you need. At this point in the life
1412 cycle of current, things change often and you are on your own
1413 to cope. The defaults can also change, so please read ALL of
1414 the UPDATING entries.
1416 Also, if you are tracking -current, you must be subscribed to
1417 freebsd-current@freebsd.org. Make sure that before you update
1418 your sources that you have read and understood all the recent
1419 messages there. If in doubt, please track -stable which has
1420 much fewer pitfalls.
1422 [1] If you have third party modules, such as vmware, you
1423 should disable them at this point so they don't crash your
1426 [3] From the bootblocks, boot -s, and then do
1431 adjkerntz -i # if CMOS is wall time
1432 Also, when doing a major release upgrade, it is required that
1433 you boot into single user mode to do the installworld.
1435 [4] Note: This step is non-optional. Failure to do this step
1436 can result in a significant reduction in the functionality of the
1437 system. Attempting to do it by hand is not recommended and those
1438 that pursue this avenue should read this file carefully, as well
1439 as the archives of freebsd-current and freebsd-hackers mailing lists
1440 for potential gotchas. The -U option is also useful to consider.
1441 See mergemaster(8) for more information.
1443 [5] Usually this step is a noop. However, from time to time
1444 you may need to do this if you get unknown user in the following
1445 step. It never hurts to do it all the time. You may need to
1446 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1447 install) after the buildworld before this step if you last updated
1448 from current before 20020224 or from -stable before 20020408.
1450 [6] This only deletes old files and directories. Old libraries
1451 can be deleted by "make delete-old-libs", but you have to make
1452 sure that no program is using those libraries anymore.
1454 [8] In order to have a kernel that can run the 4.x binaries needed to
1455 do an installworld, you must include the COMPAT_FREEBSD4 option in
1456 your kernel. Failure to do so may leave you with a system that is
1457 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1458 required to run the 5.x binaries on more recent kernels. And so on
1459 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1461 Make sure that you merge any new devices from GENERIC since the
1462 last time you updated your kernel config file.
1464 [9] When checking out sources, you must include the -P flag to have
1465 cvs prune empty directories.
1467 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1468 "?=" instead of the "=" assignment operator, so that buildworld can
1469 override the CPUTYPE if it needs to.
1471 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1472 not on the command line, or in /etc/make.conf. buildworld will
1473 warn if it is improperly defined.
1476 This file contains a list, in reverse chronological order, of major
1477 breakages in tracking -current. It is not guaranteed to be a complete
1478 list of such breakages, and only contains entries since October 10, 2007.
1479 If you need to see UPDATING entries from before that date, you will need
1480 to fetch an UPDATING file from an older FreeBSD release.
1482 Copyright information:
1484 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1486 Redistribution, publication, translation and use, with or without
1487 modification, in full or in part, in any form or format of this
1488 document are permitted without further permission from the author.
1490 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1491 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1492 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1493 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1494 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1495 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1496 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1497 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1498 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1499 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1500 POSSIBILITY OF SUCH DAMAGE.
1502 Contact Warner Losh if you have any questions about your use of