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