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 to bootstrap to the tip of
16 head, and then rebuild without this option. The bootstrap process from
17 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. Really old versions
131 of current may need to bootstrap WITHOUT_CLANG first if the clang
132 build fails (its compatibility window doesn't extend to the 9 stable
136 The IPFIREWALL_FORWARD kernel option has been removed. Its
137 functionality now turned on by default.
140 The ZERO_COPY_SOCKET kernel option has been removed and
141 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
142 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
143 mechanism which is not safe and may result in kernel crashes.
144 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
145 driver supports disposeable external page sized mbuf storage.
146 Proper replacements for both zero-copy mechanisms are under
147 consideration and will eventually lead to complete removal
148 of the two kernel options.
151 The IPv4 network stack has been converted to network byte
152 order. The following modules need to be recompiled together
153 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
154 pf(4), ipfw(4), ng_ipfw(4), stf(4).
157 Support for non-MPSAFE filesystems was removed from VFS. The
158 VFS_VERSION was bumped, all filesystem modules shall be
162 All the non-MPSAFE filesystems have been disconnected from
163 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
164 portalfs, smbfs, xfs.
167 The interface cloning API and ABI has changed. The following
168 modules need to be recompiled together with kernel:
169 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
170 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
171 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
174 The sdhci driver was split in two parts: sdhci (generic SD Host
175 Controller logic) and sdhci_pci (actual hardware driver).
176 No kernel config modifications are required, but if you
177 load sdhc as a module you must switch to sdhci_pci instead.
180 Import the FUSE kernel and userland support into base system.
183 The GNU sort(1) program has been removed since the BSD-licensed
184 sort(1) has been the default for quite some time and no serious
185 problems have been reported. The corresponding WITH_GNU_SORT
189 The pfil(9) API/ABI for AF_INET family has been changed. Packet
190 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
194 The net80211(4) ABI has been changed to allow for improved driver
195 PS-POLL and power-save support. All wireless drivers need to be
196 recompiled to work with the new kernel.
199 The random(4) support for the VIA hardware random number
200 generator (`PADLOCK') is no longer enabled unconditionally.
201 Add the PADLOCK_RNG option in the custom kernel config if
202 needed. The GENERIC kernels on i386 and amd64 do include the
203 option, so the change only affects the custom kernel
207 The pf(4) packet filter ABI has been changed. pfctl(8) and
208 snmp_pf module need to be recompiled to work with new kernel.
211 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
212 to -HEAD. Pools that have empty_bpobj in active state can not be
213 imported read-write with ZFS implementations that do not support
214 this feature. For more information read the zpool-features(5)
218 The sparc64 ZFS loader has been changed to no longer try to auto-
219 detect ZFS providers based on diskN aliases but now requires these
220 to be explicitly listed in the OFW boot-device environment variable.
223 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
224 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
225 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
228 The following sysctls and tunables have been renamed for consistency
229 with other variables:
230 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
231 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
234 The sort utility has been replaced with BSD sort. For now, GNU sort
235 is also available as "gnusort" or the default can be set back to
236 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
237 installed as "bsdsort".
240 A new version of ZFS (pool version 5000) has been merged to -HEAD.
241 Starting with this version the old system of ZFS pool versioning
242 is superseded by "feature flags". This concept enables forward
243 compatibility against certain future changes in functionality of ZFS
244 pools. The first read-only compatible "feature flag" for ZFS pools
245 is named "com.delphix:async_destroy". For more information
246 read the new zpool-features(5) manual page.
247 Please refer to the "ZFS notes" section of this file for information
248 on upgrading boot ZFS pools.
251 The malloc(3) implementation embedded in libc now uses sources imported
252 as contrib/jemalloc. The most disruptive API change is to
253 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
254 delete it prior to installworld, and optionally re-create it using the
255 new format after rebooting. See malloc.conf(5) for details
256 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
260 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
261 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
262 now spelled mips. This is to aid compatibility with third-party
263 software that expects this naming scheme in uname(3). Little-endian
264 settings are unchanged.
267 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
271 Now unix domain sockets behave "as expected" on nullfs(5). Previously
272 nullfs(5) did not pass through all behaviours to the underlying layer,
273 as a result if we bound to a socket on the lower layer we could connect
274 only to the lower path; if we bound to the upper layer we could connect
275 only to the upper path. The new behavior is one can connect to both the
276 lower and the upper paths regardless what layer path one binds to.
279 The getifaddrs upgrade path broken with 20111215 has been restored.
280 If you have upgraded in between 20111215 and 20120209 you need to
281 recompile libc again with your kernel. You still need to recompile
282 world to be able to configure CARP but this restriction already
286 The set_rcvar() function has been removed from /etc/rc.subr. All
287 base and ports rc.d scripts have been updated, so if you have a
288 port installed with a script in /usr/local/etc/rc.d you can either
289 hand-edit the rcvar= line, or reinstall the port.
291 An easy way to handle the mass-update of /etc/rc.d:
292 rm /etc/rc.d/* && mergemaster -i
295 panic(9) now stops other CPUs in the SMP systems, disables interrupts
296 on the current CPU and prevents other threads from running.
297 This behavior can be reverted using the kern.stop_scheduler_on_panic
299 The new behavior can be incompatible with kern.sync_on_panic.
302 The carp(4) facility has been changed significantly. Configuration
303 of the CARP protocol via ifconfig(8) has changed, as well as format
304 of CARP events submitted to devd(8) has changed. See manual pages
305 for more information. The arpbalance feature of carp(4) is currently
306 not supported anymore.
308 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
309 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
310 need to be recompiled.
313 The acpi_wmi(4) status device /dev/wmistat has been renamed to
317 The option VFS_ALLOW_NONMPSAFE option has been added in order to
318 explicitely support non-MPSAFE filesystems.
319 It is on by default for all supported platform at this present
323 The broken amd(4) driver has been replaced with esp(4) in the amd64,
324 i386 and pc98 GENERIC kernel configuration files.
327 sysinstall has been removed
330 The stable/9 branch created in subversion. This corresponds to the
331 RELENG_9 branch in CVS.
334 This commit modifies vfs_register() so that it uses a hash
335 calculation to set vfc_typenum, which is enabled by default.
336 The first time a system is booted after this change, the
337 vfc_typenum values will change for all file systems. The
338 main effect of this is a change to the NFS server file handles
339 for file systems that use vfc_typenum in their fsid, such as ZFS.
340 It will, however, prevent vfc_typenum from changing when file
341 systems are loaded in a different order for subsequent reboots.
342 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
343 until you are ready to remount all NFS clients after a reboot.
346 Bump the shared library version numbers for libraries that
347 do not use symbol versioning, have changed the ABI compared
348 to stable/8 and which shared library version was not bumped.
349 Done as part of 9.0-RELEASE cycle.
352 During the merge of Capsicum features, the fget(9) KPI was modified.
353 This may require the rebuilding of out-of-tree device drivers --
354 issues have been reported specifically with the nVidia device driver.
355 __FreeBSD_version is bumped to 900041.
357 Also, there is a period between 20110811 and 20110814 where the
358 special devices /dev/{stdin,stdout,stderr} did not work correctly.
359 Building world from a kernel during that window may not work.
362 The packet filter (pf) code has been updated to OpenBSD 4.5.
363 You need to update userland tools to be in sync with kernel.
364 This update breaks backward compatibility with earlier pfsync(4)
365 versions. Care must be taken when updating redundant firewall setups.
368 The following sysctls and tunables are retired on x86 platforms:
370 machdep.hlt_logical_cpus
371 The following sysctl is retired:
372 machdep.hyperthreading_allowed
373 The sysctls were supposed to provide a way to dynamically offline and
374 online selected CPUs on x86 platforms, but the implementation has not
375 been reliable especially with SCHED_ULE scheduler.
376 machdep.hyperthreading_allowed tunable is still available to ignore
377 hyperthreading CPUs at OS level.
378 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
379 where X is an APIC ID of a CPU. Be advised, though, that disabling
380 CPUs in non-uniform fashion will result in non-uniform topology and
381 may lead to sub-optimal system performance with SCHED_ULE, which is
385 cpumask_t type is retired and cpuset_t is used in order to describe
389 Changes to ifconfig(8) for dynamic address family detection mandate
390 that you are running a kernel of 20110525 or later. Make sure to
391 follow the update procedure to boot a new kernel before installing
395 Support for sun4v architecture is officially dropped
398 Several KPI breaking changes have been committed to the mii(4) layer,
399 the PHY drivers and consequently some Ethernet drivers using mii(4).
400 This means that miibus.ko and the modules of the affected Ethernet
401 drivers need to be recompiled.
403 Note to kernel developers: Given that the OUI bit reversion problem
404 was fixed as part of these changes all mii(4) commits related to OUIs,
405 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
406 handling, no longer can be merged verbatim to stable/8 and previous
410 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
411 into their kernel configurations along with 'device pci'.
414 The default NFS client is now the new NFS client, so fstype "newnfs"
415 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
416 Although mounts via fstype "nfs" will usually work without userland
417 changes, it is recommended that the mount(8) and mount_nfs(8)
418 commands be rebuilt from sources and that a link to mount_nfs called
419 mount_oldnfs be created. The new client is compiled into the
420 kernel with "options NFSCL" and this is needed for diskless root
421 file systems. The GENERIC kernel configs have been changed to use
422 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
423 To use the regular/old client, you can "mount -t oldnfs ...". For
424 a diskless root file system, you must also include a line like:
426 vfs.root.mountfrom="oldnfs:"
428 in the boot/loader.conf on the root fs on the NFS server to make
429 a diskless root fs use the old client.
432 The GENERIC kernels for all architectures now default to the new
433 CAM-based ATA stack. It means that all legacy ATA drivers were
434 removed and replaced by respective CAM drivers. If you are using
435 ATA device names in /etc/fstab or other places, make sure to update
436 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
437 where 'Y's are the sequential numbers starting from zero for each type
438 in order of detection, unless configured otherwise with tunables,
439 see cam(4)). There will be symbolic links created in /dev/ to map
440 old adX devices to the respective adaY. They should provide basic
441 compatibility for file systems mounting in most cases, but they do
442 not support old user-level APIs and do not have respective providers
443 in GEOM. Consider using updated management tools with new device names.
445 It is possible to load devices ahci, ata, siis and mvs as modules,
446 but option ATA_CAM should remain in kernel configuration to make ata
447 module work as CAM driver supporting legacy ATA controllers. Device ata
448 still can be used in modular fashion (atacore + ...). Modules atadisk
449 and atapi* are not used and won't affect operation in ATA_CAM mode.
450 Note that to use CAM-based ATA kernel should include CAM devices
451 scbus, pass, da (or explicitly ada), cd and optionally others. All of
452 them are parts of the cam module.
454 ataraid(4) functionality is now supported by the RAID GEOM class.
455 To use it you can load geom_raid kernel module and use graid(8) tool
456 for management. Instead of /dev/arX device names, use /dev/raid/rX.
458 No kernel config options or code have been removed, so if a problem
459 arises, please report it and optionally revert to the old ATA stack.
460 In order to do it you can remove from the kernel config:
465 , and instead add back:
466 device atadisk # ATA disk drives
467 device ataraid # ATA RAID drives
468 device atapicd # ATAPI CDROM drives
469 device atapifd # ATAPI floppy drives
470 device atapist # ATAPI tape drives
473 The default NFS server has been changed to the new server, which
474 was referred to as the experimental server. If you need to switch
475 back to the old NFS server, you must now put the "-o" option on
476 both the mountd and nfsd commands. This can be done using the
477 mountd_flags and nfs_server_flags rc.conf variables until an
478 update to the rc scripts is committed, which is coming soon.
481 The GNU Objective-C runtime library (libobjc), and other Objective-C
482 related components have been removed from the base system. If you
483 require an Objective-C library, please use one of the available ports.
486 ath(4) has been split into bus- and device- modules. if_ath contains
487 the HAL, the TX rate control and the network device code. if_ath_pci
488 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
489 contains the AHB glue. Users need to load both if_ath_pci and if_ath
490 in order to use ath on everything else.
492 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
493 need to load if_ath and if_ath_pci for ath(4) operation.
496 As part of the replacement of sysinstall, the process of building
497 release media has changed significantly. For details, please re-read
498 release(7), which has been updated to reflect the new build process.
501 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
502 is the last available version under GPLv2. It brings a number of new
503 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
504 4.1 and SSE 4.2), better support for powerpc64, a number of new
505 directives, and lots of other small improvements. See the ChangeLog
506 file in contrib/binutils for the full details.
509 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
510 compliant, and will now use half of hash for authentication.
511 This will break interoperability with all stacks (including all
512 actual FreeBSD versions) who implement
513 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
515 The only workaround with such peers is to use another HMAC
516 algorithm for IPsec ("phase 2") authentication.
519 Remove the uio_yield prototype and symbol. This function has
520 been misnamed since it was introduced and should not be
521 globally exposed with this name. The equivalent functionality
522 is now available using kern_yield(curthread->td_user_pri).
523 The function remains undocumented.
526 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
527 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
528 for scalar sysctls is defined but disabled. Code that needs
529 UQUAD to pass the type checking that must compile on older
530 systems where the define is not present can check against
531 __FreeBSD_version >= 900030.
533 The system dialog(1) has been replaced with a new version previously
534 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
535 with the previous version, but the libdialog associated with it has
536 a largely incompatible API. As such, the original version of libdialog
537 will be kept temporarily as libodialog, until its base system consumers
538 are replaced or updated. Bump __FreeBSD_version to 900030.
541 If you are trying to run make universe on a -stable system, and you get
542 the following warning:
543 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
544 unknown. config(8) likely too old."
545 or something similar to it, then you must upgrade your -stable system
546 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
547 stable/8) or build the config from the latest stable/8 branch and
548 install it on your system.
550 Prior to this date, building a current universe on 8-stable system from
551 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
552 error in the first kernel build phase. A new config on those old
553 systems will fix that problem for older versions of -current.
556 The TCP stack has been modified to allow Khelp modules to interact with
557 it via helper hook points and store per-connection data in the TCP
558 control block. Bump __FreeBSD_version to 900029. User space tools that
559 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
563 Generic IEEE 802.3 annex 31B full duplex flow control support has been
564 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
565 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
566 to take advantage of it instead of using custom implementations. This
567 means that these drivers now no longer unconditionally advertise
568 support for flow control but only do so if flow control is a selected
569 media option. This was implemented in the generic support that way in
570 order to allow flow control to be switched on and off via ifconfig(8)
571 with the PHY specific default to typically off in order to protect
572 from unwanted effects. Consequently, if you used flow control with
573 one of the above mentioned drivers you now need to explicitly enable
575 ifconfig bge0 media auto mediaopt flowcontrol
577 Along with the above mentioned changes generic support for setting
578 1000baseT master mode also has been added and brgphy(4), ciphy(4),
579 e1000phy(4) as well as ip1000phy(4) have been converted to take
580 advantage of it. This means that these drivers now no longer take the
581 link0 parameter for selecting master mode but the master media option
582 has to be used instead, for example like in the following:
583 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
585 Selection of master mode now is also available with all other PHY
586 drivers supporting 1000baseT.
589 The TCP stack has received a significant update to add support for
590 modularised congestion control and generally improve the clarity of
591 congestion control decisions. Bump __FreeBSD_version to 900025. User
592 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
593 sockstat) need to be recompiled.
596 The man(1) utility has been replaced by a new version that no longer
597 uses /etc/manpath.config. Please consult man.conf(5) for how to
598 migrate local entries to the new format.
601 The copyright strings printed by login(1) and sshd(8) at the time of a
602 new connection have been removed to follow other operating systems and
606 A workaround for a fixed ld bug has been removed in kernel code,
607 so make sure that your system ld is built from sources after
608 revision 210245 from 2010-07-19 (r211583 if building head kernel
609 on stable/8, r211584 for stable/7; both from 2010-08-21).
610 A symptom of incorrect ld version is different addresses for
611 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
614 The $ipv6_prefer variable in rc.conf(5) has been split into
615 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
617 The $ip6addrctl_policy is a variable to choose a pre-defined
618 address selection policy set by ip6addrctl(8). A value
619 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
622 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
623 flag (see an entry of 20090926) is set on an interface with no
624 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
625 security reason. If you want IPv6 link-local address on all
626 interfaces by default, set this to "YES".
628 The old ipv6_prefer="YES" is equivalent to
629 ipv6_activate_all_interfaces="YES" and
630 ip6addrctl_policy="ipv6_prefer".
633 DTrace has grown support for userland tracing. Due to this, DTrace is
634 now i386 and amd64 only.
635 dtruss(1) is now installed by default on those systems and a new
636 kernel module is needed for userland tracing: fasttrap.
637 No changes to your kernel config file are necessary to enable
638 userland tracing, but you might consider adding 'STRIP=' and
639 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
640 to have informative userland stack traces in DTrace (ustack).
643 The acpi_aiboost(4) driver has been removed in favor of the new
644 aibs(4) driver. You should update your kernel configuration file.
647 BSD grep has been imported to the base system and it is built by
648 default. It is completely BSD licensed, highly GNU-compatible, uses
649 less memory than its GNU counterpart and has a small codebase.
650 However, it is slower than its GNU counterpart, which is mostly
651 noticeable for larger searches, for smaller ones it is measurable
652 but not significant. The reason is complex, the most important factor
653 is that we lack a modern and efficient regex library and GNU
654 overcomes this by optimizing the searches internally. Future work
655 on improving the regex performance is planned, for the meantime,
656 users that need better performance, can build GNU grep instead by
657 setting the WITH_GNU_GREP knob.
660 Due to the import of powerpc64 support, all existing powerpc kernel
661 configuration files must be updated with a machine directive like this:
662 machine powerpc powerpc
664 In addition, an updated config(8) is required to build powerpc kernels
668 A new version of ZFS (version 15) has been merged to -HEAD.
669 This version uses a python library for the following subcommands:
670 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
671 For full functionality of these commands the following port must
672 be installed: sysutils/py-zfs
675 'vm_page's are now hashed by physical address to an array of mutexes.
676 Currently this is only used to serialize access to hold_count. Over
677 time the page queue mutex will be peeled away. This changes the size
678 of pmap on every architecture. And requires all callers of vm_page_hold
679 and vm_page_unhold to be updated.
682 WITH_CTF can now be specified in src.conf (not recommended, there
683 are some problems with static executables), make.conf (would also
684 affect ports which do not use GNU make and do not override the
685 compile targets) or in the kernel config (via "makeoptions
687 When WITH_CTF was specified there before this was silently ignored,
688 so make sure that WITH_CTF is not used in places which could lead
689 to unwanted behavior.
692 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
693 to allow 32-bit compatibility on non-x86 platforms. All kernel
694 configurations on amd64 and ia64 platforms using these options must
695 be modified accordingly.
698 The utmp user accounting database has been replaced with utmpx,
699 the user accounting interface standardized by POSIX.
700 Unfortunately the semantics of utmp and utmpx don't match,
701 making it practically impossible to support both interfaces.
702 The user accounting database is used by tools like finger(1),
703 last(1), talk(1), w(1) and ac(8).
705 All applications in the base system use utmpx. This means only
706 local binaries (e.g. from the ports tree) may still use these
707 utmp database files. These applications must be rebuilt to make
710 After the system has been upgraded, it is safe to remove the old
711 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
712 assuming their contents is of no importance anymore. Old wtmp
713 databases can only be used by last(1) and ac(8) after they have
714 been converted to the new format using wtmpcvt(1).
717 Introduce the kernel thread "deadlock resolver" (which can be enabled
718 via the DEADLKRES option, see NOTES for more details) and the
719 sleepq_type() function for sleepqueues.
722 The rc.firewall and rc.firewall6 were unified, and
723 rc.firewall6 and rc.d/ip6fw were removed.
724 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
725 variables are obsoleted. Instead, the following new rc
726 variables are added to rc.d/ipfw:
728 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
729 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
730 firewall_simple_onet_ipv6, firewall_trusted_ipv6
732 The meanings correspond to the relevant IPv4 variables.
738 The default terminal emulation for syscons(4) has been changed
739 from cons25 to xterm on all platforms except pc98. This means
740 that the /etc/ttys file needs to be updated to ensure correct
741 operation of applications on the console.
743 The terminal emulation style can be toggled per window by using
744 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
745 options can be used to change the compile-time default back to
748 To prevent graphical artifacts, make sure the TERM environment
749 variable is set to match the terminal emulation that is being
750 performed by syscons(4).
753 The layout of the structure ieee80211req_scan_result has changed.
754 Applications that require wireless scan results (e.g. ifconfig(8))
755 from net80211 need to be recompiled.
757 Applications such as wpa_supplicant(8) may require a full world
758 build without using NO_CLEAN in order to get synchronized with the
762 The iwn(4) driver has been updated to support the 5000 and 5150 series.
763 There's one kernel module for each firmware. Adding "device iwnfw"
764 to the kernel configuration file means including all three firmware
765 images inside the kernel. If you want to include just the one for
766 your wireless card, use the devices iwn4965fw, iwn5000fw or
770 The rc.d/network_ipv6, IPv6 configuration script has been integrated
771 into rc.d/netif. The changes are the following:
773 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
774 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
775 Note that both variables need the "inet6" keyword at the head.
777 Do not set $ipv6_network_interfaces manually if you do not
778 understand what you are doing. It is not needed in most cases.
780 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
783 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
784 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
786 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
787 all configured interfaces have "inet6 accept_rtadv" in the
788 $ifconfig_IF_ipv6. These are for backward compatibility.
790 3. A new variable $ipv6_prefer has been added. If NO, IPv6
791 functionality of interfaces with no corresponding
792 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
793 and the default address selection policy of ip6addrctl(8)
794 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
795 Note that if you want to configure IPv6 functionality on the
796 disabled interfaces after boot, first you need to clear the flag by
797 using ifconfig(8) like:
799 ifconfig em0 inet6 -ifdisabled
801 If YES, the default address selection policy is set as
804 The default value of $ipv6_prefer is NO.
806 4. If your system need to receive Router Advertisement messages,
807 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
808 scripts automatically invoke rtsol(8) when the interface becomes
809 UP. The Router Advertisement messages are used for SLAAC
810 (State-Less Address AutoConfiguration).
813 802.11s D3.03 support was committed. This is incompatible with the
814 previous code, which was based on D3.0.
817 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
818 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
819 control whether accepting Router Advertisement messages or not.
820 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
821 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
822 The ifconfig(8) utility now supports these flags.
825 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
826 mount(8) and -a option for df(1) to see them.
829 The old tunable hw.bus.devctl_disable has been superseded by
830 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
831 replaced by hw.bus.devctl_queue=0. The default for this new tunable
835 Remove the option STOP_NMI. The default action is now to use NMI only
836 for KDB via the newly introduced function stop_cpus_hard() and
837 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
840 The stable/8 branch created in subversion. This corresponds to the
841 RELENG_8 branch in CVS.
844 Bump the shared library version numbers for all libraries that do not
845 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
846 __FreeBSD_version to 800105.
849 Due to changes in the implementation of virtual network stack support,
850 all network-related kernel modules must be recompiled. As this change
851 breaks the ABI, bump __FreeBSD_version to 800104.
854 The TOE interface to the TCP syncache has been modified to remove
855 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
856 The cxgb driver is the only TOE consumer affected by this change, and
857 needs to be recompiled along with the kernel. As this change breaks
858 the ABI, bump __FreeBSD_version to 800103.
861 Padding has been added to struct tcpcb, sackhint and tcpstat in
862 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
863 maintaining the ABI. However, this change breaks the ABI, so bump
864 __FreeBSD_version to 800102. User space tools that rely on the size of
865 any of these structs (e.g. sockstat) need to be recompiled.
868 The NFS_LEGACYRPC option has been removed along with the old kernel
869 RPC implementation that this option selected. Kernel configurations
870 may need to be adjusted.
873 The network interface device nodes at /dev/net/<interface> have been
874 removed. All ioctl operations can be performed the normal way using
875 routing sockets. The kqueue functionality can generally be replaced
876 with routing sockets.
879 The documentation from the FreeBSD Documentation Project (Handbook,
880 FAQ, etc.) is now installed via packages by sysinstall(8) and under
881 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
884 The ABI of various structures related to the SYSV IPC API have been
885 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
886 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
890 Layout of struct vnet has changed as routing related variables were
891 moved to their own Vimage module. Modules need to be recompiled. Bump
892 __FreeBSD_version to 800099.
895 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
896 respectively. As long as no more than 16 groups per process are used,
897 no changes should be visible. When more than 16 groups are used, old
898 binaries may fail if they call getgroups() or getgrouplist() with
899 statically sized storage. Recompiling will work around this, but
900 applications should be modified to use dynamically allocated storage
901 for group arrays as POSIX.1-2008 does not cap an implementation's
902 number of supported groups at NGROUPS_MAX+1 as previous versions did.
904 NFS and portalfs mounts may also be affected as the list of groups is
905 truncated to 16. Users of NFS who use more than 16 groups, should
906 take care that negative group permissions are not used on the exported
907 file systems as they will not be reliable unless a GSSAPI based
908 authentication method is used.
911 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
912 option compiles in the support for adaptive spinning for lockmgrs
913 which want to enable it. The lockinit() function now accepts the flag
914 LK_ADAPTIVE in order to make the lock object subject to adaptive
915 spinning when both held in write and read mode.
918 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
919 changed. User applications that use this ioctl need to be rebuilt.
922 The layout of struct thread has changed. Kernel and modules need to
926 The layout of structs ifnet, domain, protosw and vnet_net has changed.
927 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
930 window(1) has been removed from the base system. It can now be
931 installed from ports. The port is called misc/window.
934 The way we are storing and accessing `routing table' entries has
935 changed. Programs reading the FIB, like netstat, need to be
939 A new netisr implementation has been added for FreeBSD 8. Network
940 file system modules, such as igmp, ipdivert, and others, should be
942 Bump __FreeBSD_version to 800096.
945 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
949 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
950 Bump __FreeBSD_version to 800094.
953 Add mnt_xflag field to 'struct mount'. File system modules need to be
955 Bump __FreeBSD_version to 800093.
958 The compiling option ADAPTIVE_SX has been retired while it has been
959 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
960 The KPI for sx_init_flags() changes as accepting flags:
961 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
962 been introduced in order to handle the reversed logic.
963 Bump __FreeBSD_version to 800092.
966 Add support for hierarchical jails. Remove global securelevel.
967 Bump __FreeBSD_version to 800091.
970 The layout of struct vnet_net has changed, therefore modules
972 Bump __FreeBSD_version to 800090.
975 The newly imported zic(8) produces a new format in the output. Please
976 run tzsetup(8) to install the newly created data to /etc/localtime.
979 The sysctl tree for the usb stack has renamed from hw.usb2.* to
980 hw.usb.* and is now consistent again with previous releases.
983 802.11 monitor mode support was revised and driver api's were changed.
984 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
985 of DLT_IEEE802_11. No user-visible data structures were changed but
986 applications that use DLT_IEEE802_11 may require changes.
987 Bump __FreeBSD_version to 800088.
990 The layout of the following structs has changed: sysctl_oid,
991 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
992 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
993 panics may be experienced. World rebuild is required for
994 correctly checking networking state from userland.
995 Bump __FreeBSD_version to 800085.
998 MLDv2 and Source-Specific Multicast (SSM) have been merged
999 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1000 The implementation of SSM within FreeBSD's IPv6 stack closely
1001 follows the IPv4 implementation.
1003 For kernel developers:
1005 * The most important changes are that the ip6_output() and
1006 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1007 and this lock has been downgraded to a non-recursive mutex.
1009 * As with the changes to the IPv4 stack to support SSM, filtering
1010 of inbound multicast traffic must now be performed by transport
1011 protocols within the IPv6 stack. This does not apply to TCP and
1012 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1014 * The KPIs used by IPv6 multicast are similar to those used by
1015 the IPv4 stack, with the following differences:
1016 * im6o_mc_filter() is analogous to imo_multicast_filter().
1017 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1018 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1019 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1020 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1021 for MLDv1 have an additional 'timer' argument which is used to
1022 jitter the initial membership report for the solicited-node
1023 multicast membership on-link.
1024 * This is not strictly needed for MLDv2, which already jitters
1025 its report transmissions. However, the 'timer' argument is
1026 preserved in case MLDv1 is active on the interface.
1028 * The KAME linked-list based IPv6 membership implementation has
1029 been refactored to use a vector similar to that used by the IPv4
1031 Code which maintains a list of its own multicast memberships
1032 internally, e.g. carp, has been updated to reflect the new
1035 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1036 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1037 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1038 implementation constraint which needs to be addressed in HEAD.
1040 For application developers:
1042 * The changes are broadly similar to those made for the IPv4
1045 * The use of IPv4 and IPv6 multicast socket options on the same
1046 socket, using mapped addresses, HAS NOT been tested or supported.
1048 * There are a number of issues with the implementation of various
1049 IPv6 multicast APIs which need to be resolved in the API surface
1050 before the implementation is fully compatible with KAME userland
1051 use, and these are mostly to do with interface index treatment.
1053 * The literature available discusses the use of either the delta / ASM
1054 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1055 using setsourcefilter(3)/getsourcefilter(3). For more information
1056 please refer to RFC 3768, 'Socket Interface Extensions for
1057 Multicast Source Filters'.
1059 * Applications which use the published RFC 3678 APIs should be fine.
1061 For systems administrators:
1063 * The mtest(8) utility has been refactored to support IPv6, in
1064 addition to IPv4. Interface addresses are no longer accepted
1065 as arguments, their names must be used instead. The utility
1066 will map the interface name to its first IPv4 address as
1067 returned by getifaddrs(3).
1069 * The ifmcstat(8) utility has also been updated to print the MLDv2
1070 endpoint state and source filter lists via sysctl(3).
1072 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1073 loopback of IPv6 multicast datagrams by default; it defaults to 1
1074 to preserve the existing behaviour. Disabling multicast loopback is
1075 recommended for optimal system performance.
1077 * The IPv6 MROUTING code has been changed to examine this sysctl
1078 instead of attempting to perform a group lookup before looping
1079 back forwarded datagrams.
1081 Bump __FreeBSD_version to 800084.
1084 Implement low-level Bluetooth HCI API.
1085 Bump __FreeBSD_version to 800083.
1088 The layout of struct malloc_type, used by modules to register new
1089 memory allocation types, has changed. Most modules will need to
1090 be rebuilt or panics may be experienced.
1091 Bump __FreeBSD_version to 800081.
1094 Anticipate overflowing inp_flags - add inp_flags2.
1095 This changes most offsets in inpcb, so checking v4 connection
1096 state will require a world rebuild.
1097 Bump __FreeBSD_version to 800080.
1100 Add an llentry to struct route and struct route_in6. Modules
1101 embedding a struct route will need to be recompiled.
1102 Bump __FreeBSD_version to 800079.
1105 The size of rt_metrics_lite and by extension rtentry has changed.
1106 Networking administration apps will need to be recompiled.
1107 The route command now supports show as an alias for get, weighting
1108 of routes, sticky and nostick flags to alter the behavior of stateful
1110 Bump __FreeBSD_version to 800078.
1113 Do not use Giant for kbdmux(4) locking. This is wrong and
1114 apparently causing more problems than it solves. This will
1115 re-open the issue where interrupt handlers may race with
1116 kbdmux(4) in polling mode. Typical symptoms include (but
1117 not limited to) duplicated and/or missing characters when
1118 low level console functions (such as gets) are used while
1119 interrupts are enabled (for example geli password prompt,
1120 mountroot prompt etc.). Disabling kbdmux(4) may help.
1123 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1124 kernel modules referencing any of the above need to be recompiled.
1125 Bump __FreeBSD_version to 800075.
1128 GEOM_PART has become the default partition slicer for storage devices,
1129 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1130 introduces some changes:
1132 MSDOS/EBR: the devices created from MSDOS extended partition entries
1133 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1134 to devices with offset-based names. fstabs may need to be modified.
1136 BSD: the "geometry does not match label" warning is harmless in most
1137 cases but it points to problems in file system misalignment with
1138 disk geometry. The "c" partition is now implicit, covers the whole
1139 top-level drive and cannot be (mis)used by users.
1141 General: Kernel dumps are now not allowed to be written to devices
1142 whose partition types indicate they are meant to be used for file
1143 systems (or, in case of MSDOS partitions, as something else than
1146 Most of these changes date approximately from 200812.
1149 The uscanner(4) driver has been removed from the kernel. This follows
1150 Linux removing theirs in 2.6 and making libusb the default interface
1151 (supported by sane).
1154 The multicast forwarding code has been cleaned up. netstat(1)
1155 only relies on KVM now for printing bandwidth upcall meters.
1156 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1157 ip6_mroute_mod respectively. The config(5) options for statically
1158 compiling this code remain the same, i.e. 'options MROUTING'.
1161 Support for the IFF_NEEDSGIANT network interface flag has been
1162 removed, which means that non-MPSAFE network device drivers are no
1163 longer supported. In particular, if_ar, if_sr, and network device
1164 drivers from the old (legacy) USB stack can no longer be built or
1168 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1169 a bunch of new language catalog files have also been added.
1170 This means that some common libc messages are now localized and
1171 they depend on the LC_MESSAGES environmental variable.
1174 The k8temp(4) driver has been renamed to amdtemp(4) since
1175 support for Family 10 and Family 11 CPU families was added.
1178 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1179 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1181 For kernel developers, the most important changes are that the
1182 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1183 and this lock has been downgraded to a non-recursive mutex.
1185 Transport protocols (UDP, Raw IP) are now responsible for filtering
1186 inbound multicast traffic according to group membership and source
1187 filters. The imo_multicast_filter() KPI exists for this purpose.
1188 Transports which do not use multicast (SCTP, TCP) already reject
1189 multicast by default. Forwarding and receive performance may improve
1190 as a mutex acquisition is no longer needed in the ip_input()
1191 low-level input path. in_addmulti() and in_delmulti() are shimmed
1192 to new KPIs which exist to support SSM in-kernel.
1194 For application developers, it is recommended that loopback of
1195 multicast datagrams be disabled for best performance, as this
1196 will still cause the lock to be taken for each looped-back
1197 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1198 be tuned to 0 to disable loopback by default; it defaults to 1
1199 to preserve the existing behaviour.
1201 For systems administrators, to obtain best performance with
1202 multicast reception and multiple groups, it is always recommended
1203 that a card with a suitably precise hash filter is used. Hash
1204 collisions will still result in the lock being taken within the
1205 transport protocol input path to check group membership.
1207 If deploying FreeBSD in an environment with IGMP snooping switches,
1208 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1209 enabled; this forces 224.0.0.0/24 group membership to be announced
1212 The size of 'struct igmpstat' has changed; netstat needs to be
1213 recompiled to reflect this.
1214 Bump __FreeBSD_version to 800070.
1217 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1218 updated to use it. This requires a buildworld/installworld in order to
1219 update the library and dependencies (usbconfig, etc). Its advisable to
1220 rebuild all ports which uses libusb. More specific directions are given
1221 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1222 libusb are no longer required and can be removed.
1225 A workaround is committed to allow the creation of System V shared
1226 memory segment of size > 2 GB on the 64-bit architectures.
1227 Due to a limitation of the existing ABI, the shm_segsz member
1228 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1229 wrong for large segments. Note that limits must be explicitly
1230 raised to allow such segments to be created.
1233 The layout of struct ifnet has changed, requiring a rebuild of all
1234 network device driver modules.
1237 The /dev handling for the new USB stack has changed, a
1238 buildworld/installworld is required for libusb20.
1241 The new USB2 stack has now been permanently moved in and all kernel and
1242 module names reverted to their previous values (eg, usb, ehci, ohci,
1243 ums, ...). The old usb stack can be compiled in by prefixing the name
1244 with the letter 'o', the old usb modules have been removed.
1245 Updating entry 20090216 for xorg and 20090215 for libmap may still
1249 The rc.conf(5) option if_up_delay has been renamed to
1250 defaultroute_delay to better reflect its purpose. If you have
1251 customized this setting in /etc/rc.conf you need to update it to
1255 xorg 7.4 wants to configure its input devices via hald which does not
1256 yet work with USB2. If the keyboard/mouse does not work in xorg then
1258 Option "AllowEmptyInput" "off"
1259 to your ServerLayout section. This will cause X to use the configured
1260 kbd and mouse sections from your xorg.conf.
1263 The GENERIC kernels for all architectures now default to the new USB2
1264 stack. No kernel config options or code have been removed so if a
1265 problem arises please report it and optionally revert to the old USB
1266 stack. If you are loading USB kernel modules or have a custom kernel
1267 that includes GENERIC then ensure that usb names are also changed over,
1268 eg uftdi -> usb2_serial_ftdi.
1270 Older programs linked against the ports libusb 0.1 need to be
1271 redirected to the new stack's libusb20. /etc/libmap.conf can
1273 # Map old usb library to new one for usb2 stack
1274 libusb-0.1.so.8 libusb20.so.1
1277 All USB ethernet devices now attach as interfaces under the name ueN
1278 (eg. ue0). This is to provide a predictable name as vendors often
1279 change usb chipsets in a product without notice.
1282 The ichsmb(4) driver has been changed to require SMBus slave
1283 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1284 All of the other SMBus controller drivers require left-justified
1285 slave addresses, so this change makes all the drivers provide the
1289 INET6 statistics (struct ip6stat) was updated.
1290 netstat(1) needs to be recompiled.
1293 NTFS has been removed from GENERIC kernel on amd64 to match
1294 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1295 will load ntfs.ko module automatically when NTFS support is
1296 actually needed, unless ntfs.ko is not installed or security
1297 level prohibits loading kernel modules. If either is the case,
1298 "options NTFS" has to be added into kernel config.
1301 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1302 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1303 800061. User space tools that rely on the size of struct tcpcb in
1304 tcp_var.h (e.g. sockstat) need to be recompiled.
1307 ng_tty(4) module updated to match the new TTY subsystem.
1308 Due to API change, user-level applications must be updated.
1309 New API support added to mpd5 CVS and expected to be present
1310 in next mpd5.3 release.
1313 With __FreeBSD_version 800060 the makefs tool is part of
1314 the base system (it was a port).
1317 The afdata and ifnet locks have been changed from mutexes to
1318 rwlocks, network modules will need to be re-compiled.
1321 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1322 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1323 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1324 architecture and 40 bytes on 64-bit architecture. The userland
1325 applications "arp" and "ndp" have been updated accordingly.
1326 The output from "netstat -r" shows only routing entries and
1327 none of the L2 information.
1330 __FreeBSD_version 800057 marks the switchover from the
1331 binary ath hal to source code. Users must add the line:
1333 options AH_SUPPORT_AR5416
1335 to their kernel config files when specifying:
1339 The ath_hal module no longer exists; the code is now compiled
1340 together with the driver in the ath module. It is now
1341 possible to tailor chip support (i.e. reduce the set of chips
1342 and thereby the code size); consult ath_hal(4) for details.
1345 __FreeBSD_version 800054 adds memory barriers to
1346 <machine/atomic.h>, new interfaces to ifnet to facilitate
1347 multiple hardware transmit queues for cards that support
1348 them, and a lock-less ring-buffer implementation to
1349 enable drivers to more efficiently manage queueing of
1353 A new version of ZFS (version 13) has been merged to -HEAD.
1354 This version has zpool attribute "listsnapshots" off by
1355 default, which means "zfs list" does not show snapshots,
1356 and is the same as Solaris behavior.
1359 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1362 The uhci, ohci, ehci and slhci USB Host controller drivers have
1363 been put into separate modules. If you load the usb module
1364 separately through loader.conf you will need to load the
1365 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1366 controller add the following to loader.conf:
1372 The ABI used by the PMC toolset has changed. Please keep
1373 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1377 atapci kernel module now includes only generic PCI ATA
1378 driver. AHCI driver moved to ataahci kernel module.
1379 All vendor-specific code moved into separate kernel modules:
1380 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1381 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1382 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1383 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1386 The TTY subsystem of the kernel has been replaced by a new
1387 implementation, which provides better scalability and an
1388 improved driver model. Most common drivers have been migrated to
1389 the new TTY subsystem, while others have not. The following
1390 drivers have not yet been ported to the new TTY layer:
1393 cy, digi, rc, rp, sio
1399 ng_h4, ng_tty, ppp, sl, snp
1401 Adding these drivers to your kernel configuration file shall
1402 cause compilation to fail.
1405 ntpd has been upgraded to 4.2.4p5.
1408 OpenSSH has been upgraded to 5.1p1.
1410 For many years, FreeBSD's version of OpenSSH preferred DSA
1411 over RSA for host and user authentication keys. With this
1412 upgrade, we've switched to the vendor's default of RSA over
1413 DSA. This may cause upgraded clients to warn about unknown
1414 host keys even for previously known hosts. Users should
1415 follow the usual procedure for verifying host keys before
1416 accepting the RSA key.
1418 This can be circumvented by setting the "HostKeyAlgorithms"
1419 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1422 Please note that the sequence of keys offered for
1423 authentication has been changed as well. You may want to
1424 specify IdentityFile in a different order to revert this
1428 The sio(4) driver has been removed from the i386 and amd64
1429 kernel configuration files. This means uart(4) is now the
1430 default serial port driver on those platforms as well.
1432 To prevent collisions with the sio(4) driver, the uart(4) driver
1433 uses different names for its device nodes. This means the
1434 onboard serial port will now most likely be called "ttyu0"
1435 instead of "ttyd0". You may need to reconfigure applications to
1436 use the new device names.
1438 When using the serial port as a boot console, be sure to update
1439 /boot/device.hints and /etc/ttys before booting the new kernel.
1440 If you forget to do so, you can still manually specify the hints
1441 at the loader prompt:
1443 set hint.uart.0.at="isa"
1444 set hint.uart.0.port="0x3F8"
1445 set hint.uart.0.flags="0x10"
1446 set hint.uart.0.irq="4"
1450 The gpt(8) utility has been removed. Use gpart(8) to partition
1454 The version that Linuxulator emulates was changed from 2.4.2
1455 to 2.6.16. If you experience any problems with Linux binaries
1456 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1457 if it fixes the problem contact emulation mailing list.
1460 ISDN4BSD (I4B) was removed from the src tree. You may need to
1461 update a your kernel configuration and remove relevant entries.
1464 I have checked in code to support multiple routing tables.
1465 See the man pages setfib(1) and setfib(2).
1466 This is a hopefully backwards compatible version,
1467 but to make use of it you need to compile your kernel
1468 with options ROUTETABLES=2 (or more up to 16).
1471 The 802.11 wireless support was redone to enable multi-bss
1472 operation on devices that are capable. The underlying device
1473 is no longer used directly but instead wlanX devices are
1474 cloned with ifconfig. This requires changes to rc.conf files.
1475 For example, change:
1476 ifconfig_ath0="WPA DHCP"
1479 ifconfig_wlan0="WPA DHCP"
1480 see rc.conf(5) for more details. In addition, mergemaster of
1481 /etc/rc.d is highly recommended. Simultaneous update of userland
1482 and kernel wouldn't hurt either.
1484 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1485 modules were merged into the base wlan module. All references
1486 to these modules (e.g. in kernel config files) must be removed.
1489 psm(4) has gained write(2) support in native operation level.
1490 Arbitrary commands can be written to /dev/psm%d and status can
1491 be read back from it. Therefore, an application is responsible
1492 for status validation and error recovery. It is a no-op in
1493 other operation levels.
1496 Support for KSE threading has been removed from the kernel. To
1497 run legacy applications linked against KSE libmap.conf may
1498 be used. The following libmap.conf may be used to ensure
1499 compatibility with any prior release:
1501 libpthread.so.1 libthr.so.1
1502 libpthread.so.2 libthr.so.2
1503 libkse.so.3 libthr.so.3
1506 The layout of struct vmspace has changed. This affects libkvm
1507 and any executables that link against libkvm and use the
1508 kvm_getprocs() function. In particular, but not exclusively,
1509 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1510 The effects are minimal, but it's advisable to upgrade world
1514 The latest em driver no longer has support in it for the
1515 82575 adapter, this is now moved to the igb driver. The
1516 split was done to make new features that are incompatible
1517 with older hardware easier to do.
1520 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1521 likewise the kernel option is now GEOM_LINUX_LVM.
1524 The default NFS mount mode has changed from UDP to TCP for
1525 increased reliability. If you rely on (insecurely) NFS
1526 mounting across a firewall you may need to update your
1530 Belatedly note the addition of m_collapse for compacting
1534 The fts(3) structures have been changed to use adequate
1535 integer types for their members and so to be able to cope
1536 with huge file trees. The old fts(3) ABI is preserved
1537 through symbol versioning in libc, so third-party binaries
1538 using fts(3) should still work, although they will not take
1539 advantage of the extended types. At the same time, some
1540 third-party software might fail to build after this change
1541 due to unportable assumptions made in its source code about
1542 fts(3) structure members. Such software should be fixed
1543 by its vendor or, in the worst case, in the ports tree.
1544 FreeBSD_version 800015 marks this change for the unlikely
1545 case that a portable fix is impossible.
1548 To upgrade to -current after this date, you must be running
1549 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1550 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1553 The ADAPTIVE_GIANT kernel option has been retired because its
1554 functionality is the default now.
1557 The AT keyboard emulation of sunkbd(4) has been turned on
1558 by default. In order to make the special symbols of the Sun
1559 keyboards driven by sunkbd(4) work under X these now have
1560 to be configured the same way as Sun USB keyboards driven
1561 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1563 Option "XkbLayout" "us"
1564 Option "XkbRules" "xorg"
1565 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1568 It has been decided that it is desirable to provide ABI
1569 backwards compatibility to the FreeBSD 4/5/6 versions of the
1570 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1571 broken with the introduction of PCI domain support (see the
1572 20070930 entry). Unfortunately, this required the ABI of
1573 PCIOCGETCONF to be broken again in order to be able to
1574 provide backwards compatibility to the old version of that
1575 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1576 again. As for prominent ports this affects neither pciutils
1577 nor xorg-server this time, the hal port needs to be rebuilt
1581 The misnamed kthread_create() and friends have been renamed
1582 to kproc_create() etc. Many of the callers already
1583 used kproc_start()..
1584 I will return kthread_create() and friends in a while
1585 with implementations that actually create threads, not procs.
1586 Renaming corresponds with version 800002.
1595 Avoid using make -j when upgrading. While generally safe, there are
1596 sometimes problems using -j to upgrade. If your upgrade fails with
1597 -j, please try again without -j. From time to time in the past there
1598 have been problems using -j with buildworld and/or installworld. This
1599 is especially true when upgrading between "distant" versions (eg one
1600 that cross a major release boundary or several minor releases, or when
1601 several months have passed on the -current branch).
1603 Sometimes, obscure build problems are the result of environment
1604 poisoning. This can happen because the make utility reads its
1605 environment when searching for values for global variables. To run
1606 your build attempts in an "environmental clean room", prefix all make
1607 commands with 'env -i '. See the env(1) manual page for more details.
1609 When upgrading from one major version to another it is generally best
1610 to upgrade to the latest code in the currently installed branch first,
1611 then do an upgrade to the new branch. This is the best-tested upgrade
1612 path, and has the highest probability of being successful. Please try
1613 this approach before reporting problems with a major version upgrade.
1615 When upgrading a live system, having a root shell around before
1616 installing anything can help undo problems. Not having a root shell
1617 around can lead to problems if pam has changed too much from your
1618 starting point to allow continued authentication after the upgrade.
1622 When upgrading the boot ZFS pool to a new version, always follow
1625 1.) recompile and reinstall the ZFS boot loader and boot block
1626 (this is part of "make buildworld" and "make installworld")
1628 2.) update the ZFS boot block on your boot drive
1630 The following example updates the ZFS boot block on the first
1631 partition (freebsd-boot) of a GPT partitioned drive ad0:
1632 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1634 Non-boot pools do not need these updates.
1638 If you are updating from a prior version of FreeBSD (even one just
1639 a few days old), you should follow this procedure. It is the most
1640 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1642 make kernel-toolchain
1643 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1644 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1646 To test a kernel once
1647 ---------------------
1648 If you just want to boot a kernel once (because you are not sure
1649 if it works, or if you want to boot a known bad kernel to provide
1650 debugging information) run
1651 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1652 nextboot -k testkernel
1654 To just build a kernel when you know that it won't mess you up
1655 --------------------------------------------------------------
1656 This assumes you are already running a CURRENT system. Replace
1657 ${arch} with the architecture of your machine (e.g. "i386",
1658 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1660 cd src/sys/${arch}/conf
1661 config KERNEL_NAME_HERE
1662 cd ../compile/KERNEL_NAME_HERE
1667 If this fails, go to the "To build a kernel" section.
1669 To rebuild everything and install it on the current system.
1670 -----------------------------------------------------------
1671 # Note: sometimes if you are running current you gotta do more than
1672 # is listed here if you are upgrading from a really old current.
1674 <make sure you have good level 0 dumps>
1676 make kernel KERNCONF=YOUR_KERNEL_HERE
1678 <reboot in single user> [3]
1685 To cross-install current onto a separate partition
1686 --------------------------------------------------
1687 # In this approach we use a separate partition to hold
1688 # current's root, 'usr', and 'var' directories. A partition
1689 # holding "/", "/usr" and "/var" should be about 2GB in
1692 <make sure you have good level 0 dumps>
1695 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1696 <maybe newfs current's root partition>
1697 <mount current's root partition on directory ${CURRENT_ROOT}>
1698 make installworld DESTDIR=${CURRENT_ROOT}
1699 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1700 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1701 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1702 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1703 <reboot into current>
1704 <do a "native" rebuild/install as described in the previous section>
1705 <maybe install compatibility libraries from ports/misc/compat*>
1709 To upgrade in-place from stable to current
1710 ----------------------------------------------
1711 <make sure you have good level 0 dumps>
1713 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1715 <reboot in single user> [3]
1722 Make sure that you've read the UPDATING file to understand the
1723 tweaks to various things you need. At this point in the life
1724 cycle of current, things change often and you are on your own
1725 to cope. The defaults can also change, so please read ALL of
1726 the UPDATING entries.
1728 Also, if you are tracking -current, you must be subscribed to
1729 freebsd-current@freebsd.org. Make sure that before you update
1730 your sources that you have read and understood all the recent
1731 messages there. If in doubt, please track -stable which has
1732 much fewer pitfalls.
1734 [1] If you have third party modules, such as vmware, you
1735 should disable them at this point so they don't crash your
1738 [3] From the bootblocks, boot -s, and then do
1743 adjkerntz -i # if CMOS is wall time
1744 Also, when doing a major release upgrade, it is required that
1745 you boot into single user mode to do the installworld.
1747 [4] Note: This step is non-optional. Failure to do this step
1748 can result in a significant reduction in the functionality of the
1749 system. Attempting to do it by hand is not recommended and those
1750 that pursue this avenue should read this file carefully, as well
1751 as the archives of freebsd-current and freebsd-hackers mailing lists
1752 for potential gotchas. The -U option is also useful to consider.
1753 See mergemaster(8) for more information.
1755 [5] Usually this step is a noop. However, from time to time
1756 you may need to do this if you get unknown user in the following
1757 step. It never hurts to do it all the time. You may need to
1758 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1759 install) after the buildworld before this step if you last updated
1760 from current before 20020224 or from -stable before 20020408.
1762 [6] This only deletes old files and directories. Old libraries
1763 can be deleted by "make delete-old-libs", but you have to make
1764 sure that no program is using those libraries anymore.
1766 [8] In order to have a kernel that can run the 4.x binaries needed to
1767 do an installworld, you must include the COMPAT_FREEBSD4 option in
1768 your kernel. Failure to do so may leave you with a system that is
1769 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1770 required to run the 5.x binaries on more recent kernels. And so on
1771 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1773 Make sure that you merge any new devices from GENERIC since the
1774 last time you updated your kernel config file.
1776 [9] When checking out sources, you must include the -P flag to have
1777 cvs prune empty directories.
1779 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1780 "?=" instead of the "=" assignment operator, so that buildworld can
1781 override the CPUTYPE if it needs to.
1783 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1784 not on the command line, or in /etc/make.conf. buildworld will
1785 warn if it is improperly defined.
1788 This file contains a list, in reverse chronological order, of major
1789 breakages in tracking -current. It is not guaranteed to be a complete
1790 list of such breakages, and only contains entries since October 10, 2007.
1791 If you need to see UPDATING entries from before that date, you will need
1792 to fetch an UPDATING file from an older FreeBSD release.
1794 Copyright information:
1796 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1798 Redistribution, publication, translation and use, with or without
1799 modification, in full or in part, in any form or format of this
1800 document are permitted without further permission from the author.
1802 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1803 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1804 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1805 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1806 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1807 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1808 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1809 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1810 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1811 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1812 POSSIBILITY OF SUCH DAMAGE.
1814 Contact Warner Losh if you have any questions about your use of