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