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