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