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