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 stable/10, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
19 20150225: p18 FreeBSD-SA-15:04.igmp
21 FreeBSD-EN-15:02.openssl
22 FreeBSD-EN-15:03.freebsd-update
24 Fix integer overflow in IGMP protocol. [SA-15:04]
26 Fix vt(4) crash with improper ioctl parameters. [EN-15:01]
28 Updated base system OpenSSL to 1.0.1l. [EN-15:02]
30 Fix freebsd-update libraries update ordering issue. [EN-15:03]
32 20150127: p17 FreeBSD-SA-15:02.kmem
35 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
36 vulnerability. [SA-15:02]
38 Fix SCTP stream reset vulnerability. [SA-15:03]
40 20150114: p16 FreeBSD-SA-15:01.openssl
41 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
43 20141223: p15 FreeBSD-SA-14:31.ntp
44 FreeBSD-EN-14:13.freebsd-update
46 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
47 Fix directory deletion issue in freebsd-update. [EN-14:13]
49 20141217: p14 FreeBSD-SA-14:30.unbound
50 Fix unbound remote denial of service vulnerability.
52 20141210: p13 FreeBSD-SA-14:28.file
53 Fix multiple vulnerabilities in file(1) and libmagic(3).
55 20141104: p12 FreeBSD-SA-14:24.sshd
56 FreeBSD-SA-14:25.setlogin
60 Fix denial of service attack against sshd(8). [SA-14:24]
62 Fix kernel stack disclosure in setlogin(2) / getlogin(2).
65 Fix remote command execution in ftp(1). [SA-14:26]
67 Fix NFSv4 and ZFS cache consistency issue. [EN-14:12]
69 20141022: p11 FreeBSD-EN-14:10.tzdata
71 Time zone data file update. [EN-14:10]
73 20141021: p10 FreeBSD-SA-14:20.rtsold
74 FreeBSD-SA-14:21.routed
75 FreeBSD-SA-14:22.namei
76 FreeBSD-SA-14:23.openssl
78 Fix rtsold(8) remote buffer overflow vulnerability. [SA-14:20]
80 Fix routed(8) remote denial of service vulnerability. [SA-14:21]
82 Fix memory leak in sandboxed namei lookup. [SA-14:22]
84 Fix OpenSSL multiple vulnerabilities. [SA-14:23]
86 20140916: p9 FreeBSD-SA-14:19.tcp
87 Fix Denial of Service in TCP packet processing. [SA-14:19]
89 20140909: p8 FreeBSD-SA-14:18.openssl
90 Fix OpenSSL multiple vulnerabilities. [SA-14:18]
92 20140708: p7 FreeBSD-SA-14:17.kmem
93 Fix kernel memory disclosure in control messages and SCTP
94 notifications. [SA-14:17]
96 20140624: p6 FreeBSD-SA-14:15.iconv
100 Fix iconv(3) NULL pointer dereference and out-of-bounds array
103 Fix multiple vulnerabilities in file(1) and libmagic(3).
106 Worked around bug with PCID implementation. [EN-14:07]
108 20140605: p5 FreeBSD-SA-14:14.openssl
109 Fix OpenSSL multiple vulnerabilities. [SA-14:14]
111 20140603: p4 FreeBSD-SA-14:11.sendmail
113 FreeBSD-EN-14:06.exec
115 Fix sendmail improper close-on-exec flag handling. [SA-14:11]
117 Fix incorrect error handling in PAM policy parser. [SA-14:13]
119 Fix triple-fault when executing from a threaded process.
122 20140513: p3 FreeBSD-SA-14:10.openssl
123 FreeBSD-EN-14:05.ciss
125 Fix OpenSSL NULL pointer deference vulnerability. [SA-14:10]
127 Fix data corruption with ciss(4). [EN-14:05]
129 20140430: p2 FreeBSD-SA-14:07.devfs
131 FreeBSD-SA-14:09.openssl
133 Fix devfs rules not applied by default for jails. [SA-14:07]
135 Fix TCP reassembly vulnerability. [SA-14:08]
137 Fix OpenSSL use-after-free vulnerability. [SA-14:09]
139 20140408: p1 FreeBSD-SA-14:05.nfsserver
140 FreeBSD-SA-14:06.openssl
141 Fix deadlock in the NFS server. [SA-14:05]
143 Fix multiple vulnerabilities in OpenSSL. [SA-14:06]
146 The behavior of gss_pseudo_random() for the krb5 mechanism
147 has changed, for applications requesting a longer random string
148 than produced by the underlying enctype's pseudo-random() function.
149 In particular, the random string produced from a session key of
150 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
151 be different at the 17th octet and later, after this change.
152 The counter used in the PRF+ construction is now encoded as a
153 big-endian integer in accordance with RFC 4402.
156 The default version of mtree is nmtree which is obtained from
157 NetBSD. The output is generally the same, but may vary
158 slightly. If you found you need identical output adding
159 "-F freebsd9" to the command line should do the trick. For the
160 time being, the old mtree is available as fmtree.
163 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
164 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
165 1.1.4_8 and verify bsdyml not linked in, before running "make
167 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
169 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
172 The rc.d/jail script has been updated to support jail(8)
173 configuration file. The "jail_<jname>_*" rc.conf(5) variables
174 for per-jail configuration are automatically converted to
175 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
176 This is transparently backward compatible. See below about some
177 incompatibilities and rc.conf(5) manual page for more details.
179 These variables are now deprecated in favor of jail(8) configuration
180 file. One can use "rc.d/jail config <jname>" command to generate
181 a jail(8) configuration file in /var/run/jail.<jname>.conf without
182 running the jail(8) utility. The default pathname of the
183 configuration file is /etc/jail.conf and can be specified by
184 using $jail_conf or $jail_<jname>_conf variables.
186 Please note that jail_devfs_ruleset accepts an integer at
187 this moment. Please consider to rewrite the ruleset name
191 BIND has been removed from the base system. If all you need
192 is a local resolver, simply enable and start the local_unbound
193 service instead. Otherwise, several versions of BIND are
194 available in the ports tree. The dns/bind99 port is one example.
196 With this change, nslookup(1) and dig(1) are no longer in the base
197 system. Users should instead use host(1) and drill(1) which are
198 in the base system. Alternatively, nslookup and dig can
199 be obtained by installing the dns/bind-tools port.
202 With the addition of unbound(8), a new unbound user is now
203 required during installworld. "mergemaster -p" can be used to
204 add the user prior to installworld, as documented in the handbook.
207 OpenSSH is now built with DNSSEC support, and will by default
208 silently trust signed SSHFP records. This can be controlled with
209 the VerifyHostKeyDNS client configuration setting. DNSSEC support
210 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
213 The GNU Compiler Collection and C++ standard library (libstdc++)
214 are no longer built by default on platforms where clang is the system
215 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
219 The PROCDESC kernel option is now part of the GENERIC kernel
220 configuration and is required for the rwhod(8) to work.
221 If you are using custom kernel configuration, you should include
225 The API and ABI related to the Capsicum framework was modified
226 in backward incompatible way. The userland libraries and programs
227 have to be recompiled to work with the new kernel. This includes the
228 following libraries and programs, but the whole buildworld is
229 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
230 kdump, procstat, rwho, rwhod, uniq.
233 AES-NI intrinsic support has been added to gcc. The AES-NI module
234 has been updated to use this support. A new gcc is required to build
235 the aesni module on both i386 and amd64.
238 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
239 Thus "device padlock_rng" and "device rdrand_rng" should be
240 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
243 WITH_ICONV has been split into two feature sets. WITH_ICONV now
244 enables just the iconv* functionality and is now on by default.
245 WITH_LIBICONV_COMPAT enables the libiconv api and link time
246 compatability. Set WITHOUT_ICONV to build the old way.
247 If you have been using WITH_ICONV before, you will very likely
248 need to turn on WITH_LIBICONV_COMPAT.
251 INVARIANTS option now enables DEBUG for code with OpenSolaris and
252 Illumos origin, including ZFS. If you have INVARIANTS in your
253 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
255 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
256 locks if WITNESS option was set. Because that generated a lot of
257 witness(9) reports and all of them were believed to be false
258 positives, this is no longer done. New option OPENSOLARIS_WITNESS
259 can be used to achieve the previous behavior.
262 Timer values in IPv6 data structures now use time_uptime instead
263 of time_second. Although this is not a user-visible functional
264 change, userland utilities which directly use them---ndp(8),
265 rtadvd(8), and rtsold(8) in the base system---need to be updated
269 find -delete can now delete the pathnames given as arguments,
270 instead of only files found below them or if the pathname did
271 not contain any slashes. Formerly, the following error message
274 find: -delete: <path>: relative path potentially not safe
276 Deleting the pathnames given as arguments can be prevented
277 without error messages using -mindepth 1 or by changing
278 directory and passing "." as argument to find. This works in the
279 old as well as the new version of find.
282 Behavior of devfs rules path matching has been changed.
283 Pattern is now always matched against fully qualified devfs
284 path and slash characters must be explicitly matched by
285 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
286 subdirectories must be reviewed.
289 The default ARM ABI has changed to the ARM EABI. The old ABI is
290 incompatible with the ARM EABI and all programs and modules will
291 need to be rebuilt to work with a new kernel.
293 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
295 NOTE: Support for the old ABI will be removed in the future and
296 users are advised to upgrade.
299 pkg_install has been disconnected from the build if you really need it
300 you should add WITH_PKGTOOLS in your src.conf(5).
303 Most of network statistics structures were changed to be able
304 keep 64-bits counters. Thus all tools, that work with networking
305 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
308 Fix targets that run multiple make's to use && rather than ;
309 so that subsequent steps depend on success of previous.
311 NOTE: if building 'universe' with -j* on stable/8 or stable/9
312 it would be better to start the build using bmake, to avoid
313 overloading the machine.
316 Fix a bug that allowed a tracing process (e.g. gdb) to write
317 to a memory-mapped file in the traced process's address space
318 even if neither the traced process nor the tracing process had
319 write access to that file.
322 CVS has been removed from the base system. An exact copy
323 of the code is available from the devel/cvs port.
326 Some people report the following error after the switch to bmake:
328 make: illegal option -- J
329 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
331 *** [buildworld] Error code 2
333 this likely due to an old instance of make in
334 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
335 which src/Makefile will use that blindly, if it exists, so if
336 you see the above error:
338 rm -rf `make -V MAKEPATH`
343 Use bmake by default.
344 Whereas before one could choose to build with bmake via
345 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
346 make. The goal is to remove these knobs for 10-RELEASE.
348 It is worth noting that bmake (like gmake) treats the command
349 line as the unit of failure, rather than statements within the
350 command line. Thus '(cd some/where && dosomething)' is safer
351 than 'cd some/where; dosomething'. The '()' allows consistent
352 behavior in parallel build.
355 Fix a bug that allows NFS clients to issue READDIR on files.
358 The WITHOUT_IDEA option has been removed because
359 the IDEA patent expired.
362 The sysctl which controls TRIM support under ZFS has been renamed
363 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
367 The mergemaster command now uses the default MAKEOBJDIRPREFIX
368 rather than creating it's own in the temporary directory in
369 order allow access to bootstrapped versions of tools such as
370 install and mtree. When upgrading from version of FreeBSD where
371 the install command does not support -l, you will need to
372 install a new mergemaster command if mergemaster -p is required.
373 This can be accomplished with the command (cd src/usr.sbin/mergemaster
377 Legacy ATA stack, disabled and replaced by new CAM-based one since
378 FreeBSD 9.0, completely removed from the sources. Kernel modules
379 atadisk and atapi*, user-level tools atacontrol and burncd are
380 removed. Kernel option `options ATA_CAM` is now permanently enabled
384 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
385 and socketpair(2). Software, in particular Kerberos, may
386 automatically detect and use these during building. The resulting
387 binaries will not work on older kernels.
390 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
391 information, see the respective 20130304 entry).
394 Recent commits to callout(9) changed the size of struct callout,
395 so the KBI is probably heavily disturbed. Also, some functions
396 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
397 by macros. Every kernel module using it won't load, so rebuild
400 The ctl device has been re-enabled in GENERIC for i386 and amd64,
401 but does not initialize by default (because of the new CTL_DISABLE
402 option) to save memory. To re-enable it, remove the CTL_DISABLE
403 option from the kernel config file or set kern.cam.ctl.disable=0
404 in /boot/loader.conf.
407 The ctl device has been disabled in GENERIC for i386 and amd64.
408 This was done due to the extra memory being allocated at system
409 initialisation time by the ctl driver which was only used if
410 a CAM target device was created. This makes a FreeBSD system
411 unusable on 128MB or less of RAM.
414 A new compression method (lz4) has been merged to -HEAD. Please
415 refer to zpool-features(7) for more information.
417 Please refer to the "ZFS notes" section of this file for information
418 on upgrading boot ZFS pools.
421 A BSD-licensed patch(1) variant has been added and is installed
422 as bsdpatch, being the GNU version the default patch.
423 To inverse the logic and use the BSD-licensed one as default,
424 while having the GNU version installed as gnupatch, rebuild
425 and install world with the WITH_BSD_PATCH knob set.
428 Due to the use of the new -l option to install(1) during build
429 and install, you must take care not to directly set the INSTALL
430 make variable in your /etc/make.conf, /etc/src.conf, or on the
431 command line. If you wish to use the -C flag for all installs
432 you may be able to add INSTALL+=-C to /etc/make.conf or
436 The install(1) option -M has changed meaning and now takes an
437 argument that is a file or path to append logs to. In the
438 unlikely event that -M was the last option on the command line
439 and the command line contained at least two files and a target
440 directory the first file will have logs appended to it. The -M
441 option served little practical purpose in the last decade so its
442 use is expected to be extremely rare.
445 After switching to Clang as the default compiler some users of ZFS
446 on i386 systems started to experience stack overflow kernel panics.
447 Please consider using 'options KSTACK_PAGES=4' in such configurations.
450 GEOM_LABEL now mangles label names read from file system metadata.
451 Mangling affect labels containing spaces, non-printable characters,
452 '%' or '"'. Device names in /etc/fstab and other places may need to
456 By default, only the 10 most recent kernel dumps will be saved. To
457 restore the previous behaviour (no limit on the number of kernel dumps
458 stored in the dump directory) add the following line to /etc/rc.conf:
463 With the addition of auditdistd(8), a new auditdistd user is now
464 required during installworld. "mergemaster -p" can be used to
465 add the user prior to installworld, as documented in the handbook.
468 The sin6_scope_id member variable in struct sockaddr_in6 is now
469 filled by the kernel before passing the structure to the userland via
470 sysctl or routing socket. This means the KAME-specific embedded scope
471 id in sin6_addr.s6_addr[2] is always cleared in userland application.
472 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
473 __FreeBSD_version is bumped to 1000025.
476 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
477 This means that the world and kernel will be compiled with clang
478 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
479 and /usr/bin/cpp. To disable this behavior and revert to building
480 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
481 of current may need to bootstrap WITHOUT_CLANG first if the clang
482 build fails (its compatibility window doesn't extend to the 9 stable
486 The IPFIREWALL_FORWARD kernel option has been removed. Its
487 functionality now turned on by default.
490 The ZERO_COPY_SOCKET kernel option has been removed and
491 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
492 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
493 mechanism which is not safe and may result in kernel crashes.
494 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
495 driver supports disposeable external page sized mbuf storage.
496 Proper replacements for both zero-copy mechanisms are under
497 consideration and will eventually lead to complete removal
498 of the two kernel options.
501 The IPv4 network stack has been converted to network byte
502 order. The following modules need to be recompiled together
503 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
504 pf(4), ipfw(4), ng_ipfw(4), stf(4).
507 Support for non-MPSAFE filesystems was removed from VFS. The
508 VFS_VERSION was bumped, all filesystem modules shall be
512 All the non-MPSAFE filesystems have been disconnected from
513 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
514 portalfs, smbfs, xfs.
517 The interface cloning API and ABI has changed. The following
518 modules need to be recompiled together with kernel:
519 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
520 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
521 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
524 The sdhci driver was split in two parts: sdhci (generic SD Host
525 Controller logic) and sdhci_pci (actual hardware driver).
526 No kernel config modifications are required, but if you
527 load sdhc as a module you must switch to sdhci_pci instead.
530 Import the FUSE kernel and userland support into base system.
533 The GNU sort(1) program has been removed since the BSD-licensed
534 sort(1) has been the default for quite some time and no serious
535 problems have been reported. The corresponding WITH_GNU_SORT
539 The pfil(9) API/ABI for AF_INET family has been changed. Packet
540 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
544 The net80211(4) ABI has been changed to allow for improved driver
545 PS-POLL and power-save support. All wireless drivers need to be
546 recompiled to work with the new kernel.
549 The random(4) support for the VIA hardware random number
550 generator (`PADLOCK') is no longer enabled unconditionally.
551 Add the padlock_rng device in the custom kernel config if
552 needed. The GENERIC kernels on i386 and amd64 do include the
553 device, so the change only affects the custom kernel
557 The pf(4) packet filter ABI has been changed. pfctl(8) and
558 snmp_pf module need to be recompiled to work with new kernel.
561 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
562 to -HEAD. Pools that have empty_bpobj in active state can not be
563 imported read-write with ZFS implementations that do not support
564 this feature. For more information read the zpool-features(5)
568 The sparc64 ZFS loader has been changed to no longer try to auto-
569 detect ZFS providers based on diskN aliases but now requires these
570 to be explicitly listed in the OFW boot-device environment variable.
573 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
574 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
575 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
578 The following sysctls and tunables have been renamed for consistency
579 with other variables:
580 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
581 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
584 The sort utility has been replaced with BSD sort. For now, GNU sort
585 is also available as "gnusort" or the default can be set back to
586 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
587 installed as "bsdsort".
590 A new version of ZFS (pool version 5000) has been merged to -HEAD.
591 Starting with this version the old system of ZFS pool versioning
592 is superseded by "feature flags". This concept enables forward
593 compatibility against certain future changes in functionality of ZFS
594 pools. The first read-only compatible "feature flag" for ZFS pools
595 is named "com.delphix:async_destroy". For more information
596 read the new zpool-features(5) manual page.
597 Please refer to the "ZFS notes" section of this file for information
598 on upgrading boot ZFS pools.
601 The malloc(3) implementation embedded in libc now uses sources imported
602 as contrib/jemalloc. The most disruptive API change is to
603 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
604 delete it prior to installworld, and optionally re-create it using the
605 new format after rebooting. See malloc.conf(5) for details
606 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
610 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
611 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
612 now spelled mips. This is to aid compatibility with third-party
613 software that expects this naming scheme in uname(3). Little-endian
614 settings are unchanged. If you are updating a big-endian mips64 machine
615 from before this change, you may need to set MACHINE_ARCH=mips64 in
616 your environment before the new build system will recognize your machine.
619 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
623 Now unix domain sockets behave "as expected" on nullfs(5). Previously
624 nullfs(5) did not pass through all behaviours to the underlying layer,
625 as a result if we bound to a socket on the lower layer we could connect
626 only to the lower path; if we bound to the upper layer we could connect
627 only to the upper path. The new behavior is one can connect to both the
628 lower and the upper paths regardless what layer path one binds to.
631 The getifaddrs upgrade path broken with 20111215 has been restored.
632 If you have upgraded in between 20111215 and 20120209 you need to
633 recompile libc again with your kernel. You still need to recompile
634 world to be able to configure CARP but this restriction already
638 The set_rcvar() function has been removed from /etc/rc.subr. All
639 base and ports rc.d scripts have been updated, so if you have a
640 port installed with a script in /usr/local/etc/rc.d you can either
641 hand-edit the rcvar= line, or reinstall the port.
643 An easy way to handle the mass-update of /etc/rc.d:
644 rm /etc/rc.d/* && mergemaster -i
647 panic(9) now stops other CPUs in the SMP systems, disables interrupts
648 on the current CPU and prevents other threads from running.
649 This behavior can be reverted using the kern.stop_scheduler_on_panic
651 The new behavior can be incompatible with kern.sync_on_panic.
654 The carp(4) facility has been changed significantly. Configuration
655 of the CARP protocol via ifconfig(8) has changed, as well as format
656 of CARP events submitted to devd(8) has changed. See manual pages
657 for more information. The arpbalance feature of carp(4) is currently
658 not supported anymore.
660 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
661 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
662 need to be recompiled.
665 The acpi_wmi(4) status device /dev/wmistat has been renamed to
669 The option VFS_ALLOW_NONMPSAFE option has been added in order to
670 explicitely support non-MPSAFE filesystems.
671 It is on by default for all supported platform at this present
675 The broken amd(4) driver has been replaced with esp(4) in the amd64,
676 i386 and pc98 GENERIC kernel configuration files.
679 sysinstall has been removed
682 The stable/9 branch created in subversion. This corresponds to the
683 RELENG_9 branch in CVS.
686 This commit modifies vfs_register() so that it uses a hash
687 calculation to set vfc_typenum, which is enabled by default.
688 The first time a system is booted after this change, the
689 vfc_typenum values will change for all file systems. The
690 main effect of this is a change to the NFS server file handles
691 for file systems that use vfc_typenum in their fsid, such as ZFS.
692 It will, however, prevent vfc_typenum from changing when file
693 systems are loaded in a different order for subsequent reboots.
694 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
695 until you are ready to remount all NFS clients after a reboot.
698 Bump the shared library version numbers for libraries that
699 do not use symbol versioning, have changed the ABI compared
700 to stable/8 and which shared library version was not bumped.
701 Done as part of 9.0-RELEASE cycle.
704 During the merge of Capsicum features, the fget(9) KPI was modified.
705 This may require the rebuilding of out-of-tree device drivers --
706 issues have been reported specifically with the nVidia device driver.
707 __FreeBSD_version is bumped to 900041.
709 Also, there is a period between 20110811 and 20110814 where the
710 special devices /dev/{stdin,stdout,stderr} did not work correctly.
711 Building world from a kernel during that window may not work.
714 The packet filter (pf) code has been updated to OpenBSD 4.5.
715 You need to update userland tools to be in sync with kernel.
716 This update breaks backward compatibility with earlier pfsync(4)
717 versions. Care must be taken when updating redundant firewall setups.
720 The following sysctls and tunables are retired on x86 platforms:
722 machdep.hlt_logical_cpus
723 The following sysctl is retired:
724 machdep.hyperthreading_allowed
725 The sysctls were supposed to provide a way to dynamically offline and
726 online selected CPUs on x86 platforms, but the implementation has not
727 been reliable especially with SCHED_ULE scheduler.
728 machdep.hyperthreading_allowed tunable is still available to ignore
729 hyperthreading CPUs at OS level.
730 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
731 where X is an APIC ID of a CPU. Be advised, though, that disabling
732 CPUs in non-uniform fashion will result in non-uniform topology and
733 may lead to sub-optimal system performance with SCHED_ULE, which is
737 cpumask_t type is retired and cpuset_t is used in order to describe
741 Changes to ifconfig(8) for dynamic address family detection mandate
742 that you are running a kernel of 20110525 or later. Make sure to
743 follow the update procedure to boot a new kernel before installing
747 Support for sun4v architecture is officially dropped
750 Several KPI breaking changes have been committed to the mii(4) layer,
751 the PHY drivers and consequently some Ethernet drivers using mii(4).
752 This means that miibus.ko and the modules of the affected Ethernet
753 drivers need to be recompiled.
755 Note to kernel developers: Given that the OUI bit reversion problem
756 was fixed as part of these changes all mii(4) commits related to OUIs,
757 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
758 handling, no longer can be merged verbatim to stable/8 and previous
762 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
763 into their kernel configurations along with 'device pci'.
766 The default NFS client is now the new NFS client, so fstype "newnfs"
767 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
768 Although mounts via fstype "nfs" will usually work without userland
769 changes, it is recommended that the mount(8) and mount_nfs(8)
770 commands be rebuilt from sources and that a link to mount_nfs called
771 mount_oldnfs be created. The new client is compiled into the
772 kernel with "options NFSCL" and this is needed for diskless root
773 file systems. The GENERIC kernel configs have been changed to use
774 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
775 To use the regular/old client, you can "mount -t oldnfs ...". For
776 a diskless root file system, you must also include a line like:
778 vfs.root.mountfrom="oldnfs:"
780 in the boot/loader.conf on the root fs on the NFS server to make
781 a diskless root fs use the old client.
784 The GENERIC kernels for all architectures now default to the new
785 CAM-based ATA stack. It means that all legacy ATA drivers were
786 removed and replaced by respective CAM drivers. If you are using
787 ATA device names in /etc/fstab or other places, make sure to update
788 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
789 where 'Y's are the sequential numbers starting from zero for each type
790 in order of detection, unless configured otherwise with tunables,
791 see cam(4)). There will be symbolic links created in /dev/ to map
792 old adX devices to the respective adaY. They should provide basic
793 compatibility for file systems mounting in most cases, but they do
794 not support old user-level APIs and do not have respective providers
795 in GEOM. Consider using updated management tools with new device names.
797 It is possible to load devices ahci, ata, siis and mvs as modules,
798 but option ATA_CAM should remain in kernel configuration to make ata
799 module work as CAM driver supporting legacy ATA controllers. Device ata
800 still can be used in modular fashion (atacore + ...). Modules atadisk
801 and atapi* are not used and won't affect operation in ATA_CAM mode.
802 Note that to use CAM-based ATA kernel should include CAM devices
803 scbus, pass, da (or explicitly ada), cd and optionally others. All of
804 them are parts of the cam module.
806 ataraid(4) functionality is now supported by the RAID GEOM class.
807 To use it you can load geom_raid kernel module and use graid(8) tool
808 for management. Instead of /dev/arX device names, use /dev/raid/rX.
810 No kernel config options or code have been removed, so if a problem
811 arises, please report it and optionally revert to the old ATA stack.
812 In order to do it you can remove from the kernel config:
817 , and instead add back:
818 device atadisk # ATA disk drives
819 device ataraid # ATA RAID drives
820 device atapicd # ATAPI CDROM drives
821 device atapifd # ATAPI floppy drives
822 device atapist # ATAPI tape drives
825 The default NFS server has been changed to the new server, which
826 was referred to as the experimental server. If you need to switch
827 back to the old NFS server, you must now put the "-o" option on
828 both the mountd and nfsd commands. This can be done using the
829 mountd_flags and nfs_server_flags rc.conf variables until an
830 update to the rc scripts is committed, which is coming soon.
833 The GNU Objective-C runtime library (libobjc), and other Objective-C
834 related components have been removed from the base system. If you
835 require an Objective-C library, please use one of the available ports.
838 ath(4) has been split into bus- and device- modules. if_ath contains
839 the HAL, the TX rate control and the network device code. if_ath_pci
840 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
841 contains the AHB glue. Users need to load both if_ath_pci and if_ath
842 in order to use ath on everything else.
844 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
845 need to load if_ath and if_ath_pci for ath(4) operation.
848 As part of the replacement of sysinstall, the process of building
849 release media has changed significantly. For details, please re-read
850 release(7), which has been updated to reflect the new build process.
853 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
854 is the last available version under GPLv2. It brings a number of new
855 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
856 4.1 and SSE 4.2), better support for powerpc64, a number of new
857 directives, and lots of other small improvements. See the ChangeLog
858 file in contrib/binutils for the full details.
861 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
862 compliant, and will now use half of hash for authentication.
863 This will break interoperability with all stacks (including all
864 actual FreeBSD versions) who implement
865 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
867 The only workaround with such peers is to use another HMAC
868 algorithm for IPsec ("phase 2") authentication.
871 Remove the uio_yield prototype and symbol. This function has
872 been misnamed since it was introduced and should not be
873 globally exposed with this name. The equivalent functionality
874 is now available using kern_yield(curthread->td_user_pri).
875 The function remains undocumented.
878 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
879 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
880 for scalar sysctls is defined but disabled. Code that needs
881 UQUAD to pass the type checking that must compile on older
882 systems where the define is not present can check against
883 __FreeBSD_version >= 900030.
885 The system dialog(1) has been replaced with a new version previously
886 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
887 with the previous version, but the libdialog associated with it has
888 a largely incompatible API. As such, the original version of libdialog
889 will be kept temporarily as libodialog, until its base system consumers
890 are replaced or updated. Bump __FreeBSD_version to 900030.
893 If you are trying to run make universe on a -stable system, and you get
894 the following warning:
895 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
896 unknown. config(8) likely too old."
897 or something similar to it, then you must upgrade your -stable system
898 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
899 stable/8) or build the config from the latest stable/8 branch and
900 install it on your system.
902 Prior to this date, building a current universe on 8-stable system from
903 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
904 error in the first kernel build phase. A new config on those old
905 systems will fix that problem for older versions of -current.
908 The TCP stack has been modified to allow Khelp modules to interact with
909 it via helper hook points and store per-connection data in the TCP
910 control block. Bump __FreeBSD_version to 900029. User space tools that
911 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
915 Generic IEEE 802.3 annex 31B full duplex flow control support has been
916 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
917 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
918 to take advantage of it instead of using custom implementations. This
919 means that these drivers now no longer unconditionally advertise
920 support for flow control but only do so if flow control is a selected
921 media option. This was implemented in the generic support that way in
922 order to allow flow control to be switched on and off via ifconfig(8)
923 with the PHY specific default to typically off in order to protect
924 from unwanted effects. Consequently, if you used flow control with
925 one of the above mentioned drivers you now need to explicitly enable
927 ifconfig bge0 media auto mediaopt flowcontrol
929 Along with the above mentioned changes generic support for setting
930 1000baseT master mode also has been added and brgphy(4), ciphy(4),
931 e1000phy(4) as well as ip1000phy(4) have been converted to take
932 advantage of it. This means that these drivers now no longer take the
933 link0 parameter for selecting master mode but the master media option
934 has to be used instead, for example like in the following:
935 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
937 Selection of master mode now is also available with all other PHY
938 drivers supporting 1000baseT.
941 The TCP stack has received a significant update to add support for
942 modularised congestion control and generally improve the clarity of
943 congestion control decisions. Bump __FreeBSD_version to 900025. User
944 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
945 sockstat) need to be recompiled.
948 The man(1) utility has been replaced by a new version that no longer
949 uses /etc/manpath.config. Please consult man.conf(5) for how to
950 migrate local entries to the new format.
953 The copyright strings printed by login(1) and sshd(8) at the time of a
954 new connection have been removed to follow other operating systems and
958 A workaround for a fixed ld bug has been removed in kernel code,
959 so make sure that your system ld is built from sources after
960 revision 210245 from 2010-07-19 (r211583 if building head kernel
961 on stable/8, r211584 for stable/7; both from 2010-08-21).
962 A symptom of incorrect ld version is different addresses for
963 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
966 The $ipv6_prefer variable in rc.conf(5) has been split into
967 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
969 The $ip6addrctl_policy is a variable to choose a pre-defined
970 address selection policy set by ip6addrctl(8). A value
971 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
974 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
975 flag (see an entry of 20090926) is set on an interface with no
976 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
977 security reason. If you want IPv6 link-local address on all
978 interfaces by default, set this to "YES".
980 The old ipv6_prefer="YES" is equivalent to
981 ipv6_activate_all_interfaces="YES" and
982 ip6addrctl_policy="ipv6_prefer".
985 DTrace has grown support for userland tracing. Due to this, DTrace is
986 now i386 and amd64 only.
987 dtruss(1) is now installed by default on those systems and a new
988 kernel module is needed for userland tracing: fasttrap.
989 No changes to your kernel config file are necessary to enable
990 userland tracing, but you might consider adding 'STRIP=' and
991 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
992 to have informative userland stack traces in DTrace (ustack).
995 The acpi_aiboost(4) driver has been removed in favor of the new
996 aibs(4) driver. You should update your kernel configuration file.
999 BSD grep has been imported to the base system and it is built by
1000 default. It is completely BSD licensed, highly GNU-compatible, uses
1001 less memory than its GNU counterpart and has a small codebase.
1002 However, it is slower than its GNU counterpart, which is mostly
1003 noticeable for larger searches, for smaller ones it is measurable
1004 but not significant. The reason is complex, the most important factor
1005 is that we lack a modern and efficient regex library and GNU
1006 overcomes this by optimizing the searches internally. Future work
1007 on improving the regex performance is planned, for the meantime,
1008 users that need better performance, can build GNU grep instead by
1009 setting the WITH_GNU_GREP knob.
1012 Due to the import of powerpc64 support, all existing powerpc kernel
1013 configuration files must be updated with a machine directive like this:
1014 machine powerpc powerpc
1016 In addition, an updated config(8) is required to build powerpc kernels
1020 A new version of ZFS (version 15) has been merged to -HEAD.
1021 This version uses a python library for the following subcommands:
1022 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1023 For full functionality of these commands the following port must
1024 be installed: sysutils/py-zfs
1027 'vm_page's are now hashed by physical address to an array of mutexes.
1028 Currently this is only used to serialize access to hold_count. Over
1029 time the page queue mutex will be peeled away. This changes the size
1030 of pmap on every architecture. And requires all callers of vm_page_hold
1031 and vm_page_unhold to be updated.
1034 WITH_CTF can now be specified in src.conf (not recommended, there
1035 are some problems with static executables), make.conf (would also
1036 affect ports which do not use GNU make and do not override the
1037 compile targets) or in the kernel config (via "makeoptions
1039 When WITH_CTF was specified there before this was silently ignored,
1040 so make sure that WITH_CTF is not used in places which could lead
1041 to unwanted behavior.
1044 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1045 to allow 32-bit compatibility on non-x86 platforms. All kernel
1046 configurations on amd64 and ia64 platforms using these options must
1047 be modified accordingly.
1050 The utmp user accounting database has been replaced with utmpx,
1051 the user accounting interface standardized by POSIX.
1052 Unfortunately the semantics of utmp and utmpx don't match,
1053 making it practically impossible to support both interfaces.
1054 The user accounting database is used by tools like finger(1),
1055 last(1), talk(1), w(1) and ac(8).
1057 All applications in the base system use utmpx. This means only
1058 local binaries (e.g. from the ports tree) may still use these
1059 utmp database files. These applications must be rebuilt to make
1062 After the system has been upgraded, it is safe to remove the old
1063 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1064 assuming their contents is of no importance anymore. Old wtmp
1065 databases can only be used by last(1) and ac(8) after they have
1066 been converted to the new format using wtmpcvt(1).
1069 Introduce the kernel thread "deadlock resolver" (which can be enabled
1070 via the DEADLKRES option, see NOTES for more details) and the
1071 sleepq_type() function for sleepqueues.
1074 The rc.firewall and rc.firewall6 were unified, and
1075 rc.firewall6 and rc.d/ip6fw were removed.
1076 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1077 variables are obsoleted. Instead, the following new rc
1078 variables are added to rc.d/ipfw:
1080 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1081 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1082 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1084 The meanings correspond to the relevant IPv4 variables.
1090 The default terminal emulation for syscons(4) has been changed
1091 from cons25 to xterm on all platforms except pc98. This means
1092 that the /etc/ttys file needs to be updated to ensure correct
1093 operation of applications on the console.
1095 The terminal emulation style can be toggled per window by using
1096 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1097 options can be used to change the compile-time default back to
1100 To prevent graphical artifacts, make sure the TERM environment
1101 variable is set to match the terminal emulation that is being
1102 performed by syscons(4).
1105 The layout of the structure ieee80211req_scan_result has changed.
1106 Applications that require wireless scan results (e.g. ifconfig(8))
1107 from net80211 need to be recompiled.
1109 Applications such as wpa_supplicant(8) may require a full world
1110 build without using NO_CLEAN in order to get synchronized with the
1114 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1115 There's one kernel module for each firmware. Adding "device iwnfw"
1116 to the kernel configuration file means including all three firmware
1117 images inside the kernel. If you want to include just the one for
1118 your wireless card, use the devices iwn4965fw, iwn5000fw or
1122 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1123 into rc.d/netif. The changes are the following:
1125 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1126 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1127 Note that both variables need the "inet6" keyword at the head.
1129 Do not set $ipv6_network_interfaces manually if you do not
1130 understand what you are doing. It is not needed in most cases.
1132 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1135 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1136 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1138 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1139 all configured interfaces have "inet6 accept_rtadv" in the
1140 $ifconfig_IF_ipv6. These are for backward compatibility.
1142 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1143 functionality of interfaces with no corresponding
1144 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1145 and the default address selection policy of ip6addrctl(8)
1146 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1147 Note that if you want to configure IPv6 functionality on the
1148 disabled interfaces after boot, first you need to clear the flag by
1149 using ifconfig(8) like:
1151 ifconfig em0 inet6 -ifdisabled
1153 If YES, the default address selection policy is set as
1156 The default value of $ipv6_prefer is NO.
1158 4. If your system need to receive Router Advertisement messages,
1159 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1160 scripts automatically invoke rtsol(8) when the interface becomes
1161 UP. The Router Advertisement messages are used for SLAAC
1162 (State-Less Address AutoConfiguration).
1165 802.11s D3.03 support was committed. This is incompatible with the
1166 previous code, which was based on D3.0.
1169 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1170 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1171 control whether accepting Router Advertisement messages or not.
1172 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1173 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1174 The ifconfig(8) utility now supports these flags.
1177 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1178 mount(8) and -a option for df(1) to see them.
1181 The old tunable hw.bus.devctl_disable has been superseded by
1182 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1183 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1187 Remove the option STOP_NMI. The default action is now to use NMI only
1188 for KDB via the newly introduced function stop_cpus_hard() and
1189 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1192 The stable/8 branch created in subversion. This corresponds to the
1193 RELENG_8 branch in CVS.
1196 Bump the shared library version numbers for all libraries that do not
1197 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1198 __FreeBSD_version to 800105.
1201 Due to changes in the implementation of virtual network stack support,
1202 all network-related kernel modules must be recompiled. As this change
1203 breaks the ABI, bump __FreeBSD_version to 800104.
1206 The TOE interface to the TCP syncache has been modified to remove
1207 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1208 The cxgb driver is the only TOE consumer affected by this change, and
1209 needs to be recompiled along with the kernel. As this change breaks
1210 the ABI, bump __FreeBSD_version to 800103.
1213 Padding has been added to struct tcpcb, sackhint and tcpstat in
1214 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1215 maintaining the ABI. However, this change breaks the ABI, so bump
1216 __FreeBSD_version to 800102. User space tools that rely on the size of
1217 any of these structs (e.g. sockstat) need to be recompiled.
1220 The NFS_LEGACYRPC option has been removed along with the old kernel
1221 RPC implementation that this option selected. Kernel configurations
1222 may need to be adjusted.
1225 The network interface device nodes at /dev/net/<interface> have been
1226 removed. All ioctl operations can be performed the normal way using
1227 routing sockets. The kqueue functionality can generally be replaced
1228 with routing sockets.
1231 The documentation from the FreeBSD Documentation Project (Handbook,
1232 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1233 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1236 The ABI of various structures related to the SYSV IPC API have been
1237 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1238 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1242 Layout of struct vnet has changed as routing related variables were
1243 moved to their own Vimage module. Modules need to be recompiled. Bump
1244 __FreeBSD_version to 800099.
1247 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1248 respectively. As long as no more than 16 groups per process are used,
1249 no changes should be visible. When more than 16 groups are used, old
1250 binaries may fail if they call getgroups() or getgrouplist() with
1251 statically sized storage. Recompiling will work around this, but
1252 applications should be modified to use dynamically allocated storage
1253 for group arrays as POSIX.1-2008 does not cap an implementation's
1254 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1256 NFS and portalfs mounts may also be affected as the list of groups is
1257 truncated to 16. Users of NFS who use more than 16 groups, should
1258 take care that negative group permissions are not used on the exported
1259 file systems as they will not be reliable unless a GSSAPI based
1260 authentication method is used.
1263 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1264 option compiles in the support for adaptive spinning for lockmgrs
1265 which want to enable it. The lockinit() function now accepts the flag
1266 LK_ADAPTIVE in order to make the lock object subject to adaptive
1267 spinning when both held in write and read mode.
1270 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1271 changed. User applications that use this ioctl need to be rebuilt.
1274 The layout of struct thread has changed. Kernel and modules need to
1278 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1279 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1282 window(1) has been removed from the base system. It can now be
1283 installed from ports. The port is called misc/window.
1286 The way we are storing and accessing `routing table' entries has
1287 changed. Programs reading the FIB, like netstat, need to be
1291 A new netisr implementation has been added for FreeBSD 8. Network
1292 file system modules, such as igmp, ipdivert, and others, should be
1294 Bump __FreeBSD_version to 800096.
1297 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1301 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1302 Bump __FreeBSD_version to 800094.
1305 Add mnt_xflag field to 'struct mount'. File system modules need to be
1307 Bump __FreeBSD_version to 800093.
1310 The compiling option ADAPTIVE_SX has been retired while it has been
1311 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1312 The KPI for sx_init_flags() changes as accepting flags:
1313 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1314 been introduced in order to handle the reversed logic.
1315 Bump __FreeBSD_version to 800092.
1318 Add support for hierarchical jails. Remove global securelevel.
1319 Bump __FreeBSD_version to 800091.
1322 The layout of struct vnet_net has changed, therefore modules
1324 Bump __FreeBSD_version to 800090.
1327 The newly imported zic(8) produces a new format in the output. Please
1328 run tzsetup(8) to install the newly created data to /etc/localtime.
1331 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1332 hw.usb.* and is now consistent again with previous releases.
1335 802.11 monitor mode support was revised and driver api's were changed.
1336 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1337 of DLT_IEEE802_11. No user-visible data structures were changed but
1338 applications that use DLT_IEEE802_11 may require changes.
1339 Bump __FreeBSD_version to 800088.
1342 The layout of the following structs has changed: sysctl_oid,
1343 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1344 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1345 panics may be experienced. World rebuild is required for
1346 correctly checking networking state from userland.
1347 Bump __FreeBSD_version to 800085.
1350 MLDv2 and Source-Specific Multicast (SSM) have been merged
1351 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1352 The implementation of SSM within FreeBSD's IPv6 stack closely
1353 follows the IPv4 implementation.
1355 For kernel developers:
1357 * The most important changes are that the ip6_output() and
1358 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1359 and this lock has been downgraded to a non-recursive mutex.
1361 * As with the changes to the IPv4 stack to support SSM, filtering
1362 of inbound multicast traffic must now be performed by transport
1363 protocols within the IPv6 stack. This does not apply to TCP and
1364 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1366 * The KPIs used by IPv6 multicast are similar to those used by
1367 the IPv4 stack, with the following differences:
1368 * im6o_mc_filter() is analogous to imo_multicast_filter().
1369 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1370 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1371 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1372 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1373 for MLDv1 have an additional 'timer' argument which is used to
1374 jitter the initial membership report for the solicited-node
1375 multicast membership on-link.
1376 * This is not strictly needed for MLDv2, which already jitters
1377 its report transmissions. However, the 'timer' argument is
1378 preserved in case MLDv1 is active on the interface.
1380 * The KAME linked-list based IPv6 membership implementation has
1381 been refactored to use a vector similar to that used by the IPv4
1383 Code which maintains a list of its own multicast memberships
1384 internally, e.g. carp, has been updated to reflect the new
1387 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1388 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1389 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1390 implementation constraint which needs to be addressed in HEAD.
1392 For application developers:
1394 * The changes are broadly similar to those made for the IPv4
1397 * The use of IPv4 and IPv6 multicast socket options on the same
1398 socket, using mapped addresses, HAS NOT been tested or supported.
1400 * There are a number of issues with the implementation of various
1401 IPv6 multicast APIs which need to be resolved in the API surface
1402 before the implementation is fully compatible with KAME userland
1403 use, and these are mostly to do with interface index treatment.
1405 * The literature available discusses the use of either the delta / ASM
1406 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1407 using setsourcefilter(3)/getsourcefilter(3). For more information
1408 please refer to RFC 3768, 'Socket Interface Extensions for
1409 Multicast Source Filters'.
1411 * Applications which use the published RFC 3678 APIs should be fine.
1413 For systems administrators:
1415 * The mtest(8) utility has been refactored to support IPv6, in
1416 addition to IPv4. Interface addresses are no longer accepted
1417 as arguments, their names must be used instead. The utility
1418 will map the interface name to its first IPv4 address as
1419 returned by getifaddrs(3).
1421 * The ifmcstat(8) utility has also been updated to print the MLDv2
1422 endpoint state and source filter lists via sysctl(3).
1424 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1425 loopback of IPv6 multicast datagrams by default; it defaults to 1
1426 to preserve the existing behaviour. Disabling multicast loopback is
1427 recommended for optimal system performance.
1429 * The IPv6 MROUTING code has been changed to examine this sysctl
1430 instead of attempting to perform a group lookup before looping
1431 back forwarded datagrams.
1433 Bump __FreeBSD_version to 800084.
1436 Implement low-level Bluetooth HCI API.
1437 Bump __FreeBSD_version to 800083.
1440 The layout of struct malloc_type, used by modules to register new
1441 memory allocation types, has changed. Most modules will need to
1442 be rebuilt or panics may be experienced.
1443 Bump __FreeBSD_version to 800081.
1446 Anticipate overflowing inp_flags - add inp_flags2.
1447 This changes most offsets in inpcb, so checking v4 connection
1448 state will require a world rebuild.
1449 Bump __FreeBSD_version to 800080.
1452 Add an llentry to struct route and struct route_in6. Modules
1453 embedding a struct route will need to be recompiled.
1454 Bump __FreeBSD_version to 800079.
1457 The size of rt_metrics_lite and by extension rtentry has changed.
1458 Networking administration apps will need to be recompiled.
1459 The route command now supports show as an alias for get, weighting
1460 of routes, sticky and nostick flags to alter the behavior of stateful
1462 Bump __FreeBSD_version to 800078.
1465 Do not use Giant for kbdmux(4) locking. This is wrong and
1466 apparently causing more problems than it solves. This will
1467 re-open the issue where interrupt handlers may race with
1468 kbdmux(4) in polling mode. Typical symptoms include (but
1469 not limited to) duplicated and/or missing characters when
1470 low level console functions (such as gets) are used while
1471 interrupts are enabled (for example geli password prompt,
1472 mountroot prompt etc.). Disabling kbdmux(4) may help.
1475 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1476 kernel modules referencing any of the above need to be recompiled.
1477 Bump __FreeBSD_version to 800075.
1480 GEOM_PART has become the default partition slicer for storage devices,
1481 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1482 introduces some changes:
1484 MSDOS/EBR: the devices created from MSDOS extended partition entries
1485 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1486 to devices with offset-based names. fstabs may need to be modified.
1488 BSD: the "geometry does not match label" warning is harmless in most
1489 cases but it points to problems in file system misalignment with
1490 disk geometry. The "c" partition is now implicit, covers the whole
1491 top-level drive and cannot be (mis)used by users.
1493 General: Kernel dumps are now not allowed to be written to devices
1494 whose partition types indicate they are meant to be used for file
1495 systems (or, in case of MSDOS partitions, as something else than
1498 Most of these changes date approximately from 200812.
1501 The uscanner(4) driver has been removed from the kernel. This follows
1502 Linux removing theirs in 2.6 and making libusb the default interface
1503 (supported by sane).
1506 The multicast forwarding code has been cleaned up. netstat(1)
1507 only relies on KVM now for printing bandwidth upcall meters.
1508 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1509 ip6_mroute_mod respectively. The config(5) options for statically
1510 compiling this code remain the same, i.e. 'options MROUTING'.
1513 Support for the IFF_NEEDSGIANT network interface flag has been
1514 removed, which means that non-MPSAFE network device drivers are no
1515 longer supported. In particular, if_ar, if_sr, and network device
1516 drivers from the old (legacy) USB stack can no longer be built or
1520 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1521 a bunch of new language catalog files have also been added.
1522 This means that some common libc messages are now localized and
1523 they depend on the LC_MESSAGES environmental variable.
1526 The k8temp(4) driver has been renamed to amdtemp(4) since
1527 support for Family 10 and Family 11 CPU families was added.
1530 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1531 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1533 For kernel developers, the most important changes are that the
1534 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1535 and this lock has been downgraded to a non-recursive mutex.
1537 Transport protocols (UDP, Raw IP) are now responsible for filtering
1538 inbound multicast traffic according to group membership and source
1539 filters. The imo_multicast_filter() KPI exists for this purpose.
1540 Transports which do not use multicast (SCTP, TCP) already reject
1541 multicast by default. Forwarding and receive performance may improve
1542 as a mutex acquisition is no longer needed in the ip_input()
1543 low-level input path. in_addmulti() and in_delmulti() are shimmed
1544 to new KPIs which exist to support SSM in-kernel.
1546 For application developers, it is recommended that loopback of
1547 multicast datagrams be disabled for best performance, as this
1548 will still cause the lock to be taken for each looped-back
1549 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1550 be tuned to 0 to disable loopback by default; it defaults to 1
1551 to preserve the existing behaviour.
1553 For systems administrators, to obtain best performance with
1554 multicast reception and multiple groups, it is always recommended
1555 that a card with a suitably precise hash filter is used. Hash
1556 collisions will still result in the lock being taken within the
1557 transport protocol input path to check group membership.
1559 If deploying FreeBSD in an environment with IGMP snooping switches,
1560 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1561 enabled; this forces 224.0.0.0/24 group membership to be announced
1564 The size of 'struct igmpstat' has changed; netstat needs to be
1565 recompiled to reflect this.
1566 Bump __FreeBSD_version to 800070.
1569 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1570 updated to use it. This requires a buildworld/installworld in order to
1571 update the library and dependencies (usbconfig, etc). Its advisable to
1572 rebuild all ports which uses libusb. More specific directions are given
1573 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1574 libusb are no longer required and can be removed.
1577 A workaround is committed to allow the creation of System V shared
1578 memory segment of size > 2 GB on the 64-bit architectures.
1579 Due to a limitation of the existing ABI, the shm_segsz member
1580 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1581 wrong for large segments. Note that limits must be explicitly
1582 raised to allow such segments to be created.
1585 The layout of struct ifnet has changed, requiring a rebuild of all
1586 network device driver modules.
1589 The /dev handling for the new USB stack has changed, a
1590 buildworld/installworld is required for libusb20.
1593 The new USB2 stack has now been permanently moved in and all kernel and
1594 module names reverted to their previous values (eg, usb, ehci, ohci,
1595 ums, ...). The old usb stack can be compiled in by prefixing the name
1596 with the letter 'o', the old usb modules have been removed.
1597 Updating entry 20090216 for xorg and 20090215 for libmap may still
1601 The rc.conf(5) option if_up_delay has been renamed to
1602 defaultroute_delay to better reflect its purpose. If you have
1603 customized this setting in /etc/rc.conf you need to update it to
1607 xorg 7.4 wants to configure its input devices via hald which does not
1608 yet work with USB2. If the keyboard/mouse does not work in xorg then
1610 Option "AllowEmptyInput" "off"
1611 to your ServerLayout section. This will cause X to use the configured
1612 kbd and mouse sections from your xorg.conf.
1615 The GENERIC kernels for all architectures now default to the new USB2
1616 stack. No kernel config options or code have been removed so if a
1617 problem arises please report it and optionally revert to the old USB
1618 stack. If you are loading USB kernel modules or have a custom kernel
1619 that includes GENERIC then ensure that usb names are also changed over,
1620 eg uftdi -> usb2_serial_ftdi.
1622 Older programs linked against the ports libusb 0.1 need to be
1623 redirected to the new stack's libusb20. /etc/libmap.conf can
1625 # Map old usb library to new one for usb2 stack
1626 libusb-0.1.so.8 libusb20.so.1
1629 All USB ethernet devices now attach as interfaces under the name ueN
1630 (eg. ue0). This is to provide a predictable name as vendors often
1631 change usb chipsets in a product without notice.
1634 The ichsmb(4) driver has been changed to require SMBus slave
1635 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1636 All of the other SMBus controller drivers require left-justified
1637 slave addresses, so this change makes all the drivers provide the
1641 INET6 statistics (struct ip6stat) was updated.
1642 netstat(1) needs to be recompiled.
1645 NTFS has been removed from GENERIC kernel on amd64 to match
1646 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1647 will load ntfs.ko module automatically when NTFS support is
1648 actually needed, unless ntfs.ko is not installed or security
1649 level prohibits loading kernel modules. If either is the case,
1650 "options NTFS" has to be added into kernel config.
1653 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1654 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1655 800061. User space tools that rely on the size of struct tcpcb in
1656 tcp_var.h (e.g. sockstat) need to be recompiled.
1659 ng_tty(4) module updated to match the new TTY subsystem.
1660 Due to API change, user-level applications must be updated.
1661 New API support added to mpd5 CVS and expected to be present
1662 in next mpd5.3 release.
1665 With __FreeBSD_version 800060 the makefs tool is part of
1666 the base system (it was a port).
1669 The afdata and ifnet locks have been changed from mutexes to
1670 rwlocks, network modules will need to be re-compiled.
1673 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1674 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1675 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1676 architecture and 40 bytes on 64-bit architecture. The userland
1677 applications "arp" and "ndp" have been updated accordingly.
1678 The output from "netstat -r" shows only routing entries and
1679 none of the L2 information.
1682 __FreeBSD_version 800057 marks the switchover from the
1683 binary ath hal to source code. Users must add the line:
1685 options AH_SUPPORT_AR5416
1687 to their kernel config files when specifying:
1691 The ath_hal module no longer exists; the code is now compiled
1692 together with the driver in the ath module. It is now
1693 possible to tailor chip support (i.e. reduce the set of chips
1694 and thereby the code size); consult ath_hal(4) for details.
1697 __FreeBSD_version 800054 adds memory barriers to
1698 <machine/atomic.h>, new interfaces to ifnet to facilitate
1699 multiple hardware transmit queues for cards that support
1700 them, and a lock-less ring-buffer implementation to
1701 enable drivers to more efficiently manage queueing of
1705 A new version of ZFS (version 13) has been merged to -HEAD.
1706 This version has zpool attribute "listsnapshots" off by
1707 default, which means "zfs list" does not show snapshots,
1708 and is the same as Solaris behavior.
1711 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1714 The uhci, ohci, ehci and slhci USB Host controller drivers have
1715 been put into separate modules. If you load the usb module
1716 separately through loader.conf you will need to load the
1717 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1718 controller add the following to loader.conf:
1724 The ABI used by the PMC toolset has changed. Please keep
1725 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1729 atapci kernel module now includes only generic PCI ATA
1730 driver. AHCI driver moved to ataahci kernel module.
1731 All vendor-specific code moved into separate kernel modules:
1732 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1733 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1734 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1735 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1738 The TTY subsystem of the kernel has been replaced by a new
1739 implementation, which provides better scalability and an
1740 improved driver model. Most common drivers have been migrated to
1741 the new TTY subsystem, while others have not. The following
1742 drivers have not yet been ported to the new TTY layer:
1745 cy, digi, rc, rp, sio
1751 ng_h4, ng_tty, ppp, sl, snp
1753 Adding these drivers to your kernel configuration file shall
1754 cause compilation to fail.
1757 ntpd has been upgraded to 4.2.4p5.
1760 OpenSSH has been upgraded to 5.1p1.
1762 For many years, FreeBSD's version of OpenSSH preferred DSA
1763 over RSA for host and user authentication keys. With this
1764 upgrade, we've switched to the vendor's default of RSA over
1765 DSA. This may cause upgraded clients to warn about unknown
1766 host keys even for previously known hosts. Users should
1767 follow the usual procedure for verifying host keys before
1768 accepting the RSA key.
1770 This can be circumvented by setting the "HostKeyAlgorithms"
1771 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1774 Please note that the sequence of keys offered for
1775 authentication has been changed as well. You may want to
1776 specify IdentityFile in a different order to revert this
1780 The sio(4) driver has been removed from the i386 and amd64
1781 kernel configuration files. This means uart(4) is now the
1782 default serial port driver on those platforms as well.
1784 To prevent collisions with the sio(4) driver, the uart(4) driver
1785 uses different names for its device nodes. This means the
1786 onboard serial port will now most likely be called "ttyu0"
1787 instead of "ttyd0". You may need to reconfigure applications to
1788 use the new device names.
1790 When using the serial port as a boot console, be sure to update
1791 /boot/device.hints and /etc/ttys before booting the new kernel.
1792 If you forget to do so, you can still manually specify the hints
1793 at the loader prompt:
1795 set hint.uart.0.at="isa"
1796 set hint.uart.0.port="0x3F8"
1797 set hint.uart.0.flags="0x10"
1798 set hint.uart.0.irq="4"
1802 The gpt(8) utility has been removed. Use gpart(8) to partition
1806 The version that Linuxulator emulates was changed from 2.4.2
1807 to 2.6.16. If you experience any problems with Linux binaries
1808 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1809 if it fixes the problem contact emulation mailing list.
1812 ISDN4BSD (I4B) was removed from the src tree. You may need to
1813 update a your kernel configuration and remove relevant entries.
1816 I have checked in code to support multiple routing tables.
1817 See the man pages setfib(1) and setfib(2).
1818 This is a hopefully backwards compatible version,
1819 but to make use of it you need to compile your kernel
1820 with options ROUTETABLES=2 (or more up to 16).
1823 The 802.11 wireless support was redone to enable multi-bss
1824 operation on devices that are capable. The underlying device
1825 is no longer used directly but instead wlanX devices are
1826 cloned with ifconfig. This requires changes to rc.conf files.
1827 For example, change:
1828 ifconfig_ath0="WPA DHCP"
1831 ifconfig_wlan0="WPA DHCP"
1832 see rc.conf(5) for more details. In addition, mergemaster of
1833 /etc/rc.d is highly recommended. Simultaneous update of userland
1834 and kernel wouldn't hurt either.
1836 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1837 modules were merged into the base wlan module. All references
1838 to these modules (e.g. in kernel config files) must be removed.
1841 psm(4) has gained write(2) support in native operation level.
1842 Arbitrary commands can be written to /dev/psm%d and status can
1843 be read back from it. Therefore, an application is responsible
1844 for status validation and error recovery. It is a no-op in
1845 other operation levels.
1848 Support for KSE threading has been removed from the kernel. To
1849 run legacy applications linked against KSE libmap.conf may
1850 be used. The following libmap.conf may be used to ensure
1851 compatibility with any prior release:
1853 libpthread.so.1 libthr.so.1
1854 libpthread.so.2 libthr.so.2
1855 libkse.so.3 libthr.so.3
1858 The layout of struct vmspace has changed. This affects libkvm
1859 and any executables that link against libkvm and use the
1860 kvm_getprocs() function. In particular, but not exclusively,
1861 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1862 The effects are minimal, but it's advisable to upgrade world
1866 The latest em driver no longer has support in it for the
1867 82575 adapter, this is now moved to the igb driver. The
1868 split was done to make new features that are incompatible
1869 with older hardware easier to do.
1872 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1873 likewise the kernel option is now GEOM_LINUX_LVM.
1876 The default NFS mount mode has changed from UDP to TCP for
1877 increased reliability. If you rely on (insecurely) NFS
1878 mounting across a firewall you may need to update your
1882 Belatedly note the addition of m_collapse for compacting
1886 The fts(3) structures have been changed to use adequate
1887 integer types for their members and so to be able to cope
1888 with huge file trees. The old fts(3) ABI is preserved
1889 through symbol versioning in libc, so third-party binaries
1890 using fts(3) should still work, although they will not take
1891 advantage of the extended types. At the same time, some
1892 third-party software might fail to build after this change
1893 due to unportable assumptions made in its source code about
1894 fts(3) structure members. Such software should be fixed
1895 by its vendor or, in the worst case, in the ports tree.
1896 FreeBSD_version 800015 marks this change for the unlikely
1897 case that a portable fix is impossible.
1900 To upgrade to -current after this date, you must be running
1901 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1902 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1905 The ADAPTIVE_GIANT kernel option has been retired because its
1906 functionality is the default now.
1909 The AT keyboard emulation of sunkbd(4) has been turned on
1910 by default. In order to make the special symbols of the Sun
1911 keyboards driven by sunkbd(4) work under X these now have
1912 to be configured the same way as Sun USB keyboards driven
1913 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1915 Option "XkbLayout" "us"
1916 Option "XkbRules" "xorg"
1917 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1920 It has been decided that it is desirable to provide ABI
1921 backwards compatibility to the FreeBSD 4/5/6 versions of the
1922 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1923 broken with the introduction of PCI domain support (see the
1924 20070930 entry). Unfortunately, this required the ABI of
1925 PCIOCGETCONF to be broken again in order to be able to
1926 provide backwards compatibility to the old version of that
1927 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1928 again. As for prominent ports this affects neither pciutils
1929 nor xorg-server this time, the hal port needs to be rebuilt
1933 The misnamed kthread_create() and friends have been renamed
1934 to kproc_create() etc. Many of the callers already
1935 used kproc_start()..
1936 I will return kthread_create() and friends in a while
1937 with implementations that actually create threads, not procs.
1938 Renaming corresponds with version 800002.
1947 Avoid using make -j when upgrading. While generally safe, there are
1948 sometimes problems using -j to upgrade. If your upgrade fails with
1949 -j, please try again without -j. From time to time in the past there
1950 have been problems using -j with buildworld and/or installworld. This
1951 is especially true when upgrading between "distant" versions (eg one
1952 that cross a major release boundary or several minor releases, or when
1953 several months have passed on the -current branch).
1955 Sometimes, obscure build problems are the result of environment
1956 poisoning. This can happen because the make utility reads its
1957 environment when searching for values for global variables. To run
1958 your build attempts in an "environmental clean room", prefix all make
1959 commands with 'env -i '. See the env(1) manual page for more details.
1961 When upgrading from one major version to another it is generally best
1962 to upgrade to the latest code in the currently installed branch first,
1963 then do an upgrade to the new branch. This is the best-tested upgrade
1964 path, and has the highest probability of being successful. Please try
1965 this approach before reporting problems with a major version upgrade.
1967 When upgrading a live system, having a root shell around before
1968 installing anything can help undo problems. Not having a root shell
1969 around can lead to problems if pam has changed too much from your
1970 starting point to allow continued authentication after the upgrade.
1974 When upgrading the boot ZFS pool to a new version, always follow
1977 1.) recompile and reinstall the ZFS boot loader and boot block
1978 (this is part of "make buildworld" and "make installworld")
1980 2.) update the ZFS boot block on your boot drive
1982 The following example updates the ZFS boot block on the first
1983 partition (freebsd-boot) of a GPT partitioned drive ad0:
1984 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1986 Non-boot pools do not need these updates.
1990 If you are updating from a prior version of FreeBSD (even one just
1991 a few days old), you should follow this procedure. It is the most
1992 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1994 make kernel-toolchain
1995 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1996 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1998 To test a kernel once
1999 ---------------------
2000 If you just want to boot a kernel once (because you are not sure
2001 if it works, or if you want to boot a known bad kernel to provide
2002 debugging information) run
2003 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2004 nextboot -k testkernel
2006 To just build a kernel when you know that it won't mess you up
2007 --------------------------------------------------------------
2008 This assumes you are already running a CURRENT system. Replace
2009 ${arch} with the architecture of your machine (e.g. "i386",
2010 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2012 cd src/sys/${arch}/conf
2013 config KERNEL_NAME_HERE
2014 cd ../compile/KERNEL_NAME_HERE
2019 If this fails, go to the "To build a kernel" section.
2021 To rebuild everything and install it on the current system.
2022 -----------------------------------------------------------
2023 # Note: sometimes if you are running current you gotta do more than
2024 # is listed here if you are upgrading from a really old current.
2026 <make sure you have good level 0 dumps>
2028 make kernel KERNCONF=YOUR_KERNEL_HERE
2030 <reboot in single user> [3]
2037 To cross-install current onto a separate partition
2038 --------------------------------------------------
2039 # In this approach we use a separate partition to hold
2040 # current's root, 'usr', and 'var' directories. A partition
2041 # holding "/", "/usr" and "/var" should be about 2GB in
2044 <make sure you have good level 0 dumps>
2047 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2048 <maybe newfs current's root partition>
2049 <mount current's root partition on directory ${CURRENT_ROOT}>
2050 make installworld DESTDIR=${CURRENT_ROOT}
2051 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2052 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2053 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2054 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2055 <reboot into current>
2056 <do a "native" rebuild/install as described in the previous section>
2057 <maybe install compatibility libraries from ports/misc/compat*>
2061 To upgrade in-place from stable to current
2062 ----------------------------------------------
2063 <make sure you have good level 0 dumps>
2065 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2067 <reboot in single user> [3]
2074 Make sure that you've read the UPDATING file to understand the
2075 tweaks to various things you need. At this point in the life
2076 cycle of current, things change often and you are on your own
2077 to cope. The defaults can also change, so please read ALL of
2078 the UPDATING entries.
2080 Also, if you are tracking -current, you must be subscribed to
2081 freebsd-current@freebsd.org. Make sure that before you update
2082 your sources that you have read and understood all the recent
2083 messages there. If in doubt, please track -stable which has
2084 much fewer pitfalls.
2086 [1] If you have third party modules, such as vmware, you
2087 should disable them at this point so they don't crash your
2090 [3] From the bootblocks, boot -s, and then do
2095 adjkerntz -i # if CMOS is wall time
2096 Also, when doing a major release upgrade, it is required that
2097 you boot into single user mode to do the installworld.
2099 [4] Note: This step is non-optional. Failure to do this step
2100 can result in a significant reduction in the functionality of the
2101 system. Attempting to do it by hand is not recommended and those
2102 that pursue this avenue should read this file carefully, as well
2103 as the archives of freebsd-current and freebsd-hackers mailing lists
2104 for potential gotchas. The -U option is also useful to consider.
2105 See mergemaster(8) for more information.
2107 [5] Usually this step is a noop. However, from time to time
2108 you may need to do this if you get unknown user in the following
2109 step. It never hurts to do it all the time. You may need to
2110 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2111 install) after the buildworld before this step if you last updated
2112 from current before 20130425 or from -stable before 20130430.
2114 [6] This only deletes old files and directories. Old libraries
2115 can be deleted by "make delete-old-libs", but you have to make
2116 sure that no program is using those libraries anymore.
2118 [8] In order to have a kernel that can run the 4.x binaries needed to
2119 do an installworld, you must include the COMPAT_FREEBSD4 option in
2120 your kernel. Failure to do so may leave you with a system that is
2121 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2122 required to run the 5.x binaries on more recent kernels. And so on
2123 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2125 Make sure that you merge any new devices from GENERIC since the
2126 last time you updated your kernel config file.
2128 [9] When checking out sources, you must include the -P flag to have
2129 cvs prune empty directories.
2131 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2132 "?=" instead of the "=" assignment operator, so that buildworld can
2133 override the CPUTYPE if it needs to.
2135 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2136 not on the command line, or in /etc/make.conf. buildworld will
2137 warn if it is improperly defined.
2140 This file contains a list, in reverse chronological order, of major
2141 breakages in tracking -current. It is not guaranteed to be a complete
2142 list of such breakages, and only contains entries since October 10, 2007.
2143 If you need to see UPDATING entries from before that date, you will need
2144 to fetch an UPDATING file from an older FreeBSD release.
2146 Copyright information:
2148 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2150 Redistribution, publication, translation and use, with or without
2151 modification, in full or in part, in any form or format of this
2152 document are permitted without further permission from the author.
2154 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2155 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2156 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2157 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2158 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2159 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2160 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2161 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2162 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2163 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2164 POSSIBILITY OF SUCH DAMAGE.
2166 Contact Warner Losh if you have any questions about your use of