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