1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of
16 stable/10, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
20 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
21 defined in symlink(7); previously symlinks were silently ignored.
24 The const qualifier has been removed from iconv(3) to comply with
25 POSIX. The ports tree is aware of this from r384038 onwards.
28 At svn r275807, The default linux compat kernel ABI has been adjusted
29 to 2.6.18 in support of the linux-c6 compat ports infrastructure
30 update. If you wish to continue using the linux-f10 compat ports,
31 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
32 encouraged to update their linux-compat packages to linux-c6 during
33 their next update cycle.
35 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
38 pjdfstest has been integrated into kyua as an opt-in test suite.
39 Please see share/doc/pjdfstest/README for a more details on how to
46 The ofwfb driver, used to provide a graphics console on PowerPC when
47 using vt(4), no longer allows mmap() of all of physical memory. This
48 will prevent Xorg on PowerPC with some ATI graphics cards from
49 initializing properly unless x11-servers/xorg-server is updated to
53 The libatf-c and libatf-c++ major versions were downgraded to 0 and
54 1 respectively to match the upstream numbers. They were out of
55 sync because, when they were originally added to FreeBSD, the
56 upstream versions were not respected. These libraries are private
57 and not yet built by default, so renumbering them should be a
58 non-issue. However, unclean source trees will yield broken test
59 programs once the operator executes "make delete-old-libs" after a
62 Additionally, the atf-sh binary was made private by moving it into
63 /usr/libexec/. Already-built shell test programs will keep the
64 path to the old binary so they will break after "make delete-old"
67 If you are using WITH_TESTS=yes (not the default), wipe the object
68 tree and rebuild from scratch to prevent spurious test failures.
69 This is only needed once: the misnumbered libraries and misplaced
70 binaries have been added to OptionalObsoleteFiles.inc so they will
71 be removed during a clean upgrade.
74 The ixgbe tunables now match their sysctl counterparts, for example:
75 hw.ixgbe.enable_aim => hw.ix.enable_aim
76 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
79 The NFSv4.1 server committed by r269398 changes the internal
80 function call interfaces used between the NFS and krpc modules.
81 As such, __FreeBSD_version was bumped.
84 The default unbound configuration has been modified to address
85 issues with reverse lookups on networks that use private
86 address ranges. If you use the local_unbound service, run
87 "service local_unbound setup" as root to regenerate your
88 configuration, then "service local_unbound reload" to load the
92 It is no longer necessary to include the dwarf version in your DEBUG
93 options in your kernel config file. The bug that required it to be
94 placed in the config file has bene fixed. DEBUG should now just
95 contain -g. The build system will automatically update things
96 to do the right thing.
99 Several ABI breaking changes were merged to CTL and new iSCSI code.
100 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
101 iscsictl need to be rebuilt to work with a new kernel.
104 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
105 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
106 which differs from the behaviour controlled by this knob.)
109 On i386 and amd64 systems, the onifconsole flag is now set by default
110 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
111 as a login TTY if it is set in the bootloader as an active kernel
112 console. No changes in behavior should result otherwise. To revert to
113 the previous behavior, set ttyu0 to "off" in /etc/ttys.
116 Clang and llvm have been upgraded to 3.4.1 release.
119 Clang and llvm have been upgraded to 3.4 release.
122 If a Makefile in a tests/ directory was auto-generating a Kyuafile
123 instead of providing an explicit one, this would prevent such
124 Makefile from providing its own Kyuafile in the future during
125 NO_CLEAN builds. This has been fixed in the Makefiles but manual
126 intervention is needed to clean an objdir if you use NO_CLEAN:
127 # find /usr/obj -name Kyuafile | xargs rm -f
130 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
131 capability mode support. Please note that enabling the feature in
132 kernel is still highly recommended.
135 OpenSSH is now built with sandbox support, and will use sandbox as
136 the default privilege separation method. This requires Capsicum
137 capability mode support in kernel.
140 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
141 been deprecated and will not be part of FreeBSD 11.0 and later
142 releases. If you use this driver, please consider switching to
143 the nfe(4) driver instead.
149 The behavior of gss_pseudo_random() for the krb5 mechanism
150 has changed, for applications requesting a longer random string
151 than produced by the underlying enctype's pseudo-random() function.
152 In particular, the random string produced from a session key of
153 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
154 be different at the 17th octet and later, after this change.
155 The counter used in the PRF+ construction is now encoded as a
156 big-endian integer in accordance with RFC 4402.
157 __FreeBSD_version is bumped to 1000701.
160 The WITHOUT_ATF build knob has been removed and its functionality
161 has been subsumed into the more generic WITHOUT_TESTS. If you were
162 using the former to disable the build of the ATF libraries, you
163 should change your settings to use the latter.
166 The default version of mtree is nmtree which is obtained from
167 NetBSD. The output is generally the same, but may vary
168 slightly. If you found you need identical output adding
169 "-F freebsd9" to the command line should do the trick. For the
170 time being, the old mtree is available as fmtree.
173 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
174 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
175 1.1.4_8 and verify bsdyml not linked in, before running "make
177 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
179 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
182 The rc.d/jail script has been updated to support jail(8)
183 configuration file. The "jail_<jname>_*" rc.conf(5) variables
184 for per-jail configuration are automatically converted to
185 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
186 This is transparently backward compatible. See below about some
187 incompatibilities and rc.conf(5) manual page for more details.
189 These variables are now deprecated in favor of jail(8) configuration
190 file. One can use "rc.d/jail config <jname>" command to generate
191 a jail(8) configuration file in /var/run/jail.<jname>.conf without
192 running the jail(8) utility. The default pathname of the
193 configuration file is /etc/jail.conf and can be specified by
194 using $jail_conf or $jail_<jname>_conf variables.
196 Please note that jail_devfs_ruleset accepts an integer at
197 this moment. Please consider to rewrite the ruleset name
201 BIND has been removed from the base system. If all you need
202 is a local resolver, simply enable and start the local_unbound
203 service instead. Otherwise, several versions of BIND are
204 available in the ports tree. The dns/bind99 port is one example.
206 With this change, nslookup(1) and dig(1) are no longer in the base
207 system. Users should instead use host(1) and drill(1) which are
208 in the base system. Alternatively, nslookup and dig can
209 be obtained by installing the dns/bind-tools port.
212 With the addition of unbound(8), a new unbound user is now
213 required during installworld. "mergemaster -p" can be used to
214 add the user prior to installworld, as documented in the handbook.
217 OpenSSH is now built with DNSSEC support, and will by default
218 silently trust signed SSHFP records. This can be controlled with
219 the VerifyHostKeyDNS client configuration setting. DNSSEC support
220 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
223 The GNU Compiler Collection and C++ standard library (libstdc++)
224 are no longer built by default on platforms where clang is the system
225 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
229 The PROCDESC kernel option is now part of the GENERIC kernel
230 configuration and is required for the rwhod(8) to work.
231 If you are using custom kernel configuration, you should include
235 The API and ABI related to the Capsicum framework was modified
236 in backward incompatible way. The userland libraries and programs
237 have to be recompiled to work with the new kernel. This includes the
238 following libraries and programs, but the whole buildworld is
239 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
240 kdump, procstat, rwho, rwhod, uniq.
243 AES-NI intrinsic support has been added to gcc. The AES-NI module
244 has been updated to use this support. A new gcc is required to build
245 the aesni module on both i386 and amd64.
248 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
249 Thus "device padlock_rng" and "device rdrand_rng" should be
250 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
253 WITH_ICONV has been split into two feature sets. WITH_ICONV now
254 enables just the iconv* functionality and is now on by default.
255 WITH_LIBICONV_COMPAT enables the libiconv api and link time
256 compatability. Set WITHOUT_ICONV to build the old way.
257 If you have been using WITH_ICONV before, you will very likely
258 need to turn on WITH_LIBICONV_COMPAT.
261 INVARIANTS option now enables DEBUG for code with OpenSolaris and
262 Illumos origin, including ZFS. If you have INVARIANTS in your
263 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
265 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
266 locks if WITNESS option was set. Because that generated a lot of
267 witness(9) reports and all of them were believed to be false
268 positives, this is no longer done. New option OPENSOLARIS_WITNESS
269 can be used to achieve the previous behavior.
272 Timer values in IPv6 data structures now use time_uptime instead
273 of time_second. Although this is not a user-visible functional
274 change, userland utilities which directly use them---ndp(8),
275 rtadvd(8), and rtsold(8) in the base system---need to be updated
279 find -delete can now delete the pathnames given as arguments,
280 instead of only files found below them or if the pathname did
281 not contain any slashes. Formerly, the following error message
284 find: -delete: <path>: relative path potentially not safe
286 Deleting the pathnames given as arguments can be prevented
287 without error messages using -mindepth 1 or by changing
288 directory and passing "." as argument to find. This works in the
289 old as well as the new version of find.
292 Behavior of devfs rules path matching has been changed.
293 Pattern is now always matched against fully qualified devfs
294 path and slash characters must be explicitly matched by
295 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
296 subdirectories must be reviewed.
299 The default ARM ABI has changed to the ARM EABI. The old ABI is
300 incompatible with the ARM EABI and all programs and modules will
301 need to be rebuilt to work with a new kernel.
303 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
305 NOTE: Support for the old ABI will be removed in the future and
306 users are advised to upgrade.
309 pkg_install has been disconnected from the build if you really need it
310 you should add WITH_PKGTOOLS in your src.conf(5).
313 Most of network statistics structures were changed to be able
314 keep 64-bits counters. Thus all tools, that work with networking
315 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
318 Fix targets that run multiple make's to use && rather than ;
319 so that subsequent steps depend on success of previous.
321 NOTE: if building 'universe' with -j* on stable/8 or stable/9
322 it would be better to start the build using bmake, to avoid
323 overloading the machine.
326 Fix a bug that allowed a tracing process (e.g. gdb) to write
327 to a memory-mapped file in the traced process's address space
328 even if neither the traced process nor the tracing process had
329 write access to that file.
332 CVS has been removed from the base system. An exact copy
333 of the code is available from the devel/cvs port.
336 Some people report the following error after the switch to bmake:
338 make: illegal option -- J
339 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
341 *** [buildworld] Error code 2
343 this likely due to an old instance of make in
344 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
345 which src/Makefile will use that blindly, if it exists, so if
346 you see the above error:
348 rm -rf `make -V MAKEPATH`
353 Use bmake by default.
354 Whereas before one could choose to build with bmake via
355 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
356 make. The goal is to remove these knobs for 10-RELEASE.
358 It is worth noting that bmake (like gmake) treats the command
359 line as the unit of failure, rather than statements within the
360 command line. Thus '(cd some/where && dosomething)' is safer
361 than 'cd some/where; dosomething'. The '()' allows consistent
362 behavior in parallel build.
365 Fix a bug that allows NFS clients to issue READDIR on files.
368 The WITHOUT_IDEA option has been removed because
369 the IDEA patent expired.
372 The sysctl which controls TRIM support under ZFS has been renamed
373 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
377 The mergemaster command now uses the default MAKEOBJDIRPREFIX
378 rather than creating it's own in the temporary directory in
379 order allow access to bootstrapped versions of tools such as
380 install and mtree. When upgrading from version of FreeBSD where
381 the install command does not support -l, you will need to
382 install a new mergemaster command if mergemaster -p is required.
383 This can be accomplished with the command (cd src/usr.sbin/mergemaster
387 Legacy ATA stack, disabled and replaced by new CAM-based one since
388 FreeBSD 9.0, completely removed from the sources. Kernel modules
389 atadisk and atapi*, user-level tools atacontrol and burncd are
390 removed. Kernel option `options ATA_CAM` is now permanently enabled
394 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
395 and socketpair(2). Software, in particular Kerberos, may
396 automatically detect and use these during building. The resulting
397 binaries will not work on older kernels.
400 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
401 information, see the respective 20130304 entry).
404 Recent commits to callout(9) changed the size of struct callout,
405 so the KBI is probably heavily disturbed. Also, some functions
406 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
407 by macros. Every kernel module using it won't load, so rebuild
410 The ctl device has been re-enabled in GENERIC for i386 and amd64,
411 but does not initialize by default (because of the new CTL_DISABLE
412 option) to save memory. To re-enable it, remove the CTL_DISABLE
413 option from the kernel config file or set kern.cam.ctl.disable=0
414 in /boot/loader.conf.
417 The ctl device has been disabled in GENERIC for i386 and amd64.
418 This was done due to the extra memory being allocated at system
419 initialisation time by the ctl driver which was only used if
420 a CAM target device was created. This makes a FreeBSD system
421 unusable on 128MB or less of RAM.
424 A new compression method (lz4) has been merged to -HEAD. Please
425 refer to zpool-features(7) for more information.
427 Please refer to the "ZFS notes" section of this file for information
428 on upgrading boot ZFS pools.
431 A BSD-licensed patch(1) variant has been added and is installed
432 as bsdpatch, being the GNU version the default patch.
433 To inverse the logic and use the BSD-licensed one as default,
434 while having the GNU version installed as gnupatch, rebuild
435 and install world with the WITH_BSD_PATCH knob set.
438 Due to the use of the new -l option to install(1) during build
439 and install, you must take care not to directly set the INSTALL
440 make variable in your /etc/make.conf, /etc/src.conf, or on the
441 command line. If you wish to use the -C flag for all installs
442 you may be able to add INSTALL+=-C to /etc/make.conf or
446 The install(1) option -M has changed meaning and now takes an
447 argument that is a file or path to append logs to. In the
448 unlikely event that -M was the last option on the command line
449 and the command line contained at least two files and a target
450 directory the first file will have logs appended to it. The -M
451 option served little practical purpose in the last decade so its
452 use is expected to be extremely rare.
455 After switching to Clang as the default compiler some users of ZFS
456 on i386 systems started to experience stack overflow kernel panics.
457 Please consider using 'options KSTACK_PAGES=4' in such configurations.
460 GEOM_LABEL now mangles label names read from file system metadata.
461 Mangling affect labels containing spaces, non-printable characters,
462 '%' or '"'. Device names in /etc/fstab and other places may need to
466 By default, only the 10 most recent kernel dumps will be saved. To
467 restore the previous behaviour (no limit on the number of kernel dumps
468 stored in the dump directory) add the following line to /etc/rc.conf:
473 With the addition of auditdistd(8), a new auditdistd user is now
474 required during installworld. "mergemaster -p" can be used to
475 add the user prior to installworld, as documented in the handbook.
478 The sin6_scope_id member variable in struct sockaddr_in6 is now
479 filled by the kernel before passing the structure to the userland via
480 sysctl or routing socket. This means the KAME-specific embedded scope
481 id in sin6_addr.s6_addr[2] is always cleared in userland application.
482 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
483 __FreeBSD_version is bumped to 1000025.
486 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
487 This means that the world and kernel will be compiled with clang
488 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
489 and /usr/bin/cpp. To disable this behavior and revert to building
490 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
491 of current may need to bootstrap WITHOUT_CLANG first if the clang
492 build fails (its compatibility window doesn't extend to the 9 stable
496 The IPFIREWALL_FORWARD kernel option has been removed. Its
497 functionality now turned on by default.
500 The ZERO_COPY_SOCKET kernel option has been removed and
501 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
502 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
503 mechanism which is not safe and may result in kernel crashes.
504 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
505 driver supports disposeable external page sized mbuf storage.
506 Proper replacements for both zero-copy mechanisms are under
507 consideration and will eventually lead to complete removal
508 of the two kernel options.
511 The IPv4 network stack has been converted to network byte
512 order. The following modules need to be recompiled together
513 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
514 pf(4), ipfw(4), ng_ipfw(4), stf(4).
517 Support for non-MPSAFE filesystems was removed from VFS. The
518 VFS_VERSION was bumped, all filesystem modules shall be
522 All the non-MPSAFE filesystems have been disconnected from
523 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
524 portalfs, smbfs, xfs.
527 The interface cloning API and ABI has changed. The following
528 modules need to be recompiled together with kernel:
529 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
530 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
531 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
534 The sdhci driver was split in two parts: sdhci (generic SD Host
535 Controller logic) and sdhci_pci (actual hardware driver).
536 No kernel config modifications are required, but if you
537 load sdhc as a module you must switch to sdhci_pci instead.
540 Import the FUSE kernel and userland support into base system.
543 The GNU sort(1) program has been removed since the BSD-licensed
544 sort(1) has been the default for quite some time and no serious
545 problems have been reported. The corresponding WITH_GNU_SORT
549 The pfil(9) API/ABI for AF_INET family has been changed. Packet
550 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
554 The net80211(4) ABI has been changed to allow for improved driver
555 PS-POLL and power-save support. All wireless drivers need to be
556 recompiled to work with the new kernel.
559 The random(4) support for the VIA hardware random number
560 generator (`PADLOCK') is no longer enabled unconditionally.
561 Add the padlock_rng device in the custom kernel config if
562 needed. The GENERIC kernels on i386 and amd64 do include the
563 device, so the change only affects the custom kernel
567 The pf(4) packet filter ABI has been changed. pfctl(8) and
568 snmp_pf module need to be recompiled to work with new kernel.
571 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
572 to -HEAD. Pools that have empty_bpobj in active state can not be
573 imported read-write with ZFS implementations that do not support
574 this feature. For more information read the zpool-features(5)
578 The sparc64 ZFS loader has been changed to no longer try to auto-
579 detect ZFS providers based on diskN aliases but now requires these
580 to be explicitly listed in the OFW boot-device environment variable.
583 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
584 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
585 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
588 The following sysctls and tunables have been renamed for consistency
589 with other variables:
590 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
591 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
594 The sort utility has been replaced with BSD sort. For now, GNU sort
595 is also available as "gnusort" or the default can be set back to
596 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
597 installed as "bsdsort".
600 A new version of ZFS (pool version 5000) has been merged to -HEAD.
601 Starting with this version the old system of ZFS pool versioning
602 is superseded by "feature flags". This concept enables forward
603 compatibility against certain future changes in functionality of ZFS
604 pools. The first read-only compatible "feature flag" for ZFS pools
605 is named "com.delphix:async_destroy". For more information
606 read the new zpool-features(5) manual page.
607 Please refer to the "ZFS notes" section of this file for information
608 on upgrading boot ZFS pools.
611 The malloc(3) implementation embedded in libc now uses sources imported
612 as contrib/jemalloc. The most disruptive API change is to
613 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
614 delete it prior to installworld, and optionally re-create it using the
615 new format after rebooting. See malloc.conf(5) for details
616 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
620 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
621 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
622 now spelled mips. This is to aid compatibility with third-party
623 software that expects this naming scheme in uname(3). Little-endian
624 settings are unchanged. If you are updating a big-endian mips64 machine
625 from before this change, you may need to set MACHINE_ARCH=mips64 in
626 your environment before the new build system will recognize your machine.
629 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
633 Now unix domain sockets behave "as expected" on nullfs(5). Previously
634 nullfs(5) did not pass through all behaviours to the underlying layer,
635 as a result if we bound to a socket on the lower layer we could connect
636 only to the lower path; if we bound to the upper layer we could connect
637 only to the upper path. The new behavior is one can connect to both the
638 lower and the upper paths regardless what layer path one binds to.
641 The getifaddrs upgrade path broken with 20111215 has been restored.
642 If you have upgraded in between 20111215 and 20120209 you need to
643 recompile libc again with your kernel. You still need to recompile
644 world to be able to configure CARP but this restriction already
648 The set_rcvar() function has been removed from /etc/rc.subr. All
649 base and ports rc.d scripts have been updated, so if you have a
650 port installed with a script in /usr/local/etc/rc.d you can either
651 hand-edit the rcvar= line, or reinstall the port.
653 An easy way to handle the mass-update of /etc/rc.d:
654 rm /etc/rc.d/* && mergemaster -i
657 panic(9) now stops other CPUs in the SMP systems, disables interrupts
658 on the current CPU and prevents other threads from running.
659 This behavior can be reverted using the kern.stop_scheduler_on_panic
661 The new behavior can be incompatible with kern.sync_on_panic.
664 The carp(4) facility has been changed significantly. Configuration
665 of the CARP protocol via ifconfig(8) has changed, as well as format
666 of CARP events submitted to devd(8) has changed. See manual pages
667 for more information. The arpbalance feature of carp(4) is currently
668 not supported anymore.
670 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
671 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
672 need to be recompiled.
675 The acpi_wmi(4) status device /dev/wmistat has been renamed to
679 The option VFS_ALLOW_NONMPSAFE option has been added in order to
680 explicitely support non-MPSAFE filesystems.
681 It is on by default for all supported platform at this present
685 The broken amd(4) driver has been replaced with esp(4) in the amd64,
686 i386 and pc98 GENERIC kernel configuration files.
689 sysinstall has been removed
692 The stable/9 branch created in subversion. This corresponds to the
693 RELENG_9 branch in CVS.
696 This commit modifies vfs_register() so that it uses a hash
697 calculation to set vfc_typenum, which is enabled by default.
698 The first time a system is booted after this change, the
699 vfc_typenum values will change for all file systems. The
700 main effect of this is a change to the NFS server file handles
701 for file systems that use vfc_typenum in their fsid, such as ZFS.
702 It will, however, prevent vfc_typenum from changing when file
703 systems are loaded in a different order for subsequent reboots.
704 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
705 until you are ready to remount all NFS clients after a reboot.
708 Bump the shared library version numbers for libraries that
709 do not use symbol versioning, have changed the ABI compared
710 to stable/8 and which shared library version was not bumped.
711 Done as part of 9.0-RELEASE cycle.
714 During the merge of Capsicum features, the fget(9) KPI was modified.
715 This may require the rebuilding of out-of-tree device drivers --
716 issues have been reported specifically with the nVidia device driver.
717 __FreeBSD_version is bumped to 900041.
719 Also, there is a period between 20110811 and 20110814 where the
720 special devices /dev/{stdin,stdout,stderr} did not work correctly.
721 Building world from a kernel during that window may not work.
724 The packet filter (pf) code has been updated to OpenBSD 4.5.
725 You need to update userland tools to be in sync with kernel.
726 This update breaks backward compatibility with earlier pfsync(4)
727 versions. Care must be taken when updating redundant firewall setups.
730 The following sysctls and tunables are retired on x86 platforms:
732 machdep.hlt_logical_cpus
733 The following sysctl is retired:
734 machdep.hyperthreading_allowed
735 The sysctls were supposed to provide a way to dynamically offline and
736 online selected CPUs on x86 platforms, but the implementation has not
737 been reliable especially with SCHED_ULE scheduler.
738 machdep.hyperthreading_allowed tunable is still available to ignore
739 hyperthreading CPUs at OS level.
740 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
741 where X is an APIC ID of a CPU. Be advised, though, that disabling
742 CPUs in non-uniform fashion will result in non-uniform topology and
743 may lead to sub-optimal system performance with SCHED_ULE, which is
747 cpumask_t type is retired and cpuset_t is used in order to describe
751 Changes to ifconfig(8) for dynamic address family detection mandate
752 that you are running a kernel of 20110525 or later. Make sure to
753 follow the update procedure to boot a new kernel before installing
757 Support for sun4v architecture is officially dropped
760 Several KPI breaking changes have been committed to the mii(4) layer,
761 the PHY drivers and consequently some Ethernet drivers using mii(4).
762 This means that miibus.ko and the modules of the affected Ethernet
763 drivers need to be recompiled.
765 Note to kernel developers: Given that the OUI bit reversion problem
766 was fixed as part of these changes all mii(4) commits related to OUIs,
767 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
768 handling, no longer can be merged verbatim to stable/8 and previous
772 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
773 into their kernel configurations along with 'device pci'.
776 The default NFS client is now the new NFS client, so fstype "newnfs"
777 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
778 Although mounts via fstype "nfs" will usually work without userland
779 changes, it is recommended that the mount(8) and mount_nfs(8)
780 commands be rebuilt from sources and that a link to mount_nfs called
781 mount_oldnfs be created. The new client is compiled into the
782 kernel with "options NFSCL" and this is needed for diskless root
783 file systems. The GENERIC kernel configs have been changed to use
784 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
785 To use the regular/old client, you can "mount -t oldnfs ...". For
786 a diskless root file system, you must also include a line like:
788 vfs.root.mountfrom="oldnfs:"
790 in the boot/loader.conf on the root fs on the NFS server to make
791 a diskless root fs use the old client.
794 The GENERIC kernels for all architectures now default to the new
795 CAM-based ATA stack. It means that all legacy ATA drivers were
796 removed and replaced by respective CAM drivers. If you are using
797 ATA device names in /etc/fstab or other places, make sure to update
798 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
799 where 'Y's are the sequential numbers starting from zero for each type
800 in order of detection, unless configured otherwise with tunables,
801 see cam(4)). There will be symbolic links created in /dev/ to map
802 old adX devices to the respective adaY. They should provide basic
803 compatibility for file systems mounting in most cases, but they do
804 not support old user-level APIs and do not have respective providers
805 in GEOM. Consider using updated management tools with new device names.
807 It is possible to load devices ahci, ata, siis and mvs as modules,
808 but option ATA_CAM should remain in kernel configuration to make ata
809 module work as CAM driver supporting legacy ATA controllers. Device ata
810 still can be used in modular fashion (atacore + ...). Modules atadisk
811 and atapi* are not used and won't affect operation in ATA_CAM mode.
812 Note that to use CAM-based ATA kernel should include CAM devices
813 scbus, pass, da (or explicitly ada), cd and optionally others. All of
814 them are parts of the cam module.
816 ataraid(4) functionality is now supported by the RAID GEOM class.
817 To use it you can load geom_raid kernel module and use graid(8) tool
818 for management. Instead of /dev/arX device names, use /dev/raid/rX.
820 No kernel config options or code have been removed, so if a problem
821 arises, please report it and optionally revert to the old ATA stack.
822 In order to do it you can remove from the kernel config:
827 , and instead add back:
828 device atadisk # ATA disk drives
829 device ataraid # ATA RAID drives
830 device atapicd # ATAPI CDROM drives
831 device atapifd # ATAPI floppy drives
832 device atapist # ATAPI tape drives
835 The default NFS server has been changed to the new server, which
836 was referred to as the experimental server. If you need to switch
837 back to the old NFS server, you must now put the "-o" option on
838 both the mountd and nfsd commands. This can be done using the
839 mountd_flags and nfs_server_flags rc.conf variables until an
840 update to the rc scripts is committed, which is coming soon.
843 The GNU Objective-C runtime library (libobjc), and other Objective-C
844 related components have been removed from the base system. If you
845 require an Objective-C library, please use one of the available ports.
848 ath(4) has been split into bus- and device- modules. if_ath contains
849 the HAL, the TX rate control and the network device code. if_ath_pci
850 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
851 contains the AHB glue. Users need to load both if_ath_pci and if_ath
852 in order to use ath on everything else.
854 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
855 need to load if_ath and if_ath_pci for ath(4) operation.
858 As part of the replacement of sysinstall, the process of building
859 release media has changed significantly. For details, please re-read
860 release(7), which has been updated to reflect the new build process.
863 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
864 is the last available version under GPLv2. It brings a number of new
865 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
866 4.1 and SSE 4.2), better support for powerpc64, a number of new
867 directives, and lots of other small improvements. See the ChangeLog
868 file in contrib/binutils for the full details.
871 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
872 compliant, and will now use half of hash for authentication.
873 This will break interoperability with all stacks (including all
874 actual FreeBSD versions) who implement
875 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
877 The only workaround with such peers is to use another HMAC
878 algorithm for IPsec ("phase 2") authentication.
881 Remove the uio_yield prototype and symbol. This function has
882 been misnamed since it was introduced and should not be
883 globally exposed with this name. The equivalent functionality
884 is now available using kern_yield(curthread->td_user_pri).
885 The function remains undocumented.
888 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
889 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
890 for scalar sysctls is defined but disabled. Code that needs
891 UQUAD to pass the type checking that must compile on older
892 systems where the define is not present can check against
893 __FreeBSD_version >= 900030.
895 The system dialog(1) has been replaced with a new version previously
896 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
897 with the previous version, but the libdialog associated with it has
898 a largely incompatible API. As such, the original version of libdialog
899 will be kept temporarily as libodialog, until its base system consumers
900 are replaced or updated. Bump __FreeBSD_version to 900030.
903 If you are trying to run make universe on a -stable system, and you get
904 the following warning:
905 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
906 unknown. config(8) likely too old."
907 or something similar to it, then you must upgrade your -stable system
908 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
909 stable/8) or build the config from the latest stable/8 branch and
910 install it on your system.
912 Prior to this date, building a current universe on 8-stable system from
913 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
914 error in the first kernel build phase. A new config on those old
915 systems will fix that problem for older versions of -current.
918 The TCP stack has been modified to allow Khelp modules to interact with
919 it via helper hook points and store per-connection data in the TCP
920 control block. Bump __FreeBSD_version to 900029. User space tools that
921 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
925 Generic IEEE 802.3 annex 31B full duplex flow control support has been
926 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
927 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
928 to take advantage of it instead of using custom implementations. This
929 means that these drivers now no longer unconditionally advertise
930 support for flow control but only do so if flow control is a selected
931 media option. This was implemented in the generic support that way in
932 order to allow flow control to be switched on and off via ifconfig(8)
933 with the PHY specific default to typically off in order to protect
934 from unwanted effects. Consequently, if you used flow control with
935 one of the above mentioned drivers you now need to explicitly enable
937 ifconfig bge0 media auto mediaopt flowcontrol
939 Along with the above mentioned changes generic support for setting
940 1000baseT master mode also has been added and brgphy(4), ciphy(4),
941 e1000phy(4) as well as ip1000phy(4) have been converted to take
942 advantage of it. This means that these drivers now no longer take the
943 link0 parameter for selecting master mode but the master media option
944 has to be used instead, for example like in the following:
945 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
947 Selection of master mode now is also available with all other PHY
948 drivers supporting 1000baseT.
951 The TCP stack has received a significant update to add support for
952 modularised congestion control and generally improve the clarity of
953 congestion control decisions. Bump __FreeBSD_version to 900025. User
954 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
955 sockstat) need to be recompiled.
958 The man(1) utility has been replaced by a new version that no longer
959 uses /etc/manpath.config. Please consult man.conf(5) for how to
960 migrate local entries to the new format.
963 The copyright strings printed by login(1) and sshd(8) at the time of a
964 new connection have been removed to follow other operating systems and
968 A workaround for a fixed ld bug has been removed in kernel code,
969 so make sure that your system ld is built from sources after
970 revision 210245 from 2010-07-19 (r211583 if building head kernel
971 on stable/8, r211584 for stable/7; both from 2010-08-21).
972 A symptom of incorrect ld version is different addresses for
973 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
976 The $ipv6_prefer variable in rc.conf(5) has been split into
977 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
979 The $ip6addrctl_policy is a variable to choose a pre-defined
980 address selection policy set by ip6addrctl(8). A value
981 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
984 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
985 flag (see an entry of 20090926) is set on an interface with no
986 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
987 security reason. If you want IPv6 link-local address on all
988 interfaces by default, set this to "YES".
990 The old ipv6_prefer="YES" is equivalent to
991 ipv6_activate_all_interfaces="YES" and
992 ip6addrctl_policy="ipv6_prefer".
995 DTrace has grown support for userland tracing. Due to this, DTrace is
996 now i386 and amd64 only.
997 dtruss(1) is now installed by default on those systems and a new
998 kernel module is needed for userland tracing: fasttrap.
999 No changes to your kernel config file are necessary to enable
1000 userland tracing, but you might consider adding 'STRIP=' and
1001 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1002 to have informative userland stack traces in DTrace (ustack).
1005 The acpi_aiboost(4) driver has been removed in favor of the new
1006 aibs(4) driver. You should update your kernel configuration file.
1009 BSD grep has been imported to the base system and it is built by
1010 default. It is completely BSD licensed, highly GNU-compatible, uses
1011 less memory than its GNU counterpart and has a small codebase.
1012 However, it is slower than its GNU counterpart, which is mostly
1013 noticeable for larger searches, for smaller ones it is measurable
1014 but not significant. The reason is complex, the most important factor
1015 is that we lack a modern and efficient regex library and GNU
1016 overcomes this by optimizing the searches internally. Future work
1017 on improving the regex performance is planned, for the meantime,
1018 users that need better performance, can build GNU grep instead by
1019 setting the WITH_GNU_GREP knob.
1022 Due to the import of powerpc64 support, all existing powerpc kernel
1023 configuration files must be updated with a machine directive like this:
1024 machine powerpc powerpc
1026 In addition, an updated config(8) is required to build powerpc kernels
1030 A new version of ZFS (version 15) has been merged to -HEAD.
1031 This version uses a python library for the following subcommands:
1032 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1033 For full functionality of these commands the following port must
1034 be installed: sysutils/py-zfs
1037 'vm_page's are now hashed by physical address to an array of mutexes.
1038 Currently this is only used to serialize access to hold_count. Over
1039 time the page queue mutex will be peeled away. This changes the size
1040 of pmap on every architecture. And requires all callers of vm_page_hold
1041 and vm_page_unhold to be updated.
1044 WITH_CTF can now be specified in src.conf (not recommended, there
1045 are some problems with static executables), make.conf (would also
1046 affect ports which do not use GNU make and do not override the
1047 compile targets) or in the kernel config (via "makeoptions
1049 When WITH_CTF was specified there before this was silently ignored,
1050 so make sure that WITH_CTF is not used in places which could lead
1051 to unwanted behavior.
1054 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1055 to allow 32-bit compatibility on non-x86 platforms. All kernel
1056 configurations on amd64 and ia64 platforms using these options must
1057 be modified accordingly.
1060 The utmp user accounting database has been replaced with utmpx,
1061 the user accounting interface standardized by POSIX.
1062 Unfortunately the semantics of utmp and utmpx don't match,
1063 making it practically impossible to support both interfaces.
1064 The user accounting database is used by tools like finger(1),
1065 last(1), talk(1), w(1) and ac(8).
1067 All applications in the base system use utmpx. This means only
1068 local binaries (e.g. from the ports tree) may still use these
1069 utmp database files. These applications must be rebuilt to make
1072 After the system has been upgraded, it is safe to remove the old
1073 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1074 assuming their contents is of no importance anymore. Old wtmp
1075 databases can only be used by last(1) and ac(8) after they have
1076 been converted to the new format using wtmpcvt(1).
1079 Introduce the kernel thread "deadlock resolver" (which can be enabled
1080 via the DEADLKRES option, see NOTES for more details) and the
1081 sleepq_type() function for sleepqueues.
1084 The rc.firewall and rc.firewall6 were unified, and
1085 rc.firewall6 and rc.d/ip6fw were removed.
1086 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1087 variables are obsoleted. Instead, the following new rc
1088 variables are added to rc.d/ipfw:
1090 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1091 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1092 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1094 The meanings correspond to the relevant IPv4 variables.
1100 The default terminal emulation for syscons(4) has been changed
1101 from cons25 to xterm on all platforms except pc98. This means
1102 that the /etc/ttys file needs to be updated to ensure correct
1103 operation of applications on the console.
1105 The terminal emulation style can be toggled per window by using
1106 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1107 options can be used to change the compile-time default back to
1110 To prevent graphical artifacts, make sure the TERM environment
1111 variable is set to match the terminal emulation that is being
1112 performed by syscons(4).
1115 The layout of the structure ieee80211req_scan_result has changed.
1116 Applications that require wireless scan results (e.g. ifconfig(8))
1117 from net80211 need to be recompiled.
1119 Applications such as wpa_supplicant(8) may require a full world
1120 build without using NO_CLEAN in order to get synchronized with the
1124 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1125 There's one kernel module for each firmware. Adding "device iwnfw"
1126 to the kernel configuration file means including all three firmware
1127 images inside the kernel. If you want to include just the one for
1128 your wireless card, use the devices iwn4965fw, iwn5000fw or
1132 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1133 into rc.d/netif. The changes are the following:
1135 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1136 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1137 Note that both variables need the "inet6" keyword at the head.
1139 Do not set $ipv6_network_interfaces manually if you do not
1140 understand what you are doing. It is not needed in most cases.
1142 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1145 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1146 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1148 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1149 all configured interfaces have "inet6 accept_rtadv" in the
1150 $ifconfig_IF_ipv6. These are for backward compatibility.
1152 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1153 functionality of interfaces with no corresponding
1154 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1155 and the default address selection policy of ip6addrctl(8)
1156 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1157 Note that if you want to configure IPv6 functionality on the
1158 disabled interfaces after boot, first you need to clear the flag by
1159 using ifconfig(8) like:
1161 ifconfig em0 inet6 -ifdisabled
1163 If YES, the default address selection policy is set as
1166 The default value of $ipv6_prefer is NO.
1168 4. If your system need to receive Router Advertisement messages,
1169 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1170 scripts automatically invoke rtsol(8) when the interface becomes
1171 UP. The Router Advertisement messages are used for SLAAC
1172 (State-Less Address AutoConfiguration).
1175 802.11s D3.03 support was committed. This is incompatible with the
1176 previous code, which was based on D3.0.
1179 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1180 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1181 control whether accepting Router Advertisement messages or not.
1182 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1183 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1184 The ifconfig(8) utility now supports these flags.
1187 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1188 mount(8) and -a option for df(1) to see them.
1191 The old tunable hw.bus.devctl_disable has been superseded by
1192 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1193 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1197 Remove the option STOP_NMI. The default action is now to use NMI only
1198 for KDB via the newly introduced function stop_cpus_hard() and
1199 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1202 The stable/8 branch created in subversion. This corresponds to the
1203 RELENG_8 branch in CVS.
1206 Bump the shared library version numbers for all libraries that do not
1207 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1208 __FreeBSD_version to 800105.
1211 Due to changes in the implementation of virtual network stack support,
1212 all network-related kernel modules must be recompiled. As this change
1213 breaks the ABI, bump __FreeBSD_version to 800104.
1216 The TOE interface to the TCP syncache has been modified to remove
1217 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1218 The cxgb driver is the only TOE consumer affected by this change, and
1219 needs to be recompiled along with the kernel. As this change breaks
1220 the ABI, bump __FreeBSD_version to 800103.
1223 Padding has been added to struct tcpcb, sackhint and tcpstat in
1224 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1225 maintaining the ABI. However, this change breaks the ABI, so bump
1226 __FreeBSD_version to 800102. User space tools that rely on the size of
1227 any of these structs (e.g. sockstat) need to be recompiled.
1230 The NFS_LEGACYRPC option has been removed along with the old kernel
1231 RPC implementation that this option selected. Kernel configurations
1232 may need to be adjusted.
1235 The network interface device nodes at /dev/net/<interface> have been
1236 removed. All ioctl operations can be performed the normal way using
1237 routing sockets. The kqueue functionality can generally be replaced
1238 with routing sockets.
1241 The documentation from the FreeBSD Documentation Project (Handbook,
1242 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1243 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1246 The ABI of various structures related to the SYSV IPC API have been
1247 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1248 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1252 Layout of struct vnet has changed as routing related variables were
1253 moved to their own Vimage module. Modules need to be recompiled. Bump
1254 __FreeBSD_version to 800099.
1257 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1258 respectively. As long as no more than 16 groups per process are used,
1259 no changes should be visible. When more than 16 groups are used, old
1260 binaries may fail if they call getgroups() or getgrouplist() with
1261 statically sized storage. Recompiling will work around this, but
1262 applications should be modified to use dynamically allocated storage
1263 for group arrays as POSIX.1-2008 does not cap an implementation's
1264 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1266 NFS and portalfs mounts may also be affected as the list of groups is
1267 truncated to 16. Users of NFS who use more than 16 groups, should
1268 take care that negative group permissions are not used on the exported
1269 file systems as they will not be reliable unless a GSSAPI based
1270 authentication method is used.
1273 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1274 option compiles in the support for adaptive spinning for lockmgrs
1275 which want to enable it. The lockinit() function now accepts the flag
1276 LK_ADAPTIVE in order to make the lock object subject to adaptive
1277 spinning when both held in write and read mode.
1280 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1281 changed. User applications that use this ioctl need to be rebuilt.
1284 The layout of struct thread has changed. Kernel and modules need to
1288 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1289 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1292 window(1) has been removed from the base system. It can now be
1293 installed from ports. The port is called misc/window.
1296 The way we are storing and accessing `routing table' entries has
1297 changed. Programs reading the FIB, like netstat, need to be
1301 A new netisr implementation has been added for FreeBSD 8. Network
1302 file system modules, such as igmp, ipdivert, and others, should be
1304 Bump __FreeBSD_version to 800096.
1307 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1311 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1312 Bump __FreeBSD_version to 800094.
1315 Add mnt_xflag field to 'struct mount'. File system modules need to be
1317 Bump __FreeBSD_version to 800093.
1320 The compiling option ADAPTIVE_SX has been retired while it has been
1321 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1322 The KPI for sx_init_flags() changes as accepting flags:
1323 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1324 been introduced in order to handle the reversed logic.
1325 Bump __FreeBSD_version to 800092.
1328 Add support for hierarchical jails. Remove global securelevel.
1329 Bump __FreeBSD_version to 800091.
1332 The layout of struct vnet_net has changed, therefore modules
1334 Bump __FreeBSD_version to 800090.
1337 The newly imported zic(8) produces a new format in the output. Please
1338 run tzsetup(8) to install the newly created data to /etc/localtime.
1341 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1342 hw.usb.* and is now consistent again with previous releases.
1345 802.11 monitor mode support was revised and driver api's were changed.
1346 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1347 of DLT_IEEE802_11. No user-visible data structures were changed but
1348 applications that use DLT_IEEE802_11 may require changes.
1349 Bump __FreeBSD_version to 800088.
1352 The layout of the following structs has changed: sysctl_oid,
1353 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1354 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1355 panics may be experienced. World rebuild is required for
1356 correctly checking networking state from userland.
1357 Bump __FreeBSD_version to 800085.
1360 MLDv2 and Source-Specific Multicast (SSM) have been merged
1361 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1362 The implementation of SSM within FreeBSD's IPv6 stack closely
1363 follows the IPv4 implementation.
1365 For kernel developers:
1367 * The most important changes are that the ip6_output() and
1368 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1369 and this lock has been downgraded to a non-recursive mutex.
1371 * As with the changes to the IPv4 stack to support SSM, filtering
1372 of inbound multicast traffic must now be performed by transport
1373 protocols within the IPv6 stack. This does not apply to TCP and
1374 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1376 * The KPIs used by IPv6 multicast are similar to those used by
1377 the IPv4 stack, with the following differences:
1378 * im6o_mc_filter() is analogous to imo_multicast_filter().
1379 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1380 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1381 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1382 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1383 for MLDv1 have an additional 'timer' argument which is used to
1384 jitter the initial membership report for the solicited-node
1385 multicast membership on-link.
1386 * This is not strictly needed for MLDv2, which already jitters
1387 its report transmissions. However, the 'timer' argument is
1388 preserved in case MLDv1 is active on the interface.
1390 * The KAME linked-list based IPv6 membership implementation has
1391 been refactored to use a vector similar to that used by the IPv4
1393 Code which maintains a list of its own multicast memberships
1394 internally, e.g. carp, has been updated to reflect the new
1397 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1398 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1399 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1400 implementation constraint which needs to be addressed in HEAD.
1402 For application developers:
1404 * The changes are broadly similar to those made for the IPv4
1407 * The use of IPv4 and IPv6 multicast socket options on the same
1408 socket, using mapped addresses, HAS NOT been tested or supported.
1410 * There are a number of issues with the implementation of various
1411 IPv6 multicast APIs which need to be resolved in the API surface
1412 before the implementation is fully compatible with KAME userland
1413 use, and these are mostly to do with interface index treatment.
1415 * The literature available discusses the use of either the delta / ASM
1416 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1417 using setsourcefilter(3)/getsourcefilter(3). For more information
1418 please refer to RFC 3768, 'Socket Interface Extensions for
1419 Multicast Source Filters'.
1421 * Applications which use the published RFC 3678 APIs should be fine.
1423 For systems administrators:
1425 * The mtest(8) utility has been refactored to support IPv6, in
1426 addition to IPv4. Interface addresses are no longer accepted
1427 as arguments, their names must be used instead. The utility
1428 will map the interface name to its first IPv4 address as
1429 returned by getifaddrs(3).
1431 * The ifmcstat(8) utility has also been updated to print the MLDv2
1432 endpoint state and source filter lists via sysctl(3).
1434 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1435 loopback of IPv6 multicast datagrams by default; it defaults to 1
1436 to preserve the existing behaviour. Disabling multicast loopback is
1437 recommended for optimal system performance.
1439 * The IPv6 MROUTING code has been changed to examine this sysctl
1440 instead of attempting to perform a group lookup before looping
1441 back forwarded datagrams.
1443 Bump __FreeBSD_version to 800084.
1446 Implement low-level Bluetooth HCI API.
1447 Bump __FreeBSD_version to 800083.
1450 The layout of struct malloc_type, used by modules to register new
1451 memory allocation types, has changed. Most modules will need to
1452 be rebuilt or panics may be experienced.
1453 Bump __FreeBSD_version to 800081.
1456 Anticipate overflowing inp_flags - add inp_flags2.
1457 This changes most offsets in inpcb, so checking v4 connection
1458 state will require a world rebuild.
1459 Bump __FreeBSD_version to 800080.
1462 Add an llentry to struct route and struct route_in6. Modules
1463 embedding a struct route will need to be recompiled.
1464 Bump __FreeBSD_version to 800079.
1467 The size of rt_metrics_lite and by extension rtentry has changed.
1468 Networking administration apps will need to be recompiled.
1469 The route command now supports show as an alias for get, weighting
1470 of routes, sticky and nostick flags to alter the behavior of stateful
1472 Bump __FreeBSD_version to 800078.
1475 Do not use Giant for kbdmux(4) locking. This is wrong and
1476 apparently causing more problems than it solves. This will
1477 re-open the issue where interrupt handlers may race with
1478 kbdmux(4) in polling mode. Typical symptoms include (but
1479 not limited to) duplicated and/or missing characters when
1480 low level console functions (such as gets) are used while
1481 interrupts are enabled (for example geli password prompt,
1482 mountroot prompt etc.). Disabling kbdmux(4) may help.
1485 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1486 kernel modules referencing any of the above need to be recompiled.
1487 Bump __FreeBSD_version to 800075.
1490 GEOM_PART has become the default partition slicer for storage devices,
1491 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1492 introduces some changes:
1494 MSDOS/EBR: the devices created from MSDOS extended partition entries
1495 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1496 to devices with offset-based names. fstabs may need to be modified.
1498 BSD: the "geometry does not match label" warning is harmless in most
1499 cases but it points to problems in file system misalignment with
1500 disk geometry. The "c" partition is now implicit, covers the whole
1501 top-level drive and cannot be (mis)used by users.
1503 General: Kernel dumps are now not allowed to be written to devices
1504 whose partition types indicate they are meant to be used for file
1505 systems (or, in case of MSDOS partitions, as something else than
1508 Most of these changes date approximately from 200812.
1511 The uscanner(4) driver has been removed from the kernel. This follows
1512 Linux removing theirs in 2.6 and making libusb the default interface
1513 (supported by sane).
1516 The multicast forwarding code has been cleaned up. netstat(1)
1517 only relies on KVM now for printing bandwidth upcall meters.
1518 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1519 ip6_mroute_mod respectively. The config(5) options for statically
1520 compiling this code remain the same, i.e. 'options MROUTING'.
1523 Support for the IFF_NEEDSGIANT network interface flag has been
1524 removed, which means that non-MPSAFE network device drivers are no
1525 longer supported. In particular, if_ar, if_sr, and network device
1526 drivers from the old (legacy) USB stack can no longer be built or
1530 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1531 a bunch of new language catalog files have also been added.
1532 This means that some common libc messages are now localized and
1533 they depend on the LC_MESSAGES environmental variable.
1536 The k8temp(4) driver has been renamed to amdtemp(4) since
1537 support for Family 10 and Family 11 CPU families was added.
1540 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1541 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1543 For kernel developers, the most important changes are that the
1544 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1545 and this lock has been downgraded to a non-recursive mutex.
1547 Transport protocols (UDP, Raw IP) are now responsible for filtering
1548 inbound multicast traffic according to group membership and source
1549 filters. The imo_multicast_filter() KPI exists for this purpose.
1550 Transports which do not use multicast (SCTP, TCP) already reject
1551 multicast by default. Forwarding and receive performance may improve
1552 as a mutex acquisition is no longer needed in the ip_input()
1553 low-level input path. in_addmulti() and in_delmulti() are shimmed
1554 to new KPIs which exist to support SSM in-kernel.
1556 For application developers, it is recommended that loopback of
1557 multicast datagrams be disabled for best performance, as this
1558 will still cause the lock to be taken for each looped-back
1559 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1560 be tuned to 0 to disable loopback by default; it defaults to 1
1561 to preserve the existing behaviour.
1563 For systems administrators, to obtain best performance with
1564 multicast reception and multiple groups, it is always recommended
1565 that a card with a suitably precise hash filter is used. Hash
1566 collisions will still result in the lock being taken within the
1567 transport protocol input path to check group membership.
1569 If deploying FreeBSD in an environment with IGMP snooping switches,
1570 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1571 enabled; this forces 224.0.0.0/24 group membership to be announced
1574 The size of 'struct igmpstat' has changed; netstat needs to be
1575 recompiled to reflect this.
1576 Bump __FreeBSD_version to 800070.
1579 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1580 updated to use it. This requires a buildworld/installworld in order to
1581 update the library and dependencies (usbconfig, etc). Its advisable to
1582 rebuild all ports which uses libusb. More specific directions are given
1583 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1584 libusb are no longer required and can be removed.
1587 A workaround is committed to allow the creation of System V shared
1588 memory segment of size > 2 GB on the 64-bit architectures.
1589 Due to a limitation of the existing ABI, the shm_segsz member
1590 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1591 wrong for large segments. Note that limits must be explicitly
1592 raised to allow such segments to be created.
1595 The layout of struct ifnet has changed, requiring a rebuild of all
1596 network device driver modules.
1599 The /dev handling for the new USB stack has changed, a
1600 buildworld/installworld is required for libusb20.
1603 The new USB2 stack has now been permanently moved in and all kernel and
1604 module names reverted to their previous values (eg, usb, ehci, ohci,
1605 ums, ...). The old usb stack can be compiled in by prefixing the name
1606 with the letter 'o', the old usb modules have been removed.
1607 Updating entry 20090216 for xorg and 20090215 for libmap may still
1611 The rc.conf(5) option if_up_delay has been renamed to
1612 defaultroute_delay to better reflect its purpose. If you have
1613 customized this setting in /etc/rc.conf you need to update it to
1617 xorg 7.4 wants to configure its input devices via hald which does not
1618 yet work with USB2. If the keyboard/mouse does not work in xorg then
1620 Option "AllowEmptyInput" "off"
1621 to your ServerLayout section. This will cause X to use the configured
1622 kbd and mouse sections from your xorg.conf.
1625 The GENERIC kernels for all architectures now default to the new USB2
1626 stack. No kernel config options or code have been removed so if a
1627 problem arises please report it and optionally revert to the old USB
1628 stack. If you are loading USB kernel modules or have a custom kernel
1629 that includes GENERIC then ensure that usb names are also changed over,
1630 eg uftdi -> usb2_serial_ftdi.
1632 Older programs linked against the ports libusb 0.1 need to be
1633 redirected to the new stack's libusb20. /etc/libmap.conf can
1635 # Map old usb library to new one for usb2 stack
1636 libusb-0.1.so.8 libusb20.so.1
1639 All USB ethernet devices now attach as interfaces under the name ueN
1640 (eg. ue0). This is to provide a predictable name as vendors often
1641 change usb chipsets in a product without notice.
1644 The ichsmb(4) driver has been changed to require SMBus slave
1645 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1646 All of the other SMBus controller drivers require left-justified
1647 slave addresses, so this change makes all the drivers provide the
1651 INET6 statistics (struct ip6stat) was updated.
1652 netstat(1) needs to be recompiled.
1655 NTFS has been removed from GENERIC kernel on amd64 to match
1656 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1657 will load ntfs.ko module automatically when NTFS support is
1658 actually needed, unless ntfs.ko is not installed or security
1659 level prohibits loading kernel modules. If either is the case,
1660 "options NTFS" has to be added into kernel config.
1663 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1664 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1665 800061. User space tools that rely on the size of struct tcpcb in
1666 tcp_var.h (e.g. sockstat) need to be recompiled.
1669 ng_tty(4) module updated to match the new TTY subsystem.
1670 Due to API change, user-level applications must be updated.
1671 New API support added to mpd5 CVS and expected to be present
1672 in next mpd5.3 release.
1675 With __FreeBSD_version 800060 the makefs tool is part of
1676 the base system (it was a port).
1679 The afdata and ifnet locks have been changed from mutexes to
1680 rwlocks, network modules will need to be re-compiled.
1683 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1684 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1685 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1686 architecture and 40 bytes on 64-bit architecture. The userland
1687 applications "arp" and "ndp" have been updated accordingly.
1688 The output from "netstat -r" shows only routing entries and
1689 none of the L2 information.
1692 __FreeBSD_version 800057 marks the switchover from the
1693 binary ath hal to source code. Users must add the line:
1695 options AH_SUPPORT_AR5416
1697 to their kernel config files when specifying:
1701 The ath_hal module no longer exists; the code is now compiled
1702 together with the driver in the ath module. It is now
1703 possible to tailor chip support (i.e. reduce the set of chips
1704 and thereby the code size); consult ath_hal(4) for details.
1707 __FreeBSD_version 800054 adds memory barriers to
1708 <machine/atomic.h>, new interfaces to ifnet to facilitate
1709 multiple hardware transmit queues for cards that support
1710 them, and a lock-less ring-buffer implementation to
1711 enable drivers to more efficiently manage queueing of
1715 A new version of ZFS (version 13) has been merged to -HEAD.
1716 This version has zpool attribute "listsnapshots" off by
1717 default, which means "zfs list" does not show snapshots,
1718 and is the same as Solaris behavior.
1721 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1724 The uhci, ohci, ehci and slhci USB Host controller drivers have
1725 been put into separate modules. If you load the usb module
1726 separately through loader.conf you will need to load the
1727 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1728 controller add the following to loader.conf:
1734 The ABI used by the PMC toolset has changed. Please keep
1735 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1739 atapci kernel module now includes only generic PCI ATA
1740 driver. AHCI driver moved to ataahci kernel module.
1741 All vendor-specific code moved into separate kernel modules:
1742 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1743 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1744 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1745 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1748 The TTY subsystem of the kernel has been replaced by a new
1749 implementation, which provides better scalability and an
1750 improved driver model. Most common drivers have been migrated to
1751 the new TTY subsystem, while others have not. The following
1752 drivers have not yet been ported to the new TTY layer:
1755 cy, digi, rc, rp, sio
1761 ng_h4, ng_tty, ppp, sl, snp
1763 Adding these drivers to your kernel configuration file shall
1764 cause compilation to fail.
1767 ntpd has been upgraded to 4.2.4p5.
1770 OpenSSH has been upgraded to 5.1p1.
1772 For many years, FreeBSD's version of OpenSSH preferred DSA
1773 over RSA for host and user authentication keys. With this
1774 upgrade, we've switched to the vendor's default of RSA over
1775 DSA. This may cause upgraded clients to warn about unknown
1776 host keys even for previously known hosts. Users should
1777 follow the usual procedure for verifying host keys before
1778 accepting the RSA key.
1780 This can be circumvented by setting the "HostKeyAlgorithms"
1781 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1784 Please note that the sequence of keys offered for
1785 authentication has been changed as well. You may want to
1786 specify IdentityFile in a different order to revert this
1790 The sio(4) driver has been removed from the i386 and amd64
1791 kernel configuration files. This means uart(4) is now the
1792 default serial port driver on those platforms as well.
1794 To prevent collisions with the sio(4) driver, the uart(4) driver
1795 uses different names for its device nodes. This means the
1796 onboard serial port will now most likely be called "ttyu0"
1797 instead of "ttyd0". You may need to reconfigure applications to
1798 use the new device names.
1800 When using the serial port as a boot console, be sure to update
1801 /boot/device.hints and /etc/ttys before booting the new kernel.
1802 If you forget to do so, you can still manually specify the hints
1803 at the loader prompt:
1805 set hint.uart.0.at="isa"
1806 set hint.uart.0.port="0x3F8"
1807 set hint.uart.0.flags="0x10"
1808 set hint.uart.0.irq="4"
1812 The gpt(8) utility has been removed. Use gpart(8) to partition
1816 The version that Linuxulator emulates was changed from 2.4.2
1817 to 2.6.16. If you experience any problems with Linux binaries
1818 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1819 if it fixes the problem contact emulation mailing list.
1822 ISDN4BSD (I4B) was removed from the src tree. You may need to
1823 update a your kernel configuration and remove relevant entries.
1826 I have checked in code to support multiple routing tables.
1827 See the man pages setfib(1) and setfib(2).
1828 This is a hopefully backwards compatible version,
1829 but to make use of it you need to compile your kernel
1830 with options ROUTETABLES=2 (or more up to 16).
1833 The 802.11 wireless support was redone to enable multi-bss
1834 operation on devices that are capable. The underlying device
1835 is no longer used directly but instead wlanX devices are
1836 cloned with ifconfig. This requires changes to rc.conf files.
1837 For example, change:
1838 ifconfig_ath0="WPA DHCP"
1841 ifconfig_wlan0="WPA DHCP"
1842 see rc.conf(5) for more details. In addition, mergemaster of
1843 /etc/rc.d is highly recommended. Simultaneous update of userland
1844 and kernel wouldn't hurt either.
1846 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1847 modules were merged into the base wlan module. All references
1848 to these modules (e.g. in kernel config files) must be removed.
1851 psm(4) has gained write(2) support in native operation level.
1852 Arbitrary commands can be written to /dev/psm%d and status can
1853 be read back from it. Therefore, an application is responsible
1854 for status validation and error recovery. It is a no-op in
1855 other operation levels.
1858 Support for KSE threading has been removed from the kernel. To
1859 run legacy applications linked against KSE libmap.conf may
1860 be used. The following libmap.conf may be used to ensure
1861 compatibility with any prior release:
1863 libpthread.so.1 libthr.so.1
1864 libpthread.so.2 libthr.so.2
1865 libkse.so.3 libthr.so.3
1868 The layout of struct vmspace has changed. This affects libkvm
1869 and any executables that link against libkvm and use the
1870 kvm_getprocs() function. In particular, but not exclusively,
1871 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1872 The effects are minimal, but it's advisable to upgrade world
1876 The latest em driver no longer has support in it for the
1877 82575 adapter, this is now moved to the igb driver. The
1878 split was done to make new features that are incompatible
1879 with older hardware easier to do.
1882 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1883 likewise the kernel option is now GEOM_LINUX_LVM.
1886 The default NFS mount mode has changed from UDP to TCP for
1887 increased reliability. If you rely on (insecurely) NFS
1888 mounting across a firewall you may need to update your
1892 Belatedly note the addition of m_collapse for compacting
1896 The fts(3) structures have been changed to use adequate
1897 integer types for their members and so to be able to cope
1898 with huge file trees. The old fts(3) ABI is preserved
1899 through symbol versioning in libc, so third-party binaries
1900 using fts(3) should still work, although they will not take
1901 advantage of the extended types. At the same time, some
1902 third-party software might fail to build after this change
1903 due to unportable assumptions made in its source code about
1904 fts(3) structure members. Such software should be fixed
1905 by its vendor or, in the worst case, in the ports tree.
1906 FreeBSD_version 800015 marks this change for the unlikely
1907 case that a portable fix is impossible.
1910 To upgrade to -current after this date, you must be running
1911 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1912 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1915 The ADAPTIVE_GIANT kernel option has been retired because its
1916 functionality is the default now.
1919 The AT keyboard emulation of sunkbd(4) has been turned on
1920 by default. In order to make the special symbols of the Sun
1921 keyboards driven by sunkbd(4) work under X these now have
1922 to be configured the same way as Sun USB keyboards driven
1923 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1925 Option "XkbLayout" "us"
1926 Option "XkbRules" "xorg"
1927 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1930 It has been decided that it is desirable to provide ABI
1931 backwards compatibility to the FreeBSD 4/5/6 versions of the
1932 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1933 broken with the introduction of PCI domain support (see the
1934 20070930 entry). Unfortunately, this required the ABI of
1935 PCIOCGETCONF to be broken again in order to be able to
1936 provide backwards compatibility to the old version of that
1937 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1938 again. As for prominent ports this affects neither pciutils
1939 nor xorg-server this time, the hal port needs to be rebuilt
1943 The misnamed kthread_create() and friends have been renamed
1944 to kproc_create() etc. Many of the callers already
1945 used kproc_start()..
1946 I will return kthread_create() and friends in a while
1947 with implementations that actually create threads, not procs.
1948 Renaming corresponds with version 800002.
1957 Avoid using make -j when upgrading. While generally safe, there are
1958 sometimes problems using -j to upgrade. If your upgrade fails with
1959 -j, please try again without -j. From time to time in the past there
1960 have been problems using -j with buildworld and/or installworld. This
1961 is especially true when upgrading between "distant" versions (eg one
1962 that cross a major release boundary or several minor releases, or when
1963 several months have passed on the -current branch).
1965 Sometimes, obscure build problems are the result of environment
1966 poisoning. This can happen because the make utility reads its
1967 environment when searching for values for global variables. To run
1968 your build attempts in an "environmental clean room", prefix all make
1969 commands with 'env -i '. See the env(1) manual page for more details.
1971 When upgrading from one major version to another it is generally best
1972 to upgrade to the latest code in the currently installed branch first,
1973 then do an upgrade to the new branch. This is the best-tested upgrade
1974 path, and has the highest probability of being successful. Please try
1975 this approach before reporting problems with a major version upgrade.
1977 When upgrading a live system, having a root shell around before
1978 installing anything can help undo problems. Not having a root shell
1979 around can lead to problems if pam has changed too much from your
1980 starting point to allow continued authentication after the upgrade.
1984 When upgrading the boot ZFS pool to a new version, always follow
1987 1.) recompile and reinstall the ZFS boot loader and boot block
1988 (this is part of "make buildworld" and "make installworld")
1990 2.) update the ZFS boot block on your boot drive
1992 The following example updates the ZFS boot block on the first
1993 partition (freebsd-boot) of a GPT partitioned drive ad0:
1994 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1996 Non-boot pools do not need these updates.
2000 If you are updating from a prior version of FreeBSD (even one just
2001 a few days old), you should follow this procedure. It is the most
2002 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2004 make kernel-toolchain
2005 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2006 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2008 To test a kernel once
2009 ---------------------
2010 If you just want to boot a kernel once (because you are not sure
2011 if it works, or if you want to boot a known bad kernel to provide
2012 debugging information) run
2013 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2014 nextboot -k testkernel
2016 To just build a kernel when you know that it won't mess you up
2017 --------------------------------------------------------------
2018 This assumes you are already running a CURRENT system. Replace
2019 ${arch} with the architecture of your machine (e.g. "i386",
2020 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2022 cd src/sys/${arch}/conf
2023 config KERNEL_NAME_HERE
2024 cd ../compile/KERNEL_NAME_HERE
2029 If this fails, go to the "To build a kernel" section.
2031 To rebuild everything and install it on the current system.
2032 -----------------------------------------------------------
2033 # Note: sometimes if you are running current you gotta do more than
2034 # is listed here if you are upgrading from a really old current.
2036 <make sure you have good level 0 dumps>
2038 make kernel KERNCONF=YOUR_KERNEL_HERE
2040 <reboot in single user> [3]
2047 To cross-install current onto a separate partition
2048 --------------------------------------------------
2049 # In this approach we use a separate partition to hold
2050 # current's root, 'usr', and 'var' directories. A partition
2051 # holding "/", "/usr" and "/var" should be about 2GB in
2054 <make sure you have good level 0 dumps>
2057 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2058 <maybe newfs current's root partition>
2059 <mount current's root partition on directory ${CURRENT_ROOT}>
2060 make installworld DESTDIR=${CURRENT_ROOT}
2061 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2062 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2063 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2064 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2065 <reboot into current>
2066 <do a "native" rebuild/install as described in the previous section>
2067 <maybe install compatibility libraries from ports/misc/compat*>
2071 To upgrade in-place from stable to current
2072 ----------------------------------------------
2073 <make sure you have good level 0 dumps>
2075 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2077 <reboot in single user> [3]
2084 Make sure that you've read the UPDATING file to understand the
2085 tweaks to various things you need. At this point in the life
2086 cycle of current, things change often and you are on your own
2087 to cope. The defaults can also change, so please read ALL of
2088 the UPDATING entries.
2090 Also, if you are tracking -current, you must be subscribed to
2091 freebsd-current@freebsd.org. Make sure that before you update
2092 your sources that you have read and understood all the recent
2093 messages there. If in doubt, please track -stable which has
2094 much fewer pitfalls.
2096 [1] If you have third party modules, such as vmware, you
2097 should disable them at this point so they don't crash your
2100 [3] From the bootblocks, boot -s, and then do
2105 adjkerntz -i # if CMOS is wall time
2106 Also, when doing a major release upgrade, it is required that
2107 you boot into single user mode to do the installworld.
2109 [4] Note: This step is non-optional. Failure to do this step
2110 can result in a significant reduction in the functionality of the
2111 system. Attempting to do it by hand is not recommended and those
2112 that pursue this avenue should read this file carefully, as well
2113 as the archives of freebsd-current and freebsd-hackers mailing lists
2114 for potential gotchas. The -U option is also useful to consider.
2115 See mergemaster(8) for more information.
2117 [5] Usually this step is a noop. However, from time to time
2118 you may need to do this if you get unknown user in the following
2119 step. It never hurts to do it all the time. You may need to
2120 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2121 install) after the buildworld before this step if you last updated
2122 from current before 20130425 or from -stable before 20130430.
2124 [6] This only deletes old files and directories. Old libraries
2125 can be deleted by "make delete-old-libs", but you have to make
2126 sure that no program is using those libraries anymore.
2128 [8] In order to have a kernel that can run the 4.x binaries needed to
2129 do an installworld, you must include the COMPAT_FREEBSD4 option in
2130 your kernel. Failure to do so may leave you with a system that is
2131 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2132 required to run the 5.x binaries on more recent kernels. And so on
2133 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2135 Make sure that you merge any new devices from GENERIC since the
2136 last time you updated your kernel config file.
2138 [9] When checking out sources, you must include the -P flag to have
2139 cvs prune empty directories.
2141 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2142 "?=" instead of the "=" assignment operator, so that buildworld can
2143 override the CPUTYPE if it needs to.
2145 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2146 not on the command line, or in /etc/make.conf. buildworld will
2147 warn if it is improperly defined.
2150 This file contains a list, in reverse chronological order, of major
2151 breakages in tracking -current. It is not guaranteed to be a complete
2152 list of such breakages, and only contains entries since October 10, 2007.
2153 If you need to see UPDATING entries from before that date, you will need
2154 to fetch an UPDATING file from an older FreeBSD release.
2156 Copyright information:
2158 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2160 Redistribution, publication, translation and use, with or without
2161 modification, in full or in part, in any form or format of this
2162 document are permitted without further permission from the author.
2164 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2165 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2166 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2167 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2168 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2169 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2170 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2171 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2172 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2173 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2174 POSSIBILITY OF SUCH DAMAGE.
2176 Contact Warner Losh if you have any questions about your use of