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