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.
21 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
22 capability mode support. Please note that enabling the feature in
23 kernel is still highly recommended.
26 OpenSSH is now built with sandbox support, and will use sandbox as
27 the default privilege separation method. This requires Capsicum
28 capability mode support in kernel.
31 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
32 been deprecated and will not be part of FreeBSD 11.0 and later
33 releases. If you use this driver, please consider switching to
34 the nfe(4) driver instead.
40 The behavior of gss_pseudo_random() for the krb5 mechanism
41 has changed, for applications requesting a longer random string
42 than produced by the underlying enctype's pseudo-random() function.
43 In particular, the random string produced from a session key of
44 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
45 be different at the 17th octet and later, after this change.
46 The counter used in the PRF+ construction is now encoded as a
47 big-endian integer in accordance with RFC 4402.
48 __FreeBSD_version is bumped to 1000701.
51 The WITHOUT_ATF build knob has been removed and its functionality
52 has been subsumed into the more generic WITHOUT_TESTS. If you were
53 using the former to disable the build of the ATF libraries, you
54 should change your settings to use the latter.
57 The default version of mtree is nmtree which is obtained from
58 NetBSD. The output is generally the same, but may vary
59 slightly. If you found you need identical output adding
60 "-F freebsd9" to the command line should do the trick. For the
61 time being, the old mtree is available as fmtree.
64 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
65 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
66 1.1.4_8 and verify bsdyml not linked in, before running "make
68 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
70 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
73 The rc.d/jail script has been updated to support jail(8)
74 configuration file. The "jail_<jname>_*" rc.conf(5) variables
75 for per-jail configuration are automatically converted to
76 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
77 This is transparently backward compatible. See below about some
78 incompatibilities and rc.conf(5) manual page for more details.
80 These variables are now deprecated in favor of jail(8) configuration
81 file. One can use "rc.d/jail config <jname>" command to generate
82 a jail(8) configuration file in /var/run/jail.<jname>.conf without
83 running the jail(8) utility. The default pathname of the
84 configuration file is /etc/jail.conf and can be specified by
85 using $jail_conf or $jail_<jname>_conf variables.
87 Please note that jail_devfs_ruleset accepts an integer at
88 this moment. Please consider to rewrite the ruleset name
92 BIND has been removed from the base system. If all you need
93 is a local resolver, simply enable and start the local_unbound
94 service instead. Otherwise, several versions of BIND are
95 available in the ports tree. The dns/bind99 port is one example.
97 With this change, nslookup(1) and dig(1) are no longer in the base
98 system. Users should instead use host(1) and drill(1) which are
99 in the base system. Alternatively, nslookup and dig can
100 be obtained by installing the dns/bind-tools port.
103 With the addition of unbound(8), a new unbound user is now
104 required during installworld. "mergemaster -p" can be used to
105 add the user prior to installworld, as documented in the handbook.
108 OpenSSH is now built with DNSSEC support, and will by default
109 silently trust signed SSHFP records. This can be controlled with
110 the VerifyHostKeyDNS client configuration setting. DNSSEC support
111 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
114 The GNU Compiler Collection and C++ standard library (libstdc++)
115 are no longer built by default on platforms where clang is the system
116 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
120 The PROCDESC kernel option is now part of the GENERIC kernel
121 configuration and is required for the rwhod(8) to work.
122 If you are using custom kernel configuration, you should include
126 The API and ABI related to the Capsicum framework was modified
127 in backward incompatible way. The userland libraries and programs
128 have to be recompiled to work with the new kernel. This includes the
129 following libraries and programs, but the whole buildworld is
130 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
131 kdump, procstat, rwho, rwhod, uniq.
134 AES-NI intrinsic support has been added to gcc. The AES-NI module
135 has been updated to use this support. A new gcc is required to build
136 the aesni module on both i386 and amd64.
139 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
140 Thus "device padlock_rng" and "device rdrand_rng" should be
141 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
144 WITH_ICONV has been split into two feature sets. WITH_ICONV now
145 enables just the iconv* functionality and is now on by default.
146 WITH_LIBICONV_COMPAT enables the libiconv api and link time
147 compatability. Set WITHOUT_ICONV to build the old way.
148 If you have been using WITH_ICONV before, you will very likely
149 need to turn on WITH_LIBICONV_COMPAT.
152 INVARIANTS option now enables DEBUG for code with OpenSolaris and
153 Illumos origin, including ZFS. If you have INVARIANTS in your
154 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
156 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
157 locks if WITNESS option was set. Because that generated a lot of
158 witness(9) reports and all of them were believed to be false
159 positives, this is no longer done. New option OPENSOLARIS_WITNESS
160 can be used to achieve the previous behavior.
163 Timer values in IPv6 data structures now use time_uptime instead
164 of time_second. Although this is not a user-visible functional
165 change, userland utilities which directly use them---ndp(8),
166 rtadvd(8), and rtsold(8) in the base system---need to be updated
170 find -delete can now delete the pathnames given as arguments,
171 instead of only files found below them or if the pathname did
172 not contain any slashes. Formerly, the following error message
175 find: -delete: <path>: relative path potentially not safe
177 Deleting the pathnames given as arguments can be prevented
178 without error messages using -mindepth 1 or by changing
179 directory and passing "." as argument to find. This works in the
180 old as well as the new version of find.
183 Behavior of devfs rules path matching has been changed.
184 Pattern is now always matched against fully qualified devfs
185 path and slash characters must be explicitly matched by
186 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
187 subdirectories must be reviewed.
190 The default ARM ABI has changed to the ARM EABI. The old ABI is
191 incompatible with the ARM EABI and all programs and modules will
192 need to be rebuilt to work with a new kernel.
194 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
196 NOTE: Support for the old ABI will be removed in the future and
197 users are advised to upgrade.
200 pkg_install has been disconnected from the build if you really need it
201 you should add WITH_PKGTOOLS in your src.conf(5).
204 Most of network statistics structures were changed to be able
205 keep 64-bits counters. Thus all tools, that work with networking
206 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
209 Fix targets that run multiple make's to use && rather than ;
210 so that subsequent steps depend on success of previous.
212 NOTE: if building 'universe' with -j* on stable/8 or stable/9
213 it would be better to start the build using bmake, to avoid
214 overloading the machine.
217 Fix a bug that allowed a tracing process (e.g. gdb) to write
218 to a memory-mapped file in the traced process's address space
219 even if neither the traced process nor the tracing process had
220 write access to that file.
223 CVS has been removed from the base system. An exact copy
224 of the code is available from the devel/cvs port.
227 Some people report the following error after the switch to bmake:
229 make: illegal option -- J
230 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
232 *** [buildworld] Error code 2
234 this likely due to an old instance of make in
235 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
236 which src/Makefile will use that blindly, if it exists, so if
237 you see the above error:
239 rm -rf `make -V MAKEPATH`
244 Use bmake by default.
245 Whereas before one could choose to build with bmake via
246 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
247 make. The goal is to remove these knobs for 10-RELEASE.
249 It is worth noting that bmake (like gmake) treats the command
250 line as the unit of failure, rather than statements within the
251 command line. Thus '(cd some/where && dosomething)' is safer
252 than 'cd some/where; dosomething'. The '()' allows consistent
253 behavior in parallel build.
256 Fix a bug that allows NFS clients to issue READDIR on files.
259 The WITHOUT_IDEA option has been removed because
260 the IDEA patent expired.
263 The sysctl which controls TRIM support under ZFS has been renamed
264 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
268 The mergemaster command now uses the default MAKEOBJDIRPREFIX
269 rather than creating it's own in the temporary directory in
270 order allow access to bootstrapped versions of tools such as
271 install and mtree. When upgrading from version of FreeBSD where
272 the install command does not support -l, you will need to
273 install a new mergemaster command if mergemaster -p is required.
274 This can be accomplished with the command (cd src/usr.sbin/mergemaster
278 Legacy ATA stack, disabled and replaced by new CAM-based one since
279 FreeBSD 9.0, completely removed from the sources. Kernel modules
280 atadisk and atapi*, user-level tools atacontrol and burncd are
281 removed. Kernel option `options ATA_CAM` is now permanently enabled
285 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
286 and socketpair(2). Software, in particular Kerberos, may
287 automatically detect and use these during building. The resulting
288 binaries will not work on older kernels.
291 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
292 information, see the respective 20130304 entry).
295 Recent commits to callout(9) changed the size of struct callout,
296 so the KBI is probably heavily disturbed. Also, some functions
297 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
298 by macros. Every kernel module using it won't load, so rebuild
301 The ctl device has been re-enabled in GENERIC for i386 and amd64,
302 but does not initialize by default (because of the new CTL_DISABLE
303 option) to save memory. To re-enable it, remove the CTL_DISABLE
304 option from the kernel config file or set kern.cam.ctl.disable=0
305 in /boot/loader.conf.
308 The ctl device has been disabled in GENERIC for i386 and amd64.
309 This was done due to the extra memory being allocated at system
310 initialisation time by the ctl driver which was only used if
311 a CAM target device was created. This makes a FreeBSD system
312 unusable on 128MB or less of RAM.
315 A new compression method (lz4) has been merged to -HEAD. Please
316 refer to zpool-features(7) for more information.
318 Please refer to the "ZFS notes" section of this file for information
319 on upgrading boot ZFS pools.
322 A BSD-licensed patch(1) variant has been added and is installed
323 as bsdpatch, being the GNU version the default patch.
324 To inverse the logic and use the BSD-licensed one as default,
325 while having the GNU version installed as gnupatch, rebuild
326 and install world with the WITH_BSD_PATCH knob set.
329 Due to the use of the new -l option to install(1) during build
330 and install, you must take care not to directly set the INSTALL
331 make variable in your /etc/make.conf, /etc/src.conf, or on the
332 command line. If you wish to use the -C flag for all installs
333 you may be able to add INSTALL+=-C to /etc/make.conf or
337 The install(1) option -M has changed meaning and now takes an
338 argument that is a file or path to append logs to. In the
339 unlikely event that -M was the last option on the command line
340 and the command line contained at least two files and a target
341 directory the first file will have logs appended to it. The -M
342 option served little practical purpose in the last decade so its
343 use is expected to be extremely rare.
346 After switching to Clang as the default compiler some users of ZFS
347 on i386 systems started to experience stack overflow kernel panics.
348 Please consider using 'options KSTACK_PAGES=4' in such configurations.
351 GEOM_LABEL now mangles label names read from file system metadata.
352 Mangling affect labels containing spaces, non-printable characters,
353 '%' or '"'. Device names in /etc/fstab and other places may need to
357 By default, only the 10 most recent kernel dumps will be saved. To
358 restore the previous behaviour (no limit on the number of kernel dumps
359 stored in the dump directory) add the following line to /etc/rc.conf:
364 With the addition of auditdistd(8), a new auditdistd user is now
365 required during installworld. "mergemaster -p" can be used to
366 add the user prior to installworld, as documented in the handbook.
369 The sin6_scope_id member variable in struct sockaddr_in6 is now
370 filled by the kernel before passing the structure to the userland via
371 sysctl or routing socket. This means the KAME-specific embedded scope
372 id in sin6_addr.s6_addr[2] is always cleared in userland application.
373 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
374 __FreeBSD_version is bumped to 1000025.
377 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
378 This means that the world and kernel will be compiled with clang
379 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
380 and /usr/bin/cpp. To disable this behavior and revert to building
381 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
382 of current may need to bootstrap WITHOUT_CLANG first if the clang
383 build fails (its compatibility window doesn't extend to the 9 stable
387 The IPFIREWALL_FORWARD kernel option has been removed. Its
388 functionality now turned on by default.
391 The ZERO_COPY_SOCKET kernel option has been removed and
392 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
393 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
394 mechanism which is not safe and may result in kernel crashes.
395 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
396 driver supports disposeable external page sized mbuf storage.
397 Proper replacements for both zero-copy mechanisms are under
398 consideration and will eventually lead to complete removal
399 of the two kernel options.
402 The IPv4 network stack has been converted to network byte
403 order. The following modules need to be recompiled together
404 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
405 pf(4), ipfw(4), ng_ipfw(4), stf(4).
408 Support for non-MPSAFE filesystems was removed from VFS. The
409 VFS_VERSION was bumped, all filesystem modules shall be
413 All the non-MPSAFE filesystems have been disconnected from
414 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
415 portalfs, smbfs, xfs.
418 The interface cloning API and ABI has changed. The following
419 modules need to be recompiled together with kernel:
420 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
421 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
422 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
425 The sdhci driver was split in two parts: sdhci (generic SD Host
426 Controller logic) and sdhci_pci (actual hardware driver).
427 No kernel config modifications are required, but if you
428 load sdhc as a module you must switch to sdhci_pci instead.
431 Import the FUSE kernel and userland support into base system.
434 The GNU sort(1) program has been removed since the BSD-licensed
435 sort(1) has been the default for quite some time and no serious
436 problems have been reported. The corresponding WITH_GNU_SORT
440 The pfil(9) API/ABI for AF_INET family has been changed. Packet
441 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
445 The net80211(4) ABI has been changed to allow for improved driver
446 PS-POLL and power-save support. All wireless drivers need to be
447 recompiled to work with the new kernel.
450 The random(4) support for the VIA hardware random number
451 generator (`PADLOCK') is no longer enabled unconditionally.
452 Add the padlock_rng device in the custom kernel config if
453 needed. The GENERIC kernels on i386 and amd64 do include the
454 device, so the change only affects the custom kernel
458 The pf(4) packet filter ABI has been changed. pfctl(8) and
459 snmp_pf module need to be recompiled to work with new kernel.
462 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
463 to -HEAD. Pools that have empty_bpobj in active state can not be
464 imported read-write with ZFS implementations that do not support
465 this feature. For more information read the zpool-features(5)
469 The sparc64 ZFS loader has been changed to no longer try to auto-
470 detect ZFS providers based on diskN aliases but now requires these
471 to be explicitly listed in the OFW boot-device environment variable.
474 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
475 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
476 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
479 The following sysctls and tunables have been renamed for consistency
480 with other variables:
481 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
482 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
485 The sort utility has been replaced with BSD sort. For now, GNU sort
486 is also available as "gnusort" or the default can be set back to
487 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
488 installed as "bsdsort".
491 A new version of ZFS (pool version 5000) has been merged to -HEAD.
492 Starting with this version the old system of ZFS pool versioning
493 is superseded by "feature flags". This concept enables forward
494 compatibility against certain future changes in functionality of ZFS
495 pools. The first read-only compatible "feature flag" for ZFS pools
496 is named "com.delphix:async_destroy". For more information
497 read the new zpool-features(5) manual page.
498 Please refer to the "ZFS notes" section of this file for information
499 on upgrading boot ZFS pools.
502 The malloc(3) implementation embedded in libc now uses sources imported
503 as contrib/jemalloc. The most disruptive API change is to
504 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
505 delete it prior to installworld, and optionally re-create it using the
506 new format after rebooting. See malloc.conf(5) for details
507 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
511 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
512 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
513 now spelled mips. This is to aid compatibility with third-party
514 software that expects this naming scheme in uname(3). Little-endian
515 settings are unchanged. If you are updating a big-endian mips64 machine
516 from before this change, you may need to set MACHINE_ARCH=mips64 in
517 your environment before the new build system will recognize your machine.
520 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
524 Now unix domain sockets behave "as expected" on nullfs(5). Previously
525 nullfs(5) did not pass through all behaviours to the underlying layer,
526 as a result if we bound to a socket on the lower layer we could connect
527 only to the lower path; if we bound to the upper layer we could connect
528 only to the upper path. The new behavior is one can connect to both the
529 lower and the upper paths regardless what layer path one binds to.
532 The getifaddrs upgrade path broken with 20111215 has been restored.
533 If you have upgraded in between 20111215 and 20120209 you need to
534 recompile libc again with your kernel. You still need to recompile
535 world to be able to configure CARP but this restriction already
539 The set_rcvar() function has been removed from /etc/rc.subr. All
540 base and ports rc.d scripts have been updated, so if you have a
541 port installed with a script in /usr/local/etc/rc.d you can either
542 hand-edit the rcvar= line, or reinstall the port.
544 An easy way to handle the mass-update of /etc/rc.d:
545 rm /etc/rc.d/* && mergemaster -i
548 panic(9) now stops other CPUs in the SMP systems, disables interrupts
549 on the current CPU and prevents other threads from running.
550 This behavior can be reverted using the kern.stop_scheduler_on_panic
552 The new behavior can be incompatible with kern.sync_on_panic.
555 The carp(4) facility has been changed significantly. Configuration
556 of the CARP protocol via ifconfig(8) has changed, as well as format
557 of CARP events submitted to devd(8) has changed. See manual pages
558 for more information. The arpbalance feature of carp(4) is currently
559 not supported anymore.
561 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
562 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
563 need to be recompiled.
566 The acpi_wmi(4) status device /dev/wmistat has been renamed to
570 The option VFS_ALLOW_NONMPSAFE option has been added in order to
571 explicitely support non-MPSAFE filesystems.
572 It is on by default for all supported platform at this present
576 The broken amd(4) driver has been replaced with esp(4) in the amd64,
577 i386 and pc98 GENERIC kernel configuration files.
580 sysinstall has been removed
583 The stable/9 branch created in subversion. This corresponds to the
584 RELENG_9 branch in CVS.
587 This commit modifies vfs_register() so that it uses a hash
588 calculation to set vfc_typenum, which is enabled by default.
589 The first time a system is booted after this change, the
590 vfc_typenum values will change for all file systems. The
591 main effect of this is a change to the NFS server file handles
592 for file systems that use vfc_typenum in their fsid, such as ZFS.
593 It will, however, prevent vfc_typenum from changing when file
594 systems are loaded in a different order for subsequent reboots.
595 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
596 until you are ready to remount all NFS clients after a reboot.
599 Bump the shared library version numbers for libraries that
600 do not use symbol versioning, have changed the ABI compared
601 to stable/8 and which shared library version was not bumped.
602 Done as part of 9.0-RELEASE cycle.
605 During the merge of Capsicum features, the fget(9) KPI was modified.
606 This may require the rebuilding of out-of-tree device drivers --
607 issues have been reported specifically with the nVidia device driver.
608 __FreeBSD_version is bumped to 900041.
610 Also, there is a period between 20110811 and 20110814 where the
611 special devices /dev/{stdin,stdout,stderr} did not work correctly.
612 Building world from a kernel during that window may not work.
615 The packet filter (pf) code has been updated to OpenBSD 4.5.
616 You need to update userland tools to be in sync with kernel.
617 This update breaks backward compatibility with earlier pfsync(4)
618 versions. Care must be taken when updating redundant firewall setups.
621 The following sysctls and tunables are retired on x86 platforms:
623 machdep.hlt_logical_cpus
624 The following sysctl is retired:
625 machdep.hyperthreading_allowed
626 The sysctls were supposed to provide a way to dynamically offline and
627 online selected CPUs on x86 platforms, but the implementation has not
628 been reliable especially with SCHED_ULE scheduler.
629 machdep.hyperthreading_allowed tunable is still available to ignore
630 hyperthreading CPUs at OS level.
631 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
632 where X is an APIC ID of a CPU. Be advised, though, that disabling
633 CPUs in non-uniform fashion will result in non-uniform topology and
634 may lead to sub-optimal system performance with SCHED_ULE, which is
638 cpumask_t type is retired and cpuset_t is used in order to describe
642 Changes to ifconfig(8) for dynamic address family detection mandate
643 that you are running a kernel of 20110525 or later. Make sure to
644 follow the update procedure to boot a new kernel before installing
648 Support for sun4v architecture is officially dropped
651 Several KPI breaking changes have been committed to the mii(4) layer,
652 the PHY drivers and consequently some Ethernet drivers using mii(4).
653 This means that miibus.ko and the modules of the affected Ethernet
654 drivers need to be recompiled.
656 Note to kernel developers: Given that the OUI bit reversion problem
657 was fixed as part of these changes all mii(4) commits related to OUIs,
658 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
659 handling, no longer can be merged verbatim to stable/8 and previous
663 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
664 into their kernel configurations along with 'device pci'.
667 The default NFS client is now the new NFS client, so fstype "newnfs"
668 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
669 Although mounts via fstype "nfs" will usually work without userland
670 changes, it is recommended that the mount(8) and mount_nfs(8)
671 commands be rebuilt from sources and that a link to mount_nfs called
672 mount_oldnfs be created. The new client is compiled into the
673 kernel with "options NFSCL" and this is needed for diskless root
674 file systems. The GENERIC kernel configs have been changed to use
675 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
676 To use the regular/old client, you can "mount -t oldnfs ...". For
677 a diskless root file system, you must also include a line like:
679 vfs.root.mountfrom="oldnfs:"
681 in the boot/loader.conf on the root fs on the NFS server to make
682 a diskless root fs use the old client.
685 The GENERIC kernels for all architectures now default to the new
686 CAM-based ATA stack. It means that all legacy ATA drivers were
687 removed and replaced by respective CAM drivers. If you are using
688 ATA device names in /etc/fstab or other places, make sure to update
689 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
690 where 'Y's are the sequential numbers starting from zero for each type
691 in order of detection, unless configured otherwise with tunables,
692 see cam(4)). There will be symbolic links created in /dev/ to map
693 old adX devices to the respective adaY. They should provide basic
694 compatibility for file systems mounting in most cases, but they do
695 not support old user-level APIs and do not have respective providers
696 in GEOM. Consider using updated management tools with new device names.
698 It is possible to load devices ahci, ata, siis and mvs as modules,
699 but option ATA_CAM should remain in kernel configuration to make ata
700 module work as CAM driver supporting legacy ATA controllers. Device ata
701 still can be used in modular fashion (atacore + ...). Modules atadisk
702 and atapi* are not used and won't affect operation in ATA_CAM mode.
703 Note that to use CAM-based ATA kernel should include CAM devices
704 scbus, pass, da (or explicitly ada), cd and optionally others. All of
705 them are parts of the cam module.
707 ataraid(4) functionality is now supported by the RAID GEOM class.
708 To use it you can load geom_raid kernel module and use graid(8) tool
709 for management. Instead of /dev/arX device names, use /dev/raid/rX.
711 No kernel config options or code have been removed, so if a problem
712 arises, please report it and optionally revert to the old ATA stack.
713 In order to do it you can remove from the kernel config:
718 , and instead add back:
719 device atadisk # ATA disk drives
720 device ataraid # ATA RAID drives
721 device atapicd # ATAPI CDROM drives
722 device atapifd # ATAPI floppy drives
723 device atapist # ATAPI tape drives
726 The default NFS server has been changed to the new server, which
727 was referred to as the experimental server. If you need to switch
728 back to the old NFS server, you must now put the "-o" option on
729 both the mountd and nfsd commands. This can be done using the
730 mountd_flags and nfs_server_flags rc.conf variables until an
731 update to the rc scripts is committed, which is coming soon.
734 The GNU Objective-C runtime library (libobjc), and other Objective-C
735 related components have been removed from the base system. If you
736 require an Objective-C library, please use one of the available ports.
739 ath(4) has been split into bus- and device- modules. if_ath contains
740 the HAL, the TX rate control and the network device code. if_ath_pci
741 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
742 contains the AHB glue. Users need to load both if_ath_pci and if_ath
743 in order to use ath on everything else.
745 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
746 need to load if_ath and if_ath_pci for ath(4) operation.
749 As part of the replacement of sysinstall, the process of building
750 release media has changed significantly. For details, please re-read
751 release(7), which has been updated to reflect the new build process.
754 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
755 is the last available version under GPLv2. It brings a number of new
756 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
757 4.1 and SSE 4.2), better support for powerpc64, a number of new
758 directives, and lots of other small improvements. See the ChangeLog
759 file in contrib/binutils for the full details.
762 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
763 compliant, and will now use half of hash for authentication.
764 This will break interoperability with all stacks (including all
765 actual FreeBSD versions) who implement
766 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
768 The only workaround with such peers is to use another HMAC
769 algorithm for IPsec ("phase 2") authentication.
772 Remove the uio_yield prototype and symbol. This function has
773 been misnamed since it was introduced and should not be
774 globally exposed with this name. The equivalent functionality
775 is now available using kern_yield(curthread->td_user_pri).
776 The function remains undocumented.
779 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
780 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
781 for scalar sysctls is defined but disabled. Code that needs
782 UQUAD to pass the type checking that must compile on older
783 systems where the define is not present can check against
784 __FreeBSD_version >= 900030.
786 The system dialog(1) has been replaced with a new version previously
787 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
788 with the previous version, but the libdialog associated with it has
789 a largely incompatible API. As such, the original version of libdialog
790 will be kept temporarily as libodialog, until its base system consumers
791 are replaced or updated. Bump __FreeBSD_version to 900030.
794 If you are trying to run make universe on a -stable system, and you get
795 the following warning:
796 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
797 unknown. config(8) likely too old."
798 or something similar to it, then you must upgrade your -stable system
799 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
800 stable/8) or build the config from the latest stable/8 branch and
801 install it on your system.
803 Prior to this date, building a current universe on 8-stable system from
804 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
805 error in the first kernel build phase. A new config on those old
806 systems will fix that problem for older versions of -current.
809 The TCP stack has been modified to allow Khelp modules to interact with
810 it via helper hook points and store per-connection data in the TCP
811 control block. Bump __FreeBSD_version to 900029. User space tools that
812 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
816 Generic IEEE 802.3 annex 31B full duplex flow control support has been
817 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
818 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
819 to take advantage of it instead of using custom implementations. This
820 means that these drivers now no longer unconditionally advertise
821 support for flow control but only do so if flow control is a selected
822 media option. This was implemented in the generic support that way in
823 order to allow flow control to be switched on and off via ifconfig(8)
824 with the PHY specific default to typically off in order to protect
825 from unwanted effects. Consequently, if you used flow control with
826 one of the above mentioned drivers you now need to explicitly enable
828 ifconfig bge0 media auto mediaopt flowcontrol
830 Along with the above mentioned changes generic support for setting
831 1000baseT master mode also has been added and brgphy(4), ciphy(4),
832 e1000phy(4) as well as ip1000phy(4) have been converted to take
833 advantage of it. This means that these drivers now no longer take the
834 link0 parameter for selecting master mode but the master media option
835 has to be used instead, for example like in the following:
836 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
838 Selection of master mode now is also available with all other PHY
839 drivers supporting 1000baseT.
842 The TCP stack has received a significant update to add support for
843 modularised congestion control and generally improve the clarity of
844 congestion control decisions. Bump __FreeBSD_version to 900025. User
845 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
846 sockstat) need to be recompiled.
849 The man(1) utility has been replaced by a new version that no longer
850 uses /etc/manpath.config. Please consult man.conf(5) for how to
851 migrate local entries to the new format.
854 The copyright strings printed by login(1) and sshd(8) at the time of a
855 new connection have been removed to follow other operating systems and
859 A workaround for a fixed ld bug has been removed in kernel code,
860 so make sure that your system ld is built from sources after
861 revision 210245 from 2010-07-19 (r211583 if building head kernel
862 on stable/8, r211584 for stable/7; both from 2010-08-21).
863 A symptom of incorrect ld version is different addresses for
864 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
867 The $ipv6_prefer variable in rc.conf(5) has been split into
868 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
870 The $ip6addrctl_policy is a variable to choose a pre-defined
871 address selection policy set by ip6addrctl(8). A value
872 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
875 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
876 flag (see an entry of 20090926) is set on an interface with no
877 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
878 security reason. If you want IPv6 link-local address on all
879 interfaces by default, set this to "YES".
881 The old ipv6_prefer="YES" is equivalent to
882 ipv6_activate_all_interfaces="YES" and
883 ip6addrctl_policy="ipv6_prefer".
886 DTrace has grown support for userland tracing. Due to this, DTrace is
887 now i386 and amd64 only.
888 dtruss(1) is now installed by default on those systems and a new
889 kernel module is needed for userland tracing: fasttrap.
890 No changes to your kernel config file are necessary to enable
891 userland tracing, but you might consider adding 'STRIP=' and
892 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
893 to have informative userland stack traces in DTrace (ustack).
896 The acpi_aiboost(4) driver has been removed in favor of the new
897 aibs(4) driver. You should update your kernel configuration file.
900 BSD grep has been imported to the base system and it is built by
901 default. It is completely BSD licensed, highly GNU-compatible, uses
902 less memory than its GNU counterpart and has a small codebase.
903 However, it is slower than its GNU counterpart, which is mostly
904 noticeable for larger searches, for smaller ones it is measurable
905 but not significant. The reason is complex, the most important factor
906 is that we lack a modern and efficient regex library and GNU
907 overcomes this by optimizing the searches internally. Future work
908 on improving the regex performance is planned, for the meantime,
909 users that need better performance, can build GNU grep instead by
910 setting the WITH_GNU_GREP knob.
913 Due to the import of powerpc64 support, all existing powerpc kernel
914 configuration files must be updated with a machine directive like this:
915 machine powerpc powerpc
917 In addition, an updated config(8) is required to build powerpc kernels
921 A new version of ZFS (version 15) has been merged to -HEAD.
922 This version uses a python library for the following subcommands:
923 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
924 For full functionality of these commands the following port must
925 be installed: sysutils/py-zfs
928 'vm_page's are now hashed by physical address to an array of mutexes.
929 Currently this is only used to serialize access to hold_count. Over
930 time the page queue mutex will be peeled away. This changes the size
931 of pmap on every architecture. And requires all callers of vm_page_hold
932 and vm_page_unhold to be updated.
935 WITH_CTF can now be specified in src.conf (not recommended, there
936 are some problems with static executables), make.conf (would also
937 affect ports which do not use GNU make and do not override the
938 compile targets) or in the kernel config (via "makeoptions
940 When WITH_CTF was specified there before this was silently ignored,
941 so make sure that WITH_CTF is not used in places which could lead
942 to unwanted behavior.
945 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
946 to allow 32-bit compatibility on non-x86 platforms. All kernel
947 configurations on amd64 and ia64 platforms using these options must
948 be modified accordingly.
951 The utmp user accounting database has been replaced with utmpx,
952 the user accounting interface standardized by POSIX.
953 Unfortunately the semantics of utmp and utmpx don't match,
954 making it practically impossible to support both interfaces.
955 The user accounting database is used by tools like finger(1),
956 last(1), talk(1), w(1) and ac(8).
958 All applications in the base system use utmpx. This means only
959 local binaries (e.g. from the ports tree) may still use these
960 utmp database files. These applications must be rebuilt to make
963 After the system has been upgraded, it is safe to remove the old
964 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
965 assuming their contents is of no importance anymore. Old wtmp
966 databases can only be used by last(1) and ac(8) after they have
967 been converted to the new format using wtmpcvt(1).
970 Introduce the kernel thread "deadlock resolver" (which can be enabled
971 via the DEADLKRES option, see NOTES for more details) and the
972 sleepq_type() function for sleepqueues.
975 The rc.firewall and rc.firewall6 were unified, and
976 rc.firewall6 and rc.d/ip6fw were removed.
977 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
978 variables are obsoleted. Instead, the following new rc
979 variables are added to rc.d/ipfw:
981 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
982 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
983 firewall_simple_onet_ipv6, firewall_trusted_ipv6
985 The meanings correspond to the relevant IPv4 variables.
991 The default terminal emulation for syscons(4) has been changed
992 from cons25 to xterm on all platforms except pc98. This means
993 that the /etc/ttys file needs to be updated to ensure correct
994 operation of applications on the console.
996 The terminal emulation style can be toggled per window by using
997 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
998 options can be used to change the compile-time default back to
1001 To prevent graphical artifacts, make sure the TERM environment
1002 variable is set to match the terminal emulation that is being
1003 performed by syscons(4).
1006 The layout of the structure ieee80211req_scan_result has changed.
1007 Applications that require wireless scan results (e.g. ifconfig(8))
1008 from net80211 need to be recompiled.
1010 Applications such as wpa_supplicant(8) may require a full world
1011 build without using NO_CLEAN in order to get synchronized with the
1015 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1016 There's one kernel module for each firmware. Adding "device iwnfw"
1017 to the kernel configuration file means including all three firmware
1018 images inside the kernel. If you want to include just the one for
1019 your wireless card, use the devices iwn4965fw, iwn5000fw or
1023 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1024 into rc.d/netif. The changes are the following:
1026 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1027 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1028 Note that both variables need the "inet6" keyword at the head.
1030 Do not set $ipv6_network_interfaces manually if you do not
1031 understand what you are doing. It is not needed in most cases.
1033 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1036 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1037 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1039 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1040 all configured interfaces have "inet6 accept_rtadv" in the
1041 $ifconfig_IF_ipv6. These are for backward compatibility.
1043 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1044 functionality of interfaces with no corresponding
1045 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1046 and the default address selection policy of ip6addrctl(8)
1047 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1048 Note that if you want to configure IPv6 functionality on the
1049 disabled interfaces after boot, first you need to clear the flag by
1050 using ifconfig(8) like:
1052 ifconfig em0 inet6 -ifdisabled
1054 If YES, the default address selection policy is set as
1057 The default value of $ipv6_prefer is NO.
1059 4. If your system need to receive Router Advertisement messages,
1060 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1061 scripts automatically invoke rtsol(8) when the interface becomes
1062 UP. The Router Advertisement messages are used for SLAAC
1063 (State-Less Address AutoConfiguration).
1066 802.11s D3.03 support was committed. This is incompatible with the
1067 previous code, which was based on D3.0.
1070 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1071 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1072 control whether accepting Router Advertisement messages or not.
1073 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1074 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1075 The ifconfig(8) utility now supports these flags.
1078 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1079 mount(8) and -a option for df(1) to see them.
1082 The old tunable hw.bus.devctl_disable has been superseded by
1083 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1084 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1088 Remove the option STOP_NMI. The default action is now to use NMI only
1089 for KDB via the newly introduced function stop_cpus_hard() and
1090 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1093 The stable/8 branch created in subversion. This corresponds to the
1094 RELENG_8 branch in CVS.
1097 Bump the shared library version numbers for all libraries that do not
1098 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1099 __FreeBSD_version to 800105.
1102 Due to changes in the implementation of virtual network stack support,
1103 all network-related kernel modules must be recompiled. As this change
1104 breaks the ABI, bump __FreeBSD_version to 800104.
1107 The TOE interface to the TCP syncache has been modified to remove
1108 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1109 The cxgb driver is the only TOE consumer affected by this change, and
1110 needs to be recompiled along with the kernel. As this change breaks
1111 the ABI, bump __FreeBSD_version to 800103.
1114 Padding has been added to struct tcpcb, sackhint and tcpstat in
1115 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1116 maintaining the ABI. However, this change breaks the ABI, so bump
1117 __FreeBSD_version to 800102. User space tools that rely on the size of
1118 any of these structs (e.g. sockstat) need to be recompiled.
1121 The NFS_LEGACYRPC option has been removed along with the old kernel
1122 RPC implementation that this option selected. Kernel configurations
1123 may need to be adjusted.
1126 The network interface device nodes at /dev/net/<interface> have been
1127 removed. All ioctl operations can be performed the normal way using
1128 routing sockets. The kqueue functionality can generally be replaced
1129 with routing sockets.
1132 The documentation from the FreeBSD Documentation Project (Handbook,
1133 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1134 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1137 The ABI of various structures related to the SYSV IPC API have been
1138 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1139 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1143 Layout of struct vnet has changed as routing related variables were
1144 moved to their own Vimage module. Modules need to be recompiled. Bump
1145 __FreeBSD_version to 800099.
1148 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1149 respectively. As long as no more than 16 groups per process are used,
1150 no changes should be visible. When more than 16 groups are used, old
1151 binaries may fail if they call getgroups() or getgrouplist() with
1152 statically sized storage. Recompiling will work around this, but
1153 applications should be modified to use dynamically allocated storage
1154 for group arrays as POSIX.1-2008 does not cap an implementation's
1155 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1157 NFS and portalfs mounts may also be affected as the list of groups is
1158 truncated to 16. Users of NFS who use more than 16 groups, should
1159 take care that negative group permissions are not used on the exported
1160 file systems as they will not be reliable unless a GSSAPI based
1161 authentication method is used.
1164 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1165 option compiles in the support for adaptive spinning for lockmgrs
1166 which want to enable it. The lockinit() function now accepts the flag
1167 LK_ADAPTIVE in order to make the lock object subject to adaptive
1168 spinning when both held in write and read mode.
1171 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1172 changed. User applications that use this ioctl need to be rebuilt.
1175 The layout of struct thread has changed. Kernel and modules need to
1179 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1180 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1183 window(1) has been removed from the base system. It can now be
1184 installed from ports. The port is called misc/window.
1187 The way we are storing and accessing `routing table' entries has
1188 changed. Programs reading the FIB, like netstat, need to be
1192 A new netisr implementation has been added for FreeBSD 8. Network
1193 file system modules, such as igmp, ipdivert, and others, should be
1195 Bump __FreeBSD_version to 800096.
1198 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1202 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1203 Bump __FreeBSD_version to 800094.
1206 Add mnt_xflag field to 'struct mount'. File system modules need to be
1208 Bump __FreeBSD_version to 800093.
1211 The compiling option ADAPTIVE_SX has been retired while it has been
1212 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1213 The KPI for sx_init_flags() changes as accepting flags:
1214 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1215 been introduced in order to handle the reversed logic.
1216 Bump __FreeBSD_version to 800092.
1219 Add support for hierarchical jails. Remove global securelevel.
1220 Bump __FreeBSD_version to 800091.
1223 The layout of struct vnet_net has changed, therefore modules
1225 Bump __FreeBSD_version to 800090.
1228 The newly imported zic(8) produces a new format in the output. Please
1229 run tzsetup(8) to install the newly created data to /etc/localtime.
1232 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1233 hw.usb.* and is now consistent again with previous releases.
1236 802.11 monitor mode support was revised and driver api's were changed.
1237 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1238 of DLT_IEEE802_11. No user-visible data structures were changed but
1239 applications that use DLT_IEEE802_11 may require changes.
1240 Bump __FreeBSD_version to 800088.
1243 The layout of the following structs has changed: sysctl_oid,
1244 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1245 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1246 panics may be experienced. World rebuild is required for
1247 correctly checking networking state from userland.
1248 Bump __FreeBSD_version to 800085.
1251 MLDv2 and Source-Specific Multicast (SSM) have been merged
1252 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1253 The implementation of SSM within FreeBSD's IPv6 stack closely
1254 follows the IPv4 implementation.
1256 For kernel developers:
1258 * The most important changes are that the ip6_output() and
1259 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1260 and this lock has been downgraded to a non-recursive mutex.
1262 * As with the changes to the IPv4 stack to support SSM, filtering
1263 of inbound multicast traffic must now be performed by transport
1264 protocols within the IPv6 stack. This does not apply to TCP and
1265 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1267 * The KPIs used by IPv6 multicast are similar to those used by
1268 the IPv4 stack, with the following differences:
1269 * im6o_mc_filter() is analogous to imo_multicast_filter().
1270 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1271 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1272 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1273 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1274 for MLDv1 have an additional 'timer' argument which is used to
1275 jitter the initial membership report for the solicited-node
1276 multicast membership on-link.
1277 * This is not strictly needed for MLDv2, which already jitters
1278 its report transmissions. However, the 'timer' argument is
1279 preserved in case MLDv1 is active on the interface.
1281 * The KAME linked-list based IPv6 membership implementation has
1282 been refactored to use a vector similar to that used by the IPv4
1284 Code which maintains a list of its own multicast memberships
1285 internally, e.g. carp, has been updated to reflect the new
1288 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1289 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1290 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1291 implementation constraint which needs to be addressed in HEAD.
1293 For application developers:
1295 * The changes are broadly similar to those made for the IPv4
1298 * The use of IPv4 and IPv6 multicast socket options on the same
1299 socket, using mapped addresses, HAS NOT been tested or supported.
1301 * There are a number of issues with the implementation of various
1302 IPv6 multicast APIs which need to be resolved in the API surface
1303 before the implementation is fully compatible with KAME userland
1304 use, and these are mostly to do with interface index treatment.
1306 * The literature available discusses the use of either the delta / ASM
1307 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1308 using setsourcefilter(3)/getsourcefilter(3). For more information
1309 please refer to RFC 3768, 'Socket Interface Extensions for
1310 Multicast Source Filters'.
1312 * Applications which use the published RFC 3678 APIs should be fine.
1314 For systems administrators:
1316 * The mtest(8) utility has been refactored to support IPv6, in
1317 addition to IPv4. Interface addresses are no longer accepted
1318 as arguments, their names must be used instead. The utility
1319 will map the interface name to its first IPv4 address as
1320 returned by getifaddrs(3).
1322 * The ifmcstat(8) utility has also been updated to print the MLDv2
1323 endpoint state and source filter lists via sysctl(3).
1325 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1326 loopback of IPv6 multicast datagrams by default; it defaults to 1
1327 to preserve the existing behaviour. Disabling multicast loopback is
1328 recommended for optimal system performance.
1330 * The IPv6 MROUTING code has been changed to examine this sysctl
1331 instead of attempting to perform a group lookup before looping
1332 back forwarded datagrams.
1334 Bump __FreeBSD_version to 800084.
1337 Implement low-level Bluetooth HCI API.
1338 Bump __FreeBSD_version to 800083.
1341 The layout of struct malloc_type, used by modules to register new
1342 memory allocation types, has changed. Most modules will need to
1343 be rebuilt or panics may be experienced.
1344 Bump __FreeBSD_version to 800081.
1347 Anticipate overflowing inp_flags - add inp_flags2.
1348 This changes most offsets in inpcb, so checking v4 connection
1349 state will require a world rebuild.
1350 Bump __FreeBSD_version to 800080.
1353 Add an llentry to struct route and struct route_in6. Modules
1354 embedding a struct route will need to be recompiled.
1355 Bump __FreeBSD_version to 800079.
1358 The size of rt_metrics_lite and by extension rtentry has changed.
1359 Networking administration apps will need to be recompiled.
1360 The route command now supports show as an alias for get, weighting
1361 of routes, sticky and nostick flags to alter the behavior of stateful
1363 Bump __FreeBSD_version to 800078.
1366 Do not use Giant for kbdmux(4) locking. This is wrong and
1367 apparently causing more problems than it solves. This will
1368 re-open the issue where interrupt handlers may race with
1369 kbdmux(4) in polling mode. Typical symptoms include (but
1370 not limited to) duplicated and/or missing characters when
1371 low level console functions (such as gets) are used while
1372 interrupts are enabled (for example geli password prompt,
1373 mountroot prompt etc.). Disabling kbdmux(4) may help.
1376 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1377 kernel modules referencing any of the above need to be recompiled.
1378 Bump __FreeBSD_version to 800075.
1381 GEOM_PART has become the default partition slicer for storage devices,
1382 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1383 introduces some changes:
1385 MSDOS/EBR: the devices created from MSDOS extended partition entries
1386 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1387 to devices with offset-based names. fstabs may need to be modified.
1389 BSD: the "geometry does not match label" warning is harmless in most
1390 cases but it points to problems in file system misalignment with
1391 disk geometry. The "c" partition is now implicit, covers the whole
1392 top-level drive and cannot be (mis)used by users.
1394 General: Kernel dumps are now not allowed to be written to devices
1395 whose partition types indicate they are meant to be used for file
1396 systems (or, in case of MSDOS partitions, as something else than
1399 Most of these changes date approximately from 200812.
1402 The uscanner(4) driver has been removed from the kernel. This follows
1403 Linux removing theirs in 2.6 and making libusb the default interface
1404 (supported by sane).
1407 The multicast forwarding code has been cleaned up. netstat(1)
1408 only relies on KVM now for printing bandwidth upcall meters.
1409 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1410 ip6_mroute_mod respectively. The config(5) options for statically
1411 compiling this code remain the same, i.e. 'options MROUTING'.
1414 Support for the IFF_NEEDSGIANT network interface flag has been
1415 removed, which means that non-MPSAFE network device drivers are no
1416 longer supported. In particular, if_ar, if_sr, and network device
1417 drivers from the old (legacy) USB stack can no longer be built or
1421 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1422 a bunch of new language catalog files have also been added.
1423 This means that some common libc messages are now localized and
1424 they depend on the LC_MESSAGES environmental variable.
1427 The k8temp(4) driver has been renamed to amdtemp(4) since
1428 support for Family 10 and Family 11 CPU families was added.
1431 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1432 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1434 For kernel developers, the most important changes are that the
1435 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1436 and this lock has been downgraded to a non-recursive mutex.
1438 Transport protocols (UDP, Raw IP) are now responsible for filtering
1439 inbound multicast traffic according to group membership and source
1440 filters. The imo_multicast_filter() KPI exists for this purpose.
1441 Transports which do not use multicast (SCTP, TCP) already reject
1442 multicast by default. Forwarding and receive performance may improve
1443 as a mutex acquisition is no longer needed in the ip_input()
1444 low-level input path. in_addmulti() and in_delmulti() are shimmed
1445 to new KPIs which exist to support SSM in-kernel.
1447 For application developers, it is recommended that loopback of
1448 multicast datagrams be disabled for best performance, as this
1449 will still cause the lock to be taken for each looped-back
1450 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1451 be tuned to 0 to disable loopback by default; it defaults to 1
1452 to preserve the existing behaviour.
1454 For systems administrators, to obtain best performance with
1455 multicast reception and multiple groups, it is always recommended
1456 that a card with a suitably precise hash filter is used. Hash
1457 collisions will still result in the lock being taken within the
1458 transport protocol input path to check group membership.
1460 If deploying FreeBSD in an environment with IGMP snooping switches,
1461 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1462 enabled; this forces 224.0.0.0/24 group membership to be announced
1465 The size of 'struct igmpstat' has changed; netstat needs to be
1466 recompiled to reflect this.
1467 Bump __FreeBSD_version to 800070.
1470 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1471 updated to use it. This requires a buildworld/installworld in order to
1472 update the library and dependencies (usbconfig, etc). Its advisable to
1473 rebuild all ports which uses libusb. More specific directions are given
1474 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1475 libusb are no longer required and can be removed.
1478 A workaround is committed to allow the creation of System V shared
1479 memory segment of size > 2 GB on the 64-bit architectures.
1480 Due to a limitation of the existing ABI, the shm_segsz member
1481 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1482 wrong for large segments. Note that limits must be explicitly
1483 raised to allow such segments to be created.
1486 The layout of struct ifnet has changed, requiring a rebuild of all
1487 network device driver modules.
1490 The /dev handling for the new USB stack has changed, a
1491 buildworld/installworld is required for libusb20.
1494 The new USB2 stack has now been permanently moved in and all kernel and
1495 module names reverted to their previous values (eg, usb, ehci, ohci,
1496 ums, ...). The old usb stack can be compiled in by prefixing the name
1497 with the letter 'o', the old usb modules have been removed.
1498 Updating entry 20090216 for xorg and 20090215 for libmap may still
1502 The rc.conf(5) option if_up_delay has been renamed to
1503 defaultroute_delay to better reflect its purpose. If you have
1504 customized this setting in /etc/rc.conf you need to update it to
1508 xorg 7.4 wants to configure its input devices via hald which does not
1509 yet work with USB2. If the keyboard/mouse does not work in xorg then
1511 Option "AllowEmptyInput" "off"
1512 to your ServerLayout section. This will cause X to use the configured
1513 kbd and mouse sections from your xorg.conf.
1516 The GENERIC kernels for all architectures now default to the new USB2
1517 stack. No kernel config options or code have been removed so if a
1518 problem arises please report it and optionally revert to the old USB
1519 stack. If you are loading USB kernel modules or have a custom kernel
1520 that includes GENERIC then ensure that usb names are also changed over,
1521 eg uftdi -> usb2_serial_ftdi.
1523 Older programs linked against the ports libusb 0.1 need to be
1524 redirected to the new stack's libusb20. /etc/libmap.conf can
1526 # Map old usb library to new one for usb2 stack
1527 libusb-0.1.so.8 libusb20.so.1
1530 All USB ethernet devices now attach as interfaces under the name ueN
1531 (eg. ue0). This is to provide a predictable name as vendors often
1532 change usb chipsets in a product without notice.
1535 The ichsmb(4) driver has been changed to require SMBus slave
1536 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1537 All of the other SMBus controller drivers require left-justified
1538 slave addresses, so this change makes all the drivers provide the
1542 INET6 statistics (struct ip6stat) was updated.
1543 netstat(1) needs to be recompiled.
1546 NTFS has been removed from GENERIC kernel on amd64 to match
1547 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1548 will load ntfs.ko module automatically when NTFS support is
1549 actually needed, unless ntfs.ko is not installed or security
1550 level prohibits loading kernel modules. If either is the case,
1551 "options NTFS" has to be added into kernel config.
1554 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1555 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1556 800061. User space tools that rely on the size of struct tcpcb in
1557 tcp_var.h (e.g. sockstat) need to be recompiled.
1560 ng_tty(4) module updated to match the new TTY subsystem.
1561 Due to API change, user-level applications must be updated.
1562 New API support added to mpd5 CVS and expected to be present
1563 in next mpd5.3 release.
1566 With __FreeBSD_version 800060 the makefs tool is part of
1567 the base system (it was a port).
1570 The afdata and ifnet locks have been changed from mutexes to
1571 rwlocks, network modules will need to be re-compiled.
1574 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1575 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1576 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1577 architecture and 40 bytes on 64-bit architecture. The userland
1578 applications "arp" and "ndp" have been updated accordingly.
1579 The output from "netstat -r" shows only routing entries and
1580 none of the L2 information.
1583 __FreeBSD_version 800057 marks the switchover from the
1584 binary ath hal to source code. Users must add the line:
1586 options AH_SUPPORT_AR5416
1588 to their kernel config files when specifying:
1592 The ath_hal module no longer exists; the code is now compiled
1593 together with the driver in the ath module. It is now
1594 possible to tailor chip support (i.e. reduce the set of chips
1595 and thereby the code size); consult ath_hal(4) for details.
1598 __FreeBSD_version 800054 adds memory barriers to
1599 <machine/atomic.h>, new interfaces to ifnet to facilitate
1600 multiple hardware transmit queues for cards that support
1601 them, and a lock-less ring-buffer implementation to
1602 enable drivers to more efficiently manage queueing of
1606 A new version of ZFS (version 13) has been merged to -HEAD.
1607 This version has zpool attribute "listsnapshots" off by
1608 default, which means "zfs list" does not show snapshots,
1609 and is the same as Solaris behavior.
1612 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1615 The uhci, ohci, ehci and slhci USB Host controller drivers have
1616 been put into separate modules. If you load the usb module
1617 separately through loader.conf you will need to load the
1618 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1619 controller add the following to loader.conf:
1625 The ABI used by the PMC toolset has changed. Please keep
1626 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1630 atapci kernel module now includes only generic PCI ATA
1631 driver. AHCI driver moved to ataahci kernel module.
1632 All vendor-specific code moved into separate kernel modules:
1633 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1634 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1635 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1636 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1639 The TTY subsystem of the kernel has been replaced by a new
1640 implementation, which provides better scalability and an
1641 improved driver model. Most common drivers have been migrated to
1642 the new TTY subsystem, while others have not. The following
1643 drivers have not yet been ported to the new TTY layer:
1646 cy, digi, rc, rp, sio
1652 ng_h4, ng_tty, ppp, sl, snp
1654 Adding these drivers to your kernel configuration file shall
1655 cause compilation to fail.
1658 ntpd has been upgraded to 4.2.4p5.
1661 OpenSSH has been upgraded to 5.1p1.
1663 For many years, FreeBSD's version of OpenSSH preferred DSA
1664 over RSA for host and user authentication keys. With this
1665 upgrade, we've switched to the vendor's default of RSA over
1666 DSA. This may cause upgraded clients to warn about unknown
1667 host keys even for previously known hosts. Users should
1668 follow the usual procedure for verifying host keys before
1669 accepting the RSA key.
1671 This can be circumvented by setting the "HostKeyAlgorithms"
1672 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1675 Please note that the sequence of keys offered for
1676 authentication has been changed as well. You may want to
1677 specify IdentityFile in a different order to revert this
1681 The sio(4) driver has been removed from the i386 and amd64
1682 kernel configuration files. This means uart(4) is now the
1683 default serial port driver on those platforms as well.
1685 To prevent collisions with the sio(4) driver, the uart(4) driver
1686 uses different names for its device nodes. This means the
1687 onboard serial port will now most likely be called "ttyu0"
1688 instead of "ttyd0". You may need to reconfigure applications to
1689 use the new device names.
1691 When using the serial port as a boot console, be sure to update
1692 /boot/device.hints and /etc/ttys before booting the new kernel.
1693 If you forget to do so, you can still manually specify the hints
1694 at the loader prompt:
1696 set hint.uart.0.at="isa"
1697 set hint.uart.0.port="0x3F8"
1698 set hint.uart.0.flags="0x10"
1699 set hint.uart.0.irq="4"
1703 The gpt(8) utility has been removed. Use gpart(8) to partition
1707 The version that Linuxulator emulates was changed from 2.4.2
1708 to 2.6.16. If you experience any problems with Linux binaries
1709 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1710 if it fixes the problem contact emulation mailing list.
1713 ISDN4BSD (I4B) was removed from the src tree. You may need to
1714 update a your kernel configuration and remove relevant entries.
1717 I have checked in code to support multiple routing tables.
1718 See the man pages setfib(1) and setfib(2).
1719 This is a hopefully backwards compatible version,
1720 but to make use of it you need to compile your kernel
1721 with options ROUTETABLES=2 (or more up to 16).
1724 The 802.11 wireless support was redone to enable multi-bss
1725 operation on devices that are capable. The underlying device
1726 is no longer used directly but instead wlanX devices are
1727 cloned with ifconfig. This requires changes to rc.conf files.
1728 For example, change:
1729 ifconfig_ath0="WPA DHCP"
1732 ifconfig_wlan0="WPA DHCP"
1733 see rc.conf(5) for more details. In addition, mergemaster of
1734 /etc/rc.d is highly recommended. Simultaneous update of userland
1735 and kernel wouldn't hurt either.
1737 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1738 modules were merged into the base wlan module. All references
1739 to these modules (e.g. in kernel config files) must be removed.
1742 psm(4) has gained write(2) support in native operation level.
1743 Arbitrary commands can be written to /dev/psm%d and status can
1744 be read back from it. Therefore, an application is responsible
1745 for status validation and error recovery. It is a no-op in
1746 other operation levels.
1749 Support for KSE threading has been removed from the kernel. To
1750 run legacy applications linked against KSE libmap.conf may
1751 be used. The following libmap.conf may be used to ensure
1752 compatibility with any prior release:
1754 libpthread.so.1 libthr.so.1
1755 libpthread.so.2 libthr.so.2
1756 libkse.so.3 libthr.so.3
1759 The layout of struct vmspace has changed. This affects libkvm
1760 and any executables that link against libkvm and use the
1761 kvm_getprocs() function. In particular, but not exclusively,
1762 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1763 The effects are minimal, but it's advisable to upgrade world
1767 The latest em driver no longer has support in it for the
1768 82575 adapter, this is now moved to the igb driver. The
1769 split was done to make new features that are incompatible
1770 with older hardware easier to do.
1773 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1774 likewise the kernel option is now GEOM_LINUX_LVM.
1777 The default NFS mount mode has changed from UDP to TCP for
1778 increased reliability. If you rely on (insecurely) NFS
1779 mounting across a firewall you may need to update your
1783 Belatedly note the addition of m_collapse for compacting
1787 The fts(3) structures have been changed to use adequate
1788 integer types for their members and so to be able to cope
1789 with huge file trees. The old fts(3) ABI is preserved
1790 through symbol versioning in libc, so third-party binaries
1791 using fts(3) should still work, although they will not take
1792 advantage of the extended types. At the same time, some
1793 third-party software might fail to build after this change
1794 due to unportable assumptions made in its source code about
1795 fts(3) structure members. Such software should be fixed
1796 by its vendor or, in the worst case, in the ports tree.
1797 FreeBSD_version 800015 marks this change for the unlikely
1798 case that a portable fix is impossible.
1801 To upgrade to -current after this date, you must be running
1802 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1803 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1806 The ADAPTIVE_GIANT kernel option has been retired because its
1807 functionality is the default now.
1810 The AT keyboard emulation of sunkbd(4) has been turned on
1811 by default. In order to make the special symbols of the Sun
1812 keyboards driven by sunkbd(4) work under X these now have
1813 to be configured the same way as Sun USB keyboards driven
1814 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1816 Option "XkbLayout" "us"
1817 Option "XkbRules" "xorg"
1818 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1821 It has been decided that it is desirable to provide ABI
1822 backwards compatibility to the FreeBSD 4/5/6 versions of the
1823 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1824 broken with the introduction of PCI domain support (see the
1825 20070930 entry). Unfortunately, this required the ABI of
1826 PCIOCGETCONF to be broken again in order to be able to
1827 provide backwards compatibility to the old version of that
1828 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1829 again. As for prominent ports this affects neither pciutils
1830 nor xorg-server this time, the hal port needs to be rebuilt
1834 The misnamed kthread_create() and friends have been renamed
1835 to kproc_create() etc. Many of the callers already
1836 used kproc_start()..
1837 I will return kthread_create() and friends in a while
1838 with implementations that actually create threads, not procs.
1839 Renaming corresponds with version 800002.
1848 Avoid using make -j when upgrading. While generally safe, there are
1849 sometimes problems using -j to upgrade. If your upgrade fails with
1850 -j, please try again without -j. From time to time in the past there
1851 have been problems using -j with buildworld and/or installworld. This
1852 is especially true when upgrading between "distant" versions (eg one
1853 that cross a major release boundary or several minor releases, or when
1854 several months have passed on the -current branch).
1856 Sometimes, obscure build problems are the result of environment
1857 poisoning. This can happen because the make utility reads its
1858 environment when searching for values for global variables. To run
1859 your build attempts in an "environmental clean room", prefix all make
1860 commands with 'env -i '. See the env(1) manual page for more details.
1862 When upgrading from one major version to another it is generally best
1863 to upgrade to the latest code in the currently installed branch first,
1864 then do an upgrade to the new branch. This is the best-tested upgrade
1865 path, and has the highest probability of being successful. Please try
1866 this approach before reporting problems with a major version upgrade.
1868 When upgrading a live system, having a root shell around before
1869 installing anything can help undo problems. Not having a root shell
1870 around can lead to problems if pam has changed too much from your
1871 starting point to allow continued authentication after the upgrade.
1875 When upgrading the boot ZFS pool to a new version, always follow
1878 1.) recompile and reinstall the ZFS boot loader and boot block
1879 (this is part of "make buildworld" and "make installworld")
1881 2.) update the ZFS boot block on your boot drive
1883 The following example updates the ZFS boot block on the first
1884 partition (freebsd-boot) of a GPT partitioned drive ad0:
1885 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1887 Non-boot pools do not need these updates.
1891 If you are updating from a prior version of FreeBSD (even one just
1892 a few days old), you should follow this procedure. It is the most
1893 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1895 make kernel-toolchain
1896 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1897 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1899 To test a kernel once
1900 ---------------------
1901 If you just want to boot a kernel once (because you are not sure
1902 if it works, or if you want to boot a known bad kernel to provide
1903 debugging information) run
1904 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1905 nextboot -k testkernel
1907 To just build a kernel when you know that it won't mess you up
1908 --------------------------------------------------------------
1909 This assumes you are already running a CURRENT system. Replace
1910 ${arch} with the architecture of your machine (e.g. "i386",
1911 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1913 cd src/sys/${arch}/conf
1914 config KERNEL_NAME_HERE
1915 cd ../compile/KERNEL_NAME_HERE
1920 If this fails, go to the "To build a kernel" section.
1922 To rebuild everything and install it on the current system.
1923 -----------------------------------------------------------
1924 # Note: sometimes if you are running current you gotta do more than
1925 # is listed here if you are upgrading from a really old current.
1927 <make sure you have good level 0 dumps>
1929 make kernel KERNCONF=YOUR_KERNEL_HERE
1931 <reboot in single user> [3]
1938 To cross-install current onto a separate partition
1939 --------------------------------------------------
1940 # In this approach we use a separate partition to hold
1941 # current's root, 'usr', and 'var' directories. A partition
1942 # holding "/", "/usr" and "/var" should be about 2GB in
1945 <make sure you have good level 0 dumps>
1948 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1949 <maybe newfs current's root partition>
1950 <mount current's root partition on directory ${CURRENT_ROOT}>
1951 make installworld DESTDIR=${CURRENT_ROOT}
1952 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1953 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1954 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1955 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1956 <reboot into current>
1957 <do a "native" rebuild/install as described in the previous section>
1958 <maybe install compatibility libraries from ports/misc/compat*>
1962 To upgrade in-place from stable to current
1963 ----------------------------------------------
1964 <make sure you have good level 0 dumps>
1966 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1968 <reboot in single user> [3]
1975 Make sure that you've read the UPDATING file to understand the
1976 tweaks to various things you need. At this point in the life
1977 cycle of current, things change often and you are on your own
1978 to cope. The defaults can also change, so please read ALL of
1979 the UPDATING entries.
1981 Also, if you are tracking -current, you must be subscribed to
1982 freebsd-current@freebsd.org. Make sure that before you update
1983 your sources that you have read and understood all the recent
1984 messages there. If in doubt, please track -stable which has
1985 much fewer pitfalls.
1987 [1] If you have third party modules, such as vmware, you
1988 should disable them at this point so they don't crash your
1991 [3] From the bootblocks, boot -s, and then do
1996 adjkerntz -i # if CMOS is wall time
1997 Also, when doing a major release upgrade, it is required that
1998 you boot into single user mode to do the installworld.
2000 [4] Note: This step is non-optional. Failure to do this step
2001 can result in a significant reduction in the functionality of the
2002 system. Attempting to do it by hand is not recommended and those
2003 that pursue this avenue should read this file carefully, as well
2004 as the archives of freebsd-current and freebsd-hackers mailing lists
2005 for potential gotchas. The -U option is also useful to consider.
2006 See mergemaster(8) for more information.
2008 [5] Usually this step is a noop. However, from time to time
2009 you may need to do this if you get unknown user in the following
2010 step. It never hurts to do it all the time. You may need to
2011 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2012 install) after the buildworld before this step if you last updated
2013 from current before 20130425 or from -stable before 20130430.
2015 [6] This only deletes old files and directories. Old libraries
2016 can be deleted by "make delete-old-libs", but you have to make
2017 sure that no program is using those libraries anymore.
2019 [8] In order to have a kernel that can run the 4.x binaries needed to
2020 do an installworld, you must include the COMPAT_FREEBSD4 option in
2021 your kernel. Failure to do so may leave you with a system that is
2022 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2023 required to run the 5.x binaries on more recent kernels. And so on
2024 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2026 Make sure that you merge any new devices from GENERIC since the
2027 last time you updated your kernel config file.
2029 [9] When checking out sources, you must include the -P flag to have
2030 cvs prune empty directories.
2032 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2033 "?=" instead of the "=" assignment operator, so that buildworld can
2034 override the CPUTYPE if it needs to.
2036 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2037 not on the command line, or in /etc/make.conf. buildworld will
2038 warn if it is improperly defined.
2041 This file contains a list, in reverse chronological order, of major
2042 breakages in tracking -current. It is not guaranteed to be a complete
2043 list of such breakages, and only contains entries since October 10, 2007.
2044 If you need to see UPDATING entries from before that date, you will need
2045 to fetch an UPDATING file from an older FreeBSD release.
2047 Copyright information:
2049 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2051 Redistribution, publication, translation and use, with or without
2052 modification, in full or in part, in any form or format of this
2053 document are permitted without further permission from the author.
2055 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2056 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2057 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2058 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2059 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2060 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2061 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2062 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2063 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2064 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2065 POSSIBILITY OF SUCH DAMAGE.
2067 Contact Warner Losh if you have any questions about your use of