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