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 20120530: p2 FreeBSD-SA-12:01.openssl (revised),
13 FreeBSD-SA-12:02.crypt
14 Update the previous openssl fix. [12:01]
16 Fix a bug in crypt(3) ignoring characters of a passphrase. [12:02]
18 20120503: p1 FreeBSD-SA-12:01.openssl
19 Fix multiple OpenSSL vulnerabilities.
25 The broken amd(4) driver has been replaced with esp(4) in the amd64,
26 i386 and pc98 GENERIC kernel configuration files.
29 This commit modifies vfs_register() so that it uses a hash
30 calculation to set vfc_typenum, which is enabled by default.
31 The first time a system is booted after this change, the
32 vfc_typenum values will change for all file systems. The
33 main effect of this is a change to the NFS server file handles
34 for file systems that use vfc_typenum in their fsid, such as ZFS.
35 It will, however, prevent vfc_typenum from changing when file
36 systems are loaded in a different order for subsequent reboots.
37 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
38 until you are ready to remount all NFS clients after a reboot.
41 Bump the shared library version numbers for libraries that
42 do not use symbol versioning, have changed the ABI compared
43 to stable/8 and which shared library version was not bumped.
44 Done as part of 9.0-RELEASE cycle.
47 During the merge of Capsicum features, the fget(9) KPI was modified.
48 This may require the rebuilding of out-of-tree device drivers --
49 issues have been reported specifically with the nVidia device driver.
50 __FreeBSD_version is bumped to 900041.
52 Also, there is a period between 20110811 and 20110814 where the
53 special devices /dev/{stdin,stdout,stderr} did not work correctly.
54 Building world from a kernel during that window may not work.
57 The packet filter (pf) code has been updated to OpenBSD 4.5.
58 You need to update userland tools to be in sync with kernel.
59 This update breaks backward compatibility with earlier pfsync(4)
60 versions. Care must be taken when updating redundant firewall setups.
63 The following sysctls and tunables are retired on x86 platforms:
65 machdep.hlt_logical_cpus
66 The following sysctl is retired:
67 machdep.hyperthreading_allowed
68 The sysctls were supposed to provide a way to dynamically offline and
69 online selected CPUs on x86 platforms, but the implementation has not
70 been reliable especially with SCHED_ULE scheduler.
71 machdep.hyperthreading_allowed tunable is still available to ignore
72 hyperthreading CPUs at OS level.
73 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
74 where X is an APIC ID of a CPU. Be advised, though, that disabling
75 CPUs in non-uniform fashion will result in non-uniform topology and
76 may lead to sub-optimal system performance with SCHED_ULE, which is
80 cpumask_t type is retired and cpuset_t is used in order to describe
84 Changes to ifconfig(8) for dynamic address family detection mandate
85 that you are running a kernel of 20110525 or later. Make sure to
86 follow the update procedure to boot a new kernel before installing
90 Support for sun4v architecture is officially dropped
93 Several KPI breaking changes have been committed to the mii(4) layer,
94 the PHY drivers and consequently some Ethernet drivers using mii(4).
95 This means that miibus.ko and the modules of the affected Ethernet
96 drivers need to be recompiled.
98 Note to kernel developers: Given that the OUI bit reversion problem
99 was fixed as part of these changes all mii(4) commits related to OUIs,
100 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
101 handling, no longer can be merged verbatim to stable/8 and previous
105 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
106 into their kernel configurations along with 'device pci'.
109 The default NFS client is now the new NFS client, so fstype "newnfs"
110 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
111 Although mounts via fstype "nfs" will usually work without userland
112 changes, it is recommended that the mount(8) and mount_nfs(8)
113 commands be rebuilt from sources and that a link to mount_nfs called
114 mount_oldnfs be created. The new client is compiled into the
115 kernel with "options NFSCL" and this is needed for diskless root
116 file systems. The GENERIC kernel configs have been changed to use
117 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
118 To use the regular/old client, you can "mount -t oldnfs ...". For
119 a diskless root file system, you must also include a line like:
121 vfs.root.mountfrom="oldnfs:"
123 in the boot/loader.conf on the root fs on the NFS server to make
124 a diskless root fs use the old client.
127 The GENERIC kernels for all architectures now default to the new
128 CAM-based ATA stack. It means that all legacy ATA drivers were
129 removed and replaced by respective CAM drivers. If you are using
130 ATA device names in /etc/fstab or other places, make sure to update
131 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
132 where 'Y's are the sequential numbers starting from zero for each type
133 in order of detection, unless configured otherwise with tunables,
134 see cam(4)). There will be symbolic links created in /dev/ to map
135 old adX devices to the respective adaY. They should provide basic
136 compatibility for file systems mounting in most cases, but they do
137 not support old user-level APIs and do not have respective providers
138 in GEOM. Consider using updated management tools with new device names.
140 It is possible to load devices ahci, ata, siis and mvs as modules,
141 but option ATA_CAM should remain in kernel configuration to make ata
142 module work as CAM driver supporting legacy ATA controllers. Device ata
143 still can be used in modular fashion (atacore + ...). Modules atadisk
144 and atapi* are not used and won't affect operation in ATA_CAM mode.
145 Note that to use CAM-based ATA kernel should include CAM devices
146 scbus, pass, da (or explicitly ada), cd and optionally others. All of
147 them are parts of the cam module.
149 ataraid(4) functionality is now supported by the RAID GEOM class.
150 To use it you can load geom_raid kernel module and use graid(8) tool
151 for management. Instead of /dev/arX device names, use /dev/raid/rX.
153 No kernel config options or code have been removed, so if a problem
154 arises, please report it and optionally revert to the old ATA stack.
155 In order to do it you can remove from the kernel config:
160 , and instead add back:
161 device atadisk # ATA disk drives
162 device ataraid # ATA RAID drives
163 device atapicd # ATAPI CDROM drives
164 device atapifd # ATAPI floppy drives
165 device atapist # ATAPI tape drives
168 The default NFS server has been changed to the new server, which
169 was referred to as the experimental server. If you need to switch
170 back to the old NFS server, you must now put the "-o" option on
171 both the mountd and nfsd commands. This can be done using the
172 mountd_flags and nfs_server_flags rc.conf variables until an
173 update to the rc scripts is committed, which is coming soon.
176 The GNU Objective-C runtime library (libobjc), and other Objective-C
177 related components have been removed from the base system. If you
178 require an Objective-C library, please use one of the available ports.
181 ath(4) has been split into bus- and device- modules. if_ath contains
182 the HAL, the TX rate control and the network device code. if_ath_pci
183 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
184 contains the AHB glue. Users need to load both if_ath_pci and if_ath
185 in order to use ath on everything else.
187 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
188 need to load if_ath and if_ath_pci for ath(4) operation.
191 As part of the replacement of sysinstall, the process of building
192 release media has changed significantly. For details, please re-read
193 release(7), which has been updated to reflect the new build process.
196 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
197 is the last available version under GPLv2. It brings a number of new
198 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
199 4.1 and SSE 4.2), better support for powerpc64, a number of new
200 directives, and lots of other small improvements. See the ChangeLog
201 file in contrib/binutils for the full details.
204 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
205 compliant, and will now use half of hash for authentication.
206 This will break interoperability with all stacks (including all
207 actual FreeBSD versions) who implement
208 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
210 The only workaround with such peers is to use another HMAC
211 algorithm for IPsec ("phase 2") authentication.
214 Remove the uio_yield prototype and symbol. This function has
215 been misnamed since it was introduced and should not be
216 globally exposed with this name. The equivalent functionality
217 is now available using kern_yield(curthread->td_user_pri).
218 The function remains undocumented.
221 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
222 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
223 for scalar sysctls is defined but disabled. Code that needs
224 UQUAD to pass the type checking that must compile on older
225 systems where the define is not present can check against
226 __FreeBSD_version >= 900030.
228 The system dialog(1) has been replaced with a new version previously
229 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
230 with the previous version, but the libdialog associated with it has
231 a largely incompatible API. As such, the original version of libdialog
232 will be kept temporarily as libodialog, until its base system consumers
233 are replaced or updated. Bump __FreeBSD_version to 900030.
236 If you are trying to run make universe on a -stable system, and you get
237 the following warning:
238 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
239 unknown. config(8) likely too old."
240 or something similar to it, then you must upgrade your -stable system
241 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
242 stable/8) or build the config from the latest stable/8 branch and
243 install it on your system.
245 Prior to this date, building a current universe on 8-stable system from
246 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
247 error in the first kernel build phase. A new config on those old
248 systems will fix that problem for older versions of -current.
251 The TCP stack has been modified to allow Khelp modules to interact with
252 it via helper hook points and store per-connection data in the TCP
253 control block. Bump __FreeBSD_version to 900029. User space tools that
254 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
258 Generic IEEE 802.3 annex 31B full duplex flow control support has been
259 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
260 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
261 to take advantage of it instead of using custom implementations. This
262 means that these drivers now no longer unconditionally advertise
263 support for flow control but only do so if flow control is a selected
264 media option. This was implemented in the generic support that way in
265 order to allow flow control to be switched on and off via ifconfig(8)
266 with the PHY specific default to typically off in order to protect
267 from unwanted effects. Consequently, if you used flow control with
268 one of the above mentioned drivers you now need to explicitly enable
270 ifconfig bge0 media auto mediaopt flowcontrol
272 Along with the above mentioned changes generic support for setting
273 1000baseT master mode also has been added and brgphy(4), ciphy(4),
274 e1000phy(4) as well as ip1000phy(4) have been converted to take
275 advantage of it. This means that these drivers now no longer take the
276 link0 parameter for selecting master mode but the master media option
277 has to be used instead, for example like in the following:
278 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
280 Selection of master mode now is also available with all other PHY
281 drivers supporting 1000baseT.
284 The TCP stack has received a significant update to add support for
285 modularised congestion control and generally improve the clarity of
286 congestion control decisions. Bump __FreeBSD_version to 900025. User
287 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
288 sockstat) need to be recompiled.
291 The man(1) utility has been replaced by a new version that no longer
292 uses /etc/manpath.config. Please consult man.conf(5) for how to
293 migrate local entries to the new format.
296 The copyright strings printed by login(1) and sshd(8) at the time of a
297 new connection have been removed to follow other operating systems and
301 A workaround for a fixed ld bug has been removed in kernel code,
302 so make sure that your system ld is built from sources after
303 revision 210245 from 2010-07-19 (r211583 if building head kernel
304 on stable/8, r211584 for stable/7; both from 2010-08-21).
305 A symptom of incorrect ld version is different addresses for
306 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
309 The $ipv6_prefer variable in rc.conf(5) has been split into
310 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
312 The $ip6addrctl_policy is a variable to choose a pre-defined
313 address selection policy set by ip6addrctl(8). A value
314 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
317 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
318 flag (see an entry of 20090926) is set on an interface with no
319 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
320 security reason. If you want IPv6 link-local address on all
321 interfaces by default, set this to "YES".
323 The old ipv6_prefer="YES" is equivalent to
324 ipv6_activate_all_interfaces="YES" and
325 ip6addrctl_policy="ipv6_prefer".
328 DTrace has grown support for userland tracing. Due to this, DTrace is
329 now i386 and amd64 only.
330 dtruss(1) is now installed by default on those systems and a new
331 kernel module is needed for userland tracing: fasttrap.
332 No changes to your kernel config file are necessary to enable
333 userland tracing, but you might consider adding 'STRIP=' and
334 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
335 to have informative userland stack traces in DTrace (ustack).
338 The acpi_aiboost(4) driver has been removed in favor of the new
339 aibs(4) driver. You should update your kernel configuration file.
342 BSD grep has been imported to the base system and it is built by
343 default. It is completely BSD licensed, highly GNU-compatible, uses
344 less memory than its GNU counterpart and has a small codebase.
345 However, it is slower than its GNU counterpart, which is mostly
346 noticeable for larger searches, for smaller ones it is measurable
347 but not significant. The reason is complex, the most important factor
348 is that we lack a modern and efficient regex library and GNU
349 overcomes this by optimizing the searches internally. Future work
350 on improving the regex performance is planned, for the meantime,
351 users that need better performance, can build GNU grep instead by
352 setting the WITH_GNU_GREP knob.
355 Due to the import of powerpc64 support, all existing powerpc kernel
356 configuration files must be updated with a machine directive like this:
357 machine powerpc powerpc
359 In addition, an updated config(8) is required to build powerpc kernels
363 A new version of ZFS (version 15) has been merged to -HEAD.
364 This version uses a python library for the following subcommands:
365 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
366 For full functionality of these commands the following port must
367 be installed: sysutils/py-zfs
370 'vm_page's are now hashed by physical address to an array of mutexes.
371 Currently this is only used to serialize access to hold_count. Over
372 time the page queue mutex will be peeled away. This changes the size
373 of pmap on every architecture. And requires all callers of vm_page_hold
374 and vm_page_unhold to be updated.
377 WITH_CTF can now be specified in src.conf (not recommended, there
378 are some problems with static executables), make.conf (would also
379 affect ports which do not use GNU make and do not override the
380 compile targets) or in the kernel config (via "makeoptions
382 When WITH_CTF was specified there before this was silently ignored,
383 so make sure that WITH_CTF is not used in places which could lead
384 to unwanted behavior.
387 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
388 to allow 32-bit compatibility on non-x86 platforms. All kernel
389 configurations on amd64 and ia64 platforms using these options must
390 be modified accordingly.
393 The utmp user accounting database has been replaced with utmpx,
394 the user accounting interface standardized by POSIX.
395 Unfortunately the semantics of utmp and utmpx don't match,
396 making it practically impossible to support both interfaces.
397 The user accounting database is used by tools like finger(1),
398 last(1), talk(1), w(1) and ac(8).
400 All applications in the base system use utmpx. This means only
401 local binaries (e.g. from the ports tree) may still use these
402 utmp database files. These applications must be rebuilt to make
405 After the system has been upgraded, it is safe to remove the old
406 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
407 assuming their contents is of no importance anymore. Old wtmp
408 databases can only be used by last(1) and ac(8) after they have
409 been converted to the new format using wtmpcvt(1).
412 Introduce the kernel thread "deadlock resolver" (which can be enabled
413 via the DEADLKRES option, see NOTES for more details) and the
414 sleepq_type() function for sleepqueues.
417 The rc.firewall and rc.firewall6 were unified, and
418 rc.firewall6 and rc.d/ip6fw were removed.
419 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
420 variables are obsoleted. Instead, the following new rc
421 variables are added to rc.d/ipfw:
423 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
424 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
425 firewall_simple_onet_ipv6, firewall_trusted_ipv6
427 The meanings correspond to the relevant IPv4 variables.
433 The default terminal emulation for syscons(4) has been changed
434 from cons25 to xterm on all platforms except pc98. This means
435 that the /etc/ttys file needs to be updated to ensure correct
436 operation of applications on the console.
438 The terminal emulation style can be toggled per window by using
439 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
440 options can be used to change the compile-time default back to
443 To prevent graphical artifacts, make sure the TERM environment
444 variable is set to match the terminal emulation that is being
445 performed by syscons(4).
448 The layout of the structure ieee80211req_scan_result has changed.
449 Applications that require wireless scan results (e.g. ifconfig(8))
450 from net80211 need to be recompiled.
452 Applications such as wpa_supplicant(8) may require a full world
453 build without using NO_CLEAN in order to get synchronized with the
457 The iwn(4) driver has been updated to support the 5000 and 5150 series.
458 There's one kernel module for each firmware. Adding "device iwnfw"
459 to the kernel configuration file means including all three firmware
460 images inside the kernel. If you want to include just the one for
461 your wireless card, use the the devices iwn4965fw, iwn5000fw or
465 The rc.d/network_ipv6, IPv6 configuration script has been integrated
466 into rc.d/netif. The changes are the following:
468 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
469 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
470 Note that both variables need the "inet6" keyword at the head.
472 Do not set $ipv6_network_interfaces manually if you do not
473 understand what you are doing. It is not needed in most cases.
475 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
478 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
479 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
481 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
482 all configured interfaces have "inet6 accept_rtadv" in the
483 $ifconfig_IF_ipv6. These are for backward compatibility.
485 3. A new variable $ipv6_prefer has been added. If NO, IPv6
486 functionality of interfaces with no corresponding
487 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
488 and the default address selection policy of ip6addrctl(8)
489 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
490 Note that if you want to configure IPv6 functionality on the
491 disabled interfaces after boot, first you need to clear the flag by
492 using ifconfig(8) like:
494 ifconfig em0 inet6 -ifdisabled
496 If YES, the default address selection policy is set as
499 The default value of $ipv6_prefer is NO.
501 4. If your system need to receive Router Advertisement messages,
502 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
503 scripts automatically invoke rtsol(8) when the interface becomes
504 UP. The Router Advertisement messages are used for SLAAC
505 (State-Less Address AutoConfiguration).
508 802.11s D3.03 support was committed. This is incompatible with the
509 previous code, which was based on D3.0.
512 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
513 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
514 control whether accepting Router Advertisement messages or not.
515 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
516 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
517 The ifconfig(8) utility now supports these flags.
520 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
521 mount(8) and -a option for df(1) to see them.
524 The old tunable hw.bus.devctl_disable has been superseded by
525 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
526 replaced by hw.bus.devctl_queue=0. The default for this new tunable
530 Remove the option STOP_NMI. The default action is now to use NMI only
531 for KDB via the newly introduced function stop_cpus_hard() and
532 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
535 The stable/8 branch created in subversion. This corresponds to the
536 RELENG_8 branch in CVS.
539 Bump the shared library version numbers for all libraries that do not
540 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
541 __FreeBSD_version to 800105.
544 Due to changes in the implementation of virtual network stack support,
545 all network-related kernel modules must be recompiled. As this change
546 breaks the ABI, bump __FreeBSD_version to 800104.
549 The TOE interface to the TCP syncache has been modified to remove
550 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
551 The cxgb driver is the only TOE consumer affected by this change, and
552 needs to be recompiled along with the kernel. As this change breaks
553 the ABI, bump __FreeBSD_version to 800103.
556 Padding has been added to struct tcpcb, sackhint and tcpstat in
557 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
558 maintaining the ABI. However, this change breaks the ABI, so bump
559 __FreeBSD_version to 800102. User space tools that rely on the size of
560 any of these structs (e.g. sockstat) need to be recompiled.
563 The NFS_LEGACYRPC option has been removed along with the old kernel
564 RPC implementation that this option selected. Kernel configurations
565 may need to be adjusted.
568 The network interface device nodes at /dev/net/<interface> have been
569 removed. All ioctl operations can be performed the normal way using
570 routing sockets. The kqueue functionality can generally be replaced
571 with routing sockets.
574 The documentation from the FreeBSD Documentation Project (Handbook,
575 FAQ, etc.) is now installed via packages by sysinstall(8) and under
576 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
579 The ABI of various structures related to the SYSV IPC API have been
580 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
581 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
585 Layout of struct vnet has changed as routing related variables were
586 moved to their own Vimage module. Modules need to be recompiled. Bump
587 __FreeBSD_version to 800099.
590 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
591 respectively. As long as no more than 16 groups per process are used,
592 no changes should be visible. When more than 16 groups are used, old
593 binaries may fail if they call getgroups() or getgrouplist() with
594 statically sized storage. Recompiling will work around this, but
595 applications should be modified to use dynamically allocated storage
596 for group arrays as POSIX.1-2008 does not cap an implementation's
597 number of supported groups at NGROUPS_MAX+1 as previous versions did.
599 NFS and portalfs mounts may also be affected as the list of groups is
600 truncated to 16. Users of NFS who use more than 16 groups, should
601 take care that negative group permissions are not used on the exported
602 file systems as they will not be reliable unless a GSSAPI based
603 authentication method is used.
606 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
607 option compiles in the support for adaptive spinning for lockmgrs
608 which want to enable it. The lockinit() function now accepts the flag
609 LK_ADAPTIVE in order to make the lock object subject to adaptive
610 spinning when both held in write and read mode.
613 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
614 changed. User applications that use this ioctl need to be rebuilt.
617 The layout of struct thread has changed. Kernel and modules need to
621 The layout of structs ifnet, domain, protosw and vnet_net has changed.
622 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
625 window(1) has been removed from the base system. It can now be
626 installed from ports. The port is called misc/window.
629 The way we are storing and accessing `routing table' entries has
630 changed. Programs reading the FIB, like netstat, need to be
634 A new netisr implementation has been added for FreeBSD 8. Network
635 file system modules, such as igmp, ipdivert, and others, should be
637 Bump __FreeBSD_version to 800096.
640 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
644 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
645 Bump __FreeBSD_version to 800094.
648 Add mnt_xflag field to 'struct mount'. File system modules need to be
650 Bump __FreeBSD_version to 800093.
653 The compiling option ADAPTIVE_SX has been retired while it has been
654 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
655 The KPI for sx_init_flags() changes as accepting flags:
656 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
657 been introduced in order to handle the reversed logic.
658 Bump __FreeBSD_version to 800092.
661 Add support for hierarchical jails. Remove global securelevel.
662 Bump __FreeBSD_version to 800091.
665 The layout of struct vnet_net has changed, therefore modules
667 Bump __FreeBSD_version to 800090.
670 The newly imported zic(8) produces a new format in the output. Please
671 run tzsetup(8) to install the newly created data to /etc/localtime.
674 The sysctl tree for the usb stack has renamed from hw.usb2.* to
675 hw.usb.* and is now consistent again with previous releases.
678 802.11 monitor mode support was revised and driver api's were changed.
679 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
680 of DLT_IEEE802_11. No user-visible data structures were changed but
681 applications that use DLT_IEEE802_11 may require changes.
682 Bump __FreeBSD_version to 800088.
685 The layout of the following structs has changed: sysctl_oid,
686 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
687 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
688 panics may be experienced. World rebuild is required for
689 correctly checking networking state from userland.
690 Bump __FreeBSD_version to 800085.
693 MLDv2 and Source-Specific Multicast (SSM) have been merged
694 to the IPv6 stack. VIMAGE hooks are in but not yet used.
695 The implementation of SSM within FreeBSD's IPv6 stack closely
696 follows the IPv4 implementation.
698 For kernel developers:
700 * The most important changes are that the ip6_output() and
701 ip6_input() paths no longer take the IN6_MULTI_LOCK,
702 and this lock has been downgraded to a non-recursive mutex.
704 * As with the changes to the IPv4 stack to support SSM, filtering
705 of inbound multicast traffic must now be performed by transport
706 protocols within the IPv6 stack. This does not apply to TCP and
707 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
709 * The KPIs used by IPv6 multicast are similar to those used by
710 the IPv4 stack, with the following differences:
711 * im6o_mc_filter() is analogous to imo_multicast_filter().
712 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
713 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
714 * IN6_LOOKUP_MULTI() has been deprecated and removed.
715 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
716 for MLDv1 have an additional 'timer' argument which is used to
717 jitter the initial membership report for the solicited-node
718 multicast membership on-link.
719 * This is not strictly needed for MLDv2, which already jitters
720 its report transmissions. However, the 'timer' argument is
721 preserved in case MLDv1 is active on the interface.
723 * The KAME linked-list based IPv6 membership implementation has
724 been refactored to use a vector similar to that used by the IPv4
726 Code which maintains a list of its own multicast memberships
727 internally, e.g. carp, has been updated to reflect the new
730 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
731 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
732 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
733 implementation constraint which needs to be addressed in HEAD.
735 For application developers:
737 * The changes are broadly similar to those made for the IPv4
740 * The use of IPv4 and IPv6 multicast socket options on the same
741 socket, using mapped addresses, HAS NOT been tested or supported.
743 * There are a number of issues with the implementation of various
744 IPv6 multicast APIs which need to be resolved in the API surface
745 before the implementation is fully compatible with KAME userland
746 use, and these are mostly to do with interface index treatment.
748 * The literature available discusses the use of either the delta / ASM
749 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
750 using setsourcefilter(3)/getsourcefilter(3). For more information
751 please refer to RFC 3768, 'Socket Interface Extensions for
752 Multicast Source Filters'.
754 * Applications which use the published RFC 3678 APIs should be fine.
756 For systems administrators:
758 * The mtest(8) utility has been refactored to support IPv6, in
759 addition to IPv4. Interface addresses are no longer accepted
760 as arguments, their names must be used instead. The utility
761 will map the interface name to its first IPv4 address as
762 returned by getifaddrs(3).
764 * The ifmcstat(8) utility has also been updated to print the MLDv2
765 endpoint state and source filter lists via sysctl(3).
767 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
768 loopback of IPv6 multicast datagrams by default; it defaults to 1
769 to preserve the existing behaviour. Disabling multicast loopback is
770 recommended for optimal system performance.
772 * The IPv6 MROUTING code has been changed to examine this sysctl
773 instead of attempting to perform a group lookup before looping
774 back forwarded datagrams.
776 Bump __FreeBSD_version to 800084.
779 Implement low-level Bluetooth HCI API.
780 Bump __FreeBSD_version to 800083.
783 The layout of struct malloc_type, used by modules to register new
784 memory allocation types, has changed. Most modules will need to
785 be rebuilt or panics may be experienced.
786 Bump __FreeBSD_version to 800081.
789 Anticipate overflowing inp_flags - add inp_flags2.
790 This changes most offsets in inpcb, so checking v4 connection
791 state will require a world rebuild.
792 Bump __FreeBSD_version to 800080.
795 Add an llentry to struct route and struct route_in6. Modules
796 embedding a struct route will need to be recompiled.
797 Bump __FreeBSD_version to 800079.
800 The size of rt_metrics_lite and by extension rtentry has changed.
801 Networking administration apps will need to be recompiled.
802 The route command now supports show as an alias for get, weighting
803 of routes, sticky and nostick flags to alter the behavior of stateful
805 Bump __FreeBSD_version to 800078.
808 Do not use Giant for kbdmux(4) locking. This is wrong and
809 apparently causing more problems than it solves. This will
810 re-open the issue where interrupt handlers may race with
811 kbdmux(4) in polling mode. Typical symptoms include (but
812 not limited to) duplicated and/or missing characters when
813 low level console functions (such as gets) are used while
814 interrupts are enabled (for example geli password prompt,
815 mountroot prompt etc.). Disabling kbdmux(4) may help.
818 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
819 kernel modules referencing any of the above need to be recompiled.
820 Bump __FreeBSD_version to 800075.
823 GEOM_PART has become the default partition slicer for storage devices,
824 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
825 introduces some changes:
827 MSDOS/EBR: the devices created from MSDOS extended partition entries
828 (EBR) can be named differently than with GEOM_MBR and are now symlinks
829 to devices with offset-based names. fstabs may need to be modified.
831 BSD: the "geometry does not match label" warning is harmless in most
832 cases but it points to problems in file system misalignment with
833 disk geometry. The "c" partition is now implicit, covers the whole
834 top-level drive and cannot be (mis)used by users.
836 General: Kernel dumps are now not allowed to be written to devices
837 whose partition types indicate they are meant to be used for file
838 systems (or, in case of MSDOS partitions, as something else than
841 Most of these changes date approximately from 200812.
844 The uscanner(4) driver has been removed from the kernel. This follows
845 Linux removing theirs in 2.6 and making libusb the default interface
849 The multicast forwarding code has been cleaned up. netstat(1)
850 only relies on KVM now for printing bandwidth upcall meters.
851 The IPv4 and IPv6 modules are split into ip_mroute_mod and
852 ip6_mroute_mod respectively. The config(5) options for statically
853 compiling this code remain the same, i.e. 'options MROUTING'.
856 Support for the IFF_NEEDSGIANT network interface flag has been
857 removed, which means that non-MPSAFE network device drivers are no
858 longer supported. In particular, if_ar, if_sr, and network device
859 drivers from the old (legacy) USB stack can no longer be built or
863 POSIX.1 Native Language Support (NLS) has been enabled in libc and
864 a bunch of new language catalog files have also been added.
865 This means that some common libc messages are now localized and
866 they depend on the LC_MESSAGES environmental variable.
869 The k8temp(4) driver has been renamed to amdtemp(4) since
870 support for Family 10 and Family 11 CPU families was added.
873 IGMPv3 and Source-Specific Multicast (SSM) have been merged
874 to the IPv4 stack. VIMAGE hooks are in but not yet used.
876 For kernel developers, the most important changes are that the
877 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
878 and this lock has been downgraded to a non-recursive mutex.
880 Transport protocols (UDP, Raw IP) are now responsible for filtering
881 inbound multicast traffic according to group membership and source
882 filters. The imo_multicast_filter() KPI exists for this purpose.
883 Transports which do not use multicast (SCTP, TCP) already reject
884 multicast by default. Forwarding and receive performance may improve
885 as a mutex acquisition is no longer needed in the ip_input()
886 low-level input path. in_addmulti() and in_delmulti() are shimmed
887 to new KPIs which exist to support SSM in-kernel.
889 For application developers, it is recommended that loopback of
890 multicast datagrams be disabled for best performance, as this
891 will still cause the lock to be taken for each looped-back
892 datagram transmission. The net.inet.ip.mcast.loop sysctl may
893 be tuned to 0 to disable loopback by default; it defaults to 1
894 to preserve the existing behaviour.
896 For systems administrators, to obtain best performance with
897 multicast reception and multiple groups, it is always recommended
898 that a card with a suitably precise hash filter is used. Hash
899 collisions will still result in the lock being taken within the
900 transport protocol input path to check group membership.
902 If deploying FreeBSD in an environment with IGMP snooping switches,
903 it is recommended that the net.inet.igmp.sendlocal sysctl remain
904 enabled; this forces 224.0.0.0/24 group membership to be announced
907 The size of 'struct igmpstat' has changed; netstat needs to be
908 recompiled to reflect this.
909 Bump __FreeBSD_version to 800070.
912 libusb20.so.1 is now installed as libusb.so.1 and the ports system
913 updated to use it. This requires a buildworld/installworld in order to
914 update the library and dependencies (usbconfig, etc). Its advisable to
915 rebuild all ports which uses libusb. More specific directions are given
916 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
917 libusb are no longer required and can be removed.
920 A workaround is committed to allow the creation of System V shared
921 memory segment of size > 2 GB on the 64-bit architectures.
922 Due to a limitation of the existing ABI, the shm_segsz member
923 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
924 wrong for large segments. Note that limits must be explicitly
925 raised to allow such segments to be created.
928 The layout of struct ifnet has changed, requiring a rebuild of all
929 network device driver modules.
932 The /dev handling for the new USB stack has changed, a
933 buildworld/installworld is required for libusb20.
936 The new USB2 stack has now been permanently moved in and all kernel and
937 module names reverted to their previous values (eg, usb, ehci, ohci,
938 ums, ...). The old usb stack can be compiled in by prefixing the name
939 with the letter 'o', the old usb modules have been removed.
940 Updating entry 20090216 for xorg and 20090215 for libmap may still
944 The rc.conf(5) option if_up_delay has been renamed to
945 defaultroute_delay to better reflect its purpose. If you have
946 customized this setting in /etc/rc.conf you need to update it to
950 xorg 7.4 wants to configure its input devices via hald which does not
951 yet work with USB2. If the keyboard/mouse does not work in xorg then
953 Option "AllowEmptyInput" "off"
954 to your ServerLayout section. This will cause X to use the configured
955 kbd and mouse sections from your xorg.conf.
958 The GENERIC kernels for all architectures now default to the new USB2
959 stack. No kernel config options or code have been removed so if a
960 problem arises please report it and optionally revert to the old USB
961 stack. If you are loading USB kernel modules or have a custom kernel
962 that includes GENERIC then ensure that usb names are also changed over,
963 eg uftdi -> usb2_serial_ftdi.
965 Older programs linked against the ports libusb 0.1 need to be
966 redirected to the new stack's libusb20. /etc/libmap.conf can
968 # Map old usb library to new one for usb2 stack
969 libusb-0.1.so.8 libusb20.so.1
972 All USB ethernet devices now attach as interfaces under the name ueN
973 (eg. ue0). This is to provide a predictable name as vendors often
974 change usb chipsets in a product without notice.
977 The ichsmb(4) driver has been changed to require SMBus slave
978 addresses be left-justified (xxxxxxx0b) rather than right-justified.
979 All of the other SMBus controller drivers require left-justified
980 slave addresses, so this change makes all the drivers provide the
984 INET6 statistics (struct ip6stat) was updated.
985 netstat(1) needs to be recompiled.
988 NTFS has been removed from GENERIC kernel on amd64 to match
989 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
990 will load ntfs.ko module automatically when NTFS support is
991 actually needed, unless ntfs.ko is not installed or security
992 level prohibits loading kernel modules. If either is the case,
993 "options NTFS" has to be added into kernel config.
996 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
997 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
998 800061. User space tools that rely on the size of struct tcpcb in
999 tcp_var.h (e.g. sockstat) need to be recompiled.
1002 ng_tty(4) module updated to match the new TTY subsystem.
1003 Due to API change, user-level applications must be updated.
1004 New API support added to mpd5 CVS and expected to be present
1005 in next mpd5.3 release.
1008 With __FreeBSD_version 800060 the makefs tool is part of
1009 the base system (it was a port).
1012 The afdata and ifnet locks have been changed from mutexes to
1013 rwlocks, network modules will need to be re-compiled.
1016 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1017 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1018 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1019 architecture and 40 bytes on 64-bit architecture. The userland
1020 applications "arp" and "ndp" have been updated accordingly.
1021 The output from "netstat -r" shows only routing entries and
1022 none of the L2 information.
1025 __FreeBSD_version 800057 marks the switchover from the
1026 binary ath hal to source code. Users must add the line:
1028 options AH_SUPPORT_AR5416
1030 to their kernel config files when specifying:
1034 The ath_hal module no longer exists; the code is now compiled
1035 together with the driver in the ath module. It is now
1036 possible to tailor chip support (i.e. reduce the set of chips
1037 and thereby the code size); consult ath_hal(4) for details.
1040 __FreeBSD_version 800054 adds memory barriers to
1041 <machine/atomic.h>, new interfaces to ifnet to facilitate
1042 multiple hardware transmit queues for cards that support
1043 them, and a lock-less ring-buffer implementation to
1044 enable drivers to more efficiently manage queueing of
1048 A new version of ZFS (version 13) has been merged to -HEAD.
1049 This version has zpool attribute "listsnapshots" off by
1050 default, which means "zfs list" does not show snapshots,
1051 and is the same as Solaris behavior.
1054 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1057 The uhci, ohci, ehci and slhci USB Host controller drivers have
1058 been put into separate modules. If you load the usb module
1059 separately through loader.conf you will need to load the
1060 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1061 controller add the following to loader.conf:
1067 The ABI used by the PMC toolset has changed. Please keep
1068 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1072 atapci kernel module now includes only generic PCI ATA
1073 driver. AHCI driver moved to ataahci kernel module.
1074 All vendor-specific code moved into separate kernel modules:
1075 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1076 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1077 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1078 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1081 The TTY subsystem of the kernel has been replaced by a new
1082 implementation, which provides better scalability and an
1083 improved driver model. Most common drivers have been migrated to
1084 the new TTY subsystem, while others have not. The following
1085 drivers have not yet been ported to the new TTY layer:
1088 cy, digi, rc, rp, sio
1094 ng_h4, ng_tty, ppp, sl, snp
1096 Adding these drivers to your kernel configuration file shall
1097 cause compilation to fail.
1100 ntpd has been upgraded to 4.2.4p5.
1103 OpenSSH has been upgraded to 5.1p1.
1105 For many years, FreeBSD's version of OpenSSH preferred DSA
1106 over RSA for host and user authentication keys. With this
1107 upgrade, we've switched to the vendor's default of RSA over
1108 DSA. This may cause upgraded clients to warn about unknown
1109 host keys even for previously known hosts. Users should
1110 follow the usual procedure for verifying host keys before
1111 accepting the RSA key.
1113 This can be circumvented by setting the "HostKeyAlgorithms"
1114 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1117 Please note that the sequence of keys offered for
1118 authentication has been changed as well. You may want to
1119 specify IdentityFile in a different order to revert this
1123 The sio(4) driver has been removed from the i386 and amd64
1124 kernel configuration files. This means uart(4) is now the
1125 default serial port driver on those platforms as well.
1127 To prevent collisions with the sio(4) driver, the uart(4) driver
1128 uses different names for its device nodes. This means the
1129 onboard serial port will now most likely be called "ttyu0"
1130 instead of "ttyd0". You may need to reconfigure applications to
1131 use the new device names.
1133 When using the serial port as a boot console, be sure to update
1134 /boot/device.hints and /etc/ttys before booting the new kernel.
1135 If you forget to do so, you can still manually specify the hints
1136 at the loader prompt:
1138 set hint.uart.0.at="isa"
1139 set hint.uart.0.port="0x3F8"
1140 set hint.uart.0.flags="0x10"
1141 set hint.uart.0.irq="4"
1145 The gpt(8) utility has been removed. Use gpart(8) to partition
1149 The version that Linuxulator emulates was changed from 2.4.2
1150 to 2.6.16. If you experience any problems with Linux binaries
1151 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1152 if it fixes the problem contact emulation mailing list.
1155 ISDN4BSD (I4B) was removed from the src tree. You may need to
1156 update a your kernel configuration and remove relevant entries.
1159 I have checked in code to support multiple routing tables.
1160 See the man pages setfib(1) and setfib(2).
1161 This is a hopefully backwards compatible version,
1162 but to make use of it you need to compile your kernel
1163 with options ROUTETABLES=2 (or more up to 16).
1166 The 802.11 wireless support was redone to enable multi-bss
1167 operation on devices that are capable. The underlying device
1168 is no longer used directly but instead wlanX devices are
1169 cloned with ifconfig. This requires changes to rc.conf files.
1170 For example, change:
1171 ifconfig_ath0="WPA DHCP"
1174 ifconfig_wlan0="WPA DHCP"
1175 see rc.conf(5) for more details. In addition, mergemaster of
1176 /etc/rc.d is highly recommended. Simultaneous update of userland
1177 and kernel wouldn't hurt either.
1179 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1180 modules were merged into the base wlan module. All references
1181 to these modules (e.g. in kernel config files) must be removed.
1184 psm(4) has gained write(2) support in native operation level.
1185 Arbitrary commands can be written to /dev/psm%d and status can
1186 be read back from it. Therefore, an application is responsible
1187 for status validation and error recovery. It is a no-op in
1188 other operation levels.
1191 Support for KSE threading has been removed from the kernel. To
1192 run legacy applications linked against KSE libmap.conf may
1193 be used. The following libmap.conf may be used to ensure
1194 compatibility with any prior release:
1196 libpthread.so.1 libthr.so.1
1197 libpthread.so.2 libthr.so.2
1198 libkse.so.3 libthr.so.3
1201 The layout of struct vmspace has changed. This affects libkvm
1202 and any executables that link against libkvm and use the
1203 kvm_getprocs() function. In particular, but not exclusively,
1204 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1205 The effects are minimal, but it's advisable to upgrade world
1209 The latest em driver no longer has support in it for the
1210 82575 adapter, this is now moved to the igb driver. The
1211 split was done to make new features that are incompatible
1212 with older hardware easier to do.
1215 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1216 likewise the kernel option is now GEOM_LINUX_LVM.
1219 The default NFS mount mode has changed from UDP to TCP for
1220 increased reliability. If you rely on (insecurely) NFS
1221 mounting across a firewall you may need to update your
1225 Belatedly note the addition of m_collapse for compacting
1229 The fts(3) structures have been changed to use adequate
1230 integer types for their members and so to be able to cope
1231 with huge file trees. The old fts(3) ABI is preserved
1232 through symbol versioning in libc, so third-party binaries
1233 using fts(3) should still work, although they will not take
1234 advantage of the extended types. At the same time, some
1235 third-party software might fail to build after this change
1236 due to unportable assumptions made in its source code about
1237 fts(3) structure members. Such software should be fixed
1238 by its vendor or, in the worst case, in the ports tree.
1239 FreeBSD_version 800015 marks this change for the unlikely
1240 case that a portable fix is impossible.
1243 To upgrade to -current after this date, you must be running
1244 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1245 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1248 The ADAPTIVE_GIANT kernel option has been retired because its
1249 functionality is the default now.
1252 The AT keyboard emulation of sunkbd(4) has been turned on
1253 by default. In order to make the special symbols of the Sun
1254 keyboards driven by sunkbd(4) work under X these now have
1255 to be configured the same way as Sun USB keyboards driven
1256 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1258 Option "XkbLayout" "us"
1259 Option "XkbRules" "xorg"
1260 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1263 It has been decided that it is desirable to provide ABI
1264 backwards compatibility to the FreeBSD 4/5/6 versions of the
1265 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1266 broken with the introduction of PCI domain support (see the
1267 20070930 entry). Unfortunately, this required the ABI of
1268 PCIOCGETCONF to be broken again in order to be able to
1269 provide backwards compatibility to the old version of that
1270 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1271 again. As for prominent ports this affects neither pciutils
1272 nor xorg-server this time, the hal port needs to be rebuilt
1276 The misnamed kthread_create() and friends have been renamed
1277 to kproc_create() etc. Many of the callers already
1278 used kproc_start()..
1279 I will return kthread_create() and friends in a while
1280 with implementations that actually create threads, not procs.
1281 Renaming corresponds with version 800002.
1290 Avoid using make -j when upgrading. While generally safe, there are
1291 sometimes problems using -j to upgrade. If your upgrade fails with
1292 -j, please try again without -j. From time to time in the past there
1293 have been problems using -j with buildworld and/or installworld. This
1294 is especially true when upgrading between "distant" versions (eg one
1295 that cross a major release boundary or several minor releases, or when
1296 several months have passed on the -current branch).
1298 Sometimes, obscure build problems are the result of environment
1299 poisoning. This can happen because the make utility reads its
1300 environment when searching for values for global variables. To run
1301 your build attempts in an "environmental clean room", prefix all make
1302 commands with 'env -i '. See the env(1) manual page for more details.
1304 When upgrading from one major version to another it is generally best
1305 to upgrade to the latest code in the currently installed branch first,
1306 then do an upgrade to the new branch. This is the best-tested upgrade
1307 path, and has the highest probability of being successful. Please try
1308 this approach before reporting problems with a major version upgrade.
1312 When upgrading the boot ZFS pool to a new version, always follow
1315 1.) recompile and reinstall the ZFS boot loader and boot block
1316 (this is part of "make buildworld" and "make installworld")
1318 2.) update the ZFS boot block on your boot drive
1320 The following example updates the ZFS boot block on the first
1321 partition (freebsd-boot) of a GPT partitioned drive ad0:
1322 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1324 Non-boot pools do not need these updates.
1328 If you are updating from a prior version of FreeBSD (even one just
1329 a few days old), you should follow this procedure. It is the most
1330 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1332 make kernel-toolchain
1333 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1334 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1336 To test a kernel once
1337 ---------------------
1338 If you just want to boot a kernel once (because you are not sure
1339 if it works, or if you want to boot a known bad kernel to provide
1340 debugging information) run
1341 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1342 nextboot -k testkernel
1344 To just build a kernel when you know that it won't mess you up
1345 --------------------------------------------------------------
1346 This assumes you are already running a CURRENT system. Replace
1347 ${arch} with the architecture of your machine (e.g. "i386",
1348 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1350 cd src/sys/${arch}/conf
1351 config KERNEL_NAME_HERE
1352 cd ../compile/KERNEL_NAME_HERE
1357 If this fails, go to the "To build a kernel" section.
1359 To rebuild everything and install it on the current system.
1360 -----------------------------------------------------------
1361 # Note: sometimes if you are running current you gotta do more than
1362 # is listed here if you are upgrading from a really old current.
1364 <make sure you have good level 0 dumps>
1366 make kernel KERNCONF=YOUR_KERNEL_HERE
1368 <reboot in single user> [3]
1376 To cross-install current onto a separate partition
1377 --------------------------------------------------
1378 # In this approach we use a separate partition to hold
1379 # current's root, 'usr', and 'var' directories. A partition
1380 # holding "/", "/usr" and "/var" should be about 2GB in
1383 <make sure you have good level 0 dumps>
1386 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1387 <maybe newfs current's root partition>
1388 <mount current's root partition on directory ${CURRENT_ROOT}>
1389 make installworld DESTDIR=${CURRENT_ROOT}
1390 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1391 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1392 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1393 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1394 <reboot into current>
1395 <do a "native" rebuild/install as described in the previous section>
1396 <maybe install compatibility libraries from ports/misc/compat*>
1400 To upgrade in-place from 8.x-stable to current
1401 ----------------------------------------------
1402 <make sure you have good level 0 dumps>
1404 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1406 <reboot in single user> [3]
1413 Make sure that you've read the UPDATING file to understand the
1414 tweaks to various things you need. At this point in the life
1415 cycle of current, things change often and you are on your own
1416 to cope. The defaults can also change, so please read ALL of
1417 the UPDATING entries.
1419 Also, if you are tracking -current, you must be subscribed to
1420 freebsd-current@freebsd.org. Make sure that before you update
1421 your sources that you have read and understood all the recent
1422 messages there. If in doubt, please track -stable which has
1423 much fewer pitfalls.
1425 [1] If you have third party modules, such as vmware, you
1426 should disable them at this point so they don't crash your
1429 [3] From the bootblocks, boot -s, and then do
1434 adjkerntz -i # if CMOS is wall time
1435 Also, when doing a major release upgrade, it is required that
1436 you boot into single user mode to do the installworld.
1438 [4] Note: This step is non-optional. Failure to do this step
1439 can result in a significant reduction in the functionality of the
1440 system. Attempting to do it by hand is not recommended and those
1441 that pursue this avenue should read this file carefully, as well
1442 as the archives of freebsd-current and freebsd-hackers mailing lists
1443 for potential gotchas. The -U option is also useful to consider.
1444 See mergemaster(8) for more information.
1446 [5] Usually this step is a noop. However, from time to time
1447 you may need to do this if you get unknown user in the following
1448 step. It never hurts to do it all the time. You may need to
1449 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1450 install) after the buildworld before this step if you last updated
1451 from current before 20020224 or from -stable before 20020408.
1453 [6] This only deletes old files and directories. Old libraries
1454 can be deleted by "make delete-old-libs", but you have to make
1455 sure that no program is using those libraries anymore.
1457 [8] In order to have a kernel that can run the 4.x binaries needed to
1458 do an installworld, you must include the COMPAT_FREEBSD4 option in
1459 your kernel. Failure to do so may leave you with a system that is
1460 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1461 required to run the 5.x binaries on more recent kernels. And so on
1462 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1464 Make sure that you merge any new devices from GENERIC since the
1465 last time you updated your kernel config file.
1467 [9] When checking out sources, you must include the -P flag to have
1468 cvs prune empty directories.
1470 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1471 "?=" instead of the "=" assignment operator, so that buildworld can
1472 override the CPUTYPE if it needs to.
1474 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1475 not on the command line, or in /etc/make.conf. buildworld will
1476 warn if it is improperly defined.
1479 This file contains a list, in reverse chronological order, of major
1480 breakages in tracking -current. It is not guaranteed to be a complete
1481 list of such breakages, and only contains entries since October 10, 2007.
1482 If you need to see UPDATING entries from before that date, you will need
1483 to fetch an UPDATING file from an older FreeBSD release.
1485 Copyright information:
1487 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1489 Redistribution, publication, translation and use, with or without
1490 modification, in full or in part, in any form or format of this
1491 document are permitted without further permission from the author.
1493 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1494 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1495 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1496 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1497 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1498 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1499 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1500 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1501 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1502 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1503 POSSIBILITY OF SUCH DAMAGE.
1505 Contact Warner Losh if you have any questions about your use of