1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of
16 stable/10, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
19 20150127: p5 FreeBSD-SA-15:02.kmem
22 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
23 vulnerability. [SA-15:02]
25 Fix SCTP stream reset vulnerability. [SA-15:03]
27 20150114: p4 FreeBSD-SA-15:01.openssl
28 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
30 20141223: p3 FreeBSD-SA-14:31.ntp
31 FreeBSD-EN-14:13.freebsd-update
33 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
34 Fix directory deletion issue in freebsd-update. [EN-14:13]
36 20141217: p2 FreeBSD-SA-14:30.unbound
37 Fix unbound remote denial of service vulnerability.
39 20141210: p1 FreeBSD-SA-14:27.stdio
42 Fix buffer overflow in stdio. [SA-14:27]
44 Fix multiple vulnerabilities in file(1) and libmagic(3).
48 The ofwfb driver, used to provide a graphics console on PowerPC when
49 using vt(4), no longer allows mmap() of all of physical memory. This
50 will prevent Xorg on PowerPC with some ATI graphics cards from
51 initializing properly unless x11-servers/xorg-server is updated to
55 The libatf-c and libatf-c++ major versions were downgraded to 0 and
56 1 respectively to match the upstream numbers. They were out of
57 sync because, when they were originally added to FreeBSD, the
58 upstream versions were not respected. These libraries are private
59 and not yet built by default, so renumbering them should be a
60 non-issue. However, unclean source trees will yield broken test
61 programs once the operator executes "make delete-old-libs" after a
64 Additionally, the atf-sh binary was made private by moving it into
65 /usr/libexec/. Already-built shell test programs will keep the
66 path to the old binary so they will break after "make delete-old"
69 If you are using WITH_TESTS=yes (not the default), wipe the object
70 tree and rebuild from scratch to prevent spurious test failures.
71 This is only needed once: the misnumbered libraries and misplaced
72 binaries have been added to OptionalObsoleteFiles.inc so they will
73 be removed during a clean upgrade.
76 The ixgbe tunables now match their sysctl counterparts, for example:
77 hw.ixgbe.enable_aim => hw.ix.enable_aim
78 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
81 The NFSv4.1 server committed by r269398 changes the internal
82 function call interfaces used between the NFS and krpc modules.
83 As such, __FreeBSD_version was bumped.
86 The default unbound configuration has been modified to address
87 issues with reverse lookups on networks that use private
88 address ranges. If you use the local_unbound service, run
89 "service local_unbound setup" as root to regenerate your
90 configuration, then "service local_unbound reload" to load the
94 It is no longer necessary to include the dwarf version in your DEBUG
95 options in your kernel config file. The bug that required it to be
96 placed in the config file has bene fixed. DEBUG should now just
97 contain -g. The build system will automatically update things
98 to do the right thing.
101 Several ABI breaking changes were merged to CTL and new iSCSI code.
102 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
103 iscsictl need to be rebuilt to work with a new kernel.
106 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
107 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
108 which differs from the behaviour controlled by this knob.)
111 On i386 and amd64 systems, the onifconsole flag is now set by default
112 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
113 as a login TTY if it is set in the bootloader as an active kernel
114 console. No changes in behavior should result otherwise. To revert to
115 the previous behavior, set ttyu0 to "off" in /etc/ttys.
118 Clang and llvm have been upgraded to 3.4.1 release.
121 Clang and llvm have been upgraded to 3.4 release.
124 If a Makefile in a tests/ directory was auto-generating a Kyuafile
125 instead of providing an explicit one, this would prevent such
126 Makefile from providing its own Kyuafile in the future during
127 NO_CLEAN builds. This has been fixed in the Makefiles but manual
128 intervention is needed to clean an objdir if you use NO_CLEAN:
129 # find /usr/obj -name Kyuafile | xargs rm -f
132 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
133 capability mode support. Please note that enabling the feature in
134 kernel is still highly recommended.
137 OpenSSH is now built with sandbox support, and will use sandbox as
138 the default privilege separation method. This requires Capsicum
139 capability mode support in kernel.
142 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
143 been deprecated and will not be part of FreeBSD 11.0 and later
144 releases. If you use this driver, please consider switching to
145 the nfe(4) driver instead.
151 The behavior of gss_pseudo_random() for the krb5 mechanism
152 has changed, for applications requesting a longer random string
153 than produced by the underlying enctype's pseudo-random() function.
154 In particular, the random string produced from a session key of
155 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
156 be different at the 17th octet and later, after this change.
157 The counter used in the PRF+ construction is now encoded as a
158 big-endian integer in accordance with RFC 4402.
159 __FreeBSD_version is bumped to 1000701.
162 The WITHOUT_ATF build knob has been removed and its functionality
163 has been subsumed into the more generic WITHOUT_TESTS. If you were
164 using the former to disable the build of the ATF libraries, you
165 should change your settings to use the latter.
168 The default version of mtree is nmtree which is obtained from
169 NetBSD. The output is generally the same, but may vary
170 slightly. If you found you need identical output adding
171 "-F freebsd9" to the command line should do the trick. For the
172 time being, the old mtree is available as fmtree.
175 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
176 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
177 1.1.4_8 and verify bsdyml not linked in, before running "make
179 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
181 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
184 The rc.d/jail script has been updated to support jail(8)
185 configuration file. The "jail_<jname>_*" rc.conf(5) variables
186 for per-jail configuration are automatically converted to
187 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
188 This is transparently backward compatible. See below about some
189 incompatibilities and rc.conf(5) manual page for more details.
191 These variables are now deprecated in favor of jail(8) configuration
192 file. One can use "rc.d/jail config <jname>" command to generate
193 a jail(8) configuration file in /var/run/jail.<jname>.conf without
194 running the jail(8) utility. The default pathname of the
195 configuration file is /etc/jail.conf and can be specified by
196 using $jail_conf or $jail_<jname>_conf variables.
198 Please note that jail_devfs_ruleset accepts an integer at
199 this moment. Please consider to rewrite the ruleset name
203 BIND has been removed from the base system. If all you need
204 is a local resolver, simply enable and start the local_unbound
205 service instead. Otherwise, several versions of BIND are
206 available in the ports tree. The dns/bind99 port is one example.
208 With this change, nslookup(1) and dig(1) are no longer in the base
209 system. Users should instead use host(1) and drill(1) which are
210 in the base system. Alternatively, nslookup and dig can
211 be obtained by installing the dns/bind-tools port.
214 With the addition of unbound(8), a new unbound user is now
215 required during installworld. "mergemaster -p" can be used to
216 add the user prior to installworld, as documented in the handbook.
219 OpenSSH is now built with DNSSEC support, and will by default
220 silently trust signed SSHFP records. This can be controlled with
221 the VerifyHostKeyDNS client configuration setting. DNSSEC support
222 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
225 The GNU Compiler Collection and C++ standard library (libstdc++)
226 are no longer built by default on platforms where clang is the system
227 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
231 The PROCDESC kernel option is now part of the GENERIC kernel
232 configuration and is required for the rwhod(8) to work.
233 If you are using custom kernel configuration, you should include
237 The API and ABI related to the Capsicum framework was modified
238 in backward incompatible way. The userland libraries and programs
239 have to be recompiled to work with the new kernel. This includes the
240 following libraries and programs, but the whole buildworld is
241 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
242 kdump, procstat, rwho, rwhod, uniq.
245 AES-NI intrinsic support has been added to gcc. The AES-NI module
246 has been updated to use this support. A new gcc is required to build
247 the aesni module on both i386 and amd64.
250 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
251 Thus "device padlock_rng" and "device rdrand_rng" should be
252 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
255 WITH_ICONV has been split into two feature sets. WITH_ICONV now
256 enables just the iconv* functionality and is now on by default.
257 WITH_LIBICONV_COMPAT enables the libiconv api and link time
258 compatability. Set WITHOUT_ICONV to build the old way.
259 If you have been using WITH_ICONV before, you will very likely
260 need to turn on WITH_LIBICONV_COMPAT.
263 INVARIANTS option now enables DEBUG for code with OpenSolaris and
264 Illumos origin, including ZFS. If you have INVARIANTS in your
265 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
267 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
268 locks if WITNESS option was set. Because that generated a lot of
269 witness(9) reports and all of them were believed to be false
270 positives, this is no longer done. New option OPENSOLARIS_WITNESS
271 can be used to achieve the previous behavior.
274 Timer values in IPv6 data structures now use time_uptime instead
275 of time_second. Although this is not a user-visible functional
276 change, userland utilities which directly use them---ndp(8),
277 rtadvd(8), and rtsold(8) in the base system---need to be updated
281 find -delete can now delete the pathnames given as arguments,
282 instead of only files found below them or if the pathname did
283 not contain any slashes. Formerly, the following error message
286 find: -delete: <path>: relative path potentially not safe
288 Deleting the pathnames given as arguments can be prevented
289 without error messages using -mindepth 1 or by changing
290 directory and passing "." as argument to find. This works in the
291 old as well as the new version of find.
294 Behavior of devfs rules path matching has been changed.
295 Pattern is now always matched against fully qualified devfs
296 path and slash characters must be explicitly matched by
297 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
298 subdirectories must be reviewed.
301 The default ARM ABI has changed to the ARM EABI. The old ABI is
302 incompatible with the ARM EABI and all programs and modules will
303 need to be rebuilt to work with a new kernel.
305 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
307 NOTE: Support for the old ABI will be removed in the future and
308 users are advised to upgrade.
311 pkg_install has been disconnected from the build if you really need it
312 you should add WITH_PKGTOOLS in your src.conf(5).
315 Most of network statistics structures were changed to be able
316 keep 64-bits counters. Thus all tools, that work with networking
317 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
320 Fix targets that run multiple make's to use && rather than ;
321 so that subsequent steps depend on success of previous.
323 NOTE: if building 'universe' with -j* on stable/8 or stable/9
324 it would be better to start the build using bmake, to avoid
325 overloading the machine.
328 Fix a bug that allowed a tracing process (e.g. gdb) to write
329 to a memory-mapped file in the traced process's address space
330 even if neither the traced process nor the tracing process had
331 write access to that file.
334 CVS has been removed from the base system. An exact copy
335 of the code is available from the devel/cvs port.
338 Some people report the following error after the switch to bmake:
340 make: illegal option -- J
341 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
343 *** [buildworld] Error code 2
345 this likely due to an old instance of make in
346 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
347 which src/Makefile will use that blindly, if it exists, so if
348 you see the above error:
350 rm -rf `make -V MAKEPATH`
355 Use bmake by default.
356 Whereas before one could choose to build with bmake via
357 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
358 make. The goal is to remove these knobs for 10-RELEASE.
360 It is worth noting that bmake (like gmake) treats the command
361 line as the unit of failure, rather than statements within the
362 command line. Thus '(cd some/where && dosomething)' is safer
363 than 'cd some/where; dosomething'. The '()' allows consistent
364 behavior in parallel build.
367 Fix a bug that allows NFS clients to issue READDIR on files.
370 The WITHOUT_IDEA option has been removed because
371 the IDEA patent expired.
374 The sysctl which controls TRIM support under ZFS has been renamed
375 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
379 The mergemaster command now uses the default MAKEOBJDIRPREFIX
380 rather than creating it's own in the temporary directory in
381 order allow access to bootstrapped versions of tools such as
382 install and mtree. When upgrading from version of FreeBSD where
383 the install command does not support -l, you will need to
384 install a new mergemaster command if mergemaster -p is required.
385 This can be accomplished with the command (cd src/usr.sbin/mergemaster
389 Legacy ATA stack, disabled and replaced by new CAM-based one since
390 FreeBSD 9.0, completely removed from the sources. Kernel modules
391 atadisk and atapi*, user-level tools atacontrol and burncd are
392 removed. Kernel option `options ATA_CAM` is now permanently enabled
396 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
397 and socketpair(2). Software, in particular Kerberos, may
398 automatically detect and use these during building. The resulting
399 binaries will not work on older kernels.
402 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
403 information, see the respective 20130304 entry).
406 Recent commits to callout(9) changed the size of struct callout,
407 so the KBI is probably heavily disturbed. Also, some functions
408 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
409 by macros. Every kernel module using it won't load, so rebuild
412 The ctl device has been re-enabled in GENERIC for i386 and amd64,
413 but does not initialize by default (because of the new CTL_DISABLE
414 option) to save memory. To re-enable it, remove the CTL_DISABLE
415 option from the kernel config file or set kern.cam.ctl.disable=0
416 in /boot/loader.conf.
419 The ctl device has been disabled in GENERIC for i386 and amd64.
420 This was done due to the extra memory being allocated at system
421 initialisation time by the ctl driver which was only used if
422 a CAM target device was created. This makes a FreeBSD system
423 unusable on 128MB or less of RAM.
426 A new compression method (lz4) has been merged to -HEAD. Please
427 refer to zpool-features(7) for more information.
429 Please refer to the "ZFS notes" section of this file for information
430 on upgrading boot ZFS pools.
433 A BSD-licensed patch(1) variant has been added and is installed
434 as bsdpatch, being the GNU version the default patch.
435 To inverse the logic and use the BSD-licensed one as default,
436 while having the GNU version installed as gnupatch, rebuild
437 and install world with the WITH_BSD_PATCH knob set.
440 Due to the use of the new -l option to install(1) during build
441 and install, you must take care not to directly set the INSTALL
442 make variable in your /etc/make.conf, /etc/src.conf, or on the
443 command line. If you wish to use the -C flag for all installs
444 you may be able to add INSTALL+=-C to /etc/make.conf or
448 The install(1) option -M has changed meaning and now takes an
449 argument that is a file or path to append logs to. In the
450 unlikely event that -M was the last option on the command line
451 and the command line contained at least two files and a target
452 directory the first file will have logs appended to it. The -M
453 option served little practical purpose in the last decade so its
454 use is expected to be extremely rare.
457 After switching to Clang as the default compiler some users of ZFS
458 on i386 systems started to experience stack overflow kernel panics.
459 Please consider using 'options KSTACK_PAGES=4' in such configurations.
462 GEOM_LABEL now mangles label names read from file system metadata.
463 Mangling affect labels containing spaces, non-printable characters,
464 '%' or '"'. Device names in /etc/fstab and other places may need to
468 By default, only the 10 most recent kernel dumps will be saved. To
469 restore the previous behaviour (no limit on the number of kernel dumps
470 stored in the dump directory) add the following line to /etc/rc.conf:
475 With the addition of auditdistd(8), a new auditdistd user is now
476 required during installworld. "mergemaster -p" can be used to
477 add the user prior to installworld, as documented in the handbook.
480 The sin6_scope_id member variable in struct sockaddr_in6 is now
481 filled by the kernel before passing the structure to the userland via
482 sysctl or routing socket. This means the KAME-specific embedded scope
483 id in sin6_addr.s6_addr[2] is always cleared in userland application.
484 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
485 __FreeBSD_version is bumped to 1000025.
488 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
489 This means that the world and kernel will be compiled with clang
490 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
491 and /usr/bin/cpp. To disable this behavior and revert to building
492 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
493 of current may need to bootstrap WITHOUT_CLANG first if the clang
494 build fails (its compatibility window doesn't extend to the 9 stable
498 The IPFIREWALL_FORWARD kernel option has been removed. Its
499 functionality now turned on by default.
502 The ZERO_COPY_SOCKET kernel option has been removed and
503 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
504 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
505 mechanism which is not safe and may result in kernel crashes.
506 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
507 driver supports disposeable external page sized mbuf storage.
508 Proper replacements for both zero-copy mechanisms are under
509 consideration and will eventually lead to complete removal
510 of the two kernel options.
513 The IPv4 network stack has been converted to network byte
514 order. The following modules need to be recompiled together
515 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
516 pf(4), ipfw(4), ng_ipfw(4), stf(4).
519 Support for non-MPSAFE filesystems was removed from VFS. The
520 VFS_VERSION was bumped, all filesystem modules shall be
524 All the non-MPSAFE filesystems have been disconnected from
525 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
526 portalfs, smbfs, xfs.
529 The interface cloning API and ABI has changed. The following
530 modules need to be recompiled together with kernel:
531 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
532 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
533 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
536 The sdhci driver was split in two parts: sdhci (generic SD Host
537 Controller logic) and sdhci_pci (actual hardware driver).
538 No kernel config modifications are required, but if you
539 load sdhc as a module you must switch to sdhci_pci instead.
542 Import the FUSE kernel and userland support into base system.
545 The GNU sort(1) program has been removed since the BSD-licensed
546 sort(1) has been the default for quite some time and no serious
547 problems have been reported. The corresponding WITH_GNU_SORT
551 The pfil(9) API/ABI for AF_INET family has been changed. Packet
552 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
556 The net80211(4) ABI has been changed to allow for improved driver
557 PS-POLL and power-save support. All wireless drivers need to be
558 recompiled to work with the new kernel.
561 The random(4) support for the VIA hardware random number
562 generator (`PADLOCK') is no longer enabled unconditionally.
563 Add the padlock_rng device in the custom kernel config if
564 needed. The GENERIC kernels on i386 and amd64 do include the
565 device, so the change only affects the custom kernel
569 The pf(4) packet filter ABI has been changed. pfctl(8) and
570 snmp_pf module need to be recompiled to work with new kernel.
573 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
574 to -HEAD. Pools that have empty_bpobj in active state can not be
575 imported read-write with ZFS implementations that do not support
576 this feature. For more information read the zpool-features(5)
580 The sparc64 ZFS loader has been changed to no longer try to auto-
581 detect ZFS providers based on diskN aliases but now requires these
582 to be explicitly listed in the OFW boot-device environment variable.
585 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
586 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
587 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
590 The following sysctls and tunables have been renamed for consistency
591 with other variables:
592 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
593 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
596 The sort utility has been replaced with BSD sort. For now, GNU sort
597 is also available as "gnusort" or the default can be set back to
598 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
599 installed as "bsdsort".
602 A new version of ZFS (pool version 5000) has been merged to -HEAD.
603 Starting with this version the old system of ZFS pool versioning
604 is superseded by "feature flags". This concept enables forward
605 compatibility against certain future changes in functionality of ZFS
606 pools. The first read-only compatible "feature flag" for ZFS pools
607 is named "com.delphix:async_destroy". For more information
608 read the new zpool-features(5) manual page.
609 Please refer to the "ZFS notes" section of this file for information
610 on upgrading boot ZFS pools.
613 The malloc(3) implementation embedded in libc now uses sources imported
614 as contrib/jemalloc. The most disruptive API change is to
615 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
616 delete it prior to installworld, and optionally re-create it using the
617 new format after rebooting. See malloc.conf(5) for details
618 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
622 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
623 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
624 now spelled mips. This is to aid compatibility with third-party
625 software that expects this naming scheme in uname(3). Little-endian
626 settings are unchanged. If you are updating a big-endian mips64 machine
627 from before this change, you may need to set MACHINE_ARCH=mips64 in
628 your environment before the new build system will recognize your machine.
631 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
635 Now unix domain sockets behave "as expected" on nullfs(5). Previously
636 nullfs(5) did not pass through all behaviours to the underlying layer,
637 as a result if we bound to a socket on the lower layer we could connect
638 only to the lower path; if we bound to the upper layer we could connect
639 only to the upper path. The new behavior is one can connect to both the
640 lower and the upper paths regardless what layer path one binds to.
643 The getifaddrs upgrade path broken with 20111215 has been restored.
644 If you have upgraded in between 20111215 and 20120209 you need to
645 recompile libc again with your kernel. You still need to recompile
646 world to be able to configure CARP but this restriction already
650 The set_rcvar() function has been removed from /etc/rc.subr. All
651 base and ports rc.d scripts have been updated, so if you have a
652 port installed with a script in /usr/local/etc/rc.d you can either
653 hand-edit the rcvar= line, or reinstall the port.
655 An easy way to handle the mass-update of /etc/rc.d:
656 rm /etc/rc.d/* && mergemaster -i
659 panic(9) now stops other CPUs in the SMP systems, disables interrupts
660 on the current CPU and prevents other threads from running.
661 This behavior can be reverted using the kern.stop_scheduler_on_panic
663 The new behavior can be incompatible with kern.sync_on_panic.
666 The carp(4) facility has been changed significantly. Configuration
667 of the CARP protocol via ifconfig(8) has changed, as well as format
668 of CARP events submitted to devd(8) has changed. See manual pages
669 for more information. The arpbalance feature of carp(4) is currently
670 not supported anymore.
672 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
673 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
674 need to be recompiled.
677 The acpi_wmi(4) status device /dev/wmistat has been renamed to
681 The option VFS_ALLOW_NONMPSAFE option has been added in order to
682 explicitely support non-MPSAFE filesystems.
683 It is on by default for all supported platform at this present
687 The broken amd(4) driver has been replaced with esp(4) in the amd64,
688 i386 and pc98 GENERIC kernel configuration files.
691 sysinstall has been removed
694 The stable/9 branch created in subversion. This corresponds to the
695 RELENG_9 branch in CVS.
698 This commit modifies vfs_register() so that it uses a hash
699 calculation to set vfc_typenum, which is enabled by default.
700 The first time a system is booted after this change, the
701 vfc_typenum values will change for all file systems. The
702 main effect of this is a change to the NFS server file handles
703 for file systems that use vfc_typenum in their fsid, such as ZFS.
704 It will, however, prevent vfc_typenum from changing when file
705 systems are loaded in a different order for subsequent reboots.
706 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
707 until you are ready to remount all NFS clients after a reboot.
710 Bump the shared library version numbers for libraries that
711 do not use symbol versioning, have changed the ABI compared
712 to stable/8 and which shared library version was not bumped.
713 Done as part of 9.0-RELEASE cycle.
716 During the merge of Capsicum features, the fget(9) KPI was modified.
717 This may require the rebuilding of out-of-tree device drivers --
718 issues have been reported specifically with the nVidia device driver.
719 __FreeBSD_version is bumped to 900041.
721 Also, there is a period between 20110811 and 20110814 where the
722 special devices /dev/{stdin,stdout,stderr} did not work correctly.
723 Building world from a kernel during that window may not work.
726 The packet filter (pf) code has been updated to OpenBSD 4.5.
727 You need to update userland tools to be in sync with kernel.
728 This update breaks backward compatibility with earlier pfsync(4)
729 versions. Care must be taken when updating redundant firewall setups.
732 The following sysctls and tunables are retired on x86 platforms:
734 machdep.hlt_logical_cpus
735 The following sysctl is retired:
736 machdep.hyperthreading_allowed
737 The sysctls were supposed to provide a way to dynamically offline and
738 online selected CPUs on x86 platforms, but the implementation has not
739 been reliable especially with SCHED_ULE scheduler.
740 machdep.hyperthreading_allowed tunable is still available to ignore
741 hyperthreading CPUs at OS level.
742 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
743 where X is an APIC ID of a CPU. Be advised, though, that disabling
744 CPUs in non-uniform fashion will result in non-uniform topology and
745 may lead to sub-optimal system performance with SCHED_ULE, which is
749 cpumask_t type is retired and cpuset_t is used in order to describe
753 Changes to ifconfig(8) for dynamic address family detection mandate
754 that you are running a kernel of 20110525 or later. Make sure to
755 follow the update procedure to boot a new kernel before installing
759 Support for sun4v architecture is officially dropped
762 Several KPI breaking changes have been committed to the mii(4) layer,
763 the PHY drivers and consequently some Ethernet drivers using mii(4).
764 This means that miibus.ko and the modules of the affected Ethernet
765 drivers need to be recompiled.
767 Note to kernel developers: Given that the OUI bit reversion problem
768 was fixed as part of these changes all mii(4) commits related to OUIs,
769 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
770 handling, no longer can be merged verbatim to stable/8 and previous
774 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
775 into their kernel configurations along with 'device pci'.
778 The default NFS client is now the new NFS client, so fstype "newnfs"
779 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
780 Although mounts via fstype "nfs" will usually work without userland
781 changes, it is recommended that the mount(8) and mount_nfs(8)
782 commands be rebuilt from sources and that a link to mount_nfs called
783 mount_oldnfs be created. The new client is compiled into the
784 kernel with "options NFSCL" and this is needed for diskless root
785 file systems. The GENERIC kernel configs have been changed to use
786 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
787 To use the regular/old client, you can "mount -t oldnfs ...". For
788 a diskless root file system, you must also include a line like:
790 vfs.root.mountfrom="oldnfs:"
792 in the boot/loader.conf on the root fs on the NFS server to make
793 a diskless root fs use the old client.
796 The GENERIC kernels for all architectures now default to the new
797 CAM-based ATA stack. It means that all legacy ATA drivers were
798 removed and replaced by respective CAM drivers. If you are using
799 ATA device names in /etc/fstab or other places, make sure to update
800 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
801 where 'Y's are the sequential numbers starting from zero for each type
802 in order of detection, unless configured otherwise with tunables,
803 see cam(4)). There will be symbolic links created in /dev/ to map
804 old adX devices to the respective adaY. They should provide basic
805 compatibility for file systems mounting in most cases, but they do
806 not support old user-level APIs and do not have respective providers
807 in GEOM. Consider using updated management tools with new device names.
809 It is possible to load devices ahci, ata, siis and mvs as modules,
810 but option ATA_CAM should remain in kernel configuration to make ata
811 module work as CAM driver supporting legacy ATA controllers. Device ata
812 still can be used in modular fashion (atacore + ...). Modules atadisk
813 and atapi* are not used and won't affect operation in ATA_CAM mode.
814 Note that to use CAM-based ATA kernel should include CAM devices
815 scbus, pass, da (or explicitly ada), cd and optionally others. All of
816 them are parts of the cam module.
818 ataraid(4) functionality is now supported by the RAID GEOM class.
819 To use it you can load geom_raid kernel module and use graid(8) tool
820 for management. Instead of /dev/arX device names, use /dev/raid/rX.
822 No kernel config options or code have been removed, so if a problem
823 arises, please report it and optionally revert to the old ATA stack.
824 In order to do it you can remove from the kernel config:
829 , and instead add back:
830 device atadisk # ATA disk drives
831 device ataraid # ATA RAID drives
832 device atapicd # ATAPI CDROM drives
833 device atapifd # ATAPI floppy drives
834 device atapist # ATAPI tape drives
837 The default NFS server has been changed to the new server, which
838 was referred to as the experimental server. If you need to switch
839 back to the old NFS server, you must now put the "-o" option on
840 both the mountd and nfsd commands. This can be done using the
841 mountd_flags and nfs_server_flags rc.conf variables until an
842 update to the rc scripts is committed, which is coming soon.
845 The GNU Objective-C runtime library (libobjc), and other Objective-C
846 related components have been removed from the base system. If you
847 require an Objective-C library, please use one of the available ports.
850 ath(4) has been split into bus- and device- modules. if_ath contains
851 the HAL, the TX rate control and the network device code. if_ath_pci
852 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
853 contains the AHB glue. Users need to load both if_ath_pci and if_ath
854 in order to use ath on everything else.
856 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
857 need to load if_ath and if_ath_pci for ath(4) operation.
860 As part of the replacement of sysinstall, the process of building
861 release media has changed significantly. For details, please re-read
862 release(7), which has been updated to reflect the new build process.
865 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
866 is the last available version under GPLv2. It brings a number of new
867 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
868 4.1 and SSE 4.2), better support for powerpc64, a number of new
869 directives, and lots of other small improvements. See the ChangeLog
870 file in contrib/binutils for the full details.
873 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
874 compliant, and will now use half of hash for authentication.
875 This will break interoperability with all stacks (including all
876 actual FreeBSD versions) who implement
877 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
879 The only workaround with such peers is to use another HMAC
880 algorithm for IPsec ("phase 2") authentication.
883 Remove the uio_yield prototype and symbol. This function has
884 been misnamed since it was introduced and should not be
885 globally exposed with this name. The equivalent functionality
886 is now available using kern_yield(curthread->td_user_pri).
887 The function remains undocumented.
890 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
891 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
892 for scalar sysctls is defined but disabled. Code that needs
893 UQUAD to pass the type checking that must compile on older
894 systems where the define is not present can check against
895 __FreeBSD_version >= 900030.
897 The system dialog(1) has been replaced with a new version previously
898 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
899 with the previous version, but the libdialog associated with it has
900 a largely incompatible API. As such, the original version of libdialog
901 will be kept temporarily as libodialog, until its base system consumers
902 are replaced or updated. Bump __FreeBSD_version to 900030.
905 If you are trying to run make universe on a -stable system, and you get
906 the following warning:
907 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
908 unknown. config(8) likely too old."
909 or something similar to it, then you must upgrade your -stable system
910 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
911 stable/8) or build the config from the latest stable/8 branch and
912 install it on your system.
914 Prior to this date, building a current universe on 8-stable system from
915 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
916 error in the first kernel build phase. A new config on those old
917 systems will fix that problem for older versions of -current.
920 The TCP stack has been modified to allow Khelp modules to interact with
921 it via helper hook points and store per-connection data in the TCP
922 control block. Bump __FreeBSD_version to 900029. User space tools that
923 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
927 Generic IEEE 802.3 annex 31B full duplex flow control support has been
928 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
929 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
930 to take advantage of it instead of using custom implementations. This
931 means that these drivers now no longer unconditionally advertise
932 support for flow control but only do so if flow control is a selected
933 media option. This was implemented in the generic support that way in
934 order to allow flow control to be switched on and off via ifconfig(8)
935 with the PHY specific default to typically off in order to protect
936 from unwanted effects. Consequently, if you used flow control with
937 one of the above mentioned drivers you now need to explicitly enable
939 ifconfig bge0 media auto mediaopt flowcontrol
941 Along with the above mentioned changes generic support for setting
942 1000baseT master mode also has been added and brgphy(4), ciphy(4),
943 e1000phy(4) as well as ip1000phy(4) have been converted to take
944 advantage of it. This means that these drivers now no longer take the
945 link0 parameter for selecting master mode but the master media option
946 has to be used instead, for example like in the following:
947 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
949 Selection of master mode now is also available with all other PHY
950 drivers supporting 1000baseT.
953 The TCP stack has received a significant update to add support for
954 modularised congestion control and generally improve the clarity of
955 congestion control decisions. Bump __FreeBSD_version to 900025. User
956 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
957 sockstat) need to be recompiled.
960 The man(1) utility has been replaced by a new version that no longer
961 uses /etc/manpath.config. Please consult man.conf(5) for how to
962 migrate local entries to the new format.
965 The copyright strings printed by login(1) and sshd(8) at the time of a
966 new connection have been removed to follow other operating systems and
970 A workaround for a fixed ld bug has been removed in kernel code,
971 so make sure that your system ld is built from sources after
972 revision 210245 from 2010-07-19 (r211583 if building head kernel
973 on stable/8, r211584 for stable/7; both from 2010-08-21).
974 A symptom of incorrect ld version is different addresses for
975 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
978 The $ipv6_prefer variable in rc.conf(5) has been split into
979 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
981 The $ip6addrctl_policy is a variable to choose a pre-defined
982 address selection policy set by ip6addrctl(8). A value
983 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
986 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
987 flag (see an entry of 20090926) is set on an interface with no
988 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
989 security reason. If you want IPv6 link-local address on all
990 interfaces by default, set this to "YES".
992 The old ipv6_prefer="YES" is equivalent to
993 ipv6_activate_all_interfaces="YES" and
994 ip6addrctl_policy="ipv6_prefer".
997 DTrace has grown support for userland tracing. Due to this, DTrace is
998 now i386 and amd64 only.
999 dtruss(1) is now installed by default on those systems and a new
1000 kernel module is needed for userland tracing: fasttrap.
1001 No changes to your kernel config file are necessary to enable
1002 userland tracing, but you might consider adding 'STRIP=' and
1003 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1004 to have informative userland stack traces in DTrace (ustack).
1007 The acpi_aiboost(4) driver has been removed in favor of the new
1008 aibs(4) driver. You should update your kernel configuration file.
1011 BSD grep has been imported to the base system and it is built by
1012 default. It is completely BSD licensed, highly GNU-compatible, uses
1013 less memory than its GNU counterpart and has a small codebase.
1014 However, it is slower than its GNU counterpart, which is mostly
1015 noticeable for larger searches, for smaller ones it is measurable
1016 but not significant. The reason is complex, the most important factor
1017 is that we lack a modern and efficient regex library and GNU
1018 overcomes this by optimizing the searches internally. Future work
1019 on improving the regex performance is planned, for the meantime,
1020 users that need better performance, can build GNU grep instead by
1021 setting the WITH_GNU_GREP knob.
1024 Due to the import of powerpc64 support, all existing powerpc kernel
1025 configuration files must be updated with a machine directive like this:
1026 machine powerpc powerpc
1028 In addition, an updated config(8) is required to build powerpc kernels
1032 A new version of ZFS (version 15) has been merged to -HEAD.
1033 This version uses a python library for the following subcommands:
1034 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1035 For full functionality of these commands the following port must
1036 be installed: sysutils/py-zfs
1039 'vm_page's are now hashed by physical address to an array of mutexes.
1040 Currently this is only used to serialize access to hold_count. Over
1041 time the page queue mutex will be peeled away. This changes the size
1042 of pmap on every architecture. And requires all callers of vm_page_hold
1043 and vm_page_unhold to be updated.
1046 WITH_CTF can now be specified in src.conf (not recommended, there
1047 are some problems with static executables), make.conf (would also
1048 affect ports which do not use GNU make and do not override the
1049 compile targets) or in the kernel config (via "makeoptions
1051 When WITH_CTF was specified there before this was silently ignored,
1052 so make sure that WITH_CTF is not used in places which could lead
1053 to unwanted behavior.
1056 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1057 to allow 32-bit compatibility on non-x86 platforms. All kernel
1058 configurations on amd64 and ia64 platforms using these options must
1059 be modified accordingly.
1062 The utmp user accounting database has been replaced with utmpx,
1063 the user accounting interface standardized by POSIX.
1064 Unfortunately the semantics of utmp and utmpx don't match,
1065 making it practically impossible to support both interfaces.
1066 The user accounting database is used by tools like finger(1),
1067 last(1), talk(1), w(1) and ac(8).
1069 All applications in the base system use utmpx. This means only
1070 local binaries (e.g. from the ports tree) may still use these
1071 utmp database files. These applications must be rebuilt to make
1074 After the system has been upgraded, it is safe to remove the old
1075 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1076 assuming their contents is of no importance anymore. Old wtmp
1077 databases can only be used by last(1) and ac(8) after they have
1078 been converted to the new format using wtmpcvt(1).
1081 Introduce the kernel thread "deadlock resolver" (which can be enabled
1082 via the DEADLKRES option, see NOTES for more details) and the
1083 sleepq_type() function for sleepqueues.
1086 The rc.firewall and rc.firewall6 were unified, and
1087 rc.firewall6 and rc.d/ip6fw were removed.
1088 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1089 variables are obsoleted. Instead, the following new rc
1090 variables are added to rc.d/ipfw:
1092 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1093 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1094 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1096 The meanings correspond to the relevant IPv4 variables.
1102 The default terminal emulation for syscons(4) has been changed
1103 from cons25 to xterm on all platforms except pc98. This means
1104 that the /etc/ttys file needs to be updated to ensure correct
1105 operation of applications on the console.
1107 The terminal emulation style can be toggled per window by using
1108 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1109 options can be used to change the compile-time default back to
1112 To prevent graphical artifacts, make sure the TERM environment
1113 variable is set to match the terminal emulation that is being
1114 performed by syscons(4).
1117 The layout of the structure ieee80211req_scan_result has changed.
1118 Applications that require wireless scan results (e.g. ifconfig(8))
1119 from net80211 need to be recompiled.
1121 Applications such as wpa_supplicant(8) may require a full world
1122 build without using NO_CLEAN in order to get synchronized with the
1126 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1127 There's one kernel module for each firmware. Adding "device iwnfw"
1128 to the kernel configuration file means including all three firmware
1129 images inside the kernel. If you want to include just the one for
1130 your wireless card, use the devices iwn4965fw, iwn5000fw or
1134 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1135 into rc.d/netif. The changes are the following:
1137 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1138 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1139 Note that both variables need the "inet6" keyword at the head.
1141 Do not set $ipv6_network_interfaces manually if you do not
1142 understand what you are doing. It is not needed in most cases.
1144 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1147 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1148 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1150 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1151 all configured interfaces have "inet6 accept_rtadv" in the
1152 $ifconfig_IF_ipv6. These are for backward compatibility.
1154 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1155 functionality of interfaces with no corresponding
1156 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1157 and the default address selection policy of ip6addrctl(8)
1158 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1159 Note that if you want to configure IPv6 functionality on the
1160 disabled interfaces after boot, first you need to clear the flag by
1161 using ifconfig(8) like:
1163 ifconfig em0 inet6 -ifdisabled
1165 If YES, the default address selection policy is set as
1168 The default value of $ipv6_prefer is NO.
1170 4. If your system need to receive Router Advertisement messages,
1171 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1172 scripts automatically invoke rtsol(8) when the interface becomes
1173 UP. The Router Advertisement messages are used for SLAAC
1174 (State-Less Address AutoConfiguration).
1177 802.11s D3.03 support was committed. This is incompatible with the
1178 previous code, which was based on D3.0.
1181 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1182 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1183 control whether accepting Router Advertisement messages or not.
1184 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1185 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1186 The ifconfig(8) utility now supports these flags.
1189 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1190 mount(8) and -a option for df(1) to see them.
1193 The old tunable hw.bus.devctl_disable has been superseded by
1194 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1195 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1199 Remove the option STOP_NMI. The default action is now to use NMI only
1200 for KDB via the newly introduced function stop_cpus_hard() and
1201 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1204 The stable/8 branch created in subversion. This corresponds to the
1205 RELENG_8 branch in CVS.
1208 Bump the shared library version numbers for all libraries that do not
1209 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1210 __FreeBSD_version to 800105.
1213 Due to changes in the implementation of virtual network stack support,
1214 all network-related kernel modules must be recompiled. As this change
1215 breaks the ABI, bump __FreeBSD_version to 800104.
1218 The TOE interface to the TCP syncache has been modified to remove
1219 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1220 The cxgb driver is the only TOE consumer affected by this change, and
1221 needs to be recompiled along with the kernel. As this change breaks
1222 the ABI, bump __FreeBSD_version to 800103.
1225 Padding has been added to struct tcpcb, sackhint and tcpstat in
1226 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1227 maintaining the ABI. However, this change breaks the ABI, so bump
1228 __FreeBSD_version to 800102. User space tools that rely on the size of
1229 any of these structs (e.g. sockstat) need to be recompiled.
1232 The NFS_LEGACYRPC option has been removed along with the old kernel
1233 RPC implementation that this option selected. Kernel configurations
1234 may need to be adjusted.
1237 The network interface device nodes at /dev/net/<interface> have been
1238 removed. All ioctl operations can be performed the normal way using
1239 routing sockets. The kqueue functionality can generally be replaced
1240 with routing sockets.
1243 The documentation from the FreeBSD Documentation Project (Handbook,
1244 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1245 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1248 The ABI of various structures related to the SYSV IPC API have been
1249 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1250 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1254 Layout of struct vnet has changed as routing related variables were
1255 moved to their own Vimage module. Modules need to be recompiled. Bump
1256 __FreeBSD_version to 800099.
1259 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1260 respectively. As long as no more than 16 groups per process are used,
1261 no changes should be visible. When more than 16 groups are used, old
1262 binaries may fail if they call getgroups() or getgrouplist() with
1263 statically sized storage. Recompiling will work around this, but
1264 applications should be modified to use dynamically allocated storage
1265 for group arrays as POSIX.1-2008 does not cap an implementation's
1266 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1268 NFS and portalfs mounts may also be affected as the list of groups is
1269 truncated to 16. Users of NFS who use more than 16 groups, should
1270 take care that negative group permissions are not used on the exported
1271 file systems as they will not be reliable unless a GSSAPI based
1272 authentication method is used.
1275 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1276 option compiles in the support for adaptive spinning for lockmgrs
1277 which want to enable it. The lockinit() function now accepts the flag
1278 LK_ADAPTIVE in order to make the lock object subject to adaptive
1279 spinning when both held in write and read mode.
1282 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1283 changed. User applications that use this ioctl need to be rebuilt.
1286 The layout of struct thread has changed. Kernel and modules need to
1290 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1291 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1294 window(1) has been removed from the base system. It can now be
1295 installed from ports. The port is called misc/window.
1298 The way we are storing and accessing `routing table' entries has
1299 changed. Programs reading the FIB, like netstat, need to be
1303 A new netisr implementation has been added for FreeBSD 8. Network
1304 file system modules, such as igmp, ipdivert, and others, should be
1306 Bump __FreeBSD_version to 800096.
1309 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1313 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1314 Bump __FreeBSD_version to 800094.
1317 Add mnt_xflag field to 'struct mount'. File system modules need to be
1319 Bump __FreeBSD_version to 800093.
1322 The compiling option ADAPTIVE_SX has been retired while it has been
1323 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1324 The KPI for sx_init_flags() changes as accepting flags:
1325 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1326 been introduced in order to handle the reversed logic.
1327 Bump __FreeBSD_version to 800092.
1330 Add support for hierarchical jails. Remove global securelevel.
1331 Bump __FreeBSD_version to 800091.
1334 The layout of struct vnet_net has changed, therefore modules
1336 Bump __FreeBSD_version to 800090.
1339 The newly imported zic(8) produces a new format in the output. Please
1340 run tzsetup(8) to install the newly created data to /etc/localtime.
1343 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1344 hw.usb.* and is now consistent again with previous releases.
1347 802.11 monitor mode support was revised and driver api's were changed.
1348 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1349 of DLT_IEEE802_11. No user-visible data structures were changed but
1350 applications that use DLT_IEEE802_11 may require changes.
1351 Bump __FreeBSD_version to 800088.
1354 The layout of the following structs has changed: sysctl_oid,
1355 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1356 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1357 panics may be experienced. World rebuild is required for
1358 correctly checking networking state from userland.
1359 Bump __FreeBSD_version to 800085.
1362 MLDv2 and Source-Specific Multicast (SSM) have been merged
1363 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1364 The implementation of SSM within FreeBSD's IPv6 stack closely
1365 follows the IPv4 implementation.
1367 For kernel developers:
1369 * The most important changes are that the ip6_output() and
1370 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1371 and this lock has been downgraded to a non-recursive mutex.
1373 * As with the changes to the IPv4 stack to support SSM, filtering
1374 of inbound multicast traffic must now be performed by transport
1375 protocols within the IPv6 stack. This does not apply to TCP and
1376 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1378 * The KPIs used by IPv6 multicast are similar to those used by
1379 the IPv4 stack, with the following differences:
1380 * im6o_mc_filter() is analogous to imo_multicast_filter().
1381 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1382 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1383 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1384 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1385 for MLDv1 have an additional 'timer' argument which is used to
1386 jitter the initial membership report for the solicited-node
1387 multicast membership on-link.
1388 * This is not strictly needed for MLDv2, which already jitters
1389 its report transmissions. However, the 'timer' argument is
1390 preserved in case MLDv1 is active on the interface.
1392 * The KAME linked-list based IPv6 membership implementation has
1393 been refactored to use a vector similar to that used by the IPv4
1395 Code which maintains a list of its own multicast memberships
1396 internally, e.g. carp, has been updated to reflect the new
1399 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1400 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1401 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1402 implementation constraint which needs to be addressed in HEAD.
1404 For application developers:
1406 * The changes are broadly similar to those made for the IPv4
1409 * The use of IPv4 and IPv6 multicast socket options on the same
1410 socket, using mapped addresses, HAS NOT been tested or supported.
1412 * There are a number of issues with the implementation of various
1413 IPv6 multicast APIs which need to be resolved in the API surface
1414 before the implementation is fully compatible with KAME userland
1415 use, and these are mostly to do with interface index treatment.
1417 * The literature available discusses the use of either the delta / ASM
1418 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1419 using setsourcefilter(3)/getsourcefilter(3). For more information
1420 please refer to RFC 3768, 'Socket Interface Extensions for
1421 Multicast Source Filters'.
1423 * Applications which use the published RFC 3678 APIs should be fine.
1425 For systems administrators:
1427 * The mtest(8) utility has been refactored to support IPv6, in
1428 addition to IPv4. Interface addresses are no longer accepted
1429 as arguments, their names must be used instead. The utility
1430 will map the interface name to its first IPv4 address as
1431 returned by getifaddrs(3).
1433 * The ifmcstat(8) utility has also been updated to print the MLDv2
1434 endpoint state and source filter lists via sysctl(3).
1436 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1437 loopback of IPv6 multicast datagrams by default; it defaults to 1
1438 to preserve the existing behaviour. Disabling multicast loopback is
1439 recommended for optimal system performance.
1441 * The IPv6 MROUTING code has been changed to examine this sysctl
1442 instead of attempting to perform a group lookup before looping
1443 back forwarded datagrams.
1445 Bump __FreeBSD_version to 800084.
1448 Implement low-level Bluetooth HCI API.
1449 Bump __FreeBSD_version to 800083.
1452 The layout of struct malloc_type, used by modules to register new
1453 memory allocation types, has changed. Most modules will need to
1454 be rebuilt or panics may be experienced.
1455 Bump __FreeBSD_version to 800081.
1458 Anticipate overflowing inp_flags - add inp_flags2.
1459 This changes most offsets in inpcb, so checking v4 connection
1460 state will require a world rebuild.
1461 Bump __FreeBSD_version to 800080.
1464 Add an llentry to struct route and struct route_in6. Modules
1465 embedding a struct route will need to be recompiled.
1466 Bump __FreeBSD_version to 800079.
1469 The size of rt_metrics_lite and by extension rtentry has changed.
1470 Networking administration apps will need to be recompiled.
1471 The route command now supports show as an alias for get, weighting
1472 of routes, sticky and nostick flags to alter the behavior of stateful
1474 Bump __FreeBSD_version to 800078.
1477 Do not use Giant for kbdmux(4) locking. This is wrong and
1478 apparently causing more problems than it solves. This will
1479 re-open the issue where interrupt handlers may race with
1480 kbdmux(4) in polling mode. Typical symptoms include (but
1481 not limited to) duplicated and/or missing characters when
1482 low level console functions (such as gets) are used while
1483 interrupts are enabled (for example geli password prompt,
1484 mountroot prompt etc.). Disabling kbdmux(4) may help.
1487 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1488 kernel modules referencing any of the above need to be recompiled.
1489 Bump __FreeBSD_version to 800075.
1492 GEOM_PART has become the default partition slicer for storage devices,
1493 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1494 introduces some changes:
1496 MSDOS/EBR: the devices created from MSDOS extended partition entries
1497 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1498 to devices with offset-based names. fstabs may need to be modified.
1500 BSD: the "geometry does not match label" warning is harmless in most
1501 cases but it points to problems in file system misalignment with
1502 disk geometry. The "c" partition is now implicit, covers the whole
1503 top-level drive and cannot be (mis)used by users.
1505 General: Kernel dumps are now not allowed to be written to devices
1506 whose partition types indicate they are meant to be used for file
1507 systems (or, in case of MSDOS partitions, as something else than
1510 Most of these changes date approximately from 200812.
1513 The uscanner(4) driver has been removed from the kernel. This follows
1514 Linux removing theirs in 2.6 and making libusb the default interface
1515 (supported by sane).
1518 The multicast forwarding code has been cleaned up. netstat(1)
1519 only relies on KVM now for printing bandwidth upcall meters.
1520 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1521 ip6_mroute_mod respectively. The config(5) options for statically
1522 compiling this code remain the same, i.e. 'options MROUTING'.
1525 Support for the IFF_NEEDSGIANT network interface flag has been
1526 removed, which means that non-MPSAFE network device drivers are no
1527 longer supported. In particular, if_ar, if_sr, and network device
1528 drivers from the old (legacy) USB stack can no longer be built or
1532 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1533 a bunch of new language catalog files have also been added.
1534 This means that some common libc messages are now localized and
1535 they depend on the LC_MESSAGES environmental variable.
1538 The k8temp(4) driver has been renamed to amdtemp(4) since
1539 support for Family 10 and Family 11 CPU families was added.
1542 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1543 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1545 For kernel developers, the most important changes are that the
1546 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1547 and this lock has been downgraded to a non-recursive mutex.
1549 Transport protocols (UDP, Raw IP) are now responsible for filtering
1550 inbound multicast traffic according to group membership and source
1551 filters. The imo_multicast_filter() KPI exists for this purpose.
1552 Transports which do not use multicast (SCTP, TCP) already reject
1553 multicast by default. Forwarding and receive performance may improve
1554 as a mutex acquisition is no longer needed in the ip_input()
1555 low-level input path. in_addmulti() and in_delmulti() are shimmed
1556 to new KPIs which exist to support SSM in-kernel.
1558 For application developers, it is recommended that loopback of
1559 multicast datagrams be disabled for best performance, as this
1560 will still cause the lock to be taken for each looped-back
1561 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1562 be tuned to 0 to disable loopback by default; it defaults to 1
1563 to preserve the existing behaviour.
1565 For systems administrators, to obtain best performance with
1566 multicast reception and multiple groups, it is always recommended
1567 that a card with a suitably precise hash filter is used. Hash
1568 collisions will still result in the lock being taken within the
1569 transport protocol input path to check group membership.
1571 If deploying FreeBSD in an environment with IGMP snooping switches,
1572 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1573 enabled; this forces 224.0.0.0/24 group membership to be announced
1576 The size of 'struct igmpstat' has changed; netstat needs to be
1577 recompiled to reflect this.
1578 Bump __FreeBSD_version to 800070.
1581 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1582 updated to use it. This requires a buildworld/installworld in order to
1583 update the library and dependencies (usbconfig, etc). Its advisable to
1584 rebuild all ports which uses libusb. More specific directions are given
1585 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1586 libusb are no longer required and can be removed.
1589 A workaround is committed to allow the creation of System V shared
1590 memory segment of size > 2 GB on the 64-bit architectures.
1591 Due to a limitation of the existing ABI, the shm_segsz member
1592 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1593 wrong for large segments. Note that limits must be explicitly
1594 raised to allow such segments to be created.
1597 The layout of struct ifnet has changed, requiring a rebuild of all
1598 network device driver modules.
1601 The /dev handling for the new USB stack has changed, a
1602 buildworld/installworld is required for libusb20.
1605 The new USB2 stack has now been permanently moved in and all kernel and
1606 module names reverted to their previous values (eg, usb, ehci, ohci,
1607 ums, ...). The old usb stack can be compiled in by prefixing the name
1608 with the letter 'o', the old usb modules have been removed.
1609 Updating entry 20090216 for xorg and 20090215 for libmap may still
1613 The rc.conf(5) option if_up_delay has been renamed to
1614 defaultroute_delay to better reflect its purpose. If you have
1615 customized this setting in /etc/rc.conf you need to update it to
1619 xorg 7.4 wants to configure its input devices via hald which does not
1620 yet work with USB2. If the keyboard/mouse does not work in xorg then
1622 Option "AllowEmptyInput" "off"
1623 to your ServerLayout section. This will cause X to use the configured
1624 kbd and mouse sections from your xorg.conf.
1627 The GENERIC kernels for all architectures now default to the new USB2
1628 stack. No kernel config options or code have been removed so if a
1629 problem arises please report it and optionally revert to the old USB
1630 stack. If you are loading USB kernel modules or have a custom kernel
1631 that includes GENERIC then ensure that usb names are also changed over,
1632 eg uftdi -> usb2_serial_ftdi.
1634 Older programs linked against the ports libusb 0.1 need to be
1635 redirected to the new stack's libusb20. /etc/libmap.conf can
1637 # Map old usb library to new one for usb2 stack
1638 libusb-0.1.so.8 libusb20.so.1
1641 All USB ethernet devices now attach as interfaces under the name ueN
1642 (eg. ue0). This is to provide a predictable name as vendors often
1643 change usb chipsets in a product without notice.
1646 The ichsmb(4) driver has been changed to require SMBus slave
1647 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1648 All of the other SMBus controller drivers require left-justified
1649 slave addresses, so this change makes all the drivers provide the
1653 INET6 statistics (struct ip6stat) was updated.
1654 netstat(1) needs to be recompiled.
1657 NTFS has been removed from GENERIC kernel on amd64 to match
1658 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1659 will load ntfs.ko module automatically when NTFS support is
1660 actually needed, unless ntfs.ko is not installed or security
1661 level prohibits loading kernel modules. If either is the case,
1662 "options NTFS" has to be added into kernel config.
1665 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1666 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1667 800061. User space tools that rely on the size of struct tcpcb in
1668 tcp_var.h (e.g. sockstat) need to be recompiled.
1671 ng_tty(4) module updated to match the new TTY subsystem.
1672 Due to API change, user-level applications must be updated.
1673 New API support added to mpd5 CVS and expected to be present
1674 in next mpd5.3 release.
1677 With __FreeBSD_version 800060 the makefs tool is part of
1678 the base system (it was a port).
1681 The afdata and ifnet locks have been changed from mutexes to
1682 rwlocks, network modules will need to be re-compiled.
1685 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1686 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1687 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1688 architecture and 40 bytes on 64-bit architecture. The userland
1689 applications "arp" and "ndp" have been updated accordingly.
1690 The output from "netstat -r" shows only routing entries and
1691 none of the L2 information.
1694 __FreeBSD_version 800057 marks the switchover from the
1695 binary ath hal to source code. Users must add the line:
1697 options AH_SUPPORT_AR5416
1699 to their kernel config files when specifying:
1703 The ath_hal module no longer exists; the code is now compiled
1704 together with the driver in the ath module. It is now
1705 possible to tailor chip support (i.e. reduce the set of chips
1706 and thereby the code size); consult ath_hal(4) for details.
1709 __FreeBSD_version 800054 adds memory barriers to
1710 <machine/atomic.h>, new interfaces to ifnet to facilitate
1711 multiple hardware transmit queues for cards that support
1712 them, and a lock-less ring-buffer implementation to
1713 enable drivers to more efficiently manage queueing of
1717 A new version of ZFS (version 13) has been merged to -HEAD.
1718 This version has zpool attribute "listsnapshots" off by
1719 default, which means "zfs list" does not show snapshots,
1720 and is the same as Solaris behavior.
1723 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1726 The uhci, ohci, ehci and slhci USB Host controller drivers have
1727 been put into separate modules. If you load the usb module
1728 separately through loader.conf you will need to load the
1729 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1730 controller add the following to loader.conf:
1736 The ABI used by the PMC toolset has changed. Please keep
1737 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1741 atapci kernel module now includes only generic PCI ATA
1742 driver. AHCI driver moved to ataahci kernel module.
1743 All vendor-specific code moved into separate kernel modules:
1744 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1745 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1746 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1747 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1750 The TTY subsystem of the kernel has been replaced by a new
1751 implementation, which provides better scalability and an
1752 improved driver model. Most common drivers have been migrated to
1753 the new TTY subsystem, while others have not. The following
1754 drivers have not yet been ported to the new TTY layer:
1757 cy, digi, rc, rp, sio
1763 ng_h4, ng_tty, ppp, sl, snp
1765 Adding these drivers to your kernel configuration file shall
1766 cause compilation to fail.
1769 ntpd has been upgraded to 4.2.4p5.
1772 OpenSSH has been upgraded to 5.1p1.
1774 For many years, FreeBSD's version of OpenSSH preferred DSA
1775 over RSA for host and user authentication keys. With this
1776 upgrade, we've switched to the vendor's default of RSA over
1777 DSA. This may cause upgraded clients to warn about unknown
1778 host keys even for previously known hosts. Users should
1779 follow the usual procedure for verifying host keys before
1780 accepting the RSA key.
1782 This can be circumvented by setting the "HostKeyAlgorithms"
1783 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1786 Please note that the sequence of keys offered for
1787 authentication has been changed as well. You may want to
1788 specify IdentityFile in a different order to revert this
1792 The sio(4) driver has been removed from the i386 and amd64
1793 kernel configuration files. This means uart(4) is now the
1794 default serial port driver on those platforms as well.
1796 To prevent collisions with the sio(4) driver, the uart(4) driver
1797 uses different names for its device nodes. This means the
1798 onboard serial port will now most likely be called "ttyu0"
1799 instead of "ttyd0". You may need to reconfigure applications to
1800 use the new device names.
1802 When using the serial port as a boot console, be sure to update
1803 /boot/device.hints and /etc/ttys before booting the new kernel.
1804 If you forget to do so, you can still manually specify the hints
1805 at the loader prompt:
1807 set hint.uart.0.at="isa"
1808 set hint.uart.0.port="0x3F8"
1809 set hint.uart.0.flags="0x10"
1810 set hint.uart.0.irq="4"
1814 The gpt(8) utility has been removed. Use gpart(8) to partition
1818 The version that Linuxulator emulates was changed from 2.4.2
1819 to 2.6.16. If you experience any problems with Linux binaries
1820 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1821 if it fixes the problem contact emulation mailing list.
1824 ISDN4BSD (I4B) was removed from the src tree. You may need to
1825 update a your kernel configuration and remove relevant entries.
1828 I have checked in code to support multiple routing tables.
1829 See the man pages setfib(1) and setfib(2).
1830 This is a hopefully backwards compatible version,
1831 but to make use of it you need to compile your kernel
1832 with options ROUTETABLES=2 (or more up to 16).
1835 The 802.11 wireless support was redone to enable multi-bss
1836 operation on devices that are capable. The underlying device
1837 is no longer used directly but instead wlanX devices are
1838 cloned with ifconfig. This requires changes to rc.conf files.
1839 For example, change:
1840 ifconfig_ath0="WPA DHCP"
1843 ifconfig_wlan0="WPA DHCP"
1844 see rc.conf(5) for more details. In addition, mergemaster of
1845 /etc/rc.d is highly recommended. Simultaneous update of userland
1846 and kernel wouldn't hurt either.
1848 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1849 modules were merged into the base wlan module. All references
1850 to these modules (e.g. in kernel config files) must be removed.
1853 psm(4) has gained write(2) support in native operation level.
1854 Arbitrary commands can be written to /dev/psm%d and status can
1855 be read back from it. Therefore, an application is responsible
1856 for status validation and error recovery. It is a no-op in
1857 other operation levels.
1860 Support for KSE threading has been removed from the kernel. To
1861 run legacy applications linked against KSE libmap.conf may
1862 be used. The following libmap.conf may be used to ensure
1863 compatibility with any prior release:
1865 libpthread.so.1 libthr.so.1
1866 libpthread.so.2 libthr.so.2
1867 libkse.so.3 libthr.so.3
1870 The layout of struct vmspace has changed. This affects libkvm
1871 and any executables that link against libkvm and use the
1872 kvm_getprocs() function. In particular, but not exclusively,
1873 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1874 The effects are minimal, but it's advisable to upgrade world
1878 The latest em driver no longer has support in it for the
1879 82575 adapter, this is now moved to the igb driver. The
1880 split was done to make new features that are incompatible
1881 with older hardware easier to do.
1884 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1885 likewise the kernel option is now GEOM_LINUX_LVM.
1888 The default NFS mount mode has changed from UDP to TCP for
1889 increased reliability. If you rely on (insecurely) NFS
1890 mounting across a firewall you may need to update your
1894 Belatedly note the addition of m_collapse for compacting
1898 The fts(3) structures have been changed to use adequate
1899 integer types for their members and so to be able to cope
1900 with huge file trees. The old fts(3) ABI is preserved
1901 through symbol versioning in libc, so third-party binaries
1902 using fts(3) should still work, although they will not take
1903 advantage of the extended types. At the same time, some
1904 third-party software might fail to build after this change
1905 due to unportable assumptions made in its source code about
1906 fts(3) structure members. Such software should be fixed
1907 by its vendor or, in the worst case, in the ports tree.
1908 FreeBSD_version 800015 marks this change for the unlikely
1909 case that a portable fix is impossible.
1912 To upgrade to -current after this date, you must be running
1913 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1914 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1917 The ADAPTIVE_GIANT kernel option has been retired because its
1918 functionality is the default now.
1921 The AT keyboard emulation of sunkbd(4) has been turned on
1922 by default. In order to make the special symbols of the Sun
1923 keyboards driven by sunkbd(4) work under X these now have
1924 to be configured the same way as Sun USB keyboards driven
1925 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1927 Option "XkbLayout" "us"
1928 Option "XkbRules" "xorg"
1929 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1932 It has been decided that it is desirable to provide ABI
1933 backwards compatibility to the FreeBSD 4/5/6 versions of the
1934 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1935 broken with the introduction of PCI domain support (see the
1936 20070930 entry). Unfortunately, this required the ABI of
1937 PCIOCGETCONF to be broken again in order to be able to
1938 provide backwards compatibility to the old version of that
1939 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1940 again. As for prominent ports this affects neither pciutils
1941 nor xorg-server this time, the hal port needs to be rebuilt
1945 The misnamed kthread_create() and friends have been renamed
1946 to kproc_create() etc. Many of the callers already
1947 used kproc_start()..
1948 I will return kthread_create() and friends in a while
1949 with implementations that actually create threads, not procs.
1950 Renaming corresponds with version 800002.
1959 Avoid using make -j when upgrading. While generally safe, there are
1960 sometimes problems using -j to upgrade. If your upgrade fails with
1961 -j, please try again without -j. From time to time in the past there
1962 have been problems using -j with buildworld and/or installworld. This
1963 is especially true when upgrading between "distant" versions (eg one
1964 that cross a major release boundary or several minor releases, or when
1965 several months have passed on the -current branch).
1967 Sometimes, obscure build problems are the result of environment
1968 poisoning. This can happen because the make utility reads its
1969 environment when searching for values for global variables. To run
1970 your build attempts in an "environmental clean room", prefix all make
1971 commands with 'env -i '. See the env(1) manual page for more details.
1973 When upgrading from one major version to another it is generally best
1974 to upgrade to the latest code in the currently installed branch first,
1975 then do an upgrade to the new branch. This is the best-tested upgrade
1976 path, and has the highest probability of being successful. Please try
1977 this approach before reporting problems with a major version upgrade.
1979 When upgrading a live system, having a root shell around before
1980 installing anything can help undo problems. Not having a root shell
1981 around can lead to problems if pam has changed too much from your
1982 starting point to allow continued authentication after the upgrade.
1986 When upgrading the boot ZFS pool to a new version, always follow
1989 1.) recompile and reinstall the ZFS boot loader and boot block
1990 (this is part of "make buildworld" and "make installworld")
1992 2.) update the ZFS boot block on your boot drive
1994 The following example updates the ZFS boot block on the first
1995 partition (freebsd-boot) of a GPT partitioned drive ad0:
1996 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1998 Non-boot pools do not need these updates.
2002 If you are updating from a prior version of FreeBSD (even one just
2003 a few days old), you should follow this procedure. It is the most
2004 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2006 make kernel-toolchain
2007 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2008 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2010 To test a kernel once
2011 ---------------------
2012 If you just want to boot a kernel once (because you are not sure
2013 if it works, or if you want to boot a known bad kernel to provide
2014 debugging information) run
2015 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2016 nextboot -k testkernel
2018 To just build a kernel when you know that it won't mess you up
2019 --------------------------------------------------------------
2020 This assumes you are already running a CURRENT system. Replace
2021 ${arch} with the architecture of your machine (e.g. "i386",
2022 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2024 cd src/sys/${arch}/conf
2025 config KERNEL_NAME_HERE
2026 cd ../compile/KERNEL_NAME_HERE
2031 If this fails, go to the "To build a kernel" section.
2033 To rebuild everything and install it on the current system.
2034 -----------------------------------------------------------
2035 # Note: sometimes if you are running current you gotta do more than
2036 # is listed here if you are upgrading from a really old current.
2038 <make sure you have good level 0 dumps>
2040 make kernel KERNCONF=YOUR_KERNEL_HERE
2042 <reboot in single user> [3]
2049 To cross-install current onto a separate partition
2050 --------------------------------------------------
2051 # In this approach we use a separate partition to hold
2052 # current's root, 'usr', and 'var' directories. A partition
2053 # holding "/", "/usr" and "/var" should be about 2GB in
2056 <make sure you have good level 0 dumps>
2059 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2060 <maybe newfs current's root partition>
2061 <mount current's root partition on directory ${CURRENT_ROOT}>
2062 make installworld DESTDIR=${CURRENT_ROOT}
2063 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2064 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2065 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2066 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2067 <reboot into current>
2068 <do a "native" rebuild/install as described in the previous section>
2069 <maybe install compatibility libraries from ports/misc/compat*>
2073 To upgrade in-place from stable to current
2074 ----------------------------------------------
2075 <make sure you have good level 0 dumps>
2077 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2079 <reboot in single user> [3]
2086 Make sure that you've read the UPDATING file to understand the
2087 tweaks to various things you need. At this point in the life
2088 cycle of current, things change often and you are on your own
2089 to cope. The defaults can also change, so please read ALL of
2090 the UPDATING entries.
2092 Also, if you are tracking -current, you must be subscribed to
2093 freebsd-current@freebsd.org. Make sure that before you update
2094 your sources that you have read and understood all the recent
2095 messages there. If in doubt, please track -stable which has
2096 much fewer pitfalls.
2098 [1] If you have third party modules, such as vmware, you
2099 should disable them at this point so they don't crash your
2102 [3] From the bootblocks, boot -s, and then do
2107 adjkerntz -i # if CMOS is wall time
2108 Also, when doing a major release upgrade, it is required that
2109 you boot into single user mode to do the installworld.
2111 [4] Note: This step is non-optional. Failure to do this step
2112 can result in a significant reduction in the functionality of the
2113 system. Attempting to do it by hand is not recommended and those
2114 that pursue this avenue should read this file carefully, as well
2115 as the archives of freebsd-current and freebsd-hackers mailing lists
2116 for potential gotchas. The -U option is also useful to consider.
2117 See mergemaster(8) for more information.
2119 [5] Usually this step is a noop. However, from time to time
2120 you may need to do this if you get unknown user in the following
2121 step. It never hurts to do it all the time. You may need to
2122 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2123 install) after the buildworld before this step if you last updated
2124 from current before 20130425 or from -stable before 20130430.
2126 [6] This only deletes old files and directories. Old libraries
2127 can be deleted by "make delete-old-libs", but you have to make
2128 sure that no program is using those libraries anymore.
2130 [8] In order to have a kernel that can run the 4.x binaries needed to
2131 do an installworld, you must include the COMPAT_FREEBSD4 option in
2132 your kernel. Failure to do so may leave you with a system that is
2133 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2134 required to run the 5.x binaries on more recent kernels. And so on
2135 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2137 Make sure that you merge any new devices from GENERIC since the
2138 last time you updated your kernel config file.
2140 [9] When checking out sources, you must include the -P flag to have
2141 cvs prune empty directories.
2143 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2144 "?=" instead of the "=" assignment operator, so that buildworld can
2145 override the CPUTYPE if it needs to.
2147 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2148 not on the command line, or in /etc/make.conf. buildworld will
2149 warn if it is improperly defined.
2152 This file contains a list, in reverse chronological order, of major
2153 breakages in tracking -current. It is not guaranteed to be a complete
2154 list of such breakages, and only contains entries since October 10, 2007.
2155 If you need to see UPDATING entries from before that date, you will need
2156 to fetch an UPDATING file from an older FreeBSD release.
2158 Copyright information:
2160 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2162 Redistribution, publication, translation and use, with or without
2163 modification, in full or in part, in any form or format of this
2164 document are permitted without further permission from the author.
2166 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2167 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2168 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2169 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2170 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2171 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2172 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2173 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2174 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2175 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2176 POSSIBILITY OF SUCH DAMAGE.
2178 Contact Warner Losh if you have any questions about your use of