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 The WITHOUT_IDEA option has been removed because
36 the IDEA patent expired.
39 The sysctl which controls TRIM support under ZFS has been renamed
40 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
44 The mergemaster command now uses the default MAKEOBJDIRPREFIX
45 rather than creating it's own in the temporary directory in
46 order allow access to bootstrapped versions of tools such as
47 install and mtree. When upgrading from version of FreeBSD where
48 the install command does not support -l, you will need to
49 install a new mergemaster command if mergemaster -p is required.
50 This can be accomplished with the command (cd src/usr.sbin/mergemaster
54 Legacy ATA stack, disabled and replaced by new CAM-based one since
55 FreeBSD 9.0, completely removed from the sources. Kernel modules
56 atadisk and atapi*, user-level tools atacontrol and burncd are
57 removed. Kernel option `options ATA_CAM` is now permanently enabled
61 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
62 and socketpair(2). Software, in particular Kerberos, may
63 automatically detect and use these during building. The resulting
64 binaries will not work on older kernels.
67 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
68 information, see the respective 20130304 entry).
71 Recent commits to callout(9) changed the size of struct callout,
72 so the KBI is probably heavily disturbed. Also, some functions
73 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
74 by macros. Every kernel module using it won't load, so rebuild
77 The ctl device has been re-enabled in GENERIC for i386 and amd64,
78 but does not initialize by default (because of the new CTL_DISABLE
79 option) to save memory. To re-enable it, remove the CTL_DISABLE
80 option from the kernel config file or set kern.cam.ctl.disable=0
84 The ctl device has been disabled in GENERIC for i386 and amd64.
85 This was done due to the extra memory being allocated at system
86 initialisation time by the ctl driver which was only used if
87 a CAM target device was created. This makes a FreeBSD system
88 unusable on 128MB or less of RAM.
91 A new compression method (lz4) has been merged to -HEAD. Please
92 refer to zpool-features(7) for more information.
94 Please refer to the "ZFS notes" section of this file for information
95 on upgrading boot ZFS pools.
98 A BSD-licensed patch(1) variant has been added and is installed
99 as bsdpatch, being the GNU version the default patch.
100 To inverse the logic and use the BSD-licensed one as default,
101 while having the GNU version installed as gnupatch, rebuild
102 and install world with the WITH_BSD_PATCH knob set.
105 The install(1) option -M has changed meaning and now takes an
106 argument that is a file or path to append logs to. In the
107 unlikely event that -M was the last option on the command line
108 and the command line contained at least two files and a target
109 directory the first file will have logs appended to it. The -M
110 option served little practical purpose in the last decade so its
111 use is expected to be extremely rare.
114 After switching to Clang as the default compiler some users of ZFS
115 on i386 systems started to experience stack overflow kernel panics.
116 Please consider using 'options KSTACK_PAGES=4' in such configurations.
119 GEOM_LABEL now mangles label names read from file system metadata.
120 Mangling affect labels containing spaces, non-printable characters,
121 '%' or '"'. Device names in /etc/fstab and other places may need to
125 By default, only the 10 most recent kernel dumps will be saved. To
126 restore the previous behaviour (no limit on the number of kernel dumps
127 stored in the dump directory) add the following line to /etc/rc.conf:
132 With the addition of auditdistd(8), a new auditdistd user is now
133 depended on during installworld. "mergemaster -p" can be used to add
134 the user prior to installworld, as documented in the handbook.
137 The sin6_scope_id member variable in struct sockaddr_in6 is now
138 filled by the kernel before passing the structure to the userland via
139 sysctl or routing socket. This means the KAME-specific embedded scope
140 id in sin6_addr.s6_addr[2] is always cleared in userland application.
141 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
142 __FreeBSD_version is bumped to 1000025.
145 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
146 This means that the world and kernel will be compiled with clang
147 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
148 and /usr/bin/cpp. To disable this behavior and revert to building
149 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
150 of current may need to bootstrap WITHOUT_CLANG first if the clang
151 build fails (its compatibility window doesn't extend to the 9 stable
155 The IPFIREWALL_FORWARD kernel option has been removed. Its
156 functionality now turned on by default.
159 The ZERO_COPY_SOCKET kernel option has been removed and
160 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
161 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
162 mechanism which is not safe and may result in kernel crashes.
163 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
164 driver supports disposeable external page sized mbuf storage.
165 Proper replacements for both zero-copy mechanisms are under
166 consideration and will eventually lead to complete removal
167 of the two kernel options.
170 The IPv4 network stack has been converted to network byte
171 order. The following modules need to be recompiled together
172 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
173 pf(4), ipfw(4), ng_ipfw(4), stf(4).
176 Support for non-MPSAFE filesystems was removed from VFS. The
177 VFS_VERSION was bumped, all filesystem modules shall be
181 All the non-MPSAFE filesystems have been disconnected from
182 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
183 portalfs, smbfs, xfs.
186 The interface cloning API and ABI has changed. The following
187 modules need to be recompiled together with kernel:
188 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
189 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
190 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
193 The sdhci driver was split in two parts: sdhci (generic SD Host
194 Controller logic) and sdhci_pci (actual hardware driver).
195 No kernel config modifications are required, but if you
196 load sdhc as a module you must switch to sdhci_pci instead.
199 Import the FUSE kernel and userland support into base system.
202 The GNU sort(1) program has been removed since the BSD-licensed
203 sort(1) has been the default for quite some time and no serious
204 problems have been reported. The corresponding WITH_GNU_SORT
208 The pfil(9) API/ABI for AF_INET family has been changed. Packet
209 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
213 The net80211(4) ABI has been changed to allow for improved driver
214 PS-POLL and power-save support. All wireless drivers need to be
215 recompiled to work with the new kernel.
218 The random(4) support for the VIA hardware random number
219 generator (`PADLOCK') is no longer enabled unconditionally.
220 Add the PADLOCK_RNG option in the custom kernel config if
221 needed. The GENERIC kernels on i386 and amd64 do include the
222 option, so the change only affects the custom kernel
226 The pf(4) packet filter ABI has been changed. pfctl(8) and
227 snmp_pf module need to be recompiled to work with new kernel.
230 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
231 to -HEAD. Pools that have empty_bpobj in active state can not be
232 imported read-write with ZFS implementations that do not support
233 this feature. For more information read the zpool-features(5)
237 The sparc64 ZFS loader has been changed to no longer try to auto-
238 detect ZFS providers based on diskN aliases but now requires these
239 to be explicitly listed in the OFW boot-device environment variable.
242 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
243 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
244 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
247 The following sysctls and tunables have been renamed for consistency
248 with other variables:
249 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
250 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
253 The sort utility has been replaced with BSD sort. For now, GNU sort
254 is also available as "gnusort" or the default can be set back to
255 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
256 installed as "bsdsort".
259 A new version of ZFS (pool version 5000) has been merged to -HEAD.
260 Starting with this version the old system of ZFS pool versioning
261 is superseded by "feature flags". This concept enables forward
262 compatibility against certain future changes in functionality of ZFS
263 pools. The first read-only compatible "feature flag" for ZFS pools
264 is named "com.delphix:async_destroy". For more information
265 read the new zpool-features(5) manual page.
266 Please refer to the "ZFS notes" section of this file for information
267 on upgrading boot ZFS pools.
270 The malloc(3) implementation embedded in libc now uses sources imported
271 as contrib/jemalloc. The most disruptive API change is to
272 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
273 delete it prior to installworld, and optionally re-create it using the
274 new format after rebooting. See malloc.conf(5) for details
275 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
279 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
280 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
281 now spelled mips. This is to aid compatibility with third-party
282 software that expects this naming scheme in uname(3). Little-endian
283 settings are unchanged.
286 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
290 Now unix domain sockets behave "as expected" on nullfs(5). Previously
291 nullfs(5) did not pass through all behaviours to the underlying layer,
292 as a result if we bound to a socket on the lower layer we could connect
293 only to the lower path; if we bound to the upper layer we could connect
294 only to the upper path. The new behavior is one can connect to both the
295 lower and the upper paths regardless what layer path one binds to.
298 The getifaddrs upgrade path broken with 20111215 has been restored.
299 If you have upgraded in between 20111215 and 20120209 you need to
300 recompile libc again with your kernel. You still need to recompile
301 world to be able to configure CARP but this restriction already
305 The set_rcvar() function has been removed from /etc/rc.subr. All
306 base and ports rc.d scripts have been updated, so if you have a
307 port installed with a script in /usr/local/etc/rc.d you can either
308 hand-edit the rcvar= line, or reinstall the port.
310 An easy way to handle the mass-update of /etc/rc.d:
311 rm /etc/rc.d/* && mergemaster -i
314 panic(9) now stops other CPUs in the SMP systems, disables interrupts
315 on the current CPU and prevents other threads from running.
316 This behavior can be reverted using the kern.stop_scheduler_on_panic
318 The new behavior can be incompatible with kern.sync_on_panic.
321 The carp(4) facility has been changed significantly. Configuration
322 of the CARP protocol via ifconfig(8) has changed, as well as format
323 of CARP events submitted to devd(8) has changed. See manual pages
324 for more information. The arpbalance feature of carp(4) is currently
325 not supported anymore.
327 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
328 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
329 need to be recompiled.
332 The acpi_wmi(4) status device /dev/wmistat has been renamed to
336 The option VFS_ALLOW_NONMPSAFE option has been added in order to
337 explicitely support non-MPSAFE filesystems.
338 It is on by default for all supported platform at this present
342 The broken amd(4) driver has been replaced with esp(4) in the amd64,
343 i386 and pc98 GENERIC kernel configuration files.
346 sysinstall has been removed
349 The stable/9 branch created in subversion. This corresponds to the
350 RELENG_9 branch in CVS.
353 This commit modifies vfs_register() so that it uses a hash
354 calculation to set vfc_typenum, which is enabled by default.
355 The first time a system is booted after this change, the
356 vfc_typenum values will change for all file systems. The
357 main effect of this is a change to the NFS server file handles
358 for file systems that use vfc_typenum in their fsid, such as ZFS.
359 It will, however, prevent vfc_typenum from changing when file
360 systems are loaded in a different order for subsequent reboots.
361 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
362 until you are ready to remount all NFS clients after a reboot.
365 Bump the shared library version numbers for libraries that
366 do not use symbol versioning, have changed the ABI compared
367 to stable/8 and which shared library version was not bumped.
368 Done as part of 9.0-RELEASE cycle.
371 During the merge of Capsicum features, the fget(9) KPI was modified.
372 This may require the rebuilding of out-of-tree device drivers --
373 issues have been reported specifically with the nVidia device driver.
374 __FreeBSD_version is bumped to 900041.
376 Also, there is a period between 20110811 and 20110814 where the
377 special devices /dev/{stdin,stdout,stderr} did not work correctly.
378 Building world from a kernel during that window may not work.
381 The packet filter (pf) code has been updated to OpenBSD 4.5.
382 You need to update userland tools to be in sync with kernel.
383 This update breaks backward compatibility with earlier pfsync(4)
384 versions. Care must be taken when updating redundant firewall setups.
387 The following sysctls and tunables are retired on x86 platforms:
389 machdep.hlt_logical_cpus
390 The following sysctl is retired:
391 machdep.hyperthreading_allowed
392 The sysctls were supposed to provide a way to dynamically offline and
393 online selected CPUs on x86 platforms, but the implementation has not
394 been reliable especially with SCHED_ULE scheduler.
395 machdep.hyperthreading_allowed tunable is still available to ignore
396 hyperthreading CPUs at OS level.
397 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
398 where X is an APIC ID of a CPU. Be advised, though, that disabling
399 CPUs in non-uniform fashion will result in non-uniform topology and
400 may lead to sub-optimal system performance with SCHED_ULE, which is
404 cpumask_t type is retired and cpuset_t is used in order to describe
408 Changes to ifconfig(8) for dynamic address family detection mandate
409 that you are running a kernel of 20110525 or later. Make sure to
410 follow the update procedure to boot a new kernel before installing
414 Support for sun4v architecture is officially dropped
417 Several KPI breaking changes have been committed to the mii(4) layer,
418 the PHY drivers and consequently some Ethernet drivers using mii(4).
419 This means that miibus.ko and the modules of the affected Ethernet
420 drivers need to be recompiled.
422 Note to kernel developers: Given that the OUI bit reversion problem
423 was fixed as part of these changes all mii(4) commits related to OUIs,
424 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
425 handling, no longer can be merged verbatim to stable/8 and previous
429 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
430 into their kernel configurations along with 'device pci'.
433 The default NFS client is now the new NFS client, so fstype "newnfs"
434 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
435 Although mounts via fstype "nfs" will usually work without userland
436 changes, it is recommended that the mount(8) and mount_nfs(8)
437 commands be rebuilt from sources and that a link to mount_nfs called
438 mount_oldnfs be created. The new client is compiled into the
439 kernel with "options NFSCL" and this is needed for diskless root
440 file systems. The GENERIC kernel configs have been changed to use
441 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
442 To use the regular/old client, you can "mount -t oldnfs ...". For
443 a diskless root file system, you must also include a line like:
445 vfs.root.mountfrom="oldnfs:"
447 in the boot/loader.conf on the root fs on the NFS server to make
448 a diskless root fs use the old client.
451 The GENERIC kernels for all architectures now default to the new
452 CAM-based ATA stack. It means that all legacy ATA drivers were
453 removed and replaced by respective CAM drivers. If you are using
454 ATA device names in /etc/fstab or other places, make sure to update
455 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
456 where 'Y's are the sequential numbers starting from zero for each type
457 in order of detection, unless configured otherwise with tunables,
458 see cam(4)). There will be symbolic links created in /dev/ to map
459 old adX devices to the respective adaY. They should provide basic
460 compatibility for file systems mounting in most cases, but they do
461 not support old user-level APIs and do not have respective providers
462 in GEOM. Consider using updated management tools with new device names.
464 It is possible to load devices ahci, ata, siis and mvs as modules,
465 but option ATA_CAM should remain in kernel configuration to make ata
466 module work as CAM driver supporting legacy ATA controllers. Device ata
467 still can be used in modular fashion (atacore + ...). Modules atadisk
468 and atapi* are not used and won't affect operation in ATA_CAM mode.
469 Note that to use CAM-based ATA kernel should include CAM devices
470 scbus, pass, da (or explicitly ada), cd and optionally others. All of
471 them are parts of the cam module.
473 ataraid(4) functionality is now supported by the RAID GEOM class.
474 To use it you can load geom_raid kernel module and use graid(8) tool
475 for management. Instead of /dev/arX device names, use /dev/raid/rX.
477 No kernel config options or code have been removed, so if a problem
478 arises, please report it and optionally revert to the old ATA stack.
479 In order to do it you can remove from the kernel config:
484 , and instead add back:
485 device atadisk # ATA disk drives
486 device ataraid # ATA RAID drives
487 device atapicd # ATAPI CDROM drives
488 device atapifd # ATAPI floppy drives
489 device atapist # ATAPI tape drives
492 The default NFS server has been changed to the new server, which
493 was referred to as the experimental server. If you need to switch
494 back to the old NFS server, you must now put the "-o" option on
495 both the mountd and nfsd commands. This can be done using the
496 mountd_flags and nfs_server_flags rc.conf variables until an
497 update to the rc scripts is committed, which is coming soon.
500 The GNU Objective-C runtime library (libobjc), and other Objective-C
501 related components have been removed from the base system. If you
502 require an Objective-C library, please use one of the available ports.
505 ath(4) has been split into bus- and device- modules. if_ath contains
506 the HAL, the TX rate control and the network device code. if_ath_pci
507 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
508 contains the AHB glue. Users need to load both if_ath_pci and if_ath
509 in order to use ath on everything else.
511 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
512 need to load if_ath and if_ath_pci for ath(4) operation.
515 As part of the replacement of sysinstall, the process of building
516 release media has changed significantly. For details, please re-read
517 release(7), which has been updated to reflect the new build process.
520 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
521 is the last available version under GPLv2. It brings a number of new
522 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
523 4.1 and SSE 4.2), better support for powerpc64, a number of new
524 directives, and lots of other small improvements. See the ChangeLog
525 file in contrib/binutils for the full details.
528 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
529 compliant, and will now use half of hash for authentication.
530 This will break interoperability with all stacks (including all
531 actual FreeBSD versions) who implement
532 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
534 The only workaround with such peers is to use another HMAC
535 algorithm for IPsec ("phase 2") authentication.
538 Remove the uio_yield prototype and symbol. This function has
539 been misnamed since it was introduced and should not be
540 globally exposed with this name. The equivalent functionality
541 is now available using kern_yield(curthread->td_user_pri).
542 The function remains undocumented.
545 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
546 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
547 for scalar sysctls is defined but disabled. Code that needs
548 UQUAD to pass the type checking that must compile on older
549 systems where the define is not present can check against
550 __FreeBSD_version >= 900030.
552 The system dialog(1) has been replaced with a new version previously
553 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
554 with the previous version, but the libdialog associated with it has
555 a largely incompatible API. As such, the original version of libdialog
556 will be kept temporarily as libodialog, until its base system consumers
557 are replaced or updated. Bump __FreeBSD_version to 900030.
560 If you are trying to run make universe on a -stable system, and you get
561 the following warning:
562 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
563 unknown. config(8) likely too old."
564 or something similar to it, then you must upgrade your -stable system
565 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
566 stable/8) or build the config from the latest stable/8 branch and
567 install it on your system.
569 Prior to this date, building a current universe on 8-stable system from
570 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
571 error in the first kernel build phase. A new config on those old
572 systems will fix that problem for older versions of -current.
575 The TCP stack has been modified to allow Khelp modules to interact with
576 it via helper hook points and store per-connection data in the TCP
577 control block. Bump __FreeBSD_version to 900029. User space tools that
578 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
582 Generic IEEE 802.3 annex 31B full duplex flow control support has been
583 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
584 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
585 to take advantage of it instead of using custom implementations. This
586 means that these drivers now no longer unconditionally advertise
587 support for flow control but only do so if flow control is a selected
588 media option. This was implemented in the generic support that way in
589 order to allow flow control to be switched on and off via ifconfig(8)
590 with the PHY specific default to typically off in order to protect
591 from unwanted effects. Consequently, if you used flow control with
592 one of the above mentioned drivers you now need to explicitly enable
594 ifconfig bge0 media auto mediaopt flowcontrol
596 Along with the above mentioned changes generic support for setting
597 1000baseT master mode also has been added and brgphy(4), ciphy(4),
598 e1000phy(4) as well as ip1000phy(4) have been converted to take
599 advantage of it. This means that these drivers now no longer take the
600 link0 parameter for selecting master mode but the master media option
601 has to be used instead, for example like in the following:
602 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
604 Selection of master mode now is also available with all other PHY
605 drivers supporting 1000baseT.
608 The TCP stack has received a significant update to add support for
609 modularised congestion control and generally improve the clarity of
610 congestion control decisions. Bump __FreeBSD_version to 900025. User
611 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
612 sockstat) need to be recompiled.
615 The man(1) utility has been replaced by a new version that no longer
616 uses /etc/manpath.config. Please consult man.conf(5) for how to
617 migrate local entries to the new format.
620 The copyright strings printed by login(1) and sshd(8) at the time of a
621 new connection have been removed to follow other operating systems and
625 A workaround for a fixed ld bug has been removed in kernel code,
626 so make sure that your system ld is built from sources after
627 revision 210245 from 2010-07-19 (r211583 if building head kernel
628 on stable/8, r211584 for stable/7; both from 2010-08-21).
629 A symptom of incorrect ld version is different addresses for
630 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
633 The $ipv6_prefer variable in rc.conf(5) has been split into
634 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
636 The $ip6addrctl_policy is a variable to choose a pre-defined
637 address selection policy set by ip6addrctl(8). A value
638 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
641 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
642 flag (see an entry of 20090926) is set on an interface with no
643 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
644 security reason. If you want IPv6 link-local address on all
645 interfaces by default, set this to "YES".
647 The old ipv6_prefer="YES" is equivalent to
648 ipv6_activate_all_interfaces="YES" and
649 ip6addrctl_policy="ipv6_prefer".
652 DTrace has grown support for userland tracing. Due to this, DTrace is
653 now i386 and amd64 only.
654 dtruss(1) is now installed by default on those systems and a new
655 kernel module is needed for userland tracing: fasttrap.
656 No changes to your kernel config file are necessary to enable
657 userland tracing, but you might consider adding 'STRIP=' and
658 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
659 to have informative userland stack traces in DTrace (ustack).
662 The acpi_aiboost(4) driver has been removed in favor of the new
663 aibs(4) driver. You should update your kernel configuration file.
666 BSD grep has been imported to the base system and it is built by
667 default. It is completely BSD licensed, highly GNU-compatible, uses
668 less memory than its GNU counterpart and has a small codebase.
669 However, it is slower than its GNU counterpart, which is mostly
670 noticeable for larger searches, for smaller ones it is measurable
671 but not significant. The reason is complex, the most important factor
672 is that we lack a modern and efficient regex library and GNU
673 overcomes this by optimizing the searches internally. Future work
674 on improving the regex performance is planned, for the meantime,
675 users that need better performance, can build GNU grep instead by
676 setting the WITH_GNU_GREP knob.
679 Due to the import of powerpc64 support, all existing powerpc kernel
680 configuration files must be updated with a machine directive like this:
681 machine powerpc powerpc
683 In addition, an updated config(8) is required to build powerpc kernels
687 A new version of ZFS (version 15) has been merged to -HEAD.
688 This version uses a python library for the following subcommands:
689 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
690 For full functionality of these commands the following port must
691 be installed: sysutils/py-zfs
694 'vm_page's are now hashed by physical address to an array of mutexes.
695 Currently this is only used to serialize access to hold_count. Over
696 time the page queue mutex will be peeled away. This changes the size
697 of pmap on every architecture. And requires all callers of vm_page_hold
698 and vm_page_unhold to be updated.
701 WITH_CTF can now be specified in src.conf (not recommended, there
702 are some problems with static executables), make.conf (would also
703 affect ports which do not use GNU make and do not override the
704 compile targets) or in the kernel config (via "makeoptions
706 When WITH_CTF was specified there before this was silently ignored,
707 so make sure that WITH_CTF is not used in places which could lead
708 to unwanted behavior.
711 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
712 to allow 32-bit compatibility on non-x86 platforms. All kernel
713 configurations on amd64 and ia64 platforms using these options must
714 be modified accordingly.
717 The utmp user accounting database has been replaced with utmpx,
718 the user accounting interface standardized by POSIX.
719 Unfortunately the semantics of utmp and utmpx don't match,
720 making it practically impossible to support both interfaces.
721 The user accounting database is used by tools like finger(1),
722 last(1), talk(1), w(1) and ac(8).
724 All applications in the base system use utmpx. This means only
725 local binaries (e.g. from the ports tree) may still use these
726 utmp database files. These applications must be rebuilt to make
729 After the system has been upgraded, it is safe to remove the old
730 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
731 assuming their contents is of no importance anymore. Old wtmp
732 databases can only be used by last(1) and ac(8) after they have
733 been converted to the new format using wtmpcvt(1).
736 Introduce the kernel thread "deadlock resolver" (which can be enabled
737 via the DEADLKRES option, see NOTES for more details) and the
738 sleepq_type() function for sleepqueues.
741 The rc.firewall and rc.firewall6 were unified, and
742 rc.firewall6 and rc.d/ip6fw were removed.
743 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
744 variables are obsoleted. Instead, the following new rc
745 variables are added to rc.d/ipfw:
747 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
748 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
749 firewall_simple_onet_ipv6, firewall_trusted_ipv6
751 The meanings correspond to the relevant IPv4 variables.
757 The default terminal emulation for syscons(4) has been changed
758 from cons25 to xterm on all platforms except pc98. This means
759 that the /etc/ttys file needs to be updated to ensure correct
760 operation of applications on the console.
762 The terminal emulation style can be toggled per window by using
763 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
764 options can be used to change the compile-time default back to
767 To prevent graphical artifacts, make sure the TERM environment
768 variable is set to match the terminal emulation that is being
769 performed by syscons(4).
772 The layout of the structure ieee80211req_scan_result has changed.
773 Applications that require wireless scan results (e.g. ifconfig(8))
774 from net80211 need to be recompiled.
776 Applications such as wpa_supplicant(8) may require a full world
777 build without using NO_CLEAN in order to get synchronized with the
781 The iwn(4) driver has been updated to support the 5000 and 5150 series.
782 There's one kernel module for each firmware. Adding "device iwnfw"
783 to the kernel configuration file means including all three firmware
784 images inside the kernel. If you want to include just the one for
785 your wireless card, use the devices iwn4965fw, iwn5000fw or
789 The rc.d/network_ipv6, IPv6 configuration script has been integrated
790 into rc.d/netif. The changes are the following:
792 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
793 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
794 Note that both variables need the "inet6" keyword at the head.
796 Do not set $ipv6_network_interfaces manually if you do not
797 understand what you are doing. It is not needed in most cases.
799 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
802 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
803 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
805 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
806 all configured interfaces have "inet6 accept_rtadv" in the
807 $ifconfig_IF_ipv6. These are for backward compatibility.
809 3. A new variable $ipv6_prefer has been added. If NO, IPv6
810 functionality of interfaces with no corresponding
811 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
812 and the default address selection policy of ip6addrctl(8)
813 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
814 Note that if you want to configure IPv6 functionality on the
815 disabled interfaces after boot, first you need to clear the flag by
816 using ifconfig(8) like:
818 ifconfig em0 inet6 -ifdisabled
820 If YES, the default address selection policy is set as
823 The default value of $ipv6_prefer is NO.
825 4. If your system need to receive Router Advertisement messages,
826 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
827 scripts automatically invoke rtsol(8) when the interface becomes
828 UP. The Router Advertisement messages are used for SLAAC
829 (State-Less Address AutoConfiguration).
832 802.11s D3.03 support was committed. This is incompatible with the
833 previous code, which was based on D3.0.
836 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
837 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
838 control whether accepting Router Advertisement messages or not.
839 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
840 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
841 The ifconfig(8) utility now supports these flags.
844 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
845 mount(8) and -a option for df(1) to see them.
848 The old tunable hw.bus.devctl_disable has been superseded by
849 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
850 replaced by hw.bus.devctl_queue=0. The default for this new tunable
854 Remove the option STOP_NMI. The default action is now to use NMI only
855 for KDB via the newly introduced function stop_cpus_hard() and
856 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
859 The stable/8 branch created in subversion. This corresponds to the
860 RELENG_8 branch in CVS.
863 Bump the shared library version numbers for all libraries that do not
864 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
865 __FreeBSD_version to 800105.
868 Due to changes in the implementation of virtual network stack support,
869 all network-related kernel modules must be recompiled. As this change
870 breaks the ABI, bump __FreeBSD_version to 800104.
873 The TOE interface to the TCP syncache has been modified to remove
874 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
875 The cxgb driver is the only TOE consumer affected by this change, and
876 needs to be recompiled along with the kernel. As this change breaks
877 the ABI, bump __FreeBSD_version to 800103.
880 Padding has been added to struct tcpcb, sackhint and tcpstat in
881 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
882 maintaining the ABI. However, this change breaks the ABI, so bump
883 __FreeBSD_version to 800102. User space tools that rely on the size of
884 any of these structs (e.g. sockstat) need to be recompiled.
887 The NFS_LEGACYRPC option has been removed along with the old kernel
888 RPC implementation that this option selected. Kernel configurations
889 may need to be adjusted.
892 The network interface device nodes at /dev/net/<interface> have been
893 removed. All ioctl operations can be performed the normal way using
894 routing sockets. The kqueue functionality can generally be replaced
895 with routing sockets.
898 The documentation from the FreeBSD Documentation Project (Handbook,
899 FAQ, etc.) is now installed via packages by sysinstall(8) and under
900 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
903 The ABI of various structures related to the SYSV IPC API have been
904 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
905 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
909 Layout of struct vnet has changed as routing related variables were
910 moved to their own Vimage module. Modules need to be recompiled. Bump
911 __FreeBSD_version to 800099.
914 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
915 respectively. As long as no more than 16 groups per process are used,
916 no changes should be visible. When more than 16 groups are used, old
917 binaries may fail if they call getgroups() or getgrouplist() with
918 statically sized storage. Recompiling will work around this, but
919 applications should be modified to use dynamically allocated storage
920 for group arrays as POSIX.1-2008 does not cap an implementation's
921 number of supported groups at NGROUPS_MAX+1 as previous versions did.
923 NFS and portalfs mounts may also be affected as the list of groups is
924 truncated to 16. Users of NFS who use more than 16 groups, should
925 take care that negative group permissions are not used on the exported
926 file systems as they will not be reliable unless a GSSAPI based
927 authentication method is used.
930 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
931 option compiles in the support for adaptive spinning for lockmgrs
932 which want to enable it. The lockinit() function now accepts the flag
933 LK_ADAPTIVE in order to make the lock object subject to adaptive
934 spinning when both held in write and read mode.
937 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
938 changed. User applications that use this ioctl need to be rebuilt.
941 The layout of struct thread has changed. Kernel and modules need to
945 The layout of structs ifnet, domain, protosw and vnet_net has changed.
946 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
949 window(1) has been removed from the base system. It can now be
950 installed from ports. The port is called misc/window.
953 The way we are storing and accessing `routing table' entries has
954 changed. Programs reading the FIB, like netstat, need to be
958 A new netisr implementation has been added for FreeBSD 8. Network
959 file system modules, such as igmp, ipdivert, and others, should be
961 Bump __FreeBSD_version to 800096.
964 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
968 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
969 Bump __FreeBSD_version to 800094.
972 Add mnt_xflag field to 'struct mount'. File system modules need to be
974 Bump __FreeBSD_version to 800093.
977 The compiling option ADAPTIVE_SX has been retired while it has been
978 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
979 The KPI for sx_init_flags() changes as accepting flags:
980 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
981 been introduced in order to handle the reversed logic.
982 Bump __FreeBSD_version to 800092.
985 Add support for hierarchical jails. Remove global securelevel.
986 Bump __FreeBSD_version to 800091.
989 The layout of struct vnet_net has changed, therefore modules
991 Bump __FreeBSD_version to 800090.
994 The newly imported zic(8) produces a new format in the output. Please
995 run tzsetup(8) to install the newly created data to /etc/localtime.
998 The sysctl tree for the usb stack has renamed from hw.usb2.* to
999 hw.usb.* and is now consistent again with previous releases.
1002 802.11 monitor mode support was revised and driver api's were changed.
1003 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1004 of DLT_IEEE802_11. No user-visible data structures were changed but
1005 applications that use DLT_IEEE802_11 may require changes.
1006 Bump __FreeBSD_version to 800088.
1009 The layout of the following structs has changed: sysctl_oid,
1010 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1011 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1012 panics may be experienced. World rebuild is required for
1013 correctly checking networking state from userland.
1014 Bump __FreeBSD_version to 800085.
1017 MLDv2 and Source-Specific Multicast (SSM) have been merged
1018 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1019 The implementation of SSM within FreeBSD's IPv6 stack closely
1020 follows the IPv4 implementation.
1022 For kernel developers:
1024 * The most important changes are that the ip6_output() and
1025 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1026 and this lock has been downgraded to a non-recursive mutex.
1028 * As with the changes to the IPv4 stack to support SSM, filtering
1029 of inbound multicast traffic must now be performed by transport
1030 protocols within the IPv6 stack. This does not apply to TCP and
1031 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1033 * The KPIs used by IPv6 multicast are similar to those used by
1034 the IPv4 stack, with the following differences:
1035 * im6o_mc_filter() is analogous to imo_multicast_filter().
1036 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1037 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1038 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1039 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1040 for MLDv1 have an additional 'timer' argument which is used to
1041 jitter the initial membership report for the solicited-node
1042 multicast membership on-link.
1043 * This is not strictly needed for MLDv2, which already jitters
1044 its report transmissions. However, the 'timer' argument is
1045 preserved in case MLDv1 is active on the interface.
1047 * The KAME linked-list based IPv6 membership implementation has
1048 been refactored to use a vector similar to that used by the IPv4
1050 Code which maintains a list of its own multicast memberships
1051 internally, e.g. carp, has been updated to reflect the new
1054 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1055 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1056 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1057 implementation constraint which needs to be addressed in HEAD.
1059 For application developers:
1061 * The changes are broadly similar to those made for the IPv4
1064 * The use of IPv4 and IPv6 multicast socket options on the same
1065 socket, using mapped addresses, HAS NOT been tested or supported.
1067 * There are a number of issues with the implementation of various
1068 IPv6 multicast APIs which need to be resolved in the API surface
1069 before the implementation is fully compatible with KAME userland
1070 use, and these are mostly to do with interface index treatment.
1072 * The literature available discusses the use of either the delta / ASM
1073 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1074 using setsourcefilter(3)/getsourcefilter(3). For more information
1075 please refer to RFC 3768, 'Socket Interface Extensions for
1076 Multicast Source Filters'.
1078 * Applications which use the published RFC 3678 APIs should be fine.
1080 For systems administrators:
1082 * The mtest(8) utility has been refactored to support IPv6, in
1083 addition to IPv4. Interface addresses are no longer accepted
1084 as arguments, their names must be used instead. The utility
1085 will map the interface name to its first IPv4 address as
1086 returned by getifaddrs(3).
1088 * The ifmcstat(8) utility has also been updated to print the MLDv2
1089 endpoint state and source filter lists via sysctl(3).
1091 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1092 loopback of IPv6 multicast datagrams by default; it defaults to 1
1093 to preserve the existing behaviour. Disabling multicast loopback is
1094 recommended for optimal system performance.
1096 * The IPv6 MROUTING code has been changed to examine this sysctl
1097 instead of attempting to perform a group lookup before looping
1098 back forwarded datagrams.
1100 Bump __FreeBSD_version to 800084.
1103 Implement low-level Bluetooth HCI API.
1104 Bump __FreeBSD_version to 800083.
1107 The layout of struct malloc_type, used by modules to register new
1108 memory allocation types, has changed. Most modules will need to
1109 be rebuilt or panics may be experienced.
1110 Bump __FreeBSD_version to 800081.
1113 Anticipate overflowing inp_flags - add inp_flags2.
1114 This changes most offsets in inpcb, so checking v4 connection
1115 state will require a world rebuild.
1116 Bump __FreeBSD_version to 800080.
1119 Add an llentry to struct route and struct route_in6. Modules
1120 embedding a struct route will need to be recompiled.
1121 Bump __FreeBSD_version to 800079.
1124 The size of rt_metrics_lite and by extension rtentry has changed.
1125 Networking administration apps will need to be recompiled.
1126 The route command now supports show as an alias for get, weighting
1127 of routes, sticky and nostick flags to alter the behavior of stateful
1129 Bump __FreeBSD_version to 800078.
1132 Do not use Giant for kbdmux(4) locking. This is wrong and
1133 apparently causing more problems than it solves. This will
1134 re-open the issue where interrupt handlers may race with
1135 kbdmux(4) in polling mode. Typical symptoms include (but
1136 not limited to) duplicated and/or missing characters when
1137 low level console functions (such as gets) are used while
1138 interrupts are enabled (for example geli password prompt,
1139 mountroot prompt etc.). Disabling kbdmux(4) may help.
1142 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1143 kernel modules referencing any of the above need to be recompiled.
1144 Bump __FreeBSD_version to 800075.
1147 GEOM_PART has become the default partition slicer for storage devices,
1148 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1149 introduces some changes:
1151 MSDOS/EBR: the devices created from MSDOS extended partition entries
1152 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1153 to devices with offset-based names. fstabs may need to be modified.
1155 BSD: the "geometry does not match label" warning is harmless in most
1156 cases but it points to problems in file system misalignment with
1157 disk geometry. The "c" partition is now implicit, covers the whole
1158 top-level drive and cannot be (mis)used by users.
1160 General: Kernel dumps are now not allowed to be written to devices
1161 whose partition types indicate they are meant to be used for file
1162 systems (or, in case of MSDOS partitions, as something else than
1165 Most of these changes date approximately from 200812.
1168 The uscanner(4) driver has been removed from the kernel. This follows
1169 Linux removing theirs in 2.6 and making libusb the default interface
1170 (supported by sane).
1173 The multicast forwarding code has been cleaned up. netstat(1)
1174 only relies on KVM now for printing bandwidth upcall meters.
1175 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1176 ip6_mroute_mod respectively. The config(5) options for statically
1177 compiling this code remain the same, i.e. 'options MROUTING'.
1180 Support for the IFF_NEEDSGIANT network interface flag has been
1181 removed, which means that non-MPSAFE network device drivers are no
1182 longer supported. In particular, if_ar, if_sr, and network device
1183 drivers from the old (legacy) USB stack can no longer be built or
1187 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1188 a bunch of new language catalog files have also been added.
1189 This means that some common libc messages are now localized and
1190 they depend on the LC_MESSAGES environmental variable.
1193 The k8temp(4) driver has been renamed to amdtemp(4) since
1194 support for Family 10 and Family 11 CPU families was added.
1197 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1198 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1200 For kernel developers, the most important changes are that the
1201 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1202 and this lock has been downgraded to a non-recursive mutex.
1204 Transport protocols (UDP, Raw IP) are now responsible for filtering
1205 inbound multicast traffic according to group membership and source
1206 filters. The imo_multicast_filter() KPI exists for this purpose.
1207 Transports which do not use multicast (SCTP, TCP) already reject
1208 multicast by default. Forwarding and receive performance may improve
1209 as a mutex acquisition is no longer needed in the ip_input()
1210 low-level input path. in_addmulti() and in_delmulti() are shimmed
1211 to new KPIs which exist to support SSM in-kernel.
1213 For application developers, it is recommended that loopback of
1214 multicast datagrams be disabled for best performance, as this
1215 will still cause the lock to be taken for each looped-back
1216 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1217 be tuned to 0 to disable loopback by default; it defaults to 1
1218 to preserve the existing behaviour.
1220 For systems administrators, to obtain best performance with
1221 multicast reception and multiple groups, it is always recommended
1222 that a card with a suitably precise hash filter is used. Hash
1223 collisions will still result in the lock being taken within the
1224 transport protocol input path to check group membership.
1226 If deploying FreeBSD in an environment with IGMP snooping switches,
1227 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1228 enabled; this forces 224.0.0.0/24 group membership to be announced
1231 The size of 'struct igmpstat' has changed; netstat needs to be
1232 recompiled to reflect this.
1233 Bump __FreeBSD_version to 800070.
1236 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1237 updated to use it. This requires a buildworld/installworld in order to
1238 update the library and dependencies (usbconfig, etc). Its advisable to
1239 rebuild all ports which uses libusb. More specific directions are given
1240 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1241 libusb are no longer required and can be removed.
1244 A workaround is committed to allow the creation of System V shared
1245 memory segment of size > 2 GB on the 64-bit architectures.
1246 Due to a limitation of the existing ABI, the shm_segsz member
1247 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1248 wrong for large segments. Note that limits must be explicitly
1249 raised to allow such segments to be created.
1252 The layout of struct ifnet has changed, requiring a rebuild of all
1253 network device driver modules.
1256 The /dev handling for the new USB stack has changed, a
1257 buildworld/installworld is required for libusb20.
1260 The new USB2 stack has now been permanently moved in and all kernel and
1261 module names reverted to their previous values (eg, usb, ehci, ohci,
1262 ums, ...). The old usb stack can be compiled in by prefixing the name
1263 with the letter 'o', the old usb modules have been removed.
1264 Updating entry 20090216 for xorg and 20090215 for libmap may still
1268 The rc.conf(5) option if_up_delay has been renamed to
1269 defaultroute_delay to better reflect its purpose. If you have
1270 customized this setting in /etc/rc.conf you need to update it to
1274 xorg 7.4 wants to configure its input devices via hald which does not
1275 yet work with USB2. If the keyboard/mouse does not work in xorg then
1277 Option "AllowEmptyInput" "off"
1278 to your ServerLayout section. This will cause X to use the configured
1279 kbd and mouse sections from your xorg.conf.
1282 The GENERIC kernels for all architectures now default to the new USB2
1283 stack. No kernel config options or code have been removed so if a
1284 problem arises please report it and optionally revert to the old USB
1285 stack. If you are loading USB kernel modules or have a custom kernel
1286 that includes GENERIC then ensure that usb names are also changed over,
1287 eg uftdi -> usb2_serial_ftdi.
1289 Older programs linked against the ports libusb 0.1 need to be
1290 redirected to the new stack's libusb20. /etc/libmap.conf can
1292 # Map old usb library to new one for usb2 stack
1293 libusb-0.1.so.8 libusb20.so.1
1296 All USB ethernet devices now attach as interfaces under the name ueN
1297 (eg. ue0). This is to provide a predictable name as vendors often
1298 change usb chipsets in a product without notice.
1301 The ichsmb(4) driver has been changed to require SMBus slave
1302 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1303 All of the other SMBus controller drivers require left-justified
1304 slave addresses, so this change makes all the drivers provide the
1308 INET6 statistics (struct ip6stat) was updated.
1309 netstat(1) needs to be recompiled.
1312 NTFS has been removed from GENERIC kernel on amd64 to match
1313 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1314 will load ntfs.ko module automatically when NTFS support is
1315 actually needed, unless ntfs.ko is not installed or security
1316 level prohibits loading kernel modules. If either is the case,
1317 "options NTFS" has to be added into kernel config.
1320 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1321 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1322 800061. User space tools that rely on the size of struct tcpcb in
1323 tcp_var.h (e.g. sockstat) need to be recompiled.
1326 ng_tty(4) module updated to match the new TTY subsystem.
1327 Due to API change, user-level applications must be updated.
1328 New API support added to mpd5 CVS and expected to be present
1329 in next mpd5.3 release.
1332 With __FreeBSD_version 800060 the makefs tool is part of
1333 the base system (it was a port).
1336 The afdata and ifnet locks have been changed from mutexes to
1337 rwlocks, network modules will need to be re-compiled.
1340 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1341 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1342 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1343 architecture and 40 bytes on 64-bit architecture. The userland
1344 applications "arp" and "ndp" have been updated accordingly.
1345 The output from "netstat -r" shows only routing entries and
1346 none of the L2 information.
1349 __FreeBSD_version 800057 marks the switchover from the
1350 binary ath hal to source code. Users must add the line:
1352 options AH_SUPPORT_AR5416
1354 to their kernel config files when specifying:
1358 The ath_hal module no longer exists; the code is now compiled
1359 together with the driver in the ath module. It is now
1360 possible to tailor chip support (i.e. reduce the set of chips
1361 and thereby the code size); consult ath_hal(4) for details.
1364 __FreeBSD_version 800054 adds memory barriers to
1365 <machine/atomic.h>, new interfaces to ifnet to facilitate
1366 multiple hardware transmit queues for cards that support
1367 them, and a lock-less ring-buffer implementation to
1368 enable drivers to more efficiently manage queueing of
1372 A new version of ZFS (version 13) has been merged to -HEAD.
1373 This version has zpool attribute "listsnapshots" off by
1374 default, which means "zfs list" does not show snapshots,
1375 and is the same as Solaris behavior.
1378 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1381 The uhci, ohci, ehci and slhci USB Host controller drivers have
1382 been put into separate modules. If you load the usb module
1383 separately through loader.conf you will need to load the
1384 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1385 controller add the following to loader.conf:
1391 The ABI used by the PMC toolset has changed. Please keep
1392 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1396 atapci kernel module now includes only generic PCI ATA
1397 driver. AHCI driver moved to ataahci kernel module.
1398 All vendor-specific code moved into separate kernel modules:
1399 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1400 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1401 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1402 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1405 The TTY subsystem of the kernel has been replaced by a new
1406 implementation, which provides better scalability and an
1407 improved driver model. Most common drivers have been migrated to
1408 the new TTY subsystem, while others have not. The following
1409 drivers have not yet been ported to the new TTY layer:
1412 cy, digi, rc, rp, sio
1418 ng_h4, ng_tty, ppp, sl, snp
1420 Adding these drivers to your kernel configuration file shall
1421 cause compilation to fail.
1424 ntpd has been upgraded to 4.2.4p5.
1427 OpenSSH has been upgraded to 5.1p1.
1429 For many years, FreeBSD's version of OpenSSH preferred DSA
1430 over RSA for host and user authentication keys. With this
1431 upgrade, we've switched to the vendor's default of RSA over
1432 DSA. This may cause upgraded clients to warn about unknown
1433 host keys even for previously known hosts. Users should
1434 follow the usual procedure for verifying host keys before
1435 accepting the RSA key.
1437 This can be circumvented by setting the "HostKeyAlgorithms"
1438 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1441 Please note that the sequence of keys offered for
1442 authentication has been changed as well. You may want to
1443 specify IdentityFile in a different order to revert this
1447 The sio(4) driver has been removed from the i386 and amd64
1448 kernel configuration files. This means uart(4) is now the
1449 default serial port driver on those platforms as well.
1451 To prevent collisions with the sio(4) driver, the uart(4) driver
1452 uses different names for its device nodes. This means the
1453 onboard serial port will now most likely be called "ttyu0"
1454 instead of "ttyd0". You may need to reconfigure applications to
1455 use the new device names.
1457 When using the serial port as a boot console, be sure to update
1458 /boot/device.hints and /etc/ttys before booting the new kernel.
1459 If you forget to do so, you can still manually specify the hints
1460 at the loader prompt:
1462 set hint.uart.0.at="isa"
1463 set hint.uart.0.port="0x3F8"
1464 set hint.uart.0.flags="0x10"
1465 set hint.uart.0.irq="4"
1469 The gpt(8) utility has been removed. Use gpart(8) to partition
1473 The version that Linuxulator emulates was changed from 2.4.2
1474 to 2.6.16. If you experience any problems with Linux binaries
1475 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1476 if it fixes the problem contact emulation mailing list.
1479 ISDN4BSD (I4B) was removed from the src tree. You may need to
1480 update a your kernel configuration and remove relevant entries.
1483 I have checked in code to support multiple routing tables.
1484 See the man pages setfib(1) and setfib(2).
1485 This is a hopefully backwards compatible version,
1486 but to make use of it you need to compile your kernel
1487 with options ROUTETABLES=2 (or more up to 16).
1490 The 802.11 wireless support was redone to enable multi-bss
1491 operation on devices that are capable. The underlying device
1492 is no longer used directly but instead wlanX devices are
1493 cloned with ifconfig. This requires changes to rc.conf files.
1494 For example, change:
1495 ifconfig_ath0="WPA DHCP"
1498 ifconfig_wlan0="WPA DHCP"
1499 see rc.conf(5) for more details. In addition, mergemaster of
1500 /etc/rc.d is highly recommended. Simultaneous update of userland
1501 and kernel wouldn't hurt either.
1503 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1504 modules were merged into the base wlan module. All references
1505 to these modules (e.g. in kernel config files) must be removed.
1508 psm(4) has gained write(2) support in native operation level.
1509 Arbitrary commands can be written to /dev/psm%d and status can
1510 be read back from it. Therefore, an application is responsible
1511 for status validation and error recovery. It is a no-op in
1512 other operation levels.
1515 Support for KSE threading has been removed from the kernel. To
1516 run legacy applications linked against KSE libmap.conf may
1517 be used. The following libmap.conf may be used to ensure
1518 compatibility with any prior release:
1520 libpthread.so.1 libthr.so.1
1521 libpthread.so.2 libthr.so.2
1522 libkse.so.3 libthr.so.3
1525 The layout of struct vmspace has changed. This affects libkvm
1526 and any executables that link against libkvm and use the
1527 kvm_getprocs() function. In particular, but not exclusively,
1528 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1529 The effects are minimal, but it's advisable to upgrade world
1533 The latest em driver no longer has support in it for the
1534 82575 adapter, this is now moved to the igb driver. The
1535 split was done to make new features that are incompatible
1536 with older hardware easier to do.
1539 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1540 likewise the kernel option is now GEOM_LINUX_LVM.
1543 The default NFS mount mode has changed from UDP to TCP for
1544 increased reliability. If you rely on (insecurely) NFS
1545 mounting across a firewall you may need to update your
1549 Belatedly note the addition of m_collapse for compacting
1553 The fts(3) structures have been changed to use adequate
1554 integer types for their members and so to be able to cope
1555 with huge file trees. The old fts(3) ABI is preserved
1556 through symbol versioning in libc, so third-party binaries
1557 using fts(3) should still work, although they will not take
1558 advantage of the extended types. At the same time, some
1559 third-party software might fail to build after this change
1560 due to unportable assumptions made in its source code about
1561 fts(3) structure members. Such software should be fixed
1562 by its vendor or, in the worst case, in the ports tree.
1563 FreeBSD_version 800015 marks this change for the unlikely
1564 case that a portable fix is impossible.
1567 To upgrade to -current after this date, you must be running
1568 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1569 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1572 The ADAPTIVE_GIANT kernel option has been retired because its
1573 functionality is the default now.
1576 The AT keyboard emulation of sunkbd(4) has been turned on
1577 by default. In order to make the special symbols of the Sun
1578 keyboards driven by sunkbd(4) work under X these now have
1579 to be configured the same way as Sun USB keyboards driven
1580 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1582 Option "XkbLayout" "us"
1583 Option "XkbRules" "xorg"
1584 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1587 It has been decided that it is desirable to provide ABI
1588 backwards compatibility to the FreeBSD 4/5/6 versions of the
1589 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1590 broken with the introduction of PCI domain support (see the
1591 20070930 entry). Unfortunately, this required the ABI of
1592 PCIOCGETCONF to be broken again in order to be able to
1593 provide backwards compatibility to the old version of that
1594 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1595 again. As for prominent ports this affects neither pciutils
1596 nor xorg-server this time, the hal port needs to be rebuilt
1600 The misnamed kthread_create() and friends have been renamed
1601 to kproc_create() etc. Many of the callers already
1602 used kproc_start()..
1603 I will return kthread_create() and friends in a while
1604 with implementations that actually create threads, not procs.
1605 Renaming corresponds with version 800002.
1614 Avoid using make -j when upgrading. While generally safe, there are
1615 sometimes problems using -j to upgrade. If your upgrade fails with
1616 -j, please try again without -j. From time to time in the past there
1617 have been problems using -j with buildworld and/or installworld. This
1618 is especially true when upgrading between "distant" versions (eg one
1619 that cross a major release boundary or several minor releases, or when
1620 several months have passed on the -current branch).
1622 Sometimes, obscure build problems are the result of environment
1623 poisoning. This can happen because the make utility reads its
1624 environment when searching for values for global variables. To run
1625 your build attempts in an "environmental clean room", prefix all make
1626 commands with 'env -i '. See the env(1) manual page for more details.
1628 When upgrading from one major version to another it is generally best
1629 to upgrade to the latest code in the currently installed branch first,
1630 then do an upgrade to the new branch. This is the best-tested upgrade
1631 path, and has the highest probability of being successful. Please try
1632 this approach before reporting problems with a major version upgrade.
1634 When upgrading a live system, having a root shell around before
1635 installing anything can help undo problems. Not having a root shell
1636 around can lead to problems if pam has changed too much from your
1637 starting point to allow continued authentication after the upgrade.
1641 When upgrading the boot ZFS pool to a new version, always follow
1644 1.) recompile and reinstall the ZFS boot loader and boot block
1645 (this is part of "make buildworld" and "make installworld")
1647 2.) update the ZFS boot block on your boot drive
1649 The following example updates the ZFS boot block on the first
1650 partition (freebsd-boot) of a GPT partitioned drive ad0:
1651 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1653 Non-boot pools do not need these updates.
1657 If you are updating from a prior version of FreeBSD (even one just
1658 a few days old), you should follow this procedure. It is the most
1659 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1661 make kernel-toolchain
1662 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1663 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1665 To test a kernel once
1666 ---------------------
1667 If you just want to boot a kernel once (because you are not sure
1668 if it works, or if you want to boot a known bad kernel to provide
1669 debugging information) run
1670 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1671 nextboot -k testkernel
1673 To just build a kernel when you know that it won't mess you up
1674 --------------------------------------------------------------
1675 This assumes you are already running a CURRENT system. Replace
1676 ${arch} with the architecture of your machine (e.g. "i386",
1677 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1679 cd src/sys/${arch}/conf
1680 config KERNEL_NAME_HERE
1681 cd ../compile/KERNEL_NAME_HERE
1686 If this fails, go to the "To build a kernel" section.
1688 To rebuild everything and install it on the current system.
1689 -----------------------------------------------------------
1690 # Note: sometimes if you are running current you gotta do more than
1691 # is listed here if you are upgrading from a really old current.
1693 <make sure you have good level 0 dumps>
1695 make kernel KERNCONF=YOUR_KERNEL_HERE
1697 <reboot in single user> [3]
1704 To cross-install current onto a separate partition
1705 --------------------------------------------------
1706 # In this approach we use a separate partition to hold
1707 # current's root, 'usr', and 'var' directories. A partition
1708 # holding "/", "/usr" and "/var" should be about 2GB in
1711 <make sure you have good level 0 dumps>
1714 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1715 <maybe newfs current's root partition>
1716 <mount current's root partition on directory ${CURRENT_ROOT}>
1717 make installworld DESTDIR=${CURRENT_ROOT}
1718 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1719 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1720 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1721 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1722 <reboot into current>
1723 <do a "native" rebuild/install as described in the previous section>
1724 <maybe install compatibility libraries from ports/misc/compat*>
1728 To upgrade in-place from stable to current
1729 ----------------------------------------------
1730 <make sure you have good level 0 dumps>
1732 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1734 <reboot in single user> [3]
1741 Make sure that you've read the UPDATING file to understand the
1742 tweaks to various things you need. At this point in the life
1743 cycle of current, things change often and you are on your own
1744 to cope. The defaults can also change, so please read ALL of
1745 the UPDATING entries.
1747 Also, if you are tracking -current, you must be subscribed to
1748 freebsd-current@freebsd.org. Make sure that before you update
1749 your sources that you have read and understood all the recent
1750 messages there. If in doubt, please track -stable which has
1751 much fewer pitfalls.
1753 [1] If you have third party modules, such as vmware, you
1754 should disable them at this point so they don't crash your
1757 [3] From the bootblocks, boot -s, and then do
1762 adjkerntz -i # if CMOS is wall time
1763 Also, when doing a major release upgrade, it is required that
1764 you boot into single user mode to do the installworld.
1766 [4] Note: This step is non-optional. Failure to do this step
1767 can result in a significant reduction in the functionality of the
1768 system. Attempting to do it by hand is not recommended and those
1769 that pursue this avenue should read this file carefully, as well
1770 as the archives of freebsd-current and freebsd-hackers mailing lists
1771 for potential gotchas. The -U option is also useful to consider.
1772 See mergemaster(8) for more information.
1774 [5] Usually this step is a noop. However, from time to time
1775 you may need to do this if you get unknown user in the following
1776 step. It never hurts to do it all the time. You may need to
1777 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1778 install) after the buildworld before this step if you last updated
1779 from current before 20130425 or from -stable before 20130430.
1781 [6] This only deletes old files and directories. Old libraries
1782 can be deleted by "make delete-old-libs", but you have to make
1783 sure that no program is using those libraries anymore.
1785 [8] In order to have a kernel that can run the 4.x binaries needed to
1786 do an installworld, you must include the COMPAT_FREEBSD4 option in
1787 your kernel. Failure to do so may leave you with a system that is
1788 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1789 required to run the 5.x binaries on more recent kernels. And so on
1790 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1792 Make sure that you merge any new devices from GENERIC since the
1793 last time you updated your kernel config file.
1795 [9] When checking out sources, you must include the -P flag to have
1796 cvs prune empty directories.
1798 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1799 "?=" instead of the "=" assignment operator, so that buildworld can
1800 override the CPUTYPE if it needs to.
1802 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1803 not on the command line, or in /etc/make.conf. buildworld will
1804 warn if it is improperly defined.
1807 This file contains a list, in reverse chronological order, of major
1808 breakages in tracking -current. It is not guaranteed to be a complete
1809 list of such breakages, and only contains entries since October 10, 2007.
1810 If you need to see UPDATING entries from before that date, you will need
1811 to fetch an UPDATING file from an older FreeBSD release.
1813 Copyright information:
1815 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1817 Redistribution, publication, translation and use, with or without
1818 modification, in full or in part, in any form or format of this
1819 document are permitted without further permission from the author.
1821 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1822 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1823 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1824 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1825 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1826 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1827 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1828 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1829 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1830 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1831 POSSIBILITY OF SUCH DAMAGE.
1833 Contact Warner Losh if you have any questions about your use of