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.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITHOUT_CLANG_IS_CC to
16 bootstrap to tip of head, and then rebuild without those options. The bootstrap
17 process from older version of current is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 10.x IS SLOW:
20 FreeBSD 10.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 Legacy ATA stack, disabled and replaced by new CAM-based one since
36 FreeBSD 9.0, completely removed from the sources. Kernel modules
37 atadisk and atapi*, user-level tools atacontrol and burncd are
38 removed. Kernel option `options ATA_CAM` is now permanently enabled
42 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
43 and socketpair(2). Software, in particular Kerberos, may
44 automatically detect and use these during building. The resulting
45 binaries will not work on older kernels.
48 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
49 information, see the respective 20130304 entry).
52 Recent commits to callout(9) changed the size of struct callout,
53 so the KBI is probably heavily disturbed. Also, some functions
54 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
55 by macros. Every kernel module using it won't load, so rebuild
58 The ctl device has been re-enabled in GENERIC for i386 and amd64,
59 but does not initialize by default (because of the new CTL_DISABLE
60 option) to save memory. To re-enable it, remove the CTL_DISABLE
61 option from the kernel config file or set kern.cam.ctl.disable=0
65 The ctl device has been disabled in GENERIC for i386 and amd64.
66 This was done due to the extra memory being allocated at system
67 initialisation time by the ctl driver which was only used if
68 a CAM target device was created. This makes a FreeBSD system
69 unusable on 128MB or less of RAM.
72 A new compression method (lz4) has been merged to -HEAD. Please
73 refer to zpool-features(7) for more information.
75 Please refer to the "ZFS notes" section of this file for information
76 on upgrading boot ZFS pools.
79 A BSD-licensed patch(1) variant has been added and is installed
80 as bsdpatch, being the GNU version the default patch.
81 To inverse the logic and use the BSD-licensed one as default,
82 while having the GNU version installed as gnupatch, rebuild
83 and install world with the WITH_BSD_PATCH knob set.
86 The install(1) option -M has changed meaning and now takes an
87 argument that is a file or path to append logs to. In the
88 unlikely event that -M was the last option on the command line
89 and the command line contained at least two files and a target
90 directory the first file will have logs appended to it. The -M
91 option served little practical purpose in the last decade so its
92 use is expected to be extremely rare.
95 After switching to Clang as the default compiler some users of ZFS
96 on i386 systems started to experience stack overflow kernel panics.
97 Please consider using 'options KSTACK_PAGES=4' in such configurations.
100 GEOM_LABEL now mangles label names read from file system metadata.
101 Mangling affect labels containing spaces, non-printable characters,
102 '%' or '"'. Device names in /etc/fstab and other places may need to
106 By default, only the 10 most recent kernel dumps will be saved. To
107 restore the previous behaviour (no limit on the number of kernel dumps
108 stored in the dump directory) add the following line to /etc/rc.conf:
113 With the addition of auditdistd(8), a new auditdistd user is now
114 depended on during installworld. "mergemaster -p" can be used to add
115 the user prior to installworld, as documented in the handbook.
118 The sin6_scope_id member variable in struct sockaddr_in6 is now
119 filled by the kernel before passing the structure to the userland via
120 sysctl or routing socket. This means the KAME-specific embedded scope
121 id in sin6_addr.s6_addr[2] is always cleared in userland application.
122 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
123 __FreeBSD_version is bumped to 1000025.
126 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
127 This means that the world and kernel will be compiled with clang
128 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
129 and /usr/bin/cpp. To disable this behavior and revert to building
130 with gcc, compile with WITHOUT_CLANG_IS_CC.
133 The IPFIREWALL_FORWARD kernel option has been removed. Its
134 functionality now turned on by default.
137 The ZERO_COPY_SOCKET kernel option has been removed and
138 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
139 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
140 mechanism which is not safe and may result in kernel crashes.
141 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
142 driver supports disposeable external page sized mbuf storage.
143 Proper replacements for both zero-copy mechanisms are under
144 consideration and will eventually lead to complete removal
145 of the two kernel options.
148 The IPv4 network stack has been converted to network byte
149 order. The following modules need to be recompiled together
150 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
151 pf(4), ipfw(4), ng_ipfw(4), stf(4).
154 Support for non-MPSAFE filesystems was removed from VFS. The
155 VFS_VERSION was bumped, all filesystem modules shall be
159 All the non-MPSAFE filesystems have been disconnected from
160 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
161 portalfs, smbfs, xfs.
164 The interface cloning API and ABI has changed. The following
165 modules need to be recompiled together with kernel:
166 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
167 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
168 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
171 The sdhci driver was split in two parts: sdhci (generic SD Host
172 Controller logic) and sdhci_pci (actual hardware driver).
173 No kernel config modifications are required, but if you
174 load sdhc as a module you must switch to sdhci_pci instead.
177 Import the FUSE kernel and userland support into base system.
180 The GNU sort(1) program has been removed since the BSD-licensed
181 sort(1) has been the default for quite some time and no serious
182 problems have been reported. The corresponding WITH_GNU_SORT
186 The pfil(9) API/ABI for AF_INET family has been changed. Packet
187 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
191 The net80211(4) ABI has been changed to allow for improved driver
192 PS-POLL and power-save support. All wireless drivers need to be
193 recompiled to work with the new kernel.
196 The random(4) support for the VIA hardware random number
197 generator (`PADLOCK') is no longer enabled unconditionally.
198 Add the PADLOCK_RNG option in the custom kernel config if
199 needed. The GENERIC kernels on i386 and amd64 do include the
200 option, so the change only affects the custom kernel
204 The pf(4) packet filter ABI has been changed. pfctl(8) and
205 snmp_pf module need to be recompiled to work with new kernel.
208 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
209 to -HEAD. Pools that have empty_bpobj in active state can not be
210 imported read-write with ZFS implementations that do not support
211 this feature. For more information read the zpool-features(5)
215 The sparc64 ZFS loader has been changed to no longer try to auto-
216 detect ZFS providers based on diskN aliases but now requires these
217 to be explicitly listed in the OFW boot-device environment variable.
220 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
221 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
222 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
225 The following sysctls and tunables have been renamed for consistency
226 with other variables:
227 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
228 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
231 The sort utility has been replaced with BSD sort. For now, GNU sort
232 is also available as "gnusort" or the default can be set back to
233 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
234 installed as "bsdsort".
237 A new version of ZFS (pool version 5000) has been merged to -HEAD.
238 Starting with this version the old system of ZFS pool versioning
239 is superseded by "feature flags". This concept enables forward
240 compatibility against certain future changes in functionality of ZFS
241 pools. The first read-only compatible "feature flag" for ZFS pools
242 is named "com.delphix:async_destroy". For more information
243 read the new zpool-features(5) manual page.
244 Please refer to the "ZFS notes" section of this file for information
245 on upgrading boot ZFS pools.
248 The malloc(3) implementation embedded in libc now uses sources imported
249 as contrib/jemalloc. The most disruptive API change is to
250 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
251 delete it prior to installworld, and optionally re-create it using the
252 new format after rebooting. See malloc.conf(5) for details
253 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
257 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
258 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
259 now spelled mips. This is to aid compatibility with third-party
260 software that expects this naming scheme in uname(3). Little-endian
261 settings are unchanged.
264 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
268 Now unix domain sockets behave "as expected" on nullfs(5). Previously
269 nullfs(5) did not pass through all behaviours to the underlying layer,
270 as a result if we bound to a socket on the lower layer we could connect
271 only to the lower path; if we bound to the upper layer we could connect
272 only to the upper path. The new behavior is one can connect to both the
273 lower and the upper paths regardless what layer path one binds to.
276 The getifaddrs upgrade path broken with 20111215 has been restored.
277 If you have upgraded in between 20111215 and 20120209 you need to
278 recompile libc again with your kernel. You still need to recompile
279 world to be able to configure CARP but this restriction already
283 The set_rcvar() function has been removed from /etc/rc.subr. All
284 base and ports rc.d scripts have been updated, so if you have a
285 port installed with a script in /usr/local/etc/rc.d you can either
286 hand-edit the rcvar= line, or reinstall the port.
288 An easy way to handle the mass-update of /etc/rc.d:
289 rm /etc/rc.d/* && mergemaster -i
292 panic(9) now stops other CPUs in the SMP systems, disables interrupts
293 on the current CPU and prevents other threads from running.
294 This behavior can be reverted using the kern.stop_scheduler_on_panic
296 The new behavior can be incompatible with kern.sync_on_panic.
299 The carp(4) facility has been changed significantly. Configuration
300 of the CARP protocol via ifconfig(8) has changed, as well as format
301 of CARP events submitted to devd(8) has changed. See manual pages
302 for more information. The arpbalance feature of carp(4) is currently
303 not supported anymore.
305 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
306 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
307 need to be recompiled.
310 The acpi_wmi(4) status device /dev/wmistat has been renamed to
314 The option VFS_ALLOW_NONMPSAFE option has been added in order to
315 explicitely support non-MPSAFE filesystems.
316 It is on by default for all supported platform at this present
320 The broken amd(4) driver has been replaced with esp(4) in the amd64,
321 i386 and pc98 GENERIC kernel configuration files.
324 sysinstall has been removed
327 The stable/9 branch created in subversion. This corresponds to the
328 RELENG_9 branch in CVS.
331 This commit modifies vfs_register() so that it uses a hash
332 calculation to set vfc_typenum, which is enabled by default.
333 The first time a system is booted after this change, the
334 vfc_typenum values will change for all file systems. The
335 main effect of this is a change to the NFS server file handles
336 for file systems that use vfc_typenum in their fsid, such as ZFS.
337 It will, however, prevent vfc_typenum from changing when file
338 systems are loaded in a different order for subsequent reboots.
339 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
340 until you are ready to remount all NFS clients after a reboot.
343 Bump the shared library version numbers for libraries that
344 do not use symbol versioning, have changed the ABI compared
345 to stable/8 and which shared library version was not bumped.
346 Done as part of 9.0-RELEASE cycle.
349 During the merge of Capsicum features, the fget(9) KPI was modified.
350 This may require the rebuilding of out-of-tree device drivers --
351 issues have been reported specifically with the nVidia device driver.
352 __FreeBSD_version is bumped to 900041.
354 Also, there is a period between 20110811 and 20110814 where the
355 special devices /dev/{stdin,stdout,stderr} did not work correctly.
356 Building world from a kernel during that window may not work.
359 The packet filter (pf) code has been updated to OpenBSD 4.5.
360 You need to update userland tools to be in sync with kernel.
361 This update breaks backward compatibility with earlier pfsync(4)
362 versions. Care must be taken when updating redundant firewall setups.
365 The following sysctls and tunables are retired on x86 platforms:
367 machdep.hlt_logical_cpus
368 The following sysctl is retired:
369 machdep.hyperthreading_allowed
370 The sysctls were supposed to provide a way to dynamically offline and
371 online selected CPUs on x86 platforms, but the implementation has not
372 been reliable especially with SCHED_ULE scheduler.
373 machdep.hyperthreading_allowed tunable is still available to ignore
374 hyperthreading CPUs at OS level.
375 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
376 where X is an APIC ID of a CPU. Be advised, though, that disabling
377 CPUs in non-uniform fashion will result in non-uniform topology and
378 may lead to sub-optimal system performance with SCHED_ULE, which is
382 cpumask_t type is retired and cpuset_t is used in order to describe
386 Changes to ifconfig(8) for dynamic address family detection mandate
387 that you are running a kernel of 20110525 or later. Make sure to
388 follow the update procedure to boot a new kernel before installing
392 Support for sun4v architecture is officially dropped
395 Several KPI breaking changes have been committed to the mii(4) layer,
396 the PHY drivers and consequently some Ethernet drivers using mii(4).
397 This means that miibus.ko and the modules of the affected Ethernet
398 drivers need to be recompiled.
400 Note to kernel developers: Given that the OUI bit reversion problem
401 was fixed as part of these changes all mii(4) commits related to OUIs,
402 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
403 handling, no longer can be merged verbatim to stable/8 and previous
407 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
408 into their kernel configurations along with 'device pci'.
411 The default NFS client is now the new NFS client, so fstype "newnfs"
412 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
413 Although mounts via fstype "nfs" will usually work without userland
414 changes, it is recommended that the mount(8) and mount_nfs(8)
415 commands be rebuilt from sources and that a link to mount_nfs called
416 mount_oldnfs be created. The new client is compiled into the
417 kernel with "options NFSCL" and this is needed for diskless root
418 file systems. The GENERIC kernel configs have been changed to use
419 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
420 To use the regular/old client, you can "mount -t oldnfs ...". For
421 a diskless root file system, you must also include a line like:
423 vfs.root.mountfrom="oldnfs:"
425 in the boot/loader.conf on the root fs on the NFS server to make
426 a diskless root fs use the old client.
429 The GENERIC kernels for all architectures now default to the new
430 CAM-based ATA stack. It means that all legacy ATA drivers were
431 removed and replaced by respective CAM drivers. If you are using
432 ATA device names in /etc/fstab or other places, make sure to update
433 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
434 where 'Y's are the sequential numbers starting from zero for each type
435 in order of detection, unless configured otherwise with tunables,
436 see cam(4)). There will be symbolic links created in /dev/ to map
437 old adX devices to the respective adaY. They should provide basic
438 compatibility for file systems mounting in most cases, but they do
439 not support old user-level APIs and do not have respective providers
440 in GEOM. Consider using updated management tools with new device names.
442 It is possible to load devices ahci, ata, siis and mvs as modules,
443 but option ATA_CAM should remain in kernel configuration to make ata
444 module work as CAM driver supporting legacy ATA controllers. Device ata
445 still can be used in modular fashion (atacore + ...). Modules atadisk
446 and atapi* are not used and won't affect operation in ATA_CAM mode.
447 Note that to use CAM-based ATA kernel should include CAM devices
448 scbus, pass, da (or explicitly ada), cd and optionally others. All of
449 them are parts of the cam module.
451 ataraid(4) functionality is now supported by the RAID GEOM class.
452 To use it you can load geom_raid kernel module and use graid(8) tool
453 for management. Instead of /dev/arX device names, use /dev/raid/rX.
455 No kernel config options or code have been removed, so if a problem
456 arises, please report it and optionally revert to the old ATA stack.
457 In order to do it you can remove from the kernel config:
462 , and instead add back:
463 device atadisk # ATA disk drives
464 device ataraid # ATA RAID drives
465 device atapicd # ATAPI CDROM drives
466 device atapifd # ATAPI floppy drives
467 device atapist # ATAPI tape drives
470 The default NFS server has been changed to the new server, which
471 was referred to as the experimental server. If you need to switch
472 back to the old NFS server, you must now put the "-o" option on
473 both the mountd and nfsd commands. This can be done using the
474 mountd_flags and nfs_server_flags rc.conf variables until an
475 update to the rc scripts is committed, which is coming soon.
478 The GNU Objective-C runtime library (libobjc), and other Objective-C
479 related components have been removed from the base system. If you
480 require an Objective-C library, please use one of the available ports.
483 ath(4) has been split into bus- and device- modules. if_ath contains
484 the HAL, the TX rate control and the network device code. if_ath_pci
485 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
486 contains the AHB glue. Users need to load both if_ath_pci and if_ath
487 in order to use ath on everything else.
489 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
490 need to load if_ath and if_ath_pci for ath(4) operation.
493 As part of the replacement of sysinstall, the process of building
494 release media has changed significantly. For details, please re-read
495 release(7), which has been updated to reflect the new build process.
498 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
499 is the last available version under GPLv2. It brings a number of new
500 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
501 4.1 and SSE 4.2), better support for powerpc64, a number of new
502 directives, and lots of other small improvements. See the ChangeLog
503 file in contrib/binutils for the full details.
506 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
507 compliant, and will now use half of hash for authentication.
508 This will break interoperability with all stacks (including all
509 actual FreeBSD versions) who implement
510 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
512 The only workaround with such peers is to use another HMAC
513 algorithm for IPsec ("phase 2") authentication.
516 Remove the uio_yield prototype and symbol. This function has
517 been misnamed since it was introduced and should not be
518 globally exposed with this name. The equivalent functionality
519 is now available using kern_yield(curthread->td_user_pri).
520 The function remains undocumented.
523 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
524 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
525 for scalar sysctls is defined but disabled. Code that needs
526 UQUAD to pass the type checking that must compile on older
527 systems where the define is not present can check against
528 __FreeBSD_version >= 900030.
530 The system dialog(1) has been replaced with a new version previously
531 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
532 with the previous version, but the libdialog associated with it has
533 a largely incompatible API. As such, the original version of libdialog
534 will be kept temporarily as libodialog, until its base system consumers
535 are replaced or updated. Bump __FreeBSD_version to 900030.
538 If you are trying to run make universe on a -stable system, and you get
539 the following warning:
540 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
541 unknown. config(8) likely too old."
542 or something similar to it, then you must upgrade your -stable system
543 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
544 stable/8) or build the config from the latest stable/8 branch and
545 install it on your system.
547 Prior to this date, building a current universe on 8-stable system from
548 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
549 error in the first kernel build phase. A new config on those old
550 systems will fix that problem for older versions of -current.
553 The TCP stack has been modified to allow Khelp modules to interact with
554 it via helper hook points and store per-connection data in the TCP
555 control block. Bump __FreeBSD_version to 900029. User space tools that
556 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
560 Generic IEEE 802.3 annex 31B full duplex flow control support has been
561 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
562 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
563 to take advantage of it instead of using custom implementations. This
564 means that these drivers now no longer unconditionally advertise
565 support for flow control but only do so if flow control is a selected
566 media option. This was implemented in the generic support that way in
567 order to allow flow control to be switched on and off via ifconfig(8)
568 with the PHY specific default to typically off in order to protect
569 from unwanted effects. Consequently, if you used flow control with
570 one of the above mentioned drivers you now need to explicitly enable
572 ifconfig bge0 media auto mediaopt flowcontrol
574 Along with the above mentioned changes generic support for setting
575 1000baseT master mode also has been added and brgphy(4), ciphy(4),
576 e1000phy(4) as well as ip1000phy(4) have been converted to take
577 advantage of it. This means that these drivers now no longer take the
578 link0 parameter for selecting master mode but the master media option
579 has to be used instead, for example like in the following:
580 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
582 Selection of master mode now is also available with all other PHY
583 drivers supporting 1000baseT.
586 The TCP stack has received a significant update to add support for
587 modularised congestion control and generally improve the clarity of
588 congestion control decisions. Bump __FreeBSD_version to 900025. User
589 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
590 sockstat) need to be recompiled.
593 The man(1) utility has been replaced by a new version that no longer
594 uses /etc/manpath.config. Please consult man.conf(5) for how to
595 migrate local entries to the new format.
598 The copyright strings printed by login(1) and sshd(8) at the time of a
599 new connection have been removed to follow other operating systems and
603 A workaround for a fixed ld bug has been removed in kernel code,
604 so make sure that your system ld is built from sources after
605 revision 210245 from 2010-07-19 (r211583 if building head kernel
606 on stable/8, r211584 for stable/7; both from 2010-08-21).
607 A symptom of incorrect ld version is different addresses for
608 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
611 The $ipv6_prefer variable in rc.conf(5) has been split into
612 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
614 The $ip6addrctl_policy is a variable to choose a pre-defined
615 address selection policy set by ip6addrctl(8). A value
616 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
619 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
620 flag (see an entry of 20090926) is set on an interface with no
621 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
622 security reason. If you want IPv6 link-local address on all
623 interfaces by default, set this to "YES".
625 The old ipv6_prefer="YES" is equivalent to
626 ipv6_activate_all_interfaces="YES" and
627 ip6addrctl_policy="ipv6_prefer".
630 DTrace has grown support for userland tracing. Due to this, DTrace is
631 now i386 and amd64 only.
632 dtruss(1) is now installed by default on those systems and a new
633 kernel module is needed for userland tracing: fasttrap.
634 No changes to your kernel config file are necessary to enable
635 userland tracing, but you might consider adding 'STRIP=' and
636 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
637 to have informative userland stack traces in DTrace (ustack).
640 The acpi_aiboost(4) driver has been removed in favor of the new
641 aibs(4) driver. You should update your kernel configuration file.
644 BSD grep has been imported to the base system and it is built by
645 default. It is completely BSD licensed, highly GNU-compatible, uses
646 less memory than its GNU counterpart and has a small codebase.
647 However, it is slower than its GNU counterpart, which is mostly
648 noticeable for larger searches, for smaller ones it is measurable
649 but not significant. The reason is complex, the most important factor
650 is that we lack a modern and efficient regex library and GNU
651 overcomes this by optimizing the searches internally. Future work
652 on improving the regex performance is planned, for the meantime,
653 users that need better performance, can build GNU grep instead by
654 setting the WITH_GNU_GREP knob.
657 Due to the import of powerpc64 support, all existing powerpc kernel
658 configuration files must be updated with a machine directive like this:
659 machine powerpc powerpc
661 In addition, an updated config(8) is required to build powerpc kernels
665 A new version of ZFS (version 15) has been merged to -HEAD.
666 This version uses a python library for the following subcommands:
667 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
668 For full functionality of these commands the following port must
669 be installed: sysutils/py-zfs
672 'vm_page's are now hashed by physical address to an array of mutexes.
673 Currently this is only used to serialize access to hold_count. Over
674 time the page queue mutex will be peeled away. This changes the size
675 of pmap on every architecture. And requires all callers of vm_page_hold
676 and vm_page_unhold to be updated.
679 WITH_CTF can now be specified in src.conf (not recommended, there
680 are some problems with static executables), make.conf (would also
681 affect ports which do not use GNU make and do not override the
682 compile targets) or in the kernel config (via "makeoptions
684 When WITH_CTF was specified there before this was silently ignored,
685 so make sure that WITH_CTF is not used in places which could lead
686 to unwanted behavior.
689 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
690 to allow 32-bit compatibility on non-x86 platforms. All kernel
691 configurations on amd64 and ia64 platforms using these options must
692 be modified accordingly.
695 The utmp user accounting database has been replaced with utmpx,
696 the user accounting interface standardized by POSIX.
697 Unfortunately the semantics of utmp and utmpx don't match,
698 making it practically impossible to support both interfaces.
699 The user accounting database is used by tools like finger(1),
700 last(1), talk(1), w(1) and ac(8).
702 All applications in the base system use utmpx. This means only
703 local binaries (e.g. from the ports tree) may still use these
704 utmp database files. These applications must be rebuilt to make
707 After the system has been upgraded, it is safe to remove the old
708 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
709 assuming their contents is of no importance anymore. Old wtmp
710 databases can only be used by last(1) and ac(8) after they have
711 been converted to the new format using wtmpcvt(1).
714 Introduce the kernel thread "deadlock resolver" (which can be enabled
715 via the DEADLKRES option, see NOTES for more details) and the
716 sleepq_type() function for sleepqueues.
719 The rc.firewall and rc.firewall6 were unified, and
720 rc.firewall6 and rc.d/ip6fw were removed.
721 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
722 variables are obsoleted. Instead, the following new rc
723 variables are added to rc.d/ipfw:
725 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
726 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
727 firewall_simple_onet_ipv6, firewall_trusted_ipv6
729 The meanings correspond to the relevant IPv4 variables.
735 The default terminal emulation for syscons(4) has been changed
736 from cons25 to xterm on all platforms except pc98. This means
737 that the /etc/ttys file needs to be updated to ensure correct
738 operation of applications on the console.
740 The terminal emulation style can be toggled per window by using
741 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
742 options can be used to change the compile-time default back to
745 To prevent graphical artifacts, make sure the TERM environment
746 variable is set to match the terminal emulation that is being
747 performed by syscons(4).
750 The layout of the structure ieee80211req_scan_result has changed.
751 Applications that require wireless scan results (e.g. ifconfig(8))
752 from net80211 need to be recompiled.
754 Applications such as wpa_supplicant(8) may require a full world
755 build without using NO_CLEAN in order to get synchronized with the
759 The iwn(4) driver has been updated to support the 5000 and 5150 series.
760 There's one kernel module for each firmware. Adding "device iwnfw"
761 to the kernel configuration file means including all three firmware
762 images inside the kernel. If you want to include just the one for
763 your wireless card, use the devices iwn4965fw, iwn5000fw or
767 The rc.d/network_ipv6, IPv6 configuration script has been integrated
768 into rc.d/netif. The changes are the following:
770 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
771 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
772 Note that both variables need the "inet6" keyword at the head.
774 Do not set $ipv6_network_interfaces manually if you do not
775 understand what you are doing. It is not needed in most cases.
777 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
780 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
781 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
783 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
784 all configured interfaces have "inet6 accept_rtadv" in the
785 $ifconfig_IF_ipv6. These are for backward compatibility.
787 3. A new variable $ipv6_prefer has been added. If NO, IPv6
788 functionality of interfaces with no corresponding
789 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
790 and the default address selection policy of ip6addrctl(8)
791 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
792 Note that if you want to configure IPv6 functionality on the
793 disabled interfaces after boot, first you need to clear the flag by
794 using ifconfig(8) like:
796 ifconfig em0 inet6 -ifdisabled
798 If YES, the default address selection policy is set as
801 The default value of $ipv6_prefer is NO.
803 4. If your system need to receive Router Advertisement messages,
804 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
805 scripts automatically invoke rtsol(8) when the interface becomes
806 UP. The Router Advertisement messages are used for SLAAC
807 (State-Less Address AutoConfiguration).
810 802.11s D3.03 support was committed. This is incompatible with the
811 previous code, which was based on D3.0.
814 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
815 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
816 control whether accepting Router Advertisement messages or not.
817 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
818 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
819 The ifconfig(8) utility now supports these flags.
822 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
823 mount(8) and -a option for df(1) to see them.
826 The old tunable hw.bus.devctl_disable has been superseded by
827 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
828 replaced by hw.bus.devctl_queue=0. The default for this new tunable
832 Remove the option STOP_NMI. The default action is now to use NMI only
833 for KDB via the newly introduced function stop_cpus_hard() and
834 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
837 The stable/8 branch created in subversion. This corresponds to the
838 RELENG_8 branch in CVS.
841 Bump the shared library version numbers for all libraries that do not
842 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
843 __FreeBSD_version to 800105.
846 Due to changes in the implementation of virtual network stack support,
847 all network-related kernel modules must be recompiled. As this change
848 breaks the ABI, bump __FreeBSD_version to 800104.
851 The TOE interface to the TCP syncache has been modified to remove
852 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
853 The cxgb driver is the only TOE consumer affected by this change, and
854 needs to be recompiled along with the kernel. As this change breaks
855 the ABI, bump __FreeBSD_version to 800103.
858 Padding has been added to struct tcpcb, sackhint and tcpstat in
859 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
860 maintaining the ABI. However, this change breaks the ABI, so bump
861 __FreeBSD_version to 800102. User space tools that rely on the size of
862 any of these structs (e.g. sockstat) need to be recompiled.
865 The NFS_LEGACYRPC option has been removed along with the old kernel
866 RPC implementation that this option selected. Kernel configurations
867 may need to be adjusted.
870 The network interface device nodes at /dev/net/<interface> have been
871 removed. All ioctl operations can be performed the normal way using
872 routing sockets. The kqueue functionality can generally be replaced
873 with routing sockets.
876 The documentation from the FreeBSD Documentation Project (Handbook,
877 FAQ, etc.) is now installed via packages by sysinstall(8) and under
878 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
881 The ABI of various structures related to the SYSV IPC API have been
882 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
883 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
887 Layout of struct vnet has changed as routing related variables were
888 moved to their own Vimage module. Modules need to be recompiled. Bump
889 __FreeBSD_version to 800099.
892 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
893 respectively. As long as no more than 16 groups per process are used,
894 no changes should be visible. When more than 16 groups are used, old
895 binaries may fail if they call getgroups() or getgrouplist() with
896 statically sized storage. Recompiling will work around this, but
897 applications should be modified to use dynamically allocated storage
898 for group arrays as POSIX.1-2008 does not cap an implementation's
899 number of supported groups at NGROUPS_MAX+1 as previous versions did.
901 NFS and portalfs mounts may also be affected as the list of groups is
902 truncated to 16. Users of NFS who use more than 16 groups, should
903 take care that negative group permissions are not used on the exported
904 file systems as they will not be reliable unless a GSSAPI based
905 authentication method is used.
908 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
909 option compiles in the support for adaptive spinning for lockmgrs
910 which want to enable it. The lockinit() function now accepts the flag
911 LK_ADAPTIVE in order to make the lock object subject to adaptive
912 spinning when both held in write and read mode.
915 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
916 changed. User applications that use this ioctl need to be rebuilt.
919 The layout of struct thread has changed. Kernel and modules need to
923 The layout of structs ifnet, domain, protosw and vnet_net has changed.
924 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
927 window(1) has been removed from the base system. It can now be
928 installed from ports. The port is called misc/window.
931 The way we are storing and accessing `routing table' entries has
932 changed. Programs reading the FIB, like netstat, need to be
936 A new netisr implementation has been added for FreeBSD 8. Network
937 file system modules, such as igmp, ipdivert, and others, should be
939 Bump __FreeBSD_version to 800096.
942 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
946 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
947 Bump __FreeBSD_version to 800094.
950 Add mnt_xflag field to 'struct mount'. File system modules need to be
952 Bump __FreeBSD_version to 800093.
955 The compiling option ADAPTIVE_SX has been retired while it has been
956 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
957 The KPI for sx_init_flags() changes as accepting flags:
958 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
959 been introduced in order to handle the reversed logic.
960 Bump __FreeBSD_version to 800092.
963 Add support for hierarchical jails. Remove global securelevel.
964 Bump __FreeBSD_version to 800091.
967 The layout of struct vnet_net has changed, therefore modules
969 Bump __FreeBSD_version to 800090.
972 The newly imported zic(8) produces a new format in the output. Please
973 run tzsetup(8) to install the newly created data to /etc/localtime.
976 The sysctl tree for the usb stack has renamed from hw.usb2.* to
977 hw.usb.* and is now consistent again with previous releases.
980 802.11 monitor mode support was revised and driver api's were changed.
981 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
982 of DLT_IEEE802_11. No user-visible data structures were changed but
983 applications that use DLT_IEEE802_11 may require changes.
984 Bump __FreeBSD_version to 800088.
987 The layout of the following structs has changed: sysctl_oid,
988 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
989 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
990 panics may be experienced. World rebuild is required for
991 correctly checking networking state from userland.
992 Bump __FreeBSD_version to 800085.
995 MLDv2 and Source-Specific Multicast (SSM) have been merged
996 to the IPv6 stack. VIMAGE hooks are in but not yet used.
997 The implementation of SSM within FreeBSD's IPv6 stack closely
998 follows the IPv4 implementation.
1000 For kernel developers:
1002 * The most important changes are that the ip6_output() and
1003 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1004 and this lock has been downgraded to a non-recursive mutex.
1006 * As with the changes to the IPv4 stack to support SSM, filtering
1007 of inbound multicast traffic must now be performed by transport
1008 protocols within the IPv6 stack. This does not apply to TCP and
1009 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1011 * The KPIs used by IPv6 multicast are similar to those used by
1012 the IPv4 stack, with the following differences:
1013 * im6o_mc_filter() is analogous to imo_multicast_filter().
1014 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1015 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1016 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1017 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1018 for MLDv1 have an additional 'timer' argument which is used to
1019 jitter the initial membership report for the solicited-node
1020 multicast membership on-link.
1021 * This is not strictly needed for MLDv2, which already jitters
1022 its report transmissions. However, the 'timer' argument is
1023 preserved in case MLDv1 is active on the interface.
1025 * The KAME linked-list based IPv6 membership implementation has
1026 been refactored to use a vector similar to that used by the IPv4
1028 Code which maintains a list of its own multicast memberships
1029 internally, e.g. carp, has been updated to reflect the new
1032 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1033 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1034 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1035 implementation constraint which needs to be addressed in HEAD.
1037 For application developers:
1039 * The changes are broadly similar to those made for the IPv4
1042 * The use of IPv4 and IPv6 multicast socket options on the same
1043 socket, using mapped addresses, HAS NOT been tested or supported.
1045 * There are a number of issues with the implementation of various
1046 IPv6 multicast APIs which need to be resolved in the API surface
1047 before the implementation is fully compatible with KAME userland
1048 use, and these are mostly to do with interface index treatment.
1050 * The literature available discusses the use of either the delta / ASM
1051 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1052 using setsourcefilter(3)/getsourcefilter(3). For more information
1053 please refer to RFC 3768, 'Socket Interface Extensions for
1054 Multicast Source Filters'.
1056 * Applications which use the published RFC 3678 APIs should be fine.
1058 For systems administrators:
1060 * The mtest(8) utility has been refactored to support IPv6, in
1061 addition to IPv4. Interface addresses are no longer accepted
1062 as arguments, their names must be used instead. The utility
1063 will map the interface name to its first IPv4 address as
1064 returned by getifaddrs(3).
1066 * The ifmcstat(8) utility has also been updated to print the MLDv2
1067 endpoint state and source filter lists via sysctl(3).
1069 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1070 loopback of IPv6 multicast datagrams by default; it defaults to 1
1071 to preserve the existing behaviour. Disabling multicast loopback is
1072 recommended for optimal system performance.
1074 * The IPv6 MROUTING code has been changed to examine this sysctl
1075 instead of attempting to perform a group lookup before looping
1076 back forwarded datagrams.
1078 Bump __FreeBSD_version to 800084.
1081 Implement low-level Bluetooth HCI API.
1082 Bump __FreeBSD_version to 800083.
1085 The layout of struct malloc_type, used by modules to register new
1086 memory allocation types, has changed. Most modules will need to
1087 be rebuilt or panics may be experienced.
1088 Bump __FreeBSD_version to 800081.
1091 Anticipate overflowing inp_flags - add inp_flags2.
1092 This changes most offsets in inpcb, so checking v4 connection
1093 state will require a world rebuild.
1094 Bump __FreeBSD_version to 800080.
1097 Add an llentry to struct route and struct route_in6. Modules
1098 embedding a struct route will need to be recompiled.
1099 Bump __FreeBSD_version to 800079.
1102 The size of rt_metrics_lite and by extension rtentry has changed.
1103 Networking administration apps will need to be recompiled.
1104 The route command now supports show as an alias for get, weighting
1105 of routes, sticky and nostick flags to alter the behavior of stateful
1107 Bump __FreeBSD_version to 800078.
1110 Do not use Giant for kbdmux(4) locking. This is wrong and
1111 apparently causing more problems than it solves. This will
1112 re-open the issue where interrupt handlers may race with
1113 kbdmux(4) in polling mode. Typical symptoms include (but
1114 not limited to) duplicated and/or missing characters when
1115 low level console functions (such as gets) are used while
1116 interrupts are enabled (for example geli password prompt,
1117 mountroot prompt etc.). Disabling kbdmux(4) may help.
1120 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1121 kernel modules referencing any of the above need to be recompiled.
1122 Bump __FreeBSD_version to 800075.
1125 GEOM_PART has become the default partition slicer for storage devices,
1126 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1127 introduces some changes:
1129 MSDOS/EBR: the devices created from MSDOS extended partition entries
1130 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1131 to devices with offset-based names. fstabs may need to be modified.
1133 BSD: the "geometry does not match label" warning is harmless in most
1134 cases but it points to problems in file system misalignment with
1135 disk geometry. The "c" partition is now implicit, covers the whole
1136 top-level drive and cannot be (mis)used by users.
1138 General: Kernel dumps are now not allowed to be written to devices
1139 whose partition types indicate they are meant to be used for file
1140 systems (or, in case of MSDOS partitions, as something else than
1143 Most of these changes date approximately from 200812.
1146 The uscanner(4) driver has been removed from the kernel. This follows
1147 Linux removing theirs in 2.6 and making libusb the default interface
1148 (supported by sane).
1151 The multicast forwarding code has been cleaned up. netstat(1)
1152 only relies on KVM now for printing bandwidth upcall meters.
1153 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1154 ip6_mroute_mod respectively. The config(5) options for statically
1155 compiling this code remain the same, i.e. 'options MROUTING'.
1158 Support for the IFF_NEEDSGIANT network interface flag has been
1159 removed, which means that non-MPSAFE network device drivers are no
1160 longer supported. In particular, if_ar, if_sr, and network device
1161 drivers from the old (legacy) USB stack can no longer be built or
1165 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1166 a bunch of new language catalog files have also been added.
1167 This means that some common libc messages are now localized and
1168 they depend on the LC_MESSAGES environmental variable.
1171 The k8temp(4) driver has been renamed to amdtemp(4) since
1172 support for Family 10 and Family 11 CPU families was added.
1175 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1176 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1178 For kernel developers, the most important changes are that the
1179 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1180 and this lock has been downgraded to a non-recursive mutex.
1182 Transport protocols (UDP, Raw IP) are now responsible for filtering
1183 inbound multicast traffic according to group membership and source
1184 filters. The imo_multicast_filter() KPI exists for this purpose.
1185 Transports which do not use multicast (SCTP, TCP) already reject
1186 multicast by default. Forwarding and receive performance may improve
1187 as a mutex acquisition is no longer needed in the ip_input()
1188 low-level input path. in_addmulti() and in_delmulti() are shimmed
1189 to new KPIs which exist to support SSM in-kernel.
1191 For application developers, it is recommended that loopback of
1192 multicast datagrams be disabled for best performance, as this
1193 will still cause the lock to be taken for each looped-back
1194 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1195 be tuned to 0 to disable loopback by default; it defaults to 1
1196 to preserve the existing behaviour.
1198 For systems administrators, to obtain best performance with
1199 multicast reception and multiple groups, it is always recommended
1200 that a card with a suitably precise hash filter is used. Hash
1201 collisions will still result in the lock being taken within the
1202 transport protocol input path to check group membership.
1204 If deploying FreeBSD in an environment with IGMP snooping switches,
1205 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1206 enabled; this forces 224.0.0.0/24 group membership to be announced
1209 The size of 'struct igmpstat' has changed; netstat needs to be
1210 recompiled to reflect this.
1211 Bump __FreeBSD_version to 800070.
1214 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1215 updated to use it. This requires a buildworld/installworld in order to
1216 update the library and dependencies (usbconfig, etc). Its advisable to
1217 rebuild all ports which uses libusb. More specific directions are given
1218 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1219 libusb are no longer required and can be removed.
1222 A workaround is committed to allow the creation of System V shared
1223 memory segment of size > 2 GB on the 64-bit architectures.
1224 Due to a limitation of the existing ABI, the shm_segsz member
1225 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1226 wrong for large segments. Note that limits must be explicitly
1227 raised to allow such segments to be created.
1230 The layout of struct ifnet has changed, requiring a rebuild of all
1231 network device driver modules.
1234 The /dev handling for the new USB stack has changed, a
1235 buildworld/installworld is required for libusb20.
1238 The new USB2 stack has now been permanently moved in and all kernel and
1239 module names reverted to their previous values (eg, usb, ehci, ohci,
1240 ums, ...). The old usb stack can be compiled in by prefixing the name
1241 with the letter 'o', the old usb modules have been removed.
1242 Updating entry 20090216 for xorg and 20090215 for libmap may still
1246 The rc.conf(5) option if_up_delay has been renamed to
1247 defaultroute_delay to better reflect its purpose. If you have
1248 customized this setting in /etc/rc.conf you need to update it to
1252 xorg 7.4 wants to configure its input devices via hald which does not
1253 yet work with USB2. If the keyboard/mouse does not work in xorg then
1255 Option "AllowEmptyInput" "off"
1256 to your ServerLayout section. This will cause X to use the configured
1257 kbd and mouse sections from your xorg.conf.
1260 The GENERIC kernels for all architectures now default to the new USB2
1261 stack. No kernel config options or code have been removed so if a
1262 problem arises please report it and optionally revert to the old USB
1263 stack. If you are loading USB kernel modules or have a custom kernel
1264 that includes GENERIC then ensure that usb names are also changed over,
1265 eg uftdi -> usb2_serial_ftdi.
1267 Older programs linked against the ports libusb 0.1 need to be
1268 redirected to the new stack's libusb20. /etc/libmap.conf can
1270 # Map old usb library to new one for usb2 stack
1271 libusb-0.1.so.8 libusb20.so.1
1274 All USB ethernet devices now attach as interfaces under the name ueN
1275 (eg. ue0). This is to provide a predictable name as vendors often
1276 change usb chipsets in a product without notice.
1279 The ichsmb(4) driver has been changed to require SMBus slave
1280 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1281 All of the other SMBus controller drivers require left-justified
1282 slave addresses, so this change makes all the drivers provide the
1286 INET6 statistics (struct ip6stat) was updated.
1287 netstat(1) needs to be recompiled.
1290 NTFS has been removed from GENERIC kernel on amd64 to match
1291 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1292 will load ntfs.ko module automatically when NTFS support is
1293 actually needed, unless ntfs.ko is not installed or security
1294 level prohibits loading kernel modules. If either is the case,
1295 "options NTFS" has to be added into kernel config.
1298 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1299 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1300 800061. User space tools that rely on the size of struct tcpcb in
1301 tcp_var.h (e.g. sockstat) need to be recompiled.
1304 ng_tty(4) module updated to match the new TTY subsystem.
1305 Due to API change, user-level applications must be updated.
1306 New API support added to mpd5 CVS and expected to be present
1307 in next mpd5.3 release.
1310 With __FreeBSD_version 800060 the makefs tool is part of
1311 the base system (it was a port).
1314 The afdata and ifnet locks have been changed from mutexes to
1315 rwlocks, network modules will need to be re-compiled.
1318 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1319 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1320 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1321 architecture and 40 bytes on 64-bit architecture. The userland
1322 applications "arp" and "ndp" have been updated accordingly.
1323 The output from "netstat -r" shows only routing entries and
1324 none of the L2 information.
1327 __FreeBSD_version 800057 marks the switchover from the
1328 binary ath hal to source code. Users must add the line:
1330 options AH_SUPPORT_AR5416
1332 to their kernel config files when specifying:
1336 The ath_hal module no longer exists; the code is now compiled
1337 together with the driver in the ath module. It is now
1338 possible to tailor chip support (i.e. reduce the set of chips
1339 and thereby the code size); consult ath_hal(4) for details.
1342 __FreeBSD_version 800054 adds memory barriers to
1343 <machine/atomic.h>, new interfaces to ifnet to facilitate
1344 multiple hardware transmit queues for cards that support
1345 them, and a lock-less ring-buffer implementation to
1346 enable drivers to more efficiently manage queueing of
1350 A new version of ZFS (version 13) has been merged to -HEAD.
1351 This version has zpool attribute "listsnapshots" off by
1352 default, which means "zfs list" does not show snapshots,
1353 and is the same as Solaris behavior.
1356 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1359 The uhci, ohci, ehci and slhci USB Host controller drivers have
1360 been put into separate modules. If you load the usb module
1361 separately through loader.conf you will need to load the
1362 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1363 controller add the following to loader.conf:
1369 The ABI used by the PMC toolset has changed. Please keep
1370 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1374 atapci kernel module now includes only generic PCI ATA
1375 driver. AHCI driver moved to ataahci kernel module.
1376 All vendor-specific code moved into separate kernel modules:
1377 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1378 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1379 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1380 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1383 The TTY subsystem of the kernel has been replaced by a new
1384 implementation, which provides better scalability and an
1385 improved driver model. Most common drivers have been migrated to
1386 the new TTY subsystem, while others have not. The following
1387 drivers have not yet been ported to the new TTY layer:
1390 cy, digi, rc, rp, sio
1396 ng_h4, ng_tty, ppp, sl, snp
1398 Adding these drivers to your kernel configuration file shall
1399 cause compilation to fail.
1402 ntpd has been upgraded to 4.2.4p5.
1405 OpenSSH has been upgraded to 5.1p1.
1407 For many years, FreeBSD's version of OpenSSH preferred DSA
1408 over RSA for host and user authentication keys. With this
1409 upgrade, we've switched to the vendor's default of RSA over
1410 DSA. This may cause upgraded clients to warn about unknown
1411 host keys even for previously known hosts. Users should
1412 follow the usual procedure for verifying host keys before
1413 accepting the RSA key.
1415 This can be circumvented by setting the "HostKeyAlgorithms"
1416 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1419 Please note that the sequence of keys offered for
1420 authentication has been changed as well. You may want to
1421 specify IdentityFile in a different order to revert this
1425 The sio(4) driver has been removed from the i386 and amd64
1426 kernel configuration files. This means uart(4) is now the
1427 default serial port driver on those platforms as well.
1429 To prevent collisions with the sio(4) driver, the uart(4) driver
1430 uses different names for its device nodes. This means the
1431 onboard serial port will now most likely be called "ttyu0"
1432 instead of "ttyd0". You may need to reconfigure applications to
1433 use the new device names.
1435 When using the serial port as a boot console, be sure to update
1436 /boot/device.hints and /etc/ttys before booting the new kernel.
1437 If you forget to do so, you can still manually specify the hints
1438 at the loader prompt:
1440 set hint.uart.0.at="isa"
1441 set hint.uart.0.port="0x3F8"
1442 set hint.uart.0.flags="0x10"
1443 set hint.uart.0.irq="4"
1447 The gpt(8) utility has been removed. Use gpart(8) to partition
1451 The version that Linuxulator emulates was changed from 2.4.2
1452 to 2.6.16. If you experience any problems with Linux binaries
1453 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1454 if it fixes the problem contact emulation mailing list.
1457 ISDN4BSD (I4B) was removed from the src tree. You may need to
1458 update a your kernel configuration and remove relevant entries.
1461 I have checked in code to support multiple routing tables.
1462 See the man pages setfib(1) and setfib(2).
1463 This is a hopefully backwards compatible version,
1464 but to make use of it you need to compile your kernel
1465 with options ROUTETABLES=2 (or more up to 16).
1468 The 802.11 wireless support was redone to enable multi-bss
1469 operation on devices that are capable. The underlying device
1470 is no longer used directly but instead wlanX devices are
1471 cloned with ifconfig. This requires changes to rc.conf files.
1472 For example, change:
1473 ifconfig_ath0="WPA DHCP"
1476 ifconfig_wlan0="WPA DHCP"
1477 see rc.conf(5) for more details. In addition, mergemaster of
1478 /etc/rc.d is highly recommended. Simultaneous update of userland
1479 and kernel wouldn't hurt either.
1481 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1482 modules were merged into the base wlan module. All references
1483 to these modules (e.g. in kernel config files) must be removed.
1486 psm(4) has gained write(2) support in native operation level.
1487 Arbitrary commands can be written to /dev/psm%d and status can
1488 be read back from it. Therefore, an application is responsible
1489 for status validation and error recovery. It is a no-op in
1490 other operation levels.
1493 Support for KSE threading has been removed from the kernel. To
1494 run legacy applications linked against KSE libmap.conf may
1495 be used. The following libmap.conf may be used to ensure
1496 compatibility with any prior release:
1498 libpthread.so.1 libthr.so.1
1499 libpthread.so.2 libthr.so.2
1500 libkse.so.3 libthr.so.3
1503 The layout of struct vmspace has changed. This affects libkvm
1504 and any executables that link against libkvm and use the
1505 kvm_getprocs() function. In particular, but not exclusively,
1506 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1507 The effects are minimal, but it's advisable to upgrade world
1511 The latest em driver no longer has support in it for the
1512 82575 adapter, this is now moved to the igb driver. The
1513 split was done to make new features that are incompatible
1514 with older hardware easier to do.
1517 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1518 likewise the kernel option is now GEOM_LINUX_LVM.
1521 The default NFS mount mode has changed from UDP to TCP for
1522 increased reliability. If you rely on (insecurely) NFS
1523 mounting across a firewall you may need to update your
1527 Belatedly note the addition of m_collapse for compacting
1531 The fts(3) structures have been changed to use adequate
1532 integer types for their members and so to be able to cope
1533 with huge file trees. The old fts(3) ABI is preserved
1534 through symbol versioning in libc, so third-party binaries
1535 using fts(3) should still work, although they will not take
1536 advantage of the extended types. At the same time, some
1537 third-party software might fail to build after this change
1538 due to unportable assumptions made in its source code about
1539 fts(3) structure members. Such software should be fixed
1540 by its vendor or, in the worst case, in the ports tree.
1541 FreeBSD_version 800015 marks this change for the unlikely
1542 case that a portable fix is impossible.
1545 To upgrade to -current after this date, you must be running
1546 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1547 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1550 The ADAPTIVE_GIANT kernel option has been retired because its
1551 functionality is the default now.
1554 The AT keyboard emulation of sunkbd(4) has been turned on
1555 by default. In order to make the special symbols of the Sun
1556 keyboards driven by sunkbd(4) work under X these now have
1557 to be configured the same way as Sun USB keyboards driven
1558 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1560 Option "XkbLayout" "us"
1561 Option "XkbRules" "xorg"
1562 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1565 It has been decided that it is desirable to provide ABI
1566 backwards compatibility to the FreeBSD 4/5/6 versions of the
1567 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1568 broken with the introduction of PCI domain support (see the
1569 20070930 entry). Unfortunately, this required the ABI of
1570 PCIOCGETCONF to be broken again in order to be able to
1571 provide backwards compatibility to the old version of that
1572 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1573 again. As for prominent ports this affects neither pciutils
1574 nor xorg-server this time, the hal port needs to be rebuilt
1578 The misnamed kthread_create() and friends have been renamed
1579 to kproc_create() etc. Many of the callers already
1580 used kproc_start()..
1581 I will return kthread_create() and friends in a while
1582 with implementations that actually create threads, not procs.
1583 Renaming corresponds with version 800002.
1592 Avoid using make -j when upgrading. While generally safe, there are
1593 sometimes problems using -j to upgrade. If your upgrade fails with
1594 -j, please try again without -j. From time to time in the past there
1595 have been problems using -j with buildworld and/or installworld. This
1596 is especially true when upgrading between "distant" versions (eg one
1597 that cross a major release boundary or several minor releases, or when
1598 several months have passed on the -current branch).
1600 Sometimes, obscure build problems are the result of environment
1601 poisoning. This can happen because the make utility reads its
1602 environment when searching for values for global variables. To run
1603 your build attempts in an "environmental clean room", prefix all make
1604 commands with 'env -i '. See the env(1) manual page for more details.
1606 When upgrading from one major version to another it is generally best
1607 to upgrade to the latest code in the currently installed branch first,
1608 then do an upgrade to the new branch. This is the best-tested upgrade
1609 path, and has the highest probability of being successful. Please try
1610 this approach before reporting problems with a major version upgrade.
1614 When upgrading the boot ZFS pool to a new version, always follow
1617 1.) recompile and reinstall the ZFS boot loader and boot block
1618 (this is part of "make buildworld" and "make installworld")
1620 2.) update the ZFS boot block on your boot drive
1622 The following example updates the ZFS boot block on the first
1623 partition (freebsd-boot) of a GPT partitioned drive ad0:
1624 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1626 Non-boot pools do not need these updates.
1630 If you are updating from a prior version of FreeBSD (even one just
1631 a few days old), you should follow this procedure. It is the most
1632 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1634 make kernel-toolchain
1635 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1636 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1638 To test a kernel once
1639 ---------------------
1640 If you just want to boot a kernel once (because you are not sure
1641 if it works, or if you want to boot a known bad kernel to provide
1642 debugging information) run
1643 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1644 nextboot -k testkernel
1646 To just build a kernel when you know that it won't mess you up
1647 --------------------------------------------------------------
1648 This assumes you are already running a CURRENT system. Replace
1649 ${arch} with the architecture of your machine (e.g. "i386",
1650 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1652 cd src/sys/${arch}/conf
1653 config KERNEL_NAME_HERE
1654 cd ../compile/KERNEL_NAME_HERE
1659 If this fails, go to the "To build a kernel" section.
1661 To rebuild everything and install it on the current system.
1662 -----------------------------------------------------------
1663 # Note: sometimes if you are running current you gotta do more than
1664 # is listed here if you are upgrading from a really old current.
1666 <make sure you have good level 0 dumps>
1668 make kernel KERNCONF=YOUR_KERNEL_HERE
1670 <reboot in single user> [3]
1678 To cross-install current onto a separate partition
1679 --------------------------------------------------
1680 # In this approach we use a separate partition to hold
1681 # current's root, 'usr', and 'var' directories. A partition
1682 # holding "/", "/usr" and "/var" should be about 2GB in
1685 <make sure you have good level 0 dumps>
1688 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1689 <maybe newfs current's root partition>
1690 <mount current's root partition on directory ${CURRENT_ROOT}>
1691 make installworld DESTDIR=${CURRENT_ROOT}
1692 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1693 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1694 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1695 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1696 <reboot into current>
1697 <do a "native" rebuild/install as described in the previous section>
1698 <maybe install compatibility libraries from ports/misc/compat*>
1702 To upgrade in-place from stable to current
1703 ----------------------------------------------
1704 <make sure you have good level 0 dumps>
1706 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1708 <reboot in single user> [3]
1715 Make sure that you've read the UPDATING file to understand the
1716 tweaks to various things you need. At this point in the life
1717 cycle of current, things change often and you are on your own
1718 to cope. The defaults can also change, so please read ALL of
1719 the UPDATING entries.
1721 Also, if you are tracking -current, you must be subscribed to
1722 freebsd-current@freebsd.org. Make sure that before you update
1723 your sources that you have read and understood all the recent
1724 messages there. If in doubt, please track -stable which has
1725 much fewer pitfalls.
1727 [1] If you have third party modules, such as vmware, you
1728 should disable them at this point so they don't crash your
1731 [3] From the bootblocks, boot -s, and then do
1736 adjkerntz -i # if CMOS is wall time
1737 Also, when doing a major release upgrade, it is required that
1738 you boot into single user mode to do the installworld.
1740 [4] Note: This step is non-optional. Failure to do this step
1741 can result in a significant reduction in the functionality of the
1742 system. Attempting to do it by hand is not recommended and those
1743 that pursue this avenue should read this file carefully, as well
1744 as the archives of freebsd-current and freebsd-hackers mailing lists
1745 for potential gotchas. The -U option is also useful to consider.
1746 See mergemaster(8) for more information.
1748 [5] Usually this step is a noop. However, from time to time
1749 you may need to do this if you get unknown user in the following
1750 step. It never hurts to do it all the time. You may need to
1751 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1752 install) after the buildworld before this step if you last updated
1753 from current before 20020224 or from -stable before 20020408.
1755 [6] This only deletes old files and directories. Old libraries
1756 can be deleted by "make delete-old-libs", but you have to make
1757 sure that no program is using those libraries anymore.
1759 [8] In order to have a kernel that can run the 4.x binaries needed to
1760 do an installworld, you must include the COMPAT_FREEBSD4 option in
1761 your kernel. Failure to do so may leave you with a system that is
1762 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1763 required to run the 5.x binaries on more recent kernels. And so on
1764 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1766 Make sure that you merge any new devices from GENERIC since the
1767 last time you updated your kernel config file.
1769 [9] When checking out sources, you must include the -P flag to have
1770 cvs prune empty directories.
1772 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1773 "?=" instead of the "=" assignment operator, so that buildworld can
1774 override the CPUTYPE if it needs to.
1776 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1777 not on the command line, or in /etc/make.conf. buildworld will
1778 warn if it is improperly defined.
1781 This file contains a list, in reverse chronological order, of major
1782 breakages in tracking -current. It is not guaranteed to be a complete
1783 list of such breakages, and only contains entries since October 10, 2007.
1784 If you need to see UPDATING entries from before that date, you will need
1785 to fetch an UPDATING file from an older FreeBSD release.
1787 Copyright information:
1789 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1791 Redistribution, publication, translation and use, with or without
1792 modification, in full or in part, in any form or format of this
1793 document are permitted without further permission from the author.
1795 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1796 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1797 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1798 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1799 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1800 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1801 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1802 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1803 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1804 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1805 POSSIBILITY OF SUCH DAMAGE.
1807 Contact Warner Losh if you have any questions about your use of