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.
20 The ofwfb driver, used to provide a graphics console on PowerPC when
21 using vt(4), no longer allows mmap() of all of physical memory. This
22 will prevent Xorg on PowerPC with some ATI graphics cards from
23 initializing properly unless x11-servers/xorg-server is updated to
27 The libatf-c and libatf-c++ major versions were downgraded to 0 and
28 1 respectively to match the upstream numbers. They were out of
29 sync because, when they were originally added to FreeBSD, the
30 upstream versions were not respected. These libraries are private
31 and not yet built by default, so renumbering them should be a
32 non-issue. However, unclean source trees will yield broken test
33 programs once the operator executes "make delete-old-libs" after a
36 Additionally, the atf-sh binary was made private by moving it into
37 /usr/libexec/. Already-built shell test programs will keep the
38 path to the old binary so they will break after "make delete-old"
41 If you are using WITH_TESTS=yes (not the default), wipe the object
42 tree and rebuild from scratch to prevent spurious test failures.
43 This is only needed once: the misnumbered libraries and misplaced
44 binaries have been added to OptionalObsoleteFiles.inc so they will
45 be removed during a clean upgrade.
48 The ixgbe tunables now match their sysctl counterparts, for example:
49 hw.ixgbe.enable_aim => hw.ix.enable_aim
50 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
53 The NFSv4.1 server committed by r269398 changes the internal
54 function call interfaces used between the NFS and krpc modules.
55 As such, __FreeBSD_version was bumped.
58 The default unbound configuration has been modified to address
59 issues with reverse lookups on networks that use private
60 address ranges. If you use the local_unbound service, run
61 "service local_unbound setup" as root to regenerate your
62 configuration, then "service local_unbound reload" to load the
66 It is no longer necessary to include the dwarf version in your DEBUG
67 options in your kernel config file. The bug that required it to be
68 placed in the config file has bene fixed. DEBUG should now just
69 contain -g. The build system will automatically update things
70 to do the right thing.
73 Several ABI breaking changes were merged to CTL and new iSCSI code.
74 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
75 iscsictl need to be rebuilt to work with a new kernel.
78 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
79 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
80 which differs from the behaviour controlled by this knob.)
83 On i386 and amd64 systems, the onifconsole flag is now set by default
84 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
85 as a login TTY if it is set in the bootloader as an active kernel
86 console. No changes in behavior should result otherwise. To revert to
87 the previous behavior, set ttyu0 to "off" in /etc/ttys.
90 Clang and llvm have been upgraded to 3.4.1 release.
93 Clang and llvm have been upgraded to 3.4 release.
96 If a Makefile in a tests/ directory was auto-generating a Kyuafile
97 instead of providing an explicit one, this would prevent such
98 Makefile from providing its own Kyuafile in the future during
99 NO_CLEAN builds. This has been fixed in the Makefiles but manual
100 intervention is needed to clean an objdir if you use NO_CLEAN:
101 # find /usr/obj -name Kyuafile | xargs rm -f
104 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
105 capability mode support. Please note that enabling the feature in
106 kernel is still highly recommended.
109 OpenSSH is now built with sandbox support, and will use sandbox as
110 the default privilege separation method. This requires Capsicum
111 capability mode support in kernel.
114 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
115 been deprecated and will not be part of FreeBSD 11.0 and later
116 releases. If you use this driver, please consider switching to
117 the nfe(4) driver instead.
123 The behavior of gss_pseudo_random() for the krb5 mechanism
124 has changed, for applications requesting a longer random string
125 than produced by the underlying enctype's pseudo-random() function.
126 In particular, the random string produced from a session key of
127 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
128 be different at the 17th octet and later, after this change.
129 The counter used in the PRF+ construction is now encoded as a
130 big-endian integer in accordance with RFC 4402.
131 __FreeBSD_version is bumped to 1000701.
134 The WITHOUT_ATF build knob has been removed and its functionality
135 has been subsumed into the more generic WITHOUT_TESTS. If you were
136 using the former to disable the build of the ATF libraries, you
137 should change your settings to use the latter.
140 The default version of mtree is nmtree which is obtained from
141 NetBSD. The output is generally the same, but may vary
142 slightly. If you found you need identical output adding
143 "-F freebsd9" to the command line should do the trick. For the
144 time being, the old mtree is available as fmtree.
147 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
148 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
149 1.1.4_8 and verify bsdyml not linked in, before running "make
151 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
153 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
156 The rc.d/jail script has been updated to support jail(8)
157 configuration file. The "jail_<jname>_*" rc.conf(5) variables
158 for per-jail configuration are automatically converted to
159 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
160 This is transparently backward compatible. See below about some
161 incompatibilities and rc.conf(5) manual page for more details.
163 These variables are now deprecated in favor of jail(8) configuration
164 file. One can use "rc.d/jail config <jname>" command to generate
165 a jail(8) configuration file in /var/run/jail.<jname>.conf without
166 running the jail(8) utility. The default pathname of the
167 configuration file is /etc/jail.conf and can be specified by
168 using $jail_conf or $jail_<jname>_conf variables.
170 Please note that jail_devfs_ruleset accepts an integer at
171 this moment. Please consider to rewrite the ruleset name
175 BIND has been removed from the base system. If all you need
176 is a local resolver, simply enable and start the local_unbound
177 service instead. Otherwise, several versions of BIND are
178 available in the ports tree. The dns/bind99 port is one example.
180 With this change, nslookup(1) and dig(1) are no longer in the base
181 system. Users should instead use host(1) and drill(1) which are
182 in the base system. Alternatively, nslookup and dig can
183 be obtained by installing the dns/bind-tools port.
186 With the addition of unbound(8), a new unbound user is now
187 required during installworld. "mergemaster -p" can be used to
188 add the user prior to installworld, as documented in the handbook.
191 OpenSSH is now built with DNSSEC support, and will by default
192 silently trust signed SSHFP records. This can be controlled with
193 the VerifyHostKeyDNS client configuration setting. DNSSEC support
194 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
197 The GNU Compiler Collection and C++ standard library (libstdc++)
198 are no longer built by default on platforms where clang is the system
199 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
203 The PROCDESC kernel option is now part of the GENERIC kernel
204 configuration and is required for the rwhod(8) to work.
205 If you are using custom kernel configuration, you should include
209 The API and ABI related to the Capsicum framework was modified
210 in backward incompatible way. The userland libraries and programs
211 have to be recompiled to work with the new kernel. This includes the
212 following libraries and programs, but the whole buildworld is
213 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
214 kdump, procstat, rwho, rwhod, uniq.
217 AES-NI intrinsic support has been added to gcc. The AES-NI module
218 has been updated to use this support. A new gcc is required to build
219 the aesni module on both i386 and amd64.
222 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
223 Thus "device padlock_rng" and "device rdrand_rng" should be
224 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
227 WITH_ICONV has been split into two feature sets. WITH_ICONV now
228 enables just the iconv* functionality and is now on by default.
229 WITH_LIBICONV_COMPAT enables the libiconv api and link time
230 compatability. Set WITHOUT_ICONV to build the old way.
231 If you have been using WITH_ICONV before, you will very likely
232 need to turn on WITH_LIBICONV_COMPAT.
235 INVARIANTS option now enables DEBUG for code with OpenSolaris and
236 Illumos origin, including ZFS. If you have INVARIANTS in your
237 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
239 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
240 locks if WITNESS option was set. Because that generated a lot of
241 witness(9) reports and all of them were believed to be false
242 positives, this is no longer done. New option OPENSOLARIS_WITNESS
243 can be used to achieve the previous behavior.
246 Timer values in IPv6 data structures now use time_uptime instead
247 of time_second. Although this is not a user-visible functional
248 change, userland utilities which directly use them---ndp(8),
249 rtadvd(8), and rtsold(8) in the base system---need to be updated
253 find -delete can now delete the pathnames given as arguments,
254 instead of only files found below them or if the pathname did
255 not contain any slashes. Formerly, the following error message
258 find: -delete: <path>: relative path potentially not safe
260 Deleting the pathnames given as arguments can be prevented
261 without error messages using -mindepth 1 or by changing
262 directory and passing "." as argument to find. This works in the
263 old as well as the new version of find.
266 Behavior of devfs rules path matching has been changed.
267 Pattern is now always matched against fully qualified devfs
268 path and slash characters must be explicitly matched by
269 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
270 subdirectories must be reviewed.
273 The default ARM ABI has changed to the ARM EABI. The old ABI is
274 incompatible with the ARM EABI and all programs and modules will
275 need to be rebuilt to work with a new kernel.
277 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
279 NOTE: Support for the old ABI will be removed in the future and
280 users are advised to upgrade.
283 pkg_install has been disconnected from the build if you really need it
284 you should add WITH_PKGTOOLS in your src.conf(5).
287 Most of network statistics structures were changed to be able
288 keep 64-bits counters. Thus all tools, that work with networking
289 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
292 Fix targets that run multiple make's to use && rather than ;
293 so that subsequent steps depend on success of previous.
295 NOTE: if building 'universe' with -j* on stable/8 or stable/9
296 it would be better to start the build using bmake, to avoid
297 overloading the machine.
300 Fix a bug that allowed a tracing process (e.g. gdb) to write
301 to a memory-mapped file in the traced process's address space
302 even if neither the traced process nor the tracing process had
303 write access to that file.
306 CVS has been removed from the base system. An exact copy
307 of the code is available from the devel/cvs port.
310 Some people report the following error after the switch to bmake:
312 make: illegal option -- J
313 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
315 *** [buildworld] Error code 2
317 this likely due to an old instance of make in
318 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
319 which src/Makefile will use that blindly, if it exists, so if
320 you see the above error:
322 rm -rf `make -V MAKEPATH`
327 Use bmake by default.
328 Whereas before one could choose to build with bmake via
329 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
330 make. The goal is to remove these knobs for 10-RELEASE.
332 It is worth noting that bmake (like gmake) treats the command
333 line as the unit of failure, rather than statements within the
334 command line. Thus '(cd some/where && dosomething)' is safer
335 than 'cd some/where; dosomething'. The '()' allows consistent
336 behavior in parallel build.
339 Fix a bug that allows NFS clients to issue READDIR on files.
342 The WITHOUT_IDEA option has been removed because
343 the IDEA patent expired.
346 The sysctl which controls TRIM support under ZFS has been renamed
347 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
351 The mergemaster command now uses the default MAKEOBJDIRPREFIX
352 rather than creating it's own in the temporary directory in
353 order allow access to bootstrapped versions of tools such as
354 install and mtree. When upgrading from version of FreeBSD where
355 the install command does not support -l, you will need to
356 install a new mergemaster command if mergemaster -p is required.
357 This can be accomplished with the command (cd src/usr.sbin/mergemaster
361 Legacy ATA stack, disabled and replaced by new CAM-based one since
362 FreeBSD 9.0, completely removed from the sources. Kernel modules
363 atadisk and atapi*, user-level tools atacontrol and burncd are
364 removed. Kernel option `options ATA_CAM` is now permanently enabled
368 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
369 and socketpair(2). Software, in particular Kerberos, may
370 automatically detect and use these during building. The resulting
371 binaries will not work on older kernels.
374 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
375 information, see the respective 20130304 entry).
378 Recent commits to callout(9) changed the size of struct callout,
379 so the KBI is probably heavily disturbed. Also, some functions
380 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
381 by macros. Every kernel module using it won't load, so rebuild
384 The ctl device has been re-enabled in GENERIC for i386 and amd64,
385 but does not initialize by default (because of the new CTL_DISABLE
386 option) to save memory. To re-enable it, remove the CTL_DISABLE
387 option from the kernel config file or set kern.cam.ctl.disable=0
388 in /boot/loader.conf.
391 The ctl device has been disabled in GENERIC for i386 and amd64.
392 This was done due to the extra memory being allocated at system
393 initialisation time by the ctl driver which was only used if
394 a CAM target device was created. This makes a FreeBSD system
395 unusable on 128MB or less of RAM.
398 A new compression method (lz4) has been merged to -HEAD. Please
399 refer to zpool-features(7) for more information.
401 Please refer to the "ZFS notes" section of this file for information
402 on upgrading boot ZFS pools.
405 A BSD-licensed patch(1) variant has been added and is installed
406 as bsdpatch, being the GNU version the default patch.
407 To inverse the logic and use the BSD-licensed one as default,
408 while having the GNU version installed as gnupatch, rebuild
409 and install world with the WITH_BSD_PATCH knob set.
412 Due to the use of the new -l option to install(1) during build
413 and install, you must take care not to directly set the INSTALL
414 make variable in your /etc/make.conf, /etc/src.conf, or on the
415 command line. If you wish to use the -C flag for all installs
416 you may be able to add INSTALL+=-C to /etc/make.conf or
420 The install(1) option -M has changed meaning and now takes an
421 argument that is a file or path to append logs to. In the
422 unlikely event that -M was the last option on the command line
423 and the command line contained at least two files and a target
424 directory the first file will have logs appended to it. The -M
425 option served little practical purpose in the last decade so its
426 use is expected to be extremely rare.
429 After switching to Clang as the default compiler some users of ZFS
430 on i386 systems started to experience stack overflow kernel panics.
431 Please consider using 'options KSTACK_PAGES=4' in such configurations.
434 GEOM_LABEL now mangles label names read from file system metadata.
435 Mangling affect labels containing spaces, non-printable characters,
436 '%' or '"'. Device names in /etc/fstab and other places may need to
440 By default, only the 10 most recent kernel dumps will be saved. To
441 restore the previous behaviour (no limit on the number of kernel dumps
442 stored in the dump directory) add the following line to /etc/rc.conf:
447 With the addition of auditdistd(8), a new auditdistd user is now
448 required during installworld. "mergemaster -p" can be used to
449 add the user prior to installworld, as documented in the handbook.
452 The sin6_scope_id member variable in struct sockaddr_in6 is now
453 filled by the kernel before passing the structure to the userland via
454 sysctl or routing socket. This means the KAME-specific embedded scope
455 id in sin6_addr.s6_addr[2] is always cleared in userland application.
456 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
457 __FreeBSD_version is bumped to 1000025.
460 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
461 This means that the world and kernel will be compiled with clang
462 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
463 and /usr/bin/cpp. To disable this behavior and revert to building
464 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
465 of current may need to bootstrap WITHOUT_CLANG first if the clang
466 build fails (its compatibility window doesn't extend to the 9 stable
470 The IPFIREWALL_FORWARD kernel option has been removed. Its
471 functionality now turned on by default.
474 The ZERO_COPY_SOCKET kernel option has been removed and
475 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
476 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
477 mechanism which is not safe and may result in kernel crashes.
478 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
479 driver supports disposeable external page sized mbuf storage.
480 Proper replacements for both zero-copy mechanisms are under
481 consideration and will eventually lead to complete removal
482 of the two kernel options.
485 The IPv4 network stack has been converted to network byte
486 order. The following modules need to be recompiled together
487 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
488 pf(4), ipfw(4), ng_ipfw(4), stf(4).
491 Support for non-MPSAFE filesystems was removed from VFS. The
492 VFS_VERSION was bumped, all filesystem modules shall be
496 All the non-MPSAFE filesystems have been disconnected from
497 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
498 portalfs, smbfs, xfs.
501 The interface cloning API and ABI has changed. The following
502 modules need to be recompiled together with kernel:
503 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
504 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
505 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
508 The sdhci driver was split in two parts: sdhci (generic SD Host
509 Controller logic) and sdhci_pci (actual hardware driver).
510 No kernel config modifications are required, but if you
511 load sdhc as a module you must switch to sdhci_pci instead.
514 Import the FUSE kernel and userland support into base system.
517 The GNU sort(1) program has been removed since the BSD-licensed
518 sort(1) has been the default for quite some time and no serious
519 problems have been reported. The corresponding WITH_GNU_SORT
523 The pfil(9) API/ABI for AF_INET family has been changed. Packet
524 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
528 The net80211(4) ABI has been changed to allow for improved driver
529 PS-POLL and power-save support. All wireless drivers need to be
530 recompiled to work with the new kernel.
533 The random(4) support for the VIA hardware random number
534 generator (`PADLOCK') is no longer enabled unconditionally.
535 Add the padlock_rng device in the custom kernel config if
536 needed. The GENERIC kernels on i386 and amd64 do include the
537 device, so the change only affects the custom kernel
541 The pf(4) packet filter ABI has been changed. pfctl(8) and
542 snmp_pf module need to be recompiled to work with new kernel.
545 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
546 to -HEAD. Pools that have empty_bpobj in active state can not be
547 imported read-write with ZFS implementations that do not support
548 this feature. For more information read the zpool-features(5)
552 The sparc64 ZFS loader has been changed to no longer try to auto-
553 detect ZFS providers based on diskN aliases but now requires these
554 to be explicitly listed in the OFW boot-device environment variable.
557 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
558 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
559 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
562 The following sysctls and tunables have been renamed for consistency
563 with other variables:
564 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
565 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
568 The sort utility has been replaced with BSD sort. For now, GNU sort
569 is also available as "gnusort" or the default can be set back to
570 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
571 installed as "bsdsort".
574 A new version of ZFS (pool version 5000) has been merged to -HEAD.
575 Starting with this version the old system of ZFS pool versioning
576 is superseded by "feature flags". This concept enables forward
577 compatibility against certain future changes in functionality of ZFS
578 pools. The first read-only compatible "feature flag" for ZFS pools
579 is named "com.delphix:async_destroy". For more information
580 read the new zpool-features(5) manual page.
581 Please refer to the "ZFS notes" section of this file for information
582 on upgrading boot ZFS pools.
585 The malloc(3) implementation embedded in libc now uses sources imported
586 as contrib/jemalloc. The most disruptive API change is to
587 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
588 delete it prior to installworld, and optionally re-create it using the
589 new format after rebooting. See malloc.conf(5) for details
590 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
594 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
595 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
596 now spelled mips. This is to aid compatibility with third-party
597 software that expects this naming scheme in uname(3). Little-endian
598 settings are unchanged. If you are updating a big-endian mips64 machine
599 from before this change, you may need to set MACHINE_ARCH=mips64 in
600 your environment before the new build system will recognize your machine.
603 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
607 Now unix domain sockets behave "as expected" on nullfs(5). Previously
608 nullfs(5) did not pass through all behaviours to the underlying layer,
609 as a result if we bound to a socket on the lower layer we could connect
610 only to the lower path; if we bound to the upper layer we could connect
611 only to the upper path. The new behavior is one can connect to both the
612 lower and the upper paths regardless what layer path one binds to.
615 The getifaddrs upgrade path broken with 20111215 has been restored.
616 If you have upgraded in between 20111215 and 20120209 you need to
617 recompile libc again with your kernel. You still need to recompile
618 world to be able to configure CARP but this restriction already
622 The set_rcvar() function has been removed from /etc/rc.subr. All
623 base and ports rc.d scripts have been updated, so if you have a
624 port installed with a script in /usr/local/etc/rc.d you can either
625 hand-edit the rcvar= line, or reinstall the port.
627 An easy way to handle the mass-update of /etc/rc.d:
628 rm /etc/rc.d/* && mergemaster -i
631 panic(9) now stops other CPUs in the SMP systems, disables interrupts
632 on the current CPU and prevents other threads from running.
633 This behavior can be reverted using the kern.stop_scheduler_on_panic
635 The new behavior can be incompatible with kern.sync_on_panic.
638 The carp(4) facility has been changed significantly. Configuration
639 of the CARP protocol via ifconfig(8) has changed, as well as format
640 of CARP events submitted to devd(8) has changed. See manual pages
641 for more information. The arpbalance feature of carp(4) is currently
642 not supported anymore.
644 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
645 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
646 need to be recompiled.
649 The acpi_wmi(4) status device /dev/wmistat has been renamed to
653 The option VFS_ALLOW_NONMPSAFE option has been added in order to
654 explicitely support non-MPSAFE filesystems.
655 It is on by default for all supported platform at this present
659 The broken amd(4) driver has been replaced with esp(4) in the amd64,
660 i386 and pc98 GENERIC kernel configuration files.
663 sysinstall has been removed
666 The stable/9 branch created in subversion. This corresponds to the
667 RELENG_9 branch in CVS.
670 This commit modifies vfs_register() so that it uses a hash
671 calculation to set vfc_typenum, which is enabled by default.
672 The first time a system is booted after this change, the
673 vfc_typenum values will change for all file systems. The
674 main effect of this is a change to the NFS server file handles
675 for file systems that use vfc_typenum in their fsid, such as ZFS.
676 It will, however, prevent vfc_typenum from changing when file
677 systems are loaded in a different order for subsequent reboots.
678 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
679 until you are ready to remount all NFS clients after a reboot.
682 Bump the shared library version numbers for libraries that
683 do not use symbol versioning, have changed the ABI compared
684 to stable/8 and which shared library version was not bumped.
685 Done as part of 9.0-RELEASE cycle.
688 During the merge of Capsicum features, the fget(9) KPI was modified.
689 This may require the rebuilding of out-of-tree device drivers --
690 issues have been reported specifically with the nVidia device driver.
691 __FreeBSD_version is bumped to 900041.
693 Also, there is a period between 20110811 and 20110814 where the
694 special devices /dev/{stdin,stdout,stderr} did not work correctly.
695 Building world from a kernel during that window may not work.
698 The packet filter (pf) code has been updated to OpenBSD 4.5.
699 You need to update userland tools to be in sync with kernel.
700 This update breaks backward compatibility with earlier pfsync(4)
701 versions. Care must be taken when updating redundant firewall setups.
704 The following sysctls and tunables are retired on x86 platforms:
706 machdep.hlt_logical_cpus
707 The following sysctl is retired:
708 machdep.hyperthreading_allowed
709 The sysctls were supposed to provide a way to dynamically offline and
710 online selected CPUs on x86 platforms, but the implementation has not
711 been reliable especially with SCHED_ULE scheduler.
712 machdep.hyperthreading_allowed tunable is still available to ignore
713 hyperthreading CPUs at OS level.
714 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
715 where X is an APIC ID of a CPU. Be advised, though, that disabling
716 CPUs in non-uniform fashion will result in non-uniform topology and
717 may lead to sub-optimal system performance with SCHED_ULE, which is
721 cpumask_t type is retired and cpuset_t is used in order to describe
725 Changes to ifconfig(8) for dynamic address family detection mandate
726 that you are running a kernel of 20110525 or later. Make sure to
727 follow the update procedure to boot a new kernel before installing
731 Support for sun4v architecture is officially dropped
734 Several KPI breaking changes have been committed to the mii(4) layer,
735 the PHY drivers and consequently some Ethernet drivers using mii(4).
736 This means that miibus.ko and the modules of the affected Ethernet
737 drivers need to be recompiled.
739 Note to kernel developers: Given that the OUI bit reversion problem
740 was fixed as part of these changes all mii(4) commits related to OUIs,
741 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
742 handling, no longer can be merged verbatim to stable/8 and previous
746 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
747 into their kernel configurations along with 'device pci'.
750 The default NFS client is now the new NFS client, so fstype "newnfs"
751 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
752 Although mounts via fstype "nfs" will usually work without userland
753 changes, it is recommended that the mount(8) and mount_nfs(8)
754 commands be rebuilt from sources and that a link to mount_nfs called
755 mount_oldnfs be created. The new client is compiled into the
756 kernel with "options NFSCL" and this is needed for diskless root
757 file systems. The GENERIC kernel configs have been changed to use
758 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
759 To use the regular/old client, you can "mount -t oldnfs ...". For
760 a diskless root file system, you must also include a line like:
762 vfs.root.mountfrom="oldnfs:"
764 in the boot/loader.conf on the root fs on the NFS server to make
765 a diskless root fs use the old client.
768 The GENERIC kernels for all architectures now default to the new
769 CAM-based ATA stack. It means that all legacy ATA drivers were
770 removed and replaced by respective CAM drivers. If you are using
771 ATA device names in /etc/fstab or other places, make sure to update
772 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
773 where 'Y's are the sequential numbers starting from zero for each type
774 in order of detection, unless configured otherwise with tunables,
775 see cam(4)). There will be symbolic links created in /dev/ to map
776 old adX devices to the respective adaY. They should provide basic
777 compatibility for file systems mounting in most cases, but they do
778 not support old user-level APIs and do not have respective providers
779 in GEOM. Consider using updated management tools with new device names.
781 It is possible to load devices ahci, ata, siis and mvs as modules,
782 but option ATA_CAM should remain in kernel configuration to make ata
783 module work as CAM driver supporting legacy ATA controllers. Device ata
784 still can be used in modular fashion (atacore + ...). Modules atadisk
785 and atapi* are not used and won't affect operation in ATA_CAM mode.
786 Note that to use CAM-based ATA kernel should include CAM devices
787 scbus, pass, da (or explicitly ada), cd and optionally others. All of
788 them are parts of the cam module.
790 ataraid(4) functionality is now supported by the RAID GEOM class.
791 To use it you can load geom_raid kernel module and use graid(8) tool
792 for management. Instead of /dev/arX device names, use /dev/raid/rX.
794 No kernel config options or code have been removed, so if a problem
795 arises, please report it and optionally revert to the old ATA stack.
796 In order to do it you can remove from the kernel config:
801 , and instead add back:
802 device atadisk # ATA disk drives
803 device ataraid # ATA RAID drives
804 device atapicd # ATAPI CDROM drives
805 device atapifd # ATAPI floppy drives
806 device atapist # ATAPI tape drives
809 The default NFS server has been changed to the new server, which
810 was referred to as the experimental server. If you need to switch
811 back to the old NFS server, you must now put the "-o" option on
812 both the mountd and nfsd commands. This can be done using the
813 mountd_flags and nfs_server_flags rc.conf variables until an
814 update to the rc scripts is committed, which is coming soon.
817 The GNU Objective-C runtime library (libobjc), and other Objective-C
818 related components have been removed from the base system. If you
819 require an Objective-C library, please use one of the available ports.
822 ath(4) has been split into bus- and device- modules. if_ath contains
823 the HAL, the TX rate control and the network device code. if_ath_pci
824 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
825 contains the AHB glue. Users need to load both if_ath_pci and if_ath
826 in order to use ath on everything else.
828 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
829 need to load if_ath and if_ath_pci for ath(4) operation.
832 As part of the replacement of sysinstall, the process of building
833 release media has changed significantly. For details, please re-read
834 release(7), which has been updated to reflect the new build process.
837 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
838 is the last available version under GPLv2. It brings a number of new
839 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
840 4.1 and SSE 4.2), better support for powerpc64, a number of new
841 directives, and lots of other small improvements. See the ChangeLog
842 file in contrib/binutils for the full details.
845 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
846 compliant, and will now use half of hash for authentication.
847 This will break interoperability with all stacks (including all
848 actual FreeBSD versions) who implement
849 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
851 The only workaround with such peers is to use another HMAC
852 algorithm for IPsec ("phase 2") authentication.
855 Remove the uio_yield prototype and symbol. This function has
856 been misnamed since it was introduced and should not be
857 globally exposed with this name. The equivalent functionality
858 is now available using kern_yield(curthread->td_user_pri).
859 The function remains undocumented.
862 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
863 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
864 for scalar sysctls is defined but disabled. Code that needs
865 UQUAD to pass the type checking that must compile on older
866 systems where the define is not present can check against
867 __FreeBSD_version >= 900030.
869 The system dialog(1) has been replaced with a new version previously
870 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
871 with the previous version, but the libdialog associated with it has
872 a largely incompatible API. As such, the original version of libdialog
873 will be kept temporarily as libodialog, until its base system consumers
874 are replaced or updated. Bump __FreeBSD_version to 900030.
877 If you are trying to run make universe on a -stable system, and you get
878 the following warning:
879 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
880 unknown. config(8) likely too old."
881 or something similar to it, then you must upgrade your -stable system
882 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
883 stable/8) or build the config from the latest stable/8 branch and
884 install it on your system.
886 Prior to this date, building a current universe on 8-stable system from
887 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
888 error in the first kernel build phase. A new config on those old
889 systems will fix that problem for older versions of -current.
892 The TCP stack has been modified to allow Khelp modules to interact with
893 it via helper hook points and store per-connection data in the TCP
894 control block. Bump __FreeBSD_version to 900029. User space tools that
895 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
899 Generic IEEE 802.3 annex 31B full duplex flow control support has been
900 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
901 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
902 to take advantage of it instead of using custom implementations. This
903 means that these drivers now no longer unconditionally advertise
904 support for flow control but only do so if flow control is a selected
905 media option. This was implemented in the generic support that way in
906 order to allow flow control to be switched on and off via ifconfig(8)
907 with the PHY specific default to typically off in order to protect
908 from unwanted effects. Consequently, if you used flow control with
909 one of the above mentioned drivers you now need to explicitly enable
911 ifconfig bge0 media auto mediaopt flowcontrol
913 Along with the above mentioned changes generic support for setting
914 1000baseT master mode also has been added and brgphy(4), ciphy(4),
915 e1000phy(4) as well as ip1000phy(4) have been converted to take
916 advantage of it. This means that these drivers now no longer take the
917 link0 parameter for selecting master mode but the master media option
918 has to be used instead, for example like in the following:
919 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
921 Selection of master mode now is also available with all other PHY
922 drivers supporting 1000baseT.
925 The TCP stack has received a significant update to add support for
926 modularised congestion control and generally improve the clarity of
927 congestion control decisions. Bump __FreeBSD_version to 900025. User
928 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
929 sockstat) need to be recompiled.
932 The man(1) utility has been replaced by a new version that no longer
933 uses /etc/manpath.config. Please consult man.conf(5) for how to
934 migrate local entries to the new format.
937 The copyright strings printed by login(1) and sshd(8) at the time of a
938 new connection have been removed to follow other operating systems and
942 A workaround for a fixed ld bug has been removed in kernel code,
943 so make sure that your system ld is built from sources after
944 revision 210245 from 2010-07-19 (r211583 if building head kernel
945 on stable/8, r211584 for stable/7; both from 2010-08-21).
946 A symptom of incorrect ld version is different addresses for
947 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
950 The $ipv6_prefer variable in rc.conf(5) has been split into
951 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
953 The $ip6addrctl_policy is a variable to choose a pre-defined
954 address selection policy set by ip6addrctl(8). A value
955 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
958 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
959 flag (see an entry of 20090926) is set on an interface with no
960 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
961 security reason. If you want IPv6 link-local address on all
962 interfaces by default, set this to "YES".
964 The old ipv6_prefer="YES" is equivalent to
965 ipv6_activate_all_interfaces="YES" and
966 ip6addrctl_policy="ipv6_prefer".
969 DTrace has grown support for userland tracing. Due to this, DTrace is
970 now i386 and amd64 only.
971 dtruss(1) is now installed by default on those systems and a new
972 kernel module is needed for userland tracing: fasttrap.
973 No changes to your kernel config file are necessary to enable
974 userland tracing, but you might consider adding 'STRIP=' and
975 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
976 to have informative userland stack traces in DTrace (ustack).
979 The acpi_aiboost(4) driver has been removed in favor of the new
980 aibs(4) driver. You should update your kernel configuration file.
983 BSD grep has been imported to the base system and it is built by
984 default. It is completely BSD licensed, highly GNU-compatible, uses
985 less memory than its GNU counterpart and has a small codebase.
986 However, it is slower than its GNU counterpart, which is mostly
987 noticeable for larger searches, for smaller ones it is measurable
988 but not significant. The reason is complex, the most important factor
989 is that we lack a modern and efficient regex library and GNU
990 overcomes this by optimizing the searches internally. Future work
991 on improving the regex performance is planned, for the meantime,
992 users that need better performance, can build GNU grep instead by
993 setting the WITH_GNU_GREP knob.
996 Due to the import of powerpc64 support, all existing powerpc kernel
997 configuration files must be updated with a machine directive like this:
998 machine powerpc powerpc
1000 In addition, an updated config(8) is required to build powerpc kernels
1004 A new version of ZFS (version 15) has been merged to -HEAD.
1005 This version uses a python library for the following subcommands:
1006 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1007 For full functionality of these commands the following port must
1008 be installed: sysutils/py-zfs
1011 'vm_page's are now hashed by physical address to an array of mutexes.
1012 Currently this is only used to serialize access to hold_count. Over
1013 time the page queue mutex will be peeled away. This changes the size
1014 of pmap on every architecture. And requires all callers of vm_page_hold
1015 and vm_page_unhold to be updated.
1018 WITH_CTF can now be specified in src.conf (not recommended, there
1019 are some problems with static executables), make.conf (would also
1020 affect ports which do not use GNU make and do not override the
1021 compile targets) or in the kernel config (via "makeoptions
1023 When WITH_CTF was specified there before this was silently ignored,
1024 so make sure that WITH_CTF is not used in places which could lead
1025 to unwanted behavior.
1028 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1029 to allow 32-bit compatibility on non-x86 platforms. All kernel
1030 configurations on amd64 and ia64 platforms using these options must
1031 be modified accordingly.
1034 The utmp user accounting database has been replaced with utmpx,
1035 the user accounting interface standardized by POSIX.
1036 Unfortunately the semantics of utmp and utmpx don't match,
1037 making it practically impossible to support both interfaces.
1038 The user accounting database is used by tools like finger(1),
1039 last(1), talk(1), w(1) and ac(8).
1041 All applications in the base system use utmpx. This means only
1042 local binaries (e.g. from the ports tree) may still use these
1043 utmp database files. These applications must be rebuilt to make
1046 After the system has been upgraded, it is safe to remove the old
1047 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1048 assuming their contents is of no importance anymore. Old wtmp
1049 databases can only be used by last(1) and ac(8) after they have
1050 been converted to the new format using wtmpcvt(1).
1053 Introduce the kernel thread "deadlock resolver" (which can be enabled
1054 via the DEADLKRES option, see NOTES for more details) and the
1055 sleepq_type() function for sleepqueues.
1058 The rc.firewall and rc.firewall6 were unified, and
1059 rc.firewall6 and rc.d/ip6fw were removed.
1060 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1061 variables are obsoleted. Instead, the following new rc
1062 variables are added to rc.d/ipfw:
1064 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1065 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1066 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1068 The meanings correspond to the relevant IPv4 variables.
1074 The default terminal emulation for syscons(4) has been changed
1075 from cons25 to xterm on all platforms except pc98. This means
1076 that the /etc/ttys file needs to be updated to ensure correct
1077 operation of applications on the console.
1079 The terminal emulation style can be toggled per window by using
1080 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1081 options can be used to change the compile-time default back to
1084 To prevent graphical artifacts, make sure the TERM environment
1085 variable is set to match the terminal emulation that is being
1086 performed by syscons(4).
1089 The layout of the structure ieee80211req_scan_result has changed.
1090 Applications that require wireless scan results (e.g. ifconfig(8))
1091 from net80211 need to be recompiled.
1093 Applications such as wpa_supplicant(8) may require a full world
1094 build without using NO_CLEAN in order to get synchronized with the
1098 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1099 There's one kernel module for each firmware. Adding "device iwnfw"
1100 to the kernel configuration file means including all three firmware
1101 images inside the kernel. If you want to include just the one for
1102 your wireless card, use the devices iwn4965fw, iwn5000fw or
1106 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1107 into rc.d/netif. The changes are the following:
1109 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1110 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1111 Note that both variables need the "inet6" keyword at the head.
1113 Do not set $ipv6_network_interfaces manually if you do not
1114 understand what you are doing. It is not needed in most cases.
1116 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1119 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1120 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1122 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1123 all configured interfaces have "inet6 accept_rtadv" in the
1124 $ifconfig_IF_ipv6. These are for backward compatibility.
1126 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1127 functionality of interfaces with no corresponding
1128 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1129 and the default address selection policy of ip6addrctl(8)
1130 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1131 Note that if you want to configure IPv6 functionality on the
1132 disabled interfaces after boot, first you need to clear the flag by
1133 using ifconfig(8) like:
1135 ifconfig em0 inet6 -ifdisabled
1137 If YES, the default address selection policy is set as
1140 The default value of $ipv6_prefer is NO.
1142 4. If your system need to receive Router Advertisement messages,
1143 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1144 scripts automatically invoke rtsol(8) when the interface becomes
1145 UP. The Router Advertisement messages are used for SLAAC
1146 (State-Less Address AutoConfiguration).
1149 802.11s D3.03 support was committed. This is incompatible with the
1150 previous code, which was based on D3.0.
1153 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1154 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1155 control whether accepting Router Advertisement messages or not.
1156 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1157 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1158 The ifconfig(8) utility now supports these flags.
1161 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1162 mount(8) and -a option for df(1) to see them.
1165 The old tunable hw.bus.devctl_disable has been superseded by
1166 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1167 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1171 Remove the option STOP_NMI. The default action is now to use NMI only
1172 for KDB via the newly introduced function stop_cpus_hard() and
1173 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1176 The stable/8 branch created in subversion. This corresponds to the
1177 RELENG_8 branch in CVS.
1180 Bump the shared library version numbers for all libraries that do not
1181 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1182 __FreeBSD_version to 800105.
1185 Due to changes in the implementation of virtual network stack support,
1186 all network-related kernel modules must be recompiled. As this change
1187 breaks the ABI, bump __FreeBSD_version to 800104.
1190 The TOE interface to the TCP syncache has been modified to remove
1191 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1192 The cxgb driver is the only TOE consumer affected by this change, and
1193 needs to be recompiled along with the kernel. As this change breaks
1194 the ABI, bump __FreeBSD_version to 800103.
1197 Padding has been added to struct tcpcb, sackhint and tcpstat in
1198 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1199 maintaining the ABI. However, this change breaks the ABI, so bump
1200 __FreeBSD_version to 800102. User space tools that rely on the size of
1201 any of these structs (e.g. sockstat) need to be recompiled.
1204 The NFS_LEGACYRPC option has been removed along with the old kernel
1205 RPC implementation that this option selected. Kernel configurations
1206 may need to be adjusted.
1209 The network interface device nodes at /dev/net/<interface> have been
1210 removed. All ioctl operations can be performed the normal way using
1211 routing sockets. The kqueue functionality can generally be replaced
1212 with routing sockets.
1215 The documentation from the FreeBSD Documentation Project (Handbook,
1216 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1217 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1220 The ABI of various structures related to the SYSV IPC API have been
1221 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1222 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1226 Layout of struct vnet has changed as routing related variables were
1227 moved to their own Vimage module. Modules need to be recompiled. Bump
1228 __FreeBSD_version to 800099.
1231 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1232 respectively. As long as no more than 16 groups per process are used,
1233 no changes should be visible. When more than 16 groups are used, old
1234 binaries may fail if they call getgroups() or getgrouplist() with
1235 statically sized storage. Recompiling will work around this, but
1236 applications should be modified to use dynamically allocated storage
1237 for group arrays as POSIX.1-2008 does not cap an implementation's
1238 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1240 NFS and portalfs mounts may also be affected as the list of groups is
1241 truncated to 16. Users of NFS who use more than 16 groups, should
1242 take care that negative group permissions are not used on the exported
1243 file systems as they will not be reliable unless a GSSAPI based
1244 authentication method is used.
1247 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1248 option compiles in the support for adaptive spinning for lockmgrs
1249 which want to enable it. The lockinit() function now accepts the flag
1250 LK_ADAPTIVE in order to make the lock object subject to adaptive
1251 spinning when both held in write and read mode.
1254 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1255 changed. User applications that use this ioctl need to be rebuilt.
1258 The layout of struct thread has changed. Kernel and modules need to
1262 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1263 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1266 window(1) has been removed from the base system. It can now be
1267 installed from ports. The port is called misc/window.
1270 The way we are storing and accessing `routing table' entries has
1271 changed. Programs reading the FIB, like netstat, need to be
1275 A new netisr implementation has been added for FreeBSD 8. Network
1276 file system modules, such as igmp, ipdivert, and others, should be
1278 Bump __FreeBSD_version to 800096.
1281 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1285 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1286 Bump __FreeBSD_version to 800094.
1289 Add mnt_xflag field to 'struct mount'. File system modules need to be
1291 Bump __FreeBSD_version to 800093.
1294 The compiling option ADAPTIVE_SX has been retired while it has been
1295 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1296 The KPI for sx_init_flags() changes as accepting flags:
1297 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1298 been introduced in order to handle the reversed logic.
1299 Bump __FreeBSD_version to 800092.
1302 Add support for hierarchical jails. Remove global securelevel.
1303 Bump __FreeBSD_version to 800091.
1306 The layout of struct vnet_net has changed, therefore modules
1308 Bump __FreeBSD_version to 800090.
1311 The newly imported zic(8) produces a new format in the output. Please
1312 run tzsetup(8) to install the newly created data to /etc/localtime.
1315 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1316 hw.usb.* and is now consistent again with previous releases.
1319 802.11 monitor mode support was revised and driver api's were changed.
1320 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1321 of DLT_IEEE802_11. No user-visible data structures were changed but
1322 applications that use DLT_IEEE802_11 may require changes.
1323 Bump __FreeBSD_version to 800088.
1326 The layout of the following structs has changed: sysctl_oid,
1327 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1328 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1329 panics may be experienced. World rebuild is required for
1330 correctly checking networking state from userland.
1331 Bump __FreeBSD_version to 800085.
1334 MLDv2 and Source-Specific Multicast (SSM) have been merged
1335 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1336 The implementation of SSM within FreeBSD's IPv6 stack closely
1337 follows the IPv4 implementation.
1339 For kernel developers:
1341 * The most important changes are that the ip6_output() and
1342 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1343 and this lock has been downgraded to a non-recursive mutex.
1345 * As with the changes to the IPv4 stack to support SSM, filtering
1346 of inbound multicast traffic must now be performed by transport
1347 protocols within the IPv6 stack. This does not apply to TCP and
1348 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1350 * The KPIs used by IPv6 multicast are similar to those used by
1351 the IPv4 stack, with the following differences:
1352 * im6o_mc_filter() is analogous to imo_multicast_filter().
1353 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1354 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1355 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1356 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1357 for MLDv1 have an additional 'timer' argument which is used to
1358 jitter the initial membership report for the solicited-node
1359 multicast membership on-link.
1360 * This is not strictly needed for MLDv2, which already jitters
1361 its report transmissions. However, the 'timer' argument is
1362 preserved in case MLDv1 is active on the interface.
1364 * The KAME linked-list based IPv6 membership implementation has
1365 been refactored to use a vector similar to that used by the IPv4
1367 Code which maintains a list of its own multicast memberships
1368 internally, e.g. carp, has been updated to reflect the new
1371 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1372 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1373 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1374 implementation constraint which needs to be addressed in HEAD.
1376 For application developers:
1378 * The changes are broadly similar to those made for the IPv4
1381 * The use of IPv4 and IPv6 multicast socket options on the same
1382 socket, using mapped addresses, HAS NOT been tested or supported.
1384 * There are a number of issues with the implementation of various
1385 IPv6 multicast APIs which need to be resolved in the API surface
1386 before the implementation is fully compatible with KAME userland
1387 use, and these are mostly to do with interface index treatment.
1389 * The literature available discusses the use of either the delta / ASM
1390 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1391 using setsourcefilter(3)/getsourcefilter(3). For more information
1392 please refer to RFC 3768, 'Socket Interface Extensions for
1393 Multicast Source Filters'.
1395 * Applications which use the published RFC 3678 APIs should be fine.
1397 For systems administrators:
1399 * The mtest(8) utility has been refactored to support IPv6, in
1400 addition to IPv4. Interface addresses are no longer accepted
1401 as arguments, their names must be used instead. The utility
1402 will map the interface name to its first IPv4 address as
1403 returned by getifaddrs(3).
1405 * The ifmcstat(8) utility has also been updated to print the MLDv2
1406 endpoint state and source filter lists via sysctl(3).
1408 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1409 loopback of IPv6 multicast datagrams by default; it defaults to 1
1410 to preserve the existing behaviour. Disabling multicast loopback is
1411 recommended for optimal system performance.
1413 * The IPv6 MROUTING code has been changed to examine this sysctl
1414 instead of attempting to perform a group lookup before looping
1415 back forwarded datagrams.
1417 Bump __FreeBSD_version to 800084.
1420 Implement low-level Bluetooth HCI API.
1421 Bump __FreeBSD_version to 800083.
1424 The layout of struct malloc_type, used by modules to register new
1425 memory allocation types, has changed. Most modules will need to
1426 be rebuilt or panics may be experienced.
1427 Bump __FreeBSD_version to 800081.
1430 Anticipate overflowing inp_flags - add inp_flags2.
1431 This changes most offsets in inpcb, so checking v4 connection
1432 state will require a world rebuild.
1433 Bump __FreeBSD_version to 800080.
1436 Add an llentry to struct route and struct route_in6. Modules
1437 embedding a struct route will need to be recompiled.
1438 Bump __FreeBSD_version to 800079.
1441 The size of rt_metrics_lite and by extension rtentry has changed.
1442 Networking administration apps will need to be recompiled.
1443 The route command now supports show as an alias for get, weighting
1444 of routes, sticky and nostick flags to alter the behavior of stateful
1446 Bump __FreeBSD_version to 800078.
1449 Do not use Giant for kbdmux(4) locking. This is wrong and
1450 apparently causing more problems than it solves. This will
1451 re-open the issue where interrupt handlers may race with
1452 kbdmux(4) in polling mode. Typical symptoms include (but
1453 not limited to) duplicated and/or missing characters when
1454 low level console functions (such as gets) are used while
1455 interrupts are enabled (for example geli password prompt,
1456 mountroot prompt etc.). Disabling kbdmux(4) may help.
1459 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1460 kernel modules referencing any of the above need to be recompiled.
1461 Bump __FreeBSD_version to 800075.
1464 GEOM_PART has become the default partition slicer for storage devices,
1465 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1466 introduces some changes:
1468 MSDOS/EBR: the devices created from MSDOS extended partition entries
1469 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1470 to devices with offset-based names. fstabs may need to be modified.
1472 BSD: the "geometry does not match label" warning is harmless in most
1473 cases but it points to problems in file system misalignment with
1474 disk geometry. The "c" partition is now implicit, covers the whole
1475 top-level drive and cannot be (mis)used by users.
1477 General: Kernel dumps are now not allowed to be written to devices
1478 whose partition types indicate they are meant to be used for file
1479 systems (or, in case of MSDOS partitions, as something else than
1482 Most of these changes date approximately from 200812.
1485 The uscanner(4) driver has been removed from the kernel. This follows
1486 Linux removing theirs in 2.6 and making libusb the default interface
1487 (supported by sane).
1490 The multicast forwarding code has been cleaned up. netstat(1)
1491 only relies on KVM now for printing bandwidth upcall meters.
1492 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1493 ip6_mroute_mod respectively. The config(5) options for statically
1494 compiling this code remain the same, i.e. 'options MROUTING'.
1497 Support for the IFF_NEEDSGIANT network interface flag has been
1498 removed, which means that non-MPSAFE network device drivers are no
1499 longer supported. In particular, if_ar, if_sr, and network device
1500 drivers from the old (legacy) USB stack can no longer be built or
1504 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1505 a bunch of new language catalog files have also been added.
1506 This means that some common libc messages are now localized and
1507 they depend on the LC_MESSAGES environmental variable.
1510 The k8temp(4) driver has been renamed to amdtemp(4) since
1511 support for Family 10 and Family 11 CPU families was added.
1514 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1515 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1517 For kernel developers, the most important changes are that the
1518 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1519 and this lock has been downgraded to a non-recursive mutex.
1521 Transport protocols (UDP, Raw IP) are now responsible for filtering
1522 inbound multicast traffic according to group membership and source
1523 filters. The imo_multicast_filter() KPI exists for this purpose.
1524 Transports which do not use multicast (SCTP, TCP) already reject
1525 multicast by default. Forwarding and receive performance may improve
1526 as a mutex acquisition is no longer needed in the ip_input()
1527 low-level input path. in_addmulti() and in_delmulti() are shimmed
1528 to new KPIs which exist to support SSM in-kernel.
1530 For application developers, it is recommended that loopback of
1531 multicast datagrams be disabled for best performance, as this
1532 will still cause the lock to be taken for each looped-back
1533 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1534 be tuned to 0 to disable loopback by default; it defaults to 1
1535 to preserve the existing behaviour.
1537 For systems administrators, to obtain best performance with
1538 multicast reception and multiple groups, it is always recommended
1539 that a card with a suitably precise hash filter is used. Hash
1540 collisions will still result in the lock being taken within the
1541 transport protocol input path to check group membership.
1543 If deploying FreeBSD in an environment with IGMP snooping switches,
1544 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1545 enabled; this forces 224.0.0.0/24 group membership to be announced
1548 The size of 'struct igmpstat' has changed; netstat needs to be
1549 recompiled to reflect this.
1550 Bump __FreeBSD_version to 800070.
1553 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1554 updated to use it. This requires a buildworld/installworld in order to
1555 update the library and dependencies (usbconfig, etc). Its advisable to
1556 rebuild all ports which uses libusb. More specific directions are given
1557 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1558 libusb are no longer required and can be removed.
1561 A workaround is committed to allow the creation of System V shared
1562 memory segment of size > 2 GB on the 64-bit architectures.
1563 Due to a limitation of the existing ABI, the shm_segsz member
1564 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1565 wrong for large segments. Note that limits must be explicitly
1566 raised to allow such segments to be created.
1569 The layout of struct ifnet has changed, requiring a rebuild of all
1570 network device driver modules.
1573 The /dev handling for the new USB stack has changed, a
1574 buildworld/installworld is required for libusb20.
1577 The new USB2 stack has now been permanently moved in and all kernel and
1578 module names reverted to their previous values (eg, usb, ehci, ohci,
1579 ums, ...). The old usb stack can be compiled in by prefixing the name
1580 with the letter 'o', the old usb modules have been removed.
1581 Updating entry 20090216 for xorg and 20090215 for libmap may still
1585 The rc.conf(5) option if_up_delay has been renamed to
1586 defaultroute_delay to better reflect its purpose. If you have
1587 customized this setting in /etc/rc.conf you need to update it to
1591 xorg 7.4 wants to configure its input devices via hald which does not
1592 yet work with USB2. If the keyboard/mouse does not work in xorg then
1594 Option "AllowEmptyInput" "off"
1595 to your ServerLayout section. This will cause X to use the configured
1596 kbd and mouse sections from your xorg.conf.
1599 The GENERIC kernels for all architectures now default to the new USB2
1600 stack. No kernel config options or code have been removed so if a
1601 problem arises please report it and optionally revert to the old USB
1602 stack. If you are loading USB kernel modules or have a custom kernel
1603 that includes GENERIC then ensure that usb names are also changed over,
1604 eg uftdi -> usb2_serial_ftdi.
1606 Older programs linked against the ports libusb 0.1 need to be
1607 redirected to the new stack's libusb20. /etc/libmap.conf can
1609 # Map old usb library to new one for usb2 stack
1610 libusb-0.1.so.8 libusb20.so.1
1613 All USB ethernet devices now attach as interfaces under the name ueN
1614 (eg. ue0). This is to provide a predictable name as vendors often
1615 change usb chipsets in a product without notice.
1618 The ichsmb(4) driver has been changed to require SMBus slave
1619 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1620 All of the other SMBus controller drivers require left-justified
1621 slave addresses, so this change makes all the drivers provide the
1625 INET6 statistics (struct ip6stat) was updated.
1626 netstat(1) needs to be recompiled.
1629 NTFS has been removed from GENERIC kernel on amd64 to match
1630 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1631 will load ntfs.ko module automatically when NTFS support is
1632 actually needed, unless ntfs.ko is not installed or security
1633 level prohibits loading kernel modules. If either is the case,
1634 "options NTFS" has to be added into kernel config.
1637 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1638 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1639 800061. User space tools that rely on the size of struct tcpcb in
1640 tcp_var.h (e.g. sockstat) need to be recompiled.
1643 ng_tty(4) module updated to match the new TTY subsystem.
1644 Due to API change, user-level applications must be updated.
1645 New API support added to mpd5 CVS and expected to be present
1646 in next mpd5.3 release.
1649 With __FreeBSD_version 800060 the makefs tool is part of
1650 the base system (it was a port).
1653 The afdata and ifnet locks have been changed from mutexes to
1654 rwlocks, network modules will need to be re-compiled.
1657 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1658 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1659 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1660 architecture and 40 bytes on 64-bit architecture. The userland
1661 applications "arp" and "ndp" have been updated accordingly.
1662 The output from "netstat -r" shows only routing entries and
1663 none of the L2 information.
1666 __FreeBSD_version 800057 marks the switchover from the
1667 binary ath hal to source code. Users must add the line:
1669 options AH_SUPPORT_AR5416
1671 to their kernel config files when specifying:
1675 The ath_hal module no longer exists; the code is now compiled
1676 together with the driver in the ath module. It is now
1677 possible to tailor chip support (i.e. reduce the set of chips
1678 and thereby the code size); consult ath_hal(4) for details.
1681 __FreeBSD_version 800054 adds memory barriers to
1682 <machine/atomic.h>, new interfaces to ifnet to facilitate
1683 multiple hardware transmit queues for cards that support
1684 them, and a lock-less ring-buffer implementation to
1685 enable drivers to more efficiently manage queueing of
1689 A new version of ZFS (version 13) has been merged to -HEAD.
1690 This version has zpool attribute "listsnapshots" off by
1691 default, which means "zfs list" does not show snapshots,
1692 and is the same as Solaris behavior.
1695 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1698 The uhci, ohci, ehci and slhci USB Host controller drivers have
1699 been put into separate modules. If you load the usb module
1700 separately through loader.conf you will need to load the
1701 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1702 controller add the following to loader.conf:
1708 The ABI used by the PMC toolset has changed. Please keep
1709 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1713 atapci kernel module now includes only generic PCI ATA
1714 driver. AHCI driver moved to ataahci kernel module.
1715 All vendor-specific code moved into separate kernel modules:
1716 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1717 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1718 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1719 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1722 The TTY subsystem of the kernel has been replaced by a new
1723 implementation, which provides better scalability and an
1724 improved driver model. Most common drivers have been migrated to
1725 the new TTY subsystem, while others have not. The following
1726 drivers have not yet been ported to the new TTY layer:
1729 cy, digi, rc, rp, sio
1735 ng_h4, ng_tty, ppp, sl, snp
1737 Adding these drivers to your kernel configuration file shall
1738 cause compilation to fail.
1741 ntpd has been upgraded to 4.2.4p5.
1744 OpenSSH has been upgraded to 5.1p1.
1746 For many years, FreeBSD's version of OpenSSH preferred DSA
1747 over RSA for host and user authentication keys. With this
1748 upgrade, we've switched to the vendor's default of RSA over
1749 DSA. This may cause upgraded clients to warn about unknown
1750 host keys even for previously known hosts. Users should
1751 follow the usual procedure for verifying host keys before
1752 accepting the RSA key.
1754 This can be circumvented by setting the "HostKeyAlgorithms"
1755 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1758 Please note that the sequence of keys offered for
1759 authentication has been changed as well. You may want to
1760 specify IdentityFile in a different order to revert this
1764 The sio(4) driver has been removed from the i386 and amd64
1765 kernel configuration files. This means uart(4) is now the
1766 default serial port driver on those platforms as well.
1768 To prevent collisions with the sio(4) driver, the uart(4) driver
1769 uses different names for its device nodes. This means the
1770 onboard serial port will now most likely be called "ttyu0"
1771 instead of "ttyd0". You may need to reconfigure applications to
1772 use the new device names.
1774 When using the serial port as a boot console, be sure to update
1775 /boot/device.hints and /etc/ttys before booting the new kernel.
1776 If you forget to do so, you can still manually specify the hints
1777 at the loader prompt:
1779 set hint.uart.0.at="isa"
1780 set hint.uart.0.port="0x3F8"
1781 set hint.uart.0.flags="0x10"
1782 set hint.uart.0.irq="4"
1786 The gpt(8) utility has been removed. Use gpart(8) to partition
1790 The version that Linuxulator emulates was changed from 2.4.2
1791 to 2.6.16. If you experience any problems with Linux binaries
1792 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1793 if it fixes the problem contact emulation mailing list.
1796 ISDN4BSD (I4B) was removed from the src tree. You may need to
1797 update a your kernel configuration and remove relevant entries.
1800 I have checked in code to support multiple routing tables.
1801 See the man pages setfib(1) and setfib(2).
1802 This is a hopefully backwards compatible version,
1803 but to make use of it you need to compile your kernel
1804 with options ROUTETABLES=2 (or more up to 16).
1807 The 802.11 wireless support was redone to enable multi-bss
1808 operation on devices that are capable. The underlying device
1809 is no longer used directly but instead wlanX devices are
1810 cloned with ifconfig. This requires changes to rc.conf files.
1811 For example, change:
1812 ifconfig_ath0="WPA DHCP"
1815 ifconfig_wlan0="WPA DHCP"
1816 see rc.conf(5) for more details. In addition, mergemaster of
1817 /etc/rc.d is highly recommended. Simultaneous update of userland
1818 and kernel wouldn't hurt either.
1820 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1821 modules were merged into the base wlan module. All references
1822 to these modules (e.g. in kernel config files) must be removed.
1825 psm(4) has gained write(2) support in native operation level.
1826 Arbitrary commands can be written to /dev/psm%d and status can
1827 be read back from it. Therefore, an application is responsible
1828 for status validation and error recovery. It is a no-op in
1829 other operation levels.
1832 Support for KSE threading has been removed from the kernel. To
1833 run legacy applications linked against KSE libmap.conf may
1834 be used. The following libmap.conf may be used to ensure
1835 compatibility with any prior release:
1837 libpthread.so.1 libthr.so.1
1838 libpthread.so.2 libthr.so.2
1839 libkse.so.3 libthr.so.3
1842 The layout of struct vmspace has changed. This affects libkvm
1843 and any executables that link against libkvm and use the
1844 kvm_getprocs() function. In particular, but not exclusively,
1845 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1846 The effects are minimal, but it's advisable to upgrade world
1850 The latest em driver no longer has support in it for the
1851 82575 adapter, this is now moved to the igb driver. The
1852 split was done to make new features that are incompatible
1853 with older hardware easier to do.
1856 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1857 likewise the kernel option is now GEOM_LINUX_LVM.
1860 The default NFS mount mode has changed from UDP to TCP for
1861 increased reliability. If you rely on (insecurely) NFS
1862 mounting across a firewall you may need to update your
1866 Belatedly note the addition of m_collapse for compacting
1870 The fts(3) structures have been changed to use adequate
1871 integer types for their members and so to be able to cope
1872 with huge file trees. The old fts(3) ABI is preserved
1873 through symbol versioning in libc, so third-party binaries
1874 using fts(3) should still work, although they will not take
1875 advantage of the extended types. At the same time, some
1876 third-party software might fail to build after this change
1877 due to unportable assumptions made in its source code about
1878 fts(3) structure members. Such software should be fixed
1879 by its vendor or, in the worst case, in the ports tree.
1880 FreeBSD_version 800015 marks this change for the unlikely
1881 case that a portable fix is impossible.
1884 To upgrade to -current after this date, you must be running
1885 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1886 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1889 The ADAPTIVE_GIANT kernel option has been retired because its
1890 functionality is the default now.
1893 The AT keyboard emulation of sunkbd(4) has been turned on
1894 by default. In order to make the special symbols of the Sun
1895 keyboards driven by sunkbd(4) work under X these now have
1896 to be configured the same way as Sun USB keyboards driven
1897 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1899 Option "XkbLayout" "us"
1900 Option "XkbRules" "xorg"
1901 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1904 It has been decided that it is desirable to provide ABI
1905 backwards compatibility to the FreeBSD 4/5/6 versions of the
1906 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1907 broken with the introduction of PCI domain support (see the
1908 20070930 entry). Unfortunately, this required the ABI of
1909 PCIOCGETCONF to be broken again in order to be able to
1910 provide backwards compatibility to the old version of that
1911 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1912 again. As for prominent ports this affects neither pciutils
1913 nor xorg-server this time, the hal port needs to be rebuilt
1917 The misnamed kthread_create() and friends have been renamed
1918 to kproc_create() etc. Many of the callers already
1919 used kproc_start()..
1920 I will return kthread_create() and friends in a while
1921 with implementations that actually create threads, not procs.
1922 Renaming corresponds with version 800002.
1931 Avoid using make -j when upgrading. While generally safe, there are
1932 sometimes problems using -j to upgrade. If your upgrade fails with
1933 -j, please try again without -j. From time to time in the past there
1934 have been problems using -j with buildworld and/or installworld. This
1935 is especially true when upgrading between "distant" versions (eg one
1936 that cross a major release boundary or several minor releases, or when
1937 several months have passed on the -current branch).
1939 Sometimes, obscure build problems are the result of environment
1940 poisoning. This can happen because the make utility reads its
1941 environment when searching for values for global variables. To run
1942 your build attempts in an "environmental clean room", prefix all make
1943 commands with 'env -i '. See the env(1) manual page for more details.
1945 When upgrading from one major version to another it is generally best
1946 to upgrade to the latest code in the currently installed branch first,
1947 then do an upgrade to the new branch. This is the best-tested upgrade
1948 path, and has the highest probability of being successful. Please try
1949 this approach before reporting problems with a major version upgrade.
1951 When upgrading a live system, having a root shell around before
1952 installing anything can help undo problems. Not having a root shell
1953 around can lead to problems if pam has changed too much from your
1954 starting point to allow continued authentication after the upgrade.
1958 When upgrading the boot ZFS pool to a new version, always follow
1961 1.) recompile and reinstall the ZFS boot loader and boot block
1962 (this is part of "make buildworld" and "make installworld")
1964 2.) update the ZFS boot block on your boot drive
1966 The following example updates the ZFS boot block on the first
1967 partition (freebsd-boot) of a GPT partitioned drive ad0:
1968 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1970 Non-boot pools do not need these updates.
1974 If you are updating from a prior version of FreeBSD (even one just
1975 a few days old), you should follow this procedure. It is the most
1976 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1978 make kernel-toolchain
1979 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1980 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1982 To test a kernel once
1983 ---------------------
1984 If you just want to boot a kernel once (because you are not sure
1985 if it works, or if you want to boot a known bad kernel to provide
1986 debugging information) run
1987 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1988 nextboot -k testkernel
1990 To just build a kernel when you know that it won't mess you up
1991 --------------------------------------------------------------
1992 This assumes you are already running a CURRENT system. Replace
1993 ${arch} with the architecture of your machine (e.g. "i386",
1994 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1996 cd src/sys/${arch}/conf
1997 config KERNEL_NAME_HERE
1998 cd ../compile/KERNEL_NAME_HERE
2003 If this fails, go to the "To build a kernel" section.
2005 To rebuild everything and install it on the current system.
2006 -----------------------------------------------------------
2007 # Note: sometimes if you are running current you gotta do more than
2008 # is listed here if you are upgrading from a really old current.
2010 <make sure you have good level 0 dumps>
2012 make kernel KERNCONF=YOUR_KERNEL_HERE
2014 <reboot in single user> [3]
2021 To cross-install current onto a separate partition
2022 --------------------------------------------------
2023 # In this approach we use a separate partition to hold
2024 # current's root, 'usr', and 'var' directories. A partition
2025 # holding "/", "/usr" and "/var" should be about 2GB in
2028 <make sure you have good level 0 dumps>
2031 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2032 <maybe newfs current's root partition>
2033 <mount current's root partition on directory ${CURRENT_ROOT}>
2034 make installworld DESTDIR=${CURRENT_ROOT}
2035 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2036 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2037 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2038 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2039 <reboot into current>
2040 <do a "native" rebuild/install as described in the previous section>
2041 <maybe install compatibility libraries from ports/misc/compat*>
2045 To upgrade in-place from stable to current
2046 ----------------------------------------------
2047 <make sure you have good level 0 dumps>
2049 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2051 <reboot in single user> [3]
2058 Make sure that you've read the UPDATING file to understand the
2059 tweaks to various things you need. At this point in the life
2060 cycle of current, things change often and you are on your own
2061 to cope. The defaults can also change, so please read ALL of
2062 the UPDATING entries.
2064 Also, if you are tracking -current, you must be subscribed to
2065 freebsd-current@freebsd.org. Make sure that before you update
2066 your sources that you have read and understood all the recent
2067 messages there. If in doubt, please track -stable which has
2068 much fewer pitfalls.
2070 [1] If you have third party modules, such as vmware, you
2071 should disable them at this point so they don't crash your
2074 [3] From the bootblocks, boot -s, and then do
2079 adjkerntz -i # if CMOS is wall time
2080 Also, when doing a major release upgrade, it is required that
2081 you boot into single user mode to do the installworld.
2083 [4] Note: This step is non-optional. Failure to do this step
2084 can result in a significant reduction in the functionality of the
2085 system. Attempting to do it by hand is not recommended and those
2086 that pursue this avenue should read this file carefully, as well
2087 as the archives of freebsd-current and freebsd-hackers mailing lists
2088 for potential gotchas. The -U option is also useful to consider.
2089 See mergemaster(8) for more information.
2091 [5] Usually this step is a noop. However, from time to time
2092 you may need to do this if you get unknown user in the following
2093 step. It never hurts to do it all the time. You may need to
2094 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2095 install) after the buildworld before this step if you last updated
2096 from current before 20130425 or from -stable before 20130430.
2098 [6] This only deletes old files and directories. Old libraries
2099 can be deleted by "make delete-old-libs", but you have to make
2100 sure that no program is using those libraries anymore.
2102 [8] In order to have a kernel that can run the 4.x binaries needed to
2103 do an installworld, you must include the COMPAT_FREEBSD4 option in
2104 your kernel. Failure to do so may leave you with a system that is
2105 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2106 required to run the 5.x binaries on more recent kernels. And so on
2107 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2109 Make sure that you merge any new devices from GENERIC since the
2110 last time you updated your kernel config file.
2112 [9] When checking out sources, you must include the -P flag to have
2113 cvs prune empty directories.
2115 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2116 "?=" instead of the "=" assignment operator, so that buildworld can
2117 override the CPUTYPE if it needs to.
2119 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2120 not on the command line, or in /etc/make.conf. buildworld will
2121 warn if it is improperly defined.
2124 This file contains a list, in reverse chronological order, of major
2125 breakages in tracking -current. It is not guaranteed to be a complete
2126 list of such breakages, and only contains entries since October 10, 2007.
2127 If you need to see UPDATING entries from before that date, you will need
2128 to fetch an UPDATING file from an older FreeBSD release.
2130 Copyright information:
2132 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2134 Redistribution, publication, translation and use, with or without
2135 modification, in full or in part, in any form or format of this
2136 document are permitted without further permission from the author.
2138 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2139 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2140 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2141 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2142 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2143 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2144 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2145 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2146 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2147 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2148 POSSIBILITY OF SUCH DAMAGE.
2150 Contact Warner Losh if you have any questions about your use of