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