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 wish 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. If you are updating a big-endian mips64 machine
295 from before this change, you may need to set MACHINE_ARCH=mips64 in
296 your environment before the new build system will recognize your machine.
299 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
303 Now unix domain sockets behave "as expected" on nullfs(5). Previously
304 nullfs(5) did not pass through all behaviours to the underlying layer,
305 as a result if we bound to a socket on the lower layer we could connect
306 only to the lower path; if we bound to the upper layer we could connect
307 only to the upper path. The new behavior is one can connect to both the
308 lower and the upper paths regardless what layer path one binds to.
311 The getifaddrs upgrade path broken with 20111215 has been restored.
312 If you have upgraded in between 20111215 and 20120209 you need to
313 recompile libc again with your kernel. You still need to recompile
314 world to be able to configure CARP but this restriction already
318 The set_rcvar() function has been removed from /etc/rc.subr. All
319 base and ports rc.d scripts have been updated, so if you have a
320 port installed with a script in /usr/local/etc/rc.d you can either
321 hand-edit the rcvar= line, or reinstall the port.
323 An easy way to handle the mass-update of /etc/rc.d:
324 rm /etc/rc.d/* && mergemaster -i
327 panic(9) now stops other CPUs in the SMP systems, disables interrupts
328 on the current CPU and prevents other threads from running.
329 This behavior can be reverted using the kern.stop_scheduler_on_panic
331 The new behavior can be incompatible with kern.sync_on_panic.
334 The carp(4) facility has been changed significantly. Configuration
335 of the CARP protocol via ifconfig(8) has changed, as well as format
336 of CARP events submitted to devd(8) has changed. See manual pages
337 for more information. The arpbalance feature of carp(4) is currently
338 not supported anymore.
340 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
341 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
342 need to be recompiled.
345 The acpi_wmi(4) status device /dev/wmistat has been renamed to
349 The option VFS_ALLOW_NONMPSAFE option has been added in order to
350 explicitely support non-MPSAFE filesystems.
351 It is on by default for all supported platform at this present
355 The broken amd(4) driver has been replaced with esp(4) in the amd64,
356 i386 and pc98 GENERIC kernel configuration files.
359 sysinstall has been removed
362 The stable/9 branch created in subversion. This corresponds to the
363 RELENG_9 branch in CVS.
366 This commit modifies vfs_register() so that it uses a hash
367 calculation to set vfc_typenum, which is enabled by default.
368 The first time a system is booted after this change, the
369 vfc_typenum values will change for all file systems. The
370 main effect of this is a change to the NFS server file handles
371 for file systems that use vfc_typenum in their fsid, such as ZFS.
372 It will, however, prevent vfc_typenum from changing when file
373 systems are loaded in a different order for subsequent reboots.
374 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
375 until you are ready to remount all NFS clients after a reboot.
378 Bump the shared library version numbers for libraries that
379 do not use symbol versioning, have changed the ABI compared
380 to stable/8 and which shared library version was not bumped.
381 Done as part of 9.0-RELEASE cycle.
384 During the merge of Capsicum features, the fget(9) KPI was modified.
385 This may require the rebuilding of out-of-tree device drivers --
386 issues have been reported specifically with the nVidia device driver.
387 __FreeBSD_version is bumped to 900041.
389 Also, there is a period between 20110811 and 20110814 where the
390 special devices /dev/{stdin,stdout,stderr} did not work correctly.
391 Building world from a kernel during that window may not work.
394 The packet filter (pf) code has been updated to OpenBSD 4.5.
395 You need to update userland tools to be in sync with kernel.
396 This update breaks backward compatibility with earlier pfsync(4)
397 versions. Care must be taken when updating redundant firewall setups.
400 The following sysctls and tunables are retired on x86 platforms:
402 machdep.hlt_logical_cpus
403 The following sysctl is retired:
404 machdep.hyperthreading_allowed
405 The sysctls were supposed to provide a way to dynamically offline and
406 online selected CPUs on x86 platforms, but the implementation has not
407 been reliable especially with SCHED_ULE scheduler.
408 machdep.hyperthreading_allowed tunable is still available to ignore
409 hyperthreading CPUs at OS level.
410 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
411 where X is an APIC ID of a CPU. Be advised, though, that disabling
412 CPUs in non-uniform fashion will result in non-uniform topology and
413 may lead to sub-optimal system performance with SCHED_ULE, which is
417 cpumask_t type is retired and cpuset_t is used in order to describe
421 Changes to ifconfig(8) for dynamic address family detection mandate
422 that you are running a kernel of 20110525 or later. Make sure to
423 follow the update procedure to boot a new kernel before installing
427 Support for sun4v architecture is officially dropped
430 Several KPI breaking changes have been committed to the mii(4) layer,
431 the PHY drivers and consequently some Ethernet drivers using mii(4).
432 This means that miibus.ko and the modules of the affected Ethernet
433 drivers need to be recompiled.
435 Note to kernel developers: Given that the OUI bit reversion problem
436 was fixed as part of these changes all mii(4) commits related to OUIs,
437 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
438 handling, no longer can be merged verbatim to stable/8 and previous
442 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
443 into their kernel configurations along with 'device pci'.
446 The default NFS client is now the new NFS client, so fstype "newnfs"
447 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
448 Although mounts via fstype "nfs" will usually work without userland
449 changes, it is recommended that the mount(8) and mount_nfs(8)
450 commands be rebuilt from sources and that a link to mount_nfs called
451 mount_oldnfs be created. The new client is compiled into the
452 kernel with "options NFSCL" and this is needed for diskless root
453 file systems. The GENERIC kernel configs have been changed to use
454 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
455 To use the regular/old client, you can "mount -t oldnfs ...". For
456 a diskless root file system, you must also include a line like:
458 vfs.root.mountfrom="oldnfs:"
460 in the boot/loader.conf on the root fs on the NFS server to make
461 a diskless root fs use the old client.
464 The GENERIC kernels for all architectures now default to the new
465 CAM-based ATA stack. It means that all legacy ATA drivers were
466 removed and replaced by respective CAM drivers. If you are using
467 ATA device names in /etc/fstab or other places, make sure to update
468 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
469 where 'Y's are the sequential numbers starting from zero for each type
470 in order of detection, unless configured otherwise with tunables,
471 see cam(4)). There will be symbolic links created in /dev/ to map
472 old adX devices to the respective adaY. They should provide basic
473 compatibility for file systems mounting in most cases, but they do
474 not support old user-level APIs and do not have respective providers
475 in GEOM. Consider using updated management tools with new device names.
477 It is possible to load devices ahci, ata, siis and mvs as modules,
478 but option ATA_CAM should remain in kernel configuration to make ata
479 module work as CAM driver supporting legacy ATA controllers. Device ata
480 still can be used in modular fashion (atacore + ...). Modules atadisk
481 and atapi* are not used and won't affect operation in ATA_CAM mode.
482 Note that to use CAM-based ATA kernel should include CAM devices
483 scbus, pass, da (or explicitly ada), cd and optionally others. All of
484 them are parts of the cam module.
486 ataraid(4) functionality is now supported by the RAID GEOM class.
487 To use it you can load geom_raid kernel module and use graid(8) tool
488 for management. Instead of /dev/arX device names, use /dev/raid/rX.
490 No kernel config options or code have been removed, so if a problem
491 arises, please report it and optionally revert to the old ATA stack.
492 In order to do it you can remove from the kernel config:
497 , and instead add back:
498 device atadisk # ATA disk drives
499 device ataraid # ATA RAID drives
500 device atapicd # ATAPI CDROM drives
501 device atapifd # ATAPI floppy drives
502 device atapist # ATAPI tape drives
505 The default NFS server has been changed to the new server, which
506 was referred to as the experimental server. If you need to switch
507 back to the old NFS server, you must now put the "-o" option on
508 both the mountd and nfsd commands. This can be done using the
509 mountd_flags and nfs_server_flags rc.conf variables until an
510 update to the rc scripts is committed, which is coming soon.
513 The GNU Objective-C runtime library (libobjc), and other Objective-C
514 related components have been removed from the base system. If you
515 require an Objective-C library, please use one of the available ports.
518 ath(4) has been split into bus- and device- modules. if_ath contains
519 the HAL, the TX rate control and the network device code. if_ath_pci
520 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
521 contains the AHB glue. Users need to load both if_ath_pci and if_ath
522 in order to use ath on everything else.
524 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
525 need to load if_ath and if_ath_pci for ath(4) operation.
528 As part of the replacement of sysinstall, the process of building
529 release media has changed significantly. For details, please re-read
530 release(7), which has been updated to reflect the new build process.
533 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
534 is the last available version under GPLv2. It brings a number of new
535 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
536 4.1 and SSE 4.2), better support for powerpc64, a number of new
537 directives, and lots of other small improvements. See the ChangeLog
538 file in contrib/binutils for the full details.
541 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
542 compliant, and will now use half of hash for authentication.
543 This will break interoperability with all stacks (including all
544 actual FreeBSD versions) who implement
545 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
547 The only workaround with such peers is to use another HMAC
548 algorithm for IPsec ("phase 2") authentication.
551 Remove the uio_yield prototype and symbol. This function has
552 been misnamed since it was introduced and should not be
553 globally exposed with this name. The equivalent functionality
554 is now available using kern_yield(curthread->td_user_pri).
555 The function remains undocumented.
558 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
559 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
560 for scalar sysctls is defined but disabled. Code that needs
561 UQUAD to pass the type checking that must compile on older
562 systems where the define is not present can check against
563 __FreeBSD_version >= 900030.
565 The system dialog(1) has been replaced with a new version previously
566 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
567 with the previous version, but the libdialog associated with it has
568 a largely incompatible API. As such, the original version of libdialog
569 will be kept temporarily as libodialog, until its base system consumers
570 are replaced or updated. Bump __FreeBSD_version to 900030.
573 If you are trying to run make universe on a -stable system, and you get
574 the following warning:
575 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
576 unknown. config(8) likely too old."
577 or something similar to it, then you must upgrade your -stable system
578 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
579 stable/8) or build the config from the latest stable/8 branch and
580 install it on your system.
582 Prior to this date, building a current universe on 8-stable system from
583 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
584 error in the first kernel build phase. A new config on those old
585 systems will fix that problem for older versions of -current.
588 The TCP stack has been modified to allow Khelp modules to interact with
589 it via helper hook points and store per-connection data in the TCP
590 control block. Bump __FreeBSD_version to 900029. User space tools that
591 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
595 Generic IEEE 802.3 annex 31B full duplex flow control support has been
596 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
597 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
598 to take advantage of it instead of using custom implementations. This
599 means that these drivers now no longer unconditionally advertise
600 support for flow control but only do so if flow control is a selected
601 media option. This was implemented in the generic support that way in
602 order to allow flow control to be switched on and off via ifconfig(8)
603 with the PHY specific default to typically off in order to protect
604 from unwanted effects. Consequently, if you used flow control with
605 one of the above mentioned drivers you now need to explicitly enable
607 ifconfig bge0 media auto mediaopt flowcontrol
609 Along with the above mentioned changes generic support for setting
610 1000baseT master mode also has been added and brgphy(4), ciphy(4),
611 e1000phy(4) as well as ip1000phy(4) have been converted to take
612 advantage of it. This means that these drivers now no longer take the
613 link0 parameter for selecting master mode but the master media option
614 has to be used instead, for example like in the following:
615 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
617 Selection of master mode now is also available with all other PHY
618 drivers supporting 1000baseT.
621 The TCP stack has received a significant update to add support for
622 modularised congestion control and generally improve the clarity of
623 congestion control decisions. Bump __FreeBSD_version to 900025. User
624 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
625 sockstat) need to be recompiled.
628 The man(1) utility has been replaced by a new version that no longer
629 uses /etc/manpath.config. Please consult man.conf(5) for how to
630 migrate local entries to the new format.
633 The copyright strings printed by login(1) and sshd(8) at the time of a
634 new connection have been removed to follow other operating systems and
638 A workaround for a fixed ld bug has been removed in kernel code,
639 so make sure that your system ld is built from sources after
640 revision 210245 from 2010-07-19 (r211583 if building head kernel
641 on stable/8, r211584 for stable/7; both from 2010-08-21).
642 A symptom of incorrect ld version is different addresses for
643 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
646 The $ipv6_prefer variable in rc.conf(5) has been split into
647 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
649 The $ip6addrctl_policy is a variable to choose a pre-defined
650 address selection policy set by ip6addrctl(8). A value
651 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
654 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
655 flag (see an entry of 20090926) is set on an interface with no
656 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
657 security reason. If you want IPv6 link-local address on all
658 interfaces by default, set this to "YES".
660 The old ipv6_prefer="YES" is equivalent to
661 ipv6_activate_all_interfaces="YES" and
662 ip6addrctl_policy="ipv6_prefer".
665 DTrace has grown support for userland tracing. Due to this, DTrace is
666 now i386 and amd64 only.
667 dtruss(1) is now installed by default on those systems and a new
668 kernel module is needed for userland tracing: fasttrap.
669 No changes to your kernel config file are necessary to enable
670 userland tracing, but you might consider adding 'STRIP=' and
671 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
672 to have informative userland stack traces in DTrace (ustack).
675 The acpi_aiboost(4) driver has been removed in favor of the new
676 aibs(4) driver. You should update your kernel configuration file.
679 BSD grep has been imported to the base system and it is built by
680 default. It is completely BSD licensed, highly GNU-compatible, uses
681 less memory than its GNU counterpart and has a small codebase.
682 However, it is slower than its GNU counterpart, which is mostly
683 noticeable for larger searches, for smaller ones it is measurable
684 but not significant. The reason is complex, the most important factor
685 is that we lack a modern and efficient regex library and GNU
686 overcomes this by optimizing the searches internally. Future work
687 on improving the regex performance is planned, for the meantime,
688 users that need better performance, can build GNU grep instead by
689 setting the WITH_GNU_GREP knob.
692 Due to the import of powerpc64 support, all existing powerpc kernel
693 configuration files must be updated with a machine directive like this:
694 machine powerpc powerpc
696 In addition, an updated config(8) is required to build powerpc kernels
700 A new version of ZFS (version 15) has been merged to -HEAD.
701 This version uses a python library for the following subcommands:
702 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
703 For full functionality of these commands the following port must
704 be installed: sysutils/py-zfs
707 'vm_page's are now hashed by physical address to an array of mutexes.
708 Currently this is only used to serialize access to hold_count. Over
709 time the page queue mutex will be peeled away. This changes the size
710 of pmap on every architecture. And requires all callers of vm_page_hold
711 and vm_page_unhold to be updated.
714 WITH_CTF can now be specified in src.conf (not recommended, there
715 are some problems with static executables), make.conf (would also
716 affect ports which do not use GNU make and do not override the
717 compile targets) or in the kernel config (via "makeoptions
719 When WITH_CTF was specified there before this was silently ignored,
720 so make sure that WITH_CTF is not used in places which could lead
721 to unwanted behavior.
724 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
725 to allow 32-bit compatibility on non-x86 platforms. All kernel
726 configurations on amd64 and ia64 platforms using these options must
727 be modified accordingly.
730 The utmp user accounting database has been replaced with utmpx,
731 the user accounting interface standardized by POSIX.
732 Unfortunately the semantics of utmp and utmpx don't match,
733 making it practically impossible to support both interfaces.
734 The user accounting database is used by tools like finger(1),
735 last(1), talk(1), w(1) and ac(8).
737 All applications in the base system use utmpx. This means only
738 local binaries (e.g. from the ports tree) may still use these
739 utmp database files. These applications must be rebuilt to make
742 After the system has been upgraded, it is safe to remove the old
743 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
744 assuming their contents is of no importance anymore. Old wtmp
745 databases can only be used by last(1) and ac(8) after they have
746 been converted to the new format using wtmpcvt(1).
749 Introduce the kernel thread "deadlock resolver" (which can be enabled
750 via the DEADLKRES option, see NOTES for more details) and the
751 sleepq_type() function for sleepqueues.
754 The rc.firewall and rc.firewall6 were unified, and
755 rc.firewall6 and rc.d/ip6fw were removed.
756 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
757 variables are obsoleted. Instead, the following new rc
758 variables are added to rc.d/ipfw:
760 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
761 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
762 firewall_simple_onet_ipv6, firewall_trusted_ipv6
764 The meanings correspond to the relevant IPv4 variables.
770 The default terminal emulation for syscons(4) has been changed
771 from cons25 to xterm on all platforms except pc98. This means
772 that the /etc/ttys file needs to be updated to ensure correct
773 operation of applications on the console.
775 The terminal emulation style can be toggled per window by using
776 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
777 options can be used to change the compile-time default back to
780 To prevent graphical artifacts, make sure the TERM environment
781 variable is set to match the terminal emulation that is being
782 performed by syscons(4).
785 The layout of the structure ieee80211req_scan_result has changed.
786 Applications that require wireless scan results (e.g. ifconfig(8))
787 from net80211 need to be recompiled.
789 Applications such as wpa_supplicant(8) may require a full world
790 build without using NO_CLEAN in order to get synchronized with the
794 The iwn(4) driver has been updated to support the 5000 and 5150 series.
795 There's one kernel module for each firmware. Adding "device iwnfw"
796 to the kernel configuration file means including all three firmware
797 images inside the kernel. If you want to include just the one for
798 your wireless card, use the devices iwn4965fw, iwn5000fw or
802 The rc.d/network_ipv6, IPv6 configuration script has been integrated
803 into rc.d/netif. The changes are the following:
805 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
806 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
807 Note that both variables need the "inet6" keyword at the head.
809 Do not set $ipv6_network_interfaces manually if you do not
810 understand what you are doing. It is not needed in most cases.
812 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
815 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
816 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
818 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
819 all configured interfaces have "inet6 accept_rtadv" in the
820 $ifconfig_IF_ipv6. These are for backward compatibility.
822 3. A new variable $ipv6_prefer has been added. If NO, IPv6
823 functionality of interfaces with no corresponding
824 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
825 and the default address selection policy of ip6addrctl(8)
826 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
827 Note that if you want to configure IPv6 functionality on the
828 disabled interfaces after boot, first you need to clear the flag by
829 using ifconfig(8) like:
831 ifconfig em0 inet6 -ifdisabled
833 If YES, the default address selection policy is set as
836 The default value of $ipv6_prefer is NO.
838 4. If your system need to receive Router Advertisement messages,
839 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
840 scripts automatically invoke rtsol(8) when the interface becomes
841 UP. The Router Advertisement messages are used for SLAAC
842 (State-Less Address AutoConfiguration).
845 802.11s D3.03 support was committed. This is incompatible with the
846 previous code, which was based on D3.0.
849 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
850 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
851 control whether accepting Router Advertisement messages or not.
852 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
853 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
854 The ifconfig(8) utility now supports these flags.
857 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
858 mount(8) and -a option for df(1) to see them.
861 The old tunable hw.bus.devctl_disable has been superseded by
862 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
863 replaced by hw.bus.devctl_queue=0. The default for this new tunable
867 Remove the option STOP_NMI. The default action is now to use NMI only
868 for KDB via the newly introduced function stop_cpus_hard() and
869 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
872 The stable/8 branch created in subversion. This corresponds to the
873 RELENG_8 branch in CVS.
876 Bump the shared library version numbers for all libraries that do not
877 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
878 __FreeBSD_version to 800105.
881 Due to changes in the implementation of virtual network stack support,
882 all network-related kernel modules must be recompiled. As this change
883 breaks the ABI, bump __FreeBSD_version to 800104.
886 The TOE interface to the TCP syncache has been modified to remove
887 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
888 The cxgb driver is the only TOE consumer affected by this change, and
889 needs to be recompiled along with the kernel. As this change breaks
890 the ABI, bump __FreeBSD_version to 800103.
893 Padding has been added to struct tcpcb, sackhint and tcpstat in
894 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
895 maintaining the ABI. However, this change breaks the ABI, so bump
896 __FreeBSD_version to 800102. User space tools that rely on the size of
897 any of these structs (e.g. sockstat) need to be recompiled.
900 The NFS_LEGACYRPC option has been removed along with the old kernel
901 RPC implementation that this option selected. Kernel configurations
902 may need to be adjusted.
905 The network interface device nodes at /dev/net/<interface> have been
906 removed. All ioctl operations can be performed the normal way using
907 routing sockets. The kqueue functionality can generally be replaced
908 with routing sockets.
911 The documentation from the FreeBSD Documentation Project (Handbook,
912 FAQ, etc.) is now installed via packages by sysinstall(8) and under
913 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
916 The ABI of various structures related to the SYSV IPC API have been
917 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
918 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
922 Layout of struct vnet has changed as routing related variables were
923 moved to their own Vimage module. Modules need to be recompiled. Bump
924 __FreeBSD_version to 800099.
927 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
928 respectively. As long as no more than 16 groups per process are used,
929 no changes should be visible. When more than 16 groups are used, old
930 binaries may fail if they call getgroups() or getgrouplist() with
931 statically sized storage. Recompiling will work around this, but
932 applications should be modified to use dynamically allocated storage
933 for group arrays as POSIX.1-2008 does not cap an implementation's
934 number of supported groups at NGROUPS_MAX+1 as previous versions did.
936 NFS and portalfs mounts may also be affected as the list of groups is
937 truncated to 16. Users of NFS who use more than 16 groups, should
938 take care that negative group permissions are not used on the exported
939 file systems as they will not be reliable unless a GSSAPI based
940 authentication method is used.
943 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
944 option compiles in the support for adaptive spinning for lockmgrs
945 which want to enable it. The lockinit() function now accepts the flag
946 LK_ADAPTIVE in order to make the lock object subject to adaptive
947 spinning when both held in write and read mode.
950 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
951 changed. User applications that use this ioctl need to be rebuilt.
954 The layout of struct thread has changed. Kernel and modules need to
958 The layout of structs ifnet, domain, protosw and vnet_net has changed.
959 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
962 window(1) has been removed from the base system. It can now be
963 installed from ports. The port is called misc/window.
966 The way we are storing and accessing `routing table' entries has
967 changed. Programs reading the FIB, like netstat, need to be
971 A new netisr implementation has been added for FreeBSD 8. Network
972 file system modules, such as igmp, ipdivert, and others, should be
974 Bump __FreeBSD_version to 800096.
977 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
981 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
982 Bump __FreeBSD_version to 800094.
985 Add mnt_xflag field to 'struct mount'. File system modules need to be
987 Bump __FreeBSD_version to 800093.
990 The compiling option ADAPTIVE_SX has been retired while it has been
991 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
992 The KPI for sx_init_flags() changes as accepting flags:
993 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
994 been introduced in order to handle the reversed logic.
995 Bump __FreeBSD_version to 800092.
998 Add support for hierarchical jails. Remove global securelevel.
999 Bump __FreeBSD_version to 800091.
1002 The layout of struct vnet_net has changed, therefore modules
1004 Bump __FreeBSD_version to 800090.
1007 The newly imported zic(8) produces a new format in the output. Please
1008 run tzsetup(8) to install the newly created data to /etc/localtime.
1011 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1012 hw.usb.* and is now consistent again with previous releases.
1015 802.11 monitor mode support was revised and driver api's were changed.
1016 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1017 of DLT_IEEE802_11. No user-visible data structures were changed but
1018 applications that use DLT_IEEE802_11 may require changes.
1019 Bump __FreeBSD_version to 800088.
1022 The layout of the following structs has changed: sysctl_oid,
1023 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1024 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1025 panics may be experienced. World rebuild is required for
1026 correctly checking networking state from userland.
1027 Bump __FreeBSD_version to 800085.
1030 MLDv2 and Source-Specific Multicast (SSM) have been merged
1031 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1032 The implementation of SSM within FreeBSD's IPv6 stack closely
1033 follows the IPv4 implementation.
1035 For kernel developers:
1037 * The most important changes are that the ip6_output() and
1038 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1039 and this lock has been downgraded to a non-recursive mutex.
1041 * As with the changes to the IPv4 stack to support SSM, filtering
1042 of inbound multicast traffic must now be performed by transport
1043 protocols within the IPv6 stack. This does not apply to TCP and
1044 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1046 * The KPIs used by IPv6 multicast are similar to those used by
1047 the IPv4 stack, with the following differences:
1048 * im6o_mc_filter() is analogous to imo_multicast_filter().
1049 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1050 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1051 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1052 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1053 for MLDv1 have an additional 'timer' argument which is used to
1054 jitter the initial membership report for the solicited-node
1055 multicast membership on-link.
1056 * This is not strictly needed for MLDv2, which already jitters
1057 its report transmissions. However, the 'timer' argument is
1058 preserved in case MLDv1 is active on the interface.
1060 * The KAME linked-list based IPv6 membership implementation has
1061 been refactored to use a vector similar to that used by the IPv4
1063 Code which maintains a list of its own multicast memberships
1064 internally, e.g. carp, has been updated to reflect the new
1067 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1068 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1069 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1070 implementation constraint which needs to be addressed in HEAD.
1072 For application developers:
1074 * The changes are broadly similar to those made for the IPv4
1077 * The use of IPv4 and IPv6 multicast socket options on the same
1078 socket, using mapped addresses, HAS NOT been tested or supported.
1080 * There are a number of issues with the implementation of various
1081 IPv6 multicast APIs which need to be resolved in the API surface
1082 before the implementation is fully compatible with KAME userland
1083 use, and these are mostly to do with interface index treatment.
1085 * The literature available discusses the use of either the delta / ASM
1086 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1087 using setsourcefilter(3)/getsourcefilter(3). For more information
1088 please refer to RFC 3768, 'Socket Interface Extensions for
1089 Multicast Source Filters'.
1091 * Applications which use the published RFC 3678 APIs should be fine.
1093 For systems administrators:
1095 * The mtest(8) utility has been refactored to support IPv6, in
1096 addition to IPv4. Interface addresses are no longer accepted
1097 as arguments, their names must be used instead. The utility
1098 will map the interface name to its first IPv4 address as
1099 returned by getifaddrs(3).
1101 * The ifmcstat(8) utility has also been updated to print the MLDv2
1102 endpoint state and source filter lists via sysctl(3).
1104 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1105 loopback of IPv6 multicast datagrams by default; it defaults to 1
1106 to preserve the existing behaviour. Disabling multicast loopback is
1107 recommended for optimal system performance.
1109 * The IPv6 MROUTING code has been changed to examine this sysctl
1110 instead of attempting to perform a group lookup before looping
1111 back forwarded datagrams.
1113 Bump __FreeBSD_version to 800084.
1116 Implement low-level Bluetooth HCI API.
1117 Bump __FreeBSD_version to 800083.
1120 The layout of struct malloc_type, used by modules to register new
1121 memory allocation types, has changed. Most modules will need to
1122 be rebuilt or panics may be experienced.
1123 Bump __FreeBSD_version to 800081.
1126 Anticipate overflowing inp_flags - add inp_flags2.
1127 This changes most offsets in inpcb, so checking v4 connection
1128 state will require a world rebuild.
1129 Bump __FreeBSD_version to 800080.
1132 Add an llentry to struct route and struct route_in6. Modules
1133 embedding a struct route will need to be recompiled.
1134 Bump __FreeBSD_version to 800079.
1137 The size of rt_metrics_lite and by extension rtentry has changed.
1138 Networking administration apps will need to be recompiled.
1139 The route command now supports show as an alias for get, weighting
1140 of routes, sticky and nostick flags to alter the behavior of stateful
1142 Bump __FreeBSD_version to 800078.
1145 Do not use Giant for kbdmux(4) locking. This is wrong and
1146 apparently causing more problems than it solves. This will
1147 re-open the issue where interrupt handlers may race with
1148 kbdmux(4) in polling mode. Typical symptoms include (but
1149 not limited to) duplicated and/or missing characters when
1150 low level console functions (such as gets) are used while
1151 interrupts are enabled (for example geli password prompt,
1152 mountroot prompt etc.). Disabling kbdmux(4) may help.
1155 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1156 kernel modules referencing any of the above need to be recompiled.
1157 Bump __FreeBSD_version to 800075.
1160 GEOM_PART has become the default partition slicer for storage devices,
1161 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1162 introduces some changes:
1164 MSDOS/EBR: the devices created from MSDOS extended partition entries
1165 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1166 to devices with offset-based names. fstabs may need to be modified.
1168 BSD: the "geometry does not match label" warning is harmless in most
1169 cases but it points to problems in file system misalignment with
1170 disk geometry. The "c" partition is now implicit, covers the whole
1171 top-level drive and cannot be (mis)used by users.
1173 General: Kernel dumps are now not allowed to be written to devices
1174 whose partition types indicate they are meant to be used for file
1175 systems (or, in case of MSDOS partitions, as something else than
1178 Most of these changes date approximately from 200812.
1181 The uscanner(4) driver has been removed from the kernel. This follows
1182 Linux removing theirs in 2.6 and making libusb the default interface
1183 (supported by sane).
1186 The multicast forwarding code has been cleaned up. netstat(1)
1187 only relies on KVM now for printing bandwidth upcall meters.
1188 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1189 ip6_mroute_mod respectively. The config(5) options for statically
1190 compiling this code remain the same, i.e. 'options MROUTING'.
1193 Support for the IFF_NEEDSGIANT network interface flag has been
1194 removed, which means that non-MPSAFE network device drivers are no
1195 longer supported. In particular, if_ar, if_sr, and network device
1196 drivers from the old (legacy) USB stack can no longer be built or
1200 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1201 a bunch of new language catalog files have also been added.
1202 This means that some common libc messages are now localized and
1203 they depend on the LC_MESSAGES environmental variable.
1206 The k8temp(4) driver has been renamed to amdtemp(4) since
1207 support for Family 10 and Family 11 CPU families was added.
1210 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1211 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1213 For kernel developers, the most important changes are that the
1214 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1215 and this lock has been downgraded to a non-recursive mutex.
1217 Transport protocols (UDP, Raw IP) are now responsible for filtering
1218 inbound multicast traffic according to group membership and source
1219 filters. The imo_multicast_filter() KPI exists for this purpose.
1220 Transports which do not use multicast (SCTP, TCP) already reject
1221 multicast by default. Forwarding and receive performance may improve
1222 as a mutex acquisition is no longer needed in the ip_input()
1223 low-level input path. in_addmulti() and in_delmulti() are shimmed
1224 to new KPIs which exist to support SSM in-kernel.
1226 For application developers, it is recommended that loopback of
1227 multicast datagrams be disabled for best performance, as this
1228 will still cause the lock to be taken for each looped-back
1229 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1230 be tuned to 0 to disable loopback by default; it defaults to 1
1231 to preserve the existing behaviour.
1233 For systems administrators, to obtain best performance with
1234 multicast reception and multiple groups, it is always recommended
1235 that a card with a suitably precise hash filter is used. Hash
1236 collisions will still result in the lock being taken within the
1237 transport protocol input path to check group membership.
1239 If deploying FreeBSD in an environment with IGMP snooping switches,
1240 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1241 enabled; this forces 224.0.0.0/24 group membership to be announced
1244 The size of 'struct igmpstat' has changed; netstat needs to be
1245 recompiled to reflect this.
1246 Bump __FreeBSD_version to 800070.
1249 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1250 updated to use it. This requires a buildworld/installworld in order to
1251 update the library and dependencies (usbconfig, etc). Its advisable to
1252 rebuild all ports which uses libusb. More specific directions are given
1253 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1254 libusb are no longer required and can be removed.
1257 A workaround is committed to allow the creation of System V shared
1258 memory segment of size > 2 GB on the 64-bit architectures.
1259 Due to a limitation of the existing ABI, the shm_segsz member
1260 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1261 wrong for large segments. Note that limits must be explicitly
1262 raised to allow such segments to be created.
1265 The layout of struct ifnet has changed, requiring a rebuild of all
1266 network device driver modules.
1269 The /dev handling for the new USB stack has changed, a
1270 buildworld/installworld is required for libusb20.
1273 The new USB2 stack has now been permanently moved in and all kernel and
1274 module names reverted to their previous values (eg, usb, ehci, ohci,
1275 ums, ...). The old usb stack can be compiled in by prefixing the name
1276 with the letter 'o', the old usb modules have been removed.
1277 Updating entry 20090216 for xorg and 20090215 for libmap may still
1281 The rc.conf(5) option if_up_delay has been renamed to
1282 defaultroute_delay to better reflect its purpose. If you have
1283 customized this setting in /etc/rc.conf you need to update it to
1287 xorg 7.4 wants to configure its input devices via hald which does not
1288 yet work with USB2. If the keyboard/mouse does not work in xorg then
1290 Option "AllowEmptyInput" "off"
1291 to your ServerLayout section. This will cause X to use the configured
1292 kbd and mouse sections from your xorg.conf.
1295 The GENERIC kernels for all architectures now default to the new USB2
1296 stack. No kernel config options or code have been removed so if a
1297 problem arises please report it and optionally revert to the old USB
1298 stack. If you are loading USB kernel modules or have a custom kernel
1299 that includes GENERIC then ensure that usb names are also changed over,
1300 eg uftdi -> usb2_serial_ftdi.
1302 Older programs linked against the ports libusb 0.1 need to be
1303 redirected to the new stack's libusb20. /etc/libmap.conf can
1305 # Map old usb library to new one for usb2 stack
1306 libusb-0.1.so.8 libusb20.so.1
1309 All USB ethernet devices now attach as interfaces under the name ueN
1310 (eg. ue0). This is to provide a predictable name as vendors often
1311 change usb chipsets in a product without notice.
1314 The ichsmb(4) driver has been changed to require SMBus slave
1315 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1316 All of the other SMBus controller drivers require left-justified
1317 slave addresses, so this change makes all the drivers provide the
1321 INET6 statistics (struct ip6stat) was updated.
1322 netstat(1) needs to be recompiled.
1325 NTFS has been removed from GENERIC kernel on amd64 to match
1326 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1327 will load ntfs.ko module automatically when NTFS support is
1328 actually needed, unless ntfs.ko is not installed or security
1329 level prohibits loading kernel modules. If either is the case,
1330 "options NTFS" has to be added into kernel config.
1333 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1334 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1335 800061. User space tools that rely on the size of struct tcpcb in
1336 tcp_var.h (e.g. sockstat) need to be recompiled.
1339 ng_tty(4) module updated to match the new TTY subsystem.
1340 Due to API change, user-level applications must be updated.
1341 New API support added to mpd5 CVS and expected to be present
1342 in next mpd5.3 release.
1345 With __FreeBSD_version 800060 the makefs tool is part of
1346 the base system (it was a port).
1349 The afdata and ifnet locks have been changed from mutexes to
1350 rwlocks, network modules will need to be re-compiled.
1353 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1354 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1355 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1356 architecture and 40 bytes on 64-bit architecture. The userland
1357 applications "arp" and "ndp" have been updated accordingly.
1358 The output from "netstat -r" shows only routing entries and
1359 none of the L2 information.
1362 __FreeBSD_version 800057 marks the switchover from the
1363 binary ath hal to source code. Users must add the line:
1365 options AH_SUPPORT_AR5416
1367 to their kernel config files when specifying:
1371 The ath_hal module no longer exists; the code is now compiled
1372 together with the driver in the ath module. It is now
1373 possible to tailor chip support (i.e. reduce the set of chips
1374 and thereby the code size); consult ath_hal(4) for details.
1377 __FreeBSD_version 800054 adds memory barriers to
1378 <machine/atomic.h>, new interfaces to ifnet to facilitate
1379 multiple hardware transmit queues for cards that support
1380 them, and a lock-less ring-buffer implementation to
1381 enable drivers to more efficiently manage queueing of
1385 A new version of ZFS (version 13) has been merged to -HEAD.
1386 This version has zpool attribute "listsnapshots" off by
1387 default, which means "zfs list" does not show snapshots,
1388 and is the same as Solaris behavior.
1391 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1394 The uhci, ohci, ehci and slhci USB Host controller drivers have
1395 been put into separate modules. If you load the usb module
1396 separately through loader.conf you will need to load the
1397 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1398 controller add the following to loader.conf:
1404 The ABI used by the PMC toolset has changed. Please keep
1405 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1409 atapci kernel module now includes only generic PCI ATA
1410 driver. AHCI driver moved to ataahci kernel module.
1411 All vendor-specific code moved into separate kernel modules:
1412 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1413 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1414 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1415 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1418 The TTY subsystem of the kernel has been replaced by a new
1419 implementation, which provides better scalability and an
1420 improved driver model. Most common drivers have been migrated to
1421 the new TTY subsystem, while others have not. The following
1422 drivers have not yet been ported to the new TTY layer:
1425 cy, digi, rc, rp, sio
1431 ng_h4, ng_tty, ppp, sl, snp
1433 Adding these drivers to your kernel configuration file shall
1434 cause compilation to fail.
1437 ntpd has been upgraded to 4.2.4p5.
1440 OpenSSH has been upgraded to 5.1p1.
1442 For many years, FreeBSD's version of OpenSSH preferred DSA
1443 over RSA for host and user authentication keys. With this
1444 upgrade, we've switched to the vendor's default of RSA over
1445 DSA. This may cause upgraded clients to warn about unknown
1446 host keys even for previously known hosts. Users should
1447 follow the usual procedure for verifying host keys before
1448 accepting the RSA key.
1450 This can be circumvented by setting the "HostKeyAlgorithms"
1451 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1454 Please note that the sequence of keys offered for
1455 authentication has been changed as well. You may want to
1456 specify IdentityFile in a different order to revert this
1460 The sio(4) driver has been removed from the i386 and amd64
1461 kernel configuration files. This means uart(4) is now the
1462 default serial port driver on those platforms as well.
1464 To prevent collisions with the sio(4) driver, the uart(4) driver
1465 uses different names for its device nodes. This means the
1466 onboard serial port will now most likely be called "ttyu0"
1467 instead of "ttyd0". You may need to reconfigure applications to
1468 use the new device names.
1470 When using the serial port as a boot console, be sure to update
1471 /boot/device.hints and /etc/ttys before booting the new kernel.
1472 If you forget to do so, you can still manually specify the hints
1473 at the loader prompt:
1475 set hint.uart.0.at="isa"
1476 set hint.uart.0.port="0x3F8"
1477 set hint.uart.0.flags="0x10"
1478 set hint.uart.0.irq="4"
1482 The gpt(8) utility has been removed. Use gpart(8) to partition
1486 The version that Linuxulator emulates was changed from 2.4.2
1487 to 2.6.16. If you experience any problems with Linux binaries
1488 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1489 if it fixes the problem contact emulation mailing list.
1492 ISDN4BSD (I4B) was removed from the src tree. You may need to
1493 update a your kernel configuration and remove relevant entries.
1496 I have checked in code to support multiple routing tables.
1497 See the man pages setfib(1) and setfib(2).
1498 This is a hopefully backwards compatible version,
1499 but to make use of it you need to compile your kernel
1500 with options ROUTETABLES=2 (or more up to 16).
1503 The 802.11 wireless support was redone to enable multi-bss
1504 operation on devices that are capable. The underlying device
1505 is no longer used directly but instead wlanX devices are
1506 cloned with ifconfig. This requires changes to rc.conf files.
1507 For example, change:
1508 ifconfig_ath0="WPA DHCP"
1511 ifconfig_wlan0="WPA DHCP"
1512 see rc.conf(5) for more details. In addition, mergemaster of
1513 /etc/rc.d is highly recommended. Simultaneous update of userland
1514 and kernel wouldn't hurt either.
1516 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1517 modules were merged into the base wlan module. All references
1518 to these modules (e.g. in kernel config files) must be removed.
1521 psm(4) has gained write(2) support in native operation level.
1522 Arbitrary commands can be written to /dev/psm%d and status can
1523 be read back from it. Therefore, an application is responsible
1524 for status validation and error recovery. It is a no-op in
1525 other operation levels.
1528 Support for KSE threading has been removed from the kernel. To
1529 run legacy applications linked against KSE libmap.conf may
1530 be used. The following libmap.conf may be used to ensure
1531 compatibility with any prior release:
1533 libpthread.so.1 libthr.so.1
1534 libpthread.so.2 libthr.so.2
1535 libkse.so.3 libthr.so.3
1538 The layout of struct vmspace has changed. This affects libkvm
1539 and any executables that link against libkvm and use the
1540 kvm_getprocs() function. In particular, but not exclusively,
1541 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1542 The effects are minimal, but it's advisable to upgrade world
1546 The latest em driver no longer has support in it for the
1547 82575 adapter, this is now moved to the igb driver. The
1548 split was done to make new features that are incompatible
1549 with older hardware easier to do.
1552 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1553 likewise the kernel option is now GEOM_LINUX_LVM.
1556 The default NFS mount mode has changed from UDP to TCP for
1557 increased reliability. If you rely on (insecurely) NFS
1558 mounting across a firewall you may need to update your
1562 Belatedly note the addition of m_collapse for compacting
1566 The fts(3) structures have been changed to use adequate
1567 integer types for their members and so to be able to cope
1568 with huge file trees. The old fts(3) ABI is preserved
1569 through symbol versioning in libc, so third-party binaries
1570 using fts(3) should still work, although they will not take
1571 advantage of the extended types. At the same time, some
1572 third-party software might fail to build after this change
1573 due to unportable assumptions made in its source code about
1574 fts(3) structure members. Such software should be fixed
1575 by its vendor or, in the worst case, in the ports tree.
1576 FreeBSD_version 800015 marks this change for the unlikely
1577 case that a portable fix is impossible.
1580 To upgrade to -current after this date, you must be running
1581 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1582 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1585 The ADAPTIVE_GIANT kernel option has been retired because its
1586 functionality is the default now.
1589 The AT keyboard emulation of sunkbd(4) has been turned on
1590 by default. In order to make the special symbols of the Sun
1591 keyboards driven by sunkbd(4) work under X these now have
1592 to be configured the same way as Sun USB keyboards driven
1593 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1595 Option "XkbLayout" "us"
1596 Option "XkbRules" "xorg"
1597 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1600 It has been decided that it is desirable to provide ABI
1601 backwards compatibility to the FreeBSD 4/5/6 versions of the
1602 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1603 broken with the introduction of PCI domain support (see the
1604 20070930 entry). Unfortunately, this required the ABI of
1605 PCIOCGETCONF to be broken again in order to be able to
1606 provide backwards compatibility to the old version of that
1607 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1608 again. As for prominent ports this affects neither pciutils
1609 nor xorg-server this time, the hal port needs to be rebuilt
1613 The misnamed kthread_create() and friends have been renamed
1614 to kproc_create() etc. Many of the callers already
1615 used kproc_start()..
1616 I will return kthread_create() and friends in a while
1617 with implementations that actually create threads, not procs.
1618 Renaming corresponds with version 800002.
1627 Avoid using make -j when upgrading. While generally safe, there are
1628 sometimes problems using -j to upgrade. If your upgrade fails with
1629 -j, please try again without -j. From time to time in the past there
1630 have been problems using -j with buildworld and/or installworld. This
1631 is especially true when upgrading between "distant" versions (eg one
1632 that cross a major release boundary or several minor releases, or when
1633 several months have passed on the -current branch).
1635 Sometimes, obscure build problems are the result of environment
1636 poisoning. This can happen because the make utility reads its
1637 environment when searching for values for global variables. To run
1638 your build attempts in an "environmental clean room", prefix all make
1639 commands with 'env -i '. See the env(1) manual page for more details.
1641 When upgrading from one major version to another it is generally best
1642 to upgrade to the latest code in the currently installed branch first,
1643 then do an upgrade to the new branch. This is the best-tested upgrade
1644 path, and has the highest probability of being successful. Please try
1645 this approach before reporting problems with a major version upgrade.
1647 When upgrading a live system, having a root shell around before
1648 installing anything can help undo problems. Not having a root shell
1649 around can lead to problems if pam has changed too much from your
1650 starting point to allow continued authentication after the upgrade.
1654 When upgrading the boot ZFS pool to a new version, always follow
1657 1.) recompile and reinstall the ZFS boot loader and boot block
1658 (this is part of "make buildworld" and "make installworld")
1660 2.) update the ZFS boot block on your boot drive
1662 The following example updates the ZFS boot block on the first
1663 partition (freebsd-boot) of a GPT partitioned drive ad0:
1664 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1666 Non-boot pools do not need these updates.
1670 If you are updating from a prior version of FreeBSD (even one just
1671 a few days old), you should follow this procedure. It is the most
1672 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1674 make kernel-toolchain
1675 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1676 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1678 To test a kernel once
1679 ---------------------
1680 If you just want to boot a kernel once (because you are not sure
1681 if it works, or if you want to boot a known bad kernel to provide
1682 debugging information) run
1683 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1684 nextboot -k testkernel
1686 To just build a kernel when you know that it won't mess you up
1687 --------------------------------------------------------------
1688 This assumes you are already running a CURRENT system. Replace
1689 ${arch} with the architecture of your machine (e.g. "i386",
1690 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1692 cd src/sys/${arch}/conf
1693 config KERNEL_NAME_HERE
1694 cd ../compile/KERNEL_NAME_HERE
1699 If this fails, go to the "To build a kernel" section.
1701 To rebuild everything and install it on the current system.
1702 -----------------------------------------------------------
1703 # Note: sometimes if you are running current you gotta do more than
1704 # is listed here if you are upgrading from a really old current.
1706 <make sure you have good level 0 dumps>
1708 make kernel KERNCONF=YOUR_KERNEL_HERE
1710 <reboot in single user> [3]
1717 To cross-install current onto a separate partition
1718 --------------------------------------------------
1719 # In this approach we use a separate partition to hold
1720 # current's root, 'usr', and 'var' directories. A partition
1721 # holding "/", "/usr" and "/var" should be about 2GB in
1724 <make sure you have good level 0 dumps>
1727 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1728 <maybe newfs current's root partition>
1729 <mount current's root partition on directory ${CURRENT_ROOT}>
1730 make installworld DESTDIR=${CURRENT_ROOT}
1731 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1732 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1733 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1734 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1735 <reboot into current>
1736 <do a "native" rebuild/install as described in the previous section>
1737 <maybe install compatibility libraries from ports/misc/compat*>
1741 To upgrade in-place from stable to current
1742 ----------------------------------------------
1743 <make sure you have good level 0 dumps>
1745 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1747 <reboot in single user> [3]
1754 Make sure that you've read the UPDATING file to understand the
1755 tweaks to various things you need. At this point in the life
1756 cycle of current, things change often and you are on your own
1757 to cope. The defaults can also change, so please read ALL of
1758 the UPDATING entries.
1760 Also, if you are tracking -current, you must be subscribed to
1761 freebsd-current@freebsd.org. Make sure that before you update
1762 your sources that you have read and understood all the recent
1763 messages there. If in doubt, please track -stable which has
1764 much fewer pitfalls.
1766 [1] If you have third party modules, such as vmware, you
1767 should disable them at this point so they don't crash your
1770 [3] From the bootblocks, boot -s, and then do
1775 adjkerntz -i # if CMOS is wall time
1776 Also, when doing a major release upgrade, it is required that
1777 you boot into single user mode to do the installworld.
1779 [4] Note: This step is non-optional. Failure to do this step
1780 can result in a significant reduction in the functionality of the
1781 system. Attempting to do it by hand is not recommended and those
1782 that pursue this avenue should read this file carefully, as well
1783 as the archives of freebsd-current and freebsd-hackers mailing lists
1784 for potential gotchas. The -U option is also useful to consider.
1785 See mergemaster(8) for more information.
1787 [5] Usually this step is a noop. However, from time to time
1788 you may need to do this if you get unknown user in the following
1789 step. It never hurts to do it all the time. You may need to
1790 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1791 install) after the buildworld before this step if you last updated
1792 from current before 20130425 or from -stable before 20130430.
1794 [6] This only deletes old files and directories. Old libraries
1795 can be deleted by "make delete-old-libs", but you have to make
1796 sure that no program is using those libraries anymore.
1798 [8] In order to have a kernel that can run the 4.x binaries needed to
1799 do an installworld, you must include the COMPAT_FREEBSD4 option in
1800 your kernel. Failure to do so may leave you with a system that is
1801 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1802 required to run the 5.x binaries on more recent kernels. And so on
1803 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1805 Make sure that you merge any new devices from GENERIC since the
1806 last time you updated your kernel config file.
1808 [9] When checking out sources, you must include the -P flag to have
1809 cvs prune empty directories.
1811 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1812 "?=" instead of the "=" assignment operator, so that buildworld can
1813 override the CPUTYPE if it needs to.
1815 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1816 not on the command line, or in /etc/make.conf. buildworld will
1817 warn if it is improperly defined.
1820 This file contains a list, in reverse chronological order, of major
1821 breakages in tracking -current. It is not guaranteed to be a complete
1822 list of such breakages, and only contains entries since October 10, 2007.
1823 If you need to see UPDATING entries from before that date, you will need
1824 to fetch an UPDATING file from an older FreeBSD release.
1826 Copyright information:
1828 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1830 Redistribution, publication, translation and use, with or without
1831 modification, in full or in part, in any form or format of this
1832 document are permitted without further permission from the author.
1834 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1835 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1836 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1837 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1838 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1839 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1840 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1841 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1842 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1843 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1844 POSSIBILITY OF SUCH DAMAGE.
1846 Contact Warner Losh if you have any questions about your use of