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