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 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
15 Fix a bug that allows NFS clients to issue READDIR on files.
18 The install(1) option -M has changed meaning and now takes an
19 argument that is a file or path to append logs to. In the
20 unlikely event that -M was the last option on the command line
21 and the command line contained at least two files and a target
22 directory the first file will have logs appended to it. The -M
23 option served little practical purpose in the last decade so it's
24 used expected to be extremely rare.
27 A new compression method (lz4) has been merged to. Please refer to
28 zpool-features(7) for more information.
30 Please refer to the "ZFS notes" section of this file for information
31 on upgrading boot ZFS pools.
34 The VFS KBI was changed with the merge of several nullfs
35 optimizations and fixes. All filesystem modules must be
39 With the addition of auditdistd(8), a new auditdistd user is now
40 depended on during installworld. "mergemaster -p" can be used to add
41 the user prior to installworld, as documented in the handbook.
47 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
48 Starting with this version the old system of ZFS pool versioning
49 is superseded by "feature flags". This concept enables forward
50 compatibility against certain future changes in functionality of ZFS
51 pools. The first two read-only compatible "feature flags" for ZFS
52 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
53 For more information read the new zpool-features(7) manual page.
54 Please refer to the "ZFS notes" section of this file for information
55 on upgrading boot ZFS pools.
58 The commit introducing bsd.compiler.mk breaks the traditional
59 building of kernels before this point. Add -m ${SRC}/share/mk
60 (for the right value of SRC) to your command lines to work
61 around; update your useland to a point after this; or use the
62 buildkernel/installkernel top-level targets. See also 20120829.
65 The IPFIREWALL_FORWARD kernel option has been removed. Its
66 functionality now turned on by default.
69 The random(4) support for the VIA hardware random number
70 generator (`PADLOCK') is no longer enabled unconditionally.
71 Add the PADLOCK_RNG option in the custom kernel config if
72 needed. The GENERIC kernels on i386 and amd64 do include the
73 option, so the change only affects the custom kernel
77 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
78 the traditional method, you must update your system with an installworld
79 before the kernel will build. The documented make buildkernel/installkernel
80 interfaces (coupled with fresh make kernel-toolchain) continue to work.
83 The sparc64 ZFS loader has been changed to no longer try to auto-
84 detect ZFS providers based on diskN aliases but now requires these
85 to be explicitly listed in the OFW boot-device environment variable.
88 Now unix domain sockets behave "as expected" on nullfs(5). Previously
89 nullfs(5) did not pass through all behaviours to the underlying layer,
90 as a result if we bound to a socket on the lower layer we could connect
91 only to the lower path; if we bound to the upper layer we could connect
92 only to the upper path. The new behavior is one can connect to both the
93 lower and the upper paths regardless what layer path one binds to.
96 The acpi_wmi(4) status device /dev/wmistat has been renamed to
100 A new VOP_ADVISE() was added to support posix_fadvise(2). All
101 filesystem modules must be recompiled.
104 The interface of the VOP_VPTOCNP(9) changed, now the returned
105 vnode shall be referenced, previously it was required to be
106 only held. All in-tree filesystems are converted.
112 The broken amd(4) driver has been replaced with esp(4) in the amd64,
113 i386 and pc98 GENERIC kernel configuration files.
116 This commit modifies vfs_register() so that it uses a hash
117 calculation to set vfc_typenum, which is enabled by default.
118 The first time a system is booted after this change, the
119 vfc_typenum values will change for all file systems. The
120 main effect of this is a change to the NFS server file handles
121 for file systems that use vfc_typenum in their fsid, such as ZFS.
122 It will, however, prevent vfc_typenum from changing when file
123 systems are loaded in a different order for subsequent reboots.
124 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
125 until you are ready to remount all NFS clients after a reboot.
128 Bump the shared library version numbers for libraries that
129 do not use symbol versioning, have changed the ABI compared
130 to stable/8 and which shared library version was not bumped.
131 Done as part of 9.0-RELEASE cycle.
134 During the merge of Capsicum features, the fget(9) KPI was modified.
135 This may require the rebuilding of out-of-tree device drivers --
136 issues have been reported specifically with the nVidia device driver.
137 __FreeBSD_version is bumped to 900041.
139 Also, there is a period between 20110811 and 20110814 where the
140 special devices /dev/{stdin,stdout,stderr} did not work correctly.
141 Building world from a kernel during that window may not work.
144 The packet filter (pf) code has been updated to OpenBSD 4.5.
145 You need to update userland tools to be in sync with kernel.
146 This update breaks backward compatibility with earlier pfsync(4)
147 versions. Care must be taken when updating redundant firewall setups.
150 The following sysctls and tunables are retired on x86 platforms:
152 machdep.hlt_logical_cpus
153 The following sysctl is retired:
154 machdep.hyperthreading_allowed
155 The sysctls were supposed to provide a way to dynamically offline and
156 online selected CPUs on x86 platforms, but the implementation has not
157 been reliable especially with SCHED_ULE scheduler.
158 machdep.hyperthreading_allowed tunable is still available to ignore
159 hyperthreading CPUs at OS level.
160 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
161 where X is an APIC ID of a CPU. Be advised, though, that disabling
162 CPUs in non-uniform fashion will result in non-uniform topology and
163 may lead to sub-optimal system performance with SCHED_ULE, which is
167 cpumask_t type is retired and cpuset_t is used in order to describe
171 Changes to ifconfig(8) for dynamic address family detection mandate
172 that you are running a kernel of 20110525 or later. Make sure to
173 follow the update procedure to boot a new kernel before installing
177 Support for sun4v architecture is officially dropped
180 Several KPI breaking changes have been committed to the mii(4) layer,
181 the PHY drivers and consequently some Ethernet drivers using mii(4).
182 This means that miibus.ko and the modules of the affected Ethernet
183 drivers need to be recompiled.
185 Note to kernel developers: Given that the OUI bit reversion problem
186 was fixed as part of these changes all mii(4) commits related to OUIs,
187 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
188 handling, no longer can be merged verbatim to stable/8 and previous
192 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
193 into their kernel configurations along with 'device pci'.
196 The default NFS client is now the new NFS client, so fstype "newnfs"
197 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
198 Although mounts via fstype "nfs" will usually work without userland
199 changes, it is recommended that the mount(8) and mount_nfs(8)
200 commands be rebuilt from sources and that a link to mount_nfs called
201 mount_oldnfs be created. The new client is compiled into the
202 kernel with "options NFSCL" and this is needed for diskless root
203 file systems. The GENERIC kernel configs have been changed to use
204 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
205 To use the regular/old client, you can "mount -t oldnfs ...". For
206 a diskless root file system, you must also include a line like:
208 vfs.root.mountfrom="oldnfs:"
210 in the boot/loader.conf on the root fs on the NFS server to make
211 a diskless root fs use the old client.
214 The GENERIC kernels for all architectures now default to the new
215 CAM-based ATA stack. It means that all legacy ATA drivers were
216 removed and replaced by respective CAM drivers. If you are using
217 ATA device names in /etc/fstab or other places, make sure to update
218 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
219 where 'Y's are the sequential numbers starting from zero for each type
220 in order of detection, unless configured otherwise with tunables,
221 see cam(4)). There will be symbolic links created in /dev/ to map
222 old adX devices to the respective adaY. They should provide basic
223 compatibility for file systems mounting in most cases, but they do
224 not support old user-level APIs and do not have respective providers
225 in GEOM. Consider using updated management tools with new device names.
227 It is possible to load devices ahci, ata, siis and mvs as modules,
228 but option ATA_CAM should remain in kernel configuration to make ata
229 module work as CAM driver supporting legacy ATA controllers. Device ata
230 still can be used in modular fashion (atacore + ...). Modules atadisk
231 and atapi* are not used and won't affect operation in ATA_CAM mode.
232 Note that to use CAM-based ATA kernel should include CAM devices
233 scbus, pass, da (or explicitly ada), cd and optionally others. All of
234 them are parts of the cam module.
236 ataraid(4) functionality is now supported by the RAID GEOM class.
237 To use it you can load geom_raid kernel module and use graid(8) tool
238 for management. Instead of /dev/arX device names, use /dev/raid/rX.
240 No kernel config options or code have been removed, so if a problem
241 arises, please report it and optionally revert to the old ATA stack.
242 In order to do it you can remove from the kernel config:
247 , and instead add back:
248 device atadisk # ATA disk drives
249 device ataraid # ATA RAID drives
250 device atapicd # ATAPI CDROM drives
251 device atapifd # ATAPI floppy drives
252 device atapist # ATAPI tape drives
255 The default NFS server has been changed to the new server, which
256 was referred to as the experimental server. If you need to switch
257 back to the old NFS server, you must now put the "-o" option on
258 both the mountd and nfsd commands. This can be done using the
259 mountd_flags and nfs_server_flags rc.conf variables until an
260 update to the rc scripts is committed, which is coming soon.
263 The GNU Objective-C runtime library (libobjc), and other Objective-C
264 related components have been removed from the base system. If you
265 require an Objective-C library, please use one of the available ports.
268 ath(4) has been split into bus- and device- modules. if_ath contains
269 the HAL, the TX rate control and the network device code. if_ath_pci
270 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
271 contains the AHB glue. Users need to load both if_ath_pci and if_ath
272 in order to use ath on everything else.
274 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
275 need to load if_ath and if_ath_pci for ath(4) operation.
278 As part of the replacement of sysinstall, the process of building
279 release media has changed significantly. For details, please re-read
280 release(7), which has been updated to reflect the new build process.
283 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
284 is the last available version under GPLv2. It brings a number of new
285 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
286 4.1 and SSE 4.2), better support for powerpc64, a number of new
287 directives, and lots of other small improvements. See the ChangeLog
288 file in contrib/binutils for the full details.
291 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
292 compliant, and will now use half of hash for authentication.
293 This will break interoperability with all stacks (including all
294 actual FreeBSD versions) who implement
295 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
297 The only workaround with such peers is to use another HMAC
298 algorithm for IPsec ("phase 2") authentication.
301 Remove the uio_yield prototype and symbol. This function has
302 been misnamed since it was introduced and should not be
303 globally exposed with this name. The equivalent functionality
304 is now available using kern_yield(curthread->td_user_pri).
305 The function remains undocumented.
308 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
309 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
310 for scalar sysctls is defined but disabled. Code that needs
311 UQUAD to pass the type checking that must compile on older
312 systems where the define is not present can check against
313 __FreeBSD_version >= 900030.
315 The system dialog(1) has been replaced with a new version previously
316 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
317 with the previous version, but the libdialog associated with it has
318 a largely incompatible API. As such, the original version of libdialog
319 will be kept temporarily as libodialog, until its base system consumers
320 are replaced or updated. Bump __FreeBSD_version to 900030.
323 If you are trying to run make universe on a -stable system, and you get
324 the following warning:
325 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
326 unknown. config(8) likely too old."
327 or something similar to it, then you must upgrade your -stable system
328 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
329 stable/8) or build the config from the latest stable/8 branch and
330 install it on your system.
332 Prior to this date, building a current universe on 8-stable system from
333 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
334 error in the first kernel build phase. A new config on those old
335 systems will fix that problem for older versions of -current.
338 The TCP stack has been modified to allow Khelp modules to interact with
339 it via helper hook points and store per-connection data in the TCP
340 control block. Bump __FreeBSD_version to 900029. User space tools that
341 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
345 Generic IEEE 802.3 annex 31B full duplex flow control support has been
346 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
347 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
348 to take advantage of it instead of using custom implementations. This
349 means that these drivers now no longer unconditionally advertise
350 support for flow control but only do so if flow control is a selected
351 media option. This was implemented in the generic support that way in
352 order to allow flow control to be switched on and off via ifconfig(8)
353 with the PHY specific default to typically off in order to protect
354 from unwanted effects. Consequently, if you used flow control with
355 one of the above mentioned drivers you now need to explicitly enable
357 ifconfig bge0 media auto mediaopt flowcontrol
359 Along with the above mentioned changes generic support for setting
360 1000baseT master mode also has been added and brgphy(4), ciphy(4),
361 e1000phy(4) as well as ip1000phy(4) have been converted to take
362 advantage of it. This means that these drivers now no longer take the
363 link0 parameter for selecting master mode but the master media option
364 has to be used instead, for example like in the following:
365 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
367 Selection of master mode now is also available with all other PHY
368 drivers supporting 1000baseT.
371 The TCP stack has received a significant update to add support for
372 modularised congestion control and generally improve the clarity of
373 congestion control decisions. Bump __FreeBSD_version to 900025. User
374 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
375 sockstat) need to be recompiled.
378 The man(1) utility has been replaced by a new version that no longer
379 uses /etc/manpath.config. Please consult man.conf(5) for how to
380 migrate local entries to the new format.
383 The copyright strings printed by login(1) and sshd(8) at the time of a
384 new connection have been removed to follow other operating systems and
388 A workaround for a fixed ld bug has been removed in kernel code,
389 so make sure that your system ld is built from sources after
390 revision 210245 from 2010-07-19 (r211583 if building head kernel
391 on stable/8, r211584 for stable/7; both from 2010-08-21).
392 A symptom of incorrect ld version is different addresses for
393 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
396 The $ipv6_prefer variable in rc.conf(5) has been split into
397 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
399 The $ip6addrctl_policy is a variable to choose a pre-defined
400 address selection policy set by ip6addrctl(8). A value
401 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
404 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
405 flag (see an entry of 20090926) is set on an interface with no
406 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
407 security reason. If you want IPv6 link-local address on all
408 interfaces by default, set this to "YES".
410 The old ipv6_prefer="YES" is equivalent to
411 ipv6_activate_all_interfaces="YES" and
412 ip6addrctl_policy="ipv6_prefer".
415 DTrace has grown support for userland tracing. Due to this, DTrace is
416 now i386 and amd64 only.
417 dtruss(1) is now installed by default on those systems and a new
418 kernel module is needed for userland tracing: fasttrap.
419 No changes to your kernel config file are necessary to enable
420 userland tracing, but you might consider adding 'STRIP=' and
421 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
422 to have informative userland stack traces in DTrace (ustack).
425 The acpi_aiboost(4) driver has been removed in favor of the new
426 aibs(4) driver. You should update your kernel configuration file.
429 BSD grep has been imported to the base system and it is built by
430 default. It is completely BSD licensed, highly GNU-compatible, uses
431 less memory than its GNU counterpart and has a small codebase.
432 However, it is slower than its GNU counterpart, which is mostly
433 noticeable for larger searches, for smaller ones it is measurable
434 but not significant. The reason is complex, the most important factor
435 is that we lack a modern and efficient regex library and GNU
436 overcomes this by optimizing the searches internally. Future work
437 on improving the regex performance is planned, for the meantime,
438 users that need better performance, can build GNU grep instead by
439 setting the WITH_GNU_GREP knob.
442 Due to the import of powerpc64 support, all existing powerpc kernel
443 configuration files must be updated with a machine directive like this:
444 machine powerpc powerpc
446 In addition, an updated config(8) is required to build powerpc kernels
450 A new version of ZFS (version 15) has been merged to -HEAD.
451 This version uses a python library for the following subcommands:
452 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
453 For full functionality of these commands the following port must
454 be installed: sysutils/py-zfs
457 'vm_page's are now hashed by physical address to an array of mutexes.
458 Currently this is only used to serialize access to hold_count. Over
459 time the page queue mutex will be peeled away. This changes the size
460 of pmap on every architecture. And requires all callers of vm_page_hold
461 and vm_page_unhold to be updated.
464 WITH_CTF can now be specified in src.conf (not recommended, there
465 are some problems with static executables), make.conf (would also
466 affect ports which do not use GNU make and do not override the
467 compile targets) or in the kernel config (via "makeoptions
469 When WITH_CTF was specified there before this was silently ignored,
470 so make sure that WITH_CTF is not used in places which could lead
471 to unwanted behavior.
474 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
475 to allow 32-bit compatibility on non-x86 platforms. All kernel
476 configurations on amd64 and ia64 platforms using these options must
477 be modified accordingly.
480 The utmp user accounting database has been replaced with utmpx,
481 the user accounting interface standardized by POSIX.
482 Unfortunately the semantics of utmp and utmpx don't match,
483 making it practically impossible to support both interfaces.
484 The user accounting database is used by tools like finger(1),
485 last(1), talk(1), w(1) and ac(8).
487 All applications in the base system use utmpx. This means only
488 local binaries (e.g. from the ports tree) may still use these
489 utmp database files. These applications must be rebuilt to make
492 After the system has been upgraded, it is safe to remove the old
493 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
494 assuming their contents is of no importance anymore. Old wtmp
495 databases can only be used by last(1) and ac(8) after they have
496 been converted to the new format using wtmpcvt(1).
499 Introduce the kernel thread "deadlock resolver" (which can be enabled
500 via the DEADLKRES option, see NOTES for more details) and the
501 sleepq_type() function for sleepqueues.
504 The rc.firewall and rc.firewall6 were unified, and
505 rc.firewall6 and rc.d/ip6fw were removed.
506 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
507 variables are obsoleted. Instead, the following new rc
508 variables are added to rc.d/ipfw:
510 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
511 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
512 firewall_simple_onet_ipv6, firewall_trusted_ipv6
514 The meanings correspond to the relevant IPv4 variables.
520 The default terminal emulation for syscons(4) has been changed
521 from cons25 to xterm on all platforms except pc98. This means
522 that the /etc/ttys file needs to be updated to ensure correct
523 operation of applications on the console.
525 The terminal emulation style can be toggled per window by using
526 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
527 options can be used to change the compile-time default back to
530 To prevent graphical artifacts, make sure the TERM environment
531 variable is set to match the terminal emulation that is being
532 performed by syscons(4).
535 The layout of the structure ieee80211req_scan_result has changed.
536 Applications that require wireless scan results (e.g. ifconfig(8))
537 from net80211 need to be recompiled.
539 Applications such as wpa_supplicant(8) may require a full world
540 build without using NO_CLEAN in order to get synchronized with the
544 The iwn(4) driver has been updated to support the 5000 and 5150 series.
545 There's one kernel module for each firmware. Adding "device iwnfw"
546 to the kernel configuration file means including all three firmware
547 images inside the kernel. If you want to include just the one for
548 your wireless card, use the devices iwn4965fw, iwn5000fw or
552 The rc.d/network_ipv6, IPv6 configuration script has been integrated
553 into rc.d/netif. The changes are the following:
555 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
556 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
557 Note that both variables need the "inet6" keyword at the head.
559 Do not set $ipv6_network_interfaces manually if you do not
560 understand what you are doing. It is not needed in most cases.
562 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
565 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
566 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
568 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
569 all configured interfaces have "inet6 accept_rtadv" in the
570 $ifconfig_IF_ipv6. These are for backward compatibility.
572 3. A new variable $ipv6_prefer has been added. If NO, IPv6
573 functionality of interfaces with no corresponding
574 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
575 and the default address selection policy of ip6addrctl(8)
576 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
577 Note that if you want to configure IPv6 functionality on the
578 disabled interfaces after boot, first you need to clear the flag by
579 using ifconfig(8) like:
581 ifconfig em0 inet6 -ifdisabled
583 If YES, the default address selection policy is set as
586 The default value of $ipv6_prefer is NO.
588 4. If your system need to receive Router Advertisement messages,
589 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
590 scripts automatically invoke rtsol(8) when the interface becomes
591 UP. The Router Advertisement messages are used for SLAAC
592 (State-Less Address AutoConfiguration).
595 802.11s D3.03 support was committed. This is incompatible with the
596 previous code, which was based on D3.0.
599 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
600 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
601 control whether accepting Router Advertisement messages or not.
602 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
603 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
604 The ifconfig(8) utility now supports these flags.
607 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
608 mount(8) and -a option for df(1) to see them.
611 The old tunable hw.bus.devctl_disable has been superseded by
612 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
613 replaced by hw.bus.devctl_queue=0. The default for this new tunable
617 Remove the option STOP_NMI. The default action is now to use NMI only
618 for KDB via the newly introduced function stop_cpus_hard() and
619 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
622 The stable/8 branch created in subversion. This corresponds to the
623 RELENG_8 branch in CVS.
626 Bump the shared library version numbers for all libraries that do not
627 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
628 __FreeBSD_version to 800105.
631 Due to changes in the implementation of virtual network stack support,
632 all network-related kernel modules must be recompiled. As this change
633 breaks the ABI, bump __FreeBSD_version to 800104.
636 The TOE interface to the TCP syncache has been modified to remove
637 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
638 The cxgb driver is the only TOE consumer affected by this change, and
639 needs to be recompiled along with the kernel. As this change breaks
640 the ABI, bump __FreeBSD_version to 800103.
643 Padding has been added to struct tcpcb, sackhint and tcpstat in
644 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
645 maintaining the ABI. However, this change breaks the ABI, so bump
646 __FreeBSD_version to 800102. User space tools that rely on the size of
647 any of these structs (e.g. sockstat) need to be recompiled.
650 The NFS_LEGACYRPC option has been removed along with the old kernel
651 RPC implementation that this option selected. Kernel configurations
652 may need to be adjusted.
655 The network interface device nodes at /dev/net/<interface> have been
656 removed. All ioctl operations can be performed the normal way using
657 routing sockets. The kqueue functionality can generally be replaced
658 with routing sockets.
661 The documentation from the FreeBSD Documentation Project (Handbook,
662 FAQ, etc.) is now installed via packages by sysinstall(8) and under
663 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
666 The ABI of various structures related to the SYSV IPC API have been
667 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
668 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
672 Layout of struct vnet has changed as routing related variables were
673 moved to their own Vimage module. Modules need to be recompiled. Bump
674 __FreeBSD_version to 800099.
677 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
678 respectively. As long as no more than 16 groups per process are used,
679 no changes should be visible. When more than 16 groups are used, old
680 binaries may fail if they call getgroups() or getgrouplist() with
681 statically sized storage. Recompiling will work around this, but
682 applications should be modified to use dynamically allocated storage
683 for group arrays as POSIX.1-2008 does not cap an implementation's
684 number of supported groups at NGROUPS_MAX+1 as previous versions did.
686 NFS and portalfs mounts may also be affected as the list of groups is
687 truncated to 16. Users of NFS who use more than 16 groups, should
688 take care that negative group permissions are not used on the exported
689 file systems as they will not be reliable unless a GSSAPI based
690 authentication method is used.
693 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
694 option compiles in the support for adaptive spinning for lockmgrs
695 which want to enable it. The lockinit() function now accepts the flag
696 LK_ADAPTIVE in order to make the lock object subject to adaptive
697 spinning when both held in write and read mode.
700 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
701 changed. User applications that use this ioctl need to be rebuilt.
704 The layout of struct thread has changed. Kernel and modules need to
708 The layout of structs ifnet, domain, protosw and vnet_net has changed.
709 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
712 window(1) has been removed from the base system. It can now be
713 installed from ports. The port is called misc/window.
716 The way we are storing and accessing `routing table' entries has
717 changed. Programs reading the FIB, like netstat, need to be
721 A new netisr implementation has been added for FreeBSD 8. Network
722 file system modules, such as igmp, ipdivert, and others, should be
724 Bump __FreeBSD_version to 800096.
727 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
731 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
732 Bump __FreeBSD_version to 800094.
735 Add mnt_xflag field to 'struct mount'. File system modules need to be
737 Bump __FreeBSD_version to 800093.
740 The compiling option ADAPTIVE_SX has been retired while it has been
741 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
742 The KPI for sx_init_flags() changes as accepting flags:
743 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
744 been introduced in order to handle the reversed logic.
745 Bump __FreeBSD_version to 800092.
748 Add support for hierarchical jails. Remove global securelevel.
749 Bump __FreeBSD_version to 800091.
752 The layout of struct vnet_net has changed, therefore modules
754 Bump __FreeBSD_version to 800090.
757 The newly imported zic(8) produces a new format in the output. Please
758 run tzsetup(8) to install the newly created data to /etc/localtime.
761 The sysctl tree for the usb stack has renamed from hw.usb2.* to
762 hw.usb.* and is now consistent again with previous releases.
765 802.11 monitor mode support was revised and driver api's were changed.
766 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
767 of DLT_IEEE802_11. No user-visible data structures were changed but
768 applications that use DLT_IEEE802_11 may require changes.
769 Bump __FreeBSD_version to 800088.
772 The layout of the following structs has changed: sysctl_oid,
773 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
774 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
775 panics may be experienced. World rebuild is required for
776 correctly checking networking state from userland.
777 Bump __FreeBSD_version to 800085.
780 MLDv2 and Source-Specific Multicast (SSM) have been merged
781 to the IPv6 stack. VIMAGE hooks are in but not yet used.
782 The implementation of SSM within FreeBSD's IPv6 stack closely
783 follows the IPv4 implementation.
785 For kernel developers:
787 * The most important changes are that the ip6_output() and
788 ip6_input() paths no longer take the IN6_MULTI_LOCK,
789 and this lock has been downgraded to a non-recursive mutex.
791 * As with the changes to the IPv4 stack to support SSM, filtering
792 of inbound multicast traffic must now be performed by transport
793 protocols within the IPv6 stack. This does not apply to TCP and
794 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
796 * The KPIs used by IPv6 multicast are similar to those used by
797 the IPv4 stack, with the following differences:
798 * im6o_mc_filter() is analogous to imo_multicast_filter().
799 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
800 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
801 * IN6_LOOKUP_MULTI() has been deprecated and removed.
802 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
803 for MLDv1 have an additional 'timer' argument which is used to
804 jitter the initial membership report for the solicited-node
805 multicast membership on-link.
806 * This is not strictly needed for MLDv2, which already jitters
807 its report transmissions. However, the 'timer' argument is
808 preserved in case MLDv1 is active on the interface.
810 * The KAME linked-list based IPv6 membership implementation has
811 been refactored to use a vector similar to that used by the IPv4
813 Code which maintains a list of its own multicast memberships
814 internally, e.g. carp, has been updated to reflect the new
817 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
818 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
819 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
820 implementation constraint which needs to be addressed in HEAD.
822 For application developers:
824 * The changes are broadly similar to those made for the IPv4
827 * The use of IPv4 and IPv6 multicast socket options on the same
828 socket, using mapped addresses, HAS NOT been tested or supported.
830 * There are a number of issues with the implementation of various
831 IPv6 multicast APIs which need to be resolved in the API surface
832 before the implementation is fully compatible with KAME userland
833 use, and these are mostly to do with interface index treatment.
835 * The literature available discusses the use of either the delta / ASM
836 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
837 using setsourcefilter(3)/getsourcefilter(3). For more information
838 please refer to RFC 3768, 'Socket Interface Extensions for
839 Multicast Source Filters'.
841 * Applications which use the published RFC 3678 APIs should be fine.
843 For systems administrators:
845 * The mtest(8) utility has been refactored to support IPv6, in
846 addition to IPv4. Interface addresses are no longer accepted
847 as arguments, their names must be used instead. The utility
848 will map the interface name to its first IPv4 address as
849 returned by getifaddrs(3).
851 * The ifmcstat(8) utility has also been updated to print the MLDv2
852 endpoint state and source filter lists via sysctl(3).
854 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
855 loopback of IPv6 multicast datagrams by default; it defaults to 1
856 to preserve the existing behaviour. Disabling multicast loopback is
857 recommended for optimal system performance.
859 * The IPv6 MROUTING code has been changed to examine this sysctl
860 instead of attempting to perform a group lookup before looping
861 back forwarded datagrams.
863 Bump __FreeBSD_version to 800084.
866 Implement low-level Bluetooth HCI API.
867 Bump __FreeBSD_version to 800083.
870 The layout of struct malloc_type, used by modules to register new
871 memory allocation types, has changed. Most modules will need to
872 be rebuilt or panics may be experienced.
873 Bump __FreeBSD_version to 800081.
876 Anticipate overflowing inp_flags - add inp_flags2.
877 This changes most offsets in inpcb, so checking v4 connection
878 state will require a world rebuild.
879 Bump __FreeBSD_version to 800080.
882 Add an llentry to struct route and struct route_in6. Modules
883 embedding a struct route will need to be recompiled.
884 Bump __FreeBSD_version to 800079.
887 The size of rt_metrics_lite and by extension rtentry has changed.
888 Networking administration apps will need to be recompiled.
889 The route command now supports show as an alias for get, weighting
890 of routes, sticky and nostick flags to alter the behavior of stateful
892 Bump __FreeBSD_version to 800078.
895 Do not use Giant for kbdmux(4) locking. This is wrong and
896 apparently causing more problems than it solves. This will
897 re-open the issue where interrupt handlers may race with
898 kbdmux(4) in polling mode. Typical symptoms include (but
899 not limited to) duplicated and/or missing characters when
900 low level console functions (such as gets) are used while
901 interrupts are enabled (for example geli password prompt,
902 mountroot prompt etc.). Disabling kbdmux(4) may help.
905 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
906 kernel modules referencing any of the above need to be recompiled.
907 Bump __FreeBSD_version to 800075.
910 GEOM_PART has become the default partition slicer for storage devices,
911 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
912 introduces some changes:
914 MSDOS/EBR: the devices created from MSDOS extended partition entries
915 (EBR) can be named differently than with GEOM_MBR and are now symlinks
916 to devices with offset-based names. fstabs may need to be modified.
918 BSD: the "geometry does not match label" warning is harmless in most
919 cases but it points to problems in file system misalignment with
920 disk geometry. The "c" partition is now implicit, covers the whole
921 top-level drive and cannot be (mis)used by users.
923 General: Kernel dumps are now not allowed to be written to devices
924 whose partition types indicate they are meant to be used for file
925 systems (or, in case of MSDOS partitions, as something else than
928 Most of these changes date approximately from 200812.
931 The uscanner(4) driver has been removed from the kernel. This follows
932 Linux removing theirs in 2.6 and making libusb the default interface
936 The multicast forwarding code has been cleaned up. netstat(1)
937 only relies on KVM now for printing bandwidth upcall meters.
938 The IPv4 and IPv6 modules are split into ip_mroute_mod and
939 ip6_mroute_mod respectively. The config(5) options for statically
940 compiling this code remain the same, i.e. 'options MROUTING'.
943 Support for the IFF_NEEDSGIANT network interface flag has been
944 removed, which means that non-MPSAFE network device drivers are no
945 longer supported. In particular, if_ar, if_sr, and network device
946 drivers from the old (legacy) USB stack can no longer be built or
950 POSIX.1 Native Language Support (NLS) has been enabled in libc and
951 a bunch of new language catalog files have also been added.
952 This means that some common libc messages are now localized and
953 they depend on the LC_MESSAGES environmental variable.
956 The k8temp(4) driver has been renamed to amdtemp(4) since
957 support for Family 10 and Family 11 CPU families was added.
960 IGMPv3 and Source-Specific Multicast (SSM) have been merged
961 to the IPv4 stack. VIMAGE hooks are in but not yet used.
963 For kernel developers, the most important changes are that the
964 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
965 and this lock has been downgraded to a non-recursive mutex.
967 Transport protocols (UDP, Raw IP) are now responsible for filtering
968 inbound multicast traffic according to group membership and source
969 filters. The imo_multicast_filter() KPI exists for this purpose.
970 Transports which do not use multicast (SCTP, TCP) already reject
971 multicast by default. Forwarding and receive performance may improve
972 as a mutex acquisition is no longer needed in the ip_input()
973 low-level input path. in_addmulti() and in_delmulti() are shimmed
974 to new KPIs which exist to support SSM in-kernel.
976 For application developers, it is recommended that loopback of
977 multicast datagrams be disabled for best performance, as this
978 will still cause the lock to be taken for each looped-back
979 datagram transmission. The net.inet.ip.mcast.loop sysctl may
980 be tuned to 0 to disable loopback by default; it defaults to 1
981 to preserve the existing behaviour.
983 For systems administrators, to obtain best performance with
984 multicast reception and multiple groups, it is always recommended
985 that a card with a suitably precise hash filter is used. Hash
986 collisions will still result in the lock being taken within the
987 transport protocol input path to check group membership.
989 If deploying FreeBSD in an environment with IGMP snooping switches,
990 it is recommended that the net.inet.igmp.sendlocal sysctl remain
991 enabled; this forces 224.0.0.0/24 group membership to be announced
994 The size of 'struct igmpstat' has changed; netstat needs to be
995 recompiled to reflect this.
996 Bump __FreeBSD_version to 800070.
999 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1000 updated to use it. This requires a buildworld/installworld in order to
1001 update the library and dependencies (usbconfig, etc). Its advisable to
1002 rebuild all ports which uses libusb. More specific directions are given
1003 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1004 libusb are no longer required and can be removed.
1007 A workaround is committed to allow the creation of System V shared
1008 memory segment of size > 2 GB on the 64-bit architectures.
1009 Due to a limitation of the existing ABI, the shm_segsz member
1010 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1011 wrong for large segments. Note that limits must be explicitly
1012 raised to allow such segments to be created.
1015 The layout of struct ifnet has changed, requiring a rebuild of all
1016 network device driver modules.
1019 The /dev handling for the new USB stack has changed, a
1020 buildworld/installworld is required for libusb20.
1023 The new USB2 stack has now been permanently moved in and all kernel and
1024 module names reverted to their previous values (eg, usb, ehci, ohci,
1025 ums, ...). The old usb stack can be compiled in by prefixing the name
1026 with the letter 'o', the old usb modules have been removed.
1027 Updating entry 20090216 for xorg and 20090215 for libmap may still
1031 The rc.conf(5) option if_up_delay has been renamed to
1032 defaultroute_delay to better reflect its purpose. If you have
1033 customized this setting in /etc/rc.conf you need to update it to
1037 xorg 7.4 wants to configure its input devices via hald which does not
1038 yet work with USB2. If the keyboard/mouse does not work in xorg then
1040 Option "AllowEmptyInput" "off"
1041 to your ServerLayout section. This will cause X to use the configured
1042 kbd and mouse sections from your xorg.conf.
1045 The GENERIC kernels for all architectures now default to the new USB2
1046 stack. No kernel config options or code have been removed so if a
1047 problem arises please report it and optionally revert to the old USB
1048 stack. If you are loading USB kernel modules or have a custom kernel
1049 that includes GENERIC then ensure that usb names are also changed over,
1050 eg uftdi -> usb2_serial_ftdi.
1052 Older programs linked against the ports libusb 0.1 need to be
1053 redirected to the new stack's libusb20. /etc/libmap.conf can
1055 # Map old usb library to new one for usb2 stack
1056 libusb-0.1.so.8 libusb20.so.1
1059 All USB ethernet devices now attach as interfaces under the name ueN
1060 (eg. ue0). This is to provide a predictable name as vendors often
1061 change usb chipsets in a product without notice.
1064 The ichsmb(4) driver has been changed to require SMBus slave
1065 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1066 All of the other SMBus controller drivers require left-justified
1067 slave addresses, so this change makes all the drivers provide the
1071 INET6 statistics (struct ip6stat) was updated.
1072 netstat(1) needs to be recompiled.
1075 NTFS has been removed from GENERIC kernel on amd64 to match
1076 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1077 will load ntfs.ko module automatically when NTFS support is
1078 actually needed, unless ntfs.ko is not installed or security
1079 level prohibits loading kernel modules. If either is the case,
1080 "options NTFS" has to be added into kernel config.
1083 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1084 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1085 800061. User space tools that rely on the size of struct tcpcb in
1086 tcp_var.h (e.g. sockstat) need to be recompiled.
1089 ng_tty(4) module updated to match the new TTY subsystem.
1090 Due to API change, user-level applications must be updated.
1091 New API support added to mpd5 CVS and expected to be present
1092 in next mpd5.3 release.
1095 With __FreeBSD_version 800060 the makefs tool is part of
1096 the base system (it was a port).
1099 The afdata and ifnet locks have been changed from mutexes to
1100 rwlocks, network modules will need to be re-compiled.
1103 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1104 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1105 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1106 architecture and 40 bytes on 64-bit architecture. The userland
1107 applications "arp" and "ndp" have been updated accordingly.
1108 The output from "netstat -r" shows only routing entries and
1109 none of the L2 information.
1112 __FreeBSD_version 800057 marks the switchover from the
1113 binary ath hal to source code. Users must add the line:
1115 options AH_SUPPORT_AR5416
1117 to their kernel config files when specifying:
1121 The ath_hal module no longer exists; the code is now compiled
1122 together with the driver in the ath module. It is now
1123 possible to tailor chip support (i.e. reduce the set of chips
1124 and thereby the code size); consult ath_hal(4) for details.
1127 __FreeBSD_version 800054 adds memory barriers to
1128 <machine/atomic.h>, new interfaces to ifnet to facilitate
1129 multiple hardware transmit queues for cards that support
1130 them, and a lock-less ring-buffer implementation to
1131 enable drivers to more efficiently manage queueing of
1135 A new version of ZFS (version 13) has been merged to -HEAD.
1136 This version has zpool attribute "listsnapshots" off by
1137 default, which means "zfs list" does not show snapshots,
1138 and is the same as Solaris behavior.
1141 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1144 The uhci, ohci, ehci and slhci USB Host controller drivers have
1145 been put into separate modules. If you load the usb module
1146 separately through loader.conf you will need to load the
1147 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1148 controller add the following to loader.conf:
1154 The ABI used by the PMC toolset has changed. Please keep
1155 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1159 atapci kernel module now includes only generic PCI ATA
1160 driver. AHCI driver moved to ataahci kernel module.
1161 All vendor-specific code moved into separate kernel modules:
1162 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1163 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1164 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1165 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1168 The TTY subsystem of the kernel has been replaced by a new
1169 implementation, which provides better scalability and an
1170 improved driver model. Most common drivers have been migrated to
1171 the new TTY subsystem, while others have not. The following
1172 drivers have not yet been ported to the new TTY layer:
1175 cy, digi, rc, rp, sio
1181 ng_h4, ng_tty, ppp, sl, snp
1183 Adding these drivers to your kernel configuration file shall
1184 cause compilation to fail.
1187 ntpd has been upgraded to 4.2.4p5.
1190 OpenSSH has been upgraded to 5.1p1.
1192 For many years, FreeBSD's version of OpenSSH preferred DSA
1193 over RSA for host and user authentication keys. With this
1194 upgrade, we've switched to the vendor's default of RSA over
1195 DSA. This may cause upgraded clients to warn about unknown
1196 host keys even for previously known hosts. Users should
1197 follow the usual procedure for verifying host keys before
1198 accepting the RSA key.
1200 This can be circumvented by setting the "HostKeyAlgorithms"
1201 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1204 Please note that the sequence of keys offered for
1205 authentication has been changed as well. You may want to
1206 specify IdentityFile in a different order to revert this
1210 The sio(4) driver has been removed from the i386 and amd64
1211 kernel configuration files. This means uart(4) is now the
1212 default serial port driver on those platforms as well.
1214 To prevent collisions with the sio(4) driver, the uart(4) driver
1215 uses different names for its device nodes. This means the
1216 onboard serial port will now most likely be called "ttyu0"
1217 instead of "ttyd0". You may need to reconfigure applications to
1218 use the new device names.
1220 When using the serial port as a boot console, be sure to update
1221 /boot/device.hints and /etc/ttys before booting the new kernel.
1222 If you forget to do so, you can still manually specify the hints
1223 at the loader prompt:
1225 set hint.uart.0.at="isa"
1226 set hint.uart.0.port="0x3F8"
1227 set hint.uart.0.flags="0x10"
1228 set hint.uart.0.irq="4"
1232 The gpt(8) utility has been removed. Use gpart(8) to partition
1236 The version that Linuxulator emulates was changed from 2.4.2
1237 to 2.6.16. If you experience any problems with Linux binaries
1238 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1239 if it fixes the problem contact emulation mailing list.
1242 ISDN4BSD (I4B) was removed from the src tree. You may need to
1243 update a your kernel configuration and remove relevant entries.
1246 I have checked in code to support multiple routing tables.
1247 See the man pages setfib(1) and setfib(2).
1248 This is a hopefully backwards compatible version,
1249 but to make use of it you need to compile your kernel
1250 with options ROUTETABLES=2 (or more up to 16).
1253 The 802.11 wireless support was redone to enable multi-bss
1254 operation on devices that are capable. The underlying device
1255 is no longer used directly but instead wlanX devices are
1256 cloned with ifconfig. This requires changes to rc.conf files.
1257 For example, change:
1258 ifconfig_ath0="WPA DHCP"
1261 ifconfig_wlan0="WPA DHCP"
1262 see rc.conf(5) for more details. In addition, mergemaster of
1263 /etc/rc.d is highly recommended. Simultaneous update of userland
1264 and kernel wouldn't hurt either.
1266 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1267 modules were merged into the base wlan module. All references
1268 to these modules (e.g. in kernel config files) must be removed.
1271 psm(4) has gained write(2) support in native operation level.
1272 Arbitrary commands can be written to /dev/psm%d and status can
1273 be read back from it. Therefore, an application is responsible
1274 for status validation and error recovery. It is a no-op in
1275 other operation levels.
1278 Support for KSE threading has been removed from the kernel. To
1279 run legacy applications linked against KSE libmap.conf may
1280 be used. The following libmap.conf may be used to ensure
1281 compatibility with any prior release:
1283 libpthread.so.1 libthr.so.1
1284 libpthread.so.2 libthr.so.2
1285 libkse.so.3 libthr.so.3
1288 The layout of struct vmspace has changed. This affects libkvm
1289 and any executables that link against libkvm and use the
1290 kvm_getprocs() function. In particular, but not exclusively,
1291 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1292 The effects are minimal, but it's advisable to upgrade world
1296 The latest em driver no longer has support in it for the
1297 82575 adapter, this is now moved to the igb driver. The
1298 split was done to make new features that are incompatible
1299 with older hardware easier to do.
1302 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1303 likewise the kernel option is now GEOM_LINUX_LVM.
1306 The default NFS mount mode has changed from UDP to TCP for
1307 increased reliability. If you rely on (insecurely) NFS
1308 mounting across a firewall you may need to update your
1312 Belatedly note the addition of m_collapse for compacting
1316 The fts(3) structures have been changed to use adequate
1317 integer types for their members and so to be able to cope
1318 with huge file trees. The old fts(3) ABI is preserved
1319 through symbol versioning in libc, so third-party binaries
1320 using fts(3) should still work, although they will not take
1321 advantage of the extended types. At the same time, some
1322 third-party software might fail to build after this change
1323 due to unportable assumptions made in its source code about
1324 fts(3) structure members. Such software should be fixed
1325 by its vendor or, in the worst case, in the ports tree.
1326 FreeBSD_version 800015 marks this change for the unlikely
1327 case that a portable fix is impossible.
1330 To upgrade to -current after this date, you must be running
1331 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1332 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1335 The ADAPTIVE_GIANT kernel option has been retired because its
1336 functionality is the default now.
1339 The AT keyboard emulation of sunkbd(4) has been turned on
1340 by default. In order to make the special symbols of the Sun
1341 keyboards driven by sunkbd(4) work under X these now have
1342 to be configured the same way as Sun USB keyboards driven
1343 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1345 Option "XkbLayout" "us"
1346 Option "XkbRules" "xorg"
1347 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1350 It has been decided that it is desirable to provide ABI
1351 backwards compatibility to the FreeBSD 4/5/6 versions of the
1352 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1353 broken with the introduction of PCI domain support (see the
1354 20070930 entry). Unfortunately, this required the ABI of
1355 PCIOCGETCONF to be broken again in order to be able to
1356 provide backwards compatibility to the old version of that
1357 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1358 again. As for prominent ports this affects neither pciutils
1359 nor xorg-server this time, the hal port needs to be rebuilt
1363 The misnamed kthread_create() and friends have been renamed
1364 to kproc_create() etc. Many of the callers already
1365 used kproc_start()..
1366 I will return kthread_create() and friends in a while
1367 with implementations that actually create threads, not procs.
1368 Renaming corresponds with version 800002.
1377 Avoid using make -j when upgrading. While generally safe, there are
1378 sometimes problems using -j to upgrade. If your upgrade fails with
1379 -j, please try again without -j. From time to time in the past there
1380 have been problems using -j with buildworld and/or installworld. This
1381 is especially true when upgrading between "distant" versions (eg one
1382 that cross a major release boundary or several minor releases, or when
1383 several months have passed on the -current branch).
1385 Sometimes, obscure build problems are the result of environment
1386 poisoning. This can happen because the make utility reads its
1387 environment when searching for values for global variables. To run
1388 your build attempts in an "environmental clean room", prefix all make
1389 commands with 'env -i '. See the env(1) manual page for more details.
1391 When upgrading from one major version to another it is generally best
1392 to upgrade to the latest code in the currently installed branch first,
1393 then do an upgrade to the new branch. This is the best-tested upgrade
1394 path, and has the highest probability of being successful. Please try
1395 this approach before reporting problems with a major version upgrade.
1399 When upgrading the boot ZFS pool to a new version, always follow
1402 1.) recompile and reinstall the ZFS boot loader and boot block
1403 (this is part of "make buildworld" and "make installworld")
1405 2.) update the ZFS boot block on your boot drive
1407 The following example updates the ZFS boot block on the first
1408 partition (freebsd-boot) of a GPT partitioned drive ad0:
1409 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1411 Non-boot pools do not need these updates.
1415 If you are updating from a prior version of FreeBSD (even one just
1416 a few days old), you should follow this procedure. It is the most
1417 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1419 make kernel-toolchain
1420 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1421 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1423 To test a kernel once
1424 ---------------------
1425 If you just want to boot a kernel once (because you are not sure
1426 if it works, or if you want to boot a known bad kernel to provide
1427 debugging information) run
1428 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1429 nextboot -k testkernel
1431 To just build a kernel when you know that it won't mess you up
1432 --------------------------------------------------------------
1433 This assumes you are already running a CURRENT system. Replace
1434 ${arch} with the architecture of your machine (e.g. "i386",
1435 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1437 cd src/sys/${arch}/conf
1438 config KERNEL_NAME_HERE
1439 cd ../compile/KERNEL_NAME_HERE
1444 If this fails, go to the "To build a kernel" section.
1446 To rebuild everything and install it on the current system.
1447 -----------------------------------------------------------
1448 # Note: sometimes if you are running current you gotta do more than
1449 # is listed here if you are upgrading from a really old current.
1451 <make sure you have good level 0 dumps>
1453 make kernel KERNCONF=YOUR_KERNEL_HERE
1455 <reboot in single user> [3]
1463 To cross-install current onto a separate partition
1464 --------------------------------------------------
1465 # In this approach we use a separate partition to hold
1466 # current's root, 'usr', and 'var' directories. A partition
1467 # holding "/", "/usr" and "/var" should be about 2GB in
1470 <make sure you have good level 0 dumps>
1473 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1474 <maybe newfs current's root partition>
1475 <mount current's root partition on directory ${CURRENT_ROOT}>
1476 make installworld DESTDIR=${CURRENT_ROOT}
1477 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1478 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1479 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1480 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1481 <reboot into current>
1482 <do a "native" rebuild/install as described in the previous section>
1483 <maybe install compatibility libraries from ports/misc/compat*>
1487 To upgrade in-place from stable to current
1488 ----------------------------------------------
1489 <make sure you have good level 0 dumps>
1491 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1493 <reboot in single user> [3]
1500 Make sure that you've read the UPDATING file to understand the
1501 tweaks to various things you need. At this point in the life
1502 cycle of current, things change often and you are on your own
1503 to cope. The defaults can also change, so please read ALL of
1504 the UPDATING entries.
1506 Also, if you are tracking -current, you must be subscribed to
1507 freebsd-current@freebsd.org. Make sure that before you update
1508 your sources that you have read and understood all the recent
1509 messages there. If in doubt, please track -stable which has
1510 much fewer pitfalls.
1512 [1] If you have third party modules, such as vmware, you
1513 should disable them at this point so they don't crash your
1516 [3] From the bootblocks, boot -s, and then do
1521 adjkerntz -i # if CMOS is wall time
1522 Also, when doing a major release upgrade, it is required that
1523 you boot into single user mode to do the installworld.
1525 [4] Note: This step is non-optional. Failure to do this step
1526 can result in a significant reduction in the functionality of the
1527 system. Attempting to do it by hand is not recommended and those
1528 that pursue this avenue should read this file carefully, as well
1529 as the archives of freebsd-current and freebsd-hackers mailing lists
1530 for potential gotchas. The -U option is also useful to consider.
1531 See mergemaster(8) for more information.
1533 [5] Usually this step is a noop. However, from time to time
1534 you may need to do this if you get unknown user in the following
1535 step. It never hurts to do it all the time. You may need to
1536 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1537 install) after the buildworld before this step if you last updated
1538 from current before 20020224 or from -stable before 20020408.
1540 [6] This only deletes old files and directories. Old libraries
1541 can be deleted by "make delete-old-libs", but you have to make
1542 sure that no program is using those libraries anymore.
1544 [8] In order to have a kernel that can run the 4.x binaries needed to
1545 do an installworld, you must include the COMPAT_FREEBSD4 option in
1546 your kernel. Failure to do so may leave you with a system that is
1547 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1548 required to run the 5.x binaries on more recent kernels. And so on
1549 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1551 Make sure that you merge any new devices from GENERIC since the
1552 last time you updated your kernel config file.
1554 [9] When checking out sources, you must include the -P flag to have
1555 cvs prune empty directories.
1557 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1558 "?=" instead of the "=" assignment operator, so that buildworld can
1559 override the CPUTYPE if it needs to.
1561 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1562 not on the command line, or in /etc/make.conf. buildworld will
1563 warn if it is improperly defined.
1566 This file contains a list, in reverse chronological order, of major
1567 breakages in tracking -current. It is not guaranteed to be a complete
1568 list of such breakages, and only contains entries since October 10, 2007.
1569 If you need to see UPDATING entries from before that date, you will need
1570 to fetch an UPDATING file from an older FreeBSD release.
1572 Copyright information:
1574 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1576 Redistribution, publication, translation and use, with or without
1577 modification, in full or in part, in any form or format of this
1578 document are permitted without further permission from the author.
1580 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1581 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1582 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1583 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1584 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1585 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1586 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1587 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1588 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1589 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1590 POSSIBILITY OF SUCH DAMAGE.
1592 Contact Warner Losh if you have any questions about your use of