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.
23 The ofwfb driver, used to provide a graphics console on PowerPC when
24 using vt(4), no longer allows mmap() of all of physical memory. This
25 will prevent Xorg on PowerPC with some ATI graphics cards from
26 initializing properly unless x11-servers/xorg-server is updated to
30 The libatf-c and libatf-c++ major versions were downgraded to 0 and
31 1 respectively to match the upstream numbers. They were out of
32 sync because, when they were originally added to FreeBSD, the
33 upstream versions were not respected. These libraries are private
34 and not yet built by default, so renumbering them should be a
35 non-issue. However, unclean source trees will yield broken test
36 programs once the operator executes "make delete-old-libs" after a
39 Additionally, the atf-sh binary was made private by moving it into
40 /usr/libexec/. Already-built shell test programs will keep the
41 path to the old binary so they will break after "make delete-old"
44 If you are using WITH_TESTS=yes (not the default), wipe the object
45 tree and rebuild from scratch to prevent spurious test failures.
46 This is only needed once: the misnumbered libraries and misplaced
47 binaries have been added to OptionalObsoleteFiles.inc so they will
48 be removed during a clean upgrade.
51 The ixgbe tunables now match their sysctl counterparts, for example:
52 hw.ixgbe.enable_aim => hw.ix.enable_aim
53 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
56 The NFSv4.1 server committed by r269398 changes the internal
57 function call interfaces used between the NFS and krpc modules.
58 As such, __FreeBSD_version was bumped.
61 The default unbound configuration has been modified to address
62 issues with reverse lookups on networks that use private
63 address ranges. If you use the local_unbound service, run
64 "service local_unbound setup" as root to regenerate your
65 configuration, then "service local_unbound reload" to load the
69 It is no longer necessary to include the dwarf version in your DEBUG
70 options in your kernel config file. The bug that required it to be
71 placed in the config file has bene fixed. DEBUG should now just
72 contain -g. The build system will automatically update things
73 to do the right thing.
76 Several ABI breaking changes were merged to CTL and new iSCSI code.
77 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
78 iscsictl need to be rebuilt to work with a new kernel.
81 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
82 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
83 which differs from the behaviour controlled by this knob.)
86 On i386 and amd64 systems, the onifconsole flag is now set by default
87 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
88 as a login TTY if it is set in the bootloader as an active kernel
89 console. No changes in behavior should result otherwise. To revert to
90 the previous behavior, set ttyu0 to "off" in /etc/ttys.
93 Clang and llvm have been upgraded to 3.4.1 release.
96 Clang and llvm have been upgraded to 3.4 release.
99 If a Makefile in a tests/ directory was auto-generating a Kyuafile
100 instead of providing an explicit one, this would prevent such
101 Makefile from providing its own Kyuafile in the future during
102 NO_CLEAN builds. This has been fixed in the Makefiles but manual
103 intervention is needed to clean an objdir if you use NO_CLEAN:
104 # find /usr/obj -name Kyuafile | xargs rm -f
107 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
108 capability mode support. Please note that enabling the feature in
109 kernel is still highly recommended.
112 OpenSSH is now built with sandbox support, and will use sandbox as
113 the default privilege separation method. This requires Capsicum
114 capability mode support in kernel.
117 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
118 been deprecated and will not be part of FreeBSD 11.0 and later
119 releases. If you use this driver, please consider switching to
120 the nfe(4) driver instead.
126 The behavior of gss_pseudo_random() for the krb5 mechanism
127 has changed, for applications requesting a longer random string
128 than produced by the underlying enctype's pseudo-random() function.
129 In particular, the random string produced from a session key of
130 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
131 be different at the 17th octet and later, after this change.
132 The counter used in the PRF+ construction is now encoded as a
133 big-endian integer in accordance with RFC 4402.
134 __FreeBSD_version is bumped to 1000701.
137 The WITHOUT_ATF build knob has been removed and its functionality
138 has been subsumed into the more generic WITHOUT_TESTS. If you were
139 using the former to disable the build of the ATF libraries, you
140 should change your settings to use the latter.
143 The default version of mtree is nmtree which is obtained from
144 NetBSD. The output is generally the same, but may vary
145 slightly. If you found you need identical output adding
146 "-F freebsd9" to the command line should do the trick. For the
147 time being, the old mtree is available as fmtree.
150 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
151 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
152 1.1.4_8 and verify bsdyml not linked in, before running "make
154 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
156 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
159 The rc.d/jail script has been updated to support jail(8)
160 configuration file. The "jail_<jname>_*" rc.conf(5) variables
161 for per-jail configuration are automatically converted to
162 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
163 This is transparently backward compatible. See below about some
164 incompatibilities and rc.conf(5) manual page for more details.
166 These variables are now deprecated in favor of jail(8) configuration
167 file. One can use "rc.d/jail config <jname>" command to generate
168 a jail(8) configuration file in /var/run/jail.<jname>.conf without
169 running the jail(8) utility. The default pathname of the
170 configuration file is /etc/jail.conf and can be specified by
171 using $jail_conf or $jail_<jname>_conf variables.
173 Please note that jail_devfs_ruleset accepts an integer at
174 this moment. Please consider to rewrite the ruleset name
178 BIND has been removed from the base system. If all you need
179 is a local resolver, simply enable and start the local_unbound
180 service instead. Otherwise, several versions of BIND are
181 available in the ports tree. The dns/bind99 port is one example.
183 With this change, nslookup(1) and dig(1) are no longer in the base
184 system. Users should instead use host(1) and drill(1) which are
185 in the base system. Alternatively, nslookup and dig can
186 be obtained by installing the dns/bind-tools port.
189 With the addition of unbound(8), a new unbound user is now
190 required during installworld. "mergemaster -p" can be used to
191 add the user prior to installworld, as documented in the handbook.
194 OpenSSH is now built with DNSSEC support, and will by default
195 silently trust signed SSHFP records. This can be controlled with
196 the VerifyHostKeyDNS client configuration setting. DNSSEC support
197 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
200 The GNU Compiler Collection and C++ standard library (libstdc++)
201 are no longer built by default on platforms where clang is the system
202 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
206 The PROCDESC kernel option is now part of the GENERIC kernel
207 configuration and is required for the rwhod(8) to work.
208 If you are using custom kernel configuration, you should include
212 The API and ABI related to the Capsicum framework was modified
213 in backward incompatible way. The userland libraries and programs
214 have to be recompiled to work with the new kernel. This includes the
215 following libraries and programs, but the whole buildworld is
216 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
217 kdump, procstat, rwho, rwhod, uniq.
220 AES-NI intrinsic support has been added to gcc. The AES-NI module
221 has been updated to use this support. A new gcc is required to build
222 the aesni module on both i386 and amd64.
225 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
226 Thus "device padlock_rng" and "device rdrand_rng" should be
227 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
230 WITH_ICONV has been split into two feature sets. WITH_ICONV now
231 enables just the iconv* functionality and is now on by default.
232 WITH_LIBICONV_COMPAT enables the libiconv api and link time
233 compatability. Set WITHOUT_ICONV to build the old way.
234 If you have been using WITH_ICONV before, you will very likely
235 need to turn on WITH_LIBICONV_COMPAT.
238 INVARIANTS option now enables DEBUG for code with OpenSolaris and
239 Illumos origin, including ZFS. If you have INVARIANTS in your
240 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
242 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
243 locks if WITNESS option was set. Because that generated a lot of
244 witness(9) reports and all of them were believed to be false
245 positives, this is no longer done. New option OPENSOLARIS_WITNESS
246 can be used to achieve the previous behavior.
249 Timer values in IPv6 data structures now use time_uptime instead
250 of time_second. Although this is not a user-visible functional
251 change, userland utilities which directly use them---ndp(8),
252 rtadvd(8), and rtsold(8) in the base system---need to be updated
256 find -delete can now delete the pathnames given as arguments,
257 instead of only files found below them or if the pathname did
258 not contain any slashes. Formerly, the following error message
261 find: -delete: <path>: relative path potentially not safe
263 Deleting the pathnames given as arguments can be prevented
264 without error messages using -mindepth 1 or by changing
265 directory and passing "." as argument to find. This works in the
266 old as well as the new version of find.
269 Behavior of devfs rules path matching has been changed.
270 Pattern is now always matched against fully qualified devfs
271 path and slash characters must be explicitly matched by
272 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
273 subdirectories must be reviewed.
276 The default ARM ABI has changed to the ARM EABI. The old ABI is
277 incompatible with the ARM EABI and all programs and modules will
278 need to be rebuilt to work with a new kernel.
280 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
282 NOTE: Support for the old ABI will be removed in the future and
283 users are advised to upgrade.
286 pkg_install has been disconnected from the build if you really need it
287 you should add WITH_PKGTOOLS in your src.conf(5).
290 Most of network statistics structures were changed to be able
291 keep 64-bits counters. Thus all tools, that work with networking
292 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
295 Fix targets that run multiple make's to use && rather than ;
296 so that subsequent steps depend on success of previous.
298 NOTE: if building 'universe' with -j* on stable/8 or stable/9
299 it would be better to start the build using bmake, to avoid
300 overloading the machine.
303 Fix a bug that allowed a tracing process (e.g. gdb) to write
304 to a memory-mapped file in the traced process's address space
305 even if neither the traced process nor the tracing process had
306 write access to that file.
309 CVS has been removed from the base system. An exact copy
310 of the code is available from the devel/cvs port.
313 Some people report the following error after the switch to bmake:
315 make: illegal option -- J
316 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
318 *** [buildworld] Error code 2
320 this likely due to an old instance of make in
321 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
322 which src/Makefile will use that blindly, if it exists, so if
323 you see the above error:
325 rm -rf `make -V MAKEPATH`
330 Use bmake by default.
331 Whereas before one could choose to build with bmake via
332 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
333 make. The goal is to remove these knobs for 10-RELEASE.
335 It is worth noting that bmake (like gmake) treats the command
336 line as the unit of failure, rather than statements within the
337 command line. Thus '(cd some/where && dosomething)' is safer
338 than 'cd some/where; dosomething'. The '()' allows consistent
339 behavior in parallel build.
342 Fix a bug that allows NFS clients to issue READDIR on files.
345 The WITHOUT_IDEA option has been removed because
346 the IDEA patent expired.
349 The sysctl which controls TRIM support under ZFS has been renamed
350 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
354 The mergemaster command now uses the default MAKEOBJDIRPREFIX
355 rather than creating it's own in the temporary directory in
356 order allow access to bootstrapped versions of tools such as
357 install and mtree. When upgrading from version of FreeBSD where
358 the install command does not support -l, you will need to
359 install a new mergemaster command if mergemaster -p is required.
360 This can be accomplished with the command (cd src/usr.sbin/mergemaster
364 Legacy ATA stack, disabled and replaced by new CAM-based one since
365 FreeBSD 9.0, completely removed from the sources. Kernel modules
366 atadisk and atapi*, user-level tools atacontrol and burncd are
367 removed. Kernel option `options ATA_CAM` is now permanently enabled
371 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
372 and socketpair(2). Software, in particular Kerberos, may
373 automatically detect and use these during building. The resulting
374 binaries will not work on older kernels.
377 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
378 information, see the respective 20130304 entry).
381 Recent commits to callout(9) changed the size of struct callout,
382 so the KBI is probably heavily disturbed. Also, some functions
383 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
384 by macros. Every kernel module using it won't load, so rebuild
387 The ctl device has been re-enabled in GENERIC for i386 and amd64,
388 but does not initialize by default (because of the new CTL_DISABLE
389 option) to save memory. To re-enable it, remove the CTL_DISABLE
390 option from the kernel config file or set kern.cam.ctl.disable=0
391 in /boot/loader.conf.
394 The ctl device has been disabled in GENERIC for i386 and amd64.
395 This was done due to the extra memory being allocated at system
396 initialisation time by the ctl driver which was only used if
397 a CAM target device was created. This makes a FreeBSD system
398 unusable on 128MB or less of RAM.
401 A new compression method (lz4) has been merged to -HEAD. Please
402 refer to zpool-features(7) for more information.
404 Please refer to the "ZFS notes" section of this file for information
405 on upgrading boot ZFS pools.
408 A BSD-licensed patch(1) variant has been added and is installed
409 as bsdpatch, being the GNU version the default patch.
410 To inverse the logic and use the BSD-licensed one as default,
411 while having the GNU version installed as gnupatch, rebuild
412 and install world with the WITH_BSD_PATCH knob set.
415 Due to the use of the new -l option to install(1) during build
416 and install, you must take care not to directly set the INSTALL
417 make variable in your /etc/make.conf, /etc/src.conf, or on the
418 command line. If you wish to use the -C flag for all installs
419 you may be able to add INSTALL+=-C to /etc/make.conf or
423 The install(1) option -M has changed meaning and now takes an
424 argument that is a file or path to append logs to. In the
425 unlikely event that -M was the last option on the command line
426 and the command line contained at least two files and a target
427 directory the first file will have logs appended to it. The -M
428 option served little practical purpose in the last decade so its
429 use is expected to be extremely rare.
432 After switching to Clang as the default compiler some users of ZFS
433 on i386 systems started to experience stack overflow kernel panics.
434 Please consider using 'options KSTACK_PAGES=4' in such configurations.
437 GEOM_LABEL now mangles label names read from file system metadata.
438 Mangling affect labels containing spaces, non-printable characters,
439 '%' or '"'. Device names in /etc/fstab and other places may need to
443 By default, only the 10 most recent kernel dumps will be saved. To
444 restore the previous behaviour (no limit on the number of kernel dumps
445 stored in the dump directory) add the following line to /etc/rc.conf:
450 With the addition of auditdistd(8), a new auditdistd user is now
451 required during installworld. "mergemaster -p" can be used to
452 add the user prior to installworld, as documented in the handbook.
455 The sin6_scope_id member variable in struct sockaddr_in6 is now
456 filled by the kernel before passing the structure to the userland via
457 sysctl or routing socket. This means the KAME-specific embedded scope
458 id in sin6_addr.s6_addr[2] is always cleared in userland application.
459 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
460 __FreeBSD_version is bumped to 1000025.
463 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
464 This means that the world and kernel will be compiled with clang
465 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
466 and /usr/bin/cpp. To disable this behavior and revert to building
467 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
468 of current may need to bootstrap WITHOUT_CLANG first if the clang
469 build fails (its compatibility window doesn't extend to the 9 stable
473 The IPFIREWALL_FORWARD kernel option has been removed. Its
474 functionality now turned on by default.
477 The ZERO_COPY_SOCKET kernel option has been removed and
478 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
479 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
480 mechanism which is not safe and may result in kernel crashes.
481 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
482 driver supports disposeable external page sized mbuf storage.
483 Proper replacements for both zero-copy mechanisms are under
484 consideration and will eventually lead to complete removal
485 of the two kernel options.
488 The IPv4 network stack has been converted to network byte
489 order. The following modules need to be recompiled together
490 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
491 pf(4), ipfw(4), ng_ipfw(4), stf(4).
494 Support for non-MPSAFE filesystems was removed from VFS. The
495 VFS_VERSION was bumped, all filesystem modules shall be
499 All the non-MPSAFE filesystems have been disconnected from
500 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
501 portalfs, smbfs, xfs.
504 The interface cloning API and ABI has changed. The following
505 modules need to be recompiled together with kernel:
506 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
507 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
508 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
511 The sdhci driver was split in two parts: sdhci (generic SD Host
512 Controller logic) and sdhci_pci (actual hardware driver).
513 No kernel config modifications are required, but if you
514 load sdhc as a module you must switch to sdhci_pci instead.
517 Import the FUSE kernel and userland support into base system.
520 The GNU sort(1) program has been removed since the BSD-licensed
521 sort(1) has been the default for quite some time and no serious
522 problems have been reported. The corresponding WITH_GNU_SORT
526 The pfil(9) API/ABI for AF_INET family has been changed. Packet
527 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
531 The net80211(4) ABI has been changed to allow for improved driver
532 PS-POLL and power-save support. All wireless drivers need to be
533 recompiled to work with the new kernel.
536 The random(4) support for the VIA hardware random number
537 generator (`PADLOCK') is no longer enabled unconditionally.
538 Add the padlock_rng device in the custom kernel config if
539 needed. The GENERIC kernels on i386 and amd64 do include the
540 device, so the change only affects the custom kernel
544 The pf(4) packet filter ABI has been changed. pfctl(8) and
545 snmp_pf module need to be recompiled to work with new kernel.
548 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
549 to -HEAD. Pools that have empty_bpobj in active state can not be
550 imported read-write with ZFS implementations that do not support
551 this feature. For more information read the zpool-features(5)
555 The sparc64 ZFS loader has been changed to no longer try to auto-
556 detect ZFS providers based on diskN aliases but now requires these
557 to be explicitly listed in the OFW boot-device environment variable.
560 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
561 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
562 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
565 The following sysctls and tunables have been renamed for consistency
566 with other variables:
567 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
568 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
571 The sort utility has been replaced with BSD sort. For now, GNU sort
572 is also available as "gnusort" or the default can be set back to
573 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
574 installed as "bsdsort".
577 A new version of ZFS (pool version 5000) has been merged to -HEAD.
578 Starting with this version the old system of ZFS pool versioning
579 is superseded by "feature flags". This concept enables forward
580 compatibility against certain future changes in functionality of ZFS
581 pools. The first read-only compatible "feature flag" for ZFS pools
582 is named "com.delphix:async_destroy". For more information
583 read the new zpool-features(5) manual page.
584 Please refer to the "ZFS notes" section of this file for information
585 on upgrading boot ZFS pools.
588 The malloc(3) implementation embedded in libc now uses sources imported
589 as contrib/jemalloc. The most disruptive API change is to
590 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
591 delete it prior to installworld, and optionally re-create it using the
592 new format after rebooting. See malloc.conf(5) for details
593 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
597 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
598 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
599 now spelled mips. This is to aid compatibility with third-party
600 software that expects this naming scheme in uname(3). Little-endian
601 settings are unchanged. If you are updating a big-endian mips64 machine
602 from before this change, you may need to set MACHINE_ARCH=mips64 in
603 your environment before the new build system will recognize your machine.
606 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
610 Now unix domain sockets behave "as expected" on nullfs(5). Previously
611 nullfs(5) did not pass through all behaviours to the underlying layer,
612 as a result if we bound to a socket on the lower layer we could connect
613 only to the lower path; if we bound to the upper layer we could connect
614 only to the upper path. The new behavior is one can connect to both the
615 lower and the upper paths regardless what layer path one binds to.
618 The getifaddrs upgrade path broken with 20111215 has been restored.
619 If you have upgraded in between 20111215 and 20120209 you need to
620 recompile libc again with your kernel. You still need to recompile
621 world to be able to configure CARP but this restriction already
625 The set_rcvar() function has been removed from /etc/rc.subr. All
626 base and ports rc.d scripts have been updated, so if you have a
627 port installed with a script in /usr/local/etc/rc.d you can either
628 hand-edit the rcvar= line, or reinstall the port.
630 An easy way to handle the mass-update of /etc/rc.d:
631 rm /etc/rc.d/* && mergemaster -i
634 panic(9) now stops other CPUs in the SMP systems, disables interrupts
635 on the current CPU and prevents other threads from running.
636 This behavior can be reverted using the kern.stop_scheduler_on_panic
638 The new behavior can be incompatible with kern.sync_on_panic.
641 The carp(4) facility has been changed significantly. Configuration
642 of the CARP protocol via ifconfig(8) has changed, as well as format
643 of CARP events submitted to devd(8) has changed. See manual pages
644 for more information. The arpbalance feature of carp(4) is currently
645 not supported anymore.
647 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
648 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
649 need to be recompiled.
652 The acpi_wmi(4) status device /dev/wmistat has been renamed to
656 The option VFS_ALLOW_NONMPSAFE option has been added in order to
657 explicitely support non-MPSAFE filesystems.
658 It is on by default for all supported platform at this present
662 The broken amd(4) driver has been replaced with esp(4) in the amd64,
663 i386 and pc98 GENERIC kernel configuration files.
666 sysinstall has been removed
669 The stable/9 branch created in subversion. This corresponds to the
670 RELENG_9 branch in CVS.
673 This commit modifies vfs_register() so that it uses a hash
674 calculation to set vfc_typenum, which is enabled by default.
675 The first time a system is booted after this change, the
676 vfc_typenum values will change for all file systems. The
677 main effect of this is a change to the NFS server file handles
678 for file systems that use vfc_typenum in their fsid, such as ZFS.
679 It will, however, prevent vfc_typenum from changing when file
680 systems are loaded in a different order for subsequent reboots.
681 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
682 until you are ready to remount all NFS clients after a reboot.
685 Bump the shared library version numbers for libraries that
686 do not use symbol versioning, have changed the ABI compared
687 to stable/8 and which shared library version was not bumped.
688 Done as part of 9.0-RELEASE cycle.
691 During the merge of Capsicum features, the fget(9) KPI was modified.
692 This may require the rebuilding of out-of-tree device drivers --
693 issues have been reported specifically with the nVidia device driver.
694 __FreeBSD_version is bumped to 900041.
696 Also, there is a period between 20110811 and 20110814 where the
697 special devices /dev/{stdin,stdout,stderr} did not work correctly.
698 Building world from a kernel during that window may not work.
701 The packet filter (pf) code has been updated to OpenBSD 4.5.
702 You need to update userland tools to be in sync with kernel.
703 This update breaks backward compatibility with earlier pfsync(4)
704 versions. Care must be taken when updating redundant firewall setups.
707 The following sysctls and tunables are retired on x86 platforms:
709 machdep.hlt_logical_cpus
710 The following sysctl is retired:
711 machdep.hyperthreading_allowed
712 The sysctls were supposed to provide a way to dynamically offline and
713 online selected CPUs on x86 platforms, but the implementation has not
714 been reliable especially with SCHED_ULE scheduler.
715 machdep.hyperthreading_allowed tunable is still available to ignore
716 hyperthreading CPUs at OS level.
717 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
718 where X is an APIC ID of a CPU. Be advised, though, that disabling
719 CPUs in non-uniform fashion will result in non-uniform topology and
720 may lead to sub-optimal system performance with SCHED_ULE, which is
724 cpumask_t type is retired and cpuset_t is used in order to describe
728 Changes to ifconfig(8) for dynamic address family detection mandate
729 that you are running a kernel of 20110525 or later. Make sure to
730 follow the update procedure to boot a new kernel before installing
734 Support for sun4v architecture is officially dropped
737 Several KPI breaking changes have been committed to the mii(4) layer,
738 the PHY drivers and consequently some Ethernet drivers using mii(4).
739 This means that miibus.ko and the modules of the affected Ethernet
740 drivers need to be recompiled.
742 Note to kernel developers: Given that the OUI bit reversion problem
743 was fixed as part of these changes all mii(4) commits related to OUIs,
744 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
745 handling, no longer can be merged verbatim to stable/8 and previous
749 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
750 into their kernel configurations along with 'device pci'.
753 The default NFS client is now the new NFS client, so fstype "newnfs"
754 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
755 Although mounts via fstype "nfs" will usually work without userland
756 changes, it is recommended that the mount(8) and mount_nfs(8)
757 commands be rebuilt from sources and that a link to mount_nfs called
758 mount_oldnfs be created. The new client is compiled into the
759 kernel with "options NFSCL" and this is needed for diskless root
760 file systems. The GENERIC kernel configs have been changed to use
761 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
762 To use the regular/old client, you can "mount -t oldnfs ...". For
763 a diskless root file system, you must also include a line like:
765 vfs.root.mountfrom="oldnfs:"
767 in the boot/loader.conf on the root fs on the NFS server to make
768 a diskless root fs use the old client.
771 The GENERIC kernels for all architectures now default to the new
772 CAM-based ATA stack. It means that all legacy ATA drivers were
773 removed and replaced by respective CAM drivers. If you are using
774 ATA device names in /etc/fstab or other places, make sure to update
775 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
776 where 'Y's are the sequential numbers starting from zero for each type
777 in order of detection, unless configured otherwise with tunables,
778 see cam(4)). There will be symbolic links created in /dev/ to map
779 old adX devices to the respective adaY. They should provide basic
780 compatibility for file systems mounting in most cases, but they do
781 not support old user-level APIs and do not have respective providers
782 in GEOM. Consider using updated management tools with new device names.
784 It is possible to load devices ahci, ata, siis and mvs as modules,
785 but option ATA_CAM should remain in kernel configuration to make ata
786 module work as CAM driver supporting legacy ATA controllers. Device ata
787 still can be used in modular fashion (atacore + ...). Modules atadisk
788 and atapi* are not used and won't affect operation in ATA_CAM mode.
789 Note that to use CAM-based ATA kernel should include CAM devices
790 scbus, pass, da (or explicitly ada), cd and optionally others. All of
791 them are parts of the cam module.
793 ataraid(4) functionality is now supported by the RAID GEOM class.
794 To use it you can load geom_raid kernel module and use graid(8) tool
795 for management. Instead of /dev/arX device names, use /dev/raid/rX.
797 No kernel config options or code have been removed, so if a problem
798 arises, please report it and optionally revert to the old ATA stack.
799 In order to do it you can remove from the kernel config:
804 , and instead add back:
805 device atadisk # ATA disk drives
806 device ataraid # ATA RAID drives
807 device atapicd # ATAPI CDROM drives
808 device atapifd # ATAPI floppy drives
809 device atapist # ATAPI tape drives
812 The default NFS server has been changed to the new server, which
813 was referred to as the experimental server. If you need to switch
814 back to the old NFS server, you must now put the "-o" option on
815 both the mountd and nfsd commands. This can be done using the
816 mountd_flags and nfs_server_flags rc.conf variables until an
817 update to the rc scripts is committed, which is coming soon.
820 The GNU Objective-C runtime library (libobjc), and other Objective-C
821 related components have been removed from the base system. If you
822 require an Objective-C library, please use one of the available ports.
825 ath(4) has been split into bus- and device- modules. if_ath contains
826 the HAL, the TX rate control and the network device code. if_ath_pci
827 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
828 contains the AHB glue. Users need to load both if_ath_pci and if_ath
829 in order to use ath on everything else.
831 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
832 need to load if_ath and if_ath_pci for ath(4) operation.
835 As part of the replacement of sysinstall, the process of building
836 release media has changed significantly. For details, please re-read
837 release(7), which has been updated to reflect the new build process.
840 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
841 is the last available version under GPLv2. It brings a number of new
842 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
843 4.1 and SSE 4.2), better support for powerpc64, a number of new
844 directives, and lots of other small improvements. See the ChangeLog
845 file in contrib/binutils for the full details.
848 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
849 compliant, and will now use half of hash for authentication.
850 This will break interoperability with all stacks (including all
851 actual FreeBSD versions) who implement
852 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
854 The only workaround with such peers is to use another HMAC
855 algorithm for IPsec ("phase 2") authentication.
858 Remove the uio_yield prototype and symbol. This function has
859 been misnamed since it was introduced and should not be
860 globally exposed with this name. The equivalent functionality
861 is now available using kern_yield(curthread->td_user_pri).
862 The function remains undocumented.
865 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
866 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
867 for scalar sysctls is defined but disabled. Code that needs
868 UQUAD to pass the type checking that must compile on older
869 systems where the define is not present can check against
870 __FreeBSD_version >= 900030.
872 The system dialog(1) has been replaced with a new version previously
873 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
874 with the previous version, but the libdialog associated with it has
875 a largely incompatible API. As such, the original version of libdialog
876 will be kept temporarily as libodialog, until its base system consumers
877 are replaced or updated. Bump __FreeBSD_version to 900030.
880 If you are trying to run make universe on a -stable system, and you get
881 the following warning:
882 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
883 unknown. config(8) likely too old."
884 or something similar to it, then you must upgrade your -stable system
885 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
886 stable/8) or build the config from the latest stable/8 branch and
887 install it on your system.
889 Prior to this date, building a current universe on 8-stable system from
890 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
891 error in the first kernel build phase. A new config on those old
892 systems will fix that problem for older versions of -current.
895 The TCP stack has been modified to allow Khelp modules to interact with
896 it via helper hook points and store per-connection data in the TCP
897 control block. Bump __FreeBSD_version to 900029. User space tools that
898 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
902 Generic IEEE 802.3 annex 31B full duplex flow control support has been
903 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
904 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
905 to take advantage of it instead of using custom implementations. This
906 means that these drivers now no longer unconditionally advertise
907 support for flow control but only do so if flow control is a selected
908 media option. This was implemented in the generic support that way in
909 order to allow flow control to be switched on and off via ifconfig(8)
910 with the PHY specific default to typically off in order to protect
911 from unwanted effects. Consequently, if you used flow control with
912 one of the above mentioned drivers you now need to explicitly enable
914 ifconfig bge0 media auto mediaopt flowcontrol
916 Along with the above mentioned changes generic support for setting
917 1000baseT master mode also has been added and brgphy(4), ciphy(4),
918 e1000phy(4) as well as ip1000phy(4) have been converted to take
919 advantage of it. This means that these drivers now no longer take the
920 link0 parameter for selecting master mode but the master media option
921 has to be used instead, for example like in the following:
922 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
924 Selection of master mode now is also available with all other PHY
925 drivers supporting 1000baseT.
928 The TCP stack has received a significant update to add support for
929 modularised congestion control and generally improve the clarity of
930 congestion control decisions. Bump __FreeBSD_version to 900025. User
931 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
932 sockstat) need to be recompiled.
935 The man(1) utility has been replaced by a new version that no longer
936 uses /etc/manpath.config. Please consult man.conf(5) for how to
937 migrate local entries to the new format.
940 The copyright strings printed by login(1) and sshd(8) at the time of a
941 new connection have been removed to follow other operating systems and
945 A workaround for a fixed ld bug has been removed in kernel code,
946 so make sure that your system ld is built from sources after
947 revision 210245 from 2010-07-19 (r211583 if building head kernel
948 on stable/8, r211584 for stable/7; both from 2010-08-21).
949 A symptom of incorrect ld version is different addresses for
950 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
953 The $ipv6_prefer variable in rc.conf(5) has been split into
954 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
956 The $ip6addrctl_policy is a variable to choose a pre-defined
957 address selection policy set by ip6addrctl(8). A value
958 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
961 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
962 flag (see an entry of 20090926) is set on an interface with no
963 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
964 security reason. If you want IPv6 link-local address on all
965 interfaces by default, set this to "YES".
967 The old ipv6_prefer="YES" is equivalent to
968 ipv6_activate_all_interfaces="YES" and
969 ip6addrctl_policy="ipv6_prefer".
972 DTrace has grown support for userland tracing. Due to this, DTrace is
973 now i386 and amd64 only.
974 dtruss(1) is now installed by default on those systems and a new
975 kernel module is needed for userland tracing: fasttrap.
976 No changes to your kernel config file are necessary to enable
977 userland tracing, but you might consider adding 'STRIP=' and
978 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
979 to have informative userland stack traces in DTrace (ustack).
982 The acpi_aiboost(4) driver has been removed in favor of the new
983 aibs(4) driver. You should update your kernel configuration file.
986 BSD grep has been imported to the base system and it is built by
987 default. It is completely BSD licensed, highly GNU-compatible, uses
988 less memory than its GNU counterpart and has a small codebase.
989 However, it is slower than its GNU counterpart, which is mostly
990 noticeable for larger searches, for smaller ones it is measurable
991 but not significant. The reason is complex, the most important factor
992 is that we lack a modern and efficient regex library and GNU
993 overcomes this by optimizing the searches internally. Future work
994 on improving the regex performance is planned, for the meantime,
995 users that need better performance, can build GNU grep instead by
996 setting the WITH_GNU_GREP knob.
999 Due to the import of powerpc64 support, all existing powerpc kernel
1000 configuration files must be updated with a machine directive like this:
1001 machine powerpc powerpc
1003 In addition, an updated config(8) is required to build powerpc kernels
1007 A new version of ZFS (version 15) has been merged to -HEAD.
1008 This version uses a python library for the following subcommands:
1009 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1010 For full functionality of these commands the following port must
1011 be installed: sysutils/py-zfs
1014 'vm_page's are now hashed by physical address to an array of mutexes.
1015 Currently this is only used to serialize access to hold_count. Over
1016 time the page queue mutex will be peeled away. This changes the size
1017 of pmap on every architecture. And requires all callers of vm_page_hold
1018 and vm_page_unhold to be updated.
1021 WITH_CTF can now be specified in src.conf (not recommended, there
1022 are some problems with static executables), make.conf (would also
1023 affect ports which do not use GNU make and do not override the
1024 compile targets) or in the kernel config (via "makeoptions
1026 When WITH_CTF was specified there before this was silently ignored,
1027 so make sure that WITH_CTF is not used in places which could lead
1028 to unwanted behavior.
1031 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1032 to allow 32-bit compatibility on non-x86 platforms. All kernel
1033 configurations on amd64 and ia64 platforms using these options must
1034 be modified accordingly.
1037 The utmp user accounting database has been replaced with utmpx,
1038 the user accounting interface standardized by POSIX.
1039 Unfortunately the semantics of utmp and utmpx don't match,
1040 making it practically impossible to support both interfaces.
1041 The user accounting database is used by tools like finger(1),
1042 last(1), talk(1), w(1) and ac(8).
1044 All applications in the base system use utmpx. This means only
1045 local binaries (e.g. from the ports tree) may still use these
1046 utmp database files. These applications must be rebuilt to make
1049 After the system has been upgraded, it is safe to remove the old
1050 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1051 assuming their contents is of no importance anymore. Old wtmp
1052 databases can only be used by last(1) and ac(8) after they have
1053 been converted to the new format using wtmpcvt(1).
1056 Introduce the kernel thread "deadlock resolver" (which can be enabled
1057 via the DEADLKRES option, see NOTES for more details) and the
1058 sleepq_type() function for sleepqueues.
1061 The rc.firewall and rc.firewall6 were unified, and
1062 rc.firewall6 and rc.d/ip6fw were removed.
1063 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1064 variables are obsoleted. Instead, the following new rc
1065 variables are added to rc.d/ipfw:
1067 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1068 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1069 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1071 The meanings correspond to the relevant IPv4 variables.
1077 The default terminal emulation for syscons(4) has been changed
1078 from cons25 to xterm on all platforms except pc98. This means
1079 that the /etc/ttys file needs to be updated to ensure correct
1080 operation of applications on the console.
1082 The terminal emulation style can be toggled per window by using
1083 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1084 options can be used to change the compile-time default back to
1087 To prevent graphical artifacts, make sure the TERM environment
1088 variable is set to match the terminal emulation that is being
1089 performed by syscons(4).
1092 The layout of the structure ieee80211req_scan_result has changed.
1093 Applications that require wireless scan results (e.g. ifconfig(8))
1094 from net80211 need to be recompiled.
1096 Applications such as wpa_supplicant(8) may require a full world
1097 build without using NO_CLEAN in order to get synchronized with the
1101 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1102 There's one kernel module for each firmware. Adding "device iwnfw"
1103 to the kernel configuration file means including all three firmware
1104 images inside the kernel. If you want to include just the one for
1105 your wireless card, use the devices iwn4965fw, iwn5000fw or
1109 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1110 into rc.d/netif. The changes are the following:
1112 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1113 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1114 Note that both variables need the "inet6" keyword at the head.
1116 Do not set $ipv6_network_interfaces manually if you do not
1117 understand what you are doing. It is not needed in most cases.
1119 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1122 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1123 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1125 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1126 all configured interfaces have "inet6 accept_rtadv" in the
1127 $ifconfig_IF_ipv6. These are for backward compatibility.
1129 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1130 functionality of interfaces with no corresponding
1131 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1132 and the default address selection policy of ip6addrctl(8)
1133 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1134 Note that if you want to configure IPv6 functionality on the
1135 disabled interfaces after boot, first you need to clear the flag by
1136 using ifconfig(8) like:
1138 ifconfig em0 inet6 -ifdisabled
1140 If YES, the default address selection policy is set as
1143 The default value of $ipv6_prefer is NO.
1145 4. If your system need to receive Router Advertisement messages,
1146 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1147 scripts automatically invoke rtsol(8) when the interface becomes
1148 UP. The Router Advertisement messages are used for SLAAC
1149 (State-Less Address AutoConfiguration).
1152 802.11s D3.03 support was committed. This is incompatible with the
1153 previous code, which was based on D3.0.
1156 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1157 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1158 control whether accepting Router Advertisement messages or not.
1159 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1160 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1161 The ifconfig(8) utility now supports these flags.
1164 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1165 mount(8) and -a option for df(1) to see them.
1168 The old tunable hw.bus.devctl_disable has been superseded by
1169 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1170 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1174 Remove the option STOP_NMI. The default action is now to use NMI only
1175 for KDB via the newly introduced function stop_cpus_hard() and
1176 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1179 The stable/8 branch created in subversion. This corresponds to the
1180 RELENG_8 branch in CVS.
1183 Bump the shared library version numbers for all libraries that do not
1184 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1185 __FreeBSD_version to 800105.
1188 Due to changes in the implementation of virtual network stack support,
1189 all network-related kernel modules must be recompiled. As this change
1190 breaks the ABI, bump __FreeBSD_version to 800104.
1193 The TOE interface to the TCP syncache has been modified to remove
1194 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1195 The cxgb driver is the only TOE consumer affected by this change, and
1196 needs to be recompiled along with the kernel. As this change breaks
1197 the ABI, bump __FreeBSD_version to 800103.
1200 Padding has been added to struct tcpcb, sackhint and tcpstat in
1201 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1202 maintaining the ABI. However, this change breaks the ABI, so bump
1203 __FreeBSD_version to 800102. User space tools that rely on the size of
1204 any of these structs (e.g. sockstat) need to be recompiled.
1207 The NFS_LEGACYRPC option has been removed along with the old kernel
1208 RPC implementation that this option selected. Kernel configurations
1209 may need to be adjusted.
1212 The network interface device nodes at /dev/net/<interface> have been
1213 removed. All ioctl operations can be performed the normal way using
1214 routing sockets. The kqueue functionality can generally be replaced
1215 with routing sockets.
1218 The documentation from the FreeBSD Documentation Project (Handbook,
1219 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1220 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1223 The ABI of various structures related to the SYSV IPC API have been
1224 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1225 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1229 Layout of struct vnet has changed as routing related variables were
1230 moved to their own Vimage module. Modules need to be recompiled. Bump
1231 __FreeBSD_version to 800099.
1234 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1235 respectively. As long as no more than 16 groups per process are used,
1236 no changes should be visible. When more than 16 groups are used, old
1237 binaries may fail if they call getgroups() or getgrouplist() with
1238 statically sized storage. Recompiling will work around this, but
1239 applications should be modified to use dynamically allocated storage
1240 for group arrays as POSIX.1-2008 does not cap an implementation's
1241 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1243 NFS and portalfs mounts may also be affected as the list of groups is
1244 truncated to 16. Users of NFS who use more than 16 groups, should
1245 take care that negative group permissions are not used on the exported
1246 file systems as they will not be reliable unless a GSSAPI based
1247 authentication method is used.
1250 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1251 option compiles in the support for adaptive spinning for lockmgrs
1252 which want to enable it. The lockinit() function now accepts the flag
1253 LK_ADAPTIVE in order to make the lock object subject to adaptive
1254 spinning when both held in write and read mode.
1257 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1258 changed. User applications that use this ioctl need to be rebuilt.
1261 The layout of struct thread has changed. Kernel and modules need to
1265 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1266 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1269 window(1) has been removed from the base system. It can now be
1270 installed from ports. The port is called misc/window.
1273 The way we are storing and accessing `routing table' entries has
1274 changed. Programs reading the FIB, like netstat, need to be
1278 A new netisr implementation has been added for FreeBSD 8. Network
1279 file system modules, such as igmp, ipdivert, and others, should be
1281 Bump __FreeBSD_version to 800096.
1284 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1288 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1289 Bump __FreeBSD_version to 800094.
1292 Add mnt_xflag field to 'struct mount'. File system modules need to be
1294 Bump __FreeBSD_version to 800093.
1297 The compiling option ADAPTIVE_SX has been retired while it has been
1298 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1299 The KPI for sx_init_flags() changes as accepting flags:
1300 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1301 been introduced in order to handle the reversed logic.
1302 Bump __FreeBSD_version to 800092.
1305 Add support for hierarchical jails. Remove global securelevel.
1306 Bump __FreeBSD_version to 800091.
1309 The layout of struct vnet_net has changed, therefore modules
1311 Bump __FreeBSD_version to 800090.
1314 The newly imported zic(8) produces a new format in the output. Please
1315 run tzsetup(8) to install the newly created data to /etc/localtime.
1318 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1319 hw.usb.* and is now consistent again with previous releases.
1322 802.11 monitor mode support was revised and driver api's were changed.
1323 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1324 of DLT_IEEE802_11. No user-visible data structures were changed but
1325 applications that use DLT_IEEE802_11 may require changes.
1326 Bump __FreeBSD_version to 800088.
1329 The layout of the following structs has changed: sysctl_oid,
1330 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1331 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1332 panics may be experienced. World rebuild is required for
1333 correctly checking networking state from userland.
1334 Bump __FreeBSD_version to 800085.
1337 MLDv2 and Source-Specific Multicast (SSM) have been merged
1338 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1339 The implementation of SSM within FreeBSD's IPv6 stack closely
1340 follows the IPv4 implementation.
1342 For kernel developers:
1344 * The most important changes are that the ip6_output() and
1345 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1346 and this lock has been downgraded to a non-recursive mutex.
1348 * As with the changes to the IPv4 stack to support SSM, filtering
1349 of inbound multicast traffic must now be performed by transport
1350 protocols within the IPv6 stack. This does not apply to TCP and
1351 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1353 * The KPIs used by IPv6 multicast are similar to those used by
1354 the IPv4 stack, with the following differences:
1355 * im6o_mc_filter() is analogous to imo_multicast_filter().
1356 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1357 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1358 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1359 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1360 for MLDv1 have an additional 'timer' argument which is used to
1361 jitter the initial membership report for the solicited-node
1362 multicast membership on-link.
1363 * This is not strictly needed for MLDv2, which already jitters
1364 its report transmissions. However, the 'timer' argument is
1365 preserved in case MLDv1 is active on the interface.
1367 * The KAME linked-list based IPv6 membership implementation has
1368 been refactored to use a vector similar to that used by the IPv4
1370 Code which maintains a list of its own multicast memberships
1371 internally, e.g. carp, has been updated to reflect the new
1374 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1375 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1376 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1377 implementation constraint which needs to be addressed in HEAD.
1379 For application developers:
1381 * The changes are broadly similar to those made for the IPv4
1384 * The use of IPv4 and IPv6 multicast socket options on the same
1385 socket, using mapped addresses, HAS NOT been tested or supported.
1387 * There are a number of issues with the implementation of various
1388 IPv6 multicast APIs which need to be resolved in the API surface
1389 before the implementation is fully compatible with KAME userland
1390 use, and these are mostly to do with interface index treatment.
1392 * The literature available discusses the use of either the delta / ASM
1393 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1394 using setsourcefilter(3)/getsourcefilter(3). For more information
1395 please refer to RFC 3768, 'Socket Interface Extensions for
1396 Multicast Source Filters'.
1398 * Applications which use the published RFC 3678 APIs should be fine.
1400 For systems administrators:
1402 * The mtest(8) utility has been refactored to support IPv6, in
1403 addition to IPv4. Interface addresses are no longer accepted
1404 as arguments, their names must be used instead. The utility
1405 will map the interface name to its first IPv4 address as
1406 returned by getifaddrs(3).
1408 * The ifmcstat(8) utility has also been updated to print the MLDv2
1409 endpoint state and source filter lists via sysctl(3).
1411 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1412 loopback of IPv6 multicast datagrams by default; it defaults to 1
1413 to preserve the existing behaviour. Disabling multicast loopback is
1414 recommended for optimal system performance.
1416 * The IPv6 MROUTING code has been changed to examine this sysctl
1417 instead of attempting to perform a group lookup before looping
1418 back forwarded datagrams.
1420 Bump __FreeBSD_version to 800084.
1423 Implement low-level Bluetooth HCI API.
1424 Bump __FreeBSD_version to 800083.
1427 The layout of struct malloc_type, used by modules to register new
1428 memory allocation types, has changed. Most modules will need to
1429 be rebuilt or panics may be experienced.
1430 Bump __FreeBSD_version to 800081.
1433 Anticipate overflowing inp_flags - add inp_flags2.
1434 This changes most offsets in inpcb, so checking v4 connection
1435 state will require a world rebuild.
1436 Bump __FreeBSD_version to 800080.
1439 Add an llentry to struct route and struct route_in6. Modules
1440 embedding a struct route will need to be recompiled.
1441 Bump __FreeBSD_version to 800079.
1444 The size of rt_metrics_lite and by extension rtentry has changed.
1445 Networking administration apps will need to be recompiled.
1446 The route command now supports show as an alias for get, weighting
1447 of routes, sticky and nostick flags to alter the behavior of stateful
1449 Bump __FreeBSD_version to 800078.
1452 Do not use Giant for kbdmux(4) locking. This is wrong and
1453 apparently causing more problems than it solves. This will
1454 re-open the issue where interrupt handlers may race with
1455 kbdmux(4) in polling mode. Typical symptoms include (but
1456 not limited to) duplicated and/or missing characters when
1457 low level console functions (such as gets) are used while
1458 interrupts are enabled (for example geli password prompt,
1459 mountroot prompt etc.). Disabling kbdmux(4) may help.
1462 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1463 kernel modules referencing any of the above need to be recompiled.
1464 Bump __FreeBSD_version to 800075.
1467 GEOM_PART has become the default partition slicer for storage devices,
1468 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1469 introduces some changes:
1471 MSDOS/EBR: the devices created from MSDOS extended partition entries
1472 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1473 to devices with offset-based names. fstabs may need to be modified.
1475 BSD: the "geometry does not match label" warning is harmless in most
1476 cases but it points to problems in file system misalignment with
1477 disk geometry. The "c" partition is now implicit, covers the whole
1478 top-level drive and cannot be (mis)used by users.
1480 General: Kernel dumps are now not allowed to be written to devices
1481 whose partition types indicate they are meant to be used for file
1482 systems (or, in case of MSDOS partitions, as something else than
1485 Most of these changes date approximately from 200812.
1488 The uscanner(4) driver has been removed from the kernel. This follows
1489 Linux removing theirs in 2.6 and making libusb the default interface
1490 (supported by sane).
1493 The multicast forwarding code has been cleaned up. netstat(1)
1494 only relies on KVM now for printing bandwidth upcall meters.
1495 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1496 ip6_mroute_mod respectively. The config(5) options for statically
1497 compiling this code remain the same, i.e. 'options MROUTING'.
1500 Support for the IFF_NEEDSGIANT network interface flag has been
1501 removed, which means that non-MPSAFE network device drivers are no
1502 longer supported. In particular, if_ar, if_sr, and network device
1503 drivers from the old (legacy) USB stack can no longer be built or
1507 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1508 a bunch of new language catalog files have also been added.
1509 This means that some common libc messages are now localized and
1510 they depend on the LC_MESSAGES environmental variable.
1513 The k8temp(4) driver has been renamed to amdtemp(4) since
1514 support for Family 10 and Family 11 CPU families was added.
1517 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1518 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1520 For kernel developers, the most important changes are that the
1521 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1522 and this lock has been downgraded to a non-recursive mutex.
1524 Transport protocols (UDP, Raw IP) are now responsible for filtering
1525 inbound multicast traffic according to group membership and source
1526 filters. The imo_multicast_filter() KPI exists for this purpose.
1527 Transports which do not use multicast (SCTP, TCP) already reject
1528 multicast by default. Forwarding and receive performance may improve
1529 as a mutex acquisition is no longer needed in the ip_input()
1530 low-level input path. in_addmulti() and in_delmulti() are shimmed
1531 to new KPIs which exist to support SSM in-kernel.
1533 For application developers, it is recommended that loopback of
1534 multicast datagrams be disabled for best performance, as this
1535 will still cause the lock to be taken for each looped-back
1536 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1537 be tuned to 0 to disable loopback by default; it defaults to 1
1538 to preserve the existing behaviour.
1540 For systems administrators, to obtain best performance with
1541 multicast reception and multiple groups, it is always recommended
1542 that a card with a suitably precise hash filter is used. Hash
1543 collisions will still result in the lock being taken within the
1544 transport protocol input path to check group membership.
1546 If deploying FreeBSD in an environment with IGMP snooping switches,
1547 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1548 enabled; this forces 224.0.0.0/24 group membership to be announced
1551 The size of 'struct igmpstat' has changed; netstat needs to be
1552 recompiled to reflect this.
1553 Bump __FreeBSD_version to 800070.
1556 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1557 updated to use it. This requires a buildworld/installworld in order to
1558 update the library and dependencies (usbconfig, etc). Its advisable to
1559 rebuild all ports which uses libusb. More specific directions are given
1560 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1561 libusb are no longer required and can be removed.
1564 A workaround is committed to allow the creation of System V shared
1565 memory segment of size > 2 GB on the 64-bit architectures.
1566 Due to a limitation of the existing ABI, the shm_segsz member
1567 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1568 wrong for large segments. Note that limits must be explicitly
1569 raised to allow such segments to be created.
1572 The layout of struct ifnet has changed, requiring a rebuild of all
1573 network device driver modules.
1576 The /dev handling for the new USB stack has changed, a
1577 buildworld/installworld is required for libusb20.
1580 The new USB2 stack has now been permanently moved in and all kernel and
1581 module names reverted to their previous values (eg, usb, ehci, ohci,
1582 ums, ...). The old usb stack can be compiled in by prefixing the name
1583 with the letter 'o', the old usb modules have been removed.
1584 Updating entry 20090216 for xorg and 20090215 for libmap may still
1588 The rc.conf(5) option if_up_delay has been renamed to
1589 defaultroute_delay to better reflect its purpose. If you have
1590 customized this setting in /etc/rc.conf you need to update it to
1594 xorg 7.4 wants to configure its input devices via hald which does not
1595 yet work with USB2. If the keyboard/mouse does not work in xorg then
1597 Option "AllowEmptyInput" "off"
1598 to your ServerLayout section. This will cause X to use the configured
1599 kbd and mouse sections from your xorg.conf.
1602 The GENERIC kernels for all architectures now default to the new USB2
1603 stack. No kernel config options or code have been removed so if a
1604 problem arises please report it and optionally revert to the old USB
1605 stack. If you are loading USB kernel modules or have a custom kernel
1606 that includes GENERIC then ensure that usb names are also changed over,
1607 eg uftdi -> usb2_serial_ftdi.
1609 Older programs linked against the ports libusb 0.1 need to be
1610 redirected to the new stack's libusb20. /etc/libmap.conf can
1612 # Map old usb library to new one for usb2 stack
1613 libusb-0.1.so.8 libusb20.so.1
1616 All USB ethernet devices now attach as interfaces under the name ueN
1617 (eg. ue0). This is to provide a predictable name as vendors often
1618 change usb chipsets in a product without notice.
1621 The ichsmb(4) driver has been changed to require SMBus slave
1622 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1623 All of the other SMBus controller drivers require left-justified
1624 slave addresses, so this change makes all the drivers provide the
1628 INET6 statistics (struct ip6stat) was updated.
1629 netstat(1) needs to be recompiled.
1632 NTFS has been removed from GENERIC kernel on amd64 to match
1633 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1634 will load ntfs.ko module automatically when NTFS support is
1635 actually needed, unless ntfs.ko is not installed or security
1636 level prohibits loading kernel modules. If either is the case,
1637 "options NTFS" has to be added into kernel config.
1640 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1641 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1642 800061. User space tools that rely on the size of struct tcpcb in
1643 tcp_var.h (e.g. sockstat) need to be recompiled.
1646 ng_tty(4) module updated to match the new TTY subsystem.
1647 Due to API change, user-level applications must be updated.
1648 New API support added to mpd5 CVS and expected to be present
1649 in next mpd5.3 release.
1652 With __FreeBSD_version 800060 the makefs tool is part of
1653 the base system (it was a port).
1656 The afdata and ifnet locks have been changed from mutexes to
1657 rwlocks, network modules will need to be re-compiled.
1660 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1661 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1662 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1663 architecture and 40 bytes on 64-bit architecture. The userland
1664 applications "arp" and "ndp" have been updated accordingly.
1665 The output from "netstat -r" shows only routing entries and
1666 none of the L2 information.
1669 __FreeBSD_version 800057 marks the switchover from the
1670 binary ath hal to source code. Users must add the line:
1672 options AH_SUPPORT_AR5416
1674 to their kernel config files when specifying:
1678 The ath_hal module no longer exists; the code is now compiled
1679 together with the driver in the ath module. It is now
1680 possible to tailor chip support (i.e. reduce the set of chips
1681 and thereby the code size); consult ath_hal(4) for details.
1684 __FreeBSD_version 800054 adds memory barriers to
1685 <machine/atomic.h>, new interfaces to ifnet to facilitate
1686 multiple hardware transmit queues for cards that support
1687 them, and a lock-less ring-buffer implementation to
1688 enable drivers to more efficiently manage queueing of
1692 A new version of ZFS (version 13) has been merged to -HEAD.
1693 This version has zpool attribute "listsnapshots" off by
1694 default, which means "zfs list" does not show snapshots,
1695 and is the same as Solaris behavior.
1698 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1701 The uhci, ohci, ehci and slhci USB Host controller drivers have
1702 been put into separate modules. If you load the usb module
1703 separately through loader.conf you will need to load the
1704 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1705 controller add the following to loader.conf:
1711 The ABI used by the PMC toolset has changed. Please keep
1712 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1716 atapci kernel module now includes only generic PCI ATA
1717 driver. AHCI driver moved to ataahci kernel module.
1718 All vendor-specific code moved into separate kernel modules:
1719 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1720 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1721 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1722 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1725 The TTY subsystem of the kernel has been replaced by a new
1726 implementation, which provides better scalability and an
1727 improved driver model. Most common drivers have been migrated to
1728 the new TTY subsystem, while others have not. The following
1729 drivers have not yet been ported to the new TTY layer:
1732 cy, digi, rc, rp, sio
1738 ng_h4, ng_tty, ppp, sl, snp
1740 Adding these drivers to your kernel configuration file shall
1741 cause compilation to fail.
1744 ntpd has been upgraded to 4.2.4p5.
1747 OpenSSH has been upgraded to 5.1p1.
1749 For many years, FreeBSD's version of OpenSSH preferred DSA
1750 over RSA for host and user authentication keys. With this
1751 upgrade, we've switched to the vendor's default of RSA over
1752 DSA. This may cause upgraded clients to warn about unknown
1753 host keys even for previously known hosts. Users should
1754 follow the usual procedure for verifying host keys before
1755 accepting the RSA key.
1757 This can be circumvented by setting the "HostKeyAlgorithms"
1758 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1761 Please note that the sequence of keys offered for
1762 authentication has been changed as well. You may want to
1763 specify IdentityFile in a different order to revert this
1767 The sio(4) driver has been removed from the i386 and amd64
1768 kernel configuration files. This means uart(4) is now the
1769 default serial port driver on those platforms as well.
1771 To prevent collisions with the sio(4) driver, the uart(4) driver
1772 uses different names for its device nodes. This means the
1773 onboard serial port will now most likely be called "ttyu0"
1774 instead of "ttyd0". You may need to reconfigure applications to
1775 use the new device names.
1777 When using the serial port as a boot console, be sure to update
1778 /boot/device.hints and /etc/ttys before booting the new kernel.
1779 If you forget to do so, you can still manually specify the hints
1780 at the loader prompt:
1782 set hint.uart.0.at="isa"
1783 set hint.uart.0.port="0x3F8"
1784 set hint.uart.0.flags="0x10"
1785 set hint.uart.0.irq="4"
1789 The gpt(8) utility has been removed. Use gpart(8) to partition
1793 The version that Linuxulator emulates was changed from 2.4.2
1794 to 2.6.16. If you experience any problems with Linux binaries
1795 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1796 if it fixes the problem contact emulation mailing list.
1799 ISDN4BSD (I4B) was removed from the src tree. You may need to
1800 update a your kernel configuration and remove relevant entries.
1803 I have checked in code to support multiple routing tables.
1804 See the man pages setfib(1) and setfib(2).
1805 This is a hopefully backwards compatible version,
1806 but to make use of it you need to compile your kernel
1807 with options ROUTETABLES=2 (or more up to 16).
1810 The 802.11 wireless support was redone to enable multi-bss
1811 operation on devices that are capable. The underlying device
1812 is no longer used directly but instead wlanX devices are
1813 cloned with ifconfig. This requires changes to rc.conf files.
1814 For example, change:
1815 ifconfig_ath0="WPA DHCP"
1818 ifconfig_wlan0="WPA DHCP"
1819 see rc.conf(5) for more details. In addition, mergemaster of
1820 /etc/rc.d is highly recommended. Simultaneous update of userland
1821 and kernel wouldn't hurt either.
1823 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1824 modules were merged into the base wlan module. All references
1825 to these modules (e.g. in kernel config files) must be removed.
1828 psm(4) has gained write(2) support in native operation level.
1829 Arbitrary commands can be written to /dev/psm%d and status can
1830 be read back from it. Therefore, an application is responsible
1831 for status validation and error recovery. It is a no-op in
1832 other operation levels.
1835 Support for KSE threading has been removed from the kernel. To
1836 run legacy applications linked against KSE libmap.conf may
1837 be used. The following libmap.conf may be used to ensure
1838 compatibility with any prior release:
1840 libpthread.so.1 libthr.so.1
1841 libpthread.so.2 libthr.so.2
1842 libkse.so.3 libthr.so.3
1845 The layout of struct vmspace has changed. This affects libkvm
1846 and any executables that link against libkvm and use the
1847 kvm_getprocs() function. In particular, but not exclusively,
1848 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1849 The effects are minimal, but it's advisable to upgrade world
1853 The latest em driver no longer has support in it for the
1854 82575 adapter, this is now moved to the igb driver. The
1855 split was done to make new features that are incompatible
1856 with older hardware easier to do.
1859 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1860 likewise the kernel option is now GEOM_LINUX_LVM.
1863 The default NFS mount mode has changed from UDP to TCP for
1864 increased reliability. If you rely on (insecurely) NFS
1865 mounting across a firewall you may need to update your
1869 Belatedly note the addition of m_collapse for compacting
1873 The fts(3) structures have been changed to use adequate
1874 integer types for their members and so to be able to cope
1875 with huge file trees. The old fts(3) ABI is preserved
1876 through symbol versioning in libc, so third-party binaries
1877 using fts(3) should still work, although they will not take
1878 advantage of the extended types. At the same time, some
1879 third-party software might fail to build after this change
1880 due to unportable assumptions made in its source code about
1881 fts(3) structure members. Such software should be fixed
1882 by its vendor or, in the worst case, in the ports tree.
1883 FreeBSD_version 800015 marks this change for the unlikely
1884 case that a portable fix is impossible.
1887 To upgrade to -current after this date, you must be running
1888 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1889 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1892 The ADAPTIVE_GIANT kernel option has been retired because its
1893 functionality is the default now.
1896 The AT keyboard emulation of sunkbd(4) has been turned on
1897 by default. In order to make the special symbols of the Sun
1898 keyboards driven by sunkbd(4) work under X these now have
1899 to be configured the same way as Sun USB keyboards driven
1900 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1902 Option "XkbLayout" "us"
1903 Option "XkbRules" "xorg"
1904 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1907 It has been decided that it is desirable to provide ABI
1908 backwards compatibility to the FreeBSD 4/5/6 versions of the
1909 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1910 broken with the introduction of PCI domain support (see the
1911 20070930 entry). Unfortunately, this required the ABI of
1912 PCIOCGETCONF to be broken again in order to be able to
1913 provide backwards compatibility to the old version of that
1914 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1915 again. As for prominent ports this affects neither pciutils
1916 nor xorg-server this time, the hal port needs to be rebuilt
1920 The misnamed kthread_create() and friends have been renamed
1921 to kproc_create() etc. Many of the callers already
1922 used kproc_start()..
1923 I will return kthread_create() and friends in a while
1924 with implementations that actually create threads, not procs.
1925 Renaming corresponds with version 800002.
1934 Avoid using make -j when upgrading. While generally safe, there are
1935 sometimes problems using -j to upgrade. If your upgrade fails with
1936 -j, please try again without -j. From time to time in the past there
1937 have been problems using -j with buildworld and/or installworld. This
1938 is especially true when upgrading between "distant" versions (eg one
1939 that cross a major release boundary or several minor releases, or when
1940 several months have passed on the -current branch).
1942 Sometimes, obscure build problems are the result of environment
1943 poisoning. This can happen because the make utility reads its
1944 environment when searching for values for global variables. To run
1945 your build attempts in an "environmental clean room", prefix all make
1946 commands with 'env -i '. See the env(1) manual page for more details.
1948 When upgrading from one major version to another it is generally best
1949 to upgrade to the latest code in the currently installed branch first,
1950 then do an upgrade to the new branch. This is the best-tested upgrade
1951 path, and has the highest probability of being successful. Please try
1952 this approach before reporting problems with a major version upgrade.
1954 When upgrading a live system, having a root shell around before
1955 installing anything can help undo problems. Not having a root shell
1956 around can lead to problems if pam has changed too much from your
1957 starting point to allow continued authentication after the upgrade.
1961 When upgrading the boot ZFS pool to a new version, always follow
1964 1.) recompile and reinstall the ZFS boot loader and boot block
1965 (this is part of "make buildworld" and "make installworld")
1967 2.) update the ZFS boot block on your boot drive
1969 The following example updates the ZFS boot block on the first
1970 partition (freebsd-boot) of a GPT partitioned drive ad0:
1971 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1973 Non-boot pools do not need these updates.
1977 If you are updating from a prior version of FreeBSD (even one just
1978 a few days old), you should follow this procedure. It is the most
1979 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1981 make kernel-toolchain
1982 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1983 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1985 To test a kernel once
1986 ---------------------
1987 If you just want to boot a kernel once (because you are not sure
1988 if it works, or if you want to boot a known bad kernel to provide
1989 debugging information) run
1990 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1991 nextboot -k testkernel
1993 To just build a kernel when you know that it won't mess you up
1994 --------------------------------------------------------------
1995 This assumes you are already running a CURRENT system. Replace
1996 ${arch} with the architecture of your machine (e.g. "i386",
1997 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1999 cd src/sys/${arch}/conf
2000 config KERNEL_NAME_HERE
2001 cd ../compile/KERNEL_NAME_HERE
2006 If this fails, go to the "To build a kernel" section.
2008 To rebuild everything and install it on the current system.
2009 -----------------------------------------------------------
2010 # Note: sometimes if you are running current you gotta do more than
2011 # is listed here if you are upgrading from a really old current.
2013 <make sure you have good level 0 dumps>
2015 make kernel KERNCONF=YOUR_KERNEL_HERE
2017 <reboot in single user> [3]
2024 To cross-install current onto a separate partition
2025 --------------------------------------------------
2026 # In this approach we use a separate partition to hold
2027 # current's root, 'usr', and 'var' directories. A partition
2028 # holding "/", "/usr" and "/var" should be about 2GB in
2031 <make sure you have good level 0 dumps>
2034 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2035 <maybe newfs current's root partition>
2036 <mount current's root partition on directory ${CURRENT_ROOT}>
2037 make installworld DESTDIR=${CURRENT_ROOT}
2038 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2039 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2040 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2041 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2042 <reboot into current>
2043 <do a "native" rebuild/install as described in the previous section>
2044 <maybe install compatibility libraries from ports/misc/compat*>
2048 To upgrade in-place from stable to current
2049 ----------------------------------------------
2050 <make sure you have good level 0 dumps>
2052 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2054 <reboot in single user> [3]
2061 Make sure that you've read the UPDATING file to understand the
2062 tweaks to various things you need. At this point in the life
2063 cycle of current, things change often and you are on your own
2064 to cope. The defaults can also change, so please read ALL of
2065 the UPDATING entries.
2067 Also, if you are tracking -current, you must be subscribed to
2068 freebsd-current@freebsd.org. Make sure that before you update
2069 your sources that you have read and understood all the recent
2070 messages there. If in doubt, please track -stable which has
2071 much fewer pitfalls.
2073 [1] If you have third party modules, such as vmware, you
2074 should disable them at this point so they don't crash your
2077 [3] From the bootblocks, boot -s, and then do
2082 adjkerntz -i # if CMOS is wall time
2083 Also, when doing a major release upgrade, it is required that
2084 you boot into single user mode to do the installworld.
2086 [4] Note: This step is non-optional. Failure to do this step
2087 can result in a significant reduction in the functionality of the
2088 system. Attempting to do it by hand is not recommended and those
2089 that pursue this avenue should read this file carefully, as well
2090 as the archives of freebsd-current and freebsd-hackers mailing lists
2091 for potential gotchas. The -U option is also useful to consider.
2092 See mergemaster(8) for more information.
2094 [5] Usually this step is a noop. However, from time to time
2095 you may need to do this if you get unknown user in the following
2096 step. It never hurts to do it all the time. You may need to
2097 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2098 install) after the buildworld before this step if you last updated
2099 from current before 20130425 or from -stable before 20130430.
2101 [6] This only deletes old files and directories. Old libraries
2102 can be deleted by "make delete-old-libs", but you have to make
2103 sure that no program is using those libraries anymore.
2105 [8] In order to have a kernel that can run the 4.x binaries needed to
2106 do an installworld, you must include the COMPAT_FREEBSD4 option in
2107 your kernel. Failure to do so may leave you with a system that is
2108 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2109 required to run the 5.x binaries on more recent kernels. And so on
2110 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2112 Make sure that you merge any new devices from GENERIC since the
2113 last time you updated your kernel config file.
2115 [9] When checking out sources, you must include the -P flag to have
2116 cvs prune empty directories.
2118 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2119 "?=" instead of the "=" assignment operator, so that buildworld can
2120 override the CPUTYPE if it needs to.
2122 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2123 not on the command line, or in /etc/make.conf. buildworld will
2124 warn if it is improperly defined.
2127 This file contains a list, in reverse chronological order, of major
2128 breakages in tracking -current. It is not guaranteed to be a complete
2129 list of such breakages, and only contains entries since October 10, 2007.
2130 If you need to see UPDATING entries from before that date, you will need
2131 to fetch an UPDATING file from an older FreeBSD release.
2133 Copyright information:
2135 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2137 Redistribution, publication, translation and use, with or without
2138 modification, in full or in part, in any form or format of this
2139 document are permitted without further permission from the author.
2141 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2142 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2143 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2144 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2145 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2146 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2147 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2148 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2149 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2150 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2151 POSSIBILITY OF SUCH DAMAGE.
2153 Contact Warner Losh if you have any questions about your use of